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 · Communications

EDI 620 Excavation Communication

The X12 document used to communicate about excavations, to obtain clearance or have affected parties locate and mark their assets.

Sent by
Excavator or one-call center
Received by
Utility operators and other affected parties
Standard
ANSI ASC X12

What is an EDI 620?

The EDI 620 Excavation Communication is the ANSI X12 transaction set used to communicate information about excavations, either to obtain clearance for the excavation or to have potentially affected parties locate their assets and supervise work near them.

Before digging, excavators must notify the owners of underground facilities, often through a one-call center, so pipes and cables can be marked. Structured notifications let utilities process locate requests automatically and dispatch locators. Responses confirm locates or clearances and close the request, and records of the exchange help establish responsibility if an underground facility is later damaged.

How the EDI 620 worksDiagram of the EDI 620 Excavation Communication. Excavator or one-call center sends it to utility operators and other affected parties. 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 N1 (Party Identification) and detail: the required EXI loop with EXI (Excavation Ticket Information), DTM (Date/Time Reference) and the required N1 loop with N1 (Party Identification). 2 optional loops are listed by their first segment.How the EDI 620 worksExcavation Communication: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 620SENDERExcavator or one-callcenterRECEIVERUtility operators andother affected parties997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code EXGS … GETransaction set 620ST … SEHEADINGBGNBeginning SegmentN1Party IdentificationDETAILRequired loop EXI · repeats many timesEXIExcavation Ticket InformationDTMDate/Time ReferenceRequired loop N1 · repeats many timesN1Party Identification+ 2 optional loops, starting with:LIELMBlue 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 620. Your trading partner's implementation guide adds its own requirements.
How the EDI 620 worksDiagram of the EDI 620 Excavation Communication. Excavator or one-call center sends it to utility operators and other affected parties. 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 N1 (Party Identification) and detail: the required EXI loop with EXI (Excavation Ticket Information), DTM (Date/Time Reference) and the required N1 loop with N1 (Party Identification). 2 optional loops are listed by their first segment.How the EDI 620 worksExcavation Communication: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 620SENDERExcavator orone-call centerRECEIVERUtility operatorsand otheraffected parties997 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 EX (GS … GE)Transaction set 620 (ST … SE)HEADINGBGNBeginning SegmentN1Party IdentificationDETAILRequired loop EXI · repeatsmany timesEXIExcavation TicketInformationDTMDate/Time ReferenceRequired loop N1 · repeatsmany timesN1Party Identification+ 2 optional loops, starting with:LIELMBlue 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 620. Your trading partner'simplementation guide adds its own requirements.

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

  • Notifying utilities of planned excavation
  • Requesting location and marking of underground assets
  • Responding with clearance or locate information

Where it fits in the document flow

This document 620 Excavation Communication
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 620 (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
  • N1
  • EXI
  • DTM
  • LIE
  • PPA
  • LM
  • LQ
  • SE

Practical example

The 620 in practice

A contractor plans to dig a trench for a new water line. The one-call center sends each utility in the area a 620 with the location, dates and type of work. The gas and telecom operators dispatch locators to mark their lines and respond that the area is marked.

Implementation

Implementation considerations for the 620

  • Follow state or national one-call rules and timelines.
  • Describe the excavation area precisely, with maps.
  • Respond to every notification, including no-conflict responses.
  • Keep records of notifications in case of damage claims.

How ECOM helps

Automate the 620 with ECOM

Industry

Telecom and Media

Equipment supply chains, service billing and partner data exchange for telecom and media companies.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

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 communications documents

All 16 communications documents

Need help with the EDI 620?

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

Request a Demo Contact us