Tracking

1. Choose this method for a single color per route.

2. Select the route’s color from six options: red, blue, green, light gray, black, and brown.

Select this method if you want to:

• View a unit’s tracking history without speed details.
• Generate multiple tracks on the map for one or multiple units simultaneously, using a different color for each track or unit.

1. Choose this method for a multi-color route based on the unit's speed.

2. By default, each color will represent a different speed range:

• Green: 0–60 km/h
• Yellow: 60–100 km/h
• Blue: 100–120 km/h
• Purple: 120–150 km/h
• Red: 150+ km/h

Select this method if you want to:

• Gain detailed insights into the unit's speed variations along the route.
• Identify speeding violations instantly without reviewing reports or unit events, while determining exactly where each speed violation occurred.

To make it easier and faster for users to start tracking their units, the system provides four predefined date ranges for generating tracking history: Today, Yesterday, Last Week, and Last Month.

If none of these options suit your needs, you can select a custom date range by setting the interval.

Enter the start date and time, as well as the end date and time, for the period in which you need to generate the unit’s track (Manually or by clicking these icons ).

Enter the exact start date and time (Manually or by clicking these icons ).

Select this option to generate your unit’s track from a specific past date and time up to today.

Enter how far back you want to track by selecting a certain number and a time-measuring unit (minutes, hours, days, weeks, months, or years).

Check the Include Current box to include the current minute, hour, day, week, month, or year.

Annotations mark geographical points where the tracking device attached to the unit sends updates to the server. Each update includes the unit’s speed, date and time.

Events are notifications sent to users to report road violations such as over speeding, crossing geofences, or harsh braking. They can also serve as reminders for upcoming services like oil changes, license renewals, or Iqama renewals.

For example, if you add an over speeding event to your unit and set the speed limit to 80 km/h, you will receive a notification if the driver exceeds this limit. The event will also appear on the generated track on the map as a capital ‘E’ symbol.

Hovering over this symbol with your mouse will display a popup containing the event’s date, time, location, and type.

Stops refer to the periods when the vehicle is not in motion. These stops can occur for various reasons, such as fueling, resting, troubleshooting, emergency situations involving the road or driver, and many others. Each stop is recorded in the vehicle’s history, and a stop icon will appear on the generated track whenever the vehicle halts.

When you hover over the stop icon, a popup will display detailed information about the stop, including the date, time, address, and duration of the stop.

Stoppage times can be customized based on the user’s preferences. Typically, stops last no longer than 5 minutes, but users can set alerts within the system to be notified if a stop exceeds the desired duration or if the vehicle remains idle for too long.

Parking refers to the time a vehicle spends in a designated parking space. The key distinction between stops and parking lies in the engine status. While a stop occurs with the engine on and speed at 0 (Engine on, speed = 0), parking is marked by the engine being off (Engine off). Additionally, parking durations are typically longer than stops, often lasting hours, days, or even longer.

Parking mostly takes place in parking lots or garages, while stops are usually observed on the road. Every time the vehicle is parked, a parking icon will appear on the generated track.

When you hover over the parking icon, a popup will display the date, time, address, and duration of the parking event.