Introduction

Active Insights leverages rich data to provide clear and compelling push-based insights for fleet managers. Using our data analysis and AI models, Active Insights helps transform your data into measurable cost savings by recommending what you can do to optimize your fleet.

Using Active Insights

Insight Card Overview

Select Dashboard & Analytics > Active Insights on the Fleet Management Application menu to open the Active Insights page and view insight cards for each insight applicable to your fleet.

Insight cards may contain the following components:

Potential Savings YTD Recent issues Category Most savings Take action

These components are explained in the following sections.

1. Potential savings YTD

The estimated potential savings value (USD) for your fleet, if you take the recommended action for this insight. It is based on the number of issues that have occurred since the beginning of the year.

The calculation is unique for each insight.

For example, for the insight Water in Fuel Detection:

• Potential Savings YTD = Average cost of maintenance activities required for water in fuel incidents that go unnoticed ✕ number of Water in Fuel Detection events identified by Active Insights within the year

The number of detections within the last 7 days.

3. Category

On the Active Insights page, you can filter by category to suit your needs and priorities:

• Manage
• Maintenance
• Safety

4. Most Savings

The top three insight cards that offer greatest fleet optimization opportunities (based on taking the recommended actions) are tagged as Most savings, 2nd most savings, and 3rd most savings.

5. Take action

Click Take action on an insight card to view detailed information about an insight and implement recommendations. For example, you can click Take action on the Collision Detection insight card to go to the Collision Detection page.

The Overview panel shows the number of identified issues, potential savings and calculation details.

Active vs. Hidden Insights

Insights are categorized automatically as Active or Hidden.

Active means that the recommended call to action (e.g. setting up the notification rule) was applied. Click the Active tab to reduce visual clutter and focus on uninvestigated insights.

Hidden means that the recommended call to action was not yet applied. Click the Hidden tab to view information for investigated insights.

Intelligent Zones

Fleets typically create zones to track operational activity, such as visits to customer locations, fuel stations, distribution points, and other areas of interest. While zones are critical for keeping up with day-to-day operations, creating them manually can be time-consuming, error-prone, and quickly outdated.

Active Insights for Intelligent Zones analyzes vehicle stop history to automatically create and manage new zones. You can save time by importing suggested zones instead of creating them manually.

How it works

Intelligent Zones records areas with high stop frequency and then expands them into new suggested zones based on your fleet movement around the area. Not only does this reduce the time needed to create zones, but zones are created more effectively as they correspond to the movement patterns of your fleet. Zones are ranked according to the number of vehicle stops, then assigned a Relevance percentage for analysis.

Intelligent Zones are identified based on a variety of criteria related to your fleet’s driving habits:

• Zones are updated on a monthly basis, and are based on clusters of stops (random stops are not considered).
• Zones must have at least 25 stops over the last 6 months. There are no minimum requirements for number of stops per vehicle, or number of different vehicles.
• Relevance is a measure of how useful a new zone may be to your fleet, and is based on data points such as stop duration, driving duration, idling duration, and so on.

Reviewing the Overview panel

The Overview panel summarizes key data related to Active Insights for Intelligent Zones.

Zones Identified This value represents the total number of suggested new zones displayed on the New Zones page. ✱ NOTE: A maximum of 100 new zones are displayed. Top Cities/Towns Listed The total number of suggested new zones are consolidated based on the city/town in which they are located. Click a city/town name to filter suggested new zones to the selected city/town only. Imported to Zones This value represents the total number of currently suggested new zones that have been imported into the Fleet Management Application database. Imported Identified Zones These values represent the total number of new zones that have been imported into the Fleet Management Application database for all time and within the previous month.

Filtering and sorting suggested new zones

The New Zones page displays up to 100 suggested new zones. You can use filters and sort options to reduce the number of zones displayed on the New Zones page and simplify the new zone import process.

Filter zones by city and/or town

Enter the name of a specific city or town and select the result returned from the dropdown menu.

