The information gleaned from data-mining initiatives is useful, so you'll need a plan to ensure continued success in this area. The cost of warehousing data from the new system needs to be included in your budget, too. While there are many correlations between an ERP implementation and other software projects, one aspect of ERP is unlike other software projects you may have undertaken. Your staff members' knowledge of your new ERP system is invaluable, and new work is created after implementation that requires their acquired expertise. You'll need to account for new staff to fill the holes your ERP team will create.
Many companies expect to see value returned from an application as soon as it is installed.
Neither of these expectations is realistic with an ERP implementation. An ERP's value can't be known until after the company has concentrated on making improvements in the business processes affected by the new system. Once your implementation is complete, you need to allow time for the kinks to be worked out of the system and the business process. An initial drop in productivity may occur while people get comfortable with the new system and processes, depending on how many changes were made. Familiarity may breed contempt, but it definitely lends itself to a higher productivity rate.