Solar monitoring offline:
Data problem or equipment failure?

When a commercial solar portal shows “offline,” zero production, or stale data, there are at least two broad possibilities: the plant stopped producing, or the monitoring chain stopped delivering trustworthy data. Both require attention. They do not require the same technician, urgency, parts, or corrective action.

Follow the full monitoring chain

A dashboard sits at the end of several connected systems. Production equipment and meters create measurements. A data logger, gateway, plant controller, or SCADA device collects them. Local Ethernet, fiber, radio, Wi-Fi, or serial links move the records. A router or modem provides backhaul. A server or cloud platform stores and displays the data. User accounts and application programming interfaces provide access.

A failure anywhere along that path can make the portal appear offline:

• Production layer: inverter trip, AC or DC outage, protective operation, control-state change, or loss of station service.
• Measurement layer: meter or sensor fault, lost power, configuration change, clock error, or failed communications port.
• Collection layer: frozen or failed logger, full storage, software problem, or local device-network interruption.
• Backhaul layer: cellular carrier outage, weak signal, damaged fiber, failed antenna, router, switch, firewall, or subscription.
• Platform layer: cloud service interruption, expired integration, account change, API failure, or dashboard display problem.

DOE FEMP's monitoring-platform guidance describes this mix of instrumentation, data acquisition, processing, reporting, alarms, work tickets, and document management. The monitoring system is an O&M tool with its own power, communications, security, and continuity requirements.

Clues that separate missing data from lost production

NREL's paper Overcoming Communications Outages in Inverter Downtime Analysis explains why the distinction is difficult: communications can disappear when an inverter trips, communications faults can occur independently, and some acquisition systems fill missing values with zero. It demonstrates methods that compare inverter data with plant-meter or cumulative-energy evidence rather than classifying every gap as downtime.

What the owner can safely verify first

Begin with records and approved user interfaces. The goal is to narrow the event without changing equipment state or erasing fault history.

1. Capture the portal state. Save screenshots, error text, affected devices, the last valid timestamp, time zone, and any data-quality flags.
2. Check the scope. Determine whether the issue affects one device, one subsystem, the whole site, or multiple sites using the same platform.
3. Review known events. Note utility outages, storms, maintenance, network changes, subscription changes, password changes, and vendor notices.
4. Compare safely available sources. Review revenue-meter, utility, facility, building-management, and inverter-platform information that the owner is already authorized to access.
5. Open an incident record. Preserve who observed the problem, when it was escalated, the business impact, and every action taken.
6. Escalate by evidence. Send network/account problems to the responsible IT or platform contact and potential production faults to the qualified solar O&M provider—often in parallel.

Do not let a green portal status end the review if energy data, alarms, or owner bills still indicate a loss. Likewise, avoid dispatching broad electrical troubleshooting solely because a cloud tile turned gray.

How a qualified service provider diagnoses the event

A structured response starts with the system architecture and approved remote checks, then moves on site only when the evidence or response plan requires it. TerraSun's solar monitoring and emergency response work ties the alarm to ownership, triage, field verification, repair, and documented closeout.

• Confirm the monitoring boundary, normal data cadence, device hierarchy, network ownership, and expected alarm route.
• Determine whether the production meter, inverters, gateway, and platform stopped reporting at the same or different times.
• Check data age, clock synchronization, local buffering, cumulative registers, raw exports, and platform data-quality flags.
• Review equipment status, alarm and event history, operating commands, utility conditions, and recent work.
• Test the relevant communications link under the approved network and cybersecurity process.
• Repair the confirmed fault, restore approved configuration, backfill retained data where possible, and verify live reporting and alarm delivery.

If the evidence points to a real inverter or electrical event, the incident moves into central inverter service or corrective maintenance. If production remained intact, the closeout should still quantify the visibility gap and correct the weak link that allowed it.

Protect performance records during recovery

Missing data can distort availability, performance ratio, warranty evidence, invoices, and lost-energy calculations. Never silently convert a gap to zero or replace it with an estimate. Preserve raw data, the original missing interval, the source used for any backfill, the method, and a quality flag that distinguishes measured from reconstructed values.

IEC 61724-1 establishes terminology, monitoring-system classes, equipment, and methods for PV performance monitoring. NREL's O&M best-practices guide likewise treats data acquisition, alarms, warranties, work history, and performance guarantees as connected parts of the O&M program. For an owner, that means monitoring repair is not complete until reporting continuity and the historical record are both addressed.

Build a more resilient monitoring program

DOE FEMP recommends operational continuity, backup and restore capability, third-party data access where needed, cybersecurity, and reliable monitoring-system power. Its remote-metering guidance also outlines cellular, satellite, radio, power-line, and fiber options and stresses coordination with the responsible cybersecurity and communications teams.

An owner-ready monitoring specification should define:

• Which meter is authoritative for energy and which systems are diagnostic.
• Expected interval, latency, retention, local buffering, and backup requirements.
• Heartbeat or stale-data alarms for every critical data path—not only equipment alarms.
• Who owns the meter, logger, network, SIM plan, platform account, credentials, and renewals.
• Notification recipients, severity rules, acknowledgement time, escalation path, and field response target.
• Secure remote-access rules, change control, supported firmware, and configuration backups.
• A tested recovery and backfill procedure, plus periodic alarm-routing verification.

The IEA PVPS climate-specific O&M guideline notes both the value of fault-detection tools and continuing limitations caused by device communication and standardization. Keep a qualified human review in the response loop, especially when an automated label will trigger a dispatch, availability penalty, or warranty action.

Electrical and cybersecurity boundary

Owners can document portal behavior and use access already assigned to them. They should not open inverter, switchgear, meter, gateway, or communications enclosures; move disconnects; bypass protective functions; alter controls; or perform electrical measurements unless the task is assigned to personnel qualified for that equipment and hazard under approved procedures.

Owner takeaway

An offline monitoring portal creates two questions: “Can we still see the plant?” and “Is the plant still producing?” Answer them separately. Capture the event, define its scope, compare independent production evidence, preserve raw data, and escalate communications and equipment paths according to the evidence. Close the incident only after live data, alarm routing, historical records, and actual plant status are verified.

Official technical references

• U.S. DOE FEMP: Monitoring Platforms for Solar Photovoltaic Systems
• U.S. DOE FEMP: Metering for Federal Solar PV Systems in Remote Locations
• NREL: Overcoming Communications Outages in Inverter Downtime Analysis
• NREL: Best Practices for Operation and Maintenance of Photovoltaic and Energy Storage Systems
• IEA PVPS Task 13: Guidelines for Operation and Maintenance of Photovoltaic Power Plants in Different Climates
• IEA PVPS Task 13: The Use of Advanced Algorithms in PV Failure Monitoring
• IEC 61724-1:2021: Photovoltaic system performance—Monitoring