Sort zones in ascending or descending order

Sort suggested new zones by one of the following:

• Name – Sort by zone name. All new zones are named “New Zone” by default.
• City – Sort by city and/or town name.
• Latest Update – Sort by latest update date. This date represents when the Intelligent Zone was last updated by the Intelligent Zones algorithm.
• Relevance – Sort by relevance. Relevance measures how useful this zone may be to your fleet.

Filter zones using advanced filters

Use advanced filters to display suggested new zones based on specific criteria, such as the number of stops made, the number of unique vehicles in the zone, or the minimum stop duration (in minutes). Press tab or click outside the text field to apply the filter.

Importing new zones from the New Zones page

1. From the Active Insights page, click View Insights on the New Zones card.
2. Click the ellipses on the right side of a specific row and select Import Zone.
3. Review the new zone on the map view and/or enter values on the Zone Details tab and click Save.

Importing new zones from the New Zone Details page

1. From the Active Insights page, click View Insights on the New Zones card.
2. Click a zone name on a specific row to view the New Zone Details page for a single zone.

3. Review the details for the recommended zone.
4. (Optional) Click Rename to change the default zone name provided by the Fleet Management Application.
5. Do one of the following:
6. 1. If you would like to import the suggested zone to your Fleet Management Application database, click Import Zone.
   1. If the suggested zone is not relevant to your fleet and will not be imported, see Archiving Zones and Providing feedback.
6. Review the new zone on the map view and/or enter values on the Zone Details tab and click Save.
7. Click Back to return to the New Zones page.

Archiving zones and providing feedback

Providing feedback on new suggested zones supports continuous improvement of the models used to recommend these zones. If new suggested zones are not relevant to you, do the following:

1. Click Archive to provide feedback on an individual zone or select multiple zones and click Archive Selected. A popup is displayed requesting your feedback on why the suggested zone is not relevant to help improve Active Insights recommendations.
2. Enter your feedback and click Submit to complete the feedback process.

Electrical Systems Rating (ESR)

The Fleet Management Application measures the health of the electrical system of your vehicles to provide an ESR on a scale from 0 to 100.

The ESR scale is based on the following status categories:

• Good – ESR of 35 or above.
• Fair – ESR of 16–34.
• Caution – ESR of 5–15. Indicates that maintenance should be scheduled for the vehicle.
• Poor – ESR of 0–4. Indicates that the battery is likely to fail.

How it works

ESR scores are calculated daily for every vehicle in the fleet. Vehicles with critical ESR ratings (below 15) are displayed on the Electrical Systems Rating page, which can be viewed by clicking View Issues on the Active Insights page. You can also view ESR data for your fleet by selecting Engine and Device… > Measurements and then selecting Electrical System Rating from the Diagnostics dropdown. Click Learn More on the Electrical Systems Rating page to view our definition of ESR and how we calculate the estimated cost avoidance.

Reviewing the Overview panel

The Overview panel summarizes key data related to Active Insights for ESR.

Identified Issues This value represents the total number of vehicles with critical ESR ratings (15 or less) displayed on the Electrical Systems Rating page. ✱ NOTE: If an insight related to a vehicle with low ESR is dismissed and the vehicle continues to have low ESR, it will reappear after 30 days.

Searching and sorting vehicles with critical ESR

You can sort vehicles by ESR rating or by vehicle name to simplify the electrical system review process. You can also search for specific vehicles using the vehicle name or the VIN.

Resolving electrical system issues

Providing feedback on resolved electrical system issues supports continuous improvement of the models used for ESR. Click Resolve and Dismiss to provide feedback and acknowledge that ESR issues with the vehicle were resolved. Once completed, the vehicle is removed from the Vehicles With Critical ESR Ratings list.

Setting up ESR notification rules

1. Do one of the following:
2. 1. Click Setup ESR Rule and Notifications on the top-right of the Electrical Systems Rating page and then click Confirm.

