By Yogesh SagaleA building starts to feel finished when the lights come on. It starts to work properly when the guard can retrieve a gate recording, a visitor can enter through the correct lane, a meeting room stays connected and a maintenance engineer can find the right cable without opening three ceilings.

That is the practical job of ELV planning. CCTV, networking, access control, communication and automation depend on routes, equipment locations, reliable power and clear operating rules. A camera count alone does not describe a complete project.

This ELV system guide explains how residential societies and commercial buildings can plan these systems together, define the interfaces between contractors and accept a finished installation with meaningful test evidence.

What ELV means—and how to define the project scope

ELV stands for Extra Low Voltage. In building projects, the term is commonly used for security, communication, networking, detection and control packages. The commercial scope is broader than a voltage label: a network rack, barrier motor or power supply may also require mains electrical work. Record those power requirements separately so responsibility is clear.

Begin with a system schedule. Identify the users, field devices, controllers, cable types, power sources, interfaces and acceptance tests. Two quotations both labelled “complete ELV work” can include very different equipment and deliverables.

Start with building operations before selecting equipment

Walk through a normal day and a difficult day. On a normal day, residents enter, visitors arrive, deliveries wait, staff use meeting rooms and security monitors the property. On a difficult day, power fails, a reader stops responding, an incident must be investigated or an alarm requires an approved response.

Each scenario produces a design requirement. A society with two gates may need central monitoring and remote equipment cabinets. An office with confidential meeting rooms needs restricted access and reliable WiFi capacity. A warehouse with long distances may require fibre links and local PoE switches.

• Mark entrances, restricted rooms, vehicle lanes, common areas and maintenance access on current drawings.
• Agree which events require a recording, notification, access denial or operator action.
• Decide who owns each system: security, facilities, IT or an appointed service team.
• Define what must remain available during a power or internet outage.
• Record growth expectations before conduits, rack sizes and switch counts are finalised.

ELV systems for residential societies

The society gate is a useful starting point because several systems meet there. Separate the camera view that records the overall lane from the view intended to identify a person or number plate. A wide overview camera does not automatically provide identification detail.

Plan the boom barrier around actual vehicle movement. Consider queue space, turning vehicles, visitor verification, delivery entry and pedestrian crossing. Safety sensors and vehicle detection must suit the installed barrier and lane. Test the obstruction response using the manufacturer’s safe procedure, and provide a documented manual operating method.

In parking areas, columns, parked vehicles and changing lighting create blind spots. Check views after occupancy as well as during installation. In lobbies and lift approaches, define the monitoring purpose and authorised access to recordings. Avoid placing cameras merely because a nearby power point is convenient.

The guard room needs a usable monitor layout, recognisable camera names, accurate device time and a simple clip export process. Recording retention should be an agreed requirement supported by a storage calculation. Training a guard to retrieve footage is as important as fitting the NVR.

• Gate and perimeter: camera views, visitor communication, vehicle access and outdoor cable protection.
• Parking and basement: coverage around columns, remote cabinet locations, PA and approved safety systems.
• Lobby and clubhouse: controlled access where needed, intercom and properly isolated visitor WiFi.
• Society office: stable LAN, firewall, administrator access and configuration backups.
• Risers and terrace routes: maintainable pathways, protected penetrations and weather-resistant equipment where appropriate.

ELV systems for offices and commercial buildings

The furniture plan drives the outlet plan. Count workstations, IP phones, printers, access points, meeting-room equipment, cameras and controllers. Confirm the occupied layout before a floor box or ceiling point is fixed.

Multi-floor buildings need a clear main equipment room and suitable floor distribution locations. Choose their positions from the real cable route, equipment load and maintenance access. Fibre uplinks often suit inter-floor and remote-building connections; the fibre type and optics must match the required speed and distance.

Commercial lobbies may need turnstiles or flap barriers to manage entry. Select them using peak pedestrian flow, credential type, accessibility and the approved emergency arrangements. Attendance records and door permission rules serve different purposes; define each requirement rather than assuming a biometric reader solves both.

Meeting rooms deserve their own schedule: network points, wireless capacity, AV equipment, room booking panels and automation controls. A room tested with one laptop may perform differently when every seat is occupied.

Networking is the foundation of connected ELV systems

