Federal Enterprise Architecture Program Management Office

1. Federal Enterprise Architecture Program Management Office Status of the Federal Enterprise Architecture

2. Table of Contents • Federal Enterprise Architecture Reference Models • Use of Component-Based Architectures • Solution Architects Working Group • Next Steps

3. The Federal Enterprise Architecture is a business-focused framework for cross-Agency, Government-wide improvement • The Federal Enterprise Architecture (FEA) is providing OMB and Federal Agencies with a new way of describing, analyzing, and improving the Federal Government and its ability to serve the citizen • The FEA will eliminate the organizational obstacles that have historically hindered improvement without forcing reorganization • The FEA is a business-focused approach … it’s not just for IT • The FEA provides a common framework for improving a variety of key areas: • Cross-agency collaboration • Improved service to the citizen • e-Government • Component Based Architecture • and more • Budget allocation • Horizontal and vertical information sharing • Performance measurement and budget/performance integration Page 3

4. The FEA Business Reference Model (BRM) was the first step in development of the FEA Business Areas Business Areas Lines of Business Lines of Business Internal Internal Lines of Business Lines of Business Sub Sub - - Functions Functions Page 4

5. Additional reference models are being developed using the BRM as a common starting point, further expanding the value proposition of the model Business Reference Model (BRM) complete (v1.0) • Lines of Business • Agencies • Customers/Partners Performance Reference Model (PRM) • Government-wide Performance Measures & Outcomes • Line of Business-Specific Performance Measures & Outcomes Business-Driven Approach Data Reference Model (DRM) • Business-focused data standardization • Cross-Agency Information exchanges Application-Capability Reference Model (ARM) • Capabilities • Functionality Technical Reference Model (TRM) • IT Services • Standards Page 5

6. Other models build upon the BRM to define desired goals for the Government’s business lines and help Agencies determine how to best allocate resources to meet those goals The Performance Reference Model (PRM) OUTCOMES DESIRED OUTCOMES common measures across agencies and programs • Citizen Service • Mission Performance • Internal efficiency The Business Reference Model (BRM) Programs tied to outcomes BUSINESS NEEDS Business support and Admin opportunities Resource distribution Human Capital Information Technology Other Capital Assets Resource reference models: - Applications - Facilities - Workforce, etc. RESOURCE ALLOCATION Applications Technology Data Workforce Equipment Fleet Facilities Page 6

7. Citizen-centered performance outcomes Integrated Budget and Performance Process using a Federal Enterprise Architecture Approach Existing Budget and Performance Process Mission Accomplishment Mission Accomplishment Labor, etc. Justice Energy Performance Reference Model Program 9 Program 4 Program 2 Program 8 Program 6 Program 1 Program 5 Program 3 Program 7 Lines of Business Lines of Business Lines of Business Uneven use of performance information Partnering Agencies Program 9 Program 4 Program 2 Program 8 Program 6 Program 1 Program 5 Program 3 Program 7 Collaborative Investments Redundant Investments • Allocation of resources is agency-specific and stove-piped • No link between funding decisions and performance • Difficult to identify duplicative functions, processes and initiatives; and opportunities to improve services • Resource allocation based on business line needs & performance results • Resources directed to capital investments that enhance government effectiveness and efficiency, and contribute to performance outcomes • Emphasis is placed on cross-Agency collaboration

8. Table of Contents • Federal Enterprise Architecture Reference Models • Use of Component-Based Architectures • Solution Architects Working Group • Next Steps

9. Component-Based Architectures, and our ability to embrace them, can support the rapid assembly of E-Gov solutions • The E-Gov Initiatives are positioned to transform existing thinking in how the Federal Government leverages technology to satisfy complex business objectives • Priority funding consideration will be provided to IT investments that leverage technology purchases across multiple entities* • Component-Based Architectures (CBA) will: • Support reusability, portability, and interoperability • Leverage existing cross-agency investments • Leverage emerging and industry-proven technologies • J2EE, .NET, XML, SOAP, Web Services, UDDI • Reduce costs and risks associated with legacy integration, technology selection, maintenance and support • Improve: • Quality and consistency of services • Customer support (citizen and intra-governmental) • Delivery and speed to market *OMB Circular A-11, Section 53 Page 9

10. Component-Based Architectures can provide the basis for cross-Agency collaboration and E-Gov transformation - Online Rulemaking and Management - (Conceptual Design) FirstGov (Point of Entry, Authentication, Service Directory) Customer Public/Citizen Services Publishing Calendar Policy Search Engine Policy Review Feedback Discussion Forums Policy Profile Alerts and Subscriptions FAQ’s, Links Shared/Reusable Components Conceptual Government Services Policy Repository Business Rules Engine Content Publishing Common Business Processes Content Management Policies, Local repositories DOT USDA EPA HHS INTERIOR ENERGY Agencies Page 10