1. Click Setup rule on the popup displayed at the bottom of the Overview panel (if applicable).

2. Notifications are sent to the email address of the Fleet Management Application user when the ESR of a vehicle drops below 15.

2. To edit the default ESR rule and notifications, click Visit Rule page to open the Exception Rule Edit page and do the following:
3. 1. Under the Name tab, name the rule and customize the rule’s color and visibility.
   3. Select the Publish to groups dropdown and select the groups to which the rule will apply.
   4. Under the Conditions tab, set conditions for when the exception rule is triggered using the available headings and their corresponding options.
   5. Under the Notifications tab, add exceptions rule notifications — including emails, alerts, or driver feedback.
   6. Click Save.

Providing feedback

Click Give Feedback to provide general feedback on the usability of this functionality and if you would recommend ESR to other Fleet Management Application users. Your valuable feedback is appreciated!

U-Turn Detection

The U-Turn Detection insight automatically identifies U-turns performed by heavy-duty trucks in your fleet. For many fleets operating class 6 to class 8 vehicles, any routing scenario that requires a driver to make a U-turn is considered undesirable and creates an extra risk of collision. You can use this insight to identify where heavy-duty vehicles are making U-turns to find hotspots to address driver behavior or route engineering.

How it works

U-turns are detected leveraging an algorithm that monitors the vehicle’s speed and position data to identify U-turn maneuvers. This pattern is relatively unique for a machine learning algorithm to understand. These events are translated into a diagnostic_id that is streamed into StatusData in the API. Active Insights and the Fleet Management Application’s Rules Engine can leverage it to generate various types of exception reporting. When the StatusData is set to 1, this indicates a U-turn was detected, and afterwards the reading is set back to 0 when the U-turn is completed. This makes it possible to count the number of U-turns completed by a vehicle or group of vehicles during a period.

Searching and sorting for heavy-duty U-turns

You can narrow vehicles down to only vehicles that performed heavy-duty U-turns by vehicle name to simplify the review process. You can also search for specific vehicles using the VIN or Date Reported.

Details for detected U-turns

To see a detected event in more detail, click the asset name from the U-turn Detection page.

The U-turn detection page displays speed details, a map with the detection location, and event details. Click View speed profile for more information on the speed and braking force. Click View trip in the bottom right corner of the map to see all details of the trip where the U-turn was detected.

Verifying U-turn events

Verifying detected U-turn events supports the continuous improvement of the U-Turn model. Click Verify detection from the table to provide feedback and acknowledge that there was a U-turn, along with any additional comments. Once completed, the table is updated to reflect that this detection has either been confirmed or false.

Creating U-turn notification rules

1. Do one of the following:
2. 1. Click Create U-turn rule on the top-right of the U-turn Detection page, then click Confirm on the U-turn Rule popup.

1. Click Setup rule on the popup displayed at the bottom of the Overview panel (if applicable).

2. To edit the default U-turn rule and notifications, click Visit Rule page to open the Exception Rule Edit page and do the following:
3. 1. Under the Name tab, name the rule and customize the rule’s color and visibility.
   1. Select the Publish to groups dropdown and select the groups to which the rule will apply.
   2. Under the Conditions tab, set conditions for when the exception rule is triggered using the available headings and their corresponding options.
   3. Under the Notifications tab, add exception rule notifications — including enabling emails, alerts, or driver feedback when a U-turn is detected.
   4. Click Save.

Providing feedback

Click Give Feedback to provide general feedback on the usability of this functionality and if you would recommend U-turn detection to other Fleet Management Application users. Your valuable feedback is appreciated!

Collision Detection

You can improve the safety of your fleet by detecting possible collisions. Additionally, you can use the point of impact information to get a better understanding of the collision. The Collision Detection insight allows you to monitor, act, and take the necessary measures to mitigate future collisions by looking at the historical patterns for a specific driver or asset.

How it works

