Designing and Commissioning Robotic Workcells

A plant-level symptom list is useful: random cycle-time variance that kills takt; repeated manual overrides during changeovers; EOAT failures that cascade into robot retrains; ambiguous HMI screens that generate operator errors; and poor documentation handed to maintenance at turnover. Those are not theoretical — they are why pragmatic engineers run a risk assessment before picking a robot or wiring a single safety input.

Contents

• How to pick the robot that hits your cycle time, accuracy, and uptime targets
• Design end-of-arm tooling so the robot isn't the weak link
• Shape the cell layout and safety systems to protect people without killing throughput
• Make PLC, robot, and HMI speak the same language (integration patterns that scale)
• Practical Application: Commissioning checklist, validation protocols, and handover deliverables
• Sources

How to pick the robot that hits your cycle time, accuracy, and uptime targets

Start from the process, not the catalog. The top-level decision variables are payload, reach, repeatability/accuracy, speed/acceleration, duty cycle / MTBF, and environmental rating (IP/cleanroom/weld cell). Global deployment trends make the business case for automation obvious — robot installs exceed half a million per year and the installed base surpasses four million units.

A practical selection workflow (do this in order and document every input):

1. Define the production requirement in measurable terms: takt (s/part), quality tolerance (mm or µm), throughput (parts/hour), shift cadence, allowable downtime, and spare-parts lead times.
2. Profile the motion: measure pick-to-place distances, orientation changes, tool-change frequency, and expected worst-case insertion forces. Record the full TCP path length and number of stops.
3. Compute a target cycle-time budget:
   • Cycle = motion_time + tooling_time + IO_time + buffer.
   • Validate with digital twin / OLP (RobotStudio, DELMIA, RoboDK). Use simulation to convert kinematics into realistic cycle times.
4. Convert cycle-time to robot specs: choose a manipulator whose joint speeds and acceleration profiles meet the simulated timing while leaving headroom for payload/inertia.
5. Check payload + EOAT + sensors + cables (total mass) against robot rated payload and examine allowable moment of inertia for the wrist. Leave a meaningful margin for peak acceleration and rework — a common integrator practice is to allow roughly 20–35% payload margin over the assembled tool + workpiece mass and to validate for inertia, not only mass.

Quick reference: robot family trade-offs

Robot type	Typical payload	Typical repeatability	Strength	Typical use cases
Articulated (6-axis)	2–2500 kg	0.02–0.1 mm	Best dexterity & reach	Welding, machine tending, assembly
SCARA	1–20 kg	0.02–0.05 mm	Fast XY pick-and-place	Electronics assembly
Delta / Parallel	<5 kg	0.05–0.2 mm	Extremely high speed	High-speed pick & place
Cartesian / Gantry	5–2000+ kg	0.01–0.5 mm	High payload & long strokes	Palletizing, large assembly
Collaborative (cobot)	0.5–35 kg	0.05–0.5 mm	Safe human proximity (limited)	Light assembly, machine tending (low force)

Source: manufacturer & industry summaries on robot families for practical sizing.

Contrarian, practical insight: don’t default to a cobot because it “avoids fences.” Collaborative operation is an application design choice, not merely a robot purchase. Use ISO/TS 15066 tools and application-level risk assessment to decide whether a collaborative mode (power & force limiting, speed-and-separation monitoring) is appropriate — many high-throughput tasks still need a fenced high-speed arm.

Design end-of-arm tooling so the robot isn't the weak link

EOAT determines whether the manipulator’s theoretical performance becomes practical performance on the floor. Common failure modes: excessive weight/inertia, poor gripping strategy (slip, crush), inaccessible sensors, and fragile quick-change interfaces.

Design checklist for EOAT:

• Define function precisely: pick points, orientations, insertion forces, cycle frequency, duty cycle.
• Calculate total payload and moment of inertia about the wrist: include gripper, vacuum cups, quick-change plate, tooling brackets, sensors, and cable chain. Treat every attached part as payload; manufacturer manuals explicitly treat externally mounted equipment as part of payload.
• Choose the gripping technology to match the part geometry: vacuum (porous parts need porous cup selection or ejection), parallel grippers (rigid predictable parts), soft/robotic grippers for variable compliance, custom jaw for nested parts.
• Add sensors to the tool: vacuum pressure sensors, part-present sensors, 6-axis F/T for insertion tasks, and proximity sensors for approach verification. Smart tooling reduces cycle failure rates and simplifies programming.
• Use a standardized tool flange and quick-change system (ISO 9409 compatible) to enable fast, repeatable swaps and reduce downtime. Quick-changers that carry power and signals cut redeployment time and errors.
• Route cables and air through the robot’s EOAT mounting or through the robot arm channels where possible to avoid snags; design modular subassemblies for repairability.
• Design for maintenance: spare jaws/cups on-site, accessible fasteners, and clear assembly drawings.

Example calculation (ballpark):

• Part: 0.5 kg
• Gripper: 0.25 kg
• F/T sensor & cables: 0.15 kg
• Total = 0.90 kg → Choose robot rated ≥1.2 kg (≈33% margin) and verify wrist inertia permissible at the intended mounting offset. Validate with the robot vendor’s inertia limits.

Real-world note: high-utilization cells use tool changers so a single robot can run multiple tasks with a 5–15 second tool swap, improving utilization and reducing capital cost per task.

Shape the cell layout and safety systems to protect people without killing throughput

Design the cell to be safe by design, then add engineered safeguards. Start every project with a documented risk assessment per ISO 12100 (limits of machinery, hazard ID, risk estimation, risk reduction). That will determine whether interlocked fencing, presence-sensing, or collaborative modes apply.

Basic guarding taxonomy and considerations (OSHA-backed):

• Interlocked barrier guard: gates with safety interlocks that stop automatic operation when opened — robust for high-energy cells.
• Fixed barrier guard: tool-access requires tools — good for high-risk, low-change operations.
• Awareness/perimeter devices (rope/paint/low rail): acceptable only after risk assessment, not for serious hazards.
• Presence sensing: light curtains, pressure mats, safety laser scanners for dynamic access — must be sized and positioned per ISO 13855 calculations (safety distance formula).

Important design callout:

Don’t treat collaboration as a product property. Design the “collaborative application” (tasks, speeds, monitored standstills, PFL) with documented risk control measures and test evidence per ISO/TS 15066 and the updated ANSI/A3 R15.06-2025 guidance.

Safety-control architecture fundamentals:

• Identify safety functions and required Performance Levels (PLr) or SIL per ISO 13849 / IEC 62061. Use PL calculations for safety-related control parts; document MTTF, diagnostic coverage, and CCF measures.
• Where modern deterministic networks are chosen, use safety-rated protocols (e.g., CIP Safety over EtherNet/IP) to carry safety I/O in the safety domain and preserve a single safety topology. GuardLogix and similar safety PLC architectures provide integrated CIP Safety and are used widely in high-availability cells. Validate device support and signatures for safety nodes.
• Calculate safe distances using ISO 13855 (S = K×T + D_DS + Z) and use measured stopping times when possible. Document the entire calculation set and measurements.

Layout rules that save rework:

• Reserve service aisles and tool-change clearances on drawings; dimension with the largest expected EOAT.
• Place E-stop and gate-reset switches in consistent, reachable locations and show them on the HMI map.
• Locate maintenance access outside the safeguarded high-speed envelope where possible.
• Design gate interlocks and resets so a manual restart requires explicit operator action and an HMI confirmation to avoid accidental auto-restarts.

Make PLC, robot, and HMI speak the same language (integration patterns that scale)

Integration patterns fall into three pragmatic archetypes:

• Hardwired I/O handshake — PLC sends Start, receives Done and Fault; simple, low-cost, deterministic for small cells.
• Fieldbus/Industrial Ethernet I/O (EtherNet/IP, PROFINET) — structured assemblies reduce wiring and improve diagnostics; use for medium-complexity cells where timing is relaxed to tens of ms. EtherNet/IP is a mature, object-oriented network widely used in discrete automation.
• High-level, data-modeled integration (OPC UA, MQTT/IIoT) — use for MES / SCADA integration, diagnostics, and digital twin synchronization. OPC UA gives platform-independent data modeling and secure transport for KPI-level telemetry.

