1. eGovOS Panel Discussion CIO Council Architecture & Infrastructure Committee Subcommittee Co-Chairs March 15, 2004

2. Leading Government in a Digital World The challenge: More efficient interaction with government while reducing operating costs in an environment of increased security, privacy, and change The approach: Shift from incremental improvements to long-term strategic advantage Invest to achieve results … Nearly $60 billion (FY05) in IT to deliver benefits and services to citizens Advance to next level of E-Government by:  Ensuring agency operational structures are optimally defined in business and technology terms  Exploiting common functions and processes across government  Eliminating duplicative systems costly to maintain and interface To be an effective leader in today’s information-driven world, you must embrace technology.

3. FEA Framework Supports Federal IT Budget Decision-Making Categorization scheme that provides a standard view of IT investments Identifies cross-organizational initiatives and targets multi-year investments instead of single year expenditures FEA, Exhibit 53, and Exhibit 300 used collectively to evaluate proposed IT investments

4. FEA: Identifying IT Collaboration Opportunities Business Areas Line of Business Service Domain Service Type Service Area Service Category Service Standard Business Reference Model Service Component Reference Model Technical Reference Model Initiatives aligned to the same sub-function, service component, service specification, and performance measure are ideal candidates for business-focused collaboration within and across Agencies Service components and specifications that are most common are candidates for enterprise licensing 24 Presidential Priority E-Gov Initiatives Sub-function Service Component Service Specification Initiatives aligned to the sub-functions, service components, and service specifications of the 24 Presidential Priority E-Gov Initiatives are candidates for consolidation / cancellation Sub-function Service Component Service Specification Initiatives aligned to the same sub-function, service component, and performance measure are good candidates for business- focused collaboration within and across Agencies Measurement Areas Measurement Categories Performance Reference Model

5. Federal Line of Business (LoB) Initiatives Financial Management Federal Health Architecture Case Management Human Resources Management Systems Grants Management The end result saves taxpayer dollars, measurably reduces the administrative burden, and significantly improves service delivery beginning in FY2005.

6. EA Maturity Assessment Assessing how close agencies are to optimizing IT planning and investment decisions Learning how agencies are using FEA guidance framework to implement their EAs Understanding areas of maturity evaluation  EA development  Policy and process

7. FEAMS: Facilitating Cross-Agency Collaboration Federal Enterprise Architecture Management System (FEAMS) to enable agency information sharing Populated with agency business case data based on FEA reference model framework FEAMS in pilot phase and user group launched Feb. 12 Plan to link FEAMS and CORE to broaden agency access to IT investment data and facilitate application reuse

8. Architecture and Infrastructure Committee (AIC) supports the CIO Council’s strategic goals and objectives.* The Council works through the AIC to develop policy, direction, and guidance for the FEA to drive business process improvement, investment management, and technical decisions; and to institutionalize the FEA in concert with agency enterprise architectures. The AIC has established three working subcommittees on Governance, Components, and Emerging Technologies to carry out this work. * CIO Council Strategic Plan: FY 2004 (February 2004; http://cio.gov/documents/CIO_Council_Strategic_Plan_FY04.pdf) Strategic Goal: Effective cross-agency collaboration to maximize use of shared solutions and best practices Objective: Provide leadership and strategic direction for the definition, design, implementation, and governance of the Federal Enterprise Architecture (FEA)

9. The Governance Subcommittee is responsible for providing policy guidance, advice and assistance to define, design, and implement Enterprise Architecture (EA) discipline and practice throughout the Federal Government. Expected Outcomes Effective implementation of the FEA Alignment of agency EAs with the FEA reference models Identification of opportunities to collaborate on, consolidate, and/or cancel current and planned IT initiatives based on insights from the FEA Expansion of the FEA to include State and Local Governments for selected Federal Lines of Business Expected Outcomes Effective implementation of the FEA Alignment of agency EAs with the FEA reference models Identification of opportunities to collaborate on, consolidate, and/or cancel current and planned IT initiatives based on insights from the FEA Expansion of the FEA to include State and Local Governments for selected Federal Lines of Business FY 2004 Focus Areas Establish a community of practice for Federal agency Chief Architects Work with OMB to develop Federal agency guidance on the integration of IT capital planning and EA processes Work with the National Association of State CIOs to develop a Government Enterprise Architecture Framework FY 2004 Focus Areas Establish a community of practice for Federal agency Chief Architects Work with OMB to develop Federal agency guidance on the integration of IT capital planning and EA processes Work with the National Association of State CIOs to develop a Government Enterprise Architecture Framework

10. The Components Subcommittee is responsible for fostering the identification, maturation, use and reuse of Component-Based Architectures and architectural components in the Federal Government. Expected Outcomes Identification of business processes, service components, and technologies for reuse through analysis of the FEA reference models Reduction of IT costs for Federal agencies achieved through the reuse of business processes, service components, and technologies Rapid solution development through the reuse of components Rapid integration of disparate business services Development and implementation of e- Gov solutions based on Component- Based Architectures Expected Outcomes Identification of business processes, service components, and technologies for reuse through analysis of the FEA reference models Reduction of IT costs for Federal agencies achieved through the reuse of business processes, service components, and technologies Rapid solution development through the reuse of components Rapid integration of disparate business services Development and implementation of e- Gov solutions based on Component- Based Architectures FY 2004 Focus Areas Complete and publish Component White Paper and Component Life Cycle Guide to promote awareness and understanding of architectural components and their use Launch CORE.GOV, a cross- agency forum for component development, registration, and re-use Establish and launch an on- line resource for EA best practices for Federal, State and Local use FY 2004 Focus Areas Complete and publish Component White Paper and Component Life Cycle Guide to promote awareness and understanding of architectural components and their use Launch CORE.GOV, a cross- agency forum for component development, registration, and re-use Establish and launch an on- line resource for EA best practices for Federal, State and Local use

11. The Emerging Technology Subcommittee is responsible for identifying technologies with the potential to improve FEA value and quality, examining cross-cutting components, and developing recommendations for their use. Expected Outcomes Improved value and common understanding of the FEA Faster adoption of validated capabilities for FEA use, based on registry creation and pilot findings Better understanding of FEA tradeoffs as established and emerging technologies compete and converge Greater FEA valuation and longer component life cycles through market-based, open standards technologies and decreased usage of proprietary technologies Expected Outcomes Improved value and common understanding of the FEA Faster adoption of validated capabilities for FEA use, based on registry creation and pilot findings Better understanding of FEA tradeoffs as established and emerging technologies compete and converge Greater FEA valuation and longer component life cycles through market-based, open standards technologies and decreased usage of proprietary technologies FY 2004 Focus Areas Develop and implement processes for identifying and scanning for potential components, based on AIC priorities Develop and implement processes for evaluating identified components FY 2004 Focus Areas Develop and implement processes for identifying and scanning for potential components, based on AIC priorities Develop and implement processes for evaluating identified components

12. The Administration supports market-based solutions that embrace the ideals of competition, innovation and choice. Federal acquisition practices must:  Provide for consistent use of competition, well-structured contracts designed to produce cost-effective quality performance from contractors, and solid contract management  Ensure that taxpayer dollars are well managed, wisely used, and deliver positive results Agency acquisition decisions must be based on sound, integrated planning processes, that effectively:  Maximize the value and minimize the risks of IT investments  Promote the integration, interoperability and adaptability of IT investments, as well as management of their scale and flexibility  Ensure that IT investments contribute measurable results to mission performance

13. Q & A