01
Start at the shared/private boundary.
Describe resident, visitor, delivery, maintenance and manager journeys. Someone may enter the lobby without rack or parking access. For each entrance, name the owner, users, intended command and states actually available.
Survey entry panels, indoor stations, cabling, power and retained references. IP, two-wire, credentials and apps describe options, not universal compatibility. Apartment count alone cannot select an architecture; verify topology, distances and reuse options.
02
Describe five zones without extending access by default.
Scroll the table horizontally to compare all three columns.
| Zone | Expected function | Point to confirm |
|---|---|---|
| Lobby and entrance | Call the intended recipient and handle the response. | Directory, hours, door, lock, power and available feedback. |
| Apartments | Receive intended calls without general access to other units. | Existing stations, interfaces, work access and responsibility limits. |
| Parking | Passage permissions and gate movement. | Pedestrians, vehicles, environment, mechanics and protection to assess. |
| Technical rooms | Access limited to authorised service personnel. | Owner, working windows, revocation and administrator accounts. |
| Shared networks | Carry defined building services. | Risers, equipment, Internet-access owner and private-space separation. |
03
A brief for the manager and installer.
Entrance and link plan
IDs for doors, buildings, risers and equipment. Include technical photos and known measurements, not a named resident directory or opening codes.
Permission lifecycle
Move-in, departure, lost credential and temporary contractor: who can create, modify and revoke? Describe roles and expected checks without real credentials.
Retained systems and decisions
References, versions, available configuration access and each item's owner. Assume neither administrator access nor permission to replace equipment in another scope.
Work organisation
Inform occupants through the agreed process, arrange needed appointments and plan continued access. The installer confirms safety, method and outage handling.
Handover and manager change
Request backups, drawings, roles, licences and an access-transfer process. Identify who holds management access; a manager change should not be an overlooked issue.
04
Example: one lost credential, not one shared building code.
ILLUSTRATIVE EXAMPLE
Fictional residence with lobbies H-A/H-B and parking P-01. A resident reports a lost credential and requests a replacement from the authorised manager.
Identify the scope
After the manager’s required verification, identify the affected credential and permissions. Do not copy another resident’s rights or create general access for convenience.
Revoke and verify
The brief requests old-credential revocation and confirmation at affected points. A message sent to the system does not prove every controller received it.
Issue the bounded replacement
Restore only agreed permissions, such as H-A but not H-B, and P-01 if authorised. Record tests and unavailable points without claiming unverified universal revocation.
A management requirement, not a guaranteed feature of every credential system. Readers, controllers and software must support the documented lifecycle and limits.
05
Managed access is not proof of overall safety.
An intercom command does not mechanically confirm opening. Professionals must assess gate protection and exits; HSE is a UK technical resource, not Moroccan regulatory approval. Confirm video fields, recipients and applicable rules before use. A shared network confers no right to access apartment networks.
06
Decisions that should not remain implicit.
Can existing indoor stations be retained?
Verify references, versions and topology. Wire count or similar appearance is insufficient. Request an explicit retained/replaced list with confirmed limits.
Can one credential open the lobby and parking?
Validate that requirement, not a promise based on frequency. Check technologies, readers, permissions and management; a shared credential format must not force shared permissions.
Does an app replace the apartment station?
Define needs for people without smartphones and during Internet loss. Confirm subscriptions, accounts, dependencies and local controls before deciding.
Who receives configuration at handover?
The designated project owner under agreed rights and licences. Specify formats, backups, support access and future transfer; do not distribute secrets in resident-shared documents.
Technical sources
External reading references. These documents explain principles; they do not certify catalogue products or their combination.
- AXIS A1210 Network Door Controller — User manualAxis Communications · Sources consulted on
- Ensuring powered doors and gates are safeHSE — United Kingdom · Sources consulted on