TRAK-Community

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.3 NATO Capability Views (NCV) 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.

Overview

The NATO Capability View is one of the 7 NATO Architecture Framework Views.

NATO Architecture Framework v3, CHAPTER 1:

The NATO Capability View (NCV) supports the process of analyzing and optimizing the delivery of military capabilities in line with NATO’s strategic intent. The NCV achieves this by capturing essential elements of NATO’s strategic vision and concepts and NATO’s capability planning process, and decomposing this data into a capability taxonomy. The taxonomy is augmented with schedule data and measures of effectiveness to enable the analysis of capability gaps and overlaps. The NCV further details the dependencies between military capabilities, enabling capability options to be built in a more coherent manner and effective trade-offs to be conducted across NATO common funded programmes.

Covered by NATO release conditions.

Views*

The NATO Capability View in NAF has the following 6* sub views:

• NCV-1 Capability Vision Subview
• NCV-2 Capability Taxonomy Subview*
• NCV-3 Capability Phasing Subview
• NCV-4 Capability Dependencies Subview
• NCV-5 Capability to Organisational Deployment Mappings Subview*
• NCV-6 Capability to Operational Activities Mapping Subview

This set is similar to that in the MODAF Strategic Viewpoint.

There are in 49 subviews* defined in the NATO Architecture Framework.

Configuration History

• 3.1 removes NCV-7 Capability to Services Mapping Subview - becomes NSOV-3 Capability to Service Mapping Subview in the NATO Service-Oriented View.

Comments

The NCV-6 is variously called NCV-6 Capability to Operational Activities Mapping Subview in Chapter 4 and NCV-6 Operational Activity to Capability Mapping Subview in Chapter 5 so it’s not obvious what the proper title is.

Note that the NATO AF 3.1 documentation isn’t yet in a consistent state - it appears to be in the process of changing Subview to View but still has view meaning both an individual (view) specification and a collection of (view) specifications. It is also confused between a view as a specification and the product of that specification.  See NATO AF v3.1 - Is It Now Time to Merge MODAF and the NATO AF?

Other Frameworks

See also:

• DNDAF::Strategic View (StratV) and DNDAF::Capability View (CapV)
• DODAF::Capability Viewpoint
• MODAF::Strategic Viewpoint
• TRAK::Enterprise Perspective

References

• Section 4.4 (page 189 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3. http://www.nhqc3s.nato.int/Browser.asp?Target=_docs/NAF_v3
• Section 5.2.3 of ANNEX 1 TO AC/322(SC/1-WG/1)N(2009)0005-ADD2. NATO Architecture Framework Version 3.1. http://www.nhqc3s.nato.int/Browser.asp?Target=_docs/NAF_v3_1
• The Residual World. NATO AF v3.1 - Is It Now Time to Merge MODAF and the NATO AF? http://trak-community.org/index.php/residualWorld/comments/nato_af_v3.1_is_it_now_time_to_merge_modaf_and_the_nato_af

 

Category:Framework -> View

Categories:

• Framework
  • View