Property Interfaces — IFC8, FIAS and XML_POS
The Oracle OPERA Hotel Property Interface application (IFC8) is used to connect various on-premise vendor management systems with the Oracle Property Management system. It sends out room and guest data to the vendor system, such as, for example, check-in of guest and check-out of guest. The interface can also receive data (for example, charges or status changes) from the external system to be stored in OPERA using synchronous TCP/IP or serial connection exchanging messages, which are based on either Oracle's universal FIAS API, XML-POS API, or many vendor-based specifications.
-
Telephone Management Systems (TMS) or middleware to TMS systems
-
Door Locking Systems
-
HSIA Internet Access Systems
-
Point of Sale Systems (Restaurant, SPA, Golf)
-
Video Services Systems
-
Guest Service systems
-
Minibar systems
-
Building Management systems
-
Miscellaneous / Other systems installed at property
The typical data exchanged via the Property Interface are check-in / check-out notifications (for example, room and guest details, guest rights), charge postings received from vendor systems, make door key requests, wake up requests, credit card payment requests, guest message notifications, room maid status notifications, and many more. This data is exchanged at the time the action occurs in OPERA or on the external system and is usually exchanged without a delay in transmission.
For IFC8 actions exchanged between OPERA Cloud and an external application, the REST APIs utilize multiple ways of connection.
There are inbound actions from the external system that will be exposed through the OHIP REST APIs. Some examples of these inbound actions are sending charges to the guest's room or hotel account, inquiry requests for Guest information by a Point-Of-Sale system, sending room status changes, wake up requests, and guest bill balance requests.
Some outbound IFC8 actions will be exposed using streaming APIs. Some examples include check-in, check-out, room-move notifications, wake-up requests, and guest text messages.
Specific outbound synchronous messages will be exposed using additional outbound service connections from the PMS to the external system. Some examples are door lock key actions (for example, make key and delete key), which require related response messages.
Note:
Posting charges via room number only (instead of reservationId) is not yet available with REST.
Table 15-4 Suggested APIs and Operations
| IFC8 Module | IFC8 Operation | REST Module | OHIP REST API | OPERA Cloud Business Event (Push or Pull) |
|---|---|---|---|---|
|
Enhanced Posting |
PostInquiry - by Room number, Name, Track2 Post List |
RSV |
getReservations |
|
|
Extended Guest Data |
GuestMessage-Request, GuestMessage-Text |
RSV |
guestMessages |
|
|
Extended Guest Data |
GuestMessage Text-online GuestMessage-retrieved GuestMessage-Delete |
Business Event |
NEW GUEST MESSAGE UPDATE GUEST MESSAGE DELETE GUEST MESSAGE |
|
|
Room Data |
Room Equipment: Voice mail notification from vendor to PMS |
RSV |
guestMessages |
|
|
Simple Posting |
PostSimple: Phone charge, Minibar charge, Video charge using room number only PostAnswer |
CSH |
postBillingCharges |
|
|
Enhanced Posting |
PostRequest: Point-of-Sale, SPA, Golf charges using Reservation Number PostAnswer |
CSH |
postBillingCharges |
|
|
Room Data |
RoomEquipment: send Room Maid Status from vendor to PMS |
HSK |
SetRoomStatus |
|
|
Room Data |
RoomEquipment: send Room Maid status from PMS to vendor |
Business Event |
UPDATE ROOM STATUS |
|
|
Room Data |
RoomEquipment: send Class Of Service, TVRights, MinibarRights, Do not Disturb (Phone) from PMS to vendor |
Business Event as of OPERA 23.4 |
UPDATE INTERFACE STATUS |
|
|
Room Data |
RoomEquipment: send MessageLight ON/OFF as message notification from PMS to vendor |
Business Event as of OPERA 23.4 |
UPDATE INTERFACE STATUS |
|
|
Wake-up Call |
Wakeup Request Wakeup Clear Wakeup Answer from vendor to PMS |
FOF |
postwakeUpCalls delete wakeUpCalls put wakeUpCalls |
|
|
Wake-up Call |
Wakeup Request Wakeup Clear Wakeup Answer from PMS to vendor |
Business Event as of OPERA 23.4 |
available soon |
|
|
Guest Data |
GuestIn notification from PMS GuestOut notification from PMS GuestdataChange notification from PMS, Room Move notification |
Business Event |
CHECK IN CHECK OUT UPDATE RESERVATION |
|
|
Room Data |
RoomEquipment: set Guest Service Status (Make Up Room, Do Not Disturb) from vendor to PMS |
HSK |
serviceRequests |
|
|
Room Data |
RoomEquipment: receive Guest Service Status change (Make Up Room, Do Not Disturb) from PMS to vendor |
Business Event as of OPERA 23.4 |
GUEST SERVICE STATUS REQUEST |
|
|
Guest Locator |
Locator On, Locator Off, Retrieve Locator |
RSV |
guestLocators |
|
|
Extended Guest Data |
Guest Bill Request / Guest Bill Items / Guest Bill Balance |
CSH |
getGuestsTransactions or getFolios |
|
|
Extended Guest Data |
Remote check-out Request (Video Check-out) |
CSH |
postBillingPayments + postFolios + postCheckout |
|
|
Night Audit |
Night Audit Start notification Night Audit End notification |
Business Event |
CLOSE BUSINESS DATE ROLL BUSINESS DATE |
|
|
Key Services |
Key Request ( New Key, Duplicate Key, One Shot Key) Key Delete Key Data Change (Room move, change check out date) - Online Key card systems Key Read |
FOF Outbound as of OPERA 23.4 |
post externalRoomKeys OPERA Cloud Outbound Syncronous |
|
|
Virtual Numbers (DID) |
GuestIn notification with Virtual Number/ Equipment Number, Status, Pool Id GuestdataChange notification with Virtual Number/ Equipment Number, Status, Pool Id GuestOut notification with Virtual Number/ Equipment Number, Status, Pool Id |
Feature is not available with OPERA Cloud |
N/A |
N/A |
Parent topic: Migrating from Legacy APIs to REST