ERP/MRP II SOFTWARE: Valuable Tips for Selection & Implementation

By Chris Gray

Over the years, the MRP II component of ERP software has gotten more and more complex. Unfortunately, too many people still think that more software features make implementation easier. In fact, my experience is the opposite. Extra features, beyond the core logic needed to make MRP II work, can cause time-consuming distractions from implementing business improvements.

PITFALLS

With "fully-featured" software, there are more potential pitfalls. Complex software is difficult to modify and hard to interface. As a result, it is easy to fall into the trap of the "cold turkey cutover" which some software developers would advise-"Use the software unmodified. Implement the whole integrated set of systems so you don't have to do any interfacing. Just get users properly motivated to make the switch over a weekend." The more complex the software, the more likely you'll follow this approach and be distracted from using implementation as an opportunity to make real business improvements.

Face it: whether the software is simple or complex, it's going to be a tough job to implement. You have to recognize that there is more risk associated with complex software, and find a way to minimize the risk without compromising the results.

WHAT'S TO BE DONE?

Here's what it takes to make sure you are successful regardless of whether your software is simple or complex:

1. Understand the simple core logic that makes MRP II work, and insist that this functionality is available in your system. The MRP II Standard System, a book that I coauthored, is the generally accepted industry standard for MRP II software. Get a copy and evaluate the software against it.

2. Pilot everything. Time phase your implementation. This will ensure there's no "cold-turkey" cut-over--the risk of something not working or working poorly is immense.

3.Verify that the implementation plan includes necessary modifications and interfacing. If you already have automated systems, you'll need some temporary bridges and perhaps some permanent interfaces. They all need to be time phased and planned for in the implementation process.

4. Have your best systems and data processing people available for modification and interfacing.

5. Do the proper amount of education on the concepts, principles, and foundations of MRP II. Reduce the learning curve and optimize behavior change by putting more time into education on the use of simple MRP II tools.

6. Don't skimp on training either. Someone in your company must understand the software features well enough to choose which to use and which not to.

7. In implementation, err on the side of simplicity, not complexity. Strike the proper balance between the structure provided by the software and your business processes so that you are truly successful.

_______________________________________________