Requester:
Michael Keller, Todd Evans, Joel Zuerlein
Request story:
Requesters need to have a better visibility of lanes initially tendered to PB Fleet and OTR, but then forced to be covered by a 3rd party carrier. The TMS Extra field value of “AdHocREC” which was added in January 2022 currently serves a hybrid role of flagging the following scenarios:
A 3rd party carrier informs PB transportation that due to some reason they are not able to serve the load tendered to them. Transportation team, tenders this load (often in short notice) to a another carrier, while flagging this “recovered” load with the extra reference of “AdHocREC”.
PB’s internal fleet (PBPS or NOTR) informs transportation that due to some reason they are not able to serve the load tendered to them. Transportation team, tenders this load (often in short notice) to another carrier, while flagging this “recovered” load with the extra reference of “AdHocREC”.
Solution:
In order to give a distinct flag for when PB internal fleet (PBPS or NOTR) need a load/lane to be “covered” by another carrier, we propose adding the “Extra” value of “AdHocREC” to the current value options. This would be without changing any other value.
In other words:
Extra value |
Description |
Data entry mode |
New Request |
AdHoc24 |
Load creation date/time |
Added care of a dynamic ruleset in MG at the time of load creation. Not available for manual entry |
Keep as is |
AdHoc48 |
Load creation date/time |
Added care of a dynamic ruleset in MG at the time of load creation. Not available for manual entry |
Keep as is |
AdHocREC |
Recovery requested/imposed by 3rd party carrier |
To be added manually by user when a 3rd party carrier informs PB transportation that due to some reason they are not able to serve the load tendered to them. |
Keep as is |
AdHocCOV |
Cover requested by PB’s internal fleet (PBPS or NOTR) |
To be added manually by user when PB’s internal fleet (PBPS or NOTR) informs transportation that due to some reason they are not able to serve the load tendered to them |
New value to be added |
Snowflake Changes:
This request imposes no change to the TMS tables in Snowflake. However it revises the interpretation of Ad Hoc.
Implementation TimeLine:
If we do not receive any objection/concerns regarding this change request, it will be applied on MercuryGate TMS Prod on Friday 3/18th.
Kayvan Shadpour
Extra reference field's new value of "AdHocCOV" was added to code table at transportation level
Preliminary proposal communicated with all stake holder on 3/14 at 14:52 via email