Industrial IoT

Can an existing PLC be connected to the cloud?

By the Vera Automation engineering team · Updated

Short answer

Yes — in most cases an existing PLC can be connected to the cloud without replacing it or changing its control logic. An edge gateway on the plant network reads selected tags from the PLC over a protocol it already supports — such as Modbus TCP, OPC UA, EtherNet/IP or Siemens S7 — and publishes them securely over MQTT or HTTPS. The connection should be read-only and outbound-only, and the PLC itself should never be exposed to the internet.

The four common approaches

ApproachHow it worksBest for
Edge gateway reads the PLCA gateway polls tags over the PLC’s native protocol and forwards themMost existing installations — no PLC changes
PLC’s built-in OPC UA serverNewer PLCs (for example Siemens S7-1500) expose tags via OPC UA to a clientModern PLCs with OPC UA licensed or enabled
Add a communications moduleA module adds Ethernet or a protocol the PLC lacksOlder PLCs with only serial ports
Read from SCADA or a historianTake data from the existing SCADA instead of the PLCSites that already have SCADA collecting everything

Protocols by PLC family

  • Siemens S7-300/400/1200/1500: S7 protocol, OPC UA on newer models and firmware, Modbus TCP via function blocks.
  • Allen-Bradley (Rockwell) CompactLogix / ControlLogix: EtherNet/IP (CIP), OPC UA through add-ons or gateways.
  • Schneider Modicon: Modbus TCP natively on most models, OPC UA on newer ones.
  • Older or smaller PLCs: Modbus RTU over RS-485 or RS-232, read through a serial gateway.

What to read

Start with a short, agreed list of tags that answer real questions: running states, alarms, counts, levels, flows, pressures, energy and run-hours. Reading hundreds of tags “because they are there” loads the PLC network and buries the useful data. Document each tag with a clear name, unit and description — this naming becomes the foundation of your dashboards and reports.

Security rules

  • Read-only by default: the cloud should not be able to write to the PLC unless there is a specific, reviewed need.
  • Separate the OT network from office IT, with the gateway as the controlled bridge.
  • Unique credentials and certificates per gateway; no default passwords.
  • Take a PLC program backup before any work, even when no logic is changed.
  • Frameworks such as IEC 62443 are a useful reference for industrial security design.

What it enables

Once plant data reaches the cloud it can feed live dashboards, alarm notifications, production and energy reports, maintenance planning and integration with ERP systems — without touching the control logic that keeps the plant running. See industrial IoT integration and PLC programming.

FAQ

Frequently asked questions

Will reading data from the PLC affect its performance?

Reading a sensible number of tags at a sensible rate has negligible impact. Polling thousands of tags every few milliseconds can load the PLC’s communications, which is why the tag list and rates are agreed up front.

Do we need to change the PLC program?

Usually not. Some PLCs need a setting enabled (such as permitting access for the S7 protocol or enabling OPC UA), and occasionally a small data block is added to collect values neatly.

What if the PLC is very old?

Serial-only PLCs can be read through a serial gateway, or the connection can be taken from existing SCADA. If the PLC is obsolete, it may be time to plan a migration.

Next step

Tell us what’s slowing you down.

Describe the process, the system or the site. We’ll come back with a clear, practical view of what can be automated — and what it would take.