7 Strategies To Erp Implementation Rates And Minimize Problems

Traditional ERP Implementations

Traditional ERP implementations are extremely risky, for both the partner deploying them as well as the customer. This is why no one offers the elusive fixed fee. The risks are merely a lot of.

The existing Dynamics NAV project costs were high because legacy methods can be very expensive. The normal implementation follows several phases originally put down by Microsoft in the waterfall project framework. Waterfall project management software has been confirmed to be costlier compared to modern "agile" approach, which is determined by LEAN techniques.

The approach which has been employed by virtually everyone since ERP has been in existence is always to bill "Time and Material." Which means customers purchase some time spent by consultants, nomatter just how or bad they are. This moves the chance through the implentor to the customer almost entirely.

In fact you may still find massive risks for the partner with these waterfall projects. I have seen Most all cases where partners were sued or threatened when these projects go very badly.

I started contemplating how we required to change this seeing a LinkedIn post that shared articles on why "Time and Material Billing is Unethical." I used to be really struck from the arguments. The writer asked a question i think summed up fantastically well:

If the restaurant charged you for your some time and material that it loved cook your steak, how do you feel?

This probably sparked my first real thoughts about how to stop as a some time to material business.
ERP Prices are incredibly unpredictable

One of the first videos that we uploaded to YouTube was my explanation of why traditional costing of ERP implementations was outrageously inaccurate. I've spent many years since working out ways to remove that inaccuracy.

Obviously the simplest way to give accurate estimates ended up being to be fixed fee. Unfortunately that traditional approach is really dangerous for that partner. It can make it truly scary to offer a fixed fee. should you not do it properly, you're in a lots of trouble. I've worked tough to develop a technique i think differs from the others.

Applying LEAN Thinking to ERP Implementations

You will find there's movement to make use of LEAN thinking to service activities. In general, LEAN is about removing waste from the physical product, however it can be applied to projects too.

I developed my own variations of waste in ERP projects.

First - there is certainly time spent from the wrong resource.

This can be typically if somebody who is too expensive does something that somebody who pays significantly less are capable of doing, or can do it faster.

Second - you will find unnecessary steps

I have discovered this happens when we perform steps to "cover their butts." A great deal of project management software falls into this. Additionally, it comes about when consultants (compensated on hours billed) push unnecessary work.

Third - you'll find wasted tasks

Sometimes customers need to do things that we, as ERP consultants, know will not work. In a traditional implementation we have no economic motivation to halt it.

Lastly - there is a "bleed" of info

Rise on the customer. Typically it's when the customer doesn't remember their training as they do not spend some time working in it enough.

Why ERP Implementations Have to Change!

Once we started doing cloud based ERP implementations with Microsoft Dynamics NAV it had been common for customers to pay $100,000 for the software and pay $200,000 because of their implementation.

Once you enter in the realm of the cloud, where Microsoft Business Central is $100 per month per user, things change. It's hart to see a client they're going to spend $2000 a month for software yet still pay $200,000 for implementation.

And we all did what our customers do. We set a price we thought the market industry would support, so we worked backwards to regulate our internal costs to make money doing that. Our customers are suppliers. They need to estimate a cost, and then adhere to it. They cannot check out their customer and say "we should bill you more because we had been inefficient within our production process." They might go out of business over night.

The newest procedure for ERP implentations.

I'm much more of a producing expert when compared to a technology expert. Few manufacturing companies think in terms of projects with project managers (Engineer to Order could be the exception). They usually think when it comes to operations managers and standard work instructions.

I applied this thinking to ERP projects. It may help that we do is implement ERP for suppliers.

Here's will be the main steps that helped us dramatically decrease the risk (and costs) of ERP projects.

We just do one sort of projectFocusing exclusively on manufacturing, plus small facilities, resulted in we're able to refine and have better each and every project. We glance at the process being a repetitive, repetable process. This does get rid of the up front form of the project plan etc. The project management goes away, and that we reduce that waste enormously.
We offset easy but tedious try to the customerWhen a $200 per hour consultant does what depends upon a clerical task, that is waste. We train absolutely free themes to accomplish many of the tedious tasks. Apparently , these are also far better produced by the client. Business Central constitutes a large amount of this easier because it has great tools for end users to complete tasks that had been hard. There's 2 of those especially which are key: Reports files Loading
We train customers to edit formsCustomers know very well what they desire their invoice to look like. They are fully aware where they want the payment date on their own PO. It can be way easier whenever we help them learn to change these items than do it for the children.
We train people to load data in the systemData loading is really a task we assign with a co-op student soon after hours training. The truth is, when customers "get" how this is done - they actually do a much better job cleaning their data and things go much smoother!
We keep services shorter and VideoPeople forget what they are taught. It goes without saying of life. There is a lot in your plate. Also, the more a person spends in training - the greater they "zone out" and start to get rid of focus. We keep services short, and record all of them as videos. People absorb increasingly can easily review what they've forgotten. This means we absolutely must train remotely. Travel time can be a killer (and totally waste)- and then we can't travel.
We maintain the project tight, and discourage changeTraditional ERP partners encourage work. Remodeling means extra profit. Not for us. Whenever we do a Business Central project, we discourage any changes in the original project. Our projects aren't super restrictive - nonetheless they do limit the features we are going to implement in "Phase 1." By continuing to keep the master plan tight, it is a lot less "creep" along with the boss is normally much happier.
We still bill for customizations, but discourage them as well Customizations are the another thing we can not predict - and we all also discourage them. Given this new model, we find customers demand a lot fewer also. They trust us more to understand were doing. Occasionally a customization is only a no-brainer, plus those cases we support and in many cases encourage them. Nevertheless - we've fewer than half the customization we used to.


For more details about User friendly Manufacturing software you can check our new web portal: check