Risk Qualitativ

Project Aerospace Risk Worksheet

Project Manager Name Here

Probability
Trigger
ID Risk Description Severity

Impact
Event/Indicator

The phone doesn't

1 2 1 LOW Nasty email
ring

Team member
2 doesn't do as 3 3 MEDIUM Nothing produced
promised

The wings don't stay

3 1 3 CRITICAL Wings fall off
on the plane

5 0 0

6 0 0

7 0 0

8 0 0

9 0 0

10 0 0

11 0 0

12 0 0

13 0 0
 14 0 0

15 0 0

Developed by PMI for PMIstandards+ with contributions from Dave Maynard, PMP ©PROJECT MANAGEMENT IN
 Risk Qualitative Assessment
ksheet

Risk Response and Description Contingency Plan

Send a nice email back Send flowers

Take appropriate action Find a good volunteeer

Strenthen wing attachments

m Dave Maynard, PMP ©PROJECT MANAGEMENT INSTITUTE, INC.
 Sponsor Project Management Institute

Updated

Date
Owner Status Date to Review
Entered

Name Here Open

Name Here Open

Name Here Open

 Failure Modes and Effects An
Project Aerospace Risk Worksheet

Project Manager Name Here

Probability
Potential

Severity
Item and Function/ Potential Potential Cause(s)/ Current Controls
Effect(s) of
Requirements Failure Mode Mechanism(s) of Failure - Prevention
Failure

Didn't update off- Update each

PC running Updates Unusable 7 8
housrs night.

MS Word
PC Failure Unusable 10 Operator Error 2 None
Working
Developed by PMI for PMIstandards+ with contributions from Dave Maynard, PMP ©PROJECT MANAGEMENT IN
des and Effects Analysis
Project
SponsorManagement Institute

Updated
Updated 12/15/2015
Detection

Current RPN Target Completion

Controls - Recommended Action Assigned Owne
Date
Detection

Check update Implement nightly

2 112 Name Date
log updates

None 10 200 Provide Training Name Date

PROJECT MANAGEMENT INSTITUTE, INC.
 Effect

None
Very Minor
Minor
Very Low
Low
Moderate
High
Very High
Hazardous with warning
Hazardous without warning

Detection
Almost Certain
Very High
High
Moderately high
Moderate
Low
Very Low
Remote
Very Remote
Absolute certainty

Probability of Failure
Remote: Failure is unlikely

Low: Relatively few failures

Moderate: Occasional failures

High: Repeated failures

Very High: Failure is almost

inevitable
Developed by PMI for PMIstandards+ with contributions from Dave Maynard, PMP ©PROJECT MANAGEMENT IN
 Severity of Effect

No effect
System operable with slight degradation of performance
System operable with moderate degradation of performance
System operable with significant degradation of performance
System inoperable without service interruption
System inoperable with slight service interruption without stopping delivery.
System inoperable with moderate service interruption without stopping delivery.
System inoperable with significant service interruption without stopping delivery.
A potential failure mode affects safe system operation, or completely stops delivery, with warning.
A potential failure mode affects safe system operation, or completely stops delivery, without warning.

Detectability
Design control will detect potential cause/mechanism and subsequent failure mode
Very high the design control will detect potential cause/mechanism and subsequent failure mode
High chance the design control will detect potential cause/mechanism and subsequent failure mode
Moderately high chance the design control will detect potential cause/mechanism and subsequent failure mode
Moderate chance the design control will detect potential cause/mechanism and subsequent failure mode
Low chance the design control will detect potential cause/mechanism and subsequent failure mode
Very low chance the design control will detect potential cause/mechanism and subsequent failure mode
Remote chance the design control will detect potential cause/mechanism and subsequent failure mode
Very remore chance the design control will detect potential cause/mechanism and subsequent failure mode
Design control cannot detect potential cause/mechanism and potential failure mode

Failure Probability
No system failure expected
One system failure expected in .25% (2.5 per 1000) of execution instances or will result in infrastructure component
downtime of up to 1 hour per month
One system failure expected in .5% (5 per 1000) of execution instances or will result in infrastructure component
downtime of up to 2 hours per month
One system failure expected in 1% (10 per 1000) of execution instances or will result in infrastructure component
downtime of up to 5 hours per month
One system failure expected in 2% (20 per 1000) of execution instances or will result in infrastructure component
downtime of up to 8 hours per month
One system failure expected in 5% (50 per 1000) of execution instances or will result in infrastructure component
downtime of up to 24 hours per month
Repeatable system failures expected in 10% (1 per 10) of program execution instances or will result in infrastructur
component downtime of up to 36 hours per month
Repeatable system failures expected in 20% (2 per 10) of program execution instances or will result in infrastructure
component downtime of up to 48 hours per month
Failures expected in 30% (3 per 10) of program execution instances or will result in infrastructure component
downtime of up to 72 hours per month
Failures expected in 50% (5 per 10) of program execution instances or will result in infrastructure component
downtime of up to 96 hours per month
or PMIstandards+ with contributions from Dave Maynard, PMP ©PROJECT MANAGEMENT INSTITUTE, INC.
Ranking

