A few years ago, I sat in a senior leadership meeting that nobody wanted to be in.
A fast-moving CPG company had invested in robots to move finished pallets from end-of-line to the wrapper. It was a contained, well-defined use case. The integration was successful, the vendor signed off, and for months, it worked. Then, throughput started slipping.
The causes were unglamorous: intermittent failures in source system communication, WiFi outages, blocked paths, and communication dropouts between systems. Each issue, individually, was manageable. Together they created a pattern nobody was catching early enough. The team responded by introducing manual picks. However, this moved workers into robot operating zones beyond what the facility was designed to support, resulting in damaged sensors and robot stands, reduced robot reliability, and increased need for manual intervention.
What was missing in this process was a layer that could see across the whole system — one that could detect communication failures trending upward, flag increasing path blockages, identify the class of operator interactions generating errors, and respond before things cascaded. What the manufacturer needed was an orchestration layer.
Throughput
Vendors typically quote throughput numbers for individual systems, but they don’t look at how those systems will perform together in your specific facility, under real operating conditions. That number is determined by how well work flows across the critical path.
To manage this workflow effectively, you need orchestration. Orchestration manages the operation at the system level: pacing releases from upstream assets to match downstream capacity, assigning tasks on global priority rather than local convenience, and catching buffer buildups before they stall flow. The assets don’t change. The way work moves through them does. That difference is where the gap between the business case and the six-month review tends to live.
Reliability and Exceptions
No automated facility runs perfectly. The problem isn’t the disruption. It’s that supervisors find out when throughput has already dropped, not when the anomaly first appeared.
The reason behind this is that design teams typically spend most of their efforts on engineering the perfect path. Once a facility goes live, that ratio inverts. Exceptions — communication failures, mis-scans, blocked paths, and operator workarounds — consume a disproportionate share of daily operational effort. Without orchestration, these disruptions are handled ad hoc. Supervisors develop individual workarounds. Tribal knowledge fills the gaps. Operators start working around the system rather than with it, which is exactly how the CPG situation accelerated from a manageable reliability issue into a physical infrastructure problem.
Orchestration brings structure to exception management with standard detection patterns, automated responses where possible, clear instructions when human intervention is needed, and — critically — a log of everything. That exception data is what turns a recurring problem into a closed gap rather than a permanent overhead.
The People Cost
Supervisors in non-orchestrated facilities spend significant time negotiating conflicts between systems, manually prioritizing queues, and making calls the technology should be making. That is not a good use of experienced operational talent, and over time it contributes to burnout and turnover in ways that rarely get traced back to the automation architecture.
When orchestration is in place, supervisors shift from firefighting to flow management, maintenance teams get richer traceability data, and operators receive consistent instructions. These effects compound quietly over time — in error rates, safety metrics, and the cost of keeping good people.
The Bottom Line
The CPG company eventually invested in orchestration. It came after the compounding issue, which is the more expensive way to learn the lesson. Orchestration belongs on the table from day one — not as an afterthought once the hardware is commissioned. By then, the gap is already built in.
The companies getting the best returns from automation are not always the ones with the most advanced equipment. They are the ones who figured out how to run what they have as a system.
Ready to start building your orchestration layer? Download this whitepaper to learn best practices for designing, deploying, and scaling orchestration effectively.
