MESSAGE IMPLEMENTATION GUIDELINES. Transportation Status

Transcription

1 Transportation Status This message description is a subset of international UN/EDIFACT message IFTSTA D.14A Published by BESTFACT Page 1 Date of release: Version: 1.0

2 Contents 1 General information of the actual message and the scope of its application Usage of the message and its restrictions on use Contents The actual guideline and its connection to other documents Updates Prerequisites Related Sources of Information Notes The work process to which the message relates Scope of the Process Parties in the Process Transportation Status Information Exchanging Process Message Document Content Specification Structure of the message Message Strcture All Segments Message Structure Used Segments Message Structure Diagram Definition of the message Message Header (UNH) Transportation Status Identification Information (BGM) Date of Transportation Status (DTM) Party Information (NAD) Consignment Information (CNI) Consignment Status (CNI/STS) Consignment References (RFF) Transportation Event Date and Time Information(DTM) Transportation Event Acknowledging Party Information (NAD) Page 2 Date of release: Version 1.0

3 6.10 Contact Information (NAD /CTA) Form of Contact (NAD/CTA/COM) Transportation Event Location (LOC) Package Identification (PCI) Transportation Event Transportation Unit (EQD) Transportation Event Transportation Unit Measurements (EQD/MEA) Package Dimensions (EQD/DIM) Message Trailer (UNT) message example Appendices Appendix 1: UN/ECE Recommendation N Trade and Transport Status Codes Appendix 2: 8155 Equipment size and type description code Appendix 3: 9013 Status reason description code Appendix 4: Service segments UNA, UNB and UNZ Page 3 Date of release: Version 1.0

4 1 General information of the actual message and the scope of its application 1.1 Usage of the message and its restrictions on use This document contains message implementation guidelines of a subset of UN/EDIFACT (United Nations Electronic Data Interchange for Administration, Commerce and Transport) IFTSTA (International multimodal status report message) based on the directory D.14A. The message is used to send status information of a transport from a carrier to a consignor and a consignee company. The message defined in this document is meant only for exchanging status information of a transportation situation. The business partners have to be absolutely certain about that the receiver of the message has possibilities to handle the status information in their information systems before they start to use the message. There are certain data elements in this message document that can be found on both header and row levels. If the data item is defined on the header level it affects the whole message document. However if the same data item is also defined on a row level it will overrule on that row the definition given on the header level. This document was made by Bestfact in the subproject Simplifying Standard Message Exchange for increasing the usage of electronic procedures in logistics. The subproject began on the 1 st of December 2014 and ended on the 30 th of June This document was created by the Finnish Information Society Development Centre (TIEKE). The purpose of this document is to increase the willingness of the companies to take electronic data interchange into use, to accelerate information system development processes and to decrease costs of information system integration by creating a common international recommendation for exchanging transportation status information. The aim of this document is also to decrease the needs of companies to create their own specifications that are not compatible with the universal message standards. Another aim is to speed up adoption of new ways to exchange information between companies and also to insure and improve competitiveness of the companies. This document is meant to be a guide in the negotiations between business partners that want to start using electronic data interchange between each other. The document can also be used in the development work of existing information systems. This document is created for the use and the needs of managers who have negotiations with their business partners and information technology specialists developing the data systems and electronic data exchange of the company. 1.2 Contents Chapter 1 General information of the actual message and the scope of its application describes the usage of the message defined here. It also presents the application restrictions. Page 4 Date of release: Version 1.0

5 Chapter 2 The actual guideline and its connection to other documents lists the most important prerequisites and some other useful sources of information for the reader of this document and presents the update information of this document. Chapter 3 The work process to which the message relates presents the business process in which the message presented in this document relates to with the related parties and their activities. Chapter 4 Data content of the message presents the information of the transportation status message as a list and it also defines the mandatory and optional elements for each mode of transport. Chapter 5 Structure of the message presents the structure of the UN/EDIFACT IFTSTA D.14A message with segment lists and a diagram. There are two segment lists in the chapter. The first one presents the segment structure of the entire message. The second list presents segments contained in this guide. The structural diagram presents only the segments the usage of which are introduced in this document. Chapter 6 Definition of the message presents the structure of the header level and the row level and it describes the usage of segments, elements, and codes. Chapter 7 Message examples gives some examples of the usage of the IFTSTA Transportation Status Message. Chapter 8 Appendixes presents the most important code lists for the codes used in the message which cannot be presented in the chapter 6, the presentation of the service segments UNA, UNB and UNZ the mapping table between the used elements of the UN/EDIFACT message and the correspondent used UBL/XML message as a separate excel document, a table as a separate excel table containing the used data elements of the actual message so that companies can map their own database elements with the elements of the message. Page 5 Date of release: Version 1.0

6 2 The actual guideline and its connection to other documents 2.1 Updates Date/Author Version Comments/changes Heikki Laaksamo 1.00 The first version. 2.2 Prerequisites In order to understand the technical backgrounds of this document the reader must be familiar with UN/EDIFACT (United Nations Electronic Data Interchange for Administration, Commerce and Transport) and EDI (Electronic Data Interchange). UN/EDIFACT is a syntax and a message dictionary which presents the form, the structure and contents of the message. EDI is a general name for the ways to interchange information electronically. 2.3 Related Sources of Information EDIFACT standard and the directories ( ) UN/CEFACT recommendations ( ) UN/EDIFACT standard versions and service segments ( ) UN/ECE Dangerous goods transportation ( ) 2.4 Notes All national and international recommendations of the contents of a transportation status have been taken into account in the creation process of this document in the extent they were applicable. Page 6 Date of release: Version 1.0

