United States
Environmental Protection Agency
Office of Water
September 1992
U.S. EPA Pretreatment Compliance Monitoring and Enforcement System
Version 3.0 (Final, September 1992)
Developed by Science Applications International Corporation
under contract with the
U.S. EPA Office of Wastewater Enforcement and Compliance
USER'S GUIDE
-------
TABLE OF CONTENTS
1.0 INTRODUCTION 1
2.0 GETTING STARTED 2
System Requirements . 2
Installation, 2
Configuration 3
Conversion 3
Accessing PCME 3
Getting Help 5
3.0 DATA ENTRY . 6
General Information 7
Regulated Pollutants 7
Pollutant Limitations . . 9
Effluent Monitoring Data. ... ......... 11
Required IU Reports ..... 12
IU Inspections 13
Compliance Schedules 13
4.0 ENFORCEMENT. . 15
Violation Detection 15
Violation Tracking 15
5.0 REPORTS 19
List Of IUS 19
IU Fact Sheet 19
Regulated Pollutants and Limits 19
IU Sampling Data 19
Sampling Frequency Report 21
IU Effluent Compliance 23
IU Yearly Compliance. 23
IU Reporting 24
IU Inspections 24
Compliance Schedules 24
Enforcement History . ......... 24
Pretreatment Performance Summary 25
6.0 UTILITIES 28
Reindex Databases 28
Pack Databases . 28
Define Sample Type 28
Revise CA Data 29
System Status 29
-------
Introduction
1.0 INTRODUCTION
The Pretreatment Compliance Monitoring and Enforcement System (PCM1
System) is designed to assist Publicly Owned Treatment Works (POTWs) and
other Control Authorities (CAs) in tracking an industrial users's (IU's)
compliance with applicable pretreatment standards. The menu-driven PCME
System provides an automated means for maintaining an inventory of all
industrial users, recording the analytical sampling information; tracking
required reports, inspections, and enforcement actions; identifying
violations; and determining significant noncompliance (SNC) as required by
40 CFR 403.8(f)(2)(vii).
-------
2.0 GETTING STARTED
Getting Started
System
Requirements
Installation
PCME is designed to run on an IBM-PC or compatible type
computer with at least 640k conventional memory, a hard
disk, and DOS Version 3.3 or higher.
PCME requires at least 1.2 megabytes (Mb) of free hard disk
space to load the program files and significantly more
available hard disk space (approximately 1 to 20 Mb per
year) as the program is run and data are saved. How much
space you will need depends on the number of Ills tracked
and the data associated "with tihese lUs.
To load the PCME Version 3.0 program from the distribution
diskettes, you must create a new subdirectory on your hard
disk (C:\PCME3 in this example) and then copy the
PCMEZIP1.EXE and PCMEZIP2.EXE files from the distribution
diskettes to the new directory. If you have been using
PCME Version 2.Ox (for reference purposes, Version 2.Ox
signifies PCME Version 2.0 and subsequent versions through
2.05), be careful that you copy these files to this new
directory and not to your old PCME directory. Otherwise,
you may OVERWRITE ANY EXISTING PCME FILES AND LOSE YOUR
DATA!
Insert PCME distribution diskette #1 into your floppy drive
(assumed Drive A in examples; substitute a: with b: if you
are utilizing Drive B:) and at your DOS root directory
type:
C:\> md pcme3
C:\> cd pcme3
C:\PCME3> copy a:pcmezipl.exe c:
After the file has been copied, remove distribution
diskette #1 and insert distibution diskette #2 into your
floppy drive and type:
C:\PCME3> copy a:pcmezip2.exe c:
After both files have been copied to your hard disk, you
will need to uncompress them to run PCME. To do this,
type:
C:\PCME3> pcmezipl
The file will uncompress itself. When PCMEZIP1.EXE has
finished uncompressing, repeat for PCMEEIP2.EXE by typing:
C:\PCME3> pcmezip2
After both files have been uncompressed, you may erase both
PCMEZIP1.EXE and PCMEZIP2.EXE from your hard disk.
-------
Configuration
Convers ion
Accessing
PCME
Getting Started 3
Before accessing PCME 3.0, you must ensure that your
computer is configured to handle this software. Examine
the CONFIG.SYS file in your DOS root directory (refer to
your DOS manual for more information). The CONFIG.SYS file
should have the following two commands:
FILES =30
BUFFERS =20
The FILES command reserves enough room to have 30 files
open at one time. If you have other programs running in
DOS (i.e. TSRs, Windows 3.1, etc.) you may need to set this
number somewhat higher. The BUFFERS command reserves
memory space for transferring information to and from
disks. The optimum number really depends on your
particular system (see DOS manual for more information).
Included on the PCME distribution diskette is a conversion
utility that converts PCME Version 2.Ox data files to PCME
Version 3.0 data files. IF YOU ARE A PCME VERSION 2.Ox
USER, YOU MUST RUN THIS UTILITY TO ACCESS YOUR OLD DATA IN
PCME 3.0.
After you have loaded and uncompressed the PCME 3.0 files
onto your hard disk, from your new PCME 3.0 subdirectory,
type:
C:\PCME3> pcmedcu
The screen shown in Figure 2.1 will appear. Enter the
subdirectory where the PCME Version 2.Ox files are found in
the SOURCE box, and enter the subdirectory where the PCME
Version 3.0 files have been loaded in the TARGET box. Once
you have entered the appropriate subdirectories, hit
-W to begin the conversion. The program will
terminate if there are any problems or inconsistencies.
The program will inform you of a successful conversion.
Once the conversion is successfully completed, you may
remove the PCME 2.Ox files from your hard disk.
If you encounter problems with the conversion, please
contact one of the individuals listed in the Getting Help
section.
Once PCME is loaded onto the hard disk, you may start the
program by typing from your new PCME Version 3.0
subdirectory:
C:\PCME3> pcme
The screen shown in Figure 2.2 will appear. Hit any key to
-------
Getting Started 4
access the main menu of PCME.
If you do not have a color monitor and encounter problems
with a disappearing highlight bar (this may happen on an
LCD screen), you can force PCME into monocolor by escaping
from PCME and typing from your new PCME subdirectory:
C:\PCME3> pcme /m
PCME Data Conversion Utility
Version 2.Ox to 3.0
=| SOURCE I =====
Enter the path where the current PCME data files
are located:
C:\PCME
— :""" ]""TARGET""I ""
Enter the path where you want the new data files
to be located:
C:\PCME3
/: Change Window j Ctrl-W: Run | Esc: Quit
Figure 2.1 - PCME Conversion Utility Screen
U.S. EPA Pretreatment Compliance Monitoring and Enforcement System
Version 3.0 (Final, September 1992)
Developed by Science Applications International Corporation
under contract with the
U.S. EPA Office of Wastewater Enforcement and Compliance
{Press any key to continue}
Figure 2.2 - Introduction Screen
-------
Getting Started 5
Getting Help If you have problems or questions as you work with PCME,
help is available in the form of phone support and a
computer bulletin board, (used via computer modem)
PCME users are with problems or questions should contact
any one of the following persons:
Mark Hoeke, SAIC 703-821-4817
James Turner, SAIC 703-821-4622
Brian Wortman, SAIC 703-821-4899
"Lee Okster, U.S. "EPA 202-260-8329
or, if you have access to a modem, and have been instructed
in use of the PCME conference on the SAIC bulletin board,
call the bulletin board at 703-821-4807 and leave a message
for James Turner or Mark Hoeke. For more information on
access, please call James Turner.
If you have received a "fatal runtime error", write down
the error message that appears on your screen (or press
"Print Screen" if you are connected to a printer) and have
it handy when calling user support.
-------
3.0 DATA ENTRY
Data Entry 6
From the main menu, to add, edit, or delete information about an
industry, use arrows to move highlight bar to Industry Data and press ,
The screen shown in Figure 3.1 will appear.
Industry Data
Enforcement
General Information
Regulated Pollutants
Pollutant Limitations
Effluent Monitoring Data
Required IU Reports
Inspections
Compliance Schedules
Reports
Utilities
Exit
Figure 3.1
To select a data entry module, use arrow keys to move highlight bar and
press on the desired module. For example, if you select General
Information a screen similar to Figure 3.2 will appear and allow you to select,
add, or delete (see General Information in this section) an industry. You may
search for a particular industry by typing in its user code.
Industry Data
Enforcement
Reports
Utilities
Exit
General Information
Regulated
Pollutant
Effluent M
Required I
Inspection
Compliance
User Out
Code fall Industry Name
ACME
BORD
COKE
CARW
GOOD
JRGS
SHPC
TYSO
TYSO
ZOO
001
001
001
001
001
001
001
001
002
001
Acme Tire Company
Borden Products
Coca-Cola
John's Car Wash
Goodyear Tire Co.
James River Graphics
Springhill Plating Co.
Tyson's Chicken
Tyson's Chicken
Zoo
Figure 3.2
-------
General
Information
Data Entry 7
Select this data entry module to add, edit, or delete
general industry information. Note that this is the
only module that will allow you to add or delete an
entire industry. Other data entry modules only allow
you to add, edit, or delete information from existing
industries.
Industry comments may be entered by pressing .
Comments may be up to 15 pages long.
Enter the applicable letter for the Category:
— * C *
- 'S1
Categorical industry
Non-categorical significant industry
Non-significant industry
Industrial Fact Sheet Information Screen
IU Code: SHPC Outfall:
Facility Name: Springhill Plating Co.
Address: 100 East Maple Street
City: Springhill State:
Contact Person: Harry Earner
Phone Number: 703-123-1122
SIC Code: 3471 Category: C
Regulated Process: Chrome plating
Cat. Standard: 40 CFR 413 <10,000
Pretreatment Type: Neutralization
Regulated Flow: 7500
Total Flow: 7500
Production Rate: N/A
001
VA Zip: 21201
Permit #: 12242312
Permit Issue Date: 01/01/91
Permit Exp. Date: 12/31/91
CWF Applied (Y/N) : N
Batch Discharge (Y/N) : N
TOMP on file (Y/N) : Y
Spill/slug plan (Y/N) : Y
Enter /edit industry information, press to enter IU comments,
previous, next, to save and exit, to abort.
Figure 3.3
Regulated Pollutants
Use this data entry module to select pollutants
to regulate for an existing industry. Upon
selecting an industry, you will be prompted by a
screen similar to Figure 3.4. Use this screen to
add or edit basic permit information (for
purposes of PCME, all individual control
mechanisms are referred to as permits) and then
select the permit you wish to edit.
-------
Data Entry 8
Once a permit has been entered or selected, the
pollutant selection screen (Figure 3.5) will
appear. Pollutant selection status may be
toggled using the key. Pollutants may be
searched using arrow keys or typing in the
pollutant name (upper/lower case sensitive).
When you have completed selection of all
pollutants press to save.
A master list of the toxic and conventional
pollutants has been provided in PCME 3.0 for
pollutant selection. This master list may be
edited by adding or deleting pollutants while the
pollutant selection screen is active. The
program will not allow you to delete pollutants
that have appeared in prior sampling data (the
program uses the master list in the reports
module to determine TRC violations in sampling
data). TRC values must be entered as 1.2 or 1.4.
Remember, once you have added a pollutant to the
master list, you must still toggle its selection
status to select it for the current industry.
If you deselect previously regulated pollutants,
pollutant limitations and frequency requirements
for the deselected pollutant in the current
permit will be deleted.
Industry Data
Enforcement
Reports
Utilities
Exit
General Information
•/Regulated Pollu
Pollutant Limit
Effluent Monito
Required IU Rep
Inspections
Compliance Sche
Permit Number
Issue
Date
MD005
MD005
MD005
05/15/88
05/15/90
05/15/92
Exp.
Date
05/14/90
05/14/92
05/14/94
Figure 3.4
-------
Data Entry 9
Selection of Regulated Pollutants Data Screen
IU Name: Springhill Plastics
IU Code: 003 Permit No.: MD005
Outfall: FAC Permit Span: 04/05/91 - 05/02/91
Default TRC
Select Pollutant Units Value
V
V
1,1, 1-Tr ichloroethane
1,1,2, 2-Tetrachloroethane
1,1, 2 -Tr ichloroethane
1 , 1-Dichloroethane
1 , 1-Dichloroethene
1,2, 4-Trichlorobenzene
1 , 2 -Dichlorobenzene
1 , 2-Dichloroethane
mg/1
rog/1
mg/1
mg/1
mg/1
mg/1
mg/1
mg/1
1.2
1.2
1.2
1.2
1.2
1.2
1.2
1.2
Type pollutant name or use arrow keys to search.
Press to toggle selection status, to edit, to
to delete, to save, or to abort.
add
Figure 3.5
Pollutant Limitations
Use this data entry module to enter numerical
limits, required sampling method, and required
sample frequencies for selected pollutants. Upon
selecting an industry, you will be prompted by a
screen similar to Figure 3.4. Use this screen to
select a permit you wish to edit or use to
copy pollutant limitations from one permit to
another permit.
If you wish to monitor a pollutant, but have no
limitations in effect, leave the daily maximum
and average limit blank. Similarly, if you do
not implement an average limit for certain
pollutants, leave only the average limit blank.
You may specify the type of average limit on a
pollutant-by-pollutant basis ('4' denotes 4-day
average, 'M1 denotes monthly average). See IU
Sampling Data in the Reports section for
descriptions on how averages are calculated.
The required sampling method is denoted by a
user-defined character code (e.g. 'G1 grab, 'C1
-------
Data Entry 10
composite). PCME allows you the flexibility to
enter whatever character code you choose.
However, you must be careful to be consistent in
data entry, as the reports generated by PCME will
compare required sampling method with the actual
sampling method and flag violations where the
codes differ. You may leave required method
blank if you do not wish to utilize this function
of PCME.
You may also enter a required frequency of
sampling on a pollutant-by-pollutant basis. To
do this, you must enter two values, each in a
separate column: the first value is the required
number of samples that must be taken, and the
second value is the timespan in which these
samples must be taken. For instance, for an
industry required to sample semi-annually, enter
'I1 for required number of samples, and 'S1
(semi-annual) for the timespan. Note that you
would not enter 2 samples per year ('2' and 'Y'),
because this would signify a frequency of two
samples taken anytime during the year and not
semi-annual sampling. Continuous sampling
requirements (pH, flow, etc.), cannot be tracked
by PCM1 3.0.
Note: Enter upper pH limit in Daily Limit column,
and lower pH limit in Average Limit column.
Industrial Effluent Limits Data Entry/Edit Screen
IU Name: Springhill Plating Co.
IU Code: SHPC
Outfall: FAC
Parameter
Permit No.: MD005
Permit Span: 05/15/90 - 05/14/92
Unit
Daily
Limit
Average
Limit
A
v
g
M
t
h
# of
Req.
Samp
S
P
n
Cadmium
Chromium
Copper
Cyanide
Lead
mg/1
rag/1
mg/1
mg/1
mg/1
0.11
2.77
3.38
1.20
0.69
0.07
1.71
2.07
0.65
0.43
M
M
M
M
M
C
C
C
C
C
1
1
1
1
1
S
S
S
S
S
Type data in directly.
Enter units
Use to save, to abort.
Figure 3.6
-------
Effluent Monitoring Data
Data Entry 11
Use this data entry module to add, edit, or
delete sampling information. Upon selecting
an industry, you will be prompted by a
screen similar to Figure 3.7. Use this
screen to add, delete, or select a sample
event.
You should enter the day the sample was
taken in the Sample Date column. The Sample
Type is analogous to the Sample Type in PCME
Version 2.Ox. In PCME Version 3.0, you have
the flexibility to define Sampling Types
(see Utilities). You must enter a defined
Sample Type in this screen. You may toggle
through defined types using the key.
Sample number is for any outfall that is
sampled more than once per day.
Once you have added or selected a sampling
event, a screen similar to Figure 3.8 will
appear.
Analytical results below detection may be
entered using '<• before the detection
limit. The BDL factor specified by the user
in the Control Authority data entry screen
(see Utilities) will be multiplied by the
detection limit for use in averaging BDL
data.
Industry Data
Enforcement
Reports
Utilities
Exit
:
")[ I[[[
General Informatit
Regulated Polluta
Pollutant Limitat
•/Effluent Monitori
Required IU Repor
Inspections
Compliance Schedu
••••::::::::::::::::::::::::::;::iH::::::::::::::::::::::;;:i
m
Sample
Date
V04/04/91
04/05/91
12/30/91
12/31/91
:::::::::::::::::::::::::::::::::::::!:
Sampling
Authority
SCHEDULED
SCHEDULED
SCHEDULED
UNSCHEDULED
:::::::::::::::•:•••:•:•:•••:::•:•:::••:::
Sample
Number
1
1
1
1
-------
Data Entry 12
Industrial Effluent Monitoring Data Entry/Edit Screen
IU Name: Springhill Plating
IU Code: SHPC Sample Date: 04/04/92
Outfall: 001 Sample Auth. : City
Sample Number: 1
Daily Average M Analysis
Parameter Name Limit Limit Units e Result
Cadmium
Chromium
Copper
Cyanide
Lead
Nickel
Silver
0.11
2.77
3.38
1.20
0.69
3.98
0.43
0.07
1.71
2.07
0.65
0.43
2.38
0.24
mg/1
mg/1
mg/1
mg/1
mg/1
mg/1
mg/1
C
C
C
C
C
C
C
<0.01
5.4
0.8
<0.05
<0.01
1.23
<0.005
Enter sampling results. Use '<' for levels below detection.
Type results: edit field to save changes to abort.
Required IU Reports
Figure 3.8
Use this data entry module to add, edit, or
delete required industry reports. Upon selecting
an industry a screen similar to Figure 3.9 will
appear. Reports may be given any name you
choose.
Required Industrial
Reporting Data Entry /Edit Screen
IU Name: Tyson's Chicken
IU Code: 003 Outfall: FAC
Date Date
Due Received Report Name Comment
02/02/90
01/15/91
07/15/91
12/31/91
01/27/91
01/01/90
Periodic
Periodic
Periodic
Compliance
Compliance
Compliance
Type due date to search, Use arrow keys, to move
edit add delete save abort
Figure 3.9
-------
IU Inspections
Data Entry 13
Use this data entry module to add, edit, or
delete information on industrial inspections.
Upon selecting an industry a screen similar to
Figure 3.10 will appear.
Inspection comments may be entered by pressing
. Inspection comments may be up to 15 pages
long.
Industrial Inspections Data Entry/Edit Screen
IU Name: Springhill Plating
IU Code: 001
Inspection
Date Time Type
01/02/90
04/05/90
10 AM
3 PM
Announced
Un-announc
Co.
Outfall: 001
Inspector
Randy Tree
Randy Tree
Industry Contact
Jeb Golombs
Jeb Golombs
Type inspection date to search, Use arrow keys, to move
edit add delete comments -W save abort
Figure 3.10
Compliance Schedules
Use this data entry module to add, edit, or
delete information on industry compliance
schedules. Upon selecting an industry a
screen similar to Figure 3.11 will appear.
The enforcement action (EA) date represents
the date that the compliance schedule was
issued. If an industry has more than one
compliance schedule, this may be shown by
the different EA dates.
The Complete Date refers to the actual date
the required milestone was completed.
-------
Data Entry 14
Compliance Schedule Data Entry /Edit Screen
IU Name: Springhill Plating Co.
IU Code: SHPC Outfall: 001
EA Milestone Complete
Date Milestone Due Date Date
11/11/89
11/11/89
11/11/89
11/11/89
11/11/89
11/11/89
Request for bids on pretreatment system
Choose winning bid
Design stage complete
Complete installation
Complete testing
Full compliance
12/31/89
04/15/90
07/01/90
09/30/90
12/31/90
01/31/91
12/14/89
04/01/90
10/04/90
12/02/90
02/22/91
02/22/91
Use arrow keys to move, edit
add delete -W save to abort.
Figure 3.11
-------
Enforcement 15
4.0 ENFORCEMENT
One of PCMI's new features to assist Control Authorities in detecting
and tracking violations and enforcement actions is the addition of an
enforcement module. The enforcement module is designed to allow you to
detect and save violation information on industries and give you the
.ability to enter enforcement action information related to detected
violations.
Violation The violation detection function will scan selected
Detection industries' sampling data, reporting data, compliance
schedule data, and enforcement actions data to detect any
violations of:
- Daily limits (Code 01)
Average limits (Code 02)
Sampling method (Code 03)
Sampling frequency (Code 04)
Report due dates (Code 05)
- Milestone due dates (Code 06)
- Enforcement response due dates (Code 07)
All violations detected will be saved in the industry
violation database, and are retrievable by using the
Violation Tracking function, or generating the Enforcement
History Report.
One example how the Violation Detection function could be
used is illustrated below:
PROBLEM: I want to know all industry violations that
occurred during previous week.
STEP 1: Run violation detection for all industries (to
accurately detect violations in sample frequency,
utilize a date range which encompasses your
longest frequency timespan).
STEP 2: Generate enforcement history report by selecting
all industries and selecting the previous week as
the date range,
PCME will generate the enforcement history report
which shows violations as well as enforcement
actions in the given date range for all selected
industries.
.Violation After detecting violations using the Violation Detection,
Tracking violation data for a particular industry may be viewed.
Data may be modified at the user's discretion, and data on
other violations may be added. User entered enforcement
-------
Enforcement 16
action data is also presented and may be modified. To
obtain the violation tracking information screen, after
selecting the Enforcement module on the main menu, move
highlight bar to Violation Tracking. A screen similar to
Figure 4.1 will appear and allow you to select an industry
to view violation data. You may search for a particular
industry by typing in its user code.
Industry Data
Enforcement
Reports
Utilities
Exit
i!i!i:!!i::ii::iiiliiii!iiiii!i!iijiiiii
;;:;::::::::::::H:i:l::;i:::::::::::::
::::::::::::••:•:::::::::::::::::•:•:::
:::»!:::::::::::::::::::::::::::::::::.
:::::::;:::|:::|:::::::: | Violation
User Out
Code fall
ACME
BORD
COKE
CARW
GOOD
JRGS
SHPC
TYSO
TYSO
ZOO
001
001
001
001
001
001
001
001
002
001
Detect ion | H:!UHH::::iUK:KH»iK:H»::HHHS:HHHHH»::U:::::::H::::::::
Industry Name
Acme Tire Company
Borden Products
Coca-Cola
John's Car Wash
Goodyear Tire Co.
James River Graphics
Springhill Plating Co.
Tyson's Chicken
Tyson's Chicken
Zoo
:::i::;:;:i::::::::::::::::::::::::::::
:::::::::::::::::::::::::::::::::::;:;:
Figure 4.1
After selecting an industry, a split screen window similar
to Figure 4.2 showing violations and enforcement actions
will appear.
In the violation window, PCME will show you all the
detected and user entered violations of the selected
industry. You may add, edit, or delete information in this
window.
If you have evaluated an industry as SNC under any of the
following 40 CFR Parts:
- 403.8(f)(2)(vii)(C)
- 403.8(f)(2)(vii)(D)
- 403.8(f)(2)(vii)(G)
- 403.8(f)(2)(vii)(H)
you should add it as a violation in industry's violation
file. To ensure the Yearly Compliance Report and
Pretreatment Performance Summary Report accurately count
-------
Enforcement 17
these "Other Reasons" in SNC counts, the VC (violation
code) that should be entered should be "00". Other user
entered violations which are not defined as SNC under 40
CFR Part 403.8(f)(2)(vii) should be entered with a
violation code that is not equal to "00".
In the enforcement action window (windows may be toggled by
pressing ), you may add, edit, or delete appropriate
information on enforcement actions in response to industry
violations. PCME does not recommend a particular
enforcement action to be taken in response to a single
violation or a pattern of violations. You should follow
your approved enforcement response plan to determine the
appropriate response to industry violations.
The EA Code refers to an enforcement action code which you
enter to signify the enforcement action that was taken in
response to the industry violation. PCME allows you the
flexibility to enter any enforcement action code, however,
if you wish the Pretreatment Performance Summary Report to
accurately show counts of enforcement actions taken, you
must enter the following two or three characters as the
first characters of the five character EA Code.
Enforcement Action EA Code
NOV Issued NOV
Administrative Order AO
Compliance Schedule SCH
Civil Suit Filed CIV
Criminal Suit Filed CRI
Penalty Collected PEN
lUs Published PUB
Other Actions OTH
The Response Date refers to the required date by which the
industry must respond to the Control Authority enforcement
action.
The Complete Date refers to the actual date when the industry
responded to the Control Authority enforcement action.
Violations will be detected when the industry does not respond
by the required response date.
-------
Enforcement 18
Enforcement History: Springhill Plating
Violation 1A
VC Violation Date Code
05
01
02
03
01
01
04
Semi-annual Report late
Chromium daily limit
Chromium monthly limit
BOD sampling method
BOD daily limit
Chromium daily limit
pH sampling frequency (0/1)
12/15/89
12/23/89
12/31/89
01/01/90
01/01/90
01/02/90
01/06/90
OTH01
NOV01
NOV02
NOV02
NOV02
NOV02
OTH02
Eh EA Response Complete
Code Enforcement Action Date Date Date
OTH01
NOV01
NOV02
Phone to remind report due
Notice sent: chromium vio 12/23
Notice sent: vio 12/31 - 01/02
12/15/89
12/24/89
01/03/90
12/20/89
01/01/90
01/08/90
12/17/89
01/08/90
01/08/90
Figure 4.2
-------
Reports 19
5.0 REPORTS
PCME Version 3.0 has twelve built-in reports for printing industrial
information. Depending upon the report, you may be able to print all or a
subset of industries and you may be able to print any specified range of
dates. To print a report, use arrows to move highlight bar to Reports at the
main menu and press . The screen shown in Figure 5.1 will appear.
Below is a description of each report, and if applicable, an explanation of
how PCME calculates the output.
Industry Data
Enforcement
'Reports
Utilities
Exit
List of lUs
IU Fact Sheet
Regulated Pollutants & Limits
IU Sampling Data
Sampling Frequency
IU Effluent Compliance
IU Yearly Compliance
IU Reporting
IU Inspections
Compliance Schedules
Enforcement History
Pretreatment Performance Summary
Figure 5.1
List of lUs
IU Fact Sheet
Regulated
Pollutants
and Limits
IU Sampling
Data
The List of lUs is an output of each industry's address,
applicable category and current permit expiration (from
General Information)
The IU Fact Sheet is an output of an industry's general
information. One or more industrial fact sheets may be
reported at one time.
The Regulated Pollutants and Limits Report is an output of an
industry's permit limits and sampling requirements (methods
and frequencies). One or more industries may be reported at
one time. If an industry has one or more expired permits, all
permits will be output.
The IU Sampling Data Report is an output of all an industry's
sampling data within a user specified reporting period. One
or more industries may be reported at one time.
-------
Reports 20
PARAMETER NAME
Chromium
Chromium
Chromium
Chromium
Oil and
Oil and
grease
grease
Oil and grease
Oil and
pH 5.5
pH 5,5
grease
- 9.5
- 9.5
DAILY
LIMIT
2.3
2.3
2.3
2.3
100
100
100
100
R*
S SAMPLE
M . DATE
G
G
G
G
G
G
G
G
G
G
09/23/91
09/24/91
10/07/91
10/08/91
09/23/91
09/24/91
"09/25/91
09/26/91
09/23/91
09/24/91
SAMPLE
TYPE
SELF
SELF
UNSCHEDULED
UNSCHEDULED
SELF
SELF
SELF
SELF
SELF
SELF
A* V*
S ANALYSIS I
M RESULT 0 UNIT
G
G
G
G
G
G
G
G
G
G
<0
<0
7.
<0
78
40
58
*
*
8
*
05
05
05
170
5.
9.
mg/1
mg/1
mg/1
mg/1
mg/1
mg/1
mg/1
* mg/1
79 *
23
Figure 5.2 - Daily Sampling Report
Violations are noted for exceedences of a parameter's daily
limit or an improper sampling method. In conjunction with the
Sampling Data Report, an Averages Sampling Data Report is also
output. The Averages Sampling Data Report calculates monthly
4-day averages and notes violations of the average limit.
PARAMETER
NAME
Chromium
Chromium
Oil and grease
L
T
M
M
M
AVERAGE
LIMIT
1.71
1.71
100
STARTING
DATE
09/01/91
10/01/91
09/01/91
ENDING
DATE
09/30/91
10/31/91
09/30/91
AVERAGE
RESULT
0.025
5.912
61.50
V*
I
0
*
# OF
SAMP
2
2
4
Figure 5.3 - Averages Sampling Data Report
Monthly averages are calculated by calendar month. Levels
below detection (indicated with '<• in sample results) will be
multiplied by the BDL averaging factor from the Control
Authority information screen (see Utilities).
Four-day average groups are calculated as four consecutive
sampling events beginning from the first sampling event ever
recorded. As an example, say an industry has sampled cadmium
9 days, which include:
1st:
2nd:
3rd:
4th:
5th:
6th:
7th:
8th:
9th:
11/09/91
11/10/91
11/11/91
11/12/91
11/13/91
01/01/92
01/02/92
01/03/92
01/04/92
— 4-day grouping
4-day grouping
• outlier
-------
Sampling
Frequency
Report
Reports 21
If you specify a reporting period as the first six months of
1992, then a four day average will be calculated for the dates
11/13/91 through 01/03/.92. Even though the industry has four
consecutive days of sampling in January 1992, PCME will start
with 11/13/91. The outlier 01/04/92 will be reported, but no
4-day average for it will be calculated. A daily violation
will be flagged for any date within the reporting period.
Four-day averages will not be calculated when there are less
than four days of sampling data. Levels below detection
(indicated with '<• in sample results) will be multiplied by
the "BDL averaging "factor from the Control Authority
information screen (see Utilities).
The sampling frequency report is designed to allow you
to list violations of sampling frequency as specified
by an industry's permit(s). PCME separates the user defined
reporting period into timespans according to the frequency
requirements (daily, weekly, monthly, quarterly,
semi-annually, yearly) and counts the number of actual results
for a given parameter within the timespan. If the number of
actual results is less than the required number for the
timespan, a violation of frequency will result. PCME will
print only those timespans in which a frequency violation
occurs.
VIOLATIONS
PERIOD
TOTAL
PARAMETER NAME
BODS
(IU
*
•
5
POTW)
:l
PERMIT
ISSUE
DATE
01/01/90
01/01/90
SPAN
START
DATE
01/01/90
02/01/90
SPAN
END
DATE
01/31/90
02/28/90
REQ.
NUM.
4
4
ACT.
NUM.
3
2
Figure 5.3 - Sampling Frequency Report Output
All parameters that are listed as a regulated pollutant on
any active permit during the requested period will appear on
sampling frequency report. Total number of samples in
period will include all samples taken during the requested
period by both the IU and the POTW regardless of whether
frequency requirements were in effect for the entire period.
Violations will appear when a parameter has not been sampled
at the required frequency by the IU. If the POTW performs
all the sampling at the IU, required frequencies should not
be specified in PCME, otherwise frequency violations will
result due to the lack of IU data. If the user defined
reporting period is less than a parameter's frequency span,
-------
Reports 22
or does not encompass one entire frequency span, no
violations can be calculated. Frequency spans are
determined as follows: .
- Daily:
- Weekly:
- Monthly;
- Quarterly:
- Semi-ann:
Frequency requirements begin on the day
after the permit issue date and end on the
permit expiration date.
A weekly span is defined as Sunday through
Saturday. If the permit issue date falls
in the middle of the week, frequency
requirements will begin the Sunday after
the permit issue date. If the permit
expiration date is in the middle of the
week, frequency requirements end the
Saturday before the permit expiration
date.
A monthly span is defined from the first
of the month to the end of the month. If
the permit issue date falls in the middle
of the month, frequency requirements will
begin on the first of the next month after
the permit issue date. If the permit
expiration date is in the middle of the
month, frequency requirements will end at
the end of the month prior to the permit
expiration date.
A quarterly span is defined as one of four
three-month periods in the Control
Authority's reporting year (see Utilities
to define reporting year). If the permit
issue date falls in the middle of the
three-month span, frequency requirements
will begin on the first day of the
following three-month period. If the
permit expiration date falls in the middle
of the three-month span, frequency
requirements will end on the last day of
the prior three-month period.
A semi-annual span is defined as one of
the two six-month periods in the Control
Authority's reporting year (see Utilities
to define reporting year). If the permit
issue date falls in the middle of the
six-month span, frequency requirements
will begin on the first day of the
following six-month period. If the permit
expiration date falls in the middle of
six-month span, frequency requirements
-------
- Yearly:
Reports 23
will end on "the last day of the prior
six-month period.
A yearly span is defined as the Control
Authority's reporting year (see Utilities
to define reporting year). If the permit
issue date falls in the middle of the
reporting year, frequency requirements
will begin on the first day of the
following reporting year. If the permit
expiration date falls in the middle of the
reporting year, frequency requirements
will end on the last day of the prior
reporting year.
IU Effluent
Compliance
The IU Effluent Compliance Report calculates industrial
effluent compliance with applicable pollutant limitations
on a pollutant-by-pollutant basis. One or more industries
may be reported at one time and you may specify any range
of dates from one day to all dates. The report will show
compliance status for both daily and average limitations.
If no data for a regulated pollutant is contained in the
specified reporting period, that pollutant will not appear
on the report.
The compliance status flag will only be determined when the
range of dates is exactly equal to six months. Note that
PCME does not interpret a range from January 1 to July 1 as
exactly six months. Instead, PCME defines a range from
January 1 to June 30 as six months.
Sampling Period Reported: 01/01/91 - 06/30/91
PARAMETER NAME
BODS
Chromium
Chromium
Oil and grease
Zinc
Zinc
pH
LIMIT
Daily
Daily
Monthly
Daily
Daily
Monthly
Daily
TOTAL
VIO.
2
0
0
2
1
1
0
TRC
VIO.
2
0
0
1
1
1
0
TOT
OBS.
3
3
1
9
11
2
9
STATUS
SNC
C
C
NC
NC
SNC
C
Figure 5.4
IU Yearly
Compliance
The IU Yearly Compliance Report calculates yearly
compliance status for all industries for a user specified
year. PCME will calculate compliance status based upon the
-------
INDUSTRIAL USER
Reports 24
definition of significant noncompliance (SNC) as defined by
40 CFR 403.8(f)(2)(vii). PCME Version 3.0 applies the SNC
definition in accordance with current EPA policy which
stipulates that chronic and TRC effluent violations
[sections (A) and (B) in 40 CFR 403.8(f)(2)(vii)] must be
evaluated at the end of each quarter in the Control
Authority's reporting year using the previous six-months of
data. If the industry is in SNC at the end of any quarter,
the industry is considered to have been in SNC for the
reporting year.
The flag denotes whether the noncompliance was due to
standards, reporting, compliance schedule milestones, or
other reasons.
COMPLIANCE
OUTFALL STATUS FLAG
Acme Tire Co.
Borden Products
Coca-Cola
John ' s Car Wash
Goodyear Tire Co.
James River Graphics
Springhill Plating Co.
Tyson's Chicken
Tyson's Chicken
001
001
001
001
001
001
001
001
002
c
c
SNC
SNC
C
C
C
c
SNC
S
S
S
Figure 5.5
IU Reporting
IU Inspections
Compliance
Schedules
Enforcement
History
The IU Reporting Report is an output of required reports of
one or more industries for a user specified time frame.
Any report that is not submitted within 30 days of the due
date will be denoted as an SNC violation.
The IU Inspection Report is an output of inspection
information for one or more industries for a user specified
time frame.
The Compliance Schedule Report is an output of compliance
schedule requirements for one or more industries for a user
specified time frame.
The Enforcement History Report is an output of violations
and enforcement actions for one or more industries in a
user specified time frame.
-------
VIOLATION HISTORY REPORT
Reports 25
Sampling Period Reported: 01/01/01 - 12/31/99
VC VIOLATION
VIOL
DATE
EA
CODE
00 403.8(f)(2)(vii)(C): Other Effluent Violations
01 pH daily limit
00 403.8(f)(2)(vii)(C): "Other Effluent Violations
01 pH daily limit
05 Periodic submitted late
09/23/91 NOV01
OB/23/91 NOV01
09/24/91 NOV01
10/09/91 NOV02
04/01/92 NOV03
Figure 5.6
ENFORCEMENT HISTORY REPORT
Sampling Period Reported: 01/01/01 - 12/31/99
EA
CODE
NOV01
NOV02
NOV03
ENFORCEMENT ACTION
Notice of Violation
Notice of Violation
Notice of Violation
ACTION
DATE
10/01/91
10/10/91
04/02/92
RESPONSE
REQ DATE
10/06/91
10/15/91
04/07/92
COMPLETE
DATE
10/03/91
10/14/91
04/09/92
Figure 5.7
Pretreatment
Performance
Summary
Total lUs:
Active
Control
Documents:
Total lUs
in SNC:
The Pretreatment Performance Summary is designed to
summarize pretreatment activity in the Control
Authority'sreporting year. Counts for the year are
broken down by: categorical industries (CIUS)» non-
categorical significant industries (Non-Cat SIUs), and
non-significant industries (non-SIUs).
Count of the total number of unique industries (unique IU
code)
Count of the number of unexpired control documents at the
the end of the pretreatment year.
Count of unique industries in significant noncompliance
as defined by 40 CFR 403.8(f)(2)(vii) anytime during the
pretreatment year.
-------
Reports 26
SNC for
Discharge
Standards:
SNC for
Reporting:
SNC for
Compliance
Schedules:
SNC for
Other
Reasons:
Sampling
Events
Conducted:
Inspections
Conducted:
lUs
Sampled:
lUs
Inspected:
IUs Subject
to Enf.
Action
NOVs Issued
Admin.
Orders
Count of unique industries in significant noncompliance
as defined by 40 CFR 403.8(f)(2)(vii)(A) or (B) anytime
for any pollutant during the pretreatment year. PCME
Version 3.0 applies the SNC definition in accordance with
current EPA policy which stipulates that chronic and TRC
effluent violations must be evaluated at the end of each
quarter in the Control Authority's reporting year using
the previous six-months of data. If the industry is in
SNC at the end of any quarter, the industry is considered
to have been in SNC for the reporting year.
Count of unique industries in significant noncompliance
as defined by 40 CFR 403.8(f)(2)(vii)(F) anytime during
the pretreatment year.
Count of unique industries in significant noncompliance
as defined by 40 CFR 403.8(f)(2)(vii)(E) anytime
during the pretreatment year.
Count of unique industries in significant noncompliance
as defined by 40 CFR 403.8(f)(2)(vii)(C), (D), (G), or
(H) anytime during the pretreatment year. Other reasons
are entered by the Control Authority in the Violation
Tracking module (see Violation Tracking).
Count of total sampling events conducted during the
pretreatment year (Control Authority or industry).
Count of total inspections conducted during the
pretreatment year.
Count of unique industries that have been sampled at
least once during the pretreatment year.
Count of unique industries that have been inspected at
least once during the pretreatment year.
Count of unique industries that have been subject to at
least one enforcement action during the pretreatment
year. Enforcement actions are entered by the Control
Authority in the Violation Detection module (see
Violation Tracking).
Count of total NOVs issued during the pretreatment year.
NOV data may be entered in the Violation Tracking module
in the enforcement action table.
Count of total administrative orders issued during the
pretreatraent year. AO data may be entered in the
Violation Tracking module in the enforcement action
table.
-------
Reports 27
Compliance
Schedules
Civil
Suits
Criminal
Suits
Penalties
Collected
IUs
Published
Other
Actions:
Count of total schedules issued during the pretreatment
year. Compliance schedule issuance data should be
entered in the Violation Tracking module in the
enforcement action table. Information regarding
milestone completion dates should be entered in the
Compliance Schedule module.
Count of total civil suits filed during the pretreatment
year. Civil suits data may be entered in the Violation
Tracking module in the enforcement action table.
Count of total criminal suits filed during the
pretreatment year. Criminal suits data may be entered in
the Violation Tracking module in the enforcement action
table.
Count of total number of penalties collected during the
pretreatment year. Penalty data may be entered in the
Violation Tracking module in the enforcement action
table.
Count of total number of IUs published during the
pretreatment year. IUs published data may be entered in
the Violation Tracking module in the enforcement action
table.
Count of total number of other actions taken by the
Control Authority during the pretreatment year. Other
actions data may be entered in the Violation Tracking
module in the enforcement action table.
-------
Utilities 28
6.0 UTILITIES
PCME Version 3.0 is equipped with five basic utility functions as
described below. To run these functions,, use arrows to move highlight bar
to Utilities at the main menu and press . The screen shown in
Figure 6.1 will appear.
Industry Data
Enforcement
Reports
Figure 6.1
Utilities
Exit
Reindex databases
Pack databases
Define sample types
Revise CA data
System status
Reindex
Databases
Pack databases
Define Sample
Type
PCME Version 3.0 uses index files to sort databases in a
specific order. Database index files are known to get
corrupted from time to time. Symptoms of a corrupted
index file include junk, garbled, or missing data. If
you suspect that you have a corrupted index file, try to
rebuild the index file using the reindexing command.
When PCME data records are deleted, the deletion is not
permanent until the database is "packed", which basically
involves rewriting the database without data records
which are marked for deletion. "Packing" is a time
intensive process, and slows performance of data entry
functions. In the interest of performance, PCME Version
3.0 is not equipped with an automatic "pack" when data is
deleted, and instead, gives the user the flexibility to
permanently delete data when it is convenient. "Packing"
is optional. You may run PCME without ever "packing"
your databases and it would run normally. Deleted data
will not appear in data entry or reports. However, data
records marked for deletion utilize hard disk space
unnecessarily and it is recommended that databases be
packed on occasion. How often will depend upon the
amount of editing and deleting of data that you perform.
During Effluent Monitoring data entry, you will be
queried for a sample type. You must enter a defined
sample type before continuing with data entry. To define
sample types, select this function by pressing .
You may add, edit, or delete defined sample types in this
presented table. Sample types are used internally by
-------
Utilities 29
PCMI to determine whether the POTW or the IU performed
the monitoring.
Revise CA Data You may add or edit control authority information using
this function.
Enter the month and day that your reporting year begins,
otherwise PCME defaults to a January 01 - December 31
reporting year.
Enter a below detection limit (BDL) averaging factor to
inform PCME how to handle analysis results below
detection when averaging data. PCME will multiply any
results below detection by this factor when calculating
averages. If no BDL averaging factor is entered PCME
will default to a value of 1.
Control Authority Information Screen
Control Authority Name: County Sewer Commission
Address: 534 East Maple Street
City: Allegheny state: Zip:
Contact Person: John Lorcom
Contact Phone Number: 123-456-7890
NPDES Permit Number:
Enter Month and Day that Reporting Year
begins (for IU compliance): 01/01
Enter factor for averaging less
than detect values (0.00 - 1.00): 0.5
Enter/edit information. Press on the last
field to save or press to abort.
Figure 6.2
System Status This function shows current status (time, date, RAM
available, hard disk space available) of your computer.
------- |