Key Performance Indicators (KPIs) are readings from vehicles that you monitor in the dashboard. The dashboard monitors when vehicles in a fleet fail to meet target values on these indicators.
To specify which KPI targets are used when the dashboard displays information about the fleet associated with a node in the hierarchy:
-
From the Tasks section of the navigation bar choose Hierarchy. The Hierarchy screen opens.
-
Select the node in the hierarchy.
-
Click Configure
at the top of the hierarchy panel.
-
For each KPI in the Configuration dialog box, specify if the node should inherit the configuration from the parent node, or if not, specify which target should be used for that KPI.
-
Click Save to save the configuration for the node.
To specify which KPI targets should be applied to a vehicle:
-
From the Tasks section of the navigation bar choose Hierarchy. The Hierarchy screen opens.
-
Select the node that the vehicle is assigned to.
-
Select the Vehicle tab on the Details panel.
-
Select the vehicle or vehicles to configure.
-
Click Configure
-
For each KPI in the Configuration dialog box, specify if the vehicles should inherit the configuration from the node to which they are assigned, or if not, specify a new target value for the KPI.
-
Click Save to save the configuration for the vehicle.
The Configuration dialog box might vary, depending on which KPIs you have displayed on your dashboard screen. It displays KPI targets using multiple tabbed pages, as described below. You only see the pages that are relevant to your KPIs.
The Times tab lets you set targets for when the vehicle starts and ends each day. It might also let you indicate if the vehicles this setting applies to belong to a supervisor. For each setting, you can enter an override value, or select the Inherited check box to accept the value inherited from the parent node in the hierarchy. The following table lists the targets you can set using the Times tab:
|
Value |
Purpose |
|---|---|
|
Is a Supervisor vehicle |
When selected, all vehicles in the fleet for the node (or the vehicle being configured) are driven by the supervisor. |
|
Start Time |
The time when the vehicle should first start moving at the beginning of the day. |
|
End Time |
The time when the vehicle should stop moving at the end of the day. |
|
Start Time Buffer |
The number of minutes on either side of the start time that the vehicle can first start moving without generating a dashboard event. |
|
End Time Buffer |
The number of minutes on either side of the end time that the vehicle can stop for the day without generating a dashboard event. |
|
First Ignition Start Time Buffer |
The number of minutes on either side of the start time that the vehicle can first turn on the ignition without generating a dashboard event. |
|
First Ignition End Time Buffer |
The number of minutes on either side of the end time that the vehicle can turn off its ignition at the end of the day without generating a dashboard event. |
The Restricted Hours tab lets you specify when vehicles may or may not be used. For each setting, you can enter an override value, or select the Inherited check box to accept the value inherited from the parent node in the hierarchy. The following table lists the targets you can set using the Restricted Hours tab:
|
Value |
Purpose |
|---|---|
|
Restricted |
When selected, all vehicles in the node for the fleet are restricted to be used only during certain hours. |
|
Start Time |
The earliest time of day that a vehicle can be used without generating an Off Hours dashboard event. |
|
End Time |
The latest time of day that a vehicle can be used without generating an Off Hours dashboard event. |
|
Days |
When any day of the week is selected, using a vehicle on that day of the week (at any hour) generates an Off Hours dashboard event. |
The Thresholds tab lets you specify target values for individual KPIs. For each setting, you can enter an override value, or select the Inherited check box to accept the value inherited from the parent node in the hierarchy. The possible target values depend on the KPIs you have on your dashboard, and the units for each KPI are given in the label for each item.
The Speeding tab lets you specify how much a vehicle can exceed the posted speed limit before the dashboard reports a speeding event. It can make sense to allow a vehicle a bit more "grace" for high speed limits than when the speed limit is very low (for example, going 10 MPH over a speed limit of 60 is very different than going 10 MPH over a speed limit of 15). Because of this, you can set two different amounts by which a vehicle can exceed the speed limit: one for high speeds and one for low speeds.
Note that for the dashboard to report a speeding event, the GPS quality for points from the vehicle must be good or excellent. For each setting, you can enter an override value, or select the Inherited check box to accept the value inherited from the parent node in the hierarchy. The following table lists the targets you can set using the Speeding tab:
|
Value |
Purpose |
|---|---|
|
Speeding Threshold |
The cutoff speed that determines whether a speeding event is determined by the "after limit" or "before limit" amount (see below). |
|
MPH over speed limit after limit |
The amount by which the vehicle can exceed the posted speed limit (not a speed category) when the posted limit is greater than or equal to the Speeding Threshold value. |
|
Ignore speeding after limit |
When selected, the MPH over speed limit after limit is not used. |
|
MPH over speed limit before limit |
The amount by which the vehicle can exceed the posted speed limit (not a speed category) when the posted limit is less than the Speeding Threshold value. |
|
Ignore speeding before limit |
When selected, the MPH over speed limit before limit is not used. |
Comments
0 comments
Please sign in to leave a comment.