United States Office of Wastewater
Environmental Protection Enforcement and Compliance
Agency
vyEPA Permit Compliance
System (PCS)
QNCR Training Manual
December 27,1993
-------
Permit Compliance System (PCS) QNCR Training
Contents
1.0 Introduction 1
1.1 Overview 1
1.2 PCS Data Facts and Structure Chart Description 2
2.0 PCS Data Entry As It Relates To The QNCR 3
2.1 Permit Facility Data 3
2.1.1 FAC1 3
2.1.2 FAC2 : 4
2.1.3 FACA ^ 5
2.2 Compliance Schedule Family 6
2.3 Pipe Schedule Data Type 8
2.3.1 OFLG 8
2.3.2 OFLT • 10
2,4 Parameter Limits Data Type H
2.4.1 LIMS 11
2.4.2 LIMM 13
2.5 Measurement Violation Data Type 14
2.5.1 EVIO 14
2.5.2 EDMR 18
2.6 Reissuance Processing . 21
2.7 Single Event Violation Data Type 23
2.8 Enforcement Action Data Type 24
3.0 Compliance Schedules • 27
3.1 Violation Detection of Compliance Schedule Events . . . 27
3.1.1 Automatic Violations 27
3.1.2 Manually Setting Compliance Schedule Violations 31
3.2 Reportable Non-Compliance (RNC) Detection for Compliance Schedules ... 32
3.2.1 Automatic Detection .... /' 32
3.2.2 Manual Detection of RNC for Compliance Schedule Violations 38
3.3 Resolved Pending and Resolving RNC for Compliance Schedules 40
3.3.1 Automatic Resolved Pending 40
3.3.2 Manual Resolved Pending 44
3.3.3 Automatic Resolution of Compliance Schedules 45
3.3.4 Manual Resolution of Compliance Schedules 49
4.0 Effluent Violations 50
4.1 Violation Detection for Measurements . 50
4.2 RNC Detection for Measurement Violations 51
$bC-6053-034-CL-2065A 11727753 ~~HI
-------
QNCR Training Pennit Compliance System (PCS)
4.2.1 Automatic Detection .
4.2.1.1 Automatic TRC Violations
4.2.1.2 Chronic RNC Violations
4.2.1.3 Coding “Other” Parameters
4.2.1.4 Violations of Administrative Limits
4.2.2 RNC for DMIR Non-Receipt
4.2.2.1 Violation Detection for Non-Receipt .
4.2.2.2 RNC Detection for Non-Receipt Violations
4.2.2.3 Incomplete/Deficient DMRs
4.2.2.4 Manual Detection of Effluent Violations
4.3 RNC Resolved Pending and Resolution for Effluent Violations
4.3.1 Automatic Resolved Pending of Effluent & Non-Receipt Violations
4.3.2 Manual Resolved Pending of System Detected RNC
4.3.3 Resolved Pending of Manually Detected Effluent Violations
Resolved Pending of Administrative Limits
Automatic Resolution of Effluent Violations
Automatic Resolution of Resolved Pending Violations
Manual Resolution of Effluent Violations
Problems Encountered on the QNCR
s ir 7!
5.1
5.2 . . 7
5.3 71
5.4 71
6.0 Facility Level RNC 7
7.0 QNCRs and Their Uses 8:
7.1 Regular or Selective QNCR .. . . 8:
7.2 Manager’s QNCR . .
7.3 Coordinator’s QNCR 81
Appendix A
Appendix B
Appendix C
Appendix D
Appendix E
5:
54
5c
5 r
60
&
4.3.4
4.3.5
4.3.6
4.3.7
4.3.8
6
6 4
6T
6
74
7
RNC for Single Event Violations
Violation Detection for Single Event Violations
RNC Detection for Single Event Violations
RNC Resolved Pending for Single Event Violations
RNC Resolution for Single Event Violations
PCS QNCR Related Tables A-
Single Event Violations
Definitions C
PCS Acronym Reference List B -
PCS Training Documentation Comment Form
iv
12127/93
SDC-0055-034-CL-2005 1
-------
Permit Compliance System (PCS) QNCR Tr2ining
SCREENS
Facility Data Screen #1 . 3
Facility Data Screen #2 4
Facility Data Screen #3 5
ComplianceSchedu lesScreen
OutfallScreen#1 8
Outfal lTreatrnentTypeScreen#2 10
Effluent Limits Screen 11
Limit Modifications Screen 13
Effluent Measurements Key Screen 14
EffluentMeasurementsScreen#2 16
Effluent DMR Data Key Screen #1 18
EffluentDMRDataScreen#2 19
Reissuance Data Screen 22
Single Event Violations Screen 23
Enforcement Actions Screen 24
Compliance Schedules Screen 27
EVIO Screen #1 63
EVIO Screen #2 63
SDC-0055-034-CL-2005A 12/27/93 v
-------
Permit Compliance System (PCS) QNCR Training
1.0 Introduction
1.1 Overview
The Quarterly Noncompliance Report (QNCR) is a pre-progranimed report that is generated
quarterly listing the National Pollutant Discharge Elimination System (NPDES) permits that
are in noncompliance according to the Federal Code of Regulations guidelines..
The Permit Compliance System (PCS) tracks the compliance and enforcement activities
conducted under the NPDES program, and automatically generates the QNCR.
These training materials are designed to assist those who work with the QNCR to better
understand its contents. The training has been designed for those who have participated in
the PCS Basic Training course.
This course concentrates on how the Reportable Non-Compliance (RNC) program detects and
resolves RNC violations within PCS. The course consists of three parts:
• The first part of the QNCR Training includes a review of the PCS-ADE screens and
associated acronyms as they relate to the QNCR.
• The second part of this training addresses RNC tracking.
• The third part of this training covers the QNCR, including how it is retrieved and how to
interpret the report.
SDC-OO55 O34-CL-2OO5A 12/27/93
-------
QNCR Training
Permit Compliance System (PCS)
1.2 PCS Data Facts and Structure Chart Description
PCS is structured in a hierarchy.
• Data exists in levels.
• Levels are built upon each other (one must exist before the one below it can exist).
• The Permit Facility (PF) record is the highest level of data. It must exist before any
other data can be entered for a facility.
• Under the PF record there are several vertical data types. These are called families of
data. The largest is the effluent family of data. This data consists of the pipe schedule,
parameters limits and measuremeritlviolation data types. (Connected by solid vertical 1ine
on the chart.)
• On the bottom of the chart, the data types are connected by dotted lines. The dotted 1ine
signify that the enforcement action keys data type can be linked to measurement,
compliance schedule and single event violations.
— ThE EFRUB T RE E TYPOS EXSTON EAO OF ThE 10 PWY CM. REOlON t FOES
2
12/27/93
SDC-0055-034-CL-2005?
-------
Permit Compliance System (PCS) QNCR Training
2.0 PCS Data Entry As It Relates To The QNCR
2.1 Permit Facility Data
The majority of the data to be entered on the Facility record comes from the application for a
permit. The following PCS-ADE screens are used to enter this information into the PCS
database.
2.1.1 FAC1
Facility Data Screen #1
08:31:23 FACILITY/PART 1 PCDEFAC I
04/09/92 SCREEN ID FAC 1
PERMIT # ________ TRANS CODE —
FACILITY _____________________________ _____________________________
NAME _____________________________ _____________________________
COGNIZANT OFFICIAL _____________________________ TELEPHONE __________
CITY CODE _____ COUNTY CODE —
SIC CODE — CODE OF FEDERAL REGULATIONS_
TYPE APPLICATION — FACILITY OWNERSHIP —
ORIGINAL PERMIT ISSUE DATE ______ ISSUED BY —
REISSWJICE I —
PRETREATMEJIT REQUIRED FEDERAL GRANT —
HEW SOURCE/DISCHARGE CODE — NEW SOURCE/DISCHARGE DATE ______
FINAL LIMITS — WATER QUALITY LIMITS —
FACILITY INACTIVE CODE — FACILITY INACTIVE DATE ______
CONSOLIDATED PERMiT U ___________ NEEDS SUFFIX —
STATE PERMIT I ________ FEDERAL PERMIT I ____________
CONTROL AUTHORITY PERMIT U _________ RECEIVING POTW PERMIT U _________
REGIONAL PRIORITY PERMIT — SUB-REGION —
ATTORNEY — ENGINEER — AVERAGE DESIGN FLOW _____
ACCEPT? YIN/N: Y FAC2 DATA? Y/N:N SLUDGE DATA? T/N:N VERSION 2.2 05/04/90
Acronyms and Field Len2ths
NPJI)*! [ PERMIT # ] (field length = 9 characters)
FNMS* [ FACILITY NAME SHORT] (field length =30 characters)
SIC2* [ SIC CODE] (field length = 4 characters)
TYPO* [ FACILITY OWNERSHIP] (field length = 3 characters)
YFYP* [ FACILITY TYPE] (field length = 6 characters)
IACC [ FACILITY INACTIVE CODE] (field length = 1 character)
IADT* [ FACILITY INACTIVE DATE] (field length = 6 characters)
FDGR* [ FEDERAL GRANT INDICATOR] (field length = 1 character)
FLIN1 [ FINAL LIMITS INDICATOR] (field length = 1 character)
SDC-0055-034-CL-2005A 12/27/93 3
-------
QNCR Training Permit Compliance System (PCS)
2.1.2 FAC2
Facility Data Screen #2
08:31:23 FACILiTY/PART 2 P EFAC2
04/06/92 SCREEIt ID: FAC2
PERMiT # _______ TRMS C E C
FACIL ITY
IIA HE
ARCHIVAL I NDICATOR RIVER BASIN # _____
RECEIVING WATERS ... ...
- - - EV1DENTIART HEARING - - - -
HEARING INDICATOR — FILE S __________ IS JE C )ES —
D OCKET# _______
- - - - USER DATA ELEMENTS - - - -
ROF 1 RDF2 RDF3 — RDF4 — RDF S RDF6 — RDF7 ______ RDF8 ______
RDF9 _____ ROF 1O _____________________________________________
- • - - N’4P ELEI ENTS - -. - —
NPSC-NMP STAT — NPFF-NMP FIT NPSO-IIMP OTR
PREVWJSYEARMANUALQHCRSTATUS 1 _2_3_6_
CURREHT TEAR MANUAL QNCR STATUS ¶ — 2 — 3 — 4 —
ACCEPT? Y/M/M: Y SLWGE DATA? YIN: N VERSiON 2.1 03/12/90
The PERMiT NUMBER, TRANS CODE and FACILITY NAME fields are carried over
from the previous screen, if Y was the response to the “MORE FAC2 DATA?” prompt.
Otherwise, enter the PERMIT NUMBER on this screen.
Acronyms and Field Lengths
PYMS (field length = 4 characters)
[ PREVIOUS YEAR MANUAL QNCR STATUS)
CYMS* (field length = 1 character)
[ CURRENT YEAR MANUAL QNCR STATUS]
4 12/27/93 SDC-OO55-Q34-CL-2OO5i
-------
Permit Compliance System (PCS)
QNCR Training
2.1.3 FACA
Facility Data Screen #3
The TRANS CODE is a C and cannot be changed.
Acronyms and Field Lengths
MNAM (field length =30 characters)
MSTI (field length =30 characters)
MST2 (field length = 30 characters)
MCTY (field length =23characters)
MSTT (field length = 2 characters)
MZIP (field length = 9 characters)
ANAM (field length =30 characters)
AST1 (field length =30 characters)
AST2 (field length = 30 characters)
ACTY (field length =23 characters)
ASTT (field length = 2 characters)
AZIP (field length = 9 characters)
[ FACILITY NAME]
[ ADDRESS LINEI]
[ ADDRESS LINE2]
[ CITY]
[ STATE]
[ ZIP]
[ FACILITY NAME]
[ ADDRESS LINE1]
[ ADDRESS LINE2I
[ CFFY]
[ STATE]
[ ZIP]
SDC 00534-tL-2O05A
1ZI27I9 i
-------
QNCR Thiining Permit Compliance System (PCS)
2.2 Compliance Schedule Family
Compliance schedules shown in the final permit and/or an enforcement action are events that
must be completed by dates specified in the permit and/or the enforcement action. For
example, a permit might contain a schedule for completing modifications to their treatment
facility. The schedule would specify when construction is to begin, when construction is to
end and when the permittee must attain final limits with the permit. This is called a
construction schedule and each event is represented as a separate compliance schedule record
in PCS. The following PCS-ADE screen is used to enter the compliance schedule event
records.
Compliance Schedules Screen
¶5:21:03 COMPLIAIJCE SCHEDULES PCDECSCH
01/14 193 SCREEN ID : CSCH
PERMIT # (NPID) ________ TRANS CODE —
CONPLIAKCE SCHEDULE NUMBER (CSCH)
DATA SWRCE CODE (DSCO) —
COMPLIANCE SCHEDULE EVENT CODE (EVNT) _____
U UAIICE SCHEDULE EVENT SCHEDULED DATE CDTSC) ______
FLIAN SCHEDULE EVENT ACTUAL DATE (OTAC) _____
LIM I REPORT RE IVED DATE (DTRC) _____
COMPLIANCE COMMENT (COP l) ______________________________
DOCKET NUMBER CCSFN) ____________
USER DATA ELEMENT #1 CROCi) — USER DATA ELEMENT #2 CRDC2 )
ACCEPT? Y/K/N/N: Y VERSION 2.1 03/12/90
Acronyms and Field LenEths
CSCH*! (field length = 2 characters
[ COMPLIANCE SCHEDULE NUMBER]
DSCD ! [ DATA SOURCE CODE] (field length = 4 characters
EYNT*! (field length = 5 characters
6 12/27/93 SDC-0055-034-CL-20052
-------
Permit Compliance System (PCS) QNCR Training
[ COMPLIANCE SCHEDULE EVENT CODE]
DTSC* _____ (field length = 6 characters)
[ COMPLIANCE SCHEDULE EVENT SCHEDULED DATE]
DTAC* ____ (field length = 6 characters)
[ COMPLIANCE SCHEDULE EVENT ACTUAL DATEI
DTRC* (field length = 6 characters)
[ COMPLIANCE REPORT RECEIVED DATE]
If a violation is recognized, PCS creates a Compliance Violation (CV) record with the same
key data elements as the Compliance Schedule (CS) record (CSCH, DSCD, EVNT), a
Compliance Schedule Violation Code (CVIO), and a Compliance Schedule Violation Date
(CVDT).
CVIO (field length = 3 characters)
(COMPLIANCE SCHEDULE ‘VIOLATION CODE’]
dO Reported Late (DTRC is greater than DTAC)
C20 Achieved Late (DTAC is greater than DTSC)
C30 Unachieved (DTRC is entered but DTAC is blank)
Not Received (Both DTRC and DTAC have not been entered)
CVDT (field length = 6 characters)
[ COMPLIANCE SCHEDULE ‘VIOLATION DATE’]
SDC-0055-034-CL-2005A 12/27/93 7
-------
QNCR Training Permit Compliance System (PCS)
2.3 PIpe Schedule Data Type
The Pipe Schedule record contains general information about the outfall of the discharge as a
whole, for example the date to begin discharging, the date to submit the monitoring reports
to the regulatory authority, and the dates the limits are in effect. The information for this
record is found in the final permit.
The following two PCS-ADE screens are used to enter the data for the Pipe Schedule record.
2.3.1 OFLG
Outfall Screen #2
08:44:13 OUTFALL PCOEOFLG
04 106/92 SCREEN ID: OFLG
PERMIT ________ TRANS CODE —
DISCHARGE WI4BER REPORT DESIG?MTOR —
INITIAL REPORT DATE ______ REPORT UNITS OUTFALL TYPE —
NUMBER OF UNITS IN REPORT PERI — TOTAL NLJ1SER OF REPORTS OLIE
INITIAL EPA SURI4ISSIOIL DATE _____ EPA SUBMISSION UNIT —
NL 48ER OF UNITS II EPA SUBMISSION PERIOD
INITIAL STATE SUBMISSION DATE ______ STATE SUBMISSION UNIT —
NUMBER OF UNITS IN STATE SUBMISSION PERIOD —
PIPE DESCRIPTION —
SEASONAL OMR PRINTING INDICATORS ___________
INITiAL LIMIT DATES: START ______ END ______
INTERIM LIMIT DATES: START ______ END ______
FINAL LIN(T DATES: START ______ END ______
TYPE EFFLUENT hASTE — AGEKCY REVIEWER _____ MI I I # CF DMR LINES
PIPE INACTIVE CODE PIPE INACTIVE DATE ______
ACCEPT? 1 / K /N/ I l: V OFLI DATA’ V/N: N SLLI GE DATA? YIN: N VERSION 2.1
03/12/90
Acronyms and Field Lengths
DSCH ! [ DISCHARGE NUMBER] (field length = 3 characters
DRID*! [ REPORT DESIGNATORJ (field length = I character)
DSDG! (field length = 4 characters
[ COMBINED DISCHARGE NUMBER AND DESIGNATOR]
STRP* [ INITIAL REPORT DATE] (field length = 6 characters
REiJN* [ REPORT UNITS] (field length = 1 character)
OUTT. [ OUTFALL TYPE] (field length 1 character)
8 12/27/93 SDC-OO55-O34-cL-2OO5
-------
Permit Compliance System ( PCS )
QNCR Tr2ining
NRI)TJS
[ NUMBER OF UNITS IN REPORT PERIODI
NORP [ TOTAL NUMBER OF REPORTS DUE]
STSU*
(INiTIAL EPA SUBMISSION DATEI
SUUN* [ EPA SUBMISSION UNIT]
NSUN
[ NUMBER OF UNITS IN EPA SUBMISSION PERIOD]
STSS
[ INiTIAL STATE SUBMISSION DATE]
SUUS* [ STATE SUBMISSION UNITJ
NSUS
[ NUMBER OF UNITS IN STATE SUBMISSION PERIOD]
PIPE [ PIPE DESCRIPTION]
ALLP*
[ SEASONAL DMR PRINTING INDICATORS]
I1SD
[ INITIAL LIMITS DATES: START]
fl J)* [ INITiAL LIMITS DATES: END]
MLSD
[ INTERIM LIMITS DATES: START]
fJ J)* [ INTERIM LIMITS DATES: END]
FLSD [ FINAL LIMITS DATES: START]
FLED* [ FINAL LIMITS DATES: END]
MDML [ MIN # OF DMR LINES]
3 characters)
6 characters)
= 1 character)
= 2 characters)
(field length = 6 characters)
(field length =25 characters)
(field length =12 characters)
(field length = 6 characters)
(field length = 3 characters)
(field length =
(field length
(field length
(field length
(field length =
(field length
1 character)
2 characters)
(field length
(field length
(field length
(field length
(field length
(field length
= 6 characters)
= 6 characters)
= 6 characters)
= 6 characters)
= 6 characters)
= 2 characters)
SDC-0055-034-CL-2005A
12/27/93
-------
QNCR Training Permit Compliance System (PCS
2.3.2 OFLT
Outfall Treatment Type Screen #2
08:18:15 OUTFALL TRMT TYPE P O DEOFLT
01/04/90 SCREEN ID: OFLT
PERMIT I ________ TRANS CODE C
DISCHARGE NI. WER — REPORT DESIGNATOR
OUTFALL TREATMENT TYPE CODES
DNR FORM COMMENTS
USER DATA ELEMENT #1 USER DATA ELEMENT #2 ______
ACCEPT? Y/K/NFM: Y VERSION Z 0 07/31/89
Acronyms and Fleid Lengths
DSCH ! [ DISCHARGE NUMBER] (field length = 4 charactersy
DRID ! [ REPORT’DESIGNATOR] (field length = 1 character)
TRET (field length = 24 characters
(OUTFALL TREATMENT TYPE CODES]
P1CM [ DMR FORM COMMENTS] (9 fields of 30 characters each)
10 12/27/93 SDC-OO55-O34-CL-2005.
-------
Permit Compliance System (PCS) QNCR Training
2.4 Parameter Limits Data Type
The information for this data type is found in the final permit along with the pipe schedule
information. The following two screens are the PCS-ADE data entry screens used to enter
the ParameterLimit and Limit Modification information.
2.4.1 LJMS
Effluent limits Screen
11:31:34 EFFLUENT LIMITS P ELINS
11/23/92 SCREEN ID: tINS
PERMIT ( lIPID) ________ TRANS CODE —
DISCHARGE IIUMBER (PLDS) REPORT DESIGNATOR (PLRD) —
LIMIT TYPE CLTYP) PARAMETER (PRAM) _____ MONITORING LOCATION (MLOC) — SEASON —
(SEAN)
FREQUENCY OF ANALYSISCFRAJI) _____ SAMPLE TYPE(SANP) — CONTESTED PARAMETERCCONP)
SEASONAL DMR PRINTING INDICATORS CALLS) ____________ STANDARD BASIS CODE (STBA)
- - - - QUANTITY LIMITS - - - - - - - - CONCENTRATION LIMITS - - - -
(LQUC) (LQAV) (LQMX) (LCUC) (LCNN) (LCAV) (LCNX)
UNIT CODE AVERAGE MAXIMUM UNIT CODE M INIMIm AVERAGE MAXIMUM
- - QUANTITY STAT BASE CODES - - - - CONCENTRATION STAT BASE CODES - -
(LQAS) CLQXS> (LOIS) (LCAS) (LCXS)
AVERAGE MAXIMUM MINIMUM AVERAGE MAXIMUM
HIN/AVG
OVERRIDES — CLCNO) (LCAO)
DOCKET NUMBER (PLFN) ____________
USER DATA ELEMENT #1 — #2 ______ ______
ACCEPT? ‘V/K/R/N/M: Y VERSION 2.2 06/12/92
Acronyms and Field Lengths
PLDS*! [ DISCHARGE NUMBER] (field length = 3 characters)
PLRD ! [ REPORT DESIGNATOR] (field length = I characters)
PDSG! (field length = 4 characters)
[ COMBINED DISCHARGE NUMBER AND DESIGNATOR]
LTYP*! [ LIMIT TYPE] (field length = 1 character)
PRAMS! [ PARAMETER] (field length = 5 characters)
MLOC ! [ MONITORING LOCATION] (field length 1 character)
SEAN*! [ SEASON] (field length 1 character)
12127/93
-------
QNCR Tr&ning Permit Compliance System (PCS)
STAT* [ STATISTICAL BASE CODE] (field length = 2 characters:
STBA [ STANDARD BASIS CODE] (field length = 1 character)
FRAN [ FREQUENCY OF ANALYSIS] (field length = 5 characters
SAMP [ SAMPLE TYPE] ___ (field length = 2 characters
CONP* [ CONTESTED PARAMETER] (field length 1 character)
ALLS (field length= 12 characters)
[ SEASONAL DMR PRINTING INDICATORS]
LQUC (field length = 2 characters)
[ QUANTiTY LIMITS: UNiT CODE]
LQAV* [ QUANTITY LIMITS:AVERAGEJ (field length 8 characters)
LQMX [ QUANT1’FY LIMITS: MAXIMUM] (field length = 8 characters)
LCUC* (field length = 2 characters)
[ CONCENTRATION LIMITS: UNIT CODE]
LCMN (field length = 8 characters)
[ CONCENTRATiON LIMiTS: MINIMUM]
LCAV* (field length = 8 characters)
[ CONCENTRATION LIMITS: AVERAGE]
LCMX* (field length = 8 characters
[ CONCENTRATION LIMITS: MAXIMUM]
LQAS (field length = 2 characters
[ QUANTITY AVERAGE LIMITS STAT BASE CODE]
LQXS (field length = 2 characters
[ QUANTITY MAXIMUM LIMITS STAT BASE CODE]
LCMS (field length = 2 characters
[ CONCENTRATION MINIMUM LIMITS STAT BASE CODE]
LCAS (field length = 2 characters
[ CONCENTRATION AVERAGE LIMITS STAT BASE CODE]
LCXS (field length = 2 characters
[ CONCENTRATION MAXIMUM LIMITS STAT BASE CODE]
LCMO (field length = I character)]
[ CONCENTRATION MINIMUM LIMITS STAT BASE CODE]
LCAO (field length = 1 character) 1
[ CONCENTRATION AVERAGE LIMITS STAT BASE CODE]
12 12/27/93 SDC-0055-034-CL-2005A
-------
Pennit Compliance System (PCS)
QNCR Training
2.4.2 LIMM
Limit Mod(ficwions Screen
11:32:14 LIMIT MODIFICATIONS PCDELI
11/23/92 SCREEN ID: UN4
PERMIT # (lIPID) _________ TRANS CODE —
DISCHARGE NLJ4BER (P 1 . 0 5 ) — REPORT DESIGNATOR (PLED) —
UNIT TYPE — PARAMETER _____ MONITORING LOCATION — SEASON —
(LTYP) (PRAM ) (NLOC) (SEAN)
MODIFICATION N1.PIBER (NOON) —
(ELSO) (ELED) (Cots)
NODIFtCAT 1ON PERIOD: START _____ END _____ CHANGE OF
STANDARD BASIS CODE CSTBA) — LIMITS STATUS
FRE JEJICY OF ANALYSIS _____ SAIWLE TYPE — CONTESTED PARAIETER —
(FRAN ) (SN IP) (CONP)
SEASONAL ONE PRINTING I N DICATORS CALLS) ___________
- - - - QUANTITY LIMITS - - - - - - - - CONCENTRATION LIMITS - - - -
(LOUC) (LQAV) (LOMX) (LOX) (LCMN) (LCAV) ( ( . 0 (X)
UNIT CODE AVERAGE MAXIMUM UNIT CODE MINIMM AVERAGE MAXIMUM
- - QUANTITY STAT BASE CODES - - - - CONCENTRATION STAT BASE CODES - -
( ( .0* 5) (I.QXS) (L OIS) (LCAS) CLCXS)
AVERAGE MAXiMUM MINiMUM AVERAGE MAXIMUM
— — KIN /AVG — —
OVERRIDES
(LCMO) CLCAO)
DOCKET NUMBER _______ DATA ELEMENT #1 — #2 ______ #3 ______
(PLFII)
ACCEPT? V t V VFRSTAU 2.. ; nA 117/92
Acronyms and Field Lengths
MODN!* [ MODIFICATION NUMBER] (field length = 1 character)
ELSD (field length = 6 characters)
[ MODIFICATION PERIOD: STAR11
ELED [ MODIFICATION PERIOD: END] (field length = 6 characters)
COLS* [ CHANGE OF LIMITS STATUS] (field length = 2 characters)
PLFN* [ DOCKET NUMBER] (field length = l2characters)
SUL-U fl )-U34-CL-2UU )A
12/27/93
13
-------
QNCR Training Permit Compliance System (PCS)
2.5 Measurement Violation Data Type
The information for this data type comes from the Discharge Monitoring Reports (DMRs) the,
pennittee must complete and send to the, regulatory agency. The following two PCS-ADE
data entry screens are used to enter the Measurement records.
2.5.1 EVIO
Effluent Measurements Key Screen
06, 0 1, 9 3: p 5• P EEEYE
1O O8 54 SCREEN 10: EVIO
EFFLUENT EASURENENTS
KEY SCREEN
PERMIT g ________ TRANS CI E
DO YOU VISH TO USE THE CYCLE OPTION? (YIN) —
MONITORING PERIOD END DATE ______ - -
• DO YOU WSH TO CYCLE THROUGH ‘PREVIOUS’ LIMITS? (Y/N) N
DISCHARGE NUMBER —
REPORT DESIGNATOR —
PARAMETER C E
NONITOR IIIG LOCATiON —
PIPE N0017 CT/N) K (NOT ALLOWED WITH CYCLE OPTION)
RANGE CHECKING? (YIN) N
RANGE TABLE ID: _____
USE NATiONAL DEFAULT TABLE? (V/N) N
ACCEPT? YIN/K: V VERSION 2. 10/01/92
Acronyms and Field Lengths
DO YOU WISH TO USE THE CYCLE (field length = 1 character)
OPTION? (Y/N) __
DO YOU WISH TO CYCLE THROUGH (field length = 1 character)
‘PREVIOUS’ LIMITS? (YIN)
MVDT ! (field length = 6 characters
[ MONITORiNG PERIOD END DATE]
14 12/27/93 SDC-0055-034-CL-2005A
-------
rermit Compliance System (PCS) QNCR Training
DSC*! [ DISCHARGE NUMBER] (field length = 3 characters)
DRD*! [ REPORT DFSIGNATORI (field length = I character)
rDSG! (field length = 4 characters)
[ COMBINED DISCHARGE NUMBER AND DESIGNATOR]
ODI* [ PIPE NODI?_(Y/N)] (field length = 1 character)
TPRM [ PARAMETER CODE] (field length = 5 characters)
MLO [ MONITORiNG LOCATION] (field length = 1 character)
SDC-0055-034-CL-2005A 12/27193 15
-------
QNCR Tr2ining Permit Compliance System (PCS
Effluent Measurements Screen #2
10:30:15 MEASUREMENTS PCD EEV IO
12/21/89 TYPE OF LIMIT - SCREEN ID: EV IO
PERMIT * ________ TRANS CODE — DISCHARGE - REPORT DESIGNATOR -
LIMIT TYPE PARAMETER
MONITORING LOCATION SEASON MODIFICATION PIUJIBER PIPE QUALIFIER
- - JAIITITY LiMITS — — - -
AVERAGE MMINLP UNIT NAME
- - - - CONCENTRATION LIMITS - - - -
MINIMUM AVERAGE NAXII M UNIT NAME
-• MEASUREMENTS
QUANTITY CONCENTRATION
MONITORING PERIOD AVERAGE MAX!MLN MINIMAl AVERAGE MAXiMUM
END DATE ______ ________ ________ ________ ________ ________
DMR RECEIVED DATE ______ RNC DETECTION : CODE — DATE ______
RNC RESOLUTION CODE — DATE ______
REPORTED # OF EXCURSIONS — REPORTED FRE JENCY OF ANALYSIS _____
REPORTED SAMPLE TYPE REPORTED QUANTITY UNIT CODE
REPORTED CONCENTRAT ION till IT CODE —
P lO DISCHARGE REASON CODE — C lANGED NEASLMEMENT /VIOLATIOIi DATE ______
ACCEPT? TiC/KIN/I VERSION 2.1 10/06/89
Aèronvms and Field Lengths
This screen appears with the fields on the top portion pre-f.Iled with data currently on the
system from the Limits record. It allows the data entry person to visually verify this
information. These fields are not discussed here as they have been discussed under Effluent
Limits Screen #1. The fields on ‘the bottom portion of the screen, which require data entry,
are described below.
MVDT! (field length = 6 characters
[ MEASUREMENTS: MONITORING PERIOD END DATE]
MQAV* (field length = 8 characters
[ MEASUREMENTS: QUANTITY: AVERAGE]
MQMX* (field length = 8 characters
[ MEASUREMENTS: QUANTITY: MAXIMIJMI
MCMN* (field length = 8 characters
(MEASUREMENTS: CONCENThATION: MINIMUM]
MCAV (field length = 8 characters
16 12127193 SDC’0055 ’03#CL2005:
-------
Permit Compliance System (PCS)
QNCR Training
[ MEASUREMENTS: CONCENTRATION: AVERAGE]
MCMX*
[ MEASUREMENTS: CONCENTRATION: MAXIMUM]
DMRR [ DMR RECEIVED DATE]
SNCE [ RNC DETECTION: CODE]
SNDE [ RNC DETECTION: DATE]
SRCE [ RNC RESOLUTION: CODE]
SRDE [ RNC RESOLUTION: DATE]
REXC [ REPORTED # OF EXCURSIONS]
RFRQ ___
[ REPORTED FREQUENCY OF ANALYSIS]
RSAM [ REPORTED SAMPLE TYPE]
RUNT
[ REPORTED QUANTITY UNIT CODE]
RCUN
[ REPORTED CONCENTRATION UNIT CODE]
NODI* [ NO DISCHARGE REASON CODE]
MVDT
[ CHANGED MEASUREMENT/VIOLATION DATE]
(field length = 8 characters)
(field length
(field length
(field length
(field length
(field length
(field length
(field length
(field length
(field length
= 6 characters)
1 character)
= 6 characters)
= 1 character)
6 characters)
= 2 characters)
5 characters)
= 2 characters)
= 2 characters)
(field length = 2 characters)
(field length
(field length
= 1 character)
= 6 characters)
SDC-0055-034-CL-2005A
I2IZIIYi
1-I
-------
QNCR Training Permit Comptiance System (PCS)
The information for this data type comes from the Discharge Monitoring Report (DMR) that
the permittee must complete and send to the regulatory agency. The user may want to use
this screen when multiple measurements are being entered, as opposed to individual
measurement entry. The following are the two PCS-ADE data entry screens used to enter
the Measurement records.
2.5.2 EDMR
Effluent DMR Data Key Screen #1
- - -
10:08:24 SCREEN ID: EDNR
EFFLUENT DflR DATA
KEV SCREEN
PERMIT # ________
TRANS C E —
DISCHARGE NUMBER —
REPORT DESIGNATOR —
RAI GE CHECKING? (TiN) N
RANGE TABLE ID:
USE NATIONAL DEFAULT: (V/N) N
ACCEPT? V/N/N: V VERSION 2.4 10/01/92
Acronyms and Field Lengths
VDSC ! [ DISCHARGE NUMBER] (field length = 3 charactersy
VDRD*! [ REPORT DESIGNATORJ (field length = 1 character)
12/27/93’ SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) QNCR Training
Effluent DMR Data Screen #2
10:35:15 EFFLUENT DNR DATA . P EED MR
12121189 SCREEN ID : EDMR
PERHIT _________ TRANS CODE
DiSCHARGE NUMBER — REPORT DESIGNATOR —
HONtTORIWG PERIOD END DATE _____
DNR RECEIVED DATE ______
S PIPE NO DISCHARGE REASON CODE
T
A VI R R RR .W
T HI E FREO.SUC . .O
Ii VPRII L I ----QUAMTITY CONCENTRATION------ X OF A N U •
S 0] AVERAGE MAXIMUM MINIMUM AVERAGE HAXDIM C ANAL. M T N I
1: ____ _] _______ _______ _______ _______ _______ — _____ —
2: ___ _____ _____ _____ _____ ___
3: ___ _] _____ _____ _____ _____ _____ ___
4: ___ _____ _____ _____ _____ _____ ___
5: _I _____ _____ _____ _____ — ___
6: ___ _3 _____ _____ _____ _____ _____ ___
1: ___ _____ _____ _____ _____ _____ — ___
I
ACCEPT? Y/IC/PFN/M: K VERSION 2.4 10/01/92
Acronyms and Field Len2ths
The following fields will be displayed from the information entered on the Key Screen:
NPID, TRANS CODE, VDSC, and VDRD.
MVDT*! [ MONITORING PERIOD END DATE] (field length = 6 characters)
DMRR [ DMR RECEIVED DATE] (field length = 6 characters)
NODI* (field length = 1 character)
[ PIPE NO DATA REASON CODE]
VPRM! [ PARAMETER CODE] (field length = 5 characters)
YMLO! [ MOMTORING LOCATION CODE] (field length 1 character)
MQAV* (field length 8 characters)
[ MEASUREMENTS: QUANTITY: AVERAGE]
MQMX* (field length = 8 characters)
[ MEASUREMENTS: QUANTITY: MAXIMUM
MCMN (field length = 8 characters)
[ MEASUREMENTS: CONCENTRATION: MINIMUM]
SDC -0055-034 -CL-2005A 12/27/93 19
-------
QNCR Training
Permit Compliance System (PCS
MCAV t
[ MEASUREMENTS: CONCENTRATION: AVERAGE]
MCMX*
[ MEASUREMENTS: CONCENTRATION: MAXIMUM]
REXC [ REPORTED # OF EXCURSIONS]
RFRQ ___
[ REPORTED FREQUENCY OF ANALYSIS]
RSAM [ REPORTED SAMPLE TYPE]
RUNT
[ REPORTED QUANTITY UNIT CODE]
RCUN
[ REPORTED CONCENTRATION UNiT CODE]
REXC [ REPORTED # OF EXCURSIONS]
NODI* [ NO DISCHARGE REASON CODE]
(field length
(field length
(field length
(field length
(field length
(field length
(field length
(field length
(field length
= 8 characters)
= 8 characters)
= 2 characters)
= S characters)
= 2 characters)
= 2 characters),
= 2 characters)
= 2 characters)
= 1 character)
20
12/27/93
SDC-0055-034-CL-20051
-------
Permit Compliance System (PCS) QNCR Training
2.6 Reissuance Processing
The reissuance process in PCS allows the user to retain a “ghosted TM copy of a permit’s limits
when a new permit is issued to the facility. This accomplishes two important objectives:
first, the current, active limit area is freed for the limits from the new permit; and secondly,
a record is kept of the limits from prevous permits. A key data element, the pipe set
qualifier, allows a distinction to be made between sets of limits. This one-character data
element is present on all pipe, limit, and measurement records, and is maintained by the
system. Although the pipe set qualifier may be retrieved, it cannot be entered by a user.
• Pipe Set Qualifier PIPQ - Pipe Schedule Records
Acronyms: LIPQ - Parameter Limit Records
VIPQ - Measurement Violation Records
• Pipe Set Qualifier 9 Current effluent family records
Values 0-8 Ghosted limits and measurements
0 is the oldest set of ghosted data
Z Measurements without associated pipes and limits
For all reissuance indicators, the following processing takes place:
S Current pipes and limits with non-zero dates are ghosted.
• All pipe schedules are retained and updated with the dates entered with the reissuance
control indicator.
• Limits retained depend on the reissuance indicator used:
- X None of the limits records from the ghosted permit are retained for use in the new
permit.
- L Only limits with a modification number of 0 are retained.
- K For the limit type of the date range entered, the last limits in effect are retained.
Only one date range may be -entered on the Reissuance Data (RCIN) screen.
SDC-0055-034-CL-2005A 12/27193 21
-------
QNCR Training
Permit Compliance System (PCS
Reissuance Data Screen
10 :60:00 REISSUANCE DATA SCREEN PCDERCIN
12/21/89 SCREEN ID: RCIN
PERMIT # ________ TRAIlS CODE C
REISSUAIICE CODE —
ENTER DATE RANGES ( /DD/YY):
INITIAL LIMITS START DATE: ______
INITIAL LIMiTS END DATE: ______
INTERIM LIMITS START DATE: ______
INTERIM LIMITS END DATE: ______
FINAL LIMITS START DATE: ______
FINAL LIMITS END DATE: ______
ACCEPT? YIN/N: Y VERSION 2.0 07/31189
Acronyms and Field Len2ths
RCIN*! (field length = 1 character)
USD (field length = 6 characters:
ILED* (field length = 6 characters;
MISD (field length = 6 characters
MIED* (field length = 6 characters
FLSD* (field length = 6 characters)
FLEI)* (field length = 6 characters)
[ REISSUANCE CODE]
[ INiTIAL LIMITS START DATE]
[ INITIAL LIMITS END DATE]
[ INTERIM LIMITS START DATE]
[ INTERIM LIMITS END DATE]
[ FINAL LIMITS START DATE]
[ FINAL LIMITS END DATE]
12/27/93
SDC-UOO34-CL-2UU5
-------
Permit Compliance System (PCS)
QNCR Training
2.7 Single Event Violation Data Type
Single event violations are violations that are not a part of any other data type in PCS. This
could include the facility operating without a certified operator, an unauthorized bypass of
discharge, etc. The following PCS-ADE screen is used to enter Single Event violations.
Single Event Violations Screen
09:30:03 SINGLE EVENT VIOLATIONS P ESVI0
10/10/89 : SCR ID : SVIO
PERMIT # - TRANS CODE —
VIOLATION CODE ____ VIOLATION DATE _____
RNC DETECTION CODE —
INC DETECTION DATE ______
RNC RESOLUTION CODE
RNC RESOLUTION DATE ______
REGIONAL FIELD I REGIONAL FIELD 2 ______
ACCEPT? V/N/H: V VERSION 2.1 10/06/89
Acronyms and Field Lengths
SVCD! [ VIOLATION CODE] (field length = 5 characters)
SVDT! [ VIOLATION DATE] (field length = 6 characters)
SNCS [ RNC DETECTION CODE] (field length = I character)
SNDS [ RNC DETECTION DATE] (field length = 6 characters)
SRCS [ RNC RESOLUTION CODEI (field length = 1 character)
SRDS [ RNC RESOLUTION DATE] (field length = 6 characters)
SVL-UU -U34-CL-2UU A
12/27/93
23
-------
QNCR Training. Permit Compliance System (PCS)
2.8 Enforcement Action Data Type
Enforcement actions are structured into two records, the enforcement action record (EA), and.
the enforcement action key record (EK).
EA records contain general overview information about the enforcement action, i.e., the EA
code, the date of the EA, docket number, EA comments, etc. There is one Ek record for
each enforcement action.
EK records contain detailed information about the violations that the enforcement action
addresses. They contain the type of violations addressed, and any keys to the violations, if
necessary. There may be many EK records for each EA record.
The top portion of the Enforcement Action (ENAC) screen is used to enter the information
on the EA record. The information below the heading “Violations that caused the
enforcement action to be issued” is used to enter the EK records. If you want to enter EK
records that address all violations of a certain type, put an X in that option. An * in the
option deletes the EK record. The system will generate the transaction to enter the EK
record. If you wish to enter an EK record to address specific violations, place an X in the
Specific Violations Option.
Enforcement Actions Screen
10:55:00 ENFORCEMENT ACTION PCDEENAC
12121/89 SCREEN ID: ENAC
PERMIT # _________ TRANS CODE
ENFORCEMENT ACTION CODE — ISSUED BY — DATE ______
STATUS CODE STATUS DATE ______
DOCKET NUMBER ____________ CLOSURE SCHEDULED DATE ______
• INITIATING PARTY 1 ______ INITIAliNG PARTY 2 ______
RESPONSE DUE DATE ______ RESPONSE ACHIEVED DATE ______
VIOLATION RECOGNITION DATE ______ USER DATA ELEMENT: #1 — #2 ______
- - - - ENFORCEMENT ACTION C U4EI1TS - - - -
#1 ______________ ______________
#3 _________ _________
#5 _________ #6 _________
#7 _____________
#9 _________________________ #10 __________________________
- - - VIOLATIONS THAT CAUSED THE ENFORCEMENT ‘ACTION TO BE ISSUED - -
— ALL NUMERIC EFFLUENT ALL STATE NON-RECEIPT SPECIFIC
— ALL COMPLIANCE SCHEDULE — ALL EPA WON-RECEIPT — VIOLATIONS
— ALL SINGLE EVENTS — ALL EPA + STATE lION-RECEIPT
ACCEPT? V/K/H /M: V VERSION 2.3 11/27/89
24 12/27/93’ . SDC-0055-034-CL-20 05A
-------
Permit Compliance System (PCS)
QNCR Training
Acronyms and Field Lengths
ENAC ! (field length = 2 characters)
EATP! (field length = 2 characters)
ENDT*! (field length 6 characters)
ENST* (field length 2 characters)
ESDT* (field length = 6 characters)
ERFN* _____ (field length = lOcharacters)
EACD (field length = 5 characters)
EIPI (field length = 5 characters)
EIP2 (field length = 5 characters)
ERDT ____ (field length = 6 characters)
EADR (field length = 6 characters)
EVDK (field length = 6 characters)
ECM1 (first 30 characters)
ECM2 (second 30 characters)
ECM3 (third 30 characters)
ECM4 (fourth 30 characters)
ECM5 (fifth 30 characters)
ECM6 (sixth 30 characters)
ECM7 (seventh 30 characters)
ECM8 (eighth 30 characters)
ECM9 (ninth 30 characters)
ECMO (tenth 30 characters)
VIOLATIONS THAT CAUSED ENFORCEMENT ACTIONS TO BE ISSUED
[ ALL NUMERIC EFFLUENT] (field length = I character)
[ ALL STATE NON-RECEWI]
[ SPECiFIC VIOLATIONS]
[ ALL COMPLIANCE SCHEDULEI
[ ALL EPA NON-RECEIPTJ
[ ALL SINGLE EVENTSI
(ALL EPA + STATE NON-RECELPTJ
These fields will automatically generate an Enforcement Key record (except in the case of
SPECIFIC VIOLATIONS) when an X is placed beside one of them, without any additional
data entry. The Enforcement Key record will have an additional Key Data Element called
the ENFORCEMENT KEY VIOLATION TYPE (the acronym is EVTP) with a violation
code depending on the type of violation the X was placed beside. Below is a listing of the
enforcement key violation types that will be generated:
[ ENFORCEMENT ACTION CODE]
[ ISSUED BY]
[ DATE]
[ STATUS CODE]
[ STATUS DATE]
[ DOCKET NUMBER]
[ CLOSURE SCHEDULE DATE]
[ INITIATING PARTY 1]
[ INITIATING PARTY 2]
[ RESPONSE DUE DATEI
[ RESPONSE ACHIEVED DATE]
[ VIOLATION RECOGNITION DATE]
[ ENFORCEMENT ACTION COMMENT #11
[ ENFORCEMENT ACTION COMMENT #2]
[ ENFORCEMENT ACTION COMMENT #3]
[ ENFORCEMENT ACTION COMMENT #41
[ ENFORCEMENT ACTION COMMENT #5]
[ ENFORCEMENT ACTION COMMENT #6]
[ ENFORCEMENT ACTION COMMENT #7]
[ ENFORCEMENT ACTION COMMENT #8]
[ ENFORCEMENT ACTION COMMENT #9]
[ ENFORCEMENT ACTION COMMENT #0]
SUL4JU J34-CL-2UU A
12/27/93
25
-------
QNCR Training Permit Compliance System (PCS
• [ ALL NUMERIC EFFLUENT]
Placing an X beside this field will generate an EVTP of El. This code means that the
enforcement action is tied to all effluent violations with an measurement violation
(MVIO) code of E90, and prior to the enforcement action date.
• [ ALL STATE NON-RECEIFFJ
Placing an X beside this field will generate an EVTP of N2. This code means that the
enforcement action is tied to all effluent non-receipt violations with an MVIO code of
D20, prior to the enforcement action date.
• [ SPECIFIC VIOLATIONS]
Placing an X beside this field will take the system to the Enforcement Action Key Screen ”
An EVTP code must be entered for the EVTP on the Enforcement Action Key Screen.
The Basic PCS Training Manual has detailed explanations. See the section on
“Enforcement Action Examples”.
• [ ALL COMPLIANCE SCHEDULE]
Placing an X beside this field will generate an EVTP of Cl. This code means that the
enforcement action is tied to all compliance schedule violations with a CVIO code of
ClO, C20, C30 and C40, since the last enforcement action date.
• [ ALL EPA NON-RECEIPT]
Placing an X beside this field will generate an EVTP of Ni. This code means that the
enforcement action is tied to all effluent violations with an MVIO code of 1)10 (DMR
overdue) since the last enforcement action date.
• [ ALL SINGLE EVENTS]
Placing an X beside this field will generate an EVTP of Si. This code means that the
enforcement action is tied to all single event violations with any Single Event Violation
Code (SVCD) code since the last enforcement action date.
• [ ALL EPA & STATE NON-RECEIPT]
Placing an X beside this field will generate an EVTP of N3. This code means that the
enforcement action is tied to all effluent violations with an MVTO code of 1)30 (DMR
Overdue) since the last enforcement action date.
26 12/27/93 SDC-OO55-O34-CL-200
-------
Permit Compliance System (PCS) QNCR Training
3.0 Compliance Schedules
There are two kinds of violations for compliance schedules. Violations occur when:
• A permittee achieves a compliance schedule late or not at all.
• .The unachieved compliance schedule is considered RNC and appears on the QNCR,
Quarterly Non-Compliance Report.
3.1 Violation Detection of Compliance Schedule Events
3.1.1 Automatic Violations
Compliance Schedule Violation (CV) records are created when the PCS database is updated
on Monday and Thursday nights. The CV record is created by a program called
COMTRAK, by comparing dates contained in three data elements in the compliance schedule
(CS) record.
Compliance Schedules Screen
15:21 O3 COMPLiANCE SCHEDULES P ECSCH
01/14/93 SCREEN ID: CSCH
PERMIT # (NPID) ________ TRANS CODE
COMPLIANCE SCHEDULE NUMBER (CSCH) —
DATA SOURCE CODE (DSCD)
COMPLIANCE SCHEDULE EVENT CODE CEVNT) _____
COMPLIANCE SCHEDULE EVENT SCHEDULED DATE (DTSC)
COMPLIANCE SCHEDULE EVENT ACTUAL DATE (OTAC) ______
COMPLIANCE REPORT RECEIVED DATE (DTRC) _____
COMPLIANCE COMMENT (C0V4) ____________________________
DOCKET NUMBER (CSFII) ___________
USER DATA ELEMENT #1 (ROd) — USER DATA ELEMENT #2 (RDC2) —
ACCEPT? V/K/N/N: Y VERSION 2.1 03/12/90
SDC-0055 -034-CL-2005A 12/27/93 27
-------
QNCR Tridning
Permit Compliance System (PCS)
Acronyms and Field Len2ths
CSCLI ! (field length
[ COMPLIANCE SCHEDULE NUMBER]
DSCD*! [ DATA SOURCE CODE]’ (field length
EVNT*! _____ (field length
[ COMPLIANCE SCHEDULE EVENT CODE]
DTSC _____ (field length
[ COMPLIANCE SCHEDULE EVENT SCHEDULED DATE]
DTAC 3 ____ (field length
[ COMPLIANCE SCHEDULE EVENT ACTUAL DATE]
DTRC (field length
[ COMPLIANCE REPORT RECEIVED DATE]
If a violation is recognized, COMTRAK creates a CV record with the same key data
elements as the CS record (CSCH, DSCD, EVNT), a Compliance Schedule Violation Code
(CVIO), and a Compliance Schedule Violation Date (CVDT).
= 2 characters)
= 4 characters)
= 5 characters)
= 6 characters)
= 6 characters)
= 6 characters)
28
12/27/93
SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) QNCR Training
Automatic CYLO Codes
Compliance violations are generated by the COMTRAK program. The codes are as follows:
Code Meaning Violation
ClO Reported Late DTRC more than 14 days past DTSC
C20 Achieved Late DTAC> DTSC
C30 Unachieved DTRC entered - DTAC not entered Current date at least
30 days or more past DTSC
C40 Not Received DTAC and DTRC are blank Current date at least 30 days
or more past DTSC
If more than one of the conditions are true, the worst case CVIO will be used (C40 is worse
than C30, etc.). The date that COMTRAK assigns to the Compliance Schedule Violation
Date (CVDT) is the same as the Scheduled Date (DTSC).
NOTE: RNC considers only C30 and C40 violations for the QNCR.
Below are examples of how C20 and C40 compliance schedule violations would appear on a.
Quick Look (QL) Report:
fl Q 2 g. L 2i: qj (These are data
eLem ts fr the
NOTE: This is a C40 violation because both the DTAC and DTRC are not present.
Think about the following :
• Are there any other violation codes that apply to this violation?
• What are they?
SDC-0055-034-CL-2005A 12/27/93 29
-------
QNCR Training Permit Compliance System (PCS)
Notice that the following is a C20 violation because the Achieved Date (DTAC) is greater
then the Scheduled Date (DTSC).
S P Y! I 2I PTh i2 PI (These are ta
eL enta fr the
CS I screen)
02 0002 90199 06/25/91 09/30/91 09/30191 C20 06/25/91
• Why is the following violation considered to be a C40?
P LMI IR !LQ I (These are dete
eL ents fren the
ai screen)
01 0001 91199 04/01/91 C40 04/01/91
• When COMTRAK creates violation codes, they are not updated until the ii update
• after the codes are created.
If a compliance schedule event has a C30 or C40 violation code, the violation code will
change to a C20 if the event was achieved Late or will disappear if the event was achieved on
time (DTAC), has been entered in the update.
30 12/27/93 SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) QNCR Training
3.1.2 Manually Setting Compliance Schedule Violations
If, based on professional judgment, it is determined that a compliance schedule should be a
violation that does not meet the automatic criteria for a violation, it can be manually set.
The manual codes are entered on the CVIO screen. To manually set a compliance schedule
violation, a CV record must be created with the same keys as the CS record, plus a manual
violation code (CVIO) and a date (CVDT).
Manual CVIO Codes
Code Meaning
MlO Manual reported. late violation
M20 Manual achieved late violation
M30 Manual unachieved violation
M40 Manual not received violation
The following example shows how to create a CV record with a manual achieved late
violation.
COMPLIANCE SCHEDULE NUMBER TR
COMPLiANCE SCHEDULE DATA SWRCE CODE 0001
:: : .:: . . coNpuANcc:: ,scHEDuLE ’ EVENT’ CODE o • • ‘ ‘ ..
DATE. ’o21591 ;
. :1
RNC DETECTION: — DATE ______ These f ek witk deteruine
RNC RESOLUTiON — DATE ______ if this vioLatia wILL be on the
Co utt t Les ”195 E ’ ’
s.... ...:.c 0KPUANCE..VI0LAT I O WC O MMENT ‘ ‘ .
USER DATA ELEMENT #2 ‘
‘ , ‘: ‘. . ‘ACCEPT?Y/K/N/N:Y’ .:. ‘ . . . :‘
SDC-0055-034-CL-2005A . 12127/93 31.
-------
QNCR Training Permit Compliance System (PCS
3.2 Reportable Non Compliance (RNC) Detection for Compliance Schedules
3.2.1 Automatic Detection
The RNC program detects RNC for compliance schedules and assigns values to four RNC
data elements on the compliance schedule that indicate these violations are non-compliant,
resolved pending or resolved.
Reportable Non-Compliance (RNC) runs the last weekend of every month. For the months
when the QNCR is due, the RNC program is run every weekend of the previous month. Fo
example, if the QNCR for July through September is due on November 30th, the RNC
program will be run every weekend during the month of November.
The RNC program looks at violations that occurred two months prior to the current month in
which the RNC program is being run. For example, if the RNC program is being run the
last weekend of December, it is looking at violations that occurred in October.
When RNC runs for compliance schedules, it considers data elements that the RNC program
assigns to the CV record.
Ce npliance Schedule Violation Data Type (CS)
QNCR Data Elements
SNCC [ RNC DETECTION CODE] (field length = I character)
This field indicates RNC detection of non-compliance for a particular compliance schedule
violation event.
SNDC [ RNC DETECTION DATE] (field length 6 character
This field contains the actual date reportable non-compliance was detected for a particular
compliance schedule violation event.
SRCC [ RNC RESOLUTION CODE] (field length = 1 character).
This field indicates the resolution status of reportable non-compliance for a particular
compliance event.
12/27193 SDC-OO55-O34-CL-2OO5,
-------
Permit Compliance System (PCS) QNCR Trnining
SRDC [ RNC RESOLUTION DATEI (field length = 6 characters)
This field contains the actual date of resolution of reported non-compliance for a particular
compliance event.
These four data element fields are populated by the RNC program when RNC CS violations
are. detected or resolved.
Compliance Schedule Events are classified into two groups:
• Schedules (Milestones)
•Reports
In the PCS Code Table for Compliance Schedule Event Codes (Table # 020), a CS event is
identified as a schedule or report event by the last character alter the description of the
event. If the last character is an ‘US”, the event is a (S)chedule, if the last character is an
“R”, the event is a (R)eport.
020 COI4PLIAIICE SCHEDULE EVENT CODES
#TABLE-CD #TABLE-DESC
00199 1ST REPORT OF PROGRESS 2R
This indicates this
event is a reporti
020 COMPLIANCE SCHEDULE EVENT CODES
#TABLE-CD #TABLE DESC
03099 BEGIN CONSTRUCTION iS
This indicates this
event is a schedutel
SDC-0055-034-CL-2005A 12/27/93 33
-------
QNCR Tralning Permit Compliance System (PCS)
RNC detection for CS violations is performed differently depending on the type of the CS
event. The values that the RNC program can enter for the RNC detection code (SNCC) are:
Code Meaning Violation
S Schedule RNC violation DTAC is blank. The current
date (the thte the RNC
program is running) is at
least 90 days or more past
the DTSC.
N Report RNC violation DTAC is blank. The current date (the date the
RNC program is running) is at least 30 days or
more past the DTSC.
When the detection code (SNCC) values have been entered, the detection date (SNDC) is set
with the date the event became an RNC violation:
• DTSC + 90 days for SNCC=S;
• DTSC + 30 days for SNCC=N.
• The SRCC is set to 1, or Unresolved RNC.
Examples of RNC:
Examnle 1 :
There is a compliance schedule record where the event code indicates that it is a (R)eport.
EVNT=91508 (Materials Containment Plan)
DTSC=062590
DTAC=blank
DTRC=blank
Today is 073190
Remember that, in order for a violation to be created, two steps must occur.
• When COMTRAK runs, a CV record with a violation code of C40 is created.
34 12127/93 SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) QNCR Training
• When RNC runs the RNC fields for compliance schedules will be populated.
SNCC=N (DTAC is blank, and we are 30 days past DTSC)
SNDC=072590 (DTSC + 30 days)
SRCC=1 (Unresolved)
...,. . . .• ....
. . . .
SDC-0055-034-CL-2005A . 12/27/93 . 35
-------
QNCR Training Permit Compliance System (PCS)
Example 2 :
There is a compliance schedule record where the event code indicates that it is a (S)chedule.
EVNT=60699 (Corrective Action Plan Submitted)
DTSC=043091
DTAC=blank
DTRC = blank
Today is 073191
When COMTRAK ran, a CV record with a violation code of C40 was created.
When RNC runs the RNC fields for compliance schedules will be populated.
SNCC=S (DTAC is blank, and we are 90 days past DTSC)
SNDC=072991 (DTSC + 90 days)
SRCC=1 (Unresolved)
An example of this appears below :
I
CSCH OSCO EVWT OTSC DTAC OTRC CVIO CVDT SNCI SNDC
02 0001 60699 04/30/91 040 04/30/91 S 07/29191 1
Below is an example of how these violations would appear on the QNCR:
HATERIALS CONTAINMENT PLAN 02 RPT 06/25/90 NC 07/25/90 3D REPORT OVERDUE
CORRECTIVE ACTION PLAN SUBMTD 02 SCH 04/30190 MC 07/29/90 2B COHPL SCHEDULE
VIOLATION
This is the description This is the This is the This is This is the A desc.
of the event code, scheduLe date from the yb. subparagraph of the
nui* er CSCN. CVDT. status, of the Regs vioLation.
for this vio.
This is from the SNCC code.
RPT Is from SNCC=N so it is a This is the
reporting vioLation. SCH is status date.
from SNCC=S so it is a scheduLe For MC it is
vioLation, the same as
SIIOC.
36 12/27/93 SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) QNCR Training
Think about the foI1owin :
• You have a compliance schedule record where the event is 03099 (Begin Construction - a
schedule event).
DTSC=020191
DTAC =021591
DTRC=022891
- What will happen when COMTRAK runs?
What will happen when RNC runs?
• You have a compliance schedule where the event is 15599 (Operations and Maintenance
Report - is a report event).
DTSC= 123191
‘ DTAC=blaiik
DTRC= 122591
Today is 012592
- What will happen when COMTRAK runs?
-. What will happen when RNC runs?
SDC-0055-034-CL-2005A 12/27/93 37
-------
QNCR Training Permit Compliance System (PCS)
3.2.2 Manual Detection of.RNC for Compliance Sehedule Violations
If a violation does not meet the automatic criteria, and, based on QNCR regulations, it
should be RNC, the RNC codes can be set manually.
To manually set RNC, a CV record must exist (or one must be created) before entering the
appropriate manual detection codes in the RNC detection (SNCC), date (SNDC), and
manual resolution (SRCC) fields.
The following manual detection codes can be used for compliance schedule violations. They
can be found in Table #195 of the PCS Codes and Descriptions Manual.
E (manual 2F - permit narrative)
F (manual 2G - violation of concern)
Q (manual 2B - pretreatment)
W (manual 2E - deficient report)
You will probably want to set SRCC to A (Manual Unresolved).
Think about the following :
Be prepared to answer the questions on the following page.
PERMIT # 1D0022 0 55 TRANS CODE C COMPLIANCE VIOL. SCREEN ID: CVIO
COMPLIANCE SCHEDULE NUMBER 02
COMPLIANCE SCHEDULE DATA SOURCE CODE 0001
COMPLIANCE SCHEDULE EVENT CODE 01999
VIOLATION CODE C20 VIOLATION DATE 021591
VIOLATiON DATE SCHEDULED ______
VIOUTION DATE RESOLVED ______
RNC DETECTION: — DATE ______ These fields will deter.ine
RNC RESOLUTION: — DATE _____ if this violation will be on the
QN . Cw ult tthtes 195 J 390.
COMPLIANCE VIOLATION COMMENT ____________________________
USER DATA ELEMENT #1 — USER DATA ELEMENT #2 ______
ACCEPT? V/K/N/H: V
38 12/27/93 SDC-0055-034-CL-20052
-------
Permit Compliance System (PCS) QNCR Training
S For 1D0022055, there is a compliance schedule event that already has a CV record, but
does not meet automatic RNC criteria.
- CS Record CSCH=02
DSCD =0001
EVNT=01999 (ADVERTISE FOR BIDS)
• DTSC=021591
DTAC = 042991
DTRC =042991
- CV Record CVIO=C20
CVDT=021591
Why doesn’t it meet automatic RNC criteria?
How would you indicate that this violation is a violation of concern, and flag that it is RNC?
(You determined• RNC on 051691.)
SDC-0055-034-CL-2005A 12127/93 39
-------
QNCR Training Permit Compliance System (PCS)
33 Resolved Pending and Resolving RNC for Compliance Schedules
3.3.1 Automatic Resolved Pending
A violation is considered to be resolved pending when:
• A formal enforcement action (EA) is entered addressing the violations.
• An extended compliance schedule (CS) is entered.
• The EA and CS are linked through a docket number.
Automatic resolved pending occurs when:
• The resolution code (SRCC) will change to 3 (RP-DUE TO FORMAL EA).
• The resolution date (SRDC) will be the date of the enforcement action (ENDT).
NOTE: In order for PCS to correctly Resolve Pending (RP) and Resolve (RE) any
violation, jj of the following pieces must be entered correctly:
- A formal enforcement action record (with an enforcement action code of 2 or 3)
addressing the compliance schedule violations and enforcement action date
(ENDT) within the QNCR window.
- EK records that are linked to the violations on the ENAC screen (Cl or C2
violations).
- A new compliance schedule from the enforcement action and the CSCH must be
one of those identified in Chapter 8 of the PCS Data Entry and Update Manual a.
causing RP (i.e., a CSCH of CC, DA, DB, DC, DD, DE, DZ, DF, GA, HA,
HC, JA, MC, or PT). These are called “extended” CSCH numbers.
- Identical docket numbers must be entered on both the EA and extended CS
records, in exactly the same manner - either right or left justified on both records. 1
40 12/27/93 SDC -OO55-O34-CL-2OO5
-------
Permit Compliance System (PCS) QNCR Training
Example :
For the following compliance schedule violation, a formal enforcement action (Administrative
Order) was taken:
— —
ENFORCEMENT ACTION
PERMIT # CNPID) 1D0022055 TRANS C E N SCREEN ID: EMAC
ENFORCEMENT ACTION; C E (ENAC) 21 IS JED BY CEATP) E DATE (ENDT) 032191
STATUS CODE (ENST) - STATUS DATE (ESOT) ______ These fields at be fi(t cut
in order to resolve (RE) the ElIAC
0OC ET N1JIBER (ERFN) a8-154 S_ CLOSURE SCHEDULE DATE CEA ) ______ -
INITIATING PARTY I (E IPI) ______ INITIATING PARTY 2 (EIP2) ______
RESPONSE DUE DATE CERDT) ___________ RESPONSE ACHIEVED DATE (EADR) ____________
VIDUTIOM RECOGNITION DATE (EVDE) ______ USER DATA ELEMENT; #1 — (RDHI) #2 CR0 1 12)
- - - -ENFORCEMENT ACTION COIB ENT (EON 1- 10)
#1 __________________ #2 __________________
#3 ___________________ #4 ___________________
#5 __________________ #6 __________________
#7 ___________________ #8 ___________________
#9 ___________________ #10 _________________
- - - VIOLATIONS THAT CAUSED ENFORCEMENT ACTIONS TO BE iSSUED - - -
— ALL NUMERIC EFFLUENT — ALL STATE Nail-RECEIPT SPECIFIC VIOLATiONS
X ALL COMPLIANCE SCHEDULE — ALL EPA NON-RECEIPT
ALL SINGLE EVENTS — ALL EPA • STATE NON-RECEIPT
ACCEPT? YIK/N/M: Y
The Administrative Order (AO) identified this violation as a reporting violation and set up a
compliance schedule for the permittee in order to return to compliance with the permit.
First, an enforcement action record is entered with a docket number. An enforcement action
key record is generated with a violation type of Cl, which links the enforcement action to all
compliance schedule violations since the last enforcement action was issued.
ENAC ENDT EATP ERFN EVTP ENST ESDT
21 03/21/91 E 88-154WW 5S Cl
SDC-0055-034-CL-2005A 12127193 4f
-------
QNCR Training Permit Compliance System (PCS)
Next, a compliance schedule from the enforcement action is entered using one of the
extended compliance schedule numbers from Table #175 of the PCS Codes and Descriptions
Manual. A docket number is also entered with each new compliance schedule. It must be
the exact docket number from the enforcement action record, and must be entered in the
same fashion.
The Compliance Schedule screen looks like this:
WIPLJANCE SCHEDULES
PERMIT # (NPID) 1D0022055 TRANS CODE N
COMPLIANCE SCHEDULE NUMBER (CSCH) DC This is a exterifed c tionce sdie i1e
DATA SOURCE CODE CDSOD) 0001
COMPLIANCE SCHEDULE EVENT CODE (EVNT) 03099
COMPLIANCE SCHEDULE EVENT SCHEDULED.DATE CDTSC) 053191
COMPLIANCE SCHEDULE EVENT ACTUAL DATE COTAC) ______
COMPLIANCE REPORT RECEIVED DATE CDTRC) ______
COMPLIANCE COMMENT (C I4) ______________________________
DOCKET NUMBER (CSFN) 88-15WJSS_ Enter this in same fashion as EKAC screen.
USER DATA ELEMENT #1 (RDC1) — USER DATA ELEMENT #2 CRDC2) —
ACCEPT? /K/N/M: Y
Here is a QL report showing the CSCH codes:
QI £ E
DC . 0001 03099 05/31/91
88-154WWSs
DC. :OODi04599 12/31/91
88-154WSS
42 12/27/93 SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) QNCR Training
The compliance violation record would then change to look like this:
DTSC 2I DTRC £ 2 i sNCc S C S CC ! 2
02 0002 90508 06/25/90 C40 06/25/90 N 07/25/90 3 03/21/91
i a
• a
SRCC is Date of
now 3 the EA
RP-due
to format
EA.
This is the way it would appear on the QNCR:
MATERIALS COHTAINIIENT PLAN 02 RPT 06/25/90 RP 03121/91 30 REPORT OVERDUE
+ ,
* a
* a
* $
It Is now The date
Resolved of the EA
• • • S Pending-RP . 5: • •• S
SDC-0055-034-CL-2005A 12/27/93 43
-------
QNCR Training Permit Compliance System (PCS
3.3.2 Manual Resolved Pending
System detected RNC may be manually set to Resolved Pending (RP) with resolution codes
of 7 or 8 in the SRCC field. A date must also be provided for SRDE. Manually detected
RNC (except those detected with manual codes of X, Y or Z) must be manually set to RP
with codes of 7 or 8 in the SRCC field. The date must also be entered in SRDE.
44 12/27/93 SDC-OO55-O34-CL-2OO
-------
Permit Compliance System (PCS) QNCR Training
3.3.3 Automatic Resolution of Compliance Schedules
Automatic Resolution will take place in one of two ways:
• The user enters the DTAC. The violation will be resolved and the SRCC will be
changed to 2 (RE-Back into compliance) in the next regular PCS update provided DTAC
is within the QNCR window. The Resolution Date (SRDC) will be set to the Achieved
Date (DTAC).
Consider the following violation:
CSCH 0S DTSC 2I £!12 2i SN SMOC SRCC SRDC
02 0002 90508 06/25190 C40 06/25/90 N 07/25/90 1
The permittee sent a letter stating that this event was achieved on September 30, 1991. After
the data has been entered, the record will look like this:
CSCH DSCD EVNT DTSC DTAC OTRC CVIO CVDT SNCC SNUC SRCC SRDC
02 0002 90508 06/25/90 09/30/91 09/30/91 C20 06/25/90 N 07125/90 2 09/30/91
The viotation code changes to Resotuflon The date
ref tect that it was reported code changes the s ae
(atel to a 2. as OTAC.
Because resolution of the violation occurred as a result of the DTAC being entered, the
SRCC will be changed to a 2 in the next regular update of PCS. The system does not have
to wait for the RNC program to run again for this. The resolution will appear on the QNCR
as follows:
MATERIALS
CONTAINMENT PLAN
02 RPT
06/25/90
RE
09/30/91
3D REPORT
OVERDUE
i
I
I
I
It
is
now The
date
:
•
.
Re
sot
véd .: : fr
au; S
L)CU5 -&J34 -CL-2UU A 12127/93 45
-------
QNCR Training
Permit Compliance System (PCS)
• Violations previously set to Resolved Pending (RP) by the system, due to entry of an
enforcement action and extended compliance schedule, are set to Resolved RE when
the PA is closed with an ENST of CL and ESDT is within the QNCR window. The
following violation is in RP because of a formal enforcement action.
The EA is closed on April 13, 1992. The closure date was entered in ESDT, on the EA
record, and appears below:
ENAC ENDT EATP ERFN EVTP ENSI ESDT
21 03/21/91 E 88- IS4WSS Cl CL 04/13/92
The compliance violation record changes as follows:
CSCH Q ! I
2i ia L2 i
S CC SNDC SRCC
02
...
0002 91508
06/25/91
:
C40
06/25/91
N
07/25/91 5
,....
,
04/13/92
..; i. .
I
.
:.
:.
. .r•
•
•
.
ResoL ion
code is 5
The date..
Iswhen..
.
. ..
..... .
. .
.
. ..
. . ‘
. •.
theEAWaS :
àLosed .. . .
..
46
12/27/93
SDC-OO55-O34-CL-2OO5 ,
-------
Pennit Compliance System (PCS) QNCR Training
Because resolution occurred as a result of closure of an EA, the system has to wait for the
next RNC program to be run before the resolution code will change to a 2. This is because
the system is comparing different families of data: the EA and the Cs.
This resolution will appear on the QNCR like this:
MATERIALS CONTAINMENT PLAN 02 RPT 06125/91 RE 04/13/92 3D REPORT OVERDUE
• I
S I
• It Is now The date
Resolved the LA wee
• (RE) closed.
NOTE: When a compliance schedule is resolved outside of the RNC time period, SRCC is
set to (W)aiting RNC Resolution. Because of this, the compliance schedule will
still be displayed on the QNCR as non-compliant until RNC is run for the month
in which the violation is resolved.
At that time, the resolution code will be changed to the appropriate resolution code.
Consider the following compliance schedule violation:
CH DSCO I DISC DTAC QI 5 IO CC SNDC SRDC
02 0002 90508 06/25/90 C40 06/25190 N 07/25/90 3 03/21/91
The EA is closed on 04/13/92. The EA closure date is entered, but when the RNC program
is run at the end of April, the RNC time period will be loolcing at September through
February. In this case, the resolution code will change to (W) and the date will be when the
EA was closed:
SDC-0055 -034 -CL-2005A 12/27/93 47
-------
QNCR Training Permit Compliance System (PCS
CH DS DTSC QTh QI YJ2 I SNDC SRCC
02 0002 91508 06/25/90 C40 06/25/90 N 07/25/90 J 06/13/92
I p
I I
Resotution Date EA
outside of was
RNC period. closed.
On the QNCR, this violation will still appear as resolved pending but the Status date will be
the SRDC date which is the date the EA was closed.
48 12/27/93 SDC-OO55-O34-CL-2OO5
-------
Permit Compliance System (PCS) QNCR Training
3.3.4 Manual Resolution of Compliance Schedules
Manually-detected RNC must be manually set to Resolve Pending (RP) and Resolve (RE).
System-detected RNC can also be manually resolved by using appropriate resolution codes
(SRCC).
Also, if the QNCR has old CS violations that need to be resolved, they can be removed from
the QNCR without being deleted. The key data elements for the specific compliance
schedules to be deleted must be known. The manual RNC resolution codes can be found in
Table #390 of the PCS Codes and Descriptions Manual.
CODE DESCRIPTION
6 RE-Manual resolution by EA with closure
7 RP-Manual RP-in compliance with administrative limit
8 RP-Manual due to formal EA
9 RE-Manual by back into compliance
A resolution date (SRDC) must also be entered.
SDC-0055 -034-CL-2005A 12/27/93 49
-------
QNCR Training Permit Compliance System (PCS)
4.0 Effluent Violations
4.1 Violation Detection for Measurements
Measurements are compared against limits in every update when measurements are entered
or limits are changed. Violations are set at this time.
The violation code (MVJO) is stored on the measurement violation (MV) record.
The MVIO field may contain any of the following codes:
DlO = DMR Overdue (EPA)
D20 = DMR Overdue (State)
D30 = DMR Overdue (EPA/State)
EOO = No violation
EOl = Monitored quantity field not entered
El I = Monitored concentration field not entered
E21 = Monitored quantity and concentration field not entered
E3 1 = Limited quantity field not entered
E41 = Limited concentration field not entered
E5 1 = Limited quantity and concentration field not entered
E90 = Numeric violation
For all Mi/JO codes of E90, the percents of the measurements that exceed the limit are also
stored on the MV record. If more than one violation is present for a specific measurement,
the highest percentage within the measurement violation is stored as the worst case
percentage.
There is no manual violation detection for measurements.
B ) Peranieter Code (PRAM) 00310
LOAV LOMX LCMII LCAV LCMX
20 25 45 50
MQAV MOMX MCMII MCAV MCMX
2t 24 45 75
VOAV VOMX VCMII VCAV VCMX WCS
5Z 0% 50% 50%
12/27/93 SDC -0055 -034 -CL -20052
-------
Permit Compliance System (PCS) QNCR Training
4.2 RNC Detection for Measurement Violations
4.2.1 Automatic Detection
Reportable Non-Compliance (RNC) for measurement is run the last weekend of every
month. For the months when the QNCR is due, the RNC program is run every weekend of
the. month, prior to when the QNCR is due. For example, if the QNCR for July through
September is due on November 30th, the RNC program will be run every weekend in the
month of November.
Measurements are evaluated on a 6-month moving time window. The four RNC data
elements that the RNC program assigns to measurements can be found on the MV record:
SNCE - detection code
SNDE - detection date
SRCE - resolution code
SRDE - resolution date
The RNC fields can be found on the EVIO screen.
MEASUREMENTS
SCREEN ID: EVIO
PERMIT # _________ TRANS CODE — DISCHARGE - REPORT DESIGNATOR -
LiMIT TYPE PARAMETER
MONITORING LOCATION SEASON MODIFICATION NUMSER PiPE QUALIFIER
- - QUANTITY LIMITS - - -
AVERAGE MAXIMI.$ UNIT NAME
- . - - CONCENTRATION UNITS - - - -
MINIMUM AVERAGE MAXIMUM UNIT NAME
MEASUREMENTS
QUANTITY CONCENTRATION
MONITORING PERiOD AVERAGE MAXIWJ NININIi AVERAGE MAXIMIM
END DATE ______ ________ ________ ________ ________ ________
DMR RECEIVED DATE _____ RIIC DETECTIOM (S CE) E — (SMOE) DATE _____
INC RE UJTION:(SRCE) E — (S E) DATE _____
REPORTED I OF EXCURSIONS REPORTED FREQUENCY OF ANALYSIS _____
REPORTED SAMPLE TYPE REPORTED.QUAMTITY UNIT CODE
• REPORTEDCONCENTRATION UNIT CODE
MO DISCHARGE REASON CODE — CHANGED NEASURENENTIVIOLAT ION DATE ______
ACCEPT? YIC/KIN/M: Y
SDC-0055-034-CL-2005A 12 /27/93 51
-------
QNCR Training Pennit Compliance System (PCSJ
The RNC Criteria for Measurement Violations
There are 3 types of parameters in PCS:
• Conventional pollutants Technical Review Criteria (TRC) Limitation Group I.
• Toxic pollutants Technical Review Criteria (TRC) Limitation Group II.
• Other Temperature, Fecal Coliform, Ph, Color, DO, Pathogenic
Organisms.
RNC considers both Conventional and Toxic pollutants for the QNCR. The “Other”
category of parameters are never considered for automatic detection of RNC.
Also, only 30-day, daily, and monthly averages are considered by RNC. Because of this,
the statistical base code is important for RNC to correctly evaluate measurements. If a
facility is not appearing on the QNCR, for E90 violations when it should be, the wrong
statistical base code may have been used.
PCS considers violations together for RNC if they are:
• Samepipe(OO1A=OO1B)
• Same parameter
• Same monitoring location
52 12/27/93 SDC-0055-034 -CL-2005A
-------
Permit Compliance System (PCS) QNCR Training
4.2.1.1 Automatic TRC Violations
A parameter does not have a Technical Review Criteria (TRC) violation unless the
measurements for that parameter have exceeded the limit t least twice within a consecutive
six-month period according to the TRC exceedance factor.
The Technical Review Criteria (TRC) factors for measurements are:
• 1.4 for conventional “utants
(measurement excee . .nit by at least 40% or more)
• 1.2 for toxic pollutants
(measurement exceeds limit by at least 20% or more)
The detection code (SNCE) is set to TRC limitations exceeded (T) for both instances when
the second (T) is encountered; the detection date (SNDE) is set to the end of the month of
the second instance; and the resolution code (SRCE) is set to 1 - unresolved. Any violations
associated with TRC violations (other violations of the same parameter that do not meet the
TRC) are in RNC, and the detection code is Effluent-Other. Violation With TRC (V).
Examples :
Parameter is a toxic
Month 01/91 02/91 03/91 04/91 05/91 06/91
MVIO E21 E90 Eli E90 E0O E01
%vio 0 21 0 42 0
SKCE T T
SNDE 043091 043091
SRCE 1 1
Parameter is conventional
Month 10/91 11/91 ¶2/91 01/92 02/92 03/92
MVIO E90 E41 E90 E90 EDO E00
%vio 51 0 40 10 0 0
SKCE T I V
SNDE 123191 123191 013192
SRCE 1 1 ¶
SDC-0055-034-CL-2005A 12127/93 53
-------
QNCR Training
Permit Compliance System (PCS)
Problem :
What will the RNC data elements be for the six-month RNC window from January - June?
What about February to July?
54
12/27/93
SDC -0055-034-CL-2005A
-------
Permit Compliance System (PCS)
QNCR Training
4.2.1.2 Chronic RNC Violations
Four numeric violations of the same parameter in a six-month period (of a 30 day, daily or
monthly average) that do not meet the TRC 1 ctor are considered Chronic Violations.
The detection code (SNCE) is set to Chronic Violation (C) for the four instances when the
fourth violation is encountered. The detection date (SNDE) becomes the end of the month
when the fourth occurred. The resolution code (SRCE) is set to unresolved (1).
If one of the violations meets TRC criteria, it will have a (1) in the detection (SNCE) field
and the other 3 violations will have a (C) in the (SNCE) field.
• What happens if two of the violations meet TRC criteria?
Example:
Problem :
W WI
v u 15 4 0 10 12 0
SNCE C C C C
SNDE 022992 022992 022992 022992
SR E 1 1 1 1
S What are the SNCE, SNIDE, and SRCE codes for the problem below?
Parameter is a conventfonat
Month 01/91 02/91 03/91 04/91 05/91 06/91
EVIO tOO E90 E90 E90 E90 EO0
Xvio 0 2 30 12 6 0
SNUE?
SRCE?
What happens if this same situation occurs for a toxic?
12127193
-------
QNCR Training Permit Compliance System (PCSI
4.2.1.3 Coding “Other” Parameters
“Other” parameters must be manually entered on the QNCR. Here is an example:
1D0022055 has a measurement record for Temperature (00011) that is a violation (E90),
but does not meet automatic RNC criteria since it is an “Other” parameter.
In order to get this parameter on the QNCR, the appropriate RNC codes must be entered
manually.
06/01/93 PCSADE PCDEKEYE
EFFLUENT MEASUREMENTS SCREEN ID: EVIO
KEY SCREEN
PERMiT # (NPID) Ib0O22 5 TRANS CODE n
MONITORING PERIOD END DATE (MVDT) 043092
DO YOU WISH TO USE THE CYCLE OPTION? Y/N) N
DO YOU WISH .10 CYCLE THROUGH ‘PREVIOUS’ LIMITS? CT/N) N
DISCHARGE NLJ BER (VDSC) 001
REPORT DESIGNATOR ( VRD) A
PARAI4ETER CODE (VPRM) 00011
MONITORING LOCATION (VMLO)1
PIPE NODI? (WOOl) (YIN) N (NOT ALLOWED WITH CYCLE OPTION)
RANGE CHECXING? (YIN) N
RANGE TABLE ID: ______
USE NATIONAL DEFAULT TABLE: (YiN) N
ACCEPT? Y/N/N: Y VERSION 2.4 10/01/92
56 . . 12/27/93 SDC-0055-034-CL-2005A
-------
Permit Compliance System ( PCS ) QNCR Training
Next, enter the RNC manual detection codes.
MEASURENENIS
SCREEN ID : EVIO
PERMIT I ID0 5 TRANS CODE n DISCHARGE - REPORT DESIGNATOR -
LIMIT TYPE PARAMETER 00011
MONITORING LOCATION SEASON MODIFICATION NLI(BER PIPE QUALIFIER
- - - - QUANTITY LIMITS - - - —
AVERAGE MAX INLM UNIT NAME
- - - - CONCENTRATION LIMITS - - -
MINDIJM AVERAGE NAXI* UNIT MANE
MEASUREMENTS
-----QUANTITY CONCENTRATION
MONITORING PERIOD AVERAGE MAXIMUM MINIMUM AVERAGE MAXIMUM
END DATE _____ _______ _______ _______ _______ _______
DMR RECEIVED DATE ______ RNC DETECTION : (SlICE) CODE F CS$I)E) DATE 043092
RIIC RESOLUTION: CSRCE) CODE A (SRDE) DATE ______
REPORTED I OF’ EXOJRSIONS — -REPORTED FREQUENCY OF ANALYSIS _____
REPORTED SAMPLE TYPE — REPORTED QUANTITY UNIT CODE —
REPORTED CONCENTRATION UNIT CODE —.
1 10 DISCHARGE REASON CODE — CHANGED MEASUREMENT/VIOLATION DATE ______
ACCEPT? Y/C! flh!M: Y
SDC-0055-034 -CL-2005A 12/27/93 57
-------
QNCR Training . Permit Compliance System (PCS)
4.2.1.4 Violations of Adminictrative Limits
Any violation of a .30 day, daily or monthly average will result in the detection code (SNCE)
being set to Administrative Order (A) for the violation of administrative limits; the detection
date (SNDE) is set to the end of the month that the violation occurred (i.e., MVDT of the.
measurement), and the resolution code in SRCE is set to unresolved (1).
Example :
NP!O FNNS
MVDT VDSG VPRM V7i10 NOAV NQNX MCIIPI MCAV MCNX MVIO
SR E
TX0034428 MRRIS COUNTY WC D #0084
02/29/92 COlA 00530 1 469.93 44.6 77.0 E90
A 02/29/92 1
58 12/27193 SDC-0055-034-CL-2005A
-------
Pennit Compliance System (PCS) QNCR Training
4.2.2 RNC for DMR Non-Receipt
4.2.2.1 Violation Detection for Non-Receipt
DMR Non-Receipt is detected in the DMR Non-Receipt Tracking program which runs once a
month. The program is run at least 60 days after the end of the monitoring period.
Non-receipts violations are flagged by creating a measurement violation record and loading a
violation code (MVIO) and date on the measurement record as follows:
• D1O-OverduetoEPA
• D20 - Overdue to State
O D30 - Overdue to State and EPA
SDC-0055-034-CL-2005A 12/27/93 59
-------
QNCR Training Permit Compliance System (PCS)
4.2.2.2 RNC Detection for Non-Receipt Violations
RNC detection for DMR non-receipt is performed automatically by the DMR Non-Receipt
Tracking program. No manual detection is allowed. RNC is detected and set at the same
time the violations are set. The detection code (SNCE) becomes N; the detection date
(SNDE) is 30 days after submission date, and the resolution code (SRCE) becomes
unresolved (1).
60 12/27193 SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) QNCR Training
4.2.2.3 Incomplete/Deficient DMRs
Any time the 30-day, daily or monthly average is missing for one part (quantity was
reported, but not concentration) of a parameter, the violation is considered
Incomplete/Deficient.
• MVIO = EO1, Eli, £21, E31, £41 or E51
• SNCE = N Non-receipt of DMR
On the QNCR, the detection code (SNCE) will be Non-receipt of DMRICS Report (N) and
the MVIO will be £01, Eli, E21, E31, E41 or £51. The detection date (SNDE) will be
equal to the Monitoring Period End Date (MVDT) for the month of the measurement that
was entered. The resolution code (SRCE) will be set to Unresolved (1). The violation will
appear as Incomplete/Deficient DMR rather than DMR non-receipt.
NOTE: If the entire parameter is not reported, RNC for DMR Non-Receipt (DlO, D20 or
D30) is flagged.
SDC-0055 -034-CL-2005A 12/27/93 61
-------
QNCR TNining Permit Compliance System (PCS
4.2.2.4 Manual Detection of Effluent Violations
Other violations determined to beRNC may be set using the manual detection codes (B, D,
E, F, G, I, 3, Q, W, X, Y, Z) found in Table #195, RNC DETECTION CODES (see the
Appendices for Tables).
Problem :
MT0023854 has a measurement record that is a violation (MVIO=E90) but that does not
meet the automatic RNC criteria.
Enter the appropriate information to set these violations to manual RNC because they are
“Violations of Concern”. RNC was detected on 033192.
The violation is:
DSDG=OO1A
LTYP=F
PRAM=000l1
MLOC=1
SEAN =0
MODN=0
MVDT=033192
62 12/27/93 SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) QNCR Tr2ining
EVIO Screen #1
06/01/93 PCS-ADE P C OEKEYE
10:08:54 EFFLUENT NEASL EMENTS SCREEN ID: EVIO
KEY SCREEN
PERMIT #. (NP ID) ________ TRANS CODE
MONITORING PERIOD END DATE: ______
DO YOU IIISH TO USE THE CYCLE OPTiON? (YIN) —
DO YOU WISH TO CYCLE THROUGH ‘PREVIOUS’ LIMITS? (Y/N) N
DISCHARGE NUMBER (VOSC)
REPORT DESIGNATOR (VDRD) —
PARAMETER CODE (VPRM) _____
MONITORING LOCATION (V) LO)_
PIPE WOO!? (NOD!) (Y/N) y (NOT ALL 4ED WITH CYCLE OPTiON)
RANGE CHECKING? (Y/N)
RANGE TABLE ID: ______
USE NATIONAL DEFAULT TABLE?
ACCEPT? YIN/N: Y VERSION 2.4 10/01192
EVIO Screen #2
MEASUREMENTS
TYPE OF LIMIT SCREEN 10 - EVIO
PERMIT # _________ TRANS CODE DISCHARGE - REPORT DESIGNATOR -
LIMIT TYPE PARAMETER
MONITORING LOCATION SEASON MODIFICATION NUMBER PIPE QUALIFIER
- - - QUANTITY LIMITS - - - -
•:AVERAGE MAXIMUM UN1TNAME.
:1 - - CONCENTRATION LIMITS : .- -
AVERAGE NAXIIIJM UNIT NAME .
MEASUREMENTS
QUANTITY CONCENTRATiON
MONITORING PERIOD AVERAGE MAXIMUM MINIMUM AVERAGE MAXIMUM
END DATE ______ ________ ________ ________ ________ ________
DMR RECEIVED DATE ______ RNC DETECTION CODE — DATE ______
RNC RESOLUTION: CODE DATE _____
1 .. : REPORTED #‘OF EX RS!OMS — REPORTED FREQUENCY OF ANALYSIS ____
REPORTED SAMPLE TYPE — REPORTED QUANTITY UNIT CODE —
REPORTED CONCENTRATION UNIT CODE —
NO DISCHARGE REASON CODE — CHANGED MEASUREMENT/VIOLATION DATE ______
ACCEPT? T IC/k/N/N Y
SDC-0055-034-CL-2005A
12127/93
63
-------
QNCR Training Permit Compliance System (PCS
4.3 RNC Resolved Pending and Resolution for Effluent Violations
4.3.1 Automatic Resolved Pending of Effluent & Non-Receipt Violations
Violations that are covered by a formal enforcement action are set to resolved pending (RP)
when:
• A formal enforcement action and an extended compliance schedule are entered.
• They are linked via a docket number.
• The enforcement action addresses the effluent and/or non-receipt violations.
The resolution code (SRCE) will become RP due to formal EA (3), the resolution date (SRDE
will be the date of the enforcement action when the ENDT falls within the RNC timefranie.
An example of this appears below :
MVOT VDSG VPRN VY4LO cVf0 SlICE SlIDE SRCE SRDE
013192 OO1A 00530 1 E90 T 043092 1
022992 OOIA 00530 1 E90 T 043092 1
An enforcement action was entered;
ENAC =21
EATP =E
ENDT = 061592
EVTP =El
ERFN = 061692WSS
64 12/27/93 SDC-0055-034-CL-2005A
-------
Peniut Compliance System (PCS) QNCR Training
An extended compliance schedule was entered:
CSCH = DZ
DSCD = 0001
EVNT = 05699
DTSC = 051593
CSFN = 061692WSS
RM y Q sN SR SRDE
013192 OO IA 00530 1 £90 T -043092 3 061592
022992 001* 00530 1 E90 1 043092 3 061592
Below is an example of how these violations would appear on the QNCR:
SOLIDS, TOTAL SUSPENDED 001* TRC 01/31/92 RP 06/15/92 2C-PERMIT EFFLUENT VIOLATION
SOLIDS. TOTAL SUSPENDED 001* TRC 02/29/92 RP 06/15/92 2C-PERNIT EFFLUENT VIOLATION
SDC-0055-034-CL-2005A 12/27/93 65
-------
QNCR Trainrng Permit Compliance System (PCS)
4.3.2 Manual Resolved-Pending of System Detected RNC
System detected RNCs may be manually set to RP with resolution codes (SRCE) of 7 or 8.
A resolution date (SRDE) must be provided. Manually detected RNC (except those detected
with codes X, Y, & Z) must be manually set to RP with codes 7 & 8 (in SRCE); the
resolution date (SRDE) must also be entered. SRCE codes of X, Y and Z automatically
Resolved-Pend.
NOTE: This would look the same on the QNCR as the example used for Automatic
Resolved-Pending on the preceding pages.
66 12/27/93 SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) QNCR Training
4.3.3 Resolved Pending of Manually Detected Effluent Violations
RNC measurement violations can be manually detected with codes:
X Eff-Manual viol w/other TRC,
Y TRC-Manual TRC and
Z CHR-Manual Chronic
These codes are handled in the same manner as system detected violations; that is, they are
automatically set to resolved (RE) and resolved-pending (RP). These codes may be used in
the case of late data entry where the measurement violation meets TRC or Chronic criteria
and was not automatically detected by the system.
NOTE: This would look the same on the QNCR as the example used for Automatic
Resolved-Pending on the preceding pages.
SDC-0055-034-CL-2005A 12/27/93 67
-------
QNCR Training Permit Compliance System (PCS)
4.3.4 Resolved Pending of Adminictrative Limits
RNC of administrative limits are set to RP if they have three months without a violation.
The resolution code (SRCE) is set to RP In Compliance Last Qtr (4) and the resolution date
(SRDE) is set to the monitoring period end date (MVDT) of the third month.
SOLiDS, TOTAL JSPE)LOED OO1A ENF 03/31192 PP 07/31/92 PP-DUE TO FORMAL ‘U
SOLIDS, TOTAL SUSPENDED OO1A ENF 04/30/92 PP 07/31/fl PP-DUE TO FORMAL EA
12fl7/93 SDC-OO55-O34-CL-2OO5
-------
Permit Compliance System (PCS) QNCR Training
4.3.5 Automatic Resolution of Effluent Violations
In order to resolve cases of SNC, a facility must have actual DMR data that have not
exceeded a limit for each month in a three-month period. The resolution code (SRCE)
becomes RE Ba k into Compliance (2), and a resolution date (SRDE) is also entered (the end
date of the six-month window). The following cases are nQi considered to be DMR
measurements and fl j resolve TRC violations:
Parameter NODI records.
• DMR non-receipt violations.
• DMR incomplete/deficient violations when the monthly average measurement is missing.
Example 1 :
DMRs for pipe 001, parameter BOD, are to be reported monthly. Months one, two, and
three have SNC violations (two TRCs and one non-TRC). Months four and six have no
effluent violations and month five has not been reported.
NOUTH 1/92 2/92 3/92 4/92 5/92 6/92
Zvio 35 25 19 0 0 0
SNCE T T V H
S E 022892 022892 033192 053192
1• 1
For the (three month) QNCR period there are no effluent measurement violations. However,
the DMR non-receipt violation does not count as a DMR measurement. The two DMR
measurements in the QNCR period do not satisfy criteria for three months clean. As a
result, the effluent SNC violations stay unresolved.
Example 2
DMRs for pipe 001, parameter BOD, are to be reported monthly. For report designator A,
months one, two, and three have no data reported (parameter NODI). Months four, five and
six have no effluent violations. For report designator B months one, two, and three have
SNC effluent violations (two TRCs arid one non-TRC). Months four, five, and six have not
been reported.
SDC-oo5g -034-CL-20 05A 12127/93 69
-------
QNCR Training Permit Compliance System (PCS)
ISI1 TH 1 / 92 2/92 3/92 4/92 5/92 6/92
NVIO E00 EO0 E0O
Xvio NODI NCD II I 0 0 0
S CE
sa
Pipe OO 1A
NIIITH 1/92 2/92 3/92 4/92 5/92 6/92
NVIO E90 E90 E90 030 D30 D30
%vio 35 25 19
i• T V
SamE 022892 022892 033192
sa 2 2 2
SRDE 063092 063092 063092
Pipe OOIB
For the QNCR period, there are no effluent measurement violations. The effluentSNC
violations will be RE back into Compliance even though report designator B has DMR
Non-Receipt violations in the QNCR period. The DMR measurements for report designator
A satisfy the criteria for three months clean.
When two or more measurement records exist for the same pipe, parameter, and monitoring
period for a month (due to multiple report designator values), only one DMR measurement i
required to consider a parameter clean for that month. Since program logic cannot determin
which measurement record was required to be entered, all measurement records will be
checked. If at least one DMR measurement exists, a parameter is considered clean for that
month.
70 12/27/93 SDC-0055-034-CL-20054
-------
Permit Compliance System (PCS) QNCR Tr2ining
Examole 3
DMRs for pipe 001, parameter BOD, are to be reported bimonthly. Months one and three
are effluent SNC and month five has no effluent violations. Months two, four, and six have
no measurements reported because none ate required.
MONTh 1/92 2/92 3/92 4/92 5/92 6/92
NVLO £90 E90 EDO
Xvie 35 29
SN I T
SImE 033192 033192
SR E I
SIDE
Since three months of actual data are required to resolve back into compliance, only
violations reported monthly could be resolved in this manner. Other reporting periods (such
as bimonthly or quarterly) would require manual resolution. Also, DMR data that is
reported monthly but submitted at a different time interval (such as quarterly) may be
sUbmitted monthly to resolve effluent SNC violations.
Example 4 :
DMRs for pipe 001, parameter BOD, are to be reported monthly. The resulting seasonal
indicators are ‘YYYNNN for months one through six. Months one, two, and three have
effluent SNC violations (two TRCs one non-TRC). Months four, five, and six have no
measurements reported because none are required as indicated by the seasonal indicators.
.MON IH:1/92
2/92
3/92
.4/92
5/92
6/92
NVIO E90
£90
E90
* o:; 35 ..
.
19
v
29
T
:::SMOE 033192
022892
033192
: .
1
.
1
.
ALLS V
V
V
N
N
N
SDC4)U 5-O34-CL-2UU A 12121193 . 11
-------
QNCR Training Permit Compliance System (PCS)
For the QNCR period, there are no effluent measurement violations. However, the
measurements not required to be reported count as DMR measurements. Thus, the
criteria for three months clean is not satisfied and the effluent SNC violations stay
unresolved.
Since three months of actual data are required to achieve back into compliance, facilities with
seasonal operations may not be able to resolve effluent SNC violations in this manner.
Example 5 :
DMRs for pipe 001, parameter BOD, are to be reported monthly. Months one and three
have SNC violations (two TRCs). Months four, five, and six have incomplete/deficient
violations where the monthly average measurement is missing.
1131flh( 1/92 2/92 3/92 4/92 5/92 6/92
MVIO E90 E00 E90 E41 E5 1 E51
Zv.o 35 29
ssic T T
S )E 033192 033192
SR I I
SiDE
For the QNCR period, there are only incomplete/deficient violations. However, these
violations do not count toward the three months clean criteria because the measurement valu
that contains the monthly average statistical code is absent ; In.this case the effluent
SNC violations stay unresolved. But keep in mind that an incomplete/deficient DMR with
the monthly average value present ffl count toward the three months clean criteria.
72 12/27/93 SDC-0055-034-CL-2OO52
-------
Permit Compliance System (PCS) QNCR Training
4.3.6 Automatic Resolution of Resolved-Pending Violations
RNC that has been set to resolved-pending (RP) by the entry of an enforcement action and a
compliance schedule are set to resolved (RE) when the enforcement action is closed with a
status code (ENST) of closed (CL). The resolution code (SRCE) is set to RE resolved PP
by closed EA (5), and the resolution date (SRDE) becomes the date the enforcement action
was closed.
Automatic Resolution of Non-Receipt Violations
If entire DMRs or individual parameters are not received, the system does not assume
compliance (E00) for that missing data. Resolution occurs when the missing data is entered
into the system, or a no discharge (NOD!) code is entered.
NOTE: When D10, 20 or 30 is the violation code;
• They cannot be blanked-out to get them to drop off of the QNCR.
• They can be deleted.
•wThey should remain on at the least 1 QNCR to show that they are Resolved.
• At the least put a NOD! code in the system for those facilities in non-receipt.
NOTE: When a non-receipt violation is resolved outside of the RNC time period; SRCE is
set to “WAITING RNC RESOLUTION” (W). Because of this, the violation will
still be displayed on the QNCR as non-compliant until RNC is run for the month
in which the violation is resolved. At that time, the resolution code will’ be
changed to the appropriate resolution code.
SDC-0055-034-CL-20 05A 12/27/93 73
-------
QNCR Training Permit Compliance System (PCS
4.3.7 Manual Resolution of Effluent Violations
Manual Resolution can be set to resolved (RE) by using codes B, 6, and 9 in the resolution
code field (SRCE). (See Table #390, RNC Resolution Codes) . A resolution date (SRDE)
must also be entered.
Problem :
What RNC data elements are set for the two six-month RNC windows June through
November 1991, and July through Dec 1991? (Do not consider January and February yet.)
Toxic Parameter:
Month 6/91 7/91 8/91 9/91 10/91 11/91 12/91 1/92 2/92
MVIO £00 EDI E90 E31 E90 E01 £21 030 D30
Zv o 0 0 72 0 47 0 0 0 0
SNCE7
SNDE7
SR CE?
SRDE7
74 12/27/93 SDC-0055-034-CL-2005 1
-------
Permit Compliance System (PCS) QNCR Training
4.3.8 Problems Encountered on the QNCR
Problem:
• The QNCR shows Incomplete/Deficient for temperature. The permit requires a
temperature (parameter code 00011) maximum only. The limits show a value for the
maximum and data was keyed in, as required for that field. An Eli violation was
generated. This means the MCMN and MCAV fields were not entered. The violation is
a false violation.
What is the problem in the above scenario?
Solution :
• Check the PCS STORET Parameter Code Tables.
• Verfy which fields are automatically closed.
• The code table for temperature shows concentration minimum, average, and maximum
fields open.
• There is not an X in those fields.
• PCS must be told to close those fields by coding DELMON (DELete the MONitoring
requirement).
The same is true if a field needs to be opened that is closed on the PCS STOREF Parameter
Code Tables. ADDMON is used to ADD the MONitoring requirement, that is, to open the
limit field that must be reported.
In some cases a facility may have the option to report a parameter or field. Code OPTMON
(OPTional MONitoring requirement) for the limit fields that have optional reporting. A
violation will not be generated when the data is not reported.
For Reported Quantity Unit (RUNT) and Reported Concentration Unit (RCUN), RCUN must
be entered to determine if the facility is in violation or not.
SDC-0055-034-CL-2005A 12/27/93 75
-------
QNCR Training Permit Compliance System (PCS
5.0 RNC for Single Event Violations
5.1 Violation Detection for Single Event Violations
Single Event violations are violations when the event record is entered. Indicate the type of
violations when choosing the violations event code.
5.2 RNC Detection for Single Event Violations
All RNC detection for Single Event violations is set manually.
There are four RNC data elements for RNC on the Single Event record:
• SNCS - detection code
• SNDS - detection date
• SRCS - resolution code
S SRDS resolution date
SINGLE EVENT VIOLATIONS
PERMIT # _________ TRANS CODE —
VIOLATW$ CODE ____ VIOLATION DATE _____
RNC.DETECTION
RIIC DETECTION DATE _____
RNC RESOLUTION E — I:..
RIIC RESOLUTION DATE _____
REGIONAL FIELD 1 REGIONAL FIELD 2 ______
: ACcEpT? Y/N/N: V VERSION 2.1 10/06/89
76 12/27/93 SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) QNCR Tr2ining
To set RNC for Single Event violations enter:
• The correct detection code (SNCS). Use the following detection codes: (from Table #195,
RNC Detection Codes: B,D,E,F,IJ.
• A detection date (SNDS).
• A resolution code (SRCS), probably manual unresolved RNC (A).
SDC-0055-034-CL-2005A 12/27/93 77
-------
QNCR Training Permit Compliance System (PCS 1
5.3 RNC Resolved Pending for Single Event Violations
Resolved pending occurs when a formal enforcement action has been entered that addresses
the single event violation and an extended compliance schedule has been entered with an
identical docket number to that of the enforcement action.
5.4 RNC Resolution for Single Event Violations
Resolution of single event violations must be set manually with a manual resolution code in
SRCS and a resolution date in SRDS.
Single event violations that are in resolved-pending (RP) status are automatically resolved
when the enforcement action is formally closed with a status code of CL in the ENST field.
78 12/27/93 SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) QNCR Training
6.0 Facility Level RNC
Four data elements on the Permit Facility record are used to track the quarterly QNCR status
of a facility as a whole:
CYQS - Automatic QNCR Status, Current year
PYQS - Automatic QNCR Status, Previous year
CYMS - Manual QNCR Status, Current year
PYMS - Manual QNCR Status, Previous year
FACILITY/PART 2
SCREEN ID: FAC2
PERMIT # _________ TRANS C )E —
FACILITY
NAME -
ARCH! VALINDICATOR — RIVER BASIN # ______
RECEIVING WATERS ___________________________________
- - - EVIDENT1ART HEARING .- - - -
- HEARING INDICATOR — FILE % ___________ ISSUE C ES — — —
DOCXET # ___________
- - - USER DATA ELEMENTS - - - -
RDF1 RDPZ — RDF3 — RDF4 — RDFS — RDF6 — RDF7 ______ RDF8 ______
RDF9 — RDF1O ________________________________________________
- - - NMP ELEMENTS - - - -
NPSC-WMP STAT — NPFF-NMP FIT — NPSO-KMP QTR
PREVIOIJSYEARMAMMLQNcR STATUS 1_2_3_4_
OJRREWT TEAk MAHUAL QNCR STATUS I — 2 — 3 - 6
ACCEPT? Y/N/H: Y
Each of these data elements is four characters, representing the facility’s status for each
quarter of a fiscal year.
CYQS is set by the PF Update portion of the RNC program based on the status of violations
in the compliance schedule, measurement, and single event violation areas. The system will
assign the status code based on the worst case violations in these areas. In other words, if
the facility has one compliance schedule that is resolved-pending and two unresolved TRC
effluent violations, then the status code will be (E) based on the unresolved violations. Refer
to Table #440.
SDC-0055-034-CL-2005A 12/27/93 79
-------
QNCR Tr iining Permit Compliance System (PCS
CYMS may be entered manually, and will override CYQS when facilities are selected to
appear on the QNCR.
The codes that can be assigned to CYQS and CYMS are as follows:
Tab’e #440
440 QNCR STATUS CODES
lTABLE• TASLE-DESC
C PL3A NT
0 NCSIIC DNR NOM-RECPT
E NC-SNC EFFLUENT ViOL
- N NC -RNC VIOLTKS DIlLY
P RESO .VED PENDHIG
R RESOLVED
S NC-SNC CDIIP SCHO yb
T NCSI IC COMP SCHO RPT
NeTE: There is one facility status code per quarter. Therefore, if more than one non-
compliant status code applies for an individual quarter, the PF update program
will assign the code in the following order of importance:
S SNC Compliance Schedule Violations
E SNC Effluent Violations
T SNC Compliance Schedule Report Violations
D SNC DMR Non-Receipt - Pipe Level Violations
N NC RNC Violations Only V
P Resolved Pending
R Resolved
C Compliant
12/27/93 SDC-0055-034-CL-200cA
-------
Permit Compliance System (PCS) QNCR Training
Exainnie :
A facility has the following violations:
Effluent Violations
PRAM SNCE SNDE SRCE
00310 (BOD) TRC 103191 Unresolved
00310 (BOD) TRC 113091 Unresolved
00530 (TSS) Chronic 103191 Resolved
Compliance Schedule Violations
EVNT SNCC SNDC SRCC
Begin Const. S 061491 ResoIved Pending
End Const. S 082591 Unresolved
RNC is running for the first quarter FY92 (10-12/91). The PF flag for this quarter will be
set to (E), for SNC effluent violations, because there are non-compliant SNC effluent
violations during the quarter.
SDC -0055-034-CL-2005A 12/27/93
-------
QNCR Training Permit Compliance System (PCS
Problem :
A facility has the following violations:
Emuent Violations
MVDT PRAM SNCE SNDE SRCE SRDE
073191 00310 (BOD) TRC 093091 RE 123191
093091 00310 (BOD) TRC 093091 RE 123191
063091 00530 (TSS) Chronic 113091 RP’ 011792
083191 00530 (TSS) Chronic 113091 RP 011792
093091 00530 (TSS) Chronic 113091 RP 011792
113091 00530 (TSS) Chronic 113091 RP 011792
Compliance Schedule Violations
EVNT SNCC SNDC SRCC SRDC
[ U Report R 072691 RP 011792
Complete TRE S 082591 RP 011792
RNC is running for first quarter FY92 (10-12/91) (RNC is running on February 28, 1992,
for the six-month period of July - December).
• What would the PF flag for this quarter be?
• What would change, if in December 1991, another. TRC violation occurred for the same
pipe and parameter as the previous TRC violations in July and September?
12/27/93 SDC-0055-034-CL-2005
-------
Permit Compliance System (PCS) QNCR Training
70 QNCRs and Their Uses
There are 4 types of QNCRs. They are:
• Regular QNCR The regular QNCR is the one used quarterly to identify those major
facilities not in compliance with their NPDES permit. This report
displays majors sorted by: municipals; then industrials; then
federals. Facilities are displayed by: Non-Compliant & Resolved;
then Resolved-Pending. For Ohio the QNCR retrieval looks like
this:
01 OH QNCR
2OQNVTYP=ECS
20 WITH SirE EQ OH
• Selective QNCR The selective or selectable QNCR can be used to obtain non-
compliance information on any facility or group of facilities. This
report is virtually the same as the regular QNCR but has the ability
to selectively get QNCRs. A retrieval to print a QNCR for
MUNICIPAL minors in Ohio could look like this:
01 OH_QNCR FOR MINORS
10 S rri EQ OH
10 MAD! NE M
10 FTYP EQ M
20 QR VTYP=ECS
• Manager’s QNCR Reports on only those facilities which have SNC violations. A
manager’s QNCR for Ohio majors looks like this:
01 OH MANAGERS QNCR
10 SIrE EQ OH.
10 MAD! EQ M
20 QM VTYP=EC
SDC-0055-034-CL-2005A 12/27193
-------
QNCR Trilning Permit Compliance System (PCS’
• Coordinator’s QNCR Includes the same as the others, but also includes additional data
elements and the codes used in data entry to facilitate QNCR
problem resolution.
01 OH COORDINATORS QNCR
10 SUE EQ OH
20 QC VIOL=ALL BREAK =YES COMP=YES
20 WITH ENDT GE 050192
20 WITH ENDT LE 093092
The following three pages show examples of three of the four QNCR types since the regular
and Selected QNCRs look the same, just different facilities can be included.
84 12/27/93 SDC-0055-034-CL-2005A
-------
Penn it Compliance System (PCS)
QNCR Training
7.1 Regular or Selective QNCR:
1 ION
:s NUMBER GRANT LIMIT
MICE OF NONCOMPLIANCE
•*ee*aflS*t •tt*et*te -
j5 COUNTY WCID #0054
INELVIEW
34428 “‘FINAL”
SC hEDULE 40-EQ
CARBONACEOIJS
SCHEDULE 40-EQ
CARBONACEOUS
SCHEDULE A0-E0
OS, TOTAL
SCHEDULE A0-EO
CARBONACEOUS
SCHEDULE A0-ED
OS, TOTAL
SCHEDULE A0-E0
CARB ACEOUS
SCHEDULE *0-EQ
)S, TOTAL
SCHEDULE AD-ED
CARBONACEOUS
DOCKET NUMBER: 91-1245
ADMINISTRATIVE ORDER
DOCKET NUMBER: 93-1294
DOCKET NUMBER: 91-1245
ADMINISTRATIVE ORDER
DOCKET NUMBER: 93-1294
DOCKET NUMBER: 91-1245
* * ‘*** •t * SUMMARY SECTION ’S S S et
07/31/92 - 0 1/3 1/93
DOCKET NUMBER: 91-1245
O9/3D 19D - 03/31/93
DOCKET NUMBER: 91-1245
02 /28 /93 - 03/31/93
DOCKET NUMBER: 91-1245
07/31/92 - 01/31/93
DOCKET NUMBER: 91-1245
02/28/91 - 06/30/92
DOCKET NUMBER: 91-1245
SCH 07/06/92
DOCKET NUMBER: 91-1265
SCN 06/06/92
DOCKET NUMBER: 91-1245
RPT 04/15/92
12/01/93 REGION 06
CIPALS
SELECTIVE QUARTERLY NON-COMPLIANCE REPORT “ ONCR “
SELECTIVE ONCR
TEXAS
FROM: 07/01/93 T0:09/3D/93
, •SSt*ea**S*t.**..S*S*..**tt*t*s *.n..*.....o. *
VIOLATION
RNC DATE
I
NON-COMPLIANT
PAGE 1
ENFORCEMENT STATUS
ENFORCEMENT ACTION DATE STATUS DATE OI IENTS
**t*S***ttttt**t***S**tt***t*SS***St*ttfltttt*SttflSttttte• 5 50fl 5 5 5 5fl 5 5 5 5 5 n 5 5 5 5e 5 5
OS DAY, 20 OD 1A ENF 07/31/93
05 DAY. 20 OD 1A ENF 07/31/93
SUSPENDED CO lA ENF 06/30/93
0014 ENF
COlA ENF
0014 ENF
0014 ENF
001* ENT
06/30/93
05/31/93
05/31/93
04/30/93
06/30/93
DOCKET NUMBER:
DOCKET NUMBER:
DOCKET NUMBER:
DOCKET NUMBER:
DOCKET NUMBER:
91- 1265
91- 1245
91-1245
91-1245
91- 1245
OS DAY, 20
SUSPENDED
OS DAY, 20
SUSPENDED
05 DAY, 20
SUSPENDED
SUSPENDED
OS DAT, 20
05 DAY, 20
05 DAT, 20
S I )S, TOTAL
)S, TOTAL
9 1 CARBONACEOUS
CARBONACEOUS
Ii CARB oNACEOUS ’
(EPA) 08/31/93 RP 08/31/93 2A ENF ORDER EFF ft/OR NARR VIO
(EPA) 08/31/93 RP 08/31/93 a ENF ORDER EFF ft/OR NARR VIO
RD D9/3D/93 a ENF ORDER EFF ft/OR NARR VIO
NC 06/30/93 2A ENF ORDER EFF ft/DR NA RR VIO
RD 09/30/93 2A ENF ORDER EFF ft/OR NARR y b
NC 05131/93 a ENF ORDER EFF ft/OR NARR VIO
RD 09/30/93 a ENF ORDER EFF ft/DR NARR VIO
NC 04/30/93 2A ENF ORDER EFF ft/DR NARR VIO
RE RESOLVED
RD RESOLVED PENDING
•NC CONTINUING NONCOMDLIANCE
RE RESOLVED
RD RESOLVED PENDING
RD 04/13/93 2B COMDL SCHEDULE VIOlATION
RD 04/13/93 2B COMPI. SCHEDULE V iOLATION
RD D4/13/93 3D REPORT OVERDUE
0014
001 A
O O IA
001k
DO 1A
MC
MC
MC
F - COMPLIANCE W/EFF LIMITS
:ONSTRUCT iON
31 1PT CONSTRUCTION PROGRESS
SDC-ou55-034-CL-2DU SX
85
-------
QNCR Training Permit Compliance System (PCS
7.2 Manager’s QNCR:
DATE: 10123/92 MANAGER’S 1CR PAGE: 1
TYPE: MUNICIPAL TEXAS QNCR PERIOD: 05/01/92 TO 07/31/92
****** *taa p*. #****.********.**e***.aI-**. ** **g***.kua- ti*****e.*.***.pjt..p* .******e. .
FACILITY: HARRIS COUNTY WCZD 10084 NPDES NO; TX0034628
LOCATION: CHANNELVIEW
EFFLUENT VIOLATIONS
VIOLATION QUARTERS ENFORCEMENT ACTION ENF.ACT.
EFFLUENT PARAMETERS OUTFALL SNC TYPE DATE ON NCR AFTER QNCR PERIOD DATE. CO S4ENTS
SOLIDS, TOTAL SUSPENDED 001 ENF.ACT. 06/92 4
05/92
02/92
BCO, CARBON. 05 DAY, 20 001 ENF.ACT. 06/92 6
05/92
04/92
O3 92
02/92
COMPLIANCE SCHEDULES
VIOLATION ENFORCEMENT ACTION ENF.ACT.
REPORT DATE SOURCE AFTER ONCR PERIOD DATE COI 4ENTS
CMPL. W IFINAL EVENT 8/31/91 ADMIN. ORDER
12/27/93 SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) QNCR Training
7.3 Coordinator’s QNCR:
DATE: 10/23/92 CCORDHIATOR’S QUARTERLY NON-CORPLIANCE REPORT PAGE: 1
MUNICIPAL REPORT PERIOD: 05/01/92 - 07/31/92
COORDINATOR’S 04CR
FACILITY STATUS
PREVIOUS YEAR CURRENT YEAR
PERMIT NAJ/ VACILITY FED’L CPC S/MANUAL) (PCS1MAI(UAL)
FAC. lIAISE NUMBER M1N TYPE GRANT LIMIT COMPLIANCE STATUS 01 02 03 04 01 02 03 04
HARRIS CNTY TX0034428 MLiOR MUNICIPAL NC-SMC CORP SCHD yb R/- El- El- SF- SI- SI- Si- SI-
0 M B VIOLATION(S) S1J 4ARY
DOCKET DETECTION RESOLUTION
DATE KEY DATA PARAMETER NUMBER COLS VIOLATION CODE/DATE/TYPE CODE/DATE/DESCRIPTION
9/30/90 COlA 9 5 00530 100 SOLIDS E90 NIJI.VIO C 01/31/91 CHR 3 02/14/91 RP-FORMALEA
6/30/92 COlA 9 5 00530 101 SOLIDS 91-1245 56 E90 KUM.VIO A 06/30/92 ENF 1 NC-UNRESOLVED RNC
2/28/91 COlA 9 5 80082 101 BOO CARS 91-1245 56 E90 NUM.VIO A 02/28/91 ENF 4 9/30/91 RP-IN COM LSTQT
3/31/91 COlA 9 5 80082 101 BOO CARS 91-1245 56 E90 NUM.VIO A 03/31/91 EIIF 49/30/91 RP -IN COM.LSTGT
4/30/91 OO1A 9 5 80082 101 800 CARS 91-1245 56 E90 NUM.VI0 A 04/30191 EIIF 4 9/30/91 RP-IN CON ISTOT
9/30/91 0010 9 5 74055 100 COLIF.FECAL 030 OVERDUE 1111/24/91 RPT I NC-UNRESOL.RNC
ENFORCEMENT ACTION(S) SUMMARY
DOCKET STATUS FORMAL/ C.S.
DATE NUMBER CODE/PARTY/ACTION STATUS DATE INFORMAL?
2/14/91 91-1245 56 EPA MCP SCHEDULE A0-EO : FORMAL YES
KEY: El ALL EFFLUENT VIOS FOR PERMIT
4/01/91 13 EPA ADM ACTION PENDING INFORMAL NO
KEY: E2 EFFLUENT VIOS FOR MONITORING PERIOD
LINKED TO: 02/28/91
KEY: E2 EFFLUENT VIOS FOR MONITORING PERIOD
LINKED 10: 03/31/91
7/31/91 91-1092 21 EPA ADMINISTRATIVE ORDER FORMAL YES
KEY: C2 SPECIFIC COMPLIANCE VIOLATION
LINKED TO: 03/15/91 MC 90 33099 C40
KEY; C2 SPECIFIC COMPLIANCE VIOLATION
LINKED TO: 04/15/91 MC 90 33199 C40
SDC-0055 -034-CL-2005A 12/27/93
-------
Permit Compliance System (PCS ) QNCR Training
Appendix A
PCS QNCR RELATED TABLES
-------
Permit Compliance System (PCS) QNCR Training
PCS QNCR RELATED TABLES
These tables are presented in the order they are used throughout this training. They are
examples from the PCS Cod€s and Descriptions Manual. They are not complete
representations of the tables.
SDC OO5S-O34-CL-2OO5A 12/27/93 A-1
-------
QNCR Training Permit Compliance System (PCS
Tables
205 FACILITY TYPE INDICATOR j
175 COMPLIANCE SCHEDULE NUMBERS
020 COMPLIANCE SCHEDULE EVENT CODES
240 DATA SOURCE CODES
480 COMPLIANCE VIOLATION CODES (AUTO AND MANUAL)
780 OUTFALL TYPE
310 LIMIT TYPE CODES
080 MONiTORING LOCATION CODES
120 STATISTICAL BASE CODES
150 SAMPLE TYPES
050 FREQUENCY OF ANALYSIS CODES
450 CONTESTED PARAMETER CODES
180 UNITCODES
490 NO DISCHARGE INDICATOR CODES
550 SINGLE EVENT VIOLATION CODES
030 ENFORCEMENT ACTION CODES
04( ENFORCEMENT ACTION STATUS CODES
340 ENFORCEMENT ACTION VIOLATION TYPES
195 RNC DETECTION CODES I
390 RNC RESOLUTION CODES 1
440 QNCR STATUS CODES 1
A-2 12/27/93 SDC-O055-034-CL-20O
-------
Permit Compliance System (PCS) QNCR Tr iining
205 FACILITY TYPE INDICATOR (FTYP)
F
•
FEDERAL
I
INDUSTRIAL
N
MUNICIPAL
0
OTHER
175
COMPLIM CE SCHEDULE NUMBERS. (C SCR)
AA 301 (I) (1)
AB 301 (I) (2)
AC’ 301 (H)
AD 308 LETTER
BI BIOMNTRNG SCH EST BY ENF ACT
CC SCHED ESTBLISHED BY CCP ‘ - EXTENDED CS
CP SCHED REQUIRING DEV OF CCP
DA 309 (A) (5) (A)—INTERIM ‘ — EXTENDED CS
DB 309 (A) (5) (A)-FINAL — EXTENDED CS
PC 309 (A) (5) (A)—MUNICIPALS — EXTENDED CS
309 (A) (5) (B) - EXTENDED CS
DE 309 (A) (6) - EXTENDED CS
DF 309 (A) (3)
DZ ADMIN. ORDERS FOR INDUSTRIALS - EXTENDED CS
FF FED FACILITY COMP AGREEMENT - EXTENDED CS
GA FED. JUDICIAL DECREES - EXTENDED CS
HA STATE JUDICIAL DECREES - EXTENDED CS
MC STATE NON-JUDICIAL DECREES (IND & MUN)- EXTENDED CS
JA STATE ADMIN. DECREES - EXTENDED CS
MC ENF SCH FOR MUN COMP STRATGY - EXTENDED CS
MI 308 REG FOR NUNI COMP STRATEGY
MP REQ ENF SCM FOR NUN COMP STRAT
NI NOV FOR INDUSTRIALS
NM NOV FOR MUNICIPALS
TR PRETREATMENT — EXTENDED CS
01 01
02 02
03 03
SDC-0055-034-CL-2005A 12/27/93 A-3
-------
QNCR Training Permit Compliance System (PCS
020 COMPLIANCE SCHEDULE EVENT CODES (EVNT)
00199 1ST REPORT OF PROGRESS 1 R
00299 2ND REPORT OF PROGRESS 1 R
00399 3RD REPORT OF PROGRESS 1 R
00499 4TH REPORT OF PROGRESS 1 R
00599 5TH REPORT OF PROGRESS 1 R
01799 COMPLETE PLANS & SPECS 1 S
01899 ADVERTISE FOR BIDS 1 S
02599 FINANCING COMPLTE CONTR AWRD 1 S
03099 BEGIN CONSTRUCTION 1 S
03599 1ST RPT CONSTRUCTION PROGRESS 1 R
03699 2ND RPT CONSTRUCTION PROGRESS 1 R
03799 3RD RPT CONSTRUCTION PROGRESS 1 R
0389 4TH RPT CONSTRUCTION PROGRESS 1 R
03999 5TH RPT CONSTRUCTION PROGRESS 1 R
04599 END CONSTRUCTION 1 S
05099 BEGIN DISCHARGE 1 S
05199 END DISCHARGE 1 S
05599 OPERATIONAL LEVEL ATTAINED 1 S
05699 FINAL COMPLIANCE W/EFF LIMITS 1 S
=—=====================================================
240 DATA SOURCE CODES (DSCD)
0700 99ZZ
0701 O4AL
0702 1 OAK
0703 O9AS
0704 O9AZ.
0705 O6AR
0706 O9CA
0707 O9CZ
0708 08C0
0709 O1CT
0710 O3DE
0711 O3DC
0712 O4FL
0713 O4GA
0714 O9GU
0715 09 111
0716 1OID
0717 05 1L
0718 05 1N
0719 07 T h
A-4 12/27193 SDC-0055-034-CL-2005
-------
Permit Compliance System (PCS) QNCR Trmning
480 COMPLIANCE VIOLATION CODES (AUTO AND MANUAL) (CVIO)
do R.EPORTED LATE VIOLATION
C20 ACHIEVED LATE VIOLATION
C30 UNACHIEVED VIOLATION
C40 NOT RECEIVED VIOLATION
MOO MPJIUAL COMP VIO (GENERIC)
M1O MANUAL REPORTED LATE VIOLATION
M20 MANUAL ACHIEVED LATE VIOLATION
M30 MANUAL UNACHIEVED VIOLATION
M40 MANUAL NOT RECEIVED VIOLATION
780 OUTFALL TYPE (OZTTT)
EFFLUENT
C CSO
R STORMWATER
S SLUDGE
_—
310 LIMIT TYPE CODES (LTYP)
I INITIAL
H INTERIM
F FINAL
080 MONITORING LOCATION CODES (MLOC)
G RAW SEW/INFLUENT
K PERCENT REMOVAL
1 EFFLUENT GROSS VALUE
5 UPSTREAM MONITORING
6 DOWNSTREAM MONITOR
SDC-0055-034-CL-2005A 12127193 A 5
-------
QNCR Training Permit Compliance System (PCS)
1.20 STATISTICAL BASE CODES (STAT)
AF AVERAGE AVERAGE
DB DAILY AVDAILY AVERAGE A
MB MAXIMUM MAXIMUM
ME MINIMUM MINIMUM
MK MO AVG MONTHLY AVERAGE A
MN NO MAX MONTHLY MAXIMUM
MO NO MIN MONTHLY MINIMUM
WA WKLY AVG WEEKLY AVERAGE
3 C 3 ODA AVG3 0 DAY AVERAGE A
7A 7 DA AVG7 DAY AVERAGE
NOTE: An ‘A’ in the third column indicates that this is the monthly average
for RNC processing.
150 SAMPLE TYPES (SAMP)
COMPOS
F l FLOIND
GR GRAB
G2 GRAB-2
G3 GRAB-3
G4 GRAB-4
G5 GRAB—5
IM IMERSN
IN INSTAN
IS INSITU
IT IMRSTB
MC MATHCL
MP MATHCP
MS MEASRD
RC RCORDR
TN TOTALZ
VI VISUAL
01 COMP—1
12 COMP12
16 COMP16
A-6 12/27/93 SDC-OOS5-O34-CL-2005
-------
Permit Compliance System (PCS) QNCR Training
050 FREQUENCY OF ANALYSIS CODES (FRAN)
01/01 DAILY Y
01/07 WEEKLY Y
01/30 ONCE/ MONTH Y
12/30 12 PER MONTH Y
99/99 CONTINUOUS N
450 CONTESTED PARAMETER CODES
(CONP)
X CONTESTED-STILL PRINTED
ON DMR
Y CONTESTED-NOT PRINTED ON
DNR
180 UNIT CODES
(LQUC)
.Q3 MGD ]MGD ] MILLION GALLONS PER DA’
12 SU ]SU ]STANDARD UNITS (I.E. PH)
15 DEG.F )DEG.F )DEGREES FAHRENHEIT
19 MG/L ]MG/L )MILLIGRANS PER LITER
.23 PERCENT]PERCENT)PERCENT
26 LBS/DYJLBS/DAY )POUNDS PER DAY
490 NO DISCHARGE INDICATOR CODES (NODI)
A GENERAL PERMIT EXEMPTION
B BELOW DETECT LIMIT/NO DETECT
C NO DISCHARGE
1 WRONG FLOW
2 OPERATIONS SHUTDOWN
3 LOW LEVEL PRODUCTION
4 LAGOON PROCESSING
5 FROZEN CONDITIONS
6 PRODUCTION BASED LIMITS DONT APPLY TO MP
7 DMR RECEIVED, PRODUCTION OR FLOW RELATED
8 OTHER
9 MONITORING IS CONDITIONAL/NOT REQ THIS MP
SDC-0055-034-CL-2005A 12/27/93 . A-i
-------
QNCR Training Permit Compliance System (PCS)
550 SINGLE EVENT VIOLATION CODES (SVCD)
01099 NON-COMPLIANCE NOTICE
02099 DISCHARGE WITHOUT A VALID PERMIT
03099 IMPROPER OPERATION AND MAINTENANCE
04099 UNAUTHORIZED BY-PASS
05099 FAILURE TO MEET 77-07-01
06099 SECTION 404 VIOLATION
07099 FAILURE TO MEET SECTION 308 REQUEST
08099 FAILURE TO APPLY FOR A PERMIT
09099 DNR QA
10099 BASELINE MONITORING REPORT VIOLATION
11099 MARINE PROTECTN & SANCTUARY ACT VIOL
12099 VIOLATION DETECTED DURING INSPECTION
13099 FAILURE TO ISSUE SIU PERMITS
14099 FAILURE TO CONDUCT INSPECTIONS
15099 FAILURE TO ESTABLISH SELF-MONITORING REQ
16099 FAILURE TO DEVELOP/ENFORCE PRET STDS.
17099 FAIL TO ENFORCE AGAINST PASS-THRU/INTF.
18099 APPROVAL AUTHORITY VIOL. OF CONCERN
19099 MONITOR FOR TOXICITY REQUIREMENT
20099 SLUDGE VIOLATION
030 ENFORCEMENT ACTION CODES (ENAC)
01 NO CURRENT ACTN WARRANTED 4
03 WARNING LETTER 1
05 PHONE CALL 1
07 MEETING WITH PERMITEE 1
11 ADM ACTION PLANNED 4
13 ADM ACTION PENDING 4
15 SECTION 308 LETTER 4
16 SHOW CAUSE HEARING OR MTG 1
18 ADJUDCTRY HEARING REQUESTED 4
20 NOTICE OF VIOLATION/NOV 1
21 ADMINISTRATIVE ORDER 2-FORMAL EA
25 CONSENT DECREE 3-FORMAL EA
27 JUD ACTION PLANNED 4
29 JUD ACTION PENDING 4
31 REFERRED TO HIGHER LVL REVIEW 4
32 UNDER REVIEW BY STATE AG 4
33 UNDER REVIEW BY EPA HQ 4
34 CEASE AND DESIST ORDER 4
35 STIPULATION COURT ORDER 3-FORMAL EA
A-8 12/27/93 SDC-0055-034-CL-200Y
-------
Permit Compliance System (PCS)
QNCR Tr2ining
Ni
*N2
N3
N4
N7
NB
N9
Si
S2
ADMINISTRATIVE EXTENSION
ADMINISTRATIVELY RESOLVED
CLOSED - BACK INTO COMPLIANCE
COMPLIANCE
CLOSED SUPERSEDED BY EA
NONCOMPLIANCE
PERMIT REVISION
RESOLVED
FOR PERMIT (EPA)
FOR PERMIT (STATE)
FOR PERMIT
MONIT PER OR PIPE
(DlO
(D2 0
(D3 0
(EPA)
(DlO
(ST)
040 ENFORCEMENT ACTION STATUS CODES (ENBT)
AE
AR
CL
CO
CS
NC
PR
RE
340 ENFORCEMENT ACTION VIOLATION TYPES (EVTP)
Cl ALL COMPLIANCE VIOS FOR PERMIT
C2 SPECIFIC COMPLIANCE VIOLATION
El ALL EFFLUENT VIOS FOR PERMIT
E2 EFFLUENT VIOS FOR MONITORING PERIOD
E3 SPECIFIC EFFLUENT VIOLATION
ALL NON-RPT VIOS
ALL NON-RPT VIOS
ALL NON-RPT VIOS
NON-RPT VIOS FOR
VIOLATIONS)
VIOLATIONS)
VIOLATIONS)
VIOLATIONS)
N5 NON-RPT VIOS FOR MONIT PER OR PIPE
N6 NON-RPT VIOS FOR MONIT PER OR PIPE
SPECIFIC NON-RPT VIOLATION (EPA)
SPECIFIC NON-RPT VIOLATION (STATE)
SPECIFIC NON—RPT VIOLATION
ALL SINGLE EVENT VIOS FOR PERil
SPECIFIC SINGLE EVENT VIOL
(D20 VIOLATIONS)
(D3 0
( p10
(D2 0
(D3 0
VIOLATIONS)
VIOLATIONS)
VIOLATIONS)
VIOLATIONS)
SUL-1JU -Ui4-LL-2UtbA
12121/93
A-9
-------
QNCR Trainng Permit Compliance System (PCS
195 RNC DETECTION CODES (SNCC)
A ENF-ADMINISTRATIVE ORDER
B DIS-MANUAL 2A4- PASS THROUGH
C CHR-CHRONIC VIOLATION
D DIS-MANUAL OTHER
E DIS-MANUAL 2F - PERMIT NARRATIVE
F DIS-MANUAL 2G - VIOLATION OF CONCERN
G DIS-MANUAL 2A1. - EFFLUENT VIOLATION
I DIS-MANUAL 2A2 - UNAUTHORIZED BYPASS
J DIS-MANUAL 2A3 - UNAUTHORIZED DISCHARGE
N RPT - NONRECEIPT OF DMR/CS REPORT
Q DIS-MANUAL 2B - PRETREATMENT
T TRC-TRC LIMITATIONS EXCEEDED
V EFF-OTHER VIOLATION WITH TRC
W DIS-MANUAL 2E - DEFICIENT RPT
X EFF—MANUAL OTHER VIOL W/. TRC
Y TRC-MANUAL TRC
Z CHR-MANUAL CHRONIC
39.0 RNC RESOLUTION CODES (SRCC)
A NC-MANUAL UNRESOLVED RNC
B RE-MANUAL BY EPA ACTION
W NC-WAITING RNC RESOLUTION
1 NC-UNRESOLVED RNC
2 RE-BACK INTO COMPLIANCE
3 RP-DUE TO FORMAL EA
4 RP-IN COMPLIANCE LAST QTR
5 RE-RESOLVED RP BY EA W/ CL
6 RE-MANUAL RES BY EA W/ CL
7 RP-MANUAL RP—IN COMP W/ADM LMT
8 RP-MANUAL DUE TO FORMAL EA
9 RE-MANUAL BY BACK INTO COMPL
A-1O 12/27/93 SDC-0055-034-CL-2005”
-------
Permit Compliance System (PCS) QNCR Training
440 QN R STATUS CODES (CYQS)
C COMPLI NT
D NC-SNC DuB NON-RECPT
E NC-SNC EFFLUENT VIOL
N NC-RNC VIOLTNS ONLY
P RESOLVED PENDING
R RESOLVED
S NC-SNC COMP SCHD VIO
T NC-SNC COMP SCHD RPT
SDC-0055-034-CL-2005A 12/27/93 A 1•t
-------
Permit Compliance System (PCS) QNCR Training
Appendix B
SINGLE EVENT VIOLATIONS.
-------
Permit Compliance System (PCS) QNCR Trnining
SINGLE EVENT VIOLATIONS
Single Event Violations are violations that are not part of any other data type in PCS. This
could include the facility operating without a certified operator, an unauthorized bypass of
discharge, etc.
This appendix includes the Key Data Elements to the SV record and PCS-ADE screens
needed to enter Single Event Violation and Enforcement Action data.
Also included are excerpts from:
Table 550 - Single Event Violation Codes
Table 030-Enforcement Action Codes
This appendix is designed to be a pull-out section to be used in training as a guide for in-
depth discussion of how Single Event Violations and Enforcement Actions are entered using
PCS-ADE.
SDC- .0055-034-CL-2005A 12127193 B-I
-------
QNCR Training Permit Compliance System (PCS
Screens
Table 550
Single Event Violation Screen
Table 030
Enforcement Action Screen
Enforcement Action Key Screen
Enforcement Action Key Screen
Enforcement Action Single Event Violation Key Screen
Enforcement Action Key Screen
Enforcement Action Key Screen
Enforcement Action Effluent Key Screen
Enforcement Action Key Screen
Enforcement Action Key Screen 1
Enforcement Action Compliance Schedule Key Screen 2
Enforcement Action Key Screen 2
Enforcement Action Single Event Violation Key Screen 2:
Enforcement Action Key Screen 2
Enforcement Action Key Screen 2
Enforcement Action Effluent Key Screen
B-2 12127/93 SDC-0055-034-CL-2005A
-------
Pennit Compliance System (PCS) QNCR Training
SINGLE EVENT VIOLATIONS
The Key Data Elements to the SV record are:
NPJD ! [ Permit Numberl (field length = 8 characters)
EVSC! [ Event Code] (field length = 5 characters)
This field describes the type of violation that took place.
EVSD! [ Single Event Violation Date] (field length = 6 characters)
This field contains the date the violation took place.
Table 550
550 Sthgte Event VioLatTon Codes
OO INJ LABORATORY NOT CERTIFIED
001DM FREQUENCY OF SAMPLING VIOLATION
00105 DETERMINE COMPLIANCE
00108 SECTION 307 VIOLATIONS
OO2NJ NO LICENSED OPERATOR
OO3NJ INSPECTOR DENIED ACCESS TO FACILITY
O O4NJ FAILURE TO PAY PERMIT FEE
01099 NON-COMPLIANCE NOTICE
02099 DISCHARGE WITHOUT A VALID PERMiT
03099 IMPROPER OPERATION AND MAINTENANCE
04099 UNAUTHORIZED BY-PASS
05099 FAILURE TO MEET 77-07-01
06099 SECTION 404 VIOLATION
07099 FAILURE TO MEET SECTION 308 REQUEST
08099 FAILURE TO APPLY FOR A PERMIT
09099 DMR QA
10099 BASELINE MONITORING REPORT VIOLATION
11099 MARINE PROTECTION & SANCTUARY ACT VIOL
12099 ViOLATION DETECTED DURING INSPECTION
13099 FAILURE TO ISSUE SW PERMETS
14099 FAILURE TO CONDUCT INSPECTIONS
15099 FAILURE TO ESTABLISH SELF-MONITORiNG REQ
16099 FAILURE TO DEVELOP/ENFORCE PRET STOS.
17099 FAIL TO ENFORCE AGAINST PASS-THRU/INTF
18099 APPROVAL AUTHORITY VIOL. OF CONCERN
SDC-0055-034-CL-2005A 12/27/93 B-3
-------
QNCR Training Permit Compliance System (PCSJ
Example :
Enter a SV record for M00000027 indicating that the permittee failed to meet a section 308
request on August 18, 1987.
Single Event Violation Screen
09:30:03 SINGLE EVENT VIOLATIONS PCOESVIQ
10110189 SCREEN 10: SVIO
• IRAI IS CODE
VIOLATION CODE ____ VIOLATION DATE _____
RNC DETECTION CODE —
RNC DETECTION DATE ______
RUC RESOLUTION CODE —
RNC RESOLUTION DATE. ______
REGIONAL FIELD I REGIONAL FIELD 2 _______
ACCEPT? tf /M: T VERSION 2.1 10/06/89
Enforcement Actions
Enforcement Actions are structured into 2 records.
• Enforcement Action record (EA)
• Enforcement Action Key record (EK).
EA records contain general overview information about the enforcement action, i.e., the EA 1
code, date, docket number, comments, etc. There is one EA record for each enforcement
action.
EK records contain detailed information about the violations that the enforcement action
addresses. They contain the type of violations addressed, and the keys to the violations, if
necessary. There are many EK records for each EA record.
12/27193 SDC 0055-034-CL-200
-------
Permit Compliance System (PCS) QNCR Training
EA Record
The Key Data Elements to the EA record are:
NPID*! [ Permit Numberj (field length = 8 characters)
ENAC! [ Enforcement Action Code] (field length = 2 characters)
This field describes the type of action taken.
Table 030
030
01 NO CURRENT ACTN WARRANTED 4
03 WARNING LETTER I
05 PHONE CALL 1
20 NOTICE OF ViOLATION/NOV 1
21 ADMINISTRATIVE ORDER 2
25 CONSENT DECREE 3
27 JUD ACTION PLANNED 4
29 JUD ACTION PENDING 4
31 REFERRED TO HIGHER LVI REVIEW 4
ENDT! [ Enforcement Action Date] (field ‘length = 6 characters)
EATP! ‘ ‘ ‘ , (field length = I character)
[ Type Order Issued (Issuing Authority)]
EEPA
S State
Other Data Elements on the EA record (not Keys)
ENST* [ EA Sthtus Code] (field length = 2 characters)
This code indicates the status of the enforcement action. It’s not important to enter anything
in this field until the EA is closed. Then enter closed (CL) or closed by a superseding EA
(CS).
SDC-0055-034-CL-2005A ‘ ‘ 12/27/93
-------
QNCR Training Permit Compliance System (PCS
ERFN* [ FSA File Number] (field length = 10 characters)
it is important to ensure that the docket number is entered in exactly the same manner as the
docket number on the CS and EF records. Choose to always either left or right justify
docket numbers and use thAt method unfailingly.
ECM1 through ECMO [ EA Comments] (fields = 30 characters each]
These comment fields relate to the entire enforcement action. These comments will appear
on the QNCR.
B -b 12/27/93 SDC -0055 -034 -CL -200 5S
-------
Permit Compliance System (PCS) QNCR Training
EA Violation Key
The Key Data Elements to the EK record are:
NPLD*! [ Permit Number] (field length = 8 characters)
EKAC! [ EK Enftwcement Action Code] (field length = 2 characters)
This field describes the type of action taken.
EKDT! [ EK Enforcement Action Date] (field length = 6 characters)
EKTP! (field length = 1 character)
[ Type Order Issued (Issuing Authority)]
EEPA
S State
EVTP! [ EA Violation Type] (field length = 2 characters)
For each EK record, this field describes the type of violations to which the EA record is
lin ked. There are four types of EVTP’s: those that address effluent, compliance schedule,
non-reporting and single event violations. In addition, the EVTP is chosen to associate the
enforcement action with either individual violations or groups of violations.
E3 - tied to an individual effluent violation
E2 - tied to all violations for a monitoring period
and/or pipe
El - tied to all effluent violations since last EA
C2 - tied to an individual CS
Cl - tied to all CS violations since last EA
S2 - tied to an individual SV violation
Si - tied to all SV violations
Ni
to - similar to the effluent choices
N9
In conjunction with these, it may be necessary to enter the Keys for the violations.
SDC-0055-034-CL-2005A 12/27/93 B-i
-------
QNCR Training Pennit Compliance System (PCS
Example :
An EK record tied to all effluent violations (EVTP=El) would not require any Keys to be
entered.
An EK tied to a specific effluent violation (EVTP=E3) would require that all Keys related to
the specific violation be provided, (i.e.; outfall number, parameter, etc.).
B-S 12127/93 SDC- 0055-034-CL-200cK
-------
Permit Compliance System (PCS) QNCR Training
PCS-ADE Screens for Enforcement Actions
The top portion of the ENAC screen is used to enter information for the EA record.
The information below the heading “Violations that caused the enforcement action to be
issued” is used to enter data for the EK records. To enter EK records that address all
violations of a certain type, enter an X in next to that option. (An * next to the option
deletes the EK record.) The system will generate the transaction to enter the EK record. To
enter an EK record to address specific violations, place an X next to the Specific Violations
option.
Enforcement Action Screen
10:55:00 ENFORCEMENT ACTION PCDEENAC
12/21189 SCREEN ID: ENAC
PERMiT # _________ TRANS CODE —
ENFORCEMENT ACTION CODE ISSUED BY — DATE _____
STATUS CODE — STATUS DATE ______
DOCKET NUMBER ____________ CLOSURE SCHEDULED DATE ______
IN 1TIAT INC PARTY 1 ______ INITIATING PARTY 2 ______
RESPONSE DUE DATE ______ RESPONSE ACHIEVED DATE —
VIOLATION RECOGNITION DATE ______ USER DATA ELEM : #1 — #2 ______
- - - - ENFORCEMENT ACTION COMMENTS - - - -
#1 ___________________________ #2 ___________________________
#3 _________ #4 _________
#5 _________ #6 _________
#7 _________ #8 _________
#9 ________________________ #10 ________________________
- - VIOLATIONS’THAT’ CAUSED THE ENFORCEMENT ACTION TO BE ISSUED - - -
— ALL NUMERIC EFFLUENT’ ALL STATE NON-RECEIPT ‘ SPECIFIC
— ALL COMPLIANCE SCHEDULE — ALL EPA NON-RECEIPT VIOLATIONS
— ALL SINGLE EVENTS — ALL EPA + STATE NON-RECEIPT’
ACCEPT? Y/K/NfH: Y. VERSION ‘2.3 11/27/89
SDC-OO55-O34-CL-2OO5A
12I 1I9i
-------
QNCR Training Permit Compliance System (PCS:
Example :
GA0000125 was issued a consent decree on 072387 by EPA. The docket number is 87-
4536. The enforcement action addressed all effluent and all compliance schedule violations.
How would this information be entered on the ENAC screen?
10:55:00 ENFORCEMENT ACTION PCDEENAC
12/21/89 - SCREEN ID: ENAC
PERMIT # ________ TRANS CODE -
ENFORCEMENT ACTION CODE — ISSUED BY — DATE _____
STATUS CODE STATUS DATE ______
DOCKET NUMBER ___________ CLOSURE SCHEDULED DATE ______
INIT iATING PARTY 1 ______ INITIATING PARTY 2 ______
RESPONSE DUE DATE ______ RESPONSE ACHIEVED DATE ______
VIOLATION RECOGNITION DATE ______ USER DATA ELEMENT: #1 — #2 ______
- - - - ENFORCEMENT ACTION COMMENTS - - - -
#1 ___________________________ #2 ___________________________
#3 _________ #4 _________
#5 _________ #6 _________
#7 _________ #8 _________
#9 _______________________ #10 ________________________
- - - VIOLATIONS THAT CAUSED THE ENFORCEMENT ACTION TO BE ISSUED - - -
— ALL NUMERIC EFFLUENT ALL STATE lION-RECEIPT SPECIFIC
— ALL COMPLIANCE SCREDULE ALL EPA NON-RECEIPT VIOLATIONS
— ALL SINGLE EVENTS — ALL EPA + STATE NOtl-RECE1PT
ACCEPT YfK/N/M: V VERSION 2.3 11/27/89
If an X is entered at the Specific Violations Option on the ENAC screen, the EAKS screen
will be displayed. All available information from the previous screen will be displayed. Th
EAKS screen may also be accessed from the PCS-ADE Main Menu. There are a total of
seven (7) EAKS screens that may be encountered, depending on the data entered on the
ENAC screen.
B-lO 12/27/93 SDC-O055-O34-CL-2O0
-------
Permit Compliance System (PCS) QNCR Training
08:20:00 PCS-ADE PCDEEA S
01104/90 SCREEN ID EA S
ENFORCEMENT ACTION
KEY SCREEN
PERMIT # _________
TRANS C E —
ENFORCEMENT ACTION C E —
TYPE ORDER ISSUED —
ENFORCEMENT ACTION DATE _____
VIOLATION TYPE -
00 YØJ WISH TO CYCLE (YIN)?
ACCEPT (YIN/N)? V VERSION 2.3 11/21189
The CYCLE option may be used to have the system display violations. When the CYCLE
option is selected, the system prompts the user to narrow the violations to be displayed. The
prompt displayed depends on the EVTP entered. The system prompts for the keys to the
violation records. fl will only display those violations that meet the key criteria.
Two of the accept options used with cycling, C and S. may require some additional
explanation. if C is entered in the accept option while cycling, an EK record for the
displayed violation is generated, and PCS-ADE will cycle to the next violation. If S is
entered, the violation is skipped, no EK record is generated, and PCS-ADE will cycle to the
next violation.
SDC-0055-034-CL-20 05A 12/27/93 B-li
-------
QNCR Training Permit Compliance System (PCS
Cycling Through Single Event Violations
Step 1: Enter the EA information on the first EAKS screen, .
Enforcement Action Key Screen
08:20:00 PCS-A DE PCOEEAKS
01104/90 SCREEN ID: EAJCS
ENFORCEMENT ACTION
KEY SCREEN
PERMIT # ma0101478
TRA NS CODE n
ENFORCEMENT ACTION CODE 21
TYPE ORDER ISSUED e
ENFORCEMENT ACTION DATE 060787
VIOLATION TYPE s2-
DO Y i WISH TO CYCLE CT/N)? y
ACCEPT (YIN/N)? Y VERSION 2.3 11127/89
B-12 12127193 SDC-OO55-O34-CL-2O0 --
-------
Permit Compliance System (PCS) QNCR Training
Step 2: PCS-ADE prompts you to narrow the SV records to be cycled through. Leaving
these prompts empty will cause PCS-ADE to cycle through all SV records.
Enforcement Action Key Screen
08:20:00 PCSADE PCDEEAICS
01/04/90 SCREEN ID EAKS
ENFORCEMENT ACTION
KEY SCREEN
PERMIT MA 01o14 7 8
TRANS CODE N
ENFORCEMENT ACTION CODE 21
TYPE ORDER ISSUED E
ENFORCEMENT ACTION DATE 060787
VIOLATION TYPE S2
DO YOU WISH TO CYCLE Cl/N)? V
VIOLATION CODE ____
VIOLATION DATE ______
ACCEPT (YIN/N)? Y VERSION 2.3 11/27189
SDC-0055-034-CL-2005A 12/27/93 B- 13
-------
QNCR Training Permit Compliance System (PCS
Step 3: PCS-ADE displays the first SV record on file..
Enfi,rceme,u Action Single Event Violation Key Screen
08:22:00 £NFORCENEIIT ACTION SiNGLE EVENT VIOLATION KEY SCREEN P EEASF
01/04/90 SCREEN ID: ES.KS
PERMIT * MA0101478 TRMS CODE N SCREEN ID: EAKS
ENFORCEMENT ACTION CODE 21 ADMINISTRATIVE ORDER
iSSUED BY E EPA ENFORCEMENT ACTION DATE 060787
V LATION TYPE $2 SPECIFIC SINGLE EVENT VIOLATION
SINGLE EVENT VIOLATION CODE 02099
SINGLE EVENT VIOLATION DATE 081886
ACCEPT (Y/NIC/S/M)? c VERSION 2.1 11/27/89
Two of the options used wth cycling are:
C When C is entered in the accept option while cycling, an EK record for the displayed
violation is generated and PCS-ADE will cycle to the next violation.
S When S is entered, the violation is skipped, no EK record is generated, and PCS-
ADE will cycle to the next vio’ation.
B-!4 SDC-0055-034 -CL-2005
-------
Permit Compliance System (PCS) QNCR Training
Cycling Through Effluent Vio’ations
Step 1: Enter the EA information on the first EAKS screen, .
Enforcement Action Key Screen
08:20:00 PCS- DE PCDEEAXS
01/04/90 SCREEN ID EAICS
ENFORCEMENT ACTION
KEY SCREEN.
PERMIT # ky0001929
TRANS C E i -
ENFORCEMENT ACTION C E 07
TYPE ORDER ISSUED e
ENFORCEP(ENT ACTION DATE 041587
VIOLATION TYPE e3
DO T J WISH TO CYCLE (YIN)? y
ACCEPT (Y/N/N)? Y VERSION 2.3 11 27/89
SDC -0055-034 .CL-2005A 12/27/93 B-15
-------
QNCR Tr2ining Permit Compliance System (PCSI
Step 2: PCS-ADE prompts you to narrow the measurement violation records you wish to
cycle through. Only violations on outfall 0011, final limits will be displayed in
this example.
Enforcement Action Key Screen
Q8 20:0O PCS-ADE PCDEEAICS
01/04/90 SCREEN ID: EAKS
E1IFORCENENT ACTION
KEY SCREEN
PERMIT # KY0001929
TRANS CODE N
ENFORCEMENT ACTION CODE 07
TYPE ORDER ISSUED E
ENFORCENEKT ACTION DATE 041587
VIOLATION TYPE E3
DO YOU WISH TO CYCLE (V/N)? E
DISCHARGE NL BER 001
REPORT DESIGNATOR I
LIMIT TYPE f
PARAMETER CODE _____
MONITORING LOCATION —
MONITORING PERIOD EkD DATE ______
B-16 12/27/93 SDC-OO55-O34-CL-2OO
-------
Pennit Compliance System (PCS) QNCR Training
Step 3: The first effluent violation for the given key information is displayed.
Enforcement Action Effluent Key Screen
08:20:15 ENFORCEMENT ACTION :EFFL T KEY SCREEN PCDEEAEF
01/04190 SCREEN ID: EAKS
PERMIT H KY0001929 TRANS CODE N
ENFORCEMENT ACTION CODE 07 MEETING 111TH PERMITTEE
ISSUED BY E EPA EJIFORCEMENT ACT iON DATE 041581
VIOLATION TYPE B SPECIFIC EFFLUENT VIOLATION
DISCHARGE H 001
DISCHARGE DESIGNATOR I
LIMIT TYPE 5
PARAMETER CODE 00011
MONITORING LOCATION 1
SEASONAL H 0
MODIFICATION NLmBER 0
MONITORING DATE 113084
ACCEPT CY/N/C/S/M)7 s VERSION 2.2 11/27/89
SDC - 0 055 - 034 -CL -2 0 05A 12 /2 7 193 B -li
-------
QNCR Training Permit Compliance System (PCS
Cycling Through Compliance Schedule Violations
Step 1: Enter the PA information on the first EAKS screen, .
Enforcement Action Key Screen
08:20:00 PCS-ADE PCDEEA)S
01/04/90 SCREEN ID EAKS
ENFORCEMENT ACTION -
KEY SCREEN
PERMIT I ak000lT ll
TRANS CODE n
ENFORCEMENT *crsou CODE 01
TYPE ORDER ISSUED s
ENFORCEMENT ACTION DATE 070986
VIOLATION TYPE cZ
DO YW WISH TO CYCLE (YiN)? y
ACCEPT (YIN/N)? Y VERSION 2.3 11/27/89
B-18 12/27193 SDC-OO55-O34-CL-2OO
-------
Permit Compliance System (PCS) QNCR Training
Step 2: PCS-ADE prompts for CS keys to narrow the display of compliance violation
records. Only those records with a compliance schedule number of 01 will be
displayed in this example.
Enforcement Action Key Screen
08:20:00 PCS-ADE PCOEEA1CS
01104 /90 S EEti ID: EAKS
E)IFORCEMEMT ACTION
KEY SCREEN
,t.
PERMIT AK000 I7II
TRANS CODE N
ENFORCEMENT ACTION CODE 01
TYPE ORDER ISSUED S
ENFORCEMENT ACTION DATE 070986
VIOLATION TYPE C2
DO YOU WISH TO CYCLE (YIN)? Y
COMPLIANCE SCHEDULE NUMBER 01
DATA SOURCE CODE
COMPLIANCE SCHEDULE NUMBER _____
VIOLATION CODE
ViOLATION DATE ______
SDC-0055-034-CL-2005A 12/27/93 B-19
-------
QNCR .Tnthiing Pennit Compliance System (PCS)
Step 3: PCS-ADE displays the first compliance schedule violation record on file for the
keys.
Enforcement Action Compliance Schedule Key Screen
08:21:00 ENFORCEMENT ACTION C PLIANCE SCHEDULE KEY SCREEN PCDEEACS
01/04/90 SCREEN IO:EAKS
PERMIT C AK00011T1 TRANS CODE N SCREEN ID: EAKS
ENFORCEMENT ACTION CODE D I NO OJRRENT ACTM ‘IIARRANTE
ISSUED BY S STATE ENFORCEMENT ACTION DATE 071086
VIOLATION TYPE C2 SPECIFIC COMPLIANCE VIOLATION
CONPLIA1 CE SCHEDULE # 01 DATA SOURCE CODE 0790
COMPLIANCE SCHEDULE EVENT CODE 00599
COMPLIANCE VIOLATION CODE C20 COMPLIANCE VIOLATION DATE 121984
ACCEPT (YIN/C/S/N)? $ VERSION 2.2 11/27/89
B-20 12/27/93 SDC OO55 .O34 CL 2OO A
-------
Permit Compliance System (PCS)
Entering an EK record for a Single Event Violation w/o Cycling
Step 1: Enter the PA information on the first EAKS screen, .
Enforcement Action Key Screen
QNCR Training
SDC-0U55-034-CL-2005A
12/27/93
ii- 1
-------
QNCR Training Permit Compliance System (PCS
Step 2: PCS-ADE displays information above the dotted line, you enter the keys to the
violation in the fields below the dotted line.
Enforcement Action Single Event Violation Key Screen
08:22:00 ENFORCENENT ACTION SINGLE EVENT VIOLATiON KEY SCREEN PCOEEASF
O1/O(,/90 SCREEN ID: EAKS
PERMIT NA0000 027 TRANS CODE N
ENFORCEKENT ACTION CODE 21 ADNINISTRATIVE ORDER
ISSUED BY S STATE ENFORCEMENT ACTION DATE 103186
VIOLATION TYPE S2 SPECIFIC SINGLE EVENT VIOLATiON
SINGLE EVENT VIOLATION CODE 02099
SINGLE EVENT VIOLATION DATE 040186
ACCEPT CT/N/iC/N)? Y VERSION 2.1 11/27/89
S-22 12/27/93 SDC-0055-034-CL-20054
-------
QNCR Tr iining
Permit Compliance System (PCS)
Entering an EK record for a Specific Effluent Violation w/o Cycling
Step 1: Enter the EA information on the first EAKS screen, .
Enforcement Action Key Screen
UC4)U -4J34-CL-2UU ,A
IhIh IIY)
13-23
-------
QNCR Training Permit Compliance System (PCS:
Step 2: The Key screen is displayed and the user enters the TRANS code, violation type
and a CYCLE option response of (N).
Enforcement Action Key Sc ieen
08:20:00 PcS E P DEEA1CS
01/04/90 SCREEN ID: EAKS
ENFORCEMENT ACTiON
KEY SCREEN
PERMIT I C00001511
TRANS CODE N
ENFORCEMENT ACTION CODE 21
TYPE ORDER I SSUED £
ENFORCEMENT ACTION DATE 010185
VIOLATION TYPE £3
DO Y J WISH TO CYCLE CT/N)? n
ACCEPT (YiN/N)? Y VERSION 2.3 11/27/89
B-24 12/27/93 SDC-OO55-O34-CL-2OO
-------
Permit Compliance System (PCS) QNCR Training
Step 3: PCS-ADE displays the information above the dotted line. The user identifies the
specific violation being addressed by providing the keys to the measurement below
the dotted line.
Enforcement Action Effluent Key Screen
08:20:15 EIIFORCEMENT ACTION EFFLUENT KEY SCREEN PCDEEAEF
01/04/90 SCREEN ID: EAKS
PERMIT I C00001S11 TRANS CODE N
ENFORCEMENT ACTION CODE 21 ADNINISTRATIVE ORDER
ISSUED BY E EPA ENFORCEMENT ACTION DATE 010185
VIOLATION TYPE E3 SPECIFIC EFFLUENT VIOLATION
- DISCHARGE I MC
DISCHARGE DESIGNATOR A
LIMIT TYPE F
PARAMETER CODE 00530
MONITORING LOCATION 1
SEASONAL 1 0
MODIFICATION NL BER 0
MONITORING DATE 103184
ACCEPT CY/N/M)? V VERSION 2.2 11/27/89
SDC-0055-034-CL-2005A 12/27/93 B-25
-------
QNCR Training Permit Compliance System (PCS)
Problem :
ME0025438 had an administrative order issued by the State on 081987. It addressed all
effluent violations during March and April of 1987.
10:55:00 ENFORCEMENT ACTION PCDEEMAC
12/21/89 SCREEN ID: ENAC
PERMIT I ________ TRAilS CODE
ENFORCEMENT ACTION CODE — ISSUED BY — DATE ______
STATUS CODE — STATUS DATE ______
DOCKET NUMBER __________ CLOSURE SCHEDULED DATE _____
INITIATING PARTY 1 ______ INITIATiNG PARTY 2 _____
RESPONSE DUE DATE ______ RESPONSE ACHIEVED DATE ______
VIOLATION RECOGNITION DATE ______ USER DATA ELEMENT: #1 #2 ______
- - - ENFORCEMENT ACTION COMMENTS - - -
#1 __________________________ #2 __________________________
#3 _________ #4 _________
15 _________ 16 _________
#7 _________ #8 _________
#9 _____________ #10 _____________
- - - VIOLATIONS THAT CAUSED THE ENFORCEMENT ACTION TO BE ISSUED - - -
— ALL NUMERIC EFFLUENT — ALL STATE NON-RECEIPT SPECIFIC
— ALL COMPLIANCE SCHEDULE ALL EPA NO$l-RECE!PT VIOLATIONS
— ALL SINGLE EVENTS — ALL EPA + STATE NON-RECEIPT
ACCEPT? Y1 IN/N : Y VERSION 2.3 11/27/89
B-26 12/27/93 SDC-0055-034 -CL-2005
-------
Permit Compliance System (PCS)
QNCR Training
SDC4X)55-O34 CL-2OO5A
12/27/93
B-27
-------
Permit Compliance System (PCS) QNCR Training
Appendix C
DEFINITIONS
-------
Permit Compliance System ( PCS ) QNCR Training
DEFENITIONS
This appendix presents key PCS QNCR definitions.
Reportable Noncompliance
Any violation appearing on a QNCR which meets at least RNC criteria.
Effluent Violations
• Any monthly average parameter effluent violation that meets TRC criteria at least two
times during two consecutive quarters (same DSDG and MLOC).
• Any monthly average parameter viilafion of the permit limit for the same parameter
occurring least f times during two consecutive quarters (same DSDG and
MLOC).
• Any violation of interim limits established in a formal administrative order.
Schedule Violations
J1 permit and formal enforcement action schedule milestones that are not achieved within 30
or 90 days of their schedule date depending on the type of compliance schedule.
Report Violations
• fl3 report that is not submitted by the due date and is overdue by 30 days or more
days.
• Failure to submit required reports or any incomplete or deficient report submissions,
including: -
• Non-receipt of measurements, at the parameter level
- Discharge Monitoring Reports (DMRs)
- Pretreatment Compliance Reports
- Final Compliance Schedule Reports.
SDC-0055 -034-CL-2005A 12/27/93 C-I
-------
QNCR Training Permit Compliance System (PCS)
Administrative Order Violations
Interim Effluent Limits
• Any violation of an interim effluent limit cited in an administrative order.
Other Violations
Single Event
• Any violation that is not an effluent violation, compliance schedule violation or
reporting violation. These include a failure to: pay penalties; maintain required
staffing; follow prescribed operations, maintenance procedures and pretreatment
violations; etc.
C-2 12/27/93 SDC-0055-034-CL-2005A
-------
Permit Compliance System (PCS) Tr iining
Appendix D
PCS Acronym Reference List
-------
Permit Compliance System (PCS) QNCR Training
Acronym Reference List
Acronym Field Name Field Length
Permit Facility Data
NPID*! PERMIT # 009
FNML* FACILITY NAME LONG 120
FNMB FACILITY NAME SHORT 030
OPFL COGNIZANT OFFICIAL 030
TELE TELEPHONE 010
CITY* CITY CODE 005
CNTY* COUNTY CODE 003
SIC2* SIC CODE 004
CFRC CODE OF FEDERAL REGULATIONS . 003
TYPA TYPE OF APPLICATION . . 002
TYPO* FACILITY OWNERSHIP . 003
ORID ORIGINAL PERMIT ISSUANCE DATE 006
EPST* ISSUED BY . 001
REIS REISSUANCE # .001
PRET* PRETREATMENT PROGRAM REQUIRED INDICATOR 001
FDGR* FEDERAL GRANT INDICATOR 001
N WS NEW SOURCE/DISCHARGE CODE 002
N DT NEW SOURCE/DISCHARGE DATE 006
FLIN* FINAL LIMITS INDICATOR 001
WQUA WATER QUALITY LIMITS . 002
IACC* FACILITY INACTIVE CODE . 001
IADT* FACILITY INACTIVE DATE 006
CSDN CONSOLIDATED PERMIT # 012
CSID CONSOLIDATED SYSTEM FACILITY IDENTIFIER 015
NEED NEEDS SUFFIX 003
STNO STATE PERMIT # 008
FFID FEDERAL PERMIT # 012
CAID CONTROL AUTHORITY PERMIT # 009
RPID RECEIVING POTW PERMIT# 009
RPRI REGIONAL PRIORITY PERMIT 001
SUBR SUB-REGION CODE 002
ATNY ATTORNEY INITIALS 003
ENGI ENGINEER INITIALS 003
FLOW* AVERAGE DESIGN FLOW 005
ARCH ARCHIVAL INDICATOR 001
BAS6* RIVER BASIN CODE . 010
RWAT RECEIVING WATERS 035
SDC-0055-034-CL-2005A 12/27/93
-------
QNCR Training Permit Compliance System (PCS
Acronym Yield Name Field Lenqtt
ERIN REARING INDICATOR oo:t
FILE #
ERS3. ISSUE CODES 00
EH S2 ISSUE CODES 00
ERS3 ISSUE CODES 003
DOCKET # 012
RDP1 REGIONAL DATA FIELD #1 00]
RPD2 REGIONAL DATA FIELD #2 00]
.RPD3 REGIONAL DATA FIELD #3 O0
RPD4 REGIONAL DATA FIELD #4 0O
RPD5 REGIONAL DATA FIELD #5 00.
RPD6 REGIONAL DATA FIELD #6 002
RPD7 REGIONAL DATA FIELD #7 00
RPD8 REGIONAL DATA FIELD #8 00
RFD9 REGIONAL DATA FIELD #9 OOE
RPD1O REGIONAL DATA FIELD #10 05(
NPSC* NPSC-NMP STAT 00:
NPFF* NPPF-NMP PIT 00:
NPSQ* NPSQ-NMP QTR 0O
P7MB PREVIOUS YEAR MANUAL QNCR STATUS 00
PYM 1 October through December
PYN2 January through March
PYN3 April through June
PYN4 July through September
CYNS* CURRENT YEAR MANUAL QNCR STATUS 001
CYM1 October through December
CYN2 January through March
CYM3 April through June
CYM4 July through September
NNAM FACILITY NAME 03
MST1 ADDRESS LINE1 03
MST2 ADDRESS LINE2 030
NCTY CITY 02
MSTT STATE 00
MZIP ZIP 009
ANAN FACILITY NAME 03’
AST 1 ADDRESS LINE1 03
AST2 ADDRESS LINE2 03b
ACT? CITY 023
ASTT STATE 00
AZIP ZIP 00
RNN( FACILITY NAME 030
RST1 ADDRESS LINE1 03
RST2 ADDRESS LINE2 03
RCTY CITY 02
RSTT STATE 002
RZIP ZIP 00
D-2 12/27/93 SDC-O055-O34-CL-20O
-------
Permit Compliance System (PCS) QNCR Training
Acronym Field Name Field Length
RTEL TELEPHONE 010
ONAX FACILITY NAME 030
OST]. ADDRESS LINE3. 030
OST2 ADDRESS LINE2 030
OCTY CITY 023
OSTT STATE 002
OZIP ZIP 009
OTEL TELEPHONE olO
EMAIl FACILITY NAME 030
EST1 ADDRESS LINE1 030
EST2 ADDRESS LINE2 030
ECTY CITY 023
ESTT STATE 002
EZIP ZIP 009
ETEL TELEPHONE 010
STTE STATE CODE 002
MADI MAJOR DISCHARGE INDICATOR 001
CYNM CITY NAME 030
CNTN COUNTY NAME 030
FTYP FACILITY TYPE 001
Acronym Field Name Field Length
Permit Event Data
PTEV*! PERMIT TRACKING EVENT CODE 005
APRD* P1099 APPLICATION RECEIVED DATE
PNOT* P3099 PUBLIC NOTICE DATE
PERD* P4099 PERMIT ISSUANCE DATE
PERE* P5099 PERMIT EXPIRATION DATE
30099 PERMIT MODIFICATION DATE
PTSC PERMIT TRACKING EVENT SCHEDULED DATE 006
PTAC* PERMIT TRACKING EVENT ACTUAL DATE 006
PTCO PERMIT TRACKING EVENT COMMENT 030
SDC-OO55 O34-CL-2005A 12/27/93 D-3
-------
QNCR Training Permit Compliance System (PCS
Acronym Field Name Field Lanat1
Compliance Schedule Family
CSCH*! COMPLIANCE SCHEDULE NUMBER 002
DSCD*! DATA SOURCE CODE 004
EVNT*! COMPLIANCE SCHEDULE EVENT CODE 0O
DTSC* COMPLIANCE SCHEDULE EVENT SCHEDULED DATE 006
DTAC* COMPLIANCE SCHEDULE EVENT ACTUAL DATE 00
DTRC* COMPLIANCE REPORT RECEiVED DATE 00’
COMM COMPLIANCE COMMENT 030
CSFN* DOCKET NUMBER OOP
USER DATA ELEMENT #1 oo:
USER DATA ELEMENT #2 00
CVIO! COMPLIANCE SCHEDULE ‘VIOLATION CODE’ 003
CVDT! COMPLIANCE SCHEDULE ‘VIOLATION DATE’ 00
VCSN I COMPLIANCE VIOLATION NUMBER
cv v1 COMPLIANCE VIOLATION EVENT CODE
VDCD! COMPLIANCE VIOLATION DATA SOURCE CODE
D-4 12/27/93 SDC-0O55-034-CL-2OO
-------
Permit Compliance System (PCS) QNCR Training
Acx onym Field Name Field Length
Inspection Scheduling Data Type
STYP! SCHEDULED INSPECTION TYPE 001
SINS! SCHEDULED INSPECTOR CODE 001
SIDT! SCHEDULED INSPECTION DATE 006
SIQR! SCHEDULED INSPECTION QTR/YEAR 003
SDTI ACHIEVED INSPECTION DATE 006
ISC 1 INSPECTION SCHEDULING COMMENTS field 1 030
18C2 INSPECTION SCHEDULING COMMENTS field 2 030
ISC3 INSPECTION SCHEDULING COMMENTS field 3 030
RTYP REVISED SCHEDULED INSPECTION TYPE 001
RINS REVISED SCHEDULED INSPECTOR CODE 002.
RIDT REVISED SCHEDULED DATE 006
RIQR REVISED SCHEDULED QTR/YERR 00.3
Acronym Field Name Field Len th
Inspection Data Type
DTIN! INSPECTION DATE 006
TYPI! INSPECTION TYPE 001
INSP* INSPECTOR CODE 001
PACC INSPECTED FACILITY TYPE 001
BIOM BIOMONITORING INSPECTION METHOD 001
QABI QA-DATA BASED INSPECTION 001
ICON INSPECTION COMMENT 050
1C25 INSPECTION COMMENT (first 25 characters)
TOTAL HOURS (PRE/INSP/POST) : 003
PRHR INSPECTION PRE PROCESSING HOURS
INER INSPECTION IN_PROCESSING HOURS
POHE INSPECTION POST-PROCESSING HOURS
FEVR FACILITY EVALUATION RATING 003
DTRR DATE REPORT RECEIVED 006
RDI1 USER DATA ELEMENT #1 003
RDI2 USER DATA ELEMENT #2 006
SDC-0055034-CL-2005A TZ1Z71 3 D-5
-------
QNCR Tr2ining Permit Compliance System (PCS
Acronym Field Name Field Lenq tI
Pretreatment Compliance Inspection Data Type
DTIAI DATE OF PRETREATMENT COMPLIANCE INSPECTION 00
SIUS* NUMBER OF SIGNIFICANT INDUSTRIAL USERS 004
CIUS* NUMBER OF CATEGORICAL INDUSTRIAL USERS 004
NOIN* StUB NOT INSPECTED OR SAMPLED 002
NOCM* StUB WITHOUT CONTROL MECHANISMS 00:
PSNC* BIDS IN BNC WITH STANDARDS OR REPORTING O0
MBNC* StUB IN SNC WITH SELF-MONITORING 0 0
SNIN* BIDS IN BNC W/ SELF-MON. & NOT INSP. OR SAMPLED 00
COOR PRETREATMENT COORDINATOR NAME 02
PRCR PROGRAM ELEMENT CHANGES 00€
NOPT % OF BIDS WHICH RAVE NOT INST. REQ PRETREATMENT 003
SNPS BIDS IN SNC WITH: PRETREATMENT STANDARDS oo:
RSNC StUB IN SNC WITH: REPORTING REQUIREMENTS O0
ERGG ENFORCEMENT RESPONSE GUIDE 002
SUPP DOES PCI SUPPORT MOST RECENT PRET. SUMMARY REPORT oo:
CMDF CONTROL MECHANISM DEFICIENCIES 00
FIDP DEFICIENCIES NOTED IN ID FILE REVIEW 0O
D uAl DATE OF PRETREATMENT COMPLIANCE INSPECTION 00
WS’!E ACCEPTANCE OF OTHER WASTE 00
RECR REMOVAL CREDITS 00
RCRD REMOVAL CREDITS APPROVAL DATE 005
RSCH RESPONSE TO SCHEDULE FOR REMEDIAL MEASURES
VSCH VIOLATION TO SCHEDULE FOR REMEDIAL MEASURES 00
DSSM PROGRAM MOD. TO ADDRESS: DOMESTIC SEWAGE STUDY 001
PIRT PROGRAM MODIFICATION TO ADDRESS: PIRT AMENDMENTS 00
SMDF DEFICIENCIES IN POTW SAMPLING OP INDUSTRIAL USERS 00
MADP MULTI-JURISDICTIONAL AGREEMENT DEFICIENCIES 00.
PTJU JURISDICTIONS COVERED BY PRETREATMENT PROGRAM 002
RDN2. REGIONAL FIELD 1.
RDN2 REGIONAL FIELD 2 00
D-6 12/27/93 SDC-0055-034-CL-2005
-------
Permit Compliance System (PCS) QNCR Training
Acronym !iel# $ame Field Length
Pretreatment Audit Inspection Data Type
DTIAI DATE OF PRETREATMENT COMPLIANCE INSPECTION 006
PTIM* DATE PERMIT MOD. TO REQUIRE PRET.IMPLEMENTATION 006
NOCM* SIUS WITHOUT CONTROL MECHANISM 003
SIUS* NUMBER OF SIGNIFICANT IUS 005
CIUS* NUMBER OP CATEGORICAL 10 5 005
EVLL* TECHNICAL EVALUATION FOR LOCAL LIMITS 001
ADLL* ADOPTION OF TECHNICALLY-BASED LOCAL LIMITS 001
NOIN* BI OS NOT INSPECTED OR SAMPLED 003
PSNC* SIUS IN SNC WITH STANDARDS OR REPORTING 003
MSNC* SIUS IN SNC WITH SELF-MONITORING 003
SNIN* SIUS IN SNC WITH SELF-MON. I NOT INSP. OR SAMPLED 003
COOR PRETREATMENT COORDINATOR NAME 025
SLDG SLUDGE DISPOSAL METHODS 006
MXPN MAXIMUM CIVIL PENALTY BY LAW 006
BUDG ANNUAL PRETREATMENT BUDGET 006
DTIA! DATE OF PRETREATMENT COMPLIANCE INSPECTION 006
PASS PASS-THROUGH 001
INTF INTERFERENCE 001
TXIN FREQUENCY OF TOXICANT SAMPLING FOR: INFLUENTS 002
TiEF FREQUENCY OF TOXICANT SAMPLING FOR: EFFLUENTS 002
TXSL FREQUENCY OF TOXICANT SAMPLING FOR: SLUDGE 002
SNPS SIUS IN SNC WITH: PRETREATMENT STANDARDS 003
RSNC SIUS IN SNC WITH: REPORTING REQUIREMENTS. 003
ERGG ENFORCEMENT RESPONSE GUIDE 001
RESO INADEQUACIES IN PRETREATMENT RESOURCES 007
FIDF DEFICIENCIES NOTED IN 10 FILE REVIEW 006
CMDF CONTROL MECHANISM DEFICIENCIES 008
LADP LEGAL AUTHORITY DEFICIENCIES 009
APDF DEFICIENCIES IN INTERPRETATION/APPLICATION OF STDS 010
ADIN INADEQUACY IN POTW’S INSPECTION & SAMPLING OF lU’S 004
DTIA I DATE OF PRETREATMENT COMPLIANCE INSPECTION 006
DMDF DEFICIENCIES IN DATA MGMT. & PUBLIC PARTICIPATION 006
SMDF DEFICIENCIES IN POTW SAMPLING OF INDUSTRIAL USERS 005
MADF MULTI-JURISDICTIONAL AGREEMENT DEFICIENCIES 004
PTJU JURISDICTIONS COVERED BY PRETREATMENT PROGRAM 002
WSTE ACCEPTANCE OF OTHER WASTE 005
DSSM PROGRAM MOD. TO ADDRESS: DOMESTIC SEWAGE STUDY 001
PIRT PROGRAM MODIFICATION TO ADDRESS: PIRT AMENDMENTS 001
RECR REMOVAL CREDITS 001
RCRD REMOVAL CREDITS APPROVAL DATE 005
RSCH RESPONSE TO SCHEDULE FOR REMEDIAL MEASURES 001
VSCH VIOLATION TO SCHEDULE FOR REMEDIAL MEASURES 001
NI} IP # OF SIUS NOT SAMPLED OR INSPECTED AT REQ. FREQ. 003
EVCL TECHNICAL EVAL. FOR COMPREHENSIVE LOCAL LIMITS 001
SflC -0055-034 -CL-2005A 12127 /93 D-7
-------
QNCR Training Permit Compliance System (PCS)
Acronym Field Name Field Lencith
NOPT % OF 81138 WE lCH RAVE NOT INSTALLED REQ. PRET. 003,
PRCII PROGRAM ELEMENT CU BGES 006
SUPP SUMMARY REPORT 001
RDN1 REGIONAL PIELD 1 003
RDN2 REGIONAL PIELD 2 00
12127/93 SDC-OO55-O34-CL-20O5
-------
Permit Compliance System (PCS) QNCR Training
Acronym Field Name Pield Lenctth
Pipe Schedule Data Type
DSCE*I DISCHARGE NUMBER 003
DRID*! REPORT DESIGNATOR 001
DSDG! COMBINED DISCHARGE NUMBER AND DESIGNATOR 004
PIPQI PIPE SET QUALIFIER 001
INITIAL REPORT DATE 006
REUN* REPORT UNITS 001
NRPU* NUMBER OF UNITS IN REPORT PERIOD 003
NORP TOTAL NUMBER OP REPORTS DUE 003
STSU* INITIAL EPA SUBMISSION DATE 006
SUUN* EPA SUBMISSION UNIT 001
NSUN* NUMBER OF UNITS IN EPA SUBMISSION PERIOD 002
STSS* INITIAL STATE• SUBMISSION DATE 006
SUUS* STATE SUBMISSION UNIT 001
NSUS NUMBER OP UNITS IN STATE SUBMISSION PERIOD .002
PIPE PIPE DESCRIPTION 025
ALLP* SEASONAL DNA PRINTING INDICATORS 012
ILSD* INITIAL LIMITS DATES: START 006
ILED* INITIAL LIMITS DATES: END 006
ML’ D* INTERIM LIMITS DATES: START 006
MLED* INTERIM LIMITS DATES: END 006
FLSD* FINAL LIMITS DATES: START 006
PLED* FINAL LIMITS DATES: END 006
WAST TYPE EFFLUENT WASTE 002
AG”LR AGENCY REVIEw R . 005
NDML NIN # OP DNA LINES 002
PIAC PIPE INACTIVE CODE 001
PIDT PIPE INACTIVE DATE 006
DRID*! REPORT DESIGNATOR 001
TRET OUTFALL TREATMENT TYPE CODES 024
P1CM DMA PORK COMMENTS 030
RDP1 USER DATA ELEMENT #1 003
RDP2 USER DATA ELEMENT #2 003
SDC-0055-034-CL-2005A 12/27/93 D-9
-------
QNCR Training Permit Compliance System (PCS
Acronym Field Name Field Lencttl
Parameter Limits Data Type
PLDS*! DISCHARGE NUMBER 003
PLRD*! REPORT DESIGNATOR 00]
PDSG! COMBINED DISCHARGE NUMBER AND DESIGNATOR 004
LIPQ! PIPE SET QUALIFIER 004
LTYP*! LIMIT TYPE
PARAMETER 00
MONITORING LOCATION 001
SEAN*! SEASON 00
STBA STANDARD BASIS CODE 00
FRAN FREQUENCY OF ANALYSIS 00
SAMP SAMPLE TYPE 00
CONP* CONTESTED PARAMETER 001
ALLS SEASONAL DMA PRINTING INDICATORS 012
LQUC* QUANTITY LIMITS: UNIT CODE 00
LQAV* QUANTITY LIMITS:AVERAGE 00E
LQMX* QUANTITY LIMITS: MAXIMUM 008
LCUC* CONCENTRATION LIMITS: UNIT CODE O0
LCMA* CONCENTRATION LIMITS: MINIMUM O0
LCAV* CONCENTRATION LIMITS: AVERAGE 008
L 2 X* CONCENTRATION LIMITS: MAXIMUM 00
PLFN* DOCKET NUMBER 01
DNA1 USER DATA ELEMENT #1 001
DMR2 USER DATA ELEMENT #2 00C
DMR3 USER DATA ELEMENT #3 00(
PLDS*! DISCHARGE NUNB R 003
PLRD*! REPORT DESIGN R 00?
LTYP*! LIMIT TYPE oo:
PRAM*! PARAMETER 00
NLOC*! MONITORING LOCATION 001
SEAS ON 00:
MODN!* MODIFICATION NUMBER 00:
ELSD MODIFICATION PERIOD: START 006
ELED MODIFICATION PERIOD: END 001
STBA STANDARD BASIS CODE 00:
COLS* CHANGE OP LIMITS STATUS 00
FRAN FREQUENCY OF ANALYSIS 005
SAMP SAMPLE TYPE 00
CONP* CONTESTED PARAMETER 00
ALLS SEASONAL DNA PRINTING INDICATORS 012
LQUC* QUANTITY LIMITS: UNIT CODE 00
LQAV* QUANTITY LIMITS:AVERAGE 00
LQAS* QUANTITY LIMITS:AVERAGE STAT BASE CODE OOZ
LQXS* QUANTITY LIMITS:MAXIMUM STAT BASE CODE 002
LQMX* QUANTITY LIMITS: MAXIMUM 00
b-lU 12/27193 SDC 0055 O34 CL 2005 .A
-------
Permit Compliance System (PCS) QNCR Training
Acronym Field Name Field Lenath
LCUC* CONCENTRATION LIMITS: UNIT CODE 002
LCNN* CONCENTRATION LIMITS: MINIMUM 008
LCMB* CONCENTRATION LIMITS: MINIMUM STAT BASE CODE 002
LCAV* CONCENTRATION LIMITS: AVERAGE 008
LCAS* CONCENTRATION LIMITS: AVERAGE STAT BASE CODE 002
LCMX* CONCENTRATION LIMITS: MAXIMUM 008
LCXS* CONCENTRATION LIMITS: MAXIMUM STAT BASE CODE 002
LCMO* CONCENTRATION LIMITS: MINIMUM OVERRIDE 001
LCAO* CONCENTRATION LIMITS: AVERAGE OVERRIDE 001
PLPN* DOCKET NUMBER 012
DMR1 USER DATA ELEMENT #1. 001.
DNR2 USER DATA ELEMENT #2 006
DNR3 USER DATA ELEMENT #3 006
SDC-0055-034-CL-2005A 12/27193 D-1 1
-------
QNCR Training Permit Compliance System (PCS
Acronym Field Name Field LencTtl
Measurement Violation Data Type
MVDT*! MONITORING PERIOD END DATE 00
VDSC*! DISCEARGE NUMBER 00
VDRD*! REPORT DESIGNATOR 002
VDSG! COMBINED DISCRARGE NUMBER AND DESIGNATOR 004
VPRM PARAMETER CODE 005
VLMO MONITORING LOCATION 00
VNOD I MEASUREMENT VIOLATION MODIFICATION NUMBER
VLIM! MEASUREMENT VIOLATION LIMIT TYPE
VSEA! MEASUREMENT VIOLATION SEASONAL NUMBER
VIPQ! PIPE SET QUALIFIER
XVIO 1 MEASUREMENT VIOLATION CODE
MQAV* MEASUREMENTS: QUANTITY: AVERAGE OW
)IQMX* MEASUREMENTS: QUANTITY: MAXIMUM OW
MCMN* MEASUREMENTS: CONCENTRATION: MINIMUM 008
MCAV* MEASUREMENTS: CONCENTRATION: AVERAGE 008
MCMX* MEASUREMENTS: CONCENTRATION: MAXIMUM OW
DNRR DMR RECEIVED DATE 006
SNCE RNC DETECTION: CODE 001
SDNE RNC DETECTION: DATE O0
SRCE RNC RESOLUTION: CODE 00
SRDE RNC RESOLUTION: DATE 006
REXC REPORTED # OF EXCURSIONS 0O
RPRQ REPORTED FREQUENCY OF ANALYSIS 00
RSAM REPORTED SAMPLE TYPE 002
RUNT REPORTED QUANTITY UNIT CODE 00
RCUN REPORTED CONCENTRATION UNIT CODE 00
NODI* NO DISCEARGE REASON CODE 0O
Acronym Field Name Field Length
Reissuance Processing
RCIN*! REISSUANCE CODE 00’
ILSD* INITIAL LIMITS START DATE: OO
ILED* INITIAL LIMITS END DATE: OCt
HLSD* INTERIM LIMITS START DATE: 00’
MLED* INTERIM LIMITS END DATE: 00
FLSD* FINAL LIMITS START DATE: 00
FLED* FINAL LIMITS END DATE: OW
D-12 12/27/93 SDC-O055-O34-CL-2005
-------
Permit Compliance System (PCS) QNCR Trnining
Acronym Field Name Field Lencrth
Single Event Violation Data Type
SVCD! VIOLATION CODE 005
BVDTI VIOLATION DATE 006
SNCS RNC DETECTION CODE 001
BNDS RNC RESOLUTION DATE 006
SRCS RNC RESOLUTION CODE 001
SRDS RNC RESOLUTION DATE 006
RDSI. REGIONAL FIELD 1 003
RDS2 REGIONAL FIELD 2 005
SDC-0055-034 -CL-2005A 12/27/93 D-13
-------
QNCR Training Permit Compliaiice System (PCS)
Acronym Field Name Field Length
Enforcement Action Data Type
ENAC*! ENFORCEMENT ACTION CODE 002
EATPI ISSUED BY O0
DATE OOG
ENST* STATUS CODE 002
ESDT* STATUS DATE 0O
ERFN* DOCKET NUMBER O1C.
ENST* ENPORCEMENT ACTION STATUS CODE
EACD CLOSURE SCHEDULE DATE 00
EIPI INITIATING PARTY 1 00
EIP2 INITIATING PARTY 2 00
ERDT RESPONSE DUE DATE 006
EADR RESPONSE ACHIEVED DATE 00
EVDK VIOLATION RECOGNITION DATE OOL
RDH1 USER DATA ELEMENT: #1 003
RbH2 USER DATA ELEMENT: #2 O0
ECMT* ENFORCEMENT ACTION COMMENT 30i
ECM I ENFORCEMENT ACTION COMMENT # 1 1st 030
ECM2 ENFORCEMENT ACTION COMMENT # 2 2nd 03
ECM3 ENFORCEMENT ACTION COMMENT # 3 3rd 03
ECM4 ENFORCEMENT ACTION COMMENT # 4 4th 03d
ECM5 ENFORCEMENT ACTION COMMENT # 5 5th 03fl
ECMG ENFORCEMENT ACTION COMMENT # 6 6th 03
ECM7 ENFORCEMENT ACTION COMMENT # 7 7th 03
ECM8 ENFORCEMENT ACTION COMMENT # 8 8th 030
ECM9 ENFORCEMENT ACTION COMMENT # 9 9th 03P
ECMO ENFORCEMENT ACTION COMMENT # 0 10th 03(
EKAC*! ENFORCEMENT ACTION CODE OO ..
EKT.P! TYPE ORDER ISSUED S O0
EXDT! ENFORCEMENT ACTION DATE 00’
VIOLATION TYPE 00:
D-14 12/27/93 SDC-0055-034-CL-2005
-------
Permit Compliance System (PCS) QNCR Tr2ining
Appendix E
PCS Training Documentation Form
-------
Permit Compliance System (PCS) QNCR Training
PCS Training Documentation Comment Form
Date: ___/ /___ Region/State:
Name:
Address:
Phone.( ) - User ID. ________
Describe your comment/request below. Please be specific. (If
you are suggesting multiple modifications, please submit each one
on a separate form. Be sure to attach any available supporting
documentation.)
12/27/93 SDC-0055-034-CL-2005A
------- |