MOS / Modules / Production
MES BY MOS
Running in production

MES & Traceability

Every unit scanned at every station. Nothing skips a stage.

Serial traceabilityStage interlockBOM checkTest resultsLabel printingGenealogy
See it on my machineSee the screen
MES & Traceability screen 1 in MOS
The screen

What it looks like in MOS

Each unit carries a serial. At every station MOS checks that the unit passed every stage before it, that the parts fitted match the bill of materials, and that the test results are within limits — and only then lets the line move on. Labels print at the right station, quality holds stop a batch on the spot, and every unit keeps its full history from first station to the truck.

Download the one-pagerSee it on my machine
Product positioning

A unit that skipped a test should never reach the truck

Paper travellers and separate test-bench files let a unit miss a stage and still ship. The record exists — in five places that never meet.

“MOS scans the unit at every station, checks it passed every stage before, that the right parts were fitted, and reads the test results from the benches — then lets it move on, or holds it.”
Today
Station 1Station 2Test benchDispatchskipped test found at dispatch
With MES & Traceability
Station 1Station 2Test benchDispatchevery stage scanned and interlocked

Drawn, not promised: the top row is a unit walking past a test that nobody notices until dispatch — or the customer. The bottom row is the same unit refused by the next station until the stage before it is on record.

End-to-end flow

5 connected stages

Hover or tap a stage to see what is captured there.

01

Work order

Released
  • Model masters
  • BOM, routing
  • Test limits
02

Stations

Interlocked
  • Scan the serial
  • Previous stage checked
  • Parts checked vs BOM
03

Tests

Read
  • Leak, vacuum
  • Hi-pot, run test
  • From the bench
04

Release / hold

Decided
  • Label prints
  • Quality hold
  • Batch stop
05

Genealogy

Kept
  • First station to truck
  • Searchable by serial
  • Dispatch
Continuous threadWork order→Stations→Tests→Release / hold→Genealogy
Part of the platform

MES & Traceability runs on MOS

Not a standalone tool — a product on the MOS platform, sharing one login, one set of people and roles, and one database with every other module. The lit layers are the ones this product uses; the signal path shows how data moves through them.

  • MOS Edge runs inside the plant — interlocks and screens keep working if the internet does not.
  • MOS Central is a one-way mirror for head office and every plant in one view.
  • Your IT never opens an inbound port.
MOS CentralEvery plant, one viewin use
MOS EdgeYour plant serverin use
MOS CoreThe operating layerin use
MOS ConnectMachine connectivityin use
MOS VisionAI on the linein use
Core engine & extensions

What is core, what extends it, what is not claimed yet

The honest map, drawn as one thread. Filled nodes are in the product today; outlined nodes are other MOS modules on the same platform; dotted nodes are roadmap and never represented as available until built. Hover a node.

● Core

● Core — in the product today○ Extension — another MOS module◌ Roadmap — not claimed
Native engine

Core functionalities

Each card ends with the thing itself as it appears in MOS — not a description of it.

Model the line

Once per model

  • Stations and order
  • Parts fitted at each
  • Tests and limits
  • Label format
Scan & interlock

At every station

  • Serial scanned
  • Previous stage must pass
  • BOM serial check
  • Reason on refusal
Read the tests

Not typed

  • Leak & vacuum
  • Hi-pot & run test
  • From Modbus or the bench DB
  • Pass/fail on the record
Release or hold

Decided per unit

  • Label at the right station
  • Quality hold stops a batch
  • Release with who & why
  • Dispatch by serial
Operational journey

8-step digital thread

Step through it or let it play. Each step: who does it, on what, what is captured, and the check that guards it.

Step 1 / 8
Step 1 · Planning

Model the line

Stations, their order, the parts fitted at each and the tests each must pass are set up once per model.

WhereMasters
CapturedRouting, BOM, limits
Guard / interlock—
● live in MOS
Where it sits

Your ERP or Tally runs the books. This adds the ground truth.

Your ERP / Tally typically givesMES & Traceability adds
A paper traveller per unitA scan at every station, interlocked
Test results in bench filesResults read from the bench onto the serial
BOM assumedBOM serials checked at the station
Recall by date rangeGenealogy searchable by serial
Hardware & connectivity

Works with what a plant already has

Stations

A scanner and a screen or tablet per station

Test benches

Read over Modbus or from the bench's own database

Labels

Label printers where labels are applied

Server

MOS Edge in the plant; works if the link drops

At a glance

The spec

What it connects to, where it runs and what it gives you — the short version your IT and your plant head both want.

ReadsScanners, test benches (Modbus or their DB), label printers
Runs onMOS Edge — in-plant, works if the link drops
Needs on siteA scanner and screen per station; bench results on the network
OutputsPer-unit genealogy, stage results, labels, quality hold/release, dispatch
Licensed byPer line / per station count
Capability transparency

What is built, what extends, what is not claimed

Core — today

Work orders, stage interlock, BOM checks, bench results, labels, hold/release, genealogy, matching.

Extension

MOS Face (operator verification) and MOS OEE on the same stations.

Integration-dependent

Each bench's protocol or database is connected at site.

Roadmap

Supplier-lot genealogy — not represented as available.

Capabilities depend on the plant's process and what is connected at site. Nothing on this page is represented as available until it is built and running.

What you get

6 outcomes

No unit skips a stage Test results on the serial, not in a file The wrong part caught at the station A batch held in one click Full history per serial Labels at the right place
Who uses it

Everyone sees what their job needs

Operator

A clear go / no-go at the station, with the reason

Quality

Holds, releases and every test result by serial

Production

Output per station and hour, first-pass yield

Dispatch

Only released units, matched and labelled

On site

What is needed in your plant

At each station

A scanner, and a screen or tablet for the go / no-go.

At test benches

The bench result read over its network or from its files.

In the plant

The MOS plant server and label printers where labels are applied.

Rollout

From the first day to the first month

Day one

The line is modelled

Stations, order, parts and tests set up with your team.

Week one

Interlocks switched on

Stations scan and refuse units that skipped a stage.

Month one

Genealogy end to end

Every unit traceable from first station to truck.

Questions

Asked about MES & Traceability

What if the network fails at a station?

The station keeps its last state and the plant server runs locally; scans are queued and posted when the link returns.

Can a supervisor override an interlock?

Only a role you allow can release a held unit, and every release is recorded with who and why.

Works with

The rest of MOS

On your own machine

See it on your own machine.

Tell us about your plant and what you want to see. We visit, connect one machine or station, and you watch your own data in MOS before anything is quoted.

  • A plant visit to see the line and the problem
  • One machine or station connected as a proof of concept
  • Your own data, live, on MOS screens
  • Scope, modules and timeline agreed in writing only after that
Thank you — request received.We will call you shortly to plan the visit.