DQS

Put Quality Alerts in Front of the Operators Who Could Repeat the Defect

Push an alert for a known defect to the machines it affects. It stays on the operator screen through every shift change, and each operator confirms it before running parts.

10in6 Quality Alerts logs every confirmation with the operator's name and the time.

1At the line
Operator console on Weld Cell B: the quality alert 'Burn-through, rear-left joint' for the FRM-0915 seat frame, with a red banner reading 'Check travel speed and tip condition before each run', the seat-frame drawing with the rear-left joint circled, and Accepted by Rita Silva, Sep 29, 3:36 PM
2In the report
Task instances for the same alert on Weld Cell B: eight acceptances from Sep 25 to Sep 29, one per shift, by Minh Nguyen on days, Rita Silva on afternoons and Ana Patel on nights, all Pass; the top row is Rita Silva at 3:31 PM, completed 3:36 PM
Rita Silva signs in at Weld Cell B at 3:31 PM and the burn-through alert opens on its own, holding her before she starts. She accepts it at 3:36 PM with her badge and PIN. The record shows every acceptance, one per shift, each by that shift's operator.

Day shift finds the defect. Night shift runs the same part without hearing about it.

The warning usually travels by word of mouth: a supervisor's conversation at handover, a note, a notice taped to the machine, an email. Some of those reach the operator on the next shift and some don't, and afterwards nobody can say for certain who knew.

The message depends on one supervisor

If the supervisor at handover forgets, or the message gets shortened on the way, the next operator starts the run without knowing what went wrong on that line a few hours earlier.

Yesterday's defect comes back

An operator who wasn't told what to look for won't check for it, and a defect that should have been a one-time event turns into a recurring one.

Nobody can prove who was told

On paper there's no record of which operators were notified, when, or whether they saw it before production resumed. When an auditor asks how a corrective action reached the floor, the answer is verbal.

How 10in6 delivers and tracks quality alerts

From the quality engineer's desk to the operator screen

Each alert is assigned to the machines or work centers it applies to. While it is active, it appears on the operator interface at each of those stations.

Alerts can include
Description of the issue What to inspect or watch for Reference images Specific work instructions Corrective action steps Escalation contact if recurrence found

A quality engineer or supervisor can raise an alert by hand, or a rule can raise it automatically: a failed quality check, an SPC signal outside the control limits, a customer complaint notification. It stays active at those stations for every operator who starts or continues work there.

Attach a photo of the defect next to the instruction for the extra check, and the operator knows exactly what to look for on the next part.

Features and visibility

What you can enforce and track

Machine-level alert targeting

Pick the machines, workstations or areas for each alert. Stations it doesn't apply to never show it.

Required acknowledgment before production

The alert opens when the operator signs in and holds them there, before they start the run, until they accept it with their badge and PIN.

Shift-to-shift consistency

An active alert stays up through shift changes, so nights and weekends see it as well as the shift that raised it.

Digital signature record

Each acknowledgment works as a signature: the operator's identity and the time, recorded ahead of their next run.

Escalation for unacknowledged alerts

If an alert sits unacknowledged past a set time, supervisors are notified by email or SMS.

Alert and acknowledgment history

Each alert keeps its history, from when it was raised through every acknowledgment to how it was resolved, for traceability and audit review.

Before Quality Alerts
  • Warnings passed on at handover, on paper or by email
  • The next operator may start without hearing about it
  • Each shift ends up with its own version of the corrective action
  • No record of who was told, or when
With 10in6 Quality Alerts
  • The alert on screen at each affected machine
  • Operator sign-off on every shift
  • The same instruction on days, nights and weekends
  • A timestamped sign-off log for audits and traceability
Common Questions

Quality Alerts questions

What should a quality alert include?
The defect, with a photo and what good looks like; the affected product, parts or lots; the machines or areas it applies to; the action required, such as an extra check, a hold or a sort; who issued it; and when it will be reviewed or closed. Keep it short enough for an operator to take in at a glance.
What triggers a quality alert?
Alerts can be triggered manually by quality engineers or supervisors, or automatically based on rules you define — such as an SPC violation, a failed quality check, or a customer complaint notification.
Can alerts be targeted to specific machines or work centers?
Yes. Alerts can be displayed at specific machines, workstations or areas. You choose which locations see which alerts, so operators at unaffected stations are not distracted by issues that do not apply to them.
What happens if an operator does not acknowledge the alert?
Escalation rules can be configured so that unacknowledged alerts are automatically escalated to supervisors or sent by email and SMS after a defined time window, so an alert does not go unnoticed during a busy run.
Is there a record of who acknowledged each alert and when?
Yes. Every alert, acknowledgment and response is timestamped and tied to the operator who responded. The audit trail shows who was notified, when they saw the alert, and that they confirmed it before continuing production.
Can instructions or images be attached to an alert?
Yes. Alerts can include specific instructions, reference images or documents that show the operator what to look for and how to respond.
Why plants choose 10in6

Set up around how your plant runs

Standardized platforms expect the plant to change to fit the software. Do-it-yourself platforms leave your team to build and maintain everything. With 10in6, we configure the system around your equipment, codes and reports, and your team runs it day to day.

01

Your equipment, codes and reports

Your checks, intervals and forms set up per line and product, and traceability built around your part numbers and your customers’ requirements.

02

Your team runs it day to day

Operators, downtime and scrap codes, products and targets, shift schedules, checks, alerts, emailed reports and real-time boards are managed by your own people. Everyday changes need no support ticket and no invoice.

03

A project manager for the bigger things

New machines, new modules and custom reports go through a 10in6 project manager who already knows your deployment, so nothing starts from scratch. If you would rather we made everyday changes too, we can.

04

Still here years later

The system keeps being refined after go-live, and new capabilities are added without rebuilding it. Some of our customer relationships have run for 12 years, and 97% of customers say they would never go back.

“Our 10in6 Project Manager has been very responsive and the software is flexible enough to be configured to our specific needs.”

— Craig Pielechaty, Process Engineering Specialist, Stackpole International
How the 10in6 delivery model works →

Stop relying on word of mouth to communicate critical quality issues.

Tell us how quality issues reach the floor today. We'll show you how an alert would reach each affected machine on your lines, with the sign-off record behind it.

Request Pricing → See Customer Results