Upgrading to Pega 7 Presentation Title Presentation Title ... · Presentation Title Presentation Title Second Line ... Simulated environment / testing of production with soap calls.
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.
Jeff R. Read III MBA, CHCIO, Chief Information Officer, Cahaba
Tom GardamSenior Dir. of Engineering, Customer Success, Pega
Dhevendra EarvaArchitect, Customer Success, Pega
Dan DiSantisSenior Director, Virtusa Polaris
Session Outline
2
• Case Study: Cahaba
• Pega Experience and Best Practices
• Audience Q&A
Our Speakers
3
Jeff R. Read, IIICIO
Cahaba
Tom GardamSenior Director of
Engineering, Customer Success
Pega
Dhevendra EarvaArchitect,
Customer Success
Pega
Dan DiSantisSenior Director, BPM Consulting,
HealthcareVirtusa
CAHABA’S JOURNEY TO PEGA 7
5
Agenda1. Who we are2. Why we upgraded to Pega 73. The Upgrade Journey4. The Road Ahead
Agenda
About Cahaba
6
EFFICIENT ADMINISTRATION
UNWAVERING DEDICATION
EMBRACING INNOVATION
• Medicare contractor (MAC) since the program inception in 1966
• Currently Jurisdiction J A/B MAC serving Alabama, Georgia and Tennessee
• One of only eight contractors processing Medicare claims in the nation
• 600+ professionals dedicated to providing innovative and cost effective services to CMS
• ISO 9001-2008 certified
We Use Pega for…
7
• Claims Processing
• Provider Customer Service
• Appeals
• Medical Review
• Provider Enrollment
Background
8
• Pega environment 5.4 with many rules written in 4.x
• New CIO brought in as change agent
• Backlog of enhancements– Major workflow changes had been put off for years
• Many applications needed to be rewritten from the ground up
• High Pega staff turnover / low retention– Lack of comprehensive documentation
Background
9
Governed by CMS Mandates
• Applications and data have highest civilian classification
• Must stay within two major versions of the current release
• Requires extensive (contractor) background checks– 30-day window to provision team
• Access restrictions mandated development system be setup in Virtusa’sAlbany, NY site for testing – Simulated environment / testing of production with soap calls
Drivers for Migrating to v7.1
10
How It Started
11
Some defects weren’t bugs
THEY WERE FEATURES (NO LONGER SUPPORTED)WHICH WOULD BE DELIVERED BY MOVING TO V7.1
Q42014
• Internal Assessment
• Partner Selection
• Partner Assessment
• Partner Engagement
MISSION CRITICAL
NEEDED REWRITING
CUSTOM JAVA
SOME V4.X CODE
POORLY DOCUMENTED CODE
13 Applications
67 Portals
30,000 Rules
PRPC v5.4
Guardrail Violations
What We Found
How We Did It
12
Engaged partner that could scale resources up or down quickly to control cost & meet deadlines Created over 2,000 test cases
Created an on-shore / off-shore testing / development
model to ensure security
Testing was completed in3 months
using complete data set
1 2 3
Upgrade completed in Dev environment in5 months
using limited data
How We Did It…Testing Environment and Teams
13
57+ off-shore developers
Virtusa’s Albanydevelopmentenvironment
15+ Onshore testers
CITcomponent integration
testing
SIT QA UATCahaba Team of Testing
11 Pega in-house developers
Initial Results of Upgrade
14
• 86% first pass rate of code post development
– 1,300 defects (14%) we had to address
– 429 critical (33%) with functional impact
– 100 defects due to rules deprecation (with 50+ related to reporting)
• Another 176 defects found after the partner delivered the code into Cahaba’s SIT environment with all of our data to test
Summary – Operational Challenges Faced
15
High-security environment
made onboarding people difficult
“Like” for “like” to avoid huge training costs
Upgrading related software because
of different compatibility modes - IE v9 and had to
go to v11
Testing integration points with
external systems
Managing the list of enhancements
deployed
And More..
16
Moving data 5TB + DB2 Data User testing Code compliance Time to upgrade: 2 weekends over 60 hours & lots of moving parts, dB updates, testing and fixes
1 2 3 4
Results and Benefits
17
• We can focus on rewriting applications in 7.1
• We can work on re-factoring rules to optimize performance
• Better look and feel for the business, more modern looking
• Developers like it better, too
• Cahaba is positioned for future growth
PEGA EXPERIENCE & BEST PRACTICES
Pega Experience and Best Practices
19
• Additional drivers for upgrading to Pega 7• Impacted Areas along with User interface• Rebuild vs. Upgrade• Different Levels of Upgrade• Pega Recommended Upgrade Approach• Strategic and Productivity Solutions upgrade• Parallel Development along with Route to Live• The ECS Engagement model
What’s Driving the Need to Upgrade?Compelling Industry Events Industry Trends & Pega7 Benefits
• Security, security, security• IE8 & IE9 retired in Jan 2016• PRPC 5.x & 6.x are not supportable on IE11
PEGAWORLD 2015 AUDIENCE SURVEY
• Co-browse, Mobility, Chat, NBA• Standardized modern UI• Fast efficient user & developer experience• Pega 7.2 = Cloud native platform
• Bulk Upgrade of UI Rules• Freeform to Dynamic layout
conversion
• Inline Styles Report
• Embedded List view to Repeating Grid conversion
Note: These are community Tools developed by Pega ECS but not officially supported
Stay Current – Pega 7 Updates
• 2–3 months interval• Packaged into new Distribution Kit (Update Kit)• Contains fixes and new features• Zero downtime updates with High Availability• Consider Updating Pega Applications