ERP Requirements Definition

Today, our industry is inundated with a plethora of ERP checklists. There are two problems with checklists: completeness and definition.  At Ultra we do not believe in ERP requirements checklists.  They add little value in evaluating ERP systems.

An ERP project is all about business process transformation with modern ERP technology. Therefore the requirement’s definition should focus on defining the future state of business processes and evaluating the ERP implementation against that future state business process model.  The future state business process model becomes the requirements definition.

The ERP requirements definition becomes a script of business processes.  The function requirements are listed within the process script.

The vendor demonstration becomes a demonstration of the future state business processes. Think of the ERP demonstration as a “day in the life” process presentation.

The demonstration starts with defining a product and then progresses through the sale process, the planning process, the production process, the shipment process, and the accounting process.  Included in the presentation are engineering processes, quality processes, warehouse processes, and human resources processes.

The ERP selection team grades each vendor on how well their system addresses the processes defined in the script.

The presentation requires the ERP vendors to use the client data.

An important part of the evaluation is ease of uses and access to information.  Treat these areas as general topics that should be understood at the front end of the presentation.