{"id":158495,"date":"2026-11-03T08:50:22","date_gmt":"2026-11-03T08:50:22","guid":{"rendered":"https:\/\/teeptrak.com\/downtime-data-without-plc-connection-sensor-layer\/"},"modified":"2026-11-03T08:50:22","modified_gmt":"2026-11-03T08:50:22","slug":"downtime-data-without-plc-connection-sensor-layer","status":"publish","type":"post","link":"https:\/\/teeptrak.com\/en\/downtime-data-without-plc-connection-sensor-layer\/","title":{"rendered":"Downtime data without a PLC connection: adding a sensor layer next to your plant-floor integration"},"content":{"rendered":"
This article is for plant managers, production managers, continuous improvement leads and maintenance managers who are planning, or already running, a plant-floor data integration project, and who keep running into the same question: what do we do with the machines that have no usable PLC connection? It explains where stop data comes from on those machines, how a non-intrusive sensor layer fits next to a full integration architecture, and how to decide machine by machine which path makes sense.<\/p>\n
\n
In short<\/div>\n
\n
Many plants mix networked lines with legacy machines that have no usable PLC data.<\/li>\n
A full plant-floor integration is the right path when clean controller tags exist.<\/li>\n
A non-intrusive sensor layer captures stops on the machines integration cannot reach yet.<\/li>\n
Shared stop definitions keep OEE comparable whichever layer produced the data.<\/li>\n<\/ul>\n<\/div>\n
Two kinds of machines on the same shop floor<\/h2>\n
Walk through almost any plant that has been running for a few decades and you will find two populations of equipment side by side. On one side, recent lines with modern controllers, a clean tag structure and a network connection that a controls engineer can reach. On the other, presses, lathes, packaging machines and test benches that still do their job perfectly well, but whose controller is obsolete, locked, undocumented, or simply not there because the machine runs on relays.<\/p>\n
The first population is the natural territory of a plant-floor integration project: read the tags, contextualize them, exchange data with the MES and the ERP. The second population is where many projects stall. The machines are not strategic enough to justify a controller upgrade, but they are often exactly where the stops, the micro-stops and the long changeovers hide. Leaving them out of the data means the picture of the plant stays incomplete, and the improvement work keeps relying on handwritten logs for part of the floor.<\/p>\n
What a full plant-floor integration brings<\/h2>\n
![\"Four](\"https:\/\/teeptrak.com\/wp-content\/uploads\/2026\/11\/teeptrak-dmc-en.png\")
<\/figure>\n