About OPERA Business Intelligence

The OPERA Business Intelligence (OBI) suite of tools enhances the analysis of OPERA data for OPERA customers (in single or multiple properties: ORS, OCIS, SFA, PMS and/or S&C) through the OBI Application and Dashboard. With OPERA BI, users can:

Access data stored in existing OPERA relational tables and view this data in multidimensional models, optimized for business intelligence
Summarize, analyze, and calculate data faster in ways not possible with standard relational tables
Query and analyze the multidimensional models natively, from within OPERA
Use the data as a resource for making sound business decisions and strategies affecting future revenue and profit

Required OBI Licenses

There are two OBI editions available: The standard edition for a single-property (OBISE1) and the enhanced enterprise edition (OBIEE) with Alerts and MS Office plug-in, for multiple properties.

OPI_BUIP <version number> - For a single property only (PMS or S&C), wanting only the standard single-property version for the OBISE1 Version of Oracle, activation of the add-on license OPI_BUIP is required.
- For installations with more than one property, only one property can be active with OBISE1. If other properties want BI, they will have to purchase OPB_<version number>. See below.
- If a single property wants the OBI Enterprise Version (OBIEE) containing full features such as Alerts and the MS Office plug-in, they may install the license OPB_<version number> for their OPERA Version). See below.
OPB_<version number> - To enable multiple properties for OBI, such as with applications ORS, SFA, OCIS, and multi-property PMS, the Oracle OBI Enterprise Version (OBIEE) must be activated with the license code OPB_<version number> (for OPERA Version 5.00.0x).

When purchasing and installing the OBI application and licenses, you will also automatically receive access to OCIS Datamarts. In this case, a separate license code is not required for OCIS DataMarts. (Within an ORS/OCIS environment without OBI, if DataMarts are required, a separate add-on license is required).

