10/31/16 Page | 1 

### Appendix A to Part 127

[ DRAFT FOR SUPPLEMENTAL NOTICE

– CLEAN VERSION ]

The following two tables identify th e minimum set of data that states, tribes, territories, and NPDES

- regulated entities must electronically report to the designated initial recipient ( NPDES authorized program or EPA ) [see 40 CFR 127.2(b)]. Use of these two tables en sure s that there is consistent and complete reporting nationwide, and expedit ious collection and processing of the data, thereby making it more accurate and timely. Taken together, these data standardizations and the corresponding electronic reporting requirements in 40 CFR 3, 1 22, 123, 127, 403, and 503 are designed to save the NPDES authorized programs considerable resources, make reporting easi er for NPDES

- regulated entities, streamline permit renewals (as permit writers typically review previous noncompliance events during permit renewal), ensure full exchange of NPDES program data between states and EPA to the public, improve environmental dec ision

- making, and protect human health and the environment.

Instructions: Table 1 provides the list of data sources and minimum submission frequencies for the ten different NPDES Data Groups. Table 2 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 t he 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 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.10/31/16 Page | 2 Table 1 : Data Sources and Regulatory Citations 1

NPDES Data Group Number 2 NPDES Data Group Program Area Data Provider Minimum Frequency 3

1 Core NPDES Permitting, Compliance, and Enforcement Data [40 CFR 122, 123, 403, 503] All NPDES Program Sectors Authorized NPDES Program Within 30 days of the completed activity

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

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

2 General Permit Reports [Notice s of Intent to discharge (NOI s ); Notice s of Termination (NOT s ); No Exposure Certifications (NECs); Low Erosivity Waivers (LEWs)] [40 CFR 122.28 and 124.5 ] All NPDES Program Sectors NPDES Permittee Prior to General Permit Issuance

, Consideration for Permit Exclusion or Waiver from Permitting , and Permit Coverage Termination

3 Discharge Monitoring Report s [40 CFR 122.41(l)(4)] Most NPDES Program Sectors NPDES Permittee At least annual, although a more frequent submission required in the permit would

apply

4 Biosolids Annual Program Report s [40 CFR 503] Biosolids NPDES Regulated 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)

7 POTW Pretreatment Program Annual Report s [40 CFR 403.12(i)] Pretreatment POTW Pretreatment Control Authority Annual10/31/16 Page | 3 Table 1 : Data Sources and Regulatory Citations 1

NPDES Data Group Number 2 NPDES Data Group Program Area Data Provider Minimum Frequency 3

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 sewer overflow event (health or environment endangerment), Monitoring report frequency specific in permit (all other sewer overflow events)

10 CWA 316(b) Annual Report s [40 CFR 125 Subparts I, J and N ] CWA Section 316(b) NPDES Permittee Annual

Note 1: NPDES regulated entities regulated by a NPDES permit will comply with all reporting requirements in their respective NPDES pe rmit. 2

Note 2 : Use the “ NPDES Data Group Number ” in this table and the “ NPDES Data Group Number ” column in Table 2 to identify the source of the required data entry

. EPA 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 number (“ 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 new data regarding the Facility Individual First Name and Last Name ( NPDES Data Group 1 and 2 ) with thei r DMR submission when there is a facility personnel change.

Note 3: The applicable reporting frequency is specified in the NPDES permit or control mechanism, which may be more frequent than the minimum frequency specified in Table 1.

Note 4: 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 example, the following data element relies on historical data: Biosolids or Sewage Sludg e Amount (Permit)

- The amount of biosolids (in dry metric tons) produced by the permitted facility in the preceding 365

- day period for each different type of biosolids and sewage sludge generated by the facility.10/31/16 Page | 4

Note 5: For the purposes of this Appendix , biosolids refers to treated or processed domestic sewage sludge.

Note 6: Authorized states will be the data provider in the event an event where the regulated entity is covered by a waiver from elec tronic reporting.10/31/16 Page | 5 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Basic Facility Information (Note: As indicated in the “CWA, Regulatory, or Other Citation” column, some of these data elements apply to Significant Indu strial Users (SIUs) and Categorical Industrial Users (CIUs) when EPA or the State is the Control Authority).

Facility Type of Ownership The code/description identifying the type of facility (e.g., s tate g overnment, m unicipal or

w ater d istrict, Federal f

acility , tribal facility ). This data element is used by the EPA data system to populate the Permit F acility T ype data element (i.e., POTW, Private, Non

POTW, and Federal). 122.21

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 7

Facility Site Name The name of the facility. Th is data element includes facilities that are S ignificant Industrial User s (SIU s ) and Categorical Industrial Users (CIUs) that discharg e (including truck transportation) to one or more POTW s and to facilit ies or locations that generate or receiv e biosolids or sewage sludge

. 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. This data element includes facilities that are Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including truck transportation) to one or more POTWs and to facilities or locations that generate or receive biosolids or sewage sludge

. 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 whose boundaries (the majority of) the facility site is located. This is not always the same as the city used for USPS mail delivery. This data element includes facilities that are Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including truck transportation) to one or more POTWs and to facilities or locations that generate or receive biosolids or sewage sludge

. 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 710/31/16 Page | 6 Table 2 : Required NPDES Data

Data Name 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 that represents the state or state equivalent for the U.S. where the facility is located

. This data element includes facilities that are Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including truck transportation) to one or more POTWs and to facilities or locations that generate or receive biosolids or sewage sludge

. 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, 50 3.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 data element includes facilities that are Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including truck transportation) to one or more POTWs and to facilities or locations that generate or receive biosolids or sewage sludge

. 122.21

, 122.21(j)(6), 122.21(q), 122.2 8(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 Bureau of Indian Affairs code for every unit of land trust allotment (“tribal land”) within Indian Country. This code will identify whether the facility is on t ribal l and and the name of the American Indian tribe or Alaskan Native entity (if applicable). 122.21

, 122.28(b)(2)(ii) 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. Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees (e.g.,

- 77.029289 ) and in accordance with Environmental Data S tandards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. This data element includes facilities that are Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including truck transp ortation) to one or more POTWs and to facilities or locations that generate or receive biosolids or sewage sludge . T his data element will also be used to describe the two

- dimensional area (polygon) regulated by a municipal storm sewer system (M S4 ) NPDES permit through use of multiple latitude and longitude coordinates

. 122.21

, 122.21(q), 122.28(b)(2)(ii) , 503.18, 503.28, 503.48 1,2 , and 410/31/16 Page | 7 Table 2 : Required NPDES Data

Data Name 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. Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees (e.g., 38.893829 ) and in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. This data element includes facilities that are Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) that discharge (including truck transportation) to one or more POTWs and to facilities or locations that generate or receive bi osolids or sewage sludge

. 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 122.21

, 122.21 (q), 122.28 (b)(2)(ii)

, 503.18, 503.28, 503.48 1,2, and 4

Facility Site Source Map Scale Number The proportional distance on the ground for one unit of measure on the map or photo for the facility

. These data are provided in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. EPA National Geospatial Data Policy

– CIO Policy Transmittal 05

- 002 1,2

Facility Site Horizontal Accuracy Measure The measure of the accuracy (in meters) of the facility’s latitude and longitude coordinates. These data are provided in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. EPA National Geospatial Data Policy

– CIO Policy Transmittal 05

- 002 1,2

Facility Site Horizontal Collection Method Description of the method used to determine the latitude and longitude coordinates for the facility. These data are provided in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. EPA National Geospatial Data Policy

– CIO Policy Transmittal 05

- 002 1,2

Facility Site Horizontal Reference Datum The code/description for the reference datum used in determining latitude and longitude coordinates for the facility

. These data are provided in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. EPA National Geospatial Data Policy

– CIO Policy Transmittal 05

- 002 1,210/31/16 Page | 8 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Facility Site Reference Point The code/description for the place for which geographic coordinates were established. These data are provided in accordance with Environmental Data Standards Council

, L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. EPA National Geospatial Data Policy

– CIO Policy Transmittal 05

- 002 1,2

Facility Individual Affi liation Type Code The way that the contact or address is affiliated with the facility (e.g., "Owner," “Operator,” or "Main Contact"). This is a unique code that identifies the nature of the individual's affiliation to the facility. 122.21

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i), 1,2, 4, and 7

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

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 7

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

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 7

Facility Individual Title The title held by an individual in an organization affiliated with this facility. 122.21

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 7

Facility Individual Organization The legal, formal name of an organization that is affiliated with the individual affiliated with this facility. 122.21

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 7

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

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 7

Facility Individual City The name of the city, town, village, or other locality for the individual affiliated with this facility. 122.21

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 710/31/16 Page | 9 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Facility Individual State The U.S. Postal Service (USPS) abbreviation that represents the state or state equivalent for the U.S. for the individual affiliated with this facility. 122.21

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 7

Facility Individual Zip Code The combination of the 5

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

- digit extension code (if available) that represents the geographic segment that is a sub unit of the ZIP Code assigned by the U.S. Postal Service to a geographic location for the individual affiliated with this facility. 122.21

, 122.28(b)(2)(ii)

, 403.8(f), 403.1 0, 403.12(i) 1,2, 4, and 7

Facility Individual E

- Mail Address The e

- mail address of the designated individual affiliated with this facility. 122.21

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 7

Facility Organization Formal Name The legal, formal name of an organization that is affiliated with the facility. 122.21

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 7

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

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 7

Facility Organization City The name of the city of the organization that is affiliated with the facility. 122.21

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 7

Facility Organization State The U.S. Postal Service abbreviation that represents the state or state equivalent for the organization affiliated with the facility. 122.21

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 710/31/16 Page | 10 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Facility Organization Zip Code The combination of the 5

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

- digit extension code (if available) that represents the geographic segment that is a sub unit of the ZIP Code assigned by the U.S. Postal Service to a geographic location for the organization affiliated with the facility. 122.21

, 122.28(b)(2)(ii)

, 403.8(f), 403.10, 403.12(i) 1,2, 4, and 7

Basic Permit Information (Note: As indi cated in the “CWA, Regulatory, or Other Citation” column, some of these data elements apply to Significant Industrial Users ( SIUs) and Categorical Industrial Users (CIUs) when EPA or the State is the Control Authority)

.

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

. 403.10 1,2

Master General Permit Number The unique identifier of the master general permit, which is linked to a General Permit Covered Facility. This data element applies to facilities regulated by a master general permit. 403.1 0 1,2

Permit Type The unique code/description identifying the type of permit. 122.2

, 403.10 1,2

Permit Component This will identify one or more applicable NPDES subprograms (e.g., pretreatment, CAFO, CSO, POTW, biosolids, stormwater) for the permit record. This field is only required when the permit includes one or more NPDES subprograms. 122.2, 403.10 1,2

Permit Is sue Date This is the date the permit was issued. The date must be provided in YYYY

- MM

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

. 122.46

, 403.10 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 YY YY is the year, MM is the month, and DD is the day

. 122.46 , 403.1 0 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 YY YY is the year, MM is the month, and DD is the day

. 122.62, 122.63 , 403.1 0 110/31/16 Page | 11 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

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

- MM

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

. 122.46 , 403.10 1

Permit Termination Date This is the date the permit was terminated. The date must be provided in YYYY

- MM

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

. This data element can be system generated when the permittee does not file a permit renewal application. 122.64

, 403.10 1

Permit Major/Minor Status Indicator The flag to indicate if the permit is a major or non

- major (“ minor ”)

. This data element is i nitially system generated (defaults to “ Minor ” ) and updatable only by EPA OECA Headquarters

. 122.2 1

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

generated to match effective date and updatable only by EPA OECA Headquarters

. The date must be provided in YYYY

- MM

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

. 122.2 1

Permit Application Total Design Flow This is the total flow that a permitted facility was designed to accommodate, in millions of gallons per day ( MGD ), as stated on its NPDES application. This data element does not apply to regulated entities that do not discharge (e.g., some biosolids generators) and entities that only discharge stormwater. 122.21

, 122.28(b)(2)(ii)

, 403.10(f), 1,2

Permit Application Total Actual Av erage Flow This is the average total flow that a permitted facility will actually discharge at the start of its permit term, in MGD, as stated on its NPDES application

. This data element does not apply to regulated entities that do not discharge (e.g., some biosolids generators) and entities that only discharge stormwater. 122.21, 122.28(b)(2)(ii)

, 122.41 , 403.10(f) 1,210/31/16 Page | 12 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Complete Permit Application/NOI Received Date This is the date on which the complete application for a 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 YY YY is the year, MM is the month, and DD is the day

. This data element can be system generated when the complete NPDES permit application or complete 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 a 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 YY YY is the year, MM is the month, 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 code/description that indicates whether the permit is Effective, Expired, Administratively Continued, Pending, Not Needed, Retired, or Terminated. 122.64, 122.46

, 403.10(f) 1

Master General Permit Industrial Category This code/description identifies the industrial category covered by the master general permit. This field is system

- required for master general permits only. 122.28(b)(2)(ii), 403.10(f) 1

Permit Issuing Organization Type This is the type of organization issuing or granting a permit. 12 3 .4 1 , 403.10(f) 1

DMR Non

- Receipt Turns non

- r eceipt tracking for discharge monitoring reports (DMRs) “ on ” or “ off ” for

non

- major permits (a.k.a. “minors”)

. This field is always “on” for m ajor permit s. This field is initially set to “on.” This data element is system generated and can be modified by EPA Headquarters. 123.45 1

Reportable Noncompliance T racking Turns r eportable n oncompliance (RNC) tracking “ on ” or “ off ” for non

- major permits (a.k.a. “minors”)

. This field is always “on” for m ajor permit s. This field is initially set to “on.” This data element is system generated and can be modified by EPA Headquarters. 123.45 110/31/16 Page | 13 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Applicable Effluent Limit ations Guideline s The applicable effluent limitations guideline s and new source performance standards for the NPDES permit (e.g., Part 414

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

. 122.44 , 403.10(f) 1

Permit Compliance Tracking Status This is a code/description that indicates whether the permit is currently “ on ” or “ off ” for compliance tracking purposes. Initially system

- generated to match effective date. 123.45 , 403.10(f) 1

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

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

- MM

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

. 123.45 , 403.10(f) 1

RNC Status Quarter The quarter of the p ermit reportable noncompliance ( RNC ) status. 123.45 , 403.10(f) 1 RNC Status Year The year of the p ermit reportable noncompliance ( RNC ) status. 123.45 , 403.10(f) 1

RNC Status (Manual) The status of reportable noncompliance (RNC) as it was entered by the regulatory authority before the official Quarterly Noncompliance Report (QNCR) or NPDES Noncompliance Report (NNCR) for the RNC quarter for the permit. 123.45 , 403.10(f) 1

Associated NPDES ID Numbers If applicable, t he unique identifier for a NPDES Permit that is related to another NPDES Permit or other NPDES ID number. For example, this data element could be used to identify the receiving POTW’s permit number for an industrial user

, the recipient POTW’s permit number f or a satellite collection system

, and 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). 403.10(f) 1 through 5, 7, 8, 9

SIC Codes The four

- digit Standard Industrial Classification (SIC) code/description that represents the economic activity of the facility

. 122.21

, 122.28(b)(2)(ii)

, 403.10(f) 1 ,2, and 710/31/16 Page | 14 Table 2 : Required NPDES Data

Data Name 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. 122.21, 122.28(b)(2)(ii), 403.10(f) 1,2, and 7

NAICS Codes The six

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

. EPA SIC/NAICS Data Standard, Satndard No. EX000022.2, 6 January 2006, O ffice of Management and Budget, Executive Office of the Pr esident, Final Decision on North American Industry Classification System (62 FR 17288)

, 403.10(f) 403.10(f)

, 1,2, and 710/31/16 Page | 15 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

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. EPA SIC/NAICS Data Standard, Satndard No. EX000022.2, 6 January 2006, Office of Management and Budget, Executive Office of the President, Final Decision on North American Indus try Classification System (62 FR 17288), 403.10(f) 403.10(f), 1,2, and 7

Permittee Street Address The mailing street address of the permit holder. 122.21

, 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.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.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.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.28(b)(2)(ii), 403.10(f) 1,210/31/16 Page | 16 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

NPDES Data Group Number This is the u nique code/ description that identifies the types 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)] }. 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

Electronic Submission Type This is the unique code/description for each NPDES program data submitted by the facility (“ NPDES Data Group Number ”) that describes how the data was electronically collected or processed. 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 prog ram 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 da ta 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 authorized NPDES program who then electronically uses manual data entry to electronica lly process these data ; (5) 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; (6) NPDES regulat ed entity submits NPDES program data using an other electronic reporting system (e.g., third

- party). This data element could be system generated for NPDES program data electronically reported by NPDES regulated entities. 123.26, 123.41(a) and CWA 308 1

Narrative Condition s and Permit Schedules (Note: As indicated in the “CWA, Regulatory, or Other Citation” column, some of these data elements apply to Significant Indu strial Users (SIUs) and Categorical Industrial Users (CIUs) when EPA or the State is the Control Authority).10/31/16 Page | 17 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )
Description The unique code/ description that identifies the type of narrative condition. 122.47 , 403.10(f) 1

Narrative Condition Number This identifies a narrative condition and its elements uniquely for a permit. 122.47 , 403.10(f) 1

Schedule Date The date on which a 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 YY YY is the year, MM is the month, and DD is the day

. 122.47 , 403.10(f) 1

Actual Date The date on which the permittee achieved the schedule event. The date must be provided in YYYY

- MM

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

. 122.47 , 403.10(f) 1

Report Received Date The date on which the regulatory authority receives a report from the permittee indicating that a Schedule Event was completed (e.g., Start Construction) or the required report was enclosed. The date must be provided in YYYY

- MM

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

. 122.47 , 403.10(f) 1

Event The code (s) or description (s) indicating the particular event (s) with which the permittee is scheduled to comply. This i nclude s program reports including the Cooling Water Yearly Status Report , which all new facilities subject to 125 Subpart I or N must submit

. 122.47 , 403.10(f) 1

Permitted Feature (Note: These ‘ Permitted Feature ’ data elements are only required to be submitted for permits that require 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 U sers (SIUs) and Categorical Industrial Users (CIUs) when EPA or the State is the Control Authority).
Application Design Flow (MGD) The flow that a permitted feature was designed to accommodate, in MGD. This data element does not apply to regulated entities that do not discharge (e.g., some biosolids generators) and entities that only discharge stormwater. 122.21

, 122 .28(b)(2)(ii)

, 403.10(f) 1 ,210/31/16 Page | 18 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

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

, as stated on its NPDES application

. . This data element does
not apply to regulated entities that do not discharge (e.g., some biosolids generators) and entities that only discharge stormwater. 122.21

, 122.28(b)(2)(ii)

, 403.10(f) 1 ,2

Permitted Feature ID The identifier assigned for each location at which conditions are being applied. 122.21

, 122.28(b)(2)(ii)

, 403.10(f) 1 ,2

Type The code/description indicating the type of permitted feature (e.g. External Outfall, Sum

, 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 . Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees (e.g.,

- 77.029289 ) and in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. 122.21

, 122.28(b)(2)(ii) 1 ,2

Permitted Feature Latitude The measure of the angular distance on a meridian north or south of the equator for the f permitted feature . Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees (e.g., 38.893829 ) and in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. 122.21

, 122.28(b)(2)(ii) 1 ,2

Permitted Feature Source Map Scale Number The number that represents the proportional distance on the ground for one unit of measure on the map or photo for the permitted feature

. These data are provided in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. EPA National Geospatial Data Policy

– CIO Policy Transmittal 05

- 002 1 ,210/31/16 Page | 19 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Permitted Feature Horizontal Accuracy Measure The measure of t he accuracy (in meters) of the permitted feature ’s lat itude and longitude coordinates. These data are provided in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. EPA National Geospatial Data Policy

– CIO Policy Transmittal 05

- 002 1 ,2

Permitted Feature Horizontal Collection Method The text that describes the method used to determine the latitude and longitude coordinates for the permitted feature

. These data are provided in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. EPA National Geospatial Data Policy

– CIO Policy Transmittal 05

- 002 1 ,2

Permitted Feature Horizontal Reference Datum The code/description that represents the reference datum used in determining latitude and longitude coordinates for the permitted feature

. These data are provided in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. EPA National Geospatial Data Policy

– CIO Policy Transmittal 05

- 002 1 ,2

Permitted Feature Reference Point The code/description for the place for which geographic coordinates were established. These data are provided in accordance with Environmental Data Standards Council

, L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. EPA National Geospatial Data Policy

– CIO Policy Transmittal 05

- 002 1 ,2

POTW Wastewater Treatment Technology Level Description This data element describes the level of wastewater treatment technology (e.g., primary equivalent to secondary, secondary, advanced, other) at each outfall. This data element only applies to POTWs. 122.21(j)(3)(iii) and CWA 516 1,2

POTW Wastewater Treatment Technology Unit Operations The code/description of the wastewater treatment technology unit operations (e.g, grit removal, flow equalization, complete mix activated sludge secondary treatment, biological nitrification) at each outfall . This data element is required for POTWs that discharge above 10 MGD and is optional below 10 MGD

. 122.21(j)(2)(ii)(A) and CWA 516 1,210/31/16 Page | 20 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Limit Set (Note: These ‘ Limit Set ’ data elements are only required to be submitted for permits that require effluent limits and 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 Use rs (SIUs) and Categorical Industrial Users (CIUs) when EPA or the State is the Control Authority ).
Limit Set Designator The alphan umeric field that is used to designate a particular grouping of parameters within a limit set. 122.45 , 403.10(f) 1

Type The unique code/description identifying the type of limit set (i.e. Scheduled, Unscheduled). 122.45 , 403.10(f) 1

Months Limit Set Applies The default months that the limit set applies. Defaults to all 12 months. 122.45 , 403.10(f) 1

Initial Monitoring Date The date on which monitoring starts for the first monitoring period for the limit set; this date will be blank for Unscheduled L imit Sets. The date must be provided in YYYY

MM

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

. 122.45 , 403.10(f) 1

Initial DMR Due Date The date that the first DMR for the limit set is due to the regulatory authority; this date will be blank for Unscheduled Limit Sets. The date must be provided in YYYY

- MM

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

. 122.45 , 403.10(f) 1

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

annually = 6, quarterly = 3). For example, if the permittee was required to provide reports for each month, the number of report units would be one. 122.45 , 403.10(f) 1

Number of Submission Units The number of months between DMR 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 (=mo nthly) and the number of submission units would be three (=three months of information in each submission). 122.45 , 403.10(f) 110/31/16 Page | 21 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Status The status of the Limit Set (i.e., Active or Inactive); Limit Sets will not have violations generated when a Limit Set is Inactive unless an Enforcement Action Limit is present. 122 Subpart C , 403.10(f) 1

Limit Set Status Start Date The date that the Limit Set Status started. The date must be provided in YYYY

- MM

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

. 123.45 , 403.10(f) 1

Limit (Note: These ‘Limit’ data elements are only required to be submitted for permits that require effluent limits and outfall mon itoring for stationary point sources. Additionally, as indicated in the “CWA, Regulatory, or Other Citation” column, some of these data elements apply to Significant Industrial Use rs (SIUs) and Categorical Industrial Users (CIUs) when EPA or the State is the Control Authority).
Monitoring Location The code/description of the monitoring location at which sampling should occur for a limit parameter. 122.45 , 403.10(f) 1

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

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 YY YY is the year, MM is the month, and DD is the day

. 122.45 , 403.10(f) 1

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 YY YY is the year, MM is the month, and DD is the day

. 122.45 , 403.10(f) 1

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

Stay Type 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 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) 110/31/16 Page | 22 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )
Stay Start Date The date on which a limit stay begin s. The date must be provided in YYYY

- MM

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

. 124.19 , 403.10(f) 1

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

- MM

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

. 124.19 , 403.10(f) 1

Reason for 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 Type The code that indicates whether a limit is an enforceab le, 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 Enforcement Action that imposed the Enforcement Action limit; this data element helps tie the limit record to the Final Order record in the database. 122.45 , 403.10(f) 1

Final Order ID The unique identifier for the Final Order that imposed 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 be provided in YYYY

- MM

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

. 122.62 , 403.10(f) 1

Modification Type The type of permit modification that created this limit (e.g. major, minor, permit authorized change). 122.62 , 403.10(f) 1

Parameter The unique code/description identifying the parameter being limited and/or monitored. 122.41(j)

, 403.10(f) 110/31/16 Page | 23 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Months The months that the limit applies. Defaults to limit set months. 122.46 , 403.10(f) 1

Value Type The indication of the limit value type (e.g., Quantity 1, Concentration 2). 122.45(f) , 403.10(f) 1

Quantity Units

, Concentration Units The 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 code/description representing the unit of measure applicable to the limit and DMR values entered by the user (e.g., 30

- day average, daily maximum). 122.45(d) , 403.10(f) 1

Optional Monitoring Flag The flag allowing users to indicate that monitoring is optional but not required (i.e., effluent violation generation will be suppressed for optional monitoring). 122.45 , 403.10(f) 1

Qualifier The unique code identifying the limit value operator (e.g

. , <, =, >). 122.45 , 403.10(f) 1

Value The actual limit value number from the Permit or Enforcement Action Final Order. 122.45 , 403.10(f) 1

Biosolids Information on NPDES Permit Application or Notice of Intent (Note: The ‘ Biosolids Management Facility Type ’ is also required for the Biosolids Annual Report ).

Biosolids Management Facility Type The unique code/description that identifies whether the facility was issued a permit as a biosolids generator, processor, or end user (e.g., land application site, surface disposal site, incinerator). For the Biosolids Annual Report this data element is also t he unique code/description that identifies an off

- site facility or location receives biosolids or sewage sludge from this facility. 122.21(q)

, 122.28(b)(2)(ii)

, 503.18, 503.28, 503.48 1,2 , and 410/31/16 Page | 24 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Biosolids or Sewage Sludge Treatment Processes (Permit) This data element identifies the biosolids or sewage sludge treatment process or processes at the facility. For example, this may indicate whether primary, secondary, and tertiary treatment is being used, and the type of the biosolids or sewage sludge treatment process or processes used, including drying processes. 122.21(q)(6), 122.28(b)(2)(ii) 1.2

Biosolids or Sewage Sludge Management Practice (Permit) This data element will identify the type of biosolids or sewage sludge management practice or practices (e.g., land application, surface disposal, incineration) for each different form of biosolids and sewage sludge generated by the facility. 122.21(q)(6), 122.28(b)(2)(ii) 1.2

Biosolids or Sewage Sludge Form (Permit) This data element describes 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 practice used by the facility. 122.21(q)(6), 122.28(b)(2)(ii) 1.2

Biosolids or Sewage Sludge Pathogen Class (Permit) This data element will identify the pathogen class or classes (e.g., Class A, Class B) of biosolids or sewage sludge generated by the facility. The facility will separately report the pathogen class for each biosolids or sewage sludge manage ment 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 Options (Permit) This data element will identify the land application and surface disposal vector attraction reduction options used by the facility. 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 slu dge 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 Land Application Option (Permit) This data element will identify the land application option or options used by the facility (e.g., EQ, PC, CPLR, APLR). The facility will separately report the land application option for each biosolids or sewage sludge management practice used by the faci lity and for each biosolids or sewage sludge form as well as by each biosolids or sewage sludge pathogen class and each vector attraction reduction option. 122.21(q)(6), 122.28(b)(2)(ii) 1.210/31/16 Page | 25 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Biosolids or Sewage Sludge Amount (Permit) The amount of biosol ids (in dry metric tons) produced by the permitted facility in the preceding 365

- day period for each different type of biosolids and sewage sludge generated by the facility. This identification will be made for each biosolids or sewage sludge management pr actice or practices used by the facility, each biosolids or sewage sludge form, each pathogen class, each vector attraction reduction option, and each land application option

. 122.21 (q)

, 122.28(b)(2)(ii) 1,2

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

Facility CAAP Flag A binary “yes/no” flag to indicate whether the facility includes Concentrated Aquatic Animal Production (CA AP ). 12 2.21(i)(2 ), 122.24, 122.25, 122.28(b)(2)(ii) 1,2

Facility CAFO Flag 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 Concentrated Animal Feeding Operation (CAFO). The date must be provided in YYYY

- MM

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

. 122.23 110/31/16 Page | 26 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 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) t he size of the AFO and the amount of wastes reaching waters of the United States; (2) t he location of the AFO relative to waters of the United States; (3) t he means of conveyance of animal wastes and process 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 relevant factors.

. 122.23(c) 1

CAFO Animal Type 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,
t urkeys, other)

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

CAFO Animal Maximum Number s The 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 mor e 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 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 a 12 month period. 122.2 1(i)(1)(v)

, 122.28(b)(2)(ii) 1,2

CAFO MLPW The unique code/description that identifies t he type of CAFO material generated by the facility (i.e., manure, litter, and process wastewater or ‘MLPW’ ) in a 12 month period

. 122.2 1(i)(1)(v iii )

, 122.28(b)(2)(ii) 1,210/31/16 Page | 27 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

CAFO MLPW Amounts The maximum amount of CAFO material generated by the facility (i.e.

, manure, litter

, and process wastewater) in a 12 month period

. 122.2 1(i)(1)(v iii )

, 122.28(b)(2)(ii) 1,2

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

. 122.2 1(i)(1)(v iii )

, 122.28(b)(2)(ii) 1,2

CAFO MLPW Transferred The maximum amount of CAFO material generated by the facility (i.e., manure, litter

, and process wastewater) 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 material (i.e., manure, litter , and process wastewater)

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

CAFO MLPW Containment and Storage Type Code The type (s) of CAFO material 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.

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

CAFO MLPW Containment and Storage Maximum Capacity Amounts The maximum storage or containment value for each CAFO material containment and storage type at the facility. 122.2 1 (i) (1)(vi), 122.28(b)(2)(ii) 1,2

CAFO MLPW Containment and Storage Maximum Capacity Amounts Unit The unit for the maximum storage or containment value for each CAFO material containment and storage type at the facility (e.g., gallons). 122.2 1 (i) (1)(vi), 122.28(b)(2)(ii) 1,210/31/16 Page | 28 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Construction and Industrial Stormwater Information (from the permitting authority derived from the NPD ES Permit Application, Notice of Intent, or No Exposure Certification, or Low Erosivity Waiver)

Permit Required by Residual Designation The permit writer may designate additional storm water discharges as requiring NPDES permits whe n 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 pollutants to waters of the United States

. This data element identifies whether the permit writer is using t his authority

, commonly referred to as the

“ Residual Designation” authority, to regulate stormwater discharges through a NPDES permit. CWA 402(p)(2)(E) and (6) and 1 22.26 (a)(9)(i)(D) 1

Residual Designation Determination Date The date when the permit writer made the designation that the stormwater discharge s , or category of discharges within a geographic area, contributes to a violation of a water quality standard or is a significant cont ributor of pollutants to waters of the United States

. The date must be provided in YYYY

- MM

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

. CWA Section 402(p)(2)(E) and (6) and 1 22.26 (a)(9)(i)(D) 1

No Exposure Certification Approval Date This is the date on which the No Exposure Certification (NEC) was 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 r unoff. This date would be provided by the permitting authority. The date must be provided in YYYY

MM

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

. 122.26 (g) 110/31/16 Page | 29 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Low Erosivity Waiver Approval Date The NPDES Stormwater Phase II Rule allows NPDES pe rmitting authorities to accept “low erosivity waivers” (LEWs) for small construction sites. The waiver process exempts small construction sites (disturbing under five acres) from NPDES permitting requirements when the rainfall erosivity fact or is less than five during the period of construction activity

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

- MM

- DD format

, where YY YY is the year, MM is the month, and DD is the day

. 122.26(b)(15) 1

Construction Stormwater Information on NPDES Permit Application, Notice of Intent, or Waiver Request [ including stormwater large construction activity requiring permit coverage under 122.26(b)(14)(x) ]

Total Area of the Site This is the total area (to the nearest quarter acre) of the construction site. Th is data field is only required for individual construction stormwater permit applications. 122.26 (c)(1)(ii)(B ), 122.28(b)(2)(ii) 1

Total Activity Area (Construction) Total area (to the nearest quarter acre) of the construction activities. 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, excav ated materials disposal areas, borrow areas). 122.26 , 122.28(b)(2)(ii) 1,2

Post

- Construction Total Impervious Area Total impervious area (to the nearest quarter acre) of the site after the construction addressed in the permit application is completed . Thi s data field is only required for individual construction stormwater permit applications. 122.26(c)(1)(ii)(E) 1

Proposed Stormwater Best Management Practices for Construction Activities This is a code/description that describes the p roposed measures, including best management practices, to control pollutants in stormwater discharges from construction activities. This includes a brief description of applicable s tate and local erosion and sediment control requirements

. 122.26(c)(1)(ii)(C)

, 122.28(b)(2)(ii) 1 ,210/31/16 Page | 30 Table 2 : Required NPDES Data

Data Name 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 a code/description that describes the p roposed measures to control pollutants in stormwater discharges that will occur after construction operations have been completed, including a brief description of applicable s tate or loca l erosion and sediment control requirements . This data field is only required for ind ividual construction stormwater permit applications. 122.26(c)(1)(ii)(D) 1

Soil and Fill Material Description This is a code/description that field describes the nature of fill material and existing data describing soils or the quality of the discharge. T his data field is only required for individual construction stormwater permit applications. 122.26(c)(1)(ii)(E) 1

Runoff Coefficient of the Site This is an estimate of the runoff coefficient of the site after the construction addressed in the permit application is completed . This data field 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 YY YY

- MM

- DD format where YY YY is the year, MM is the month, 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 YY YY

- MM

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

. 122.26, 122.28(b)(2)(ii) 1,2

Industrial Stormwater Information on NPDES Permit Application, Notice of Intent, or Permitting Exclusion Request (excluding large construction activity requiring permit coverage under 122.26(b)(14)(x))

Total Activity Area (Industrial) Total area (to the nearest quarter acre) of the faci lity that contains industrial activities and processes. These activities and processes may include (but are not limited to) u sing, storing or cleaning industrial machinery or equipment, and areas where residuals from using, storing or cleaning industrial machinery or equipment remain and are exposed to
stormwater ; m aterials or products stored outdoors ; m aterials contained in open, deteriorated or leaking storage drums, barrels, tanks, and similar containers ; and m aterials or products from past industrial a ctivity

. 122.26 , 122.28(b)(2)(ii) 1,210/31/16 Page | 31 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Current Total Impervious Area The current t otal impervious area (to the nearest quarter acre) of the facility. This data field is only required for individual industrial stormwater permit applications. 122.26(c)(1)( i)(B), 1 Proposed Stormwater Best Management Practices for Industrial Activities This is a field that describes the structural and non

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

. 122.26(c)(1)(i)(B), 122.28(b)(2)(ii) 1 ,2

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

MS4 Permit Class The unique code/description that identifies the size of the MS4 permit holder : Phase I

– large or medium MS4s and Phase II

– small MS4s

. 122.26 , 122.28(b)(2)(ii) 1 ,2

Unique Number for Each Municipality Covered Under MS4 Permit The u nique number for each municipality covered under MS4 permit. Use of t his number will allow greater geographic resolution for the MS4 components being tracked and ensure consistency from year to year. The number would essentially be similar to an outfall number, for distinguishing compliance at various locations. 122.28(b)(2)(ii) and CWA 301(d), 304(b) 1,2, 6

MS4 Public Education Program The unique code/description that identifies the educational materials the permittee intend s to distribute or equivalent outreach activities ther permittee will implement to inform the community 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)(B), (D)(4) and (A)(6); 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 unique code/description 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 frequenc y of the action. This data field only applies to Phase II MS4s. 122.34(d)(1)(ii)

, 122.28(b)(2)(ii) 210/31/16 Page | 32 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

MS4 Public Involvement and P articipation Program The unique code/description 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 unique code/description 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 field only applies to Phase II MS4s

. 122.28(b)(2)(ii) 122.34(d)(1)(ii) 2

MS4 Illicit Discharge Detection and E limination: MS4 System Map The unique code/description that identifies whether the permittee has developed a storm sewer system map showing the location of all outfalls and names and locations of all waters of the U.S. that receive discharges from those outfalls

. 122.21(f)

, 122.26(d)(1)(iii)(B), 122.28(b)(2)(ii)

, 122.34(b)(3)(ii)(A)

, 122.34(d)(1)(i)

, 1,2

MS4 Illicit Discharge Detection and Elimination: Ordinance or Other Regulatory Mechanism The unique c ode/description that identifies whether the permittee has enacted an ordinance or other regulatory mechanism to prohibit non

- stormwater discharges into its MS4 to the extent allowable by state, local or tribal law

. 122.21(f)

, 122.26(d)(2)(i)(B) and (C), 122.26(d)(2)(iv)(B)(1), 122.28(b)(2)(ii)

, 122. 34(b)(3)(ii)(B), 122.34(d)(1)(i); 1,2

MS4 Illicit Discharge Detection and Elimination : Enforcement The unique code/description that identifies the procedures and actions the permittee will take to enforce the prohibition on non

- stormwater discharges to the MS4. 122.21(f)

, 122.26(d)(2)(iv)(B)(1), 122.28(b)(2)(ii)

, 122.34(b)(3)(ii)(B), 122.34(d)(1)(i) 1,210/31/16 Page | 33 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

MS4 Illicit Discharge Detection and Eli mination Program The unique code/description that identifies the procedures and actions the permittee will take to detect and address non

- stormwater discharges, including illegal dumping, to permittee’s system. 122.21(f), 12 2.26(d)(2)(iv)(B )

, 122.28(b)(2)(ii), 122.34(b)(3)(ii)(C)

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

MS4 Illicit Disch arge Detection and Elimination: Public Education The unique code/description that identifies the procedures and actions the permittee will take to inform public employees, businesses and the general public of hazards associated with illegal discharges and improper disposal of waste. 122.21(f), 122.26(d)(2)(iv)(B), 122.28(b)(2)(ii), 122.34(b)(3) (ii)(D)

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

MS4 Measurable Goals Associated With Illicit Discharge Detection and Elimination Program The unique code/description 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 field only applies to Phase II MS4s. 122.34(d)(1)(ii) 2

MS4 Constructi on Site Stormwater R unoff Control O rdinance or Other Regulatory Mechanism The unique code/description that identifies the permittee’s ordinance to the extent allowable by state, local or tribal law or other regulatory mechanism, including sanctions
to ensure compliance, to require erosion and sediment controls

. 122.21(f), 122.26(d)(2)(iv)( D ), 122.28(b)(2)(ii), 122.34(b)(4)(ii)(A)

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

MS4 Construction Site Stormwater Runoff Control Program : Erosion and S ediment C ontrols The unique code/description that identifies the permittee’s requirements for construction site operators to implement appropriate erosion and sediment control BMPs. 122.21(f), 122.26(d)(2)(iv)(D), 122.28(b)(2)(ii), 122.34(b)(4)(ii)(B)

, 122.34(d)(1)(i) 1,210/31/16 Page | 34 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

MS4 Construction S ite Stormwater Runoff Control Program : W aste Control The unique code/description that identifies the permittee’s requirements for construction site operators to control waste such as discarded building materials, concrete truck washout, chemi cals, litter, and sanitary waste at the construction site that may cause adverse impacts to water quality

. 122.21(f), 122.26(d)(2)(iv)(D), 122.28(b)(2)(ii), 122.34(b)(4)(ii)(C)

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

MS4 Construction S ite Stormwater Runoff Control Program: Plan R eview The unique code/description that identifies the permittee’s procedures for site plan review which incorporate consideration of potential water quality impacts

. 122.21(f), 122.26(d)(2)(iv)(D), 122.28(b)(2)(ii)

, 122.34(b)(4)(ii)(D)

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

MS4 Construction Site Stormwater Runoff Control Program: Public Information The unique code/description that identifies the permittee’s procedures for receipt and consideration of information submitted by the public. 122.21(f), 122.26(d)(2)(iv)(D), 122.28(b)(2)(ii), 122.34(b)(4)(ii)(E)

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

MS4 Construction Site Stormwater Runoff Control Program : Site Inspections And Enforcement The unique code/description that identifies the permittee’s procedures for site inspection and enforcement of control measures. 122.21(f), 122.26(d)(2)(iv)(D) (3)

, 122.28(b)(2)(ii), 122.34(b)(4)(ii)(F)

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

MS4 Measurable Goals Associated with the Construction Site Stormwater Runoff Control Program The unique code/descripti on that identifies the measurable goals associated with the construction progra m, i ncluding, 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 field only applies to Phase II MS4s. 122.34(d)(1)(ii) 210/31/16 Page | 35 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

MS4 Post

- Construction Stormwater Management In New Development And Redevelopment : BMPs The unique code/description that identifies the combination of structural and/or non

structural b est management practices (BMPs) (including o n which MS4s require retention on site of particular sized storms or runoff volumes ), which the permittee is using to address stormwater runoff from new development and redevelopment projec ts that disturb greater than or equal to one acre. 122.21(f), 122.26(d)(2)(iv)( A )( 2 ), 122.28(b)(2)(ii), 122.34(b)(5)(ii)(A)

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

MS4 Post

- Construction Stormwater Management In New Development And Redevelopment : \ Ordinance or Other Regulatory Mechanism The unique code/description that identifies the permittee’s ordinance to the extent allowable by state, local or tribal law or other regulatory mechanism to address post

construction runoff from new development and redevelopm ent projects

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

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

MS4 Post

- Construction Stormwater Management In New Development And Redevelopment: Long

Term Maintenance Of B MPs The unique code/description that identifies the permittee’s program to ensure adequate long

- term operation and maintenance of BMPs used for controlling runoff from new development and development projects. 122.21(f), 122.26(d)(2)(iv)(A)(2), 122.28(b)(2)(i i), 122.34(b)(5)(ii)(C)

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

MS4 Measurable Goals Associated with the Post

Construction : Stormwater Management Program The unique code/description that identifies 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 field only applies to Phase II MS4s. 122.34(d)(1)(ii) 2

MS4 Pollution Prevention/ Good Housekeeping for Municipal Operations Program The unique code/description that identifies the permittee’s operation and maintenance program that includes a training component and has the ultimate goal of preventing or reducing po llutant runoff from municipal operations. 122.21(f), 122.26(d)(2)(iv)(A)(2), 122.28(b)(2)(ii), 122.34(b)(6)(i)

, 122.34(d)(1)(i) 1,210/31/16 Page | 36 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

MS4 Additional Measures The unique code/description that identifies the any other additional measures in the permittee’s stormwater management program that is required by the permit such as controls to be consistent with the assumptions and requirements of any available wasteload allocation prepared by a state and approved by EPA

. 122.28(b)(2)(ii)

, 122.34(b), 122.34(d) 122. 44(d)(1)(vii)(B) 1,2

MS4 Measurable Goals for Additional Measures The unique code/description that identifies the measurable goal for any additional
program measure

. This data field only applies to Phase II MS4s. 122.28(b)(2)(ii)

, 122.34( e ) 2

POTW Collection System Information on NPDES Permit Application or Notice of Intent

Name of Collection System Th is is the unique name of each collection system that provid es flow to the permittee

. This includes unincorporated connector districts and satellite c ollection systems, which are sanitary sewers owned or operated by another entity that conveys sewage or industrial wastewater 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 System 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 satelli te collection systems

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

, 122.28(b)(2)(ii) 1,2

Permit Number for Collection System This is the NPDES permit number (if any) 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

Population of Collection System Th is is the population for each unique co llection 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,210/31/16 Page | 37 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Percentage of Collection System That Is a Combined Sewer System F or each unique collection system that provides flow to the permittee , t h is is the percentage of the collection systemthat is a combined sewer system. This includes unincorporated connector districts and satellite collecti on systems

. This 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 system. 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

Combined Sewer System Information on NPDES Permit Application or Notice of Intent

C omplete and I mplement

a L ong

- T erm CSO C ontrol P lan All Phase II and post

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

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

- 18698) . This data element identifies whether the permit requires the permit holder to complete and implement a long

- term CSO control plan and whether the permit holder is in compliance with this permit language. CWA 402(q)(1) 1

Nine Minimum CSO Controls Developed All combined sewer system NPDES permittees are required to implement the nine minimum controls outlined in EPA’s Combined Sewer Overflow (CSO) Control Policy ( 19 April 1994; 59 Federal Register 18688

- 18698) . This data element identifies whether the permit holder developed the nine minimum controls in compliance with permit language. CWA 402(q)(1) 1

Nine Minimum CSO Controls Implemented All combined sewer system NPDES permittees are required to implement the nine minimum controls outlined in EPA’s Combined Sewer Overflow (CSO) Control Policy ( 19 April 1994; 59 Federal Register 18688

- 18698) . This data element identifies whether the permit holder implemented the nine minimum controls in compliance with permit language. CWA 402(q)(1) 110/31/16 Page | 38 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Enforcement Mechanism for the LTCP All Phase II and post

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

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

- 18698) . This data element identifies the type of enforcement mechanism used to require the development and implementation of a LTCP. CWA 402(q)(1) 1

LTCP Submitted All Phase II and post

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

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

- 18698) . This data element identifies whether the permit holder submitted the LTCP for approval by the permitting authority. CWA 402(q)(1) 1

LTCP Approved All Phase II and post

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

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

- 18698) . This data element identifies whether the LTCP submitted by the permit holder was approved by the permitting authority. CWA 402(q)(1) 1

LTCP Approval Date All Phase II and post

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

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

- 18698) . This data element identifies the date when the permitting authority approved the LTCP. The date must be provided in YYYY

- MM

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

. CWA 402(q)(1) 110/31/16 Page | 39 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Actual Date Completed LTCP and CSO Controls All Phase II and post

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

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

- 18698) . This data element identifies the date by which the permit holder completed all required LTCP and CSO controls. The date must be provided in YYYY

- MM

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

. CWA 402(q)(1) 1

Enforceable Sched ule to Complete LTCP and CSO Controls All Phase II and post

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

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

- 18698) . This data element identifies whether the permit holder is on an enforceable schedule to complete all required LTCP and CSO controls. CWA 402(q)(1) 1

Other CSO Control Measures with Compliance Schedule This data element identifies whether the permit holder has other CSO control measures specified in a compliance schedule, beyond those identified in the nine minimum controls, LTCP, or a plan for sewer system separation. CWA 402(q)(1) 1

Approved Post

Construction Compliance Monitoring Program This data element indicates whether the permit holder is currently operating under an approved post

- construction compliance monitoring program. CWA 402(q)(1) 1

Pretreatment Information on NPDES Permit Application or Notice of Intent (this includes permit 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 Pretreatment Program Report (403.12(i) as needed.]

Pretreatment Program Required Indicator The code/description indicating if the permitted municipality is required to develop a pretreatment program. 122.28(b)(2)(ii), 122.44(j) 1

Pretreatment Program Approval or Modification Date The date the pretreatment program wa s approved or modified

. The date must be provided in YYYY

- MM

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

. 122.28(b)(2)(ii), 403.8(a) and (b), 403.11 110/31/16 Page | 40 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Pretreatment Program Modification Type The code/description of the type of 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 1

Approval Authority Name The name of the agency that is the designated approval authority. 122.28(b)(2)(ii), 403.8(a) and (b), 403.11 1

Industrial User Type Flag The unique code/description that identifies the type of industrial user discharging to a POTW [e.g., Significant Industrial User (SIU), Standard Categorical Industrial Users (CIU ), Non

- Significant Categorical In dustrial User (NSCIU), M iddle Tier Categorical Industrial User (MTCIU ) , and Dental Industrial User (DIU) ]. This data element is at the facility

- level and is required for all SIUs, CIUs, NSCIUs, MTCIUs , and DIUs

, [Note: These data will be added or updated through the Annual Pretreatment Program Report (403.12(i) as needed.] 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 This data element will identify for each Significant Industrial User (SIU) or Categorical Industrial User (CIU) that is discharging (including truck transportation) to a POTW whether the SIU is subject to local limits. [Note: These data will be added or updated through the Annual Pretreatment Program Report (403.12(i) as needed.] 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 More Stringent Than Categorical Standards This data element will identify for each Significant Industrial User (SIU) or Categorical Industrial User (CIU) that is discharging (including truck transportation) to a POTW whether the SIU is subject to local limits that are more stringent than the applicable categorical standards. T his data element will track the percentage of effluent limits that are based on local limits as they are more stringent than categorical standards

. [Note: These data will be added or updated through the Annual Pretreatment Program Report (403.12(i) as needed.] 122.21(j)(6 )

, 122.28(b)(2)(ii), 122.44(j ) , 403.12(i) 1 ,2 ,710/31/16 Page | 41 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Applicable Categorical Standards This data element will identify for each Significant Industrial User (SIU) or Categorical Industrial User (CIU) that is discharging (including truck transportation) to a POTW the applicable categorical standard ( s ) by its 40 CFR part number (e.g., Metal Finishing

– Part 433, Electrical and Electronic Components

– Part 469 )

. [Note: These data will be added or updated through the Annual Pretreatment Program Report (403.12(i) as needed.] 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 (including truck transportation) to a POTW the total 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 This data element will identify for each Significant Industrial User (SIU) or Categorical Industrial User (CIU) whether 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 requir e the Control Authority to develop and enforce local limits when the discharge from an IU causes or contributes to any problems (including upset, interference, bypass) at the receiving POTW’s effluent discharge or biosolids. 122.21(j)(6 )

, 122.28(b)(2)(ii), 122.44(j )(2)(ii), 403.5(c) 1 ,2

Receiving RCRA Waste This data element will identify 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 ,2

Receiving Remediation Waste This data element will identify whether the POTW has received RCRA or CERLCA waste from off

- site remedial activities within the last three years. 122.21(j)(7 )

, 122.44(j ) 1 ,2

Control Authority Name The name of the C ontrol A uthority for the Significant Industrial User (SIU) or Categorical Industrial User (CIU) discharging to a POTW. This will be the name of the State or EPA Region when they are the Control Authority. 122.28(b)(2)(ii), 122.44(j ) 1 ,2

Control Authorit y NPDES Permit Number The NPDES permit number of the C ontrol A uthority for the Significant Industrial User (SIU) or Categorical Industrial User (CIU) discharging to a POTW. 122.28(b)(2)(ii), 122.44(j) 1 ,2

Cooling Water Intake Information on NPDES Permit Application or Notice of Intent10/31/16 Page | 42 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

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 125 Subpart I, 2 = New Offshore Oil and G as Facility under 40 CFR 125 Subpart N, 3 = Existing Facility under 40 CFR 125 Subpart J, 4 = BPJ Facility under 40 CFR 125.80(c)

, 40 CFR 125.90(b), 40 CFR 125.130(c), or 401.14 )

. 122.21(r), 122.28(b)(2)(ii), 125 Subpart I, J, and N, 401.14 and CWA 316(b) 1,2

Number of Cooling Water Intake Structures (CWISs) Th is is th e number of cooling water intake structures (CWISs) at the facility. 122.21(r), 122.28(b)(2)(ii), 125.86, 125.9 5 , 125.136, 401.14 and CWA 316(b) 1,2

Design Intake Flow for Cooling Water Intake Structure (s) This is the cumulative design intake flow (DIF), in units of MGD, for each cooling water intake structure at the facility. DIF is the value assigned (during facility’s design) to the total volume of water withdrawn from a source water body over a specific time period. This value is based on maximum design flow capacities. 122.21(r), 122.28(b)(2)(ii )

, 125.80, 125.86, 125.90, 125.95, 125.131, 125.136, 401.14 and CWA 316(b) 1 ,2

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 capacities for each cooling water intake structure at the facility , as opposed to the DIF, which is based on maximum design flow capacities. For existing facility, Actu al Intake Flow (AIF) means the average volume of water withdrawn on an annual basis by the cooling water intake structures over the past three years. After [INSERT DATE 5 YEARS AFTER EFFECTIVE DATE OF THE SUBPART J FINAL RULE], AIF means the average volume of water withdrawn on an annual basis by the cooling water intake structures over the previous five years. 122.21(r), 122.28(b)(2)(ii), 125.86, 125.95, 125.136, 401.14 and CWA 316(b) 1 ,2

Location Type for Cooling Water Intake Structure The unique code/description that identifies the location and description for each cooling
water intake structure . These values are 1=shoreline intake description (flushed, recessed), 2= intake canal, 3=embayment, bank, or cove, 4=submerged offshore intake, 5=near

- shore submerged intake, 6=shoreline submerged intake , 7=other

. 122.21(r), 122.28(b)(2)(ii), 125.86, 125.9 5 , 125.136, 401.14 and CWA 316(b) 1 ,210/31/16 Page | 43 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Maximum Through

Screen Design Velocity This is the maximum velocity (in feet/second) of the water intake through the screen for each cooling water intake structure. 122.21(r), 122.28(b)(2), 125.86, 125.9 5 , 125.136, 401.14 and CWA 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. 122.21(r), 122.28(b)(2), 125.86, 125.9 5 , 125.136, 401.14 and CWA 316(b) 1 ,2

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

. 122.21(r), 122.28(b)(2)(ii), 125.86, 125. 95 , 125.136, 401.14 and CWA 316(b) 1,2

Cooling Water Intake Chosen Compliance Method The unique code/description to indicate the compliance method selected for each cooling water intake structure based on EPA’s CWA 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 125.94(c) compliance options were chosen and reported as part of 122.21(r)(6). 122.21(r)(6), 122.28(b)(2)(ii), 125.84, 125.85, 125.94, 125.134, 125.135, 401.14 and CWA 316(b) 1,2

Cooling Water Information Submitted A binary “yes/no” flag to indicate whether the facility has submitted the required information based on compliance method chosen. 125.86, 125.9 5 , 125.136, 401.14 and CWA 316(b) 1

Alternative Requirements Provision Request Date The date of any request under the Alternative Requirements provision as defined under 40 CFR 125.85

, 40 CFR 125.94(e)(2) or 40 CFR 125.135. The date must be provided in YY Y Y

- MM

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

. 122.28(b)(2) , 125.85, 125.94(e)(2), 125.135 and CWA 316(b) 1 ,210/31/16 Page | 44 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Existing Facilities

– Request for R educed I nformation in A pplication S ubmittal The date of any request for reduced information requirements regarding cooling water intake structure and waterbody information. The request must be submitted to the Director at least two years and six months prior to the expiration of its current NPDES permit. The owner or operator’s request must identify each elem ent that it determines has not substantially changed since the previous permit application and the basis for the determination. The Director has the discretion to accept or reject any part of the request. The date data must 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), 125.95(a) and (c) and CWA 316(b) 1,2

Source Water Baseline Biological Characterization Data : Species Name For new and existing facilities, a listing of each species (or relevant taxa) for all life stages in the vicinity of the cooling water intake structure. 122.21(r)(4), 122.28(b)(2), 125.86, 125.95, 125.136, 401.14 and CWA 316(b) 1,2

Source Water Baseline Biological Characterization Data: Species Number For new and existing facilities, the number of each species (or relevant taxa) in the vicinity of the cooling water intake structure. 122.21(r)(4), 122.28(b)(2), 125.86, 125.95, 125.136, 401.14 and CWA 316(b) 1,2

Source Water Baseline Biological Characterization Data: Threatened or Endangered Flag For new and existing facilities, a unique code/description that describes for each species (or relevant taxa) whether the species is threatened, endangered, or is an otherwise protected species that might be susceptible to imp ingement and entrainment at the facility’s cooling water intake structures. 122.21(r)(4), 122.28(b)(2), 125.86, 125.95, 125.136, 401.14 and CWA 316(b) 1,2

CWA Section 316(a) Thermal Variance Information on NPDES Permit Application or Notice of Intent Request for Thermal Variance The unique code/description that describe the thermal variance r equest submitted by the permittee (e.g., 1 = new request, 2 = renewal request ). 125 Subpart H and CWA 316(a) 110/31/16 Page | 45 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Thermal Variance Study Date This is the date when the permittee submitted studies/data to support its 316(a) demonstraton or support the continuation of the variance. The date must be provided in YYYY

- MM

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

. 122.28(b)(2)(ii), 125 Subpart H and CWA 316(a) 1

Public Notice of Section 316(a) Requests This is the unique code/description that describe s whether the permitting authority included the information required under 124.57(a) in the public notice regarding the CWA section 316(a) request. 124.57, 125 Subpart H and CWA 316(a) 1

Thermal Variance Granted This the unique code/description that describe s whether the permitting authority has granted the permittee a CWA 316(a) variance for the controlling NPDES permit. 122.28(b)(2)(ii), 125 Subpart H and CWA 316(a) 1

Thermal Variance Date This is the date when the permitting authority granted the permittee a CWA 316(a) variance for the controlling NPDES permit. The date must be provided in YYYY

- MM

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

. 122.28(b)(2)(ii), 125 Subpart H and CWA 316(a) 1

Thermal Variance Value This is the numeric value of the alternative effluent limitation(s) granted for each Permitted Feature. 122.28(b)(2)(ii), 125 Subpart H and CWA 316(a) 1

Non

- Variance T hermal Standards and Limitations This is the non

- variance numeric value of the thermal effluent limitation (s) based on effluent limitations guidelines or water quality standards for each Permitted Feature

. 122.28(b)(2)(ii) , 125 Subpart H and CWA 316(a) 1

Thermal Variance Unit This is the unit of measure (e.g., o F or o C of discharged effluent, o F or o C different between discharged effluent and receiving waterbody, o F or o C different between discharged effluent and inlet water source) associated with numeric value of the alternative effluent limitation granted (“Thermal Variance Value”) and thermal effluent limitation based on effluent guidelines or water quality standards (“ Non

- Waiver Thermal Standards and Limitations ”). 122.28(b)(2)(ii)125 Subpart H and CWA 316(a) 110/31/16 Page | 46 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Compliance Monitoring Activity

Compliance Monitoring ID The unique identifier for the compliance monitoring activity. 123.26, 123.41(a) and CWA 308 1

Permitted Feature Identifier The unique identifier for the permitted feature number (s) entered by the user for the inspected permitted feature(s)

. This data element will provide a linkage to location data from the NPDES permit application. This data elemen t can be left blank if the compliance monitoring activity does not involve a permitted feature. 123.26

, 123.41(a) and CWA 308 1

Compliance Monitoring Activity Actual End Date The actual date on which the c ompliance m onitoring a ctivity ended. The date mus t be provided in YYYY

- MM

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

. 123.26, 123.41(a) and CWA 308 1

Compliance Monitoring Activity Planned End Date The planned date for the c ompliance m onitoring a ctivity to end. The date must be provided in YYYY

- MM

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

. 123.26, 123.41(a) and CWA 308 1

Compliance Monitoring State The US Postal Service abbreviation that represents that state or state equivalent for the U.S. i n which the c ompliance m onitoring a ctivity occurred. 123.26, 123.41(a) and CWA 308 1

Compliance Activity The unique code/description that identifies a type of compliance event. For example, there are codes for inspection, investigation, information request, and offsite records review. 123.26, 123.41(a) and CWA 308 1

Compliance Monitoring Type The code/description indicating the type of compliance monitoring activity taken by a regulatory Agency. Each compliance monitoring activity has a variety of different types, such as audit, sampling, case development, follow

- up, reconnaissance without sampling,
etc. 123.26, 123.41(a) and CWA 308 110/31/16 Page | 47 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Bio m onitoring Inspection Method The unique code that identifies the type of biomonitoring inspection method (e.g., discrete acute

, discrete chronic

, discrete method

, flow

- through method

, flow

- through
acute , flow

- through chronic )

. This data element supplements the Compliance Monitoring Category and Compliance Monitoring Type Inspection Type recorded for all inspections. 123.26, 123.41(a) and CWA 308 1

Compliance Monitoring Category The unique code/description identifying the compliance monitoring or inspection category code/description

. 123.26, 123.41(a) and CWA 308 1

Compliance Monitoring Action Reason The unique code that identifies the purpose of an activity. 123.26, 123.41(a) and CWA 308 1

Was this a State, Federal or Joint (State/Federal) Inspection? The flag indicating if the inspection is a joint inspection by federal

, state , tribal, or territorial personnel

. 123.26, 123.41(a) and CWA 308 1

Compliance Monitoring Agency Type An indicator w hether the compliance monitoring activity was designated as an EPA or

s tate activity/i nspection

. 123.26, 123.41(a) and CWA 308 1

Programs Evaluated The unique identifier for the programs evaluated in or pertinent to the activity. 123.26, 123.41(a) and CWA 308 1

Compliance Monitoring Activity (Biosolids Inspections)

Def iciencies Identified Through the Biosolids Inspection This data element will identify each deficienc y identified in that facility’s biosolids implementation for each biosolids inspection. These deficiencies will allow users to distinguish between noncompliance and significant noncompliance (SNC). 1 23.26, 123.41(a), 123.45, and CWA 308 110/31/16 Page | 48 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Compliance Monitoring Activity (AFO/CAFO Inspections)

Animal Type 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 more, 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 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 308 1

Animal Numbers in Open Confinement (Inspection) 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 308 1

MLPW Containment and Storage Type Code (Inspection) The type(s) 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 308 1

MLPW Containment and Storage Type Within Design Capacity (Inspection) The 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 ML PW at the time of inspection.. 122.23 , 123.26, 123.41(a) and CWA 308 1

AFO/CAFO Unauthorized Discharges (Inspection) A binary “yes/no” flag to indicate whether t here evidence of unauthorized discharge(s) of pollutants from the facility’s production area and/or land application area(s)

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

Permit Requirements Implement ion (Inspection) The unique code/description that identifies whether or not the facility is properly implementing its 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 308 110/31/16 Page | 49 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Compliance Monitoring Activity (Sewer Overflows Inspections and Audits)

Sewer Overflow Longitude This data element is required for sewer overflow inspections without a permitted feature identifier. The measure of the angular distance on a meridian east or west of the prime meridian for the sewer overflow . Entered in either d ecimal d egrees or in d egree s m inutes

s econds; stored in decimal degrees (e.g.,

- 77.029289 )

. This data element will enable users to compare this inspection to a sewer overflow incident report. These data are provided in accordance with Environmental Data Standards Council , L atitude / L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. 123.26 , 123.41(a) 1

Sewer Overflow Latitude This data element is required for sewer overflow inspections without a permitted feature identifier. The measure of the angular distance on a meridian north or south of the equator for the sewer overflow . Entered in either d ecimal d egrees or in d egrees m inutes Seconds; stored in decimal degrees (e.g., 38.893829 )

. This data element will enable users to compare this inspection to a sewer overflow incident report. These data are provided in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 20 06

. 123.26 , 123.41(a) 1

Type of Sewer Overflow A code identifying the type of sewer overflow (including CSO, SSO, Bypass , Other Discharge from the Collection System or Treatment Works ). 123.26 , 123.41(a) 1

Sewer Overflow Cause The likely cause of the overflow event (e.g., broken pipe, fats/oil/grease, mechanical failure, pump station electrical failure, etc.). 123.26 , 123.41(a) 1

Duration of Sewer O verflow event (hours) Duration of the sewer overflow event (in hours). I f the discharge has not been corrected, the b est professional judgment from the compliance inspector of the time the sewer overflow is expected to continue

. 123.26 , 123.41(a) 110/31/16 Page | 50 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Sewer Overflow Discharge Volume (gallons) Best professional judgment from the compliance inspector on the estimated number of gallons of sewer overflow

. 123.26 , 123.41(a) 1

Failure to Submit Sewer Overflow Incident Report This data element would indicate whether the POTW has failed to provide 24

- hr. notification of sewer overflows or failed to submit sewer overflow incident follow

- up reports within the required five days. 122.41(l)(6) and (7)

, 123.26, 123.41(a) 1

Compliance Monitoring Activity (Pretreatment Inspections and Audits)

Def ic iencies Identified Through the Pretreatment Inspections or Audits This data element will identify each d eficiency or deficiencies identified by EPA or the authorized NPDES program for each pretreatment inspection and audit. These deficiencies will allow users to distinguish between noncompliance and significant noncompliance (SNC)

. These deficiencies 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 ai lure to issue/reissue control mechanisms 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 308 1

Compliance Monitoring Activity ( Discharge Monitoring Report , and Pretreatment Periodic Compliance Reports for Significant Industrial Users (SIUs) and Categorical Industrial Users (CIUs) when EPA or the State is the Control Authority )

Permitted Feature The identifier assigned for each location at which conditions are being applied. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 1,2,3,6,810/31/16 Page | 51 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Limit Set The unique identifier tying the DMR form to its Limit Set record. 122.41(l)(4)(i ), 123.26, 123.41(a), 403.12(e), 403.12(h) 1,2,3,6,8

Parameter Code The unique code/description identifying the parameter reported on the DMR. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 1,2,3,6,8

Monitoring Location The code/description of the monitoring location at which the sampling occurred for a DMR parameter. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 1,2,3,6,8

Monitoring Period End Date The date that the monitoring period for the values covered by this DMR form ends. The date must be provided in YYYY

- MM

- DD format where YY YY 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,2,3,6,8

NODI The unique code/description that indicates the reason that “No Discha rge” or “No Data” was reported in place of the DMR value. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 1,2,3,6,8

Value The DMR value number reported on the DMR form. 122.41(l)(4)(i) , 123.26, 123.41(a), 403.12(e), 403.12(h) 1,2,3,6,8

Concentration Units/ Quantity Units The code/description representing the unit (s) of measure applicable to quantity or concentration limits and measurements as entered by the user on the DMR form. 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 1,2,3,6,8

Value Received Date The date the DMR value was received by the regulatory authority. The date must be provided in YYYY

- MM

- DD format where YY YY 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) 110/31/16 Page | 52 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Value Type The unique code/description identifying a DMR value type (i.e. Quantity 1, Quantity 2, Concentration 1, Concentration 2, Concentration 3). 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 1,2,3,6,8

Qualifier The unique code identifying the limit value operator (e.g., <, =, >). 122.41(l)(4)(i), 123.26, 123.41(a), 403.12(e), 403.12(h) 1,2,3,6,8

Compliance Monitoring Activity (Periodic Program Reports )

Date Report Received T he date the report was received. The date must be provided in YYYY

- MM

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

. These are data elements that are common to reports required in Parts 122, 123, 403, and 503 1

Start Date of Reporting Period T he start date of the reporting period. The date must be provided in YYYY

- MM

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

. For the Sewer Overflow Event Report this is the start or best estimate of the start date for each Sewer Overfl ow Discharge Number

. These are data elements that are common to reports required in Parts 122, 123, 403, and 503 4 through 10

End Date of Reporting Period T he end date of the reporting period. The date must be provided in YYYY

- MM

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

. For the Sewer Overflow Event Report this is the end or best estimate of the end date for each Sewer Overflow Discharge Number These are data elements that are common to reports required in Parts 122, 123, 403, and 503 4 through 10

NPDES Data Group Number (Program Report) This data element identifies for each program report submission the types 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 is a system generated data element. These are data elements that are common to reports required in Parts 122, 123, 403, and 503 4 through 10

Compliance Monitoring Activity (Data Elements Specific to Biosolids Annual Program Reports )10/31/16 Page | 53 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Biosolids or Sewage Sludge Treatment Processes This data element identifies the biosolids or sewage sludge treatment process or processes at the facility. For example, this may indicate whether primary, secondary, and tertiary treatment is being used, and the type of the biosolids or sewage sludge
treatment proces s or processes used, including drying processes. 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge Analytical Methods The unique code (s) /description (s) that identify the analytic methods used by the facility to analyze for enteric viruses, fecal coliforms, helminth ova

, Salmonella sp ., and other regulated parameters. 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 503.23 503.8(b), 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge M anage ment P ractice This data element will identify the type of biosolids or sewage sludge management practice or practices (e.g., land application, surface disposal, incineration) for each different form of biosolids and sewage sludge generated by the facility. 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 Sewag e Sludge Form This data element describes 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 sewag e sludge management practice or practices used by the facility

. 503.18, 503.28, 503.48 4

Annual W hole Biosolids or Sewage S ludge A pplication R ate This data element identifies the annual whole biosolids or sewage sludge application rate for biosolids or sewage sludge sold or given away in bags or containers (see 40 CFR 503.13 ). The facility will separately report the application rate for each biosolids or sewage sludg e management practice used by the facility and by each biosolids or sewage sludge form. 503.18 410/31/16 Page | 54 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Biosolids or Sewage Sludge Pathogen Class This data element will identify the pathogen class or classes (e.g., Class A, Class B) for biosolids or sewage sl udge 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 biosolids or sewage sludge form. 503.18, 503.28, 503.48

Biosolids or Sewage Sludge Vector Attraction Reduction Options This data element will identify the land application and surface disposal vector attraction reduction options used by the facility. The facility will separately report the vector attraction reduction options for e ach 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 Land Application Option This data element will identify the land application option or options used by the facility (e.g., EQ, PC, CPLR, APLR). The facility will separately report the land application option 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 and each vector attraction reduction option

. 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge Volume Amount This is the amount (in dry metric tons) of biosolids or sewage sludge generated by the facility

. 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 we ll as by each biosolids or sewage sludge pathogen class , by each vector attraction reduction option , and by each land application option.. 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge Monitored Parameter This is the biosolids or sewage sludge parameter that is monitored 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 sl udge 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 503.23

. 503.18, 503.28, 503.48 410/31/16 Page | 55 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Biosolids or Sewage Sludge Monitored Parameter Concentration This is the concentration value of the Biosolids or Sewage Sludge Monitored Parameter. 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge s Monitored Parameter Units This is the measurement unit (e.g., mg/kg) associated with the Biosolids or Sewage Sludge Monitored Parameter Concentration

. 503.18, 503.28, 503.48 4

Biosolids or Sewage Sludge Measured Cumulative Pollutant Loading Amount This is the measured cumulative amount of a pollutant ( in kg per hectare) that has been applied to each off

- site area of land as specified in the regulations at 40 CFR 503 during the entire life of the application site

. The list of pollutants to be measured is at 40 CFR 503.13, Table 2. When the measured cumulative pollutant loading amount exceeds the Cumulative Pollutant Lo ading Rate (CPLR) limit for any pollutant, as identified at 40 CFR 503.13, Table 2, no additional bulk biosolids subject to CPLR limits may be applied to the site. 503.13 4

Biosolids or Sewage Sludge Measured Annual Pollutant Loading Amount This is the me asured amount of a pollutant ( in kg per hectare ) that has been applied to each off

- site area of land as specified in the regulations at 40 CFR 503 in the preceding 365

- day period. This value is compared against the Annual Pollutant Loading Rate (see 40 CF R 503.13, Table 4) to determine compliance for each Biosolids or Sewage Sludge Receiving Site for each preceding 365

- day period. 503.13 4

Compliance Monitoring Activity (Data Elements Specific to CAFO Annual Program Reports )

CAFO Animal Types (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) 510/31/16 Page | 56 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

CAFO Animal Maximum Number (Program Report) The 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 Confinement (Program Report ) The 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 material generated by the facility (i.e., manure, litter, and process wastewater or ‘MLPW’) in the previous 12 month s

. 122.42(e)(4)(ii) 5

CAFO MLPW Amounts (Program Report) The total amount of CAFO material generated by the facility (i.e., manure, litter , and process wastewater) 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 total amount of CAFO material generated by the facility (i.e., manure, litter , and process wastewater) in the previous 1 2 month s

. 122.42(e)(4)(ii) 5

CAFO MLPW Transferred (Program Report) The total amount of CAFO material generated by the facility (i.e., manure, litter , and process wastewater) 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 N umber of A cres for L and A pplication C overed by the N utrient 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) 510/31/16 Page | 57 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Total N umber 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 Type (Program Report) The unique code/description that identifies for each d ischarge 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. 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 months

. The date must be provided in YYYY

- MM

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

. 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

. . 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. 122.42(e)(4)(vi) 5

Whether NMP A pproved

or D eveloped by C ertified P lanner (Program Report) The unique code/description 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 material used or generated by the facility (i.e., manure, litter , and process wastewater) in the previous 12 months. 122.42(e)(4)( vi ii) 510/31/16 Page | 58 Table 2 : Required NPDES Data

Data Name 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 material used or generated by the facility (i.e., manure, litter , and process wastewater) 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 material used or generated by the facility (i.e., manure, litter , and process wastewater) in the previous 1 2 month s

. 122.42(e)(4)( v i i i) 5

CAFO MLPW Nitrogen or Phosphorus Form (Program Report) The form (e.g., t otal nitrogen , a mmonium

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

. 122.42(e)(4)( v i i i) 5

Field Identification Number (Program Report) A unique field number to which CAFO MLPW was 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) 510/31/16 Page | 59 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) 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) 5

CAFO MLPW Land Application For Each Field (Program Report) The unique code/description that identifies for each field the type of CAFO material (i.e

., manure, litter, and process wastewater or ‘MLPW’) 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 material (i.e., manure, litter , and process wastewater) for each field in the previous 12 months and used for land application. The maximum amount of CAFO material is calculated in accordance with procedures in the Linear Approach [40 CFR 122.42(e)(5)(i)(B)] or the Narrative Rate Approach [40 CFR 122.42(e)(5)(ii)(D)]. 122.42(e)(4)( vi ii) 5

CAFO MLPW Land Application Actual Amount For Each Field (Program Report) The actual a mount of CAFO material (i.e., manure, litter , and process wastewater) for each field in the pr evious 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 material (i.e., 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

., amount 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)(vii i) 510/31/16 Page | 60 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) 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

., amount of phosphor us 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)( v i 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)( v i i i) 5

Soil Tes t 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 descri bed in 40 CFR 122.42(e)(5)(ii). 122.42(e)(4)( v i i i) 5

Nitrogen Amount of A ny 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 A ny S upplemental Fertilizer A pplied (Program Report) For each field used for land appl ication, 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 122.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 (Data Elements Specific to Municipal Separate Storm Sewer System Program Reports ) (Note: The MS4 permit may require one report for each unique governmental entity or one report per permit).10/31/16 Page | 61 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) MS4 Reliance on Other Go vernment E ntities : Status Flag This is a code indicating that the permittee relies on another unique governmental entity to satisfy any of the permit requirements. 122.26(d)(2)(vii)

, 122.34(g)(v) 6

MS4 Relian ce on Other Government Entities: Permit Component Flag This is a code that identifies for each MS4 permit component the responsible government entity by using the unique number for the responsible municipality. (The unique number would allow greater geographic resolution for the MS4 components being tracked a nd would ensure consistency from year to year. The number would essentially identify who is taking responsibility for complying with each MS4 permit component

. 122.34(g)(i) and (v), 122.35(a) and 122.42(c 6

MS4 Permit Component s Descriptions This code/description will identify for each unique municipality all of the permitted components 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 impl ement in its NOI or permit application. The groupings of these MS4 components will include public education and outreach on stormwater impacts; public involvement/participation; illicit discharge detection and elimination; construction site
stormwater runo ff; post

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

Changes to MS4 Permit Components This code/description will describe for ea ch unique municipality any changes made to MS4 permit components (e.g., BMPs) during the reporting period. 122.34(g)(3)(iv) and 122.42(c) 6

Identified Measurable Goal for Each MS4 P ermit Component Identified measurable goal for each MS4 permit component for each unique municipality for each MS4 permit component

. This data element only applies to Phase II MS4s. 122.34(g)(3) 6

Status and Assessment of Compliance with MS4 Permit Components Status and assessment of the permittee’s compliance with its MS4 permit for each unique municipality. 122.34(g)(3) and 122.42(c) 610/31/16 Page | 62 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Changes to MS4 Measurable Goals This code/description will identify any changes the permittee made to the measurable goals for each unique municipality that were made since the last annual report was submitted. 122.34(g)(3)(iv) and 122.42(c) 6

Progress Toward Achieving Identified MS4 Measurable Goals This is an indication of the progress made to date on achieving the identified measurable goals for each unique municipality for each MS4 perm it component

. 122.34(g)(3) (i) 6

Summary of MS4 Data and Monitoring Results Provide text summary of information collected and analyzed, including monitoring data, if any, during the reporting period for each unique municipality for each MS4 permit component

. 122.26(d)(1)(iv) and (d)(2)(v), 122.34(g)(3) (ii), and 122.42(c) 6

Summary of Planned MS4 Activities Provide a text summary of the stormwater activities to be undertaken during the next reporting cycle for each unique municipality for each MS4 permit component

. 122.34(g)(3)(iii) and 122.42(c) 6

MS4 Enforcement Action Type For each unique municipality covered under the MS4 permit, identify the types of enforcement actions taken during the past reporting period (e.g., notice of violations , s top

w ork 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

. 122.34(g)(3) and 122.42(c) 6

MS4 Enforcement Action Number For each unique municipality covered under the MS4 permit and for each MS4 Enforcement Action Type , identify the number 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. 122.34(g)(3) and 122.42(c) 610/31/16 Page | 63 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

MS4 Municipa lity Enforcement Agency For each unique municipality that has the authority to conduct enforcement actions covered under the MS4 permit and for each MS4 Enforcement Action Type, identify the corresponding MS4 Municipal Enforcement Agency by its unique mun icipality number (“ Unique Number for Each Municipality Covered Under MS4 Permit ”). 122.34(g)(3) and 122.42(c) 6

Compliance Monitoring Activity (Data Elements Specific to Pretreatment Program Annual Reports , SIU Periodic Compliance Reports in Municipalities without an Approved Pretreatment Program )

SNC Published A unique code/description that identifies whether public notice was made for each Significant Industrial User (SIU) and Non

- Significant Catego rical Industrial Users (NSCIU) in SNC

. 403.12(i)(2), 403.8(f)(2)(viii) 7

SNC with Pretreatment Enforceable Compliance Schedule Flag A unique code/description that identifies whether each Industrial User (SIU) and Non

Significant Catego rical Industrial User (NSCIU) in SNC has one or more enforceable

c ompliance pretreatment schedule (s). 403.12(i)(2), 403.8(f)(2)(viii) 7

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

- MM

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

. 403.5(c), 403.12(i)(4), 403.8(f)(4) 7

Local Limits Evaluat ion Date This is the most recent date on which the Control Authority evaluated the 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. 122.44(j)(2)(ii), 403.5(c), 403.12(i)(4), 403.8(f)(4) 7

Local Limits Pollutants This is the list of the pollutants for which the Control Authority derived 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

. 403.5(c), 403.12(i)(4) 7

POTW Discharge Contamination Indicator (Program Report) A unique code/description that identifies whether there have been any problems ( e.g., pass

- through or interference) with the receiving POTW’s effluent discharge within the reporting period

. 403.8(f)

, 403.12(i) 710/31/16 Page | 64 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) POTW Biosolids Contamination Indicator (Program Report) A unique code/description that identifies whether there have been any problems ( e.g., pass

- through or interference) with the receiving POTW’s biosolids within the reporting period

. 403. 8(f)

, 403.12(i) 7

Industrial User Control Mechanism Flag A unique code/description that identifies whether the Industrial User has a current Control Mechanism. 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 is effective . The date must be provided in Y YYY

- 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 YY YY is the year, MM is the month, and DD is the day

. 403.8(f)

, 403.12(i) 7

SNC with Pretreatment Standards (Program Report) This data element will identify for each Significant Industrial User (SIU) and Non

Significant Catego rical Industrial User (NSCIU) that is discharging (including truck transportation) to this POTW whether the IU was in Significant Non

- Compliance (S NC) with pretreatment requirements in the reporting period

. 403.8(f)

, 403.12(i) 7

SNC with Pretreatment Standards Pollutants (Program Report) This data element will identify for each Significant Industrial User (SIU) and Non

Significant Categorical Indust rial User (NSCIU) that is discharging (including truck transportation) the pollutants that related to the IU ’s Significant Non

- Compliance (SNC)
status with pretreatment requirements in the reporting period

. 403.8(f), 403.12(i) 7

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) that is discharging (including truck transportation) to this POTW whether th e IU was in Significant Non

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

- monitoring reports, notice of change in Industrial User discharge, hazardous waste notification and BMP certification) in the reporting period

. 403.8(f)

, 403.12(i) 710/31/16 Page | 65 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

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) that is discharging (including truck transportation) to this POTW whether the IU was in Significant Non

- Compliance (SNC) with any other control mechanism requirements in the reporting period

. 403.8(f)

, 403.12(i) 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) that is discharging (including truck transportation) to this POTW the month or months the IU is in SNC in the r eporting period

. The se data must be provided in YYYY

- MM format where YYYY is the year and MM is the month. 403.8(f)

, 403.12(i) 7

Number of Industrial User Inspections by Control Authority This data element will identify for each Significant Industrial User (SIU) , Dental Industrial User (DIU), and Non

- Significant Catego rical Industrial User (NSCIU) the number of inspections conducted by the Control Authority in the reporting period

. 403.8(f)

, 403.12(i) 7

Number of Industrial User Sampling Events by Control Authority This data element will identify for each Significant Industrial User (SIU) , Dental Industrial User (DIU), and Non

- Significant Catego rical Industrial User (NSCIU) the number of complete sampling events conducted by the Control Authority in 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) , Dental Industrial User (DIU), and Non

- Significant Categorical Industrial User (NSCIU) the number of required self

- monitoring sampling events in the reporting period that must be reported to the Control Authority

. 403.8(f), 403.12(i) 7

Actual Number of Industrial User Self

Monitoring Events This data element will identify for each Significant Industrial User (SIU) , Dental Industrial User (DIU), and Non

- Significant Categorical Industrial User (NSCIU) the actual number of self

- monitoring sampling events i n the reporting period submitted to the Control Authority. 403.8(f), 403.12(i) 710/31/16 Page | 66 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Types of Industrial User Enforcement Action This data element will identify for each Significant Industrial User (SIU) , Dental Industrial User (DIU), and Non

- Significant Categoric al Industrial User (NSCIU) the type(s) of enforcement action(s) (e.g., formal notices of violation or equivalent actions, administrative orders, civil suits, criminal suits) issued by the Control Authority in the reporting per iod

. 403.8(f), 403.12(i) 7

Number of Industrial User Enforcement Actions This data element will identify for each Significant Industrial User (SIU) , Dental Industrial User, and Non

- Significant Categorical Industrial User (NSCIU) and for each type of enfor cement action the total number of enforcement actions issued by the Control Authority in 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) , Dental Industrial User (DIU), and Non

- Significant Catego rical Industrial User (NSCIU) in 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 Collected For civil judicial Enforcement Actions, the dollar amount of the penalty collected from each Significant Industrial User (SIU) , Dental Industrial User (DIU), and Non

- Significant Catego rical Industrial User (NSCIU) in the reporting period . For Administrativ e 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) This data element will identify for each Significant Ind ustrial User (SIU) , Dental Industrial User (DIU), and Non

- Significant Catego rical Industrial User (NSCIU) whether the Industrial User caused or contributed to any problems with the receiving POTW’s effluent discharge in the previous reporting period. EPA r egulations require the Control Authority to develop and enforce local limits when the discharge from an IU causes or contributes to any problems ( e.g., pass

- through or interference) at the receiving POTW. 403.5(c), 403.8(f)

, 403.12(i) 710/31/16 Page | 67 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Industrial User Biosolids Contamination Indicator (Program Report) This data element will identify for each Significant Industrial User (SIU) , Dental Industrial User (DIU), and Non

- Significant Catego rical Industrial User (NSCIU) whether the Industrial User caused or contr ibuted to any problems with the receiving POTW’s biosolids in the previous reporting period. 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., pass

- t hrough or interference) at the receiving POTW. 403.5(c), 403.8(f)

, 403.12(i) 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) that is discharging (including truck transportation) to this POTW the total wastewater flow rate (in gallons per day) in the previous reporting period

. 403.8(f)

, 403.12(i) 7 ,8

Middle

- Tier Significant Industrial User Reduced Reporting Flag This code/description will identify for each Middle

- Tier Significant Industrial User ( MT SIU) whether the Control Authority has granted reduced reporting requirements in accordance with 40 CFR 403.12(e)(3). 403.12(e)(3), 403.12(i)(2) 7

Non

- Significant Cate go rical Industrial User (NSCIU) and Dental Industrial User (DIU) Certification Submitted to Control Authority This code/description will identify for each Non

- Significant Catego rical Industrial User (NSCIU) and Dental Industrial User (DIU) whether it has given its required annual compliance certification with in the reporting period

. 403.12(i)(2), 403.12(q) 7 ,8

Control Authority Resources A unique code/description that identifies whether the pretreatment program has sufficient resources (e.g., budget , full

- time equivalent labor) to fully implement its pretreatment program

. 403.12(i)(4) 7

Compliance Monitoring Activity (Data Elements Specific to Sewer Overflow Event Reports)10/31/16 Page | 68 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Sewer Overflow Discharge Number This data element will allow the reporting of multiple sewer overflows on one report. Each individualized sewer overflow will be given a unique number (e.g., 1, 2, 3, and so on) for each Sewer Overflow Event Report

. This field will be system generat ed to accommodate one or more individual sewer overflows. 122.41(l)(6) and (7) 9

Sewer Overflow Permitted Feature This data element will identify the permitted feature(s), if any, for each Sewer Overflow Discharge Number . If the sewer overflow is not associated with a permitted feature than this data element can be left blank. 122.41(l)(6) and (7) 9

Sewer Overflow Longitude (Sewer Overflow Event Report) This data element is required for each Sewer Overflow Discharge Number that do es not have a permitted feature identifier, which is reported on the NPDES permit application or Notice of Intent for NPDES permit coverage. The measure of the angular distance on a meridian east or west of the prime meridian for the sewer overflow . Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees (e.g.,

- 77.029289 )

. These data are provided in accordance with Environmental Data Standards Council , L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, January 6, 2006

. If the sewer overflow is associated with a permitted feature than this data element can be left blank. 122.41(l)(6) and (7) 9

Sewer Overflow Latitude (Sewer Overflow Event Report) This data element is required for each Sewer Overflow Discharge Numbe r that do es not have a permitted feature identifier, which is reported on the NPDES permit application or Notice of Intent for NPDES permit coverage. The measure of the angular distance on a meridian north or south of the equator for the sewer overflow . E ntered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees (e.g.,

- 77.029289 )

. These data are provided in accordance with Environmental Data Standards Council

, L atitude/ L ongitude D ata S tandard

, Standard No.: EX000017.2

, Janua ry 6, 2006

. If the sewer overflow is associated with a permitted feature than this data element can be left blank. 122.41(l)(6) and (7) 910/31/16 Page | 69 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Type of Sewer Overflow (Sewer Overflow Event Report) A code identifying the type of sewer overflow (including CSO, SSO, or Bypass from the Collection System or Treatment Works ) for each Sewer Overflow Discharge Number

. 122.41(l)(6) and (7) 9

Sewer Overflow Cause The likely cause of the overflow event (e.g., broken pipe, fats/oil/grease, mechanical failure

, pump station electrical failure, inadequate sewer system capacity, etc.) for each Sewer Overflow Discharge Number

. 122.41(l)(6) and (7) 9

Duration of Sewer O verflow event (hours) (Sewer Overflow Event Report) Duration of the sewer overflow event (in hours) for each Sewer Overflow Discharge Number . I f the discharge has not been corrected, the b est professional judgment from the permitted facility of the time the sewer overflow is expected to continue

. 122.41(l)(6) and (7) 9

Sewer Overflow Discharge Volume (gallons) (Sewer Overflow Event Report) Best professional judgment from the permitted facility on the estimated number of gallons of sewer overflow for each Sewer Overflow Discharge Number

. 122.41(l) (6) and (7) 9

Receiving Waterbody Name for Permitted Feature (Sewer Overflow Event Report) This data element is required for sewer overflow inspections without a permitted feature identifier. Best professional judgment from the permitted facility of the name of the waterbody that is or will likely receive the discharge from each Sewer Overflow Discharge Number

. 122.41(l)(6) and (7) 9

Dry or W et W eather Occurrence for Sewer Overflow B est professional judgment from the permitted facility on whether the sewer overflow

, by Sewer Overflow Discharge Number

, occurred during dry or wet weather. 122.41(l)(6) and (7) 9

Corrective Actions Taken or Planned for Sewer Overflows (Sewer Overflow Event Report) The unique code/description that describes the steps taken or planned to reduce, eliminate, and prevent reoccurrence of future sewer overflows for each Sewer Overflow Discharge Number

. 122.41(l)(6) and (7) 910/31/16 Page | 70 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Type of Potential Impact of Sewer Overflow Event (Sewer Overflow Event Report) Th is describes the type of potential human health or environmental impact(s) (e.g., beach closure) for each Sewer Overflow Discharge Number

. Under 40 CFR 122.41(l)( 6), “the permittee shall report any noncompliance which may endanger health or the environment.” This data element would provide information regarding the nature of such potential endangerment. 122.41(l)(6) and (7) 9

Compliance Monitoring Activity (Data Elements Specific to CWA Section 316(b) A nnual R eport s)
Biological Monitoring

– Request for R educe Monitoring A pproval D ate The date the director approved the request for reduced biological monitoring as outlined in 40 CFR 125.87(a ), 125.96, or 125.137

. 125.87, 125.96, 125.137, 401.14 and CWA 316(b) 1

Velocity Monitoring

- Compliance with the Velocity Requirements The unique code/description indicating whether or not the facility is in compliance with the velocity requirement for each permitted cooling water intake structure. 1 = new facility is in compliance with the Maximum Through

- Screen Design Intake Velocity of 0.5 fps as require under 125.84(b)(2) or (c)(1) or 125.134(b)(2), 2 = new facility is reducing the le vel of adverse environmental impact to a comparable level as require under 125.84(d) or 125.134(c)(1), 3 = new facility is in compliance with alternative requirements as outlined in 125.85 or 125.135, 4 = existing facility if velocity monitoring is require d, is in compliance with the maximum design intake velocity of 0.5 fps, the maximum actual through screen velocity of 0.5 fps, or an alternative requirements established by the Director. A value of zero means the facility is not subject to 125 Subpart I, J , or N and is in compliance with the limits based on BPJ. 125.87, 125.96, 125.137, 401.14 and CWA 316(b) 10

CWA 316(b) Biological Monitoring

- Species Name (Program Report) For new and existing facilities, a listing of each species (or relevant taxa) for all life stages in the vicinity of the cooling water intake structure. 125.87, 125.96, 125.98 125.137, 401.14 and CWA 316(b) 1010/31/16 Page | 71 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

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

- Species Number (Program Report) For new and existing facilities, the number of each species (or relevant taxa) in the vicinity of the cooling water intake structure. 125.87, 125.96, 125.98 125.137, 401.14 and CWA 316(b) 10

CWA 316(b) Biological Monitoring

- Threatened or Endangered Flag (Program Report) For new and existing facilities, a unique code/description that describes for each species (or relevant taxa) whether the species is threatened, endangered, or is an otherwise protected species that might be susceptible to impingement and entrainment at the facility’s cooling water intake structur es. 125.87, 125.96, 125.98 125.137, 401.14 and CWA 316(b) 10

CWA 316(b) Biological Monitoring

- Species Impinged and Entrained (Program Report) For new and existing facilities, the number of each species (or relevant taxa) impinged and entrained per year in the vicinity of the cooling water intake structure. 125.87, 125.96, 125.98 125.137, 401.14 and CWA 316(b) 10

Data Elements Common to Violations, Enforcement Actions, and Final Orders

Violation Code The code/description that uniquely identif ies each type of v iolation 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 automatically generated based upon DMRs, schedules,
etc. CWA Section 309, 123.45 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 YY YY is the year, MM is the month, and DD is the day .This data element may be system generated. CWA Section 309, 123.45 1

Violation s10/31/16 Page | 72 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Agency Identifying the Single Event Violation (SEV) The code/description identifying the agency that identified the s ingle e vent v iolation (SEV). 123.26, 123.41(a)

, 123.45 1

Single Event Violation Date The date of a s ingle e vent v iolation (SEV) that occurred on one 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.26, 123.41(a), 123.45 1

Single Event Violation Start Date If the single event violation (SEV) occurred over multiple days, the date the occurrence began. The date must be provided in YYYY

- MM

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

. 123.26, 123.41(a), 123.45 1

Single Event Violation End Date If the single event violation (SEV) occurred over multiple days, the date the occurrence ended. This field will be left blank to denote an ongoing or unresolved SEV. The date must be provided in YYYY

- MM

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

. 123.26, 123.41(a), 123.45 1

RNC Detection Code The type of reportable noncompliance ( RNC ) detected. It can be entered automatically by the system or it c an be entered manually. 123.26, 123.41(a), 123.45 1

RNC Detection Date The date that reportable noncompliance ( RNC ) was detected. It can be entered manually or automatically. This date may vary according to the type of violation detected. The date must be provided in YYYY

- MM

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

. 123.26, 123.41(a), 123.45 1

RNC Resolution Code The reportable noncompliance ( RNC ) status (i.e., noncompliant, resolved pending, waiting resolution, resolved) of the violation. It can be entered manually or automatically by the system. 123.26, 123.41(a), 123.45 1

RNC Resolution Date The date reportable noncompliance ( RNC ) was marked to its current resolution status. It can be entered manually or automatically. The date must be provided in YYYY

- MM

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

. 123.26, 123.41(a), 123.45 110/31/16 Page | 73 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Enforcement Action s

Enforcement Action Identifier The number of the e nforcement a ction; for a judicial action, the number as referred to by the Court where the action was filed. For F ederal enforcement actions, this field will be have three components, each separated by a hyphen (e.g., HQ

- 2003

- 1234). 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. 123.27, 123.41(a) , and CWA Section 309 1

Enforcement Action Name The name associated with this enforcement action. 123.27, 123.41(a), and CWA Section 309 1

Enforcement Action Type The code/description that uniquely identifies the type of formal or informal enforcement action. This code identifie s, for example, whether the enforcement action is a civil judicial referral, a notice of violation, an administrative penalty order, administrative order, etc. 123.27, 123.41(a), and CWA Section 309 1

Programs Violated The code/description that uniquely identifies each program (e.g., pretreatment) associated with the enforcement activity. 123.27, 123.41(a), and CWA Section 309 1

Milestones/ Sub

- activities This data element describes the milestones and sub

- activities. Some of these milestones are system generated. 123.27, 123.41(a), and CWA Section 309 110/31/16 Page | 74 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Sub

- Activity Type Code A code/description that uniquely identifies each type of enforcement action milestone and/or sub

- activity (e.g., COMPS = compliance achieved, MECDJ = motion to enforce consent agreement, AHRG = administrative hearing , AMNCA = amended complaint ). Some of these milestones are system generated. 123.27, 123.41(a), and CWA Section 309 1

Actual Date The date on which the milestone was achieved/sub ac tivity was conducted. The date must be provided in YYYY

- MM

- DD format where YY YY is the year, MM is the month, and DD is the day . Some of these dates are system generated. 123.27, 123.41(a), and CWA Section 309 1

Final Orders

Final Order Type A code/description that uniquely identifies the regulatory instrument used by the EPA to settle the e nforcement a ction. This code identifies, for example, whether the final order is an administrative compliance order, an administrative penalty order, Feder al facility agreement, etc. 123.27, 123.41(a), and CWA Section 309 1

Final Order Issued/ Entered Date For a judicial enforcement action 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 was issued. The date must be provided in YYYY

- MM

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

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

Penalty10/31/16 Page | 75 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 )

Civil 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 or Final Order. 123.27, 123.41(a), and CWA Section 309 1

Civil Penalty Amount Collected For civil judicial e nforcement a ctions, the dollar amount of the penalty collected from the defendant(s). For a dmi nistrative e nforcement a ctions, it is the dollar amount collected of the penalty assessed in the Consent or Final Order. 123.27, 123.41(a), and CWA Section 309 1

Compliance Schedule

Compliance Schedule Number A two

- digit number which in combination with the Compliance Schedule Type and NPDES ID uniquely identifies a c ompliance s chedule. 123.27, 123.41(a), and CWA Section 309 1
Compliance Schedule Type The code/description that identifies the type of compliance schedule (e.g., an administrative formal action has the code “A”, a judicial action has the code “J”)

. 123.27, 123.41(a), and CWA Section 309 1 Compliance Schedule Description The code/description that identifies each type of condition or requirement (e.g., b est m anagement p ractices p lan development ) for the compliance schedule. 123.27, 123.41(a), and CWA Section 309 1 Compliance Schedule Event Code The unique code/description that identifies each event that is added within a c ompliance

s chedule

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

Compliance Schedule 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 YY YY is the year, MM is the month, and DD is the day

. 123.27, 123.41(a), and CWA Section 309 110/31/16 Page | 76 Table 2 : Required NPDES Data

Data Name Data Description CWA, Regulatory (40 CFR) , or Other Citation NPDES

Data Group Number ( see Table 1 ) Compliance Schedule Actual Date The actual date on which the c ompliance s chedule event was completed or achieved. The date must be provided in YYYY

- MM

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

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

Compliance Schedule Report Received Date The date the regulatory agency received the report required by the c ompliance s chedule report. The date must be provided in YYYY

- MM

- DD format where YY YY 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 the 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 f or control mechanisms for new facilities reported on a Pretreatment Program Annual 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 dat a elements in this table conform to EPA’s policy regarding the application requirements for renewal or reissuance of NPDES pe rmits for discharges from municipal separate storm sewer systems (see 61 FR 41698; 6 August 1996).
(3) The data elements in this t able are also supported by the Office Management and Budget approved permit applications and forms for the NPDES program.