PLC Data Collection and Machine Connectivity

How PLC data collection works

Each controller is read in its own protocol. Talking S7 to a Siemens CPU or ADS to a Beckhoff means reading the data blocks your engineers already maintain, at cycle-level rates, with no translation layer in between that drops context or adds delay. Commissioning a controller is measured in hours: point the driver at its IP address, map the tags agreed with whoever maintains the programme, and the data starts to arrive. On an S7-1200 or S7-1500 the CPU project needs PUT/GET access enabled and non-optimised data blocks.

Supported controllers and protocols

Native drivers cover nine PLC brands: Siemens (S7comm/Step7 and S7-Light, from S7-300/400 to S7-1200/1500), Rockwell Automation / Allen-Bradley (AB-ETH, Logix, DF1), Schneider Electric (UMAS), Beckhoff (ADS/TwinCAT), Mitsubishi Electric (MC Protocol), Omron (FINS), Delta (DVP), Keyence (KV) and WAGO. Injection moulding machines connect over EUROMAP 63, and Fanuc controls through FOCAS. Everything else goes over the open protocols: OPC UA, Modbus TCP and Modbus RTU for drives, meters and older controllers, EtherNet/IP in Rockwell- and Omron-based plants, and MQTT where a publish-subscribe pipeline suits IT better. The driver-by-driver list is in which PLCs work with MSF.

Plants that already run SCADA or an OPC server have a third route. MSF reads the existing OPC UA/DA server and the tag tree it already curates, and PROFINET, BACnet and DNP3 are collected through that layer. No new device talks to the controllers, which is often the fastest path where nobody wants one on the control network.

What the data feeds

Machine states, counts and cycle times are what the manufacturing execution system runs on: live order status, OEE and TEEP per machine, line and plant, and a Pareto of downtime and scrap. Where a controller exposes alarm or fault codes, they map to stop reasons, so short stops no longer vanish from the record. Before trusting the numbers, the OEE data quality audit checks how each one is captured.

The same events trigger counter-based preventive work in maintenance (CMMS), join power readings in energy management to give energy per product, and close the ERP work-order loop: counts flow back and the goods receipt is posted to the ERP without a manual entry. What an MES does with that data is covered in a separate guide.

Machines without a usable PLC

A press with a contactor panel has no controller worth talking to. META Smart I/O reads its run contacts, cycle signals and alarms through an interposing relay or isolated input, so the machine's own circuit is neither loaded nor altered, and safety circuits are never tapped. MSF IIoT cards report running, idle and stopped on machines without a PLC, and AI cameras count where no signal exists at all. In a typical plant the native drivers cover the newer machines and retrofit I/O the older ones, and the MES sees one consistent stream from both. The legacy machine connectivity assessment gives a preliminary connection method for each machine before any hardware is ordered.

Read-only by default

Collection is read-only: no write items configured in the collector, a tag or DB list agreed with whoever maintains the programme, and the PLC on its own VLAN, with all communication going outbound over TLS through a secure gateway proxy and role-based access on top. Anything that writes back to a machine, such as a recipe download or a setpoint push on changeover, is a separate connection scoped on purpose. The information security management system (ISMS) of Meta Smart Factory d.o.o. is certified to ISO/IEC 27001:2022, and the certificate covers how the platform is designed, developed, deployed, operated, maintained and supported, including its cloud-hosted infrastructure.