Building management systems
Five vendor systems.
None of them yours.
puniq unifies every building management system you run into one readable layer you own, on your own premises.
The problem
Your building does not need another dashboard
The pattern repeats across towers in Riyadh, Jeddah and Dammam. Chillers report to one BMS, lighting to a KNX system, doors to an access control system, meters to a spreadsheet. Each was bought on its own contract, and each keeps its own truth.
- 01Five vendors, five screens
HVAC on the vendor's BMS, lighting on a KNX system, access control on its own server, sub-meters exporting to a spreadsheet, the fire alarm panel talking to nobody. Five logins, five naming schemes, five versions of the same building.
- 02One supplier for every change
The BMS system company that delivered the head end (the server and software that read your controllers) holds the passwords, the graphics and the license. Every new point, every export, every change order goes through them, at their price. That is the lock-in tax. The development lead at Résidence Aïcha 2 put it plainly: We did not want to discover, two years after handover, that our own building was locked to a supplier we had stopped trusting.
- 03Nobody can answer the simple question
How much cooling did the building use last Tuesday, and which chiller wasted it? Five dashboards give five numbers. None of them agree, and none of them are yours. No AI, no benchmark and no Mostadam evidence works until the building is readable.
What you get
One readable layer, yours to keep
We do not rip anything out. puniq sits above your existing controllers, normalizes their points to open protocols and hands you one model of the whole building, running on your premises.
One answer to any question about the building
Every controller, protocol, gateway and data point in your building is inventoried and mapped into one model. Each reading is named once, time-aligned and traceable back to the controller it came from.
Swap any vendor without losing history
Your systems normalized to BACnet, Modbus and MQTT, the languages your controllers already speak. Any qualified integrator in Saudi Arabia can service the layer, so no single supplier holds your points.
A building you can audit, transfer and keep
The Documented Data Map, the full vendor-neutral record of how your building is wired and read, is handed to your team at close. Legacy integrators leave a wiring diagram and an invoice. You keep the whole map.
How it works
From fragmented to readable in four phases
A disciplined engineering method with a fixed scope, delivered by engineers, not account managers. Weeks, not months. Nothing is ripped out.
- 01
Discover
We inventory every controller, protocol, gateway and data point in the building. Nothing is assumed. We document what is really running, including the systems no one remembered was there.
- 02
Unify
We normalize each system to open protocols and map every point into one shared model. Duplicate names collapse, the time base aligns, and the building becomes one readable structure.
- 03
Validate
We check the unified layer against the physical building. Readings are cross-verified, gaps are flagged, and every figure is confirmed against the controller it came from before sign-off.
- 04
Hand over
We hand the running on-premises layer to your team and close with the Documented Data Map. From there it is yours to operate, audit and extend, with no dependency on us or any vendor.
Proof
German engineering, applied to your building
05 partners and clients across Germany and North Africa. Engagements are led by Waddah Zekri, who reads a building at the controller level, not just the dashboard: industrial automation at ENIT Tunis, forecasting research at TU Dresden, predictive maintenance with HOOTS, instrumentation at CERN. Berlin-engineered rigor, and a refusal to ever lock you back in.
Energy waste typically removable
Vendor systems unified into one layer
Phases, weeks to a readable building, not months
Documented Data Map, yours to keep
We had three systems and three vendors and still could not answer one question: how much power do we actually have to spare? Putting it all on one screen changed how we think about the building.
Hotel Diar El Medina, Hammamet
A hotel tied to a single supplier: 3 systems unified, 100% data ownership returned, 25% indicative energy waste targeted, in validation.
Read more Case studyRésidence Aïcha 2, Immobilière de l'Archipel
A new residential development: one readable layer specified before construction, open protocols mandated in the tender, 35% indicative lifecycle energy headroom designed in.
Read moreWhy puniq
Why not just buy another vendor BMS
A vendor BMS is not a bad product. It is a product that ties your building to the company that sold it. Here is what changes when an engineer with no hardware to sell designs the layer. Engineer-led. No black boxes. Yours to keep.
Guide
Building automation systems, BMS and DDC, explained for Saudi buyers
Five short answers for anyone specifying, comparing or pricing a building management system in Saudi Arabia.
01What a building management system does, and how it differs from building automation and DDC
A building management system, or BMS, is the software and controller layer that watches and steers a building's plant: chillers, air handling units, pumps, lighting, meters and doors. It runs schedules and setpoints, raises alarms and keeps trend logs. In a Gulf building, most of that work is cooling.
The terms overlap on purpose. The older, wider label is building automation systems, or BAS, and it is the one most specifications still use. DDC, direct digital control, is the layer underneath: the controllers in the plant room that open a valve or speed up a fan. A BMS reads and coordinates the DDC controllers.
What you own is the controllers and the points on them. What a vendor sells is the head end that reads them. puniq works at the controller level, so the layer you keep is the one that lasts. Start with what a BMS is, in plain words, then DDC controls explained.
02BACnet, KNX and Modbus: the open-protocol foundation of a vendor-neutral BMS
A protocol is the language a controller speaks. BACnet is the open standard for HVAC and most head ends. Modbus is the plain, robust language of meters, chillers and drives. A KNX system usually sits behind KNX lighting control, blinds and room panels in offices and villa compounds. MQTT carries time-stamped readings to wherever the analytics run.
Vendor-neutral means the layer reads all of these as they are, over open interfaces, with no proprietary gateway in between. puniq specifies BACnet, Modbus and MQTT for anything new, and inventories the KNX islands and Modbus meters you already have so they are in the map, not outside it.
Which protocol wins decides who owns your building for its whole operating life. How BACnet, KNX and Modbus compare goes deeper, and why open protocols beat lock-in makes the commercial case.
- BACnet: HVAC controllers, AHUs, chiller plant head ends
- Modbus: power meters, sub-meters, chillers, variable speed drives
- KNX: lighting control, blinds, room controllers, villa automation
03Siemens, Schneider or Honeywell BMS? How to buy any brand without lock-in
Most building management system companies in Saudi Arabia sell one of a handful of platforms. A Siemens BMS system, a Schneider BMS or a Honeywell BMS each run a large building well. The risk is not the brand. It is the contract: proprietary graphics, a licensed head end, and one BMS system company allowed to touch your points.
puniq resells none of them, so nothing in our design is there to hit a hardware margin. We write the open-protocol tender language so any brand can bid on equal terms. You take it to market; we read whatever you already run. You keep the brand you trust and lose the dependency.
Comparing brands first? Read the independent 2026 BMS comparison and how to evaluate BMS software. Whatever the brand, three clauses keep it open:
- Every point exposed over BACnet or Modbus, no license fee for the export
- Graphics, passwords, engineering tools and naming standard handed to the owner at commissioning
- Any qualified integrator may service the system, in writing
04Access control, fire alarm and HVAC in one readable layer
These are the three systems almost every Saudi building has, and the three that least often talk. HVAC lives on the BMS. The access control system runs on its own server with its own gateway and license. The fire alarm panel stands alone by design and must keep its own loop.
One readable layer does not mean one controller for everything. It means every system reports into the same model, with the right boundaries kept for security-critical functions. Doors and fire stay on their own hardware. Their status, alarms and events are read, time-aligned and stored next to chiller data, so occupancy explains cooling load and a fire event explains why the AHUs stopped.
Cooling is the largest energy line in a Gulf building, so it is where a readable layer matters first. See HVAC control across every chiller and vendor, or the wider guide to multi-vendor BMS integration.
05What a BMS costs in Saudi Arabia: price drivers and how to budget
There is no single BMS system price. Four things drive the cost of a building management system in Saudi Arabia. First, the point count: every sensor, valve and meter the system reads. Then the number of vendor systems to tie in, the protocols they speak, and how much of the head end is licensed rather than owned. Cooling load and building size set the point count.
Two costs are easy to miss. The first is the lock-in tax: every later change order from a single supplier. The second is waste: in a fragmented building, the energy waste typically removable is 40%. Budget for the layer that lets you see it.
For capex and opex ranges per point, read the real cost of a BMS in the Gulf. To size your building, run the BMS points and budget estimator and bring the result to the assessment.
Systems and protocols
What the layer reads: BACnet, Modbus, MQTT and every vendor BMS
Named here as what owners in Saudi Arabia already run. puniq sits over them on open interfaces. None of these are partnerships or vendor endorsements.
- BACnet
- Modbus
- MQTT
- OPC
- HVAC and chiller plant
- Air handling units and pumps
- Lighting and KNX islands
- Metering and sub-metering
- Access control
- Fire alarm (status and events)
- Lifts
- On-site generation
- Siemens
- Schneider Electric
- Honeywell
- Johnson Controls
- KNX systems
Frequently asked questions
What is a building management system?
How much does a BMS system cost in Saudi Arabia?
Do we have to replace our Siemens, Schneider or Honeywell BMS?
BMS vs building automation system: what is the difference?
Does a vendor-neutral BMS help with Mostadam certification?
Can a KNX system integrate with a BMS?
How do we choose a BMS system company in Saudi Arabia?
What does puniq not do?
Tell us which systems you already run
Send the vendor names, the building type and the city. An engineer maps where the audit starts and what the Documented Data Map will cover, before any scope is written. You own the building, the data and the map. We only own the method.
The team replies within two business days.