Service-Oriented Government
Mark Johnson
Director Consulting, CGI-AMS
Timothy Davis
Senior Solution Architect Manager, Oracle
September 12, 2006
Agenda
Government Under Pressure
SOA Concepts & Maturity Model
Trends and Developments
SOA in Government
The Path to Successful SOA
2
Government Under Pressure
Nothing stimulates the
imagination like a budget cut.
Sign on the desk of former
PA Budget Director
3
Government’s Business Transformation Imperative
Whether the organization requires dramatic changes or
incremental improvements, managing government modernization
in the face of growing constraints requires a new way of thinking.
Demands
Rising customer expectations
Political pressure/visibility
New and expanding scope and mandates
Government Imperative
Constraints Spend less, but spend smarter
Reduced budgets Improve service to customers and
Government personnel shortage internal users
Aging infrastructure Reduce total cost of ownership
Get the most out of investments
New Technology Enablers
already made
Open standards
Inexpensive computing
Pervasive computing
4
National Priorities
Governors
Fix systems
Improve efficiencies, become more
adaptive, and measure success
Get a handle on healthcare
Especially Medicare
Transform, modernize and
restructure government
CA Performance Review
WA Competitive Council
MN Drive to Excellence
5
Transforming Government
I plan a total review of government - its
performance, its practices, its cost. …
Every governor proposes moving boxes
around to reorganize government. I don't
want to move boxes around; I want to
blow them up.
Governor Arnold Schwarzenegger, State of California
The future is coming at us faster than it ever has.
It's a tidal wave of change. If we don't get on top
of it and ride it, it will drown us … We need to
make government both leaner and more effective,
and we can do both.
Governor Tim Pawlenty, State of Minnesota
6
Summary
An organizational problem looking for a
business solution – not an
integration problem looking for a
technology solution
7
SOA Concepts & Maturity Model
"Things should be made as
simple as possible, but no
simpler."
Albert Einstein
8
SOA – Historical Progression
Separate Distributed Application Web SOA
Applications Applications Integration Services
Tightly Coupled Loosely Coupled
Application Focus Business Process Focused
Silos and Stovepipes Enterprise View
Inflexible to changes in Very agile and flexible
business process or
market conditions
9
A service …
Is a unit of work done by a service provider to
achieve results for the service consumer Service Consumer
Is a software component that is capable of
providing access to functions and data
Service
Is exposed to other components via a service Service Interface
description Service
Implementation
Appears as a ―black box‖ to the service Service
consumer Business
Logic
Is interacted via message exchanges
Encompasses a business perspective Service
Private Data
Decouples its interface from its implementation
Is built to last Service Provider
10
Service-Orientation
Service Orientation
Use of ―open‖ interoperability protocols that facilitate application
assembly based solely on service descriptions and organized in
a way that supports the dynamic discovery of appropriate
services at run time
Architecture
A process of putting together components to achieve some
overall goal
A blueprint that comprises the components organized by layers,
their visible properties, their relationships and interactions, and
constraints
A discipline that addresses cross-cutting concerns to manage
complexity and encourage holistic thinking
11
SOA - Bringing Business and IT Together
A solution and architectural design approach…
…whereby business activity
…which is implemented within
+
components are packaged as
an architectural
well-defined services,
technology framework
accessible electronically by
optimized for this purpose
partners, suppliers and others
Business Focus Technology Focus
12
Business Value of SOA
Agility & Accelerated Delivery
Separation of business process logic and business rules from
applications
Business processes can be changed easily
Shorter time-to-deployment for changed processes
Reduced Cost
Consolidation of infrastructure leads to fewer components and
hence reduced initial cost and license
Simpler infrastructure management
Higher Quality
Eliminating redundancy reduces inconsistent data and
inconsistent behavior
Use of open standards and well-defined architectural constructs
leads to better understanding
13
Challenges
Organization & Governance
New processes in which many different IT and business players have a role
Defining and validating services, Managing reuse
Allocating costs - Who pays?
Core funding from a central authority vs. Usage based billing for common services
Free market to allow best services to survive vs. Forced monopoly to minimize overall
costs
Architecture
Requires development discipline and methodologies that must be defined and
enforced
Software
Need to invest in tools and technology to service-enable established IT assets
Lack of SOA Expertise and Experience
Few mature SOA methodologies
14
Traditional Model
A Vertically Integrated Approach
Historically, each department/agency had a vertically integrated
approach to application, data, processes, and technology
Gaps in
enterprise-wide
business
processes
Functional
redundancy
Monolithic
applications
Data
Technology redundancy
inefficiencies
Technological
stagnation
15
16
End
Users
Users
Citizens
Providers
Government
SOA Example
IVR/PBX/ACD/CTI Portal
Middleware
Service Delivery Framework
Composite State-Wide Applications
Child
TANF Child Care SACWIS
Support
Health and Child Juvenile
MMIS
Nutrition Support Justice
Content Screening and
Management Intake
Output Participant
HHS Reference Architecture
Management Management
Provider
Workflow
Management
Business Resource
Intelligence Management
Search Financial
Management
Rules Engine Asset
Management
Enterprise Security
Enterprise Management
Audit Eligibility
Hardware and Software Platform
Evidence
Alerts
Management
Infrastructure Services
Common HHS Services
ETL Workload/Staff
Management
Enterprise Service Integration (ESB)
Legacy
Integration Courts
CRM Rev Max
Electronic Case
Payment Management
Service
Directory
Development Framework
Platform, Tools and Methodolgoies
Business Transformation Tools and Methodologies
SOA Example
HHS Reference Architecture
Create value-add Expose application
composite services and/ business components
or applications using as services
common HHS services
Enterprise Security
End
Users Common HHS Services
Business Transformation Tools and Methodologies
Juvenile
Support
Justice
Child
Workload/Staff
Screening and
Management
Management
Management
Management
Management
Management
Management
Management
Composite State-Wide Applications
Participant
Resource
Evidence
Platform, Tools and Methodolgoies
Financial
Rev Max
Portal
Eligibility
Provider
Courts
Intake
Asset
Case
Development Framework
Providers Service Delivery Framework
SACWIS
Support
Child
Enterprise Service Integration (ESB)
Service
Child Care
Rules Engine
Management
Management
Intelligence
Integration
Electronic
IVR/PBX/ACD/CTI
MMIS
Workflow
Directory
Business
Payment
Content
Legacy
Search
Output
Alerts
Audit
CRM
ETL
Middleware
Government
Users
Health and
Nutrition
TANF
Infrastructure Services
Citizens
Enterprise Management
Hardware and Software Platform
Leverage common HHS Leverage shared Externalize HHS
services for developing enterprise services business rules into a
business processes using rules engine
17 service orchestration
Centralized vs. Federated
A successful SOA requires both centralized
and federated components
Singular vision & goals, governance,
Local
enterprise repository management, and Rules
many operational functions should be State
Rules
centralized Federal
Rules
Service development should be federated to
the producing units
Allow for local units to override/extend business
rules (rules are hierarchical in nature – federal,
state, local)
18
SOA Maturity Model
Enterprise governance, continuous
improvement
Ongoing business process evaluation and
re-engineering
Full business processes via SOA, enhance
and extend business processes
SOA architecture leadership, technology
standards
Integrate SOA in development processes
Apply SOA to immediate organizational
needs
Initial SOA projects, create service
definitions
19
Trends and Developments
―A good leader is someone
whose troops will follow him, if
only out of curiosity.‖
Gen. Colin Powell
20
Gartner Hype Cycle
21
Gartner
SOA is transformational, 5-10 years to mainstream adoption
SOA is inevitable
Core of successful transition to SOA in the public sector
Set realistic expectations of costs and benefits
Especially with the business and policymakers
Key is coordinating applications and divisions within IT
Managing metadata, resolving data vs. process tensions, adopting
SOA-aware platform tools
22
Gartner
By 2008
Leading vendors will offer extensible platform technologies using
pluggable SOA-style design in their internal architecture (0.7
probability)
By 2010
More than 50 percent of large organizations will have established
a composition portfolio for SOA in their journey toward a business
process platform (0.7 probability).
In 2006
Lack of working governance mechanisms in midsize-to-large
(greater than 50 services) post-pilot SOA projects will be the most
common reason for project Failure (0.8 probability).
23
IDC and Aberdeen
IDC report
SOA spending will reach $8.6 billion in 2006—a 138 percent
increase from 2005, when spending totaled $3.6 billion.
By 2010, IDC estimates companies will spend upwards of $33 billion
on SOA services
Aberdeen Group
From 2006 to 2010, SOAs could help Global 2,000 corporations save
up to $53 billion in IT costs
SOA can help save up to 25% on application development costs
when used over the entire development life cycle
24
SOA in Government
―Gentlemen, we have no money,
… therefore we must think.‖
Lord Rutherford
25
SOA Examples – City Government
Local Government - Citizen services
DCStat (http://www.adtmag.com/print.aspx?id=18271)
Integrates data stored on individual systems
150 data sets, crime statistics, city services
requests, geographic features, etc
Analyzes data to reveal patterns and trends
Notifies city officials of potential problems
SOA architecture
Integration with a agency legacy systems
J2EE backend, .NET as the presentation
Benefits
Improved services
Reduced costs
Level 1, with aspects of Level 2 & 3
Integrated SOA in development processes
Integration with externals, Enhanced business processes
26
SOA Examples – County Government
County Government – Legacy Assets
Miami-Dade County
Majority of applications on mainframe
Leveraged SOA to expose legacy
applications
Standardized access to Property Tax System
Answer Center Project
Allows the public call, fax, email or enter queries
over the web for any issue
Single access point
Extensive integration with legacy systems
Benefits
Improved customer service levels
Reduced costs
Level 1, with aspects of Level 2 & 3
Integrated SOA in development processes
Integration with externals
27
SOA Examples – State Government
Human Services – Child Welfare
Wisconsin & DC SACWIS
Systems built with web services
Inter-application functionality
External agency integration
Mobile device integration
Potential for value-add services
Master Data Management
Common eligibility determination
Benefits
Flexibility and responsiveness
Reduced Cost
Level 1, with aspects of Level 2 & 3
Integrated SOA in development processes
Integration with externals
28
SOA Examples – State Government
Enterprise State Government
California Enterprise Architecture Program
SOA a key component (segment) of the
Enterprise Architecture
SOA Blueprint that supports business
Defined SOA principles and Established SOA
Center of Excellence
SOA leadership, governance, and management
of components
Expected Benefits
Reduced total cost of ownership
More responsive to changing business
requirements, reduce the time to develop
new applications
Attempting level 4/5
Enterprise governance, tracking performance
Full business processes via SOA
29
SOA Examples
Federal Government
The Customer The Business Problem
• Market study for SOA platform
• US-Visit is an evolving program
administered by the
• Point of entry screening
Department of Homeland
system that required
Security
integration to multiple systems
including MQ Series
• Captures biometric information
of most non-US citizens going
through specific Ports of Entry Key Takeaways
(PoE)
• Completeness of SOA solution
• http://www.dhs.gov/dhspublic/i
and ease of use
nterapp/content_multi_image/c
ontent_multi_image_0006.xml • Gov’t preference of ease of
integration to Oracle DB
• Extremely Scalability Issues
Resolved with Benchmark
30
SOA Examples
Federal Government
The Customer The Business Problem
• Project: Traffic Flow
• The FAA is responsible for Management Modernization
regulating civil aviation in the Project (TFM-M)
United States to promote safety
• Need to process 17,000
• http://www.faa.gov/ transactions/minute
• Decision maker: CSC Program • CSC already prototyping a
Manager, FAA TFM-M Program 100% proprietary Integration
Manager solution involving:
•ProActivity
•BEA WL Platform
Key Takeaways •CA-Entrust
Complete SOA Oracle stack •Oracle DB
•Business Objects
lowers time-to-completion
Application Server EE,
Discoverer, Portal, BPEL PM,
BAM
31
SOA Examples
Federal Government
NAVSEA Current Implementation Timeframe:
September 16, 2004 - Live with 2,500 users and involves about
(Derived from: Conversation with Dave Scheid, 20-25 apps. Using Plumtree Portal and Active
NAVSEA Port Hueneme and W White.) Directory.
Organization deploying: Naval Surface Warfare - Plan is to then rollout to other warfare centers
Center (NSWC) under NAVSEA in FY06 and 07 (one year’s time), to around
15,000-20,000 users.
Goal: to have a seamless data flow from people
who create infomation to the people who Use of Oracle COREid
consume it—i.e. the sailor on the deck plate NAVSEA is most interested in the access control
who requires tech procedure and knowledge portion and to set up policies for individuals to
to his job. Tech procedure are created on the access thee different applications.
shore. Flow must be seamless between - They want SSO as well as the logging
capability for security concerns.
Creation of information
In the future, they will likely adopt a federated
Publication of information
model to share access across the US Naval
Distribution of information (out to ship) organizations, including - NAVSEA, NAVSUP,
Shore – Need to access reliability data, (support) and SPAWAR, NAVAIR.
historical, current supply info via apps:
SCM, R&D apps, Test and evaluation,
Engineering
32
SOA Examples
Local Government
The Customer The Business Problem
• Greater Los Angeles region,
• So. CAL Regional Crime
effectively fighting crime and
Fighting Data Sharing Initiative
terrorism
• Reduce crime and fear of crime
• Regional Data Sharing
• Prevent terrorist acts
• Real time crime Intel (criminals
• http://www.lasd.org/
don’t care about borders)
• Need to Integrate: LASD,
LAPD, Local Cities, State, FBI • Crime alerts immediately
data based on Global Justice available
XML Standard • Failed integration project using
Vitria against LARCIS – LA
County’s Incident Crime
Key Takeaways Database and sharing this data
with LA Police Department
Successful Proof of Concept
• Must use Open Standards
Integration strategy as the front
end of a standards-based Global
Justice XML solution
33
SOA Examples
Local Government
The Customer The Business Problem
• LA DHS provides Welfare • Disperate Systems required a
Programs, Clinics, Hospitals & Health Care Data Model
Public Health Care Programs in • Needed strong HL-7 Support
LA County and Easy to Use HealthCare
• http://www.ladhs.org/ Adapter
• Pressure to improve the quality
of care
Key Takeaways
• Important regulatory, security
& privacy requirements
BPEL strong support for
“message formatted data” • Regional eHealth Care Record
leapfroged Oracle past
competition
DHS will replace all of SeeBeyond
with BPEL – our time to
deployment is much faster.
34
The Path to Successful SOA
―Success is going from failure to
failure without a loss of
enthusiasm.‖
Winston Churchill
35
The Path to a Successful SOA Project
The Path to a Successful SOA Project
Select
Application
Build
Service
Portfolio
Service
Bus
Business
Process
User Scalability
Interface
Dashboard
Security
36
Step 0 | Select An Application
Step 0 | Select An Application
start CRITERIA
Eligible • Broken Process
Human Task For
• Lack of Visibility
Services
• Variance
Business Rules ? • Integration Points
Manager • Clear Metrics
Approval
Check DELIVERABLE
Automated Tasks Fraud
Detection • Process Sketch
Notify • Set of Human Tasks
Citizen • Set of Automated Tasks
Benefits
• Set of Business Events
Business Event Processed • Set of Business Rules
end
37
Step 1 | Build Portfolio of Services
Step 1 | Build Portfolio of Services
BEST PRACTICES
• Contract/Interface First
• Coarse Grain Documents
• Asynchronous Interactions
• Undo/Cancel Operations
• Versioning
• WS-I, Wrapped Document
Style
• WSIF Binding to Java, JCA
Database IMS, CICS SAP
Java
Oracle, PSFT
38
Step 2 | Establish SOA Integration Framework
Step 2 | Wire Through An Enterprise Service Bus
BEST PRACTICES
• UDDI Registry
• JCA Adapters
• Integration with Policy
Management Framework
• Service Virtualization
Logical Naming
• Differed, Reliable Delivery
Enterprise Service Bus (Configurable)
.NET, SAP, Mainframe, Oracle,
Java
Retek, PeopleSoft, Siebel, etc
39
Step 3 | Orchestrate into End-to-End
Processes
Step 3 | Orchestrate into End-to-End Processes
BEST PRACTICES
• BPEL
• XSLT Transformation
• Human Workflow Service
fx
• Rules Service
BPEL Workflow Rules
• Notification Service
• Error Hospital Service
Enterprise Service Bus • ESB Binding and Wiring
• Tracing and Debugging
• Iterative Development
• Unit Testing
.NET, SAP, Mainframe, Oracle,
Java
Retek, PeopleSoft, Siebel, etc
40
Step 4 | Expose through Rich User
Interfaces
Step 4 | Expose through Rich User Interfaces
BEST PRACTICES
Portal, JSF Applications, .NET, Microsoft Office
• JSF
• WSRP, JSR-168
• .NET
fx
BPEL Workflow Rules
Enterprise Service Bus
.NET, SAP, Mainframe, Oracle,
Java
Retek, PeopleSoft, Siebel, etc
41
Step 5 | Deliver Real-time Dashboards
Step 5 | Deliver Real-time Dashboards
BEST PRACTICES
Portal, JSF Applications, .NET, Microsoft Office
• KPI First
• Sensors to Collect Events
without Business Process
fx
Changes
BPEL Workflow Rules • Real-time Dashboard
• Alert/Actions
(Fusion Effect)
Enterprise Service Bus
.NET, SAP, Mainframe, Oracle,
Java
Retek, PeopleSoft, Siebel, etc
42
Step 6 | Secure Interactions
Step 6 | Secure Interactions BEST PRACTICES
Portal, JSF Applications, .NET, Microsoft Office
• WS-Policy, WS-Security
• Change Policy without
Changing Endpoint
fx • Integrated with ESB
BPEL Workflow Rules (Multi-binding Support)
• Agent and Gateway Mode
• Support for Java and .NET
Enterprise Service Bus
.NET, SAP, Mainframe, Oracle,
Java
Retek, PeopleSoft, Siebel, etc
43
Step 7 | Scale On Demand
Step 7 | Scale On Demand
Portal, JSF Applications, .NET, Microsoft Office BEST PRACTICES
• Asynchronous Interactions
• Support for Large XML
Documents
fx • Clustering-Friendly
BPEL Workflow Rules • JCA and Java Binding
• Batch API
Enterprise Service Bus
.NET, SAP, Mainframe, Oracle,
Java
Retek, PeopleSoft, Siebel, etc
44
In Summary
Business drives architecture
Need a vision to guide SOA evolution
Overall themes and recommendations
SOA creates opportunities for ―pluggable business‖
SOA applies to many scenarios
Services must be designed in a process-centric way
Learn from emerging patterns in the real world
Orchestration is a good first step into greater levels of SOA
flexibility
45
Questions and Comments
46
Thank You
Timothy Davis Mark Johnson
951.514.9951 608.251.8218
mark.johnson@cgi.com
timothy.davis@oracle.com