EOHHS Services Oriented Architecture Implementation

EOHHS Services Oriented Architecture Implementation screenshot

Text-only Preview

Commonwealth of MassachusettsExecutive Office of Health and Human ServicesServices Oriented Architectureand Web ServicesImplementation and Lessons LearnedJason SnyderChief Technology OfficerExecutive Office of Health and Human ServicesAugust 6, 2007SOA Implementation OverviewEOHHS and its SOA Vision OverviewSOA Guiding PrinciplesService IntegrationImplement an integration architecture based oncommon set of industry standards and tools:-Shared Security Services-Enterprise Service Bus-Enterprise Application Integrationinteragency enterprise “glue”Finance ManagementService GovernanceDevelop and adopt Secretariat standards forInformation Technologycommon development tools and techniques-Executive Sponsorship via Steering Committee-Development driven by Unified ProcessMethodology-Architectural Review and guidance-Outline responsibilities and ownership of technicalPurchase of Servicesshared assetsService InfrastructureHuman ResourcesSecretariat pilot for high available, fault tolerancearchitecture-Adopt existing standards from the State InformationTechnology organization-Assist in developing standards when none existsFacilities Planning-Architectural Review and guidance-Improve Operational EfficiencyService 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 andworkflow3SOA Implementation OverviewWhy is SOA right for EOHHS?CommonalityDisparityApplication AApplication BApplication CAre there truly Shared Service opportunities across EOHHS?4SOA Implementation OverviewBusiness Process across EOHHS AgenciesIndividual business processes are supported by multiple applications, even within individual agenciestSNEsSSNeRyR1SPSISOICilyJASB2CEVISPDRSDSMMSISNCSJCSPISsMAASPSHISSIISSVALmBHaEACMMSPSAsFa-InfoS-A-e-M-P-RE-M-CRS-e-eCDSCMEHIHSNEPSSTW-F-DI-F-IIS-MM-UCP-AEAAAAAA-SHRRRH-H-H-H-H-H-H-H-H-H-H-SA-BAAAA-SSBHMTTTS-CDMDMDMDMDMDDMDMDMDMDPDPDPDPDPDPDPDPDPDPDPDSDDTDTDDDYEHHCFMC1. Intake and eligibility determination2. Resource / program referral3. Service ordering and provision4. Recipient case management5SOA Implementation OverviewLarge-scale ProjectsA 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 change6SOA Implementation OverviewSharing informationExternal view:Internal view:Citizens do not distinguish between theTraditional funding sources and program organization of the government agenciesconfigurations and individual agency mandateswhich provide the services and the enforce the image of each project andgovernment itself.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 citizens7SOA Implementation OverviewEstablish a Foundation for SOA1) 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 use8SOA Implementation OverviewCreating business interestGovernment 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 & Stabilization2. 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 9SOA Implementation OverviewInitial SOA Vision for EOHHS10Document Outline
  • ÿ
  • ÿ
  • ÿ
  • ÿ
  • ÿ
  • ÿ
  • ÿ
  • ÿ
  • ÿ
  • ÿ
  • ÿ
  • ÿ
  • ÿ
  • ÿ