...
Info |
---|
In addition the IP address and the port number, there are several configuration options which depend on the IFC settings at the Fidelio/Opera side. Normally, you can leave the default options. If the communication is not working correctly, please ask the Fidelio/Opera integrator whether "LRC" or "Use Ack" option have to be used. |
Then, the used devices hotel rooms have to be createddefined. This is done within the "Device Room definitions" within the menu "Modules" -> "KabaFidelio/Opera". Each definition line corresponds to one deviceroom. The first column defines the device room name. The device room 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 must identically be the name that is used within the Fidelio/Opera system. If you do not know them, please ask the Fidelio/Opera integrator for the room list.
The next two columns "Building Name" and "Floor Name" are 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 devicesrooms, the NETx BMS Server has to be restarted. Afterwards, the configured devices are shown within the item tree under the sub tree "NETx\XIOAPI\KabaNXA_FIDELIO".
The retrieved information from Kaba Fidelio/Opera 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.
Data points for each room
Here all available Server Items that are available for each room are listed (including their access rights):
- BuildingNumber (read only)
- LevelNumber (read only)
- RoomNumber (read only)
- Description (read only)
- GuestsCount (read only)
- GuestName (read only)
- GuestLanguage (read only)
- GuestVIP (read only)
- RoomChecked (read only)
- ClassOfService (read only)
- DoNotDisturb (read only)
- RoomStatus (read and write)
- ClearText (read only)
- GuestArrivalDate (read only)
- GuestDepartureDate (read only)
- PrinterPort (read only)
- MessageCount (read only)
- NextMessage (write only)
- MessageText (read only)
- GetMessage (write only)
- SendMessage (read and write)
- MessageLightStatus (read only)
...
Note that this list of data points is fixed by MICROS Fidelio/Opera – not by the NETx BMS Server.
The room status is a very important information which can also be changed from the NETx BMS Server side. Fidelio/Opera specifies the following predefined values:
Code | Room status |
---|---|
1 | Dirty/Vacant |
2 | Dirty/Occupied |
3 | Clean/Vacant |
4 | Clean/Occupied |
5 | Inspected/Vacant |
6 | Inspected/Occupied |
...