1. Tutorial Mr. Walt Okon Mr. David McDaniel (ctr) February 2013
Capability Views
Tutorial
Mr. Walt Okon
Mr. David McDaniel (ctr)
February 2013

2. Topics Joint Staff definition of Capability
DoDAF Meta Model (DM2) Formalization of the Joint Staff definition
DoDAF Capability Views
Exemplar set #1
Exemplar set # 2
Actual examples
6 Feb 2013 2

3. Introduction
Capability is the organizing concept for force management in response to mission orders. The Joint Staff defines capability as,
The ability to achieve a desired effect under specified standards and conditions through combinations of means and ways to perform a set of tasks. [[i]]
Thus, the capability requirement has 6 components: 1) the desired effects, 2) measures associated with the effects, 3) tasks to be performed, 4) standards of performance (metrics) for the tasks, 5) conditions under which the tasks must be performed, and 6) measures associated with the conditions. Capability configurations that can provide or support intermediate, contributing, partial, and end effects are then modeled and evaluated against actual reported readiness data. These are modeled in the DoD capability model as shown in the next slide
[i] Joint Chiefs of Staff; Joint Capabilities Integration and Development System (JCIDS); CJCSI H; January 2012
6 Feb 2013

4. DoDAF Meta Model (DM2) of Capability
6 Feb 2013

5. Some important things to note about this model
Desired effects are resource states. This simplification is enabled by the formal ontology on which the model is founded (described briefly in DoDAF Vol III). Specifically, 1) because the ontology is four-dimensional, all instances are spatio-temporal extents so a resource has a temporal extent and has possible future extents, and 2) because the ontology is meronymic, resources have wholes and parts so that a resource can be a complex aggregate of all types of things, in principle including Political, Military, Economics, Social, Infrastructure, and Information (PMESII).
Desired resource states are ontologically synonymous with goals, objectives, and outcomes. Extensive research by the DoD working group that developed this model concluded that there was no objective distinction between the concepts because only subjective terms such as “more”, “greater”, “longer term”, “broader”, etc. were used to distinguish them. Since the foundation ontology is spatio-temporally mereologic, this distinction is not necessary.
Desired resource states can be for resource states of adversarial or neutral parties as well as blue force. For example, for a Joint Suppression of Air Defenses (JSEAD) mission, the desired effects might include that the resource state of the target area’s air defenses reaches some desired measures of destruction, denial, disruption, degradation, and / or deception (D5). For a humanitarian assistance mission, the desired effects might include that the resource state for the victim population reaches nutrition, shelter, health, and low casualty rates.
Activities, including operational activities, are considered ontologically synonymous with Tasks. Though arguable, the DoD capability modeling group could not determine an objective distinction.
6 Feb 2013

6. Some important things to note about this model (cont’d)
Measures enable modeling of the quantifiable aspects of the desired effect as well as the performance of tasks and the conditions under which they must be performed. The concept of measure is this model derives from [[i]]. The ability to ascribe measures to what may seem unmeasureable effects is inspired by [[ii]] but is substantiated by measures in the Universal Joint Task List (UJTL) [[iii]] associated with every task and by the measures standard operating procedures established by DOT&E [[iv]].
In addition to measures associated with task performance, specified standards also imply conformance with guidance, rules, etc., shown as a constraint on the performance of the tasks.
Conditions are modeled in accordance with the UJTL conditions and, therefore, measures are also associated with conditions.
A related resource flow model, of which core elements are shown above (Activity, activityProducesResource, activityConsumesResource, and Resource) links Activities to produced resources (i.e., resource states and typically complex aggregates of resources) so that the tasks to produce the desired effects are modeled as resource flows. This enables not only linkage of the tasks with the desired effects but also modeling of intermediate (e.g., causal) desired effects that can lead to the end-state desired effect. Activities and their performers are the core of the ways and means – capability configuration – that is the focus of the presentation and algorithmic work proposed herein.
Capability configuration that might provide such a capability are modeled as performers, which are typically aggregates of, for example, air, space, and cyber assets that are located geo-spatially and that have measures associated with their overall performance and readiness as well as the individual elements that comprise them, including the personnel.
[i] Ellis, Brian; Basic Concepts of Measurement; Cambridge University Press, Oct 1, 1968
[ii] Hubbard, Douglas; How to Measure Anything: Finding the Value of "Intangibles" in Business; John Wiley & Sons, Aug 3, 2007
[iii] Joint Chiefs of Staff; Universal Joint Task Manual; CJCSM E; August 2008
[iv] Director, Operational Test and Evaluation (DOT&E), Joint Test and Evaluation Methodology (JTEM); Joint Mission Thread Measures Development Standard Operating Procedures (SOP); May 3, 2010
[v] DoDAF CV-2: This model identifies and describes one or more hierarchies of capabilities provided by an architecture, and it specifies the types of hierarchical relationships between these capabilities.
6 Feb 2013

