Techbanq

Real estate · the intelligence layer

The building already has the data; the software layer is what is missing

A commercial building of any recent vintage runs a BMS, meters and hundreds of sensors — and their data usually ends at a workstation in the plant room. The smart-building work is software: reading what those systems already measure, joining energy to occupancy to comfort, and putting the result in front of the people who can act on it.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
COO, CTO
Decision
Add an intelligence layer over existing building systems without a hardware programme
Languages
EN · AR

Information security for software delivery

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The layer’s job

What software over a BMS has to deliver before it earns the word smart

These are the requirements we scope a smart-building layer against. Each produces something the operation can use; a layer that produces only a dashboard has stopped at the second row.

Read what exists, as it is

Connects to the BMS, meters and sensors over the protocols they already speak, without ripping out or replacing the control layer.

What the operation gets: The building’s data off the plant-room workstation and into one place.

Make the points mean something

Normalises thousands of cryptically named points into a model of the building — this sensor, on this AHU, serving this floor — because analytics over unnamed points is guesswork.

What the operation gets: A point model any future use case builds on instead of re-deciphering.

Join energy to occupancy and comfort

Puts consumption, presence and conditions on one timeline, so the question becomes “why is tower B cooling empty floors on Friday” rather than “what was last month’s bill”.

What the operation gets: Findings specific enough to act on the same week.

Turn a finding into an action

Routes an anomaly to the right place — a work order for facilities, a schedule change proposal for the operator, an alert with its context attached rather than a bare threshold breach.

What the operation gets: A loop that closes, which is the difference between monitoring and managing.

The unglamorous truth

Smart-building projects die in the point-naming spreadsheet

The pitch decks show dashboards; the project reality is integration. A building assembled over years carries a BMS from one vendor, chiller controls from another, metering added in a retrofit and sensors from whichever contractor was cheapest that quarter — each speaking its own protocol, each naming its points in its own dialect. “AHU-03-SAT” and “B2_AH3_SUPPLY_TMP” may be the same sensor or different ones, and until someone establishes which, every chart drawn over them is fiction. The decisive work of a smart-building programme is this normalisation: mapping what exists, naming it consistently, and validating that the data says what its label claims. It is unglamorous, it is most of the effort, and it is the asset every later use case inherits.

This is also why we take no position on hardware. We do not sell sensors, controllers or a BMS, and the engagement carries no incentive to find your building under-instrumented. Where the survey shows a use case genuinely needs measurement the building does not take — a metering gap, a zone with no occupancy signal — we say so and scope around it or defer it, and the hardware, if any is bought, comes from the building’s own contractors on its own terms.

The shape of it

Many building signals, one model, three kinds of outcome

The layer is a funnel, not a pipeline: heterogeneous signals converge into one contextualised model, and everything the operation consumes is drawn from that model rather than from any single system.

A surface diagram: BMS controls, energy meters, occupancy signals and comfort sensors converge into a normalised building model, which feeds energy decisions, comfort interventions and maintenance triggers.

  • BMS and plant controls

    HVAC states, setpoints, alarms over the native protocols.

  • Energy and utility meters

    Electricity, water and cooling consumption, ideally per zone or tenant.

  • Occupancy and access signals

    Presence, counters and access events that say who the building is actually serving.

  • Comfort and environment sensors

    Temperature, humidity and air quality where they are measured.

What we do

The normalised building model

One vocabulary for every point, tied to the building’s real spaces and assets, with the data validated against what its labels claim.

  • Energy decisions

    Schedules and setpoints challenged with evidence — consumption against actual occupancy, not against habit.

  • Comfort interventions

    The persistently hot meeting room found and fixed before the complaint, because the signal was joined to the space.

  • Maintenance triggers

    Equipment drifting from its normal behaviour raises a work order in the FM system while the fix is still small.

The model in the middle is the investment; the outcomes on the right are interchangeable and grow over time.

Our role

What we build above the control layer and what stays below it

  1. 01

    The survey and the honest scoping

    We start by establishing what the building actually measures and how trustworthy each signal is, so the first use cases are chosen by the data that exists rather than by the demo that impressed.

  2. 02

    The integration and the model

    We build the connections to the BMS and meters and the normalised point model over them — the layer’s foundation, and the part that outlives any individual dashboard or algorithm.

  3. 03

    Read first, write with ceremony

    The layer begins read-only. Where a use case later justifies writing back — a schedule, a setpoint — it goes through the BMS’s own controls, within limits agreed with the operator, with the control system’s protections untouched.

The control layer — the BMS, its safeties and the contractors who maintain it — stays exactly where it is and whose it is; we build the software above it that turns what it already measures into decisions the building’s operators and owners can act on.

Common questions

What buyers ask

Do we need new sensors before a smart-building layer is worthwhile?+

Usually far fewer than the hardware-led pitches suggest, and the honest answer comes from a survey rather than a catalogue. A building with a working BMS and utility metering already measures enough for the first tier of value: schedules challenged against occupancy patterns, equipment drifting from normal behaviour, consumption that does not match what the building is doing. We deliberately sell no hardware, so the survey has no thumb on the scale — where a use case genuinely needs a measurement the building does not take, we name the gap and let you fill it through your own contractors, or defer that use case until it is worth filling.

Our towers run different BMS vendors. Does that break the software layer?+

It is the situation the layer exists for. Multi-vendor estates are the norm, not the exception — buildings are delivered years apart by different contractors, and consolidating them onto one BMS is a capital project few portfolios can justify. The software layer connects to each system over the protocol it speaks, and the normalised model above is where the estate becomes one thing: the same point vocabulary, the same spaces, the same analytics across towers regardless of whose controller sits in each plant room. The practical caveat is age — a very old controls installation with no readable interface may need its integration path scoped specially, which the initial survey establishes per building before anything is promised.

Who should own the building data the layer collects — us, tenants or the vendor?+

The building’s owner or operator, contractually and technically, and a custom layer makes that clean in a way platform subscriptions often do not. The data lands in a store you control, under your cloud accounts, exportable in open formats — so changing analytics suppliers later means changing the software above the data, not ransoming the history out of someone’s platform. Tenant-facing questions sit inside that ownership: what a tenant sees of their own zone’s consumption and comfort is a commercial decision the system enforces per lease, and per-tenant metering data is theirs to see and yours to steward. What we would not accept on your behalf is an arrangement where years of your building’s operating history are only rentable back from a vendor.

Map it to your portfolio

A systems survey of one building — what the BMS, meters and sensors already measure, what state the data is in, and which two use cases that data can honestly support first.

Start the conversation