VERMAS VERIFICATION OF MASS

Transcription

1 The SOLAS Container Weight Verification Requirement VERMAS VERIFICATION OF MASS GUIDELINE FOR THE XML VERMAS MESSAGE Version 1.3 Message: VERMAS Version: 1.3 Date: June 2016 Source: Portic 1

2 0 TABLE OF CONTENTS 0 TABLE OF CONTENTS 1 1 CHANGE CONTROL 2 2 GENERAL INTRODUCTION 4 3 MESSAGE STRUCTURE 6 Structure 6 XML declaration 7 Element description 7 4 USE CASES 27 5 INFORMATION USAGE IN EACH USE CASE 29 6 SCHEMA 30 1

3 1 CHANGE CONTROL Version Date Changes 1.3 June 2016 Version 1.3 (June 2016) Due to some changes in the national legislation (15 th June 2016) the following changes have been applied in the use case 8 (VGM communication between carrier and terminal): Verification date in element trcd_date.time.period (Group 5) changes from required to optional. Method used for weighing the container in element trsd_document.message.details (Group 7) changes from required to optional. 1.2 June 2016 Version 1.2 (June 2016) introduces the following changes: This message implementation guide is based on EDIFACT VERMAS message from D16A. Code 749 is used in tred_document.message.name.coded element, instead of code XXX that was used before the publication of EDIFACT Directory D16A. All the examples that used code XXX have been changed to the new code 749. Due to some changes in the national legislation, now the references to the weighing equipment are not mandatory and, in order to maintain the compatibility with the applications developed, the transmission of the weighing equipment identification is optional now. In a weighing order message ( 127 in tred_document.message.name.coded element), always have to be sent the container identification or a container reference number. And, in a VGM notification message ( 749 in tred_document.message.name.coded element) the container identification is always required, being optional its container reference number. The data element tred_document.identifier in element trsd_document.message.details (group 7) changes from required to optional. Use cases sections have been added. 1.1 May 2016 Version 1.1 (May 2016) introduces the following changes: This message implementation guide is based on VERMAS MIG v.0.5 from SMDG. According to v0.5 of the SMDG VERMAS MIG, the Submitter of the message (code TB ) has been included in element trsd_name.and.address.g2 (group 2). It has also been included carrier details in element trsd_name.and.address.g2 (group 2) (code CA ). According to the minimum information that is required in the national legislation in the documents from shipper to carrier, it has been included: tred_postal.identification.code and tred_country.coded of element trsd_name.and.address.g2 (group 2) to inform about the addresses of the submitter and the shipping agent. element trcd_reference in group 4 with qualifier AGP ) element trsd_document.message.details (group 7) indicating that, if the method used to obtain the verified gross mass (method 1 or 2) is included in that segment, it is equivalent to declaring that the equipment meets the requirements specified in national legislation for those weighing equipment. And if method 2 is indicated, it is stating that the requirements of national law are met in order to use that method. 2

4 Previous version includes some segments that are unnecessary in our Port, or segments with information duplicated in other segments, so: use of element trcd_reference in group 1 (because the same information is in element trcd_reference of group 4); element trcd_reference (group 4); element trcd_date.time.period (group 7) has been removed, because part of this information was also in element trcd_date.time.period (at header level) and part at the trcd_date.time.period element in group 5; element trsd_document.message.details (group 7); element trsd_name.and.address.g8 (group 8); element trsd_name.and.address.g8 (group 8) and element trsd_name.and.address.g8 (group 8) have been removed the following data elements and codes: o tred_country.subdivision.identifier and tred_country.subdivision.name Country subdivision details o tred_party.name2, tred_party.name3, tred_party.name4, tred_party.name5 o tred_street.and.number.p.o.box2, tred_street.and.number.p.o.box3, tred_street.and.number.p.o.box4 o In data element tred_code.list.qualifier code INTTRA has been removed o In data element tred_code.list.responsible.agency.coded code GS1 has been removed 1.0 February 2016 Version 1.0 was the first version Please, refer to the VERMAS EDIFACT guide in order to see the use case example messages. This guide has been created from the Fòrum Telemàtic EDIFACT guide. In the case of any discrepancies, please refer to the EDIFACT guide. 3

5 2 GENERAL INTRODUCTION This MIG is based on the MIG developed by the SMDG. SCOPE The Verified Gross Mass message may be used for both national and international applications. The VERMAS message is typically exchanged between a shipper of goods for ocean transport, a forwarder, a non-vessel operating common carrier, an operator of a container weighing facility, a container terminal operator / stevedore, a vessel operator, a shipping line, the vessel's master, a container operator, a slot charterer. It is based on universal practice related to monitoring the logistics transport chain and is not dependent on the type of business or industry. FUNCTIONAL DEFINITION In relation to a supply chain including the transport of a packed container on an ocean vessel, the Verified Gross Mass message (VERMAS) permits to submit the Verified Gross Mass of the packed container and supporting information as legally required by the SOLAS Convention Chapter VI, Part A, Regulation 2. VERMAS can be different parties at different times in the process chain. It is not dedicated to a particular process step in the transport chain. VERMAS shall only be used for transmission of the SOLAS Verified Gross Mass and directly related information. FIELD OF APPLICATION The Verified Gross Mass message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry. PRINCIPLES VERMAS incorporates information on the Verified Gross Mass (VGM) of a packed container, the time, place and method of obtaining the VGM, the responsible parties, and references required by the receiver to assign the VGM to his transactions. The message is used to transmit information related to one or many containers belonging to a clearly defined transport from a shipper to a consignee. The message can be exchanged between any two parties in the maritime transport chain as per mutual agreement. The sender may have obtained the Verified Gross 4

6 Mass himself or he may forward a VGM received from a 3rd party. Each party in the transport chain can be a sender or a receiver of a VERMAS message. The only mandatory information in the message is on the container and on the VGM. All other information is optional and transmission depends on the role of sender and receiver in the transport chain. It is essential that sender and receiver agree on the information and references to be transmitted. The VERMAS is a small message for a clearly dedicated purpose. It shall only be used for transmission of the VGM as required by SOLAS and directly related information. It shall not be used as a handling order. The message will not be used for reporting of empty containers. The SOLAS Convention was ratified by and therefore applies to literally all sea going states worldwide. But at the time of developing the VERMAS message not all states have published their national legislation. Future legislations may result in additional reporting requirements that may lead to an enhanced message scope. Dependent on nature of cargo further attributes such as temperature control, identification of dangerous goods, non-standard dimensions, handling requirements may be added. PARTICULARITIES OF THE MIG FOR THE PORT OF BARCELONA DE8169 of segment EQD will not be used in the MIG for the Port of Barcelona because all containers have to be full (empty containers are out of the scope of this procedure). Segment LOC from Group 4 will not be used in the MIG for the Port of Barcelona. The information related to the locations related to container s transport chain will be transmitted using other container messages (i.e. acceptance orders or loading lists). Only the code VGM (Verified gross mass - transport equipment verified gross weight) will be accepted in DE6313 of segment MEA because the VERMAS will be sent only when the VGM has to be communicated between two parties. In order to link the VERMAS message with the other documentary transactions associated to a loading operation on a vessel, the booking number and the shipping agent always have to be declared. The association among several messages that are related to the same communication of the VGM information between two parties will be based in the use of the same reference in all the messages. For that purpose, the Sender's reference to the original message (code AGO ) declared in segment RFF from group 1 will be the same in all the messages used for the same communication of the VGM of a container (the original message, modifications and even the cancellation). 5

7 3 MESSAGE STRUCTURE Structure In this section you can see a high level detailed of the message, where you can see the segments, segment groups and, for each element if it is mandatory or not, and, an element can have repetitions, the minimum and maximum number of repetitions. Mandatory elements are marked with a continuous line. Non mandatory elements are marked with a dashed line. 6

8 XML declaration All VERMAS messages must have the same XML declaration. When the VERMAS message is used as a weighing order (element tred_document.message.name.coded with value 127 ) the XML declaration will be: <?xml version="1.0" encoding="iso "?> <!DOCTYPE VERMASSOL SYSTEM "VERMAS.dtd"> When the VERMAS message is used as a weigh communication (element tred_document.message.name.coded with value 749 ) the XML declaration will be: <?xml version="1.0" encoding="iso "?> <!DOCTYPE VERMASCOM SYSTEM "VERMAS.dtd"> Element description VERMAS VERMAS.HEADER VERMAS.GROUP1 VERMAS.GROUP2 VERMAS.GROUP4 VERMAS.GROUP5 VERMAS.GROUP7 VERMAS.GROUP8 VERMAS.GROUP9 anxs_interchange.header anxs_message.header trcd_date.time.period trcd_reference tred_city.name tred_code.list.qualifier tred_code.list.responsible.agency.coded tred_communication.address.identifier tred_communication.means.type.code tred_contact.function.coded tred_contact.identifier tred_contact.name tred_country.coded tred_country.subdivision.identifier tred_country.subdivision.name tred_date.time.period tred_date.time.period.format.qualifier tred_date.time.period.qualifier tred_document.identifier tred_document.message.name.coded tred_document.message.number tred_document.name tred_document.name.code tred_equipment.identification.number tred_equipment.qualifier tred_equipment.size.and.type.identification tred_measurement.attribute.coded tred_measurement.purpose.code.qualifier tred_measurement.unit.code tred_measurement.value tred_message.function.coded tred_party.id.identification tred_party.name1 tred_party.name2 tred_party.name3 tred_party.name4 tred_party.name5 7

9 tred_party.qualifier tred_postal.identification.code tred_reference.number tred_reference.qualifier tred_seal.issuer tred_seal.number tred_street.and.number.p.o.box1 tred_street.and.number.p.o.box2 tred_street.and.number.p.o.box3 tred_street.and.number.p.o.box4 trsd_beginning.of.message trsd_communication.contact trsd_contact.information trsd_document.message.details trsd_equipment.details trsd_measurements trsd_name.and.address.g2 trsd_name.and.address.g8 trsd_seal.number element anxe_association.assigned.code element anxs_message.header enumeration SMDG10 element anxe_controlling.agency element anxs_message.header enumeration UN element anxe_message.reference.number element anxs_message.header minlength 1 maxlength 14 8

