DODAF - DOD Architecture Framework Version 2.02 - DOD Deputy Chief Information Officer

DM2 Data Groups

Capability

The Capability Data Group provides information on the collection and integration of activities that combine to respond to a specific requirement. A capability, as defined here is "the ability to achieve a desired effect under specified standards and conditions through combinations of means and ways to perform a set of tasks." This definition is consistent with that contained in the JCIDS Instruction published by the Joint Staff.

Data Group Description

The DoDAF Meta Model for the data comprising Capability is shown in the figure below. Items of note:

  1. Ways and means are interpreted in DM2 language to be Resources and Activities
  2. Because a Desired Effect is a desired state of a Resource (see Goals data group), a Capability is about states (persistence of current ones, or changes to future ones) of Resources. 
  3. Capabilities link to Measures (Metrics) through the Activities they entail and the Desired Effects sought.
  4. Capabilities relate to Services via the realization of the Capability by a Performer that is a Service. In general, a Service would not provide the Desired Effect(s) but, rather, access to ways and means (Activities and Resources) that would.

 

DoDAF Meta Model for Capability 

DoDAF Meta Model for Capability
(Click image to enlarge)


Usage in Core Processes

Data for Capabilities are used to describe the capability; define acquisition and development requirements necessary to provide the required capability; facilitate understanding of capability execution; develop/update/improve doctrine and educational materials in support of capability execution; and to facilitate sharing and reuse of data.

The Capabilities Data Group (CDG) has a representation at varying levels, from enterprise level to solutions and applies to all DoD core processes. This includes enterprise goals associated with the overall vision, that provide a strategic context for the capabilities described by an architecture, and an accompanying high-level scope, more general than the scenario-based scope defined in an operational concept diagram. At this level, the CDG enables a high-level description of capabilities in decision-makers contexts that can be used for communicating a strategic vision regarding capability evolution. Factors considered in a Capability Based Analysis are:

  1. Doctrine
  2. Organizations
  3. Training
  4. Materiel
  5. Leadership and Education
  6. Personnel
  7. Facilities

The following sections document how the Capability Data Group and DM2 support analysis of each of these factors.

In Joint Pub 1-02, Dictionary of Military and Associated Terms, doctrine is defined as "Fundamental principles by which the military forces or elements thereof guide their actions in support of national objectives. It is authoritative but requires judgment in application."

The concept of judgment required in application deals with decision making and cannot be precisely modeled except perhaps as rules affecting the applicability of other rules. The parts of doctrine that can be modeled are included in the capability data group as follows:

a. Principles are modeled as Rules.

b. Military forces and elements thereof are modeled as types and assemblies of Performers.

c. Actions are modeled as Activities.

Thus, doctrine is contained in the specification of certain fundamental Rules, Activities, and Performers and the relationships among them. These relationships are:

a. Each Performer must be of one or more Activities.

b. Each Activity must be by one or more Performers.

c. Each Rule may be a constraint on one or more Activities.

d. Each Activity may be constrained by one or more Rules.

e. Each Rule may be a constraint on one or more Performers.

f. Each Performer may be constrained by one or more Rules.

Thus, since the DM2 contains the entities and relationships listed above it contains the necessary and sufficient set of entities and relationships to permit the modeling of doctrine and a separate data group for Doctrine is not required.

Organization. An organization is a specific real-world assemblage of people and other resources organized for an ongoing purpose. DM2 models Organizations as a type of Performer.

Defining an Organization as an assemblage means that each Organization exhibits a whole/part relationship whereby each Organization may be an assembly of other Organizations and each Organization may also be a component of one or more other Organizations. The following DM2 relationships are involved in the capability based analysis of Organization where each Organization is a type of Performer:

a. Each Capability must be the result of one or more Activities.

b. Each Activity must be by one or more Performers, where each Performer must be a type of Organization, therefore, each Capability must be provided by one or more Organizations.

c. Each Organization must be the Performer of one or more Activities.

d. Each Rule may be a constraint on one or more Organizations.

