Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D01A Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Berth management message

Version:D
Release:01A
Contr. Agency:UN
Revision:1
Date:2000-10-26
SOURCE:D4 Transport (SWG)

CONTENTS
Berth management message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard terms and definitions
  5. MESSAGE DEFINITION
    1. Segment clarification
    2. Segment index (alphabetical sequence by tag)
    3. Message structure
      1. Segment table

For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction


This message also occurs in the following versions of this standard:
D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B

0. INTRODUCTION

This specification provides the definition of the Berth management message (BERMAN) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional definition

The Berth management message is a message from a carrier, its agent or means of transport to the authority responsible for port and waterway management, requesting a berth, giving details of the call, vessel, berth requirements and expected operations.


1.2. Field of application

The Berth management 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.


1.3. Principles

This message is meant to comply with requirements of authorities concerning the request for berthing services. The following guidelines, rules and functionality apply to this Berth management message:

1- A message will contain information on only one means of transport/conveyance. The only exception will be the case of covering pre-announcement function.

2- A ship call may require several berths.

3- One berth may be the scenario of several operations.

4- The message has to cater for the provision of sending updates (cancellation, replace, provisional, definitive) or new services request such as shifts and request for second berth. The message will cover the function of pre-announcement of vessels.

The Transport SWG Working Group (D4) has developed recommendations for a harmonised implementation of this message through its subgroup ITIGG (International Transport Implementation Guidelines Group). Users implementing the message are strongly advised to apply these recommendations, which may be obtained from the D4 secretariat.


2. REFERENCES

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.


3. TERMS AND DEFINITIONS


3.1. Standard terms and definitions

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.


4. MESSAGE DEFINITION


4.1. Segment clarification

This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.

0010 UNH, Message header

A service segment starting and uniquely identifying a message. The message type code for the Berth management message is BERMAN.

Note: Berth management messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065BERMAN
0052D
005401A
0051UN

0020 BGM, Beginning of message

A segment to indicate the beginning of the message by identifying the message by a message number.

0030 DTM, Date/time/period

A segment to identify a date and time on which the message is prepared.

0040 FTX, Free text

A segment to give free form or coded text information at message level

0050 RFF, Reference

A segment to provide a reference relating to the whole message, such as: - reference to previous message.

0060 Segment Group 1: NAD-SG2

A group of segments to identify a party related to the message.

0070 NAD, Name and address

A segment to identify the name and address of the ship's agent. The function to be qualified: - ship agent

0080 Segment Group 2: CTA-COM

A group of segments to identify a contact and its communications related to the party.

0090 CTA, Contact information

A segment to identify a person or a department within the party.

0100 COM, Communication contact

A segment to identify a communication number of the contact to whom communication should be directed.

0110 Segment Group 3: TDT-RFF-DTM-MEA-FTX-SG4-SG5

A group of segments to specify details for the arriving means of transport.

0120 TDT, Details of transport

A segment to identify the transport details of the arriving vessel.

0130 RFF, Reference

A segment to identify a relevant reference number, such as: - Lloyds number - shipping line reference - conference - internal customer code

0140 DTM, Date/time/period

A segment to identify a date and time related to the arrival of the means of transport, such as: - estimated time of arrival - estimated time of departure

0150 MEA, Measurements

A segment to specify physical dimensions of the vessel such as: - breadth - total length - draught - dead-weight

0160 FTX, Free text

A segment to provide supplementary information related to the means of transport, such as: - segregated ballast tanks - double bottom

0170 Segment Group 4: LOC-DTM

A group of segments to specify details of the ship's route

0180 LOC, Place/location identification

A segment to identify locations related to the transport details, such as: - previous port of call - next port of call - port of origin - port of destination

0190 DTM, Date/time/period

A segment to identify a date and time related to the ports of call in the ship's route

0200 Segment Group 5: GOR-RFF-NAD

A group of segments to provide customs information

0210 GOR, Governmental requirements

A segment to indicate the requirement for a specific governmental action and/or procedure. Codes indicating the movement of goods (import, export, transit) and other customs requirements regarding the ship calls will be applied

0220 RFF, Reference

A segment to identify a relevant reference codes, such as - customs codes for vessel routes - customs codes for special transit procedures

0230 NAD, Name and address

A segment to identify the name and address of a party relevant to the message, such as: - cargo brokers, consortia members sharing the vessel

