commonwealth of massachusetts executive office of health and

Commonwealth of MassachusettsExecutive Office of Health and Human Services

Implementation and Lessons Learned

Jason SnyderChief Technology Officer

Executive Office of Health and Human Services

April 2, 2008

Services Oriented Architectureand Web Services

SOA Implementation Overview

2

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 Integration interagency 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 Information Technology 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 and expose them "beyond four walls" -Leverage and Extend existing assets-Break down organizational barrier and IT Silos-Establish Business process management and workflow

Finance Management


3

Why is SOA right for EOHHS?

Are there truly Shared Service opportunities across EOHHS?

Application A Application B Application C

Commonality Disparity


4

Business Process across EOHHS Agencies

CH

E-I

nfoS

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

SP

S

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

DT

A-B

EA

CO

N

DT

A-D

IMS

DT

A-F

MC

S

DT

A-I

IS

DT

A-S

SP

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


5

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


6

Evaluation Matrix

Service Enablement vs Agency BenefitNew Process Assessment

Muggles Business Drivers

Stars

Agency Benefit

Ser

vice

En

ab

lem

ent

Technology DriversDocMgt

Elig

Client

ITSpprt

Outcom

Intake

Prvider POS

Prcmnt SecMgt


7

Evaluation Matrix 2

Efficiency vs. Customer ExperienceNew Process Assessment

Muggles Customer Experience Drivers

Stars

Customer Experience

Eff

icie

ncy

Efficiency Drivers

DocMgt

Elig

Client

ITSpprt

Outcom

Intake

Prvider

POS

Prcmnt

SecMgt


8

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:


9

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


10

Creating business interest

Government is different – collaboration across the organization is required!

EOHHS is offering:

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

• Business Services Design and Technical Services Development• Shared Infrastructure• ESB Service for integration• Role-based Single Sign on Security Solution• Document Management Solution• Common Portal for Access – The User Gateway• Workflow Services• Registry / Repository Services• SWIKI Collaboration Site


11

Initial SOA Vision for EOHHS


12

Shared Infrastructure - Hosting Platform for Services


13

Building Methodology and Process


14

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


15

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


16

Building a Single Sign-on Security Solution


17

The First Business Service – Common Intake


18

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


19

Integrated SOA Architecture and Governance


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


23

Integration Services - Legacy Integration

Goal: Mature the Web Services Capabilities at HHS

This project Delivers:• WS Access of Content from Legacy Sources• Security Integration at the WS Client

Objectives:• Develop Web Services Integration Capabilities

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

Web Services Integration With MA-21 Mainframe Legacy System


24

ESB - Enhancement for File Transfer Service

Goal: Work to Provide Generalized File Transfer Services

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

Objectives:• Develop Web Services File Transfer Capabilities

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


25

Portal - Composite Application Integration

Goal: POC to Mature the Portal Capabilities at HHS

This POC Delivers:• Integration of Content from Multiple Sources on One Screen• Four Styles of Integration

• Develop Services and User Interface Integration Capabilities

• 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


26

Service Management - Registry / Repository

Goal: Organize Web Service Creation and Access

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


27

Next Steps - Extend the Portfolio

Goal: Work to Identify Additional Technical and Business Services

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

Objectives:• Develop ‘Pipeline’ of New Business and Technical

Services

• 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


28

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

13)Enterprise Governance and Balancing Business / Technology Leadership 14)Securing Predictable Funding15)Managing across regime change 16)Identifying the right services and processes to “Harvest”17)Involving the business appropriately18)Building a centralized, sustainable development organization19)Operational support model for managing services20)Collaboration is a culture21)Setting expectations with external development communities

What we learned:

What we are still learning:

commonwealth of massachusetts executive office of health and

Documents