Choose where to start

Compare Monitoring Architectures and Costs

Buyer-oriented frameworks for system selection, LoRaWAN versus cellular LPWA, and lifecycle cost modeling.

Use these comparisons before a request for proposal, pilot or architecture decision. They deliberately avoid vendor rankings because suitability depends on site distribution, operator coverage, maintainability, data needs and response workflow. Score evidence rather than marketing claims: installed reference checks, forced outage recovery, data export, device identity, update controls, field-service intervals and end-to-end alert tests. Lifecycle cost should keep site visits, connectivity, gateways, calibration, replacement and operations visible as separate variables. If one uncertain assumption can reverse the preferred option, make that uncertainty a pilot objective rather than hiding it in an average.

Compare Remote Water Monitoring Systems by Lifecycle, Not Dashboard Features

A procurement framework for sensors, power, connectivity, data ownership, security, maintenance and response integration.

Open

LoRaWAN vs Cellular LPWA for Water Monitoring

Compare private LoRaWAN with NB-IoT/LTE-M by site density, gateway responsibility, field coverage, energy, roaming, backhaul and failure concentration.

Open

Water Monitoring Costs: Build a Five-Year TCO Model

A transparent cost model for hardware, installation, connectivity, field visits, calibration, replacements, software and response operations.

Open

Remote monitoring site planner

Estimate raw payload volume and choose the first connectivity pilot.

Open

Pump downtime calculator

Model pump-outage days under a repair-time target.

Open

Connectivity field procedure

Turn the architecture decision into installed-site evidence.

Open
How to use this section

Before a commercial pilot, turn every important requirement into an observable test and mark whether the evidence comes from a specification, a supplier demonstration or the installed field system. Unknowns are acceptable before the pilot; hidden unknowns are not. Use the comparison matrix to decide what the pilot must resolve, then use lifecycle cost only after operating responsibilities are explicit.