Elevator and floor access project definition: A decision tree that defines elevator and floor access scope, decision authority, message set, degraded.

Geplaatst op: dec. 18, 2024

Elevator and Floor Access for Smart Lock Projects: What Buyers Must Define First

Elevator and Floor Access for Smart Lock Projects: What Buyers Must Define First

Elevator and floor access project definition is what this piece addresses for the system that has to work on a real door. Most floor-access briefs arrive as one column in a spreadsheet. It lists the floors, names the lobby reader, marks the service lift, and notes that the upper floors are restricted. That column records which spaces exist. It says nothing about who may cross them, which system decides, what the lift side sends back, or what the building does when the link is down.

Direct answer. The one-line answer — elevator and floor access project definition is the working record for elevator and floor access project definition. elevator and floor access project definition is worthless until elevator-and-floor-access is attached to it as evidence. An elevator and floor access project definition is an integration view. Lock, door, reader and system have to behave together. elevator and floor access project definition is where the first interface behind elevator and floor access project definition fails.

  • Draw the interface — write down what hands over between lock, door and system at elevator and floor access project definition
  • Exercise the handover — record the sequence that proves elevator-and-floor-access works end to end
  • Archive the record — store the commissioning evidence with the file for node writing journey down
  • For elevator and floor access project definition, elevator and floor access is what each step has to answer to.

Elevator and floor access project definition is the work of turning that column into decisions somebody can sign, each resting on the one before it. Get the order wrong and the project opens with the expensive questions — hardware, interface, commissioning — while nobody has agreed what the system is for.

This is a decision tree for the integrator at evaluation stage: nine nodes, each forcing one question and producing one field. A field is answered by a named party or carried into an open-items register with an owner.

The tree in one view — elevator and floor access project definition

flowchart TD
  A[Journey written as origin and destination] --> B[Scope line drawn and exclusions written]
  B --> C[Decision owner named for each journey]
  C --> D[Message schedule written as states]
  D --> E[Unavailable behaviour approved per door]
  E --> F[Clock and record rules fixed]
  F --> G[Entitlement binding rule fixed]
  G --> H[Definition pack signed]
  C --> I[Open item registered with a named owner]
  I --> C
NodeThe question it forcesThe artefact it produces
1Which journey must cross the building?Journey sheet: origin, destination, reason
2Which floors, doors and devices are in scope?Scope line with exclusions
3Where may the access decision live?Authority statement and escalation path
4What crosses the boundary, in which order?Message schedule with a missing-message rule
5What happens when the link is down?Approved behaviour per unavailable case
6Which clock stamps the events?Time source and reconciliation rule
7What is written, where, and who may read it?Record schedule and reader list
8Which credentials carry which floors?Entitlement binding rule and change path
9What is deliberately still open?Open-items register with named owners

The order is the argument. Nodes 1 and 2 cost nothing to settle and are expensive to get wrong, because every later node inherits them. Node 9 is not a failure to define; it is the list of what somebody else must still decide. The range this procurement eventually buys from is the smart door locks.

Node 1 — Write the journey down before the door list

A floor-access project begins with a movement question, not a device question: who needs to cross which boundary, and why must that crossing be controlled? A staff member reaching an operational floor, an escorted visitor, a contractor whose entitlement expires — each needs a different device or none at all.

The journey sheet names the origin, the destination, the credential class and the reason the crossing is restricted. A staff member needs a reader at the landing; a guest may be carried by an entitlement in the property system. The sheet is what stops the lobby becoming the only protected door in the building.

Node 2 — Draw the scope line, including what sits outside it

Elevator and floor access scope is usually drawn as a circle around the lobby and the lift core. That circle is where the lock's responsibility starts and stops, so the exclusions matter: service lifts on staff-only routes, riser doors, car call panels, floor selection devices, and landing doors controlled by another party.

Two systems claiming the same landing door is the classic way an integration loses a week. Write who owns the landing door release at each controlled door, and mark every door where that ownership sits elsewhere. The published Hotel Smart Lock Elevator Access and Hotel Smart Lock Access Control Integration pieces describe that boundary from the property side.

Node 3 — Say where the decision is allowed to live

Three parties can plausibly hold the decision for a floor request: the access controller, the elevator group controller, or the property system. Each produces a different interface contract and a different person to call at midnight. Name, for each journey, which one decides and what the other two are told.

If two systems can each grant, the definition has produced an ambiguity rather than an answer. Keep the vocabulary precise: a reader reports what was presented, the controller decides what it means, and a lift system may accept or refuse a destination without knowing about credentials.

The path between a reader and its controller decides how much the door can decide on its own. Wiegand is a legacy wiring convention that carries a data line and usually a power and a ground, and it says nothing about encryption or device identity. OSDP is a specified, addressed, bidirectional protocol with device addressing and a defined message structure. Whether a given lock implements either one is a per-SKU question to confirm on the dated product page for the specific SKU.

Node 4 — Write the interface as states, not as features

Elevator floor access integration is described in features and settled in states. "The systems are integrated" is not a description. A floor access control interface is a message schedule: who sends what, what the receiver does with it, and what happens when it never arrives.

