Access Control & Gate Barrier Specification and Budget Guide

Published by MTT — My Telecom Technology, a systems integrator working across Bahrain and Saudi Arabia since 2007. More about MTT.

This guide is vendor-neutral and does not publish price ranges. It sets out the decisions that determine both the specification and the budget, so proposals can be compared on the same basis.

The most under-surveyed part of any access project is the door leaf itself. Frame type, leaf material, existing lock, closer condition, fire rating and glazing all determine which locking device is appropriate and how much builder's work is needed.

• maglocks, electric strikes and motorised locks each suit different frames and fire strategies;
• fire-rated doors constrain what may be fitted and how it must behave on alarm;
• door position sensors and request-to-exit devices are part of the scope, not accessories;
• closers and alignment must be serviceable, otherwise doors are propped and the system is bypassed;
• turnstiles and speed gates need floor loading, power and often civil coordination.

Barriers are specified by duty, not by boom length and price. Match the rating to the busiest realistic pattern at that lane — a logistics gate running continuously is a different machine from a staff car park with a short morning peak.

• peak vehicles per hour per lane, with a growth allowance;
• opening and closing speed required to clear the peak without queueing to the public road;
• stacking space on the approach, which is a civil constraint more often than a technology one;
• separate lanes or credentials for HGV, staff and visitor traffic where the mix differs;
• bollards, sliding gates or crash-rated products only where a genuine vehicle-mitigation requirement exists;
• intercom and a manual release for exceptions, so the lane is never propped open during a fault.

See gate barriers and vehicle access for how MTT delivers these lanes.

Controller architecture determines resilience and future cost. Consider how many doors each controller serves, whether decisions continue locally if the server is unreachable, how events are buffered during an outage, and how a controller is added later.

Then ask for software costs to be itemised: base platform, per-door or per-controller licences, client or user licences, modules for visitor management, biometrics or integration, and annual software maintenance. Server or hosting requirements, backups and administrator accounts belong in the same conversation.

These items are the most common source of variation on access projects because they are frequently outside the equipment quotation. Establish early who is providing:

• foundations or plinths for barriers, turnstiles and pedestals;
• ducting and containment for loops, reader cabling and camera runs;
• power supplies at each lane, door group and controller cabinet;
• network paths to controllers, ANPR cameras and intercoms;
• builder's work to doors, frames and glazing;
• lane marking, signage, lighting and pedestrian segregation.

Access systems degrade administratively before they degrade mechanically. Leavers stay enrolled, temporary permissions become permanent, and doors that no longer close properly get propped.

Budget for planned maintenance covering barrier mechanics and safety device testing, door hardware and closers, battery and power supply checks, firmware and configuration backup, and a periodic permissions review. Our AMC guide covers how to structure that properly.

• a site plan marking the doors and lanes to be controlled;
• user groups, approximate numbers and shift or visitor patterns;
• peak vehicle volumes per lane, if vehicles are in scope;
• details of any existing access system, controllers and credentials;
• your fire strategy or the requirements affecting door release;
• whether civil works, power and network are provided by others;
• the systems you want integrated, and their versions;
• site access constraints and the programme you are working to.