ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 452 — Railroad Problem Log Inquiry / Advice

The 452 documents an operational problem reported on a railroad line: track defect, wagon incident, delay, missing manifest — exchange between carriers and infrastructure.

Purpose

The 452 is used on the Class I network to communicate incidents and delays between carriers, infrastructure (track owner) and customers. It carries the incident type, location (subdivision, milepost), train or consist affected, estimated impact, and a description.

It is part of the RailInc EDI program and feeds Operations Centers. Acknowledged by 997, it may be followed by a 214 (Shipment Status) for customer propagation. It is ephemeral by nature — a resolved incident triggers a follow-up 452, not a cancellation.

Envelope structure

The 452 travels within the three X12 envelope levels (ISA/IEA, GS/GE with functional group PL, and ST/SE). Didactic example in release 004010:

x12 example-452.x12 
ISA*00*          *00*          *ZZ*BNSFOPS       *ZZ*UPOPS         *260514*1900*U*00401*000000452*0*P*>~
GS*PL*BNSFOPS*UPOPS*20260514*1900*1*X*004010~
ST*452*0001~
ZD*INQ*PROB-2026-005~
N9*WB*WAYBILL-7780019~
N7*BNSF*7780019*A402~
LX*1~
G62*02*20260514*1*1845~
K1*Track defect on subdivision MP 142.5, eastbound stopped~
NA*HH*1845-2200~
SE*9*0001~
GE*1*1~
IEA*1*000000452~

Common segments

  • Header — ST, ZD (Beginning Segment for Problem Log) qualified INQ (Inquiry) or ADV (Advice).
  • Wagon reference — N7, N9 (waybill).
  • Description — G62*02 (Date Time), K1 (Remarks free-text), NA*HH (impact hours).
  • Incident code — AAR / RailInc code list for the defect nature.
  • Summary — SE.

Common pitfalls

  • Inquiry vs Advice: ZD01 = INQ is a question, ADV is a notification; mixing them up means nobody answers.
  • Operational volume: a major incident generates dozens of 452 (one per affected train); the 452 must have a hub-side TTL, otherwise the log explodes.
  • Geolocation: K1 or NA must carry an MP (Milepost) reference and a standard AAR Subdivision; free-text geography does not map onto the network.

Documentation

The code 452 and the name Railroad Problem Log Inquiry / Advice are public and listed on x12.org/products/transaction-sets. The complete structure of loops, qualifiers and code lists is distributed by DISA via the proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.