Operational Views (OV) [Logical Views]

OV-3 Operational Information Exchange Matrix

The Operational Information Exchange Matrix (OV-3) addresses operational information exchanges between nodes.

Background:

Information exchanges provide further detail of the interoperability requirements associated with the operational capability of interest. The focus is on information exchanges that cross the capability boundary.

Usage:

Data objects:

The data in an OV-3 can include:

Representation:

Detailed Product Description:

The Operational Information Exchange Matrix (OV-3) identifies the information transfers that are necessary to support the operational nodes to achieve a specific operational task. This view is initially constructed from the information contained in the Operational Node Connectivity Description (OV-2). But OV-3 provides a more detailed definition of the information flows between operational nodes.

The Operational Information Exchange Matrix details information exchanges by identifying which nodes exchange what information, with whom, why the information is necessary, and the key attributes of the associated information products. The focus should be on identifying information exchanges that cross the capability boundary.

Information exchanges express the relationship across the three basic Architecture data elements for the Operational Viewpoint (operational activities, operational nodes, and information flows) with a focus on the specific aspects of the information flow and the information content. OV-3 is one of a suite of operational views that address the information content of the operational architecture (the others being OV-2, OV-5 and OV-7).

The OV-3 Product identifies information elements and relevant attributes of the information exchange and associates the exchange to the producing and consuming Operational Nodes and activities and to the Needline that the exchange satisfies. Needlines are logical requirements-based collaboration relationships between nodes (as shown in OV-2). A Needline is uni-directional.

An information element is a formalised representation of information subject to an operational process (see OV-7). Information elements may mediate activity flows and dependencies (se OV-5). Hence they may also be ‘carried’ by needlines that express collaboration relationships between nodes. The same information element may be used in one or more information exchanges.

The aspects of the information exchange that are crucial to the operational mission will be tracked as attributes in OV-3. For example, if the subject Architecture concerns tactical battlefield targeting, then the timeliness of the enemy target information is a significant attribute of the information exchange. To support the needs of security architecture, IERs should also address criticality and classification.

There is not always a one-to-one mapping of OV-3 information exchanges to OV-2 Needlines; rather, many individual information exchanges may be associated with one Needline. In OV-3, this information is captured in tabular form.

The MOD does not currently prescribe the column headings in an OV-3 Matrix.


More Complex OV-3 Example

The emphasis in this View is on the logical and operational characteristics of the information being exchanged, with focus on the exchanges crossing the capability boundary. It is important to note that OV-3 is not intended to be an exhaustive listing of all the details contained in every information exchange of every Operational Node associated with the Architecture in question. Rather, this Product is intended to capture the most important aspects of selected information exchanges.

There is an important caveat on use of OV-3 for security architectures. In that context, it is important to identify every possible and required exchange.

Page version 1.1, dated 4th April 2007