New usability feature for freight orders & bookings in TM 9.0: Logistical execution status
There is another nice feature introduced with TM 9.0.
It is about the logistical execution status of a freight order or freight booking.
The business Challenge here is, that very often there are multi-stop documents and it is not easy to find out about the current execution status.
So is was not easily visible in a document whether a document departed, arrived, was loaded, ... at a specific location.
Therefore a new collective status was introduced that collects the latest 'execution status' of a freight order or booking including location and last time stamp.
This is called logistical execution status.
Of course this status can also easily be seen on the POWLs.
In addition to this nice usability improvement we have enhanced the function even more.
If you decide not to report arrival/departure at one stop, then once you report a arrival at a following stop the arrival/departure will be reported for the predecessor stops automatically.
How does this look like in principle?
1. In this example there are two FU. One has to be delivered from Shipper 1 to Consignee 1. The other from Shipper 2 to Consignee 2.
The Stop Sequence is Shipper 1 --> Shipper 2 --> Consignee 1 --> Consignee 2.
As long as the execution did not start the logistical execution status will be initial.
Now the goods are loaded at Shipper 1 (this may be reported manually or by event management) with event 'loading start'.
The logistical execution status changes to: Location Shipper 1 - loaded - date & time.
This is reflected in a single field & can also be displayed easily in the POWLs
As soon as the 'departure' event is reported at shipper 1 location the status turns to: Location Shipper 1 - departed with date & time.
As soon as the goods arrive and the 'arrival' event is reported at shipper 2 location the status turns to: Location Shipper 2 - arrived with date & time.
This chain of events continues now in every location until final arrival at Location Consignee 2.
The logistical status turns into Location Consignee 2 - arrived with date & time
How does that look like in the system:
First of all the status can easily be seen in the worklists.
So a planner gets very quick access to the execution information of an order.
For some orders he can see that execution did not start yet. For others he can see that execution started already.
Now let's have a look how the logistical execution chain is executed:
Below an order with initial status, where execution did not start yet.
Now loading start at the first location starts & the event is set manually. The logistical status changes into 'Loading Location' & 'Loaded' Status & timestamp.
You can see that also in EM the event is raised.
Now departure at the first location is reported. The logistical status changes into 'Location' & 'Departed' Status & timestamp.
Again you can that in EM the departed event is raised.
After arrival at the intermediate stop, the logistical status changes into 'Location 2' & 'Arrived' Status & timestamp.
Now we do not report any further events, but report directly the arrival in the final destination.
The logistical status changes into 'Location 3' & 'arrived' status & timestamp.
Finally 'unloaded' is reported at the final location which set's the final status in our example.
In the overview of the events in the order you can see, that many events are set automatically due to successor information:
The status can easily be seen in the worklist: