Resources
Traceability, written by the engineer who built it
No gated whitepapers and no vendor gloss. These are the things we had to work out to ship the product, written for the person who has to make it work on a shop floor.
- Audit and compliance8 min read
What an IATF 16949 auditor actually asks for on traceability
Clause references are easy to quote and not much use at 09:00 on audit day. This is what gets asked for in the room, and what a record has to contain to answer it.
- Machine integration9 min read
Capturing torque data from a PLC over RS485 without losing readings
Getting a number out of a torque controller is easy. Getting every number, tied to the right unit, with a timestamp you can defend, is the actual job.
- Data modelling7 min read
What a part genealogy record must contain
Most genealogy implementations answer the backward question well and the forward question badly. The cause is almost always one modelling decision made early.
- Marking7 min read
Laser marking or label printing for traceability
Both are legitimate. The decision is made by your process, not by preference, and the expensive mistake is in the scanner budget rather than the marker.
- Quality operations8 min read
Planning a recall scope calculation before you need one
A recall is not the time to discover what your records cannot answer. Run the query now, on a lot you chose at random, and find out.
- Buying8 min read
MES or standalone traceability: choosing without over-buying
The honest version of this comparison is not which is better. It is which problem you have, and whether you can afford the one that solves more of them.
Would you rather just ask?
If one of these is close to a problem you have, call and ask. We will give you the answer whether or not it leads anywhere commercially.