Exceptions Report

The objective of the Exceptions Report is to provide users with information on reasons why tasks of an item were failed.

Whats new?

Previously, users could only view failure reasons for their own fleet. There was no visibility into failure reasons for downstream partners.

In this version, users can holistically see failure reasons for both his fleet and his partners'. Users can also choose to view failure reasons in a single leg, or across all legs.

---

Description

The date range filter of the Exceptions report is based on the Execution Date.

Some key information that could be extracted from this report includes:

• Who failed the item? i.e. downstream partner, or in-house fleet driver

  • If a DSP failed it, users can see the DSP name who failed it. They will not be able to see the DSP’s driver nsme

  • If a in-house fleet driver failed it (i.e. the driver is your driver), then the user can see the name of this driver

• Which leg did the item fail in + which task was failed

• Reason for failure

---

Filters

There are 11 filters used in the exceptions report

• Date Type
• Date Range
• Leg
• Item Status
• Task Type
• Driver Name
• Downstream Partner
• Sender Name
• Service Type
• Item Type
• Exception Reason

Date Type

There are 3 date type options in this filter. 

• Creation Date
  

  Filtering on the creation date displays order-items only created within the specified date range.

• Commit To Date
  

  Filtering on the commit to date displays order-items where tasks have a commit to date within the specified date range.

• Assigned Date
  

  Filtering on the assigned date displays order-items where tasks have been assigned within the specified date range, irrespective of what the order-item states/statuses are.

Date Range

The Date Range filter allows you to select a single date or a customised date range.

Leg

The Leg filter gives dispatchers the option to filter on a particular leg he is concerned with, or no legs at all.

If an item in inserted into the product with the multi-leg feature i.e.
Leg 1: Pick up @ A, Drop off @ B
Leg 2: Pick up @ B, Drop off @ C, Pick up @ C, Drop off @ D
Leg 3: Pick up @ D, Drop off @ E

then;

Filtering on Leg 1:
Would only show the state of the item concerned from Point A to Point B

Filtering on Leg 2:
Would only show the state of the item concerned from Point B to Point D

Filtering on Leg 3:
Would only show the state of the item concerned from Point D to Point E

Not Filtering on any Leg:

Would show the state of an item, considering all legs i.e. Point A to Point E

Item Status

The Item state filter allows users to select on all/ 1 of the following states (also found in the dashboards):

1. Unassigned

2. Assigned

3. Completed

4. Transfer Pending

5. Transfer-Unassigned

6. Transfer-Assigned

7. Transfer-Completed

8. Cancelled

Task Type

User able to focus only on pick ups or drop offs or both.

Driver Name

The Driver Name filter enables a user to extract information for all items that have been tagged to one(many) specific driver(s).

Downstream Partner

The Downstream Partner filter enables a user to extract information for all items that have been transferred to one(many) specific partner(s)

Sender Name

The Sender filter enables a user to extract information for all items that were placed by a particular sender account or have been transferred from one a specific upstream partner

Service Type

The Service Type filter enables a user to extract information for all items tagged to a particular service type

Item Type

The Item Type filter enables enables a user to extract information for all items belonging to a particular item type.

Exception Reason

The exception reason filter enables a user to search for a particular exception from the entire list. This works most effectively when exceptions are well defined in dispatcher system - so as to avoid a list of free-text exception reasons