11. Components - and their supporting architectures - provide a “building block” approach to effectively leverage disparate business services and technologies GovBenefits (Eligibility Assistance Online) Conceptual Sample List Sample List Participating Agencies / Programs Federal Enterprise Architecture 150 Federal Benefit Programs Business Reference Model (BRM) Disaster Housing Program Individual / Family Grants G.I. Bill Rural Rentals Beneficiary Travel Veterans / Survivors FEMA - VA - Social Services - Burial Services - Housing Benefits - Medical Services - Monetary Benefits Employment Service WIA Youth Activities DOL - Component-Based Architecture Application Capability Reference Model (ARM) Content Management FirstGov.Gov - Collaboration - Data Management - Commerce - Search - Reporting - Analysis / Logic - Procurement - Financial - CRM - Human Capital Mgmt - Logistics - Content Management Business Rules Engine CRM User Feedback Data Management Demographics Technology Reference Model (TRM) Technologies Standards, Specifications • Presentation • Business Logic • Data Interchange • Internet Platforms • Data Management • Graphics • Security JRun Application Server Enterprise Java Beans (EJB) Java Server Pages (JSP) Oracle, JDBC http://www.java.sun... http://www.javasun... http://www.java.sun... SQL 92 Page 11

12. To support development and reuse of components, best practices outline the use of a tiered solution architecture - Solution Design and Development - (Conceptual Framework) PRESENTATION / INTERFACE Abstracts the complexity of the application from the user or interfacing applications. SECURITY Security provides an overarching framework that includes a series of defensive mechanisms and functions designed to protect the system, data and information from unintentional or malicious threats. CUSTOMER INTERFACING SYSTEM SECURITY BUSINESS LOGIC Business functionality is modular and component based, enabling greater maintainability and interoperability. PRESENTATION / INTERFACE INFORMATION STORAGE Information stored in persistent relational, object-based, and/or file based repositories is abstracted to hide the complexity of the storage system from the interfacing applications. BUSINESS LOGIC TRANSACTION MGMT. Ensures/optimizes access, quality, consistency, and integrity of operational data. TRANSACTION MANAGEMENT INFORMATION STORAGE Page 12

13. Table of Contents • Federal Enterprise Architecture Reference Models • Use of Component-Based Architectures • Solution Architects Working Group • Next Steps

14. The Solution Architects Working Group (SAWG) is focused on assisting the 24 Presidential Priority E-Gov Initiatives in areas related to: • Solution Architecture Planning • Review and / or creation of supporting documentation • Forward-thinking approaches – aimed at risk mitigation • Conveyance of best practices and lessons learned based on years of knowledge and expertise • Architecture Design • Identification of components, buy vs. build methodologies • Component-Based implementations – leveraging existing capabilities across the Federal Government (i.e., Pay.Gov, FirstGov.gov, etc) • Rapid Development and Enterprise Architecture methodologies – what are the critical successes, minimize stranded investments • Expertise and Knowledge • XML, Web Services (what’s the right approach) • Security, Authentication (what you need to plan for now) • Hosting and Platforms (leveraging what’s available now) • Relationships with other Federal, State and Industry Working Groups • XML Working Group, Federal Architecture Working Group (FAWG) • NASCIO • Industry Advisory Council (IAC), OASIS (Interoperability) Page 14

15. The SAWG Leadership Team consists of solution architects who are focused across vertical areas of expertise • Executive Management • Directional Oversight Norman Lorentz Expanded structure based on demand of skills • Recommendations • Program Management Chief Architect Solution Architects • Delivery Oversight • Communication/Outreach Senior Solution Architect Solution Architect Solution Architect Solution Architect Solution Architect Solution Architect PRESENTATION Forms, Scripting DHTML, XSL, XML JSP, ASP HTML, JavaScript FirstGov Integration SECURITY SSL, e-Authentication Encryption Security MESSAGING SOAP Web Services XML ebXML BUSINESS LOGIC EJB, COM, COM+ UML, Use Cases PLATFORMS & DB J2EE, .NET SQL, Databases Services Architecture Supporting Partners OMB Portfolio Managers Managing Partners Government-wide Groups State and Local Industry Working Groups (i.e., NASCIO, w3.org), others Industry Page 15

16. The SAWG can help at virtually any stage across the initiatives’ development and implementation life cycle Operations and Maintenance Design Prepare Develop Test Implement Requirements Definition Planning Phase Business Case See Development Artifacts Support Plan Performance Specifications Project Management Plan Security Specifications Business Requirements Functional Requirements - Use Cases - Activity Diagrams Implementation Plan Operations and System Admin Manuals System Architecture Software Development Plan Security, Contingency Plans Configuration / Change Mgmt Plan Risk Management Plan Testing - User Acceptance - Independent Test Plans, Scenarios Page 16

17. Table of Contents • Federal Enterprise Architecture Reference Models • Use of Component-Based Architectures • Solution Architects Working Group • Next Steps

18. Near-Term Next Steps for the SAWG and FEA Solution Architects Working Group • Engage with e-Gov Initiatives • Create the E-Gov Solution Development Life Cycle (SDLC) • Intended to supplement existing SDLC’s • Focused on cross-agency collaboration and development • Will identify and provide examples of supporting Artifacts • Integrate Component-Based Architecture Guidance • Within the Federal Enterprise Architecture E-Gov Guidance • Create and Deliver Intellectual Capital • Best Practices • Lessons Learned • Case Studies, White Papers • Delivered through http://www.feapmo.gov Federal Enterprise Architecture • Issue FEA Management and Maintenance Plan • Define and validate the Draft ARM and TRM • Continue consultations with Department of Defense and intelligence agencies to obtain their input on the Business Reference Model • Work with OMB and Business Line owners from Federal Agencies to define government-wide and Line of Business-specific performance measures and outcomes (PRM) • Launch Federal EAMS on the FEAPMO website Page 18