Using Enterprise Architecture to Solve Business Problems

1. IT Summit Conference October 4, 2006 Panel on Using Enterprise Architecture to Solve Business Problems Dick Burk Chief Architect and Manager, Federal EA Program Office of Management and Budget Lisa Schlosser CIO, Department of Housing and Urban Development Scott Bernard Deputy CIO, Federal Railroad Administration For slide details go to “notes”

2. Value to the Mission FEA Practice Guidance September 28, 2006 Dick Burk Chief Architect and Manager, Federal Enterprise Architecture Program, OMB

3. FEA Practice Guidance • Value to the Mission –Increase the value of architecture activities to improve results in agency mission areas. • Two primary concepts described in the FEA Practice Guidance • Enterprise Architecture (EA) Transition Strategy • Segment Architecture

4. Structure • Currently based on four chapters • Chapter 1 – Introduction • Chapter 2 – EA Transition Strategy • Chapter 3 – Introducing Segment Architecture • Chapter 4 – Developing Segment Architecture • Additional chapters to be determined

5. Chapter 1 – Introduction • Provides an overview of the concepts described in the other guidance documents. • Chapter 1 sections • Delivering Mission Value • Principles • Performance Improvement Lifecycle • Architecture Levels • Key terms

6. Chapter 1 – Introduction • Performance Improvement Lifecycle • Architecture Levels

7. Chapter 2 – EA Transition Strategy • Describes what is included in an EA transition strategy and provides guidance on developing and using an EA transition strategy. • Chapter 2 sections: • Transition Strategy Concepts • Developing the Transition Strategy • Using the Transition Strategy

8. EA Transition Strategy and Sequencing Plan

9. Chapter 3 – Introducing Segment Architecture • Describes segment architecture concepts, the content included in segment architecture, and how to use segment architecture. • Chapter 3 sections • Segment Architecture Concepts • Segment Identification and Integration • Initiating Segment Architecture • Applying Segment Architecture

10. Segment Identification

11. Three Types of Segments • Core Mission Area • Unique service area defining the mission or purpose of the agency • Core mission areas are defined in the agency Business Model. • Business Service: • Common or shared business service supporting a core mission area. • Business services are defined in the agency Business Model and include the processes and back office services used to achieve the purpose of the agency. • Enterprise Service: • Common or shared IT service supporting core mission areas and business services. • Enterprise services are defined in the agency Service Model and include the applications and service components used to achieve the purpose of the agency.

12. Chapter 4 – Developing Segment Architecture • Planned – In Development • Will provide guidance on how to develop segment architecture, when one should be developed, and who should participate in the development.

13. For Further Information:www.egov.gov

14. Federal CIO Council Architecture & Infrastructure Committee (AIC)Lisa Schlosser Co-Chairperson

15. AIC Vision In 2006-2007, the AIC will implement projects that support and demonstrate the ability of the CIO Council to effectively architect, invest, and implement solutions to improve the performance of government. Results will be documented as demonstrated by improved performance in terms of both mission outcomes and operational efficiency.

16. AIC Organizational Structure

17. Emerging Technology Subcommittee Tuning ET Together - From Stovepipes to Wind Chimes • Purpose: This subcommittee provides an “incubator” organizing process to accelerate discovery, maturation, and validation of capabilities that leverage FEA principles and priorities. The key components of our charter are: • Greater foresight and discernment as established and emerging technologies compete and converge • Longer life-cycles through market-based, open standards technologies • Common understanding of business scenarios to anticipate performance outcomes and mitigate risks. • Participation in this subcommittee will help you improve your agencies’ strategic foresight and collaboration capacity around strategic IT assets. Key FY06/FY07 Activities/Deliverables 1. Forging effective IPv6 strategies together (example in FY06) 2. Life-cycle process for ET discovery and collaborative action 3. Strategic Dialogue Among Communities at Open Forums - Expedition Workshops Co-Chair Contact Information

18. Data Architecture Subcommittee (DAS)Build to Share Purpose: To advances the management of Federal data as a national asset; stewardship of the Federal Enterprise Architecture (FEA) Data Reference Model (DRM), FEA DRM Management Strategy; to promote the use and improvement of data and data standards across the Federal Government; to facilitate of community collaboration and information sharing using communities of interests, both federal and intergovernmental. Key FY06/FY07 Activities/Deliverables 1. FEA DRM updates and revisions 2. Implementation strategies, best practices, and success stories 3. Establish an authoritative knowledge center for Federal data-related issues and opportunities Co-Chair Contact Information

19. GovernanceSubcommitteeGovernance for a Transformed Government Purpose: This subcommittee provides policy guidance, and advice and assistance in the definition, design and implementation of Enterprise Architecture (EA) discipline and practice throughout the Federal government. It serves as the core Federal group providing advocacy for EA integration of business and technology architectures across, state, local and international boundaries. The Governance Subcommittee serves as a focal point for the development and coordination of Federal government-wide policy, guidance, including best practices for EA development and implementation. Participation in this subcommittee will provide an opportunity to gain experience in applying the reference models to improve efficiency and effectiveness within your agency. Co-Chair Contact Information • Key FY06/FY07 Activities/Deliverables • RMMP/Consolidated FEA RM • EGIF/ Awareness /Paper SOA State of Practice • Transformative Governance Models and Best • Practices for eGov Shared Services (January 2007)

