BTA Briefing: Business Enterprise Architecture (BEA) Overview Presented by Christal Lambert February 3, 2010

Human Resources Admin Services Communications Comptroller PEO: Finance PEO: Sourcing PEO: Human Resources Direct Reporting Programs Stakeholder Relationships - PSAs, Components, External DoD Enterprise Initiative Oversight BEA and ETP Support Component Program Implementation DBSAE Program Implementation Support Investment Management Support BTA Organization Chart Updated: 23JUN2009 Deputy Director Priorities & Requirements Financial Management Priorities & Requirements Supply Chain Management Priorities & Requirements Human Resource Management Defense Business Systems Acquisition Executive Director Deputy Director CoCOM Engagement Economic Roundtable Warfighter Initiatives Warfighter Requirements Business Enterprise Architecture (BEA) Enterprise Transition Plan Performance Management & Reporting Business Capability Lifecycle External Liaison Integration Assessment Planning Enterprise Planning & Investment ERP Systems Vendor Relationships Stakeholder Education Enterprise Integration IT Security Facilities P2P Operations Chief of StaffContracting

Why Are We Building the BEA The NDAA of 2005 Mandated: Development of a Business Enterprise Architecture (BEA) to guide IT business investments Establishment of an Investment Review Board (IRB) process to certify modernization investments over $1M Development of an Enterprise Transition Plan (ETP) to provide an enterprise-wide framework for managing the transition from the “As-Is” state to the “To-Be” Provides a blueprint to guide and constrain investments Guides business management systems modernization efforts Provides foundational data standards and rules Establishes standards for interoperable IT systems Enables accurate, reliable, timely, and compliant information for decision-makers Describes what the DoD is trying to achieve and when we will get there Establishes a program baseline of which to measure progress Establishes integration of transition plans across the business mission area Provides time-phased milestones, performance metrics, and a statement of the financial and non- financial resource needs The Investment Review Board enforces the transformation through the certification process

What is the BEA The enterprise architecture for the DoD that describes the Departments business operations through defined business transformation priorities, the business capabilities required to support those priorities and the combinations of enterprise systems and initiatives that enable those capabilities. What is Used to Manage the BEA A set of COTS tools and a subset of IMIE capabilities and services that enable development, management and presentation of architecture content. Foundational Questions/Terms 4

Major BEA Releases

Lessons Learned No Boiling the Ocean Approach Establish Firm Baseline Stakeholder Review/Concurrence During Development Business Rules Necessary for Compliance Lessons Learned Establish Enterprise Priorities Perform Architecture Development in Segments Stakeholder Engagement throughout the lifecycle Establish Governance – Requirements and Content Federation not Integration

7 Background (CBMs & BEPs) Plan/Budget ProcurementITHRLegalDesign/DevStorage/Trans.MaintenanceDisposal Human Resources Management Weapon System Lifecycle Management Materiel Supply & Service Management Real Property & Installations Lifecycle Management Financial Management Core Business Missions PV AV MV/CSE FV RPA Functional Requirements Sources Who are our people, what are their skills, where are they located? Who are our industry partners, and what is the state of our relationship with them? What assets are we providing to support the warfighter, and where are these assets deployed? How are we investing our funds to best enable the warfighting mission?

Intended UseGoals Investment Management Prioritize projects based on architecture compliance Determine Impact of changes Monitor the realization of goals and benchmarks Legacy System Retirement Transformation Process Standardization Business Process Reengineering Accelerate Change System Development Re-use components Constraints (Standard Interfaces) Implementation Guidelines DoD EA Evolution - Fit for Purpose 8

How is the BEA Used? Compliance Require adherence to standard business rules, data, and LRPs Investment Management/Portfolio Management Drive better investment decisions in accordance with NDAA Improve the ability to uncover and address duplication and redundancies Transformation Strong linkage with FIAR to review E2E processes Identify logical business segments for audit review Development System development Architecture development

10 DBSMC Baseline Stakeholder Baseline BEA 7.0 Release Timeline JulyOctDec Feb Mar Deliver BEA 7.0 3/12 Package & Deliver 3/1-3/12 May Begin Next Release Jan CIO Baseline BEA 6.1 Informational Release 7/29 10/ Content Freeze 9/ Content Freeze 12/18 EP&I Development Cycle 5/05 – 12/18 BIP Prioritization & Schedule Stakeholder Review 1/11-1/22 CIO Review 1/25-2/5 DBSMC Review 2/23-2/25 BEA 6.2 Informational Release

4/5/201012/17/ /11/ wk 1 month Collaboratio n pattern 2 wks 1 wk 3 weeks BEA 8.0 BIP Process

1/25/10 DoD DCMO BMA CTO & CA 1 Strategy and Roadmap for DoD Business Operations Transformation Stds. Performance Measures Semantic Technology CV & Primitives Roadmap Past (BMA Federation Strategy version 2.4a) Present (BOE Execution Roadmap) BEA 3.0 BOE Vision DCMO/CIO Policies CIO - DIEA Arch. Fed. MDR Federation Implementation Plan CIO/DISA – Federal Cloud BEA 8.x Semantic Mediation & Data Virtualization (BTI) NCES/CES BOE Service Enablement Domains HRM/ Med FM Logistics RPILM WSLM/ MSSM Execution DBSAE SOA Imp. Strategy Enterprise Standards Cloud Strategy Future (BMA Architecture Strategy version 3.0) Initial BOE Experience DBSMC/IRBsDCMO/DCIO; EGB; BECCM Version 2.4a DoD Strategic Mgmt. Plan (SMP) Common Vocabulary RDF OWL Vision & Strategy Planning & Roadmap Infrastructure Governance Data Integration BI