提案依頼書の説明として適切なものはどれか。
平成25年度 秋期 ITパスポート試験 問17
This question's explanation and your answers so far.
問 17
Incorrectア
The creating party and the direction of the request are both reversed. It is not the vendor side but the client (ordering) company that creates a request for proposal, and it is also the client side that presents the requirements for systematization. A structure in which the vendor asks the client to present its requirements does not hold as a description of a request for proposal.
Incorrectイ
The work in which the client and the vendor jointly pin down the development content accurately and concretely corresponds to requirements definition and the fixing of specifications (a requirements definition document or a system specification) that come after the vendor to be ordered from has been decided. A request for proposal is a document that the client creates alone before vendor selection and presents to the candidate vendors, so both the timing and the creating party are different.
- ウ
正解 The correct answer is ウ. A request for proposal (RFP) is a document created by the side that wants to introduce an information system — that is, by the client (ordering) company — asking the several vendors that are candidates to receive the order, "For this requirement of ours, please propose concretely how you would realize it." An RFP states such things as the purpose of the systematization, the target business operations, the required functions, constraints such as budget and delivery date, the format and submission deadline of the proposal, and the evaluation criteria for selecting a vendor. In response, the vendors submit proposals and quotations, and the client compares and evaluates them to decide which vendor to place the order with. Therefore ウ, which satisfies both "it is the client company that creates it" and "its purpose is to request concrete system proposals from candidate vendors," is appropriate.
Incorrectエ
The document that a client issues for the purpose of broadly collecting information and accumulating technology trends, know-how, and knowledge is a request for information (RFI). An RFI is used at the stage before an RFP to gather information about the market and about vendors, so its purpose differs from that of a request for proposal, which requests the concrete proposals themselves. The point that the creating party is the client is correct, but it is wrong because the purpose is different.
- Request for proposal (RFP) = a document created by the client (ordering) company that requires candidate vendors to submit concrete system proposals and quotations. Its contents include the purpose of the systematization, the required functions, constraints such as budget and delivery date, the format and submission deadline of the proposal, and the evaluation criteria for selection.
- Keep in mind how the procurement flow maps to documents: information gathering uses an RFI (request for information) → requesting proposals uses an RFP (request for proposal) → the vendors submit proposals and quotations → a vendor is selected and contracted → the development content is made concrete in documents such as a requirements definition document. Do not mix up the fact that the RFI and the RFP are both documents created by the client, whereas the proposal and the quotation are documents created by the vendor side.