Factory CCTV Expansion Planning: Cameras, Access Control and the Fire Alarm

Updated 6 Oct 2026 · 10 min read · by Secured Engineers Editorial Team

An operator watches two screens showing an abstract floor plan with camera and door-access icons in a security control room, a colleague standing beside her and a card reader by the glass door. — Concept illustration made for this page with an AI image tool — not a photograph of a Secured Engineers project.

Expansions are where ELV systems fragment. The original CCTV came with the building, access control was added a few years later, and now a new bay, gate or warehouse needs cameras and doors of its own. Unless someone plans the addition as part of one system, the site ends up with a second recorder, another management application and a door controller that does not know the fire alarm exists — and a guard expected to join them up during an incident.

This checklist is for facility and IT heads planning CCTV and access control for an expansion or renovation. It covers four decisions to settle before buying: what each camera is for and where privacy limits it, network, storage and power capacity, who owns the fire-alarm interface, and how the work is tested and handed over.

Camera purpose and privacy boundaries

Write down what each new camera is for before choosing it. A camera meant to detect someone crossing a fence line needs a very different image from one meant to identify a face at a gate or read a number plate at a barrier. The purpose sets the image detail needed at the target, which sets the lens, resolution, mounting position and lighting — and, through them, the bitrate and the storage.

For each new camera, record	Why it matters
Purpose: detect, observe, recognise or identify — and what (people, vehicles, number plates, a process)	Sets the image detail needed at the target
Area covered, distance to the target, day and night lighting	Decides the lens, the resolution and whether infrared or added lighting is needed
Recording mode: continuous, scheduled or motion-triggered	Can change storage substantially
Retention period, set by a written policy	Drives storage size; footage kept longer than needed adds cost and risk
Privacy limits: no views into toilets, changing or rest areas; masking where a view crosses a neighbour’s property or a public road	Keeps recording to what the purpose needs
Signage at monitored areas	Tells people they are being recorded
Who may view live, view recorded and export, and how exports are logged	Footage and access logs identify people; access should be limited and traceable

Digital footage and access-control logs of identifiable people can be personal data. The Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 (MeitY, G.S.R. 846(E), 13 November 2025) are coming into force in phases; under the Rules’ commencement clause, the rules on notice, security safeguards, breach intimation and retention apply eighteen months after publication. How they apply to your cameras, signage and retention is a question for your legal adviser — a written purpose and retention period for each camera makes that conversation easier.

There is also a procurement check. CCTV cameras and recorders are under BIS compulsory registration, and BIS’s implementation guidelines of 22 October 2024 say that after 9 April 2025 no licence is granted for CCTV camera models that do not comply with MeitY’s Essential Requirement(s) for Security of CCTV, and non-compliant models are removed from existing licences. Ask the supplier for each model’s registration and its compliance with those requirements.

Network, storage and PoE capacity

An expansion adds load to recorders, switches and power supplies sized for the original site. Check each before buying cameras.

Bitrate drives everything. Bandwidth and storage depend on the camera model, scene detail, light and motion, resolution, frame rate, codec and compression, the recording mode and the retention period. Axis’s Site Designer documentation states that the power, bandwidth and storage values its tool reports are estimates only; treat any calculator the same way and confirm with measured bitrates from the cameras you will install.
Storage arithmetic. Storage = average bitrate × recording time × retention days. One camera averaging 4 Mbit/s and recording continuously for 30 days needs 4 ÷ 8 × 86,400 × 30 ≈ 1,296 GB, about 1.3 TB, before RAID or redundancy overhead. Halve the bitrate and storage halves; double the retention and it doubles. The CCTV storage and network planning calculator runs this for a whole camera schedule.
Recorder limits. Channel licences, incoming bandwidth and drive bays on the existing recorder or video-management server — often the reason an expansion needs a second recorder.
Switch and PoE budget. Add up each device’s PoE power from its datasheet (heaters and infrared illuminators raise it), compare with each switch’s total PoE budget and port count, and keep headroom. Copper Ethernet is limited to 100 m per run, so a new building beyond that needs a fibre link and a local switch.
Uplinks and separation. Check the uplink from new switches to the recorder, and keep security traffic on its own network or VLAN rather than the office network.
Power continuity. Recorders, core switches and access controllers belong on a UPS sized for the outage you need to ride through. A camera on a switch that died with the mains records nothing.

Fire-alarm interface responsibility

Most ELV integration is convenience. The interface with the fire alarm is not: it is part of the building’s life-safety design under the approved fire scheme, which NBC 2016 Part 4 (Fire and Life Safety) frames and the local fire authority approves as part of the building’s fire approval. When access control is extended to new doors, settle these points in writing before installation:

Which doors release on alarm. Escape-route doors that the access system locks are normally required to release on the fire-alarm signal and on loss of power; the fire scheme specifies which doors and how. Take the door list from the scheme designer, not the access-control vendor.
Who provides the interface. Typically the fire-alarm contractor provides the output (a relay or monitored module per zone or door group) and the access-control contractor wires it to the controllers and locks. Both contracts must say so, or each will assume the other — the same interface gap described in multi-contractor coordination failures.
Who programs the cause-and-effect. The panel logic — which zone releases which doors, and what else operates — belongs to the fire-alarm contractor and the scheme designer, issued as a revised cause-and-effect matrix.
What CCTV does on alarm. Cameras can bookmark footage or switch views on a fire or door-forced event. That is a convenience integration and must never sit in the life-safety path.
Who re-tests it. After handover, the door-release test belongs on the fire system’s maintenance calendar, not only the security contractor’s — an interlock nobody exercises is an assumption, as the fire system nobody tests shows.

