Breakout Session Exploring the Differences between Enterprise and System s A Look at the Different Methods, Tools, and Techniques James Martin Kevin Kreitman Jeff Diehl Scott Bernard Slide 1
Abstract Point: Most of the ground system architectures for military systems use the DOD Framework (DODAF). Counterpoint: It might be more appropriate in many cases to use the Federal Enterprise Framework (FEAF) or perhaps even a different framework. This panel will explore the different approaches to architectural modeling of enterprises (like FEAF) versus warfighting systems (per DODAF). We will look at case studies where FEAF and DODAF have been applied and extract lessons learned to determine when each framework is appropriate. We will develop the selection criteria to assist in the planning stages of an architecture task for determining the best one or more frameworks to use. Slide 2
Enterprise Example Slide 3
DODAF Example Slide 4
Potential Work Items Definitions System Enterprise (System) (Enterprise) Architectural Goals Enterprise Architecting Systems Architecting Framework Benefits DODAF FEAF Others? Case Studies NOAA AFSCN Others? Lessons Learned For above and others Selection Criteria Key attributes of each framework Key drivers of architecture Slide 5
Topics 1. 1. Introductions 2. 2. DOD Framework 3. 3. Federal Enterprise Framework 4. 4. Air Force Enterprise Framework 5. 5. Discussion Slide 6
Introductions Background Development (mainly) Military Other Technology Domain Space Airplane Avionics Ground Communications Business Domain Commercial Aerospace Defense Other Government Other Discipline Systems Engineering Software Engineering Hardware Engineering Other Job Responsibility Management Architecting Engineering Other Level Enterprise Mission Program System Software Slide 7
A view represents the whole system from a particular viewpoint Reduces perceived complexity through separation of concerns views are an end result of doing architecting An has Multiple Views Family Usage (Operational) Plumbing View (System) Plumbing Code (Technical) Slide 8
The Three Main Views in the DOD Framework Slide 9
View Type All Views Operational Systems Technical Framework Product AV-1 AV-2 OV-1 OV-2 OV-3 OV-4 OV-5 OV-6a OV-6b OV-6c OV-7 SV-1 SV-2 SV-3 SV-4 SV-5 SV-6 SV-7 SV-8 SV-9 SV-10a SV-10b SV-10c SV-11 TV-1 TV-2 Framework Product Name Overview and Summary Information Integrated Dictionary High-Level Operational Concept Graphic Operational Node Connectivity Description Operational Information Exchange Matrix Organizational Relationships Chart Operational Activity Model Operational Rules Model Operational State Transition Description Operational Event-Trace Description Logical Data Model Systems Interface Description Systems Communications Description Systems-Systems Matrix Systems Functionality Description Operational Activity to Systems Function Traceability Matrix Systems Data Exchange Matrix Systems Performance Parameters Matrix Systems Evolution Description Systems Technology Forecast Systems Rules Model Systems State Transition Description Systems Event-Trace Description Physical Schema Technical Standards Profile Technical Standards Forecast Slide 10
Tiered Hierarchy of s TIER 0 National / Int l s US, NATO, Other Countries TIER 1 Department / Federal s DOD, IC, HLS, DOC, DOT, TIER 2 Cmd/Service/Agency s Air Force, Army, Navy, TIER 3 Mission Area / X-MA s Space, Wx, Combat Ops, Mobility, TIER 4 Program / Node s MILSTAR, AFSCN, AOC, Enterprise s s for Mission Areas, Programs, Nodes & Systems Slide 11
Air Force & Federal Frameworks are the Context for DODAF Federal Enterprise Framework (FEAF) Air Force EAF DODAF Slide 12
The FEAF Components DODAF Technical View DODAF Operational View Standards Business Drivers Technology Drivers Business Technology Business Models Sub- Models Business Technology Strategic Direction DODAF Systems View Current Segments Models Target Transitional Processes Slide 13
OMB s Family of Reference Models The Federal Enterprise (FEA) is being constructed through a collection of inter-related reference models designed to facilitate cross-agency analysis and opportunities for collaboration Business-Driven Approach Performance Reference Model (PRM) Government-wide Performance Measures & Outcomes Line of Business-Specific Performance Measures & Outcomes Business Reference Model (BRM) Lines of Business Agencies, Customers, Partners Service Component Reference Model (SRM) Capabilities and Functionality Services and Access Channels Data Reference Model (DRM) Business-focused data standardization Cross-Agency Information exchanges Technical Reference Model (TRM) Component-Based Published TBD IT Services Standards Source: Enterprise : Your Blueprint for Transformation Norman Lorentz, OMB, Chief Technology Officer October 7-8, 2002 Slide 14
The FEA Business Reference Model (BRM), V. 1.0 Web Services Telephone -Voice -Interactive E-system to System Public/Private Partnerships Fax Kiosk Face to Face Mail Governmentto-Citizen Access Channels Business Areas Lines of Business Internal Lines of Business Sub-Functions (pictured on following pages) Web Services Program Admin Public Asset Management Marketable Asset Management Defense & Nat l Security Ops Diplomacy & Foreign Relations Disaster Management Domestic Economy Education Energy Management Insurance Public Health Recreation & National Resources Social Services R&D & Science Telephone -Voice -Interactive Services to to Citizens E-system to System Public/Private Partnerships Fax Kiosk Compliance Regulated Regulated Activity Activity Approval Approval Consumer Safety Safety Environmental Management Law Law Enforcement Legal Revenue Revenue Collection Collection Trade Trade (Import/Export) (Import/Export) Transportation Transportation Workforce Workforce Management Management Face to Face Mail Employeeto-Employee Access Channels Legislative Management Business Management of Information IT Management Planning and Resource Allocation Regulatory Management Support Delivery of Services Controls and Oversight Public Affairs Internal Risk Management and Mitigation Federal Financial Assistance Inter-Agency Internal Operations / Infrastructure Intra-Agency Human Resources, Financial Management Admin Supply Chain Management Human Resources, Financial Management Admin Supply Chain Management Source: Enterprise : Your Blueprint for Transformation Norman Lorentz, OMB, Chief Technology Officer October 7-8, 2002 Slide 15
The AF ENTERPRISE (a (a mission area decomposition) THE THE AF AF ENTERPRISE SPACE SPACE COMBAT OPS COMBAT OPS ISR ISR MOBILITY WEATHER MOBILITY WEATHER AIR TRAFFIC AIR TRAFFIC MGMT MGMT SPECIAL OPS SPECIAL OPS INFOSTRUCTURE INFOSTRUCTURE INFO MGMT INFO MGMT INFO ASSURANCE INFO ASSURANCE TRANSPORT/COMPUTING TRANSPORT/COMPUTING MODELLING/SIMULATION MODELLING/SIMULATION COMBAT & BUSINESS COMBAT & BUSINESS SUPP ORT SUPP ORT CON- TRACT CON- TRACT FINANCIAL SERVICES ACQUISITION FINANCIAL SERVICES ACQUISITION COMPTROLLER ACQUISITION COMPTROLLER ACQUISITION LEGAL SERVICES CONTRACTING LEGAL SERVICES CONTRACTING = MISSION AREAS = MISSION AREAS PERSONNEL AFFAIRS PERSONNEL AFFAIRS PERSONNEL HEALTH PERSONNEL SERVICES CHAPLAIN HEALTH SERVICES PUBLIC CHAPLAIN AFFAIRS QUALITY PUBLIC & AFFAIRS MANPOWER QUALITY & MANPOWER SOURCE: Enterprise Architecting, AF-CIO/A, Aug 02 LOGISTICS LOGISTICS MATERIAL MGMT LOGISTICS MATERIAL PLANS MGMT CIVIL LOGISTICS ENGINEERING PLANS SERVICES CIVIL ENGINEERING MUNITIONS SERVICES TRANSPORTATION MUNITIONS SUPPLY TRANSPORTATION MAINTENANCE SUPPLY MAINTENANCE 7 7 Slide 16
Air Force Enterprise Framework AF Enterprise Descriptions Drivers & Inputs Inputs Perspectives Air Force Reference Models Mission Area & Cross Mission Area Views Views & Products & Products Program & Node Views Views & Products & Products Uses Uses & Impacts Ref: Air Force Enterprise Framework (AF-EAF), AF Chief Architect s Office, DRAFT v1.5 (25 April 2003) Slide 17
AF-EAF Inputs & Outputs Drivers & Inputs GOVERNANCE & GUIDANCE Legislation (e.g. CCA) Directives, Policy & Instructions Air Force Arch Guidance & Charters ARCHITECTURE INPUTS Strategic Vision & Plans CONOPS & Capabilities Requirements (e.g. ORDs) Task Lists (e.g. AFTL, UJTL) External (e.g. GIG Arch.) Other Mission, Business, & System Info Perspectives AF Enterprise Descriptions Air Force Reference Models Mission Area & Cross Mission Area Views & Views & Products Products Program Node Program & Node Views & Views & Products Products Uses & Impacts PPBS Process Joint Capabilities Integration & Development Acquisition Planning & Operations EA Life Cycle Process Other Uses Ref: Air Force Enterprise Framework (AF-EAF), AF Chief Architect s Office, DRAFT v1.5 (25 April 2003) Slide 18
Relationship to FEAF and DODAF Relevant Frameworks Federal Enterprise Framework (FEAF) DOD Framework (DODAF) Perspectives AF Enterprise Descriptions Air Force Reference Models Mission Area & Cross Mission Area Views Views & Products & Products Program & Node Views Views & Products & Products Relevant Reference Models & Views Five Reference Models (Adapted from FEAF) Operational View Technical View System View Ref: Air Force Enterprise Framework (AF-EAF), AF Chief Architect s Office, DRAFT v1.5 (25 April 2003) Slide 19
Example s at Different Levels TIER 0 National / Int l s US, NATO, Other Countries Integrated Global Environmental Observing System (IGEOS) TIER 1 Department / Federal s DOD, IC, HLS, DOC, DOT, TIER 2 Cmd/Service/Agency s Air Force, Army, Navy, TIER 3 Mission Area / X-MA s Space, Wx, Combat Ops, Mobility, Global Information Grid (GIG) AF Space & C4ISR Conops NOAA Observing System (NOSA) Combat Operations Mission Area Spacelift Mission Area TIER 4 Program / Node s MILSTAR, AFSCN, AOC, Integrated Overhead Sigint (IOSA) SBR, SBIRS, SBSS, MilSatCom, Slide 20
Mapping from 5-Tier Hierarchy to Air Force-EAF Perspectives Slide 21
DOD Enterprise s are Nested into Higher Level s Air Force Enterprise Mission Areas Nodes Systems Systems Systems Systems Systems Systems WARNING: at a higher level is the intersection of lower levels, NOT the union of lower levels. Slide 22
Discussion What are the different objectives at the different tiers of architecture? Federal and Department Service and Agency Mission Area Program and Node What are the pros and cons of each architecture framework? Federal DOD Air Force Home Grown? Slide 23