Writing an emergency vehicle RFQ

Give suppliers a requirement they can price

Suppliers need to understand the vehicle’s duty and operating conditions before they can price a comparable scope. An RFQ connects that duty to the chassis and route limits. It also identifies the equipment and its interfaces, with the documents and acceptance method needed to check the finished vehicle.

Describe the mission before the vehicle

Describe the incident or service mission, who will use the vehicle and where. Set out the response sequence, then identify the duty that determines the design. This might be pump flow at a stated pressure or recovery of a defined casualty. For an aerial platform, it might be a basket position at a stated load; for mobile power, a load schedule.

Name the destination country and describe the terrain and climate. Give suppliers the road and bridge limits, then the site access and ground conditions. State the expected deployment duration and identify any information still unknown.

Define chassis, body and payload

State any required chassis brand, drive layout, steering position, emissions basis or service constraint only when the project has a reason for it. Otherwise describe the route and payload problem and ask the supplier to propose a compatible chassis.

Require a mass and axle-load review for the completed vehicle. It must account for the body and installed equipment, operating fluids, crew, loose equipment and operational payload. Use a revision-controlled drawing to show the body dimensions and storage layout, with access to controls and maintenance points.

Build the equipment and interface schedule

List every major system and loose item with quantity, model or performance basis, installation responsibility and required document. Include mechanical, hydraulic, electrical, communications, air, water, fuel and software interfaces where they apply.

Separate required, optional and conditional equipment. This prevents optional items from appearing as included and helps suppliers price genuine alternatives.

Specify evidence and acceptance

For each important function, state the operating condition and pass criteria. Specify the test method and instrument, with a record for the witness to complete. Name the drawings and load charts you need, along with manuals and certificates. Include labels, parts information and training records where required; “all necessary documents” leaves the scope unclear.

Agree how suppliers will submit deviations and who will approve them. Keep a record of their closure. At final inspection, identify the finished vehicle and check it against the latest approved revision.

RFQ structure

• Mission, users and response sequence
• Destination, route, climate and operating site
• Chassis, body, payload and access constraints
• Equipment, loose items and interface schedule
• Operating duty and performance conditions
• Drawings, documents, inspection and acceptance records
• Options, exclusions, open items and supplier responsibilities

Give suppliers a common reply format

Ask suppliers to respond against the same requirements rather than sending only their catalogue. The main-site quotation guide recommends normalizing scope, supporting records and delivery basis before comparing totals. [3]

A blank cell leaves the requirement unresolved; it does not establish agreement or a priced exclusion. Ask for a revised response if the missing information changes the comparison. [3]

Compare the replies against this RFQ

The quotation evaluation guide explains how to compare the replies and resolve differences in scope. Keep the supplier’s deviations with the supporting documents, then transfer the agreed requirements to the pre-shipment inspection plan.

Evidence boundary

This guide is a drafting framework, not an engineering approval or destination specification. The buyer, supplier and relevant authorities must confirm the final requirements, test basis and contractual documents for the project.