Collisions are detected and classified based on a model that monitors telematics data and applies what it learns as signals in accelerometer data. Due to data granularity, the model can provide details about a collision, such as point of impact, magnitude, trigger type, location, time, and more. A collision is detected when the force goes above 2.6g. Once a collision is detected, it is translated into a diagnostic_id that is streamed into StatusData in the API.

Searching and sorting for collisions

Search for particular assets to see if they have been in any possible collisions by asset name or VIN to speed up the review process. Sort the collisions by asset name, VIN, date and time, or detected location. You can also filter the results by date range. The default date range is the last four days for the majority of databases.

Viewing details for detected collisions

To see the detected event in more detail, click the asset name of the event in the table.

The Collision Detection page displays speed details, a map with the detection location, and event details. Click View engine profile for more information on the speed and braking force (G force). Click View trip in the bottom right corner of the map to see all details of the trip where the collision was detected.

Verifying detected collisions

Verifying detected collisions supports the continuous improvement of the algorithms. Click Verify detection from the table to provide feedback and acknowledge that there was a collision, along with any additional comments.

Once completed, the table updates to reflect that this detection has either been confirmed or false.

Creating Collision Detection rules

1. Click Set up collision detection rule from the Collision Detection page, then click Confirm on the popup.

2. Click Setup rule on the popup displayed at the bottom of the Overview panel (if applicable).

3. To edit the default Collision Detection rule and notifications, click Visit Rule page to open the Exception Rule Edit page and do the following:
4. 1. Under the Name tab, name the rule and customize the rule’s color and visibility.
   1. Select the Publish to groups dropdown and select the groups to which the rule will apply.
   2. Under the Conditions tab, set conditions for when the exception rule is triggered using the available headings and their corresponding options.
   3. Under the Notifications tab, add exception rule notifications — including enabling emails, alerts, or driver feedback when a collision is detected.
   4. Click Save.

Providing feedback

Click Give Feedback to provide general feedback on the usability of this functionality and if you would recommend Collision detection to other Fleet Management Application users. You may also provide feedback when leaving the insight (prompted upon returning to dashboard). Thank you for your valuable feedback!

Water in Fuel

Water in Fuel is an important condition to monitor to maintain vehicle health. Water in Fuel causes lower fuel economy, both due to decreased combustion efficiency and the engine control module (ECM) many times defaulting to safer timing and ignition parameters, which also decreases efficiency. Over longer periods, Water in Fuel can corrode internal fuel system components, which can lead to reliability issues and potentially fuel leaks. Lastly, monitoring Water in Fuel in aggregate across large numbers of vehicles can help you identify contaminated fuel sources, which need to have the in-ground tank mitigated.

How it works

Water in Fuel events are detected using an algorithm that reduces the noise of engine faults to better alert the user to real Water in Fuel events. Once an event is discovered, it is translated into a diagnostic_id that is streamed into StatusData in the API. Active Insights and the Fleet Management Application’s rules engine can leverage it to generate various exception reports. When the StatusData is set to 1, it means a Water in Fuel event has been detected. The value will remain at 1 until the issue is resolved, and it is set back to 0. By assigning the numerical value to this event, you can track multiple vehicles experiencing the same issue.

Searching and sorting for Water in Fuel events

Search for particular assets to see if they have any Water in Fuel events by asset name or VIN to speed up the review process. Sort the events by asset name, VIN, date and time, or detection location. You can also filter the results by date range. The default date range is the last four days for the majority of databases.

Verifying Water in Fuel events

Verifying detected Water in Fuel events supports the continuous improvement of the algorithms. Click Verify detection from the table to provide feedback and acknowledge that there was an issue, along with any additional comments.

Once completed, the table updates to reflect that this detection has either been confirmed or false.

Creating Water in Fuel exception rules

1. To create a Water in Fuel rule, do one of the following:
2. 1. From the Water in Fuel detection page, click Get notified of next detection, then click Confirm on the popup.

1. Click Setup rule on the popup displayed at the bottom of the Overview panel (if applicable).

