Fidelio/Opera 1: Integrating MICROS Fidelio/Opera

Basic architecture

The NETx BMS Server provides an interface which can be used to integrate information from the hotel management system MICROS Fidelio/Opera. Using this interface, information about the check-in/check-out procedure, the hotel guests and the hotel room states can be retrieved. In addition, it is also possible to send dedicated information from the NETx BMS Server to the MICROS Fidelio/Opera system. This interface for the NETx BMS Server is certified by MICROS. The offical certificate can be found here.

The following figure shows how the integration has to be done.

In order to connect to MICROS Fidelio/Opera system, the so called IFC interface from MICROS Fidelio/Opera has to be activated at the MICROS Fidelio/Opera side. This has to be done by the MICROS Fidelio/Opera integrator.

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 services.

Integration steps

To start, open the BMS Studio. First, configure the IP address and port number that you have enter within the web service URL. This can be done by selecting "Driver Configuration" within the menu "Modules" -> "Kaba".

Then, the used devices have to be created. This is done within the "Device definitions" within the menu "Modules" -> "Kaba". Each definition line corresponds to one device. The first column defines the device name. The device name must be unique and is shown within the item tree the NETx BMS Server. The next column "Device ID" is optional. "Device Name" and "Device ID" are used to assign a web service notification to the corresponding item within the item tree. This means that either "Device Name" or "Device ID" must be the same as the Kaba software uses within the web service request. The 3rd column "Path" is used to define an optional structure within the item tree. "Description" is used to provide additional information which is stored within the item property "Description". The remaining field "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 hub.

After having defined all devices, the NETx BMS Server has to be restarted. Afterwards, the configured devices are shown within the item tree under the sub tree "NETx\XIO\Kaba".

The retrieved information from Kaba is stored as Server Items. Each retrieved field from the web service request 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: