photo sharing and upload picture albums photo forums search pictures popular photos photography help login
Topics >> by >> several_solutions_to_erp_i

several_solutions_to_erp_i Photos
Topic maintained by (see all topics)




Traditional ERP Implementations




Traditional ERP implementations are extremely high-risk, for the partner deploying them and also for the customer. This is the reason almost nobody supplies the elusive fixed fee. The potential for loss are merely an excessive amount of.

That old Dynamics NAV project costs were high because legacy methods can be very expensive. The typical implementation follows numerous phases originally determined by Microsoft within a waterfall project framework. Waterfall project management has been shown to become more costly compared to the modern "agile" approach, which is depending on LEAN techniques.

The approach that is employed by virtually everyone since ERP has been online is always to bill "Time and Material." Which means that customers buy time spent by consultants, nomatter just how or bad they're. This moves the danger through the implentor for the customer almost entirely.

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

I began thinking about the way we required to change this after reading a LinkedIn post that shared a write-up on why "Time and Material Billing is Unethical." I had been really struck by the arguments. The writer asked a matter i think summed it fantastically well:

In case a restaurant charged you to the time and material it latched onto cook your steak, how does one feel?

This probably sparked my first real thoughts about how you can~the way to~tips on how to~the best way to~ways to stop as being a serious amounts of material business.
ERP Costs are incredibly unpredictable

Among the first videos which i uploaded to YouTube was my explanation of why traditional costing of ERP implementations was outrageously inaccurate. I've spent recent years since working out solutions to remove that inaccuracy.

Obviously the simplest way to give accurate estimates was to be fixed fee. Unfortunately that traditional approach is really risky for your partner. Celebrate it scary to supply a fixed fee. should you not do it right, you have a lot of trouble. I have worked tough to develop an approach i think is unique.

Applying LEAN Thinking to ERP Implementations

You will find there's movement to make use of LEAN thinking to service activities. Normally, LEAN is approximately removing waste coming from a physical product, however it is true to projects too.

I came up with my very own variations of waste in ERP projects.

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

This is typically if somebody who costs too much does something that someone who will be paid much less can perform, or are able to do it faster.

Second - you'll find unnecessary steps

I find this happens when individuals perform steps to "cover their butts." Lots of project management software falls into this. In addition, it happens when consultants (compensated on hours billed) push unnecessary work.

Third - you can find wasted tasks

Sometimes customers wish to accomplish items that we, as ERP consultants, know won't work. Inside a traditional implementation we have no economic motivation to halt it.

Lastly - there is a "bleed" of knowledge

It's usually about the customer. Typically it's if the customer doesn't remember their training they do not spending some time in the machine enough.

Why ERP Implementations Need to Change!

Once we started doing cloud based ERP implementations with Microsoft Dynamics NAV it turned out common for purchasers to spend $100,000 for that software and pay $200,000 for his or her implementation.

When you type in the realm of the cloud, where Microsoft Business Central is $100 per month per user, things change. It's hart to tell a client they will spend $2000 monthly for software but still pay $200,000 for implementation.

So we did what our customers do. We set an expense we thought the market would support, and that we worked backwards to regulate our internal costs and make money doing that. Our customers are suppliers. They need to estimate an amount, and then stick to it. They cannot go to their customer and say "we have to bill you more because we had arrived inefficient within our production process." They would close shop over night.

The new way of ERP implentations.

I'm much more of a producing expert compared to a technology expert. Few manufacturers think regarding projects with project managers (Engineer to get may be the exception). They generally think with regards to operations managers and standard work instructions.

I applied this thinking to ERP projects. It may help that every carry out is implement ERP for suppliers.

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

We merely do one sort of projectFocusing exclusively on manufacturing, and in small facilities, meant we might refine and have better with each project. We glance on the process as a repetitive, repetable process. This kind of gets rid of the in advance kind of the job plan etc. The project management disappears altogether, and now we reduce that waste enormously.
We offset easy but tedious work to the customerWhen a $200 hourly consultant does what comes from a clerical task, that's waste. We train the customers to complete some of the tedious tasks. Apparently , kinds superior made by the buyer. Business Central is really a lot of this easier given it has great tools for end users to do tasks that was once hard. There are 2 of the particularly which might be key: Reports files Loading
We train people to edit formsCustomers determine what they really want their invoice to check like. They understand where they desire the deadline on their PO. It's way easier if we help them learn to change this stuff compared to it on their behalf.
We train customers to load data to the systemData loading is a task we assign into a co-op student soon after hours training. The reality is, when customers "get" how this can be done - they are doing a far better job cleaning their data and things go much smoother!
We keep workout sessions shorter and VideoPeople forget what they are taught. It's a fact of life. You have a lot on your plate. Also, the more time a person spends in training - the more they "zone out" and commence to reduce focus. We keep services short, and record them all as videos. People absorb many can readily review what they've got forgotten. This means we absolutely must train remotely. Travel time can be a killer (and totally waste)- therefore we can't travel.
We maintain your project tight, and discourage changeTraditional ERP partners encourage remodeling. Extra work means extra profit. Not for individuals. Whenever we perform Business Central project, we discourage any changes from your original project. Our projects aren't super restrictive - nevertheless they do limit the features we will implement in "Phase 1." By keeping the master plan tight, it is a lot less "creep" and the boss is usually much happier.
We still bill for customizations, but discourage them as well Customizations include the a very important factor we can not predict - therefore we also discourage them. Considering this new model, look for customers demand a lot fewer also. They trust us more to be aware what we have been doing. Occasionally a customization is simply no-brainer, as well as in those cases we support and even encourage them. Having said that - we've fewer than half the customization we used to.


To learn more about Best cloud ERP browse the best webpage




has not yet selected any galleries for this topic.