IoT and connected devices
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.
Start with your workflow. We agree the first deliverable, data boundaries, scope and budget before work begins.
What we can deliver
Workflow in focus
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.
Every device gets its own identity and certificate, traffic is encrypted with TLS, and firmware updates are signed and can be rolled back.
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.
Run the platform in an EU region or on your own server at the site, with open protocols and full data export.
Connected products
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.
Start with one module. Add others when you need them, on the same terms.
Yes. Start with one workflow, one team and an agreed outcome. We scope the pilot after learning about your data, systems and constraints.
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.
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
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 guideTurn 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 guideKeep 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