• Information Technology

LICT processes the following standard EDI formats:

Message Type Version Automated 
1 BAPLIE Import  1.5,2.0:1921,D95B 
2 BAPLIE Export 1.5,2.0:1921,D95B Yes
3 COARRI Load (Export) 1.2:D95B Yes
4 COARRI Load (Export) 1.2:D95B  
5 COPRAR Discharge (Import) 1.2:D95B  
6 COPRAR Load (Import) 1.2:D95B  
7 MOVINS (Import) 2.0:D95B
8 CODECO 1.3,1.4:D95B Yes

Automated messages are automatically generated by the TOS system and dispatched to the client at a predefined email address.

The EDI messages are further explained as follows:

I. BAPLIE (Ver.1.5, 2.0:1921, D95B): Bay Plan

The BAPLIE file is the first message received by LICT from the Line Operator or any representative Agency. The file is imported into the TOS EDI system which will simultaneously update the vessel’s stowage plan.

LICT Operations Planners will then have clear information of how containers are stowed on the vessel, that is, the vessel’s arrival condition. Information (container data) at this stage is not expected to be entirely accurate, but there should be enough information for an LICT Operations Planner to know:

The number of containers

The number of containers to be discharged

The container number, size, type, IMO class

The container’s expected next port of discharge

Such information is important for logical planning where both vessels and the yard are concerned.

Before or after a vessel’s departure, LICT can send a BAPLIE Export message (Version 1.5 or 2.0). In the case of vessel departures, this will be generated and dispatched automatically by the TOS system.

II. MOVINS (Ver. 2.0: D95B): Stowage Instruction

The MOVINS file is a second stage message from the Line Operator or any representative Agency concerning the same vessel for which a BAPLIE file would already have been received. The file is imported through the TOS EDI system. Although not essential, this message is particularly useful because Planners will have instructions on all containers which are to be discharged, shifted, or re-stowed.

Projections are therefore automatically created. LICT Operations Planners need these to check instructions, apply the instructions received, and make any changes to the projections.

There is no need to export any MOVINS file from the Terminals (Port). MOVINS files will only be received from the Operator or owner of the Means of Transport.

III. COPRAR (Ver. 1.2: D95B): Container Loading /Discharge Order

The COPRAR file is also a second level message, received by LICT from a container Line Operator for the containers that the Line is representing. The file is useful because upon importing it from within the TOS EDI system, LICT Operations Planners will have further updated information regarding the records of containers which are to be discharged or to be loaded.

It is important to note that for all COPRAR messages, that is for both discharge and loading orders, LICT expects one 'original' message to be sent when the Agent / Line finalises the order. Any subsequent changes are to be communicated via email messages, or through other mediums such as fax lists, that should clearly highlight changes to the original COPRAR order.

i. COPRAR Discharge [SMDG Document 43]

The BAPLIE file might not contain updated container records (for example destination port codes). The COPRAR Discharge message is received from the various Line Operators who have containers on a particular vessel. This means LICT may receive several COPRAR Discharge messages from various Shipping Lines for any single vessel.

Container records specified in each COPRAR file received, from every single client, is validated against the containers that were originally received on the BAPLIE. As such containers would have been registered in the host system at BAPLIE import stage.

On importing the COPRAR file, any differences, such as container prefix or number differences on the vessel’s discharge list are highlighted, but weight, POD, size, types, missing container records or extra container records etc. are automatically and transparently updated by the host system. Therefore, LICT will have an updated discharge list for every respective Agent. It is important to note the implications of such automation, i.e. that the COPRAR Discharge message is considered to have priority over BAPLIE messages.

ii. COPRAR Load [SMDG Document 45]

In case of a COPRAR Load order, the containers specified in the COPRAR file sent by the Agent is tagged (Out Bound vessel code is automatically updated) and the loading list is automatically generated.

Special attention must be given especially when dealing with transhipmentcontainer records. Certain information in the loading order COPRAR file, which does not correspond with the information on the Terminals’ host database, must not differ from the corresponding record’s information on the TOS system. Such information includes but is not limited to container prefix or number, weight, POD and so on. Such differences are highlighted and investigated.

IV. COARRI (Ver. 1.2:D95B): Container Loading/Discharge Report

The COARRI file is a stage three message, and is transmitted by LICT to the Line Operators or any representative Agency after discharge or loading operations have been completed. The file is useful to the Line Operator or representative Agency because it will contain container records which would have been either discharged or loaded, re-stowed or shifted from / to a vessel.

This message acts as a final confirmation of containers which have been either discharged or loaded, re-stowed or shifted from / to a vessel by the Terminal to the Line Operator or any representative Agency.

V. CODECO (Ver.1.3, 1.4: D95B): Container Delivery Confirmation

CODECO provides the definition of the Container gate-in/gate-out report message. The CODECO message completes the cycle of an import delivered container discharged from vessel or starts the cycle of an export container received from truck or rail to be loaded to a vessel.

The message acts by which LICT confirms that the containers specified have been delivered or picked up by an inland carrier (road, or rail).

CODECO messages will be sent automatically to the requesting agents/shipping line twice a day by the TOS EDI system.
Lattakia International Container
Terminal LLC
Lattakia Port, Lattakia, Syria
Tel: +963 41 5011
Fax: +963 41 463014