This issue is particularly symptomatic of companies that are implementing ERP for the first time and transferring their legacy data into the new system from Excel spreadsheets, manual records, or old disparate applications. Basically, the issue is that old data that have been used and stored for years can for many reasons appear approximate or even incorrect in the new job card software reality. In fact, according to our research, replacing a legacy system and consolidating disparate solutions are the top two common challenges companies face.
For example, take this situation from my previous work experience (during an ngo accounting software implementation project for a midsize metal manufacturer): in the middle of the project, we converted existing bills of materials (BOMs), BOM routings, and hour tariffs into the new system and realized that the products’ new lead times exceeded real ones by a factor of two or more.
Thanks to adequate time allotted for the conversion phase during project planning, we had some time to fix the data by dedicating engineers and analysts to this task full-time for a few months and modifying the implementation plan accordingly; but even in this case, the project was delayed for two months. So, be careful with your old information, as it can be far from reflecting the current reality, and always make “pilot” tests of new system outputs using legacy data before converting or transferring all the data over to the new system.
Business Philosophy Changes
ERP implementation brings significant changes to a company’s conventional business model and the day-to-day practices it has been using for years or even decades. Take these examples of likely changes to business processes with a new cold storage software solution:
- some employees’ level of responsibility is dramatically increased, as with the new system it is more difficult (sometimes impossible) to fix erroneous data or typing errors;
- new approaches to data reporting and mining and, thus, new managerial principles and practices have to be established; and
- business models and business processes might require massive changes because of new real-time opportunities and data availability.
These are only a few examples of how serious and meaningful business transformation can be, post-implementation.
Using wise and forward-looking ideas and conceptions when implementing ngo accounting software, it is definitely possible to get a return that is something much more appreciable than a simple change in format of data or an updated user interface. This is a real challenge, but at the same time it is a great opportunity to refresh the business and bring new ideas as well as laying a strategic foundation for your organization’s future.
“Mindshift” Issues
This is the most difficult type of issue to resolve. It’s easy to forget that the success of the implementation of a field service management software system depends mainly upon the users. The system itself is a non-living and logical entity that follows logical steps and processes as it has been programmed to, but the users of the system are humans who were used to processes with software being one way and will more than likely find it hard to switch to a new way of doing things, especially if the benefit of the new methods is not immediately obvious or forthcoming.
This is an ERP Software project manager‘s “favorite” variety of problem (meaning their worst nightmare), arising from users’ habits and their understanding of what is good for the business in general and for the user in particular. “It’s always been like this, long before you came in,” “I don’t think it will ever work,” “It’s not working on my PC,” “I will be talking with the CEO about this system,” or “You don’t understand how it should work”—these comments should sound familiar to anyone who’s ever tried to implement a new system or change users’ requirements.
It is really difficult to describe or classify the possible problems that can arise among the user base when a new enterprise CRM software system is implemented; actually, almost any question can appear. Unfortunately, change is hard to accept without seeing the visible advantages of it, and if you don’t take steps to help your employees see these advantages before the implementation begins you will likely regret it later. I would recommend trying to predict such problems at the planning stage in order to reduce the potential negative impact of users’ contra-collaboration activities.
Also, gaining the interest of different groups and categories of system users well ahead of the project’s start date and keeping them involved during the implementation will help to encourage the “mindshift” required in your employees for a successful implementation. Consider following these steps to keep employees informed and engaged before, during, and after a big manufacturing software implementation project:
- inform all employees of news and project milestones as the project progresses
- establish reliable feedback communication channels for employees
- stimulate employees to generate new ideas and provide suggestions
- organize interesting and promising training sessions
- celebrate the best user achievements in training and with the new software system
Affected employees at all levels must become allies to the free job card management software project team for a new system implementation, as ignoring users’ experience and concerns puts in doubt the success of the entire project and can kill any excellent undertakings.
Planning for Implementation Success… It’s Not Easy, But It’s Worth It
Like almost any enterprise-wise undertaking, implementing software requires a lot of planning, effort, and monitoring to ensure success and minimize problems. Addressing the five challenges above can help with the planning stages and make sure all potential issues are addressed before the implementation gets underway. Addressing challenges head-on and making sure you’ve done your due diligence means that you’ll be able to feel confident in your organizational implementation and keep the costs and time down as much as possible.
+ There are no comments
Add yours