972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Transport

BERMAN Berth management

The UN/EDIFACT message a carrier, its agent or a vessel uses to request a berth from the port authority and give details of the call.

Sent by
Carrier, its agent or the vessel
Received by
Port or waterway authority
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT BERMAN message?

BERMAN is the UN/EDIFACT berth management message. The directory defines it as a message from a carrier, its agent or the means of transport to the authority responsible for port and waterway management, requesting a berth and giving details of the call, the vessel, berth requirements and the expected operations.

Port authorities use berth requests to allocate berths, pilots and tugs and to plan traffic. Requests are sent before arrival and updated as the vessel's estimated time of arrival changes.

How the EDIFACT BERMAN message worksDiagram of the UN/EDIFACT BERMAN Berth management message. Carrier, its agent or the vessel sends it to port or waterway authority. It usually starts the exchange. It is usually followed by CALINF. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: the required SG1 loop with NAD (Name and address) and the required SG3 loop with TDT (Transport information). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT BERMAN message worksBerth management: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeBERMANSENDERCarrier, its agent orthe vesselRECEIVERPort or waterwayauthorityCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCALINFVessel call information2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage BERMANUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 99NADName and addressMandatory group SG3 · repeats up to 99TDTTransport information+ 4 conditional groups, starting with:CTALOCGORTSRBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for BERMAN. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT BERMAN message worksDiagram of the UN/EDIFACT BERMAN Berth management message. Carrier, its agent or the vessel sends it to port or waterway authority. It usually starts the exchange. It is usually followed by CALINF. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: the required SG1 loop with NAD (Name and address) and the required SG3 loop with TDT (Transport information). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT BERMANmessage worksBerth management: who sends it, where it fitsand what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeBERMANSENDERCarrier, itsagent or thevesselRECEIVERPort orwaterwayauthorityCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYCALINFVessel call information2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message BERMAN (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 99NADName and addressMandatory group SG3 · repeats upto 99TDTTransport information+ 4 conditional groups, starting with:CTALOCGORTSRBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for BERMAN.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends BERMAN, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around BERMAN and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Requesting a berth for a vessel call
  • Updating arrival times and berth requirements
  • Informing the port of planned cargo operations

Where it fits in the message flow

This message BERMAN Berth management
Usually followed by CALINF Vessel call information

Structure

Mandatory segments in BERMAN (directory D.21A)

In UN/EDIFACT directory D.21A, the BERMAN message has 40 segment positions arranged in 10 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • SG1 (NAD)
  • SG3 (TDT)
  • UNT

Practical example

BERMAN in practice

A liner agent in Gothenburg expects a container vessel in 48 hours. It sends the port authority a BERMAN with the vessel's identity and dimensions, the estimated arrival and departure, the requested berth and the planned operations. The port allocates the berth and schedules pilotage, and the agent sends updates as the arrival time firms up.

Implementation

Implementation considerations for BERMAN

  • Send requests within the port's notification deadlines.
  • Update the estimated arrival time promptly as it changes.
  • Use IMO numbers and port codes consistently.
  • Follow the national single window or port community specification.

How ECOM helps

Automate BERMAN with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related transport messages

All 36 transport messages

Need help with BERMAN?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us