What Is an Advice Note?

RFP (request for proposal) refers to a document that provides detailed information in order to meet the identified needs from the perspective of the customer. In most cases, there is no need to prepare a formal requirements proposal, but to do so verbally.

Demand proposal

Right!

RFP (request for proposal) refers to a document that provides detailed information in order to meet the identified needs from the perspective of the customer. In most cases, there is no need to prepare a formal requirements proposal, but to do so verbally.

Writing an RFP should be serious, responsible, and serious, with specific content,

1. Title 2. Title 3. Body (beginning, body, end)
4. Signature and time

The requirements proposal must state the project objective or purpose, including any reasonable or background information that may be useful to the contractor, so that the contractor can prepare the corresponding proposal. Draft a formal requirements proposal, with the following guidelines:
(1) Must provide a statement of work (SOW)
(2) Must include customer requirements to define specifications and attributes.
(3) It should explain what kind of deliverables the client expects the contractor or project team to provide.
(4) Any items that should be provided by the customer should be listed.
(5) Explain what needs customer approval.
(6) Can indicate the type of contract the customer wants to adopt.
(7) It can indicate the payment method the customer wants to use.
(8) Indicate the schedule required for project completion.
(9) Guide and explain the format and content of the contractor's application.
(10) Indicate the deadline by which the client wishes the potential contractor to submit an application.
(11) Evaluation criteria may be included.

A Request for Proposal (RFP) is the first written document for a project client to formally establish contact with a developer, also called a tender. Generally drafted by the project's customers, it mainly describes the customer's needs, conditions, and specific requirements for project tasks, and sends it to potential developers. A demand proposal is a requirement specification prepared by the customer to ensure that the supplier understands the requirements of the project and provides a project proposal based on this. Although it does not ensure that the customer can obtain the ideal solution, it can help customers find the system preparation as close to their needs as possible. The purpose is to make the developer or project team understand what the customer wants from a customer's own perspective, through a comprehensive and detailed statement, to meet the customer's identified needs at a feasible price.
For some customers with smaller budgets, developers are often reluctant to spend energy preparing formal proposal proposals. In this case, the client's demand proposal becomes very important. In fact, no matter the size of the project, a requirement proposal needs to be written.
First, the requirements proposal needs to describe the goals and needs of the user. The process of compiling a demand proposal is also a process for customers to further clarify their goals and requirements, and to build a bridge for deep communication between customers and suppliers. This effort is worth the effort, even if the supplier does not see or is willing to respond to the demand proposal for various reasons.
Second, the requirement proposal can save the time of selection and make the comparison between suppliers easier. The information provided by the customer to all bidding suppliers is the same, which avoids repeated communication with various developers. At the same time, there is a demand proposal as a benchmark. The customer can constrain each developer to submit proposal proposals in a consistent format to improve Comparability between suppliers.
Third, the requirements proposal can avoid some potential omissions. When preparing a demand proposal, customers often overlook important factors because they pay too much attention to specific details. After receiving the demand proposal, some suppliers may actively challenge such omissions to remind customers. In order to make their proposal proposals more attractive, some developers may even propose some good ideas that are not covered in the requirements proposal to expand the customer's thinking.

^[1]

Example: Project management software development project requirements proposal of an enterprise. Relevant unit: An enterprise (Party A) decided to adopt project management for management due to business development needs. In order to control the project execution process more effectively, the enterprise It was decided to develop a project management software to meet this need ^[1] .
1. The work statement developers will perform the following tasks: develop project management software.
The main functions of the development project management software include the entry of project and work information, the drawing of the project network plan map, the arrangement of the project time plan, the formulation of the Gantt chart, the entry and analysis of project execution information, and the output of various plan reports Features.
2. Developers are required to provide development plans and implementation plans in accordance with relevant national standards.
3 The deliverables meet the project management software required by Party A.
4 Terms provided by Party A Party A will help developers become familiar with the project management process.
5. Contract type Contracts must be paid at an agreed price to developers who provide work that meets the requirements of the demand proposal.
6. Developers must submit 5 applications for backup by November 30, 2004.
7. Timetable Party A hopes to select a developer by December 25, 2004. The time limit for this project to be completed is 20-25 weeks. The project will be implemented from January 1, 2005. It requires a trial run of more than 4 weeks before the formal acceptance of the software, and appropriate modifications according to the trial operation.
8. Payment method 1/3 of the total payment when the project is completed 1/3.
When the project is completed 2/3, 1/3 of the total amount is repaid.
When Party A is satisfied with the 100% completion of the project and the developer has fulfilled all the contractual obligations, it will pay another 1/3 of the total.
9. Application content (the developer's application includes at least the following)
(1) Method. Developers can clearly understand the requirements and understand what is expected. And to describe in detail the way the developer leads the project requires a detailed description of each task and a detailed description of how the task is completed.
(2) Deliverables. The developer provides a detailed description of the deliverable.
(3) Schedule. List a Gantt chart or network chart with a schedule of detailed tasks to be performed each month so that the project can be completed within the required project completion date.
(4) Experience. Describe the projects the developer has recently implemented, including customer names, addresses and phone numbers.
(5) Personnel arrangements. List the names and detailed resumes of the person who will be designated as the principal of the project, and their achievements in similar projects.
(6) Cost. The total cost must be stated and a budget list of the project must be provided.
10 Application Evaluation Criteria (1) Scheme (30%). The developer proposed a construction plan.
(2) Experience (30%). The experience of the developer and the principal responsible for the execution of a similar project.
(3) Cost (30%). Fixed costs listed in the developer application.
(4) Schedule (10%). In order to complete the project on or before the project completion date, the developer should provide a detailed construction plan.