Utilities and water

Pump stations, reservoirs and substations you cannot visit every day

For small water and power utilities with assets spread over many small stations, a short crew, and little power or network to spare at any of them.

The problem

Many small stations, few people, and a binder in each one.

01

A round of visits to learn nothing changed

Operators drive a circuit of stations to read a panel and look around, because the station itself tells the office nothing.

02

Paper logs that stay in the pump house

The inspection sheet lives in a binder on site, so the office sees it weeks later, if at all.

03

On call and on your own

A night call-out goes to one person, at a station where phone coverage is patchy.

04

Which pump was rebuilt, and when?

The answer is in one operator's memory or a box of invoices, so the same fault gets diagnosed twice.

A week of one dish

Starlink installs software when it chooses, and the dish reboots to do it. Powoflow lists each update, the reboot it caused and the outage that followed, so the operator on call can tell a routine restart from a failed link.

Why it matters
A week of dish history: each software update, the reboot it caused and the outage that followed.

What it does not do yet

  • We have not bench tested level and pressure sensors yet. Ask, and we tell you plainly what we can supply.
  • Powoflow is not a SCADA system and does not replace one. It records, raises alarms and organises the work. Control of pumps and similar equipment is available on request through the Powoflow Sense Mesa gateway or the S2100 data logger, set up with you for your equipment.
  • No automatic station-down alarm. You set a not-reporting alarm on one sensor at the station.
  • The remote-site kit has not finished its solar trial at our test site, so we give no battery or data figures yet.

Tell us about your hardest station to reach

Where it is, what is in it and how often someone drives there.