Collaborative robot safety is central to deploying automation in workspaces shared by people and robots. Cobots can expand automation options and support Industry 4.0 initiatives, but their ability to operate without safety fencing does not remove the need to assess and manage risk. A collaborative application must use a defined safety approach that protects people while accounting for how the robot and workers interact.
ISO/TS 15066 specifies safety requirements for collaborative industrial robot systems and their work environments. It supplements ISO 10218-1 and ISO 10218-2, which address broader industrial robot safety requirements. The technical specification identifies four collaborative operating modes. At least one must be fulfilled, and there must also be a visual indication when the robot is operating collaboratively.
Why collaborative robot safety depends on the operating mode
The term “collaborative robot” describes a robot intended to work alongside people; it does not, by itself, explain how a particular application manages interaction. The operating mode defines the safety measure used during that interaction. In practice, the mode needs to make sense for the robot’s task, the way people enter or work in the shared space, and the expected relationship between human activity and robot motion.
The four modes set out in ISO/TS 15066 address different aspects of that relationship. Some prevent robot movement when a person enters the collaborative space. Others make the robot’s movement dependent on a person’s actions, maintain separation, or limit the effects of contact. They are distinct approaches, not interchangeable labels for a robot’s general safety features.
Four collaborative robot operating modes
Safety-rated monitored stop
In a safety-rated monitored stop, the robot stops when a person enters the collaborative space. This mode is based on stopping robot motion in response to human presence, rather than allowing the robot to continue operating alongside the person in that space.
For an application using this approach, the key operating principle is the relationship between entry into the collaborative space and the robot’s stop. The intended response should be clear in the system’s operating plan, and the collaborative state should be visibly indicated as required.
Hand guiding
With hand guiding, a person’s hand controls the robot’s motion. The human is therefore directly involved in directing movement, rather than simply working near an independently moving robot. This makes the intended interaction different from a mode in which the robot controls its own movement while a person is present.
When considering hand guiding, teams need to define how the person will guide the motion as part of the task. The mode should be understood in terms of the actual operating sequence, rather than assumed to apply merely because a worker can physically reach the robot.
Speed and separation monitoring
Speed and separation monitoring requires the robot to maintain a specified distance and speed in relation to the person. The operating approach therefore depends on both separation and robot motion: the robot maintains the specified conditions rather than relying solely on a stop or on limiting the effects of contact.
This mode makes the relationship between the human and robot positions important to the application. Engineers and integrators should ensure that the specified distance and speed are treated as requirements of the intended operating mode, not as informal assumptions about how people will behave around the equipment.
Power and force limiting
Power and force limiting uses inherent design and controls to limit impact at contact events. Unlike a mode based on keeping a person separated from a moving robot, this approach addresses the potential consequences of contact through the robot’s design and control measures.
The source of the protection matters: the mode relies on design and controls that limit impact. It should not be interpreted as a general permission for contact or as a substitute for defining how the collaborative task will operate.
Planning a collaborative application
Choosing a collaborative operating mode starts with the work process. System integrators and plant teams need to understand when people may enter the shared workspace, whether they guide the robot, how separation is maintained, and whether the application relies on limiting impact at contact. These questions help connect the selected mode to the real interaction taking place on the production floor.
- Define the interaction: Establish whether the task calls for a monitored stop, human-guided motion, monitored separation, or impact limitation.
- Connect the mode to the workspace: Consider how people and robot movement relate within the intended work environment.
- Make collaborative operation visible: Provide the visual indication required when the robot is in collaborative operation.
- Keep the standards in context: Use ISO/TS 15066 alongside the broader industrial robot safety requirements covered by ISO 10218-1 and ISO 10218-2.
These considerations do not replace application-specific safety assessment. They help teams avoid treating “collaborative” as a complete safety plan and focus attention on the operating mode that governs human-robot interaction.
Conclusion
Collaborative robot safety is achieved through defined safeguards, not simply by placing a robot in a human-occupied workspace. ISO/TS 15066 describes four operating modes: safety-rated monitored stop, hand guiding, speed and separation monitoring, and power and force limiting. At least one must be fulfilled, and collaborative operation must be visually indicated. For engineers, integrators, and plant leaders, the practical priority is to match the mode to the task and the way people will interact with the robot.
Access Official Technical PDF