1. PeopleSoft 9.2 Upgrade at Centene Better Health Outcomes at Lower Costs Chris Dando – Manager, Financial Systems Operations Sajeed Nadaf – Lead, Application Software Engineer Eric Rakers – Architect, Lead PSAdmin Oracle OpenWorld 2015 Confidential and Proprietary Information

2. Agenda 2 Centene Overview Our PeopleSoft Journey 9.2 Upgrade Process Lessons Learned Training 9.2 Functionality Adopted Roadmap with Selective Adoption Key Takeaways Questions

3. Centene Overview 3 15,800 employees # 186 on the Fortune 500 list WHO WE ARE St. Louis based company founded in Milwaukee in 1984 $ 3.7 billion in cash and investments $ 20.8-21.2 billion expected revenue for 2015 WHAT WE DO 23 states with government sponsored healthcare programs 4.6 million members 237,000 Physicians 2,000 Hospitals in our provider networks & Medicaid (20 states) Exchanges (11 States) MA D-SNP (8 States) Correctional (4 States)

4. Our PeopleSoft Journey 4 200920122013201420152016 400 Users AM GL Record-2-Report BI AR CM AP PO Spend & Supplier Mgmt ePro PC IT Platform Initial Go Live On Premise App & Tools Upgrade 9.0  9.1 8.49  8.52 OS, Database PT Upgrade 8.52  8.53 Latest App Bundles App & Tools Upgrade 9.1  9.2.10 8.53  8.54 OS, Database Tools Upgrade Latest PUM Image 8.54  8.55 Oracle DB on Exadata, Linux Strategic Decision Windows Server 2012 R2 SQL Server 2012 WebLogic 12c

5. 9.2 Upgrade Process 5 FY15 Technology Release 5 Pre-Upgrade Application 9.1 Bundle 27 PeopleTools 8.53 Platform Tuxedo 11.1.1.2.0 Verity 6.5.1 WebLogic 10.3.6.0 SQL Server 2012 Windows Server 2008 R2 Post-Upgrade Application 9.2 PI10 PeopleTools 8.54 Platform Tuxedo 12.1.1.0 SES 11.2.2.2.0 WebLogic 12.1.3.0.1 SQL Server 2012 Windows Server 2012 R2

6. 9.2 Upgrade Process 6 8 Steps to Success 1.Education 2.Upgrade Planning & Buy-in 3.Demo Build 4.Initial Pass 5.Test Move 1, 2, n 6.Dress Rehearsal 7.Go Live 8.Project Closure

7. 9.2 Upgrade Process 7 Step 1: Education Purpose To ensure that all players involved with your PeopleSoft product are aware of available features and functionality in the new release, understand the upgrade process and what resources are available. Product Owner/Project Manager & PS Admins Review the higher level feature documentation and summarize it based on how it fits into your current environment Product Owner role for each module that regularly checks for new features/functionality Compare to your Product Backlog Internal user groups Support Team (Functional & Technical) Should be a year-round activity (each new image release) Educate across skill sets (Functional/Developer/Administrators) Everyone should understand the upgrade path & process Lots of resources available

8. 9.2 Upgrade Process 8 Step 1: Education Available Resources PeopleSoftInfo.com Video Feature Overviews (Doc ID 1362821.1) PeopleSoft 9.2 Upgrade Home Page (Doc ID 1629720.1) PeopleTools 8.54 Upgrade Home Page (Doc ID 1915618.1) Getting Started on your PeopleSoft Upgrade (Doc ID 739129.1) Certified Upgrade Path Platform Certification Matrix (Doc ID 747587.1) PeopleSoft Upgrade Resources Report (Doc ID 1117047.1) Release Value Proposition (Doc ID 1474260.1) Cumulative Feature Overview Tool (now online) (Doc ID 793151.1) FSCM 9.2 Application Release Notes (Doc ID 1495347.1) PT 8.54 Resolved Incidents (Doc ID 1677055.1) PeopleSoft Update Manager (PUM) Home Page (Doc ID 1641843.2) PeopleSoft YouTube Channel Sources utilized year-round

