OXI is the business-data exchange channel of OPERA 5 on-premise. Where IFC8 handles device events, OXI moves business objects — reservations, guest profiles, rates, inventory and blocks — as XML messages uploaded from or downloaded into OPERA.
What OXI exchanges
| Object | Typical use |
|---|---|
| Reservations | CRS delivers bookings; OPERA uploads changes and stay status |
| Profiles | CRM / loyalty sync of guest data and preferences |
| Rates | Central or revenue system maintains pricing |
| Inventory | Availability for distribution |
| Blocks / allotments | Sales & catering group blocks |
| Stay history | Data warehouse and guest value analysis |
Implementation tips
- Objects and master data — decide which system owns each object (e.g. rates owned by the revenue system).
- Conversion tables — map room types, rate codes, market and source codes, payment types. This is usually the longest part.
- Message handling — create, update and cancel actions per object.
- Errors and resync — alert on failed messages and agree when to resync.
- Bulk loads — run initial profile or history loads off-peak and in batches.
For reporting-only needs, a read-only database extract is often simpler than OXI.