1. Upgrading the Oracle Applications: Going Beyond the Technical Upgrade Atlanta OAUG March 19, 1999 Robert Cooney

2. Outline of the Presentation ä Preliminary Questions ä Critical Upgrade Issues ä Upgrading the Applications ä Methodology ä Options ä Upgrade Details ä Tasks ä Documentation ä Conclusion ä Questions and Answers

3. Preliminary Questions ä ä Upgrade Plan ä ä Objective ä ä Year 2000 Compliance ä ä Optimize Business Processes ä ä Migrate to Multi-Org for Global Deployment ä ä Upgrade to Current Vendor Supported Technology ä ä Migrate to Internet Enabling Applications (NCA) ä ä Reduce Reliance on Customizations ä ä Others ä ä Direction CharacterSmart Client (GUI)NCA ä ä 10.7 Standard ä ä 10.7 Multi-org ä ä Release 11 Standard ä ä Release 11 M.Oä

4. Preliminary Questions ä ä New Features/Modules to be implemented ä ä EDI ä ä Web Self Service Applications ä ä APS ä ä PDM ä ä Business Information Solutions ä ä Bar Coding ä ä Others ä ä Status on Upgrade Plan ä ä Discussions/RFP/Started/Completed ä ä Time FrameTentative Start Date ä ä Tentative End Date ä ä Implementation (In-house/Consulting/Both) ä ä Decision Deadline ä ä Budget ($ Value)

