Category Archives: Roadmap

Lr – Lines of Development

NAF v3: NPV-2 MODAF: AcV-2

TaxonomyStructureConnectivityProcessesStatesSequencesInformationConstraintsRoadmap
Logical
Specifications
L1
Node Types
NAV-2
AV-2
L2
Logical Scenario
NOV-2
OV-2
L3
Node Interactions
NOV-2, NOV-3
OV-2,OV-3
L4
Logical Activities
NOV-5
OV-5
L5
Logical States
NOV-6b
OV-6b
L6
Logical Sequence
NOV-6c
OV-6c
L7
Logical Data Model
NSV-11a
OV-7
L8
Logical Constraints
NOV-6a
OV-6a
Lr
Lines of Development
NPV-2
AcV-2

The Lr view specifies the logical threads (lines of development) for a set of projects and programmes. The status of each of these threads can be shown at the various milestones in the projects or programmes.

Background

The Lr view is primarily intended to support the acquisition process across multiple projects or programmes, including the management of dependencies between projects and the integration of all the DLODs to achieve a successfully integrated military capability.

Use of the Lr view should support the management of capability delivery and be aligned with Cr Capability Phasing view.

Usage

  • Project management and control (including delivery timescales).
  • Project dependencies and the identification of associated risk.
  • Portfolio management
  • Through Life Management Planning (TLMP).

Representation

Detailed View Description

Key Elements and Their Relationships

lr-hlmm

Meta-Model

The detailed meta-model for Lr can be viewed here

Ar – Architecture Roadmap

NAF v3: NAV-1 MODAF: AV-1

The Ar Architecture Roadmap view specifies the project plan for the architecture, the key approval milestones and the roles and responsibilities.

Background

Usage

Representation

Detailed View Description

Key Elements and Their Relationships

Meta-Model

ap-meta-model

Pr – Configuration Management

NAF v3: NSV-8 MODAF: SV-8

TaxonomyStructureConnectivityProcessesStatesSequencesInformationConstraintsRoadmap
L4-P4 (NSV-5)
Physical
Resource
Specifications
P1
Resource Types
NAV-2, NSV-2a,7,9,12
AV-2, SV-2a,7,9,12
P2
Resource Structure
NOV-4,NSV-1
OV-4, SV-1
P3
Resource Connectivity
NSV-2, NSV-6
SV-2, SV-6
P4
Resource Functions
NSV-4
SV-4
P5
Resource States
NSV-10b
SV-10b
P6
Resource Sequence
NSV-10c
SV-10c
P7
Physical Data Model
NSV-11b
SV-11
P8
Resource Constraints
NSV-10a
SV-10a
Pr
Configuration Management
NSV-8
SV-8

The Pr Configuration Management view depicts the whole lifecycle view of a Resource, describing how its configuration changes over time.

Background

The Pr view provides an overview of how a capability configuration structure changes over time. It shows the structure of different versions of Resources (usually Capability Configurations or Service Implementations) mapped against a timeline.

Usage

  • Development of incremental acquisition strategy.
  • Planning technology insertion.

Representation

Detailed View Description

Key Elements and Their Relationships

pr-hlmm

Meta-Model

The detailed meta-model for Pr can be viewed here

Dr – Deployment Schedule

NAF v3: NCV-5 MODAF: StV-5

TaxonomyStructureConnectivityProcessesStatesSequencesInformationConstraintsRoadmap
Deployed
Resources
D1
Master Data
NAV-2
AV-2
D2
Deployed Resources
NOV-4
OV-4
Dr
Deployment Schedule
NCV-5
StV-5

A Dp Deployment Schedule addresses the roll-out of resource packages (new capabilities, organisational change, etc.) into individual organisations.

Background

The Dr shows the planned capability deployment into individual organisations for a set of Enterprise Phases. Each Enterprise Phase snapshot lists the Organisations and the Resource Package that it is planned to receive. Each Resource Package may be traced to the Capability it delivers. The Dp View may also specify the possible interactions between the deployed Capability so that planners can see at a glance which organisations have compatible systems, and when.

