Andon Escalation Benchmarks for MES and OEE Buyers

Andon escalation is often the difference between a minor disruption and a full-blown loss event. For buyers of MES and OEE software, the way a platform detects, routes and resolves Andon calls has a direct impact on OEE, maintenance workload and the credibility of real time data on the shop floor.

This article explains how to benchmark Andon response and fix times per line and per shift, how those benchmarks relate to OEE performance, and how a modern MES and OEE platform like Fabrico can help you manage them in real time.

Why Andon escalation matters for MES and OEE buyers

Many teams invest heavily in OEE dashboards and production reporting, yet still struggle with recurring microstops and chronic minor losses. The root cause is often slow or inconsistent Andon response and escalation. If issues are not acknowledged and resolved quickly, the MES ends up recording more downtime and speed loss than necessary and OEE becomes a lagging indicator, not a performance lever.

For MES and OEE buyers, Andon is not only a visual or cultural tool. It is a data and workflow problem. You need:

• Standardized Andon categories that tie directly to OEE loss buckets
• Reliable capture of each Andon event from the machine or operator
• Clear ownership for who responds and who fixes the problem
• Measured response time and fix time, by line and shift
• Automatic triggers for maintenance and production actions when thresholds are breached

Without that, you are left with MES and OEE metrics that describe the past but do not help you react in the present.

How Fabrico treats Andon inside MES and OEE

Fabrico is a cloud based MES and OEE platform for manufacturers. It captures production and downtime data directly from machines, classifies each loss, and links Andon calls to both real time dashboards and follow up actions. Its built in maintenance management makes it possible to route equipment related issues directly into maintenance work, without separate tools or spreadsheets.

In practice, this means that every Andon event can be:

• Detected at the machine level
• Assigned a loss category that feeds OEE
• Timed from alert to first response
• Timed from alert to fix completion
• Escalated to maintenance or production leads when thresholds are exceeded

To understand how Andon fits into the broader MES landscape, you can read more about the relationship between MES and OEE in this article: OEE vs MES.

Key Andon metrics: response time and fix time

When you evaluate MES and OEE software, pay specific attention to how it supports the following two Andon metrics.

1. Andon response time

Response time is the elapsed time from when an Andon signal is created to when a responsible person acknowledges it and arrives at the station or accesses the problem in the system. For operations leaders, this metric shows how quickly the team reacts to problems, not how fast the problem is solved.

A practical implementation in your MES and OEE platform should allow you to:

• Start the timer as soon as the operator hits the Andon button or the machine triggers an automatic alert
• Stop the timer when the assigned role, for example, line leader, technician or mechanic, logs into the event or scans a QR code at the station
• View average and median response time per line, per product family and per shift
• Filter by Andon category, for example, quality, material, equipment, safety

2. Andon fix time

Fix time is the elapsed time from Andon alert creation to issue resolution. It is the window during which your MES records some combination of downtime, speed loss or quality risk. Fix time has a direct effect on OEE and on the perceived reliability of your equipment and processes.

Your MES and OEE software should let you:

• Track fix duration separately from response time
• Capture root cause and action taken for each event
• Link repeating issues to maintenance tasks through the built in maintenance management
• Report on fix time distributions, not only averages, so you can see outliers and chronic problems

Both response time and fix time should be visible on the same real time dashboards where you monitor OEE and losses. If you are exploring options for that, this guide on best OEE software with real time dashboards provides useful evaluation criteria.

Measuring Andon times per line and per shift

In multi line and multi shift plants, averages hide more than they reveal. You need to understand how Andon performance varies across lines and shifts, because that is often where you find behavioral and staffing gaps that drag down OEE.

Per line measurement

Measure Andon response and fix times per line so you can:

• Spot lines with strong OEE but weak reaction to disturbances, which may signal overburdened support staff
• Identify lines with fast response but long fix times, which may indicate complex equipment or poor standard work
• Compare lines that run similar products to see where best practices are not shared

Your MES and OEE platform should allow line level drill down from plant wide views to individual cells, with time based filtering so you can isolate specific campaigns, changeovers or new product introductions.

Per shift measurement

Shift based metrics are equally important. Response and fix times often vary by:

• Experience and skill mix of operators and technicians on each shift
• Availability of maintenance support and technical leadership
• Workload patterns, such as peaks in changeovers or high mix orders

Measuring Andon metrics by shift allows you to:

• Compare first, second and third shift performance objectively, not anecdotally
• Adjust staffing and cross training to reduce dependency on a few key people
• Target coaching where response is slow or fixes are inconsistent

