Building automation, controls and ELV/ICT systems
Domain 7: Building automation, controls and ELV/ICT systems
This domain tests integration of control and low-voltage systems with the electrical infrastructure. You must define points, sequences, protocols, network segregation and commissioning evidence.
Core rules
- Produce a points list and sequence of operation before selecting controllers; each point needs range, signal type, alarm and failure state.
- Match protocols and gateways: BACnet, Modbus, KNX and proprietary buses are not automatically interoperable.
- Separate IT, ELV, fire and control networks physically or logically; use VLANs, firewalls and access control where integration is required.
- Provide power, containment, earthing and surge protection for ELV/ICT racks and field devices.
- Design for spare capacity (typically 10–20% I/O and network ports) and clear labelling.
- Commission by point-to-point test, sequence test, trend review and as-built documentation.
Worked example
An air-handling unit needs four analogue inputs (temperature, humidity, pressure, CO₂), six digital inputs (status, alarms, filter, fan proofs), three analogue outputs (valves, damper) and five digital outputs (fan, damper, enable). Total = 4 + 6 + 3 + 5 = 18 points. Add 20% spare: 18 × 1.20 = 21.6, so specify 24 I/O. Check that the controller’s point types match, not just the total count.
Traps
- Specifying a protocol without testing interoperability.
- Omitting spare I/O and ports.
- Mixing fire and building-control networks without segregation.
- Commissioning sequences without trend or failure-mode tests.