#mikeonmonday #smartERP #ahead

#mikeonmonday #smartERP #strength

#mikeonmonday #smartERP #strategy

#mikeonmonday #smartERP #action

#mikeonmonday #smartERP #Truth

#mikeonmonday #smartERP #proof

#mikeonmonday #smartERP #plan

#mikeonmonday #smartERP #Focus

#mikeonmonday #smartERP #shortcuts

#mikeonmonday #smartERP #dialogue

#mikeonmonday #smartERP #important

Before implementing an ERP system in an organisation or project, it is crucial that the implementation process be planned. Implementation planning includes developing the implementation strategy and implementation schedule and organising the implementation team.

The plan documents the who, what, why, where, when, and how of the project. It is the outcome of discussions with ALL affected, involving negotiations over resources, timescales and costs. Timescales need great care – against disruption or momentum being lost!.

The statement of needs by a user that triggers the development of a system – a user need or necessary feature, function, or attribute of a system that can be sensed from outside the system. Requirements are specifications of what should be implemented.

One approach is to walk through all processes, identifying who does what, what materials are used and generated, and who provides and receives them. These materials may be reports, suppliers’ and customers’ documents, internal documents, plans, computer screens, etc.

Everybody should have a needs analysis which will essentially be the justification for the project. Key elements should be a report of why the ERP system is needed, which functional areas need maximum focus, and what are the areas that need to be improved.

A first step of ERP planning is to assemble the critical stakeholders of the project. This should include ALL people who have a direct influence over the project in terms of how the resources should be allocated, including anybody with an influence on the ERP core team.

#mikeonmonday #smartERP #attitude

ERP systems vary enormously in strengths and weakness. A pre-evaluation process should eliminate those packages that are not suitable for the company’s business processes. One can zero in on the few best packages by looking at the product culture of the vendors.

Like any project, an ERP implementation has to go through different phases. There are no clear demarcating lines between phases although they may seem linear and distinct from each other. In reality, phases are quite fluid throughout an actual implementation.