1 About this Template Dear Colleague, –This template is provided to you by Panaya to help you communicate the facts about your upgrade within your company. –The template is not a comprehensive project plan but rather a concise briefing with the essential points –We wish you a successful upgrade! Best regards, The Panaya Team

Free Upgrade Simulations Offer Is there an upgrade project on your horizon? Then you are invited to see exactly what you are up against. See the this slide for details.this slide 2

Copyright and Terms of Usage 3 –You are free to copy, share, and modify to your needs. –You are not allowed to sell the template –This document is provided by Panaya Inc. It is completely independent of and not affiliated with Oracle®. –Oracle is a registered trademark of Oracle. Oracle and other Oracle products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Oracle. All other product and service names mentioned are the trademarks of their respective companies. DISCLAIMER OF WARRANTY Panaya Inc. makes no representation or warranties, either express or implied, by or with respect to anything in this document, and it shall not be liable for any implied warranties of merchantability or fitness for a particular purpose or for any indirect special or consequential damages.

4 Oracle® EBS R12 Upgrade at [Company] Project Brief [NAME] Project Manager

5 Agenda 1.Project Goals 2.Upgrade Synopsys 3.Go Live Date 4.Scope 5.Leadership Team 6.Stakeholders 7.Timeline 8.Cost 9.Risk Management 10.Assumptions 11.Next Steps 12.Resources 13.About Panaya

6 1. Project Goals Avoid “End of Support” (2013 for , 2010 for and ) Enable New Functionality –Key function 1 –Key function 2 –Key function 3

7 Additional Goals (choose all that apply) Meet Compliance Requirements Standardization Consolidation Reduce maintenance Align business processes Other…

8 2. Upgrade Synopsys Upgrade Type: [Technical/Functional] Duration: XX months Go Live Date: Friday, XX/XX/2011 Impact on External Systems : [interfaces with XX, integration with YY] Downtime: XX hours (typically at least 72 hours) Cost: $XM (typically $0.5M-$1.6M)

9 3. Go Live Date Reasoning: (choose all that apply) –Holiday/Off peak –Next available window is ______ –In synch with financial/logistical events –Approved by all stakeholders Fri X/XX/2011 Downtime XX H Freeze: XX weeksDual maintenance: XX months Upgrade

10 4. Scope Database Hardware Dependencies on other components (Legacy systems) Customization Mapping and Cleansing Functional Improvements

11 5. Upgrade Leadership Team ModuleIT Lead Business Owner FIN HR SCM CRM BI … Functional leadership RoleLead Project Manager DBA Development QA System Administrator Training General and Technical

12 6. Stakeholders RoleName Sponsor Business 1 Business 2 Business 3

13 7. Upgrade Timeline Date Pre-upgrade analysis Prepare project plan Resource plan Project team training plan Clean up unused objects Scope definition Retool process Run automated upgrade simulation Custom object inventory Required adjustments Prepare test plans Execute upgrade cycles Adjust modifications and developments Unit testing Ongoing upgrade simulations to track progress UAT Performance test Develop cutover plan Rehearsal upgrade Run final upgrade simulation (verification) More testing as needed Communicate cutover plans Upgrade PROD Verify Cutover Troubleshoot problems Post processing (if any) Preparation PlanningExecution Final Preparation Production Cutover

14 Timeline Dependencies Downtime - when and how much Team availability UAT availability HW lead time Other projects that might impact the upgrade

15 8. Cost Estimates RoleAmount Software Hardware Resources (Internal) Resources (External) Cost of Downtime Total

16 9. Risk Management RiskProbabilityImpactMitigation Critical failure after go live H/M/LFinancial loss of $$/day -Oracle Critical Account -Team Extended Support -Running automated upgrade simulation & verification -Documented test scenarios -3 rehearsals before go live Missing the go live date H/M/L -Next available date is 3 month later -Need extended support from Oracle -Delay other projects -Plan a buffer -Stakeholder commitment to schedule and resources -Key users commitment to UAT Failure of interface to other applications H/M/L-Data errors - Dedicated interface testing sessions Performance issuesH/M/L-User productivity loss -Run Performance / Load testing in earlier phases of the upgrade -Sizing done by ___ -Purchase new hardware OtherH/M/L

Assumptions Assumption 1 Assumption 2 Assumption 3

Next Steps Next Step 1 Next Step 2 Next Step 3

Resources Online –Oracle Whitepaper: Planning Your E-Business Suite Upgrade from Release 11i to 12.1Oracle Whitepaper: Planning Your E-Business Suite Upgrade from Release 11i to 12.1 –Oracle Whitepaper: Upgrading EBS 11i Forms + OA Framework Personalizations to EBS 12Oracle Whitepaper: Upgrading EBS 11i Forms + OA Framework Personalizations to EBS 12 –Oracle Blog: Oracle E-Business Suite TechnologyOracle Blog: Oracle E-Business Suite Technology –Panaya ArticlesPanaya Articles Panaya’s Automated Upgrade Simulation –For a FREE trial simulation of your upcoming upgrade, or to schedule a demo visit

20 About Panaya’s Upgrade Automation Software Panaya's software-as-a-service helps companies that use SAP or Oracle reduce 80% of their upgrade and testing risk and effort. Utilizing a cloud- based supercomputer, Panaya simulates the upcoming upgrade, automatically pinpointing which custom programs will break as a result of the upgrade and automatically fixing most of these problems. Panaya’s testing solutions dramatically expedite ERP testing and eliminate the need for manual test script maintenance. Seamlessly capturing business knowledge in the background, as users work with the ERP applications, Panaya automatically generates plain-English test scripts that are rapidly executed and continually self-adjust based on test results. To learn more or apply for a free upgrade evaluation, visit:

Clearly see your programs, required adjustments, and test plans 21

Detailed resource and budget requirements 22