Posted by Redfaire International
How to rollout your core model in a way that works with your business requirements.
In our article 4 Steps to Build your JD Edwards Global ERP System, we explained how to create your Core Model and the steps to follow to implement this across your organization. Now we will discuss how to rollout your core model and how this adapts in reality to your business requirement.
When we are about to roll out our core model, we need to define what is ‘rollable’. Processes, organizational structure, master data, configuration, platform, custom processes, integration, and global templates, are key elements that can be rolled to other sites.
We also have areas that can’t be rolled to different territories. Regulatory localizations, local integrations and local processes are specifically created to comply with government regulations across countries and regions where an organization has plants and business units.
When you look at the rollout, you will have a site that could have all the aspects you have previously defined. This is a site that has a global common core model and a group of processes. As you move forward with your rollouts, you may find that in some sites the percentage of business processes used, differs from the pilot site core model.
It is looking at it all to define what are your global elements, group elements, and what are you localizations along the way.
The core model has some specific inputs. In this project preparation phase, you will have your standardized processes, have defined what is global, group and local, and also identified your applications gaps. For example, if part of your business is not supported by standard ERP functionality.
Once you have created and validated your Rollout kit, methodology and plan, you move to validate your common architecture. All these elements are part of your rollout Project Output.
Let's take a look at the Pros and Cons of these different scenarios.
Doing it yourself
+ Lower cost (this is a perception)
- Availability of knowledge and resources
- Extend business downtime
Shared responsibility
- Clear governance required – who is responsible for what?
+ Complementing business expertise (users) with ERP knowledge (consultants)
+ Decrease business downtime
Full outsourcing
- High dependence on partner, low control
+ Low business disruption
To find the right partner, you must have a clear idea of what you expect from that partner. Drawing up a long list that takes key points into account is a great way to answer questions and can provide the criteria to assess potential partners.
On the very top level there is the steering committee. It is important that you include your C-level team in the project. This helps makes sure that people really understand the reason for the project.
Next is the core team, this consist of business analysts from your company. They typically guard the project and make sure that deviations occur at a minimum.
On the next level, you will find your rollout team in the local site, where usually the number of resources from a partner increases. Normally companies hire partners with local knowledge and understanding of language and culture for the local rollouts.On the third level, you have the support team who provide 1st and 2nd line life support throughout the project. This team makes sure that the sites which are already live keep functioning while you roll out to other sites.
The scale and challenges of a global ERP implementation should never be underestimated. Our team has a business background and understands the challenges of implementing an ERP system on an organization on a global scale.
Redfaire International can help you plan your international rollout strategy and ensure excellent execution of your global ERP strategy at a local level.
Get in touch for more information.
Please complete the form and our Global Enquiries team will be in touch to help you.
UK: +44 118 9653 904
IRL: + 353 61 512 840