Five evidence questions before shortlisting a supplier
Score the evidence behind the answer; do not award capability points for a yes/no response alone.
- Application fit
- Can the team translate parts, process and output into testable system requirements?
- Technical boundary
- Are platform source, versions, interfaces and subcontracted work identified?
- Delivery control
- Are owners, reviews, changes, issues and evidence controlled by revision?
- Acceptance
- Do FAT, SAT and document handover have objective criteria and records?
- Lifecycle
- Are training, backups, spares, escalation and change support assigned?
Shortlist on evidence that matches the intended project. A strong reference in another process, country or platform is context, not proof that this application, service route or commercial obligation is covered.
Start with application understanding, not a robot brand
A supplier should be able to restate the production problem in engineering terms: part family and variation, material and presentation, process sequence, quality checks, target good output, changeover, utilities, environment, operators and foreseeable abnormal states. Ask what remains unknown and what test would close each uncertainty. A model recommendation made before these inputs are understood is a product suggestion, not yet an engineered solution.
OSHA describes an industrial robot system as more than the manipulator: it includes the end effector, control system, power sources, sensors and communication interfaces. ISO 10218-2 addresses integration across design, commissioning, operation, maintenance and decommissioning. The buyer therefore needs evidence that the supplier can control the complete application boundary it is quoting, including work performed through partners.
- Ask for a written application assumption list and the validation route for each critical assumption.
- Separate platform supply, system integration and site work; one company may not own all three.
- Require named inputs from the buyer as well as outputs from the supplier.
Further reading: OSHA — Industrial Robot Systems and System Safety ↗ · ISO — ISO 10218-2:2025 industrial robot applications and cells ↗
Classify every supplier answer before scoring it
Applicable, current evidence shows the process or resource exists.
The quoted scope names owner, revision, output and acceptance.
Capability may exist, but this product, region or interface is still open.
Useful as a question prompt, not as procurement evidence.
Distinguish verified capability, project commitments and promotion
A useful comparison records both the claim and its evidence. Demonstrated capability may be supported by an applicable procedure, controlled sample, current certificate within its stated scope, redacted project record, test report or named technical resource. A project commitment appears in the quotation or responsibility matrix with owner, revision and acceptance method. Marketing language such as ‘turnkey’, ‘global support’ or ‘all brands’ is neither until its exact boundary is documented.
A3's integrator certification uses organizational review, on-site audit and practical assessment as a benchmark, while A3 also cautions that buyers still need to understand the actual project's standards, digital interfaces and support needs. Treat any certification as scoped third-party evidence, verify that it is current, and never infer coverage outside the certificate or program.
Further reading: A3 — Robotic Integrator Certification Program ↗ · A3 — How to Pick the Right System Integrator ↗
Compare the project system that produces the cell
Technical skill alone does not control schedule or scope. Request the project organization, design-review cadence, requirement and document index, issue log, change-approval path, procurement plan, software repository and escalation route. Identify who can approve a substitute component, what triggers a price or schedule change, and which baseline the FAT will test. Where work is subcontracted, the prime supplier should state how requirements and evidence flow through that boundary.
FAT and SAT should be planned before award because they define what ‘complete’ means. Compare test parts, operating modes, sample duration, pass/fail criteria, witnesses, records, defect closure and re-test ownership. Also compare the handover package: as-built drawings, program and backup versions, risk-assessment and validation records where applicable, manuals, spare-parts list, training evidence and open-item register.
Evidence-led supplier comparison flow
Freeze application inputs and mandatory gates
Request records, scope and owners
Resolve assumptions and subcontracted boundaries
Pass mandatory gates before weighting preferences
Issue one baseline and compare deviations
Convert the shortlist into a project-specific commercial boundary
Do not collapse the checklist into one opaque total score. A supplier can be strong in application engineering and weak in the destination service route, or offer a sound platform while excluding fixture design and site commissioning. Keep mandatory gates separate from weighted preferences. Mark each line confirmed, conditional, open or not applicable, and attach the evidence reference. An unresolved mandatory line remains a procurement risk even when the overall score is high.
After capability screening, send every shortlisted supplier the same RFQ baseline and require a deviation list. TubeFrame can help structure a multi-brand configuration, supplier boundary and evidence request from the workpiece and intended application, subject to project review. Authorization, certification, delivery, warranty and service geography must be confirmed in writing for the exact supplier, product and destination.
Industrial robot supplier capability and evidence checklist
Use one row set for every candidate. Add mandatory/preferred weighting only after the evidence class and project relevance are recorded.
Copy the rows into your RFQ or investment worksheet.
| Comparison area | Supplier response required | Risk / open item | Acceptable evidence |
|---|---|---|---|
| Application understanding | Requirements, assumptions and feasibility risks | Model proposed before inputs are known | Application study and open-input log |
| Platform source | Manufacturer, model, controller and supply route | Authorization or availability inferred | Current written product and route confirmation |
| Technical documents | Datasheets, drawings, interface and revision list | Generic brochure replaces project files | Controlled document index and sample |
| Interface engineering | Mechanical, electrical, I/O, network and utility ownership | Cross-vendor gap has no owner | Interface matrix and design review record |
| Safety process | Applicable standards, risk and validation responsibility | Robot declaration treated as cell approval | Scoped procedure and project deliverable list |
| Project organization | Named technical, commercial and escalation roles | Dependence on one unavailable person | Organization chart and communication plan |
| Quality control | Inspection, nonconformity and corrective-action route | Quality promise without records | Procedure and example controlled record |
| Change management | Baseline, approval classes and substitution notice | Unilateral component or software change | Change workflow and revision history |
| FAT and SAT | Test scope, criteria, records, defect and re-test owners | ‘FAT included’ without protocol | Draft protocol and report template |
| Spares and lifecycle | Critical spares, backup, obsolescence and replacement route | Only initial hardware is covered | Project spare list and support boundary |
| Service boundary | Destination coverage, hours, response route and exclusions | ‘Global support’ lacks responsible entity | Named route and commercial terms |
| Commercial responsibility | Warranty, delivery, taxes, insurance, liability and acceptance | Terms conflict across documents | Order-of-precedence and deviation schedule |
Frequently asked questions
What should an industrial robot supplier comparison include?
Compare application understanding, platform and supply route, documents, interfaces, safety process, project organization, quality, change control, FAT/SAT, spares, service and commercial responsibilities using the same evidence request for every candidate.
Does certification prove that a supplier fits my project?
No. A current certification can provide useful third-party evidence within its stated scope, but the buyer must still verify the intended application, people, interfaces, destination, quoted responsibilities and acceptance plan.
How should a buyer score promotional claims?
Do not score them as capability. Convert the claim into a specific question, request applicable evidence, and classify the final answer as demonstrated, committed for this project, still open or unsupported.
Should the lowest-price robot supplier win?
Price should be compared only after scope, assumptions, deviations, interfaces, acceptance and lifecycle responsibilities are normalized. A lower total with missing work is not a like-for-like offer.
Primary sources and evidence boundary
Turn supplier claims into a reviewable project boundary
Share the application, workpiece, target output, destination and preferred responsibility split. TubeFrame can identify open supplier inputs and structure a comparable multi-brand RFQ, subject to project review.
Prepare a supplier comparison ↗