| Robot and Controller Compatibility |
Supported robot kinematics, controller generations, payload ranges, coordinate systems, and firmware versions. |
A documented compatibility matrix and a successful test using the buyer’s exact robot model and controller revision. |
Prevents unexpected reprogramming, hardware replacement, or loss of existing production assets. |
15% |
| Industrial Communication |
Native or gateway support for common industrial Ethernet, fieldbus, TCP/IP, digital I/O, analog I/O, and serial communication. |
Protocol documentation, sample configuration files, diagnostic tools, and a live handshake with the target PLC or machine. |
Reliable communication is essential for coordinated motion, machine status, alarms, and production sequencing. |
12% |
| Safety Architecture |
Safety-rated stop functions, protective devices, permission levels, safety zones, reset logic, and separation between standard and safety control. |
Risk assessment, safety circuit diagrams, validation records, and alignment with applicable machinery-safety requirements such as ISO 10218 and ISO 13849. |
Safety functions must be validated for the complete cell rather than assumed from software features alone. |
18% |
| Ease of Programming |
Graphical programming, reusable templates, waypoint teaching, parameter management, error messages, and recovery workflows. |
A trained operator should be able to create, save, modify, and recover a basic pick-and-place task with limited assistance. |
Lower programming complexity reduces commissioning time and dependence on specialist engineers. |
10% |
| API and SDK Access |
Availability of documented APIs, software development kits, command libraries, authentication, versioning, and example code. |
A developer can connect to the robot, read status, send a controlled command, and handle faults using published documentation. |
Open interfaces support custom applications, machine vision, production databases, and factory-management systems. |
10% |
| Vision and Sensor Integration |
Compatibility with 2D or 3D cameras, force or torque sensors, barcode readers, proximity sensors, and calibration workflows. |
Repeatable calibration procedure, timestamped data exchange, and demonstrated performance under expected lighting and cycle conditions. |
Sensor integration determines whether the system can handle variable product position, quality inspection, and contact tasks. |
8% |
| Simulation and Offline Programming |
Digital models, collision checking, reachability analysis, cycle-time estimation, and program transfer to the physical cell. |
The software identifies unreachable poses and collisions before deployment, with a documented process for validating the transferred program. |
Virtual commissioning can reduce production downtime and reveal layout problems before installation. |
7% |
| Performance and Motion Quality |
Path accuracy, repeatability, interpolation, speed control, acceleration limits, vibration behavior, and cycle-time consistency. |
Measured results from a representative task, including cycle time, positional repeatability, and error rate at the intended payload. |
Advertised robot specifications may not reflect actual results after tooling, payload, safety limits, and process constraints are added. |
8% |
| Data Logging and Traceability |
Event logs, alarm history, user actions, program versions, production counts, timestamps, and export formats. |
Logs can be filtered, exported, retained according to site policy, and linked to a production batch or work order. |
Traceable records simplify troubleshooting, quality investigations, and preventive maintenance. |
5% |
| Cybersecurity and Access Control |
Role-based access, password policy, secure updates, network segmentation, backup controls, and vulnerability response procedures. |
Documented security controls, user-role testing, update history, and a clear process for reporting and resolving vulnerabilities. |
Connected robot cells can affect production continuity and factory networks if access is not controlled. |
7% |
| Localization and Documentation |
Language availability, technical manuals, electrical diagrams, software release notes, training materials, and regional compliance documents. |
Operators and maintenance staff can access complete documentation in the required working language. |
Clear documentation reduces commissioning errors and supports multi-country deployment. |
5% |
| Support and Lifecycle Management |
Remote support, spare-part availability, software maintenance, backward compatibility, training, and escalation procedures. |
Defined service-level targets, support channels, maintenance policy, backup process, and published product lifecycle information. |
Long-term support affects total cost of ownership and production availability more than initial software price alone. |
5% |