UG 281363 New CTMS Execution Screen

Solution Overview

A new Execution screen will be created.

The screen will allow all of the functionality of the existing Trip Debrief screen, plus modifications to allow for:

• Extended ODO entry
• Driver Briefing
• Driver Exception Handling

The screen will be optimised for each trip status, showing the user the necessary data entries for each step, depending on the status of the order.

Extensive use of popups will be used to ensure that the entry of the data is a seamless as possible, directing the user to enter the data in as close a way to the operational requirement as possible.

An increased auditing level will be added, as well as Load ID visibility, to allow users to see how the new functionality would integrate into the existing process.

The styling of the product will approach DHL standards and colour schemes, to show the styling capability of the new product UI.

Auto-complete - This shows data in the database by matching against the user's entry as they enter it. The functionality provides a seamless lookup system. Note that this is buffered, to prevent unnecessary requests to the database and reduce load.

Tab blocks - These allow panels of data to be shown or hidden by clicking on the tab required. These blocks help make better use of available screen space

Accordion blocks - These allow data to be shown or hidden by clicking on the title bar. These blocks help make better use of available screen space, as an alternative to Tab blocks.

Resizing blocks/data elements - blocks of data are only as big as they need to be, resulting in better use of screen space. Labels and data will resize based on the resolution of the screen, to better support lower-resolution devices. Where the resolution is too low to show all data, scroll-bars are then used, both within panels and for the entire screen.

Validator Call-outs - these display pop-up bubbles next to data that has failed validation, making it easier to validate and enter whole blocks of data without having to submit data several times. As each validation error is cleared, the call-outs will disappear. Note that the call-outs can be created to link through to further screens (for example, to call a maintenance screen to enter data).

Modal Popups - these pop-up screens are used extensively throughout the product. They allow for cleaner entry of data, by expanding and extending the data being entered from the normal screen. They make the entry of data cleaner and easier and enhance readability.

Adjustable Grids - Grids of data can be manipulated when using the screen to show only the data required at this stage. Further, the data in the grids can be paged (to save space), sorted (for ease of use), user-definable (manually choosing columns to display) and editable (for direct data entry into the grid).

Links - web-based systems make extensive use of links. This allows the systems that use them to interoperate between screens without having to add space-expensive buttons.

Masked Edit Boxes

Scope

This is a prototype, showing the capability. There is a simplified database in use in the back-end, with demonstration data. It is unlikely that updating data will be required but, where possible, the prototype will incorporate this.

C-TMS Execution Screen

The screen begins by requesting the user to find a trip. This can be through the traditional CTMS mechanism of choosing a schedule and a trip from the drop-down lists provided, or by directly entering a trip in the provided box. Simply typing part of the Trip ID will match all similar trips, which can be selected from the list. This is an example of an Auto-complete entry box.

Once selected (by clicking the provided button), the screen displays the trip details.

The details displayed are relevant to the status of the trip:

• Planned
• Accepted
• En Route
• Complete
• Debriefed
• Confirmed

A top panel is shown to display the current Status of the Trip, allow moving to the next Status, and optionally display an audit history of the trip.

The screen makes use of Accordion blocks for the different areas of data (there are 3 panels: data entry, Orders list and Trip Stops list), and Tab blocks for data entry.

Each status of the Trip is covered below, showing the main features.

Planned

A General tab is displayed and open for the Trip, showing general data and allowing the user to enter and view Vehicle and Driver. Drop-down lists are used for these elements. Validation is performed and displayed in-line through Validator Call-outs.

Optionally, the user may enter and view Crew and Instructions information, by clicking on the appropriate button. These are entered and validated through a Modal pop-up screen.

When a driver and vehicle have been entered, the user will be prompted to change the status to Accepted if required.

The screen also displays a list of Orders on the Trip. Only the columns required at this stage are shown (for example, no Delivered quantities or POD are displayed at this stage). Note that the grid also shows a link to the Load number associated to the Order - clicking this will allow you to see all orders and trips associated to that load.

A list of Trip stops is shown at the bottom of the screen. Again, all unnecessary columns have been removed, and data cannot be edited at this stage.

Re-plan and Add Stop buttons are available from this point, to call additional screens (not part of prototype).

Accepted

Re-plan and Add Stop links will be available from this point, to call additional screens (not part of prototype).

Entry button to show status of trip, allowing change to next status only. At this stage, write an audit entry and link to Trip, Driver.

