View NAF:NOV-4 Organisational Relationship Chart Subview
Overview
The NOV-4 Organisational Relationship Chart subview is part of the NATO Operational 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.4 NATO Operational View (NOV)
in AC/322(SC/1-WG/1)N(2009)0005-ADD2. NATO Architecture Framework Version 3.1
document from https://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.5.4
The Organisational Relationship Chart identifies the key players in the operational domain that is subject to the architecture effort, and illustrates the organisational relationships among these key players.
Covered by NATO release conditions
Description
From the NATO Architecture Framework v3
, CHAPTER 4, Section 4.5.4
An NOV-4 product particularly identifies the key players. These key players may be deployed to the nodes of an NOV-2, which contain added detail on how the key players interact together in order to conduct their corresponding operational activities of NOV-5. Key players seem to be best described using role-based descriptions, independent of the fact whether a role actually involves an entire operational node or just a single human role. NOV-4 may be developed using strictly role-based elements representing the key players.
There can be many types of organisational relationships between the key players:
- Command and Control (C2) relationships;
- hierarchical relationships;
- functional relationships;
- reporting relationships;
- collaboration relationships, and so on.
Organisational relationships are important to depict in a NATO Operational View, because they can illustrate fundamental human roles (e.g. who or what type of skill is needed to conduct operational activities) as well as management relationships (e.g., command structure or relationship to other key players). Also, organisational relationships may influence how the operational nodes in an NOV-2 are connected. For example, command and control relationships may differ under different circumstances. Differing command relationships may mean that activities are performed differently or by different units. Different coordination relationships may mean that connectivity requirements are changed.
Covered by NATO release conditions
Data Objects*
From the NATO Architecture Framework v3.1
, CHAPTER 5, Section 5.2.4.4
The data in an NOV-4 can include:
- Organisation Types
- Resource Composition relationships
- Resource Interaction relationships
- Post Types
- Role Type*
- Actual Posts and Organisations
- Competences
- Information Elements (each carried by one or more Information Exchange)
Covered by NATO release conditions
From The MODAF Operational Viewpoint
p24:
Full size:File:MODAF OV4OrganisationalRelationships simpplifiedMM.gif
Subject to Crown Copyright
Note: The fragment of simplified metamodel is identical to that in MODAF 1.2.004 for the MODAF::OV-4 Organisational Relationships Chart View with the following substitutions for view/subview number:
- MODAF::OV-4 equates to NAF::NOV-4
- MODAF::SV-1 equates to NAF::NSV-1
- MODAF::AcV-1/MODAF::AcV-2 equates to NAF::NPV-1/NAF::NPV-2
- MODAF::StV-2 equates to NAF::NCV-2
Presentation
Configuration History
- 3.1 replaces Role with Role Type in data objects
Comments
The NOV-4 looks to be misplaced. It could be described using the NSV-1.
Stereotypes such as Actual Post, Post Type, Actual Organisation, Organisation Type are defined in the glossary for the NATO Operational View. These are really part of the solution and therefore the System View. Node is the structural equivalent to Resource in the Operational View.
Role / Role type is part of the NATO System View
Resource Interactions are definitely part of the NATO System View not the operational one (which should be solution independent).
Competence, in the Operational View, is closely associated with a Functional Resource which is in the System View.
These are legacy structural problems probably inherited from MODAF.
The equivalent could be expressed using the NSV-1 System Interface Description Subview.
Ways of depicting an organisation chart and also role extents using different frameworks are covered separately.
References
- Section 4.5.4 (page 208 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
- Section 5.2.4.4 (page 382 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
- Section 5.2.4.5 of Chapter 5 AC/322(SC/1-WG/1)N(2009)0005-ADD2 NATO Architecture Framework Version 3.1
- The MODAF Operational Viewpoint. 26th April 2010. https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/38711/20100426MODAFOVViewpoint1_2_004U__1_.pdf
Other Frameworks
See also:
- Organisation - Organisation structure is addressed by the DNDAF::OV-4a Organizational Relationships Chart Subview whereas Role - Organisation mapping and competence is addressed by the DNDAF::OV-4b Organization to Role/Skill Matrix Subview
- DODAF::OV-4 Organizational Relationships Chart Model
- MODAF::OV-4 - Organisational Relationships Chart View
- TRAK::SVp-01 Solution Structure Viewpoint - for the structure and governance, TRAK::SVp-02 Solution Resource Interaction Viewpoint - for the Resource Interactions between Organisations, Jobs and Roles and competence is addressed using the TRAK::SVp-06 Solution Competence Viewpoint
Category:Framework -> View
Category:NAF -> Subview
Category:Operational