Office of Enforcement and Compliance Assurance

Electronic Rule

Analysis B:

General Permit Reports

 August 2010

By

Shane A. Knipschild
1. What is eNOI?

The electronic Notice of Intent system (eNOI) is an online system that allows facilities to 

submit the following general permit reports, which are required under current EPA regulations 

(40 CFR 122.28 and 124.5):

 Notice of Intent to discharge (NOI); 

 Notice of Termination (NOT); 

 No Exposure Certifications (NECs); 

 Low Erosivity Waivers (LEWs)]

The eNOI system includes an e-Reporting system that enables industrial permittees to 

submit quarterly Discharge Monitoring Reports, Annual Reports, and Non-Compliance Reports 

as required in the EPA 2008 MSGP permit. As of June 2009, the eNOI system is used to submit 

NOIs under the EPA’s NPDES Vessel General Permit (VGP).

2. What does the eNOI tool do?

The eNOI system allows Owner Operators to apply for coverage under the MSGP, CGP, 

and VGP programs. Users can also submit NOTs, LEWs, and NECs under the CGP and MSGP. 

Once Owner Operators obtain coverage, users can also terminate and modify coverage. An 

acknowledgement letter and PDF of the NOI is generated in the eNOI system and also emailed to 

the Certifying Official for documentation. The eNOI system also allows users to submit a variety 

of reports as required under the MSGP.

3. How does the eNOI system lead to cost savings?

The primary cost saving occurs because an eNOI system reduces the number of hardcopy submittals and manual data entry into the NOI database. eNOI also fulfills the following: is 

an inexpensive form of public notice; notifies permittees immediately if incorrect data is entered; 

provides an efficient means of recordkeeping and receipt notification for EPA and permittees; 

and allows the public to easily search the database for NOIs and will reduce EPA time spent 

responding to public requests about NOI data via web-based interfaces. Approximately 15% of 

NOIs are still submitted in hard-copy, accepted and processed by the NOI processing center.

4. Should eNOI be implemented as a tool attached to ICIS, or as a standalone system?

eNOI should be implemented as a tool attached to ICIS. Currently EPA’s eNOI tool is 

managed by the Office of Water (OW). 75% of the federal data is entered into the eNOI system. 

Planned eNOI expansion by OW will include Pesticides, CAFOs, Construction General Permits 

(CGPs) and vessels. Consistency across the eNOI reporting system would enable the data to be 

implemented into other systems. Regardless of how eNOI is integrated with ICIS and NetDMR, 

OWM plans to add the following sets of coverage to eNOI:

 Vessel Reporting for small cruise ships: Annual Reports and Non-Compliance 

Reports within the next 6 months; One Time Reports within the next 12 months
 EPA Pesticides Permit: issue date April 2011

 CGP issue date June 2011, which will include an effluent guideline in the permit 

and hence will require a reporting function in eNOI

 CAFO: registration form for medium CAFOs, issue date Fall 2011.

5. What are the key steps that will need to be taken to facilitate permitee adoption of 

the selected eNOI tool?

Currently 75% of the eNOI data is being reported electronically. Permitees have already 

adopted the eNOI tool. Steps to incorporate the 25% data that is entered via a clearinghouse 

would have to be implemented. The Electronic Reporting Rule would transition the permitees

who currently submit paper copies to report their data electronically. In the full integration 

option, all eNOI functionality would be incorporated within ICIS and NetDMR, and eNOI would 

no longer exist as a separate system. All data would be consolidated within ICIS, and a new 

module supporting NOI program requirements and management tools for OWM would be built. 

NetDMR would have new modules added so it could be the interface with which permittees 

submitted NOIs, DMRs, and any other NOI-related reporting data1. 

In order for eNOI to be subsumed within ICIS and NetDMR, the following high-level steps 

would need to be performed:

• MSGP, covered facility, Permitted Feature, Limit Set, Limit, DMR, and reporting data will 

be loaded into ICIS; some of this data entry may occur as a data migration from eNOI, and a 

significant percentage may require manual entry

• ICIS will be enhanced to add screens to allow management of the NOI program and to 

update existing functionality to include NOI data elements as needed

• NetDMR will be enhanced to add modules to allow electronic submittal of NOIs, NOIrelated DMRs, and reporting data

• The ICIS/NetDMR data flows will be enhanced to add flows that support the new NOI data 

streams 

• ICIS reporting will be enhanced to support NOI program standard and ad hoc reporting needs

This solution would leverage the existing ICIS/NetDMR infrastructure, security, and technology

environment. The use of the NetDMR framework will allow for state installations of eNOI for 

their own systems and will provide the means for data sharing via web services and XML 

schemas.

Figure 5-1, eNOI Full Integration Solution depicts the envisioned solution.

 

1 Note: Section 3 outlines an eNPDES reporting solution which would allow for submittal of reports and 

achievement dates via NetDMR; that functionality may overlap with some of the proposed eNOI functionality.
Figure 5-1: eNOI Full Integration Solution

In the partial integration option, eNOI would continue to be maintained as a separate system 

which would flow data to ICIS and NetDMR. In this scenario, ICIS would be updated to contain 

the new NOI data, but would not have a new NOI management module built. All the data would 

reside in ICIS, and the data would also reside in eNOI. 

In order to create the data flows between eNOI and NetDMR and ICIS, the following high-level 

steps would need to be performed:

• MSGP, covered facility, Permitted Feature, Limit Set, Limit, DMR, and reporting data will 

be loaded into ICIS; some of this data entry may occur as a data migration from eNOI, and a 

significant percentage may require manual entry

• ICIS will be enhanced to update existing functionality to include NOI data elements as 

needed

• NetDMR will be enhanced to receive DMR data from eNOI, OR eNOI will send DMR data 

directly to ICIS

• Data flows will be created that flow NOI, DMR, and reporting data from eNOI to ICIS 

and/or NetDMR and/or state systems.

This solution would require a new infrastructure for flowing data between eNOI and other 

applications. It would also require eNOI to complete its CROMERR compliance upgrades and 

would make sharing the installation code with states more difficult.
Figure 5-2, eNOI Partial Integration Solution depicts the envisioned solution.

Figure 5-2: eNOI Partial Integration Solution

6. Is the existing eNOI tool sufficiently capable to meet state needs? If not, can 

NetDMR be reasonably modified to include the additional state needs (e.g., daily 

monitoring information, biosolids monitoring, or attachment of additional reports)?

The current ENOI system would have to be modified to meet state NOI needs. The eNOI 

system is designed for federally issued general permits. The current eNOI system does not 

contain specific DMR information. The information resides in the permit and the permitees 

request coverage under the eNOI system. Specific DMR information like limits, limit sets, 

parameters and values would have to be entered in ICIS in order to use the EDMR system. Daily 

monitoring is not available in either the eNOI system or ICIS NetDMR. The systems would 

have to be modified to accept this type of data. In the eNOI system reports are saved as PDFs. 

Data in these reports would have to be extracted and entered into ICIS. ICIS is not specifically

designed to accept PDF and can not evaluate a PDF document against reporting requirements.

7. For states with existing eNOI systems, what requirements will need to be established 

to make the information obtained through those systems compatible with the 

