Malone r12 upgrade-versus-reimplementation


Published on

Published in: Education, Technology
  • Be the first to comment

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

No notes for slide

Malone r12 upgrade-versus-reimplementation

  1. 1. Delivering Oracle Success R12 Upgrade Vs. Re-implementation John MaloneHeartland Oracle Users Group Conference October 20, 2011
  2. 2. About DBAK Oracle solution provider Co-founded in 2005 Based in Englewood, CO Core Technology and EBS Applications More than 140 implementations, upgrades, conversions, and support projects for 90+ clients Average 15 years of Oracle expertise Oracle Gold Partner OEM “Specialized”
  3. 3. Agenda Upgrade vs. Re-implementation Impact Analysis Case Studies Questions© DBAK 2011 3
  4. 4. Upgrade vs. Reimplementation Data quality Changes to Key Flexfields Multiple Oracle EBS environments Significant changes to business structures (acquisitions, mergers, re-organizations) since initial implementation Number and complexity of customizations Changes to business process requirements Oracle EBS version© DBAK 2011 4
  5. 5. Upgrade vs. Reimplementation Upgrade Re - Implement 1 2 3 4 5 6 7 8 9 10 Does your Application configuration still meet your business requirements? (considering They meet our A change is needed growth,expansion, acquisition) requirements Do you wish to make changes to configurations that cannot be easily Our existing We require modified (flexfield structures, Customizations, configuration is OK changes Calendar) Has your business structure changed Our structure is correct Our structure significantly since your implementation for our needs needs to change ( more/less business units/orgs, currencies, shared services) How significantly have you integrated with 3rd party applications that could be Not Much Significantly replaced with new Oracle Applications modules, features or functionality?© DBAK 2011 5
  6. 6. R12 Methodology Phase I Phase II Test R12 Assessment and Impact Analysis Iteration 1 Test Iteration 2 Test Iteration 3 - New Features Prioritization - Technical Architecture Analysis UAT - Application Architecture Analysis - Assessment Review - Project Scope Training - Project Schedule Post-Production Support Planning and Execution Milestones R12 Go Live© DBAK 2011 6
  7. 7. Impact Analysis New Features Prioritization Technical Architecture Analysis Application Architecture Analysis Assessment Review Project Scope Project Schedule© DBAK 2011 7
  8. 8. Impact Analysis New Features Prioritization New/Changed R12 Features and Functionality • Review existing (standard and custom) functionality within 11i and look for opportunities to leverage new features within R12 – Primary goals are to: » Remove customizations where possible » Identify opportunities to leverage new R12 functionality • Analyze impacts to current business processes and determine the approach going forward with R12 • Determine which new features will be included in the R12 upgrade and which features could be included in post upgrade projects • Reference Materials – Release Content Documents (RCD) – Release Value Proposition (RVP) documents – Product specific upgrade guides (e.g. Financials, Procurement) – Oracle E-Business Suite Release 12.x Information Center© DBAK 2011 8
  9. 9. Impact Analysis Technical Architecture Analysis Technical Architecture • Analyze impacts to the infrastructure between 11i and R12 – Servers – Operating System version – Database version – Application Server version – Disk Space (Storage) requirements – Reporting – Workstations (e.g. browsers, memory, CPU) – Third party software impacts • Reference Materials – Upgrade Guide for 11i to R12 – R12 Infrastructure - Differences between 11i and 12 – Oracle Applications Release 12 Upgrade Sizing and Best Practices© DBAK 2011 9
  10. 10. Impact Analysis Application Architecture Analysis Application Architecture and Extensions/Customizations • Interfaces with 3rd party applications • Workflow • Reporting tools (e.g. BI Publisher, e-Text) • New application modules • Impact to existing extensions/customizations • Reference Materials • Upgrade Guide for 11i to R12 • 11.5.10 to 12.x EBS Object Changes© DBAK 2011 10
  11. 11. Impact Analysis Assessment Review Review Impact Analysis results Project Scope Develop Project Scope • Determine Upgrade or Reimplementation Approach • Consider: – Technical Architecture Impact – Applications Architecture and Extensions/Customizations Impact – New/Changed Features Prioritization – Functional and Business Process Impact Assessment© DBAK 2011 11
  12. 12. Impact Analysis Project Schedule Develop Project Schedule based on Impact Assessment results • Including timeline, resources, and cost • Leverage experienced R12 resources to supplement internal team members • Project schedule/plan • Reference Materials • E-Business Suite Technical Guided Upgrade Path from to 12.1.3 • Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 Next Steps Organize and launch Phase II (Upgrade) • Determine if you want to use Maintenance Wizard or other tools (MS-Project, Excel) to track and manage upgrade tasks • Start Iteration 1 test and customizations migration© DBAK 2011 12
  13. 13. Case Study – R12 Upgrade for an Energy Company Company Description Scope • Leading provider in the mid-stream services for the • Develop the methodology and tools for completing the R12 natural gas industry. Headquartered in Denver, the upgrade project. company is engaged in the gathering, processing and • Conduct the upgrade assessments to define the project transportation of natural gas; the transportation, scope, resource requirements, and project schedule. fractionation, storage and marketing of NGLs; and the • Manage the upgrade project tasks, resources, issues, and gathering and transportation of crude oil. risks Management Challenge Results • The company implemented Oracle Financials, Projects, • Completed the impact analysis for new/changed features, iExpense, and Logical Apps in the 2007-2008. They have customizations, application architecture and infrastructure approximately 200 core application users and all employees are iExpense users. They have a moderate • Created a detail project schedule and assigned resources number of extensions/ customizations and several to the various work streams. mission critical interfaces between Oracle EBS and their • Utilized extract out of Maintenance Wizard to create the revenue/operations applications. initial list of upgrade tasks • The project objective was to migrate the Oracle • Completed three upgrade test cycles (iterations) and User applications from 11.5.10 to R12 and also upgrade the Acceptance testing database from 10g to 11g. The upgrade would be • Created end user training materials and conducted training installed on a new server and include an upgrade of the courses operating system. • Executed the production cutover plan to complete the • High level planning had been completed but the approach upgrade over a weekend to minimize impact on daily for executing the project had not been determined. business operations. • Project was completed on-time (6 months) and under budget. There were very few post-production issues.© DBAK 2011 13 13
  14. 14. Case Study – R12 Implementation for Services Company Company Description Scope - Re-implement Oracle E-Business Suite (R12.1.3) • Leading provider of software and services that help the • Impact Assessment world’s best companies manage their extended workforce – Review existing 11i functionality and procured services. – New R12 functionality • Global provider of contingent labor. » Prioritize new features Management Challenge • Leverage setups from existing 11i system • The companies Oracle E-Business suite had not been • Re-implement Oracle R12 for existing modules upgraded in many years (version 11.5.4), however • Migrate required customizations and interfaces to R12 business changes required changes in how the company • Limited Data Conversion: used Oracle. – Due to increasing volume and a need for additional – GL –Balances and current year transactions flexibility, a custom front office application was – AR/AP – Customers/Suppliers developed to replace Oracle Projects. The legacy – AR/AP – Open invoices Projects data still exists and there is a large quantity of data that is no longer used. – Fixed Assets – load existing into R12 – Implement new module: Fixed Assets. • System Setup / System Validation / Integration Testing – Consolidation of many operating units • Migration to Production • The company wanted to expand use Oracle functionality Expected Results to enable business processes • Expand usage of current Oracle functionality to enable – The company wanted to take advantage of new business processes features within Oracle R12 • Ability to use new R12 functionality – Enable existing functionality not being used to automate business processes • Reduction of customizations • Key implementation versus upgrade decision factors • Clean-up of old/non-used data – Limited Down-time available for cutover • Ability to quickly cut-over to the new system – 11.5.4 version expanded the tasks required for • Deployment on new hardware platform upgrade • Consolidated operating units – The company is switching to a new hardware platform© DBAK 2011 14 14
  15. 15. Questions© DBAK 2011 15
  16. 16. Contact John Malone 720.475-8600 Presentation available at:© DBAK 2011 16