OV-3 – Operational Resource Flow Matrix

The OV-3 details the operational information exchanges between performers, as defined in the OV-2, Operational Resource Flow Description.

Information exchanges help define the interoperability requirements associated with the operational capability of interest. Although the primary purpose of this view is to specify information exchanges, an OV-3 may also list flows of materiel, energy and human resources.

Usage

The intended usage of the OV-3 includes:

• Definition of interoperability requirements.

Product Description

The OV-3 identifies the resource transfers that are necessary to support operations to achieve a specific operational task. This model is initially constructed from the information contained in the OV-2 Operational Resource Flow Description model. But the OV-3 provides a more detailed definition of the Resource Flows for operations within a community of anticipated users.

The Operational Resource Flow Matrix details Resource Flow exchanges by identifying which Operational Activity and locations exchange what resources, with whom, why the resource is necessary, and the key attributes of the associated resources. The OV-3 identifies resource elements and relevant attributes of the Resource Flows and associates the exchange to the producing and consuming Operational Activities and locations and to the Needline that the Resource Flow satisfies. OV-3 is one of a suite of operational models that address the resource content of the operational architecture (the others being OV-2 Operational Resource Flow Description, OV-5b Operational Activity Model, and DIV-2 Logical Data Model).

An architect may specify attributes for the Resource Flows in OV-3. Typical attributes would be “timeliness”, “availability”, “protective marking”, “non-repudiation”, etc.

The emphasis in this view is on the logical and operational characteristics of the Resource Flows. It is important to note that OV-3 is not intended to be an exhaustive listing of all the details contained in every Resource Flow of every Operational Activity and location associated with the Architectural Description in question. Rather, this model is intended to capture the most important aspects of selected Resource Flows. The table below shows an example of the relevant information content.

Data Description	Nature of Transaction	Performance Attributes	Information Assurance	Security
Data element Name and Identifier Content Format Type Media Type Accuracy Units of Measurement Data Standard	Transaction Type Triggering Event Interoperability Level Achieved Criticality	Periodicity Timeliness Throughput Size	Access Control Availability Confidentiality Dissemination Control Integrity Non-Repudiation Consumer	Protection (Type Name, Duration, Date) Classification Classification Caveat Releasability Security Standard

 

Creating an Operational Resource Flow (Performer-Based) table

The OV-3 Operational Resource Flow (Performer-Based) table identifies the information transfers that are necessary to enable the performers to achieve a business objective. It details information exchanges by identifying which performers exchange what information, with whom, why the information is necessary, and the key attributes of the associated information products.

To create an Operational Resource Flow (Performer-Based) table:

1. Click on Operational Resource Flow (Performer-Based) in the Action Artifact area to open the Operational Resource Flow (Performer-Based) table.
2. This opens the Operational Resource Flow (Performer-Based) table with OperationalExchanges listed. The OperationalExchanges are defined in OV-2.
3. For each of the OperationalExchanges:
   1. Enter its ID
   2. Select the items involved in the operational exchange.
   3. Optionally fill in the attributes of operational exchanges.

Creating an Operational Resource Flow (Role-Based) table

The Operational Resource Flow (Role-Based) table specifies the information exchanges among performers. Unlike the performer-based table, role-based table focuses on the interactions between roles inside the operational performers.

To create an Operational Resource Flow (Role-Based) table:

1. Click on Operational Resource Flow (Role-Based) in the Action Artifact area to open the Operational Exchanges table.
2. This opens the Operational Exchanges table with OperationalExchanges listed.
3. For each of the OperationalExchanges:
   1. Create a new OperationalExchange by clicking on the New Operational Exchange above the table.
   2. This creates a new row of OperationalExchange. Enter its name.
   3. Select the OperationalConnector that the OperationalExchange realizes. The OperationalConnectors are defined in OV-2.
   4. Select the items involved in the operational exchange.
   5. Optionally fill in the attributes of operational exchanges.

DoDAF in Visual Paradigm

The DoDAF is brought to you by Visual Paradigm, a full-featured development platform. Visual Paradigm provides an easy-to-use, model-driven DoDAF tool that supports the development of DoDAF 2.02 views and models. You can create integrated DoDAF products and generate architectural documents that facilitate organizations to efficiently coordinate enterprise architecture initiatives.