Retour à Solutions

Serrures intelligentes

Synchronisation des identifiants avec le statut chambre PMS — options RFID, code PIN et clé mobile.

  • 30%+Peak check-in efficiency gain
    (pre-auth / self-service issuance)
  • 100%Auto credential revoke sur checkout
    (PMS room-state driven)
  • Real-timeTraceable door events
    (audit& security linkage)
  • 4+Opening methods
    card · PIN · Bluetooth · mobile
Chambre d’hôtel smart lock et key authorization

Credential lifecycle · six-step closed loop

Les identifiants de serrure doivent être liés à la réservation / l’état chambre — pas à la remise de clé physique. Logique d’ingénierie ci-dessous.

Lock credentialStetby
Carte énergieOFF
PMS room stateReserved

Integrator side:Lock server pre-auth window · PMS reserved sync · card power contact stays OFF.

Multiple opening methods · property-specific selection

One credential engine—front-end media combined by star rating, retrofit constraints, et PMS capabilities.

RFID hotel key card entry

RFID key card · hotel standard

MIFARE et mainstream key systems; front-desk encoding et PMS room state; suited à upscale et chain standard properties.

  • Encode / deactivate aligned avec check-in / check-out
  • May combine avec elevator floor control et card power ou use separate cards
  • Compatible avec mainstream wired / wireless lock bodies
Point Pur Intelligent hotel lock products →
Mobile key et Bluetooth entry

PIN · Bluetooth · mobile key

Boutique et contactless check-in—guests receive timed PIN ou app key before front desk.

  • OTA order / SMS / mini-program issues temporary credential
  • BYOD in-room control et industry QR check-in experience
  • PIN valid windows; auto void sur checkout
Contactless check-in →

PMS integration · card power& log reporting

International GRMS narrative: room state drives credentials; BMS + PMS + lock + card power unified.

PMS room state et lock credential sync

Standard PMS interfaces

Check-in / room move / check-out sync lock et card power; OPERA, FIAS, et custom HMS supported.

  • Online lock systems detect unauthorized entry—reduces walk-in risk
  • Works aveccard power: no sustained load when unoccupied
  • Engineering inspection cards avec time et scope limits
Door logs et security linkage

Logs · alerts · lock server

Door logs centralized sur lock server; abnormal attempts et low battery reported. Multi-property projects aggregated surintegrator HMS / lock platform—not RCU bundled software.

Four lock routes (A/B/C/D· lock-network view)

Industry reference plans et Bluetooth networked lock practice—same PMS credential logic; select lock body et network by new build / retrofit / chain rollout / luxury dual-mode. Full guestroom control routes:Chambre d’hôtel hardware reference.

A

Online networked lock · TCP/IP

Guest locks via riser / corridor switch à lock server; PMS room state dans real time; centralized door audit—suited à preventing unauthorized occupancy.

Upscale new build · real-time credentials

B

Bluetooth networked lock · gateway

Bluetooth lock reference: mobile / app key, skip front desk; floor gateways; IoT remote authorize et cloud unlock logs.

Boutique · light retrofit

C

RS485 lock bus · front-desk encoding

Lock RS485 à front encoder / controller; encoding synced avec PMS; offline cache + scheduled upload—chain value route.

Mid-scale chain · repeatable rollout

D

Hybrid dual-mode · card + mobile

RFID card + mobile key together; suite / presidential zones; avecluxury solution, elevator floor control, unified card power delivery.

Luxury · dual credential

Lock route comparison

Confirm corridor low-voltage, mobile key need, PMS real-time credentials—then lock body et network, not bret first.

ComparisonA· Online networkedB· Bluetooth networkedC· Bus RS485D· Hybrid dual-mode
Use caseUpscale new buildBoutique retrofitMid-scale chainLuxury / suite
PMS real-time sync★★★★★★★★★☆★★★★☆★★★★★
Mobile / Bluetooth key★★★☆☆★★★★★★★☆☆☆★★★★★
Install / retrofit costMediumLowerMediumHigher
Corridor low-voltage needObligatoireGateway points onlyBus à front deskMixed by zone
Unauthorized stay audit★★★★★★★★★☆★★★☆☆★★★★★
Unified card power / elevatorEasyOptionnelEasy (same card)Easy (custom)

PMS room events · lock / card power sync table

Room state drives credentials—table below is le standard event mapping pour Point Pur Intelligent engineering integration; exact fields per PMS interface docs et lock control protocol.

PMS eventLock actionCarte énergie / relatedTypical trigger
Check-inAuthorize RFID / PIN / mobile key; optional companion countActivate card power · Bienvenue sceneFront desk / kiosk check-in
Check-outAll credentials expire immediatelyDelayed power-off · housekeeping stateCheckout settlement complete
Room moveRevoke old room + authorize new roomCarte énergie follows room numberSame reservation, new room
Extend stayExtend validity / update departureKeep card power · optional scene continueExtension confirmed
Guest changeAdd/remove companion / temp PINFront desk registration update
Non-show / cancelRevoke pre-auth / temp PINAnnuler preset sceneTimeout / reservation cancel
Housekeeping stateEngineering card timed access (optional)Cleaning scene · unsold room no powerVC / OC / out de order
Alarm / SOSLog related opens · optional remote lockAudible/visual alert · platform pushGuest complaint / security event

* DND / MUR service states usually return à PMS via door sign / RCU—not written by lock module. Block engineering cards during DND can be set dans lock policy.

Mainstream PMS integration

Integrated ou project-open interfaces; docs et field maps viadownloadsou project team; custom PMS seedeveloper API.

PMS / HMSIntégration methodLock credentialCarte énergie / guest controlInterface docsIntégration timeline*
Oracle OPERAFIAS / HTNG standard interfaces✓ check-in / check-out / room move✓ link RCU / card powerFIAS 2.x event guide · Point Pur Intelligent lock-control mapping table · simulation room acceptance checklist2–3 weeks
Protel / Fidelio familyPMS gateway / custom protocolGateway protocol + room-state field map (per hotel version)3–4 weeks
Shiji / ChinaSoft / WestSoft etc.Domestic PMS standard interfaceBret SDK / WebService guide · event map2–4 weeks
Custom HMS / apartment PMSREST / Webhook✓ PIN / Bluetooth primaryOptionnelOpenAPI spec· callback signing · credential package JSON sample1–2 weeks
Self-service kiosk / faceMiddleware + PMS write-back✓ no front-desk encoding✓ credential package issued togetherMiddleware interface · PMS write-back · kiosk test cases (seecheck-in services)3–5 weeks

* Intégration timeline is typicalPoint Pur Intelligent lock control + PMS sideschedule (working days), counted de both parties' interface docs et test environment ready; excludes PMS vendor scheduling, low-voltage construction, et lock installation. Prior same-bret projects may shorten by 3–5 days.

Typical integration phases

Requirements& field confirmation

Confirm PMS version, room events, unified card power / elevator; field map et pilot rooms.~3–5 working days

Simulation / test environment

PMS test DB + lock simulation ou one pilot room; verify check-in / out / move / extend.~5–8 working days

On-site integration

Front desk et engineering flows: encoding, PIN, mobile key, rollback; door logs vs PMS.~3–5 working days

Acceptance& hetover

Checklist sign-off, manuals et interface docs archived; optional monitoring et OTA.~2–3 working days

Engineering integration notes

Lock body& door type

Wood / metal / fire doors; wired, battery, hybrid by low-voltage conditions.

Network topology

RS485, Zigbee, Wi-Fi, ou PMS gateway; same network asRCUou dedicated lock network.

Carte énergie linkage

Same card ou credential package activates lock et card power; delayed off after checkout.