When upgrading, it's easy to wonder: should we keep the SCADA system or switch to an IIoT platform? The question is often poorly posed. First, it must be clarified which tasks are time- or safety-critical, and who needs to use the data outside the control room.

What does SCADA do well?

The primary value of SCADA is the monitoring and operator management of technological processes. It displays statuses, alarms and intervention options in close connection with local control and PLCs. Its predictable operation is especially important where a delay or incorrect command can have production, quality or safety consequences.

Fast and secure control loops should remain at the local layer they are designed and validated for.

What does IIoT add?

The industrial IoT layer can collect data from multiple devices, sites, and systems and make it available for analysis and other business processes. It can help you interpret energy and health data together, compare sites or integrate your maintenance system.

SCADA and local automationTime-critical monitoring and controlLocal operator operationTechnological alarmsValidated intervention logic
IIoT data and integration layerLinking data from multiple systemsLong-term storage and analysisSite ComparisonBusiness and Maintenance Processes

Collaborative Architecture

A common and sensible solution is for SCADA to provide local monitoring while a regulated gateway delivers selected data to the IIoT platform. The data flow can be one-way, if only analysis is the goal, or strictly controlled two-way, if authorized commands are also needed.

Machine and meter→PLC and SCADA→Controlled connection→IIoT platform→Business process

The interface must be documented and controllable. The time stamp, the unit of measure, the data quality indicator and the recording of which system is the authentic source of the given data are important.

Retrofit: not everything has to be replaced

For older equipment, a properly disconnected gateway can convert the necessary values ​​to a more standard data connection without having to rebuild the working control. It's worth starting with a small pilot: a few relevant signals, a clear use case and predefined success criteria.

Cyber ​​Security and Liability

Connecting the control network to enterprise or cloud systems brings new risks. Segmentation, least privilege, encrypted connection, logging and update responsibility are therefore part of the architecture. You should be especially careful with remote write options.

Decision Checklist

  • Which functions require local, deterministic operation?
  • What data is needed outside of SCADA and why?
  • Which system is the authentic source of each data?
  • Is one-way data transfer enough?
  • What happens in the event of a network or platform outage?
  • Are interfaces and permissions documented and logged?

Not a replacement, but a clean role

A good architecture preserves the local, fail-safe role of SCADA and supplements it with IIoT capabilities where sharing, analyzing or integrating data into a business process provides real value.

Let's discuss the integration