Data Exchange Description
The Toxics Release Inventory is an EPA program enacted as part of the Emergency Planning and Community Right to Know Act (EPCRA) of 1986. Every year, tens of thousands of facilities in the United States submit reports to EPA and the States on releases and transfers of certain toxic chemicals. The primary Web-based reporting tool used by facilities to report their toxic releases is called the Toxics Release Inventory – Made Easy Web (TRI-MEweb).
The Flow Implementation Guide provides a high-level overview of the data flow.
TRI Data Exchange (TDX): EPA’s Central Data Exchange (CDX) node converts the TRI data transmitted by TRI-MEweb into XML and automatically forwards copies of electronic TRI submissions to state Exchange Network Nodes. TDX allows states to receive raw TRI data in real time and also reduces the burden on reporting facilities, allowing them to submit only once through CDX, with the data being sent to both EPA and their state simultaneously. Additionally, TDX participants receive electronic copies of TRI reports submitted to EPA via paper. Facilities that report via paper are still required to report to both EPA and their State.
TDX Program Monthly Conference Calls: To participate, contact Shane Knipschild at knipschild.shane [at] epa.gov.
Memorandum of Agreement
States participating in TDX must sign a Memorandum of Agreement (MOA) with EPA that outlines the specific roles and responsibilities between the State and EPA for the purposes of successfully transmitting TRI data via the Exchange Network. Download the most recent Model Memorandum of Agreement.
TRI Form A and Form R Stylesheet Viewers
To view TRI XML data in the more familiar Form A and Form R formats, download an XSLT file that will mark up the TRI Form A and TRI Form R .xml files to a human-readable format. This style sheet assumes that the .xml files are well formed according to the TRI v6.0 schema.
The TRI schema and supporting flow documentation have been approved for use on the Exchange Network. TRI v4.0 is used to support Reporting Years 2008, 2009, and 2010. Implementation resources for this version follow.