7 3 The work process to which the message relates 3.1 Scope of the Process In this process description only the transportation status exchanging process is described. The transportation status information is transmitted electronically as an UN/EDIFACT IFTSTA message between the parties. The activities in the process before the transportation status exchanging, for example making the carriage contract or requesting for quotation, transportation ordering, and sending the waybill have been left out of the description. Activities occurring later in the process e.g. invoicing have also been left out of the transportation status process description. 3.2 Parties in the Process The following table presents the parties involved in the transportation status information exchanging process. Party Carrier party Role The party that takes the consignment to be transported. The party that is responsible for supplying the transportation service. The party that hands over the goods to the receiver. The party that sends the transportation status message. The consignor party The party that prepares consignment. The party that hands over the goods for transportation. The party that receives the transportation status message. The party that undertakes the required actions based on the transportation status information. The consignee party The party that receives the transportation status message. The party that undertakes the required actions based on the transportation status information. The party that receives the goods. A third party (an agent, a terminal etc.) The party that receives the transportation status message. The party that undertakes the required actions based on the transportation status information. Table 3.2.1: The parties involved in the transportation status information exchanging process Page 7 Date of release: Version 1.0

8 3.3 Transportation Status Information Exchanging Process Figure represents different activities of a transportation status information exchanging process as they are divided between the three parties introduced in the chapter 3.2. Figure 3.3.1: The transportation status exchaning process The following table contains the activities of the parties involved in the transportation status exchanging process described in the figure Page 8 Date of release: Version 1.0

9 Party Activity Description The consignor party / A third party (an agent, a portal etc.) The consignee party / A third party (an agent, a portal etc.) Preparing consignment Handing over goods Receiving status information Processing status information Receiving status information Processing status information Receiving goods The consignor prepares the consignment for transporting The consignor hands over the goods for the carrier party to be transported. The consignor of the goods or a third party receives the consignment status electronically. The consignor of the goods or a third party processes the consignment status message and undertakes the required actions based on it. The consignee of the goods or a third party receives the consignment status electronically. The consignee of the goods or a third party processes the consignment status message and undertakes the required actions based on it. The consignee receives the goods. Carrier Party Picking up goods The carrier party delivers the transportation equipment according to the agreement to the location of the collection and picks up the goods to be transported. Transporting goods Creation status information Sending status information Handing over goods The carrier party transports the goods as is defined in the waybill. The carrier party creates the transportation status in their own information system when the situation of the transport so requires. The carrier party sends the transportation status message electronically to the consignor of the goods, to the consignee of the goods and/or to a third party. The carrier party hands over the goods to the consignee party. Table 3.3.1: The activities of the parties involved in the transportation status information exchanging process Page 9 Date of release: Version 1.0

10 4 Message Document Content Specification The following table represents the list of information of the transportation status message. In the third column there are also the identifiers of the segments in which the actual piece of information is situated in the message. There is a linkage to the actual segments in the chapter 6 Definition of the message in the fourth column. The four right most columns indicate which piece of information is mandatory, optional or not used for each mode of transport. The receiver of the message can use the information sent by the message issuer according to the extent to which their information system is capable to handle the data. Therefore the receiver of the message must not save all the data that is received and classified as optional. However the sender of the message is obliged to send all the information that is classified as mandatory and the receiver has to handle and save all this information in to their information system. M (mandatory), O(optional), C(conditional), R(recommended) Page 10 Date of release: Version 1.0

11 Information content Observation / example Segment Section Road transport Rail transport Maritime transport Air transport Message identifier UNH 6.1 M M M M Document type BGM 6.2 M M M M Transportation status identifier Transportation status date and time BGM 6.2 M M M M DTM 6.3 M M M M Party information Role Party identifier Party name The sender of the transportation status message The receiver of the transportation status message Either the name or the party identifier must be given Either the name or the party identifier must be given NAD 6.4 M M M M NAD 6.4 M M M M NAD 6.4 C C C C NAD 6.4 C C C C Page 11 Date of release: Version 1.0

12 Transportation event information The running row number of the transportation status message The identifier of the transportation document Transportation event code Waybill, carrier s identifier Collected, Damaged, En route, etc. CNI 6.5 M M M M CNI 6.5 M M M M CNI/STS 6.6 M M M M Transportation event text Textual form CNI/STS 6.6 O O O O The reason code for the transportation event code The reason for the transportation event text Damaged, Goods units missing, Weather conditions, etc. Textual form CNI/STS 6.6 M M M M CNI/STS 6.6 O O O O Transportation event references Reference type Waybill Carrier s reference number RFF RFF RFF 6.7 M M M M 6.7 O O O O 6.7 O O O O Page 12 Date of release: Version 1.0

13 Reference identifier Consignee s reference number Consignor s reference number RFF RFF RFF 6.7 O O O O 6.7 O O O O 6.7 M M M M Transportation event related date and time Date and time type Date and time of event Date and time of event DTM DTM DTM 6.8 M M M M 6.8 M M M M 6.8 M M M M Date and time expression format DTM 6.8 M M M M Transportation event acknowledging party Identifier of organisation of acknowledging party NAD 6.9 O O O O Name of organisation of acknowledging party NAD 6.9 O O O O Identifier of department of 6.10 O O O O Page 13 Date of release: Version 1.0

14 acknowledging party Name of department of acknowledging party NAD/CTA NAD/CTA 6.10 O O O O Name of person of acknowledging party NAD/CTA 6.10 O O O O Acknowledging party contact type NAD/CTA/ COM 6.11 O O O O Telephone number Mobile phone number Telefax address Other contact channel (URL, Skype address) NAD/CTA/ COM NAD/CTA/ COM NAD/CTA/ COM NAD/CTA/ COM NAD/CTA/ COM 6.11 O O O O 6.11 O O O O 6.11 O O O O 6.11 O O O O 6.11 O O O O Acknowledging party contact number / address NAD/CTA/ COM 6.11 O O O O Transportation event Page 14 Date of release: Version 1.0

