Systems Engineering Plan (SEP)
The SEP is used as a management tool to guide the program’s Systems Engineering (SE) activities by providing a documented technical approach for the program. The SEP includes key technical risks, processes, resources, metrics, and completed and scheduled SE activities. In accordance with DoDI 5000.02, the SEP is required at Milestones (MSs) A, B, and C, and all programs must use the OSD approved SEP Outline to guide SEP preparation.
In accordance with DoDI 5000.02 and the SEP Outline, the SEP contains the program’s ESOH planning information and related design considerations. ESOH design considerations are particularly important for MS A to ensure SE addresses ESOH design considerations during the Technology Maturation and Risk Reduction (TMRR) phase, which includes a significant amount of the design development, testing, and the Preliminary Design Review. Starting prior to MS A, the program office should begin to document ESOH hazard data in the government’s hazard tracking system (HTS) and prepare an initial National Environmental Policy Act (NEPA)/ Executive Order (E.O.) 12114, Environmental Effects Abroad of Major Federal Actions, Compliance Schedule for the TMRR phase. These may be included in the MS A SEP as attachments in Table 4-6.1, Design Considerations.
The minimum ESOH planning information in the SEP should include:
- identification of ESOH responsibilities, organizational structure, and the User Representative
- identification of required ESOH certifications (e.g., approvals, endorsements, releases)
- description of contract language and requirements (e.g., Data Item Descriptions, Contract Data Requirements Lists [CDRL])
- description of the approach to minimize ESOH risks through design and other methods in accordance with MIL-STD-882E, DoD Standard Practice for System Safety (e.g., logistics, training, hazard communication, compliance)
- description of the method for tracking hazards throughout the life-cycle of the system
In accordance with the SEP Outline, Table 4.6-1, Design Considerations, must include specific ESOH information – Cognizant Program Management Organization, Certification, Documentation, Contractual Requirements (CDRL Number), and Description/Comments. A best practice is to include detailed ESOH information in all appropriate sections of the SEP and provide cross-references to those locations in the SEP Design Considerations Table to avoid duplication. Additional sections of the SEP that may be appropriate for ESOH input include 2.2: Technical Certifications, 3.3: Engineering and Integration Risk Management, 3.4.1: Government Program Office Organization, 3.4.2: Program Office Technical Staffing Levels, 3.4.4: Engineering Team Organization and Staffing, 3.6: Technical Performance Measures and Metrics, 4.4: Technical Reviews, and 4.7: Engineering Tools. See the Guide to ESOH in the SEP, PESHE and NEPA/E.O. 12114 Compliance Schedule, for detailed guidance on incorporating ESOH planning and design considerations into the SEP.
The SEP is used as a management tool to guide the program’s Systems Engineering (SE) activities by providing a documented technical approach for the program. The SEP includes key technical risks, processes, resources, metrics, and completed and scheduled SE activities. In accordance with DoDI 5000.02, the SEP is required at Milestones (MSs) A, B, and C, and all programs must use the OSD approved SEP Outline to guide SEP preparation.
In accordance with DoDI 5000.02 and the SEP Outline, the SEP contains the program’s ESOH planning information and related design considerations. ESOH design considerations are particularly important for MS A to ensure SE addresses ESOH design considerations during the Technology Maturation and Risk Reduction (TMRR) phase, which includes a significant amount of the design development, testing, and the Preliminary Design Review. Starting prior to MS A, the program office should begin to document ESOH hazard data in the government’s hazard tracking system (HTS) and prepare an initial National Environmental Policy Act (NEPA)/ Executive Order (E.O.) 12114, Environmental Effects Abroad of Major Federal Actions, Compliance Schedule for the TMRR phase. These may be included in the MS A SEP as attachments in Table 4-6.1, Design Considerations.
The minimum ESOH planning information in the SEP should include:
· identification of ESOH responsibilities, organizational structure, and the User Representative
· identification of required ESOH certifications (e.g., approvals, endorsements, releases)
· description of contract language and requirements (e.g., Data Item Descriptions, Contract Data Requirements Lists [CDRL])
· description of the approach to minimize ESOH risks through design and other methods in accordance with MIL-STD-882E, DoD Standard Practice for System Safety (e.g., logistics, training, hazard communication, compliance)
· description of the method for tracking hazards throughout the life-cycle of the system
In accordance with the SEP Outline, Table 4.6-1, Design Considerations, must include specific ESOH information – Cognizant Program Management Organization, Certification, Documentation, Contractual Requirements (CDRL Number), and Description/Comments. A best practice is to include detailed ESOH information in all appropriate sections of the SEP and provide cross-references to those locations in the SEP Design Considerations Table to avoid duplication. Additional sections of the SEP that may be appropriate for ESOH input include 2.2: Technical Certifications, 3.3: Engineering and Integration Risk Management, 3.4.1: Government Program Office Organization, 3.4.2: Program Office Technical Staffing Levels, 3.4.4: Engineering Team Organization and Staffing, 3.6: Technical Performance Measures and Metrics, 4.4: Technical Reviews, and 4.7: Engineering Tools. See the Guide to ESOH in the SEP, PESHE and NEPA/E.O. 12114 Compliance Schedule, for detailed guidance on incorporating ESOH planning and design considerations into the SEP.
