Top 5 Tips to Cut the Effort of your Oracle EBS R12 Project by a Third

Jonathan Pearson, Solutions Consultant

Top 5 tips to cut the effort of your

Oracle EBS R12 project by a third

Delivering Quality Through Innovation

© 2013 Original Software

Oracle EBS is…

Critical & Integral – runs the business

Very complicated – a mystery to most

Often customized

Challenging to test


Vote in this quick poll

What is your company’s current situation?

Already upgraded to R12.1

Plan to upgrade to R12.1

Plan on deciding when to upgrade to R12.1

Are discontinuing use of EBS

Getting support for 11i via 3rd party

Re-implement EBS


Situation Assessment

End of life coming for 11i

Tip 1

Understand who needs to be involved


Upgrade responsibilities

IT responsibility

Database Changes

Customization redevelopment

Project Management

Business responsibility

Functional & process changes

System validation

UAT

Training Materials


Stakeholders

Training

Business Analyst

Power User

DBA Programmers

Help Desk

Project Managers Business Leaders



How many Power Users do you expect to

involve in Testing & Validation?

Less than 10

10 to 30

31 to 50

50 to 70

Over 70

Tip 2

Understand how much effort it will take


Overlooked impact


Typical work impact

and cost of effort

Tip 3

Understand the biggest challenges


Biggest challenges

Confirmed top 3 Challenges

Inadequate validation processes

Poor communication and collaboration

Limited access to needed business resources


Optimized validation

Current 11i functionality defines

requirements of R12 testing

Customizations add to complexity

“ALL about TESTING and

VALIDATION” a business perspective

You need to involve business to test –

in a big way


Are you enabled for success?

Are your current scenarios

well documented?

Are your business users

easily accessible?



How well documented are your business

processes?

Poorly

Some documentation, likely out of date

Customizations documented, little else

Well documented

Tip 4

Centralize your information


Knowledge transfer is key

Transform “Tribal” knowledge

into formal

It’s all about collaboration


Why do you need a

knowledge base?

Sheer volume

Prioritize

» Business critical vs. low impact

» High risk vs. low risk

Categorize

» Standard vs. Customizations

Various & Numerous people

involved

Different skills & areas of expertise


Foundations for collaboration


What to collaborate?

Project plans

Resources

Timescales

Tasks

Progress

Coverage

Re-use

Knowledge

Data

Environments

Availability

Audit

Traceability

Customizations

Complexity

Process


Collaboration – How?

How to establish a Knowledge Base?

Workflow & Process to “herd the cats”

Dashboards & Visibility

Time saving tools

Tip 5

Implement process best practice


Understand the upgrade process


Once upgrade process starts…

All ongoing initiatives

stop until upgrade is

done

Make this your reality

What needs to be in place?


Technology can help

Provide Structure & best practice

Unified collaboration

Capture knowledge

Manage validations

Effective automation



What is the most important success factor for an

Oracle EBS upgrade at your organization?

Minimize the risk of the application not supporting

core business

Minimize the project cost

Deliver as quickly as possible

Minimize the time business users

participate in the project


Technology benefits

Ensure Success

Greater coverage, less risk

Increase Visibility

Shared problem, shared success

Minimize Impact

Start Quickly

Easy to use

Save 30% Time, Money

During upgrade

On-going patches

Eliminate a CRP


Projected savings in labor


The difference between

success and failure…

Thank you for joining us

Complete this Oracle EBS R12 upgrade

survey and receive the survey report

origsoft.com/oracle-survey

Get in touch…

Call: UK +44 (0)1256 338666 l USA (1) 630 321 0092

Click: www.origsoft.com/contact

Email: [email protected]