A public building is a civic building that the public visits by right, by appointment, or by ticket — a public library, a community centre, a civic hall, a

Δημοσιεύτηκε στις: Μαϊ 28, 2024

Smart Locks for Public Buildings

Smart Locks for Public Buildings

A public building is a civic building that the public visits by right, by appointment, or by ticket — a public library, a community centre, a civic hall, a public museum or civic gallery, a one-stop service counter, a civic theatre, a recreation centre, a swimming pool, a parks maintenance depot, a registry office. It is not, in this article, a government building. Government buildings — the administrative offices of a state, council or agency — are the subject of the SOP-lens article that this site publishes separately, with a deliberately procedural and compliance-led framing. Public buildings are governed differently: by an opening-hours policy that the public reads in advance, by an after-hours booking policy that lets civic tenants share the building, by a vendor-escrow policy that hands keys to cleaners, hirers and contractors on a controlled rotation, and by an egress and safety policy that the authority having jurisdiction and the operator's own counsel own, not the lock manufacturer. The door-lock product fits inside that governance. It does not replace any of it.

We have quoted and built electronic locks for 10+ years, into 80+ countries, and what follows is the manufacturer-side decision piece on what a defensible public-building smart-lock programme looks like when the five governing pillars are kept separate. The through-line is one sentence: opening hours discipline, after-hours booking windows, vendor key escrow and safety-versus-egress tradeoffs are four different lock operating regimes; conflating them into a single RFQ is the most common public-sector procurement mistake. Five pillars follow.

This article is for system integrators, distributors and procurement officers serving municipal authorities, civic trusts, public-library services, recreation authorities, community-hall operators and civic-theatre boards. It is deliberately distinct from Smart Locks for Government Buildings (the procedural SOP lens for administrative buildings — chain-of-custody, audit retention, named-custodian mechanical override), from Smart Locks for Critical Infrastructure (the consequence-led lens — utility, transport, energy assets), from Smart Locks for Campuses: A Master-Plan Buyer's Hub for Site Entries, Perimeter Doors, and the Honest Boundary With Central Identity Systems (the perimeter and master-plan lens — site entries, vehicle gates, central identity systems) and from Smart Locks for Laboratories: A Round-by-Round Comparison Across Teaching Lab, Research Lab, Chemical Store and Cleanroom-Adjacent Vestibule (the single-building library lens — public entrance, stacks, special collections, study rooms). Where these lenses overlap on civic doors they are named and routed.


Pillar 1 — The five-class civic door map

Almost every subsequent decision on a public-building programme is easier if the door population is first drawn on a single page with five named door classes and a per-door governance label. Without that map, one RFQ sent to one supplier invites that supplier to quietly absorb scope the per-door product does not own, and the procurement conversation drifts from "which lock on which door" to "please replace our building management system," which is a different vendor's job.

Door classTypical door examplesGovernance ownerPublic-building entry point
Public-facing front-of-house doorsMain entrance, vestibule, accessible entrance, exit doors on the egress pathBuilding manager / facilities officer + AHJPublic use during opening hours; egress discipline dominates; the lock is one component inside an egress system — see Pillar 5
Opening-hours-locked doorsReading-room doors in a library, exhibition galleries in a civic museum, court / studio / activity-room doors in a community centre, hall doors in a civic theatreDepartmental head — librarian, curator, hall managerPublic access during the posted hours; staff-controlled at all other times; this is the canonical "scheduled unlock" lock problem
After-hours bookable doorsHirer-booked rooms in a civic hall, sports-hall courts outside staffed hours, meeting rooms let to community groups, theatre stage when a hirer takes the buildingBookings officer + named duty managerBooking-window-only access via code or RFID issued at booking time; per-credential expiry mandatory
Vendor / contractor doorsCleaning-cupboard doors, plant-cupboard doors, service-yard doors, server-room or IT-closet doors, delivery-bay doors, food-and-beverage service doorsEstates / facilities manager + named vendor adminMechanical-key escrow for named vendors on a controlled rotation; per-job or per-window credential expiry
Staff back-of-house doorsStaff-only offices, back-of-house corridors, kitchen / servery, staff WCs, cash office, payroll office, records room, plant roomBuilding manager / facilities officerWorkplace-grade access control; the lock product's most comfortable fit

