A properly organized, well written Request for Proposal will eliminate the false starts, wheel-spinning, and unforeseen project requirements that cause many large scale, complex projects to go over-budget and behind schedule.
Cost/Benefit Analysis, Project Domain definition, Planning, and other global issues are addressed below. Links to informational content such as whitepapers and "How-To" articles about specific ERP Software application areas follow after that.
Considering all the things that MUST be done when in the software selection phase of any project, correct Request for Proposal (RFP) preparation is the most important! Why? Because the request for proposal directly affects all of the following:
Without an accurate future savings forecast, it is impossible to calculate the financial impact of a proposed product. Creating a meaningful RFP ensures all operational and procedural needs and related efficiency improvements are identified. This enables you to enjoy the benefits of full weighted grade point score suitability and cost/benefit analysis when evaluating vendor RFP responses!
(NOTE: Additional information about using an RFP to collect relevant cost/benefit data is available in the Optimized RFP Guide. Please see the Optimized RFP Guide Details Form to order.)
Project Domain - You might hear that a Request for Proposal is a waste of time, that a knowledgeable vendor will answer questions such as - What should a new system do? Should legacy systems be integrated or replaced? Not true at all!! How could a vendor answer these questions without first having spent a good deal of time examining your operations? And if they did, how do you know their suggestions aren't biased to their own offerings? A request-for-proposal puts you in control of your own destiny, due to the good
project planning made possible with a detailed RFP! And if you feel there is not enough time, or need assistance, there are reliable rfp software tools that make it easier!
Clearly defining the boundaries of a new system, and exactly where and how it will integrate with other systems, procedures, and departments is known as establishing the "project domain" of a new system project. Having this up-front will help you select the system best for your immediate and long-term needs, manage the entire project more effectively. Establishing the correct Project Domain is one of the most important benefits of preparing a request for proposal (RFP)!
In short, an Request for Proposal (RFP) is not just a one-time use tool for preparing just one type of RFP, but a project management tool useful over and over again for many different applications!
(NOTE: Additional information about using an RFP to collect relevant cost/benefit data is available in the Optimized RFP Guide. Please see the Optimized RFP Guide Details Form to order.)
More detailed information about selecting ERP Software for the following application types is available at:
Stop back often - new sections are added frequently
Project Planning - Done correctly, an RFP becomes a mission critical tool for successfully planning any project! Why? Ideally, the department or procedure to BEGIN the system implementation with should be the one that offers, if improved, the biggest return on the initial investment of time, people, and money. This sounds deceptively simple, but in actuality becomes very complex when data conversion, user training, and enterprise resource planning (ERP) system software issues come into play. The required system features and business priorities identified during the request for proposal preparation and rfp response evaluation processes are extremely helpful when deciding just where and when to begin system implementation!
Vendor Proposal Evaluation - Without a Request for Proposal to use as a yardstick, it is impossible to evaluate vendor RFP responses in a QUANTITATIVE manner that ensures all responses are reviewed in a consistent, objective, unbiased manner. Each vendor proposal would be different if there was no common measuriong stick - the request for proposal!
