Resource
Link Machine Data To Manufacturing Jobs
Why machine monitoring alone produces figures that are difficult to relate to production decisions, and what changes when telemetry is joined to the job.
Machine monitoring is usually sold on utilisation. A screen appears in the office, everybody looks at it for a fortnight, and then it becomes wallpaper.
The reason is not that the data is wrong. It is that a percentage with no context does not tell anybody what to do differently.
What Changes With Context
When a reading is joined to the works order and operation that were running, the questions become answerable in operational terms.
- A machine stopped for four hours — which order was on it, and is that order now late?
- This operation was quoted at ninety minutes and the machine says it ran for three hours. Is the routing wrong, or was that job unusual?
- A machine has stopped reporting while a job is booked to it. Is it broken, or is the collector down?
Protocols, Briefly
MTConnect is an open standard for machine data, maintained by the MTConnect Institute, and is well supported on newer controls. Modbus is older, widely implemented and much simpler. FANUC controls are commonly read through FOCAS, which needs a library from the manufacturer.
What a given machine can report varies enormously, and age matters more than brand. Establishing what your controls actually expose is a job for the start of a project, not an assumption at the end of one.
See Keystone Precision With Your Manufacturing Workflow
A tailored walkthrough follows one of your jobs from customer demand through planning, production, quality and despatch.