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 · Customs and regulatory

WASDIS Waste disposal information

The UN/EDIFACT message that reports waste and cargo residues on board a vessel still to be disposed of at the next port, and the last inspection.

Sent by
Vessel operator or agent
Received by
Port authority or waste reception facility
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT WASDIS message?

WASDIS is the UN/EDIFACT waste disposal information message. The directory defines it as a message conveying information on the last inspection, or on waste and cargo residues on board a means of transport such as a vessel, or related to its equipment, that are still to be disposed of at the next place or port of call.

Many ports require advance notification of ship-generated waste so reception facilities can plan collection, and regulations such as those implementing MARPOL require ships to deliver waste ashore. The message carries the types and quantities of waste, storage capacity and where it was last delivered.

How the EDIFACT WASDIS message worksDiagram of the UN/EDIFACT WASDIS Waste disposal information message. Vessel operator or agent sends it to port authority or waste reception facility. It usually starts the exchange. 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 SG3 loop with TDT (Transport information). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT WASDIS message worksWaste disposal information: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeWASDISSENDERVessel operator oragentRECEIVERPort authority orwaste receptionfacilityCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage WASDISUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG3 · repeats up to 1TDTTransport information+ 4 conditional groups, starting with:RFFLOCNADDGSBlue 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 WASDIS. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT WASDIS message worksDiagram of the UN/EDIFACT WASDIS Waste disposal information message. Vessel operator or agent sends it to port authority or waste reception facility. It usually starts the exchange. 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 SG3 loop with TDT (Transport information). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT WASDISmessage worksWaste disposal information: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeWASDISSENDERVessel operatoror agentRECEIVERPort authority orwaste receptionfacilityCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message WASDIS (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG3 · repeats upto 1TDTTransport information+ 4 conditional groups, starting with:RFFLOCNADDGSBlue 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 WASDIS.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends WASDIS, 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 WASDIS 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

  • Notifying a port of waste to be delivered ashore
  • Reporting waste storage on board before arrival
  • Supporting port reception facility planning

Where it fits in the message flow

This message WASDIS Waste disposal information

No other message routinely comes directly before or after WASDIS; it is exchanged when the business event occurs. If the partners agree, the receiver confirms each interchange with a CONTRL syntax and service report.

Structure

Mandatory segments in WASDIS (directory D.21A)

In UN/EDIFACT directory D.21A, the WASDIS message has 26 segment positions arranged in 6 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
  • SG3 (TDT)
  • UNT

Practical example

WASDIS in practice

A tanker will call at a European port in two days. Its agent sends the port authority a WASDIS listing the quantities of oily waste, garbage and sewage on board, the remaining storage capacity and the last port where waste was delivered. The port arranges a reception barge for the oily waste during the call.

Implementation

Implementation considerations for WASDIS

  • Meet the port's advance notification deadline.
  • Use the waste categories the regulations and port require.
  • Keep records of waste delivered for inspections.
  • Check whether the port receives notifications through a single window.

How ECOM helps

Automate WASDIS with ECOM

Industry

Trucking and Transportation

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

Solution

EDI Integration

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

Solution

Logistics Automation

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

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

Related messages

Related customs and regulatory messages

All 14 customs and regulatory messages

Need help with WASDIS?

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

Request a Demo Contact us