7. Capability Data Group and the Capability Views
CV-1 Vision
CV-2 Capability Taxonomy
CV-3 Capability Phasing
CV-4 Capability Dependencies
CV-5 Capability To Organizational Development Mapping
CV-6 Capabilities to Operational Activities Mapping
CV-7 Capabilities to Services Mapping
6 Feb 2013

8. Core Components of Capability (red outline)
CV-1 Vision
CV-2 Capability Taxonomy
CV-3 Capability Phasing
CV-4 Capability Dependencies
CV-5 Capability To Organizational Development Mapping
CV-6 Capabilities to Operational Activities Mapping
CV-7 Capabilities to Services Mapping
6 Feb 2013 8

9. CV-1 Vision CV-1 Vision CV-2 Capability Taxonomy
CV-3 Capability Phasing
CV-4 Capability Dependencies
CV-5 Capability To Organizational Development Mapping
CV-6 Capabilities to Operational Activities Mapping
CV-7 Capabilities to Services Mapping
6 Feb 2013 9

10. CV-2 Capability Taxonomy
CV-1 Vision
CV-2 Capability Taxonomy
CV-3 Capability Phasing
CV-4 Capability Dependencies
CV-5 Capability To Organizational Development Mapping
CV-6 Capabilities to Operational Activities Mapping
CV-7 Capabilities to Services Mapping
6 Feb 2013

11. CV-3 Capability Phasing
CV-1 Vision
CV-2 Capability Taxonomy
CV-3 Capability Phasing
CV-4 Capability Dependencies
CV-5 Capability To Organizational Development Mapping
CV-6 Capabilities to Operational Activities Mapping
CV-7 Capabilities to Services Mapping
6 Feb 2013 11

12. CV-4 Capability Dependencies
CV-1 Vision
CV-2 Capability Taxonomy
CV-3 Capability Phasing
CV-4 Capability Dependencies
CV-5 Capability To Organizational Development Mapping
CV-6 Capabilities to Operational Activities Mapping
CV-7 Capabilities to Services Mapping
6 Feb 2013

13. CV-5 Cap to Org Development
CV-1 Vision
CV-2 Capability Taxonomy
CV-3 Capability Phasing
CV-4 Capability Dependencies
CV-5 Capability To Organizational Development Mapping
CV-6 Capabilities to Operational Activities Mapping
CV-7 Capabilities to Services Mapping
6 Feb 2013 13

14. CV-6 Capability/Activities
CV-1 Vision
CV-2 Capability Taxonomy
CV-3 Capability Phasing
CV-4 Capability Dependencies
CV-5 Capability To Organizational Development Mapping
CV-6 Capabilities to Operational Activities Mapping
CV-7 Capabilities to Services Mapping
6 Feb 2013

15. CV-7 Capability/Services
CV-1 Vision
CV-2 Capability Taxonomy
CV-3 Capability Phasing
CV-4 Capability Dependencies
CV-5 Capability To Organizational Development Mapping
CV-6 Capabilities to Operational Activities Mapping
CV-7 Capabilities to Services Mapping
6 Feb 2013 15

16. Examples
Derived from the Object Management Group (OMG) Unified Profile for MODAF and DoDAF (UPDM) Appendix C example for “Search and Rescue”.
One set illustrating analysis
Another set illustrating relationship to DM2
6 Feb 2013

17. SAR Capability Vision (CV-1)
8/29/2018
SAR Capability Vision (CV-1)
Vision: Save lives, defend our borders, and protect the environment
Mission: Reduce operating costs to meet budget cuts
Goal: Increase personnel recovery effectiveness and efficiency
Capability
Manage SAR Support
Operate SAR Mission
Coordinate SAR Operations
Focus for “thread” 17
6 Feb 2013 17

