Skip to content
Inteched
← All products

Inteched BMS · Building management

Every building in one view, and an energy bill that finally goes down.

One estate, before and after

Monday. The bill is up again.

Fourteen buildings, and nobody can say which one.

Five controller brands.

Five logins, five naming schemes, no single view.

Saturday, 03:00. Block C is running.

Heating and air handling, for nobody.

Now every building is on one screen.

Every brand, every point, named the same way.

Out of hours, off.

Schedules fixed for the buildings that drifted.

Next March, the bill went down.

And Dan can show which building did it.

Request a demo

An illustrative estate, based on our buildings work.

What you get with Inteched BMS

  • One viewof every building

    Every controller brand and every point on one screen, named the same way.

  • Lowerenergy spend

    Out-of-hours running found and switched off, building by building.

  • Everyalarm with an owner

    Every alarm routed to a named person, with escalation if nobody acts.

  • Weeklydrift report

    Buildings that slip back into old habits flagged before the bill arrives.

Features

Open any feature for the detail.

Point collectionBACnet/IP, Modbus TCP and major vendor APIs, read-only by default.
Inteched BMS reads BACnet/IP, Modbus TCP and the main vendor interfaces, read-only by default. Point names are normalised so the same sensor means the same thing in every building.
Alarm managementRouting rules, acknowledgement, escalation rotas and SMS call-out.
Alarms are routed by building, system and priority to whoever is on the rota. Unacknowledged alarms escalate on a timer, by SMS or phone call.
Floor plansEquipment and live values shown on each floor.
Equipment and live values sit on each floor plan, so an operator can see where an alarm is and what is around it.
TrendsHistory by point, equipment and building, with comparison across sites.
History by point, equipment and building, kept for years, with side-by-side comparison across sites.
EnergyMeter data, schedules and out-of-hours analysis.
Meter data, schedules and setpoints compared across the estate. Out-of-hours running and drift are flagged with the likely saving.
Equipment historyAlarms and maintenance by asset, linked to work orders in your maintenance system.
Alarms, trends and maintenance kept against each asset, linked to work orders in your maintenance system.
BACnet and Modbus controllersMaintenance systemsEnergy metersSMS gatewaysInteched BMS

Fits the systems you have

BACnet and Modbus controllers
Read-only by default, write only where you allow it.
Maintenance systems
Work orders raised from alarms, closed back automatically.
Energy meters
Half-hourly data from meters and data loggers.
SMS gateways
Call-outs and escalation for the on-call rota.
  • Cloud, or on a server in your estate
  • A small gateway on each site network
  • Read-only connection to controllers by default
  • Single sign-on and a full audit log
Integrations directory →

Common questions

Do we have to replace our controllers?
No. Inteched BMS sits above the controllers you already have and reads from them. Nothing on site needs replacing.
Which vendors does it support?
Anything that speaks BACnet/IP or Modbus TCP, plus the main vendor interfaces. We confirm every site during scoping.
Can it change setpoints?
Only if you allow it. Connections are read-only by default, and writes are limited by role and logged.
How is the site network kept safe?
A small gateway on each site makes outbound connections only. No inbound ports are opened on the building network.
How long does it take to connect an estate?
A first group of buildings is usually live in 6 to 10 weeks. Further sites follow in days once point naming is agreed.
How is it priced?
A subscription by building or point count, with connection work priced after the scoping study.

See Inteched BMS in action

A 30-minute walkthrough with your own workflows in mind.

Request a demo