Speed and Separation Monitoring (SSM) is one of the four collaborative operating modes defined in ISO/TS 15066 for industrial cobots. Instead of a fixed safety cage, the controller continuously computes the minimum protective separation distance Sp required between the human and the robot for the robot's current commanded speed, and never lets the robot move faster than the speed that keeps the real separation D at or above Sp:
S_p(v_r) = v_h·(T_r + T_b) + v_r·T_r + v_r² / (2·a_r) + C
v_h human approach speed (default 1.6 m/s in the standard)
T_r system reaction/reset time (sensing + processing delay)
T_b robot braking-onset time (folded into T_r here)
v_r robot's current speed
a_r robot's braking deceleration once a stop is triggered
C intrusion distance (how far a limb can reach before detection)
Because Sp grows with vr (linearly from reaction time, quadratically from the stopping distance), the simulator inverts the formula every frame: given the live measured separation D, it solves the quadratic for the largest vr that still satisfies Sp(vr) ≤ D, clamped to [0, vmax]. That solved value is the commanded speed you see the arm actually move at — the closer the worker gets, the smaller the quadratic root, the slower (and eventually zero) the robot moves, exactly as a real SSM-rated cobot controller behaves.
- vh / Walk toward / away — moves the human avatar and sets the assumed worst-case approach speed used in the formula.
- Tr — a slower sensor/control loop demands more standoff distance even at the same speed.
- ar — weaker brakes (small ar) blow up the vr²/(2ar) term, shrinking the safe speed fast.
- vmax — the ceiling the controller is allowed to command when nobody is nearby.
Real deployments use this exact calculation with lidar or 3D time-of-flight cameras tracking worker position at 20–50 Hz, re-solving Sp every cycle — it is the mathematical basis for cobots like the Universal Robots UR-series and KUKA LBR iiwa running SSM-mode line-side, without any fixed fence.