Oxaide
Data quality checklist

BESS telemetry quality checklist for teams that know weak data becomes weak evidence

Use this checklist before diligence, warranty, insurer, lender, or O&M review. It helps you test whether the telemetry can actually support a battery conclusion, or whether missing windows, summary layers, and timestamp issues are quietly distorting the story.

The checklist

1Confirm what raw and near-raw telemetry actually exists at module, rack, cluster, and site level
2Check timestamp integrity, timezone consistency, and daylight-saving handling across exports
3Identify missing windows, dropped packets, and unexplained flatlines before analysing trends
4Compare BMS, SCADA, and historian coverage to see which layer is masking signal loss
5Verify whether temperature, current, and voltage resolution are sufficient for the intended diagnosis
6Check whether sampling intervals changed during the operating history and how that affects trend interpretation
7Document which signals are original measurements and which are derived summary metrics
8Make the evidence boundary explicit: what the dataset can support confidently and what it cannot
How Oxaide Reads BESS TelemetryBESS Monitoring Software AlternativeRapid BESS Health Assessment
Operating posture

Scope first

Defined review scope

Boundary, telemetry window, and mandate question are pinned down before conclusions move.

Encrypted handling

Protected review workflow

Review traffic and operating data are handled with encrypted transfer and controlled access.

Customer boundary

Customer-controlled deployment

Managed, private, and isolated deployment paths are available when the environment requires them.

Direct accountability

Principal sign-off

Technical accountability stays close to the method rather than disappearing into a generic workflow.