...
The NETx BMS Server provides the opportunity to integrate event information from Kaba online door lockshotel room status information from an Infor Hotel Management System (HMS). The following figure shows how the integration has to be done.
Kaba door locks are using a wireless communication protocol which is based on ZigBee. In order to retrieve information like door events, ZigBee/IP hubs are required. These hubs are provided by Kaba and have the aim to translate ZigBee packets into IP packets for the local area network (LAN). Depending on the project multiple ZigBee hubs are needed.
The events are centrally collected by the Kaba server software. This software package provides an interface called Messenger LENS web service interface. This interface provides the opportunity to send events via push notifications to third-party software. In detail, the Kaba software acts as a web service client that sends web service requests to our NETx BMS Server which in turn acts as web service server. The communication protocol itself is based on SOAP web servicesThe Infor HMS provides a standardized interface based on the SOAP protocol which provides a two-way communication between the NETx BMS Server and the Infor HMS to synchronize status of hotel rooms and receive updates such as check in, check out, and room move.
On NETx BMS Server startup, the current status of all configured rooms is synchronized to our system. Once the Infor plugin has been started, the Infor HMS notifies our system when on of the following actions occur:
- Room Check In (101)
- Room Check Out (102)
- Room Move (103 => 104)
The NETx BMS Server keeps track of the room status within the item tree.
Installation
The driver is implement implemented as a plugin for the NETx BMS Server. Therefore, it has to be installed via the Extension Manager. To do so, stop the NETx BMS Server and open the Extension Manager via the BMS Studio using the menu "Extensions". Select the "KabaInfor" interface and press install as shown in the following screenshot:
...
After having installed the interface, restart the NETx BMS Studio.
Integration steps
First, the Messenger LENS web service interface has to be configured. Open a web browser and open the login screen of the Messenger LENS web interface. Within the http URL, use the IP address of the PC where the Kaba software is running.
Afterwards, select the "Configuration" tab, select "Group Permissions" and add a new group permission. Within the wizard, go through step 1 - 3 and select the events and locks that you want to receive within the NETx BMS Server. Within step 4, select "Allow User's Web Service" and enter the following URL (replace <IP BMS Server> with the IP address of the PC where the NETx BMS Server is running and choose a free port (e.g. 6005):
| No Format |
|---|
http://<IP BMS Server>:<Port>/ |
The following screenshot shows an example.
Finish the configuration by going through the remaining steps 5 - 7.
Afterwards, change to the tab "Operations", select "Subscription" and add a new subscription. Select the events, the user and the locks. Within the last step (step 4) of the wizard, "Notify me on my Web server" should be selected and the web service URL should be shown.
As next, open the BMS Studio. First, configure the communication port that you have enter within the web service URL. This can be done by selecting "Driver Configuration" within the menu "Modules" -> "Kaba".
...
Basic
Once the Infor plugin has been successfully installed, you should see a menu entry "Infor" within the menu "Modules".
To configure how to connect to the Infor HMS and vice versa, click the "Configuration ..." entry within "Modules" => "Infor".
Parameters (the yellow highlighted parameters are MANDATORY for the Infor Plugin to work properly)
| Parameter | Description | Example | Note |
|---|---|---|---|
| NETx Infor endpoint | The NETx BMS Server endpoint to listen for incoming requests from the Infor HMS | http://192.168.1.100:5055/infor | |
| Infor HMS endpoint | The Infor HMS endpoint to send outgoing requests from the NETx BMS Server. | http://192.168.1.101:5055/netx | Please request this endpoint from the Infor HMS operator and enter it accordingly |
| Infor HMS Hotel Code | The identifier of the controlled hotel | HMS01 | Please request this endpoint from the Infor HMS operator and enter it accordingly |
| Request timeout | The request timeout in seconds | 60 | Optional |
Rooms
For the NETx BMS Server to know which rooms need be tracked, you have to provide some information regarding the room definitions.
You should be able to export this information from the Infor HMS and import it to the NETx BMS Studio so that you don't have to enter it manually.
To do so, click the "Room definitions" menu entry within the "Modules" => "Infor" entry.
Each definition line corresponds to one hotel room within the Infor HMS. The first column "ID" represents the unique room ID (for example 101), the second column "Path" represents the path that is used to define the structure within the item tree.
The remaining fields "Persistent", "Historical" and "Synchronize" have the same functionality as for all other interfaces within the NETx BMS Server.
The following figure shows an example where 1 door lock is defined. In addition, the ZigBee/IP called "Hub Floor1" is also defined in order to receive events dedicated to the ZigBee/IP hubof a set of configured rooms which should be tracked.
After having defined all devicesrooms, the NETx BMS Server has to be restarted. Afterwards, the configured devices rooms are shown within the item tree under the sub tree "NETx\XIO\KabaInfor\Main".
The retrieved information from Kaba is stored as Server Items. Each retrieved field from the web service request for each room from the Infor HMS is stored as one server item. Regardless which fields are selected within the Messenger LENS interface, all fields are always shown within the NETx BMS Server. However, only 5 Server Items are counted to the license for each defined device. All other items are not counted to the license and are thus for free.
The most important information is the "Event ID" and "Event Name" which indicate the event type. This information can be linked to an XLogic command or LUA task in order to trigger some actions like changing a data point (e.g. trigger a lighting scene). The following table gives an overview of all events:
| Event ID | Event Name |
|---|---|
| Date time Error |
| Date time OK | |
| 42 | Deadbolt reset (retracted) |
| 26 | Deadbolt / Privacy |
| 4 | Door ajar clear or Door Secure |
| Door ajar Generic | |
| 41 | Door Ajar Guest Long |
| Door Ajar Guest Short | |
Door Ajar Staff Long | |
| Door Ajar Staff Short | |
| Door Latched | |
| Door Unlatched | |
| 17 | Generic Egress |
| Guest Key Used | |
| 8195 | Hub status OFFLINE |
| 8194 | Hub status ONLINE |
| Key Error - Canceled Key Used | |
| 66 | Key error - Expired |
| Key Error - Other | |
| Key error - Wrong Room | |
| 55 | Lock status OFFLINE |
| 54 | Lock status ONLINE |
| Low battery | |
| Low Battery Clear or Battery Normal | |
| Mechanical Key Override | |
| New Guest Key Used | |
| Paging Keys | |
| Staff Key Used | |
| Standing Intruder | |
| Transaction Failed | |
| Wandering Intruder |
a server item "RoomChecked" within the configured path.