PeopleSoft 9.2 HCM Re-ImplementationReducing Customizations and Moving to the Person Model
In July 2012, BTRG embarked on the multi-phase mission to upgrade SLAC’s PeopleSoft Financials, Human Capital Management (HCM), and Supply Chain Management Systems from 8.9 to 9.1. As the HCM phase drew near, Oracle announced the release of PeopleSoft 9.2. After an efficient but thorough evaluation process, both BTRG and SLAC agreed that advancing to 9.2 instead of 9.1 would provide more features and more alignment with overall project goals. The scope of work included Core HR and Absence Management.
Traditional Upgrade vs. Re-Implementation
Before jumping to 9.2, BTRG and SLAC’s teams had to consider whether a traditional upgrade or a re-implementation approach would be best. SLAC’s PeopleSoft 8.9 HCM application had a very high level of customizations. Looking to drop the weight of these complex customizations and start clean to leverage more of 9.2’s fresh out-of-the-box features, both teams determined that a re-implementation would be the most efficient. Because a re-implementation approach is less common, SLAC had to rely heavily on BTRG’s advanced PeopleSoft expertise. Through the re-implementation, BTRG eliminated the old customized objects (including records, fields, and a completely customized portal registry), as well as facilitated a cleanup through the re-conversion of data while moving it from 8.9 to 9.2.
SLAC National Accelerator Laboratory (SLAC) is one of 10 Department of Energy (DOE) Office of Science laboratories and is operated by Stanford University.
Department of Energy
$350 Million (2012)
PeopleSoft 9.2 HCM Re-Implementation
85 Percent Reduction in Customizations
Intuitive usability with efficient WorkCenters & Dashboards
Completed on-time and within-budget
PeopleSoft became the System of Record (SOR) for all persons
Improved interface and enhanced reporting
Strengthened self-service experience
Migrate your data from one version to another using Oracle’s delivered tools to identify any changes in record structures and provide necessary defaults to utilize in the process.
Move business configuration and data from current into new database
Implement the software vanilla and then import your data to the defined record structures
Start with a clean PeopleSoft 9.2 database
Leave all modified object and customizations behind
Move to the Person Model
The Person Model provides a complete picture of the various relationships and any movement between those relationships a person may have within SLAC (i.e. employee, contingent worker, or person of interest). Switching to a Person Model meant that PeopleSoft would now be the sole system of record (SOR) for all persons associated with SLAC.
Working with SLAC personnel, BTRG defined classifications for persons of interest and contingent workers. A conversion process was developed to bring the data from the custom records in the 8.9 environment and create the corresponding POI and CWR records in the 9.2 environment. During the re-implementation, SLAC desired to change the department structure. BTRG assisted SLAC personnel to define profiles which could be assigned to specific users.