1 Fit For Purpose Example Capability AoA 11 May 2010 Architecture, Standards & Interoperability Directorate Office of the DoD Deputy Chief Information.

1

Fit For Purpose Example

Capability AoA11 May 2010

Architecture, Standards & Interoperability Directorate

Office of the DoD Deputy Chief Information Officer

2

Agenda

• Accomplishments Since Release of DoDAF V2.0 Promulgation Memo – Shelton Lee

• UPDM Search & Recue (SAR) Exemplars -Dave McDaniel

• DoDAF V2.0 SAR Analysis and Fit-for-Purpose Exemplar – Shelton Lee

• DoDAF V2.0 Way Ahead – Mike Wayson

• Questions & Answers - DoDAF V2.0 Development Team

Search & Rescue Concept of Operations

3

When the US pilot is shot down or has a mishaps resulting with the pilot in water the request to organize the search and rescue operations is forwarded to the Coalition SAR coordinating unit

The SAR coordinating unit tries to obtain available rescue pick-up resources and synchronize them with medical facility to be used during the operation

Under normal situations this is not a problem

Survival Time in Cold Water

Water Temperature Exhaustion of Unconsciousness in

Expected Survival Time

70–80° F (21–27° C) 3–12 hours 3 hours – indefinitely

60–70° F (16–21° C) 2–7 hours 2–40 hours

50–60° F (10–16° C) 1–2 hours 1–6 hours

40–50° F (4–10° C) 30–60 minutes 1–3 hours

32.5–40° F (0–4° C) 15–30 minutes 30–90 minutes

<32° F (<0° C) Under 15 minutes Under 15–45 minutes

Search & Rescue As-Is State & Problem Statement

5

In sea states of 7 or greater there are inadequate resources available to perform a successful search & rescue

Rescue Rate is 40 percent in sea states 7 or greater

Require significant US military and other government resources resulting in little or no positive outcome

Search & Rescue To-Be State & Desired Operational Outcome

6

Goal: Achieve a Survival Rate of 100 percent in high sea states of 10 or less

What is a Capability

7

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.

Alternatives

• Use Capability Viewpoint models to capture 3 alternatives

– Alt1 – DOTMLPF solution (training)

– Alt 2 – Minor Materiel solution

– Alt 3 – System solution

8

Methodology: DoDAF V2.0 Six-Step Architecture Development Process

9

Determine theintended use of the architecture


1

Determinescope of

architecture

Determinescope of

architecture

2Determine data

required tosupport

architecturedevelopment

Determine datarequired to

supportarchitecturedevelopment

3Collect, organize,

correlate, andstore architecture

data

Collect, organize,correlate, and

store architecturedata

4Conduct

analyses insupport of

architectureobjectives

Conductanalyses insupport of


5Document

Results IAWDecision-Maker

needs

DocumentResults IAW

Decision-Makerneeds

6

Provide list of data needed and use

cases


cases

3.1

Model toDM2 Concept

List

Model toDM2 Concept

List

Review list of architecture dataand determine if it meets the use

cases


cases

3.2

DM2 ConceptualData Model &

Logical Data Model


Logical Data Model

Assist with the Architect’s

data collectionprocesses



4.1

List of architecture

data


data

PotentialCollectionMethods


SelectedCollectionMethods


Verify the datacollected meetsthe use cases


5.1

ExampleUses

ExampleUses

Fit-for-PurposeUse

Fit-for-PurposeUse

Determine howdata needs to be

presented


presented

6.1

LegacyProducts

LegacyProducts User

Requirements

UserRequirements Example

Presentations

ExamplePresentations

Fit-for-PurposePresentations


Decision Makers

Subject Matter Experts

Analyst

Architect Manager


Architect

Introduction

• Use Capability Viewpoint models to capture 3 alternatives– Alt1 – DOTMLPF solution (training)– Alt 2 – Minor Materiel solution– Alt 3 – System solution

• Supporting models: – Alt 1: OV-4, OV-6a– SV-1 hierarchy– SV-1 interface model, OV-6c

• Capability Measures Matrix• Fit for Purpose View based on the data

– Dashboard10

CV-1 Capability Vision

11

Use CV-1 to show • Capability Desired Effects• Mapped to Vision

CV-2 Capability Hierarchy

12

Use CV-2 to show • Capability with Desired Effect – High Sea State Rescue• Current state capability and target state alternatives

Alternative 1 - DOTMLPF

13

• Alternative 1 is a DOTMLPF Solution• Requires Training for new skills• OV-4 shows org chart with new skills

Alternative 1 – Target Process Flow

14

• OV-6c Event Trace Description used to capture new process flow• Could be simulated to determine Search Time, Rescue Time, etc.

Alternative 2 – Materiel Solution

15

Source: Survival at Sea for Mariners, Aviators and Search and Rescue PersonnelDr. C.J. Brooks and Mr. Peter Gibbs, Q.G.A. Survival Systems Ltd. Dartmouth, Nova Scotia

Alternative 2 – Materiel Solution

16

• Alternative 2 is a materiel solution – improved jumpsuit for pilots• Capability decomposed into a SV-1 showing Pilot equipped with new

