Operational View (OV) is one of the basic views defined in the enterprise architecture (EA) of the Department of Defense Architecture Framework V1.5 (DoDAF) and is related with concept of operations. Under DODAF 2, which became operational in 2009, the collections of views are now termed 'viewpoints' and no longer views. Other enterprise architecture frameworks may or do have operational views. For example, the MODAF has an Operational Viewpoint and the NATO Architecture Framework has an Operational View (collection of subviews). This article will further explain the construction of the Operational View of the DoDAF V1.5.
The "Operational View" (OV) in the DoDAF Enterprise architecture framework (version 1/1.5) ('Operational Viewpoint' in DODAF 2) describes the tasks and activities, operational elements, and information exchanges required to conduct operations. A pure Operational View is material independent. However, operations and their relationships may be influenced by new technologies such as collaboration technology, where process improvements are in practice before policy can reflect the new procedures.
The operational viewpoint provides a means to describe what is needed in a solution-free or implementation-free way. There may be some cases, however, in which it is necessary to document the way processes are performed given the restrictions of current systems, in order to examine ways in which new systems could facilitate streamlining the processes. In such cases, an Operational View may have material constraints and requirements that must be addressed. For this reason, it may be necessary to include some high-level Systems View (SV) architecture data as overlays or augmenting information onto the Operational View products.
The Department of Defense Architecture Framework (DoDAF) defines a standard way to organize a systems architecture into complementary and consistent views. It is especially suited to large systems with complex integration and interoperability challenges, and is apparently unique in its use of "operational views" detailing the external customer's operating domain in which the developing system will operate.
The DoDAF defines a set of products that act as mechanisms for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through graphic, tabular, or textual means. These products are organized under four views:
Each view depicts certain perspectives of an architecture as described below. Only a subset of the full DoDAF viewset is usually created for each system development. The figure represents the information that links the operational view, systems and services view, and technical standards view. The three views and their interrelationships driven – by common architecture data elements – provide the basis for deriving measures such as interoperability or performance, and for measuring the impact of the values of these metrics on operational mission and task effectiveness.
The Department of Defense Architecture Framework (DoDAF) has defined a series of seven different types of Operational View products. There are seven OV products described in this section:
Description (OV-6a, 6b, and 6c)
DoD Electronic Commerce Concept of Operations (OV-1). https://handwiki.org/wiki/index.php?curid=1826691
Joint Network Enabled Weapon (NEW) Capability Operational Concept Graphic (OV-1). https://handwiki.org/wiki/index.php?curid=1244019
Joint Task Force Concept of Operations (OV-1). https://handwiki.org/wiki/index.php?curid=1988888
Example OV-1 for NCOW. https://handwiki.org/wiki/index.php?curid=1843271
OV-2 Template. https://handwiki.org/wiki/index.php?curid=1908539
Notional Example of an OV-2 Depicting Service Providers. https://handwiki.org/wiki/index.php?curid=1953668
UML OV-2 Template. https://handwiki.org/wiki/index.php?curid=1163602
OV-3 – Template. https://handwiki.org/wiki/index.php?curid=1559814
OV-4 – Template. https://handwiki.org/wiki/index.php?curid=1867363
UML OV-4 Sample. https://handwiki.org/wiki/index.php?curid=1755953
Operational Activity Hierarchy Chart (OV-5) – Template. https://handwiki.org/wiki/index.php?curid=1730360
Operational Activity Diagram (OV-5) – Template. https://handwiki.org/wiki/index.php?curid=1591653
OV-5 – Template with Notional Annotations. https://handwiki.org/wiki/index.php?curid=1385518
UML Example OV-5. https://handwiki.org/wiki/index.php?curid=1338358
In addition to examining behavior over time, one can also assess an overall dynamic mission cost over time in terms of human and system/network resource dollar costs and their processes dollar costs. Analysis of dollar costs in executable architectures is a first step in an architecture based investment strategy, where we eventually need to align architectures to funding decisions to ensure that investment decisions are directly linked to mission objectives and their outcomes. The figure on the right illustrates the anatomy of one such dynamic model.
State transitions in executable operational architectural models provide for descriptions of conditions that control the behavior of process events in responding to inputs and in producing outputs. A state specifies the response of a process to events. The response may vary depending on the current state and the rule set or conditions. Distribution settings determine process time executions. Examples of distribution strategies include: constant values, event list, constant interval spacing, normal distribution, exponential distribution, and so forth. Priority determines the processing strategy if two inputs reach a process at the same time. Higher priority inputs are usually processed before lower priority inputs.
Processes receiving multiple inputs need to define how to respond. Examples of responses include: process each input in the order of arrival independent of each other, process only when all inputs are available, or process as soon as any input is detected. Processes producing multiple outputs can include probabilities (totaling 100 percent), under which each output would be produced. Histograms are examples of generated timing descriptions. They are graphic representations of processes, human and system resources, and their used capacity over time during a simulation run. These histograms are used to perform dynamic impact analysis of the behavior of the executable architecture. Figure 4-23 is an example showing the results of a simulation run of human resource capacity.