Heavy-Payload AMR RFQ Template: How to Compare Supplier Quotes and Technical Evidence
Two suppliers quote the same heavy-payload transport project. Both offer autonomous mobile robots, charging equipment and commissioning. One proposal is cheaper. Yet its price excludes station controls, charges separately for software access and assumes that the buyer will provide a technician during every production shift. The other proposal includes those responsibilities. Comparing the cover-page totals would reward a difference in scope before anyone has established a difference in value.
A useful heavy payload AMR RFQ makes these differences visible before the purchase order. It connects each requirement to an operating condition, a supplier commitment, supporting evidence, an accountable party and a price treatment. Procurement can then compare offers that solve the same material-flow problem.
This AMR RFQ template is designed for factory buyers purchasing an integrated transport application. It covers the robot, load interface, stations, fleet software and implementation responsibilities. An OEM buying an unfinished chassis will need a different delivery boundary. The practical objective here is a bid package that engineering, operations, procurement, maintenance and IT can review together.
First decision: is the project ready for a priced quotation?
An RFQ is a request for quotation. It works best when suppliers can price a sufficiently defined requirement. If the buyer is still deciding between a towing system, an under-cart robot and a lift-platform architecture, requesting a single fixed price may conceal fundamental design differences.
A request for information can establish supplier capabilities. A request for proposal can explore competing solutions. These are useful distinctions, rather than compulsory stages for every project. An experienced buyer may proceed directly to quotation when the application boundary and supplier shortlist are already clear.
Before release, settle three questions: what must the system deliver, what site conditions may suppliers assume, and which responsibilities remain with the buyer? If one answer is unresolved, identify the uncertainty and request a separately priced assumption or option. Do not let each bidder quietly invent a different baseline.
The existing AMR procurement checklist provides a broader starting point for equipment selection. At the quotation stage, turn that selection logic into controlled requirements and response fields. A recommendation such as “check charging suitability” must become a requirement tied to shift length, available charging windows and the promised production output.
The buyer's issue package: six documents that make quotations comparable
A strong AMR technical specification begins with the process, not a list of attractive robot features. Issue one revision-controlled package to all participating suppliers. Include a document register so that a layout update cannot be mistaken for an informal illustration.
| Attachment | Buyer-provided content | Required supplier response |
|---|---|---|
| A. Mission and demand schedule | Pickup and delivery points, load families, shift calendar, demand peaks, empty-carrier returns and transfer-time boundaries. | Proposed fleet and charging concept, capacity assumptions and unresolved demand constraints. |
| B. Load and carrier register | Mass ranges, dimensions, support points, center-of-gravity envelope, carrier variation and relevant drawings. | Supported combinations, restrictions, required adaptations and configuration-specific evidence. |
| C. Site conditions | Route drawings, aisle restrictions, floor observations, gradients, doors, crossing traffic and network constraints. | Survey findings, required modifications and the party responsible for each prerequisite. |
| D. Interface and responsibility map | Stations, PLCs, production systems, electrical supplies, data owners and existing controls contractors. | Interface deliverables, named responsibility boundaries and any third-party dependency. |
| E. Verification and acceptance schedule | Required outcomes, test conditions, records, review stages and proposed acceptance responsibilities. | Verification method, evidence available now, future test commitments and exceptions. |
| F. Commercial return schedule | Common price categories, comparison period, currency, delivery basis and option rules. | Itemized prices, recurring charges, exclusions, price validity and payment assumptions. |
Label every input as measured, estimated or still to be confirmed. A supplier should not be expected to guarantee performance against an unknown floor condition, but the buyer should not accept an unlimited disclaimer either. Specify the survey or measurement that will close the uncertainty and the date by which its commercial consequences must be resolved.
Use the site's AMR site survey checklist to organize site observations. For load data, reference payload and center-of-gravity limits when defining the supported operating envelope. The RFQ should preserve those conditions in the supplier's answer, rather than reduce them to a single payload number.
Build the response matrix before requesting prices
For effective AMR supplier evaluation, separate three things that sales proposals often combine: what the supplier promises, what evidence currently supports that promise, and how the delivered system will be verified. These are related questions, but they are not interchangeable.
Give each requirement a stable identifier. Ask suppliers to retain the identifiers when they submit deviations, test reports and commercial options. The following structure is an editorial procurement template; it is not a form prescribed by ISO, VDA or NIST.
| Field | What to enter |
|---|---|
| Requirement ID and priority | A stable reference and classification as mandatory, evaluated or optional. |
| Requirement and operating condition | The required outcome, units, applicable load, route, software configuration and measurement boundary. |
| Supplier response | Complies, conditional, deviation, not offered or not assessed, with an explicit explanation. |
| Evidence reference | Document title, revision, date, relevant page or test record, and configuration covered. |
| Verification commitment | Proposed inspection, analysis or test; acceptance threshold; responsible party; and delivery stage. |
| Dependency and owner | Required buyer action, third-party work or site condition, including its responsible organization. |
| Commercial treatment | Included price line, separately priced option, buyer-retained cost or unresolved quotation item. |
| Closure record | Open question, decision owner, agreed deadline and final approved disposition. |
A compliance response is not an evidence grade
“Complies” should identify a commitment against the stated condition. “Conditional” should identify the condition precisely. “Deviation” should describe the difference and its operational consequence. A blank field remains unresolved; it does not mean included, compliant or free.
Record evidence maturity separately. A catalog statement, an engineering calculation, a configured laboratory test and a witnessed site test answer different questions. Choose evidence appropriate to the claim. A controlled fatigue analysis may be more relevant to a structural question than a short demonstration in a warehouse.
For example, a runtime claim needs its load, duty cycle, charging policy and auxiliary power conditions. MiR's published MiR1350 specifications distinguish active operating time at maximum payload from operation without payload and note the influence of local conditions and configuration. This manufacturer example supports requesting conditional specifications; it is not a runtime benchmark for every heavy-payload platform. See the official MiR1350 specifications.
Do not demand completed site acceptance evidence before the equipment exists. At tender stage, request applicable existing evidence plus a binding plan for project-specific verification. Record who will supply representative loads, approve the method, witness the test and pay for a repeat test if the first result fails.
Ask for evidence at the boundaries where proposals become ambiguous
Safety: identify the configuration and the operating zone
ISO 3691-4:2023 addresses safety requirements and verification for driverless industrial trucks and their systems. Its public scope also identifies the importance of operating-zone conditions. Buyers should therefore ask which equipment configuration, system boundary and site assumptions a supplier's safety documentation covers. See the official ISO 3691-4:2023 scope.
A certificate, a supplier declaration and a project risk assessment are different records. Request the issuer, subject, revision and limitations of each relevant document. Assign responsibility for reviewing the complete application, including the top module and transfer stations. A component document should not silently become evidence for the entire installation.
Interoperability: specify the actual exchange, not only a protocol name
If suppliers offer VDA 5050 connectivity, request the supported version, capabilities, optional actions, extensions and the fleet-controller combination to be tested. VDA's official publication identifies version 3.0.0 in March 2026. A newer published version does not establish which version a particular product implements.
The VDA specification does not, by itself, cover project acceptance, safety, traffic-management algorithms, peripheral interfaces or cybersecurity. Put those requirements in separate rows. See the official VDA 5050 publication and its published technical specification.
Ask the supplier to describe order rejection, connection loss, restart and recovery behavior for the proposed integration. An interoperability demonstration should exercise relevant exceptions as well as a successful transport order. Record any proprietary extension that another robot or controller would need to implement.
Remote support: make access and recovery deliverables visible
IT and operational technology teams should review the proposed remote-support route before award. Request an access diagram, approval process, account responsibilities, activity records and a method for removing access. Include backup ownership and a restoration demonstration in the delivery plan.
These requests align with the remote-access and recovery guidance in NIST SP 800-82 Revision 3. That publication is OT security guidance, not an AMR product certification. Translate the relevant guidance into requirements suited to the plant's architecture and policies.
Turn interface assumptions into named work packages
The most expensive ambiguity may sit between suppliers. The robot vendor assumes the conveyor contractor will change the PLC. The conveyor contractor assumes the robot integrator owns transfer recovery. Operations discovers the gap when a load stops halfway through a handoff.
Define the AMR integration scope around observable outcomes. For a transfer station, identify who supplies sensors, modifies the PLC, implements the handshake, handles interrupted transfers and confirms the final load state. “Interface included” is too broad to settle those responsibilities.
For every interface, record the two connected systems, the information or physical state exchanged, the implementing party and the party that approves the result. Assign one owner to coordinate shared tests. Technical ownership and commercial payment can sit with different organizations, so record both explicitly.
The same discipline applies to network surveys, electrical installation, charger placement, building permits where relevant, server provisioning and production downtime. Buyer-retained work is not automatically a supplier exclusion to reject. It is a responsibility to understand, resource and include in the comparison when bids allocate it differently.
Make the price return explain what the buyer must actually purchase
A useful AMR quotation comparison begins with a common commercial boundary. Ask suppliers to distinguish base scope, mandatory additions, optional enhancements and recurring commitments. Do not compare a turnkey proposal with a robot-only price and then treat the difference as a discount.
For each line item, request quantity, unit, unit price, extended price, currency, payment timing and the requirement IDs covered. Record freight, taxes and delivery terms separately. Specify the comparison date and exchange-rate convention when quotations use different currencies.
Software deserves its own schedule. BlueBotics' fleet-manager RFQ guidance identifies licensing, software tools, programming, commissioning, training and support as distinct cost areas. Its scope is fleet-management procurement; the broader project schedule here also includes hardware and site responsibilities. See the BlueBotics fleet-manager RFQ guide.
- Hardware and application equipment: robots, load interfaces, chargers, docking equipment, station modifications and initial spare parts.
- Engineering and deployment: surveys, software configuration, PLC work, project management, travel, commissioning and production support.
- Software rights: robot and site limits, required modules, hosting, update entitlement, data access and expansion charges.
- Service commitments: preventive maintenance, support coverage, on-site attendance, replacement parts and agreed escalation arrangements.
- Change mechanisms: day rates, additional station prices, fleet expansion, layout changes and charges after the included commissioning period.
Require “included in line X” rather than an unexplained zero. Separate a fixed charge from an estimate, a cap and an item still awaiting a quotation. An unknown price should remain visible as uncertainty; entering zero makes an incomplete offer appear commercially superior.
Also distinguish warranty from service coverage. A warranty may address defects without defining an engineer's arrival time or a production-restoration commitment. Compare service hours, response definitions, exclusions, escalation routes and the resources needed at the buyer's site.
Worked example: the cheaper quotation changes after scope alignment
The following figures are invented solely to demonstrate bid normalization. They are not supplier quotations, market prices, expected savings or evidence of a typical project cost. Assume both offers have already passed the same technical gate and propose equivalent delivery and service outcomes.
| Compared commitment | Supplier A | Supplier B |
|---|---|---|
| Initial quoted package | $240,000 | $275,000 |
| Required station integration | $40,000 additional | Included in package |
| Required commissioning and training | $20,000 additional | Included in package |
| Comparable annual software and service fees | $18,000 per year | $12,000 per year |
| Five years of those fees | $90,000 | $60,000 |
| Compared total | $390,000 | $335,000 |
Supplier A appears $35,000 cheaper at quotation level. After adding the required scope and five years of fees, Supplier B is $55,000 lower on this defined comparison. The annual-fee row is explanatory: add the five-year fee total once, rather than adding both rows.
This is an undiscounted comparison of specified purchase and service commitments. It excludes taxes, financing, energy, retained labor, downtime and other costs outside the example. Fees are assumed to apply in years one through five without escalation. It is not a complete total-cost-of-ownership model.
In a real tender, verify that the two service packages genuinely cover the same outcomes. If an unresolved interface could add substantial cost, request clarification or show a documented range. Do not manufacture a precise adjusted total from an unsupported allowance.
Apply qualification gates before weighted scoring
Start AMR supplier qualification by identifying the conditions that must be satisfied for an offer to remain eligible. Examples include the required operating envelope, an acceptable safety responsibility boundary, a credible integration plan and acceptance of essential verification obligations.
A gate may require evidence available now or agreement to a defined future test. Make the distinction explicit. A supplier should not fail merely because a project-specific site test cannot yet occur, but a promise to define the test after purchase is not equivalent to an agreed verification plan.
Score only offers that pass the applicable gates. The following weights are an illustrative buyer-designed model, not an industry standard. Set them before reviewing prices and adapt them to the consequences of failure at the particular plant.
| Criterion | Weight | What reviewers assess |
|---|---|---|
| Application fit | 30% | Ability to meet the defined missions and operating conditions without unacceptable restrictions. |
| Evidence and verification readiness | 20% | Relevance of supporting records and clarity of the remaining verification commitments. |
| Integration and delivery | 20% | Responsibility clarity, implementation resources, dependencies and schedule credibility. |
| Service and maintainability | 15% | Support arrangements, repair capability, documentation, spares and plant maintenance workload. |
| Normalized commercial offer | 15% | Comparable scope, recurring commitments, price certainty and agreed commercial conditions. |
Define criterion-specific scoring anchors before evaluation. For each criterion scored from zero to five, its weighted contribution is the weight multiplied by the score divided by five. Keep reviewers' evidence notes beside the score. A discount must not compensate for failure of a mandatory requirement.
Operations should review process assumptions; engineering should review technical fit; maintenance should review recovery and service workload; IT should review connectivity and access; procurement should control commercial consistency. Finance can test the comparison assumptions without replacing the technical gate with a payback calculation.
Use controlled clarification rounds to close material gaps
After the first submissions, compile questions by requirement ID. Prioritize ambiguities that change eligibility, scope, cost or the delivery schedule. A request such as “please confirm integration” is unlikely to resolve anything. Ask which PLC program changes, test records and recovery functions are included in a specified price line.
When a clarification changes the common requirement, issue an addendum to all affected bidders through the same controlled process. Protect each supplier's confidential design and pricing. Require each revised offer to identify the RFQ revision, quotation revision and assumptions it supersedes.
Keep optional alternatives separate from the compliant base offer. A supplier may propose a different robot count, charging arrangement or station design that improves the application. Evaluate its technical consequences and price independently so that an attractive alternative does not obscure the original comparison.
Close each material item as accepted, rejected or retained with an explicit owner and deadline. Do not let an unresolved commercial issue disappear into meeting notes. If a remaining uncertainty could reverse the supplier ranking, the award recommendation should explain that uncertainty directly.
Carry the evidence trail into the award and acceptance package
The final AMR acceptance criteria should be traceable to the requirements used to select the supplier. Preserve requirement IDs through design review, factory acceptance testing, site acceptance testing and handover. This prevents a promised capability from being replaced by a convenient demonstration.
For each critical outcome, agree the test conditions, duration or sample, instruments, allowable interruptions, result calculation and treatment of failed runs. Define what constitutes a completed mission and which delays fall inside the measured boundary. Agree who approves deviations and what evidence is required to close them.
Identify the approved hardware, top module, software version and relevant configuration baseline. Specify how changes trigger an impact review and, where needed, repeat verification. Include training records, maintenance instructions, backup access, spare-parts lists and unresolved punch-list items in the handover schedule.
A disciplined award package links the final scope, quotation, deviations, verification schedule and responsibility matrix. Its value is practical: when production, engineering and the supplier disagree later, they can return to a shared record of what was purchased and how completion will be demonstrated.
Focused FAQ
What should a heavy-payload robot quotation include?
It should identify the configured equipment, operating assumptions, load interfaces, software rights, integration work, commissioning, training, service obligations and exclusions. It should also connect performance commitments to evidence and a verification plan. A robot price alone cannot describe the cost or responsibility boundary of an integrated factory application.
Can the same template cover AGVs and AMRs?
Yes, the response structure can accommodate both. Adapt the AGV RFQ requirements to the proposed guidance method, infrastructure, route-change process and traffic-control responsibilities. Compare the required material-flow outcome under common conditions rather than assuming that the technology label determines performance or installation effort.
What if a supplier will not share confidential test reports?
Agree a proportionate alternative, such as a redacted report, a controlled review or a witnessed demonstration with an agreed protocol. Record the limitations of what was reviewed. Confidentiality can change the evidence-sharing method; it should not convert an unsupported statement into an accepted performance guarantee.
Should the lowest normalized price win?
Not automatically. First confirm mandatory compliance, then apply the evaluation method established before bids were received. Relevant evidence, integration responsibility, delivery capability and service resources can justify a different selection. Record the reasons so the recommendation remains understandable beyond the team that conducted the tender.
How much detail belongs in an initial tender?
Provide enough detail to prevent material assumptions from diverging between suppliers. Prioritize mission demand, operating conditions, boundaries and verification. If important inputs remain unknown, state how they will be resolved. A shorter controlled package is more useful than a lengthy specification filled with requirements nobody can measure.
Who should own the final comparison?
Procurement should maintain the controlled commercial comparison, while accountable technical and operational reviewers approve their respective requirements. Assign a project owner to resolve cross-functional decisions. The final recommendation should show passed gates, remaining conditions, comparable commitments and the evidence supporting the proposed award.
Editorial and evidence note: This article presents an independently developed procurement workflow. The response fields, evaluation weights and commercial example are illustrative recommendations, not standardized forms or reported customer results. Linked primary sources support the specific statements beside them; they do not endorse this template or certify any proposed installation.
