Skip to content
Anonymized operational patternPortfolio operators · 5 min read

Local event or shared cause?

A site fault or a wider data outage?

An anonymized pattern showing how comparison across sites can help choose the right investigation path.

“

One silent site can mean something very different from several data sources going silent at the same time.

01

Starting situation

An operator follows production across geographically separate sites with different manufacturer access and local connections.

02

The problem

Data stops at one site. A local fault, central provider outage and authorization problem require different responses.

03

What became visible

The state of other connected systems provides context for whether the pattern affects one source or several.

04

SM Sentinel's role

SM Sentinel shows known connection and event states on a common timeline without automatically labelling missing data as an inverter fault.

05

Human next step

The operator checks access, the manufacturer service, local networking and only then the equipment if necessary.

06

Expected operational outcome

More targeted troubleshooting and fewer unnecessary site visits may be possible, depending on available data and internal processes.

07

What is this story based on?

Recurring cases where source status and cross-site comparison are a better first step than a quick fault label.

08

Service boundary

This comparison supports decisions; it does not replace manufacturer diagnostics, electrical safety checks or on-site service.

NEXT STEP

Find out what we can see from your system.

After connection, you can make a clearer choice about which SM Sentinel plan fits your operation.