Common orchestration decision: choose a single master of sequence. Most automotive and high-reliability cells make the PLC the sequencer (authoritative recipe and I/O timing) and the robot an intelligent actuator; exceptions exist where complex kinematic coordination or motion synchronization requires the robot controller to run the sequence and the PLC to supervise. Pick what your operations team can support.

Example PLC → Robot handshake pattern (structured-text pseudocode):

(* PLC state machine for a single robot cell *)
TYPE RobotState : (INIT, HOMED, READY, START_CMD, RUNNING, COMPLETE, ERROR);
VAR
  state : RobotState := INIT;
  Robot_StartCmd : BOOL; (* output to robot *)
  Robot_Done : BOOL;     (* input from robot *)
  Robot_Error : BOOL;    (* input from robot *)
END_VAR

CASE state OF
  INIT:
    IF SystemHomed THEN state := HOMED; END_IF;
  HOMED:
    IF ReadyForCycle THEN state := READY; END_IF;
  READY:
    IF StartRequest THEN Robot_StartCmd := TRUE; state := START_CMD; END_IF;
  START_CMD:
    Robot_StartCmd := TRUE;
    state := RUNNING;
  RUNNING:
    IF Robot_Done THEN Robot_StartCmd := FALSE; state := COMPLETE; ELSIF Robot_Error THEN Robot_StartCmd := FALSE; state := ERROR; END_IF;
  COMPLETE:
    LogCycleMetrics();
    state := READY;
  ERROR:
    TriggerAlarm();
END_CASE

Use consistent tag naming — Cell1.Robot1.Command.Start, Cell1.Robot1.Status.Code, Cell1.Robot1.Metrics.CycleTime_ms — and document the map in the functional specification.

HMI design: follow ISA-101 lifecycle and display guidance to keep screens simple, prioritize situational awareness, and minimize operator cognitive load. Don’t overload the primary operator screen; use a Level-0/1/2 display hierarchy and dedicated diagnostic screens for maintenance.

Vision & sensors: use machine vision for flexible part location and for reducing fixturing. Vision-guided robotics reduces precision requirements on fixturing and lowers EOAT complexity — integrate vision outputs into the robot TCP compensation routine. Vendors such as Cognex provide VGR toolsets and prebuilt robot drivers that simplify calibration and hand-eye transforms.

Security: treat OT network segmentation and device hardening as part of the design. Apply IEC/ISA 62443 principles for zones/conduits, access control, and device lifecycle management. Design secure update processes for robot firmware and EOAT electronics.

Practical Application: Commissioning checklist, validation protocols, and handover deliverables

This is the execution plan you will use the day the system shows up. The checklist below is compact but intentionally actionable — convert it into your live FAT/SAT protocols and attach pass/fail evidence for each item.

Pre-FAT (vendor factory checks)

• Mechanical fit & function: verify EOAT fits, flange torque, cable routes.
• Electrical: wiring continuity, correct terminal labeling, breaker sizing, control power present.
• Software: version-tagged PLC & robot projects in VCS; HMI build deployed.
• Safety: interlock wiring, safety PLC configuration exported.

FAT (Factory Acceptance Test)

• Verify sequence under dry-cycle and with low payload; measure cycle time and compare to simulated target (target tolerance ±5%).
• Safety function tests: open gates, trip light curtain, check monitored standstill, test E-stop & lockouts; record pass/fail and measured response times.
• IO mapping verification and tag table validation (PLC ↔ Robot).
• Collision & reach test (slow jog + collision detection).
• Vision & sensor calibration checks; pick success rate over a sample set (e.g., 100 picks).

SAT (Site Acceptance Test)

• Repeat FAT on site under production conditions (material, power, ambient).
• Measure repeatability with n samples (e.g., 25 positions × 5 repeats) and ensure within tolerance.
• Stress test: run for a continuous block (e.g., 8 hours) and record uptime, faults, and mean time to recover.

Validation & documentation (as-built evidence)

• Safety validation report: hazard log, PL/SIL calculation, safety function test evidence (per ISO 13849 / IEC 62061).
• FAT / SAT test report, with timestamped logs and video when useful.
• Digital twin snapshot: signed OLP program used for acceptance.
• PLC & HMI source with version, compiled binaries, README with build instructions and rollback procedure.
• Spare parts list with SKU, expected lead time, and minimum on-site stock.