Note: OBIEE (v5.0.02.01+) OPB_<version number>provides access to S&C Advanced Reporting with no additional add-on license. These reports do not require data cubes and are directly compiled from OPERA tables by using real-time online transactional processing (OLTP). S&C Advanced Reporting is also available for users who do not have the OBIEE (OPB_<version number> license by activating an add-on license (OPS_SAREP S&C) and ORO_<version number> Oracle BI SE-one User Interface license for S&C Advanced Reporting views. See more details about S&C Advanced Reporting Setup in this help topic: S&C Advanced Reporting Setup (S&C Advanced Reporting Setup, http://www.).

Note: The remainder of the information in this topic is for OBIEE OPB_<version number> and OPI_BUIP <version number> licenses.

Room Sum Requirements

Here are some considerations regarding the OPERA application licenses and the OBI licenses as far as amount of rooms allowed.

The OBI license is based on a specific number of rooms. The OPERA application installation (ORS, OCIS, SFA, PMS and/or S&C) is also based on a specified number of rooms.
Because not all properties in a multi-property environment (OBI Enterprise Version OBIEE with the license code OPB_<version number>) will be using OBI, a property application parameter is available (OBI>Property>BI Enabled) that when set to Y, provides the selected property access to the OBI cubes. (This parameter must be set to Y for every BI property in a single and multiple-property environment.)
- The sum of all rooms for all properties that are BI Enabled must be less than the number of rooms in the BI license. If the sum of all rooms for all properties that are BI Enabled is greater than the number of rooms in the OBI license, the OBI cubes will not be maintained or updated any longer. An error will be found in the Error logs. For single PMS installations, the number of rooms in the PMS license must match the number of rooms in the OBI license.
- For single S&C installations, the number of rooms in the S&C license must match the number of rooms in the OBI license.
- For single PMS installations combined with S&C installations, the number of rooms in the PMS license must match the number of rooms in the OBI license.

OBI Cube Descriptions

Note: When the OBI DIM Security parameter is set to Y, users will need to rebuild all OBI cubes. The drop cube with full rebuild should be used when rebuilding the cubes. After a cube is rebuilt, the dimensions will only be linked to the property that owns them and will be property specific. Using the Market dimension as an example, users in Property A will only be able to see the market codes specific to Property A, and users in Property B will only be able to see the market codes for Property B, etc.

Some available OBI Cubes are:

Company Cube - Provides statistics for Companies. Identifies companies that provide maximum revenue. Under-performing companies can be quickly identified.

Travel Agent Cube - Similar to Company Analytics, identifies Travel Agents that provide maximum revenue. Under-performing Travel Agents can be quickly identified.

Daily Summary Cube - Provides a snapshot of each property after the ‘end of day’ process has finished. This is a high level view of your property, allowing you to quickly see trends.

Financial History Cube - Provides financial information at the transaction code level. Incorporates detailed-level financial transaction figures. Users can observe which departments are not performing, potentially affecting gross profit.

Reservation Pace Cube - Builds a booking pace and forecasting cube. Monitors ‘on the books’ reservations and blocks. When combined with budget and forecast figures, provides users with comprehensive insight of what is occurring at the property for the next 18 months. The Reservation Pace Cube is a collection of snapshots of the future 18 months. At every predefined date, the system takes and keeps the snapshot for the next 18 months. This lets the user see how the future appeared, on any snapshot date. The size of the Reservation Pace cube is a multiple of Future Cubes by the number of snapshot dates. This cube also has 'week ago' and 'day ago' calculations.

Monthly Resv Pace Cube - The Monthly Pace Cube is similar to the Reservation Pace Cube but it contains the monthly level data for future reservations and blocks. It stores data for up to three years and adds more dimensions, such as Source Code, Channel, and Res Insert Source. When the OBI_SYNC_LOCAL_DATAMARTS_FOR_PACE and OBI_USE_LOCAL_DATAMARTS_FOR_PACE parameters are set to Y, data is loaded from the reservation_summary_log_lcl_vw and obi_reservation_stat_daily_lcl views. These views are built from local tables in the BI database.

Reservation History Cube - Provides detailed statistics for past reservations on a daily level. Detailed level reservation transaction and budget analysis is available. Combined with future reservations and forecast projections, allows you to see market changes and many other factors that are affecting your occupancy and ADR.

Future Resv Monthly Cube - Provides detailed statistics for 'on the books' reservations and blocks. This Cube provides users with comprehensive insight of what is occurring at the property for the next 18 months (defined by the application setting OBI>Global>Future Stay Months). The Reservation Future Cube is always a snapshot on the business date for the future 18 months. There is only one snapshot which gets overwritten everyday. When the OBI_SYNC_LOCAL_DATAMARTS_FOR_PACE and OBI_USE_LOCAL_DATAMARTS_FOR_PACE parameters are set to Y, data is loaded from the reservation_summary_log_lcl_vw and obi_reservation_stat_daily_lcl views. These views are built from local tables in the BI database.

Monthly Resv History Cube - The Monthly Pace Cube is similar to the Reservation Pace Cube but it contains the monthly level data for future reservations and blocks. It stores data for up to three years and adds more dimensions, such as Event (Blocks and Reservations), Rate Code, Source Code, Channel, and Reservation Insert Source.

Request Log Cube - Captures requests made from ORS. Reports on channels by day and hour are possible from this cube.

Block History Cube - Captures historical data for past allotments. The records will be populated once a day after night audit for allotment dates equal to the closing date being run by the night audit process.

Stay Cube - Contains statistical information based on stay records analyzed by Resort, Guest, Company, Market, Rate, Revenue Type, Room Type, Rate Code and Insert Source.

Additional Processes

A Stage Table is available for Financial Stat Daily Records and can be viewed in ORS/OCIS. It displays financial records that did not pass conversion successfully and have been staged. Access ORS/OCIS>Data Mart>Stage Financial Statistics. The Financial Statistics Staged Records screen appears. Previously, it had been difficult and cumbersome for users to find and fix financial stat daily records in OXI-HUB, while the user needed to go to different applications to check for failed records. This screen (Financial Statistics Staged Records) displays when the Data Mart or BI license code is active, revealing staged financial records. The screen includes the Property, Business Date when staged, PMS Conf. No., PMS Transaction Code, Market, Status, and Import Date of the Staged Record.
Comp and House Use flags have been added to the Reservation History Cube. The flags will help identify Complementary and House Use rooms and revenues. The data is updated through the Sync Utility in Utilities>Synchronize Utilities>Synchronize OBI Data Mart Utility.
Company Stats are based on the top company in the hierarchy. When a company has been set up in a hierarchical relationship, the top Company Id in the reservation (in the C-SUB and C-MASTER relationship), populates the RESERVATION_STAT_DAILY Table. A new column called parent_company_id has been added to the table. If no company hierarchical relationship has been configured, then this column simply contains the Company Id of the company that is not in a relationship. The field in this column is populated whenever the OPERA API is updated or when the RESERVATION_STAT_DAILY Sync Utility is run through Utilities>Synchronize OBI Data Mart Utility>Synch. Reservation Statistics.
OBI text labels on the OBI Dashboard can be customized for a specific language or even changed from one English language label to another (i.e. Property to Hotel). This customization can include static Dashboard labels as well as the text from query results. Oracle responses, report labels, subject areas, metrics, and dimensions can also be customized and translated into another language. Other examples of translatable text elements include the content of text strings, the text for prompts such as the names of links and buttons, and the text of error and informational messages that are displayed to users as the result of an action. Translations are done mainly with the Oracle pre-built language pack. The Oracle BI Documentation provides instructions on how to make translations.