Manufacturing engineers evaluating alert systems often find themselves comparing Andon systems and Manufacturing Execution Systems (MES). Both touch production visibility and downtime — but they solve different problems, operate at different levels, and deploy on vastly different timelines.
"We had MES for five years before we added Andon. The MES showed us machines were down, but it never told us why operators were standing around waiting for help." — As one automotive manufacturer explainedUnderstanding the distinction helps you avoid over-investing in a full MES when you only need faster response time tracking — or under-investing in a standalone Andon when your plant could benefit from both. This guide clarifies what each system does, when one alone is sufficient, and when combining both delivers the best outcome.
What Each System Does
MES: Strategic Production Visibility
A Manufacturing Execution System orchestrates production from order release to finished goods. Its core functions include:
- Production scheduling and dispatching — which jobs run where and when
- Quality management — inspections, test results, nonconformance tracking
- OEE and machine performance — availability, performance rate, quality yield
- Workforce management — labor tracking, skill assignments
- Material and traceability — lot tracking, genealogy
"Our MES dashboard tells us exactly when each machine stopped and for how long. It's great for OEE. But it doesn't capture the 10 minutes an operator spent walking the floor looking for maintenance before anyone responded." — As one food and beverage processor noted
Andon: Tactical Response and Human Wait Time
An Andon system addresses the gap between "problem occurs" and "help arrives." Its core functions include:
- Instant alerts — button press to pager vibration in under a second
- Automatic escalation — unanswered calls notify backup, then supervisor
- Response time tracking — time to respond (TTR) and time to fix (TTF)
- Real-time status boards — who's waiting, where, and for how long
"MES tracks machines, not people. The Andon data showed us 3.5 hours of operator idle time per shift that didn't appear on any OEE dashboard." — As one medical device manufacturer discovered
Comparison Table
| Factor | MES | Andon System |
|---|---|---|
| Primary focus | Machine performance (OEE, throughput, quality) | Human wait time and response |
| Scope | Strategic — scheduling, traceability, workforce | Tactical — instant alerts, escalation |
| Deployment timeline | 6–18 months typical | Hours to days |
| What it shows | What happened (downtime, output, yield) | Why operators waited |
| Alert delivery | Dashboard, reports — often after the fact | Sub-second to wearable pagers |
| Data granularity | Machine-level, shift-level | Call-level, station-level |
| Typical investment | Six figures (platform + implementation) | $5K–$15K for pilot (wireless systems) |
| Recurring costs | Licensing, support, often subscription | One-time purchase (optional SMS add-on) |
When One Is Enough
MES Alone May Suffice When:
- Your pain is machine-centric. You need OEE, traceability, quality management, and scheduling — and response time isn't a bottleneck.
- Responders are stationary and visible. Supervisors have line-of-sight to problems; there's no "finding help" gap.
- You're building a greenfield system. You have the budget and timeline for a full MES rollout, and Andon will be part of that platform.
"We're rolling out MES across three plants. Andon is a module in the platform — we're adding it as part of the deployment. It made sense to keep everything in one system." — As one aerospace supplier described
Andon Alone May Suffice When:
- Your pain is response time. Operators wait too long for maintenance, quality, or materials. You need faster alerts and data on wait time.
- MES isn't on the roadmap. Budget or priorities don't support a full MES. You need a focused solution for response and escalation.
- You need results fast. A full MES takes months. A standalone Andon can be operational in hours.
- You're running a pilot. Before committing to enterprise software, you want to prove the value of response time improvement with minimal investment.
"We needed something in weeks, not months. The Andon system was running and generating Pareto data before our MES evaluation was even finished." — As one general manufacturing operations manager recalled
When You Need Both
The strongest case for having both is when MES gives you the "what" and Andon gives you the "why."
MES shows what happened: Machine X was down for 23 minutes. OEE dropped 8%. Scrap increased on line 2.
Andon shows why operators waited: The call went out at 2:14, maintenance arrived at 2:31. Seventeen minutes of wait time before anyone responded.
"Combined, we finally had the full picture. MES told us we had downtime. Andon told us we had an escalation problem — calls were going to the wrong person and sitting." — As one tier-1 automotive supplier reportedPlants that deploy both typically use Andon for real-time alerting and response tracking, then feed that data into MES or BI for unified reporting. The Andon REST API makes integration straightforward for plants with existing MES or ERP systems.
"Our MES vendor wanted six figures for their Andon module. We got a dedicated Andon system for a fraction of that and integrated it via API. The data flows into our production dashboards anyway." — As one heavy vehicle manufacturer explained
Solution Categories: How Andon Fits the Landscape
Andon functionality is available in three main forms — each with different fit and trade-offs.
Software-only cloud platforms integrate with existing SCADA, HMI, or PLC infrastructure. Alerts surface through dashboards and mobile apps. Best when you have robust automation already and don't want new hardware.
Wireless hardware + software systems use physical call buttons and wearable pagers. Alerts travel via radio frequency — sub-second delivery, no Wi-Fi dependency. Best for noisy plants with mobile responders.
MES modules with Andon features bundle Andon into a broader production management suite. Best when you're already deploying a full MES and want a single platform. Trade-off: you typically wait for the full MES rollout, and the Andon capability may be secondary to the platform's core functionality.
"Our facility is too noisy for radios. We needed something on our wrists that vibrates. Software on a phone doesn't work when you're wearing gloves and can't hear notifications." — As one plastics manufacturer observedThe choice among these categories depends on your facility layout, responder behavior, existing automation, and timeline. A food and beverage plant with strict hygiene and glove requirements will favor physical buttons and wearable pagers over touchscreen interfaces. A facility with robust SCADA on every machine may prefer software integration over new hardware.
Integration: Making Andon and MES Work Together
For plants with both systems, integration typically flows one way: Andon → MES/ERP/BI.
Andon systems with REST APIs can push call data, response times, and escalation events to external systems. That means:
- Downtime events in MES can be enriched with Andon wait-time data
- Pareto charts from Andon can feed into production dashboards
- Response time metrics can appear alongside OEE on a single screen
"We run both. MES handles scheduling and OEE. The Andon system handles who gets paged and how fast. Our BI team pulls from both for a complete view of downtime and response." — As one packaging manufacturer described
"OEE said we had 12% downtime. Andon showed us that half of that was operators waiting for someone to show up. Different problem, different fix." — As one plastics manufacturer put it
What We Offer: MMCall Andon System 4.0
We built a wireless hardware + software Andon system for plants that need instant alerts, response tracking, and escalation — without waiting for a full MES deployment or paying platform-scale prices.
Key facts:
- Deployed in 1,000+ plants including Toyota, Honeywell, Amazon
- Existing customers see 40% average response time reduction
- REST API for MES/ERP integration
- One-time purchase, no monthly fees
- 60-day free trial
Frequently Asked Questions
Does an Andon system replace MES?
No. MES covers scheduling, quality, traceability, OEE, and workforce management. Andon covers real-time alerts, escalation, and response time tracking. They complement each other. MES shows what happened; Andon shows why operators waited.
Can Andon data integrate with MES?
Yes. Andon systems with REST APIs can push call logs, response times, and escalation events to MES, ERP, or BI tools. Many plants run both and feed Andon data into their production dashboards.
How long does it take to deploy an Andon system vs MES?
Standalone Andon systems (wireless hardware + software) typically deploy in hours to days. MES platforms often take 6–18 months. If response time is your immediate pain, Andon can deliver results while you evaluate or roll out MES.
Do I need MES to use an Andon system?
No. Andon systems operate independently. They can integrate with MES when you have one, but they don't require it. Many plants run Andon alone for years.
Should I use the Andon module in my MES or a standalone system?
It depends. If you're already deploying a full MES and the Andon module meets your needs (alert delivery, escalation, data capture), the module can work. If you need faster deployment, lower cost, or dedicated hardware (e.g., wearable pagers in noisy plants), a standalone wireless Andon system may be a better fit.
Related resources: