Credential sync with PMS room status — RFID, PIN and mobile key options.
Lock credentials should bind to reservation / room state—not physical key handoff. Core engineering logic below.
Integrator side:Lock server pre-auth window · PMS reserved sync · card power contact stays OFF.
Integrator side:Check-in issues card/PIN/mobile key · card power ON · Welcome scene triggered.
Integrator side:Companion/inspection timed access · low battery to engineering · door logs written in real time.
Integrator side:Batch revoke old room · migrate new room · driven by PMS room-move event.
Integrator side:Instant check-out revoke · delayed card-power off · enter clean/VC state.
Integrator side:Audit log archive · abnormal open alerts · optional security platform.
One credential engine—front-end media combined by star rating, retrofit constraints, and PMS capabilities.
MIFARE and mainstream key systems; front-desk encoding and PMS room state; suited to upscale and chain standard properties.
Boutique and contactless check-in—guests receive timed PIN or app key before front desk.
International GRMS narrative: room state drives credentials; BMS + PMS + lock + card power unified.
Check-in / room move / check-out sync lock and card power; OPERA, FIAS, and custom HMS supported.
Door logs centralized on lock server; abnormal attempts and low battery reported. Multi-property projects aggregated onintegrator HMS / lock platform—not RCU bundled software.
Industry reference plans and Bluetooth networked lock practice—same PMS credential logic; select lock body and network by new build / retrofit / chain rollout / luxury dual-mode. Full guestroom control routes:Guestroom hardware reference.
Guest locks via riser / corridor switch to lock server; PMS room state in real time; centralized door audit—suited to preventing unauthorized occupancy.
Upscale new build · real-time credentials
Bluetooth lock reference: mobile / app key, skip front desk; floor gateways; IoT remote authorize and cloud unlock logs.
Boutique · light retrofit
Lock RS485 to front encoder / controller; encoding synced with PMS; offline cache + scheduled upload—chain value route.
Mid-scale chain · repeatable rollout
RFID card + mobile key together; suite / presidential zones; withluxury solution, elevator floor control, unified card power delivery.
Luxury · dual credential
Confirm corridor low-voltage, mobile key need, PMS real-time credentials—then lock body and network, not brand first.
| Comparison | A· Online networked | B· Bluetooth networked | C· RS485 bus | D· Hybrid dual-mode |
|---|---|---|---|---|
| Use case | Upscale new build | Boutique retrofit | Mid-scale chain | Luxury / suite |
| PMS real-time sync | ★★★★★ | ★★★★☆ | ★★★★☆ | ★★★★★ |
| Mobile / Bluetooth key | ★★★☆☆ | ★★★★★ | ★★☆☆☆ | ★★★★★ |
| Install / retrofit cost | Medium | Lower | Medium | Higher |
| Corridor low-voltage need | Required | Gateway points only | Bus to front desk | Mixed by zone |
| Unauthorized stay audit | ★★★★★ | ★★★★☆ | ★★★☆☆ | ★★★★★ |
| Unified card power / elevator | Easy | Optional | Easy (same card) | Easy (custom) |
Room state drives credentials—table below is the standard event mapping for PurePoint Smart engineering integration; exact fields per PMS interface docs and lock control protocol.
| PMS event | Lock action | Card power / related | Typical trigger |
|---|---|---|---|
| Check-in | Authorize RFID / PIN / mobile key; optional companion count | Activate card power · Welcome scene | Front desk / kiosk check-in |
| Check-out | All credentials expire immediately | Delayed power-off · housekeeping state | Checkout settlement complete |
| Room move | Revoke old room + authorize new room | Card power follows room number | Same reservation, new room |
| Extend stay | Extend validity / update departure | Keep card power · optional scene continue | Extension confirmed |
| Guest change | Add/remove companion / temp PIN | — | Front desk registration update |
| No-show / cancel | Revoke pre-auth / temp PIN | Cancel preset scene | Timeout / reservation cancel |
| Housekeeping state | Engineering card timed access (optional) | Cleaning scene · unsold room no power | VC / OC / out of order |
| Alarm / SOS | Log related opens · optional remote lock | Audible/visual alert · platform push | Guest complaint / security event |
* DND / MUR service states usually return to PMS via door sign / RCU—not written by lock module. Block engineering cards during DND can be set in lock policy.
Integrated or project-open interfaces; docs and field maps viadownloadsor project team; custom PMS seedeveloper API.
| PMS / HMS | Integration method | Lock credential | Card power / guest control | Interface docs | Integration timeline* |
|---|---|---|---|---|---|
| Oracle OPERA | FIAS / HTNG standard interfaces | ✓ check-in / check-out / room move | ✓ link RCU / card power | FIAS 2.x event guide · PurePoint Smart lock-control mapping table · simulation room acceptance checklist | 2–3 weeks |
| Protel / Fidelio family | PMS gateway / custom protocol | ✓ | ✓ | Gateway protocol + room-state field map (per hotel version) | 3–4 weeks |
| Shiji / ChinaSoft / WestSoft etc. | Domestic PMS standard interface | ✓ | ✓ | Brand SDK / WebService guide · event map | 2–4 weeks |
| Custom HMS / apartment PMS | REST / Webhook | ✓ PIN / Bluetooth primary | Optional | OpenAPI spec· callback signing · credential package JSON sample | 1–2 weeks |
| Self-service kiosk / face | Middleware + PMS write-back | ✓ no front-desk encoding | ✓ credential package issued together | Middleware interface · PMS write-back · kiosk test cases (seecheck-in services) | 3–5 weeks |
* Integration timeline is typicalPurePoint Smart lock control + PMS sideschedule (working days), counted from both parties' interface docs and test environment ready; excludes PMS vendor scheduling, low-voltage construction, and lock installation. Prior same-brand projects may shorten by 3–5 days.
Confirm PMS version, room events, unified card power / elevator; field map and pilot rooms.~3–5 working days
PMS test DB + lock simulation or one pilot room; verify check-in / out / move / extend.~5–8 working days
Front desk and engineering flows: encoding, PIN, mobile key, rollback; door logs vs PMS.~3–5 working days
Checklist sign-off, manuals and interface docs archived; optional monitoring and OTA.~2–3 working days
Wood / metal / fire doors; wired, battery, hybrid by low-voltage conditions.
RS485, Zigbee, Wi-Fi, or PMS gateway; same network asRCUor dedicated lock network.
Same card or credential package activates lock and card power; delayed off after checkout.
Developer APIfor self check-in, third-party apps, custom HMS UI.
Updates on RCU controllers, smart panels and engineering documentation.
Product updates, project references and industry news by email.
Wiring diagrams, BOM lists, Modbus/API docs and field guidance.
