Utility-Scale Solar Monitoring vs SCADA: What Each Should Do

By Alex Montekristobelgrade, REIG Solar Technical Team

At a 200 MW solar plant, utility-scale solar monitoring and SCADA both collect data from hundreds of inverters, sensors, and meters. Both feed dashboards and both generate reports. The boundary between them looks blurry — until something goes wrong. A grid operator issues a curtailment order and the operator discovers their monitoring system cannot execute it. Or an independent engineer audits the performance ratio and finds two conflicting numbers: one from the monitoring platform, one from the SCADA historian. These are not edge cases, however. They are the direct consequence of treating utility-scale solar monitoring and SCADA as interchangeable when they serve fundamentally different purposes.

What Utility-Scale Solar Monitoring Actually Does

At the plant level, utility-scale solar monitoring collects irradiance, inverter output, module temperature, wind speed, energy metering, and availability data from distributed sensors across a plant and logs it to a historian for analysis and reporting. It gives project managers, asset owners, and O&M teams the data they need to calculate performance ratios, detect underperforming strings, and document energy delivery against PPA obligations. Yet utility-scale solar monitoring does not send a single command to any piece of field equipment. That is the functional boundary, and it is absolute.

In other words, think of the monitoring system as the plant’s memory and analytical engine. Specifically, it records what happens, calculates what it means, and presents it to people who make decisions. That said, the system is passive with respect to equipment: sensors write to it, but it never writes back to sensors or controllers.

From Sensor to Historian: The Monitoring Data Path

To trace the data path: the monitoring data path begins at the sensor. A pyranometer measures plane-of-array irradiance. An RTD measures module temperature. An inverter reports AC output, efficiency, and fault codes. Each value travels to the data acquisition system (DAS), where it is timestamped, scaled, and stored in a historian database. From there, the analytics platform calculates performance ratio (PR), specific yield, and availability, displaying results on dashboards segmented by operations vs asset management views.

In fact, the historian is the core asset of a monitoring system. It holds every data point from commissioning onward, structured for time-series queries. When an independent engineer audits a plant’s performance claim or an offtaker disputes an energy delivery figure, the historian is therefore the authoritative source. Completeness and accuracy of that historian (not real-time control responsiveness) is the primary quality measure for utility-scale solar monitoring.

IEC 61724-1:2021: Class A Standards for Utility-Scale Solar Monitoring

Notably, IEC 61724-1:2021 governs monitoring system accuracy for PV plants. The standard defines two accuracy classes: Class A for utility-scale and large commercial installations, and Class B for smaller sites where estimated or nearby-station data is acceptable. Class A requirements include annual pyranometer recalibration, weekly cleaning schedules, heating and ventilation for dew and frost mitigation, and specific accuracy thresholds for irradiance, temperature, and wind sensors. The 2021 revision also added requirements for albedo measurement on bifacial module installations, a significant upgrade from the 2008 edition.

In short, IEC 61724-1 defines what the monitoring system must measure and how accurately. It says nothing about control. That scope belongs to the next system entirely. For more on Class A sensor requirements and pyranometer selection, see Solar DAS Commissioning: Irradiance and Weather QA.

What SCADA Does That Utility-Scale Solar Monitoring Cannot

US solar facilities lost an average of $5,720 per megawatt to equipment issues in 2024 — with power loss rates climbing from 1.84% in 2020 to 5.77% by the time of the most recent analysis (Raptor Maps, PV Magazine March 2025). SCADA is the system that can act on those losses in real time. Monitoring tells you what is wrong. SCADA issues the command that fixes it — or isolates it before it becomes worse.

By definition, SCADA stands for Supervisory Control and Data Acquisition. The control half of that definition is what separates it from a monitoring system. A SCADA system sends commands to field equipment. That is, it writes inverter set points. It executes curtailment orders from the grid operator. It manages reactive power output to support voltage stability at the point of interconnection. When a protection relay operates, SCADA confirms the event, sequences the response, and logs the state change with millisecond precision. None of that is possible in a read-only monitoring architecture.

RTUs, PLCs, and Real-Time Control Logic

In the field, SCADA control works through Remote Terminal Units (RTUs) distributed across the plant. Each RTU polls field devices (inverters, trackers, meters, protection relays) at intervals as short as one second. When the SCADA controller sends a command, the RTU translates it into the device protocol (Modbus TCP, DNP3, IEC 61850) and writes the new set point directly to the equipment. The total round-trip, from operator command to equipment response, happens in seconds. By contrast, a monitoring system on the same network can observe this transaction but cannot initiate it.

Also, for a detailed look at how SCADA architecture is structured at a plant level, see Solar SCADA Architecture and Control Signals for Utility-Scale PV.

Grid Compliance Functions SCADA Must Handle

For transmission-connected plants, grid interconnection agreements specify control functions that monitoring systems cannot perform. IEEE 1547-2018, the standard governing distributed energy resource interconnection, requires voltage regulation, frequency response, reactive power support, and fault ride-through capability. Each of these requires real-time, bidirectional communication with inverters; a read-only connection cannot meet this requirement. Indeed, a monitoring system that observes voltage at the point of interconnection and generates an alert is compliant with nothing. The SCADA system that responds to that voltage event by adjusting reactive power output across multiple inverters within seconds is what IEEE 1547-2018 actually demands.

