Following request has just been received. You are being informed in advance out of curtesy, in case your dashboards/tool’s logic is targeting values in the TMS Load Performance Extra field.
Pleased express any possible objection/concerns you may have before Thursday 5/12th.
Requester:
Michael Tylock, Brad Hoff, Lisi Moeai
Request story:
Requesters need to have an additional value which would have different use cases for the Presort BU vs GEC BU;
Presort has the requirement to flag any load which is being built/scheduled out of the ordinary schedule, even if it’s not an AdHoc (within 24 hours from pickup date, by GEC definitions).
GEC wants to leverage this new value to identify GEC Courier AdHocs.
Solution:
To serve the Presort & GEC requirement without compromising the existing AdHoc logic in place, we propose adding a new value of “Extra” to the Load-level reference field of “Extra”. This would be without changing any other value.
Advantage is that the Presort & GEC transportation teams can still filter by AdHoc flags as well as this new value, without the need of creating an additional reference (which would also need MercuryGate ruleset changes).
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 |
|
AdHoc48 |
Load creation date/time |
Added care of a dynamic ruleset in MG at the time of load creation. Not available for manual entry |
|
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. |
|
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 |
|
Extra |
Any Presort load which are created different from the regular schedule or carrier |
To be added manually by user to applicable loads, based on BU specific definitions stated on the left |
New value to be added |
Snowflake Changes:
This request imposes no change to the TMS tables in Snowflake. And does not revise the interpretation of Ad Hoc.
Kayvan Shadpour
Deployed to Prod and stake holders informed via email.
Data stake holder informed over email. Planning deployment for 5/13th