Mobility setup guide

Mobility setup gives WiFi observations a site and spatial context. Decide which location and areas you want to investigate, and who owns the data collection and interpretation.

Prepare the site

1. Confirm the location is available to the intended users and has the correct property context.
2. Build the spatial model: buildings, floors, floor plans, and areas used for analysis.
3. Record the relevant networks and access points. Separate infrastructure inventory from what a device actually observes.
4. Prepare Android devices for the measurements the program requires.
5. Configure the collection deployment for a small pilot, then verify the data.

A plan or area boundary does not create observations. A device without the required access may report to Lens yet provide no usable WiFi scan or position.

Verify the site

Open Analyze → Pulse for the location and a period containing the pilot. Check the reading count and how many areas can be judged. If the area of interest has too few readings, extend or correct collection before interpreting its color.

Mobility WiFi infrastructure

Mobility uses WiFi infrastructure context to investigate what devices observe. A network is a service identity seen by devices; an access point is a piece of radio infrastructure that may advertise one or more networks.

The location workspace has an access point panel. A configured access point and an access point detected during a scan are related but different facts. The first describes inventory; the second records an observation from a device at a time and place.

Plan the inventory

Record the networks relevant to the study and the access points that the site can identify reliably. Use a naming convention that site staff can maintain. For each access point, verify its floor and placement before using it as map context.

Do not infer coverage from a list of installed access points. Measurements are still needed to see what devices experienced in particular spaces and periods.

Mobility WiFi networks

A network is the WiFi service a device sees or uses. The same network name can appear through several access points, across floors or buildings. Filter by network in the Report view when you need to narrow the observations.

What a network filter answers

A filtered view shows observations associated with the selected network in the chosen site and period. It does not prove that other networks were absent everywhere: scanning depends on device capability, permissions, and where and when the device traveled.

When a device reports a current network, distinguish it from other networks it detected nearby. A device may see a network without joining it. Check the metric and the intended question before treating scan results as a connection test.

Plan consistent names

Agree which network names are in scope, including guest and operational networks if both matter. Network names alone do not identify a physical access point or guarantee that authentication and internet access worked.

Mobility access points

An access point is radio infrastructure at a site. Mobility can represent known access points in the location workspace and show access point observations during WiFi analysis.

Check identity and place

Confirm the access point’s identity and intended floor with the network team. A label without a reliable radio identifier can lead to confusion when names are reused. Place the access point on the correct plan so that map context helps interpretation.

Read a detected access point

A device hearing an access point establishes that it detected a radio at a particular time and place. Signal strength varies with the device, band, obstacles, and position. A strong signal does not establish service reachability or throughput.

In Diagnose, compare the access point finding with the number and distribution of contributing readings. An access point appearing in sparse evidence deserves verification before hardware changes.