Skip to main content
Deutsch (Deutschland) Français (France)

Search

search shadow

Articles in this section

RCA Launch: May 16th

Rich Hellinga
Rich Hellinga
Updated

In this article

What’s Launching?

We are launching 18 new root cause errors (in addition to the 17 errors that exist today, 35 errors in total) that will give our customers, internal operators and carriers more granular information. This release addresses a key issue with RCA where many shipments are categorized under an error labeled as “Unknown”, and covers two types of shipments: a) DriveView shipments and b) shipments without an Active Tracking Method.

What’s Changing?

  1. 18 New Root Cause Errors

    1. We are expanding TL RCA to include 18 new root cause errors specifically for two types of shipments:

      1. Driveview Shipments (12 errors)

      2. Shipments that did not track with an Active Tracking Method (6 errors)

      3. More details on current errors and the new errors launching- in green- can be found: Root Cause Errors - Internal Knowledge Base - Confluence (atlassian.net)

    2. With these new errors, we have reduced the number of shipments falling in “Unknown” by 50% and expanded the number of Driveview errors from 3 errors to 12, giving our customers more visibility and actionable information on why shipments are failing to track.

    3. The new errors will be attributed to shipments that completed on April 20, 2023 or later.

  2. Affected Shipments by Shipment Tracking Type

    1. Customers and Internal Operators will now have visibility into Tracking Type at the shipment level and have visibility into shipments that did not have an active tracking method. There will be a new tracking type introduced, labeled as “None”, which means the shipment did not have an active tracking method.

  3. Root Cause Errors Over Time

    1. Customers now have a visualization of how root causes for their affected shipments are trending over time. They can also drill into the shipments directly affected by the root cause to download for faster investigation and mitigation.

How does this impact internal analytics?

  1. New Root Cause Errors

    1. P44 OS: TL-Carrier Scorecard

      1. The New 18 Tracking Errors will be available in the ‘Root Cause Analysis’ section of the Dashboard.

  2. New ‘Shipment Tracking Type Column’

    1. On 5/17, the internal analytics team will update four internal dashboards to give internal operators a new “Shipment Tracking Type” column which gives visibility into shipments that did not have an active tracking method in addition to the current “Tracking Type” column which is a proxy for the Carrier Level Tracking Type.

    2. The internal dashboards that will be updated with the new “Shipment Tracking Type” column include:

      1. p44OS: TL-Carrier Scorecard

      2. p44OS: Tracking Performance - TL Capacity Provider

      3. Tableau: TL Tracking and Data Quality Dashboard

      4. Tableau: 360

Where can I learn more?

  • Internal Knowledge Base (IKB):

  • More information around what’s changed and Q&A: Wiki Launch Page

  • Slack channel: #rca-improv-launch-may-23

  • May 18th: Live Feed Event with the L&D team to <add>

  • May 24th: Close the Gap - How Truckload Shipments are Tracked

    • On May 24th, the L&D team will launch a new close the gap series which <add>

New Error Q&A:

Q1: What does No Active Tracking Method at the shipment level mean?

A1:No Active Tracking Method at the shipment level means that Project44 was unable to find a Tracking Method to connect to track this particular shipment. This can be due to carrier configuration or provided data given to us on the shipment. Consider when you create a shipment without a valid equipment identifier. It will go into a status of DISPATCHED - PENDING TRACKING METHOD. Assuming no other intervention occurs, this shipment will time out without tracking. This shipment would have No Active Tracking Method.

Q2: What is an example when I would see “None” as a shipment tracking method?

A2:You would see None as a tracking method on a shipment if p44 couldn’t determine the tracking method for the shipment. This would happen on shipments that have a status of DISPATCHED-PENDING TRACKING METHOD before timing out.

Q3: I used to see a high % of errors in error bucket xyz. Now that number has decreased. Where did the shipments go?

A3: Since we added new errors, our ability to granularly define tracking issues has improved. This means that you will see new errors and the distribution of errors among the existing buckets has changed as we were able to identify a more specific cause for a given shipment. This is a good thing! It means we can be more specific with what went wrong on tracking. One example: Instead of saying “ELD Shipment not Tracked” we can break it down to why: “Equipment Identifier Type Mismatch".

Q4: I thought the breakdown of connection type at the top was based on how the carriers were supposed to track? Why did that change?

A4: The graphic you’re referencing on the top right of RCA was never meant to act as a distribution of shipments by carrier onboarding method. It is a reflection of how each individual shipment tracks. It’s quite possible that a carrier has multiple tracking methods configured. Showing how the shipments attempted to (or didn’t) track allows us to compare with how we would expect them to track and find issues.

Q5: What do I tell my customers about this new tracking type None?

A5: Explain to customers that we have improved our reporting to provide more granular and specific errors. Instead of focusing on how a shipment most likely should track (previous iterations of RCA) and providing our best estimate of the tracking method, we’ve focused on what is actually happening to the shipment. This allows us to easily compare the Shipment Tracking Type and the Tracking Type column to see where discrepancies might occur.

Related articles