Joint Capabilities Integration & Development System (JCIDS) Process
- Overview: JCIDS Process
- Overview: Procurement Process
- Capabilities Based Assessment (CBA)
- Initial Capabilities Document (ICD)
- Capability Development Document
- Capability Production Document (CPD)
- Instruction: CJCSI 3170.01H
 
- Capabilities Based Assessment (CBA)
- Concept of Operations (CONOPS)
- DOTMLPF-P Analysis
- DOTMLPF-P Change Recommendation
- Force Protection KPP
- Functional Area Analysis (FAA)
- Functional Capabilities Board (FCB)
- Functional Configuration Audit (FCA) 
- Functional Needs Analysis (FNA)
- Functional Solutions Analysis (FSA)
- ICD or CDD Waiver Request
- Information Support Plan (ISP)
- Interoperability
- J8 Force Directorate
- JCIDS Gatekeeper
- JCIDS Process Flow Chart
- JCIDS Responsibilities
- JCIDS Studies Repository
- Joint Capability Tech Demonstration
- Joint Capabilities Board (JCB)
- Joint Capabilities Document (JCD)
- Joint Operations Concept (JOpsC)
- Joint Staff Responsibilities
- Joint Requirements Oversight Council
- Joint Requirements Prioritization
- Joint Urgent Operational Need (JUON)
- Key Interface Profiles
- Key Performance Parameters (KPP)
- Key System Attributes (KSA)
- Military Utility Assessment (MUA)
- Net-Ready KPP
- Non-Materiel Solution
- Post-Implementation Review (PIR)
- Post Independent Analysis
- Requirements Document Sequence
- Requirements Training & Certification
- Survivability Key Performance Parameter
- Sustainment KPP
- System Functional Review (SFR)
- System Requirements Review (SRR)
- System Threat Assessment
- System Verification Review (SVR)
- Systems Engineering Plan (SEP)
 
 
 
 
 
 
 
JCIDS Process
Systems Engineering Plan
 

DoDI 5000.02 Systems Engineering PlanThe Systems Engineering Plan (SEP) is a living document that details the execution, management, and control of the technical aspects of an acquisition program from conception to disposal. The SEP outlines how the systems engineering process is applied and tailored to meet objectives for each acquisition phase. The SEP captures a program’s current and evolving systems engineering strategy and its relationship with the overall program management effort. The SEP should include the process and criteria for updating the document. The SEP is updated as needed to reflect technical progress achieved to date and to reflect changes in the technical approaches stemming from the findings and results of the technical reviews, program reviews, acquisition milestones, or other program decision points. The SEP is updated and submitted for Milestone Decision Authority (MDA) approval at each program milestone.  

The purpose of the SEP is to help program technical managers develop their systems engineering approach—providing a firm and well-documented technical foundation for the program. A rigorous technical planning process forces thoughtful consideration and debate, allows for integration and coordination of technical activities across all levels of management, and results in a sound systems engineering strategy commensurate with the program’s technical issues, life cycle phasing, and overall objectives.  

DoD Systems Engineering Plan (SEP) Preparation Guide

Addendum to SEP Preparation Guide v2, 2 July 2009


The Office of the Secretary of Defense (OSD) suggests that programs organize the SEP according to five critical focus areas: [1]
  1. Program Requirements: The SEP should define how the program will manage all requirements (statutory, regulatory, derived, certification).
  2. Technical Staffing and Organization Planning: The SEP should show how the program will structure and organize the program team to satisfy requirements.
  3. Technical Baseline Management: The SEP should establish a technical baselines approach.
  4. Technical Review Planning: The SEP should show how the program will manage the technical effort, including the technical baselines, through event-based technical reviews.
  5. Integration with Overall Management of the Program: The SEP should link SE to other management efforts, including the Acquisition Strategy, test planning, sustainment planning, Configuration Management, Risk Management, and life-cycle management.

Key documents that refer to the Systems Engineering Plan and should be coordinated with:


AcqTips:    
- The Systems Engineering Plan (SEP) is not a Systems Engineering Management Plan (SEMP).  The SEMP is developed to manage the development of a system by a contractor. Its written in response to a government SEP and provides unique insight as to the application of a contractor's standards, capability models, and toolsets to the development of a system.
- The SEP should be established early in the program definition stages and updated periodically as the program matures. Only by starting systems engineering processes early and monitoring them through the life cycle can programs effectively manage cost, schedule, and performance.
- Software planning in the Systems Engineering Plan

AcqLinks:
- DoD Instruction 5000.02 "Operation of the Defense Acquisition System" - 8 Dec 2008
- [1] DoD Systems Engineering Preparation Guide
- Addendum to SEP Preparation Guide v2, 2 July 2009
- Defense Acquisition Guidebook (DAG) – Chapter 8.5.1.2
- SE Plan Frequent Questions
- How to Prepare a SEP that Works
- Iterations in the Systems Engineering Process Guide, 14 Sept 2009
- Template: Systems Engineering Plan (SEP)
  

Click Here!

Sponsors

Click Here!