1
2
3
4
5
6
7
8
9
10

Ranking
1
2
3
4
5
6
7
8
9
10

Ranking
1

10
 Common Data

Filling out the Data sheet completes the header portion of all remaining sheets in the proj

Project
Project #
Project Manager
Sponsor
Last updated
Developed by PMI for PMIstandards+ with contributions from Dave Maynard, PMP ©PROJECT MANAGE
 Common Data

Filling out the Data sheet completes the header portion of all remaining sheets in the project workbook.

Aerospace Risk Worksheet

Name Here
Project Management Institute
r PMIstandards+ with contributions from Dave Maynard, PMP ©PROJECT MANAGEMENT INSTITUTE, INC.
Identifying Risks
Identifying risks to achieving objectives so they may be managed will generally take place during the quotation, order receipt -
early in the life of a project as possible, because a risk not identified at this stage may be excluded from further analysis.

What Can Happen, Where and When?

The aim is to generate a comprehensive list of sources of possible risks and future events that could impact the objectives of d
Tools for identifying risks may include: Fault Tree Analysis (FTA), Failure Mode and Effects Analysis (FMEA), Historical Data Ana
• Requirements.– Customer-identified or your company’s determined special requirements
• Technology.- The degree to which existing technology has demonstrated sufficient maturity to be realistically capable of me
• Production/facilities. - The ability to achieve performance objectives based on available manufacturing resources and proces
• Outsourcing capabilities. The abilities, experience, knowledge, and availability of outsourced process suppliers
• Cost. The ability of your company to achieve cost objectives. This includes the effects of errors in estimating techniques used
• Management. The degree to which plans and strategies exist and are realistic and consistent. Staffing and supervision should
• Schedule. The sufficiency of time allocated to achieve objectives—short lead times from customers, long lead times from sup

Why and How Can it Happen?

Having identified what events might occur, it is necessary to determine the root causes for these events. There may be many w
event.
During the risk assessment for those risks, the root causes (risks) are to be analyzed with the process control established for th

Risk Evaluation
Using the results of the calculation, the overall risk level can be found on the Risk Assessment Scoring chart at the appropriate

For risks scoring in the low (green) category, risk mitigating measures and/or actions are not required. Monitor and Review for
For risks scoring in the moderate (yellow) category, existing controls must be evaluated for effectiveness. For controls assesse
Risk / Reward, etc.).
All risks scoring in the high (red) category shall require risk mitigating measures and/or actions and monitoring for further asse
Risk Mitigating Measures and Actions
Risk mitigating measures and/or actions are those options for modifying risks; the selection and implementation of those optio

Risk Analysis
Once the root causes have been identified, their likelihood to occur and the severity of consequences should they occur are to

Each root cause shall be assigned a likelihood level and a consequence level score. These will be used to evaluate the overall r
Risk Evaluation
Using the results of the calculation, the overall risk level can be found on the Risk Assessment Scoring chart at the appropriate

For risks scoring in the low (green) category, risk mitigating measures and/or actions are not required. Monitor and Review for

For risks scoring in the moderate (yellow) category, existing controls must be evaluated for effectiveness. For controls assesse
Risk / Reward, etc.).

All risks scoring in the high (red) category shall require risk mitigating measures and/or actions and monitoring for further asse

Risk Mitigating Measures and Actions

Risk mitigating measures and/or actions are those options for modifying risks; the selection and implementation of those optio

The Risk Mitigation Plan involves the cyclical process of:

Selection of Mitigating Options
Selecting the most appropriate mitigating options involves balancing the costs of implementation against the benefits derived
consider all both direct and indirect costs and all benefits, whether tangible or intangible.

Decisions should account for the need to consider carefully those rare but severe risks that may warrant risk mitigations that a
If budgetary constraints exist, the mitigation plan should clearly specify the priority order in which measures and/or actions sh
If after implementation residual risk remains, this risk should be evaluated and a decision should be made about whether to re

Preparing and Implementing Risk Mitigation Plans

The purpose of the risk mitigation plan is to document how the chosen options will be implemented. The plan may be docume
• Task/issue description;
• Action/response;
• Owner of task/issue;
• Timing and scheduling requirements, and
• Performance measures.

Monitor and Review

Ongoing review is essential to ensure that the management plan remains relevant and effective. The factors that affect the lik
delivery performance, as well as actual progress against the mitigation plan, should provide information about the effectivene
Developed by PMI for PMIstandards+ with contributions from Dave Maynard, PMP ©PROJECT MANAGEMENT INSTITUTE, INC