Industrial Robot RFQ Comparison Matrix

Freeze one RFQ baseline before requesting prices

The RFQ baseline should identify the part family, drawings and revision, material and incoming variation, process sequence, quality criteria, target good output, shifts, changeovers, site environment, utilities, layout envelope, destination and intended acceptance route. State what the buyer will supply: sample parts, upstream and downstream equipment, network access, power, air, gas, extraction, rigging, operators and production time. If bidders start from different inputs, later price normalization cannot recover a fair comparison.

NIST's integrator definition spans final engineering, documentation, hardware procurement, custom software, installation, testing and commissioning. That breadth explains why ‘robot system’ is not a sufficient RFQ line. Decompose the requested outcome into physical equipment, software, engineering work, site work, evidence and lifecycle support, then require bidders to state where their responsibility starts and stops.

• Issue one numbered requirement set and one controlled bidder-question log.
• Require a quotation validity date and the configuration revision it prices.
• Separate mandatory scope from alternates so options do not disappear inside totals.

Further reading: NIST — Integrator definition from control-system specification guidance ↗

Normalize configuration, scope status and commercial assumptions

For each hardware and software line, capture quantity, manufacturer and model or performance specification, controller release, licensed option, approved equivalent, included accessories and document revision. For engineering and service lines, capture hours or visits only when the supplier states them; otherwise compare the defined output and boundary. ‘Programming included’ should become a list of part programs, modes, recipes, backups, comments, passwords, source files and change support.

Use explicit status values: included, priced option, excluded, buyer-supplied, third-party direct, allowance or pending clarification. An allowance is not a fixed price, and an approved equivalent is not the same as an identified model. Preserve taxes, duties, insurance, payment milestones, Incoterm, quotation assumptions and escalation clauses outside the technical matrix but link them to the same comparison revision.

Assign every interface and acceptance record

Robotic cells combine components that exchange mechanical loads, electrical power, safety signals, production states, data, utilities and physical parts. NIST's interoperability work highlights that integration depends on information models, protocols and test methods, not merely compatible connectors. Use an interface responsibility matrix naming the provider of each side, design authority, installation owner, test condition and evidence record.

Safety is an application responsibility. Universal Robots' integration guidance, for example, places risk assessment, machine interfaces, protective measures, safety settings, validation, instructions and retained documentation within the integration boundary. Do not generalize one manufacturer's wording to every product or jurisdiction; use it to expose the questions that the project must assign and verify. FAT should test the agreed factory baseline, while SAT should test destination interfaces and handover conditions that cannot be proven at the supplier site.

Further reading: NIST — Robotic Systems Interoperability and Integration ↗ · Universal Robots — Integration and Responsibility ↗ · ISO — ISO 10218-2:2025 industrial robot applications and cells ↗

Build the comparison total without inventing missing costs

Keep three values separate: the supplier quotation total, confirmed priced options needed to meet the common baseline, and buyer-side residual scope. If a required line has no price, leave it open and request clarification; do not insert a TubeFrame estimate or an anonymous market number. A comparison can identify exposure qualitatively—open, conditional or excluded—until a valid cost and owner exist. This preserves the original quotation and prevents false precision.

Lifecycle scope deserves its own comparison. ABB's public supplier handbook illustrates that spare parts can involve hardware, repair, service tools, software and documentation, and that obsolescence and substitution need controlled handling. Do not import ABB's supplier requirements as a universal promise. Instead, ask each bidder for the project-specific critical-spares list, availability route, repair path, backup and restore package, training, support contact, exclusions and end-of-life notice process.

Further reading: ABB Robotics — Supplier Handbook ↗

Industrial robot RFQ normalization matrix

Add quantity, supplier price, status and revision in your commercial worksheet. These prompts define what must be clarified; they do not supply a price.

Copy the rows into your RFQ or investment worksheet.