Commonwealth of Massachusetts Executive Office of Health and ...


Published on

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Commonwealth of Massachusetts Executive Office of Health and ...

  1. 1. Implementation and Lessons Learned Jason Snyder Chief Technology Officer Executive Office of Health and Human Services April 2, 2008 Services Oriented Architecture and Web Services
  2. 2. EOHHS and its SOA Vision Overview Facilities Planning SOA Guiding Principles Finance Management Information Technology Purchase of Services Human Resources Service Integration Implement an integration architecture based on common set of industry standards and tools: -Shared Security Services -Enterprise Service Bus -Enterprise Application Integration interagency enterprise “glue” Service Governance Develop and adopt Secretariat standards for common 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 Infrastructure Secretariat pilot for high available, fault tolerance architecture -Adopt existing standards from the State Information Technology organization -Assist in developing standards when none exists -Architectural Review and guidance -Improve Operational Efficiency Service Agility Connect and build on existing and planned core applications 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
  3. 3. Why is SOA right for EOHHS? Are there truly Shared Service opportunities across EOHHS? Application A Application B Application C Commonality Disparity
  4. 4. Business Process across EOHHS Agencies Individual business processes are supported by multiple applications, even within individual agencies
  5. 5. Large-scale Projects <ul><li>A 2003 Survey identified 15 monolithic applications across EOHHS that supported more than 10 discrete business processes each. </li></ul><ul><li>Monolithic development results in: </li></ul><ul><li>Less functionality delivered than required </li></ul><ul><li>Significant Schedule Overruns </li></ul><ul><li>Significant Cost overruns </li></ul><ul><li>Performance problems </li></ul><ul><li>Difficulty in assessment of project success </li></ul><ul><li>Much higher Operational Costs </li></ul><ul><li>Limited Agility in response to change </li></ul>
  6. 6. Evaluation Matrix
  7. 7. Evaluation Matrix 2
  8. 8. Sharing information Traditional funding sources and program configurations and individual agency mandates enforce the image of each project and application 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 the organization of the government agencies which provide the services and the government itself. External view: Internal view:
  9. 9. Establish a Foundation for SOA <ul><li>Acknowledge that it will be multiyear, multiphase engagement </li></ul><ul><li>Plan for achieving agency/individual agreement </li></ul><ul><li>Define objective –end state (or long term future state) </li></ul><ul><li>Prioritize SOA infrastructure development </li></ul><ul><li>Develop methodology and organizations to support </li></ul><ul><li>Identify key first services </li></ul><ul><li>Strong QA Center </li></ul><ul><li>Encourage a Culture of Collaboration </li></ul><ul><li>Provide an open, accessible and objective Governance metric to measure performance and use </li></ul>
  10. 10. Creating business interest <ul><li>Government is different – collaboration across the organization is required! </li></ul><ul><li>EOHHS is offering: </li></ul><ul><li>Architecture, Process and Technical Assistance from EOHHS </li></ul><ul><ul><li>Methodology, Quality and Governance, Lessons Learned, Innovation & Stabilization </li></ul></ul><ul><li>Business Services Design and Technical Services Development </li></ul><ul><li>Shared Infrastructure </li></ul><ul><li>ESB Service for integration </li></ul><ul><li>Role-based Single Sign on Security Solution </li></ul><ul><li>Document Management Solution </li></ul><ul><li>Common Portal for Access – The User Gateway </li></ul><ul><li>Workflow Services </li></ul><ul><li>Registry / Repository Services </li></ul><ul><li>SWIKI Collaboration Site </li></ul>
  11. 11. Initial SOA Vision for EOHHS
  12. 12. Shared Infrastructure - Hosting Platform for Services
  13. 13. Building Methodology and Process
  14. 14. ESB Services <ul><li>Message Store & Forward Queuing </li></ul><ul><li>Message Transformation & Replication </li></ul><ul><li>Message Routing </li></ul><ul><li>Message Security Authentication and Authorization </li></ul><ul><li>Enterprise XML Gateway Firewall for Externally Accessible Web Services </li></ul><ul><li>HHS XML Gateway for Web Service Centralization </li></ul><ul><li>WSDL-based Web Service Management </li></ul><ul><li>Common Reference Adaptor </li></ul><ul><li>Legacy Integration </li></ul><ul><li>File Transfer Services </li></ul><ul><li>Status and Monitoring Dashboard </li></ul><ul><li>Message Publish & Subscribe </li></ul>
  15. 15. Building the ESB <ul><li>Minimize Source and Destination coding by providing configurable services </li></ul><ul><li>Combines advantages of high reliability with loosely coupling integration </li></ul><ul><li>Centralized auditing, monitoring and logging </li></ul>Asynchronous Services Delivery guaranteed by Integration Bus Publishing system delivers payload and continues processing its business functions
  16. 16. Building a Single Sign-on Security Solution
  17. 17. The First Business Service – Common Intake
  18. 18. Evolutionary Updates Required to Address <ul><li>SOA Governance – Services are still not being developed – applications in a shared environment </li></ul><ul><li>Collaboration outside project teams limited </li></ul><ul><li>Improving Project stability </li></ul><ul><li>Operational model poorly defined </li></ul><ul><li>Projects lie low – service identification limited </li></ul><ul><li>Technical services still needed (Document management, Registry, etc.) </li></ul><ul><li>Impact of updates to shared services to existing applications </li></ul><ul><li>Asynchronous Communication does not meet business need </li></ul><ul><li>Inconsistent Deployment activity </li></ul>
  19. 19. Integrated SOA Architecture and Governance
  20. 20. Innovation and Stabilization
  21. 21. Building a Business and Technical Services Portfolio <ul><li>Business Services: </li></ul><ul><ul><li>Immunization Forecast Web Services </li></ul></ul><ul><ul><li>MA-21 Web Services </li></ul></ul><ul><ul><li>NewMMIS Web Services </li></ul></ul><ul><ul><li>Scheduling Service </li></ul></ul><ul><ul><li>Organization Management Service </li></ul></ul><ul><ul><li>HIPAA Translation Services </li></ul></ul><ul><ul><li>Case Management Services </li></ul></ul><ul><ul><li>On-line Invoicing (EIM/ESM) </li></ul></ul><ul><ul><li>Licensing Services </li></ul></ul><ul><ul><li>Lockbox Services </li></ul></ul><ul><ul><li>GIS Services </li></ul></ul><ul><ul><li>ePay Service </li></ul></ul><ul><ul><li>Technical Services: </li></ul></ul><ul><ul><ul><li>Shared Infrastructure </li></ul></ul></ul><ul><ul><ul><li>Enterprise Service Bus </li></ul></ul></ul><ul><ul><ul><ul><li>Asynchronous Queue-based Message Delivery </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Synchronous Web Services </li></ul></ul></ul></ul><ul><ul><ul><ul><li>ESB Services - Transformation, Replication, Routing, Security </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Legacy Integration Adaptors </li></ul></ul></ul></ul><ul><ul><ul><ul><li>File Transfer Service </li></ul></ul></ul></ul><ul><ul><ul><li>Access and Identity Management Services </li></ul></ul></ul><ul><ul><ul><li>Document Management Services </li></ul></ul></ul><ul><ul><ul><li>User Portal Services </li></ul></ul></ul><ul><ul><ul><li>Workflow Services </li></ul></ul></ul><ul><ul><ul><li>Registry & Repository Services </li></ul></ul></ul>
  22. 22. Introducing Web Services
  23. 23. Integration Services - Legacy Integration <ul><li>Goal: Mature the Web Services Capabilities at HHS </li></ul><ul><li>This project Delivers: </li></ul><ul><ul><li>WS Access of Content from Legacy Sources </li></ul></ul><ul><ul><li>Security Integration at the WS Client </li></ul></ul><ul><li>Objectives: </li></ul><ul><li>Develop Web Services Integration Capabilities </li></ul><ul><li>Provide Mechanisms that: </li></ul><ul><ul><li>Deliver WSDL-based Services Management </li></ul></ul><ul><ul><li>Promote XML Gateway Usage </li></ul></ul><ul><ul><li>Promote Legacy Integration </li></ul></ul>Web Services Integration With MA-21 Mainframe Legacy System
  24. 24. ESB - Enhancement for File Transfer Service <ul><li>Goal: Work to Provide Generalized File Transfer Services </li></ul><ul><li>This Work Delivers: </li></ul><ul><ul><li>Web Services-based File Transfer Services </li></ul></ul><ul><ul><li>Prototype for Publish & Subscribe Capabilities </li></ul></ul><ul><li>Objectives: </li></ul><ul><li>Develop Web Services File Transfer Capabilities </li></ul><ul><li>Provide Mechanisms that: </li></ul><ul><ul><li>Deliver Reliable File Transfer Services </li></ul></ul><ul><ul><li>Integrated with Shared Security </li></ul></ul><ul><ul><li>Integrated with Document Repository Mechanism </li></ul></ul>
  25. 25. Portal - Composite Application Integration <ul><li>Goal: POC to Mature the Portal Capabilities at HHS </li></ul><ul><li>This POC Delivers: </li></ul><ul><ul><li>Integration of Content from Multiple Sources on One Screen </li></ul></ul><ul><ul><li>Four Styles of Integration </li></ul></ul><ul><li>Develop Services and User Interface Integration Capabilities </li></ul><ul><li>Provide Mechanisms that: </li></ul><ul><ul><li>Deliver Consistent User Experience </li></ul></ul><ul><ul><li>Promote Use of Portals and Portlets </li></ul></ul><ul><ul><li>Promote Reuse of Services </li></ul></ul><ul><ul><li>Provide Legacy Systems Integration </li></ul></ul><ul><ul><li>Provide Composite Application Building </li></ul></ul>
  26. 26. Service Management - Registry / Repository <ul><li>Goal: Organize Web Service Creation and Access </li></ul><ul><li>This project Delivers: </li></ul><ul><ul><li>Common Repository of XML Artifacts </li></ul></ul><ul><ul><li>Registry that exposes available web services </li></ul></ul>
  27. 27. Next Steps - Extend the Portfolio <ul><li>Goal: Work to Identify Additional Technical and Business Services </li></ul><ul><li>This Work Delivers: </li></ul><ul><ul><li>Identification of Services with High Reuse Potential </li></ul></ul><ul><ul><li>Criteria to Identify Business vs. Technical Services </li></ul></ul><ul><ul><li>Enterprise Registry and Repository Solution </li></ul></ul><ul><li>Objectives: </li></ul><ul><li>Develop ‘Pipeline’ of New Business and Technical Services </li></ul><ul><li>Provide Mechanisms that: </li></ul><ul><ul><li>Deliver Services By Design </li></ul></ul><ul><ul><li>Provide Accessible Integration to Legacy and New Systems </li></ul></ul><ul><ul><li>Promote Reuse </li></ul></ul>8/04 Enterprise Service Bus Shared Security IE&R 12/04 Infrastructure Upgrade 8/05 eTag Enterprise Reporting IRIS PDM STARS 12/05 TPI HMIS Infrastructure Upgrade 8/06 Enterprise Budgeting Legislative Budget HCIS SIMS 10/06 EIM/ESM Initial Release Web Services infrastructure Release 2 Stabilization Release 2.5 Current State
  28. 28. Recommendations <ul><li>Centralized governance and QA empowerment needed </li></ul><ul><li>Plan for cost savings to be more gradual </li></ul><ul><li>Expect a variety of solution alternatives </li></ul><ul><li>Revisit the vision – share it </li></ul><ul><li>Measure the outcome </li></ul><ul><li>Strong communication across the organization is essential </li></ul><ul><li>Build and they will come is not a strong approach </li></ul><ul><li>Build services by business need </li></ul><ul><li>Change will be continuous – provide direction for it </li></ul><ul><li>Enterprise Governance and Balancing Business / Technology Leadership </li></ul><ul><li>Securing Predictable Funding </li></ul><ul><li>Managing across regime change </li></ul><ul><li>Identifying the right services and processes to “Harvest” </li></ul><ul><li>Involving the business appropriately </li></ul><ul><li>Building a centralized, sustainable development organization </li></ul><ul><li>Operational support model for managing services </li></ul><ul><li>Collaboration is a culture </li></ul><ul><li>Setting expectations with external development communities </li></ul>What we learned: What we are still learning: