To RFP or not to RFP
It has been my experience that a request for proposal for any large scale project is crucial
for any business when undertaking something that will have an affect on their business processes
or their local computing environment. A RFP or Request for Proposal is a tender that a corporation
puts out to various vendors so work can begin on what will eventually be either a change in the
overall business support system or their operational support system.
These changes can involve anything from making small tweaks to their current processes or systems
or to completely overhauling it from the ground up to build something that will improve the
way the operate internally or with external entities. RFP's are crucial to learn more about what
a vendor will be doing the change and how that change will be brought about and the various costs
associated with it.
Some of the most basic things that one should have in an RFP are as follows:
1. Description of company, including type of organizational structure
2. Business goals
3. Project goals
4. Scope of project
5. Time constraints
6. Budget constraints
b. Existing system
d. Operating systems
f. Application software
m. Disaster recovery
i. Installation issues
These are just a few things that I would look for in an RFP; not only would a vendor have to fill out in
detail what they will be doing with any existing systems but they would also have to describe how to conserve
on implementing new systems without going over budget or project time constraints.
Again the RFP can be as long and detailed as a company wants but can also be for smaller projects that may do
smaller changes to existing systems that wont have too much of an impact on how things are done. This in my opinion
can save an organization valuable time but also help with their bottom line.