The Root Cause Analysis (RCA) page allows you to review all completed routes that contained at least one violation. From this page, you can document the Cause of the Violation, Product Status, Action Taken, and any additional notes for future reference or reporting.
Once all required details are entered and saved, the route will be removed from this page and stored in the Root Cause Archive for long-term recordkeeping.
📋 Purpose of this Page
The RCA page is designed to help you identify and record why violations occurred, ensuring accountability and continuous improvement.
A record appears under this page once a route with a violation has been completed—that is, once the trailer reaches its final stop, not when it returns to the Distribution Center (DC).
Once the RCA shows up in this page, you have 24 hours from route completion to finalize the RCA. If not completed within this timeframe, the entry will appear as late (or incomplete if details were never submitted) in the RCA Report.
If there are no RCAs pending, this page will display as empty.
🔍 Search and Filter Options
Use the available filters to quickly locate specific pending RCAs:
Route Name – Search by a specific route identifier.
Start Date / End Date – Filter RCAs by the route’s scheduled start or end date.
Vehicles – Filter results by the vehicle or trailer that ran the route.
Violations – Cold, Hot, Missing Data, Excessive Gap in Data (More details about what triggers each violation in the section below)
🛠️ Completing a Root Cause Analysis
Select the route you wish to review from the list.
-
Enter the following details for each violation:
Cause of Violation – Identify what led to the issue.
-
Product Status – Indicate whether the product was affected or remained within safe limits. Options available:
Ok
Not Ok
Action Taken – Describe the corrective or preventive action performed.
Notes (optional) – Add any additional comments or context for reference.
-
Click Submit Assessment once all fields are completed.
The route will be removed from this list and added to the Root Cause Archive page.
|
Important: Lists of Cause of Violation and Action Taken items may vary per DC. |
If the violation occurred due to incorrect route details (e.g., inaccurate start time or temperature), you can click on the route and edit it to correct the information before saving your RCA.
The following video provides information about the Root Cause Analysis (RCA) page:
🚨 What Triggers an RCA?
RCAs are triggered only when a violation occurs during a route. If a route only contains a warning, no RCA will be generated.
The Understanding Route Violations Support Article provides a list of all violations which trigger an RCA.
⏱️ Routes Appearing Days After the End Date
In some cases, a route may appear on the Root Cause Analysis (RCA) page several days after the route actually ended. This behavior is typically related to route duration settings and trailer data issues.
Why This Happens
Routes that do not properly end remain open in the system for up to five days, which is the default timeout period. If a route does not receive the expected end-of-route data, the system keeps it active until this timeout is reached. Once the route is automatically closed, it then appears on the RCA page for review.
This usually occurs when:
The route was linked to the incorrect vehicle.
The assigned vehicle never departed from the Distribution Center (DC).
Trailer or telemetry data was not received as expected.
These scenarios are more common in environments where routes are managed by an external system (such as a WMS).
What You Can Do
If you notice a route appearing on the RCA page days after it ended:
Open the route from the RCA page.
Review the route duration and confirm the correct vehicle was assigned.
If needed, update the vehicle information using the Edit Route option.
If you’re unsure which vehicle should be assigned or need assistance correcting the route details, we recommend reaching out to our Support team for help.
If you have any other questions regarding RCAs, please reach out to our Support team for further guidance. |