5. Preliminary Questions ä ä Existing Environment ä ( ä Hardware (SUN/HP/IBM/Sequent/Others) ä ä Oracle (Version) ä ä Oracle Applications (Version) ä ä Front End (Char / GUI / Citrix / NCA) ä ä Other ERP Systems ä ä Existing Implementation ä ä (In-house/Consulting/Both) ä ä Actual Start Date ä ä Actual End Date ä ä $ Value ä ä User Base Number (On-line v/s Remote) ä ä Existing Architecture ä ä Single/Multi-Install ä ä Multi-org Architecture ä ä Vanilla Implementation(Y/N) ä ä Critical Business Processes Bolt-on ä ä Interfaces (Y/N) ä ä EDI (Y/N) ä ä Reporting DB/Tool (Y/N) ä ä Data Warehouse (Y/N)

6. Year 2000 Compliance ä Releases of Oracle Applications prior to 10.7 are not Year 2000 compliant ä Oracle and most industry experts strongly recommend that businesses move to Year 2000 compliant applications no later than June, 1999 Migration to Internet Enabling Applications (NCA) ä New functionality ä Significant improvements in scalability and ease of development/systems management Critical Upgrade Issues

7. Migration to Multi-Org for Global Deployment ä Oracle’s new Multi-Org feature enables effective multi-site and global deployment of Oracle Applications without customizations Upgrade to Current Release ä It is necessary to stay current with the major releases of Oracle Applications to receive the highest level of service from Oracle Support Optimize Business Processes ä Optimization of core business processes is an ongoing challenge for any organization. Most organizations find it difficult to sustain a focus on business process optimization after initial implementation of Oracle Applications.

8. Critical Upgrade Issues Reduce Reliance on Customizations ä Significant changes in the supporting technology for Oracle Applications will require many companies to redesign or significantly upgrade custom code ä Year 2000 compliance and Multi-Org will also require retrofitting most customizations written before Release 10.7

9. Upgrade Methodology ä Checkup ä Review current critical processes to accommodate a changing business ä Infrastructure analysis (hardware and network architecture) for NCA/Internet enabled deployment of Oracle Application ä Impact Analysis on customizations and interfaces with new Oracle Application Architecture ä Explore Web Enabled Self Service Applications and Electronic Commerce Technology (EDI gateways, Intranet and Internet based solution)

10. Upgrade Methodology ä Upgrade ä Implement new Oracle modules and features ä Design and setup multiple organization structure ä Execute upgrade process including client specific pre and post upgrade steps ä Retrofit customizations and interfaces to support Y2K and Multi-org Application Architecture ä Implement decision support applications ä Consolidation of multiple sets of books into a single, multi- site implementation ä Rollout applications to additional sites ä Migrate to WEB enabled (Oracle NCA) architecture

11. Upgrade Methodology ä Central Repository ä Document templates for each major deliverable to ensure quality and consistency throughout upgrade project life cycle ä Application Design Standards ä Application Development Standards ä User Testing Standards - emphasis on Y2K testing ä Training and QA Standards ä Comprehensive patch list for patches ä Comprehensive Bug list for each Oracle Application ä Methods, techniques, toolkit and control mechanism ä Comprehensive Project Plan (milestone driven) ä System Performance Management Techniques ä Control Systems for TAR Management and Patch Management

12. Upgrade Methodology ä Strategy, Checklist and Plans ä Infrastructure Analysis ä NCA deployment Strategy ä Instance Management Plan ä Concurrent Development Strategy ä User Test Plans ä Acceptance Test Strategy ä Production Cut-over Plan ä Post-production Mission Control Plan

13. Upgrade Methodology ä An integrated approach that keeps the focus on business results during technical upgrades ä Applies business-focused implementation methodology to upgrades: ä Upgrade to current, vendor-supported technology ä Achieve tangible business results for relatively small incremental investment ä Transfer significant knowledge to client project team to achieve rapid transition and consulting team roll-off

14. Upgrade Options 9.x or 10.x Std 11.0 Std Upgrade Process Option 1: Stand-alone installs to 11.0 Standard Stand-alone installs

15. Upgrade Options 11.0 MO 9.x or 10.x Std Converted 11.0 M.O. Empty 11.0 M.O. Configure MO with Setups New Install 11.0 Option 2: 9.x or 10.x Standard stand-alone installs to New/Fresh 11.0 Multi-Org Install

16. Upgrade Options 9.x or 10.x Std 11.0 MO 11.0 M.O. Configure MO with Setups Upgrade Process 11.0 M.O. Option 3: Upgrade one Standard stand alone install to 11.0 Multi-Org and Convert other 9.x or 10.x Standard Stand Alone installs

17. Upgrade - Key Functional Tasks ä Conduct ‘Analysis Phase’ to establish baseline ä Review critical processes ä Determine upgrade impact ä Review list of customizations and determine the disposition of each ä Finalize and refine scope ä Publish relevant gap list of features and functions ä Assess current business process environment in relation to new Oracle Applications functionality ä Determine new process design ä Develop acceptance testing strategy and test plan ä Develop production cut-over and post-production mission control plans

18. Upgrade Details - Key Technical Tasks ä Manage the technical upgrade process including client specific pre and post upgrade steps ä System Performance Management ä Database architecture, sizing and tuning ä Impact of moving to NCA architecture ä Backup and recovery requirements strategy ä Applications tuning ä Customizations tuning ä Develop initial customizations list ä Assess total technical effort using our repeatable Porting Matrix and Year 2000 compliance steps ä Develop concurrent development strategy ä Assess impact on interfaces and “downstream” systems ä Port and test relevant customizations ä Infrastructure-Analysis NCA deployment strategy

19. Upgrade Details - Recommended Documentation Functional ä Major Gaps Analysis ä 10.7/11 New Features Training ä New Features Deployment Strategy ä New Process Designs ä User Acceptance Testing Approach ä Cutover Strategy Technical ä Upgrade Checklist ä Customizations Matrix with Dispositions ä Customization Impact Analysis ä Technical Infrastructure Plan Including NCA Impact ä Concurrent Development Standards ä Coding and Development Standards

20. Conclusion - Full Upgrade Solution ä Year 2000 Compliance ä Optimize Business Processes ä Migrate to Multi-Org for Global Deployment ä Upgrade to Current Vendor Supported Technology ä Migrate to Internet Enabling Applications (NCA) ä Reduce Reliance on Customizations

21. Questions & Answers