EDI 418 Rail Advance Consist for Interchange and Yard Planning
For edi and integration analysts, it leads at shippers, 3pls and carriers · Understand the problem

EDI 418 Rail Advance Consist for Interchange and Yard Planning: Illustrative TMS–ERP order and invoice handoff review beside a warehouse floor; not a client facility.
Quick answer: edi 418 rail advance interchange consist
The X12 418 Rail Advance Interchange Consist gives a connecting railroad advance details of cars it will receive: a BAX header with location, consist type and train identity, W1 blocks, W2 car records with reporting mark, number, commodity code and load status, and hazardous material loops. AAR Circular OT-56 requires sending it with or before physical interchange.
TL;DR — what you’ll learn
- BAX02 carries the consist type; AAR Circular OT-56 maps ten business arrangements to codes, including T for a normal train, J for trackage rights or haulage and Y for actual interchange.
- Under OT-56, a 418-J with hazardous material must reach the host before the train arrives, and any change to hazmat shipment, placement or identification must be retransmitted.
- A receiving system can test every placarded car against 49 CFR 174.85, such as the sixth-car rule and the ban on different placard groups standing next to each other.
- In the illustrative yard example, planning from a stale consist cost $1,050 in re-switching and delay, against $126 when the corrected 418 arrived first.
Topics: edi 418 rail advance interchange consist · consist order · placarded car placement · BAX02 type of consist code · 49 CFR 174.85 position in train
All quantities, amounts, product codes and events are illustrative teaching examples.
A train arrives at an interchange yard before dawn. The receiving railroad's yard plan was built at midnight from the advance consist, with each block assigned a track and the two placarded tank cars set to move on the morning's outbound train. At inbound inspection the car inspector finds a different train: a bad-order car set out en route, two extra tank cars picked up at an intermediate yard, and a poison gas tank car coupled directly behind a flammable liquid tank car.
The delivering railroad had changed the consist without resending it. Every decision downstream, from track assignment to crew calls to the hazardous material position check, was made on stale data. The X12 418 Rail Advance Interchange Consist exists to prevent exactly this, and the industry circular that governs it sets a timing rule and a retransmission rule that a receiving system can enforce automatically.
- What this guide covers: what a 418 carries, the BAX consist type codes, the W1 and W2 car records, the hazardous material loops, and the timing and resend duties in AAR Circular OT-56.
- What it adds: a placement check against 49 CFR 174.85, yard planning uses, a timestamped incident, worked costs in USD and INR, India's rake formation practice and a partner onboarding checklist.
What the 418 tells a connecting railroad before cars arrive
The 418 is a railroad-to-railroad notice of equipment about to change hands. X12 describes it as transmitting advance information on equipment being interchanged to a connecting rail carrier, and also allows it to come from a consignor or go to a consignee.
Most shippers never see one. The senders and receivers are Class I railroads, regional and short line railroads, terminal and switching carriers, and tenant railroads running over a host's track. A large plant with its own rail operation, or a terminal operator switching cars for a railroad, may receive 418s under an agreement. The 418 sits beside related rail sets in the X12 catalogue: 404 Rail Carrier Shipment Information, 417 Rail Carrier Waybill Interchange and 410 Rail Carrier Freight Details and Invoice.
The governing industry rule is short. AAR Circular OT-56, published through Railinc, directs tenant railroads to use the appropriate consist code and the 418, unless host and tenant agree otherwise, and states that under Car Service Rule 7 railroads shall transmit the appropriate 418 with or in advance of the physical movement of equipment from one carrier to another. The copy hosted by Railinc carries an effective date of 6 April 2026.
BAX consist type codes and the business arrangement each signals
The second element of the BAX header, BAX02, tells the receiver why the consist is being sent. OT-56 maps each business arrangement between railroads to a code, and the code drives what the receiver does with the message.
Scroll horizontally to see all columns.
| OT-56 business arrangement | BAX02 code | What the receiving railroad does with it |
|---|---|---|
| Trackage rights or haulage | J (joint track) | Host checks the tenant train's hazardous cars before it enters host track |
| Temporary detour | D | Host plans a foreign train over its line for the detour period |
| Advanced automatic equipment identification consist | A | Matches the list with tag reads from a wayside reader |
| Bad order | B | Routes the car to inspection or repair track |
| Information only advanced consist | L | Updates visibility without triggering interchange accounting |
| Passing | P | Records cars passing through without being set out |
| Release from bad order | R | Returns a repaired car to service in the yard plan |
| Switch | S | Plans switching moves for cars exchanged in a yard |
| Train (normal) | T | Builds the receiving yard plan for an arriving train |
| Actual interchange | Y | Confirms that the cars physically changed hands |
The X12 code list for element 579 in release 008040 also contains C (crew only), I (inspection) and O (liability transfer to a delinquent road under Car Hire Rule 15). A receiving system should reject a code it has not agreed with the sender, rather than guess its meaning.
The EDI 418 Rail Advance Interchange Consist identifies its purpose in BAX02, and AAR Circular OT-56 maps ten railroad arrangements to codes such as T for a normal train and J for trackage rights; under Car Service Rule 7 the message must be sent with or before the physical interchange.
Reading the segments: BAX header, W1 blocks and W2 car records
A 418 is a header followed by blocks of cars, each car carrying its own identity, commodity, status and optional hazardous material detail. In release 008040, up to 30 W1 blocks can each hold up to 800 W2 car loops.
- BAX header: BAX01 Standard Point Location Code, BAX02 type of consist, BAX03 to BAX05 a date and time with its qualifier, BAX06 interchange train identification, then optional elements for a second location, a reference number (the reader identification for tag-based consists), direction, the date and time the last car passed the reader, time zone, purpose and service level.
- NM1 loop: optional named parties with addresses and references, repeated up to 999 times.
- W1 block identification: one element, the block identifier, which groups cars destined for the same classification or the same onward train.
- W2 equipment identification: equipment initial and number (the reporting mark and car number), commodity code using STCC, equipment description code, equipment status code and net tons, with optional elements for chassis, check digit, car type, repair need, tag status and orientation.
- Per-car detail: W3 consignee, IMA interchange move authority, W4 consignor, W5 carrier and route, W6 special handling, PS protective service and REF references.
- SE trailer: segment count and control number, closing the transaction set.
Equipment status, W2-05, is the field most yard plans depend on. Its code list includes L for load, E for empty, W for revenue empty, LI and LO for loaded inbound and outbound, and D and O for deadhead and operating locomotives. Loads and empties go to different tracks, and an operating locomotive in the consist tells the receiver where an engine stands for the placement check later in this guide.
One field is missing that many integrators assume exists. The W2-14 Position element describes where a shipment sits inside a car, trailer or container, not where the car stands in the train. If your yard logic needs standing order from the head end, confirm in the sender's implementation guide that W2 loops are sent in train order, and test it with a known consist before relying on it.
Hazardous material loops and why retransmission is mandatory
Each W2 car can carry a loop of hazardous material segments, and OT-56 treats that loop as the reason the 418 exists. The circular sets two duties beyond the general timing rule: send hazmat detail before the train arrives on foreign track, and resend whenever it changes.
In release 008040 the loop opens with LS and closes with LE. Inside it, LH1 carries hazardous identification and can repeat up to 1,000 times per car, followed by LH2 classification, LH3 shipping name, LFH free-form information, LEP EPA-required data, LH4 Canadian dangerous goods requirements, LHT transborder requirements, LHR identifying reference numbers, PER contacts and an N1 party loop.
- Joint track hazmat: for a 418-J, OT-56 requires all available hazardous material details, transmitted to the host before the train arrives on the foreign track.
- Real-time changes: changes to the consist must reach the host before train movement.
- Resend triggers: retransmission is required whenever the hazardous material shipment, its placement or its regulatory identification changes.
- Crew paperwork: 49 CFR 174.26 separately requires the train crew to hold a paper consist showing the position in the train and contents of each hazardous material car, updated at intermediate stops.
- Electronic consist: 49 CFR 174.28, added by the June 2024 final rule at 89 FR 52993, requires railroads to keep that consist electronically, off the train, and make it available to emergency responders.
Checking placarded car placement against 49 CFR 174.85
A receiving railroad can run the federal train-position rules on every 418 before the train arrives. The rules depend on each car's placard group, whether it is a tank car, its distance from an engine or occupied caboose, and what stands next to it, and the 418 supplies enough of that to flag most problems.
Section 174.85 sorts placarded cars into four groups. Group 1 is Divisions 1.1 and 1.2 explosives. Group 2 covers Divisions 1.3 to 1.5, most Class 2 gases, Classes 3, 4, 5 and 8, and Class 6 liquids other than Division 6.1 Packing Group I Zone A. Group 3 is Division 2.3 Zone A gases and Division 6.1 PG I Zone A liquids. Group 4 is Class 7 radioactive material.
Scroll horizontally to see all columns.
| Restriction in 174.85(d) | Applies to | 418 data needed to test it |
|---|---|---|
| 1. Not nearer than the sixth car from the engine or occupied caboose, when train length permits | Group 1 cars, Group 2 tank cars, Group 3 tank cars | Car sequence, locomotive status codes, hazard class and zone |
| 2. If length does not permit, near the middle but not nearer than the second car | Same cars as restriction 1 | Car count and sequence |
| 3. Not next to an open-top car whose lading protrudes, or could shift to protrude, beyond the car ends | Same cars as restriction 1 | Car type of each neighbour; lading detail usually needs the waybill |
| 4. Not next to a loaded flat car, except closed TOFC/COFC, auto carriers and cars with vehicle tie-downs | Same cars as restriction 1 | Neighbour equipment description and load status |
| 5. Not next to a vehicle or container with an engine or open flame running | Same cars as restriction 1 | Special handling or protective service segments |
| 6. Placarded cars of different placard groups not next to each other | All four groups | Placard group of both neighbours |
| 174.85(b) and (c): radioactive car one non-placarded car from engine or caboose; residue tank car one car other than a placarded tank car | Group 4 cars and tank cars with residue | Status codes and hazmat loop |
The 418 does not carry a placard group. The receiving system must derive it from the class, division, packing group and hazard zone in the LH segments, using a fixed lookup reviewed by the railroad's hazardous materials officer. The check below assumes the W2 loops arrive in train order and treats every operating locomotive as an engine, the cautious reading.
# 174.85 placement check over a parsed 418 (cars in train order, index 1..N)
# grp[i] : placard group 1-4, or 0 if not placarded
# tank[i] : True if tank car; loco[i] : True if W2-05 = "O"
# risky[i] : grp[i] == 1 or (grp[i] in (2, 3) and tank[i])
for i in 1..N:
if grp[i] == 0: continue
d = min(|i - j| for j where loco[j]) # cars from nearest engine
if risky[i] and length_permits and d < 6:
flag(i, "174.85(d) row 1: nearer than sixth car")
if risky[i] and not length_permits and d < 2:
flag(i, "174.85(d) row 2: nearer than second car")
for k in (i - 1, i + 1):
if risky[i] and loaded_flat_not_exempt(k):
flag(i, "174.85(d) row 4: next to loaded flat car")
if grp[k] != 0 and grp[k] != grp[i]:
flag(i, "174.85(d) row 6: different placard groups adjacent")
if grp[i] == 4 and d < 2:
flag(i, "174.85(b): radioactive car needs one non-placarded car")
# length_permits is a trainmaster decision, not a computed value
A receiving railroad's yard system can test every placarded car in an EDI 418 against 49 CFR 174.85(d), flagging Group 1 cars and Group 2 or 3 tank cars nearer than the sixth car from an engine and any two cars of different placard groups coupled together, before a train is accepted.
Using the advance consist to plan the receiving yard
The 418's commercial value is time: a yard that knows what is coming can assign tracks, crews and inspections before the train stops. Each W1 block maps to a classification decision, and each W2 status code tells the yard whether the car goes to a departure track, a storage track or the repair track.
- Block to track: W1 block identifiers let the yardmaster assign receiving and classification tracks before arrival, so the switch crew's first move is planned rather than discovered.
- Load and empty split: W2-05 separates loads for onward trains from empties returning to car owners or storage.
- Bad-order cars: a B consist code or a W2-16 repair flag sends the car to the repair track instead of a departure track.
- Switching limits: 49 CFR 174.83 bars certain placarded cars from being cut off while in motion or struck by cars moving under their own momentum, including loaded Division 1.1 and 1.2 cars, Division 2.3 Zone A and Division 6.1 PG I Zone A cars, and DOT 113 tank cars placarded Division 2.1. Flagging them in the plan keeps them out of free-rolling moves.
- Protective service: PS segments tell the yard which cars need heating, cooling or other attention while they wait.
Acknowledge every 418 with a 997 so the sender knows the consist was received and parsed. Our guide to EDI 997 functional acknowledgments covers how to watch for missing acknowledgments; a consist with no acknowledgment should prompt a phone call before the train arrives, not after.
Incident trace: a late consist change and a misplaced tank car
The opening scenario followed a predictable sequence. Every step had a record that could have stopped it, and the failure was that the consist change never reached the receiving railroad as a resent 418.
- 00:10, consist sent: the delivering railroad transmits a 418-T for train M412 with 58 cars in three W1 blocks; the receiver returns a 997 at 00:11 and its yard system passes the placement check.
- 00:40, yard plan built: the receiving yardmaster assigns block B1 to track 7 and block B2, which holds placarded tank cars ABCX 100245 (Group 2) and ABCX 100318 (Group 2), to track 9 for the 08:00 outbound.
- 03:25, consist changes en route: at an intermediate yard the delivering crew sets out a bad-order covered hopper and picks up tank cars ABCX 200511 (Group 3, Division 2.3 Zone A) and ABCX 200634 (Group 2). The paper consist is updated under 174.26, but no new 418 is sent.
- 05:50, inspection finds a different train: arriving with 59 cars, M412 shows ABCX 200511 coupled directly to ABCX 200634, a Group 3 and Group 2 pair that 174.85(d) row 6 prohibits.
- 06:05 to 09:00, recovery: the yardmaster holds block B2, a switch crew separates the pair with a non-placarded car, the yard plan is rebuilt by hand, the corrected 418 arrives at 07:40, and the outbound leaves 60 minutes late.
Two controls would have caught the change before arrival. The sender's system should resend whenever a hazmat car is added, as OT-56 requires. The receiver's system should compare the car count and hazmat car list in the 418 with the arrival tag reads from the last wayside reader, and alert the yardmaster when they differ.
What a stale consist costs in dollars and rupees
The cost of a stale or missing consist is mostly unplanned crew time and delay, small per train but repeated across every interchange. The figures below are illustrative rates, not tariffs; replace them with your own crew, locomotive and wagon-hour costs.
Scroll horizontally to see all columns.
| Cost line | US interchange: stale 418 | US interchange: corrected 418 before arrival | India siding: wagon list error | India siding: list checked before release |
|---|---|---|---|---|
| Unplanned switching | 1.5 h x $420 = $630 | 0.3 h x $420 = $126 (planned move) | Not applicable | Not applicable |
| Extra inspection or tally recheck | 2 h x $60 = $120 | Nil | 4 staff x 3 h x ₹250 = ₹3,000 | Nil |
| Delay to train or rake release | 1 h x $300 = $300 | Nil | 42 wagons x 3 h x ₹100 = ₹12,600 | Nil |
| Total per event | $1,050 | $126 | ₹15,600 | Nil |
At one such event a week, the US difference of $924 per event is about $48,000 a year at a single interchange point. The India column describes a different failure, explained in the next section: there is no carrier-to-carrier consist message for a siding operator to receive, so the cost comes from the siding's own wagon list not matching the railway's documents.
India: rake formation at sidings without an X12 418
We found no X12 418 exchange on Indian Railways. Wagon and rake movement data sit in the Freight Operations Information System (FOIS), and a siding operator's consist discipline is about recording wagons in rake order and matching them to the railway's documents.
The FOIS portal describes the system as tracking wagons, locomotives and trains, generating the Railway Receipt and integrating with major customers' legacy systems. For a private siding loading a rake, the working record is the siding's own loading tally: each wagon number in the order placed, its load, seal numbers and loading time. That tally must match the wagon list the railway uses for the Railway Receipt, or release is held while the mismatch is corrected.
- Rake order tally: record wagon numbers in placement order as each wagon is placed, not from memory after loading.
- Document match: compare the tally with the railway's wagon list before requesting release, so a keying error is fixed while the rake is still within free time.
- Dangerous goods: rail carriage of dangerous goods follows the Railways Red Tariff Rules, 2000, made under Sections 67 and 87 of the Railways Act, 1989, most recently amended by notification G.S.R. 770(E) of 21 October 2025; marshalling instructions come from the railway, so take them from your zonal railway's current instructions.
- Demand to receipt: the commercial chain from rake demand to Railway Receipt is covered in our guide to linking rail demand, allotment and railway receipts.
Rake formation at Indian private sidings has no X12 418 counterpart; the siding's loading tally of wagon numbers in placement order must match the FOIS wagon list behind the Railway Receipt, and dangerous goods wagons follow the Railways Red Tariff Rules, 2000, amended most recently by G.S.R. 770(E) on 21 October 2025.
Validation rules, ownership and an onboarding checklist for 418 feeds
A 418 feed is only as reliable as its owners and its validation rules. Assign each record to a named team, automate the checks that are pure rules, and keep the judgement calls with the yardmaster and the hazardous materials officer.
Scroll horizontally to see all columns.
| Record | Held in | Owner | Approves corrections |
|---|---|---|---|
| Train make-up and car sequence | Delivering railroad's transportation system | Delivering road's yardmaster or train dispatcher | Delivering road's terminal superintendent |
| Hazardous material description per car | Shipper's shipping papers and the waybill carried in the 417 | Shipper, then originating railroad | Originating railroad's hazardous materials desk |
| 418 mapping, codes and resend logic | Sender's EDI translator and map | Sender's EDI analyst | Sender's EDI manager |
| Receiving yard plan | Receiving railroad's yard system | Receiving yardmaster | Receiving trainmaster |
| Placard group lookup table | Receiving railroad's reference data | Hazardous materials officer | Hazardous materials officer |
Scroll horizontally to see all columns.
| Task | Handled by | Rule | Decided by |
|---|---|---|---|
| Rejecting an unagreed BAX02 consist code | Fixed rule in the translator | Code must be on the partner's agreed list | Nobody; message returned |
| Deriving placard group from LH class, division and zone | Fixed lookup | Group definitions in 174.85 | Hazmat officer maintains the table |
| Running position and adjacency checks | Fixed rule | 174.85(b), (c) and (d) | Yardmaster clears each flag |
| Comparing the consist with wayside tag reads | Software match | Car count and every hazmat car must match | Yardmaster on any difference |
| Reading a tenant crew's photographed handwritten switch list | Software suggests car numbers | Each number shown beside the image | Clerk confirms every number |
| Deciding whether train length permits sixth-car placement | Person | 174.85(d) rows 1 and 2 | Trainmaster |
Scroll horizontally to see all columns.
| Item | What to agree | How to test it |
|---|---|---|
| X12 release | The release and the partner's implementation guide | Parse three sample consists without errors |
| Consist codes | Which BAX02 codes each side sends | One test message per agreed code |
| Timing | Lead time before arrival, at least with the movement under Car Service Rule 7 | Compare message time with arrival time over two weeks |
| Resend triggers | Hazmat shipment, placement or identification changes | Add a hazmat car to a test train and confirm a resend |
| Train order | Whether W2 loops follow standing order from the head end | Check one consist against a physical walk of the train |
| Acknowledgment | 997 returned within an agreed number of minutes | Alert when no 997 arrives |
| Location codes | SPLC values for each interchange point | Reject unknown codes in testing |
For broader context on rail and multimodal planning, see our logistics and supply chain hub. If you are scoping a consist validation or yard planning integration, outline the partners and message volumes in our request for proposal form.
Discuss this workflow
Describe your current systems, the recurring exception and the outcome you need. Keep shipment, customer and financial records out of the initial message.
Common operational questions
Practical answers for operations, engineering, and finance teams working on edi 418 rail advance interchange consist in logistics & supply chain.
Who sends and receives an EDI 418?
When must a 418 be transmitted?
Does the 418 show each car's position in the train?
Is there an Indian equivalent of the X12 418?
References
Sources checked 13 November 2026. US and India statutory authorities and vendor documentation support platform facts; the worked examples and diagrams are original.
- ASC X12 - Transaction set listing: 418 Rail Advance Interchange Consist (with 404, 410 and 417)Official transaction set names and the 418 purpose statement. Accessed 13 November 2026.
- Association of American Railroads, via Railinc - Circular No. OT-56, Compliance with EDI Requirements Pertaining to Advanced Interline Consist TransmissionConsist codes by business arrangement, Car Service Rule 7 timing, and hazardous material retransmission rules. The hosted copy is dated 16 July 2018 and shows an effective date of 6 April 2026. Accessed 13 November 2026.
- Stedi - X12 release 008040, 418 segment list and BAX, W1, W2 element definitionsSecondary reference used because the X12 standard text is licensed; segment order, loop repeats, element names and code lists (elements 578 and 579) were read from this published dictionary. Accessed 13 November 2026.
- eCFR - 49 CFR 174.85 Position in train of placarded cars, transport vehicles, freight containers, and bulk packagingsRestrictions 1 to 6, the placard group definitions and paragraphs (b) and (c). Text read through the eCFR versioner API. Accessed 13 November 2026.
- eCFR - 49 CFR 174.26 Notice to train crews, and 174.28 Electronic train consist informationHard-copy consist with position of each hazardous material car, updates at intermediate stops, and the electronic consist duty added at 89 FR 52993 (24 June 2024). Accessed 13 November 2026.
- eCFR - 49 CFR 174.83 Switching placarded rail cars, transport vehicles, freight containers, and bulk packagingsCars that may not be cut off while in motion or struck by cars moving under their own momentum. Accessed 13 November 2026.
- Gazette of India - Ministry of Railways notification G.S.R. 770(E), Railways Red Tariff (Second Amendment) Rules, 2025, 21 October 2025Confirms the Railways Red Tariff Rules, 2000 (G.S.R. 266, 15 July 2000) made under Sections 67 and 87 of the Railways Act, 1989, and the latest amendment. Accessed 13 November 2026.
- CRIS / Indian Railways - About FOIS (Freight Operations Information System)Describes FOIS tracking of wagons, locomotives and trains, Railway Receipt generation and integration with major customers' systems. Accessed 13 November 2026.
- FMCSA — 49 CFR Part 395 Hours of Service & Electronic Logging Devices (ELD)US federal motor carrier dispatch and driver duty-status compliance mandate.
- ULIP & NIC GST E-Way Bill Portal — Unified Logistics & Rule 138 ComplianceIndian statutory goods-in-transit and multi-modal logistics verification framework.