The Data Flow Divide: From Sensor to Historian vs Sensor to Controller

In fact, two distinct data paths run from the same field sensor at a utility-scale solar plant. One path feeds the monitoring historian at one-minute intervals per IEC 61724-1:2021. The other feeds the SCADA controller at one-second intervals for real-time control decisions. Both paths may share the same physical wire. Their data governance must stay separate.

The sampling rates differ, specifically. A Class A utility-scale solar monitoring system typically logs irradiance and energy data at one-minute intervals, as required under IEC 61724-1:2021. A SCADA control loop polls device state every one to ten seconds to support real-time response. Historian archives for long-term storage often aggregate to fifteen-minute intervals. These are not interchangeable. Averaged fifteen-minute historian data cannot support a millisecond protection decision. Real-time SCADA polling data is not calibrated to the accuracy standard required for performance ratio calculation under IEC 61724-1.

Why the Two Data Paths Must Stay Separate

Consequently, a well-architected plant maintains both paths. The monitoring historian owns the performance record: the single source of truth for energy delivery, PR, and availability KPIs. The SCADA historian owns the operational record: the log of control actions, fault events, and device state changes. Each serves its audience: performance metrics for asset management, operational records for O&M and grid compliance reporting.

Where the Two Systems Overlap and Why That Creates Problems

However, modern OEM inverter portals blur the monitoring-SCADA line intentionally. A vendor portal that displays real-time inverter power, allows a technician to reset a fault remotely, and schedules a power setpoint change is performing both monitoring and SCADA functions in a single interface. That is technically acceptable when one unified system governs both. The problem arises when EPC teams assume their monitoring platform performs control functions it was never engineered to execute, or treat monitoring and SCADA as parallel deployments that can operate independently without a unified data governance layer.

The result is a critical data integrity failure called the “two-number problem.” Asset managers query the monitoring platform for the month’s IEC 61724-1-compliant performance ratio. The SCADA historian (queried independently by a grid compliance engineer) returns a different PR value for the same period. Both numbers are calculated from irradiance data, although from different irradiance sources with different calibration histories. Neither team can easily explain the discrepancy. The offtaker gets two competing figures. The independent engineer flags a data quality issue. What started as a procurement decision: letting the inverter OEM handle monitoring becomes a contractual dispute six months after COD.

In short, vendor portals are a useful supplement to a proper monitoring architecture. They are not a substitute for it. For project managers and commissioning leads, the procurement decision should always be: one unified monitoring historian, one SCADA system with defined control scope, and explicit documentation of which system owns each data point.

Failure Modes: What Breaks When Monitoring and SCADA Roles Are Confused

To illustrate the cost: across US solar facilities, power loss rates climbed from 1.84% in 2020 to 5.77% in 2024 (Raptor Maps, 2025) — and unclear monitoring-SCADA scope contributes to this trend in three repeating patterns. For example, performance ratio disputes arise from mismatched irradiance sources. Meanwhile, curtailment compliance fails when monitoring cannot execute grid operator commands. Finally, cybersecurity gaps open when monitoring portals expose SCADA networks. All three are preventable at design stage.

Performance Ratio Disputes in Utility-Scale Solar Monitoring

Yet the most common failure is also the quietest. IEC 61724-1:2021 Class A specifies that irradiance data used for performance ratio calculation must come from an on-site pyranometer with documented calibration. When the monitoring system uses one pyranometer and the SCADA historian pulls from a secondary sensor with a different calibration date, the two systems produce systematically different PR values. The divergence is small on any given day (often 0.3% to 0.8%), yet it compounds over a 20-year PPA period into a material financial disagreement. Therefore, the fix requires a single, authoritative irradiance source, acknowledged by both systems, with a shared calibration record. In projects we have commissioned, resolving this single conflict eliminated the PR dispute entirely, and typically shaved six to eight weeks off post-COD performance reconciliation.

Grid Compliance Failures and Cybersecurity Gaps

Grid compliance failure, however, happens at interconnection testing when a utility witness requests a curtailment demonstration and the monitoring system cannot respond. This is not hypothetical. Plants that relied on inverter-level vendor portals for curtailment rather than a unified SCADA with RTU control have failed utility witness tests, delayed COD, and triggered liquidated damages under EPC contracts. IEEE 1547-2018 does not accept a monitoring dashboard as evidence of curtailment capability. It requires a demonstrated, documented control response.

Cybersecurity gaps emerge because monitoring systems are typically designed for accessibility: cloud dashboards, web APIs, mobile access — while SCADA networks must be segmented, hardened, and subject to NERC CIP access controls at bulk electric system plants. When both systems share a network segment or use the same VPN credentials, a monitoring portal breach becomes a potential pathway to SCADA. Therefore, network segmentation between the monitoring platform and SCADA OT zone is not optional. It is a design requirement from day one of commissioning.

