The OV-5a and the OV-5b “Operational Activity Model” describe the operations that are normally conducted in the course of achieving a mission or a business goal. It describes operational activities (or tasks); Input/Output flows between activities, and to/from activities that are outside the scope of the Architectural Description.
The OV-5a and OV-5b describes the operational activities that are being conducted within the mission or scenario. The OV-5a and OV-5b can be used to:
- Clearly delineate lines of responsibility for activities when coupled with OV-2 “Operational Resource Flow Description”.
- Uncover unnecessary Operational Activity redundancy.
- Make decisions about streamlining, combining, or omitting activities.
- Define or flag issues, opportunities, or operational activities and their interactions (information flows among the activities) that need to be scrutinized further.
- Provide a necessary foundation for depicting activity sequencing and timing in the OV-6a “Operational Rules Model”, the OV-6b “State Transition Description”, and the OV-6c “Event-Trace Description”.
The OV-5b describes the operational, business, and defense portion of the intelligence community activities associated with the Architectural Description, as well as the:
- Relationships or dependencies among the activities.
- Resources exchanged between activities.
- External interchanges (from/to business activities that are outside the scope of the model).
An Operational Activity is what work is required, specified independently of how it is carried out. To maintain this independence from implementation, logical activities and locations in OV-2 “Operational Resource Flow Description” are used to represent the structure which carries out the Operational Activities. Operational Activities are realized as System Functions (described in SV-4 “Systems Functionality Description”) or Service Functions (described in SvcV-4 Services Functionality Description) which are the how to the Operational Activities what, i.e., they are specified in terms of the resources that carry them out.
The intended usage of the OV-5a and OV-5b includes:
- Description of activities and workflows
- Requirements capture
- Definition of roles and responsibilities
- Support task analysis to determine training needs
- Problem space definition
- Operational planning
- Logistic support analysis
- Information flow analysis
|DoDAF Viewpoint Matrix|
- The DoDAF descriptions in this website are very generic and are mostly taken from the DoDAF Architecture Framework website. Make sure you visit the actual website for the most update information and a more thorough explanation of each viewpoint.
- DoDAF Version 1.0, although outdated, has some good examples on how to construct AV’s, OV’s, and SV’s.
AcqLinks and References:
-  DoDAF Architecture Framework Version 2.02
- DoD Architecture Framework Working Group Version 1.0, Volume 1: Definition and Guideline, 9 Feb 04 (Old Version)
- DoD Architecture Framework Version 1.0, Volume 2: Product Description, 9 Feb 04 (Old Version)
- Website: DoDAF Architecture Framework – DoD Deputy Chief Information Officer
- Website: DoDAF Version 2.02 Journal