TMS 7.12 MyCarrierPackets

Overview

Assure Assist's Assure Advantage provides Carrier monitoring and insurance compliance with MyCarrierPackets (MCP) Carrier Onboarding and Assure Advantage Carrier Monitoring.

Revenova's integration with Assure Assist:

• Get completed Carrier Application/MyCarrierPackets and creates the Carriers in the TMS.

• Gets the latest set of Carrier information changes and updates the Carriers in the TMS.

• Synchronizes the list of monitored Carriers between the TMS and MCP.

  • The list of 'monitored Carriers' are Carriers with the Monitor Carrier Checked on the Transportation Profile.

Setup

Navigate to the MCP website and log in. Add any Carriers to the list of monitored Carriers. This list of monitored Carriers is pulled into the TMS based on the steps below.

Enter Credentials

Enable the MyCarrierPackets integration by: 

1. Navigating to TMS Admin, 

2. Select Credentials. 

3. Select the Global Services tab,

4. Find MyCarrierPackets in the list and open the card. 

5. Check the Enabled boxes as needed.

6. Enter the   User ID and Password 1 into the text fields. 

7. Click the Save button when finished.

Valid credentials are required from an MCP subscription. MCP provides the User ID and Password 1.  

Warning:

If using MyCarrierPackets, do NOT enable SaferWatch or RMIS. Disable both SaferWatch and RMIS in TMS Admin, Global Services.

Remote Site Settings

Check the Remote Site Settings when upgrading from a previous release TMS release. Verify they match the Service and Test Service URLs listed below.

1. Click the Setup gear icon in the top right corner.

2. From the drop-down, click Setup.

3. In the Quick Find Toolbar type Remote Site Settings and click the link.

4. From the list of remote sites find MCP and click the Edit link.

5.  Update the Remote Site URL to match the Service URL below: 

Service URL: https://api.mycarrierpackets.com

Test Service URL: https://api.mycarrierpackets.com

TMS Admin

Global Settings

1. Allow Carrier Address Updates: Checked allows MCP to update Carrier billing and shipping addresses.

2. Carrier Remit To Sync : Checked allows MCP to automatically update the Carrier Remit To field on the Carrier's Transportation Profile.

3. Default Carrier Mode: Use this mode when onboarding Carriers from MCP if the packet from MCP does not include a Mode. Must have an MCP ID.

4. Carrier Monitor Run Frequency (Mins): How often the CarrierMonitorMCPJob runs, in minutes. This job adds new Carriers to onboard or update current Carrier information. The lowest setting is 15 minutes.

5. Carrier Monitor Last Run: The date and time the CarrierMonitorMCPJob was last successfully run. This value is used in several API calls to MCP.

Modes

1. The MCP Mode field is populated on the 6 packaged modes received from MCP.

• Air Freight, Drayage, Intermodal, LTL, Ocean FCL and Truckload

• Verify the Minimum Weight, Maximum Weight, and Weight Units fields. They should populate for each Mode record.

Intellivite Link Information

MyCarrierPackets provides two URLs/link to access the carrier application/packet.

1. General link.

2. Personal link for the user.

Either may be input on the User record in the TMS. Decide how to use it in email templates. Add it to the signature line or create a standard Carrier Invite template that users may send from the TMS. They may add those links to Community landing pages (that can be public pages) and/or their website.

Batch Processes

Carrier updates sent from MyCarrierPackets are processed by the CarrierMonitorMCPJob.

The CarrierMonitorMCPJob runs continuously. The job brings new Carriers and any Carrier FMCSA data changes into the TMS from MyCarrierPackets. New Carriers are created in the TMS and existing Carriers are updated with the latest set of changes from MCP. The list of monitored Carriers is generated from the Carrier Transportation Profiles where the Monitor Carrier field is Checked.

Run the CarrierMonitorMCPJob from the list of Batch Processes on the Performance IQ Lightning Web Component (LWC).

This batch job runs in 3 different modes.

1. First time run (when Carrier Monitor Last Run preference is set to null/blank):

   1. Gets the list of monitored Carriers from MCP and creates/updates those Carriers in the TMS. The Carrier Monitor checkbox on the Transportation Profile of the Carriers is set to true (Carrier is monitored at MCP).

   2. Gets the list of Carriers in the TMS where Carrier Monitor checkbox on the Transportation Profile of the Carrier is set to false and registers that Carrier as unmonitored at MCP.

   3. Get the completed packets from MCP and creates/updates those Carriers in the TMS.

   4. Update the Carriers in the TMS with the latest set of changes from MCP for monitored Carriers only.

2. Daily run (Monday through Saturday) (when Carrier Monitor Last Run preference has a date/time in the past):

   1. Get the completed packets from MCP and creates/updates those Carriers in the TMS.

   2. Update the Carriers in the TMS with the latest set of changes from MCP for monitored Carriers only.

3. Sunday run:

   1. Gets the list of Carriers in the TMS where Carrier Monitor checkbox on the Transportation Profile of the Carrier is set to false and registers that Carrier as unmonitored at MCP.

   2. Gets the list of monitored Carriers from MCP and creates/updates those carriers in the TMS. The Carrier Monitor checkbox on the Transportation Profile of the carriers is set to true (Carrier is monitored at MCP).

   3. Get the completed packets from MCP and create/update those Carriers in the TMS.

• Update the Carriers in the TMS with the latest set of changes from MCP for monitored Carriers only.

Notes

• Online Carrier applications are never used with MyCarrierPackets. Onboarding occurs on their website portal.

• The Carrier Transportation Profile field Last Carrier Review Date is set every time MCP data is pulled during the batch job. 

• An individual user can manually update compliance and certification fields to override MCP risk fields.

When a Carrier is rejected perform these two tasks:

1.  "Uncheck" the Monitor Carrier field on the Carrier Transportation Profile.

2. Set the Carrier Review Status field to "Rejected."

Table Guide

The following fields are inserted/updated by the MCP Carrier Monitoring API as follows:

I – Insert

U – Update

(1) => update if the global setting “Allow Carrier Address Updates” is checked OR the value in the TMS field is null

(2) – update if the value in the TMS field is null

(3) – update if there is a value in the response

(4) – update if there is a value in the response AND the value in the TMS field is null

(5) – update if the global setting “Carrier Remit To Sync” is checked AND the response has factor company information

(6) – update to ‘Pending’ if RMIS Certified is not ‘Yes’

(7) – set to ‘Pending’ by the TMS 

Table Guide:

I – Insert

U – Update

(1) => update if the global setting “Allow Carrier Address Updates” is checked OR the value in the TMS field is null

(2) – update if the value in the TMS field is null

(3) – update if there is a value in the response

(4) – update if there is a value in the response AND the value in the TMS field is null

(5) – update if the global setting “Carrier Remit To Sync” is checked AND the response has factor company information

(6) – update to ‘Pending’ if RMIS Certified is not ‘Yes’

(7) – set to ‘Pending’ by the TMS

Risk Assessment Scores and Mapping

• In the API: Unacceptable, UnacceptableReview and UnacceptableFail mean Unacceptable (>= 10,000 points).

• In the site: Review Required = UnacceptableReview and “Unacceptable (unable to invite)” = UnacceptableFail.