2.5.1.13. Section 13: Program Cost. Follows the same format as a regular CDD with the exception of the following:

2.5.1.13.1. In place of the required resources table used in a CDD, identify the programmed funding by year for the software development and sustainment and for hardware refresh and integration, as shown in Figure B-18. Provide rationale for the level of funding required in the same manner as for a CDD.

2.5.1.13.2. Cite applicable lifecycle cost analyses, conducted IAW Reference [51], including other cost models that may include other U.S. Government agency/department or exportable-based business cases to reduce DoD lifecycle costs. Ensure that resource estimates have been reviewed by the Sponsor’s cost analysis organization to ensure best practices are being followed. Ensure that any final reports or other results documentation is uploaded into KM/DS for reference purposes.

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

2.5.13.5. In a similar manner to what is required by References [5], [52], and [53], describe how the resources outlined in Figure B-14 are affordable under the limitations of the Component’s expected Total Obligation Authority (TOA) over a 30-year timeframe, including identification of legacy capabilities which will be reduced in scope or eliminated to allow funding of the proposed new capability. The 30-year "sand chart" data will be generated using the same OSD inflator values used to comply with affordability in Reference [5], and will be provided within the CDD or as supplemental data uploaded to the KM/DS system.