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

X12 transaction guide · Transportation

EDI 715 Intermodal Group Loading Plan

The X12 document intermodal shippers and carriers use to share detailed stowage of containers and other equipment on rail cars.

Sent by
Intermodal shipper, carrier or ramp operator
Received by
Rail carrier, terminal or other party
Standard
ANSI ASC X12

What is an EDI 715?

The EDI 715 Intermodal Group Loading Plan is the ANSI X12 transaction set intermodal and domestic shippers and carriers use to provide detailed information on the stowage of containers and other equipment on rail cars, such as which container goes on which well of a double-stack car.

Loading plans affect safety and efficiency: weight distribution and car capacity limits must be respected, and ramps need the plan to load trains quickly. Sharing it electronically helps ramps and railroads build trains without rekeying.

How the EDI 715 worksDiagram of the EDI 715 Intermodal Group Loading Plan. Intermodal shipper, carrier or ramp operator sends it to rail carrier, terminal or other party. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), GR2 (Train Data) and the required GR4 loop with GR4 (Loading Cluster). 1 optional loops are listed by their first segment.How the EDI 715 worksIntermodal Group Loading Plan: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 715SENDERIntermodal shipper,carrier or rampoperatorRECEIVERRail carrier, terminalor other party997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code GLGS … GETransaction set 715ST … SEHEADINGBGNBeginning SegmentGR2Train DataRequired loop GR4 · repeats up to 100GR4Loading Cluster+ 1 optional loop, starting with:N7Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 715. Your trading partner's implementation guide adds its own requirements.
How the EDI 715 worksDiagram of the EDI 715 Intermodal Group Loading Plan. Intermodal shipper, carrier or ramp operator sends it to rail carrier, terminal or other party. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), GR2 (Train Data) and the required GR4 loop with GR4 (Loading Cluster). 1 optional loops are listed by their first segment.How the EDI 715 worksIntermodal Group Loading Plan: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 715SENDERIntermodalshipper, carrieror ramp operatorRECEIVERRail carrier,terminal or otherparty997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code GL (GS … GE)Transaction set 715 (ST … SE)HEADINGBGNBeginning SegmentGR2Train DataRequired loop GR4 · repeats up to100GR4Loading Cluster+ 1 optional loop, starting with:N7Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 715. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 715, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 715 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Planning the loading of containers on rail cars
  • Sharing stowage positions with ramps and railroads
  • Updating plans after changes at the ramp

Where it fits in the document flow

This document 715 Intermodal Group Loading Plan
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 715 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BGN
  • GR2
  • GR4
  • N7
  • SE

Practical example

The 715 in practice

An intermodal marketing company has 120 containers to move from a ramp in Los Angeles to Chicago. It sends the railroad a 715 assigning each container to a car and position, with weights, so heavier boxes sit in the bottom wells. The ramp loads the train to the plan, and the railroad uses it to check car weight limits.

Implementation

Implementation considerations for the 715

  • Respect car capacity and weight distribution rules in the plan.
  • Identify cars and containers by their reporting marks and numbers.
  • Send updates when equipment or positions change.
  • Align the plan with waybills and other shipment data.

How ECOM helps

Automate the 715 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.

Industry

3PL and Warehousing

Warehouse orders, shipping advice, receipts and inventory reporting between brands, 3PLs, carriers and retailers.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related transportation documents

All 80 transportation documents

Need help with the EDI 715?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us