Overview
Gaining visibility into diagnostic trouble codes across your entire fleet can be difficult, and can leave you guessing about what the codes mean and how to address them.
The Trouble Codes log eliminates this challenge by providing a centralized view of all reported codes, ensuring you have fleet-wide transparency. Each code is paired with a clear definition, powered by IntelliShift’s API and SAE standards, so you can quickly understand the issue and take action. From the Trouble Codes screen, you can create issues directly, integrating trouble code management into your maintenance workflow. This feature ensures you stay informed, make faster decisions, and keep your fleet operating efficiently.
Table of Contents
- View Trouble Codes
- Trouble Code Navigation Overview
- Create an Issue from a Trouble Code
View Trouble Codes
To view Trouble Codes, follow these steps:
- In the left-hand navigation, select the "Maintenance” service module.
- In the top navigation, select "Trouble Codes."
Please note, if you do not see this feature, you will need to contact an Administrator. Only Account Administrators and Administrators can change your permissions.
Trouble Code Navigation Overview
While viewing the Trouble Codes log, you can
- Search and filter across the table's header (1)
- View asset ID (2)
- View Trouble Code (3)
- View date code triggered (4)
- View SAE trouble code definition powered by IntelliShift's API (5)
- Identify if the Malfunction Indicator Lamp was on/off with code (6)
- Create an Issue (7)
- Hide Code from Log (8)
Create an Issue from a Trouble Code
Issues serve as the starting point for resolving problems, providing a centralized hub to track and assess reported concerns. Once an issue is created, you can update its status, add comments, or attach supporting documents. If the issue requires more extensive work, you can escalate it by creating a Work Order to manage the resolution, track labor, parts, and associated costs.
Follow the steps below to create an issue from a Trouble Code.
Comments
0 comments
Article is closed for comments.