These are data elements that are common to reports required in parts 122, 123, 403, and 503
                                 4,5,6,7,9,10
End Date of Reporting Period (Program Report)
The end date of the reporting period for the program report. The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day. For the Sewer Overflow/Bypass Event Report this is the end or best estimate of the end date for each Sewer Overflow/Bypass Identifier.
These are data elements that are common to reports required in parts 122, 123, 403, and 503
                                 4,5,6,7,9,10
NPDES Data Group Number (Program Report)
This data element identifies the NPDES Data Group for each program report submission. This corresponds to Table 1 in this appendix {e.g., 7 = Pretreatment Program Reports [40 CFR 403.12(i)]}.This data element also applies to Significant Industrial User Compliance Reports in Municipalities Without Approved Pretreatment Programs [40 CFR 403.12(e) and (h)], which is NPDES Data Group Number 8 (Table 1 in this appendix). This can be a system generated data element.
These are data elements that are common to reports required in parts 122, 123, 403, and 503
                                 4 through 10
Compliance Monitoring Activity Information (Data Elements Specific to Sewage Sludge/Biosolids Annual Program Reports)
Biosolids or Sewage Sludge Treatment Processes
 The one or more unique codes/descriptions that identify the biosolids or sewage sludge treatment process or processes at the facility. For example, this data element uses codes to identify treatment processes in the following categories: preliminary operations (e.g., sludge grinding and degritting), thickening (concentration), stabilization, anaerobic digestion, aerobic digestion, composting, conditioning, disinfection (e.g., beta ray irradiation, gamma ray irradiation, pasteurization), dewatering (e.g., centrifugation, sludge drying beds, sludge lagoons), heat drying, thermal reduction, and methane or biogas capture and recovery.
                            503.18, 503.28, 503.48
                                       4
Biosolids or Sewage Sludge Analytical Methods
 The one or more unique codes/descriptions that identify each of the analytic methods used by the facility to analyze enteric viruses, fecal coliforms, helminth ova, Salmonella sp., and other regulated parameters. For example, EPA requires facilities to monitor for the certain parameters, which are listed in Tables 1, 2, 3, and 4 at 40 CFR 503. 13 and Tables 1 and 2 at 40 CFR 503.23. This data element stores each analytic methods used by the facility only once for each annual report (not for each parameter measurement).
                       503.8(b), 503.18, 503.28, 503.48
                                       4
Biosolids or Sewage Sludge Form
 The one or more unique codes/descriptions that identify the nature of each biosolids and sewage sludge material generated by the facility in terms of whether the material is a biosolid or sewage sludge and whether the material is ultimately conveyed off-site in bulk or in bags. The facility will separately report the form for each biosolids or sewage sludge management practice or practices used by the facility and pathogen class.
                            503.18, 503.28, 503.48
                                       4
Biosolids or Sewage Sludge Management Practice
 The one or more unique codes/descriptions that identify the type of biosolids or sewage sludge management practice or practices (e.g., land application, surface disposal, incineration) used by the facility. The facility will separately report the management practice for each biosolids or sewage sludge form and pathogen class. This data element will also identify the management practices used by surface disposal site owners/operators (see 40 CFR 503.24).
                            503.18, 503.28, 503.48
                                       4
Biosolids or Sewage Sludge Pathogen Class
 The one or more unique codes/descriptions that identify the pathogen class or classes [e.g., Class A, Class B, Not Applicable (Incineration)] for biosolids or sewage sludge generated by the facility. The facility will separately report the pathogen class for each biosolids or sewage sludge management practice used by the facility and by each biosolids or sewage sludge form.
                            503.18, 503.28, 503.48
                                       4
Biosolids or Sewage Sludge Amount (Program Report)
 This is the amount (in dry metric tons) of biosolids or sewage sludge applied to the land, prepared for sale or give-away in a bag or other container for application to the land, or placed on an active sewage sludge unit. This identification will be made for each biosolids or sewage sludge management practice used by the facility and by each biosolids or sewage sludge form as well as by each biosolids or sewage sludge pathogen class.
                            503.18, 503.28, 503.48
                                       4
