Workshop for ACT – IAC, EA-SIG Mr. David McDaniel (ctr) 20 July 2012

Slides:



Advertisements
Similar presentations
1 Information Enterprise Architecture v September Walt Okon Senior Architect Engineer Senior Architect Engineer for Information Sharing Enterprise.
Advertisements

DoD Architectures and Systems Engineering Integration
DoDAF V2.0 Community Update Overview
DoD Information Enterprise Architecture v2.0
C2 Integration Division Marine Corps Combat Development Command
Navy’s Operational Authority for Naval Networks, Information Operations, and FORCEnet 2004 Strike, Land Attack & Air Defense Annual Symposium Vice Admiral.
BENEFITS OF SUCCESSFUL IT MODERNIZATION
DRAFT Reporting Department of Defense Programs to OMB Improving PEO and Local Program Manager Use of Exhibit 300s to Show Business Value / Architecture.
Object Management Group Presentation Unified Architecture Framework and Methodology Key Component to Interoperability 13 November 2014 Walt Okon Professor,
Georgina Anthony Antonella Demartini Chanell Fletcher Jacob Lile Serenay Usta.
Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.
James R. Enos US Military Academy Synthesizing DoDAF Architectures to Develop the Joint Capability Enterprise Architecture.
Proposed EA Assessment Framework 2.0 Chief Architect’s Forum (CAF) Dick Burk Chief Architect and Director of Federal Enterprise Architecture Program, OMB.
9/11/ SUPPORT THE WARFIGHTER DoD CIO 1 Sample Template Community of Interest (COI) Steering Committee Kick-off Date: POC: V1.0.
Program Manager, Information Sharing Environment UNCLASSIFIED ISE Enterprise Architecture and Common Standards Program.
DoD Acquisition Domain (Sourcing) (DADS) Analysis of Alternatives (AoA) E-Business/SPS Joint Users’ Conference November 15-19, 2004 Houston, TX.
The Planning, Programming, Budgeting and Execution (PPBE) Process John Roth Department of Defense Deputy Comptroller (Program/Budget)
The Planning, Programming, Budgeting and Execution (PPBE) Process John Roth Deputy Comptroller (Program/Budget)
CoCom Involvement in the Joint Capabilities Process November 4, 2003.
12 August 2010 DoDAF Development Team
A Net-Centric DoD NII/CIO 1 Sample Template Community of Interest (COI) Steering Committee Kick-off Date: POC:
Rapid Response Enterprise Architecture Modeling™ By: Thach Le Darren Barber
MPE – Enabling ALL to securely SEE, DECIDE, ACT MPE - Highlights  Establish Core Implementation Working Group  Build Joining, Membership, and Exiting.
Connecting People With Information Transforming the Way the DoD Manages Data M. David Allen OASD(NII)/DoD CIO May 23, 2006 “The.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
BEA Orientation November 13, 2007
I n t e g r i t y - S e r v i c e - E x c e l l e n c e As of: 3/1/2016 Air Force Weather Agency CEISC Committee Focus Shift - Proposed Modification to.
Overview MRD Enterprise MRD Process
“Unified” (Common) Architecture Framework (UAF) Joint Project
MORS Special Meeting: Risk, Trade Space, & Analytics for Acquisition
VERSION 15 Primitives – Lexicon IPR 6 August 2008
Today’s Summary Tab 4 Tab 6 Tab 2 Tabs 3 and 5 Defense Acquisition
Requirements Executive Overview Workshop Requirements Management Certification Training Mr. Matt Ghormley.
DoDAF 2 Was Designed to Support DoD’s 6 Core Processes
Patrick Gorman Assistant Head Architecture Framework
Architecture Tool Vendor’s Day Tool Characterization Template
Unified Architecture Framework NATO Architecture CaT Introduction
Criticality and Risk in DODAF 2
Update on the Architecture CAT
Defense Acquisition System
Official Current Version of DoDAF
DoDAF Version 2.03 Update 05 Jan 2012 DoDAF Team 1 1.
DoD Architecture Tools, Commercial Tools
Improving Mission Effectiveness By Exploiting the Command’s Implementation Of the DoD Enterprise Services Management Framework - DESMF in the [name the.
Identify the Risk of Not Doing BA
VERSION 15 DoDAF Vendor’s Day Session 22 July 2008
US Kickoff brief to Frameworks Convergence Meeting
Unified Architecture Framework NATO Architecture CaT Results
Brief to Extraordinary NATO A-CAT Mr. Walt Okon January 2013
Brief to Extraordinary NATO A-CAT Mr. Walt Okon January 2013
Architecture Tool Vendor’s Day
Improving Mission Effectiveness By Exploiting the Command’s Implementation Of the DoD Enterprise Services Management Framework - DESMF in the [name the.
Air Force Airborne SIGINT Architecture & Analysis
Agenda All-Monday 15 Sep 0800 Welcome - Opening remarks
Overview and Role in DoD Governance
Introduction DoDAF 2.0 Meta Model (DM2) TBS dd mon 2009 VERSION 15
Introduction DoDAF 2.0 Meta Model (DM2) TBS dd mon 2009 VERSION 15
Headquarters U.S. Air Force
Headquarters U.S. Air Force
Weapons System Lifecycle Management (WSLM) Information Brief
International Council on Systems Engineering (INCOSE)
Review June 2012 London Unified Architecture Framework Meeting
NATO Architecture Capability Team (A-CaT) Workshop
PPBE JEOPARDY!.
DoD Architecture Framework Overview
Architecture & Interoperability Directorate
CORE Name: CORE® Description:
US Kickoff brief to Frameworks Convergence Meeting
International Defense Enterprise Architecture Specification (IDEAS)
International Defense Enterprise Architecture Specification (IDEAS)
Presentation transcript:

Workshop for ACT – IAC, EA-SIG Mr. David McDaniel (ctr) 20 July 2012 History of DoDAF to 2.02 Workshop for ACT – IAC, EA-SIG Mr. David McDaniel (ctr) 20 July 2012

Overall architecture framework convergence vision DoDAF v1.5 1995 C4ISR F/W v1.0 v2.0 UAF v2.05 2003 2007 JCIDS & NR-KPP Applicability beyond C4ISR Use-based Integrated Architecture 2009 2010 2012 2014 v2.01 v2.02 v2.03 DoDAF/DNDAF v2.04 1997 2016 2013 Joint Interoperability DoDAF v1.0 C4ISR F/W v2.0 Net-centricity and SoA SvcV views 26 AV/OV/SV/TV views Linked to I&S policies CADM 2.0 Fit-for-purpose Data-centric architecture Improved models of systems, services, capabilities, rules, measures DoDAF Meta Model (DM2) based on IDEAS Urgent CRs 52  1 XSD IDEAS Foundation v1.0 fixes TECHEDITS DM2 OWL Federal Common Approach DNDAF Security Views MODEM – DM2 Harmonization (IDEAS Domain Level) NATO NAF UDAF Standardization, e.g., ISO OMG OASIS Framework Objective: Achieve a single integrated Architecture Framework for interoperability. Achieve a US, Canada, and United Kingdom single Framework with a common Data Meta Model Achieve alignment with the US Government Common Approach to Enterprise Architecture 19 June 2012 2 2

DoDAF 2 Was Designed to Support DoD’s 6 Core Processes OPS DAS SE CPM JCIDS PPBE Operations (OPS) Joint Capability Integration Development System (JCIDS) Defense Acquisition (DAS) Systems Engineering (SE) Capability Portfolio Management (CPM) Programming Planning and Budget Execution (PPBE) DoDAF 2.0 is designed to support the key processes of the Department of Defense (DoD): 1) Capabilities Development and Integration, 2) Budgeting, 3) Acquisition, 4) Systems Engineering, 5) Portfolio Management, and 6) Operations Planning. It is required to support those for both the Warfighting Mission Areas and Business Mission Areas:

