Telemetry lake & SCADA historian
We consolidated 30 years of fragmented SCADA historians into a single telemetry lake for a water utility: 10 years of flows, pressures and levels online, with drift flagged before field crews notice.
The situation.
A water utility with 30 years of fragmented SCADA historians across depots.
ScopeA single telemetry lake for flows, pressures and levels: protocol adapters to site RTUs, gap detection and backfill, calibration-drift alerts, and 10-year replay for model calibration and regulator queries.
10-year telemetry online; drift flagged before field crews notice.
What made it hard.
Historic data changed units at source upgrades without notification: we detected step changes statistically and mapped unit lineage per series.
RTU clock drift corrupted event ordering: we enforced ingestion-time sequencing with source-clock preservation.
Common questions.
What was the scope?
A single telemetry lake for flows, pressures and levels: protocol adapters to site RTUs, gap detection and backfill, calibration-drift alerts, and 10-year replay for model calibration and regulator queries.
Who was the client?
Client names are withheld under confidentiality agreements. References are available on request.
What was the outcome?
10-year telemetry online; drift flagged before field crews notice.
Systems integration
EDRMS, CRM/ERP, D365, third-party APIs, legacy modernisation.
Explore this capability →This is one of roughly fifty engagements we ship per year. The full record, 2011 to today, lives on the delivery history page.