Initial Requirements study:

ERP decision involves considerable investments.   It is necessary that the top management of the company is crystal clear about what they really expect from an ERP package.

It is necessary that the top management team members along with the functional management team members are fully involved in defining their requirements of the ERP that the organization contemplates.  This will also give clear idea as to what ERP will do and WHAT ERP WILL NOT DO.  The expectations for the actual user mangers are set right through this approach.  Another advantage is in form of getting "commitment of ownership" by the actual user managers in the subsequent phases of ERP implementations.  As nothing was forced on them, the chances of user managers putting up resistance at a later stage stands reduced.

One simple question needs to be addressed:  What do we expect from integrated software package, such as DNS?  Typical answers to this question could be as follows.  This will also spell out ROI (return on investment).  Instead of asking general question, 'what is ROI', ask will DNS be able to achieve the following?  That means you are clear about your definition of ROI. 

• Reduction in inventory of raw materials, (or WIP and finished product).

• Real time MIS

• Improvement in delivery performance

• Improvement in productivity through elimination of duplication

• Reduction in response time to react to customer requests / design changes.  ................

• Less-paper office

• Preparing of accurate and faster sales invoice.

It is very easy to go on adding expectations to this list.  Then it could become more of a 'wish-list' that is far from what the actual requirements are.

As is always said, there is difference between what one wants and what one needs !!