JCIDS Process

The Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 5123.01 “Charter Joint Requirements Oversight Council (JROC) and Implementation of the Joint Capabilities Integration and Development System (JCIDS)” implements the JROC as a statutory council to the Chairman of the Joint Chiefs of Staff (CJCS), and delineates the roles and responsibilities of the JROC, its […]

Note: The Manual for the Operations of the Joint Capabilities Integration and Development System (JCIDS) has been replaced by CJCSI 5123.01H. Note: The new Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 5123.01H “Charter Joint Requirements Oversight Council (JROC) and Implementation of the Joint Capabilities Integration and Development System (JCIDS)” replaces the CJCSI 31070.01.  

The System Functional Review (SFR) is a technical review to ensure that the system’s functional baseline is established and can satisfy the requirements of the Initial Capabilities Document (ICD) or draft Capability Development Document (CDD) within the currently allocated budget and schedule. It also determines whether the system’s lower-level performance requirements are fully defined and

  Joint Operations Concepts (JOpsC) is a family of joint future concepts consisting of a Capstone Concept for Joint Operations (CCJO), Joint Operating Concepts (JOC), Joint Functional Concepts (JFC), and Joint Integrating Concepts (JIC). The objective of JOpsC is to guide the transformation of the joint force so that it is prepared to operate successfully

The Joint Staff (JS) Deputy Director for Requirements (J-8) serves as the JCIDS Gatekeeper for the Joint Capabilities Integration and Development System (JCIDS) Process and maintains a studies repository to facilitate visibility into studies related to capability requirements and the generation of JCIDS documents. Sponsors provide the results of any studies or analyses intended to

The 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

A System Requirements Review (SRR) is a formal review conducted to ensure that system requirements have been completely and properly identified and that a mutual understanding exists between the government and the contractor. It ensures that the system under review can proceed into initial systems development and that all system and performance requirements derived from

The Sustainment Key Performance Parameter (KPP) is mandatory for all systems and is designed to enhance system life-cycle management. The attributes for the Sustainment KPP are identified in the Capability Development Document (CDD) and Capability Production Document (CPD) and apply to all pre-Milestone C programs. Manual: JCIDS Manual of Operations –  Sustainment KPP Guide outlined in

The Survivability Key Performance Parameter (KPP) is mandatory for all manned systems and is designed to enhance personnel survivability in an asymmetric threat environment. The attributes for the Survivability KPP are identified in the Capability Development Document (CDD) and Capability Production Document (CPD) and apply to all pre-Milestone C programs. Manual:  JCIDS Manual for the

  Members of the Armed Forces and employees of the Department of Defense (DoD) with authority to generate capability requirements for Major Defense Acquisition Programs (MDAP) may not participate in the requirements generation process unless the member or employee successfully completes a certification training program. [2]   Personnel have varying degrees of responsibility within the

  Figure: JCIDS Requirements Sequencing [1] 1. The Initial Capabilities Document (ICD) is the most common starting point for new capability requirements.[1] Once validated, the ICD typically leads to an Analysis of Alternatives (AoA) and then the Capability Development Document (CDD) and Capability Production Document (CPD) for development of a materiel capability solution. An ICD

A Post-Implementation Review (PIR) verifies the Measures of Effectiveness (MOEs) of the Initial Capabilities Document (ICD) or the benefits of a business plan. The PIR is a sequence of activities and reviews that when combined, provide the necessary information to determine the degree to which a materiel investment operating in its intended environment meets the

A non-materiel solution is a resolution to an identified need that doesn’t require a material solution or a system to be developed. The non-materiel solution can be developed from Doctrine, Organization, Training, Leadership and Education, Personnel, Facilities and Policy (DOTMLPF-P) analysis that is derived from a Functional Solutions Analysis (FSA) in the Capabilities Bases Assessment (CBA).

The Net-Ready Key Performance Parameter (NR-KPP) assesses the net-ready attributes required for both the technical exchange of information and the end-to-end operational effectiveness of that exchange. It evaluates information needs, information timeliness, Information Assurance (IA), and net-ready attributes. Its requirements are summarized in the NR-KPP Checklist. Net-Ready Key Performance Parameter (NR-KPP) References Guidebook: Navy Net-Ready

A Military Utility Assessment (MUA) is an assessment of the operational utility of a system.  It’s completed at the end of a Joint Capability Technology Demonstration (JCTD) and may be a suitable replacement for the required analysis used in a Initial Capability Document (ICD). MUAs that do not contain the critical elements of information presented

Key Interface Profiles (KIP) are the technical specifications that allow access to the Global Information Grid (GIG). Systems need to conform to various KIPs based on desired functionality so they can interface properly with the GIG. KIPs are listed in CJCSI 6212.01E and are divided into three families: Transport Family – covers SATCOM at various

Joint prioritization of capability requirements addresses statutory responsibilities of the Joint Requirements Oversight Committee (JROC) and the Command of Joint Chief of Staff (CJCS). In addition to satisfying statutory responsibilities, Joint prioritization within Joint Capability Area (JCA) portfolios provides context for decision-makers across the Department. [1] Each Functional Capabilities Board (FCB) will establish Joint priorities

The Joint Requirements Oversight Council (JROC) charters and oversees the work in developing overarching joint operational and integrating concepts for joint missions during the joint concept development component of the JCIDS Process. The JROC reviews and approves all joint capabilities documents designated as JROC interest and supports the acquisition review process. The JROC validates capability

Update: The JCD has been eliminated, and the functions of the document have been incorporated into the Initial Capabilities Document (ICD).  JCDs developed under a previous version of CJCSI 3170.01 are still accepted per the guidance in Enclosure B. The Joint Capabilities Document (JCD) is a requirements document that was developed to capture a set

Functional Capabilities Board (FCB) The responsibilities of the FCB include ensuring that DOTMLPF Change Recommendations (DCR) and policy aspects of new capabilities are being appropriately considered in the JCIDS documents, evaluate the Key Performance Parameters (KPP) submitted by the sponsor, identify other potential KPPs, ensure leadership organization participates in the JCIDS process, assist with comments

  The Joint Capabilities Board (JCB) assists the Joint Requirements Oversight Council (JROC) in carrying out its duties and responsibilities. The JCB reviews and, if appropriate, endorses all Joint Capabilities Integration and Development System (JCIDS and Doctrine, Organization, Training, Materiel, Leadership, Personnel, Facilities and Policy (DOTMLPF-P) Change Recommendation (DCR) documents prior to their submission to

See JCIDS Manual JCIDS Manual for the Operations of the JCIDS Process, Page 3 for a clearer view Figure: Overview of JCIDS Process [1]   AcqLinks and References: [1] JCIDS Manual for the Operations of the JCIDS Process, Page 3 Updated: 8/4/2021

The Joint Staff (JS) Deputy Director for Requirements (J-8) serves as the Gatekeeper for the Joint Capabilities Integration and Development System (JCIDS) Process. This individual makes the initial joint potential designation of JCIDS documents and determines lead and supporting Functional Capabilities Boards (FCB) for capability documents. The Gatekeeper is supported in these functions by FCB