Enterprise Architecture Segment Report

1. Enterprise ArchitectureSegment Report Rich von Bostel Chief Enterprise Architect, Office of the CIO U.S. Department of Justice Co-Lead, OMB Performance and Investment Tiger Team 1

2. Purpose of the EA Segment Report • Four main goals for this effort: • Ensure agency segment architectures are generating results • Identify opportunities for reuse and cross-agency collaboration • Provide a format for architects to engage with business owners • Provide updated, standardized segment information to OMB • The Segment Report has been created to report information generated from the FSAM to meet OMB’s EA Assessment Framework 3.0 Criteria EAAF 3.0 FSAM* Segment Report OMB EA Submission * The FSAM Logical Data Model Supporting EA Reporting Requirements Appendix contains a cross-walk between FSAM Artifacts and the Exhibit 53, Exhibit 300, and the EA Segment Report

3. Quarterly Segment Reporting February – Initial May – Completion August – Use November – Results • EASR for all Segments • Must complete only the first two forms • EASR for all Segments • EASR must be completed based on Segment Maturity • Segment Documents uploaded to MAX • Segment Milestones Updated • EASR Updates based on Ex. 53 and Ex. 300 Submissions • Segment Milestones Updated • EASR Updates based on end of the year performance results • Segment Milestones Updated

4. Segment Report Sections/Forms

5. Required Completion Based on Segment Maturity

6. Detailed Information Required by Segment Maturity

7. Identification & Mapping Forms Basic Segment Identification Information Segment Alignment / Mapping also includes FEA Reference Models

8. Performance Form The Performance Form is intended to capture Segment Performance at multiple levels; Strategic Layer – High level metrics showing support of Agency Strategic Goals Segment Layer – Segment specific metrics such as Cost Savings and Avoidance Program Layer – Program and PART specific metrics Business Layer – IT Investment and Activity metrics based on the PRM Line of Sight Segment Performance should leverage current performance architecture activities as indicated in the diagram below

9. Performance Form * FSAM Performance Scorecard requires identical information

10. Transition Planning Form • Transition Planning is focused on showing the activities and milestones that help mature a Segment towards Completion • Sample Segment Development Milestones may include • Segment Architecture Document Development • Business Process Reengineering • Target Architecture Development • System Retirement/Implementation • Business Owner Sign-Off

11. Collaboration and Reuse Form • Reuse of other Segments • Major stakeholders • Business Capability/ Activity Reuse Business Reuse Data Reuse • Data Exchanges • Data Entity Reuse • Secondary IT Investment Mappings • System Service (SOA) Reuse Sys/Service

12. Engaging Vendors through OMG The Object Management Group (OMG): Non-profit industry group Worked with OMB on the Federal Transition Framework (FTF) After the EASR is final (Dec. 12), OMG will create a standard UML model and XML schema for it UML model and XML schema should be approved at Mar. 2009 OMG meeting These will help tool vendors to support the EASR as a standard federal EA report to OMB Goal: EA tools will auto-generate populated EA Segment Reports for federal Agencies to submit periodically to OMB. Tool Vendor support for EASR will probably not be ready for the Feb. 2009 submission to OMB.

13. Next Steps EASR Release The EA Segment Report has been completed and final version will be available via the new OMB FEA-PMO website by COB Friday Dec. 12.  Submissions to OMB OMB is finalizing the submission format for the EASR Possible Formats may include Excel and/or XML OMB requests that Agencies include Segment Documents with their submissions to the OMB MAX site (https://max.omb.gov/) First submissions due in Feb. 2009 (see slide 3 above).

14. Backup Slides 14

15. Reporting Base on Segment Type A Core Mission Area Segment represents a unique service area defining the mission or purpose of the agency. Core mission areas are defined by the agency business model (e.g., tactical defense, air transportation, energy supply, pollution prevention and control, and emergency response).   These Segments should be able to complete all areas of the Segment Report. A Business Service segment included common or shared business services supporting the core mission areas. Business services are defined by the agency business model and include the foundational mechanisms and back office services used to achieve the purpose of the agency (e.g., inspections and auditing, program monitoring, human resource management, and financial management). These Segments may focus more heavily on Collaboration and Reuse within the Segment Report as they provide support to multiple core mission areas. An Enterprise Service Segment includes common or shared IT services supporting core mission areas and business services. Enterprise services are defined by the agency service model and include the applications and service components used to achieve the purpose of the agency (e.g., knowledge management, records management, mapping/GIS, business intelligence, and reporting).    These Segments may only have a few (if any) enterprise-wide investments mapped to them since they focus mainly on providing collaboration and reuse throughout an Agency. Enterprise Service segments may have little information in the Performance and Transition Planning form, as their focus will be on reusing investments primarily mapped to another segment and provide services used by multiple segments.