DODA Exec Seminar

DoD Architecture FrameworkExecutive Seminar: 

DoD Architecture Framework Executive Seminar Maj Brian Hartt Air Force Institute of Technology

Topics: 

Topics Architecture Overview DoD Architecture Framework (DoDAF) Background Architecture Products—AOC Example Relevance to Requirements and Acquisition

Architecture Overview: 

Architecture Overview Why are we here?

What is an Architecture? : 

What is an Architecture? “The structure of components, their relationships, and the principles and guidelines governing their design and evolution over time.” - IEEE STD 610.12 as stated in the DoD Architecture Framework (DoDAF) Architecture is useful for designing unprecedented, complex systems

Architecting a House: 

Architecting a House When do you NOT need an architect? Simple site Existing design Existing subdivision When do you need an architect? Difficult site Unique design “Oneness” with the setting (i.e. integration) But, when do you REALLY need an architect?

When do you need an Architect?: 

When do you need an Architect? Planned community Integrated services Interoperable systems Efficient operations Complementary facilities

USAF’s Planned Community : 

USAF’s Planned Community

An Architecture hasMultiple Views*: 

Three major views (or perspectives) logically combine to describe an architecture Operational View (OV) Systems View (SV) Technical Standards View (TV) Views provide different perspectives on the same architecture *As Defined in the DoD Architectural Framework (DoDAF) An Architecture has Multiple Views*

Operational View (OV): 

Operational View (OV) The Citizens have the Operational View A Community operates as: Place to work, shop, entertain, … Place to raise a family Place to help neighbors Place to call home For the Citizens, the focus is on the ConOps; the infrastructure is taken for granted; the systems are expected to seamlessly interact and inter-operate

Systems View (SV): 

Systems View (SV) The Builder has the Systems View A Community is a system of systems: Electrical Water & Sewer Communications Roads Etc. For the Builder, the Community’s infrastructure is the main focus; the various systems and sub-systems must be carefully spec’ed, designed, and installed

Technical Standards View (TV): 

Technical Standards View (TV) The Builder and the Inspector have the Technical View Homes must comply with building codes and standards: National Electrical Code ANSI building standards IEEE electronics standards Codes, specs, and standards provide the foundation upon which every process and system in the Community is based

Summary of Views and Constraints: 

Summary of Views and Constraints System View (Builder) Physical Structure Design Principles, Reference Models and Rules Logical Operational View (Citizen) Intended Uses and Processes Conceptual Technical Standards View (Builder and Inspector) Building Codes / Standards Standardization (Components) Physical

All View (AV): 

All View (AV) The Architect has the All View The “Big Picture” Scope Purpose Intended users Environment Etc. The Architect must understand all the overarching aspects that relate to all three of the views

What is the DoDArchitecture Framework?: 

Framework is partitioned into three volumes: Volume I: Definitions and Guidelines Volume II: Product Descriptions Volume III: Deskbook Purpose of the DoD Architecture Framework, Version 1.0, is to: Define a common approach for developing, presenting, and integrating of DoD architecture descriptions What is the DoD Architecture Framework?

Framework History: 

1994 2004 Framework History 1996 1997 Evolving to a DOD instruction

DoD Architecture Framework -Scope: 

DoD Architecture Framework - Scope Framework defines architecture views: Operational Systems Technical Standards “All View” Products Each view is composed of sets of architecture information that are depicted via graphics, tables, or textual products

Architecture is Documented using Models: 

Architecture is Documented using Models A Model is worth 1000 pictures A1 A2 I2 I1 I3 Entity Name A1 A2 A3 Entity Name A1 A2 A3 Relationship Function 1 Function 2 Source A Sink X

DoD Framework Products(Format of Products): 

DoD Framework Products (Format of Products) OPERATIONAL (OV) SYSTEMS (SV) TECHNICAL (TV) CADM: Core Architecture Data Model ALL (AV)

DoD Framework Products(Format of Products): 

DoD Framework Products (Format of Products) OPERATIONAL (OV) SYSTEMS (SV) TECHNICAL (TV) CADM: Core Architecture Data Model ALL (AV)

Slide20: 

Architecture Example: Aerospace Operations Center (AOC) Why AOC? Unclassified—FOUO Complex environment Background The AOC is the JFACC’s weapon system for command & control of air and space forces Closely coordinated acquisition between ESC and AFC2ISRC

DoD Framework Products(Format of Products): 

DoD Framework Products (Format of Products) OPERATIONAL (OV) SYSTEMS (SV) TECHNICAL (TV) CADM: Core Architecture Data Model ALL (AV)

AV-1: Overview and Summary Information: 

AV-1: Overview and Summary Information Narrative description Overarching document guiding the architecture effort Defines scope, purpose, uses, analysis method, assumptions, products, context, tools and resources Read First

AV-1: Overview and Summary Information: 

AV-1: Overview and Summary Information Identification Architecture Title: Aerospace Operations Center (AOC) Block 10 (Simplified Example) Architects: ESC, AFC2ISR Center, and AFIT Purpose Problem Description: AOCs have not previously been baselined; units created their own AOCs according to various local methods and designs; AOCs were not a standardized, integrated weapon system. Purpose: AOC Block 10 sets a baseline “as is” architecture for a generic AOC; this supports ongoing AOC efforts, including contract RFP, weapon system integration and test, and future AOC development. Scope: This architecture depicts the evolution of a generic AOC and details the AOC high-level activities and major information exchanges.

AV-2: Integrated Dictionary: 

Glossary with definitions of terms used in the architecture Each item in the architecture should have a corresponding entry Dictionary should cross-reference all items AV-2: Integrated Dictionary

DoD Framework Products(Format of Products): 

