In this section you'll outline your overall approach for developing solutions that satisfy validated capability requirements and gaps. You'll also identify those interdependencies you need satisfied to provide a successful capability solution.

- Provide a summary of the overall program strategy for reaching FOC and if applicable, the relationship between increments defined in each incremental annex.

- Address those considerations such as needed technologies, other systems in the FoS or SoS, and inactivation of legacy systems relevant to your incremental delivery plan.

- For follow-on increments, provide an update on the acquisition status of previous increments.

- Discuss any program strategy updates that reflect knowledge gained from previous increments, changes in approved Service or Joint Concepts, changes to CONOPS, and changes to the solution architecture.

- Reminder: Like the other sections of a CDD, information here relies heavily on data provided by the PMO members of your CDD Development Team.

Briefly describe plans to use a Modular Open System Approach (MOSA). This includes any integration of capabilities developed within the system as well as any plan for evolution of capabilities added, removed, or replaced in future increments. Ensure this is in sync with the PM's MOSA strategy.

Define actions that constitute attainment of IOC and FOC of the current increment. Specify the target date for IOC and FOC based on discussions and coordination between the members of your team. Describe the types and quantities of required assets needed to attain IOC and FOC.

If your solution will integrate into one or more host platforms (such as munitions or radios), define the integration requirements and timing in the definitions of IOC and FOC. Do this rather than trying to define what the threshold and objective platform requirement are in Section 5.

- Consider defining multiple sets of IOC and FOC dates to identify "lead" and "following" integration platforms.

- If the warfighter needs all intended integration platforms on the same schedule, then identify a single set of IOC and FOC dates.

- If you need options for future integration on additional platforms not currently planned or resourced, then capture any integration limitations in Section 6.

Identify the operational units, including other DoD Components, government agencies, or allied & partner nations that will employ the capability solution. Define the required quantities for each organization. This information will leverage the DoDAF OV-4 generated during prior analysis.

- Provide a link to your updated OV-4

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