Measurement, Meaning, Control: Where Each System Belongs

Altogether, the Measurement, Meaning, Control framework maps directly onto the monitoring-SCADA boundary. Measurement sits across both systems: utility-scale solar monitoring measures energy production, irradiance, and environmental conditions for completeness and accuracy; SCADA measures equipment state for control accuracy and protection coordination. Meaning belongs primarily to monitoring: the historian, analytics platform, and dashboard convert raw readings into performance ratios, degradation trends, and O&M priorities. Control belongs exclusively to SCADA; every command that reaches field equipment flows through the SCADA layer, never through the monitoring platform.

As a result, this framework matters because it prevents scope creep in both directions. A monitoring engineer who extends read access to write functions is out of scope. A SCADA engineer who bypasses the monitoring historian to create an unofficial performance record is creating the two-number problem. When applied rigorously, Measurement, Meaning, Control keeps each system in its lane and keeps the data record coherent enough to be auditable, defensible, and financeable.

Standards That Govern Utility-Scale Solar Monitoring and SCADA

To be clear, three standards define the technical requirements for utility-scale solar monitoring and SCADA at utility-scale plants, and they do not overlap. IEC 61724-1:2021 governs monitoring system accuracy: Class A requirements include annual pyranometer recalibration, weekly cleaning, and documented calibration chains. IEEE 1547-2018 governs grid interconnection for distributed energy resources, requiring the real-time control functions that only SCADA can execute. NERC CIP standards apply cybersecurity requirements specifically to SCADA networks at bulk electric system facilities, not to monitoring platforms unless those platforms share a network segment with SCADA.

In practice, understanding which standard applies to which system prevents two common commissioning errors. First, applying monitoring-grade data (fifteen-minute averages) to SCADA protection functions that require one-second resolution. Second, treating the monitoring system as NERC CIP-exempt when it shares network infrastructure with a CIP-applicable SCADA. Notably, both types of error have been cited in NERC compliance notices.

For a complete breakdown of how tagging and scaling errors corrupt monitoring data, see Solar DAS Tagging: Units, Scaling, and QC. For SCADA reference architecture, see Solar Plant SCADA System: Reference Architecture Diagram.

How REIG Integrates Utility-Scale Solar Monitoring and SCADA from Day One

To solve this, REIG Solar commissions utility-scale solar monitoring and SCADA as integrated systems from day one, not as sequential deployments from separate vendors. The field-proven RenergyWare platform ships as a NEMA 4 / UL-listed enclosure with DAS historian and SCADA control layers pre-configured before the commissioning engineer arrives on site, eliminating the two-number problem at its source.

As a result, the data flow divide, the role boundaries, and the cybersecurity segmentation between monitoring and SCADA are engineered into the hardware, not bolted on during SAT. In our commissioning experience, plants that separate monitoring and SCADA procurement from separate vendors spend an average of four to six additional weeks in commissioning resolving data governance conflicts; none of these arise in a pre-integrated deployment.

Specifically, REIG’s commissioning-ready approach delivers: one shared irradiance source acknowledged by both monitoring and SCADA, eliminating the two-number problem; a unified data governance model where monitoring historian and SCADA operational historian are segregated but cross-referenceable; and a network topology where the monitoring cloud path and the SCADA OT zone are on separate VLANs with documented firewall rules before COD.

Ultimately, for project managers defining scope for an upcoming utility-scale plant, the question is not “monitoring or SCADA?” but rather: “who owns the integration between them?” If that question does not have a single answer at the time of EPC contract execution, the two-number problem and its financial consequences are already in the schedule. Contact REIG Solar to define the scope before it becomes a commissioning problem.

The field-proven RenergyWare platform integrates both utility-scale solar monitoring and SCADA in a commissioning-ready enclosure. Contact REIG Solar to define the monitoring-SCADA boundary for your next project before it becomes a commissioning problem.

• Further reading: Solar SCADA ROI: How Controls and Data Increase Revenue
• Further reading: SCADA Integration Services: Scope, Deliverables, and How to Prevent Rework
• Further reading: Solar DAS Commissioning Targets: Completeness, Accuracy, and Latency
• Further reading: Pyranometer for Utility-Scale PV: Accuracy Classes Explained

References

1. Raptor Maps / PV Magazine (March 2025). “US Solar Facilities Lost $5,720 Per MW to Equipment Issues in 2024.” pv-magazine.com
2. IEC (2021). IEC 61724-1:2021, Photovoltaic System Performance Monitoring, Part 1: Monitoring. International Electrotechnical Commission. Technical and economic KPIs discussion in IEA-PVPS T13-28 (2024).
3. IEEE (2018). IEEE 1547-2018, Standard for Interconnection and Interoperability of Distributed Energy Resources. standards.ieee.org
4. NERC. NERC CIP Reliability Standards: Cybersecurity for the Bulk Electric System. nerc.com
5. IEA-PVPS Task 13 (2024). Technical and Economic KPIs for PV O&M (T13-28). iea-pvps.org