How to Create an ERP Software RFP: Business Requirements
Begin the business requirements section of your ERP software RFP with flow diagrams covering the major processes in your business - whether those are batch production cycles at a process manufacturer, or a purchase and stocking cycle at a retailer. This workflow is there to give prospective vendors context for the ERP requirements that will follow.
Format & Pertinent Information
Now it is time to list the requirements that have arisen from process inefficiencies in the workflow described above. There is no right or wrong way to format this section of your ERP software RFP, but the format you choose can influence a vendor to respond in a manner that you are happy with. Requirements can be displayed in long-form prose or in a tabular manner, but whatever formatting options you choose, you should always provide the following information for each requirement:
- Title - giving the requirement a title will give you and your vendor a reference point going forward.
- Reason - these could be cost reductions, cycle time improvements, competitive advantage, automation, elimination of workarounds etc.
- Priority - this can be qualitative (description of importance) or quantitative (priority score)
- Function - the functional area of the business which has the requirement
- Expectations - Where possible, give prospective vendors a quantifiable target
- Time frame - immediate, six months, two years etc. All of this is will help the ERP vendor to make the best possible proposal
- Integration - detail any requirements for this feature to integrate with external systems (include software specifications for legacy systems)
- Customization - is this requirement needed day one, out-of-the-box, or is long-term development of a custom solution acceptable?
Your requirements will not all be process related. You may want an ERP vendor who is minority-owned or local to your production plant. Your ERP system may need to run on Windows 8 and support touch screen devices or you may require a system
Having detailed your requirements, it is important to provide a format for prospective ERP vendors to reply to each requirement. This format will improve the quality of responses as well as ensuring you can easily process these responses once received. Giving vendor responses a structure also allows you to compare them directly, requirement-by-requirement.
This section of your ERP software RFP can follow much the same format you used to detail your requirements, covering areas such as feature availability, timeframe and customization. But detailing your expectations for a vendor’s response are not as simple as that, as we will find out in the next article in this series.
Featured white papers
70 features to look for in your next ERP
A comprehensive guide to help you identify requirements for your ERP selectionDownload
ERP Software RFP Guide
The comprehensive guide to developing an RFP document for your ERP projectDownload
ERP Software Pricing Guide
Get your comprehensive guide to the cost of ERP softwareDownload
The invitation to tender process for ERP
What should be included in your ERP ITT
Three ERP requirements gathering best practices
The best practices you should keep in mind when starting your requirements gathering
Considering specialty ERP requirements during selection
What industries require specialist ERP features and why they're useful during selection