1. 1 Fit For Purpose Example Capability Analysis 11 May 2010 Shelton Lee (Contractor) Architecture, Standards & Interoperability Directorate Office of the DoD Deputy Chief Information Officer shelton.lee@lmco.com

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

3. Methodology: DoDAF V2.0 Six-Step Architecture Development Process 3 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 Architect Subject Matter Experts

4. What is a Capability “The ability to achieve a desired effect under specified standards and conditions through combinations of means and ways across DOTMLPF to perform a set of tasks to execute a specified course of action.” 4 Source: CJCSI 3170.01G, Joint Capabilities Integration and Development System

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

6. Determine Data Required 6 Immersion in cold water can quickly numb the extremities to the point of uselessness. Cold hands cannot fasten the straps of a lifejacket, grasp a thrown rescue line, or hold onto an over-turned boat. Within minutes, severe pain clouds rational thought. And, finally, hypothermia (exposure) sets in, and without rescue and proper first aid treatment, unconsciousness and death Normal body temperature of course, is 98.6. Shivering and the sensation of cold can begin when the body temperature lowers to approximately 96.5. Amnesia can begin to set in at approximately 94, unconsciousness at 86 and death at approximately 79 degrees.

7. Search & Rescue Concept of Operations 7 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.

8. Search & Rescue As-Is State & Problem Statement 8 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

9. Search & Rescue To-Be State & Desired Operational Outcome 9 Goal: Achieve a Rescue Rate of 100 percent in high sea states of 10 or less

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

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

12. Alternative 2 – Materiel Solution 12 Alternative 2 is a materiel solution – improved jumpsuit for pilots Capability decomposed into a SV-1 showing Pilot equipped with new Waterproof Thermal Jumpsuit

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

14. Alternative 3 – OV-6c Event Trace 14 OV-6c Event Trace Model used to capture new sequencing Used to determine Measure of Effectiveness of new capability

15. Alternative 1 – Target Process Flow 15 OV-6c Event Trace Description used to capture new process flow Could be simulated to determine Search Time, Rescue Time, etc.

16. Alternative 2 – Materiel Solution 16 Source: Mr. Peter Gibbs, Q.G.A. Survival Systems Ltd. Dartmouth, Nova Scotia

17. Alternative 3 – Major System Solution 17 Source: Dr. C.J. Brooks Survival Systems Ltd. Dartmouth, Nova Scotia

18. Measure Guidelines: 18 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

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

20. Fit For Purpose Views 20 Observations: Alternative 1 presents the highest Risk Factor but also the highest “Feasibility Level” Alternative 3 the lowest Risk Factor but lowest Feasibility Level

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

22. Capability Metrics 22 Using Measure/Measure Type Capture Capability Metrics in a matrix format This is based on as-is and/or to-be architecture descr Provides basis for quantitative analysis Capabilities across the top Measure Type on the side Measure and UoM in cells

23. Fit for Purpose CV-2 Model 23 CV-2 Capability Taxonomy view with FfP Dashboard Indicators High-low status bars, “speedometer” gauges aid in AoA

24. Capability-Based Assessment (CBA) 24 If a Capability-Based Assessment (CBA) is available, the measures development process should leverage information already developed as a part of the JCIDS process. The CBA identifies scenarios, military objectives, mission outcomes, associated desired effects, and task representations. This process lines up well with the JMT construct and the Senior Warfighters Forum (SWarF) prioritized list of capability attributes (Table 3) for battlespace awareness, command and control, logistics, and net-centric capabilities.