Geolocation

When logging into Mobile with geolocation (geo-fencing) enabled (via the log-in screen), the applications asks the user via the Confirm Site pop-up if he/she is within a certain distance to the nearest known site. If the user is outside of the geofence of the nearest known site location, then the system does not ask for site confirmation and does not associate this log-in to that site.

The goal of the geolocation functionality is to allow users to associate themselves in vx Suite to a nearby known site location while allowing for variations in the accuracy of different devices used to pinpoint users' locations. Clients may have different standards and allow the location and accuracy of their users and devices to fall in different ranges. Therefore, every client using mobile should log in to the central application and set an accuracy threshold under Client Admin. To configure the accuracy threshold, clients must complete the form on the Mobile Settings screen in the central application: Sites > Organizations > (Select HQ) > Admin > Mobile Settings.

The following fields are included on this page:

• Geofence Setting: These settings may be defined at the Client, Site, or Site Type Level.
• Geofence Units: The client must select how the distances will be measured, by Meters (m), Kilometers (km), Feet (ft), Yards (yd), or Miles (mi).
• Geofence: Free text field that tells the system how close the user must be to a site in order for him/her to be associated to that site.
• Accuracy Threshold: Free text field defining how much additional leeway in range the user is given; the accuracy of the user's device must be less than this value.
• Default Site Location Order: In Mobile, when the user wishes to Change Location, the pop-up will generate with a list of sites sorted by the order type selected here, either Alphabetically (by site name/number) or by Proximity (by distance from current location); default is Alphabetically.

To determine the on-site status of the user, the system first takes into account the accuracy of the technician's device and if it is within the defined Accuracy Threshold. Then the system compares the user's distance from the site to the Geofence (plus or minus the accuracy). If they are within this range, the user may associate to this site.

Example: If the Geofence is set to 200m, the accuracy of the technician's device is 350m, the Accuracy Threshold is set to 500m, and the reading of the technician's location is 600m away from this site, then the technician is not considered to be at the site. The problem here is that the technician's location is greater than the combined value of the defined Geofence and the accuracy of the technician's device.

Example: If the Geofence is set to 200m, the accuracy of the technician's device is 750m, the Accuracy Threshold is set to 500m, and the reading of the technician's location is 600m away from this site, then the system rejects the association to the site and the Work Order History displays "NA" for the At Site field. The problem here is that the accuracy of the technician's device is greater than the defined Accuracy Threshold. In other words, the accuracy is so poor that the system should not consider the latitude-longitude of the technician to be accurate.

The Mobile Dashboard Admin screen displays all site and client mobile dashboards currently configured in the vx Suite system. Documentation on this configuration can be found here.