6. Separate Testing and MRP Implementation
You want to know how your new system works before you go all in, right?
That’s why it’s useful to start with a testing period where you can play around and iron out the details. You could start with one product to keep the process simple. Probably best to go with your key product if you have one, and that can serve as the centerpiece to work around.
After you’ve tested that, and the ironing has been done you can move on to implement your system to its full capacity. If you’ve already run your tests properly, then you shouldn’t be overwhelmed by any unexpected jabs.
But even then, you want to constantly be reviewing your processes to make sure that you’re getting the most out of it. Especially in the first couple of months.
7. Get Everyone in the Loop
It becomes a lot easier to make sure your MRP implementation goes to plan if you have your team to support you. Doing this alone just means you’re going to have to go back on yourself later down the line. Better to get it right on the first run, right?
MRP implementation can be a lengthy process. Depending on the complexity of your business, it could be a matter of weeks, but more realistically it’s a matter of months.
But that’s why everyone who’s going to be using it must be kept up to date with the potential changes and training required ahead of time. This is a significant incoming change and should be treated as such.
It’s going to make the transition a lot smoother if the team is less resistant and more receptive to the change.
Give regular updates as to what stage you’re at, but even more importantly, use the opportunity for feedback. Especially from those who will be using it most frequently - like the production planner.
Your team can give insight into the nuances and details you might miss.
Remember: Team effort required.
8. Be Prepared for Change
Your processes might have to be slightly adjusted when executing MRP software.
Each system works differently, so your workflow could be affected by features like reorder point and perpetual inventory.
Take this as a positive step and run with it. Otherwise, you’ll be fighting against the system you’re trying to implement.
That’s only going to slow things down.
It’s much better to understand the benefits and spread the love to your team.