View NAF:Capability Configuration
Version & Date
Version 3.1.
Overview
The Capability Configuration is one of the NAF Stereotypes that form the NATO Architecture Framework Metamodel (NMM). It is defined as part of the NATO System View (NSV).
Definition
NATO AF v3.1, Chapter 5 p116
A composite structure representing the physical and human resources (and their interactions) in an enterprise.
A CapabilityConfiguration is a set of artefacts or an organisation configured to provide a capability, and should be guided by [doctrine] which may take the form of Standard or OperationalConstraint stereotypes.
Covered by NATO release conditions.
Revision History
NAF 3.0:
A combination of organisational aspects (with their competencies) and equipment that combine to provide a capability. A <<CapabilityConfiguration>> is a physical asset or organisation configured to provide a capability, and must be guided by [doctrine] which may take the form of <<Standard>> or <OperationalConstraint>> stereotypes.
Covered by NATO release conditions.
Comments
Note that in version 3.1 Capability Configuration can have a Function and can interact.
NATO AF v3.1, Chapter 5, 5.2.6.1 p116:A Capability Configuration is a combination of organisational resources (with their competencies) and equipment that combine to provide a capability. A Capability Configuration is a combination of Artifacts (be they termed Systems or Platforms) or Organisational Resource configured with other Resources (System, Roles, other Capability Configurations, Software) to provide a capability. A physical resource contributing to a capability must either be an organisational resource or a physical asset, i.e. a system cannot contribute alone (it must be hosted on a physical asset or used by an organisational resource or both)).
Capability Configurations fulfill the operational capability needs and are usually defined to fulfill the requirements associated with Nodes (see NOV-2).
Covered by NATO release conditions.
This means that NAF:System cannot include people (Human Resource) - people are always external to a system. A system in NAF cannot provide any capability nor can NAF be used for a soft system.
References
Section 5.2.6.1 (p411) of APPENDIX 5 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework v3, CHAPTER 5
Section 5.2.6.14 (p439) of APPENDIX 5 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework v3, CHAPTER 5
Other Frameworks
See:
MODAF::Capability Configuration
TRAK::System
Category:Stereotype
Category:Defence
Category:NAF -> View -> Systems