Checks scheduled by the line, rejects booked to the order.
A check falls due when an order starts, every so many minutes or every so many parts. A failed point schedules its own recheck, a critical one alerts the supervisor at once, and every reject is declared against a reason and the order that made it.
A control plan on paper cannot show what happened.
The sheet says every 500 parts. Whether the check was done at 500, at 900 or after the run, the sheet cannot say, and a failed measurement leaves no trace of what followed it. In VZIAM MES a check is a job with a due time, a result and a history, a recheck is chained to the check that failed, and a lot whose releasing point is open stays held.
Five rules the quality module enforces.
Each one replaces a line in a procedure with a behaviour of the software, which is the part an auditor can check.
- 01
A reject without a reason is refused.
Any quantity of rejects needs an active reason from the tree. A quantity larger than the order’s total output needs a supervisor’s confirmation, so a slip on the numpad cannot sink the quality figure.
- 02
A failed check schedules its own recheck.
For each check, the quality manager decides: no recheck, the failed points only, or the full check. The recheck joins the operator’s queue with the failed points highlighted, chained to the check before it.
- 03
A critical point does not wait.
A non-conforming critical control point alerts the supervisor at once, requires a comment from the operator and stays open until a recheck conforms.
- 04
A releasing point holds the lot.
While a releasing point is non-conforming, the lot stays blocked for release. A supervisor can force the release, but only with a written justification, which stays on the record.
- 05
A late check is flagged, not forgotten.
A check past its due time turns orange; past the delay you accept, the supervisor is told. Skipping a check requires a reason.
From the control plan to the Pareto of rejects.
Triggers by event, time or quantity
At the start of an order, at the start of a shift or when a component is consumed; every so many minutes; or every so many parts. Each with the delay you accept before it counts as late.
Scoped to where it applies
A check can apply to one machine, one article, a whole workshop, or every machine but a few. The operator sees only what is due, most urgent first, and can start a check on demand.
Rejects declared at the cockpit
Quantity on a numpad, reason from a tree of defects with your own codes. The quality factor of OEE is updated on the server as soon as the declaration is saved.
The chain behind every non-conformity
The quality history shows each check with its rechecks in sequence, so how many attempts a point took to conform is a fact on file, not a recollection.
Pareto charts of rejects
Rejects by reason, machine and period, from the same records the OEE comes from, next to the Pareto of stops.
Release with a reason
A lot is released, quarantined or rejected by the roles you authorise, with a written reason for every change of state. Who decided, when and why stays with the lot.
What the module commits to.
- Triggers
- Order start · shift start · component consumed · time · quantity
- Scope
- Machine · article · workshop · exclusions
- Recheck
- None · failed points · full check
- Critical points
- Supervisor alerted at once
- Reject reason
- Required, from an active reason
- Forced release
- Written justification required
Frequently asked questions.
Bring one of your control plans and ask the engineers how it would be set up.
Book a callWhen its trigger fires: an event such as an order or a shift starting, a time interval, or a quantity of parts. Checks are listed by due time, most urgent first, and can also be started on demand.
The check is recorded with its non-conforming points. Depending on how the check is configured, a recheck of the failed points or of the whole check is scheduled; if the point is critical, the supervisor is alerted at once and the operator must add a comment.
Not by default: a non-conforming releasing point keeps the lot blocked. A supervisor can force the release with a written justification, which stays on the record.
Yes. A reject declaration updates the quality factor on the server as soon as it is saved, for the order it was declared against.
Those standards certify a quality system, not a piece of software. VZIAM MES keeps the records an auditor asks for (checks, rechecks, release decisions and their reasons), and whether they satisfy a given audit is for your auditor to judge.
Plan the change before it reaches the line.
Request a demo and an engineer looks at how your production runs today, shows how the software would fit around it, and where a pilot on one line would start.
01Pick a time
Choose a slot in the calendar, and note what you make and what reads your machines today.
02Screen shared with an engineer
A video call with someone who builds the software, in English or French.
03What would connect
For each machine, its path: native (OPC UA, MQTT or HTTP push), through a gateway, or nothing to build.