Why? The data set allows calculation of daily revenue forecast and optimal productivity as well as staffing level in PMI. What? The data set comprises of a daily snapshot of all sales and catering reservations recorded on the book for the next 365 days.
| # | PMI data element (target) | Description | Mandatory / Optional | Comment |
|---|---|---|---|---|
| 1 | Property ID | ID of the property (hotel, restaurant) | O | |
| 2 | Property Name | Name of the property (hotel, restaurant) | M | |
| 3 | Department ID | ID of the department within the property | O | |
| 4 | Department Name | Name of the department within the property | M | |
| 5 | EventType ID | ID of the event type | O | |
| 6 | EventType Name | Name of the event type | M | An event type can be any kind of catering activity; it can be as simple as a one-hour reception, or something more complex such as a three-day business meeting with meals, breaks, and specific meeting room, setup, and resource requirements. Other common examples are: dinner, meeting, coffee break, etc. These attributes are used to map associated revenue to correct departments and segments. |
| 7 | MealPeriod ID | ID of the meal period | O | |
| 8 | MealPeriod Name | Name of the meal period (e.g. Breakfast, Lunch, Dinner) | O | |
| 9 | Extract Date | Date of the data extract | M | |
| 10 | Event Date | Event Date | M | |
| 11 | Covers | Number of covers/guests | M | |
| 12 | NetRevenue | Revenue without VAT and other authority charge rates | M | |
| 13 | Event Status | Booking status of the reservation | M |
Please note: The table above shows the PMI data elements required. Equivalent data elements must be identified in source S&C application as part of the extract specification exercise.
The export should be scheduled daily as early as possible in the morning.
See this article about transfer methods