national data base?

States with existing eNOI systems would have to design and map their systems to EPAs 

data standards. In addition, ICIS system required and program required data elements would 

have to be identified and then mapped or created using the state eNOI system data.
8. For states with an existing eNOI system, how will its data be submitted to EPA? 

Data from the state eNOI systems could be submitted using the Net DMR principles. 

Currently Net DMR uses XML scripts and CDX validation to batch data into ICIS. A direct 

system to system script could also be generated and implemented.

9. For states with existing NPDES data systems, but without eNOI systems, how will 

the states’ receive information from EPA after permitees submitted it using the

national eNOI tool?

ICIS is capable of generating a file from the reporting tool (Business Objects). That can 

be used to transfer data from the national system back to the states. A validation process would 

have to be developed to remove duplicate data. Also a script could be created to extract the 

required state data from ICIS and other requirements of state systems. .

10. Should the regulated universe for this requirement include all permittees covered by 

all master general permits? If so, how should the national tool be adapted?

Some states currently use the national system for eNOI data. The national system would 

have to be modified to allow state system entered data and or permitee entered data, or

transferred to the national system.

 

11. Should requirements for some of these master general permits be phased in later? 

If so, which ones and when? 

The requirements for specific programmatic interests should follow the rule 

implementation.

12. Will all of the required basic-facility and basic-permit data elements be obtained 

through use of the eNOI tool? If not, what are the alternative sources?

No. Not all of the basic permit data is available in the eNOI system. Permit system and 

programmatic data like limits, limit sets and values would have to be entered in the national 

system based on the permits. Facility data can be extracted and loaded into the national system 

via the batch process when the national system batch process is completed for facility data.

13. How will EPA ensure that place holder information from the master general 

permits (including limit information) will be in ICIS-NPDES prior to need to enter 

other information related to the facilities covered by the master general permits?

A formal plan will have to be developed following the phase in process of the rule. Dates 

established for the rulemaking phase in options can be used as milestones for ICIS module 

development. The following is an example plan for implementing eNOI.
Technical:

1. Identifying existing EPA and/or state tools/experience:

a. EPA and the states have experience developing and implementing an eNOI system. 

EPA’s Office of Water has developed and is currently using an eNOI system, nationally. 

Alaska and Arizona have developed stat eNOI systems. Also the national system is 

utilized by some stated for managing general permit data.

b. The challenges and risks associated with the full implementation solution are relatively

minor. As stated previously, the general concept, solution framework, security, and 

procedures have been vetted via the existing NetDMR solution. Standard technology

project challenges and risks will apply.

For the partial implementation solution, additional challenges and risks will be accrued in 

the following areas:

 Making eNOI CROMERR-compliant

 Creating new data flows between eNOI and ICIS and/or NetDMR

 Determining integration of security requirements between eNOI and ICIS/NetDMR.

2. Mapping of information collected from tool to data element list to identify what is 

captured by e-reporting tool (number of data elements, data gaps, etc.)

Direct mapping has not been accomplished but estimates for the eNOI mapping are around 

90% with exception to the DMR data as related to OW’s eNOI system. This could also depend 

on the modifications of the ICIS system to accommodate non–mapped data elements.

3. Size of the reporting universe using e-reporting tool

Currently the eNOI universe is expanding in the OW system. This is due to the 

programmatic inclusion of Pesticides, CGP and CAFOs. 2009 estimates for eNOI data is 

approximately 100,000 NOIs in the system. The construction general permit universe is 

estimated at several hundred thousand sites and over a hundred thousand sites for industrial 

facilities. 

4. Reporting of information based on existing regulations:

The MSGP NOI consists of seven major data components: 1) Facility Operator 

Information (name, EIN number, mailing address) 2) Facility Information (name, previous 

permit coverage, address, lat/long, area of coverage, federal facility or Indian lands) 3) Discharge 

Information (if discharge to an MS4, list of receiving waters, impaired waters, TMDLs, 

pollutants causing impairment, water quality standards, Federal Effluent Limitation Guidelines 

and Sector/Subsector requirements) 4) Stormwater Pollution Prevention Plan (SWPPP) Contact 

Information (contact name and phone number) 5) Endangered Species Protection (criterion 
listing and documentation) 6) Historic Preservation (criterion listing) and 7) Certifier and 

Preparer information (name, title, electronic signature, email). 

The CGP NOI consists of six data components: 1) Operator Information (name, EIN, 

mailing address) 2) Project Information (name, address, lat/long, method of mapping, project in 

Indian County, estimated project start and end date, estimated area disturbed) 3) SWPPP 

Information (SWPPP prepared in advance to NOI, location to view SWPPP, SWPPP contact) 4) 

Discharge Information (names of waterbodies and TMDLs) 5) Endangered Species Protection 

(criterion listing, tracking number) 6) Certification Information (name, title, electronic 

signature). 

The VGP NOI consists of five major data components: 1) Facility Operator Information 

(name, EIN, mailing address) 2) Vessel Information (name, IMO, call sign, flag state, type, 

dimensions, ballast water capacity, year built, date last and next anticipated dry-dock, onboard 

treatment system, treatment system type and capacity, ballast water data, type of anti-fouling hull 

coating, prior coverage) 3) Vessel Voyage Information (home port, US ports visiting, number 

passengers, travel beyond EEZ, engaged in Pacific Nearshore Voyages) 4) Discharge 

Information (list discharges, engage in industrial operations, experimental ballast water treatment 

system) 5) Certifier and Preparer Information (name, title, electronic signature, email). 

The MSGP DMR consists of five data components: 1) Facility Information (name, 

mailing address) 2) Discharge Information (monitoring periods, monitor for cadmium, copper, 

lead, zinc, chromium, nickel, silver, hardness level) 3) Outfall Information (total outfalls 

identified in SWPPP, outfall name and list of substantially identical outfalls) 4) Monitoring 

Information (nature of discharge, duration of event, rainfall amount, time since previous storm 

event, list table of outfall name, monitoring type, parameter, concentration, units, results 

descriptions, collection date, exceedance, no further pollutant reduction achievable, comments or 

explanation of any violation) 5) Certifier and Preparer Information (name, title, electronic 

signature, email)

General Permits: EPA and authorized states, tribes, and territories issue general permits 

to cover multiple similar facilities under a single permit. Where a large number of similar 

facilities require permits, a general permit allows the permitting authority to allocate resources in 

a more efficient manner and provide more timely permit coverage than would occur if individual 

permits had to be issued to each similar facility. States, tribes, and territories must seek EPA 

approval to administer general permits.[1] EPA’s regulations governing the General Permit 

Program are located at 40 CFR 122.28. EPA and authorized programs have issued over 700 

general permits nationwide. General permits typically share common elements:[2]

 Sources that involve the same or substantially similar types of operations;

 Sources that discharge the same types of wastes or engage in the same types of sludge use 

or disposal;

 Sources that require the same effluent limitations or operating conditions, or standards for 

sewage sludge use or disposal; or

 

[1] See http://cfpub.epa.gov/npdes/statestats.cfm.

[2] See 40 CFR 122.28(a)(2).
 Sources that require the same monitoring where tiered conditions may be used for minor 

