Operational Views (OV) [Logical Views]

OV-1a High-Level Operational Concept Graphic

The OV-1a describes a mission, class of mission, or scenario. It shows the main Operational Nodes (see OV-2 definition) and interesting or unique aspects of operations. It describes the interactions between the subject architecture and its environment, and between the architecture and external systems. A textual description accompanying the graphic is crucial. Graphics alone are not sufficient for capturing the necessary architecture data.

Background:

The OV-1a provides a graphical view of what the architecture is about and an idea of the players and operations involved. An OV-1a can be used to orient and focus detailed discussions. Its main use is to aid human communication, and it is intended for presentation to high-level decision makers.

Usage:

Data objects:

An OV-1a is typically just a graphic. The data to be included in an OV-1a can be any business objects of interest, including:

Representation:

Detailed Product Description:

Each Operational View relates to a specific point within the Enterprise’s timeline.

The High-Level Operational Concept Graphic describes a mission, class of mission, or scenario. It may highlight the key Operational Nodes (see OV-2 definition) and interesting or unique aspects of the concepts of operations. It provides a description of the interactions between the subject Architecture and its environment, and between the Architecture and external systems. A textual description accompanying the graphic is crucial. Graphics alone are not sufficient for capturing the necessary Architecture data.

The purpose of OV-1a is to provide a quick, high-level description of what the Architecture is supposed to do, and how it is supposed to do it. An OV-1a View Product can be used to orient and focus detailed discussions. Its main utility is as a facilitator of human communication, and it is intended for presentation to high-level decision makers.

OV-1a consists of a graphical executive summary for a given Architecture with accompanying text (amplified in OV-1b). An OV-1a View Product identifies the mission/domain covered in the Architecture and the viewpoint reflected in the Architecture. OV-1a will convey, in simple terms, what the Architecture is about and an idea of the players and operations involved.


Example OV-1a

The content of an OV-1a View Product depends on the scope and intent of the Architecture, but in general it describes the business processes or missions, high-level operations, organisations, and geographical distribution of assets. The Product will frame the operational concept (what happens, who does what, in what order, to accomplish what goal) and highlight interactions to the environment and other external systems. However the content will still be of an executive summary level as other Views allow for more detailed definition of interactions and sequencing.

During the course of developing an Architecture, several versions of an OV-1a View Product may be produced. An initial version may be produced to focus the effort and illustrate its scope. After other Products within the Architecture’s scope have been developed and verified, another version of this Product may be produced to reflect adjustments to the scope and other Architecture details that may have been identified as a result of the Architecture development. After the Architecture has been used for its intended purpose and the appropriate analysis has been completed, yet another version may be produced to summarise these findings to present them to high- level decision makers. In other cases, OV-1a is the last Product to be developed, as it conveys summary information about the whole Architecture for a given scenario.

OV-1a is the most general of the Architectural Views and the most flexible in format. Because the format is freeform and variable, no template is shown for this View. However, an OV-1a Product usually consists of one or more graphics (or possibly a video-clip), as needed, as well as explanatory text.


Example OV-1a (Source: DCSA)

From a modelling perspective, the OV-1a View is useful in establishing the context for a suite of related operational views. This context may be in terms of Enterprise Phase, a time period, a mission and/or a location. In particular this provides a container for the spatio-termporally constrained performance parameters depicted in OV-1c.

To illustrate this, the operational performance metrics for desert warfare in Phase 1 may be different to those in Phase 2. The metrics for jungle warfare in Phase 2 may be different to those for desert warfare in Phase 2.

The context may also explicitly involve a Mission. In M3, a Mission is defined in quite general terms as a purpose to which resources may be directed.

When the subject of the Architecture is a business capability rather than a battlespace capability, then some adjustment is needed in the use of terminology. However, the idea of having a High Level (Business) Operational Concept still makes sense and the graphical representation in OV-1a still adds value to the more structured views that may be created.

Page version 1.1, dated 4th April 2007

Top of Page