The single most important move in this map is the bracketed rule at the bottom of the table: every public-building door is policy-controlled, not free, and the lock product fits each door class at a different depth — from "scheduled unlock" on opening-hours doors to "mechanical-key escrow with audit" on vendor doors to "component inside an egress system" on front-of-house doors. The next four pillars go door class by door class.

How to use this map

Three rules. Walk the building and mark every door that takes a credential — not every door in the building, but every door whose opening is policy-controlled rather than free. On the worksheet, write the door class from the table above. Write the governance owner. Note any door whose lock is downstream of a building-wide system (a fire-panel release, a BMS-controlled unlock, an intercom with reception, an elevator destination dispatch), and tag those doors with the phrase "Not the lock supplier's scope." The doors that survive this filter are the ones the per-door-lock RFQ will name. Doors with the tag go to a different contract lot — typically a system-integrator RFQ for the central building system, a fire-egress hardware professional for monitored release, or an alarm contractor for monitored intruder.

The single-supplier-for-everything temptation recurs in civic procurement because the RFP process encourages a single point of accountability. The honest answer is that the door-lock supplier is good at the door lock, the system integrator is good at the central system, and the two contracts are written separately so neither quietly absorbs the other. A single supplier covering all of it is usually a single supplier that has over-promised in writing.


Pillar 2 — Opening hours discipline

The second pillar is the public-building lock problem most people think they have, and most people solve wrong. Opening hours discipline is the policy that says: from Monday to Friday, 09:00 to 20:00, this door is open to the public; outside those hours it is staff-controlled. Posted publicly; on the door; on the council website; on the library's printed schedule. It is also, on a public building, a politically visible commitment that the public can read and complain about. The lock on these doors is the operational expression of the schedule.

What the lock actually has to do

Two operational moves, repeated every weekday, plus the same moves repeated for evening or weekend extension when the building is open for an evening programme:

  1. Schedule-driven unlock at the posted opening time. The lock releases automatically for the public-facing side at the moment the building opens, on every day the building is open. On the staff-facing side the lock is staff-controlled all day.
  2. Schedule-driven re-secure at the posted closing time. At the closing minute the public side re-seals; any staff member exiting after hours uses the staff credential; the public-side credential becomes inactive until the next scheduled open.

The schedule is held in the lock's management software (PC software on supported hotel-class models — see the catalog spec base — or app-based management on Bluetooth-class models), and the schedule change is made by a named administrator who is the duty manager for the day. Check the model’s published specification for the SKU under evaluation that the schedule is held on the lock itself or on the management software, what the override path is when the schedule needs to be changed at short notice (a late evening booking, an emergency closure, a public holiday swap), and what the audit trail of schedule changes looks like.

What the opening-hours discipline spec must contain

Five non-negotiable inclusions before any model is shortlisted for opening-hours duty:

  1. Posted-schedule as the canonical input. The lock's schedule must mirror the publicly posted schedule exactly, including seasonal extensions, public-holiday closures, evening-programme windows and emergency closures. A model whose schedule is held only in a phone app the duty manager may or may not have is the wrong model. Check the model’s published specification that the schedule is held on the lock or on the management software, and that it can be exported for the duty-manager handover.
  2. Manual override for early closure or late opening. A public building sometimes closes early (severe weather, power outage, public-health instruction) or opens late (staff absence, equipment failure). The lock must release to a staff manual override without a network, without a phone, without a credential-server connection. Check the model’s published specification what the override path is.
  3. Audit trail of every override. A duty manager who closes the building 90 minutes early on a Tuesday in February should leave an audit record that the building manager can review. Check the model’s published specification whether the lock's audit log captures manual-override events distinctly from scheduled events.
  4. Mechanical override in custody of the named building manager. Every opening-hours door has a mechanical key in the cylinder. The custody chain matters: who holds the key, where the master is held, what the rotation period is for the seal, what the lost-key protocol is. Mechanical-override design and keyway custody are both model-specific and must be confirmed on the product page.
  5. Battery type, count and service interval. An opening-hours door on a five-day-a-week, 50-week-a-year cycle is doing roughly 250 schedule-driven cycles plus an unknown number of override cycles per year. A model with a battery rotation interval shorter than the planned maintenance cycle forces a budget line the building manager did not plan for. Battery type (commonly 4 × AA on hotel-class locks and equivalent spec on others; check the model’s published specification) and dead-battery behaviour (does the lock fail-secure or fail-safe, and what is the mechanical-key path) belong on the product spec block before order.

