291374

DHL C-TMS

Portal TMS Airport Screen

FUNCTIONAL SPECIFICATION - 10.7

23/09/11 - 1.0
Reference: FS 291374 MS-8KNHQJ

FUNCTIONAL OVERVIEW

Client Requirement

Airport Screen

Develop web facing order query and plasma TV scrolling display of order and order fulfilment status.

Solution

C-TMS Changes: The C-TMS reason codes table will be altered to include a new reason code type element. The reason code maintenance screen will be changed so that this new element can be maintained. This will allow this element to be set to “Failure” or “Non-failure”. The “Non-failure” value will be the default value.

Calidus Portal Changes: A new airport page will be developed within the Calidus Portal web application’s TMS module. This will therefore use the existing Calidus Portal login process and menu system. A new Network Rail style will be created for the Calidus Portal web application (allowing the system to use a Network Rail colour scheme and logo).

This new page will use the full page width (i.e. replacing the existing menu links which appear down the left of the page with a single ‘Home’ button to allow the user to return to the Calidus Portal home page and restore the menus).

When the page is first called it will run a query against the C-TMS data to retrieve a snapshot of all orders which have been assigned to trips and which have a delivery date that matches the current date.

Once this snapshot has been returned the page will display the first 30* rows of the snapshot data and start a 30-second timer. After these 30 seconds the page will display the next 30* rows of the snapshot data. This will continue until there are no more rows from the original snapshot to display at which point the page will re-run the query against the C-TMS data to retrieve a new snapshot of the orders.

The user will be able to click on any of the column headings to sort the data by this column. Doing so will cause the page to query the C-TMS data again to get an up to date snapshot and start displaying this snapshot from the first 30* rows of data again.

If the user manually refreshes the page it will again query the C-TMS data again to get an up to date snapshot and start displaying this snapshot from the first 30* rows of data again.

This means the snapshot is not updated for each new 30* rows of data shown, only once all rows from the snapshot have been shown. This is to prevent any changes being made to the data causing orders to be missed.

• The 30 rows is an estimated number of rows that can be displayed on the page at one time. This may be changed and will use the maximum number of rows that can be displayed at a time.

This page will also display a date/time, this will be the date/time that the snapshot last returned data.

For each order the snapshot will return (and the page will display) the following data:

• Trip ID - The trip ID of the trip this order is assigned to.
• Order - The order reference.
• Haulier - The name associated with the haulier for this trip.
• Vehicle - The description of the trailer type associated with the stops for this order.
• Collection Point - The description of the collection point for this order.
• PTA - The time portion of the planned time of arrival for the collection stop of this order.
• Delivery Point - The description of the delivery point for this order.
• PTA - The time portion of the planned time of arrival for the delivery stop of this order.
• Status - This will return/show F (if any of the reason codes used against this order have the new reason code type set to “Failure”, see C-TMS changes above), JC (if the order has no failure reason codes and the trip is complete) or B (if the order has no failure reason codes and the trip is not complete).

The text for the data for an order will be colour coded based on the Status returned from the C-TMS query (see above). If this is JC (Journey complete) the text for this orders data will be shown in green, if the status is B (Briefed) the text for this orders data will be shown in black and if the status is F (Failed) the text for this orders data will be shown in red.

The functional specification will include a sample layout for the new airport page showing the layout for these elements. All of these data elements will be display items only, i.e. the user will not be able to click on any of these to ‘drill down’ into a more detailed display.

Notes:

• The ETA times included in the original change request are not yet available and so will not be included in this development.
• The data retrieval for this data will assume that none of the orders are being cross-docked (otherwise an order could have multiple trips, multiple collection & delivery points etc.).