249804

249804 PA-7DJDPE Amend Debrief Screen - TRIPDTL v2.54

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

FUNCTIONAL OVERVIEW

Client Requirement

Amend Debrief Screen - TRIPDTL v2.54 - Reduce level of input, but retain ability to change by exception

Default into Order Debrief Screen. When accessed from amended OVERVIEW v1.6(Waterfall) screen, open Trip highlighted in waterfall screen. Pre populate 'Actual' times, 'Actual Weight' and 'Actual Volume' from 'Planned' where appropriate. Move 'Set Status' button to more prominent position on Right hand side. Widen or amend font of POD column to allow 'POD' label to be visible when highlighted. Add Message on screen to 'Change Actual values if incorrect' Allow multiple selection of orders for POD confirmation.

Solution

When the Trip Debrief (TRIPDTL) screen is opened, whether from the Main Menu or when called from another screen, it will always default into the ‘Order Debrief’ tab, instead of the current ‘General’ tab.

The ‘Set Status’ button and associated Status drop down list will be moved to the right hand side of the screen, so it is more prominent. The 2 buttons originally next to ‘Set Status’ will be aligned on the left hand side; these include ‘Add Order’ and ‘Calc Time’.

When the ‘Debrief’ button in the Waterfall (TRIP_OVERVIEW) screen is clicked, the Trip Debrief (TRIPDTL) screen will be opened and the Trip Details of the currently selected Trip will be passed in.

A new button will be placed on the TRIPDTL screen, on the left side of the Save button below the Actuals input area. It will be named ‘Set Actuals’, and when clicked will pre-populate all the Actual Arrive and Depart Times, and Save these. It will also include the functionality to allow the user to Debrief by Exception.

This is achieved through the following process: User enters Actual Date/Times only at stops that do not match their Planned Date/Times User clicks new ‘Set Actuals’ button and the system automatically pre-populates the other stops Actuals.

System will not pre-populate Stop Actuals if they can not be met when compared to previous stop Actuals entered manually by the user E.g If the manually entered Actual Depart time at Stop 2 is after the Planned Arrive time at Stop 3, the system will not pre-populate Stop 3 Actuals as it is not possible to meet this Planned Arrive deadline when compared to the Actual Depart Time at Stop 2.

In the Order Debrief tab 2 new buttons will be added to allow pre-population of Actual Quantities: • The first one will be placed directly below the ‘Actual Despatched’ input area and named ‘Set Desp’. This will pre-populate ‘Actual Despatched’, ‘Actual Weight’ and ‘Actual Volume’ for all Order Lines. This also has the Debrief by Exception functionality, where if the user manually enters Actuals for 1 order line and clicks ‘Set Desp’ all other Order Line quantities will be pre-populated, except those manually entered. • The second button will be placed below the ‘Actual Delivered’ input area and named ‘Set Del’. This button will only pre-populate ‘Actual Delivered’ quantities, and again, it has the Debrief by Exception functionality.

‘POC’ and ‘POD’ column buttons will be amended so that the Text is visible when an Order Line is in focus.

Also in the Order Debrief tab, 2 new buttons will be placed below the current ‘POC’ and ‘POD’ columns of buttons. They will be named ‘POC All’ and ‘POD All’. They will have the same functionality as the current ‘POC’ and ‘POD’ buttons, except that instead of only applying a POC/POD to the corresponding Order Line, they will apply a POC or POD to all Order Lines in the Order Debrief tab. If some Order Lines have a POC/POD already applied, then the ‘POC All’/’POD All’ will only apply POC/POD to those that do not have a POC/POD. Please note than these 2 buttons will not include the functionality to Remove All POC/POD. This will have to be done by individual line using the current ‘POC’ or ‘POD’ buttons next to an Order Line.

The current ‘Non-Conformance’ button and ‘POD/CMR No.’ Text Box will be moved down a line to make space for the new buttons.

Finally, there will be an overall ‘Set All Actuals’ button placed on the bottom right hand side of the TRIPDTL screen. This will be used to pre-populate all Actuals with the current Planned Quantities. This is only to be used if there is no Exceptions during Debrief as it will pre-populate all Stops ‘Actual Arrive Dates/Times’ and ‘Depart Times’, all Orders ‘ Actual Despatched’, ‘Actual Delivered’, ‘Actual Weight’ and ‘Actual Volumes’ and then automatically Save all Actuals.