15 location Location code Location name LOC LOC 6.12 O O O O 6.12 O O O O Package information Package identifier type Package identifier PCI PCI 6.13 O O O O 6.13 O O O O Transportation unit Transportation unit identifier Transportation unit type Transportation unit size and type code Transportation unit size and type in text form EQD EQD EQD EQD 6.14 O O O O 6.14 O O O O 6.14 O O O O 6.14 O O O O Page 15 Date of release: Version 1.0

16 State of reloading Original transportation unit Present transportation unit EQD EQD 6.14 O O O O 6.14 O O O O Measurements Measurement type EQD/MEA 6.15 O O O O Measurement Cargo loaded Temperature EQD/MEA EQD/MEA EQD/MEA 6.15 O O O O 6.15 O O O O 6.15 O O O O Measurement characteristics EQD/MEA 6.15 O O O O Measure Number of units Observed Out of range Weight, volume EQD/MEA EQD/MEA EQD/MEA EQD/MEA 6.15 O O O O 6.15 O O O O 6.15 O O O O 6.15 O O O O Temperature Measured when a deviant value is detected EQD/MEA 6.15 O O O O Page 16 Date of release: Version 1.0

17 Measurement unit EQD/MEA 6.15 O O O O Package dimensions Dimension characteristics EQD/DIM 6.16 O O O O Length Width Height Diameter Measurement unit Gross dimensions Off-standard EQD/DIM EQD/DIM EQD/DIM EQD/DIM EQD/DIM EQD/DIM EQD/DIM 6.16 O O O O 6.16 O O O O 6.16 O O O O 6.16 O O O O 6.16 O O O O 6.16 O O O O 6.16 O O O O Number of segments UNT 6.17 M M M M Page 17 Date of release: Version 1.0

18 5 Structure of the message 5.1 Message Strcture All Segments In this chapter the whole structure of the IFTSTA message published in the UN/EDIFACT directory D.14A is presented. Pos. No. Seg. ID Name Req. Des. Max.Use Group Repeat Notes and Commens 0010 UNH Message Header M BGM Beginning of Message M DTM Date/Time/Period C TSR Transport Service Requirements C Segment Group 1: NAD-SG13 C NAD Name and Address M Segment Group 2: CTA-COM C CTA Contact Information M COM Communication Contact C Segment Group 3: RFF-DTM C RFF Reference M DTM Date/Time/Period C LOC Place/Location Identification C FTX Free Text C CNT Control Total C Segment Group 4: EQD-STS-MEA-DIM-SEL- C RFF-TPL-TMD-SG5-SG6-SG7-SG9-SG11- SG EQD Equipment Details M STS Status C MEA Measurements C DIM Dimensions C SEL Seal Number C RFF Reference C TPL Transport Placement C TMD Transport Movement Details C Segment Group 5: DGS-FTX C DGS Dangerous Goods M FTX Free Text C Segment Group 6: LOC-DTM C LOC Place/Location Identification M DTM Date/Time/Period C Segment Group 7: EQA-SEL-SG8 C EQA Attached Equipment M SEL Seal Number C Segment Group 8: LOC-DTM C LOC Place/Location Identification M DTM Date/Time/Period C 9 Page 18 Date of release: Version 1.0

19 0370 Segment Group 9: TDT-DTM-RFF-SG10 C TDT Transport Information M DTM Date/Time/Period C RFF Reference C Segment Group 10: LOC-DTM C LOC Place/Location Identification M DTM Date/Time/Period C Segment Group 11: TMP-RNG C TMP Temperature M RNG Range Details C Segment Group 12: DAM-COD C DAM Damage M COD Component details C Segment Group 13: CNI-LOC-CNT-SG14 C CNI Consignment Information M LOC Place/Location Identification C CNT Control Total C Segment Group 14: STS-RFF-DTM-DOC- FTX-SG15-LOC-PCI-SG17-SG19 M STS Status M RFF Reference C DTM Date/Time/Period C DOC Document/Message Details C FTX Free Text C Segment Group 15: NAD-SG16 C NAD Name and address M Segment Group 16: CTA-COM C CTA Contact Information M COM Communication Contact C LOC Place/Location Identification C PCI Package Identification C Segment Group 17: TDT-DTM-RFF-SG18 C TDT Transport Identification M DTM Date/Time/Period C RFF Reference C Segment Group 18: LOC-DTM C LOC Place/Location Identification M DTM Date/Time/Period C Segment Group 19: EQD-MEA-DIM-SEL- C 99 RFF-TPL-TMD-SG20-SG EQD Equipment Details M MEA Measurements C DIM Dimensions C SEL Seal Number C RFF Reference C TPL Transport Placement C TMD Transport Movement Details C Segment Group 20: LOC-DTM C 9 Page 19 Date of release: Version 1.0

20 0830 LOC Place/Location identification M DTM Date/Time/Period C Segment Group 21: EQA-SEL-SG22 C EQA Attached Equipment M SEL Seal Number C Segment Group 22: LOC-DTM C LOC Place/Location Identification M DTM Date/Time/Period C Segment Group 23: GID-HAN-SPG-DGS- C 99 FTX-GDS-LOC-QTY-SG24-SG25-SG26- SG GID Goods Item Details M HAN Handling Instructions C SGP Split Goods Placement C DGS Dangerous Goods C FTX Free Text C GDS Nature of Cargo C LOC Place/Location Identification C QTY Quantity C Segment Group 24: MEA-EQN C MEA Measurements M EQN Number of Units C Segment Group 25: DIM-EQN C DIM Dimensions M EQN Number of Units C Segment Group 26: RFF-DTM C RFF Reference M DTM Date/Time/Period C Segment Group 27: PCI-GIN C PCI Package Identification M GIN Goods Identity Number C UNT Message Trailer M 1 Page 20 Date of release: Version 1.0

