Group Blocks
Group block messages are expected to always be full overlays, where the last one received “wins” based on the “lastModifiedDateTime”. IDeaS RMS uses the group block code as the unique identifier. Do not reuse this code within the PMS/CRS for submission of group block data to IDeaS for a single property database.
Personal Identifying Information (PII)
IDeaS does not request any Personal Identifying Information and expects that the sending system removes all PII data from group block messages before sending.
Group Code
We expect the group block code to be unique. Do not reuse it for a single Hotel. This code becomes the index to which all changes to the group block are applied.
Group Block Status Codes and Expected Handling
Group Status codes that you provide for each group block are set up based on their PMS/CRS status. They are mapped depending on whether they are deducting or non-deducting from general inventory.
| PMS / CRS Status | API Group Status Code | Deducts Inventory |
|---|---|---|
| Cancel | CANCELLED | No |
| Definite | DEFINITE | YES |
| Hold | TENTATIVE | No |
| Lost / Declined | LOST/REGRET | No |
| Prospect | PROSPECT | No |
| Strong Tentative | DEFINITE | YES |
| Tentative | TENTATIVE | No |
| Weak Tentative | PROSPECT | No |
Group Booking Date/Time
We request that you send the create date of when the group block was first entered into the PMS/CRS. The create date of the group helps IDeaS RMS forecast group block data. This is an optional attribute, and if the PMS/CRS does not store this date, it will not impact the integration testing.
Group Block “Block” Count
The “blocks” value for a Group block is the count of rooms held from inventory each night, against each room type. This value does not change unless the number of rooms held is reduced or the block is reduced or washed to the pickup count.
Group Reservation Pickup Reporting
As reservations are booked against the block, IDeaS RMS expects to receive an update to the Group Block pickup count along with the associated reservations.
Group Rate Code, Room Type, and Occupancy Reporting
The API requires that you provide a single rate code for the combination of room type and occupancy date. If a system allows for multiple rate codes for a single room type and occupancy date, we expect the sending system to consolidate the reporting into one room type and occupancy date and a default rate code.
Example
This PMS/CRS allows multiple rate codes to be used on a group block for the same room type and occupancy date.
| 1-Oct | 2-Oct | 3-Oct | 4-Oct | |
|---|---|---|---|---|
| RoomType: | AKN | AKN | AKN | AKN |
| Blocked Count: | 10 | 10 | 10 | 10 |
| RateCode: | ASSOC | ASSOC | ASSOC | ASSOC |
| RateValue: | 100.00 | 100.00 | 120.00 | 120.00 |
| RoomType: | AKN | AKN | AKN | AKN |
| Blocked Count: | 6 | 6 | 6 | 6 |
| RateCode: | ACP | ACP | ACP | ACP |
| RateValue: | 85.00 | 85.00 | 105.00 | 105.00 |
Below shows the consolidation of the two rate codes for the same room type and occupancy dates, done by calculating a weighted average of the rate value. You can also see the consolidation in the example table below.
For 1-Oct & 2-Oct: (10×100+6×85) / (10+6) = 94.38
For 3-Oct & 4-Oct: (10×120+6×105) / (10+6) = 114.38
This table shows the consolidated multiple rate codes and rate values into a single entry for room type and occupancy date reporting, with a generic rate code (example) and a weighted average rate value.
| 1-Oct | 2-Oct | 3-Oct | 4-Oct | |
|---|---|---|---|---|
| RoomType: | AKN | AKN | AKN | AKN |
| Blocked Count: | 16 | 16 | 16 | 16 |
| RateCode: | GRP | GRP | GRP | GRP |
| RateValue: | 94.38 | 94.38 | 114.38 | 114.38 |
Special Handling of Group Block Data
Send Group blocks to IDeaS when any changes are made against the group, including the following:
- Blocks count changes
- Pickup count changes
- Group status code changes
- Date changes
- Room type changes
- Rate code
- Market segment
- Rate values