Handover deliverables (minimum)

• Functional & Design Specification: one-line requirements mapped to tests.
• Control & Robot Code: commented, version-controlled, with build/deploy instructions.
• Operations & Maintenance Manual: electrical schematics, mechanical drawings (CAD), machine steps for reset/maintenance, safety interlock list, torque specs.
• Handover checklist & training records: operator and maintenance training sign-offs.
• Warranty & support contacts and recommended service schedule.

Commissioning acceptance criteria (example numeric gates)

• Throughput: measured cycle time within ±5% of simulated target across a 4-hour run.
• Quality: 99.5% first-pass yield for critical features.
• Safety: all safety functions meet PL/SIL targets with recorded test evidence.
• Availability: >95% availability during the acceptance run.

Practical tip: run a documented fault injection session during commissioning — simulate an EOAT jam, a missing part, a light-curtain interruption, and measure MTTR and operator workflows. Record and improve procedures.

Sources

Record of 4 Million Robots in Factories Worldwide — IFR World Robotics 2024 - Industry scale and recent installation statistics used to justify automation investment context.

What are the different types of industrial robots? — igus Engineer’s Toolbox (Oct 2023) - Reference for robot family trade-offs and common applications.

i4 Robot User Manual (Omron) — Installation & Payload Notes - Manufacturer guidance that externally mounted equipment counts toward payload and inertia considerations.

Bringing automation barriers down with end-of-arm tooling — OnRobot blog - Practical EOAT design considerations and quick-change tooling examples.

How to Find the Right End-of-Arm Tooling (EOAT) for Your Robots and Cobots — Automate / A3 Industry Insights - Guidance for EOAT selection and application-specific considerations.

Guidelines For Robotics Safety — OSHA - Machine-guarding methods and guidance on interlocked barriers, fixed barriers, and presence sensing devices.

What Is ANSI/A3 R15.06-2025? — ANSI Blog (Dec 2025) - Summary of the 2025 update to robot safety standards and key changes consolidated from ISO 10218.

Testing Thresholds for Collaborative Robot Safety — Automate / A3 (RIA) Industry Insights - Explains ISO/TS 15066 approaches and collaborative operation modes.

Vision Guided Robotics — Cognex product/technology overview - Vision-guided robotics use-cases and integration notes.

ISO 13849-1: Background & Update (ANSI Blog coverage) - Overview of ISO 13849 role in safety-related parts of control systems and performance level methodology.

What is IEC 62061? — 61508 Association overview - Explanation of IEC 62061 and its application to functional safety of machine control systems.

GuardLogix 5570 Controller Systems Safety Reference (Rockwell manual excerpt) - CIP Safety and GuardLogix safety architecture reference for integrating robot safety with Logix systems.

IIoT / Industry 4.0 — ODVA (EtherNet/IP) technology overview - EtherNet/IP capabilities and role in industrial network architectures.

OPC Unified Architecture (OPC Foundation overview) - OPC UA capabilities for secure, vendor-neutral data modeling and communications.

How ISA-101 Lifecycle Standard Improves Operator Effectiveness — ARC Advisory summary - HMI lifecycle and display design guidance aligned to ISA-101.

IEC 62443: Ultimate OT Security Guide — Rockwell Automation summary - OT cybersecurity principles and zone/conduit model guidance for industrial systems.

Vision Guided Robotics — Vision Systems and integration examples (Cognex/industry articles) - Practical examples of integrating vision for pick-and-place and guidance.

Benefits of virtual factory acceptance test systems — Control Engineering - Practical FAT/SAT execution tips and virtual acceptance strategies.

ISPE Guidance Documents & GAMP 5 references — ISPE - Commissioning and qualification lifecycle and GAMP reference for validated industries.

EN ISO 13855 — Positioning of safeguards (Pilz overview) - Safety distance formula and guidance for positioning presence-detection devices.

Apply these checks, document the metrics, and build the acceptance tests into the contract and control plan so the robot commissioning phase proves compliance — not just functionality — before you release the cell to production.