10 element anxe_message.type element anxs_message.header enumeration VERMAS element anxe_message.type.release.number element anxs_message.header enumeration 16A element anxe_message.version.number element anxs_message.header enumeration D element anxe_recipient.identification element anxs_interchange.header minlength 1 maxlength 35 Receiver of the message composed by country code + CIF code. For example ESA element anxe_sender.identification Código de país + NIF de la empresa que emite el mensaje. Por ejemplo ESA element anxs_interchange.header minlength 1 maxlength 35 Sender of the message composed by country code + CIF code. For example ESA

11 element anxs_interchange.header children anxe_sender.identification anxe_recipient.identification element VERMAS.HEADER edifact UNB segment element anxs_message.header children anxe_message.reference.number anxe_message.type anxe_message.version.number anxe_message.type.release.number anxe_controlling.agency anxe_association.assigned.code element VERMAS.HEADER edifact UNH segment element trcd_date.time.period children tred_date.time.period.qualifier tred_date.time.period tred_date.time.period.format.qualifier elements VERMAS.GROUP5 VERMAS.HEADER edifact DTM segment Date and/or time, or period relevant to the specified date/time/period type. It is recommended to transmit date and time as UTC. element trcd_reference children tred_reference.qualifier tred_reference.number 10

12 elements VERMAS.GROUP1 VERMAS.GROUP4 edifact RFF segment element tred_city.name Type restriction of xs:string element trsd_name.and.address.g8 Restrictions maxlength 35 Name of a city. element tred_code.list.qualifier element trsd_name.and.address.g8 enumeration EORI enumeration TAX Code identifying a user or association maintained code list. Usage of this data element is required if C is transmitted as ZZZ. EORI: EORI number TAX: TAX ID element tred_code.list.responsible.agency.coded element trsd_name.and.address.g8 enumeration ZZZ Code specifying the agency responsible for a code list. ZZZ: Mutually defined element tred_communication.address.identifier element trsd_communication.contact minlength 1 maxlength 512 To identify a communication address. element tred_communication.means.type.code 11

13 element trsd_communication.contact enumeration EM enumeration FX enumeration MA enumeration TE Code specifying the type of communication address. EM Electronic mail FX Telefax MA Mail TE Telephone element tred_contact.function.coded element trsd_contact.information enumeration BN enumeration RP Code specifying the function of a contact (e.g. department or person). BN Certification contact RP (Authorized) responsible person element tred_contact.identifier element trsd_contact.information maxlength 17 To identify a contact, such as a department or employee. element tred_contact.name element trsd_contact.information minlength 1 maxlength 35 Name of a contact, such as a department or employee. In case 3139=RP this data element is interpreted as signature (name of responsible person in capital letters). element tred_country.coded element trsd_name.and.address.g8 maxlength 3 Identification of the name of the country or other geographical entity as defined in ISO and UN/ECE Recommendation 3. In some business cases specification of the country in which ascertainment of weight has taken place is required. 12

14 element tred_country.subdivision.identifier element trsd_name.and.address.g8 maxlength 9 element tred_country.subdivision.name element trsd_name.and.address.g8 maxlength 70 element tred_date.time.period element trcd_date.time.period minlength 1 maxlength 35 The value of a date, a date/time, a time or of a period in a specified representation element tred_date.time.period.format.qualifier element trcd_date.time.period enumeration CCYYMMDDHMM element tred_date.time.period.qualifier element trcd_date.time.period enumeration 137 enumeration

15 Header Group Document issue date time 798 Weight ascertained - Date/Time when gross mass was obtained element tred_document.identifier element trsd_document.message.details minlength 1 maxlength 70 To identify a document. Unique identification of documentation: - in case SHP, SM1, SM2 define ID for reference. element tred_document.message.name.coded element trsd_beginning.of.message enumeration 749 enumeration Documentation about Solas Verified Gross Mass 127 Transport equipment special service instruction. To be used when the receiving party has to weight the container element tred_document.message.number element trsd_beginning.of.message minlength 1 maxlength 70 Sender's Unique Internal Reference Number element tred_document.name Name of a document. element trsd_document.message.details minlength 1 maxlength 35 element tred_document.name.code 14

16 element trsd_document.message.details enumeration SHP enumeration SM1 enumeration SM2 Code specifying the document name. SHP - Responsibility to obtain verified gross mass ("shipper") SM1 - Certificate for ascertainment of VGM according to method 1 SM2 - Certificate for ascertainment of VGM according to method 2 SHP - NAD group specifies party and responsible person SM1 - NAD group specifies party and optionally further details SM2 - NAD group specifies party and optionally further details SHP Party responsible for verification of gross mass SM1 SOLAS verification method 1 SM2 SOLAS verification method 2 One container can have only one method. It is not possible that the same container has used both method 1 and method 2. element tred_equipment.identification.number element trsd_equipment.details maxlength 17 Equipment Number Container numbers must include both prefix and number, expressed as a contiguous string without spaces or hyphens. In a weighing order message ( 127 in element tred_document.message.name.coded), always have to be sent the container identification or a container reference number (trcd_reference element, group 4, with SQ in tred_reference.qualifier). In a VGM notification message ( 749 in element tred_document.message.name.coded) the container identification is always required, being optional its container reference number. element tred_equipment.qualifier element trsd_equipment.details enumeration CN CN: Container element tred_equipment.size.and.type.identification element trsd_equipment.details maxlength 10 Equipment Size and type. 15

