Door position contacts handover documentation: A field runbook for writing down every door position contact at handover, so a later controller change.

Opublikowano: lis 22, 2024

Documenting Door Position Contacts for Handover and Audit

Documenting Door Position Contacts for Handover and Audit

An integration failure is usually a sequence failure, so door position contacts handover documentation is traced here from handover to commissioning. Three years after a building changed hands, the access controller on the fourth floor was swapped. The replacement was fitted by a technician who had never worked on that floor, and its screen offered inputs named for zones and auxiliaries. Two doors reported into the wrong inputs: one read permanently open, another permanently closed while it stood shut. The handover pack held a door schedule and a controller schedule, and nothing that said which input belonged to which door.

Direct answer. In brief, this article covers door position contacts handover documentation from door position contacts handover documentation to door-position-contacts. It states what to confirm about door position contacts handover documentation on the dated product page where a figure is involved. A door position contacts handover documentation is an integration guide. Every component has an obligation to the next. door position contacts handover documentation is the first one tested for door position contacts handover documentation.

  • Draw the interface — write down what hands over between lock, door and system at door position contacts handover documentation
  • Exercise the handover — record the sequence that proves door-position-contacts works end to end
  • Archive the record — store the commissioning evidence with the file for two readers one sheet
  • This is the sequence door position contacts handover documentation has to follow, anchored on door position contacts.

The contact itself was never at fault. A door position contact is a switch that reports open or closed; it reports a state, not a cause. What was missing was the written record tying a physical switch on a named leaf to a named input on a named controller. That record is door position contacts handover documentation, and it is the only part of the contact layer that survives the people who built the system.

Two readers, one sheet

Nothing is binding until a supplier.

Write for the first reader and the second gets an appendix; write for the second and the first gets a library. The test that separates them is short: could a competent stranger rebuild the mapping from the sheet alone, without telephoning anybody? The record set that answers that starts with one card per door, filled in while the installer is still on site. The earlier published note on this is Hotel Smart Lock System Integrator Guide. The product family this applies to is the smart door locks.

The contact record card

One card per door, because the door is the unit that can be handed over, replaced, tested and audited.

Card fieldWhat it statesSourceIf left blank
Door referenceThe identifier used for that openingThe agreed door scheduleAn input cannot be tied back to a door
Leaf, type, actuation memberWhether the leaf swings or slides, and what moves the switchSite survey and observationA contact that never actuates looks like a working one
Controller, input, panel labelThe controller, the terminal, the name a technician seesController configuration read on siteThe state cannot be traced to a source
Rule on the stateThe system rule that turns a state into an eventThe system ownerA raw state is later read as an alarm
Captured by and onThe name and date of the person who filled the cardThe capture sessionThe card cannot serve as evidence

A card is not a specification and does not replace one: it is the as-built counterpart, describing the doors as they were actually installed.

The capture session at the door

Fifteen minutes per door, and the routine is the same every time.

  • Close the door, let the system settle, record the baseline state.
  • Open it under the approved method, watch the input change, write down the label.
  • Close again and confirm the input restores.
  • Open once more and note the event raised, or that none is.
  • Write the contact type, actuation member and input address on the card.

The last step is the one that gets skipped. Anyone can describe a contact in the abstract; few can say what moves it on that door, and the record that saves a fault call names that member.

The mapping sheet that decides the next controller change

The second artefact is the mapping sheet: the card list viewed across the building, and what a controller replacement is worked from.

Door referencePhysical contactController inputPanel labelRule on the open state
Main entranceConcealed switch in the frame rebateTerminal 3, controller AZone 3Held-open timer at the approved threshold
Tenant corridorSurface switch on the leafTerminal 7, controller AAux 2Event logged, no alarm
Service stairConcealed switch in the frame rebateTerminal 11, controller BZone 5Forced-open alarm by the system rule

When a controller is replaced, this sheet is the work order, and the replacement arrives at the same end state as the original.

