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 161 Train Sheet

The X12 document railroads use to exchange train sheet information so crews operating on other railroads know current operating conditions.

Sent by
Rail carrier
Received by
Rail carrier whose crews or trains operate on the sender's lines
Standard
ANSI ASC X12

What is an EDI 161?

The EDI 161 Train Sheet is the ANSI X12 transaction set that lets railroads exchange train sheet information and ensures that crews operating equipment on other railroads are aware of current operating conditions.

Trains often run over several railroads' tracks under trackage rights. A train sheet records a train's movement, crews and conditions, and sharing it keeps each railroad informed about trains on its lines and about conditions its crews will meet elsewhere. It supports safe joint operations. It covers run-through trains too.

How the EDI 161 worksDiagram of the EDI 161 Train Sheet. Rail carrier sends it to rail carrier whose crews or trains operate on the sender's lines. 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: BTS (Beginning Segment for Train Sheets) and V9 (Event Detail). 1 optional loops are listed by their first segment.How the EDI 161 worksTrain Sheet: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 161SENDERRail carrierRECEIVERRail carrier whosecrews or trainsoperate on thesender's lines997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code TRGS … GETransaction set 161ST … SEHEADINGBTSBeginning Segment for Train SheetsV9Event Detail+ 1 optional loop, starting with:NM1Blue 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 161. Your trading partner's implementation guide adds its own requirements.
How the EDI 161 worksDiagram of the EDI 161 Train Sheet. Rail carrier sends it to rail carrier whose crews or trains operate on the sender's lines. 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: BTS (Beginning Segment for Train Sheets) and V9 (Event Detail). 1 optional loops are listed by their first segment.How the EDI 161 worksTrain Sheet: who sends it, where it fits andwhat the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 161SENDERRail carrierRECEIVERRail carrierwhose crews ortrains operateon the sender'slines997 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 TR (GS … GE)Transaction set 161 (ST … SE)HEADINGBTSBeginning Segment for TrainSheetsV9Event Detail+ 1 optional loop, starting with:NM1Blue 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 161. Your trading partner'simplementation guide adds its own requirements.

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

  • Sharing train movement records between railroads
  • Informing crews of operating conditions
  • Supporting trackage rights operations

Where it fits in the document flow

This document 161 Train Sheet
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 161 (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
  • BTS
  • V9
  • NM1
  • SE

Practical example

The 161 in practice

A railroad runs trains over a partner's line under trackage rights. The partner sends it 161 train sheet data on its trains' movements and the conditions on the line, such as speed restrictions. The railroad's dispatchers and crews plan their operations with current information.

Implementation

Implementation considerations for the 161

  • Share updates as operating conditions change.
  • Identify trains consistently between railroads.
  • Route safety-relevant information to operations staff.
  • Agree which operating details are exchanged.

How ECOM helps

Automate the 161 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

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

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 161?

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

Request a Demo Contact us