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 455 Railroad Parameter Trace Registration

The X12 document a freight carrier uses to register parameters for selecting movement activity from a central data store, or to query past activity.

Sent by
Freight carrier or authorized party
Received by
Central rail data store
Standard
ANSI ASC X12

What is an EDI 455?

The EDI 455 Railroad Parameter Trace Registration is the ANSI X12 transaction set a freight carrier can use to request the establishment of a set of parameters for selecting movement activity from a central data store over time, to request information about past activities within a date range, and to maintain those registrations.

Instead of asking about each car, a party registers a trace, for example all cars of a given owner or all cars moving to a given destination, and receives matching events as they occur.

How the EDI 455 worksDiagram of the EDI 455 Railroad Parameter Trace Registration. Freight carrier or authorized party sends it to central rail data store. It usually starts the exchange. It is usually followed by 451 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BTC (Beginning Segment for Parameter Trace Registration). 1 optional loops are listed by their first segment.How the EDI 455 worksRailroad Parameter Trace Registration: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 455SENDERFreight carrier orauthorized partyRECEIVERCentral rail data store997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY451Railroad Event Report997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code PBGS … GETransaction set 455ST … SEHEADINGBTCBeginning Segment for Parameter Trace Registration+ 1 optional loop, starting with:LXBlue 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 455. Your trading partner's implementation guide adds its own requirements.
How the EDI 455 worksDiagram of the EDI 455 Railroad Parameter Trace Registration. Freight carrier or authorized party sends it to central rail data store. It usually starts the exchange. It is usually followed by 451 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BTC (Beginning Segment for Parameter Trace Registration). 1 optional loops are listed by their first segment.How the EDI 455 worksRailroad Parameter Trace Registration: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 455SENDERFreight carrieror authorizedpartyRECEIVERCentral rail datastore997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY451Railroad Event Report997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code PB (GS … GE)Transaction set 455 (ST … SE)HEADINGBTCBeginning Segment forParameter Trace Registration+ 1 optional loop, starting with:LXBlue 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 455. Your trading partner'simplementation guide adds its own requirements.

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

  • Registering ongoing traces of car movements
  • Requesting historical movement activity
  • Changing or cancelling trace registrations

Where it fits in the document flow

This document 455 Railroad Parameter Trace Registration
Usually followed by 451 Railroad Event Report997 Functional Acknowledgment

Structure

Mandatory segments in the 455 (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
  • BTC
  • LX
  • SE

Practical example

The 455 in practice

A car leasing company wants to follow every car in its fleet across all railroads. It registers a trace with a 455 using its reporting marks as parameters. From then on, events for any of its cars are delivered automatically.

Implementation

Implementation considerations for the 455

  • Define parameters that capture exactly what is needed.
  • Review registrations as fleets and needs change.
  • Plan for the volume of events a trace produces.
  • Check the central system's authorization rules.

How ECOM helps

Automate the 455 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 455?

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

Request a Demo Contact us