erDiagram
    DOOR_CARD ||--|| CONTACT_ENTRY : describes
    DOOR_CARD }o--|| CONTROLLER_INPUT : maps_to
    CONTACT_ENTRY ||--|| CONTROLLER_INPUT : actuates
    CONTROLLER_INPUT ||--o{ POSITION_EVENT : yields
    POSITION_EVENT }o--|| RULE_SET : interpreted_by
    POSITION_EVENT }o--|| CLOCK : stamped_by
    DOOR_CARD ||--o{ HANDOVER_PACK : released_in

The sheet is also where the layer under the contact shows up. Wiring conventions such as Wiegand, and specified bidirectional protocols such as OSDP, decide what a controller can offer a contact input: whether it can be supervised and whether the state arrives as a live level or a stamped event. Whether a given model implements any of them is a per-model question, so confirm on the dated product page for the specific SKU before the sheet is signed.

One more line belongs on the sheet: whether the rule lives in the controller or in the management platform, since that decides where a later configuration change must be made.

What a contact state cannot be asked to prove

The record is precise about what it saw and silent about everything else: a contact state does not say who opened the door, whether the opening was authorised, or why the door stood open. It is not a request to exit signal, which tells the system that the door was operated from the escape side and is not itself a release command. It says nothing about what the lock does when power is removed, because whether a door fails safe or fails secure is decided by the door's role and its approval, not by the product.

The rule that turns a state into an event lives elsewhere: in the controller, in the platform, or in the client's approved rule set. The contact reports the state; the system decides what the state means, and the card names where that decision is made. A card that says only that a door reported open is half a record, and a later reader will take it for an alarm.

Clocks, event memory, and the record that survives an outage

Two clocks make any comparison impossible, so the sheet names the authority: one stamps the state at the controller, another stamps the event at the platform. When they disagree, every reconciliation becomes an argument about whose clock is right.

The sheet also separates two things often merged: the audit log, a record of an event with a time and a source, and the event memory, the buffer a lock keeps when it cannot reach the server. The gap between them is where events are lost, so naming where events are stored does not answer what happened to the states recorded while the network was down.

Name the degraded case in full: the network unavailable, the controller unreachable, the server down. For each, the sheet says what the door does, what the record does, what the operator sees, and who closes the mismatch. The offline case is the design, not the exception, and whether the state lives on the device or on a server is a per-project answer on the sheet.

Who may read the record, and how long it

A door position record is small, and it is not neutral. The open state of a staff door, joined with a time and a door reference, describes someone's movement through a building, and it names a person only where it is joined with the identity behind the credential.

The sheet must not invent a retention period or a readership list. It records who answers the question, where the answer is filed, and who approved it.

CONFIRM-WITH-LOCAL-DATA-PROTECTION-ADVISER — which retention period applies to door position and access event records in the jurisdiction where the building stands, who approves it, and which role may read an export.

CONFIRM-WITH-LOCAL-FIRE-SAFETY-AUTHORITY — which authority signs off on the release behaviour of the door assembly, and whether the assessment covers lock, exit device and closer together.

Where an answer has not arrived, the sheet carries a placeholder instead of a guess: retention period — to be filled; export readership — to be filled; approval reference — to be filled. A placeholder is checkable; a guessed duration is relied on for years.

Four signatures on the contact handover sheet

SignatureWhat the signer acceptsEvidence attached
Commissioning engineerThe cards were filled at the doors namedCapture notes and the dated card set
Controls integratorInputs, labels and rules match the installed configurationExported configuration and mapping sheet
Client technical ownerThe degraded behaviour and the offline case were exercisedOutage test record and result
Client record ownerThe readership of the record and its retention answerAdviser response and approval

Each signature carries a version number and a date: a sign-off without a version accepts a system nobody described, and a version without a date cannot be ordered against the pack.

Ownership is worth one line before the signatures are collected: who supplies the contact record, who installs it, who owns the door after handover, and who maintains the mapping may be four answers belonging to four organisations, a split worked through in Who Owns Door Position Contacts: Supplier, Integrator or Client.

The read-back test a month after handover

Thirty days after the handover, someone who did not build the system takes the pack and does three things.

  • Rebuild one door's mapping on a spare controller from the sheet alone, then compare the result with the card.
  • Reconstruct one door-open event, and confirm that the rule on the card is the rule that was applied.
  • Find the source of one door-held-open alarm, and follow it back through the sheet to a physical contact.

If any of the three fails, the failure belongs to the documentation rather than the hardware, and the card is corrected while the people who built the system are still reachable. Door Position Contacts: The Test Plan a Buyer Should Demand sets out the same structure for a purchase.

It is worth pairing this with smart lock engineering drawing checklist. That is the same question door position contacts handover documentation has to answer here.

What to request from the lock supplier before the site is signed

The supplier's part in the handover record is small and specific. For each SKU on the project, ask for the dated product page reference, the contact input type or types the model offers, the reader-to-controller wiring convention, and the documented behaviour of the input when the door is held or its wiring is disturbed.

The same question is worked through in more detail in smart lock door compatibility matrix. That is the same question door position contacts handover documentation has to answer here.The wider specification behind the contact layer belongs in the requirements document that precedes the site work: start with Door Position Contacts Requirements Document Template. Where the contact sits inside a larger scheme, Door Position Contacts for Smart Lock Projects: What Buyers Must Define First argues that case, while Door Position Contacts Failure Patterns and How to Recover covers recovery after a failure.

CONFIRM-PER-SUPPLIER: for the specific SKU under evaluation, provide the dated product-page reference for the contact input type, the reader-to-controller wiring convention, the owner of each documented dependency, and what changes and who is notified when it changes.

The record set that answers the question this runbook opens with is what a supplier hands over with the doors and what the client keeps: door position contacts handover documentation, shaped as one card per door, one mapping sheet, one signature page, and a line for every answer still to be filled. Ask for it during evaluation.

The commercial step that follows is to request a quote.

Twój koszyk
Twoje doświadczenie na tej stronie zostanie poprawione dzięki zezwoleniu na pliki cookie Polityka plików cookie
Chat on WhatsApp