An effective MES and OEE platform will let you filter Andon events and OEE performance by shift code, then view drill downs by line and machine. In Fabrico, this same view is used by operations, maintenance and continuous improvement teams, so everyone works from one version of the truth.

What does a good Andon time look like

Every plant is different, and good Andon times will depend on process type, automation level, staffing and product mix. Instead of chasing universal numbers, MES and OEE buyers should focus on setting internal benchmarks that link Andon performance explicitly to OEE and to business impact.

A practical approach is:

1. Baseline current performance: use your MES and OEE data to capture a few weeks of Andon response and fix times per line and shift
2. Segment by type of issue: look separately at equipment, material, quality and changeover related Andon events, because each has different expectations
3. Link to OEE: identify which lines and shifts have the largest OEE gaps, and see how response and fix times compare to better performing areas
4. Set realistic targets: define target bands for response and fix times by category, for example, a quicker target for safety incidents than for cosmetic quality checks
5. Iterate quarterly: review targets every few months as training, maintenance and process improvements take effect

Rather than declaring a single number as good, you want a clear structure: short response times for urgent issues, acceptable fix times based on complexity and availability of spare parts or skills, and a continuous trend of improvement in both.

Using Andon benchmarks to improve OEE

When Andon metrics are tightly integrated with your MES and OEE, they become levers for focused improvement, not just operational hygiene.

1. Reducing unplanned downtime

By monitoring fix times for equipment related Andon events, you can identify machines where recurring failures or slow diagnosis lead to extended stops. With Fabrico, those events can trigger maintenance actions directly in the built in maintenance management workflows, turning repeated Andon calls into structured work to eliminate root causes over time.

2. Cutting speed losses and minor stops

Short microstops may not always trigger formal Andon calls, but when they do, response and fix times are key inputs to your speed loss analysis. Integrating Andon timestamps with machine data allows you to see if a line is constantly choked by minor issues that could be addressed through better standard work, training or small design changes.

3. Improving changeovers and planned stops

Many plants use Andon during changeovers to call for materials, tooling or quality checks. Measuring response and fix times around these events helps you streamline handoffs between production, maintenance, logistics and quality. The result is shorter planned downtimes and more predictable schedule adherence, which then feeds into better availability scores in your OEE.

4. Strengthening maintenance planning

Andon data is a rich source of information on where maintenance should focus. When your MES and OEE platform has maintenance management built in, repeated Andon events on the same asset can be recorded as triggers for preventive tasks, inspections or condition based checks. Over time, this reduces both Andon volume and fix time, as issues are identified earlier and addressed more systematically.

For industries with high equipment intensity, such as fabrication shops, these connections are particularly important. You can learn more about OEE applications in that environment here: OEE for metal fabrication.

What to look for in MES and OEE software for Andon management

When evaluating MES and OEE platforms, assess Andon capabilities with the same rigor you apply to core OEE functionality. Specifically, look for:

• Automatic event capture through PLCs, sensors or machine interfaces, with the option for operators to trigger manual Andon calls
• Unified loss model where every Andon event is classified into availability, performance or quality loss buckets that feed OEE
• Configurable escalation rules based on time thresholds or issue severity, so alerts can escalate to line leaders, maintenance or management
• Role based workflows that show each user exactly which Andon events require their attention, and capture their actions in a structured way
• Real time visibility for both shop floor and office users, including per line and per shift performance views
• Integrated maintenance follow up that turns repeated Andon events into structured jobs, inspections or improvement tasks using the built in maintenance management functionality

Fabrico combines these capabilities with a cloud based architecture and modern real time dashboards, so plants can roll out Andon practices consistently across lines and sites, while keeping OEE and maintenance data fully aligned.

Implementing Andon benchmarks with Fabrico

For teams that want to move quickly from theory to practice, a typical implementation with Fabrico involves:

1. Connecting key lines and machines to capture production and downtime signals
2. Defining standard Andon categories aligned with your OEE structure
3. Configuring response and fix time tracking, with clear ownership per issue type
4. Setting initial benchmarks per line and shift, based on a short baseline period
5. Building real time views that highlight overdue Andon events, slow responses and long fixes
6. Linking chronic Andon issues to maintenance actions inside the platform, so they are addressed systematically

From there, plant managers, production managers and maintenance leaders can use the same data set to run daily reviews, weekly performance walks and monthly improvement meetings, all centered around how Andon performance supports better OEE.

To see how this works on real production and maintenance data, you can Request a demo or Contact us.