システム開発に関する RFP (Request For Proposal) の提示元及び提示先として, 適切なものはどれか。
平成21年度 春期 ITパスポート試験 問3
This question's explanation and your answers so far.
問 3
Incorrectア
The receiving side is wrong. The CIO (Chief Information Officer) belongs to the company's own management and oversees its information strategy; the CIO is not in a position to write a proposal and apply for the work. What the information systems department submits to the CIO is a plan or an internal approval document that explains the systemization plan and the soundness of the investment in order to obtain approval, not an RFP, which is a request for proposals. An RFP is strictly a document issued to vendors outside the company.
- イ
正解 An RFP (Request For Proposal) is a document presented by the side that procures the system, that is, by the user company placing the order, to the candidate vendors that may take on the development, in order to ask them: we want to build a system like this, so please send us a proposal. It brings together the information a vendor needs in order to write a proposal, such as the purpose of the systemization, the target business operations, the functional and performance requirements, the budget, the delivery deadline, the contract conditions, and the criteria for evaluating and selecting proposals. Inside the user company, the department that pulls this procurement together is the information systems department. It interviews the user departments about what they need for their work, organizes those needs into requirements, compiles them into an RFP, and presents it to several vendors. Each vendor writes a proposal and a quotation based on the RFP it received and replies with them, and the ordering side compares and evaluates the replies, selects a vendor, and moves on to the contract. In other words, the issuing side is the internal information systems department (the ordering side) and the receiving side is the external vendor (the candidate supplier side), so イ, which states this combination, is appropriate. If you keep in mind the one-way flow from the orderer to the candidate supplier, from inside the company to outside, you can narrow down the choices easily.
Incorrectウ
The receiving side is wrong, and the flow of information runs the other way as well. The user department is an internal department that actually uses the system, and it is the side that sends its business needs and requirements to the information systems department. The information systems department collects those needs from the user departments, organizes them into requirements, reflects them in the RFP, and presents it to vendors. The direction in which the information systems department would present an RFP to the user department therefore does not hold.
Incorrectエ
Both the issuing side and the receiving side are wrong, and the direction is reversed. What a vendor submits to the ordering side is the proposal and the quotation it writes after receiving an RFP, not the RFP itself. The RFP is issued by the side that procures, and the proposal comes back from the side that is procured from; the two form a pair that runs in opposite directions. In addition, the CIO named as the recipient is also part of the company's own management, and is not in a position to receive an RFP as the contact point for requesting proposals from vendors.
- An RFP (Request For Proposal) is a document that the user company placing the order (in practice, its information systems department) presents to several vendors to convey the purpose of the systemization, the target operations, the requirements, the budget, the delivery deadline, the selection criteria and so on, and thereby ask them for proposals. The direction, issuer = the orderer and receiver = the vendor, is the single most important point on this topic.
- Tell the procurement flow and its matching documents apart: gather market and technical information with an RFI (Request For Information), ask for proposals with an RFP, have vendors submit proposals and quotations, evaluate and select, then sign the contract. Remember that the RFP travels from the orderer to the vendor while the proposal travels back from the vendor to the orderer, so their directions are opposite, and that the user department is the source of requirements while the CIO is the internal approver and overseer, so neither of them is a recipient of an RFP.