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

1. BTA Briefing:Business Enterprise Architecture (BEA) Overview Presented by Christal LambertFebruary 3, 2010

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

3. 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” ETP BEA • 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 • 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 The Investment Review Board enforces the transformation through the certification process IRB

4. Foundational Questions/Terms 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. 4

5. Major BEA Releases

6. 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) Who are our people, what are their skills, where are they located? Human Resources Management Who are our industry partners, and what is the state of our relationship with them? Weapon System Lifecycle Management What assets are we providing to support the warfighter, and where are these assets deployed? Materiel Supply & Service Management Core Business Missions How are we investing our funds to best enable the warfighting mission? Real Property & Installations Lifecycle Management Financial Management Functional Requirements Sources PV AV MV/CSE RPA FV Plan/Budget Procurement IT HR Legal Design/Dev Storage/Trans. Maintenance Disposal 7

8. DoD EA Evolution - Fit for Purpose 8

9. 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. 9/24 12/18 7.0 Content Freeze 6.2 Content Freeze 5/05 – 12/18 EP&I Development Cycle 3/1-3/12 Package & Deliver 1/11-1/22 Stakeholder Review 1/25-2/5 2/23-2/25 DBSMC Review CIO Review BEA 7.0 Release Timeline 10/28 7/29 3/12 Feb Mar May July Oct Dec Jan Deliver BEA 7.0 BIP Prioritization & Schedule Begin Next Release BEA 6.1 Informational Release BEA 6.2 Informational Release Stakeholder Baseline CIO Baseline DBSMC Baseline

11. BEA 8.0 BIP Process 1 wk 1 month 3 weeks 1 wk 2 wks 1 wk Collaboration pattern Collaboration pattern 4/5/2010 12/17/2010 3/11/2010

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