21 5.2 Message Structure Used Segments In this chapter the segments of the IFTSTA message which is published in the UN/EDIFACT directory D.14A used in this message implementation guidelines are presented. Pos. Seg. Req. Group No. ID Name Des. Max.Use Repeat ness 0010 UNH Message Header M 1 R 0020 BGM Beginning of Message M 1 R 0030 DTM Date/Time/Period C 9 R 0050 Segment Group 1: NAD-SG13 C 9 R 0060 NAD Name and Address M 1 R 0500 Segment Group 13: CNI-LOC-CNT-SG14 C R 0510 CNI Consignment Information M 1 R 0540 Segment Group 14: STS-RFF-DTM-DOC- FTX-SG15-LOC-PCI-SG17-SG19 M 99 R 0550 STS Status M 1 R 0560 RFF Reference C 999 O 0570 DTM Date/Time/Period C 9 O 0600 Segment Group 15: NAD-SG16 C 9 O 0610 NAD Name and address M 1 O 0620 Segment Group 16: CTA-COM C 9 O 0630 CTA Contact Information M 1 O 0640 COM Communication Contact C 9 O 0650 LOC Place/Location Identification C 1 O 0660 PCI Package Identification C 99 O 0740 Segment Group 19: EQD-MEA-DIM-SEL- C 99 O RFF-TPL-TMD-SG20-SG EQD Equipment Details M 1 O 0760 MEA Measurements C 9 O 0770 DIM Dimensions C 9 O 1120 UNT Message Trailer M 1 R Page 21 Date of release: Version 1.0

22 5.3 Message Structure Diagram In this chapter the structure of the transportation status message according to the UN/EDIFACT IFTSTA directory D.14A is indicated. Only the segments introduced in this message implementation guideline are presented. Page 22 Date of release: Version 1.0

23 6 Definition of the message The element and segment lists used as the basis for these message implementation guidelines are defined in UN/EDIFACT directory D.14A. In this section each used segment is presented as it is described in the UN/EDIFACT IFTSTA D.14A message. The segments are presented in the order they are defined in the UN/EDIFACT IFTSTA message definition. The occurrence of the segment groups are presented in the message definition. The instructions after the element name include a specification of the obligatoriness of the element, and the type and the length of the element in according to the UN/EDIFACT directory 14A. The recommendations for the use of the element for each mode of transport can be found in the four right most columns of the table using the following notation: M O C X Mandatory information Optional information Conditional (usage dependent on the usage of another element) Not in use This notation is used to clarify the usage of the elements. The type and the length of the elements are defined as follows: types: length: examples: - a = characters - n = numbers - an = characters and/or numbers - N = standard length -..N = varying length, maximum length N - a3 = three characters - an..15 = maximum 15 characters or numbers Negative numbers are expressed with a minus sign (-) in front of the number. Use of the plus sign (+) is not required. The decimal separator and plus or minus signs are not included in the length of the element. If there is an element in a segment the values of which are codes the codes are according to the code list of the UN/EDIFACT directory D.14A or UN/ECE. The international UNTDED directory gives guidelines for the usage of decimals as follows: Weight Cubic Unit price Other prices Exchange rate Percentage Tax value Other amounts 3 decimals 4 decimals 4 decimals 3 decimals 6 decimals 4 decimals 4 decimals 3 decimals Page 23 Date of release: Version 1.0

24 These are guidelines that can be disregarded if needed. However, it is recommended that the receiver of a message can handle element values with the above mentioned decimals into their system. The decimals that are unnecessary or meaningless for the processing of the information should be left out. It is recommended that the decimal separator (a point or a comma) would be defined in the service segment UNA that is the first segment in a batch of messages exchanged in the same time. The instructions in the message definition are meant for guiding the usage of segments and elements. Page 24 Date of release: Version 1.0

25 6.1 Message Header (UNH) Segment: UNH Message Header Position: 0010 Group: Level: 0 Usage: Mandatory Max Use: 1 Purpose: A service segment starting and uniquely identifying a message. The message type code for the International multimodal status report message is IFTSTA. Note: International multimodal status report messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 IFTSTA 0052 D B 0051 UN Notes: The segment states the unique message identifier (element 0062) that can be e.g. a running number. This identifier can be used later on for to track down the actual message. The values of the elements of the composite data element S009 tell to the receiver of the message that the message and its structures are according to UN/EDIFACT IFTSTA message and the directory used is D.14A. The constant used in the element 0057 tells that the message sent or received is according to these message implementation guidelines made in the Bestfact project Simplifying Standard Message Exchange. This information is recommended to be used. Examples: UNH IFTSTA:D:14A:UN++++FI0098:1:1:ZTI' Composite data element Element Name / Usage / Codes A message with an identifier is an IFTSTA message according to the UN/EDIFACT directory D.14A compliant. The message follows recommendations of the message implementation guidelines FI0098 version 1, release 1 released by TIEKE Finnish Information Society Development Centre. UNH segment and its usage Obligatoriness: Mandatory Obligatoriness/ Repetition/ Type/Length Usage in each mode of transportation C R M A 0062 MESSAGE REFERENCE NUMBER M 1 an..14 M M M M Page 25 Date of release: Version 1.0

