Case Study: Upgrade Strategies for PeopleSoft Financials and Supply Chain 9.1


Published on

Case study presentation by Berlin Packaging with strategies for performing a PeopleSoft upgrade to Financials and Supply Chain 9.1 with services partner Smart ERP Solutions.

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Case Study: Upgrade Strategies for PeopleSoft Financials and Supply Chain 9.1

  1. 1. Case Study: Upgrade Strategies forPeopleSoft Financials and Supply Chain Steven Canter Doris
  2. 2. Reminder: Pleasecomplete thedistributed feedbackforms.In appreciation for yourcomments you’ll beentered to win an iPad!
  3. 3. Agenda• About Smart ERP Solutions• About Berlin Packaging• Acquisition Overview• Integration Strategy• Gaining Synergies• Lessons Learned• Q&A
  4. 4. AboutSmart ERP Solutions
  5. 5. Smart ERP Solutions Comprised of the best former developers, architects, support, functional consultants and executives from PeopleSoft/Oracle Unique best practices and expertise in PeopleSoft strategic planning, implementation, upgrade and add-on / customization services Provide cost-effective, robust and repeatable add-on “Smart Solutions” for PeopleSoft applications as an alternative to customizations High Quality of Service at Every Level and Role: Executive Leadership, Project Management, Functional and Technical Expertise
  6. 6. Upgrade Strategies for PeopleSoft Financials and Supply Chain
  7. 7. Introduction to Berlin Packaging ™
  8. 8. What We Sellplastic glass metal closures
  9. 9. Oracle Software in UsePeopleSoft Modules (8.8) Other Applications • Order Management • User Productivity Kit • Inventory • Purchasing • Enterprise Performance • Manufacturing Management (Hyperion • Product Configurator Planning) • Billing • Accounts Receivable • Accounts Payable • General Ledger
  10. 10. Recent Company History• 02/28/2010 – Acquired All-Pak, Inc.• 12/13/2010 – All-Pak live on Berlin’s PeopleSoft System• 12/15/2010 – Acquired Continental Packaging Solutions• 4/4/2011 – Continental live on Berlin’s PeopleSoft System• No bandwidth during this period to work on ERP upgrade
  11. 11. Why Upgrade• Get current on support• Leverage new features • Improved Fulfillment Engine • Notification/Alert Framework • Collections Workbench• Customization removal not a driver
  12. 12. Project Approach• Largely a “technical upgrade”• Optional new features implemented only if major business process not required• Track new features for implementation post go-live• Outsource as much of technical work as possible• 8.8 customization throughout most of project
  13. 13. Partner Selection• Offshore capabilities to mitigate cost of retrofit (estimated 6,000-10,000 hours)• Limit use of subcontractors for accountability reasons• Berlin to deal only with on-shore staff• Experience with Supply Chain modules• Ability to grow/shrink project team as needed• Prefer a fixed-bid proposal
  14. 14. Project Strategy• Jointly managed by Berlin and SmartERP• No formal fit/gap with end-user team• End users not involved until after first test move complete• Development by SmartERP – Berlin development team to liaison with Berlin functional users• Project documentation resides in Berlin SharePoint site• Development issues tracked in SmartERP Ace system
  15. 15. Berlin Project Team• Project Manager• Development Manager and Staff• Training Lead• Functional Leads/Teams (OM, IN, MFG, AP, AR, GL, PO)• Team members from around the US• Total project team size ~30 members
  16. 16. Team Organization• Team lead for each functional area• Primary and secondary developer assigned to each• Each team responsible for unit test script development• Cross-functional team to create system test plan• Each team responsible for review/update of UPK lessons for that area• Regular meetings throughout via web conference
  17. 17. Project Timeline
  18. 18. Key Project Timeline• Initial move August-October• First test move in November – then unit testing by tech team• Second test move in January – then system testing by entire team• Third test move in March – then system testing by entire team• Go live in May
  19. 19. Training Strategy• Oracle University delivers delta training in January• Full team plus other key users attend classroom training• Series of companywide web conferences starting 45-days before go-live• Sandbox environment available at start of web conferences• UPK lessons updated/added as needed
  20. 20. UPK Development• Team leads review existing UPK lessons• Existing lessons categorized as needed • User experience only – just new screen shots needed • Changed business process – redo lesson• New lessons created as needed• UPK developer sits with SME to create lessons• Combination of training lead and temporary help
  21. 21. Testing Strategy• Create ~500 unit test scripts• Scripts combined as needed for business process scenarios (order-to-cash, procure-to-pay, etc.)• Scripts/scenarios managed through SharePoint list• 2 rounds of system testing, two weeks each, in Chicago• Consideration given to Test Framework, but skipped• All system enhancements must be ready for Test II
  22. 22. Customization Strategy• Customization at normal pace until TM2 begins• Customization limited to crucial business needs afterward• Careful tracking of all changes after initial snapshot• After TM3, no retrofit. Dual development in 8.8 and 9.1.• Retrofit is primarily SmartERP responsibility• Post TM3 changes are 100% Berlin responsibility
  23. 23. Infrastructure• All new infrastructure utilized for 9.1• App/web/batch servers virtualized. DB server is physical.• 100% Windows environment with SQL Server 2008• System testing takes place on production environment• Performance Monitor utilized to evaluate performance• Companywide stress-test executed prior to go-live
  24. 24. MS Project Plan
  25. 25. SharePoint Site
  26. 26. Project Calendar
  27. 27. System Test Plan
  28. 28. Sample Test Script
  29. 29. Go Live Checklist
  30. 30. ACE Tracking System
  31. 31. UPK Lessons
  32. 32. Important Lessons• Understand the goals of the upgrade• Ensure that internal team and partner are aligned• If no code-freeze then change management is key• Be as inclusive as possible with training and testing• Have good tools for managing the project• There is no such thing as too much communication
  33. 33. August 27-29, 2012 Connecticut Convention Center Hartford, Connecticut USAPeopleSoft RECONNECT is a new PeopleSoft-focusedevent, replacing Quest Regional events. This new event willoffer in-depth education into PeopleSoft product modules in away that isn’t possible at COLLABORATE due to to find out more.
  34. 34. Any Questions? Reminder: Please complete the distributed feedback forms. In appreciation for your comments you’ll be entered to win an iPad!
  35. 35. Thank YouFor more information visit berlinpackaging.comFor more information visit smarterp.comCopyright © 2012Smart ERP Solutions, Inc.