On this page
Occupancy — PMS
Plan hotel occupancy context for Mobility and distinguish occupancy from presence or network usage.
The planned occupancy module adds hotel demand context to Mobility using aggregate data from a property management system (PMS). It is in development; the scope below describes the intended model, not an available setup procedure.
What occupancy describes
The model distinguishes occupied rooms from guests and actual figures from forecasts. A hotel can have similar room occupancy on two nights and a different number of guests. Those values answer different questions and should retain their denominators when compared.
| Input | Meaning |
|---|---|
| Business date | The hotel-local date to which the occupancy belongs |
| Actual or forecast | Whether the figure describes reported occupancy or expected demand |
| Rooms available and occupied | The basis for room occupancy |
| Guest capacity and guests | The basis for guest occupancy |
| Optional room-type detail | Additional breakdown below the whole-hotel aggregate |
The intended input is aggregate occupancy. It does not require guest identities or individual room-stay records.
Plan the mapping
Identify the Lens location corresponding to each property, its local business-date convention, and the source fields for each total. Agree how corrections and updated forecasts will be supplied. Keep actual and forecast figures distinguishable throughout that process.
Before using a comparison, check whether the relevant dates have data and whether the latest delivery includes corrections. A forecast is context for expected demand, not evidence of the number of guests who actually stayed.
Read occupancy alongside WiFi
Compare matching properties and clearly defined periods. Higher occupancy can provide a useful reason to investigate a change in measured WiFi conditions, but PMS data does not measure connected devices or traffic.
Hotel occupancy also does not locate people by building, floor, or area. It must not be described as spatial presence or used to imply live crowd counts on a floor plan.
Plan the source mapping, then read how to interpret these figures alongside WiFi.
Plan PMS data mapping
The occupancy module is in development. This page is a planning guide for an integration, not an activation procedure.
Identify the source
For each property, identify the PMS owner, the Lens location, and the hotel’s local time zone. Agree which source fields represent rooms available, rooms occupied, guest capacity, and guests. Keep actual and forecast figures distinct; a forecast can be revised before the night occurs.
The planned input uses whole-hotel daily aggregates, with optional detail by room type. It does not require guest names, individual room stays, or live device locations.
Check mapping quality
Choose a few dates with known totals and reconcile them with the source report. Confirm that a date refers to the same hotel-local night in both systems. Decide how corrections and updated forecasts will be delivered and who will notice stale data.
An enabled module does not establish that an integration delivered data for a specific date. Plan a freshness check before any operational comparison.
Interpret occupancy alongside WiFi
The planned occupancy view adds hotel-level demand context to Mobility. It is in development. Use this explanation to plan analysis questions; do not treat current sample PMS panels as integrated data.
Match the period and property
Check that the occupancy date and WiFi period refer to the same property and compatible local time window. Room occupancy and guest occupancy have different denominators. A percentage by itself cannot tell you which one was used or how many people were present.
Compare actual figures with measured WiFi where possible. A forecast is useful for planning expected demand, but it is not evidence of the night that occurred.
Keep interpretation bounded
Higher guest occupancy can motivate an investigation of network behavior under demand. It does not measure concurrent WiFi devices or prove that demand caused a coverage problem. An empty WiFi area is still a measurement gap, whatever the hotel occupancy figure says.
Occupancy is aggregated at hotel level. It cannot establish presence on a floor or in an area, and it does not populate Mobility’s 2.5D map with people.