26 Identifier of the message S009 MESSAGE IDENTIFIER M 1 M M M M 0065 Message type M 1 an..6 M M M M IFTSTA International multimodal status report message 0052 Message version number M 1 an..3 M M M M D Draft version 0054 Message release number M 1 an..3 M M M M 14A Release 2014 A 0051 Controlling agency, coded M 1 an..3 M M M M UN UN/CEFACT 0057 Association assigned code C 1 an..6 X X X X 0110 Code list directory version number C 1 an..6 X X X X 0113 Message type sub-function identification C 1 an..6 X X X X 0068 COMMON ACCESS REFERENCE C 1 an..35 X X X X S010 STATUS OF THE TRANSFER C 1 X X X X 0070 Sequence of transfers M 1 n..2 X X X X 0073 First and last transfer C 1 a1 X X X X S016 MESSAGE SUBSET IDENTIFICATION C 1 X X X X 0115 Message subset identification M 1 an..14 X X X X 0116 Message subset version number C 1 an..3 X X X X 0118 Message subset release number C 1 an..3 X X X X 0051 Controlling agency, coded C 1 an..3 X X X X S017 MESSAGE IMPLEMENTATION GUIDELINE IDENTIFICATION 0121 Message implementation guideline identification FI Message implementation guideline version number Message implementation guideline release number 1 C 1 O O O O M 1 an..14 O O O O C 1 an..3 O O O O C 1 an..3 O O O O 0051 Controlling agency, coded C 1 an..3 O O O O ZTI TIEKE Finnish Information Society Development Centre S018 SCENARIO IDENTIFICATION C 1 X X X X 0127 Scenario identification C 1 an..14 X X X X 0128 Scenario version number C 1 an..3 X X X X 0130 Scenario release number C 1 an..3 X X X X 0051 Controlling agency, coded C 1 an..3 X X X X Page 26 Date of release: Version 1.0

27 6.2 Transportation Status Identification Information (BGM) Segment: BGM Beginning of Message Position: 0020 Group: Level: 0 Usage: Mandatory Max Use: 1 Purpose: A segment indicating the beginning of a message and identifying the consignment for which status is being reported. Notes: Examples: The segment states in the element C002/1001 that this is a transportation status message that contains the status information. The segment also tells the identifier of the transportation status in the element C106/1004. BGM Composite data element A transportation status message the identifier of which is Element Name / Usage / Codes BGM segment and its usage Obligatoriness: Mandatory Obligatoriness/ Repetition/ Type/Length Usage in each mode of transportation C R M A C002 DOCUMENT/MESSAGE NAME C 1 M M M M 1001 Document name code C an..3 M M M M Type of the message 44 Transport status report M M M M 1131 Code list identification code C an..17 X X X X 3055 Code list responsible agency code C an..3 X X X X 1000 Document name C an..35 X X X X C106 DOCUMENT/MESSAGE IDENTIFICATION C 1 M M M M 1004 Document identifier C an..70 M M M M Identifier of the transport status 1056 Version identifier C an..9 X X X X 1060 Revision identifier C an..6 X X X X 1225 MESSAGE FUNCTION CODE C 1 an..3 X X X X 4343 RESPONSE TYPE CODE C 1 an..3 X X X X 1373 DOCUMENT STATUS CODE C 1 an..3 X X X X 3453 LANGUAGE NAME CODE C 1 an..3 X X X X Page 27 Date of release: Version 1.0

28 6.3 Date of Transportation Status (DTM) Segment: DTM Date/Time/Period Position: 0030 Group: Level: 1 Usage: Conditional (Required) Max Use: 9 Purpose: A segment indicating the date of the message. Notes: Examples: The segment indicates the document creation date and time in other words the date and the time of the transportation status information in the element C507/2080 and the time format used in the element C507/2379. DTM+137: EET:303' Composite data element The time of creation of the transportation status message is the 21th of Janyary 2015 at 1:18 pm Eastern European time. Element Name / Usage / Codes DTM segment and its usage Obligatoriness: Mandatory Obligatoriness/ Repetition/ Type/Length Usage in each mode of transportation C R M A C507 DATE/TIME/PERIOD M 1 M M M M 2005 Date or time or period function code qualifier M an..3 M M M M The role of the date and the time 137 Document issue date time M M M M 2380 Date or time or period text C an..35 M M M M Creation date and time of the message 2379 Date or time or period format code C an..3 M M M M Format of the date and time expression 102 CCYYMMDD O O O O 203 CCYYMMDDHHMM O O O O 303 CCYYMMDDHHMMZZZ O O O O ZZZ = Time zone Page 28 Date of release: Version 1.0

29 6.4 Party Information (NAD) Segment: NAD Name and address Position: 0060 (Trigger Segment) Group: Segment Group 1 (Name and Address) Mandatory, Max Use 9 Level: 1 Usage: Mandatory Max Use: 1 Purpose: A segment identifying a party to the consignment such as shipper or consignee. Notes: The segment states the parties involved by an identification code (company or place of business) in the element C082/3039 or in a structured form in the composite data elements C080, C059 and C819 and in the elements 3164, 3251 and The usage of an identification code is recommended. In regular contacts only the party identification number should be used and the name of the party and the address related information can be omitted. The role of the party can be indicated in the element The processing of the free text can be difficult for the message receiver so the usage of the composite data element C058 is not recommended. Remarks: Each message should always contain two NAD segments indicating the originator and the receiver of the message. In different countries and business branches there could be recommendations to use certain kind of the party identifiers. Examples: NAD+MS :100:5++TRANS-COMPANY LTD The sender of the transportation status message is Trans-Company Ltd, party identification number of which is NAD segment and its usage Obligatoriness: Mandatory Composite data element Element Name / Usage / Codes Obligatoriness/ Repetition/ Type/Length Usage in each mode of transportation C R M A 3035 PARTY FUNCTION CODE QUALIFIER M 1 an..3 M M M M Role of the party MR Message recipient M M M M MS Document/message issuer/sender M M M M C082 PARTY IDENTIFICATION DETAILS C 1 O O O O Page 29 Date of release: Version 1.0

