In short: An andon system lets an operator call for help the moment a problem appears, and escalates the call until someone responds. The lights and boards are simple; the failures happen when a wireless call is lost between the button, the board and the team leader's phone, so the network has to be designed for the andon system as carefully as the response process is.
Key Takeaways
- A missed call is worse than no button — an operator who presses andon and hears nothing assumes help is coming, so a dropped wireless message turns a two-minute fix into a stopped line.
- The response clock starts at the press — escalation from team leader to supervisor to manager runs on timers, so the network's delay and reliability set how honest those timers are.
- One network for the whole floor — andon buttons, team leaders' handhelds, the andon board and the OEE system share the same coverage problem, and a single private 5G network with priority for alarms solves it once.
In a nutshell

What is an andon system?
An andon system is a way for anyone on a production line to signal a problem straight away, so that a team leader comes to the station while the problem is still small. The word is Japanese for a paper lantern, and the practice comes from the Toyota Production System, where any worker on the assembly line can pull a cord to call for help. At Toyota's Burnaston plant in Derbyshire, as on Toyota lines worldwide, a pull does not stop the line at once; the line runs on to a fixed position at the end of the work zone, and stops there only if the problem has not been cleared. Most calls are dealt with before that point.
A modern andon system has four parts: (i) a way to raise the call, whether a cord, a button, a foot pedal or a tablet screen; (ii) a signal at the station, usually a stack light, so the team leader can see where the call is from; (iii) an andon board, a large display that shows the status of every station on the line; and (iv) an escalation rule, which moves an unanswered call up from team leader to supervisor to manager after set intervals. Many plants add reason codes (material, quality, machine, safety) so the call goes to the right person, and log every call so the data feeds into OEE and continuous-improvement work.
The principle is that problems are cheaper to fix where they start. A loose clip caught at station 4 costs a minute; the same clip found at end-of-line inspection costs a strip-down, and found by a customer it costs a warranty claim.
Why do andon calls go missing?
Andon calls go missing because a wireless call system is only as reliable as its weakest radio link, and factory floors are hard places for radio. A hard-wired andon on a fixed assembly line rarely fails; a cord, a relay and a cable to the board is about as dependable as factory equipment gets. The trouble starts when the plant goes wireless, which most now do for good reasons: cells get reorganised, lines move, and team leaders no longer stand under the board but carry a phone, handheld or smartwatch.
At that point the call has to cross two or three wireless hops. The button talks to a gateway or access point, the gateway talks to the andon software, and the software pushes an alert to a handheld that may be at the far end of the hall. Each hop has its own failure mode:
- Sleeping buttons. Battery-powered Wi-Fi buttons sleep to save power and have to rejoin the network when pressed. On a congested 2.4 GHz band that can take seconds, and occasionally fails without telling anyone.
- Steel and moving metal. Racking, presses, overhead cranes and parked forklifts block and reflect signal. A button that worked during commissioning can sit in a dead spot after a re-layout or when a pallet of steel coil is parked in front of the access point.
- Roaming handhelds. A team leader's handheld that holds on to a distant access point instead of moving to a closer one will miss or delay a push notification. Factory Wi-Fi is often tuned for laptops in offices, and roaming on the shop floor is where it is weakest.
- Shared airtime. The andon button competes with scanners, tablets, CCTV and the canteen's guest Wi-Fi. Andon messages are tiny, but they queue behind everything else when the network is busy, and a busy network usually means a busy line.
- Changes nobody tested. IT rotates a Wi-Fi password, changes a certificate or moves a VLAN, and the andon buttons, which nobody thought of as IT devices, drop off quietly.
A lost andon call looks exactly like a slow response. The operator presses, the light does not change, and the team leader never knew. The andon data then records a response time that never happened, or no call at all, and the continuous-improvement team draws conclusions from a gap in the network.
How fast does an andon call need to reach a team leader?
An andon call needs to reach a team leader within a few seconds, and it needs to arrive every time; reliability matters more than raw speed. Take a moving line with a 60-second takt time, a common pace for automotive sub-assembly. If the line runs on to a fixed stop position at the end of the station's work zone, the team leader has, at best, the rest of that cycle to arrive and judge the problem. A notification that arrives 10 seconds late has eaten a sixth of that window. One that never arrives means the line stops.
Escalation timers raise the stakes. A typical rule might alert the team leader at once, the supervisor after two minutes and the production manager after five. Those timers are only as honest as the delivery underneath them. If a third of calls reach the team leader late, the supervisor is pulled in for problems that were already in hand, and within a few weeks people stop trusting the escalations and start ignoring them.
The data involved is trivial: a station ID, a reason code and a timestamp, a few hundred bytes. Andon needs consistent delivery more than bandwidth, with an acknowledgement back to the station so the light changes colour when someone accepts the call. An operator who sees the light turn from red to amber knows help is on the way and can get on with containment; an operator who sees nothing has to keep pressing or walk off the station to find someone.
Which wireless options suit an andon system?
The right wireless option for an andon system depends on how much of the floor it has to cover, whether team leaders carry devices, and what else the network will carry. Each of the common choices has a place, and a small plant with one fixed line may need nothing more than cable.
| Option | Strengths | Limits |
|---|---|---|
| Hard-wired cord, button and stack light | Very reliable, cheap on a fixed line | Every re-layout means new cable; no alerts to phones |
| Proprietary sub-GHz radio (868 MHz) | Good range, long battery life, simple | Usually vendor-locked; buttons and receivers only |
| LoRaWAN buttons | Very long battery life, few gateways | Delivery takes seconds and is not guaranteed; weak for acknowledgements |
| Factory Wi-Fi | Already installed, cheap devices | Roaming, sleeping clients and shared airtime cause missed calls |
| Private 5G | Licensed spectrum, designed coverage, priority for alarm traffic | Higher upfront cost; needs SIM-based devices |
Sub-GHz radio and LoRaWAN are good at getting a button press from a far corner of a large hall, and plenty of plants use them successfully for simple call-for-help buttons. They are weaker once the plant wants the full loop: acknowledgement back to the station, alerts to handhelds, voice or photo from the team leader, and the call record flowing into the MES or OEE system. At that point the andon is sharing a network with everything else on the floor, and the question becomes which network.
Wi-Fi can do the job with careful design, and our Wi-Fi 6 versus private 5G piece sets out where each fits. The recurring difficulty is that factory Wi-Fi is usually shared with office-style traffic, designed for coverage rather than mobility, and changed by people who do not know the andon depends on it.
What does private 5G change for andon?
Private 5G changes three things for an andon system: the spectrum is licensed to the site, the coverage is designed for the whole floor including the awkward corners, and andon traffic can be given its own priority. In the UK, a factory can obtain an Ofcom Shared Access licence for the 3.8 to 4.2 GHz band (5G band n77), which means no neighbouring network shares the airtime and no visitor's hotspot can interfere.
Within the network, each class of traffic can be given its own quality-of-service settings, so an andon call is not queued behind a CCTV stream or a scanner upload when the line is busy. SIM-authenticated devices also avoid the password-rotation problem; a handheld or andon gateway stays on the network because its SIM is provisioned, not because someone remembered to update a pre-shared key. Handover between radio cells is built into the standard, which is what a team leader walking from one end of the hall to the other needs.
There are trade-offs. Battery-powered 5G buttons are not yet as cheap or long-lived as sub-GHz ones, so a common design keeps simple radio buttons at the station feeding a 5G-connected gateway, while team leaders' handhelds, the andon board and the tablets run directly on 5G. A private 5G network also costs more upfront than adding access points, which is why it makes most sense when the plant has several jobs for it: andon, handhelds for forklift and pedestrian safety, machine data for OEE monitoring, and the cameras for vision inspection.
How do you plan a wireless andon rollout?
Plan a wireless andon rollout by mapping where calls start and where responders walk, then proving the network covers both before buying buttons. Most andon projects are bought as software and hardware, with the network treated as already there, and the gaps surface weeks after go-live as calls that "nobody saw".
A sensible sequence for a UK plant:
- Map every station and every responder route. Include the stores, the goods-in dock and the maintenance workshop, since material and machine calls are routed there.
- Survey during a full shift. Walk the routes with a test handheld while the line runs, cranes move and forklifts park in their usual places. A survey on a quiet Sunday will flatter the network.
- Decide the escalation rule first, then the delivery target. If the supervisor is alerted at two minutes, the team leader's alert needs to arrive within seconds on every station, and the test should measure that end to end, from button press to handheld.
- Close the loop. Require an acknowledgement that changes the station light, and log both the call and the acknowledgement with timestamps.
- Treat andon devices as production equipment. Put them on a change-control list so a network change cannot silently take them offline.
Funding can help a smaller manufacturer take the first step. The Made Smarter adoption programme offers match-funded support for digital technology projects in SMEs in several English regions, and an andon system tied to OEE data is the kind of contained, measurable project those programmes tend to back.
The first test is cheap. Pick the worst station on the floor, the one behind the racking or next to the press, press the button fifty times across a busy shift, and count how many alerts arrived on the team leader's handheld and how long each took. If the answer is less than fifty, or the slowest took more than a few seconds, the andon system has a network problem to fix before it has a process problem. We are happy to run that coverage survey with you on the manufacturing floor.