2. To edit the default Water in Fuel rule and notifications, click Visit Rule page to open the Exception Rule Edit page and do the following:
3. 1. Under the Name tab, name the rule and customize the rule’s color and visibility.
   2. Select the Publish to groups dropdown and select the groups to which the rule will apply.
   3. Under the Conditions tab, set conditions for when the exception rule is triggered using the available headings and their corresponding options.
   4. Under the Notifications tab, add exception rule notifications — including enabling emails, alerts, or driver feedback when a Water in Fuel event is detected.
   5. Click Save.

Providing feedback

Click Give Feedback to provide general feedback on the usability of this functionality and if you would recommend Water in Fuel detection to other Fleet Management Application users. You may also provide feedback when leaving the insight (prompted upon returning to dashboard). Thank you for your valuable feedback!

Camshaft Position Sensor

A camshaft position sensor is an electronic device that monitors the camshaft position and speed, and feeds that data to the vehicle’s engine control module (ECM). The ECM uses this data to control how much fuel enters the combustion chamber and ignition timing to ignite the fuel. A malfunctioning camshaft position sensor may give you a warning before it fails. If the warning symptoms are ignored and the camshaft position sensor completely fails, the vehicle will not start. Scheduling maintenance reminders ahead of time can prevent roadside breakdowns.

How it works

Camshaft Position Sensor event detection is determined by an algorithm that leverages vehicle fault codes and additional vehicle information to determine the severity and legitimacy of these events. This data is collected on a daily basis to provide accurate information for your fleet. Once an event is discovered, it is translated into a diagnostic_id that is streamed into StatusData in the API. Active Insights and the Fleet Management Application’s rules engine can leverage it to generate various reports. When the StatusData is set to 1, it means an event has been detected. The value remains at 1 until the issue is resolved, and then it is set back to 0.

Searching and sorting for Camshaft Position Sensor failures

Search for particular assets with camshaft position sensor failures by asset name or VIN. You can also sort the table by asset name, VIN, date and time, or detection location.

Verifying Camshaft Position Sensor Failure events

Verifying detected Camshaft Position Sensor Failure events supports the continuous improvement of the algorithms used for detections. Click Verify detection from the table to provide feedback and acknowledge that there was an issue, along with any additional comments.

Once completed, the table updates to reflect that this detection has either been confirmed or false.

Creating Camshaft Position Sensor Failure exception rules

1. To create a rule, do one of the following:
2. 1. From the Camshaft Position Sensor Failures page, click Get notified of next detection, then click Confirm on the popup.

1. Click Setup rule on the popup displayed at the bottom of the Overview panel (if applicable).

2. To edit the default rule and notifications, click Visit Rule page to open the Exception Rule Edit page and do the following:
3. 1. Under the Name tab, name the rule and customize the rule’s color and visibility.
   2. Select the Publish to groups dropdown and select the groups to which the rule will apply.
   3. Under the Conditions tab, set conditions for when the exception rule is triggered using the available headings and their corresponding options.
   4. Under the Notifications tab, add exception rule notifications — including enabling emails, alerts, or driver feedback when a camshaft position sensor event is detected.
   5. Click Save.

Providing feedback

Click Give Feedback to provide general feedback on the usability of this functionality and if you would recommend Camshaft Position Sensor Failure detections to other Fleet Management Application users. You may also provide feedback when leaving the insight (prompted upon returning to dashboard). Thank you for your valuable feedback!

Anti-Lock Braking Systems (ABS)

Anti-Lock Braking Systems (ABS) are mechanical systems in vehicles that allow drivers to continue to steer while pressing down on the brakes. This is a crucial safety feature as it can help drivers avoid collisions and allow them to brake safely. The Anti-Lock Braking Systems (ABS) Insight identifies assets with malfunctioning ABS so the asset can be taken off the road to schedule any required maintenance and prevent collisions.

How it works

