|
|
|
|
|
|
|
| Topics >> by >> several_ways_to_erp_implem |
| several_ways_to_erp_implem Photos Topic maintained by (see all topics) |
||
|
Traditional ERP implementations are extremely high-risk, for the partner deploying them and for the customer. This is the reason almost nobody provides elusive fixed fee. The potential risks are merely a lot of. The old Dynamics NAV project costs were high because legacy methods can be very expensive. The normal implementation follows several phases originally set out by Microsoft in a waterfall project framework. Waterfall project management has been proven to be higher priced compared to modern "agile" approach, which can be depending on LEAN techniques. The approach which has been used by virtually everyone since ERP has been online is to bill "Time and Material." Because of this customers buy time spent by consultants, nomatter how good or bad these are. This moves the risk in the implentor to the customer almost entirely. In fact you may still find massive risks for your partner with your waterfall projects. I've seen Most all cases where partners were sued or threatened when these projects go very badly. I started contemplating the way we had to change this reading a LinkedIn post that shared an article on why "Time and Material Billing is Unethical." I had been really struck through the arguments. The writer asked an issue that we think summed it down fantastically well: If a restaurant charged you for the some time and material it took to cook your steak, would you feel? This probably sparked my first real opinion of the way to stop as being a serious amounts of material business. ERP Costs are incredibly unpredictable One of the primary videos that I uploaded to YouTube was my explanation of why traditional costing of ERP implementations was outrageously inaccurate. I've spent recent years since figuring out ways to remove that inaccuracy. Obviously the simplest way to give accurate estimates ended up being to be fixed fee. The trouble is that traditional approach is indeed high risk for your partner. Commemorate it genuinely scary use a fixed fee. unless you do it right, you are in a lot of trouble. I've worked very hard to develop an approach that I think differs from the others. Applying LEAN Thinking to ERP Implementations There is a movement to use LEAN thinking to service activities. Generally, LEAN is approximately removing waste from your physical product, however it can be applied to projects too. I developed my own variations of waste in ERP projects. First - there exists time spent with the wrong resource. This really is typically if somebody who is too expensive does something which somebody that will be paid much less are able to do, or can do it faster. Second - you can find unnecessary steps I have found such a thing happens when people perform steps to "cover their butts." A lot of project management falls into this. It also comes about when consultants (compensated on hours billed) push unnecessary work. Third - you can find wasted tasks Sometimes customers want to do stuff that we, as ERP consultants, know won't work. Within a traditional implementation we have no economic motivation to stop it. Lastly - there's a "bleed" of info It's usually for the customer. Typically it's if the customer doesn't remember their training because they don't spend time employed in the machine enough. Why ERP Implementations Have to Change! If we started doing cloud based ERP implementations with Microsoft Dynamics NAV it absolutely was common for patrons to spend $100,000 for your software and pay $200,000 because of their implementation. After you enter the arena of the cloud, where Microsoft Business Central is $100 per month per user, things change. It's hart to tell an individual they will spend $2000 monthly for software yet still pay $200,000 for implementation. And then we did what our customers do. We set a price we thought the marketplace would support, and that we worked backwards to regulate our internal costs and make money doing that. Our company is manufacturers. They should estimate an amount, and after that stick to it. They can't visit their customer and say "we need to bill you more because i was inefficient within our production process." They would go out of business over night. The new procedure for ERP implentations. I'm a greater portion of a producing expert than the usual technology expert. Few companies think regarding projects with project managers (Engineer to get may 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 every we all do is implement ERP for manufacturers. Here's are the main steps that helped us dramatically lessen the risk (and charges) of ERP projects. We simply do one kind of projectFocusing exclusively on manufacturing, as well as in small facilities, meant that we might refine and acquire better with each and every project. We look at the process as a repetitive, repetable process. This process gets rid of the at the start design of the work plan etc. The job management goes away, and that we reduce that waste enormously. We offset easy but tedious attempt to the customerWhen a $200 per hour consultant does what comes from a clerical task, that's waste. We train absolutely free themes to do some of the tedious tasks. It turns out that kinds much better produced by the client. Business Central constitutes a large amount of this easier because it has great tools for users to complete tasks that was previously hard. There's two of the in particular which might be key: Reports and knowledge Loading We train people to edit formsCustomers understand what they need their invoice to take a look like. They do know where they want the payment date on their PO. It's way easier whenever we help them learn to improve these items compared to it for the children. We train people to load data into the systemData loading can be a task we assign with a co-op student soon after hours training. Truth be told, when customers "get" how this is accomplished - they are doing a far better job cleaning their data and things go much smoother! We keep exercise sessions shorter and VideoPeople forget what they're taught. It's a fact of life. You have a lot on the plate. Also, the more time someone spends in training - the greater they "zone out" and start to shed focus. We keep training sessions short, and record every one of them as videos. People absorb more and can easily review what they've forgotten. This implies we absolutely must train remotely. Travel time is often a killer (and totally waste)- therefore we can't travel. We maintain the project tight, and discourage changeTraditional ERP partners encourage remodeling. Work means extra profit. Not for us. When we execute a Business Central project, we discourage any changes from your original project. Our projects aren't super restrictive - however they do limit the features we will implement in "Phase 1." By maintaining the plan tight, there's a lot less "creep" along with the boss is normally much happier. We still bill for customizations, but discourage them Customizations include the a very important factor we can't predict - and we all also discourage them. With all this new model, we discover customers require a lot fewer also. They trust us more to be aware what were doing. Occasionally a customization is simply no-brainer, and in those cases we support as well as encourage them. Having said that - we've fewer than half the customization we accustomed to. More info about Best cloud ERP go our resource: click here |
||
|
||
