ServiceOriented Government Mark Johnson Director Consulting, CGIAMS Timothy Davis Senior Solution Ar

1
Service-Oriented GovernmentMark
JohnsonDirector Consulting, CGI-AMS Timothy
DavisSenior Solution Architect Manager, Oracle
September 12, 2006
2
Agenda

• Government Under Pressure
• SOA Concepts Maturity Model
• Trends and Developments
• SOA in Government
• The Path to Successful SOA

3
Government Under Pressure
Nothing stimulates the imagination like a budget
cut. Sign on the desk of former
PA Budget Director
4
Governments 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

• Constraints
• Reduced budgets
• Government personnel shortage
• Aging infrastructure

• New Technology Enablers
• Open standards
• Inexpensive computing
• Pervasive computing

5
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

6
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
7
Summary
An organizational problem looking for a business
solution not an integration problem looking for
a technology solution
8
SOA Concepts Maturity Model
"Things should be made as simple as possible, but
no simpler." Albert
Einstein
9
SOA Historical Progression
Tightly Coupled Loosely Coupled
Application Focus Business Process Focused
Silos and Stovepipes Enterprise View
Inflexible to changes in business process or
market conditions
Very agile and flexible
10
A service

• Is a unit of work done by a service provider to
  achieve results for the service consumer
• Is a software component that is capable of
  providing access to functions and data
• Is exposed to other components via a service
  description
• Appears as a black box to the service consumer
• Is interacted via message exchanges
• Encompasses a business perspective
• Decouples its interface from its implementation
• Is built to last

11
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

12
SOA - Bringing Business and IT Together
A solution and architectural design approach
whereby business activity components are
packaged as well-defined services, accessible
electronically by partners, suppliers and others
which is implemented within an architectural
technology framework optimized for this purpose

Business Focus
Technology Focus
13
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

14
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

15
Traditional ModelA 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
Department C
Dept. Processes
Monolithic applications
Department B
Department A
Data redundancy
Dept. Application/Data
Technology inefficiencies
Technological stagnation
Dept. Technology
16
SOA Example HHS Reference Architecture
17
SOA Example HHS Reference Architecture
18
Centralized vs. Federated

• A successful SOA requires both centralized and
  federated components
• Singular vision goals, governance, enterprise
  repository management, and many operational
  functions should be centralized
• 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)

19
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

20
Trends and Developments
A good leader is someone whose troops will
follow him, if only out of curiosity. Gen. Colin
Powell
21
Gartner Hype Cycle
22
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

23
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).

24
IDC and Aberdeen

• IDC report
• SOA spending will reach 8.6 billion in 2006a
  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

25
SOA in Government
Gentlemen, we have no money, therefore we must
think. Lord Rutherford
26
SOA Examples City Government

