dod ea conference dodaf in action
DESCRIPTION
DoDAF architecture example using a functional “thread” of Search and Rescue (SAR) conceptProvides an architectural example of DoDAF 2.0 in Action using a real world constructShows how architectural analysis can answer SAR Program Management questions.TRANSCRIPT
![Page 1: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/1.jpg)
DoDAF 2.0In ActionIn Action
Search and Rescue (SAR) Example User Experience and Analysis
Presented by Shelton Lee
Paul Johnson11 April 2011
![Page 2: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/2.jpg)
• Search and Rescue (SAR) Example Overview
• Why SAR as an Example? • SAR Scenario Perspective• SAR Scenario Trigger• DoDAF Development Process• SAR Analysis• Conclusion and Recommendations
Contents
04/09/23 2DoD Enterprise Architecture Conference
![Page 3: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/3.jpg)
• DoDAF architecture example using a functional “thread” of Search and Rescue (SAR) concept
• Provides an architectural example of DoDAF 2.0 in Action using a real world construct
• Shows how architectural analysis can answer SAR Program Management questions
• Limited to United States Coast Guard SAR
• Focused on “search” aspect of SAR only
• Defined using current (as-is) capabilities• Data used throughout for illustrative purpose only
Search and Rescue (SAR) Example Overview
04/09/23 3DoD Enterprise Architecture Conference
![Page 4: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/4.jpg)
• Publicly and freely available information to support detailed architecture
• Universally understood concept performed and supported worldwide
• Enough information to support all relevant DoDAF 2.0 views
• Concept contains real world problems that can be solved with architecture
Why SAR as an Example?
04/09/23 4DoD Enterprise Architecture Conference
Complete example uses most of the DoDAF 2.0 views to describe SAR – demonstration only shows one small “thread”
![Page 5: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/5.jpg)
• SAR scenario will be accomplished through several roles in context of Program Management
• Two primary roles will exchange information:• SAR Program Manager (PM)• SAR Enterprise Architect (EA)
• Demonstration will alternate between static presentation and interactive product display
SAR Scenario Perspective
04/09/23 5DoD Enterprise Architecture Conference
Other roles are typically necessary to complete a fully integrated enterprise architecture but will not be addressed for demonstration
![Page 6: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/6.jpg)
SAR Scenario Trigger – Problem Statement
04/09/23 6DoD Enterprise Architecture Conference
Rescuing the Coast Guard From Chronically Low BudgetJuly 2010 By Stew Magnuson National Defense Magazine article
“Everyone loves the Coast Guard, but that affection hasn’t translated into a budget that can sustain its ships, aircraft and personnel”
The service (USCG) saw its proposed 2011 budget cut by 3 percent.
![Page 7: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/7.jpg)
• Problem statement triggered conversation between PM and EA teams
• Enterprise architecture team recommended using latest version of framework - DoDAF 2.0
• DoDAF six-step process recommended as best practice by enterprise architecture team
• Collaborative efforts were undertaken between:• Program Management Team• Enterprise Architecture Team• Operational Team• System and Engineering Team
SAR Scenario
04/09/23 7DoD Enterprise Architecture Conference
![Page 8: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/8.jpg)
1. Determine Intended Use of architecture
2. Determine Scope of architecture
3. Determine Data Required to support architecture development
4. Collect, Organize, Correlate, & Store architectural data
5. Conduct Analyses in support of architecture objectives
6. Document Results in accordance with decision-maker needs
DoDAF Six-Step Development Process
04/09/23 8DoD Enterprise Architecture Conference
![Page 9: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/9.jpg)
• Find ways we can reduce cost to meet new budget restrictions using enterprise architecture data
• Use analysis methods for time and cost
• Examine data and dependencies of “search”
• What is highest value that could be gained for this effort?
• Build “search” architecture outwards
• Establish foundation for future optimization
Step 1 - Determine Intended Use of Architecture
04/09/23 9DoD Enterprise Architecture Conference
Our primary intent is to understand costs associated with “search” and look for any anomalies that may reveal a way to cut costs without reducing efficiency…
![Page 10: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/10.jpg)
• Excerpt from Overview and Summary Information (AV-1)
Purpose Excerpt from Overview and Summary Information (AV-1)
04/09/23 10DoD Enterprise Architecture Conference
Architecture OverviewThis architecture is scoped to the USCG SAR mission and specifically to events immediately following an incident up to the administrative closure of the response effort. This will present an opportunity to demonstrate how systems and people act together to accomplish this mission while data associated with these actions will expose utility, value and opportunities for improved performance.
![Page 11: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/11.jpg)
• Limit to Coast Guard specific SAR• Focus on “search” aspect of SAR through
capability and functional analysis• Define AS-IS (current only) capabilities• Identify and focus on elements that have a
high cost (time and money)
Step 2 - Determine Scope of Architecture
04/09/23 11DoD Enterprise Architecture Conference
• Phase 1 of EA development will provide enough “depth” to discover possible vulnerabilities that require future optimization
![Page 12: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/12.jpg)
• Definition: Scenario from a conceptual level. • Main operational concepts
• System and operational (human) interaction
• Data Sources: Mission Statement, Policy Document, Subject Matter Expert (SME) Interview, Concept of Operations (CONOPs), Tactic, Technique and Procedure, Operational Requirement Document
• Purpose: Provide high-level description of what the architecture is supposed to do and how it is supposed to do it.
• Analysis: Find costly and burdensome capabilities that others are dependent upon for speed and reliability
• Consumers:• Executive Level Stakeholder
• Enterprise Architect
• Program Manager
• General Stakeholder
High Level Operational Concept Graphic (OV-1)
04/09/23 12DoD Enterprise Architecture Conference
![Page 13: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/13.jpg)
SAR High Level Operational Concept Graphic (OV-1)
04/09/23 13DoD Enterprise Architecture Conference
![Page 14: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/14.jpg)
• Disaster occurs (person is in distress)• Emergency beacon is activated• Signal is picked up by other ships and
satellites• Signal received by Mission Control Center• Search team analyzes signal for location• Rescue Coordination Center dispatches
search and rescue team• Debrief and “lessons learned”
High Level Operational Concept Graphic (OV-1)
04/09/23 14DoD Enterprise Architecture Conference
![Page 15: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/15.jpg)
Step 3 - Determine Data Required to Support Architecture Development
04/09/23 15DoD Enterprise Architecture Conference
Reason Data Required
Understand high level context for scope Capabilities and Functions of Scope
Knowledge of how “search” capabilities are conducted by human functions
Human Processes and Rules regarding “search” specific functions
Provide static source to pinpoint high cost functional area(s) of human and system process
Data for cost and time of both acting together
Understand high level system functions and how they support process and rule
Systems and their designed System Functions
Knowledge of how “search” is conducted by systems and their system functions
“Search” specific System Processes and Rules
![Page 16: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/16.jpg)
• Operational (Human) Process (OV-6)• Human Processes, Rules and Data
• System Process (SV-10)• System Processes, Rules and Data
Step 3 - Determine Artifacts Required to Support Architecture Development
04/09/23 16DoD Enterprise Architecture Conference
A number of other supportive views were created to understand and define the entire SAR program – only ones relevant to the demonstration thread are listed
•Overview and Summary Information (AV-1)•Scope, Goals and Purpose
•Capability Vision (CV-1)•Goals, Purpose, and Capability dependencies
• Capability to Activity Map (CV-6)• Capability and Functions of Scope
•Capability Taxonomy (CV-2)•Capability Dependencies
![Page 17: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/17.jpg)
• Description: Describes a Project's Visions, Goals, Objectives, Plans, Activities, Events, Conditions, Measures, Outcomes, and produced objects.
• Purpose:
• Explains need for architecture and what it should demonstrate• Defines types of analyses and who is expected to perform analyses• Relates decisions expected to be made on basis of an analysis and
resultant actions
• Data Sources: Policy Document, Subject Matter Expert (SME) Interview, Concepts of Operations (CONOPs), Tactic, Technique and Procedure, Operational Requirement Document
• Analysis: Determine level of effort required to produce product set to answer architectural questions
• Consumers:
• Executive Level Stakeholder• Enterprise Architect• Program Manager• General Stakeholder
Overview and Summary Information (AV-1)
04/09/23 17DoD Enterprise Architecture Conference
![Page 18: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/18.jpg)
SAR Overview and Summary Information (AV-1)
04/09/23 18DoD Enterprise Architecture Conference
![Page 19: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/19.jpg)
SAR Overview and Summary Information Graphical Example
04/09/23 19DoD Enterprise Architecture Conference
Overview
Goal
Vision
View
Architecture Development Phase
Purpose: Enable readers to understand the scope of the EA effort through graphic visualization of the vision, goals, overview and the views contained in each development phase.
![Page 20: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/20.jpg)
• ScenarioThe scenario for this example begins with an event resulting in the activation of a beacon. The particular beacon used will affect the time required to receive and transmit the signal to a Local User Terminal and onward to a Mission Control Center where it may be validated. Once validated the signal is the basis of a satellite based search for the “person in distress”. Here again , time delays may result because of the beacon used. The “person in distress” is located, rescued and returned to the Mission Control Center where the SAR mission is administratively closed.
• PurposeThe EPIRB (Emergency Position Indicating Radio Beacon) for 121 MHz are being phased out and 406 MHz are becoming the standard for search and rescue (SAR) throughout the world. This system change will affect the way SAR is conducted primarily from a search perspective.
• DescriptionThis release and subsequent releases will describe USCG Search and Rescue (SAR) mission with enough details to optimize performance and reduce costs for SAR.
• OverviewThis architecture is scoped to the USCG SAR mission and specifically to events immediately following an incident up to the administrative closure of the response effort. This will present an opportunity to demonstrate how systems and people act together to accomplish this mission while data associated with these actions will expose utility, value and opportunities for improved performance.
SAR Overview and Summary Information (AV-1)
04/09/23 20DoD Enterprise Architecture Conference
![Page 21: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/21.jpg)
• Data was collected using tools that can capture all data to support DoDAF 2.0 views
• Worked with operational and system team to gather information to create views
Step 4 - Collect, Organize, Correlate, and Store Architectural Data
04/09/23 21DoD Enterprise Architecture Conference
• Data was stored in a repository that supports robust storage and analytical capabilities
• Data was collected through screen entry and import
![Page 22: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/22.jpg)
• Definition: Overall vision for transformational endeavors, which provides a strategic context for capabilities described and high-level scope.
• Data Sources: Policy Document, Subject Matter Expert (SME) Interview, Concept of Operations (CONOPs), Tactic, Technique & Procedure, Operational Requirement Document
• Purpose: Provide strategic context for capabilities described in Architectural Description and communicates strategic vision regarding capability structure
• Analysis: Vision to goals with supportive capability
• Consumers:• Decision maker• Enterprise Architect
Capability Vision (CV-1)
04/09/23 22DoD Enterprise Architecture Conference
![Page 23: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/23.jpg)
SAR Capability Vision (CV-1)
04/09/23 23DoD Enterprise Architecture Conference
Capability
Goal
Guidance
Vision
Purpose: Understand relationships between SAR vision , goals and supportive capability
Focus for “thread”
![Page 24: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/24.jpg)
• 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
SAR Capability Vision (CV-1)
04/09/23 24DoD Enterprise Architecture Conference
Focus for “thread”
![Page 25: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/25.jpg)
• Definition: Hierarchy of capabilities decomposed down to leaf level to categorize 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
Capability Taxonomy (CV-2)
04/09/23 25DoD Enterprise Architecture Conference
![Page 26: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/26.jpg)
SAR Capability Taxonomy(CV-2)
04/09/23 26DoD Enterprise Architecture Conference
Purpose: Understand SAR capabilities in context of each other and note any anomalies that are exposed through attributed “data graphics”.
Focus for Scenario: Locate Person in Distress
Capability
Leaf Capability
Time and cost data is for illustrative purpose only and does not reflect real values.
![Page 27: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/27.jpg)
• Execute SAR (Capability)• Operate SAR Mission (Capability)
• Locate Person in Distress (Capability)• Support Person in Distress (Capability)• Conduct Recovery (Capability)
SAR Capability Taxonomy(CV-2)
04/09/23 27DoD Enterprise Architecture Conference
Highest level Capability (root)
Lower level Capability (child/parent)
Focus for Scenario (leaf)
The border between capability and operational activity is defined at leaf level. Capabilities structure categories of activities independent of processes at an implementation.
![Page 28: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/28.jpg)
• Definition: Captures capabilities required and activities that enable those capabilities.
• Purpose: • Shows leaf level capabilities.
• Aligns leaf level capabilities with supporting activities
• Provides categorization and 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
Capability To Operational Activity (CV-6)
04/09/23 28DoD Enterprise Architecture Conference
![Page 29: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/29.jpg)
SAR Capability to Operational Activity (CV-6)
04/09/23 29DoD Enterprise Architecture Conference
Most expensive activity
Capability
Purpose: Express leaf level capabilities and their supporting operational activities.
Leaf –level Capability relates to Operational Activity
Time and cost data is for illustrative purpose only and does not reflect real values.
![Page 30: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/30.jpg)
• 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)• Increase Situational Awareness (Activity)• Deliver Supply (Activity)
• Conduct Recovery(Capability)• Deploy Recovery Team (Activity)• Recover Person in Distress (Activity)• Authenticate Person in Distress (Activity)
SAR Capability to Operational Activity (CV-6)
04/09/23 30DoD Enterprise Architecture Conference
Most expensive activity
![Page 31: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/31.jpg)
• “Fit for purpose” view to support relation of Activity to supportive Processes (one to many)
• One Activity may support or describe many Processes
• Each Process model supports different ways of performing each Activity
Activity to Process Map (FFP)
04/09/23 31DoD Enterprise Architecture Conference
![Page 32: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/32.jpg)
Activity to Process Map (FFP)
04/09/23 32DoD Enterprise Architecture Conference
ProcessModel(s)
Most expensive process
Purpose: Show relationships between activities and processes.
Time and cost data is for illustrative purpose only and does not reflect real values.
Pragmatica Innovations
![Page 33: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/33.jpg)
• Definition: Models the timing and sequencing of events that capture operational behavior of an process or function.
• Purpose: Traces actions in a scenario or sequence of events• Data Sources: Subject Matter Expert (SME) Interview, Concept of
Operations (CONOPs), Tactic, Technique and Procedure, Operational Requirement Document
• Analysis:• Cost and timing of process
• Process dependency on logical data and state changes
• Consumers:• Enterprise Architect
• Program Manager
• General Stakeholder
Operational (Human) Process Model (OV-6)
04/09/23 33DoD Enterprise Architecture Conference
![Page 34: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/34.jpg)
SAR Operational Process Model – Perform SARSAT Search (OV-6)
04/09/23 34DoD Enterprise Architecture Conference
Using supportive data (as mandated in DoDAF 2.0) we can see this process seems to be taking too long and thus costing too much money.
Process
Most expensive process
Gateway
Human(s) represented as Pool
Time and cost data is for illustrative purpose only and does not reflect real values.
Supportive Data
![Page 35: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/35.jpg)
• Deploy Direction Finding Team• Track Signal
• Emergency beacons of varying frequencies are used by victims to aid the coast guard in finding them.
• Determine Search Area• If search area is small then (determined in another process)
• Search small area ($25,000, 10 hours)
• If search area is large then (determined in another process)• Search large area ($100,000, 54 hours)
• Search for Distressed Victims• Is Person in Distress Located?
• Person in Distress is located
• Person in Distress is not located
SAR Operational Process Model - Perform SARSAT Search (OV-6)
04/09/23 35DoD Enterprise Architecture Conference
![Page 36: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/36.jpg)
• Analysis revealed that “problem” was not in operational (human) process but possibly a system or system process problem
• Had to move “through” the architecture to understand source of problem• Large area resulted from Determine Search Area
Process• Based on ability to track signal• Type of signal was based on type of satellite• Analysis performed on systems related to costs
Enterprise Architecture Analysis
04/09/23 36DoD Enterprise Architecture Conference
![Page 37: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/37.jpg)
• Definition: Defines system scenario from a logical level with system and system process interaction
• Data Sources: Subject Matter Expert (SME) Interview, Concept of Operations (CONOPs), Tactics, Techniques and Procedures, Operational Requirement Documents
• Purpose: Provide system process interaction
• Analysis: System process cost and time analysis. Resource impact analysis. System Behavioral analysis. Identification of non-functional system requirements
• Consumers:• Enterprise Architect• Program Manager• General Stakeholder
System Process (SV-10)
04/09/23 37DoD Enterprise Architecture Conference
![Page 38: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/38.jpg)
SAR System Process – Monitor Distress Signal (SV-10)
04/09/23 38DoD Enterprise Architecture Conference
Looking at systems involved in this process we can see that the system (EPIRB) seems to be the root cause –specifically the 121 MHz beacon.
Process
Most complex path
Data Object
Gateway
System(s) represented as “Lane”
Time and cost data is for illustrative purpose only and does not reflect real values.
![Page 39: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/39.jpg)
SAR System Process –Monitor Distress Signal (SV-10)
• Start Monitor Distress Signal • Select Beacon?
• Transmit 121.5 MHz Signal • LEOSAR in Range?
• Repeat 121.5 Signal• LUT in Range?
• LUT Receive Signal• Confirm Signal?
• LUT Transmit Signal
![Page 40: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/40.jpg)
• Multiple types of analyses are available to an architectural effort with two primary categories:• Static analysis leverages model structure and attributes to
derive qualitative, quantitative and functional analyses• Dynamic analysis (executable models) examine temporal,
spatial, or other performance aspects of a solution through dynamic simulations
• Static analyses were performed using analysis tools through database queries for function and quantity
Step 5 – Conduct Analysis in Support of Architecture Objective
04/09/23 40DoD Enterprise Architecture Conference
![Page 41: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/41.jpg)
• Quantitative analysis was performed across entire architecture to discover the process where anomaly first appears - Perform SARSAT Search
• Looked at process from human and system side which are both tied to the same operational activity
• Problem was revealed in system view analysis - specifically radio beacons (121.5 and 406 MHz)
Step 5 – Conduct Analysis in Support of Architecture Objective
04/09/23 41DoD Enterprise Architecture Conference
![Page 42: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/42.jpg)
• Many types of static analyses are available using architectural data
• Two specific types were chose to best represent our SAR example problem • Process Analysis
• Operational from cost & time perspective• System from an efficiency perspective
• SWOT (Strength, Weakness, Opportunity and Threat)
• 121.5 MHz beacon (EPIRB)• 406 MHz beacon (EPIRB)
Step 5 – Conduct Analysis in Support of Architecture Objective
04/09/23 42DoD Enterprise Architecture Conference
![Page 43: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/43.jpg)
Process Analysis(Cost and Time)
04/09/23 43DoD Enterprise Architecture Conference
121.5 MHz beacon search costs $103,000 and takes 55 hours to locate versus $28,500 and 11 hours to locate when using 406 MHz version
Time and cost data is for illustrative purpose only and does not reflect real values.
121.5MHzCost
406 MHzCost
121.5MHzTime
406 MHzTime
![Page 44: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/44.jpg)
SWOT Analysis
04/09/23 44DoD Enterprise Architecture Conference
Strength Weakness Opportunity Threat
121.5 MHz EPIRB
•Cheap to purchase•Light weight•Trusted technology
•Ineffective •Reduced range
•Salvage for parts•Recycle plastic•Investigate reuse?
•Very expensive to search•Increased chance of not locating victim in time
406 MHz EPIRB
•Instant pickup •Identifying information•More powerful signal•Transmits longer period of time
•Cost more•Heavier weight•Bulkier
•More lives saved•Reduced cost of searching
•No migration plan•Impacts to general public if mandated for use
![Page 45: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/45.jpg)
• Results were documented using DoDAF 2.0 artifacts and supportive data
• Architecture structured and reflected solution for analysis
• Architecture presented requirements for change through updates in the architecture – the “to-be” or future state
Step 6 - Document Results In Accordance With Decision-Maker Need
04/09/23 45DoD Enterprise Architecture Conference
![Page 46: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/46.jpg)
• Updated views and new views to present the way forward...
Phase 2 of SAR Architecture Development
04/09/23 46DoD Enterprise Architecture Conference
![Page 47: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/47.jpg)
• Conclusion • 121.5Mhz beacons cost more time and money to
locate
• Recommendations• Phase out older 121.5mhz beacon technology• Change & implement new system standards
Conclusion and Recommendations
04/09/23 47DoD Enterprise Architecture Conference
![Page 48: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/48.jpg)
48
“DoDAF in Action” booth is at T5 for complete details of SAR Example
DoD booth is at T1 for details or DoDAF general questions
DoD booth is at T4 for government representative
Complete SAR enterprise architecture is also available at http://DoDAFinAction.com
Questions?
![Page 49: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/49.jpg)
Contact Information
Shelton LeeOffice: 703-916-7340Mobile: 703-973-4274
04/09/23 49
Paul W. JohnsonOffice: 757-575-5243
Mobile: [email protected]
DoD Enterprise Architecture Conference
![Page 50: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/50.jpg)
Backup Slides
• Following slides are backup and supporting information
![Page 51: DOD EA conference DoDAF in Action](https://reader033.vdocuments.site/reader033/viewer/2022061201/547a4605b4af9fe7318b482f/html5/thumbnails/51.jpg)
Quality Assurance
• Architecture completeness - existing views compared to projected views in AV-1, object counts,
• Architecture validation – diagram counts and information compared to compliances such as JCIDS
• Object completeness – completeness of data attribute information
• Object connectedness – relationships between objects, count, average, lack of relationships
• Object correctness – validation of information vs sources, reference source tracking