should be used. If the contractor’s tool is acceptable, then this merely requires Government direct, networked access to that tool. Provide a risk cube (see Figure Technical Risks and Mitigation Planning – or a listing of the current system-level technical risks with: As-of date Risk rating Description Driver Mitigation status Expectations: Programs commonly use hierarchal boards to address risks and have integrated risk systems with their contractors, and their approach to identify risks is both top-down and bottoms-up. Risks related to technology maturation, integration, and each design consideration indicated in Table 4.6-1 should be considered in risk identification process. Figure 3.3-1 Risk Cube (mandated) (sample) Note: Include an as-of date time sensitive figure – Figure 3.3-2 Risk Burn-down Plan (optional) (sample) Note: Include an as-of date time sensitive figure – Technical Organization Government Program Office Organization - Provide planned program office organization structure (i.e., wiring diagram to illustrate hierarchy) with an as-of date and include the following elements: Legend, as applicable (e.g., Functional Leads (e.g., T&E, logistics, risk, reliability, software) Organization to the program Core, matrix, and contractor support office reports personnel Program Manager (PM) Field or additional Service representatives Systems Engineer (LSE/CSE)
should be used. If the contractor’s tool is acceptable, then this merely requires Government direct, networked access to that tool. Technical Risks and Mitigation Planning – Provide a risk cube (see Figure or a listing of the current system-level technical risks with: As-of date Risk rating Description Driver Mitigation status Expectations: Programs commonly use hierarchal boards to address risks and have integrated risk systems with their contractors, and their approach to identify risks is both top-down and bottoms-up. Risks related to technology maturation, integration, and each design consideration indicated in Table 4.6-1 should be considered in risk identification process. Figure 3.3-1 Risk Cube (mandated) (sample) Note: Include an as-of date – time sensitive figure Figure 3.3-2 Risk Burn-down Plan (optional) (sample) Note: Include an as-of date – time sensitive figure Technical Organization Government Program Office Organization - Provide planned program office organization structure (i.e., wiring diagram to illustrate hierarchy) with an as-of date and include the following elements: Legend, as applicable (e.g., Organization to the program office reports Program Manager (PM) Systems Engineer (LSE/CSE) Functional Leads (e.g., T&E, logistics, risk, reliability, software) Core, matrix, and contractor support personnel Field or additional Service representatives
PDUSD-Approved.SEP_Outline-04-20-2011.docx