Attachment_F_Risk_Assessment_Matrix_Instructions_Template.pptx
PPTX presentation 181 KB Posted
- Attached to
- CoasterChase
- Opportunity number
- HR001125S0014
About this file
The file is a Risk Assessment Matrix Instructions Template for proposal submissions to a Broad Agency Announcement (BAA). The template requires proposers to identify and analyze the top five technical risks associated with proposed research, including detailed risk statements, potential impact quantification, mitigation strategies, and contingency plans. The template uses a 5x5 matrix to assess risk probability and consequence, with specific guidance on documenting risk scores before and after proposed mitigation efforts.
Two example risks are detailed in the template: a Wafer Run risk involving chip production challenges (with potential $4M cost and 3-month schedule delay) and a Weather risk that could impact scheduled test events. The template mandates that risk descriptions include likelihood of occurrence, potential consequences, handling strategies, and specific mitigation timelines. Proposers must submit the Risk Assessment Matrix in Microsoft PowerPoint using a "[OrganizationName]_Risk_Assessment_Matrix" file naming convention, and failure to follow the prescribed format may result in proposal non-review.
Risk Assessment Matrix
View the file
Other files
| File | Type | Posted |
|---|---|---|
| HR001125S0014-Amendment-01.pdf | ||
| Attachment_E_Cost_Proposal_Spreadsheet__UPDATE_.xlsx | XLSX spreadsheet | |
| Attachment_C_Proposal_Volume_1_Instructions_Template.pdf | ||
| Attachment_E_Cost_Proposal_Spreadsheet_v3.xlsx | XLSX spreadsheet | |
| Attachment_B_Proposal_Summary_Slide_Instructions_Template.pptx | PPTX presentation | |
| Attachment_D_Proposal_Volume_2_Instructions_Template.docx | DOCX document | |
| HR001125S0014.pdf | ||
| Attachment_A_Abstract_Instructions_Template.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Use of this template is required for all proposal submissions to this BAA. Proposers must include all information in the Proposal Summary Slide Template, Proposal Instructions and Volume I Template (Technical and Management), Proposal Instructions and Volume II Template (Cost), and Risk Assessment Matrix Instructions and Template to constitute a full proposal submission. Proposals not meeting the format prescribed herein may not be reviewed.
The Risk Assessment Matrix Template must include all components and must be submitted in Microsoft PowerPoint format under the file naming convention “[OrganizationName]_Risk_Assessment_Matrix”.
Clearly describe the top five technical risks associated with the proposed research. For each risk:
Provide a clear, concise Risk Statement / Description of the issue Quantify the potential impact on program success. Consider factors such as: schedule delays, cost overruns, performance degradation, inability to achieve key milestones.
Provide a detailed mitigation plan that includes specific actions to be taken to reduce the likelihood and/or impact of the risk. Mitigation plans should be realistic, feasible, and cost-effective.
Clearly articulate the potential payoff associated with successfully avoiding or overcoming the risk.
Describe any contingency plans that will be implemented if mitigation strategies are not successful.
Outline your approach to monitor risks, track progress, and adjust plans as needed.
Risk Assessment Matrix Instructions and Template
Risk Overview: 5 X 5 Matrix What is going to make this program fail?
80-90% 60-80% 40-60% 20-40% 1-20%
| 1 Minimal | 2 | ||
| Minor | 3 | ||
| Moderate | 4 | ||
| Significant | 5 |
Critical
Probability/Likelihood Consequence/Impact Wafer Run before mitigation Probability of unsuccessful Wafer Run is high, with critical impact.
Risk Score before mitigation = 20 Risk Score after mitigation = 9 Wafer Run after mitigation Probability of weather impacting scheduled test event.
Risk Score before mitigation = 10 Risk Score after mitigation = 6
Risk Overview: Description What is going to make this program fail?
| Risk ID | ||||||
| /Rank Order | Name | Risk Statement /Description | Likelihood of event occurring | Consequence /Impact to the Program | Handling Strategy | Mitigation Strategy |
| Timeline to fix and/or realize |
| 1 | Wafer Run | What is the problem statement (in full sentences). E.g. The Foundry has just developed their 14 nm process for chip wafer runs. If the Foundry wafer run does not produce high yield chips, then my company will not have the chips to provide for the camera sensors. No other Foundry can produce the chip. We have older chips that do not meet the full performance spec. | Level 4: Highly Likely | |
| Since this is the first time for this process this event has a high probability of occurring | Level 5: Significant Impact |
Cost: Each wafer run is approximately $4M Schedule: Each run takes approximately 3 months. Additional unplanned run will cause a minimum of 3-month delay.
Performance: If the runs are unsuccessful then the camera sensors will not meet the metrics.
Accept (and Monitor)
Avoid
Transfer
Control
Burn Down 1) Request additional $4M from the customer for a second run: 6-month schedule delay
2) Use currently available chips: Less performance capability, no delay in program.
3) Potential to have AFRL fund cost
4) Modeling and Sim
5) Series of activities that decrease or mitigate the risk. Performers will spend 3 months reviewing the design and mask.
Initial wafer run in month 4. Results expected in month 5.
Decision to rerun or use existing chips would be in month 6`
| 2 | Weather | Adverse weather may impact our ability to get good data at the scheduled test event. Facility availability is limited, and contract end date is 2 months after planned test event. | Level 5: Significant Likelihood |
| Level 2: Minor Impact |
Facility may not be available another time.
Could be that some participants / transition partners will be unable to reschedule if needed.
Equip must be shipped in advance.
Sunk travel and shipping costs. Accept (and Monitor) 1) During event planning, identify and communicate a contingency date in case of adverse weather.
2) Build timeline to ensure time to process data after the contingency date.
3) Follow the forecast and make a determination a week out. Decision to reschedule would be in month 21 of 24.
image2.png
File details come from the government source that posted it. Updated .