30 3039 Party identifier M an..35 M M M M The identifier of the party used in the electronic interchange 1131 Code list identification code C an..17 M M M M Type of the code list Codes according to the code lists of UN/EDIFACT D.03A 100 Enhanced party identification O O O O 3055 Code list responsible agency code C an..3 O O O O The administrator of the code list 5 ISO (International Organization for O O O O Standardization) 9 GS1 86 Assigned by party originating the message O O O O C058 NAME AND ADDRESS C 1 X X X X 3124 Name and address description M an..35 X X X X 3124 Name and address description C an..35 X X X X 3124 Name and address description C an..35 X X X X 3124 Name and address description C an..35 X X X X 3124 Name and address description C an..35 X X X X C080 PARTY NAME C 1 O O O O 3036 Party name M an..70 M M M M Name of the organization 3036 Party name C an..70 O O O O Name of the unit of the organization 3036 Party name C an..70 X X X X 3036 Party name C an..70 X X X X 3036 Party name C an..70 X X X X 3045 Party name format code C an..3 X X X X C059 STREET C 1 X X X X 3042 Street and number or post office box identifier M an..35 X X X X 3042 Street and number or post office box identifier C an..35 X X X X 3042 Street and number or post office box identifier C an..35 X X X X 3042 Street and number or post office box identifier C an..35 X X X X 3164 CITY NAME C 1 an..35 X X X X C819 COUNTRY SUBDIVISION DETAILS C 1 X X X X 3229 Country subdivision identifier C an..9 X X X X 1131 Code list identification code C an..17 X X X X 3055 Code list responsible agency code C an..3 X X X X 3228 Country subdivision name C an..70 X X X X 3251 POSTAL IDENTIFICATION CODE C 1 an..17 X X X X 3207 COUNTRY IDENTIFIER C 1 an..3 X X X X Page 30 Date of release: Version 1.0

31 6.5 Consignment Information (CNI) Segment: CNI Consignment information Position: 0510 (Trigger Segment) Group: Segment Group 13 (Consignment information) Conditional (Optional), Max Use Level: 1 Usage: Mandatory Max Use: 1 Purpose: A segment to identify a consignment for which status details are given. Notes: Remarks: The segment states the identifier of the waybill document related to the actual transportation status. The row number of the transportation status is stated in the element If the same message is used for reporting the status of several consignments, each of them has to be given on their own rows. If the consignment identifier assigned by carrier is used in the element C503/1004 and the receiver does not have it in their information system, a reference number of the waybill or another reference should also be stated in the RFF segment of the segment group 14. There could be national recommendations of the form and the length of waybill number. Ask for the form of the waybill number from the authority dividing waybill numbers in the country. Examples: CNI Composite data element Element Name / Usage / Codes The consignment identifier assigned by the carrier is and it is the first consignment of the transportation status message. CNI segment and its usage Obligatoriness: Mandatory Obligatoriness/ Repetition/ Type/Length Usage in each mode of transportation C R M A 1490 CONSOLIDATION ITEM NUMBER C 1 n..5 M M M M The running row number of the transportation staus message C503 DOCUMENT/MESSAGE DETAILS C 1 M M M M 1004 Document identifier C an..70 M M M M The identifier of the waybill or other Page 31 Date of release: Version 1.0

32 transport document 1373 Document status code C an..3 X X X X 1366 Document source description C an..70 X X X X 3453 Language name code C an..3 X X X X 1056 Version identifier C an..9 X X X X 1060 Revision identifier C an..6 X X X X 1312 CONSIGNMENT LOAD SEQUENCE IDENTIFIER C 1 an..4 X X X X Page 32 Date of release: Version 1.0

33 6.6 Consignment Status (CNI/STS) Segment: STS Status Position: 0550 (Trigger Segment) Group: Segment Group 14 (Status) Mandatory, Max Use 99 Level: 2 Usage: Mandatory Max Use: 1 Purpose: A segment specifying the status relating to a consignment (e.g. loaded). Notes: This segment states the event and reason of the transportation status. An assumption is made that this message is only used for reporting of the transportation status, therefore the status type should always be 1 (Transportation). The event of the transportation is given in a coded form in the element C555/4405 and in textual form in the element C555/4404. The reason code for the event is stated in coded form in the element C556/9013 and in textual form in the element C556/9012. It is recommended to use the coded forms for the events and reasons. Additional information for the event and the reason codes can be given in the elements C555/4404 and C556/9012. Maximum five reason codes can be given (C555) for one event in the repetitions of the composite data element C556. When the consignment has been delivered to the consignee (the element C555/4405 has the value 22 (Delivery, completed as per instruction)), the name of the consignee of the consignment can be stated in the NAD segment group 15. If the consignment is reloaded (the element C555/4405 has the value 79 (Reloaded onto a means of transport)), the original transportation unit or the current transportation unit information can be given in the EQD segment group 19. Examples: STS The consignment is delayed due to bad weather conditions. STS+1+31 The consignment is en route and is on schedule. STS Packages are damaged. Page 33 Date of release: Version 1.0

