Robot matching needs gates, not one score

A percentage can hide the reason a project fails

A single compatibility percentage is attractive, but it can produce the wrong decision. A strong commercial score cannot compensate for a robot that cannot carry the configured load, operate in the required temperature or meet the applicable safety scope.

The safer approach is to test non-negotiable requirements first and rank only the candidates that remain. Unknown hard constraints should stop comparison until someone measures or verifies them.

The matching sequence

• Scope: is the intended use supported?
• Compliance: is the required evidence available or explicitly pending?
• Physical fit: load, reach, route, access, environment and utilities.
• Performance: throughput, duty, accuracy, sensing and autonomy.
• Integration: interfaces, network, data, cybersecurity and control authority.
• Operations: support, maintenance, charging, recovery and availability.
• Commercial ranking: cost, delivery, service model and trial terms.

Compare the complete solution

RobotAtom keeps three things separate: the robot platform, the configured solution and the provider offer. A base robot may be capable while the proposed tool, software or local support arrangement is not. Each recommendation should show the evidence, operating conditions, assumptions, capability margin and next validation action.

Give every bidder the same version of the work

Hard gates are only the first step. Two suppliers can both claim to meet a requirement while answering different questions. One may quote a base robot and another a guarded cell. One may time a clean demonstration cycle while another includes failed attempts and operator intervention. A side-by-side price or throughput table hides those differences unless the buyer first fixes the task and evidence boundary.

Issue one versioned brief to every bidder. It should state the task sequence and accepted output, part or load variation, site conditions, interfaces, utilities, operator contribution, operating window, test sample, measurement rule and known exclusions. If a clarification changes the brief, issue the same new version to all bidders. This is a practical buyer control inferred from measurement principles, not an ISO or NIST procurement requirement.

NIST's robotics measurement programme says application and environment matter to validation, and that system performance combines component and integrated-system behaviour. The implication for procurement is narrow but important: a component specification can inform a shortlist, while the offered configuration still needs evidence against the actual work.

Ask for the offered configuration, not a family brochure

Record the model and revision, end-effector, sensors, controls, software, safeguards, integration scope and options included in the price. Name the manufacturer, integrator and support owner. Ask which interfaces and buyer-provided inputs are excluded. A robot datasheet is useful for checking manufacturer characteristics; it is not proof that an unpriced gripper, a different firmware release or an untested site interface is part of the offer.

ISO 9946:1999 concerns how manufacturers present the characteristics of manipulating industrial robots. ISO 9283:1998 concerns robot performance criteria and test methods. Those scopes do not turn robot-level figures into evidence of accepted output from a configured cell. Both standards were confirmed in 2021 and were under review when checked on 27 September 2026; this article does not imply their full text is publicly available or that they certify a bid.

Make outcome claims inspectable

For each claimed rate, accuracy or availability figure, ask what was measured, for how long, on which configured system, with which sample and under which operating conditions. Retain the numerator and denominator, every retry or manual intervention, the exception rule, the observer and the date. Label a simulation, supplier demonstration, buyer-witnessed trial and production observation differently. A demonstration can justify another test; it cannot silently become site acceptance.

If one supplier excludes retries and another includes them, the two percentages are not comparable. If one tests only the easiest item and another tests the full agreed mix, do not average the claims together. Keep both results visible and request a common retest or a clearly qualified comparison. NIST's performance-assessment work connects component measurements and task decomposition to system performance in its research context; it does not prescribe a universal acceptance threshold for this buyer's application.

Keep safety and commercial scope outside the score

An unresolved application-safety question is not a discountable weakness in a weighted ranking. For an industrial robot cell, identify who will undertake the qualified application risk assessment, integration review and validation before use. ISO 10218-2:2025 addresses industrial robot applications and cells through integration, commissioning, operation and maintenance, within its stated scope. For a relevant driverless industrial truck, ISO 3691-4:2023 addresses safety and verification in the operating-zone context. Neither a bidder's reference to a standard nor this comparison record approves a site-specific installation.

Commercial terms need the same boundary discipline. Compare total proposals only after commissioning, buyer-provided work, support hours, spares, software licences, remote access, schedule and exclusions are visible. The cheapest visible number may simply omit work that another supplier priced. Mark the gap open instead of pretending a spreadsheet can resolve it.

Decide whether a claim is ready to compare

Use three dispositions for each supplier claim: comparable under the same brief and measurement rule; conditional, with a named clarification or retest; or not yet comparable because a hard fact is missing or the task differs. Retain the brief version, requirement, evidence link and date, configuration, conditions, result, exception, reviewer, owner and next test. This is an evidence-admissibility decision, not a supplier certification or a replacement for engineering judgement.

The separate RobotAtom bid-parity worksheet lets a buyer record one shared brief and two supplier responses without submitting the entries to RobotAtom. Use the broader supplier assessment for support, import, data, exclusions and delivery ownership. Bring a qualified safety specialist into any application-safety decision, and agree a buyer-site acceptance protocol before treating a supplier demonstration as a deployment result.