0240 Segment Group 6: TSR-LOC-MEA-DTM-POC-FTX-SG7

A group of segments to specify details for the transport service requirements

0250 TSR, Transport service requirements

A segment to specify berthing service details of the arriving vessel, such as: - arrival and berth - arrival and mooring - change of berth - change of side

0260 LOC, Place/location identification

A segment to identify locations related to the berth details, such as: - preferred berth - preferred side for berthing - preferred mooring site - goods position - pilot embarkation point

0270 MEA, Measurements

A segment to specify current physical dimensions of the vessel when entering the port, such as: - actual draught

0280 DTM, Date/time/period

A segment to identify a date and time related to the arrival of the means of transport at the berth and mooring site specified, such as: - actual date and time for berthing - estimated departure

0290 POC, Purpose of conveyance call

A segment to specify the purpose of conveyance call, such as: - cargo operation - repair

0300 FTX, Free text

A segment to provide supplementary information related to the berth details, such as: - waste disposal facilities - supplies requested (water, power, fuel)

0310 Segment Group 7: HAN-NAD-SG8

A group of segments to specify details for the operations to be carried out.

0320 HAN, Handling instructions

A segment to identify the type of handling movement, such as: - loading - unloading

0330 NAD, Name and address

A segment to identify a name and address of a party, such as: - stevedoring company

0340 Segment Group 8: GDS-FTX-MEA-EQN-DGS

A group of segments to specify details of the cargo to be handled.

0350 GDS, Nature of cargo

A segment to identify the type of cargo, such as: - containers - dry bulk - liquid bulk - others

0360 FTX, Free text

A segment to provide detailed information related to the type of cargo

0370 MEA, Measurements

A segment to specify cargo weight

0380 EQN, Number of units

A segment to identify number of units, such as: - containers - cars

0390 DGS, Dangerous goods

A segment to identify dangerous goods

0400 UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.


4.2. Segment index (alphabetical sequence by tag)

BGM Beginning of message
COM Communication contact
CTA Contact information
DGS Dangerous goods
DTM Date/time/period
EQN Number of units
FTX Free text
GDS Nature of cargo
GOR Governmental requirements
HAN Handling instructions
LOC Place/location identification
MEA Measurements
NAD Name and address
POC Purpose of conveyance call
RFF Reference
TDT Details of transport
TSR Transport service requirements
UNH Message header
UNT Message trailer

4.3. Message structure


4.3.1. Segment table

├─UNH Message header ×1 (M)
├─BGM Beginning of message ×1 (M)
├─DTM Date/time/period ×9 (C)
├─FTX Free text ×9 (C)
├─RFF Reference ×9 (C)
├─Segment Group 1 ×9 (M)
├─NAD Name and address ×1 (M)
└─Segment Group 2 ×9 (C)
──├─CTA Contact information ×1 (M)
──└─COM Communication contact ×9 (C)
├─Segment Group 3 ×99 (M)
├─TDT Details of transport ×1 (M)
├─RFF Reference ×9 (C)
├─DTM Date/time/period ×9 (C)
├─MEA Measurements ×99 (C)
├─FTX Free text ×9 (C)
├─Segment Group 4 ×999 (C)
├─LOC Place/location identification ×1 (M)
└─DTM Date/time/period ×9 (C)
└─Segment Group 5 ×9 (C)
──├─GOR Governmental requirements ×1 (M)
──├─RFF Reference ×9 (C)
──└─NAD Name and address ×99 (C)
├─Segment Group 6 ×9 (C)
├─TSR Transport service requirements ×1 (M)
├─LOC Place/location identification ×9 (C)
├─MEA Measurements ×9 (C)
├─DTM Date/time/period ×9 (C)
├─POC Purpose of conveyance call ×9 (C)
├─FTX Free text ×9 (C)
└─Segment Group 7 ×9 (C)
──├─HAN Handling instructions ×1 (M)
──├─NAD Name and address ×9 (C)
──└─Segment Group 8 ×9 (C)
────├─GDS Nature of cargo ×1 (M)
────├─FTX Free text ×9 (C)
────├─MEA Measurements ×9 (C)
────├─EQN Number of units ×9 (C)
────└─DGS Dangerous goods ×9 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D01A Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify Legacy Data Integration with Stylus Studio XML Enterprise Edition - Free Download!
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2011 All Rights Reserved.