1. Home
  2. Solutions
  3. Factory intelligence
  4. PLC data connectivity

PLC Data to Cloud in Qatar

Read run states, counts and process values from the Siemens, Rockwell and other PLCs you already run, over OPC UA, EtherNet/IP or Modbus TCP, without touching the control logic.

OPC UA, EtherNet/IP, Modbus TCPOther driversRead-onlyNo change to the PLC programEdge gateway on siteQuoriam Edge QE35

Last updated

Quoriam integrations screen with nine connected systems, including PLCs on Line 2 and pump stations PS-1 to PS-5 read over OPC UA, 1,126 tags, last synced one second ago with no errors
Illustration: Quoriam's integrations screen, with PLC tags from a production line and five pump stations syncing live.

What does PLC data to cloud mean?

Getting PLC data to the cloud means reading values a controller already holds, such as run state, counts, speeds and temperatures, and sending them to a platform outside the control network. An edge gateway reads each PLC over OPC UA or its native protocol, read-only, and forwards the values, so production and maintenance teams see them live.

Each PLC already knows whether its machine is running, how many units it made and how hot the glue tank is. The question is how to get those values out without risking the line: a read-only connection through a gateway in its own network zone, with your automation team agreeing every tag.

This is the layer under OEE monitoring and downtime tracking: once the tags are mapped, both run on the same feed.

SCADA exports

The data sits on one site's server and leaves by spreadsheet.

Changing the PLC program

New logic to push data out, with a stop and retesting.

Read-only edge gateway

Reads the tags the PLC already exposes. The program stays as it is.

Four protocols, and what each one needs.

How the gateway talks to a PLC depends on its make and age.

Common PLC protocols, the controllers that use them, and what to check first
ProtocolCommon onWhat to check first
OPC UAVendor-neutralSiemens S7-1200 and S7-1500, many other modern PLCs, SCADA and OPC serversServer switched on; on Siemens CPUs, an OPC UA runtime licence per CPU; a user with read-only rights
Siemens S7ISO-on-TCP, port 102Siemens S7 PLCs, S7-1200 and S7-1500 includedOn S7-1200 and S7-1500, PUT/GET access and non-optimised data blocks; PUT/GET also allows remote writes
EtherNet/IPCIP, TCP port 44818Rockwell Allen-Bradley ControlLogix, CompactLogix and Micro800Controller tag names; explicit messaging runs over TCP
Modbus TCPPort 502Older PLCs, drives and metersA register map from the machine builder, since Modbus registers carry numbers only

Sources: OPC UA, OPC Foundation; licence per CPU, Siemens Industry Mall (S7-1200) and OSD Schenck (S7-1500); S7, Coreflux and Industrial Monitor Direct; EtherNet/IP, Wikipedia and Software Toolbox; Modbus TCP, Nanotec. Older and proprietary protocols are reached through middleware such as Kepware or Ignition, so any controller either of them supports can be connected.

Network segregation, by zones and conduits.

IEC 62443 groups plant assets into zones with the same security needs, joined by conduits that control what crosses between them.

Network segregation, by zones and conduits.
ElementIn IEC 62443 termsIn a Quoriam connection
Control zonePLCs, HMIs and SCADA that run the processUnchanged. The gateway reads from it through a conduit you control
Conduit to the PLCsA defined path between zones, enforced by firewall rules as specific as possibleNamed PLCs, named ports, requests from the gateway only
Gateway zoneA separate zone between the control network and the business networkThe edge gateway sits here
Conduit to the platformThe path out to the business network or the internetOutbound from the gateway to the Quoriam platform
Security levelA target level for each zone and conduit, set from a risk assessmentSet by your OT security team; the gateway is configured to it

Zones, conduits and security levels: INCIBE-CERT and Automation.com.

How it works.

  1. Survey

    With your automation team, we list each PLC's make, model, firmware and protocol, and agree the tags to read.

  2. Connect

    The Quoriam Edge QE35 connects through the conduit your OT team approves and reads each PLC over OPC UA or its native protocol, read-only.

  3. Map

    Each tag gets a name, a unit and a machine, so LB-204's glue temperature reads as that everywhere.

  4. Watch the link

    Uplink, sync times and errors are monitored, with an alert if a PLC stops answering.

Isometric illustration: an industrial site, with the Quoriam platform above it as a live dashboard and the decision layer on top

System view

For IT, OT and security reviewers: where the data goes, and how.

  1. On the linePLCs, SCADA or an existing OPC server
  2. At the edgeQuoriam Edge QE35 in its own network zone, read-only
  3. NetworkPlant network or cellular, encrypted and kept apart from the control network
  4. Quoriam platformOn your premises or cloud hosted in Qatar
  5. Your team and systemsOEE, downtime and maintenance on Quoriam; data to your ERP

Hardware and integrations.

One gateway per line or hall, reading what is already there.

  • Quoriam Edge QE35 gateway, front view
    Edge gatewayQuoriam Edge QE35, on the plant network or its own zone
  • Existing OPC servers
    SCADA or a plant OPC UA server, read instead of each PLC
  • Milesight EM300-DI pulse counter
    State and count sensorsOnly on machines without a PLC
Reads from
PLCs over OPC UA, Modbus TCP and EtherNet/IP; SCADA over OPC UA
Writes to
Nothing on the control network
Sends to
The Quoriam platform; ERP systems

Hardware agnostic. Makes we fit includeWe can work with any maker and choose the device for each site. The platform reads them all.

What your team sees.

What is connected, and what the tags turn into.

Quoriam integrations screen listing nine connected systems, including PLCs via Ignition 8.1 over OPC UA with 1,126 tags on Line 2 and pump stations PS-1 to PS-5, last synced one second ago with no errors
Integrations. Each system with its protocol, last sync and errors; here, PLCs read over OPC UA through an Ignition server.
Quoriam devices and gateways screen with 412 of 418 devices reporting, gateway uplink health over 24 hours, and wired devices such as BTU-17 read over Modbus TCP through edge gateway EDGE-LT-01
Devices and gateways. Gateway uplink health and each device's protocol.
Quoriam line status board for Line 2 with seven machines, each showing state, speed against rated and time in state, the labeller marked as the constraint
What the tags become. Run state, speed against rated and time in state, per machine.

Where it's used in Qatar.

Anywhere useful data is locked in a controller.

  • Production lines

    Food, packaging and building-materials lines in Mesaieed and the free zones.

    Manufacturing
  • Pump stations and utilities

    PLCs at unmanned stations, read for run status, pressure and flow.

    Remote operations monitoring
  • Oil, gas and energy

    Package PLCs on compressors and skids, read without changing the vendor's program.

    Oil, gas and energy

Questions buyers ask.

Something else? Ask us during the free assessment.

How do you get PLC data to the cloud?

An edge gateway on the plant network reads tag values from each PLC, over OPC UA or the PLC's own protocol, and sends them to the Quoriam platform. The PLC program is not changed. Your automation team approves the tags and the network path.

Is it safe to connect a PLC to the cloud?

With the right design, yes. IEC 62443 separates the control network into zones joined by controlled conduits; the gateway sits in its own zone, reads PLCs read-only and connects outward to the platform. Your OT security team sets the target security level and the firewall rules.

What is OPC UA?

OPC UA is a vendor-neutral standard for exchanging industrial data, released by the OPC Foundation in 2008. It runs on anything from a PLC to a cloud server, and supports certificate authentication, signed and encrypted messages and audit logs. Many modern PLCs have an OPC UA server built in, sometimes behind a licence.

Which PLCs and protocols do you support?

Siemens, Rockwell, Schneider, ABB, Mitsubishi and Omron controllers, among others, over OPC UA, Modbus TCP or EtherNet/IP, and SCADA over OPC UA. Older PLCs and proprietary protocols are reached through middleware such as Kepware or Ignition, so anything either of them supports can be connected, and the list keeps growing. Send us the make, model and firmware of each PLC and we confirm the route.

Do we need to change the PLC program?

No logic changes. Some PLCs need a setting changed first: switching on the OPC UA server, adding its licence, or on Siemens S7-1200 and S7-1500, allowing PUT/GET access. Each means a download to the PLC at a planned stop. We prefer OPC UA, since PUT/GET also opens remote writes.

What hardware is needed?

One Quoriam Edge QE35 gateway usually serves a line or a hall, on the plant network or a separate zone. Machines with no PLC get a state or count sensor. Where you already run SCADA or an OPC server, we can often read that instead of each PLC.

What does a PLC connection cost?

It depends on how many PLCs you connect, their protocols and the network work needed. Most plants start with one line as a pilot. The free three-week assessment surveys your PLCs and network, then gives a scope and a fixed price.

Get the data out without touching the line.

A free three-week assessment. We survey your PLCs, protocols and network with your automation team, then recommend the safest route for each machine.

We take on two assessments a month.

Quoriam is designed to pay back within six months. How we calculate payback