nl
Book a demo

Know which customer got which batch.

Solution 06 · Quality + Production modules

Enter an order number and you see machine, operator, raw material and every measurement from that day. Three years later too.

Try it on one product groupHow it works
What changes

From half a day of searching to two minutes.

Today
  • A complaint or audit costs half a day of digging through folders.
  • You don't know exactly which material lot went into which delivery.
  • When in doubt you block more stock than necessary.
With AIONIX
  • Everything we measure is linked to order and batch automatically.
  • On a complaint you see within two minutes what happened that day.
  • You block only the batches that are actually affected.
In the portal

This is how it looks in the AIONIX portal.

portaal.aionix.be/production/history
AIONIX portal, timeline per machine with stops and reasons
Timeline per machineEvery minute of the day, per line, ready to rewind.
Every stop with a reasonFrom emergency stop to maintenance, with duration and cause.
Export for customer or auditPick a period, export, send it on.
How it works

Capture, link, retrieve.

Step 01

Capture

Every measurement, stop and registration automatically gets a timestamp, machine and operator.

Step 02

Link

Order, batch and material lot are tied together, with no extra work for the floor.

Step 03

Retrieve

You search by order number or batch and get the full story, ready to send on.

The chain

What hangs on a batch.

Traceability is not a separate archive. It is the set of references that appears once every registration lands on the same data layer.

  1. 1

    Material

    Which raw material, which supplier, which delivery number. Where a supplier gives no batch number, you register at delivery or pallet level.

  2. 2

    Production order

    Which order consumed the material, and how much of it. This is the link the ERP does not make.

  3. 3

    Machine and time

    Which line it ran on, in which hour, with which recipe and which parameter version.

  4. 4

    Operator and shift

    Who ran it and who did the check. Not to hold anyone to account, but so a deviation can be asked about.

  5. 5

    Measurement

    The quality registration belonging to that order, with the tolerance that applied at the time.

  6. 6

    Delivery

    Which batch went to which customer. This is the link that decides the scope of a recall.

How far the chain runs is your call. Every extra registration point costs time on the floor, so we start from the question you cannot answer today.

Who works with it

The same batch number, four different questions.

Operator

Scans what they use

Material and batch against the order, on the screen at the line. No separate notebook.

Quality manager

Walks from complaint to batch

From a customer complaint back to the order, the machine, the shift and the material that went into it.

Production manager

Knows the scope

On a problem the question is how much was affected. That is a search, not a reconstruction.

Managing director

Limits the damage

A targeted recall of the batches involved instead of everything as a precaution.

What customers ask first

Five questions about traceability.

So do we have to scan everything?
No, only what you need to find again later. We start from the question you cannot answer today, usually which material went into which order, and register the minimum for that. You can always add more later; every extra scan point costs time on the floor.
What if a supplier gives us no batch number?
Then you register at the level you do have: a delivery, a pallet, a date. The chain gets coarser there, and the system shows it that way. An honest link that is broad beats one that pretends to be precise.
How fast do we know which customers got a batch?
That is a search on the batch number, not a day in the archive. You get the orders the batch went into and the deliveries that left from them. How far that chain runs depends on what you register.
How long is that history kept?
As long as you need it, and you decide that. Some sectors work to a shelf life plus a margin, others to the lifetime of the product. We agree the retention period up front, because it shapes how much you register and what it costs to keep.
Is this enough for our sector?
That varies too much to answer here. What a food producer has to demonstrate is not what a supplier to the construction industry has to demonstrate. We start from what your customer or auditor asks for and set the registration up so you can show it.
How it connects

Traceability is what the other modules leave behind.

Traceability isn't a separate archive you fill in. It's what emerges once the modules of the MOM platform all register on the same data layer.

Production monitoring

Production supplies the skeleton: which order on which machine, with which operator, at what time. Without that registration there is nothing to hang a batch on.

Quality

Quality attaches the measurements to that same order. That is what turns an audit question about one batch into a search instead of a reconstruction from paper.

Work orders

What the operator registers at the line is the detail traceability lives on. Leave it on paper and the trail stays in the filing cabinet.

To see what per-item traceability delivers, read how Depro Profiles keeps an image of every panel in the cloud. How modules give each other context is covered in modular MES in practice.

For manufacturers in West Flanders

Put your entire shop floor on the same platform.

No 'big bang'. As a West Flanders-based team, we start at your SME with the first module on the first line, prove the value, and build out together to your full platform, at the pace and budget of an SME.

Book a demo