On-demand ERP and On-Site ERP are essentially similar services with a few fundamental differences. Before one can get into their implementation, understanding them would be ideal. On-demand ERP is much like a Google document. You will need a user login and password to get your own document and then you are good to go. You will be able to make use of the entire Microsoft package. On-site ERP is like having Microsoft Office on your computer. One will need an installation disk as well as dedicated storage space to deploy it.
In the case of on-demand ERP, the company requiring it will need to buy a subscription. In terms of the way the two functions, both on-demand ERP and on-site ERP are virtually the same.
Choosing one as an option is a result of a number of other factors that may influence the company. It will also depend on the scope of the project and what kind of a solution is needed. Irrespective of whether you are looking at on-site ERP or on-demand ERP, appropriate planning and execution are very essential for flawless implementation. Here are a few points you can tick off as the team gets set for a project.
- Scope Management – In order for team members to perform optimally, the scope of the project is to be defined clearly so that clear goals and objectives can be provided. The scope of the project (list of tasks that needs to be accomplished) and scope of the product (detailed features & functionalities of the ERP package) are to be decided by the senior management in discussion with the ERP implementation team. Experts can be involved in the discussions as required.
- Process ownership – The core team will need to take complete responsibility and ownership of their respective functional areas. Ownership facilitates clear communication between teams, coordination with subject matter experts and consultants and arriving at insights about functionalities that have maximum impact on different processes / departments.
- Internal and external communication –Roles and responsibilities of the project team should be communicated clearly by the project manager. In addition, it is essential, that a brief note about the project must be given to all the employees, stakeholders and customers.
- Requirement analysis – A complete analysis of the business is to be done to ensure all critical requirements are taken into account. Including key members from every department will help list down all critical requirements.
- Risk management – ERP implementation, as like other projects, involves risk factors. It is the responsibility of the project team to foresee potential risk factors and take appropriate preventive measures. A contingency plan will prove to be effective so that unexpected outcomes can be met.
- Impact analysis and training – The team must discuss the way in which business processes will change with the new application. Work flow might be affected with redundant tasks being eliminated and hence certain departments might have to be dissolved. It is the job of the project team to analyze this beforehand and intimate the management so that expectations are realistic. Accordingly, training should be imparted to all the teams so that all employees are aware of the new processes.
There can be multiple ways to approach each of the above mentioned aspects. It is up to the project team to decide the best way to proceed with the project in accordance with the business environment.
Image Source :: www.globemps.com