Five systems, five screens.
The BMS, the meters, the lifts and the fire panel each speak their own protocol.
We design, connect and run the sensor network: temperature, air quality, occupancy, energy, leaks and vibration, joined to your BMS, with rules that raise the right alarm and predict the next failure.
IoT building monitoring uses networked sensors to track temperature, air quality, occupancy, energy, leaks and vibration as they happen. AIM United designs and connects the sensor network, joins it to your BMS and places each sensor on the BIM model, with rules that raise alarms and predict failures. We monitor buildings in Saudi Arabia, the UAE and the GCC.
The BMS, the meters, the lifts and the fire panel each speak their own protocol.
So the one that matters is muted with the rest.
No sensor where the risk is, or a sensor nobody connected.
Its vibration had been climbing for three weeks.
Show one type at a time, then tap a sensor on the model or below to read it: its value, its last 24 hours and how it reaches the network.
Switch rules on and off. Each one watches the sensors and raises an alarm on the model only when its condition holds.
Vibration velocity has risen from 1.6 to 3.9 mm/s in two weeks. At this rate it reaches the 4.5 mm/s service threshold in about nine days.
Drag through the day. Floors fill as people arrive, and the energy load and air quality follow them.
Which sensors, where and how many, planned on the BIM model.
Sensors, gateways and networks installed, tested and documented.
Existing systems joined over BACnet, Modbus and MQTT, without replacing what works.
Live views for operators, and weekly energy and comfort reports for owners.
Rules with thresholds, delays and escalation, so an alarm means something.
Vibration, run-hours and trends turned into a service date before the failure.
Schedules, set-points and demand matched to real occupancy.
Space use, air quality and comfort, floor by floor.
ISO 41001AIM United also delivers facility management, certified to ISO 41001:2018, so our monitoring is designed by people who run buildings.
Every device gets a points list: object type, units, alarm limits and a name that follows the project's naming convention. Where the platform uses them we tag points with Project Haystack or Brick, so dashboards and rules find the right data without hand mapping. Each point is tested end to end, from the field device to the dashboard, before handover.
Building systems are operational technology. In Saudi Arabia, critical facilities align with the National Cybersecurity Authority's Operational Technology Cybersecurity Controls (OTCC-1:2022). We keep field networks separate from the corporate IT network, route data to the platform through gateways, and agree at the start who owns the data and where it is hosted.
Retrofits start from what is already there: we read the existing BMS over BACnet or Modbus and add wireless sensors only where there are gaps. New buildings plan the network on the coordinated MEP model. Either way the readings flow into a digital twin for operations, on buildings across Saudi Arabia, the UAE and the GCC.
Yes. We integrate over BACnet, Modbus and MQTT and add sensors only where the existing system has gaps, so nothing that works needs replacing.
Both. Plant and meters are usually wired; leak, air quality and occupancy sensors are often wireless (LoRaWAN), which avoids opening ceilings in an occupied building.
Every alarm comes from a rule with a threshold, a delay and an owner. We tune the rules in the first weeks of operation, so alarms are few and each one needs an action.
Watching how an asset behaves (vibration, temperature, run-hours) and spotting the trend that comes before a failure, so it is serviced on a planned date instead of after a breakdown.
IoT is the sensor network and the data: what is measured, how it is connected and which rules act on it. The Living Twin puts that data on the model and runs operations and maintenance from it.
The schedule of every data point the system reads or writes: each sensor value, set-point, status and alarm, with its object type, units, limits and agreed name. It is the contract between the field devices, the BMS and the dashboards, and the checklist for commissioning.
Yes. We integrate with the systems already installed over open protocols such as BACnet, Modbus and MQTT, and coordinate with your BMS vendor on points, naming and access, instead of replacing equipment that works.
Field networks are kept separate from the corporate network, devices are reached only through gateways, accounts and remote access are controlled, and firmware is kept up to date. For critical facilities in Saudi Arabia we align the design with the NCA's OT cybersecurity controls.
You do. We agree at the start where the data is hosted, who can access it and how it is exported, so it stays usable if the platform or the service provider changes.