Technology

Sensors connected directly to a Robot terminal — scale heads, barcode scanners, temperature probes, contact inputs. Captured at the line and pushed to the Robot SCADA & IOT Server with the same authenticated transport as every other Robot transaction.

Long-range, low-power sensors using LoRaWAN — temperature, humidity, weight, and contact monitoring. A single gateway covers most packhouses and cold stores; sensors run for years on a battery.

Higher-bandwidth sensors that publish directly to the on-site MQTT broker over the existing Wi-Fi infrastructure — useful where mains power is available and reporting cadence is high.

Bluetooth Low Energy sensors and asset beacons for short-range applications — environmental monitoring inside containers, asset tagging, location-aware workflows.

Industrial MikroTik routers with BLE radios act as facility-wide BLE gateways — relaying beacon and sensor traffic from anywhere on the network to the central broker, all from the same hardware that handles routing, Wi-Fi, and switching.

Standards-compliant LoRa gateways forward sensor uplinks to the on-premise LoRaWAN Chirpstack server, part of the Robot IOT Server Stack, where they are decoded and per topic pushed onto the MQTT bus.

An authenticated, password-protected MQTT broker is the central pub/sub fabric — sensor uplinks, gateway traffic, and inter-service messaging all flow here, with separate credential sets for server-side workers and IoT devices.

An on-premise LoRaWAN network Chirpstack server handles gateway management, device provisioning, downlink scheduling, and per-topic payload decoding — all inside your network, all part of the Robot SCADA & IOT Server Stack.

Robot terminals and ITPC stations exchange transactional events with the Robot SCADA & IOT Server over HTTP using a JSON message format — the same format used end-to-end through the data pipeline.

The platform pushes sensor data out to third-party systems two ways: an outbound JSON-over-HTTP push to a partner endpoint for simple integrations, or — optionally — a RabbitMQ message bus that consumers subscribe to when a higher-throughput, durable queue is required. Pick whichever matches your integration partner's capabilities.

Every measurement, transaction, and event lands in a purpose-built time-series store inside the Robot SCADA & IOT Server. Range queries stay fast across hundreds of millions of rows; compression and retention policies keep storage cost predictable.

Live dashboards query the time-series store directly — bay temperatures, container counts, sensor health, throughput trends. The same database the application writes to is the one the dashboards read from.

Threshold breaches, sensor offline transitions, container movements, and operator actions are recorded as structured, severity-tagged events with full audit trail and configurable alerting.

JSON over HTTP, MQTT topics, and an optional RabbitMQ bus expose the platform's data surface to ERPs, traceability systems, and BI tools. Sensor data can be pushed outbound to a third-party HTTP endpoint or, where durability and throughput matter, made available on the message bus for partners to consume — without forcing a rebuild of your existing stack.