Geofencing
The creation of virtual boundaries in RTLS software that trigger automated actions when assets or personnel enter, exit, or dwell within defined areas. Enables location-based automation including alerts, access control, and process verification. Geofences can be simple shapes or complex 3D volumes, static or dynamic based on operational conditions.
Functionality that triggers actions or generates alerts when tracked assets or personnel cross virtual boundaries (geofences). Geofencing is core RTLS capability enabling location-based automation and monitoring. Geofencing event types: (1) Entry events - tag enters defined geofence, triggering entry timestamp recording and optional entry actions. (2) Exit events - tag leaves geofence, recording exit timestamp and triggering exit actions. (3) Dwell events - tag remains in geofence exceeding specified duration threshold, indicating process completion, delays, or anomalies. (4) Proximity events - tag approaches but doesn't enter geofence (warning zone). Geofencing actions include: visual/audible alerts (notifying operators or security personnel), automated logging (recording zone transitions for analytics and compliance), external system integration (triggering MES operations, updating WMS inventory, notifying ERP), physical control (door unlocking, barrier operation), and workflow triggers (initiating next process step). Geofencing applications: access control (restricting unauthorized personnel from hazardous or secure areas), process tracking (confirming work items progress through required process steps in correct sequence), safety enforcement (alerting when pedestrians enter forklift traffic zones), dwell time monitoring (identifying bottlenecks from excessive dwell times), and inventory management (tracking material movements between zones for automatic inventory transactions). Geofencing performance requirements: detection latency 0.5-2 seconds typical (time from actual boundary crossing to event detection), false positive rate under 5% (incorrect triggers undermine user confidence), and false negative rate under 2% (missed events create compliance and safety risks). Proper geofence design critical - boundaries should provide adequate buffer zones accounting for positioning accuracy (typically 2-3x position error tolerance).