What impact would it have on your daily tasks in terms of time saving or cost reduction? |
Easier to identify which FRO is overweight when you are trying to mass send/update a list of FROs. |
How frequently would you use this improvement? |
Daily |
How should it work? |
Currently when a load is too heavy to send we will receive an error message that states "FRO is not ready due to overweight". We would instead like to see something like "67001234567 is not ready due to overweight" so we do not have to spend time cross referencing FROs and the execution column to look for which FRO(s) is unable to send in a list of 50 FROs for example. |