differences within a class (e.g., size or seasonal activity).

The regulations at 40 CFR 122.28(a)(1) provide for general permits to cover dischargers 

within an area corresponding to specific geographic or political boundaries such as the 

following:

 Designated planning area;

 Sewer district; and

 City, county, or state boundary.

The process for developing and issuing NPDES general permits is similar to the process 

for individual permits; however, there are some differences in the sequence of events. For 

general permits, the permitting authority first identifies the need for a general permit and collects 

data that demonstrate that a group or category of dischargers has similarities that warrant a 

general permit. In deciding whether to develop a general permit, permitting authorities consider 

whether:

 A large number of facilities will be covered;

 The facilities have similar production processes or activities;

 The facilities generate similar pollutants; and

 Whether uniform water quality-based effluent limits (WQBELs) (where 

necessary) will appropriately implement water quality standards.

The remaining steps of the general permit process are the same as for individual permits. 

The permitting authority develops a draft permit that includes effluent limitations (if applicable), 

monitoring conditions, special conditions, and standard conditions. The permitting authority then 

issues a public notice and addresses public comments, coordinates with EPA as appropriate in 

the review process, completes a CWA section 401 certification process, develops the 

administrative record, and issues the final permit. The final permit will also establish the 

requirements for the specific information that must be submitted by a facility that wishes to be 

covered under the general permit. After the final general permit has been issued, there are several 

general permit reports that facilities must submit to their permitting authority, including:

 Notice of Intent (NOI) to discharge: This is the initial submission seeking 

coverage under a general permit [40 CFR 122.28(b)(2)(i) and (ii)]; 

 Notice of Termination (NOT): A request by the permittee to terminate their 

coverage under an existing permit (40 CFR 124.5);

 No Exposure Certification (NEC): A certification from a facility indicating that 

coverage under an existing stormwater general permit is not necessary due to 

certain facility-specific conditions [40 CFR 122.26(g)(1) and (4)]; and

 Low Erosivity Waiver (LEW): A certification from a facility indicating that 

coverage under an existing construction stormwater general permit is not 

necessary due to certain facility-specific or climate conditions [40 CFR 

122.26(b)(15)].
It is important to note that EPA general permit regulations (40 CFR 122.28) do not 

require all general permit covered facilities to submit NOIs for all general permits issued by EPA 

and authorized state NPDES programs. Some general permits provide for automatic coverage.

This means that neither EPA nor the authorized state, tribe, or territory programs will have 

information regarding exactly which facilities are regulated under these general permits.

General permits cover a wide range of facility types that range from the very large (e.g., 

offshore oil and gas facilities, seafood processors) to very small discharges. Discharges from 

facilities covered under general permits include a variety of pollutants, such as total suspended 

solids, biochemical oxygen demand, oil and grease, bacteria, nutrients, hydrocarbons, metals, 

and toxics. 

All other general permits submitted via eNOI will include the following facility

data elements, shown in Table 14-1:

Data Name Data Description

Basic Facility Information

Facility Type of Ownership

The code/description identifying the type of facility 

(e.g., state government, municipal or water district, 

Federal facility, tribal facility). This data element is 

used by the EPA data system to populate the Permit 

Facility Type data element (i.e., POTW, Private, NonPOTW, and Federal).

Facility Site Name The name of the facility.

Facility Site Address The address of the physical facility location.

Facility Site City

The name of the city, town, village, or other locality, 

when identifiable, within whose boundaries (the 

majority of) the facility site is located. This is not 

always the same as the city used for USPS mail delivery.

Facility Site State 

The U.S. Postal Service (USPS) abbreviation that 

represents the state or state equivalent for the U.S. where 

the facility is located.

Facility Site Zip Code

The combination of the 5-digit Zone Improvement Plan 

(ZIP) code and the 4-digit extension code (if available) 

that represents the geographic segment that is a sub unit 

of the ZIP Code assigned by the U.S. Postal Service to a 

geographic location where the facility is located.

Facility Site Tribal Land Indicator

The Bureau of Indian Affairs code for every unit of land 

trust allotment (“tribal land”) within Indian Country. 

This code will identify whether the facility is on tribal 

land and the name of the American Indian tribe or 

Alaskan Native entity (if applicable).

Facility Site Longitude

The measure of the angular distance on a meridian east 

or west of the prime meridian for the facility. Entered in 

either Decimal Degrees or in Degrees Minutes Seconds; 

stored in decimal degrees and in accordance with 

Environmental Data Standards Council, 

Latitude/Longitude Data Standard, Standard No.: 

EX000017.2, January 6, 2006
Facility Site Latitude

The measure of the angular distance on a meridian north 

or south of the equator for the facility. Entered in either 

Decimal Degrees or in Degrees Minutes Seconds; stored 

in decimal degrees and in accordance with 

Environmental Data Standards Council, 

Latitude/Longitude Data Standard, Standard No.: 

EX000017.2, January 6, 2006.

Facility Site Source Map Scale Number

The number that represents the proportional distance on 

the ground for one unit of measure on the map or photo 

for the facility. These data are provided in accordance 

with Environmental Data Standards Council, 

Latitude/Longitude Data Standard, Standard No.: 

EX000017.2, January 6, 2006.

Facility Site Horizontal Accuracy Measure

The measure of the accuracy (in meters) of the facility’s 

latitude and longitude coordinates. These data are 

provided in accordance with Environmental Data 

Standards Council, Latitude/Longitude Data Standard, 

Standard No.: EX000017.2, January 6, 2006.

Facility Site Horizontal Collection Method

The text that describes the method used to determine the 

latitude and longitude coordinates for the facility. These 

data are provided in accordance with Environmental 

Data Standards Council, Latitude/Longitude Data 

Standard, Standard No.: EX000017.2, January 6, 2006.

Facility Site Horizontal Reference Datum

The code/description that represents the reference datum 

used in determining latitude and longitude coordinates 

for the facility. These data are provided in accordance 

with Environmental Data Standards Council, 

Latitude/Longitude Data Standard, Standard No.: 

EX000017.2, January 6, 2006.

Facility Site Reference Point

The code/description for the place for which geographic 

coordinates were established. These data are provided in 

accordance with Environmental Data Standards Council, 

Latitude/Longitude Data Standard, Standard No.: 

EX000017.2, January 6, 2006.

Facility Individual Affiliation Type Code

The way that the contact or address is affiliated with the 

facility (e.g., "Owner," “Operator,” or "Main Contact"). 

This is a unique code that identifies the nature of the 

individual's affiliation to the facility. 

Facility Individual First Name The given name of an individual affiliated with this 

facility.

Facility Individual Last Name The surname of an individual affiliated with this facility.

Facility Individual Title The title held by an individual in an organization 

affiliated with this facility.

Facility Individual Organization The legal, formal name of an organization that is 

affiliated with the individual affiliated with this facility.

Facility Individual Street Address The physical address of the individual affiliated with this 

facility.

Facility Individual City The name of the city, town, village, or other locality for 

the individual affiliated with this facility.

Facility Individual State

The U.S. Postal Service (USPS) abbreviation that 

represents the state or state equivalent for the U.S. for 

the individual affiliated with this facility.
Facility Individual Zip Code

