Cobots in auto assembly require rigorously engineered safety, not hype. This post breaks down how standards like ISO 10218, ISO/TS 15066, and EN ISO 13849-1 drive collaborative cell design. We explore practical architectures for sensor fusion, real-time speed and separation monitoring (SSM), and functional safety implementation, showing how to validate and continuously audit safety systems to ensure robust human-robot collaboration on the factory floor.
All of the engineering principles in Part 1 apply directly in the UK, but they sit inside a specific legal and standards framework: the Supply of Machinery (Safety) Regulations 2008 at the point of supply, the Provision and Use of Work Equipment Regulations 1998 (PUWER) in use, and the UK implementations of the core robot and functional‑safety standards (BS EN ISO 10218‑1/‑2 and EN ISO 13849‑1). Part 2 explains how a cobot cell that is already engineered around ISO 10218, ISO/TS 15066 and EN ISO 13849 is packaged, documented, and operated so that it can be defended to HSE and internal governance as compliant UK work equipment on a live auto assembly line.
Two core UK regulations frame how cobot cells are supplied and used on auto assembly lines:
HSE’s review of machinery safety standards highlights ISO 10218 and EN ISO 13849 as key technical references for demonstrating that cobot cells supplied under SMSR and operated under PUWER have been engineered and validated to an acceptable standard of safety.
You can even express the regulatory split in code, to drive plant‑side automation around documentation and checks:
#Non-legal, illustrative model of UK machinery duties.
from enum import Enum
class Regime(Enum):
SMSR = "Supply of Machinery (Safety) Regulations 2008"
PUWER = "Provision and Use of Work Equipment Regulations 1998"
MACHINERY_DUTIES = {
Regime.SMSR: [
"EHSR compliance demonstrated (e.g. via BS EN ISO 10218, EN ISO 13849-1).",
"Technical file compiled (risk assessments, PL calcs, drawings, test reports).", "UKCA/CE marking and Declaration of Conformity/Inc. issued.",
],
Regime.PUWER: [
"Equipment suitable for intended use and environment.",
"Planned inspections and maintenance for guards, scanners, E-stops, safety logic.", "Operators trained and safe systems of work in place.",
"Modifications trigger updated risk assessment and, if needed, revalidation.",
],
}
In a real system, a compliance dashboard or CI‑like gate for safety changes can read a structure like this and enforce that all SMSR and PUWER artefacts are present before a cobot cell is released or modified.
The global standards discussed in Part 1 map directly to British and European publications:
As a result, UK auto assembly projects generally write risk assessments, safety architectures, and validation reports explicitly against BS EN ISO 10218‑1/‑2 and EN ISO 13849‑1, citing ISO/TS 15066 for detailed collaborative limits and test methodology when justifying PFL and SSM design choices.
Applying the earlier engineering content in a UK context means layering these standards and regulations on top of the global design.
You can represent the PLr mapping in configuration to drive both design and validation:
#Example (non-safety) config fragment for a UK cobot cell
cell_id: "BODY-IN-TRIM-CELL-07" standards: robot: "BS EN ISO 10218-1/2:2025" safety_controls: "EN ISO 13849-1:2015" collaboration_support: "ISO/TS 15066 (supporting)" safety_functions:
name: "SSM stop on zone violation" plr: "d" category: "3" inputs: ["scanner_front", "scanner_side", "robot_position"]
name: "Safe limited speed in collaborative space" plr: "d" category: "3" inputs: ["robot_encoder_safety", "safety_plc_mode"]
name: "PFL enforcement for trim install" plr: "d" category: "3" inputs: ["joint_torque_safety", "speed_limit_profile"]
This sort of structured definition makes it easier to prove, during audits, that each function has an explicit PLr, category, and linkage to specific sensors and safety logic.
In other words, the technical content of the original blog;ISO 10218, EN ISO 13849, ISO/TS 15066, sensor fusion, real‑time safety decisioning, and auditability;remains valid, but a UK deployment must explicitly connect each of those design choices to BS EN implementations of the ISO standards, SMSR obligations at supply, and PUWER obligations in use to be fully defensible in a UK auto assembly environment.
Seen from a UK perspective, the “rise of cobots” in auto assembly is only sustainable if every station has a traceable safety case: design to BS EN ISO 10218 and EN ISO 13849‑1, conformity under the Supply of Machinery (Safety) Regulations 2008, and disciplined operation, inspection, and modification under PUWER. When those pieces are in place:and backed by real‑time monitoring and auditable safety events: collaborative robots stop being a novelty and become just another category of well‑engineered work equipment that can safely share space with people on the line.