What the opening-hours discipline spec must defer

Three deliberate deferrals, named so the RFQ does not ask the lock manufacturer for them:

  1. The publicly posted schedule itself. A council's decision to open the library until 20:00 on Tuesdays is a policy decision made in a council chamber, not a lock-manufacturer decision. The lock reflects the policy; it does not write it.
  2. The signage on the door. A printed opening-hours poster on the door is a signage decision; a council-communications decision; a public-information decision. The lock and the signage should match; the lock manufacturer is not the source of the signage.
  3. The accessibility / egress / panic-hardware release. An opening-hours door that becomes an egress door in an emergency is governed by the AHJ's life-safety interpretation, not by the lock product's spec sheet. The lock on that door is one component inside the egress system. Pillar 5 names this boundary in detail.

A useful rule of thumb: if the schedule change on the door is decided by a person who is not the building manager, the lock is on the wrong governance door. A model whose schedule can be edited by any staff credential on a Tuesday morning is a model the duty manager cannot defend in a public hearing. Check the model’s published specification that schedule edits are role-gated.


Pillar 3 — After-hours booking windows

The third pillar is the civic-building lock problem that has the most public-facing political risk and the least honest industry coverage. Civic halls, community centres, recreation centres and civic theatres are routinely hired out to community groups, theatre companies, sports clubs, wedding parties, faith groups, school examinations and commercial hirers outside the building's staffed hours. The booking window is the time slot the hirer has been granted; the booking window is also, on a public building, the only time the hirer has legal possession of the building for the duration of the booking. The lock product is the operational expression of that legal possession.

What the lock actually has to do

Three operational moves on every booking:

  1. Issue a booking-window credential at booking confirmation. When the bookings officer confirms a Saturday-evening hall booking for the local drama society, the system issues a credential (RFID card, PIN code, app-Bluetooth key) that activates at the booking start time and expires at the booking end time. Per-credential expiry is mandatory; a credential that does not expire is a credential the bookings officer cannot defend.
  2. Release the lock on a credential presented during the booking window only. A credential presented before the booking window is refused; a credential presented after the booking window is refused; a credential presented during the booking window releases the lock and writes an audit record. The audit record is the booking officer's proof that the hirer arrived within window.
  3. Forfeit the credential at the booking end. At the booking end minute the credential is automatically invalidated. A hirer who tries to re-enter the building after the booking end is refused; the bookings officer and the duty manager receive an attempted-after-hours-access event in the audit log; the building is sealed for the next booking or for the staff next day.

Per-credential window support is a model-specific capability. Check the model’s published specification for the SKU under evaluation that the SKU supports per-credential time windows down to the smallest unit the bookings officer needs — hourly for most hall bookings, multi-day for wedding-weekend hires, multi-week for theatre-season lets.

After-hours booking window checklist

A bookings officer who is issuing credentials to outside hirers needs a controlled workflow that the lock can support. Eight items, in order:

