eohhs services oriented architecture implementation

Commonwealth of MassachusettsExecutive Office of Health and Human Services

Implementation and Lessons Learned

Jason SnyderChief Technology Officer

Executive Office of Health and Human Services

August 6, 2007

Services Oriented Architectureand Web Services

SOA Implementation Overview

3

Facilities Planning

EOHHS and its SOA Vision Overview

Information Technology

Purchase of Services

Human Resources

SOA Guiding Principles

Service IntegrationImplement an integration architecture based oncommon set of industry standards and tools:-Shared Security Services-Enterprise Service Bus-Enterprise Application Integrationinteragency enterprise “glue”

Service GovernanceDevelop and adopt Secretariat standards forcommon development tools and techniques

-Executive Sponsorship via Steering Committee-Development driven by Unified Process

Methodology-Architectural Review and guidance-Outline responsibilities and ownership of technical

shared assets

Service InfrastructureSecretariat pilot for high available, fault tolerancearchitecture

-Adopt existing standards from the State InformationTechnology organization

-Assist in developing standards when none exists-Architectural Review and guidance-Improve Operational Efficiency

Service AgilityConnect and build on existing and planned coreapplications in order to:

-"Service Enable" existing core application andexpose them "beyond four walls"

-Leverage and Extend existing assets-Break down organizational barrier and IT Silos-Establish Business process management andworkflow

Finance Management


4

Why is SOA right for EOHHS?

Are there truly Shared Service opportunities across EOHHS?

Application A Application B Application C

Commonality Disparity


5

Business Process across EOHHS Agencies

CH

E-In

foS

ys

DM

A-A

PS

DM

A-e

MB

R

DM

A-M

A21

DM

A-P

AC

ES

DM

A-R

EV

S

DM

A-S

SPS

DM

H-M

HIS

DM

R-C

RS

DM

R-e

ISP

DM

R-e

SD

R

DP

H-C

DS

DP

H-C

MS

P

DP

H-E

IIS

DP

H-H

IS

DP

H-H

S

DP

H-N

ED

SS

DP

H-P

VM

S

DP

H-S

AM

IS

DP

H-S

LIS

DP

H-T

BIS

DP

H-W

HN

DS

S-F

amily

Net

DTA

-BEA

CO

N

DTA

-DIM

S

DTA

-FM

CS

DTA

-IIS

DTA

-SSP

S

DY

S-M

AJJ

IC

EH

S-M

assC

AR

ES

HC

F-U

CP

MC

B-A

FS

1. Intake and eligibility determination

2. Resource / program referral

3. Service ordering and provision

4. Recipient case management

Individual business processes are supported by multiple applications, even within individual agencies


6

Large-scale Projects

A 2003 Survey identified 15 monolithic applications across EOHHS that supported more than 10 discrete business processes each.

Monolithic development results in:

•Less functionality delivered than required•Significant Schedule Overruns•Significant Cost overruns•Performance problems•Difficulty in assessment of project success•Much higher Operational Costs•Limited Agility in response to change


7

Sharing information

Traditional funding sources and program configurations and individual agency mandatesenforce the image of each project andapplication as a separate entity unto itself.However - Redundant Data exists across the Enterprise with limited sharing of information and no common framework for collection equals …confusion and enhanced complexity for our citizens

Citizens do not distinguish between theorganization of the government agencieswhich provide the services and the government itself.

External view: Internal view:


8

Establish a Foundation for SOA

1) Acknowledge that it will be multiyear, multiphase engagement2) Plan for achieving agency/individual agreement3) Define objective –end state (or long term future state)4) Prioritize SOA infrastructure development5) Develop methodology and organizations to support6) Identify key first services7) Strong QA Center8) Encourage a Culture of Collaboration9) Provide an open, accessible and objective Governance metric to measure performance and use


9

Creating business interest

Government is different – collaboration across the organization is required!

EOHHS is offering:

1. Architecture, Process and Technical Assistance from EOHHS• Methodology, Quality and Governance, Lessons Learned, Innovation & Stabilization

2. Business Services Design and Technical Services Development3. Shared Infrastructure4. ESB Service for integration5. Role-based Single Sign on Security Solution6. Document Management Solution7. Common Portal for Access – The User Gateway8. Workflow Services9. Registry / Repository Services10. SWIKI Collaboration Site


