This spec is for the new F&B Analytics module only. Some elements may not be valid for all properties, like segment, then ignore that.
| # | PMI data element | Description | Mandatory / Optional | Comment |
|---|---|---|---|---|
| 1 | Property ID and/or name | Identification of the property (hotel, restaurant) | Mandatory | The import flow for a property is mostly set up per property. In this case the property identifier is specified in the flow. If a data set (file) includes data for multiple properties, the property identifier needs to be part of the data set (file). |
| 2 | Department ID and/or name | Identification of the department within the property | Mandatory | This field is mandatory if the file contains more than one unit. |
| 3 | Date and time stamp | Transaction date and time | Mandatory | Will be used to drill down into daily activity pattern, useful for planning and staffing |
| 4 | Account ID and/or name | Identification of the account | Mandatory | |
| 5 | Aticle ID and/or name | Identification of the item sold | Mandatory | The items sold will be mapped to item category like starter, main or dessert/wine, beer, non-alcoholic. And mapped to a higher level, i.e. Food and Beverage |
| 6 | MealPeriod ID and/or name | Identification of the meal period | Optional | Required when using covers. If this field is not available in the source system, the records can be grouped based on time of the day. |
| 7 | Table number | Which tables are sold | Mandatory | Mainly used to identify number of tables sold |
| 8 | Check number | Identification of checks | Mandatory | Used to link sales to covers and segments |
| 9 | Covers | Number of covers/guests | Mandatory | Required when using covers. |
| 10 | Cover segment | Inhouse, External etc. | Mandatory | |
| 11 | Revenue | Revenue without VAT and other authority charge rate | Mandatory | If the revenue includes VAT this can be corrected in the mapping. Only one percentage can be used in the mapping to subtract additional charges. Note: Usually, revenue registered in POS (e.g. Micros) is automatically fed to PMS (Opera). However, adjustments (at higher level) are often made in PMS without these changes being fed back to POS. Therefore, it is common that revenue in PMS is used to update in PMI – not revenue from Micros. |