Every modern plant carries a serial-era heritage: meters, burners, compressors, chillers — healthy devices speaking yesterday’s protocol. Three integration patterns cover practically all of it.
Pattern one: the PLC as gateway
The machine’s own S7 polls its Modbus devices (CM module for RTU, MB_CLIENT for TCP) and folds the data into its interface DBs. Right when the devices belong to the machine — its burner, its chiller: one owner, one diagnostic world, data flowing upward through the same OPC UA/Profinet contract as everything else. Wrong when devices are shared plant infrastructure — a PLC that happens to poll the site’s meters becomes an accidental utility with an SLA nobody signed.
Pattern two: the dedicated bridge
A protocol gateway presents the serial device as a Profinet device (see our gateway selection notes). Right for single serious devices needing to look native to the control layer — a legacy analyzer feeding a Profinet line — and for keeping third-party scope contractually separate.
Pattern three: the edge concentrator
One box (industrial PC or IoT gateway) polls fleets of Modbus devices and publishes upward (OPC UA server or MQTT). Right for meter parks, building systems, anything read-mostly at relaxed rates. Concentrates the register-map archaeology in one maintainable place, keeps forty conversations off the PLCs entirely — and matches how energy-monitoring projects actually grow.
Cross-cutting rules: every polled device gets a health flag someone sees; register maps live in the dossier; and stale-data behavior is configured, never defaulted.
FAQ
Latency expectations through these paths? Seconds-class end to end for concentrator patterns — fine for their read-mostly nature; control-relevant devices deserve pattern one or two.
When is replacing the device honest? When integration engineering approaches the price of a native-Profinet successor — common for small sensors, rare for big packaged equipment.
Zone Otomasyon has integrated meter parks, burners and thirty-year-old chillers without replacing what works. Legacy integration.