How to Determine a Phasing Approach for Your ERP System


In choosing an ERP implementation phasing strategy, organizations should carefully weigh their options. The ideal phasing strategy depends on a number of factors and each organization may choose a different approach.

How quickly will employees adapt the new ERP system? How much risk are we comfortable with? How much money are we willing to spend? These are just a few questions organizations should ponder before deciding on a phasing strategy.

Following are three common implementation phasing strategies and the advantages and disadvantages of each:
Big Bang Approach – This strategy means all modules are installed across the entire organization at the same time and all users concurrently move to the new ERP system. Once the new system is launched, the old system is completely turned off. Because of this finality, the big bang approach can be quite risky and organizations should develop contingency plans to account for the possibility of the new system crashing. Despite these risks, the big bang approach can work well for organizations that are looking for a faster and lower cost implementation.

Phased Rollout – This strategy means that users move to the new ERP system in a predetermined series of steps. Software can be rolled out by module, by business unit or by geography. The advantage of a phased rollout is that employees have more time to learn and adapt to the new system. Unfortunately, this approach takes longer than the big bang approach and several adjustments may need to be made along the way to keep the two systems temporarily bridged. Bridging the two systems is essential because the first modules to be implemented may not function optimally without critical information from modules yet to be implemented.

Parallel Adoption – This strategy means the old and new system are running at the same time during the majority of implementation. Employees can learn the new ERP system while still using the old system to perform daily tasks. This strategy is the least risky of the three because the old system is easily accessible in case the new system causes major problems. Parallel adoption is more expensive, however, and is somewhat inefficient since data is being entered twice – once in the old system and once in the new system. Nonetheless, many companies choose parallel adoption after weighing the costs of a backfired big bang adoption.

Implementation is one of the most difficult and crucial aspects of an ERP project so there should never be a rush to get it over with. Be sure to choose your implementation strategy carefully and ensure that effective organizational change management and business process management guide your implementation every step of the way.

Comments

Post a Comment

Popular posts from this blog

Determine the Business Value of ERP

Image
Return on Investment (ROI) is one of the most important considerations for the company management. After all, any investment must yield some value to be worthwhile. But what about the ROI of an Enterprise Resource Planning (ERP) system? Understandably, management may be hesitant to invest in a costly software solution like ERP. Like any new technology, ERP systems  take time to implement  and require all workers  to be adequately trained . Is the value of ERP really worth the cost? Answering this question comes down to understanding two things: what kinds of value ERP brings to your company and how to attach a dollar amount to them. In this post, we’ll cover both. Adding Value to Organization Before understanding the value of an ERP solution that brings to the organization, first there is a need to understand where the existing challenges and pain points persist. When weighing the potential areas where ERP will bring value to the business,  one ...
Read more

Customization in ERP Software Implementation

Image
Customization is one of the most controversial topics surrounding ERP software.  A majority of companies have every intention of leveraging vanilla, off-the-shelf software during their software selection process.  However, as project teams get into the details of the software during the implementation cycle, requests to make one or more customizations to the software are inevitable. The reason for the controversy around customization is threefold. First, it increases the complexity and risk of an implementation, while at the same time making it potentially more difficult to upgrade software in the future.  Second, it in some ways undermines the best practices built into the software, which software vendors often spend significant R&D developing.  Thirdly and finally, customization is often a symptom of bigger problems, including a solution’s mismatch with a company’s requirements or a lack of project controls during implementation. So what to do?  ...
Read more

Best Practices to Manage End-to-End Business Processes in Your ERP System

Image
It’s no secret that most ERP systems fail to deliver the business benefits anticipated by the organizations implementing the software. 50-percent of organizations fail to receive at least 50-percent of the expected business benefits from their investments in enterprise software. Adding insult to injury, and as outlined in our blog last week, is the fact that most organizations experience a misalignment between their business operations and ERP systems, which typically worsens over time as the companies go through acquisitions, international expansion, supply chain reorganizations, and other changes. The reasons for the failures to achieve business benefits as well as operational misalignments with ERP software often point to business processes. As opposed to incorporating process best practices in their ERP systems, most ERP vendors and system integrators use the flawed practice of designing and configuring the software to handle a hodgepodge of transact...
Read more