The ABS algorithm intakes fault codes from the vehicle and filters out false positives. Once it is determined that a failure has occurred, it is translated into a diagnostic_id that is streamed into StatusData in the API. Active Insights and the Fleet Management Application’s rules engine can leverage it to generate various reports. When the StatusData is set to 1, it means that an ABS failure has been detected. The value remains at 1 until the issue is resolved, and then it is set back to 0. By assigning the numerical value to this event, you can track multiple vehicles experiencing the same issue.

Searching and sorting for ABS failures

From the ABS failures list, search particular assets by either their name or VIN. Sort the list by asset name, VIN, date and time, or detection location.

Verifying ABS failures

Verifying detected ABS events supports the continuous improvement of the algorithms used for ABS failure detections. Click Verify detection from the table to provide feedback and acknowledge that there was an issue with the ABS, along with any additional comments.

Once completed, the table updates to reflect that this detection has either been confirmed or false.

Creating ABS exception rules

1. To create a rule, do one of the following:
2. 1. From the Anti-Lock Braking Systems (ABS) page, click Get notified of next detection, then click Confirm on the popup.

1. Click Setup rule on the popup displayed at the bottom of the Overview panel (if applicable).

2. To edit the default rule and notifications, click Visit rule page to open the Exception Rule Edit page and do the following:
3. 1. Under the Name tab, name the rule and customize the rule’s color and visibility.
   2. Select the Publish to groups dropdown and select the groups to which the rule will apply.
   3. Under the Conditions tab, set conditions for when the exception rule is triggered using the available headings and their corresponding options.
   4. Under the Notifications tab, add exception rule notifications — including enabling emails, alerts, or driver feedback when an ABS event is detected.
   5. Click Save.

Providing feedback

Click Give Feedback to provide general feedback on the usability of this functionality and if you would recommend Anti-Lock Braking Systems (ABS) to other Fleet Management Application users. You may also provide feedback when leaving the insight (prompted upon returning to dashboard). Thank you for your valuable feedback!

Exhaust Gas Regulator (EGR)

The main components that make up the exhaust gas regulator (EGR) system are the EGR valve and, for many diesel vehicles, an EGR cooler. Accompanying the EGR system are a series of sensors which monitor their operation. When these sensors are sending fault codes, the operation of the components may be beyond acceptable operating conditions. This could indicate an issue with the EGR system. A properly operating EGR can theoretically increase the efficiency of a gasoline engine. The Exhaust Gas Regulator (EGR) insight identifies assets with malfunctioning EGR systems on a daily basis. Scheduling maintenance reminders to address these malfunctions helps you avoid engine performance issues caused by EGR failures.

How it works

The EGR algorithm intakes fault code data and filters out false positives by identifying if the EGR system malfunction is caused by circuitry or mechanical source. Once it is determined that a failure has occurred, it is translated into a diagnostic_id that is streamed into StatusData in the API. Active Insights and the Fleet Management Application’s rules engine can leverage it to generate various reports. When the StatusData is set to 1, it means that an EGR failure has been detected. The value remains at 1 until the issue is resolved, and then it is set back to 0.

Searching and sorting for EGR failures

From the EGR failures list, search for particular assets by either their name or VIN. Sort the list by asset name, VIN, date and time, or detection location.

Verifying EGR events

Verifying detected EGR events supports the continuous improvement of the algorithms used to detect EGR malfunctions. Click Verify detection to provide feedback and acknowledge that there was an issue with the vehicle, along with any additional comments.

Once completed, the table updates to reflect that this detection has either been confirmed or false.

Creating EGR exception rules

1. To create a rule, do one of the following:
2. 1. From the Exhaust Gas Regulator (EGR) page, click Get notified of next detection, then click Confirm on the popup.

1. Click Setup rule on the popup displayed at the bottom of the Overview panel (if applicable).

