The Andon system market has evolved significantly over the past decade. What started as cord-pulls and stack lights has branched into four distinct product architectures — each with different strengths, limitations, and ideal use cases.
"We evaluated multiple options before settling on our approach. The key was understanding what type of system actually fits our facility, not just which one had the best demo."This guide maps the current landscape of Andon systems available for manufacturing, organized by architecture type, so you can identify which category fits your plant's needs before evaluating specific vendors.
The Four Types of Andon Systems Available Today
1. Traditional Wired Systems
The original Andon approach: cord-pulls, hardwired stack lights, and simple visual indicators mounted on production lines.
How they work: Operators pull a cord or press a hardwired button, which illuminates a stack light at the station and on a central Andon board. A supervisor visually monitors the board and dispatches help.
When this works fine: Traditional wired systems are proven in plants with straightforward, single-department workflows where supervisors have direct line-of-sight to the Andon board. They're low-tech, reliable, and well-understood by operators.
"We had stack lights, but the only way anyone knew about a problem was if they happened to be looking at the board."Limitations:
- No data capture — there's no record of when a call was made, when someone responded, or how long the fix took
- No automatic notification — alerts depend on someone watching
- No escalation — if the first responder doesn't notice, the call sits indefinitely
- Installation cost — hardwired systems require electrical contractors and facility modifications
- Limited flexibility — adding or moving stations means rewiring
2. Wireless Hardware + Software Systems
Standalone systems that combine wireless call buttons, wearable pagers (watch-style or belt-clip), and locally-installed software for data capture and escalation.
How they work: Operators press a wireless button at their station. The signal reaches a transmitter via RF, which routes alerts to specific pagers based on call type. Software running on a local PC logs every event, generates reports, and manages escalation sequences.
When this works fine: These systems excel in noisy, high-traffic manufacturing environments where responders are mobile. Watch pagers vibrate to get attention where radios and PA systems fail. They're ideal for plants that want fast deployment without IT infrastructure changes.
"Our maintenance technicians are constantly moving between lines. They can't stand next to a screen watching for alerts — they need it on their wrist."Strengths:
- Sub-second alert delivery — button press to pager vibration in under 1 second
- Works independently of plant Wi-Fi or IT network
- Data stored locally — no cloud dependency, no recurring data fees
- Automatic escalation — unanswered calls notify a backup, then a supervisor
- Pre-configured systems ship ready to connect — typical setup under 60 minutes
- Physical buttons and wearable pagers work in noisy, glove-wearing, restricted environments
- Requires physical hardware installation (buttons at stations, pagers for staff)
- Signal range depends on facility layout — large plants may need repeaters
- Software runs on a local PC — requires a dedicated machine
3. Software-Only Cloud Platforms
Web-based applications that integrate with existing plant infrastructure (SCADA, HMI, PLC) to surface Andon-style alerts through dashboards, mobile apps, and email/SMS.
How they work: Software connects to existing automation systems or runs as a standalone web app. Operators trigger alerts through touchscreens, tablets, or computer interfaces. Alerts display on dashboards and push notifications to mobile devices. Data is stored in the cloud.
When this works fine: Cloud platforms are a strong fit for plants that already have robust SCADA/HMI infrastructure and want to add Andon functionality without installing new hardware. They're also suited for organizations that want centralized visibility across multiple facilities.
"We already had a SCADA system on every machine. We didn't want to install a parallel set of hardware — we wanted software that worked with what we had."Strengths:
- No physical hardware to install (leverages existing screens, tablets, phones)
- Centralized dashboard across multiple facilities
- Integration with existing automation stack
- Remote access for corporate visibility
- Depends on plant Wi-Fi or network connectivity — if the network goes down, alerts may not reach responders
- Cloud storage raises data ownership and privacy questions
- Subscription pricing — monthly or annual fees that accumulate over time
- Alert latency depends on network conditions — not instant like RF
- Not ideal for operators wearing gloves or in restricted areas where touchscreens are impractical
- Requires IT involvement for deployment and ongoing maintenance
4. MES Modules with Andon Features
Manufacturing Execution System (MES) platforms that include Andon alerting as one module within a broader suite of production management tools.
How they work: Andon functionality is part of a larger MES platform that also handles scheduling, quality, OEE tracking, and workforce management. Alerts are triggered through the MES interface and routed through the platform's notification system.
When this works fine: If your plant is already investing in a full MES deployment, adding the Andon module makes sense as part of a unified system. This avoids managing a separate tool for alerting.
"We were already three months into our MES rollout. Adding Andon as a module meant one fewer system to manage."Strengths:
- Unified platform — Andon data feeds directly into OEE, quality, and scheduling dashboards
- Single vendor for the full production management stack
- Deep integration with production planning and workforce management
- High cost — MES platforms are significant capital investments
- Long deployment timelines — MES rollouts often take 6-18 months
- Andon is secondary to the core MES functionality — may lack dedicated alerting features
- Overkill for plants that only need response time tracking and escalation
- Vendor lock-in — switching MES platforms means losing the Andon system too
How They Compare
| Factor | Traditional Wired | Wireless Hardware + Software | Software-Only Cloud | MES Module |
|---|---|---|---|---|
| Deployment time | Weeks (electrical work) | Hours to days | Days to weeks | Months |
| Recurring costs | None | None (optional SMS/email add-on) | Monthly/annual subscription | Part of MES contract |
| Data ownership | None (no data) | Local storage — you own it | Cloud — vendor-hosted | Vendor platform |
| Offline capability | Works (no data) | Full functionality | Degraded or none | Depends on architecture |
| Alert latency | Visual only | < 1 second (RF) | Network-dependent | Network-dependent |
| Escalation | None | Automatic, configurable | Varies by platform | Varies by module |
| Hardware included | Stack lights, cords | Buttons, pagers, lights, transmitter | None (BYOD) | Varies |
| IT dependency | None | Low (standalone PC) | High (network, cloud) | High (full MES stack) |
| Best for | Simple, single-line | Multi-department, noisy, mobile | SCADA-equipped, multi-site | Full MES deployment |
Best Architecture for Your Situation
If your responders are mobile and your plant is noisy: Wireless hardware with wearable pagers. Radios get missed. PA systems compete with ambient noise. Watch pagers vibrate — they work regardless of noise level or location.
"Radios don't work in our environment. Between the noise and the fact that technicians are moving between areas, calls just get missed."If you already have SCADA/HMI on every machine: A software-only cloud platform that integrates with your existing automation. You'll avoid installing duplicate hardware and can leverage your current investment.
If you need fast deployment with minimal IT involvement: Wireless standalone systems. Pre-configured hardware ships ready to connect. Setup typically takes under an hour, with no network changes required.
"We needed something fast. We had a trial on the floor generating data within the first week."If you're already rolling out a full MES: Add the Andon module to your existing platform. It avoids another vendor relationship and keeps your data in one place.
If budget is your primary constraint: Compare one-time purchase models (wireless hardware, traditional wired) against recurring subscription costs (cloud, MES). Over 3-5 years, subscription fees often exceed the upfront cost of a hardware system.
What We Offer: MMCall Andon System 4.0
We built a wireless hardware + software system because we saw manufacturing plants struggling with the gap between "machine is running" and "operator is productive." Radios got missed. Stack lights went unwatched. And nobody had data on how much time was actually being lost.
Key facts:
- Deployed in 1,000+ plants including Toyota, Honeywell, Amazon, Volkswagen, and Foxconn
- Existing customers see 40% average response time reduction and 10-12% downtime reduction
- One-time purchase — no monthly software fees, no cloud subscriptions
- 60-day free trial with full equipment, training, and setup support
- Pre-configured and shipping-ready — typical setup under 60 minutes
Frequently Asked Questions
What is the best Andon system for a small plant?
For plants with fewer than 20 stations, a wireless hardware + software system typically offers the best value. It deploys in hours, requires no IT infrastructure, and provides full data capture and escalation from day one. Cloud platforms and MES modules are often more system than a small operation needs.
How much does an Andon system cost?
Costs vary dramatically by architecture. Traditional wired systems cost mainly in installation labor. Wireless hardware systems range from $5,000-$15,000 for a pilot covering 10-20 stations. Cloud platforms charge monthly subscriptions. MES modules are typically part of a six-figure platform investment. For a detailed breakdown, see our cost and pricing guide.
Can I start with a pilot and expand later?
Yes — this is the recommended approach regardless of which architecture you choose. Most wireless and cloud systems are designed for incremental deployment. Start with one line or department, prove the value, then expand. For guidance on running a pilot, see our implementation guide.
Do I need Wi-Fi for an Andon system?
It depends on the architecture. Wireless hardware systems operate on radio frequency and don't need Wi-Fi for core alerting. Cloud platforms and MES modules typically require network connectivity. If Wi-Fi is unreliable or restricted in your facility, an RF-based system avoids that dependency.
How do I calculate ROI for an Andon system?
Start with your downtime cost per hour, multiply by the number of stations and hours of operation, then apply a conservative improvement estimate (10-15% is typical). Our ROI calculator does this math automatically, or see our ROI calculation guide for the methodology.
Related resources: