ICIS-NPDES Policy Statement 

DRAFT 

U.S. Environmental Protection Agency 

April 30, 2007 
ICIS-NPDES Policy Statement April 30, 2007 draft ii

ICIS-NPDES Policy Statement

Table of Contents Page

A. Introduction 1

B. Relationship of this ICIS-NPDES Policy Statement to the PCS 3 

 Policy Statement (as revised since issuance in October 1985) 

C. RIDE and Key Data Groupings 3 

D. Efficient Options to Provide Data into ICIS-NPDES 5

E. ICIS-NPDES Data Entry Expectations 7 

F. Data Entry Targets for National Consistency 10

G. Development and Implementation of Transition Plans 12

H. Additional Operational Activities 13 

I. Policy Revision and Relationship to Other Policies 14 

J. Appendices

 1. RIDE by Data Area and Program Area 

2a. Detailed RIDE Table for States, Territories, Tribes and Regions 

 2b. Additional Federal-only RIDE table for Regions 

 3. RIDE Data Entry Considerations by Program Area 

 3a. Revised EPA RIDE Data Entry Model 

4. Key National Targets for Data in ICIS-NPDES 

 5. Template for a Transition Plan 

 6 Roles and Responsibilities 

7. Definitions of Terms and Acronyms 

 a. Terms 

 b. Acronyms 
ICIS-NPDES Policy Statement April 30, 2007 draft 1

A. Introduction 

The U.S. Environmental Protection Agency (EPA) has the primary responsibility 

to ensure that the Clean Water Act’s (CWA) National Pollutant Discharge Elimination 

System (NPDES) program is effectively and consistently implemented across the 

country. In order for EPA to manage the NPDES national program, EPA needs ready 

access to information on the facilities that are regulated by the NPDES program. Some 

of EPA’s national NPDES information needs are described below: 

• Timely access to facility-specific permit, discharge, compliance and 

enforcement information in a nationally consistent format is critical for EPA 

to 1) develop effective regulations, such as national effluent guidelines for 

specific industrial sectors, 2) identify non-compliance problems, trends, and 

their associated environmental impacts on both an intra-state and inter-state 

basis, and 3) develop effective national strategies for improving compliance 

and environmental protection. 

 

• EPA needs information to demonstrate results achieved by effectively using 

resources to meet NPDES program goals, including the Government 

Performance and Results Act (GPRA) measures reported to Congress. Under 

this Act, EPA and other agencies are required to develop long-range Strategic 

Plans, Annual Performance Plans with measures and targets, and Annual 

Performance Reports describing how well targets are met.1

 OMB is now 

linking Agency budgets, including funding for State grants, directly to each 

program’s strategic plans and targets. 

 

• EPA needs facility-specific data to inform the Program Assessment Rating 

Tool (PART) process, which is now used to assess 20% of all Federal 

programs each year. In combination, GPRA and PART require EPA to align 

program activities to annual performance plans, clarify organizational 

expected outcomes, manage outcomes rather than inputs and activities, and 

design measurement systems that accurately track results. In the PART 

process, OMB evaluates performance in program purpose and design, 

strategic planning, program management, and program results and 

accountability. State and Federal funding levels, including State grants, in the 

President’s budget are now linked to PART and have been significantly 

impacted by the PART rating. 

 

 

1

 Examples of GPRA measures for the NPDES program include tracking of schedules for combined sewer 

overflow (CSO) long-term control plans; percent of permits that are current; percent of scheduled highpriority permits that are current; number of facilities covered by storm water permits for municipalities 

(MS4s) and for construction; percent of concentrated animal feeding operations (CAFOs) covered by an 

NPDES permit; percent of significant industrial users (SIUs) in publicly-owned treatment works (POTWs) 

with pretreatment programs that implement applicable pretreatment requirements; and percent of known 

categorical industrial users in non-pretreatment POTWs that have control mechanisms that cover 

pretreatment requirements. 
ICIS-NPDES Policy Statement April 30, 2007 draft 2

• EPA needs detailed information for its program oversight responsibilities. For 

example, Permitting for Environmental Results (PER) was established to 

analyze how the NPDES programs could improve integrity, efficiency, and 

environmental results in the face of declining resources, increasing backlogs, 

expansion of the NPDES program, and third-party petitions and lawsuits to 

withdraw NPDES Programs. Another example, the State Review Framework 

process is used to ensure minimum national consistency in State NPDES 

compliance and enforcement programs. 

• EPA responds to frequent NPDES inquiries from various Congressional 

members, regarding certain facilities, companies, or activities that may be 

national in scope, particularly in conjunction with oversight hearings, 

requiring immediate access to multi-State, facility-specific data on particular 

pollutant discharges. 

In the past, EPA primarily obtained this information from the Permit Compliance 

System (PCS). Since 1985, PCS served as the official national information system used 

for management of the NPDES program. The NPDES program has evolved considerably 

since the creation of PCS. In recent years, there has been an increasing realization, 

confirmed by State water quality reports, that, in addition to traditional major sources, 

smaller and/or non-traditional sources also contribute significantly to the pollution of our 

nation's waters. These smaller and non-traditional sources include facilities in particular 

program areas such as biosolids, concentrated animal feeding operations (CAFOs), 

combined sewer systems (CSSs), separate sanitary sewer systems (SSSs), stormwater and 

pretreatment. 

The evolution of the NPDES program since the inception of PCS has created an 

increasing need to better reflect a more complete picture of the NPDES program and the 

diverse universe of regulated sources. PCS no longer meets the national needs of EPA to 

manage the NPDES program and no longer meets the NPDES program needs of 

individual States that use PCS to implement the NPDES program in their States. 

During the past several years, EPA has worked closely with its State partners in 

an effort to modernize PCS as an NPDES component of EPA’s existing Integrated 

Compliance Information System (ICIS). To accurately reflect the NPDES program, 

ICIS-NPDES was designed to include data and functionality for the full breadth of the 

NPDES program for a variety of permit types and program areas. 

This Policy Statement describes the essential information (defined as the 

Requisite ICIS-NPDES Data Elements [RIDE]) EPA needs nationally to effectively 

manage the national NPDES program. These RIDE and the information that they 

represent are also essential to the individual permitting authorities for effective 

implementation and enforcement of the NPDES program. 
ICIS-NPDES Policy Statement April 30, 2007 draft 3

This ICIS-NPDES Policy Statement establishes ICIS-NPDES as the database of 

record for the national NPDES program and seeks to ensure that ICIS-NPDES contains 

accurate, complete, consistent, and timely information, in accordance with the Data Entry 

Protocols specified in Section E.1. of this Policy Statement. Through implementation of 

this Policy Statement, EPA can effectively manage the NPDES national program to 

ensure that the human health and environmental protection goals of the CWA are met. 

This Policy Statement does not substitute for any CWA statutory provisions or EPA 

regulations and is intended as guidance pursuant to applicable regulations (e.g., 40 

CFR§123.41(a)) . 

B. Relationship of this ICIS-NPDES Policy Statement to the PCS Policy 

Statement (as revised since issuance in October 1985) 

The PCS Policy Statement (issued in October 19852

 and later revised) remains the 

Agency policy for use of PCS for those States, Territories and Tribes currently using or 

transferring data into PCS. The States, Territories and Tribes currently transferring data 

into PCS should review this ICIS-NPDES Policy Statement as certain steps should be 

taken now for a successful transition from PCS to ICIS-NPDES. As set forth in Section 

G, the transition plans for hybrid and non-direct (batch) users of ICIS-NPDES are 

intended to address this need for advance planning. 

As a State, Territory or Tribe moves into ICIS-NPDES (whether as a direct user, 

hybrid user or as a non-direct user) and data is entered directly or is made available for 

batch transfer into ICIS-NPDES, the data entry roles, activities and responsibilities of that 

permitting authority are covered by this ICIS-NPDES Policy Statement. Water 

Enforcement National Data Base (WENDB) is the minimum required data when using 

PCS; Requisite ICIS-NPDES Data Elements (RIDE) have been identified as the 

minimum data that should be available in ICIS-NPDES. 

C. RIDE and Key Data Groupings 

This Policy Statement designates the specific set of data elements that are 

essential for EPA to effectively manage the national NPDES program. These data 

elements are the Requisite ICIS-NPDES Data Elements or RIDE for ICIS-NPDES. EPA 

has consulted with States and Regions extensively in developing and refining RIDE. In 

FY 2002, EPA and State staff and managers identified the data needed to successfully 

implement and manage the NPDES program. Their recommendations were discussed by 

the State and EPA members of the PCS Steering Committee, and subsequently adopted 

 

2

 As issued in 1985, the PCS Policy Statement specified that: 1) PCS would be the national data base of 

record for the NPDES program; 2) the EPA Regions must use PCS directly; and 3) all NPDES authorized 

States must either use PCS directly or develop and maintain an interface that transfers the State’s data to 

PCS. The PCS Policy Statement further defined the minimum required data necessary to enable PCS to 

function as a useful operational and management tool for the NPDES program; in PCS, this list of 

minimum required data was called WENDB. 
ICIS-NPDES Policy Statement April 30, 2007 draft 4

by the PCS Modernization Executive Council as the first draft of what later came to be 

called RIDE. 

 

EPA sought additional state input into RIDE and the development of this Policy 

Statement by expanding the Steering Committee to add representatives from the 

Environmental Council of States (ECOS) and the Association of State and Interstate 

Water Pollution Control Administrators (ASIWPCA). In 2006 and 2007, this Expanded 

Steering Committee held three face-to-face meetings, conducted numerous conference 

calls, and created several workgroups. Based on those efforts, EPA has made significant 

reductions in the initial RIDE list and other revisions to reduce the data entry burden. 

RIDE can be grouped into four main data areas and several data sub-areas, as 

identified in Table 1 below. 

Table 1: RIDE Overview by Data Areas 

ICIS-NPDES 

Data Area Sub-Areas 

Customary 

Entry 

Frequency 

Additional 

Permit 

Component 

Information 

Facility 

Basic Information, Contacts, 

Addresses, Latitude, Longitude 

Once 

(updated if 

necessary) 

None 

Permit 

Basic Information, Narrative 

Condition, Permit Schedule, Permitted 

Feature, Limit 

Once/ 

permit cycle 

Inspections Once/ year 

or less 

Discharge Monitoring Reports 

(DMRs) 

Once/ 

month/ limit 

Compliance 

Monitoring 

Violations As they 

occur 

Biosolids, 

CAFOs, 

CSSs, SSSs, 

Stormwater, 

Pretreatment 

Enforcement 

Basic Information, Milestones, 

Sub-activities, Final Orders, Penalties, 

Compliance Schedules 

As they 

occur 

None 

The data element organization shown in Table 1 is reflected in Appendix 1, which 

is a chart that identifies how many RIDE are associated with each data area. For 

example, Appendix 1 indicates that there are 25 RIDE associated with facility data, 82 

RIDE associated with permitting data, 125 RIDE associated with special program areas, 

and 53 RIDE associated with compliance monitoring and enforcement. 
ICIS-NPDES Policy Statement April 30, 2007 draft 5

Appendix 1 also indicates that, of the 285 RIDE3 to be entered or transferred into 

ICIS-NPDES by permitting authorities, 43 are conditional in that data entry or transfer is 

only expected under rare circumstances or if another RIDE is entered with a particular 

code. An example of such a conditional RIDE would be “Animal: Other” in the CAFO 

component sub-area of RIDE permit information; this data element would only be 

necessary if the entry of the RIDE “Animal: Type” (also in the CAFO component subarea of permit information) was answered with something other than one of the animal 

types listed in the “drop-down menu” of the data entry screen in ICIS-NPDES. 

 A detailed list of all 285 RIDE, with columns providing information regarding 

data element descriptions, equivalent data elements in PCS, permit types for which that 

data element is needed, and comments is provided in Appendix 2a. Appendix 2a also 

identifies each of the 43 conditional RIDE by means of shaded rows on the table.

For a specific facility, not all of the 285 RIDE are likely to apply. The number of 

RIDE that will apply to a particular NPDES facility will vary based on facility-specific 

factors, such as the type of permit(s), the activities undertaken by the State, Territory, 

Tribe or EPA at the facility (e.g., inspections, enforcement actions), and the particular 

operations and processes engaged in by the facility in the particular program area (e.g., 

biosolids, CAFOs, CSSs, SSSs, stormwater and pretreatment). Appendix 3 describes the 

data entry considerations for various special program areas; Appendix 3a indicates the 

estimated data entry resources for various program areas and permit types. 

As Table 1 indicates, the frequency of data entry for RIDE will vary depending on 

the type of data. Many data elements are entered once (e.g., those associated with facility 

identification); permit specific information is usually entered only once every five years; 

Discharge Monitoring Reports (DMRs) are generally entered monthly; inspection, 

violations and enforcement data are entered only if or as those activities occur. Some 

other data elements are system-generated for direct users. In addition, in an effort to 

reduce the resource burden of ICIS-NPDES startup, EPA is working with the individual 

States, Territories or Tribes to ensure that existing facility, permit, compliance 

monitoring and enforcement data is migrated from PCS to ICIS-NPDES. 

 

D. Efficient Options to Provide Data into ICIS-NPDES 

 ICIS-NPDES is a user-friendly system, providing desktop access, real-time data 

and powerful reporting tools. ICIS-NPDES utilizes new technology and promotes 

integrated processing of information. Two efficient methods for States, Territories and 

Tribes to provide EPA with RIDE are through: 

 

3

 An additional 27 RIDE are required for data entry into ICIS-NPDES by EPA Regions for Federal 

activities (e.g., inspections, enforcement actions) and for non-authorized States, Territories and Tribes for 

which the Region is manually entering RIDE. See Appendix 2b for a list of these additional Federal-only 

RIDE. 
ICIS-NPDES Policy Statement April 30, 2007 draft 6

• direct data entry via user-friendly web interfaces, with point and click features 

and drop down menus, including easy-to-use DMR data entry screens; and, 

• batch transferring of data, using approved ICIS-NPDES XML schema, via the 

Agency's Central Data Exchange (CDX) portal and the National Environmental 

Information Exchange Network, and possible utilization of an electronic DMR 

tool, such as NetDMR for facilities. 

Data transfer to ICIS-NPDES is expected to be seamless and transparent. EPA 

recognizes that some States, Territories or Tribes may use both methods of data entry, 

depending on the type of data and their own needs. Because consistent and objective 

compliance tracking is a central component of an effective and credible enforcement 

program, States, Territories and Tribes are encouraged to use ICIS-NPDES directly as a 

primary management system for their NPDES programs. (EPA Regions are required to 

directly use ICIS-NPDES.) 

However, because some States already have their own NPDES databases and plan 

to continue using them to manage the program, these States may batch transfer data to 

ICIS-NPDES. EPA is working with non-direct-user (batch) States through an Integrated 

Project Team (IPT) to develop, test and implement the batch transfer of RIDE to 

ICIS-NPDES. Batch transfer programs from States, Territories and Tribes should 

conform to EPA Central Data Exchange procedures and should use approved ICISNPDES XML schema formats. 

EPA has provided grants to assist States in making the transition from PCS to 

ICIS-NPDES. For example, during FY 2004-2005, ICIS-NPDES was addressed in 

13 Exchange Network grants to facilitate batch information exchange from States that are 

not direct users of ICIS-NPDES. During that same period, EPA’s Office of Enforcement 

and Compliance Assurance (OECA) also provided 21 grants totaling $3.57 million in 

preparations at the State level to migrate data from PCS into ICIS-NPDES or to otherwise 

transition into ICIS-NPDES. 

The RIDE Data Entry Estimate Model developed in association with the 

Expanded Steering Committee has estimated that over 90% of RIDE data entry resources 

are associated with data entry of DMRs. To maximize efficiencies realized already by 

some States, EPA encourages States, Territories and Tribes to pursue electronic reporting 

of DMR data directly by permitted facilities. Electronic DMR submission (verification, 

authentication, and authorization) should be consistent with the Agency’s requirements 

set forth in the Cross-Media Electronic Reporting Final Rule (Federal Register, 

October 13, 2005). 

EPA is working with States to create a national tool (NetDMR) to support 

electronic reporting of DMR data directly from facilities to the permitting authority, a 

feature that will dramatically reduce the cost of entering DMR data into ICIS-NPDES as 

well as into State information systems. Electronic reporting of DMR data will increase 

the quality and amount of DMR data available, while leading to reduced manual data 
ICIS-NPDES Policy Statement April 30, 2007 draft 7

entry costs. This will improve implementation and management of the NPDES program 

by increasing the available effluent data that states and EPA can use to identify and target 

compliance and environmental problems. As many as 20 States are developing electronic 

DMR reporting systems or have applied for EPA grants to develop such systems, and a 

handful of States have already implemented online electronic DMR reporting tools. 

E. ICIS-NPDES Data Entry Expectations 

1. Data Entry Protocols

Once a State, Territory, Tribe or EPA begins using ICIS-NPDES, they are expected to 

follow data entry, timeliness and quality protocols that govern EPA data. EPA may 

assess these protocols on a regular basis. In summary, all data entered or batched into 

ICIS-NPDES should be: 

• Timely: Data for a State, Territory or Tribe should be entered or batched into 

ICIS-NPDES within 30 days of the event/action. For EPA Regions, data for 

inspections, single event violations, and enforcement actions should be entered 

into ICIS-NPDES within 14 days; Regions should enter permit limits, permit limit 

sets, DMRs and other RIDE into ICIS-NPDES within 30 days of receipt. Timely 

data is critical because ICIS-NPDES provides “real time” data for use and 

analysis. In addition, some of this data is accessible to the public through ECHO 

and Envirofacts. 

• Accurate: The design of ICIS-NPDES, with “drop-down” menu lists, standard 

Oracle data validation checks, data standards and ICIS-NPDES XML schema will 

greatly reduce data entry errors. RIDE data should be identical with that reported 

on the DMR, permit or other input document. 

• Complete: Reporting of RIDE ensures that all necessary information is available 

for the purposes of program management, oversight and reporting. This 

ICIS-NPDES Policy Statement establishes an overall goal of at least 98% 

completeness for data entry and, in the appendices to this document, describes 

other targets related to data completeness during the transition period (such as 

interim national data targets for DMR data entry for non-major facilities). 

• Consistent: Data needs to be comparable for use in national and interstate 

watershed analyses and the ICIS-NPDES system design incorporates the Agency 

Data Standards requirements to provide consistent standards for reporting. To 

ensure national consistency, batch transfer programs from States and Tribes 

should conform to EPA Central Data Exchange procedures and should use 

approved ICIS-NPDES XML schema formats.
ICIS-NPDES Policy Statement April 30, 2007 draft 8

2. “Prospective” Entry/Availability of Non-WENDB Data

For those RIDE that were not WENDB data elements in PCS, data 

entry/availability of RIDE in ICIS-NPDES should be “prospective” in nature. That is, 

the RIDE data entry or transfer into ICIS-NPDES for these particular elements should be 

completed from some date forward (in accordance with approved transition plans, as 

described in Sections F and G) without a need to enter old data. One caveat to this rule 

occurs in the case of new enforcement actions addressing violations that are not already 

in the system; EPA expects violation (and any relevant inspection) information associated 

with these actions to be entered into ICIS-NPDES with the enforcement actions. 

3. Few Data Entry Distinctions between Majors and Non-Majors

In PCS, some WENDB data elements apply to every facility regardless of its 

permit type; other WENDB data elements in PCS apply just to major facilities. However, 

in ICIS-NPDES, unlike PCS, few distinctions in data entry expectations for RIDE have 

been made between major facilities and non-major facilities. Exceptions include the 

“phased-in” data entry of DMRs, associated limits, and limit sets for non-majors (as 

described above), and distinctions for some program areas, as described below and in 

Appendix 3, which provides a brief synopsis for each program area. 

4. Appropriate Linkages in ICIS-NPDES

 Appropriate linkages between the data for compliance monitoring, violations and 

enforcement items should be entered into ICIS-NPDES. For example, an inspection 

should be linked to all violations identified during the inspection, which in turn should be 

linked to any resulting enforcement action, penalty or compliance schedule. In addition, 

the information for an unpermitted facility which subsequently becomes a permittee 

could be linked in ICIS-NPDES. 

5. Violation Tracking

The automatic tracking function in ICIS-NPDES for DMR non-receipt and other 

violations (e.g., compliance schedule) will be “turned on” for both majors and 

non-majors. For non-major permits, this can be “turned off” during the transition period 

(described in Section G) and turned back on as DMR entry begins for those facilities, but 

no later than the final expected data entry date listed in that State's or Tribe’s transition 

plan (also described in Section F). This will allow EPA, States and Tribes to obtain the 

full benefit of automatic tracking of these violations and makes effective use of the 

resources allocated to data collection and data entry. In addition, such tracking may be 
ICIS-NPDES Policy Statement April 30, 2007 draft 9

very beneficial to automate NPDES reporting requirements such as the Annual 

Non-Compliance Report for NPDES Non-Majors required by 40 CFR §123.45 (c). 

6. Significant Industrial Users in Non-Pretreatment Cities

 

RIDE data on specific Significant Industrial Users (SIUs) are only expected in 

ICIS-NPDES if the pretreatment control authority is EPA, the State, the Territory, or the 

Tribal permitting authority, rather than a municipal treatment facility implementing an 

approved local pretreatment program. However, States, Territories, Tribes and Regions 

could use ICIS-NPDES to track additional SIUs, if so inclined. 

7. Stormwater Construction Sites 

For the large universe of stormwater construction sites, RIDE should be entered 

or transferred into ICIS-NPDES for States, Territories and Tribes if the State, Territory or 

Tribe issues the facility (whether Phase I or Phase II) a formal enforcement action, an 

administrative penalty order, or an informal enforcement action (but only if the informal 

enforcement action addresses significant non-compliance [SNC]4 under that construction 

site permit). In such circumstances, RIDE should be entered or transferred into 

ICIS-NPDES for the facility information and permit information for that site (if not 

already available in ICIS-NPDES), the enforcement action, penalty or compliance 

schedule, and all inspections and associated identified violations which precipitated that 

enforcement action. As indicated in Appendix 4, these enforcement actions, inspections, 

and all other RIDE for stormwater construction sites should begin to entered or 

transferred into ICIS-NPDES as they occur effective August 1, 2007, or within four 

months after migration to ICIS-NPDES. For all other stormwater construction sites, data 

from DMRs, associated limits and limit sets need not be entered into ICIS-NPDES. 

For EPA Regions, RIDE for all stormwater construction inspections performed by 

the Regions and all resulting enforcement actions by the Regions are expected to be 

entered into ICIS-NPDES and linked appropriately. In order to enter RIDE data into 

ICIS-NPDES, the facility information and permit information for that site will have to be 

entered into ICIS-NPDES by the Region (if such information is not already available in 

ICIS-NPDES). 

8. Satellite Collection Systems to Separate Sanitary Sewer Systems (SSSs); Other 

Unpermitted Facilities 

The ICIS 2.0 Users Guide (Permits section) states that: "Unpermitted facilities are 

records established in ICIS to allow for tracking of activities (e.g., inspections and 

 

4

 Significant non-compliance (SNC) for stormwater construction sites and which informal enforcement 

actions will address such SNC will be defined in the wet weather SNC guidance, currently under 

development by EPA. 
ICIS-NPDES Policy Statement April 30, 2007 draft 10

enforcement actions) that are associated with facilities that do not have [NPDES] permits. 

They may not contain narrative conditions, schedules, or limits." 

RIDE data entry is not expected for those portions of a State program that are 

"broader in scope" than the approved NPDES program (under 33 U.S.C. § 1342(b)). In 

general (except for SIUs in non-pretreatment cities), RIDE data are expected to be 

entered into ICIS-NPDES for unpermitted facilities only if the facility has been issued a 

formal enforcement action, an administrative penalty order, or an informal enforcement 

action (but only if the informal enforcement action addresses significant non-compliance, 

or if the facility should have a NPDES permit. In such situations, the facility RIDE and 

permit RIDE (if any) should be entered into ICIS-NPDES before the compliance 

monitoring, violation and enforcement information can be entered and appropriately 

linked. 

For example, for SSS satellite systems, RIDE should be entered if the SSS 

satellite system receives a formal enforcement action, an administrative penalty order, or 

an informal enforcement action (but only if the informal enforcement action addresses the 

SSS significant non-compliance [SNC]5

). In such circumstances, RIDE should be 

entered for the facility information and permit information (if any) for that site, the 

enforcement action, penalty or compliance schedule, and all inspections and identified 

violations which precipitated that enforcement action. 

F. Data Entry Targets for National Consistency 

EPA expects that there will be a transition period (described in Section G) as 

States become acclimated to ICIS-NPDES as a new information system. In addition, 

EPA recognizes that non-direct-user States, Territories and Tribes may need to take steps 

to adjust their own information systems to include all RIDE and then map to the 

appropriate ICIS-NPDES XML schema so that data from their data systems will transfer 

to ICIS-NPDES; such adjustments and mapping also should be addressed in transition 

plans. EPA will rely on ICIS-NPDES for direct user States, Tribes and Regions and will 

continue to rely on PCS information for non-direct-user States, Territories and Tribes 

until they have migrated to ICIS-NPDES. PCS will be shut down once all States, 

Territories and Tribes have been migrated to ICIS-NPDES. 

NPDES-authorized States, Territories or Tribes have the flexibility within the 

transition plan to identify a specific prioritization scheme for RIDE data entry or transfer 

by specific dates. Although NPDES-authorized States, Territories or Tribes have 

flexibility in the specifics of the transition plan, there are several national data targets 

which should also be incorporated into the transition plan. These national targets, set 

forth in Appendix 4, are intended to provide national consistency so that EPA can begin 

to use ICIS-NPDES for national analysis for certain data sets. 

 

5

 Significant non-compliance (SNC) for SSSs and which informal enforcement actions will address such 

SNC will be defined in the wet weather SNC guidance, currently under development by EPA. 
ICIS-NPDES Policy Statement April 30, 2007 draft 11

EPA has set national data targets based on permit type, program area and data 

family. These national targets are based on an approach similar to that developed by the 

Matrix Priority Workgroup, a subgroup of the Expanded Steering Committee, in June to 

August 2006. These national target dates apply to all States, Territories, Tribes and 

Regions, whether direct, hybrid or non-direct (batch) users of ICIS-NPDES, with the 

provision that the dates may be extended as necessary up to four months after a State, 

Territory, Tribe or Region migrates to ICIS-NPDES. 

1. Ensure ICIS-NPDES data entry or transfer of those RIDE for which WENDB 

equivalents existed in PCS

Existing WENDB elements are expected to be up-to-date when the permitting 

authority begins RIDE data entry or transfer into ICIS-NPDES. States, Territories, 

Tribes and Regions scheduled to migrate to ICIS-NPDES are encouraged to ensure that 

all WENDB data is complete and accurate in PCS before data migration occurs. 

Therefore, data entry or transfer into ICIS-NPDES for those RIDE for which WENDB 

equivalents existed in PCS is expected to be available in ICIS-NPDES very early in the 

transition period. 

2. Entry of Non-DMR Compliance Monitoring, Violations and Enforcement as They 

Occur

 With the exception of certain stormwater construction sites as discussed in 

Section E.8., data associated with non-DMR compliance monitoring (e.g., inspections), 

single event violations, enforcement actions, penalties, and compliance schedules are to 

be entered or otherwise made available into ICIS-NPDES as those events occur, and in 

accordance with the Data Entry Protocols (described in Section E.1.). Appropriate 

linkages should be made within ICIS-NPDES, as described in Section E.5. If there is 

compliance monitoring or enforcement activity at a facility without corresponding 

Facility or Permit Data in ICIS-NPDES, then that Facility and/or Permit information 

should be entered into ICIS-NPDES in order for compliance and enforcement events to 

be properly entered into the system. As indicated in Appendix 4, enforcement actions, 

inspections and violations are expected to be entered or transferred into ICIS-NPDES 

prospectively after August 1, 2007, or within four months after migration to 

ICIS-NPDES. 

3. Phase-In of Limits and DMRs for Non-Majors 

States, Territories, Tribes and EPA Regions may “phase-in” the data entry of 

DMRs (and associated limits and limit sets) for non-majors. Under this phase-in, the data 

entry or transmission of DMRs (also limits and limit sets) to ICIS-NPDES for non-majors 

should be prioritized to focus initially on those non-majors located in priority watersheds 

(impaired watersheds). Appendix 4 describes the national targets for DMR entry and 
ICIS-NPDES Policy Statement April 30, 2007 draft 12

availability in ICIS-NPDES for non-majors. These national data targets for DMR data 

entry and transfer for non-major facilities are based on the concept that the permitting 

authority may prioritize certain non-major facilities for DMR data entry, with DMR 

RIDE for the other non-majors awaiting the availability of NetDMR. For the first few 

years of implementation of this policy statement, EPA Headquarters will annually assist 

each State, Tribe and Region by providing a list of non-major facilities located in priority 

watersheds; this list could then be used for determining priorities for DMR (as well as 

other RIDE) data entry into ICIS-NPDES. 

4. Permit Data Not Yet Collected

 If there is permit RIDE data that a State or Tribe currently does not collect or have 

in its existing permit or permit application, availability of these particular data elements 

in ICIS-NPDES may be delayed until reissuance of the permit. For example, if a 

particular permit does not yet require the metadata associated with latitude and longitude 

for pipe locations, those particular RIDE for that permittee may be delayed until 

reissuance of the permit. All individual non-stormwater NPDES permits are issued on a 

five-year cycle; therefore, all permit RIDE should be complete within five years of 

issuance of this Policy Statement. 

G. Development and Implementation of Transition Plans 

Each NPDES-authorized State, Territory, Tribe or EPA Region should develop a 

transition plan which describes how and when RIDE data entry or transfer to 

ICIS-NPDES will occur (note: data transfer is not available to EPA Regions other than in 

the data migration from PCS to ICIS-NPDES). This transition plan should include an 

implementation schedule designed to result in RIDE data entry or transfer into 

ICIS-NPDES by the end of the transition period. The transition period applies primarily 

to those RIDE without WENDB equivalents in PCS. 

The approach taken to ensure such data entry or transfer into ICIS-NPDES may 

vary to some degree by State, Territory, Tribe or Region depending on the current status 

and projected availability of the data and resources. States, Territories, Tribes and 

Regions are encouraged to work with the existing RIDE Data Entry Estimate Model 

when developing their ICIS-NPDES transition plan to quantify and assess the resource 

implications for data entry of specific data types or program areas. 

 The national ICIS-NPDES data targets are described in Appendix 4. A template 

of a transition plan is included as Appendix 5. 

The schedule for submission of such recommended transition plans will vary 

based upon the type of ICIS-NPDES user (i.e., direct users, hybrid users and non-direct 

users) (see Appendix 4). Hybrid and non-direct (batch) users have been given four 

additional months to understand the ICIS-NPDES XML schemas as part of the process of 
ICIS-NPDES Policy Statement April 30, 2007 draft 13

developing their transition plans. The transition plan and milestone schedule for 

NPDES-authorized States and Tribes will be reviewed and approved by EPA Regions at 

the Division Director level (Enforcement and Water) within three months of submission 

of that plan by the State or Tribe to EPA. Similarly, transition plans and milestone 

schedules for non-authorized States, Territories and Tribes will be developed by EPA 

Regions, with review and approval by EPA Headquarters within three months of 

Regional submission. These activities are included in the ICIS-NPDES roles and 

responsibilities table in Appendix 6. 

EPA Regions should seek to incorporate the activities and schedule in the 

approved transition plan into subsequent State-EPA or Tribe-EPA management 

agreements, performance partnership grants (PPGs) or performance partnership 

agreements (PPAs), when these agreements are due for renewal, throughout the transition 

period. At the end of the transition period, when States and Tribes have fully 

implemented RIDE entry, the State-EPA or Tribe-EPA management agreement, PPG or 

PPA should be modified, when these agreements are due for renewal, to reflect the need 

for continued timely, accurate and complete entry and availability of RIDE data. 

H. Additional Operational Activities 

To ensure a smooth and effective operation of ICIS-NPDES, permitting 

authorities should undertake a variety of additional activities, including those listed 

below: 

1. Participate in ICIS-NPDES Governance: A governance structure with 

Headquarters, Regional, and State representatives will be formed for making 

decisions regarding ICIS Release 2.0 and subsequent releases. The governance 

structure will institute a standard communication and decision-making process for 

system enhancements and system issues. 

2. Establish and Maintain Roles and Responsibilities: Defining and maintaining 

clear roles, responsibilities and activities is essential to managing a decentralized 

national data base such as ICIS-NPDES. Appendix 6 identifies these roles and 

responsibilities for States, Territories, Tribes, EPA Regions, and for various 

offices at EPA Headquarters. 

3. Monitor Data Quality: As the data is migrated to the new system and as users 

become familiar with ICIS-NPDES, permitting authorities should pay particular 

attention to reviewing data reports and results to ensure that the data is entered 

correctly and reporting is accurate and timely. As ICIS-NPDES problems arise, 

they should be reported to user support; user support, in turn, will elevate 

problems to the governance structure as appropriate. 

 

As described earlier in this document, timely, accurate, complete and consistent 

reporting is the foundation for effective program management and reliable public 

access to data; therefore, data quality will remain an area of focus for ICIS-
ICIS-NPDES Policy Statement April 30, 2007 draft 14

NPDES implementation. As States and Tribes move beyond transitioning into 

ICIS-NPDES and the system becomes the established national NPDES data base 

of record, careful attention should be paid by all parties to data quality, with 

procedures and checklists in place to ensure that RIDE data is entered within set 

timelines and is entered completely and accurately. 

 

I. Policy Revision and Relationship to Other Policies 

 The NPDES program will continue to evolve. States and EPA will need to work 

together to ensure that program guidance reflects program and policy changes. As new 

guidance documents are developed or as existing guidance is modified, close 

coordination between these documents and ICIS-NPDES will be needed to determine 

whether and how ICIS-NPDES can support these changes. For example, EPA is 

currently working with States on finalizing various guidance documents and policies that 

may be useful to the NPDES-authorized agencies; such guidance documents and policies 

include the wet weather SNC guidance document, the Compliance Monitoring Strategy, 

the ICIS-NPDES Data Element Dictionary, and the Single Event Violation Data Entry 

Guide. Changes needed to ICIS-NPDES to accommodate new regulations, guidance 

documents, or policy will be directed to the established ICIS-NPDES governance 

structure. 

 EPA expects to review on a periodic basis (of approximately five years) how well 

this ICIS-NPDES Policy Statement is meeting the business needs of the NPDES 

program. EPA anticipates that the first such review will occur two to three years after 

issuance of this Policy Statement to assess the success of the transition plans and the 

experience of working with the batch transfer process. 
April 30, 2007 DRAFT

Biosolids Biosolids CAFOs CAFOs CSO/SSOs CSO/SSOs Pretreatment Pretreatment 

APPENDIX 1: RIDE by Data Area and Program Are

Core Data Requirements # of Data 

Elements

Facility 25Permitting 82Compliance Monitoring 33Enforcement 20

Total 160

(incl. 22 conditional)

Core Data Requirements # of Data 

Elements

Facility 25Permitting 82Compliance Monitoring 33Enforcement 20

Total 160

(incl. 22 conditional)

17

Additional 125 Special Regulatory Elements

Total RIDE Elements = 285 (including 43 condition

49

(incl. 7 conditional)

33

(incl. 2 conditional)

19 

(incl. 12 conditional)
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

Facility Basic Info Facility Type of Ownership TYPO

The code/ description identifying the type of facility (e.g., State Government, Municipal or Water Distric, Federal Facility). This data element is used by the system to populate the Permit Facility Type data element (i.e., POTW, Non-POTW, Federal).

No Yes Yes 

Facility Basic Info Facility Site Name RNAM The name of the facility. Yes Yes Yes 

Facility Basic Info Address RST1 The address of the physical facility location. Yes Yes Yes Facility Basic Info City RCTY

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.

Yes Yes Yes 

Facility Basic Info State RSTT The USPS abbreviation that represents the state or state equivalent for the US and Canada. Yes Yes Yes Facility Basic Info Zip Code RZIP

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.

Yes Yes Yes 

Facility Basic Info Tribal Land HQ01 The Bureau of Indian Affairs code for every unit of land within Indian Country. No Yes Yes 

Note: Highlighted rows indicate RIDE that are conditionally-required and only need to be entered under certain circumstances, as described in the "Sytem-Required" column and the "Comment" column. Some of these fpresence/ absence of another RIDE; others only need to be entered rarely.

RIDE Data Element Description PCS equivalent (if available)1 System Required Sub-Area 2

FACILITY DATA ELEMENTS1. This column provides the PCS acronyms that correspond to each RIDE element. If blank, there is no known equivalent. Also, the PCS acronyms represent WENDB elements required in PCS, unless otherwise noted.

3. From the ICIS 2.0 Users Guide (Permits section): "Unpermitted facilities are records established in ICIS to allow for tracking of activities (e.g., inspections and enforcement actions) that are associated with facilities th

may not contain narrative conditions, schedules, or limits." Data entry requirements do not apply to those portions of a State program that are "broader in scope" than the approved NPDES program (under 33 U.S.C. § 1preatreatment cities, the facility, compliance monitoring, and enforcement data for unpermitted facilities is only RIDE if there has been a formal enforcement action, an administrative penalty order or an informal enforce

SIUs in non-pretreatment cities, RIDE is expected. Examples of unpermitted facilities include SSS satellite systems and AFOs that, after inspection, are determined to be CAFOs requiring a NPDES permit.2. From the ICIS-NPDES Detailed Design Document (page 4-2): “Data elements are marked as system required when entry of the data element is required by ICIS-NPDES in order for a user to add a particular record inelements are not entered, ICIS-NPDES will reject the transaction."Area Data Element Name 

Permit Type in ICIS-NPDES

2a-1
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Facility Lat/Long Longitude FLON

The measure of the angular distance on a meridian east or west of the prime meridian for a Facility Interest. Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees.

No Yes Yes 

Facility Lat/Long Latitude FLAT

The measure of the angular distance on a meridian north or south of the equator for a Facility Interest. Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees.

No Yes Yes 

Facility Lat/Long Facility Source Map Scale Number FLLS The number that represents the proportional distance on the ground for one unit of measure on the map or photo. No Yes Yes Facility Lat/Long Horizontal Accuracy Measure FLLC The measure of the accuracy (in meters) of the latitude and longitude coordinates. No Yes Yes Facility Lat/Long Horizontal Collection Method FLLM The text that describes the method used to determine the latitude and longitude coordinates for a point on the earth. No Yes Yes Facility Lat/Long Horizontal Reference Datum FLLT The code/ description that represents the reference datum used in determining latitude and longitude coordinates. No Yes Yes Facility Lat/Long Reference Point FLLD The code/ description for the place for which geographic coordinates were established. No Yes Yes Facility Non-Gov Contacts Affiliation Type The way that the contact is affiliated with the Facility (e.g., Owner) No Yes Yes Facility Non-Gov Contacts First Name The given name of an individual. No Yes Yes Facility Non-Gov Contacts Last Name The surname of an individual. No Yes Yes Facility Non-Gov Contacts Individual Title The title held by a person in an organization. No Yes Yes Facility Non-Gov Contacts Organization MNAM, ONAM The legal, formal name of an organization that is affiliated with the facility site. No Yes Yes Facility Non-Gov Address Street Address MST1, OST1 The address that describes the physical location of a building or event, including urban-style street address or rural address. No Yes Yes 

2a-2
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Facility Non-Gov Address Affiliation Type The way that the contact or address is affiliated with the Facility (e.g., Owner) No Yes Yes Facility Non-Gov Address Organization Formal Name MNAM, ONAM The legal, formal name of an organization that is affiliated with the facility site. No Yes Yes Facility Non-Gov Address City MCTY, OCTY The name of the city in which the address exists. No Yes Yes Facility Non-Gov Address State MSTT, OSTT The U.S. Postal Service abbreviation that represents the state or state equivalent for the U.S. No Yes Yes Facility Non-Gov Address Zip Code MZIP, OZIP

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.

No Yes Yes 

Permit Basic Info NPDES ID NPID This is the NPDES permit number. Yes Yes Yes 

Permit Basic Info Master General Permit Number NPID The unique identifier of the master general permit which is linked to a General Permit Covered Facility.

Yes, when adding 

a General Permit 

Covered Facility 

permit. 

Permit Basic Info Permit Type PTYP The unique code/ description identifying the type of permit. Yes Yes Yes 

Permit Basic Info Issue Date PTEV, PTAC (PERD) This is the date the permit was issued.

Not for new 

permits, but for 

compliance 

tracking or 

reissuance

Yes Yes 

Permit Basic Info Effective Date PTEV, PTAC (PEFD) This is the date on which the permit is effective.

Not for new 

permits, but for 

compliance 

tracking or 

reissuance

Yes Yes 

PERMIT DATA ELEMENTS

2a-3
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Permit Basic Info Expiration Date PTEV, PTAC (PERE) This is the date the permit will expire.

Not for new 

permits, but for 

compliance 

tracking or 

reissuance

Yes Yes 

Permit Basic Info Termination Date IADT This is the date the permit was terminated. No Yes Yes 

Permit Basic Info Major/Minor Rating Code MRAT

This is the numeric total of ranking points assigned to nonPOTW facilities and used to delineate them as a major or minor facility. The numeric value entered for this data element comes from the total score assigned to the facility on the NPDES Permit Ranking Work Sheet.

No Yes 

Permit Basic Info Total App. Design Flow FLOW This is the flow that a permitted facility was designed to accommodate, in MGD. No Yes Permit Basic Info Total App. Actual Avg. Flow FLOW This is the actual flow that a permitted facility accomodated based on the application, in MGD. No Yes 

Permit Basic Info

Complete Application/NOI Received Date

PTEV (P2099) (not WENDB), PTAC

This is the date on which the complete application for a NPDES permit was received. No Yes 

Permit Basic Info Application/NOI Received Date PTEV, PTAC (APRD) This is the date on which the application for a NPDES permit was received. No Yes Permit Basic Info Permit Status

This is a code/ description that indicates whether the permit is Effective, Expired, Administratively Continued, Pending,Not Needed, Retired, or Terminated. 

Yes Yes Yes 

Permit Basic Info General Permit Industrial Category GPCT This code/ description that identifies the industrial category of a general permit. Yes Yes

Permit Basic Info Issuing Organization Type EPST This is the type of organization issuing or granting a permit. Yes Yes Yes Permit Basic Info DMR Non-Receipt Turns Non-Receipt tracking on/off for Minors. Always on for Majors. Defaulted initially to On. Yes Yes 

Permit Basic Info RNC Turns RNC tracking on/off for Minors. Always on for Majors. Defaulted initially to On. Yes Yes Permit Basic Info Applicable Effluent Limit Guideline CFRC The effluent guideline that applies to the permit. No Yes Yes 

2a-4
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Permit Basic Info Compliance Tracking Status IACC 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. Yes Yes 

Permit Basic Info Compliance Tracking Status Start Date IADT 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. Yes Yes Permit Basic Info RNC Status Quarter CYMS, PYMS The quarter of the Permit RNC status. No Yes 

Permit Basic Info RNC Status Year CYMS, PYMS The year of the Permit RNC status. No Yes Permit Basic Info RNC Status (Manual) CYMS, PYMS

The status of reportable noncompliance as it was entered by the user before the official QNCR for the RNC quarter for the permit.

No Yes 

Permit Basic Info SIC Codes SIC2

The four digit Standard Industrial Classification (SIC) code/ description that represents the economic activity of a company.

No Yes Yes Yes 

Permit Basic Info Associated NPDES Permit SLID This is the NPDES number of the associated permits. No Yes Permit Basic Info NAICS Codes The six digit code/ description that represents a subdivision of an industry that accomodates user needs in the US. No Yes Yes Yes Permit Permittee Street Address RST1 The address that describes the physical location of the permittee. Yes Yes 

Permit Permittee Organization Formal Name NAM1 The legal, formal name of an organization that is affiliated with the facility site. Yes Yes Permit Permittee Zip Code RZIP

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.

Yes Yes 

Permit Permittee City RCTY The name of the city, town, or village where the mail is delivered. Yes Yes 

2a-5
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Permit Permittee State RSTT The U.S. Postal Service abbreviation that represents the state or state equivalent for the U.S. Yes Yes 

Permit Biosolids Annual Dry Sludge Production SLPV The amount of sludge a facility produces in DMT/year on a dry weight basis. No Yes 

Permit Biosolids

Amount EQ Product Distribute and Marketed 

The amount (dry metric tons) of EQ product distributed. No Yes 

Permit Biosolids Amount Land Applied The amount (dry metric tons) of biosolids land applied. No Yes Permit Biosolids Amount Incinerated The amount (dry metric tons) of biosolids incinerated. No Yes Permit Biosolids Amount Codisposed in an MSW Landfill The amount of dry metric tons co-disposed in a MSW landfill. No Yes Permit Biosolids Amount Surface Disposal The amount (dry metric tons) of biosolids used for surface disposal. No Yes Permit Biosolids Amount Managed Other Methods The amount (dry metric tons) of biosolids managed using methods not previously described. No Yes Permit Biosolids Biosolids End Use Disposal Type SLDG This is the code identifying the type of end use disposal. No Yes Permit CAFO Designation Reason

 If the facility was designated, indicate the reason the facility was designated, such as the amount of waste reaching waters, location, slope, rainfall, etc.

Yes, if "yes" is 

entered for "Is the 

Animal Facility a 

CAFO?" and 

"small" is entered 

for CAFO 

classification

Yes 

Permit CAFO CAFO Designation Date If the facility received a permit as a result of being designated, indicate the date on which the facility is designated as a CAFO. No Yes Permit CAFO Solid Manure or Litter Generated The total amount of manure in tons generated annually by the facility. No Yes Permit CAFO Solid Manure or Litter Transferred The number of tons of manure or litter produced by the CAFO that will be transferred to other persons. No Yes Permit CAFO Liquid Manure or Wastewater Generated The total amount of manure in gallons generated annually by the facility. No Yes Permit CAFO Liquid Manure or Wastewater Transferred The total amount of manure in gallons produced by the CAFO that will be transferred to other persons. No Yes 

2a-6
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Permit CAFO NMP Developed Date The date that an NMP was developed by the facility. No Yes Permit CAFO CAFO Classification

The unique code/ description that identifies the how the facility was classified for a "Concentrated Animal Feeding Operation?" Options are Large, Medium and Small (Designation).

No Yes 

Permit CAFO Animal: Type The unique code/ description that identifies the operation’s applicable animal sector(s). Yes Yes Permit CAFO Animal: Other

The free-form text field to describe the operation's applicable animal sector if Other is selected for Animal Type Code.

No Yes 

Permit CAFO Total Number The total number of each type of livestock at the facility. No Yes Permit CAFO Containment: Type The unique code/ description for the type of containment used by the operation. Yes Yes Permit CAFO Containment: Total Capacity The total capacity, in gallons, of the containment structure. No Yes Permit CAFO Containment: Other The free-form text field to describe the type of containment if Other is selected for Containment Type Code. No Yes Permit CAFO Storage: Type The unique code/ description that describes the type of storage used by the CAFO. Yes Yes Permit CAFO Storage: Other

The free-form text field to describe the type of storage used by the operation if the Other code is selected for storage type code attribute.

No Yes 

Permit CAFO Days of Storage This is how many days of storage there were for each storage type selected. No Yes Permit CAFO Storage Total Capacity Measure This is the total capacity, in tons or gallons, of the storage structure. No Yes Permit Storm Water State Water Body Name RWAT? This identifies the name(s) of the receiving water into which the storm water flows directly. No Yes Permit Storm Water - Construction NOT Terminate Date This is the date on which the facility’’s coverage was terminated.

One data element 

must be entered 

in this section to 

save the record

Permit Storm Water - Construction Entire Project Size This code describes the plan size of the project (<1 acre, 1- 5 acres, or >5 acres). At least 1 element is required to save this component Yes Permit Storm Water - Industrial NOT Terminate Date This is the date on which the coverage was terminated. No 

2a-7
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Permit Storm Water - Industrial No Exposure Authorized Date This is the date on which the No Exposure Waiver was authorized. No Permit Storm Water - MS4 MS4 Permit Class This is the code/ description that identifies the regulatory basis for MS4 permit (small/medium/large) Yes Yes Permit Storm Water - MS4 Receiving MS4 Name This is the name of the receiving MS4(s). No Yes Permit CSO CSS Population Served This is the population served by the combined sewer system (individuals or households). Yes Yes Permit CSO Percent of Collection System Combined This is the percentage of the total collection system that is combined. Yes Yes Permit CSO Name of CSS Satellite Collection System This is the name of each satellite collection system providing flow to the permittee. No Yes Permit CSO

Permit ID of CSS Satellite Collection System

This is the permit ID of each satellite collection system providing flow to the permittee. No Yes 

Permit Pretreatment Pretreatment Program Required Indicator PRET The code/ description indicating if the permitted municipality is required to develop a pretreatment program. Yes Yes Permit Pretreatment Pretreatment Program Approved Date The date the pretreatment program is approved.

Yes, if 

Pretreatment 

Program 

Required 

Indicator is 

"Approved".

Yes 

Permit Pretreatment Control Authority NPDES ID CAID The permit ID of the POTW's or IU's control authority.

Yes, if 

PRetreatment 

Program 

Required 

Indicator is 

"Covered".

Yes 

Permit POTW SSCS Population Served This is the population served by the sanitary sewer collection system (individuals or households). This data element applies to all POTWs. Yes Yes 

2a-8
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Permit POTW Length of SSCS This is the number of miles of pipe in the sanitary sewer collection system. Yes Yes Narr. Cond/Permit Schedule

Narr.Cond/ Schedule Description The unique code/ description that identifies the type of narrative condition. Yes Yes Yes 

Narr. Cond/Permit Schedule

Narr.Cond/ Schedule

Narrative Condition Number

CSCH, VCSN, EVSN

This identifies a narrative condition and its elements uniquely for a permit. Yes Yes Yes 

Narr. Cond/Permit Schedule Event Schedule Date DTSC, CVDT The date on which a schedule event is due to be completed and against which compliance will be measured. Yes Yes Yes 

Narr. Cond/Permit Schedule Event Actual Date DTAC The date on which the permittee achieved the schedule event. No Yes 

Narr. Cond/Permit Schedule Event Report Received Date DTRC

The date on which the regulatory authority receives a report(generally a letter) from the permittee indicating that a Schedule Event was completed (e.g., Start Construction) or the required report was enclosed.

No Yes 

Narr. Cond/Permit Schedule Event Event EVNT, CVEV, EVEV The code/ description indicating the particular event with which the permittee is scheduled to comply. Yes Yes Yes 

Permitted Feature Basic Info Application Design Flow (MGD) The flow that a permitted feature was designed to accommodate, in MGD. No Yes 

Permitted Feature Basic Info Application Actual Average Flow (MGD) The flow that a permitted feature actually had at the time of application, in MGD. No Yes Permitted Feature Basic Info Permitted Feature ID DSCH, PLDS The identifier assigned for each location at which conditions are being applied. Yes Yes 

Permitted Feature Basic Info Master General Category ID DSCH The identifier assigned for each location at which conditions are being applied. Yes Yes Permitted Feature Basic Info Type OUTT The code/ description indicating the type of permitted feature (e.g. External Outfall, Sum). Yes Yes Yes 

Permitted Feature Lat/Long Latitude PLAT

The measure of the angular distance on a meridian north or south of the equator for a Permitted Feature; stored in decimal degrees.

No Yes 

Permitted Feature Lat/Long Longitude PLON

The measure of the angular distance on a meridian east or west of the prime meridian for a Permitted Feature; stored in decimal degrees.

No Yes 

Permitted FeatureNarrative Conditions/ Permit Schedules

2a-9
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Permitted Feature Lat/Long Horizontal Accuracy Measure PLLC The measure of the accuracy (in meters) of the latitude and longitude coordinates. No Yes Permitted Feature Lat/Long Reference Point PLLD The code/ description for the place for which geographic coordinates were established. No Yes Permitted Feature Lat/Long Source Map Scale Number PLLS The number that represents the proportional distance on the ground for one unit of measure on the map or photo. No Yes Permitted Feature Lat/Long Horizontal Collection Method PLLM The code/ description that represents the method used to determine the latitude and longitude coordinates for a point on the earth. No Yes Permitted Feature Lat/Long Horizontal Reference Datum PLLT The code/ description that represents the reference datum used in determining latitude and longitude coordinates. No Yes Limit Set Basic Info Limit Set Designator DRID, PLRD The alphanumeric field that is used to designate a particular grouping of parameters within a limit set. Yes Yes Yes 

Limit Set Basic Info Type The unique code/ description identifying the type of limit set (i.e. Scheduled, Unscheduled). Yes Yes Yes 

Limit Set Basic Info Default Months Limit Set Applies ALLP The default months that the limit set applies. Defaults to all 12 months. Yes Yes Yes 

Limit Set Basic Info Initial Monitoring Date STRP

The date on which monitoring starts for the first monitoring period for the limit set; this date will be blank for Unscheduled Limit Sets.

Yes, except for 

unscheduled limit 

sets

Yes 

Limit Set Basic Info Initial DMR Due Date STSS, STSU

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.

Yes, except for 

unscheduled limit 

sets

Yes 

Limit Set Basic Info Number of Report Units NRPU

The number of months in the monitoring periods for the DMRs for the limit set (e.g., monthly = 1, semi-annually = 6, quarterly = 3).

Yes Yes 

Limit Set

2a-10
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Limit Set Basic Info Number of Submission Units NSUS, NSUN

The attribute stores the number of months for submitting the DMRs for the limit set (e.g., monthly = 1, semiannually = 6, quarterly = 3); this data element will be blank for Unscheduled Limit Sets.

Yes, except for 

unscheduled limit 

sets

Yes 

Limit Set Basic Info Compliance Tracking Status Start Date PIDT The date that the Limit Set Status started. Yes Yes 

Limit Set Basic Info Status PIAC

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.

Yes Yes 

Limit Basic Info Monitoring Location MLOC The code/ description of the monitoring location at which sampling should occur for a limit parameter. Yes Yes Yes 

Limit Basic Info Season Number SEAN, ESEA

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.

Yes Yes Yes 

Limit Basic Info Start Date ELSD, FLSD, ILSD, MLSD The date on which a limit starts being in effect for a particular parameter in a limit set. Yes Yes Yes Limit Basic Info End Date ELED, FLED, ILED, MLED The date on which a limit stops being in effect for a particular parameter in a limit set. Yes Yes Yes Limit Basic Info Change of Limit Status Indicator COLS The code/ description that describes circumstances affecting limits, such as formal enforcement actions or permit modifications. No Yes Yes 

Limit Basic Info Stay Type CONP

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.

Yes Yes 

Limit Basic Info Stay Start Date PTEV (P7099), PTAC The date on which a limit stay begins. Yes, if Stay Type is entered Yes 

Limit Basic Info Stay End Date The date on which a limit stay is lifted. No Yes 

Limit

2a-11
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Limit Basic Info Reason for Stay The text that represents the reason a stay was applied to a limit. Yes, if Stay Type is entered Yes 

Limit Basic Info Stay Limit Value

MCMX, MCAV, MCMN, MQMX, MQAV

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.

Yes, when Stay 

Type is "Z". Yes 

Limit Basic Info Limit Type OUTT

The code that indicates whether a limit is an enforceable or an alert limit (e.g., action level, benchmark) that does not receive effluent violations.

Yes Yes 

Limit Basic Info 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.

Yes Yes 

Limit Basic Info Final Order ID PLFN

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.

Yes Yes 

Limit Basic Info Eligible for Burden Reduction The indication of whether a limit parameter is eligible for monitoring burden reduction. Yes Yes Limit Basic Info Modification Effective Date PTEV, PTAC (PMDD) The effective date of the permit modification that created this limit. Yes Yes Yes 

Limit Basic Info Modification Type The type of permit modification that created this limit (e.g. major, minor, permit authorized change). Yes Yes Yes Limit Basic Info Parameter PRAM The unique code/ description identifying the parameter being limited and/or monitored. Yes Yes Yes Limit Basic Info Months ALLS (not WENDB) The months that the limit applies. Defaults to limit set months. Yes Yes Yes Limit Basic Info Value Type

LCMX, LCMN, LCAV, LQMX, LQAV

The indication of the limit value type (e.g., Quantity 1, Concentration 2). Yes Yes Yes 

Limit Basic Info Quantity Units / Concentration Units LCUC, LQUC The code/ description representing the unit of measure applicable to quantity or concentration limits as entered by the user. No, except to save limit value. Yes Yes 

2a-12
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Limit Basic Info Statistical Base Code

LCXS, LCAS, LCMS, LQXS, LQAS

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) CHECK DATA STANDARD.

No, except to 

save limit value. Yes Yes 

Limit Basic Info Optional Monitoring Flag

LCMX/ LCMN/ LCAV/ LQMX/ LQAV (OPMON)

The flag allowing users to indicate that monitoring is optional but not required (i.e., effluent violation generation will be suppressed for optional columns).

Yes Yes Yes 

Limit Basic Info Qualifier The unique code identifying the limit value operator (e.g. <= ,<, ). Yes Yes Yes Limit Basic Info Value

LCMX, LCMN, LCAV, LQMX, LQAV

The actual limit value number from the Permit or Enforcement Action Final Order. No Yes Yes 

Compliance Monitoring Activity Basic Info

Compliance Monitoring Activity Actual End Date

DTIN, DTIA The actual date on which the Compliance Monitoring Activity ended. Yes, if there is no planned end date Yes Yes 

Compliance Monitoring Activity Basic Info

Compliance Monitoring Activity Planned End Date

SIDT (not WENDB)

The planned date for the Compliance Monitoring Activity to end.

Yes, if there is no 

actual end date Yes Yes 

Compliance Monitoring Activity Basic Info State The US Postal Service abbreviation that represents that state or state equivalent for the U.S. Yes Yes Yes Compliance Monitoring Activity Basic Info Compliance Activity Type The unique code/ description that identifies a type of compliance event or enforcement action. Yes Yes Yes Compliance Monitoring Activity Basic Info Compliance Monitoring Type TYPI The code/ description indicating the type of compliance monitoring activity taken by a regulatory Agency. Yes Yes Yes 

Compliance Monitoring Activity Basic Info Bio-Monitoring Inspection Method

The unique code that identifies the type of biomonitoring inspection method. This data element supplements the Compliance Monitoring Category and Compliance Monitoring Type Inspection Type recorded for all inspections.

Yes, if "biomonitoring" is 

entered as 

Compliance 

Monitoring Type

Yes Yes 

Compliance Monitoring Activity Basic Info Compliance Monitoring Category TYPI The unique code/ description identifying the compliance monitoring or inspection category code/ description. Yes Yes Yes 

Compliance Monitoring Activity Basic Info Compliance Monitoring Action Reason The unique code that identifies the purpose of an activity. Yes Yes Yes 

COMPLIANCE MONITORING DATA E

2a-13
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Compliance Monitoring Activity Basic Info

Was this a State, Federal or Joint (State/Federal) Inspection?

INSP The flag indicating if the inspection is a joint inspection of federal and state. No Yes Yes 

Compliance Monitoring Activity Basic Info Compliance Monitoring Agency Type INSP Whether it's an EPA or State Inspection Yes Yes Yes 

Compliance Monitoring Activity Basic Info Law Sections Violated TYPI The unique identifier for the Section(s) of law violated and cited in the activity. No Yes Yes 

Compliance Monitoring Activity CAFO Designation Reason

 If the facility was designated, indicate the reason the facility was designated, such as the amount of waste reaching waters, location, slope, rainfall, etc.

Yes, if "yes" is 

entered for "Is the 

Animal Facility a 

CAFO?" and 

"small" is entered 

for CAFO 

classification

Yes 

Compliance Monitoring Activity CAFO Animal: Type The unique code/ description that identifies the operation’’s applicable animal sector(s). No Yes Compliance Monitoring Activity CAFO Animal: Other (Please specify) The free-form text field to describe the CAFO's applicable animal sector if Other is selected for Animal Type. No Yes Compliance Monitoring Activity CAFO Animal: Total Number The total number of each type of livestock at the facility. No Yes Compliance Monitoring Activity CAFO Containment: Type The unique code/ description for the type of containment used by the operation. No Yes Compliance Monitoring Activity CAFO Containment: Total Capacity The total capacity, in gallons, of the containment structure. No Yes Compliance Monitoring Activity CAFO Containment: Other The free-form text field to describe the type of containment if Other is selected for Containment Type. No Yes Compliance Monitoring Activity CAFO CAFO Classification

The unique code/ description that identifies the how the facility was classified for a "Concentrated Animal Feeding Operation?" Options are Large, Medium and Small (Designation).

No Yes 

Compliance Monitoring Activity CAFO CAFO Designation Date The date on which the facility is designated as a Concentrated Animal Feeding Operation (CAFO). No Yes Compliance Monitoring Activity CAFO Solid Manure or Litter Generated The total amount of manure in tons generated annually by the facility. No Yes 

2a-14
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Compliance Monitoring Activity CAFO Solid Manure or Litter Transferred The number of tons of manure or litter produced by the CAFO that will be transferred to other persons. No Yes Compliance Monitoring Activity CAFO Liquid Manure or Wastewater Generated The total amount of manure in gallons generated annually by the facility. No Yes Compliance Monitoring Activity CAFO Liquid Manure or Wastewater Transferred The number of gallons of manure or litter produced by the CAFO that will be transferred to other persons. No Yes Compliance Monitoring Activity CAFO NMP Developed Date The date that an NMP was developed by the facility. No Yes Compliance Monitoring Activity CAFO NMP Last Updated Date The date that the NMP was last updated by the facility. No Yes Compliance Monitoring Activity CAFO Is the Animal Facility Type a CAFO? The flag to indicate if the facility is classified as a CAFO or not. No Yes Compliance Monitoring Activity CAFO Storage: Type The unique code/ description that describes the type of storage used by the operation. No Yes Compliance Monitoring Activity CAFO Storage: Other

The free-form text field to describe the type of storage used by the operation if the Other code is selected for storage type code attribute.

No Yes 

Compliance Monitoring Activity CAFO Days of Storage The number of days of storage there were for each storage type selected. No Yes Compliance Monitoring Activity CAFO Storage Total Capacity Measure The total capacity, in tons or gallons, of the storage structure. No Yes Compliance Monitoring Activity CSO Permitted Feature Identifier The unique identifier for the permitted feature number entered by the user for the CSO.

Yes, if CSO Overflow Location Street Address or Lat/long info is not entered

Yes Yes 

Compliance Monitoring Activity CSO Location Street Address The street address location of the overflow.

Yes, if Permitted Feature Identifier or Lat/long info is not entered

Yes Yes 

Compliance Monitoring Activity CSO Longitude

The measure of the angular distance on a meridian east or west of the prime. Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees.

Yes, if CSO Overflow Location Street Address or Permitted Feature Identifier is not entered

Yes Yes 

2a-15
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Compliance Monitoring Activity CSO Latitude

The measure of the angular distance on a meridian north or south of the equator. Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees.

Yes, if CSO Overflow Location Street Address or Permitted Feature Identifier is not entered

Yes Yes 

Compliance Monitoring Activity CSO CSO Overflow Event Date The date of the actual CSO overflow event. Yes Yes Yes Compliance Monitoring Activity Pretreatment SIUs SIUS The total number of SIUs.

Yes, if any 

compliance 

monitoring SIU 

information is 

entered.

Yes

Compliance Monitoring Activity Pretreatment SIUs Without Control Mechanism NOCM The number of SIUs for which a current control mechanism is required but not yet issued or has expired, as observed during the program audit or PCI. No Yes Compliance Monitoring Activity Pretreatment SIUs Not Inspected NOIN The number of SIUs not inspected within the reporting year, as observed during the program audit or PCI. No YesCompliance Monitoring Activity Pretreatment SIUs Not Sampled NINF The number of SIUs not sampled within the reporting year, as observed during the program audit or PCI. No YesCompliance Monitoring Activity Pretreatment SIUs in SNC with Pretreatment Standards SNPS (not WENDB), PSNC The significant industrial users in SNC with pretreatment standards within the reporting year, observed during the program audit or PCI. No Yes Compliance Monitoring Activity Pretreatment

SIUs in SNC with Reporting Requirements

RSNC (not WENDB), PSNC

The significant industrial users in SNC with reporting requirements within the reporting year, as observed during the program audit or PCI.

No Yes

Compliance Monitoring Activity Pretreatment CIUs CIUS The total number of CIUs. No YesCompliance Monitoring Activity Pretreatment Pass-Through/ Interference Indicator PASS, INTF (not WENDB) The flag indicating if there have been any incidents of pass- through or interference at the POTW within the reporting year, as observed during the program audit or PCI. No Yes Compliance Monitoring Activity SSO Location Street Address The street address location of the overflow event. Yes, if Lat/long info is not entered Yes Yes Compliance Monitoring Activity SSO Longitude

The measure of the angular distance on a meridian east or west of the prime. Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees.

Yes, if Location 

Street Address is not 

entered

Yes Yes 

2a-16
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Compliance Monitoring Activity SSO Latitude

The measure of the angular distance on a meridian north or south of the equator. Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees.

Yes, if Location 

Street Address is not 

entered

Yes Yes 

Compliance Monitoring Activity SSO SSO Event Date The date for which the SSO event is being reported. Yes Yes Yes DMR Basic Info Permitted Feature VDSC, EVDS The identifier assigned for each location at which conditions are being applied. Yes Yes DMR Basic Info Limit Set VDRD, EVRD The unique identifier tying the DMR form to its Limit Set record. Yes Yes DMR Basic Info Parameter Code VPRM, EVPR The unique code/ description identifying the parameter reported on the DMR. Yes Yes DMR Basic Info Monitoring Location VMLO, EVML The code/ description of the monitoring location at which the sampling occurred for a DMR parameter. Yes Yes DMR Basic Info Monitoring Period End Date MVDT The date that the monitoring period for the values covered by this DMR form ends. Yes Yes DMR Basic Info NODI NODI

The unique code/ description that indicates the reason that “No Discharge” or “No Data” was reported in place of the DMR value.

No Yes 

DMR Basic Info Value

MCMX, MCAV, MCMN, MQMX, MQAV

The DMR value number reported on the DMR form. No Yes 

DMR Basic Info Concentration Units/ Quantity Units RCUN, RUNT (not WENDB) The code/ description representing the unit of measure applicable to quantity or concentration limits and measurements as entered by the user on the DMR form. No Yes DMR Basic Info Value Received Date DMRR (not WENDB) The date the DMR value was received by the regulatory authority. No Yes DMR Basic Info Value Type

MCMX, MCAV, MCMN, MQMX, MQAV

The unique code/ description identifying a DMR value type (i.e. Quantity 1, Quantity 2, Concentration 1, Concentration 2, Concentration 3).

Yes Yes 

DMR Basic Info Qualifier

MCMX, MCAV, MCMN, MQMX, MQAV

The unique code identifying the DMR value operator (e.g., <, T, >, E, =). It defaults to "=". Yes Yes 

DMR

2a-17
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

DMR Biosolids - Incinerator

Compliance with National Emission Standard for Beryllium in 40 Code of Federal Regulations (CFR) Part 61

The flag indicating whether the facility is in compliance with the National Emission Standard for Beryllium in 40 CFR Part 61.

No Yes 

DMR Biosolids - Incinerator

Compliance with National Emission Standard for Mercury in 40 CFR Part 61

The flag indicating whether the facility is in compliance with the National Emission Standard for Mercury in 40 CFR Part 61.

No Yes 

DMR Biosolids - Land Application Site Pollutant Table(s) Met The code/ description identifiying the pollutant table in the biosolids regulations (i.e. 1-4) that was met by the facility for land application on this DMR. No Yes DMR Biosolids - Land Application Site Does facility certify pathogen reduction for land application? The flag indicating if the facility certifies pathogen reduction for surface disposal. No Yes DMR Biosolids - Land Application Site

Does the Facility certify Vector Attraction Reduction for land application?

The flag indicating if the facility certifies Vector Attraction Reduction (VAR) for surface disposal. No Yes 

DMR Biosolids - Surface Disposal Does facility certify pathogen reduction for surface disposal? The flag indicating if the facility certifies pathogen reduction for surface disposal. No Yes DMR Biosolids - Surface Disposal

Does facility certify vector attraction reduction for surface disposal?

The flag indicating if the facility certifies Vector Attraction Reduction (VAR) for surface disposal. No Yes 

Violation Basic Info NPDES ID NPID The activity ID of the permit to which the violation is associated. Yes Yes Yes 

Violation Basic Info Violation Code CVIO, MVIO, SVCD

The code/ description identifying which type of Violation has occurred (e.g., D80 = Required Monitoring DMR Value Non-Receipt, E90 = Effluent Violation, C20 = Schedule Event Achieved Late).

Yes Yes Yes 

Violations

2a-18
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Violation Basic Info Single Event Violation Date SVDT The date of a Single Event Violation; it is only used for Single Event Violations. Yes Yes Yes 

Violation Basic Info Single Event Start Date If the single event violation ocurred over multiple days, the date the ocurrence began. No Yes Yes 

Violation Basic Info Single Event End Date If the single event violation ocurred over multiple days, the date the ocurrence ended. No Yes Yes Violation RNC RNC Detection Code SNCC, SNCE, SNCS The type of RNC detected. It can be entered automatically by the system or it can be entered manually. No Yes Yes Violation RNC RNC Detection Date SNDC, SNDE, SNDS

The date that RNC was detected. It can be entered manually or automatically. In cases in which RNC is detected by ICIS –– NPDES, the detection date entered will vary according to the type of violation detected.

No Yes Yes 

Violation RNC RNC Resolution Code SRCC, SRCE, SRCS The RNC status (i.e., noncompliant, resolved pending, waiting resolution, resolved) of the violation. It can be entered manually or automatically by the system. No Yes Yes Violation RNC RNC Resolution Date SRDC, SRDE, SRDS The date RNC was marked to its current resolution status. It can be entered manually or automatically. No Yes Yes Program Reports

2a-19
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Program Reports Basic Info Report Received/ Event Date: PSED, DTRC The date the report was received. Yes Yes 

Program Reports Basic Info NPDES ID NPID The unique identifier for an activity performed at or related to a particular site. Yes Yes Program Reports Biosolids Report Coverage End Date The date that report coverage ends. Yes Yes 

Program Reports Biosolids Number of Report Units The number of months that the report covers. Yes Yes Program Reports CAFO Animal Types The unique code/ description that identifies the operation’s applicable animal sector(s). No Yes Program Reports CAFO Animal: Other

The free-form text field to describe the operation's applicable animal sector if Other is selected for Animal Type Code.

No Yes 

Program Reports CAFO Total Number The total number of each type of livestock at the facility. No Yes Program Reports CAFO Discharges During Year from Production Area The flag indicating if there is any discharge from the production area during the year. No Yes Program Reports CAFO Solid Manure or Litter Generated The total amount of manure in tons generated annually by the facility. No Yes Program Reports CAFO Liquid Manure or Wastewater Generated The total amount of manure in gallons generated annually by the facility. No Yes Program Reports CAFO Liquid Manure or Wastewater Transferred The number of gallons of manure or litter produced by the CAFO that will be transferred to other persons. No Yes Program Reports CAFO Solid Manure or Litter Transferred The number of tons of manure or litter produced by the CAFO that will be transferred to other persons. No Yes Program Reports CAFO

Does the facility have an NMP developed or approved by a certified planner?

The yes/no flag indicating whether the facility has Nutrient Manure Management Plan developed or approved by a certified planner.

No Yes 

Program Reports CAFO Total Number of Acres Identified by NMP The number of acres the existing NMP covers. No Yes Program Reports CAFO

The total number of acres used for land application in past 12 months

The total number of acres used for land application in past 12 months. No Yes 

2a-20
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Program Reports CSO Permitted Feature Identifier The unique identifier for the permitted feature number entered by the user for the CSO. No Yes Program Reports CSO Location Street Address The street address location of the overflow.

Yes, if Permitted 

Feature Identifier 

or Lat/long info is 

not entered

Yes Yes 

Program Reports CSO Longitude

The measure of the angular distance on a meridian east or west of the prime. Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees.

Yes, if CSO 

Overflow 

Location Street 

Address or 

Permitted Feature 

Identifier is not 

entered

Yes Yes 

Program Reports CSO Latitude

The measure of the angular distance on a meridian north or south of the equator. Entered in either Decimal Degrees or in Degrees Minutes Seconds; stored in decimal degrees.

Yes, if CSO 

Overflow 

Location Street 

Address or 

Permitted Feature 

Identifier is not 

entered

Yes Yes 

Program Reports Pretreatment

Pretreatment Performance Summary Start Date

PSSD The date on which the Pretreatment Performance Summary Report starts. Yes Yes 

Program Reports Pretreatment SIUs The total number of SIUs. No Yes Program Reports Pretreatment SIUs Without Control Mechanism The number of SIUs for which a current control mechanism is required but not yet issued or has expired, as reported on the annual report. No Yes 

2a-21
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Program Reports Pretreatment SIUs Not Inspected The number of SIUs not inspected, as reported on the annual report. No Yes Program Reports Pretreatment SIUs Not Sampled The number of SIUs not sampled, as reported on the annual report. No Yes Program Reports Pretreatment SIUs in SNC with Pretreatment Standards The significant industrial users in SNC with pretreatment standards, as reported on the annual report. No Yes Program Reports Pretreatment

SIUs in SNC with Reporting Requirements

The significant industrial users in SNC with reporting requirements, as reported on the annual report. No Yes 

Program Reports Pretreatment Violation Notices Issued to SIUs VINO (not WENDB), FENF

The number of formal notices of violation or equivalent actions that have been issued to SIUs. Notices do not include AOs (which are defined as a formal notice to the user of violations and requires specific actions with specificdates to address those violations. AOs may include penalties.)

No Yes 

Program Reports Pretreatment Administrative Orders Issued to SIUs ADOR (not WENDB), FENF

The number of administrative orders issued to SIUs. An Adminstrative Order (AO) is defined as a formal notice to the user of violations and requires specific actions with specific dates to address those violations. AOs may includepenalties.

Yes Yes 

Program Reports Pretreatment Civil Suits Filed Against SIUs CIVL (not WENDB) The number of civil suits filed against SIUs, as reported on the annual report. No Yes Program Reports Pretreatment Criminal Suits Filed Against SIUs CRIM (not WENDB), JUDI The number of criminal suits filed against SIUs, as reported on the annual report. No Yes Program Reports Pretreatment CIUs The total number of CIUs. No Yes Program Reports Pretreatment Pass-Through/ Interference Indicator The flag indicating if there have been any incidents of pass- through or interference at the POTW in the past year, as reported on the annual report. No Yes Program Reports Pretreatment

Date of Most Recent Technical Evaluation for Local Limits

The date on which the Pretreatment Control Authority has technically evaluated the need for local limits. No Yes 

Program Reports Pretreatment

Date of Most Recent Adoption of Technically Based Local Limits

The date of most recent approval of technically based local limits for pollutants by Pretreatment Approval Authority. If 1 or 2 local limits are updated at a time (on-going), the latest adoption date (approval) would be the date of the last approval, even if it was for only one pollutant. 

No Yes 

2a-22
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Program Reports Pretreatment Local Limits Pollutants This is the list of the pollutants for which local limits were derived, not at the outfall but at the headworks.

Yes, if a date is 

entered for Date 

of Most Recent 

Adoption of 

Technically 

Based Local 

Limits

Yes 

Program Reports Pretreatment Removal Credits Application Status The status of the application for removal credits. No Yes Program Reports Pretreatment

Date of Most Recent Removal Credits Approval 

This is the date the application for removal credits was approved.

Yes, if the 

Removal Credits 

Application 

Status is 

"approved".

Yes 

Program Reports Pretreatment Removal Credits This field contains a list of pollutants for which removal credits were granted.

Yes, if the 

Removal Credits 

Application 

Status is 

"approved".

Yes 

Program Reports Pretreatment SIUs in SNC Published in Newspaper SVPU The number of significant industrial users in SNC published in the newspapers, as reported on the annual report. No Yes Program Reports Pretreatment

Industrial Users (IUs) from which Penalties have been collected

IUPN Number of IUs (not SIUs) from which penalties have been collected, as reported on the annual report. No Yes 

Program Reports Pretreatment SIUs in SNC with Pretreatment Schedule SSNC The number of Significant industrial users in SNC with pretreatment schedule, as reported on the annual report. No Yes Enforcement Action Basic Info Enforcement Action Identifier ERFN, CSFN

The number of the Enforcement Action; for a judicial action, the number as referred to by the Court where the action was filed. This number is also used to link compliance schedules to enforcement actions.

Yes Yes Yes 

Enforcement Action Basic Info Forum ENAC, EKAC

This is the legal forum in which the Enforcement Action is brought. For Administrative Formal, the action is brought before an administrative body or tribunal. Yes Yes Yes 

Enforcement Action Basic Info Enforcement Action Type ENAC

A description that uniquely identifies the type of enforcement action (i.e., civil judicial, bankruptcy). For administrative enforcement actions, the type is the statute section authorizing the action.

Yes Yes Yes 

ENFORCEMENT DATA ELEMENTS

2a-23
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Enforcement Action Basic Info Programs Violated ENAC The code that identifies the program associated with an activity. Yes, except for Federal actions Yes Yes Enforcement Action Basic Info Reason for deleting enforcement action Reason for deleting enforcement action. Yes, if deleting action. Yes Yes Enforcement Action Basic Info Violation Code EVTP, ESVC, ECVC

The code/ description identifying which type of Violation has occurred (e.g., D80 = Required Monitoring DMR Value Non-Receipt, E90 = Effluent Violation, C20 = Schedule Event Achieved Late).

Yes Yes Yes 

Enforcement Action Basic Info Violation Date EVMD, ECVD, ESVD

If there is a Single Event Violation, use Single Event Viuolation Date; if DMR reporting violation, use DMR Due Date; if DMR measurement violation, use Monitoring Period End Date; if Permit Schedule violation, use Permit Schedule Date; if a Compliance Schedule violation, use Compliance Schedule Date.

Yes Yes Yes 

Final Orders Basic Info Final Order Type ENAC, EKAC

A code/ description that uniquely identifies the regulatory instrument used by the EPA to settle the Enforcement Action.

Yes Yes Yes 

Final Orders Basic Info Violation Code EVTP, ESVC, ECVC

The code/ description identifying which type of Violation has occurred (e.g., D80 = Required Monitoring DMR Value Non-Receipt, E90 = Effluent Violation, C20 = Schedule Event Achieved Late).

Yes Yes Yes 

Final Orders Basic Info Violation Date EVMD, ECVD, ESVD

If there is a Single Event Violation, use Single Event Viuolation Date; if DMR reporting violation, use DMR Due Date; if DMR measurement violation, use Monitoring Period End Date; if Permit Schedule violation, use Permit Schedule Date; if a Compliance Schedule violation, use Compliance Schedule Date.

Yes Yes Yes 

Final Orders Basic Info Final Order Issued/ Entered Date ENDT, EKDT

The civil case date the Final Order is signed by the presiding Judge and entered by the Clerk of the Court; it is the date the Clerk stamps on the document. For an Administrative Formal EA, this is the Final Order Issued Date; for a Judicial EA, this is the Final Order Entered Date.

No Yes Yes 

Penalty Basic Info

Cash Civil Penalty Amount Required-By Statute

APAMAPPA

For civil judicial Enforcement Actions, the dollar amount of the penalty assessed against the defendant(s) as specified in the final entered Consent Decree or Court Order. For Administrative Enforcement Actions, it is the dollar amount of the penalty assessed in the Consent/Final Order.

No Yes Yes 

Compliance Schedule Schedule Compliance Schedule Number CSCH, VCSN, EVSN A two-digit number which in combination with the Schedule Type and NPDES ID uniquely identifies a Compliance Schedule. Yes Yes Yes 

Compliance Schedule Schedule Schedule Descriptor The code/ description indicating the type of Narrative Condition applies for the schedule. No Yes Yes 

Final OrdersPenaltiesCompliance Schedules

2a-24
APPENDIX 2a: DETAILED RIDE TABLE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

Master 

General 

Permits

RIDE Data Element Description PCS equivalent (if available)1 System Required Area Data Element Name Sub-Area 2 

Permit Type in ICIS-NPDES

Compliance Schedule Event Schedule (Start) Date DTSC, ERDT, CVDT The date the event is scheduled to be occur (i.e., the due date). Yes Yes Yes 

Compliance Schedule Event Actual Date DTAC The actual date on which the Compliance Schedule event occurred. No Yes Yes 

Compliance Schedule Event Report Received Date DTRC The date the regulatory agency received the Compliance Schedule report. No Yes Yes Compliance Schedule Event Schedule Event EVNT, CVEV, EVEV The unique code/ description that identifies the Compliance Schedule event. Yes Yes Yes 

Milestones/ Subactivities Basic Info Sub Activity Type ENAC, ENST, APHR, APAP

A code/ description that uniquely identifies a type of sub activities and/or milestones in the lifecycle of an enforcement action, such as "complaint filed" or "action closed".

Yes Yes Yes 

Milestones/ Subactivities Basic Info Actual Date ENDT, APFO, ESDT, APPC, APAF The date on which the milestone was achieved/sub activity was conducted. No Yes Yes 

Milestones/ Sub-activities

2a-25
APPENDIX 2b: ADDITIONAL FEDERAL RIDE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

M

G

P

Permit Basic Info Major/Minor Status Indicator MADI The flag to indicate if the permit is a major or minor. Initially system generated (defaults to Minor) and updatable only by HQ users. Yes Major Minor Rating Sheet 122.2/ CWA 301(d), 304(b), and 304(m) NPDES universe inventory tracking/ NPDES Mgmt Report (PER)/ ECHO/ OTIS/ ANCR/ WL/ Accomplishments reporting /ELG Annual Review Yes 

Permit Basic Info Major/Minor Status Start Date PTAC The date that the Permit became its current Major/Minor status. Initially system-generated to match effective date and updatable only by HQ users. Yes Major Minor Rating Sheet 122.2 NPDES universe inventory tracking/ NPDES Mgmt Report (PER)/ ECHO/ OTIS/ ANCR/ WL/ Accomplishments reporting Yes Permit CAFO

Number of Acres of Contributing Drainage from Production Area

This is the number of acres that are drained and collected in the production area. No App./ NOI/ Annual Report 122.23 To determine possibility of runoff from production areas Yes 

Compliance Monitoring Activity Basic Info Region The code/ description that represents the EPA Region. Yes Inspection Form 3560 none NPDES Mgmt Report (PER)/ ECHO/ OTIS/ Accomplishments reporting/ State Framework Yes Yes Compliance Monitoring Activity Basic Info If state, local, or tribal lead, did EPA assist? INSP The flag indicating whether the EPA assisted with an activity when either the state, local, or tribal agency was the lead. No Inspection Form 3560, ICDS CWA 308 Accomplishments reporting Yes Yes Compliance Monitoring Activity Basic Info

If Joint, what was the purpose of the participation of the other party?

The reason for joint inspection. Yes Inspection Form 3560, ICDS CWA 308 Data QA Yes Yes 

Compliance Monitoring Activity Basic Info Which party had the lead? INSP The flag indicating who is the lead of the joint inspection. Yes Inspection Form 3560, ICDS CWA 308 ECHO/ OTIS/ WL/ Accomplishments reporting Yes Yes Compliance Monitoring Activity Basic Info Federal Statute Violated A code that uniquely identifies the law that is authorizing the activity or being violated. Yes Inspection Report CWA 308 Accomplishments reporting Yes Yes Compliance Monitoring Activity CAFO

Number of Acres of Contributing Drainage from Production Area

Number of acres from production area used for drainage. No App./ NOI; Inspection 122.23 Supports enforcement and compliance monitoring Yes 

Enforcement Action Basic Info Enforcement Action Name The name assigned to the enforcement action by the lead attorney; generally the primary defendant's name is used as the enforcement name. Yes, except for state actions User-defined, can be facility name CWA Section 309 Accomplishments reporting Yes Yes Enforcement Action Basic Info Comments ECM1-ECM10 (not WENDB) The free-form textual comments entered by the user/ analyst to further describe the corresponding data in a sensitive field. No

User-defined, 

based on 

enforcement 

action/ 

administrative 

record

CWA Section 309 Data QA Yes Yes 

Enforcement Action Basic Info Federal Statutes Violated A code that uniquely identifies the law that is authorizing the activity or being violated. Yes

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Accomplishments reporting Yes Yes 

Enforcement Action Basic Info Law Sections Violated The Section(s) of law violated and cited in the action. Yes, except for State actions

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Accomplishments reporting Yes Yes 

1. This column provides the PCS acronyms that correspond to each RIDE element. If blank, there is no known equivalent. Also, the PCS acronyms represent WENDB elements required in PCS, unless otherwise noted.PERMIT DATA ELEMENTS2. From the ICIS-NPDES Detailed Design Document (page 4-2): “Data elements are marked as system required when entry of the data element is required by ICIS-NPDES in order for a user to add a particular record into the system... If [system-]required data elements are not entered, ICIS-NPDE3. From the ICIS 2.0 Users Guide (Permits section): "Unpermitted facilities are records established in ICIS to allow for tracking of activities (e.g., inspections and enforcement actions) that are associated with facilities that do not have [NPDES] permits. They may not contain narrative conditions, 

apply to facilities covered by a state program that is "broader in scope" than the approved NPDES program (under 33 U.S.C. § 1342(b)). Except for SIUs in non-preatreatment cities, the facility, compliance monitoring, and enforcement data for unpermitted facilities is only RIDE if there has been order or an informal enforcement action that addressed SNC. For SIUs in non-pretreatment cities, RIDE is expected. Examples of unpermitted facilities include SSS satellite systems and AFOs that, after inspection, are determined to be CAFOs requiring a NPDES permit.

Note: This is a list of additional RIDE exclusively for federal users and should be entered in addition to the RIDE listed in Appendix 2a. This list does not yet include all federal data entry requirements. 

Regulatory 

Citation Data Use 

ENFORCEMENT DATA ELEMENTS

System 

Required

Sub-Area RIDE Data Element Description 2

COMPLIANCE MONITORING DATA E

PCS equivalent (if available)

Area Data Element Name 1

Permit Type in ICIS-NPDE

Information 

Source

2b-1
APPENDIX 2b: ADDITIONAL FEDERAL RIDE 

Unpermitted 

Facility3

Standard/ Individual/ 

Industrial User Permits & 

Associated Permit Records 

M

G

P

Regulatory 

Citation Data Use 

System Required Sub-Area RIDE Data Element Description 2 PCS equivalent (if available) Area Data Element Name 1

Permit Type in ICIS-NPDE

Information 

Source

Enforcement Action Basic Info Priorities

A code that uniquely identifies the national or regional priority that prompted the initiation of an activity such as an inspection or enforcement action. Must enter National, Regional or Core.

Yes

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Accomplishments reporting Yes Yes 

Enforcement Action Basic Info Respondents/ Defendants The name of the defendant, or respondent associated with the Enforcement Action. Yes, except for State actions

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Accomplishments reporting Yes Yes 

Enforcement Action Basic Info

Summary / NonCompliance or Corrective Action Description

The summary of the violation environmental problem and a description of the cause of action (basis of legal action). The summary could be extracted from the referral transmission memo or letter or it could be required as a first section of a revised standardized referral document.

Yes

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Accomplishments reporting Yes Yes 

Enforcement Action Basic Info Pollutants The ICIS internal identifier for a substance. Yes

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Data QA Yes Yes 

Enforcement Action Basic Info Violation Type EVTP A unique code identifying the type of violation. Yes

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Accomplishments reporting Yes Yes 

Enforcement Action Gov contacts Affiliation Type The way that the contact is affiliated with the activity.

Yes, for Federal 

Formal 

Enforcement 

Actions

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Data QA Yes Yes 

Enforcement Action Gov contacts First Name The given name of an individual.

Yes, for Federal 

Formal 

Enforcement 

Actions

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Data QA Yes Yes 

Enforcement Action Gov contacts Last Name The surname of an individual.

Yes, for Federal 

Formal 

Enforcement 

Actions

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Data QA Yes Yes 

Final Orders Basic Info Final Order Name

The name of a final order associated with an enforcement action as assigned by the lead EPA attorney for federal actions.

Yes

User-defined, 

based on 

enforcement 

action/ 

administrative 

record

CWA Section 309 Accomplishments reporting Yes Yes 

Final Orders Basic Info Respondents/ Defendants The name of the defendant, or respondent, associated with the enforcement action. Yes

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Accomplishments reporting Yes Yes 

Final Orders Basic Info Federal Statutes Violated A code that uniquely identifies the law that is authorizing the activity or being violated. Yes

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Accomplishments reporting Yes Yes 

Final Orders Basic Info Final Order Lodged Date The date the settlement document is given to the clerk of the court for lodging in the district court; it is the date the clerk stamps on the document. (Federal judicial EA's only.) Yes Administrative Record CWA Section 309 Accomplishments reporting Yes Yes Final Orders Basic Info Violation Type EVTP A unique code identifying the type of violation. Yes

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Accomplishments reporting Yes Yes 

Milestones/ Subactivities Basic Info Enforcement Action Resolution Type This is the mechanism by which the Enforcement Action is resolved.

Yes, when 

concluding an 

enforcement 

action.

Enforcement 

Action/ 

Administrative 

Record

CWA Section 309 Data QA Yes Yes 

Milestones/ Sub-activitiesFinal Orders

2b-2
APPENDIX 3, April 30, 2007 DRAFT 

3-1 

RIDE Data Entry Considerations by Program Area 

Since January 2006, EPA and the States have been actively involved in renewed discussions which have included cons

expectations for data entry or transfer into ICIS-NPDES for each program area and possible phasing of selected data, partic

facilities. The Resources workgroup formed by the ICIS-NPDES Expanded Steering Committee produced a RIDE Data En

which was used to estimate RIDE data entry resources (in full-time equivalents [FTEs]) both nationally and for nine individsynopsis of the national assumptions and results of the RIDE Data Entry Estimate Model for the various program areas is pbelow, with the percent of total RIDE data entry based upon the RIDE Data Entry Model estimate. With the exception of pnot capable of providing sufficient information regarding these program areas. 

Program Area Estimated Universe % of Total RIDE Data Comments 

Biosolids 6,000 sludge-only facilities 2% Only seven States are currently authorized to impleme

Combined Sewer 

Systems (CSSs) 

821 CSSs, with 8,924 combined 

sewer outfall locations <1% 

Number of CSSs varies considerably by State; the Sing

Entry Guide (under development) will clarify data e

overflow volumes. 

Concentrated 

Animal Feeding 

Operations (CAFOs) 

13,800 large or medium CAFOs 

with permits; 224,217 AFOS or 

CAFOs without permits 

1% 

States have indicated that some CAFO RIDE currentl

have been some implementation delays by certain 

development of new CAFO regulations (antic

Pretreatment 1,464 approved local programs 

Mostly 

WENDB in 

PCS; <1% for 

new 

non-WENDB 

Most of these data elements were WENDB in PC

well-populated by some States. RIDE are also exp

transferred into ICIS-NPDES for SIUs in non-p

Separate Sanitary 

Sewer Systems 

(SSSs) 

20,000 sanitary sewer overflows 

per year 

<1% 

For SSS satellite systems, RIDE is not expected to be e

ICIS-NPDES unless the satellite has been issued a for

administrative penalty order, or an informal enforceme

the SSS significant noncompliance (SNC); the Singl

Entry Guide (under development) will clarify data e

overflow volumes. 

Stormwater (SW) 

280 Phase I MS4s, 7,500 Phase II 

MS4s, 100,000 Phase I SW 

industrial non-const., 10,000 

Phase II SW industrial non-const., 

100,000 Phase I SW const., 

150,000 Phase II SW const. 

3% 

For SW construction sites, RIDE is not expected to b

into ICIS-NPDES unless the facility has been issued 

action, administrative penalty order, or an informal en

addresses the SW significant noncompliance (SNC) a

reporting for SW industrial non-const. is not RIDE un
April 30, 2007 DRAFT

APPENDIX 3a: EPA RIDE Data Entry 

The striped slices reflect data that is being entered into PCS/ ICIS-NPDE

Other new requirements 

1%

AFO/ CAFO

1%

CSO, SSO, new 

Pretreatment

<1% Biosolids 2%

WENDB (1)

16%

Other Required NonMajor Individual 

Outfalls, Limits, & DMRs 

34%

Stormwater

3%

Non-Major In

Outfalls, Limits

already being 

35%

Non-Major nonStormwater General 

Outfalls, Limits, & DMRs

8%

Note: Full Circle represents 1.8 FTEs per State per 

(based on February 2007 revised model) 
4-1

APPENDIX 4, April 30, 2007 DRAFT 

Key National Targets for Data in ICIS-NPDES 

A phased transition period allows permitted authorities (States, Territories, Tribes and EPA 

Regions) to become familiar with the ICIS-NPDES system, make program adjustments if necessary, 

and initiate data entry or transfer of the RIDE into ICIS-NPDES. The transition period applies 

primarily to that RIDE for which WENDB equivalents did not exist in PCS. EPA recommends that 

States, Territories and Tribes develop transition plans to promote a timely and efficient move from 

PCS to ICIS-NPDES. The key national targets for data entry that should be incorporated into the 

transition plans for all current and prospective users of ICIS-NPDES are described below. 

 By August 1, 2007, all NPDES-authorized States, Territories and Tribes should begin to 

develop an ICIS-NPDES transition plan that includes a strategy to fully enter all RIDE within the 

target dates specified. The draft transition plan for each individual State, Territory and Tribe 

should be submitted no later than the deadlines stated below to the EPA Region for review and 

approval. Hybrid and non-direct (batch) users have been allocated four additional months to review 

the ICIS-NPDES XML schemas as they develop their transition plans. This also allows some 

phasing of the Regional workload to review these plans. EPA Regions which are responsible for 

direct implementation of the NPDES program in a non-authorized State or Tribal area shall submit 

their own transition plans to EPA Headquarters by December 1, 2007. EPA will review and 

approve adequate plans within three months of receipt. 

Direct 

Users 

Hybrid/ Batch 

Users Target 

8/1/2007 8/1/2007 - Begin development of ICIS-NPDES transition plans 

12/1/2007 4/1/2008 

- Submit State and Tribal transition plans to the EPA Regions for review and approval. (Regions 

that are developing transition plans for States and Tribes that are not authorized for the NPDES 

program will submit such plans to EPA HQ for review and approval.) 

3/1/2008 7/1/2008 - Complete EPA review and approval of all transition plans for States, Tribes and EPA Regions. 

In 2006 and 2007, EPA worked with the States -- via the Expanded Steering Committee, and 

its associated Resources and Matrix Workgroups -- to further refine the RIDE list and to closely 

examine key concepts associated with ICIS-NPDES. EPA has used the information and products 

from those efforts to develop the national data targets for the early years of implementation of the 

ICIS-NPDES Policy Statement. These national data targets (presented in the table below) should be 

incorporated into the transition plans for each State, Territory, Tribe or Region. The target dates in 

the table below apply to all States, with the understanding that all dates may be extended up to four 

months after a State migrates to ICIS-NPDES. 

The transition plans should also ensure that data associated with non-DMR compliance 

monitoring (e.g., inspections), single event violations, enforcement actions, penalties and 

compliance schedules should be entered or transferred into ICIS-NPDES as those events occur 

(after migration from PCS to ICIS-NPDES). The transition plans should also ensure that 

appropriate linkages between the data for these compliance monitoring and enforcement items are 

also entered into ICIS-NPDES. In addition, the transition plans should ensure RIDE data entry or 

transfer to ICIS-NPDES is consistent with all requirements of Sections E, F, and G of this Policy 

Statement and with the RIDE list (in Appendix 2a; for Federal users, Appendices 2a and 2b). A 

transition plan template is provided in Appendix 5. 
4-2 

DETAILED TARGETS FOR STATES, TRIBES, AND REGIONS 

By the dates below or within four months of migration to ICIS-NPDES (whichever is later), all users are expected to meet these nationa

Target (these represent 98% data completeness unless otherwise specified) Majors Individual Non-Majors Facility/ Permit Information  Basic Information - WENDB 8/1/2007  Facility Latitudes/Longitudes3 8/1/2007 5/1/2008  Special Program Area Permit Components4 and other new (non-WENDB) RIDE 5/1/2008 12/1/2008 Permitted Feature Data3, Limit Sets, Limits and DMRs5 Traditional Universe 8/1/2007 

≥50% (with an emphasis on those facilities located in priority watersheds) by 9/1/2008. Enter data for remaining facilities 2 years after NetDMR is implemented 

≥25% facilitwaterEnter years imple

 Stormwater Industrial permits N/A N/A  Biosolids 5/1/2008 12/1/2008 Narrative Conditions (Permit Schedules were WENDB for majors) 8/1/2007 No later than 8/1/2010 Inspections  Traditional Universe (i.e., traditional majors and non-majors, excluding wet weather program areas) and Pretreatment – (were WENDB in PCS)  Special Program Areas 

Entered as they occur 

Violations  Permit/ Compliance Schedule and DMR violations System-generated based on data  Single Event Violations Entered as they occur Program Reports  Existing WENDB (Pretreatment) 8/1/2007 8/1/2007 6  New Special Program Areas (Biosolids, CAFOs, CSOs) No later than 8/1/2010 Enforcement Actions (Were WENDB for majors) Entered as they occur 1 EPA may revise these dates for batch and hybrid users to address any unforeseen issues related to the finalization of the ICIS-NPDES XML schema by the Integrated Pr

2 RIDE for facility, permit, compliance monitoring, violations and enforcement data for SSS satellites and Stormwater-Construction sites is not expected except if the Statenforcement action, administrative penalty order, or other informal enforcement action which addresses the stormwater SNC. In this case, the data should be entered as th

3 If this locational data (latitude, longitude, source map scale number, horizontal accuracy measure, horizontal collection method, horizontal reference datum, and referenc

collected, the permitting authority may wait until permit reissuance to enter or transfer this particular data. 

4 These special program area elements apply to CAFOs, Biosolids, CSOs, Pretreatment, POTW, and Storm Water facilities. 5 Note that some permits do not have DMR requirements; for these permits, limit, limit set, and DMR data entry will not be necessary. 

6 Pretreatment Performance Summary Data is currently WENDB for major facilities and for minor facilities that are PL 92-500 Construction Grant recipients. 
5-1 

APPENDIX 5, April 30, 2007 DRAFT 

Template for a Transition Plan 

As described in Sections F and G of this Policy Statement, the transition plan and 

target schedule for authorized States, Territories and Tribes will be reviewed and 

approved by EPA Regions at the Division Director level (Enforcement and Water) within 

three months of submission to EPA. Similarly, transition plans and target schedules for 

non-authorized States, Territories or Tribes will be reviewed and approved by EPA 

Headquarters within three months of Regional submission. 

The transition plans should include the following information:

I. Name of State/Territory/Tribe/Region: 

II. Type of User: Direct Non-direct Hybrid/Combination 

 (If hybrid/combination, please provide short explanation). 

III. Number of facilities in each of these categories: Traditional majors Traditional individual non-majors Traditional general- permitted non-majors Biosolids CAFOs Approved pretreatment programs SIUs in non- pretreatment 

cities CSSs SSSs MS4s Nonconstruction industrial stormwater sites Stormwater construction sites (annually) 

 

IV. Strategy/Approach: 

Provide a short description of the State, Territorial, Tribal or Regional plan for 

meeting national RIDE reporting targets in ICIS-NPDES within the transition period. 

Each of the following items should be covered in the strategy description: 

A. Overall implementation strategy: by permit type, by watershed, by prioritization 

of minors, other; 

B. Gap analysis to determine areas where RIDE currently are not collected or not 

available electronically (To assist in this effort, EPA will generate a report to 

indicate how well-populated the various WENDB data elements are in PCS); 

C. Description of business processes that need to be changed to address data gaps 

and to ensure that RIDE flows to ICIS-NPDES. How will this be done? Will 

data entry be centralized? Will spreadsheets or other tracking be phased into 

ICIS? 

D. If non-direct users or hybrid/combination users, description of changes needed to 

be made to the data system of the State, Territory or Tribe; 
5-2 

E. Incorporation of national data entry targets (as identified in Appendix 5) into the 

strategy and the schedule; 

F. Description of the amount of grant money that has been made available to the 

State, Territory or Tribe for the transition from PCS to ICIS-NPDES and which 

activities are to be accomplished with the grant money; 

G. Description of additional training or equipment that may be necessary; 

H. Description of impacts on other data systems within the State, Territory or Tribe; 

and 

I. Description of quality assurance (QA) procedures that will be used to ensure data 

quality and timeliness. 

V. Schedule: 

This schedule should be developed with reference to Appendix 4 of the Policy 

Statement (Key National Targets for Data in ICIS-NPDES). The schedule should 

include key targets for RIDE data entry, national data entry targets and data system 

modifications necessary to directly use, link or transfer data to ICIS-NPDES. 

Within the national data entry targets, the permitting authority has flexibility in 

the prioritization approach that is used for data entry or data transfer to ICIS-NPDES. 

One option for prioritizing RIDE data entry or transfer into ICIS-NPDES is to prioritize 

data entry for facilities located in priority watersheds; this approach is particularly 

encouraged in the possible phasing of the data entry of DMRs for non-major facilities (as 

discussed in Section F of the Policy Statement). Another prioritization option would use 

permit components for specific program areas, such as CSSs, SSSs, pretreatment, 

biosolids, stormwater-MS4s, stormwater-industrial (non-construction), stormwaterconstruction and CAFOs. Another approach would be to enter all available RIDE data 

for facilities covered by major individual permits, then those covered by non-major 

individual permits, non-stormwater general permits and stormwater general permits. 

Although States, Territories or Tribes may exercise flexibility regarding which program 

areas or permit types are made available in ICIS-NPDES first, any such prioritization 

effort should still ensure that national data targets are met. 

As an example, the attached table is a suggested format for a Data Entry Schedule 

Chart to be included in the Transition Plan for each State, Territory, Tribe or Region if 

using a permit type prioritization for RIDE data entry or transfer into ICIS-NPDES: 
5-3 

DATA ENTRY SCHEDULE CHART: DETAILED TARGETS 

Target (these represent 98% data completeness unless otherwise specified) Majors Individual Non-Majors 

Facility/ Permit Information  Basic Information – (expected to be available without delay; WENDB data migrated from PCS)  Facility Latitudes/Longitudes  Special Program Area Permit Components and other new (non-WENDB) RIDE Permitted Feature Data, Limit Sets, Limits and DMRs  Traditional Universe  Stormwater Industrial permits  Biosolids Narrative Conditions (Permit Schedules)( were WENDB for majors)Inspections  Traditional Universe and Pretreatment –  (historical data will be migrated from PCS, where such data was WENDB)  Special Program Areas Violations  Permit/ Compliance Schedule and DMR violations  Single Event Violations Program Reports  Existing WENDB (Pretreatment)(not a new requirement)  New Special Program Areas (Biosolids, CAFOs, CSOs) Enforcement Actions (previously was WENDB for majors only)
5-4 

VI. Resources: 

 Explain resource implications, in terms of staffing, training, other support as well 

as anticipated cost savings from electronic reporting. States are encouraged to use the 

RIDE Data Entry Estimate Model to estimate annual ICIS-NPDES data entry resources 

for the State. To the extent known, explain how these resource estimates may shift over 

the initial few years. 

VII. Linkages 

 For hybrid or non-direct users, provide sufficient detail as to what data will be 

directly entered into ICIS-NPDES (if any), and what data will be shared or transferred to 

ICIS-NPDES using ICIS-NPDES XML schema, including any phasing of data 

exchanged and frequency. In addition, the transition plan should clearly indicate what 

measures will be taken to ensure that entry of associated linkages between permits, 

inspections, violations and enforcement data will occur and be present in ICIS-NPDES. 

VIII. Contacts 

 Identify key system contacts, including: system administrator; data steward; data 

entry personnel; responsible manager; other agency contacts. Please specifically identify 

the key contact regarding the development and implementation of the transition plan. 
6-1

APPENDIX 6, April 30, 2007 DRAFT 

Key ICIS-NPDES Roles and Responsibilities 

Defining and maintaining clear roles and responsibilities are essential to 

managing a decentralized database such as ICIS-NPDES. The table below summarizes 

key management responsibilities for each group (NPDES-authorized States, Territories 

and Tribes, EPA Regions, OECA, OW, and OEI) in maintaining a successful system. 

Authorized State, Territory or Tribe 

1. Attend ICIS-NPDES User Group meetings and conference calls; 

2. Develop transition plan and work with the Region during the review process; 

3. Enter or transfer data to ICIS-NPDES pursuant to the standards set forth in Sections E, F 

and G of this Policy Statement, in the RIDE list and in the approved transition plan; 

4. Have complete, accurate RIDE data in ICIS-NPDES within the approved transition 

period; 

5. Ensure data quality in ICIS-NPDES; 

6. Establish, maintain and implement clear ICIS-NPDES management agreements; 

7. Identify System Administrator and Data Steward; 

8. Manage users within the State, Territory or Tribe; 

9. Identify training needs for users within the State, Territory or Tribe; 

10. Manage, research and correct reported data issues; and 

11. Work closely with Regional and OECA/ OW representatives including participating in 

ICIS-NPDES workgroups and in major decisions related to ICIS-NPDES through the 

system governance bodies. 

EPA Region 

1. Attend ICIS-NPDES User Group meetings and conference calls as needed; 

2. Develop transition plans for non-authorized States, Territories and Tribes; work with 

Headquarters during the review process; 

3. Enter data pursuant to the standards set forth in Section E of this Policy Statement, in the 

Federal RIDE list and in the approved transition plan; 

4. Enter NPDES data for non-authorized States, Territories and Tribes in accordance with 

Sections E, F and G of this Policy Statement and have complete RIDE data in system 

within the approved transition period; 

5. Ensure data quality in ICIS-NPDES; 

6. Monitor and supplement data entry from States, Territories and Tribes, if necessary; 

7. Review and approve transition plans; 

8. Review and approve transition plans; 

9. Establish, maintain and ensure implementation of clear ICIS-NPDES management 

agreements with States, Territories or Tribes, incorporating such agreements into PPAs or 

similar documents; 

10. Identify System Administrator and Data Steward; 

11. Train and manage users; 

12. Manage, research and correct reported data issues; 

13. Work closely with Regional and OECA/ OW representatives including participating in 

ICIS-NPDES workgroups and in major decisions related to ICIS-NPDES through the 

system governance bodies; and 

14. Provide a source of ICIS-NPDES technical assistance and training. 
6-2

OECA 

1. Request appropriate resources to support ICIS-NPDES; 

2. Operate and maintain ICIS-NPDES; 

3. Evaluate and improve ICIS-NPDES to better ensure customer satisfaction; 

4. Provide programmatic knowledge and experience; 

5. Assert leadership in ensuring that compliance and enforcement information is kept 

current and complete by States, Territories, Tribes and Regions; 

6. Resolve issues; 

7. Maintain ICIS governance process; 

8. Organize national meetings and conference calls; 

9. Work closely with OW and Regional, State, Territorial and Tribal representatives and 

associations on major decisions related to ICIS-NPDES; 

10. Manage user contact lists, sensitive data access, RNC and DMR non-receipt flags, and 

develop guidance and reference tables; 

11. Monitor State-Region, Territory-Region and Tribe-Region ICIS-NPDES management 

agreements; 

12. Review and approve transition plans submitted by Regions for non-authorized States, 

Territories and Tribes; and 

13. Secure and provide training for use of ICIS-NPDES. 

OW 

1. Work with OECA to ensure the availability of adequate resources; 

2. Monitor State-Region, Territory-Region and Tribe-Region ICIS-NPDES management 

agreements; 

3. Review and approve transition plans submitted by Regions for non-authorized States, 

Territories and Tribes; 

4. Provide programmatic knowledge and experience; 

5. Participate in ICIS-NPDES governance bodies; 

6. Assert leadership in ensuring permit information is kept current and complete by States, 

Territories, Tribes and Regions; 

7. Resolve issues; and 

8. Work closely with OECA, Regional, State, Territorial and Tribal representatives and 

associations, including participating in ICIS-NPDES workgroups and in major decisions 

related to ICIS-NPDES. 

OEI 

1. Work with OECA to ensure the availability of adequate resources; 

2. Manage Exchange Network, ICIS-NPDES XML schema, security protocols, and data 

standards (including locational and facility data standards); 

3. Work closely with OECA, OW, Regional, State, Territorial and Tribal representatives 

on major decisions related to ICIS-NPDES; and 

4. Assist in data exchange between States, Territories, Tribes and EPA. 
7a-1

APPENDIX 7a, April 30, 2007 DRAFT 

Definitions of Terms 

Authorized State or Tribe 

For the purposes of this document, an authorized State or Tribe is a State or Tribal 

government which has received NPDES permitting authority from EPA. 

 

Batch data entry 

Batch data entry in ICIS-NPDES is the transmission of eXtensible Markup Language 

(XML) data files through the Central Data Exchange into ICIS-NPDES. For comparison, 

in PCS, batch data entry occurred via upload of fixed format data files to the mainframe. 

Core data 

Core data refers to the RIDE information associated with facility, permit, compliance 

monitoring, and enforcement data types. 

Data element 

A specific field or column name in ICIS-NPDES or PCS that contains information when 

data is entered. 

Direct data entry 

This refers to manual data entry by key punching, often in the case where the State, Tribe 

or EPA Region is using PCS or ICIS-NPDES as their primary NPDES data management 

system. 

Direct user State or Tribe 

In an NPDES program implemented by an authorized State or Tribe which will use 

ICIS-NPDES to manage the NPDES program, direct users manually enter data into 

ICIS-NPDES through the keyboard into web screens. 

Hybrid State or Tribe 

In an NPDES program implemented by an authorized State or Tribe which will use 

ICIS-NPDES to manage the NPDES program, hybrid users manually enter some of the 

data (usually non-DMR data) into ICIS-NPDES through the keyboard into web screens. 

They also electronically transfer the rest of the data (usually DMR data) into 

ICIS-NPDES; this electronic method of data entry will likely increase, especially with the 

availability of eDMR (electronic DMR) tools, such as NetDMR. 

ICIS 

The acronym ICIS stands for the Integrated Compliance Information System, developed 

by EPA to serve as a national multi-media data system. 
7a-2

Major 

A major facility is defined as follows: a major municipal facility has a flow of 1 million 

gallons per day or greater, a service population of 10,000 or greater or a significant 

impact on water quality; industrial facilities are considered major facilities based on a 

rating system that allocates points in various categories, including flow, pollutant 

loadings and water quality factors. EPA Regions, States and Tribes also have the 

discretion to identify other facilities as major facilities due to environmental concerns. 

Non-direct user State or Tribe 

Such a State or Tribal NPDES program uses another software system, besides 

ICIS-NPDES, to manage the NPDES program and only ensures that data is entered or 

transferred to ICIS-NPDES and is available to satisfy national reporting responsibilities 

and national program management needs. These States and Tribes are expected to rely 

heavily on electronic transfer (batch) using CDX and the Exchange Network, but may 

also use keyboard data entry for some purposes, particularly if the State or Tribe database 

has not been modified to include all RIDE. 

Non-major 

The universe of facilities regulated under the NPDES program that are not 

“major”facilities. Non-major facilities can also be referred to as “minor” facilities, 

although this does not denote a less important status. 

PCS 

The acronym PCS stands for the Permit Compliance System, which served as the national 

database of record for the NPDEs program since 1985. 

Program components 

Program components refer NPDES permit requirements associated with particular 

program areas. In ICIS-NPDES, a group of data elements are available to users to track 

program-specific data on Publicly-Owned Treatment Works (POTWs), Combined Sewer 

Overflows (CSOs), Sanitary Sewer Overflows (SSOs), Pretreatment, Biosolids, 

Stormwater, and Concentrated Animal Feeding Operations (CAFOs). 

RIDE 

The acronym RIDE stands for the Requisite ICIS-NPDES Data Elements, defined as the 

essential national information needed from NPDES-authorized agencies for EPA to meet 

the national NPDES national program management, oversight and reporting needs. 

Single event violation 

A Single Event Violation is a violation of a NPDES permit or regulatory requirement that 

is observed or determined by the permitting authority (EPA Region or authorized State/ 

local/ tribal government), and is distinct from violations that are system-generated (e.g., 

effluent limit violations arising from DMR submission, DMR non-receipt or compliance 

schedule violations). An unauthorized bypass or discharge, a violation detected during an 

inspection, a narrative violation description reported on a DMR, and a pretreatment 

violation are examples of Single Event Violations. 
7a-3

System-required data 

Key data elements that are necessary in order to submit information or proceed to the 

next screen in ICIS-NPDES. 

WENDB 

The acronym WENDB stands for the Water Enforcement National Data Base data 

elements, identified as the required data elements in the Permit Compliance System 

(PCS), which served as the national database of record for the NPDES program since 

1985. 

Wet weather sources 

These are non-traditional NPDES sources which include storm water runoff from 

industrial and municipal sectors, discharges from concentrated animal feeding operations 

(CAFOs), and overflows from combined and sanitary sewer systems (CSOs and SSOs). 

Such sources have been a program priority for EPA’s enforcement and compliance 

program since 1998. 
7b-1

APPENDIX 7b 

Definition of Acronyms 

CAFO - Concentrated Animal Feeding Operation 

CDX - Central Data Exchange 

CFR - Code of Federal Regulations 

CSO - Combined Sewer Overflow 

CSS – Combined Sewer System 

DMR - Discharge Monitoring Report 

ECHO - Enforcement and Compliance History Online 

ICIS - Integrated Compliance Information System 

MS4 - Municipal Separate Storm Sewer System 

NPDES - National Pollutant Discharge Elimination System 

OC – EPA’s Office of Compliance 

OECA - EPA’s Office of Enforcement and Compliance Assurance 

OEI - EPA’s Office of Environmental Information 

OW - EPA’s Office of Water 

PCS - Permit Compliance System 

POTW - Publicly-Owned Treatment Works 

RIDE - Requisite ICIS-NPDES Data Elements 

RNC - Reportable Non-Compliance according to 40 CFR §123.45 

SNC - Significant Non-Compliance according to 40 CFR §123.45 

SSO - Sanitary Sewer Overflow 

SSS – Sanitary Sewer System 
7b-2

WENDB - Water Enforcement National Data Base 

XML - eXtensible Markup Language