20. ServicesSubcommitteeEnabling Shared Services Purpose: Enable Shared Services through development of a Shared Services Strategy, a roadmap for CORE.gov, and a set of demonstration projects focused on Information Exchange and other integration concerns with Shared (LoB) Solution and composite applications. • Key FY06/FY07 Activities/Deliverables • Shared services management strategy including management framework and policy maturity model. • User and strategy driven CORE.gov tools, product roadmap, and solution architecture • Shared Services demonstration leveraging participant capabilities Co-Chair Contact Information

21. The SOA Vision Enterprise LOB LOB Business Function Core IT Service • Enterprise Integration: IT solutions support strategic LOBs. IT modernization promotes re-use though the automation of common business functions and core IT services. Program Offices n n n n n n n n n n n n n n n n n n n n n n n n n n n Modernization n n n n n n Applications/Business Processes n n n n n n n n n n n n n n • Program Orientation: Transaction focused with data rich solutions tailored to support specific program business requirements.

22. Vision: Focus on SOA

23. SOA Success Story

24. Critical Success Factor: Infrastructure Optimization Critical Success Factor: Infrastructure Optimization 24

25. CORE.gov: Helping Advance EA in Government • Promotes accessible and flexible platforms for enhanced collaboration and knowledge sharing. • Supports SOA by providing space to develop and blend business and IT strategy on a controlled environment. • Ensures cost effective methods of identifying and optimizing government business processes that can be shared and modified to meet specific agency needs. Enables secure and cost effective methods to develop government business processes across multiple agencies • Promotes the participation of SOA activity with increased ease of participation. • Provides a well managed environment with several tools that employ capability to find, evaluate, share and download information that is essential to the development of services and lines of business.

26. AIC Next Steps • Requesting representatives to serve on all committees; please send interested names to Stephanie Powers at AIC_Support@sra.com by May 31st • Each subcommittee will convene over year to solicit participation in producing the deliverables laid out in this presentation

27. Federal Railroad Administration U.S. Department of Transportation Case Study in Using Enterprise Architecture to Solve Business Problems The Mobile Workforce Initiative Scott A. Bernard, PhD Deputy Chief Information Officer Chief Architect scott.bernard@dot.gov

28. About FRA FRA is one of eleven modal administrations in the Department of Transportation. The mission of FRA is to promulgate and enforce rail safety regulations; administer railroad assistance programs; conduct research and development in support of improved railroad safety and national rail transportation policy; provide for the rehabilitation of Northeast Corridor rail passenger service; and consolidate government support of rail transportation activities. Locations:Headquarters:Washington, DC 8 Regional Offices:Atlanta, Boston, Chicago, Dallas, Kansas City, Philadelphia, Portland, Sacramento Workforce:Approximately 840, over half are field safety inspectors. Lines of Business:Office of the Administrator/Deputy Administrator Office of Financial Management and Administration Office of the Chief Counsel Office of Civil Rights Office of Railroad Development Office of Policy Office of Public Affairs Office of Safety

29. RITA DOT “Federated” Approach to EA FRA is taking responsibility for its part of the DOT EA • FRA has aligned IT resources to the standards of the DOT Common Operating Environment (COE). • Cross-cutting and modal-specific applications will be hosted in one data center at the new DOT HQ in 2007. • Standards for mobile computing and communications are still emerging.

30. FRA EA Framework DOT EA

31. Business Problem: Many of FRA’s Railroad Safety Inspectors have difficulty gaining and maintaining mobile communications and computing links in the field and at hotels. Lots of gaps in coverage, slow dial-up connections. Technology Issues: - Lack of agency/department standards for mobile communications. - Lack of agency/department standards for mobile computing. - Variety of communications and computing equipment in use. - Variety of dial-up, VPN, DSL remote data access solutions in use. - Lack of effective Tier 1 and Tier 2 assistance in trouble shooting. Architecture Solution: (Working with DOT CTO) PRM: Identify mobile computing line-of sight process, establish metrics. BRM: No change in mission area, function, sub-functions. SRM: Establish a mobile workforce business service that is co-sponsored by the Office of Financial Mgmt. & Admin. and the Office of Safety. DRM: Identify data exchange requirements and standards. TRM: Establish new standards for mobile communications & computing. SPP: Identify data protection solutions for PII data and mobile equipment.

32. Solving the Business Problem Establish the Mobile Workforce Initiative (MWI) to provide railroad field inspectors and other mobile users with standard computing and computing equipment and broadband service packages. HQ Encrypted & Rugged Laptop VPN Regional Offices PDA & Biometric USB Drive Internet RAS Broadband Cellular DSL Portable Printer & Scanner Railroad Inspector Connectivity Options Standard Equipment

33. MWI Deployment Timeframe: • FY 2007 / Q1 • Expected Outcomes of MWI: • Improved work productivity in the field • Improved work productivity at hotels • More mission capability • Quicker deployment of applications/updates to field inspectors • Improved telecommuter support • Improved Continuity of Operation capabilities • Improved security for mobile computing • More collaboration between CIO and Lines of Business • More agency/headquarters collaboration on standards • More awareness of and support for FRA and DOT architectures