Door Position Contacts for a Hotel Property
This door position contacts hotel case is issued as a bid and spec sheet for system integrators evaluating hotel access-control work. It defines the boundary between the door, its contact, the controller and the property workflows that consume door-state events. Use it with Door Position Contacts for Smart Lock Projects: What Buyers Must Define First and the Door Position Contacts Requirements Document Template before issuing a tender.
Direct answer. Short version — door position contacts hotel case is treated here as door position contacts hotel case first. door-position-contacts comes second. The evidence for door position contacts hotel case is named in the sections below. A door position contacts hotel case treats the handover as the unit of work. door position contacts hotel case decides the interface. door position contacts hotel case is operable on day one only if it does.
This article defines door position contacts hotel case through door position contacts hotel case. The definition of door position contacts hotel case is deliberately narrow. It is non-statutory, and it applies to the market and product being discussed.
- Trace the interface — write down what hands over between lock, door and system at door position contacts hotel case
- Verify the handover — record the sequence that proves door-position-contacts works end to end
- Preserve the trail — store the commissioning evidence with the file for tendering boundary
- Treat this as the door position contacts hotel case sequence, with door position contacts as the reference.
1. Tender Boundary and Contractor Responsibility
The door position contacts hotel case covers survey, point-schedule development, hardware coordination, installation, controller configuration, interface mapping, testing, defect correction and handover. The contractor is responsible for showing how each requirement will be delivered rather than merely naming a product family. The model this procurement ends up comparing is the SLK-002 Keypad RFID Lock for Guesthouses — check the dated product page for the specific SKU.
The tender package must separate four workstreams: The comparable treatment of the same question sits in Door Position Contacts Cost and Effort Drivers Without Quoting Prices.
- Physical door work: mounting position, cable route, switch condition, frame movement and local equipment constraints.
- Control work: input assignment, event mapping, time source, state retention and configuration control.
- Property-system work: room or area mapping, exception handling, operational ownership and interface boundaries.
- Acceptance work: witnessed tests, recorded results, closure of defects and delivery of the final configuration record.
The hotel remains responsible for deciding which operational events matter and who receives them. The integrator remains responsible for the configured interface between the contact and that decision. The fire or egress specialist, where applicable, remains responsible for the approved release strategy. These boundaries should appear in the tender rather than being inferred later.
2. Hotel Door Classes That Set Different Reporting Duties
A single hotel may contain doors with materially different reasons for monitoring. The door position contacts hotel case must classify each door before the bidder selects a design. Use the following classes as a starting schedule, then replace them with project-specific door classes.
| Door class | Typical monitoring purpose | Required state reporting | Boundary that must remain explicit |
|---|---|---|---|
| Guest room | Room-status service or operational notification | Open and closed | The event does not identify the occupant, prove occupancy or establish why the door opened |
| Connecting or suite door | Coordination between connected spaces | Open and closed | A change in one internal door does not by itself describe movement through another door |
| Public entrance | Arrival, opening-hours or exception workflow | Open and closed | A valid opening and an abnormal opening require separate classification rules |
| Staff-only door | Operational awareness for restricted areas | Open and closed | Authorization remains the credential system’s decision, not the contact’s decision |
| Service or maintenance door | Activity monitoring outside guest-facing areas | Open and closed | Late opening may be an exception, while the cause remains unconfirmed |
| Back-of-house door | Operational and security-event workflow | Open and closed, including fault reporting where available | Food, laundry, plant and storage areas may need different response ownership |
| Monitored egress or fire-interface door | Approved monitoring interface | Open and closed without duplicating the release function | Door monitoring, request-to-exit signalling and alarm release remain separate functions |
The required field survey should include door swing, frame, hinge, latch, existing hardware, cabling space and local equipment. The Office Smart Lock Site Survey provides a useful format for recording physical conditions, while Smart Lock Retrofit Site Survey is relevant where an existing door set is being retained. Neither survey replaces a project-specific point schedule.
3. Minimum Signal, State and Interpretation Schedule
A door position contact, or DPS, is a switch that reports whether a door is open or closed. It reports a state, not a cause. The input does not prove who opened the door, whether an opening was authorized, whether the latch is engaged, whether the lock is secured or why the condition occurred.
DPS open closed reporting shall be mapped through the controller into named states. The controller owns the controller door state; the contact supplies the physical input, and the property system decides what that state means for its workflow. The tender must not leave “door sensor” as the final event name because operational teams need a definition they can use consistently.
| Signal condition | Controller representation | Permitted record | Conclusion that must not be added |
|---|---|---|---|
| Closed | Closed state | Door ID, state, controller time and event source | The door is locked or the occupant has departed |
| Open | Open state | Door ID, state, controller time and event source | Someone entered, a credential was used or the room is occupied |
| Open beyond an approved threshold | Held-open exception | Door ID, threshold policy, controller time and event source | The cause is intrusion, a staff visit or a mechanical fault |
| Input fault or invalid circuit | Unknown or fault state | Door ID, fault type where detectable, time and source | The door is physically open |
| No fresh update during supervision | Unknown or stale state | Door ID, last valid time and fault source | The last recorded state remains current |
A wired door position switch is the baseline physical implementation contemplated by this schedule. The bidder must confirm mounting method, cable type, conductor allocation, route, termination method and interference with the door operation after the site survey. Where the selected input architecture can detect a broken or shorted line, that condition should be distinguishable from a normal open or closed state.
The tender must also specify what happens during a change of state. The expected sequence is a physical change, an input change at the controller, a controller-stamped event, delivery to the configured platform and an operational response where required. A door held manually in one position does not generate repeated events unless the selected design and approved policy define that behavior.
4. Access Control Point Schedule Required in the Bid
The access control point schedule is the contractual index between physical doors and logical workflows. Each line must be traceable to an as-built drawing and to controller configuration. A room number or area name alone is insufficient when the property contains duplicate room identifiers, suites, service doors or multiple door leaves.
| Required schedule field | Bidder response |
|---|---|
| Project door reference | Unique physical identifier tied to the final drawing and asset register |
| Door class and area | Guest, public, staff, service, back-of-house or other approved classification |
| Controller and input | Exact controller location, input designation and wired interface method |
| Electrical arrangement | Contact type, cable route, supervision method and field-termination notes |
| State dictionary | Closed, open, held open, fault and unknown labels used by the controller |
| Event definition | Event code, source, direction and whether the event represents a change or a level |
| Time ownership | Controller clock source, timestamp meaning and platform receipt-time treatment |
| Property-system mapping | Room, area or workflow destination, including local API or cloud API boundary |
| Failure behavior | Required behavior for network, server, controller and input-fault conditions |
| Test and evidence | Acceptance method, expected result, witness role and retained evidence |
The bidder should provide a sample line for each door class and identify every assumed field. Gaps must be marked as clarification items rather than silently completed. The final schedule also belongs in the door-position-contacts asset register so maintenance teams can connect an alarm at the door to its approved response.
Where a guest-room event feeds a property-management workflow, the room identifier is a mapping key, not proof of occupancy. The property-system owner must approve the mapping and the access-control integrator must demonstrate that an event from one physical door cannot be reassigned to another room by configuration error.
5. Event Chain and Decision Ownership
The door position contact sends an electrical state to a controller input. The controller holds the door state, applies its clock and creates the event record. The receiving system may then alert staff, update a workflow or queue an exception. The contact itself does not send credentials, authorize entry or command a release.
flowchart LR
A[Door movement] --> B[Door position contact]
B --> C[Controller input]
C --> D[Controller door state]
D --> E[Event workflow]
D --> F[Exception queue]
E --> G[Property and security teams]
F --> H[Maintenance owner]
The lock reports the state; the system decides what the state means. This wording should be applied consistently in drawings, configuration guides and operator training. In practice, a door may be opened by a guest, employee, contractor, housekeeping team or an approved emergency procedure. The workflow can classify the event, but the physical input cannot establish the actor.
The tender must name the owner for every transition in the chain. The door supplier or installer owns physical fit and termination. The system integrator owns controller mapping and event delivery. The hotel or property operator owns the response rule and escalation path. The platform owner owns uptime, identity management and record availability. Where several parties touch one interface, the contract should identify the party that opens and closes a change ticket.
6. Degraded Modes and Recovery Requirements
The offline case is the design, not the exception. The bidder must describe the door-local, controller-local and platform-local behavior separately. In a centralized arrangement, the controller and its local records remain part of the access-control system while the server is unavailable. In a standalone arrangement, more decisions remain at the door, but the device configuration still needs controlled ownership and revision history.
| Failure condition | Required local behavior | Record and recovery requirement | Named owner |
|---|---|---|---|
| Contact wiring opens, shorts or becomes intermittent | Avoid presenting an unsupported door state as reliable | Preserve the last valid state, expose a fault where detectable and identify the affected line | Installer for wiring; controller team for input |
| Controller loses local power | Restore from the approved power strategy and rebuild the controller door state from the designed configuration | Document boot results, state recovery and any lost event-memory content | System integrator |
| Network connection is unavailable | Continue the approved door-local function and buffer events according to the selected architecture | Identify the local API or cloud API boundary, buffer capacity and reconciliation procedure | Platform owner |
| Property-management server is unavailable | Keep the access-control function independent unless an approved design says otherwise | Preserve event memory and report the upstream outage without changing the physical input | Property-system owner |
| Controller or server is restored | Reconcile buffered events in their original sequence | Flag unresolved gaps and prevent silent replacement of missing events | System integrator |
Event memory is the buffer that a device keeps when it cannot reach the server. An audit log is the retained record of events with a time and source. They are not interchangeable: event memory may be temporary, while the audit log has defined access and retention rules. The recovery procedure must show what happens when the buffer is full, when timestamps differ and when a restored device has been assigned a new identity.
The field response should be based on the Door Position Contacts Failure Patterns and How to Recover. A fault ticket should identify the door, controller, input and last confirmed state rather than simply reporting that the sensor failed.
CONFIRM-PER-SUPPLIER: For every proposed lock, controller and interface component, provide the dated product page for the specific SKU and written evidence for contact input method, event data, event-memory behavior, offline operation and API boundary. Do not infer an unstated capability from a product family name.
7. Time, Records and Guest-Access Data Boundaries
The controller should own the event timestamp because it observes the input. The platform receipt timestamp is a separate field. A usable record names the event source, physical door, controller, state, controller time, time quality, event identifier and any platform receipt time. The platform must not replace the controller timestamp with its own clock after synchronization has occurred.
The bidder must document clock ownership, synchronization source, time-zone treatment and behavior after a controller restart. When clocks disagree, the receiver should preserve both values or mark the discrepancy rather than silently changing the source time. This allows operations staff to distinguish a door event from a delayed platform delivery.
A door-open record does not contain a person’s identity. Combining it with credential, guest, room-assignment or video records can create personal-data consequences, so that combination should be specified separately. The tender must state where the audit log lives, who administers it, who can export it, how retention is configured and whether a guest can receive an event record.
CONFIRM-WITH-LOCAL-HOTEL-PRIVACY-LEAD: Confirm which room-access events may be retained, who may view them, how long they remain and the approved response to an access request. Record any relationship between door state and occupancy as a per-property design question.
8. RTE, Egress and Fire-Alarm Separation
A request to exit, or RTE, is the signal from an exit device indicating operation from the escape side. It is not a release command. Release on the escape side is the default behavior of the exit device, and the RTE signal tells the system that the operation happened. A DPS cannot be used as a substitute RTE input.
The fail-safe or fail-secure state of an electric lock is selected according to the door’s role and the project approval, not according to the door position contact. The tender should keep door monitoring, free-egress hardware, electric locking, RTE reporting and fire-alarm interfaces as separate schedule sections. Combining them in one drawing without clear interfaces creates false assurance about both monitoring and release.
An open-door event on an egress door must not be described automatically as an alarm, and a fire-alarm interface must not be described as a door-position source. Where monitoring and release interfaces meet, the responsible specialist defines the sequence and the evidence required for acceptance.
CONFIRM-WITH-LOCAL-FIRE-EGRESS-APPROVAL: Identify the approving authority, release sequence, monitored-door scope and evidence required for each egress or fire-interface door. This is a per-project question, and the door position contact does not decide release.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm the jurisdiction-specific requirements that apply to this property and submit the evidence requested by the approving authority.
9. Hotel Commissioning Acceptance Tests
Hotel commissioning acceptance tests must demonstrate both the physical input and the complete event chain. A bench test of the contact is not sufficient. Each approved door class should be represented in the test plan, and any sampling method should be agreed with the hotel before testing begins.
| Test | Method | Pass condition | Retained evidence |
|---|---|---|---|
| Installed-state verification | Operate the door through its normal range and inspect mounting and wiring | Contact follows the defined closed and open positions without preventing door operation | Signed physical checklist and photograph |
| Closed-to-open event | Move the door from closed to open and then close it | Correct event source, door reference, state and controller timestamp appear in the receiving workflow | Event-detail screen and test record |
| Open-to-closed event | Return the door to closed | The workflow changes to the defined closed state without creating a duplicate event | Event-detail screen and test record |
| Held-open exception | Hold the door open beyond the approved policy threshold | The approved exception appears once for the event and remains associated with the correct door | Configuration extract and event record |
| Input-fault test | Use the approved test method for the installed supervision arrangement | A line fault is identified as fault or unknown rather than silently reported as a normal door state | Fault record and controller capture |
| Controller restart | Restore power to the selected controller | The configured state and reporting behavior return as designed, with any event-memory effect documented | Commissioning log |
| Network interruption | Disconnect the approved network path | Door-local operation follows the submitted degraded-mode design and events remain recoverable | Before-and-after event comparison |
| Platform restoration | Restore the upstream connection | Buffered events are reconciled, gaps are flagged and no duplicate workflow action is created | Recovery log |
| Clock validation | Compare controller, platform and reference time using the approved method | Source time and receipt time remain distinguishable and the time source is documented | Clock test sheet |
| Room or area mapping | Trigger an event on the selected physical door | The event reaches only the approved room or area mapping | Property-system screenshot and schedule line |
| Operational response | Raise the approved exception | The named recipient receives the event and follows the agreed response procedure | Call log, ticket or dispatch record |
A failed test remains open until the cause is corrected and the affected test is repeated. Related tests should be repeated when a correction could alter configuration, wiring, timing or mapping. Acceptance should be based on the installed configuration and submitted evidence, not on a supplier demonstration performed away from the property.
10. Responsibility Matrix and Handover Package
The responsibility matrix must follow the event chain rather than using “supplier” as an indefinite role. Where a lock supplier, electrical contractor, access-control integrator and property-system vendor are separate entities, each interface needs a named owner.
| Activity | Physical or hardware party | System integrator | Hotel operations or security | Approval owner |
|---|---|---|---|---|
| Site survey and door-fit record | Prepare and sign the record | Review integration constraints | Confirm operational use | Accept scope |
| Point schedule and event dictionary | Supply physical facts | Produce logical mapping | Decide response meaning | Approve schedule |
| Contact installation and termination | Install, inspect and test | Witness input operation | Receive operational briefing | Accept workmanship |
| Controller configuration | Supply interface requirements | Configure and back up | Authorize operational rules | Approve change |
| Property-system mapping | Provide supported interface facts | Configure approved mapping | Own room and area data | Approve test plan |
| Event and exception validation | Support physical diagnosis | Own end-to-end test | Witness and exercise response | Sign acceptance |
| Maintenance handover | Supply as-built and component records | Supply logic and configuration record | Assign service ownership | Accept support route |
The handover package must include the final point schedule, as-built door and input drawings, controller configuration export, event dictionary, clock and time-source record, interface documentation, test sheets, defect log, approved exception list and named maintenance contacts. It should also identify unresolved items that were accepted as operational limitations, together with their owners and review points.
The handover format should follow Documenting Door Position Contacts for Handover and Audit. The hotel should be able to trace every configured door-state alert back to its physical door without relying on a technician’s personal memory or an undocumented spreadsheet.
11. Bidder Response and Deviation Schedule
The bidder should return the point schedule, technical narrative, interface evidence, test plan, responsibility matrix and deviation list as one coordinated package. A change to one schedule line must be reflected in the drawings, controller configuration, event dictionary and test script.
| Bid area | Mandatory response | Evidence expected |
|---|---|---|
| Door classification | State the classes used and the reason for each class | Marked door schedule |
| Contact and input design | Describe the physical and electrical arrangement | Survey basis and interface drawing |
| State and event model | Define closed, open, held open, fault and unknown handling | Controller configuration extract |
| Property-system interface | Name the local API or cloud API boundary and event mapping | Written interface description |
| Degraded operation | Explain behavior for each approved failure condition | Failure-mode test sequence |
| Time handling | Identify the event clock, synchronization and receipt-time treatment | Clock configuration record |
| Records and access | State where the audit log resides and who administers it | Access-control and retention matrix |
| Acceptance | Provide a test per door class plus exception handling | Witnessable test script |
| Product evidence | Address every proposed SKU individually | Dated product pages and supporting documents |
| Deviations | Identify omissions, substitutions and unresolved assumptions | Numbered deviation schedule |
Silence should not be treated as a design decision. Every proposed substitution must identify the affected schedule line, operational effect, test change and handover document. Where the bidder cannot yet confirm a capability, the bid should carry an open clarification rather than an implied promise.
It is worth pairing this with the smart locks for factories. That is the same question door position contacts hotel case has to answer here.
12. Procurement Decision Schedule and Release Check
The final decision schedule should prevent a technically workable contact from being paired with the wrong operating model. Comparing options forces the buyer to identify what must be true on both sides of the interface.
| Decision | Option A | Option B | Selection rule | Required evidence |
|---|---|---|---|---|
| Position source | Dedicated physical contact at the door | Position information provided by another installed device | Choose the source that can be verified at the installed door without assuming an unstated product capability | Survey, interface drawing and dated product-page evidence |
| State authority | Controller holds the authoritative door state | Device holds more of the state and exports it | Define who maintains state through restart, network loss and configuration change | Controller and device responsibility record |
| Property interface | Local API boundary | Cloud API boundary | Select the boundary required by the property architecture and operating model | Interface specification and failure behavior |
| Upstream outage | Local event memory and later reconciliation | No retained event sequence | The selected option must be supported by evidence; absence of retained events must be visible | Capacity evidence and recovery test |
| Operational exception | Named team receives and acts on the event | Event is displayed without an assigned response | Prefer an assigned response owner unless the hotel approves passive handling | Dispatch rule, roster and escalation path |
Release the tender package only after the door classes, point schedule, event dictionary, degraded modes, clock owner, record-access rules, acceptance tests and approval questions are complete. The supplier response should then be assessed against the same baseline, with every deviation visible. This creates a hotel bid package in which the hardware, controller, property system and operating teams share one definition of the door state and one accountable route from fault detection to corrective action.
The commercial step that follows is to request a quote.

