IO-Sphere
Build on existing systems rather than replace them.
Most projects come up against the same obstacle: gaining an overall view appears to require replacing everything. IO-Sphere takes the opposite approach: your controllers, meters and building management system remain in place, and their data is centralised.
One box on the building network, the platform as SaaS, and no inbound port to open on your network.
- 272
- device models recognised
- 35
- manufacturers covered
- 11
- field protocols
- 24 h
- of readings kept offline
- No limit
- on how long history is kept
Architecture
A simple architecture, from field to cloud.
The IO Hub provides the link between the building’s devices and IO-Sphere. Your teams work in a single platform.
Your devices
Controllers, sensors, meters and cameras, whether already installed or yet to come.
- Modbus
- BACnet
- LoRaWAN
- OPC UA
IO Hub edge
On the building’s local network: it polls the devices and sends their data upstream.
Supervision, alarms, automations, schedules and dashboards.
Your teams
Operators, technicians, energy managers: each with the views their job needs.
- SaaS, hosted in France by OVHcloud
- Up to 24 hours of measurements kept locally if the link drops
Integrations
Compatible with your devices’ protocols.
BACnet/IP and Zigbee describe their own points: IO-Sphere discovers them automatically. For Modbus and LoRaWAN, more than 270 ready-made drivers translate each device: ATIM, Carel, Dragino, Elsys, Milesight, Netvox, NKE Watteco, Socomec…
Protocols
- Modbus TCP
- Modbus RTU
- BACnet/IP
- KNX
- DALI
- OPC UA
- LoRaWAN
- MQTT
- Zigbee
- ONVIF
- RTSP
Manufacturer connectors
- Shelly
- Daikin
- Don’t see your protocol?Contact us
Shared core
From connected building to managed building.
The core functions of IO-Sphere, included whichever modules are switched on.
Dashboards
Views per site, building, floor or system, with the widgets each role needs.
Alarms
Severity levels, a delay before triggering, and detection that never writes to the devices.
Automations
Write a setpoint when a condition is met or at a set time.
Schedules
Normal / Eco states on weekly time slots, with exceptions for public holidays or closures.
Calculated points
Deviation, ratio, rolling average: the result becomes a point in its own right, ready to monitor and alarm on.
Spatial model & assets
Site › building › floor › space, virtual devices, categories and systems.
Points table
The full inventory of points, exportable to Excel.
AI assistant
A built-in AI assistant to save time in day-to-day operations.
Modules
One shared core, a module for each need.
Each client switches on the modules its project needs. Data, alarms and permissions stay the same: no new silo.
3D & 2D
Read the data right on the building.
3D model and 2D plans: an event is located at a glance, and every team shares the same picture.
GIS
From site to territory, on a map.
Buildings, devices and events placed on a map, to supervise scattered assets up to the scale of a territory.
EMS
Measure, understand and cut consumption.
Consumption, cost and carbon per building and per use, in kWh/m², corrected for heating degree-days, with drift detection and measured savings.
Multi-site
The whole portfolio, one shared view.
Compare sites, align indicators, centralise alarms and roll out the same standards across the portfolio.
SCADA
Installations as live diagrams.
Synoptic diagrams of technical installations, updated in real time, to follow a boiler room, an air handling unit or a network at a glance.
ESG
From operational data to ESG indicators.
Consumption, emissions and actions taken, consolidated across the portfolio, to feed non-financial reporting with traceable data.
Diagnostics
From the alarm to its root cause.
History, drifts and links between devices analysed to help operators find where an anomaly comes from and prioritise the fix.
CMMS
From supervision to maintenance.
A work order raised straight from an alarm, with the device, its location and its maintenance history.
VMS
Video as contextualised estate data.
Video streams and events tied to a zone, a device, an alarm or a 2D, 3D or map view: video is no longer an isolated screen.
SIQ
Measure how well spaces are used.
Space Intelligence Quotient: occupancy, comfort and environmental quality combined into indicators that show whether spaces meet occupants’ needs.
In the field
An alarm, where it actually happens.
Measurements are displayed on the installation schematic, where operators have their bearings, rather than in a table.
- Your plant as schematics: air-handling units, boiler rooms, networks
- Every point shows its latest value in its own place, not in a list
- A fault appears on the device concerned, and only on it
Security & hosting
Your data stays in France.
IO-Sphere is delivered as SaaS, hosted by OVHcloud in France and operated by ID4IT. We guarantee the sovereignty of your data.
Hosted in France
OVHcloud servers in France, a dedicated instance and databases for each customer, backed up every night to separate storage.
Encrypted in transit
HTTPS everywhere. The IO Hub opens its own encrypted connection to the platform: no inbound port to open on the building network.
Stronger sign-in
One-time code sent by e-mail or a passkey, and the account locks after 5 failed attempts.
Least-privilege access
Read or write, per building, floor, space and system: everyone sees and controls only their own scope.
Sealed audit trail
Every action is recorded in a chained log: any later change can be detected.
AI under control
Nothing an AI assistant suggests is applied without a user’s approval.
FAQ
Answers to the most common questions.
Is IO-Sphere a BMS?
No. A BMS controls a building’s technical devices. IO-Sphere sits above the existing systems, BMS included, to bring their data together and drive the performance of a building, a portfolio or a territory.
Do we need to replace our BMS or our devices?
No. IO-Sphere connects to the controllers, sensors and meters already installed, through their standard protocols. An existing BMS can stay in place: IO-Sphere reads its points over BACnet or Modbus.
Are our devices compatible?
IO-Sphere supports Modbus, BACnet, LoRaWAN, Zigbee and OPC UA, and comes with more than 270 ready-made drivers: ATIM, Carel, Dragino, Elsys, Milesight, Netvox, NKE Watteco, Shelly, Socomec… For a Modbus or LoRaWAN device not in the library, a driver can be created from the interface.
What do we need to install on site?
One IO Hub: a small box, or a service on a Linux or Windows PC, plugged into the building network. It connects out to IO-Sphere and never waits for inbound connections.
What happens in the event of an internet outage?
The IO Hub keeps up to 24 hours of measurements and sends them as soon as the connection is back. Schedules and automations keep running on site.
Where is our data hosted?
In France, by OVHcloud. Each customer has its own instance and its own databases.
Does IO-Sphere help comply with the French BACS decree?
It provides the functions the decree requires: hourly monitoring per zone, data kept beyond 5 years, drift alerts, manual shutdown and device control. We work out with you what each building has to cover.
Can we use it on mobile?
Yes, in the phone or tablet browser, with no app to install.
How are alerts sent?
By e-mail: to users, external addresses, mailing lists or following an on-call rota.
Can we start with a single site?
Yes. The shared core covers a first building; modules are then switched on as you need them, without changing platform.
Do you work with integrators?
Yes. ID4IT publishes the platform and our integration partners deploy it close to the sites. If you already work with an integrator, they can install IO-Sphere for you.