Waterproof Thermal Jumpsuit

Alternative 3 – Major System Solution

17

Source: Survival at Sea for Mariners, Aviators and Search and Rescue PersonnelDr. C.J. Brooks Survival Systems Ltd. Dartmouth, Nova Scotia

Alt 3 – Major System Solution

18

Major system solution

To be defined by systemarchitecture

Including high level SV-1

Alternative 3 – SV-10c Event Trace

19

• SV-10c Event Trace Model used to capture new sequencing• Used to determine Measure of Effectiveness of new capability

Measure Guidelines:

20

1. Keep measures simple. A simple measure requires only a single measurement (e.g., hours to develop an operation order).

2. Measures and criteria should reflect an understanding of activity.

3. Measures and criteria should reflect how an activity contributes to mission success.

4. Measures should be sensitive to the impact of conditions.

5. Measures should be developed that distinguish among multiple levels of performance.

6. Measures should focus on the outputs, results of performance, or on the process to achieve the activity.

7. Measures should try to take advantage of the strengths of both absolute and relative scales.

Source: Joint Mission Thread Measures Development Standard Operating Procedures (SOP) Draft , 3 May 2010

Capability Metrics

21

Using Measure/Measure Type

Capture Capability Metrics in a matrix format

This is based on as-is and/or to-be architecture description

Provides basis for quantitative analysis

• Capabilities across the top• Measure Type on the side• Measure and Unit of

Measure in cells

Fit For Purpose Views

22

Observations:• Alternative 1 and 3 have shorter Search Times• Alternative 2 does NOT address search time or Rescue Time• Alternative 3 ONLY address search time, not rescue time


23

Observations:• Alternative 1 presents the highest Risk Factor but also the

highest “Feasibility Level”• Alternative 3 the lowest Risk Factor but lowest Feasibility Level


24

Observations:• Alternative 3 provides the highest survival rate, at the greatest

cost.• Alternative 1 and 2 provide a much improved Survival Rate at

significantly less cost

Fit for Purpose CV-2 Model

25

• CV-2 Capability Taxonomy view with FfP Dashboard Indicators• High-low status bars, “speedometer” gauges aid in AoA

Methodology: DoDAF V2.0 Six-Step Architecture Development Process

26



1

Determinescope of

architecture

Determinescope of

architecture

2Determine data

required tosupport

architecturedevelopment

Determine datarequired to

supportarchitecturedevelopment

3Collect, organize,

correlate, andstore architecture

data

Collect, organize,correlate, and

store architecturedata

4Conduct

analyses insupport of


Conductanalyses insupport of


5Document

Results IAWDecision-Maker

needs

DocumentResults IAW

Decision-Makerneeds

6


cases


cases

3.1

Model toDM2 Concept

List

Model toDM2 Concept

List


cases


cases

3.2


Logical Data Model


Logical Data Model





4.1


data


data







5.1

ExampleUses

ExampleUses

Fit-for-PurposeUse

Fit-for-PurposeUse


presented


presented

6.1

LegacyProducts

LegacyProducts User

Requirements

UserRequirements Example

Presentations

ExamplePresentations



Decision Makers


Analyst

Architect Manager


Architect

Agenda

• Accomplishments Since Release of DoDAF V2.0 Promulgation Memo – Shelton Lee





DoDAF V2.1 Way Ahead

28

Validate DM2 against analysis requirements and use cases

Develop process-specific use case exemplar

Generate PES XML from DM2 conformant database

Create Fit for Purpose Views in context of use case

Develop analysis use case scenario

Update DoDAF Essential Guide

29

Questions

DoDAF V2.0 Contacts

30

Michael WaysonGovernment Sponsor

[email protected]

Shelton LeeDoDAF Working Group

[email protected]

Dave McDanielDoDAF DM2 Working Group

[email protected]

Rick MyersDoDAF Website [email protected]

Backup Slides

31

32

Agenda

• Accomplishments Since Release of DoDAF V2.0 Promulgation Memo – Mike Wayson


• DoDAF V2.0 Architectural Models and the DM2 objects captured in the context of the relevant model – Chris White




DM2-Model Correlation

33

OV-6c Event Trace

Description

SV-1 System Interface

Description

OV-4 Organizational Relationships

CV-2 Capability Taxonomy

CV-1 CapabilityVision

SV-10C Event Trace

Description

PV-2 Project Timelines

Capability Viewpoint

34



Capability Viewpoint

35



Operational Viewpoint

36

OV-6c Event Trace

Description


Operational Viewpoint

37

OV-6c Event Trace

Description


Systems Viewpoint

38


Description

SV-10C Event Trace

Description

Systems Viewpoint

39


Description

SV-10C Event Trace

Description


Project Viewpoint

40

DM2-Model Correlation

41

OV-6c Event Trace

Description


Description




SV-10C Event Trace

Description


1 Fit For Purpose Example Capability AoA 11 May 2010 Architecture, Standards & Interoperability Directorate Office of the DoD Deputy Chief Information.

Documents

capability hierarchy

capability vision

rescue time

search time

capability data group

available rescue

rescue operations

system solution