e. Each Organization may be constrained by one or more Rules.

f. Each Rule may be a constraint on one or more Activities.

g. Each Activity may be constrained by one or more Rules.

Training is defined as an activity or set of Activities to increase the capacity of one or more performers to perform one or more tasks under specified conditions to specific standards:

a. Each Performer may be either an Organization or a Person.

b. Each Performer must be of one or more Activities.

c. Each Activity must be performed under one or more Conditions.

d. Each Activity must be completed to meet one or more Standards.

e. Each Standard must be specified by one or more Measures.

Materiel is a type of Resource. Like Organization above, each Materiel exhibits a whole/part relationship whereby each Materiel may be an assembly of other Materiels and each Materiel may also be a component of one or more other Materiels.

The following DM2 relationships are involved in the capability based analysis of materiel where each Materiel is a part of a Performer:

a. Each Performer must be assigned to one or more Organizations.

b. Each Performer must be used by one or more Persons, where each Person must be the member of only one Organization at any one time.

c. Each Capability must be the result of one or more Activities.

d. Each Activity must be by one or more Performers, where each Performer must be either an Organization or a Person using a Performer.

e. Each Performer must be the Performer of one or more Activities.

f. Each Rule may be a constraint on one or more Performers.

g. Each Performer may be constrained by one or more Rules.

h. Each Rule may be a constraint on one or more Activities.

i. Each Activity may be constrained by one or more Rules

Leadership and Education. Joint Pub 1-02 does not define leadership. In the context of the DM2, leadership is defined as the ability to lead. Joint Pub 1-02 defines Military Education as the systematic instruction of individuals in subjects that will enhance their knowledge of the science and art of war. Thus, to a certain extent, leadership is a set of skills that can be taught as part of the science and art of war and a smaller set of skills that can be trained as Activities that must be performed under specified conditions to meet specified standards.

Leadership is about the judgment required in application of doctrine; it deals with decision making and cannot be precisely modeled except perhaps as rules affecting the applicability of other rules.

Personnel. Personnel refer to Persons. Each Person is a type of Performer.

The following DM2 relationships are involved in the capability based analysis of materiel where each Person is a type of Performer:

a. Each Person must be assigned to only one Organization at any one time.

b. Each Person may the user of one or more Materiels.

c. Each Materiel must be used by one or more Persons.

d. Each Capability must be the result of one or more Activities.

e. Each Activity must be by one or more Performers, where each Performer must be either an Organization or a Person using a Materiel.

f. Each Person must be the Performer of one or more Activities.

g. Each Rule may be a constraint on one or more Persons.

h. Each Person may be constrained by one or more Rules.

i. Each Rule may be a constraint on one or more Persons.

j. Each Activity may be constrained by one or more Rules.

Facilities. A Facility is defined as a real property entity consisting of underlying land and one or more of the following: a building, a structure (including linear structures), a utility system, or pavement. Please note that this definition requires that facilities be firmly sited on or beneath the surface of the earth. Things like tents, aircraft, and satellites that are not affixed to a single location on or beneath the surface of the earth are a type of Materiel. Materiel are germane to capability-based analysis through the following relationships:

a. Each Facility may be the site of one or more Performers and any Materiel that is part-of the Performer(s).

b. Each Performer may be at only one Facility or within a Materiel enclosure at any one time.

c. Because a Facility is an Individual, it has a spatial and temporal extent.

An Individual instance of Materiel has a spatial and temporal extent in contrast to a Type which does not. Generally Architectural Descriptions deal with Types of Materiel, not specific Individuals, e.g., not specific serial-numbered items of equipment. However, the DM2 does represent a Performer at a Location and, consequently, any Materiel that is part of the Performer would also be at the Location.

Presentation

Capabilities are typically depicted in tabular or textual form. In some cases a pictorial is used to help clarify the Capability. It is desirable that Capabilities be presented in a structured manner showing primary and derived capabilities. Capabilities should be presented in a manner depicting traceability to both Activities and Goals.