Click here for tutorials
Kaba Interface
This interface allows the front desk staff to issue request to encode key cards for guests at check-in time, upon changes to the reservation (date change, room move), issue replacement cards, issue new cards.
Check-in and the Kaba Interface
Upon completion of RDPWin's guest check-in process (or other option that requires the system to prompt for keys to be encoded), the KeyCardRequest form is shown to the user and allows selection of both the number of keys to encode and the encoder to use.
When the room number does not exist in Table RL signifying the room does not
have a Kaba lock installed, the system prompts with the Continue With screen
instead of the Key Card Request screen.
When using the interface protocol, Kaba Web Service, and the user clicks the Submit button, instead of creating a request file, RDPWin communicates directly with the Kaba Web Service.
ATLAS User Name
RDPWin stores an ATLAS user name and password set for each front desk user. This can be stored in Users.dat, WinConfig or some other place.
Kaba Web Service
The URL for the Web service address needs to be stored in RDPWin such as the Program Control Table for KeyCard Interface (Table PL).
Click these links for Frequently Asked Questions or Troubleshooting assistance.
04/05/2010
© 1983-2009 Resort Data Processing, Inc. All rights reserved.