View DNDAF:OV-4a Organizational Relationships Chart Subview



OV-4a Organizational Relationships Chart Subview

Version & Date

1.6 See DNDAF Release History


The OV-4a subview is part of the DNDAF Operational View.

The Operational View-4a (OV-4a): Organizational Relationships Chart illustrates the organizational structure and relationships. The OV-4a answers the questions: who is who? Who is responsible for whom and for what?


The OV-4a defines the various relationships that exist between organizations including relationships to external organizations.

The main purpose of OV-4a is to depict an overall picture of the organization relationship structure. OV-4a intends to address the questions “who are the organizations?” and “which organizations are responsible for what?” The OV-4a can also be used for other organizational analysis and reconfiguration.

The human resource roles and skills associated with each organization will be addressed in OV-4b, Organization to Role/Skill Matrix.


Regardless of the scope of the architecture project, decision makers as well as operators need to understand the command structure and relationships among organizations.



The Organizational Relationships Chart (OV-4a) illustrates the command structure and/or relationships among organizations that are the players in the scope of architecture project.

Detailed Description

OV-4a illustrates the relationships among organizations or resources in the architecture project. These relationships can include supervisory reporting, command and control relationships, and command- subordinate relationships. It may also include a coordination relationship between equals, where two organizations coordinate or collaborate without one having a supervisory or command relationship over the other. Others may be defined depending on the purpose of the architecture.

Enterprise Architects may define various kinds of relationships necessary and important within their architecture to support the goals of the architecture project. For example, dynamic teams or task forces (i.e., new operational nodes) may be created in real time with only limited life spans and assigned missions, and could have needlines assigned to them.

Subview DADM Elements

The DADM entities and attributes provided below are the elements that this sub-view is responsible for creating:




  • graphical



  • p43 Figure 3.7.1 in DND/CF Architecture Framework (DNDAF)  Volume 2: DND/CF Views and Sub-Views
  • p30 Figure 2.8.1 in DND/CF Architecture Framework (DNDAF)  Volume 4: DND/CF User Guide


The OV-2 is the prerequisite for this sub-view:


See DNDAF Subview Dependencies



This represents part of the solution - the “how to” - and therefore isn’t in keeping with the abstract or logical nature of the Operational View. This is a legacy from DODAF that affects MODAF and NAF as far as the OV-4 is concerned.

The subview is flexible in terms of the relationship allowed between organisation elements as the examples show - ‘commands’, ‘coordinates’, ‘advises’  but as there is no declared set of relationships to restrict the architect’s choice and meaning of the subview there is potential for inconsistency which makes sharing architecture models more difficult.

Other Frameworks

See also:


Category:Framework -> Specification
Category:Framework -> Subview



© 2010 Eclectica Systems Ltd.