The CV-3 “Capability Phasing” addresses the planned achievement of capability at different points in time or during specific periods of time. The CV-3 supports the capability audit processes and similar processes used across the different COIs by providing a method to identify gaps or duplication in capability provision. The CV-3 indicates capability increments, which should be associated with delivery milestones within acquisition projects (when the increments are associated with capability deliveries).
The intended usage of the CV-3 includes:
- Capability planning (capability phasing).
- Capability integration planning.
- Capability gap analysis.
A CV-3 can be used to assist in the identification of capability gaps/shortfalls (no fielded capability to fulfill a particular capability function) or capability duplication/overlap (multiple fielded capabilities for a single capability function).
The CV-3 is populated by analyzing programmatic project data to determine when projects providing elements of capability are to be delivered, upgraded and/or withdrawn (this data may be provided in part by a PV-2 “Project Timelines” model). Then capability increments identified can be structured according to the required capabilities determined in the CV-2 “Capability Taxonomy” model and the phases. Alternatively, a set of desired capability increments can be viewed and then compared to the project plans. In practice, the population of the model tends to iterate between considering the desired capability and considering what capability is planned to be delivered. The output from this iterative approach can be a table that represents the required capability phasing.
The CV-3 can be presented as a table consisting of rows representing Capabilities (derived from the CV-2 Capability Taxonomy model) and columns representing phases (from CV-1 “Vision model”).
At each row-column intersection in the CV-3 table, the capability increment that represents the change in Capability within that phase can be displayed. If the availability of the Capability spans multiple periods of time, then this can be indicated by an elongated color coded bar. If there are no Capabilities planned to satisfy the Capability Requirements in that period of time then a blank space can be left.
A variant CV-3, in which the names of the projects that can deliver the capability increments are included, can identify capability gaps and shortfalls. The essence is the relationship between projects, capabilities and time. The model may be used to envisage the need for interventions in projects (to fulfill a capability gap) or to represent current plans (the availability of capability according to their delivery timescales).
- The DoDAF descriptions in this website are very generic and are mostly taken from the DoDAF Architecture Framework website. Make sure you visit the actual website for the most update information and a more thorough explanation of each viewpoint.
- DoDAF Version 1.0, although outdated, has some good examples on how to construct AV’s, OV’s, and SV’s.
AcqLinks and References:
-  DoDAF Architecture Framework Version 2.02
- DoD Architecture Framework Working Group Version 1.0, Volume 1: Definition and Guideline, 9 Feb 04 (Old Version)
- DoD Architecture Framework Version 1.0, Volume 2: Product Description, 9 Feb 04 (Old Version)
- Website: DoDAF Architecture Framework – DoD Deputy Chief Information Officer
- Website: DoDAF Version 2.02 Journal
- Website: DoDAF Meta Model (DM2)
- Website: DoD Information Enterprise Architecture
- Website: OMB Enterprise Architecture Assessment Framework (EAAF)