Montana DPPHS Enterprise Architecture Montana Department of Public Health and Human Services Deloitte Consulting LLP
Presenters Ron Baldwin CIO, Montana Department of Public Health and Human Services David Sisk Chief Technologist, State Health and Human Services, Deloitte Consulting 2
Where We Started Business Inefficient workflow Lack of policy automation Redundant data entry in multiple systems Outdated policies and processes Federal program changes (PPACA, HIPAA) Technology Legacy systems (difficult to change and use) Siloed systems (lack of interoperability) Policy/rules imbedded in program code Multiple system sign-ons Emerging IT standards and guidelines (MITA) 3
Vision for the Future Support the Enterprise MT DPHHS Other State Agencies Federal Exchange MITA aligned Improve Service Delivery Cross-Program Sharing Self Service Rapid Service Cost Effective Replacement Strategy Incremental Approach Establish Enterprise Architecture Leverage Federal Support Position for Future Growth and New Programs 4
Enterprise Progression LEGACY TEAMS Increment 1 2009 Increment 2 2012 New World Order CHIMES - Medicaid CHIMES - SFSL CHIMES - EA October 1, 2012 Single Sign On Common Client Index SNAP TANF Medicaid Mainframe Decommissioned M C e H d I i M c E a S i d n- Tier Web- based RDBMS C H I M E S M e d i c a i d Shared Fiscal Services Layer C H I M E S C T H S A I N N M A F E P S n- Tier Web- based RDBMS ESB 5 Integra=on ESB M A S N A P T A N F F u t u r e G r o w t h CHIMES EA Pla3orm Seamless and Interoperable to End User
Our Project Design and implement systems New SNAP and TANF systems Shared Fiscal Services Layer (SFSL) Create seamless user interface with current Medicaid system Integrate Medicaid-only data and functions into system driver Integrate shared processes across system Enterprise Architecture Common Client Index (CCI) Single Sign-on User Documentation Tool and Correspondence Support Enterprise Service Bus 6
Enterprise Architecture Component Overview Approach Outcomes Tools Data Eliminate redundant data Collect data common across programs one time Use business rules to identify how data is used Identify required data dynamically based on program request 70% of data collected identified as common across programs and collected once Oracle Data Business Rules Leverage DPHHS investment in Defined 3,000 its Business Rules Management unique SNAP Software (ILOG) to define, and TANF deploy and execute SNAP business rules and TANF business rules ILOG Business Rules Reports Eliminate redundant or outdated reports Crystal Reports Reports Standard delivery method Common look and feel 7
Enterprise Architecture Component Overview Approach Outcomes Tools Correspondence Analyze correspondence to identify opportunities to consolidate and simplify notices Develop common look and feel for all correspondence Reduced eligibility notices from 148 to 1 ADOBE Correspondence User Documentation Develop common look and feel Provide links to other user resources policy, CBT, FAQ Developed 390 user guides providing step-by step instructions for all CHIMES-EA and SFSL functions Robohelp User Documentation 8
Enterprise Architecture Component Overview Approach Outcomes Tools Common Client Index Eliminate duplicate SSNs Merge duplicate customers across legacy systems Eliminated over 8,000 duplicate entries across programs Positioned for use across the enterprise TIBCO Common Client Index Single Sign-on Design for current and future applications Positioned for future growth Tivoli Access Manager Single Sign-on Enterprise Service Bus Develop repeatable process to facilitate data sharing Developed over 40 web services across multiple applications Positioned for future growth MuleESB Enterprise Service Bus 9
Enterprise Architecture Component Overview Approach Outcomes Tools ETL Develop a standardized process Positioned for future growth Pentaho ETL Tools / Management Process Support transparency Provide consistent access to status and progress Assign responsibility and accountability to specific project resources Developed repeatable processes and reliable tools in place for future projects Jama/JIRA Tools / Management Process 10
Communication is Key to Success Transparent Reporting Federal Partners State Agencies Customers Communication Plan Who, what, when, how Review and revise regularly Fun and inclusive Bi- monthly newsleeer Promotional Video Weekly Tips 11
What We Achieve Accelerated Schedule Developed CHIMES-EA in 19 months and remained on schedule Improved Worker Efficiency Common look and feel across systems Support for business process enhancement Seamless workflow Accessible online help Enhanced Service to Customers New channels to access services Accurate and timely eligibility decision supported by automated business rules Positioned for Future Growth Repeatable processes Reusable tools Lower cost 12
Where Are We Now CHIMES EA Development Schedule Jan 11 May 11 DESIGN OCT SEP AUG JUL JUN MAY APR MAR FEB JAN DEC NOV OCT SEP 2012 AUG JUL JUN MAY APR MAR FEB JAN 2011 REQUIREMENTS May 11 Oct 11 May 11 Oct 12 CONVERSION CONSTRUCTION Jul 11 Jan 12 SYSTEM INTEGRATION TEST Oct 11 Mar 12 USER ACCEPTANCE TEST Apr 12 Jul 12 PILOT 13 10/1/12 GO LIVE 8/12-9/12
Our Project Please contact: Ron Baldwin, CIO State of Montana Department of Public Health and Human Services rbaldwin@mt.gov David Sisk, Chief Technologist, State Health and Human Services Deloitte Consulting dasisk@deloitte.com 14