1. Embracing Selective Adoption in a 9.2 World
Larry Zagata
Vice President, Solution Delivery
MIPRO Consulting
July 18, 2018

2. Presenters Larry Zagata – Managing Partner, VP Delivery
25 years Information Technology Experience
19 years PeopleSoft Experience
9 years at PeopleSoft
(M)

3. About MIPRO Our Heritage Founded by former PeopleSoft execs in 2005
More than 500 engagements throughout North America
Dedicated exclusively to PeopleSoft engagements
Our Passion
Award winning culture attracting experienced talent
Reputation for being innovative, candid and customer focused
Integrity –taking pride in consistently doing the right thing
Our Focus
The success of our customers, achieving their objectives
PeopleSoft HCM, Financials, Supply Chain, ALM Implementations, Upgrades and Optimizations

4. Agenda Introductions Selective Adoption Overview
What should be in a Selective Adoption Strategy
Maintenance Strategies
Calendar
Communications
Adoption Criteria
Resources
PeopleTools strategy
PeopleSoft Test Framework
Information to assist you
Conclusion
Q&A

5. PEOPLESOFT SELECTIVE ADOPTION OVERVIEW

6. Selective Adoption Terminology
Selective Adoption: Selective adoption is the named process by which PeopleSoft customers are able to “selectively” determine how they will apply maintenance and new features as they are delivered approximately every 10 weeks by Oracle.
PUM: PeopleSoft Update Manager (PUM) is a new Lifecycle Management tool that enables PeopleSoft customers to stay current on application maintenance using selective adoption. PUM works with PeopleSoft Change Assistant to facilitate this new process. PUM leverages PeopleSoft Update Images (PIs).
Change Assistant: Oracle’s PeopleSoft Change Assistant is a standalone, Windows based, Java program that orchestrates the process of updating or upgrading your PeopleSoft system. Change Assistance automates many steps of the update process, provides a step-by step-process for applying maintenance and is integrated with PUM using change packages created from the PI.

7. Selective Adoption Terminology
PTF: PeopleSoft Test Framework is a tool that helps automate the testing process and really allows for the more frequent updating and application of PeopleSoft Update Images. PTF automates various tasks within the PeopleSoft application, primarily functional testing.
PeopleSoft Update Images (PI): PeopleSoft Update Images are Oracle VM VirtualBox virtual machines that are downloaded from My Oracle Support (MOS) to your system. PI’s are published and released on a specific schedule approximately every quarter. All PI’s will contain bug fixes and most, but not all PI’s, will contain new features/functionality. PI’s are cumulative, meaning PI 14 will contain all of the content from PI 1 through PI 13.

8. Selective Adoption Overview
How PeopleSoft Selective Adoption is different
Not the same bug deployment strategy of the past
Provides for a SAAS like model
Selective Adoption approach
Provides new functionality delivered more frequently
Creates a need for a different approach to staffing
Eliminates large scale upgrades (if executed properly)
Changes how organizations budget

9. What is PUM
Starting with PeopleSoft 9.2 applications, the PeopleSoft Virtual Image is delivered along with PUM.
Quick and easy to download a current PeopleSoft Update Image with the VirtualBox technology.
Full, cumulative PeopleSoft image that is a working PeopleSoft environment for the applications pillar with the most up to date fixes.
Ability to search for specific fixes by bug ID or by specific object reference.
Generating a custom change package based on the customer selection and the patches already applied to the customer environment.
Reviewing the detail of the changes before selecting the update into the package.
Providing a change package where each distinct object is called out only one time and applied only one time in the correct sequence.
No more prerequisite bundles or maintenance packs.

10. PUM – Things to Remember
You can selectively apply patches with reduced time, effort, and cost.   
Bundles and Maintenance Packs are no longer used.  Instead, a tailored custom package is automatically generated based on the parameters you select from the latest PeopleSoft source image.  
You have access to all updates from Oracle on a cumulative basis and can select and search for specific updates such as new features, legal and regulatory changes, or a patch related to a specific issue, process or object.   
Any prerequisites are automatically identified. 
The  process of generating a change package is enabled through a new wizard with easy to follow steps and options.   As changes are introduced to your test environment the PeopleSoft Test Framework provides a closed loop process to run regression tests scripts against your changes. 

