platform · Australia · 2025

Novel Aquatech Portal

Engineering end-to-end software, IoT, and clean-tech solutions for urban challenges.

Duration5 months
Team3 engineers
StackReact · Node.js · PostgreSQL · MQTT · Chart.js · Azure
Livenovelaquatech.com
Alsoportal.novelaquatech.com

The problem

Service history, sensor readings and client commitments lived in three separate spreadsheets and one engineer's memory.

When a client asked whether their plant had been serviced on schedule, answering took a phone call and half a day.

How we approached it

We built the client-facing report first and worked backwards. If the portal could not produce the report a client wanted, the underlying data model was wrong.

Telemetry ingestion was designed to tolerate intermittent connectivity — installations lose network regularly, and a gap in readings must not look like a fault.

Architecture

Devices

On-site controllers publish readings over MQTT with local buffering.

Ingest

Broker writes to a time-series store; gaps recorded explicitly, not inferred.

Rules

Threshold and trend alerts routed to the right service engineer.

Scheduling

Service intervals per contract, with automatic escalation.

Portal

Client-facing dashboard and downloadable compliance reports.

Outcome

  • Client reporting became self-service, removing roughly a day a week of manual work.
  • Service-level breaches are now caught before the client notices them.

40+sites monitored live.

Tell us the hard part. That is the bit we want.

A 20-minute call, no deck. Bring the problem you have not been able to hand to anyone else.