Skip to main content

Capability Requirement (CR) Documents

The Joint Capabilities Integration and Development System (JCIDS) serves as the foundation for articulating and validating military capability requirements through three key documents: the Initial Capabilities Document (ICD), the Capability Development Document (CDD), and DOTmLPF-P Change Recommendations (DCR). Together, these documents outline the lifecycle of a capability solution, from identifying and addressing critical capability gaps to guiding the development and production of materiel and non-materiel solutions.

While the ICD, CDD, and DCRs represent *validated capability requirement documents, it is critical to emphasize that certain other documents and sources, while valuable and informative, are not validated capability requirement documents. These sources may provide essential context or support for the capability development process, but they do not substitute for the rigorous validation required under the JCIDS process.

It is also important to note that validated Joint Emergent Operational Needs (JEONs), Joint Urgent Operational Needs (JUONs), and Service-specific Urgent Operational Needs (UONs), such as the USMC Urgent Universal Need Statement (U-UNS), can represent capability requirements only after they have been validated by the appropriate authority. Refer to [[Urgent Needs Process & D-UNS]] for additional guidance on the validation process.

Examples of documents and sources that are not validated capability requirements include:

  • Integrated Priority Lists (IPL) from Combatant Commands (COCOMs), U.S. Fleet Forces Command (USFF), or Type Commands (TYCOMs).
  • Inputs from Platform and Enabling Naval Aviation Requirements Groups (NARG).
  • Program Manager (PM) inputs for issue sheets or requirements documentation.
  • Requests or inputs from other OPNAV directorates addressing seam issues.
  • Requirements memos or requests for new capabilities from OSD, Navy, or USMC Stakeholders.
  • N81 Campaign Analysis or mission area assessment cards (capability cards).
  • Engineering Change Proposals (ECP), which, as noted in the NAVAIR ECP Checklist, are based on previously validated requirements ("Big R" or "little R").

These examples, while useful for identifying operational needs or priorities, do not constitute validated capability requirements as defined by the JCIDS process.

Initial Capabilities Document (ICD)​

The Initial Capabilities Document (ICD) identifies joint military capability requirements and associated capability gaps that pose unacceptable operational risks if unaddressed. It recommends solutions to mitigate these gaps, which may include materiel, non-materiel, or combined approaches. A validated ICD is required for the Materiel Development Decision (MDD) and provides foundational input for the Analysis of Alternatives (AoA) and Milestone A decision in the Defense Acquisition Process. The ICD quantifies capability gaps by functional area, range of military operations, and timeframe, while summarizing capability analysis and maintaining traceability to operational contexts, threats, and other critical factors. Once approved, the ICD is not updated. Its format is detailed in the JCIDS Manual.

Capability Development Document (CDD)​

The Capability Development Document (CDD), including Information System (IS-CDD) and Software (SW-CDD) variants, outlines developmental Key Performance Parameters (KPPs), Key System Attributes (KSAs), and Additional Performance Attributes (APAs) to support the creation of materiel capability solutions that address validated capability gaps. Each increment in an evolutionary acquisition program requires a CDD or CDD annex, providing measurable and testable capabilities to guide development through the Technology Maturation and Risk Reduction (TMRR) and Engineering and Manufacturing Development (EMD) phases.

The CDD traces its foundation to predecessor documents like the Initial Capabilities Document ([[ICD]]) and includes life-cycle cost considerations while identifying [[DOTmLPF-P]] impacts. A sponsor-approved draft [[CDD]] is required for Milestone A and TMRR RFP releases, while a validated CDD is necessary for Development RFP and Milestone B decisions. The IS and SW variants streamline requirements for IT and software programs, emphasizing cost, schedule, performance, and flexibility for rapid incorporation of evolving technologies, while avoiding unique hardware development. These variants can leverage the "IT Box" concept to delegate detailed capability delivery to oversight bodies, ensuring agile responses to technological changes.

DOTmLPF-P Change Recommendation (DCR)​

A DCR proposes non-materiel capability solutions as an alternative to, or complement of, materiel capability solutions. DCRs are not required by JCIDS when non-materiel solutions impact only the sponsor organization. In this case, usage of a DCR is at the discretion of the Service, [[CCMD]], or other DoD Component.

The DCR process is the method DoD mitigates capability gaps using non-materiel approaches.

Doctrine​

Evaluates current combat strategies and methodologies to identify areas for improvement or adaptation, ensuring alignment with evolving operational requirements.

Organization​

Assesses the structure and composition of military units and commands to optimize effectiveness and efficiency in mission execution.

Training​

Examines existing training programs to ensure they adequately prepare personnel for current and future operational challenges.

materiel​

This aspect is intentionally in lowercase due to being frequently misunderstood. In regards to DOTmLPF-P, materiel refers to the quantities and relative allocations of equipment to units.

Leadership and education​

Focuses on the development and education of leaders at all levels to ensure they possess the necessary skills and knowledge for effective command.

Personnel​

Evaluates the availability and readiness of qualified individuals to meet operational demands across various scenarios.

Facilities​

Assesses the adequacy and condition of physical infrastructure, including installations and industrial facilities, to support operational requirements.

Policy​

Common approaches and procedures

JUON, JEON, and Service UON​

A Joint Urgent Operational Need (JUON), Joint Emergent Operational Need (JEON) or DoD Component Urgent Operational Need (UON) specifies capability requirements driven by ongoing or anticipated contingency operations, which if left unfulfilled, would result in capability gaps leading to unacceptable loss of life or critical mission failure.

See Urgent Needs Process & D-UNS.

References​

  1. OPNAV N9IJ Requirements Processes Overview
  2. Capability Development Document (CDD) | www.dau.edu
  3. Initial Capabilities Document (ICD) | www.dau.edu
  4. DOTmLPF-P Change Recommendation (DCR) | www.dau.edu