2. To edit the default rule and notifications, click Visit rule page to open the Exception Rule Edit page and do the following:
3. 1. Under the Name tab, name the rule and customize the rule’s color and visibility.
   2. Select the Publish to groups dropdown and select the groups to which the rule will apply.
   3. Under the Conditions tab, set conditions for when the exception rule is triggered using the available headings and their corresponding options.
   4. Under the Notifications tab, add exception rule notifications — including enabling emails, alerts, or driver feedback when an EGR event is detected.
   5. Click Save.

Providing feedback

Click Give Feedback to provide general feedback on the usability of this functionality and if you would recommend EGR Fault detections to other Fleet Management Application users. You may also provide feedback when leaving the insight (prompted upon returning to dashboard). Thank you for your valuable feedback!

Engine Coolant

An engine coolant system refers to the components responsible for cooling the engine and removing heat from other heat producing processes in the engine. Accompanying the engine coolant system are a series of sensors which monitor their operation. When these sensors are sending fault codes, it indicates that the operation of the components may be beyond acceptable operating conditions. This could indicate an issue with the engine coolant system. The Engine Coolant insight gives you visibility to faults that can help you predict when maintenance is required and how urgent it is.

How it works

The Active Insights Engine Coolant algorithm intakes fault code data and identifies which faults are related to the coolant system. Once it has flagged an incident, it is translated into a diagnostic_id that is streamed into StatusData in the API. Active Insights and the Fleet Management Application’s rules engine can leverage it to generate various reports. When the StatusData is set to 1, it means that a coolant system incident has been detected. The value remains at 1 until the issue is resolved, and then it is set back to 0.

Searching and sorting for Engine Coolant events

From the list of Engine Coolant events, search for particular assets by their name or VIN. Sort the list by asset name, VIN, date and time, or detection location.

Verifying Engine Coolant events

Verifying detected Engine Coolant events supports the continuous improvement of the algorithms used to detect engine coolant malfunctions. Click Verify detection to provide feedback and acknowledge that there was an issue with the vehicle, along with any additional comments.

Once completed, the table updates to reflect that this detection has either been confirmed or false.

Creating Engine Coolant exception rules

1. To create a rule, do one of the following:
2. 1. From the Engine Coolant page, click More and select Get notified of next detection, then click Confirm on the popup box.

1. Click Setup rule on the popup displayed at the bottom of the Overview panel (if applicable).

2. To edit the default rule and notifications, click Visit Rule page to open the Exception Rule Edit page and do the following:
3. 1. Under the Name tab, name the rule and customize the rule’s color and visibility.
   2. Select the Publish to groups dropdown and select the groups to which the rule will apply.
   3. Under the Conditions tab, set conditions for when the exception rule is triggered using the available headings and their corresponding options.
   4. Under the Notifications tab, add exception rule notifications — including enabling emails, alerts, or driver feedback when an Engine Coolant event is detected.
   5. Click Save.

Providing feedback

Click Give Feedback to provide general feedback on the usability of this functionality and if you would recommend Engine Coolant Fault detections to other Fleet Management Application users. You may also provide feedback when leaving the insight (prompted upon returning to dashboard). Thank you for your valuable feedback!

Glow Plug

The glow plug is a critical part of an engine cylinder that helps with fuel efficiency by heating incoming fuel and air in the engine. This is a key functionality in colder weather conditions, when engines have to work harder to stay at an operable temperature. The Glow Plug insight identifies assets with a potentially malfunctioning glow plug on a daily basis. Scheduling maintenance reminders to address these detections helps you avoid engine performance issues and improve fuel efficiency in colder climates.

How it works

The Active Insights Glow Plug algorithm intakes fault code data and identifies which faults are related to the glow plug. Once it has detected a fault, it is translated into a diagnostic_id that is streamed into StatusData in the API. Active Insights and the Fleet Management Application’s rules engine can leverage it to generate various reports. When the StatusData is set to 1, it means that a glow plug incident has been detected. The value remains at 1 until the issue is resolved, and then it is set back to 0.

Searching and sorting for Glow Plug events