MessageSenderWhat it meansIf it never arrives
Floor requestControllerA holder wants a destinationThe request expires and the requester is told why
Destination authorisationDecision ownerThat destination is permittedNo destination is offered
Car assignmentLift systemA car is committed to the journeyThe request expires or stays local
Landing release requestControllerA landing may openThe landing stays as it is, and the state is recorded
Release acknowledgementLift systemThe landing was releasedThe controller holds an unmatched request
Event recordEither sideA decision was takenReconciliation at the next exchange

Two clocks and an unmatched request are where events are lost, so the schedule names who reconciles.

Node 5 — Draw the unavailable case before the normal case

Degraded mode access control is where most floor-access definitions go silent, and silence becomes the commissioning argument. For each element — the network link, the controller, the server, the lift side — the building needs an answer: whether the door behaves as its own approval allows, whether a local manual route exists, or whether nothing opens and an operational procedure takes over.

The sequence between a floor release and an access-controlled landing is written as a field, completed by the party holding the approval, because it is a life-safety decision and not a device setting. The offline case is the design, not the exception: name the state each door takes, who may authorise a manual release, and the reconciliation on return.

Node 6 — Give the project one clock and one event name

Events with two clocks cannot be reconciled, however carefully both are labelled. Name the time source, say how devices are synchronised to it, and say what happens to a record whose timestamp is missing or drifting.

Keep two things apart. The audit log is the record of events with a time and a source. The event memory is the buffer a lock keeps when it cannot reach the server. They are not the same, and the difference is where events disappear. Say which events must survive an outage.

Node 7 — Decide what is written, where it lives, and who

A floor-access record shows who crossed which floor and when, which makes it personal data in most jurisdictions. The record schedule names the fields, the repository, the authorised readers, the export format used for an investigation, and the retention period — a field for the client to complete, not a default the integrator sets.

CONFIRM-WITH-LOCAL-PRIVACY-LEAD: Confirm the retention period for records that show who entered which floor and when, who may read or export them, and who signs the rule.

The reader list matters as much as the retention rule, because support access is where records leak. Say who may open a session, what bounds it, and how it is recorded.

Node 8 — Bind the credential to the floor entitlement

A credential is what a person holds, an identity is the person behind it, and personalisation is the per-person data carried on it. A floor access credential entitlement may live on the credential, in the access controller, in the property system, or in the elevator group controller. The definition names which one, because the answer decides how quickly a role change takes effect and what an auditor can see.

Write the change path too: what happens when a role changes mid-day, what happens when a credential is issued for a floor and then withdrawn, and who carries out each change when the entitlement sits elsewhere.

Node 9 — List the fields you are deliberately leaving open

A definition is finished when every open item has an owner and a question attached to it. This register travels to the supplier and back.

Field to be completedAnswered bySettled before
Floors and zones in scopeClient and site operatorQuotation
Restricted floor schedule per zoneClientQuotation
Interlock sequence per controlled landingParty holding the approvalDesign freeze
Retention period for floor-access recordsClient privacy leadDesign freeze
Authoritative time sourceIntegrator with building systemsDesign freeze
Door state when the link is downSafety approverCommissioning
Manual release authority and procedureClient operationsCommissioning
Fire service and firefighter access routeClient with the fire authorityCommissioning
Sign-off matrix for the nine nodesClientHandover

CONFIRM-WITH-LOCAL-EGRESS-LEAD: Confirm the release of a landing door on an escape route, the sequence between a floor release and an access-controlled landing, and who may authorise a manual release.

CONFIRM-WITH-LOCAL-FIRE-APPROVER: Confirm the firefighter access route through the lift core and the interface to the fire alarm system, and who signs that interface.

Assembling the tree into something that can be signed

Each node is signed by the party that owns it: the journey and scope by the client's operations lead, the authority statement with the party who runs the lifts, the unavailable behaviour with the safety approver, the records rules with the privacy lead. The output is one document with nine sections, one open-items register, and a signature against each node — the elevator and floor access project definition the rest of the procurement draws on.

It is worth pairing this with smart locks for conference rooms. That is the same question elevator and floor access project definition has to answer here.Four documents sit next to this one, each answering a different question. Elevator and Floor Access Requirements Document Template holds the fields this tree produces. Elevator and Floor Access: The Test Plan a Buyer Should Demand tests the result. Security Questions to Ask About Elevator and Floor Access presses on the interface, and Documenting Elevator and Floor Access for Handover and Audit carries the evidence forward. When the link fails in service, Elevator and Floor Access Failure Patterns and How to Recover starts from the symptom.

This article states no certification status for any product, no price, no order quantity, no production lead time and no warranty period, because those are quoted rather than published.

If the tree matches a project you are quoting, attach the nine fields and the register to your request for quotation through request a quote, and put the device behaviour on your own doors with order samples first.

Winkelwagen
Uw ervaring op deze site wordt verbeterd door cookies toe te staan Cookiebeleid
Chat on WhatsApp