The Rio platform
Rio works with the protocols already on site, runs control, graphics and alarms on the box itself, and sends every reading to Oversee in the cloud.
The BMS, plus systems outside it such as lighting control.
BACnet · Modbus · KNX · OPC UA
Reads every point once a minute and holds data through outages.
Outbound MQTT over TLS
Archives every reading first, then summarises each hour and day.
Parquet · API · CSV
Twin platform, BI or data lake, reading only the sites you grant.
Read-only, open formats
Rio Gateway
DIN rail, one power feed, one network port. Registered with a one-time code, with applications switched on from the cloud and no site visit.
On the gateway
Each application is a module on the gateway, licensed per device and switched on from Rio Control. Logic, alarms and graphics run on the box itself, so when the line is down the building carries on.
Graphics
Engineers design pages of widgets bound to live site data; operators use them in the Rio interface or full screen on wall panels. Plant is drawn in 3D and follows the real thing: fans turn, the heat wheel rotates and water flows while its valve is open.
Logic
A block editor for building control. Build a program from inputs, gates, timers, PID loops and schedules, then deploy it to the gateway. Everyone connected edits one shared draft and can see each other's changes as they happen, allowing for collaborative logic design and review. Every change is recorded and you can go back in time if new logic ever causes a problem.
Triggers by point and class, contact groups and webhooks.
Watch what is on your network, monitor performance, and alert on unknown devices.
Site systems from anywhere, with a killswitch, locked to only the users and networks you specify.
Ships a reading a minute to the cloud archive, and holds readings through an outage.
Oversee
Oversee records what a building is actually doing, every temperature, meter, pump, valve, fan and fault, once a minute, and keeps it for the life of the building. It is a monitoring platform, not a control system: it watches a building, and cannot operate one.
Minute detail for 90 days by default, or longer by agreement; hourly and daily summaries kept for good.
Every reading is archived before anything is done with it, gateways keep recording through an outage and catch up afterwards, and every summary can be rebuilt from the original readings.
When a sensor fails or a meter goes quiet, the chart says so, with the reason. A gap is never filled with a guess, and a missing hour is never drawn as a zero.
Totals are taken from the meter's own register, so they always agree with the meter itself. Glitches are caught, and wraps, resets and meter replacements are handled, never guessed.
Full history as Parquet, by site and day, for Athena, Spark, Databricks or any Parquet reader.
Machine-to-machine access for your twin platform, scoped to the sites you grant.
Minute data as CSV on request. Commissioning logs and meter records imported into the same history.
Integrations
Client and server on BACnet and Modbus, so data flows both ways between Rio and the building's own systems.
Rio and your BMS
Rio can control a building itself, with its own logic, graphics and alarms running on the gateway. If you don't want to use our logic, you can keep your existing BMS: Rio sits alongside Trend, Niagara or EcoStruxure, collecting data for the twin. This is how Rio compares with a typical BMS supervisor.
| Aspect | A BMS supervisor, typically | Rio with Oversee |
|---|---|---|
| Built to | Run plant on one site: setpoints, sequences and alarms | Run plant on site, or work beside the BMS, and keep trusted data across a whole estate |
| Sources | Its own controllers first; other systems via drivers | Its own field interfaces, the BMS where there is one, and systems outside it such as lighting, water or ventilation control |
| History | Trend logs set up point by point, sized for fault-finding | Every point, every minute; hourly and daily summaries kept for good |
| Data quality | A failed sensor and a flat line can look the same | Bad readings and outages marked with the reason, kept out of totals |
| Portfolio | A head-end per site, or an extra enterprise layer | Every building in one organisation, behind one sign-in |
| Network | Remote access by VPN or an inbound port | Outbound MQTT over TLS to AWS IoT Core. Nothing to open |
| Data out | Exports and integrations per vendor, per site | Open Parquet archive, query API and CSV, the same on every site |
| Risk | Changes are made on the live control system | Control stays on site, on the gateway or the BMS. Oversee only observes; remote operation is limited to people you authorise |
Secure by design
The gateway connects out to AWS IoT Core over MQTT and TLS. No inbound rule, static address or VPN.
Each Rio is issued a certificate when registered, revoked the moment it is decommissioned.
Oversee can tune how a site reports, never how it runs. Remote operation, where enabled, goes through Rio's own interface and permissions.
No organisation can list, see or claim another's devices or data.
A client, FM provider or twin team sees only what you share, and you can revoke it centrally.
One sign-in across the platform, with multi-factor authentication and passkeys.
1 By default.
2 Oversee only observes. Where Rio runs the logic and remote access is enabled, people you authorise can operate the building through the gateway's own interface, under strict permissions you control.
Smaller sites
Where a site doesn't warrant a full BMS, Rio can provide comprehensive control and visualisation, as well as collecting the data.
Residential
Rio suits residential installations too, bringing lighting, shading, audio and home automation into one place with the same graphics, logic and remote access.
See what the Rio platform can do for your building, campus or whole estate.
office@logicallyus.com · 01183 111 010
