User:KuvobaLubuqu

[ERP wiki - the minute of truth has arrived. That's right: the launch. Or rather, it's several days before the launch of one's ERP implementation, along with your company is about the proverbial pins-and-needles because it prepares for the much-anticipated go-live date. Hopefully, if you've followed the prior tips on kickstarting the ERP implementation; managing the transition; and employing a qualified ERP consultant, you're already well-prepared for when your systems are go and you're ready to flip the switch, figuratively speaking. As you count along the days before your organization undergoes what's likely probably the most significant change in its history since it was founded, here are some last-minute what to review prior on the official launch: Are you sure you're actually prepared to go-live? Don't make mistake of skipping this seemingly obvious step, but you would be surprised at how tempting it can be to stick to a go-live date which was determined six months or more in the past but which ended up to be unrealistic. Hopefully after many months of planning, communications, training, and testing, to not mention producing and going through countless checklists, you will probably be in a posture to answer that question with great confidence, but when there's doubt concerning whether or not you together with your staff are ready or that the system itself is ready for its close-up, there's nothing wrong with moving that go as far back just to produce sure. Training - Providing quality training for your customers is vital to the success of your launch. Before introducing any training program for your new users, you need to invest some time in one-on-one sessions training department supervisors and team leads. They'll be capable to provide you with final feedback before engaging the masses. In the event you can, you need to always encourage department heads to participate as bystanders and supporters through the training process so that they are able to help explain the way the processes employees are actually employed to for so many years is planning to be interpreted in their new ERP system. Having said that, remember that the post-launch period will also have several hiccups, regardless of how flawless your pre-launch preparation was. You may find that, despite scrupulous scrubbing, the information migration isn't complete or still contains errors. You and your employees will inevitably forget how seamlessly integrated your product is now, so when someone makes a mistake during the processing of the customer order, the consequences ripples over the system far more quickly. Regardless of how you plan for success, understand that part of that plan must include contingencies for errors and unforeseen events. Be relentless inside your communications. Perhaps at no other stage inside entire pre-launch period is communications among all stakeholders most important. Ensure that most staff members are periodically briefed around the go-live date, things to expect, who they can turn to should they have any questions, and how you can contact the help desk or support team. Ensure that all staff members have help manuals at their fingertips, whether in print format, CD, corporate intranet, or even wiki, knowning that they understand how you can utilize it to discover the information they need. Make a list, and look it twice. Or more. ERP implementation checklists are ubiquitous to every system, and they're especially critical inside weeks leading up for the go-live date. Ideally, the checklist will are already created months before it's ever needed, as it'll undoubtedly have a huge selection of details that should be reviewed ahead of the launch date. Reports and Forms - Regardless of the wonderful benefits users get each year once they commence to grow in your systems, it's absolutely essential that the reports and forms they have been according to for many years will likely be available with your new software. This will probably be a testimony to your "listening skills" during early implementation. The way by which your software conducts business and achieves results is bound to get greatly not the same as how your previous system worked, but your employees' reports and forms is gonna be the first opportunity to win them within the go-live process and reduce some of the apprehension about missing familiar tools. Security. Assess the entire system's security configuration and administration thoroughly, in the security in the data and connections themselves to the data which is available to every one individual user. Make sure that users are able to review and/or edit everything they desire in order to perform their jobs, but that any access to sensitive details are limited to authorized employees only. Once the go-live date may be reached, of course, one other half from the implementation begins: the post-launch date review, which may include additional training, system changes, and the like. In my next post, I'll look at some from the key points to consider as soon as the go-live date and beyond.