Case studies
These are real sessions on production systems, published with the customer's identity removed. Site, controller, network, and tag names are synthetic, and hardware and third-party platform names are generalized. The reasoning, the citations, and the measured outcomes are as they happened.
Real sessions on production systems: what was asked, what the engine returned, what it got wrong, and what changed on the floor.
All studies
A Merge Releasing in Slugs: Eliminating the Code Before Touching the Line
An operator reported a merge releasing in alternating 30-second slugs instead of its configured 4:1 ratio. A byte-level diff cleared the deployed routine in minutes, a live read confirmed the configuration matched intent, and the export everyone would have reached for turned out to carry stale values that pointed the wrong way.
July 17, 2026
ReadTwo Stacked Root Causes Behind a Five-Hour Palletizer Stop
The screen read waiting on a host assignment. The host had dispatched four assignments during the stop and the controller rejected all four with the same status code. Two local causes, and the second one was created by recovering from the first.
July 13, 2026
ReadReproducing a Cloud Starvation Metric From 18 Controller Tags
The site wanted an alert when a line had been starved more than a set percentage of the last twenty minutes. The number lived in a cloud analytics stack nobody could get API access to. Every term in its formula was either a controller tag or a known constant.
July 1, 2026
ReadScoping a Ghost Fault Down From a Conveyor to One Zone
A conveyor element on the overview screen had been flashing red against a data point the running system no longer maintains. The floor wanted the whole conveyor deleted. The control logic showed one orphaned zone reference and five live ones.
June 22, 2026
ReadDecommissioned in the Host, Still Running on the Floor
A sortation lane had been retired in the warehouse host and pieces of it were still energized: some units faulted, some waiting, some running. The engineer wanted all of it showing not-enabled, least invasive option first, with cited evidence that it would not reach the rest of a large control area.
June 19, 2026
ReadOEE Was Counting Four Lanes That Were Switched Off
Four destacker lanes were physically off and still scoring as available. Finding the per-lane switch took one search. Proving that the other candidate bit commands ten units across the merge zone took a full cross-reference, and that was the part that mattered.
June 19, 2026
ReadFour Faults on the Screen, One in the Controller
An operator listed four faulted conveyor zones off a supervisory screen and asked why they were all down. The tag names did not exist in the controller, the first hypothesis was wrong, and the live read overturned the premise of the question.
June 19, 2026
ReadA Cross-Controller Feed Permit: 8 Minutes by Hand, 20 Seconds Traced
An engineer knew a 24 V output told an upstream conveyor it was safe to feed. They did not know the tag, the routine, or the conditions, and the answer crossed a controller boundary. They had been searching for eight minutes when they asked, which gave the session a measured baseline.
June 18, 2026
ReadReading an OEE State Machine Out of a Vendor Instruction Body
An engineer asked how a conveyor's OEE state is calculated. The routine they were reading only calls the instruction that decides it. The state machine sits inside three vendor add-on instructions, among 148 in a 112 MB export, and the rule that separates blocked from faulted is a single alarm-code threshold.
June 11, 2026
ReadHave a system like this?
These sessions started with an engineer asking a question about a running plant. If that sounds like yours, we will walk your controllers with you.