Spatial model

Mobility uses a 2.5D spatial model to organize a site’s buildings and floors and place its floor plans and areas in context. This model belongs exclusively to the Mobility solution.

The elements of the model

2.5D describes floors in their building context while retaining a plan-based view of each level. It does not imply a navigable three-dimensional building model.

The Pulse example shows a floor with three measured areas and one area with too few readings.

For practical setup, follow Buildings and floors, Floor plans, and Areas.

Choose useful boundaries

For a fictional hotel, a lobby, a meeting space, and a guest corridor may need separate interpretation. A single broad area can conceal differences between them; too many small areas can leave little evidence for each one. Choose a useful level of detail for the measurements you can actually collect.

Keep the distinction between an area and the devices that observe it. Drawing an area does not make a device report from there, and adding a floor plan does not generate measurements.

Check the context before interpreting a map

Confirm the building and floor, the plan being displayed, and the selected period. Then check whether observations are available in the space being investigated. Treat unmeasured space as a gap in evidence rather than a successful or failed measurement.

A hotel-level occupancy figure does not populate this spatial model with guest positions. Occupancy by hotel and presence by area are separate capabilities; the planned PMS module concerns the former.

Mobility buildings and floors

Buildings and floors provide the hierarchy for Mobility’s plan-based view. Before editing, confirm the physical naming with the site owner and decide which spaces are in the initial collection scope.

Build the hierarchy

1. Open Deploy → Locations and select the intended location.
2. In Buildings and floors, add each relevant building and then its floors.
3. Use names that distinguish repeated levels, such as a lobby level in different buildings.
4. Check the building and floor tree before adding plans or areas. If a floor is under the wrong building, correct it before attaching further context.

A ground or exterior level may also be present for spaces outside a building. Treat it as site context, not as proof that exterior WiFi has been measured.

Verify the result

Select each floor and confirm that the map and tree refer to the same level. Then continue with floor plans and areas. For a measured site, inspect Pulse to verify that readings appear in the expected level.

Mobility floor plans

A floor plan is a visual reference attached to a floor. Its usefulness depends on matching the actual level and placing it correctly on the map.

Add a plan

1. In Deploy → Locations, open the location and select the intended building and floor.
2. Use the map’s plan controls to upload the approved plan for that level.
3. Place and align the plan against known site features. Confirm its orientation and extent with someone familiar with the building.
4. Reopen the floor and verify that the plan and building label are still correct.

Use a plan that is permitted to be shared with the people who can access this location. A plan with the wrong scale or orientation can make correctly collected observations appear misplaced.

Verify analysis context

After devices report, compare visible areas and observations in Pulse or Diagnose with known spaces. If the plan is correct but readings sit elsewhere, investigate device positioning and area boundaries before moving the plan to fit the data.

Mobility areas

An area is a space within Mobility’s spatial model. The current location editor calls mapped areas zones. Define them around meaningful operational questions, such as a lobby, meeting room, or exterior pool area.

Define an area

1. Open the intended location and floor in Deploy → Locations.
2. Select Zones in the spatial workspace and use the drawing tools on the map.
3. Give the area a recognizable name and check its boundary against the floor plan.
4. Repeat for the spaces in the pilot collection scope.

Avoid overlapping or ambiguous boundaries where a device’s observation could be attributed to an unexpected area. Use the fewest areas that still let stakeholders distinguish the problem spaces.

Verify the evidence

Open Pulse for a period with readings. Check whether each area is measured, too sparse to judge, or unmeasured. The fictional MareaClara example shows all three kinds of evidence on one floor. Redraw a boundary only if it is spatially wrong; increase or repair collection if the area is simply under-sampled.