Collaborative Robot
System
Topic overview
Quick facts
- Definition of Collaborative Robot in functional safety
- Collaborative Robot in depth
- The case for Collaborative Robot
- Collaborative Robot in practice
- Where teams get Collaborative Robot wrong
- Collaborative Robot and its standards
- Industries where Collaborative Robot applies
- Ask our team about Collaborative Robot
- Terms related to Collaborative Robot
The standards define four collaboration methods, and precision about them matters because their engineering differs completely. Safety-rated monitored stop halts the robot, with certified monitoring, while a person is in the shared space and resumes when they leave. Hand guiding permits motion only under direct operator control of a guiding device.
Speed and separation monitoring keeps a protective distance between robot and human using safety-rated sensing, slowing and stopping as people approach.
Power and force limiting (PFL) allows actual contact, but bounds its severity by design so that pressures and forces stay below biomechanical thresholds; publishes those thresholds per body region and defines how transient and quasi-static contact are evaluated.
The most consequential correction to popular understanding: there is no such thing as a certified-safe cobot, only a safe collaborative application. A PFL-capable robot arm carrying a sharp tool, a heavy gripper, or working near a person's face can be far more dangerous than a conventional robot behind a fence.
The application risk assessment, robot plus end effector plus workpiece plus task plus workspace, is what determines safety, and the 2025 revision of ISO 10218 integrates much of TS 15066's content while sharpening exactly these application requirements.
PFL applications are validated by measurement: force and pressure at the actual contact points are measured with calibrated biofidelic devices and compared to the TS 15066 limits for the body regions actually exposed, with speeds reduced until measurements pass.
Quasi-static contact (trapping a hand against a fixture) is typically the binding constraint, and clamping situations near fixed surfaces demand particular attention in cell layout.
The case for Collaborative Robot
Cobots are sold on the promise of fenceless automation and quick deployment, and the safety reality determines whether that promise survives contact with a real application: PFL force limits frequently cap speeds well below the robot's capability, quietly destroying the cycle-time assumptions in the business case.
Buyers who treat the arm's marketing as the safety argument inherit legal responsibility they did not price, in most regimes the integrator or employer owns the application risk assessment. Understanding early which collaboration method the task actually supports is therefore a make-or-break input to automation ROI models, not a compliance detail.
Collaborative Robot in practice
Collaborative application assurance
The integrator (or end user acting as one) performs an risk assessment of the complete application, selects the collaboration method per task step, and engineers accordingly: safety-rated monitored stop and SSM require certified sensing with distances computed from approach speeds and stop times; PFL requires identifying every credible contact scenario, classifying body regions, and designing end effectors and workspace geometry to avoid sharp edges and clamping points.
PFL validation uses calibrated measurement devices at the identified contact points, documented against the TS 15066 thresholds; safety functions carry ISO 13849 PL ratings, typically PL d.
Auditors want the contact scenario inventory, the measurement records with device calibration, the field or distance calculations, and evidence the assessment covers the tool and workpiece, not just the bare arm.
Where teams get Collaborative Robot wrong
Collaborative Robot and its standards
ISO 10218-1/-2 sets the requirements that Collaborative Robot work has to satisfy: safety requirements for industrial robots (part 1) and robot systems and integration (part 2).
Collaborative Robot is defined and governed by ISO/TS 15066 - guidance for collaborative robot operation, including power and force limiting thresholds.
Collaboration methods (ISO 10218 / TS 15066)
| Method | Principle | Typical use |
|---|---|---|
| Safety-rated monitored stop | Robot stops while human in space | Hand-loading stations |
| Hand guiding | Operator moves robot directly | Teaching, lift assist |
| Speed and separation monitoring | Speed scales with human distance | Shared floorspace, fenceless cells |
| Power and force limiting | Contact forces below injury limits | Small payload assembly beside people |
Industries where Collaborative Robot applies
Robotics & Automation programs lean on Collaborative Robot because the sector covers industrial robots, cobots, amrs, and automated warehousing systems.
Ask our team about Collaborative Robot
Ben TwomblyFounder & CEOLeads CSA's functional-safety, certification, and engineering programs for safety-critical products and organizations. His assessor-side background informs practical programs that connect standards, engineering work, and credible evidence.
Tom CyrPrincipal Safety Engineer, IFSPSupports industrial and rail functional-safety programs with safety analysis, requirements, lifecycle planning, and certification-readiness guidance.Terms related to Collaborative Robot
How each connects to Collaborative Robot:
Programs that deal with Collaborative Robot almost always involve AMR in the same phase.
Safety Function is the natural next concept after Collaborative Robot; assessors expect teams to connect the two.
PTC is a system of the same kind; teams comparing the two usually need both.
ATO plays the same role in its domain that Collaborative Robot plays here.
Understanding Collaborative Robot is easier with Functional Safety as context, and vice versa.
Teams working on Collaborative Robot typically encounter Performance Level in the same program.
Understanding Collaborative Robot is easier with Verification and Validation as context, and vice versa.
Teams working on Collaborative Robot typically encounter Safety Management System in the same program.
Teams working on Collaborative Robot typically encounter Functional Safety Engineer in the same program.
Safety Manager complements Collaborative Robot: one frames the question, the other shapes the evidence.
Safety-Critical System complements Collaborative Robot: one frames the question, the other shapes the evidence.