Overview

This Function shall be capable of providing the following facilities:

(1) The ability to support the monitoring of a transport order all along its life cycle.
(2) At the phase of the execution, after achievement of all necessary operations during the preparation phase the ability to store transport order in the data store of On-board Data.
(3) During an on going mission, the ability to also support any modification required or felt necessary, associated to events and locations.
(4) The ability to indicate, program and trigger the types of monitoring of transport order progress required from the On-board Application and/or the Driver.
(5) The ability to automatically trigger reports (electronic signature of the road waybill or consignment note) or require the Driver to add relevant information.
(6) The ability to send reports on Driver initiative, pick up report and proof of delivery (or a delivery difficulty, or even refusal, etc.).

Functional Requirements

(a) receive transport order description from the create new transport order Function
(b) receive transport order description, modification or information from the Fleet Manager, inform the Driver and store this data in the store of On-board Data
(c) store transport order information in the store of On-board Data
(d) receive event from the task management Function about the transport order
(e) receive event generated from trip resources the Function
(f) for each received event inform the Driver, process required operations on required transport order and store result in the store of On-board Data:
(f1) require validity check for a new or modified transport order,
(f2) get necessary signatures at pick up, and, most, at delivery (POD),
(f3) close transport order and generate reports
(g) maintain a queue of transport orders under execution for Driver consultation
(h) process information requests about transport order from Fleet Manager
(i) receive payment receipts, associate them to transport order and store them on the store of On-board Data.

Diagrams

Parent Higher Level Function

• 8.3.1 Manage Task and Transport Order

Input logical dataflows

• fd.fvd-trip_input_3
• mffo_mgm_commercial_information
• mffo_mgm_incident_information_MTO
• mffo_mgm_statutory_information_MTO
• mffo_mgm_transport_order_status_request
• mffo_new_transport_order
• mffo_read_on_board_monitor_order_data
• mffo_task_event
• mffo_transport_order_status
• pepf.mffo_payment_receipt_MTO

Output logical dataflows

• mffo_load_on_board_monitor_order_data
• mffo_rsc_commercial_incident_information
• mffo_rsc_commercial_information
• mffo_rsc_statutory_information_MTO
• mffo_transport_order_event
• mffo_transport_order_TBC
• td.fvd-trip_output_3

User needs