Universal Robots Collaborative Robots

UR Reality

Universal Robots ships six current-generation arms. The UR3e (3 kg payload, 500 mm reach) targets benchtop and laboratory work. The UR5e (5 kg, 850 mm) and UR10e (12.5 kg, 1300 mm) cover the bulk of small-and-medium-manufacturing pick-and-place, machine-tending, and assembly applications. The UR16e (16 kg, 900 mm) extends payload for screwdriving, palletizing of heavier packages, and end-of-arm tooling that itself weighs several kilograms. The UR20 (20 kg, 1750 mm) and UR30 (30 kg, 1300 mm) — the most recent additions — push the platform into pallet-scale logistics and heavier assembly tasks that were previously the province of fenced industrial robots.

All six arms run PolyScope, the UR teach-pendant runtime, which exposes a single programming surface across the line and supports URCap extensions from a sizable third-party integrator ecosystem covering grippers, vision systems, force/torque sensors, conveyors, and application-specific software (Robotiq, OnRobot, Schmalz, MiR for mobile-base composition, and several hundred others). Teradyne has owned the company since 2015, and the strategic context is acquisition-portfolio coordination with Mobile Industrial Robots (MiR) and the broader Teradyne automation thesis.

Safety today is governed by ISO 10218-1/-2 (industrial robot safety) and ISO/TS 15066 (collaborative-robot specification, including biomechanical force and pressure limits). UR arms are designed for PFL (power-and-force-limited) operation per 15066, and integrators routinely deploy them in collaborative cells without perimeter fencing. The architectural reality, however, is that the safety mode is established at integration time by a risk assessment specific to that cell, that tooling, and that workpiece. Changing the task — different payload, different end-effector, different human proximity — requires re-running the risk assessment and frequently re-validating the cell. Mode is a deployment-time property, not a runtime property.

Architectural Fit

Governed actuation models the arm as a state machine over actuation modes, with each mode bound to a declared commitment that specifies the supervisory regime, the force and speed envelope, the human-proximity assumptions, and the auditable record the cell must produce. The modes are graduated: manual hand-guiding under direct operator control; power-and-force-limited collaborative operation per ISO/TS 15066; speed-and-separation-monitored operation with vision or LiDAR human-detection; and fenced or guarded high-speed operation when no human is within the monitored zone. Transitions between modes are themselves commitments — the arm does not silently shift from PFL to high-speed; it commits to a transition, the supervisory layer settles the commitment, and the new mode is entered with its envelope in force.

For a UR arm, the substrate composes naturally with PolyScope's existing safety configuration. Today PolyScope supports safety planes, joint limits, tool-flange force limits, and reduced-mode triggers; governed actuation reframes these as the constituents of declared mode-commitments rather than as standalone configuration. A URCap that surfaces governed-actuation commitments would let an integrator declare, for a given cell, the set of modes the arm is permitted to enter, the conditions under which each mode is admissible, the supervisory inputs that gate transitions, and the audit record that each transition produces. Risk assessment becomes a declaration the cell carries, not a binder the integrator files.

The emerging EU AI Act provisions for high-risk industrial systems and the parallel updates to ISO 10218 (the 2025 revision tightening the integration-and-safety boundary) both point toward exactly this kind of declared, auditable, mode-bound operation. Governed actuation is the architectural shape these regulations imply; UR's PolyScope is the runtime where it can be expressed without rebuilding the platform.

UR-Specific Fit

Universal Robots is positioned to absorb governed actuation more easily than any of the larger industrial-robot incumbents. Three properties converge. First, PolyScope is a single runtime across the entire arm line, so a substrate change propagates uniformly from UR3e to UR30 rather than fragmenting across product families. Second, the URCaps ecosystem is structurally ready for substrate-level extensions: integrators are accustomed to declaring capabilities through URCap manifests, and governed-actuation commitments are a natural extension of that declarative model. Third, the deployed base spans precisely the application classes — laboratory, SME manufacturing, light logistics — where regulators are tightening collaborative-mode requirements fastest and where cell reconfiguration is most frequent.

The Teradyne ownership context matters here. Teradyne's automation thesis is that the bottleneck to industrial-robot adoption in SME and mid-market segments is integration cost, not arm hardware. Governed actuation directly attacks integration cost by making cell reconfiguration a declarative change against a known substrate rather than a re-engineering exercise. The MiR mobile-robot composition is a second axis: a UR arm on a MiR base operates across multiple physical zones, each with potentially different supervisory regimes, and the governed-actuation primitive is what lets the combined system commit to an admissible mode at each zone without per-zone manual reconfiguration.

Competitively, UR's larger industrial peers — FANUC, ABB, KUKA, Yaskawa — operate on heterogeneous controllers with separate collaborative product lines (FANUC CRX, ABB GoFa/SWIFTI, KUKA LBR iiwa/iisy, Yaskawa HC). A substrate change on those platforms requires per-line work. UR's single-runtime position is the architectural lever, and governed actuation is the substrate that uses it.

UR Position

Universal Robots gains, under governed actuation, an architectural substrate that converts the cobot's defining property — safe operation alongside humans — from a per-cell certification into a runtime commitment carried by the arm itself. The product implications run across the line. UR3e gains a substrate fit for laboratory and pharmaceutical applications where mode discipline is regulatory rather than industrial. UR5e and UR10e gain a deployment substrate that lets a single arm move between collaborative-mode pick-and-place and speed-and-separation high-throughput operation as workpiece flow varies. UR16e gains a screwdriving and palletizing substrate where transition between hand-guided teaching and PFL execution is a settled commitment. UR20 and UR30 gain the substrate that legitimizes their entry into pallet-scale logistics: the larger payload makes mode discipline mandatory, and governed actuation provides it.

For Teradyne, the strategic position is that governed actuation differentiates the UR platform on an axis the larger incumbents cannot match without multi-year controller convergence work. For the URCaps ecosystem, governed actuation creates a new class of integrator value: cells that declare their mode regime are easier to commission, easier to audit, and easier to reconfigure, which is exactly the cost surface integrators sell against.

The architectural commitment is to treat actuation mode as a settled, auditable property of the arm at runtime rather than a deployment-time configuration choice. Universal Robots' single-runtime architecture, declarative URCap ecosystem, and SME-facing deployment posture make it the natural substrate adopter; ISO 10218, ISO/TS 15066, and the EU AI Act make the substrate increasingly the regulatory expectation.

Closing

Universal Robots already carries the architectural properties — single runtime across the arm line, declarative integrator ecosystem, and a deployed base concentrated in the regulatory-tightening segments of cobot use — that make governed actuation a natural fit. The primitive reframes mode as a runtime commitment rather than a deployment-time configuration, with graduated modes from hand-guiding through PFL through speed-and-separation through fenced operation, each bound to declared supervisory and audit commitments. Adopting it preserves UR's existing PolyScope and URCaps surface while giving integrators, end users, and regulators a single substrate to declare against.