Robotics Automation Integration Engineer

Robotics and Automation Integration Engineer

When to Use

• Commission robot and automation cells—layout, sequence of operations, cycle time targets, recovery modes
• Integrate industrial arms, cobots, gantries with PLCs, PC control, and cell peripherals at the I/O and protocol layer
• Connect AMRs/AGVs to fleet managers, traffic zones, dock stations, and warehouse/line handoff points
• Wire safety interfaces—e-stops, light curtains, safety relays, safe torque off, reset permissives (not SIL certification)
• Map fieldbuses and industrial Ethernet—Profinet, EtherNet/IP, EtherCAT, Modbus; device profiles, I/O lists, GSD/EDS
• Configure robot OEM integration—Ethernet/IP, Profinet device, native SDK/RPC bridges, teach-pendant workflow hooks
• Integrate vision, conveyors, sortation, palletizing—trigger/handshake, reject paths, jam and fault propagation
• Define MES/WMS/ERP handoffs—order release, completion, traceability, and exception events at the cell boundary
• Run FAT/SAT integration—I/O forcing, dry cycle, production trial, punch lists, as-built documentation
• Bridge ROS/ROS2 to factory systems where used for interoperability—not full autonomy stack design

When NOT to Use

• Bare-metal MCU firmware, ISR/RTOS on chip, driver bring-up without cell integration → embedded-real-time-software-engineer
• DCS/PLC control application logic, scan-cycle determinism, historian/alarm server code → control-software-developer
• OT cyber program, Purdue segmentation, IEC 62443, passive ICS monitoring → scada-ics-cyber-security-specialist
• WMS business logic, waves, slotting, inventory allocation → wms-developer
• Autonomy AI stack, perception/planning for unmanned systems → tactical-ai-autonomy-developer
• Physics/digital twin simulation without field integration scope → simulation-software-engineer
• HIL security bench, bus fault injection for security assessment → hardware-in-the-loop-security-tester
• Multi-sensor fusion algorithms for vehicles/robots without factory cell scope → sensor-fusion-engineer
• Formal SIL/LOPA, legal safety certification, or certified risk assessment sign-off → site process safety / engineering

Related skills

Core Workflows

1. Scope and integration boundaries

Define cell boundaries, safety interfaces, protocol ownership, and RACI with controls, software, and operations.

See `references/robotics_automation_integration_scope.md`.

2. Cell architecture and safety

Lay out zones, access modes, safety device wiring concepts, and reset/recovery without merging safety and standard control.

See `references/cell_architecture_and_safety.md`.

3. Fieldbuses, Ethernet, and I/O mapping

Produce device lists, network topology, address maps, and signal dictionaries between robot, PLC, and peripherals.

See `references/fieldbuses_and_io_mapping.md`.

4. Robot, AMR, and motion integration

Integrate arms/cobots/gantries and AMR fleet handshakes—programs, registers, APIs, and motion coordination at cell level.

See `references/robot_amr_and_motion_integration.md`.

5. Vision, conveyors, and peripherals

Connect cameras, sortation, palletizing, printers, and material-handling equipment with clear fault and reject semantics.

See `references/vision_conveyors_and_peripherals.md`.

6. Commissioning, FAT/SAT, and enterprise handoffs

Execute factory acceptance, site acceptance, MES/WMS/ERP interfaces, and turnover documentation.

See `references/commissioning_fat_sat_and_handoffs.md`.

Outputs

• Integration specification — devices, protocols, IP plans, GSD/EDS inventory, ownership matrix
• I/O and signal dictionary — PLC ↔ robot ↔ peripheral mapping, scaling, debounce, interlocks
• Cell sequence diagram — modes, auto/manual, recovery, fault escalation
• Safety interface sheet — e-stop zones, STO paths, reset permissives (for safety review, not cert)
• FAT/SAT test pack — dry cycle, production trial, defect log, sign-off criteria
• Handoff package — as-built drawings, parameter exports, backup images, MES/WMS interface spec
• Commissioning runbook — power-up order, homing, first-article, change-control after go-live

Principles

• Separate safety from standard control — never merge SIS/safety PLC logic with production sequences in one undocumented layer
• Document every handshake — robot ready, part present, vision OK, conveyor clear, AMR at station
• Simulate before power — offline I/O simulation, virtual robot where OEM supports it, then controlled FAT
• Never instruct unsafe live changes — require operations and safety authority for bypasses affecting personnel
• Prefer standard fieldbuses — avoid ad-hoc serial glue when an industrial Ethernet profile exists
• Coordinate peers — route control-app depth, OT security, WMS logic, and autonomy to named skills
• ROS is a bridge, not the plant standard — use ROS/ROS2 only where explicitly required for interoperability

