What is an ERP Health Committee and Why Should I Have One?

Mark Feldhamer President LogicData Headshot | April 19th, 2021

ERP systems are an amazing advance in technology and can definitely solve a number of problems for any manufacturer. Putting everything on one database makes so many things easier, more visible or in some cases possible, where it wasn’t possible before.

So, how is it that after a few years, the system sometimes doesn’t work as well as it did when it was first implemented?

How do spreadsheets and point solutions creep back in?

How does an ERP system that once worked pretty well become cumbersome and unwieldy?

How do we get to a point where a manager who once loved their ERP system, now treats it with adversarial disdain?

Is it the fault of the ERP System? Actually, it isn’t.

The answer lies with a tool needed to keep your system running well – an ERP Health Committee.

Let me explain. Maintaining an ERP system is a lot like maintaining a car. There are regular activities that should be done to ensure the ongoing health of the system. Any system left unattended will degrade over time and finally break down completely. Just like a car that doesn’t get an oil change for 4 years will break down (usually on a highway in the middle of traffic), so will an ERP system that doesn’t get regular maintenance break down just when you need it the most.

This is where your ERP Health Committee comes in.

At LogicData, we recommend you assemble the original implementation team and appoint them as your ERP Health Committee, with regularly scheduled meetings in which the team reviews the key functions of CSI/SyteLine, such as:

 Is our ERP process documentation published and available?

  • Have our users been trained on our ERP processes?
  • Are our users applying what they have been trained on?
  • Do our process documents need revision due to changes in how the company operates (e.g. new products, acquisitions, new regulations, new customer requirements, etc.)?
  • Are any users deploying outside systems to do their jobs, such as spreadsheets or Access databases, that should be part of the ERP system?
  • What problems are our users reporting? Are these due to failure to follow existing procedures, or do they indicate a need to revisit the procedures and improve upon them?

Engaging the lead consultant that helped with your original implementation and having him or her attend these committee meetings as well, will go a long way in ensuring that the committee will be effective. The consultant’s knowledge of CSI/SyteLine and your business can significantly assist in spotting gaps and resolving issues. As our passion is making your ERP System work for you, we would be happy to have our consultants continue their relationship with you and your Health Committee.

The investment spent in purchasing and implementing your ERP system shouldn’t be allowed to go to waste due to lack of system maintenance. Having your team spend a few hours a month to ensure the ongoing effectiveness of CSI/SyteLine is time well spent. Some of our most successful customers even hold this meeting weekly.

Those enterprises who do have an ERP Health Committee find that their satisfaction with their system remains high and they continue to get great ongoing ROI.

Contact us today for help in creating and implementing your ERP Health Committee.

Leave a Reply

Your email address will not be published. Required fields are marked *

As with cost, implementation time is also dependent on the same factors mentioned above. LogicData offers multiple implementation methodologies that can be adapted to your specific needs and resource availability. Considering a very basic implementation of just the core functionality of SyteLine, and employing a LogicData managed implementation approach, time to value can be achieved in as little as 3-4 months. A full implementation of all core SyteLine functionality utilizing a standard implementation approach, and assuming full client resource availability, can generally be completed in 6 to 8 months. To determine the best implementation methodology and timeline estimate for your specific situation, please contact us.

The cost of software and implementation will vary based on many factors such as user count, functionality requirements, deployment, implementation methodology, customization, data conversion, integration, and internal resources. However, for a basic configuration of SyteLine annual subscription pricing can begin at approximately $18,000 annually for a minimum of 10 users or a one-time cost of $20,000 plus annual maintenance for a minimum of 5 users in an on-premise deployment. A primarily self-directed implementation of such a basic configuration, although not recommended, can likely be achieved for approximately $30,000. LogicData recommends our standard “train-the-trainer” implementation approach which is estimated to start at roughly $65,000 for a basic implementation. For further information on pricing specific to your needs, please contact us.