Port ervices Corporation (.A.O.G) Electronic Data Interchange Message Implementation Guide (MIG) Version Number: 1.00 Document issue Date : 15 th Aug 2008 DOCMENT INFOAMTION: This document is version 1.00. This version supersedes all prior versions circulated or exchanged with any party. PC will not be responsible for any confusion arising from use of prior versions. Any minor modification to this document will carry version numbers 1.xx and any major modification to this document will carry version numbers 2.xx. Please feel free to make printouts for use in your organisation. PC has taken precaution to stick to ANI standards, codes used in OP-Customs sys and the codes used for registration with PC. PC has also provided translation tables wherever appropriate. Please feel free to call us for any clarification in the contact numbers given below. PC is organising a meet on 21 st Aug 2008 at 09:00 hours to 11:00 hours during which your operation controllers and IT staff could join for an open house discussion.
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) This message implementation guide aims to standardise the use of N/EDIFACT messages - BAPLIE, COPA, COAI, CODECO, MOVIN, IFTMC and APEAK in the standard format for information exchange between the Port ervices Corporation and its Port Community. This process is to standardize the information exchanged as well as replace the manual manifest with electronic document. This effort paves the way for the digitisation of vessel and container information totally; reduce errors due to data entry, effective and efficient service to the trade. The NEDIFACT message version implemented is based upon the directory D95.B of NEDIFACT. This message implementation guide takes into account the recommendation, principles and rules coming from the ITIGG (International Transport Implementation Guidelines Groups) which aims to harmonise the use of codes and segments for several kind of transport modes. Code lists mentioned in this document are exhaustive. Any additional code will have to be requested to PC in order to be added to this document. For any other information, please contact us at the following address: Port ervices Corporation (.A.O.G) P.O Box: 133 Muscat, Postal Code: 100, ultanate of Oman. Website: www.pscoman.com Tel: +968.24714000 Ext 216; Fax: +968.24711618 E-mail : m-it@pscoman.com (Manager IT) 24714000 Ext 216 amit@pscoman.com [Asst manager IT]; 24714000 Ext 376 sap-w@pscoman.com [AP-CATO] ; 24714000 Ext 282 and sh-plng@pscoman.com [ection Head Planning] 24714000 Ext 347 Web ite: www.pscoman.com First edition July 2008 2
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) CONTENT CONTENT 3 1. NDETANDING THI GIDE... 4 2. INTODCTION 6 2.1 N/EDIFACT MEAGE FOMAT 6 2.2 GENEAL NOTE FO THI GIDE 6 2.3 ELECTONIC DATA INTECHANGE (EDI) TANDAD MEAGING - N/EDIFACT 6 2.4 FNCTIONAL E FO THE N/EDIFACT MEAGE ET 8 (BAPLIE, COPA, COAI, CODECO, MOVIN, IFTMC AND APEAK) 8 2.5 FNCTIONAL LE FO N/EDIFACT MEAGE ET 9 (BAPLIE, COPA, COAI, CODECO, MOVIN, IFTMC AND APEAK) 9 2.6 DATA COMMNICATION 12 2.7 DATA TANMIION LE 13 2.8 DATA QALITY 13 2.9 CONFIMATION/ACKNOWLEDGEMENT OF TANMIION 13 3. BINE DATA ITEM IN NEDIFACT MEAGE ET 15 3.1 BINE DATA ITEM IN BAPLIE 15 3.2 BINE DATA ITEM IN COPA 18 3.3 BINE DATA ITEM IN COAI 20 3.4 BINE DATA ITEM IN CODECO 23 3.5 BINE DATA ITEM IN MOVIN 27 3.6 BINE DATA ITEM IN IFTMC 30 3.7 BINE DATA ITEM IN APEAK 33 4. MEAGE TCTE DEFINED 35 4.1 MEAGE TCTE OF INTECHANGE HEADE NB NZ 35 4.2 MEAGE TCTE OF INTECHANGE HEADE BAPLIE 1.5 38 4.3 MEAGE TCTE OF INTECHANGE HEADE BAPLIE 2.0 54 4.4 MEAGE TCTE OF INTECHANGE HEADE COPA 77 4.5 MEAGE TCTE OF INTECHANGE HEADE MOVIN 103 4.6 MEAGE TCTE OF INTECHANGE HEADE IFTMC 126 4.7 MEAGE TCTE OF INTECHANGE HEADE COAI 220 4.8 MEAGE TCTE OF INTECHANGE HEADE CODECO 252 4.9 MEAGE TCTE OF INTECHANGE HEADE APEAK 289 5. CODE EFEED IN THI GIDE 296 5.1 CODE LIT FO VOA (VEEL OPEATING AGENT) 296 5.2 CODE LIT FO CONTAINE LINE (OPEATO) WITH THEI EPECTIVE AGENT AT PC 299 5.3 CODE LIT FO THE FOWADE EGITEED WITH PC 309 5.4 CODE LIT FO TCKING COMPANIE 315 5.5 CODE LIT FO THE PACKAGE TYPE EGITEED WITH PC 354 5.6 OTHE CODE LIT EGITEED IN PC 356 5.7 EO CODE LIT FO NDETANDING APEAK MEAGE 356 6. LIT OF ACONYM 363 First edition July 2008 3
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 1. NDETANDING THI GIDE... Each of the messages has a brief description at the segment level. It gives a picture as to how segments and segment groups used are structured. A summary of their technical information is provided like their position in the message, their tag, their name, their (basic and user) status and also the repetition factor. This is followed with the detailed explanation of each of the segment groups and segments with the technical information associated with the data elements and composite data elements for each of the messages is given. In addition, a separate table gives the data elements in business terminology indicating their positions in the message. The information used in the guide is explained below:.no: Information Explanation 1. 2. 3. 4. egment Identifier egment Terminator Field eparators imple Element eparators 5. egment Group 6. sage The egment identifier (also known as Tag ) is a 3 character string that identifies which segment follows. The 3 letter code is usually a mnemonic, so for example the NAD segment contains Name and Address information. The 3 character segment identifier is always followed by the field separator + character. The segment terminator identifies the end of an EDI segment. The segment terminator is character. The field separators, separate either a simple or composite data element within a message segment. The default character is a + character. The simple element separators, separate the lowest level of data (simple element) within the EDI message segment. The default character is a : character. A set of segments grouped together in a specific order to address a business situation. The usage field indicates the status of the segment / Composite date element / imple data element in the message. The various status indicators are: 7. Character tatus 8. Base tatus (B) M C O X Mandatory Conditional mandatory under certain conditions Optional Not sed equired This is the status of the segment / Composite date element / imple data element as defined in the NEDIFACT standards. 9. ser tatus This is the status of the segment / Composite date element / First edition July 2008 4
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG).No: Information Explanation () 10. epetition () 11. imple data element as in use in PC. The maximum number of times the particular segment / Composite date element / imple data element is repeatable in the message /segment. The data type and the maximum length permitted for each of the simple data element. 12. AN..3 Alphanumeric data type of field length up to 3 characters. 13. AN3 Alphanumeric data type of fixed field of length 3 characters. 14. N..3 Numeric data type of field length up to 3 numbers. 15. N3 Numeric data type of fixed field length of 3 numbers. First edition July 2008 5
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 2. INTODCTION The purpose of this manual is to provide guidelines to the port users of Port ultan Qaboos, namely, the VOA Vessel Operating Agents, COA Container Operating Agents, Forwarders, Consignees, and other interested parties for the preparation and transfer of vessel and manifest data using N/EDIFACT messages - BAPLIE, COPA, COAI, CODECO, MOVIN, IFTMC and APEAK in the standard format. This implementation guide defines the structure of the messages to seamlessly transfer information between the Port and the various trade partners. 2.1 N/EDIFACT Message Format The messages are from the standard Electronic Data Interchange (EDI) message set as approved for use by the nited Nations/Electronic Data Interchange for Administration, Commerce, and Trade (N/EDIFACT) under the auspices of the nited Nations Economic Commission for Europe (N/ECE). These messages set are adopted by MDG for use by all the interested parties in the Port Community for the transmission of Vessel and container / cargo data to terminal / port authorities. This N/EDIFACT Message et documentation identifies the format and syntax rules that concerned parties must follow in transmitting data to the appropriate authorities in Ports or Port Community. PC has found it necessary to extend the NEDIFACT standard messages to meet certain Operational requirements that are currently unique to the Port ultan Qaboos. However, every effort has been made to conform to the overall N/EDIFACT standard. The extensions use standard N/EDIFACT segments and data elements, as well as private code sets in certain segments where they are allowed. 2.2 General Notes for this Guide This document is intended to be a technical guide for explaining the N/EDIFACT messages BAPLIE, COPA, COAI, CODECO, MOVIN, IFTMC and APEAK syntax as implemented by PC. ome data elements marked as conditional under the NEDIFACT may be mandatory under certain regulations. This guide does not attempt to explain all of the situations in which various conditional elements must be present, and it should not be seen as a substitute for PC laws and regulations (Tariff Book & Port egulations). The PC Message Implementation Guide (MIG) contains reporting requirements. Every attempt has been made to ensure this guide conforms to those reporting requirements, but in all cases, the PC laws and regulations (Tariff Book & Port egulations) take priority over the contents of this guide. 2.3 Electronic Data Interchange (EDI) tandard Messaging - N/EDIFACT First edition July 2008 6
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) PC supports seven distinct N/EDIFACT standard messages for electronic information exchange with vessel & container / cargo operators for system compliance. The EDIFACT Bay plan "BAPLIE" will be used to transmit information about ALL occupied places onboard of a vessel to the terminal operator (PC) for the inbound voyage and to the carrier from PC for the outbound voyage. In general only complete messages "BAPLIE" have to be transmitted, whereas only occupied stowage locations, either by equipment or special cargo (break bulk), should be mentioned. The NEDIFACT COAI message is a message by which the container terminal (PC) reports that the containers specified have been discharged from a seagoing vessel (discharged as ordered), or have been loaded into a seagoing vessel. The NEDIFACT COPA message is a message to order to the container terminal (PC) from the vessel operating agent (VOA) that the containers specified have to be discharged from a seagoing vessel or have to be loaded into a seagoing vessel. The NEDIFACT MOVIN message is a towage instruction message contains details of the loading profile given by the vessel operating agent (VOA), giving instructions regarding the loading, discharging and restowage of equipment and/or cargoes and the location on the means of transport where the operation must take place. The NEDIFACT CODECO message is a message by which a terminal (PC) confirms that the containers specified have been delivered or picked up by the inland carrier (road or barge). This message can also be used to report internal terminal container movements (excluding loading and discharging the vessel) and to report the change in status of container(s) without those containers having physically been moved. The NEDIFACT IFTMC message is a message wherein the vessel operating agent (VOA) & forwarder intimates the terminal (PC) about the Cargo / Container manifest. The NEDIFACT APEAK message is a message whose function is: (a) To inform a message issuer that his message has been received by the addressee's application and has been rejected due to errors encountered during its processing in the application. (b) To acknowledge to a message issuer the receipt of his message by the addressee's application. Tables 1, 2 and 3 below identify uses of the specific messages. Technical details concerning message layouts are further described throughout this document. Basically, PC uses the message set in D95B directory and the corresponding versions in MDG. The details of the various versions and the directory list are given below. Table 1: List of message initiated by the Vessel Operating Agent.No Vessel Operating Agent initiated messages NEDIFACT Version Message Function / ecipient Message Name MDG NEDIFACT BAPLIE (Inbound) 1.5 91.1 towage Bay plan / PC First edition July 2008 7
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 2.07 D95B 2.1 D95B COPA 1.2 D95B Container Discharge List / PC Container Load List / PC MOVIN 2.04 D95B 2.1 D95B Loading Profile / PC IFTMC D95B Vessel Cargo / Container Manifest / PC Table 2: List of message initiated by the Forwarder.No NEDIFACT Message Name Forwarder initiated messages MDG Version NEDIFACT Message Function / ecipient IFTMC D95B Vessel Cargo / Container Manifest / PC Table 3: List of message initiated by the Terminal Operator (PC).No NEDIFACT Message Name BAPLIE (Out bound) Terminal Operator (PC) initiated messages MDG Version 1.5 91.1 2.07 D95B NEDIFACT Message Function / ecipient towage Bay plan / VOA (VEEL OPEATING AGENT) 2.1 D95B COAI 1.2 D95B Container Discharged eport / VOA (VEEL OPEATING AGENT) Container Loaded eport / VOA (VEEL OPEATING AGENT) APEAK D00A Acknowledgement for the receipt of the messages / VOA (VEEL OPEATING AGENT) or Forwarder CODECO 1.4 D95B Container movement / status report / COA (CONTAINE OPEATING AGENT) 2.4 Functional ses for the N/EDIFACT Message set (BAPLIE, COPA, COAI, CODECO, MOVIN, IFTMC and APEAK) The functional uses of the message set are given below: First edition July 2008 8
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) a. The BAPLIE message is used in this implementation to support a number of critical information reporting functional requirements. These include: towage Bay Plan of containers in a vessel. It creates the inventory data in the PC system. b. The COPA message is used for supporting critical information for the vessel and yard operations in PC The container discharge list for inbound vessels or container load list for outbound vessels. Confirmation of the discharging or loading containers for a vessel. The details of the container operating agents of the containers in the vessel. c. The MOVIN message is used for supporting critical information for loading of the vessel and yard operations in PC. The loading profile of the vessel is received from Vessel Operating Agent that facilitates the yard planning. d. The IFTMC message is used for supporting critical information for the ownership of the container or cargo. This furnishes the ownership details of the container and the cargo contained in it. e. The CODECO message is used for providing critical information to the container operating agents. The container gated in or out of the terminal is informed to the owner of the container according to the period selected by the COA (CONTAINE OPEATING AGENT). The change in status of the container within the yard of the terminal. f. The COAI message is used for providing critical information to the vessel operating agent. Confirmation of the loading or discharging activity in the terminal is provided to the agent to facilitate the planning at the agent s end. g. The APEAK message is used for acknowledging the receipt of the critical information by PC. An acknowledgement in case there are no errors in the received EDI message. A mechanism to convey the errors observed in the EDI message in the event of failure of EDI message. 2.5 Functional rules for N/EDIFACT Message set (BAPLIE, COPA, COAI, CODECO, MOVIN, IFTMC and APEAK) The functional rules for the usage of this message set are given below. Table 4: Functional eporting ules for the various EDI messages FNCTIONAL LE FO EDI MEAGE.NO 1. NEDIFACT MEAGE NAME BAPLIE (Inbound) LE FO THE MEAGE Precondition: The BAPLIE submission is possible subject to the condition that the voyage is declared in the port. BAPLIE will be entertained only from the concerned vessel operating agent (VOA for the vessel s voyage). The vessel operating agent s declared voyage number is used to First edition July 2008 9
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 2. COPA map the BAPLIE file to the corresponding rotation number in the PC system. The PC system is scheduled to check for new uploads every 15 minutes. Cut off Time for submission: ystem treats the successful uploading time of BAPLIE as the submission time. The last BAPLIE file received before the cut off time is treated as the final BAPLIE. A late submission charge is levied on any BAPLIE uploaded after the specified time in the port regulations for various voyages. (Attached as annexure to this guide). Any BAPLIE received after the cut off time for the voyage is not auto uploaded instead the BAPLIE file to be submitted and uploaded from the planning office manually after levy of the late submission charge. Cut off Time for amendment: Any BAPLIE that is uploaded after the process of reconciliation of the Container Discharge List (submitted vide the EDI message COPA) and the BAPLIE is treated as amendment. BAPLIE for amendment after the cut off time is not auto uploaded. The planning office will upload manually after the levy of the applicable amendment charges. No amendment is entertained after the commencement of the operations and for such amendments the process of making a special request for container attribute change is made. Precondition: The COPA submission is possible subject to the condition that the voyage is declared in the port. COPA will be entertained only from the concerned vessel operating agent (VOA for the vessel s voyage) and only in a single file and not in bits and pieces. No COPA file is entertained from the COAs (Container Operating Agents). The vessel operating agent s declared voyage number is used to map the COPA file to the corresponding rotation number in the PC system. The PC system is scheduled to check for new uploads every 15 minutes. Cut off Time for submission: ystem treats the successful uploading time of COPA as the submission time. The last COPA file received before the cut off time is treated as the final COPA. A late submission charge is levied on any COPA uploaded after the specified time for inbound and outbound voyages in the port regulations for vessels coming from various ports. Any COPA file received after the cut off time for the voyage is not auto uploaded instead the COPA file to be submitted and uploaded from the planning office manually after levy of the late submission charge. Cut off Time for amendment: For Inbound voyage, any COPA that is uploaded after the reconciliation of the Container Discharge List (submitted by the EDI message COPA) with BAPLIE is treated as amendment and applicable charges are levied. COPA uploaded before the cut off time for amendment, replaces the previously submitted COPA. For the outbound voyage, any COPA that is uploaded after the reconciliation of the container load list and yard inventory is treated as amendment and applicable charges are levied. First edition July 2008 10
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) No amendment is entertained after the commencement of the operations and for such amendments the process of making a special request for container attribute change is made. 3. MOVIN Precondition: The MOVIN submission is possible subject to the condition that the voyage is declared in the port. MOVIN will be entertained only from the concerned vessel operating agent (VOA for the vessel s voyage) and only in single file and not in bits and pieces. The vessel operating agent s declared voyage number is used to map the MOVIN file to the corresponding rotation number in the PC system. The PC system is scheduled to check for new uploads every 15 minutes. 4. IFTMC Precondition: The IFTMC submission is possible subject to the condition that the voyage is declared in the port. The first IFTMC will be entertained only from the concerned vessel operating agent (VOA for the vessel s voyage), the manifest needs to contain the transfer document number through which the next forwarder for the Bill of Lading is authorized to process the manifest further. IFTMC is filed only in a single file and not in bits and pieces. The vessel operating agent s declared voyage number is used to map the IFTMC file to the corresponding rotation number in the PC system. The subsequent forwarders have to indicate the Transfer Document Number issued by the VOA in their EDI message before it is uploaded successfully as long as they are transferring the manifest. For final manifest, the transfer document number is not required. The PC system is scheduled to check for new uploads every 15 minutes. Cut off Time for submission: There is no cut off time as such for the IFTMC but no delivery or processing of delivery documents is possible in the absence of the IFTMC. Cut off Time for amendment: The DO / BOE validation signifies the cut off time for amendment without charges. IFTMC uploaded before the cut off time for amendment, replaces the previously submitted IFTMC. For cargo, the cut off time for IFTMC is the discharge commencement of cargo. Any IFTMC uploaded later than the cut off time is not auto uploaded in the system. In such instances, the VOA / Forwarder to contact the Central Documentation Office of the Port to revoke the DO / BOE validation and manually modify the concerned data. Amendment charges are levied for the same. No amendment is possible for the delivered container or cargo. 5. BAPLIE (Outbound) Precondition: After the completion of the vessel, PC will upload the out bound BAPLIE in the folder for the VOA in its FTP folder. The concerned agent may log in to the FTP folder and pick up the outbound BAPLIE. 6. COAI Precondition: After the completion of the vessel, PC will upload the COAI in the folder for the VOA in its FTP folder. The concerned agent may log in to the FTP folder and pick up the COAI. First edition July 2008 11
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 7. CODECO 8. APEAK The CODECO message is generated by the PC system based on the settings assigned for each of the COA (CONTAINE OPEATING AGENT) (Depending up on the timing defined at the time of registration.). It shows the Gate In or Gate Out or any change in the status of the container within PC container yard including stuffing completion, unstuffing completion, grounding etc. For the messages received from Port users (VOA or Forwarder), PC is in a position to acknowledge the status of the message and provide error information if the message is not in order. Invalid messages will not be uploaded in the PC system. Port sers desirous of receiving the acknowledgement for the message need to intimate at the time of registration. Code Converter 1. ize Type: PC by default accepts the standard size type of IO 2716 or 6346. Private size type is entertained subject to prior registration of the same with PC. 2. Port Code: Psc is using the N location code for ports in all the messages. For referring to other codes for the ports, please register with PC before hand. 3. Operator code (Container Line): imilarly, for the usage of a different code for the Container Lines registered in PC, the Port ser needs to register the code for the Container Line in advance. 2.6 Data Communications 2.6.1 Communicating Directly with PC PC offers its Port sers three methods to communicate electronic documents directly with PC. 1. By File Transfer Protocol: Interested port users may sign a non-disclosure agreement for transferring NEDIFACT messages in the electronic form using the File Transfer Protocol. There are two options for implementing the file transfer. Please note that this option is available for exchange of electronic documents in NEDIFACT standard format and not for other forms of documents. Through Web browser (L): The internet may be used to access the L given below to initiate a secure session with the port to deposit their NEDIFACT documents according to the assigned access rights. Go to WWW.pscoman.com/ftp.htm Enter the user name and password assigned. elect File Transfer Protocol option. Deposit the NEDIFACT message in the in folder or Cut the NEDIFACT message from the out folder. Log off and terminate the session. oftware L-VPN solution: A L-VPN client software is loaded in the port user s system. Through this client software, it is possible to establish a secure socket layer connection to initiate a secure session with the port to deposit their NEDIFACT documents according to the assigned access rights. Click the icon for the L-VPN Client. Enter the user name and password assigned. elect File Transfer Protocol option. Deposit the NEDIFACT message in the in folder or Cut the NEDIFACT message from the out folder. First edition July 2008 12
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) Log off and terminate the session. 2. By email: The port user may email the NEDIFACT message using any email client to the port as attachment to the email id: plan-ct@pscoman.com. The planning section in the container terminal will manually upload the EDI file to the PC EDI engine. 3. Manual delivery: The soft copy of the NEDIFACT message is delivered by the port user to the planning office inside the container terminal or to CDO as applicable to the message. Port personnel upload the same manually into the EDI engine. 2.7 Data Transmission ules A single transmission of a message to PC must consist of a well-formed, syntax compliant, single instance of a message from the NEDIFACT message set - BAPLIE, COPA, COAI, CODECO, MOVIN, IFTMC and APEAK. The following rules must be followed for all messages sent to PC: 1. A single transmission (message) sent to PC must include only one instance of a message from the set. 2. Only a N/EDIFACT segment terminator ( ), one byte in length, serves to separate the message into records (segments). 3. Each block must have a complete set of NB, NH, NT, and NZ header/trailer segments. 4. Each block must have a BGM segment and contain the TDT and voyage details segments. 2.8 Data Quality With the increasing volume and importance of the data being sent to PC, the quality and uniformity of data transmissions is of great concern. The following policies are followed: 1. Message syntax rules described in this document must be followed. This includes mandatory values for specified data elements and coding practices for groups of data segments (such as the vessel details). Transmissions that fail to follow these rules and practices may be rejected by the system. Also, certain syntax errors such as those involving a required segment for a segment group may cause the data for subsequent containers in the transmission to be lost. 2. No exceptions to the syntax rules will be made for any port user. 3. The field length of the key business data elements are according to the PC system requirements and may or may not be in accordance to those defined in the N standards. Therefore, please use the field length defined for the key business data elements according to that defined for the PC ystem. 2.9 Confirmation/Acknowledgement of Transmissions First edition July 2008 13
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) PC will send an application generated confirmation message to those senders who want acknowledgment after receiving and processing a NEDIFACT message transmission. The confirmation is sent as a N/EDIFACT APEAK message. First edition July 2008 14
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 3. BINE DATA ITEM IN NEDIFACT MEAGE ET 3.1 Business data items in BAPLIE Table 5: Business data items in N/EDIFACT BAPLIE.NO DATA ELEMENT EDIFACT MAPPING ser ATTIBTE tatus EDIT & LE EGMENT DATA ELEMENT TAG DATA TYPE LENGTH 1. Voyage Number TDT 0050+8028 AN p to 10 Accepts all alpha numeric characters. Though the standards prescribe AN..17. 2. Vessel Operator (Vessel Operating Agent) TDT 0050+C040:3127 AN p to 4 Validated against the code registered for the Vessel Operating agent (VOA) in the port. Though the standards prescribe AN..17. 3. Call ign TDT 0050+C222:8213 AN p to 8 Validated against the call sign registered in the port as given by Lloyd s registry. Though the standards prescribe AN..9. 4. Vessel Name TDT 0060+C222:8212 AN p to 30 Free test entry of the name of the vessel. Though the standards prescribe AN..35. 5. Last port of call (LPC) LOC 0060+3225 (For DE qualifier 3227 = 5 ) AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 6. Next port of call (LPC) LOC 0060+3225 (For DE qualifier 3227 = 61 ) AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 7. ETA DTM 0070+C507:2380 (For DE qualifier 2005 = 132 ) AN p to 35 Date value according to the format. First edition July 2008 15
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG).NO DATA ELEMENT EDIFACT MAPPING ser ATTIBTE tatus EDIT & LE EGMENT DATA ELEMENT TAG DATA TYPE LENGTH 8. ETD DTM 0070+C507: 2380 (For DE qualifier 2005 = 133 ) AN p to 35 Date value according to the format. 9. ATA DTM 0070+C507:2380 (For DE qualifier 2005 = 178 ) AN p to 35 Date value according to the format. 10. ATD DTM 0070+C507: 2380 (For DE qualifier 2005 = 136 ) AN p to 35 Date value according to the format. 11. towage Cell Position LOC 0090+C517:3225 (For DE qualifier 3227 = 147 AN p to 7 Validate the value according to IO definition for cell location - Bay/ow/Tier (BBBTT). Though the standards prescribe AN..25. 12. Weight of container MEA 0130+C174:6314 (For DE qualifier 6311 = WT and 0130+C174:6411 = KGM N p to 10 Weight value is taken in Kilograms only. Though the standards prescribe N..18. 13. Over dimensional values forward or back (length) DIM 0140+C211:6168 (For DE qualifier 6411 = CMT and 0140+6145 = 5 or 6. N p to 5 Though the standards prescribe N..15. 14. Over dimensional values right or left (width) DIM 0140+C211:6140 (For DE qualifier 6411 = CMT and 0140+6145 = 7 or 8. N p to 5 Though the standards prescribe N..15. 15. Over dimensional values (height) DIM 0140+C211:6008 (For DE qualifier 6411 = CMT and 0140+6145 = 9 ). N p to 5 Though the standards prescribe N..15. 16. Container temperature TMP 0150+C239:6246 (For DE qualifier 6245 = 2 and C239:6411 = CEL or FAH ). N 3 17. Port of Loading (POL) LOC 0160+C517:3225 (For DE qualifier 3227 AN p to 5 Validated against port code as in N location code. Though First edition July 2008 16
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG).NO DATA ELEMENT EDIFACT MAPPING ser ATTIBTE tatus EDIT & LE EGMENT DATA ELEMENT TAG DATA TYPE LENGTH = 9 ). the standards prescribe AN..25. 18. Port of Discharge (POD) LOC 0160+C517:3225 (For DE qualifier 3227 = 11 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 19. Final Port of Discharge (FPOD) LOC 0160+C517:3225 (For DE qualifier 3227 = 64 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 20. Final Destination (FND) LOC 0160+C517:3225 (For DE qualifier 3227 = 83 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 21. Container Number EQD 0190+C237:8260 (For DE qualifier 8053 = CN ). AN p to 12 Container number (number is not validated). Though the standards prescribe AN..17. 22. Container size type EQD 0190+C224:8155 (For DE qualifier 8053 = CN ). AN p to 4 Validated with IO 6346 or IO 2716 or with the private codes registered prior with the port. Though the standards prescribe AN..10. 23. Container tatus EQD 0190+8249 (For DE qualifier 8053 = CN ). AN p to 3 Validated with values "2" : Export, "3" : Import, "6" : Transhipment, '11'=Direct delivery 24. Full or Empty EQD 0190+8169 (For DE qualifier 8053 = CN ). AN p to 3 Validated with values "4" : Empty, "5" : Full 25. Attached Equipment to Container (Bundled container or reefer attachment) EQA 0200+C234:8260 (For DE qualifier 8053 = CN or G ). AN p to 17 lave container numbers if CN or the attached reefer generator number if G. If CN, then the container number is restricted to 12 Characters. 26. hipping line NAD 0210+C082:3039 (For DE qualifier 3035 AN p to 35 The code as registered with the port for the Container Line. First edition July 2008 17
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG).NO DATA ELEMENT EDIFACT MAPPING ser ATTIBTE tatus EDIT & LE EGMENT DATA ELEMENT TAG DATA TYPE LENGTH = CA ). Though the standards prescribe AN..10. 27. IMDG Code DG 0230+C205:8351 (For DE qualifier 8273 = IMD ). AN p to 7 Validated against the IMDG code f IMO 28. N DG Number DG 0230+C234:7124 (For DE qualifier 8273 = IMD ). N 4 Validated against the N Number for dangerous cargo 3.2 Business data items in COPA Table 6 Business Data Items in N/EDIFACT COPA. EDIFACT MAPPING ATTIBTE.NO DATA ELEMENT EGMENT DATA ELEMENT TAG DATA TYPE LENGTH EDIT & LE 1. Nature of the Order (Discharge or Loading) BGM 0020+C002:1001 AN p to 3 Validated against the values "43" or "118" : Discharging Order; "45" or "121" : Loading Order 2. Voyage Number TDT 0060+8028 AN p to 10 Accepts all alpha numeric characters. Though the standards prescribe AN..17. 3. Vessel Operator (Vessel Operating Agent) TDT 0060+C040:3127 AN p to 4 Validated against the code registered for the VOA (VEEL OPEATING AGENT) in the port. Though the standards prescribe AN..17. 4. Call ign TDT 0060+C222:8213 AN p to 8 Validated against the call sign registered in the port as given First edition July 2008 18
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) by Lloyd s registry. Though the standards prescribe AN..9. 5. Vessel Name TDT 0060+C222:8212 AN p to 30 Free test entry of the name of the vessel. Though the standards prescribe AN..35. 6. Container Number EQD 0130+C237:8260 (For DE qualifier 8053 = CN ). AN p to 12 Container number (number is not validated). Though the standards prescribe AN..17. 7. Container size type EQD 0130+C224:8155 (For DE qualifier 8053 = CN ). AN p to 4 Validated with IO 6346 or IO 2716 or with the private codes registered prior with the port. Though the standards prescribe AN..10. 8. Container tatus EQD 0130+8249 (For DE qualifier 8053 = CN ). AN p to 3 Validated with values "2" : Export, "3" : Import, "6" : Transhipment. 9. Full or Empty EQD 0130+8169 (For DE qualifier 8053 = CN ). AN p to 3 Validated with values "4" : Empty, "5" : Full 10. Container type movement TMD 0160+C219:8335 AN p to 3 Validates for these values only - "2" : LCL, "3" : FCL 11. Port of Loading (POL) LOC 0170+C517:3225 (For DE qualifier 3227 = 9 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 12. Port of Discharge (POD) LOC 0170+C517:3225 (For DE qualifier 3227 = 11 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 13. Final Port of Discharge (FPOD) LOC 0170+C517:3225 (For DE qualifier 3227 = 64 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 14. Place of delivery LOC 0170+C517:3225 (For DE qualifier 3227 = 7 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 15. Weight of container MEA 0180+C174:6314 (For DE qualifier 6313 = G or T and 0180+C174:6411 = KGM N p to 10 Weight value is taken in Kilograms only. Though the standards prescribe N..18. First edition July 2008 19
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 16. Over dimensional values forward or back (length) DIM 0190+C211:6168 (For DE qualifier 6411 = CMT and 0190+6145 = 5 or 6. N p to 5 Though the standards prescribe N..15. 17. Over dimensional values right or left (width) DIM 0190+C211:6140 (For DE qualifier 6411 = CMT and 0190+6145 = 7 or 8. N p to 5 Though the standards prescribe N..15. 18. Over dimensional values (height) DIM 0190+C211:6008 (For DE qualifier 6411 = CMT and 0190+6145 = 9 ). N p to 5 Though the standards prescribe N..15. 19. Container temperature TMP 0200+C239:6246 (For DE qualifier 6245 = 2 and C239:6411 = CEL or FAH ). N 3 20. IMDG Code DG 0240+C205:8351 (For DE qualifier 8273 = IMD ). AN p to 7 Validated against the IMDG code f IMO 21. N DG Number DG 0240+C234:7124 (For DE qualifier 8273 = IMD ). N 4 Validated against the N Number for dangerous cargo 22. Container Agent Operating NAD 0310+C082:3039 (For DE qualifier 3035 = CF ). AN p to 3 The code as registered with the port for the container operator (Container Line). Though the standards prescribe AN..17. 3.3 Business data items in COAI Table 7 Business Data Items in N/EDIFACT COAI. EDIFACT MAPPING ATTIBTE.NO DATA ELEMENT EGMENT DATA ELEMENT TAG DATA TYPE LENGTH EDIT & LE 1. Nature of the eport (Discharge or Loading) BGM 0020+C002:1001 AN p to 3 Validated against the values "98" : Arrival Intimation or Discharging eport First edition July 2008 20
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) "270" : Loading eport 2. Voyage Number TDT 0060+8028 AN p to 10 Accepts all alpha numeric characters. Though the standards prescribe AN..17. 3. Vessel Operator (Vessel Operating Agent) TDT 0060+C040:3127 AN p to 4 Validated against the code registered for the VOA (VEEL OPEATING AGENT) in the port. Though the standards prescribe AN..17. 4. Call ign TDT 0060+C222:8213 AN p to 8 Validated against the call sign registered in the port as given by Lloyd s registry. Though the standards prescribe AN..9. 5. Operational port of loading LOC 0080+C517:3225 (For DE qualifier 3227 = 9 ) AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 6. Operational port of discharging LOC 0080+C517:3225 (For DE qualifier 3227 = 11 ) AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 7. ETA DTM 0090+C507:2380 (For DE qualifier 2005 = 132 ) AN p to 35 Date value according to the format. 8. ETD DTM 0090+C507: 2380 (For DE qualifier 2005 = 133 ) AN p to 35 Date value according to the format. 9. ATA DTM 0090+C507:2380 (For DE qualifier 2005 = 178 ) AN p to 35 Date value according to the format. 10. ATD DTM 0090+C507: 2380 (For DE qualifier 2005 = 136 ) AN p to 35 Date value according to the format. 11. Vessel Operator (Vessel Operating Agent) TDT 0110+C082:3039 AN p to 4 Validated against the code registered for the VOA (VEEL OPEATING AGENT) in the port. Though the standards prescribe AN..17. 12. Container Number EQD 0130+C237:8260 (For DE qualifier 8053 = CN ). AN p to 12 Container number (number is not validated). Though the standards prescribe AN..17. First edition July 2008 21
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 13. Container size type EQD 0130+C224:8155 (For DE qualifier 8053 = CN ). AN p to 4 Validated with IO 6346 or IO 2716 or with the private codes registered prior with the port. Though the standards prescribe AN..10. 14. Container tatus EQD 0130+8249 (For DE qualifier 8053 = CN ). AN p to 3 Validated with values "2" : Export, "3" : Import, "6" : Transhipment, 15. Full or Empty EQD 0130+8169 (For DE qualifier 8053 = CN ). AN p to 3 Validated with values "4" : Empty, "5" : Full 16. Container type movement TMD 0150+C219:8335 AN p to 3 Validates for these values only - "2" : LCL, "3" : FCL 17. Port of Loading (POL) LOC 0170+C517:3225 (For DE qualifier 3227 = 9 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 18. Port of Discharge (POD) LOC 0170+C517:3225 (For DE qualifier 3227 = 11 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 19. Place of Delivery (FND) LOC 0170+C517:3225 (For DE qualifier 3227 = 7 ). AN p to 5 Validated against code as in N location code. Though the standards prescribe AN..25. 20. towage Cell Position LOC 0180+C517:3225 (For DE qualifier 3227 = 147 ) AN p to 25 Validate the value according to IO definition for cell location - Bay/ow/Tier (BBBTT) 21. Weight of container MEA 0190+C502:6314 (For DE qualifier 6313 = G and 0190+C174:6411 = KGM N p to 10 Weight value is taken in Kilograms only. Though the standards prescribe N..18. 22. Over dimensional values forward or back (length) DIM 0200+C211:6168 (For DE qualifier 6411 = CMT and 0200+6145 = 5 or 6. N p to 5 Though the standards prescribe N..15. 23. Over dimensional values - right or left (width) DIM 0200+C211:6168 (For DE qualifier 6411 = CMT and 0200+6145 = 7 or 8. N p to 5 Though the standards prescribe N..15. 24. Over dimensional values (height) DIM 0200+C211:6168 (For DE qualifier 6411 = CMT and 0200+6145 = 9 ). N p to 5 Though the standards prescribe N..15. First edition July 2008 22
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 25. Container temperature TMP 0210+C239:6246 (For DE qualifier 6245 = 2 and C239:6411 = CEL or FAH ). N 3 26. IMDG Code DG 0250+C205:8351 (For DE qualifier 8273 = IMD ). AN p to 7 Validated against the IMDG code f IMO 27. N DG Number DG 0250+C234:7124 (For DE qualifier 8273 = IMD ). N 4 Validated against the N Number for dangerous cargo 28. Vessel Operator (Vessel Operating Agent) TDT 0290+C040:3127 AN p to 4 Validated against the code registered for the VOA (VEEL OPEATING AGENT) in the port. Though the standards prescribe AN..17. 29. Container Agent Operating NAD 0320+C082:3039 (For DE qualifier 3035 = CF ). AN p to 3 The code as registered with the port for the container operator (Container Line). Though the standards prescribe AN..17. 3.4 Business data items in CODECO Table 8 Business Data Items in N/EDIFACT CODECO. EDIFACT Mapping Attributes.No Data Element egment Data Element Tag Data Type Edits & ules 1. Nature of the eport (Gate In / Gate Out) BGM 0020+C002:1001 AN p to 3 Validated against the values "34" : Transport Equipment Gate In eport "36" : Transport Equipment Gate Out eport 2. Voyage Number TDT 0060+8028 AN p 10 to Accepts all alpha numeric characters. Though the standards prescribe AN..17. First edition July 2008 23
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 3. Vessel Operator (Vessel Operating Agent) TDT 0060+C040:3127 AN p to 4 Validated against the code registered for the (VEEL OPEATING AGENT) in the port. Though the standards prescribe AN..17. 4. Call ign TDT 0060+C222:8213 AN p to 8 Validated against the call sign registered in the port as given by Lloyd s registry. Though the standards prescribe AN..9. 5. Operational port of loading LOC 0080+C517:3225 (For DE qualifier 3227 = 9 ) AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 6. Operational port of discharging LOC 0080+C517:3225 (For DE qualifier 3227 = 11 ) AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 7. ETD DTM 0090+C507: 2380 (For DE qualifier 2005 = 133 ) AN p 35 to Date value according to the format. 8. ATA DTM 0090+C507:2380 (For DE qualifier 2005 = 178 ) AN p 35 to Date value according to the format. 9. Container Number EQD 0260+C237:8260 (For DE qualifier 8053 = CN ). AN p 12 to Container number (number is not validated). Though the standards prescribe AN..17. 10. Container size type EQD 0260+C224:8155 (For DE qualifier 8053 = CN ). AN p to 4 Validated with IO 6346 or IO 2716 or with the private codes registered prior with the port. Though the standards prescribe AN..10. Validated with values "2" : Export, 11. Container tatus EQD 0260+8249 (For DE qualifier 8053 = CN ). AN p to 3 "3" : Import, "6":Transhipment, "":torage Empty First edition July 2008 24
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 12. Full or Empty EQD 0260+8169 (For DE qualifier 8053 = CN ). AN p to 3 Validated with values "4" : Empty, "5" : Full 13. eference Number Bill of lading for Import / Booking number for export. FF 0270+C506:1154 (For DE qualifier C506:1153 = BM or BN ). AN p 30 to s are populated as the case may be. The standard prescribes an..35 14. Container type movement TMD 0280+C219:8335 AN p to 3 Validates for these values only - "2" : LCL, "3" : FCL 15. Port of Loading (POL) LOC 0300+C517:3225 (For DE qualifier 3227 = 9 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 16. Port of Discharge (POD) LOC 0300+C517:3225 (For DE qualifier 3227 = 11 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 17. Place of Delivery (FND) LOC 0300+C517:3225 (For DE qualifier 3227 = 7 ). AN p to 5 Validated against code as in N location code. Though the standards prescribe AN..25. 18. Final Port of Destination (FPOD) LOC 0300+C517:3225 (For DE qualifier 3227 = 164 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 19. Activity location (FPOD) LOC 0300+C517:3225 (For DE qualifier 3227 = 165 ). AN p to 5 For activity changing the status of the container like CF, CX, GD. Validated against code as in N location code. 20. Weight of container MEA 0310+C174:6314 (For DE qualifier 6313 = G and 0310+C174:6411 = KGM N p 10 to Weight value is taken in Kilograms only 21. Over dimensional values- forward or back (length) DIM 0320+C211:6168 (For DE qualifier 6411 = CMT and 0320+6145 = 5 or 6. N p to 5 Though the standards prescribe N..15. 22. Over dimensional values- right or left (width) DIM 0320+C211:6140 (For DE qualifier 6411 = CMT and 0320+6145 = 7 or 8. N p to 5 Though the standards prescribe N..15. First edition July 2008 25
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 23. Over dimensional values (height) DIM 0320+C211:60088 (For DE qualifier 6411 = CMT and 0320+6145 = 9 ). N p to 5 Though the standards prescribe N..15. 24. Container temperature TMP 0190+C239:6246 (For DE qualifier 6245 = 2 and C239:6411 = CEL or FAH ). N 3 25. IMDG Code DG 0230+C205:8351 (For DE qualifier 8273 = IMD ). AN p to 7 Validated against the IMDG code f IMO 26. N DG Number DG 0230+C234:7124 (For DE qualifier 8273 = IMD ). N 4 Validated against the N Number for dangerous cargo The values used are "2" : ail 27. Mode of inland transport TDT 0390+C220:8067 AN p to 3 "3" : oad "8" : Barge 28. Transport Means TDT 0390+C228:8179 AN p to 2 The values used are 31 : Truck 29. Transport id TDT 0390+C222:8213 AN p to 7 Validated against the registered trucks in PC Validated against values 30. Activity location LOC 0400+C517:3225 (For DE qualifier 3227 = 165 ) AN p to 5 "CF" : CF "GD" : Grounding "CX" : Cross stuffing 31. Container Operator (Container Line). NAD 0420+C082:3039 AN p 35 to Validated against the code registered for the Container Line in the port. 32. Vessel Operator (Vessel Operating Agent) TDT 0290+C040:3127 AN p to 4 Validated against the code registered for the VOA (VEEL OPEATING AGENT) in the port. Though the standards prescribe AN..17. First edition July 2008 26
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 33. Container (Container Line) Agent NAD 0320+C082:3039 (For DE qualifier 3035 = CF ). AN p 35 to The code as registered with the port for the container operator (Container Line).. 3.5 Business data items in MOVIN Table 9 Business Data Items in N/EDIFACT MOVIN. EDIFACT MAPPING ATTIBTE.NO DATA ELEMENT EGMENT DATA ELEMENT TAG DATA TYPE LENGTH EDIT & LE 1. Voyage Number TDT 0050+8028 AN p to 10 Accepts all alpha numeric characters. Though the standards prescribe AN..17. 2. Vessel Operator (Vessel Operating Agent) TDT 0050+C040:3127 AN p to 4 Validated against the code registered for the VOA (VEEL OPEATING AGENT) in the port. Though the standards prescribe AN..17. 3. Call ign TDT 0050+C222:8213 AN p to 8 Validated against the call sign registered in the port as given by Lloyd s registry. Though the standards prescribe AN..9. Validates for values "E" : estow 4. Handling instructions HAN 0110+4079 AN p to 3 "HI" : hift "LOA" : Loading 5. towage Cell Position LOC 0120+C517:3225 (For DE qualifier 3227 = 147 ) AN p to 7 Validate the value according to IO definition for cell location - Bay/ow/Tier (BBBTT). Though the standards prescribe AN..25. First edition July 2008 27
PC Electronic Data Interchange (EDI) Message Implementation Guide (MIG) 6. Weight of container MEA 0170+C502:6314 (For DE qualifier 6313 = G and 0310+C174:6411 = KGM N p to 10 Weight value is taken in Kilograms only. Though the standards prescribe N..18. 7. Over dimensional valuesforward or back (length) DIM 0180+C211:6168 (For DE qualifier 6411 = CMT and 0180+6145 = 5 or 6. N p to 5 Though the standards prescribe N..15. 8. Over dimensional values - left or right (width) DIM 0180+C211:6168 (For DE qualifier 6411 = CMT and 0180+6145 = 7 or 8. N p to 5 Though the standards prescribe N..15. 9. Over dimensional values (height) DIM 0180+C211:6168 (For DE qualifier 6411 = CMT and 0180+6145 = 9 ). N p to 5 Though the standards prescribe N..15. 10. Container temperature TMP 0190+C239:6246 (For DE qualifier 6245 = 2 and C239:6411 = CEL or FAH ). N 3 11. Port of Loading (POL) LOC 0210+C517:3225 (For DE qualifier 3227 = 9 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 12. Port of Discharge (POD) LOC 0210+C517:3225 (For DE qualifier 3227 = 11 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 13. Place of Delivery LOC 0210+C517:3225 (For DE qualifier 3227 = 83 ). AN p to 5 Validated against code as in N location code. Though the standards prescribe AN..25. 14. First Port of Discharge (FPOD) LOC 0210+C517:3225 (For DE qualifier 3227 = 64 ). AN p to 5 Validated against port code as in N location code. Though the standards prescribe AN..25. 15. Bill of lading for Import / Booking number for export. FF 0220+C506:1154 (For DE qualifier C506:1153 = BM =1 or DI = Cell Position or ET ). AN p to 30 s are populated as the case may be and for BM it will be always 1 ee message for details. The standard prescribes an..35 16. Container Number EQD 0240+C237:8260 (For DE qualifier 8053 = CN ). AN p to 12 Container number (number is not validated). Though the standards prescribe AN..17. 17. Container size type EQD 0240+C224:8155 (For DE qualifier 8053 = CN ). AN p to 4 Validated with IO 6346 or IO 2716 or with the First edition July 2008 28