Impala sends out hotel-specific step-by-step self-onboarding walkthrough guides. Configuration can be completed by a PMS user with sufficient superuser permissions in the user interface without needing technical skills. The entire process typically takes less than 30 minutes.
Reports are generated in the Opera application server as text files and uploaded securely to Impala’s ingestion endpoint using Opera’s SFTP delivery methods. Impala offers the strongest possible encryption option available, with 2048-bit private key encryption using a generated passphrase.
Impala generates hotel-specific report configurations for reports containing personally identifiable information (PII) to make sure only the minimally required data points are included in the text reports. This minimises the data footprint of all parties involved. Hotels can set up their firewall configuration to only allow SFTP outbound traffic for the specific static IP address. The Impala ingestion API (SFTP) is available as a guard against SSL certificate miss-issuance, DNS spoofing, and domain takeover attacks.
OXI interfaces don’t allow for 2048-bit private key encryption protected by a passphrase, while SFTP Delivery Methods (the mechanism Impala uses within Opera) do support this option. Impala offers its product at a fraction of the cost of what a PMS charges hotels for a one-of installation and ongoing support and maintenance. This enables hotels to use innovative technologies cost-effectively.
Impala’s installation can be completed in 30 minutes, whereas activating an OXI can take months. In addition, with OXI, licenses need to be ordered. The set-up involves high-touch sales processes and account management, and costly remote or on-site installs.
The data flow for Oracle Hospitality Opera can be reviewed here.