18. SAR Capability Vision (CV-1)
Purpose –understand USCG vision , goals and supportive capability
Save lives, project the environment, and defend our borders
Capability Vision
Increased personnel recovery effectiveness (xx% successful recovery rate)
Desired Effects
Reduced operating costs to meet budget cuts ($xx)
Increased personnel recovery efficiency (xx% less resource cost)
Manage SAR Support
Operate SAR Mission
Coordinate SAR Operations
Tasks
NGOs
Conditions
Weather
PMESII*
Speed (xx hrs)
*Political, Military, Economic, Social, Infrastructure and Information systems
Sea State 18
6 Feb 2013

19. Capability Taxonomy (CV-2)
8/29/2018
Capability Taxonomy (CV-2)
Definition: Hierarchy of capabilities decomposed down to leaf level to expose activities
Data Sources: Policy Document, Subject Matter Expert (SME) Interview, Concept of Operations (CONOPs), Tactic, Technique & Procedure, Operational Requirement Document
Purpose: Identify and organize capabilities through logical decomposition to support planning and gap analysis
Analysis: Which capabilities support & relate to each other
Consumers:
Enterprise Architect
Program Manager 19
6 Feb 2013 19

20. SAR Capability Taxonomy (CV-2)
8/29/2018
SAR Capability Taxonomy (CV-2)
Execute SAR (Capability)
Operate SAR Mission (Capability)
Locate Personnel (Capability)
High level Capability (parent) 20
6 Feb 2013 20

21. SAR Capability Taxonomy (CV-2)
8/29/2018
SAR Capability Taxonomy (CV-2)
Focus for Scenario
Capability
Purpose – Understand SAR capabilities in context of each other. 21
6 Feb 2013 21

22. Capability To Operational Activity (CV-6)
8/29/2018
Capability To Operational Activity (CV-6)
Definition: Captures capabilities required and activities that enable those capabilities.
Purpose:
Decomposes down to unique leaf level
Provides organization of activities
Data Sources: Policy Document, Subject Matter Expert (SME) Interview, Concept of Operations (CONOPs), Tactic, Technique & Procedure, Operational Requirement Document
Analysis: What activities support which capabilities
Consumers:
Enterprise Architect
Program Manager
This decomposes the capabilities into unique operations at a leaf level.
Each of these level functions can now be analyzed in a context level process model 22
6 Feb 2013 22

23. Capability To Operational Activity (CV-6)
8/29/2018
Capability To Operational Activity (CV-6)
Operate SAR Mission (Capability)
Locate Person in Distress (Capability)
Perform Electronic Search (Activity)
Perform Visual Search (Activity)
Support Person in Distress (Capability)
Establish Communications (Activity)
Most expensive activity 23
6 Feb 2013 23

24. SAR Capability to Operational Activity (CV-6)
8/29/2018
SAR Capability to Operational Activity (CV-6)
Purpose – Decomposes capability down to unique leaf level and shows all supportive operational activities that support each capability.
Enterprise architect view typically
Leaf –level Capability relates to Operational Activity
Most expensive activity
Capability 24
6 Feb 2013 24

25. UPDM SAR Example Set Illustrating DM2
6 Feb 2013

26. UPDM SAR CV-1
*In MODAF the CVs are called Strategic Views (StV)
6 Feb 2013

27. Partial1 CV-1 with DM2 Markups
6 Feb 2013

28. UPDM SAR CV-2
6 Feb 2013

29. Partial1 CV-2 with DM2 Markups
6 Feb 2013

30. UPDM SAR CV-4
6 Feb 2013

31. Partial1 CV-4 with DM2 Markups
6 Feb 2013

32. UPDM SAR CV-5
6 Feb 2013

33. Partial1 CV-5 with DM2 Markups
6 Feb 2013

34. UPDM SAR CV-6
6 Feb 2013

35. CV-6 with DM2 Markups
6 Feb 2013

36. CV-7 with DM2 Markups
6 Feb 2013

37. Some Actual Examples of CV-1 and CV-3
6 Feb 2013