Importance of a

CRP run.
r n

Conference Room Pilot

CRP of ERP 1 j.zaveri@dnserp.com

 CRP IS LIKE SIGNING A
DELIVERY CHALLAN
‹ Successful
S f l implementation
i l i off any
ERP requires change in attitudes
andd old
ld h
habits
bit
‹ As it builds a good foundation for
information flow in your
organization, the importance of
ERP has to be understood at all
levels.

CRP of ERP 2 j.zaveri@dnserp.com

 Proper CRP will also ensure that the
cost and time will be minimal for all
concerned.
‹ Formally appoint an ERP coordinator/s
„ Full time assignment
„ Not necessarily an IT person
„ ERP vendor will impart necessary training to
‘coordinator/s’ on various aspects of ERP.
Especially on the MIS and data structures.
structures
This is to reduce dependability on ERP
vendor and gain confidence in the ERP
system even after implementation is over.
over
„ In turn the coordinator will train other
users. This will ensure a smooth handover
off programs from
f ERP vendor
d team
t to
t you

CRP of ERP 3 j.zaveri@dnserp.com

 Appoint chief of ERP
project
‹ The
Th P
Principal
i i l / Dean
D / Registrar
R i t or
the owner or
the top finance man
„ He has necessary authority

„ He will have to spend time in the

review meetings – between
coordinator and DNS ERP
implementers team - during the full
CRP run till the roll out stage

CRP of ERP 4 j.zaveri@dnserp.com

 CRP run = First ERP
demonstration
‹ Users
U from
f accounts, purchase,
h
admission, stores, academics,
lib
library, administration,
d i i t ti and
d allll
other concerned officers who is
going
i to
t contribute
t ib t th
the input
i t data
d t
or are users of ‘DNS ERP’ outputs
mustt be
b presentt

CRP of ERP 5 j.zaveri@dnserp.com

 Password
As yyou increase security,
y yyou lose convenience.

‹ USER MANAGEMENT
Define security levels
„ Administrator, Executive, Users
‹ Access - Rights
„ Which menu to be visible for whom
‹ Master Creations

CRP of ERP 6 j.zaveri@dnserp.com

 Infrastructure
‹ Assess hardware
A h d requirement
i
details to get the optimum
performance
f for
f ERP package.
k
For instance, upgrading RAM, etc.
‹ Network speed
‹ Modem and net connections

CRP of ERP 7 j.zaveri@dnserp.com

 CRP run
‹ Prepare Masters
‹ Enter one month data
‹ Ensure all possible scenarios
‹ Opening balances from signed audited balance
sheet
h t
‹ Certify Printouts – physical file of Hardcopy
‹ Carry out essential customization
‹ Involve Auditors, CA, consultants
‹ LIMIT UNNECESSARY CUSTOMIZATION
‹ Prepare the POC (Proof of Concept) file
and user must sign

CRP of ERP 8 j.zaveri@dnserp.com

 About ERP Project
‹ We
W have
h b
been ddoing
i ERP
implementations for over a decade.
‹ We have gathered real life experience
and would like to share some lessons
that we have learnt in the past
„ Some DO and DON’T

CRP of ERP 9 j.zaveri@dnserp.com

 LESSONS # 1
1. DNS iimplementation
l t ti mustt b
be a B
Business
i P
Project
j t
„ IT is only the enabler
2. Ignore Change Management at your own peril
„ DO BPR
3. Also consider retention policy
„ Announce incentive
4. Resources / People
„ Put your best people on the DNS ERP Project
5. Adequate IT infrastructure is a must
6. Top management must be present in the review
meetings

CRP of ERP 10 j.zaveri@dnserp.com

 LESSONS # 2
1. Pay attention to the quality of your Master
D t
Data
„ Well worth the time spent to get it right

2
2. Definition and implementation of Backup
Strategy is essential
3. CRP Run is critical exercise for ERP success
4. Budget as per TCO [total cost of ownership]
plan
5. Li it customization
Limit t i ti
6. ERP implementation is a journey and not a
destination

CRP of ERP 11 j.zaveri@dnserp.com

 ‹Proof of concept
p and roll out

Thank you
y

CRP of ERP 12 j.zaveri@dnserp.com