Single Event Violations (SEV) Data Transfer to ICIS

Description

The following is a list of deliverables from this project:

Automatic assignment of SEV codes to DWE’s NJPDES NOVs within the NJEMS Database to be submitted to EPA.

Data query/flow for Linkages between Compliance Evaluations, Enforcement Actions, and SEVs to be submitted to EPA.

Automatically generated XML spreadsheets for the submission of SEV and Linkage Data to EPA’s Exchange Network Services Center. This includes generating data for the Reportable Noncompliance (RNC) fields for SEVs triggering SNC status. The RNC fields will be used for EPA’s NPDES Noncompliance Reports (NNCRs).

Addition of Deficiency Codes to the compliance monitoring data currently being submitted to EPA for Pretreatment, Urban Stormwater (MS4), and CAFOs. (As there are only 2 CAFO facilities, a determination may be made during this project that data entry for CAFOs will be handled manually).
Listed below is how DWE expects the sequence of events and the data to be shared with EPA:

A DWE inspector completes a compliance monitoring activity (e.g., on-site inspection, off-site desk audit) of the NPDES regulated entity.

Next the DWE inspector completes the inspection report that documents the findings in NJEMS/PEGA. DWE reviews relevant records to assess compliance with Clean Water Act and applicable NPDES permits, compliance orders, and other regulations and laws. The inspection report is reviewed by the inspector’s supervisor and then locked.

DWE shares key inspection report data (e.g., compliance monitoring activity end date) and deficiencies with EPA's national NPDES data system (ICIS-NPDES). Timely data entry is within 40 days of the date of the completed inspection report or record. The next steps may happen prior to submission of this data; however, this is where EPA puts this step in their Data Sharing Guidance.

Next the DWE inspector determines that the NPDES-regulated entity has one or more events of noncompliance and issues an enforcement action such as an NOV (Notice of Violation). The SEV code is automatically applied based on which permit condition is out of compliance either instantaneously or by nightly cycle.

Next DWE shares this via an electronic data transfer of this Single Event Violation and related linkage data with EPA’s national NPDES data system (ICIS NPDES). Timely data entry is within 40 days of the determination date.

RNC fields will be updated with resolution data as violations are handled by DWE and submitted to EPA.

Problem Statement

The implementation of new data entry guidance for NPDES deficiency and Single Event Violation (SEV) data, as outlined by the EPA's eRule data sharing requirements (40 CFR 127.23), presents several challenges for DWE. These requirements necessitate accurate sharing of SEV data and deficiencies across five NPDES programs, including Pretreatment, Urban Stormwater (MS4), Sewer Overflow/Bypass, and CAFOs. Current processes involve manual correction of data errors, outdated SEV codes, and insufficient automation in assigning SEV codes to Notices of Violation (NOVs). To ensure compliance, DWE must update the MS4 SEV code implementation, automate SEV code assignments according to the latest guidelines, and establish effective linkages between Compliance Evaluations, Enforcement Actions, and SEVs in a format accepted by the EPA. Addressing these issues is critical for maintaining regulatory compliance and optimizing data management practices.

Project Justification

The NPDES eRule requires EPA and approved States to manage NPDES deficiency and SEV data as follows: (1) deficiencies and SEVs for all NPDES-regulated entities, as defined at 40 CFR 127.2(h), should be determined and recorded in EPA’s national NPDES data system in a manner that is timely, accurate, complete, and nationally consistent; (2) deficiencies and SEVs discovered through EPA or approved State on-site compliance monitoring activity should be linked to that activity; (3) SEVs should be linked to the matching enforcement actions (if a matching enforcement action exists); and (4) the four Reportable Noncompliance (RNC) fields must be included in the SEV record when the corresponding violation triggers Significant Noncompliance (SNC).

Estimated Transactions

None

Created

28 January 2026, 08:35

Target Rollout Date

1 January 2027

Target Rollout Date Reason

This is well before the definitive deadline by EPA of (12/21/2028). Program would like to get this moving and taken care of sooner than later.

Updated

28 January 2026, 14:54

Attachments

Activity