Refinement of the One GSA Day One January 27, 2005

P A G E 2 One GSA Initiative GSA wants to move from a current fragmented set of processes and systems to a unified target architecture

P A G E 3 One-GSA H.R. Finance Marketing PBS FTS FSS Schedules Buildings I.T. Telecoms One-GSA Solutions GSA Stovepipes Un-Architected Solution Architected Solution Auto Supplies

P A G E 4 EA Value Proposition for GSA Facilitate process changes that will make GSA easier to do business with – improve agility Reduce cost by eliminating duplicate systems and reducing cost of maintaining remaining systems - cost alignment rather than cost cutting Improve GSA’s service performance levels and the availability of common/shared resources Provide a common point of departure for future strategic analyses EA methodology is the means to achieve the One GSA vision Christopher Fornecker GSA CTO

P A G E 5 The “One GSA” Methodology Value Chain Analysis Model Driven Architecture On Service Oriented Architecture = E xecutable EA +

P A G E 6 Definitions Enterprise Architecture (EA) – defines the business, the information necessary to operate the business, the technologies necessary to support the business operations, and the transitional processes for implementing new technologies in response to the changing needs of business Value Chain Analysis (VCA) – an enterprise wide collaboration model that aligns processes and activities with respect to value generation for GSA’s customers, taking into account competitive alternatives in the market place Model Driven Architecture (MDA) – an approach to building models about your business, the architecture that supports your business, and the technology you use to implement the architecture. MDA allows you to build separate business and technology models and integrate and simulate them to dynamically visualize the impacts to your business

P A G E 7 Value Focused Target Architecture One GSA Target EA Time Line Trends Critical Success Factors Time Line Trends Critical Success Factors Projects Business Models Workflow I.T. Systems Specs Collaborative Environment Documentation &Training Business Drivers Current Processes FAR Current Environment Trends Initiatives

P A G E 8 Architecture Goals A scalable and robust enterprise architecture Driven by business needs and processes Loosely coupled enterprise components Support for FEA Capital Planning and governance Support for Systems Engineering Support for componentized acquisition Enable rapid provisioning of solutions –Simple, reproducible processes supporting reuse Agnostic from –Organizational Structure –Technology –Systems Environment Enable the integration and collaboration of multiple –Agencies, Business units (internal and external) –Suppliers –Systems, Technologies

P A G E 9 Strategic Migration to Reusable Components Separate and Non-Interoperable Applications Ad Hoc Point to Point Integration of MonolithicSystems Systems Composed of Interoperable Components Standards based integration of MonolithicSystems Customer Focused Domain Models DriveAgile Systems of Interoperable Components You are here

P A G E 10 EA Governance Structure One GSA Target EA OMB - 300Initiative EA Governance Acquisition Business Drivers Guides Refines Specifies Satisfies

P A G E 11 One GSA EA Project Scope Produce a One GSA Enterprise Architecture that: –Includes a target vision for One GSA EA –Will contribute to a green light from OMB –Provide a basis for identifying business improvement opportunities –Provides the basis for a sequencing plan –Provides the foundation for further architecture detail –Establish a reference architecture that will both guide and be refined by further efforts to realize One GSA

P A G E 12 One GSA EA Value Chains Shared Services Value Chains I.T. Services Financial Management Services Human Capital Services Plan and Design Develo p and Deliver Provi de After Care Acquisition Value Chain Marketing Development of Government-wide Policy

P A G E 13 VC + MDA = One GSA Value Chains and MDA offer two organizationally agnostic viewpoints of the same enterprise VC MDA

P A G E 14 Roles, Activity and the organization Roles are an organizationally agnostic way to organize business processes Organizational units, people and systems are the actors playing roles Role

P A G E 15 Composition of the target model One-GSA Target Model Acquisition Get it right focus Finance Marketing Transition Plan HR Policy I.T. Project Management Facilities Management Buy from stock Solutions Provisioning Value Chains Processes Collaborations Roles

