×
Menu
Index

OV-5b: Operational Activity Model

 
The diagram and steps (below the image) walk the user through populating data in Collector for an OV-5b: Operational Activity Model activity 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-5b describes the activities or tasks that are performed during an operation, mission, or process. It is similar to an OV-5a: Operational Activity Decomposition Tree (which is typically expressed as a class diagram); however, an OV-5b can also include inputs and outputs.
 
It may be helpful to sketch out the overall operation or process (on a whiteboard or paper) before entering data into Collector.
 
Nodes and elements that should be populated at the end of this process:
Node
Element
Views Also Used In
Operational Activity
Name
Composition
CV-6, OV-2, OV-3, OV-5a, SvcV-5, SV-5a, SV-5b
Node
Name
IsCapableOfPerforming
OV-2, OV-3, OV-6c
Node Role
Node
Performs In Context
 
Operational Activity Action
Source Activity
Target Activity
Name (optional)
 
Operational Parameter (optional)
Name
 
Node Operation (optional)
Operational Activity
Input Operational Parameter
Output Operational Parameter
Node
OV-2
 
(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 process and the activities that are conducted within it, select the Operational Activity node in the Outlook Bar.
2a. Enter the name of the overall (or parent) process in the Name element. (If the node is empty, click the Add button in the Ribbon Bar.)
 
2b. Enter the activities in the Name element.
 
2c. In the Composition element, select the parent process from the menu for each associated activity. If the newly added parent does not appear in the menu, click the Update References or Refresh Data button in the Ribbon Bar.
 
3. Next, we need to assign performers to the process. These task performers can be organizations, units, groups, roles, or posts, and are captured in the Node node, a general repository for all task performers. Select that node now.
3a. Add any new performers to the Name element.
 
3b. In the IsCapableOfPerforming element, select the activity parent process for each applicable performer.
 
4. Now that the performers are identified, we will assign their individual tasks or activities in the Node Role node.
4a. If a record does not already exist for a performer, then add a record and select that performer in the Node element.
 
4b. For each node, select the activities they accomplish in the Performs In Context element.
 
5. The steps of the process are outlined in the Operational Activity Action node. The first step is selected in Source Activity, and the next step is selected in Target Activity. The previous Target Activity will then become the Source Activity in the next record. (NOTE: It may be easier to order the steps first in Excel, and then either paste into the table or select from the drop-down menu in Collector.)
 
6. The Operational Parameter node is where the inputs and outputs are captured. Enter both inputs and outputs in the Name element.
 
7. Lastly, we need to define where the input is used and where the output is created during the process. This is done in the Node Operation node. In the Operational Activity element, select the activity that uses or creates the item. If the item is used, select it in the Input Operational Parameter element; if it is created, select it in the Output Operational Parameter element. In the Node element, select the performer involved.
 
8. In the Reporter module, select the OV-5b report and generate it. (See how to design an OV-5b if you need to create or modify the OV-5b for this process.) If the resulting process flow is not correct, then return to Collector and make any necessary changes.
© 2019 Exostrategies, Inc.