Rady Children’s Hospital-San Diego

PeopleSoft Innovator

Rady Children’s Hospital-San Diego replaced a SaaS talent acquisition solution with PeopleSoft Recruiting

Summary

Rady Children’s Hospital-San Diego, in conjunction with their partner Huron Consulting, replaced a third party SaaS talent acquisition solution with PeopleSoft Recruiting, including Fluid Candidate Gateway, deployed using a two-stack approach.

Customer comments

Rady Children's Hospital-San Diego replaced a SaaS Talent Acquisition solution with PeopleSoft Talent Acquisition Management (TAM) and Candidate Gateway (CG). They rolled out TAM and CG in an innovative 2 stack approach where they stood up a completely new Application, web and database servers, that meant applicants log on to an external facing application that did not hold any existing employee information. This was done to further secure their employee information and to segregate External applicants completely so that they cannot access the main database.

They rolled out TAM for 2 entities; Rady Children's Hospital and Rady Children’s Physicians Management Services (2 External careers sites and 2 internal career sites).

The 2 Stack approach meant jobs needed to be created in both DBs. Rather than require Managers and Recruiters to enter these manually, multiple interfaces were created to keep Recruitment data (Job Openings and Postings, Applicant and Applications) in sync between the 2 stacks; external facing DB and internal DB

Interfaces were scheduled to run multiple times a day, thus eliminating dual data entry for the recruitment team. For the end user, it appears as if it is a single system.

Transaction data - interface
  • Managers would create jobs only on one internal PS instance via MSS. Job listed to be posted externally were automatically sent to external DB via Job interface (that was run 4 time a day)
  • Recruitment Team would progress applicants through the recruitment process in the main internal DB as applicant information was interfaced from external DB to main DB multiple times a day.
  • Internal Applicants used ESS to apply for vacancies that are posted on internal sites. Whereas, external applicants applied for the same vacancy via external facing DB.
Setup data - interface
  • Integration Broker messages were used to keep the company structure in sync between the 2 stacks.
  • Non-departmental tree security was used to eliminate the overhead of maintaining departmental tree security in 2 DBs
Other setup
  • Installation last ID were strategically numbered to avoid overlap between the 2 DBs
  • URL definitions were updated on the Email notification to identify the recipient and accordingly provide the appropriate link either to internal or external sites