How to Write an Effective ERP RFP for a Mid-Sized Australian Plant
An ERP selection can absorb cash, management attention and production capacity for months. For a mid-sized plant, the request for proposal (RFP) should do more than list modules: it should translate operating priorities into evidence vendors must supply. A strong document shows what must work on the shop floor, what the business needs to improve, and how every response will be judged.
Too many requests become catalogue exercises, where the lowest initial price attracts attention while integration gaps surface after contract signature. A mid-sized manufacturer needs a document that gives experienced vendors enough detail to respond honestly and protects the buying team from vague claims. It should also preserve options, since plant scale, product mix and existing systems rarely match one vendor’s standard configuration.
Preparing the business case and scope
Start with the operating problem, not the software. Name the sponsor, decision date, budget range and measurable outcomes such as shorter order-to-cash cycles, fewer stocktake variances, improved schedule adherence or lower unplanned downtime. Document the current baseline and the case for change. If the business cannot explain why automation is worth the disruption, a feature-heavy RFP will not solve that weakness.
Define the boundary before asking about features. State which legal entities, sites, warehouses, product lines and processes are in scope, and whether manufacturing, distribution, field service and group finance must share one instance. Include interfaces to the current general ledger, payroll system, CAD or product data, and shop-floor equipment. For an Australian operation, identify differences between a metropolitan plant and a regional operation, such as staffing, freight access, technician travel and reliance on fly-in-fly-out support.
Writing testable system requirements
Prioritise requirements by writing “must”, “should” and “optional” against testable outcomes. A typical mid-sized plant may need robust manufacturing execution, yet robustness has no meaning until the process is defined. State whether each requirement applies to standard work orders, batch or serial-controlled stock, BOM and routing changes, job costing, purchasing, MRP, quality, maintenance, sales, distribution and service. Name the reports and decisions each function must make, including who receives them and when.
Describe the environment as precisely as the functionality. Cover user roles, devices, glove-friendly shop-floor screens, barcode or RFID handling, audit trails, cybersecurity, backup, restore and response times. Include Australian operating requirements where relevant: payroll interfaces aligned with the Fair Work National Employment Standards and applicable awards such as the Manufacturing Award 2020, GST and BAS treatment in finance, and energy and emissions reporting for facilities subject to the Safeguard Mechanism or customer-driven climate targets.
Designing a credible vendor response
Give every vendor the same response template and timetable. Require an executive summary, a requirement-by-requirement compliance matrix, an implementation approach, named roles and responsibilities, product roadmap, data-migration method, training plan, assumptions, exclusions and total pricing. Ask suppliers to identify partner companies, subcontractors and support locations. This exposes delivery dependencies that polished product demonstrations can conceal.
Build the evaluation method into the RFP. Use mandatory pass-or-fail gates for non-negotiable capabilities, then weighted criteria for usability, implementation quality, support, cost and strategic fit. Give shortlisted vendors the same plant scenario to demonstrate: a rush order, a BOM revision, a stocktake discrepancy and a month-end close. Request an Australian reference, permission for a site visit and a limited proof of concept using representative data. In Australian business settings, concise, direct answers are more credible than sales language or unsupported claims of “best practice”.
Comparing commercial and delivery risk
Compare the whole investment, not the licence. Require a five-to-seven-year view of software, implementation, configuration, customisation, integration, data cleansing, training, hosting, support, upgrades and exit costs, all in Australian dollars and shown with GST treatment. Ask about exchange-rate exposure if the vendor bills in another currency. Manufacturers importing machinery or spares through ports such as Melbourne or Botany need the ERP to support landed-cost visibility, supplier lead times and Incoterms, but procurement assumptions should also be tested against actual Australian logistics.
Treat implementation and contract risk as part of the technical decision. Review cutover, rollback, parallel running, production-downtime allowances, change management and hypercare, especially around a planned shutdown. Confirm data ownership, access controls, breach-notification duties under the Privacy Act 1988, subcontractor accountability, continuity planning and termination assistance. References should be checked for communication quality and measurable results, not merely the size of the customer logo.
Recommendations for a decision-ready RFP
A decision-ready RFP is a controlled release package rather than an open-ended request. Keep the narrative brief, but make the evidence obligations exact.
During evaluation, involve operations, finance, IT, HR and the people who will use the system. Give one scoring owner per criterion and record every assumption before commercial negotiations begin.
- Define each mandatory requirement by process, data, timing and failure condition.
- Separate genuine operating constraints from preferences and bid assumptions.
- Require fixed deliverables and named responsibilities for migration, integration and training.
- Use the same demonstration scenario and scoring matrix for every shortlisted vendor.
- Verify Australian customer references and proposed delivery partners through direct discussion.
- Price the five-to-seven-year total cost of ownership in Australian dollars.
- Include pass-or-fail gates, contractual remediation and a tested cutover and rollback plan.
The practical takeaway is to release the RFP only when each business outcome maps to a testable requirement, a scoring rule and a cost. If that chain is missing, tighten the document before responses arrive; a specific request will usually produce a more dependable implementation than a longer, generic one.