ELV / Life-Safety Building Map.
Interactive building cross-section. Toggle CCTV, access control, addressable fire alarm, public address, IP-PBX, server room and BMS — see device locations, cabling and where each system terminates.
- Layers
- 7
- View
- Cross-section
- Type
- Interactive
- Voltage
- < 50V
— Building map · ELV intelligence board
Seven systems. One building.
Pick a system. The cross-section lights up its devices and cabling, drawing the head-end relationships in one glance.
Building systems index
- IP Surveillance · CCTV. Edge cameras across perimeter, lobby, corridors and lifts. NVR in the server room. Retention sized to 30–90 days. Recording continues on UPS during outages.
- Access Control. Card / fingerprint readers on every restricted door. Magnetic locks fail-safe on fire alarm. Controllers daisy-chained to the access server in the server room.
- Addressable Fire Alarm. Detector loop addresses every device individually. Cause-and-effect logic shuts dampers, releases mag-locks, homes lifts to ground. Panel in BMS / FCC room.
- Public Address · PAVA. EN 54-16 voice-evacuation backbone. Zoned paging by floor / area. Fire-alarm event overrides routine paging instantly. Amplifier rack in server room.
- IP-PBX · Voice. DID numbering, voicemail-to-mail, mobile twinning, hunt groups. Survivable branch path keeps voice live when the WAN drops.
- Server / MDF Room. Climate-controlled enclosure for NVR, IP-PBX, AC server, switches and routers. UPS-backed; precision cooling; addressable detection inside the room.
- Building Management System. Supervisory control over HVAC, lighting and sub-metering. Coordinated trips on fire-alarm cause-and-effect. Head-end in the FCC / BMS room.
· Engineering advisory · ELV / Life-Safety Map
What the cross-section tells the architect and the owner.
The toggles reveal where seven systems live in the building, but the four notes below frame what coordinating them as one stack means for conduit count, civil scope, head-end space and operations after handover.
Deployment observations
- Coordinating CCTV, access control, fire alarm, PA, IP-PBX, structured cabling and BMS as one stack cuts civil scope (conduit runs, cable trays, head-end rack space) by 18-22 percent versus separate-vendor deployments — measured across three multi-block builds in the studio's portfolio.
- Fire-alarm cable must be segregated from data cable per IS 14665 / IEC 60332 — physical separation in the conduit, or a fire-rated cable jacket. The cross-section preview is a useful coordination surface, but the segregation is non-negotiable at installation.
- BMS integration with the other six systems is increasingly the default — fire-alarm cause-and-effect signals trigger AHU shutdown, access-control events open BMS audit trails, CCTV events bookmark BMS log entries. Specify the integration API at design freeze, not at commissioning.
Operational notes
- One ELV head-end rack with all seven systems requires one operator workflow and one configuration baseline — versus seven separate vendor consoles with seven separate operations cadences. The reduction in operator load is the highest-impact decision for facility managers.
- Patch-panel labelling against the architect's floor plan (room number + system + cable ID) is the discipline that pays back across the building's life. The first ELV move-around after handover reveals whether the labelling discipline held.
Lifecycle implications
- Structured cabling is a 20-year asset; the systems running on it (CCTV NVRs, fire panels, BMS controllers) are 8-12 year refresh cycles. Pull Cat6A to every device location at first install — the cable plant outlives two generations of head-end equipment, and rip-out cost is the largest avoidable scope creep in ELV.
- Spare conduit capacity at first install is the single best protection against future scope creep. Specify 30-40 percent spare conduit fill at architectural drawings; the marginal civil cost is trivial compared to a re-pull years later.
· Why it matters
Most owners learn that ELV exists when the building does not get its occupancy certificate. Toggling each system on the cross-section makes the picture concrete — a fire-alarm loop wraps every floor, CCTV tails the perimeter and lobbies, access-control covers every locked door, public-address zones the building, and the BMS pulls all of it into one head-end. Together they share the same conduits and the same rack — but only if someone plans them together.
· Frequently asked
ELV systems —
what people ask first.
What counts as ELV?
Extra-low-voltage systems — anything running below 50 V. The seven canonical systems are CCTV, access control, addressable fire alarm, public address, IP-PBX, structured cabling and BMS. Some practitioners include intrusion alarm and intercom; we cover those under access control and PA respectively.
Why design ELV as one stack?
Because they share infrastructure — conduits, racks, cable trays, server rooms and power. A coordinated ELV design saves around 20 percent on civil works and avoids the classic problem of running fire-alarm cable next to data cable in the same conduit, which fails the IS code.
Do you handle each system in-house?
Yes — CCTV, access, fire alarm, PA, IP-PBX, structured cabling and BMS are all delivered by the same studio. The single-handle commercial model is the reason the integration actually works.
What about retrofit?
We start with a building survey, then layer the missing systems into existing tray runs where possible. Fire alarm and access control are the most common retrofits; CCTV and BMS retrofit cleanly when there is a coherent network backbone.
How does this relate to the cinema, automation or BMS scope?
ELV is the shared chassis. Cinema, automation and BMS sit on top of it — they all need the same network, the same head-end and the same cable plant. We design ELV first because everything else hangs from it.
· Begin
Need an ELV stack
that actually integrates?
Send the building drawings, the occupancy and the systems already in place. We will write back with an integrated scope within two working days.