Automotive production runs on takt time. Every second an operator waits for maintenance, materials, or quality support is a second the line is out of sync. OEMs and Tier-1 suppliers face a unique set of pressures: IATF 16949 documentation requirements, multi-shift 24/7 operation, noisy stamping and assembly environments, and the expectation that sister plants run identical systems for audit consistency.
"We evaluated multiple options before settling. The key was finding something that fit our casting operation, our OEM customer expectations, and our multi-building layout — not just which vendor had the best demo."This guide maps how automotive plants evaluate and choose Andon systems, organized by solution category and weighted for the criteria that matter most in this industry.
Why Automotive Is Different
Automotive manufacturing imposes requirements that general manufacturing does not. Understanding these differences shapes which system architecture makes sense.
Takt time sensitivity. Assembly lines run to a defined cycle. A 90-second takt time means a five-minute wait for materials translates to multiple units of lost production — and that wait often doesn't appear on OEE dashboards, which track machine state, not operator idle time.
"Operators waiting on maintenance and forklift support — those lost minutes never showed up on our OEE. We knew we were losing time, but we couldn't prove where."IATF 16949 documentation. Many automotive suppliers must document response processes, escalation protocols, and corrective action records. An Andon system that captures timestamps, responder identity, and resolution codes supports audit readiness without manual paperwork.
Multi-shift, 24/7 operation. Plants running around the clock need systems that perform consistently across shifts. Response time data that varies by shift — faster days, slower nights — often reveals staffing or supervision gaps, but only if the system captures it.
Noisy environments. Stamping, welding, assembly, and paint shops generate ambient noise that drowns out radios and PA systems. Any alert system that relies on audible cues will underperform in these areas.
"Radios get missed in our environment. Between the press room and the welding cells, nobody can hear a page. We needed something that works when you can't hear."Sister-plant standardization. Multi-site operations often standardize on one Andon approach so that training, processes, and audit evidence are consistent. A system that works in one plant but cannot replicate across sites creates long-term inconsistency.
Material shortages and takt disruption. When material handlers or forklift operators don't respond quickly, stations go idle. The call might be "materials" rather than "maintenance," but the impact on takt time is the same.
"Material shortages were killing our takt. We'd have operators standing there waiting for a forklift while the line backed up. No one was tracking that as downtime — it was just 'waiting on material.'"
The Four Categories of Andon Systems
1. Traditional Wired Systems
Cord-pulls, hardwired stack lights, and central Andon boards wired to each station.
How they work: Operator pulls a cord or presses a hardwired button. A stack light illuminates at the station and on a central board. A supervisor monitors the board visually and dispatches help.
When this works in automotive: Single-line operations with direct supervisor line-of-sight. Proven, simple, and low-tech. Sufficient for some Tier-2 or sub-assembly areas with straightforward workflows.
Limitations for automotive:
- No data capture — no record of call time, response time, or resolution
- No escalation — if the first responder doesn't notice, the call sits
- No differentiation between maintenance, quality, materials, or supervisor calls
- Installation requires electrical contractors and facility modifications
- Adding or moving stations means rewiring
- Radios or PA still required to reach mobile technicians — and they fail in noisy areas
2. Wireless Hardware + Software Systems
Standalone systems combining wireless call buttons, wearable pagers (watch-style), and locally-installed software for data capture, routing, and escalation.
How they work: Operators press wireless buttons at their station. RF signals reach a transmitter that routes alerts to specific pagers by call type. Software on a local PC logs events, generates reports, and manages escalation sequences.
When this works in automotive: Noisy environments where responders are mobile. Watch pagers vibrate where radios fail. Plants with multiple maintenance sub-areas (injection, painting, CNC, assembly) need call routing so the right team gets the alert.
"We have maintenance split across injection, painting, and CNC. We needed routing — not a broadcast to everyone. The right person had to get the right call."Strengths:
- Sub-second alert delivery — button press to pager vibration in under 1 second
- Works independently of plant Wi-Fi
- Local data storage — no cloud, often preferred for OEM customer data agreements
- Automatic escalation — unanswered calls notify backup, then supervisor
- Pre-configured call types (maintenance, quality, materials, supervisor) align with automotive workflows
- Multi-building coverage with signal repeaters
- Physical buttons and wearable pagers work in glove-wearing, high-noise environments
- Requires physical hardware (buttons, pagers, transmitter)
- Large or multi-building plants may need repeaters for full coverage
- Software runs on a local PC — requires a dedicated machine
3. Software-Only Cloud Platforms
Web-based applications that integrate with SCADA, HMI, or PLC to surface Andon-style alerts through dashboards, mobile apps, and email/SMS.
How they work: Software connects to existing automation or runs as a standalone web app. Operators trigger alerts via touchscreens, tablets, or computers. Alerts display on dashboards and push to mobile devices. Data is stored in the cloud.
When this works in automotive: Plants with robust SCADA/HMI infrastructure and strong Wi-Fi. Useful for multi-site visibility when corporate wants centralized dashboards. Some OEMs and Tier-1s with strict data residency policies may restrict cloud storage.
Strengths:
- No new physical hardware if leveraging existing screens and tablets
- Centralized visibility across multiple facilities
- Integration with existing automation stack
- Depends on network connectivity — if Wi-Fi drops, alerts may not reach responders
- Cloud storage can conflict with customer data agreements
- Subscription pricing accumulates over time
- Alert latency depends on network conditions
- Touchscreens impractical in many automotive environments (gloves, grease, restricted zones)
4. MES Modules with Andon Features
Manufacturing Execution System platforms that include Andon alerting as one module within a broader production management suite.
How they work: Andon functionality lives inside a larger MES that handles scheduling, quality, OEE, and workforce management. Alerts are triggered and routed through the MES interface.
When this works in automotive: Plants already investing in a full MES rollout. Andon becomes one fewer system to manage and feeds directly into OEE and quality dashboards.
Strengths:
- Unified platform — Andon data feeds OEE, quality, scheduling
- Single vendor for production management
- Deep integration with production planning
- High cost — MES platforms are major capital investments
- Long deployment — 6–18 months typical
- Andon is secondary to core MES; dedicated alerting features may be limited
- Overkill if the primary need is response time tracking and escalation
- Vendor lock-in — changing MES means losing the Andon system
Evaluation Criteria for Automotive Plants
| Criterion | Why It Matters for Automotive |
|---|---|
| IATF 16949 documentation | Response process evidence, escalation logs, corrective action records |
| Takt time sensitivity | Sub-second alerts, clear distinction between wait time and repair time |
| Multi-shift performance | Consistent behavior across day/night/weekend; shift-level reporting |
| Noisy environment operation | Works without audible alerts — vibration, not voice |
| Call type routing | Maintenance, quality, materials, supervisor — routed to the right team |
| Multi-building coverage | Signal reach across stamping, assembly, paint, logistics |
| Sister-plant replication | Same system, same configuration across sites |
| Data ownership & residency | Local storage often preferred for OEM customer agreements |
| Offline capability | System continues if network drops |
| Deployment speed | Pilot in days, not months — prove value before full rollout |
Real Results from Automotive Plants
Automotive facilities that implement Andon systems often see measurable improvements within weeks:
"We achieved 71% wait time reduction at our heavy vehicle assembly plant. The data showed us exactly where the bottlenecks were — it wasn't guessing anymore."
"At our 24/7 casting facility, we hit 19-day payback. The combination of faster response and documented data for our OEM customer made the case easy."These outcomes depend on fit: the right architecture for the facility, proper call type configuration, and escalation sequences that match how teams actually work.
Choosing the Right Fit
If your plant is noisy and responders are mobile: Wireless hardware with wearable pagers. Stamping, welding, and paint shops drown out radios. Watch pagers that vibrate deliver alerts regardless of ambient noise.
If you have multiple maintenance sub-areas: A system that routes calls by type — injection, painting, CNC, assembly — so the right team gets the right alert. Broadcast systems send everything to everyone, which creates confusion and delay.
If OEM audit documentation is a driver: Prioritize systems that capture timestamps, responder identity, and resolution codes. Export to CSV for IATF 16949 record retention.
If you're rolling out across sister plants: Choose an architecture that replicates easily. Same hardware, same software, same configuration. Training and processes stay consistent; audits expect it.
If you need to prove value quickly: Start with a pilot on one line or department. Wireless systems typically deploy in hours. First Pareto data often appears within 48 hours — before the trial ends.
What We Offer: MMCall Andon System 4.0
We built a wireless hardware + software Andon system because automotive plants told us they needed instant alerts in noisy environments, data for OEM audits, and systems that could replicate across sister plants.
Key facts:
- Used by Toyota, Magna, Honeywell, Faurecia, CNH Industrial, Volvo, Volkswagen, and other automotive manufacturers
- 40% average response time reduction among existing customers
- Pre-configured for automotive: maintenance, quality, materials, and supervisor call types
- Multi-building coverage with signal repeaters — stamping to assembly to paint
- 60-day free trial with full equipment, training, and setup support
- Local data storage — no cloud, no recurring software fees
- Typical setup under 60 minutes; first Pareto data within 48 hours
Frequently Asked Questions
What Andon system do OEMs typically use?
OEMs run a mix of approaches — traditional wired, wireless hardware, MES-integrated, and software-only. The trend is toward systems that capture data (response time, escalation, resolution) and support IATF 16949 documentation. Wireless hardware systems are common in noisy stamping, welding, and assembly areas where radios underperform.
Do Tier-1 suppliers need different Andon features than OEMs?
Tier-1 suppliers often face the same pressures: OEM audit expectations, takt time sensitivity, multi-shift operation, and noisy environments. The main difference is scale — Tier-1s may have smaller facilities or multiple sister plants. A system that works in one plant and replicates easily supports standardization.
How does Andon data support IATF 16949?
IATF 16949 requires documented processes for problem resolution, escalation, and corrective action. Andon systems that log call time, responder identity, arrival time, and resolution provide audit-ready evidence without manual paperwork. Export to CSV for record retention.
Can an Andon system work across multiple buildings?
Yes. Wireless RF-based systems use signal repeaters to extend range. Multi-building coverage (e.g., stamping, assembly, paint) is achievable with proper repeater placement. Cloud and MES systems depend on network coverage across buildings.
What is typical payback for an Andon system in automotive?
Results vary by facility. Automotive plants often report 30–45 day payback; heavy vehicle assembly and 24/7 casting operations have reported payback in as little as 19 days. Factors include downtime cost per hour, number of stations, shift configuration, and baseline response times.
Related resources: