EPA Enterprise SOA Strategy Progress Update

1
EPA Enterprise SOA StrategyProgress Update

• September 25, 2006

2
Recap Purpose of the EPA Enterprise SOA
Strategy Task and Key Deliverables

• OEI is developing the EPAs Enterprise SOA
  Strategy to address the challenges and capitalize
  on the opportunities that SOA presents
• Service Oriented Architecture (SOA) is a new way
  of planning and integrating complex IT systems,
  business processes, and even whole enterprises to
  get the most bang for the buck
• SOA is causing a sea change in government as well
  as commercial markets worldwide bigger than the
  one Client-Server caused
• Key deliverables will include an EPA-approved SOA
  strategy document, related briefing materials,
  and an executive-level briefing
• SOA Business Demand Assessment
• SOA Sourcing Strategy
• SOA Governance Strategy

3
Recap What Will the EPAs Enterprise SOA
Strategy Address?
SOA BUSINESSDEMAND ASSESSMENT
SOA SOURCING(SUPPLY) STRATEGIES
SOA GOVERNANCESTRATEGY

• EPA SOA Business Strategy and Goals
• How proposed strategy helps meet EPAs
  business goals
• Define SOA in relation to the EPAs Enterprise
  Architecture
• Define SOA in terms of the FEA and SCBA
  whitepaper

• SOA Development strategy and major components
  to be developed
• SOA Infrastructure Review
• SLA Strategy
• EPA SOA Transition Strategy
• Funding Strategies
• Outreach
• SOA Best Practices

• IT Governance Impacts
• Central vs. Distributed ownership of SOA
  technologies
• SOA and the SDLC
• Governance process for standards
• Governance for web services implementations
  across the EPA
• Roles for existing EPA workgroups and
  committees

4
Schedule Update
Wk 1
Wk 6
Wk 7
Wk 8
Wk 9
Wk 10
Wk 11
Wk 2
Wk 3
Wk 5
Wk 4
SOA Strategy Development
We are Here
Award
Kickoff Meeting
1-1 Kick-off

• Identify key stakeholders
• Meet with EPA management to discuss scope and
  objectives
• Define deliverables
• Detail the approach to task deliverables
• Hold Kickoff Meeting

1-2 Review Materials and Interview Participants

• Rough Strategy Report
• Initial Briefing

• Interview Stakeholders
• Review EPA Materials

Post Briefing Report
1-3 Rough Strategy and Initial Briefing

• Develop Draft SOA Strategy
• Present Strategy, capture issues

• Updated Briefing
• Draft Strategy Document

1-4 Update briefing, prepare Draft document

• Final Document
• Executive Brief

• Resolve issues
• Update Strategy

1-4 Finalize Strategy

• Produce Final SOA Strategy Document
• Produce Executive-Level Brief

Periodic Meeting Summaries
2.3 Status Meetings and Summaries
5
SOA Strategy Contents

• Executive Summary
• SOA Strategy Framework
• Key SOA Concepts
• Value and Benefits of SOA
• 5 Stages of SOA Value
• SOA Adoption Lifecycle
• EPA SOA Demand Assessment
• Customer and Stakeholder Needs
• Business Services that Fulfill Needs
• Enabling Services that support Business Services
• EPA SOA Sourcing Strategy
• SOA Reference Specification Strategy
• SOA Transition Management Strategy
• EPA SOA Governance and Management Strategy

FOCUS OFDISCUSSIONSTO DATE
FOCUS OFFUTUREDISCUSSIONS
6
How Can the EPA Use SOA to Achieve Strategic
Value?
7
Customer Concerns (What Must Be Done) Should be
Separated From Provider Concerns (How It Gets
Done)
5 STAGES OF SOA VALUE gtgt STAGE 1 ALIGNED
STAKEHOLDERS
DEMANDSIDE
SUPPLYSIDE
Value
Customers Stakeholders
Components
Services
Services deliver valueto customers stakeholders
Customers receive services
Components provide services

• Demand Profile (What Must Be Done)
• Functionality
• Customer
• Outputs
• Interface/ delivery channels
• Metrics
• Cost/ affordability
• Service Level Agreements (SLA)
• Risk tolerance
• Governance
• Change management
• Sign-up / separation agreements

• Supply Profile (How It Gets Done)
• Sourcing
• Make/ buy component parts
• Reuse
• Assembly of Component Parts
• Orchestration among parts
• Harmonization of data
• Dependency chains (recursion)
• Deployment
• Sequencing plan
• Legacy wrapping
• Operations

8
Complex Services Should be Decomposed so that
they can be Sourced with Cheaper, Commodity
Components
5 STAGES OF SOA VALUE gtgt STAGE 2 LOWER COSTS
9
The Value of Services to Stakeholders Should be
Clearly Traceable in Order to Substantiate SOA
Investments
5 STAGES OF SOA VALUE gtgt STAGE 3 ENHANCED
CAPABILITIES
DEMAND SIDE
SUPPLY SIDE
CUSTOMERSAND STAKE-HOLDERS
RESULTS
SERVICES
COMPONENTS
ElementaryComponents(Manual or Automated)
Aggregate Components
Vision / Strategies
ServiceCapabilities
Needs /Imperatives
ServiceRequirements
Objectives
OrganizationalComponents
IT SystemComponents
Req. r1
Capability c1
Automated A1
Req r2
Capability c2
Need n1
Objective o1
Req r3
Automated A2
Capability c3
Org 1
System S1
Need n2
Strategy X
Customer X
Req r2
Automated A1
Capability c2
Need n3
Objective o2
Req r4
Automated A2
Capability c4
Need n4
Req r5
Capability c5
Objective o3
Need n5
System S2
Automated A3
Org 2
Req r6
Capability c6
Objective o4
Need n6
Strategy Y
Stakeholder Y
Req r1
Automated A1
Capability c1
Need n4
System S1
Req r4
Automated A2
Capability c4
Objective o5
Need n7
Req r7
Org 1
Manual M1
Capability c7
Need n8
Req r4
Automated A2
Capabilty c4
System S1
Req r2
Capability c2
Automated A1
10
5 STAGES OF SOA VALUE gtgt STAGE 4 INCREASED
EFFICIENCY
Sharing Mechanisms Should be Instituted in Order
to Overcome Organizational Barriers to Sharing
Laissez Faire
Center of Excellence
Shared Service
Autocratic
Federated

• All IT responsibilities and resources in
  divisions
• Minimal enterprise coordination
• Few standards or architectures
• No CIO, or CIO purely a staff role

• Most IT responsibilities and resources in
  divisions
• Divisions coordinate efforts when efforts benefit
  individual organizations
• Minimal standards common architecture for
  coordinated efforts
• CIO facilitates cooperation among divisions

• Mix of resources between divisions and cross
  division centers of excellence
• Enterprise coordination in areas determined to be
  strategic
• Enterprise standards and architecture to
  facilitate cooperation and data sharing
• CIO manages centers of excellence and coordinates
  strategic planning

• Services provided to divisions for a fee and
  subject to Service Level Agreements
• Core services managed by enterprise
• Compliance to enterprise standards and
  architecture imposed by shared services
• CIO runs shared services as a distinct business
  offering

• All resources and priorities controlled
  centrally
• Enterprise sets priorities for divisions
• Standards and architecture enforced by central
  group
• CIO runs central group

Decentralized
Centralized
11
Governance and Management Processes Should be
Tuned to Facilitate SOA Adoption
5 STAGES OF SOA VALUE gtgt STAGE 5 HIGHER QUALITY

• EPA-Wide SOA Planning
• Identify SOA opportunities
• Prioritize SOA opportunities based on value
• Plan SOA sourcing activities based on priorities
• Individual Service Lifecycle Management
• Service Planning (Roadmaps)
• Service Sourcing
• Acquisition
• Assembly
• Quality Assurance
• Deployment
• Service Operation

12
SOA Can Deliver Compelling Value to the EPAs
Leaders by Helping them to Address Key Challenges

SOA DEMAND ASSESSMENT
13
In Order to Address the EPAs Key Challenges,
Changes Need to be Made to the EPAs Services
SOA DEMAND ASSESSMENT
BUSINESSSERVICES
COMMON ENABLINGSERVICES
TECHNOLOGYSERVICES
Summary
EPA BRM LOBsand Sub-Functions
EPA TRMServices
OEI Toolbox
Granularity
EPA BusinessProcesses
OEI ToolSolutions
Notional SolutionArchitecture Services
Detailed
ElementaryBusiness Services
ElementaryEnabling Services
ElementaryTechnical Services
Applicability
Specialized
Generalized
Shaded areas indicate service profile information
not yet discovered during SOA strategy assessment
14
Next Steps

• Information gathering sessions with OEI
  stakeholders
• Questionnaire for Web Services Working Group
  members
• Refinement of Demand Assessment based on above
  input
• Sourcing and Governance Strategies discussions
• Rough Strategy document