When to load references

Cell architecture and safety

Table of contents

1. Cell layout zones 2. Access modes 3. Safety device integration 4. Reset and recovery 5. Documentation for safety review

Cell layout zones

Produce a zone diagram linking physical areas to safety inputs and control permissives.

Access modes

Document mode entry/exit conditions and which subsystems must agree (PLC, robot controller, AMR fleet).

Safety device integration

Integration engineer delivers: device list, wiring interface sheet, signal names, expected safe state on trip—not SIL proof.

Reset and recovery

1. Identify trip cause — safety vs. process fault vs. robot alarm 2. Clear hazard — personnel out, tooling safe, AMR path clear 3. Safety reset — twist reset, OSSD clear, safety PLC acknowledge per design 4. Control reset — PLC fault ack, robot alarm reset, vision re-arm 5. Homing / re-sync — axis home, tool frame verify, conveyor clear 6. Production resume — first-cycle slow speed if policy requires

Define forbidden auto-restart conditions (e-stop pressed, gate open, vision fail).

Documentation for safety review

Provide to site safety / integrator:

• Safety IO list with device tag, function, and normal state
• Sequence diagram showing safety permissives gating motion
• Muting matrix (if any)—sensor, condition, max duration, operator presence
• STO and stop category mapping per axis/drive
• Known limitations (e.g., cobot hand-guiding only in teach mode)

Do not claim compliance with ISO 10218, ISO 3691-4, or local regulations without qualified review.

Commissioning, FAT/SAT, and handoffs

Table of contents

1. Commissioning phases 2. FAT checklist themes 3. SAT and go-live 4. MES, WMS, and ERP interfaces 5. Turnover package

Commissioning phases

Never skip safety device functional test before enabling motion at speed.

FAT checklist themes

Factory acceptance (vendor shop or integrator hall):

• [ ] I/O dictionary matches signed drawing
• [ ] Safety chain test—each e-stop, curtain, door
• [ ] Robot reach and interference check vs. model
• [ ] Cycle time measured N consecutive cycles
• [ ] Recovery from each defined fault class
• [ ] Vision pass/fail and reject routing
• [ ] AMR dock/undock with robot interlock
• [ ] HMI screens: mode, fault, reset (integration tags only)
• [ ] Backup/restore procedure demonstrated
• [ ] Spare parts list and recommended stock

Record punch list with owner and target date; block SAT only for safety-critical open items.

SAT and go-live

Site acceptance on customer floor:

• Re-verify network after transport (cable damage, IP drift)
• Re-teach or confirm frames if cell moved
• Align with site OT policies (scada-ics-cyber-security-specialist)
• Operator training on modes, resets, and LOTO
• Run at rate with customer quality sign-off
• Hypercare period—defined response times and escalation

Change control after go-live: parameter changes require revision log; robot path edits require re-FAT slice if safety-affecting.

MES, WMS, and ERP interfaces

Document message spec: OPC UA nodes, REST, MQTT, or flat file—schema, retry, idempotency, and error codes.

Integration engineer owns cell boundary; enterprise workflow depth routes to WMS/MES teams.

Turnover package

Deliver to customer operations and maintenance:

Archive media in customer CMMS or document control per site rules.

Fieldbuses and I/O mapping

Table of contents

