Technology & compliance

A hybrid architecture that is demonstrated, not declared

LoRaWAN as the primary channel, W-MBus OMS and NB-IoT where they are needed, and a platform that measures the quality of every single transmission.

Architecture

Four decoupled layers, each replaceable without touching the others

The radio layer identifies devices by technical serial number; the link to a customer account exists only in the application layer.

LAYER 1 · FIELD

Meters and sensors

  • MID-certified static ultrasonic meters, IP68
  • 19 multi-vendor families already integrated
  • Pressure and flow sensors, SCADA points
  • Local buffer: nothing lost while offline
→
LAYER 2 · NETWORK

Hybrid network, managed by ICCOM

  • LoRaWAN EU868, class A, OTAA, ADR
  • Multi-gateway reception and network deduplication
  • Gateways with cellular backhaul in outlying areas
  • ChirpStack v4 in the ICCOM datacentre
→
LAYER 3 · HYDROGUARD PLATFORM

Where data becomes a decision

  • 19 codecs decoded, dedup, plausibility checks
  • Radio quality measured on every uplink
  • Buffer recovery up to 90 days
  • Leak analytics, DMA/NRW, alarms with workflow
  • Tariff engine, e-invoicing, PostGIS GIS
→
LAYER 4 · APPLICATIONS

Dashboards and integration

  • Real-time operational dashboard, four languages
  • REST API, CSV/JSON/EDIFACT exports
  • Regulatory reports generated by the platform
  • Customer portal with self-reading
Transmission

No single radio reaches every meter pit — which is why the architecture is hybrid

Five transmission paths normalised into one platform, with the same quality, security and alarm criteria.

ChannelWhen it is usedWhat the platform guarantees
LoRaWAN EU868 — primaryThe ordinary channel: ICCOM-managed network, multi-gateway reception, class A/OTAA/ADRNetwork deduplication, radio margin measured on every uplink, redundancy KPIs
Gateway + cellular backhaulHamlets and clusters without fixed connectivity: densification with an ICCOM-managed SIMA uniform meter fleet; SIM and monitoring covered by the service
W-MBus OMSCommissioning, walk-by/drive-by, continuity at residual pointsReceiver-file import with preview and the same plausibility checks
NB-IoT — residual ≤1%Individual points that cannot be solved otherwise, after field verificationDedicated authenticated endpoint; same data and alarm pipeline
Manual / self-readingReconciliation, commissioning, customers in transitionCustomer portal plus operator CSV upload, anti-fraud and monotonicity checks
169 MHz systems: supported when the field device bridges to LoRaWAN or IP — the normalisation boundary is the codec registry, not the radio layer. Every reading is labelled with its source, so billing and reports can tell the channels apart.
Measured quality

Every uplink is measured: coverage is demonstrated with numbers

Frame counter, receiving gateways, spreading factor and latency are recorded for every transmission and become contractual KPIs.

≥98%
Packet Delivery Ratio per device, with rollover and rejoin handling
≥99.5%
monthly data completeness — computed before and after buffer recovery
≥2
receiving gateways per urban meter; SF11–12 share monitored
p50/p95
send → dashboard latency measured on every uplink

RF margin map

Every meter is classified on the GIS by radio margin: weak clusters drive gateway densification before they turn into missed reads.

Field test sessions

Cover open / closed / after rainfall: observation windows are recorded in the platform and KPIs are compared per condition.

Projected battery life

Battery trend per device on its real transmission profile: autonomy is verified, with a configurable alarm.

Meters

Multi-vendor interoperability: the utility chooses the meter

19 families already decoded. Qualification requirement: documented payload, unique keys handed over, decoder verified against the manufacturer’s test vectors.

G2 MisuratoriDiehlItronMaddalenaApator KamstrupZennerSensusAxiomaB-Meters Honeywell / ElsterJanzPietro FiorentiniWatertechDragino W-MBus OMSNB-IoTSigfoxCayenne LPP
📐

Reference meter

Static ultrasonic, MID, IP68, LoRaWAN class A + W-MBus OMS with automatic switching, local buffer ≥30 days, DN15–DN50. For large customers: Woltmann, electromagnetic or large-diameter ultrasonic meters.

🚨

Canonical multi-vendor alarms

Leak, reverse flow, tampering, battery, blockage and metrological error mapped onto canonical types: one alarm engine for the whole fleet, whatever the manufacturer.

🗃️

Unknown payloads retained

Uplinks that cannot be decoded are stored raw and can be re-decoded retroactively: no data lost while a new model is being qualified.

Network sensors: beyond meters, HydroGuard ingests pressure and flow sensors and SCADA points (Modbus TCP), correlating them with district consumption for leak analysis.
Technology stack

Proven open source, with no vendor or network-server lock-in

LayerTechnologyRole
RuntimeNode.js 22 · ExpressModular monolith, 30+ service modules
Time seriesInfluxDBTelemetry, radio quality, hourly profiles
Relational + GISPostgreSQL + PostGISMaster data, billing, mapping, audit
Queue & cacheRedis + BullMQAsync jobs, outbox, notifications, exports
IoT / LoRaWANChirpStack v4 · Mosquitto MQTTNetwork server, OTAA, ADR — never the source of truth
FrontendReact 18Operational dashboard, four languages
ObservabilityPrometheus · structured loggingMetrics, alerts, correlated logs
Continuity by design: a transactional outbox towards external systems, queues with dead-lettering, buffer recovery, encrypted backups with scheduled restore drills, and 16 operational runbooks.
Security & compliance

Critical-infrastructure standards, evidence generated by the platform

Identity and access

  • RBAC with roles per tenant and scope
  • Step-up MFA on privileged operations
  • JWT RS256 with zero-downtime key rotation
  • Managed, revocable sessions

Data protection

  • PII encrypted at rest (AES-256-GCM)
  • TLS in transit, unique OTAA device keys
  • Pseudonymisation by design
  • Immutable hash-chained audit trail

Regulation

  • GDPR: erasure, portability, fiscal archiving
  • NIS2: incident register, early warning on time
  • Technical-quality and authority reports automated
  • Country-specific e-invoicing formats

Operations

  • EU datacentres; on-premise optional
  • Encrypted backups + scheduled restore drills
  • OWASP reviews and continuous cross-tenant testing
  • Periodic penetration testing
Portability guaranteed by contract: data, device keys and decoders remain the utility's property. Changing supplier always remains possible.
Funding

Water-network digitalisation is fundable — with reportable KPIs

Leakage reduction and network digitalisation are eligible under a number of national and EU funding lines. Eligibility depends on the programme and the country.

💶

What tends to qualify

Programmes targeting leakage reduction, network digitalisation and operational efficiency, typically with milestones and mandatory KPI monitoring.

📋

Requirements met

MID meters, a platform with measured SLAs, automatic technical-quality indicator reports, full investment traceability and an immutable audit trail.

🤝

ICCOM support

Documentation support for the funding application, project KPIs verifiable in the dashboard, and transparent reporting for the controlling bodies.

Coverage

Service coverage in Italy

Water utilities served and active pilot projects.

Want to see these numbers on your own network?

A free technical assessment and a Demo Kit installable in 5 days: coverage is measured, not estimated.

Request the Demo Kit → Contact us

See how HydroGuard transforms your water network

Request a demo