Live monitoring · sensors to ERP
Sensors, gateways that keep readings through outages, dashboards and alerts: we design the chain, support the installation and run it. A reading that matters reaches the person on shift; a repeated fault opens a work order in your ERP.
One-off setup · monthly licence · EU hosting or your own server · support from the team that built it
Cold room 2
3.4 °C
Cold room 3
4.1 °C7.2 °C
Freezer 1
−19.6 °C
Compressor 3 · vibration
3.1 mm/s6.8 mm/s
Main meter, Warehouse B
38.6 kW
Dispatch dock humidity
61 % RH
Office air
720 ppm
Gateway B
Online
Data quality · 24 h
99.9 %
Example data. In a real project the work order is created in RDCopilot ERP as a service job linked to the asset record.
Example data.
Use cases
Each site starts from one question: which reading would have saved you money or stock last year? The sensors, the network and the alert rules follow from the answer.
| Room | Now | Min | Max | Peaks |
|---|---|---|---|---|
| Room 1 | 3.8 °C | 2.9 °C | 4.6 °C | 2 |
| Room 2 | 3.4 °C | 2.7 °C | 5.1 °C | 4 |
| Room 3 | 4.1 °C | 3.2 °C | 5.6 °C | 6 |
| Room 4 | 2.9 °C | 2.4 °C | 3.9 °C | 1 |
Peaks: brief rises that recover within the rule duration (likely door openings). Not alarms.
| Circuit | kW now | kWh today | kWh last week |
|---|---|---|---|
| Main | 38.6 | 412 | 436 |
| Cold rooms | 21.3 | 231 | 240 |
| Compressors | 11.8 | 118 | 121 |
| Lighting | 3.2 | 38 | 52 |
| Asset | Vibration | Running | Starts/day | Status |
|---|---|---|---|---|
| Compressor 1 | 2.4 mm/s | 5 880 h | 14 | ● OK |
| Compressor 2 | 2.9 mm/s | 6 020 h | 11 | ● OK |
| Compressor 3 | 4.8 mm/s | 6 214 h | 23 | ▲ Warning |
| Compressor 4 | 1.9 mm/s | 3 410 h | 9 | ● OK |
| Room | °C | % RH | CO₂ ppm | Status |
|---|---|---|---|---|
| Office 1 | 22.4 | 44 | 720 | ● OK |
| Office 2 | 23.1 | 41 | 1 140 | ▲ Ventilate |
| Meeting room | 24.0 | 47 | 980 | ● OK |
| Canteen | 21.6 | 52 | 860 | ● OK |
| Dispatch office | 19.8 | 58 | 640 | ● OK |
| Training room | 22.9 | 45 | 1 020 | ▲ Ventilate |
| Room | Mon | Tue | Wed | Thu | Fri |
|---|---|---|---|---|---|
| Office 1 | 780 | 940 | 1 080 (above limit) | 890 | 760 |
| Office 2 | 820 | 1 120 (above limit) | 1 160 (above limit) | 1 010 (above limit) | 880 |
| Meeting room | 690 | 760 | 820 | 1 040 (above limit) | 700 |
| Canteen | 640 | 700 | 720 | 680 | 610 |
Architecture
Most monitoring problems sit between two suppliers. We design and run the whole chain, so a missing reading has one owner.
We choose
Energy meters, cold-room and process probes, vibration and running-hour sensors, humidity, building conditions, air quality where needed.
You get
A sensor plan per location, with power and mounting for each point.
We choose
Edge gateways that filter outliers, keep accurate timestamps and store readings while the link is down.
You get
An outage delays data instead of losing it.
We choose
Building LAN or Wi-Fi where it exists, LoRaWAN or cellular IoT (NB-IoT, LTE-M) for wide or remote areas, Modbus or OPC UA for equipment already on the floor.
You get
A written network choice per site, with the reasons.
We choose
MQTT with the right QoS level, OPC UA where machines speak it, duplicate control on arrival.
You get
Each reading counted once, with the time it was measured.
We choose
Retention and aggregation rules per signal, documented API and export.
You get
Raw data kept as long as you need it, summaries for long trends, CSV whenever you ask.
We choose
Dashboards per role, threshold rules with duration, alerts by e-mail, SMS or push, a mobile companion app.
You get
The right person hears about it, once, with the trend attached.
We choose
Links to RDCopilot ERP, Reports and your maintenance process.
You get
Repeated faults become work orders, energy lands in reports.
Hardware
Sensors are chosen per use, not from a catalogue. These six device types cover most sites; the site survey decides how many of each, where they mount and how they are powered. Work inside electrical panels is done by a licensed electrician, yours or one arranged in the proposal. Reading intervals are examples and are set per signal.
Edge gateway · outage test
The gateway keeps every reading with the time it was measured, then replays the backlog when the link returns. Late readings are marked on the data-quality dashboard, not dropped.
GW-B · online · buffer 0 readingsGW-B · link down — buffering 214 readings
Example data. An outage delays data instead of losing it.
Every device is listed in the device inventory you receive at handover, with its location, network and power. How we choose the network
Alarms that lead somewhere
Too many alerts and people mute the app. Too few and the first sign of trouble is a stopped line. Rules are tuned on site during the pilot.
CR-03 · 7.2 °C · 14:22:00Measured every 60 seconds, stamped at the sensor.
> 6 °C for 10 minA limit and a duration, so a door opened for a minute is not an alarm.
push + SMS → shift leadOne message with the value, the trend and what to check first.
not acknowledged in 15 min → maintenance leadIf nobody confirms, the next person is told.
3rd fault in 7 days → ERPThe order is linked to the asset, with the readings attached; spare parts come from stock.
Read the full guide: from sensor alert to work order
Mobile companion app · iOS and Android
Data quality
Was the value fine, the sensor off or the link down? We track every reading as on time, late, missing or suspect, show it on a data-quality dashboard and explain each flag. Commissioning ends only when that dashboard is clean.
| Device | Expected | Received | Late | Missing | Suspect | Reason |
|---|---|---|---|---|---|---|
| CR-02 | 1 440 | 1 440 | 0 | 0 | 0 | No flags |
| CR-03 | 1 440 | 1 440 | 2 | 0 | 0 | Replayed from gateway buffer after a 2 min link drop |
| CMP-03 | 288 | 288 | 0 | 0 | 1 | Same value 6 times in a row — check mounting |
| RH-01 | 96 | 96 | 0 | 0 | 0 | No flags |
Security
Each device has its own identity and certificate. No universal default passwords.
Traffic from gateway to platform runs over TLS.
Firmware updates are signed, verified on the device before install, and can be rolled back.
Shift leads, maintenance and management see what their role needs.
Raw readings, validation flags and every threshold change are kept with timestamps.
Open protocols, documented API and full export. EU region or your own server on site.
Connections
We list only the protocols and systems we support.
RDCopilot telemetry platform
ingest · store · rules · alerts · APIPart of RDCopilot
Project
We walk the site, check power, network coverage and existing controllers. You get a sensor plan per location and an itemised proposal.
Deliverables: Sensor plan · proposal
One room, line or building, live on the platform. Rules are tuned with the people who receive the alerts.
Deliverables: Live dashboards · tuned rules
The remaining points are installed with our support and commissioned. Commissioning checks and a clean data-quality dashboard close each site.
Deliverables: Commissioning checks · clean data quality
Operating guide, device inventory and runbooks. We keep the platform updated and answer when something looks wrong.
Deliverables: Operating guide · device inventory · runbooks
One site, one use case; sensors, gateway, dashboards and alerts; ends with a decision on rollout.
Ask about this: PilotSeveral sites or use cases on one platform, with ERP and Reports links.
Ask about this: Site rolloutYou already have meters or controllers with Modbus or OPC UA; we connect them through a gateway, check data quality and security, and add sensors only where a reading is missing.
Ask about this: Start from what you havePricing
Survey, sensor plan, installation support, commissioning and training. The proposal lists each sensor, gateway and network item.
Per user, terminal or workspace; the proposal is scoped to the sites and devices you connect. Includes the platform, EU hosting, backups, security and functional updates, and support.
In an EU region, or on your own server at the site. Open protocols and full export either way.
The team that built your system, in English or Romanian.
Extra development is billed at a fixed hourly rate, only against estimates you approve in writing. Get a setup and licence quote
Guides
Compare LoRaWAN, NB-IoT, LTE-M, Wi-Fi and Ethernet by payload, reporting interval, range, power and coverage, then pick the right link for each part of a monitoring site.
Keep sensor data complete through power cuts, link drops and broker restarts with store-and-forward gateways, the right MQTT QoS, idempotent ingestion and a recovery test you can repeat.
Turn sensor readings into action: alert rules with duration and hysteresis, clear push cards, work orders in ERP for repeated alerts, spare parts from inventory and a closed loop in reports.
Questions
Something else on your mind? Ask it in the survey request; an engineer answers.
Not usually. Equipment with Modbus or OPC UA connects through a gateway, and we add sensors only where a reading is missing. The site survey lists what stays and what is new.
The gateway keeps readings locally and sends them when the link returns, with the time each was measured. Late readings are marked, not lost, and duplicates are removed on arrival.
It depends on distance, how often you need a reading and what powers the sensor. We choose per site and per sensor group and write the reasons down; the dashboards do not care which radio carried the value.
Alerts go to named roles by e-mail, SMS or push. Rules combine a limit with a duration, and unconfirmed alerts escalate to the next person. We tune them during the pilot with the people on shift.
Yes. With RDCopilot ERP, a repeated fault opens a service job linked to the asset, with the readings attached. For another ERP or maintenance system, we connect through its API.
In an EU region or on your own server at the site. Readings are available through a documented API and full CSV export at any time.
It depends on the site and the number of points; the survey proposal gives a dated plan. A pilot covers one room, line or building so you can judge the alerts before rolling out.
A one-off setup fee covers the survey, installation support, commissioning and training. A monthly licence covers the platform, EU hosting, updates and support. Extra work is billed at a fixed hourly rate against estimates you approve.
Site survey
List the sites, the cold rooms, panels or machines, and the problem you want to catch earlier. An engineer replies with questions, then a survey date. No technical specification needed.
Your first sensor
4.1 °C