MESoperator execution that writes its own batch record.
V5’s MES isn’t a dashboard — it’s the kiosk in the operator’s hands. Every action is signed, in sequence, with the device evidence already attached.
The kiosk IS the eBMR.
Watch a single batch step happen on a real station. Every tap captures evidence, hashes it, and refuses to advance unless the recipe agrees.
Bulk silos, full bags, minor weigh-ups — all converging on one batch record.
Watch the actual plant flow: a silo meters flour to the mixer while an operator scans and tips a 25 kg bag, a second operator weighs a 38 g minor into a tared scoop, the tank line opens a metered shot of oil, the blend drops, fills the line, and pallets walk out the door with a GS1 label. Every step is a tap on a kiosk and a hash on the eBMR.
Silo SI-04 meters flour to the blender
The recipe asks for 482.0 kg of bulk flour. The silo driver opens the rotary valve, the load cell trickles to target, and the kiosk shows live kg climbing. Operator only watches — no manual scoops at this scale.
- SI-04 · lot K228 · QA released
- target 482.000 kg · actual 482.014 kg · in band
- valve auto-trim at 480.5 → 0.4 kg/s → 0.05 kg/s
An MES isn't a logger.It's a four-way handshake.
Every step on the V5 kiosk is rejected unless the operator is trained, the equipment is in cal, the recipe revision is the one the WO was released against, and the lot is the lot the picker actually staged. Four signals, one handshake. No handshake, no step. No step, no record entry.
Watch a step bind itself, one signal at a time.
What the operator sees: a step that physically can't be touched until the four signals are present. What the system sees: a hash being assembled from cryptographically signed inputs.
- Operator scans badgeOPERATOR: M. Aoki · skill: weighing v3.1 ✓
- Operator scans equipment
- Recipe pulled from WO
- Operator scans staged lot
- Handshake complete — step unlocked
The recipe can't change under a running batch.
When the WO is released, V5 takes a hash-sealed snapshot of the MMR at that exact second and binds it to the WO forever. If R&D publishes rev 5 mid-shift, this batch keeps running on rev 4. The next released WO picks up rev 5. Old batches stay reviewable against the version they were actually made on.
- 21 CFR 211.100(a) — written and approved procedures
- ISO 13485 §7.5.1 — controlled production
- EU GMP Annex 11 — version control of computerised systems
The four things a V5 kiosk will physically refuse.
Step 7 cannot open while step 6 is unsigned. The button doesn't exist on this device until step 6 closes.
12.572 kg into a 12.500 ± 0.025 envelope returns a 409. Operator gets a deviation ticket — not a re-tare.
Scanned L-24-0917-B against staged L-24-0918-A? Refused. Audit trail records the attempt.
SOP rev moved to v3.2 yesterday. Operator trained on v3.1. Step is locked until training is re-acknowledged.
Variance shows up while the batch is still alive.
V5 tracks running yield as each component is added. If you're 3% under by step 6, the supervisor's phone buzzes — not the month-end COGS report. By the time the batch posts, there's already a deviation ticket attached and a CAPA owner assigned.
A floor that can't be wrong is a floor that doesn't need to be checked.
The handshake is the difference between an MES that records what happened and one that decides what's allowed to happen.
Curious how the MES actually behaves at the kiosk?
Where AI actually earns its place.
AI rides alongside execution — it reads the batch as it runs, flags what a supervisor would catch on a good day, and drafts the paperwork nobody enjoys writing. Every output is a suggestion an authorised human signs or rejects.
- 01
Deviation drafted the moment a step breaks
When a reading falls out of band, AI writes the deviation narrative from the actual step data — equipment, lot, operator, timestamps, prior occurrences on the same line — so QA edits a draft instead of starting from a blank box.
Typical deviation write-up drops from ~40 minutes to a few minutes of review.
- 02
Batch review-by-exception triage
At batch close AI ranks every exception by regulatory weight and product impact, groups repeats, and puts the two things that actually matter at the top of the reviewer's queue.
Reviewers stop scrolling 200 clean steps to find the two that aren't.
- 03
Yield-variance root-cause hints
Where yield drifts, AI correlates the batch against operator, shift, scale, ambient conditions and raw-material lot, and proposes the two or three most likely contributors with the evidence behind each.
- 04
Paper SOP to executable steps
Drop in an existing Word or PDF procedure and AI proposes the step sequence, tolerance bands, signature points and witness rules. Engineering adjusts and approves through normal change control.
Cuts first-recipe build time from days to an afternoon.
- 05
Ask V5 on the kiosk
Operators ask 'what does this step mean?' in plain language and get an answer sourced from the effective SOP version — not a guess, and not the version that expired last quarter.
AI never signs, never releases a batch, and never overrides a tolerance gate. It drafts, ranks and explains; a trained human with the right authority makes every regulated decision, and the audit trail records who accepted or changed the suggestion.
The eBMR is the single source of truth — everything binds to it.
Scales, printers, lab instruments, ERP, doc control, maintenance — each system reads from or writes to the same batch record in real time. No spreadsheets in the middle.
Wondering how V5 MES plugs into your stack?
The edge cases the floor actually lives in.
Real production isn't a happy path. Here are four moments the MES has to nail — and how V5 nails them.
Network drops mid-batch
Kiosk keeps executing locally against the snapshotted MMR. Signatures and readings cache; reconcile when the link returns — order and timestamps preserved.
Lot runs out mid-dispense
V5 prompts for a second approved lot, captures both as a structured split, and writes both to genealogy. No paper note, no reconciliation later.
Step needs to be unwound
Reversal is a recorded e-signed action — not a delete. Original reading stays in the audit trail; reason code mandatory; downstream re-locks until the new value is in band.
Branching SOPs (AQL pass/fail)
Decision points route the operator down the correct branch automatically; the path taken is part of the batch record so QC reviews the route, not just the outcome.
Got an MES edge case the team's worried about?
Just ask V5 — it knows the product cold.
Pick a question or type your own. V5 answers grounded in how mes — manufacturing execution for regulated shop floors | v5 ultimate actually behaves on the floor.
The rest of the platform this plugs into.
V5 isn't a bolt-on. Every module shares the same data, the same audit trail, the same operator. Pick where to look next.
WMS
Receiving, putaway, transfers, cycle counts, picks, pack & ship — all lot-aware, bin-accurate, FEFO/FIFO-enforced and barcode-driven.
QMS
Built-in QMS: deviations, CAPA, supplier scorecards, in-process AQL, release-by-exception. Aligned with 21 CFR 211/820, ISO 13485 and 111.
Document control with hard kiosk-level training enforcement.
Versioned SOPs, two-person e-sig approval, training acks, hard kiosk block on day one if assigned docs are overdue or unacknowledged.
Got questions, or want to see it on your shop floor?
Ask V5 — our code-aware assistant — or spin up a workspace. Both are free.