Oracle E-Business Suite Release 12.2 momentum is growing. Come to this session and hear from Oracle and its customers regarding experiences deploying and running Oracle E-Business Suite 12.2. Customers will discuss lessons learned in the process of upgrading and reveal how they are using new functionality in Oracle E-Business Suite 12.2, including the Online Patching feature.
14. Imagination at work
GE Transportation
Oracle EBS R12 Upgrade
October 28th, 2015
Andrew McVeagh – Oracle CoE Leader
GE Proprietary Information—Class III (Confidential)
Export Controlled—U.S. Government approval is required prior to export from the
U.S., re-export from a third country, or release to a foreign national wherever
located.
15. We are GE Transportation.
We set potential in motion.
15
Rail
Drilling Services
Mining Marine
Stationary
19. Our Business runs on Oracle
A Case Study: GE Transportation R12 Upgrade
19
20. How we use Oracle E-Business Suite
Shop Floor to Financials
20
62 Active Modules including…
• Bills of Material
• Cash Management
• Collections
• Depot Repair
• Field Service
• General Ledger
• Inventory
• Latin America Localizations
• Master Scheduling/MRP
• Mobile Applications
• Order Management
• Payables
• Projects
• Purchasing
• Receivables
• Regional Localizations
• Shipping Execution
• Supplier Scheduling
• Warehouse Management
• Work in Process
18 Active Countries
• Australia
• Brazil
• Canada
• China
• France
• India
• Indonesia
• Italy
• Kazakhstan
• Kenya
• Mexico
• Mozambique
• Netherlands
• Singapore
• South Africa
• Sweden
• United Kingdom
• United States
…and everything in between
6 Languages In Use
• American English
• Brazilian Portuguese
• Italian
• Latin American Spanish
• Russian
• Simplified Chinese
21. Why Oracle R12? | Benefits & Focus Areas
Oracle EBS 11.5.10.2 12.2.3
• Reduced downtime (online patching)
• Required foundation (GE Global Enterprise Standards)
• Enhanced Drill-back/down capability (GL to Sub-Ledger)
• Premier Oracle Support for our environments
21
Focus Areas - Key Functional Changes
• Required financial redesign (Custom Inventory Transaction Pre GL Processor retired)
• Localizations were all redesigned by Oracle for R12
o Brazil required full redesign and integration with 3rd parties
o Italy and other localizations required some rework
• Oracle moves to some web based forms vs. traditional java forms
o Customer, Vendor forms etc.
22. Oracle R12 | Journey
Mar
Functional ReadinessFunctional ReadinessEnd to End System RemediationEnd to End System RemediationHack-a-thon Code-a-thonCode-a-thon
Feb Mar Apr May Jun Jul Aug Sep
Go LiveGo Live
Apr ‘15
Technical Design & Code Remediation Finance, Brazil, 3rd party & Downstream Systems User Acceptance Testing & TrainingEBS Upgrade
Oct Nov Jan FebDec
22
Project Phases
Code-a-thon
• Identified and architected similar changes and provided guiding principals for coding changes
• 50 developers worked to resolve identified issues over 60 days
End to End System Remediation
• Drove financial re-architecture, interface remediation and changed business process where mandatory
• Monitored key performance indicators for any underlying issues
Functional Readiness
• Sent team members to key locations globally to train and assist during full end to end user acceptance testing
• Saturated business with communication and training
Hack-a-thon
• Leveraged a focused team to deliver a working environment in 10 days
• Ran the upgrade on a test environment to see where we stood and started remediation
Go Live
• Executed business continuity plans during 100 hour upgrade outage
…a faster approach to ERP Upgrades
23. 11 upgrade cycles
3 dry runs for cutover
372 step detailed cutover plan
DBA commands scripted
One team mentality
Divide and conquer approach
Global updates twice a week
Weekly executive updates
Business Ownership of Signoff
All users surveyed for readiness
Signoff by executives by area
IT delivered, business decided
2 month hard freeze
Meticulous tracking of changes
Patching cycle coordination
Force all updates in IT tools
23
Technical Preparedness Accountability
Teamwork Change Management
Oracle R12 | Key Success Factors
25. Oracle R12 | Key Lessons Learned
• Give ample training opportunities and survey for effectiveness
Communication and Training
• Business Continuity Planning needs 3-4 months minimum planning
• OVER communicate via every method available to your team
26. Oracle R12 | Key Lessons Learned
• Send key IT and functional users to sites for UAT
User & Performance Testing
• Ensure all key business workflows are covered (close gaps SIT to UAT)
• Performance Testing: 4 months before go-live … you will need to tune
… 80+ person cross functional team, 500+ UAT testers
27. Oracle R12 | Key Lessons Learned
27
• Keep development team for issue resolution for at least 8 weeks
Go-Live & After-care plan
• 24*7 dedicated help line – manned with project team
• Establish rhythm for executive report outs during and after go-live
28. Oracle R12 | Facts and Summary of Issues
28
• Oracle Concurrent Manager – directory structure – start in empty directory
• IT help & support line: 309 questions over 2 weeks
Post Go-Live Facts
• KPI Monitoring: Continuous evaluation of business indicators
• Total # of unique users logged into Oracle R12: 3321
A review of key resolved issues
• Advanced Supply Chain planning – Demand was being dropped - patch
• Minimum requested order quantities ignored for 3% of parts – patch
• 6 Finance issues - critical to April close - Worked SR’s – SLA configuration
• 10-15 key Oracle forms did not work properly - Recompiled corrupted files
29. Our business is running well on R12
Functional
Outcomes
• All critical business processes worked on Day 1
• All users trained and able to work on system
• Equivalent Functionality and Reports
• 6 Successful Monthly Closes
• 2 Successful Quarterly Financial Closes
• Close cycle time remains unchanged
• Compliant & Seamless reporting (OBIEE & Hyperion)
Ongoing Support
• Optimize close to increase cycles per day
• Monitor KPI’s for any underlying issues
Ongoing Support
• Resolve remaining R12 bugs with Oracle development
• Monitor all sub-systems for health and performance
Technical
Outcomes
• Technical conversion successfully completed
6 months post go live – operating successfully
• On-line patching cycle successful
Took <90 minutes, previously 12+ hours on 11i
• No reduced performance for business users
Initial performance issues resolved
Initial forms lag resolved
29
Oracle R12 | Summary & Outcomes