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.

Check your lock-in risk

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.

  1. 01
    Five 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.

  2. 02
    One 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.

  3. 03
    Nobody 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.

See the Data Auditor
01

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.

02

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.

03

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

010

Energy waste typically removable

020

Vendor systems unified into one layer

030

Phases, weeks to a readable building, not months

041 map

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.
Operations ManagerHotel Diar El Medina, Hammamet

Why 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.

Typical vendor BMSpuniq
Who owns the data
Your server, but in the vendor's format, behind their license.
Your premises, in the Documented Data Map.
Protocols
Open at the controller, proprietary graphics and tools at the head end.
BACnet, Modbus, MQTT: what your controllers already speak.
Adding a system later
A change order from the same supplier.
Any qualified integrator, tendered competitively.
Hardware in the design
Boxes specified to hit a hardware margin.
Zero. We specify open parts, you buy and own them.
What you keep at handover
A wiring diagram and an invoice.
The whole map, 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.

Protocols
  • BACnet
  • Modbus
  • MQTT
  • OPC
Building systems the layer reads
  • 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
Brands and standards you may already run, not partners
  • Siemens
  • Schneider Electric
  • Honeywell
  • Johnson Controls
  • KNX systems

Frequently asked questions

What is a building management system?
A building management system is the software and controller layer that reads 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. A vendor-neutral BMS does the same on open protocols, so the owner, not the supplier, holds the points, the graphics and the history.
How much does a BMS system cost in Saudi Arabia?
A BMS system price in Saudi Arabia is set by point count, the number of vendor systems to tie in, the protocols they speak, and how much of the head end is licensed rather than owned. puniq publishes no price list, because the scope is fixed after the assessment. For capex and opex ranges per point, read the real cost of a BMS in the Gulf, then size your building with the points and budget estimator.
Do we have to replace our Siemens, Schneider or Honeywell BMS?
No. puniq does not rip anything out. We sit above your existing controllers, normalize their points to open protocols and give you one readable model of the whole building. The brand stays. The dependency on one BMS system company goes. Whether an old head end should be retrofitted or retired is answered in the audit, not in a sales call. See BMS retrofit vs rip-and-replace.
BMS vs building automation system: what is the difference?
Mostly vocabulary. The term building automation systems is the older, broader one used in specifications; BMS is what operators say. Both describe the same layer over DDC controllers, and SCADA is the industrial cousin. What matters more is whether every point is exposed over BACnet or Modbus, and whether you own the data. After handover the same layer feeds your facility management software.
Does a vendor-neutral BMS help with Mostadam certification?
It helps with the evidence. Your Mostadam or LEED consultant will ask for metered energy data, and a readable, vendor-neutral layer produces it from real meters rather than estimates. puniq is not a Mostadam consultant and does not award points. It supplies the data layer the consultant uses. See Mostadam evidence from real meters for the credits a readable building supports.
Can a KNX system integrate with a BMS?
Yes. The KNX system running your lighting control, the access control system and the HVAC BMS each keep their own hardware and safety boundaries. The layer reads their status, events and readings into one time-aligned model, so the building can finally show occupancy, lighting and cooling side by side. At villa and compound scale, see smart home systems designed open.
How do we choose a BMS system company in Saudi Arabia?
Score every BMS system company on openness before price: each point exposed over BACnet or Modbus with no export license, graphics and passwords handed over at commissioning, and any qualified integrator allowed to service the system, in writing. puniq is neither a vendor nor an integrator. A Berlin-based software company that sells engineering, not boxes, we audit what exists, design the vendor-neutral layer, and your contractors build from the specification. Metering questions continue on the energy management system page.
What does puniq not do?
We do not resell a manufacturer's stack, sell or hold hardware, or take control of your plant. The AI building management layer that can sit on top later is advisory only, and a person always approves every recommended action. If you want one more dashboard, puniq is the wrong call. If you want the building readable and yours, book an assessment.

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.

DEFRESTRع