DoD Framework Products (Format of Products) OPERATIONAL (OV) SYSTEMS (SV) TECHNICAL (TV) CADM: Core Architecture Data Model ALL (AV)

Operational ViewsDevelopment Sequence: 

Operational Views Development Sequence First Second Third Fourth OPERATIONAL (OV)

Slide27: 

OV-1: High-level Operational Concept Description Depicts AOC operational concept (key inputs, outputs, controls, and mechanisms) Provides text description of the ConOps Marketing brochure or “Archi-toon”

Slide28: 

OV-5: Operational Activity Model Conduct Dynamic-State Operations Conduct Steady-State Operations Conduct Air Operations Step 1: Functional Decomposition (structured similar to WBS)

Slide29: 

OV-5: Operational Activity Model Execute ATO Conduct Steady-State Operations Conduct Dynamic-State Operations Intelligence Strategic Plan Doctrine, ROE Operations Directions Dynamic Targeting Directions Step 2: Model the activity flow (aka IDEF0 model) Conduct Air Operations ATO Steady-State Plan

Slide30: 

OV-2: Operational Node Connectivity Description ATO Planning Cell ATO Execution Cell Air Operations Center Strategic Plan ATO Strat Intel Tac Intel Strategic Reconnaissance (Big Bird) Tactical Reconnaissance (Predator) Airborne Command & Control (AWACS) Shooter Operations Directions Dynamic Targeting Directions Air Intel OV-2 depicts nodes and high-level information flow (needlines) Note: “As Is” Architecture

Slide31: 

OV-3: Operational Information Exchange Matrix

DoD Framework Products(Format of Products): 

DoD Framework Products (Format of Products) OPERATIONAL (OV) SYSTEMS (SV) TECHNICAL (TV) CADM: Core Architecture Data Model ALL (AV)

Slide33: 

SV-1: System Interface Description

Slide34: 

SV-1: System Interface Description Note: For demonstration purposes, this chart depicts only the AOC and AWACS systems. (Other system nodes not shown)

Slide35: 

SV-2: System Communication Description Note: For demonstration purposes, this chart depicts only the AOC and AWACS systems. (Other system nodes not shown)

Slide36: 

SV-6: System Data Exchange Matrix

DoD Framework Products(Format of Products): 

DoD Framework Products (Format of Products) OPERATIONAL (OV) SYSTEMS (SV) TECHNICAL (TV) CADM: Core Architecture Data Model ALL (AV)

Slide38: 

TV-1: Technical Standards Profile C4ISR Domain

DoD Framework Products(Format of Products): 

DoD Framework Products (Format of Products) OPERATIONAL (OV) SYSTEMS (SV) TECHNICAL (TV) CADM: Core Architecture Data Model ALL (AV)

Architecture Product Relationships: 

Architecture Product Relationships Integrated Architecture (as described by Joint Staff/J8)

SEQUENCE OF PRODUCTS (from AMC): 

AV-1 SEQUENCE OF PRODUCTS (from AMC) OV-1 AV-2

SEQUENCE OF PRODUCTS (from AMC): 

AV-1 OV-1 OV-5 OV-3 OV-2 AV-2 OV-4 SEQUENCE OF PRODUCTS (from AMC)

SEQUENCE OF PRODUCTS (from AMC): 

AV-1 OV-1 OV-5 OV-3 OV-2 AV-2 OV-4 SV-5 SV-4 SV-1 SV-2 SV-3 SEQUENCE OF PRODUCTS (from AMC) TV-1

SEQUENCE OF PRODUCTS (from AMC): 

AV-1 OV-1 OV-5 OV-3 OV-2 OV-7 AV-2 OV-4 SV-5 SV-6 SV-4 SV-1 SV-11 SV-2 SV-3 TV-2 TV-1 SEQUENCE OF PRODUCTS (from AMC) OV-6c OV-6b OV-6a

SEQUENCE OF PRODUCTS (from AMC): 

AV-1 OV-1 OV-5 OV-3 OV-2 OV-7 AV-2 OV-4 SV-5 SV-6 SV-4 SV-1 SV-11 SV-2 SV-3 SV-8 SV-9 SV-7 TV-2 TV-1 SEQUENCE OF PRODUCTS (from AMC) OV-6c OV-6b OV-6a SV-10c SV-10b SV-10a

DoD Framework Products: 

AV-1 OV-1 OV-5 OV-2 AV-2 OV-4 SV-4 SV-1 SV-2 TV-1 DoD Framework Products Documents Legend Models

Requirements and Acquisition Process: 

Requirements and Acquisition Process

CJCSI 3170.01D Architecture Elements Summary: 

CJCSI 3170.01D Architecture Elements Summary

Slide49: 

CJCSI 3170.01D Architecture Elements Summary

Slide50: 

S1.1 S1 S2 S1.2 S2.1 S2.2 A1 A2 A3 C A2.1 A2.2 A3.1 A1.1 A1.2 A3.2 S3.1 S3.2 Activities Capability Nodes Systems Functions $/PEs OVs SVs Architecture & Capabilities Node Financial Data Node $ $ $ for Acquisition, Personnel, TTP Changes,... $

https://afkm.wpafb.af.milSearch for “Architecture Training CoP”: 

https://afkm.wpafb.af.mil Search for “Architecture Training CoP” DoDAF Download Site Workshop (short course)

Executive Summary: 

Executive Summary Summary:  In a net-centric warfighting environment, there is a great need for integration and interoperability in order to achieve warfighting capabilities.  Integrated architectures are central to the DoD approach, and the DoD Architecture Framework is the playbook for integrated architectures.   This seminar will introduce the basic concepts of architecture and explain the most common Operational Views (OVs), System Views (SVs), and Technical Views (TVs).  These views are required by the three capabilities documents (ICDs, CDDs, and CPDs) and have great relevance to the requirements and acquisitions communities.