2.5. Document Body. The body of an IS-ICD differs from a regular ICD in two sections and shall be no more than 10 pages long including any content modified or augmented by a classified appendix, if used. See the regular ICD section for content of the unchanged sections.

2.5.1. Section 1: Operational Context. No change from a regular ICD to the operational context section in the IS-ICD.

For reference or comparison, below is what the JCIDS Manual says for the ICD 2021 itself:

2.5. Document Body.

2.5.1. The body of the ICD will have four Sections and will be no more than 10 pages long.

2.5.2. Section 1: Operational Context.

2.5.2.1. The purpose of this Section is to provide operational context for the capability identified in the ICD. This information explains how the capability, being concept based and threat informed, contributes to the missions and activities of the Joint Force.

{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.2.2. Describe the Range of Military Operations (ROMO) being addressed and the traceability to relevant parts of Unified Command Plan (UCP)-assigned missions, OPLANs/CONPLANs, supporting scenario products, Service and Joint Concepts, CONOPS, and/or other relevant factors to the capability identified in the ICD. If survivability and operations are required in, or after exposure to, CBRN environments (i.e., chemical, biological, radiological, contamination and/or initial nuclear effects, such as High-Altitude Electromagnetic Pulse (HEMP)), discuss how and where it fits in the operational context. Discuss the impact of a loss of the capability and if the loss would lead to critical mission failure.

2.5.2.3. Sponsors shall address Exportability "Allied/Partner Interoperability and Coalition Use" as per the Conventional Arms Transfer Policy in this Section of the CONOPS.

2.5.2.4. Identify the timeframe under consideration for IOC and FOC based on input from supported/supporting CCMDs and the acquisition community. The timeframes presented must be consistent with the DoDAF CV-3 and any phasing of capability proposed in Section 3 of the ICD.

2.5.2.5. Identify what measurable operational outcomes are required; what effects must be produced to achieve those outcomes; how they complement the integrated joint/multinational warfighting force; and what enabling capabilities are required to achieve the desired operational outcomes.

2.5.2.6. 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.

2.5.2.6.1. Narrative in the operational context Section must be consistent with the DoDAF OVs generated during prior analysis, as modified for the scope and purpose of the ICD. Required DoDAF views are listed in Appendix H to Enclosure B Figure B-28 and if the Net-Ready certification is applicable, additional views listed in Figure B-31.

2.5.2.6.2. Do not include other architecture data and associated artifacts/views in the document unless specifically needed for illustration purposes.