From the list of Glow Plug events, search for particular assets by either their name or VIN. Sort the list by asset name, VIN, date and time, or detection location.

Verifying Glow Plug events

Verifying detected Glow Plug events supports the continuous improvement of the algorithms used to detect glow plug malfunctions. Click Verify detection to provide feedback and acknowledge that there was an issue with the vehicle, along with any additional comments.

Once completed, the table updates to reflect that this detection has either been confirmed or false.

Creating Glow Plug exception rules

1. To create a rule, do one of the following:
2. 1. From the Glow Plug page, click Get notified of next detection, then click Confirm on the popup box.

1. Click Setup rule on the popup displayed at the bottom of the Overview panel (if applicable).

2. To edit the default rule and notifications, click Visit rule page to open the Exception Rule Edit page and do the following:
3. 1. Under the Name tab, name the rule and customize the rule’s color and visibility.
   2. Select the Publish to groups dropdown and select the groups to which the rule will apply.
   3. Under the Conditions tab, set conditions for when the exception rule is triggered using the available headings and their corresponding options.
   4. Under the Notifications tab, add exception rule notifications — including enabling emails, alerts, or driver feedback when a Glow Plug event is detected.
   5. Click Save.

Providing feedback

Click Give Feedback to provide general feedback on the usability of this functionality and if you would recommend Glow Plug Fault detections to other Fleet Management Application users. You may also provide feedback when leaving the insight (prompted upon returning to dashboard). Thank you for your valuable feedback!

Cylinder Misfire

Cylinder misfires can occur on almost all internal combustion engine (ICE) vehicles. Cylinder misfires are not an issue, but a symptom of other problems with the vehicle’s engine, some of which might be serious. If left untreated, these incidents can result in larger issues that incur a lot of cost. With early detection of these events, you can avoid future costly repairs. The Cylinder Misfire insight identifies assets with confirmed misfire incidents on a daily basis, allowing you to schedule required maintenance to address these incidents.

How it works

The Active Insights Cylinder Misfire algorithm intakes fault code data and identifies confirmed misfire faults. Once it has detected a fault, it is translated into a diagnostic_id that is streamed into StatusData in the API. Active Insights and the Fleet Management Application’s rules engine can leverage it to generate various reports. When the StatusData is set to 1, it means that a misfire incident has been detected. The value remains at 1 as long as an additional misfire event occurs within a 5-day interval, after this timeframe it is set back to 0.

Searching and sorting for Cylinder Misfire events

From the list of Cylinder Misfire events, search for particular assets by either their name or VIN. Sort the list by asset name, VIN, date and time, or detection location.

Verifying Cylinder Misfire events

Verifying detected Cylinder Misfire events supports the continuous improvement of the algorithms used to detect Cylinder Misfire malfunctions. Click Verify detection to provide feedback and acknowledge that there was an issue with the vehicle, along with any additional comments.

Once completed, the table updates to reflect that this detection has either been confirmed or false.

Creating Cylinder Misfire exception rules

1. To create a rule, do one of the following:
2. 1. From the Cylinder Misfire page, click Get notified of next detection, then click Confirm on the popup box.

1. Click Setup rule on the popup displayed at the bottom of the Overview panel (if applicable).

2. To edit the default rule and notifications, click Visit rule page to open the Exception Rule Edit page and do the following:
3. 1. Under the Name tab, name the rule and customize the rule’s color and visibility.
   2. Select the Publish to groups dropdown and select the groups to which the rule will apply.
   3. Under the Conditions tab, set conditions for when the exception rule is triggered using the available headings and their corresponding options.
   4. Under the Notifications tab, add exception rule notifications — including enabling emails, alerts, or driver feedback when a camshaft error is detected.
   5. Click Save.

Providing feedback

Click Give Feedback to provide general feedback on the usability of this functionality and if you would recommend Cylinder Misfire Fault detections to other Fleet Management Application users. You may also provide feedback when leaving the insight (prompted upon returning to dashboard). Thank you for your valuable feedback!