P A G E 16 Enterprise Components in SOA Enterprise Components must be independent & loosely coupled While being able to interoperate with each other using services Making the information system a lattice of cooperating components Simulated or real Representing both business and technology components Driven from the business model Providing an “Enterprise service bus” using a services oriented architecture Service One-GSA Target Model

P A G E 17 Legacy “Wrapping” Wrapping allows existing programs and data to work with and work as enterprise components. Legacy systems are wrapped as a set of services. Adapters Legacy Enterprise Services Legacy Services

P A G E 18 Understanding the models Roles Collaboration Activities Protocols Documents Value chains Value chain processes

P A G E 19 Collaborations ContextualizeRoles

P A G E 20 Example collaboration and roles

P A G E 21 Roles Compose Inner Roles- Specify Service Granularity

P A G E 22 Protocols Organize Information Choreographed by Roles

P A G E 23 Fully Elaborated Protocols – DRM IEP Focus is on business collaboration information - not on technology representation, or ODS information model This is an example of a ‘Purchasing’ Protocol with various inner Protocols and their Types specified Inner Protocols are sub- conversations, and they can be reused in other Protocols or as top- level Protocols This is an organizing framework for data entity composition and categorization, ala the DRM Information Exchange Package (IEP) idea

P A G E 24 Collaboration Data – DRM Business Context FulfillmentNotice -Document Object as Business Information Entity that provides collaborative context to Core Data Components Includes Composition, Type and Cardinality May be derived from existing sources and mapped to any DRM Representation (Java Object, XML Document) GOAL is to link the ODS ERD to the SQL query executed by a ‘component in role’ on behalf of a specific business process collaboration

P A G E 25 Roles Choreograph Value Chain Activities

P A G E 26 Enterprise Collaboration Architecture (ECA) Implementation Net Hardware Operating System Middleware Framework, & Container Interaction Path Component in Role Interaction (With Information) Role Collaboration

P A G E 27 One-GSA Collaborative Acquisition Environment (CAE) Helping get acquisition right

P A G E 28 The Collaborative Acquisition Environment The CAE is people, organizations & systems working together to achieve fair, open and effective federal acquisition The cornerstone of CAE is the FAR, the FAR is the normative specification of acquisition The FAR and associated business processes, information, roles and interactions are formalized in a standards based business model of acquisition Information technology will help facilitate acquisition with workflow, information resources, training and business rule enforcement based on the CAE model

P A G E 29 What will CAE Achieve? The acquisition process will be; –More Streamlined – due to automation and integration of resources –More Reliable – business rules and processes are “baked in” to the CAE –Less Costly – due to less duplication, confusion and risk –More Open – since there is no required centralized system

P A G E 30 How does the CAE Help GSA? The roles GSA plays in federal acquisition become better defined and understood GSA will provide acquisition services through the CAE CAE will assist in achieving a “One GSA” since it will align acquisition processes and resources GSA will be the source of the CAE business model as well as the components and services to realize it GSA will not only “get it right”, it will support other agencies getting it right.

P A G E 31 What is the CAE Approach? Use of industry standards for “Model Driven Architecture” to capture the federal acquisition business models Identification of the roles, responsibilities and interactions of federal acquisition Mapping of these roles to open technology components for implementation Hosting of information resources on agency resources or on shared resources Support “wrapping” of existing systems as CAE nodes or creating new application components Providing (open source?) components that implement the CAE model Providing products and services to assist agencies in supporting the CAE

P A G E 32 The Ecosystem AgenciesGSAVendors I.T. Components Collaborative Acquisition Environment Model Components derived directly from the CAE model facilitate Collaborative Acquisition – getting it right Legacy & Shared Data Legacy & Shared Systems

P A G E 33 CAE Model Deliverables Collaborative Acquisition Environment Model Training Service Oriented Architecture Interfaces Component Implementations FEA Compliance Workflow Specifications Use of “Model Driven Architecture” technologies Produces real and valuable products from the model