Migrate Spaces Connector 2.x to Connector 3 Click here >>

Proximity Reporting

This application shows the history of where a person was in a network based on the devices they carry and the other devices that were in the same area. This is used to assist in contract tracing.

Proximity Reporting provides a history of where a device has been and a report on which other devices were in the same zone, floor and building. The App will also report on the count of the number of devices that have been in contact with the reporting device. ​

Use Cases & Value

Show the history of where a device has been in last 1 to 30 of days (default 15) and which other users and devices that have been in same space​.

History of where a device has been​

There are two versions of device history: 1) an aggregated history that shows the buildings, floors and zones that a user has been at, aggregated over the time frame of the report 2) view history as a day-wise journey to help a user remember where they were on specific days to assist in a contract tracing interview.

Useful to: The Work Place Resources (WPR) groups that are responsible for cleaning and rectification of spaces that have been visited by a person who is self reporting.

Value Delivered: WPR will now need to only clean areas that are known to have been visited instead of cleaning the entire campus when there is a self reporting individual.​

List of users that have interacted with the device​​

Get to know which other users (based on their devices) the target device was in contact with during the target period of the report. The duration of contact is aggregated over the time period and is broken into groups for: 1) More than 4 hours, 2) less than 4 hours 3) more than 15 mins and 4) less then 15 mins. From a distance perspective, the report is broken down into – 30ft from target device, same floor, but more than 30ft and same building but different floor.​

Useful to: HR departments that need to inform users that they have been in close contact with the person who self-reported

Value Delivered: Reduces the people that need to be notified from all users of the enterprise to only those who may have been impacted.​

Data Quality

Learn how we filter data to reduce noise & how you can increase the accuracy of your counts ​

Current Methodology​​

  • Associated users are searched by their USERNAME​
  • The USERNAME is matched to specific devices that they used on the network for the report duration time,​
  • This information is then matched with other users on the network to create a list of who the person was in contact with​

Implications for verticals​​

  • The method of how users are associated to wireless is very important. If user get on WIFI via a captive portal, this solution will not work.​
  • The solution is designed for WorkSpaces, Education and MFG​
  • The solution is not designed for Hospitality or Public Venue ​

Prerequisites for accuracy of Proximity Reporting​

  • The data for the Proximity report is based on the Wi-Fi calculated location of the devices. The data will be best when a location quality Wifi network is deployed. The accuracy of the location of each individual is normally +/-30ft/10M. The accuracy of the location of the individuals who were in the same space is also dependent on the quality of the uploaded MAPS and AP placement.​​

Disclaimer: Please note that due to the nature of Wi-Fi signals, there is no guarantee as to the accuracy of the data provided in the Proximity Reporting Application. The data about where the designated user has been as provided by the Proximity Impact report is based solely on information collected when that user’s associated device is on and connected to WIFI, and is dependent on the maps and accuracy of the location of access points. The report includes information about other users and associated devices that may have been in the proximate area as the designated user for varied amounts of time, but is also limited based on the accuracy of WIFI and collection of data only when devices are associated to WIFI. Accordingly, the Proximity Impact report is provided “as is” for your reference without any warranties of accuracy, whether explicit or implicit. ​

Please complete the following pre-requisite for access to Proximity Reporting. The app requires Detect and Locate to be functional before it can be enabled. The app has separate Role Based Access Control (RBAC) and requires users be invited to this app in order for them to use it. ​

Step 1: Complete Cisco Spaces Onboarding Process​

P.S. : The above process needs to be done only once. It is not repeated for every app. Please ignore if already completed.​

Step 2: Setup & test Detect & Locate​

  • Setup and test Detect and Locate. Find a userID and show the history of the user. This is the source for Proximity reporting​
  • Invite users to the Proximity Reporting capability in RBAC.​
  • Create a test report by finding a username for testing that has been associated to the network some time in the last 14 days and run a test report.​

Please take a moment to check if you’re able to successfully setup and use the app. Click on ‘yes’ to indicate it’s working for you. And on ‘Not yet’ if you want any assistance .​​