Upgrade split or Split Upgrade

1.

2. Upgrade & splitor Split & Upgrade

3. Agenda How We Got Here Urgency What is �the Split� Upgrade Scenarios Integration Options Summary Q/A

4. How We Got Here PeopleSoft HRMS 7 (1997) PeopleSoft released Student Administration (SA) SA was installed on top of the HCM application PeopleSoft HRMS 8.9 (2004) SA was more fully integrated with HCM via the Person Model Student Administration renamed Campus Solutions (CS) PeopleSoft HRMS 9.0 (2006) Last version in which CS and HCM are jointly installed Oracle will not release CS major upgrades moving forward CS enhancements will now come through Feature Pack releases

5. How We Got Here PeopleSoft HRMS 9.1 (2009) HCM is now a stand alone application All CS portal registry entries are removed Issues that Lead Up to the Split Product management issues Bundle release related issues Increase in upgrade complexity Greater flexibility, scalability & setup options

6. Urgency Extended Support for PeopleSoft 8.9 is expiring Oracle supported upgrade path from HRMS 8.9 to 9.0 expires Dec 2012 Oracle HCM 9.0 premier support expires 12/31/2011. � However, PeopleSoft clients have until 12/31/2012 before being assessed a fee for extended support. � Extended Support expires 12/31/2014.Oracle HCM 9.0 premier support expires 12/31/2011. � However, PeopleSoft clients have until 12/31/2012 before being assessed a fee for extended support. � Extended Support expires 12/31/2014.

7. What is �the Split� Stand up new application stack (PRD, DEV, TST, etc.) Copy HCM onto the new stack Designate new stack as either CS or HR Remove HR access from portal registry in CS Remove CS access from portal registry in HR (not necessary in HCM 9.1) Integrate the separate instances Perform data clean up, for example Remove paycheck data from CS Remove student financials data from HCM

8. Upgrade Scenarios Upgrade and Split Upgrade HRMS to 9.0 Go Live Split CS and HCM Upgrade HCM to 9.1 Configure Integration Go Live Spilt and Upgrade Split CS and HCM Upgrade CS to 9.0 and HCM to 9.1 Configure Integration Go Live

9. Upgrade and Split

10. Split and Upgrade

12. Integrating CS and HCM Oracle delivered integrations CS 9.0 Bundle 19/Feature Pack 4 HCM 9.0 Bundle 14 HCM 9.1 Bundle 3 A few included integrations Person data � Keep person bio/demo in sync Workforce Admin - Keep HR job data in sync in case CS business processes require knowledge of this information Person configuration data

13. Delivered Integration Example Let�s focus on Person bio/demo data Oracle delivers functionality to keep the following data in sync Personal Data Disability Data Citizenship/Visa Data POI Data

14. Records Included

15. Integration Steps Determine if integration is needed - Is it important to have a single EMPLID for a person across your institution? Determine Integration Points - Is there data in CS and HCM that should be kept in sync? Person data is usually a requirement Other integration points are determined by business processes and/or fit gap analysis Determine Integration Option to be Implemented Implement Integration If your business processes and data governance policies on campus are such that the various systems of record, HRMS, CS, etc., already operate independently with no need or desire to synchronize records or create a single EMPLID, then no integration between systems is necessary. If your business processes and data governance policies on campus are such that the various systems of record, HRMS, CS, etc., already operate independently with no need or desire to synchronize records or create a single EMPLID, then no integration between systems is necessary.

16. Integration Options Distinct Owner Owner/Subscriber Higher Education Constituent Hub (HECH) Delivered Bi-Directional

17. Distinct Ownership Utilize External Search Match Introduced in HRMS 9.0 Feature Pack 4 Ability to use Search Match functionality across applications CS and HCM data will not be kept in sync through delivered integration Main purpose is to ensure one EMPLID per person Simplest Solution

18. Distinct Owner Example

19. Distinct Owner Considerations HCM and CS own their own data - No need to set up and maintain governance policies HCM and CS will not encounter material business process changes Eliminate need for IT to support additional message-based integration Is a good option if keeping data synced between CS and HCM is not a requirement

20. Owner/Subscriber Either HCM or CS is defined as the point of entry for Person data and becomes the �Owner� The other system becomes the �Subscriber� All Person data will be added, updated, and deleted within the Owner system The Subscriber system will be kept in sync via published updates from the Owner Oracle recommends CS as the owner, but is up to each institution

21. Owner/Subscriber Example

22. Owner/Subscriber Considerations Reduces likelihood of creating duplicate records Provides a consistent Person record across CS and HCM Ensures the creation of a single EMPLID per person PeopleSoft ships with all the integration tools in order to sync, no additional software will be needed Business Processes for person data entry, including self service, will change for the subscribing system Navigation from subscriber system to owner system can be set up through the portal registry to avoid logging into two different systems

23. Higher Education Constituent Hub (HECH) HECH is a separate application and database CS and HCM will publish changes to HECH and subscribe to HECH for updates HECH becomes the golden source for Person data Provides bi-directional data syncing, allowing CS and HCM the ability to update Person data in either system If your institution has many entry points for person data (not just CS and HCM), HECH should be considered

24. HECH Example

25. HECH Considerations Provides bi-directional data syncing causing minimal impact on existing business processes Provides the most comprehensive solution for managing Person records Provides a concrete source for the golden Person data Enables a consistent Person record across all enterprise applications Includes other capabilities such as more comprehensive Search Match function and optional address cleansing Requires additional software license purchase Requires additional infrastructure Implementation is resource intensive

26. HECH Considerations

27. Delivered Bi-Directional Utilizes delivered PeopleSoft integration tools Integration Broker Service Operations, Messages, and Handlers Publishing and subscription services Provides bi-directional data syncing, allowing CS and HCM the ability to update Person data in either system Provides similar functionality as the HECH option�without HECH

28. Delivered Bi-Directional Example

29. Delivered Bi-Directional Considerations Provides bi-directional data syncing causing minimal impact on existing business processes Provides similar functionality to HECH option without the cost and complexity Delivered functionality is utilized and is supported by Oracle

30. Other Integration Considerations Assign a Data Steward for Person Data Responsible for data integrity Duplicate record resolution Configuration data adds and changes Batch Publish Process ID Delete/ID Change batch processes Translate Values Many values from the translate table are utilized to track Person Data Military Status Visa Status Configuration sync does not handle translate values Two methods can be employed to address Translate Values Update manually with careful coordination Create a custom batch process to keep the values in sync Compare Process

32. Additional Considerations Infrastructure � Split will require new hardware Software � HECH requires additional licensing Administration Spilt will require administration of an additional application stack Integration will require additional administration HECH will require administration of a new application stack

33. Summary HRMS 8.9 Support is Running Out We�ve Discussed Two Upgrade Options Upgrade & Split Split & Upgrade Upgrade Decision Matrix We�ve Discussed Four Integration Options Distinct Owner Owner/Subscriber HECH Delivered Bi-Directional Integration Decision Matrix

34. Q/A