34 STS segment and its usage Obligatoriness: Mandatory Composite data element Element Name / Usage / Codes Obligatoriness/ Repetition/ Type/Length Usage in each mode of transportation C R M A C601 STATUS CATEGORY C 1 M M M M 9015 Status category code M an..3 M M M M Type of status 1 Transport 1131 Code list identification code C an..17 X X X X 3055 Code list responsible agency code C an..3 X X X X C555 STATUS C 1 M M M M 4405 Status description code M an..3 M M M M Despription of the status in coded form UN/ECE Recommendation no. 24 (TRADE AND TRANSPORT STATUS CODES Revision 5) codes 1 Arrival, completed O O O O 13 Collection/pick-up, completed O O O O 18 Damaged in the course of O O O O transportation 20 Delayed, in the course of O O O O transportation 21 Delivery, completed O O O O 24 Departure, completed O O O O 31 En route O O O O 41 Handed over under continued O O O O responsibility 48 Loading, completed onto a means of O O O O transport 53 Collection/pick-up, not completed O O O O 117 Missing O O O O 323 Return in progress O O O O 349 Handed over O O O O NOTE: The entire UN/ECE Recommendation 24 (TRADE AND TRANSPORT STATUS CODES Revision 4) is as the Appendix Code list identification code C an..17 O O O O 3055 Code list responsible agency code C an..3 O O O O The administrator of the code list 6 UN/ECE (United Nations - Economic Commission for Europe) O O O 4404 Status description C an..35 O O O O Despription of the status in textual form or additional information for the status code C556 STATUS REASON C 1 M M M M 9013 Status reason description code M an..3 M M M M Reason of the status code in coded form 14 Damaged O O O O 27 Goods units missing O O O O O Page 34 Date of release: Version 1.0

35 33 Lost goods/consignments/equipment O O O O 34 Means of transport damaged O O O O 40 Not identified O O O O 60 Unacceptable condition O O O O 63 Weather conditions O O O O 108 Goods not barcoded O O O O NOTE: The entire UN/EDIFACT 9013 code list is presented in the Appendix Code list identification code C an..17 X X X X 3055 Code list responsible agency code C an..3 O O O O The administrator of the code list 6 UN/ECE (United Nations - Economic Commission for Europe) O O O O 9012 Status reason description C an..256 O O O O Reason of the status code in textual form C556 STATUS REASON C 1 O O O O 9013 Status reason description code M an..3 O O O O Reason of the status code in coded form; See codes in the first repetition of the composite data element C Code list identification code C an..17 X X X X 3055 Code list responsible agency code C an..3 O O O O The administrator of the code list; See codes in the first repetition of the composite data element C Status reason description C an..256 O O O O Reason of the status code in textual form C556 STATUS REASON C 1 O O O O 9013 Status reason description code M an..3 O O O O Reason of the status code in coded form; See codes in the first repetition of the composite data element C Code list identification code C an..17 X X X X 3055 Code list responsible agency code C an..3 O O O O The administrator of the code list; See codes in the first repetition of the composite data element C Status reason description C an..256 O O O O Reason of the status code in textual form C556 STATUS REASON C 1 O O O O 9013 Status reason description code M an..3 O O O O Reason of the status code in coded form; See codes in the first repetition of the composite data element C Code list identification code C an..17 X X X X 3055 Code list responsible agency code C an..3 O O O O The administrator of the code list; See codes in the first repetition of the composite data element C Status reason description C an..256 O O O O Reason of the status code in textual form Page 35 Date of release: Version 1.0

36 C556 STATUS REASON C 1 O O O O 9013 Status reason description code M an..3 O O O O Reason of the status code in coded form; See codes in the first repetition of the composite data element C Code list identification code C an..17 X X X X 3055 Code list responsible agency code C an..3 O O O O The administrator of the code list; See codes in the first repetition of the composite data element C Status reason description C an..256 O O O O Reason of the status code in textual form Page 36 Date of release: Version 1.0

37 6.7 Consignment References (RFF) Segment: RFF Reference Position: 0560 Group: Segment Group 14 (Status) Mandatory, Max Use 99 Level: 3 Usage: Conditional Max Use: 999 Purpose: A segment identifying a reference relating to the status (e.g. House Bill of Lading number). Notes: Remark: Examples: The segment states the transportation status relating references such as the transportation order identifier in the element C506/1154. The type of the reference is stated in the element C506/1153. This segment states the consignment identifier assigned by the receiver of transportation status message in the element C506/1154 if the element C503/1004 of the CNI segment states the consignment identifier assigned by the carrier (that the receiver does not have in their information system). RFF+AAM: Composite data element The waybill number is Element Name / Usage / Codes RFF segment and its usage Obligatoriness: Optional Obligatoriness/ Repetition/ Type/Length Usage in each mode of transportation C R M A C506 REFERENCE M 1 M M M M 1153 Reference code qualifier M an..3 M M M M Type of the reference AAM Waybill number O O O O AAO Consignment identifier, consignee O O O O assigned BN Consignment identifier, carrier O O O O assigned CU Consignment identifier, consignor assigned O O O O 1154 Reference identifier C an..70 M M M M Identifier of the reference 1156 Document line identifier C an..6 X X X X 1056 Version identifier C an..9 O O O O 1060 Revision identifier C an..6 X X X X Page 37 Date of release: Version 1.0

