Skip to content
AtheronLABS

You're visiting from the United States. Prices are shown in US dollars. Not right?

labs@atheron:~/industries/water-utilities/data$ query --warehouse --dashboards

Operations data

SCADA, lab and billing data in one place, read only.

Your operators have the data. It is split between the historian, the lab's files and the billing system, and the control room is the only place some of it can be seen. We bring it into one warehouse through read-only connections, so dashboards and report data come from the record, not a spreadsheet.

// what matters here

What is different in this industry.

01

Read only, always

Historian data comes through a one-way connection your control systems team approves. Nothing is ever written to SCADA.

02

Samples with their history

Each lab result keeps its sample point, method and chain of custody, so a number can be traced to the bottle.

03

Water loss you can see

Production set against billed consumption by zone shows where water goes missing.

04

Report data, not reports filed

Report data is prepared from the records for your responsible operator to review and submit.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb app

Operations data warehouse

Hypothetical. Not a client, not a result.

// The problem

A utility's operators see SCADA only in the control room, lab results live in spreadsheets, and the monthly report data and the council's dashboard are assembled by hand from both.

// What we would build

A data warehouse that reads SCADA historian data through a read-only connection, takes in lab results and billing consumption, and shows dashboards for operators, managers and council. It prepares report data for your responsible operator to review and submit. Nothing is ever written back to SCADA or any control system.

// What is in it

  • Historian data read through a one-way, read-only connection your control systems team approves
  • Lab results imported from your lab's files, with the sample, method and chain of custody kept
  • Consumption by zone from billing, set against production, to see water loss
  • Dashboards for operators, managers and council, each with what they need
  • Report data prepared from the records for your responsible operator to review and submit
  • Hosting, backups and monitoring run for you in a Canadian region

// Stack

  • PostgreSQL
  • dbt
  • Historian API (read-only)
  • Next.js
  • Apache Superset
  • AWS Canada

// estimate

Build
≈ US$89,700 to US$137,000, delivered within 19 weeksCAD 127,800 to 195,500
Hosting
≈ US$492 a monthCAD 700 a month
Support
≈ US$5,010 a monthCAD 7,135 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery
2.9 to 3.4 weeks
Design approved
2.9 to 4.9 weeks
Core features
2.9 to 4.4 weeks
Full build
1.9 to 2.9 weeks
Testing and fixes
0.9 weeks
Report data reconciled against a past period
0.9 to 1.4 weeks
Launch
0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Billing system API access from your vendor
1 to 4 weeks
Your control systems team's review of the read-only connection
4 to 8 weeks

How it is paid

Deposit 20%
CAD 25,560 to 39,100
Discovery 6.8%
CAD 8,690.40 to 13,294.00
Design approved 6.8%
CAD 8,690.40 to 13,294.00
Core features 20.4%
CAD 26,071.20 to 39,882.00
Full build 13.6%
CAD 17,380.80 to 26,588.00
Testing and fixes 6.8%
CAD 8,690.40 to 13,294.00
Report data reconciled against a past period 8.7%
CAD 11,118.60 to 17,008.50
Launch 6.9%
CAD 8,818.20 to 13,489.50
Holdback, 30 days after launch (10%)
CAD 12,780 to 19,550

// questions

Questions we get about this.

Can the dashboards change setpoints or start pumps?

No. The warehouse reads data only, through a one-way connection. Control stays with your operators and your control system.

Which historians can you read from?

Those with a published API or a read-only database view, such as AVEVA PI. We check yours with your control systems team before we quote.

Will it file our monthly drinking water report?

It prepares the report data for your responsible operator to review and submit. We give no regulatory advice.

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Data warehouse and dashboards for water and wastewater operations | Atheron Network Labs