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 436 Locomotive Information

The X12 document used to provide rail carriers with locomotive status and location information.

Sent by
Rail carrier or locomotive owner
Received by
Rail carrier
Standard
ANSI ASC X12

What is an EDI 436?

The EDI 436 Locomotive Information is the ANSI X12 transaction set that provides rail carriers with locomotive status and location information.

Railroads share and lease locomotives, and run trains with power from other carriers. Knowing where each locomotive is and whether it is in service, stored or under repair helps railroads balance power across their networks and settle locomotive usage. Status values distinguish locomotives in service, stored, under repair or in transit, and reports include the location and time of each change.

How the EDI 436 worksDiagram of the EDI 436 Locomotive Information. Rail carrier or locomotive owner sends it to rail carrier. 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: LFI (Beginning Segment for Locomotive Information) and N7 (Equipment Details). 0 optional loops are listed by their first segment.How the EDI 436 worksLocomotive Information: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 436SENDERRail carrier orlocomotive ownerRECEIVERRail carrier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code LIGS … GETransaction set 436ST … SEHEADINGLFIBeginning Segment for Locomotive InformationN7Equipment DetailsBlue 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 436. Your trading partner's implementation guide adds its own requirements.
How the EDI 436 worksDiagram of the EDI 436 Locomotive Information. Rail carrier or locomotive owner sends it to rail carrier. 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: LFI (Beginning Segment for Locomotive Information) and N7 (Equipment Details). 0 optional loops are listed by their first segment.How the EDI 436 worksLocomotive Information: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 436SENDERRail carrier orlocomotiveownerRECEIVERRail carrier997 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 LI (GS … GE)Transaction set 436 (ST … SE)HEADINGLFIBeginning Segment forLocomotive InformationN7Equipment DetailsBlue 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 436. Your trading partner'simplementation guide adds its own requirements.

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

  • Reporting the location of foreign locomotives
  • Reporting locomotive status changes
  • Supporting locomotive balancing and settlement

Where it fits in the document flow

This document 436 Locomotive Information
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 436 (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
  • LFI
  • N7
  • SE

Practical example

The 436 in practice

A railroad uses locomotives from a connecting carrier on run-through trains. It reports each foreign locomotive's location and status with the 436 as trains move. The owning railroad tracks its fleet and plans when to recover the units.

Implementation

Implementation considerations for the 436

  • Identify locomotives by their reporting marks and numbers.
  • Report locomotive status changes promptly.
  • Reconcile usage with locomotive settlement agreements.
  • Agree reporting points with partner railroads.

How ECOM helps

Automate the 436 with ECOM

Industry

Trucking and Transportation

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

Solution

Supply Chain Visibility

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

Solution

EDI Integration

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

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

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

Request a Demo Contact us