OperationIoT Monitoring & Smart Buildings
All services Esc

IoT Monitoring & Smart Building Systems Every sensor on real equipment, every point live.

We design, connect and commission the sensors and BMS points on chillers, pumps, air handling and fan coils, and in the rooms for air quality, occupancy and leaks, with rules that raise the right alarm and trends that predict the next failure.

AIM United · In short

What is IoT building monitoring?

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 problem

The building has sensors. Nobody hears them.

01 · Silos

Five systems, five screens.

The BMS, the meters, the lifts and the fire panel each speak their own protocol.

02 · Noise

A thousand alarms a day.

So the one that matters is muted with the rest.

03 · Blind spots

The leak is found by the tenant below.

No sensor where the risk is, or a sensor nobody connected.

04 · Reactive

The pump fails on a Friday night.

Its vibration had been climbing for three weeks.

Stage 1 · Sensors on real equipment

Every sensor sits on the thing it measures.

Unit A-01 and its plant yard, the same federated MEP model as our Immersive Reality and As-built pages: 39 devices and 69 BACnet points on the chiller, the pumps, the fresh-air unit, the fan coils and their valves, the distribution board, and air quality, occupancy, leak, smoke and door sensors in the rooms. The values follow a 24-hour day at 12 minutes a second. Tap a sensor on the model or pick one below.

Sensor type
Devices

Stage 2 · The plant, as the BMS sees it

Chiller to fan coil, every value live.