17 Container size and type according to ISO6346 codes. element tred_measurement.attribute.coded element trsd_measurements enumeration VGM VGM Verified gross mass - transport equipment verified gross weight element tred_measurement.purpose.code.qualifier element trsd_measurements enumeration AAE element tred_measurement.unit.code element trsd_measurements enumeration KGM KGM: Kilogram element tred_measurement.value element trsd_measurements minlength 1 maxlength 18 To specify the value of a measurement. When the VERMAS message is used as a weighing order (element tred_document.message.name.coded with value 127 ) it has to be declared a weight of 0 Kg. element tred_message.function.coded element trsd_beginning.of.message enumeration 1 enumeration 5 enumeration 9 1 Cancellation 5 Replace 16

18 9 Original (new message) element tred_party.id.identification elements trsd_name.and.address.g2 trsd_name.and.address.g8 minlength 1 maxlength 35 Party identification For shipping agent use the company NIF; for carriers use the SCAC codes and, for submitters and the rest of agents, the company NIF or the Portic ID can be used) element tred_party.name1 elements trsd_name.and.address.g2 trsd_name.and.address.g8 minlength 1 maxlength 70 Identification of a transaction party by name, one line. element tred_party.name2 element trsd_name.and.address.g8 minlength 1 maxlength 35 element tred_party.name3 element trsd_name.and.address.g8 minlength 1 maxlength 35 element tred_party.name4 element trsd_name.and.address.g8 minlength 1 maxlength 35 17

