ELV systems cover the low-voltage services that shape how a building is used, secured and operated, yet they are often procured late and coordinated loosely. Many of the problems we are asked to resolve on site began with design decisions that were never made early enough in the programme.
What ELV covers in practice
Extra-low-voltage systems are the building services that operate below the main power distribution and usually depend on a network. In a typical project the term covers CCTV, access control, intercom, public address, intrusion detection, structured cabling, master clock systems and the interfaces to building management and audio-visual equipment. The exact list depends on the building type and on the design team’s definitions, which is why the scope should be written down.
The label matters because it affects procurement. When ELV is treated as a single package, one contractor can be responsible for coordination across systems; when it is split across several packages, the interfaces between them need to be written down. Most site disputes we see concern an interface that two parties each assumed the other would provide.
- CCTV and video management
- Access control, intercom and visitor management
- Public address and voice alarm interfaces
- Intrusion detection and perimeter protection
- Structured cabling and network infrastructure
- Building management and control interfaces
- AV, displays and specialist systems where specified
Structured cabling is the foundation
Structured cabling is the physical layer every other ELV system relies on, and it is the most expensive element to change later. Design should settle cable categories, outlet locations, containment routes, cabinet sizes and the separation of security and building networks before first fix. A cabling design drawn after the containment is installed will always be a compromise.
Test results matter as much as installation. Copper links should be certified for the category specified, fibre should be tested at the correct wavelength, and the results should be handed over as part of the documentation package. Without them, a fault years later becomes a debate about who installed what rather than a straightforward repair.
Cabling design should also allow for change. Spare capacity at cabinets, spare fibre cores between buildings and spare containment capacity in risers are inexpensive at construction stage and expensive to add later. A building may add cameras, access-controlled doors or wireless access points long before it changes its electrical distribution.
Integration and the interfaces that fail
Integration is where ELV projects are most often underestimated. A door that must release on a fire alarm, a camera that must record on an access event, or a lift lobby that must restrict access after hours all depend on an interface between systems supplied by different parties. Each interface needs a defined protocol, a responsible owner and a test that proves it works.
Native integration through a common platform is not always available across brands, and where it is claimed, it should be demonstrated rather than accepted from a datasheet. A simple rule is that any interface which matters operationally should be tested with both systems live, before the building is handed over. In Dubai, security-related ELV work also has to reflect SIRA requirements, and fire interfaces are reviewed by Civil Defence, so the approval position belongs in the interface matrix rather than in a handover meeting.
Where systems are supplied by different vendors, a written interface matrix is worth more than a coordination meeting. It lists each connection, the protocol, the party responsible for configuration and the test that will demonstrate it. The matrix can be reviewed at design stage and used again at commissioning, which is precisely when memory of the original agreement matters least.
The practical test of an ELV package is not the device list. It is the number of interfaces that were never assigned to anyone.
Design coordination and responsibility gaps
ELV design depends on information other disciplines hold: room layouts from the architect, power from the electrical engineer, heat load from the mechanical team, and network topology from IT. Where the ELV package is developed separately from those drawings, the coordination usually happens on site, at the point where changes are slowest and most expensive.
Clarity of responsibility matters as much as technical coordination. On a typical project the consultant specifies, the main contractor procures, the ELV subcontractor installs and the IT team controls the network. Each boundary needs a named owner for design, installation, configuration and testing, and that ownership should survive into handover rather than ending at practical completion.
Design reviews should include the ELV package explicitly rather than treating it as a specialist add-on. Riser space, cabinet locations, equipment room cooling and power, containment routing and maintenance access are all decided by other disciplines, and each one constrains what the ELV design can achieve. Once those decisions are fixed, the specialist has very little room to improve them.
Procurement and handover
ELV equipment is often procured on price and specification compliance alone, with less attention paid to local support, spare-part availability and firmware history. For systems that will run for a decade, the ability to obtain a replacement camera, controller or card reader in the UAE matters more than a marginal difference in unit cost.
Handover should include as-built drawings, IP schedules, credentials, configuration backups, licences, warranties and test records. Passwords and administrative accounts should be transferred formally, not left with the installer. A building that cannot administer its own systems is dependent on one contractor by default, and that dependency becomes expensive the first time a change is needed.
A staging plan helps on occupied sites. Systems can be migrated floor by floor or building by building, with temporary interfaces where continuity matters. The plan should identify what runs in parallel, what must be cut over, and who signs off each stage before the next begins. On live properties the sequence, not the technology, is usually what determines whether the work succeeds.
Discuss a similar requirement