Usage

  • Fielding planning.
  • Business change planning.
  • Capability integration planning.
  • Capability options analysis.
  • Capability redundancy/overlap/gap analysis.
  • Identification of deployment level shortfalls.

Representation

Detailed View Description

Key Elements and Their Relationships

Meta-Model

Dr - meta-model

Sr – Service Roadmap

No equivalent NAF 3.1 or MODAF view

TaxonomyStructureConnectivityProcessesStatesSequencesInformationConstraintsRoadmap
C1-S1 (NSOV-3)
Service
Specifications
S1
Service Taxonomy
NAV-2, NSOV-1
AV-2, SOV-1
S3
Service Interfaces
NSOV-2
SOV-2
S4
Service Functions
NSOV-3
SOV-5
S5
Service States
NSOV-4b
SOV-4b
S6
Service Interactions
NSOV-4c
SOV-4c
S7
Service I/F Parameters
NSOV-2
SOV-2
S8
Service Policy
NSOV-4a
SOV-4a
Sr
Service Roadmap

The purpose of Sr is to show versions (and version history with dates) of Service Specifications.

Background

Usage

Representation

Detailed View Description

Key Elements and Their Relationships

sr-hlmm

  • Service Specification
  • Project Milestone
  • Service Level
  • Service Specification Version Succession (relationship)

Meta-Model

The detailed meta-model for Sr can be viewed here

Cr – Capability Roadmap

NAF v3: NCV-3 MODAF: StV-3

TaxonomyStructureConnectivityProcessesStatesSequencesInformationConstraintsRoadmap
ConceptsC1
Capability Taxonomy
NAV-2, NCV-2
AV-2, StV-2
C2
Enterprise Vision
NCV-1
StV-1
C3
Capability Dependencies
NCV-4
StV-4
C4
Standard Processes
NCV-6
StV-6
C5
Effects
C7
Performance Parameters
NCV-1
StV-1
C8
Planning Assumptions
Cr
Capability Roadmap
NCV-3
StV-3

The Cr provides a representation of the actual or estimated availability of capabilities over a period of time (derived from capability delivery milestones in acquisition projects).

Background

Cr Views support the Capability Audit process and similar processes used across different communities of interest by providing a method to identify gaps or duplication in capability provision.

The view indicates capability increments, which are derived from delivery milestones within acquisition projects.

Usage

  • Capability planning (capability phasing).
  • Capability integration planning.
  • Capability gap analysis.
  • High-level dashboard for acquisition management.

Representation

Cr is usually shown as a timeline with rows for each capability. The timescale is measured horizontally. Resources that provide those capabilities are shown as bars within the rows. The width of the bar depends on the service life of the resources.

Detailed View Description

The Cr provides a representation of the available capability levels at different points in time or during specific periods of time (associated with the Enterprise Phases – see C2).

The Cr view is presented as a timing chart showing capabilities on the vertical axis and time on the horizontal axis. Active capability configurations are shown as bars against the capabilities they provide, with the start and end of the bars corresponding to the capability configuration coming into and going out of service. Where nothing meets a particular capability at a particular time, whitespace is shown so as to highlight capability gaps.

cr-example-1

The view is created by analysing project data to determine when projects acquiring resources that provide military capability are to be delivered, upgraded and/or withdrawn (this data may be provided in part by a Lines of Development View (Lr), and the mappings from capability to resources that is provided in P2 and Pr).

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 table is overlaid with the names of the projects that will deliver the capability increments:

cr-example-2

 

The essence of this variant view is the relationship between projects, capabilities and time (normally, an StV-3 will hide the project). The view may be used to determine 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).

A Cr can be used to assist in the identification of capability gaps/shortfalls (no capability configurations that fulfil a particular capability) or capability duplication/overlap (multiple fielded capabilities for a single capability function).

Note that C2 specifies the requirement for capability at each Enterprise Phase, whereas Cr reflects the output of capability programmes (e.g. acquisition, training, etc.) over time. The requirement specified in C2 may or may not be met by those programmes. 

Key Elements and Their Relationships

cr-hlmm

  • Capability
  • Resource Package
  • Capability Configuration
  • Project
  • Project Milestone

Meta-Model

The detailed meta-model for Cr can be viewed here