The combination of the 5-digit Zone Improvement Plan 

(ZIP) code and the 4-digit extension code (if available) 

that represents the geographic segment that is a sub unit 

of the ZIP Code assigned by the U.S. Postal Service to a 

geographic location for the individual affiliated with this 

facility.

Facility Individual E-Mail Address The e-mail address of the designated individual affiliated 

with this facility.

Facility Organization Formal Name

The legal, formal name of an organization that is 

affiliated with the facility.

Facility Organization Street Address The physical address of the organization affiliated with 

the facility.

Facility Organization City The name of the city of the organization that is affiliated 

with the facility.

Facility Organization State

The U.S. Postal Service abbreviation that represents the 

state or state equivalent for the organization affiliated 

with the facility.

Facility Organization Zip Code

The combination of the 5-digit Zone Improvement Plan 

(ZIP) code and the 4-digit extension code (if available) 

that represents the geographic segment that is a sub unit 

of the ZIP Code assigned by the U.S. Postal Service to a 

geographic location for the organization affiliated with 

the facility.

Basic Permit Information

NPDES ID This is the unique NPDES permit number.

Master General Permit Number The unique identifier of the master general permit, 

which is linked to a General Permit Covered Facility.

Permit Type

The unique code/description identifying the type of 

permit.

Permit Issue Date

This is the date the permit was issued. The date data 

must be provided in 

CCYY-MM-DD format where CC is the century, YY is 

the year, MM is the month and DD is the day.

Permit Modification/Amendment Date

This is the date on which the permit was modified or 

amended. The date data must be provided in CCYYMM-DD format where CC is the century, YY is the 

year, MM is the month and DD is the day.

Permit Application Total Design Flow

This is the flow that a permitted facility was designed to 

accommodate, in millions of gallons per day (MGD), as 

stated on its NPDES application.

Permit Application Total Actual Average Flow

This is the actual average flow that a permitted facility 

will likely accommodate, in MGD, as stated on its 

NPDES application.

Permit Application/NOI Received Date

This is the date on which the application for a NPDES 

permit was received or a Notice of Intent (NOI) for 

coverage under a master general permit was received. 

The date data must be provided in CCYY-MM-DD 

format where CC is the century, YY is the year, MM is 

the month and DD is the day.
Associated NPDES ID Numbers

If applicable, the unique identifier for a NPDES Permit 

that is related to another NPDES Permit or other NPDES 

ID number. For example, this data element could be 

used to identify the receiving POTW’s permit number 

for an industrial user, the recipient POTW’s permit 

number for a satellite collection system, municipalities 

covered under the same MS4 permit, etc.

SIC Codes

The four-digit Standard Industrial Classification (SIC) 

code/description that represents the economic activity of 

the permitted facility.

NAICS Codes

The six-digit North American Industry Classification 

System (NAICS) code/description that represents the 

economic activity of the permitted facility.

Permittee Street Address The address that describes the physical location of the 

permit holder.

Permittee Organization Formal Name The legal, formal name of the organization that holds the 

permit.

Permittee Zip Code

The combination of the 5-digit Zone Improvement Plan 

(ZIP) code and the 4-digit extension code (if available) 

that represents the geographic segment that is a sub unit 

of the ZIP Code assigned by the U.S. Postal Service to a 

geographic location for the permit holder.

Permittee City The name of the city, town, or village where the mail is 

delivered for the permit holder.

Permittee State

The U.S. Postal Service abbreviation that represents the 

state or state equivalent for the U.S. for the permit 

holder.

Description The unique code/ description that identifies the type of 

narrative condition.

Narrative Condition Number This identifies a narrative condition and its elements 

uniquely for a permit.

Schedule Date

The date on which a schedule event is due to be 

completed and against which compliance will be 

measured. The date data must be provided in CCYYMM-DD format where CC is the century, YY is the 

year, MM is the month and DD is the day.

Actual Date

The date on which the permittee achieved the schedule 

event. The date data must be provided in CCYY-MMDD format where CC is the century, YY is the year, MM 

is the month and DD is the day.

Report Received Date

The date on which the regulatory authority receives a 

report (generally a letter) from the permittee indicating 

that a Schedule Event was completed (e.g., Start 

Construction) or the required report was enclosed. The 

date data must be provided in CCYY-MM-DD format 

where CC is the century, YY is the year, MM is the 

month and DD is the day.

Event The code/ description indicating the particular event 

with which the permittee is scheduled to comply.

Biosolids Information on NPDES Permit Application or Notice of Intent

Average Annual Dry Biosolids Production The average annual amount of biosolids (in dry metric 

tons) produced by the permitted facility. 
Average Annual Amount of Exceptional Quality (EQ) 

Product Distributed and Marketed 

The average annual amount (in dry metric tons) of 

Exceptional Quality (EQ) biosolids product distributed 

and marketed. This refers to biosolids that meet the 

ceiling concentrations in Table 1 of §503.13 and the 

pollutant concentrations in Table 3 of §503.13; the Class 

A pathogen requirements in §503.32(a); and one of the 

vector attraction reduction requirements in 

§503.33(b)(1) through (b)(8). 

Average Annual Amount of Land Applied Biosolids The average annual amount (in dry metric tons) of 

biosolids land applied.

Average Annual Amount of Incinerated Biosolids The average annual amount (in dry metric tons) of 

biosolids incinerated.

Average Annual Amount of Biosolids Co-Disposed in 

MSW

The average annual amount (in dry metric tons) of 

biosolids co-disposed in a municipal solids waste 

(MSW) landfill.

Average Annual Amount of Biosolids Surface Disposal The average annual amount (in dry metric tons) of 

biosolids used for surface disposal.

Average Annual Amount of Biosolids Otherwise 

Managed

The average annual amount (in dry metric tons) of 

biosolids managed using methods not otherwise 

described. For example, if a POTW sends its biosolids to 

a regional composter or heat dryer, that tonnage would 

included in this data element.

Biosolids Management Facility Type

The unique code indicating whether the facility was 

issued a permit as a biosolids generator, processor, or 

end user disposal site.

Animal Feeding Operation Information on NPDES Permit Application or Notice of Intent

Facility CAFO Flag A binary “yes/no” flag to indicate whether the facility is 

a Concentrated Animal Feeding Operation (CAFO).

Facility Animal Types

The unique code/description that identifies the animal 

sector(s) at the facility.

Facility Annual Average Total Number The annual average total number of each type of 

livestock at the facility.

Facility Annual Average Total Number (Unhoused 

Confinement)

The annual average total number of each type of 

livestock at the facility in unhoused confinement. This is 

the number of animals, by type, in open confinement 

that are held at the facility for a total of 45 days or more 

on an annual basis.

Permit/NOI CAFO Waste Type The type of CAFO waste described (i.e., manure, litter, 

process wastewater).

Permit/NOI Status of the CAFO Waste The status of the CAFO waste described (i.e., generated, 

or generated and transferred).

Permit/NOI 12-Month Amount of CAFO Waste

The total amount of each CAFO waste (i.e.,, manure, 

litter, or process wastewater) (in tons) with that status 

(i.e., generated, or generated and transferred) from this 

facility in the previous 12 months.

Total Number of Acres for Land Application Covered 

by the Nutrient Management Plan

Total number of acres (to the nearest quarter acre) for 

land application covered by the nutrient management 

plan in the previous 12 months.

Facility Manure Containment or Storage Containment 

Type Code

The unique code/description for the type(s) of manure 

containment and storage used by the operation.

Facility Manure Annual Average Total Capacity The annual average total capacity (in gallons) of manure 

containment and storage structure(s).

Construction and Industrial Stormwater Information on NPDES Permit Application, Notice of Intent, or 

Waiver Request
Total Area of the Site This is the total area (to the nearest quarter acre) of the 

facility site.

Total Activity Area 

Total area (to the nearest quarter acre) of the facility that 

contains industrial activities and processes and 

construction activities. These activities and processes 

may include (but is not limited to) using, storing or 

cleaning industrial machinery or equipment, and areas 

where residuals from using, storing or cleaning 

industrial machinery or equipment remain and are 

exposed to stormwater; materials or products stored 

outdoors; materials contained in open, deteriorated or 

leaking storage drums, barrels, tanks, and similar 

containers; and materials or products from past industrial 

activity. Construction activities include excavation of 

lands.

Current Total Imperious Area The current total impervious area (to the nearest quarter 

acre) of the facility or site.

Post-Construction Total Impervious Area

Total impervious area (to the nearest quarter acre) of the 

permitted facility impervious area after the construction 

addressed in the permit application is completed.

Proposed Best Management Practices for Industrial 

Activities and Stormwater

This is a text field that describes the proposed measures, 

including best management practices, to control 

pollutants in storm water discharges during construction, 

including a brief description of applicable State and 

local erosion and sediment control requirements.

Post-Construction Best Management Practices for 

Industrial Activities and Stormwater Discharges

This is a text field that describes the proposed measures 

to control pollutants in storm water discharges that will 

occur after construction operations have been completed, 

including a brief description of applicable State or local 

erosion and sediment control requirements. This field 

also describes the nature of fill material and existing data 

describing soils. 

Soil and Fill Material Description This field describes the nature of fill material and 

existing data describing soils.

Runoff Coefficient of the Site

This is an estimate of the runoff coefficient of the site 

after the construction addressed in the permit application 

is completed.

Estimated Construction Project Start Date

The estimated start date for the construction project 

covered by the NPDES permit. The date data must be 

provided in CCYY-MM-DD format where CC is the 

century, YY is the year, MM is the month and DD is the 

day.

Estimated Construction Project End Date

The estimated end date for the construction project 

covered by the NPDES permit. The date data must be 

provided in CCYY-MM-DD format where CC is the 

century, YY is the year, MM is the month and DD is the 

day.

Municipal Separate Storm Sewer System (MS4) Information on NPDES Permit Application or Notice of 

Intent

MS4 Permit Class This is the code/description that identifies the size of the 

MS4 permit holder (small/medium/large).

MS4 Public Education Program

The unique code/description that identifies the public 

education programs the permittee intends to use to 

distribute educational materials to the community.
MS4 Measurable Goals Associated With Public 

Education Program

The unique code/description that identifies the types of 

measurable goals associated with the public education 

programs.

MS4 Public Involvement and Participation Program

The unique code/description that identifies the public 

involvement and participation programs the permittee 

intend to use to distribute educational materials to the 

community.

MS4 Measurable Goals for the Public Involvement and 

Participation Program

The unique code/description that identifies the types of 

measurable goals associated with the public involvement 

and participation programs.

MS4 System Map

A data flag indicating whether the permittee has 

developed a storm sewer system map showing the 

location of all outfalls and names and locations of all 

waters of the U.S. that receive discharges from those 

outfalls.

MS4 Prohibition Enforcement

The unique code/description that identifies the 

procedures and actions the permittee will take to enforce 

the prohibition on non-stormwater discharges to the 

MS4.

MS4 Detecting Non-Stormwater Discharges

The unique code/description that identifies the 

procedures and actions the permittee will take to detect 

and address non-stormwater discharges, including illegal 

dumping, to permittee’s system.

MS4 Public Education: Illegal Discharges

The unique code/description that identifies the 

procedures and actions the permittee will take to inform 

public employees, businesses and the general public of 

hazards associated with illegal discharges and improper 

disposal of waste.

MS4 Construction Runoff Ordinance

The unique code/description that identifies the 

permittee’s ordinance or other regulatory mechanism, 

including sanctions to ensure compliance, to require 

erosion and sediment controls.

MS4 Erosion and Sediment Controls

The unique code/description that identifies the

permittee’s requirements for construction site operators 

to implement appropriate erosion and sediment control 

BMPs.

MS4 Construction Site Waste

The unique code/description that identifies the 

permittee’s requirements for construction site operators 

to control waste such as discarded building materials, 

concrete truck washout, chemicals, litter, and sanitary 

waste at the construction site that may cause adverse 

impacts to water quality.

MS4 Construction Site Review

The unique code/description that identifies the 

permittee’s procedures for site plan review which 

incorporate consideration of potential water quality 

impacts.

MS4 Public Information

The unique code/description that identifies the 

permittee’s procedures for receipt and consideration of 

information submitted by the public.

MS4 Site Inspections And Enforcement

The unique code/description that identifies the 

permittee’s procedures for site inspection and 

enforcement of control measures.
MS4 Controls For Stormwater From New Development 

And Redevelopment

The unique code/description that identifies the 

combination of structural and/or non-structural best 

management practices (BMPs), which the permittee is 

using to address stormwater runoff from new 

development and redevelopment projects that disturb 

greater than or equal to one acre. 

MS4 Stormwater Ordinance For New Development And 

Redevelopment

The unique code/description that identifies the 

permittee’s ordinance or other regulatory mechanism to 

address post-construction runoff from new development 

and redevelopment projects.

MS4 Maintenance Of BMPs

The unique code/description that identifies the 

permittee’s program to ensure adequate long-term

operation and maintenance of BMPs used for controlling 

runoff from new development and development projects.

MS4 Runoff From Municipal Operations

The unique code/description that identifies the 

permittee’s operation and maintenance program that 

includes a training component and has the ultimate goal 

of preventing or reducing pollutant runoff from 

municipal operations.

MS4 Additional Measures

The unique code/description that identifies the any other 

additional measures in the permittee’s stormwater 

management program that is required by the permit. 

MS4 Measurable Goals for Additional Measures

The unique code/description that identifies the 

measurable goal for each of the programs or BMPs to 

address stormwater including, as appropriate, the months 

and years in which the permittee will undertake required 

actions, including interim milestones and the frequency 

of the action

Collection System Information on NPDES Permit Application or Notice of Intent

Name of Collection System

This is the name of each collection system (by 

municipality or area) providing flow to the permittee. 

This includes unincorporated connector districts.

Owner Name of Collection System

This is the owner name of each collection system (by 

municipality or area) providing flow to the permittee. 

This includes unincorporated connector districts.

Owner Type of Collection System

This is the ownership type of each collection system 

(including municipality owned, privately owned). This 

includes unincorporated connector districts.

Permit Number for Collection System

This is the NPDES permit number (if applicable) of each 

