ERP Implementation Procurement Plan
This is a practical guide to building a procurement plan for an erp implementation project — what will be bought, how and from whom, adapted to the realities of replacing or deploying an enterprise resource planning system across the whole organisation.
What a Procurement Plan is
A procurement plan is what will be bought, how and from whom. For the full concept and how it works in general, see Procurement Management. On an erp implementation project it plays the same role, tuned to this kind of work.
Why it matters for an ERP Implementation project
ERP Implementation projects live or die on replacing or deploying an enterprise resource planning system across the whole organisation. A well-built procurement plan gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how erp implementation projects drift into avoidable delay and cost.
What to include
- What to procure
- Contract types
- Selection criteria
- Timeline and SLAs
ERP Implementation-specific considerations
Tailor the procurement plan to the risks that most often derail erp implementation projects:
- Under-estimated data migration
- Business-process change resistance
- Customisation over-reach
Example
On a real erp implementation project, the procurement plan would be shaped by replacing or deploying an enterprise resource planning system across the whole organisation. In particular, it should explicitly account for the project’s biggest risks — under-estimated data migration, business-process change resistance, customisation over-reach — rather than treating them as afterthoughts.