Low Level Function
8.2.2.1.1 Elaborate and Store Operational trip and load plan

Overview

This Function shall be capable of providing the following facilities:

(1) The ability to manage the creation of the actual details of the Freight Vehicle trip, including details of the load, once confirmation of the freight transport order has been received.
(2) The ability to ensure that the trip is created taking into account such things as the origin/destination, departure/arrival times, special requests about traffic, weather and pollution plus the nature of the freight cargo, e.g. hazardous goods or not.
(3) The ability to request any other appropriate resources for each Freight Vehicle trip.
(4) The ability to load details of the created trip into the store of Resources Data and to then request the preparation of the appropriate information about the cargo and trip in the correct form.

Functional Requirements

(a) wait for a fleet preparation requests
(b) build from all confirmed transport orders the actual trips with associated load and store it in the store of Resources Data
(c) for each trip request for allocation of all needed resources
(d) elaborate the route request to the information provider by:
(d1) providing the freight transport conditions (origin/destination, and departure/arrival time),
(d2) formulating special requests about traffic, weather, pollution,
(d3) indicating whether or not the freight if of hazardous type
(e) wait for the answer then store it under the store of Resources Data
(f) request for documents preparation.

Diagrams

The Diagram(s) is (are) the diagram(s) where you can find the function :
  • DFD 8.2.2.1 Plan & Prepare Fleet Operations
  • Functional tree 8.2

    • Parent Higher Level Function

    Input logical dataflows

    Output logical dataflows

    User needs

    Number

    Description

    9.5.1.5
    The system shall be able to transfer any necessary information about an operation, e.g. route, (hazardous or oversize) cargo, etc. to the relevant authorities, e.g. TCCs, TICs etc.
    9.5.1.7
    The system shall enable the consignee to receive information, e.g. delivery note, invoice etc. directly from the vehicle.
    9.5.1.8
    The system shall enable the shipper to receive information, e.g. destination, contractual data etc. directly from the vehicle.
    9.5.2.10
    The system shall be able to predict a time of arrival.
    9.5.2.8
    The system shall be able to provide an optimal route for each 'normal' vehicle.
    9.5.2.9
    The system shall be able to provide suitable routes for 'abnormal' vehicles, e.g. oversized, overweight, hazardous cargo etc.
    9.5.3.35
    The system shall be able to record the location of operational points, e.g. pick up, delivery, home base.
    9.5.3.38
    The system shall be able to report automatically the receipt and/or reading of incoming messages to the sender.
    9.5.3.41
    The system shall be able to assist the process of confirming that the driver is suitable qualified to take a given cargo, e.g. dangerous goods.
    9.5.4.2
    The system shall be able to manage freight and fleets in such a way that the distribution of goods in an urban area will be made in the most efficient manner.
    9.5.4.3
    The system shall be able to manage the use of (un-)loading zones to aid the distribution of goods in an urban area.