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

MOVINS Stowage instruction

The UN/EDIFACT message that gives a terminal instructions for loading, discharging and restowing equipment and cargo on a vessel.

Sent by
Carrier or central vessel planner
Received by
Container terminal
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT MOVINS message?

MOVINS is the UN/EDIFACT stowage instruction message. The directory defines it as a message containing details of one means of transport, giving instructions for the loading, discharging and restowage of equipment or cargo and the locations on board where those operations must take place.

A carrier's central planner uses MOVINS to tell a terminal where containers for each destination, weight class or type should be stowed. The terminal's planners then assign individual containers to positions and report the result in a BAPLIE.

How the EDIFACT MOVINS message worksDiagram of the UN/EDIFACT MOVINS Stowage instruction message. Carrier or central vessel planner sends it to container terminal. It usually starts the exchange. It is usually followed by BAPLIE and COARRI. 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 SG4 loop with TDT (Transport information) and the required SG6 loop with HAN (Handling instructions). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT MOVINS message worksStowage instruction: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeMOVINSSENDERCarrier or centralvessel plannerRECEIVERContainer terminalCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYBAPLIEBayplan/stowage planoccupied and emptylocationsCOARRIContainerdischarge/loadingreport2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage MOVINSUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG4 · repeats up to 9TDTTransport informationMandatory group SG6 · repeats up to 9HANHandling instructions+ 4 conditional groups, starting with:RFFNADLOCBlue 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 MOVINS. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT MOVINS message worksDiagram of the UN/EDIFACT MOVINS Stowage instruction message. Carrier or central vessel planner sends it to container terminal. It usually starts the exchange. It is usually followed by BAPLIE and COARRI. 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 SG4 loop with TDT (Transport information) and the required SG6 loop with HAN (Handling instructions). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT MOVINSmessage worksStowage instruction: who sends it, where it fitsand what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeMOVINSSENDERCarrier orcentral vesselplannerRECEIVERContainerterminalCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYBAPLIEBayplan/stowage plan occupied andempty locationsCOARRIContainer discharge/loading report2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message MOVINS (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG4 · repeats upto 9TDTTransport informationMandatory group SG6 · repeats upto 9HANHandling instructions+ 4 conditional groups, starting with:RFFNADLOCBlue 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 MOVINS.Your trading partner's implementation guide adds itsown requirements.

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

  • Instructing a terminal on the stowage of containers to be loaded
  • Allocating vessel space by port of discharge
  • Ordering restows during a port call

Where it fits in the message flow

This message MOVINS Stowage instruction
Usually followed by BAPLIE Bayplan/stowage plan occupied and empty locationsCOARRI Container discharge/loading report

Structure

Mandatory segments in MOVINS (directory D.21A)

In UN/EDIFACT directory D.21A, the MOVINS message has 43 segment positions arranged in 13 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
  • SG4 (TDT)
  • SG6 (HAN)
  • UNT

Practical example

MOVINS in practice

Before a vessel calls at Antwerp, the carrier's central planner sends the terminal a MOVINS reserving bays for containers bound for New York and Savannah, with weight limits and reefer plug positions. The terminal plans the loading within those slots, and after departure it sends the final BAPLIE back to the carrier.

Implementation

Implementation considerations for MOVINS

  • Agree with terminals on the level of detail in instructions.
  • Keep MOVINS consistent with the arrival bayplan.
  • Include restow instructions where cargo must be moved.
  • Follow SMDG guidance where partners use it.

How ECOM helps

Automate MOVINS 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 MOVINS?

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

Request a Demo Contact us