refinement of the one gsa day one january 27, 2005
TRANSCRIPT
![Page 1: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/1.jpg)
Refinement of the One GSA
Day One
January 27, 2005
![Page 2: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/2.jpg)
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
![Page 3: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/3.jpg)
P A G E 3
One-GSA
H.R.Finance
Marketing
PBS
FTS
FSS
Sch
edule
s
Build
ings
I.T.
Tele
com
s
One-GSASolutions
GSA Stovepipes
Un-Architected Solution Architected Solution
Auto
Supplie
s
![Page 4: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/4.jpg)
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 ForneckerGSA CTO
![Page 5: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/5.jpg)
P A G E 5
The “One GSA” Methodology
Value Chain Analysis
Model Driven Architecture
On Service Oriented
Architecture
= Executable EA+
![Page 6: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/6.jpg)
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
![Page 7: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/7.jpg)
P A G E 7
Value Focused Target Architecture
One GSA Target EA
Time LineTrends
Critical Success Factors
Time LineTrends
Critical Success Factors
ProjectsProjects
Business ModelsBusiness Models
WorkflowWorkflow
I.T. Systems SpecsI.T. Systems Specs
Collaborative EnvironmentCollaborative Environment
Documentation &TrainingDocumentation &Training
Business DriversBusiness Drivers
Current ProcessesCurrent Processes
FARFAR
Current EnvironmentCurrent Environment
TrendsTrends
InitiativesInitiatives
![Page 8: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/8.jpg)
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
![Page 9: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/9.jpg)
P A G E 9
Strategic Migration to Reusable Components
Separate and Non-Interoperable Applications
Ad Hoc Point to Point Integration of Monolithic Systems
Systems Composed of Interoperable Components
Standards based integration of Monolithic Systems
Customer Focused Domain Models Drive Agile Systems of Interoperable Components
•You are here
![Page 10: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/10.jpg)
P A G E 10
EA Governance Structure
One GSA Target EA
OMB - 300Initiative
EA Governance
Acquisition
Business Drivers
•Guides
•Refines
Specifies
•Satisfies
![Page 11: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/11.jpg)
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
![Page 12: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/12.jpg)
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 Develop and
Deliver Provide
After Care
Acquisition Value Chain
Marketing
Development of Government-wide Policy
![Page 13: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/13.jpg)
P A G E 13
VC + MDA = One GSA
Value Chains and MDA offer two organizationally agnostic viewpoints of the same enterprise
Value Chain
Process
Process
Process
Activity
Activity
Activity
Activity
Activity
Activity
Activity
Activity
Activity
.
.
.
One GSA
Collaboration
Role
Collaboration
CollaborationRole
Role
Role
Role
Role
Role
.
.
.
•VC •MDA
![Page 14: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/14.jpg)
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
•Org
•a
•b
•c
•d
•Role•Role•Role
•Role•Role•Role
•Role•Role•Role
![Page 15: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/15.jpg)
P A G E 15
Composition of the target model
One-GSA Target Model
Acquisition Get it right focus
Finance
Marketing
TransitionPlan
HR
Policy
I.T.
Project Management
Facilities Management
Buy from stock
Solutions Provisioning
Value ChainsProcesses
CollaborationsRoles
![Page 16: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/16.jpg)
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
Service
Serv
ice
Ser
vice
One-GSA Target Model
![Page 17: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/17.jpg)
P A G E 17
Legacy “Wrapping”Legacy “Wrapping”
Wrapping allows existing programsWrapping allows existing programsand data to work with and workand data to work with and workas enterprise components.as enterprise components.Legacy systems are wrapped asLegacy systems are wrapped asa set of services.a set of services.
Adapters
Legacy
EnterpriseServices
LegacyServices
![Page 18: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/18.jpg)
P A G E 18
Understanding the models
• Roles
• Collaboration
• Activities
• Protocols
• Documents
• Value chains
• Value chain processes
![Page 19: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/19.jpg)
P A G E 19
Collaborations Contextualize Roles
![Page 20: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/20.jpg)
P A G E 20
Example collaboration and roles
![Page 21: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/21.jpg)
P A G E 21
RolesRoles Compose
Inner RolesInner Roles - Specify Service Granularity
![Page 22: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/22.jpg)
P A G E 22
Protocols Organize InformationInformation Choreographed by Roles
![Page 23: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/23.jpg)
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
![Page 24: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/24.jpg)
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
![Page 25: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/25.jpg)
P A G E 25
Roles Choreograph Value Chain Activities
![Page 26: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/26.jpg)
P A G E 26
Enterprise Collaboration Architecture (ECA)
Implementation
Net
Hardware
OperatingSystem
Middleware Framework,& Container
Interaction Path
Component in Role
Interaction(With Information)
Role
Collaboration
![Page 27: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/27.jpg)
P A G E 27
One-GSA Collaborative Acquisition Environment (CAE)
Helping get acquisition right
![Page 28: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/28.jpg)
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
![Page 29: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/29.jpg)
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
![Page 30: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/30.jpg)
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.
![Page 31: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/31.jpg)
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
![Page 32: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/32.jpg)
P A G E 32
The EcosystemAgencies GSA Vendors
I.T. ComponentsI.T. Components
I.T. ComponentsI.T. Components
I.T. ComponentsI.T. Components
Collaborative Acquisition Environment Model
Components derived directly from the CAE model facilitateCollaborative Acquisition – getting it right
Legacy & SharedData
Legacy & SharedSystems
![Page 33: Refinement of the One GSA Day One January 27, 2005](https://reader030.vdocuments.mx/reader030/viewer/2022032707/56649e215503460f94b0dc66/html5/thumbnails/33.jpg)
P A G E 33
CAE Model Deliverables
Collaborative Acquisition Environment Model
Training
Service Oriented
Architecture Interfaces
Component Implementations
FEA Compliance
WorkflowSpecifications
Use of “Model Driven Architecture” technologiesProduces real and valuable products from the model