Oracle Cloud & PeopleSoft Day 2017

1. Managing 9.2: Customer Stories
Mark Thomas – Hays
Heather Davies – Oxfam
Alex Lightstone – pp BAT

2. The PeopleSoft Estate
 PSHR on Windows Server 2012, SQL 2012
 PeopleTools 8.54.17; 9.2 and all updates to PUM013
plus a few critical patches,
 PSFSCM –being upgraded very soon:
 On windows server 2008, SQL 2012 upgrading to
windows server 2012
 PeopleTools8.53/ going to 8.55.13 (plus several
POC’s), 9.2 PUM005 going to PUM020 on selected
modules and some patches to PUM022, will apply
parts of PUM023 when available (features required).

3. Having got to 9.2….
 In summary our Selective Adoption strategy is to get
reasonably current, stay in support, adopt new
technology, according to resource availability and
business priorities. NB this is an evolving approach.
 When we apply updates we try to introduce what
adds business value/is a priority, together with must
do to stay in support/keep things working. We also
use an agile approach and that means not introducing
all new features at once (if it extends time) so we can
release value early.
 The reason we decided on this strategy was the
business priority coupled with limited resources/time.

4. Our Experience / Lessons learnt
 We are really only now implementing/reviewing our
selective adoption approach.
 Our experience of the process so far is limited as we
required a PeopleTools upgrade to take advantage of
new features.
 Major lessons learnt would be need to be aware of
how much work may be involved with the advance in
PeopleTools (e.g. Crystal reports gone, soon SES and
MAP approvals). Also need to bear in mind some PUM
updates require certain PeopleTools patch levels for
features.

5. If I had to give one piece of
advice to others starting out on
the 9.2 SA journey it would be…
Start the journey, don’t get too
het up on strategy as it can
evolve over time to meet
priorities.
Don’t underestimate users, our
experience of the fluid user
interface, was easy acceptance
by all users globally, with no
training required. Give them
new features where possible.

6. The PeopleSoft Estate - Hays
All residing on an Oracle 12.2.01 database
Hays Version - Today
Module Application Tools
FINANCE 9.2 Image 18 8.55.07
HCM - CORE 9.2 Image 17 8.55.07
HCM - GP 9.2 Image 17 8.55.07
CRM 9.2 Image 13 8.55.13
INTERACTION
HUB
9.1 Image 2 8.55.07
ELM 9.2 Image 15 8.55.13

7. Having got to 9.2….Hays
Maintenance Model
 In summary our Selective Adoption strategy has
evolved:
 Jan 2015 – 9.2 Upgrade (Application & Tools)
 Jan 2017 – 9.2 Image Update/Tools Upgrade
 From Jan 2017 – “Sustainable BAU Model” to Keep PS
Current
 May 2017 Keep Current 1: CRM & ELM Image & Tools
 Introduced new Sprint based development process
 Our Image Updates are typically “technical” due to the
Hays appetite on risk (keep paying 27,000 workers
each week, every week!)

8. Having got to 9.2….Hays
Maintenance Model

9. Hays Experience / Lessons learnt
 Our experience of the process so far has shown:
 PTF will be a huge benefit for managing business testing
implications of SA
 Perfect for agile/sprint methodologies
 Importance of partner and user network – huge thank you
to Cedar, Claire and Steve!
 Business collaboration key to realising benefits of new
features – focus on business problems
 PeopleTools – spot releases can easily be included
 Major lessons learnt would be to automate as many of
the deployment processes as possible

10. If I had to give one piece of
advice to others starting out on
the 9.2 SA journey it would be…
Plan your SA journey early,
otherwise an image catch up is
a significant project.
Identify business problems that
can be resolved with new
functionality and deliver
quickly. This will create real
interest from other
users/teams for similar
solutions.

11. The PeopleSoft Estate - BAT
 PeopleSoft HCM (HR and GP) on Red Hat Linux 5.5
x64, Oracle 11g (11.2.0.4.0) and Windows 2008 R2
 PeopleTools 8.54.30; HCM 9.2; Global Payroll Core and
UK updates to Image 15 plus 2017/18 payroll updates
 Planning to upgrade to PeopleTools 8.56 and get
current on all updates up to PUM 23 in September
 Primary function of PeopleSoft is as a payroll
application, minimal HR to support payroll functions
 Self-Service payslips with SSO via IBM Access Manager

12. Having got to 9.2….
 BAT Selective Adoption strategy is to stay current on
payroll updates and stay in support for PeopleTools
 Biannual "get current" loading all new features and
updates from latest PUM images
 Aim to upgrade PeopleTools version at the same time
 Payroll compliance is the driving factor behind all
updates. Payroll must be up to date with legislation
 Decision to apply both bug fixes and legislative
updates as bug fixes may also affect compliance

13. Our Experience / Lessons learnt
 Need to stay relatively up to date as otherwise a
critical fix may require large number of pre-requisites
 Any PRPs are only available on My Oracle Support
until the following PUM image is released
 Adopt Fluid – it is the basis for most new features
 Allow plenty of time for testing and to update
customisations requiring adapting to new features
 Use Event Mapping (PeopleTools 8.55) where possible
to avoid having to reapply customisations

14. If I had to give one piece of
advice to others starting out on
the 9.2 SA journey it would be…
Don't forget PeopleTools. You
must also plan your PeopleTools
upgrades to ensure you remain
supported, particularly for
critical Security Updates and
new hardware certifications.
New features may require the
latest PeopleTools version so
you also need to include that in
your SA planning.

15. Q & A