United States Office of Wastewater
Environmental Protection Enforcement and Compliance
Agency
Permit Compliance
System (PCS)
Basic Training Manual
December 13,1993
Recycled/Recyclable
Primed on paper that contains
at least 50% recycled fiber
-------
Permit Compliance System (PCS) Basic Training
Contents
1.0 Introduction 1
1.1 Important Telephone Numbers 1
1.2 Data Entry Basics and Concepts 2
1.3 PCS Terminology and Concepts 3
1.4 WENDB Data Elements * 3
1.5 Key Data Elements ! 3
1.6 Entering Data into PCS 5
1.7 PCS Processing of Data 5
1.8 Transaction Codes 6
2.0 PCS Data Entry Screens 7
2.1 PCS-ADE Main Menu 7
2.2 Permit Facility Data 8
2.2.1 FAC1 Facility Data/Part 1 9
2.2.2 FAC2 Facility Data/Part 2 16
2.2.3 FAGD Facility Geographic Data Type 21
2.2.4 FACA Facility Address 24
2.2.5 FACO Facility Owner/Operator Address 26
2.2.6 SLPF Sludge Facility Data 28
2.3 PTRK Permit Event Data 30
2.4 Compliance Schedule Family 33
2.4.1 CSCH Compliance Schedules Screen 34
2.4.2 CVIO Compliance Violations Screen 37
2.5 Inspection Data Type 41
2.5.1 INSS Inspection Schedule Data Type 42
2.5.1.1 INSP Inspections Screen 46
2.6 Pretreatment Compliance Inspection Data Type 50
2.6.1 PCI1 Pretreatment Compliance Inspection Screen 50
2.6.2 PCI2 Pretreatment Compliance Inspection Screen 2 56
2.7 Pretreatment Audit Inspection Data Type 60
2.7.1 PAU1 Pretreatment Audit Screen 1 60
2.7.2 PAU2 Pretreatment Audit Screen 2 65
2.7.3 PAU3 Pretreatment Audit Screen 3 71
2.7.4 SLIN Sludge Inspection Data Screen 77
2.8 Pipe Schedule Data Type 80
2.8.1 OFLG Outfall Screen 81
2.8.2 OFLT Outfall Treatment Type Screen 87
2.8.3 OFGD Outfall Geographic Data Type 89
2.8.4 SLPS Sludge Outfall Data 92
SDC-0055-034-ST-3003 12/13/93 in
-------
Basic Training Permit Compliance System (PCS)
2.9 Parameter Limits Data Type 94
2.9.1 LIMS Effluent Limits Screen 1 94
2.9.2 LIMM Limit Modifications Screen_2 - 101
2.9.3 SEAN Seasonal Limits Split Screen 109
2.10 Measurement Violation Data Type 112
2.10.1 EDMR Key Screen 112
2.10.2 EDMR Screen 2 114
2.10.3 EVIO Key Screen 118
2.10.4 EVIO Effluent Measurements 122
2.11 Single Event Violation Data Type 126
2.11.1 SVIO Single Event Violations 127
2.12 Enforcement Action Data Type 129
2.12.1 ENAC Enforcement Actions Screen 130
2.12.2 EAKS Enforcement Action Key Screen 137
2.12.2.1 Entering an EK Record For a Specific Effluent Violation Without
Cycling 139
2.12.2.2 Entering an EK Record For a Specific Effluent Violation With
Cycling 141
2.12.2.3 Entering an EK Record For a Specific Compliance Schedule Violation
Without Cycling 144
2.12.2.4 Entering an EK Record For a Specific Compliance Schedule Violation
With Cycling 146
2.12.2.S Entering an EK Record For a Single Event Violation Without
Cycling 149
2.12.2.6 Entering an EK Record For a Single Event Violation With Cycling 151
2.12.3 Administrative Penalty Order 154
2.12.3.1 EAP1 Administrative Penalty Order Screen 1 154
2.12.3.2 EAP2 Administrative Penalty Order Screen 2 160
2.13 Reissuance Processing 164
2.13.1 RCIN Reissuance Data 165
2.14 Pretreatment Summary 167
2.14.1 PPS1 Pretreatment Summary Report 168
2.15 Evidentiary Hearings 173
2.15.1 EVHR Evidentiary Hearing Screen 174
2.16 Grants 176
2.16.1 GRNT Grants Screen 177
3.0 Inquiry 179
3.1 Manager's Inquiry 179
3.1.1 Creating a Set Using Set Maintenance 180
3.1.2 Creating a Set Using Primary Selection Criteria 184
3.1.3 Selecting a Manager's Inquiry Report 198
iv ' 12/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
3.1.4 Selecting an Inspections Report 198
3.2 Prompt Mode 209
3.2.1 Selecting a Prompt Mode Report 210
3.2.2 Facility Directory Report 211
3.2.3 Verifying Selection Criteria 218
3.2.4 Tally 219
3.2.S Producing a Report 221
3.3 Command Mode 222
3.3.1 Selection Statements 224
3.3.2 Logical Operators 226
3.3.3 Selection Defaults 231
3.3.4 Display Statements 231
3.3.5 Sort Statements 232
3.3.6 Tally 233
4.0 Generalized Retrievals 239
4.1 The 00 Card 239
4.2 The 01 Card 240
4.3 The 10 Card 241
4.3.1 Logical Operators 241
4.3.2 Use of PCS Acronyms to Select Facilities 248
4.3.3 The 10 WITH Card 249
4.4 The 11 OR Card 253
4.5 The 20 Card 254
4.6 The 30 Card 254
4.7 The 40 Card 256
4.8 Retrievals With Options on the 20 Card 256
4.8.1 HEADERS=LONG 256
4.8.2 EXPAND=YES and T>' Acronym 257
4.8.3 SKIP=x 259
4.8.4 SUPPRESS=YES 262
4.8.5 PAGE BREAK 263
4.8.6 TAB 265
4.8.7 Multiple Display Lines 266
4.8.8 TOP=YES 268
4.8.9 Indenting Multiple Line Reports 269
4.9 The 40 WITH Card 270
SbC-0055-034-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
Exhibits
PCS Data Facts and Structure Chart Description 4
PCS-ADE Main Menu Screen 7
Facility Menu 8
Facility Data/Part 1 Screen 9
Facility Data/Part 2 Screen 16
Facility Geographic Data Screen 21
Facility Address Screen 24
Facility Owner/Operator Address Screen 26
Sludge Facility Data Screen 28
Permit Tracking Screen 30
Compliance Schedules Screen 34
Compliance Violations Screen 37
Inspections Menu 41
Inspection Scheduling Screen 42
Inspections Screen 46
Pretreatment Compliance Inspection Screen SO
Pretreatment Compliance Inspection Screen 2 56
Pretreatment Audit Screen 1 60
Pretreatment Audit Screen 2 65
Pretreatment Audit Screen 3 71
Sludge Inspection Data Screen 77
Effluent Menu 80
Outfall Screen 81
Outfall Treatment Type Screen 87
Outfall Geographic Data Screen 89
Sludge Outfall Data Screen 92
Effluent Limits Screen 1 94
Limit Modifications Screen 2 101
Seasonal Limits Split Screen 109
Effluent DMR Data Key Screen 1 112
Effluent DMR Data Screen 2 114
Effluent Measurements Key Screen 118
Effluent Measurements-Type of Limit Screen 2 122
Single Event Violations Screen 127
Enforcement Action Menu 129
Enforcement Actions Screen 130
Enforcement Actions Sample Screen 136
Enforcement Action Key Screen 137
Enforcement Action Key Screen 139
Enforcement Action Effluent Key Screen 140
vi 12/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
Enforcement Action Key Screen 141
Enforcement Action Effluent Key Screen 143
Enforcement Action Compliance Schedule Key Screen 145
Enforcement Action Compliance Schedule Key Screen 148
Enforcement Action Single Event Violation Key Screen 150
Enforcement Action Single Event Violation Key Screen 153
Administrative Order Screen 1 154
Administrative Order Screen 2 16°
Reissuance Data Screen 165
Other Menu 167
Pretreatment Summary Screen 168
Other Menu l7^
Evidentiary Hearing Screen I74
Other Menu n6
Grants Screen I77
SbC-0033-034-ST-3003 13713733 " vn
-------
Basic Training Permit Compliance System (PCS)
Appendices
Appendix A PCS Code Tables
Appendix B City Master File
Appendix C STORET Table Examples
Appendix D Quick Reference List of Acronyms
Appendix E Error Handling/Hints Class Notes
Appendix F Training Documentation Comment Form
vm 12/13/93 SDU-UOD3-OJ4-M-JUOJ
-------
Permit Compliance System (PCS) Basic Training
1.0 Introduction
This manual is designed for those users who enter data into the Permit Compliance System
(PCS). It is designed to be used along with classroom instruction.
The Basic Training Manual contains:
PCS data entry screens
Acronym descriptions for each screen
Inquiry
Generalized retrieval
1.1 Important Telephone Numbers
There are two important telephone numbers for those who work with EPA's Permit
Compliance System (PCS).
PCS User Support Hot-Line
Questions concerning the database can be answered by calling the PCS User Support Hotline
at: (703)908-2680
If all user support staff members are unavailable, there is voice mail available to leave a
message. Your message, request or question will be responded to as quickly as possible in
the order that it was received. Please be sure your message includes:
Name
Location
Telephone number
A complete explanation of your question or problem
The PCS User support staff can also be the first point of contact if you are unsure of
something concerning PCS.
National Computer Center (NCC) IBM User Support
The second telephone number of importance is NCC User Support in Research Triangle
Park, North Carolina. Questions concerning the IBM mainframe computer should be
directed to them at: (800) 334-2405 or (919) 541-7862.
SDC-0055-034-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
1.2 Data Entry Basics and Concepts
Terms and Examples:
BYTE One character of data.
Alphanumeric or special characters.
Example: The letter A is one (1) BYTE of data.
FIELD A series of related bytes.
Example: A NAME field consisting of a person's name.
NAME: John Doe
RECORD A series of related fields.
Example: A Personnel RECORD with six (6) fields.
NAME: John Doe
ADDRESS: 121 John Doe's Lane
CITY: Doeville
STATE: DOE
ZIP: 23456-7890
SS#: 123-45-6789
FILE A series of related records.
Example: All personnel records for a company make up the Personnel FILE.
DATABASE A series of related files.
Example: The personnel file, payroll file, withholdings file, and accounts
payable and receivable could make up a company's DATABASE.
T27I3753 SbC-Ou55-oi4-s r-3003
-------
Permit Compliance System (PCS) Basic Training
1.3 PCS Terminology and Concepts
A FIELD is called a DATA ELEMENT.
A RECORD is called a DATA TYPE.
- A FAMILY is made up of related DATA TYPES.
- ACRONYMS are 4 character abbreviations for data element names.
Example: The field containing the name of the facility is called FACILITY NAME
LONG. The PCS acronym for this data element is FNML.
1.4 WENDB Data Elements *
EPA Headquarters, in Washington, D.C., requires certain data elements for tracking
purposes, for example, counts of:
Permits issued to major and minor facilities
Permits issued to municipals and industrials
Major permits with limits and the kinds of limits
This tracking process is called the Water Enforcement National Data Base (WENDB).
In this documentation WENDB data elements are indicated by an asterisk (*) after the field
name.
1.5 Key Data Elements !
The Permit Compliance System requires specific data in order to be able to identify and
process records. These required fields are called Key data elements. The Key data element
is an address to the record. It tells the PCS system where to find a record. The system will
not process data entered unless all Key data elements are entered.
The Key data elements are most easily identified and visible because they are those fields
above the dotted line on the data entry screens.
In this documentation Key data elements are indicated by an exclamation point (!) after the
element name.
St>C-00#-034-ST-300312/13/93
-------
Basic Training
Permit Compliance System (PCS)
PCS Data Facts and Structure Chart Description
[l
^^
n
n
sen
PARA
MEASL
V
PPE
EDULE
METER
LMITS
DATA
REUENT
OLATKM
DATA
1
COUP
so>
on*
so
vc
LIANCE
EDULE
DATA
IIANCE
KEDULE
LA TON
DATA
ENFOR
ENFOK
PERMIT FACILITY DATA
}
"""suUSJ , "SoSS "EVENT *""*!»? '"SSI
DATA ' DATA DATA DATA »IA
1 1
1 NOT REQUIRED TO ENTER
SEE 1SPECTON
"oTr. n*I»
IOEUENT S110LE PCWUOir
KEY VIOLATION DATA
DATA DATA
1
THE EFFLUENT RECORDS TYPES EXBT ON EACH OF THE 10 PHVSEAL REODNAL FLES
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 ars called families of data. The
largest is the effluent family of data. It consists of the pipe schedule, parameters limits and
measurement/violation data types. (Connected by solid vertical lines on the chart.)
On the bottom of the chart, the data types are connected by dotted lines. The dotted lines signify
that the enforcement action key data type can be linked to measurement, compliance schedule and
single event violations.
12/13/93
-3UUJ
-------
Permit Compliance System (PCS) Basic Training
1.6 Entering Data into PCS
Batch Cards (Resembles an 80 column punch card transmitted to the IBM mainframe in
North Carolina.)
PCS-ADE-Permit Compliance System (ADABAS Data Entry)
1.7 PCS Processing of Data
After data is entered, through either method, the data is processed by the IBM mainframe.
The following steps occur:
PCS edits the data.
PCS checks the data to ensure it can be added to the database.
If data entry is through the batch card method, an edit report of data and errors is sent to
the user. If PCS-ADE is the method used to enter data, editing occurs during data entry.
Error messages are displayed at the top of the screen, no report is generated.
Data goes into a "HOLD" file until system updates are run (Monday and Thursday
nights) when the data is added to the database.
PCS data is processed by the IBM mainframe in the following order:
- X Mass Delete
- D Delete
- N New
- C Change
- R Replace
The system sends an update report listing the data added to the database and the data
rejected.
Records can be any length (not limited to 80 characters).
Data must be 80 characters or less due to the 80 column keypunch limitation.
It takes more than 1 card to add 1 record to PCS.
SDC-0055-034-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
1.8 Transaction Codes
When the record is found, the transaction or function to be performed on the record must be
identified to the PCS system.
N NEW The transaction code used to add the record to the system.
C CHANGE The transaction code used to edit existing data.
D DELETE The transaction code used to delete or remove a record from the
system.
X MASS DELETE The transaction code used to delete a record and all lower level data
' types associated with the record.
- CAUTION!!! Use the "X" transaction code with care!
NOTE: DO NOT USE THE "X" TRANSACTION CODE TO INACTIVATE
A FACILITY. The entire facility and all related information will be
removed permanently from the database.
R REPLACE The transaction code used to delete the record and add only the new
data elements entered.
- CAUTION!!! Use the "R" transaction code with care.
NOTE: Always enter all data elements for a record when using this transaction
code. The system does not allow the use of this code for facility data.
This code works best for measurement or permit event data.
12/13/93 SDL.-UU55-U34-& 1 -6VU6
-------
Permit Compliance System (PCS) Basic Training
2.0 PCS Data Entry Screens
2.1 PCS-ADE Main Menu
The PCS-ADE Main Menu is used to access the individual screens required for data entry
into the Permit Compliance System. To access a particular screen, the four letter screen
name abbreviation is entered. The system returns to this screen after a session with a
selected screen has ended.
PCS-ADE Main Menu Screen
11/23/92 PCS-ADE Data Entry Subsystem PCOENENU
11:13:45 Main Menu
Enter screen 10 or 'X' to select 8 submenu
Screen ID:
_ Facility
_ Effluent
~ Enforcement Action
_ Inspections
~ Compliance Schedule
~ Tables
~ Other
~ Quit
(PF1,13=Help; PF3,15=Main Menu; PK,16=Ouit; PF8=Bottom> Version 1.0
St>C-Ofctf-034-ST-3M3 12/13/03
-------
Basic Training Permit Compliance System (PCS)
2.2 Permit Facility Data
The majority of the data to be entered on the Facility record comes from the application for a
permit. The Facility Menu is used to access Facility related screens.
Facility Menu
11/14/92 PCS-ADE Data Entry Subsystem PCDEMENU
11:00:58 Facility Menu
Enter screen ID or 'X' to select an option
Screen ID:
FAC1
FAC2
FACA
FACO
FAGD
PTRK
RCIN
SLPF
EXIT
Facility Data screen 1
Facility Data screen 2
Facility Address screen 1
Facility Address screen 2
Facility Geographic Data
Permit Tracking
Reissuance screen
Sludge Facility screen
Return to Main menu
CPF1.13=Help; PF3,15=Main Menu; PF4,16=Quit; PF8=Bottom)
-------
Permit Compliance System (PCS) Basic Training
The following PCS-ADE screens are used to enter facility information into the PCS database.
2.2.1 FAC1 FacUity Data/Part 1
Facility Data/Part 1 Screen
15:35:09 FACILITY/PART 1 PCOEFAC1
11/20/92 SCREEN ID: FAC1
PERMIT 0
-------
Basic Training Permit Compliance System (PCS)
FNML* [FACILITY NAME LONG] (4 fields of 30 characters each)
This field is a WENDB data element. Only the first thirty (30) characters of the Facility
Name field are usually used.
NOTE: The first 30 characters of the FACILITY NAME field are called FNMS. This
acronym is used most often for Inquiry and Retrieval purposes.
OFFL [COGNIZANT OFFICIAL] (field length=30 characters)
This field contains the name of the person whose signature appears on the application.
He/She must be an executive officer of the facility.
TELE [TELEPHONE] (field length = 10 characters)
This is the telephone number of the cognizant official entered in the OFFL field.
CITY* [CITY CODE] (field length = 5 characters)
This is a WENDB data element. This code comes from the City Master Listing. A
complete City Master Listing can be printed using the dataset 'JXLA040.CITYMAST.JCL'
in ISPF. Appendix D of this document contains an excerpt of this list.
CNTY* [COUNTY CODE] (field length = 3 characters)
This is a WENDB data element. It is generated when CITY code is entered. It is not
necessary to enter this field when a transaction code of 'N' is used. The COUNTY CODE
is found on the City Master Listing with the CITY CODE.
SIC2* [SIC CODE] (field length = 4 characters)
This is a WENDB data element. It stands for Standard Industrial Classification. (The code
assigned represents what the business is, not what the business does.) A listing of SIC codes
can be found in TABLE 140 in the PCS Codes and Descriptions Manual.
Examples:
2819 Petroleum Refining
4952 Sewerage Systems
4911 Power Generation
10 12/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
CFRC [CODE OF FEDERAL REGULATIONS] (field length = 3 characters)
This field is automatically generated by the SIC2 field, but can be edited or changed. This
field describes the federal regulation associated with this permit. A listing of Federal
Regulations Codes can be found in TABLE 070 in the PCS Codes and Descriptions Manual.
TYPA [TYPE OF APPLICATION] (field length = 2 characters)
This field indicates the form used to apply for a permit. A listing of application types can be
found in TABLE 410 in the PCS Codes and Descriptions Manual.
Examples:
2A Long-form 'c'
2D Short-form 'c'
TYPO* [FACILITY OWNERSHIP] (field length = 3 characters)
This is a WENDB data element. Valid codes include:
PUB Public
PRI Private
FED Federal
STA State
BPP Both Public and Private
GRID [ORIGINAL PERMIT ISSUANCE DATE] (field length = 6 characters)
This field contains the date that the original permit was issued.
EPST* [ISSUED BY] (field length = 1 character)
This field is a WENDB data element. Valid options include:
E EPA
S State
SDC-0055-034-ST-3003 12/13/93 11
-------
Basic Training Permit Compliance System (PCS)
REIS [REISSUANCE #] (field length = 1 character)
This field indicates the number of times that a permit has been reissued. The first time a
permit is issued this number is 0. The first time the permit is reissued it is 1, and so on.
PRET* (field length = 1 character)
[PRETREATMENT PROGRAM REQUIRED INDICATOR]
This field is a WENDB data element. Valid options include:
C Covered under another program
R Program required, not approved
Y Program approved
blank Program not required
FDGR* [FEDERAL GRANT INDICATOR] (field length = 1 character)
This is a WENDB data element. If this facility is a PL 92-500 grantee, a '$' is entered in
this field.
NEWS [NEW SOURCE/DISCHARGE CODE] (field length = 2 characters)
This field indicates this facility can begin construction after promulgation of the New Source
Performance Standards, as defined in 40 CFR. The listing of valid New Source/Discharge
Codes can be found in TABLE 400 in the PCS Codes and Descriptions Manual.
NSDT [NEW SOURCE/DISCHARGE DATE] (field length = 6 characters)
This is the date that the new code for new source or discharge was permitted.
FLIM* [FINAL LIMITS INDICATOR] (field length = 1 character)
This field is a WENDB data element. It indicates that the facility is capable of achieving
final limits. Valid options include:
F Indicates that the facility is on Final Limits.
blank Indicates the facility is not on Final Limits.
15713793 SDC-005$-634-i»T-iJoO:i
-------
Permit Compliance System (PCS) Basic Training
WQUA [WATER QUALITY LIMITS] (field length = 1 character)
This field indicates that the permit contains water quality-based limits. Valid options
include:
Y Permit contains water quality-based limits
blank Permit does not contain water quality-based limits.
IACC* [FACILITY INACTIVE CODE] (field length = 1 character)
This is a WENDB data element. This field indicates that this facility is:
A Active
I Inactive
IADT* [FACILITY INACTIVE DATE] (field length = 6 characters)
This field is a WENDB data element. It must be entered when the value entered for the
IACC field is T. This field contains the date the facility became inactive.
CSDN [CONSOLIDATED PERMIT #] (field length = 12 characters)
This field indicates the first twelve characters of the CONSOLIDATED SYSTEM
FACILITY IDENTIFIER (CSID).
NEED [NEEDS SUFFIX] (field length = 3 characters)
This field indicates the last three characters of the CONSOLIDATED SYSTEM FACILITY
IDENTIFIER (CSID).
STNO [STATE PERMIT #] (field length = 8 characters)
If one exists, this field indicates the permit number of the state-issued permit.
FFID [FEDERAL PERMIT #] (field length=12 characters)
This number is a unique identifier for each federally-owned facility. It consists of: the state
code, in positions 1 and 2, a dash ' - ' in position 3, the Agency or Bureau number in
positions 4 through 7 and the GSA number in positions 8 through 12.
SDC-00&-034-ST-3003 12713753 T3
-------
Basic Training Permit Compliance System (PCS)
CAID [CONTROL AUTHORITY PERMIT #] (field length = 9 characters)
This field indicates the permit number of the facility that is the Control Authority of the
pretreatment program. Refer to the chapter on "Coding Considerations" in the PCS Data
Entry, Edit, and Update Manual for instructions on properly coding this field.
RPID [RECEIVING POTW PERMIT #] (field length = 9 characters)
This field indicates the permit number of the facility receiving the discharge for the
pretreatment program. Refer to the chapter on "Coding Considerations" in the PCS Data
Entry, Edit, and Update Manual for instructions on properly coding this field.
RPRI [REGIONAL PRIORITY PERMIT] (field length = 1 character)
This field is a management tool used by the region to assign priorities to facilities for permit
issuance.
SUBR [SUB-REGION CODE] (field length = 2 characters)
This field can be used by states to enter the sub-region codes applicable to their states.
ATNY [ATTORNEY INITIALS] (field length = 3 characters)
Enter the initials of the attorney associated with this facility.
ENGI [ENGINEER INITIALS] (field length = 3 characters)
Enter the initials for the engineer associated with this facility.
FLOW* [AVERAGE DESIGN FLOW] (field length = 5 characters)
This is a WENDB data element used for municipal facilities. The amount of flow the facility
was designed to handle is entered in this field in millions of gallons per day (MOD).
[ACCEPT? Y/N/M] (field length = 1 character)
The valid responses to this field are:
Y (Yes) to accept the data entered and continue.
N (No) does not accept the data entered. It refreshes the screen.
M (Main Menu) does not accept the data entered. Returns the system to the Main
Menu.
14 12/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
[FAC2 DATA? Y/N] (field length = 1 character)
Indicate:
Y (Yes) to continue to the FAC2 screen
N (No) will not continue to the FAC2 screen.
[SLUDGE DATA? Y/N] (field length = 1 character)
Indicate:
Y (Yes) to continue to the SLPF screen.
N (No) will not continue to the SLPF screen.
SDC-0055-034-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
2.2.2 FAC2 Facility Data/Part 2
Facility Data/Part 2 Screen
15:39:49 FACILITY/PART 2 PCOEFAC2
11/20/92 SCREEN ID: FAC2
PERMIT # (MPIO) TRAMS CODE C
FACILITY
NAME
ARCHIVAL INDICATOR _ RIVER BASIN #
(ARCH) (BAS6)
RECEIVING MATERS CRWIT)
.... EVIDENTIARY HEARING - - - -
HEARING INDICATOR FILE f ISSUE CODES
(EHIN) (EHFN) (EHS1XEHS2XEHS3)
DOCKET *
(EHDK)
~ - USER DATA ELEMENTS
RDF1 RDF2 RDF3 RDF4 RDF5 RDF6 RDF7 RDF8
RDF9 ~ RDF10 ~
- - - - HUP ELEMENTS - - - -
NPSC-NNP STAT _ NPFF-NMP FIT _ NPSQ-NMP OTR _
PREVIOUS YEAR MANUAL ONCR STATUS 1234 (PYMS)
CURRENT YEAR MANUAL QNCR STATUS 1 _ 2 _ 3 _ 4 _ (CYMS)
ACCEPT? Y/N/M: Y SLUDGE DATA? Y/N: N VERSION 2.2 12/10/91
*Note: On-line screen does not contain acronyms.
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, the PERMIT NUMBER and TRANS CODE must be entered on this screen.
ARCH [ARCHIVAL INDICATOR] (field length = 1 character)
Measurement records that are more than two years old are archived every year. An entry of
'N' in this field indicates that the measurement records for this permit number should not be
archived. Valid options include:
N Measurements will not be archived
blank Measurements will be archived
15 15713793 SDC-OO^-034-il-iOOi
-------
Permit Compliance System (PCS) Basic Training
BAS6 [RIVER BASIN CODE] (field length = 6 characters)
Enter the associated river basin code for this facility. A listing of River Basin Codes can be
found on the City Master Listing with the city and county codes.
RWAT [RECEIVING WATERS] (field length=35 characters)
The name of the body of surface waters which receive the discharge are indicated in this
field.
EHIN [HEARING INDICATOR] (field length = 1 character)
This field indicates that the permit has an active evidentiary hearing. This field defaults to
T for Inactive. To indicate that the permit has an evidentiary hearing, enter 'A' for Active.
EHFN [FTLE#] (field length =12 characters)
This field indicates the EPA file number associated with the evidentiary hearing.
EHS1/EHS2/EHS3 [ISSUE CODES] (3 fields of 3 characters each)
These fields indicate the reason(s) why the permittee requested an evidentiary hearing. The
complete listing of evidentiary hearing codes can be found in TABLE 500 in the PCS Codes
and Descriptions Manual.
EHDK [DOCKET #] (field length = 12 characters)
This field indicates the legal case DOCKET NUMBER of the evidentiary hearing.
RDF1/RDF2/RDF3 (3 fields of 1 character each)
These fields are for optional user data elements. Their contents and use are dictated by the
region or state.
RDF4/RDF5/RDF6 (3 fields of 3 characters each)
These fields are for optional user data elements. Their contents and use are dictated by the
region or state.
SDC-00&-034-ST-30M12/13/93
-------
Basic Training Permit Compliance System (PCS)
RDF7/RDF8/RDF9 (3 fields of 6 characters each)
These fields are for optional user data elements. Their contents and use are dictated by the
region or state.
RDF10 (2 fields of 50 characters each)
This field is also for optional user data elements. Its contents and usage is dictated by the
region or state.
NPSC* [NPSC-NMP STAT] (field length = 1 character)
This field is a WENDB data element. It is used solely for permits that are regulated under
the National Municipal Policy (NMP). It indicates that a final and enforceable Municipal
Compliance Plan (MCP) schedule has been established to meet all statutory requirements in
accordance with the NMP. A complete listing of codes can be found in TABLE 510 in the
PCS Codes and Descriptions Manual.
NPFF* [NPFF-NMP FIT] (field length = 1 character)
This field is a WENDB data element. It is used solely for permits that are regulated under
the National Municipal Policy (NMP). It indicates the final fitness of the POTW to comply
with the Municipal Compliance Plan (MCP) schedule and to meet the statutory requirements
with the NMP. A complete listing of the codes can be found in TABLE 520 of the PCS
Codes and Descriptions Manual.
NPSQ* [NPSQ-NMP QTR] (field length = 1 character)
This field is a WENDB data element. It is used solely for permits that are regulated under
the National Municipal Policy (NMP). It indicates the fiscal quarter during which the final
enforceable Municipal Compliance Plan (MCP) schedule is anticipated to be or was
established. A complete listing of the codes can be found in TABLE 530 in the PCS Codes
and Descriptions Manual.
12713793
-------
Permit Compliance System (PCS) Basic Training
PYMS (field length = 4 characters)
[PREVIOUS YEAR MANUAL QNCR STATUS]
These four Melds can be manually entered to indicate the compliance status of the facilities
that appeared on the QNCR during the previous fiscal year which began October 1 and ended
on September 30. The four fields can be retrieved with the acronym PYMS or they can be
retrieved separately with the acronyms below:
1 (PYM1) 1st Quarter of the previous fiscal year
(Oct through December)
2 (PYM2) 2nd Quarter of the previous fiscal year
(January through March)
3 (PYM3) 3rd Quarter of the previous fiscal year
(April through June)
4 (PYM4) 4th Quarter of the previous fiscal year
(July through September)
The complete listing of codes for these fields can be found in TABLE 440 in the PCS Codes
and Descriptions Manual.
CYMS* (field length = 1 character)
[CURRENT YEAR MANUAL QNCR STATUS]
These fields are WENDB data elements. They can be manually entered to indicate the
compliance status of the facilities that are appearing on the QNCR during the current fiscal
year that began October 1 and will end September 30. The CURRENT YEAR QNCR
STATUS codes are automatically moved to the PREVIOUS YEAR MANUAL QNCR
STATUS codes every January. The four fields can be retrieved separately with the
acronyms below:
1 (CYM1) 1st Quarter of the current fiscal year
(October through December)
2 (CYM2) 2nd Quarter of the current fiscal year
(January through March)
3 (CYM3) 3rd Quarter of the current fiscal year
(April through June)
4 (CYM4) 4th Quarter of the current fiscal year
(July through September)
The complete listing of codes for these fields can be found in TABLE 440 in the PCS Codes
and Descriptions Manual.
$DC-M5$-034-$T-3003 12713753
-------
Basic Training Permit Compliance System (PCS)
ACCEPT? Y/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered. Returns to the FAC1 screen or a refreshed FAC2
screen.
N (No) does not accept the data entered. Displays a refreshed FAC2 screen.
M (Main Menu) does not accept data entered. Returns the system to the Main Menu.
[SLUDGE DATA? Y/N] (field length = 1 character)
Indicate:
Y (Yes) to continue to the SLPF screen.
N (No) will not continue to the SLPF screen.
25 13713793
-------
Permit Compliance System (PCS) Basic Training
2.2.3 FAGD Facility Geographic Data Type
This screen is used to enter Facility Geographic Data information. The TRANS CODE is a
'C' that is hard-coded and cannot be changed.
Facility Geographic Data Screen
13:20:00.6 Permit Facility Geographic Data PGDPFAGO
08/30/93 Screen 10: FAGD
Permit * Trans Code C
Latitude (FLAT) Longitude (FLOM)
LAT/LONG Code of Accuracy (FLLC) _
LAT/LONG Method (FLLM) LAT/LOMG Datum CFLLT) _
LAT/LOMG Scale CFLLS) LAT/LOHG Description (FLLD)
Reach Number:
USGS Hydrologic Basin Code (FHBC) Stream Segment (FSEG)
Mileage Indicator (FMLG)
Receiving Stream Classification Code CFRSC)
ACCEPT? Y/M/M: Y VERSIOM 1.0 12/11/93
FLAT* [LATITUDE] (field length = 8 characters)
This field is a WENDB data element. The global latitude where this discharge is located is
entered in this field. It must be entered in the fixed format:
Character 1 + Northern Hemisphere
- Southern Hemisphere
Characters 2 and 3 Degrees
Characters 4 and 5 Minutes
Characters 6 and 7 Seconds
Character 8 Tenths of a Second
-------
Basic Training Permit Compliance System (PCS)
FLON* [LONGITUDE] (field length = 9 characters)
This field is a WENDB data element. The global longitude where this discharge is located is
entered in this field. It must be entered in the fixed format:
Character 1 + Eastern Hemisphere
- Western Hemisphere
Characters 2, 3 and 4 Degrees
Characters 5 and 6 Minutes
Characters 7 and 8 Seconds
Character 9 Tenths of a Second
FLLC* [LAT/LONG CODE OF ACCURACY] (field length = 1 character)
This field is a WENDB data element. It indicates the level of accuracy of the LATITUDE
and LONGITUDE fields. LATITUDE and LONGITUDE must be entered before data can
be entered into this field. This field must match the tenths of a second in the LATITUDE
and LONGITUDE fields. The codes for this field are contained in TABLE 470 in the PCS
Codes and Descriptions Manual.
FLLM* [LAT/LONG METHOD] (field length = 1 character)
This field is a WENDB data element. It indicates the method used to measure LATITUDE
and LONGITUDE coordinates. LATITUDE and LONGITUDE must be entered before data
can be entered into this field. The codes for this field are contained in TABLE 471 in the
PCS Codes and Descriptions Manual.
FLLT* [LAT/LONG DATUM] (field length = 1 character)
This field is a WENDB data element. It represents a network of reference points from
which geographic computations can be made. LATITUDE and LONGITUDE must be
entered before data can be entered into this field. The codes for this field are contained in
TABLE 472 in the PCS Codes and Descriptions Manual.
FLLS* [LAT/LONG SCALE] (field length = 1 character)
This field is a WENDB data element. It represents the scale of source map used to
determine LATITUDE and LONGITUDE. LATITUDE and LONGITUDE must be entered
before data can be entered into this field. The codes for this table are contained in TABLE
473 in the PCS Codes and Descriptions Manual.
22 I27T3753 SDC-M5$-Oi4-JiT-:40o:J
-------
Permit Compliance System (PCS) Basic Training
FLLD* [LAT/LONG DESCRIPTION] (field length = 5 characters)
This field is a WENDB data element. It represents precisely to what the LATITUDE and
LONGITUDE refer. LATITUDE and LONGITUDE must be entered before data can be
entered into this field. The codes for this table are contained in TABLE 474 in the PCS
Codes and Descriptions Manual.
FBBC* [USGS HYDROLOGIC BASIN CODE] (field length = 8 characters)
This field is a WENDB data element. It represents a code assigned by the United States
Geological Survey to identify drainage water basins for facilities by their geographical
location. It is also referred to as Cataloging Unit and as HUC by frequent users of Reach
information. The codes for this field are contained in TABLE 800 in the PCS Codes and
Descriptions Manual.
FSEG [SCHEDULE STREAM SEGMENT] (field length = 4 characters)
This field represents a code used to identify pieces of water from one significant event to
another, where significant event represents the mouth of a body of water, the confluence of
two streams, etc. The codes for this field are contained in TABLE 804 in the PCS Codes
and Descriptions Manual.
FMLG [MILEAGE INDICATOR] (field length = 5 characters)
This field represents the length of a particular facility stream segment in miles downstream
from the beginning of the stream segment. The decimal can be entered in any position as
long as the number is in the form 99.999. The codes for this field are contained in TABLE
804 in the PCS Codes and Descriptions Manual.
FRSC [RECEIVING STREAM CLASSIFICATION CODE] (field length = 2 characters)
This field describes the related facility segment type. The codes for this field are contained
in TABLE 805 in the PCS Codes and Descriptions Manual.
SDC-M55-034-ST-3003 12713753 25
-------
Basic Training Permit Compliance System (PCS)
2.2.4 FACA FacUity Address
Facility Address Screen
08t16:30 FACILITY ADDRESS PCOEFACA
01/04/90 SCREEN ID: FACA
PERMIT # TRANS CODE C
- - - - PRIMARY DMR MAILING ADDRESS
FACILITY NAME CMNAM)
ADDRESS LINET (MSTt)
ADDRESS LINE2 (NST2)
CITY (MCTY> STATE CMSTT) ZIP
-------
Permit Compliance System (PCS) Basic Training
An ALTERNATE DMR MAILING ADDRESS is entered if the DMRs are to be mailed to
an address that is different from the primary mailing address. This address will print on the
DMR mailing label instead of the primary DMR mailing address.
ANAM [FACILITY NAME] (field length=30 characters)
This field contains the name of the alternate facility address for DMRs.
AST1 [ADDRESS LINE1] (field length=30 characters)
AST2 [ADDRESS LINE2] (field length=30 characters)
ACTY [CITY] (field length =23 characters)
ASTT [STATE] (field length = 2 characters)
AZEP [ZIP] (field length = 9 characters)
RNAM [FACILITY NAME] (field length=30 characters)
This field contains the facility location name.
RST1 [ADDRESS LINE1] (field length=30 characters)
RST2 [ADDRESS LINE2] (field length=30 characters)
RCTY [CITY] (field length=23 characters)
RSTT [STATE] (field length = 2 characters)
RZBP [ZIP] (field length = 9 characters)
RTEL [TELEPHONE] (field length = 10 characters)
This field contains the telephone number associated with this facility location.
ACCEPT? Y/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) to accept the data entered and display a refreshed screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and returns the system to the Main
Menu.
12713793 25
-------
Basic Training
Permit Compliance System (PCS)
2.2.5 FACO Facility Owner/Operator Address
Facility Owner/Operator Address Screen
08:44:13
1/14/90
PERMIT *
OWNER/OPERATOR ADDRESS
TRAMS CODE C
- - - - FACILITY OWNER ADDRESS - - - -
PCDEFACO
SCREEN ID: FACO
FACILITY KANE (OMAN)
ADDRESS LINC1 (OST1)
ADDRESS L1NE2 COST2)
CITY (OCTY)
TELE:
STATE
-------
Permit Compliance System (PCS) Basic Training
EST1 [ADDRESS LJNE1] (field length=30 characters)
EST2 [ADDRESS UNE2] (field length=30 characters)
ECTY [CITY] (field length =23 characters)
ESTT [STATE] (field length = 2 characters)
EZIP [ZIP] (field length = 9 characters)
SNAM [HANDLER NAME] (field length=30 characters)
This field contains the name of the sludge handler.
SST1 [ADDRESS LDVE1] (field length =30 characters)
SST2 [ADDRESS LDVE2] (field length=30 characters)
SCTY [CITY] (field length=23 characters)
SSTT [STATE] (field length = 2 characters)
SZIP [ZIP] (field length = 9 characters)
ACCEPT? Y/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) to accept the data entered and display a refreshed screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and returns the system to the Main
Menu.
SDC-00&-034-ST-3003 12713753 " 27
-------
Basic Training Permit Compliance System (PCS)
2.2.6 SLPF Sludge Facility Data
Sludge Facility Data Screen
11:00:59 SLUDGE FACILITY DATA PCDESLPF
04/08/92 SCREEN IDS SLPF
PERMIT 0 CUPID) TRAMS CODE: C
FACILITY
NAME
SLUDGE FACILITY INDICATOR (SLIM) _
SLUDGE CLASS FACILITY INDICATOR (SLCI) _
SLUDGE RELATED PERMIT # (SLID)
ANNUAL DRY SLUDGE PRODUCTION CSLPV) (DHT/YR)
USER-DEFINED SLUDGE RELATED DATA ELEMENT 1 (SLP1)
USER-DEFINED SLUDGE RELATED DATA ELEMENT 2 (SLPZ)
ACCEPT? Y/K/N/H: _ VERSION 1.0 07/18/91
The PERMIT NUMBER, TRANS CODE and FACILITY NAME fields are carried over
from the previous screen, if *Y' was the response to the MORE SLUDGE DATA? prompt.
Otherwise, the PERMIT NUMBER must be entered on this screen. The TRANS CODE is a
'C" and cannot be changed.
SLIN [SLUDGE FACILITY INDICATOR] (field length = 1 character)
This field represents the identifier for the type of sludge facility. Valid options include:
S Non-NPDES sludge permit only
O Sludge only NPDES permit
B NPDES permit with sludge pipe
blank Contains no sludge pipes
These can be found in TABLE 790 of the PCS Codes and Descriptions Manual.
25 I27B793
-------
Permit Compliance System (PCS) Basic Training
SLCI (field length = 1 character)
[SLUDGE CLASS FACILITY INDICATOR]
This field indicates the classification assigned to any pretreatment POTW or facility known
or expected to have sludge problems (primarily incinerators).
SLID [SLUDGE RELATED PERMIT #] (field length = 9 characters)
The associated sludge/NPDES permit number for those facilities with different permits for
their sludge and effluent discharges.
SLPV (field length = 7 characters)
[ANNUAL DRY SLUDGE PRODUCTION]
This field represents the amount of sludge a facility produces in Dry Metric Tons DMT/year
on a dry weight basis.
SLP1 (field length = 2 characters)
[USER-DEFINED SLUDGE RELATED DATA ELEMENT 1]
This is a user-defined field. Consult with the Regional PCS Coordinator before using this
field.
SLP2 (field length = 6 characters)
[USER-DEFINED SLUDGE RELATED DATA ELEMENT 1]
This is a user-defined field. Consult with the Regional PCS Coordinator before using this
field.
SDC-00&-034-ST-3003 1270753 25
-------
Basic Training Permit Compliance System (PCS)
2.3 PTRK Permit Event Data
Permit tracking events are dates that events occur in the NPDES permit issuing process. The
following PCS-ADE screen is used to enter this information into the PCS database.
Permit Tracking Screen
11:37:03 PERMIT TRACXXBS PCDEPTRK
11/33/92 3CREBN ID: PIKK
HERMIT t (HPIO> TRMia OODff _
PBRMXT rSWXOXS BVBHT CODS (PTBV)
PERMIT TRACKIB9 BVBHT SCHBDOLSD DATE (FTSC)
PSKMXT TJtACKXNO EVERT ACTOAL DATE (PTAC) __
PBKMIT TRAOCX8S EVBRT OOMHHtTT (PICO) _^_^__
08BR DATA BLBMBRT f 1 OSBR DATA BLBNBHT «2
*Note: On-line screen does not contain acronyms.
Permit Event Data Type (PE) - Screen/Acronym/Field Descriptions
NPID*! [PERMIT #J (field length = 9 characters)
This field is both a WENDB data element and a Key data element.
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
30 ^2/13793 SDC-0055-034-ST-3U03
-------
Permit Compliance System (PCS) Basic Training
PTEV*! [PERMIT TRACKING EVENT CODE] (field length = 5 characters)
This field is a Key data element. It is WENDB data element for specific event codes. The
following are the WENDB Permit Tracking event codes:
(PI099) Application Received
(P2099) Application Complete
(P3099) Public Notice
(P4099) Permit Issuance
(P5099) Permit Expiration
(30099) Permit Modification
Another useful event code is P6099, which is the Permit Effective event code. It is not a
WENDB data element event code.
For Inquiry and Retrieval purposes, there are five acronyms that can be used to retrieve these
events. They are:
APRD Application Received
PNOT Public Notice
PERD Permit Issuance
PERE Permit Expiration
PERF Permit Effective
A complete listing of the Permit Tracking Event Codes can be found in TABLE 110 in the
PCS Codes and Descriptions Manual.
PTSC (field length = 6 characters)
[PERMIT TRACKING EVENT SCHEDULED DATE] (MMDDYY)
This field indicates when an event is scheduled to be completed. It is used for state and
regional purposes only. When EPA headquarters pulls reports for permit tracking events,
they will only be looking at the PERMIT TRACKING EVENT ACTUAL DATE.
PTAC* (field length = 6 characters)
[PERMIT TRACKING EVENT ACTUAL DATE] (MMDDYY)
This field is a WENDB data element for the PERMIT TRACKING EVENT CODES that are
WENDB data elements. It indicates the actual date that the event took place.
SDC-0055H)34-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
PTCO (field length=30 characters)
[PERMIT TRACKING EVENT COMMENT]
This field is available for any comments to be made about the permit tracking event.
RDE1 [USER DATA ELEMENT #1J (field length = 3 characters)
RDE2 [USER DATA ELEMENT #2] (field length = 3 characters)
These Melds are used for regionally or state defined purposes. Check with the Regional PCS
Coordinator on the use of these fields.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
32 12/13/95
-------
Permit Compliance System (PCS) Rasic Training
2.4 Compliance Schedule Family
Compliance schedules are contained in the final permit and/or an enforcement action. They
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 their permit. This
is called a construction schedule and each event is represented as a separate compliance
schedule record in PCS. The Compliance Schedule Menu is used to reach the Compliance
Schedules and Compliance Schedules Violations screens.
Compliance Schedule Menu
11/14/92 PCS-ADE Data Entry Subsystem PCDEHEHU
11:00:58 Compliance Schedule Menu
Enter screen ID or 'X' to select an option
Screen ID:
CSCH - Compliance Schedules
"_ CVIO Compliance Schedule Violations
EXIT - Return to Nain menu
-------
Basic Training
Permit Compliance System (PCS)
2.4.1 CSCH Compliance Schedules Screen
The following PCS-ADE screen is used to enter the compliance schedule event records.
Compliance Schedules Screen
15:11:03
01/14/93
PERMIT t (NPID)
COMPLIANCE SCHEDULES
TRANS CODE
(CSCH)
COMPLIANCE SCHEDULE
DATA SOURCE COW (D8CD)
COMPLIANCE SCHEDULE EVENT CODE (EVHT)
CGMFLZANCB SCHEDULE EVERT SCHEDULED DATE (DT8C)
COMPLIANCE SCHBDDLE EVENT ACTUAL DATE (OTAC)
COMPLIANCE REPORT RECEIVED DATE (DTRC)
COMPLZANCB COKMBHT (COHM) __________________
DOCKET NUMBER (CSFH)
USER DATA ELEMENT ffl
ACCEPT? Y/K/N/M: K
USER DATA ELEMENT §2
FCDEC8CH
SCREEN IDs CSCH
VERSION 2.1 03/12/90
*Note: On-line screen does not contain acronyms.
Compliance Schedule Data Type (CS1 - Screen/Acronvm/Field Descriptions
NPID*! [PERMIT #] (field length = 9 characters)
This field is both a WENDB data element and a Key data element.
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
CSCH*! [COMPLIANCE SCHEDULE NUMBER] (field length = 2 characters)
This field is both a WENDB and a Key data element. A numeric code in this field indicates
that this schedule is from a permit. An alphabetic code indicates that this schedule is from
34-
157T375T
-------
Permit Compliance System (PCS) Basic Training
an enforcement action. A complete listing of COMPLIANCE SCHEDULE NUMBERS can
be found in TABLE 175 in the PCS Codes and Descriptions Manual. The COMPLIANCE
SCHEDULE NUMBERS that are designated as having events from a formal enforcement
action have the phrase "EXTENDED CS" beside them.
DSCD*! [DATA SOURCE CODE] (field length = 4 characters)
This field is both a WENDB and a Key data element. It is used to uniquely identify the
COMPLIANCE SCHEDULE NUMBER. When an alphabetic COMPLIANCE SCHEDULE
NUMBER has been used, indicating that the scheduled event is from a formal enforcement
action, the DATA SOURCE CODE should reflect the pipe or pipe-grouping to which the
schedule pertains.
EVNT*! (field length = 5 characters)
[COMPLIANCE SCHEDULE EVENT CODE]
This field is a both a WENDB and a Key data element. It indicates the individual
compliance schedule events specified in the final permit and/or enforcement action. There
are hundreds of COMPLIANCE SCHEDULE EVENT CODES in TABLE 020 in the PCS
Codes and Descriptions Manual. All COMPLIANCE SCHEDULE EVENT CODES are
WENDB data elements, but if a construction schedule is entered, there are three
COMPLIANCE SCHEDULE EVENT CODES that must be present. They are:
03099 Begin Construction
04599 End Construction
05599 Attain Compliance with Final Limits
-or-
05699 Final Compliance w/Effluent Limits
DTSC* (field length = 6 characters)
[COMPLIANCE SCHEDULE EVENT SCHEDULED DATE]
This field is a WENDB data element. It indicates the date the event is scheduled to be
completed.
DTAC* (field length = 6 characters)
[COMPLIANCE SCHEDULE EVENT ACTUAL DATE]
This field is a WENDB data element. It indicates the date the event is achieved.
$t>C-005$-034-ST-30031371375335
-------
Basic Training Permit Compliance System (PCS)
DTRC* (field length = 6 characters)
[COMPLIANCE REPORT RECEIVED DATE]
This field is a WENDB data element. It contains the date that the Compliance report was
received. If it is not entered, the system defaults to the same date as the COMPLIANCE
SCHEDULE EVENT ACTUAL DATE.
COMM [COMPLIANCE COMMENT] (field length=30 characters)
This field is used to enter any comment(s) about this compliance report that should be
tracked and recorded.
CSFN* [DOCKET NUMBER] (field length = 8 characters)
This field is a WENDB data element only when the COMPLIANCE SCHEDULE NUMBER
is alphabetic, indicating this schedule is from an enforcement action.
RDC1 [USER DATA ELEMENT #1] (field length = 3 characters)
RDC2 [USER DATA ELEMENT #2] (field length = 6 characters)
These fields are used for whatever additional information is to be tracked by the system.
They are optional data entry fields.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
35 12/13/93 $DC-00#-034-$T-3003
-------
Permit Compliance System (PCS) Basic Training
2.4.2 CVIO Compliance Violations Screen
Compliance Violations Screen
15*21:38 COMPLIANCE VIOLATION PCDECVIO
01/14/93 SCREEN 10: CVIO
PEWIT * (NPIDJ TRAMS CODE
COMPLIANCE SCHEDULE NUMBER _
COMPLIANCE SCHEDULE DATA SOURCE CODE (DSCD)
COMPLIANCE SCHEDULE EVENT CODE (CVEV>
VIOLATION CODE
-------
Basic Training Permit Compliance System (PCS)
an enforcement action. A complete listing of COMPLIANCE SCHEDULE NUMBERS can
be found in TABLE 175 in the PCS Codes and Descriptions Manual. The COMPLIANCE
SCHEDULE NUMBERS that are designated as having events from a formal enforcement
action have the phrase "EXTENDED CS" beside them.
DSCD*! [DATA SOURCE CODE] (field length = 4 characters)
This field is both a WENDB and a Key data element. It is used to uniquely identify the
COMPLIANCE SCHEDULE NUMBER. When an alphabetic COMPLIANCE SCHEDULE
NUMBER has been used, indicating that the scheduled event is from a formal enforcement
action, the DATA SOURCE CODE should reflect the pipe or pipe-grouping to which the
schedule pertains. Valid codes appear in TABLE 240 in the PCS Codes and Descriptions
Manual.
CVEV*! (field length = 5 characters)
[COMPLIANCE SCHEDULE EVENT CODE]
This field is a both a WENDB and a Key data element. It indicates the individual
compliance schedule events specified in the final permit and/or enforcement action. There
are hundreds of COMPLIANCE SCHEDULE EVENT CODES in TABLE 020 in the PCS
Codes and Descriptions Manual. All COMPLIANCE SCHEDULE EVENT CODES are
WENDB data elements, but if a construction schedule is entered, there are three
COMPLIANCE SCHEDULE EVENT CODES that must be present. They are:
03099 Begin Construction
04599 End Construction
05599 Attain Compliance with Final Limits
-or-
05699 Final Compliance w/Effluent Limits
There are two additional acronyms and field names that may be of use for purposes of
obtaining information from the system. These fields are internally generated. A brief
description of them follows:
CVIO! (field length = 3 characters)
[COMPLIANCE SCHEDULE 'VIOLATION CODE']
This field is a Key data element. It can be generated by the system or may be entered
manually. Codes that can be generated are:
CIO Reported Late (DTRC is greater than DTAC)
C20 Achieved Late (DTAC is greater than DTSC)
55 T37T3753 $DC-W$5-M4-iiT-:JOO:J
-------
Permit Compliance System (PCS) Basic Training
C30 Unachieved (DTRC is entered but DTAC is blank)
C40 Not Received (Both DTRC and DTAC have not been entered)
Manual Codes are:
M10 M20 M30 M40
CVDT! (field length = 6 characters)
[COMPLIANCE SCHEDULE 'VIOLATION DATE']
This field is a Key data element. It contains the date that the compliance schedule was
violated.
SNCC* [RNC DETECTION] (field length = 1 character)
This field is a WENDB data element. It indicates the non-compliance (RNC) for a particular
compliance schedule violation event. It is automatically generated by the system, unless it is
entered manually.
SNDC* [RNC DETECTION DATE] (field length = 6 characters)
This field is a WENDB data element. It is the actual date of reportable non-compliance
(RNC) for a particular compliance schedule violation event. It is usually system generated.
SRCC* [RNC RESOLUTION] (field length = 1 character)
This field is a WENDB data element. It indicates the resolution of a reported non-
compliance (RNC) for a particular compliance event. It is usually system generated. If
entered manually, it must be a valid manual RNC resolution code.
SRDC* [RNC RESOLUTION DATE] (field length = 6 characters)
This field is a WENDB data element. It is the actual date of resolution for a reported non-
compliance (RNC) for a particular compliance event. It is usually system generated.
VCMT (field length=30 characters)
[COMPLIANCE VIOLATION COMMENT]
This field is used to enter any appropriate comments related to a particular compliance event.
12713753
-------
Basic Training Permit Compliance System (PCS)
RDV1 [USER DATA ELEMENT #1] (field length = 3 characters)
RDV2 [USER DATA ELEMENT #2] (field length = 6 characters)
These fields are used for whatever additional information is to be tracked by the system.
They are optional data entry fields.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
40 E7T3753
-------
Permit Compliance System (PCS) Basic Training
2.5 Inspection Data Type
Inspections are performed on facilities by either EPA or the State regulatory agency usually
once a year. An Inspection Report is completed and the information to be entered into PCS
comes from this Inspection Report. The Inspections Menu is used to reach Inspection related
screens.
Inspections Menu
11/14/92 PCS-ADE Data Entry Subsystem PCOEMENU
11:00:58 Inspections Menu
Enter screen ID or 'X' to select an option
Screen ID:
IMSP Inspections
3 INSS - Inspection Schedule
PCI1 Pretreatnent Camp Insp screen 1
3 PCI 2 - Pretreatnent Conp Insp screen 2
PAU1 - Pretreatment Audit screen 1
3 PAU2 - Pretreatnent Audit screen 2
~ PAU3 Pretreatnent Audit screen 3
SLIM - Sludge Inspection
EXIT - Return to Main menu
-------
Basic Training Permit Compliance System (PCS)
2.5.1 INSS Inspection Schedule Data Type
This data type is used to keep track of inspections that are scheduled to be performed. It can
be linked to the actual inspection that was performed when the key data elements on the
Inspection Scheduling record and the Inspection record are the same. Even though the
Inspection Scheduling record is at a higher level than the Inspection record, the Inspection
Scheduling record does not have to be entered in order to enter the Inspection record. The
following screen is used in PCS-ADE to enter the information for the Inspection Scheduling
record.
Inspection Scheduling Screen
08:45:43 IHSPSCTIOH 3CHKDULHHJ FCOEZN3S
04/03/90 SCRBBH ID: INS3
PERMIT f TRASS CODS _
SCHEDULED INSPECTION TYPE (STOP) _ SCHEDULED INSPECTOR CODE (SIRS) _
SCHBDOLBO ZHSPBCTIUH DATE (8IDT) _^___
OR SCHEDULED INSPECTION QTH/YKAR (3IQR) _ / __
ACHIEVED IHSPECTIOH DATE (SDTX)
(NOTE: BHTRY OP SDTI ONLY NECBSSAKY FOR MODIFICATION
OP A LXIOSD 8CHEDDLB RECORD.)
INSPECTION 8CHBDUX.IB9 COMKEHX3*
USC1)
{ISO)
{I8C3)
MODIFICATION OF IHSPECTIOB SCHEDULING XBY INPORMXriON:
REVISED SCHEDULED IDSFBCTIOH TYPE (HT5fP) _
HBVISBD SCKEDULBD IHSFBCIOR CODE {KIRS) _
REVISED SCHHDOUm D*TB (RIDT) *"
REVISED SCHEDULED OTR/YBMt {RltJRJ _ /
ACCBPT7 Y/R/M/Mt X VBX9ION 3.0 03/05/90
Inspection Scheduling Data Type (IS1 - Screen/Acronym/Field Descriptions
NPID*! [PERMIT #J (field length = 9 characters)
This field is both a WENDB data element and a Key data element.
42 12/13/93 SDC-0055-Q34-ST-3003
-------
Permit Compliance System (PCS) Basic Training
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
STYP! [SCHEDULED INSPECTION TYPE] (field length = 1 character)
This field is a Key data element. Examples of valid codes are listed below. A complete
listing of valid codes can be found in TABLE 280 in the PCS Codes and Descriptions
Manual.
Example:
C compliance evaluation
S compliance sampling
X toxic
SINS! [SCHEDULED INSPECTOR CODE] (field length = 1 character)
This field is a Key data element and indicates who is scheduled to conduct the inspection.
Examples of valid codes for this field are listed below. A complete listing of valid codes can
be found in TABLE 290 in the PCS Codes and Descriptions Manual.
Example:
R Region
S State
J Joint EPA and State (EPA lead)
T Joint EPA and State (State lead)
SBDT! [SCHEDULED INSPECTION DATE] (field length = 6 characters)
This field is a Key data element and indicates the date the inspection is to be conducted. It
cannot be entered if you are entering the Scheduled Inspection Qtr/Year.
SIQR! (field length = 3 characters)
[SCHEDULED INSPECTION QTR/YEAR]
This field is a Key data element. Enter the fiscal quarter and year the inspection is
scheduled to be performed. Fiscal quarters are:
Quarter 1 October 1 - December 31
Quarter 2 January 1 - March 31
Quarter 3 April 1 - June 30
Quarter 4 July 1 - September 30
SDC-0055-034-ST-3003 12/13/93 43*
-------
Basic Training Permit Compliance System (PCS)
This element cannot be entered if you are entering the Scheduled Inspection Date.
SDH [ACHIEVED INSPECTION DATE] (field length = 6 characters)
This date only needs to be entered if an inspection record has been entered and the comments
on the inspection scheduling records has to be changed.
ISC1 (field length=30 characters)
[INSPECTION SCHEDULING COMMENTS Held 1]
ISC2 (field length=30 characters)
[INSPECTION SCHEDULING COMMENTS field 2]
ISC3 (field length=30 characters)
[INSPECTION SCHEDULING COMMENTS field 3]
Any comments relating to the scheduled inspection are entered in these fields.
RTYP (field length = 1 character)
[REVISED SCHEDULED INSPECTION TYPE]
This field is entered only if it is necessary to change the Key data elements.
REVS (field length = 1 character)
[REVISED SCHEDULED INSPECTOR CODE]
This field is entered only if it is necessary to change the Key data elements.
RIDT [REVISED SCHEDULED DATE] (field length = 6 characters)
This field is entered only if it is necessary to change the Key data elements.
RIQR [REVISED SCHEDULED QTR/YEAR] (field length = 3 characters)
This field is entered only if it is necessary to change the Key data elements.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
4412/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
SDC-0055-034-ST-3003 12/13/93 45
-------
Basic Training Permit Compliance System (PCS)
2.5.1.1 INSP Inspections Screen
The following PCS-ADE screen is used to enter information for the inspection record.
Inspections Screen
08(45:56 IH3PBCTIOH3 FCDBIHS?
04/03/90 SCREEN ID:
PERMIT t ^___^_ TSAS8 OODB _
IKSFECTIOH DATE {DTXH) _____ XMSPECTXOR T»B (TYPI) _
IB3FECIOR CODE
USER DATA BLEMENT !
-------
Permit Compliance System (PCS) Basic Training
TYPI*! [INSPECTION TYPE] (field length - 1 character)
This field is both a key and WENDB data element. It indicates the type of inspection that
was conducted. Examples of the codes are listed below. A complete listing of Inspection
Type codes can be found in TABLE 280 in the PCS Codes and Descriptions Manual.
Example:
C Compliance evaluation
S Compliance sampling
X Toxic
INSP* [INSPECTOR CODE] (field length = 1 character)
This field is a WENDB data element. It indicates who conducted the inspection. Examples
of these codes are listed below. A complete listing of Inspector Codes can be found in
TABLE 290 of the PCS Codes and Descriptions Manual.
Example:
R Region
S State
J Joint EPA lead
T Joint state lead
FACC [INSPECTED FACILITY TYPE] (field length = 1 character)
This field describes the type of facility that is being inspected. A complete listing of valid
codes can be found in TABLE 300 in the PCS Codes and Descriptions Manual. They are:
1 Municipal
2 Industrial
3 Agricultural
4 Federal
BIOM (field length = 1 character)
[BIOMONTFORING INSPECTION METHOD]
When a 'B' is entered in the INSPECTION TYPE field, this field should be entered. It
indicates which type of biomonitoring inspection was conducted. The codes for this field can
be found in TABLE 260 in the PCS Codes and Descriptions Manual.
SDC-0055-034-ST-3(X)3 12/13/93 47
-------
Basic Training Permit Compliance System (PCS)
QABI [QA-DATA BASED INSPECTION] (field length = 1 character)
A 'Q' is entered in this field if the inspection is based on QA/DMR data.
ICOM [INSPECTION COMMENT] (2 fields of SO characters each)
IC25 INSPECTION COMMENT (first 25 characters)
For TYPE of I or U, it is WENDB to enter the number of facilities inspected in the first
three characters of ICOM with leading zeros.
[TOTAL HOURS (PRE/INSP/POST)] (3 fields of 3 characters each)
These three fields indicate the number of hours for pre-inspection, the inspection itself and
post-inspection work. They can be retrieved separately by the acronyms listed below.
PRHR [INSPECTION PRE-PROCESSING HOURS]
The total number of hours expended by the inspection team for pre-investigation activities
(planning, travel to the site, etc.) Include clerical/ administrative and lab personnel time,
where applicable.
INHR [INSPECTION IN-PROCESSING HOURS]
The total number of hours expended by the inspection team for activities during the
inspection (processing, etc.) Include clerical/ administrative and lab personnel time,
where applicable.
POHR [INSPECTION POST-PROCESSING HOURS]
The total number of hours expended by the inspection team for post-inspection activities
(report production, travel from site, lab support, etc). Include clerical/ administrative
and lab personnel time, where applicable.
FEVR [FACILITY EVALUATION RATING] (field length = 3 characters)
This field is user-defined and is used to rate the quality assurance of an inspection.
DTRR [DATE REPORT RECEIVED] (field length = 6 characters)
This field contains the date that the inspection report was received.
48 12/13/93 SDCHXJ55-034-ST-3003
-------
Pfennit Compliance System (PCS) Basic Training
RDI1 [USER DATA ELEMENT #1] (field length = 3 characters)
This is a user-defined field. Consult with the Regional PCS Coordinator before using this
field.
RDI2 [USER DATA ELEMENT #2] (field length = 6 characters)
This is a user-defined field. Consult with the Regional PCS Coordinator before using this
field.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
[PRETREATMENT DATA?] (field length = 1 character)
This field is used to indicate that a Pretreatment Inspection was performed. If a 'Y' is
entered in this field and the INSPECTION TYPE field has a 'P', PCS-ADE will
automatically display the PCI1 screen. If a 'Y' is entered in this field and the INSPECTION
TYPE field has a 'G' PCS-ADE will automatically display the PAU1 screen, so that
Pretreatment Audit data can be entered.
[SLUDGE DATA? Y/N] (field length = 1 character)
Indicate:
Y (Yes) to continue to the SLTN screen.
N (No) will not continue to the SLIN screen.
SDC-0055-034-ST-3003 12/13/93 49
-------
Basic Training Permit Compliance System (PCS)
2.6 Pretreatment Compliance Inspection Data Type
Data for this data type may be entered only if the Type of Inspection (TYPE) is P
(Pretreatment Compliance Inspection) on the Inspection record.
The data for these screens comes from the Pretreatment Compliance Inspection report. The
following are the PCS-ADE screens to enter the PCI. If the TYPE is 'P' on the INSP
screen, PCS-ADE will automatically display the PCI1 screen when you type *Y" for
PRETREATMENT DATA? or you may access these screens from the PCS-ADE Main
Menu.
2.6.1 PCI1 Pretreatment Compliance Inspection Screen
Pretreatment Compliance Inspection Screen
17:06:18 PRBTRKATHBNT COMPLIANCE INSPECTION PCDBPCI1
04/05/90 SCREEN ID: PCX!
PERMIT * TRANS CODS _
DATS OF PCIs (DTIA) ~
NUMBER OF SXGNIFXCABT IDS (BIOS) NUMBER OF CATEGORICAL IDS (CXOS)
SXB3 HOT ZHSFBCTBD OR SAMPLED (HOZH) ___
ana WITHOUT CONTROL MBCwuixaMa (ROCM)
3ID8 IN atiC WITH STANDARDS OR REPORTING (PSHC)
SZDS IN SHC WITH 8ELF-MONXTORXNO (MSHC)
aroa IH SHC WITH SELF-MONXTORXNG t HOT INSPECTED OR SAMPLED (SHIN)
PRBTRBATHBHT COORDINATOR HAMS (ODOR) ________________^^______
PROGRAM BLXNBHT CHANGES (FRCH)
t OF 3103 WHICH HAVE NOT INSTALLED REQUIRED FRBTRBATMBNT
-------
Permit Compliance System (PCS) Basic Training
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
DTIA! (field length = 6 characters)
[DATE OF PRETREATMENT COMPLIANCE INSPECTION]
This field is a Key data element. This date must be the same as the Inspection Date (DIN).
SIUS* (field length = 4 characters)
[NUMBER OF SIGNIFICANT INDUSTRIAL USERS]
This field is a WENDB data element. It is the number of significant industrial users that
were inspected during the PCI.
CIUS* (field length = 4 characters)
[NUMBER OF CATEGORICAL INDUSTRIAL USERS]
This field is a WENDB data element. This is the number of categorical industrial users that
were inspected during the PCI. This field cannot be higher than the number entered in the
SIUS field.
NOIN* (field length = 3 characters)
[SIUS NOT INSPECTED OR SAMPLED]
This field is a WENDB data element. It represents the number of SIUs that were not
inspected or sampled by the Pretreatment Control Authority in the past year. The report
supplies this information as a percentage of all SIUSs. To determine the number to be
entered, multiply the percentage by the total number of SIUs. This number cannot be greater
than the number in the SIUS field.
NOCM* (field length = 3 characters)
[SIUS WITHOUT CONTROL MECHANISMS]
This field is a WENDB data element. It represents the number of SIUs for which a current
control mechanism is required. The report supplies this information as a percentage of all
SIUs. To determine the number to be entered, multiply the percentage by the total number
of SIUs. This number cannot be greater than the number in the SIUS field.
SDC-0055-034-ST-3D03 12/13/93 51
-------
Basic Training Permit Compliance System (PCS)
PSNC* (field length = 3 characters)
[SIUS IN SNC WITH STANDARDS OR REPORTING]
This field is a WENDB data element. It represents the number of SIUs that are in SNC in
the past year with applicable pretreatment standards or reporting requirements. The report
supplies this information as a percentage of all SIUs. To determine the number to be
entered, multiply the percentage by the total number of SIUs. This number cannot be greater
than the number in the SIUS field.
MSNC* (field length = 3 characters)
[SIUS IN SNC WITH SELF-MONITORING]
This field is a WENDB data element. It represents the number of SIUs which were in SNC
in the past year with applicable self-monitoring requirements, either by failing to accurately
report non-compliance, or failure to provide self-monitoring data within 30 days of the due
date. Only the following values may be entered in this field:
0-9 Valid numeric characters
NA Not Applicable - If this is entered, it must be left justified.
SNIN* (field length = 3 characters)
[SIUS IN SNC WITH SELF-MONITORING & NOT INSPECTED OR SAMPLED]
This field is a WENDB data element. It represents the number of SIUs in SNC with self-
monitoring requirements and which have not been inspected and/or sampled by the
Pretreatment Control Authority in the past year. Only the following values may be entered
in this field:
0-9 Valid numeric characters
NA Not Applicable - If this is entered, it must be left justified.
COOR (field length =25 characters)
[PRETREATMENT COORDINATOR NAME]
This field represents the name of the Pretreatment Coordinator or contact at the Pretreatment
Control Authority.
52 12/13/93 SDC-0055-034-il-JUU3
-------
Permit Compliance System (PCS) Basic Training
PRCH [PROGRAM ELEMENT CHANGES] (field length = 6 characters)
This field indicates what program elements were changed without approval since the last PCI
or follow-up. Valid options, which can be found in TABLE 560 in the PCS Codes and
Descriptions Manual, include:
A Legal authority
C Control mechanism implementation
E Enforcement program
I Inspection/monitoring program
L Local limits
R Resources
NOPT (field length = 3 characters)
[% OF SIUS WHICH HAVE NOT INSTALLED REQUIRED FRETREATMENT]
This field indicates the approximate percentage of SIUs which have failed to install
pretreatment technologies to meet applicable pretreatment standards, although required to do
so. The number entered represents a percentage, not a count. The percentage is entered as
a whole number. The system will not allow a decimal point or a percentage sign to be
entered.
SNPS (field length = 3 characters)
[SIUS IN SNC WITH: PRETREATMENT STANDARDS]
This field indicates the number of SIUs currently in SNC with applicable pretreatment
standards.
RSNC (field length = 3 characters)
[SIUS IN SNC WITH: REPORTING REQUIREMENTS]
This Meld represents the number of SIUs currently in SNC with applicable pretreatment
reporting requirements in the past year.
ERGG [ENFORCEMENT RESPONSE GUIDE] (field length = 1 character)
This is a one-character 'Y'es/'N'o field indicating whether the Pretreatment Control
Authority has developed and uses enforcement response guides to indicate the range of
appropriate, relatively standard, responses to specific types of non-compliance.
5DC-0055-034-ST-3003 12/13/93 5J
-------
Basic Training _ Permit Compliance System (PCS)
SUPP (field length = 1 character)
[DOES PCI SUPPORT MOST RECENT PRETREATMENT SUMMARY REPORT]
This is a one-character 'Y'es/'N'o field indicating whether the PCI generally supports
statements made by the Pretreatment Control Authority in the most recent report.
CMDF (field length =8 characters)
[CONTROL MECHANISM DEFICIENCIES]
This field contains codes that represent the components that are not sufficient or are not
contained in the Pretreatment Control Authority control mechanism, which it issues to
industrial users. Valid codes can be found in TABLE 580 in the PCS Codes and
Descriptions Manual. They include:
A Refer to local ordinance/legal authority
C Standard conditions
D Effective and expiration dates
I IU self-monitoring requirements
L Applicable discharge limits
R IU reporting requirements
S Sampling location
(field length = 6 characters)
[DEFICIENCIES NOTED IN IU FILE REVIEW]
This field indicates the broad areas in which deficiencies were noted during the PCI or audit
inspector's review of industrial user files. Valid codes can be found in TABLE 570 in the
PCS Codes and Descriptions Manual. Valid options include:
C Control Mechanisms
E Enforcement by the POTW
F File Contents
I IU self-monitoring
M POTW compliance monitoring
S Spills/Slug loading
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
54 - 12713753
-------
Permit Compliance System (PCS) Basic Training
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
MORE DATA ? (field length = 1 character)
Enter 'Y'es if more data is to be entered. Respond 'N'o if there is no additional data to
enter at this time.
SDC-M#-034-ST-3003 12/13/93 55
-------
Basic Training Permit Compliance System (PCS)
2.6.2 PCI2 Pretreatment Compliance Inspection Screen 2
Pretreatment Compliance Inspection Screen 2
17:07:53 PRBTRBAWBOT COMPLIAHCB IH8FECXTOH PCDEPCI3
04/05/90 SCRBBH ID: PCZ2
PERMIT * _ TRAMS OODB C
DATE OP PCIs
-------
Permit Compliance System (PCS) Basic Training
WSTE [ACCEPTANCE OF OTHER WASTE] (field length = 6 characters)
This field contains codes that indicate the POTW receives other wastes besides domestic
sewage or industrial process wastewater. Valid codes can be found in TABLE 680 in the
PCS Codes and Descriptions Manual. Valid options include:
L Landfill leachate
N None
O Other
R RCRA/CERCLA site wastes/leachate
S Hauled septage
RECR [REMOVAL CREDITS] (field length = 1 character)
This field indicates the status of the application for removal credit for the Pretreatment
Control Authority. Valid codes can be found in TABLE 670 in the PCS Codes and
Descriptions Manual. Valid options include:
A Approved
D Denied
N Not applicable
P Pending
RCRD [REMOVAL CREDITS APPROVAL DATE] (field length = 5 characters)
This field indicates the date the application for removal credits was approved.
RSCH (field length = 1 character)
[RESPONSE TO SCHEDULE FOR REMEDIAL MEASURES]
This field indicates whether a formal enforcement action has been taken in response to a
violation of any schedule for implementation of needed remedial measures identified as a
result of audits or inspections. Valid options include:
Y Yes
N No
SDC-0055-034-ST-3003 12/13/93 57
-------
Basic Training Permit Compliance System (PCS)
VSCH (field length = 1 character)
[VIOLATION TO SCHEDULE FOR REMEDIAL MEASURES]
This field indicates whether there has been a violation of any schedule issued by the
Pretreatment Control Authority for implementation of needed remedial measures identified as
a result of audits or inspections. Valid options include:
Y Yes
N No
DSSM (field length = 1 character)
[PROGRAM MODIFICATION TO ADDRESS: DOMESTIC SEWAGE STUDY]
This field indicates whether the pretreatment program is adequate to sufficiently address the
new program requirements imposed through regulations issued as a follow-up to the domestic
sewage study. Valid options include:
Y Yes
N No
PIRT (field length = 1 character)
[PROGRAM MODIFICATION TO ADDRESS: PIRT AMENDMENTS]
This field indicates whether the pretreatment program is adequate to sufficiently address all
new program requirements imposed by the recent PIRT amendments to the General
Pretreatment Regulations. Valid options include:
Y Yes
N No
SMDF (field length = 5 characters)
[DEFICIENCIES IN POTW SAMPLING OF INDUSTRIAL USERS]
This field represents the deficiencies which exist in the Pretreatment Control Authority's
sampling of industrial users. Valid codes can be found in TABLE 660 in the PCS Codes and
Descriptions Manual. Valid options include:
C Inadequate chain of custody
F Inadequate sampling frequency
P Improper sampling protocols
S Improper/inadequate parameters sampling
T Improper sample types
55 I37I3753
-------
Permit Compliance System (PCS) Basic Training
MADF (field length = 4 characters)
[MULTI-JURISDICTIONAL AGREEMENT DEFICIENCIES]
This field represents the deficiencies which exist in the Pretreatment Control Authority's
multi-jurisdictional agreements. Valid codes can be found in TABLE 650 in the PCS Codes
and Descriptions Manual. Valid options include:
A Lack of oversight authority
I Lack of inspection authority
N Lack of remedies for non-compliance
R Poor delineation of responsibility
PTJU (field length = 2 characters)
[JURISDICTIONS COVERED BY PRETREATMENT PROGRAM]
This field represents the number of jurisdictions covered by the Pretreatment Control
Authority's pretreatment program, including those outside the usual jurisdictional boundaries
of the POTW.
RDN1 [REGIONAL FIELD 1] (field length = 3 characters)
RDN2 [REGIONAL FIELD 2] (field length = 6 characters)
These are user-defined fields. Consult with the Regional PCS Coordinator before using these
fields.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
SbC-005$-034-ST-3003 12/13/93
-------
Basic Training
Permit Compliance System (PCS)
2.7 Pretreatment Audit Inspection Data Type
The data for these screens comes from the Pretreatment Audit Inspection report. The
following are the PCS-ADE screens to enter the PAU. If the TYPI is F or G on the INSP
screen, PCS-ADE will automatically display the PAU1 screen when you type 'Y' for
PRETREATMENT DATA? or you may access these screens from the PCS-ADE Main
Menu.
Data for this data type may be entered only if the Type of Inspection (TYPI) is F
(Follow-Up) or G (Pretreatment Audit Inspection) on the Inspection record.
2.7.1 PAU1 Pretreatment Audit Screen 1
Pretreatment Audit Screen 1
08152:50
04/09/90
PBRMZT t
PRBTRKATMBHT AUDIT
TRANS COOS
PCDEPAU1
SCREED ID: PAD1
DATS OP AUDIT: (DTXA)
DAXB PKHKIT MODIPXBD TO REOOIRB PHSTREATMKHT mPLSMZHTATION (FTIM) _____
SIGNIFICANT INDUSTRIAL U8BR8 WITHOUT COBTTROL MBCHARX8M (HOCM)
NUMBER OP SIGNIFICANT IDS (SIDS) NUMBER OP CATEGORICAL IDS
-------
Permit Compliance System (PCS) Basic Training
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
DTIA! (field length = 6 characters)
[DATE OF PRETREATMENT COMPLIANCE INSPECTION]
This field is a Key data element. This date must be the same as the Inspection Date (DTIN).
PTTM* (field length = 6 characters)
[DATE PERMIT MODIFIED TO REQUIRE PRETREATMENT IMPLEMENTATION]
This field is a WENDB data element. It indicates the date the Pretreatment Control
Authority's NPDES permit was modified to require pretreatment implementation.
NOCM* (field length = 3 characters)
[SIGNIFICANT INDUSTRIAL USERS WITHOUT CONTROL MECHANISM]
This field is a WENDB data element. It represents the number of SIUs for which a current
control mechanism is required but not yet issued. The audit report supplies this information
as a percentage of all SIUs. To determine the number to be entered in this field, multiply
the percentage by the total number of SIUs. This number cannot be greater than the number
in the SIUS field.
SIUS* [NUMBER OF SIGNIFICANT IUS] (field length = 5 characters)
This field is a WENDB data element. This is the number of significant industrial users that
were inspected during the audit.
CIUS* [NUMBER OF CATEGORICAL IUS] (field length = 5 characters)
This field is a WENDB data element. This is the number of categorical industrial users that
were inspected during the audit. This number cannot be greater than the number in the SIUS
field.
EVLL* (field length = 1 character)
[TECHNICAL EVALUATION FOR LOCAL LIMITS]
This field is a WENDB data element. It indicates whether the Pretreatment Control
Authority has technically evaluated the need for local limits for any pollutants required by the
SDC-0055-034-ST-3003 12/13/93 61
-------
Basic Training Permit Compliance System (PCS)
Pretreatment Approval Authority. Valid options for this field include:
N No
P Partial
Y Yes
ADLL* (field length = 1 characters)
[ADOPTION OF TECHNICALLY BASED LOCAL LIMITS]
This field is a WENDB data element. It is related to the EVLL field. This field indicates
whether the Pretreatment Control Authority has adopted local limits for certain pollutants, if
a technical evaluation indicated the need for such local limits. Valid codes can be found in
TABLE 700 in the PCS Codes and Descriptions Manual. Valid options include:
N No
Y Yes
Z Not applicable
NOIN* [SIUS NOT INSPECTED OR SAMPLED] (field length = 3 characters)
This field is a WENDB data element. It represents the number of SIUs that were not
inspected or sampled by the Pretreatment Control Authority in the past year. The audit
report supplies this information as a percentage of all SIUs. To determine the number to be
entered in this field, multiply the percentage by the total number of SIUs. This number
cannot be greater than the number in the SIUS field.
PSNC* (field length = 3 characters)
[SIUS IN SNC WITH STANDARDS OR REPORTING]
This field is a WENDB data element. It represents the number of SIUs that are in SNC in
the past year with applicable pretreatment standards or reporting requirements. The report
supplies this information as a percentage of all SIUs. To determine the number to be
entered, multiply the percentage by the total number of SIUs. This number cannot be greater
than the number in the SIUS field.
MSNC* (field length = 3 characters)
[SIUS IN SNC WITH SELF-MONITORING]
This field is a WENDB data element. It represents the number of SIUs which were in SNC
in the past year with applicable self-monitoring requirements, either by failing to accurately
62 12/13/93 SDC-0055-034-M-.3UU.J
-------
Permit Compliance System (PCS) Basic Training
report non-compliance, or failure to provide self-monitoring data within 30 days of the due
date. Only the following values may be entered in this field:
0-9 Valid numeric characters
NA Not Applicable - If this is entered, it must be left justified.
SNIN* (field length = 3 characters)
[SIUS IN SNC WITH SELF-MONITORING & NOT INSPECTED OR SAMPLED]
This field is a WENDB data element. It represents the number of SIUs in SNC'with self-
monitoring requirements and which have not been inspected and/or sampled by the
Pretreatment Control Authority in the past year. Only the following values may be entered
in this field:
0-9 Valid numeric characters
NA Not Applicable - If this is entered, it must be left justified.
COOR (field length =25 characters)
[PRETREATMENT COORDINATOR NAME]
This field represents the name of the Pretreatment Coordinator or contact at the Pretreatment
Control Authority.
SLDG [SLUDGE DISPOSAL METHODS] (field length = 6 characters)
This field represents the disposal methods the POTW utilizes to dispose of their sludge.
MXPN [MAXIMUM CIVIL PENALTY BY LAW] (field length = 6 characters)
This field indicates the maximum civil penalty per day per violation which the Pretreatment
Control Authority is authorized to impose or cause to be imposed on its industrial users by
law. No special characters, decimal points or commas are allowed.
BUDG [ANNUAL PRETREATMENT BUDGET] (field length = 6 characters)
This field represents the total level of annual funding used to implement the Control
Authority's pretreatment program. No special characters, decimal points or commas are
allowed.
SbC-OOtf-034-ST-3003 15713753 53
-------
Basic Training Permit Compliance System (PCS)
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu0.
MORE DATA ? (field length = 1 character)
Enter 'Y'es if more data is to be entered. Respond 'N'o if there is no additional data to
enter at this time.
54 12713753
-------
Permit Compliance System (PCS)
Basic Training
2.7.2 PAU2 Pretreatment Audit Screen 2
Pretreatment Audit Screen 2
08)53:54
04/09/90
PERMIT t ,
AUDIT
TRANS coos c
DATE OF AUDITl {DTZA)
PASS-XHRODOR (PASS) _
ICY OF TOXZCAHT
SBHPUOIB FOR*
(ZNTF) _
(TXZH)
BFFLDBHTS (TXBF)
SLUMS
-------
Basic Training Permit Compliance System (PCS)
PASS [PASS-THROUGH] (field length = 1 character)
This field indicates if there have been any incidents of pass-through at the POTW during the
past year. Valid options for this field include:
Y Yes
N No
INTF [INTERFERENCE] (field length = 1 character)
This field indicates if there have been any incidents of interference at the POTW during the
past year. Valid options for this field include:
Y Yes
N No
TXIN (field length = 2 characters)
[FREQUENCY OF TOXICANT SAMPLING FOR: INFLUENTS]
This field indicates the number of times that toxicant sampling of the influent was performed
at the POTW during the past year.
TXEF (field length = 2 characters)
[FREQUENCY OF TOXICANT SAMPLING FOR: EFFLUENTS]
This field indicates the number of times that toxicant sampling of the effluent was performed
at the POTW during the past year.
TXSL (field length = 2 characters)
[FREQUENCY OF TOXICANT SAMPLING FOR: SLUDGE]
This field indicates the number of times that toxicant sampling of the sludge was performed
at the POTW during the past year.
SNPS (field length = 3 characters)
[SIUS IN SNC WITH: PRETREATMENT STANDARDS]
This field indicates the number of SIUs currently in SNC with applicable pretreatment
standards.
66 12/13/93 SDC-0055-034-& 1-3003
-------
Permit Compliance System (PCS) Basic Training
RSNC (field length = 3 characters)
[SIUS IN SNC WITH: REPORTING REQUIREMENTS]
This field represents the number of SIUs currently in SNC with applicable pretreatment
reporting requirements in the past year.
ERGG [ENFORCEMENT RESPONSE GUIDE] (field length = 1 character)
This is a one-character 'Y'es/'N'o field indicating whether the Pretreatment Control
Authority has developed and uses enforcement response guides to indicate the range of
appropriate, relatively standard, responses to specific types of non-compliance.
RESO (field length = 7 characters)
[INADEQUACIES IN PRETREATMENT RESOURCES]
This field represents the inadequacies in the Control Authority's pretreatment resources.
Valid codes can be found in TABLE 600 in the PCS Codes and Descriptions Manual. Valid
options include:
A Insufficient access to analytical equipment
E Insufficient safety equipment
F Insufficient funding
P Inadequate numbers of personnel
S Insufficient sampling equipment
T Insufficient training of personnel
V Insufficient numbers of vehicles
FTDF (field length = 6 characters)
[DEFICIENCIES NOTED IN IU FILE REVIEW]
This field indicates the broad areas in which deficiencies were noted during the PCI or audit
inspector's review of industrial user files. Valid codes can be found in TABLE 570 in the
PCS Codes and Descriptions Manual. Valid options include:
C Control Mechanisms
E Enforcement by the POTW
F File Contents
I IU self-monitoring
M POTW compliance monitoring
S Spills/Sludge loading
SDC-0055-034-ST-3003 12/13/93 67
-------
Basic Training Permit Compliance System (PCS)
CMDF (field length = 8 characters)
[CONTROL MECHANISM DEFICIENCIES]
This field contains codes that represent the components that are not sufficient or are not
contained in the Pretreatment Control Authority control mechanism, that it issues to
industrial users. Valid codes can be found in TABLE 580 in the PCS Codes and
Descriptions Manual. Valid options include:
A Refer to local ordinance/legal authority
C Standard conditions
D Effective and expiration dates
I IU self-monitoring requirements
L Applicable discharge limits
R IU reporting requirements
S Sampling location
LADF [LEGAL AUTHORITY DEFICIENCIES] (field length = 9 characters)
This field represents the areas of problems or deficiencies that exist in the legal authority of
the Pretreatment Control Authority as a result of changes since program approval. Valid
codes can be found in TABLE 590 in the PCS Codes and Descriptions Manual. Valid
options include:
A Applying & enforcing pretreatment standards
C Complying with confidentiality requirements
D Deny or impose conditions on new or increased contributions
H Halting or preventing discharges
I Allowing industrial user inspections & sampling
N Obtaining remedies for non-compliance
P Control industrial user through permit, contract, etc.
R Requiring submission of industrial user reports
S Requiring development of industrial user compliance schedule
58 12713753
-------
Permit Compliance System (PCS) Basic Training
APDF (field length=10 characters)
[DEFICIENCIES IN INTERPRETATION/APPLICATION OF STANDARDS]
This field indicates the deficiencies noted in the Pretreatment Control Authority's
interpretation and application of pretreatment standards to industrial users. Valid codes can
be found in TABLE 630 in the PCS Codes and Descriptions Manual. Valid options include:
A Fail to apply more stringent standards
C Incorrect categorization of industrial users
D Improper designation of sampling location
I Fail to identify categorical industrial users
L Application of inappropriate long-term average
M Fail to use effective control mechanism
P Improper application of production-based standards
S Inadequate sample type and/or frequency
T Fail to apply appropriate TTO limits
W Misuse of combined wastestream formula
ADIN (field length = 4 characters)
[INADEQUACY IN POTW'S INSPECTION & SAMPLING OF lUs]
This field indicates whether the Pretreatment Control Authority performs inadequate
inspections and sampling of its industrial users to accomplish a number of specific goals.
Valid codes can be found in TABLE 660 in the PCS Codes and Descriptions Manual. Valid
options include:
A Fail to assess compliance of industrial users
C Fail to characterize industrial user pollutants
E Fail to provide admissible evidence
I Fail to investigate non-compliance
R Fail to receive/review all industrial user reports
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
SbC-00#-034-ST-3003 15713793 59
-------
Basic Training Permit Compliance System (PCS)
MORE DATA ? (field length = 1 character)
Enter 'Y'es if more data is to be entered. Respond 'N'o if there is no additional data to
enter at this time.
70 12/13/93 St)C-OOSS-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
2.7.3 PAU3 Pretreatment Audit Screen 3
Pretreatment Audit Screen 3
oat54*42 ntBTKunanT AUDIT PCDEPADS
OA/03/90 SCREBH ID: PAO3
PERMIT * TRAM CODS C
OATS OF AOBXTi (DTXA) _________
DBFXCX8MCU3 ZB DATA MABA0BM8BT fc PUBLIC PARTICIPATION
MOLTI-JURISDICTXOHAL A3RBKMBHT DBTXCZBHCZBS (MADF)
COVERED BY PRBTREATMBHT ntaaitMt (pmr)
or wutauooa w*ars (KCBA> _
HUH WMXB (W3TB) _____
PROQKAM HODZFICKTZOa TO ADDRESS: DOMESTIC SBWACK STODY (DSflM) _
PI«T JUfflHEKBHTS (VIRT) _
RBMOVK. CRKD1T3 (RKCR) _ RKMOWU. CREDITS APFROVM. OKtB {RCRD>
RSSPOMSB TO VIOIATiaR O? 8CHBDUU FOR RBMBDXAL MBMOX8S (RflCH) _
VIOLATIOH OF BCKBDOU FOR R8MKDIAL MBASQRE3 (V8CK) _
flITJa HOT SAMPLED OH IH3PBCTBD AT RBQUIRBD PRBOQEHCX (HINF)
T8CHHICM. BVALOXTIOH FOR COMFXBHBN8ZVB LOCAL LIMITS (BVCL) _
OF BIOS WHICH H&VB HOT ZH3T&LLBD RBgOIRBD FRBTRTMT (HOPT)
PROGRAM KLBMEHT CHANGES (PRCH)
SWMARY RBPORT (SOPP) _
RBOIOHAL FIELD 1 0055-034-ST-3{X)3 12/13/93 71
-------
Basic Training Permit Compliance System (PCS)
DMDF (field length = 6 characters)
[DEFICIENCIES IN DATA MANAGEMENT & PUBLIC PARTICIPATION]
This field represents the deficiencies in the Pretreatment Control Authority's data
management and public participation efforts. Valid codes can be found in TABLE 610 in the
PCS Codes and Descriptions Manual. Valid options include:
A Fail to provide public access to effluent data
C Fail to handle confidentiality
D Poor document of activity in industrial user files
M Fail to maintain records for 3 years
N Fail to notify re. development of local limits
P Fail to publish annual list of significant violations
SMDF (field length = 5 characters)
[DEFICIENCIES IN POTW SAMPLING OF INDUSTRIAL USERS]
This field represents the deficiencies which exist in the Pretreatment Control Authority's
sampling of industrial users. Valid codes can be found in TABLE 660 in the PCS Codes and
Descriptions Manual. Valid options include:
C Inadequate chain of custody
F Inadequate sampling frequency
P Improper sampling protocols
S Improper/inadequate parameters sampling
T Improper sample types
MADF (field length = 4 characters)
[MULTI-JURISDICTIONAL AGREEMENT DEFICIENCIES]
This field represents the deficiencies which exist in the Pretreatment Control Authority's
multi-jurisdictional agreements. Valid codes can be found in TABLE 650 in the PCS Codes
and Descriptions Manual. Valid options include:
A Lack of oversight authority
I Lack of inspection authority
N Lack of remedies for non-compliance
R Poor delineation of responsibility
72 12/13/93 SDCHK)55-034-bI-3UUJ
-------
Permit Compliance System (PCS) Basic Training
PTJU (field length = 2 characters)
[JURISDICTIONS COVERED BY PRETREATMENT PROGRAM]
This field represents the number of jurisdictions covered by the Pretreatment Control
Authority's pretreatment program, including those outside the usual jurisdictional boundaries
of the POTW.
RCRA [ACCEPTANCE OF HAZARDOUS WASTE] (field length = 1 character)
This field indicates whether the POTW accepts hazardous waster by truck, rail, or dedicated
pipe. Valid options for this field include:
Y Yes
N No
WSTE [ACCEPTANCE OF OTHER WASTE] (field length = 5 characters)
This field contains codes that indicate the POTW receives other wastes besides domestic
sewage or industrial process wastewater. Valid codes can be found in TABLE 680 in the
PCS Codes and Descriptions Manual. Valid options include:
L Landfill leachate
N None
O Other
R RCRA/CERCLA site wastes/leachate
S Hauled septage
DSSM (field length = 1 character)
[PROGRAM MODIFICATION TO ADDRESS: DOMESTIC SEWAGE STUDY]
This field indicates whether the pretreatment program is adequate to sufficiently address the
new program requirements imposed through regulations issued as a follow-up to the domestic
sewage study. Valid options include:
Y Yes
N No
PIRT (field length = 1 character)
[PROGRAM MODIFICATION TO ADDRESS: PIRT AMENDMENTS]
This field indicates whether the pretreatment program is adequate to sufficiently address all
new program requirements imposed by the recent PIRT amendments to the General
SDC-0055-034-ST-300312/13/93 7?
-------
Basic Training Permit Compliance System (PCS)
Pretreatment Regulations. Valid options include:
Y Yes
N No
RECR [REMOVAL CREDITS] (field length = 1 character)
This field indicates the status of the application for removal credit for the Pretreatment
Control Authority. Valid options include:
A Approved
D Denied
N Not applicable
P Pending
RCRD [REMOVAL CREDITS APPROVAL DATE] (field length = 5 characters)
This field indicates the date the application for removal credits was approved.
RSCH (field length = 1 character)
[RESPONSE TO SCHEDULE FOR REMEDIAL MEASURES]
This field indicates whether a formal enforcement action has been taken in response to a
violation of any schedule for implementation of needed remedial measures identified as a
result of audits or inspections. Valid options include:
Y Yes
N No
VSCH (field length = 1 character)
[VIOLATION TO SCHEDULE FOR REMEDIAL MEASURES]
This field indicates whether there has been a violation of any schedule issued by the
Pretreatment Control Authority for implementation of needed remedial measures identified as
a result of audits or inspections. Valid options include:
Y Yes
N No
74 12/13/93 5DC-0055-(M4-M-3UUJ
-------
Permit Compliance System (PCS) Basic Training
NINF (field length = 3 characters)
[NUMBER OF SIUS NOT SAMPLED OR INSPECTED AT REQUIRED
FREQUENCY]
This field represents the number of SIUs which were not sampled and/or inspected by the
Pretreatment Control Authority at a frequency in accordance with the approved pretreatment
program or NPDES permit.
EVCL (field length = 1 character)
[TECHNICAL EVALUATION FOR COMPREHENSIVE LOCAL LIMITS]
This field indicates whether the Pretreatment Control Authority technically evaluated the need
for, and adopted as necessary, local limits to address toxicity concerns, sludge criteria, and
pollutants specifically designated by the Pretreatment Approval Authority. Valid options for
this field include:
Y Yes
N No
NOPT (field length = 3 characters)
[% OF SIUS WHICH HAVE NOT INSTALLED REQUIRED PRETREATMENT]
This field indicates the approximate percentage of SIUs which have failed to install
pretreatment technologies to meet applicable pretreatment standards, although required to do
so. The number entered represents a percentage, not a count. The percentage is entered as
a whole number. The system will not allow a decimal point or a percentage sign to be
entered.
PRCH [PROGRAM ELEMENT CHANGES] (field length = 6 characters)
This field indicates what program elements were changed without approval since the last PCI
or follow-up. Valid codes can be found in TABLE 560 in the PCS Codes and Descriptions
Manual. Valid options include:
A Legal authority
C Control mechanism implementation
E Enforcement program
I Inspection/monitoring program
L Local limits
R Resources
St>C-0055-034-ST-3003 12713733 75
-------
Basic Training Permit Compliance System (PCS)
SUPP [SUMMARY REPORT] (field length = 1 character)
This is a one-character 'Y'es/'N'o field indicating whether the PCI generally supports
statements made by the Pretreatment Control Authority in the most recent report.
RDN1 [REGIONAL FIELD 1] (field length = 3 characters)
RDN2 [REGIONAL FIELD 2] (field length = 6 characters)
These two fields and their use are user defined.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
76 12/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
2.7.4 SUN Sludge Inspection Data Screen
The following PCS-ADE screen is used to enter information for the sludge inspection record.
Sludge Inspection Data Screen
11jOO:59 SLUDGE INSPECTION DATA
07/18/91 SCREEN ID: SLIN
PERMIT * (NPIDJ TRANS CODE C
INSPECTION DATE _
TOTAL * SLUDGE VIOLATIONS:
INCINERATOR CSLVI) LAND APPLICATION (SLVL)
DIST/KKTG (SLVD) SURFACE DISPOSAL (SLVS)
CO-DISPOSAL CSLCD) MGT PRACTICES (SLVP)
OTHER (SLOT)
SLUDGE-RELATED COMMENT 1 (SLID
SLUDGE-RELATED COMMENT 2 (SLI2)
SLUDGE-RELATED COMMENT 3 (SLI3)
ACCEPT? Y/K/N/M: _ VERSION 1.0 07/18/91
NPID*! [PERMIT #] (field length = 9 characters)
This field is both a WENDB data element and a Key data element.
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
DTIN! [INSPECTION DATE] (field length = 6 characters)
This field is a Key data element. It indicates the date the inspection was conducted.
SDCTXJ55-034-ST-3003 12/13/93 77
-------
Basic Training Permit Compliance System (PCS)
TYPI! [INSPECTION TYPE] (field length = 1 character)
This field is a key data element. It indicates the type of inspection that was conducted.
Examples of the codes are listed below. A complete listing of Inspection Type codes can be
found in TABLE 280 in the PCS Codes and Descriptions Manual.
C Compliance evaluation
S Compliance sampling
X Toxic
[TOTAL # SLUDGE VIOLATIONS]
SLVI [INCINERATOR] (field length = 3 characters)
This field contains the total number of quality limit violations detected at the
INCINERATOR.
SLVL [LAND APPLICATION] (field length = 3 characters)
This field contains the total number of LAND APPLICATION site sludge quality limit
violations detected.
SLVD [DIST/MKTG] (field length = 3 characters)
This field contains the total number of DISTRIBUTION/MARKETING sludge quality limits
violations detected.
SLVS [SURFACE DISPOSAL] (field length = 3 characters)
This field contains the total number of SURFACE DISPOSAL sludge quality limit violations
detected.
SLCD [CO-DISPOSAL] (field length = 3 characters)
This field contains the total number of CO-DISPOSAL sludge quality limit violations
detected.
SLVP [MGT PRACTICES] (field length = 3 characters)
This field contains the total number of MANAGEMENT PRACTICES sludge quality limit
violations detected.
78 12/13/93 SDC-0055-034-ST-3UU3
-------
Permit Compliance System (PCS) Basic Training
SLOT [OTHER] (field length = 3 characters)
This field contains the total number of OTHER sludge quality limit violations detected.
SLI1 [SLUDGE-RELATED COMMENT 1] (field length=30 characters)
SLI2 [SLUDGE-RELATED COMMENT 2] (field length=30 characters)
SLB [SLUDGE-RELATED COMMENT 3] (field length=30 characters)
These fields are used for any additional information to be tracked in the system concerning
sludge inspections. Any additional descriptive information can be entered.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
SDC-0055-O34-ST-3003 12/13/93 79
-------
Basic Training Permit Compliance System (PCS)
2.8 Pipe Schedule Data Type
The Pipe Schedule record contains general information about the outfall of the discharge as a
whole, such as, 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 Effluent Menu is used to reach Outfall related
screens.
Effluent Menu
11/14/92 PCS-ADE Data Entry Subsystem PCDENENU
11:00:58 Effluent Menu
Enter screen ID or 'X' to select an option
Screen ID:
OFLG
OFLT
OFGD
SLPS
LI US
LINN
SEAN
EDNR
EVIO
EXIT
Outfall General Data
Outfall Treatment Type/Coonents
Outfall Geographic Data
Sludge outfall
Limits
Limit Notifications
Seasonal Limit Split
Effluent DNR Data
Effluent Measurements/Violations
Return to Nain Menu
-------
Permit Compliance System (PCS) Basic Training
The following PCS-ADE screens are used to enter the data for the Pipe Schedule record.
2.8.1 OFLG Outfall Screen
Outfall Screen
11:29:08 OUTFALL PCDEOFLG
11/23/92 SCREEN ID: OFLG
PERMIT * (NMD) TRANS CODE
DISCHARGE NUMBER REPORT DESIGNATOR (DRID) _
INITIAL REPORT DATE (STRP) REPORT UNITS (REUN) OUTFALL TYPE (OUTT)
NUMBER OF UNITS IN REPORT PERIOD (NRPU) TOTAL NUMBER OF REPORTS DUE (NORP>
INITIAL EPA SUBMISSION DATE (STSU) EPA SUBMISSION UNIT (SUUN)
NUMBER OF UNITS IN EPA SUBMISSION PERIOD (NSUN) _
INITIAL STATE SUBMISSION DATE (STSS) STATE SUBMISSION UNIT (SUUS)
NUMBER OF UNITS IN STATE SUBMISSION PERIOD (NSUS) _
PIPE DESCRIPTION (PIPE)
SEASONAL DMR PRINTING INDICATORS (ALIP)
INITIAL LIMIT DATES: START (ILSD) END (ILED)
INTERIM LIMIT DATES: START (MLSO) END (MLED)
FINAL LIMIT DATES: START (FLSD) END (FLED)
TYPE EFFLUENT WASTE (UAST) AGENCY REVIEWER MIN # OF DMR LINES _
PIPE INACTIVE CODE (PIAC) _ PIPE INACTIVE DATE (PIDT)
ACCEPT? Y/K/N/M: Y OFLT DATA? N SLUDGE DATA? N VERSION 2.2 01/14/92
*Note: On-line screen does not contain acronyms.
Pipe Schedule Data Type (PS) - Screen/Acronym/Field Descriptions
NPID*! [PERMIT #] (field length = 9 characters)
This field is both a WENDB data element and a Key data element.
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
SDC-0055-034-ST-3CX)3 12/13/93 81
-------
Basic Training Permit Compliance System (PCS)
DSCH*! [DISCHARGE NUMBER] (field length = 3 characters)
This field is both a WENDB and a Key data element. The data for this field is found in the
final issued permit and is usually called the Outfall Serial Number.
DRID*! [REPORT DESIGNATOR] (Meld length - 1 character)
This Meld is both a WENDB and a Key data element. It is used to distinguish between more
than one set of conditions that apply to the same Outfall Serial Number.
DSDG! (field length = 4 characters)
[COMBINED DISCHARGE NUMBER AND DESIGNATOR]
This field is a Key data element that is system generated. The DISCHARGE NUMBER and
the REPORT DESIGNATOR combine to create this field. This field can be used for Inquiry
and Retrieval purposes.
STRP* [INITIAL REPORT DATE] (field length = 6 characters)
This field is a WENDB data element. The date entered must be the first day of month. The
DMR non-receipt tracking program uses this field to determine the beginning and end of the
monitoring period.
REUN* [REPORT UNITS] (field length = 1 character)
This field is a WENDB data element. The entry in this field must always be 'M'onthly.
OUTT [OUTFALL TYPE] (field length = 1 character)
This field identifies the type of pipe outfall being tracked. Valid codes can be found in
TABLE 780 in the PCS Codes and Descriptions Manual. Valid options include:
Blank Default to Effluent
C Combined Sewer Overflow
I Influents
R Stormwater
S Sludge
T Stream
82 12/13/93 SDC-OU55-OJ4-&1-JUUJ
-------
Permit Compliance System (PCS) Basic Training
NRPU* (field length = 3 characters)
[NUMBER OF UNITS IN REPORT PERIOD]
This field is a WENDB data element. This field works in conjunction with the STRP field to
determine how many 30-day periods will be included in one monitoring period.
If the monitoring period is a monthly period, 001 is entered in this field.
If the monitoring period is a 60-day period, 002 is entered in this field.
If the monitoring period is a quarterly period, enter 003 in this field, etc.
NORP [TOTAL NUMBER OF REPORTS DUE] (field length = 3 characters)
This field indicates the number of sets of DMRs the permittee will send to the agency over
the lifetime of the permit. If the permittee must send in DMRs every month, and the permit
issuance is for 60 months, enter 060 in this field. If the permittee must send in DMRs on a
quarterly basis, and the permit issuance period is for 60 months, enter 020 in this field, etc.
STSU* [INITIAL EPA SUBMISSION DATE] (field length = 6 characters)
This field is a WENDB data element, if applicable. This is the date when the DMR has to
be postmarked as specified in the "Reporting of Monitoring Results" section in the
boilerplate of the permit. The date entered in this field must be after the completed
monitoring period. The system will use the fields STRP and NRPU to determine the
monitoring period. For example, if STRP is 010192 and NRPU is 001, the system will
determine the monitoring period is from 010192 to 013192, so the date in STSU must be
after 013192.
SUUN* [EPA SUBMISSION UNIT] (field length = 1 character)
This field is a WENDB data element, if applicable. The entry in this field must always be
'M'onthly.
NSUN* (field length = 2 characters)
[NUMBER OF UNITS IN EPA SUBMISSION PERIOD]
This field is a WENDB data element, if applicable. This field is how often the DMR has to
be submitted.
If the DMR is submitted every month, 01 is entered.
If the DMR is submitted every 2 months, 02 is entered.
If the DMR is submitted every 3 months, 03 is entered.
SDC-00&-034-ST-3M3 I57T3753 53
-------
Basic Training Permit Compliance System (PCS)
STSS* [INITIAL STATE SUBMISSION DATE] (field length = 6 characters)
This field is a WENDB data element, if applicable. This is the date when the DMR has to
be postmarked as specified in the "Reporting of Monitoring Results" section in the
boilerplate of the permit. The date entered in this field must be after the completed
monitoring period. The system will use the fields STRP and NRPU to determine the
monitoring period. For example, if STRP is 010192 and NRPU is 001, the system will
determine the monitoring period is from 010192 to 013192, so the date in STSU must be
after 013192.
SUUS* [STATE SUBMISSION UNIT] (field length = 1 character)
This field is a WENDB data element, if applicable. The entry in this field must always be
M'onthly.
NSUS (field length = 2 characters)
[NUMBER OF UNITS IN STATE SUBMISSION PERIOD]
This field is a WENDB data element, if applicable. This field is how often the DMR has to
be submitted.
If the DMR is submitted every month, 01 is entered.
If the DMR is submitted every 2 months, 02 is entered.
If the DMR is submitted every 3 months, 03 is entered.
PIPE [PD7E DESCRIPTION] (field length=25 characters)
This field is a description of the outfall or any special conditions at the outfall. It prints in
the upper right-hand corner on the pre-printed DMR form.
ALLP* (field length=12 characters)
[SEASONAL DMR PRINTING INDICATORS]
This field is a WENDB data element. It identifies which months the outfall will be
discharging. This is a 12-character field and each character will accept either a 'Y', to show
there is a discharge, or 4N*, to show there is not a discharge. If this field is left blank, the
system, will generate 12 'Y' responses to show that outfall is discharging every month.
ILSD* [INITIAL LIMITS DATES: START] (field length = 6 characters)
ILED* [INITIAL LIMITS DATES: END] (field length = 6 characters)
84 12/13/93 SDCHXJ55-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
These fields are WENDB data elements, if the permit has initial limits.
MLSD* [INTERIM LIMITS DATES: START] (field length = 6 characters)
MLED* [INTERIM LIMITS DATES: END] (field length = 6 characters)
These fields are WENDB data elements, if the permit has interim limits.
FLSD* [FINAL LIMITS DATES: START] (field length = 6 characters)
FLED* [FINAL LIMITS DATES: END] (field length = 6 characters)
These fields are WENDB data elements, if the permit has final limits.
* NOTE: The pipe schedule record MUST contain at least one set of limits dates but can
contain more than one set, as long as the end date does not overlap the start
date of the previous set of limits.
WAST [TYPE EFFLUENT WASTE] (field length = 2 characters)
This field represents the type of effluent being discharged through this outfall. A complete
list of effluent waste types can be found in TABLE 220 in the PCS Codes and Descriptions
Manual.
AGYR [AGENCY REVIEWER] (field length = 5 characters)
This field is for the name or initials of the person responsible for reviewing the permit.
MDML [MEV # OF DMR LINES] (field length = 2 characters)
This field will create extra blank lines when pre-printing DMRs. A DMR contains seven
parameters on one sheet. If more than seven lines are needed, enter a number greater than
seven and an extra blank DMR will be printed.
PIAC [PIPE INACTIVE CODE] (field length = 1 character)
This field is a WENDB data element. If there is no entry in this field, the system defaults to
'A' for active. An entry of T on this field will inactivate only this discharge number and
report designator.
PIDT [PIPE INACTIVE DATE] (field length = 6 characters)
This field is a WENDB data element, only if PIAC is T.
SDC-0055-034-ST-3003 12/13/93 J»
-------
Basic Training Permit Compliance System (PCS)
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
[SLUDGE DATA? Y/N] (field length = 1 character)
Indicate:
Y (Yes) to continue to the SLPS screen.
N (No) will not continue to the SLPS screen.
So 12/13/93 SDC-0055-O34-al-3OU3
-------
Permit Compliance System (PCS)
Basic Training
2.8.2 OFLT Outfall Treatment Type Screen
Outfall Treatment Type Screen
11:2»:49
11/33/93
VOMIT t (HMD)
OUTPAXJ. TKMT TYFB
DISCHARGE NUMBER (MOO
TRASS COM C
UPORT DBSIOKUOR
OOTPJUX. XRBXDOrr TTFB CODES
CMR FORM OOMMBHX8
(PIC1)
(PICS)
(PICS)
(PIC7 )
(PIC9)
(pica).
(PIC4)_
(PIC6).
(pica)
OSKB DATA BLBKBMT f 1
OSBX OKTA BLBNBHT
PCDBOPLT
8CRBBR ZDl OPLT
VBR9IOW 2.1 03/13/90
*Note: On-line screen does not contain acronyms.
Pipe Schedule Data Tvne (PS) - Screen/Acronym/Field Descriptions
NPID*! [PERMIT #] (field length = 9 characters)
This field is both a WENDB data element and a Key data element.
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
DSCH*! [DISCHARGE NUMBER] (field length = 4 characters)
This field is both a WENDB and a Key data element. The data for this field is found in the
final issued permit and is usually called the Outfall Serial Number.
-------
Basic Training Permit Compliance System (PCS)
DRID*! [REPORT DESIGNATOR] (field length = 1 character)
This field is both a WENDB and a Key data element. It is used to distinguish between more
than one set of limits that apply to the same Outfall Serial Number.
TRET [OUTFALL TREATMENT TYPE CODES] (field length=24 characters)
This field identifies the type of treatment used at this outfall. A complete list of treatment
types can be found in TABLE 190 in the PCS Codes and Descriptions Manual.
PICM [DMR FORM COMMENTS] (9 fields of 30 characters each)
These fields are for any comments concerning this outfall. Any comments entered here will
print on the bottom of the DMR.
RDP1 [USER DATA ELEMENT #1] (field length = 3 characters)
RDP2 [USER DATA ELEMENT #2] (field length = 3 characters)
These are user defined fields. Check with the Regional PCS Coordinator for their use.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
12/13/93 SOC-OOSS-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
2.8.3 OFGD Outfall Geographic Data Type
This screen is used to enter Outfall Geographic Data information. The TRANS CODE is a
'C' that is hard-coded and cannot be changed.
Outfall Geographic Data Screen
f3t16:48.3 OUTFALL GEOGRAPHIC DATA PCOEOFGD
08/30/93 SCREEN ID: OFGD
PERMIT * . TRAMS CODE C
DISCHARGE NUMBER REPORT DESIGNATOR _
LATITUDE LONGITUDE CPLON)
LAT/LONG CODE OF ACCURACY (PLLC) _
tAT/LONG METHOD (PLLM) LAT/LONG DatUB
REACH NUMBER:
USGS NYDROLOGIC BASIN CODE (PHBO STREAM SEGMENT (PSEG)
MILEAGE INDICATOR (PMLG)
RECEIVING STREAM CLASSIFICATION CODE (PRSC) _
ACCEPT? Y/N/M: Y VERSION 2.2 01/11/93
PLAT* [PIPE: LATITUDE] (field length = 8 characters)
This field is a WENDB data element. It indicates the latitude of this outfall. It is entered as
follows:
Character 1 + Northern Hemisphere
- Southern Hemisphere
Characters 2 and 3 Degrees
Characters 4 and 5 Minutes
Characters 6 and 7 Seconds
Character 8 Tenths of a second
12713753 55
-------
Basic Training Permit Compliance System (PCS)
PLON* [PIPE: LONGITUDE] (field length = 9 characters)
This field is a WENDB data element. It indicates the longitude of this outfall. It is entered
as follows:
Character 1 + Eastern Hemisphere
- Western Hemisphere
Characters 2, 3 and 4 Degrees
Characters 5 and 6 Minutes
Characters 7 and 8 Seconds
Character 9 Tenths of a second
PLLC* [LAT/LONG ACCURACY] (field length = 1 character)
This field is a WENDB data element. It describes the technical accuracy of the
Latitude/Longitude data. It must be a valid number 1 through 8. Valid options include:
1 nearest 10th of a second
2 nearest second
3 nearest 10 seconds
4 nearest 30 seconds
5 nearest minute
6 nearest 10 minutes
7 nearest 30 minutes
8 nearest degree
PLLM* [LAT/LONG METHOD] (field length = 1 character)
This field is a WENDB data element. It indicates the method used to measure LATITUDE
and LONGITUDE coordinates. LATITUDE and LONGITUDE must be entered before data
can be entered into this field. The codes for this field are contained in TABLE 471 in the
PCS Codes and Descriptions Manual.
PLLT* [LAT/LONG DATUM] (field length = 1 character)
This field is a WENDB data element. It represents a network of reference points from
which geographic computations can be made. LATITUDE and LONGITUDE must be
entered before data can be entered into this field. The codes for this field are contained in
TABLE 472 in the PCS Codes and Descriptions Manual.
50 13713753
-------
Permit Compliance System (PCS) Basic Training
PLLS* [LAT/LONG SCALE] (field length = 1 character)
This field is a WENDB data element. It represents the scale of source map used to
determine LATITUDE and LONGITUDE. LATITUDE and LONGITUDE must be entered
before data can be entered into this field. The codes for this field are contained in TABLE
473 in the PCS Codes and Descriptions Manual.
PLLD* [LAT/LONG DESCRIPTION] (field length = 5 characters)
This field is a WENDB data element. It represents precisely to what the LATITUDE and
LONGITUDE refer. LATITUDE and LONGITUDE must be entered before data can be
entered into this field. The codes for this field are contained in TABLE 475 in the PCS
Codes and Descriptions Manual.
PHBC [USGS HYDROLOGIC BASIN CODE] (field length = 8 characters)
This field represents a code assigned by the United States Geological Survey to identify
drainage water basins for outfalls by their geographical location. It is also referred to as
Cataloging Unit and as HUC by frequent users of Reach information. The codes for this
field are contained in TABLE 800 in the PCS Codes and Descriptions Manual.
PSEG [SCHEDULE STREAM SEGMENT] (field length = 4 characters)
This field represents a code used to identify pieces of water from one significant event to
another, where significant event represents the mouth of a body of water, the confluence of
two streams, etc. The codes for this field are contained in TABLE 804 in the PCS Codes
and Descriptions Manual.
PMLG [MILEAGE INDICATOR] (field length = 5 characters)
This field represents the length of a particular outfall stream segment in miles downstream
from the beginning of the stream segment. The codes for this field are contained in TABLE
804 in the PCS Codes and Descriptions Manual.
PRSC [RECEIVING STREAM CLASSIFICATION CODE] (field length = 2 characters)
This field describes the related outfall segment type. The codes for this field are contained
in TABLE 805 in the PCS Codes and Descriptions Manual.
$bC-M55-034-ST-3003 12/13/93
-------
Basic Training
Permit Compliance System (PCS)
2.8.4 SLPS Sludge Outfall Data
This screen is used to enter information about a sludge outfall. The TRANS CODE is a 'C'
that is hard-coded and cannot be changed.
Sludge Outfall Data Screen
11tOO:S9
07/18/91
PERMIT f eNPID)
SLUDGE OUTFAU DATA
PCDESLPS
SCREEN ID: SLPS
DISCHARGE KUKBER (DSCH)
TRANS CODE: C
REPORT DESIGNATOR CDRID)
OUTFALL TYPE (OUTT) S
SLUDGE USE OPTION (SLTP) _
LAND REUSE OPTION (SLLR) _
CROP CLASS (SLCC) _
CROP TYPE
-------
Permit Compliance System (PCS) Basic Training
DRTO*! [REPORT DESIGNATOR] (field length = 1 character)
This field is both a WENDB and a Key data element. It is used to distinguish between more
than one set of limits that apply to the same Outfall Serial Number.
OUTT [OUTFALL TYPE] (field length = 1 character)
This field identifies the type of pipe outfall being tracked. It is always hard-coded S for
Sludge.
SLTP [SLUDGE USE OPTION] (field length = 1 character)
This field is used to identify the type of reuse or disposal used by a facility for sludge
purposes. A complete list of Sludge Use Option codes can be found in TABLE 730 of the
PCS Codes and Descriptions Manual.
SLLR [LAND REUSE OPTION] (field length = 2 characters)
This field indicates the type of land reuse option for application of sewage sludge. A
complete list of Land Reuse Option codes can be found in TABLE 750 of the PCS Codes
and Descriptions Manual.
SLCC [CROP CLASS] (field length = 1 character)
This field indicates the type of crop grown on sludge amended fields. A complete list of
Crop Class codes can be found in TABLE 760 of the PCS Codes and Descriptions Manual.
SLCT [CROP TYPE] (field length = 2 characters)
This field is used to describe the type of crop grown on sludge amended fields. A complete
list of Crop Type codes can be found in TABLE 770 of the PCS Codes and Descriptions
Manual.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
SDC-0055-034-ST-3003 12/13/93 "~ 55
-------
Basic Training Permit Compliance System (PCS)
2.9 Parameter Limits Data Type
The information for this data type is found in the final permit along with the pipe schedule
information. The following are the PCS-ADE data entry screens used to enter the Parameter
Limit and Limit Modification information.
2.9.1 LTMS Effluent Limits Screen 1
Effluent limits Screen 1
Ill31>34 KF-Ulglff LOOTS PCDEUMS
11/33/92 SCRBBH IDl UXM8
FBJMXT {HFXD} ________ THAH8 CODE _
DXSdUMB OTMBBR (PUDS) REPORT DBSXQHATOR (PUD) _
UHXT T»B UTYF) PARMCBTKR (tRAM) MOHITORim LOCATIQM (MLOC) _ SBABOH _
~ <8BW>
PXBOUBHCX OF AHALXSX8 (FRAH) _____ SAMFL- TYPB tOMHf) UWlBaXBO PXRMOXBR (COHP> _
SBKBOHAL ENR PXIHTIBQ IIHJICMOM {ALLS) ___________ aXKMDMtO BASIS CODB (87BA) _
- - - QOMfTXTY LXMZT8 --- .... COHCBSTBATIOl! LZMITB ....
(LQOC) (LCOC) (LOOI) (LCAV) (LCMX)
OODB AVBRA8E MAZIMDM CHIT COOB MZHZMDM AVXRAOB MAXZKOX
- QUANTITY 8TAT BASE CODES - - COHCBHTRATIOM 8TAT BASE CODES -
-------
Permit Compliance System (PCS) Basic Training
PLDS*! [DISCHARGE NUMBER] (field length = 3 characters)
This field is both a WENDB data element and a Key data element. It is the discharge
number and must be the same as the DSCH field on the Pipe Schedule record.
PLRD*! [REPORT DESIGNATOR] (field length = 1 character)
This field is both a WENDB data element and a Key data element. It is the report designator
and must be the same as the DRED field on the Pipe Schedule record.
NOTE: For retrieval purposes, the following acronym and field can be used. It is a
combination of the DISCHARGE NUMBER and the REPORT DESIGNATOR.
PDSG! (field length = 4 characters)
[COMBINED DISCHARGE NUMBER AND DESIGNATOR]
System generated. This field is a Key data element. It is created by a combination of the
DISCHARGE NUMBER and REPORT DESIGNATOR fields. It can be used for Inquiry
and Retrieval purposes.
LTYP*! [LIMIT TYPE] (field length = 1 character)
This field is both a WENDB and a Key data element. This field must correspond to the
limits dates on the Pipe Schedule record. Valid codes can be found in TABLE 310 in the
PCS Codes and Descriptions Manual. Valid options include:
I Initial
M Interim
F Final
PRAM*! [PARAMETER] (field length = 5 characters)
This field is both a WENDB and a Key data element. It is the STORET Parameter code.
The valid codes for this field can be found in TABLE 160 in the PCS Codes and
Descriptions Manual.
Example:
00011 Temp degrees fahrenheit
00300 Dissolved Oxygen
00310 BOD
00400 pH
00530 TSS
St)C-003S-034-ST-3003 12713793 55
-------
Basic Training Permit Compliance System (PCS)
00610 Ammonia
50050 Flow
MLOC*! [MONITORING LOCATION] (field length = 1 character)
This field is both a WENDB and a Key data element. This code identifies the location where
the sample is to be taken from. The valid codes for this field can be found in TABLE 080 in
the PCS Codes and Descriptions Manual.
Example:
G Influent point
1 Effluent point
5 Upstream point
6 Downstream point
K % removal
SEAN*! [SEASON] (field length = 1 character)
This field is both a WENDB and a Key data element. This field represents whether a
parameter is sampled on a seasonal basis. The valid codes for this field are:
1 -9
A-Z
The code 0 represents that the parameter is sampled all year and is not seasonal.
FRAN [FREQUENCY OF ANALYSIS] (field length = 5 characters)
This field indicates the frequency in which the sample for this pollutant must be taken. A
complete list of frequency of analysis codes can be found in TABLE 050 in the PCS Codes
and Descriptions Manual.
Example:
01/01 daily
01/30 monthly
01/07 weekly
01/DS once per discharge
99/99 continuous
95 11713753 SDC-005^-Oi4-S I'-
-------
Permit Compliance System (PCS) Basic Training
SAMP [SAMPLE TYPE] (field length = 2 characters)
This field indicates the method to be used to collect the sample for this pollutant. A
complete list of sample types can be found in TABLE ISO in the PCS Codes and
Descriptions Manual.
Example:
GR grab
CP composite
24 24-hour composite
CN continuous
CONP* [CONTESTED PARAMETER] (field length = 1 character)
This field is a WENDB data element. This field indicates if a parameter has been contested
with an evidentiary hearing. Valid options for this field include:
blank not contested
X contested but still printed on dmr
Y contested but not printed on dmr
ALLS (field length=12 characters)
[SEASONAL DMR PRINTING INDICATORS]
This Meld indicates the months of the year this parameter is to be monitored. A 'Y' in an
individual seasonal indicator means that the parameter is to be monitored that month. An
'N' in the seasonal indicator means that the parameter is not to be monitored for that month.
If this field is left blank, the system will generate the same monitoring months as the ALLP
field on the Pipe Schedule record.
STBA [STANDARD BASIS CODE] (field length = 1 character)
This field indicates the type of technology used to calculate the limits in the permit.
LQUC* (field length = 2 characters)
[QUANTITY LIMITS: UNIT CODE]
This field is a WENDB data element. This field indicates the units of measurement that will
be used for the quantity portion of this parameter. A complete listing of unit codes can be
found in TABLE 161 in the PCS Codes and Descriptions Manual.
SDC-0055-034-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
Example:
01 kilograms per day
26 pounds per day
03 million gallons per day
08 gallons per day
LQAV* [QUANTITY LIMITS: AVERAGE] (field length = 8 characters)
This field is a WENDB data element. This field indicates the limit for the average quantity.
LQMX* [QUANTITY LIMITS: MAXIMUM] (field length = 8 characters)
This field is a WENDB data element. This field indicates the limit for the maximum
quantity.
LCUC* (field length = 2 characters)
[CONCENTRATION LIMITS: UNIT CODE]
This field is a WENDB data element. This field indicates the units of measurement that will
be used for the concentration portion of the parameter. A complete listing of unit codes can
be found in TABLE 161 in the PCS Codes and Descriptions Manual.
Example:
19 mg/1
28 ug/1
12 pH standard units
IS degrees fahrenheit
LCMN* (field length = 8 characters)
[CONCENTRATION LIMITS: MINIMUM]
This field is a WENDB data element. This field indicates the limit for the minimum
concentration.
LCAV* (field length = 8 characters)
[CONCENTRATION LIMITS: AVERAGE]
This field is a WENDB data element. This field indicates the limit for the average
concentration.
95 12713753
-------
Permit Compliance System (PCS) Basic Training
LCMX* (field length = 8 characters)
[CONCENTRATION LIMITS: MAXIMUM]
This field is a WENDB data element. This field indicates the limit for the maximum
concentration.
LQAS* (field length = 2 characters)
[QUANTITY AVERAGE: STATISTICAL BASE CODE]
This field is a WENDB data element. This field indicates the statistical base code for the
limit quantity average.
LQXS* (field length = 2 characters)
[QUANTITY MAXIMUM: STATISTICAL BASE CODE]
This field is a WENDB data element. This field indicates the statistical base code for the
limit quantity maximum.
LCMS* (field length = 2 characters)
[CONCENTRATION MINIMUM: STATISTICAL BASE CODE]
This field is a WENDB data element. This field indicates the statistical base code for the
limit concentration minimum.
LCAS* (field length = 2 characters)
[CONCENTRATION AVERAGE: STATISTICAL BASE CODE]
This field is a WENDB data element. This field indicates the statistical base code for the
limit concentration average.
LCXS* (field length = 2 characters)
[CONCENTRATION MAXIMUM: STATISTICAL BASE CODE]
This field is a WENDB data element. This field indicates the statistical base code for the
limit concentration maximum.
LCMO* (field length = 2 characters)
[CONCENTRATION MINIMUM OVERRIDE]
This field is a WENDB data element. This field indicates how the concentration minimum
measurement is compared to the concentration minimum limit. If a ' Y* is entered, a
violation will be recognized if the measurement is greater than the limit.
SbC-M$5-034-ST-3003 12713753 95
-------
Basic Training Permit Compliance System (PCS)
LCAO* (field length = 2 characters)
[CONCENTRATION AVERAGE OVERRIDE]
This field is a WENDB data element. This field indicates how the concentration average
measurement is compared to the concentration average limit. If a ' Y' is entered, a violation
will be recognized if the measurement is less than the limit. If left blank, a violation will be
calculated as a percentage over the limit.
PLFN* [DOCKET NUMBER] (field length=12 characters)
This field is a WENDB data element, if the original limit came from an enforcement action.
DMR1 [USER DATA ELEMENT #1] (field length = 1 character)
DMR2 [USER DATA ELEMENT #2] (field length = 6 characters)
DMR3 [USER DATA ELEMENT #3] (field length = 6 characters)
These are user defined fields. Check with the Regional PCS Coordinator for their use.
ACCEPT? Y/K/R/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
R (Retain) will accept all data on the screen but will not refresh the screen. Retains
everything on the screen so multiple screens with similar or the same characteristics
can be entered.
TBS I37I3753
-------
Permit Compliance System (PCS) Basic Training
2.9.2 LIMM Limit Modifications Screen 2
Limit Modifications Screen 2
Ill 32 si* LXNR MODXPICKTIOHS PCUBLIMi
11/23/93 SCHBEH XDt LUM
PERMIT f _ LIMITS 3TATOS
PRBQDEKCr OP AHAU3IS . SAMFLB TXPB COHTSSTED
(PlUUf) (SAMP) (CORP>
aSASOHAL DMR WUHTIHO XBDICATOXS
OOMITXTV LIMITS - - - .... COTCEHTHATIOH LIMITS
(I«AV) <_coc) (LCX») (uav)
UHTT CODE XVBMCE MAXIMOM ONZT CODS MUnWH AVBRAGB MAXDTOH
- gOMTITT STKT BA3B CODES - - - - CONCEHTRATIOH STMT BASE CODES - -
(LQAS) (LOXS) (LCM3) (LCA8) (LCZS)
&VSRAOS Munm Kumaw XVEBMSE M&XTMDM
MXH/AVO
OVERRIDES
*Note: On-line screen does not contain acronyms.
Parameter Limits Data Tvpe (PL) - Screen/Acronym/Field Descriptions
NPID*! [PERMIT #] (field length = 9 characters)
This field is both a WENDB data element and a Key data element.
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
PLDS*! [DISCHARGE NUMBER] (field length = 3 characters)
This field is both a WENDB data element and a Key data element. It is the discharge
number and must be the same as the DSCH field on the Pipe Schedule record.
SbC-MSS-OS^ST-SWB I37T3793 TOT
-------
Basic Training Permit Compliance System (PCS)
PLRD*! [REPORT DESIGNATOR] (field length = 1 character)
This field is both a WENDB data element and a Key data element. It is-the report designator
and must be the same as the DRID field on the Pipe Schedule record.
LTYP*! [LIMIT TYPE] (field length = 1 character)
This field is both a WENDB and a Key data element. Valid options for this field include:
I Initial
M Interim
F Final
PRAM*! [PARAMETER] (field length = 5 characters)
This field is both a WENDB and a Key data element. It is the STORET Parameter code.
The valid codes for this field can be found in TABLE 160 in the PCS Codes and
Descriptions Manual.
Example:
00011 Temp degrees Fahrenheit
00300 Dissolved Oxygen
00310 BOD
00400 pH
00530 TSS
00610 Ammonia
50050 Flow
MLOC*! [MONITORING LOCATION] (field length = 1 character)
This field is both a WENDB and a Key data element. This code identifies the location where
the sample is to be taken from. The valid codes for this field can be found in TABLE 080 in
the PCS Codes and Descriptions Manual.
Example:
G Influent point
1 Effluent point
5 Upstream point
6 Downstream point
K % removal
102 12/13/93 SDCHXJ55-O.34-bl-.JUlU
-------
Permit Compliance System (PCS) Basic Training
SEAN*! [SEASON] (field length = 1 character)
This field is both a WENDB and a Key data element. This field represents whether a
parameter is sampled on a seasonal basis. The valid codes for this field are:
1-9
A-Z
The code 0 represents that the parameter is sampled all year and is not seasonal.
MODN!* [MODIFICATION NUMBER] (field length = 1 character)
This field is both a WENDB and a Key data element. It does not appear on the LIMS
screen, but is generated by the system from the LIMS screen and is always the value zero
(0). The value entered on this screen must be numeric and must be the next highest value
than the last modification.
ELSD [MODIFICATION PERIOD:START] (field length = 6 characters)
This is the beginning date of the modification and the date the modification is effective, or
the date the enforcement action is signed.
ELED [MODOTCATION PERIOD:END] (field length = 6 characters)
This is the ending date of the modification and is the expiration date of the permit, the date
the modification expires or the date the permittee met all of the requirements of the
enforcement action and the enforcement action is officially closed.
STBA [STANDARD BASIS CODE] (field length = 1 character)
This field indicates the type of technology used to calculate the limits in the permit. If this
field is left blank, it will default to the value entered on the Limit record.
COLS* [LIMITS STATUS] (field length = 2 characters)
This field is a WENDB data element. If the modification is from an enforcement action, the
appropriate enforcement action code is entered in the first two characters of this field. The
enforcement action codes can be found in TABLE 030 in the PCS Codes and Descriptions
Manual.
SDC-00#-034-ST-3003 15715753 HJ3
-------
Basic Training Permit Compliance System (PCS)
FRAN [FREQUENCY OF ANALYSIS] (field length = 5 characters)
This Meld indicates the frequency in which the sample for this pollutant must be taken. A
complete list of frequency of analysis codes can be found in TABLE 050 in the PCS Codes
and Descriptions Manual. If this field is left blank, it will default to the value entered on the
Limit record.
Example:
01/01 Daily
01/30 Monthly
01/07 Weekly
01/DS Once per discharge
99/99 Continuous
SAMP [SAMPLE TYPE] (field length = 2 characters)
This field indicates the method to be used to collect the sample for this pollutant. A
complete list of sample types can be found in TABLE ISO in the PCS Codes and
Descriptions Manual. If this field is left blank, it will default to the value entered on the
Limit record.
Example:
GR Grab
CP Composite
24 24-hour composite
CN Continuous
CONP* [CONTESTED PARAMETER] (Field length = 1 character)
This field is a WENDB data element. This field indicates if a parameter has been contested
with an evidentiary hearing. The codes for this field are contained in TABLE 450 in the
PCS Codes and Descriptions Manual. Valid options for this field include:
blank Not contested
X Contested but still printed on DMR
Y Contested but not printed on DMR
ALLS (field length=12 characters)
[SEASONAL DMR PRINTING INDICATORS]
This field indicates the months of the year this parameter is to be monitored. A 'Y' in an
individual seasonal indicator means that the parameter is to be monitored that month. An
TU5 12/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
*N' in the seasonal indicator means that the parameter is not to be monitored for that month.
If this field is left blank, the system will generate the same monitoring months as the ALLP
field on the Pipe Schedule record.
LQUC* (field length = 2 characters)
[QUANTITY LJMrrS:UNIT CODE]
This field is a WENDB data element. This field indicates the units of measurement that will
be used for the quantity portion of this parameter. A complete listing of unit codes can be
found in TABLE 161 in the PCS Codes and Descriptions Manual.
Example:
01 Kilograms per day
26 Pounds per day
03 Million gallons per day
08 Gallons per day
LQAV* [QUANTITY UMITS:AVERAGE] (field length = 8 characters)
This field is a WENDB data element. This field indicates the limit for the average quantity.
LQMX* [QUANTITY UMTTS:MAXIMUM] (field length = 8 characters)
This field is a WENDB data element. This field indicates the limit for the maximum
quantity.
LCUC* (field length = 2 characters)
[CONCENTRATION LEVnTS:UNIT CODE]
This field is a WENDB data element. This field indicates the units of measurement that will
be used for the concentration portion of the parameter. A complete listing of unit codes can
be found in TABLE 161 in the PCS Codes and Descriptions Manual.
Example:
19 Mg/1
28 Ug/1
12 pH standard units
15 Degrees fahrenheit
SDC-W55-034^STX5003 12/13/93 105
-------
Basic Training Permit Compliance System (PCS)
LCMN* (field length = 8 characters)
[CONCENTRATION LEVflTS:MINIMUM]
This field is a WENDB data element. This field indicates the limit for the minimum
concentration.
LCAV* (field length = 8 characters)
[CONCENTRATION UMTTSrAVERAGE]
This field is a WENDB data element. This field indicates the limit for the average
concentration.
LCMX* (field length = 8 characters)
[CONCENTRATION LEVHTStMAXIMUM]
This field is a WENDB data element. This field indicates the limit for the maximum
concentration.
LQAS* (field length = 2 characters)
[QUANTITY AVERAGErSTATISTICAL BASE CODE]
This field is a WENDB data element. This field indicates the statistical base code for the
limit quantity average.
LQXS* (field length = 2 characters)
[QUANTITY MAXIMUMrSTATISTICAL BASE CODE]
This field is a WENDB data element. This field indicates the statistical base code for the
limit quantity maximum.
LCMS* (field length = 2 characters)
[CONCENTRATION MINIMUM:STATISTICAL BASE CODE]
This field is a WENDB data element. This field indicates the statistical base code for the
limit concentration minimum.
LCAS* (field length = 2 characters)
[CONCENTRATION AVERAGE:STATISTTCAL BASE CODE]
This field is a WENDB data element. This field indicates the statistical base code for the
limit concentration average.
106 12/13/93 SDC-0055-034-il-3UUJ
-------
Permit Compliance System (PCS) Basic Training
LCXS* (field length = 2 characters)
[CONCENTRATION MAXIMUM:STATISTTCAL BASE CODE]
This field is a WENDB data element. This field indicates the statistical base code for the
limit concentration maximum.
LCMO* (field length = 2 characters)
[CONCENTRATION MINIMUM OVERRIDE]
This field is a WENDB data element. This field indicates how the concentration minimum
measurement is compared to the concentration minimum limit. A violation will be
recognized if the measurement is greater than the limit.
LCAO* (Meld length = 2 characters)
[CONCENTRATION AVERAGE OVERRIDE]
This field is a WENDB data element. This field indicates how the concentration average
measurement is compared to the concentration average limit. A violation will be recognized
if the measurement is less than the limit.
PLFN* [DOCKET NUMBER] (field length =12 characters)
This field is a WENDB data element, if the original limit came from an enforcement action.
The data entered should always be either left-justified or right-justified. It is the user's
choice and the user should always remain consistent when entering docket numbers.
DMR1 [USER DATA ELEMENT #1] (field length = 1 character)
DMR2 [USER DATA ELEMENT #2] (field length = 6 characters)
DMR3 [USER DATA ELEMENT #3] (Meld length = 6 characters)
These are user defined fields. Check with the Regional PCS Coordinator for their use.
ACCEPT? Y/K/R/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
SDC-0055-034-ST-3003 12/13/93 1U7
-------
Basic Training Permit Compliance System (PCS)
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
R (Retain) will accept all data on the screen but will not refresh the'screen. Retains
everything on the screen so multiple screens with similar or the same characteristics
can be entered.
108 12/13/93 SDC-O055-Q34-iI-JUU3
-------
Permit Compliance System (PCS) Basic Training
2.9.3 SEAN Seasonal Limits Split Screen
Seasonal Limits Split Screen
This screen is used to enter seasonal differences on limits that are currently non-seasonal.
11:32:46 SEASONAL LIMITS SPLIT PCDESEAN
11/23/92 SCREEN ID: SEAN
PERMIT # _______ TRANS CODE N
DISCHARGE NUMBER (PLOS) DISCHARGE TYPE (PLRD) _
LINIT TYPE CLTYP* PARAMETER CODE
-------
Basic Training Permit Compliance System (PCS)
PLRD [DISCHARGE TYPE] (field length = 1 character)
This field contains a one digit number assigned for each point of discharge. It links a limit
to a pipe schedule.
LTYP [LIMIT TYPE] (field length = 1 character)
This field is used to limit the period during which a specific parameter limit applies. It
relates limits to the pertinent set of dates appearing on the corresponding Pipe Schedule
record.
PRAM*! [PARAMETER CODE] (field length = 5 characters)
This field is both a WENDB and a Key data element. It is the STORET Parameter code.
The valid codes for this field can be found in TABLE 160 in the PCS Codes and
Descriptions Manual.
Example:
00011 Temp degrees fahrenheit
00300 Dissolved Oxygen
00310 BOD
00400 pH
00530 TSS
00610 Ammonia
50050 Flow
MLOC*! [MONITORING LOCATION] (field length = 1 character)
This field is both a WENDB and a Key data element. This code identifies the location where
the sample is to be taken from. The valid codes for this field can be found in TABLE 080 in
the PCS Codes and Descriptions Manual.
Example:
G Influent point
1 Effluent point
5 Upstream point
6 Downstream point
K % removal
TTO 15713753
-------
Permit Compliance System (PCS) Basic Training
SEAN*! [SEASON] (field length = 1 character)
This field is both a WENDB and a Key data element. This field represents whether a
parameter is sampled on a seasonal basis. The valid codes for this field are:
1 -9
A-Z
The code 0 represents that the parameter is sampled all year and is not seasonal.
SEASONAL SPLIT DATA ELEMENTS
NSEN [NEW SEASON NUMBER 1 - 12] (field length = 1 character)
This field is used to indicate one of the seasons that are created as a result of the season
split. It is associated with the ALLS field.
ALLS (field length = 12 characters)
[SEASONAL DMR PRINTING INDICATORS]
This field indicates the months of the year this parameter is to be monitored. A ' Y' in an
individual seasonal indicator means that the parameter is to be monitored that month. An
'N' in the seasonal indicator means that the parameter is not to be monitored for that month.
For seasonal limit splits, the ALLS must be completed for every new season number.
ACCEPT? Y/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
$t>C-0055-034-ST-3003 12/13/93TTT
-------
Basic Training Permit Compliance System (PCS)
2.10 Measurement Violation Data Type
The information for this data type comes from the Discharge Monitoring Reports (DMRs)
that the permittee must complete and send to the regulatory agency. The following are the
PCS-ADE data entry screens used to enter the Measurement records.
2.10.1 EDMR Key Screen
Affluent DMR Data Key Screen 1
SCSSW ID: BOHR
FCS-ADB
BFPLOBHT CMR OUA
JCBY SCHBBH
PBKMZT __________
TOWS CODE _
DiaCHUOB BOMBER (VDSC>
KBPORT DK3IGHATOH (VDRD) _
UfflOB OIBCKZH67 (Y/H) _
HANGB TABLE IDj
USB HKriORM. OBHULT TABLE? (X/H) _
BCCBFI7 Z/B/M: T
*Note: On-line screen does not contain acronyms.
Effluent DMR Data Type (MV) - Screen/Acronym/Fleld Descriptions
NPID*! [PERMIT #1 (field length = 9 characters)
This field is both a WENDB data element and a Key data element.
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
TT3 12/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Rasic Training
VDSC*! [DISCHARGE NUMBER] (field length = 3 characters)
This field is both a WENDB and a Key data element. This is the number associated with
this discharge. It must be the same as the DSCH field on the Pipe Schedule record.
VDRD*! [REPORT DESIGNATOR] (field length = 1 character)
This field is both a WENDB and a Key data element. The entry signifies the report
designator. It must be the same as the DRID field on the Pipe Schedule record.
NOTE: For retrieval purposes, the following acronym and field can be used. It is a
combination of the DISCHARGE NUMBER and the REPORT DESIGNATOR.
[RANGE CHECKING (Y/N)] (field length = 1 character)
The valid responses to this field are:
Y Yes will allow the user to use the range checking table.
N No will not allow the user to perform range checking.
[RANGE TABLE ID] (field length = 5 characters)
The Range Table ID is entered in this field. Contact the Regional or State PCS Coordinator
for Range Table IDs.
[USE NATIONAL DEFAULT TABLE? (Y/N)] (field length = 1 character)
The valid responses to this field are:
Y Yes, if the National Default Table is to be used.
N No, if the National Default Table is not to be used.
ACCEPT? Y/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
SbC-M5$-034-ST-3003 12/13/93 TT5
-------
Basic Training Permit Compliance System (PCS)
2.10.2 EDMR Screen 2
Effluent DMR Data Screen 2
«**««»* >"
PEWIIT * (NPID) TRAMS CODE _ EFFLUENT ONR DATA SCREEN 10: EDMR
DISCHARGE NUMBER CVDSC) , REPORT DESIGNATOR
-------
Permit Compliance System (PCS) Basic Training
NODI* (field length = 1 character)
[PIPE NO DATA REASON CODE]
This field is a WENDB data element, if applicable. It represents the reason why there was
no discharge for an entire pipe. The concept of a pipe NODI applies to data entry only.
Parameter NODI records will be generated, stored, and modified on the data base for each
limit when a pipe level NODI transaction is entered.
There are seven lines for data entry for each of the fields described below.
VPRM!* [PARAMETER CODE] (field length = 5 characters)
This field is a Key data element. It is the STORET Parameter Code.
VMLO! [MONITORING LOCATION CODE] (field length = 1 character)
This field is both a WENDB and a Key data element. It represents the monitoring location
of the parameter.
MQAV* (field length = 8 characters)
[MEASUREMENTS: QUANTITY: AVERAGE]
This field is a WENDB data element, if applicable. If the permittee reported a value in the
QUANTITY AVERAGE section on the DMR, enter that number in this field.
MQMX* (field length = 8 characters)
[MEASUREMENTS: QUANTITY: MAXIMUM]
This field is a WENDB data element, if applicable. If the permittee reported a value in the
QUANTITY MAXIMUM section on the DMR, enter that number here.
MCMN* (field length = 8 characters)
[MEASUREMENTS: CONCENTRATION: MINIMUM]
This field is a WENDB data element, if applicable. If the permittee reported a value in the
CONCENTRATION MINIMUM section on the DMR, enter that number here.
MCAV* (field length = 8 characters)
[MEASUREMENTS: CONCENTRATION: AVERAGE]
This field is a WENDB data element, if applicable. If the permittee reported a value in the
CONCENTRATION AVERAGE section on the DMR, enter that number here.
SDC-M5S-034-ST-3003 12713733 TB
-------
Basic Training _ Permit Compliance System (PCS)
MCMX* (^eld length = 8 characters)
[MEASUREMENTS: CONCENTRATION: MAXIMUM]
This field is a WENDB data element, if applicable. If the permittee reported a value in the
CONCENTRATION MAXIMUM section on the DMR, enter that number here.
REXC [REPORTED # OF EXCURSIONS] (field length = 2 characters)
This field represents the number of excursions reported on the DMR form.
RFRQ (field length = 5 characters)
[REPORTED FREQUENCY OF ANALYSIS]
This field represents the frequency of analysis used by the permittee and requested on the
DMR form.
RSAM [REPORTED SAMPLE TYPE] (field length = 2 characters)
This field represents the sample type used by the permittee and reported on the DMR form.
(field length = 2 characters)
[REPORTED QUANTITY UNIT CODE]
This field represents the unit of measurement used by the permittee when the sample was
taken. Data is entered in this field only when the reported unit of measurement is different
from the unit of measurement on the limit record.
RCUN (field length = 2 characters)
[REPORTED CONCENTRATION UNIT CODE]
This field represents the unit of measurement used by the permittee when the sample was
taken. Data is entered in this field only when the reported unit of measurement is different
from the unit of measurement on the limit record.
REXC [REPORTED # OF EXCURSIONS] (field length = 2 characters)
This field represents the number of times a limit was exceeded, as reported on the DMR
form.
R7T3753
-------
Permit Compliance System (PCS) Basic Training
NODI* [NO DISCHARGE REASON CODE] (field length = 1 character)
This field is a WENDB data element, if applicable. It represents the reason why this
parameter was not discharged.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
P Accepts data entered and keeps everything.
$bC-M$$-034-ST-3M3 12/13/93 TT7
-------
Basic Training Permit Compliance System (PCS)
2.10.3 EVIO Key Screen
Effluent Measurements Key Screen
11/23/93 PCS-ABB
11:3406 BPPLOE8T KBASOHBHRHTS SCREEN ZDt BVIO
KBY SCRBER
PERMIT f: (HFZO} THARS OODBi _
MDRXTOBXRQ PERIOD EHD DATS* (MVDT)
DO TOO WISH TO 08B THE CYCUS OPTZOH? _
DO YOB WISH TO CYCLE THROUGH 'PREVIOUS' LIMITS? (Y/H) R
DISCHARGE BOMBER: (VDSC)
REPORT DESIOOaOR:
-------
Permit Compliance System (PCS) Basic Training
DO YOU WISH TO CYCLE THROUGH (field length = 1 character)
'PREVIOUS' LIMITS? (Y/N)
In PCS previous limits are called "ghosted limits". The valid options for this field include:
Y Yes
N No
MVDT*! [MONITORING PERIOD END DATE] (field length = 6 characters)
This field is both a WENDB and a Key data element. This date comes from the Monitoring
Period End Date on the DMR and should be the last day of the month.
VDSC*! [DISCHARGE NUMBER] (field length = 3 characters)
This field is both a WENDB and a Key data element. This is the number associated with
this discharge. It must be the same as the DSCH field on the Pipe Schedule record.
VDRD*! [REPORT DESIGNATOR] (field length = 1 character)
This field is both a WENDB and a Key data element. The entry signifies the report
designator. It must be the same as the DRID field on the Pipe Schedule record.
NOTE: For retrieval purposes, the following acronym and field can be used. It is a
combination of the DISCHARGE NUMBER and the REPORT DESIGNATOR.
VDSG! (field length = 4 characters)
[COMBINED DISCHARGE NUMBER AND DESIGNATOR]
This system generated field is a Key data element. It is created by a combination of the
DISCHARGE NUMBER and REPORT DESIGNATOR fields. It can be used for Inquiry
and Retrieval purposes.
VPRM*! [PARAMETER CODE] (field length = 5 characters)
This field is both a WENDB and a Key data element. It is the STORET Parameter code.
The valid codes for this field can be found in TABLE 160 in the PCS Codes and
Descriptions Manual.
SbC-Ott$-034-
-------
Basic Training Permit Compliance System (PCS)
Example:
00011 Temp degrees fahrenheit
00300 Dissolved Oxygen
00310 BOD
00400 pH
00530 TSS
00610 Ammonia
50050 Flow
VMLO*! [MONITORING LOCATION] (field length = 1 character)
This field is both a WENDB and a Key data element. This code identifies the location from
which the sample is to be taken. The valid codes for this field can be found in TABLE 080
in the PCS Codes and Descriptions Manual.
Example:
G Influent point
1 Effluent point
5 Upstream point
6 Downstream point
K % removal
NODI* [PIPE NODI? (Y/N)] (field length = 1 character)
This field is a WENDB data element if the pipe did not discharge anything for the
monitoring period. If there was no discharge, enter *Y' in this field, otherwise this field
should be skipped.
[RANGE CHECKING (Y/N)] (field length = 1 character)
The valid responses to this field are:
Y Yes will allow the user to use the range checking table.
N No will not allow the user to perform range checking.
[RANGE TABLE ID] (field length = 5 characters)
The Range Table ID is entered in this field. Contact the Regional or State PCS Coordinator
for Range Table IDs.
I57T3753
-------
Permit Compliance System (PCS) Basic Training
[USE NATIONAL DEFAULT TABLE? (Y/N)] (field length = 1 character)
The valid responses to this field are:
Y Yes, if the National Default Table is to be used.
N No, is used if the National Default Table is not to be used.
SDC-0055-034-ST-3003 12/13/93
-------
Basic Training
Permit Compliance System (PCS)
2.10.4 EVIO Effluent Measurements-Type of Limit Screen 2
Effluent Measurements-Type of Limit Screen 2
11:35:16
11/33/92
PERMIT * (NPIO)
MEASUREMENTS
TYPE OF LIMIT - CURRENT
TRANS CODE DISCHARGE #
(PLOS)
LIMIT TYPE (LTYP) PARAMETER (PRAM)
MONITORING LOCATION _ SEASON _ MODIFICATION NUMBER _
(NLOC) (SEAN) (NOON)
- - - - QUANTITY LIMITS -
-------
Permit Compliance System (PCS) Basic Training
MVDT! (field length = 6 characters)
[MEASUREMENTS: MONITORING PERIOD END DATE]
This field is both a WENDB and a Key data element. This date comes from the Monitoring
Period End Date on the DMR and should be the last day of the month.
MQAV* (field length = 8 characters)
[MEASUREMENTS: QUANTITY: AVERAGE]
This field is a WENDB data element, if applicable. If the permittee reported a value in the
QUANTITY AVERAGE section on the DMR, that number is entered in this field.
MQMX* (Meld length = 8 characters)
[MEASUREMENTS: QUANTITY: MAXIMUM]
This field is a WENDB data element, if applicable. If the permittee reported a value in the
QUANTITY MAXIMUM section on the DMR, that number is entered in this field.
MCMN* (field length = 8 characters)
[MEASUREMENTS: CONCENTRATION: MINIMUM]
This field is a WENDB data element, if applicable. If the permittee reported a value in the
CONCENTRATION MINIMUM section on the DMR, that number is entered in this field.
MCAV* (field length = 8 characters)
[MEASUREMENTS: CONCENTRATION: AVERAGE]
This field is a WENDB data element, if applicable. If the permittee reported a value in the
CONCENTRATION AVERAGE section on the DMR, that number is entered in this field.
MCMX* (field length = 8 characters)
[MEASUREMENTS: CONCENTRATION: MAXIMUM]
This field is a WENDB data element, if applicable. If the permittee reported a value in the
CONCENTRATION MAXIMUM section on the DMR, that number is entered in this field.
DMRR [DMR RECEIVED DATE] (field length = 6 characters)
This field is the date the DMR was received by the agency. The value in this field will be
generated by the system, if there is no data entered.
$bC-OOS5-034-ST-3003 15713753 123
-------
Basic Training Permit Compliance System (PCS)
SNCE [RNC DETECTION: CODE] (field length = 1 character)
This field is a WENDB data element, if applicable. It is used for the manual entry of an
RNC detection code. If no data is entered, the system will automatically generate this field
when the RNC update program runs, if a violation has occurred.
SNDE [RNC DETECTION: DATE] (field length = 6 characters)
This field is a WENDB data element, if applicable. It is used for the manual entry of an
RNC detection code. If no data is entered, the system will automatically generate this field
when the RNC update program runs, if a violation has occurred.
SRCE [RNC RESOLUTION: CODE] (field length = 1 character)
This field is a WENDB data element. It is used for the manual entry of an RNC resolution
code. If no data is entered, the system will automatically generate this field when the RNC
update program runs, if a violation has occurred. The codes for this field are contained in
TABLE 390 in the PCS Codes and Descriptions Manual.
SRDE [RNC RESOLUTION: DATE] (field length = 6 characters)
This field is a WENDB data element. It is used for the manual entry of an RNC resolution
code. If no data is entered, the system will automatically generate this field when the RNC
update program runs, if a violation has occurred.
REXC [REPORTED # OF EXCURSIONS] (field length = 2 characters)
This field represents the number of excursions reported on the DMR form.
RFRQ (field length = 5 characters)
[REPORTED FREQUENCY OF ANALYSIS]
This field represents the frequency of analysis used by the permittee and requested on the
DMR form.
RSAM [REPORTED SAMPLE TYPE] (field length = 2 characters)
This field represents the sample type used by the permittee and reported on the DMR form.
124 12/13/93 iDC-
-------
Permit Compliance System (PCS) _ Basic Training
(field length = 2 characters)
[REPORTED QUANTITY UNIT CODE]
This field represents the unit of measurement used by the permittee when the sample was
taken. Data is entered in this field only when the reported unit of measurement is different
from the unit of measurement on the limit record.
RCUN (field length = 2 characters)
[REPORTED CONCENTRATION UNIT CODE]
This field represents the unit of measurement used by the permittee when the sample was
taken. Data is entered in this field only when the reported unit of measurement is different
from the unit of measurement on the limit record.
NODI* [NO DISCHARGE REASON CODE] (field length = 1 character)
This field is a WENDB data element, if applicable. It represents the reason why a parameter
or an entire pipe did not have a discharge.
MVDT (field length = 6 characters)
[CHANGED MEASUREMENT/VIOLATION DATE]
This field is used to change the monitoring period end date of a measurement that is on file.
ACCEPT? Y/C/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
C (Cycle) is used to cycle through the measurements.
It will accept the data entered on the screen and display
the next limit record to be entered.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
I27T3753 125
-------
Basic Training Permit Compliance System (PCS)
2.11 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 Other Menu is used to reach the Single Event Violations screen.
Other Menu
11/14/92 PCS-ADE Data Entry Subsystem PCDEMENU
11:00:58 Other Menu
Enter screen ID or 'X' to select an option
Screen ID: ___
SVIO - Single Event Violations
~ PPS1 - Pretreatment Sunmary
EVm - Evidentiary Hearings
~ GRNT » Grants
EXIT - Return to Main menu
-------
Permit Compliance System (PCS) Basic Training
2.11.1 SVIO Single Event Violations
The following PCS-ADE screen is used to enter Single Event violations. -
Single Event Violations Screen
IS;24:35 5IBQLB BVBHT VIOLATIONS FCDBSVIO
01/14/93 SCRBBH ID: SVIO
VBRMXT f (HPXD) THAHS CODS _
VXOUXXOK COM (8VCD) VIOLWIOH DAT* (8VDT)
BBC DBTBCTIOH COOK C-00$$-034-ST-3003 12/13/93 127
-------
Basic Training Permit Compliance System (PCS)
SVDT! [VIOLATION DATE] (field length = 6 characters)
This field is a Key data element. It represents the date the single event violation occurred.
SNCS* [RNC DETECTION CODE] (field length = 1 character)
This field represents the manual RNC detection code. A complete list of RNC detection
codes can be found in TABLE 195 in the PCS Codes and Descriptions Manual.
SNDS* [RNC DETECTION DATE] (field length = 6 characters)
This field represents the date the single event violation was detected as RNC.
SRCS* [RNC RESOLUTION CODE] (field length = 1 character)
This field represents the manual RNC resolution code. A complete list of RNC detection
codes can be found in TABLE 390 in the PCS Codes and Descriptions Manual.
SRDS* [RNC RESOLUTION DATE] (field length = 6 characters)
This field represents the date on which the RNC was resolved.
RDS1 [REGIONAL FIELD 1] (field length = 3 characters)
RDS2 [REGIONAL FIELD 2] (field length = 5 characters)
These are user-defined fields. Check with the PCS Regional Coordinator for their use.
ACCEPT? Y/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
15713753
-------
Permit Compliance System (PCS) Basic Training
2.12 Enforcement Action Data Type
Enforcement actions are structured into 2 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 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 any keys to the violations, if
necessary. There may be many EK records for each EA record.
The top portion of the 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. (* 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.
The Enforcement Action Menu is used to reach the Enforcement Action screens.
Enforcement Action Menu
11/14/92 PCS-ADE Data Entry Subsystem PCOEHENU
11:00:58 Enforcement Action Menu
Enter screen ID or 'X' to select an option
Screen ID: . .
ENAC - Enforcement Action
EAKS - Enforcement Action Keys
EAP1 - ADN Penalty Order screen 1
3 EAP2 - ADN Penalty Order screen 2
EXIT - Return to Main menu
(PF1,13=Kelp; PF3,15=*ain Menu; PF*.16=Quit; PF8=8ottom>
SDC-0055-034-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
2.12.1 ENAC Enforcement Actions Screen
Enforcement Actions Screen
14:99:53 BHFORCBODIT' ACTION
ll/33/»3 8CRBBH ID» BUM
PBBMXT »
DOCOCT WWBBR (BRPlO CLOSURB 4CKBDULSD DATS (BACD)
XHXTXAXXHS PARTY 1 (BXPX) X8XTXATXNQ VXKtt 2 (BZP.) ______
XKSFOMSB DOB DXTB (BBDT) ______ BBSFCXISB ACHIEVXD J3MXB (BKDK) ______
vxouTzar RBCOommar DAXB Y/K/H/M! K VBMIOII _2±4__03/ia/90_
*Note: On-line screen does not contain acronyms.
Enforcement Actions Data Type (EM - Screen/Acronym/Field Descriptions
NPID*! [PERMIT #] (field length = 9 characters)
This field is both a WENDB data element and a Key data element.
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
ENAC*! [ENFORCEMENT ACTION CODE] (field length = 2 characters)
This field is both a WENDB and a Key data element. The 2-digit code in this field describes
the type of action taken:
-------
Permit Compliance System (PCS) Basic Training
Valid options for this field include the following:
OS Phone call
21 Administrative order
25 Consent Decree
54 MCP Required AO-EO
56 MCP Schedule AO-EO
72 Pretreatment Admin Order
A complete list can be found in TABLE 030 of the PCS Codes and Descriptions Manual.
EATP! [ISSUED BY] (field length = 2 characters)
This Meld is a Key data element. Valid options for this field include:
EEPA
S State
ENDT*! [DATE] (field length = 6 characters)
This field is both a WENDB and a Key data element. This field represents the date the
enforcement action was issued or signed.
ENST* [STATUS CODE] (field length = 2 characters)
This field is a WENDB data element in certain circumstances. It indicates the status of the
enforcement action. The only options for this field that are considered to be WENDB are
'C' to close the enforcement action and 'C' to indicate that the enforcement action is closed
but superseded by another enforcement action. A complete listing of the valid options for
this field can be found in TABLE 040 in the PCS Codes and Descriptions Manual.
ESDT* [STATUS DATE] (field length = 6 characters)
This field is a WENDB data element when a code has been entered in the ENST field. It
represents the date that the status of the enforcement action changed.
ERFN* [DOCKET NUMBER] (field length=10 characters)
This field is a WENDB data element when the code entered in the ENST field is a formal
enforcement action code. This field contains the file number or case number of the
enforcement action.
SbC-0055-034-ST-30W 13713793 " TJT
-------
Basic Training Permit Compliance System (PCS)
EACD [CLOSURE SCHEDULE DATE] (field length = 6 characters)
This field contains the date the enforcement action is scheduled to be closed.
EIPI [INITIATING PARTY 1] (field length = 5 characters)
This field contains the initials of the primary person who initiated the enforcement action.
EIP2 [INITIATING PARTY 2] (field length = 5 characters)
This field contains the initials of the secondary person who initiated the enforcement action.
ERDT [RESPONSE DUE DATE] (field length = 6 characters)
This field represents the date on which the permittee is due to respond to the agency in
accordance with the action taken.
EADR [RESPONSE ACHIEVED DATE] (field length = 6 characters)
This field represents the date the permittee completed the response agreed upon in the
enforcement action.
EVDK [VIOLATION RECOGNITION DATE] (field length = 6 characters)
This field represents the date the effluent violation became known to the permitting agency.
132 I57T3753
-------
Permit Compliance System (PCS) Basic Training
RDH1 [USER DATA ELEMENT: #1] (field length = 3 characters)
RDH2 [USER DATA ELEMENT: #2] (field length = 5 characters)
These are user-defined fields. Check with the PCS Regional Coordinator for their use.
ECM1 [ENFORCEMENT ACTION COMMENT # 1] (first 30 characters)
ECM2 [ENFORCEMENT ACTION COMMENT # 2] (second 30 characters)
ECM3 [ENFORCEMENT ACTION COMMENT # 3] (third 30 characters)
ECM4 [ENFORCEMENT ACTION COMMENT # 4] (fourth 30 characters)
ECM5 [ENFORCEMENT ACTION COMMENT # 5] (fifth 30 characters)
ECM6 [ENFORCEMENT ACTION COMMENT # 6] (sixth 30 characters)
ECM7 [ENFORCEMENT ACTION COMMENT # 7] (seventh 30 characters)
ECM8 [ENFORCEMENT ACTION COMMENT # 8] (eighth 30 characters)
ECM9 [ENFORCEMENT ACTION COMMENT # 9] (ninth 30 characters)
ECMO [ENFORCEMENT ACTION COMMENT # 0] (tenth 30 characters)
The fields above are populated with free-form information. These fields use acronyms that
can be used to perform generalized retrievals or inquiries on enforcement action records.
VIOLATIONS THAT CAUSED ENFORCEMENT ACTIONS TO BE ISSUED
[ALL NUMERIC EFFLUENT] (field length = 1 character)
[ALL STATE NON-RECEIPT]
[ALL EPA NON-RECEIPT]
[ALL EPA + STATE NON-RECEIPT]
[ALL COMPLIANCE SCHEDULE]
[ALL SINGLE EVENTS]
[SPECIFIC VIOLATIONS]
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
violation types that will be generated:
[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 MVIO code of £90, since the
last enforcement action date.
SbC-OOSS-034-SY-3003 12713793T33
-------
Basic Training Permit Compliance System (PCS)
[ALL STATE NON-RECEIPT]
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, since the last enforcement action date.
[ALL EPA NON-RECEIPT]
Placing an 'X' beside this field will generate an EVTP of Nl. This code means that the
enforcement action is tied to all effluent violations with an MVIO code of D10 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 MVIO code of D30 since the
last enforcement action date.
[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
CIO, C20, C30 and C40 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 SVCD code since the last
enforcement action date.
[SPECIFIC VIOLATIONS]
Placing an 'X' beside this field will take the system to the Enforcement Action Key
Screen. This will automatically generate a code in the EVTP field. A code must be
entered for the EVTP on the Enforcement Action Key Screen. Additional explanation is
available in the next section of this manual "Enforcement Action Examples".
134 12/13/93 SbC-OOSS-OS^'l'-JOOi
-------
Permit Compliance System (PCS) Basic Training
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
SDC-0055-034-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
Enforcement Action Examples
The following samples, examples, and procedures describe various aspects of Enforcement
Actions and how the Permit Compliance System handles them.
Example:
GA0000125 was issued a consent decree on 072392 by EPA, docket number 87-4536. The
enforcement action addressed all effluent and all compliance schedule violations.
NOTE: Any entry (except under specific violations) made on the screen below the
"VIOLATIONS THAT CAUSED THE ENFORCEMENT ACTION TO BE
ISSUED" will create an EK record.
Enforcement Actions Sample Screen
10)55:00 ENFORCEMENT ACTION FCDBBKAC
12/31/89 SCREEN ID: BNAC
PERMIT # 990000135 TRANS CODE n
ENFORCEMENT ACTION CODE 25 ISSUED BT e DATE 072392
STATUS CCffiS STATUS DATE
DOCKET NDMBBH 87-4536 CLOSURE SCHEDULED DATE
INITIATING PARTY 1 _______ INITIATING PARTV 2
RESPONSE DOB DATE RESPONSE ACHIEVED DATE
VIOLATION RECOGNITION DATE ______ OSBR DATA BLBMBNTt fl «2
- - ENFORCEMENT ACTION COMMENTS - - - -
«1 «2
«3 f«
ts *«
7 |»
*» tlO
. . . VIOLATIONS THAT CAUSED THE ENFORCEMENT ACTION TO BE ISSUED - -
X ALL NUMERIC EFFLUENT _ ALL STATE NON-RECEIPT _ SPECIFIC
X ALL COMPLIANCE SCHEDULE _ ALL EPA NON-RECEIPT VIOLATIONS
_ ALL SINGLE EVERTS ALL EPA * STATE NOH-RECEIPT
136 12/13/93 SDCXX)55-034-ST-3003
-------
Permit Compliance System (PCS)
Basic Training
If *X' is entered in the Specific Violations Option on the ENAC screen, the EAKS screen
will be displayed. Available information from the previous screen will be filled in. The
EAKS screen may also be accessed from the main menu. There are seven EAKS screens
that you may encounter, depending on what data is entered on the first screen.
2.12.2 EAKS Enforcement Action Key Screen
Enforcement Action Key Screen
11/33/92
PCS-ADB
BHFORCBMBMT ACTION
KEY SCREEN
PCDBSAKS
SCRBEH ID: BAKS
PERMIT t *»t^ Type fEA) - Screen/Acronym/Field Descriptions
NPID*! [PERMIT #] (field length = 9 characters)
This field is both a WENDB and a Key data element.
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
137
12/13/93
-------
Basic Training Permit Compliance System (PCS)
EKAC*! [ENFORCEMENT ACTION CODE] (field length = 1 character)
This field is both a WENDB and a Key data element. The 2-digit code in this field describes
the type of action taken:
Valid options for this field include the following:
OS Phone call
21 Administrative order
25 Consent Decree
54 MCP Required AO-EO
56 MCP Schedule AO-EO
72 Pretreatment Admin Order
A complete list can be found in TABLE 030 of the PCS Codes and Description Manual.
Tables.
EKTP! [TYPE ORDER ISSUED] (field length = 1 character)
This field is a Key data element. Valid options for this field include:
EEPA
S State
EKDT! [ENFORCEMENT ACTION DATE] (field length = 6 characters)
This field is a both a WENDB and a Key data element. This field represents the date the
enforcement action was issued or signed.
EVTP*! [VIOLATION TYPE] (field length = 2 characters)
This field is both a WENDB and a Key data element. It represents the code that links an
enforcement action record to specific violations. A complete listing of enforcement action
violation codes can be found in TABLE 340 of the PCS Codes and Descriptions Manual.
[DO YOU WISH TO CYCLE (Y/N)] (field length = 1 character)
The Cycle Option is used for the system to display violations to you. If the cycle option is
selected, the system will prompt you to narrow the violations you wish to see as you cycle.
The prompt displayed will depend on the EVTP you enter. The system will ask you to
provide keys to violation records. It will then only display those violations that meet the key
criteria.
135 12/13/93 SDC-O055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
2.12.2.1 Entering an EK Record For a Specific Effluent Violation Without Cycling
Step 1: Enter the EA information on the first EAKS screen, .
Enforcement Action Key Screen
0»i20tOO PC6-ADB
OX/04/90 SCREBH X»i BAKS
ACTIOW
KEY SCUBR
» CO000131X
TRASS OOD> H
CEKERT ACITOH OOOB 21.
ORDER ISSUED B
ACTION DATE 010192
VIOLATION TYPE 83
DO YOU WISH TO CYCLE (Y/N) 7 H
ACCEPT
-------
Basic Training Permit Compliance System (PCS)
Step 2: PCS-ADE displays the information above the dotted line. Identify the specific
violation being addressed by providing the keys to the measurement below the dotted
line.
Enforcement Action Effluent Key Screen
SCTIDW BPPLOTDfT KBY SCXKBR PQBBK8F
01/04/90 8CRBBH ID: BMC8
PERMIT « OOO001S11 TSAH3 OQDB B
B8PORCBHBRT JkGTXOH OODB 31 MIMXBZSTKKnVE QKDSK
XSSDBD BY * BFA BHVOBCBIRBr aCTZOH OBXB 010192
VIOLATICW TITS B3 SFBCIRC BVrUIBMr VIOLKTICDI
DUCNUttB t lac
DISCHAROB DBfllGHKTOK a
LIMIT TCTB f
FABAHBTER CODE 00530
8BMORM. 0
MQDIPICATIOM MOMBBR 0
MOHITOKXNB DATE 103192
ACCBPT
-------
Permit Compliance System (PCS) Basic Training
2.12.2.2 Entering an EK Record For a Specific Effluent Violation With Cycling
Step 1: Enter the EA information on the first EAKS screen, .
Enforcement Action Key Screen
oat ao: oo PC»-AI» PCMKMCS
01/04/90 aCRBBH XDi EAKS
BHFORCBMBltT JU3XOK
KBY SCRBBH
* kyOOOi»29
TWOS com ii
ERPOBCIMBHT ACTION OOD8 07
TYPE (ffiOBR ISSDBD e
BHFOtCBMBHT ACTZ08 DATE 041593
VXOUXXOR TVFB «3
00 YOO WISH TO CTCLB (Y/H)7 V
ACCEPT
-------
Basic Training
Permit Compliance System (PCS)
Step 2: Narrow which measurement violation records to cycle through by entering the
requested data. Only violations on outfall 0011, final limits will be displayed in this
example.
Enforcement Action Key Screen
0«i30iOO
OX/04/90
TCS'JkDE
BNFOKCBBNT ACTIOW
PCDBRMCS
3CRBBH ID: BARS
f KY0001929
mats CODE ir
BRPORCBBQTT ACTION OQDB 07
TCTB OBDBK IS30ED B
ACTIOM DATE 041592
VIOUTIOH TTFS B3
00 YOT WISH TO CTCLB (Y/R)? B
DISCHAXGB 8DMBBR 001
XBFOXT DB8ZQNKZOX 1
LDOT n?B f
PARAMBTBH CODS
MONITORING XOCKTXOH _
PBRIM) BUD DATS
ACCEPT (Y/H/M)7 Y
VKH3IOH 3.3 11/37/69
142
12/13/93
SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
Step 3: The first effluent violation for the given key information is displayed.
Enforcement Action Effluent Key Screen
06)20:15 ZBFOXCBWI ACHOW BFFUJWT nX SCRBBH
01/04/90 3CRKBH H>» BAKS
PERMIT * KV0081939 TRAMS CODB V
BHFORCBMBNT ACTXC4T CODE 07 MBBTXNB WITH FERMXTXBB
ISSUED ax * EPA mratamBHr ACTXOH DATS 941592
VXOLATIOH TYPB U flfKCIFIC BFPLOBHT VXOLAZZOH
DZSGBMOB t 001
DI8CHARCB DBSIGHATOK 1
LIMIT TYPE 5
VARAMBTBK OQDV 00011
MONITORim LOCXTTOH i
SR&3OHAI. fl 0
MODXFXCXrXOH UtJHBBR 0
MCMITOItlHa DAT* 2.13091
ACCEPT (Y/H/C/fl/M)? a VBBSION 2.2 11/27/89
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-ST-3003 12/13/93 143
-------
Basic Training Permit Compliance System (PCS)
2.12.2.3 Entering an EK Record For a Specific Compliance Schedule Violation
Without Cycling
Step 1: Enter the EA information on the first EAKS screen, .
Enforcement Action Key Screen
08.20100 Ka-AOB PCBBBAXS
01/04/90 SCRKBK ZDt RMS
BHFOROMHHr ACTION
OX SOiBBM
PERMIT t 110000027
TRANS CODS B
ACTXOH OODB 01
TXTB ORDER ISSOBD
BHFOXCBMSHT ACTIOH DATS 123193
VIOUCTZON TYPB C2
DO TOD WISH TO CYCLB (Y/M>? n
(Y/N/M)? Y VnSION 3.3 11/37/89
144 12/13/93 SbC-00&-034-!iT-:JOOi
-------
Permit Compliance System (PCS) Basic Training
Step 2: PCS-ADE displays the information above the dotted line. Enter the information
below the dotted line.
Enforcement Action Compliance Schedule Key Screen
061*1:00 RMMKCBMRKr ACTIOH CONPLXMKB SCHEDULE KEY SOWER PCDEBACS
01/04/90 SCRBBH ID: BAES
PERMIT f FLOQ00037 TRASS OODB x
EBFOKCBMBHT ACTIOH OODB flr SO CDRUHT ACSV WMUKMRB
IMOED BY 8 STKTK BHVOBCBNBRT BCTIOR OKIE X23192
VXOLKTZOII nra ca SPBCIFIC OQMFLIMICB VXOLXTZOH
COKFUlkRCE ftCHBDOU f BC DKIA. SOURCE CODE 0001
COMPLIANCE SCHEDULE BVKHT CODE 04099
COMPLXABCE VXOtATIOH CODE C20 OOMFLIAHCB VlOLKtlOH DATE 060S92
ACCEPT (Y/H/CAF/MJ7 Y VBHSIOH 2.1 11/37/89
SDC-flKS-034-ST-3003 T27T3753
-------
Basic Training Permit Compliance System (PCS)
2.12.2.4 Entering an EK Record For a Specific Compliance Schedule Violation With
Cycling
Step 1: Enter the EA information on the first EAKS screen, .
Enforcement Action Key Screen
0*1aoioo tea-Mat KDBBAKS
01/04/9O 3CRBRN XBt EAKS
1 ACTXOg
KBY SQtBBH
PBRKET ff AX00017U.
nuns COOB n
ACTIOff CODE 01
TX» OXDKH ISSUED 9
amncEMHirr ACTIOH DATS 010993
VXOUIXQR TWS Cl
DO TOD 1IZ3H TO CTCLB (Y/B)7 y
ACCBPT (Y/R/Ml? Y VBRSIOR 2.3 11/37/89
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.
12/13/93 5DC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
Enforcement Action Key Screen
VCS-ADK PCDSBMCS
OX/04/90 SCRBBH ZOi SAKS
Acnos
m**OftCBHKHT JtfTIOH GQDB 01
nrre OBDSR TSSOBD a
BHPQKCaHBm ACTIOH OKtB 070992
VXOUTXOH TlfPB C2
DO TOV WISH TO CTCU (Y/H)? T
COMFLUHCK SCHBDOLB ROMBBR 01
DUOA SOTOCB CODE
OOKPLIMICB 8CH8DDL8 HUMBRX
VIO1ATIOU OODB
VIOLATION DAT*
ACCEPT (Y/R/M)? T VTO3IOH 2.1 11/31/88
SbC-005S-034-ST-3003 12/13/93
-------
Basic Training Permit 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
«fti3icOO ENFORCEMENT ACTION COMPLIANCE SCHEDULE ant SCREEN PCDBBACS
01/04/90 SCREEN ZDiEAKS
PERMIT * AXOOOiril TRANS CODE V SCREEN JDJ BAEB
BHKXtcBMmrr »CTK» oora 01 BO canmrr xcnr WAJWAHTE
ISSUBD BY 8 BTRTB BHPORCBMBHT ACTZON DATE 071O»3
vzoLxrxoH TXPB ca SVBCXVZC COMPLIAHCB VIOLATIOR
OOffLZAHCB fiCHUOLB I 01 DATA SOOHCB CODE 0790
COMPLIANCE SCMEDOU BVBRT CODE 00599
COMPLIANCE VIOLATION CODE C20 COMPLIANCE VIOLATION DATE 121991
ACCEPT (Y/H/C/8/M)} a VERSION 3,2 11/27/89
148 12/13/93 SDC-0055-034-M-3UUJ
-------
Permit Compliance System (PCS) Basic Training
2.12.2.5 Entering an EK Record For a Single Event Violation Without Cycling
Step 1: Enter the EA information on the first EAKS screen, .
Enforcement Action Key Screen
OtilOtOO PCS-ADE
04/04/90 SCREEN IDs BUS
BHPO8CBMBMT ACTION
nrr SCMMEH
JkCTXOR CODB 31
TTFB QROBR laflOTED a
BHFORCBNBBtr ACTZON DKTB 101192
VZOXAXZOV TYFB 93
DO XOO WISH 1O CXCLB <*/M)7 n
ACC8PT
-------
Basic Training Permit Compliance System (PCS)
Step 2: PCS-ADE displays information above the dotted line. Enter the keys to the violation
in the fields below the dotted line.
Enforcement Action Single Event Violation Key Screen
o*i2a:00 BHFORCBMnrr action amour BVBHT VXOUTXOH KB* SCREKH FCDEBMF
Ox/04/90 SCRSBH ID: BAKS
PERMIT * MM000037 TOMS OODB Jl
KHPORCKMBar Acrxoa CODE ai tasuusnaam oum
XS80BD BY « «XKTK KHPOHC1MKWT ACTIOR OKXC 103193
VTOLUXOM TTPB 82 4PBCZKC SIHOUI KVBRT VZOLKTZOH
8XRCLB BVBRT VXOLKTIOB OODB 03099
BVBHT VIOLKTZOII DATE 040193
ACCBPT (Y/H/r/M)? Y VBHSItM 3.1 11/37/89
T30 I27T3753
-------
Permit Compliance System (PCS) Basic Training
2.12.2.6 Entering an EK Record For a Single Event Violation With Cycling
Step 1: Enter the EA information on the first EAKS screen, .
Enforcement Action Key Screen
o*> ao i oa POS-ADK PCDBBMS
01/04/90 SCHBBS XBt
mfOKCBMBMT ACXXOB
tan sauna
FBRMTT f 0101478
TUO» CODE B
BHFOKCMBIIT ACTION CODB 21
TTPB cam, ISSUED e
BHPORCBKBHT ACTZOIt DUB 060792
TZOUTira TYPE 82
DO YOO WISH TO CYCLE (Y/H)7 V
(Y/H/M)? T VSKSIOH 2.3 11/27/89
12/13/93
-------
Basic Training
Permit Compliance System (PCS)
Step 2: Narrow the SV records to be cycled through by entering the requested data. Leaving
these prompts empty will cause PCS-ADE to cycle through all SV records.
Enforcement Action Key Screen
06)20:00
01/04/90
PCS-ADB
PCDBEftXS
3CRBBH ID: 8AKS
ACTION
KBX flCUKB
PERMIT « 100101476
TRAK8 OOO8 M
1 ACTIOH OODB 31
TYP» OHDER ISSDSD B
EHFOBC8MEHT ACTIOH DATS 060793
VZOtATIOB TTfPB 83
DO TO? WISH TO CYCLB (T/R)7 Y
VIOLATION COOB
VIOLXTIOH DKTB
ACCEPT (Y/H/M)7 Y
VBB3ION 2.3 11/27/89
T5T
1J/13/W
-------
Permit Compliance System (PCS) Basic Training
Step 3: PCS-ADE displays the first SV record on file.
Enforcement Action Single Event Violation Key Screen
06:32:00 HHPOTCBIBW ACTXOV SINGLE EVBWT VIOLATION EBY SCRBBH FCDEBASP
01/04/90 SCREEN XDl BMCS
PERMIT « MAOlOi478 1UUI8 CODE H 8CBBBH XD« BMCS
HFOXCEMMMT ACXZOV CODE 21 AMUHISTlWnVF OKDEX
ISSUED BY E EPA BHPORCEHEWT ACTKM DATE 060792
VXOIATIO8 TYPE 83 8PBCZFIC SZHQLS EVBHT VXOLATZON
SINOLR BVEWT VZOUZZOM CODE 03099
8IHGLB BVBBT VXOLAXZOH DATE 081891
ACCEPT (Y/H/C/S/M)? C VBRSIOI 1.1 11/27/89
SbC-005S-034-Sf-3003 12/13/93 133
-------
Basic Training Permit Compliance System (PCS)
2.12.3 Administrative Penalty Order
There are two screens associated with Administrative Penalty Orders. These screens are
used to enter all relevant information pertaining to these type orders.
2.12.3.1 EAP1 Administrative Penalty Order Screen 1
Administrative Order Screen 1
14l57:09 ADMINISTRATIVE PENALTY ORDER PCDEEAP1
11/23/92 SCREEN ID: EAP1
PERMIT # TRANS CODE C
ENFORCEMENT ACTION PENALTY AMOUNT (APAM)
CLASS 2 APPEAL (APAP) DATE JUDICIAL APPEAL (APAF)
DATE PENALTY COLLECTED (APPC)
DATE PUBLIC NOTICE ISSUED (APNT)
PUBLIC COMMENTS CAPCM) _
COMMENT PERIOD DEADLINE (APCD) DATE HEARING REQ'D
-------
Permit Compliance System (PCS) Basic Training
ENAC*! [ENFORCEMENT ACTION CODE] (field length = 2 characters)
This field is both a WENDB and a Key data element. The 2-digit code in this field describes
the type of action taken. Valid options for this field include the following:
OS Phone call
21 Administrative order
25 Consent Decree
54 MCP Required AO-EO
56 MCP Schedule AO-EO
72 Pretreatment Admin Order
A complete list can be found in TABLE 030 of the PCS Codes and Descriptions Manual.
EATP! [ISSUED BY] (field length = 2 characters)
This field is a Key data element. Valid options for this field include:
EEPA
S State
ENDT*! [DATE] (field length = 6 characters)
This field is a both a WENDB and a Key data element. This field represents the date the
enforcement action was issued or signed.
APCL* [CLASS] (field length = 1 character)
This field is a WENDB data element. It represents the classification for an administrative
penalty. The class is defined by a statutory maximum penalty amount, the length of the
comment period and the nature of the hearing. The hearing is held before an EPA
Administrative Law Judge. Valid options for this field include:
1 A Class I Administrative Order.
Maximum Penalty = $25,000.00
2 A Class n Administrative Order.
Maximum Penalty = $125,000.00
$DC-M53-034-
-------
Basic Training Permit Compliance System (PCS)
APHR* [HEARING] (field length = 1 character)
This Meld is a WENDB data element. It represents whether the respondent requests a
hearing to contest an administrative penalty.
APFO* [DATE OF FINAL ORDER] (field length = 6 characters)
This field is a WENDB data element. It represents the date that the final administrative
penalty order was issued and the administrative penalty amount was assessed.
APAM* [PENALTY AMOUNT] (field length = 6 characters)
This field is a WENDB data element. It represents the dollar amount of the assessed
administrative penalty. This field is checked against the CLASS (APCL) field. No special
characters can be entered, i.e., $ or ,.
APAP* [CLASS H APPEAL] (field length = 1 character)
This field is a WENDB data element. It indicates that an appeal of the decision in a Class H
action was filed. Valid options for this field include:
A Agency, EPA
B Both Agency and Respondent
R Respondent
APAF* [DATE JUDICIAL APPEAL] (field length = 6 characters)
This field is a WENDB data element. It is the date when the respondent filed an appeal to
an Administrative Penalty Order and provided notice of the appeal to an EPA administrator.
It must be a valid date on or after the DATE OF FINAL ORDER (APFO).
APPC* [DATE PENALTY COLLECTED] (field length = 6 characters)
This field is a WENDB data element. It is the date that verification of full or final payment
of an Administrative Penalty amount was received. It must be a valid date and be on or after
the DATE OF FINAL ORDER (APFO).
APNT [DATE PUBLIC NOTICE ISSUED] (field length = 6 characters)
This field is the date a public notice for the Administrative Penalty Order was issued. This
date serves as the beginning of the comment period.
155 12713753
-------
Permit Compliance System (PCS) Basic Training
APCM [PUBLIC COMMENTS] (field length = 1 character)
This field indicates whether public comments were received in response to a proposed
Administrative Penalty Order. The valid responses to this field are:
Y Yes, if there were comments.
blank System Default.
APCD [COMMENT PERIOD DEADLINE] (field length = 6 characters)
This field is the final date when public comments will be accepted.
APRR [DATE HEARING REQ'D] (field length = 6 characters)
This field is the date when the respondent requested a hearing to contest an Administrative
Penalty Order.
APHD [SCH DATE OF HEARING] (field length = 6 characters)
This field is the date on which the hearing is scheduled to convene.
APAH [DATE OF HEARING] (field length = 6 characters)
This field is the actual date the hearing was convened.
APHS (field length = 6 characters)
[DATE OF PREHEARING SUBMISSION]
This field is the deadline set for the submission of major facts concerning the Administrative
Penalty Order.
APPO [DESIGNATED ALJ OR PO] (field length=20 characters)
This field indicates the last name of either the Administrative Law Judge or the Presiding
Officer at the Administrative Penalty hearing.
APPH (field length = 1 character)
[PUBLIC PARTICIPANT IN HEARING]
The valid response to this field is (Y)es to indicate whether a third party offers oral or
written evidence at the hearing.
12713793
-------
Basic Training Permit Compliance System (PCS)
APPP (field length = 6 characters)
[DATE COMMENTERS' PETITIONS FOR RECONSIDERATION RECEIVED]
This is the date when the commenters' petitions and request for reconsideration were
received to contest the Administrative Penalty Order.
APDP (field length = 1 character)
[DISPOSITION OF COMMENTERS' PETITIONS]
This field represents the end result of the commenters' petitions. The valid responses to this
field are:
G Granted
D Denied
APD2 [DEADLINE CLASS H APPEAL] (Meld length = 6 characters)
This field is the final date for an appeal to be filed in order to contest an Administrative Law
Judge's decision.
APA2 (field length = 6 characters)
[DATE CLASS H DECISION APPEALED]
This is the date that the decision of an Administrative Law Judge was appealed to a Judicial
Officer in a Class JJ action.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
158 12/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
[MORE A.P.O. DATA?] (field length = 1 character)
The valid responses to this field are:
Y Yes, if there is additional AO information to be entered.
N No, is used if there is no additional AO information to be entered.
SbC-OOSg-034-ST-3003 12713753
-------
Basic Training Permit Compliance System (PCS)
2.12.3.2 EAP2 Administrative Penalty Order Screen 2
Administrative Order Screen 2
tt*.S7:45 ADM PENALTY ORDER PCDEEAP2
11/23/92 SCREEM ID: EAP2
PERMIT # TRANS CODE C
ENFORCEMENT ACTION CODE (EHAC) _ ISSUED BY (EATP) _ DATE
SCH DATE OF APPEAL WARING (APHA) DATE OF HEARING (APM2)
DATE APPEAL DECISION ISSUED CAPAD)
D^ -. JUDICIAL DECREE FILED
DATE 4 CAP04) COMMENT * (APC4)
ACCEPT? Y/K/N/M: Y VERSION 2.2 03/12/90
Administrative Penalty Order (AO) - Screen/Acronym/Field Descriptions
NPID*! [PERMIT #] (field length = 9 characters)
This field is both a WENDB data element and a Key data element.
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
ENAC*! [ENFORCEMENT ACTION CODE] (field length = 2 characters)
This field is both a WENDB and a Key data element. The 2-digit code in this field describes
the type of action taken:
ISO 12/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
Valid options for this field include the following. A complete list can be found in TABLE
030 of the PCS Codes and Description Manual.
OS Phone call
21 Administrative order
25 Consent Decree
54 MCP Required AO-EO
56 MCP Schedule AO-EO
72 Pretreatment Admin Order
EATP! [ISSUED BY] (field length = 2 characters)
This field is a Key data element. Valid options for this field include:
EEPA
S State
ENDT*! [DATE] (field length = 6 characters)
This field is both a WENDB and a Key data element. This field represents the date the
enforcement action was issued or signed.
APHA [SCH DATE OF APPEAL HEARING] (field length = 6 characters)
This field is the date on which the Judicial Officer is scheduled to meet with both parties in
an appeal to an Administrative Law Judge's decision.
APH2 [DATE OF HEARING] (field length = 6 characters)
This is the actual date on which the appeal to an Administrative Law Judge's decision
convenes.
NOTE: This field is only valid if the Administrative Penalty Order Class (APCL) field
contains a *2'.
APAD (field length = 6 characters)
[DATE APPEAL DECISION ISSUED]
This is the date an appeal decision to a Class JJ Administrative Penalty Order is signed by a
Judicial Officer.
SDC-0055-034-ST-3003 12/13/93 ibl
-------
Basic Training Permit Compliance System (PCS)
NOTE: This field is only valid if the Administrative Penalty Order Class (APCL) field
contains a '2*.
APJF [DATE JUDICIAL. DECREE FILED] (field length = 6 characters)
This is the date when an appellate court enters its final order affirming or reversing EPA's
decision.
APPA (field length = 6 characters)
[PENALTY ASSESSED BY JUDICIAL DECREE]
This field represents the dollar amount of the Administrative Penalty Order as assessed by an
officer of the court. No special characters are allowed, i.e., $ or ,. Leading zeros must be
entered.
APPD (field length = 6 characters)
[DEADLINE FOR PENALTY PAYMENT]
This is the date by which the first Administrative Penalty payment must be paid.
APTC [TOTAL PENALTY COLLECTED] (field length = 8 characters)
This field represents the total dollar amount collected for an Administrative Penalty Order.
No special characters are allowed, i.e., $ or ,. Leading zeros must be entered.
ADMINISTRATIVE PENALTY ORDER USER COMMENTS
AF01 [DATE 1] (field length = 6 characters)
AP02 [DATE 2] (field length = 6 characters)
AP03 [DATE 3] (field length = 6 characters)
AP04 [DATE 4] (field length = 6 characters)
These fields are used to enter the dates associated with the comments entered in the following
fields.
APC1 [COMMENT 1] (field length=20 characters)
APC1 [COMMENT 2] (field length =20 characters)
APC1 [COMMENT 3] (field length =20 characters)
APC1 [COMMENT 4] (field length =20 characters)
162 12/T3/9J SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
These fields are used to enter any comments associated with the administrative order penalty.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
SbC-003$-034-ST-3(X)3 12/13/93
-------
Basic Training Permit Compliance System (PCS)
2.13 Reissuance Processing
The reissuance process in PCS allows the user to retain a "ghosted" 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 imposed by the new permit; and
secondly, a record is kept of the limits from previous 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: LTPQ Parameter Limit Records
VTPQ Measurement Violation Records
Pipe Set Qualifier 9 Current effluent family records
Values: 0-8 Ghosted limits and measurements
0 Oldest set of ghosted data
Z Measurements without associated pipes and limits
For all indicators, the following processing takes place:
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 (RCIN).
Which limits are retained depends on the RCIN 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 RCIN screen.
164 12/13/93 iDC-W55-Ui4-a I-3UO3
-------
Permit Compliance System (PCS)
Basic Training
2.13.1 RCIN Reissuance Data
Reissuance Data Screen
1U3T.39
11/23/M
{BFXO)
DMA SCREEN
THABS CODE C
HBZS30MKB CODB (RCXM) _
HATB juunw
INITIAL LIMITS START DATE: (XL8D)
INITIAL LIMITS END DATS: (ILKD)
INTERIM LOOTS START DXTBt (ML8D)
INTERIM LIMITS BUD DATE: (MLBD)
FIRM. LIMITS START DATS: {PLSO}
FIHAL LIMITS BHD DATS: (PLED)
*Note: On-line screen does not contain acronyms.
FCDBRCXH
SCRSBtT IDs KCm
Processing - Screen/Acronym/Fit
NPID*! [PERMIT #]
(field length = 9 characters)
This field is both a WENDB data element and a Key data element.
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
RCIN*! [REISSUANCE CODE]
(field length = 1 character)
This field is both a WENDB and a Key data element. The code is entered to instruct PCS to
perform the reissuance process, and specifies which limits the user wishes to leave in the
current limit area for the new permit. Along with the code, date ranges must be provided
for the limits in effect in the new permit. Both the code and the date ranges are entered on
the RCIN screen.
12/13/93
153
-------
Basic Training Permit Compliance System (PCS)
ILSD* [INITIAL LIMITS START DATE:] (field length = 6 characters)
This field is a WENDB data element, if applicable. It is the date on which initial limits
began for the discharge/designator.
ILED* [INITIAL LIMITS END DATE:] (field length = 6 characters)
This field is a WENDB data element, if applicable. It is the date on which initial limits
ended for the discharge/designator.
MLSD* [INTERIM LIMITS START DATE:] (field length = 6 characters)
This field is a WENDB data element, if applicable. It is the date on which interim limits
began for the discharge/designator.
MLED* [INTERIM LIMITS END DATE:] (field length = 6 characters)
This field is a WENDB data element, if applicable. It is the date on which interim limits
ended for the discharge/designator.
FLSD* [FTNAL LIMITS START DATE:] (field length = 6 characters)
This field is a WENDB data element, if applicable. It is the date on which final limits began
for the discharge/designator.
FLED* [FINAL LIMITS END DATE:] (field length = 6 characters)
This field is a WENDB data element, if applicable. It is the date on which final limits ended
for the discharge/designator.
ACCEPT? Y/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
lOO 12/13/93 iDC-UUDD-WM 1 - JUU 6
-------
Permit Compliance System (PCS)
Basic Training
2.14 Pretreatment Summary
The Pretreatment Summary is an annual report of the status of the SIUs that are discharging
to the POTW. The Other Menu is used to reach the Pretreatment Summary screen.
Other Menu
11/14/92
11:00:58
PCS-ADE Data Entry Subsystem
Other Menu
PCDEMENU
Enter screen JO or 'X' to select an optic
Screen 10: ___
SVIO Single Event Violations
PPS1 Pretreatment Sunmary
EVHR - Evidentiary Hearings
GRNT » Grants
EXIT - Return to Main menu
(PF1.13*Help; PF3.15=Main Menu; PF4.16=Quit; PF8=Bottcm)
157
SDC-005S-034-ST-3003
"E7I3753"
-------
Basic Training Permit Compliance System (PCS)
2.14.1 PPS1 Pretreatment Summary Report
The PPS1 screen is used to enter the data from the Pretreatment Summary Report.
Pretreatment Summary Screen
15:25:09 PRETREATNENT SUMMARY PCDEPPS1
01/14/93 SCREEN 10: PPS1
PERMIT *
IUS FROM WHICH PENALTIES HAVE BEEN COLLECTED (IUPN)
SIUS ON COMPLIANCE SCHEDULES
DOLLAR AMOUNT OF PENALTIES COLLECTED
ACCEPT? Y/K/N/M: v VERSION 2.1 04/27/90
Pretreatment Summary Data Type (SP) - Screen/Acronym/Field Descriptions
NPID*! [PERMIT #] (field length = 9 characters)
This field is both a WENDB and a Key data element.
[TRANS CODE] (field length = 1 character)
This field indicates the action being taken.
168 12/13/93 SDC-0055-034-I>1-3003
-------
Permit Compliance System (PCS) Basic Training
PSED*! [REPORT END DATE] (field length = 6 characters)
This field is both a WENDB and a Key data element. It represents the end date of the
period that the Pretreatment Performance Summary covers. It is required on all SP records
and cannot be changed.
PSSD* [REPORT START DATE] (field length - 6 characters)
This field is a WENDB data element. It represents the start date of the period that the
Pretreatment Performance Summary covers. It is required on all SP records.
SSNC* (field length = 3 characters)
[SIUS IN SNC W/PRETREATMENT COMPLIANCE SCHEDULE]
This field is a WENDB data element. It represents the total number of all significant
industrial users (SIUs) in significant noncompliance (SNC) with pretreatment compliance
schedules, violating compliance schedule milestones by 90 days, or by violating compliance
schedule reporting deadlines by 30 days. Only the following values are allowed in the field:
0-9 Valid Numeric Characters.
NA "Not-Applicable"
* Leading zeros are not required. Entering zeros only will store "0" in the database. The
entire field may be left blank to indicate that no data has been entered. If "NA" is
entered, it must be left-justified.
FENF* (field length = 3 characters)
[NOVs AND AOs ISSUED AGAINST SIUS]
This field is a WENDB data element. It represents the number of notices of violation,
administrative orders, and equivalent actions which have been issued against significant
industrial users by the pretreatment control authority in the past year. Leading zeros are not
required. The entire field may be left blank to indicate that no data has been entered.
JUDI* (field length = 2 characters)
[CIVIL & CRIMINAL JUDICIAL ACTION AGAINST SIUS]
This field is a WENDB data element. It represents the number of civil or criminal judicial
suits filed in court by pretreatment control authorities against significant industrial users
(SIUs) in the past year. Leading zeros are not required. The entire field may be left blank
to indicate that no data has been entered.
SDC-0055-034-ST-301B 12/13/93 ioy
-------
Basic Training Permit Compliance System (PCS)
SVPU* (field length = 3 ; haracters)
[SIUS WITH SIGNIFICANT VIOLATIONS PUBLISHED]
This field is a WENDB data element. It represents the number of significant industrial users
(SIUs) with significant violations in the past year published by the pretreatment control
authority in the largest local daily newspaper located in the municipality serviced by the
control authority. Leading zeros are not required. The entire field may be left blank to
indicate that no-data has been entered.
IUPN* (field length = 3 characters)
[IUS FROM WHICH PENALTIES HAVE BEEN COLLECTED]
This field is a WENDB data element. It represents the number of industrial users from
which monetary penalties/fines (beyond typical user charges) have been collected by the
pretreatment control authority in the past year. Leading zeros are not required. The entire
field may be left blank to indicate that no data has been entered.
SOCS (field length = 3 characters)
[SIUS ON COMPLIANCE SCHEDULES]
This field represents the number of significant industrial users (SIUs) currently required to
meet compliance schedules. Leading zeros are not required. The entire field may be left
blank to indicate that no data has been entered.
SIGN (field length = 3 characters)
[CATEGORICAL INDUSTRIAL USERS IN SNC]
This field represents the number of categorical industrial users in significant noncompliance
(SNC) in the past year. Leading zeros are not required. The entire field may be left blank to
indicate that no data has been entered.
VINO (field length = 3 characters)
[VIOLATION NOTICES ISSUED TO SIUS]
This field represents the number of formal notices of violation or equivalent actions which
have been issued by the pretreatment control authority to significant industrial users (SIUs) in
the past year. Entering zeros only will store "0" in the database. The entire field may be left
blank to indicate that no data has been entered.
170 12/13/93
-------
Permit Compliance System (PCS) Basic Training
ADOR (field length = 3 characters)
ADMINISTRATIVE ORDERS ISSUED TO SIUS]
This field represents the number of administrative orders or equivalent actions issued, by the
pretreatment control authority to significant industrial users (SIUs) in the past year. Entering
zeros only will store "0" in the database. The entire field may be left blank to indicate that
no data has been entered. All leading zeros are suppressed. Numeric fields are displayed
right-justified on Quick Look reports.
CTVL (field length = 2 characters)
[CIVIL SUITS FILED AGAINST SIUS]
This field represents the number of civil suits filed by the pretreatment control authority
against significant industrial users (SIUs) in the past year. Leading zeros are not required.
The entire field may be left blank to indicate that no data has been entered.
CRIM (field length = 2 characters)
[CRIMINAL SUITS FILED AGAINST SIUS]
This field represents the number of criminal suits filed by pretreatment control authorities
against significant industrial users (SIUs) in the past year. Leading zeros are not required.
The entire field may be left blank to indicate that no data has been entered.
NENF (field length = 3 characters)
[SIUS SUBJECT TO ANY ENFORCEMENT ACTION]
This field represents the number of significant industrial users (SIUs) which have been
subject to any type of formal enforcement action by the pretreatment control authority within
the past year. Leading zeros are not required. The entire field may be left blank to indicate
that no data has been entered.
PAMT (field length = 7 characters)
[DOLLAR AMOUNT PENALTIES COLLECTED]
This field represents the dollar amount of penalties/fines (excluding surcharges) collected by
the pretreatment control authority against industrial users in the past year. Dollar amount
should be entered. There is no implicit or explicit decimal point. No special characters ('$')
are allowed and no commas. Leading zeros are not required. The entire field may be left
blank to indicate that no data has been entered.
SDC-0055-034-ST-3003 12/13/93 171
-------
Basic Training Permit Compliance System (PCS)
RDR1 [REGIONAL FIELD 1] (field length = 3 characters)
RDR2 [REGIONAL FIELD 2] (field length = 3 characters)
These are user-defined fields. Check with the PCS Regional Coordinator for their use.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
172 12/13/93 iIJC-OU33-O J^-a 1
-------
Permit Compliance System (PCS) Basic Training
2.15 Evidentiary Hearings
The Evidentiary Hearings data type is a record of the different events that occur for
evidentiary hearings, i.e., the requested hearing date, the date the hearing was granted, etc.
The Other Menu is used to reach the Evidentiary Hearings screen.
Other Menu
11/14/92 PCS-ADE Data Entry Subsystem PCDEMEMU
11:00;58 Other Menu
Enter screen ID or 'X' to select an option
Screen JD: __
SVIO - Single Event Violetions
~ PPS1 - Pretreatwnt Suanary
EVW - Evidentiary Hearings
~ GRNT - Grants
EXIT - Return to Main mnu
CPF1.13*Help; Pf3,15-Main Menu,- PF4.16*Quft; PF8»Botton>
SbC-M55-034-ST-3M3 12/13/93 T73
-------
Basic Training
Permit Compliance System (PCS)
2.15.1 EVER Evidentiary Hearing Screen
Each event code requires the use of a separate data entry screen. The EVHR screen is used
to enter evidentiary hearing data.
Evidentiary Hearing Screen
15:25:55
01/U/93
PERMIT *
-------
Permit Compliance System (PCS) Basic Training
EHEV*! (field length = 5 characters)
[EVIDENTIARY HEARING EVENT CODE]
This field is both a WENDB and a Key data element. It describes the evidentiary hearing
event.
EHDT (Meld length = 6 characters)
[EVIDENTIARY HEARING EVENT DATE]
This field describes the date the evidentiary hearing event occurred.
EHCO (Meld length=30 characters)
[EVIDENTIARY HEARING EVENT COMMENT]
This field contains any comments associated with the evidentiary hearing event.
RDH1 [USER DATA ELEMENT #1] (Meld length = 3 characters)
RDH2 [USER DATA ELEMENT #2] (Meld length = 6 characters)
These Melds are defined by the Region. Check with the PCS Coordinator for their use.
ACCEPT? Y/K/N/M (Meld length = 1 character)
The valid responses to this Meld are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
SDC-0055-034-ST-3003 12/13/93
-------
Bask Training Permit Compliance System (PCS)
2.16 Grants
The Grants data type is merely a reference to whether the facility has a grant, as in a
construction grant, for example. The Other Menu is used to reach the Grants screen.
Other Menu
11/14/92 PCS-ADE Bate Entry Sttevatoi PCDEMENU
11:00:58 Other Menu
Enter eerem ID or 'X' to aeiect an option
Screen ID: ___
SVIO - Single Event Violations
PPS1 Pretreatment SUBMIT
EVHR - Evidentiary Hearings
~ GBMT - Granta
EXIT - Return to Main menu
tPFI.H-Nelp; PF3,15-Mafn Menu; PF4,16»fluit; PF8»Bottom)
T75 : 15713753
-------
Permit Compliance System (PCS)
Basic Training
2.16.1 GRNT Grants Screen
The grant number and a short comment field are the only information available for this data
element. The GRNT screen is used to enter grant data.
Grants Screen
15:26:43
01/14/93
PERMIT * (NP1D)
GRANT NUMBER
-------
Basic Training Permit Compliance System (PCS)
GRNO! [GRANT NUMBER] (field length = 9 characters)
This field is a Key field. It contains the GRANT NUMBER of the grant for this permit.
GRST [GRANT STATUS] (field length = 3 characters)
This field is a code that represents the status of the grant. The only code available at this
time is:
G10 Grant Recorded
GRCO [GRANT COMMENT] (field length=30 characters)
This field represents any comments associated with the grant record.
ACCEPT? Y/K/N/M (field length = 1 character)
The valid responses to this field are:
Y (Yes) accepts the data entered and displays a refreshed screen.
K (Keep) accepts the data entered, displays a refreshed screen and retains the Key data
elements from the previous screen.
N (No) does not accept the data entered and displays a refreshed screen.
M (Main Menu) does not accept the data entered and the system displays the Main
Menu.
T78 12113/93
-------
Permit Compliance System (PCS) Basic Training
3.0 Inquiry
The PCS database system has an on-line retrieval facility called Inquiry. There are three
modes of operation for Inquiry retrievals. They are:
Manager's Inquiry
Prompt Mode
Command Mode
3.1 Manager's Inquiry
The Manager's Inquiry facility is designed to provide reports for managers or those who
need management type information from PCS. The reports are prefprmatted. The system is
menu driven. There is very little knowledge of the system required to obtain on-line reports
or retrievals. Manager's Inquiry prompts, through a series of selection screens, to define the
criteria necessary for the retrieval of information. Selection criteria are defined by entering
an "X" next to a specific criterion followed by pressing . Keyboards may vary in
some cases, so < ENTER > may substitute for .
08/28/89 PCIPNAIK
Welcome to the Environmental Protection Agency's
Permit Compliance System Inquiry Subsystem
Mark selection with an 'X' or '?' for Help
_ PROMPT Node for pre-foraatted reports
_ COMMAND Mode for adhoc queries
x MANAGER'S Inquiry
_ QUIT - Exit Inquiry
Through Manager's Inquiry reports can be generated by (a) selecting a specific facility
number and producing a preformatted report for that facility, or (b) creating a set containing
a number of facilities, which can then be applied to the preformatted reports.
SbC-OOS5-034-ST-3003 12713793 T79
-------
Basic Training Permit Compliance System (PCS)
There are three ways to use Manager's Inquiry. They are:
Create a set using Set Maintenance.
Create a set using Primary Selection Criteria.
. Select a Manager's Inquiry mode report with specific criteria.
3.1.1 Creating a Set Using Set Maintenance
Set Maintenance is used to create a group of facilities (called a set) used in generating
information found in any of the Manager's Inquiry preformatted reports.
These newly-created sets may be saved under a user-defined name and used again. Up to 16
sets can be saved.
To create a set using Set Maintenance select Manager's Inquiry on the Inquiry Main
Selection screen.
08/28/89 PCIPNAIH
Welcome to the Environmental Protection Agency's
Permit Compliance System Inquiry Subsystem
Nark selection with an 'X' or '?' for Help
_ PROMPT Node for pre-formatted reports
_ COMMAND Node -for adhoc queries
x MANAGER'S Inquiry
_ QUIT - Exit Inquiry
180 12/13/93 SDt.-UU55-UJ4-ai-.3Uiw
-------
Permit Compliance System (PCS) Basic Training
A screen will appear offering the option of generating the Manager's reports or creating a set
to be applied to the reports using Set Maintenance or Primary Selection Criteria.
To create a set using Set Maintenance enter "X" next to that option followed by .
The Permit Numbers Set Maintenance screen will appear.
04/11/89 NANAGER'S INQUIRY 12:07:54
MAIN MENU PCQPMA1N
Select One:
x Set Maintenance
_ Primary Selection Criteria
_ Generate Reports
_OUIT
Nark Selection with an 'X'
At this point, a set can be created, modified or deleted.
"?" If you don't remember a set name, typing a "?" at the "Set Name:" line will
display a window listing the names of all sets stored under your user ID.
$t>C-005$-034-ST-3M3 13713733
-------
Basic Training
Permit Compliance System (PCS)
Select any existing set with an "X".
05/22/89
User Ifts MX
Set *«: ? _
Perarft
MANAGER'S INQUMr
Perwt Niaters Set Maintenance
Facility
Remit *
More Penal t Hunters? _
WIT:
1 Nark uith an 'X' to
select an existing Sat
x lUCT
13:51:30
PCQPSETH
Facility Ni
The set "Lucy", in this example, with the stored permits will appear. At this point the set
can be modified by adding or deleting permits.
1 04/11/89
MANAGER'S INQUIRY
PERMIT NUMBERS SET MAINTENANCE
=12:14:21
PCQPSETM
User ID: MLC
Set Name: LUCY_
Perait *
Facility
1. CT0000055 BRISTOL BABCOCK INST
3.
S.
7.
9.
More Perait Ninfcers? _
QUIT:_
LAST UPDATED: 12:13:23 04/11/89
DELETE THE SET? _
Perait* Facility Name
2. CT0000027 J. B. COGGIMS MFC
4.
6.
8.
10.
12/13/93
-------
Permit Compliance System (PCS)
Basic Training
NEW SET NAME
In order to save a new set enter an identifying name followed by
on the "Set Name:" line. The permit numbers for the new
set may then be entered.
DELETING A SET An existing set can be deleted by selecting the "Delete the Set?"
option on the right-hand portion of the Permit Numbers Set
Maintenance screen.
04/11/89
MANAGER'S INQUIRY
PERMIT NUMBERS SET MAINTENANCE
> 12:23:15
PCQPSETM
User ID: MLC
Set NM»: LUCY2_
Permit * Facility
Permit *
Facility N<
1.
3.
3.
1
9.
11.
13.
15.
17.
19.
AR0022667
OC0026026
OK0025119
LAOQ04804
LA0004715
LA0003859
AR0022705
TX0029742
OK0025Q20
TX0003123
CHEVRON OIL CO-PRESC
EDNOND. CITY OF CPUA
FREEMAN'S LS AUCTION
GETTY OIL CO-PLAQUEN
GULF OIL CORP-SOUTH
KERR-MCGEE CHEM CORP
MISSISSIPPI CKEN.COR
PHILLIPS PETROLEUM C
RIKGLING COMH. LS AU
SUN Oil CO-CHAMBERS
2.
4.
6.
g.
10.
12.
14.
16.
18.
20.
OK0025241
NM002S542
TX0003735
NK0025411
NN0027120
TX0002992
AR0021857
AR0022748
LA0003964
HN0027103
DAVIS HATCHERY
FORNI BROTHERS DAI
GETTY OIL CO-EAGLE
GOOD SERVICE DAIRY
INDIAN LAND-PUEBLO
KIRBY LUMBER
PARIS. CITY OF
RALSTON PURINA CO
SOUTHERN NATURAL 6
USAEC-LOS ALAMOS (
More Permit Hunters?
QUIT:
When the set has been created type "X" at the QUIT option followed by . The new
set will be saved and the system will exit from Set Maintenance and return to the Manager's
Inquiry Main Menu screen.
SDC-0055-034-ST-3003
12/13/93
183
-------
Basic Training Permit Compliance System (PCS)
3.1.2 Creating a Set Using Primary Selection Criteria
The Primary Selection Criteria option of creating a set was designed for users with little
experience on data terminal keyboards.
This option prompts you to specify up to eight criteria that will characterize the facilities in
the set.
The procedures are simple: select a criterion by entering "X" followed by .
Inquiry will display a window that lists the choices for thai criterion. Once selection is
complete, press and Inquiry will display all facilities that meet the selection criteria.
Enter "X" next to Primary Selection Criteria on the Manager's Inquiry Main Menu screen.
04/11/89 MANAGER'S IMUIRY 12:07:54
MAIN MENU PCOPHAIN
Select One:
_ Set Maintenance
x Prinary Selection Griterie
_ Generate Reports
_«U1T
Nark Selection with an 'X'
184 12/13/93 SDC-OU55HM4-&1-JUU.J
-------
Ftermit Cfflnplh"1^ System (PCS) ____ Baric Training
The Primary Selection Criteria screen will appear and ask what criteria will be applied when
selecting the facilities for the set.
5/04/89 »i MI ...,.. in r.. MANAGER'S IKQUIRT *»imnmmmm^i 11:46:49
PrlMry Selection Criteri*
Select By:
Facility Keae
~ Major/Minor Indicator
~ Facility Type
lesion 05 (default)
~ State
Fernit Expiration Date
_ Start Date
~ End Date
USGS Hydrelogical Basin Codes
_ Standard Industry Classif ication(s] _ River BasirKs)
QUIT : _
SDC-0055-034-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
The Primary Selection Criteria are discussed below.
Facility Name
This criterion allows the user to specify a facility name or a range of names to be viewed.
After entering "X" next to this criterion a display window will appear for the user to enter an
alphabetical range.
Prlnary Selection Criteria
Select By:
X Facility
Najo * ................
I Feel J
Regl 1 FacHtty D
] Starting Fran : AA
Permit I Ending at : M _
Star * ----- -------------------
~ End Date
USCS Hydrelogical Basin Cades
Standard Industry Classifications) _ River Basin**)
QUIT : _
For example, by entering "AA" in the "Starting From" line and "M" in the "Ending at"
options followed by , Inquiry will respond by recording the choices on the Primary
Selection Criteria screen. At this point, press < CR> to see a list of the selected facilities
or to the next criterion.
Inquiry will display all facility names (AA - ZZ) if a facility name or range is not specified.
186 12/13/93 SDCHXJ55-O34-ai-JUUJ
-------
Pennit Compliance System (PCS) Basic Training
Major/Minor Indicator (MADI)
This criterion allows for specifying whether major or minor facilities will be included in the
set.
If "X" is entered next to the Major/Minor Indicator followed by , Inquiry will
display a window for Major/Minor Indicator selection.
05/04/891 " "'""i iT-nni MANAGER'S INQUIRY 11:47:45
Primary Selection Criteria
Select By:
x ractucy
x Najor/Min
_ Facility
_ Region
_ State
Permit Expir
_ Start Date
End Date
1
Major/Minor Indicator 3
]
_ Major 1
_ Minor 1
USGS Hydrological Basin Codes
_ Standard Industry Classifications) _ River Basin(s)
QUIT :
Inquiry will respond by recording that indicator on the Primary Selection Criteria screen.
to the next criterion or press for a list of facilities with a Major or Minor
indicator.
Inquiry will display both major and minor facilities if no selection is made.
SDC-0055-034-ST-3003 12/13/93 187
-------
Basic Training Permit Compliance System (PCS)
Facility Type
This criterion specifies whether municipal, industrial or Federal facilities will be included in
the set.
A display window for the Facility Type criterion will appear when'selected with an "X" and
< CR >. Next, select the appropriate facility type with an "X" and press < CR >.
05/22/99 i NMI in MANAGER'S INQUIRY ' ' ' 14:06:07
I'M wry Selection Criteria
Select By:
x Facility
X Major/ Nf
x Facility
Keg ion
_ State
Penatt Expfr
Start Oat
End Date
Facility Type
Municipal
~ Federal
Industrial
3
1
3
3
3
3
1
3
US6S Hydrologtcal Basin Codes
Standard Industry ClassiflcationCs) _ River fiasin(s)
QUIT :
Inquiry responds by recording that facility type on the Primary Selection Criteria screen.
Only one facility type can be selected at a time. All facility types will be displayed if no
facility type is selected.
Press to look at the specified selection (and any other criteria previously selected) or
to the next criterion.
18JJ 12/13/93 SDC-0055-UJ4-M-JUU.3
-------
Permit Compfiance System (PCS)
Basic Training
Region
This criterion specifies the Region where the facilities are located. In most cases only one
Region is accessed at a time.
Select this criterion with an "X" followed by . A window for Region selection will
appear. Select the Region.
ER'S INQUIRY i
>14407:15
Prinry Selection Criteria
Select By:
X Facility
X Major/ Ni
X Facility
X Region 0
x State
emit Expir
Start Dat
~ End Date
US6S ttydrologicei Basin Codes
~ Standard Industry Classification]
J
OUIT *
CHOOSE ONE REGION
01
02
03
04
05
I 06
07
~ 08
09
10
to the next criterion or press to see the facilities in the specific Region
selected. Mark them with an "X" if they need to be included in the set.
Inquiry will display all the facilities in a Region if no selection is made.
SDC-0055-fl34-ST-3003
12/13/93
189
-------
Basic Training
Permit Compliance System (PCS)
State
It is possible to specify which State or States to use when selecting the facilities for the set.
(A Regional user must first select the Region criterion in order to select the State criterion.)
Select the State(s) within a Region with an "X" and press .
05/22/89
I'ff INQUIRY
14:07:15
Prinary Selection Criteria
Select By:
X recility
X Nejor/ N1
X Facility
X Region 0
x State
Penrit Expir
Start Oat
~ End Date
USGS Mydrological Basin Codes
Standard Industry Classification^)
QUIT :
SELECT ANY STATES
IL
IN
NI
MM
OH
UI
Press to see a listing of facilities within the selected State(s) or to the next
criterion. Inquiry will display all the facilities in the States within a Region, if a single State
is not specified.
T90
12/13/93
bDL.-UU53-U.J4-a 1 oUUo
-------
Permit Compliance System (PCS)
Rasic Training
Permit Expiration Date
Selecting this criterion selects facilities having permits that expire within a certain timeframe
or on a specific date. First, a window will appear asking for a permit start month.
05/22/89<
t'S INQUIRY'
>14:08:27
Primary Selectien Criteria
4
Select By:
X Facility
X Major/ Hi
X Facility
Xttmnlnn ft
Region u
X State I
Fermi t Expir
x Start Dat
_ End Date
USGS Hydrological Basin Codes
~ Standard Industry Classif icat
OHffT * ^
Ml* 1 ^ ~
Expiration
Start Date
Mnaiafc
Honrn
January
February
March
April
_ Kay
June .
~ July :
~ August
Sept ]
October ]
Noveaber ]
1 December :
r
I
1
1
1
1
1
1
1
Select a month by entering an "X" followed by . Next, a window will appear for
selection of the Start Year. After making a selection for the Start Year, the same cycle of
screens will appear asking for a permit end date, month and year. (The screens are not
shown).
After making the selections, press to display a list of facilities for the specified
permit expiration date range. These selections can be included in the set by marking them
with an "X". to the next criterion to complete the selection criteria.
Inquiry will display facilities with any expiration date if no permit expiration date is
specified.
SDC-0055-034-ST-3003
12/13/93
191
-------
Basic Training Permit Compliance System (PCS)
USGS Hydrologic Basin Codes
This criteria provides the USGS Hydrologic Basin Code Sub-field Selection Criteria menu.
The United States Geological Survey has created Hydrologic Basin codes. They provide a
means to determine the area into which a facility discharges, and the particular stream
segments into which a facility discharges, so the impact of discharges into a waterway can be
evaluated. The codes aid in retrieving Limits and Discharge Monitoring Information on
particular stream segments so the impact of discharges into a waterway can be evaluated.
09/2V93 i i NI j MANAGER'S INQUIRY i. i "i m 11:46:49
USCS Hydrologic Basin Code Sub-field Selection Criteria
Select Ones
_ USGS Region
_ USGS Sub-region
_ USGS Accounting Unit
_ USGS Cataloging Unit/Nydrologic Basin Cd
OUIT :
192 !l27I3/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
The USGS Hydrologic Basin Code Sub-field Selection Criteria menu contains the following
selections:
USGS Region
- A two character hydrologic code subdividing and identifying each region of the
United States. This code provides the first two characters of the USGS Hydrologic
Basin Code.
USGS Sub-region
- A four character code consisting of Region and two additional characters which
further subdivides and identifies basin areas of the United States. This code provides
the first four characters of the USGS Hydrologic Basin Code.
USGS Accounting Unit
- The combination of Region, Sub-region, and two additional characters used by USGS
for managing the National Water Data Network. This code provides the first six
characters of the USGS Hydrologic Basin Code.
USGS Hydrologic Basin Code (Cataloging Unit)
- The combination of Region, Sub-region, Accounting Unit, and two additional
characters used by the USGS Office of Water Data Coordination in maintaining the
Catalog of Information on Water Data. These eight characters make up the USGS
Hydrologic Basin Code.
SDC-0055-034-ST-3003 12/13/93 193
-------
Basic Training Permit Compliance System (PCS)
Standard Industrial Classification Code (SIC2)
Facilities from a specific industry, as classified by the Standard Industrial Classification
codes (SIC2), can also be selected.
Choose the Standard Industrial Classification (SIC) criterion with an the usual "X" followed
by . A list of SIC codes will appear.
Nurber Selected:
ILLINOIS
BITUMINOUS COM. MB U6MITE
~ BITUMINOUS i LIGNITE MINE SERV
~ CRUDE PETROLEUM I NATURAL GAS
~ OIL AMD GAS FIELD SERVICES KEC
~ DIMENSION STOKE
1421 NO DESCRIPTION
" CRUSHED AND BROKEN LIMESTONE
CRUSHED AND BROKEN GRANITE
~ 1441 NO DESCRIPTION
~ CONSTRUCTION SARD AMD GRAVEL
~ INDUSTRIAL SAND
FLUORSPAR
~ NONMETALLIC MINERALS SERVICES
NONMETAUIC MINERALS, NEC
~ SINGLE-FAMILY HOUSING CONSTRUC
~ WATER SEWER AM) UTILITY LINES
~ HEAVY CONSTRUCTION NEC
CONCRETE UORK
' STRUCTURAL STEEL ERECTION
OUIT:
Select up to five SIC codes by marking them with an "X". The SIC codes will be recorded
on the Primary Selection Criteria screen when is pressed.
As with the other criteria, to the next criterion or press , to see the
facilities specified by the previous criteria.
Inquiry will display facilities with all SIC codes for selection if an SIC code is not specified.
154 12/13/93
-------
Permit Compliance System (PCS) Basic Training
River Basin (BAS4)
The last criterion, River Basin, allows facilities on a specific river basin to be included in the
set.
The procedures here are the same as the other seven criteria. Enter "X" followed by
to see a listing of the river basins within a specific Region or State.
PRESS EMTER TO CONFIRM SELECTIONS
ILLINOIS
X NE/PENOBSCOT R.
X OR/NUSKINOM R.
X OR/SALT R.
X OR/UABASH R.
X OR/CUMBERLAND R.
OR/OHIO R-MAIN STEM
IM/RAINY R.
~ UN/L. UP MISSISSIPPI
UN/WISCONSIN R.
UN/MISS. R-UAPSIPIN!
UN/ROCK R.
OU1T:
It is possible to select up to 5 river basin codes at one time. These river basins will be
recorded on the Primary Selection Criteria screen.
Inquiry will display facilities with all river basin codes for selection if no river basin code is
specified.
Press and Inquiry will list the facilities Jhat meet all the primary selection criteria
designated.
SbC-MSS-034-ST-3003 13713753 ' 155
-------
Basic Training Permit Compliance System (PCS)
Next, select the facilities with an "X" to be included in the set.
PRESS £NTE8 TO CONFIRM SELECTIONS Facilities Selected:
ILLINOIS X Select ail displayed
X BATAVIA. CITY OF ILQ02Z543
X BAXTER HEALTHCARE. INC. ILOOZ407A
X BEAROSTOUN SWG TRNT PLT 1LOOZS135
X BELLEVILLE. VILLAGE OF IL0021873
X BELVIDERE. CITY OF ILOOZ7685
X BENSENVIUJE, VIUAGE OF IUM21849
X BENTON, C1TT OF U0022S6S
X BLOOHINGDALE SOUTH STP ILODZT130
X BLOOHIMCTOH-IIORHAL SJK ILOOZ7731
X BOLINGBROOK STF IL0032689
X BORDER INC. IL00013SO
At this point a set has been created. It must be named before applying it to any of the
Preformatted reports. There are three possible options: (1) creating a permanent set by
saving it, (2) temporarily saving the set under the Inquiry-generated name of "TEMPSET"
(3) ignoring the selections made and starting over.
155 15713753
-------
Permit Compliance System (PCS)
Basic Training
ILLINOIS Select all displayed
~ C1PS-COFFEEN
~ CIPS-GRAHD TOUER
CIPS-MJTSONVILLE
CIPS-NEREDOS1A
"* CIPS-NEVTON
" CIRCLE SMELTING, 1HD
" CITIZEN UTILITY CO.-PLT«
~ CITIZENS UTILITY COMPANY OF
~ CLARK OIL REFINING
" aiNTON SANITARY DISTRICT
1L
Select one of the following:
Save set under your
Save set under reserved
'TENPSET'
Ignore selections
1
30
1ELA
] CO
JET
IN
1
3AID
IL0000108
U0000124
IL0006120
JL0000116
ILOM9191
U0005231
JL0032727
IL0032735
IL00012U
JLM23612
IL0028Z15
IL0002178
IL0002186
IL0002194
IL0002208
110002216
IL0002224
IL0002232
IL0002241
QUIT: x
After naming the set, Inquiry will save it under the user ID and it will become one of the
sets stored under Set Maintenance. The set can then be used repeatedly to generate
Preformatted reports.
If the set is to be used only during the current session, enter "X" next to "TEMPSET"
followed by .
Inquiry will temporarily save the set under "TEMPSET" and go directly to the Report
Selection screen where reports with the newly created "TEMPSET" can be generated. When
the Inquiry session is terminated, "TEMPSET" will be deleted from the system.
If either changes are needed to the set or to create a different set, enter "X" next to the
"Ignore" option followed by . The selections will be deleted and the user can start
again.
197
SbC-OOS5-034-ST-3(X)3
12/13/93
-------
Basic Training Permit Compliance System (PCS)
3.1.3 Selecting a Manager's Inquiry Report
The next step is to obtain specific information on the facilities selected.
Each of the Manager's Inquiry reports is in a fixed format with the most useful and
commonly sought after information on different aspects of NPDES permits.
There are nine reports that can be produced.
Facility Directory Enforcement Actions
Facility Overview Outfall Limits
Permit Events Report DMR Overview
Inspections Evidentiary Hearings
Compliance Schedules and Violations
3.1.4 Selecting an Inspections Report
This report lists the permit number, facility name, facility type, type of inspection, inspection
date, inspector, QA-based data, and any comments.
The report selection process is the same as that of Primary Selection Criteria; that is, criteria
for the report is entered through selection screens.
T5S 15713753
-------
Compliance System (PCS)
Basic Training
To begin generating an Inspections Report enter "X" next to "Generate Reports" on the
Inquiry Main Menu followed by .
04/11/89 * MANAGER'S IHQUIRY '
MAIM MENU
12:07:54
PCQPHAIN
Select One:
_ Set Maintenance
_ Primary Selection Criteria
x Generate Reports
.QUIT
Inquiry will display the Report Selection screen.
04/26/89
MANAGER'S INQUIRY
Report Selection
Select One:
Facility Directory
~ Facility Overview
~ Permit Events
x Inspections
_ Compliance Schedules
~ Enforcement Actions
Outfall Limits
~ OHR Overview
** Evidentiary Hearings
CAJIT: _
7:02:14
PCQPRPTS
T27T375T
T55
-------
Basic Training Permit Compliance System (PCS)
The Report Selection screen will prompt for the selection of one of nine reports. Select the
Inspections Report with "X" followed by .
The Inspections Permit/Set Selection screen will appear.
**** Manager's Inquiry *** 10:48:50
Permit / Set Selection PCQPRPTS
Facility Directory
Select One:
X Permit Number
Set
The Permit/Set Selection screen offers the option of generating a report based either on a
single permit number or a set of permits.
** Manager's Inquiry ** 10:48:50
Permit / Set Selection PCQPRPTS
Facility Ofrectory
Select One:
x Perm » +
Set 1 J
] 1
] Enter Permit Number: ________ 1
+..... .., *
200 12/13/93 &DC-OU55-OJ4-M-.JUU.J
-------
Permit Compliance System (PCS) Basic Training
If the Permit Number option is selected, enter the permit number in the space provided
followed by < CR>. Use this option to look at a single permit only.
In the second option, choosing a set, enter an "X next to "Set Name:" followed by .
A .window will appear on the Permit/Set Selection screen prompting for the set name.
04/26/89 **** Manager's Inquiry ** 09:02:51
Permit / Set Selection PCQPRPTS
Inspections
Select One:
Permit timber
x Set -i **
1
Enter: 1
Set Mane: I
UserID: SFL 1
Use Partial Set: (Nark with 'X') 1
auiT: ..
Enter "?" in "Set Name:" followed by . Inquiry will display the names of all the
sets saved under the user ID. Make a selection of any set with an "X".
To produce the report using only a portion of the facilities in a set, enter a set name and
mark an "X" next to "Use Partial Set". Inquiry will display all the facilities in the set.
Mark those facilities with an "X" that will be applied to the reports.
After making a selection, press .
SbC-0055-034-<5T-3003 13713793 25T
-------
Basic Training Permit Compliance System (PCS)
Inquiry will display the Inspection Criteria screen. Note that the first permit, IL0000035 -
AMOCO-WOODDRTVER, is ready for inspection criteria to be applied to it.
04/26/89 **** MANAGER'S INQUIRY *** 09:03i18
Inspection Criteria PCQPINSS
1L0000035 - ANOCO-UOODRIVER
inspection Date
Start Date
~ End Date
_ Inspection Type
_ Inspector
_ Tally
_ Restart Set
QUIT : _ Press to view report
The system is now ready for the user to select the criteria for the Inspections report.
202 12/13793 SDC-0055-034-ST-3003
-------
Permit rifT"8""* System (PCS) Basic Training
Inspection Date Range
Specify the timeframe within which a certain facility has been inspected. Select this criterion
in the usual mannerwith an "X" followed by .
Inquiry will respond by displaying an Inspection Stan Date window.
Inspection Date
X Start Date 1/1/88
_ End Date
_ Inspection Type
_ Inspector
. Tally
_ Restart Set
OU1T : Press to view report
SbC-M5$-034-ST-3W3 12713753 203
-------
Basic Training
Permit Compliance System (PCS)
Enter an "X" next to the appropriate month followed by . Next, a start year window
(not shown here) will appear. Follow the same procedure.
11
110000035
Inspection
x Stsrt
.Cnd Da
_ Iraptctio
_ Inspector
_ Tally
Restart
QUIT : _ Press
rapection Criteria PCQPIMSS
Inspection
Start Data
Month
........
* January
February
March
I April
"June
"July
'August
_Sept
October
November
"December
^.
1
h
Inquiry will clear the window from the screen and enter the selected date on the Inspection
Criteria screen.
To specify an end date place an "X" next to End Date and follow the same procedures used
in selecting the Start Date.
If no timeframe is specified, Inquiry will display all inspection dates for the selected permit.
SDC-0055-034-iJT-300:J
204-
12/13/93
-------
Pprmit
System (PCS)
Basic Training
Inspection Type
The Inspection Type criterion is used to identify those facilities that have undergone a
specific type of inspection. Select this criterion with an "X" and < CR >.
Inquiry will then display the Inspection Type screen.
Inspe
UM00108
Inspec
X S
X E
x Imp
Tsll
Res
Inspection Type
PRETREATMENT COMPU INSPECTION
PERFORMANCE AUDIT
COMPLIANCE BIOMONITORIKG
COMPLIANCE EVAL (NON-SAMPLING)
CORPS OF ENGINEERS INSPECTION
COMPLIANCE SAMPLING
TOXICS INSPECTION
RECONNAISSANCE
ENFORCEMENT CASE SUPPORT
DIAGNOSTIC
INDUSTRIAL USER INSPECTION
PRETREATMENT AUDIT
IND. USER INSP. U/ PRET. AUDIT
FOLLOW-UP INSPECTION
PRETREATMENT FOLLOU-UP
QUIT :
Press
-------
Basic Training
Permit Compliance System (PCS)
Inspector Type Criterion
The Inspector Type criterion identifies those facilities with a specific inspector type.
If this criterion is selected, Inquiry will display the Inspector Codes window.
04/26/89
I rape
1L0000108
inspec
X S
X E
X Imp
x Insp
MANAGER'S INQUIRY
O9.'10:03
QUIT:
_ *»
Press
-------
Pennift fiHnpFa"* System (PCS) Basic Training
Producing a Tally
The Tally feature is used to determine the number of records in the database that satisfy the
selection criteria.
To produce a tally, enter "X" at the Tally criterion option.
Inquiry will calculate the number of records that meet the selection criteria.
04/26/89 MANAGER'S INQUIRY TALLY RESULTS 14:35:27
Inspection Report
There Here a total of 5 Facility(s) checked.
There Mere 58 Inspections Records fond for 2 Facility(s).
SDC-0055MD34-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
Displaying the Report Output Data
The Inspection Report may be produced directly from the criteria screen or after the Tally
report is completed. To produce an Inspections Report, press and make no entry at
the Tally option.
An example of an Inspections Report is shown below.
MANAGER'S INQUIRY 14:39:34
Inspection Report PCQPINSR
U000003S - ANOCO-UOODRIVER
Facility Type: INDUSTRIAL
COMPLIANCE SAMPLING Inspection Date: 07/12/78
Inspector: STATE « Data-Based:
Consents: OUT/780805/780810/ EF/ENFORCEMENT PENDING
Facility Type: INDUSTRIAL
COMPLIANCE SAMPLING Inspection Date: 07/26/79
Inspector: STATE OA Data-Based:
Cements: . 7909U
Frequently, when looking at a set of permits, Inquiry will indicate that more output can be
obtained. Press and the next screen of information will be displayed.
When all of the report data has been displayed, the following message will appear: End of
Report - Enter to continue.
Entering will return to the Manager's Inquiry Report Selection screen where another
report can be selected or Inquiry can be exited from.
To end the Inquiry session, type "X" followed by at the "Quit" line. The system
will exit Inquiry and return to TSO.
208 12713793
-------
Permit r-nmpiiaiM-* System (PCS) Basic Training
3.2 Prompt Mode
Inquiry's Prompt Mode provides fixed format reports containing the most useful and most
commonly sought after information about a specific aspect of NPDES permits.
Information ranging from broad summary data to detailed measurement data, at the level of
an individual outfall, can be accessed quickly for review. This makes Prompt Mode a
valuable tool for those who need quick access to information on NPDES permits.
This section of the manual will cover an Inquiry Prompt mode session for producing the
Facility Directory Report. The main topics are:
Selecting a Prompt mode report,
Specifying selection criteria,
Verifying selection criteria (and reentering, if appropriate),
Getting a tally of the number of permit records selected by the criteria and/or displaying
the report output data.
SbC-M55-034-ST-3003 I57T3753 205
-------
Basic Training Permit Compliance System (PCS)
3.2.1 Selecting a Prompt Mode Report
To enter Prompt mode enter "X" on the Inquiry Main Selection Screen. -
Welcome to the Environmental Protection Agency's
Perait Compliance System Inquiry Subsystem
Nark selection with an 'X' or '?' for Help
x PROMPT ftode for ore-formatted reports
_ COMNMO Node for adhoc queries
_ MANAGER'S Inquiry
_ QUIT Exit Inquiry
Inquiry will respond by displaying the Prompt Mode Main Selection Screen.
03/21/89 **** PCS Inquiry - Proopt Node **** PCIPPRNP
Main Selection
Report Description
COD Cod* t Description Report
DIR Facility Directory
FAC Facility Overview Report
LIN Outfall Limits Report
OMR DNR Overview Report
SCK Compliance Schedule t Violations
INS Inspection Report
PER Permit Tracking Report
KEA Evidentiary Hearing Report
ENF Enforcement Action Report
(Q)uit - to end Inquiry session (C)omnand - to enter Coansnd Node
Enter Selection
210 12/13/93 SDC-0055-034-ST-3003
-------
Permit CTlJance Systan (PCS) Basic Training
Respond to the "Enter Selection" prompt by entering the three-character name of the report
to be produced.
The short forms of the report names (entries in the 'Report' column of the selection screen)
are the selection names for each of the reports.
To select the Facility Directory type DIR.
3.2.2 Facility Directory Report
The Facility Directory Report lists basic identifying data on permitted facilities selected
according to user-specified values. For example, the Facility Directory Report lists the
Permit Number, Facility Name, Major/Minor Indicator, Permit Issue and Expiration dates,
and the City, County and State where the facility is located for each permit included in the
report.
To get a report that contains this information for only those permits of interest, qualify the
selection criteria on the Facility Directory Selection Screen.
To produce the Facility Directory Report, entry of at least one of the following selection
criteria is required:
Facility Name Major/Minor Indicator
Region State
County Code Type of Ownership
River Basin Code Permit Expiration Date
Standard Industrial Classification (SIC)
Since the selection of permit files for the Facility Directory Report can be based on any
single criterion or on any possible combination of them, it is possible to use this report to
answer a wide variety of questions:
What is the permit number of a facility known only by name?
Which facilities in a given county are major dischargers?
Which facilities located in a particular river basin are engaged in a specific industry (SIC
code)?
What are the publicly-owned facilities in a particular county whose permits will expire
during the current fiscal year?
SbC-0055-034-ST-3003 15713753 ZTT
-------
Basic Training Permit Compliance System (PCS)
The Facility Directory Report Selection Screen is displayed below:
M/04/89 *" «8 Inquiry » Prompt Node *» POIR
Facility Directory Selection Screen -
Facility
Start C*):-» - End C*J* *.
Major/Minor Indicator <*)*..*.,..
Region (*) ,,.....,..
State <*J *.......»....
State/County Code <).«..,**,
Type Ownership Code (*)....*
SIC I * t*).»..*.. »...
4 Ois. Maj/Min River Basin C*>:
Permit Expiration Date Range Caa MMDDTY)
Start <*>: * - End <): *
Talty (y/n): N
Cmd: Press to produce output
Selection criteria for the Facility Directory Report:
Facility Name Criteria - 1 afld End Rane Otional^
The Facility Name criteria consists of Start and End fields where a name or a range of names
for the report can be specified. The Facility Name criteria are entered to:
List basic identification data on a specific facility whose name is known.
List one or more of several facilities with the same or similar name (for example, in
cases where two or more facilities are operated by a single owner).
Find a facility by name, without knowing the correct spelling of the name.
To specify a facility name or range of names, enter up to eight characters of the name in
both the Start Field and the End Field. An entry in the Start Field will specify the beginning
value for a range of names. An entry in the End Meld will specify the ending value for the
range of names. If only one facility name is of interest, specify the same characters in the
Start Field and the End field. The value for the Start Field must be less than the value for
the End Field or an error message will be displayed.
' 12/13/93 SDC-Q055-034-5T-3003
-------
Permit fff'"pl""MH' System (PCS) Basic Training
An "*" is entered in both the "Start" and "End" fields to locate any permits meeting the rest
of the criteria specified. This will instruct Inquiry to select facilities with name values from
"AA" through "ZZ999999" or all facilities.
If selection of the Facility Name criteria is followed by , Inquiry will produce the
report using default values for any unspecified selection criteria.
To move between fields use the key. Inquiry will move to the next selection
criterion on the Facility Directory Report Selection Screen, the Major/Minor indicator:
Major/Minor Indicator Criterion (optional)
The Major/Minor Indicator Criterion is used to specify and display the major/minor status of
a facility.
One of three choices can be specified:
Select major discharging facilities only - For major dischargers only, enter "M".
Select minor discharging facilities only - For minor dischargers only, enter a "BLANK".
Select major and minor discharging facilities - To list both major and minor dischargers,
an "*" is entered.
If selection of the Major/Minor Indicator criterion is followed by , Inquiry will
produce the report using the values selected and any values for unspecified criteria will be
the defaults. Move to the next selection criterion with .
Region Criterion (optional)
The Region criterion is used to specify the Region for the report.
Enter the two-digit code for a specific Region.
Since PCS users now have national access capability, enter a specific Region code.
When a Region is selected followed by , Inquiry will produce the report using the
Region criterion and any default values for the other unspecified criteria. Move to the State
Selection criterion field by using the key.
SDC-0055-0343.T-3WJ3 12/13/93 213
-------
Basic Training Permit Compliance System (PCS)
State Criterion (optional)
The State criterion is used to specify the State to be displayed on the report. After selecting
a Region to view, enter a two-character State code for those States in the specified Region.
If the State criterion entered is followed by < CR>, Inquiry will produce the report using
the State criterion and any other criteria selected. Inquiry will use the default values of any
unspecified criteria.
County Code (optional)
The County Code criterion is used to specify the counties to display on the report. To view
a listing of the county codes, enter "?" in the first space for the County Code followed by
.
04/04/69 *** PCS Inquiry - Proof* Node *** PCIFDIR
Facility Directory Selection Screen
Facility Name
Start <*3r End (): *
Major/Minor Indicator <*).
Region (*)
State <*)
State/County Code <}
Type of Ownership Code C*>.....
SIC Code ().....»............
4 Dig. Maj/Nin River find basin
4.............................................. ..--.+
1 1
1 This field indicates State/County code. 1
} Exaaples; CT009, VA013 3
1 1
J Do you wish to see a Ifst of available values? , Inquiry will display a listing of the County Codes for the specified State.
To return to the Selection Screen after viewing the codes, press .
21412/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
To list only the facilities that are located in a specific county, enter the 2-character alphabetic
State code plus the 3-digit county code.
An '*' must be entered to display any permit in any county. Inquiry will use the default of
all county codes.
When is pressed, Inquiry will produce the report using the county code criterion and
any default values for any unspecified selection criteria. to the next selection
criterion to continue selecting criterion for this report.
Type of Ownership Criterion (optional)
The Type of Ownership criterion is used to select facilities with a specific type of ownership.
To view a listing of the Type of Ownership codes, enter "?" in the first space for the code
followed by .
04/04/89 *** PCS Inquiry Preopt Mode **** PCIPD1R
- Facility Directory Selection Screen -
Facility I
Start (*): * - End <*>: *
Major/Minor Indicator <*)...... *
Region <*> *
State <>... *
State/County Coda <«)....,... *3
rype of Ownership Code (*) 7_
SIC Code <*) *
4 Dig. Naj/Min River Basin <>: *
+........................-............._..-.._.........-...-.....+
I 1
] This field fa a code far Type of Ownership code. 1
] Examples: FED, PRI, PUB 3
I 1
1 1
1 Do you Hish to see a list of available values? (Y/N): y 1
+.................._................................ ...«
Entering " Y" in response to "Do you wish to see a list of available values ?" followed by
will display Type of Ownership codes.
To return to the Selection Screen after viewing the codes, press .
SDC-0055-034-ST-3003 12/13/93 115
-------
Basic Training Permit Compliance System (PCS)
To list only those facilities of a specific type of ownership (that also meets other selection
criteria), enter one of the Type of Ownership codes.
To list the facilities that meet the other selection criteria regardless of the type of ownership,
enter "*".
After entering the Type of Ownership, press < CR>. Inquiry will produce the report using
any criteria selected up to this point and also the default values for any unspecified selection
criteria. After selecting Type of Ownership, to the next field to continue
selections for the report.
Standard Industrial Classification (SIO Code Criterion rootional)
Using this criterion instructs Inquiry to list only those facilities engaged in a particular type
of industrial activity classified by the SIC codes.
To view a listing of the SIC codes, enter "?" in the first space for the SIC selection criteria
followed by .
04/04/89 ** WS Inquiry - F-rcapt Node **** PCIPOIR
Facility Directory Selection Screen -
Facility Home
Start (*>: * - End (>:
Major/Minor Indicator {) *
Region () _
State <*) *_
State/County Code {*) *
Type of Ownership Code () *_
SIC Code ()................... ?
* Dig. Naj/Nin River Basin <): *
This is the 'principal activity causing the facility 3
discharge' code* 1
Exanptes: 0131 (cotton), 1477 (sulfur) 3
Do you wish to see a list of available values? (Y/N): y ]
Enter " Y" in response to "Do you wish to see a list of available values?" followed by
and Inquiry will display the SIC codes.
12713753
-------
Permit Compliance System (PCS)
Basic Training
Press to return to the Selection Screen after viewing the codes.
Entering "N" followed by returns to the selection screen at the SIC criterion.
To specify a SIC code, enter the appropriate 4-digit numeric code.
To list facilities meeting the specified selection criteria regardless of industrial classification,
an '*' must be entered. Inquiry will use the default value of all SIC codes.
Press to produce a report using all the values selected up to now, or to
the next selection criterion.
Major/Minor River Basin Code Criterion (optional)
This criterion instructs Inquiry to list only those facilities within a specified major or minor
river basin.
To see a listing of the Major/Minor River Basin codes, enter "?" in the first space for the
code followed < CR >.
04/04/89
« PCS Inquiry - Pronpt Node *
facility Directory Selection Screen -
facility Nam
Start <*): *_
- End (*>: *
Major/Minor Indicator <).
Region (*)
State ()
State/County Code <)
Type of Ownership Cede (>
SIC Code (*>
4 Dig. Maj/Nin River Basin <*>: ?
PCIPDIR
Cndr
This is the Major/Minor river basin code used to
dfttenaine what river basin a facility is located on.
Example: '0316' - James River; '1104' - Gila River.
Do you wish to see a list of available values? (Y/N): y
SDC-0055-034-ST-3003
12/13/93
L\. I
-------
Bask Training Permit Compliance System (PCS)
Entering " Y" in response to "Do you wish to see a list of available values?" followed by
will display the Major/Minor River Basin Codes specific to the selected Region of
State.
To return to the Selection Screen after viewing the codes, press .
To specify a river basin, enter the appropriate 4-digit numeric code followed by .
NOTE: The 4-digit major/minor river basin code consists of a 2-digit major river basin
code plus a 2-digit minor river basin within the major river basin system.
Selection of this criterion specifies only the facilities located in the
major/minor river basin.
Enter '*' for Inquiry to default to all river basin codes. Press to see the report
based on the selection criteria and any other default values not specified, or to the
next field.
Permit Expiration Date Range Criterion (optional)
This criterion instructs Inquiry to list only those facilities whose NPDES permits expire (1)
on a specific date or (2) within a specified range of dates.
The date(s) must be entered in the 'MMDDYY' format. This means that the date entry must
be six characters long only-month, day, and year entries must each be two characters long.
The entry for "January 1, 1989" would be '010189'.
To select only those permits expiring on a specific date, the same date must be entered in
the Start and End fields.
To specify an expiration date range, enter the appropriate beginning date (for example,
010182) and ending date (for example, 123186) must be entered.
If an expiration date is not specified, enter '*'. Inquiry will then use the default value of all
dates.
This is the last of the criteria needed to produce the Facility Directory Report.
3.2.3 Verifying Selection Criteria
Carefully review the selection criteria to ensure that they were entered correctly. If any
changes need to be made, to that criterion and enter the appropriate change.
When the selection criteria are verified for accuracy, execute the report by pressing < CR >.
21512/13/93 SDC-0055-034-ST-3003
-------
Permit C'lHnp'fr"''** System (PCS) Basic Training
3.2.4 Tally
The Tally feature is used to determine the number of records in the data base that satisfy the
selection criteria entered on the selection screen before actually producing the report on-line.
To specify that Inquiry produce a tally enter 'Y' followed by . Inquiry will search
the database and count the number of records that meet the selection criteria.
When 100 facilities have been compared against the selection criteria, Inquiry will display
the "Return to Selection Screen".
100 Facilities have been coqpared against the selection criteria
Reading this many records causes long pauses between pages
To increase the efficiency of your inquiries, please be more
specific with your selection criteria.
If a large selection is necessary, you say want to consider
tm or wore inquiries on subsets of the targe selection.
You have the option of continuing this inquiry or returning
selection screen.
Return to Selection Screen . The
system will return to the selection screen.
SDC-0055-034-ST-3003 12/13/93 219
-------
Basic Training Permit Compliance System (PCS)
To continue with the report, verify that "N" is entered at the Return to Selection Screen field
and press . Inquiry will continue to search the PCS database until another 100
facilities have been evaluated, at which point, the Return to Selection Screen will reappear
indicating that 200 facilities have been compared against the selection criteria. The screen
will continue to appear for every 100 facilities until all the facilities meeting the selection
criteria have been evaluated. Inquiry will then display the Tally Report.
03/16/80 *» PCS Inquiry Prompt Mode *** PCIPHEAR
FACIUTY DIRECTORY REPORT
THERE WERE A TOTAL OF 100 FACILITIES CHECKED
THERE WERE 36 FACILITIES THAT NET YOUR SELECTION CRITERIA.
End of Report Press to continue.
220 12/13/93 SL J-0055-034-ST-3003
-------
Compliance System (PCS)
Basic Training
3.2.5 Producing a Report
The Facility Directory Report may be produced after the Tally Report by pressing < CR>.
If a tally of the records is not desired prior to the report being produced, "N" must be
entered at the Tally criterion followed by .
Inquiry will proceed to display the Facility Directory Report. An example follows:
FACILITY DIRECTOR*
PERMIT
NUMBER
FACILITY
NAME
MAJOR/
MINOR
1>ERMIT
ISSUED
CT0000086 AMERICAN CYANANIDE COMPANY MAJOR 12/12/83
CITY: WALLINGFORD /T/ COUNTY: NEW HAVEN
CT002S291 AMERICAN ELECTRO PRODUCTS INC. MAJOR
CITY: UATERBURY " COUNTY: NEW HAVEN
MA0003361 AMERICAN OPTICAL CORP MAJOR 06/29/84
CITY: SOUTHBRIDQE COUNTY! WORCESTER
NH0021229 AMERICAN METAL FABRICATORS MAJOR 03/27/84
CITY: HUDSON /T/ COUNTY: HILLSBOROUGM
RI0000132 AMERICAN HOECHST CORP. MAJOR 03/30/82
CITY: COVENTRY COUNTY: KENT
PERMIT
EXPIRES
12/12/88
STATE:
STATE:
06/29/90
STATE:
03/27/89
STATE:
03/30/87
STATE:
CT
CT
MA
NH
RI
Cod
PRESS ENTER TO CONTINUE
The last line of this display indicates that more report output can be obtained. To continue
producing report output, enter . The next page of the report will be displayed.
Enter "Q" followed by to end the display of this report. Inquiry will return to the
report selection screen.
When all of the report data has been displayed, the following message will appear: End of
Report - Press < ENTER > to continue. Entering returns Inquiry to the Facility
Directory Selection Screen. Another report may be selected or Inquiry can be exited.
To end the session, enter "Q" followed by on the Facility Directory Selection
Screen. The system will exit to the Prompt Mode Main Selection Screen. Entering "Q" on
the "CMD:" line will return to the Inquiry Main Selection Screen where Inquiry is exited
St>C-M5$-034-ST-30ti3
12/13/93
-22T
-------
Basic Training Permit Compliance System (PCS)
from by entering "X" at the "QUIT" line. When the system returns to TSO, log off the
system.
3.3 Command Mode
The Command mode provides the user with the capability to choose groups of permits, at the
regional or the state level, and decide how these permits will be displayed on the screen.
To choose the Command mode from the Inquiry main menu, enter an 'X' beside 'Command
Mode for adhoc queries' as in the following example:
08/28/89 PCIPNAIN
Welcone to the Environmental Protection Agency's
Penrit Coaplfence System Inquiry Subsystem
Hark selection «ith en 'X' or '?' for Help
_ PROMPT Node for pre-fornstted reports
x COMMAND Mode for edhoc queries
_ MANAGER'S Inquiry
_ WIT - Exit inquiry
222 12113/93 &DU-UU55-U J*-o 1 -
-------
Permit ry«ipK«~* System (PCS) Basic Training
To access the Command mode while in the Prompt mode, type a *C* at the bottom of the
Prompt Mode Main Selection screen where it says 'Enter selection: _ ' as in the following
example:
08/28/89 » PCS Inquiry - Proopt Mode * PCIPPRNP
- Main Selection -
Report Description
ODD Code * Description Report
O1R Facility Directory
FAC Facility Overview Report
UN Outfall Linits Report
DMR OMR Overview Report
SCK Compliance Schedule £ Violations
INS Inspection Report
PER Permit Tracking Report
HEA Evidentiary Hearing Report
ENF Enforcement Action Report
(Q)uft - to end Inquiry session (Ooragand to enter Coomand Mode
Enter selection; c
Press and the Command Mode Selection Screen will be displayed:
08/28/89 ** PCS Inquiry - Comaand Mode **** PCIPOD
- Selection Screen -
Selection:
Selection:
Selection:
Selection:
Selection:
Selection Default(s): RECH EQ 04, IACC £0 A
More To Select (y/n): N
Display:
Display:
Sort;
Tally to Produce Output
SDC-0055-034-ST-3003 ^2/13793 223
-------
Basic Training Permit Compliance System (PCS)
The Command Mode Selection Screen is used to select the facilities desired, sort the facilities
and choose how the facilities are to be displayed on the terminal screen.
3.3.1 Selection Statements
The first thing the Inquiry system needs to know is which facilities to select. SELECTION
STATEMENTS are used to accomplish this. There are 5 'Selection:' lines used to enter
selection statements.
In order to use the Command mode, it is necessary to be familiar with the four character
PCS acronyms since these acronyms are used for selection statements, sort selections and
display statements. The format for all selection statements is:
ACRONYM -> LOGICAL VALUE -> OPERATOR
The ACRONYM can be any valid PCS acronym, the LOGICAL OPERATOR is any valid
logical operator and the VALUE is a value related to the acronym in the selection statement.
An example of a selection statement is:
STTE EQ SC
This example tells Inquiry to select the state equal to South Carolina, where STTE is the
acronym for state, EQ is the logical operator EQUAL TO and SC is the value for the state of
South Carolina.
If you formatted a selection statement like this:
STTE EQ 03
Inquiry would not find any matches. The value 03 is not a valid value for the acronym
STTE. STTE is the acronym for the two digit state code and 03 is not a valid state code.
More than one selection statement can be used at one time, if necessary. For example, if
you want to select all the major municipals in the state of South Carolina you need three
selection statements:
STTEEQ SC
MADIEQM
FTYPEQM
224 12/13/93 aDU-UU55-UJ4-& 1 -JIXU
-------
Permit rumplta"** System (PCS) Basic Training
It is not necessary to specify all three statements. You could ask for all facilities in South
Carolina but you would have to look at each one to see if it is a major municipal. It is much
more efficient to use all three selection statements so that the system only selects and
displays the facilities of interest.
All three statements can be expressed on the same selection line by using a space between
each statement, as in the following example:
Selection: stte eq sc madi eq m ftyp eq m _
Selection: _ . _
Selection: _ __^_
Selection: __ __
Selection: _ __
There are 5 lines to enter selection statements. As many selection statements as needed can
be entered.
Try these:
Problem #1
What would the selection statements be to select all facilities in South Carolina that have an
approved pretreatment program and are on final limits?
Selection:
Selection:
Selection:
Selection:
Selection:
Problem #2
What would the selection statements be to select all facilities in South Carolina in Aiken
county (county code 003) that have an SIC code of 4911 and have a PL 92-500 grant?
Selection:
Selection:
Selection:
Selection:
Selection:
SDC-0055-034-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
3.3.2 Logical Operators
The only logical operator discussed so for has been EQ (Equal To). There are others. The
logical operators that can be used in Inquiry are:
EQ - Equal To
NE - Not Equal To
AL - Alternate
BT - Between
GT - Greater Than
GE - Greater Than or Equal To
LT - Less Than
LE - Less Than or Equal To
Not Equal To (NE)
Not Equal To (NE) can be used to select facilities for a particular acronym where that
acronym has numerous values. NE is used to tell Inquiry to select the facilities that are not
equal to the values specified in your selection statements.
For example, the acronym FTYP has 4 values - M (municipals), I (industrials), F (federals)
and O (others). To select all facilities that are not municipals, use NE in the following
manner:
FTYPNEM
This example tells the Inquiry system to select all facilities where the facility type is not
equal to M (municipals).
Try this:
Problem
What would the selection statements be to see all minor municipals in Aiken county, South
Carolina (county code 003)?
Selection:
Selection:
Selection:
Selection:
Selection:
225 12/13/93 SDC-0055-034-ST-3003
-------
Ptennit Compliance System (PCS) Basic Training
Alternate (AL)
In the situation where an acronym is needed to specify more than one value, EQ cannot be
used because this would tell Inquiry to find one facility that has more than one value for the
same acronym for the same key data elements. That is not possible.
For example, if you have two or more NPDES permit numbers to be viewed, and EQ is used
to specify each of the permit numbers, Inquiry will indicate that no facilities meet the
selection criteria.
The problem is that the system is trying to find one facility that is equal to all of the permit
numbers. That is not possible since only one permit number can be assigned to each facility.
In this case the logical operator alternate (AL) is used in the following manner:
NPID AL SC0000019
NPID AL SC0000043
NPID AL SC0000051
This tells Inquiry to select SC0000019, and/or SC0000043, and/or SC0000051. In
INQUIRY, AL can be used only 3_ times for the same acronym in the same Inquiry session.
AL applies to any acronym in PCS that has more than one value.
Try this:
Problem
What would the selection statements be to find all the facilities in South Carolina that have
had Compliance Biomonitoring inspections, Compliance Evaluation inspections or
Compliance Sampling inspections performed for all municipals and industrials?
Selection:
Selection:
Selection:
Selection:
Selection:
SDC-0055-034-ST-3003 12/13/93 u.1
-------
Basic Training Permit Compliance System (PCS)
Between (BT)
Between (BT) is used to specify date ranges. For example, to view all the inspections that
had been performed for South Carolina for 2nd quarter FY92, the following selection
statements are used:
STTEEQSC
DTIN BT 010192 033192
Try this:
Problem
What would the selection statements be to find all DMR data for 3rd quarter FY92 for South
Carolina major municipals?
Selection:
Selection:
Selection:
Selection:
Selection:
Greater Than (GT)
Greater Than (GT) is used to select a particular acronym and see all of the values that are
greater than the value specified in the selection statement. In the structure of PCS, A is the
lowest alphabetic value and Z is the highest value. 0 is the lowest numeric value and 9 is the
highest value. A blank field is always lower than the alphabetic or numeric values. For
example, the acronym PRET (Pretreatment Program Indicator) has four possible values. Y
(pretreatment program is required and approved), R (pretreatment program is required but
not approved yet), C (covered by another POTW's pretreatment program) and blank means
that the facility does not have a pretreatment program.
To see all of the facilities in South Carolina that have a pretreatment program, structure the
selection statement in the following manner:
PRCTGT
To indicate a blank in Inquiry type a single quotation mark, followed by a space, followed
by another single quotation mark.
When using the logical operator GT, it does not include the value specified in the selection
228 12/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
statement. It can also be used for dates for everything greater than a certain date. For a
date range, use the logical operator BT.
Try this:
Problem
What would the selection statements be to display all of the facilities in South Carolina with
a permit issuance date after March 31, 1992?
Selection:
Selection:
Selection:
Selection:
Selection:
Greater Than or Equal To (GE)
Greater Than or Equal To (GE) is used in the same manner as GT. The only difference is,
GE includes the value specified in the selection statement.
Try this:
Problem
What would the selection statements be to display all of the South Carolina facilities that
have been inspected since January 1, 1992?
Selection:
Selection:
Selection:
Selection:
Selection:
SDC-OOS5-034-ST-3M3 12/13/93 "225
-------
Basic Training Permit Compliance System (PCS)
Less Than (LT)
Less Than (LT) is used to select all the values for a particular acronym that are less than the
value specified in the selection statement. For example, to see all the facilities that do not
have a pretreatment program, the selection statement would be:
PRETLTC
Like GT, LT does not include the value that is specified in the selection statement.
Try this:
Problem
What would the selection statements be to display all the South Carolina permits that have
expired?
Selection: ____ <--this
Selection: _____ date
Selection: would
Selection: _ be the
Selection: current
date!
Less Than or Equal To (LE)
Less Than or Equal To (LE) is used in the same manner as LT. The only difference is, LE
includes the value specified in the selection statement.
Try this:
Problem
What would the selection statements be to display all the active and inactive permits in South
Carolina?
Selection:
Selection:
Selection:
Selection:
Selection:
230 12713793
-------
System (PCS) Basic Training
3.3.3 Selection Defaults
Following the selection statements, there is a line that says:
Selection Defaults): REGN EQ 04, IACC EQ A
These are the defaults in effect for INQUIRY. If you are a state user, the default is set up to
be your state only. It is therefore not necessary to select your state in your selection
statements.
If you are a regional user, the default is set up to be your region. In this case, you would
have to select a state in the selection statements, unless you wanted the entire region. The
system always defaults to only active permits. To look at inactive permits, you have to
specify inactive permits in the selection statements.
The next line after the defaults is:
More To Select (y/n): N
If 'YES' (Y) is the response to this statement, the system will display more selection lines.
This feature is used only if the first 5 selection lines are not enough and additional selection
lines are required to complete the selections.
3.3.4 Display Statements
After the facilities, in which you are interested, are selected you are ready to tell Inquiry
what to display on the terminal. To accomplish this, use the 'Display:' line to start listing the
acronyms to see the output, as in the following example:
Display: npid fhms madi ftyp
Display:
This Display statement tells Inquiry to display the NPDES permit number, facility name,
major discharge indicator and the facility type for the facilities that you are selecting. The
acronyms specified on the display line become the headers when the data is displayed on the
terminal, as in the following example:
NPID PNMS MADI FTYP
SC0000043 GRANITEVILLE CO/GREGG WATER PT I
SC0000051 GRANITEVILLE CO/HATER PLANT I
SC0000141 CORNELL-DUBILIER MARKETING INC M I
SC0000175 US DEPARTMENT OF ENERGY M F
SDC-0055-034-ST-3003 12/13/93 231
-------
Bask Training Permit Compliance System (PCS)
There are 2 display lines available to enter acronyms. As many acronyms as needed can be
used, however, the screen is limited to displaying only 80 characters of data, so be aware of
the length of the data elements being displayed. In the above example, NPID is 9 characters,
FNMS is 30 characters, MADI is 4 characters and FTYP is 4 characters. Inquiry is
automatically going to insert one space between data elements, so include that space in the 80
character limit. This example displays a total of SO characters including one space between
data elements.
If you are unsure of the length of a data element, Appendix B in the PCS Generalized
Retrieval Manual has the field size for the acronyms for PCS. Look under the column
heading 'QL Short Head Size* to find the length appropriate for INQUIRY.
One of the limitations of Inquiry is that you cannot display data from more than one data
family in an Inquiry session. For example, if you tried to display compliance schedules and
limits data like this:
Display: npid fhms csch evnt dtsc dtac pdsg pram
Display:
The error message 'DISPLAY/SORT OF UNRELATED DATA GROUPS' would appear at
the top of the screen.
3.3.5 Sort Statements
After the selection statements and display statements have been entered, Inquiry can be told
how you want the output sorted. To do this, use the line that says 'Sort:' to list the
acronyms in the order that you want the display sorted, as in the following example:
Sort: madi npid
This is telling Inquiry to display the output sorted first by the Major Discharge Indicator
(MADI), then by NPDES Permit Number (NPID). MADI has two values, blank to indicate
the permit is a minor permit and M to indicate the permit is a major permit. First, Inquiry
will sort the permits by the MADI, then it will sort by NPID, within each value of MADI.
The output will display all minors sorted by NPID, then it will display all majors sorted by
NPID. You can sort by as many acronyms as the Sort line will contain. Sort statements are
not required in order to use INQUIRY, however, if you do not sort the output, the display
will be in a random order.
232 12/13/93 SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
3.3.6 Tally
After the Sort statements, there is a line that asks if you want to tally your display:
Tally (y/n): N
The default for this statement is No (N). If you change the response to Yes (Y), then you
will get a tally of the number of records that will be displayed on the terminal.
The following is an example to show how all the statements are put together.
Example:
You are responsible for sub-region LS in South Carolina. You want to see all the municipals
and industrials in your sub-region that do not have PL 92-500 grants and have issued
permits. The information you want displayed on the terminal is the permit number, facility
name, major discharge indicator, facility type, permit issuance date and the permit expiration
date. You want the data sorted by facility type and facility name.
08/28/87 *** PCS Inquiry - Coraand Node *** PCIPCMD
- Selection Screen -
Selection: stte eq sc ftyp al m ftyp at i fdar ne * subr eq Is.
Selection: perd gt 010170
Selection:
Selection: -
Selection: __^_
Selection Default(s): REGN EQ 04, IACC EQ A
More To Select (y/n): N
Display: npid fn» nadi ftyp perd pere_
Display: _^^^____^__________
Sorti ftyp fnms_
Tally to Produce Output
1^713793 333
-------
Basic Training Permit Compliance System (PCS)
After you have typed all of your statements, you have to press the < CR>. Inquiry will
check the selection, display and sort statements for any errors. If there are no errors, this
screen will remain the same. If you type everything in small letters, as in the example
above, the letters will change to capitals as in the example below:
08/28/89 **» PCS fnqufry - Conmnd Node *** PCIKMD
< Selection Screen -
Selection: SITE EB SC ttYP AL N fTTP M. I FDGR ME * SUM EQ IS
Selection: PERD 6T 010170 ~
Selection: . ..
Selection: ___________________.^_____________________
Selection:
Selection Oefeult(s>: IACC EQ A
More To Select 10 FNNS «M>r FTYP PERD PESE
Oisptey:
Sort: ftyp fms_
Telly to Produce Output
234 12/13/93 SDC-O055-034-ST-3003
-------
System (PCS) Basic Training
When Inquiry has finished checking the statements for errors, press a second time to
produce the report. When is pressed the second time, the screen will change to
inform you that it is processing your request, as in the following example:
08/28/89 " PCS Inquiry - Command Node ** PCI POO
PROCESSING YOUR INQUIRY REQUEST
While this screen is displayed, there is nothing to do until it has finished processing the
report. If there was a mistake made, there is nothing to be done about it until the report is
displayed on the screen, so be careful and look at your Inquiry statements carefully before
pressing .
The advantage of using Inquiry is that it can process a report in a matter of a few minutes.
For this reason, Inquiry is intended to be used to view a small amount of data in a short
amount of time. If you find that Inquiry is taking more than 5 to 10 minutes to process a
report, use a Generalized Retrieval for extract the data.
SbC-M$$-034-ST-3003 12/13/93 235
-------
Basic Training
Permit Compliance System (PCS)
When it has finished processing, your report will be displayed:
NPID
FUNS
NADI FTYP PERD
PERE
SC0034291
SC0037435 ADN1RAL/DIV OF NAGIC CHEF INC
SC0040045 AMOCO FOAM PRODUCTS CO
SC0027529 AUGUSTA SAND ft GRAVEL COMPANY
SC0041769 AUGUSTA SAND ft GRAVEL/BEECH IS
SC0032671 Brooklnd Plantatn Hone for Boy
SC00297S1 CANNON DOVA APTS/R C R INC
SC0034908 CAROLINA CAR WASH
SC0038351 CAROLINA METALS INC
SC0003891 CYPRUS INDUSTRIAL MINERALS CO
SC0038903 DIXIE CLAY COMPANY
SC0040592 DUCANE COMPANY
SC0040185 EDISTO HIGH SCHOOL
SC0041424 EMRO MARKETING/PORT OIL *284
SC0039888 EMRO NKTG/STARVIN MARVIN *127
SC0001147 GA PACIFIC/HOLLY HILL LUMBER
SC0000094 GRANITEVILLE CO/STEVENS STEAM
SC0000051 GRANITEVILLE CO/WATER PLANT
SC0000078 GRANITEVILLE CO/UOODHEAD OIV
SC0032638 GREEN ACRES MHP/J D R CORP
SC0003531 GREENWOOD MILLS/EDISTO PLANT N
SC0001163 GREENWOOD MILLS/LINER PLT #17 M
SC0033723 HUNTER-KINARD-TVLER HS
SC0022675 J N HUBER COPR/LANGLEY PLT
SC0040096 J M HUBER CORP/CONGER NINE
SC0024341 J M HUBER/EDISTO PLT
SC0000582 KIMBERLY-CLARK CORP N
SC0038105 KIRKLAND MINING CO INC
SC0042307 MARTIN NARIETTA/AIKEN QUARRY
SC0003093 NILLIKEN ft CO/BARNWELL MILL N
SC0004073 MULT I TEX CORPORATION
SC0030937 NORTHWOOD ESTATES/MIDLANDS UT
SC0030066 ORANGEBURG SAUSAGE COMPANY
SC0038008 ORANGEBURG/PEARSON WATER PLANT
SC0024422 RED CARPET INN/ORANGEBURG
SC0038679 ROPER OUTDOOR PRODUCTS
SC0000574 SC ELEC ft GAS/URQUHART STM STA M
SC0029271 SC HWY DEPT REST AREA 126 WEST
SC0029289 SC HWY DEPT/REST AREA 1-26 EA
SC0040444 SEABOARD RR/JACKSON GROUNC WTR
SC0032387 T E WANNAMAKER SO
SC0028240 T R FREEMAN CAR WASH
SC0034894 TODDS CAR WASH
SC0025941 UTICA TOOL COMPANY INC
SC0000221 WHITLOCK COMBING COMPANY N
SC0042595 BAMBERG BOARD OF PUBLIC WORKS
SC0025143 BARNWELL CITY OF N
SC0040037 BOWMAN, TOWN OF
SC0021113 BRANCHVILLE TOWN OF
SC0040215 DENMARK CITY OF
SC0030368 N AUGUSTA/BELVEDERE TERRACE SO
SC003936S SANTEE PUBLIC SERVICE DISTRICT
SC0023272 SPRINGFIELD/PLANT #1
SC0023281 SPRINGFIELD/PLANT 02
SC0042099 TOWN OF EHRHARDT
SC0026204 WAGENER TOWN OF
02/23/88 03/31/93
01/09/87 01/31/92
06/23/87 07/31/92
08/29/86 09/30/91
11/06/87 11/30/92
03/02/87 03/31/92
01/13/88 01/31/93
07/06/83 07/31/88
01/19/88 02/28/92
06/15/81 08/01/86
10/26/83 11/30/88
07/31/86 08/31/91
04/14/86 04/30/91
05/01/87 05/31/92
06/21/85 07/31/90
01/08/88 01/31/93
05/15/86 05/31/91
04/01/87 03/31/92
05/15/86 05/31/91
05/31/88 06/30/93
10/13/86 10/31/91
10/13/86 10/31/91
06/15/88 06/30/93
08/29/86 09/30/91
07/31/86 08/31/91
09/18/86 10/31/91
01/12/84 01/31/89
11/06/87 11/30/92
09/09/88 09/30/93
06/21/85 07/31/90
05/15/86 05/31/91
06/12/87 06/30/92
04/12/82 05/01/87
09/06/83 09/30/88
03/12/87 03/31/92
06/24/83 07/31/88
02/27/84 03/31/89
04/14/87 04/30/92
04/14/87 04/30/92
01/24/86 02/28/91
10/31/77 11/30/82
01/19/88 02/28/93
04/04/86 04/30/89
03/30/8') 04/30/94
11/24/86 12/31/91
N 09/12/88 09/30/93
N 05/09/89 05/31/94
M 05/14/86 05/31/91
N 12/19/84 01/31/90
N 09/30/85 10/31/90
N 02/13/85 02/28/90
N 09/03/85 09/30/90
H 06/13/88 06/30/93
N 06/13/88 06/30/93
N 06/06/88 06/30/93
H 12/02/86 12/31/91
12/13/93
-------
Permit Compliance System (PCS) Basic Training
Try the following problems. Feel free to review any of the notes in this handout to help
solve the problems.
Problem #1
Find out which South Carolina permits are going to expire in 1st quarter FY93. Display the
permit number, facility name, major discharge indicator, permit issuance date and permit
expiration date and sort it by major discharge indicator and permit expiration date.
08/28/89 *** PCS Inquiry - Conaand Node **** PC1PWD
Selection Screen -
Selection:
Selection:
Selection:
Selection:
Selection:
Selection Defeult(s): REGN EQ 04, UCC EQ A
More To Select (y/n): N
Display:
Display:
Sort:
Tally (y/n): N
Press «ENTER> to Produce Output
SDC-0035-034-ST-3003 12/13/93 237
-------
Basic Training Permit Compliance System (PCS)
Problem #1
For SC0003093, SC0000221 and SC0023272, your boss wants to know which parameters
have had numeric violations since January 1, 1992. Display the permit number, monitoring
period end date, measurement discharge number, measurement parameter code, and .
measurement monitoring location. Sort the display by permit number and monitoring period
end date.
48/28/89 **** PCS Inquiry ~ Caramel Node *** PC1KMD
Selection Screen -
Selection:
Selection:
Selection:
Selection:
Selection:
Select fen OefeultCft): RECN EQ 04, IACC EO A
More To Select to Produce Output
238 12/13/93 SDC-0055-034-5T-3U03
-------
Prnnif rftmplianM> System (PCS) Bane Training
4.0 Generalized Retrievals
Generalized retrievals are batch jobs that process on the IBM at the National Computer
Center (NCC) in Raleigh, NC. The job will process and you will receive a print-out of the
data requested.
4.1 The 00 Card
To submit a generalized retrieval, you must have certain elements in your retrieval request.
The first thing you must have is a 00 card. The 00 card tells the system; how much time to
allow for your job to process, a job identifier, remote number, number of copies, job
priority, a syntax check, forms number and number of lines. The format for the 00 card is:
00 SYNTAX=NO JOBID=REON3 TIME=1M PRTY=2 RMT=255 COPIES =1 BIN=005 MSGCLASS=A
NOTE: There is an additional 00 card used for public access users requesting
retrievals. This 00 card is called the account card. It looks like this:
00 ACCTNAME=AAAAPCSYP
SYNTAX tells the system to check on the retrieval statements. A syntax check will look at
your retrieval statements for obvious errors, such as a display line that is too long, or a
misspelled acronym, etc. For a syntax check, specify SYNTAX=YES on the 00 card. A
syntax check will NOT produce a report. For a report, specify SYNTAX=NO on the 00
card.
JOBED gives the retrieval a name that prints on the cover page of the retrieval printout. Any
name can be used. The name can be one to five characters in length.
TIME tells the system how much time to allow the system to process the job. This is
optional, but if not specified, the system will default to allow only seven seconds and that
may not be enough time. Knowing how much time to specify comes from experience. A
good rule of thumb is, the lower in the PCS data structure that the data comes from, the
more time needed to process the retrieval. For example, if you are asking to see only
Facility data for the permits in your state, you will not need more than a minute of time. If
you are asking to view all the DMR data for all of your facilities for the past quarter, you
may need more than ten minutes of time.
SDC-0055-034-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
PRTY is the priority to be assigned for the retrieval. There are only two priorities used.
PRTY= 1 is the lowest priority. Any retrievals with PRTY=1 will not process until after 5
p.m. Eastern time. Any retrievals with a time of five minutes or more also will not process
until after 5 p.m. If you have five minutes or more of time on your retrieval, you should
specify PRTY= 1 so that your timesharing cost will be the least. PRTY =2 is the other
priority code which costs more than PRTY=1, but it allows retrievals to process in the same
day, if you have less than five minutes of time specified.
RMT is the remote (or printer) number where the retrieval is to be printed. Remote number
2S5 is a special number that does not print the retrieval but holds it in an output spooler so
you can view it on the screen. To specify a remote number, type RMT= and the number of
your remote.
COPIES allows you to specify the number of copies to be printed when the retrieval finishes
processing. If only one copy is required, do not specify this option. The number of copies
can be between 1 and 99.
BIN number tells the computer operator the bin number for the printout when it is printed.
In most cases, the bin number is M followed by the user ID. In the example above, D005 is
the bin number used at EPA headquarters.
MSGCLASS specifies the output class to which system messages and JCL statements for the
job are to be written. MSGCLASS=A would include the entire JCL for the retrieval,
whereas MSGCLASS=Z would include no JCL.
4.2 The 01 Card
The second line of the retrieval request must contain a title for the retrieval. The format for
the title card is as follows:
01 03 A TITLE FOR YOUR RETRIEVAL
You can specify up to five title lines for the retrieval. The format for the additional lines is
as follows:
01 03 A TITLE FOR YOUR RETRIEVAL
02 THE NEXT LINE DOES NOT CONTAIN A REGION CODE
03 NEITHER DOES THE THIRD LINE-
04 NOT THIS LINE EITHER
05 NOPE. NOT ON THIS LINE EITHER
The first title card is required. It contains the region number and then the first line of the
title. Title cards 02 through 05 are optional.
233 12/13/93
-------
Permit Compliance System (PCS) Bask Training
4.3 The 10 Card
4.3.1 Logical Operators
After the title cards have been entered, the selection statements can be entered. Selection
statements are entered on a 10 card in the format:
10 ACRONYM LOGICAL VALUE
OPERATOR
The ACRONYM is any valid PCS acronym. The OPERATOR is any logical operator and
the VALUE is a value that is related to the acronym specified in the statement. The valid
logical operators are:
EQ - EQUAL TO
ME - NOT EQUAL TO
AL - ALTERNATE
GT - GREATER THAN
GE - GREATER THAN OR EQUAL TO
LT - LESS THAN
LE - LESS THAN OR EQUAL TO
To select all the facilities in Pennsylvania, the selection statement would look like this:
10 STTE EQ PA
As many 10 card selection statements as are required can be entered. A retrieval is allowed
to contain up to 99 lines, not including the JCL. Therefore, as many 10 card selection
statements as will fit within the 99 lines can be entered.
When entering multiple selection statements, each statement is entered on separate 10 cards.
For instance, if you want to look at all majors that are expiring in 3rd quarter FY 1995 in
the state of Pennsylvania, the 10 card statements would look like this:
10 STTE EQ PA
10 MADI EQ M
10 PERE GE 040195
10 PERE LE 063095
If you want to select two or more values for the same acronym, use the logical operator AL
instead of EQ. When using EQ, you are telling the system that you want to select an
acronym that is Equal To a certain value. If you tell the system to select an acronym Equal
To one value and then tell the system to select the same acronym Equal To a different value,
it will attempt to find that acronym Equal To two different values in the same permit and that
is not possible. Consider this retrieval:
12713793 " Z*T
-------
Base Training Permit Copiplianre System (PCS)
00 SYNTAX=NO JOBID=EQUAL TIME=20S PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF HOW NOT TO USE EQ
10 NPID EQ PA0021237
10 NPID EQ PA0021181
20 QL
40 NPID FNMS MADI TYPO SIC2 INCL FTYP
This retrieval is asking the system to find the NPDES permit numbers, PA0021237 and
PA0021181 for the same facility. You will receive the following message:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=EQUAL TIME=20S PRTY=2 BIN=DOO5 RMT=255
10 HQ EXAMPLE OF HOW NOT TO USE EQ
10 NPID EQ PA0021237
10 NPID EQ PA0021181
20 QL
40 NPID FNMS MADI TYPO SIC2 INCL FTYP
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
THERE WERE NO NPDES QUALIFYING FOR THE SELECTION CRITERIA
The system is saying that there are no permits that qualify for these retrieval statements
because there is not a permit that has two different permit numbers. AL (Alternate) is used
to choose these permits as in the following example:
00 SYNTAX=NO JOBID=ALTER TIME=20S PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF HOW TO USE AL
10 NPID AL PA0021237
10 NPID ALPA0021181
20 QL
40 NPID FNMS MADI TYPO SIC2 INCL FTYP
Now you will receive the desired output:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID-ALTER TIME=20S PRTY=3 BIN=D005 RMT=255
01 HQ EXAMPLE OF HOW TO USE AL
10 NPID AL PA0021237
10 NPID AL PA0021181
20 QL
40 NPID FNMS MADI TYPO SIC2 INCL FTYP
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
232 12713793 SDC-OOSS-O^T-JOiW
-------
Permit Compliance System (PCS)
Radr Training
06/16/89
EXAMPLE OF HOW TO USE AL
NPID
FNMS
MADZ TYPO SIC2 INCL FTYP
PA0021181 DOYLESTOWN BOROUGH '(GREEN ST S PUB 4952 M M
PA0021237 NEWPORT BOROUGH MUNICIPAL AUTH PUB 4952 M M
The Major Discharge Indicator (MADI) contains only two values, an M if it is a major or
blank if it is a minor. To choose major facilities, you must use the selection statement
MADI EQ M. To choose minor facilities, use the selection statement MADI NE M, which
means select all facilities where the value for the Major Discharge Indicator is not equal to
M as in the following example:
00 SYNTAX=NO JOBID=NOTEQ TTME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF HOW TO USE NE
10 SITE EQ PA
10 MADI NE M
20 QL
40 NPID FNMS MADI TYPO SIC2 INCL FTYP
Your output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=NOTEQ TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE HOW TO USE NE
10 STTE EQ PA
10 MADI NE M
20 QL
40 NPID FNMS MADI TYPO SIC2 FTYP
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
06/19/89
EXAMPLE OF HOW TO USE NE
QL
NPID FNMS
QL
MADI TYPO SIC2 FTYP
PA0000078 WELCH FOODS INC-NORTH EAST PA
PA0000094 PENELEC FRONT STREET
PA0000116 TRUE TEMPER CORP LAKE CITY
PA0000124 HAMMERMILL PAPER-ERIE
PA0000132 BESSEMER 6 LK ERIE RR- ALB I ON S
PA0000167 NATIONAL FORGE CO ERIE DIV
PA0000205 WESTERN PENNA. WATER CO.-MONONG
PA0000213 W. PA WATER COMPANY - KANE DIS
PA0000221 WESTERN PENNA. WATER CO.-UNIONT
PA0000248 WESTERN PENNA. WATER CO.-MCDONA
PA0000256 PUNXSUTAWNEY WATER SERICE CO
PA0000264 WESTERN PA WATER CO-NEW CASTLE
PA0000272 WESTERN PENNA. WATER CO.-PITTSB
PRI
PRI
PRI
PRI
PRI
PRI
PRI
PRI
PRI
PRI
PRI
PRI
PRI
2033
4911
3312
2621
3743
3321
4941
4941
4941
4941 ]
4941 ]
4941 ]
4941 ]
:
c
c
c
SDC-W55-034-ST-3003
12/13/93
-------
Basic Training
Permit Compliance System (PCS)
PA0000302 WEST PA WATER COMPANY/ INDIANA
PA0000329 ELLWOOD CONSOLID WTR-WURTEMBUR
PRI 4941 I
PRI 4941 I
Notice that for all of the facilities listed, the value for the .iADI column is blank which
means that these facilities are minors.
To select major facilities that have been issued permits since 093088, use GT, as in the
following example:
00 SYNTAX=NO JOBID=GRTHN TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF HOW TO USE GT
10 SITE EQ PA
10 MADI EQ M
10 PERD GT 093088
20 QL
40 NPID FNMS FTYP PERD PERE
Your output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID-GRTHN TIME=2M PRTY=2 BIN=DOO5 RMT=255
01 HQ EXAMPLE OF HOW TO USE GT
10 STTE EQ PA
10 MADI EQ M
10 PERD GT 093088
20 QL
40 NPID FNMS FTYP PERD PERE
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
06/15/95
EXAMPLE OF HOW TO USE GT
NPID FNMS FTYP PERD PERE
PA0001791 GTE SYLVAN I A INC WARREN
PA0007625 HEDSTROM CO - BEDFORD
PA0008761 ARMSTRONG WORLD INDUSTRIES
PA0009300 HOWES LEATHER COMPANY
PA0010031 PENNSYLVANIA ELECTRIC CO
PA0012475 MET ED PORTLAND
PA0012742 ATLAS POWEDER CO. - REYNOLDS P
PA0012769 ROHM 6 HAAS-DELAWARE VLY INC.
PA0013862 WYETH-AYERST LABORATORIES, INC
PA0020257 GROVE CITY BOROUGH
PA0021814 MANSFIELD BOROUGH STP
PA0026221 DALLAS AREA MUNICIPAL AUTH.
PA0026646 ANTIETEM VALLEY MUNICIPAL AUTH
PA0026701 MORRISVILLE BOROUGH MUN AUTH-S
PA0026905 CONNELLSVILLE MUN.AUTH-STP
PA0029491 CLARION AREA AUTHORITY
I
I
I
I
I
I
I
I
I
M
M
M
M
M
M
M
10/01/88 10/24/93
04/11/89 04/11/94
05/04/89 05/04/94
04/28/89 10/28/91
11/23/88 11/22/93
11/30/88 11/30/93
12/01/88 11/30/93
01/31/89 01/31/94
11/04/88 11/04/93
05/02/89 05/01/94
04/26/89 04/25/94
01/13/89 01/12/94
03/13/89 03/13/94
05/15 '99 05/19/94
10/31 38 10/31/93
01/20/89 01/19/94
ETS^ AAge jM^-i'T-'mm
-------
Permit
System (PCS)
BaSM* Training
When using GT, the value specified is not included, only the values that are GREATER
THAN the one specified are included. Another way to retrieve similar data, as in the above
example, is by using the logical operator GE which means GREATER THAN OR EQUAL
TO. This will include the value specified in the retrieval statement as in the following
example:
00 SYNTAX=NO JOBID=GREQL TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF HOW TO USE GE
10 STTE EQ PA
10 MADI EQ M
10 PERD GE 100188
20 QL
40 NPID FNMS FTYP PERD PERE
The output will look like this:
RETRIEVAL
STATEMENTS
60 SYNTAXoNO JOBID=GREQL TIME=2M PRTY=2 BIN=DOO5 RMT=255
01 HQ EXAMPLE OF HOW TO USE GE
10 STTE EQ PA
10 MADI EQ M
10 PERD GE 100188
20 QL
40 NPID FNMS FTYP PERD PERE
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
06/15/95
EXAMPLE OF HOW TO USE GE
QL ****************************************************** QL
NPID FNMS FTYP PERD PERE
PA0001791
PA0007625
PA0008761
PA0009300
PA0010031
PA0012475
PA0012742
PA0012769
PA0013862
PA0020257
PA0021814
PA0026221
PA0026646
PA0026701
PA0026905
PA0029491
GTE SYLVANIA INC WARREN
HEDSTROM CO - BEDFORD
ARMSTRONG WORLD INDUSTRIES
HOWES LEATHER COMPANY
PENNSYLVANIA ELECTRIC CO
MET ED PORTLAND
ATLAS POWEDER CO. - REYNOLDS P
ROHM & HAAS-DELAWARE VLY INC.
WYETH-AYERST LABORATORIES, INC ]
GROVE CITY BOROUGH 1
MANSFIELD BOROUGH STP 1
DALLAS AREA MUNICIPAL AUTH. 1
ANTIETEM VALLEY MUNICIPAL AUTH 1
MORRISVILLE BOROUGH MUN AUTH-S 1
CONNELLSVILLE MUN. AUTH- STP 1
CLARION AREA AUTHORITY 1
10/25/88
04/11/89
05/04/89
04/28/89
11/23/88
11/30/88
12/01/88
01/31/89
[ 11/04/88
( 05/02/89
4 04/26/89
4 01/13/89
4 03/13/89
4 05/19/89
4 10/31/88
4 01/20/89
10/24/93
04/11/94
05/04/94
10/28/91
11/22/93
11/30/93
11/30/93
01/31/94
11/04/93
05/01/94
04/25/94
01/12/94
03/13/94
05/19/94
10/31/93
01/19/94
SDC-OOSS-O^T-TO
12/13/93
-------
Training
Permit Cojnpliance System (PCS)
To look at Pennsylvania facilities that have not been issued a permit, use the logical operator
LT, as in the following example:
00 SYNTAX=NO JOBID=LSTHN TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF HOW TO USE LT
10 STTE EQ PA
10 PERD LT 010170
20 QL
40 NPID FNMS FTYP PERD PERE
The output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=LSTHN TIME=2M PRTY=2 BIN=D005 RMT=Zb5
01 HQ EXAMPLE OF HOW TO USE LT
10 STTE EQ PA
10 PERD LT 010170
20 QL
40 NPID FNMS FTYP PERD PERE
** DEFAULTS
10 IAOC EQ A
10 PTYP AB
IN EFFECT **
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
06/15/95
QL
NPID
EXAMPLE OF HOW TO USE LT
»****«
FNMS
FTYP PERD
PERE
PA0000728 KOPPERS CO INC VERONA I
PA0000787 PITTSBURGH GEAR CO NEVILLE ISL I
PA0000817 TEXTRON INC TALON DIV PLANT 7 I
PA0001449 ROTOBLAST ABRASIVES PLANT
PA0001503 DREXEL DYNAMICS CORF KITTAN PT
PA0001546 BRIDGEVILLE GLASS PLANT GE CO
PA0001694 ELLIOTT CO DIV CARRIER CORP
PA0001805 GLENSHAW GLASS CO INC
PA0001911 KAISER ALUM & CHEM OHIOPYLE
PA0001937 MCGRAW-EDISON POWER SYS DIV
PA0002160 PITTSBURGH TUBE CO-MONACA
PA0002186 HK PORTER COMPANY INC
PA0002356 QUAKER STATE OIL-WEB LSE BAT 2
PA0002364 QUAKER STATE OIL REFINING C.ORP
PA0002496 STACKPOLE CARBON CO-ST MARYS
PA0002500 STACKPOLE CARBON CO
PA0002534 STACKPOLE CARBON-BENZINGER PLT
PA0002569 WOLF HEAD OIL REF CO
PA0002585 TELEDYNE VASCO COLONIAL PLANT
235"
12/13/93
-------
Permit Compliance System (PCS) Bask Training
As with GT, LT does not include the value that was specified in the retrieval statement. Use
LE which means LESS THAN OR EQUAL TO to include the value in the retrieval
statement. For instance, if you want to see all the permits that were issued in 1st quarter
FY89 for major Pennsylvania facilities, submit the following retrieval statements:
00 SYNTAX=NO JOBID=LSEQL TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF HOW TO USE LE
10 STTE EQ PA
10 MADI EQ M
10 PERD GE 100188
10 PERD LE 123188
20 QL
40 NPID FNMS FTYP PERD PERE
The output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=LSEQL TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF HOW TO USE LE
10 STTE EQ PA
10 MADI EQ M
10 PERD GE 100188
10 PERD LE 123188
20 QL
40 NPID FNMS FTYP PERD PERE
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
06/15/95
EXAMPLE OF HOW TO USE LE
NPID FNMS FTYP PERD PERE
PA0001791 GTE SYLVANIA INC WARREN
PA0010031 PENNSYLVANIA ELECTRIC CO
PA0012475 MET ED PORTLAND
PA0012742 ATLAS POWEDER CO. - REYNOLDS P
PA0013862 WYETH-AYERST LABORATORIES, INC
10/25/88 10/24/93
11/23/88 11/22/93
11/30/88 11/30/93
12/01/88 11/30/93
11/04/88 11/04/93
PA0026905 CONNELLSVILLE MUN.AUTH-STP - M 10/31/88 10/31/93
PA0051926 PHILA ELEC LIMERICK I 12/20/88 12/20/93
PA0053147 UPPER SAUCON TWP. MUN AUTH M 11/02/88 11/02/93
SDC-0055-034-ST-3003 12/13/93 2*7
-------
Basic Training
Permit Compliance System (PCS)
4.3.2 Use of PCS Acronyms to Select Faculties
Through the use of 10 card selection statements, you can use any PCS acronym to select
facilities to appear on a retrieval. For example, if you want to see all Pennsylvania major
facilities that have permit requirements for BOD (00310), use these selection statements:
00 SYNTAX=NO JOBID=NO10W TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF SELECTING BOD FOR PA MAJORS
10 STTE EQ PA
10 MADI EQ M
10 PRAM EQ 00310
20 QL SUPPRESS=YES SKIP=1
40 NPID PDSG PRAM MLOC MODN SEAN STAT FRAN SAMP LQUC LCUC
The output will look like this:
RETRIEVAL
STATEMENTS
60 SYNTAX=NO JOBID=NOlOW TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF SELECTING BOD FOR PA MAJORS
10 STTE EQ PA
10 MADI EQ M
10 PRAM EQ 00310
20 QL SUPPRESS=YES SKIP=1
40 NPID PDSG PRAM MLOC MODN SEAN STAT FRAN SAMP LQUC LCUC
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
06/15/95
EXAMPLE OF SELECTING BOD FOR PA MAJORS
QL ***************************************************** QL
NPID PDSG PRAM MLOC MODN SEAN STAT FRAN SAMP LQUC LCUC
PA0001201 001A 00300 1
001A 00310 1
001A 00400 1
001A 50050 1
001A 74055 1
PA0001295 00 1A 00310 1
"001A 00340 1
001 A 00400 1
001A 00530 1
001A 00556 1
001A 00610 1
001A 00745 1
001A 50050 1
001A 74055 1
PA0001716 009A 00310 1
009A 00400 1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
15
10
15
70
03
10
10
15
10
97
10
10
C6
03
10
15
99/99 MS
02/30 GR
99/99 RC
99/99 RC
01/30 24
01/07 24
01/07 24
01/07 GR
01/07 24
01/07 G3
01/07 24
01/07 24
99/99 MS
01/07 GR
02/30 GR
02/30 GR
26
03
26
26
26
26
26
26
03
19
12
13
12
19
13
19
12
-------
Ptennit Compliance System (PCS)
Bask Training
009A 00530 1
009A 00556 1
009A 50050 1
009A 74055 1
PA0001988 024A 00310 1
02 4A 00400 1
024A 00530 1
024A 00556 1
024A 00610 1
024A 34696 1
024A 50050 1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
10
97
70
03
70
15
70
97
. 70
70
70
02/30 GR
02/30 GR
02/30 MS 03
02/30 GR
01/07 24
01/01 GR
01/07 24
01/07 G3
01/07 24 '
02/30 24
99/99 MS 03
19
19
13
19
12
19
19
19
19
4.3.3 The 10 WITH Card
This retrieval will display all the facilities that have a BOD requirement as part of their
permit. To see only the facilities that have a permit requirement to take a BOD sample once
per week, select PRAM EQ 00310 and further qualify that statement using a 10 WITH card
that says 10 WITH FRAN EQ 01/07 as in the following example:
00 SYNTAX=NO JOBID=WTH10 TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF USING 10 WITH CARD
10 STTE EQ PA
10 MADI EQ M
10 PRAM EQ 00310
10 WITH FRAN EQ 01/07
20 QL SUPPRESS=YES
40 NPID PDSG PRAM MLOC MODN SEAN STAT FRAN SAMP LQUC LCUC
The output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=WTH10 TIME=2M PRTY=2 BIN=DOO5 RMT=255
01 HQ EXAMPLE OF USING 10 WITH CARD
10 STTE EQ PA
10 MADI EQ M
10 PRAM EQ 00310
10 WITH FRAN EQ 01/07
20 QL SUPPRESS=YES
40 NPID PDSG PRAM MLOC MODN SEAN STAT FRAN SAMP LQUC LCUC
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
12/13/93
-------
Bask Training
Permit Compliance System (PCS)
06/15/95
NPID
EXAMPLE OF USING 10 WITH CARD
******************************
PDSG PRAM MLOC MOON SEAN STAT FRAN SAMP LQUC LCUC
PA0001295 001A 00310 1
001A 00340 1
001A 00400 1
001A 00530 1
001A 00556 1
001A 00610 1
001A 00745 1
001A 50050 1
001A 74055 1
PA0002135 O01A 00300 1
001A 00310 1
001A 00400 1
001A 00530 1
00 1A 00556 1
001A 00610 1
001A 50050 1
001A 74055 1
002 A 00310 1
002A 00400 1
002A 00556 1
002A 50050 1
023B 00310 1
024B 00310 1
025B 00310 1
026B 00310 1
027B 00310 1
PA0002666 002B 00310 1
002B 00610 1
002B 01045 1
010A 00300 1
010A 00310 1
010A 00400 1
010A 00530 1
010A OO556 1
010A 00610 1
010A 00745 1
010A 50050 1
010A 74055 1
012B 00310 1
012B 00610 1
012B 01045 1
021B 00310 1
021B 00610 1
021B 01045 1
022B 00310 1
022B 00610 1
-022B 01045 1
s in the facilities listed above,
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
there
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
10
10
15
10
97
10
10
C6
03
15
10
15
10
10
10
04
03
10
15
10
04
52
52
52
52
52
10
10
10
10
10
15
10
10
10
10
04
03
10
10
10
10
10
10
10
10
10
are sometimes
01/07 24
01/07 24
01/07 GR
01/07 24
01/07 G3
01/07 24
01/07 24
99/99 MS
01/07 GR
01/07 GR
01/07 08
01/07 GR
01/07 08
01/07 G3
01/07 08
99/99 RC
01/07 GR
02/30 GR
02/30 GR
02/30 GR
02/30 MS
02/90 GR
02/90 GR
02/90 GR
02/90 GR
02/90 GR
O1/90 GR
01/90 GR
01/90 GR
01/07 GR
01/07 08
01/07 GR
01/07 08
01/O7 24
01/07 08
01/30 08
99/99 RC
01/07 GR
01/90 GR
01/90 GR
01/90 GR
01/90 GR
01/90 GR
01/90 GR
01/90 GR
01/90 GR
01/90 GR
more than
26
26
26
26
26
26
03
26
26
26
26
03
03
26
26
26
26
26
03
12
19
13
19
12
13
19
12
19
19
19
19
19
19
19
19
19
19
12
19
13
19
19
19
19
19
19
19
19
19
one BOD 1
facility and sometimes the other BOD's have a frequency of analysis that is not once per
week. In every facility there is at least one BOD that has a frequency of analysis of once per
week, every facility listed meets the selection criteria of the 10 cards. Later on, we will
learn how to restrict the output even more to see only the BOD parameters that are sampled
once per week.
25()
12/13/93
-------
Permit Compliance System (PCS) Bask Training
Suppose you want to submit a retrieval for all majors in Pennsylvania and all minor PL
92-500 grantees in Pennsylvania. How would this work? ($ is the symbol that represents PL
92-500 grantees.)
You could structure your 10 card selection statements like this:
00 SYNTAX=NO JOBID=ORCRD TIME=1M PRTY=2 BIN=D005 RMT=255
01 HQ ALL MAJORS AND MINOR PL 92-500'S IN PENNSYLVANIA
10 STTE EQ PA
10 FDGR EQ $
20 QL
40 NPID FNMS MADI FDGR
Let's see what the retrieval will look like:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=ORCRD TIME=1M PRTY=2 BIN=D005 RMT=255
01 HQ ALL MAJORS AND MINOR PL 92-500'S IN PENNSYLVANIA
10 STTE EQ PA
10 FDGR EQ $
20 QL
40 NPID FNMS MADI FDGR
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
06/15/95
ALL MAJORS AND MINOR PL 92-500'S IN PENNSYLVANIA
NPID FNMS MADI FDGR
PA0020214 MOUNT UNION BOROUGH $
PA0020257 GROVE CITY BOROUGH M $
PA0020320 LITITZ SEWAGE AUTHORITY M $
PA0020460 PENNRIDGE AUTHORITY M $
PA0020664 MIDDLETOWN WASTEWATER TREATMEN M $
PA0020699 MONTGOMERY BOROUGH $
PA0020711 TOPTON BOROUGH $
PA0020788 DERRY BOROUGH $
PA0020885 MECHANICSBURG BOROUGH MUNICIPA M $
PA0020915 PINE GROVE BOROUGH AUTHORITY $
PA0020923 NEW OXFORD MUNICIPAL FACILITY $
PA0020940 TUNKHANNOCK BOROUGH MUNICIPAL $
PA0021067 MOUNT JOY SEWAGE TREATMENT PLA M $
PA0021075 MYERSTOWN BOROUGH M $
PA0021407 BOROUGH OF POINT MARION $
PA0021504 WESTERN BUTLER COUNTY AUTH M $
PA0021601 HAMBURG BORO M $
PA0021709 BIRDSBORO BOROUGH M $
PA0021806 ANNVILLE TOWNSHIP S
SDC-0055-O34-ST-3003 T2/I3/93 251
-------
Bask Training Permit Compliance System (PCS)
Through the use of the 10 card selection statements we have chosen all Pennsylvania
facilities that have a PL 92-500 grant for majors and minors. Is that what we wanted? No!
We wanted to see all major facilities and all minors that have a PL 92-500 grant. Let's
restructure the 10 card selection statements and try again:
00 SYNTAX=NO JOBID=ORCRD TIME=1M PRTY=2 BIN=D005 RMT=255
01 HQ ALL MAJORS AND MINOR PL 92-500'S IN PENNSYLVANIA
10 STTE EQ PA
10 MADI EQ M
10 MADI NE M
10 FDGR EQ $
20 QL
40 NPID FNMS MADI FDGR
Now your selection statements are MADI EQ M to retrieve all majors and MADI NE M to
retrieve all minors and FDGR EQ $ to retrieve all PL 92-500 grantees. That sounds like
what we want. Let's take a look at the output to see what we got:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=ORCRD TIME=1M PRTY=2 BIN=D005 RMT=255
01 HQ ALL MAJORS AND MINOR PL 92-500'S IN PENNSYLVANIA
10 STTE EQ PA
10 MADI EQ M
10 MADI NE M
10 FDGR EQ $
20 QL
40 NPID FNMS MADI FDGR
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
THERE WERE NO NPDES QUALIFYING FOR THE SELECTION CRITERIA
The retrieval did not select anything!! Why? Because we have the same acronym that is
equal to a value and not equal to the same value. Remember the alternate (AL) logical
operator. If you are using the same acronym, then you must use AL unless it is a range of
values and you can use GE and LE. Then how can we do this retrieval?
This is really two separate retrievals. First, you'want to see all major facilties and then you
want to see all minor facilities that have a PL 92-500 grant. There is a way to run this
retrieval without having to submit two separate retrievals. In your selection statements
specify an OR statement that tells the system to select these facilities OR to select another set
of facilities.
252 12/13/93 SDC-0055-U:J4-i 1-
-------
Permit Compliance System (PCS) Basic Training
4.4 The 11 OR Card
This is proceeded by the card number 11 and is specified in the following manner:
00 SYNTAX=NO JOBID=ORCRD TIME=1M PRTY=2 BIN=D005 RMT=255
01 HQ ALL MAJORS AND MINOR PL 92-500s IN PENNSYLVANIA
10 STTE EQ PA
10 MADI EQ M
11 OR
10 STTE EQ PA
10 MADI NE M
10 FDGR EQ $
20 QL
40 NPID FNMS MADI FDGR
When using the 11 OR card, you must re-enter all statements that apply to the selection
statement for each type of retrieval, in this case, STTE EQ PA. That's because the system
recognizes the statement on each side of the 11 OR card as being a separate retrieval.
You can specify up to ten 11 OR cards in one retrieval. Let's take a look at the output for
this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=ORCRD TIME=1M PRTY=2 BIN=D005 RMT=255
01 HQ ALL MAJORS AND MINOR PL 92-5008 IN PENNSYLVANIA
10 STTE EQ PA
10 MADI EQ M
11 OR
10 STTE EQ PA
10 MADI NE M
10 FDGR EQ S
20 QL
40 NPID FNMS MADI FDGR
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
06/15/95
ALL MAJORS AND MINOR PL 92-SOOs IN PENNSYLVANIA
QL A******************************************************* QL
NPID FNMS MADI FDGR
PA0020125 MONACA BOROUGH MUNICIPAL AUTHO M
PA0020141 BROOKVILLE MUN AUTH M
PA0020168 EAST STROUDSBURG BORO STP M
PA0020214 MOUNT UNION BOROUGH $
PA0020257 GROVE CITY BOROUGH M $
SDC-0055-034-ST-3003
-------
Basic Training Permit Compliance System (PCS)
PA0020273 MILTON MUNICIPAL AUTHORITY M
PA002029O QUAKERTOWN BOROUGH MUNICIPAL T M
PA0020320 LITITZ SEWAGE AUTHORITY M
PA0020346 PUNXSUTAWNEY, HUN. AUTH. OF TH M
PA0020401 JOHNSONBURG BOROUGH M
PA002O460 PENNRIDGE AUTHORITY M
PA0020486 BELLEFONTE BOROUGH M
PA0020621 HAYNESBORO BOROUGH AUTHORITY M
PA0020664 MIDDLETOWN WASTEWATER TREATMEN M
PA0020699 MONTGOMERY BOROUGH
PA0020711 TOPTON BOROUGH
PA0020788 DERRY BOROUGH
PA0020826 DOVER TOWNSHIP SEWER AUTHORITY M
PA0020885 KECHANICSBURG BOROUGH MUNICIPA M
PA0020893 MANHEIM STP M
PA0020915 PINE GROVE BOROUGH AUTHORITY
PA0020923 NEW OXFORD MUNICIPAL FACILITY
PA0020940 TUNKHANNOCK BOROUGH MUNICIPAL
PA0021067 MOUNT JOY SEWAGE TREATMENT PLA M
PA0021075 MYERSTOWN BOROUGH M
PA0021113 GLASSPORT BOROUGH M
5
-5
$
$
$
$
$
$
$
$
$
$
Notice that a lot of the majors also have a PL 92-500 grant. That's because we selected
ALL majors regardless of whether they have a PL 92-500 grant or not; but also notice that
the minors are all PL 92-500 grantees, which is exactly what we want.
4.5 The 20 Card
After you have selected all of the facilities with 10 cards, the next thing you have to have is
a 20 card which tells the system what type of retrieval you are running. Currently, there are
27 different report types available in PCS. The one we are going to concentrate on for right
now is the Quick Look (QL) report. The QL report is the most versatile of the report types
because you control what your print-out is going to look like. You specify a 20 card report
type in the following format:
20 QL
where QL stands for Quick Look so the system knows that this will be a Quick Look report.
All of the report types are specified in the same manner by typing 20 and the two character
code for that report type. For more information on the types of reports available in PCS,
please refer to the PCS Generalized Retrieval manual.
4.6 The 30 Card
The next card for a QL retrieval is the 30 card which tells the system how to sort the
facilities that you have selected. The 30 card is optional. If you do not include a 30 card in
your request, the system will sort by region, state, the NPDES permit number (NPID) then
by the key data elements for the type of data you are displaying.
254 12/13793 SDC-0055-034-5T-3003
-------
Permit Compliance System (PCS)
Basic Training
To specify a sort on a retrieval, type 30 followed by the acronyms that you want to sort on
in the order that you want the report sorted as in the following example:
30 MADI FNMS
This tells the system that you want to sort the retrieval by the major discharge indicator and
then by the facility name. An example of this is below:
09/19/95
SORTING A RETRIEVAL WITH THE 30 CARD
QL
NPID FNMS MADI
QL
SC0043567
SC0042595
SC0037621
SC0028754
SC0034461
SC0032182
SC0021121
SC0042919
SC00305S4
SC0001716
SC0035319
SC0036226
SC0004014
SC0040363
SC0026018
SC0022705
SC0028622
SCO031968
SC0022381
SC0031577
SC0043001
SC0028673
SC0042277
SC0025950
SC0040614
SC0025143
SC0021032
SC0039624
SC0039853
SC0004162
SC0003115
SC0021318
SC0025933
SC0000582
SC0038164
SC0020257
SC0024490
SC0033553
SC0035700
SC0001490
SC0002020
SC0040517
SC0038121
SC0001341
SC0020214
SC0038156
ABBEVILLE CITY BARN/GROUND WTR
BAHBERG BOARD OF PUBLIC WORKS
CAINHOY ELEMENTARY SCHOOL
DACUSVILLE EL fi HS/PICKENS CO
EARL OWENSBY STUDIOS
FAIRFAX SD/THE DEVELOPMENT COR
GAFFNEY TOWN OF/WATER PLANT
HAGLEY LAKE CO INC
IDLEWOOD SD/CAROLINA HATER
JACKSON MILLS/HELLFORD PLANT
KAYDON CORPORATION
LAKE CITY-SCRANTON CONVLST CTR
MACALLOY CORP-CHARLESTON
NATIONAL DYE WORKS
OAK GROVE ELEMENTARY SCHOOL
P T L HERITAGE VILLAGE
QUAIL MEADOW PARK
Road King Truck Stop
SALUDA TOWN OF
TALL TALES FISH CAMP
UNION AMOCO STATION
VALLEYBROOK SD/CAROLINA WATER
W R GRACE/BALL MINE
YEMASSEE TOWN OF
ABBEVILLE CITY OF/LONG CANE CR M
BARNWELL CITY OF M
CAMDEN, CITY OF M
DARLINGTON/WWTF-BLACK CRK M
EASLEY/MIDDLE BRANCH WWTP M
FIBER INDUSTRIES INC M
GA PACIFIC/RUSSELLVILLE PLT M
HAMPTON TOWN OF M
JOHNSONVILLE/EAST PLANT M
KIMBERLY-CLARK CORP M
LAKE CITY/LAKE SWAMP PLANT M
MARION/SOUTH MAIN STREET PLANT M
NEWBERRY/BUSH RIVER PLT M
OCONEE CO SWR COM-CONEROSS CRK M
PENDLETON-CLEMSON REGIONAL SWR M
REEVES BROS/BISHOPVILLE FINISH M
SC ELEC & GAS/CANADYS STATION M
THERMAL OXID CORP/GSX M
UNION CAMP CORPORATION M
VERATEC M
WARE SHOALS/DAIRY STREET PLANT M
YORK / FISHING CREEK (NEW) M
SDC-UU55-O34-ST-3U03
12/13/93
255
-------
Permit Compliance System (PCS)
4.7 The 40 Card
The next card you need for a QL retrieval is the 40 card. The 40 card tells the system how
to display the data on your print-out and is exclusive to the QL report. You specify the 40
card by typing 40 and list the acronyms you want on your retrieval with one space between
each acronym as in the following manner:
40 NPID FNMS MADI TYPO SIC2 INCL FTYP
The acronyms that you list on the 40 card become the headers on your print-out. The
print-out for the example above would look like this:
06/15/95
RETRIEVAL EXAMPLE
QL ******************************************************* QL
NPID FNMS MADI TYPO SIC2 INCL FTYP
PA0021181 DOYLESTOWN BOROUGH (GREEN ST S PUB 4952 M M
PAOO21237 NEWPORT BOROUGH MUNICIPAL AUTH PUB 4952 M M
4.8 Retrievals With Options on the 20 Card
You are allowed to display 132 characters of data on one line of your retrieval so a retrieval
is more versatile than INQUIRY. As you will notice, the headers are still the acronyms that
you specified on the 40 card. If you are giving this retrieval to somebody who is not
knowledgeable of PCS acronyms, this may be confusing.
4.8.1 HEADERS=LONG
You can make the headers display in expanded form by specifying HEADERS =LONG on
the 20 card in the following manner:
00 SYNTAX=NO JOBID=HEADR TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF HEADERS=LONG
10 STTE EQ SC
10 FTYP ALI
10 FTYP AL M
20 QL HEADERS=LONG
40 NPID FNMS FTYP
The output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID-HEADR TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF HEADERS=LONG
10 STTE EQ SC
10 FTYP AL I
23512/13/93 SDC-O055-034-ST-3003
-------
Permit Compliance System (PCS) Baric Training
10 FTYP AL M
20 QL HEADERS=LONG
40 NPZD FNMS FTYP
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
09/15/95
EXAMPLE OF HEADERS=LONG
QL ******************************************************* QL
PERMIT NUMBER FACILITY NAME SHORT FACILITY TYPE
SC0000043 GRANITEVILLE CO/GREGG HATER PT
SC0000051 GRANITEVILLE CO/WATER PLANT
SC0000876 STONE CONTAINER CORP/FLORENCE
SC0000906 AMOCO PERFORMANCE PRODUCTS INC
SC0000914 LOBECO PRODUCTS INC
SC0000949 TIMKEN CO/GAFFNEY BEARING PLT
SC0000957 SSSD/BUCKEYE FOREST PLANT M
SC0001724 SIEMENS-ALLIS/ITE ELECT PROD I
SC0001741 CHESTER/MANETTA MILLS M
SC0020010 CLEMSON/MAIN PLANT M
SC0020052 SULLIVANS ISLAND TOWN OF M
Using HEADERS =LONG increases the print size of the data element to accommodate the
longer headings. Because of this, you will not be able to display as many acronyms on one
line.
4.8.2 EXPAND=YES and 'D' Acronym
Any acronym that you are displaying that has a code as the value will display the code. This
could be confusing to people unfamiliar with PCS. You can display the description of that
code in one of two ways.
You can use EXPAND=YES on the 20 card to display the descriptions of the codes. This
will expand every code that is being displayed on your retrieval. It is specified in the
following manner:
00 SYNTAX=NO JOBID=EXPND TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF EXPAND=YES
10 SITE EQ SC
10 CNTY EQ 003
20 QL HEADERS =LONG EXPAND=YES
40 NPID FNMS FTYP MADI FDGR
SDC-0055-034-ST-3003 12/13/93 an
-------
Bask Training Permit Cop^r"0"^ System (PCS)
The output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX-NO JOBID=EXPND TZHE-2N PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF EXPAND=YES
10 STTE EQ SC
10 CNTY EQ 003
20 QL HEADERS=LONG EXPAND=YES
4O NPZD FNMS PTYP MADI FD6R
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
09/20/95
EXAMPLE OF EXPAND=YES
PERMIT NUMBER FACILITY NAME SHORT FACILITY TYPE MAJ/MIN IND FED GRNT IND
SCOOOOO43 GRANITEVILLE CO/GREGG WATER PT INDUSTRIAL MINOR
SCOOOOO51 GRANITEVILLE CO/HATER PLANT INDUSTRIAL MINOR
SCO000175 US DEPARTMENT OF ENERGY FEDERAL MAJOR
SCOO00574 SC ELEC & GAS/URQUHART STM STA INDUSTRIAL MAJOR
SCOOOOS82 KIMBERLY-CLARK CORP INDUSTRIAL MAJOR
SC0024457 AIKEN CO PUB SV AUTH/HORSE CRK MUNICIPAL MAJOR FEDERAL GRANT
SC0026204 WAGENER TOWN OF MUNICIPAL MINOR
SC0030368 N AUGUSTA/BELVEDERE TERRACE SD MUNICIPAL MINOR
This method will expand all of the acronyms on your retrieval that can be expanded. This
may not be what you want. If you only wanted to expand some of the acronyms but not all
of them, you can use the second method to expand acronyms. In this method, you type a
'D' at the end of the acronym that you want expanded as in the following example:
00 SYNTAX=NO JOBID=DESCR TTME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF DESCRIPTION
10 STTE EQ SC
10 CNTY EQ 003
20 QL HEADERS =LONG
40 NPID FNMS FTYPD MADI FDGR
258 12/13/93
-------
Permit Compliance System (PCS) Basic Training
In this example, a 'D' was typed at the end of FTYP so a description will be printed for this
acronym, but the other acronyms will still be printed as codes. Your output will look like
this:
RETRIEVAL
STATEMENTS
00 SYNTAX-NO JOBID=DESCR TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF DESCRIPTION
10 STTE EQ SC
10 CNTY EQ 003
20 QL HEADERS*»LONG
40 NPID FNMS FTYPD MADI FDGR
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
09/20/95
EXAMPLE OF DESCRIPTION
QL ft*********************************************************** QL
PERMIT NUMBER FACILITY NAME SHORT FACILITY TYPE MAJ/MIN IND FED GRNT IND
SC0000043
SC0000051
SC0000175
SC0000574
SC0000582
SC0024457
SC0026204
SC0030368
GRANITEVILLE CO/GREGG HATER PT INDUSTRIAL
GRANITE VILLE CO/WATER PLANT INDUSTRIAL
US DEPARTMENT OF ENERGY FEDERAL
SC ELEC & GAS/URQUHART STM STA INDUSTRIAL
KIMBERLY-CLARK CORP INDUSTRIAL
AIKEN CO PUB SV AUTH/ HORSE CRK MUNICIPAL
WAGENER TOWN OF MUNICIPAL
N AUGUSTA/BELVEDERE TERRACE SD MUNICIPAL
M
M
M
M
$
A 'D' can be used at the end of any acronym that has a description for the code.
4.8.3 SKIP=x
To make your retrieval more readable, you can skip lines between facilities. On the 20 card,
you type SKIP=x where x is the number of lines that you want to skip. You are allowed to
skip up to 3 lines.
You specify skip in the following manner:
00 SYNTAX=NO JOBID=SKIP TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF HEADERS =LONG and SKIP=1
10 STTE EQ SC
10 FTYP AL I
10 FTYP ALM
20 QL HEADERS=LONG SKIP=1
40 NPID FNMS FTYP
SDC-0055-034-ST-3003 12/13/93
-------
Training Permit CopipHa"^ System (PCS)
This will skip one line between facilities. Your output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=SKIP TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF SKIP
10 STTE EQ SC
10 FTYP AL I
10 FTYP AL M
20 QL KEADERS=LONG SKIP=1
40 NPID FNMS FTYP
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
09/19/95
EXAMPLE OF SKIP
QL A****************************************************** QL
PERMIT NUMBER FACILITY NAME SHORT FACILITY TYPE
SC0000043 GRANITEVILLE CO/GREGG WATER PT I
SC0000051 GRANITEVILLE CO/WATER PLANT I
SC0000876 STONE CONTAINER CORP/FLORENCE I
SC0000906 AMOCO PERFORMANCE PRODUCTS INC I
SC0000914 LOBECO PRODUCTS INC I
SC0000949 TIMKEN CO/GAFFNEY BEARING PLT I
SCOOOO957 SSSD/BUCKEYE FOREST PLANT M
SC0001724 SIEMENS-ALLIS/ITE ELECT PROD I
SC0001741 CHESTER/MANETTA MILLS M
SC0020010 CLEMSON/MAIN PLANT M
SC0020052 SULLIVANS ISLAND TOWN OF M
Inspection With Options
If you want a QL retrieval of inspections that have been performed at a facility, the report is
going to list each inspection on a separate line. The NPDES number and the facility name
will be repeated on every line. This is because the DTTN, INSP and TYPI are listed more
than one time and the facility data is repeated every time a new DTTN is listed which can
make it very confusing to read the report.
260 T2/1379J SDC-O055-OJ4-ST-3003
-------
Permit Compliance System (PCS) Raw Training
SKIP=1
To make the report more readable, you can use the SKIP option and skip a line between
facilities like this:
EXAMPLE OF INSPECTIONS
QL ************************* QL
NPID FNMS DTIN INSP TYPI
SC0000043 GRANTTEVILLE CO/GREGG WATER PT 10/20/87 S S
SC0000051 GRANTTEVELLE CO/WATER PLANT
SC0000078 GRANTTEVILLE CO/WOODHEAD DIV 11/19/85 S R
SC0000078 GRANTTEVILLE CO/WOODHEAD DIV 11/20/85 S S
SC0000078 GRANTTEVILLE CO/WOODHEAD DIV 05/21/86 S S
SC0000078 GRANTTEVILLE CO/WOODHEAD DIV 11/05/86 S S
SC0000078 GRANITEVILLE CO/WOODHEAD DIV 10/20/87 S S
SC0000078 GRANITEVILLE CO/WOODHEAD DIV 01/26/88 S B
SC0000078 GRANITEVILLE CO/WOODHEAD DIV 05/09/88 S R
SC0000078 GRANITEVILLE CO/WOODHEAD DIV 09/06/88 S S
SC0000078 GRANITEVILLE CO/WOODHEAD DIV 04/04/89 S S
SC0000086 GRANITEVILLE CO/HICKMAN DIV 11/19/85 S R
SC0000086 GRANITEVILLE CO/HICKMAN DIV 11/20/85 S S
SC0000086 GRANITEVILLE CO/HICKMAN DIV 05/21/86 S S
SC0000086 GRANITEVILLE CO/HICKMAN DIV 11/05/86 S S
SC0000086 GRANITEVILLE CO/HICKMAN DIV 10/20/87 S S
SC0000086 GRANITEVILLE CO/HICKMAN DIV 05/09/88 S R
SC0000086 GRANITEVILLE CO/HICKMAN DIV 09/06/88 S S
SC0000086 GRANITEVILLE CO/HICKMAN DIV 04/04/89 S S
SC0000094 GRANTTEVILLE CO/STEVENS STEAM 11/19/85 S R
SC0000094 GRANITEVILLE CO/STEVENS STEAM 11/20/85 S S
SC0000094 GRANITEVILLE CO/STEVENS STEAM 05/22/86 S S
SC0000094 GRANITEVILLE CO/STEVENS STEAM 11/05/86 S S
SC0000094 GRANITEVILLE CO/STEVENS STEAM 10/20/87 S S
SC0000094 GRANITEVILLE CO/STEVENS STEAM 05/09/88 S R
SC0000094 GRANITEVILLE CO/STEVENS STEAM 09/06/88 S S
SC0000094 GRANITEVILLE CO/STEVENS STEAM 04/04/89 S S
This makes the report easier to read because all data for one facility is listed together. There
is still the problem-of the facility data being repeated for every DTIN.
5UC-UU33-UJ4-M-3UU3 12/13/93 2ol
-------
Basic Training Permit Compliance System (PCS)
4.8.4 SUPPRESS=YES
There is another 20 card option that will solve the problem called SUPPRESS=YES. It is
listed on the 20 card in the following manner:
00 SYNTAX=NO JOBID=SUPPR TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF SUPPRESS=YES
10 STTE EQ SC
10FTYP ALI
10FTYP ALM
20 QL SUPPRESS=YES SKIP=1
40 NPID FNMS DTIN INSP TYPI
The output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID«SUPPR TIME=2M PRTY=2 BIN=DOO5 RMT=255
01 HQ EXAMPLE OF SUPPRESS=YES
10 STTE EQ SC
10 FTYP AL I
10 FTYP AL M
20 QL SUPPRESS=YES
40 NPID FNMS DTIN INSP TYPI
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
EXAMPLE OF SUPPRESS=YES
QL ******************************************************* QL
NPID FNMS DTIN INSP TYPI
SC0000043 GRANITEVILLE CO/GREGG WATER PT 10/20/87 S S
SC0000051 GRANITEVILLE CO/HATER PLANT
SC0000078 GRANITEVILLE CO/WOODHEAD DIV 11/19/85 S R
11/20/85 S S
05/21/86 S S
11/05/86 S S
10/20/87 S S
01/26/88 S B
05/09/88 S R
09/06/88 S S
04/04/89 S S
SUPPRESS=YES only suppresses facility data that is being displayed on your retrieval. The
facility data will be printed on the first line of that facility.
262 12/13/93 SDC-0055-034-i I -JIXU
-------
Permit Compliance System (PCS) Bask Training
4.8.5 PAGE BREAK
No PAGE BREAK
You could sort your retrieval in such a way that a group of facilities would be displayed
together. For example, there is a data element at the facility level called Engineer's Initials
(ENGI) that allows you to enter the initials of the engineer that is responsible for that permit.
You could sort by ENGI so that all of the facilities assigned to a particular engineer are
grouped together as in the following example:
00 SYNTAX=NO JOBID=BREAK TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF NO PAGE BREAK
10 STTE EQ FL
20 QL
30 ENGI
40 NPID FNMS CNTY ENGI MADI FTYP
The output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=BREAK TIME=2M PRTY=2 BIN=O005 RMT=255
01 HQ EXAMPLE OF NO PAGE BREAK
10 STTE EQ FL
20 QL
30 ENGZ
40 NPZD FNMS CNTY ENGI MADI FTYP
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
09/21/95 PAGE: 1
EXAMPLE WITHOUT PAGE BREAK
NPID FNMS CNTY ENGI MADI FTYP
FL0000124
FL0000370
FL0000523
FL0000752
FL0001589
FL0037915
FL0000060
FL0001678
FL0002313
FL0002593
FL0028592
FL0040380
FL0040967
FL0041378
ROYSTER PHOSPHATES INC
AGRICO CHEM SO PIERCE
C F CHEM BARTOW PHOSPH BARTOW
FARMLAND IND BARTOW
SEMINOLE FERT. CORP. -BARTOW COM
FARMLAND INDUSTRIES INC
REICHHOLD CHEM JAX
TRI-GAS INC.
AIR PROD 6 CHEM ESCAM PENSACOL
AMERICAN CYANAMID
RONNYS MOBILE RANCH
HILLSBORO CO-APOLLO BCH SPRAY
GEN DEV UTIL - N PORT ST LUCIE
FORT LAUDERDALE - GT LOHMEYER
081
105
105
105
105
105
031
099
113
113
085
057
111
Oil
AEZ
AEZ
AEZ
AEZ
AEZ
AEZ
ALF
ALF
ALF
ALF
ALF
ALF
ALF
ALF
M
M
M
M
M
M
M
M :
M 1
]
1
]
1
:
[
[
4
C
1
SDC-0055-034-ST-3003 1Z/13/9J
-------
Bask Training Permit Compliance System (PCS)
FL0041432 HERCULES INCORPORATED VERO BCH 061 ALF I
FL0003034 HOLLY HILL WATER TREAT 127 BCC I
FL0020591 JAX SAN JOSE SHOR STP 031 BCC M
FL0024201 WHISPERING CR VILL-FT PIERCE 111 BCC I
FL0027839 MONTICELLO-STP 065 BCC M
FL0033758 NORTHEAST FL STATE HOSP 003 BCC M I
PAGE BREAK
If you wanted to separate this retrieval and give each engineer the page with only their
facilities listed, you would have to cut the report with a pair of scissors. However, there is
an option on the 20 card that will provide a page break depending on the acronym(s) you
have specified on the sort (30) card. In this case, it would provide a page break on the
engineer's initials because that is the acronym that is used to sort the retrieval. You specify
a page break on the 20 card in the following manner:
00 SYNTAX=NO JOBID=BREAK TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF PAGE BREAK
10 STTE EQ FL
20QLBREAK=1
30ENGI
40 NPID FNMS CNTY ENGI MADI FTYP
The output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=BREAK TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF PAGE BREAK
10 STTE EQ FL
20 QL BREAK=1
30 ENGI
40 NPID FNMS CNTY ENGI MADI FTYP
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
264 12/13/93 SDC-0055-034-&I-.3UU.J
-------
Permit O-"p'^nr«> System (PCS) Basic Training
09/21/95 PAGE: 1
EXAMPLE OF PAGE BREAK
QL ****************************************************** QL
NPID FNMS CNTY ENGI MAD I FTYP
FL0000124 ROISTER PHOSPHATES ZNC 081 AEZ M I
FL0000370 AGRICO CHEM SO PIERCE 105 AEZ M I
FL0000523 C F CHEM BARTON PHOSPH BARTOW 105 AEZ M Z
FL0000752 FARMLAND IND BARTOW 105 AEZ M Z
FL0001589 SEMINOLE FERT.CORP.-BARTOW COM 105 AEZ M Z
FL0037915 FARMLAND INDUSTRIES INC 105 AEZ M Z
SUB-TOTAL QUZCK LOOK PRINT LINES: 6
09/21/95 PAGE:
EXAMPLE OF PAGE BREAK
QL ******************************************************
NPID FNMS CNTY ENGI HAD! FTYP
FL0000060 REICHHOLD CHEM JAX 031 ALF M I
FL0001678 TRI-GAS INC. 099 ALF I
FL0002313 AIR PROD 6 CHEM ESCAM PENSACOL 113 ALF M I
FL0002593 AMERICAN CYANAMID 113 ALF M I
FL0028592 RONNYS MOBILE RANCH 085 ALF Z
FL0040380 HZLLSBORO CO-APOLLO BCH SPRAY 057 ALF M
FL0040967 GEN DEV OTZL - N PORT ST LUCIE 111 ALF Z
FL0041378 FORT LAUDERDALE - GT LOHMEYER Oil ALF M
FL0041432 HERCULES INCORPORATED VERO BCH 061 ALF Z
SUB-TOTAL QUZCK LOOK PRINT LZNES: 9
09/21/95 PAGE: 3
EXAMPLE OF PAGE BREAK
QL ****************************************************** QL
NPZD FNMS CNTY ENGI MAD I FTYP
FLO003034 HOLLY HILL WATER TREAT 127 BCC Z
FL0020591 JAX SAN JOSE SHOR STP 031 BCC M
FL0024201 WHZSPERZNG CR VZLL-FT PZERCE 111 BCC Z
FL0027839 MONTZCELLO-STP 065 BCC M
FL0033758 NORTHEAST FL STATE HOSP 003 BCC M Z
SUB-TOTAL QUZCK LOOK PRINT LINES: 5
TOTAL QUICK LOOK PRINT LINES: 20
If you specified more than one field on the 30 Card, you could specify BREAK=n, where n
equals any number from 1 through 9.
4.8.6 TAB
When a display line is printed on a retrieval, the system automatically adds one space
between fields. You might want more than one space and you can accomplish this by the use
of the TAB option.
The TAB option is used on a 40 card in the exact place where you want the tab inserted.
You must type TAB plus the number of spaces you want to insert as in the following
manner
12/13/93
-------
Basic Training Pamit Compliance System (PCS)
00 SYNTAX=NO JOBID=TAB TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF TAB
10 STTE EQ SC
10 CNTY EQ 003
20 QL TOP=YES
40 NPID FNMS TAB4 MADI TAB4 FTYP
The output will look like this:
RETRIEVAL
STATEMENTS
OO SYNTAX=NO JOBZD=TAB TIME^ZM PRTY=2 BIN=DOO5 RHT=255
01 HQ EXAMPLE OF TAB
10 STTE EQ SC
10 CNTY EQ 003
20 QL TOP-YES
40 NPID FNMS TAB4 MADI TAB4 FTYP
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
09/21/89 PAGE: 1
EXAMPLE OF TAB
OL **************************************************** QL
NPID FNMS MADI FTYP
SC0000043 GRANITEVILLE CO/GREGG HATER PT I
SCOOOOOS1 GRANITEVILLE CO/WATER PLANT I
4.8.7 Multiple Display Lines
On a QL retrieval, you can display up to 132 characters on a 40 card. Sometimes this may
not be enough room so you are allowed to use more than one 40 card to display data. You
are allowed to use up to five 40 cards and each 40 card can display 132 characters. You
specify additional 40 cards by typing 40 followed by a / and then the acronyms you want as
in the following example:
00 SYNTAX=NO JOBID=TOP TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF MULTIPLE DISPLAY LINES
10 STTE EQ SC
10 CNTY EQ 003
20 QL
40 NPID FNMS MADI FTYP
40 / CSCH DSCD EVNT DTSC DTAC
266 12/13/93 SDC-0055HW-& 1 -JOOJ
-------
Permit Campfiance System (PCS) Bask Training
This is going to print two lines on your retrieval like this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=TOP TIME=2M PRTY=2 BIN»DOO5 KMT=255
01 HQ EXAMPLE OF MULTIPLE DISPLAY LINES
10 STTE EQ SC
10 CNTY EQ 003
20 QL
40 NPID FNMS MADI FTYP
40 / CSCH DSCD EVNT DTSC OTAC
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
09/21/95 PAGE: 1
EXAMPLE OF MULTIPLE DISPLAY LINES
QL ft*************************************************** QL
NPID FNMS MADI FTYP
SC0000043 GRANITEVILLE CO/GREGG WATER PT I
CSCH DSCD EVNT DTSC DTAC
01 0745 00099
01 0745 00199 01/01/89 12/09/88
01 0745 00299 01/01/90
01 0745 00399 01/01/91
01 0745 00999 10/01/89
01 0745 15099 04/01/89
01 0745 95499 01/01/90
NPID FNMS MADI FTYP
SC0000051 GRANITEVILLE CO/WATER PLANT I
CSCH DSCD EVNT DTSC DTAC
01 0745 00099
01 0745 00199 01/01/88 12/31/87
01 0745 00299 01/01/89 01/20/89
01 0745 00399 01/01/91
02 0745 00999 04/01/88
02 0745 15099 10/01/87
NPID FNMS MADI FTYP
SC0000078 GRANITEVILLE CO/WOODHEAD DIV I
CSCH DSCD EVNT DTSC DTAC
01 0745 00099
SDC-0055-034-ST-3003 12/13/yj
-------
Bask Training Permit Compliance System (PCS)
4.8.8 TOP-YES
You will notice that on every display line, the headers are also displayed. This can take up
room on your report so you may not want the headers displayed on every line. On the 20
card you can specify TOPYES and this tells the system to print the headers at the top of
each page only one time as in the following example:
00 SYNTAX=NO JOBID=TAB TTME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF TOP=YES
10 STTE EQ SC
10 CNTY EQ 003
20QLTOP=YES
40 NPID FNMS MADI FTYP
40 / TABS CSCH DSCD TAB2 EVNT TAB2 DTSC TAB2 DTAC
The output will look like this:
RETRIEVAL
STATEMENTS
OO SYNTAX«NO JOBID=TOP TIME=2M PRTY=2 BIN»D005 RMT=255
01 HQ EXAMPLE OF TOP=YES
10 STTE EQ SC
10 CNTY EQ 003
20 QL TOP=YES
40 NPID FNMS MADI FTYP
40 / CSCH DSCD EVNT DTSC DTAC
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
09/21/95 PAGE: 1
EXAMPLE OF MULTIPLE DISPLAY LINES
QL A*****************************************************
NPID FNMS MADI FTYP
CSCH DSCD EVNT DTSC DTAC
SC0000043 GRANITEVILLE CO/GREGG WATER PT
01 0745 00099
01 0745 00199 01/01/89 12/09/88
01 0745 00299 01/01/90
01 0745 00399 01/01/91
01 0745 00999 10/01/89
01 0745 15O99 04/01/89
01 0745 95499 01/O1/90
SCOOOOOS1 GRANITEVILLE CO/WATER PLANT
01 0745 00099
01 0745 00199 01/01/88 12/31/87
01 0745 00299 O1/01/89 01/20/89
01 0745 00399 01/01/91
02 0745 00999 04/01/88
02 0745 15099 10/01/87
12/13/93 SDC-0055-034-ST-3U03
-------
Permit Compliance System (PCS) Bask Training
4.8.9 Indenting Multiple Line Reports
When you have more than one 40 card in your retrieval, you are not allowed to use the
option SUPPRESSYES. The above report could be a little confusing to read because
everything is left-justified. You can use the TAB option on the 40 card to indent the line to
make it more readable as in the following example:
00 SYNTAX=NO JOBID=TAB TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF INDENTING MULTIPLE LINE REPORTS
10 STTE EQ SC
10 CNTY EQ 003
20 QL TOP=YES
40 NPID FNMS MADI FTYP
40 / TAB3 CSCH DSCD TAB2 EVNT TAB2 DTSC TAB2 DTAC
The output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX =»NO JOBID=TAB TIME°2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF INDENTING MULTIPLE LINE REPORTS
10 STTE EQ SC
10 CNTY EQ 003
20 QL TOP=YES
40 NPID FNMS MADI FTYP
40 / TAB3 CSCH DSCD TAB2 EVNT TAB2 DTSC TAB2 DTAC
** DEFAULTS IN EFFECT **
10 IACC EQ A
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
O9/21/95 PAGE: 1
EXAMPLE OF INDENTING MULTIPLE LINE REPORTS
QL *************************************************** QL
NPID FNMS MADI FTYP
CSCH DSCD EVNT DTSC DTAC
SC0000043 GRANITEVILLE CO/GREGG HATER PT
01 0745 00099
01 0745 00199 01/01/89 12/09/8B
01 0745 - 00299 01/01/90
01 0745 00399 01/01/91
01 O745 00999 10/01/89
01 0745 15099 04/01/89
01 0745 95499 01/01/90
SC0000051 GRANITEVILLE CO/HATER PLANT
01 0745 00099
01 0745 00199 01/01/88 12/31/87
01 0745 00299 01/01/89 01/20/89
01 0745 00399 01/01/91
02 0745 00999 04/01/88
02 0745 15099 10/01/87
SDC-0055-034-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
4.9 The 40 WITH Card
Earlier, there was an example of a retrieval that was choosing BOD with a frequency of
analysis of 01/07 and the example listed those BODs plus all of the other parameters in the
system for that outfall. The reason everything is listed is because the 10 cards select the
facilities that have the characteristics of all of the 10 cards so in that example, the retrieval
selected the facilities that had BOD with a frequency of analysis of 01/07. As you
remember, the 40 card displays the acronyms in the order that you specify but when the
facility has been selected using the 10 cards everything for that facility is selected and
displayed using the 40 cards. In order to narrow the display of data for a particular facility,
you have to use 40 WITH cards and repeat the characteristics that you specified using the 10
cards as in the following example:
00 SYNTAX=NO JOBID=WTH40 TIME=2M PRTY=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF USING 40 WITH CARD
10 STTE EQ PA
10 MADI EQ M
10 PRAM EQ 00310
10 WITH FRAN EQ 01/07
20 QL SUPPRESS = YES
40 NPID PDSG PRAM MLOC MODN SEAN STAT FRAN SAMP LQUC LCUC
40 WITH PRAM EQ 00310
40 WITH FRAN EQ 01/07
The output will look like this:
RETRIEVAL
STATEMENTS
00 SYNTAX=NO JOBID=WTH40 TIME=2M PRT5f=2 BIN=D005 RMT=255
01 HQ EXAMPLE OF USING 40 WITH CARD
10 STTE EQ FA
10 MADI EQ M
10 PRAM EQ 00310
10 WITH FRAN EQ 01/07
20 QL SUPPRESS=YES
40 NPID PDSG PRAM MLOC MODN SEAN STAT FRAN SAMP LQUC LCUC
40 WITH PRAM EQ 00310
40 WITH FRAN EQ 01/07
** DEFAULTS IN EFFECT **
10 IACC EQ A -
10 PTYP AB
NO ERRORS DETECTED - REQUEST CAN BE PROCESSED
270 12/13/93 SDC-OU55-034-ST-3U03
-------
Permit Compliance System (PCS) Basic Training
06/19/95
EXAMPLE OF USING 40 WITH CARD
OL ******************************************************* QL
NPID PDSG PRAM KLOC MOON SEAN STAT FRAN SAMP LQUC LCUC
PA0001295 001A 00310 1 0 0 10 01/07 24 26
PA0002135 001A 00310 1 0 0 10 01/07 08 26
PA0002666 010A 00310 1 0 0 10 01/07 08 26
The only rule you have to follow using 40 WITH cards is the last acronym you use on your
40 card must be from the same data type as the acronym on your 40 WITH card as in the
following example:
40 NPID CSCH EVNT DTSC PDSG PRAM MLOC
40 WITH PRAM EQ 00310
SDC-0055-034-ST-3003 12/13/93 271
-------
Permit Compliance System (PCS) Basic Training
Appendix A
PCS Code Tables
-------
Permit Compliance System (PCS) Bask Training
PCS CODE TABLES
The following tables are used with the FAC1 screen:
140 SIC CODES (1987) (BIC2)
4923 GAS TRANSMISSION AND DISTRIBUT
4924 NATURAL GAS DISTRIBUTION
4925 GAS PRODUCTION/DISTRIBUTION
4931 ELEC & OTHER SERVICES COMBINED
4932 GAS & OTHER SERVICES COMBINED
4939 COMBINATION UTILITY SVC, NEC
4941 WATER SUPPLY
4952 SEWERAGE SYSTEMS
4953 REFUSE SYSTEMS
4959 SANITARY SERVICES, NEC
4961 STEAM SUPPLY
4971 IRRIGATION SYSTEMS
5012 AUTOS & OTHER MOTOR VEHICLES
5013 AUTOMOTIVE PARTS AND SUPPLIES
410 TYPE OF APPLICATION CODES (TYPA)
LA STANDARD A
LC STANDARD B
LR RAPP
SA SHORT A
SB SHORT B
SC SHORT C
SD SHORT D
TS TENN. SHORT
2A MUNICIPAL
2B ANIMAL/AQUATIC
2C INDUSTRIAL
2D NEW SOURCES
2E NO WASTEWATER
SDC-0055-034-ST-3(KK 12/13/93
-------
Rqyir Training
Permit Compliance System (PCS)
200 TYPE OF OWNERSHIP CODES
(TYPO)
BPP
FED
PRI
PUB
STA
PUB PRI
FEDERAL
PRIVATE
PUBLIC
STATE
205 FACILITY TYPE INDICATOR
(FTYP)
F
I
M
O
FEDERAL
INDUSTRIAL
MUNICIPAL
OTHER
380 PRETREATMENT PROGRAM REQUIRED INDICATOR CODES
(PRET)
C
R
Y
COVERED
PRET PROG REQD - NOT APPROVED
APPROVED PRETREATMENT PROGRAM
400 NEW SOURCE CODES
(NEWS)
(blank) STD NPDES PERMIT
D NEW DISCHARGE PERMIT
EX EXEMPT
N NEW SOURCE PERMIT
NO NEW SOURCE PERMIT (OTH)
NW NEW SOURCE PERMIT (OWE)
12/13/93
-------
Permit Compliance System (PCS)
Training
The following code tables are used with the FAC2 screen:
510 KMP FINAL SCHEDULE
(NPSC)
A
C
P
R
FINAL SCH SET-AO
ACHIEVED COMPLIANCE
FINAL SCH SET-PERMIT
CASE FILED
520 NMP FINANCIAL STATUS OF POTW
(NPFF)
0
1
2
3
4
FINANCIAL STAT-UNKNOWN
FINANCIAL STAT-NOT ISSUE
FINANCIAL STAT-ISSUE
UNDER CONST.-92-500
UNDER CONST.-STATE
SDC-0055-Q34-ST-3003
12/13/93
A-3
-------
Training
Permit Compliance System (PCS)
530
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
s
T
U
V
W
X
Y
Z
1
2
3
440
C
D
E
N
P
R
S
T
MMF QUARTER SCHEDULE ESTABLISHED
QTR ENDING 3/31/84
QTR ENDING 6/30/84
QTR ENDING 9/30/84
QTR ENDING 12/31/84
QTR ENDING 3/31/85
QTR ENDING 6/30/85
QTR ENDING 9/30/85
QTR ENDING 12/31/85
QTR ENDING 3/31/86
QTR ENDING 6/30/86
QTR ENDING 9/30/86
QTR ENDING 12/31/86
QTR ENDING 3/31/87
QTR ENDING 6/30/87
QTR ENDING 9/30/87
QTR ENDING 12/31/87
QTR ENDING 3/31/88
QTR ENDING 6/30/88
QTR ENDING 9/30/88
QTR ENDING 12/31/88
QTR ENDING 03/31/89
QTR ENDING 06/30/89
QTR ENDING 09/30/89
QTR ENDING 12/31/89
QTR ENDING 03/31/90
QTR ENDING 06/30/90
QTR ENDING 06/30/90
QTR ENDING 09/30/90
QNCR STATUS CODES
COMPLIANT
NON-COMPLIANT (DMR NON-RECEIPT)
NON-COMPLIANT (SNC EFF VIOLATIONS)
NON-COMPLIANT (RNC VIOLATIONS)
RESOLVED PENDING
RESOLVED
NON-COMPLIANT-SNC COMPLIANCE SCHEDULE
NON-COMPLIANT-SNC COMPLIANCE SCHEDULE
(NPSOJ
(CYQS)
VIOLATIONS
REPORT
12713793-
-------
Permit Compliance System (PCS) Basic Training
The following tables are used with the FAGD and OFGD screens:
471 LATITUDE/LONGITUDE METHOD DESCRIPTIONS (FLLK, PLLM)
A MAP INTERPOLATION
B NAVIGATION-QUALITY GPS
C REMOTE SENSING
D ZIP CODE CENTROID
U UNKNOWN
1 ADDRESS MAPPING
2 AERIAL PHOTO W/ GROUND CONTROL
3 CADASTRAL SURVEY
4 STATE PLAN COORD. SYSTEM CONV
5 TOWNSHIP-SECTION-RANGE SYS CONV
6 UTM COORDINATES CONVERSION
7 RAW PHOTO EXTRACTION
8 GPS SURVEY
9 LORAN-C NAVIGATIONAL DEVICE
472 LATITUDE/LONGITUDE DATUM DESCRIPTIONS (FLLT, PLLT)
U UNKNOWN
1 NAD27
2 NADS3
473 LATITUDE/LONGITUDE SCALE DESCRIPTIONS (FLLS, PLLS)
N NOT APPLICABLE
U UNKNOWN
1 15,840
2 20,000
3 24,000
4 25,000
5 62,500
6 63,000
7 63,350
8 63,360
9 250,000
12713793
-------
Basic Training
Permit Compliance System (PCS)
474 FACILITY LATITUDE/LONGITUDE DESCRIPTIONS
(FLLM)
01099 CENTROID OF PROCESSING AREA
02099 FRONT DOOR OF FACILITY
475 OUTFALL LATITUDE/LONGITUDE DESCRIPTIONS
(PLLM)
01099
END OF DISCHARGE POINT
800 U868 HYDROLOGIC BASIN CODE DESCRIPTIONS (Partial List)
(FHBC, PHBC)
01010002 ALLAGASH R
01010003 FISH R
01010004 CANADIAN BORDER
01010005 CANADIAN BORDER
01020001 PENOBSCOT R, W BR
01020002 PENOBSCOT R, E BR
01020003 MATTAWAMKEAG R
01020004 PISCATAQUIS R
01020005 PENOBSCOT R
01030001 KENNEBEC R
01030002 DEAD R
01030003 KENNEBEC R
01040001 ANDROSCOGGIN R
01040002 ANDROSCOGGIN R
801 USGS HYDROLOGIC REGIONS (Partial List)
(FREG,PREG)
01
02
03
04
05
06
07
08
09
10
11
12
13
14
NEW ENGLAND REGION
MID-ATLANTIC REGION
SOUTH ATLANTIC-GULF REGION
GREAT LAKES REGION
OHIO REGION
TENNESSEE REGION
UPPER MISSISSIPPI REGION
LOWER MISSISSIPPI REGION
SOURIS-RED-RAINY REGION
MISSOURI REGION
ARKANSAS-WHITE-RED REGION
TEXAS-GULF REGION
RIO GRANDE REGION
UPPER COLORADO REGION
A-O
12/13793
SDC-0055-034-ST-3003
-------
Permit Compliance System (PCS) Basic Training
802 USG8 HYDROLOGIC SOB-REGIONS (Partial List) (FSRG, PSR6)
0101 ST. JOHN
0102 PENOBSCOT
0103 KENNEBEC
0104 ANDROSCOGGIN
0105 MAINE COASTAL
0106 SACO
0107 MERRIMACK
0108 CONNECTICUT
0109 MASSACHUSETTS-RHODE ISLAND COASTAL
0110 CONNECTICUT COASTAL
0111 ST. FRANCOIS
0201 RICHELIEU
0202 UPPER HUDSON
0203 LOWER HUDSON-LONG ISLAND
0204 DELAWARE
0205 SUSQUEHANNA
803 DS68 HYDROLOGIC ACCOUNTING UNIT (Partial List) (FAUN,PAUN)
010100 ST. JOHN.
010200 PENOBSCOT.
010300 KENNEBEC.
010400 ANDROSCOGGIN.
010500 MAINE COASTAL.
010600 SACO.
010700 MERRIMACK.
010801 UPPER CONNECTICUT
010802 LOWER CONNECTICUT
010900 MASSACHUSETTS-RHODE ISLAND COASTAL.
011000 CONNECTICUT COASTAL.
011100 ST. FRANCOIS.
020100 RICHELIEU.
020200 UPPER HUDSON.
020301 LOWER HUDSON
020302 LONG ISLAND
804 USGS REACH NUMBER/SEGMENT NUMBERS/MAXIMUM MILEAGE (Partial
List) (FREA, PREA)
01010003 0010 05200
01010003 0011 11000
01010003 0012 00200
01010003 0013 00500
01010003 0014 15100
01010003 0015 00600
01010003 0016 03600
SDC-O055-034-ST-300312/13/93 X77
-------
Basic Training Permit Compliance System (PCS)
80S U868 STREAM CLASSIFICATION CODES FRSC, PRSC
A OPEN WATER REACH
B BI-DIRECTIONAL REACH
C COASTLINE
E ENTRY REACH
G GREAT LAKES SHORELINE
I ISLAND SHORELINE
L LAKE (NOT GREAT LAKE) OR RESERVOIR SHORELINE
M OPEN WATER REACH
N ISOLATED REACH
R REGULAR REACH
S SOURCE OF HEADWATERS REACH
T TERMINAL REACH
W WIDE RIVER SHORELINE
X SOURCE AND TERMINAL REACH
Z TERMINAL AND ENTRY REACH
The following code table is used with the PTRK screen:
110 PERMIT TRACKING EVENT CODES (PTEV)
P1099 APPLICATION RECEIVED
P2099 APPLICATION COMPLETE
P3099 DRAFT PERMIT/PUBLIC NOTICE
P4099 PERMIT ISSUED
P5099 PERMIT EXPIRED
P6099 PERMIT EFFECTIVE
30099 PERMIT MODIFIED
A-8 12/13/93 SDC-OQ55-034^ST-31X)3
-------
Permit
ianw* System (PCS)
Bask Training
The following code tables ate used with the PTRK screen:
175 COMPLIANCE SCHEDULE NUMBERS
(CSCH)
AA
AB
AC
AD
BI
CC
CP
DA
DB
DC
DD
DE
DF
DZ
FF
GA
HA
HC
JA
MC
MI
MP
NI
NM
PT
SL
TR
01
02
03
301 (I) (1)
301 (I) (2)
301 (H)
308 LETTER
BIOMNTRNG SCH EST BY ENF ACT
SCHED ESTBLISHED BY CCP
SCHED REQUIRING DEV OF CCP
309 (A) (5) (A) -INTERIM
309 (A) (5) (A) -FINAL
309 (A) (5) (A) -MUNICIPALS
309 (A) (5) (B)
309 (A) (6)
309 (A) (3)
ADMIN. ORDERS FOR INDUSTRIALS
FED FACILITY COMP AGREEMENT
FED. JUDICIAL DECREES
STATE JUDICIAL DECREES
STATE NON- JUDICIAL DECREES (IND & MUN) -
STATE ADMIN. DECREES
ENF SCH FOR MUN COMP STRATGY
308 REG FOR 'MUNI COMP STRATEGY
REQ ENF SCH FOR MUN COMP STRAT
NOV FOR INDUSTRIALS
NOV FOR MUNICIPALS
PRETREATMENT
SLUDGE
PRETREATMENT
EXTENDED CS
EXTENDED CS
EXTENDED CS
EXTENDED CS
EXTENDED CS
EXTENDED CS
EXTENDED CS
EXTENDED CS
EXTENDED CS
EXTENDED CS
EXTENDED CS
EXTENDED CS
EXTENDED CS
EXTENDED CS
SDC-0055-034-ST-3003
12/13/93
-------
Bask Training Permit Compliance System (PCS)
020 COMPLIANCE SCHEDULE EVENT CODES (EVNT)
00199
00299
00399
00499
00599
01799
01899
02599
03099
03599
03699
03799
03899
03999
04599
05099
05199
05599
05699
1ST REPORT OF PROGRESS
2ND REPORT OF PROGRESS
3RD REPORT OF PROGRESS
4TH REPORT OF PROGRESS
5TH REPORT OF PROGRESS
COMPLETE PLANS & SPECS
ADVERTISE FOR BIDS
FINANCING COMPLTE CONTR AWRD
BEGIN CONSTRUCTION
1ST RPT CONSTRUCTION PROGRESS
2ND RPT CONSTRUCTION PROGRESS
3RD RPT CONSTRUCTION PROGRESS
4TH RPT CONSTRUCTION PROGRESS
5TH RPT CONSTRUCTION PROGRESS
END CONSTRUCTION
BEGIN DISCHARGE
END DISCHARGE
OPERATIONAL LEVEL ATTAINED
FINAL COMPLIANCE W/EFF LIMITS
1 R
1 R
1 R
1 R
1 R
1 S
1 S
1 S
1 S
1 R
1 R
1 R
1 R
1 R
1 S
1 S
1 S
1 S
1 S
480 COMPLIANCE VIOLATION CODES (AUTO AMD MANUAL)(CVIO)
CIO REPORTED LATE VIOLATION
C20 ACHIEVED LATE VIOLATION
C30 UNACHIEVED VIOLATION
C40 NOT RECEIVED VIOLATION
MOO MANUAL COMP VIO (GENERIC)
M10 MANUAL REPORTED LATE VIOLATION
M20 MANUAL ACHIEVED LATE VIOLATION
M30 MANUAL UNACHIEVED VIOLATION
M40 MANUAL NOT RECEIVED VIOLATION
A-10 12/13/93 SDLHKJ35-UJ4-51 -JtXW
-------
Permit Compliance System (PCS) Basic Training
The following tables are used with the INSP screen:
280 INSPECTION TYPE CODES (TYPI)
A PERFORMANCE AUDIT
B COMPLIANCE BIOMONITORING
C COMPLIANCE EVAL (NON-SAMPLING)
D DIAGNOSTIC
E CORPS OF ENGINEERS INSPECTION
F PRETREATMENT FOLLOW-UP
G PRETREATMENT AUDIT
I INDUSTRIAL USER INSPECTION
L ENFORCEMENT CASE SUPPORT
P PRETREATMENT COMPL. INSPECTION
R RECONNAISSANCE
S COMPLIANCE SAMPLING
U IND. USER INSP. W/ PRET. AUDIT
X TOXICS INSPECTION
2 IU SAMPLING INSPECTION
3 IU NON-SAMPLING INSPECTION
4 IU TOXICS INSPECTION
5 IU SAMPLING INSPECTION W/PRETREATMENT
6 IU NON-SAMPLING INSPECTION W/PRETREATMENT
7 IU TOXICS W/PRETREATMENT
290 INSPECTOR CODES (INSP)
C CONTRACTOR
E CORPS OF ENGINEERS
J JOINT EPA & ST (EPA LEAD)
N NEIC
R EPA (REGIONAL)
S STATE
T JOINT EPA & ST (ST LEAD)
300 INSPECTED FACILITY TYPE CODES (FACC)
1 MUNICIPAL
2 INDUSTRIAL
3 AGRICULTURAL
4 FEDERAL
SDC-0055-034-ST-3003 12/13/93 A-ll
-------
Bask Training Permit Compliance System (PCS)
260 BIOMONITORZNG INSPECTION METHODS CODES (BIOM)
B DISCRETE ACUTE
C DISCRETE CHRONIC
D DISCRETE METHOD
F FLOW-THROUGH METHOD
G FLOW-THROUGH ACUTE
H FLOW-THROUGH CHRONIC
A-1Z 12/13/93 SDC-0055-a*4-M-JtX«
-------
Permit Compliance System (PCS) Bask Training
The following code tables are used with the PCI1 screen:
560 PROGRAM ELEMENT CHANGES (PRCH)
A LEGAL AUTHORITY
C CONTROL MECH. IMPLEMENTATION
E ENFORCEMENT PROGRAM
I INSPECTION/MONITORING PROGRAM
L LOCAL LIMITS
R RESOURCES
580 CONTROL MECHANISM DEFICIENCIES (CMDF)
A REF TO LOCAL ORD./LEGAL AUTH
C STANDARD CONDITIONS
D EFFECTIVE AND EXPIRATION DATES
I IU SELF-MONITORING REQ
L APPLICABLE DISCHARGE LIMITS
R IU REPORTING REQ
S SAMPLING LOCATION
T SAMPLE TYPE
570 DEFICIENCIES IDENTIFIED DURING IU FILE REVIEW (FIDF)
C CONTROL MECHANISMS
E ENFORCEMENT BY THE POTW
F FILE CONTENTS
I IU SELF-MONITORING
M POTW COMPLIANCE MONITORING
S SPILLS/SLUG LOADING
SDC-M55-034-ST-3003 12/13/93
-------
Basic Training Permit Compliance System (PCS)
680 ACCEPTANCE OF HASTES OTHER THAN DOMESTIC & INDUST.(WSTE)
L LANDFILL LEACHATE
N NONE
O OTHER
R RCRA/CERCLA SITE WASTES/LEACH
S HAULED SEPTA6E
670 REMOVAL CREDITS (RECR)
A APPROVED
D DENIED
N NOT APPLICABLE
P PENDING
12713793
-------
Permit Compliance System (PCS) . Basic Training
The following code tables are used with the Pretreatment screens:
660 DEFICIENCIES IN POTW SAMPLING OF IU'8 (SMDF)
C INADEQUATE CHAIN OF CUSTODY
F INADEQUATE SAMPLING FREQUENCY
P IMPROPER SAMPLING PROTOCOLS
S IMPROPER/INADEQ PARAMS SAMP
T IMPROPER SAMPLE TYPES
650 MDLTIJURISDICTIONAL AGREEMENT DEFICIENCIES (MADF)
A LACK OF OVERSIGHT AUTHORITY
I LACK OF INSPECTION AUTHORITY
N LACK OF REMEDIES FOR NON-COMPL
R POOR DELINEATION OF RESPONSIB
690 TECHNICAL EVALUATION FOR LOCAL LIMITS (EVLL)
N NO
P PARTIAL
Y YES
700 ADOPTION OF TECHNICALLY BASED LOCAL LIMITS (ADLL)
N NO
Y YES
Z NOT APPLICABLE
12713793
-------
Basic Training Permit Compliance System (PCS)
640 SLUDGE DISPOSAL METHODS (8LD6)
A LAND APPLICATION
D OCEAN DISPOSAL
I INCINERATION
L LANDFILL
O OTHER
P PUBLIC DIST/MARKETING
S SURFACE IMPOUNDMENTS
600 INADEQUACIES IN PRETREATMENT RESOURCES (RESO)
A INSUFF ACCESS TO ANALYT EQUIP
E INSUFF SAFETY EQUIPMENT
F INSUFFICIENT FUNDING
P INADEQ NUMBERS OF PERSONNEL
S INSUFF SAMPLING EQUIPMENT
T INSUFF TRAINING OF PERSONNEL
V INSUFF NUMBERS OF VEHICLES
590 LEGAL AUTHORITY DEFICIENCIES (LADF)
A APPLYING & ENFORCING PT STANDARDS
C COMPLYING W/CONFIDENTIALITY REQUIREMENTS
D DENY/CONDITION NEW/INCREASED CONTRIB
H HALTING/PREVENTING DISCHARGES
I ALLOWING IU INSPECTIONS & SAMPLING
N OBTAINING REMEDIES FOR NON-COMPLIANCE
P CONTROL IU THRU PERMIT, CONTRACT, ETC.
R REQUIRING SUBMISSION OF IU REPORTS
S REQUIRING DEV OF IU COMPLIANCE SCHED
A-16 12/13/93 &DL.-UU53-tl3*o 1-JUU3
-------
Permit Compliance System (PCS) Bask Training
630 DEFICIENCIES IN INTERP. £ APPL. OF FRET. STANDARDS
(APDF)
A FAIL TO APPLY MORE STRINGENT STANDARD
C INCORRECT CATEGORIZATION OF IUS
D IMPROPER DESIGNATION OF SAMP LOCATION
I FAIL TO IDENTIFY CIUS
L APPLIC OF INAPPROPRIATE LONG-TERM AVG
M FAIL TO USE EFFECTIVE CONTROL MECHANISM
P IMPROPER APPLIC OF PROD-BASED STANDARDS
S INADEQUATE SAMPLE TYPE AND/OR FREQUENCY
T FAIL TO APPLY APPROPRIATE TTO LIMITS
W MISUSE OF COMBINED WASTESTREAM FORMULA
620 INADEQUACY OF POTW'S INSPECTION £ SAMPLING OF IUS
(ADIN)
A FAIL TO ASSESS COMPLIANCE OF lU'S
C FAIL TO CHARACTERIZE IU POLLUTANTS
E FAIL TO PROVIDE ADMISSIBLE EVIDENCE
I FAIL TO INVESTIGATE NON-COMPLIANCE
R FAIL TO RECEIVE/REVIEW ALL IU REPORTS
610 DEFICIENCIES IN DATA MANAGEMENT & PUBLIC PARTICIP.
(DMDF)
A FAIL TO PROV PUBLIC ACCESS TO EFFL DATA
C FAIL TO HANDLE CONFIDENTIALITY
D POOR DOCUMENT OF ACTIVITY IN IU FILES
M FAIL TO MAINTAIN RECORDS FOR 3 YEARS
N FAIL TO NOTIFY RE. DEV OF LOCAL LIMITS
P FAIL TO PUB ANNUAL LIST OF SIGNIF VIOL
310 LIMIT TYPE CODES (LTYP)
I INITIAL
M INTERIM
F FINAL
SDC-0055-G34-ST-3003 12/13/93 A-I /
-------
Basic Training
Permit Compliance System (PCS)
220 TYPE OF EFFLUENT WASTE
(WAST)
01
02
03
04
05
.06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
SANITARY
NONCONTACT COOLING WATER
STORM WATER RUNOFF
PROCESS WATER
OTHER
SANI,COOLING
SANI,COOLING,RUNOFF
SANI,COOLING,RUNOFF,PROCESS
SANI,COOLNG,RUNOFF,PROC,OTH
SANI,RUNOFF
SANI,RUNOFF,PROCESS
SANI,RUNOFF,PROCESS,OTHER
SANI,PROCESS
SANI,PROCESS,OTHER
SANI,OTHER
COOLING,RUNOFF
COOLING,RUNOFF,PROCESS
COOLING,RUNOFF,PROCESS,OTH
COOLING,PROCESS
COOLING,PROCESS,OTHER
COOLING,OTHER
RUNOFF,PROCESS
RUNOFF,PROCESS,OTHER
RUNOFF,OTHER
PROC,OTHER
SANI,COOLING,PROCESS
SANI,COOLING,OTHER
SANI,COOLING,PROCESS,OTHER
SANI,RUNOFF,OTHER
COOLING,RUNOFF,OTHER
SANI,COOLING,RUNOFF,OTHER
CONTACT COOLING WATER
CONT COOL WATER/PROC/COOLING
GROUND WATER TREATMENT
MINE PIT DEWATERING
CONTACT & NON-CONTACT COOL WTR
12/13/93
SDC-Q055-034-& 1-3U03
-------
Permit Compliance System (PCS) Bask Training
190 TREATMENT TYPES (TRET)
IT SCREENING
2F DISINFECTION (CHLORINE)
3A ACTIVATED SLUDGE
4A DISCHARGE TO SURFACE WATER
5A AEROBIC DIGESTION
5D CENTRIFUGATION
5L GRAVITY THICKENING
5Q LANDFILL
iDC-W33-UJ4-iT-3(W3 12/13/93
-------
Bask Training Permit Cognpiiang* System (PCS)
The following code tables are used with the LJMS screen:
080 MONITORING LOCATION COOES (MLOC)
G RAW SEW/INFLUENT
K PERCENT REMOVAL
1 EFFLUENT GROSS VALUE
5 UPSTREAM MONITORING
6 DOWNSTREAM MONITOR
120 STATISTICAL BASE CODES (STAT)
AF AVERAGE AVERAGE
DB DAILY AVDAILY AVERAGE
MB MAXIMUM MAXIMUM
ME MINIMUM MINIMUM
MK MO AVG MONTHLY AVERAGE
MN MO MAX MONTHLY MAXIMUM
MO MO MIN MONTHLY MINIMUM
WA WKLY AVGWEEKLY AVERAGE
3C 30DA AVG30 DAY AVERAGE
7A 7 DA AVG7 DAY AVERAGE
NOTE: An 'A' in the third column indicates that this is the monthly average for RNC
processing.
A-20 12/13/93 SDC-0055-034-ST-3003
-------
Pirmif Complin"*1*' System (PCS) Basic Training
The following code tables are used with the LIMS screens:
130 STANDARDS BASIS CODES (STBA)
A EFFLUENT GUIDELINES
B NON DEGRADATION STNDS
1 WQS
2 BCT
3 BAT
4 BPWTT
5 BPT
6 STS
7 NSPS
8 BMP
9 TES
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
SDC-0055434-ST-3U03 I27I3753
-------
Base Training Permit Compliance System (PCS)
ISO SAMPLE TYPES (SAMP)
CP
FI
GR
G2
G3
G4
G5
IM
IN
IS
IT
MC
MP
MS
RC
TM
VI
01
12
16
COMPOS
FLOIND
GRAB
GRAB-2
GRAB-3
GRAB-4
GRAB-5
IMERSN
INSTAN
INSITU
IMRSTB
MATHCL
MATHCP
MEASRD
RCORDR
TOTALZ
VISUAL
COMP-1
COMP12
COMP16
450 CONTESTED PARAMETER CODES (CONP)
X CONTESTED-STILL PRINTED ON DMR
Y CONTESTED-NOT PRINTED ON DMR
180 UNIT CODES (LQUC)
03 MGD ]MGD ] MILLION GALLONS PER DAY
12 SU ]SU ]STANDARD UNITS (I.E. PH)
15 DEG.F ]DEG.F ]DEGREES FAHRENHEIT
19 MG/L ]MG/L ]MILLIGRAMS PER LITER
26 LBS/DY]LBS/DAY-]POUNDS PER DAY
-------
Permit Compliance System (PCS) _ Basic Training
The following code tables are used with the EVIO screen:
210 VIOLATION CODES (EFFLUENT) (MVIO)
D10 DMR OVERDUE (EPA)
D20 DMR OVERDUE (STATE)
D30 DMR OVERDUE (EPA/ST)
EOO MEASUREMENT ONLY, NO VIOLATION
E01 MONITOR ONLY, QUANTITY ABSENT
Ell MONITOR ONLY, CONC ABSENT
E21 MONITOR ONLY, QTY/CONC ABSENT
E31 LIMITED, QUANTITY ABSENT
E41 LIMITED, CONCENTRATION ABSENT
E51 LIMITED, QTY/CONC ABSENT
E90 NUMERIC VIOLATION
490 NO DATA 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
Q OTHER
9 MONITORING IS CONDITIONAL/NOT REQ THIS MP
SDC-0055-034-ST-3(X)3 12/13/93
-------
Training
Permit Compliance System (PCS)
The following code tables are used with the SVIO screen:
550 SINGLE EVENT VIOLATION CODES (8VCD)
01099
02099
03099
04099
05099
06099
07099
08099
09099
10099
11099
12099
13099
14099
15099
16099
17099
18099
19099
20099
NON-COMPLIANCE NOTICE
DISCHARGE WITHOUT A VALID PERMIT
IMPROPER OPERATION AND MAINTENANCE
UNAUTHORIZED BY-PASS
FAILURE TO MEET 77-07-01
SECTION 404 VIOLATION
FAILURE TO MEET SECTION 308 REQUEST
FAILURE TO APPLY FOR A PERMIT
DMR QA
BASELINE MONITORING REPORT VIOLATION
MARINE PROTECTN & SANCTUARY ACT VIOL
VIOLATION DETECTED DURING INSPECTION
FAILURE TO ISSUE SIU PERMITS
FAILURE TO CONDUCT INSPECTIONS
FAILURE TO ESTABLISH SELF-MONITORING REQ
FAILURE TO DEVELOP/ENFORCE PRET STDS.
FAIL TO ENFORCE AGAINST PASS-THRU/INTF.
APPROVAL AUTHORITY VIOL. OF CONCERN
MONITOR FOR TOXICITY REQUIREMENT
SLUDGE VIOLATION
-------
Permit Compliance System (PCS) Basic Training
The following code tables are used with the ENAC screen:
030 ENFORCEMENT ACTION COOES (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
040 ENFORCEMENT ACTION STATUS CODES (ENST)
AE ADMINISTRATIVE EXTENSION
AR ADMINISTRATIVELY RESOLVED
CL CLOSED - BACK INTO COMPLIANCE
CO COMPLIANCE
CS CLOSED SUPERCEEDED BY EA
NC NONCOMPLIANCE
PR PERMIT REVISION
RE RESOLVED
SDC-U055-Q34-ST-3003 12/13/93
-------
Basic Training
Permit Compliance System (PCS)
340 ENFORCEMENT ACTION VIOLATION TYPES
(EVTF)
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
.Nl ALL NON-RPT VIOS FOR PERMIT (EPA)
N2 ALL NON-RPT VIOS FOR PERMIT (STATE)
N3 ALL NON-RPT VIOS FOR PERMIT
N4 NON-RPT VIOS FOR MONIT PER OR PIPE
N5 NON-RPT VIOS FOR MONIT PER OR PIPE
N6 NON-RPT VIOS FOR MONIT PER OR PIPE
N7 SPECIFIC NON-RPT VIOLATION (EPA)
N8 SPECIFIC NON-RPT VIOLATION (STATE)
N9 SPECIFIC NON-RPT VIOLATION
SI ALL SINGLE EVENT VIOS FOR PERM
S2 SPECIFIC SINGLE EVENT VIOL
(DIG
(D20
(D30
(EPA)
(DIG
(ST)
(D20
(D30
(DIG
(D20
(D30
VIOLATIONS)
VIOLATIONS)
VIOLATIONS)
VIOLATIONS)
VIOLATIONS)
VIOLATIONS)
VIOLATIONS)
VIOLATIONS)
VIOLATIONS)
12/13/93
-------
Permit Compliance System (PCS)
Training
The following tables are used with various screens:
195 RNC DETECTION CODES Effluent (SNCE)
Compliance Schedule (SNCC)
Single Event (SNCS)
A
B
C
D
E
F
G
I
J
N
Q
S
T
V
W
X
Y
Z
390
A
B
W
1
2
3
4
5
6
7
8
9
ENF-ADMINISTRATIVE ORDE
DIS-MANUAL 2A4 - PASS-THROUGH
CHR-CHRONIC VIOLATION
DIS-MANUAL OTHER
DIS-MANUAL 2F - PRMT NARRATIVE
DIS-MANUAL 2G - VIO OF CONCERN
DIS-MANUAL 2A1 - EFFLUENT VIOL
DIS-MANUAL 2A2 - UNAUTH BYPASS
DIS-MANUAL 2A3 - UNAUTH DISCH
RPT-NONRECEIPT OF DMR/CS RPT
DIS-MANUAL 2B - PRETREATMENT
SCH-COMPLIANCE SCHEDULE VIOL
TRC-TRC LIMITATIONS EXCEEDED
EFF-OTHER VIOLATION WITH TRC
DIS-MANUAL 2E - DEFICIENT RPT
EFF-MANUAL OTHER VIOL W/ TRC
TRC-MANUAL TRC
CHR-MANUAL CHRONIC
RNC RESOLUTION CODES Effluent
Compliance Schedule
Single Event
NC-MANUAL UNRESOLVED RNC
RE-MANUAL BY EPA ACTION
NC-WAITING RNC RESOLUTION
NC-UNRESOLVED RNC
RE-BACK INTO COMPLIANCE
RP-DUE TO FORMAL EA
RP-IN COMPLIANCE LAST QTR
RE-RESOLVED RP BY EA W/ CL
RE-MANUAL RES BY EA W/ CL
RP-MANUAL RP-IN COMP W/ADM -LMT
RP-MANUAL DUE TO FORMAL EA
RE-MANUAL BY BACK INTO COMPL
(SRCE)
(SRCC)
(SRCS)
T27T379T
-------
Permit Compliance System (PCS) Basic Training
Appendix B
City Master File
-------
:nnit Compliance System (PCS)
Basic Training
12500001 LEHISTON
**
12600001 LEHISTON ORCHARDS
**
) 5000000 LEWISVILLE
**
35300000 LINCOLN
**
35500000 LINCOLN COUNTY
**
37500000 LORENZO
**
40000000 LOWMAN
**
42500000 LUCILE
**
45000000 LUND
**
CITY MASTER FILE SAMPLE
069 NEZ PERCE 01 12,691
069 NEZ FERCE 01 9,680
051 JEFFERSON 02 385
019 BONNEVILLE 02
063 LINCOLN 02 3,686
051 JEFFERSON 02 200
015 BOISE 01 100
049 IDAHO 01 20
029 CARIBOU 02 10
26,068 55 13 08 462442 *]
1170112 *]
X 44 13 08 462236 *]
1165748 *]
468 10 13 06 434200 *]
1120042 *]
300 13 06 433042 C]
1115748 C]
3,057 33 13 06 425900 )
1140800 ]
100 10 13 06 434342 *)
1115224 *]
is 1 0 13 07 440454 *)
1153700 *]
30 1 0 13 08 453212 *]
1161812 *]
X 10 13 06 423830 *]
1115318 *)
SDC-0055-034-ST-3003
12/13/93
B-l
-------
Permit Compliance System(PCS) Basic Training
Appendix C
Storet Table Examples
-------
Permit Compliance System (PCS)
Basic Training
DUN DATE: 03/05/93
BUN TIME: 14:41:23.5
PROG ID: PCRHQPRA
STORE!
CODE STAND ACCEPT STAND ACCEPT
U.S. ENVIRONMENTAL PROTECTION AGENCY
OFFICE OF UATER ENFORCEMENT
PERMIT COMPLIANCE SYSTEM DBMS
EFFLUENT LIMITS
PARAMETER CODES TABLE
SORTED BY DESCRIPTION
PAGES: 39/40/41
PARAMETER DESCRIPTION
LIMIT MOT USUALLY COOED FOR:
QTY OTY CONC CONC CONC
AVG MAX MIN AVG MAX
00310
01
00311 01
81010
47024 49
00140 42
70026
00698
2P
01
01020 01
78463
82057
52
26
35
50
51
59
71
76
1U
2J
26
35
50
51
59
71
76
1U
2J
47
44
45
26
35
50
51
71
76
1W
2J
26
35
40
50
51
71
76
1U
2J
66
19
19
23
19
19
19
69
20
21
22
28
32
36
37
90
20
21
22
28
32
36
37
20
21
22
28
32
37
20
21
22
28
32
36
37
20
21
22
28
32
36
37
20
21
BOD, 5-DAY
(20 DEC. C)
TOXIC
STORET 129
CLASS LIST
10
BOD, 5-DAY DISSOLVED
10
BOO, 5-DAY PERCENT REMOVAL
BOD, 5-DAY 20 DEC C PER CFS OF STREAMFLW
BOD, 5-DAYC20 DEG.OPER PRODUCTION
BOD, 5-DAY, TOTAL
BORIC ACID
15
10
10
10
07
BORON, DISSOLVED
(AS B)
08
BORON, SLUDGE, TOTAL DRY WEIGHT (AS B)
BORON, TOTAL
08
08
12/1303
-------
Basic Training
Permit Compliance System (PCS)
RUN DATE: 03/05/93
RUN TIKE: 14:41:23.5
PROG ID: PCRHQPRA
U.S. ENVIRONMENTAL PROTECTION AGENCY
OFFICE OF WATER ENFORCEMENT
PERMIT COMPLIANCE SYSTEM DBMS
EFFLUENT LIMITS
PARAMETER CODES TABLE
SORTED BY DESCRIPTION
PAGES: 4W2
STORET
CODE
01022
00999
30311
82198
71870
71872
STAND ACCEPT
01 26
35
40
50
51
7J
76
1U
2J
01 26
35
40
50
51
71
76
1U
2J
01 26
35
40
50
51
71
76
1U
2J
01 26
35
40
50
51
71
76
1V
2J
01 26
35
40
50
51
71
76
It*
STAND ACCEPT PARAMETER DESCRIPTION
19 20 BORON, TOTAL
-------
Permit Compliance System (PCS) Basic Training
Appendix D
Acronym Reference List
-------
Permit Compliance System (PCS)
Basic Training
Acronm
Acronym Reference List
Permit Facility Data
Field Length
NPID*! PERMIT #
FNML* FACILITY NAME LONG
FNMB FACILITY NAME SHORT
OFFL COGNIZANT OFFICIAL
TELE TELEPHONE
CITY* CITY CODE
CNTY* COUNTY CODE
8IC2* SIC CODE
CODE OF FEDERAL REGULATIONS
TYPA TYPE OF APPLICATION
TYPO* FACILITY OWNERSHIP
ORID ORIGINAL PERMIT ISSUANCE DATE
EPST* ISSUED BY
REIS REISSUANCE #
PRET* PRETREATMENT PROGRAM REQUIRED INDICATOR
FDGR* FEDERAL GRANT INDICATOR
NEW SOURCE/DISCHARGE CODE
NEW SOURCE/DISCHARGE DATE
FLIM* FINAL LIMITS INDICATOR
WQUA WATER QUALITY LIMITS
IACC* FACILITY INACTIVE CODE
IADT* FACILITY INACTIVE DATE
CSDN CONSOLIDATED PERMIT #
CSID CONSOLIDATED SYSTEM FACILITY IDENTIFIER
NEED NEEDS SUFFIX
STNO STATE PERMIT #
FFID FEDERAL PERMIT #
CAID CONTROL AUTHORITY PERMIT #
RPID RECEIVING POTW PERMIT #
RPRI REGIONAL PRIORITY PERMIT
SUBR SUB-REGION CODE
ATNY ATTORNEY INITIALS
ENGI ENGINEER INITIALS
FLOW* VERAGE DESIGN FLOW
ARCH ARCHIVAL INDICATOR
BAS6 RIVER BASIN CODE
RWAT RECEIVING WATERS
FLAT* LATITUDE
FLON* LONGITUDE
FLLC* LAT/LONG CODE OF ACCURACY
FLLM* LAT/LONG METHOD
009
120
030
030
010
005
003
004
003
002
003
006
001
001
001
001
002
006
001
002
001
006
012
015
003
008
012
009
009
001
002
003
003
005
001
010
035
008
009
001
001
SDC-0055-034-ST-3003
12/13793
D-l
-------
Basic Training Permit Compliance System (PCS)
Acronym "p-iaia ^»*»a Field Length
FLLT* LAT/LONG DATUM 001
PLLS* LAT/LONG SCALE 001
FLLD* LAT/LONG DESCRIPTION 005
PKBC* U8GS BYDROLOGIC BASIN CODE 008
FSEG FACILITY STREAM SEGMENT 004
FMLG FACILITY MILEAGE;INDICATOR 005
FR8C FACILITY RECEIVING BTREAM CLASSIFICATION CODE 002
EHIN HEARING INDICATOR 001
FILE # 012
ISSUE CODES 003
ISSUE CODES 003
ISSUE CODES 003
DOCKET # 012
RDF1 REGIONAL DATA FIELD #1 001
RFD2 REGIONAL DATA FIELD #2 001
RFD3 REGIONAL DATA FIELD #3 001
RFD4 REGIONAL DATA FIELD #4 003
RFD5 REGIONAL DATA FIELD #5 003
RFD6 REGIONAL DATA FIELD #6 003
RFD7 REGIONAL DATA FIELD #7 006
RFD8 REGIONAL DATA FIELD #8 006
RFD9 REGIONAL DATA FIELD #9 006
RFD10 REGIONAL DATA FIELD #10 050
NP8C* NPSC-NMP STAT 001
NPFF* NPFF-NMP FIT 001
NP8Q* NPBQ-NMP QTR 001
PYMS PREVIOUS YEAR MANUAL QNCR STATUS 004
PYM1 October through December
PYM2 January through March
PYM3 April through June
PYM4 July through September
CYMS* CURRENT YEAR MANUAL QNCR STATUS 001
CYM1 October through December
CYM2 January through March
CYM3 April through June
CYM4 July through September.
MNAM FACILITY NAME 030
MST1 ADDRESS LINE1 030
MST2 ADDRESS LINE2 030
MCTY CITY 023
MSTT STATE 002
MZIP ZIP 009
ANAM FACILITY NAME 030
AST1 ADDRESS LINE1 030
AST2 ADDRESS LINE2 030
ACTY CITY 023
ASTT STATE 002
AZIP ZIP 009
RNAM FACILITY NAME 030
D-Z 12/13/93 SDC-0055-034-5T-3003
-------
Permit Compliance System (PCS) Basic Training
Acronym yftoid M»I^« Field Length
R8T1 ADDRESS LIHE1 030
R8T2 ADDRESS LIHE2 030
RCTY CITY 023
RSTT STATE 002
RZZP ZIP 009
RTEL TELEPHONE 010
ONAM FACILITY NAME 030
OST1 ADDRESS LIHE1 030
OST2 ADDRESS LINE2 030
OCTY CITY 023
OSTT STATE 002
OZIP ZIP 009
OTEL TELEPHONE 010
ENAM 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 yi^id u»m«* 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-0055-034-ST-3003 12/13/93
-------
Basic Training
Permit Compliance System (PCS)
Acronym
Field Name
Field Length
Compliance Schedule Family
CSCH*! COMPLIANCE SCHEDULE NUMBER
DSCD*I DATA SOURCE CODE
EVNT*! COMPLIANCE SCHEDULE EVENT CODE
DTSC* COMPLIANCE SCHEDULE EVENT SCHEDULED DATE
DTAC* COMPLIANCE SCHEDULE EVENT ACTUAL DATE
DTRC* COMPLIANCE REPORT RECEIVED DATE
COMM COMPLIANCE COMMENT
CSFN* DOCKET NUMBER
USER DATA ELEMENT #1
USER DATA ELEMENT #2
CVTO! COMPLIANCE SCHEDULE 'VIOLATION CODE'
CVDT1 COMPLIANCE SCHEDULE 'VIOLATION DATE'
VCSN! COMPLIANCE VIOLATION NUMBER
CVEVI COMPLIANCE VIOLATION EVENT CODE
VDCD! COMPLIANCE VIOLATION DATA SOURCE CODE
002
004
005
006
006
006
030
008
003
006
003
006
002
005
004
D-4
12/13/93
SDC-Q055-U34-3 1
-------
Permit Compliance System (PCS) Basic Training
Acronym f**ia Kama Field Length
Inspection Scheduling Data Type
STYP! SCHEDULED INSPECTION TYPE 001
SINS I SCHEDULED INSPECTOR CODE 001
SIDT! SCHEDULED INSPECTION DATE 006
SIQR! SCHEDULED INSPECTION QTR/YEAR 003
8DTI ACHIEVED INSPECTION DATE 006
I8C1 INSPECTION SCHEDULING COMMENTS field 1 030
I8C2 INSPECTION SCHEDULING COMMENTS field 2 030
ISC3 INSPECTION SCHEDULING COMMENTS field 3 030
RTYP REVISED SCHEDULED INSPECTION TYPE 001
RIN8 REVISED SCHEDULED INSPECTOR CODE 001
RIDT REVISED SCHEDULED DATE 006
RIQR REVISED SCHEDULED QTR/YEAR 003
Acronym vie*\a v«m«* Field Length
Inspection Data Type
DTIN! INSPECTION DATE 006
TYPI! INSPECTION TYPE 001
INSP* INSPECTOR CODE 001
FACC INSPECTED FACILITY TYPE 001
BIOM BIOMONITORING INSPECTION METHOD 001
QABI QA-DATA BASED INSPECTION 001
ICOM INSPECTION COMMENT 050
IC25 INSPECTION COMMENT (first 25 characters)
TOTAL HOURS (PRE/INSP/POST) 003
PRHR INSPECTION PRE_PROCESSING HOURS
INHR INSPECTION IN-PROCESSING HOURS
POHR 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
SDCHX)55-034-ST-3(XB 12/13/93 D-5
-------
Basic Training
Permit Compliance System (PCS)
Acronym
Field Length
Pretreatmant Compliance Inspection Data Type
DTZA!
8IU8*
CIUS*
NOIN*
NOCK*
P8NC*
MSNC*
SNIN*
COOR
PRCH
NOPT
8NP8
RSNC
ERGG
SUPP
CMDP
FIDF
DTIA1
WSTE
RECR
RCRD
RSCH
VSCH
DSSM
PIRT
SMDF
MADF
PTJU
RDN1
RDN2
DATE OF PRETREATMENT COMPLIANCE INSPECTION 006
NUMBER OF SIGNIFICANT INDUSTRIAL USERS 004
NUMBER OF CATEGORICAL INDUSTRIAL USERS 004
8IU8 NOT INSPECTED OR SAMPLED 003
8IUS WITHOUT CONTROL MECHANISMS 003
8IU8 IN SNC WITH STANDARDS OR REPORTING 003
8IU8 IN SNC WITH SELF-MONITORING 003
8IUS IN SNC W/ 8ELF-MON. t NOT INSP. OR SAMPLED 003
PRETREATMENT COORDINATOR NAME 025
PROGRAM ELEMENT CHANGES 006
% OF 8IU8 WHICH HAVE NOT INST. REQ. PRETREATMENT 003
8IUS IN SNC WITH: PRETREATMENT STANDARDS 003
8IUS IN SNC WITH: REPORTING REQUIREMENTS 003
ENFORCEMENT RESPONSE GUIDE 001
DOES PCI SUPPORT MOST RECENT PRET. SUMMARY REPORT 001
CONTROL MECHANISM DEFICIENCIES 008
DEFICIENCIES NOTED IN ID FILE REVIEW 006
DATE OF PRETREATMENT COMPLIANCE INSPECTION 006
ACCEPTANCE OF OTHER WASTE 006
REMOVAL CREDITS 001
REMOVAL CREDITS APPROVAL DATE 005
RESPONSE TO SCHEDULE FOR REMEDIAL MEASURES 001
VIOLATION TO SCHEDULE FOR REMEDIAL MEASURES 001
PROGRAM MOD. TO ADDRESS: DOMESTIC SEWAGE STUDY 001
PROGRAM MODIFICATION TO ADDRESS: PIRT AMENDMENTS 001
DEFICIENCIES IN POTW SAMPLING OF INDUSTRIAL USERS 005
MULTI-JURISDICTIONAL AGREEMENT DEFICIENCIES 004
JURISDICTIONS COVERED BY PRETREATMENT PROGRAM 002
REGIONAL AFIELD 1 003
REGIONAL FIELD 2 006
13713753
-------
Permit Compliance System (PCS) Basic Training
Acronym p**id v«m^ Field Length
Pretreatment Audit Inspection Data Type
DTIA! DATE OF PRETREATMENT COMPLIANCE INSPECTION 006
PTIM* DATE PERMIT MOD. TO REQUIRE PRET. IMPLEMENTATION 006
NOCM* SIUS WITHOUT CONTROL MECHANISM 003
BIDS* NUMBER OF SIGNIFICANT IUS 005
CIUS* NUMBER OF CATEGORICAL IUS 005
EVLL* TECHNICAL EVALUATION FOR LOCAL LIMITS 001
ADLL* ADOPTION OF TECHNICALLY-BASED LOCAL LIMITS 001
NOIN* SIUS 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. « NOT INSP. OR SAMPLED 003
COOR PRETREATMENT COORDINATOR NAME 025
SLDG SLUDGE DISPOSAL METHODS 006
MZPN 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
TXEF 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 IU FILE REVIEW 006
CMDF CONTROL MECHANISM DEFICIENCIES 008
LADF LEGAL AUTHORITY DEFICIENCIES 009
APDF DEFICIENCIES IN INTERPRETATION/APPLICATION OF STDS 010
ADIN INADEQUACY IN POTW'S INSPECTION fi SAMPLING OF ID'S 004
DTIA! DATE OF PRETREATMENT COMPLIANCE INSPECTION 006
DMDF DEFICIENCIES IN DATA MGMT. 6 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
NINF # OF SIUS NOT SAMPLED OR INSPECTED AT REQ. FREQ. 003
EVCL TECHNICAL EVAL. FOR COMPREHENSIVE LOCAL LIMITS 001
SDC-0055-Q34-ST-3003 12/13/93 D-7
-------
Basic Training Permit Compliance System (PCS)
Acronym g-»«»i«i v«ni«» Field Length
NOPT % OF BIDS WHICH HAVE NOT INSTALLED REQ. FRET. 003
PRCH PROGRAM ELEMENT CHANGES 006
SUPP SUMMARY REPORT 001
RDN1 REGIONAL FIELD 1 003
RDN2 REGIONAL FIELD 2 006
D-8 12/13/93 SDC-0055-034-iI-3WB
-------
Permit Compliance System (PCS) Basic Training
Acronym V*»IA v»*\» Field Length
Pipe Schedule Data Type
D8CH*! DISCHARGE NUMBER 003
DRZD*! REPORT DESIGNATOR 001
D8DG! COMBINED DISCHARGE NUMBER AND DESIGNATOR 004
PIPQ! PIPE SET QUALIFIER
STRP* INITIAL REPORT DATE 006
REUN* REPORT UNITS 001
NRPU* NUMBER OF UNITS IN REPORT PERIOD 003
NORP TOTAL NUMBER OF REPORTS DUE 003
8TSU* 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 OF UNITS IN STATE SUBMISSION PERIOD 002
PIPE PIPE DESCRIPTION 025
ALLP* SEASONAL DMR PRINTING INDICATORS 012
ZLSD* INITIAL LIMITS DATES: START 006
ILED* INITIAL LIMITS DATES: END 006
MLSD* INTERIM LIMITS DATES: START 006
MLED* INTERIM LIMITS DATES: END 006
FLSD* FINAL LIMITS DATES: START 006
FLED* FINAL LIMITS DATES: END 006
WAST TYPE EFFLUENT WASTE 002
AGYR AGENCY REVIEWER 005
MDML MIN # OF DMR LINES 002
PLAT* PIPE: LATITUDE 008
PLON* PIPE: LONGITUDE 008
PLLC* LAT/LONG ACCURACY 001
PLLM* LAT/LONG METHOD 001
PLON* PIPE: LONGITUDE 008
PLLT* LAT/LONG DATUM 001
PLLS* LAT/LONG SCALE 001
PLLD* LAT/LONG DESCRIPTION 005
PHBC PIPE SCHEDULE USGS HYDROLOGIC BASIN CODE 008
PSEG PIPE SCHEDULE STREAM SEGMENT 004
PMLG PIPE SCHEDULE MILEAGE INDICATOR 005
PRSC PIPE SCHEDULE RECEIVING STREAM CLASSIFICATION CODE 002
PIAC PIPE INACTIVE CODE 001
PIDT PIPE INACTIVE DATE 006
DRID*! REPORT DESIGNATOR 001
TRET OUTFALL TREATMENT TYPE CODES 024
PICM DMR FORM COMMENTS 030
RDP1 USER DATA ELEMENT #1 003
RDP2 USER DATA ELEMENT #2 003
5DC-0055-034-ST-3003 12/13/93 L)-y
-------
Bask Training
Permit Compliance System (PCS)
Acronym
Field Name
Field Length
parameter Limits Data Type
PLDS*!
PLRD*!
PDSG!
LIPQ!
LTYP*!
PRAM*!
MLOC*!
SEAN*!
STBA
FRAN
SAMP
CONP*
ALLS
LQUC*
LQAV*
LQMX*
LCUC*
LCKN*
LCAV*
LCMX*
PLFN*
DMR1
DMR2
DMR3
PLDS*!
PLRD*!
LTYP*!
PRAM*!
MLOC*!
SEAN*!
MODN!*
ELSD
ELED
STBA
COLS*
FRAN
SAMP
CONP*
ALLS
LQUC*
LQAV*
LQAS*
LQZS*
LQMZ*
DISCHARGE NUMBER
REPORT DESIGNATOR
COMBINED DISCHARGE NUMBER AND DESIGNATOR
PIPE SET QUALIFIER
LIMIT TYPE
PARAMETER
MONITORING LOCATION
SEASON
STANDARD BASIS CODE
FREQUENCY OF ANALYSIS
SAMPLE TYPE
CONTESTED PARAMETER
SEASONAL DMR PRINTING INDICATORS
QUANTITY LIMITS: UNIT CODE
QUANTITY LIMITS: AVERAGE
QUANTITY LIMITS: MAXIMUM
CONCENTRATION LIMITS: UNIT CODE
CONCENTRATION LIMITS: MINIMUM
CONCENTRATION LIMITS: AVERAGE
CONCENTRATION LIMITS: MAXIMUM
DOCKET NUMBER
USER DATA ELEMENT #1
USER DATA ELEMENT #2
USER DATA ELEMENT #3
DISCHARGE NUMBER
REPORT DESIGNATOR
LIMIT TYPE
PARAMETER
MONITORING LOCATION
SEASON
MODIFICATION NUMBER
MODIFICATION PERIOD: START
MODIFICATION PERIOD: END
STANDARD BASIS CODE
CHANGE OF LIMITS STATUS
FREQUENCY OF ANALYSIS
SAMPLE TYPE
CONTESTED PARAMETER
SEASONAL DMR PRINTING INDICATORS
QUANTITY LIMITS: UNIT CODE
QUANTITY LIMITS: AVERAGE
QUANTITY LIMITS: AVERAGE STAT BASE CODE
QUANTITY LIMITS: MAXIMUM STAT BASE CODE
QUANTITY LIMITS: MAXIMUM
003
001
004
004
005
001
001
001
005
002
001
012
002
008
008
002
008
008
008
012
001
006
006
003
001
001
005
001
001
001
006
006
001
002
f* f* f
005
002
001
012
002
008
002
002
008
D-IO
12/13/93
SDC-O055-034-:S 1 -
-------
Permit Compliance System (PCS) Basic Training
Acronym g-iniii v»mm Field Length
LCUC* CONCENTRATION LIMITS: UNIT CODE 002
LCMN* CONCENTRATION LIMITS: MINIMUM 008
LCMS* 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
LCZS* CONCENTRATION LIMITS: MAXIMUM STAT BASE CODE 002
LCMO* CONCENTRATION LIMITS: MINIMUM OVERRIDE 001
LCAO* CONCENTRATION LIMITS: AVERAGE OVERRIDE 001
PLFN* DOCKET NUMBER 012
DMR1 USER DATA ELEMENT #1 001
DMR2 USER DATA ELEMENT #2 006
DMR3 USER DATA ELEMENT #3 006
SDC-0055-034-ST-3003 12713793
-------
Basic Training
Permit Compliance System (PCS)
Acronym
Field Length
Measurement violation Data Type
MVDT*! MONITORING PERIOD END DATE
VDSC*! DISCHARGE NUMBER
VDRD*! REPORT DESIGNATOR
VDSGI COMBINED DISCHARGE NUMBER AND DESIGNATOR
VPRM PARAMETER CODE
VLMO MONITORING LOCATION
VMOD! MEASUREMENT VIOLATION MODIFICATION NUMBER
VLIM! MEASUREMENT VIOLATION LIMIT TYPE
V8EA! MEASUREMENT VIOLATION SEASONAL NUMBER
VIPQ! PIPE SET QUALIFIER
MVIO! MEASUREMENT VIOLATION CODE
MQAV* MEASUREMENTS: QUANTITY: AVERAGE
MQMX* MEASUREMENTS: QUANTITY: MAXIMUM
MCMN* MEASUREMENTS: CONCENTRATION: MINIMUM
MCAV* MEASUREMENTS: CONCENTRATION: AVERAGE
MCMZ* MEASUREMENTS: CONCENTRATION: MAXIMUM
DMRR DMR RECEIVED DATE
SNCE RNC DETECTION: CODE
SDNE RNC DETECTION: DATE
6RCE 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
006
003
001
004
005
001
008
008
008
008
008
006
001
006
001
006
002
005
002
002
002
001
Acronym
Field Name
Field Length
Reissuance Processing
RCIN*! REISSUANCE CODE
ILSD* INITIAL LIMITS START DATE:
ILED* INITIAL LIMITS END DATE: ~
MLSD* INTERIM LIMITS START DATE:
MLED* INTERIM LIMITS END DATE:
FLSD* FINAL LIMITS START DATE:
FLED* FINAL LIMITS END DATE:
001
006
006
006
006
006
006
D-1Z
12/13/93
SDC-0055-034-& 1 -JUUJ
-------
Permit Compliance System (PCS)
Basic Training
Acronym
Field
Field Length
Single Event Violation Data Type
8VCD! VIOLATION CODE
SVDT! VIOLATION DATE
SNC8 RNC DETECTION CODE
SNDS RNC RESOLUTION DATE
SRCS RNC RESOLUTION CODE
SRDS RNC RESOLUTION DATE
RDS1 REGIONAL FIELD 1
RDS2 REGIONAL FIELD 2
005
006
001
006
001
006
003
005
SDC-W55-034-ST-3CXW
12/13/93
D-13
-------
Basic Training
Permit Compliance System (PCS)
Acronym
Pield Mama
Field Length
Enforcement Action Data Type
ENAC*! ENFORCEMENT ACTION CODE
EATP! ISSUED BY
ENDT*! DATE
ENST* STATUS CODE
ESDT* STATUS DATE
ERFN* DOCKET NUMBER
ENST* ENFORCEMENT ACTION STATUS CODE
EACD CLOSURE SCHEDULE DATE
EIPI INITIATING PARTY 1
EIP2 INITIATING PARTY 2
ERDT RESPONSE DUE DATE
EADR RESPONSE ACHIEVED DATE
EVDK VIOLATION RECOGNITION DATE
RDH1 USER DATA ELEMENT: #1
RDH2 USER DATA ELEMENT: #2
ECMT* ENFORCEMENT ACTION COMMENT
ECM1 ENFORCEMENT ACTION COMMENT # 1
ECM2 ENFORCEMENT ACTION COMMENT # 2
ECM3 ENFORCEMENT ACTION COMMENT # 3
ECM4 ENFORCEMENT ACTION COMMENT # 4
ECM5 ENFORCEMENT ACTION COMMENT # 5
ECM6 ENFORCEMENT ACTION COMMENT # 6
ECM7 ENFORCEMENT ACTION COMMENT # 7
ECM8 ENFORCEMENT ACTION COMMENT # 8
ECM9 ENFORCEMENT ACTION COMMENT # 9
ECHO ENFORCEMENT ACTION COMMENT # 0
EKAC*! ENFORCEMENT ACTION CODE
EKTP! TYPE ORDER ISSUED
EKDT! ENFORCEMENT ACTION DATE
EVTP*! VIOLATION TYPE
1st
2nd
3rd
4th
5th
6th
7th
8th
9th
10th
002
002
006
002
006
010
005
005
005
006
006
006
003
005
300
030
030
030
030
030
030
030
030
030
030
001
001
006
002
D-14
12/13/93
-JUtu
-------
Permit Compliance System (PCS) Basic Training
Appendix £
Error Handling Helps/Hints
Class Notes
-------
Permit Compliance System (PCS) Basic Training
Error Handling Helps/Hints class Notes
SDC-W55-034-ST-300312/13/93 E-l
-------
Permit Compliance System (PCS) Basic Training
Appendix F
Training Documentation
Comment Form
-------
Permit Compliance System (PCS) Basic Training
-------
Basic Training Permit Compliance System (PCS)
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.)
SbC-0055-034-ST-3003 12/13/93
------- |