Decision table: extend, integrate or replace

Situation found	Typical option	Check before committing
Existing recorder has spare channels, bandwidth and drive bays	Extend it	Camera compatibility (ONVIF profile or the recorder’s supported list), licences, retention after the added load
Recorder full or near the end of support	Add a recorder under the same management software, or migrate both sites to a new platform	Whether old and new cameras appear on one screen with one audit trail
Closed, single-vendor access system	Extend with the same vendor, or plan a phased replacement	Cost per door, support life, and a fire-alarm release input per door group
New building far from the existing network	Fibre link and a local switch, or a local recorder viewed centrally	Uplink capacity and the 100 m copper limit
New escape doors need access control	Fail-safe locking with fire-alarm release	The fire scheme’s door list and the revised cause-and-effect matrix
Gate needs number-plate capture	Dedicated camera and lighting at the barrier	Approach speed, angle, night lighting, and the purpose and retention record
Expansion adds a second operator room	Central management with role-based access	Who may view, export and administer, and how accounts are reviewed

Acceptance tests and operating ownership

Agree the acceptance tests in the purchase order so they are priced and witnessed rather than negotiated at handover:

Each camera’s view and image detail checked against its written purpose, by day and by night
Recording verified for every camera in the agreed mode, and retention proved by checking the oldest footage once the period has run, or by calculation from measured bitrates
Time synchronised across cameras, recorders and access controllers, so events line up in an investigation
Footage export tested, including the export log
Access control: card enrolment and deletion, door-forced and door-held alarms, and the fire-alarm release tested door by door with the fire-alarm contractor present
Power: mains removed to prove the UPS carries the recorder, switches and controllers for the agreed time

Then hand over so the owner, not the installer, controls the system: administrator credentials in the owner’s name, a device schedule with IP addresses and locations, firmware versions, configuration backups, the network diagram, the revised cause-and-effect matrix and the maintenance schedule. A system whose only administrator account belongs to the contractor is one the site does not control — the same lock-in risk as in the BMS vendor lock-in trap.

Secured Engineers designs and installs CCTV, access control and their fire-alarm interfaces as one low-voltage scope under its ELV service. For an expansion review, send the asset schedule, the existing system details and the performance you need through the quote request. Other expansion and renovation planning guides are collected in Insights.

Where the expansion adds AI video analytics, ANPR at the gate or face recognition at a turnstile, the video management system becomes the integration layer that the access-control and fire-alarm interfaces hang off. Scope it with the camera schedule, not after it, and name in the acceptance test which analytic each camera must serve.

Sources and how to verify

National Building Code of India 2016 (SP 7:2016) — Bureau of Indian Standards; Part 4 Fire and Life Safety (fire detection and alarm, means of egress).
Digital Personal Data Protection Rules, 2025 — Ministry of Electronics and Information Technology, G.S.R. 846(E), 13 November 2025; rule 1 (commencement).
Guidelines for implementation of Essential Requirement(s) for Security of CCTV — BIS Registration Department, 22 October 2024.
AXIS Site Designer manual — Axis Communications; manufacturer documentation on bandwidth, storage and PoE estimates.

Confirm locally: the door-release requirements with your fire-scheme designer and the fire authority, and your data-protection obligations with your legal adviser.

Frequently asked

What information do I need before planning a CCTV and access-control expansion?

A site plan of the expansion with the areas to cover, a written purpose for each new camera (detect, observe, recognise or identify, and what), the retention period you need, the existing recorder and software details with spare capacity, the network layout and switch models, the list of new doors with those on escape routes marked, the approved fire scheme’s door-release requirements, and who will operate the system.

Which site conditions can change the scope or budget of a CCTV expansion?

Distance from the existing network (copper Ethernet is limited to 100 m, so remote buildings need fibre), a recorder without spare channels or storage, switches without enough PoE budget, poor night lighting at gates and fences, a closed access-control system that only its vendor can extend, escape doors that need fire-alarm release wiring, and no UPS for the core equipment. Each adds hardware or design work.

What should I send an engineer for a project-specific review of an ELV expansion?

The asset schedule (existing cameras, recorders, switches, access controllers and readers, with makes and models), the expansion layout, the performance you need from each new camera and door, the retention period, the fire-alarm panel details and cause-and-effect matrix, and any problems with the current system. With these, the engineer can separate what the existing system can absorb from what has to be added.

We already own mismatched systems — can they be integrated?

Often partly. Cameras that support open standards such as ONVIF, and panels with relay or monitored outputs, integrate well; closed legacy systems may need a gateway or a phased replacement at the end of their life. Map what can talk to what before buying anything new, so the expansion does not add another island.

What is a cause-and-effect matrix?

The fire-alarm system’s documented logic: which detection zone or input triggers which outputs, such as door releases, fan and damper actions, lift homing and voice evacuation. It is designed with the fire scheme, tested at commissioning and re-tested on the maintenance calendar, and it must be revised whenever an expansion adds doors or zones.

Related services

More insights

ELV Systems

A Fire Alarm That Cries Wolf Is Worse Than No Alarm at All

After the third false evacuation, your team stops believing the panel — and someone puts the sounders on silent. False alarms are not bad luck; they are almost always a detector-selection or placement error that was baked in at design.