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-16, 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.

2.5.1.4.2.1. The IT Box model uses initial minimum values in place of initial objective values so that the baseline capability is clearly specified, and the delegated oversight body has flexibility to further develop capabilities without revalidation of the JCIDS document.

2.5.1.4.2.2. Initial minimum values represent the achievable level of required capability needed to incorporate current technology to meet the baseline capability.

2.5.1.4.2.3. Successor documents must be provided to the KM/DS system for information purposes and visibility in the capability portfolios.

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

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 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 CDD (Section 6).