Changeover, not labor, was the real bottleneck
At a mid-volume appliance plant in southern Poland, the limiting factor on a refrigerator control-box assembly line was not nominal robot speed. It was changeover. The line produced multiple box-build variants with different cable harness routings, screw patterns, and connector positions. Manual stations handled the product mix reasonably well, but defect rates climbed on late shifts and throughput collapsed whenever a batch switched from one SKU family to another. The automation project that followed did not start with a broad digital transformation program. It started with a simple manufacturing problem: cut changeover time without sacrificing traceability or first-pass yield.
The factory chose a vision-guided cobot cell architecture around Universal Robots arms, Siemens SIMATIC PLC control, and a MES-connected recipe layer because the process required frequent reconfiguration rather than maximum payload. The key engineering question was whether collaborative robots could hold takt in a constrained assembly environment that mixed screwdriving, connector insertion verification, label reading, and in-station inspection. The answer depended less on cobot marketing claims and more on fixture design, PLC handshake discipline, and how the vision system handled cable position variability.
The process: box-build assembly with high SKU variation
The product was a control enclosure used in white-goods platforms sold across EU markets. Each enclosure required a sequence of operations:
- Placement of molded housing into a locating fixture
- Insertion and routing of pre-cut wiring harnesses
- Connector seating into designated ports
- Torque-controlled screw fastening of PCB and retention brackets
- 2D code scan and serial association
- Final visual check for connector color, wire routing, and missing fasteners
Before automation, the line ran at a takt of roughly 54 seconds on the main family and 68 to 75 seconds on lower-volume variants. Changeovers took 42 minutes on average because operators had to swap fixtures, retrieve printed work instructions, verify part presentation bins, and perform first-piece quality confirmation. The plant’s OEE losses were concentrated in three buckets: micro-stoppages from misplaced harnesses, rework due to incomplete connector seating, and planned downtime during SKU transitions.
Those constraints made a conventional hard-automation approach unattractive. A dedicated indexed assembly machine would have delivered lower cycle time on the highest-volume SKU, but it would also have locked the plant into a narrow product envelope. With annual model revisions and retailer-specific configuration changes, the economics favored flexible automation with software-driven recipes.
Why cobots made sense here—and where they did not
Universal Robots cobots were selected for two reasons: deployment footprint and rapid variant teach-in. In this application, payload was modest, with the heaviest handled component below 3 kilograms, and required repeatability was within the range needed for screw presentation and pick-and-place tasks when backed by mechanical guidance features in the fixture. The cobots were not expected to force-fit misaligned parts or perform high-force insertion. That distinction is important. The successful deployment came from assigning the robots only the tasks they could execute consistently:
- Picking housings and subcomponents from structured trays
- Presenting a servo screwdriving spindle to programmed coordinates
- Holding a smart camera at repeatable inspection angles
- Transferring finished enclosures to a downstream conveyor
Operations with higher uncertainty remained either fixture-assisted or human-supervised. Harness routing, for example, used poka-yoke nest geometry and a machine vision confirmation step rather than free-space robotic cable manipulation, which would have added complexity and failure modes. This was a practical factory decision, not a technology compromise. In mixed-model electronics-adjacent assembly, the lowest-risk automation strategy is usually to automate part stabilization, fastening, and verification before attempting dexterous flexible-part handling.
Cell architecture: Siemens PLC at the center, vision at the edge
The line was built around a Siemens SIMATIC S7 PLC controlling station logic, interlocks, and conveyor zoning. A Siemens HMI exposed recipe selection, maintenance diagnostics, and Andon messages. The MES layer pushed production orders, serial numbers, and variant recipes into the PLC, while traceability data flowed back upstream after each assembly step.
The cobots did not operate as isolated islands. Each robot cycle was governed by explicit PLC handshakes:
- Part present confirmed
- Correct recipe loaded
- Fixture clamped and safe
- Screwdriver ready and torque program matched
- Vision inspection result pass/fail
- Serial number assigned and logged
This matters because many underperforming robot cells fail at system boundaries, not inside the robot program itself. In this plant, the decisive engineering work was around state management. If the camera failed to validate connector seating, the PLC blocked screwdriving. If torque data came back out of tolerance, the MES record flagged the serial and diverted the part to a rework lane. If a recipe mismatch appeared between scanned work order and station configuration, the line could not restart until the discrepancy cleared. That approach reduced the chance of building the wrong variant faster than any robot speed increase would have.
Vision came from industrial smart cameras mounted in fixed positions plus one camera carried by the cobot for angled inspection. The fixed cameras verified housing orientation, connector color sequence, and presence/absence checks. The robot-mounted camera handled close-up confirmation of difficult-to-see retention clips. Lighting design was critical: diffuse dome lighting solved glare from glossy plastic covers, while coaxial illumination improved contrast on laser-marked data matrix codes.
The fixture did more than the robot
The most underrated element in the project was not the cobot arm or the camera. It was the modular fixture. Engineers created a base nest with quick-lock change plates, pneumatic locators, and encoded variant identification. Once a change plate was inserted, the fixture transmitted its variant ID to the PLC, which cross-checked it against the MES recipe. That reduced the chance of a physical setup mismatch during changeover.
The fixture also constrained cable paths using interchangeable guides matched to harness families. Instead of asking the cobot to route every wire precisely, the system placed the harness into guided channels and then used vision to validate final position. This hybrid design delivered most of the quality benefit at a fraction of the complexity of full robotic harness manipulation.
The result was a changeover reduction from 42 minutes to 11 minutes. Most of that gain came from three design decisions:
- Tool-less fixture plate exchange under 3 minutes
- Automatic recipe load from MES after variant scan
- Elimination of paper instructions and manual first-piece setup checks
Cycle time and uptime: what actually changed
On the highest-volume SKU family, the automated cell reached a sustained cycle time of 47 seconds after stabilization, down from 54 seconds manually. On low-volume variants, cycle time improved less dramatically, from roughly 70 seconds to 58–61 seconds, but line balance improved because quality checks became more consistent. The bigger win was uptime behavior. Before the project, micro-stoppages linked to missing connectors or incorrect screw programs were frequent and difficult to diagnose. After integration, every stop had a coded reason in the PLC and HMI.
Three-month post-launch data showed:
- First-pass yield: improved from 96.1% to 98.7%
- Average changeover time: reduced 74%
- Unplanned downtime: reduced 31%
- Rework related to connector seating and missing fasteners: reduced 63%
These numbers are more realistic than the dramatic labor-savings claims often attached to collaborative robotics. The cell still required operators, especially for replenishment, exception handling, and low-volume engineering changes. But output became more predictable, and quality costs fell in a way finance could measure.
The economics: flexible automation works only if utilization is protected
The capital cost was not trivial. A two-cobot cell with screwdriving, vision, modular fixtures, guarding, conveyors, PLC integration, and MES connectivity can easily cost far more than the robot arms alone suggest. In projects like this, end users that budget only for robots usually understate real installed cost by a wide margin. The major cost blocks were integration engineering, fixture design, torque tools, safety hardware, and production validation.
For this plant, the business case worked because the cell served a broad SKU range and ran across multiple shifts. The payback model included:
- Reduced rework labor and scrap exposure
- Lower changeover losses
- Deferred hiring on a constrained labor market
- Higher line availability during seasonal peaks
- Traceability improvements that reduced warranty investigation time
Maintenance planning was equally important. The team scheduled weekly camera lens cleaning, monthly end-effector inspection, and torque tool calibration intervals linked to cycle count rather than calendar only. Spare parts strategy focused on high-failure, low-cost components first: vacuum cups, cable sets, connector blocks, and lighting units. Plants that automate flexible assembly often focus too much on robot MTBF and too little on peripheral reliability. In practice, lights, feeders, connectors, and tooling generate a large share of stoppages.
For manufacturers evaluating a similar cell, this robot TCO calculator is a useful starting point because it forces installed-cost and utilization assumptions into the same model rather than treating robot purchase price as the main variable.
What the integrator had to solve before launch
The difficult part was not getting the robot to move. It was making the station recover gracefully from faults. In one early trial, a partially seated connector passed mechanical placement but failed visual validation. The initial logic forced a full cell reset, costing several minutes. Engineers later added a localized recovery routine: the PLC held the pallet, prompted the operator through an HMI check, and resumed without resetting the entire station if the error remained contained. That single software improvement materially improved effective throughput.
Another challenge was recipe governance. With variant-heavy assembly, uncontrolled program edits can become a hidden source of downtime. The plant therefore locked robot and vision parameter changes behind engineering authorization, with recipe versions synchronized between MES and station PLC. That prevented drift between the digital definition of a product and the physical station configuration.
What this deployment says about cobots in real factories
This Polish appliance deployment is a good reminder that collaborative robots perform best where product variation is high, payloads are modest, and process discipline matters more than raw speed. They are not a universal answer for assembly automation. In high-force insertion, very short takt packaging, or heavy material handling, conventional industrial robots or dedicated machinery still win. But in mixed-model box build, the combination of modular fixturing, machine vision, torque traceability, and PLC-managed recipes can unlock a very specific advantage: fast changeovers without surrendering control of quality data.
The deeper lesson is that successful industrial robotics projects are usually won in the interfaces between systems. PLC logic, MES recipe integrity, fixture design, lighting stability, and maintenance routines often determine ROI more than the robot brand. Plants chasing flexibility should pay less attention to headline robot specifications in isolation and more attention to the production logic surrounding them. That is where the 31 missing minutes of changeover were really found.