11. WHAT SHOULD BE PART OF YOUR SELECTIVE ADOPTION STRATEGY?

12. MAINTENANCE STRATEGIES

13. Maintenance Strategies
Proactive
Selective
Reactive
Hybrid/Custom

14. Proactive Maintenance
With this strategy, you regularly download the PI when it is released and have the most current PI available locally so that you can use it immediately when needed for your business.
This approach has several benefits:
You run the application code that is the same version as that of the Oracle Software Support team, which makes identifying and solving new problems faster and more efficient.
New updates are easier to apply because fewer prerequisites need to be applied retroactively.
You can use the current PI to understand the effect of planned customizations and to mitigate the effect of future integration of those customizations by better understanding the latest PeopleSoft code.
This strategy uses more resources, and planning and scheduling are dependent on how often you choose to update and for what scope. PUM can make updating faster and easier.
Does require more testing and involvement to ensure everything functions properly

15. Selective Maintenance
The key difference between this strategy and the proactive strategy is that your selection typically will result in a smaller scope and less of an effect as compared to the proactive strategy, which may require more time, resources, and planning.
This strategy enables you to download the PI regularly and review the updates posted for your application, but then you can apply only the updates that are relevant to your organization.
Use the PUM PIA Application in the image to search the available updates by various search criteria.
PUM enables you to select the updates you want and to include requisite updates automatically. It then generates the change package definition you need in order to apply the changes you selected in one change package.
The benefit of this strategy is that it enables you to stay reasonably current without the high level of resource dedication or scheduling that is associated with the proactive strategy.
The challenge of this approach is that business users may think the schedule is not predictable.
This strategy gives you the ability to plan and schedule your maintenance activities better. 

16. Reactive Maintenance
With this strategy, you do not apply any regular maintenance until you encounter a problem. Waiting to apply your maintenance until you have an issue may inconvenience your users, potentially compromising efficiency and adversely affecting your business operations because the timing of the discovery of the problem is not under your control. 
You also do not get any new functionality if you apply images only when you encounter a problem
Less updates, require less involvement in users for testing
If you do not apply images, then eventually you will be so far behind it will be similar to an upgrade when you do have to catch up
You can still leverage the power of the PI and the PUM application by regularly downloading the current PI and keeping it available for quick inquiries about updates and fixes that were already released.

17. Maintenance Comparison Chart
It is recommended to execute a maintenance “catch up” a minimum once per year. New functionality can be adopted on a separate schedule.

18. Maintenance What if we do nothing?
In 3 or 4 years you’ll be far enough behind that it will be a similar situation as an upgrade from one version to the next
As time progresses, you will have a less stable PeopleSoft solution
As time progresses, you will find it harder and hard to adopt new functionality because of the pre-requisites and interdependencies of the bug fixes

19. Sample Client Strategy 1
Main drivers for this client
Change Management and Training. Cannot introduce change to the organization often.
Selective Adoption Strategy
Execute a maintenance “catch up” once per year in October
Apply all bug fixes during the catch up
“Selective” functionality will be applied
Upgrade PeopleTools once per year (based on release schedule) in coordination with catch up
Download latest Image every quarter
Established specific criteria to apply image content or not
Evaluate any bug fixes required
Regulatory updates as required

20. Sample Client Strategy 2
Client really absorbed Selective Adoption
Minor (bugs, regulatory)
2 times per year
1.5 to 2 month projects
Minor enhancements
Major (new enhancements)
5 month major project
1 time per year
Get current twice a year

21. Sample Client Strategy 3
No specific schedule
Mantra is to not be “too far behind” (3-4 images)
More IT focused
Limited Business Involvement (testing only)
Limited new functionality deployed
Everything is applied, bug fixes and new functionality, but new functionality not released
Limited use of PTF

22. Sample Client Strategy 4
Developed a “repeatable” and defined update process
Detailed project plan and project controls
Once a year update to remain relatively current
Apply all bug fixes
Apply value add new business functionality
Heavy use of PTF

23. Changing the Strategy
Need to forget the old maintenance and support strategy
Move all normal support and project requests into your new maintenance schedule
Implement fixes
Implement new features
De-customize
Execute image updates and testing
Business and IT requests
Emergency Support
Agreed upon and prioritized projects
AR new feature
Fix 122
Image 18 new content
PS Admin
Business Analysts
IT Developers
Training
Security 23

24. Thoughts on your Strategy?
What are your constraints?
Time of year
Staffing limitations
Budget
Resource availability
Current customization level
Etc.
What are your IT/Business drivers?
Business needs frequent updates
IT policy to remain current on fixes

25. OTHER STRATEGY CONTENT

26. Calendar Create a specific Selective Adoption Calendar
Publish the calendar for IT and Business
Update and maintain the calendar
Important for everyone to understand the schedule for selective adoption
Image Use
Schedule (SAMPLE)
Download Image for future use and reference
Every image. Every Quarter.
Create a demo environment from image
Evaluate technical bug fixes
Every other image. Every other Quarter.
Evaluate new functionality
Apply technical fixes
Every other image. Every quarter based upon the defined criteria established by customer.
Apply new functionality

27. Communications
Established a specific communication calendar around PUM
Calendar will be utilized to communicate to the broader internal business entities related to the review and analysis of PUM images. This calendar is a reminder to let these various audiences understand when the review and analysis of the PUM images is occurring.

28. Communications Plan Communications include Timing of the image release
Timing of the review and analysis
Reminder of the criteria utilized to determine if content from an image will be applied
Anticipated regression testing dates
Analysis results
Business process impact/changes and training required
Timeline for new changes to take affect

29. Update Criteria (Sample)
Established specific criteria utilized to determine whether a technical fix or new functionality will be applied via a PeopleSoft Image once evaluated:
Is the technical fix or new functionality required to address a critical business process that is not functioning?
Is the technical fix or new functionality required to address a critical business process that is currently utilizing a work around?
Is the technical fix or new functionality required to address a business issue identified and promised by a date that is approaching or past?
Will the technical fix or new functionality require regression testing that the technical resources can properly support?
Will the technical fix or new functionality require regression testing that the business can properly support?
Will the technical fix or new functionality create a significant change management or training need for the business users?
Other

30. RESOURCES

31. Selective Adoption - Resources
Defined resource roles and responsibilities associated with PUM
PS Admin(s)
Downloads latest image content
Prepares image for use as a demo environment
Evaluates the necessity of technical bug fixes
Prepares the PUM Images for updating
Prepares change packages
Execute change package
Migrates changes between environments
Maintain migrations log
Supports PeopleSoft Test Framework at the administration level
Coordinates regression testing with technical development team and functional team
Executes regression testing at the administration level

32. Selective Adoption - Resources
Business Analyst(s)
Should represent all modules
Responsibilities
Evaluate business value of image contents
Coordinates the application of functionality with the PS Admin
Prepares and executes use of any PeopleSoft Test Framework scripts
Coordinates and executes regression testing with the PS Admin, Technical developers and functional leads
Assists with testing of new functionality
Coordinates/updates any business process documentation
Coordinates with any training/change management needs with end users/functional team

33. Selective Adoption - Resources
Business stakeholders
Should represent all modules
Responsibilities
Promotes functionality required
Participates in selective adoption meetings
Participates in testing new functionality

34. TESTING

35. Selective Adoption - Testing
Testing represents large majority of the PUM effort
Automate testing to assist with the process
Try to test as much as possible in an automated fashion before the business gets involved to reduce the business time required

