Building systems

Turn Building System Data Into Operational Action

Your building management system already knows something is wrong. The gap is between that knowledge and an accountable, recorded response.

Request a Demo See Live Operations

The business problem

The BMS raises alarms into a room, not a workflow

Building system alarms are displayed on a console in a control room. They are acknowledged verbally, cleared without a record, and produce a work order only if someone chooses to raise one manually. The BMS holds the technical truth while the service record holds something different.

Alarms acknowledged without an attributable recordManual re-entry required to create workPoint names that mean nothing to a work-order systemTechnical and service records that do not reconcile

The IntelliGrid approach

Point mapping, then automation

Building system points are mapped to assets and locations in the IntelliGrid register, so an incoming event arrives with meaning. Severity classification, correlation and rule-based conversion then produce assigned work automatically, with the originating event retained as evidence.

Point-to-asset mapping established during deploymentSeverity classification and event correlationRule-based conversion into assigned work ordersOriginating event retained on the work order

Capabilities

Integration scope

Connectivity is established per site against the systems actually installed. Protocol and gateway support is confirmed during technical discovery rather than assumed.

BMS

Building management system alarms, status and setpoint data.

CCMS

Central control and monitoring system events across plant.

SCADA

Supervisory control data where industrial systems are present.

Gateway integration

Protocol gateways used where direct interfaces are unavailable.

Energy meters

Consumption and demand data for operational and ESG use.

Point mapping

System points associated with assets, systems and locations.

Event normalisation

Different alarm vocabularies reduced to one classification.

Read-oriented integration

Monitoring and workflow generation, with any control scope defined explicitly.

Workflow

BMS event to closure

STEP 1

BMS

Building system detects an out-of-range condition.

STEP 2

Event

Alarm and associated telemetry passed to IntelliGrid.

STEP 3

IntelliGrid

Event normalised, deduplicated and classified.

STEP 4

Asset

Matched to the asset record with history and criticality.

STEP 5

Priority

Severity and criticality determine priority and SLA.

STEP 6

Work Order

Assigned, executed, verified and closed.

Business benefits

Building system knowledge converted into accountable work One classification across systems from different vendors Evidence retained from detection through to closure Existing building systems retained rather than replaced Technical and service records that reconcile

Connects with

BMS CCMS SCADA Protocol gateways IoT gateways Energy meters APIs & webhooks

See integration architecture →

Frequently asked

Can IntelliGrid connect to our existing BMS?

In most cases yes, and the platform is designed to sit above building systems rather than replace them. The available interface — vendor API, gateway or protocol bridge — is established during technical discovery, and point-to-asset mapping is part of deployment.

Does IntelliGrid control building plant?

The standard deployment is monitoring and workflow generation. Any control scope is defined explicitly with the client and the building system integrator, and is not assumed.