IP cameras, WiFi access points, phones and many controllers depend on structured cabling and switches. Design the physical network and the security policies together. Shared infrastructure can simplify maintenance, but different users and devices need controlled access.

Select Cat6 or Cat6A against the required Ethernet speed, run length, PoE load and project lifetime. Cat6A is a strong option where 10G capability and future upgrades are required. Use genuine solid-copper installation cable and compatible category-rated connectors. The link performance depends on the complete installed system.

For conventional balanced copper Ethernet cabling, plan within a 90 m permanent link and a 100 m channel including patch cords. Measure the routed path, including drops and service allowance. If distances are too long, move or add a distribution location or use a suitable fibre design rather than relying on a link light.

The fixed links should be certified to the specified limit using the correct adapters and a calibrated field tester. Fluke Testing provides traceable results when performed with a suitable certification tester; continuity testing alone does not establish category performance. See our Cat6 and Cat6A certification guide and office structured cabling guide.

Size PoE switches by both port count and total power budget. Use the connected device datasheets, including maximum operating demand and available switch power. Reserve capacity for the planned expansion. The UPS must support the active network equipment and its powered devices, rather than only the recorder.

VLANs, firewall rules and remote access

Create network zones with a clear purpose: staff, visitors, CCTV, building controllers and management. An example zone plan is shown below; VLAN numbers are illustrative and should follow the site IP plan.

VLANs organise traffic; firewall policies or suitable access controls enforce which zones may communicate. Test isolation from an actual guest client, including reachable internal services, rather than accepting an SSID name as proof.

Avoid exposing camera, NVR or controller administration directly to the public internet. Choose an approved remote-access method with individual accounts, strong authentication and limited permissions. Maintain firmware, review access and retain configuration backups. Our office firewall setup guide explains the policy planning in more detail.

CCTV design: visibility, retention and retrieval

Write the purpose of each camera view before choosing megapixels. An overview shows activity; an identification view requires suitable detail at a defined target position. Lens choice, mounting height, backlight, night lighting and motion all influence the result.

Agree retention days and recording mode. Estimate storage from camera count, average bitrate and recording duration, then allow for overhead and variation. For illustration, 16 cameras averaging 4 Mbps each generate about 691 GB per day of continuous video before overhead. Thirty days is about 20.7 TB in decimal units; available usable storage and actual encoding behaviour still need checking.

Verify live view, playback, timestamps, night performance and export. A camera that appears online while its recording schedule is disabled is an incomplete installation. Assign recognisable names such as “Gate Entry Lane” and reconcile them with the drawing and device list.

Door access, boom barriers and pedestrian barriers

A door system includes the reader, controller, lock, door hardware, power supply, exit devices and approved emergency arrangements. Confirm the required behaviour during normal access, denied access, controller failure and power loss. Lock selection and release behaviour must suit the approved door and life-safety design.

For barriers and turnstiles, establish what authorises entry: guard command, card, RFID, visitor approval or a supported ANPR workflow. Define where the permission record lives and who can change it. Compatibility must be demonstrated for the specific products and software versions.

Document interfaces in a matrix: initiating event, receiving system, required action, reset method and responsible contractor. For example, a permitted credential can request a barrier opening, but the safety controller still determines whether movement is safe. Security convenience must not bypass the equipment’s safety functions.

Fire alarm, PA and emergency voice: design the interfaces carefully

Fire detection and emergency communication need their approved system design, circuits, power arrangements and testing. An ordinary music or paging amplifier is not automatically an emergency voice system. Cable selection, monitoring, battery backup and zoning depend on the approved specification.

Coordinate the fire alarm cause-and-effect schedule with authorised designers and the relevant project approval requirements. It identifies which outputs follow each event and how they reset. Building controls, access release and emergency messages must follow this documented design.

Keep dedicated safety-system architecture clear in the drawings. Monitoring on a building network does not make the office switch or general automation controller a substitute for the required safety controls. Test permitted interfaces jointly so each contractor sees both the initiating event and the receiving action.

Complete home and office automation

Automation should reduce daily effort while keeping the building easy to operate. Start with scenes users need: meeting-room presentation mode, scheduled lighting, controlled blinds, occupancy-based operation or an authorised home-away scene.

Choose the control platform and wiring strategy before the electrical installation is finalised. Confirm load compatibility, actuator locations, local controls, network dependencies and the interfaces to HVAC or AV equipment. Integration is a defined connection with an agreed behaviour, rather than a promise that every device works with every app.