#Booking-window workflow itemLock product's roleOut-of-scope
1Booking made and deposit takenNoneBookings system; payment; deposit policy
2Booking confirmation issued with date, start, endNoneHire agreement; terms and conditions
3Credential issued (RFID, PIN or app) with per-booking expiryLock product's central roleHirer identity verification (institutional)
4Credential delivered to hirer (collection, post, email)NoneDelivery method is institutional
5Credential activated at booking start timeLock product — schedule gateNone within per-door scope
6Credential honoured only during booking windowLock product — time-window checkNone within per-door scope
7Credential forfeited at booking end timeLock product — automatic invalidationNone within per-door scope
8Audit log exported to bookings officer at week-endLock product — retrieval pathLong-term retention is institutional

What the booking-window spec must contain

Five non-negotiable inclusions before any model is shortlisted for after-hours booking duty:

  1. Per-credential time windows down to the hour. The smallest credible booking unit on a civic hall is one hour; on a recreation centre it is half an hour; on a civic theatre it is half a day. A model whose smallest credential window is a full day cannot serve the bookings officer's actual schedule. Check the model’s published specification.
  2. Per-credential cancellation by the bookings officer. When a hirer cancels, the bookings officer must be able to invalidate the credential immediately and remotely, without visiting the door. Check the model’s published specification that cancellation is role-gated and auditable.
  3. Per-credential audit trail retrievable per booking. The bookings officer must be able to pull an audit record for a single hirer for a single booking, not just a building-wide event log. Check the model’s published specification.
  4. Mechanical override in custody of the duty manager. The duty manager's mechanical key is the path when a credential fails, when a hirer is locked out, or when a booking overruns. The custody chain is named and the key is held in a sealed envelope on the duty manager's person or in the building's named-key safe. Check the model’s published specification the cylinder design and keyway family.
  5. Anti-passback where the building has a defined ingress / egress path. Some civic halls have a clear one-way flow during booking (main door in, fire door out); some have free-flow. Where the policy is one-way, anti-passback support prevents a credential from being lent to a second person mid-booking. Check the model’s published specification whether the SKU supports anti-passback and how it is configured.

A booking-window honest scope point

A lock with a per-credential booking window does not, by itself, perform the identity verification on the hirer. The bookings officer does that. A lock that "verifies" the hirer by reading their fingerprint is doing something else — it is a biometric lock with a different legal posture, and on a public building the data-protection implications of capturing hirers' biometrics outside a staff relationship belong to the operator's data-protection officer and to the relevant national framework. This is named, not solved, here. Check the model’s published specification whether the SKU under evaluation supports biometric credentials and what the enrolment and storage path is.


Pillar 4 — Key escrow for civic vendors

The fourth pillar is the lock problem that civic procurement handles worst. Civic buildings depend on a regular flow of named vendors — cleaning crews, maintenance contractors, security patrol officers, IT service technicians, food-and-beverage suppliers, plant-room service vendors, equipment hirers (the sound-and-lighting contractor for a civic theatre, the ice-resurfacing machine contractor for a recreation centre), and one-off specialist contractors for tasks like window cleaning, gutter clearing, pest control, lift inspection. Every one of those vendors needs access on a controlled window, and most civic procurement handles the access through a mechanical-key escrow that is poorly controlled, poorly audited and routinely compromised by photocopying, sticky-label keyrings and unrecorded handovers. The lock product's job here is to give the building manager a per-vendor, per-window credential that does not require photocopying a key.

The four vendor classes on a typical public building

Vendor classAccess shapeGovernance ownerBest-fit credential lane
Cleaning crewRecurring window (often late evening or early morning) on a defined door listBuilding managerPer-key PIN with per-day or per-week expiry; mechanical key as backup
Maintenance contractorOne-off or scheduled window for a named taskBuilding manager + estatesPer-job RFID with per-job expiry; mechanical key as backup
Security patrol officerRoutine night-time patrol across a defined routeBuilding manager or contracted security supervisorPatrol-class RFID with time-stamped check points; check the model’s published specification whether the SKU supports patrol verification
Plant / specialist contractor (lift inspector, gas engineer, fire-extinguisher service, pest control)One-off or annual windowEstates + the relevant compliance ownerPer-visit RFID or PIN with auto-expiry on the named visit window

What the key-escrow spec must contain

Five non-negotiable inclusions before any model is shortlisted for vendor escrow:

  1. Per-vendor credential with per-window expiry. The cleaning crew for Tuesday and Thursday evenings gets a Tuesday-and-Thursday credential that expires at the end of each shift; the lift inspector for the annual visit gets a one-day credential that expires at midnight. A model whose vendor credentials do not expire automatically forces the building manager into a manual deletion queue, and a manual queue is the queue that goes unwiped. Check the model’s published specification.
  2. Named-vendor audit trail retrievable per vendor per visit. When a building manager is asked "did the cleaning crew enter on Tuesday," the answer must be one minute away. Check the model’s published specification that the audit log is searchable per credential and exportable to a CSV or PDF the building manager can hand to the council's compliance officer.
  3. Mechanical-key escrow protocol separate from the smart-lock system. The mechanical key remains the backup path and is held in a named key safe, usually with the building manager and one deputy. Check the model’s published specification the cylinder design and keyway family, and write the key-rotation protocol into the building manager's standing operating procedure.
  4. Revocation on vendor change without a lockout of other vendors. When the cleaning contractor changes in March, the building manager must be able to revoke all credentials issued to the outgoing contractor without disturbing the credentials of the incoming contractor or the ongoing maintenance contractors. Check the model’s published specification that revocation is per-credential, not per-lock.
  5. No vendor-side enrolment of new credentials. A cleaning crew supervisor who can enrol a new cleaner onto the building's lock without the building manager's involvement is a supervisor the building manager cannot defend. Check the model’s published specification that enrolment is role-gated to a named building-side administrator.

The honest key-escrow anti-physical point

A smart lock does not, by itself, prevent a vendor from copying a mechanical key at a hardware shop. The mechanical key is the backup path; if the building manager's protocol allows an unrestricted key, the protocol is the failure mode, not the lock. The smart lock's job is to make the smart credential the path of normal use, so that the mechanical key is touched only in failure or override, and so that any use of the mechanical key is the exception that the audit log highlights. Check the model’s published specification whether the lock logs mechanical-key use as a distinct event class with a time-stamp.

A second honest scope point: the smart lock is not the vendor-insurance policy. If a cleaning contractor is asked to prove they cleaned the building on Tuesday, the proof is a cleaning log, a patrol-class RFID check, a sign-in register, or a service report — not the lock's audit trail in isolation. The lock audit supports the proof; it does not constitute it.


Pillar 5 — Safety versus egress tradeoffs, honestly framed

The fifth pillar is the editorial core of this article and the one most often written dishonestly in civic procurement. The temptation is to claim that a smart lock contributes to the safety of a public building in a way the lock product can certify. The honest position is the opposite: a smart lock on a public building door is a credential-and-product component. It supports safety by being reliable in the sense of doing its job every day, and it supports egress by failing in the direction the egress plan requires. Neither contribution is a safety certification; neither is a substitute for the egress system; neither is a substitute for the operator's written safety policy. The lock manufacturer cannot certify fire compliance, panic-hardware compliance, accessibility / ADA-equivalent compliance, or authority-having-jurisdiction approval. None of those compliance items are the lock manufacturer's competence, none are within the lock product's spec block, and any line in an RFQ that asks the lock manufacturer for one of those certifications is a line that needs to be split.

The four honest safety / egress scopes

ScopeWho owns itLock product's roleOut-of-scope (named)
Fire-egress behaviour on a public-facing doorAHJ + operator's counsel + fire-safety hardware professionalThe lock fails in the direction the egress plan requires; the lock's fail-secure vs fail-safe behaviour is a credential-coordination conversation, not a fire-rating conversationFire-rating certification, fire-alarm panel release, panic-hardware certification
Accessibility / ADA-equivalent compliance on a public-facing doorAHJ + operator's accessibility officerThe lock supports accessible operation (card on a lowered reader, app-Bluetooth for non-key holders, mechanical key override); the lock does not certify accessibilityDoor-operator hardware, threshold design, signage, wayfinding
Public-facing door monitoring (reception / intercom / vestibule flow)Building manager + reception operatorThe lock supports scheduled unlock, manual override by reception, audit of door events; the lock is not the visitor-management systemIntercom, video, reception workflow, visitor-management software
Intruder resistance after hoursBuilding manager + alarm contractorThe lock's mechanical-override discipline and audit log support a coordinated intruder response; the lock is not the alarmAlarm panel, monitored response, ARC routing, police response

The honest observation: the lock product's safety role is narrow and supportive. It is the role of doing its job on a normal day, failing in the right direction in an abnormal day, and producing an audit record that the building manager, the duty manager and the AHJ can reason about. It is not the role of substituting for the egress hardware, the alarm, the fire panel, or the operator's written safety policy. Any lock supplier — including us — that offers to certify any of these is a supplier that has over-stepped in writing.

The three honesty disciplines on every public-building RFQ

Three disciplines follow from the four scopes above and apply to every public-building smart-lock programme:

  1. Refuse in writing to certify fire, egress, accessibility or alarm compliance. The lock product is a component; the system is a system. Any RFQ line that conflates the two is a line that needs to be split. Check the model’s published specification what the lock's fail-secure / fail-safe direction is, and write that direction into the operator's egress plan as a contractual conversation with the AHJ and the operator's counsel — not as a lock-manufacturer certification.
  2. Name the operator's egress plan as the canonical input. A public building's egress plan is written before any lock is purchased; the lock is specified to the egress plan's requirements; the egress plan is updated if the lock changes the plan's assumptions. The lock does not write the egress plan and the lock manufacturer does not sign the egress plan. Check the model’s published specification that the lock's specification can be reconciled with the operator's written egress plan and the AHJ's interpretation.
  3. Refuse to write the operator's safety policy. The operator's safety policy is the operator's document, signed by the operator's accountable officer, and reviewed on the operator's review cycle. The lock supports the policy; the lock does not write the policy. The integrator's role is to surface the boundary at every RFQ meeting where the boundary is at risk of being blurred.

These three disciplines are not criticisms of lock products. They are the disciplines that keep a public-building programme defensible at a public hearing, at an internal compliance review, and at the AHJ's next inspection.

A second honesty discipline: the safety / egress model choice

The supporting services hold that the lock's mechanical-override design, fail-secure / fail-safe direction, mechanical-key custody, audit-trail capability, and battery behaviour all belong on the product spec block before order. None of these is a safety certification; all of them are inputs to the operator's egress plan, to the AHJ's review and to the building manager's standing operating procedure. The SLK-9936S hotel-class lock product-page-documented spec block — door thickness 36–100 mm, RFID Mifare 1 @ 13.56 MHz, read distance 0–5 cm, read time under 0.25 s, 4 × AA power, battery operating cycles above 15,000, audit / event records up to 1,000, 5-pin cylinder, 3-point latch, stainless steel + alloy body, multiple finish options, mechanical emergency access, multilingual management software, standalone or centralized database modes — is invoked here once as a documentation-format yardstick: it shows what granularity of disclosure a sophisticated public-building lock spec block should contain. The SLK-9936S is positioned for 1–5 star hotels; the figures are hotel-class and do not transfer to public-building models. The model actually ordered for a public-building door must be confirmed on the product page.


Decision matrix — public-building door class to lock product fit

The matrix below summarises the per-door catalogue fit for every door class named in the five pillars, with the honest out-of-scope tags inline. Three rules apply: (a) the matrix reads per-door, not per-building; (b) per-model capabilities must be confirmed on the product page for the SKU under evaluation; (c) the SLK-9936S product-page-documented spec block is published here as a documentation-format yardstick only; the figures are hotel-class and do not transfer to public-building models.

Door classGovernance ownerBest-fit credential laneMechanical-override holderOut-of-scope (named)
Public-facing front-of-house entranceBuilding manager + AHJKeypad or RFID with scheduled unlockBuilding managerFire-egress hardware, panic hardware, accessibility hardware, intercom, reception workflow
Accessible side entranceBuilding manager + accessibility officerRFID with lowered reader or app-BluetoothBuilding managerThreshold design, door-operator hardware, signage
Reading-room (library)LibrarianRFID or keypad with posted-scheduleLibrarianPosted opening-hours policy is institutional
Exhibition gallery (civic museum)CuratorRFID with schedule; per-curator-of-staff credentialCurator + named deputyExhibition policy, fire-load policy, signage
Hall / studio / activity-room door (community centre)Hall managerRFID or keypad with per-booking-window credentialHall manager + duty managerBooking-system workflow, deposit policy, hire agreement
Sports-hall court (recreation centre)Recreation managerRFID with per-booking-window credentialRecreation managerBooking-system workflow, supervising-staff rota
Civic theatre auditorium doorTheatre managerRFID or keypad with per-production credentialTheatre manager + duty managerProduction agreement, fire-curtain system
Stage door (civic theatre)Theatre managerRFID with named-stage-staff rosterTheatre managerStage-rigging certification, performer agreements
Hirer-booked meeting room (community centre)Bookings officerKeypad with per-booking PIN, per-credential expiryBookings officer + duty managerBookings-system workflow, hire agreement
Cleaning-cupboard doorBuilding managerKeypad with per-cleaning-shift PINBuilding managerCleaning-contractor SLA, payment
Maintenance contractor doorBuilding managerRFID with per-job expiryBuilding managerMaintenance-contract SLA, RAMS documentation
Plant-room doorEstates / facilitiesFingerprint or RFID with per-contractor expiryChief engineer / facilitiesBMS, alarm, gas-safe certification
Service-yard / delivery-bay doorBuilding managerOutdoor-class lock with scheduled unlock and auditBuilding managerWeather envelope — check the model’s published specification
Server / IT-closet doorBuilding manager + IT leadRFID or fingerprint with named-IT-staff rosterIT leadUPS, fire suppression, network itself
Staff-only officeBuilding managerFingerprint, keypad or RFIDBuilding managerNone within per-door scope
Back-of-house corridorBuilding managerRFIDBuilding managerNone within per-door scope
Records roomBuilding manager + records officerFingerprint or RFID with named-records-staff rosterRecords officerRecords-management compliance is institutional

Catalog-coverage snapshot for the public-building programme

The catalogue has 79 published models across Smart Door Locks, Fingerprint, Hotel, Keypad, Outdoor, RFID, Face Recognition, Cabinet, Glass and Video Camera categories; per category, 77 Smart Door Locks, 37 Fingerprint, 24 Hotel, 18 Keypad, 10 Outdoor, 9 RFID, 6 Face Recognition, 6 Cabinet, 3 Video Camera, 3 Glass. Unlocking methods across the catalogue span fingerprint, passcode, RFID / IC card, mechanical key, app / Bluetooth across TTLock, Tuya and Doodle lanes, remote control, 3D face on a small number of face-recognition models, hotel PC software, camera / cat-eye and 4G. Palm-vein, Matter, Zigbee and Apple Home Key are not in the catalogue and are not attributable to any model — do not request them. Check the model’s published specification for the SKU under evaluation which unlocking methods and which app lane are supported.


Illustrative scenario — a multi-purpose civic centre

Consider a multi-purpose civic centre that combines a public library on the ground floor, a community hall with three bookable rooms on the first floor, a small civic theatre with a 220-seat auditorium and a stage, a public gallery with two exhibition rooms, a registrar's one-stop service counter, a recreation centre with two sports halls and a swimming pool, and a basement plant room with boiler, chiller and electrical plant. The building manager has been asked by the council to "send a smart-lock RFQ to the existing lock supplier." The building manager pauses.

