Many buildings.
No way to compare them.

01Facility management software, CMMS and BMS: who owns what after handover

Facility management software runs the business of a building: contracts, assets, tenants and space. CMMS software (a computerized maintenance management system) runs the work: tickets, schedules and spare parts. The BMS (building management system) runs the plant: chillers, air handlers, lighting and access, through DDC, the controllers in the plant room.

After handover you inherit all three, rarely the data under them. The BMS keeps trends in a proprietary format, the CMMS knows only what someone typed in, the FM software sees invoices. puniq adds no fourth tool. It builds the readable layer under all three, so a CMMS ticket can point at the controller behind it. Start with how to read a BMS, see how one site's building management system gets unified, and check that any tool you compare:

• Takes a feed on open protocols, not only manual entry
• Exports every work order and reading at contract end
• Shows the controller behind a fault, not only the complaint

02Multi-site energy management and energy benchmarking across a portfolio

Multi-site energy management starts with a boring problem: the sites do not measure the same thing. One reports monthly kWh from the utility bill, another has sub-meters per floor, a third only trends the chiller plant. Energy benchmarking software cannot rank what it cannot compare.

The fix is upstream of the software. When every site runs the same unified model, every point named once, time-aligned and traceable to its controller, a benchmark means something. AI Optimization, the advisory cloud layer, then scores every asset, floor and system against its own history and against comparable buildings in the portfolio, and forecasts load and peak demand days ahead. Try the energy use intensity benchmark with your own numbers, and read the KPIs every operator should track before choosing what to compare.

• Energy use intensity per site, by building type
• Chiller plant efficiency, site against site
• Peak demand and the days it will hit
• Anomalies ranked and explained, not an alarm count

03Hospitality: hotel energy management, HVAC control and guest room energy

A hotel energy management system has to work around guests. Cooling runs for every room that is sold, whether or not the guest is in it, and the hotel HVAC control system rarely knows the difference. The front desk system, the room controls and the chiller plant belong to different vendors. Guest room energy management usually means a key card switch and nothing else.

Hospitality energy efficiency improves when the room controls, the access system and the chiller plant share one model. Setpoints, access events, chiller load and metering land in one on-premises layer, and the AI layer flags the floor cooling empty rooms or the air handler drifting from its baseline. Your engineer decides. Hotel Diar El Medina in Hammamet is our running example: three systems unified in a hotel that makes its own power, 25% indicative energy waste targeted, still in validation. For the plant side, see HVAC control across every chiller and vendor.

04Retail: supermarket energy management across stores

Supermarket energy management is a portfolio problem by definition. A chain runs many near-identical stores, so one store's kWh per square meter is a direct test of another's. Refrigeration and cooling dominate the bill, run around the clock, and a compressor that has slowly drifted looks normal until the quarterly bill arrives.

Because the stores are alike, benchmarking works unusually well. Once each store's controllers, meters and refrigeration monitoring are read into the same model, the AI layer ranks stores against each other and flags the outliers. Your maintenance planner gets a reason to visit before stock is at risk. No store chain is on our case list yet; the method is the one running in the hotel above. Read how to unify chillers, lighting and metering from different vendors, and see how one AI layer over every system stays advisory.

05From buildings to smart cities: one readable layer at district scale

Smart cities are built one readable building at a time. A district operator in Riyadh or the wider Gulf inherits the hotel group's problem, multiplied. Every developer handed over a different BMS, a different metering standard and a different naming scheme. The district dashboard becomes a patchwork of exports.

The answer at district scale is not a bigger dashboard. It is the same open-protocol, on-premises layer at every building, with one naming and topology standard, so the district can be benchmarked the way a portfolio is. For new phases, that standard goes into the tender before the controls contractor is chosen, the way residential compounds are designed open from day one. For the bigger picture, read where smart buildings in Saudi Arabia are heading.