19 element tred_party.name5 element trsd_name.and.address.g8 minlength 1 maxlength 35 element tred_party.qualifier Group 2 elements trsd_name.and.address.g2 trsd_name.and.address.g8 enumeration CF enumeration CA enumeration TB enumeration AM enumeration SPC enumeration WPA The identification of the shipping agent and the submitter is required and the carrier s identification is optional. CF Container operator/lessee (use this code for the shipping agent) (Mandatory) CA Carrier (Optional) TB Submitter (Mandatory) Group 8 Group for specification of a) party responsible of SOLAS verified gross mass declaration (SOLAS' shipper) b) the person authorized to sign VGM documents c) the weighing party for the method specified in DOC segment Each party's responsible person might be specified by CTA group Name/address data transmitted in this segment depend on function code SPC - data about company responsible to verify gross mass according to SOLAS regulations WPA - data about company which actually has determined VGM AM - data about person (individual) authorized to sign a document Communication details for the specified company/person can be transmitted in the subsequent CTA group. In context of VGM documentation specification of a party by code is doubtful because the receiving party might not be aware of the used code list. element tred_postal.identification.code element trsd_name.and.address.g8 maxlength 17 18

20 Code specifying the postal zone or address. element tred_reference.number element trcd_reference minlength 1 maxlength 70 element tred_reference.qualifier Group 1 element trcd_reference enumeration AAS enumeration ABE enumeration ACW enumeration AGO enumeration SI enumeration AGP enumeration BN enumeration SQ enumeration VOR To specify references applicable to the whole message, such as the previous message reference. One occurrence of this segment is required: reference included in DE1004 as a Sender's Unique Internal Reference Number. Also, a reference to a previous message will be necessary when the function of the message is other than original. Group 4 AAS Transport contract document identifier (Optional) ABE Declarant's reference number (Optional) ACW Reference number to previous message (Dependant: Optional only for Original New Message. Mandatory for Replacement or Cancellation) AGO Sender's reference to the original message (the same reference for the same communication of a VGM) (Mandatory) To specify references related to the container. This reference is intended to relate the transmitted VGM data to message recipient's internal business transactions. The booking number always must be sent. The weighing equipment identification is not required, but it is maintained as optional in this version in order to preserve the compatibility with version 1.1. AGP Company issued equipment ID (Owner/operator, non-government issued equipment reference number). Weighing equipment ID. (Optional) BN Consignment identifier, carrier assigned (i.e.booking number) (Mandatory) SI SID (Shipper's identifying number for shipment) (Optional) SQ Equipment sequence number (reference assigned to the container before the container number was known) (Optional) VOR Transport equipment gross mass verification order reference. Reference number identifying the order for obtaining a Verified Gross Mass (weight) of a packed transport equipment as per SOLAS Chapter VI, Regulation 2, paragraphs 4-6.(Optional) element tred_seal.issuer element trsd_seal.number 19

21 enumeration AA enumeration AB enumeration SH Code specifying the name of the sealing party. AA Consolidator AB Unknown SH Shipper element tred_seal.number element trsd_seal.number minlength 1 maxlength 35 The identification number of a seal affixed to a transport unit. element tred_street.and.number.p.o.box1 element trsd_name.and.address.g8 maxlength 35 Street address and/or PO Box number in a structured address: one line. element tred_street.and.number.p.o.box2 element trsd_name.and.address.g8 maxlength 35 element tred_street.and.number.p.o.box3 element trsd_name.and.address.g8 maxlength 35 element tred_street.and.number.p.o.box4 element trsd_name.and.address.g8 20

22 maxlength 35 element trsd_beginning.of.message children tred_document.message.name.coded tred_document.message.number tred_message.function.coded element VERMAS.HEADER edifact BGM segment element trsd_communication.contact children tred_communication.address.identifier tred_communication.means.type.code element VERMAS.GROUP9 edifact COM segment To identify a communication number of a department or a person to whom communication should be directed. Contact address for party or person (according to function qualifier in current CTA group). element trsd_contact.information children tred_contact.function.coded tred_contact.identifier tred_contact.name element VERMAS.GROUP9 edifact CTA segment To identify a person or a department to whom communication should be directed. With function code RP the segment is used for transmission of a signature (person's name in capital letters). Code and/or name of a contact such as a dept. or employee. Code preferred. Required if function code = RP element trsd_document.message.details 21

23 children tred_document.name.code tred_document.name tred_document.identifier element VERMAS.GROUP7 edifact DOC segment To identify documents, either printed, electronically transferred, or referenced as specified in message description, including, where relevant, the identification of the type of transaction that will result from this message. The DOC is used to specify type of SOLAS VGM documentation and a unique reference. element trsd_equipment.details children tred_equipment.qualifier tred_equipment.identification.number tred_equipment.size.and.type.identification element VERMAS.GROUP4 edifact EQD segment To specify container or equipment details. element trsd_measurements children tred_measurement.purpose.code.qualifier tred_measurement.attribute.coded tred_measurement.unit.code tred_measurement.value element VERMAS.GROUP5 edifact MEA segment To specify physical measurements, including dimension tolerances, weights and counts. To specify transport equipment gross weight and verified gross mass. Depending on the value of element tred_document.message.name.coded, it will be necessary to send certain information in the trsd_measurements element: If tred_document.message.name.coded = 749, it has to be declared a weight bigger than 0 Kg. If tred_document.message.name.coded = 127, then it has to be declared a weight of 0 Kg. 22

24 element trsd_name.and.address.g2 children tred_party.qualifier tred_party.id.identification tred_party.name1 tred_street.and.number.p.o.box1 tred_city.name tred_postal.identification.code tred_country.coded element VERMAS.GROUP2 edifact NAD segment element trsd_name.and.address.g8 children tred_party.qualifier tred_party.id.identification tred_code.list.qualifier tred_code.list.responsible.agency.coded tred_party.name1 tred_street.and.number.p.o.box1 tred_city.name tred_postal.identification.code tred_country.coded element VERMAS.GROUP8 edifact NAD segment element trsd_seal.number 23

25 children tred_seal.number tred_seal.issuer element VERMAS.GROUP4 edifact SEL segment element VERMAS children VERMAS.HEADER VERMAS.GROUP1 VERMAS.GROUP2 VERMAS.GROUP4 element VERMAS.GROUP1 children trcd_reference element VERMAS A group of segments to specify references relating to the whole message. element VERMAS.GROUP2 children trsd_name.and.address.g2 element VERMAS A group of segments to identify a party and/or addresses and related contacts. element VERMAS.GROUP4 children trsd_equipment.details trcd_reference trsd_seal.number VERMAS.GROUP5 VERMAS.GROUP7 24

26 element VERMAS A group of segments containing information about one packed container. Group transmitting VGM information about a container: - Identification and routing information - Gross mass (status verified or not) - DOC group for documentation of VGM element VERMAS.GROUP5 children trsd_measurements trcd_date.time.period element VERMAS.GROUP4 A group to specify measurements. A group specifying a packed container's gross mass, when it is verified and optionally the date/time when it was determined. element VERMAS.GROUP7 children trsd_document.message.details VERMAS.GROUP8 element VERMAS.GROUP4 To identify documents, either printed, electronically transferred, or referenced as specified in message description, including, where relevant, the identification of the type of transaction that will result from this message. Group specifying documentation related to SOLAS gross mass verification of a packed container. element VERMAS.GROUP8 children trsd_name.and.address.g8 VERMAS.GROUP9 element VERMAS.GROUP7 element VERMAS.GROUP9 children trsd_contact.information trsd_communication.contact element VERMAS.GROUP8 A Group of segments to identify a contact and his communications. 25

27 Group for specification of - contact information and/or signature of a responsible person - communication contact for party or person CTA segment with qualifier RP: - signature CTA segment with qualifier BN: - party or person name COM segment: - phone, fax, or physical address of party or person element VERMAS.HEADER children anxs_interchange.header anxs_message.header trsd_beginning.of.message trcd_date.time.period element VERMAS 26

28 4 USE CASES Use cases described in this chapter shall be implemented in the Port of Barcelona in the way as specified here. No Sender Receiver Use Case Details 1 Shipper Carrier Shipper has determined the weight himself (Standard process) 8 Carrier Terminal (Standard process) 2 Shipper Carrier 3rd party has weighed, as instructed by the shipper 4 Weighing Station Shipper Shipper had ordered the weighing 5 Weighing Station Carrier Shipper had ordered the weighing and instructed the weighing station to report to the carrier 6 Terminal Carrier If standard procedure at the terminal to weigh each container or a specific order to weigh a container 9 Carrier Shipper Carrier has got knowledge of a weight (e.g. from Terminal) 10 Carrier Terminal Carrier orders the weighing to the terminal 11 Shipper Carrier Shipper orders the weighing to the carrier 12 Shipper Weighing Shipper orders the weighing to the Station weighing station 13 Carrier Weighing Carrier orders the weighing to the weighing Station station (The number of the use case is based on the use cases included in the SMDG VERMAS v.0.4 MIG) GRAPHICAL REPRESENTATION OF THE USE CASES Shipper 1. VGM and additional information Carrier 2. VGM and additional information Terminal 1 8 Fig. 1 Standard process 27

29 3. Weighing value 2 Shipper Carrier 4. VGM information 1. Weighing instruction 2. Weighing value 4 Weighing 12 Station 2b. Weighing value 5 8 Termin al Fig. 2 Shipper orders weighing to a weighing station 1. Weighing instruction Weighing value Shipper Carrier 3. VGM information Terminal Weighing value 8 1b. Weighing instruction Weighing 13 Station Fig. 3 Carrier orders weighing to a weighing station 2. Weighing instruction Weighing instruction Shipper Carrier Terminal 4. Weighing value 9 3. Weighing value 6 Fig. 4 Carrier orders weighing to the terminal 28

30 5 INFORMATION USAGE IN EACH USE CASE Use case From/To S-->C S-->C W-->S W-->C T-->C C-->T C-->S C-->T S-->C S-->W C-->W Message function NL Who weighs S 3rd 3rd 3rd T S/3rd T/3rd T T/3rd 3rd 3rd 1 f Document issue date time M M M M M M M M M M M 2 a, (g) Shipper (the company) as Party Name and Address M M X X X C X C C C C 3 Full Name of the Authorized Person (at the Shipper) M M X X X C X X X X X 4 Contact details of the Shipper C C X X X X X X X X X 5 Carrier s Booking number M M M M M M M M M M M 6 (g) Carrier as Party Name and Address (Issuer of the booking) M M M M M M M M M M M 7 Container ID M M M M M M M C C C C 8 Container reference number C C C C C C C C C C C 9 Seal Number C C C C C C C C C C C 10 c Verified Gross Mass Value M M M M M M M X X X X 10b c Verified Gross Mass (Set to "0") X X X X X X X M M M M 11 Verification Date M M M M M C M X X X X 12 Shipper s internal reference C C C C C C X X C C X 13 d Method used (1 or 2) M M M M M C M X X X X 14 Weighing equipment ID C C C C C X C X X X X 15 b, (g) Party (the company) that has ascertained the VGM, Name and Address S 3rd 3rd 3rd T X T/3rd X X X X 16 Name of the person who has ascertained the VGM S 3rd 3rd 3rd T X T/3rd X X X X 17 e Document issuing party M M M M M M M M M M M 18 g Place where document has been issued M M M M M M M M M M M 19 Unique reference ID (documentation) C C M M M C M X X X X 20 Transport equipment gross mass verification order reference X X C C C X C C C C C Information usage in the use case: C: Conditional M: Mandatory X: Not used From/To: S: Shipper C: Carrier T: Terminal 3 rd : Third party Exemple: S-->C From shipper to carrier NL (national legislation): Contenido mínimo de los documentos a que se refiere el número 1 del apartado séptimo de la resolución del Director General de la Marina Mercante (junio de 2016) NL Description a Nombre y domicilio del expedidor. b Si la verificación es realizada por un tercero en nombre del expedidor se indicará el nombre y domicilio de uno y otro. c Masa bruta verificada del contenedor lleno, en kilogramos d Método de obtención de la masa bruta. e Nombre y firma (se admite la firma electrónica) de la persona física o jurídica que expide el documento. f Fecha de la expedición del documento. g Lugar de la expedición del documento. Message function: 749: Weighing information 127: Weighing order/instruction Who weighs: S: Shipper T: Terminal 3 rd : Third party 29

31 6 SCHEMA <xs:schema xmlns:xs=" <!-- MESSAGE STRUCTURE --> <xs:element name="vermas"> <xs:element ref="vermas.header"/> <xs:element ref="vermas.group1" maxoccurs="9"/> <xs:element ref="vermas.group2" maxoccurs="9"/> <xs:element ref="vermas.group4" maxoccurs="99999"/> <xs:element name="vermas.header"> <xs:element ref="anxs_interchange.header"/> <xs:element ref="anxs_message.header"/> <xs:element ref="trsd_beginning.of.message"/> <xs:element ref="trcd_date.time.period"/> <xs:element name="vermas.group1"> <xs:element ref="trcd_reference"/> <xs:element name="vermas.group2"> <xs:element ref="trsd_name.and.address.g2"/> <xs:element name="vermas.group4"> <xs:element ref="trsd_equipment.details"/> <xs:element ref="trcd_reference" maxoccurs="9"/> <xs:element ref="trsd_seal.number" minoccurs="0" maxoccurs="9"/> <xs:element ref="vermas.group5" minoccurs="1" maxoccurs="9"/> <xs:element ref="vermas.group7" minoccurs="0" maxoccurs="9"/> <xs:element name="vermas.group5"> <xs:element ref="trsd_measurements"/> <xs:element ref="trcd_date.time.period" minoccurs="0"/> <xs:element name="vermas.group7"> <xs:element ref="trsd_document.message.details"/> <xs:element ref="vermas.group8" minoccurs="0" maxoccurs="9"/> <xs:element name="vermas.group8"> <xs:element ref="trsd_name.and.address.g8"/> <xs:element ref="vermas.group9" minoccurs="0" maxoccurs="9"/> 30

32 <xs:element name="vermas.group9"> <xs:element ref="trsd_contact.information"/> <xs:element ref="trsd_communication.contact" minoccurs="0" maxoccurs="9"/> <!-- MESSAGE SEGMENTS --> <!-- UNB --> <xs:element name="anxs_interchange.header"> <xs:element ref="anxe_sender.identification"/> <xs:element ref="anxe_recipient.identification"/> <xs:element name="anxe_sender.identification"> <xs:minlength value="1"/> <xs:maxlength value="35"/> <xs:element name="anxe_recipient.identification"> <xs:minlength value="1"/> <xs:maxlength value="35"/> <!-- funb --> <!-- UNH --> <xs:element name="anxs_message.header"> <xs:element ref="anxe_message.reference.number"/> <xs:element ref="anxe_message.type"/> <xs:element ref="anxe_message.version.number"/> <xs:element ref="anxe_message.type.release.number"/> <xs:element ref="anxe_controlling.agency"/> <xs:element ref="anxe_association.assigned.code" minoccurs="0"/> <xs:element name="anxe_message.reference.number"> <xs:minlength value="1"/> <xs:maxlength value="14"/> <xs:element name="anxe_message.type"> <xs:enumeration value="vermas"/> <xs:element name="anxe_message.version.number"> <xs:enumeration value="d"/> <xs:element name="anxe_message.type.release.number"> <xs:enumeration value="16a"/> 31

33 <xs:element name="anxe_controlling.agency"> <xs:enumeration value="un"/> <xs:element name="anxe_association.assigned.code"> <xs:enumeration value="smdg10"/> <!-- funh --> <!-- BGM --> <xs:element name="trsd_beginning.of.message"> <xs:element ref="tred_document.message.name.coded"/> <xs:element ref="tred_document.message.number"/> <xs:element ref="tred_message.function.coded"/> <xs:element name="tred_document.message.name.coded"> <xs:enumeration value="749"/> <xs:enumeration value="127"/> <xs:element name="tred_document.message.number"> <xs:minlength value="1"/> <xs:maxlength value="70"/> <xs:element name="tred_message.function.coded"> <xs:enumeration value="1"/> <xs:enumeration value="5"/> <xs:enumeration value="9"/> <!-- fbgm --> <!-- DTM --> <xs:element name="trcd_date.time.period"> <xs:element ref="tred_date.time.period.qualifier"/> <xs:element ref="tred_date.time.period"/> <xs:element ref="tred_date.time.period.format.qualifier"/> <xs:element name="tred_date.time.period.qualifier"> <xs:enumeration value="137"/> <xs:enumeration value="798"/> <xs:element name="tred_date.time.period"> <xs:minlength value="1"/> 32

34 <xs:maxlength value="35"/> <xs:element name="tred_date.time.period.format.qualifier"> <xs:enumeration value="203"/> <!-- fdtm --> <!-- RFF --> <xs:element name="trcd_reference"> <xs:element ref="tred_reference.qualifier"/> <xs:element ref="tred_reference.number"/> <xs:element name="tred_reference.qualifier"> <xs:enumeration value="aas"/> <xs:enumeration value="abe"/> <xs:enumeration value="acw"/> <xs:enumeration value="ago"/> <xs:enumeration value="si"/> <xs:enumeration value="agp"/> <xs:enumeration value="bn"/> <xs:enumeration value="sq"/> <xs:enumeration value="vor"/> <xs:element name="tred_reference.number"> <xs:minlength value="1"/> <xs:maxlength value="70"/> <!-- frff --> <!-- EQD --> <xs:element name="trsd_equipment.details"> <xs:element ref="tred_equipment.qualifier"/> <xs:element ref="tred_equipment.identification.number" minoccurs="0"/> <xs:element ref="tred_equipment.size.and.type.identification" minoccurs="0"/> <xs:element name="tred_equipment.qualifier"> <xs:enumeration value="cn"/> <xs:element name="tred_equipment.identification.number"> <xs:maxlength value="17"/> <xs:element name="tred_equipment.size.and.type.identification"> <xs:maxlength value="10"/> 33

35 <!-- feqd --> <!-- SEL --> <xs:element name="trsd_seal.number"> <xs:element ref="tred_seal.number"/> <xs:element ref="tred_seal.issuer"/> <xs:element name="tred_seal.number"> <xs:minlength value="1"/> <xs:maxlength value="35"/> <xs:element name="tred_seal.issuer"> <xs:enumeration value="aa"/> <xs:enumeration value="ab"/> <xs:enumeration value="sh"/> <!-- fsel --> <!-- MEA --> <xs:element name="trsd_measurements"> <xs:element ref="tred_measurement.purpose.code.qualifier"/> <xs:element ref="tred_measurement.attribute.coded"/> <xs:element ref="tred_measurement.unit.code"/> <xs:element ref="tred_measurement.value"/> <xs:element name="tred_measurement.purpose.code.qualifier"> <xs:enumeration value="aae"/> <xs:element name="tred_measurement.attribute.coded"> <xs:enumeration value="vgm"/> <xs:element name="tred_measurement.unit.code"> <xs:enumeration value="kgm"/> <xs:element name="tred_measurement.value"> <xs:minlength value="1"/> <xs:maxlength value="18"/> <!-- fmea --> <!-- DOC --> <xs:element name="trsd_document.message.details"> <xs:element ref="tred_document.name.code"/> 34

36 <xs:element ref="tred_document.name" minoccurs="0"/> <xs:element ref="tred_document.identifier" minoccurs="0"/> <xs:element name="tred_document.name.code"> <xs:enumeration value="shp"/> <xs:enumeration value="sm1"/> <xs:enumeration value="sm2"/> <xs:element name="tred_document.name"> <xs:minlength value="1"/> <xs:maxlength value="35"/> <xs:element name="tred_document.identifier"> <xs:minlength value="1"/> <xs:maxlength value="70"/> <!-- fdoc --> <!-- NAD --> <!-- NAD Group 2 --> <xs:element name="trsd_name.and.address.g2"> <xs:element ref="tred_party.qualifier"/> <xs:element ref="tred_party.id.identification"/> <xs:element ref="tred_party.name1" minoccurs="0"/> <xs:element ref="tred_street.and.number.p.o.box1" minoccurs="0"/> <xs:element ref="tred_city.name" minoccurs="0"/> <xs:element ref="tred_postal.identification.code" minoccurs="0"/> <xs:element ref="tred_country.coded" minoccurs="0"/> <!-- NAD Group 8 --> <xs:element name="trsd_name.and.address.g8"> <xs:element ref="tred_party.qualifier"/> <xs:element ref="tred_party.id.identification" minoccurs="0"/> <xs:element ref="tred_code.list.qualifier" minoccurs="0"/> <xs:element ref="tred_code.list.responsible.agency.coded" minoccurs="0"/> <xs:element ref="tred_party.name1" minoccurs="0"/> <xs:element ref="tred_street.and.number.p.o.box1" minoccurs="0"/> <xs:element ref="tred_city.name" minoccurs="0"/> <xs:element ref="tred_postal.identification.code" minoccurs="0"/> <xs:element ref="tred_country.coded" minoccurs="0"/> <xs:element name="tred_party.qualifier"> <xs:enumeration value="cf"/> <xs:enumeration value="ca"/> <xs:enumeration value="tb"/> <xs:enumeration value="am"/> <xs:enumeration value="spc"/> <xs:enumeration value="wpa"/> <xs:element name="tred_party.id.identification"> 35

37 <xs:minlength value="1"/> <xs:maxlength value="35"/> <xs:element name="tred_code.list.qualifier"> <xs:enumeration value="eori"/> <xs:enumeration value="tax"/> <xs:element name="tred_code.list.responsible.agency.coded"> <xs:enumeration value="zzz"/> <xs:element name="tred_party.name1"> <xs:minlength value="1"/> <xs:maxlength value="70"/> <xs:element name="tred_street.and.number.p.o.box1"> <xs:maxlength value="35"/> <xs:element name="tred_city.name"> <xs:maxlength value="35"/> <xs:element name="tred_postal.identification.code"> <xs:maxlength value="17"/> <xs:element name="tred_country.coded"> <xs:maxlength value="3"/> <!-- fnad --> <!-- CTA --> <xs:element name="trsd_contact.information"> <xs:element ref="tred_contact.function.coded"/> <xs:element ref="tred_contact.identifier" minoccurs="0"/> <xs:element ref="tred_contact.name" minoccurs="0"/> <xs:element name="tred_contact.function.coded"> <xs:enumeration value="bn"/> <xs:enumeration value="rp"/> 36

38 <xs:element name="tred_contact.identifier"> <xs:maxlength value="17"/> <xs:element name="tred_contact.name"> <xs:minlength value="1"/> <xs:maxlength value="35"/> <!-- fcta --> <!-- COM --> <xs:element name="trsd_communication.contact"> <xs:element ref="tred_communication.address.identifier"/> <xs:element ref="tred_communication.means.type.code"/> <xs:element name="tred_communication.address.identifier"> <xs:minlength value="1"/> <xs:maxlength value="512"/> <xs:element name="tred_communication.means.type.code"> <xs:enumeration value="em"/> <xs:enumeration value="fx"/> <xs:enumeration value="ma"/> <xs:enumeration value="te"/> <!-- fcom --> </xs:schema> 37