To simplify the work of the EquipmentOperator and to avoid transport order information (eg product, loading date and loading location information) needs to be re-typed when assigning a product load from a transport order to an equipment ID by the despatcher, the digital eECD process allows the Seller to send the transport order information upfront via Elemica - NxtPort to the ECLIC platform . This integrated process allows the dispatcher to simply assign the equipment while all required order information is copied automatically. A schematic overview between the Non-integrated and Integrated process can be find below:
1.1 Non-integrated Seller process
In the “non-integrated Seller” eECD process, the equipment is assigned manually by the dispatcher who select the seller, product and loader and complete the order reference and loading location.
1.2 Integrated Seller process (e.g. with Elemica or other transport order communication platforms)
In the integrated Seller eECD process, the transport order reference information is used as a search key by the dispatcher on the ‘create or assign load’ screen. If the transport order was received, correctly mapped to a loading location and assigned to this equipment operator by the Seller, the transport order and all its delivery notes are visualized for the user to select the correct delivery note line (DN_LINE). When the selection is made, the seller/loader/product/loading date and loading address fields are automatically copied from the DN_LINE information.
In case the “transport order” search key is used, the transport order is only be made visible to the transport company to whom the transport order was assigned (part of the data provided by Elemica). In other words, each Elemica transport order transaction has a valid eECD licenced EqOp assigned and the search key is a combination of the EqOp and transport order reference. This link is handled automatically by the eECD platform upon reception of the transport orders.
The Elemica eECD process and XML message format can be re-used for other companies and IT integrators as per following scheme:
The typical XML example message and format used to exchange the ECLIC uniform data fields can be found here:
From a Seller point of view there are 2 supporting integration files or tables provided:
An extended “loading location” master data CSV file to be able to assign loading locations automatically based upon the transport order message data. An example of the CSV file can be find here below and this file is maintained by the Seller - location manager and admin role.
2. a Duns translation table per Seller to ensure that the organizations used within the transport order messages do matches with the organization on the ECLIC platform. This table is maintained by the Seller via NxtPort using the Jira ticketing process. As example of such table you can find below
Code on Elemica order message
Code on eECD platform
Bertschi Belgium NV
Hoyer GmbH Internati
Lanfer Logistik GmbH
Wauters Global Logistics N.V.