· System map · early-stage reference
Staging · not indexedBuilding Technology & ELV Systems Map
A conceptual map of how building-technology layers relate — power, network, ELV, AV, automation, life-safety and monitoring — so coordination happens before procurement.
TechnoGuru engineering team · Systems-integration practice, Guwahati|Reviewed 2026-06-10
Quick answer
Modern buildings run several technology layers that depend on each other: power and backup, the network backbone, the ELV and security layer, the AV and display layer, automation and control, the fire and life-safety interface, and BMS monitoring — all handed over with documentation. This map shows how those layers relate so the coordination decisions get made before procurement, when they are cheapest to change.
This is a conceptual relationship map, not a site-specific drawing. Final design depends on drawings, site conditions, equipment selection, applicable codes and commissioning.
System map · early-stage reference
Building-technology layers on a shared coordination spine
What the diagram shows
A conceptual spine diagram. A central coordination spine runs through the building-technology layers in dependency order, stacked from the foundation up: power and backup at the base, then the network backbone, the ELV and security layer, the AV and display layer, the automation and control layer, the fire and life-safety interface, and the BMS and monitoring relationship at the top — with an AMC, documentation and commissioning rail alongside. Each layer rests on the ones below it; nothing in the diagram is a real building's layout, quantities, topology or device placement.
Legend
- 01
- Power & backup — Conditioned power, UPS and battery backup where the brief needs it.
- 02
- Network backbone — Structured network carrying data, IP devices and building services.
- 03
- ELV & security — Surveillance, access and intrusion disciplines — named, never placed.
- 04
- AV & display — Meeting AV, displays/projection/LED and audio, confirmed per room.
- 05
- Automation & control — Lighting, shading, HVAC set-points and scene control on top.
- 06
- Fire / life-safety — Interface awareness only — life-safety is project-specific and code-reviewed.
- 07
- BMS & monitoring — Coordinates and monitors services over the building's life.
- AMC
- Docs & support — As-builts, labelling, commissioning records and the support plan.
· Typical coordination points
How the pieces relate — a coordination map, not a layout.
- 01
Power and backup support
Clean, conditioned power and the right backup approach (UPS, and battery energy storage where the brief needs it) underpin every other layer. The supported load and holdover are an engineering decision, confirmed after the equipment list is known.
- 02
Network backbone
A structured network carries data, voice, IP cameras, access control, AV-over-IP and building services. The backbone, distribution and capacity are planned early because almost everything rides on it.
- 03
ELV and security layer
Surveillance, access control, intrusion detection and related ELV systems coordinate with the network and with life-safety. This map names the disciplines only — never a real coverage plan or device placement.
- 04
AV and display layer
Meeting-room AV, displays, projection or LED, and audio/PA depend on room conditions, the network and power. Feasibility is confirmed against the actual rooms, not assumed.
- 05
Automation and control layer
Lighting, shading, HVAC set-points and scene control sit on top of the other layers. Control choices follow the systems they orchestrate, so they are scoped after the layers below are agreed.
- 06
Fire and life-safety interface awareness
Life-safety is its own discipline; here we only flag where other systems must be aware of it (for example, where notification or controlled releases are coordinated). Life-safety design is project-specific and code-reviewed.
- 07
BMS and monitoring relationship
A building management layer can monitor and coordinate services over time. What it monitors and how is scoped against the systems actually installed.
- 08
AMC and support documentation layer
Long-term support depends on clean as-built documentation, labelling and a maintenance plan — decided as part of the design, not bolted on afterwards.
- 09
Commissioning and handover documentation
Each layer is commissioned and handed over with records. Coordinating documentation early is what makes the building serviceable later.
- 10
Why coordination comes before procurement
Pathways, power budgets and the network are hardest to change once procurement starts. Agreeing the relationships early avoids rework and keeps every later choice open.
When to use this guide
- At concept or schematic stage, to agree which technology layers a building needs and how they overlap.
- When briefing an architect, consultant or owner on what 'building technology' covers beyond a single trade.
- Before procurement, to check that pathways, power and the network can carry every downstream system.
- As an early discussion reference in a coordination meeting across disciplines.
When not to use it
- As a site-specific design — it carries no quantities, placements, topology, addressing or zones.
- As a substitute for drawings, a BOQ review, a site survey or commissioning.
- To claim code compliance — applicable codes and the authority of record govern the real design.
· What to share with TechnoGuru
Bring these to the conversation.
- The building type, scope and which disciplines are in or out.
- Architectural drawings or a floor-plate concept when available.
- Any brand or platform preferences and constraints.
- Programme stage — concept, tender or construction.
- Who the coordinating consultant or authority of record is.
- Timeline, phasing and the support expectation after handover.
What this guide is — and isn't
- Conceptual relationship map only — it shows disciplines and coordination points, never a real building's device placement, coverage, topology, addressing or restricted areas.
- Final design depends on drawings, site conditions, equipment selection, applicable codes and commissioning.
- No quantities, pricing or vendor-relationship claims are expressed or implied.
Tools that turn this into numbers
Full toolkit →- ELV / Life-Safety Building MapInteractive cross-section of a building. Toggle between CCTV, access control, fire, PA, IP-PBX, server room and BMS — see device locations and where each cabling backbone lands.
- Structured Cabling EstimatorEstimate total structured-cabling length, patch panel count and IDF closet count against floor area and drop count. Panduit, CommScope, Belden, Legrand, Corning, Furukawa, R&M. Cat6, Cat6A, Cat7, Cat8 copper plus OM3, OM4, OS2 fibre. TIA-568 compliant.
- CCTV Storage Retention CalculatorMulti-brand, codec-aware CCTV storage retention sizing across Hikvision, Dahua, Axis, Hanwha, Bosch, Honeywell, CP Plus and Prama. Computes storage TB, HDD count plan, recorded bandwidth and an NVR/VMS class recommendation against camera count. Pairs with the CCTV Coverage Calculator.
- Network & PoE CalculatorSized to year-three load — switches, Wi-Fi 7 access points, PoE budget (watts), Cat6A run count, port/AP sizing. Cisco / HPE Aruba / Juniper-class enterprise gear.
· Common questions
Before you ask us.
Can this map replace a final system design?
No. It is a planning reference that shows how the layers relate. A final design depends on drawings, site conditions, the equipment selected, applicable codes and commissioning.
What does ELV cover in a building?
ELV (extra-low-voltage) is the family of low-voltage systems — structured cabling and networking, surveillance, access control, intrusion, AV and PA, and similar — that let a building's services work together. The precise scope is project-specific.
Why coordinate before procurement?
Pathways, power budgets and the network backbone are the hardest things to change once procurement starts. Agreeing the relationships early keeps the later choices open and avoids rework.
How should an architect or consultant use this?
As an early discussion reference in a coordination meeting — to agree which layers the building needs and where they overlap, before the drawings and BOQ are fixed.
What should be shared before a written estimate?
Building type and scope, drawings or a floor-plate concept when available, any platform preferences, the programme stage, and the support expectation after handover. A written estimate follows a technical review.
Pricing · written estimate after review
Need a price for this scope?
Share your drawings, BOQ or project brief on WhatsApp/call +91 88110 34444 or email info@technoguru.in for a written estimate after review. Pricing depends on drawings, site conditions, system scope, brand selection, cabling stage, integration depth, commissioning, logistics, GST, approvals and support expectations — so we prepare it per project after a technical review rather than publishing standard rates.
Back to all visual guides