Test local/manual operation, restart after power loss and behaviour when the internet is unavailable. Record configuration ownership and backup procedures. A lighting system should remain understandable to facilities staff after the person who programmed it has left.

Cable pathways, racks, power and earthing

Coordinate ELV routes with electrical, HVAC, plumbing and fire services before ceilings close. Use an agreed pathway schedule showing tray capacity, conduit sizes, pull access, segregation requirements and fire-stopped penetrations. Separation and support details must follow the specified cable system and applicable installation requirements.

Size trays and cabinets for installed cable, bend radius, heat and future additions. Tight ties, crushed cable and sharp edges can damage performance. Keep connections accessible and outdoor joints in suitable enclosures. A drawing of the final route is useful only if it matches what was actually installed.

Provide rack elevations, cooling or ventilation, secure access and suitable maintenance clearance. Document earthing and bonding requirements for racks, metallic pathways and shielded systems. Coordinate mains supply and protection with the electrical design.

State the required backup duration and verify it under a representative load. Fire alarm batteries, door-controller supplies and the network UPS may serve different duties. Listing “UPS provided” does not explain which devices continue working or for how long.

A practical project sequence

• Survey: review the site, existing infrastructure, floor plans and operating needs.
• Design: prepare device layouts, cable routes, rack elevations, network zones and interface schedules.
• Scope freeze: agree quantities, product compatibility, responsibilities and acceptance criteria.
• Installation: coordinate first-fix routes, then pull, label, terminate and mount equipment.
• Configuration: set permissions, recording, network policies, time synchronisation and backups.
• Validation: test individual systems, interfaces and agreed failure scenarios.
• Handover: reconcile records, train operators and nominate maintenance owners.

Testing and handover: define what a pass means

Acceptance should be agreed before installation. Each test needs a device or point ID, method, expected outcome, observed result and corrective action if it fails. Retest corrected defects and record the final status.

Give the owner as-built drawings, asset models and serial numbers, rack elevations, cable IDs, device IPs, warranties and service contacts. Transfer credentials securely to authorised people. Train the guard, facilities operator and IT administrator on their own tasks; a single general demonstration rarely covers all three.

Common mistakes that become maintenance problems

• Comparing only device quantities while ignoring pathways, power, storage and tests.
• Placing cameras and APs where cables happen to end rather than where coverage is required.
• Using one unrestricted network for staff, guests, cameras and management.
• Leaving interface responsibility between two contractors undefined.
• Backing up the NVR but leaving its PoE switches without backup.
• Closing ceilings before labels, route checks and agreed inspections are complete.
• Accepting camera live view or network link lights as the entire handover test.
• Keeping configurations and passwords only with the installer.
• Buying incompatible components without a demonstrated integration workflow.

How to compare ELV quotations

Ask each bidder to price the same device schedule and state every inclusion: cable type and length basis, pathways, termination, racks, electrical supplies, UPS scope, licences, storage, integration, testing and documentation. Record exclusions explicitly.

Separate optional expansion from the essential operating scope. Spare fibre, tray space and rack capacity can be economical during construction, but the amount should follow the owner’s growth plan. A complete quotation makes future costs and responsibilities visible.

APYS Projects: ELV, networking and electrical coordination

APYS Projects handles ELV, networking and electrical works for homes, offices, societies, companies and commercial buildings. Our scope includes structured cabling, WiFi, Fluke Testing, firewall setup, CCTV, access control, fire alarm, PA systems, boom barriers, turnstiles, flap barriers and complete home and office automation.

Our team can coordinate the cable pathways, electrical provisions, equipment installation, configuration, testing and handover around the actual site requirements. Share the drawings, current infrastructure and operating needs so the proposal can describe a complete working system.

If there is wire or cable, APYS Projects can handle the complete solution.

Need an ELV layout for a society or commercial building? Contact APYS Projects with your site plan and scope. Enquiries: Purchase@apysprojects.com · +91 9921490342. Office: Wagholi, Pune – 412207, Maharashtra. Serving clients across India.

Technical references

Reference guidance: Fluke Networks: cable testing and link limits; Axis: surveillance network hardening; BIS: National Building Code. Final designs and acceptance tests should follow the project specification, current applicable requirements and the selected manufacturers’ instructions.