RIO includes change request for ‘Add Message on screen to 'Change Actual values if incorrect'’, but this will not be required due to the nature of the new functionality.

Scope

This change will be applied to system version 10.6 on CONTST and once approved CONPRD. This was requested by Consumer Networks, but as this is an improvement to current functionality, it will be released over time to all contracts, excluding SAR as it has its own code stream for screen TRIPDTL.

FUNCTIONAL DESCRIPTION

New Functionality

Below is a sample screenshot of the new TRIPDTL screen display – once opened.

Changes include: Opening with ‘Order Debrief’ tab in focus Set status button moved right, and other buttons realigned ‘POC’ and ‘POD’ buttons amended so text on label can be read New ‘Set Actuals’ and ‘Set All Actuals’ buttons at bottom of form New ‘Set Desp’, ’Set Del’, ‘POC All’ and ‘POD All’ buttons on Order Debrief tab

IMAGE

This screen can also be called from the Waterfall (TRIP_OVERVIEW) screen - by clicking the ‘Debrief’ button. The screen will open on the ‘Order Debrief’ tab, and the Trip Details of the trip selected in the Overview screen will be passed in. The screen will not be in Read Only mode, so the user will be able to input Actuals

Process Flow for ‘Set Actuals’ button

Below is a sample screenshot of a trip with the Order Details and Trip Stop details displayed. User enters Actuals for 2 stops, as these are exceptions, meaning that the planned Arr/Dep times were not met.

IMAGE

Clicking the ‘Set Actuals’ button will pre-populate all other stop Actuals, except Stop 2 and Stop 6. This is because the planned arrive times can not be met when compared to the depart times on the previous stop, which the exceptions have been entered for. E.g. Stop 1 Actual Depart is at 03:30, and will not be able to meet the Planned Arrive time of 03:23 at stop 2.

The other stop Actuals (Stop 3, 4 and 7) will be pre-populated as these times can, in theory, be met - as the driver was only 7 minutes behind at stop 1 and 11 minutes behind at stop 5. It is possible for the driver to make up the time and Arr/Dep the other stops at the Planned times. Below is a sample screenshot, after the ‘Set Actuals’ button is clicked.

IMAGE

The user will now have to fill in Stop 2 and Stop 6 Actuals manually.

If the ‘Set Actuals’ button is clicked when no Exceptions have been entered, then all stop Actuals will pre-populate with the Planned times.

Process Flow for ‘Set Desp’ and ‘Set Del’ buttons

The ‘Set Desp’ and ‘Set Del’ buttons on the ‘Order Debrief’ tab will work in a similar fashion. When a user enters some despatched quantities, and clicks the ‘Set Desp’ button, all other values will be pre-populated with the Planned values.

Below is a sample screenshot of what the user has entered, and the following screenshot is an example of how the Actuals would display as - after the ‘Set Desp’ button is clicked:

IMAGE IMAGE

The ‘Set Del’ button has the same functionality as the ‘Set Desp’, where it will populate all Delivered Actuals that have not already been entered.

Process Flow for ‘POC All’ and ‘POD All’ buttons

The ‘POC All’ and ‘POD All’ buttons will apply a POC or POD for all orders in the ‘Order Debrief’ tab. If a few orders already have a POC or POD applied, the ‘POC All’/’POD All’ will apply a POC or POD to those that do not.

Note: these buttons do not have the functionality to remove all POC/POD. This will have to be performed individually, per order, using the existing ‘POC’ or ‘POD’ button.

Below is a sample screenshot after all POC’s are applied using the ‘POC All’ button:

IMAGE

All current error trapping functionality will remain on this screen. E.g. Trying to Apply a POC when no Actual Date/Times entered will display message ‘You must specify the Actual Arrive Date’.

Process Flow for ‘Set All Actuals’ button

Finally, the button ‘Set All Actuals’ will be used to pre-populate all actual values, and perform an automatic save. This is to be used only if there have been no exceptions on Stop times, despatched quantities or delivered quantities. Below is a sample screenshot of a trip with no actual data entered - it is again followed by a screenshot displaying the trip details, if the ‘Set All Actuals’ button was clicked:

IMAGE
IMAGE

IMAGE

References

IMAGE

Glossary

IMAGE

Document History

IMAGE

Authorised By

Dave Meir	Development Manager
Suk Sandhu	TMSCC MTS Product Manager