Architecting and designing > NATO Architecture Framework (NAF) > NAF v3 > Creating Operational View products for NAF 3
  
Creating Operational View products for NAF 3
The operational architecture view describes the tasks, activities, operational elements, and information flows that are required for a military operation to take place. It describes what types and how often information can be exchanged, which tasks and activities are supported by the information exchanges, and the nature of information exchanges in order to establish specific interoperability requirements.
There are seven NOV products:
High-Level Operational Concept Graphic (NOV-1)
Operational Node Connectivity Description (NOV-2)
Operational Information Exchange Matrix (NOV-3)
Organizational Relationships Chart (NOV-4)
Operational Activity Model (NOV-5)
Operational Event/Trace (NOV-6)
Logical Data Model (NOV-7)
The following standards apply to the operational architecture:
The primary purpose of an operational architecture is to define operational elements, activities and tasks, and information exchange requirements
Operational architectures incorporate doctrine and assigned tasks and activities
Activities and information-exchange requirements can cross organizational boundaries
Operational architectures are not generally systems-dependent
Generic activity descriptions are not based on an organizational model or force structure
Operational architectures should clearly identify the time phase(s) covered (for example, specific years; “as is” or “to be;” “baseline,” “planned,” and “transitional”).
See also
NOV-1 High-level Operational Concept
NOV-4 Organizational Relationships charts
Creating NOV-1a High-level Operational Concept diagrams for NAF 3
Creating NOV-2 operational node connectivity diagrams for NAF 3
Generating NOV-3 Information Exchange Matrix reports for NAF 3
Creating NOV-5 Activity Models for NAF 3
Creating NOV-6 activity sequence and timing diagrams for NAF 3
NAF v3