Biosolids or Sewage Sludge Pathogen Reduction Options
 The one or more unique codes/descriptions that identify the options used by the facility to control pathogens (e.g., Class A  -  Alternative 1, Class A  -  Alternative 2, Class A  -  Alternative 3, Class A  -  Alternative 4, Class A  -  Alternative 5, Class A  -  Alternative 6, Class B  -  Alternative 1, Class B  -  Alternative 2, Class B  -  Alternative 3, or pH Adjustment (Domestic Septage). The facility will separately report the pathogen reduction options for each biosolids or sewage sludge management practice used by the facility and by each biosolids or sewage sludge form as well as by each biosolids or sewage sludge pathogen class.
                            503.18, 503.28, 503.48
                                       4
Biosolids or Sewage Sludge Vector Attraction Reduction Options
 The one or more unique codes/descriptions that identify the options used by the facility for vector attraction reduction. See a listing of these vector attraction reduction options at 40 CFR 503.33(b)(1) through (11). The facility will separately report the vector attraction reduction options for each biosolids or sewage sludge management practice used by the facility and by each biosolids or sewage sludge form as well as by each biosolids or sewage sludge pathogen class.
                            503.18, 503.28, 503.48
                                       4
Biosolids or Sewage Sludge 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 sludge form. EPA requires facilities to monitor for the certain parameters, which are listed in Tables 1, 2, 3, and 4 at 40 CFR 503. 13 and Tables 1 and 2 at 40 CFR 503.23, pathogens (e.g., fecal coliform, Salmonella sp., enteric viruses, helminth ova), and vector attraction reduction parameters (e.g., specific oxygen uptake rate, and total, fixed, and volatile solids).
                            503.18, 503.28, 503.48
                                       4
Biosolids or Sewage Sludge Monitored Parameter Value
 This is the value of the Biosolids or Sewage Sludge Monitored Parameter.
                            503.18, 503.28, 503.48
                                       4
Biosolids or Sewage Sludge Monitored Parameter Units
 This is the measurement unit (e.g., mg/kg) associated with the Biosolids or Sewage Sludge Monitored Parameter Value.
                            503.18, 503.28, 503.48
                                       4
Biosolids or Sewage Sludge Monitored Parameter End Date
 This is the end date of the monthly monitoring period for the biosolids or sewage sludge sampling (e.g., 1/31/2015 for biosolids or sewage sludge monitoring data in January 2015). This data element is used to track the frequency of biosolids or sewage sludge monitoring in the reporting period (e.g., annual, quarterly, bi-monthly, or monthly). For example, see Table 1 of 40 CFR 503.16 (Land Application), Table 1 of 40 CFR 503.26 (Surface Disposal).
                            503.18, 503.28, 503.48
                                       4
Biosolids or Sewage Sludge - Surface Disposal Maximum Allowable Pollutant Concentration
 This data element is applicable to facilities that use an active surface disposal sites (e.g., monofills, surface impoundments, lagoons, waste piles, dedicated disposal sites, and dedicated beneficial use sites) without a liner. This data element identifies the maximum allowable pollutant concentration for each of the three pollutants: arsenic, chromium, and nickel (in units of mg/kg). This data element will use Tables 1 and 2 of 40 CFR 503.23 or the procedures identified in 40 CFR 503.23(b).
                                503.23, 503.28
                                       4
Biosolids or Sewage Sludge - Land Application or Surface Disposal Deficiencies
 This data element is applicable to facilities that use land application and/or an active surface disposal site (e.g., monofills, surface impoundments, lagoons, waste piles, dedicated disposal sites, and dedicated beneficial use sites). This data element uses one or more unique codes/descriptions to identify all deficiencies in the biosolids or sewage sludge program within the reporting period. For example, this data element uses a unique code/description to identify when a biosolids or sewage sludge pollutant concentration exceed a ceiling concentration (e.g., Table 1 of 40 CFR 503.13 for facilities utilizing land application). This data element also uses a unique code/description to identify when the facility failed to properly collect and analyze its biosolids or sewage sludge in accordance with the approved analytical methods (including appropriate method holding times). This data element also uses a unique code/description to identify deficiencies with pathogen reduction and/or vector attraction reduction. For facilities that use an active surface disposal site this data element will use a unique code/description to identify any deficiencies in meeting the applicable surface disposal requirements [see 40 CFR 503.24(a) through (n)].
                                503.18, 503.28
                                       4
Compliance Monitoring Activity Information (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 lambs, horses, ducks, and turkeys.
                                122.42(e)(4)(i)
                                       5
CAFO Animal Maximum Number (Program Report)
The estimated maximum number of each type of animal in open confinement or housed under roof (either partially or totally) which are held at the facility for a total of 45 days or more in the previous 12 months.
                                122.42(e)(4)(i)
                                       5
CAFO Animal Maximum Number in Open Confinement (Program Report)
The estimated maximum number of each type of animal in open confinement which are held at the facility for a total of 45 days or more in the previous 12 months.
                                122.42(e)(4)(i)
                                       5
CAFO MLPW (Program Report)
The unique code/description that identifies the type of CAFO manure, litter, and process wastewater generated by the facility i.e.in the previous 12 months.
                               122.42(e)(4)(ii)
                                       5
CAFO MLPW Amounts (Program Report)
The estimated total amount of CAFO manure, litter, and process wastewater generated by the facility in the previous 12 months.
                               122.42(e)(4)(ii)
                                       5
CAFO MLPW Amounts Units (Program Report)
The unit (e.g., tons, gallons) for the estimated total amount of CAFO manure, litter, and process wastewater generated by the facility i.e.in the previous 12 months.
                               122.42(e)(4)(ii)
                                       5
CAFO MLPW Transferred (Program Report)
The estimated total amount of CAFO manure, litter, and process wastewater generated by the facility i.e.in the previous 12 months that is transferred to other persons. The units for this data element will be the same as the units for the "CAFO MLPW Amounts (Program Report)" data element.
                               122.42(e)(4)(iii)
                                       5
Total Number of Acres for Land Application Covered by the Nutrient Management Plan (Program Report)
Total number of acres for land application covered by the current nutrient management plan.
                               122.42(e)(4)(iv)
                                       5
Total Number of Acres Used for Land Application (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 discharge from the permittee's production area in the previous 12 month whether a 25-year, 24-hour rainfall event was the cause for the discharge. These data are optional if permittee uses a Discharge Monitoring Report (DMR) to provide the permitting authority with information on their discharges.
                             122.42(e)(4)(vi), 412
                                       5
Discovery Dates 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 YYYY is the year, MM is the month, and DD is the day. These data are optional if permittee uses a Discharge Monitoring Report (DMR) to provide the permitting authority with information on their discharges.
                               122.42(e)(4)(vi)
                                       5
Duration of Discharges from Production Area (Program Report)
The estimated duration time (in hours) of each discharge from the permittee's production area in the previous 12 months. These data are optional if permittee uses a Discharge Monitoring Report (DMR) to provide the permitting authority with information on their discharges.
                               122.42(e)(4)(vi)
                                       5
Approximate Volume of Discharge from Production Area (Program Report)
The approximate volume (in gallons) of each discharge from the permittee's production area in the previous 12 months. These data are optional if permittee uses a Discharge Monitoring Report (DMR) to provide the permitting authority with information on their discharges.
                               122.42(e)(4)(vi)
                                       5
Whether NMP Approved or Developed by Certified Planner (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 manure, litter, and process wastewater used or generated by the facility i.e.in the previous 12 months.
                              122.42(e)(4)(viii)
                                       5
CAFO MLPW Phosphorus Content (Program Report)
The phosphorus content of CAFO manure, litter, and process wastewater used or generated by the facility i.e.in the previous 12 months.
                              122.42(e)(4)(viii)
                                       5
CAFO MLPW Nitrogen or Phosphorus Units (Program Report)
The unit(s) (e.g., lbs/tons, lbs/1,000-gallons) for the nitrogen and phosphorus content of CAFO manure, litter, and process wastewater used or generated by the facility i.e.in the previous 12 months.
                              122.42(e)(4)(viii)
                                       5
CAFO MLPW Nitrogen or Phosphorus Form (Program Report)
The form (e.g., total nitrogen, ammonium-nitrogen, total phosphorus) for the nitrogen and phosphorus content of CAFO manure, litter, and process wastewater used or generated by the facility i.e.in the previous 12 months.
                              122.42(e)(4)(viii)
                                       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 Crop(s) Planted for Each Field (Program Report)
Actual crop(s) planted for each field.
                              122.42(e)(4)(viii)
                                       5
Actual Crop Yield(s) for Each Field (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 actual crop yield(s) for each field (e.g., bushels per acre).
                              122.42(e)(4)(viii)
                                       5
Method for Calculating Maximum Amounts of Manure, Litter, and Process Wastewater (Program Report)
The unique code/description that identifies whether the CAFO used the Linear Approach [40 CFR 122.42(e)(5)(i)] or the Narrative Rate Approach [40 CFR 122.42(e)(5)(ii)].
                              122.42(e)(4)(viii)
                                       5
CAFO MLPW Land Application For Each Field (Program Report)
The unique code/description that identifies for each field the type of CAFO manure, litter, and process wastewater i.e.in the previous 12 months and used for land application.
                              122.42(e)(4)(viii)
                                       5
CAFO MLPW Land Application Maximum Amount For Each Field (Program Report)
The maximum amount of CAFO manure, litter, and process wastewater for each field in the previous 12 months and used for land application. The maximum amounts of CAFO manure, litter, and process wastewater is calculated in accordance with procedures in the Linear Approach [40 CFR 122.42(e)(5)(i)(B)] or the Narrative Rate Approach [40 CFR 122.42(e)(5)(ii)(D)].
                              122.42(e)(4)(viii)
                                       5
CAFO MLPW Land Application Actual Amount For Each Field (Program Report)
The actual amount of CAFO manure, litter, and process wastewater for each field in the previous 12 months and used for land application.
                              122.42(e)(4)(viii)
                                       5
CAFO MLPW Land Application For Each Field Unit (Program Report)
The unit (e.g., tons, gallons) for the maximum and actual amount of CAFO manure, litter, and process wastewater for each field in the previous 12 months and used for land application.
                              122.42(e)(4)(viii)
                                       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)(viii)
                                       5
Phosphorus Soil Test Measurement (Narrative Rate Approach) (Program Report)
For each field used for land application, the results of the most recent soil phosphorus analysis for any soil test taken in the preceding 12 months (i.e., amount of phosphorus in the soil). This data element is only applicable to facilities using the Narrative Rate Approach as described in 40 CFR 122.42(e)(5)(ii).
                              122.42(e)(4)(viii)
                                       5
Soil Test Measurement Form (Narrative Rate Approach) (Program Report)
The 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)(viii)
                                       5
Soil Test Measurement Unit(s) (Narrative Rate Approach) (Program Report)
The unit(s) for the amounts of nitrogen and/or phosphorus for any soil test results. This data element is only applicable to facilities using the Narrative Rate Approach, as described in 40 CFR 122.42(e)(5)(ii).
                              122.42(e)(4)(viii)
                                       5
Nitrogen Amount of Any Supplemental Fertilizer Applied (Program Report)
For each field used for land application, provide the amount of nitrogen in supplemental fertilizer applied in the previous 12 months. This data element is only applicable to facilities using the Narrative Rate Approach as described in 40 CFR 122.42(e)(5)(ii).
                              122.42(e)(4)(viii)
                                       5
Phosphorus Amount of Any Supplemental Fertilizer Applied (Program Report)
For each field used for land application, provide the amount of phosphorus in supplemental fertilizer applied in the previous 12 months. This data element is only applicable to facilities that are using the Narrative Rate Approach as described in 40 CFR 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 Information (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).
MS4 Reliance on Other Government Entities Status
This is a unique code (e.g., "Yes", "No") that identifies whether the permittee relies on another unique governmental entity to satisfy any of the permit requirements.
                              122.26(d)(2)(vii),
                                122.34(g)(3)(v)
                                       6
MS4 Reliance on Other Government Entities: Permit Component Status
For each MS4 permit component this data element identifies the responsible government entity. This data element uses the `Unique Identifier for Each Municipality Covered Under MS4 Permit' data element. Use of this identifier allows for greater geographic resolution for the MS4 components being tracked. This unique identifier does not change over time. The number identifies the entity taking responsibility for complying with each MS4 permit component.
               122.34(g)(3)(i) and (v), 122.35(a) and 122.42(c)
                                       6
MS4 Permit Components Descriptions and Measurable Goals
The one or more codes/descriptions that identify for each unique municipality all of the permitted components and measurable goals that are included in the MS4 permit. For Phase II MS4s, these components will be pre-populated from the BMPs each Phase II MS4 permittee indicated it will implement in its NOI or permit application. The groupings of these MS4 components will include public education and outreach on stormwater impacts; public involvement/participation; illicit discharge detection and elimination; construction site stormwater runoff; post-construction stormwater management in new development and redevelopment; and pollution prevention/good housekeeping for municipal operations.
                          122.34(g)(3) and 122.42(c)
                                       6
Changes to MS4 Permit Components and Measurable Goals
The one or more codes/descriptions that describe for each 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
Status of Compliance with each Minimum Control Measure
The unique code (e.g., "Yes", "No") that identifies if the permittee has completed each measureable goal associated with each MS4 permit component.
                          122.34(g)(3) and 122.42(c)
                                       6
Progress and Summary of Results with Each Minimum Control Measure
This is a text summary describing the permittee's compliance and progress toward meeting each measurable goal including a summary of results for each unique municipality.
                          122.34(g)(3) and 122.42(c)
                                       6
MS4 Enforcement Action Type
For each unique municipality covered under a Phase I MS4 permit, this data element identifies the one or more types of enforcement actions taken during the past reporting period (e.g., notice of violations, stop work orders, administration orders, administrative fines, civil penalties, criminal actions). 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. This data element is optional for Phase II MS4s.
                          122.34(g)(3) and 122.42(c)
                                       6
MS4 Enforcement Action Number
For each unique municipality covered under a Phase IIMS4 permit and for each MS4 Enforcement Action Type, this data element identifies the number of enforcement actions taken by responsible MS4 Municipal Enforcement Agency. The unique municipality covered under the MS4 permit will identify "No Authority" for this data element if the municipality does not have the authority to conduct enforcement actions. For Phase II MS4s this data element will be the total number of enforcement actions taken during the reporting period.
                          122.34(g)(3) and 122.42(c)
                                       6
MS4 Municipality Enforcement Agency
For each unique municipality covered under the MS4 permit and for each MS4 Enforcement Action Type, this data element identifies the corresponding MS4 Municipal Enforcement Agency by its unique municipality number ("Unique Identifier for Each Municipality Covered Under MS4 Permit").This data element is only required for permittees that have co-permittees under their unique MS4 permit.
                          122.34(g)(3) and 122.42(c)
                                       6
MS4 Industrial Stormwater Control
The one or more unique codes/descriptions that identify how the MS4 permittee will comply with industrial stormwater control requirements, including (at a minimum): (1) status of the ordinance or other regulatory mechanism to control the contribution of pollutants by stormwater discharges associated with industrial activity, including authority to carry out all inspection, surveillance and monitoring procedures necessary to determine compliance and noncompliance, and including sanctions to ensure compliance; (2) status of the MS4 permittee industrial stormwater inventory, which identifies facilities with industrial activities and assesses the quality of the stormwater discharged from each facility with an industrial activity; (3) status of program to monitor and control pollutants in stormwater discharges from municipal landfills, hazardous waste treatment, disposal and recovery facilities, industrial facilities that are subject to Toxics Release Inventory (TRI) reporting requirements (Emergency Planning and Community Right-To-Know Act Section 313), and industrial facilities that are contributing a substantial pollutant loading to the MS4; and (4) status of monitoring program for discharges associated with industrial facilities. This data element is optional for Phase II MS4s.
                 40 CFR 122.26(d)(2)(i)(A, B, C, E, and F) and
         40 CFR 122.26(d)(2)(ii) and (iv)(A)(5) and (iv)(C), 122.42(c)
                                       6
Compliance Monitoring Activity Information (Data Elements Specific to Pretreatment Program Reports, SIU Periodic Compliance Reports in Municipalities without an Approved Pretreatment Program)
(Note: These data elements do not apply to the development, evaluation, or compliance monitoring activities supporting wastewater surcharge rates.)
SNC Published
A unique code (e.g., "Yes", "No") that identifies for each Significant Industrial User (SIU) and Non-Significant Categorical Industrial Users (NSCIU) in SNC whether the Control Authority published a public notice within the reporting period.
                        403.8(f)(2)(viii), 403.12(i)(2)
                                       7
SNC with Pretreatment Enforceable Compliance Schedule Status
The unique code/description that identifies for each Significant Industrial User (SIU) and Non-Significant Categorical Industrial User (NSCIU) in SNC whether the industrial user in SNC is subject to one or more enforceable compliance schedules within the reporting period.
                        403.8(f)(2)(viii), 403.12(i)(2)
                                       7
Local Limits Adoption Date
This is the most recent date on which the Control Authority adopted new local limits within the reporting period. The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day. The Control Authority can leave this data element blank on the Pretreatment Program Report if the Control Authority did not adopt any new local limits within the reporting period.
         122.44(j)(2)(ii), 403.5(c), 403.8(f)(4) and (5), 403.12(i)(4)
                                       7
Local Limits Evaluation Date
This is the most recent date on which the Control Authority completed an evaluation on the potential need for local limits within the reporting period. The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day. The Control Authority can leave this data element blank on the Pretreatment Program Report if the Control Authority did not evaluate any local limits within the reporting period.
  122.44(j)(2)(ii), 403.5(c), 403.8(f)(4) and (5), 403.12(i)(4), 403.8(f)(4)
                                       7
Local Limits Pollutants
This is the list of the pollutants for which the Control Authority adopted local limits. The Control Authority will only need to enter each pollutant once no matter how many treatment works are managed by the Control Authority. The Control Authority can leave this data element blank on the Pretreatment Program Reports if the Control Authority did not change the pollutants for which the Control Authority derived local limits.
                            403.5(c), 403.12(i)(4)
                                       7
POTW Discharge Contamination Indicator (Program Report)
The one or more unique codes/descriptions that identify any problems (e.g., pass-through, interference, violation of NPDES permit limits) with the receiving POTW's effluent discharge within the reporting period. See 40 CFR 403.3(k) and (p). EPA regulations require the Control Authority to develop and enforce local limits when the discharge from an IU causes or contributes to any problems at the receiving POTW.
                              403.8(f), 403.12(i)
                                       7
POTW Biosolids or Sewage Sludge Contamination Indicator (Program Report)
The one or more unique codes/descriptions that identify any problems (e.g., interference with the use or disposal of biosolids or sewage sludge, violation of NPDES permit requirements or EPA's regulations at 40 CFR part 503) with the receiving POTW's biosolids or sewage sludge within the reporting period. See 40 CFR 403.3(k). EPA regulations require any Control Authority that must develop a Pretreatment Program also to develop and enforce local limits to ensure that the discharge from an IU does not cause or contribute a disruption of biosolids' use or disposal at the receiving POTW.
                              403.8(f), 403.12(i)
                                       7
Industrial User Control Mechanism Status
A unique code/description that identifies whether the Industrial User is subject to an effective Control Mechanism within the reporting period.
                              403.3(k), 403.5(c),
                              403.8(f), 403.12(i)
                                       7
Industrial User Control Mechanism Effective Date
The date when the active Control Mechanism for the Industrial User became effective. The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day.
                       403.8(f)(1)(iii)(B)(1), 403.12(i)
                                       7
Industrial User Control Mechanism Expiration Date
The date when the active Control Mechanism for the Industrial User will expire. The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day.
                              403.8(f), 403.12(i)
                                       7
SNC with Pretreatment Standards or Limits (Program Report)
This data element will identify for each Significant Industrial User (SIU) and Non-Significant Categorical Industrial User (NSCIU) whether the IU was in Significant Non-Compliance (SNC) with any pretreatment standard or local limits applicable to the industrial user's discharge within the reporting period.
                              403.8(f), 403.12(i)
                                       7
SNC with Pretreatment Standards or Limits Pollutants (Program Report)
This data element will identify for each Significant Industrial User (SIU) and Non-Significant Categorical Industrial User (NSCIU) the pollutants that related to the industrial user's Significant Non-Compliance (SNC) status with any applicable pretreatment standard or local limits within 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 Categorical Industrial User (NSCIU) whether the 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) within the reporting period.
            123.26, 123.41(a), 123.45, 403.8(f), 403.10, 403.12(i)
                                      1,7
SNC with Other Control Mechanism Requirements (Program Report)
This data element will identify for each Significant Industrial User (SIU) and Non-Significant Categorical Industrial User (NSCIU) whether the IU was in Significant Non-Compliance (SNC) with any other control mechanism requirements within the reporting period. This data element does not include instances of SNC that relate to the industrial user's applicable discharge standards or local limits or reporting requirements.
            123.26, 123.41(a), 123.45, 403.8(f), 403.10, 403.12(i)
                                      1,7
Listing of Months in SNC
This data element will identify for each Significant Industrial User (SIU) and Non-Significant Categorical Industrial User (NSCIU) the month or months the IU is in SNC within the reporting period. These data must be provided in YYYY-MM format where YYYY is the year and MM is the month.
            123.26, 123.41(a), 123.45, 403.8(f), 403.10, 403.12(i)
                                      1,7
Number of Industrial User Inspections by Control Authority
This data element will identify for each Significant Industrial User (SIU) the number of inspections conducted by the Control Authority within the reporting period.
                              403.8(f), 403.12(i)
                                       7
Number of Industrial User Sampling Events by Control Authority
This data element will identify for each Significant Industrial User (SIU) the number of complete sampling events conducted by the Control Authority within the reporting period.
                              403.8(f), 403.12(i)
                                       7
Number of Required Industrial User Self-Monitoring Events
This data element will identify for each Significant Industrial User (SIU) the number of required self-monitoring sampling events within 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) the actual number of self-monitoring sampling events within the reporting period submitted to the Control Authority.
                              403.8(f), 403.12(i)
                                       7
Types of Industrial User Enforcement Action
This data element will identify for each Significant Industrial User (SIU) the type(s) of formal enforcement action(s) (e.g., formal notices of violation or equivalent actions, administrative orders, civil suits, criminal suits) issued by the Control Authority within the reporting period. The Control Authority can also optionally use this data element to track informal actions that they issued within the reporting period.
                              403.8(f), 403.12(i)
                                       7
Number of Industrial User Enforcement Actions
This data element will identify for each Significant Industrial User (SIU) and for each type of enforcement action the total number of formal enforcement actions issued by the Control Authority within the reporting period. The Control Authority can also optionally use this data element to track informal actions that they issued within the reporting period.
                              403.8(f), 403.12(i)
                                       7
Industrial User Cash Civil Penalty Amount Assessed
For civil judicial Enforcement Actions, the dollar amount of the penalty assessed against each Significant Industrial User (SIU) and Non-Significant Categorical Industrial User (NSCIU) within the reporting period as specified in the final entered Consent Decree or Court Order. For Administrative Enforcement Actions, it is the dollar amount of the penalty assessed in the Consent/Final Order.
                                CWA section 309
                                       7
Industrial User Cash Civil Penalty Amount Collected
For civil judicial Enforcement Actions, the dollar amount of the penalty collected from each Significant Industrial User (SIU) and Non-Significant Categorical Industrial User (NSCIU) within the reporting period. For Administrative Enforcement Actions, it is the dollar amount collected of the penalty assessed in the Consent/Final Order.
                                CWA section 309
                                       7
Industrial User POTW Discharge Contamination Indicator (Program Report)
The one or more unique codes/descriptions that identify for each Significant Industrial User (SIU) and Non-Significant Categorical Industrial User (NSCIU) whether the Industrial User caused or contributed to any problems (e.g., pass-through, interference, violation of NPDES permit limits) with the receiving POTW's effluent discharge in the previous reporting period. See 40 CFR 403.3(k) and (p). EPA regulations require the Control Authority to develop and enforce local limits when the discharge from an IU causes or contributes to any problems e.g.at the receiving POTW.
       123.26, 123.41(a), 123.45, 403.5(c), 403.8(f), 403.10, 403.12(i)
                                      1,7
Industrial User Biosolids or Sewage Sludge Contamination Indicator (Program Report)
The one or more unique codes/descriptions that identify for each Significant Industrial User (SIU) and Non-Significant Categorical Industrial User (NSCIU) whether the Industrial User caused or contributed to any problems (e.g., interference with the use or disposal of biosolids or sewage sludge, violation of NPDES permit requirements or EPA's regulations at 40 CFR part 503) with the receiving POTW's biosolids or sewage sludge in the previous reporting period. See 40 CFR 403.3(k). EPA regulations require the Control Authority to develop and enforce local limits when the discharge from an IU causes or contributes to any problems e.g.at the receiving POTW.
       123.26, 123.41(a), 123.45, 403.5(c), 403.8(f), 403.10, 403.12(i)
                                      1,7
Industrial User Wastewater Flow Rate (Program Report)
This data element will identify for each Significant Industrial User (SIU) and Non-Significant Categorical Industrial User (NSCIU) the maximum monthly average wastewater flow rate (in gallons per day) in the previous reporting period.
                   403.8(f), 403.12(e), 403.12(h), 403.12(i)
                                      7,8
Middle-Tier Significant Industrial User Reduced Reporting Status
The unique code/description that identifies for each Middle-Tier Significant Industrial User (MTSIU) whether the Control Authority has granted reduced reporting requirements in accordance with 40 CFR 403.12(e)(3).
         123.26, 123.41(a), 123.45, 403.10, 403.12(e)(3), 403.12(i)(2)
                                      1,7
Non-Significant Categorical Industrial User (NSCIU) Certification Submitted to Control Authority
The unique code/description that identifies for each Non-Significant Categorical Industrial User (NSCIU) whether the facility has reported its required annual compliance certification to the Control Authority within the reporting period.
          123.26, 123.41(a), 123.45, 403.10, 403.12(i)(2), 403.12(q)
                                      1,7
Notification of Changed Discharge Submission
The unique code (e.g., "Yes", "No") that identifies for each Significant Industrial User (SIU) and Non-Significant Categorical Industrial User (NSCIU) whether the Industrial User submitted a notification within the reporting period to the Control Authority of a substantial change in the volume or character of pollutants in their discharge, including the listing or characteristic hazardous wastes for which the Industrial User previously submitted notice.
                        403.8(f), 403.12 (i), 403.12(j)
                                      1,7
Compliance Monitoring Activity Information (Data Elements Specific to Sewer Overflow/Bypass Event Reports)
[Note: These data elements apply to sewer overflows and bypass events at POTWs. These data elements do not apply to industrial facilities. This report uses the `Permitted Feature Identifier (Compliance Monitoring Activity)' data element to identify the location of each sewer overflow or bypass at a permitted feature. Each bypass location should be permitted and have an identifier in the `Permitted Feature Identifier (Permit)' data element. This report will also identify the location of each sewer overflow at an unpermitted feature.]
Sewer Overflow/Bypass Identifier
This data element will allow the reporting of multiple sewer overflows or bypasses on one report. Each individualized sewer overflow or bypass will be given a unique identifier (e.g., 1, 2, 3, and so on) for each Sewer Overflow/Bypass Event Report. This field can be system generated to accommodate one or more individual sewer overflows or bypasses. If the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire sewer system the POTW can use this data element to indicate that the number of sewer overflows cannot be tabulated as they are too numerous to count.
                  122.41(l)(4), (6), and (7) and 122.41(m)(3)
                                     3, 9
Sewer Overflow Longitude for Unpermitted Feature (Sewer Overflow/Bypass Event Report)
This data element is required for each Sewer Overflow/Bypass Identifier without a corresponding identifier in the `Permitted Feature Identifier (Permit)' data element, which is reported on the NPDES permit application or Notice of Intent for NPDES permit coverage. This data element is the measure of the angular distance on a meridian east or west of the prime meridian for the sewer overflow location. The format for this data element is decimal degrees (e.g., -77.029289) and the WGS84 standard coordinate system. The `Permitted Feature Identifier (Compliance Monitoring Activity)' data element is used to identify the location of each sewer overflow at a permitted feature. If the sewer overflow is associated with a private residence the longitude of the nearest collection system structure (e.g., manhole) can be used for this data element to the extent that reporting is required. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire sewer system and are too numerous to count. This data element can also be system generated if the Sewer Overflow/Bypass Event Report collects the street location of the sewer overflow and the street location can be used to generate an accurate longitude value. (Note: "Post Office Box" addresses and "Rural Route" addresses are generally not geocodable).
                          122.41(l)(4), (6), and (7)
                                     3, 9
Sewer Overflow Latitude for Unpermitted Feature (Sewer Overflow/Bypass Event Report)
This data element is required for each Sewer Overflow/Bypass Identifier without a corresponding identifier in the `Permitted Feature Identifier (Permit)' data element, which is reported on the NPDES permit application or Notice of Intent for NPDES permit coverage. This data element is the measure of the angular distance on a meridian north or south of the equator for the sewer overflow location. The format for this data element is decimal degrees (e.g., -77.029289) and the WGS84 standard coordinate system. The Permitted Feature Identifier (Compliance Monitoring Activity) data element is used to identify the location of each sewer overflow at a permitted feature. If the sewer overflow is associated with a private residence the latitude of the nearest collection system structure (e.g., manhole) can be used for this data element to the extent that reporting is required. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire sewer system and are too numerous to count. This data element can also be system generated if the Sewer Overflow/Bypass Event Report collects the street location of the sewer overflow and the street location can be used to generate an accurate longitude value. (Note: "Post Office Box" addresses and "Rural Route" addresses are generally not geocodable).
                          122.41(l)(4), (6), and (7)
                                     3, 9
Type of Sewer Overflow/Bypass (Sewer Overflow/Bypass Event Report)
A unique code/description that identifies the type of sewer overflow or bypass (e.g., CSO or SSO from the POTW's collection system, anticipated bypass from the treatment works, unanticipated bypass from the treatment works) for each Sewer Overflow/Bypass Identifier. For bypass events the permittee will also use this data element to identify if any NPDES effluent limitations were violated as a result of the bypass.
                  122.41(l)(4), (6), and (7) and 122.41(m)(3)
                                     3, 9
Type of Sewer Overflow/Bypass Structure
A unique code/description that identifies the type of sewer overflow or bypass structure (e.g., manhole, CSO outfall) for each Sewer Overflow/Bypass Identifier. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire sewer system and are too numerous to count.
                  122.41(l)(4), (6), and (7) and 122.41(m)(3)
                                     3, 9
Sewer Overflow/Bypass Cause
The one or more unique codes/descriptions that best represent the likely cause of the sewer overflow or bypass (e.g., broken pipe, fats/oil/grease, mechanical failure, pump station electrical failure, wet weather, vandalism) for each Sewer Overflow/Bypass Identifier.
                  122.41(l)(4), (6), and (7) and 122.41(m)(3)
                                     3, 9
Duration of Sewer Overflow/Bypass (hours) (Sewer Overflow/Bypass Event Report)
Estimated duration of the sewer overflow or bypass (in hours) for each Sewer Overflow/Bypass Identifier. If the discharge has not been corrected, this is the best professional judgment from the sewer owner or in the case of a bypass, the treatment plant owner, of the time the sewer overflow or bypass is expected to continue. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire sewer system and are too numerous to count.
                  122.41(l)(4), (6), and (7) and 122.41(m)(3)
                                     3, 9
Sewer Overflow/Bypass Discharge Volume (gallons) (Sewer Overflow/Bypass Event Report)
Best professional judgment from the sewer owner on the estimated number of gallons of sewer overflow or bypass for each Sewer Overflow/Bypass Identifier. If the discharge has not been corrected, this is the best professional judgment from the sewer owner or in the case of a bypass, the treatment plant owner, of the volume of overflow or bypass prior to cessation. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire sewer system and are too numerous to count.
                  122.41(l)(4), (6), and (7) and 122.41(m)(3)
                                     3, 9
Receiving Waterbody Name for Unpermitted Feature (Sewer Overflow/Bypass Event Report)
This data element identifies the receiving waterbody name for each Sewer Overflow/Bypass Identifier that does not have a corresponding value in the `Permitted Feature Identifier (Permit)' data element. This data element will use the best professional judgment of the sewer owner to identify the name of the waterbody that is or will likely receive the discharge from each Sewer Overflow/Bypass Identifier. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire sewer system and are too numerous to count.
                          122.41(l)(4), (6), and (7)
                                     3, 9
Wet Weather Occurrence for Sewer Overflow/Bypass Status
The unique code (e.g., "Yes", "No") that represents the best professional judgment of the sewer owner, or in the case of a bypass, the treatment plant owner, regarding whether the sewer overflow or bypass, by Sewer Overflow/Bypass Identifier, occurred during wet weather.
                  122.41(l)(4), (6), and (7) and 122.41(m)(3)
                                     3, 9
Corrective Actions Taken or Planned for Sewer Overflow/Bypass (Sewer Overflow/Bypass Event Report)
The unique code/description that describes the steps taken or planned to reduce, eliminate, and prevent reoccurrence of future sewer overflows or bypasses for each Sewer Overflow/Bypass Identifier and the related impacts to health and the environment. This data element can be used to identify the portion of the sewer overflow or bypass that was contained and recovered prior to any discharge to waters of the U.S. This data element will also identify if any monitoring of the receiving waterbody was done during and/or after the sewer overflow or bypass to gauge the potential impact to health and the environment. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire sewer system and are too numerous to count.
                  122.41(l)(4), (6), and (7) and 122.41(m)(3)
                                     3, 9
Type of Potential Impact of Sewer Overflow/Bypass (Sewer Overflow/Bypass Event Report)
The unique code/description that describes the type of potential health or environmental impact(s) (e.g., beach closure) for each Sewer Overflow/Bypass Identifier. Under 40 CFR 122.41(l)(6), "the permittee shall report any noncompliance which may endanger health or the environment." This data element provides information regarding the nature of such potential endangerment. The POTW can leave this data element blank on the Sewer Overflow/Bypass Event Report if the sewer overflows are caused by an extreme weather event (e.g., hurricane) that floods the entire sewer system and are too numerous to count.
                  122.41(l)(4), (6), and (7) and 122.41(m)(3)
                                     3, 9
Compliance Monitoring Activity Information (Data Elements Specific to CWA section 316(b) Annual Reports)
{Note: Where the Director requires additional measures to protect Federally-listed threatened or endangered species or critical habitat pursuant to 40 CFR 125.94(g), the Director shall require reporting associated with those measures [see 40 CFR 125.97(g)]. The following data elements correspond to this reporting requirement. These data elements are only required for facilities that are required to report on their additional measures to protect Federally-listed threatened or endangered species or critical habitat}.
CWA Section 316(b) Biological Monitoring - Species Name (Program Report)
For existing facilities, a listing of each Federally-listed threatened or endangered species (or relevant taxa) for all life stages that might be susceptible to impingement and entrainment at the facility's cooling water intake structure(s). Specific monitoring protocols and frequency of monitoring will be determined by the Director.
     125.96, 125.97(g), 125.98, 125.138(b), 401.14 and CWA section 316(b)
                                      10
CWA Section 316(b) Biological Monitoring - Species Number (Program Report)
For existing facilities, the number of each Federally-listed threatened or endangered species (or relevant taxa) that might be susceptible to impingement and entrainment at the facility's cooling water intake structure(s). Specific monitoring protocols and frequency of monitoring will be determined by the Director.
     125.96, 125.97(g), 125.98, 125.138(b), 401.14 and CWA section 316(b)
                                      10
CWA Section 316(b) Biological Monitoring - Threatened or Endangered Status (Program Report)
For existing facilities, a unique code/description that identifies for each Federally-listed threatened or endangered species (or relevant taxa) whether the species is threatened, endangered, or is an otherwise protected species that might be susceptible to impingement and entrainment at the facility's cooling water intake structure(s). Specific monitoring protocols and frequency of monitoring will be determined by the Director.
      125.96, 125.97(g), 125.98, 125.138(b), 401.14 and CWA section 316(b)
                                      10
CWA Section 316(b) Biological Monitoring - Species Impinged and Entrained (Program Report)
For existing facilities, the number of each Federally-listed threatened or endangered species (or relevant taxa) impinged and entrained per year by the facility's cooling water intake structure(s). Specific monitoring protocols and frequency of monitoring will be determined by the Director.
     125.96, 125.97(g), 125.98, 125.138(b), 401.14 and CWA section 316(b)
                                      10
CWA Section 316(b) Biological Monitoring - Applicable Measures to Protect Designated Critical Habitat (Program Report)
For existing facilities, a text summary of the measures taken by the permittee to protect designated critical habitat in the vicinity of impingement and entrainment at the facility's cooling water intake structure(s).
     125.96, 125.97(g), 125.98, 125.138(b), 401.14 and CWA section 316(b)
                                      10
Information Common to Violations, Enforcement Actions, and Final Orders
[Note: Single Event Violation (SEV) data elements are mandatory for construction stormwater inspections that identify CWA violations that result in a regulatory authority taking a formal enforcement action. SEV data elements are optional for other construction stormwater inspections.]
Violation Code
The unique code/description that identifies each type of violation that has occurred at the facility (e.g., D80 = Required Monitoring DMR Value Non-Receipt, E90 = Effluent Violation, C20 = Schedule Event Achieved Late). This includes single event violations (SEVs) and violations that are system generated based upon DMRs, schedules, etc.
                          123.45 and CWA section 309
                                       1
Violation Date
This is the date of the violation, which varies depending on the type of violation. The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day. This data element may be system generated and does not apply to single event violation dates.
                          123.45 and CWA section 309
                                       1
Violation Information
Agency Identifying the Single Event Violation (SEV)
The unique code/description that identifies the agency that identified the single event violation (SEV).
                           123.26, 123.41(a), 123.45
                                       1
Single Event Violation Start Date
The date the single event violation (SEV) began. If the SEV occurred on one date, this data element is optional as this date can be system generated to equal "Single Event Violation End Date" when left blank. The date 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 End Date
The date the single event violation (SEV) 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 YYYY is the year, MM is the month, and DD is the day.
                           123.26, 123.41(a), 123.45
                                       1
RNC Detection Code
The unique code/description that identifies the type of reportable noncompliance (RNC) detected by the regulatory authority.
                           123.26, 123.41(a), 123.45
                                       1
RNC Detection Date
The date that reportable noncompliance (RNC) was detected. This date may vary according to the type of violation detected. 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
RNC Resolution Code
The unique code/description that identifies the reportable noncompliance (RNC) status (e.g., noncompliant, resolved pending, waiting resolution, resolved) for each violation. This data element can be entered manually or system generated.
                           123.26, 123.41(a), 123.45
                                       1
RNC Resolution Date
The date reportable noncompliance (RNC) was marked to its current resolution status. This data element is entered manually. The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day.
                           123.26, 123.41(a), 123.45
                                       1
Enforcement Action Information
[Note: NPDES authorized programs will only need to share criminal action information with EPA when the criminal case is concluded.]
Enforcement Action Identifier
The unique identifier for each enforcement action. For EPA enforcement actions, this field will be have three components, each separated by a hyphen (e.g., 04-2014-4509). These three components are: (1) the EPA Region responsible for the enforcement action as identified by the EPA Region code (e.g., 04); (2) the four-digit fiscal year during which the enforcement action is initiated (e.g., 2014); and (3) a four-digit, user-assigned sequence number between 0001 and 9999 (e.g., 4509). States will be able to use this same structure, or they will be able to use a different structure of their choosing provided that the first two characters of the identifier constitute the state code (e.g., Alabama = "AL").
                    123.27, 123.41(a), and CWA section 309
                                       1
Enforcement Action Forum
This identifies the forum of the formal enforcement action (e.g., administrative formal, judicial). This can be system generated.
                    123.27, 123.41(a), and CWA section 309
                                       1
Enforcement Action Type
The unique code/description that identifies the type for each formal or informal enforcement action. This code/description identifies, for example, whether the enforcement action is a civil judicial referral, a notice of violation, an administrative penalty order, administrative order, or criminal prosecution.
                    123.27, 123.41(a), and CWA section 309
                                       1
Programs Violated (Enforcement Action)
The unique code/description that identifies each program (e.g., pretreatment, biosolids/sewage sludge, MS4s, Core NPDES program) associated with each enforcement activity.
                    123.27, 123.41(a), and CWA section 309
                                       1
Enforcement Action Sub-activity Type
A unique code/description that identifies the type for each sub-activity associated with each enforcement activity (e.g., COMPS = compliance achieved, MECDJ = motion to enforce consent agreement, AHRG = administrative hearing, AMNCA = amended complaint). Some of these sub-activities are system required and some can be system generated. Data on sub-activities that are not milestones are optional.
                    123.27, 123.41(a), and CWA section 309
                                       1
Enforcement Action Sub-activity Completion Date
The date on which the sub-activity was completed. This data element is required for each sub-activity provided. The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day. Some of these dates can be system generated.
                    123.27, 123.41(a), and CWA section 309
                                       1
Final Order Information
(Note: These data elements are linked to the "Enforcement Action Identifier". NPDES authorized programs will only need to share criminal action information with EPA when the criminal case is concluded.)
Final Order Identifier
The unique identifier for each final order. This data element can be system generated.
                    123.27, 123.41(a), and CWA section 309
                                       1
Final Order Type
A unique code that identifies the legal process used by the authorized NPDES program to settle the enforcement action (e.g., administrative compliance order, an administrative penalty order, consent decree, Federal facility agreement, criminal conviction or plea agreement).
                    123.27, 123.41(a), and CWA section 309
                                       1
Final Order Issued/ Entered Date
For a judicial enforcement action this is the date the Clerk of the Court stamps the document after it is signed by the presiding Judge. For an administrative formal enforcement action this is the date the Final Order was issued. For a criminal enforcement action, this is the date the sentence was imposed. The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day.
                    123.27, 123.41(a), and CWA section 309
                                       1
NPDES Closed Date
The date of closure for each NPDES final order. The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day.
                    123.27, 123.41(a), and CWA section 309
                                       1
Penalty Information
(Note: These data elements are linked to the "Enforcement Action Identifier". NPDES authorized programs will only need to share criminal action information with EPA when the criminal case is concluded.)
Penalty Amount Assessed
For civil judicial enforcement actions, the dollar amount of the penalty assessed against the defendant(s) as specified in the final entered Consent Decree or Court Order. For administrative enforcement actions, it is the dollar amount of the penalty assessed in the Consent Decree or Final Order. For criminal enforcement actions, it is the dollar amount of the fine agreed to by the defendant or sentenced by the Court and should include fields for prison time, probation, home confinement or monitoring periods, restitution, and special assessments.
                    123.27, 123.41(a), and CWA section 309
                                       1
Penalty Amount Collected
For civil judicial enforcement actions, the dollar amount of the penalty collected from the defendant(s). For administrative enforcement actions, it is the dollar amount collected of the penalty assessed in the Consent Decree or Final Order. For criminal enforcement actions, it is the dollar amount of the fine paid by the defendant as well as restitution and special assessments.
                    123.27, 123.41(a), and CWA section 309
                                       1
Supplemental Environmental Project Identifier
The unique identifier for each supplemental environmental project. This data element can be system generated.
                    123.27, 123.41(a), and CWA section 309
                                       1
Supplemental Environmental Project Amount
The assessed cost, in dollars, of the one or more of the defendant's Supplemental Environmental Projects (SEPs). This is the dollar amount that is assessed either in addition to civil penalties or in lieu of civil penalties. This data element is only required if there is a SEP and may be entered at a later date when the data is available.
                    123.27, 123.41(a), and CWA section 309
                                       1
Supplemental Environmental Project Description
This text field summarizes the Supplemental Environmental Projects (SEPs) that the respondent has completed in response to an enforcement action. This data element is only required if there is a SEP and may be entered at a later date when the data is available.
                    123.27, 123.41(a), and CWA section 309
                                       1
Compliance Schedule Information
(Note: These data elements are linked to the "Enforcement Action Identifier".)
Compliance Schedule Number
This number that in combination with the Compliance Schedule Type and NPDES ID uniquely identifies a compliance schedule.
                    123.27, 123.41(a), and CWA section 309
                                       1
Compliance Schedule Type
The unique code/description that identifies the type of compliance schedule (e.g., an administrative formal action = "A", a judicial action = "J").
                    123.27, 123.41(a), and CWA section 309
                                       1
Compliance Schedule Description
The unique code/description that identifies each type of condition or requirement
(e.g., best management practices plan 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 compliance schedule.
                    123.27, 123.41(a), and CWA section 309
                                       1
Compliance Schedule Due Date
The date the compliance schedule event is scheduled to be completed (i.e., the due date). The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day.
                    123.27, 123.41(a), and CWA section 309
                                       1
Compliance Schedule Actual Date
The actual date on which the compliance schedule event was completed or achieved. The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day.
                    123.27, 123.41(a), and CWA section 309
                                       1
Compliance Schedule Report Received Date
The date the regulatory agency received the report required by the compliance schedule report. The date must be provided in YYYY-MM-DD format where YYYY is the year, MM is the month, and DD is the day.
                    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 for control mechanisms for new facilities reported on a Pretreatment Program Report [40 CFR 403.12(i)]. Additionally, the NPDES program authority can decide whether to allow NPDES regulated entities to override these pre-populated data.
(2) The data elements in this table conform to EPA's policy regarding the application requirements for renewal or reissuance of NPDES permits for discharges from municipal separate storm sewer systems (see 61 FR 41698; 6 August 1996).
(3) The data elements in this table are also supported by the Office Management and Budget approved permit applications and forms for the NPDES program.
(4) These data will allow EPA and the NPDES program authority to link facilities, compliance monitoring activities, compliance determinations, and enforcement actions. For example, these data will provide several ways to make the following linkages: linking violations to enforcement actions and final orders; linking single event violations and compliance monitoring activities; linking program reports to DMRs; linking program reports to compliance monitoring activities; and linking enforcement activities and compliance monitoring activities.