• No results found

The data stores are an important issue in the Van Heezik project. The FMCS and Chainware products will keep their data stores synchronised. For instance whenever an order is entered in Chainware, the information is directly taken over by FMCS. And whenever a status of a consignment is changed the status is immediately taken over by Chainware.

Mechanisms will have to be build to synchronise the data stores Orders, Trips, Trip/Cargo status and Vehicle/Drivers between PTV and Interchain.

The following points need elaboration in the technical specification:

• definition of data that can be used and/or modified by the Fleet and Cargo Management System;

• mechanisms to control the integrity and consistency in the databases.

The data storage defined is an abstract of the logical model of the Chainware database. The following data stores are included in the model.

data store contents

Orders all consignments accepted by the forwarder

Reusable equipment reusable equipment used in transport process Order status operational status of the consignment Trip/Cargo status status of the trip and cargo

Accepted Orders all consignments accepted by the carrier

Vehicle/Drivers availability and data of resources and materials

Below is a description of each type of data storage of the fields that currently supported by Chainware. Orders consignment number departmentcode handlingcode operational period employee (adm) principal reference loading date/time unloading date/time shipper loading place consignee unloading place agent customs data COD id goods information - marks and numbers - quantity - type of package - commodity - gross weight - nett weight - cubic meters - loading meters - volume weight 3 - dimensions - goods value cost and charges - activity - purchase / sales ID - relation (debtor/creditor) - currency - exchange rate - tariff - amount in [curr] - invoice information - financial period

- reference accounting system - status code transport instructions trip reference documents - type of document - date created - document number

- way printed (EDI/printer) - status code

status code Reusable equipment consignment number date quantity type of package

type of logistic address (code) logistic address quality code status code Order status consignment number date/time place

tracking and tracing code description status code Trip/Cargo status trip number date/time place

tracking and tracing code description status code Accepted Orders same as orders Trips trip number departmentcode handlingcode operational period employee (owner) place of departure place of destination date/time of departure date/time of arrival vehicle code trailer code equipment code driver 1 code driver 2 code charter consignments planned cost and charges - activity

- purchase / sales ID - relation (debtor/creditor)

- currency - exchange rate - tariff - amount in [curr] - invoice information - financial period

- reference accounting system - status code

documents

- type of document - date created - document number

- way printed (EDI/printer) - status code

tracking and tracing status code

Vehicle Driver

vehicle number driver number

registration number name

vehicle type licenses

cost centre code cost centre code

vehicle/trailer ID salary information

charter ID (trip) time worked

reefer ID (trip) activities worked

technical information (trip) expenses made

(trip) time used (trip) kms driven (trip) fuel used

Information Flows

The origin, destination and contents for each information flow is given below. Also the supplier who will be responsible for the construction of the interface is given.

The information that is important for the demonstrator project is printed in italic. In some cases functions can reside in the same company or in different companies. When functions are external to each other the information is exchanged via EDI. When functions reside in the same company the information exchange will be an on-line process via data store synchronisation.

If applicable this distinction is made clear.

The EDI indication that is stated behind some of the descriptions, refers to the numbering of the messages within the EDI project, as described in the User Requirements.

Interface IF.2 Transport Instruction (EDI 1) who Interchain

from consignment initiation to order entry

information - request for transport information - request for quotations

Interface IF.3 Instruction Confirmation (EDI 2) who Interchain

from order entry

to consignment initiation information - transport information

- quotations

- transport booking confirmation - transport booking refusal

Interface IF.5 Consignment Status Report (EDI 6) who Interchain

from order information to shipper/consignee information - order information

- order status information (i.e. delay, arrival) Interface IF.9a Consignment Status Report (EDI 5)

IF.9.b On-line order progress report who IF.9a Interchain

IF.9b Data store synchronisation from cargo information

to order tracking information - cargo information

- cargo status information (i.e. delay, arrival) Interface IF.14.a Transport Instruction (EDI 3)

IF.14.b On-line Pick-up information who IF.14a Interchain

IF.14b Data store synchronisation from order dispatching

to order acceptance information - order information

- transport instruction

Interface IF.15 Instruction Confirmation (EDI 4) who Interchain

from order acceptance to order dispatching

information - confirmation of the instruction with freight charge - refusal

Interface IF.16 Activity Report + reusable equipment (MDC)

who PTV

from driver

to cargo monitoring

information - shipment status (loading / unloading) - reusable equipment

- working hours - free text message

Interface IF.19 Loading/Unloading orders (Download or MDC)

who PTV

from transport planning

to driver

information - order information, like addresses and goods - tripplanning (times, places, routes .... ) - reusable equipment

Interface IF.31 Location information (MDC)

who PTV

from vehicle

to fleet vehicle monitoring information - location of the vehicle

- kilometres

- cargo information (temperature) - technical vehicle information

Interface IF.35.1 Expenses, Time Report, Fuel Report, Reusable equipment IF.35.2 Km’s

who MobiCoach

from 35.1 vehicle 35.2 driver to trip data processing information - 35.1 km’s driven

- 35.1 fuel used

- 35.1 technical vehicle information - 35.2 hours worked (time sheet) - 35.2 expenses made

- 35.2 equipment - 35.2 cargo information

Interface IF.38.1 Additional Cost Message (EDI 8) IF.38.2 Invoice (EDI 12)

who Interchain from invoicing

to 38.1 consignment initiation 38.2 freight payment handling information - 38.1 additional cost warning message

- 38.2 invoice freight charges

Interface IF.48 Reusable equipment information who To be decided

from tripdata processing

to reusable equipment registration information - number of packages

- types of packages - condition - POD

Interface IF.49 Overview Reusable Equipment who To be decided

from reusable equipment registration to loading / unloading address information - statistic information

Interface IF.50 Proof of Delivery, including reusable equipmt info (EDI 10) who Interchain

from order information to consignment initiation

information - information about delivery of the consignment - damage reporting

Interface IF.51.a Proof of Delivery, including reusable equipmt info (EDI 9) IF.51.b On-line POD, including reusable equipment info

who IF.51a Interchain

IF.51b Data store synchronisation from cargo information

to reusable equipment registration

information - information about delivery consignment - damage reporting

- reusable equipment

Interface IF.52 Additional Cost Message (EDI 7) who Interchain

from invoicing to order dispatching information - explanation of cause

- charges

Interface IF.53 Invoice (EDI 11) who Interchain

from invoicing to order dispatching information - shipment identification

- charges

The priorities with respect to Interchain are:

1. Data store synchronisation with Ordis; 2. IF.2 Transport Instruction (EDI 1); 3. IF.3 Instruction Confirmation (EDI 2); 4. IF.5 Consignment Status Report (EDI 6); 5. IF.14 Transport Instruction (EDI 3);

6. IF.50 Proof of Delivery, including reusable equipment info (EDI 10) 7. IF.9 Consignment Status Report (EDI 5);

8. IF.51 Proof of Delivery, including reusable equipment info (EDI 9); 9. IF.38.1 Additional Cost Message (EDI 8);

10. IF.38.2 Invoice (EDI 12);

11. IF.52 Additional Cost Message (EDI 7); 12. IF.53 Invoice (EDI 11);

13. IF.15 Instruction Confirmation (EDI 4); 14. Reusable equipment information;

15. Upgrading of the existing interface with the external trip data processing system; 16. Quotations database;