TMS Issue Tracking - QA and Production

SpendDelegationMatrix

Recap of the SpendDelegationMatrix requirements:

1. After the Assign Carrier Rate activity, create an activity to check and make a systemic decision based on Ref: Extra, Carrier Total Line Haul, (TBD if Carrier Total Fuel needed), Carrier Distance is less than a specified threshold input.
2. Have one editable input based on Carrier Distance < 500 miles and a separate input based on Carrier Distance >= 500 miles. – Would like flexibility to have more than just > 500 miles or < 500 mile thresholds…we may end up decided to have a < 100 mile, 100.1-499.9 mile, 500.0-999.99 mile and 1,000= mile thresholds or some other mix of mile distances depending on where we see material differences in rates per mile for various distance ranges
3. The evaluation is a cost/rate per mile metric compared to the input, or (Carrier Total LH + Carrier Total Fuel)/Carrier Distance < Input
a. See attached spreadsheet, SpendDelegation.xls, Column J for the sample IF statement




  • Kayvan Shadpour
  • Apr 28 2021
  • Ready for PB Retest
  • Attach files
  • Kayvan Shadpour commented
    May 17, 2021 20:38

    Astro wrote:

    Updated clip levels for new brackets above 500 miles

    PB GEC Linehaul FTL loads from Sept 1 - Dec 31, 2020

    Intermediate and long haul distances



    Distance

    Quantity

    Rate per mile

    % difference

    Cum % difference


    > 2000

    538

    $2.90




    1500-2000

    156

    $2.98

    3%



    1000-1500

    533

    $3.12

    5%

    8%


    500-1000

    2,555

    $3.47

    11%

    20%


  • Kayvan Shadpour commented
    May 07, 2021 18:11

    New idea;
    To use the customer rate as the threshold, and a DRS comparing it to the carrier rate.

    If Customer Rate < Carrier Rate --> OK

    If Customer Rate = Carrier Rate --> OK or Review

    If Customer Rate > Carrier Rate --> Manager Approval Required

  • Kayvan Shadpour commented
    April 28, 2021 12:59

    From: Geno Schwartz <Geno.Schwartz@mercurygate.com>
    Sent: Tuesday, April 27, 2021 10:02 AM
    To: Astrophel Evora <ASTROPHEL.EVORA@pb.com>; William Bailey <WILLIAM.BAILEY@pb.com>; Kayvan Shadpour <Kayvan.Shadpour@pb.com>
    Cc: Edward Ronga <Edward.Ronga@pb.com>; Wil Mulligan <wil.mulligan@mercurygate.com>; Kyle Birchard <kyle.birchard@mercurygate.com>
    Subject: RE: PB/MG Weekly Call

    The internal rate index is a very similar benchmark. The main difference is that the IRI value is derived from the TMS’s own data on any give O/D pair vs Transcore which is derived from a broader set of external entities. IRI is displayed as a reference in various places depending on how its being used, many times in the manage quotes screen where carriers are sourced/solicited.

  • Kayvan Shadpour commented
    April 28, 2021 12:58

    From: Astrophel Evora <ASTROPHEL.EVORA@pb.com>
    Sent: Tuesday, April 27, 2021 8:21 AM
    To: Geno Schwartz <Geno.Schwartz@mercurygate.com>; William Bailey <WILLIAM.BAILEY@pb.com>; Kayvan Shadpour <Kayvan.Shadpour@pb.com>
    Cc: Edward Ronga <Edward.Ronga@pb.com>
    Subject: RE: PB/MG Weekly Call

    Are you talking about the internal rate index (IRI)? Like this EL Reference on LD71703?

    You could compare the Total Line Haul rate (not the Carrier Total) to this Internal Rate Index reference, to trigger the approval check? If Total LH > IRI, then assign EL to (Manager role/specified users) for the approval activity.

  • Kayvan Shadpour commented
    April 28, 2021 12:56

    From: Geno Schwartz <Geno.Schwartz@mercurygate.com>
    Sent: Tuesday, April 27, 2021 7:46 AM
    To: William Bailey <WILLIAM.BAILEY@pb.com>; Kayvan Shadpour <Kayvan.Shadpour@pb.com>
    Cc: Astrophel Evora <ASTROPHEL.EVORA@pb.com>; Edward Ronga <Edward.Ronga@pb.com>
    Subject: RE: PB/MG Weekly Call

    GM All,

    As it stands today ,there isnt a functionality in the TMS that will take an ‘amount’ and convert it to a rate per mile amount based on a routes distance (O/D pair zip to zip etc). This would be an item for the Product Roadmap at this time.

    I can offer up an alternative integrated solution that would take the ongoing management of an excel file full of zip codes , miles , and rates off your shoulders. The solution uses real market-paid rates (contract and /or spot market) from other brokers and shippers over the past week, 2 wks, month, quarter etc. and applies this cost amount to the load as a reference to be used as a benchmark for PB users to use as a guide when they are negotiating with carriers in transactional scenarios. The idea of managing and driving transactional freight spend down doesn’t change but the index/benchmark that is used along with the required maintenance effort does. In this scenario you would be using recent spot market costs (submitted by other transport providers) as your negotiation guide and the idea of using it as the trigger to require/not require further approval doesn’t change. The data is updated on a rolling 14 day schedule and is managed by the 3rd party (DAT Transcore). With that said it requires a subscription to Transcores Rate Index product and the integration is used to populate the rates as references that would be used as the benchmark.

    Thank You,


    Geno Schwartz

    Implementation Specialist

    m: +1 (312) 498-1709

    200 Regency Forest Dr, Suite 400 | Cary, NC 27518
    mercurygate.com






  • Kayvan Shadpour commented
    April 28, 2021 12:56

    From: William Bailey <WILLIAM.BAILEY@pb.com>
    Sent: Thursday, April 22, 2021 3:21 PM
    To: Kayvan Shadpour <Kayvan.Shadpour@pb.com>; Geno Schwartz <Geno.Schwartz@mercurygate.com>
    Cc: Astrophel Evora <ASTROPHEL.EVORA@pb.com>; Edward Ronga <Edward.Ronga@pb.com>
    Subject: FW: PB/MG Weekly Call

    Team:

    Astro and I met today and analyzed the MercuryGate Sept 1 – Dec 31 2020 activity regarding the Fuel surcharge frequency and whether we could ignore fuel in our spend delegation rule and just take Linehaul charge/divided by zip to zip distance and route to mgr for approval if > a preset not to exceed amount which will be based on distance (ie..>500 miles, , 500 miles, etc).

    We concluded that the frequency of cases for the > 500 mile and < 500 mile activity where just using the linehaul amount divided by miles would have failed to send activity for Mgr approval that we would have intended to be sent was very small (< 20 over 4 months) and therefore we can use the simplified approach of linehaul charge divided by zip to zip distance vs preset not to exceed amount.

    We do have one question. Since fuel is a separate category in Mercurygate, can we add a 2nd calculation and route to Mgr any cases where fuel per mile exceeds a separate preset not to exceed amount. In essence, we would evaluate each “Carrier Rate Accepted” case before the analyst can “send the tender” and if linehaul per mile exceeds the present limit or fuel per mile exceeds a different preset limit, then they get routed to Mgr for approval and if both are below the preset tolerance than analyst can hit the “send the tender” button. Please confirm?

    Thanks.