Tuesday 5 July 2011

CRP and all about its Approach !!

Welcome first time implementor !!!

Apologies if you are not, but this is really what I thought when you landed on this page.

CRP... a buzz word amongst ERP implementors (one of them being me!) n more often you are challenged to prove your metal in IT world with how good and goregeous your CRP is ... 90 % of time its measurement for an ability for functional consultant !!!

Lets get serious now!


What is a CRP?

The definition of prototyping, or a conference room pilot (CRP) is “a product model constructed for testing and
evaluation to see how the product performs before releasing the product to manufacture.” A conference room pilot is
exactly that, a prototyping of the software functionality and customizations prior to releasing the product to the end
user.
Each customization should be prototyped and executed during a series of detailed pilots or module walk-throughs.
Each pilot should be designed to target a specific stage, event, or business process of the enterprise during an
implementation and should determine success or failure as the outcome.
Some organizations may want to have separate module walk-through or prototyping sessions for departmental
customizations. The entire project team should participate in the execution of the CRP, validating the interoperability
of the business processes and customizations.
The objective of this paper is to walk through the steps required to design an effective CRP. The diagram
(Figure 1)
depicts the process, with subsequent pages providing additional supporting information for each stage.
Where to begin?
The best place to start is to describe the overall process of a CRP. Obviously this is only one approach, and there are
many ways in which a CRP can be defined and executed. Here is an approach that we’ve used in the past that has
been very successful. The diagram below
To assist in documenting the future organization the creation of documents known as the future business models are
created. These will become the “to be business model” documents for your organization. These will also become the
driving force behind the creation of your new organization. These future models will be reorganized to fit the Oracle
Applications, and another new document gets created, called business scenarios. These business scenarios are
mapped to fit the terminology and functionality of the Oracle Application modules.
(Figure 1) describes the steps of getting to a CRP.
Stage 2:Definition Stage 3:Execution
Stage 1: Identification
Generate List of'
Business Scenarios
Analyze Current
Business Processes
Determine Current
Business Requirements
Define Future
Business Processes
Determine Future
Business Requirements
Create Testing Scenarios
Create Master
CRP Plan
Create Business
Scenario Scripts
Create Testing
Scenarios Scripts
Execute CRP
Schedule Resources
Execute CRP
Execute CRP
Success!
1
3
2
Create Training Scenarios
Create Training
Scenarios Scripts
Resolve CRP Issues/Problems
Figure 1