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.
OV products
▪High-Level Operational Concept Graphic (OV-1)
▪Operational Node Connectivity Description (OV-2)
▪Operational Information Exchange Matrix (OV-3)
▪Organizational Relationships Chart (OV-4)
▪Operational Activity Model (OV-5)
▪Operational Rules Model, State Transition Description, and Event-Trace Description (OV-6a, 6b, and 6c)
▪Logical Data Model (OV-7)
Standards
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 may 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”).