Digital Andon Systems: Pulling the Cord Without the Cord

The andon's job is to make problems loud. Digital versions make them loud, routed, timed, and remembered. Here's how they work.

Written by George Munguia · Published Jul 19, 2026

The andon is lean's loudest idea: when something is wrong, the operator makes it visible immediately, and the line's support system responds. Cords and stack lights did this for decades within line-of-sight. The digital version keeps the principle and fixes the physics: visibility no longer decays with distance, and the response, not just the signal, becomes part of the system.

What digital adds to the cord

Routing: a quality concern pages the quality tech, a jam pages maintenance, a material short pages the water spider, the right responder, not whoever notices the light.
Escalation: unacknowledged calls climb, five minutes to the supervisor, fifteen to the manager, so no call dies in the noise.
The clock: raise-to-acknowledge and raise-to-resolve are measured per event, making response a managed capability instead of a hope.
Context: the call carries station, order, and machine state (from the PLC feed), so the responder arrives knowing, not asking.

The history is half the value

Every andon event is a labeled data point: where, what category, how long to respond, how long to fix. Six months of events cluster into the plant's real pareto, the station that calls for materials every Tuesday, the machine whose jams precede its failures, the shift whose calls go unanswered longest. This is the dataset that turns support staffing and layout debates into evidence (and it feeds the same ML that clusters downtime causes, see how powersports assembly plants run digital andon next to takt boards).

Rolling it out without killing it

Andons die one way: calls go unanswered, the floor learns pulling is pointless, and the system becomes furniture. Prevention is operational, not technical: staff the response before turning on the calls, publish response-time numbers weekly, and treat an unanswered andon as the failure, not the operator's overuse. Start with two or three call types (help, materials, quality), add categories after response discipline holds. And put andon on the same stations as capture (the paperless checklist), one screen the operator already touches, not a separate box (category context: connected worker technology).

Frequently Asked Questions

What is a digital andon system?

A system letting operators raise problems from the station, help, quality, materials, safety, with automatic routing to the right responder, timed escalation if unacknowledged, and a full history of every event for analysis.

How is digital andon better than lights and cords?

Physical andons signal the vicinity; digital andons page the right person, escalate unanswered calls, carry machine and order context, and record response times, making the response system measurable and improvable.

Why do andon systems fall into disuse?

Unanswered calls. Once the floor learns that pulling brings nobody, pulling stops. Successful rollouts staff the response first, measure acknowledge and resolve times publicly, and treat slow response, not frequent calls, as the failure.

What can andon history data reveal?

The plant's real support pareto: which stations call most and why, which machines' jams precede failures, where response is slow by shift. Clustered over months, it turns staffing, layout, and maintenance debates into evidence.

The Operations Brief

The best of what we publish, once a week.

Practical guides on high-production manufacturing, straight from the floor. No spam, unsubscribe anytime.

You're in. The next brief lands Monday morning.

See Harmony on your line

Harmony connects your machines, systems, and paperwork into one real-time operational layer — no rip-and-replace. See what it looks like in a plant like yours: read the CLS case study.

Book a Demo →

← Back to Resources