This arguably, the most crucial phase for the success of the ERP implementation. Put very simply, this is the process through whichiTtpanies create a complete model of where they are now, and in which direction they want to head in the future. The trick is to design a model, which both anticipates and covers any functional gaps. It has been estimated that even the best ERP package, custom tailored to a company's needs, meets only 80% of the company's functional requirements.
The remaining 20% of these requirements present a problematic issue for the company's BPR (business process reengineering). One of the most affordable, albeit painful, solutions entails altering the business to 'fit' the ERP package. Of course, a company can simply agree to live without a particular function (the Ch/ but annoying solution). Other solutions include:
Pinning your hopes on an upgrade (low cost but risky) entifYing a third-part~ product that might fill the gap (hopefully it also partners with the ERP package~eeping interfacing to a minimum)
.( Designing a custom pro'gram /
. ftering the ERP source code, (the most expensive alternative; usually reserved for mission-critical installations)
as all implementations are becoming most cost-sensitive, the BPR approach has come under some real scrutiny.
|