• Local Government - Citizen services
• DCStat (http//www.adtmag.com/print.aspx?id18271)
  
• 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

27
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

28
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

29
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

30
SOA Examples Federal Government
The Customer
The Business Problem

• Market study for SOA platform
• Point of entry screening system that required
  integration to multiple systems including MQ
  Series

• US-Visit is an evolving program administered by
  the Department of Homeland Security
• Captures biometric information of most non-US
  citizens going through specific Ports of Entry
  (PoE)
• http//www.dhs.gov/dhspublic/interapp/content_mult
  i_image/content_multi_image_0006.xml

Key Takeaways

• Completeness of SOA solution and ease of use
• Govt preference of ease of integration to
  Oracle DB
• Extremely Scalability Issues Resolved with
  Benchmark

31
SOA Examples Federal Government
The Customer
The Business Problem

• Project Traffic Flow Management Modernization
  Project (TFM-M)
• Need to process 17,000 transactions/minute
• CSC already prototyping a 100 proprietary
  Integration solution involving
• ProActivity
• BEA WL Platform
• CA-Entrust
• Oracle DB
• Business Objects

• The FAA is responsible for regulating civil
  aviation in the United States to promote safety
• http//www.faa.gov/
• Decision maker CSC Program Manager, FAA TFM-M
  Program Manager

Key Takeaways
Complete SOA Oracle stack lowers
time-to-completion Application Server EE,
Discoverer, Portal, BPEL PM, BAM
32
SOA Examples Federal Government

• NAVSEA
• September 16, 2004
• (Derived from Conversation with Dave Scheid,
  NAVSEA Port Hueneme and W White.)
• Organization deploying Naval Surface Warfare
  Center (NSWC) under NAVSEA
•  
• Goal to have a seamless data flow from people
  who create infomation to the people who consume
  iti.e. the sailor on the deck plate who requires
  tech procedure and knowledge to his job. Tech
  procedure are created on the shore. Flow must be
  seamless between
• Creation of information
• Publication of information
• Distribution of information (out to ship)
• Shore Need to access reliability data,
  historical, current supply info via apps SCM,
  RD apps, Test and evaluation, Engineering

• Current Implementation Timeframe
• -    Live with 2,500 users and involves about
  20-25 apps. Using Plumtree Portal and Active
  Directory.
• -    Plan is to then rollout to other warfare
  centers in FY06 and 07 (one years time), to
  around 15,000-20,000 users.
•  
• Use of Oracle COREid
• NAVSEA is most interested in the access control
  portion and to set up policies for individuals to
  access thee different applications.
• -    They want SSO as well as the logging
  capability for security concerns.
• In the future, they will likely adopt a federated
  model to share access across the US Naval
  organizations, including - NAVSEA, NAVSUP,
  (support) and SPAWAR, NAVAIR.

33
SOA Examples Local Government
The Customer
The Business Problem

• So. CAL Regional Crime Fighting Data Sharing
  Initiative
• Reduce crime and fear of crime
• Prevent terrorist acts
• http//www.lasd.org/
• Need to Integrate LASD, LAPD, Local Cities,
  State, FBI data based on Global Justice XML
  Standard

• Greater Los Angeles region, effectively fighting
  crime and terrorism
• Regional Data Sharing
• Real time crime Intel (criminals dont care about
  borders)
• Crime alerts immediately available
• Failed integration project using Vitria against
  LARCIS LA Countys Incident Crime Database and
  sharing this data with LA Police Department
• Must use Open Standards

Key Takeaways
Successful Proof of Concept Integration strategy
as the front end of a standards-based Global
Justice XML solution
34
SOA Examples Local Government
The Customer
The Business Problem

• LA DHS provides Welfare Programs, Clinics,
  Hospitals Public Health Care Programs in LA
  County
• http//www.ladhs.org/

• Disperate Systems required a Health Care Data
  Model
• Needed strong HL-7 Support and Easy to Use
  HealthCare Adapter
• Pressure to improve the quality of care
• Important regulatory, security privacy
  requirements
• Regional eHealth Care Record

Key Takeaways
BPEL strong support for message formatted data
leapfroged Oracle past competition DHS will
replace all of SeeBeyond with BPEL our time to
deployment is much faster.
35
The Path to Successful SOA
Success is going from failure to failure without
a loss of enthusiasm. Winston
Churchill
36
The Path to a Successful SOA Project
The Path to a Successful SOA Project
Select Application
Build Service Portfolio
Service Bus
Business Process
Scalability
User Interface
Dashboard
Security
37
Step 0 Select An Application
Step 0 Select An Application
CRITERIA
start

• Broken Process
• Lack of Visibility
• Variance
• Integration Points
• Clear Metrics

Eligible For Services
Human Task
?
Business Rules
Manager Approval
DELIVERABLE
Check Fraud Detection
Automated Tasks

• Process Sketch
• Set of Human Tasks
• Set of Automated Tasks
• Set of Business Events
• Set of Business Rules

Notify Citizen
Benefits Processed
Business Event
end
38
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
SAPOracle, PSFT
Java
39
Step 2 Wire Through An Enterprise Service Bus
Step 2 Establish SOA Integration Framework
BEST PRACTICES

• UDDI Registry
• JCA Adapters
• Integration with Policy Management Framework
• Service VirtualizationLogical Naming
• Differed, Reliable Delivery(Configurable)

Enterprise Service Bus
.NET, SAP, Mainframe, Oracle, Retek, PeopleSoft,
Siebel, etc
Java
40
Step 3 Orchestrate into End-to-End Processes
Step 3 Orchestrate into End-to-End Processes
BEST PRACTICES

• BPEL
• XSLT Transformation
• Human Workflow Service
• Rules Service
• Notification Service
• Error Hospital Service
• ESB Binding and Wiring
• Tracing and Debugging
• Iterative Development
• Unit Testing

fx
BPEL
Workflow
Rules
Enterprise Service Bus
.NET, SAP, Mainframe, Oracle, Retek, PeopleSoft,
Siebel, etc
Java
41
Step 4 Expose through Rich User Interfaces
Step 4 Expose through Rich User Interfaces
Portal, JSF Applications, .NET, Microsoft Office
BEST PRACTICES

• JSF
• WSRP, JSR-168
• .NET

fx
BPEL
Workflow
Rules
Enterprise Service Bus
.NET, SAP, Mainframe, Oracle, Retek, PeopleSoft,
Siebel, etc
Java
42
Step 5 Deliver Real-time Dashboards
Step 5 Deliver Real-time Dashboards
Portal, JSF Applications, .NET, Microsoft Office
BEST PRACTICES

• KPI First
• Sensors to Collect Events without Business
  Process Changes
• Real-time Dashboard
• Alert/Actions(Fusion Effect)

fx
BPEL
Workflow
Rules
Enterprise Service Bus
.NET, SAP, Mainframe, Oracle, Retek, PeopleSoft,
Siebel, etc
Java
43
Step 6 Secure Interactions
Step 6 Secure Interactions
Portal, JSF Applications, .NET, Microsoft Office
BEST PRACTICES

• WS-Policy, WS-Security
• Change Policy without Changing Endpoint
• Integrated with ESB(Multi-binding Support)
• Agent and Gateway Mode
• Support for Java and .NET

fx
BPEL
Workflow
Rules
Enterprise Service Bus
.NET, SAP, Mainframe, Oracle, Retek, PeopleSoft,
Siebel, etc
Java
44
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
• Clustering-Friendly
• JCA and Java Binding
• Batch API

fx
BPEL
Workflow
Rules
Enterprise Service Bus
.NET, SAP, Mainframe, Oracle, Retek, PeopleSoft,
Siebel, etc
Java
45
Overall themes and recommendations
In Summary

• Business drives architecture
• Need a vision to guide SOA evolution
• 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

46
Questions and Comments
47
Thank You

• Timothy Davis
• 951.514.9951
• timothy.davis_at_oracle.com

Mark Johnson608.251.8218mark.johnson_at_cgi.com