18. Capstone Requirements

a. Capstone Requirements provide top-down unified and overarching guidance to the Joint Force to align and enable continuous modernization and integration of bottom-up developed capabilities. Capstone Requirements identify the Joint Force needs, but do not prescribe how to execute the supporting capability development. Capstone Requirements provide capability developers a unified, joint perspective to focus resources and efforts. Capstone Requirements capture JCRs and prioritize them within a portfolio for iterative analysis under the DoW’s CPM process.

b. Identification and Sponsorship. Capstone Requirements may be submitted by any Service or component. However, requirements sponsors that wish to develop a CRD must first provide justification to the JCB via general officer/flag officer/senior executive service (GO/FO/SES) memo. The memo should identify alignment to joint concept or joint operational problem, key stakeholders, JCAs, a tentative timeline for CRD development, and expected outcomes. The JCB reviews and accepts the memo and the assigned FCB provides coordination support to the sponsor.

c. Development and Approval. Upon acceptance by the JCB and assignment of an FCB coordinator, the CRD sponsor co-develops the Capstone Document with all key stakeholders and SMEs across the Services and components. The stakeholder community includes concept writers, capability developers, acquisition SMEs, and requirements SMEs. The FCB coordinator assists the sponsor with facilitating document development activities and expediting staffing and commenting actions. Capstone Requirements will be approved through the JROC and distributed for use.

d. Implementation. Capstone Requirements provide a shared understanding of warfighter needs through a “mission command” approach to requirements— defining high-level, enduring Capabilities Required, as well as supporting capabilities that encompass “needed effects” and “enabling capabilities.” Approved Capstone Requirements are foundational to cross-portfolio analysis—including, but not limited to, JFD, JCI, and CPM—and transparency to close high-risk gaps and inform leader resource decisions. The FCB will continuously review the CRD’s portfolio of JCRs for changes, including changes driven by the threats, capability development, and programs and technologies status changes.

e. WAS stakeholders can leverage Capstone Requirements to accelerate Service/component requirements processes and pursue all available acquisition pathways and efforts to support the needs of warfighters. This approach supports agile capability development sprints and iterative fielding, providing real-time visibility of where to prioritize resourcing and technology investments for both urgent/emerging needs and long-term modernization.

f. Capstone Requirement JCRs guide experimentation and exercises objectives to provide for better informed assessments of capability solution performance, gap closure, and residual risk. Capstone Requirements can also support resource decision making in the PPBE process by providing for robust traceability between the missions, requirements, and capability solutions supported by DoW resources.

g. See Joint Requirements Documents for document format information.

From Enclsoure B of the JFRP Manual:

a. Capstone Requirements Documents. Capstone Requirements provide top-down unified and overarching guidance to the Joint Force to align and enable continuous modernization and integration of bottom-up developed capabilities. Capstone Requirements identify the Joint Force needs, but do not prescribe how to execute the supporting capability development. Capstone Requirements provide capability developers a unified, joint perspective to focus resources and efforts. Capstone Requirements capture JCRs and prioritize them within a portfolio for iterative analysis under the DoW’s CPM process.

3. Joint Force Requirements Documents Formats

a. JFR documents will contain the following information:

(1) Cover Page. Required for all, with additional details for CDR.

(2) Executive Summary. Required for all.

(3) Section 1: Operational Context. Required for all, with additional details for CDR.

(4) Section 2: Threat Summary. Required for all, with additional details for CDR.

(5) Section 3: Joint Capability Requirements and Gaps. Required for all, with additional details for CDR and JDCR.

(6) Section 4: Interoperability. Required for CRD and CDR. Not applicable for JDCR.

(7) Section 5: Final Recommendations/Implementation Plans. Required for all, with additional details for JDCR.