Destin8 and Container Gross Mass Verification (VGM)

Transcription

1 1. Legal Background and Requirements a. International: SOLAS regulation 2, chapter VI, paragraphs 4 to 6. Adopted November 2014 and entering into force 1 July 2016 with the intervening period considered the transition period. b. UK: MCA Guidelines (MGN 534) for UK implementation of the mandatory amendments requiring the shipper (as named on the bill of lading, waybill or through bill) to verify and provide the container s gross mass to the carrier and terminal representative prior to it being loaded onto a ship. c. MGN 534 states that participants within the supply chain should agree amongst themselves the processes necessary to ensure that the weights are available prior to the packed container being loaded aboard the ship. The guidelines apply to export consignments only i.e. inbound containers have been verified in the country of loading. d. The SOLAS provisions do not apply to containers being loaded on a chassis or trailer on a ro-ro ship that is engaged on short sea voyages. e. Methods of obtaining the VGM of a packed container i. Method 1 (SM1) weighing the container using calibrated and certified weighing equipment (COPARN definition EGW=Gross Weight (including transport unit) ii. Method 2 (SM2) weighing all packages, cargo items, pallets, dunnage and other securing material and adding the tare (COPARN definition Option G+T where G=Gross weight (excluding transport unit) and T=Tare weight (transport unit)) f. The use of SM2 is subject to the shipper using a certified method approved by the MCA or its authorised body. Approved companies will be registered on an MCA database accessible to shippers, carriers and terminal operators. SM2 is the preferred option unless the cargo items do not lend themselves to individual weighing. g. The VGM SM1 or SM2 must be communicated by the shipper in a shipping document e.g. a declaration including a weight certificate produced by a weighing station (SM1) or in case of SM2, the shipper s approval number. If appropriate, EDI methods can also be used. Irrespective of the format, a duly authorised person must sign the VGM document; the signature may be electronic or may be replaced by the name in capitals of the authorised person. h. The shipper can provide the VGM direct to the carrier or the terminal, other than having to be submitted sufficiently in advance to be used in the preparation of the ship stowage plan there are no defined timescales in the guidelines for the provision of the VGM as this is not deemed a regulatory issue. i. If the terminal weighs a packed container, then the carrier and the terminal operator will need to have a process for determining which value to use. A container with a VGM exceeding the maximum CSC gross may not be loaded. j. Discrepancies should be resolved between the terminal and the carrier and parties are encouraged to consider how non-compliances are identified and rectified. The MCA should be notified and incidents may result in withdrawal of a company s SM2 approval. The enforcement threshold is +/- 5% of the VGM on a case-by-case basis. The carrier and/or the terminal operator must maintain adequate systems and audit records to verify that the VGM or change to the VGM are managed before loading to a ship. Destin8 and Container Gross Mass Verification (VGM) v1.1 - MCP plc

2 2. Data Formats and Values a. MCA SM2 Authorisation Number 1234/GB/12AA i sequential number issued by the MCA (this will need to allow for ) ii. GB country of issue iii. 12AA expiry date of approval b. Verified Gross Mass (VGM) i. Temporary measurement attribute code adopted by SMDG (subject to UN/CEFACT DMRs) for use in the EQD MEA segment on COPARN, COARRI and CODECO messaging with a max measurement value of 16an. Example: MEA+AAE+VGM+KGM:10474 c. SOLAS Packed Container Responsible Party (SPC) and Authorised Person (AM) i. Temporary Party Function Code Qualifiers adopted by SMDG for use in the NAD Party Name segment (AM is Mandatory, SPC optional if the VGM is present in the MEA segment). Max value of 35an. Example: NAD+AM+++JOHN DILLINGER d. SOLAS Method of ascertaining a Verified Gross Mass i. SM1 (Method 1) Temporary code adopted by SMDG for Verified Gross Mass ascertained by weighing. Used in the EQG segment, Example: FTX+ABS++SM1:ZZZ:SMD ii. SM2 (Method 2) Temporary code adopted by SMDG for Verified Gross Mass ascertained by calculation. Used in the EQD segment. Example: FTX+ABS++SM2:ZZZ:SMD e. Terminal weight checking (Temporary attribute codes adopted by SMDG) i. Terminal Weighing Party (WPA) used in the CODECO header (BGM) Segment. Max value of 35an. Example: NAD+WPA+CONWS:TER:ZZZ ii. VGM verification reference (VGR) for use in the COPARN/CODECO/COARRI EQD segment. Max value of 35an. Example: RFF+VGR:V iii. Date/time of terminal verification (798) for use in the COPARN/CODECO EQD segment. Max value of 12an. Example DTM+798: :203 iv. Terminal VGM verification order reference (VOR) for use in the COPARN/CODECO EQD segment (COPARN/CODECO). Max value of 35an. Example: RFF+VOR:V v. Transport Equipment Status Change Report (999) code for use in the CODECO Message Header (BGM) segment where the verified gross mass was checked after a normal Gate in move. Example: BGM AB vi. BN Certification Contact - Document type code for use in the CODECO Message Header (BGM) segment for the Department/Person responsible for issuing a verified gross mass. Example: CTA+BN+: JOHN SMITH f. Certificates i. No apparent requirement to provide copy certificates and/or certificate references in the information exchange described in the MGN. g. Method 1 (SM1) and Method 2 (SM2) i. Default to SM2 if VGM present and the SPC references an MCA authorisation number else SM1. Destin8 and Container Gross Mass Verification (VGM) v1.1 - MCP plc

3 3. Destin8 OLTP, ISL and EDIFACT messaging a. OLTP In i. Add new Verified Gross Mass section to transactions EBK and EBM to allow fields for Method (3an), Shipper VGM (5n), AM (35an), SPC (35an), Date/Time (12n), VGR (35an), VOR (35an). Fields cannot be amended after loading or where the terminal operator does not permit changes to a VGM submitted by the terminal on in-gate. ii. Add new Verified Gross Mass section to ENQ to display fields for Method (3an), Shipper VGM (5n), AM (35an), SPC (35an), Terminal VGM (5n), WPA (35an), VGR (35an), Date/Time (12an), VOR (35an), VGR (35an). Checklist dropdown selection (in Additional Options) to be extended to include Checklisted with VGM and Checklisted without VGM. iii. Modify EIN Action Type A to enable the wharfinger to update export booking records for units with no previously declared VGM or, where applicable, to check a previously declared VGM. Include fields for Method (3an), VGM (5an), AM (35an), SPC (35an), WPA (35an), VGR (35an), Date/Time (12an), VOR (35an), BN (35an). Where the terminal is adding a new VGM as a result of a VGM check, include the original VGM in any output except the CODECO. Action A for VGM changes not permissible if DPG Prior Approval exists. b. OLTP Out (Text) i. Discrepancy output notification (VGM01) to include fields for Method (3an), VGM (5an), AM (35an), SPC (35an), WPA (35an), VGR (35an), Date/Time (12an), VOR (35an), BN (35an) and Terminal Weighing Notification (VGM02) to carrier, declarant, notify party and terminal plus the usual vessel, voyage, UCN, Unit id, Unit type/size, and booking information etc. c. ISL Out (Existing) i. EBK01 add fields for Method (3an), VGM (5n), AM (35an), SPC (35an), Date/Time (12an), VGR (35an), VOR (35an) to the end of the message. ii. EBM01 add fields for Method (3an), Shipper VGM (5an), AM (35an), SPC (35an), Date/Time (12an), VGR (35an), VOR (35an) to the end of the message. iii. EIN01/EIN02 - add fields for Method (3an), VGM (5an), AM (35an), SPC (35an), WPA (35an), VGR (35an), Date/Time (12an), VOR (35an), BN (35an) and VGM (Booked) (5an) at the end of the message. If the booked VGM is different to the terminal VGM iv. ELC01 add fields for Method (3an), VGM (5n), AM (35an), SPC (35an), Date/Time (12n), VGR (35an) to the end of the message. v. ECK01 add a field for VGM (5n) to the end of the message (Request/Removal section before Modification (Action=M)) and Old VGM (5n) if the VGM has been amended. Destin8 and Container Gross Mass Verification (VGM) v1.1 - MCP plc

4 d. ISL In (Existing) i. EBI01 add fields for Method (3an), VGM (5n), AM (35an), SPC (35an), Date/Time (12n), VGR (35an), VOR (35an) to the end of the message. ii. EBI04 - add fields for Method (3an), Shipper VGM (5n), AM (35an), SPC (35an), Date/Time (12n), VGR (35an), VOR (35an) to the end of the message. Fields cannot be amended after loading or where the terminal operator does not permit changes to a VGM submitted by the terminal on in-gate. iii. EIN add fields for Method (3an), VGM (5n), AM (35an), SPC (35an), WPA (35an), VGR (35an), Date/Time (12n), VOR (35an), BN (35an) to the end of message when used for Ingate Action Type A. Where the terminal is adding a new VGM as a result of a VGM check, include the original VGM in any output. Action A for VGM changes not permissible if DPG Prior Approval exists. e. ISL Out (New) i. Discrepancy output notification (VGM01) to include fields for Method (3an), VGM Booked (5n), VGM Terminal (5n), AM (35an), SPC (35an), WPA (35an), VGR (35an), Date/Time (12n), VOR (35an), BN (35an) and a Terminal Weighing Notification (VGM02) to include fields for Method (3an), VGM Terminal (5n), WPA (35an), Date/Time (12n), VOR (35an), BN (35an) to carrier, declarant, notify party and terminal plus the usual vessel, voyage, UCN, Unit id, Unit type/size, and booking information etc. f. EDIFACT (Existing) i. COPARN D95B adapt to allow create/amend processing of the SMDG VGM, SM1/2, SPC, AM, Date/Time (798), VGR and VOR attributes described in section 2b, c, d and e above. ii. CODECO D95B adapt to allow processing of SMDG VGM, SM1/2, SPC, AM, WPA, VGR, Date/Time (798), BN and VOR attributes described in section 2b, c, d and e above. CODECO D95B amendments must be generated as a Transport Equipment Status Change Report using code 999 the header (BGM) if the EIN A is for a VGM update. iii. COARRI 95B - adapt to allow processing of SMDG VGM, SM1/2, SPC, AM, VGR and Date/Time (798) attributes described in section 2b, c, d and e above g. Port Charges functionality to enable the Destin8 Port Charge module to invoice cargo brokers or declarants for terminal VGM declarations or check weighing of pre-exec d export units is required. This should include functionality that will automatically calculate a port charge based on a configurable +/- discrepancy percentage of declared versus checked VGM where required e.g. a flag set against the terminal operator code/berth. The charging triggers will be the EIN A/VGM01 and/or EIN A/VGM02 update (see a.iii and d.iii above) Destin8 and Container Gross Mass Verification (VGM) v1.1 - MCP plc

5 4. Business & Functional Issues and/or Additional Requirements a. OLTP/EDIFACT/ISL reject groupage create/amend options if the accumulated weight of groupage exceeds or fall short of that entered at 9-digit level where the 9-digit booking includes a VGM SM1/SM2 declaration. b. EHA01 currently allows for amendment of the unit tare weight, subject to future review this will continue to be permitted even if a SM1 VGM exists. EHA01 ISL input permits the use of the { function to retain the original booking value). c. No changes required for processing of import consignments as the VGM will have been declared at the original port of origin/loading. d. Other than adding a VGM and VGM Old field to the ECK01 output, no changes required for existing checklisting functionality (including all COPRAR processing). VGM visibility will be maintained through ENQ OLTP display and search functions detailed in 3.a.ii and 3.e.i (VGM01/02 output) above. e. For audit purposes, storage of two or more VGM declarations and associated information to be facilitated and made available in PNQ, current declarations only in ENQ. See also 3.a.iii above. f. Timescale for transitioning the VGM requirements condensed information to all carriers and terminal operators by 15 January 2016, Destin8 EDIFACT and ISL message specifications and implementation guides by 10 February Target for Destin8 UAT availability w/c 4 April 2016 (Release 4.14) with PRD implementation 7 June 2016 (Release 4.15) to allow for shipments reaching the port of destination on or after the 1 July Destin8 and Container Gross Mass Verification (VGM) v1.1 - MCP plc