collection system (by municipality or area) providing 

flow to the permittee. This includes unincorporated 

connector districts.

Population of Collection System

This is the population served for each collection system 

(by municipality or area) that provides flow to the 

permittee. This includes unincorporated connector 

districts.

Percentage of Collection System That Is a Combined 

Sewer System

This is the percentage of the collection system, for each 

collection system (by municipality or area), that is a 

combined sewer system. This includes unincorporated 

connector districts.

Combined Sewer System Information on NPDES Permit Application or Notice of Intent
Complete and Implement a Long-Term CSO Control 

Plan

All Phase II and post-Phase II combined sewer system 

NPDES permittees are required to complete and 

implement a long-term CSO control plan as described in 

EPA’s Combined Sewer Overflow (CSO) Control Policy 

(19 April 1994; 59 Federal Register 18688-18698). This 

data element identifies whether the permit requires the 

permit holder to complete and implement a long-term

CSO control plan and whether the permit holder is in 

compliance with this permit language.

Nine Minimum CSO Controls Developed

All combined sewer system NPDES permittees are 

required to implement the nine minimum controls 

outlined in EPA’s Combined Sewer Overflow (CSO) 

Control Policy (19 April 1994; 59 Federal Register 

18688-18698). This data element identifies whether the 

permit holder developed the nine minimum controls in 

compliance with permit language.

Nine Minimum CSO Controls Implemented

All combined sewer system NPDES permittees are 

required to implement the nine minimum controls 

outlined in EPA’s Combined Sewer Overflow (CSO) 

Control Policy (19 April 1994; 59 Federal Register 

18688-18698). This data element identifies whether the 

permit holder implemented the nine minimum controls 

in compliance with permit language.

Enforcement Mechanism for the LTCP

All Phase II and post-Phase II combined sewer system 

NPDES permittees are required to complete and 

implement a long-term CSO control plan as described in 

EPA’s Combined Sewer Overflow (CSO) Control Policy 

(19 April 1994; 59 Federal Register 18688-18698). This 

data element identifies the type of enforcement 

mechanism used to require the development and 

implementation of a LTCP. 

LTCP Submitted

All Phase II and post-Phase II combined sewer system 

NPDES permittees are required to complete and 

implement a long-term CSO control plan as described in 

EPA’s Combined Sewer Overflow (CSO) Control Policy 

(19 April 1994; 59 Federal Register 18688-18698). This 

data element identifies whether the permit holder 

submitted the LTCP for approval by the permitting 

authority. 

LTCP Approved

All Phase II and post-Phase II combined sewer system 

NPDES permittees are required to complete and 

implement a long-term CSO control plan as described in 

EPA’s Combined Sewer Overflow (CSO) Control Policy 

(19 April 1994; 59 Federal Register 18688-18698). This 

data element identifies whether the LTCP submitted by 

the permit holder was approved by the permitting 

authority. 
LTCP Approval Date

All Phase II and post-Phase II combined sewer system 

NPDES permittees are required to complete and 

implement a long-term CSO control plan as described in 

EPA’s Combined Sewer Overflow (CSO) Control Policy 

(19 April 1994; 59 Federal Register 18688-18698). This 

data element identifies the date when the permitting 

authority approved the LTCP. The date data must be 

provided in CCYY-MM-DD format where CC is the 

century, YY is the year, MM is the month and DD is the 

day.

Actual Date Completed LTCP and CSO Controls

All Phase II and post-Phase II combined sewer system 

NPDES permittees are required to complete and 

implement a long-term CSO control plan as described in 

EPA’s Combined Sewer Overflow (CSO) Control Policy 

(19 April 1994; 59 Federal Register 18688-18698). This 

data element identifies the date by which the permit 

holder completed all required LTCP and CSO controls. 

The date data must be provided in CCYY-MM-DD 

format where CC is the century, YY is the year, MM is 

the month and DD is the day.

Enforceable Schedule to Complete LTCP and CSO 

Controls

All Phase II and post-Phase II combined sewer system 

NPDES permittees are required to complete and 

implement a long-term CSO control plan as described in 

EPA’s Combined Sewer Overflow (CSO) Control Policy 

(19 April 1994; 59 Federal Register 18688-18698). This 

data element identifies whether the permit holder is on 

an enforceable schedule to complete all required LTCP 

and CSO controls. 

Other CSO Control Measures with Compliance 

Schedule

This data element identifies whether the permit holder 

has other CSO control measures specified in a 

compliance schedule, beyond those identified in the nine 

minimum controls, LTCP, or a plan for sewer system 

separation.

Approved Post-Construction Compliance Monitoring 

Program

This data element indicates whether the permit holder is 

currently operating under an approved post-construction 

compliance monitoring program.

