Discharge Monitoring Report

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

A Discharge Monitoring Report (DMR) is a United States regulatory term for a periodic water pollution report prepared by industries, municipalities and other facilities discharging to surface waters.[1] The facilities collect wastewater samples, conduct chemical and/or biological tests of the samples, and submit reports to a state agency or the United States Environmental Protection Agency (EPA). All point source dischargers to ”Waters of the U.S.” must obtain a National Pollution Discharge Elimination System (NPDES) permit from the appropriate agency, and many permittees are required to file DMRs.[2]

NPDES permits and DMR reporting process

For permits other than stormwater permits, the agencies issue effluent limitations for specific pollutants, pursuant to the Clean Water Act (CWA). The basis for these limitations depends on the type of discharging facility, the discharge characteristics and status of the specific surface water body receiving the discharge.

  • National technology-based standards apply to many industries (these standards are called "effluent guidelines"), and to municipal sewage treatment plants.[3]
  • Some dischargers are subject to water quality-based effluent limitations, derived from water quality standards for the adjacent water body.
  • For pollutants not covered by the above circumstances, the agency may set technology-based limitations based on its "best professional judgment" (BPJ).[4]

Most NPDES permits require facilities to submit monthly DMRs, but some permits require seasonal or semi-annual reporting. Facilities may collect and analyze samples more frequently, e.g. weekly, and summarize the results for the prescribed reporting period. Permits typically require reporting of wastewater flow and the results of one or more chemical tests, such as pH, biochemical oxygen demand (BOD), total suspended solids (TSS), nutrients (nitrates and phosphorus), various toxic pollutants, temperature, etc. Some permits also require aquatic biomonitoring of the receiving waterbody.

Accessing DMR Data

The CWA defines DMR data as publicly available information (except for data that would reveal trade secrets).[5] EPA houses DMR data in its Integrated Compliance Information System (ICIS). The NPDES e-reporting Tool Discharge Monitoring Report (NetDMR) is an EPA web-based tool that allows NPDES permittees to electronically sign and submit their discharge monitoring reports to EPA via a secure internet connection (NetDMR is the new tool that replaced the previous Permit Compliance System (PCS)). Information from ICIS database is available through EPA's "Envirofacts" website and "Enforcement and Compliance History Online" (ECHO).[6][7] The Agency provides a DMR "Pollutant Loading Tool" to help users determine who is discharging, what pollutants they are discharging and how much, and where they are discharging.[8] EPA also allows users to search its Facility Registry System, to compare a facility's compliance with air, water and solid waste permits and regulations.[9]

See also

Notes

  1. United States Environmental Protection Agency (EPA), Washington, D.C. (2010) "NPDES Permit Writers' Manual." Document no. EPA-833-K-10-001. p. 8-14.
  2. Note: Some permittees, notably stormwater dischargers (e.g., construction site operators and municipal separate storm sewer systems), may not be required to file DMRs. These facilities prepare stormwater pollution prevention plans and may be required to submit other reports, which vary from state to state. See EPA, "Stormwater Pollution Prevention Plans for Construction Activities." (Accessed 2016-03-17.)
  3. EPA. "Secondary Treatment Regulation." Code of Federal Regulations, 40 C.F.R. 133.
  4. EPA, "NPDES Permit Writers' Manual," Section 5.2.3. "Case-by-Case TBELs for Industrial Dischargers." pp. 5-44ff.
  5. United States. Clean Water Act, section 308(b), 33 U.S.C. § 1318(b).
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.