Fleet Management

Overview

Fleet Management

1. Fleet Management Enabled

   1. When Checked, the Fleet Management module is enabled in the TMS.

   2. Uncheck the box and click Save to stop running an active instance of Fleet Management Job 3.

2. Driver Log Grace Period (Days)

   1. This setting determines the number of days Hours of Service (HOS) logs are retrieved. This allows for adjustment of past Hours of Service (HOS) logs for the number of days.

   2. Hours of Service Logs are never created for the current day. Example: The Driver Log Grace Period is set to 2 days. The current date is 8/23/24. Hours of Service Logs are retrieved for 8/21/24 and 8/22/24.

3. Fleet Management Job Last Run

   1. The date and time set by the Fleet Management Jobs each time the job successfully runs.

4. Fleet Management Default ELD Provider

   1. The backup default value for Fleet Asset and Driver records when the ELD Brand field is not set when records are created.

   2. Select a value from the picklist for the default ELD Provider.

5. Fleet Management Pass Counter

   1. The Fleet Management Pass Counter allows for running single passes of either the Fleet Management and Fleet Management 2 Jobs.

   2. Set this value (0-13) to run one pass of the Fleet Management Job. Use for debugging only.

   3. Set this value (1-12) to run one pass of the Fleet Management 2 Job. Use for debugging only.

   4. This field does not impact running Fleet Management Job 3.

6. IFTA Mileage Reporting Enabled

   1. When Checked, the IFTA Report Job is enabled and displays the IFTA Report buttons in the Fleet Management Console Trip Planner.

7. IFTA Off Route Miles

   1. The number of Off Route Miles precision for IFTA Reporting.

   2. The default value is 0.03.

8. Datatable View Query Limit

   1. Improve performance returning records from the Fleet Management Console grid view. This field limits the number of rows returned when searching Fleet records.

   2. Reduce the value of the results returned to improve performance. Use caution when decreasing the number of results. Set filters and ordering priority to ensure records are not overlooked.

   3. The default value is 500.

9. Freight Plan Load View Query Limit

   1. Improve performance returning records from the Fleet Management Console Freight Plan Load grid view. This field limits the number of rows returned when searching Freight Plan Loads.

   2. Decrease the value of the results returned to improve performance. Use caution when decreasing the number of results. Set filters and ordering priority to ensure records are not overlooked.

   3. The default value is 200.

10. Driver Decline Reason Required

    1. When Checked, a Driver must provide a decline reason when selecting Decline in the Driver Confirmation email.

11. Monochrome Trip Builder

    1. When Checked, Stops are identified in monochrome in the Fleet Management Trip Builder.

12. Default Trip Plan Start

    1. When a Trip Plan Segment is the first Segment on a Trip Plan, the value in this field is the default start location.

    2. This field is optional.

    3. This field populates into the Trip Builder to add a start location when planning Trips.

13. Fleet Management Job
    Only one Fleet Management job may be enabled at one time.

    1. FleetManagementJob: All 13 passes of the Fleet Management Job run and enable other Fleet Management features.

       1. The Fleet Management Job controls calls to the Samsara API end points.

       2. Do not enable the Fleet Management Job when using the Catena API integration.

    2. FleetManagementJob2: All 9 passes of the Fleet Management 2 Job run and enable other Fleet Management features.

       1. Fleet Management Job 2 controls calls to the Catena API end points.

       2. Do not enable Fleet Management Job 2 when using the Samsara API integration.

    3. FleetManagementJob3: Fleet Management Job 3 performs the same actions as the Fleet Management Job. The job uses fewer asynchronous threads and is mostly platform event-based. Fleet Management Job 3 runs approximately 10 times faster than the Fleet Management Job.

       1. Fleet Management Job 3 controls calls to the Samsara API end points.

       2. Do not enable Fleet Management Job 3 when using the Catena API integration.

14. Fleet Management Email

    1. Errors from the Fleet Management and Fleet Management 2 Jobs are sent to this email address.

15. Fleet Management Default Carrier

    1. The internal Carrier Account that handles all Fleet loads. Set a Fleet Account record as the default Carrier when using the Samsara integration.

    2. The Catena integration does not require a Default Carrier. It is recommended to include a Default Carrier as a precaution when creating or updating Fleet Asset and Driver records during Passes 3 and 5 of the Fleet Management 2 Job.

16. Sync Active Drivers Only

    1. This field only applies to Fleet Management Job 2. See job documentation for more information.

    2. When Checked, Fleet Management Job 2 attempts to synchronize Driver records between the TMS and Catena.

       1. Note that Drivers should be deactivated in both the TMS and in Catena to prevent duplication issues.

    3. When Unchecked, all Drivers in the ELD Provider are created or updated in the TMS.

17. Sync Active Fleet Assets Only

    1. This field only applies to Fleet Management Job 2. See job documentation for more information.

    2. When Checked, Fleet Management Job 2 attempts to synchronize Fleet Asset records between the TMS and Catena.

       1. Note that Fleet Assets should be deactivated in both the TMS and in Catena to prevent duplication issues.

    3. When Unchecked, all Fleet Assets in the ELD Provider are created or updated in the TMS.

18. Create ELD Trip On Dispatch

    1. When Checked, route/trip information is sent to the Catena or Samsara integrations when the Dispatch button is clicked on the Trip Plan Segment.

    2. When Unchecked, route/trip information is sent to the Catena or Samsara integrations when the Driver Confirmation Status is set to Accepted.

       1. Trip/route information is sent to Trimble when the Dispatch button is clicked on the Trip Plan Segment.

19. Disable ELD Dispatch

    1. When Checked, the TMS does not create trips or dispatch to the ELD Providers by the Catena or Samsara integrations.

       1. Check this field when the ELD Provider connected through the Catena integration does not support receiving trip information.

20. Timezone Update Disabled

    1. The Fleet Management and Fleet Management 2 Jobs set this field to Checked if unable to update Account records with the appropriate time zone field values.

21. Email Modal for Driver Confirmation

    1. When Checked, the email modal opens when a user clicks the Confirm Driver button on the Trip Plan LWC.

    2. Dispatchers may add comments to the Driver Confirmation email before sending to a Driver.

22. Show Line Item Button on Trip Plan Modal

    1. When Checked, the Show Line Item button is available when Trip Planning in the Fleet Management module.

23. Show Plan Freight Button

    1. When Checked, The Plan Freight button is available for LTL/Load consolidation in the Fleet Management Console to open the Fleet Freight Plan Console.

24. Default Trip Plan End

    1. When a Trip Plan Segment is the last Segment on a Trip Plan, the value in this field is the default end location.

    2. This field is optional.

    3. This field populates into the Trip Builder to add an end location when planning Trips.

25. Trip Plan Events

    1. Accessorial Review

       1. When Checked, a Trip Event is generated when adding a Load to a Trip Plan that contains an accessorial. Add the accessorial to the Trip Plan to resolve the Trip Event. This field supports the PayIQ package.