The chilled-water loop as an operator's schematic: CH-01 makes chilled water, CHWP-01 pushes it up the riser on a variable-speed drive, and FAHU-01 and three fan coils take what they need through their valves. Supply and return temperatures, valve positions, fan speeds and power all come from the points on the model. Tap a component to find it on the model, or tap the plant on the model to find it here.

    Stage 3 · Rules and alarms

    An alarm is raised, owned, and closed.

    Rules decide what becomes an alarm. Each alarm then has a priority, an owner and a lifecycle: raised, acknowledged, shelved, cleared. Switch a rule off and its alarms disappear from the day; pick an alarm and walk it through.

      Alarms raised today0
        Alarm flood · CH-01 trips at 15:05

        40 raw alarms in 90 seconds

          Predictive maintenance

          FAHU-01 supply fan bearing: service in 9 days

          14 days agoToday+9 days

          Vibration velocity on the fan bearing (point JED-B01-EX-FAHU-01-VIB, AI-9) has risen from 1.6 to 3.9 mm/s in two weeks. At this rate it reaches the 4.5 mm/s service limit in about nine days, so the bearing is changed on a planned visit, not after a trip.

          The work order behind each alarm, its technician and its close-out run in the digital twin. This page stops at the point, the rule and the alarm.

          Stage 4 · Sequences of operation

          The controls, through one day.

          Drag through the day. Rooms fill and empty, the fan coils set back when nobody is home, fresh air follows CO₂, and the chilled-water supply resets with the load. The same clock drives every value on the page.

          06:00
          0People home
          0Plant and unit, kW
          0Highest CO₂, ppm
            00:0012:0024:00
              From sensor to dashboard

              Open protocols, one data path, a separate OT network.

              1. 01 · FieldSensors, meters, actuatorsWired on BACnet MS/TP and Modbus RTU, wireless on LoRaWAN, placed where the risk and the load are.
              2. 02 · ControlControllers and gatewaysDDC-P01 runs the plant, each fan coil has its own controller, and GW-01 and GW-02 turn LoRaWAN and Modbus into BACnet objects.
              3. 03 · OT networkBMS server and historianBACnet/IP on its own network and VLANs, with the trend log, the alarm server and the schedules.
              4. 04 · Through a DMZPlatform, dashboards and the twinData leaves the OT network only through a DMZ with MQTT over TLS, one way unless a write is agreed.
              BACnetASHRAE 135 (also ISO 16484-5): chillers, AHUs, fan coils and the BMS, as objects and properties.
              ModbusMeters, drives and plant controllers, read through a gateway and mapped to BACnet points.
              MQTTLight, encrypted messaging from the edge to the platform, outbound only.
              LoRaWANLong-range, low-power wireless for leak, air quality, occupancy and door sensors.
              Zone 0–1 · Field39 devicesMS/TP trunk, Modbus RTU, LoRaWAN radio
              Zone 2 · ControlDDC-P01, FCU-01–03, CH-01 cardGW-01 LoRaWAN, GW-02 Modbus
              Zone 3 · OT networkBMS server, historian, alarmsBACnet/IP, its own VLAN, no internet route
              DMZBroker and jump hostMQTT over TLS out; remote access by named account with MFA
              Zone 4 · EnterpriseDashboards and the twinReads the data; never reaches a controller directly

              NCA OTCC-1:2022For critical facilities in Saudi Arabia we design the zones, remote access and accounts to align with the National Cybersecurity Authority's Operational Technology Cybersecurity Controls.

              What we deliver

              Everything a smart building needs to listen and act.

              01

              Sensor design and placement

              Which sensors, where and how many, placed on the coordinated MEP model with their device and point names. Model and device schedule.

              02

              Points list, naming and tags

              Every BACnet object with its name, Haystack or Brick tags, units, reporting and alarm limits, agreed with you and the BMS vendor. XLSX.

              03

              BMS integration

              Chillers, pumps, AHUs, fan coils and meters joined over BACnet, Modbus, MQTT and LoRaWAN, keeping the equipment that works.

              04

              Installation and commissioning

              Point-to-point tests, sequences run against the written sequence of operation, alarms forced and cleared. Commissioning record.

              05

              Alarms and rules

              Priorities, owners, delays, root-cause suppression and escalation, so an alarm means an action. Alarm philosophy and rule list.

              06

              Plant graphics and dashboards

              Operator schematics with live points, trends and weekly energy and comfort reports for owners.

              07

              OT network and security

              Field, control and OT zones, a DMZ, named remote access, aligned with NCA OTCC-1:2022 where it applies. Network drawings.

              08

              Predictive maintenance and energy

              Vibration, run hours and trends turned into service dates; meters, schedules and setpoints tuned to real occupancy.

              This service · IoT and BMS integration
              • Sensors, meters, controllers and gateways, placed and installed
              • The points list: names, tags and BACnet objects
              • Plant graphics, sequences of operation and alarm rules
              • Commissioning, the OT network and its security
              Digital Twins & FM · operations on top
              • Work orders raised from alarms, and their close-out
              • Planned maintenance and asset history
              • Space use, monthly reports and reviews
              • The model as the operations front end
              Where it applies

              Buildings where a missed alarm costs the most.

              250+

              Engineers across BIM, MEP design and contracting, so the sensors, the points and the coordinated MEP model come from one team.

              ISO 19650

              Information management to ISO 19650: device and point data are handed over with the model, named and checked.

              ISO 9001

              Quality, environment and safety management certified to ISO 9001, ISO 14001 and ISO 45001, from installation to commissioning.

              ISO 41001AIM United also delivers facility management, certified to ISO 41001:2018, so our monitoring is designed by people who run buildings.

              Points, commissioning and security

              A sensor counts once it is a named, tested point.

              Every device gets a points list, like the one below: 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.

              The points list

              69 points, each one named, tagged and tested.

              The points list is the contract between the field devices, the BMS and every dashboard. Ours carries, for each point: the name in the project convention, the tag set, the BACnet object type and instance, units, how it reports, its alarm limits, and the system, equipment and room it belongs to, with the commissioning record next to it.

              System

              Commissioning record: P2P = tested point to point from the device to the BMS graphic; Trend = logging at the agreed interval; Alarm = limit forced and the alarm seen, acknowledged and cleared.

              Codes and standards

              The rules a smart building answers to in the Kingdom.

              What each one asks of the monitoring
              Code or standardWhat it asksWhere it shows
              NCA OTCC-1:2022Operational Technology Cybersecurity Controls from the National Cybersecurity Authority, for organisations that run OT in critical facilities: separated networks, controlled remote access, managed accounts, monitoring.The zones and DMZ above
              Saudi Building CodeThe energy conservation codes, SBC 601 for non-residential and SBC 602 for residential buildings, set the efficiency and HVAC control requirements the controls are designed to.Setback, fresh-air control, CHW reset
              ASHRAE 135 · BACnetThe object model and services for building automation: every value is an object with a type, an instance and properties a BMS can read, write or trend.Object type and instance on every point
              Project Haystack · BrickOpen tagging and schema conventions, so software can tell a chilled-water supply temperature from a room temperature without a person mapping it.The tag set column
              SEECThe Saudi Energy Efficiency Center leads the national energy efficiency programme, buildings included. Metered energy is the evidence efficiency work rests on.Energy meters EM-01 to EM-03

              The fire alarm system stays on its own panel and its own approvals: the BMS reads the detectors through a BACnet interface for the record and the graphics, and never writes to the fire panel.

              How we run it

              Survey, points, install, commission, tune.

              1. 01

                Survey

                What is already installed and on which protocol, read from the existing BMS, the drawings and a walk of the plant.

              2. 02

                Points

                The points list, naming and tags agreed with the client and the BMS vendor, and every device placed on the coordinated MEP model.

              3. 03

                Install

                Sensors, controllers and gateways installed, the OT network built in its zones, the field wiring labelled to the points list.

              4. 04

                Commission

                Point-to-point tests, sequences run against the written sequence of operation, alarms forced and cleared, trends checked.

              5. 05

                Tune

                Limits, delays and rules tuned in the first weeks of operation, so alarms stay few and each one needs an action.

              Questions buyers ask

              FAQ

              Can you connect to our existing BMS?

              Yes. We integrate over BACnet, Modbus and MQTT and add sensors only where the existing system has gaps, so nothing that works needs replacing.

              Wired or wireless sensors?

              Both. Plant, controllers and meters are usually wired; leak, air quality, occupancy and door sensors are often wireless (LoRaWAN), which avoids opening ceilings in an occupied building.

              How do you avoid alarm floods?

              Every alarm comes from a rule with a threshold, a delay, a priority and an owner. Root-cause suppression hides the alarms that follow from one fault, repeats of a point count once and chatter is filtered, so a chiller trip raises one alarm, not forty. We tune the rules in the first weeks of operation.

              What is predictive maintenance?

              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.

              How is IoT different from a digital twin?

              IoT is the sensor network and the data: what is measured, how it is connected, how each point is named and which rules act on it. The digital twin puts that data on the model and runs operations and maintenance from it.

              What is a points list?

              The schedule of every data point the system reads or writes: each sensor value, setpoint, 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.

              What is BACnet, and why does it matter?

              BACnet is the open protocol for building automation, published as ASHRAE 135 and as ISO 16484-5. Every value is an object with a type and an instance, such as an analog input or a binary output, that any compliant BMS can read, write and trend, so equipment from different makers works on one system.

              What do Project Haystack and Brick tags do?

              They describe what a point is in a form software can read: a chilled-water leaving temperature sensor on CH-01, not just AI-1 on device 201001. Dashboards, analytics and fault-detection rules then find the right points on any building without someone mapping them by hand.

              How do you test the points before handover?

              Point to point: every sensor is checked against a reference reading and every output is driven and watched at the device, from the field to the BMS graphic. Then the sequences are run against the written sequence of operation, alarms are forced and cleared, and the trend logs are checked. The results are recorded against the points list.

              Do you work with our existing BMS vendor?

              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.

              How are the sensors and network kept secure?

              Field and control networks are kept apart from the corporate network, data leaves through a DMZ, devices are reached only through gateways, remote access uses named accounts, and firmware is kept up to date. For critical facilities in Saudi Arabia we align the design with the NCA's Operational Technology Cybersecurity Controls (OTCC-1:2022).

              Can the BMS connect to the fire alarm system?

              The BMS can read the fire alarm panel through an interface, for the records and the graphics. The fire system keeps its own hard-wired interfaces to the plant and its own approvals; the BMS never controls it.

              Who owns the data?

              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.