What do you think was done right on the System's Risk Management and Evaluation Methodology for the project below? Any suggestions for improvements?

Overview of Proposed Project

Best Glide Ratio System is a system that will automatically compute the aircraft's glide ratio, distance that the aircraft can cover given the current glide ratio and provide the pilot with nearest airport location. BGRS will use Global Positioning Satellite (GPS) almanac data to determine if the aircraft is capable of reaching the nearest airport and automatically provide a track to that airport. BGRS consists of a small display or head unit that is mounted in the aircraft's glare shield. The display will provide the pilot with critical information such as the current glide ratio, time left until altitude is exhausted, remaining distance available, and track to the nearest airport if it is reachable. BGRS will reduce the pilot workload during an emergency condition and eliminate the need for the pilot to make calculations by hand or flight computer. BGRS will be certified and comply with the latest FAA regulations.

Risk Philosophy

The overall risk philosophy of the BGRS program is to either transfer, accept, or control the risk. That is, the program is not risk adverse due to the system being developed. Although it is intended to be used on General Aviation (GA) aircraft, it does not fall into Federal Aviation Administrations minimum equipment required for either visual or instrument flight rules. It is intended to supplement, not replace pilot decision making. Lastly, the system relies heavily on the Global Positioning Satellite (GPS) system which is used throughout the aviation industry today.

Risk Management Approach

The primary goal of risk management is to provide a disciplined process to identify and control risks throughout the system life cycle (INCOSE, 2015). Using a structured risk management approach enables the program to mitigate the effects of cost, schedule, and technical risks to the program (INCOSE, 2015). BGRS will follow the following process to manage risk:

• Document the risk in the programs risk register
• Categorize the risk in terms of cost, schedule, or technical performance
• Establish the level of risk in terms of probability of likelihood and consequence
• Develop a risk mitigation strategy
• Continually monitor and assess risks

Each month a risk meeting will be held to status BGRS risks. The meeting will be chaired by the Program Manager and Lead Systems Engineer. All integrated product leads will attend the meeting. The purpose of the meeting is to ensure that the level of risk is still current, and that the mitigation strategy is effective for all open risks. Additionally, it provides a forum for introduction of new BGRS risks.

Risk Management Demonstration

Table 1 provides the current risk register for BGRS with examples from each risk category. Since risk assessment is a continuous process, the table is still in work. It should be noted that ideally risks should be identified in the planning phase. Each risk is described using the If , then format. Each risk is then categorized based on the impact - cost, schedule, or technical. The likelihood of occurrence and consequence values are established qualitatively and range from 1 to 5, with 5 being the most severe. A mitigation strategy is developed for each risk. Lastly, the status of each risk is tracked. Risks status will either be in Open, Retired, or Transferred status.

Table 1

BGRS Risk Register

Risk Number Title Risk Description ( format) Category Likelihood Consequence Mitigation Steps Status If material delivery is late, then build task (7.1) - Identify long lead items and release BGRS-R-01 Material will slip along with predecessors. Schedule 2 4 POs ahead of other items. Open If simulation software lacks fidelity required to - Complete technical analysis of accurately model flight conditions, then glide commercially avial able simulation BGRS-R-02 Simulation Software calcuations could be skewed. Technical 3 software products. Open - Identify software language to be used If software staffing is inadequate to support early, investigate potential to staff schedule, then labor will have to be internally from other engineering BGRS-R-03 Software Labor supplemented with contractors. Cost 2 2 disciplines. OpenHigh High X X Consequence Medium Consequence Medium Low Low Low Medium High Low Medium High Likelihood Likelihood BGRS-R-01 - Material BGRS-R-02 - Simulation Software High Consequence Medium X LOW Low Medium High Likelihood BGRS-R-03 - Software Labor