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 · Government and regulatory

EDI 284 Commercial Vehicle Safety Reports

The bi-directional X12 document authorized parties use to request and send reports on the safe operation of commercial road vehicles.

Sent by
Enforcement agency, carrier or authorized party
Received by
Agency, carrier or authorized party
Standard
ANSI ASC X12

What is an EDI 284?

The EDI 284 Commercial Vehicle Safety Reports is the bi-directional ANSI X12 transaction set authorized parties can use to request and send reports on information related to the safe operation of commercial road vehicles, such as inspection and crash reports.

Roadside inspections, crashes and violations feed carriers' safety records, which regulators use to target enforcement and shippers use to select carriers. Electronic exchange gets reports into safety databases quickly and lets carriers see and correct their records. Carriers can review their records.

How the EDI 284 worksDiagram of the EDI 284 Commercial Vehicle Safety Reports. Enforcement agency, carrier or authorized party sends it to agency, carrier or authorized party. 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: BGN (Beginning Segment) and detail: the required HL loop with HL (Hierarchical Level). 4 optional loops are listed by their first segment.How the EDI 284 worksCommercial Vehicle Safety Reports: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 284SENDEREnforcement agency,carrier or authorizedpartyRECEIVERAgency, carrier orauthorized party997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code IHGS … GETransaction set 284ST … SEHEADINGBGNBeginning Segment+ 1 optional loop, starting with:NM1DETAILRequired loop HL · repeats many timesHLHierarchical Level+ 3 optional loops, starting with:LQNM1MTXBlue 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 284. Your trading partner's implementation guide adds its own requirements.
How the EDI 284 worksDiagram of the EDI 284 Commercial Vehicle Safety Reports. Enforcement agency, carrier or authorized party sends it to agency, carrier or authorized party. 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: BGN (Beginning Segment) and detail: the required HL loop with HL (Hierarchical Level). 4 optional loops are listed by their first segment.How the EDI 284 worksCommercial Vehicle Safety Reports: who sendsit, where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 284SENDEREnforcementagency, carrieror authorizedpartyRECEIVERAgency, carrieror authorizedparty997 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 IH (GS … GE)Transaction set 284 (ST … SE)HEADINGBGNBeginning Segment+ 1 optional loop, starting with:NM1DETAILRequired loop HL · repeats manytimesHLHierarchical Level+ 3 optional loops, starting with:LQNM1MTXBlue 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 284. Your trading partner'simplementation guide adds its own requirements.

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

  • Sending roadside inspection reports
  • Requesting a carrier's safety reports
  • Exchanging crash report data

Where it fits in the document flow

This document 284 Commercial Vehicle Safety Reports
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 284 (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
  • BGN
  • NM1
  • HL
  • LQ
  • AMT
  • LIE
  • MTX
  • SE

Practical example

The 284 in practice

An inspector performs a roadside inspection on a truck and finds a brake defect. The inspection report is transmitted to the national safety database, and the carrier later requests its recent inspection reports to review defects across its fleet.

Implementation

Implementation considerations for the 284

  • Follow the regulator's current data systems and formats.
  • Identify carriers and vehicles with official identifiers.
  • Protect drivers' personal data under applicable law.
  • Review reports and request corrections where needed.

How ECOM helps

Automate the 284 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 government and regulatory documents

All 29 government and regulatory documents

Need help with the EDI 284?

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

Request a Demo Contact us