Most commercial buildings are not short on technology. They are short on coherence. A typical tower runs five or more vendor systems for HVAC, lighting, access, metering and fire safety, and none of them speak the same language. Each was installed by a different integrator, each holds its data hostage in a proprietary format, and each behaves as if the others do not exist. The result is a building full of sensors that cannot tell you what is actually happening inside it.
At puniq we do not fix that with another dashboard bolted on top of the chaos. We fix it with method. Every engagement, whether it is a Data Auditor assessment of an existing building or an Infrastructure Blueprint for a new build, moves through the same four phases: discover, unify, optimize, hand over. The phases are deliberate, sequential and documented. German rigor applied to a problem most of the industry treats as someone else's mess.
Phase one: discover
We start by inventorying the building as it really is, not as the drawings claim. That means walking every plant room, opening every controller cabinet, and cataloguing each device, protocol and data point we find. BACnet, Modbus, KNX, M-Bus, proprietary RS-485 loops, the orphaned PLC nobody documented when the original contractor left. We record what speaks, what is mute, and what is quietly lying.
Discovery is unglamorous and it is the phase everyone wants to skip. We do not. At a hotel like Diar El Medina in Hammamet we found HVAC, access automation and energy metering each locked to a separate vendor, with a turbine generating power on site that no one was measuring against grid prices. You cannot optimize what you have not mapped. So we map first, exhaustively, before we touch a single setpoint.
You cannot optimize what you have not mapped. So we map first, exhaustively, before we touch a single setpoint.
Phase two: unify
With the inventory complete, we build the layer that makes the building readable. puniq normalizes every system into one vendor-neutral data model, on premises, with open protocols doing the translation. The proprietary loops stay where they are. We do not rip and replace. We put a common language over the top so that a temperature reading from one vendor and a meter pulse from another finally sit in the same coordinate system.
- Each device is given a stable, human-readable identity, so a point means the same thing tomorrow as it does today.
- Protocols are bridged through open standards, never through a black box only we can open.
- The data stays in the building, auditable and yours, with no dependency on a cloud you cannot leave.
This is the Hardware Shield principle in practice: no new hardware on your balance sheet, software margins and low regulatory friction. Unify is where a fragmented building stops being five buildings pretending to be one.
Phase three: optimize
Only once the building is readable do we layer on intelligence. Our AI Optimization service benchmarks performance, forecasts demand and flags anomalies before they become failures. It is advisory by design and human in the loop. The system recommends; your operators decide. That is not a limitation, it is a deliberate boundary that keeps the optimization layer outside BSI C5 and NIS2 audit scope, so adopting it does not drag your building into a compliance project.
Optimization is also where the regulatory tailwind pays off. GEG §71a already mandates automation and monitoring for larger buildings, and the EU Taxonomy and CSRD turn energy reporting into a legal obligation rather than a nice-to-have. A unified, readable building produces that evidence almost as a by-product. The same data that trims 30 to 40 percent of energy waste is the data your sustainability report needs.
Phase four: hand over
Here is where puniq parts ways with the rest of the market. Legacy integrators leave you with a working system and a dependency. PropTech SaaS leaves you with a subscription and a login. We leave you with the Documented Data Map.
The Data Map is the full, written record of your building's intelligence: every system, every point, every protocol, every translation rule, drawn into one navigable document that any competent engineer can read without us in the room. It is the deliverable that turns a project into an asset. It is also the answer to the question every facilities director should ask before signing anything: what happens when the vendor walks away?