--- title: "IoT monitoring and architecture | R&D COPILOT" lang: en canonical: https://iot.rdcopilot.com/ content_version: 6e0b6afb3553eaa731f3a579a6475759a93d4cc1ac8e62cad561abe30a888a0a contact: https://rdcopilot.com/contact/ --- [Home](https://rdcopilot.com/)/[Services](https://rdcopilot.com/services/)/IoT monitoring and architecture IoT and connected devices # Sensor data you can trust, from the device to the decision An IoT system is only as useful as the data that survives the trip from the sensor to the person who acts on it. We design and run the whole chain. Sensors are chosen per use: energy meters, cold-room and process temperature, equipment vibration and running hours, humidity, building conditions and, where needed, air quality. Gateways filter outliers, keep timestamps accurate and buffer readings while the link is down. The network is picked per site: the building network or Wi-Fi where it exists, LoRaWAN or cellular IoT for wide or remote areas, and Modbus or OPC UA for equipment already on the floor. Readings arrive over MQTT in a time-series store with retention, aggregation and export, then feed dashboards, threshold rules and alerts on the web and in a mobile app. Each device has its own identity, encrypted transport and signed over-the-air updates. Alerts and readings can open maintenance work in the ERP or update asset records, so sensor data ends up where the team already works. Setup is a one-off implementation fee, and the platform runs on a monthly subscription that covers hosting in the EU, updates and support. [Request a scoped quote](https://rdcopilot.com/contact/?service=iot-monitoring) [Request access](https://rdcopilot.com/account/?service=iot-monitoring) Start with your workflow. We agree the first deliverable, data boundaries, scope and budget before work begins. What we can deliver ## What your team receives. - Site survey and sensor plan: sensors, network, power and security for each location - Telemetry platform with MQTT and OPC UA ingestion, time-series storage, documented APIs and data export - Dashboards, threshold rules and alerts by e-mail, SMS or push notification - Device identity, TLS, role-based access and signed OTA updates - Commissioning checks and a data-quality dashboard: missing, late and suspect readings - Mobile companion app and connections to ERP, maintenance and reporting - Handover pack: operating guide, device inventory and runbooks Workflow in focus ### IoT monitoring and architecture A distributor runs two warehouses and a fleet of cold rooms. Temperature probes and energy meters report over the building network, a gateway holds readings during outages, and compressor vibration sensors flag wear. When a cold room drifts above its limit, the shift lead gets a push alert with the recent trend, and a repeated compressor fault opens a maintenance order in the ERP. The final design follows your systems, documents and operating requirements. ## Keep your team in control. ### Device security Every device gets its own identity and certificate, traffic is encrypted with TLS, and firmware updates are signed and can be rolled back. ### Data you can audit Raw readings, validation flags and every threshold change are kept with timestamps, so a value on a chart can be traced back to the device and the rule that judged it. ### EU hosting or on site Run the platform in an EU region or on your own server at the site, with open protocols and full data export. Connected products ## One thread, from first contact to final report. Every RDCopilot product works on its own and does more alongside the others. A campaign lead lands in the CRM, a won deal becomes an ERP order, the goods receipt updates stock, the invoice goes to e-Factura, and HR records feed payroll. Sensor readings and alerts reach the same dashboards. Reports and the AI assistant read from the right source, and mobile apps and eLearning take the work to the field and to your people. 1. [**Marketing**Attract and qualify demand](https://rdcopilot.com/services/marketing-and-sales/) 2. [**CRM**Track every customer and deal](https://rdcopilot.com/products/crm/) 3. [**ERP, stock and POS**Fulfil the order](https://rdcopilot.com/products/erp/) 4. [**Accounting and tax**e-Factura, e-TVA, e-Transport, declarations](https://rdcopilot.com/products/accounting/) 5. [**HR, payroll and REGES**People and their records](https://rdcopilot.com/products/hr/) 6. [**IoT monitoring**Sensors, readings and alerts ยท you are here](https://rdcopilot.com/services/iot-monitoring/) 7. [**Reports and AI**Decisions with the source attached](https://rdcopilot.com/products/ai/) 8. [**Mobile apps**The workflow in the field](https://rdcopilot.com/services/mobile-apps/) 9. [**eLearning**Training for your team and customers](https://rdcopilot.com/products/elearning/) Start with one module. Add others when you need them, on the same terms. Can we start small? Yes. Start with one workflow, one team and an agreed outcome. We scope the pilot after learning about your data, systems and constraints. Can our data stay in the EU? We can scope EU-hosted or self-hosted options. The proposal identifies where each component processes and stores data, which providers are involved, and any transfer or remote-access implications. EU hosting alone does not establish compliance. Can we use the tools we already have? We start with your current workflow and systems. The proposal identifies the integrations, data access and handoffs needed for a useful first deliverable. From idea to implementation ## Guides for your workflow. ### [Choosing the network for an IoT monitoring site: LoRaWAN, NB-IoT, LTE-M, Wi-Fi or Ethernet](https://rdcopilot.com/insights/iot-network-choice-lorawan-nb-iot/) 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. [Read guide](https://rdcopilot.com/insights/iot-network-choice-lorawan-nb-iot/) ### [From sensor alert to work order: connecting IoT monitoring to ERP and a mobile app](https://rdcopilot.com/insights/iot-sensor-alert-erp-work-order/) 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. [Read guide](https://rdcopilot.com/insights/iot-sensor-alert-erp-work-order/) ### [Telemetry that survives outages: buffering, MQTT QoS and duplicate control](https://rdcopilot.com/insights/iot-telemetry-outage-buffering-mqtt/) 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. [Read guide](https://rdcopilot.com/insights/iot-telemetry-outage-buffering-mqtt/)