ELV Systems: Defining Scope and Building Interfaces

KEY POINTS

Define ELV by the systems and work included in your project.
Assign responsibility for power, cabling, networks and software interfaces.
Test the agreed functions and hand over records the facilities team can use.

ELV stands for extra-low voltage. In building project discussions, an “ELV package” often groups communication, security and control systems. The package name alone does not define the electrical classification or safety requirements of every device; associated equipment can also use mains power.

Describe the systems, not just the package

Start with a schedule of the functions required. A clear schedule makes quotations easier to compare and reduces uncertainty between the electrical, IT, security and facilities teams.

System	Questions to settle
CCTV	Which areas, recording arrangements and user permissions are required?
Access control	Which doors, credentials, operating states and approved emergency interfaces are included?
Data and communication cabling	Where are outlets, racks, patching and network responsibilities defined?
Building monitoring and control	Which points are monitored or controlled, and by which system?
Fire alarm	What approved design, interfaces and acceptance process apply?

ETES’s ELV service scope provides the relevant starting point for discussing the work. Equipment selection, software licensing and third-party integrations should be expressly included or excluded in the proposal.

Make the interfaces visible

For each connection, record the source, destination, signal or protocol, cable route and contractor responsible. Include the power source and any backup requirement. A physical cable connection does not by itself establish that two systems exchange the correct information.

For fire alarm interfaces, use the approved control logic and test requirements. NFPA 72 includes emergency control interfaces within its scope, but the applicable edition and local requirements must be established for the project. Do not assume every access-controlled door has the same emergency behaviour.

Agree access and information ownership

Determine who administers user accounts, network settings, recordings and configuration backups. Agree remote access and update arrangements before handover. NIST’s operational technology guidance is a useful reference where building systems interact with physical processes and operating constraints.

Access to security recordings and personal information also needs to follow the owner’s policies and applicable obligations. Keep the electrical installation scope distinct from ongoing administration unless both are specifically agreed.

Prepare acceptance and handover records

Define functional tests in terms the owner can verify: a device is correctly identified, an approved event reaches the intended destination, a cable test is recorded, or a user role has the agreed permissions.

Request labelled drawings, cable and device schedules, test results, configuration records, operating instructions and an outstanding-items list for the agreed work. A good brief also states the site location, systems involved, existing equipment, access restrictions and target schedule.