10

Initial SOA Vision for EOHHS


11

Shared Infrastructure - Hosting Platform for Services


12

Building Methodology and Process


13

ESB Services

•Message Store & Forward Queuing•Message Transformation & Replication•Message Routing•Message Security Authentication and Authorization•Enterprise XML Gateway Firewall for Externally Accessible Web Services•HHS XML Gateway for Web Service Centralization•WSDL-based Web Service Management•Common Reference Adaptor•Legacy Integration•File Transfer Services•Status and Monitoring Dashboard•Message Publish & Subscribe


14

Building the ESB

-Minimize Source and Destination coding by providing configurable services-Combines advantages of high reliability with loosely coupling integration-Centralized auditing, monitoring and logging

Asynchronous Services

Delivery guaranteed by Integration Bus

Publishing system delivers payload and continues processing its business functions

PI4

PI4 Changed ESB picture to enphatize Core architectural patternsPasquale Iocola, 7/22/2007


15

Building a Single Sign-on Security Solution


16

The First Business Service – Common Intake

Catalog of Services

• Basic Needs• Cash

Assistance• Food• Medical

Eligibility Screening

?

Common Application

Individuals and families call or visit a single HHS offices or a convenient contracted service provider to request services.

Visits to multiple agency offices are eliminated.

A trained intake worker at an agency, advocate or provider office assists applicants using:

• Health and Human Services’ Virtual Gateway online Internet portal @ www.mass.gov

• Community Catalyst’s RealBenefits tool

IE&R functions are planned to be offered directly to HHS clients and the general public in future

releases.

Necessary supporting documentation (legal, financial,

etc.) is mailed to an individual or central HHS processing unit(s) for

verification and secure storage.

Information from the common application is sent electronically to

appropriate HHS agency systems for

determination of eligibility, benefits and

service availability, reducing cycle-time

delays experienced with processing paper.

Virtual Gateway users can:1) Browse a catalog of HHS (and

potentially external) programs and services

2) Perform a pre-screening trial eligibility calculation

3) Proceed directly to entering detail for an online request of services, application for services, or performing a status check on a previous request for assistance or application

The first two actions can be conducted anonymously.

The applicant is notified by phone or in writing of requests for additional information, as well as final

benefit determination and availability.

1

2

3

4

5

6


17

Evolutionary Updates Required to Address

1) SOA Governance – Services are still not being developed – applications in a shared environment2) Collaboration outside project teams limited3) Improving Project stability4) Operational model poorly defined5) Projects lie low – service identification limited6) Technical services still needed (Document management, Registry, etc.)7) Impact of updates to shared services to existing applications8) Asynchronous Communication does not meet business need9) Inconsistent Deployment activity


18

Integrated SOA Architecture and Governance


19

Culture of Collaboration - MassForge

Goal: Work to Mature HHS Artifact Management and Release Management Processes

This Work Delivers:1. Replacement of SWIKI2. Artifact Repository3. Release and Project Management Tools

Objectives:1. Deploy Enabling Tools for Collaboration and

Release Management

2. Provide Mechanisms that:• Deliver Artifact Management Tools• Deliver Project Management Tools• Deliver Release Management Tools

Release Management:The Big Picture! Put ‘em all together!•SubVersion - to continuously integrate code

•Ant, Maven - to standardize builds and deployment processes

•AntHill/Continuum - to automatically build and deploy applications, and integrate automated regression testing


20

Innovation and Stabilization


21

Building a Business and Technical Services Portfolio

Business Services:• Immunization Forecast Web Services• MA-21 Web Services• NewMMIS Web Services• Scheduling Service• Organization Management Service• HIPAA Translation Services• Case Management Services• On-line Invoicing (EIM/ESM)• Licensing Services• Lockbox Services• GIS Services• ePay Service

Technical Services:• Shared Infrastructure• Enterprise Service Bus

– Asynchronous Queue-based Message Delivery– Synchronous Web Services – ESB Services - Transformation, Replication, Routing,

Security– Legacy Integration Adaptors– File Transfer Service

• Access and Identity Management Services• Document Management Services• User Portal Services• Workflow Services• Registry & Repository Services


