OV-2: Operational Resource Flow Description

The steps below walk the user through populating data in Collector for an OV-2: Operational Resource Flow Description class diagram. This how-to topic presumes a novice-level knowledge of Architex and the Collector module. These steps can be completed by a user with write access to the module and architecture.
An OV-2 describes the flow of resources between performers within an operational context.
It may be helpful to sketch out the overall operation (on a whiteboard or paper) before entering data into Collector.
Nodes and elements that should be populated at the end of this process:
Views Also Used In
OV-3, OV-5b, OV-6c
Operational Activity
CV-6, OV-3, OV-5a, OV-5b, SvcV-5, SV-5a, SV-5b
Node Operation
Operational Activity
OV-3, OV-5b
Operational Exchange Item
OV-3, OV-6c
Operational Exchange
Operational Exchange Item
Source Node
Target Node
OV-3, OV-6c
(Screenshots are from the SAR EA Example architecture, provided with most data services.)
1. Load the desired architecture (based on the UPDM 2.1 Framework) in Collector.
2. To capture the performers of the operation or mission, select the Node node in the Outlook Bar. This node is a general repository for all task performers, which can include organizations, units, groups, roles, or posts.
2a. Add the performers to the Name element. (If there are no records in the node, click the Add button in the Ribbon Bar.)
2b. In the Composition element, select a parent performer to create a nested hierarchy of nodes. Not every performer needs to have a parent. If your newly added parent does not appear in the drop-down menu, click the Update References or the Refresh Data button in the Ribbon Bar.
3. The activities performed by a node are identified in the Operational Activity node. Select it, and add any new items to the Name element.
4. The activities are connected to their performers in the Node Operation node.
4a. In the Operational Activity element, select an activity from the pull-down menu.
4b. In the Node element, select the performer that carries out that activity.
5. Any items exchanged between the performers during the operation are identified in the Operational Exchange Item node.
6. The connections between nodes, plus which items are exchanged, are defined in the Operational Exchange node.
6a. Select the start of the connection (or relationship) from the Source Node element.
6b. Select the recipient of the connection from the Target Node element.
6c. Select the item exchanged during the step in the Operational Exchange Item element.
7. In the Reporter module, select the OV-2 report and generate it. (See how to create an OV-2 if you need to create or modify the OV-2 for this enterprise.) If the resulting diagram is not correct, then return to Collector and make any necessary changes.
© 2019 Exostrategies, Inc.