Overview
Geofencing is a critical feature in TrackTik, and it is primarily used to manage and monitor personnel movements at a site level. This guide will cover the fundamental concepts of geofencing, best practices for setting up and managing geofences, and recommendations to ensure optimal performance, accuracy, and compliance. We'll also explore how geofences integrate with mobile app restrictions to control clock-ins and user activities.
What is Geofencing
Purpose of Geofences
- Geofences are virtual boundaries set up at the site level to define allowed and restricted areas for personnel.
- They help manage movement, control clock-ins, and generate alerts when users enter or exit designated areas.
Allowed vs. Restricted Areas
- Geofences can be configured as allowed areas (where personnel are permitted) or restricted areas (where personnel should not enter).
- Example Use Case: Setting up a restricted geofence prevents guards from lingering at nearby locations like a café.
Best Practices
Geofence Placement
- Geofences should be set up around site properties rather than at the zone level.
- If needed, geofences can be set up at a zone (e.g., for a central HQ), but this is only useful for specific scenarios like managing clock-ins at a head office.
Geofence Creation
- Use the Geofencing Setup Guide for detailed steps.
- Ensure the site address is accurate and recognized by Google Maps. This will create a geocode for the site and allow the map to center on the site.
Geofence Design
- For allowed areas, create a slightly larger boundary than the physical site to avoid false alerts.
- For restricted areas, define boundaries precisely to prevent entry into prohibited zones.
Managing Alerts and Notifications
- Configure alerts to trigger for exiting allowed areas or entering restricted areas.
- Limit notifications to prevent overwhelming users with redundant alerts (e.g., avoid triggering alerts for exiting restricted zones or entering allow zones).
Adjusting GPS Accuracy
- Adjust the GPS accuracy settings (in meters) to balance precision and reliability.
- Default GPS accuracy should be set to less than 50 meters to minimize false alerts while maintaining accurate tracking.
Custom Notifications
- Create custom notification rules for geofences, as there is no default setting.
Integrating Geofences with Mobile App Restrictions
Mobile App Clock-In Restrictions
- Ensure clock-ins are only allowed within defined geofences to prevent unauthorized clock-ins outside the site.
- The Block Clock In When Not in Range option enforces this rule.
- For sites with inconsistent GPS signals, enable Permit Clock In and Open a System Exception to allow clock-ins while flagging exceptions for review.
Mobile App Login Restrictions
- While separate from geofences, login restrictions control whether users can access the mobile app based on site assignments.
- Configure this to ensure only authorized users can log into devices at specific sites.
Monitor GPS Tracks and Exceptions
- Use the tracks feature to monitor user movement within geofences, distinguishing between GPS pings and activity logs.
- Green pings represent periodic location data, while Red activity logs detail specific activities like clock-ins, checkpoints, and reports. NOTE: Activities will center on the screen regardless of GPS location. The Red activity dots can be used simply as an activity timeline, while the Green GPS pings will act as the user's location during the timeline.
Best Practices for Monitoring Geofence Logs and Events
Events vs. Logs
- Events: Show specific occurrences, like entering or exiting a geofence. These are more focused and capture movement across geofences.
- Logs: Capture all GPS pings within geofences, providing a detailed list of device interactions. Export logs for analysis, particularly when troubleshooting geofencing accuracy.
Data Exporting
- Export events and logs to CSV or Excel for detailed review, especially for compliance tracking and performance evaluation.
Adjusting GPS Settings
- If GPS pings are inconsistent or inaccurate, adjust settings
- GPS accuracy should be less than 50 meters for general use and less than 25 meters for more precise tracking.
- Modify GPS ping rates to 3 or 5 minutes based on site needs and device battery capacity.
Troubleshooting common issues
Inaccurate GPS Data
- GPS location data can be impacted by external factors such as poor or inconsistent data service (e.g., weak cell signal, being indoors or underground), the quality of the mobile device, and similar conditions. For improved performance, it is recommended to use high precision mode and connect to Wi-Fi when possible.
Frequent False Alerts
- Increase the minimum GPS accuracy setting and slightly expand allowed geofences to reduce false exits or entries.
No Geofence Logs
- Ensure at least one geofence is active at the site. Geofence logs will only populate if a geofence exists.