Description
The parking time event is a crucial aspect of fleet management, as it provides valuable insights into the efficiency and productivity of your fleet operations. By monitoring and analyzing parking durations, managers can optimize vehicle usage, reduce idle time, and enhance overall fleet performance.
Understanding the importance of parking time events allows fleet managers to:
- Improve route planning: Analyzing parking time data helps identify patterns and trends, enabling managers to optimize routes and schedules, reducing unnecessary downtime and increasing productivity.
- Monitor driver behaviour: Tracking parking time events enables managers to evaluate driver habits, ensuring that they adhere to company policies and take appropriate breaks while minimizing unauthorized stops.
- Enhance fuel efficiency: Excessive idling during parking can lead to increased fuel consumption. By monitoring parking time events, fleet managers can address this issue and implement strategies to reduce fuel costs.
- Increase vehicle utilization: Identifying underused vehicles based on parking time data allows managers to redistribute resources more effectively, maximizing the return on investment for each vehicle in the fleet.
- Ensure regulatory compliance: Monitoring parking time events helps ensure that drivers comply with local regulations, such as mandatory rest periods and parking restrictions, avoiding potential fines and penalties.
The Parking Time rule is designed to notify users when the system detects parking durations exceeding a specified limit. This rule generates alerts whenever the allowed parking time is surpassed, enabling your clients to stay informed about instances where drivers exceed the designated parking time limit.
For example, if users need to monitor the parking duration for drivers within their organization or another entity, and this duration should not exceed 30 minutes according to their standards, you can utilize this rule. By doing so, they will receive notifications in the user interface, via email or SMS, when a driver violates the specified standard. They can also build reports and review the historical timeline of when these events occurred.
Settings
Allowed Parking Time:
The parking time starts counting from the moment the vehicle enters the parking state. You have the flexibility to set an interval ranging from 5 to 60,000 minutes. Once the vehicle transitions out of the parking state (Parked), the allowed time resets. For a detailed understanding of how parking detection works, please consult the article on Parking Detection.
Geofence:
Fill out the section if the rule needs to work only inside/outside of the selected geofences.
Bind zone to rule:
Enables geofence rule binding.
Map button:
Shows bound geofences on the map.
Notifications
Emergency notification:
is used for important events. A message on the screen and the sound signal can only be disabled by clicking on the notification. Please note, some browsers can block notification sound until user activity is recorded on the page.
Push notifications:
Receive push notifications on the mobile app and web interface.
Add geofence name to the notification:
Adds names of the specified geofences to the notification text. This option is available only when the "Inside" geofence binding radio button is selected on the "Settings" tab.
SMS notifications:
List of recipients for SMS notifications when the event occurs.
Email notifications:
List of recipients for email notifications when the event occurs.
Schedule
Set a schedule for when the rule will run. If your schedule indicates that the event should not run some day or time period, it will not appear as a notification in the user interface, and notifications via SMS or email will not be sent. Additionally, you can choose a default template for quick scheduling.
The platform specifics
- The "Parking Time" alert has a 10-second reset timer, meaning the alert event will not occur more often than once every 10 seconds. If this type of event occurs in time the rule has been waiting for the reset, this event will be omitted by the platform, including the reports.
- This rule is a generic type and is not specific to any particular hardware, which means it can be applied to multiple trackers simultaneously. This allows for the selection of several trackers within a single rule.
Event reports
To view the dates when the events were received, you can build the "Report on all events" report.