36. PeopleSoft Test Framework
PTF automates various tasks within the PeopleSoft application, primarily functional testing which will enable testers to execute more tests with greater accuracy during a shorter time
PTF works by replicating the actions of a single user executing functional tests against the PeopleSoft browser-based application
Users can record manual test procedures and save them within the framework. Later (perhaps after an application upgrade or patch), those tests can be executed against the application to verify whether the application still behaves as expected
Test assets (tests and test cases) are stored in a database as Application Designer objects which can be managed along with other PeopleTools-managed objects through PeopleSoft Lifecycle Management

37. PeopleSoft Test Framework
“PTF includes a number of features not available in other commercially available record and playback automation tools, including:”
Test assets are PeopleTools managed objects, which enables PTF to validate recorded objects against PeopleSoft object metadata definitions
Features that help users manipulate data within the PeopleSoft rowset-oriented data structure
Functionality that automates numerous PeopleSoft-specific functions, such as running processes through Process Scheduler
Functionality that interfaces with other PeopleSoft automation tools, such as Data Mover and PsQuery.

38. PTF - Terminology Functional Test Script Functional Test Scenarios
Outlines a transaction to be tested, such as "Voucher Creation".
Written by a functional analyst, includes the
Navigation
Steps to perform in the screen
Success and failure conditions
Functional Test Scenarios
Represents
Variations on test scripts, such as creating a voucher with withholding and one without withholding
Combination of test scripts, such as a Procure to Pay process

39. PeopleSoft Test Framework
PTF stores your test transactions and results in a easy to use tree structure

40. PeopleSoft Test Framework
PTF allows you to build your test and store each step and indicate which steps pass or fail

41. PeopleSoft Test Framework
When the test cases are run, PTF will execute the test steps using the delivered PeopleSoft front end.

42. PeopleSoft Test Framework
Test results are then stored in a tree based structure with red-icons for “errors” and green icons for “pass”

43. PeopleSoft Test Framework
PeopleSoft Test Framework scripts are available in offshore lab
Starting point is of course the test case. Test cases contain test scripts.
Break test case down further to one or two common scenarios and add test data to the scenario.

44. PEOPLETOOLS

45. PeopleTools
Important to have a PeopleTools strategy that is in consideration with the Selective Adoption Strategy
Remember the Oracle PeopleTools policy
Full support for 12 months after the next version is released
Limited support for additional 12 months
You may need to be on a supported version to apply maintenance!
Some features/function, need the latest version of tools
Create an upgrade strategy, apply when available if possible
Architecture considerations

46. SELECTIVE ADOPTION INFORMATION

47. Selective Adoption - Resources
Cumulative Feature Overview Tool – Demo
CFO tool generic, or environment specific
Release notes
Demo images
Planned features and enhancements pages
rLoop= &id= &_afrWindowMode=0&_a df.ctrl-state=15g84nidpx_4
PUM Update Manager Dashboard
MDSTART_FLUID.PTIA_MDSTARTPAGE.GBL?GMenu=PTIA_MDSTART _FLUID&GComp=PTIA_MDGROUPLET&GPage=PTIA_MDGROUPLE T&ActionFooter=N&pslnkid=PTIA_MD_PUM_DASHBOARD

48. Selective Adoption - Resources

49. STRATEGY CONCLUSION

50. Conclusion How will the staffing model change for your organization?
What maintenance strategy is appropriate for your organization?
What update calendar will your organization adopt?
What will the strategy be for functional updates vs. bug fixes?
Will you leverage PeopleSoft Test Framework?

51. SELECTIVE ADOPTION WORKSHOP

52. Selective Adoption Workshop
Provide education on the value of SA
Provide education on the technical aspects of PUM
Allow for interaction and Q&A with a PUM specialist
Help you determine:
Who in the organization should be in charge of SA?
Which one of the three recommended update strategies should you deploy?
What type of update calendar should we adopt?
What are the three types of patches delivered with PUM? How do all 3 affect my organization?
How do I deal with customizations? What tools are there to support customization analysis?

53. Please complete a session evaluation
Session ID:
Contact Info:
Tel: