Page **1** of **79** 

### Appendix A to **P a**  **rt 127 -**  **Minimum S et of NPDES**  **D ata**  The following two tables identify th e minimum set of NPDES data that authorized states, tribes, territories must enter or transfer to EPA’s national NPDES data sy stem as well as what NPDES

- regulated entities must electronically report to the designated initial recipient ( authorized NPDES program or EPA) [see 40 CFR 127.2(b)]. Authorized NPDES programs will be th e data provider in the event the regulated entity is covered b y a waiver from electronic reporting

. Use of these two tables en sure s that there is consistent and complete reporting nationwide, and expeditious collection and processing of the data, thereb y m aking it more accurate and timely

. Taken together, these data standardizations and the corresponding electronic reporting requirements in 40 CFR parts 3, 1 22, 123, 124, 125, 127, 403, and 503 are designed to save the NPDES authorized programs considerable resources, make reporting easier for NPDES

- regulated entities, streamline permit renewals (as permit writers ty picall y review previous noncompliance events during permit renewal), ensure full exchange of NPDES program data between states and EPA to the pub lic, improve environmental decision

- making, and protect human health and the environment.

Authorized NPDES programs may also require NPDES regulated entities to submit more data than what is listed in this appendix. The authorized NPDES program can require NPDES regulated entities to submit these “non

- a ppendix A” data on paper , electronically , or attachments to electronic notices and reports filed in compliance with this part
.
**Instructions:** Table 1 of this appendix provides the list of data sources and minimum submission frequencies for the ten different NPDES Data Groups. Table 2 of this appendix provides the data that must be electronically reported for each of these NPDES Data Groups

. The use of each data element is determined by identifying the number(s) in the column labeled “NPDES Data Group Number” in Table 2 and finding the corresponding “NPDES Data Group Number” in Table 1. For example, a value of “ 1” in Table 2 means that this d ata element is required in the electronic transmission of data from the NPDES program to EPA ( Core NPDES Permitting, Compliance, and Enforcement Data)

. Likewise, a value of “1 through 10 ” in Table 2 means that this data element is required in all ten NPDES data groups. NPDES regulated entities that have no historical record ( e.g. , “greenfield” facilities) do not need to provide data elements that rely on historical data elements. For the purposes of this a ppendix, the term ‘sewage sludge’ [see 40 CFR 503.9 (w)] also refers to the material that is commonly referred to as ‘biosolids.’ EPA does not have a regulatory definition for biosolids but this material is commonly referred to as sewage sludge that is placed on, or applied to the land to use the beneficial properties of the material as a soil amendment, conditioner, or fertilizer. EPA’s use of the term ‘biosolids’ in this a ppendix is to confirm that information about beneficially used sewage sludge (a.k.a. biosolids) is part of the data collected in this a ppendix

.Page **2** of **79 Table 1**  **: Data Sources and Regulatory Citations 1**  **NPDES Data**  **Group Number**  **2 NPDES Data Group**  **Program Area**  **Data Provider Minim** **um Frequency**  **3**

1 Core NPDES Permitting, Compliance, and Enforcement Data [40 CFR parts 122, 123, 403, 503] All NPDES Program Sectors Authorized NPDES Program Within 4 0 day s of the completed activity

or within 4 0 days of receipt of a report from a regulated entity [see § 127.23(a)(1)]

. However, the frequency associated wi th any particular permittee may be considerably less [ e.g. , once every five years for mo st permit information].

2 General Permit Reports [Notice s of Intent to discharge (NOI s ); Notice s of Termination (NOT s ); No Exposure Certifications (N OEs ); Lo w Erosivity Waivers and Other Waivers from Stormwater C ontrols (LEWs)] [40 CFR 122.26(b)(15) , 122.28 and 124.5 ] All NPDES Program Sectors NPDES Permittee P rior to obtaining coverage under a general permit or c onsideration for p ermit e xclusion or waiver from p ermitting , and p ermit c overage termination

. General permits are generally issued once every five years. 3 Discharge Monitoring Report s [40 CFR 122.41(l)(4)] Most NPDES Program Sectors NPDES Permittee At least annual, more frequent submission s may be required by the permit

4 Sewage Sludge/Biosolids Annual Program Report s [40 CFR part 503] Sewage Sludge/Biosolids NPDES Regulated Sewage Sludge/Biosolids Generator and Handler Annual

5 Concentrated Animal Feeding Operation (CAFO) Annual Program Reports [40 CFR 122.42(e)(4)] CAFO CAFO Annual

6 Municipal Separate Storm Sewer System (MS4) Program Report s [40 CFR 122.34(g)(3) and 122.42(c)] MS4 NPDES Permittee Year two and year four of permit coverage (Small MS4), Annual (Medium and Large

MS4)Page **3** of **79 Table 1**  **: Data Sources and Regulatory Citations 1**  **NPDES Data**  **Group Number**  **2 NPDES Data Group**  **Program Area**  **Data Provider Minim** **um Frequency**  **3**

7 Pretreatment Program Report s [40 CFR 403.12(i)] Pretreatment POTW Pretreatment Control Authority , Approval Authority for SIUs in Municipalities Without Approved Pretreatment Programs Annual

8 Significant Industrial User Compliance Reports in Municipalities Without Approved Pretreatment Programs [40 CFR 403.12(e) and (h)] Pretreatment Significant Industrial User Bi

- Annual

9 Sewer Overflow Event Reports [40 CFR 122.41(l)(6) and (7)] Sewer Overflows NPDES Permittee Within 5 days of the time the permittee becomes aware of the se wer overflow event (health or environment endangerment), Monitoring report frequency specific in permit (all other sewer overflow events) 10 CWA s ection 316(b) Annual Report s [40 CFR part 125 , subpart J ] CWA s ection 316(b) NPDES Permittee Annual

**1** Entities regulated by a NPDES permit will comply with all reporting requirements in their respective NPDES permit. **2** Use the “NPDES Data Group Number” in this table and the “NPDES Data Group Number” column in Table 2 of this appendix to identify the source of the required data entry
. E PA notes that electronic systems may use additional data to facilitate electronic reporting as well as management and reporting of electronic data

. For example, NPDES permittees may be required to enter their NPDES permit num ber (“NPDES ID ”

– NPDES Data Group 1 and 2 ) into the applicable electronic reporting system in order to identify their permit and submit a Discharge Monitoring Report ( DMR

- NPDES Data Group 3 ). Additionally, NPDES regulated entities may be required to enter and submit data to update or correct erroneous data. For example, NPDES permittees may be required to enter ne w data regarding the Facility Individual First Name and Last Name (NPDES Data Group 1 and 2 ) wi th their DMR submission when there is a facility personnel change.Page **4** of **79 3**  The applic able reporting frequency is specified in the NPDES permit or control mechanism, which may be mo re frequent than the minimum frequency specified in this table.Page **5** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  **Basic Facility Inform ation**  [Note: As indicated in the “CWA, Regulatory, or Other Citation” column, some of these data elements apply to Significant Indus trial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including non - domestic wa stewater delivered by truck, rail, and dedicated pipe or other means of transportation) to one or more POTWs and to regulated entities or locations that generate, process, or receive biosolids or sewage sludge .] Facility T ype of Ownership The unique code/description identifying the type of facility ( e.g. , s tate g overnment, m unicipal or water district, Federal f acility , tribal facility). This data element is used by EPA ’s national NPDES data system to identify the facility type ( e.g. , POTW, Non

POTW, and Federal). 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 403.8(f), 403.10, 403.12(i) , 503.18, 503.28, 503.48 1,2, 4, and 7

Facility Site Name The name of the facility

. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 122.44(j) , 403.8(f), 403.10, 403.12(i), 503.18, 503. 2 8 , 503. 4 8 1,2, 4, and 7

Facility Site Address The address of the physical facility location

. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 122.44(j) , 403.8(f) , 403.10 , 403.12(i) , 503.18, 503.28, 503.48 1,2, 4, and 7

Facility Site City The name of the city, town, village, or other locality, when identifiable, within which the boundaries (the majority of) the facility site is located. This is not always the same as the city used for USPS mail delivery. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 122.44(j) , 403.8(f) , 403.10, 403.12(i) , 503.18, 503.28, 503.48 1,2, 4, and 7Page **6** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 
Facility Site State The U.S. Postal Service (USPS) abbreviation for the state or state equivalent for the U.S. where the facility is located

. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 122.44(j) , 403.8(f), 403.10, 403.12(i) , 503.18, 503.28, 503.48 1,2, 4, and 7

Facility Site Zip Code The combination of the 5

- digit Zone Improvement Plan (ZIP) code and the 4

- digit extension code (if available) where the facility is located

. 

### This zip code match the “Facility Site City” or the city used for USPS mail delivery

. 122.2 1 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 122.44(j) , 403.8(f), 403.10, 403.12(i) , 503.18, 503.28, 503.48 1,2, 4, and 7

Facility Site Tribal Land Indicator The EPA Tribal Internal Identifier for every unit of land trust allotment (“tribal land”) within Indian Country (i.e., Federally recognized American Indian and Alaska Native tribal entities ) . This unique identifier will identify whether the facility is on tribal l and and the current name of the American Indian tribe or Alaskan Native entity. This unique identifier is different from the Bureau of Indian Affairs tribal code and does not change when a Tribe changes its nam e. 122.21 , 122.21(q), 122.28(b)(2)(ii), 503.18, 503.28, 503.48 1,2, and 4

Facility Site Longitude The measure of the angular distance on a meridian east or west of the prime meridian for the f acility. The format for this data element is d ecimal d egrees ( e.g. , - 77.029289 ) and the WGS84 standard coordinate system. T his data element will also be used to d escribe the two - dimensional area (polygon) regulated by a municipal storm sewer system (M S4 ) NPDES permit through use of multiple latitude and longitude coordinates

. For MS4 the polygon data should provide a reasonable estimate of the MS4 boundaries. This data element can also be system generated w hen the Facility Site Address, Facility Site City, and Facility Site State data elements can be used to generate accurate longitude and latitude values. (Note: “P ost Office Box ” addresses and “Rural Route” addresses are generally not geocodable ). 122.21 , 122.21(q), 122.28(b)(2)(ii) , 503.18, 503.28, 503.48 1,2, and 4Page **7** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Facility Site Latitude The measure of the angular distance on a meridian north or south of the equator for the f acility. The format for this data element is d ecimal d egrees ( e.g. , 38.893829 ) and the WGS84 standard coordinate system

. This data element will also be used to describe the two - dimensional area (polygon) regulated by a municipal storm sewer system (MS4) NPDES permit through use of multiple latitude and longitude coordinates

. This data element can also be system generated when the Facility Site Address, Facility S ite City, and Facility Site State data elements can be used to generate accurate longitude and latitude values. (Note: “Post Office Box” addresses and “Rural Route” addresses are generally not geocodable). 122.21 , 122.21 (q), 122.28(b)(2)(ii), 503.18, 503.2 8, 503.48 1,2, and 4

Facility Contact Affiliation Type The affiliation of the contact with the facility ( e.g. , "Ow ner," “Operator,” or "Main Contact"). This is a unique code/description that identifies the nature of the individual's affiliation to the fa cility. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 403.8(f), 403.10, 403.12(i), 503.18, 503.28, 503.48 1,2, 4, and 7

Facility Contact First Name The given name of an individual affiliated with this facility. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 403.8(f), 403.10, 403.12(i), 503.18, 503.28, 503.48 1,2, 4, and 7

Facility Contact Last Name The surname of an individual affiliated with this facility. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 403.8(f), 403.10, 403.12(i), 503.18, 503.28, 503.48 1,2, 4, and 7Page **8** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 
Facility Contact Title The title held by an individual in an organization affiliated with this facility. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 403.8(f), 403.10, 403.12(i) , 503.18, 503.28, 503.48 1,2, 4, and 7

Facility Contact E

- Mail Address The business e

- mail address of the designated individual affiliated with this facility. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii) , 403.8(f), 403.10, 403.12(i) , 503.18, 503.28, 503.48 1,2, 4, and 7

Facility Organization Formal Name The legal name of the person, firm, public organization, or other entity that operates the facility . This name may or may not be the same name as the facility. The operator of the facility is the legal entity that controls the facility’s operation rather than the facility or site manager. This data element should not use a colloquial name . This field is optional for MS4 permittees. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 403.8(f), 403.10, 403.12(i) , 503.18, 503.28, 503.48 1,2, 4, and 7

**Basic Perm** **it Inform**  **ation** [Note: As indi cated in the “CWA, Regulatory, or Other Citation” column, some of the se data elements also apply to Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including non

- domestic wastewater delivered by truck, rail, and dedicated pipe or other means of transportation) to one or more POTWs and to regulated entities or locations that generate, process, or receive biosolids or sewage sludge .]Page **9** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

NPDES ID This is the unique identifier for the NPDES permit or control mechanism for NPDES regulated entities or Unpermitted ID for an unpermitted facility

. This data elements is used for compliance monitoring activities, violation determinations, and enforcement actions. This data element also applies to Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (incl uding non

- domestic wastewater delivered by truck, rail, and dedicated pipe or other means of transportation) to one or mo re POTWs in states where the POTW is the Control Authority

. 122.2, 122.21, 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii) , 122.34(g)(3), 122 .41(l)(4)(i), 122.41(l)(6) and (7), 122.41(m)(3), 122.42(c), 122.42(e)(4), 123.26, 123.41(a), 125.96, 125.97(g), 125.98, 125.138(b), 401.14, 403.10, 403.12(e), 403.12(h), 403.12(i), 503.18, 503.28, 503.48 1,2 , 3, 4, 5, 6, 7, 8, 9, 10

Master General Permit Number The unique identifier of the master general permit, which is linked to a General Permit Covered Facility. This data element only applies to facilities regulated by a master general permit. 122.2, 122.21, 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 1 22.34(g)(3), 122.41(l)(4)(i), 122.41(l)(6) and (7), 122.41(m)(3), 122.42(c), 122.42(e)(4), 123.26, 123.41(a), 403.1 0, 403.12(e), 403.12(h), 403.12(i), 503.18, 503.28, 503.48 1,2

Permit T ype The unique code/description identifying the type of permit [ e.g. , NPDES Individual Permit , NPDES Master General Permit , General Permit Covered Facility , State Issued Non

-NPDES General Permit , Individual IU Permit (Non

-NPDES) , Individual State Issued Permit (Non

-NPDES) ]. 122.2, 122.21, 122.21(j)(6), 122.21(q), 122.28(b) (2)(ii), 403.10 1,2Page **10** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Permit Com

ponent This will identify one or more applicable NPDES subprograms ( e.g. , pretreatment,

CAFO, CSO, POTW, biosolids/sewage sludge, stormwater) for the permit record. This field is only required when the permit includes one or mo re NPDES subprograms. 122.2, 122.21, 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 403.10 1,2

Permit Issue Date This is the date the permit was issued. The date mu st be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.46 1

Permit Effective Date This is the date on which the permit is effective. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.46 , 122.21, 122.21(j)(6), 122.21(q), 403.10 1 Permit Modification/Amendment Date This is the date on which the permit was modified or amended. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.62, 122.63, 403.10 1

Permit Expiration Date This is the date the permit will expire. The date mu st be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.46 , 122.21, 122.21(j)(6), 122.21(q), 403.10 1
Permit Termination Date This is the date the permit was terminated. The date mu st be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.64 , 403.10 1 Permit Major/Minor Status Indicator This code/description identifies the permit status as “M ajor” or “Nonmajor” (a.k.a. “Minor”). This data element is initially system generated and defaults to “Minor”. T he mo st recent permit status is copied w hen the permit is reissued

. 122.2 1
Permit Major/Minor Status Start Date The date that the p ermit became its current Major/Minor status. Initially system

generated to match effective date. The date mu st be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.2 1
Permit Application Total Design Flow This is the design flow rate that a permitted facility was designed to accommodate, in millions of gallons per day ( MGD ). This is only required for wastewater treatment plants

. 122.21 , 122.28(b)(2)(ii), 403.10(f), 1,2
Permit Application Total Actual Av erage Flow This is the annual average daily flow rate that a permitted facility will likely accommodate at the start of its permit term, in MGD. This is only required for wa stewater treatment plants. 122.21, 122.28(b)(2)(ii), 122.41 , 403.10(f) 1,2Page **11** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 
Com plete Permit Application/NOI Received Date This is the date on which the complete application for an individual NPDES permit was received or a complete Notice of Intent (NOI) for coverage under a master general permit was received

. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. This data element can be system generated when the com plete NOI is electronically received by the NPDES program . 122.21 , 122.28(b)(2)(ii), 403.10(f) 1

Permit Application/NOI Received Date This is the date on which the application for an individual NPDES permit was received or a Notice of Intent (NOI) for coverage under a master general permit was received

. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the mo nth, and DD is the day

. This data element can be system generated when the NPDES permit application or NOI is electronically received by the NPDES program. 122.21 , 122.28(b)(2)(ii), 403.10(f) 1

Permit Status This is a unique code/description that identifies the permit status ( e.g. , Effective, Expired, Administratively Continued, Pending, Not Needed, Retired, Denied, and Terminated)

. This is system generated for all statuses except “Not Needed, ” which must be user entered

. 122.21, 122.21(j)(6), 122 .21(q), 122.64, 122.46 , 403.10(f) 1

Master General Permit Industrial Category These are the one or more unique codes/descriptions that identify the one or more industrial categories covered by the master general permit. This field is required for master general permits only. 122.21, 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 403.10(f) 1

Permit Issuing Organization Type This is the type of organization issuing a permit ( e.g. , County , Federal , Local , Municipal , Regional , State , Tribal )

. 122.21, 122.21(j)(6), 122.21(q), 12 3 .4 1 , 403.10(f) 1Page **1 2**  of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

DMR Non

- Receipt Turns non - r eceipt tracking for compliance monitoring submission s [ e.g. , discharge mo nitoring reports (DMRs)] “ on” or “ off ” for non - major permits (a.k.a. “minors”)

. This field is always “ on” for major permit s. This data element is initially system generated (defaults to “on”) and the most recent value is copied when the permit is reissued . . This data element will also be used to track non

- receipt tracking of periodic compliance mo nitoring data [ 40 CFR 403.12(e) and (h)] for Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including non

- domestic wastewater delivered by truck, rail, and dedicated pipe or other means of transportation) to one or mo re POTWs in states whe re EPA or the State is the Control Authority)

. 123.45 , 403.10(f) 1

DMR Non

- Receipt Start Date This is the date on which the permit’s “on” or “off” period for DMR Non

- Receipt tracking status began. Initially system

- generated to match effective date. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day. This data element will also be used to track non

- receipt tracking of periodic compliance monitoring data [ 40 CFR 403.12(e) and (h)] f or Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including non

- domestic wastewater delivered by truck, rail, and dedicated pipe or other means of transportation) to one or more POTWs in states where EPA or the State is the Control Authority). 123.45 , 403.10(f) 1

Reportable Noncompliance T racking Turns reportable noncompliance (RNC) tracking “ on” or “ off ” for non - major permits (a.k.a. “minors”)

. This data element is initially system generated (defaults to “on”) and the most recent value is copied w hen the permit is reissued

. 123.45 , 403.10(f) 1 Reportable Noncompliance Tracking Start Date This is the date on which the permit’s “on” or “off” period for Reportable Noncompliance Tracking status began. Initially system
- generated to match effective date. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day. 123.45 , 403.10(f) 1Page **13** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Applicable Effluent Limitations Guideline s The applicable effluent limitations guideline s and new source performance standards in the NPDES permit ( e.g. , p art 414

- Organic chemicals, plastics, and synthetic fibers point source category)

. This data element also applies to SIUs and CIUs that discharge (including non

- domestic wastewate r delivered by truck, rail, and dedicated pipe or other means of transportation) to one or more POTWs in states where the POTW is the Control Authority

. 122.21, 122.21(j)(6), 122.21(q), 122.44 , 403.10(f) 1

Permit Com

pliance Tracking Status This is a unique code/description that indicates whether the permit is currently “ on” or “ off ” for compliance tracking purposes. This data element is initially system generated (defaults to “on”) and the most recent value is copied when the permit is reissued

. 122.2 1, 122.21(j)(6), 122.21(q), 123.45 , 403.10(f) 1

Permit Com

pliance Tracking Status Start Date This is the date on which the permit’s “ on” or “ of f ” period for compliance tracking status began. Initially system

- generated to match effective date. The date mu st be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.21, 122.21(j)(6), 122.21(q), 123.45 , 403.10(f) 1

RNC Status (Manual) The status of reportable noncompliance (RNC) as it was entered by the regulatory authority for the official Quarterly Noncompliance Report (QNCR) or NPDES Noncompliance Report (NNCR). This data element can also be revised by the regulatory authority. 122.21, 122.21(j)(6), 122.21(q), 123.45 , 403.10(f) 1
RNC Status (Manual) Year The year associated with the RNC Status (Manual) being reported . This data element is used for the official Quarterly Noncompliance Report (QNCR) or NPDES Noncompliance Report (NNCR). This data element can also be revised by the regulatory authority. 122.21, 1 22.21(j)(6), 122.21(q), 123.45 , 403.10(f) 1
RNC Status (Manual) Quarter The quarter associated with the RNC Status (Manual) being reported. This data element is used for the official Quarterly Noncompliance Report (QNCR) or NPDES Noncompliance Report (NNC R). This data element can also be revised by the regulatory authority. 122.21, 122.21(j)(6), 122.21(q), 123.45 , 403.10(f) 1Page **14** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Associated NPDES ID Number If applicable, the unique identifier for each NPDES Permit that is related to another NPDES Permit. For example, this data element identifies the recipient POTW’s NPDES ID for each satellite collection system, the suppliers of biosolids and sewage sludge to a land application site, and the one or more NPDES IDs for other permitted operators at the same construction site or industrial facility. This data element does not apply to municipal storm sewer systems (MS4s) as other data elements create linkages between these entities. 122.2, 122.21, 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 122.41(l)(4)(i), 122.41(l)(6) and (7), 122.41(m)(3), 122.42(e)(4), 123.26, 123.41(a), 503.18, 503.28, 503.48 1 through 5

7, 8, and 9

Associated NPDES ID Number Reason The unique code/description that identifies the reason for the association between two NPDES IDs (e.g., ETP = Effluent Trade Partner , APR = Associated Permit Record , SIP = Switched To An Individual Permit , SGP = Switched To A General Permit This data element does not apply to municipal storm sewer systems (MS4s) as other data elements create linkages between these entities. 122.2, 122.21, 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 122.41(l)(4)(i), 122.41(l)(6) and (7), 122.41(m)(3), 122.42(e)(4), 123.2 6, 123.41(a), 503.18, 503.28, 503.48 1 through 5

7, 8, and 9

Receiving POTW ID This data element will identify for each Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) the unique identifier of the one or more POTWs receiving th e discharge. This includes non - domestic wastewater delivered by truck, rail, and dedicated pipe or other means of transportation to the one or more receiving POTWs . This data element only applies to SIUs and CIUs and will link the industrial discharger to the one or more receiving POTWs. 122.21, 122.21(j)(6), 1,2, and 7

SIC Code The one or more four

- digit Standard Industrial Classification (SIC) codes that represent the economic activities of the facility

. This data element also applies to SIUs and CIUs th at discharge (including non

- domestic waste water delivered by truck, rail, and dedicated pipe or other means of transportation) to one or more POTWs in states where the POTW is the Control Authority . A value of “4952 ” can be sy stem generated for POTWs and T WTDS. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii) , 403.10(f) , 403.12(e), 403.12(h), 403.12(i) , 503.18, 503.28, 503.48 1,2, and 7Page **15** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  SIC Code Primary Indicator This data element will identify the primary economic activity, SIC code, of the facility

. This data element is required for electronic data transfer between state and EPA systems. This data element also applies to SIUs and CIUs that discharge (including non - domestic wastewater delivered by truck, rail, and dedicated pipe or other means of transportation) to one or more POTWs in states where the POTW is the Control Authority

. 122.21, 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 403.10(f) , 403.12(e), 403.12(h), 403.12(i), 503.18, 503.28, 503.48 1,2, and 7

NAICS Code The six

- digit North American Industry Classification System (NAICS) code/description that represents the economic activity of the facility

. This field is optional if the “SIC Code” data element is provided for the facility. EPA SIC/NAICS Data Standard, Standard No. EX000022.2, 6 January 2006, O ffice of Management and Budget, Executive Office of the President, Final Decision on North American Industry Classification System (62 FR 17288), 403.10(f) 1,2, and 7

NAICS Code Primary Indicator This data element will identify the primary economic activity, NAICS code, of the facility . This data element is required for electronic data transfer between state and EPA systems. This field is optional if the “ SIC Code ” data element is provided for the facility. EPA SIC/NAICS Data Standard, S tandard No. EX000022.2, 6 January 2006, Office of Management and Budget, Executive Office of the President, Final Decision on North American Industry Classification System (62 FR 17288), 403.10(f) , 1,2, and 7Page **16** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Permittee Mailing Address The mailing address of the permit holder. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 403.10(f) 1,2

Permittee Organization Formal Name The legal, formal name of the organization that holds the permit. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii) , 403.10(f) 1,2

Permittee City The name of the city, town, or village where the mail is delivered for the permit holder

. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii) , 403.10(f) 1,2

Permittee State The U.S. Postal Service abbreviation that represents the state or state equivalent for the U.S. for the permit holder. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii) , 403.10(f) 1,2

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. 122.21 , 122.21(j)(6), 122.21(q), 122.28(b)(2)(ii), 403.10(f) 1,2Page **17** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Residual Designation Determination Code Under section 402(p)(2)(E) and (6) and 40 CFR 122.26 (a)(9)(i)(C) and (D), the authorized NPDES program or the EPA Regional Administrator may specifically designate stormwater discharges as requiring an NPDES p ermit. In this ‘residual designation’ process the NPDES permitting authority regulates stormwater discharges based on: (1) wasteload allocations that are part of “total maximum daily loads” (TMDLs) that address the pollutant(s) of concern in the stormwater discharges [see 40 CFR 122.26(a)(9)(i)(C)]; or (2) the determination that the stormwater discharge, or category of stormwater discharges within a geographic area, contributes to a violation of a water quality standard or is a significant contributor of po llutants to waters of the United States [see 40 CFR 122.26(a)(9)(i)(D)]. This data element is the unique code/description that identifies the main basis for this residual designation determination. This data element only applies to stormwater permits. 122. 26 (a)(9)(i) (C) and (D) and CWA section 402(p) 1

Electronic Reporting Waiver Type T he unique code/description that identifies whether the authorized NPDES program has granted the permittee a waiver from electronic reporting in compliance with this part (1 = temporary waiver; 2 = permanent waiver). This data element should be left blank if the permittee does not have a waiver from electronic reporting in compliance with this part. 123.26, 123.41(a) and CWA section 308 1

Electronic Reporting Waiver Expirati on Date This is the expiration date for a temporary waiver from electronic reporting in compliance with this part. This data element should be left blank if the permittee has a permanent waiver from electronic reporting or if the permittee does not have a waiver from electronic reporting in compliance with this part. 123.26, 123.41(a) and CWA section 308 1Page **18** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Electronic Submission Ty pe ( General Permit Reports ) This is the unique code/description for each general permit report submitted by the facility or entity. Notices, certifications, and waiver requests covered by this data element are listed in Table 1 in this appendix (i.e., NPDES Data Group 2). This data element describes how each submissio n was electronically collected or processed by the initial recipient [see § 1 27.2(b)]. For example, these unique codes/descriptions include: (1) NPDES regulated entity submits NPDES program data using an EPA electronic reporting system; (2) NPDES regulated entity submits NPDES program data using an authorized NPDES program electronic reporting system ; (3) NPDES regulated entity has temporary waiver from electronic reporting and submits NPDES program data on paper to the authorized NPDES program who then electronically uses manual data entry to electronically process these data; (4) NPDES regulated entity has a permanent waiver from electronic reporting and submits NPDES program data on paper to the authori zed NPDES program who then electronically uses manual data entry to electronically process these data ; ( 5 ) NPDES regulated entity has an episodic waiver from electronic reporting and submits NPDES program data on paper to the authorized NPDES program who then electronically uses manual data entry to electronically process these data; (6) NPDES regulated entity submits NPDES program data on paper in a form that allows the authorized NPDES program to use of automatic identification and data capture technology to electronically process these data; (7) NPDES regulated entity submits NPDES program data using another electronic reporting system ( e.g. , third

party). This data element can sometimes be system generated (e.g., incorporated into an electronic reporting tool). This data element does not identify the electronic submission ty pe of other reports (NPDES Data Groups = 3 through 10 in Table 1), which is tracked by the “ Electronic Submission Type ( Com pliance Monitoring Activity) ” data element. 123.26, 123.41(a) and CWA section 308 1Page **19** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

NPDES Data Group Number This is the unique code/description that identifies the ty pes of NPDES program data that are required to be reported by the facility. This corresponds to Table 1 in this appendix { e.g. , 3 = Discharge Monitoring Report [40 CFR 122.41(l)(4)] }. This data element can be system generated . This data element will record each NPDES Data Group that the facility is required to submit. For example, when a POTW is required to submit a Discharge Monitoring Report, Sewage Sludge/Biosolids Annual Program Report, Pretreatment Program Report, and Sewer Overflow/Bypass Event Report, the values for this data element for this facility will be 3, 4, 7, and 9. The following general permit r eports will have the following values for this data element: 2a = Notice of Intent to discharge (NOI); 2b = Notice of Termination (NOT); 2c = No Exposure Certification (NOE); and 2d = Lo w Erosivity Waiver or Other Waiver from Stormwater Controls (LEW). 122.2, 122.21, 122.21(j)(6), 122.21(q) , 122.28(b)(2)(ii), 122.34(g)(3), 122.41(l)(4)(i), 122.41(l)(6) and (7), 122.41(m)(3), 122.42(c), 122.42(e)(4), 123.26, 123.41(a), 403.10, 403.12(e), 403.12(h), 403.12(i), 503.18, 503.28, 503.48 and CWA section 308 1

**Narrative Condition s**  **and Permit Schedules Inform**  **ation** [Note: As indicated in the “CWA, Regulatory, or Other Citation” column, these data elements also apply to Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including non

- domestic wastewater delivered by truck, rail, and dedicated pipe or other means of transportation) to one or more POTWs in states whe re EPA or the State is the Control Authority]

. Permit Narrative Condition Code The unique code/description that identifies the type of narrative condition. 122.47 , 403.10(f) 1 Permit Narrative Condition Number This number uniquely identifies a narrative condition and its elements for a permit. 122.47 , 403.10(f) 1
Permit Schedule Date The date on which a permit schedule event is due to be completed and against which compliance will be measured. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.47 , 403.10(f) 1
Permit Schedule Actual Date The date on which the permittee achieved the schedule event. The date mu st be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.47 , 403.10(f) 1Page **20** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Required Report Received Date The date on which the regulatory authority receives a report from the permittee indicating that a s chedule d e vent was completed ( e.g. , the s tart of c onstruction) or the date on which the regulatory authority received the required report. The date mu st be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.47 , 403.10(f) 1

Permit Schedule Event Code The unique code/description indicating the one or more event s with which the permittee is scheduled to comply. 122.47 , 403.10(f) 1 **Perm itted Feature**  **Information** [Note: These ‘Permitted Feature’ data elements are only required to be submitted for permits that require limits or outfall monitoring for stationary point sources. Additionally, a s indicated in the “CWA, Regulatory, or Other Citation” column, some of these data elements apply to Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including non

- domestic wastewater delivered by truck, rail, and dedicated pipe or other means of transportation) to one or more POTWs in states whe re EPA or the State is the Control Authority]

. Permitted Feature Application Actual Average Flow

(MGD) The average flow that a permitted feature will actually discharge or transmit, in MGD,

at the start of its permit term

. This data element does not apply to regulated entities that do not discharge ( e.g. , some biosolids/sewage sludge generators) and entities that only discharge stormwater. This data element may also not apply to some intermittent dischargers. 122.21 , 122.28(b)(2)(ii) , 403.10(f) 1 ,2

Permitted Feature I dentifier (Permit) The identifier assigned for each location at which conditions are being applied (e.g., external outfall)

. This data element also identifies cooling water intake structures. 122.21 , 122.28(b)(2)(ii) , 403.10(f) 1 ,2
Permitted Feature Ty

pe The code/description that uniquely identifies the type of permitted f eature ( e.g. e xternal outfall, sum , intake structure, cooling water intake structure ). 122.21 , 122.28(b)(2)(ii), 4 03.10(f) 1 ,2 Receiving Waterbody Name for Permitted Feature The name of the waterbody that is or will likely receive the discharge from each permitted feature. 122.21 , 122.28(b)(2)(ii) 1 ,2
Permitted Feature Longitude The measure of the angular distance on a meridian east or west of the prime meridian for the permitted feature

. The format for this data element is d ecimal d egrees ( e.g. , - 77.029289 ) and the WGS84 standard coordinate system. 122.21 , 122.28(b)(2)(ii) 1 ,2Page **21** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Permitted Feature Latitude The measure of the angular distance on a meridian north or south of the equator for the permitted feature

. The format for this data element is d ecimal d egrees ( e.g. , 38.893829 ) and the WGS84 standard coordinate system. 122.21 , 122.28(b)(2)(ii) 1 ,2 **Limit Set Inform**  **ation** (Note: These ‘ Limit Set ’ data elements are only required to be submitted for permits that require limits or outfall monitoring for stationary point sources. Additionally, as indicated in the “CWA, Regulatory, or Other Citation” column, these data elements apply to Significant Industrial Users (SIUs ) and Categorical Industrial Users (CIUs) that discharge (including non

- domestic wa stewater delivered by truck, rail, and dedicated pipe or other means of transportation) to one or more POTWs in states whe re EPA or the State is the Control Authority). Limit Set Designator The alphanumeric field that is used to designate a particular grouping of parameters within a limit set. 122.45 , 403.10(f) 1 Limit Set Ty

pe The unique code/description identifying the type of limit set ( e.g. , s cheduled,

unscheduled). 122.45 , 403.10(f) 1 Modification Effective Date (Limit Set) The effective date of the permit modificati on that updated or created a limit s et. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the mo nth, and DD is the day. 122.45, 403.10(f) 1
Modification T ype (Limit Set) The type of permit modification that updated or created this limit set ( e.g. , major mo dification , minor mo dification, permit authorized change). 122.45, 403.10(f) 1 Initial Monitoring Date The date on which monitoring starts for the first monitoring period for the limit set , T his date will be blank for unscheduled l imit s ets. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.45 , 403.10(f) 1Page **22** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Initial DMR Due Date The date that the first com pliance monitoring submission ( e.g. , DMR) for the limit set is due to the regulatory authority . T his date will be blank for unscheduled l imit s ets. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the mo nth, and DD is the day

. This data element will also b e used to tra ck non

- receipt tracking of periodic compliance monitoring data [ 40 CFR 403.12(e) and (h)] for Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including non

- domestic wastewater delivered by truck, rail, and dedicated pipe or other means of transportation) to one or more POTWs in states where EPA or the State is the Control Authority). 122.45 , 403.10(f) 1

Number of Report Units The number of months covered in each compliance monitoring period ( e.g. , monthly = 1, semi

- annually = 6, quarterly = 3). 122.45 , 403.10(f) 1

Number of Submission Units The number of months between compliance monitoring submissions ( e.g. , monthly = 1, semi

- annually = 6, quarterly = 3). This data element will be blank for unscheduled limit sets. For example, if the permittee was required to submit monthly reports every quarter, the number of report units would be one ( i.e. , mo nthly) and th e number of submission units would be three ( i.e. , three months of information in each submission). 122.45 , 403.10(f) 1

Limit Set Status The status of the l imit s et ( e.g. , a ctive , inactive)

. Limit s ets will not have violations generated when a l imit s et i s i nactive unless an e nforcement a ction l imit is present. subpart C of 122 , 403.10(f) 1 Limit Set Status Start Date The date that the Limit Set Status started. The date mu st be provided in YYYY

- MM

DD format where YYYY is the year, MM is the month, and DD is the day

. 123.45 , 403.10(f) 1 **Limit Inform**  **ation** (Note: These ‘Limit’ data elements are only required to be submitted for permits that require limits or outfall monitoring for stationary point sources. Additionally, as indicated in the “CWA, Regulatory, or Other Citation” column, some of these data elements apply to Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including non

- domestic wastewater delivered by truck, rail, and dedicated pipe or other means of transportation) to one or more POTWs in states whe re EPA or the State is the Control Authority). Monitoring Location Code The unique code/description of the monitoring location at which sampling should occur for a limit parameter. 122.45 , 403.10(f) 1Page **23** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Limit Season Number Indicates the season of a limit and is used to enter different seasonal limits for the same parameter within a single limit start and end date. 122.45 , 403.10(f) 1
Limit Start Date The date on which a limit starts being in effect for a particular parameter in a limit set. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.45 , 403.10(f) 1

Limit End Date The date on which a limit stops being in effect for a particular parameter in a limit set. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.45 , 403.10(f) 1 Change of Limit Status Indicator The unique code/description that describes circumstances affecting limits, such as formal enforcement actions or permit modifications. subpart C of 122 , 403.10(f) 1

Limit Stay

T ype The unique identifier of the type of stay applied to a limit ( e.g. , X, Y, Z), which

indicates whether the limits do not appear on the compliance monitoring report ( e.g. , DMR) at all, are treated as monitor only, or have a stay value in effect during the period of the stay. 122.45 , 403.10(f) 1

Limit Stay

Start Date The date on which a limit stay begins. The date must be provided in YYYY

- MM

- DD

format where YYYY is the year, MM is the month, and DD is the day

. 124.19 , 403.10(f) 1
Limit Stay

End Date The date on which a limit stay is lifted. The date mu st be provided in YYYY

- MM

- DD

format where YYYY is the year, MM is the month, and DD is the day

. 124.19 , 403.10(f) 1 Reason for Limit Stay The text that represents the reason a stay was applied to a permit. 124.19 , 403.10(f) 1 Stay Limit Value The numeric limit value imposed during the period of the stay for the limit; if entered, during the stay period, the system will use this limit value for calculating compliance, rather than the actual limit value that was stayed. 124.19 , 403.10 (f) 1
Limit T ype The unique code/description that indicates whether a limit is an enforceable, or alert limit ( e.g. , action level, benchmark) that does not receive effluent violations. 122.45 , 403.10(f) 1 Enforcement Action ID The unique identifier for the e nforcement a ction that imposed the e nforcement a ction limit; this data element helps uniquely tie the limit record to the f inal o rder record. 122.45 , 403.10(f) 1Page **24** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Final Order ID The unique identifier for the Final Order that im posed the Enforcement Action limit; this data element ties the limit record to the Final Order record in the database. 122.45 , 403.10(f) 1 Modification Effective Date The effective date of the permit modification that created this limit. The date must b e provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.62 , 403.10(f) 1
Modification T ype The type of permit modification that created this limit ( e.g. major, minor, permit authorized change). 122.62 , 403.10(f) 1
Limit Parameter Code The unique code/description identifying the parameter being limited and/or monitored. 122.41(j) , 403.10(f) 1
Limit Months The months that the limit applies. 122.46 , 403.10(f) 1
Limit Value Type The indication of the limit value type ( e.g. , Quantity 1, Concentration 2). 122.45(f) , 403.10(f) 1 Limit Quantity or Concentration Units The unique code/description representing the unit (s) of measure applicable to quantity or concentration limits as entered by the user. 122.45(f) , 403.10(f) 1
Statistical Base Code The unique code/description representing the unit of measure applicable to the limit and compliance monitoring activity ( e.g. , DMR) values entered by the user ( e.g. , 30

- day average, daily maximum). 122.45(d) , 403.10(f) 1 Optional Monitoring Code The code/description that indicate s when mo nitoring is optional but not required ( e.g. , DMR Non

- Receipt violation generation will be suppressed for optional monitoring). 122.45 , 403.10(f) 1 Limit Value Qualifier The unique code identifying the limit value operator ( e.g., “ < ” , “ = ” , “ > ” ). 122.45 , 403.10(f) 1 Limit Value The actual limit value number from the Permit or Enforcement Action Final Order. 122.45 , 403.10(f) 1Page **25** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  **Sewage Sludge/Biosolids Inform ation on**  **NPDES Permit Application or Notice of Intent**  (Note: As indicated in the “CWA, Regulatory, or Other Citation” column, these data elements apply to Treatment Works Treating Domestic Sewage whose sewage sludge use or disposal practices are regulated by part 503 .) Biosolids/Sewage Sludge Management Facility Ty pe The unique code/description that identifies whether the facility was issued a permit as a biosolids/sewage sludge generator, processor, or end user ( e.g. , land application site, surface disposal site, incinerator). For the Sewage Sludge/Biosolids Annual Report this data element is also the unique code/description that identifies an off

- site facility or location receives biosolids or sewage sludge from this facility. This data element is also required for the Sewage Sludge/Biosolids Annual Report. 122.21(q) , 122.28(b)(2)(ii), 503.18, 503.28, 503.48 1,2, and 4

Biosolids or Sewage Sludge Treatment Processes (Permit) The one or more unique codes/descriptions that identifies the biosolids or sewage sludge treatment process or processes at the facility. For example, this may include treatment processes in the following categories: preliminary operations ( e.g. , sludge grinding and degritting), thickening (concentratio n), stabilization, anaerobic digestion, aerobic digestion, composting, conditioning, disinfection ( e.g. , beta ray irradiation, gamma ray irradiation, pasteurization), dewatering ( e.g. , centrifugation, sludge drying beds, sludge lagoons), heat drying, thermal reduction, and methane or biogas capture and recovery. 122.21(q)(6), 122.28(b)(2)(ii) 1.2

Biosolids or Sewage Sludge Form

(Permit) The one or more unique codes/descriptions that identify the nature of each biosolids and

sewage sludge material generated by the facility in terms of whether the material is a biosolid or sewage sludge and whether the material is ultimately conveyed off

- site in bulk or in bags. The facility will separately report the form for each biosolids or sewage sludge management practi ce and pathogen class

. 122.21(q)(6), 122.28(b)(2)(ii) 1.2

Biosolids or Sewage Sludge Management Practice (Permit) The one or more unique codes/descriptions that identify the type of biosolids or sewage sludge management practice or practices ( e.g. , land application, surface disposal, incineration) used by the facility. The facility will separately report the practice for each different form of biosolids and sewage sludge generated by the facility and pathogen class

. 122.21(q)(6), 122.28(b)(2)(ii) 1 .2Page **26** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Biosolids or Sewage Sludge Pathogen Class (Permit) The one or more unique codes/descriptions that identify the pathogen class or classes ( e.g. , Class A, Class B , Not Applicable ) for biosolids or sewage sludge generated by the facility. The facility wil l separately report the pathogen class for each biosolids or sewage sludge management practice used by the facility and for each biosolids or sewage sludge form. 122.21(q)(6), 122.28(b)(2)(ii) 1.2

Biosolids or Sewage Sludge Vector Attraction Reduction Op tions (Permit) The one or more unique codes/descriptions that identify the option(s) used by the facility for vector attraction reduction. See a listing of these vector attraction reduction options at 40 CFR 503.33(b)(1) through (11). The facility will separately report the vector attraction reduction options for each biosolids or sewage sludge management practice used by the facility and for each biosolids or sewage sludge form as well as by each biosolids or sewage sludge pathogen class. 122.21(q)(6), 122.28(b)(2)(ii) 1.2

Biosolids or Sewage Sludge Pathogen Reduction Option s (Permit) The one or more unique codes/descriptions that identify the option(s) used by the facility to control pathogens ( e.g. , Class A

– Alternative 1, Class A

– Alternative 2, Class A

– Alternative 3, Class A

– Alternative 4, Class A

– Alternative 5, Class A

– Alternative 6, Class B

– Alternative 1, Class B

– Alternative 2, Class B

– Alternative 3, or pH Adjustment (Domestic Septage). The facility will separately rep ort the pathogen reduction options for each biosolids or sewage sludge management practice used by the facility and by each biosolids or sewage sludge form as well as by each biosolids or sewage sludge pathogen class. 122.21(q)(6), 122.28(b)(2)(ii) 1.2

B iosolids or Sewage Sludge Amount (Permit) This is the amount (in dry metric tons) of biosolids or sewage sludge applied to the land, prepared for sale or give

- away in a bag or other container for application to the land, or placed on an active sewage sludge unit in the preceding 365

- day period. This identification will be made for each biosolids or sewage sludge management practice used by the facility and by each biosolids or sewage sludge form as well as by each biosolids or sewage sludge pathogen class. 122.21 (q) , 122.28(b)(2)(ii) 1,2

**Animal Feeding Operation Inform ation on**  **NPDES Permit Application or Notice of Intent** Page **27** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Facility CAAP Designation A unique code ( e.g. , “Yes”, “No”) to indicate whether the facility includes Concentrated Aquatic Animal Production (CAAP ). 12 2.21(i)(2 ), 122.24, 122.25, 122.28(b)(2)(ii) 1,2 Facility CAFO Type The unique code/description that identifies whether the facility includes a small, medium or large Concentrated Animal Feeding Operation (CAFO)

. 122.2 1(i)(1), 122.23, 122.28(b)(2)(ii) 1,2 CAFO Designation Date The date on which the facility is designated as a small or medium Concentrated Animal Feeding Operation (CAFO). The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.23 1

CAFO Designation Reason The reason(s) the State Director or the Regional Administrator used to designate an animal feeding operation as a small or medium CAFO. [Ed note: Large and medium CAFO definitions are in 40 CFR 122.23(b)]. This text field can include the following factors: (1) the size of the AFO and the amount of wastes reaching waters of the United States; (2) the location of the AFO relative to waters of the United States; (3) the means of conveyance of animal wastes and proce ss waste waters into waters of the United States; (4) th e slope, vegetation, rainfall, and other factors affecting the likelihood or frequency of discharge of animal wastes manure and process waste waters into waters of the United States; and ( 5 ) o ther rel evant factors

. 122.23(c) 1

CAFO Animal T ype s The unique code/description that identifies the animal type(s) at the facility ( e.g. , beef cattle, broilers, layers, swine weighing 55 pounds or more, swine weighing less than 55 pounds, mature dairy cows, dairy heifers, veal calves, sheep and lambs, horses, ducks, turkeys, other)

. 122.2 1(i)(1) (v), 122.28(b)(2)(ii) 1,2

CAFO Animal Maximum Number s The estimated maximum number of each type of animal in open confinement or housed under roof (either partially or totally) which are held at the facility for a total of 45 days or more in a 12 month period

. 122.2 1(i)(1)(v) , 122.28(b)(2)(ii) 1,2 CAFO Animal Maximum Number s in Open Confinement The estimated maximum number of each type of animal in open confinement which are held at the facility for a total of 45 days or more in a 12 month period. 122.2 1(i)(1)(v) , 122.28(b)(2)(ii) 1,2Page **28** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 
CAFO MLPW The unique code/description that identifies the type of CAFO manure, litter, and process wastewater generated by the facility i.e. in a 12 month period

. 122.2 1(i)(1)(viii ) , 122.28(b)(2)(ii) 1,2

CAFO MLPW Amounts The estimated amount of CAFO manure, litter, and process wastewater generated by the facility i.e. in a 12 month period

. 122.2 1(i)(1)(viii ) , 122.28(b)(2)(ii) 1,2

CAFO MLPW Amount s Units The unit ( e.g. , tons, gallons) for the estimated maximum amount of CAFO manure, litter, and process wastewater generated by the facility i.e. in a 12 month period

. 122.2 1(i)(1)(viii ) , 122.28(b)(2)(ii) 1,2

CAFO MLPW Transferred The estimated maximum amount of CAFO manure, litter, and process wastewater generated by the facility i.e. in a 12 month period that is transferred to other persons

. The units for this data element will be the same as the units for the “ CAFO MLPW Amount s” data element. 122.2 1(i)(1)( i x) , 122.28(b)(2)(ii) 1,2
Total Number of Acres Available for Land Application Total number of acres under the control of the applicant that are available for land application of CAFO manure, litter, and process wastewater

. 122.21(i)(1)(vii), 122.28(b)(2)(ii) 1,2

CAFO MLPW Containment and Storage Ty pe The unique code/description describing the one or more ty pe s of CAFO manure, litter, and process wastewater containment and storage ( e.g. , lagoon, holding pond, evaporation pond, anaerobic lagoon, storage lagoon, evaporation pond, aboveground storage tanks, belowground storage tanks, roofed storage shed, concrete pad, im pervious soil pad, other) at the facility

. 122.2 1(i)(1)(vi), 122.28(b)(2)(ii) 1,2

CAFO MLPW Containment and Storage Maximum Capacity Amounts The estimated maximum capacity of each CAFO manure, litter, and process wastewater containment and storage type at the facility. 122.2 1(i)(1)(vi), 122.28(b)(2)(ii) 1,2Page **29** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  CAFO MLPW Containment and Storage Maximum Capacity Amounts Unit The unit for the estimated maximum capacity of each CAFO manure, litter, and process wa stewater containment and storage ty pe at the facility ( e.g. , gall ons). 122.2 1(i)(1)(vi), 122.28(b)(2)(ii) 1,2
**Construction and Industrial Storm water Inform**  **ation [from the per**  **mitting authority derived from the No Exposure Certification,**  **Low Erosivity Waiver,**  **and Other Waiver**  **From Storm** **water Controls (see Exhibit 1 to 40**  **CFR 122.26(b)(15) ]** 

No Exposure Certification Approval Date This is the date on which the No Exposure Certification (NOE) wa s authorized by the NPDES permitting authority

. Submission of a No Exposure Certification means that the facility does not require NPDES permit authorization for its stormwater discharges due to the existence of a condition of “ no exposure. ” A condition of no exposure exists at an industrial facility when all industrial materials and activities are protected by a storm resistant shelter to prevent exposure to rain, snow, snowmelt, and/or runoff and the operator complies with all re quirements at 40 CFR 122.26(g)(1) through (4)

. This date is provided by the permitting authority. The date must be provided in YYYY

- MM

- DD format where YYYY i s the year, MM is the month, and DD is the day

. 122.26 (g) 1

Lo w Erosivity Waiver or Other Waiver From Stormwater Controls Approval Date The NPDES Stormwater Phase II Rule allows NPDES pe rmitting authorities to accept low erosivity waivers and other waivers from stormwater controls (LEWs) for small construction sites. The waiver process exempts small construction sites (disturbing under five acres) from NPDES permitting requirements when the rainfall erosivity factor is less than five during the perio d of construction activity as well as other criteria [see Exhibit 1 to 40 CFR 122.26(b)(15) ]

. This is the date when the NPDES permitting authority granted such waiver, based on information from the entity requesting the waiver; this date is provided by the permitting authority. The date must be provided in YYYY

- MM

- DD format , where YYYY is the year, MM is the month, and DD is the day

. Exhibit 1 to 40 CFR 122.26(b)(15) 1

**Construction Storm water Inform**  **ation on NPDES Permit**  **Application, Notice of Intent, or Wa iver Request [**  **including construction activity requiring permit coverage under**  **40 CFR 122.26(b)(14)(x)**  **]**Page **30** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Total Area of the Site This is an estimate of the total area of the construction site at the time of permit application (in acres) . This data element is only required for individual construction stormwater permit applications. Values under 5 acres will be reported to the nearest tenth of an acre or nearest quarter acre. Authorized NPDES programs will have the discretion to choose whether permittees should report to the nearest tenth of an acre or nearest quarte r acre for values under 5 acres

. 122.26 (c)(1)(ii)(B ) 1

Total Activity Area (Construction) This is the estimate of the total area of the construction activities at the time of permit application or filing of notice of intent to be covered under a general permit (in acres). Areas of construction activity include areas of clearing, grading, and/or excavation and areas of construction support activity ( e.g. , concrete or asphalt batch plants, equipment staging yards, material storage areas, excavated materials disposal areas, borrow areas). Values under 5 acres will be reported to the nearest tenth of an acre or nearest quarter acre. Authorized NPDES programs will have the discretion to choose whether permittees should report to the nearest tenth of an acre or nearest quarter acre for values under 5 acres. 122.26 , 122.28(b)(2)(ii) 1,2

Post

- Construction Total Im pervious Area This is the estimate of total impervious area of the site after the construction addressed in the permit application is completed (in acres). This estimate is made at the time of the permit application. This data element is only required for individual constructio n stormwater permit applications. Values under 5 acres will be reported to the nearest tenth of an acre or nearest quarter acre. Authorized NPDES programs will have the discretion to choose whether permittees should report to the nearest tenth of an acre o r nearest quarter acre for values under 5 acres. 122.26(c)(1)(ii)(E) 1

Proposed Stormwater Best Management Practices for Construction Activities This is the one or more unique code s that list the most important p roposed measures, including best management practices, to control pollutants in stormwater discharges from construction activities. This data element includes temporary s tructural measures ( e.g. , check dams, construction road stabilization, silt fences), v egetative measures ( e.g. , mulching, seeding, sodding, straw /hay bale dikes), and permanent structures ( e.g. , land grading, riprap slope protection, streambank protection). This data element field is only required for individual construction stormwater permit applications. 122.26(c)(1)(ii)(C) 1Page **31** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Post

- Construction Stormwater Best Management Practices for Construction Activities This is the one or more unique code s that list the most important p roposed long

- term measures and permanent structures to control pollutants in stormwater discharges , which will occur after the completion of construction operations . The codes for this data element include long

- term control measures ( e.g. , c leaning and removal of debris after major storm events , h arvesting vegetation when a 50 percent reduction in the original open water surface area occurs , s ediment cleanout , r epairing embankment s, side slopes , and control structure s) and permanent structures ( e.g. , land grading, riprap slope protection, streambank protection , ponds, we tlands, infiltration basins, sand filters, filter strips). This data element is only required for individual construction stormwater permit applications. 122.26(c)(1)(ii)(D) 1

Soil and Fill Material Description This is a text field describes the nature of fill material and existing data describing soils or the quality of the discharge. This data element is only required for individual construction stormwater permit applications. 122.26(c)(1)(ii)(E) 1
Runoff Coefficient of the Site (Post

- Construction) This is an estimate of the overall runoff coefficient of the site after the construction addressed in the permit application is completed . This data element is only required for individual construction stormwater permit applications. 122.26(c)(1)(ii)(E) 1
Estimated Construction Project Start Date The estimated start date for the construction project covered by the NPDES permit. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the mo nth, and DD is the day

. 122.26, 122.28(b)(2)(ii) 1,2
Estimated Construction Project End Date The estimated end date for the construction project covered by the NPDES permit. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the mo nth, and DD is the day

. 122.26, 122.28(b)(2)(i i) 1,2 **Industrial Storm water Information on NPDES Permit Application**  **[ excluding**  **construction activity requiring permit coverage under**  **40 CFR 122.26(b)(14)(x)]** Page **32** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Total Surface Area Drained (Industrial) This is an estimate of the total surface area drained at the facility at the time of permit application (in acres) . This data field is only required for individual industrial stormwater permit applications. Values under 5 acres will be reported to the nearest tenth of an acre or nearest quarter acre. Authorized NPDES programs will have the discretion to choose whether permittees should report to the nearest tenth of an acre or nearest quarter acre for values under 5 acres. 122.26(c)(1)(i)(B) 1

Total Impervious Surface Area (Industrial) This is the estimate of the total im pervious area at the facility at the time of permit application (in acres). This data element is only required for individual industrial stormwater permit applications. Values under 5 acres will be reported to the nearest tenth of an acre or nearest quarter acre. Authorized NPDES programs will have the discretion to choose whether permittees should report to the nearest tenth of an acre or nearest quarter acre for values under 5 acres. 122.26(c)(1)(i)(B) 1

Proposed Stormwater Be st Management Practices (Industrial) This is the one or more codes that identify the structural and non

- structural control measures (including treatment) to control pollutants in stormwater discharges from industrial activities

. This data element includes long

- term measures ( e.g. , good housekeeping of waste
- handling and waste

- storage areas , c ollecting debris and yard material , proper management of v ehicle wash and equipment maintenance areas) and permanent structures ( e.g. , covers, pads, diversion berms or channels , v egetative buffer strips , e rosion prevention and sediment control such as land grading, riprap slope protection, streambank protection) to control pollutants in stormwater discharges . This data element is only required for individual industrial s tormwater permit applications. 122.26(c)(1)(i)(B) 1

**Municipal Separate Storm Sewer System**  **(MS4) Inform**  **ation on NPDES Permit Application or Notice of Intent** MS4 Permit Class The unique code/description that identifies the size of the MS4 permit holder ( e.g. , Phase I = large or medium MS4s, Phase II = small MS4s). 122.26 , 122.28(b)(2)(ii) 1 ,2Page **33** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Unique Identifier for Each Municipality Covered Under MS4 Permit The unique identifier for each municipality covered under MS4 permit. Use of this identifier allow s for greater geographic resolution for the MS4 components being tracked . This unique identifier does not change over time. Use of this unique identifier is similar to how the ‘ Permitted Feature Identifier (Permit)’ data element is used to distinguish betwe en permitted features. 122.21(f) , 122.26(d) 122.28(b)(2)(ii) , 122.34(g)(3) , and 122.42(c) 1,2, 6

MS4 Public Education Program The one or more unique codes/descriptions that identifies the educational materials the permittee intend s to distribute or equivalent outreach activities the permittee will im plement to inform the target audience about the impacts of stormwater discharges and the steps the public can take to reduce stormwater pollutants

. 122.21(f) , 122.26(d)(2)(iv) (A)(6), (B) (5) and (6) , and (D)(4); 122.28(b)(2)(ii) , 122.34(b)(1) , 122.34(d)(1)(i) 1,2

MS4 Measurable Goals Associated With Public Education Program The one or more unique codes/descriptions that identifies measurable goals associated with the public education program s including, as appropriate, the months and years in which the permittee will undertake required actions, including interim milestones and the frequency of the action. This data element only applies to Phase II MS4s. 122.34(d)(1)(ii) , 122.28(b)(2)(ii) 1, 2

M S4 Public Involvement and P articipation Program The one or more unique codes/descriptions that identifies how the permittee intends to involve the public and at minimum comply with State, Tribal, and local public notice requirements to implement its public involvement and participation program

. 122.21(f) , 122.26(d)(2)(iv), 122.28(b)(2)(ii) , 122.34(b)(2) , 122.34(d)(1)(i) 1,2

MS4 Measurable Goals for the Public Involvement and P articipation Program The one or more unique codes/descriptions that identifies the measurable goals associated with the public involvement and participation program including, as appropriate, the months and years in which the permittee will undertake required actions, including interim milestones and the frequency of the action. This data element only applies to Phase II MS4s

. 122.28(b)(2)(ii) 122.34(d)(1)(ii) 1, 2Page **34** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

MS4 Illicit Discharge Detection and Elimination The one or more unique code s/description s that identif y how the permittee will comply with Illicit Discharge Detection and Elimination requirements, including (at a minimum): (1) the status of the permittee’s 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 ; (2) the status of the ordinance or other regulatory mechanism to prohibit non

- stormwater discharges into the permittee’s MS4; (3) the procedures and actions the permittee takes to enforce the prohibition of non

- stormwater discharges to the permittee’s MS4; (4) the status of the program that identifies the procedures and actions the permittee will take to detect and address non

- stormwater discharges, including illegal dumping, to the permittee’s MS4; and (5) the status of procedures and acti ons the permittee will take to inform public employees, businesses and the general public of hazards associated with illegal discharges and improper disposal of waste. 122.21(f) , 122.26(d)(1)(iii)(B), 122.26(d)(2)(i)(B) and (C), 122.26(d)(2)(iv)(B), 122.28 (b)(2)(ii) , 122.34(b)(3)(ii)(A)

– (D), 122.34(d)(1)(i) 1,2

MS4 Measurable Goals Associated With Illicit Discharge Detection and Elimination Program The one or more unique code s/description s that identifies the measurable goals associated with the illicit discharge detection and elimination program, including, as appropriate, the months and years in which the permittee will undertake required actions, including interim milestones and the frequency of the action. This data element only applies to Phase II M S4s. 122.34(d)(1)(ii) 1,2

MS4 Construction Site Stormwater R

unoff Control The one or more unique codes/descriptions that identif y how the permittee will comply with the Construction Site Runoff Control requirements, including (at a minimum): (1) status of the ordinance or other regulatory mechanism to require erosion and sediment controls, including sanctions to ensure compliance ; (2) status of requirements for construction site operators to implement appropriate erosion and sediment control BMPs and control waste at the construction site that may cause adverse impacts to water quality; (3) status of procedures for site plan review that incor porate consideration of potential water quality impacts; (4) status of procedures for receipt and consideration of information submitted by the public; and (5) status of procedures for site inspection and enforcement of control measures. 122.21(f), 122.26 (d)(2)(iv)( D ), 122.28(b)(2)(ii), 122.34(b)(4)(ii) , 122.34(d)(1)(i) 1,2Page **35** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  MS4 Measurable Goals Associated with the Construction Site Stormwater Runoff Control Program The one or more unique code s/descripti ons that identify the measurable goals associated with the construction program, including, as appropriate, the months and years in which the permittee will undertake required actions, including interim milestones and the frequency of the action. This data element only applies to Phase II MS4s. 122.34(d)( 1)(ii) 1,2

MS4 Post

- Construction Stormwater Management In New Development And Redevelopment The one or more unique code s/description s that identif y how the permittee will comply with the Post

- Construction Stormwater Management in New Development and Redevelopment requirements, including (at a minimum): (1) status of ordinance or other regulatory mechanism to address post

- construction runoff from new d evelopment and redevelopment projects; (2) how the permittee plans to address stormwater runoff from new development and redevelopment projects that disturb a minimum of greater than or equal to one acre (including if the permittee requires on

- site retention of stormwater; and (3) status of a plan to ensure adequate long

- term operation and maintenance of BMPs for controlling runoff from new development and redevelopment projects

. 122.21(f), 122.26(d)(2)( iv)(A)( 2 ), 122.28(b)(2)(ii), 122.34(b)(5) , 122.34(d)(1)(i) 1,2

MS4 Measurable Goals Associated with the Post

Construction : Stormwater Management Program The one or more unique code s/description s that identif y the measurable goals associated with the post

- construction program, including, as appropriate, the months and years in which the permittee will undertake required actions, including interim milestones and the frequency of the action. This data element only applies to Phase II MS4s. 122.34(d)(1)(ii) 1, 2

MS4 Pollution Prevention/ Good Housekeeping for Municipal Operations Program The one or more unique code s/description s that identif y how the permittee will comply with the Pollution Prevention/Good Housekeeping requirements

. 122.21(f), 122.26(d)(2)(iv)(A) (1), (2) and (3) , 122.28(b)(2)(ii), 122.34(b)(6)(i) , 122.34(d)(1)(i) 1,2

MS4 Additional Measures The one or more unique code s/description s that identif y any other additional measures that are required by the permit such as controls to b e consistent with the assumptions and requirements of any available wasteload allocation prepared by a state and approved by EPA

. This data element is optional if there are no MS4 additional measures. 122.28(b)(2)(ii) , 122.34(b), 122.34(d) 122.44(d)(1)(vii)(B) 1,2Page **36** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  **POTW Information on NPDES Permit Application or Notice of Intent** 

Name of Collection Sy stem This is the unique name of each collection system that provid es flow to the permittee

. This includes unincorporated connector districts and satellite collection systems, which are sanitary sewers owned or operated by another entity that conveys sewage or industrial waste water to this permittee . This data element applies to POTWs. 122.1(b) and 122.21(j)(1)(iv) , 122.28(b)(2)(ii) 1,2
Owner Type of Collection Sy stem The unique code/description that identifies the ownership type for each unique collection system that provides flow to the permittee ( e.g. , municipality owned, privately owned). This includes unincorporated connector districts and satellite collection systems

. This data element applies to POTWs. 122.1(b) and 122.21(j)(1)(iv) , 122.28(b)(2)(ii) 1,2

Collection System Identifier This is the NPDES permit number (“NPDES ID”) for each unique collection system that provides flow

to the permittee . If there is no NPDES permit number for the collection system this data element will be a unique identifier for each collection system that p rovides flow

to the permittee. This includes unincorporated connector districts and satellite collection systems

. This data element applies to POTWs. 122.1(b) and 122.21(j)(1)(iv) , 122.28(b)(2)(ii) 1,2
Population of Collection Sy stem This is the estimated population for each unique collection system that provides flow to the permittee . This includes unincorporated connector districts and satellite collection systems
. This data element applies to POTWs. 122.1(b) and 122.21(j)(1)(iv) , 122.28(b)(2)(ii) 1,2
Percentage of Collection Sy stem That Is a Com bined Sewer System F or each unique collection system that provides flow to the permittee , this is the

estimated percentage of the collection system that is a combined sewer system. This includes unincorporated connector districts and satellite collection systems . This estimated percentage is calculated separately for each unique collection system that provides flow

to the permittee and is based on the service population of each unique collection sy stem. T his data element applies to POTWs. 122.1(b) and 122.21(j)(1)(iv) and (vii), 122.28(b)(2)(ii) 1,2

POTW Wastewater Treatment Technology Level Description This data element describes the level of wastewater treatment technology [ e.g. , raw discharge (no treatment), primary treatment, secondary wastewater treatment, advanced treatment] used at the facility. This data element only applies to POTWs. 122.21(j)(3)(iii), 122.28(b)(2)(ii) and CWA section 516 1,2Page **37** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 
POTW Wastewater Disinfection Technology The o ne or more unique codes/descriptions that describe the types of disinfection technology that are used at the facility ( e.g. , chlorination, ozonation, ultraviolet disinfection). This data element will also use a code/description to identify if this facility is using dechlorination, which may be required if the facility uses chlorination for disinfection. This data element only applies to POTWs. 122.21(j)(3)(iii), 122.28(b)(2)(ii) 1,2

POTW Wastewater Treatment Technology Unit Operations The one or more unique codes/descriptions that describe the wastewater treatment technology unit operations ( e.g. , grit removal, flow equalization, complete mix activated sludge secondary treatment, trickling filter, facultative lagoon, biological nitrification) used at the facility. This data element is required for POTWs that have a design flow capacity equal to or above 10 million gallons per day (MGD) and is optional for POTWs with a design flow capacity below

10 MGD. 122.21(j)(2)(ii)(A), 122.28(b)(2)(ii) and CWA secti on 516 1,2

**Combined Sewer Overflow Inform**  **ation** [Note: All Phase II and post

- Phase II combined sewer system NPDES permittees are required to complete and implement a long

- term CSO control plan (LTCP) as described in EPA’s Combined Sewer Overflow (CSO) Control Policy (19 April 1994; 59 Federal Register 18688

- 18698). These data will be updated by the authorized NPDES program on a timely basis as changes occur with the combined sewer system and the LTCP as well as with the P OTW’s implementation and compliance with the LTCP.]

L ong - T erm CSO C ontrol P lan Permit Requirements and Compliance This data element uses a unique code/description that identifies whether the permit requires the permit holder to complete and im plement a LTCP and w

hether the permit holder is in compliance with these permit requirements. 122.41(h), 122.43, 123.41(a) and CWA section 402 (q)(1) , Com bined Sewer Overflow (CSO) Control Policy (5 9 FR 18688

- 18698, 19 April 1994 ) 1Page **38** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Nine Minimum CSO Controls Developed This data element uses a unique code/description to identify by number each of the nine minimum control measures outlines in the CSO Control Policy that the permit holder has implemented in compliance with the applicable permit and/or enforcement mechanism . These unique codes are: (1) Proper operation and regular maintenance programs for the sewer system and the CSOs ; (2) Maximum use of the collection system for storage ; (3) Review and modification of pretreatment requirements to assure CSO impacts are mini mized ; (4) Maximization of flow to the publicly owned treatment works for treatment ; (5) Prohibition of CSOs during dry weather ; (6) Control of solid and floatable materials in CSOs ; (7) Pollution prevention ; (8) Public notification to ensure that the publ ic receives adequate notification of CSO occurrences and CSO im pacts ; and (9) Monitoring to effectively characterize CSO impacts and the efficacy of CSO controls . For example, i f the permit holder has only developed the “Maximum use of the collection syste m for storage ” minimum control measure then the permitting authority will record “2” for this data element. Likewise, i f the permit holder has developed all nine minimum control measures then permitting authority will record 1, 2, 3, 4, 5, 6, 7, 8, and 9 f

or this data element. 122.41(h), 122.43 , 123.41(a) and CWA section 402 (q)(1) , Com bined Sewer Overflow (CSO) Control Policy (59 FR 18688

- 18698, 19 April 1994) 1Page **39** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Nine Minimum CSO Controls Implemented This data element uses a unique code/description to identify by number each of nine minimum control meas ures outlined in the CSO Control Policy that the permit holder has implemented in compliance with the applicable permit and/or enforcement mechanism. These unique codes are: (1) Proper operation and regular maintenance programs for the sewer system and the CSOs; (2) Maximum use of the collection system for storage; (3) Review and modification of pretreatment requirements to assure CSO impacts are minimized; (4) Maximization of flow to the publicly owned treatment works for treatment; (5) Prohibition of CSOs during dry weather; (6) Control of solid and floatable materials in CSOs; (7) Pollution prevention; (8) Public notification to ensure that the public receives adequate notification of CSO occurrences and CS O im pacts; and (9) Monitoring to effectively characterize CSO impacts and the efficacy of CSO controls. For example, if the permit holder has only developed the “Maximum use of the collection system for storage” minimum control measure then the permitting authority will record “2” for this data element. Likewise, if the permit holder has developed all nine minimum control measures then permitting authority will record 1, 2, 3, 4, 5, 6, 7, 8, and 9 for this data element

. 122.41(h), 122.43 , 123.41(a) and CWA section 402 (q)(1) , Com bined Sewer Overflow (CSO) Control Policy (59 FR 18688

- 18698, 19 April 1994) 1

LTCP Submission and Approval Type This data element uses a unique code/description to identify whether the most recent version of the LTCP was received and approved by the permitting authority ( e.g. , most recent version of the LTCP was submitted by permit holder and was approved by the permitting authority, most recent version of the LTCP was submitted by permit holder but has not yet been approved by permi tting authority, permit holder is required to submit a revised LTCP but the permitting authority has not yet received the revised LTCP from the permit holder, permit holder has not yet submitted a LTCP). 122.41(h), 122.43 , 123.41(a) and CWA section 402 (q) (1) , Com bined Sewer Overflow (CSO) Control Policy (59 FR 18688

- 18698, 19 April 1994) 1

LTCP Approval Date This data element identifies the date w hen the permitting authority approved the most current version of the LTCP. This data element will be updated for each revision to the LTCP. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.41(h), 122.43 , 123.41(a) and CWA section 402 (q)(1) , Com bined Sewer Overflow (CSO) Control Policy (59 FR 18688

- 18698, 19 April 1994) 1Page **40** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Enforceable Mechanism and Schedule to Complete LTCP and CSO Controls This data element uses a unique code/description to identify whether the permit holder is on an enforceable schedule to complete all required LTCP and CSO controls and the ty pe of enforcement mechanism. 122.41(h), 122.43 , 123.41(a) and CWA section 402 (q)(1) , Com bined Sewer Overflow (CSO) Control Policy (59 FR 18688

- 18698, 19 April 1994) 1

Actual Date Completed LTCP and CSO Controls This data element identifies the date by which the permit holder completed construction and implementation of all currently required LTCP and CSO controls. This data element will be updated for each revision to the LTCP and CSO controls

. The date must be p rovided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.41(h), 122.43 , 123.41(a) and CWA section 402 (q)(1) , Com bined Sewer Overflow (CSO) Control Policy (59 FR 18688

- 18698, 19 April 1994) 1

Approved Post

Construction Com

pliance Monitoring Program This data element uses a unique code/description to indicate whether the permit holder is currently implementing an approved post

- construction compliance monitoring program. 122.41(h), 122.43 , 123.41(a) and CWA section 402 (q)(1) , Com bined Sewer Overflow (CSO) Control Policy (59 FR 18688

- 18698, 19 April 1994) 1

Other CSO Control Measures with Com pliance Schedule This data element uses a unique code/description to identify whether the permit holder

has other CSO control mea sures specified in a compliance schedule, beyond those identified in the nine minimum controls, long

- term CSO control plan (LTCP), or a plan for sewer system separation. 122.41(h), 122.43 , 123.41(a) and CWA section 402 (q)(1) , Com bined Sewer Overflow (CSO) Control Policy (59 FR 18688

- 18698, 19 April 1994) 1Page **41** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  **Pretreatm ent**  **Information on NPDES Per mit Application**  **or Notice of Intent**  **(this includes per mit application data required for all new and existing**  **POTWs [40 CFR 122.21(j)(6)] [Note: These data will be**  **added or updated through the Annual P retreatm**  **ent Program Report, see**  **40 CFR 403.12(i)**  **, as**  **needed. It is also important to note that the ‘Associated NPDES ID Number’ identifies the receiving POTW’s NPDES per**  **mit number for ea ch**  **industrial user. ]**  Pretreatment Program Required Indicator The unique code/description that describes whether the permitted municipality is required to develop or implement a pretreatment program (in accordance with 40 CFR 403)

. 122.28(b)(2)(ii), 122.44(j) 1 Pretreatment Program Approval or Modification Date The date the pretreatment program wa s approved or substantially modified

. This data element can be system generated by carrying forward the most recent date (approval or mo dification). The date must be provided in YYYY

- MM

- DD f ormat where YYYY is the year, MM is the month, and DD is the day

. 122.28(b)(2)(ii), 403.8(a) and (b), 403.11 1
Pretreatment Program Modification Ty

pe The unique code describing the type of substantial modification to a POTW

Pretreatment Program, which includes the initial start of a pretreatment program. 122.28(b)(2)(ii), 403.8(a) and (b), 403.11 , 403.18 1

Industrial User Ty

pe The unique code/description that identifies the type of each industrial user discharging

to a POTW [ e.g. , Significant Industrial User (SIU), Standard Categorical Industrial Users (CIU), Non

- Significant Categorical Industrial User (NSCIU), and M iddle Tier Categorical Industrial User (MTCIU)]. This data element is at the permit or control mechanism level and i s required for each SIU, CIU, NSCIU, and MTCIU. This data element also applies to S IUs and CIUs that discharge non

- domestic wastewater by truck, rail, and dedicated pipe or other means of transportation to one or more POTWs. 122.21(j)(6), 122.28(b)(2)(ii), 122.44(j) , 403.12(i) 1,2,7

Significant Industrial User Subject to Local Limits The unique code ( e.g. , “Yes”, “No”) that identifies for each Significant Industrial User (SIU) or Categorical Industrial User (CIU) discharging to a POTW ( including non

domestic waste water delivered by truck, rail, and dedicated pipe or other means of transportation) whether the SIU is subject to local limits. 122.21(j)(6 ) , 122.28(b)(2)(ii), 122.44(j ), 403.12(i) 1 ,2,7Page **42** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Significant Industrial User Subject to Local Limits More Stringent Than Categorical Standards The unique code ( e.g. , “Yes ” , “No ” ) that identifies for each Categorical Industrial User (CIU) discharging to a POTW ( including non

- domestic wastewater delivered by truck, rail, and dedicated pipe or other means of tran sportation) whether the CIU is subject to one or more local limits that are more stringent than the applicable categorical standards. 122.21(j)(6 ) , 122.28(b)(2)(ii), 122.44(j ), 403.12(i) 1 ,2,7

Applicable Categorical Standards This data element will identify for each Categorical Industrial User (CIU) discharging to a POTW ( including non

- domestic wastewater delivered by truck, rail, and dedicated pipe or other means of transportation) the applicable categorical standard(s) by its 40 CFR part number ( e.g. , Metal Finishing

– p art 433, Electrical and Electronic Com ponents

– Part 469 ) . This data element will track the one or more applicable categorical standards even when the CIU is subject to one or more local limits that are mo re stringent than the applicable categorical standards

. 122.21(j)(6 ) , 122.28(b)(2)(ii), 122.44(j ), 403.12(i) 1 ,2,7

Significant Industrial User Wastewater Flow

Rate This data element will identify for each Significant Industrial User (SIU) or Categorical

Industrial User (CIU) that is discharging to a POTW ( including non

- domestic wa stewater delivered by truck, rail, and dedicated pipe or other means of transportation) the estimated maximum monthly average wastewater flow rate (in gallons per day). 122.21(j) (6 ) , 122.28(b)(2)(ii), 122.44(j ) 1 ,2

Industrial User Causing Problems at POTW The unique code/description that identifies for each Significant Industrial User (SIU) or Categorical Industrial User (CIU) whe ther it caused or contributed to any problems (including upset, bypass, interference, pass

- through) at a POTW within the past four and one

- half calendar 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, and bypass) at the receiving POTW’s effluent discharge or biosolids/sewage sludge management. This data element also applies to SIUs and CIUs that discharge non

- domes tic wastewater by truck, rail, and dedicated pipe or other means of transportation to one or more POTWs. 122.21(j)(6 ) , 122.28(b)(2)(ii), 122.44(j )(2)(ii), 403.5(c) 1 ,2

Receiving RCRA Waste The unique code/description that identifies whether a POTW has received RCRA hazardous waste by truck, rail, or dedicated pipe within the last three calendar years. 122.21(j)(7 ) , 122.28(b)(2)(ii), 122.44(j ) 1 ,2Page **43** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Receiving Remediation Waste The unique code/description that identifies whether the POTW has received RCRA or CERLCA waste from off

- site remedial activities within the last three calendar years. 122.21(j)(7 ) , 122.44(j ) 1 ,2

Control Authority Identifier This data element identifies the one or more Control Authorities for each S ignificant Industrial User (SIU) or Categorical Industrial User (CIU) . When the Control Authority is a POTW this data element will use the POTW’s NPDES ID. There will also be a unique identifier for each state and EPA Region for SIUs and CIUs when they are the Control Authority. 122.28(b)(2)(ii), 122.44(j) 1 ,2
**Cooling Water Intake Information on NPDES Permit Application or Notice of Intent**  Cooling Water Intake Applicable Subpart The unique code/description that identifies the regulatory subpart the facility is subject to [ e.g. , 1 = New

Facility under 40 CFR part 125 , subpart I, 2 = New Offshore Oil and G as Facility under 40 CFR part 125 , subpart N, 3 = Existing Facility under 40 CFR part 125 , subpart J, 4 = BPJ Facility under 40 CFR 125.80(c) , 40 CFR 125.90(b), 40 CFR 125.130(c), or 40 CFR 401.14 ]

. 122.21(r), 122.28(b)(2)(ii), subpart s I, J, and N of 125 , 401.14 , and CWA section 316(b) 1,2

Design Intake Flow

for Cooling Water Intake Structure (s) D esign Intake Flow (D IF ) means the value , in units of million gallons per day (MGD), assigned to each cooling water intake structure design that corresponds to the maximum instantaneous rate of flow of water the cooling water intake system is capable of withdrawing from a source waterbody. The f acility’s DIF may be adjusted to reflect permanent changes to the maximum flow capability of the cooling water intake system to withdraw

cooling water, including pumps permanently removed from service, flow limit devices, and physical limitations of the piping. DIF does not include values associated with emergency and fire suppression capacity or redundant pumps ( i.e. , back

- up pumps). For new facilities this is the design maximum flow capacity of the cooling water intake structure. See 40 CFR 125.83 and 125 .92. This data element will be reported for each cooling water intake structure, which will have a “Permitted Feature ID.” Specific monitoring protocols and frequency of monitoring will be determined by the Director

. 122.21(r), 122.28(b)(2)(ii), 125.80, 125.86, 125.90, 125.92, 125.95, 125.131, 125.136, 401.14 , and CWA section 316(b) 1 ,2Page **4 4**  of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Actual Intake Flow

for Cooling Water Intake Structure (s) This actual flow value, in units of MGD, is intended to represent on

- the

- ground intake flow for each cooling water intake structure at the facility , as opposed to the DIF, which is based on maximum design flow intake . For existing facility, Actual Intake Flow (AIF) means the average flow rate of water withdrawn on an annual basis by each cooling water intake structure over the past three years. After October 14, 2019 , AIF means the average flow rate of water withdrawn on an annual basis by each cooling water intake structure over the previous five years. Actual intake flow is measured at a location within the cool ing water intake structure that the Director deems appropriate. The calculation of actual intake flow includes days of zero flow . AIF does not include flows associated with emergency and fire suppression capacity. See 40 CFR 125.92. This data element will be reported for each cooling water intake structure, which will have a “Permitted Feature ID.” Specific monitoring protocols and frequency of mo nitoring will be determined by the Director. 122.21(r), 122.28(b)(2)(ii), 125.86,125.92(a), 125.95, 125.136, 401.14 , and CW A section 316(b) 1 ,2

Location T ype for Cooling Water Intake Structure The unique code/description that identifies the location and description for each cooling water intake structure [ e.g. , 1 = shoreline intake description (flushed, recessed), 2 = intake canal, 3 = em

bayment, bank, or cove, 4 = submerged offshore intake, 5 = near shore submerged intake, 6 = shoreline submerged intake , 7 = Offshore Velocity Cap (800 foot minimum distance from shoreline), 8 = other]

. Each cooling water intake s tructure will have its own “Permitted Feature ID.” 122.21(r), 122.28(b)(2)(ii), 125.86, 125.9 5 , 125.136, 401.14 and CW A section 316(b) 1 ,2

Actual Through

- Screen Velocity This is the actual through

- screen velocity (in feet/second) of the water intake through the screen for each cooling water intake structure at an existing facility

. This is the measured average intake velocity as water passes through the structural components of a screen measured perpendicular to the screen mesh during normal operation s. See 40 CFR 125.94. This data element will be reported for each cooling water intake structure, which will have a “Permitted Feature ID.” Specific monitoring protocols and frequency of monitoring will be determined by the Director. 122.21(r), 122.28(b)(2 ), 125.86, 125.94, 125.9 5 , 125.136, 401.14 and CWA section 316(b) 1 ,2Page **45** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Source Water for Cooling Purposes The unique code/description that describes the one or more source water for cooling purpose for each cooling water intake structure [ e.g. , 1 = Ocean, 2 = Estuary, 3 = Great Lake, 4 = Fresh River, 5 = Lake/Reservoir , 6 = contract or arrangement with an independent supplier (or multiple suppliers)]

. Each cooling water intake structure will have its own “Permitted Feature ID.” 122.21(r), 122.28(b)(2)(ii), 1 25.86, 125. 95 , 125.136, 401.14 and CW A section 316(b) 1,2

Cooling Water Intake Structure Chosen Com pliance Method The unique code/description to indicate the one or more compliance method selected

for each cooling water intake structure based on EPA’s CW A section 316(b) regulations or based on BPJ. For new facilities for example, Track I, Track II, alternative requirements, etc. For existing facilities, which of the 40 CFR 125.94(c) compliance options were chosen and reported as part of 40 CFR 122.21(r)(6) , w hether the facility has chosen to comply on an intake basis or facility wide, or whether alternative requirements were requested

. F acilities have the option to comply on a facility wide or on an intake basis

. Each cooling water intake structure will have its own “Permitted Feature ID.” 122.21(r)(6), 122.28(b)(2)(ii), 125.84, 125.85, 125.94, 125.134, 125.135, 401.14 and CWA section 316(b) 1,2

Source Water Baseline Biological Characterization Data: Threatened or Endangered Status For new and existing facilities, a unique code/description that identifies whether there are Federally

- listed threatened or endangered species (or relevant taxa) that mi ght be susceptible to impingement and entrainment at the facility’s cooling water intake structures . This unique code/description will also identify whether designated critical habitat is in the vicinity of facility’s cooling water intake structure
. 122.21(r)(4), 122.28(b)(2), 125.86, 125.95, 125.136, 401.14 and CW A section 316(b) 1,2

**CWA section 316(a) Ther**  **ma l Variance Inform**  **ation on NPDES Permit Application or Notice of Intent** Thermal Variance Request T ype The unique code/description that describe s the thermal variance r equest submitted by the discharger ( e.g. , 1 = new request, 2 = renewal request). 125 , subpart H and CWA section 316(a) 1 Public Notice of Section 316(a) Requests This is the unique code that describe s whether the NPDES permitting authority included the information required under 40 CFR 124.57(a) in the public notice regarding the CWA section 316(a) request. 124.57, 125 , subpart H and CW A section 316(a) 1Page **46** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Thermal Variance Granted Date This is the most recent date when the NPDES permitting authority granted or renewed a CWA section 316(a) variance for the controlling NPDES permit. The date mu st be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.28(b)(2)(ii), subpart H of 125 and CWA section 316(a) 1
**Compliance Monitoring Activity Inform**  **ation (General)**
Com pliance Monitoring Identifier The unique identifier for the compliance monitoring activity performed by the authorized NPDES program and EPA (e.g., inspections). This data element can be system generated. 123.26, 123.41(a) and CWA section 308 1

Permitted Feature Identifier ( Com

pliance Monitoring Activity) The unique identifier for the permitted feature number (s) entered by the user for the inspected or monitored permitted feature(s)

. This data element will use the same number used by ‘ Permitted Feature Identifier (Permit) ’ data element for each compliance monitoring activity permitted feature. This will provide a unique link between each compliance monitoring activity permitted feature and the corresponding NPDES permitted feature. This data element can be left blank if the compliance mo nitoring activity does not involve a permitted feature. For Sewer Overflow/Bypass Event Reports this data element will identify the permitted feature(s ), if any, for each Sewer Overflow/Bypass Identifier . The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the se wer overflows are caused by an extreme weather event ( e.g. , hurricane) that floods the entire se wer system and are too numerous to count. This data element applies to compliance monitoring activities performed by the authorized NPDES program and EPA (e.g., inspections) as well as compliance mo nitoring reports submitted by the NPDES regulated entity (e.g., DMRs, program reports). 122.34(g)(3), 122.41(l)(4)(i), 122.41(l)(6) and (7) , 122.41(m)(3) , 123.26 , 123.41(a) , 122.42(c) , 403.12(e), 403.12(h) and CWA section 308 1, 3, 4, 6, 8, and 9Page **47** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Electronic Submission Ty pe ( Com pliance Monitoring Activity) This is the unique code/description for each report submitted by the NPDES regulated entity. Report submissions covered by the data element are listed in Table 1 in this appendix (i.e., NPDES Data Groups 3 through 10). This data element describes how each submission was ele ctronically collected or processed by the initial recipient [see § 1 27.2(b)]. For example, these unique codes/descriptions include: (1) NPDES regulated entity submits NPDES program data using an EPA electronic reporting system; (2) NPDES regulated entity submits NPDES program data using an authorized NPDES program electronic reporting system ; (3) NPDES regulated entity has temporary waiver from electronic reporting and submits NPDES program data on paper to the authorized NPDES program who then electronical ly uses manual data entry to electronically process these data; (4) NPDES regulated entity has a permanent wa iver from electronic reporting and submits NPDES program data on paper to the authorized NPDES program who then electronically uses manual data entry to electronically process these data ; ( 5 ) NPDES regulated entity has an episodic waiver from electronic reporting and submits NPDES program data on paper to the authorized NPDES program who then electronically uses manual data entry to electronically process these data; (6) NPDES regulated entity submits NPDES program data on paper in a form that allows the authorized NPDES program to use of automatic identification and data capture technology to electronically process these data; (7) NPDES regulated entity submits NPDES program data using another electronic reporting system ( e.g. , third

-party). This data element can sometimes be system generated ( e.g. , incorporated into an electronic reporting tool). This data element does not identify the electronic submission type of general permit reports (NPDES Data Group =2 in Table 1), which is tracked by the
“ Electronic Submission T ype ( General Permit Reports ) ” data element. This data element applies to information submitted by NPDES regulated entities and does not apply to compliance monitoring information generated by authorized NPDES programs and EPA ( e.g. , inspection data). 123.26, 123.41(a) and CWA section 308 1

**Compliance Monitoring Activity Inform ation (**  **General Data Generated from Authorized NPDES**  **Programs and EPA )** Page **48** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Com pliance Monitoring Activity Actual End Date The actual date on which the c om pliance monitoring a ctivity ended. For example, the date of an authorized NPDES program inspection of a facility can be used for this data element. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 123.26, 123.41(a) and CWA section 308 1

Com pliance Monitoring Activity The unique code/description that identifies each com pliance mo nitoring activity taken by the authorized NPDES program ( e.g. , inspection, investigation, information request, offsite records review). 123.26, 123.41(a) and CWA section 308 1
Com pliance Monitoring Ty pe The unique code/description that identifies each com pliance monitoring activity ty pe taken by a regulatory Agency ( e.g. , audit, biomonitoring, case development, diagnostic, evaluation, reconnaissance with s am pling , r econnaissance without s am pling , sampling)

. 123.26, 123.41(a) and

CWA section 308 1

Bio monitoring Test Type The unique code/description that identifies the type of biomonitoring inspection method ( e.g. , acute, chronic, or flow through) and sample type ( e.g. , grab, composite)

. This data element supplements the Compliance Monitoring T ype data e lement. This data element only applies to compliance monitoring activities that involve biomonitoring. 123.26, 123.41(a) and CWA section 308 1

Com pliance Monitoring Action Reason The unique code/description that identifies the reason for the initiation of the compliance monitoring activity ( e.g. , Agency Priority, Citizen Complaint/Tip, Core Program)

. 123.26, 123.41(a) and CWA section 308 1 Was this a State, Federal or Joint (State/Federal) Inspection? This data element identifies if the inspection is a jo int inspection by federal , state , tribal, or territorial personnel

. Only one value for this data element may be used for each compliance monitoring activity [ e.g. , State, Federal, Joint (State/Federal)]. 123.26, 123.41(a) and CWA section 308 1
Programs Evaluated The unique code/description for the one or more programs evaluated or related to the compliance monitoring activity ( e.g. , NPDES Base Program, Biosolids/Sewage Sludge, Pretreatment, and MS4)

. 123.26, 123.41(a) and CWA section 308 1
**Compliance Monitoring Activity Inform**  **ation (Program Data Generated from** **Authorized NPDES Program s and EPA)** Page **49** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Def iciencies Identified Through the Biosolids/Sewage Sludge Com pliance Monitoring This is the unique code/description that that identif ies each deficiency in the facility’s biosolids and sewage sludge program (40 CFR part 503) for each compliance mo nitoring activity ( e.g. , inspections, audits) by the regulatory authority. This data element includes unique codes to identify when the facility f ailed to comply with any applicable permit requirements or enforcement actions

. The values for this data element will distinguish between noncompliance and significant noncompliance (SNC). 1 23.26, 123.41(a), 123.45 and CWA section 308 1

Deficiencies Identified Through the MS4 Com pliance Monitoring This is the unique code/description that that identifies each deficiency in the MS4’s

program to control stormwater pollution for each compliance monitoring activity ( e.g. , inspections, audits) by the regulatory authority. This data element includes unique codes to identify when the MS4 failed to comply with any applicable permit requirements or enforcement actions. The values for this data element will distinguish between noncompliance and significant noncompliance (SNC). 1 23.26, 123.41(a), 123.45 and CWA section 308 1

Def ic iencies Identified Through the Pretreatment Com pliance Monitoring This is the unique code/description that that identifies each deficiency in the POTW ’s

authorized pretreatment program for each pretreatment compliance monitoring activity ( e.g. , inspections, audits) by the regulatory authority. The values for this data element will distinguish between noncompliance and significant noncompliance (SNC). These unique codes include: (1) f ailure to enforce against p ass through and/or interference; (2) f ailure to submit required reports within 30 days ; (3) f ailure to meet compliance sch edule milestones within 90 days; (4) f ailure to issue/reissue control mec hanisms to 90% of SIUs within 6 months ; (5) f ailure to inspect or sample 80% of SIUs within the past 12 months; and (6) f ailure to enforce standards and reporting requirements

. 123.26, 123.41(a), 123.45, 403.10, and CWA section 308 1Page **50** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Deficiencies Identified Through the Sewer Overflow/Bypass Com pliance Monitoring This is the unique code/description that that identifies each deficiency in the POTW’s

control of combined sewer overflows, sanitary sewer overflows, or bypass events for each com pliance monitoring activity ( e.g. , inspections, audits) by the regulatory authority. This data element includes unique codes to identify when a POTW has failed to provide 24

- hour notification to the NPDES permitting authority or failed to submit the Sewer Overflow/Bypass Event Report within the required 5

- day period. This data element also includes unique codes to identify when the POTW failed to comply with any applicable long

- term

CSO control plan , permit requirements, or enforcement actions. The values for data element will distinguish between noncompliance and significant noncompliance (SNC). 122.41(h), 122.41(l)(6) and (7), 122.43, 123.26, 123.41(a) , and CWA section s 308 and 402 (q)(1) 1

**Compliance Monitoring Activity Inform**  **ation ( AFO/CAFO**  **Prog ram** **Data Generated from Authorized NPDES Programs and EPA** **)**

Animal Ty

pe s (Inspection) The unique code/description that identifies the animal type(s) at the facility at the time of inspection ( e.g. , beef cattle, broilers, layers, swine weighing 55 pounds or mo re, swine weighing less than 55 pounds, mature dairy cows, dairy heifers, veal calves, sheep and lambs, horses, ducks, turkeys, other). 122.23 , 123.26, 123.41(a) , and CWA section 308 1

Animal Numbers (Inspection) The number of each type of animal in open confinement or housed under roof (either partially or totally) which are held at the facility at the time of inspection

. 122.23 , 123.26, 123.41(a) and CWA section 308 1 Animal Numbers in Open Confinement (Inspecti on) The number of each type of animal in open confinement which are held at the facility at the time of inspection. 122.23 , 123.26, 123.41(a) and CWA section 308 1

MLPW Containment and Storage Type (Inspection) The one or more ty pes of containment and storage ( e.g. , anaerobic lagoon, roofed storage shed, storage ponds, underfloor pits, above ground storage tanks, below ground storage tanks, concrete pad, impervious soil pad, other) at the facility at the time of inspection. 122.23 , 123.26, 123.41(a) and CWA section 308 1Page **51** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  MLPW Containment and Storage Type Within Design Capacity (Inspection) The one or more unique code s/description s that identifies whether or not the facility is operating within the design capacity for each type of containment and storage used by the facility for MLPW at the time of inspection. 122.23 , 123.26, 123.41(a) and CWA section 308 1

AFO/CAFO Unauthorized Discharges (Inspection) A unique code ( e.g. , “Yes”, “No”) that indicate s whether there evidence of unauthorized discharge(s) of pollutants from the facility’s production area and/or land application area(s) to a water of the U,S. 122.23, 123.26, 123.41(a) and CWA section 308 1
Permit Requirements Im plementation (Inspection) The unique code/description that identifies whether or not the facility is properly im plementing its NPDES permit requirements, including the applicable Nutrient Management Plan (NMP) or other nutrient management planning , at the time of inspection. 122.23 , 123.26, 123.41(a) and CWA section 308 1 **Compliance Monitoring Activity Inform**  **ation ( Discharge Monitoring Report**  **, and Pretreatm ent Periodic Compliance Reports for**  **Significant Industrial Users (SIUs) and Categorical Industrial Users (CIU**  **s) when EPA or the State is the Control Authority ) [Note: Authorized NPDES program**  **s will identify in the applicable NPDES per**  **mits will identify whether MS4 regulated entities are required to submit DMRs.]** Limit Set Designator ( Com pliance Monitoring Activity) The unique identifier tying the compliance monitoring activity ( e.g. , DMR submission) to the corresponding Limit Set record. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 3,6,8 Parameter Code ( Com pliance Monitoring Activity) The unique code/description identifying the parameter reported on the com pliance mo nitoring activity ( e.g. , DMR submission)

. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 3,6,8 Monitoring Location Code (Com

pliance Monitoring Activity) The unique code/description that identifies the monitoring location at which the sampling occurred for a compliance monitoring activity parameter ( e.g. , DMR submission)

. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 3,6,8 Limit Season Number (Com pliance Monitoring Activity) The unique identifier tying the compliance monitoring activity ( e.g. , DMR submission) to the Limit Season Number of the corresponding limit. This data element is necessary as a parameter can have different seasonal limits within a single limit start and end date. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 3,6,8 Monitoring Period End Date (Com

pliance Monitoring Activity) The monitoring period end date for the values covered by the compliance monitoring activity ( e.g. , DMR submission)

. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 3,6,8Page **52** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  No Data Indicator (NODI) (Com pliance Monitoring Activity) The unique code/description that indicates the reason that “No Discharge” or “No Data” wa s reported on the compliance monitoring activity ( e.g. , DMR submission) ( e.g. , B = Below Detection Limit, C = No Discharge). 122.41(l)(4)(i), 123.26, 123.41(a), 403.12 (e), 403.12(h) 3,6,8

Value (Com

pliance Monitoring Activity) The number value reported on the com pliance monitoring activity ( e.g. , DMR form)

. 122.41(l)(4)(i) , 123.26, 123.41(a), 403.12(e), 403.12(h) 3,6,8 Quantity or Concentration Units (Com

pliance Monitoring Activity) The unique code/description that identifies the one or more unit s of measure that are applicable to quantity or concentration limits and measurements as entered on the compliance monitoring activity ( e.g. , DMR submission)

. This field i s optional if the units are the same as the limit units

. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 3,6,8
Value Received Date (Com pliance Monitoring Activity) The date the compliance monitoring value was received by the regulatory authority ( e.g. , DMR submission)

. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 1 Value Type (Com

pliance Monitoring Activity) The unique code/description identifying a value type ( e.g. , Quantity 1, Quantity 2, Concentration 1, Concentration 2, Concentration 3) on a compliance monitoring activity ( e.g. , DMR submission)

. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 3,6,8 Value Qualifier (Com pliance Monitoring Activity) The unique code identifying the qualifier for the reported value ( e.g. , “ < ” , “ = ” , “ > ” ) on a compliance monitoring activity ( e.g. , DMR submission)

. This field is optional if the qualifier is “=”. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 3,6,8 **Compliance Monitoring Activity Inform**  **ation (Periodic Program** **Reports )**  Program Report Received Date T he date the program report was received. The date must be provided in YYYY

- MM

DD format where YYYY is the year, MM is the month, and DD is the day

. These are data elements that are common to reports required in p arts 122, 123, 403, and 503 1Page **53** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Program Report Event ID The unique identifier for each program report submission. This will provide for unique tracking of program report submissions. This data element can be system generated. These are data elements that are common to reports required in p arts 122, 123, 403, and 503 1

Start Date of Reporting Period (Program Report) T he start date of the reporting period for the program report. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day . For the Sewer Overflow/Bypass Event Report this i s the start or best estimate of the start date for each Se wer Overflow/Bypass Identifier. These are data elements that are common to reports required in p arts 122, 123, 403, and 503 4,5,6,7,9,10
End Date of Reporting Period (Program Report) T he end date of the reporting period for the program report. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. For the Sewer Overflow/Bypass Event Report this is the end or best estimate of the end date for each Sewer Overflow /By pass Identifier. These are data elements that are common to reports required in p arts 122, 123, 403, and 503 4,5,6,7,9,10

NPDES Data Group Number (Program Report) This data element identifies the NPDES Data Group for each program report submission . This corresponds to Table 1 in this appendix { e.g. , 7 = Pretreatment Program Reports [ 40 CFR 403.12(i) ] }. This data element also applies to Significant Industrial User Compliance Reports in Municipalities Without Approved Pretreatment Programs [ 40 CFR 403.12(e) and (h)] , which is NPDES Data Group Number 8 (Table 1 in this appendix). This can be a system generated data element. These are data elements that are common to reports required in p arts 122, 123, 403, and 503 4 through 10
**Compliance Monitoring Activity Inform**  **ation (Data Elements Specific to Sewage Sludge/Biosolids Annual Program Reports**  **)**

Biosolids or Sewage Sludge Treatment Processes The one or more unique codes/descriptions that identify the biosolids or sewage sludge treatment process or processes at the facility. For example, this data element uses codes to identify treatment processes in the following categories: preliminary operations ( e.g. , sludge grinding and degritting), thickening (concentration), stabilization, anaerobic digestion , a erobic digestion , com posting, conditioning, disinfection ( e.g. , b eta ray irradiation, g amma ray

irradiation, p asteurization), dewatering ( e.g. , centrifugation , sludge drying beds, sludge lagoons), heat drying, thermal reduction, and methane or biogas capture and recovery. 503.18, 503.28, 503.48 4Page **54** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 
Biosolids or Sewage Sludge Analytical Methods The one or more unique code s/descriptions that identify each of the analytic methods used by the facility to analyze enteric viruses, fecal coliforms, helminth ova , Salmonella sp ., and other regulated parameters. For example, EPA requires facilities to monitor for the certain parameters, which are listed in Tables 1, 2, 3, and 4 at 40 CFR 503. 13 and Tables 1 and 2 at 40 CFR 503.23 . This data element stores each analytic methods used by the facility only once for each annual report (not for each parameter measurement). 503.8(b), 503.18, 503.28, 503.48 4

Biosolids or Sewag e Sludge Form The one or more unique codes/descriptions that identify the nature of each b iosolids and sewage sludge material generated by the facility in terms of whether the material is a biosolid or s ewage sludge and whether the material is ultimately conveyed off

- site in bulk or in bags. T he fa cility will separately report the form for e ach biosolids or sewage sludge management practice or practices used by the facility and pathogen class

. 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge M anagement P ractice The one or more unique codes/descriptions that identify the type of biosolids or sewage sludge management practice or practices ( e.g. , land application, surface disposal, incineration) used by the facility. The facility will separately report the management practice for each biosolids or sewage sludge form and pathogen class. This data element will also identify the management practices used by surface disposal site owners/operators (see 40 CFR 503.24 ). 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge Pathogen Class The one or more unique codes/descriptions that identify the pathogen class or classes [ e.g. , Class A, Class B, Not Applicable (Incineration)] for biosolids or sewage sludge generated by the facility. The facility will separately report the pathogen class for each biosolids or sewage sludge management practice used by the facility and by each bio solids or sewage sludge form. 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge Amount (Program Report) This is the amount (in dry metric tons) of biosolids or sewage sludge applied to the land, prepared for sale or give

- away in a bag or other container for application to the land, or placed on an active sewage sludge unit

. This identification will be made for each biosolids or sewage sludge management practice used by the facility and by each biosolids or sewage sludge form as well as by each b iosolids or sewage sludge pathogen class

. 503.18, 503.28, 503.48 4Page **55** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Biosolids or Sewage Sludge Pathogen Reduction Options The one or more unique codes/descriptions that identify the options used by the facility to control pathogens ( e.g. , Class A

– Alternative 1, Class A

– Alternative 2, Class A

– Alternative 3, Class A

– Alternative 4, Class A

– Alternative 5, Class A

– Alternative 6, Class B

– Alternative 1 , Class B

– Alternative 2, Class B

– Alternative 3, or pH Adjustment (Domestic Septage). The facility will separately report the pathogen reduction options for each biosolids or sewage sludge management practice used by the facility and by each biosolids or sewage sludge form as well as by each biosolids or sewage sludge pathogen class

. 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge Vector Attraction Reduction Options The one or more unique codes/descriptions that identify the options used by the facility for vector attraction reduction. See a listing of these vector attraction reduction options at 40 CFR 503.33(b)(1) through (11). The facility will separately report the vector attraction reduction options fo r each biosolids or sewage sludge management prac tice used by the facility and by each biosolids or sewage sludge form as well as by each biosolids or sewage sludge pathogen class

. 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge Monitored Parameter This is the biosolids or sewage sludge parameter that is mo nitored by the facility. If there is more than one class, then the facility will separately report each monitored parameter for each biosolids or sewage sludge management practice used by the facility and by each biosolids or sewage sludge form

. EPA requires facilities to monitor for the certain parameters, which are listed in Tables 1, 2, 3, and 4 at 40 CFR 503. 13 and Tables 1 and 2 at 40 CFR 503.23 , pathogens ( e.g. , f ecal c oliform , Salmonella sp., e nteric viruses , helminth ova ), and vector attraction reduction parameters ( e.g. , specific oxygen uptake rate, and total, fixed, and volatile solids). 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge Monitored Parameter Value This is the value of the Biosolids or Sewage Sludge Monitored Parameter. 503.18, 503.28, 503.48 4 Biosolids or Sewage Sludge Monitored Parameter Units This is the measurement unit ( e.g. , mg/kg) associated with the Biosolids or Sewage Sludge Monitored Parameter Value. 503.18, 503.28, 503.48 4Page **56** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 
Biosolids or Sewage Sludge Monitored Parameter End Date This is the end date of the monthly monitoring period for the biosolids or sewage sludge sampling ( e.g. , 1/31/2015 for biosolids or sewage sludge monitoring data in January 2015). This data element is used to track the f requency of biosolids or sewage sludge mo nitoring in the reporting period ( e.g. , annual, quarterly, bi

- mo nthly, or monthly). For example, see Table 1 of 40 CFR 503.16 (Land Application), Table 1 of 40 CFR 503. 26 (Surface Disposal). 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge

- Surface Disposal Maximum Allowable Pollutant Concentration This data element is applicable to facilities that use an active surface disposal sites ( e.g. , mo nofills, surface impoundments, lagoons, waste piles, dedicated dispo sal sites, and dedicated beneficial use sites) without a liner. This data element identifies the maximum allowable pollutant concentration for each of the three pollutants: arsenic, chromium, and nickel (in units of mg/kg). This data element will use Table s 1 and 2 of 40 CFR 503.23 or the procedures identified in 40 CFR 503.23(b). 503.23, 503.28 4

Biosolids or Sewage Sludge

- Land Application or Surface Disposal Deficiencies This data element is applicable to facilities that use land application and/or an active surface disposal site ( e.g. , monofills, surface impoundments, lagoons , waste piles, dedicated disposal sites, and dedicated beneficial use sites). This data element uses one or more unique codes/descriptions to identify all deficiencies in the b iosolids or sewage sludge program within the reporting period. For example, this data element uses a unique code/description to identify when a biosolids or sewage sludge pollutant concentration exceed a ceiling concentration ( e.g. , Table 1 of 40 CFR 503.1 3 for facilities utilizing land application). This data element also uses a unique code/description to identify when the facility failed to properly collect and analyze its biosolids or sewage sludge in accordance with the approved analytical methods ( including appropriate method holding times ). This data element also use s a unique code/description to identify deficiencies with pathogen reduction and/or vector attraction reduction. For facilities that use an active surface disposal site this data element wi ll use a unique code/description to identify any deficiencies in meeting the applicable surface disposal requirements [see 40 CFR 503.24(a) through (n) ]. 503.18, 503.28 4

**Compliance Monitoring Activity Inform**  **ation (Data Elements Specific to CAFO Annual Program** **Reports )** Page **57** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  CAFO Animal T ypes (Program Report) The unique code/description that identifies the permittee ’s applicable animal sector(s) in the previous 12 months

. This includes (but not limited to) beef cattle, broilers, layers, swine weighing 55 pounds or more, swine weighing less than 55 pounds, mature dairy cows, dairy heifers, veal calves, sheep and lamb s, horses, ducks, and turkeys. 122.42(e)(4)(i) 5

CAFO Animal Maximum Number (Program Report) The estimated maximum number of each type of animal in open confinement or housed under roof (either partially or totally) which are held at the facility for a total of 45 days or more in the previous 12 months

. 122.42(e)(4)(i) 5 CAFO Animal Maximum Number in Open Conf inement (Program Report) The estimated maximum number of each type of animal in open confinement which are hel d at the facility for a total of 45 days or more in the previous 12 months. 122.42(e)(4)(i) 5
CAFO MLPW (Program Report) The unique code/description that identifies the type of CAFO manure, litter, and process wastewater generated by the facility i.e. in the previous 12 month s . 122.42(e)(4)(ii) 5 CAFO MLPW Amounts (Program Report) The estimated total amount of CAFO manure, litter, and process waste water generated by the facility in the previous 12 months

. 122.42(e)(4)(ii) 5 CAFO MLPW Amount s Units (Program Report) The unit ( e.g. , tons, gallons) for the estimated total amount of CAFO manure, litter, and process wastewater generated by the facility i.e. in the previous 1 2 month s . 122.42(e)(4)(ii) 5 CAFO MLPW Transferred (Program Report) The estimated total amount of CAFO manure, litter, and process waste water generated by the facility i.e. in the previous 12 month s that is transferred to other persons. The units for this data element will be the same as the units for the “CAFO MLPW Amount s (Program Report) ” data element. 122.42(e)(4)(ii i ) 5
Total Number of Acres for L and A

pplication C ov ered by the Nutrient M anagement P lan (Program Report) Total number of acres for land application covered by the current nutrient management plan

. 122.42(e)(4)(iv) 5Page **58** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Total Number of Acres Used for L and A pplication (Program Report) The total number of acres under control of the CAFO and used for land application in the previous 12 months. 122.42(e)(4)(v) 5

Discharge Ty

pe (Program Report) The unique code/description that identifies for each discharge from the permittee’s production area in the previous 12 month whether a 25

- year, 24

- hour rainfall event was the cause for the discharge. These data are optional if permittee uses a Discharge Monitoring Report (DMR) to provide the permitting authority with information on their discharges. 122.42(e)(4 ) (vi), 412 5
Discovery Date s of Discharges from Production Area (Program Report) The date of each discharge from the permittee’s production area in the previous 12 mo nths

. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. These data are optional if permittee uses a Discharge Monitoring Report (DMR) to provide the permitting authority with information on their discharges. 122.42(e)(4)(vi) 5

Duration of Discharge s from Production Area (Program Report) The estimated duration time (in hours) of each discharge from the permittee’s production area in the previous 12 months

. These data are optional if permittee uses a Discharge Monitoring Report (DMR) to provide the permitting authority with information on their discharges

. 122.42(e)(4)(vi) 5 Approximate Volume of Discharge from Production Area (Program Report) The approximate volume (in gallons) of each discharge from the permittee’s production area in the previous 12 months. These data are optional if permittee uses a Discharge Monitoring Report (DMR) to provide the permitting authority with information on their discharges. 122.42(e)(4)(vi) 5
Whether NMP A

pproved or D eveloped by C ertified P lanner (Program Report) The unique code/descriptio n that identifies whether the current version of the NMP was approved or developed by a certified nutrient management planner. 122.42(e)(4)(vii) 5

CAFO MLPW Nitrogen Content (Program Report) The nitrogen content of CAFO manure, litter, and process wastewater used or generated by the facility i.e. in the previous 12 months. 122.42(e)(4)(vi ii) 5Page **59** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  CAFO MLPW Phosphorus Content (Program Report) The phosphorus content of CAFO manure, litter, and process waste water used or generated by the facility i.e. in the previous 12 months

. 122.42(e)(4)(vi ii) 5 CAFO MLPW Nitrogen or Phosphorus Units (Program Report) The unit (s) ( e.g. , lbs/tons, lbs/1,000

- gallons) for the nitrogen and phosphorus content of CAFO manure, litter, and process waste water used or generated by the facility i.e. in the previous 1 2 month s . 122.42(e)(4)(vi i i) 5 CAFO MLPW Nitrogen or Phosphorus Form (Program Report) The form ( e.g. , total nitrogen , ammo nium

- nitrogen , total phosphorus ) for the nitrogen and phosphorus content of CAFO manure, litter, and process wastewater used or generated by the facility i.e. in the previous 12 months

. 122.42(e)(4)(vi i i) 5
Field Identification Number (Program Report) A unique field number to which CAFO MLPW wa s applied in the previous 12 months

. This data element will be used when the term “for each field” is used in the CAFO Annual Program Report. 122.42(e)(4)(viii) 5
Actual C rop(s) P lanted for E ach F ield (Program Report) Actual crop(s) planted for each field

. 122.42(e)(4)(viii) 5
Actual Crop Y ield(s) for E ach F ield (Program Report) Actual crop yield(s) for each field

. 122.42(e)(4)(viii) 5 Actual Crop Yield(s) for Each Field Units (Program Report) The unit (s) for the a ctual crop yield(s) for each field ( e.g. , bushels per acre). 122.42(e)(4)(viii) 5 Method for Calculating Maximum Amounts of Manure, Litter, and Process Wastewater (Program Report) The unique code/description that identifies whether the CAFO used the Linear Approach [40 CFR 122.42(e)( 5)(i)] or the Narrative Rate Approach [40 CFR 122.42(e)(5)(ii)]. 122.42(e)(4)(viii) 5Page **60** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  CAFO MLPW Land Application For Each Field (Program Report) The unique code/description that identifies for each field the type of CAFO manure, litter, and process wastewater i.e. in the previous 12 month s and used for land application

. 122.42(e)(4)(vi ii) 5
CAFO MLPW Land Application Maximum Amount For Each Field (Program Report) The maximum amount of CAFO manure, litter, and process wa stewater for each field in the previous 12 months and used for land application. The maximum amount s of CAFO manure, litter, and process wastewater is calculated in accordance with procedures in the Linear Approach [40 CFR 122.42(e)(5)(i)(B)] or the Narr ative Rate Approach [40 CFR 122.42(e)(5)(ii)(D)]. 122.42(e)(4)(vi ii) 5

CAFO MLPW Land Application Ac tual Amount For Each Field (Program Report) The actual amo unt of CAFO manure, litter, and process wastewater for each field in the previous 12 months and used for land application

. 122.42(e)(4)(vi ii) 5
CAFO MLPW Land Application For Each Field Unit (Program Report) The unit ( e.g. , tons, gallons) for the maximum and actual amount of CAFO manure, litter, and process wastewater for each field in the previous 12 months and used for land application

. 122.42(e)(4)(vi ii) 5 Nitrogen Soil Test Measurement (Narrative Rate Approach) (Program Report) For each field used for land application, the results of the most recent soil nitrogen analysis for any soil test taken in the preceding 12 months ( i.e. , amo unt of nitrogen in the soil). This data element is only applicable to facilities using the Narrative Rate Approach as described in 40 CFR 122.42(e)(5)(ii). 122.42(e)(4)(viii) 5 Phosphorus Soil Test Measurement (Narrative Rate Approach) (Program Report) For each field used for land application, the results of the most recent soil phosphorus analysis for any soil test taken in the preceding 12 months ( i.e. , amo unt of phosphorus in the soil). This data element is o nly applicable to facilities using the Narrative Rate Approach as described in 40 CFR 122.42(e)(5)(ii). 122.42(e)(4)(vi i i) 5
Soil Test Measurement Form (Narrative Rate Approach) (Program Report) T he form ( e.g. , total nitrogen, ammonium

- nitrogen, total phosphorus) for each soil test measurement
. This data element is only applicable to facilities using the Narrative Rate Approach as described in 40 CFR 122.42(e)(5)(ii). 122.42(e)(4)(vi i i) 5Page **61** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Soil Test Measurement Unit(s) (Narrative Rate Approach) (Program Report) The unit(s) for the amounts of nitrogen and/or phosphorus for any soil test results. This data element is only applicable to facilities using the Narrative Rate Approach, as described in 40 CFR 122.42(e)( 5)(ii). 122.42(e)(4)(vi i i) 5 Nitrogen Amount of Any S upplemental Fertilizer A pplied (Program Report) For each field used for land application, provide the amount of nitrogen in supplemental fertilizer applied in the previous 12 months. This data element is only applicable to facilities using the Narrative Rate Approach as described in 40 CFR 122.42(e)(5)(ii). 122.42(e)(4)(viii) 5 Phosphorus Amount of Any S upplemental Fertilizer A

pplied (Program Report) For each field used for land application, provide the amount of phosphorus in supplemental fertilizer applied in the previous 12 months. This data element is only applicable to facilities that are using the Narrative Rate Approach as described in 40 CFR 12 2.42(e)(5)(ii). 122.42(e)(4)(viii) 5 Supplemental Fertilizer Applied Units (Program Report) The unit(s) for the amount (s) of nitrogen and/or phosphorus in any supplemental fertilizer applied in the previous 12 months ( e.g. , ppm, pounds per acre). This data element is only applicable to facilities using the Narrative Rate Approach, as described in 40 CFR 122.42(e)(5)(ii). 122.42(e)(4)(viii) 5 **Compliance Monitoring Activity Inform**  **ation (Data Elements Specific to**  **Municipal Separate Storm Sewer System**  **Prog ram** **Reports )**  (Note: The MS4 permit may require one report for each unique governmental entity or one report per permit). MS4 Reliance on Other Go vernment Entities Status This is a unique code ( e.g. , “Yes”, “No”) that identifies whether the permittee relies on another unique governmental entity to satisfy any of the permit requirements

. 122.26(d)(2)(vii) , 122.34(g) (3) (v) 6

MS4 Reliance on Other Government Entities: Permit Com

ponent Status For each MS4 permit component this data element identifies the responsible

government entity . This data element uses the ‘ Unique Identifier for Each Municipality Covered Under MS4 Permit ’ data element. Use of this identifier allow s for greater geographic resolution for the MS4 components being tracked . This unique identifier does not change over time. The number identif ies the entity taking responsibility for complying with each MS4 permit com ponent
. 122.34(g) (3) (i) and (v), 122.35(a) and 122.42(c ) 6Page **62** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

MS4 Permit Component s Descriptions and Measurable Goals The one or more codes/descriptions that identify for each unique municipality all of the permitted components and measurable goals that are included in the MS4 permit. For Phase II MS4s, these components will be pre

-populated from the BMPs each Phase II MS4 permittee indicated it will implement in its NOI or permit application. The groupings of these MS4 components will include public education and outreach on stormwater im

pacts; public involvement/participation; illicit discharge detection and elimination; construction site stormwater runoff; post

- construction stormwater management in new development and redevelopment; and pollution prevention/good housekeeping for munic ipal operations. 122.34(g)(3) and 122.42(c) 6

Changes to MS4 Permit Com ponents and Measurable Goals Th e one or more code s/description s that describe for each unique municipality any changes made to MS4 permit components ( e.g. , BMPs) during the reporting p eriod. 122.34(g)(3)(iv) and 122.42(c) 6 Status of Compliance with each Minimum Control Measure The unique code ( e.g. , “Yes”, “No”) that identifies if the permittee has completed each measureable goal associated with each MS4 permit component. 122.34(g)(3) and 122.42(c) 6 Progress and Summary of Results with Each Minimum Control Measure This is a text summary describing the permittee’s compliance and progress toward meeting each measurable goal including a summary of results for each unique municipality. 122.34(g)(3) and 122.42(c) 6

MS4 Enforcement Action Ty pe For each unique municipality covered under a Phase I MS4 permit, this data element identifies the one or more types of enforcement actions taken during the past reporting period ( e.g. , notice of vio lations , s top work o rders , administration orders, a dministrative f ines , c ivil p enalties , c riminal a ctions ). The unique municipality covered under the MS4 permit will identify “No Authority” for this data element if the municipality does not have the authority to conduct enforcement action s . This data element is optional for Phase II MS4s. 122.34(g)(3) and 122.42(c) 6Page **63** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

MS4 Enforcement Action Number For each unique municipality covered under a Phase II MS4 permit and for each MS4 Enforcement Action Type , this data element identif ies the num

ber o f enforcement actions taken by responsible MS4 Municipal Enforcement Agency

. The unique municipality covered under the MS4 permit will identify “No Authority” for this data element if the municipality does not have the authority to conduct enforcement actions. For Phase II MS4s this data element will be the total number of enforcement actions taken during the reporting period. 122.34(g)(3) and 122.42(c) 6

MS4 Municipality Enforcement Agency For each unique municipality covered under the MS4 permit and for each MS4 Enforcement Action Type, this data element identif ies the corresponding MS4 Municipal Enforcement Agency by its unique municipality number (“Uni que Identifier for Each Municipality Covered Under MS4 Permit”).This data element is only required for permittees that have co

-permittees under their unique MS4 permit. 122.34(g)(3) and 122.42(c) 6

MS4 Industrial Stormwater Control The one or more unique codes/descriptions that identify how the MS4 permittee will comply with i ndustrial stormwater control requirements, including (at a minimum): (1) status of the ordinance or other regulatory mechanism to control the contribution of po llutants by stormwater discharges associated with industrial activity, including authority to carry out all inspection, surveillance and monitoring procedures necessary to determine compliance and noncompliance, and including sanctions to ensure compliance ; (2) status of the MS4 permittee industrial stormwater inventory, which identifies facilities with industrial activities and assesses the quality of the stormwater discharged from each facility with an industrial activity; (3) status of program to mo nitor and control pollutants in stormwater discharges from municipal landfills, hazardous waste treatment, disposal and recovery facilities, industrial facilities that are subject to Toxics Release Inventory (TRI) reporting requirements ( Emergency Planning and Community Right

- To

- Know Act S ection 313 ), and industrial facilities that are contributing a substantial pollutant loading to the MS4; and (4) status of monitoring program for discharges associated with industrial facilities. This data element is optional f or Phase II MS4s. 40 CFR 122.26(d)(2)(i)(A, B, C, E, and F) and 40 CFR 122.26(d)(2)( ii) and (iv)(A)(5) and (iv)(C), 122.42(c) 6Page **64** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  **Compliance Monitoring Activity Inform**  **ation (Data Elements Specific to**  **Pretreatm ent Program**  **Reports , SIU Periodic Compliance**  **Reports in Municipalities without an Approved Pretreatm**  **ent Program )**  (Note: These data elements do not apply to the development, evaluation, or compliance monitoring activities supporting wastewater surcharge rates.) SNC Published A unique code ( e.g. , “Yes ”, “No”) that identifies for each Significant Industrial User (SIU) and Non

- Significant Catego rical Industrial Users (NSCIU) in SNC whether the Control Authority published a public notice within the reporting period. 403.8(f)(2)(viii) , 403.12(i)(2) 7
SNC with Pretreatment Enforceable Compliance Schedule Status The unique code/description that identifies for each Significant Industrial User (SIU) and Non

- Significant Catego rical Industrial User (NSCIU) in SNC whether the industrial user in SNC is subject to one or more enforceable c om pliance schedule s within the reporting period. 403.8(f)(2)(viii), 403.12(i)(2) 7

Local Limits Adoption Date This is the most recent date on which the Control Authority adopted new local limits within the reporting period. Th e date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day . The Control Authority can leave this data element blank on the Pretreatment Program Report if the Control Authority did not adopt any new local limits within the reporting period. 122.44(j)(2)(ii), 403.5(c), 403.8(f)(4) and (5), 403.12(i)(4) 7

Local Limits Evaluation Date This is the most recent date on which the Control Authority completed an evaluation on the potential need for local limits within the reporting period. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day. The Control Authority can leave this data element blank on the Pretreatment Program Report if the Control Authority did not evaluate any local limits within the reporting period. 122.44(j)(2)(ii), 403.5(c), 403.8(f) (4) and (5), 403.12(i)(4), 403.8(f)(4) 7

Local Limits Pollutants This is the list of the pollutants for which the Control Authority adopted local limits. T he Control Authority will only need to enter each pollutant once no matter how many treatment works are managed by the Control Authority

. The Control Authority can leave this data element blank on the Pretreatment Program Reports if the Control Authority did not change the pollutants for which the Control Authority derived local limits

. 403.5(c), 403.12(i)(4) 7Page **65** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  POTW Discharge Contamination Indicator (Program Report) The one or more unique code s/descriptions that identif y any problems ( e.g. , pass through, interference, violation of NPDES permit limits) with the receiving POTW’s effluent discharge within the reporting period. See 40 CFR 403.3(k) and (p). EPA regulations require the Control Authority to develop and enforce local limits when the discharge from an IU causes or contributes to any problems at the receiving POTW. 403.8(f) , 403.12(i) 7

POTW Biosolids or Sewage Sludge Contamination Indicator (Program Report) The one or more unique codes/descriptions that identif y any problems ( e.g. , interference with the use or disposal of biosolids or sewage sludge , violation of NPDES permit requirements or EPA’s regulations at 40 CFR part 503) with the receiving POTW’s biosolids or sewage sludge within the reporting period

. See 40 CFR 403.3(k). EPA regulations require any Control Authority that must develop a Pretreatment Program also to develop and enforce local limits to ensure that the discharge from an IU does not cause or contribute a disruption of biosolids’ use or disposal at the receiving POT W. 403.8(f) , 403.12(i) 7

Industrial User Control Mechanism Status A unique code/description that identifies whether the Industrial User is subject to an effective Control Mechanism within the reporting period

. 403.3(k), 403.5(c), 403.8(f) , 403.12(i) 7 Industrial User Control Mechanism E ffective Date The date when the active Control Mechanism for the Industrial User became effective

. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day. 403.8(f) (1)(iii )(B)(1) , 403.12(i) 7 Industrial User Control Mechanism Expiration Date The date when the active Control Mechanism for the Industrial User will expire. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the mo nth, and DD is the day

. 403.8(f) , 403.12(i) 7
SNC with Pretreatment Standards or Limits (Program Report) This data element will identify for each Significant Industrial User (SIU) and Non

Significant Catego rical Industrial User (NSCIU) whether the IU was in Significant Non

- Com

pliance (SNC) with any pretreatment standard or local limits applicable to the industrial user’s discharge within the reporting period

. 403.8(f) , 403.12(i) 7
SNC with Pretreatment Standards or Limits Pollutants (Program Report) This data element will identify for each Significant Industrial User (SIU) and Non

Significant Categorical Industrial User (NSCIU) the pollutants that related to the industrial user’s Si gnificant Non

- Com pliance (SNC) status with any applicable pretreatment standard or local limits within the reporting period

. 403.8(f), 403.12(i) 7Page **66** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  SNC with Reporting Requirements (Program Report) This data element will identify for each Significant Industrial User (SIU) and Non

Significant Catego rical Industrial User (NSCIU) whether the IU was in Significant Non

- Com

pliance (SNC) with reporting requirements ( including baseline monitoring reports, notice of potential problems, periodic self

- mo nitoring report s, notice of change in Industrial User discharge, hazardous waste notification and BMP certification) within the reporting period

. 123.26, 123.41(a), 123.45, 403.8(f) , 403.10, 403.12(i) 1, 7

SNC with Other Control Mechanism Requirements (Program Report) This data element will identify for each Significant Industrial User (SIU) and Non

Significant Catego rical Industrial User (NSCIU) whether the IU was in Significant Non

- Com

pliance (SNC) with any other control mechanism requirements within the reporting period

. This data element does not include instances of SNC that relate to the industrial user’s applicable discharge standard s or local limit s or reporting requirements. 123.26, 123.41(a), 123.45, 403.8(f) , 403.10, 403.12(i) 1, 7

Listing of Months in SNC This data element will identify for each Significant Industrial User (SIU) and Non

Significant Catego rical Industrial User (NSCIU) the month or months the IU is in SNC within the reporting period

. The se data must be provided in YYYY

- MM format where YYYY is the year and MM is the month. 123.26, 123.41(a), 123.45, 403.8(f) , 403.10, 403.12(i) 1, 7
Number of Industrial User Inspections by Control Authority This data element will identify for each Significant Industrial User (SIU) the number of inspections conducted by the Control Authority within the reporting period

. 403.8(f) , 403.12(i) 7 Number of Industrial User Sam pling Events by Control Authority This data element will identify for each Significant Industrial User (SIU) the number of complete sampling events conducted by the Control Authority within the reporting period

. 403.8(f) , 403.12(i) 7 Number of Required Industrial User Self

Monitoring Events This data element will identify for each Significant Industrial User (SIU) the number of required self

- mo nitoring sampling events with in the reporting period that must be reported to the Control Authority

. 403.8(f), 403.12(i) 7 Actual Num

ber of Industrial User Self

Monitoring Events This data element will identify for each Significant Industrial User (SIU) the actual number of self

- mo nitoring sampling events within the reporting period submitted to the Control Authority. 403.8(f), 403.12(i) 7Page **67** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Ty pes of Industrial User Enforcement Action This data element will identify for each Significant Industrial User (SIU) the type(s) of formal enforcement action(s) ( e.g. , formal notices of violation or equivalent actions, administrative orders, civil suits, criminal suits) issued by the Control Authority with in the reporting period . The Control Authority can also optionally use this data element to track informal actions that they issued within the reporting period. 403.8(f), 403.12(i) 7

Number of Industrial User Enforcement Actions This data element will identify for each Significant Industrial User (SIU) and for each ty pe of enforcement action the total number of forma l enforcement actions issued by the Control Authority within the reporting period

. The Control Authority can also optionally use this data element to track informal actions that they issued within the reporting period. 403.8(f), 403.12(i) 7

Industrial User Cash Civil Penalty Amount Assessed For civil judicial Enforcement Actions, the dollar amount of the penalty assessed against each Significant Industrial User (SIU) and Non

- Significant Catego rical Industrial User (NSCIU) within the reporting period 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. CWA section 309 7

Industrial User Cash Civil Penalty Amount Collec ted For civil judicial Enforcement Actions, the dollar amount of the penalty collected from each Significant Industrial User (SIU) and Non

- Significant Catego rical Industrial User (NSCIU) within the reporting period . For Administrative Enforcement Actions, it is the dollar amount collected of the penalty assessed in the Consent/Final Order. CWA section 309 7

Industrial User POTW Discharge Contamination Indicator (Program Report) The one or more unique codes/descriptions that identify for each Significant Industrial User (SIU) and Non

- Significant Catego rical Industrial User (NSCIU) whether the Industrial User caused or contributed to any problems ( e.g. , pass - through, interference 

### , violation of NPDES permit limits ) wi th the receiving POTW’s effluent discharge in the previous reporting period. See 40 CFR 403.3(k) and (p)

. EPA regulations require the Control Authority to develop and enforce local limits when the discharge from an IU causes or contributes to any problem s e.g. at the receiving POTW. 123.26, 123.41(a), 123.45, 403.5(c), 403.8(f) , 403.10 , 403.12(i) 1, 7Page **68** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Industrial User Biosolids or Sewage Sludge Contamination Indicator (Program Report) The one or more unique codes/descriptions that identify for each Significant Industrial User (SIU) and Non

- Significant Catego rical Industrial User (NSCIU) whether the Industrial User caused or contributed to any problems ( e.g. , interference with the use or disposal of biosolids or sewage sludge , violation of NPDES permi t requirements or EPA’s regulations at 40 CFR part 503 ) with the receiving POTW’s biosolids or sewage sludge in the previous reporting period. See 40 CFR 403.3(k). EPA regulations require the Control Authority to develop and enforce local limits when the discharge from an IU causes or contributes to any problems e.g. at the receiving POTW. 123.26, 123.41(a), 123.45, 403.5(c), 403.8(f) , 403.10 , 403.12(i) 1, 7

Industrial User Wastewater Flow

Rate (Program Report) This data element will identify for each Significant Industrial User (SIU) and Non

Significant Catego rical Industrial User (NSCIU) the maximum monthly average wa stewater flow

rate (in gallons per day) in the previous reporting period. 403.8(f) , 403.12(e), 403.12(h), 403.12(i) 7 ,8
Middle

- Tier Significant Industrial User Reduced Reporting Status The unique code/description that identifies for each Middle

- Tier Significant Industrial User (MTSIU) whether the Control Authority has granted reduced reporting requirements in accordance with 40 CFR 403.12(e)(3). 123.26, 123.41(a), 123.45, 403.10 , 403.12(e)(3), 403.12(i)(2) 1, 7
Non

- Significant Catego rical Industrial User (NSCIU) Certification Submitted to Control Authority The unique code/description that identifies for each Non

- Significant Catego rical Industrial User (NSCIU) whether the facility has reported its required annual compliance certification to the Control Authority within the reporting period. 123.26, 123.41(a), 123.45, 403.10 , 403.12(i)(2), 40 3.12(q) 1, 7

Notification of Changed Discharge Submission The unique code ( e.g. , “Yes”, “No”) that identifies for each Significant Industrial User (SIU) and Non

- Significant Categorical Industrial User (NSCIU) w hether the Industrial User submitted a notification within the reporting period to the Control Authority of a substantial change in the volume or character of pollutants in their discharge, including the listing or characteristic hazardous wastes for which the Industrial User previously submitted notice. 403.8(f) , 403.12 (i), 403.12(j) 1,7Page **69** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  **Compliance Monitoring Activity Inform**  **ation (Data Elements Specific to Sewer Overflow** **/Bypass Event Reports)**  [Note: These data elements apply to se wer overflows and bypass events at POTWs. These data elements do not apply to industrial facilities. This report uses the
‘ Permitted Feature Identifier (Compliance Monitoring Activity) ’ data element to identify the location of each sewer overflow or byp ass at a permitted feature. Each bypass location should be permitted and have an identifier in the ‘ Permitted Feature Identifier ( Permit)’ data element. This report will also identify the location of each se wer overflow at an unpermitted feature. ]

Sewer Overflow

/By pass Identifier This data element will allow the reporting of multiple sewer overflows or bypasses on one report. Each individualized sewer overflow or by pass will be given a unique identifier ( e.g. , 1, 2, 3, and so on) for each Sewer Overflow/By pass Event Report . This field can be system generated to accommodate one or more individual sewer overflows or bypasses. I f the sewer overflow s are caused by an extreme weather event ( e.g. , hurricane) that floods the entire sewer system the POTW can use this data element to indicate that the number of sewer overflows cannot be tabulated as they are too numerous to count. 122.41(l)(4), (6) , and (7) and 122.41(m)(3) 3, 9

Sewer Overflow Longitude for Unpermitted Feature ( Sewer Overflow/Bypass Event Report) This data element is required for each Sewer Overflow/Bypass Identifier without a corresponding identifier in the ‘ Permitted Feature Identifier (Permit)’ data element , which is reported on the NPDES permit application or Notice of Intent for NPDES permit coverage. This data element is th e measure of the angular distance on a meridian east or west of the prime meridian for the se wer overflow location

. The format for thi s data element is d ecimal d egrees ( e.g. , - 77.029289 ) and the WGS84 standard coordinate system. T he ‘ Permitted Feature Identifier (Compliance Monitoring Activity) ’ data element is used to identify the location of each se wer overflow at a permitted feature. If the sewer overflow is associated with a private residence the longitude of the nearest collection system structure ( e.g. , manhole) can be used for this data element to the extent that reporting is required. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the se wer overflows are caused by an extreme weather event ( e.g. , hurricane) that floods the entire se wer system and are too numerous to count
. This data element can also be system generated if the Sewer Overflow/Bypass Event Report collects the street location of the sewer overflow and the street location can be used to generate an accurate longitude value. (Note: “Post Office Box” addresses and “Rural Route” addresses are generally not geoco dable). 122.41(l)(4), (6), and (7) 3, 9Page **70** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 

Sewer Overflow Latitude for Unpermitted Feature ( Sewer Overflow/Bypass Event Report) This data element is required for each Sewer Overflow/Bypass Identifier without a corresponding identifier in the ‘Permitted Featu re Identifier (Permit)’ data element, which is reported on the NPDES permit application or Notice of Intent for NPDES permit coverage . This data element is the measure of the angular distance on a meridian north or south of the equator for the sewer overfl ow location

. The format for this data element is d ecimal d egrees ( e.g. , - 77.029289 ) and the WGS84 standard coordinate system. T he Permitted Feature Identifier (Compliance Monitoring Activity) data element is used to identify the location of each se wer overflow at a permitted feature. If the sewer overflow is assoc iated with a private resid ence the latitude of the nearest collection system structure ( e.g. , manhole ) can be used for this data element to the extent that reporting is required

. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the se wer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire se wer system and are too numerous to count. This data element can also be system generated if the Sewer Overflow/Bypass Event Report collects the street location of the sewer overflow and the street location can be used to generate an accurate longitude value. (Note: “Post Office Box” addre sses and “Rural Route” addresses are generally not geocodable). 122.41(l)(4), (6), and (7) 3, 9

Ty pe of Sewer Overflow /By pass ( Sewer Overflow/Bypass Event Report) A unique code/description that identif ies the type of sewer overflow or by pass ( e.g., CSO or SSO from the POTW’s collection system, anticipated b ypass from the treatment works, unanticipated bypass from the treatment works ) for each Sewer Overflow/Bypass Identifier

. For bypass events the permittee will also use this data element to identify if any NP DES effluent limitations were violated as a result of the bypass. 122.41(l)(4), (6), and (7) and 122.41(m)(3) 3, 9

Ty pe of Sewer Overflow /By pass Structure A unique code/description that identifies the type of sewer overflow or by pass structure ( e.g. , manhole, CSO outfall) for each Sewer Overflow/Bypass Identifier. The POTW can leave this data element blank on the Se wer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire s ewer system and are too numerous to count. 122.41(l)(4), (6), and (7) and 122.41(m)(3) 3, 9Page **71** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Sewer Overflow/By

pass Cause The one or more unique codes/descriptions that best represent the likely cause of the sewer overflow or bypass ( e.g. , broken pipe, fats/oil/grease, mechanical failure , pum p station electrical failure, wet weather, vandalism) for each Sewer Overflow/Bypass Identifier

. 122.41(l)(4), (6), and (7) and 122.41(m)(3) 3, 9

Duration of Sewer O verflow /By pass (hours) ( Sewer Overflow/Bypass Event Report) Estimated duration of the sewer overflow or by pass (in hours) for each Sewer Overflow/Bypass Identifier. I f the discharge has not been corrected, this is the b est professional judgment from the sewer owner or in the case of a bypass, the treatment plant owner, of the time the sewer overflow or by pass is expected to continue

. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire sewer system and are too numerous to count. 122.41(l)(4), (6), and (7) and 122.41(m)(3) 3, 9

Sewer Overflow/By

pass Discharge Volume (gallons) ( Sewer Overflow/Bypass Event Report) Best profes sional judgment from the se wer owner on the estimated number of gallons of sewer overflow or bypass for each Sewer Overflow/Bypass Identifier. If the discharge has not been corrected, this is the best professional judgment from the sewer owner or in the ca se of a bypass, the treatment plant owner, of the volume of overflow or by pass prior to cessation. The POTW can leave this data element blank on the Se wer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire se wer system and are too numerous to count. 122.41(l)(4), (6), and (7) and 122.41(m)(3) 3, 9

Receiving Waterbody Name for Unpermitted Feature ( Sewer Overflow/Bypass Event Report) This data element identifies the receiving waterbody name for each Sewer Overflow/Bypass Identifier that does not have a corresponding value in the ‘ Permitted Feature Identifier (Permit)’ data element. This data element will use the best professional judgment of the sewer owner to identif y the name of the waterbody that is or will likely receive the discharge from each Sewer Overflow/Bypass Identifier. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire sewer system and are too numerous to count. 122.41(l)(4), (6), and (7) 3, 9Page **72** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  W et W eather Occurrence for Sewer Overflow /By pass Status The unique code ( e.g. , “Yes”, “No”) that represents the b est professional judgment of

the sewer owner, or in the case of a bypass, the treatment plant owner, regarding whether the se we r overflow or bypass, by Sewer Overflow/Bypass Identifier, occurred during wet weather. 122.41(l)(4), (6), and (7) and 122.41(m)(3) 3, 9

Corrective Actions Taken or Planned for Sewer Overflow /By pass ( Sewer Overflow/Bypass Event Report) The unique code/description that describes the steps taken or planned to reduce, eliminate, and prevent reoccurrence of future sewer overflows or bypasses fo r each Sewer Overflow/Bypass Identifier and the related impacts to health and the environment. This data element can be used to identify the portion of the sewer overflow or bypass that was contained and recovered prior to any discharge to waters of the U. S. This data element will also identify if any monitoring of the receiving waterbody was done during and/or after the sewer overflow or bypass to gauge the potential impact to health and the environment

. The POTW can leave this data element blank on the Se wer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire sewer system and are too numerous to count. 122.41(l)(4), (6), and (7) and 122.41(m)(3) 3, 9

Ty pe of Potential Im

pact o f Sewer Overflow /By pass (Sewer Overflow/Bypass Event Report) The unique code/description that describes the type of potential health or environmental im pact(s) ( e.g. , beach closure) for each Sewer Overflow/Bypass Identifier

. Under 40 CFR 122.41(l)(6), “the permittee shall report any noncompliance which may endanger health or the environment.” This data element provides information regarding the nature of such potential endangerment. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the se wer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire se wer system and are too numerous to count. 122.41(l)(4), (6), and (7) and 122.41(m)(3) 3, 9

**Compliance Monitoring Activity Inform**  **ation (Data Elements Specific to**  **CWA section 316(b)**  **A nnual**  **R eport**  **s)** { Note: Where the Director requires additional measures to protect Federally

- listed threatened or endangered species or critical habitat pursuant to 40 CFR 125.94(g), the Director shall require reporting associated with those measures [see 40 CFR 125.97(g)]. The following data ele me nts correspond to this reporting requirement. These data elements are only required for facilities that are required to report on their additional measures to protect Federally

- listed threatened or endangered species or critical habitat }

.Page **73** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  CWA Section 316(b) Biological Monitoring

- Species Name (Program Report) For existing facilities, a listing of each Federally

- listed threatened or endangered species (or relevant taxa) for all life stages that might be susceptible to impingement and entrainment at the facility’s cooling water intake structure ( s )

. Specific monitoring protocols and frequency of monitoring wil l be d etermined by the Director. 125.96, 125.97(g), 125.98 , 125.138(b), 401.14 and CWA section 316(b) 10 CWA Section 316(b) Biological Monitoring

- Species Number (Program Report) For existing facilities, the number of each Federally

- listed threatened or endangered species (or relevant taxa) that might be susceptible to impingement and entrainment at the facility’s cooling water intake structure ( s )

. Specific monitoring protocols and frequency of monitoring will be determined by the Director. 125.96, 125.97(g), 125.98 , 125.138(b), 401.14 and CWA section 316(b) 10 CWA Section 316(b) Biological Monitoring

- Threatened or Endangered Status (Program Report) For existing facilities, a unique code/description that identifies for each Federally

- listed threatened or endangered species (or relevant taxa) whether the species is threatened, endangered, or is an otherwise protected species that might be susceptible to im pingement and entrainment at the facility’s cooling water intake structu re(s)

. Specific mo nitoring protocols and frequency of monitoring will be determined by the Director. 125.96, 125.97(g), 125.98 , 125.138(b), 401.14 and CWA section 316(b) 10 CWA Section 316(b) Biological Monitoring

- Species Impinged and Entrained (Program Report) For existing facilities, the number of each Federally

- listed threatened or endangered species (or relevant taxa) impinged and entrained per year by the facility’s cooling water intake structure(s)

. Specific monitoring protocols and frequency of monitoring will be determined by the Director. 125.96, 125.97(g), 125.98 , 125.138(b), 401.14 and CWA section 316(b) 10 CWA Section 316(b) Biological Monitoring

- Applicable Measures to Protect Designated Critical Habitat (Program Report) For existing facilities, a text summary of the measures taken by the permittee to protect designated critical habitat in the vicinity of impingement and entrainment at the facility ’s cooling water intake structure (s). 125.96, 125.97(g), 125.98 , 125.138(b), 401.14 and CWA section 316(b) 10

**Inform ation**  **Common to Violations, Enforcement Actions, and Final Orders** [Note: S ingle Event V iolation (SEV) data elements are mandatory for construction stormwater inspections that identify CWA violations that result in a regulatory authority taking a formal enforcement action. SEV data elements are optional for other construction stormwater inspections .]Page **74** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 
Violation Code The unique code/description that identif ies each type of violation that has occurred at the facility ( e.g. , D80 = Required Monitoring DMR Value Non

- Receipt, E90 = Effluent Violation, C20 = Schedule Event Achieved Late) . This includes single event violations (SEVs) and violations that are system generated based upon DMRs, schedules, etc. 123.45 and CWA section 309 1

Violation Date This is the date of the violation, which varies depending on the type of violation. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the mo nth, and DD is the day . This data element may be system generated and does not apply to single event violation dates. 123.45 and CWA section 309 1

**Violation Inform**  **ation** Agency Identifying the Single Event Violation (SEV) The unique code/description that identif ies the agency that identified the s ingle e vent violation (SEV). 123.26, 123.41(a) , 123.45 1 Single Event Violation Start Date T he date the single event violation (SEV) began. If the SEV occurred on one date, this data element is optional as this date can be system generated to equal “ Single Event Violation End Date ” when left blank. The date mu st be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 123.26, 123.41(a), 123.45 1

Sin gle Event Violation End Date T he date the single event violation (SEV) ended

. This field will be left blank to denote an ongoing or unresolved SEV. The date mu st be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 1 23.26, 123.41(a), 123.45 1
RNC Detection Code The unique code/description that identifies the type of reportable noncompliance ( RNC ) detected by the regulatory authority. 123.26, 123.41(a), 123.45 1
RNC Detection Date The date that reportable noncompliance ( RNC ) wa s detected . This date may vary according to the type of violation detected. The date mu st be provided in YYYY

- MM

DD format where YYYY is the year, MM is the month, and DD is the day

. 123.26, 123.41(a), 123.45 1

RNC Resolution Code The unique code/description that identifies the reportable noncompliance ( RNC ) status ( e.g. , noncompliant, resolved pending, waiting resolution, resolved) for each violation. This data element can be entered manually or system generated

. 123.26, 123.41(a), 123.45 1Page **75** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  RNC Resolution Date The date reportable noncompliance ( RNC ) was marked to its current resolution status. This data element is entered manually. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is th e day

. 123.26, 123.41(a), 123.45 1 **Enforcement Action Information**  [Note: NPDES authorized programs will only need to share criminal action information with EPA when the criminal case is concluded .]

Enforcement Action Identifier The unique identifier for each e nforcement a ction . For EPA enforcement actions, this field will be have three components, each separated by a hyphen ( e.g. , 04

- 2014

- 4509). These three components are: (1) the EPA Region responsible for the e nforcement a ction as identified by the EPA Region code ( e.g. , 04); (2) the four

- digit fiscal year during which the e nforcement a ction is initiated ( e.g. , 2014); and (3) a four

- digit, user

- assigned sequence number between 0001 and 9999 ( e.g. , 4509)

. States will be able to use this same structure, or they will be able to use a different structure of their choosing provided that the first two characters of the identifier constitute the state code ( e.g. , Alabama = “AL”)

. 123.27, 123.41(a) , and CWA section 309 1

Enforcement Action Forum This identifies the forum of the formal enforcement action (e.g., administrative f ormal , j udicial ). This can be system generated. 123.27, 123.41(a) , and CWA section 309 1
Enforcement Action Type The unique code/description that identifies the type for each formal or informal enforcement action. This code/description identifies, for example, whether the enforcement action is a civil judicial referral, a notice of violation, an administrative penalty order, administrative order, or criminal prosecutio n . 123.27, 123.41(a), and CWA section 309 1 Programs Violated (Enforcement Action) The unique code/description that identifies each program ( e.g. , pretreatment, biosolids/sewage sludge, MS4s, Core NPDES program) associated with each enforcement activity. 123.27, 123.41(a), and CWA section 309 1Page **7 6**  of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 
Enforcement Action Sub

a ctivity Type A unique code/description that identifies the ty pe for each sub

- activity associated with each enforcement activity ( e.g. , COMPS = compliance achieved, MECDJ = mo tion to enforce consent agreement, AHRG = administrative hearing , AMNCA = amended complaint). Some of these sub

- activities are system required and some can be sy stem generated. Data on sub

- activities that are not milestones are optional. 123.27, 123.41(a), and CWA section 309 1

Enforcement Action Sub

activity Completion Date The date on which the sub

- activity was com pleted

. This data element is required for each sub

- activity provided. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day . Some of these dates can be system generated. 123.27, 123.41(a), and CWA section 309 1

**Final Order Inform**  **ation** (Note: These data elements are linked to the “E nforcement Action Identifier”. NPDES authorize d programs will only need to share criminal action information with EPA when the criminal case is concluded

. ) Final Order Identifier The unique identifier for each final order. This data element can be system generated. 123.27, 123.41(a), and CWA section 309 1
Final Order Type A unique code that identifies the legal process used by the authorized NPDES program to settle the e nforcement a ction ( e.g. , administrative compliance order, an administrative penalty order, consent decree, Federal facility agreement, criminal conviction or plea agreement). 123.27, 123.41(a), and CWA section 309 1

Final Order Issued/ Entered Date For a judicial enforcement ac tion this is the date the Clerk of the Court stamps the document after it is signed by the presiding Judge

. For an a dministrative f ormal enforcement action this is the date the Final Order wa s issued. For a criminal enforcement action, this is the date the sentence was imposed. The date mu st be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 123.27, 123.41(a), and CWA section 309 1Page **77** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )** 
NPDES Closed Date The date of closure for each NPDES final order. The date must be provided in YYYY

MM

- DD format where YYYY is the year, MM is the month, and DD is the day. 123.27, 123.41(a), and CWA section 309 1 **Penalty Inform**  **ation** (Note: These data elements are linked to the “E nforcement Action Identifier”. NPDES authorized programs will only need to share criminal action information with EPA when the criminal case is concluded. )

Penalty Amount Assessed For civil judicial e nforcement a ctions, the dollar amount of the penalty assessed against the defendant(s) as specified in the final entered Consent Decree or Court Order. For a dministrative e nforcement a ctions, it is the dollar amount of the penalty assessed in the Consent Decree or Final Order. For criminal enforcement actions, it is the dollar amount of the fine agreed to by the defendant or sentenced by the Court and should include fields for prison time, probation, home confinement or monitoring periods, restitution, and special assessments

. 123.27, 123.41(a), and CWA section 309 1

Penalty Amount Collected For civil judicial e nforcement a ctions, the dollar amount of the penalty collected from the defendant(s). For a dministrative e nforcement a ctions, it is the dollar amount collected of the penalty assessed in the Consent Decree or Final Order. For criminal e nforcement actions, it is the dollar amount of the fine paid by the defendant as well as restitution and special assessments

. 123.27, 123.41(a), and CWA section 309 1

Supplemental Environmental Project Identifier The unique identifier for each supplemental environmental project

. This data element can be system generated. 123.27, 123.41(a), and CWA section 309 1Page **78** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Supplemental Environmental Project Amount T he assessed cost, in dollar s, of the one or more of the defendant’s Supplemental Environmental Projects (SEPs) . This is the dollar amount that is assessed either in addition to civil penalties or in lieu of civil penalties

. This data element is only required if there is a SEP and may be entered at a later date w hen the data is available. 123.27, 123.41(a), and CWA section 309 1

Supplemental Environmental Project Description This text field summarizes the Supplemental Environmental Projects (SEPs) that the respondent has completed in response to an enforcement action

. This data element is only required if th ere is a SEP and may be entered at a later date w hen the data is available

. 123.27, 123.41(a), and CWA section 309 1
**Compliance Schedule Information**  (Note: These data elements are linked to the “E nforcement Action Identifier”.) Com pliance Schedule Number This number that in com bination with the Compliance Schedule Type and NPDES ID uniquely identifies a c om pliance s chedule. 123.27, 123.41(a), and CWA section 309 1 Com pliance Schedule Ty pe The unique code/description that identifies the type of compliance schedule ( e.g. , an administrative formal action = “A”, a judicial action = “J”)

. 123.27, 123.41(a), and CWA section 309 1 Com pliance Schedule Description The unique code/description that identifies each type of condition or requirement ( e.g. , b est management p ractices p lan development) for the compliance schedule. 123.27, 123.41(a), and CWA section 309 1 Com pliance Schedule Event Code The unique code/description that identifies each event that is added within a c om pliance s chedule

. 123.27, 123.41(a), and CWA section 309 1 Com pliance Schedule Due Date The date the compliance schedule event is scheduled to be completed ( i.e. , the due date). The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 123.27, 123.41(a), and CWA section 309 1
Com pliance Schedule Actual Date The actual date on which the c om pliance s chedule event was completed or achieved. The date must be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 123.27, 123.41(a), and CWA section 309 1Page **79** of **79 Table**  **2 : Required NPDES**  **Program Data** 

**Data Nam e**  **Data Description CWA, Regulatory**  **(40 CFR)**  **, or Other**  **Citation NPDES** 

**Data Group**  **Number (**  **see Table**  **1 )**  Com pliance Schedule Report Received Date The date the regulatory agency received the report required by the c om pliance s chedule report. The date mu st be provided in YYYY

- MM

- DD format where YYYY is the year, MM is the month, and DD is the day

. 123.27, 123.41(a), and CWA section 309 1
**Notes:** (1) The NPDES program authority may pre

-populate these data elements and other data elements ( e.g. , Federal Registry System ID) in th e NPDES electronic reporting systems in order to create efficiencies and standardization. For example, the NPDES program authority may configure their electronic reporting system to automatically generate NPDES IDs for control mechanisms for new facilities reported on a Pretreatment Program Report [40 CFR 403.12(i)]. Additionally, the NPDES program authority can decide whether to allow NPDES regulated entities to override these pre

-populated data. (2) The data elements in this table conform to EPA’s policy regarding the application requirements for renewal or reissuance of NPDES permits for discharges from municipal separate storm sewer systems (see 61 FR 41698; 6 August 1996). (3) The data elements in this table are also supported by the Office Management and Budget approved permit applications and forms for the NPDES program. (4) These data will allow EPA and the NPDES program authority to link facilities, compliance monitoring activities, complianc e determinations, and enforcement actions. For example, these data will provide several ways to make the following linkages: l inking violations to enforcement actions and final orders; linking single event violations and compliance monitoring activities; linking program reports to DMRs; linking program reports to compliance monitoring activities; and linking enforcement activities and com pliance monitoring activities

.