Pretreatment Information on NPDES Permit Application, Notice of Intent, (or Pretreatment Compliance 

Audit or Inspection) (this includes permit application data required for all new and existing POTWs (40 CFR 

122.21(j)(6))

Pretreatment Program Required Indicator

The code/description indicating if the permitted 

municipality is required to develop a pretreatment 

program.

Pretreatment Program Approved Date

The date the pretreatment program was approved. The 

date data must be provided in CCYY-MM-DD format 

where CC is the century, YY is the year, MM is the

month and DD is the day.

Approval Authority Name The name of the agency that is the designated approval 

authority.
Program Modification Date for Required Pretreatment 

Streamlining Changes

EPA’s Pretreatment Streamlining Rule (14 October 

2005; 70 Federal Register 60134-60198) revised several 

provisions of the General Pretreatment Regulations (40 

CFR Part 403). In particular, the Pretreatment 

Streamlining Rule made 13 more stringent changes to 

the General Pretreatment provisions (40 CFR Part 403). 

The rule requires that EPA and state NPDES permitting 

authorities revise NPDES permits and approved 

pretreatment program authorizations to require 

implementation of these 13 more stringent changes. This 

is the date when the Control Authority adopted the 

required 13 changes from the Pretreatment Streamlining 

Rule. The date data must be provided in CCYY-MMDD format where CC is the century, YY is the year, MM 

is the month and DD is the day.

Program Modification Date for Optional Pretreatment 

Streamlining Changes

EPA’s Pretreatment Streamlining Rule (14 October 

2005; 70 Federal Register 60134-60198) revised several 

provisions of the General Pretreatment Regulations (40 

CFR Part 403). In particular, the Pretreatment 

Streamlining Rule made 7 changes to the General 

Pretreatment provisions (40 CFR Part 403) that provide 

more flexibility. The rule give EPA and state NPDES 

permitting authorities the option to revise NPDES 

permits and approved pretreatment program 

authorizations for these 7 changes. This is the date when 

the Control Authority adopted the optional 7 changes 

from the Pretreatment Streamlining Rule. The date data 

must be provided in CCYY-MM-DD format where CC 

is the century, YY is the year, MM is the month and DD 

is the day.

Program Modification Type for Optional Pretreatment 

Streamlining Changes

EPA’s Pretreatment Streamlining Rule (14 October 

2005; 70 Federal Register 60134-60198) revised several 

provisions of the General Pretreatment Regulations (40 

CFR Part 403). In particular, the Pretreatment 

Streamlining Rule made 7 changes to the General 

Pretreatment provisions (40 CFR Part 403) that provide 

more flexibility. This data element identifies which of 

the 7 optional provisions from the Pretreatment 

Streamlining Rule were adopted by the Control 

Authority.

Significant Industrial User Name

The name of each Significant Industrial User (SIU) that 

is discharging (including truck transportation) to this 

POTW.

Significant Industrial User Address

The mailing address of each Significant Industrial User 

(SIU) that is discharging (including truck transportation) 

to this POTW.

Significant Industrial User City

The name of the city, town, village, or other locality, 

when identifiable, within whose boundaries (the 

majority of) for each Significant Industrial User (SIU) 

that is discharging (including truck transportation) to this 

POTW.

Significant Industrial User State 

The U.S. Postal Service (USPS) abbreviation that 

represents the state or state equivalent for the U.S. for 

each Significant Industrial User (SIU) that is discharging 

(including truck transportation) to this POTW.
Significant Industrial User Zip Code

The combination of the 5-digit Zone Improvement Plan 

(ZIP) code and the 4-digit extension code (if available) 

that represents the geographic segment that is a sub unit 

of the ZIP Code assigned by the U.S. Postal Service to a 

geographic location for each Significant Industrial User 

(SIU) that is discharging (including truck transportation) 

to this POTW.

Significant Industrial User Subject to Local Limits

This data element will identify for each Significant 

Industrial User (SIU) that is discharging (including truck 

transportation) to this POTW whether the SIU is subject 

to local limits.

Significant Industrial User Subject to Local Limits More 

Stringent Than Categorical Standards 

This data element will identify for each Significant 

Industrial User (SIU) that is discharging (including truck 

transportation) to this POTW whether the SIU is subject 

to local limits that are more stringent than the applicable 

categorical standards.

Industrial User Subject to Categorical Standards

This data element will identify for each Significant 

Industrial User (SIU) that is discharging (including truck 

transportation) to this POTW whether the SIU is subject 

to categorical standards.

Applicable Categorical Standards

This data element will identify for each Significant 

Industrial User (SIU) that is discharging (including truck 

transportation) to this POTW the applicable categorical 

standards.

Significant Industrial User Process Wastewater Flow 

Rate

This data element will identify for each Significant 

Industrial User (SIU) that is discharging (including truck 

transportation) to this POTW the process wastewater 

flow rate (in gallons per day).

Type of Significant Industrial User Process Wastewater 

Flow

This data element will identify for each Significant 

Industrial User (SIU) that is discharging (including truck 

transportation) to this POTW the type of process 

wastewater flow (continuous or intermittent).

Significant Industrial User Non-Process Wastewater 

Flow Rate

This data element will identify for each Significant 

Industrial User (SIU) that is discharging (including truck 

transportation) to this POTW the non-process 

wastewater flow rate (in gallons per day).

Type of Significant Industrial User Non-Process 

Wastewater Flow

This data element will identify for each Significant 

Industrial User (SIU) that is discharging (including truck 

transportation) to this POTW the type of non-process 

wastewater flow (continuous or intermittent).

Industrial User Causing Problems at POTW

This data element will identify for each Significant 

Industrial User (SIU) whether it caused or contributed to 

any problems (including upset, bypass, interference, 

pass-through) at this POTW within the past four and 

one-half years. EPA regulations require the Control 

Authority to develop and enforce local limits when the 

discharge from an IU causes or contributes to any 

problems (including upset, interference, bypass) at the 

receiving POTW’s effluent discharge or biosolids.

Receiving RCRA Waste

This data element will identify whether the POTW has 

received RCRA hazardous waste by truck, rail, or 

dedicated pipe within the last three years. 

Receiving Remediation Waste

This data element will identify whether the POTW has

received RCRA or CERLCA waste from off-site 

remedial activities within the last three years.
Control Authority Name

The name of the Control Authority for the Significant 

Industrial User discharging to this POTW. This will be 

the name of the State or EPA Region when they are the 

Control Authority. This field may also come from the 

pretreatment compliance audit or inspection.

Control Authority NPDES Permit Number

The NPDES permit number of the Control Authority for 

the Significant Industrial User discharging to this 

POTW. This field may also come from the pretreatment 

compliance audit or inspection.

Cooling Water Intake Information on NPDES Permit Application or Notice of Intent

Type of Facility

The unique code/description that identifies the type of 

facility based on regulations, 1 = New Facility under 125 

Subpart I, 2 = New Offshore Oil & gas Facility under 40 

CFR 125 Subpart N, 3 = Existing Facility under 40 CFR 

125 Subpart J, 4 = BPJ Facility over 2 MGD under 40 

CFR 125.90(b), 401.14.

Number of Cooling Water Intake Structures (CWISs) The number of cooling water intake structures (CWISs) 

at the facility.

Design Intake Flow for Cooling Water Intake Structure

The design intake flow (DIF), in units of MGD, is the 

total designed amount of flow for each permitted cooling 

water intake structure. This value is based on maximum 

design flow capacities.

Actual Intake Flow for Cooling Water Intake Structure

This actual flow value, in units of MGD, is intended to 

represent on-the-ground intake flow capacities in the 

preceding year, as opposed to the DIF, which is based on 

maximum design flow capacities.

Average Reported Intake Flow for Cooling Water Intake 

Structure

This average flow value, in units of MGD, is intended to 

represent on-the-ground intake flow capacities in the 

preceding year, as opposed to the DIF, which is based on 

maximum design flow capacities.

Percentage of Intake for Cooling Purposes

This is the percentage of water intake that is used for 

cooling purposes for each permitted cooling water intake 

structure.

Location Type for Cooling Water Intake Structure

The unique code/description that identifies the location 

and description for each intake. These values are 

1=shoreline intake description (flushed, recessed), 2= 

intake canal, 3=embayment, bank, or cove, 

4=submerged offshore intake, 5=near-shore submerged 

intake, 6=shoreline submerged intake.

Distance Offshore for Submerged Cooling Water Intake 

Structure The distance (in feet) from shore for each CWIS.

Maximum Through-Screen Velocity

This is the maximum velocity (in feet/second) of the 

water intake through the screen for each permitted 

cooling water intake structure.

Average Through-Screen Velocity

This is the average through-screen velocity (in 

feet/second) of the water intake through the screen for 

each permitted cooling water intake structure.

Percentage of Mean Annual Flow Withdrawn – Fresh 

Water Facilities

The percentage of the source water annual mean flow 

withdrawn as compared to the total design intake flow

from all cooling water intake structures located in a 

freshwater river or stream at the permitted facility.
Percentage of Design Intake Flow over Tidal Cycle –

Tidal River or Estuary Facilities

The percentage of the volume of the water column 

within the area centered about the opening of the intake 

in a tidal river or estuary with a diameter defined by the 

distance of one tidal excursion at the mean low water 

level as compared to the facility’s total design intake 

flow over one tidal cycle of ebb and flow.

Waterbody Type

The unique code/description that describes the 

impingement control technologies for each CWIS. A 

value of 1 = Ocean, 2 = Estuary, 3 = Great Lake, 4 = 

Fresh River, 5 = Lake/Reservoir.

Canal/Fish Return Length This is the length for any fish return system at the 

permitted facility.

Significant Navigation or Waterbody Use Type Near 

The Intake Entrance

The unique code/description for the type of navigation 

or waterbody use near each CWIS. A value of 1 (one) 

indicates the intake is located where boat/barge 

navigation near the intake is a consideration when 

making any potential modifications to the intake. A 

value of 0 (zero) indicates navigation does not occur in 

the vicinity of the intake. Navigational considerations 

affect which impingement and entrainment technologies 

may be used by intakes located in embayments, banks, 

or coves.

Mean Intake Water Depth

This is the mean depth (in feet) for each CWIS. This 

value is used for the estimation of total existing screen 

width.

Intake Well Depth

The intake well depth (in feet) is the distance from the 

intake deck to the bottom of the screen well for each 

CWIS, and includes both water depth and distance from 

the water surface to the deck. The intake well depth is 

used to select the depth of the required screen.

Debris Loading

The unique code/description that describes the amount 

of debris near each CWIS. A value of 1 (one) indicates 

high levels of debris and trash near the intake. A value 

of 0 (zero) indicates debris is low or negligible. A 

facility that uses a trash rack is likely to have a high 

debris loading.

Impingement Control Technology In-Place

The unique code/description that describes the 

impingement control technologies for each CWIS. A 

value of 1= Modified Traveling Screens, 2= Passive 

Intake (Velocity Cap, Coarse Wedgewire Screens, 

Porous Dam, Leaky Dike, etc.), 3= Barrier net, and 4 = 

Fish Diversion or Avoidance (Louvers, Acoustics, etc.)., 

5 = Other technology. A value of zero means no 

controls.

Entrainment Control Technology in-Place

The unique code/description that describes the 

entrainment control technologies for each CWIS. A 

value of 1= Traveling Screens w/ Fine Mesh, 2= Far 

Offshore Intake, and 3 = Passive Screens w/ Fine Mesh, 

4 = Closed-Cycle Recirculating System, 5 = Other 

Technology. A value of zero means no controls.

Track II Comprehensive Demonstration Study 

Submission Date

The date of any submission of any Track II 

Comprehensive Demonstration Study. The date data 

must be provided in CCYY-MM-DD format where CC 

is the century, YY is the year, MM is the month and DD 

is the day.
Design and Construction Technology Plan Submission 

Date

The submission date of any Design and Construction 

Technology Plan. The date data must be provided in 

CCYY-MM-DD format where CC is the century, YY is 

the year, MM is the month and DD is the day.

Source Water Biological Study Submission Date

The submission date of any Source Water Biological 

Study. The date data must be provided in CCYY-MMDD format where CC is the century, YY is the year, MM 

is the month and DD is the day.

Verification Monitoring Plan Submission Date

The submission date of any Verification Monitoring 

Plan. The date data must be provided in CCYY-MM-DD 

format where CC is the century, YY is the year, MM is 

the month and DD is the day.

Source Water Physical Data Submission Date

The submission date of any Source Water Physical Data. 

The date data must be provided in CCYY-MM-DD 

format where CC is the century, YY is the year, MM is 

the month and DD is the day.

Cooling Water Intake Structure Data Submission Date

The submission date of any Cooling Water Intake 

Structure Data. The date data must be provided in 

CCYY-MM-DD format where CC is the century, YY is 

the year, MM is the month and DD is the day.

Source Water Baseline Biological Characterization Data 

Submission Date

The submission date of any Source Water Baseline 

Biological Characterization Data. The date data must be 

provided in CCYY-MM-DD format where CC is the 

century, YY is the year, MM is the month and DD is the 

day.

New Facilities – Alternative Requirements Provision 

Request Approval Date

The approval date of any request under the Alternative 

Requirements provision as defined under 40 CFR 125.85 

or 40 CFR 125.135. The date data must be provided in 

CCYY-MM-DD format where CC is the century, YY is 

the year, MM is the month and DD is the day.

CWA Section 316(a) Thermal Variance Information on NPDES Permit Application or Notice of Intent

Thermal Variance Unit

This is the unit of measure (e.g., oF or oC of discharged 

effluent, oF or oC different between discharged effluent 

and receiving waterbody, oF or oC different between 

discharged effluent and inlet water source) associated 

with numeric value of the alternative effluent limitation 

granted.

Thermal Variance Granted

This is a flag indicating whether the permitting authority 

has granted the permittee a CWA 316(a) variance for the 

controlling NPDES permit.

Thermal Variance Value This is the numeric value of the alternative effluent 

limitation granted.

Thermal Variance Date

This is the date when the permitting authority granted 

the permittee a CWA 316(a) variance for the controlling 

NPDES permit. The date data must be provided in 

CCYY-MM-DD format where CC is the century, YY is 

the year, MM is the month and DD is the day.

Thermal Variance Study Date

This is the date when the facility submitted new 

studies/data based on actual operation experience to 

support the continuation of the variance. The date data 

must be provided in CCYY-MM-DD format where CC 

is the century, YY is the year, MM is the month and DD 

is the day.

Compliance Monitoring Activity (Discharge Monitoring Report, and Pretreatment SIU Periodic Compliance 

Reports in Municipalities without an Approved Pretreatment Program)
Permitted Feature The identifier assigned for each location at which 

conditions are being applied.

Limit Set The unique identifier tying the DMR form to its Limit 

Set record.

Parameter Code The unique code/description identifying the parameter 

reported on the DMR.

Monitoring Location The code/description of the monitoring location at which 

the sampling occurred for a DMR parameter.

Monitoring Period End Date

The date that the monitoring period for the values 

covered by this DMR form ends. The date data must be 

provided in CCYY-MM-DD format where CC is the 

century, YY is the year, MM is the month and DD is the 

day.

NODI

The unique code/description that indicates the reason 

that “No Discharge” or “No Data” was reported in place 

of the DMR value.

Value The DMR value number reported on the DMR form.

Concentration Units/ Quantity Units

The code/description representing the unit of measure 

applicable to quantity or concentration limits and 

measurements as entered by the user on the DMR form.

Value Type

The unique code/description identifying a DMR value 

type (i.e. Quantity 1, Quantity 2, Concentration 1, 

Concentration 2, Concentration 3).

Qualifier The unique code identifying the limit value operator 

(e.g., <, =, >).

Civil Penalty Amount Assessed

For civil judicial Enforcement Actions, the dollar 

amount of the penalty assessed against the defendant(s) 

as specified in the final entered Consent Decree or Court 

Order. For Administrative Enforcement Actions, it is 

the dollar amount of the penalty assessed in the 

Consent/Final Order.

Civil Penalty Amount Collected

For civil judicial Enforcement Actions, the dollar 

amount of the penalty collected from the defendant(s). 

For Administrative Enforcement Actions, it is the dollar 

amount collected of the penalty assessed in the 

Consent/Final Order.

5. EPA prioritization of base data needed to support the tool (e.g., limit data needed to 

enable e-DMR).

All permit required, system required and programmatic data would have to be loaded in 

the national system. For example limits, limit sets, limit values do not exist for eNOI data 

entered into OW’s system. Some state eNOI data may exist in the national system where the 

states utilize the national system for records.