Short Descriptions Operations (OPS) Combatant Command CONOPS Standing communications and operations plans (COMPLAN, O-PLANs) These describe networks, systems, organization, activities, equipment allocation, etc., Joint Capability Integration Development System (JCIDS) Focal point for DoD service chiefs to prioritize needs, shortfalls, and gaps Tightly coupled with DAS and PPBE processes Defense Acquisition System (DAS) Approval process for all acquisitions Milestones reviews Four acquisition categories ~ $ value Architecture data assists go/no-go/contingent decisions Systems Engineering (SE) Technical execution of an acquisitions All programs in the acquisition process must have a Systems Engineering Plan The developed system engineering documents and specifications should flow from and be consistent with the architecture Capability Portfolio Management (CPM) Process for managing $’s by required capabilities Architecture models link investments to the desired effects, tasks, and conditions of capabilities Programming Planning and Budget Execution (PPBE) Annual 5-year budget proposal to Congress Each DoD component develops one and then consolidated by White House to go to Congress Architecture models are used to determine interconnected impacts and to justify the $ request Related to Capital Planning and Investment Control (CPIC) OPS DAS SE CPM JCIDS PPBE DoDAF 2.0 is designed to support the key processes of the Department of Defense (DoD): 1) Capabilities Development and Integration, 2) Budgeting, 3) Acquisition, 4) Systems Engineering, 5) Portfolio Management, and 6) Operations Planning. It is required to support those for both the Warfighting Mission Areas and Business Mission Areas:

The Processes are Intertwined JCIDS DAS PPBE

… and asynchronous and multi-organizational Periodic (annual): PPBE CPM DoD PPBE CPM White House Military Staff HQ (JCS) JCIDS Combatant Commands Doctrine Commands Training Commands Legend: BES — Budget Estimate Submission COCOM — Combatant Commander CPA — Chairman’s Program Assessment DAWG — Deputies Advisory Working Group FYDP — Future Years Defense Program MBI — Major Budget Issues Program ManagerPB — President’s Budget PEO/PM — Program Executive Officer/Program Manager  POM — Program Objectives Memorandum RMDs — Resource Management Decisions Event Driven: JCIDS DAS SE OPS Presidential Cabinet Civilians OPS DAS SE Acquisition Organizations

DoDAF 2.0 Provides the Specification and Guidance to Support the Core Processes with Architectures OPS JCIDS DAS SE CPM PPBE Process Supported Views Data Ontology Specifies: An underlying DoDAF Meta Model (DM2) for describing architectures A set of legacy models (products) that depict some subset of architecture data Provides guidance for: Architectural description development “Fit For Purpose” (FFP) views that optimize Return On Investment (ROI) for the process being supported data conforming to the DM2 FFP-based presentation of data FFP Legacy Capabilities Resource Flows Projects Performers Services Reification Rules Pedigree Locations

Questions?