SCADA Systems for Utility-Scale Solar Plant Monitoring

A utility-scale solar plant operates unattended for 8,000+ hours per year across a 25-year project life. SCADA (Supervisory Control and Data Acquisition) is the nervous system that transforms hundreds of individually operating inverters, trackers, and meteorological sensors into a managed, monitorable asset. Without properly designed SCADA, fault response times increase from minutes to days, grid operator compliance requirements go unmet, and O&M costs rise sharply.

This guide covers SCADA architecture, communication protocols, grid operator interface requirements, cybersecurity standards, and how manufacturer-provided plant management systems (Sungrow iSolarCloud, Huawei FusionSolar) compare to third-party SCADA platforms.

SCADA Architecture for a Solar Plant

A typical utility-scale solar SCADA system has three layers:

Field Level (Level 0): Sensors and Controllers

The field level includes all physical devices that generate data or receive control commands: inverters, string monitoring devices, weather stations (pyranometer, ambient temperature, wind speed, humidity), tracker controllers, revenue-grade energy meters, MV switchgear with protection relays, and transformer monitoring (oil temperature, winding temperature, tap position).

Station Level (Level 1): Plant Controller / SCADA Server

The plant controller aggregates data from all field devices and executes plant-level control functions: active power curtailment, reactive power regulation (Q(U) / Q(P) curves), frequency response, fault ride-through co-ordination, and E-stop. It communicates upward to the grid operator's control centre and downward to individual inverters. Hardware is typically an industrial PC or ruggedised server (Beckhoff, Siemens PCS 7, ABB Symphony Plus, or a dedicated solar plant controller from Sungrow or Huawei).

Supervisory Level (Level 2): Cloud / Remote Monitoring

Cloud-based portals (Sungrow iSolarCloud, Huawei FusionSolar, SMA Sunny Portal, or third-party platforms such as AlsoEnergy, Parasol, or Greensmith) provide the O&M team with dashboards, alarm management, performance analytics, and reporting. Revenue-grade production data is exported to the offtaker's billing system and to the independent engineer for performance assessment.

Communication Protocols

Protocol	Layer	Used For	Typical Standard
Modbus TCP/RTU	Field → Station	Inverter status, active/reactive power, alarms, MPPT data	Sungrow, Huawei Modbus maps (manufacturer-specific)
IEC 61850 MMS/GOOSE	Field → Station	Protection relay data, switchgear status, transformer data	IEC 61850-7-420 (DER extensions)
IEC 60870-5-104	Station → Grid operator	Telecontrol: active power setpoint, status, alarms	Most TSOs in Europe, Middle East, Asia
DNP3	Station → Grid operator	Telecontrol (North America, Australia)	IEEE 1815, NERC CIP compliant
MQTT / REST API	Station → Cloud	Cloud monitoring data upload, alarm push	Sungrow iSolarCloud API, Huawei FusionSolar API
OPC UA	Any	Plant historian, third-party integration	IEC 62541, preferred for SCADA interoperability

Sungrow and Huawei inverters communicate natively via Modbus TCP to the plant controller. Both manufacturers also publish IEC 61850 models for their inverters (available in their SCADA integration packages) allowing direct IEC 61850 communication for projects where the TSO requires this protocol throughout the plant.

Grid Operator Interface Requirements

Grid operators and system operators (TSOs, DSOs) require bidirectional communication with utility-scale solar plants for:

Active power curtailment: Setpoint received from the grid operator's control centre (typically via IEC 60870-5-104 or DNP3) and executed within 10 seconds (or faster for Category B DERs under IEEE 1547-2018). The plant controller distributes the curtailment setpoint proportionally across all online inverters.
Reactive power regulation: Q setpoint or power factor setpoint received from the grid operator and implemented across the inverter fleet. Some grid operators require local Q(U) droop control at the MV bus — confirm the exact requirement with the utility's interconnection engineer.
Revenue metering: Bidirectional revenue-grade meters (IEC 62053-22 Class 0.5S or better) at the point of common coupling (PCC) with pulse output or Modbus TCP to the plant SCADA. Required for PPA settlement and grid operator billing.
Protection relay coordination: Under-over voltage/frequency relays at the PCC programmed to match the grid operator's protection coordination study. Relay settings files (COMTRADE, CID) must be submitted to the grid operator for approval before energisation.

Sungrow iSolarCloud vs Huawei FusionSolar: Plant Monitoring Comparison

Feature	Sungrow iSolarCloud	Huawei FusionSolar
Plant dashboard	Web + iOS/Android app	Web + iOS/Android app
Data logging interval	5 min (standard), 1 min (premium)	5 min (standard), 1 min (SmartLogger 3000A)
String-level monitoring	Yes (via Smart Logger / combiner box)	Yes (via SmartLogger + Smart Combiner)
Alarm management	Push notification; email; SMS (configurable)	Push notification; email; SMS
Grid code compliance functions	Q(U), P(f), curtailment via Modbus	Q(U), P(f), curtailment via Modbus/IEC 61850
Third-party inverter integration	Limited (Modbus adapter available)	Limited (SmartLogger 3000A supports 3rd-party via RS485)
API / data export	REST API, Excel/CSV export	REST API (FusionSolar OpenAPI), CSV export
Local plant controller	Sungrow Smart Energy Controller SEC-1000	Huawei SmartLogger 3000A + SmartPCS controller
Cybersecurity certification	ISO 27001 (cloud); local network firewall	IEC 62443 (in progress); ISO 27001 cloud

For projects with mixed-brand inverter fleets or where the owner requires a vendor-neutral monitoring platform, third-party SCADA systems (AlsoEnergy PowerTrack, Siemens SICAM SCC, Eaton Power Xpert) are preferred. They integrate with multiple inverter brands via Modbus and offer standardised reporting formats for O&M contractors and asset managers.

Cybersecurity Requirements for Solar SCADA

Utility-scale solar plants are increasingly treated as critical infrastructure, with NERC CIP (North America) and IEC 62443 (international) setting cybersecurity requirements. Key requirements include:

Network segmentation: Corporate IT network strictly separated from OT (operational technology) SCADA network via industrial firewall or demilitarised zone (DMZ). The grid operator communication link (IEC 60870-5-104 or DNP3) must be on an isolated OT network segment.
Encrypted communications: TLS 1.2+ for all cloud communications. VPN tunnel (IKEv2 or WireGuard) for remote access by O&M personnel. Plain Modbus TCP on a flat OT network is acceptable only when the OT network has no internet exposure.
Access control: Role-based access control (RBAC) with multi-factor authentication for remote access. All access attempts logged. Default manufacturer passwords changed before commissioning.
Patch management: SCADA server OS and application software patched per vendor schedule. Industrial systems require change management processes before patch application to avoid unplanned restarts.

SCADA Specification for EPC Contracts

EPC contracts for utility-scale projects should specify the SCADA system requirements in the technical schedule (Employer's Requirements). Key items to specify include: data points list (minimum 50–100 points per inverter), data retention period (minimum 10 years), alarm response time (<5 minutes for critical alarms), availability (99.5%+ for local historian), and grid operator interface protocol. Econo Solar's technical team can assist in preparing SCADA technical requirements aligned with the proposed inverter equipment.

To get a package quote including inverters, plant controller, and SCADA integration specifications, submit your project details here.

What is the difference between SCADA and a plant management system (PMS)?

The terms are often used interchangeably but have a technical distinction. SCADA (Supervisory Control and Data Acquisition) is the broader category covering data acquisition, supervisory control, and HMI. A Plant Management System (PMS) or Energy Management System (EMS) is the control logic layer within SCADA that executes plant-level optimisation decisions: active power setpoint dispatch, reactive power regulation, BESS charge/discharge scheduling, and grid service provision. For solar-only plants, the PMS functions are relatively simple; for solar+BESS hybrid plants, the EMS becomes significantly more complex and is a specialised product (Sungrow PowerTitan EMS, Huawei FusionSolar Smart Energy Controller).

How many Modbus data points does a typical solar inverter expose?

Modern string inverters from Sungrow and Huawei expose 200–400 Modbus register addresses covering real-time data (AC power, DC voltage, DC current per MPPT, frequency, power factor, reactive power), status (operating mode, fault codes, grid connection status), configuration (active power limit, reactive power setpoint), and historical counters (daily/total energy). The plant controller typically polls 50–80 key registers per inverter at 5-second intervals for real-time monitoring, and collects full register maps at longer intervals for detailed diagnostics.

Can I use a cloud-only monitoring system without a local plant controller?

For projects below 1 MW where the grid operator does not require telecontrol, cloud-only monitoring via the inverter's built-in Wi-Fi or LAN connection to iSolarCloud or FusionSolar is acceptable. For utility-scale projects (>1 MW), a local plant controller is required because: (1) grid operator control commands must be executed in <10 seconds regardless of internet connectivity; (2) protection functions must not depend on cloud availability; (3) local historian data must be retained even during internet outages. A local plant controller with local historian, supplemented by cloud monitoring for remote access, is the standard architecture for projects above 1 MW.