No items found.
Every plant runs on the same quiet gap. When a machine stops on Line 3, the operators standing next to it know instantly, but the supervisor in the tier meeting, the maintenance tech two aisles over, and the plant manager off-site don't find out until minutes, sometimes hours, are gone.
Closing that gap is exactly why an andon system exists. An andon system is a real-time signaling method that alerts operators, supervisors, and maintenance to production or quality issues the moment they happen — visual or auditory signals, mobile notifications, or both — so the right person can respond fast.
The real question isn't whether to run one, but how: keep proven light towers, layer on andon software that pushes alerts to phones, or run both. This is a practical look at where each one wins and where each one breaks down. The measures: response speed, alert reach, escalation, accountability, and fit for high-mix, multi-line floors.
Key takeaways
- The core difference is simple: andon lights are line-of-sight and instant for people on the floor, while mobile alerts reach the right person anywhere, on any device, with context attached.
- Mobile alerts extend response beyond what anyone can see from the line. A plant manager with text alerts turned on knows the moment a machine goes down unexpectedly, then reviews the uptime graph the next morning to walk through what happened with the supervisors.
- Faster, routed response pays off. One team working across production, finance, and maintenance cut downtime from 6.8 hours/day per machine to 3.4 hours/day per machine over five months — a 50% cut on the same floor, with the same people.
- Most modern floors run both. They pair on-floor visual signals with software-driven escalation so nothing gets lost between shifts or across sites.
What an andon system does on the modern factory floor
An andon system makes production and quality problems visible the instant they happen, so operators, supervisors, and maintenance can act fast. That's the whole job: the people who can fix it find out while they can still do something about it. The rest is how the signal reaches the team.
The concept traces back to lean manufacturing and the Toyota Production System, where surfacing a problem the moment it appeared, rather than letting it hide, was the point. That floor-level heritage still holds.
One common misconception worth correcting: andon doesn't always mean the line stops immediately. The signal's job is to surface the issue and pull help. The actual response, whether to stop, adjust, or escalate, depends on the situation.
Think of it as a loop: make the problem visible, pull the right help, then act. A modern andon system can read a machine's own heartbeat — its live electrical signature — so the team knows what's actually happening instead of waiting for someone to notice. That same job, surfacing the problem and getting the right person to it, can be done two ways: by lights or by mobile alerts. Start with the lights.
Traditional andon lights: where visual signals still work best
A classic setup is familiar for good reason: stack lights, tower lights, andon boards, pull cords, sometimes a horn. It's simple, and simple survives busy shifts.
The case for lights is simple. They give instant awareness to anyone with line of sight. No device, no login, no app. Operators read them at a glance: green, yellow, red. And when hands are full and the floor is loud, that glance is often faster than any notification.
Lights are strongest when:
- The work happens in a single cell or a tightly grouped area.
- It's a manual assembly station where operators are always present.
- The people who need to respond are already within sight of the machine.
- You want simple status that needs no training.
Well-placed floor visuals genuinely earn their spot in that context. But a light only reaches people who can see it, and it carries status but no context. It tells you something stopped. It can't tell you why, how often, or whether the same issue is brewing on another line.
Mobile andon alerts: how software extends escalation beyond the line
Software sends the signal to the right person on their phone — by SMS, email, or app — the moment a machine goes down, then routes it up the chain if no one responds. This reaches the people who aren't in line of sight. On any given shift, that's most of your leadership.
Building escalation paths for chronic stops. Recurring stops are where software can help most. A fifth micro-stop on Line 2 isn't something anyone can be expected to catch by eye. Andon software routes it to the right role, then escalates up a defined chain if it isn't resolved within a set time. No issue sits idle waiting for a glance. That routing is often what wins team buy-in in the first place:
It was plug and play. We were live on Guidewheel a day or two after receiving the sensors. We set up alerts and the team started receiving emails and text messages about issues they needed to know about. That was the aha moment that really got the team bought-in.
Director of Manufacturing at a building products manufacturer
Triggering andon from real-time machine signals, no manual pull. A modern andon system can fire off the machine's own electrical signature, its live heartbeat, instead of waiting for an operator to notice a stop. An Integrated Operating Platform like Guidewheel clips a sensor onto any machine's power line — legacy press or brand-new line — and reads its state, so your team knows the machine is down the moment it happens, without anyone having to pull a cord. Getting live is fast, too: one Fortune 500 automotive manufacturer reported setup took about 40 minutes to get sensors installed and data flowing. That speed matters, because the problem is real: a 30-second fix can cost a full day when nobody knows the machine is down.
Mobile alerts also capture a full event log with timestamps, which is where the accountability difference shows up.
Lights vs. mobile alerts: comparing response speed, visibility, and accountability
The trade-off, plainly. The cost on the mobile side is setup: someone has to get devices into hands and agree who answers which alert. A light asks nothing of you but a glance.
Andon lights vs. mobile alerts at a glance
| Factor | Andon Lights | Mobile / Digital Alerts |
|---|---|---|
| Visibility range | Line-of-sight only | Anywhere, any device |
| Who sees the alert | People near the line | Operators, supervisors, maintenance, off-site managers |
| Context | Color-coded status | Root cause, history, suggested action |
| Escalation | Manual, walk over or call | Automatic, role-based routing |
| Response speed | Instant for those present | Instant for the right person, regardless of location |
| Accountability / data capture | None | Full event log with timestamps |
| Fit for remote supervisors | Poor | Strong |
Teams running Guidewheel get the mobile side of this table: instant SMS and email alerts, plus live machine status from wherever they are.
On accountability, digital alerts create a record the team can actually act on later, which a light simply can't. The record isn't there to check up on anyone. It's there so the same argument doesn't have to happen twice.
Guidewheel has made it very easy to see downtime. I have text alerts turned on and am notified when a machine is down unexpectedly. When I check the uptime graph in the morning I am able to question why the machine was down and work with the supervisors to improve training to avoid downtime in the future.
Assistant Plant Manager at an injection molding manufacturer
Each does a different job well. And each starts to strain at scale in different ways.
Where each approach breaks down in high-mix, multi-line operations
Where lights break down at scale. Picture a floor with many lines and frequent changeovers, common in plastics and packaging, steel and metals, or consumer goods. When 15 towers are lit at once, nobody can triage by glance, and because nothing gets logged, Monday's tier meeting turns into a debate about what actually happened. A missed light isn't inattention. By the time anyone looks up, the line has already moved on, and the only record left in the room is memory.
Where mobile alerts break down. To be fair, software has its own failure modes. When an alert fires on every micro-stop, it stops meaning anything — that's alert fatigue, and it's a setup problem, not an operator problem. The same thing happens when escalation routes point at the wrong role, or when an alert arrives with nothing but a timestamp. The fix is smarter alerts, carrying context, routed to the right role.
Side by side, the failure modes look like this:
| Andon Lights | Mobile Alerts |
|---|---|
| Many lines lit at once, no way to triage | Every micro-stop pings the team, causing fatigue |
| Large or partitioned plants, no line of sight | Escalation routes point to the wrong role |
| Off-shift and multi-site leaders see nothing | Alerts arrive with no context to act on |
| Nothing logged, so meetings become debates | Volume drowns out what actually matters |
When a hybrid andon system makes more sense than choosing one or the other
On most modern floors, the smartest move is a hybrid andon system: keep the physical light for instant on-floor awareness, and add mobile alerts so the right support arrives fast with the right context, whether they're two aisles away or at another plant.
The division of labor is clean. The light handles the person nearby who needs to know now. The mobile alert handles the right person anywhere who needs context, with escalation if ignored. They cover each other's gaps.
Walk one stop end to end. A stack light flags Line 4 for the operator. The same machine-signal trigger fires a mobile alert to the maintenance tech and logs the event. If no one responds inside the set window, it escalates to the supervisor. The plant manager sees it on the shared Scoreboard and can walk through it with the shift the next morning. And because the fix lands in minutes instead of hours, there's less scrap, fewer wasted run-hours, and less energy burned per part.
You don't have to replace your light towers to modernize. You add a lightweight andon software layer on top, start with one bottleneck line, and prove it there before you commit to the whole floor.
Key questions to ask before investing in andon software
How do you measure response time to machine stops? Measure from the moment the machine stops to the moment the right person acknowledges and acts. That takes a system that timestamps the stop on its own and logs the response, so your team can track it and improve it shift over shift.
What to ask a vendor:
- Does it trigger automatically from real machine signals, or does it still rely on a manual pull?
- Can it send instant SMS and email alerts, and route them to the right role?
- Does it escalate automatically if the first person doesn't respond?
- Does it timestamp every stop so you can measure and improve response time?
- Does it show real-time machine status from anywhere, for cross-shift and multi-site leaders?
- Does it give operators and supervisors a shared Scoreboard so everyone sees the same numbers?
- Does it capture downtime tags and root cause for faster action and better tier meetings?
- How fast can it go live, and does it work on any machine regardless of age, without PLC integration or IT lift? With Guidewheel the sensor clips on in about 2.5 minutes, and teams are often live the same day.
Every facility has different goals, materials, and operating realities, so use these as reference points for your own floor. The move is the same: pick your biggest bottleneck line, add the alerts, and measure the response-time improvement in weeks.
Start closing the response gap on your floor
The plants that respond fastest aren't the ones with the most lights. They're the ones where the right person knows the moment something stops, with enough context to act. If that's what you're after, an Integrated Operating Platform like Guidewheel clips onto any machine, fires instant alerts, and gives your whole team the same real-time machine truth, without disrupting what already works.
Ready to see it on your bottleneck line? Book a demo and watch how fast machine signals turn into routed, accountable response.
Frequently asked questions
What is andon software?
Andon software is the digital layer of a modern andon system. It gives your team real-time machine visibility and alerts they can act on fast to cut downtime. Instead of relying only on a physical light someone has to see, it flags the issue and routes it to the right person. They hear about it on whatever device they have and can act on it, and every stop leaves a record of what happened.
Do you need andon lights if you have mobile alerts?
Not always, but many plants keep both because they do different jobs. A physical light gives instant, line-of-sight awareness to anyone at the machine, while mobile alerts reach the right supervisor or maintenance tech anywhere with context attached. The light tells whoever's standing there. The alert, plus a shared Scoreboard, keeps operators, supervisors, and off-site leaders on the same numbers.
How long does it take to deploy andon software?
Days, usually. One team was live on Guidewheel a day or two after receiving the sensors, while another reported setup took about 40 minutes to get sensors installed and data flowing. From there, teams turn on alerts and start using real machine data with operators and supervisors right away.
Can andon software send SMS and email alerts automatically?
Yes. Guidewheel includes instant SMS and email alerts for downtime response, sent automatically the moment a machine goes down. Alerts can be routed to the right role and escalated up the chain if the first person doesn't respond, so no issue sits idle waiting for someone to notice it.
Can andon software show real-time machine status remotely?
Yes. Guidewheel provides real-time machine status from anywhere, so supervisors and plant managers can see what's happening whether they're on the floor, in the office, or at another site. Remote access and reporting support cross-shift handoffs and multi-site management from a single source of truth.
About the author
Lauren Dunford is the CEO and Co-Founder of Guidewheel, the FactoryOps platform helping manufacturers find hidden capacity and hit their productivity and sustainability goals using lightweight, plug-and-play machine data. A Stanford graduate and World Economic Forum Technology Pioneer, Lauren champions a practical, operator-first approach to manufacturing digitization, proving value in weeks rather than years by empowering the people closest to the work.
