Data Level Differences

In G3 RMS, you might notice data differences between different reporting levels, like the property level compared to the market segment level. For example, Revenue On Books at the property level may not equal the sum of Revenue On Books for all Forecast Groups. These data discrepancies may exist within a dashboard or report or compared to your Reservation System The primary reservation system, like a PMS or CRS, that provides data to G3 RMS. The data from that one system is used by the RMS to forecast, optimize and produce controls. The controls are sent to all selling systems, which for some integrations may exclude the reservation system..

It's important to understand that these data discrepancies are reporting challenges only. They have no impact on your forecast and decisions, where G3 RMS uses market segment and room type level information as the basis for its optimization.

Occupancy and Revenue for Property, Market Segment, or Forecast Group

Most discrepancies in data can be explained by the fact that some values shown in G3 RMS are based on summary data and others on transactional data. Both are received directly from the reservation system. An example of summary data is the total number of rooms sold by market segment. Transactional data is all the details from all individual reservations booked under that market segment.

G3 RMS displays the occupancy and revenue on books values at the property level based on summary level data from the reservation system. For the market segment or Forecast Group level, G3 RMS cannot use the market segment summary data from your reservation system. Instead, G3 RMS needs to add up transactional data from individual reservations. The original market segments from your reservation system differ from the market segments G3 RMS uses because you used attributes to modify the original market segments to provide G3 RMS with the best data for forecasting and optimization.

These are a few other scenarios when the general differences between summary and transactional data lead to data differences in G3 RMS:

Multiday Reservations

Discrepancies can occur when multi-day reservations include rate amounts or rate codes and market segments that differ between the days. For example, a three-night reservation consists of a corporate rate code for the first and last night and a Package code for the second. The transactional rate code data counts the second night as Package. The summary property level data uses the corporate rate code for all three nights, as determined by the last night's data. Similarly, if a three-night reservation was priced at daily rates of $100, $150 and $200, the Business Analysis Dashboard shows a rate of $150 for all nights because it averages the rates and attributes the data based on the last night’s market segment, rate code, etc.

No Show Revenue Codes

The reservation system may send No Show revenue to G3 RMS. Categorizing it as room revenue may result in data discrepancies, depending on whether it was booked against a physical room type or a pseudo room type.

Pseudo Room Types

Revenue posted to paymaster/pseudo room types is not reflected in the Forecast Group level data, where G3 RMS excludes pseudo room types. If the property level data from the reservations system, however, is a direct summation of all room types, it could include revenue posted to pseudo room types.

Re-Attribution or Removal of Rate Codes

Rate codes that are re-purposed or deleted impact the revenue values at the G3 RMS market segment level, which is combined to produce the Forecast Group level summary.

Pickup for Rate Code and Market Segment

You might see differences in the pickup between rate code and market segment levels, because G3 RMS maintains pace only at the market segment level. To determine pickup at the rate code level, G3 RMS adds up individual reservations, inferring the pickup based on the booked date of the reservation. The following are a few scenarios that cause these differences: 

Pace Maintained only from Nightly Processing to Nightly Processing

G3 RMS does not maintain intraday booking pace to record incremental bookings between nightly processing and intraday processing. Booking pace is only stored from one day to another, from one business day end to the next.

Consequently, rate code level pickup (based on the booking date of each reservation) may feature rooms booked during an intra-day processing. However, at the market segment level, this pickup is reflected in the next day’s Nightly Processing.

Modification of Arrival Date or Length of Stay

When the arrival date or length of stay changes for a reservation, G3 RMS treats it as a new booking.

While this does not impact the actual pace recorded at the market segment level, the booked date reflected in the new reservation is used to derive rate code level pickup. The “true” booking date not being reflected on the updated reservation leads to discrepancies between the rate code and market segment level pickup.

Group Blocks with Incomplete Pickup

As group blocks appear, the rooms sold are appropriately recorded at the market segment level.

However, until the reservations arrive with actual pickup against the block, no rate code level information can be recorded. This will lead to discrepancies between the market segment and rate code level wherever group blocks are greater than the picked up rooms on the block.

These discrepancies are more likely further from the day of arrival, where there is more pickup pending on group blocks.