IoT monitoring

Connect Physical Building Systems to Digital Operations

Sensing is only useful when a reading is attached to an asset, a location and a workflow. That mapping is what turns telemetry into maintenance.

Request a Demo See Anomaly Detection

The business problem

Sensors deployed, insight not delivered

IoT pilots often end with a vendor dashboard showing live graphs that nobody watches. Devices drop offline unnoticed, batteries die without replacement, readings are not tied to the asset register, and no reading has ever caused a work order to be raised.

Device dashboards separate from operationsOffline devices and dead batteries unnoticedReadings not mapped to assets or locationsNo path from a reading to assigned work

The IntelliGrid approach

Telemetry inside the operational model

Devices are registered against assets and locations, their health and connectivity monitored as part of system status, and thresholds and baselines linked to the alerting and work-order engine. A reading that matters becomes a task, not a chart.

Devices mapped to assets and locations on registrationDevice health, battery and last-communication monitoredThresholds and anomaly baselines both supportedAlerts that create work orders under your rules

Device types

What is typically deployed

Device selection depends on what the building already instruments and where the operational risk sits. Supported models are confirmed per deployment.

Temperature

Space, plant and cold-chain temperature monitoring.

Humidity

Conditions in humidity-sensitive spaces and equipment rooms.

Air quality

CO₂ and particulate monitoring against occupancy and ventilation.

Occupancy

Space utilisation and presence for demand-based servicing.

Water metering

Consumption profiling by building, riser or tenancy.

Leak detection

Early detection in plant rooms, risers and wet areas.

Power metering

Circuit and asset-level electrical consumption and quality.

Vibration

Condition monitoring on rotating equipment.

Pressure

Differential pressure across filters and pumping systems.

Motion and door state

Security and access-related events tied to operations.

Workflow

Device to decision

STEP 1

Device recorded against its asset and location.

STEP 2

Collect

Telemetry streamed through the gateway.

STEP 3

Monitor

Device health, battery and connectivity tracked.

STEP 4

Evaluate

Thresholds and baselines assessed continuously.

STEP 5

Alert

Qualifying conditions raised in the operations queue.

STEP 6

Act

Work order raised, assigned and closed.

Business benefits

Readings that are attributable to a specific asset Device failure treated as an operational issue, not an IT one Both threshold and baseline-based detection available Sensing extended where instrumentation is thin A documented path from reading to completed work