DARPA_PS_26_137_Firefox_Attch_G_Risk_Matrix.pptx
PPTX presentation 286 KB Posted
- Attached to
- Firefox
- Solicitation number
- DARPA-PS-26-137
About this file
This is a Risk Matrix guidance template document for a DARPA proposal submission related to the Firefox program (DARPA-PS-26-137). The document provides instructions and examples for contractors to identify, assess, and present major risks associated with their proposed approach to developing non-invasive brain-computer interface (BCI) technology.
The template requires proposers to identify risks across multiple categories—technical, programmatic, contractual, and other cost, schedule, or performance-impacting areas—and present them in a structured format. For each identified risk, contractors must provide: a risk statement with likelihood of occurrence, consequence to the program, and mitigation strategy; a likelihood level (1-5 scale, ranging from "Not Likely" at >1% to <20% probability to "Near Certainty" at >80% to <99%); a consequence level (1-5 scale measuring deviation from cost, schedule, and performance baselines); and a target resolution date with post-mitigation consequence assessment. The document includes sample likelihood and consequence criteria, example risk assessment formats, and guidance on presenting risk summary matrices by category. Proposers must remove all guidance slides from their final presentation submissions and organize identified risks into one table per risk category, clearly showing pre- and post-mitigation risk levels.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| DARPA-PS-26-137.pdf | ||
| DARPA_PS_26_137_Firefox_Attach_D_Cost_Proposal_Spreadsheet.xlsx | XLSX spreadsheet | |
| DARPA_PS_26_137_Firefox_Attach_C_Model_OT_for_Prototype.docx | DOCX document | |
| DARPA_PS_26_137_Firefox_Attch_B_Abstract_Template.docx | DOCX document | |
| DARPA_PS_26_137_Firefox_Attch_A_Abstract_Summary_Template.pptx | PPTX presentation | |
| DARPA_PS_26_137_Firefox_Attch_F_OPP_Guidelines_and_Instructions.docx | DOCX document | |
| DARPA_PS_26_137_Firefox_Attch_E_Milestone_and_Payment_Schedule.xlsx | XLSX spreadsheet |
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
Please identify the major risks in your approach that are likely to have risk to cost, time, or performance.
Include your definitions of Likelihood and Consequence (additional guidance provided on additional slides) To the extent possible, quantify the likelihoods and consequences Present your identified risk items One table per risk category (technical, programmatic, contractual, or other category that will impact cost, schedule, performance) You must categorize your risks Present your risk summary matrices by category Show the pre- and post-mitigation risk levels for the identified risks Guidance – Risks and Mitigation Plan Please remove this guidance slide from your final presentation
Guidance – Two Aspects to Risk Likelihood:
Risk likelihood is the evaluated probability an event will occur given existing conditions.
The estimated likelihood of the risk should be tied to a specific well-defined risk event or condition and risk statement.
The probability of occurrence should be established based on quantitative programmatic and engineering analyses to the extent practical.
Consequence:
During analysis, each risk should be evaluated in terms of impact to the program (i.e., effect of the event on program cost, schedule, and performance) should the risk be fully realized.
Risk consequence is measured as a deviation against program cost, schedule, and performance baselines.
While the government and contractor will at times have different perspectives on risks and priorities, they should seek to have a common framework for risk consequence and likelihood criteria.
Sample Risk Likelihood Criteria (It is up to your expert judgment on the specifics for this slide and the next slide for consequence)
| LEVEL | LIKELIHOOD | Probability of Occurrence | Log Scale of Likelihood |
| 5 | Near Certainty | >80% to < 99% | 5 (likely): 1:10 |
| 4 | Highly Likely | >60% to < 80% | 4 (somewhat likely): 1:1000 |
| 3 | Likely | >40% to < 60% | 3 (somewhat unlikely): 1:10,000 |
| 2 | Low Likelihood | >20% to < 40% | 2 (unlikely): 1:100,000 |
| 1 | Not Likely | >1% to < 20% | 1 (very unlikely): 1 in 1,000,000 |
| Risk Statement | Likelihood of event occurring | Consequence to the program | Mitigation strategy |
| Risk 1 |
Brief description Performance metric Category of risk (e.g., technical, programmatic, contractual,…)
| Likelihood level (1, 2, 3, 4, or 5) | |
| Explanation, risk drivers | Consequence level (1, 2, 3, 4, or 5) |
Type of consequence (e.g., cost, schedule, performance, transition, etc) Explanation Description Target resolution date Post-mitigation consequence level
| Risk 2 |
| … |
| Risk N |
Sample Risk Assessments and Mitigations Summary (Present by category: technical, programmatic, contractual, or other category that will impact cost, schedule, performance,…)
Guidance: Risk Matrix Example
Sample Risk Summary Matrix (use one matrix per category) Category: Technical (Can be Technical, Programmatic, Contractual or other category that will have significant impact on the program in terms of cost, schedule, performance)
| 5 | |||||
| 4 | |||||
| 3 | |||||
| 2 | |||||
| 1 | |||||
| 1 | 2 | 3 | 4 | 5 |
Risk #1:
Risk #2:
Risk #3:
Risk #4:
Consequence Probability/Likelihood image3.png
File details come from the government source that posted it. Updated .