Opera PMS Local connects the hotel's front-desk system to the automation server, maps each room to a KNX address and carries check-in and check-out into the room's automation, and manages energy according to whether the room is occupied: a hotel integration application.
The front desk knows; the automation does not
In a hotel, room automation switches the lights, the climate and the scenes. But whether a room is occupied or empty is something the front desk knows and the automation does not. When that information never reaches the automation, even rooms that were never given to anyone are heated and cooled, and energy runs to waste. The hotel's largest cost is managed without the one piece of information that would settle it.
It connects the hotel's PMS to the automation
Opera PMS Local connects the hotel's management system (PMS) — known as Opera, or by its former name Fidelio — to the automation server. You map the hotel's room numbers to KNX addresses; every check-in and check-out at the front desk applies straight to that room's automation. The application is an independent application developed by Sona; Opera, Fidelio and the related names belong to their owners.
Setup is one job: mapping the rooms
The real work of commissioning is the room mapping. Each row holds the room number from the hotel's Opera system and the KNX address that will carry that room's occupancy. If the address does not exist on the device, the application creates it and names it in the language you chose. The mapping rests on the hotel's own room number; there is no conversion table and no layer in between.
An occupied room greets the guest, an empty room saves
When a room is checked in, its address goes to occupied; when it is checked out, it returns to empty. Your scenes do the rest: when the room fills, it greets the guest at the light level and temperature they want; when it empties, it goes into saving mode on its own. Rooms with nobody in them are not heated and cooled for nothing. The application writes to these addresses only when something changes, so it does not load the bus by sending the same information over and over.
An unmapped room does not slip past
Once the connection is up, if a check-in arrives for a room that is not on your list, the application does not pass over it quietly. It lists the room number as a suggestion at the top of the screen; when you click it, the mapping form opens with the number already filled in and all you have to do is enter the address. At the same time a low-priority information record drops into the central alarm list and stays there until you complete the mapping.
The health of the connection is visible on screen
The state of the Opera connection is written to a KNX address and reports three cases separately: you closed the connection yourself, the connection is healthy, or the connection dropped. Put that on the graphic screen or in the building management system and you can watch the health of the link without ever opening the application. A drop also goes into the central alarm list, so the technician on night duty does not confuse a planned shutdown with a real fault.
Manual synchronization is one touch
The moment you suspect the front-desk screen and the state in the field have drifted apart, you can pull the current state of every room again. Writing a one to the KNX address reserved for it is enough, and you tie that address to a button on the graphic screen. The application suppresses synchronization requests that arrive back to back for a short while, so it does not flood the hotel's system with requests.
The connection and the mapping live on the server
Both the Opera connection and all the room mapping run on the automation server, on site; the data does not go to the cloud. The application keeps the last two thousand events in a persistent log, so when the history of a problem has to be looked at, the trail is in the service team's hands.
Your installation lives in one file
Your room mappings, your network settings and your language choice are downloaded as a single file. On restore, the records are processed one by one, rows that already exist are skipped, and at the end a summary shows how many records were added. If the backup was taken while the connection was open, the application re-establishes the connection itself at the end of the restore; you move the same installation to another server in minutes.
How Opera PMS Local works: introduction
Connecting the hotel's management system to the automation server, mapping room numbers to KNX addresses, and applying check-in and check-out to the room automation.
Frequently asked questions
Which hotel systems does it work with?
It works with the hotel's management system (PMS) known as Opera, or by its former name Fidelio. The connection is made over that software's interface on the hotel side; the address and port are obtained from the hotel's IT team.
Was this application made by the company that develops Opera?
No. Opera PMS Local is an independent application developed by Sona, and it connects to the hotel's existing system over that system's own interface. Opera, Fidelio and the related names belong to their owners.
Does it work without Alert Plus installed?
No. Because the application passes events such as a dropped connection or an unmapped room to the central alarm manager, Alert Plus has to be installed. The right order is to install Alert Plus first and this application after it.
Does anything have to change in the hotel's software?
Nothing new is developed on the hotel's software. The application connects over the existing interface and listens to the events; room numbers and the reservation flow stay as they are on the hotel side. What is needed for the connection is that this interface is open and that the address and port are provided. The work on your side is mapping the room numbers to KNX addresses.
Can rooms be added later?
Yes. The room list is edited only while the connection is closed; you close the connection, add the room and reconnect. And if a check-in arrives for an unmapped room, the application warns you anyway.
Does the data go to the cloud?
No. The connection and the mapping run locally on the automation server, and the event log is kept on the device.
How many rooms can be mapped?
Every room in the hotel is mapped one by one, and each room is given its own KNX address. It is recommended that the application be given its own address range, not used for anything else.
Does the license change with the number of rooms?
No. The license is tied to the automation server; however many rooms are mapped on that server, the license stays the same. In a hotel chain, each property has its own server and its own license.
Opera PMS Local is included in the BMS Plus license and installs from the store in Sona Application Center.
The application runs on the Sona BMS automation server. If touch panels are wanted in the rooms, SonaHMI panels connect to the same platform.
Become a Sona dealer.
Build your projects on a single platform. Training, technical support and the application catalog are open to our dealers.