SCADA vs. Industrial IoT Architecture, Integration, and Where Each Fits

SCADA and Industrial IoT (IIoT) are often discussed as competing technologies. From an engineering perspective, they typically solve different problems.

SCADA provides supervisory monitoring and control of industrial processes.

IIoT extends operational data across systems, sites, and applications.

In many modern architectures, they work together.

What Is SCADA?

SCADA, or Supervisory Control and Data Acquisition, provides operators with centralized visibility and supervisory control of industrial processes.

A typical architecture looks like

Field Devices → PLCs/RTUs → SCADA → HMI/Historian

SCADA commonly provides:

• HMI visualization

• Alarm management

• Historical trending

• Equipment status

• Supervisory commands

• Reporting and event logging

PLCs and RTUs generally execute the underlying control logic, including sequences, interlocks, permissives, and PID loops. SCADA provides the supervisory layer operators use to interact with that process.

This distinction is important because properly designed local control should not necessarily depend on continuous connectivity to higher-level systems.

What Is Industrial IoT?

Industrial IoT extends connectivity and data access beyond the traditional control system.

IIoT platforms can collect information from PLCs, RTUs, SCADA systems, historians, meters, sensors, drives, gateways, and other industrial devices.

That information can then support:

Remote monitoring

Multi-site visibility

Centralized historization

Alarm notifications

Analytics

Cross-system data aggregation

Enterprise dashboards

Cloud, edge, on-premise, or hybrid applications

This is particularly useful for organizations operating geographically distributed infrastructure.

SCADA	Industrial IoT
Supervisory monitoring and control	Connectivity and data aggregation
Usually plant or process focused	Often multi-site or enterprise focused
Primarily operator focused	Supports broader authorized users
HMI, alarms and control	Remote visibility and analytics
PLC/RTU integration	Cross-system integration
Operational historization	Centralized and cross-site data

The boundaries are increasingly blurred. Modern SCADA platforms include web, cloud, and analytics capabilities, while IIoT platforms increasingly offer functions historically associated with SCADA.

What problem does the architecture need to solve?

Does IIoT Replace SCADA?

Not necessarily.

Consider an existing facility with PLC-based control, established SCADA, alarm management, and a historian.

The control architecture may work perfectly well, while the organization still struggles with

• Monitoring multiple facilities

• Remote visibility

• Cross-site historical analysis

• Access to data outside the control room

• Connecting previously isolated assets

Replacing SCADA may add unnecessary cost and complexity.

Instead, an IIoT layer can potentially extend selected operational data while the existing control system continues performing its established function.

How SCADA and IIoT Work Together

Sensors & Equipment

↓

PLCs / RTUs

↓

SCADA / HMI / Historian

↓

IIoT Platform

↓

Remote Monitoring / Analytics / Applications

Each layer has a different responsibility.

PLCs and RTUs execute local control.

SCADA provides supervisory monitoring and operator interaction.

IIoT extends selected operational information across systems, locations, and applications.

Maintaining these boundaries can improve resilience and prevent higher-level connectivity requirements from unnecessarily affecting critical control functions.

Protocols and Data Integration

Industrial environments rarely contain equipment from a single manufacturer or generation.

Common protocols include

• Modbus TCP/RTU

• DNP3

• OPC UA

• EtherNet/IP

• BACnet

• SNMP

• IEC 61850 where applicable

• MQTT

  
  

Protocol compatibility is only part of the integration problem.

Engineers must also consider data types, timestamps, quality, polling rates, bandwidth, tag structures, alarm behavior, and communications failures.

The goal isn't simply moving a value from one system to another. The data must retain enough context to remain operationally meaningful.

What Happens When Communications Fail?

This becomes especially important with remote assets.

Industrial systems should define

• What continues operating locally

• What data is buffered

• How timestamps are maintained

• How communication failures are detected

• What happens to alarms

• How historical data is synchronized after connectivity returns

A remote monitoring connection may disappear.

The physical process often cannot.

Cybersecurity Considerations

Extending OT data to additional systems also introduces additional interfaces.

Architecture should consider

• Network segmentation

• Firewalls

• VPNs

• Encryption and certificates

• Role-based access

• Least-privilege principles

• Authentication

• Logging and auditing

• Controlled remote access

  
  

Instead of asking

“How do we get PLC data into the cloud?”

A better engineering question is

“Which operational data needs to cross the OT boundary, who needs access to it, and how can we provide that access securely?”

For example let's use Water and Wastewater

Consider a utility operating a treatment facility along with remote lift stations, tanks, pumps, PLCs, and RTUs.

Local controllers continue operating the process. SCADA continues providing supervisory control.

An IIoT platform can provide an additional layer for centralized monitoring of information such as

• Pump status

• Tank levels

• Flow and pressure

• Communications status

• Alarms

• Historical trends

The objective is broader visibility without unnecessarily changing the underlying control strategy.

Another example is Solar and BESS

A utility-scale renewable project may contain inverters, trackers, meters, weather stations, protection equipment, plant controllers, BMS/EMS systems, PLCs, and SCADA.

SCADA provides site-level operational visibility.

An IIoT layer can aggregate selected information across multiple sites, creating portfolio-level visibility while appropriate control functions remain at the plant level.

This separates plant control from portfolio-level operational intelligence.

Where aviCore Fits

aviCore is designed to operate alongside industrial control infrastructure and provide an additional layer of operational visibility.

Depending on the application architecture, aviCore can support

• Real-time monitoring

• Historical trending

• Alarm visibility and notifications

• Multi-site dashboards

• Remote asset monitoring

• Data historization

• Industrial protocol integration

• Role-based access

• Store-and-forward capabilities

For brownfield systems, this can provide a path toward broader IIoT capabilities without automatically replacing existing PLC or SCADA infrastructure.

When Does IIoT Make Sense?

Engineers should consider an additional IIoT layer when there is a defined operational requirement, such as

Distributed assets

Multiple remote sites need centralized visibility.

Different control platforms

Data needs to be consolidated across equipment and manufacturers.

Remote monitoring

Authorized personnel need operational information outside the control room.

Historical analysis

Data needs to be compared across assets or facilities.

Growth

Existing architecture becomes difficult to scale as additional sites are added.

Before implementation, determine what data is required, which system retains control authority, what happens during communications loss, who needs access, and how OT network boundaries will be protected.

In Conclusion

SCADA and IIoT are not inherently competing technologies.

PLCs and RTUs control the process.

SCADA supervises the process.

IIoT extends the accessibility and usefulness of operational data.

For many industrial environments, the strongest architecture combines these capabilities while maintaining clear boundaries between local control and higher-level connectivity.

The objective isn't to connect everything.

It's to make the right operational data available to the right systems and people without compromising the reliability of the underlying process.