NO GRID POWER · OUTDOOR
NORVI EC-M12
Battery powered · IP67 · low-duty-cycle
telemetry
CELLULAR
LTE-M / NB-IoT
2G
Industrial IoT Solution
Remote Asset Monitoring for Industrial Equipment & Sites
Monitor tanks, pumps, meters, machinery, and unattended assets by connecting industrial sensors to NORVI edge hardware and sending telemetry to the cloud over cellular, Ethernet, or Wi-Fi. Build an asset monitoring system around the power, signal, and connectivity conditions at each site.
IP67Battery-powered EC-M12 field telemetry
200 I/OScalable NORVI X platform range
4–20 mAPlus digital inputs and RS-485
Cloud-readyMQTT, ThingsBoard and Azure examples
REMOTE ASSET MONITORING ARCHITECTURE
Route field data by site conditions
Select by power · I/O · network
01 · FIELDSensors &
Sensors &
machine signals
4–20 mA
RS-485
Digital
02 · EDGE + NETWORK
Choose the route that matches the site
24 V DC · DIN RAIL
NORVI X
Modular I/O · monitoring + local control
Ethernet
Wi-Fi
X2 / X3 cellular
Both paths collect field data, process it at the edge, and move telemetry to the application layer.
03 · APPLICATIONCloud &
Cloud &
operations
Dashboard
Alerts
Analytics
AI workflows
Remote monitoring fundamentals
What Is Remote Asset Monitoring?
Remote asset monitoring is the collection of operating or sensor data from equipment that cannot be checked continuously on site. An asset monitoring system connects field sensors to an edge device, sends telemetry through a network, and makes the data available to dashboards, alarms, maintenance workflows, or analytics platforms.
The operational problem
01
Assets are spread across remote, distributed, or unattended locations.
02
Manual inspections can delay detection of abnormal levels, temperatures, equipment states, or process conditions.
03
Some sites have no fixed Internet connection, so the network path must come from the monitoring hardware.
04
Some sites also have no grid power, while field devices expose different signal types such as 4–20 mA, digital status, or Modbus RTU.
System architecture
How a NORVI Asset Monitoring System Works
Match the field interface, edge platform, network, and cloud integration to the installation instead of forcing every site into the same architecture.
01
Field sensors & machine signals
Use EC-M12 variants for a small number of analog, RS-485, digital, or mixed signals. Use NORVI X expansion modules when a powered machine or cabinet needs more channels.
02
Edge processing & local storage
EC-M12 uses an ultra-low-power STM32L072. NORVI X uses ESP32-S3 and adds RTC, display, Ethernet, RS-485, Wi-Fi and Bluetooth. Both families document microSD support for application-specific logging workflows.
03
Network connectivity
EC-M12 targets low-power cellular telemetry with LTE Cat-M1 and NB-IoT. X1 uses Ethernet/Wi-Fi, X2 adds 4G LTE Cat 1 + 2G, and X3 adds 4G LTE Cat 4.
Compare X1 / X2 / X304
Cloud-ready telemetry
NORVI documentation demonstrates MQTT telemetry to ThingsBoard and secure Azure IoT Hub integration using X.509 certificates. Once measurements reach the application layer, they can feed dashboards, alarm logic, trends, or predictive workflows.
Azure IoT examplePlatform selection
Choose the Right NORVI Platform
The most important first decision is whether the remote site is battery-powered and low-duty-cycle, or powered and expected to support modular I/O, continuous connectivity, and local automation.
No grid power · outdoor
NORVI EC-M12
Battery-powered IP67 telemetry node
EC-M12
- Best for periodic telemetry where long runtime matters more than continuous high-rate communication.
- Fixed variants for 4–20 mA, RS-485 / Modbus RTU, digital, or mixed inputs.
- SIM7070 cellular modem with LTE Cat-M1, NB-IoT and 2G.
- Wall or pole mounting with IP67 protection for remote outdoor deployments.
24 V DC · DIN rail
NORVI X
Modular monitoring and control platform
X1–X3
- Best when the site has 24 V DC power and needs more I/O or local control.
- Modular digital, analog, relay, transistor, RTD and other expansion options.
- Ethernet, Wi-Fi and built-in RS-485 across the CPU family; cellular on X2 / X3.
- IP20 hardware intended for a protected industrial cabinet or panel.
| Requirement | EC-M12 | NORVI X1 | NORVI X2 | NORVI X3 |
|---|---|---|---|---|
| Typical power model | Built-in non-rechargeable battery | 24 V DC | 24 V DC | 24 V DC |
| Installation | Wall / pole mount | DIN rail | DIN rail | DIN rail |
| Protection | IP67 | IP20 | IP20 | IP20 |
| Core use | Low-power remote telemetry | Powered LAN / Wi-Fi site | Powered cellular site | Powered higher-throughput cellular site |
| Cellular | Cat-M1 / NB-IoT / 2G | — | 4G LTE Cat 1 + 2G | LTE Cat 4 |
| Ethernet | — | Yes | Yes | Yes |
| Wi-Fi / Bluetooth | — | Yes | Yes | Yes |
| RS-485 | B variant | Built in | Built in | Built in |
| Local storage | microSD | microSD | microSD | microSD |
| I/O approach | Fixed, variant-specific | Modular | Modular | Modular |
Deployment patterns
Remote Monitoring Deployment Patterns
Start from the asset, power source, signal interface, and available network. These four patterns cover the most common remote-monitoring decisions.
Pattern 01
Off-grid tank or reservoir monitoring
Level sensor → EC-M12 → NB-IoT / LTE-M → cloud dashboard
Use the analog variant with a compatible 4–20 mA level sensor, or the RS-485 variant with a Modbus RTU level sensor. NORVI documents a reservoir workflow that sends ultrasonic level data to ThingsBoard with alarm rules.
Reservoir monitoring guide
Pattern 02
Remote utility or environmental telemetry
Meter / sensor → EC-M12 → cellular → MQTT / cloud
Use low-frequency measurements where battery runtime and outdoor protection matter more than continuous high-rate data. Documented interface choices include 4–20 mA, RS-485 / Modbus RTU, and digital inputs.
Modbus to MQTT guide
Pattern 03
Machine monitoring IoT for a powered site
Machine I/O / Modbus → NORVI X → LAN / Wi-Fi / cellular → cloud
Choose X1 when the plant already has Ethernet or Wi-Fi. Choose X2 or X3 when the controller needs its own cellular path. The modular platform suits machines with many signals or where monitoring and local automation must coexist.
Explore NORVI X documentation
Pattern 04
Distributed remote cabinets
Multiple field signals → NORVI X2 / X3 → cellular → central cloud
Use this architecture where every site has power but not a dependable wired Internet connection. Select X2 where 4G LTE Cat 1 plus 2G fits the carrier environment; select X3 where LTE Cat 4 is preferred.
X2 datasheetTechnical proof
Proven Low-Power Telemetry with EC-M12
Battery life is application-specific, so the page presents NORVI’s published low-power study as a documented estimate rather than a guarantee.
Published EC-M12 4–20 mA study
Two 19,000 mAh ER34615H cells · 38,000 mAh total nominal capacity
For practical deployment planning, use 6+ years for a 1-hour transmission interval. NORVI’s documented test model calculated 11.4 years under its specific assumptions, but real-world battery life depends on cellular signal strength, reconnection time, sensor current, transmission frequency, temperature, firmware behavior, and other deployment conditions.
Local data
microSD-supported logging workflows
Both platform families document microSD support for local logging, commissioning data, or application-specific buffering implemented in firmware.
MQTT + dashboards
ThingsBoard telemetry examples
NORVI documents RS-485 Modbus readings transmitted over MQTT and a reservoir example with cloud visualization and alarm configuration.
Secure cloud example
Azure IoT Hub with X.509
An EC-M12 example publishes 4–20 mA telemetry to Azure IoT Hub using X.509 certificates over TLS.
View implementation guideEngineering fit check
When This Architecture Is Not the Right Fit
Clear constraints help qualify a deployment before hardware selection and prevent a low-power telemetry node from being specified for the wrong workload.
Continuous high-rate monitoring
Do not choose EC-M12 where communication must be continuous or high-frequency. Use a powered platform such as NORVI X instead.
Exposed outdoor NORVI X
NORVI X CPU modules are IP20. Use an appropriate industrial enclosure or cabinet where greater ingress protection is required.
Unverified cellular compatibility
Supported bands differ between EC-M12, X2, and X3. Confirm deployment-country carrier technology and bands before final hardware selection.
Built-in AI claims
NORVI hardware collects and moves field data. AI or predictive analytics should be described as downstream cloud or application functions.
Application fit
Where Remote Asset Monitoring Creates Value
Use the platform decision to support the field environment rather than treating each application as a separate technology stack.
Tank & reservoir monitoring
4–20 mA or RS-485 level sensors, periodic cloud updates, and application-layer threshold alarms.
Pump station monitoring
Collect process values, equipment status, Modbus data, and remote alarm inputs from distributed pumping sites.
Water & utility monitoring
Collect level, flow, pressure, meter, or status signals from distributed infrastructure.
Industrial machine monitoring
Combine RS-485 and modular I/O with Ethernet, Wi-Fi, or cellular connectivity using NORVI X.
Agriculture & irrigation
Remote soil, water, tank, irrigation, or environmental telemetry where power and connectivity are limited.
Remote industrial sites
Use cellular connectivity where a fixed LAN is unavailable, with the edge platform chosen around available site power.
FAQs
Common
Questions
Can’t find what you’re looking for? Our team is available for a free technical consultation.
A remote asset monitoring system connects sensors or machine data to an edge device, sends the measurements over a network, and makes them available to dashboards, alarms, maintenance workflows, or analytics systems without requiring continuous on-site inspection.
NORVI EC-M12 is the better fit for low-power remote telemetry. It uses built-in lithium thionyl chloride batteries and is designed for duty-cycled operation in outdoor IP67 installations.
Yes. EC-M12-BC-C6-C-A provides two analog inputs and is documented for 4–20 mA sensor applications. EC-M12-BC-C6-C-D combines two analog inputs with one digital input.
Yes. EC-M12-BC-C6-C-B includes an RS-485 interface. NORVI documents an example that reads a Modbus RTU sensor and publishes the data to ThingsBoard over MQTT.
Yes, with the cellular CPU variants. NORVI X2 uses a SIMCOM A7672X modem with 4G LTE Cat 1 and 2G support, while NORVI X3 uses a Quectel EC25 LTE Cat 4 modem. X1 is intended for Ethernet and Wi-Fi-connected sites.
NORVI documentation includes EC-M12 examples for MQTT telemetry to ThingsBoard and secure telemetry to Azure IoT Hub using X.509 certificates over TLS. The exact cloud integration depends on the application firmware and cloud configuration.
NORVI X is modular. The documented expansion range includes digital inputs, relay and transistor outputs, 0–10 V and 4–20 mA analog inputs, analog outputs, RTD-related options, and other modules. NORVI states that the platform can scale up to 200 I/O points across the range.
Project selection support
Build the Right Remote Monitoring Architecture
Tell us the sensor type, number of I/O points, available power, communication coverage, reporting interval, and selected cloud platform. NORVI can help match the field interface, network method, and controller architecture to the site.
