Skip to content
HAPISTECH

Capability 04

BMS and smart buildings

Building management and smart building interfaces that make plant, energy and comfort data legible to the people running the site.

Start a project briefHow we work

Problem and opportunity

The data exists; the picture usually does not

Modern buildings generate plenty of points. Facilities teams still work from alarms, spreadsheets and vendor consoles that were never designed for daily decisions or for reporting to an owner.

  • Energy performance is discussed monthly, after the fact.
  • Alarms are noisy, so real faults are missed.
  • Each subsystem has its own interface and its own login.

What Hapis delivers

Scope of delivery

Site and asset model

A consistent structure for buildings, zones, plant and points that later views depend on.

Operational interface

Readiness views for the day: what is running, what is out of range, what needs attention.

Energy and performance visibility

Consumption and trend views tied to areas and equipment, not just a single meter.

Reporting

Owner and tenant reporting produced from the same source as the operational view.

How the system works

The layers behind the interface

Each layer has a defined responsibility, so the system can be extended without rewriting what already works.

  1. 01

    Acquire

    Data from BMS, meters, controllers and gateways through supported protocols.

  2. 02

    Normalise

    Consistent naming, units and asset hierarchy across vendors.

  3. 03

    Present

    Role-appropriate views for technicians, managers and owners.

  4. 04

    Act

    Alerting, work notes and escalation, with control actions kept under existing site authority.

Integration and architecture

Where it connects

  • Read integration with existing BMS and metering infrastructure.
  • IoT gateways where legacy plant has no accessible interface.
  • Time-series storage sized for the point count and retention required.
  • Control changes stay with the appointed controls contractor unless explicitly agreed.

Use cases

Typical applications

Multi-site facilities view

One console covering several properties with comparable metrics.

Energy accountability

Tenant or department level visibility to support cost allocation.

Maintenance support

Trends and fault history that shorten diagnosis time on site.

These describe the shape of the work. Named client references are published only with written approval.

Delivery process

How a project runs

  1. 01

    Discover

    Survey existing systems, points, protocols and reporting needs.

  2. 02

    Design

    Asset model, data flow and interface structure.

  3. 03

    Build

    Interface and pipeline built against a representative subset first.

  4. 04

    Integrate

    Staged rollout across systems and sites with validation at each step.

  5. 05

    Improve

    Refine alarms, thresholds and reporting with the facilities team.

Questions

Answered directly

Do you replace our BMS?
Usually not. We add a visibility and reporting layer over what is installed, and integrate rather than rip out.
Which protocols?
We assess what is available on site, commonly BACnet, Modbus or vendor APIs via a gateway, and confirm feasibility in the survey.
Can it control equipment?
Control scope is defined explicitly with the site and the controls contractor. Default delivery is read and report.

Next

Tell us what you need to run better

Start a project brief

Live building and utility projects

Other capabilities