Guardian News & Media (GNM)Oracle E-Business Suite R12

UpgradeWith Mokum & Panaya

April 2013

   

Introductions & Background• Richard Eltham, Technical Manager, Mokum• Weeb Cnossen, Marketing Programs Director, Panaya• Binyamin Kamilar, Senior Customer Success Manager, Panaya• David Taylor, Technical Analyst, Oracle Applications Team,

GNM(formerly Technical Consultant

at Mokum)• Technical Team Lead on GNM’s Oracle R12 Upgrade

Project

• Oracle E-Business Suite Financials & HR: from R11.5.10 to R12.1.3

• Project duration: July 2012 to April 2013

• Systems Integrator: Mokum

• Largest European consultancy focusing exclusively on Oracle Applications

• 150 permanent staff, serving every vertical, particularly financial services, retail, transportation, media and public sector

• Completed more E-Business Suite R12 upgrades in the UK than any other consultancy

• Oracle Gold Partner

• UK presence, with offices in London, Manchester and Dublin

• UKOUG Partner of the Year award winners since 2009• E-Business Suite Gold Partner of the Year – 2012 and 2013

• Pioneer and Market leader in SaaS-based ERP Upgrade and Maintenance Automation Technology

• Selling globally in 50+ countries with 1,000+ customers

• 2200+ successful projects (of which 200+ EBS R12 Upgrades)

• Oracle Gold Partner

• Advocated on oracle.com as a way to reduce the cost and risk of the R12 upgrade

• UKOUG Silver Partner of the Year Award winners 2013

Why Panaya?• In partnership with Mokum: Panaya was part of the R12

upgrade “package” offered by Mokum to GNM

• Used to identify existing customisations in R11 (11i), and to detail the R12-upgrade coding and unit-testing tasks

To provide a robust, reliable baseline for the estimation, resourcing and planning of R12 upgrade technical work

• Also, to identify customisations rarely used, and consider retiring them, rather than upgrading to R12

How was Panaya used at GNM?

To provide a baseline for the estimation, resourcing and planning of R12 upgrade technical work

To project manage the R12 coding and unit-testing tasks on an object-by-object basis, using Panaya’s project management portal

¨

Panaya Extracts and Analyses at GNM1. Extracted a list of custom eBusiness objects from R11

Production instance (using Panaya extract utility)2. Performed weekly Panaya extracts prior to, and during, the

R12 upgrade project3. Performed Panaya analyses, to provide the following:

- Details of coding and unit-testing tasks to upgrade each object to R12

- Estimated effort per upgrade task- Usage statistics for “user-entry points” (custom and

standard reports, forms, concurrent programs, etc.)

Using the results…1. Identified customisation retirements, based on Panaya

usage statistics and consultation with the business

reduce upgrade effort2. Grouped custom components into Logical Units of Work (by

Apps module and function) – this was a “manual” processe.g.

“GNMAP001_RCS_Interface”3. Calculated sum of Panaya coding and unit-testing estimates

per LUW, and added 25% effort per LUW (for admin, documentation, code installation scripts, etc.)

4. Compared total estimated technical effort with project timeline, and determined number of developers required

GNM R12 Upgrade Statistics (approx.)• 4100+ custom objects identified in R11 Production instance• 30% R11 customisations retired prior to R12 upgrade• Custom components grouped into 96 custom LUW’s (“modules”)

GNMAP001_RCS_Interface

GNMAP002…• Traditional Estimate: 850-1100 days• Panaya Estimated coding/unit testing effort: 300 days• Bulk of Technical upgrade work to be delivered in 10 weeks (50

days) 6

full time developers• Actual: 537 days – included CR’s, UAT rework and Post Go-Live

Support

Unit-tested, R12-upgraded customisations delivered on time, and on budget Overall savings relative to traditional estimate- 36%

Panaya – brief appraisalStrengths• Automated listing and analysis of R11 customisations…

reduces manual effort during project planning stage provides a robust, reliable baseline for estimation,

resourcing and planning• A comprehensive Panaya knowledge base underpins automated

coding analysis

Weaknesses• Project managing individual coding tasks is time-consuming

managed on the basis of delivery of LUW’s for UAT, and UAT sign-off• Some custom objects were outside of Panaya’s scope at time of

project: OA Framework customisations and personalisation's [now

available] Custom Discoverer EUL objects (Folders) [now available]

Panaya case studies on Oracle.com

• An assessment of the complexity of customer’s upgrade project based on the total number of customizations

• Usage analytics to scope what can be cleansed from the system when moving to Release 12

• A project plan including the number of corrections and tests required, prioritized by the likelihood of failure in Release 12

Complementary Upgrade Analysis

Questions…

Interested in a live demo? Visit Panaya - Stand #37Visit Mokum - Stand #41