22

Introducing Web Services

PI1

PI1 Changed picture, content is the same. Included compliance with Enterprise Policies, WS-I CompliancePasquale Iocola, 7/22/2007


23

Integration Services - Legacy Integration

Goal: Mature the Web Services Capabilities at HHS

This project Delivers:1. WS Access of Content from Legacy Sources2. Security Integration at the WS Client

Objectives:1. Develop Web Services Integration Capabilities

2. Provide Mechanisms that:• Deliver WSDL-based Services Management• Promote XML Gateway Usage• Promote Legacy Integration

Web Services Integration With MA-21 Mainframe Legacy SystemPI5

PI5 Changed picture, more streamlined and simplified.

Changed Text:No more POC, but production servicePasquale Iocola, 7/22/2007


24

ESB - Enhancement for File Transfer Service

Goal: Work to Provide Generalized File Transfer Services

This Work Delivers:1. Web Services-based File Transfer Services2. Prototype for Publish & Subscribe Capabilities

Objectives:1. Develop Web Services File Transfer Capabilities

2. Provide Mechanisms that:• Deliver Reliable File Transfer Services• Integrated with Shared Security• Integrated with Document Repository Mechanism


25

Document Management Services

Image Management Services

Document Management Services

Auditing and Logging

Message Handlers

Library Services

Session Managem

entC

ontent TransferS

ecurity Services

Web Services

Framew

ork

RM

RPS

Email

ILM

DAM

WP

Portal

Custom Data Types

Persistence Integration Extensions

Custom JWS/JavaBean

Web Services

Content from many sources

Workflow, Document

Management and Archival

Persistence and Integration


26

Portal - Composite Application Integration

Goal: POC to Mature the Portal Capabilities at HHS

This POC Delivers:1. Integration of Content from Multiple Sources on One Screen2. Four Styles of Integration

1. Develop Services and User Interface Integration Capabilities

2. Provide Mechanisms that:• Deliver Consistent User Experience• Promote Use of Portals and Portlets• Promote Reuse of Services• Provide Legacy Systems Integration• Provide Composite Application Building


27

Service Management - Registry / Repository

Goal: Organize Web Service Creation and Access

This project Delivers:Common Repository of XML ArtifactsRegistry that exposes available web services

PI6

PI6 Added picture to include UDDI FunctionalityMetadata repository, and connection to end point and web services infrastructure (XMLGW)Pasquale Iocola, 7/22/2007


28

Next Steps - Extend the Portfolio

Goal: Work to Identify Additional Technical and Business Services

This Work Delivers:1. Identification of Services with High Reuse Potential2. Criteria to Identify Business vs. Technical Services3. Enterprise Registry and Repository Solution

Objectives:1. Develop ‘Pipeline’ of New Business and Technical

Services

2. Provide Mechanisms that:• Deliver Services By Design• Provide Accessible Integration to Legacy and New Systems• Promote Reuse

8/04Enterprise Service Bus

Shared SecurityIE&R

12/04Infrastructure Upgrade

8/05eTag

Enterprise ReportingIRISPDM

STARS

12/05TPI

HMISInfrastructure Upgrade

8/06Enterprise Budgeting

Legislative BudgetHCISSIMS

10/06EIM/ESM

Initial Release Web Servicesinfrastructure

Release 2Stabilization Release 2.5 Current State

PI7

PI7 Inserted project timeline and comparison with initial projects portfolio to show expansionPasquale Iocola, 7/22/2007


29

Recommendations

1) Centralized governance and QA empowerment needed2) Plan for cost savings to be more gradual3) Expect a variety of solution alternatives4) Revisit the vision – share it5) Measure the outcome6) Strong communication across the organization is essential7) Build and they will come is not a strong approach8) Build services by business need9) Change will be continuous – provide direction for it

1) Enterprise Governance and Balancing Business / Technology Leadership 2) Securing Predictable Funding3) Managing across regime change 4) Identifying the right services and processes to “Harvest”5) Involving the business appropriately6) Building a centralized, sustainable development organization7) Operational support model for managing services8) Collaboration is a culture9) Setting expectations with external development communities

What we learned:

What we are still learning:

eohhs services oriented architecture implementation

Documents