The primary purpose of the OV-2 View is to model the Nodes that provide the focus for capability requirements in an operational context. The secondary purpose of the OV-2 View is to define a logical network of information flows.
Operational nodes
According to the MODAF 1.2 specification, the nodes on the OV-2 do not need to correspond to specific organizations, systems, or locations. This allows you to establish Information Exchange Requirements (IERs) without inadvertently specifying solutions.
You can specify the following properties for an operational node:
•Operational Activities (Introduction tab): Describe what actions are to be performed in the node (for example, Sending Orders).
•Supports Capabilities (StV tab): Capabilities that the Node supports.
•Required Location (OV tab): Location(s) of the Node.
•Related Actual Organization (OV tab): The Actual Organizations that are involved with a particular mission.
•Represents Known Resource (SV tab): You can relate the Node to Capability Configurations, Platforms, System Resources, Software, Physical Assets, Role Types, Post Types, and Organization Types. The Choices button of this property provides a heterogeneous list of these definition types.
•Provides Service (SOV tab): Services that the operational node provides.
•Consumes Service (SOV tab): Services that the operational node consumes.
You can use an Explorer diagram to graphically show relationships between operational nodes and each of the artifacts above.
Logical flow lines
You can draw logical flow lines between operational nodes on an OV-2 diagram.
•A logical flow line can take on stereotypes <<Needline>>, <<Energy Flow>>, <<Movement of People>>, or <<Material Flow>>. The default stereotype of a logical flow line is <<Needline>>.
•You can specify the stereotype of the logical flow in the MODAF tab of its definition dialog. You can specify that the logical flow is one of the following types.
Needlines and information exchange requirements
A needline (specifically a logical flow line of stereotype <<Needline>>) can have information exchanges specified against it. information exchanges describe what information is needed to support the activities between the operational nodes. By modeling this information, you can understand and make decisions about which systems are needed to satisfy the business needs of an organization or functional area.
You can add information exchanges to the definition of a logical flow line of stereotype <<Needline>> in its Info. Exchanges tab. If you do not see the Info. Exchanges tab in the definition, then the logical flow line does not have the <<Needline>> stereotype set.
Information exchange characteristics can be output to an OV-3 Information Exchange Matrix (select Reports > MODAF Reports > OV-3 Operational Information Exchange Matrix, and see Generating OV-3 Information Exchange Matrix reports for MODAF). An information exchange can also be seen on the definition of an ICOM Arrow on an OV-5 Activity Model Diagram.
Note In MODAF 1.2, the OV-2 diagram changed by renaming needline to logical flow. Your existing needlines will remain on a diagram, but now are named “Logical Flow” with the stereotype set to <<Needline>>.
Tabs associated with the Information Exchange are:
Nature of Transaction
Referenced Data: Refers to entities on the OV-7 Logical Data Model
Purpose/Trigger Event:Can be associated to this definition dialogue if relevant.
Mission/Scenario
Language
Content
Size/Units
Media
Collaborative or One Way
LISI Level Required
Performance Requirements
Frequency, Timeliness, Throughput, Other
Information Assurance Attributes
Classifications/Declassifications Restrictions, Criticality/Priority, Integrity Checks Required, Assured Authorization TO Send/Receive