1. Protocol selection 2. [Network topology](#network topology) 3. Device configuration 4. I/O mapping process 5. Diagnostics and commissioning

Protocol selection

Prefer one primary industrial Ethernet per cell segment; use gateways deliberately with documented latency.

Network topology

• Cell switch — managed switch with VLAN if OT policy requires; document port list
• Robot controller — often dual-port; avoid unintended loops; disable unused protocols
• PLC / PC control — scanner/adapter roles per vendor; fixed IP or DCP as policy dictates
• AMR wireless — separate from robot cable plant; coordinate handoff AP coverage with fleet vendor
• Time sync — IEEE 1588 only where required (vision sync, EtherCAT DC); otherwise document clock source

Deliver one-line diagram: IPs, device names, cable IDs, patch panel references.

Device configuration

Record firmware versions in as-built—robot, PLC, safety PLC, drives, camera.

I/O mapping process

Build a signal dictionary (spreadsheet or DB) with columns:

Group signals by handshake phase: power, enable, cycle, fault, maintenance.

Diagnostics and commissioning

• Ping and name resolution check before download
• Bus diagnostics: lost frames, device not found, wrong module
• Force table for FAT—map forces to physical pins with sign-off
• Document comm loss behavior—hold last state vs. fail-safe per signal class
• Capture Wireshark only under OT security approval (scada-ics-cyber-security-specialist)

For control-scan logic inside PLC, hand detailed loop design to control-software-developer.

Robot, AMR, and motion integration

Table of contents

1. Industrial robot integration 2. Cobot specifics 3. Gantry and external axes 4. AMR and AGV fleet integration 5. Coordination and collision avoidance 6. ROS and ROS2 bridges

Industrial robot integration

Teach pendant workflow (integration level): document job numbers, data registries used for PLC handshake, and who may alter paths after FAT sign-off.

Avoid deep motion tuning in this skill—focus on interfaces and commissioning.

Cobot specifics

• Confirm reduced mode when persons in shared space
• Speed/separation monitoring if used—sensor placement per integrator
• Hand-guiding only in authorized modes
• Application standards (ISO 10218-2, TS 15066) referenced by safety team—not certified here

Gantry and external axes

• Synchronize robot kinematics with linear/rotary external axes
• Shared estop and enable chain across drives
• Homing order documented (gantry first vs. robot first)
• Soft limits in both robot and motion controller—must agree

AMR and AGV fleet integration

Document station IDs, traffic rules, and fire/evacuation behavior with fleet vendor.

Warehouse rule depth → wms-developer; cell I/O here.

Coordination and collision avoidance

• Interlocks — robot cannot enter volume while AMR present
• Mutual exclusion zones — PLC bits or fleet API locks
• Predictable idle positions — robot park point when AMR docks
• Single source of truth for “cell clear” before motion enable

Use sequence charts for multi-device cycles; avoid hidden race conditions in parallel threads.

ROS and ROS2 bridges

Use only when required (research cells, mixed-vendor glue):

Production lines should prefer industrial Ethernet + PLC over ROS for determinism and supportability.

Autonomy algorithms → tactical-ai-autonomy-developer; physics models → simulation-software-engineer.

Robotics and automation integration scope

Table of contents

1. Purpose 2. Terminology 3. In scope 4. Out of scope 5. Roles and RACI 6. Handoffs

Purpose

Define robotics and factory automation integration boundaries—connecting robots, AMRs, PLCs, peripherals, vision, and enterprise systems into runnable production cells.

This skill covers integration design, commissioning, and acceptance—not autonomy research, WMS product logic, or OT security program ownership.

Terminology

In scope

Out of scope

Roles and RACI

R = responsible, A = accountable, C = consulted, I = informed

Handoffs

• To `control-software-developer` — scan-cycle logic, alarm models, historian tags beyond cell I/O
• To `embedded-real-time-software-engineer` — custom boards, firmware on microcontrollers in tooling
• To `scada-ics-cyber-security-specialist` — VLAN design, remote access policy, monitoring agents on OT networks
• To `wms-developer` — inventory transactions, pick/put rules, RF workflows behind AMR missions
• From mechanical/electrical — layout drawings, device bills of material, safety circuit schematics for review

Vision, conveyors, and peripherals

Table of contents

1. Vision-guided robotics 2. Conveyors and sortation 3. Palletizing and depalletizing 4. Grippers, tool changers, and utilities 5. Fault propagation

Vision-guided robotics

Deliver vision interface spec: registers, strings, or fieldbus assembly layout; timeout and retry policy.

Algorithm development for detection → vision vendor or tactical-ai-autonomy-developer if ML-heavy; this skill wires results into the cell.

Conveyors and sortation

Jam logic: stop upstream, notify robot hold, HMI prompt with physical location ID.

Sortation controls at WCS depth may involve wms-developer for destination rules; integration engineer defines PLC ↔ sorter handshake.

Palletizing and depalletizing

• Layer patterns from robot or pallet software—version pattern IDs
• Slip sheet, tier sheet, stretch wrapper interlocks
• Height check and load stability sensors
• SKU change procedure: who loads pattern, verification first cycle

Grippers, tool changers, and utilities

Map analog thresholds and debounce in signal dictionary (fieldbuses_and_io_mapping.md).

Fault propagation

Define a cell fault code list:

Avoid duplicate alarms on every device—root cause at cell supervisor level where possible.