Skip to Main Content
First Mile Ideas Portal
Created by Guest
Created on Feb 1, 2023

Item to be add on freight order worklist

MONITORING
Worklist items to be added in FO list: profitability , Customer Type ( example BCO) , how many times appointments has changed, and if changed by vendor or customer


as agreeded with Krishna Kishore Kantipudi let me add some comments in order to speed CR

profitability : is required for all fro and it will help to send fro to vendor when cost is not recovered
COST IMPACT around 10% of fro,

Customer Type ( example BCO) : is required for all fro / fwo , it will improve dispatcher/cx communication because will allow dispatcher to identify gcss owner and will be usefull in case of priority list to be finalized
FTE IMPACT around 0,15 fte/day

How many times appointments has changed: is required for all fro / fwo , it will assist to perform vendor performance report
FTE IMPACT around 0,1 fte/day

  • Attach files
  • Rasmus Thiim
    Aug 15, 2025

    Hello Angela,

    I would like to split this idea up, as there's 3 different ideas in here:

    Profitability - I will add this is a proposed scenario in the Guided User Journey, where we may have the space to surface the expected financial impacts on freight orders (think similar to how triangulation works)

    Customer Type (BCO) - captured another idea for GUJ where "Indicators" would apply (Spot, Twill, BCO, Prism etc. etc.)

    Amount of appointment changes - Will bring this idea for discussion with Execution and Vendor Management value streams.

    By splitting these I'll go ahead and close this idea as Will not Implement. OK?

  • Hichem Tlemsani
    Sep 20, 2023

    Hi Angela, as it has been a long time since this idea was submitted I suggest to refresh it through a Gemba for example September/October timeline

  • Guest
    Jul 26, 2023

    as agreeded with Krishna Kishore Kantipudi let me add some comments in order to speed CR

    profitability : is required for all fro and it will help to send fro to vendor when cost is not recovered
    impact around 10% of fro,

    Customer Type ( example BCO) : is required for all fro / fwo , it will improve dispatcher/cx communication because will allow dispatcher to identify gcss owner and will be usefull in case of priority list to be finalized
    impact around 0,15 fte/day

    How many times appointments has changed: is required for all fro / fwo , it will assist to perform vendor performance report
    impact around 0,1 fte/day