Request for solution

A request for solution (RFS, also known as request for proposed solution)[1] is a commercial document that describes a technological or organizational situation and demands a solution (for example, a new arrangement of information technology, IT) to possible suppliers of this solution. This document is normally issued by the organization which would benefit from the solution. The buying organisation keeps a dialogue with would-be suppliers to determine together the best solution.[1]

A complex arrangement of parts. A request for solution could ask a simpler arrangement performing the same functions.
Not to be confused with Wikipedia:Request for solutions, which is a Wikipedia phased out dispute solving method.

The difference with a request for proposal (RFP) consists of the RFS being much more open and leaving more space to innovate. Both RFP and RFS have requirements, but those of RFS are more general.[2] RFSs also need less time[2] to be answered, so they are likely to get a higher number of responses.

"A classic example of request for solution: the client gave general instructions regarding the solution while laying lesser restrictions on specific technology."[3]

"In contrast to a detailed, buyer-led RFP, the RFS is an open-ended, collaborative process. The customer describes its environment, objectives, concerns, and risk tolerance and the potential suppliers come back with solutions that meet those general requirements."[4]

The RFS may be used as the first step in a procurement process. Once a determined solution has been selected, the process can advance one step, issuing, for example, a RFP, more specific and detailed.

Controversy

Lutz Peichert[5] challenges the need for yet another procurement term (RFS) when RFP already exists. John Healer,[5] on the contrary, has found "the Request for Solution language to be of value". Researchers[1] from the University of Tennessee consider RFS "an emerging competitive bidding methodology".

gollark: Or he's too busy subtly adjusting the colours of buttons.
gollark: It's probably embedded in thousands of lines of cryptic PHP spaghetti.
gollark: We need more drama, more *action*, more **suggestions/requests**.
gollark: Go to Suggestions/Requests!
gollark: Ah, yes.

See also

References
  1. Vitasek, Kate; Kling, Jeanne; Keith, Bonnie; Handley, David (2016). Unpacking Collaborative Bidding (PDF). Tennessee, USA: HASLAM COLLEGE OF BUSINESS. p. 9. Archived from the original (PDF) on 28 April 2017. Retrieved 27 April 2017.
  2. Tonti, Jon (July 3, 2012). "Out with Request for Proposals and in With Request for Solutions". Nearshore Americas. Retrieved 11 April 2017.
  3. mkrishna (July 27, 2012). "Why Request for Solution (RFS) is a better approach". Suyati. Retrieved 18 April 2017.
  4. Overby, Stephanie (June 15, 2012). "Why Your IT Outsourcing RFP Is Holding You Back". CIO from IDG. IDG. Retrieved 11 April 2017.
  5. Peichert, Lutz (July 19, 2012). "Lutz Peichert's Blog". Lutz Peichert. Retrieved 18 April 2017.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.