Architecting and designing : DoDAF : DoDAF 2 : Creating enterprise models using DoDAF 2 Viewpoints : Building DoDAF 2 models for the Operational Viewpoint : OV-02 Operational Resource Flow Description and Alternative diagrams (DoDAF 2) : OV-02 Operational Resource Flow Description diagrams
  
OV-02 Operational Resource Flow Description diagrams
You can draw the following symbols on an OV-02 Operational Resource Flow Description diagram:
Performer, and any of its subtypes, such as Interface (Port), Organization, Performer, Person, Service. Service Interface, or System
Resource Flow line symbols between Performers
The OV-02 can also show the location of Operational facilities or locations, and can optionally be annotated to show flows of information, funding, people, or materiel between Operational Activities.
Note An alternative to the OV-02 Operational Resource diagram is available in System Architect: the OV-02 Operational Resource Alternative diagram enables you to draw not only Performers and Resource Flows between them, but also many other artifact types.
The following artifacts are drawn on the OV-02 Operational Resource Flow Alternative diagram:
Performer
Performer is the person or organization that performs an Activity. There are several kinds of performers, such as Person and Organization, but also System, Interface, Service, and Service Interface. All of these kinds of Performer inherit all of their properties from Performer.
You specify the Activity or Activities that a Performer performs via the ActivityPerformedbyPerformer relationship. On the OV-2, you can draw an ActivityPerformedByPerformer line from an Activity to any kind of Performer symbol.
Activity
An Activity is work (not specific to a single organization, weapon system, or individual) that transforms inputs (Resources) into outputs (Resources) or changes their state.
ActivityPerformedByPerformer
You can specify that an Activity is performed by a Performer by drawing an ActivityPerformedByPerformer line from an Activity to a Performer on the OV-02 Operational Resource Flow Alternative diagram.
Information
Information is a type of Resource: it inherits Resource's properties and behavior.
Capability
You can relate Capabilities to the Activities that perform them by drawing an ActivityAbletoPerformCapability line from an Activity to a Capability.
Resource
The following are types of resources:
Resource
ArchitecturalDescription
Data
DomainInformation
Information
Materiel
Performer
Person
Organization
Service
ServiceDescription
Service Interface
System Interface (Port)
ActivityChangesResource
You can specify that an Activity effects change on a Resource by drawing an ActivityChangesResource line from an Activity to any kind of Resource (and any kind of Performer since Performer is a subclass of Resource), available on the OV-02 Operational Resource Alternative diagram.
Materiel
Materiel is a type of Resource. Materiel represents equipment, apparatus, or supplies that are of interest, without distinction as to its application for administrative or combat purposes. You can draw Materiel on the OV-02 diagram, and specify what Activity effects change on Materiel by drawing an ActivityChangesResource line from an Activity to a Materiel symbol.
ActivityAbletoPerformCapability
You can specify that an Activity is able to perform a Capability by drawing an ActivityAbletoPerformCapability line from an Activity to a Capability, available on the OV-02 Operational Resource Alternative diagram.
describedBy
Any kind of Thing can be described by Information. In the DM2 metamodel, this means that Activity, Resource, or Capability can be described by Information: you can draw a describedBy line from Activity, Resource (and all of its subtypes), or Capability, to the Information symbol (or supertypes such as Resource). The describedBy relationship enables you to specify how the following model types describe one another:
Any type of Resource describedBy another Resource (for example, you might specify that a Resource is described by an Information type. Once you draw the describedBy relationship between a Resource and an Information symbol, then the Resource definition's ListOf Information property is populated accordingly.
Any type of Performer describedBy any type of Resource (for example, you might specify that a Performer is described by a Resource. Once you draw a describedBy relationship from Performer to Resource, the Performer's ListOf Resource property is populated accordingly.
See also
OV-02 Operational Resource Flow alternative diagrams
OV-02 Operational Resource Flow Description and Alternative diagrams (DoDAF 2)
Artifact types of the DoDAF 2 metamodel
Relationships of the DoDAF 2 metamodel