BEA 10.0 CCB Architecture Artifact Approval Brief 3 December 2012 Randy Turner, ODUSD(I&E) BEI Department of Defense

BLUF DBC approved integration of EEIM into the BEA 10.0 on 10/26/12; RPILM briefed the DBC and provided a binder of draft EEIM artifacts (including DoDAF products) and background documentation. Addition of the enterprise energy information management (EEIM) requirements into the BEA will establish a capability to capture, analyze, and report standard energy information, both at the Component and DoD levels. This capability will give DoD a better understanding and ability to manage energy information across those enterprises. The EEIM capability will be implemented by integrating two major platforms: An OSD-hosted EEIM centralized capability that establishes the DoD enterprise IT infrastructure, maintains a common data language, and creates reporting/business analytics applications DoD Component (Military Services, WHS, and Defense Agencies) implementation of a Component-specific capability that integrates systems and processes to streamline collection, assimilation, and analysis of accurate and timely facility energy data. EEIM is expected to deliver the following outcomes: Systematic tracking of energy efficiency improvements against energy project investments Improvement in timeliness and accuracy of reimbursable customer billing Provision of actionable information to decision-makers and users alike Reduction in utility late fees, utility overcharges, and the time spent processing utility invoices Leveraging of enterprise data to predict future trends/analyze future energy investment strategies Enhance competition to improve asset energy performance by enabling comparisons at and beyond the installation level Creation and tracking of asset level metrics.

Interdependencies/E2E Equities/LOE Business Requirements: DoD has undertaken the Enterprise Energy Information Management (EEIM) effort to: Establish an integrated facility management system capability Enable interoperability with Component systems for efficient energy data exchange across Enterprise Improve scalability of energy investment information to enable the visibility of installation and facility-level management and reporting. How will the proposed BEA change support achieving specified business outcome? Improve Investment Decisions Optimize DOD Enterprise Business Processes Develop an Information Infrastructure Define a Target Defense Business Systems Computing Environment Other – Report Energy and Water Use to External Stakeholders. Interdependencies across PSA functional areas that must be addressed: There will be no changes or updates to the E2Es based on EEIM EEIM will have standard touch points with other E2Es, including Procure-to-Pay (P2P) and Service Request to Resolution (SR2R) EEIM will not include updates to the current structure and content of Acquire-to-Retire (A2R). The AT&L community has identified several necessary A2R change needs that are outside the scope of the addition of EEIM. Estimated Total LOE: 153 Hours View/Work Segment: Hours: 4 New OV-6c Diagrams 24 Add & Adjust OV-5b Diagrams 24 Add New OV-6a Business Rules 4 Update OV-2 1 Update SV-1 1 Add 1 New DIV-2 Diagram 32 “Major” change level 8 4 Stakeholder Workshops 24 23 Object Definitions 24 Secondary Work Level 5 3 Integration Level 4 8

CCB Prioritization/Approval Recommendation Proposed BEA CCB Criteria [Architecture Requirements] Identify your conformance with the below stated criteria (slides 5-6). Type of EA artifact is clearly understood Business Element Business Requirement Business Strategy Business Outcome Business Mandate Investment Management Process Support Element Portfolio Management Support (e.g., binning and bucketing by Operational Activities, Capabilities, E2E, etc.) EA Structure Element (common vocabularies, documentation methodologies, etc.)

CCB Prioritization/Approval Recommendation Proposed BEA CCB Criteria [Architecture Requirements] Identify your conformance with the below stated criteria Impact of proposed change Cost/impact of proposed change to BEA (i.e., how many systems/processes, architectures across DoD will be effected?) Prioritization (Provide your summary recommendation and rationale for including the requirement in BEA 10.0) CCB, in consultation with Functional Sponsor, has assigned proposed priority (low, medium, high) Maturity of proposed EA approach Clear “line of sight” from business requirement to proposed EA artifact(s) Functional Sponsor has validated proposed EA artifact(s) will assist with achieving intended business requirement/strategy/outcome/mandate EA artifact resource estimate complete (how many people for how long)