Most remote monitoring projects don't fail because the sensor was wrong. They fail because the edge hardware was picked before anyone looked hard at the site: no grid power, no fixed internet, a signal type the controller doesn't speak natively. Once you separate the field signal from the network path from the power source, choosing hardware stops being a guess.
What remote asset monitoring actually requires
At its core, a remote asset monitoring system connects a field sensor to an edge device, moves that reading over a network, and lands it somewhere useful, a dashboard, an alarm rule, a maintenance queue. The hard part is rarely the cloud side. It's the field-to-edge link, because every site brings a different combination of constraints:
- No fixed internet connection, so the network has to originate from the monitoring hardware itself (cellular, usually)
- No grid power, which rules out anything with meaningful standby draw
- A mix of signal types: 4-20 mA loops, RS-485/Modbus RTU, or simple digital status
Trying to force one controller architecture to cover all three is where most designs go wrong. NORVI's remote asset monitoring solution page lays this out as a routing decision rather than a single product recommendation, and that framing is worth borrowing even if you're not using their hardware.
Two edge paths, not one
For sites with no grid power and outdoor exposure, a battery-powered, low-duty-cycle node makes sense. The NORVI EC-M12 is built around an STM32L072 with a SIM7070 cellular modem (LTE Cat-M1, NB-IoT, 2G), IP67-rated, and fixed into variants for 4-20 mA, RS-485/Modbus RTU, or digital inputs. It's designed for periodic telemetry where battery runtime matters more than communication frequency. NORVI's own low-power study puts a two-cell 38,000 mAh pack at roughly 6+ years of practical runtime on a 1-hour transmit interval, though actual life depends heavily on signal strength and firmware behavior at your site.
For sites with 24V DC power, the calculus flips. The NORVI X platform runs an ESP32-S3 with modular I/O (up to 200 points across the range), built-in RS-485, Ethernet and Wi-Fi, with cellular available on the X2 and X3 variants. If the plant already has a LAN, X1 covers it. If the controller needs its own cellular uplink, X2 (4G LTE Cat 1 + 2G) or X3 (LTE Cat 4) fill that gap depending on throughput needs. NORVI's X1/X2/X3 comparison is a useful reference when the modem choice isn't obvious from the datasheet alone.
A pattern worth stealing: off-grid tank monitoring
One of the more common deployments is a tank or reservoir with no power and no wired connection nearby. The pattern is straightforward: a 4-20 mA or Modbus RTU level sensor feeds an EC-M12, which reports over NB-IoT or LTE-M to a cloud dashboard on a fixed interval. NORVI documents a reservoir monitoring build that pushes ultrasonic level data into ThingsBoard with alarm thresholds, and a related Modbus-over-MQTT guide for RS-485 sensors on the same kind of link. If you need TLS and certificate-based auth instead, there's also a documented Azure IoT Hub integration using X.509.
Where this breaks down
This architecture isn't a fit for continuous, high-rate monitoring; a battery node doing duty-cycled reporting shouldn't be asked to stream. It also isn't a fit for exposing IP20-rated hardware outdoors without an enclosure, and it doesn't hold up if you haven't confirmed the cellular bands your carrier actually supports before locking in hardware. None of these are dealbreakers, they're just decisions that need to happen before the BOM is finalized, not after the first field failure.
Takeaway
Remote asset monitoring architecture comes down to three questions asked in order: what power is available at the site, what signal type the asset exposes, and what network path can originate from the hardware itself. Answer those first and the controller choice, EC-M12 for off-grid low-duty-cycle telemetry, NORVI X for powered sites needing more I/O or local control, follows naturally. The full breakdown, including a platform comparison table and deployment patterns for pumps, utilities, and distributed cabinets, is on the NORVI remote asset monitoring page.
Top comments (0)