9. 9.2 Upgrade Process 9 Step 2: Upgrade Planning & Buy-in Project Management Highlights Project Charter, Scope and Work Breakdown Structure Upgrade enables you to implement new features/functionality Summarize applicable highlights for stakeholders Prioritize the scope Project Schedule 4-5 month project timeline 2 months where entire team is engaged Project Team & Kickoff Project team & key stakeholders; all on the same page Internally staffed Communication Plan Weekly status reports Daily standup meetings SharePoint used for document repository and issue tracking Achieve Stakeholder Buy-in Create Project Timeline Engage the Core Team Communicate Regularly

10. 9.2 Upgrade Process 10 Project WBS Technical Enhancements Business Functionality Enhancements

11. 9.2 Upgrade Process 11 Project Timeline

12. 9.2 Upgrade Process 12 Step 3: Demo Build Purpose The Demo environments allow to you perform comparisons between environments. Starting point for the initial pass to an upgraded environment. 3 Demo environments Current Demo - same version/bundle as PROD; no customizations or bolt-on’s New Release Demo - 9.2 environment; no customizations or bolt-on’s PUM Demo – latest PUM image; not necessarily the image upgrading to Building out your Demo environments takes time; plan accordingly Roughly 4-6 weeks Current Demo vs New Release Demo Compare 1 – what is new from Oracle Current Demo vs Current PROD Compare 2 – these are your customizations and bolt-on’s Chapters 1 & 2 from our certified path upgrade template New Release Demo Copy of Current Demo New Release Demo (PUM)

13. 9.2 Upgrade Process 13 Step 4: Initial Pass Purpose The outcome of the Initial Pass is to have an upgraded environment with your Production data/configuration and the Oracle code line. Typically does not contain customizations or bolt-ons. S C T New Release Demo (PUM) PS 9.1 Database PS 9.2 Database S = Source T = Target C = Copy of Current Demo = Initial Pass Database Initial Pass New Release Demo 9.2 Current Demo Copy 9.1 Production 9.1 Decide what to bring into your Initial Pass environment PS Project UPGCUST includes all changes Anything Oracle has updated that we haven’t touched we choose to keep When in doubt take delivered code Some configuration in upgraded environment is typically required (Chapter 6) We choose to keep our bolt-on’s through the initial pass by updating the UPGCUST project compare tables. This means we don’t have to reapply bolt-on’s to the upgraded environment Only want to reapply true customizations Chapters 2, 4 & 5 from our certified path upgrade template Upgraded Copy of Production Copy of Production 9.1

14. 9.2 Upgrade Process 14 Step 5: Test Move 1, 2, n Purpose Full team is now engaged as analysts start testing functionality, developers apply customizations and PSAdmins are streamlining their process. Parallel Efforts Functional Analysts perform configuration (Chapter 6) and start testing; before all customizations are complete Developers are reapplying customizations; migrate to TEST when ready (Chapter 6) PSAdmins are starting next test move; automating scripts and nailing down timing Perfect the process Perform several test moves; throw away environments Work with PSAdmins to get as much in the source as possible Perform pre-conversion cleanup Reduce post-conversion work Assign PS Security owner PS 9.1 Database PS 9.2 Database S = Source T = Target = Initial Pass Database Production 9.1 Test 1 Initial Pass Environment New DEV Re-apply Customizations Maintain Security Migrate S T 1 1 2 2 3 3 Copy of Production 9.1 4 4 Configure

15. 9.2 Upgrade Process 15 Step 6: Dress Rehearsal Purpose To mimic your Go Live process as closely as possible in order to validate timings, ensure you have a complete template/checklist and identify any other possible issues before Go Live. Minimize the differences between your Test Moves and Go Live New hardware? perform the dress rehearsal on the new hardware Consider data center physical locations FY14 upgrade Go Live timeline impacted because our PROD servers where in a different physical location than DEV Created network latency we had not anticipated There will be some differences that you can only do when you go live Our cutover plan had a column for “applicable for Go Live” Do it at the same time/day you plan to do actual go live (Weekend/Overnight) This will help you know what teams will be ready if you need to call on them Communicate as if it were Go Live; except to your users Operate from your functional and technical cutover plans Give yourself a couple weeks between rehearsal and Go Live to make adjustments

