View NAF:NPV-2 Programme to Capability Mapping Subview

NATO_logo.gif

Overview

The NPV-2 Programme to Capability Mapping subview is part of the NATO Programme View and one of the 49 NATO Architecture Framework subviews*.

Version & Date

Version 3.1

* =  changed at 3.1

+ =  new at 3.1

The change history is derived from the definition of each NATO Architecture view within section 5.2.8 NATO Programme View (NPV) in AC/322(SC/1-WG/1)N(2009)0005-ADD2.  NATO Architecture Framework Version 3.1 document from http://www.nhqc3s.nato.int/Browser.asp?Target=_docs/NAF_v3_1 .

See NAF Release History.

Purpose

From the NATO Architecture Framework v3, CHAPTER 4, Section 4.9.2

The Programme to Capability Mapping (NPV-2) subview is intended primarily to support the acquisition and fielding processes, including the management of dependencies between projects and the integration of all relevant project and programme elements to achieve a capability as defined by in NATO capability package (CP).

Covered by NATO release conditions.

Definition

From the NATO Architecture Framework v3, CHAPTER 4, Section 4.9.2

The NPV-2 maps programmes and projects to capabilities to show how the specific projects and programme elements help to achieve a NATO capability, as defined in a CP. Projects are mapped to the capability for a particular timeframe or epoch. Projects may contribute to multiple capabilities and may mature across epochs. This subview analysis can be used to identify capability redundancies and shortfalls, highlight programme phasing issues, expose organisational or system interoperability problems, and support programme decisions, such as when to phase out a legacy system.

Covered by NATO release conditions.

Data Objects

From the NATO Architecture Framework v3.1, CHAPTER 5, Section 5.2.8.2

The data in an NPV-2 can include:

Covered by NATO release conditions.

From The MODAF Acquisition (AcV) Viewpoint p4:

MODAF_AcV-2_simplified.jpg

Subject to Crown Copyright

This diagram is taken from MODAF 1.2.004 MODAF::AcV-2 Programme Timelines View as it is identical to that in NAF 3.1 with the following substitutions for view/subview number:

Presentation

Configuration History

Comments

This subview looks to have the same purpose as the MODAF AcV-02 which shows dependencies between Projects. If so, then Capability itself is not shown(it isn’t identified as being needed in the list of stereotypes) and the name is confusing as the NCV-3 Capability Phasing Subview shows capability phasing and shortfalls. Simply mapping to a Capability Configuration is insufficient as a Capability might be supported by many Capability Configurations. The name and intent of the view is therefore inconsistent with the definition.

It is also poorly defined since if it is there is no sense of the focus being on the effect of time on the deployment/removal of Capability Configurations which leads to the effects on Capability. This is normally shown using a Gantt chart and yet the focus is on capabilities and not time dependencies between projects.

References

Other Frameworks

See also:

 

 


Category:Framework -> View
Category:NAF -> Subview
Category:Procurement
Category:Acquisition
Category:Programme

Categories:

 

© 2010 Eclectica Systems Ltd.