If change to next status, check that the Driver Brief and Despatched Quantities information has been entered - if not, popup validation forcing entry as below (automatically switching between tabs/accordions as necessary.

Accordion display First accordion panel, two tabs, general (from above) then

Driver Brief panel (open)

Some questions with tick box and entry:

• Keys given to driver
• Advise of route and vehicle
• Advise of TLC drops of Traffic Issues
• Check Driving License
• Enter shift start time - time entry only.
• Ops 13 checks carried out

All are required.

Save button.

User must enter all values. Validation popups if not entered.

Saving this will prompt the user to change the status to En Route.

Accordion Panel (closed) with ability to see order details grid as above, plus Despatched quantities:

• Stop
• Load Location
• Stop
• Unload location
• Cust Ref
• Planned and despatched qty, weight and Volume, UOMs together
• Load Number

Despatched quantities must be entered.

Button under despatched quantities to allow all to be set to planned quantities (if not already entered).

Save button.

Panel (not part of accordion) with Grid of Stops under tab panel as above.

En Route

Re-plan and Add Stop links will be available from this point, to call additional screens (not part of prototype).

Entry button to show status of trip, allowing change to next status only.

History link will be available from this point, to call a separate screen with the Trip ID as a parameter.

If change to next status, check that the Order Quantities and Trip Times have all been been entered - if not, popup validation forcing entry as below. Also needs to check that at least a Start and End ODO have been entered.

At this stage, write an audit entry and link to Trip, Tractor, Driver.

Accordion display First accordion panel (closed), three tabs, General, Driver Brief (from above) then: Driver ODO:

• Grid showing
• Date
• Time
• Type (Start/End/Fuel)
• Mileage
• Fuel Drawn

Save button

Can add records at any time for any type. At this stage, write an audit entry and link to Trip, Tractor, Driver.

Second accordion panel (open) with ability to see order details grid as above, plus Delivered quantities:

• Stop
• Load Location
• Stop
• Unload location
• Cust Ref
• Planned, despatched and Delivered qty, weight and Volume, UOMs together
• Reason Code
• Load Number

Delivered quantities must be entered. If the delivered quantity entered does not match the Despatched quantities, a Reason code must be entered. Do this through a Popup, allowing entry of reason code and displaying description. A comment box should also be allowed. A Trip audit should be written if this is the case.

Button under delivered quantities to allow all to be set to despatched quantities (if not already entered).

Panel (not part of accordion) with Grid of Stops under tab panel as above. Also add:

• Actual arrival and depart date and time.
• ETA arrival date and time.
• Actual Distance - entered
• Actual Time - calculated

Actual arrival and depart date and time and actual distance for each stop can be entered. Only the first row's data can be entered initially.

On entry of first stop's actual arrival/depart date and time, check whether delivered quantities entered for all orders to that stop. If not, pop open an entry grid for the orders only, forcing entry of quantities and reason code as above. When entered and saved, update the orders panel above.

Also at this stage, check the arrival time against the delivery window against the orders associated to the stop. If the arrival time is outside the window associated to the order(s), pop up a window showing the orders affected and prompt to enter a reason code as before. This reason should be applied to all affected orders. A Trip Audit should be written if this is the case.

Once first entered, can save - that's OK. At this stage, write an audit entry and link to Trip, Tractor, Driver.

The user can then continue entering against the following stops one by one.

ETA dates and times will be forecast from outside the system. If they are available, the system needs to RAG-colour the ETA fields:

• If the ETA against a stop is later than the delivery window of any orders associated to that stop, the background should be coloured red.
• Otherwise, the background should be coloured green.

Furthermore, the following stops should then be checked based on the new calculated ETA depart and planned drive time against the stop, to predict an ETA against these lines. The same check should be performed against these following trips. If any of these further calculated ETAs are outside the delivery window of any orders associated to the stop, the ETA fields should be coloured Amber.

Clicking on a Red-coloured ETA field should pop up a window allowing the user to email all affected customers with their new ETA.

Button under Actual Dates/Times to set to Planned (if not already set)

When all quantities and dates entered, prompt user whether they want to change status to Completed.

Completed

Entry button to show status of trip, allowing change to next status only.

History link will be available from this point, to call a separate screen with the Trip ID as a parameter.

If change to next status, check that the Driver Debrief information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions/popups as necessary. At this stage, write an audit entry and link to Trip, Driver.

Accordion display First accordion panel (open), four tabs, General, Driver Brief, Driver ODO (from above) then:

Driver Debrief tab: Checklist of items:

• Ops 13 Carried out
• Defect Found
• Tick Vosa Checked Vehicle
• Update Fleet Compliance Check List
• Button to show Driver Discrepancies
• Checkbox to show discrepancies dealt with
• Shift End Time entry

Save button

Driver Discrepancies pops up a window showing:

All numbered discrepancies (late arrivals, departures, delivered quantity changes) in a grid.

A comment should be allowed to be added per discrepancy.

Save button

When all data entered, ask user whether they want the status to go to Debriefed.

Debriefed

Entry button to show status of trip, allowing change to next status only.

History link will be available from this point, to call a separate screen with the Trip ID as a parameter.

If change to next status, check that the POD information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions/popups as necessary. At this stage, write an audit entry and link to Trip.

Accordion display

As above, with Orders panel (shown) allowing entry of POD at end of grid - all other items display only.

The POD entry will consist of a series of check boxes against the grid, with a button under to set all as received. If the POD is set, provide a button/icon to view the POD through a popup.

Trips panel can now be closed as part of the accordion.

Confirmed

History link will be available from this point, to call a separate screen with the Trip ID as a parameter.

Accordion display

As above, but with Finance tab (part of general accordion) shown: Show grand total of payments and button to add new payments.

Trips panel closed as part of the accordion.

Audit Screen

Audit records are written at one of three levels (Trip, Tractor, Driver) at various stages in the process above. This screen reports on them.

Screen accepts parameters of Trip, Trailer or Driver.

For Trip - display all records found. Any others, limit to 20 to a page.

For Trip, get Audit Type records of Trip for the supplied Trip ID. For Tractor, get Audit Type records of Tractor for the supplied Tractor ID For Driver, get Audit Type records of Trip for the supplied Driver.

The page should display the information in the audit record, plus links for whatever other levels this audit record links to.

So, we have the following:

Audit 1, with information "Driver Briefed" is linked to the Trip ID and the Driver ID

Audit 2, with information "Trip En-Route" is linked to the Trip ID, Tractor ID and Trailer ID.

etc.

If we search for the Trip ID, we will return both audit records.

If we search for the Tractor ID, we will get only audit 2.

If the user clicks a link against an audit, call the same screen with the new parameter.

There should be a capability to click an audit record and see all the details, showing comments entered against the audit, and an ability to add more comments.

Load Screen

This screen shows all orders associated to the load ID passed in.