2.5.1.4. Section 4: Program Summary. Same as the regular CDD with the addition to the following:

2.5.1.4.1. Development of the IT Box.

2.5.1.4.2. The "IT Box" construct, Figure B-12, calls for fewer iterations of validating JCIDS documents through the JCIDS process by describing the overall IS program and delegating validation of detailed follow-on requirement and solution oversight to a flag-level organization other than the JROC or JCB.

For reference or comparison, below is what the JCIDS Manual says for the DCR 2025 itself:

2.5.4. Section 4: Program Summary.

2.5.4.1. The purpose of this Section is to outline the overall approach for developing capability solutions to satisfy validated requirements and associated capability gaps and to identify related interdependencies that must be satisfied to provide a successful capability solution.

2.5.4.2. Provide a summary of the overall program strategy for reaching FOC and, if applicable, the relationship between increments defined in the IS-CDD. Carefully address the considerations (e.g., technologies to be developed, other systems in the FoS or SoS, inactivation of legacy systems) relevant to the incremental delivery plan. For follow-on increments, provide an update on the acquisition status of previous increments. Discuss any updates to the program strategy to reflect knowledge gained from previous increments, changes in approved Service or Joint Concepts, changes to CONOPS, or changes to the solution architecture or the DoD Information Enterprise Architecture (IEA).

2.5.4.3. Describe the modular open system approach (MOSA) that will be used/implemented in program capabilities development and acquisition weapon system design in accordance with program or enterprise level MOSA objectives. Briefly describe the system being designed plans to use a MOSA, including integration of capabilities developed within the system and/or plan for evolution of capabilities that will be added, removed, or replaced in future increments, as well as how the program defines its modules and modular system interfaces per Title 10 U.S. Code Section 4401. The use of MOSA will enhance interoperability, competition, commonality, enable technology insertion, and reduce the cost of future engineering upgrades.

2.5.4.4. Define what actions will constitute attainment of IOC and FOC of the current increment. Specify the target date for IOC and FOC attainment based on discussions and coordination between the Requirement Sponsor and the acquisition community. Describe the types and quantities of required assets needed to attain IOC and FOC.

2.5.4.4.1. If the capability solution is intended to be integrated into one or more host platforms (such as for munitions or radios), then Sponsors should define the integration requirements and timing in the definitions of IOC and FOC in this Section. This is the preferred approach rather than trying to define what the threshold and objective platform requirement is in Section 5 of the IS-CDD.

2.5.4.4.1.1. Multiple sets of IOC and FOC dates may be defined to identify "lead" and "following" integration platforms.

2.5.4.4.1.2. If all intended integration platforms need to be available to the warfighter on the same schedule, then the Sponsor should identify a single set of IOC and FOC dates.

2.5.4.4.1.3. If the Sponsor would like to preserve the option for future integration on additional platforms not currently planned or resourced, then the Sponsor should capture any integration limitations in the Other System Attributes Section of the IS-CDD (Section 6).

2.5.4.4.2. Identify the operational units, including other DoD Components, government agencies, or allied/partner nations that will employ the capability solution, and define the required quantities for each organization. This information will leverage and be consistent with the DoDAF OV-4 generated during prior analysis and will be updated for the scope and purpose of the IS-CDD.

2.5.4.4.3. Total quantities must include the operational inventory as well as required quantities for training, spares, scheduled repair, and anticipated attrition over the lifecycle. Initial production planning should be based on these quantities, and changes to it may trigger a JROC/JCB Tripwire review IAW Enclosure A of this manual.