Montana DPPHS Enterprise Architecture Montana Department of Public Health and Human Services Deloitte Consulting LLP
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Montana DPPHS Enterprise Architecture
Montana Department of Public Health and Human Services Deloitte Consulting LLP
2
Presenters
Ron Baldwin CIO, Montana Department of Public Health and Human Services
David Sisk Chief Technologist, State Health and Human Services, Deloitte Consulting
3
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)
4
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
5
Enterprise Progression
SNAP TANF
Medicaid
Increment 1 2009
Increment 2 2012
New World Order
Mainframe
Integra=on
CHIMES – EA Pla3orm Seamless and Interoperable to
End User
Single Sign On
Common Client Index
Shared Fiscal Services Layer
ESB
MA
SNAP
TANF
Future Growth
CHIMES
Medicaid
CHIMES
TANF
CHIMES
SNAP
CHIMES -‐ SFSL CHIMES -‐ EA
TEAMS
Decommissioned
October 1, 2012
CHIMES -‐ Medicaid
CHIMES
Medicaid
LEGACY
n-‐Tier Web-‐based RDBMS
n-‐Tier Web-‐based RDBMS ESB
6
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
7
Area Approach Outcomes Tools Area
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 its Business Rules Management Software (ILOG) to define, deploy and execute SNAP and TANF business rules
• Defined 3,000 unique SNAP and TANF business rules
ILOG Business Rules
Reports • Eliminate redundant or outdated reports
• Standard delivery method
• Common look and feel
Crystal Reports
Reports
Enterprise Architecture Component Overview
8
Area Approach Outcomes Tools Area
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
Enterprise Architecture Component Overview
9
Area Approach Outcomes Tools Area
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
Enterprise Architecture Component Overview
10
Area Approach Outcomes Tools Area
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
Enterprise Architecture Component Overview
11
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
Promotional Video
Bi-‐monthly newsleEer
Weekly Tips
12
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
13
Where Are We Now
2011 2012
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
DEC
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
CHIMES – EA Development Schedule
May 11 – Oct 12
Jan 11 – May 11
Oct 11 – Mar 12
Jul 11 – Jan 12
8/12-9/12
Apr 12 – Jul 12
May 11– Oct 11
10/1/12 GO
LIVE
REQUIREMENTS
DESIGN
CONVERSION
CONSTRUCTION
SYSTEM INTEGRATION TEST
USER ACCEPTANCE TEST
PILOT
14
Our Project
Please contact: Ron Baldwin, CIO State of Montana Department of Public Health and Human Services [email protected]
David Sisk, Chief Technologist, State Health and Human Services Deloitte Consulting [email protected]
Related Documents