Walking the building with the five-class civic door map, the building manager marks roughly 180 lockable doors and tags about 132 of them as in the per-door-lock catalogue's natural fit — library reading-room doors (24), library back-of-house staff doors (8), community-hall bookable-room doors (3), community-hall kitchen and servery (4), sports-hall storerooms and admin (6), swimming-pool staff rooms and plant cupboards (12), civic-theatre auditorium and stage doors (8), civic-theatre box office and admin (5), public-gallery exhibition and staff doors (8), registrar's office and records room (6), cleaning-cupboard doors (12), maintenance contractor doors (8), staff-only offices (14), back-of-house corridors (8), server / IT-closet doors (4), plant-room doors (4). The building manager tags the remaining 48 doors as not in scope for a single per-door-lock supplier: 6 main entrances and accessible side entrances (sent to the egress-discipline conversation with a qualified door hardware professional, the AHJ and the operator's counsel), 8 service-yard and delivery-bay doors where a combined egress, weather and alarm coordination is in play (sent to a system-integrator RFQ), 4 networked reader doors reading the council's one-card credential (sent to the council identity-system contract), 12 monitored intruder / fire-alarm-controlled doors (sent to the alarm contractor), 6 BMS-coordinated plant doors (sent to the BMS integrator), 12 panic-hardware-controlled emergency-exit doors (sent to the egress-hardware professional).

The 132 doors are split into five lots — one per door class — and the RFQ is sent for each lot separately, with a per-door spec worksheet and a request to verify against the model’s published specification each per-model capability: door thickness envelope, credential capacity, per-credential expiry, audit depth, mechanical-override design, battery spec, app / Bluetooth lane where relevant, weather envelope on outdoor-facing doors, and any specific integration requirement. The SLK-9936S product-page-documented spec block is attached to the briefing pack as a documentation-format yardstick only, with an explicit no-porting-across-models firewall: the figures are hotel-class and do not transfer to the public-building lots.

This is what a clean public-building RFQ looks like. It does not deliver the egress system, the alarm, the fire panel or the BMS. It delivers 132 per-door decisions, each named on its own line, each confirmed on the product page, each with mechanical override and audit posture decided in writing. The other 48 doors go to the appropriate contract lots.


Where this article leaves the integrator

A defensible public-building smart-lock programme is a programme that splits the door population into five named classes — front-of-house public doors, opening-hours-locked doors, after-hours bookable doors, vendor / contractor doors, and staff back-of-house doors — and treats each class as a different lock operating regime with its own governance owner, its own per-credential discipline, its own mechanical-override custody chain and its own audit posture. It refuses to conflate opening hours with booking windows, refuses to conflate booking windows with vendor escrow, refuses to conflate any of them with the egress and safety conversation that the AHJ and the operator's counsel own. It writes the lock product's spec block against the product page, and it routes every fire, egress, accessibility and AHJ-compliance line away from the lock manufacturer.

The five pillars above are the lock-supplier's honest contribution to that conversation. They are deliberately distinct from the SOP-lens approach the government-buildings article takes for administrative buildings, from the consequence-led approach the critical-infrastructure article takes for utility and energy assets, and from the perimeter-led approach the campuses article takes for site entries and vehicle gates. Where the lenses overlap — and they do, on plant rooms, on staff-only corridors, on mechanical-key custody — the overlap is named and routed.

The next move is on the integrator's side: send the per-door spec worksheet with each door class as a separate lot, request confirmation on the product page for every per-model capability, attach the operator's egress plan and refuse in writing to certify anything the lock product does not certify. For a per-lot quotation, an audit-trail export format, a sample-test programme or a multi-building rollout, request a quotation with the worksheet attached and the door-class tags preserved. For samples on a small lot before the RFQ is finalised, the sample-ordering page names the documentation pack the supplier should send with each sample.

Το καλάθι σας
Η εμπειρία σας σε αυτόν τον ιστότοπο θα βελτιωθεί με την ενεργοποίηση των cookies Πολιτική cookies
Chat on WhatsApp