Get Help to the Line Faster
Let operators call maintenance, quality, team leads, material handlers, or other support groups with a single action — and track every call from trigger to resolution.
10in6 turns support requests from the floor into structured, visible, and measurable response workflows.
When a line needs help, speed matters — and informal processes lose time.
A machine stops. A quality issue appears. Material is missing. The operator knows something is wrong, but getting the right person involved is often less structured than it should be.
Someone walks over to find a supervisor. A radio call goes out. A text gets sent. A team lead hears about it late. Maintenance responds, but no one has a clear record of when the issue started, how long the response took, or what the actual resolution was.
The line gets support eventually. But the process around it is inconsistent — and that inconsistency creates delay, makes follow-up harder, and leaves the team with less visibility into where response time is being lost.
It also makes it harder to see which types of calls happen most often, which areas are under the most pressure, and where recurring issues are affecting production flow. Andon works best when calling for help is immediate, visible, and trackable. That is what 10in6 helps provide.
From the button press to the resolved record.
The operator triggers a call for assistance
From the 10in6 Operator Console, shop floor personnel can trigger an Andon call with a simple button press. The call is tied to the type of support needed — maintenance, quality, team leadership, material delivery, or other configured groups.
This makes it easier to ask for help without delay and without leaving the process.
The right team is notified immediately
Once the call is triggered, the alert is routed to the appropriate people based on the call type and workflow. Notifications can be shown on Andon boards and Real-Time displays, and can also be delivered by email or SMS where needed.
This helps the right people see the issue sooner and respond faster.
The call stays visible until it is resolved
The Andon call is not just sent and forgotten. It remains part of a tracked workflow so supervisors and support teams can see that the issue is active, who is responding, and whether it has been resolved.
That prevents calls from being handled informally or falling through the cracks.
Response and resolution timing are recorded
10in6 tracks when the call was triggered, when someone responded, and when the issue was resolved. This creates a clearer record of support performance and gives the plant better visibility into where response time is improving or falling behind.
Help requests become usable operational data.
Call history builds into improvement insight
As calls accumulate, the system can support reporting on call types, departments, response times, and recurring issues. Teams can use that information to identify common disruptions and focus improvement efforts where support demand is highest. That makes Andon more than an alerting tool — it becomes part of how the plant improves response and removes recurring friction from the floor.
What it looks like
| Alert Description: | Material Handler Call |
| Location: | Injection Department · Injection #2 |
| Summary | |||||
|---|---|---|---|---|---|
| Work Order | Classification | Category | Sub-Category | Status | Who Initiated |
| 266450 | General | Material Handler | Waiting for response | Super | |
| Issue Owner 1 | Issue Owner 2 | Issue Owner 3 | Due Date | Priority | |
| 30-Nov-21 | 0 | ||||
| Issue Description | |
|---|---|
| Black Resin Needed at Injection 2 |
| Resolution History | ||||
|---|---|---|---|---|
| Entry | Entered By | Time Entered | Corrective Action | Resolution |
Every request, every response, every minute — on the record.
With 10in6 Andon Calls, your team can see:
- Active calls for assistance on the floor
- Which type of support is being requested
- Who was notified and who responded
- Response time and resolution time for each call
- Real-time visibility through Andon boards and display screens
- Alerts delivered by email or SMS
- Recurring call types and high-demand departments
- Historical trends that show where support issues are affecting production
- The issue record behind each escalation
Why a structured call process matters
When operators need help, they should not have to depend on finding the right person manually or hoping the message gets passed along. A structured Andon workflow removes that uncertainty.
It gives operators a simple and consistent way to escalate issues. It gives supervisors and support teams visibility into what is active. And it gives the plant a clearer record of how well the response process is actually working — which improves both reaction time and accountability.
Why tracking turns calls into signals
An Andon call is not just a request for help. It is also a signal. If the same types of calls keep happening, or if certain calls take too long to resolve, that tells the plant something important about where support systems are weak and where recurring losses are building.
Tracking turns those signals into something the team can work from — identifying common disruptions, measuring response performance, and focusing improvement efforts where support demand is highest.
Andon Calls works especially well alongside:
Andon Calls questions
- What types of Andon calls can be created?
- Calls can be configured for the types of support your plant needs, such as maintenance, quality, team leaders, material delivery, management, and more.
- How are people notified?
- Depending on the deployment, notifications can be shown on Andon boards and Real-Time displays, and can also be sent by email or SMS.
- Can the system track who responded?
- Yes. The workflow can record who responded to the call, along with response and resolution timing.
- Can Andon calls be customized for our process?
- Yes. Call types and routing workflows can be configured to match your operation and the support groups involved.
- What happens after a call is triggered?
- The call remains visible within the workflow until it is addressed, helping supervisors and support teams track the issue through to resolution.
- Can we report on recurring call types?
- Yes. Historical reporting can be used to review call patterns, response performance, and the types of issues that occur most often.
- Does this integrate with the Operator Console?
- Yes. Andon Calls can be triggered directly from the 10in6 Operator Console.
Works alongside these MES capabilities
Need this configured around your actual equipment and workflows?
Every 10in6 deployment includes our team — connecting your equipment, configuring your workflows, and supporting your operation long after go-live.
Help the floor get support without delay.
Give operators a faster way to call for help, make issues visible immediately, and track every response from trigger to resolution.