Room Cube Dimension Dictionary_Updated

HQ RO PMS
Dimension
Block Leadtime
Room Cube
Stay Trend – Leadtime – Block

Metric Description

• Group Block Booking Lead Time
• Example value includes “10”

Description
Typical Use Case

• Display group booking lead time of each reservation; Booking lead time is the difference
between date booking turned tentative and date of planned arrival.

• This dimension should mainly be used with filter on Group, using dimension “Market Category” in
“Market Segmentation” folder.

• For FIT booking, lead time should be defined as the difference between date booking made and
date of planned arrival. In such case, dimensions under “Leadtime” should be used.
Block Leadtime (# of days)

Date Booking Turned Definite Date Of Planned Arrival
(Tentative Date) (Date of Stay - Day 1)

Description Date of Stays
Interface Ref./ Detailed Logic
• Blueprint will look up “Tentative Date”
PMS Configuration & “Date of Stay - Day 1” of each
reservation; Leadtime shows the
number of days between “Block
Insert Date(Tentative Date)” & “Date
of Stay - Day 1” (e.g. leadtime is 1
day if tentative date is 15/3/2025 and
date of stay - day 1 is 16/3/2025)

• Return “Unknown” when either “Block
Insert Date” & “Date of Stay” is empty

151

HQ RO PMS
Dimension
Block Leadtime Bracket
Room Cube
Stay Trend – Leadtime – Block

Metric Description

• Group Booking Lead Time Bracket
• Example values include “11-14”, “15-21”

Description
Typical Use Case

• Display group booking lead time of each reservation; Group Booking Lead Time is first calculated
and is then categorized into respective Brackets.

• This dimension should mainly be used with filter on Group, using dimension “Market Category” in
“Market Segmentation” folder.

• For FIT booking, lead time should be defined as the difference between date booking made and
date of planned arrival. In such case, dimensions under “Leadtime” should be used.

Block Leadtime (# of days) Categorize Leadtime Bracket

Date Booking Turned Definite Date Of Planned Arrival
(Tentative Date) (Date of Stay - Day 1)

Date of Stays

Description
Interface Ref./ Detailed Logic

• Blueprint will look up “Tentative Date” & “Date of Stay - Day 1” of each reservation; Leadtime
shows the number of days between “Block Insert Date(Tentative Date)” & “Date of Stay - Day 1”
(e.g. leadtime is 1 day if tentative date is 15/3/2025 and date of stay - day 1 is 16/3/2025). This is
then categorized into respective leadtime Brackets

• Return “Unknown” when either “Block Insert Date” & “Date of Stay” is empty

152

Stay Trend – Length of Stay

153

HQ RO PMS

Length of Stay Dimension

Room Cube
Stay Trend – Length of Stay

Metric Description

• Length of Stay

• Example value includes “10”

Description
Typical Use Case

• Display length of stay of each reservation; Length of Stay is the number of days between arrival
date & departure date

• This dimension should be used with Arrivals, instead of Room Nights as we are looking at duration
and not per night stayed

• Use this to together with dimensions in folder “Market Segmentation” & “Country” to analyze the
booking pattern by market segment & guest demographics
Length of Stay (# of days)
(2 days in the example)

Date Of Arrival Date Of Departure
Descri(p1tsitoMn arch) (3rd March)

Interface Ref./ Detailed Logic
PMS Configuration

• Blueprint will look up “Date of
Departure (Date of Stay - End Day)”
& “Date of Arrival (Date of Stay - Day
1)” of each reservation; Length of
Stay shows the number of days
between “Date of Departure” &
“Date of Arrival” (e.g. length of stay is
2 days if arrival date is 1/3/2025 and
departure date is 3/3/2025)

• Return “Unknown” when either “Date
of Departure” or “Date of Arrival” is
empty

154

HQ RO PMS

Length of Stay Bracket Dimension

Room Cube
Stay Trend – Length of Stay

Metric Description

• Length of Stay Bracket
• Example values include “3-4”, “5-7”

Description
Typical Use Case

• Display length of stay bracket of each reservation; Length of Stay is first calculated and is then
categorized into respective Brackets

• This dimension should be used with Arrivals, instead of Room Nights as we are looking at duration
and not per night stayed

Length of Stay (# of days) Categorize
(2 days in the example)
Length of Stay Bracket

Date Of Arrival Date Of Departure
Descri(p1tsitoMn arch) (3rd March)

Interface Ref./ Detailed Logic

• Blueprint will look up “Date of Departure (Date of Stay - End Day)” & “Date of Arrival (Date of
Stay - Day 1)” of each reservation; Length of Stay shows the number of days between “Date of
Departure” & “Date of Arrival” (e.g. length of stay is 2 days if arrival date is 1/3/2025 and
departure date is 3/3/2025). This is then categorized into respective Length of Stay Brackets

• Return “Unknown” when either “Date of Departure” or “Date of Arrival” is empty

155

Stay Trend – Repeat Stay

156

HQ RO PMS

Repeat Stay - Hotel Level Dimension

Room Cube
Stay Trend – Repeat Stay

Metric Description

• Repeat Stay At The Same Hotel

• Example values include “First Stay” & “Repeat Stay”

Description
Typical Use Case

• Display whether the reservation is first stay in the property or repeat stay in the same property.

• Please note that in Blueprint BI, a stay is recognized as “Repeat Stay” if a guest stays at the same
hotel for more than once since 2015. The reason is that guest profiles and stay records are not
shared across hotels.

• Typically to be used in conjunction with dimension in folder “Market Segmentation” to
understand the repeat stay business performance. In general, Group segment should be filtered
out to make your figures more reliable. Keep it to Public and Negotiated if you can

Description

Interface Ref./ Detailed Logic

• Blueprint will look up whether there was past reservation with the same customer profile (based
on customer ID) in the same property. If look up is successful, return “Repeat Stay”; If look up is
unsuccessful, return “First Stay”. Please note that if the guest has stayed only once at every
properties, he/ she will still be counted as “First Stay”

• Return “Unknown” when there is no customer profile attached (e.g. when customer profile is
purged due to guest request (GDPR concerns) or when the reservation is not yet picked up) or
when the reservation concerned is incomplete with no successful departure (only date of arrival
is recorded without date of departure)

157

Stay Trend – Stay Type

158

HQ RO PMS

Stay Type Dimension

Room Cube
Stay Trend – Stay Type

Metric Description

• Stay Type
• Example values include “Weekend Getaway” & “Extended Stay”

Description
Typical Use Case

• Categorize reservations into different stay types based on the assumptions in the table below
• Typically to be used in conjunction with dimensions “Public Rates” & “Negotiated” in “Market

Code” to better understand guest staying pattern
• Use this to understand if there is potential to create a Weekend package or weekend activities

Stay Type Assumption
Extended Stay
5 or more nights stay

Description Day Use 0 nights
Weekend Getaway
Extended Weekend Friday check-in with 1-2 nights stay or
Overnight Business Saturday check-in with 1 night stay
Extended Business
Thursday or Friday check-in with a 3-4 nights stay or
Saturday check-in with a 2-4 night stay

Sunday through Thursday check-in with 1 night stay

All other scenarios, such as: Thursday check-in for 2 nights or
Sunday through Wednesday check-in with a 2-4 nights stay

Interface Ref./ Detailed Logic

• Blueprint will look up the stay pattern of each reservation; Classify each reservations into
respective “Stay Types” based on the assumptions listed above. For abnormal stay pattern (e.g.
negative room nights), Blueprint will classify them into “Other”

• This dimension is not applicable to Resorts

159

Stay Trend – Turnaway Reason

160

HQ RO PMS
Dimension
Turnaway Reason
Room Cube
Stay Trend – Turnaway Reason

Metric Description

• When booking has not been completely processed or canceled before confirmation number is
generated

• Example values include “Hotel Turnaway”, “Guest Turnaway”, etc.

Description
Typical Use Case

• This is required when turning down a booking
• This dimension should be used with Turnaways, Turnaway Nights, Turnaway ADR and Turnaway

Rev in Misc – under Statistics folder in Measure

Description

Interface Ref./ Detailed Logic

161

Stay Trend – Time of Arrival.Hour

162

HQ RO PMS

Time of Arrival.Hour Dimension

Room Cube
Stay Trend – Time of
Arrival.Hour

Metric Description

• To capture guest’s estimated time of arrival prior check in
• Example values include “1”, “16” & “Unknown”

Description
Typical Use Case

• To analyze guest’s departure pattern from various market mix, which facilitate Front Office /
Guest Relations to provide customized guest services (i.e. late check out upsell); and also
Housekeeping for room make up schedule

Description
Interface Ref./ Detailed Logic

PMS Configuration

• Blueprint will look up the ETA field on
the reservation if arrival transportation
details is provided.

• Return “Unknown” when there is no
value.

163

Stay Trend – Time of Departure.Hour

164

HQ RO PMS

Time of Departure.Hour Dimension

Room Cube
Stay Trend – Time of
Departure.Hour

Metric Description

• To obtain guest’s estimated time of departure prior check in or during stay
• Example values include “1”, “16” & “Unknown”

Description
Typical Use Case

• To analyze guest’s arrival pattern from various market mix, which facilitate Front Office / Guest
Relations to better optimize room assignment prior to guest checks in; and also Housekeeping for
room make up schedule

Description
Interface Ref./ Detailed Logic

PMS Configuration

• Blueprint will look up the ETD field on
the reservation if departure
transportation details is provided.

• Return “Unknown” when there is no
value.

165