2.5. Document Body.

2.5.1. The body of the Joint DCR shall have the following 5 sections, and shall be no more than 30 pages long. In cases where a limited amount of content is classified at a higher level than the document, an appendix classified at a higher level than the base document may be used to facilitate greater access to the document.

2.5.1.1. Section 1: Operational Context.

2.5.1.1.1. The purpose of this section is to provide the operational context and conceptual basis for the recommendations addressed by the Joint DCR. This information facilitates the review and validation of the Joint DCR from the standpoint of how the recommendations address or enable solutions to validated requirements and contribute to the missions and activities of the joint force.

2.5.1.1.1.1. Narrative in the operational context section is to be consistent with DoDAF OVs generated during prior analysis, as modified for the scope and purpose of the Joint DCR, including the DoDAF OV-1, OV-2, OV-4, and OV-5a.

2.5.1.1.1.2. Include the DoDAF OV-1 in this section and, where applicable, ensure high-level intelligence system connectivity and interoperability are accurately and adequately illustrated in the DoDAF OV-1. Do not include other architecture data and associated artifacts/views in the document unless specifically needed for illustration purposes in the body of the Joint DCR. Provide data for the remainder of the required DoDAF OVs in the repository located at the URL specified in the reference section of the document.

{NOTE: The term Range of Military Operations (ROMO) has been removed from Joint terminology and replaced with the term Competition Continuum. For more information and context, refer to the ‘Other Joint Documents’ folder under “Show Help” and “View Documents.” The term ROMO remains in the citation below to remain faithful to the authoritative document.”}

2.5.1.1.2. Describe the ROMO being addressed and the traceability to relevant parts of the UCP assigned mission, OPLANs/CONPLANs, SSA products. Service and Joint Concepts, CONOPS, and/or other relevant factors to the capability requirements identified in the DCR.

2.5.1.1.3. Address interoperability as how it may apply to the DCR.

2.5.1.1.4. Address Exportability “Allied/Partner Interoperability and Coalition Use” as per the Conventional Arms Transfer Policy.

2.5.1.1.5. If the Joint DCR is a successor document to one or more validated JCIDS documents:

2.5.1.1.5.1. Cite the validated source document(s) that identified the capability requirements addressed or enabled by the Joint DCR and ensure that any source documents not already present in the KM/DS system are provided to the Joint Staff Gatekeeper for reference purposes.

2.5.1.1.5.2. From the source document(s), summarize the operational context associated with the validated requirements addressed or enabled by the Joint DCR. Ensure any changes to the operational context that have occurred since validation of the requirements are addressed. If any changes to the operational context have been made, ensure the DoDAF OVs submitted with the ICD are updated and resubmitted to reflect the applicable changes.

2.5.1.1.5.3. For Joint DCRs with impact on intelligence equities, ensure any key intelligence support capabilities affected by the changes to DOTmLPF-P are addressed within the operational context.

2.5.1.1.6. If the Joint DCR is not based on a validated JCIDS document, provide the operational context as outlined for Section 1 of an ICD. If applicable, ensure this section includes reference to relevant JROCMs, CCMD Integrated Priority List (IPL)s, joint monthly readiness reviews, quarterly reports to the SecDef, etc., that relate to the change recommendations.