16. 9.2 Upgrade Process 16 Step 7: Go Live Purpose To upgrade your PeopleSoft application to the latest and greatest PeopleSoft version. You’re Ready At this point you are an expert at this; multiple tests and dress rehearsals Prepare a functional check out list for functional team and end users (pre & post) Verifying data in Production throughout the day of go live Our Timing: Started on Friday, 6pmCST. Fully checked out and done by Saturday, 2pmCST Communications Canned communications ready to go for each milestone; This provides a status (ahead or behind schedule) Of all the work in the upgrade, this is what a lot of people see and evaluate your project on Post Go Live Be prepared for issues to arise the following week There will be issues you didn’t catch during testing and lots of user questions Keep a copy of your 9.1 environment for at least one quarter after Go Live 9.2 source as well (did something not get reapplied?)

17. 9.2 Upgrade Process 17 Step 8: Project Closure Purpose Meet with stakeholders and project team members to celebrate the successes and review what we could have done better. Celebrate with the team This is a major accomplishment Team is probably ready to blow off some steam Officially close out the project with stakeholders Review what was accomplished Discuss what went well and what could have gone better Discuss plans for next year’s release

18. 9.2 Upgrade Process 18 Project WBS Technical Enhancements Business Functionality Enhancements

19. Lessons Learned 19 Lessons We Learned During this Upgrade Secure Enterprise Search (SES) installation took more time than expected Crystal & BI Publisher PT8.54 supports Crystal but still required a customization in 9.2 for AP check and Billing Invoice printing Try to convert to BIP before upgrade (PT 8.55) Don’t try to build (PeopleSoft Test Framework) PTF scripts during the project IE11 or Chrome 60 defects logged: SQL DB Issues Reviewing Cash Settlement issue ARUPDATE – Parallel processing Browser usability issues – labels wrapping and/or overlapping Bank Reconciliation values – signs changed

20. Training 20 Training Tips Utilized a combination of instructor led courses and a Learning Management System to deliver training User Experience Training Viewing Invoice Images – Related Content Report Manager Navigational changes, modular screens Pivot Grids WorkCenters E-Procurement Training Creating a Requisition Express Item Entry

21. 9.2 Functionality Adopted 21 WorkCenter & Dashboard Learnings Understanding WorkCenter inner workings Migration of WorkCenters from Demo to other environments Using Data migration Workbench to migrate WorkCenter projects Issues we faced with Migration of WorkCenters between environments Using DMS scripts to migrate Filter & Filter values Migration of Pivot grids for Dashboards Some useful links for WorkCenter and their migrations Customized WorkCenter code to include multiple business units in filters. PeopleSoft FSCM 9.2 WorkCenter Red Paper Migrating WorkCenter Pagelet Configurations between Databases

22. 9.2 Functionality Adopted 22 WorkCenter & Dashboard Learnings

23. 9.2 Functionality Adopted 23 AP Invoice Image – Related Content

24. 9.2 Functionality Adopted 24 Supplier OnBoarding Centene’s Accounts Payable and Procurement departments are undergoing a strategic initiative to improve their processes by implementing PeopleSoft Supplier Onboarding. This solution will provide a supplier entry platform that will allow for better visibility into suppliers, better control over approvals, and an overall more efficient process. Benefits: Better visibility into who is doing business with suppliers More controls around supplier master data Less manual data entry for Accounts Payable We have to do following: We used Data migration workbench to migrate delivered Supplier Onboarding template for registering suppliers and then modified it. Built custom ADS objects for Supplier onboarding Customized to bring the supplier classification onto the Supplier record when going through Supplier Onboarding(this functionality was not delivered)

25. Roadmap with Selective Adoption 25 How do we plan to use Selective Adoption / PUM? Still formulating overall strategy We plan to stay current annually Keeps skills fresh among internal team members The further away you get from base code line, the more changes you’ll be testing/applying Level loads budgets from year to year vs. a spike/staffing every 3 PTF is a big part of our test plan in FY16 We believe the upgrade process will be simplified We have pulled 5 fixes out of newer images and implemented them to PROD New approach to new features/functions If available in a new image we are likely to pull it down and implement it throughout the year Still very important to keep PeopleTools current each year

26. Key Takeaways 26 Start educating yourself now on what is available in the latest releases Abundance of resources available Everyone should have an understanding of the different environments involved in the test moves Prioritize scope with the expectation of descoping new features as you get closer to go live. You’ll still be further ahead than if you didn’t scope it at all. Demo build takes time Get as much in the source as possible; comes for free (Tools objects) Run as many test moves as possible Automate as many conversion scripts as possible Dress Rehearsal should mimic Go Live as much as possible Communicate milestones during Go Live Prepare for heavy support post Go Live Celebrate

27. Questions? 27 ?