2.5.4. Section 4: Final Recommendations. Same as the regular ICD with the addition of th e “IT Box.” D iscussion in this section should be tailored to the IS solution and focus on how the Sponsor intends to develop and deliver the required capabilities detailed above.

2.5.4.1. The “IT Box” construct, Figure B-3, 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.4.1.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.4.1.2. Initial minimum values represent the achievable level of required capability needed to incorporate current technology to meet the baseline capability.

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

2.5.4.2. Inclusion of lifecycle costs for the program. Break out costs into annual estimates of development and integration as well as sustainment costs as shown in Figure B-4. While detailed cost of software development is unknown, cost estimates should be created in accordance with Reference [51] and should be updated throughout the development process.

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

2.5.5.1. The purpose of this section is to identify one or more paths forward to satisfy the CRs and close or mitigate associated capability gaps identified in the document. Ensure recommendations reflect a thorough understanding of the threat considerations, intelligence support requirements, and capabilities for the functional and operational areas.