38 6.8 Transportation Event Date and Time Information(DTM) Segment: DTM Date/Time/Period Position: 0570 Group: Segment Group 14 (Status) Mandatory, Max Use 99 Level: 3 Usage: Conditional Max Use: 9 Purpose: A segment indicating the date and time of the status or event. Notes: Examples: The segment states the transportation event relating date and time information in the element C507/2080 and the format of the date and time information in the element C507/2379. DTM+78: EET:303' Composite data element The date and the time of the event is the 21th of January 2015, 11:52 am Eastern European time. Element Name / Usage / Codes DTM segment and its usage Obligatoriness: Optional Obligatoriness/ Repetition/ Type/Length Usage in each mode of transportation C R M A C507 DATE/TIME/PERIOD M 1 M M M M 2005 Date or time or period function code qualifier M an..3 M M M M Role of the date and time expression 78 Event date/time/period, actual M M M M 2380 Date or time or period text C an..35 M M M M Date and time of the event 2379 Date or time or period format code C an..3 M M M M Format of the date and time expression 102 CCYYMMDD O O O O 203 CCYYMMDDHHMM O O O O 303 CCYYMMDDHHMMZZZ O O O O ZZZ = time zone O O O O 718 CCYYMMDDCCYYMMDD O O O O 719 CCYYMMDDHHMMCCYYMMDDHHMM O O O O Page 38 Date of release: Version 1.0

39 6.9 Transportation Event Acknowledging Party Information (NAD) Segment: NAD Name and address Position: 0610 (Trigger Segment) Group: Segment Group 15 (Name and Address) Conditional, Max Use 9 Level: 3 Usage: Mandatory Max Use: 1 Purpose: A segment specifying the name and/or address associated with the event such as notify party, terminal address, trucking company for gate move. Notes: The segment states the transportation event relating acknowledging party. The company can be stated by the party identification number in the element C082/3039 or by name in the element C080/3036. Either one these have to be given for the acknowledging party if this NAD segment is used. The address information should not be given in this segment. For regular customers only the usage of the party identification number is recommended. The role of the party is stated in the element 3035 that has always the value TF (Source of information). The processing of free text can be difficult for the receiver so the usage of free text should be avoided. There for the usage of the composite data element C058 is not recommended. Remarks: Examples: In different countries and business branches there could be recommendations to use certain kind of the party identifiers. NAD+AP :100:5 The identification number of the acknowledging company is NAD segment and its usage Obligatoriness: Optional Composite data element Element Name / Usage / Codes Obligatoriness/ Repetition/ Type/Length Usage in each mode of transportation C R M A 3035 PARTY FUNCTION CODE QUALIFIER M 1 an..3 M M M M Role of the party TF Source of information M M M M C082 PARTY IDENTIFICATION DETAILS C 1 O O O O 3039 Party identifier M an..35 M M M M Page 39 Date of release: Version 1.0

40 The identifier of the party used in the electronic interchange 1131 Code list identification code C an..17 M M M M Type of the code list Codes according to the code lists of UN/EDIFACT D.03A 52 Value added tax identification O O O O 58 Business account number O O O O 100 Enhanced party identification O O O O 3055 Code list responsible agency code C an..3 O O O O The administrator of the code list 5 ISO (International Organization for O O O O Standardization) 86 Assigned by party originating the message O O O O C058 NAME AND ADDRESS C 1 X X X X 3124 Name and address description M an..35 X X X X 3124 Name and address description C an..35 X X X X 3124 Name and address description C an..35 X X X X 3124 Name and address description C an..35 X X X X 3124 Name and address description C an..35 X X X X C080 PARTY NAME C 1 O O O O 3036 Party name M an..70 O O O O Name of the organization 3036 Party name C an..70 O O O O Name of the unit of the organization 3036 Party name C an..70 X X X X 3036 Party name C an..70 X X X X 3036 Party name C an..70 X X X X 3045 Party name format code C an..3 X X X X C059 STREET C 1 X X X X 3042 Street and number or post office box identifier M an..35 X X X X 3042 Street and number or post office box identifier C an..35 X X X X 3042 Street and number or post office box identifier C an..35 X X X X 3042 Street and number or post office box identifier C an..35 X X X X 3164 CITY NAME C 1 an..35 X X X X C819 COUNTRY SUBDIVISION DETAILS C 1 X X X X 3229 Country subdivision identifier C an..9 X X X X 1131 Code list identification code C an..17 X X X X 3055 Code list responsible agency code C an..3 X X X X 3228 Country subdivision name C an..70 X X X X 3251 POSTAL IDENTIFICATION CODE C 1 an..17 X X X X 3207 COUNTRY IDENTIFIER C 1 an..3 X X X X Page 40 Date of release: Version 1.0

41 6.10 Contact Information (NAD /CTA) Segment: CTA Contact information Position: 0630 (Trigger Segment) Group: Segment Group 16 (Contact Information) Conditional (Optional), Max Use 9 Level: 2 Usage: Mandatory Max Use: 1 Purpose: A segment to identify a person or department. Notes: Remarks: Examples: The segment states a contact person or a department in charge relating to the party. The name of the person or the department can be stated in the element C056/3412. If there is an identifier code for the department it can be stated in the element C056/3413. The role of the person or the department can be stated in the element The qualifier IC of the element 3139 is recommended because it is difficult for many software systems to handle the role of the contact person or the division. In many countries it is prohibited to send the personal identifier of a person in the message. CTA+IC+:JOHN SMITH' The acknowledging person is John Smith. CTA segment and its usage Obligatoriness: Optional Composite data element Element Name / Usage / Codes Obligatoriness/ Repetition/ Type/Length Usage in each mode of transportation C R M A 3139 CONTACT FUNCTION CODE C 1 an..3 O O O O Role of the contact person or the department IC Information contact O O O O C056 CONTACT DETAILS C 1 O O O O 3413 Contact identifier C an..17 O O O O Identifier of the acknowledging department 3412 Contact name C an..256 O O O O Name of the acknowledging person or the department Page 41 Date of release: Version 1.0