The Request for Information is part of the pre-selection of potential software manufacturers and solutions. Companies ask non-binding price and performance information from software providers. The term Request for Information (RFI) comes from the field of e-business and describes a process from the software tendering of companies. Often this whole process together with a general pre-selection is called Request for Information. Find out more on this website.
Request for Proposal as a concrete request
In addition to the RFI, there is a Request for Proposal (RFP) in the software selection and software procurement. After obtaining a rough overview of the prices and services for general products from different providers, the Request for Proposal asks for more detailed information about possible software solutions. In contrast to the RFI, the RFP consists of binding offers and should only be requested from those providers who are realistically eligible.
Chapter / Contents of a Request for Information (RFI)
For a RFI, you need a good structure to almost completely take into account all the important things in the tendering process.
Target Description / Purpose
This chapter explains what you want to do with the system. Ideally, this is a process description that explains how this system should support the processes.
Definitions / abbreviations
In general, business terms and abbreviations are used by default in companies. Always assume that terms are used in other companies in a different modified context.
Declaration of trust
All information provided in this document and the entire tendering process must be kept strictly confidential. This chapter should be written together with the purchasing department and the legal department.
Description of the tender process
This section describes the schedule, rules and contacts and their roles. The selection criteria and potential exclusion criteria must also be described here.
Functional and non-functional requirements
All functional functions should be described in this section.Non-functional requirements include usability / usability requirements, authorization concept, operational processes, documentation and training.
Technical requirements such as requirements for hardware and middleware, performance, scalability, reliability, robustness, data security, technical architecture, etc. are also part of the RFI.
Information about licensing models, business models such as product vendors, licensing providers, service companies, etc. are queried in this chapter.
Conclusion: Strategy and Partnership
This very important chapter poses questions and requirements for the software provider regarding strategic direction and partnerships. Product strategy, near shore, offshore, outsourcing and strategic alliances are part of this chapter. Presentation Current financial status, number of employees in product development, industry expertise, employee policy, etc. are important information for a strategic partnership and are queried in this chapter of the RFI. As you can see the whole range of facilities of RFI in BPM sector, the quality of the BPM system thus should also be high in quality.