| Version: | D |
|---|---|
| Release: | 02B |
| Contr. Agency: | UN |
| Revision: | 2 |
| Date: | 2003-02-13 |
| SOURCE: | D4 Transport (SWG) |
|
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 |
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.
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.
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.
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.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
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 element | 0065 | BERMAN |
| 0052 | D | |
| 0054 | 02B | |
| 0051 | UN |
A segment to indicate the beginning of the message by identifying the message by a message number.
A segment to identify a date and time on which the message is prepared.
A segment to give free form or coded text information at message level
A segment to provide a reference relating to the whole message, such as: - reference to previous message.
A group of segments to identify a party related to the message.
A segment to identify the name and address of the ship's agent. The function to be qualified: - ship agent
A group of segments to identify a contact and its communications related to the party.
A segment to identify a person or a department within the party.
A segment to identify a communication number of the contact to whom communication should be directed.
A group of segments to specify details for the arriving means of transport.
A segment to identify the transport details of the arriving vessel.
A segment to identify a relevant reference number, such as: - Lloyds number - shipping line reference - conference - internal customer code
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
A segment to specify physical dimensions of the vessel such as: - breadth - total length - draught - dead-weight
A segment to provide supplementary information related to the means of transport, such as: - segregated ballast tanks - double bottom
A group of segments to specify details of the ship's route
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
A segment to identify a date and time related to the ports of call in the ship's route
A group of segments to provide customs information
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
A segment to identify a relevant reference codes, such as - customs codes for vessel routes - customs codes for special transit procedures
A segment to identify the name and address of a party relevant to the message, such as: - cargo brokers, consortia members sharing the vessel
A group of segments to specify details for the transport service requirements
A segment to specify berthing, pilot and tugboat service details of the arriving vessel, such as: - arrival and berth, - change of berth, - change of side, - request for pilots service, - request for tugboat service, - request for mooring service
A segment to indicate number of ports of call by the same captain on board in the same vessel
A segment to provide supplementary information related to the berthing, pilot, tugboat and mooring service details, such as: - payment terms, - remarks required by government sector
A group of segments to specify details of the service required.
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
A segment to specify current physical dimensions of the vessel when entering the port, such as: - actual draught
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: - estimated/actual date and time for berthing, - estimated departure, - estimated arrival time to the pilot station, - estimated time for tugboat service start
A segment to indicate number of pilots or tugboats required.
A segment to specify the purpose of conveyance call, such as: - cargo operation - repair
A segment to provide supplementary information related to the berth details, such as: - waste disposal facilities - supplies requested (water, power, fuel)
A group of segments to specify details for the operations to be carried out.
A segment to identify the type of handling movement, such as: - loading - unloading
A segment to identify a name and address of a party, such as: - stevedoring company
A group of segments to specify details of the cargo to be handled.
A segment to identify the type of cargo, such as: - containers - dry bulk - liquid bulk - others
A segment to provide detailed information related to the type of cargo
A segment to specify cargo weight
A segment to identify number of units, such as: - containers - cars
A segment to identify dangerous goods
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.
| 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 | |
| QTY | Quantity | |
| RFF | Reference | |
| TDT | Transport information | |
| TSR | Transport service requirements | |
| UNH | Message header | |
| UNT | Message trailer |
| ├─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 Transport information | ×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) |
| │─├─QTY Quantity | ×9 | (C) |
| │─├─FTX Free text | ×9 | (C) |
| │─└─Segment Group 7 | ×9 | (C) |
| │───├─LOC Place/location identification | ×1 | (M) |
| │───├─MEA Measurements | ×9 | (C) |
| │───├─DTM Date/time/period | ×9 | (C) |
| │───├─QTY Quantity | ×9 | (C) |
| │───├─POC Purpose of conveyance call | ×9 | (C) |
| │───├─FTX Free text | ×9 | (C) |
| │───└─Segment Group 8 | ×9 | (C) |
| │─────├─HAN Handling instructions | ×1 | (M) |
| │─────├─NAD Name and address | ×9 | (C) |
| │─────└─Segment Group 9 | ×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) |