Geofencing zones are virtual elements in the positioning systems that define safe and dangerous zones.
When the geofencing zone violation event occurs, the system does some actions. It can be, among others:
Geofencing zones can be static within the map or move along with mobile objects, for example, forklifts, AGVs, or cranes.
Geofencing zones around dangerous objects:
Preventing people from climbing stairs:
Preventing people from standing under the crane load:
Preventing forklifts hitting AGVs:
Static geofencing zones are defined on the map. They define either safe or dangerous zones, But the key characteristic of them that is effectively a property of the map – not mobile objects.
Static geofencing zones are supported by the system and do not require any special SW development or additional customization.
Mobile geofencing zones are significantly more complex than static geofencing zones and typically require additional customization because each case is unique.
Geofencing zones can be 2D and 3D. For example, if you want to prevent people from climbing stairs, you can set an upper limit for people’s mobile beacons. When their measured Z coordinate exceeds the limit, the person will be warned, and the record of the violation will be done in the system.
A similar approach can be used for drones – to prevent them from flying lower than allowed to the floor or closer than allowed to some objects.
Along with the location coordinates (XYZ for 3D or XY for 2D or X for 1) of your mobile beacon, you get many other pieces of information, for example:
So, by interpreting the data received from your mobile beacon or modem, your external system can automatically make decisions to ring an alarm or even stop machines or engines and prevent accidents.
The protocols are open and readily available.
Effectively, everything that is streamed is also recorded in the log file. Thus, it is possible not only to react immediately when a geofencing zone violation occurs but also to use the log file for a post-event analysis and the lessons-learned.
The Log File format is also described in the Protocols PDF.
In some cases, interpreting the protocol and extracting geofencing violation data is too complex for the external device, particularly when interfacing with simple devices. In this case, it is possible to use a pin, for example, on the Super-Beacon. The pin will be turned into the opposite position when the geofencing zone violation occurs.
Thus, it is possible to control the simplest devices, such as alarms or control engines, with just two wires: alarm and ground wires.
The functionality is enabled by a special SW license: MMSW0006: Dedicated pin for geofencing alarm.