Strategic Views (StV) [Capability Views]
StV-3 Capability Phasing

StV-3 addresses the planned achievement of capability at different points in time or during specific periods of time, i.e. capability phasing.
Background:
StV-3 Views support the Capability Audit process and similar processes used across the different COIs by providing a method to identify gaps or duplication in capability provision.
The view indicates capability increments, which should be associated with delivery milestones within acquisition projects (when the increments are associated with capability deliveries).
Usage:
- Capability planning (capability phasing)
- Capability integration planning
- Capability gap analysis
Data objects:
The data in an StV-3 can include:
- Capability
- Capability Configuration
- Capability Increment (Project Milestone)
- Out of Service (Project Milestone)
- Enterprise Phase

Relationships Between Key Data Objects (Simplified from M3)
Representation:
- Tabulation
![]()
Detailed Product Description:
The Capability Phasing (StV-3) View provides a representation of the available military capability at different points in time or during specific periods of time (associated with the Enterprise Phases – see StV-1).
The StV-3 View is a tabular view consisting of rows representing Capabilities (derived from the Capability Taxonomy (StV-2) View) and columns representing Enterprise Phases (from StV-1). See the example below.
At each row-column intersection in the StV-3 table, the capability increment that represents the change in Capability within that Enteprise Phase is displayed. If the availability of the Capability spans multiple periods of time then this is indicated by an elongated colour-coded ‘bar’. If there are no Capabilities planned to satisfy the Capability Requirements in that period of time then a blank space will be left.

Example StV-3
The View is created by analysing programmatic project data to determine when projects providing elements of military capability are to be delivered, upgraded and/or withdrawn (this data may be provided in part by a Programme Timelines (AcV-2) View). Then capability increments identified are structured according to the required capabilities determined in the Capability Taxonomy (StV-2) View and the Enterprise Phases.
Alternatively a set of desired capability increments can be modelled and then compared to the programme plans. In practice, the construction of the view tends to iterate between considering the desired capability and considering what capability is planned to be delivered.
The output from this iterative approach is a tabular view that represents the required capability phasing.
However, there is a variant view in which the previous table is overlaid with the names of the projects that will deliver the capability increments. See example below.

Example StV-3 (Source: Sustainment Deskbook)
The essence of this variant view is the relationship between projects, capabilities and time. The view may be used to envisage the need for interventions in projects (to fulfil a capability gap) or to represent current plans (the availability of capability according to their delivery timescales). It provides a
An StV-3 View Product can be used to assist in the identification of capability gaps/shortfalls (no fielded capability to fulfil a particular capability function) or capability duplication/overlap (multiple fielded capabilities for a single capability function).
Page version 1.1, dated 4th April 2007