Security system design is usually judged on the finished installation, but most of its value is settled much earlier, in the risk assessment, the coverage plan and the access zoning. Getting those decisions right reduces rework, removes coverage gaps and gives the operator a system that is straightforward to run.
Begin with a risk assessment
A risk assessment should describe what the building is protecting, who uses it and what the realistic threats are. For a residential tower, a warehouse and a cultural venue the answers differ completely, and the security design should follow. Asset value, occupancy patterns, access points, operating hours and the site’s relationship to its surroundings are the basic inputs.
The assessment should be written down and agreed with the client before equipment is selected. A design that begins with a camera count and a brand preference tends to produce coverage where it is easy to install rather than where it is needed, and it gives no basis for judging whether the system is adequate after handover.
The output should be a document the client can act on: assets, exposure, likelihood, existing controls and recommended treatment. It should also state what is out of scope, because a design that quietly assumes the perimeter fence or the external lighting will be dealt with by someone else is not a design at all — it is a device list waiting to be renegotiated. In Dubai, security systems also fall under SIRA requirements, which is a further reason to settle the scope and the documentation at design stage rather than during installation.
Coverage planning for cameras
Camera coverage should be planned against purposes rather than angles. A camera at an entrance may need to identify faces, while a camera in a car park may only need to record vehicle movement. Resolution, lens choice, mounting height and light conditions all follow from the purpose, and the resulting images should be tested against it rather than assumed.
Coverage plans should show the fields of view over the architectural layout so that gaps and overlaps are visible. Corridors, stair cores, lift lobbies, loading areas and the perimeter are the usual priorities. Privacy-sensitive areas such as changing rooms and private entrances need explicit treatment rather than accidental coverage from a nearby camera.
- Entrances and vehicle gates where identification matters
- Lift lobbies, stair cores and main circulation routes
- Loading bays, service corridors and refuse areas
- Perimeter lines and roof access
- Car park entries, ramps and level signage
- Cash, plant and other restricted areas
Lighting and the physical layer
Lighting is part of the security design, not a separate electrical decision. Illumination at the camera location matters more than a manufacturer’s claim about low-light performance, and infrared or white-light illuminators need power, mounting and maintenance planned together with the camera. A coverage plan without a lighting plan is only half a plan.
The physical layer deserves the same attention: camera housings suited to outdoor heat and dust, correct mounting to resist wind load, containment that protects cabling, and power arrangements that keep working through a failure. In the UAE climate, heat management and dust ingress have a direct effect on image quality and on how long a device remains serviceable.
Lighting levels should be checked at commissioning, in the conditions the system will actually face. A camera that performs well at midday can produce unusable evidence at night, and the difference is usually illumination and lens choice rather than the recorder. Where lighting is controlled on a schedule, the security design should confirm that the schedule does not leave coverage gaps.
Access zoning and movement control
Access control works best when it reflects how people actually move. A zoning plan should define public, controlled and restricted areas, the transitions between them, and what happens at each transition during normal operation, out of hours and in an emergency. Drawn properly, the plan becomes the basis for door schedules, reader selection and alarm rules.
Zoning decisions should be documented per door: the reader type, the credential population, the release conditions, the time schedules and the fail-safe or fail-secure behaviour. This is also where fire-related release requirements are resolved, because an access-controlled door must not become a trap during an evacuation. Reviewing the door schedule with the operator before installation is almost always cheaper than changing it after the building opens.
The zoning plan should also account for visitors, contractors and deliveries, which are the movements most likely to be unplanned. A visitor process that relies on a receptionist remembering to issue a pass is not a control, and it tends to fail at exactly the busiest times. A defined process, recorded in the system, gives the operator something to audit.
Control room, documentation and commissioning
A control room should be designed around the operator’s task: room to sit, sightlines, display layout, lighting that does not reflect on screens, and an arrangement that keeps attention on the video wall. Access and environmental conditions should protect the equipment as well as the staff, and the room should be designed for the number of people who will actually work in it.
Documentation should be usable by the operator rather than only by the installer. As-built drawings, device schedules, IP addressing, credentials, configuration backups and test records belong in a single handover package, kept current as the system changes. A system that is documented only at installation becomes progressively harder to maintain and to extend.
Commissioning proves that the system behaves as designed. Test scripts should cover camera image quality, recording and retrieval, access events and alarms, intercom and door release functions, integration with fire systems where relevant, and the reporting the operator will use. Evidence should be retained, because a commissioning record is the only proof that a function was tested.
Security systems are judged in the minutes after an incident, not in the week after handover. Coverage, access and recording should be designed for that moment.
Discuss a similar requirement