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

2. 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

3. 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

4. Survival Time in Cold Water Water TemperatureExhaustion of Unconsciousness in Expected Survival Time 70–80° F (21–27° C) 3–12 hours3 hours – indefinitely 60–70° F (16–21° C) 2–7 hours2–40 hours 50–60° F (10–16° C) 1–2 hours1–6 hours 40–50° F (4–10° C) 30–60 minutes1–3 hours 32.5–40° F (0–4° C) 15–30 minutes30–90 minutes <32° F (<0° C) Under 15 minutesUnder 15–45 minutes

5. 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

6. 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

7. 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.

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

9. Methodology: DoDAF V2.0 Six-Step Architecture Development Process 9 Determine the intended use of the architecture Determine the intended use of the architecture 1 Determine scope of architecture Determine scope of architecture 2 Determine data required to support architecture development Determine data required to support architecture development 3 Collect, organize, correlate, and store architecture data Collect, organize, correlate, and store architecture data 4 Conduct analyses in support of architecture objectives Conduct analyses in support of architecture objectives 5 Document Results IAW Decision-Maker needs Document Results IAW Decision-Maker needs 6 Provide list of data needed and use cases Provide list of data needed and use cases 3.1 Model to DM2 Concept List Model to DM2 Concept List Review list of architecture data and determine if it meets the use cases Review list of architecture data and determine if it meets the use cases 3.2 DM2 Conceptual Data Model & Logical Data Model DM2 Conceptual Data Model & Logical Data Model Assist with the Architect’s data collection processes Assist with the Architect’s data collection processes 4.1 List of architecture data List of architecture data Potential Collection Methods Potential Collection Methods Selected Collection Methods Selected Collection Methods Verify the data collected meets the use cases Verify the data collected meets the use cases 5.1 Example Uses Example Uses Fit-for-Purpose Use Fit-for-Purpose Use Determine how data needs to be presented Determine how data needs to be presented 6.1 Legacy Products Legacy Products User Requirements User Requirements Example Presentations Example Presentations Fit-for-Purpose Presentations Fit-for-Purpose Presentations Decision Makers Subject Matter Experts Analyst Architect Manager Subject Matter Experts Architect

10. 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 –Dashboard 10

11. CV-1 Capability Vision 11 Use CV-1 to show Capability Desired Effects Mapped to Vision

12. 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

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

14. 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.

15. Alternative 2 – Materiel Solution 15 Source: Survival at Sea for Mariners, Aviators and Search and Rescue Personnel Dr. C.J. Brooks and Mr. Peter Gibbs, Q.G.A. Survival Systems Ltd. Dartmouth, Nova Scotia

16. 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

17. Alternative 3 – Major System Solution 17 Source: Survival at Sea for Mariners, Aviators and Search and Rescue Personnel Dr. C.J. Brooks Survival Systems Ltd. Dartmouth, Nova Scotia

18. Alt 3 – Major System Solution 18 Major system solution To be defined by system architecture Including high level SV-1

19. 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

20. 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

21. 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

22. 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. Fit For Purpose Views 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. Fit For Purpose Views 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

25. 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

26. Methodology: DoDAF V2.0 Six-Step Architecture Development Process 26 Determine the intended use of the architecture Determine the intended use of the architecture 1 Determine scope of architecture Determine scope of architecture 2 Determine data required to support architecture development Determine data required to support architecture development 3 Collect, organize, correlate, and store architecture data Collect, organize, correlate, and store architecture data 4 Conduct analyses in support of architecture objectives Conduct analyses in support of architecture objectives 5 Document Results IAW Decision-Maker needs Document Results IAW Decision-Maker needs 6 Provide list of data needed and use cases Provide list of data needed and use cases 3.1 Model to DM2 Concept List Model to DM2 Concept List Review list of architecture data and determine if it meets the use cases Review list of architecture data and determine if it meets the use cases 3.2 DM2 Conceptual Data Model & Logical Data Model DM2 Conceptual Data Model & Logical Data Model Assist with the Architect’s data collection processes Assist with the Architect’s data collection processes 4.1 List of architecture data List of architecture data Potential Collection Methods Potential Collection Methods Selected Collection Methods Selected Collection Methods Verify the data collected meets the use cases Verify the data collected meets the use cases 5.1 Example Uses Example Uses Fit-for-Purpose Use Fit-for-Purpose Use Determine how data needs to be presented Determine how data needs to be presented 6.1 Legacy Products Legacy Products User Requirements User Requirements Example Presentations Example Presentations Fit-for-Purpose Presentations Fit-for-Purpose Presentations Decision Makers Subject Matter Experts Analyst Architect Manager Subject Matter Experts Architect

27. 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

28. 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. 29 Questions

30. DoDAF V2.0 Contacts 30 Michael Wayson Government Sponsor michael.wayson@osd.mil Shelton Lee DoDAF Working Group shelton.lee@lmco.com Dave McDaniel DoDAF DM2 Working Group davem@silverbulletinc.com Rick Myers DoDAF Website Administrator richard.k.myers@lmco.com

31. Backup Slides 31

32. 32 Agenda Accomplishments Since Release of DoDAF V2.0 Promulgation Memo – Mike Wayson UPDM Search & Recue (SAR) Exemplars -Dave McDaniel DoDAF V2.0 Architectural Models and the DM2 objects captured in the context of the relevant model – Chris White 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

33. DM2-Model Correlation 33 OV-6c Event Trace Description SV-1 System Interface Description OV-4 Organizational Relationships CV-2 Capability Taxonomy CV-1 Capability Vision SV-10C Event Trace Description PV-2 Project Timelines

34. Capability Viewpoint 34 CV-2 Capability Taxonomy CV-1 Capability Vision

35. Capability Viewpoint 35 CV-2 Capability Taxonomy CV-1 Capability Vision

36. Operational Viewpoint 36 OV-6c Event Trace Description OV-4 Organizational Relationships

37. Operational Viewpoint 37 OV-6c Event Trace Description OV-4 Organizational Relationships

38. Systems Viewpoint 38 SV-1 System Interface Description SV-10C Event Trace Description

39. Systems Viewpoint 39 SV-1 System Interface Description SV-10C Event Trace Description

40. PV-2 Project Timelines Project Viewpoint 40

41. DM2-Model Correlation 41 OV-6c Event Trace Description SV-1 System Interface Description OV-4 Organizational Relationships CV-2 Capability Taxonomy CV-1 Capability Vision SV-10C Event Trace Description PV-2 Project Timelines