Skip to content
Inteched
← Solutions

Building monitoring · built on Inteched BMS

Every alarm reaches a named person, and repeat faults get noticed.

One archive store, before and after

Store B’s dehumidifier faults again.

Someone clears it at the panel. No name, no note.

Six faults in a month.

Nobody saw the pattern until mould showed on the boxes.

Now the alarm reaches Grace.

With its history: the third fault in nine days.

Store B holds at 50%.

Every alarm has a name on it. The records stay dry.

Request a demo

An illustrative archive, based on our buildings work.

What you get with building monitoring

  • Everyalarm with a name

    Every alarm goes to a person, and nobody can clear it without a note.

  • Repeatfaults caught early

    Repeat faults flagged early, so the cause is fixed before damage is done.

  • Everyalarm on record

    Who saw it, when and what they did, ready for the next review.

What’s included

Collection

  • BACnet, Modbus, vendor APIs
  • Trend storage

Alarms

  • Routing rules
  • Escalation rotas

Maintenance

  • Tasks from alarms
  • Equipment history

Reporting

  • Alarms by equipment
  • Response times

Where customers start

Alarm routing for one campus
Connect the controllers in a group of buildings, set routing and escalation rules, and give technicians alarms on their phones.
Out-of-hours running review
Collect trend data from plant across the estate and report equipment running outside occupied hours, for the energy lead to act on.

Connects to

  • Building controllers
  • Maintenance systems
  • Floor plans
  • SMS and email

Schedule a tailored demonstration.

Request a demo