...
The retrieved information from CharPMS is stored as Server Items. Here all available Server Items that are available for each room are listed (including their access rights):
| Item name | Data type | Access | Notes |
|---|---|---|---|
| RoomNumber | String | read only | Specified within room definitions within NETx Server. Must be identical with the room number used within CharPMS. |
| Description | String | read only | Specified within room Definitions within NETx Server. |
| RoomChecked | Boolean | read only | True if at least 1 guest is check in this room – false if all guests are checked out. |
| RoomCheckedForecast | Boolean | read only | True if there is a forecast check in for this room – false if all guests are checked out. |
| VacancyStatus |
| Number | read only |
Occupancy status for this room (the following default mapping can be changed here):
| |||
| RoomStatus | Number | read and write | Room status (the following default mapping can be changed here):
This information can also by written by the NETx Server. |
| DND | Boolean | read and write | Do not disturb information for this room.. This information can also by written by the NETx Server. |
| GuestName | String | read only | Guest name that is received |
from CharPMS. | |||
| GuestLanguage | String | read only | Language code that is received from |
CharPMS. E.g. |
EN, |
DE, ... |
| GuestVIP |
| Number | read only | VIP status that is received from |
CharPMS. | |||
| GuestArrivalDate | DateTime | read only | Arrival data and time of guest. Normally, this is equal to the check-in data and time. |
| |||
| GuestDepartureDate | DateTime | read only | Scheduled |
departure data and time of guest |
Note that this list of data points is fixed by MICROS Fidelio/Opera – not by the server.
The room status is a very important information which can also be changed from the server side. Fidelio/Opera specifies the following predefined values:
...
. |
...
Adding control functionality
After having configured the Fidelio/Opera interface, the provided data points can be linked to other data points within the server. You can use V-Links, Server Tasks, LUA script or XLogic commands for providing this functionality.
A typical use case would be the mapping of the RoomCheck item from Fidelio/Opera to a data point like the set point or the mode of the room's climate control. For implementing this use case, a predefined XLogic command called "HotelCheckInCheckOut" is already included within the server. Open the XCommand Event Definitions (BMS Studio --> Extensions) and add a new definition line. Give the logic a name (e.g. Room101), select "ON_INPUT" as type and select the XLogic "HotelCheckInCheckOut". Within the configuration dialog, select the input item (e.g. NETx\API\NXA_FIDELIO\PartA\Floor1\101\RoomChecked) and as output the data point that shall be controlled by the checkin/checkout signal (e.g. KNX group address of the set point of the room). The following screenshot shows an example:
Repeat these steps for a hotel rooms. After having finished all definitions, restart the server.
| Info |
|---|
To add additional definitions in a more easier and faster way, you can use the export/import to MS Excel function of the definition table. |
Article applies to the following products:
- NETx BMS Platform
- NETx Multi Protocol ServerNETx BMS Server 2.0