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 179 Environmental Compliance Reporting

The X12 document commercial and public facilities use to submit environmental compliance reports to federal, state and local agencies.

Sent by
Commercial or public facility
Received by
Environmental protection agency
Standard
ANSI ASC X12

What is an EDI 179?

The EDI 179 Environmental Compliance Reporting is the ANSI X12 transaction set commercial and public facilities can use to submit environmental compliance reports to the Environmental Protection Agency and to state and local environmental agencies.

Facilities report emissions, discharges, waste and other monitoring data under their permits. Electronic reporting replaces paper forms and lets agencies analyze compliance data more quickly. Agencies now operate their own electronic reporting systems, so the formats accepted should be confirmed with each. Data must be certified by the facility.

How the EDI 179 worksDiagram of the EDI 179 Environmental Compliance Reporting. Commercial or public facility sends it to environmental protection agency. 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 the required NM1 loop with NM1 (Individual or Organizational Name) and detail: the required HL loop with HL (Hierarchical Level). 8 optional loops are listed by their first segment.How the EDI 179 worksEnvironmental Compliance Reporting: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 179SENDERCommercial or publicfacilityRECEIVEREnvironmentalprotection agency997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code EPGS … GETransaction set 179ST … SEHEADINGBGNBeginning SegmentRequired loop NM1 · repeats many timesNM1Individual or Organizational Name+ 4 optional loops, starting with:LMQTYOOIDETAILRequired loop HL · repeats many timesHLHierarchical Level+ 4 optional loops, starting with:NM1LMN9OOIBlue 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 179. Your trading partner's implementation guide adds its own requirements.
How the EDI 179 worksDiagram of the EDI 179 Environmental Compliance Reporting. Commercial or public facility sends it to environmental protection agency. 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 the required NM1 loop with NM1 (Individual or Organizational Name) and detail: the required HL loop with HL (Hierarchical Level). 8 optional loops are listed by their first segment.How the EDI 179 worksEnvironmental Compliance Reporting: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 179SENDERCommercial orpublic facilityRECEIVEREnvironmentalprotectionagency997 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 EP (GS … GE)Transaction set 179 (ST … SE)HEADINGBGNBeginning SegmentRequired loop NM1 · repeatsmany timesNM1Individual orOrganizational Name+ 4 optional loops, starting with:LMQTYOOIDETAILRequired loop HL · repeats manytimesHLHierarchical Level+ 4 optional loops, starting with:NM1LMN9OOIBlue 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 179. Your trading partner'simplementation guide adds its own requirements.

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

  • Submitting discharge monitoring reports
  • Reporting emissions under permits
  • Submitting periodic compliance reports

Where it fits in the document flow

This document 179 Environmental Compliance Reporting
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 179 (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
  • LM
  • LQ
  • NM1
  • QTY
  • OOI
  • HL
  • III
  • N9
  • SE

Practical example

The 179 in practice

A chemical plant must report wastewater discharge monitoring results monthly under its permit. Its environmental management system sends the agency the measured values for each parameter and outfall. The agency checks them against permit limits.

Implementation

Implementation considerations for the 179

  • Confirm the reporting format each agency accepts.
  • Validate data against permit limits before submission.
  • Meet the reporting deadlines in each permit.
  • Keep certified records available for inspections.

How ECOM helps

Automate the 179 with ECOM

Industry

Manufacturing

Customer schedules, supplier connectivity and shipping integrated with the ERP for manufacturers.

Solution

Enterprise Integration

Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.

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

All 29 government and regulatory documents

Need help with the EDI 179?

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

Request a Demo Contact us