Federal Enterprise Architecture Program Management Office Status of

  • Slides: 18
Download presentation
Federal Enterprise Architecture Program Management Office Status of the Federal Enterprise Architecture

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

Table of Contents Federal Enterprise Architecture Reference Models Use of Component-Based Architectures Solution Architects

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

The Federal Enterprise Architecture is a business-focused framework for cross-Agency, Government-wide improvement The Federal

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: - Budget allocation - Horizontal and vertical information sharing - Performance measurement and budget/performance integration Page 3 - Cross-agency collaboration - Improved service to the citizen - e-Government - Component Based Architecture - and more

The FEA Business Reference Model (BRM) was the first step in development of the

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

Additional reference models are being developed using the BRM as a common starting point,

Additional reference models are being developed using the BRM as a common starting point, further expanding the value proposition of the model Business-Driven Approach Business Reference Model (BRM) • Lines of Business • Agencies • Customers/Partners complete (v 1. 0) Performance Reference Model (PRM) • Government-wide Performance Measures & Outcomes • Line of Business-Specific Performance Measures & Outcomes 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

Other models build upon the BRM to define desired goals for the Government’s business

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 OUTCOMES • Citizen Service • Mission Performance • Internal efficiency D S RE ME I S O DE TC OU common measures across agencies and programs The Performance Reference Model (PRM) The Business Reference Model (BRM) Programs tied to outcomes SS E N SI S U B ED NE Business support and Admin opportunities Resource distribution CE ON R OU ATI S RE LOC AL Page 6 Information Technology Applications Technology Data Human Capital Other Capital Assets Workforce Equipment Fleet Facilities Resource reference models: - Applications - Facilities - Workforce, etc.

Integrated Budget and Performance Process using a Federal Enterprise Architecture Approach Existing Budget and

Integrated Budget and Performance Process using a Federal Enterprise Architecture Approach Existing Budget and Performance Process Mission Accomplishment Citizen-centered Program 9 Program 8 Program 7 Program 6 Program 5 Program 4 Program 3 Program 2 Program 1 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 Lines of Business Program 9 Program 8 Program 7 Program 6 Program 5 Performance Reference Model Lines of Business Uneven use of performance information Program 4 Program 3 Program 1 Program 2 Labor, etc. Justice Energy performance outcomes Lines of Business Partnering Agencies Collaborative Investments • 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

Table of Contents Federal Enterprise Architecture Reference Models Use of Component-Based Architectures Solution Architects

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

Component-Based Architectures, and our ability to embrace them, can support the rapid assembly of

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: n n n Page 9 Support reusability, portability, and interoperability Leverage existing cross-agency investments Leverage emerging and industry-proven technologies w J 2 EE, . NET, XML, SOAP, Web Services, UDDI Reduce costs and risks associated with legacy integration, technology selection, maintenance and support Improve: w Quality and consistency of services w Customer support (citizen and intra-governmental) w Delivery and speed to market *OMB Circular A-11, Section 53

Component-Based Architectures can provide the basis for cross-Agency collaboration and E-Gov transformation - Online

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

Components - and their supporting architectures - provide a “building block” approach to effectively

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

To support development and reuse of components, best practices outline the use of a

To support development and reuse of components, best practices outline the use of a tiered solution architecture - Solution Design and Development (Conceptual Framework) 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 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. Page 12 PRESENTATION / INTERFACE Abstracts the complexity of the application from the user or interfacing applications. BUSINESS LOGIC Business functionality is modular and component based, enabling greater maintainability and interoperability. BUSINESS LOGIC TRANSACTION MANAGEMENT INFORMATION STORAGE TRANSACTION MGMT. Ensures/optimizes access, quality, consistency, and integrity of operational data.

Table of Contents Federal Enterprise Architecture Reference Models Use of Component-Based Architectures Solution Architects

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

The Solution Architects Working Group (SAWG) is focused on assisting the 24 Presidential Priority

The Solution Architects Working Group (SAWG) is focused on assisting the 24 Presidential Priority E-Gov Initiatives in areas related to: Solution Architecture Planning n n n 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 n Identification of components, buy vs. build methodologies Component-Based implementations – leveraging existing capabilities across the Federal Government (i. e. , Pay. Gov, First. Gov. gov, etc) Rapid Development and Enterprise Architecture methodologies – what are the critical successes, minimize stranded investments Expertise and Knowledge n n n 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 n n Page 14 n XML Working Group, Federal Architecture Working Group (FAWG) NASCIO Industry Advisory Council (IAC), OASIS (Interoperability)

The SAWG Leadership Team consists of solution architects who are focused across vertical areas

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

The SAWG can help at virtually any stage across the initiatives’ development and implementation

The SAWG can help at virtually any stage across the initiatives’ development and implementation life cycle Planning Phase Design Requirements Definition Prepare Develop Business Case Project Management Plan Test Implement See Development Artifacts Support Plan Performance Specifications Business Requirements Security Specifications 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 Test Plans, Scenarios Page 16 Testing - User Acceptance - Independent Operations and Maintenance

Table of Contents Federal Enterprise Architecture Reference Models Use of Component-Based Architectures Solution Architects

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

Near-Term Next Steps for the SAWG and FEA Solution Architects Working Group Engage with

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) n Intended to supplement existing SDLC’s n Focused on cross-agency collaboration and development n Will identify and provide examples of supporting Artifacts Integrate Component-Based Architecture Guidance n Within the Federal Enterprise Architecture E-Gov Guidance Create and Deliver Intellectual Capital n Best Practices n Lessons Learned n Case Studies, White Papers n Delivered through http: //www. feapmo. gov Page 18 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 Businessspecific performance measures and outcomes (PRM) Launch Federal EAMS on the FEAPMO website