Architecture and Infrastructure Committee AIC Briefing to FOSE
Architecture and Infrastructure Committee (AIC) Briefing to FOSE 2003 April 9, 2003
AIC Objectives Integrate OMB and CIOC Architecture Efforts Develop (simpler) and Consistent Taxonomy and Terminology Facilitate Cross-agency efforts: common meta data, tools Oversee “operationalization” of architecture efforts A new subcommittee structure was developed to support these objectives 2
New AIC Structure Move from ad hoc efforts to priority and schedule-driven efforts with committed staff AIC Laura Callahan, DHS Governance John Przysucha, DOE Bob Haycock, FEAPMO • John Gilligan, USAF • Norm Lorentz, OMB Components Reynolds Cahoon, NARA Bob Haycock, FEAPMO Emerging Tech. Dawn Meyerriecks, DISA Mark Day, EPA Working Groups XML - Marion Royal, GSA; Owen Ambur, DOI PKI - Judith Spencer, GSA XML Web Services - Brand Niemann, EPA Universal Access - Susan Turnbull, GSA 3
CIO Council has established expectations for federal agency participation in AIC Agencies have begun designating senior-level representatives to the Governance and Components Subcommittees (25% time commitment per subcommittee). Volunteers have begun populating the Emerging Technology Subcommittee and its ongoing working groups. Subcommittee participation contributes to executive development objectives of CIOC. AIC products will benefit all agencies and accelerate achievement of CIOC goals 4
Enterprise Architecture Governance Subcommittee Leadership – John Przysucha, DOE; Bob Haycock, OMB Subcommittee Mission: n n Develop policy, direction and guidance by which the Federal Enterprise Architecture (FEA) is a driver of business process improvement, investment management, and technical decisions in order to institutionalize the FEA throughout Government Assist in implementing the FEA and other Enterprise Architectures (EAs) throughout Government Three Subcommittee Goals: 1. Integrate EA into the Government’s management processes 2. Define the alignment of department/agency EAs with the FEA 3. Describe how the FEA will facilitate the connection of State and Local EAs to Federal business lines and agency architectures Recent Progress: n Subcommittee members selected and subcommittee activated n FY 2003 work plan completed 5
Enterprise Architecture Governance Subcommittee Tasks Mission-related • Develop FEA Principles Goal 1: Integrate EA into the Government’s Management processes • Integrate EA into the Capital Planning and Investment Control Process • Integrate EA into the Strategic Management and Budget Formulation/Execution Processes • Integrate EA into the Project Management, Workforce Planning and Security Management Processes Goal 2: Define alignment of department/ agency EAs with FEA • Determine the major EA frameworks used by Federal agencies • Analyze how agencies align with the emerging FEA • Propose a federated FEA model that complements agency EAs Goal 3: Describe how the FEA will facilitate the connection of State and Local EAs to Federal business lines and agency architectures • • • Develop a Government Enterprise Architecture Framework Conduct a Joint Architecture Integration Pilot Conduct a Joint Component Directory/Repository Pilot Develop a Joint Government Data and Information Reference Model Identify new approaches to Joint Enterprise Software Licensing Conduct expanded Joint Architecture Integration Pilots 6
Components Subcommittee Leadership – Reynolds Cahoon, NARA; Bob Haycock, OMB Draft Subcommittee Mission: n Foster the identification, maturation, and re-use of enterprise architecture components and component-based enterprise architectures in Government Draft Subcommittee Goal: n Facilitate cross-Agency development and implementation of enterprise architecture components Recent Progress: n n Subcommittee members selected and subcommittee activated FY 2003 workplan completed; four tasks identified: w Develop a Components Based Architecture An Enterprise Architecture Component White is defined as "a self contained Paper business process or service w Develop a Components Registry/Repository Concept with predetermined functionality that may be exposed through a Paper business w Develop a Solution Development Life Cycle or technology interface. " w Develop and Market Quick Win 7
Emerging Technology Leadership – Mark Day, EPA; Dawn Meyerriecks, DISA Goal – Coordinate and guide technology tracking efforts of the federal government. Accelerate the implementation of commercially-developed technology resolving common challenges Initial Objectives n n To provide a clearinghouse function between industry and agencies To help discover and close technological gaps in the federal business and technology infrastructure Recent progress n Activation of the subcommittee n Development if initial draft 2003 work plan 8
Architecture and Infrastructure Committee Interrelationships Industry Inherently Governmental Functions Opportunities for Public-Private Interactions Priorities Governance PRM BRM Policy Recommendations Component Voids Components SRM TRM DRM Candidate Components Emerging Technology 9
FEA - Program Management Office Reference Model Release Schedule Performance Reference Model Business Reference Model Service Component Reference Model Data and Information Reference Model Technical Reference Model Federal Version Review General Release PRM 1. 0 Mid-April Early May BRM 2. 0 February 28 th Mid-April SRM 1. 0 January 29 th Mid-April DRM 1. 0 TBD TRM 1. 0 January 29 th Mid-April 10
Development of the Draft BRM, Version 2. 0 is nearing completion DRAFT Business Reference Model, Version 2. 0 Defense and National Security Services for Homeland Security Citizens Intelligence Operations Education Law Enforcement Energy International Affairs and Commerce Health Transportation Litigation and Judicial Activities General Government Correctional Activities Government Service Delivery Direct Services for Citizens Knowledge Creation Public Goods Creation and Mgmt Regulated Activity Management Legislative Relations Public Affairs Regulatory Creation Planning and Resource Allocation Supply Chain Management Human Resource Management Environmental Management Natural Resources Disaster Management Community and Social Services Economic Development Income Security Workforce Management Mode of Delivery Support Delivery of Services Management of Government Resources Financial Management Financial Vehicles Federal Financial Assistance Credit and Insurance Financial Transfers to States Controls and Oversight Revenue Collection Internal Risk Mgmt and Mitigation Administrative Management Information and Technology Management 11
The Draft BRM, Version 2. 0 aligns with three critical management frameworks / improvement initiatives The President’s Budget and Performance Integration Initiative and the FEA Performance Reference Model n n The revised model differentiates between the purpose of the government and mechanism/process used to deliver services to the customer This distinction aligns with the Performance Reference Model’s focus on outcomes (purpose of government) and outputs (mechanism/process) OMB’s Budget Function Classifications n These classifications provide a similar functional description of Federal activities JFMIP’s New Framework for Financial Management Systems n n Within the revised BRM, financial management is an element of the Lines of Business and Sub-functions throughout the four Business Areas The core processes of financial management - as defined by JFMIP - have been incorporated into the model’s Financial Management Line of Business 12
Within the Draft BRM, Version 2. 0, Mode of Delivery and Services for Citizens should be thought of collectively Services for Citizens Mode of Delivery What is the purpose of government? What “outcomes” is the government hoping to achieve? What mechanisms does the government use to achieve these outcomes? What are the “outputs” of these processes? With this relationship in place, all Government programs, agencies, mission-related IT systems, etc. , can be aligned to both a Service for Citizens and a Mode of Delivery 13
The Draft FEA Performance Reference Model (PRM): “At-A-Glance” w A standardized performance measurement framework designed to: n Enhance available performance information, WHAT IS n Better align inputs with outcomes, and THE PRM? n Identify improvement opportunities across organizational boundaries. w Agencies can use the PRM to select standard performance indicators—which may be new or coincide with those already in use—which can be tailored or “operationalized” to the specific environment. HOW WILL THE w The PRM can be integrated into the existing federal budget process. PRM BE w The PRM can mutually reinforce and work together with GPRA and current USED? PMA Budget and Performance Integration initiatives such as the PART, and Common Measures. WHAT IS THE PRM STATUS? w Currently in draft form, beginning the internal OMB review process. w Once approved in OMB, a Working Draft will be released for agency comment. w A final PRM will be released to use during FY 2005 budget formulation. 14
The PRM will help agencies identify the performance improvement opportunities that will drive Government transformation 15
The PRM structure is designed to clearly articulate “Line of Sight”—the cause and effect relationship between inputs, outputs and outcomes 16
The Draft Service Component Reference Model (SRM) framework is comprised of three inter-related service-oriented tiers – each of which describes capabilities in greater levels of granularity Service Domain The collection of business oriented service categories that align service / component capabilities to a level in which they support the objectives and performance of the business. Level of Granularity 7 Service Layers Service Types A collection of business-driven, service types (or categories) that assist the Service Layer in accomplishing of mission and/or performance objectives. 29 Service Types Service Components The collection of components and/or capabilities that support the Service Type. 163 Service Components 17
The SRM is a business-driven, functional framework that classifies capabilities (or service components) according to how they support business and performance objectives Access and Delivery Channels Business Process Performance Measures Cross-Cutting Service Areas (i. e. , Search, Security) Support Services Customer Services Service Types Process Automation Services Business Management Services Digital Asset Services Business Analytical Services Service Components Back Office Services Service Domain 18
The SRM is supported by multiple access and delivery channels that provide a foundation for accessing and leveraging the Service Component Accessing the Component (Example: Renewal of Drivers License ) Private/Public Partnership Mobile, Wireless Web Browser Kiosks PDA System to System Web Service EAI Other Access Channels (FEA-TRM) Phone, Fax Mail Face to Face Internet Portal Intranet Marketplace Extranet Exchange Peer to Peer Commerce Integration Delivery Channels (FEA-TRM) Service Level Agreement to structure how Service Components are accessed and leveraged Service Domains Service Types, and Service Components (FEA-SRM) 19
The SRM will assist in defining business process and performance gaps that may be leveraged to improve services to stakeholders (citizens, business partners, agencies) What level of process, performance, and outcome is the Service Component achieving? Does this help to close a performance gap? Access Channels (FEA-TRM) Delivery Channels (FEA-TRM) Business Process Performance Measures (FEA-PRM) Service Domains Service Types, and Service Components (FEA-SRM) 20
The Draft Technical Reference Model (TRM) is comprised of three technical tiers to support the construction, exchange, and delivery of service components FEA TRM Technical Tiers: Service Access and Delivery The collection of Access and Delivery Channels that will be used to leverage the Service Component, and the Legislative Requirements that govern it’s use and interaction Service Framework The underlying foundation and technical elements by which Service Components are built, integrated and deployed across Component-Based and Distributed Architectures. Service Platform A collection of platforms and specifications that embrace Component-Based Architectures and Service Component reuse How to leverage and access Service Components How to build, deploy, and exchange Service Components How to support and maintain Service Components 21
Service Access and Delivery How to leverage and access Service Components The TRM provides an effective means by which service components can be leveraged, built, and deployed across the Federal Government Access Channels Delivery Channels Service Framework Service Requirements Service Integration How to build, deploy, and exchange Service Components Service Interface / Interoperability Component Architecture Security Service Platforms Service Transport Presentation / Interface Business Logic Data Interchange Data Management Service Platforms How to support and maintain Service Components
The TRM will provide guidance and recommendations that support the development and implementation of service components that embrace a Component-Based Architecture Par tial Security Component Architecture Security - X. 509 - NIST / FIPS 186 - Secure Socket Layers (SSL) Presentation / Interface Business Logic Data Interchange Data Management - XBRL, JOLAP, OLAP - JDBC, ODBC - ADO, ADO. Net Data Interchange - XML - eb. XML - RDF, WSUI - XSLT Presentation / Interface - HTML - JSP, ASP. Net - DTHML, CSS, XHTMLMP Business Logic - Java/J 2 EE (EJB) - C, C++, Java. Script - COM/COM+, C# - Visual Basic List
The goal of the Draft Data and Information Reference Model (DRM) is to support investment and E-Gov planning by providing a framework in which agencies can leverage existing data components across the Federal Government Goals and Objectives: Promote horizontal and vertical information sharing between business lines Business-focused data standardization that can be categorized for re-use Re-Use and integration of data as opposed to duplication Enabler to support Crossagency collaboration Facilitate Cross-agency information exchanges Consistent means to categorize and classify data Integrated Enterprise Agency 1 State Agency 2 FEA-DRM Agency 3 Local Agency 4 24
The DRM framework provides a consistent method of categorizing and describing the data supporting the Business Lines and Sub-Functions of the BRM C onc e DRM Framework Focus Points Classifications FEA-BRM Criminal Suspects Will heavily leverage XML and interoperability principles Illegal Aliens Classifications of data will form the basis for the definition of business-driven XML Schemas Terrorist Activity Apprehensions XML Schemas will be stored within a central repository (e. g. . , XML. Gov, FEAMS) Security and data privacy are TOP priorities Will provide effective means to communicate with State and local governments al (Business Functions / Sub-Functions) Based on ISO 11179 Will leverage industry vocabularies ptu Events Law Enforcement Border Control Intelligence Gathering Anti. Terrorism 25
Questions and Answers
Contact Information 27
- Slides: 27
