Responding to an RFP: A Vendor's Viewpoint
Robert A. Kington
Abstract
Robert A. Kington
Abstract
A typical vendor of library automation systems cannot, and most likely will not want to, respond to all requests for proposals (RFPs) that it receives. Certain “elimination factors” contribute to the decision to bid or not bid. These include: 1) specifications for the use of computer equipment not employed by the vendor; 2) required features not provided by the vendor's software; 3) performance requirements not met or performed differently by the vendor; 4) a “wired” RFP based on a competitor's system; 5) the size and complexity of the RFP itself; and 6) competition for a vendor's time, such as posed by numerous other previously‐received RFPs that must be answered.
A significance statement is not available in the OpenAlex record.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
A typical vendor of library automation systems cannot, and most likely will not want to, respond to all requests for proposals (RFPs) that it receives. Certain “elimination factors” contribute to the decision to bid or not bid. These include: 1) specifications for the use of computer equipment not employed by the vendor; 2) required features not provided by the vendor's software; 3) performance requirements not met or performed differently by the vendor; 4) a “wired” RFP based on a competitor's system; 5) the size and complexity of the RFP itself; and 6) competition for a vendor's time, such as posed by numerous other previously‐received RFPs that must be answered.
Key concepts: Vendor, Request for proposal, Computer science, Automation, Software, Competition (biology), Operating system, Business