Who this is for
If operators have learned to ignore the BMS dashboard, the alarms are the problem, not the operators.
You probably need this if…
- Energy costs keep rising and nobody can explain exactly why.
- HVAC and other systems run on separate, disconnected controls.
- Operators have stopped trusting alarms because of constant false alerts.
- You're building or retrofitting and want integrated controls designed in.
- There's no historical trend data to support energy or maintenance decisions.
- Staff still do manual rounds to check equipment status.
Where it applies
Probably not the right fit when…
- A small office where the landlord already manages HVAC and building systems.
- A single AC unit or small plant with no integration or monitoring need.
Technical overview
A building management system is only valuable if operators trust its alarms. We design BMS and IBMS points lists around what actually needs monitoring, integrate HVAC, power and life-safety systems, and avoid the alarm fatigue that makes everyone ignore the dashboard.
Technologies we work with
Reference architecture
Design principles
- Keep essential control sequences and local safeties in field controllers rather than making basic building operation dependent on a supervisory server.
- Use consistent point naming, engineering units, alarm priorities and trend intervals across integrated building systems.
- Segment building automation networks from enterprise IT and restrict remote access through controlled, monitored gateways.
- Keep regulated life-safety functions within their approved systems; BMS integration must not replace required autonomous protection.
Specification baseline
| Aspect | Specification | Why it matters |
|---|---|---|
| Control protocols | Select BACnet/IP, BACnet MS/TP, Modbus TCP, Modbus RTU or supported native interfaces according to equipment capability | Protocol compatibility, object models and writable points must be confirmed per device. |
| Field autonomy | Retain essential sequences, safe operating states and communications-loss behaviour in local controllers | Local autonomy reduces dependence on central services. |
| Interoperability | Produce a point list and protocol mapping with units, scaling, alarms, access rights and command priorities | A common protocol does not automatically guarantee consistent point semantics. |
| Energy monitoring | Trend key plant states and energy meters at intervals suited to control and reporting objectives | Useful trends help distinguish operational waste from normal load variation. |
| Security | Use OT segmentation, controlled engineering access, credential management and configuration backups | Building systems can affect physical operations and require disciplined change control. |
| Commissioning | Test sensor values, command responses, interlocks, sequences, alarms and communications-loss behaviour | Point-to-point and functional tests validate actual system behaviour. |
Key design decisions
Control deployment
Local autonomy, equipment-specific sequences and resilience during supervisory outages are priorities.
Central monitoring and optimisation are priorities while essential control remains local.
Integration protocol
Building automation interoperability and structured building-control objects are required.
Meters, drives or plant equipment expose supported register-based data and control interfaces.
Sizing & calculations
Controller I/O count = required physical inputs and outputs plus engineered spare capacity, subject to signal type and expansion requirements.
A plant with 24 inputs and 16 outputs requires 40 points; a 20% planning allowance gives 48 points before selecting I/O modules.
Trend records per day = point count multiplied by samples per point per day; storage also depends on record size and retention.
200 points logged every 5 minutes produce 57,600 records per day before metadata, indexing and database overhead.
Assess controller and network capacity from actual point counts, polling rates, device limits and alarm traffic.
500 points polled every 10 seconds represent an average of 50 point reads per second before protocol overhead and other traffic.
Standards, protocols & references
Handover documentation
- BMS architecture and network diagrams
- Point list and controller I/O schedules
- Control sequences and cause-and-effect documentation
- Protocol mapping and integration register
- Functional performance and alarm test reports
- Operator training and configuration backups
What you get
- One operator view across HVAC, power and life-safety
- Alarm thresholds tuned so operators actually act on them
- Energy and utilisation data you can report on
What we deliver
Monitoring & control
- DDC controllers and field devices
- HVAC, lighting and power monitoring
- Sprinkler and utility monitoring
Alarms & escalation
- Public address and general alarm
- Threshold tuning to reduce false alerts
- Escalation and notification workflows
Integration
- Electrical cabling and conducting
- Interface with fire alarm and access control
- Energy and utilisation reporting
