ENFORCEMENT
MANAGEMENT
SYSTEM
USERS
GUIDE
S. ENVIRONMENTAL PROTECTION AGENCY
-------
ENFORCEMENT MANAGEMENT SYSTEM
MARCH 1972
USERS GUIDE
ENVIRONMENTAL PROTECTION AGENCY
OFFICE OF AIR PROGRAMS
RESEARCH TRIANGLE PARK, N. C. 27711
CONTRACT NUMBER 68-02-0079
PREPARED BY
v~@
THE RESEARCH CORPORATION
. OF NEW ENGLAND
HARTFORD, CONNECTICUT 06106
\
"
-------
ACKNOWLEDGEMENT
In developing the Enforcement Management System described in this
manual, TRC has been guided by the Office of Air Programs. In particular
Mr. Lloyd Hedgepeth provided extensive technical assistance and guidance
as the various aspects of the program were developed.
We are also indebted to the state and local agencies who provided
valuable time to the authors during the formative and design stages of
the proj ecL
Participating in a meaningful way were the state agencies
of Maryland, Missouri and New Jersey.
Local agencies in St. Louis, St.
Louis County, Baltimore and Baltimore County also gave generously of their
time.
The principal authors of the system (Scott Shanks, Robert Hippler
and Ed Cohen) also wish to thank the other members of the Office of Air
Programs staff and of The Research Corporation of New England staff who
participated in the project.
Hi
-------
This report was furnished to the Environmental
Protection Agency by The Research Corporation
of New England in fulfillment of contract number
68-02-0079. The contents of this report are re-
produced herein as received from the contractor.
The opinions, findings, and conclusions are those
of the authors and not necessarily those of the
Environmental Protection Agency. Mention of
company or product names does not constitute
endorsement by the Environmental Protection Agency.
iv
-------
TABLE OF CONTENTS
Section
Title
ACKNOWLEDGEMENT
TABLE OF CONTENTS'
1.0
MANAGEMENT GUIDE
2.0
SYSTEM DESCRIPTION
3.0
STANDARD COMPUTERIZED SYSTEM
3.1
Project Leader and Data Bank Coordinator
3.2
Computer System Description
3.3
Operation of the System
3.4
Input Forms.
3.5
Output Reports
3.6
Files Maintained by the Data Bank Coordinator
3.7
System Startup
4.0
ADVANCED COMPUTERIZED SYSTEM
4.1
Description
4.2
Technical Details
5.0
MANUAL
5.1
General Description
5.2
System Description
5.3 .
Data Bank Coordinator
5.4
System Support
5.5
Startup
v
Page
iii
iv
1
7
16
17
20
25
28
42
70
70
85
85
90
99
99
100
117
121
123
-------
TABLE OF CONTENTS (Cont'd)
Section Title Page
6.0 ALERT HANDLING 128
7.0 COMPLAINT HANDLING 131
8.0 AIR QUALITY RELATIONSHIP 137
APPENDIX
1.0
SYSTEM NARRATIVE - OVERVIEW
142
2.0
PROGRAM NARRATIVES
146
2.1
2.2
Program 1 - Update
Program 2 - Extract
146
151
2.3
Program 3 - Print Run
154
2.4
Description of Sort 1 and 2
155
3.0
STARTUP PROCEDURES
157
3.1
Initializing COBOL Tables
157
3.2
Building the Initial Master File
168
4.0
EDIT DESCRIPTION
170
5.0
OPERATING INSTRUCTIONS
172
5.1
Request for Computer Processing
17?
5.2
JCL for DOS and OS
177
6.0
MASTER FILE RECORD LAYOUTS
184
7.0
CONTROL CARD LAYOUT
187
8.0
PERSONNEL AND LETTER CARD LAYOUT
190
9.0
KEYPUNCH INSTRUCTIONS
193
vi
-------
Figure
1.1
1.2
2.1
3.1
3.2
3.3
3.3A
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
3.12
3.13
3.14
3.15
3.16
3.17
LIST OF ILLUSTRATIONS
Title
Data collection flow.
Data flow, abatement actions.
Enforcement system schematic, showing system monitoring of
enforcement activities.
Computer processing schematic
System actions.
Source data entry form, Emission point entry form
Source data entry form, source data form.
Action card. Design at top is for installations with
interpreting keypunches. The lower design is for 60-column
interpreters. .
Special action card.
Overdue action report prepared by computerized system.
Future schedule summary prepared by computerized system.
Future schedule summary prepared by computerized system.
Geographic locator prepared by computerized system.
Geographic locator prepared by computerized system.
Sample letter produced by system for mailing to source.
Sample letter produced by system for mailing to source.
Sample letter produced by system for mailing to source.
Sample letter produced by system for mailing to source.
Sample letter produced by system for mailing to source.
Sample letter produced by system for mailing to source.
Sample letter produced by system for mailing to source.
vii
Page
4
5
9
21
27
29
34
37
39
43
44
45
47
48
50
51
52
53
54
55
56
-------
LIST OF ILLUSTRATIONS (cont'd)
Figure
Title
3.18
Sample letter produced by-system for mailing to source.
Source action summary prepar~d by computerized system.
Action su~ary report prepared by computerized system.
3.19
3.20
3.21
Source registration report prepared by computerized system.
3.22
Edit and update report prepared by computerized system.
Sample action cards.
Sample action cards.
Sample special action cards.
Sample special action cards.
Sample special cards.
3.23
3.24
3.25
3.26
3.27
3.28
Flow of data.
3.29
Milestone chart.
3.30
Estimated time for system startup and operation.
4.1
Schematic scheduling function.
4.2
System schematic.
4.3
Shifting weeks on personnel card.
5.1
System files and recommended sheet holder.
5.2
Emission point data sheet.
5.3
Company data sheet.
5.4
Charge out sheet.
5.5
Action copy (white).
5.6
Source file copy (blue).
5.7
Suspense copy (yellow).
viii
Page
57
59
61
62
64
65
66
67
68
69
71
73
84
86
91
93
101
103
104
105
107
108
109
-------
LIST OF ILLUSTRATIONS (cont'd)
Figure
Title
5.8
Individual schedule copy (pink).
5.9
Section schedule copy (green).
5.10
Action sheet set distribution.
5.11
Filled in action sheet.
5.12
Filled in action sheet.
5.13
Action summary report.
5.14
Overdue action report.
5.15
Generalized system operation.
5.16
Manual system start-up.
6.1
Schematic, processing of alert data.
7.1
General complaint handling schematic.
Table
4.1
Next action table.
4.2
Date table.
ix
Page
110
111
112
114
116
118
119
122
124
130
133
97
98
-------
APPENDIX
LIST OF ILLUSTRATIONS
Figure
Title
Page
1.1
Computer processing schematic.
143
2.1
Adding new action record to master file.
148
2.2
Master file format and delete logic.
149
3.1
Control cards to create initial master file.
169
5.1
Request for computer time and services.
173
5.2
Completed computer time request sheet.
174
5.3
Enforcement management system using four devices.
175
5.4
Enforcement management system using three devices.
176
5.5
Cataloging linked programs.
178
5.6
Execute IBM 360 DOS EMS version from catalogued programs.
180
5.7
Execute EMS from 360 OS catalogued programs.
181
5.8
Compile, deck, link, execute.
182
5.9
Execute Enforcement Management System from object decks.
183
6.1
Data card layout - letter card.
185
6.2
Data card layout - personnel schedule card.
186
Table
3.6
Personnel table. 158
Agency table. 160
Action table. 161
Section table. 163
Results table. 164
Agency table. 165
Letter Table. 167
3.1
3.2
3.3
3.4
. 3.5
3. 7
x
-------
1.0
MANAGEMENT GUIDE
The Enforcement Management System provides an organized methodology
for use by state and local air pollution agencies to control enforcement
activities.
Modern information processing techniques have been applied to
this area, including mechanized processing of enforcement data which uti-
lizes electronic computers.
The system emphasizes management control of .
the enforcement function, and establishes standardized methods of handling
data.
It produces a variety of reports and summaries to meet the needs
of various agency staff members.
Installation of this system in an air
pollution agency should improve the efficiency of the enforcement function,
and greatly increase management's ability to control this operation.
In
addition, the system provides greatly improved access to information which
has been gathered over a period of time so that this information can be
made available quickly for a number of purposes including external reporting
requirements.
All members of the staff should benefit from the installation of the
Enforcement Management System:
. Agency management will obtain improved operational control over the
enforcement function. Control is effected through the monitoring
of summary reports which are produced on a periodic basis. Reports
summarize actions that have been completed and indicate any scheduled
actions which have not been performed.
. Engineers, inspectors, and other staff members will have better access
to specific source records relating to individual establishments.
Details of agency interaction with those sources and details con-
cerning the specifics of the source itself are made available in a
form substantially improved over typical agency operation.
1
-------
Advantages to the heads of individual sections, such as Engineering
and Inspection, are as follows:
. Scheduled actions and ~onsequent workloads are highly visible
to the section head through the schedule reports. The section
head can evaluate the upcoming workload in terms of available
personnel and schedule changes in routine activities based on this
information.
. The system provides basic information for the evaluation of per-
sonnel through the summaries of actions that have been performed.
. Access to specific details of agency interaction with pollution
sources is greatly improved and the availability of such source
data should save the section head substantial time.
. The need to perform clerical work by technical and professional
personnel is reduced. Clerical personnel will be relieved of
the preparation of routine letters through the system's ability
to prepare automatically certain standardized letters to sources.
. The necessity to maintain a file to indicate when future actions
such as review and inspections should be performed is eliminated.
. Source data is made readily available in centralized locations so
that preparation for interaction with the source is minimized.
The system is available in three levels of activity for different
sized agencies.
Basically, all three systems are similar in that they
emphasize the preparation and handling of similar reports and forms.
The
first level (level 1) is entirely manual and does not require the use of
computing equipment.
It provides many of the' benefits of the system for
a minimum expenditure of time and resources.
The Standard Computerized
System (level 2) requires the use of a small-to-medium capacity general
purpose computer.
It does substantially more than the manual system and
provides additional reports beyond the capabilities of the manual system.
The Advanced Computerized System, an extension of the level 2 system, pro-
vides a measure of automatic action scheduling.
It is ~ompletely compatible
2
-------
with the level 2 system and the transition to the advanced system can be
made with minimum difficulty.
The basic outputs produced by the computerized versions of the system
are listed below.
Detailed explanations
of the individual outputs are
included in Section 3.
The outputs are:
. Source Action Summary
. Overdue Action Report
. Geographic Locator
. Action Cards
. Source Registration Report
. Future Schedule Summary
. Standardized Agency Letters
. Edit and Update Report
The Enforcement Management System (computerized versions) is designed
to handle data from more than one agency.
Often, both local and state
agencies within the state interact with pollution sources.
In some
cases, agencies may have jurisdiction over certain types of sources but
must rely on larger state agencies for assistance in dealing with complex
sources.
In other cases, agencies may have a clear geographic jurisdiction
but must follow the same general regulations.
Each source can be coded
to indicate the agency which has jurisdiction.
Reports prepared by the
system segregate source data by agency, and can be readily separated for
distribution to a number of separate agencies.
Utilizing the system's capabilities, a single agency could operate
the Enforcement Management System for a number of agencies in a given
geographic area.
Some of the possibilities are indicated in the attached
diagrams, Figure 1.1, and 1.2.
3
-------
~
~
Reports
Registration
Activity
Registration
Activi ty .
Sources
I Sources I
Figure 1.1
-Data collection flcr-~.
4
-------
~
~
Action
Info
Ac t ion
Info
. Abatement
Activi.ty
Abatement
Activity
Sources
Sources
Figure
_1.2
Data flow, abatement actions.
5
-------
The Enforcement Management System has been developed for u~e by
state and local air pollution agencies.
The system utilizes general
principles and procedures which may also be of use to other agencies
concerned with the environment.
In particular, state agencies con-
cerned with water and with solid waste may find the system of value.
The concept of the action card interacting with the data base to enable
the system to produce specially tailored schedules and summaries of
operational activities is applicable to agencies of many types.
Should such agencies develop an interest in the system, we re-
commend careful study of the agency requirements and of the system itself
before action is taken.
Modifications may be necessary to meet local
needs.
If this course is taken, contact should be maintained with the
Office of Air Programs, in order to learn of changes and experience that
may be available from other similar agencies.
In addition, such ex-
perience as may be gained by each agency should be available for use of
others at the state and local level.
6
-------
2.0
SYSTEM DESCRIPTION
The term "Enforcement Management System" as used in this section
refers to all three levels of the system:
manual, standard computerized,
and advanced computerized.
Specific details of these levels are found in
the next sections.
The Enforcement Management System sChedules, tracks, monitors, and
records a control agency's interactions with a pollution source.
The
system can be viewed as cyclical in nature, in that an agency's actions
in relation to a particular source occur repeatedly over a length of time,
one step leading to the next.
The.system tracks and monitors these steps,
updating various files, schedules, and reports.
The output produced by the system is as follows:
Permit Letters, Registration Certificates and other orders and notices.
These notices are produced automatically by the system when the results.
of an action call for such a letter or notice to be sent.
These notices
are printed on continuous forms on the computer, and can have the
agency's letterhead preprinted on the form.
Action Card.
These cards describe a single. action to be performed.
They are prepared by the computer system, with key information printed
across the top of the card.
The agency staff member who performs the
action fills in the card after the action is complete.
This is done by
checking the proper preprinted spaces, and writing in any needed comments.
The card is then returned to the system, which records the results of the
action in the data base (the new information havi~g been keypunched).
The
7
-------
system may produce a variety of new entries on the various reports
.and a new action card, depending on the specifics of the information
fed back to the system.
Future Schedule Summary.
This report lists actions scheduled for the
future.
Separate reports are prepared for individual staff members,
and for agency sections.
Overdue Action Reports.
This report lists those actions which were
not completed by the source or agency in the scheduled time.
Action Summary.
This report lists all performed actions, with the
reported results.
The list is categorized by type of actions.
Geographic Locator.
This report lists all sources that are being
processed by the system in two sequences:
by grid coordinates and by
city and street address.
E~ch new location shows all sources in the
system.
Source Action Summary.
This report shows past and scheduled actions
relating to each source.
The summary report contains results, staff
comments, and other data relating to the actions, and provides a history
of agency interactions with the source.
Source Registration Printout.
This report tists data regarding the
pollution source (including generalized company data), and data about
specific emission points.
Taken together, these products comprise a means for an agency to control
its enforcement actions.
The system, which is depicted schematically in
Figure 2.1, is designed around and depends on the action card concept.
This
8
-------
SOURCE
REGISTRATION
\D
ENFORCEMENT
SYSTEM
SOURCE
ACTION
SUMMARY
ACTION
CARD
SCHEDULE
FOR EACH
INSPECTOR
FIGURE
NEW DATA
ADDED BY
2 ;.1.
ENFORCEMENT
SYSTEM
ACTIVITY
SCHEDULE
WITH NEXT
STEP
SOURCE
ACTION
SUMMARY
Enforcement system schematic) showing
system monitoring of enforcement activities.
ACTION CARD
FOR NEXT
ST P
RESULTS
OF
AGENCY
ACTIONS
-------
illustration shows a single cycle in the processing.
An action (in this
case, registration) activates the system.
The system produces a number of
reports and a new action card, which describes the next step and includes
the assignment of the action to a staff member.
When the action is completed,
the action card is returned to the system.
Annotated on the card are the
action results and the next indicated step.
In the advanced version of the
system, many actions are assigned automatically.
The system prepares a
new action card for the next step and produces additional reports, which
include the data regarding the completed actions and the new actions.
In more detail, a sequence of "actions" with a specific source might
begin with the receipt of a complaint.
The staff reviews the geographic
locator to see if the source is known to the agency.
An inspection is
scheduled to verify the complaint.
The system produces an action card for
the planned inspection, and lists the inspection on the automatically pre-
pared staff schedules.
Complaint
Received
Action
Card
Inspection
Scheduled
System
Staff
Schedule
10
-------
During the inspection a pollution source is discovered.
Reference to
the geographic locator or to the source registration printout shows that
the source is not currently known. to the agency.
Basic data about the
source is fed to the system and a date is scheduled for the expected re-
ceipt of the completed registration.
The first action card is returned
to the system with the results of the inspection and the next step indi-
cated.
The system produces a "registration requested" letter to the
source,
a new action card and staff schedule, and lists the completed
action on the source action summary.
Action
Results
Letter
to
Source
Staff
Schedule
Basic
Data
About
Source
System
Action
Card
Source Actio
Summary
A delay is encountered and the registration date is rescheduled.
The
"non-receipt" of the registration causes an entry on the overdue action
report.
When the registration receipt date is rescheduled, the system pre-
pares new printouts, reflecting the status of the action.
The new staff
schedules reflect the revisions.
11
-------
Systen:
Source
Action
Summary Shows
elay
No Action
Results
Followup
Letter to
Source Card
Action
Card With
New Data
The registration form is finally received and a review of the reg-
istration
information is scheduled.
The action card is returned to
the system with the review assignment date indicated, and a new action
card is produced for the engineer who will perform the review.
Data from
the registration form are entered onto the master file, and the system
produces a source registration report and updated schedules.
The new
schedules include the new "next action", as well as other new actions entered
at that time.
Regis-
tration
Data
Action
System
Card
Source
Action
Summary
Review
Scheduled
Schedule
Showing R~gis
Review.
Source
Registration
Report.
12
-------
The review of the source information is finished, a temporary permit is
issued if the source is not in,compliance and a review with the source per-
sonnel is scheduled to establish an abatement plan.
Temp.
Permit
to
~ Source
Scheduled
Receipt of
Plan
Source Action
Summary
Schedule
Receipt of
Abatement Plan
I System
. Action
Card
The compliance schedule is established and the various steps or mile-
stones for monitoring the plan are entered and scheduled.
These schedules
may extend over a period of months or several years into the future.
The
system will keep track of these scheduled actions unti~ their scheduled
performance time passes.
If the action cards are not returned at the scheduled
time, an entry'will appear on the overdue action report.
Plan
Miles tone
Actions
System
Action
Cards
Future
Schedules
13
-------
At every milestone date that has been entered, the system checks to
see if the indicated action has been performed, and records the actions
that have been accomplished.
Action
Summaries
~
,./
Action
Results
System
It should be noted
that the system features which provide for the
entry of a number of future actions ideally fit the requirements of a com-
pliance schedule
negotiated between a local agency and a specific pollution
source.
Once the s'chedule has been agreed upon, the various steps can be
entered into the system with the anticipated date of accomplishment indi-
cated for each of the steps.
The system will list each action on the
various reports and summaries and produce action cards for each step.
The various staff schedules that are printed will remind individual staff
members of the dates and actions that are required.
If the specific mile-
stones are not accomplished on the dates indicated,the actions will be listed
on the overdue action report.
If changes are required in the schedule or if
other modifications to the compliance plan are indicated~the new information
can be entered by returning the appropriate action card to the system.
14
-------
Modifications will be immediat~ly reflected in the new reports from sum-
maries which are generated.
If the various actions indicated in the com-
pliance schedule are completed on time, the action card is returned with
the new information added.
The system then records these actions as com-
pleted.
At any point staff members can determine the status of the compliance
plan for a specific source by reviewing the source action summary for that
source.
15
-------
3.0
STANDARD COMPUTERIZED SYSTEM
This section describes the Standard Computerized System which we
recommend for use by agencies of all sizes.
Larger agencies who -will
eventually want to use the Advanced Computerized System with its
scheduling features should start off with the Standard System and move up.
The programs are completely compatible and the data records and files that
are maintained by the system can be used in the Advanced System without
conversion.
Should it be necessary to delay installation of this system,
work can be started with the Manual System described in Section 5 of this
report.
The following sections describe the details of the system.
Section 3.1 describes the requirements for a project leader and
data bank coordinator.
Section 3.2 describes the operation of the system from the
standpoint of the computer analyst.
Section 3.3 describes the system operation, including sample forms.
Section 3.4 discusses input forms used in the system.
Section 3.5 provides actual samples of output forms.
Section 3.6 describes the files which must be maintained at
the data bank coordinator's station.
Section 3.7 indicates steps that must be taken to start up the
system.
Section 3.8 indicates the resources required to start and
operate the system.
In addition, the Appendix to this report includes specific computer
details of the system design.
The Appendix consists of keypunch instructions
for the various forms, data record layouts of the master file, JCL (job
control language) printout for operation under both Disk Operating System
16
-------
(DOS) and Operating System (OS), and layouts of specific card formats
such as agency letter formats, schedule card layouts and personnel card
layouts, system and program narratives, and program maintenance procedures.
3.1
Project Leader and Data Bank Coordinator
For most agencies, two individuals should be designated to direct
the system activities within the agency.
The data bank coordinator (DBC)
should be full-time.
The other, the project leader, would act only in an
advisory capacity but would serve to direct the efforts of the data bank
coordinator in the operation of the system.
The project leader should be an experienced management official in
the agency, perhaps the Assistant Director or similar individual.
He
should be capable of working with the section leaders in the agency and
should understand their technical problems.
He will be the guiding force
behind the installation of the Enforcement Management System and should be
in a position to negotiate with other agencies who may desire to implement
the system using the multi-agency features.
He need not be directly ac-
quainted with computer procedures, as necessary program maintenance and other
related functions should be performed by someone who is directly associated
with the computer installation.
The project leader's functions are:
o
Oversee the operation of the system
o
Coordinate difficulties which may arise in system operation
o
Follow up on management reports from the system, including pre-
sentation of these reports to others
o
Provide and promote vigorous management involvement in the system.
The position of data bank coordinator is highly important to the success
of the system installation.
For all but the very small agencies, we recommend
that this position be full-time.
However, this is not a net addition to the
staff, since some of the system functions that are being performed by the
17
-------
coordinator replace existing functions that would have to be performed in
any case.
The coordinator may be chosen from existing agency personnel, or
should be experienced with air 'pollution control agency procedures.
He or
she should be experienced in dealing with people at all levels and have been
exposed to computerized systems of one type or another.
The exact functions of the data bank coordinator will vary with agency
size and practice.
In a small agency, the coordinator may do other tasks
including maintenance of certain files related to the system.
However, it
is necessary not to burden the data bank coordinator with tasks which will
detract from his ability to keep the system functioning.
Specific functions
are as follows:
o
Provide training for agency staff members who will participate
in system operation.
o Maintain various files and computer printouts for use by staff
members.
o
Monitor and maintain the flow of data to and from the computer
installation and to and from the various staff sections.
o Monitor
system.
o Provide
use of the information and reports generated by the
assistance for filling out the various entry forms by
staff members.
This activity is particularly important in the
preparation of action cards and manual action cards.
o
Review workloads with section heads based on the future
schedule summaries.
Such review with the various section
heads should provide the staff members with the ability to make
better decisions regarding their utilization of technical person-
nel.
In addition, reviews will provide the section heads with
18
-------
better information regarding the capabilities that the
system offers them in the management of their sections.
o
Monitor the system's automatic scheduling features for the
advanced level of the system.
o
Release standarized letters, permits, etc. produced by the
system to sources, usually through the mail.
The DBC
checks the outgoing letters to ensure that the originator
requested the correct standardized letter for the particular
situation.
If the amount of standard material being re-
leased becomes voluminous, it may be necessary to require
the staff originator to check to see that the material is
being sent to the source he originally intended.
Then the DBC
would be responsible. for checking to see that the staff
member had concurred (through signature or initials) prior to
mailing the material.
19
-------
3.2
Computer System Description
Tne computer segment of the Enforcement Management System accepts,
updates, and summarizes information regarding sources of air pollution
and emphasizes the enforcement function, its control and management.
The
Computer Processing Schematic, Figure 3.1, identifies the various aspects
of computer processing that the system will undertake.
The first run, the update run, accepts as input the old master file,
which is maintained on magnetic tape or disk.
This file was initiated
during startup and contains both action data regarding individual emission
sources and registration information which has been collected.
Additional
input consists of action cards being returned to the system with additional
data keypunched from handwritten comments on the cards themselves, new source
data, and a deck of miscellaneous change data (changes and deletions to
current master file) collected by the agency.
These two decks of cards are
put on tape and then sorted and matched against the master file.
A control
card and a personnel card file are also used as input.
The information on the
master file is updated and new data are added reflecting the new and changed
information.
There is also an option to delete existing information.
As
part of the update process an edit and error list is printed which indicates
all changes made to the file and reports errors in the input data.
Output
from the run is an updated master magnetic tape which is used for further pro-
cessing;
therefore e~ch processing cycle produces a new master tape.
It is
recommended that agencies retain a number of generations of this tape for
backup purposes in case processing errors occur.
The normal processing cycle would next include an extract run which pulls
20
-------
!action ca~c.s.1
""J"
misce11aneou
data
first sort.
sort
transaction
file
future
schedu!e
action
su=ery
,
update
run
extract
run
'.
second
sort
-,
f
.~
~_deck - ... J
. r--:J
:i new
I fiction
L-.s..ws
Figure 3.1.
Computer processing schematic.
21
-------
data from the master file for the various reports which will be printed.
In some cases, information from one record of the master file may be ex-
tracted a number of times for. different reports.
Each extracted record
will have a fairly lengthy
sort key which will enable the system to sort
records for each report together.
The sort will also group records by agency
in the proper sequence for each of the reports as well as for new action cards
to be sorted.
The output from the extract run is a magnetic tape of ex-
tracted data.
This tape is then processed by a standard IBM 360 sort.
Modifications
for sorts available from other producers of computer equipment will be
relatively easy to make since the sort key will consist of several fields
arranged continuously.
The sort produces a magnetic tape with the records
in appropriate sequence.
This tape is the input to the print run.
If registrations, permits, letters, etc., are to be printed, a
special deck of cards is entered, reflecting various prewritten or "canned"
letters which are to be sent directly to various sources.
These letters
are designed to be printed by the computer on continuous forms preprinted
with the control agency's letterhead.
At the bottom of Figure 3.1 from left
to right, the first output from the print run is the letters and certificates
just discussed.
The next product
is the geographic locator which is
printed in two versions:
one in sequence by grid coordinates, and the other
in sequence by city and street.
The next report is the overdue action report
which, like the geographic locator, is printed on plain computer paper.
The
future schedule summary is a basic report which is distributed to all users
of the system and indicates actions that are scheduled for the coming week,
22
-------
as well as actions scheduled further in the future.
The action summary
report is a summarization of actions which have occurred in the past,
arranged for management review;
this report indicates the results of
the action when it has been reported.
The source action summary is
classified by individual source, and includes all actions that have been
recorded relating to each source, including those planned for the future.
These actions are grouped by individual emission point.
For example, an
individual manufacturing plant may have both a boiler and process emission.
These are treated separately and actions relating to each are grouped to-
gether.
For actions which relate to the entire plant, such as generalized
complaints or letters, a general category identified as emission point 000
is established and general actions are grouped on the, listing at that point.
The final output from the print run is the new action cards.
These have to
be either interpreted or printed across the top in some way
(such as by
use of a keypunch machine with the printing option installed).
The cards
themselves are preprinted.
A sample action card is shown in Section 3.4 ,
Figure 3.4.
Certain actions common to most agencies are indicated in the
preprinted
P9rtion of the card.
Agencies may perform different actions, or
call similar actions by different titles.
It is anticipated that each
agency will want to prepare its own list, perhaps working with a representa-
tive of the Office of Air Programs, to develop its own format.
The system
is completely flexible and is not limited to the actions that are indicated
in the samples.
One action card design will allow spacing for printing
across the top of the card using standard interpreter spacing (60 characters
per line), and another using standard keypunch spacing (80 characters per line).
Either design may be chosen.
23
-------
A few general notes that will relate to several reports are appropriate.
When "comments" are to be entered, the staff members can enter up to 495
characters, and the keypunch operator will punch additional cards to enter the
data.
These data will be keypunched into additional cards by the keypunch
operator and retained by the system on the master file.
The general file sequence logic will depend on a source number which
will be random in nature and will be assigned consecutively by agencies.
If
two or more agencies are being run at one center, they may duplicate source
numbers, since an agency code is included in the record.
Included in the sequence logic will be a three-digit emission point number.
Agency actions are numbered individually.
The person entering a new action card for a particular source may not
have the action summary report before him, and so may not know the next sequ~n~
tial action number.
He can simply enter "99" as an action number, and the
system will convert the "99" to the proper sequential action number.
When an action is against the entire source, the system will create an
emission point numbered 000.
Therefore, an emission point should never be
assigned 000, as this will be provided when a new action card enters the system
with emission point 000, and action number 01.
This emission point is really
a "catchall" for complaints and other actions which apply to the entire source.
The phrase "entire source" is automatically entered in the description field
when this record is printed on the various reports.
24
-------
3.3
Operation of the System
In the general operation of the Enforcement Management Systemt it is
assumed that the agency views pollution emission sources as being-divisible
into specific emission points.
This is the normal philosophy of enforcement
operation.
Basic records maintained by the Enforcement Management System
consist of general information about a sourcet and additional information
about the specific emission points that exist within a source.
A source
number field is provided and a subfield is provided for emission point numbers.
The "permit unit" concept utilized by the individual agency has a-signi-
ficant effect on the operation of the system.
Local practice varies in the
assignment of registration numbers and permits to specific emission points.
In some casest a registration number applies to the entire sourcet but
specific permits are issued to individual emission points.
OccasionallYt
agencies have decided to assign permits to control devices separately from
the processes to which they may be attached.
The system handles this as follows:
A source number is assigned per-
manently to each source.
Each emission point not only has an emission point
numbert but can also be assigned a registration number and a permit number
which are changeable at any time.
Both the registration number and the
permit number have been made large (12 digits) so that any manner of coding
may be incorporated.
Some agencies may wish to include the source number as the first digits
of the registration number or the permit number.
In other cases where sepa-
rate numbers are desired for the air pollution control device and the process
itselft the emission point registration number could be used for the process
and the permit number field for the device.
25
-------
Discussion in this documentation assumes the assignment of emission
point numbers by like device o~ emission type.
Registration numbers are
assumed to be assigned by the process of simply filing a description with
the agency.
Space has been provided for a registration number which may
be different for each emission point.
Because practice varies substantially
from one agency to another, it is suggested that the data bank coordinator
maintain control of the numbering process and maintain a manual ledger of
number assignments.
The source number is of particular significance to
the system operation and this may be cross-referenced to an alphabetical
list, although in most cases those desiring to find the source number of
a particular source can do so with the geographic locator.
Normal interaction of an agency with a specific source follows the
steps which are indicated in the attached Figure 3.2.
Systems actions on the
flow chart are shown in the blocks with rounded ends.
For example,
"Issue permit, schedule reinspect ion" indicates a system action.
26
-------
Basic RERistration Form
Rec'd-From Source
System Schedules
Engr. Review
4"
Complete File
In Enforcement Mgmt
System
Review of Source
EQi$si~n Data By
Engr. Group
Issue Pennit If
Required, Update
File. Prepare Reports,
and Schedule Inspectio
No
Modifications
Needed, Review
With Source
t 1 es p a
",'ite: New Data,
Inspections Scheduled
at Various Installation
l' .
Plan Rec'd [.
Approved By
Engineering
Syste~ IS$~es Compliance
Letter, Schedules Receipt
of !,ew Plan
Issue Temporary
Permit, Schedule
Source Inspection
Inspect
Source to
Ensure Co~pliance.
Conduct Tests as Needed.
Issue Permit,
Schedule Reinspection
Modifications
Needed, Review
With Source
Permit Rec'd
By Source
System Issues Cornplianc
Letter, Schedules
Reinspection
Reschedule Activities,
Monitor Additional
Construction
Periodic Reinspection,
Testing,
or Review of Citizen
Complaints
Prepa~e Periodic"
Reports Based
on Schedule
Resur.ey of Source
Figure 3.2.
System actions.
27
-------
3.4
Input Forms
rnput forms for the Enforcement Management System consist of four
keypunchable documents as follows:
o
Source Data Form
o
Emission Point Entry Form
o
Action Card (machine-prepared)
o
Special Action Card (hand-prepared)
These forms are prepared by staff personnel and keypunched onto standard
80-column punched cards for entry into the Enforcement Management
System.
The data elements and the use of each form are as described below:
Source Data Form - This form is the basic entry mechanism for general
information about the company, or other emission source.
A copy of this form
is included in this report as Figure 3.3 .
The following data elements are
included on this form:
Agency Code - This is a number which is preprinted on the form itself.
This data field is used when the system is operated for a number of
agencies or locations.
Numbering in the various agencies may follow
any numeric sequence.
If it is desired to separate reports and other
data by offices of a particular agency, sources associated with the
individual office should receive an agency code number different from
that of the central office.
For example, if a system were being operated
for two agencies, the first might be numbered 010 and the second, 020.
The offices of the first agency would then be 011, 012, etc;
those of
the second agency would be 021, 022, etc.
County Code - Each county in a particular state should be assigned a
number and this number should be used in these data.
Four digits are
28
-------
SOURCE DATA ENTRY FORM
SOURCE DATA FORM
I . . I
Agency Code
County Code
.
Source No.
...J:.....
Card Code
Coordinates
UTN: Zone (if used) I
I I
EW
NS
Source Name
Street
, ,
Number
Name
Time Factor I
Update Code~'
N, C, or D
Card Code
2
-
,!
Ci'ty
I I
. ,
State
Zip Code
Area Code
Telephone
Contact
SIC Code
Agency
Inspector No.
, I
Agency
Engineer No.
Update Code L-'
N, C, or D
Card Code ~
I . I I . I
Source Description
Card Code ~,
L..-'
Line Code (Leave blank except "C")
Upda te Code t
N, C, or D
Comments:
Figure 3. 3.
Source data entry form, source data form.
29
-------
provided, although fewer digits may be used.
Source Number - This is a sequential number assigned to a source
which is entered during the initial entry of the source data.
A book
should be maintained by the data bank coordinator to indicate the source
numbering.
The source number itself has no particular significance and
may be duplicated when utilized by several agencies.
The source number
assignment book is simply a list of numbers and companies used to keep
track of the last number assigned.
Location of specific source data is
by source number and should it not be known, the geographic locator can
be consulted to determine the source number.
Card Code - This field is preprinted to assist in the keypunching process.
Coordinates - Three fields are associated with the assignment of coor-
dinates to a specific source.
These are UTM (Universal Transverse
Mercator) Zone, the East-West Coordinate, and the North-South Coordinate.
It is strongly recommended that coordinates be assigned to the various
sources.
However, it is possible to leave these fields blank without
interfering with the operation of the system.
"Zoning" these sources
allows locating sources in specific areas.
The ability to utilize the
data that have been collected for modeling and simulation purposes depends
on this zoning.
Generally speaking, the UTM system is preferred.
In
this case, a zone indication is desirable unless the agency's jurisdic-
tion is entirely contained in one UTM zone.
If a longitude-latitude
system is used, the zone field can be left blank.
Each agency should
decide what coordinate system it wishes to use and stick to it.
It is
also essential to decide on the positioning of the digits.
For example,
30
-------
under UTM zoning, usually five digits are assigned.
These should be
located to the right of the coordinate field on the form itself and
the keypunch instructions,modified to indicate only the five digits.
Longitude and latitude generally only consist of six digits.'
Source Name - Show the company or other name of the source at this
location.
If the first word on the official title is "The" or a similar
phrase, omit this and begin with the first significant word such as Acme
Co., not The Acme Co.
Street - Show the number and name at the location of the air pollutant
emissions.
Time Factor - This data'element is usable only by the advanced computerized
system;
however, it is recommended that it be filled in by agencies
using the standardized computerized system so that they may easily pro-
gress to the more advanced system.
The advanced system utilizes this
time factor in scheduling.
The factor is a three-digit field indicating
usual amount of time encountered in dealing with this source.
This in-
volves an estimate of factors such as complexity, of operation, distance
from agency office and so on.
I
If 1.00 is entered, it is an average
source.
2.00 indicates a difficult source, and .50 indicates a source
of less than average difficulty.
If no entry is made; the system assigns
1.00.
Update Code - The letters N, C, or D are entered here depending on
whether the source is new, to be changed, or to be deleted.
In order
for the entry to pass the various computer edits, this field must be
properly filled in.
For example, if a change is intended but an N is
entered, the edit routines will reject the cards being entered into the
system.
31
-------
City - This field is used for the city or postal address at which the
source is located.
State - The two-digit postal abbreviation for the state is entered here.
Zip Code - This field is for the six-digit, numeric zip code of the ad-
dress indicated.
Telephone - Show the complete telephone number at the location.
The
first three digits are the Area Code.
Contact - Indicate the responsible official at that location with whom
the agency normally has contact or who normally handles pollution-re-
lated matters.
This name will appear on letters~ permits~ and so forth
which are generated by the system.
SIC Code - This code is the standard industrial classification code for
the type of installation being considered.
It should be entered if known.
Agency Inspector Number - This number is assigned to a staff member of
the air pollution agency who normally performs inspections at this instal-
lation.
The first digit may be a letter which indicates the section to
which the staff member reports.
The second two digits are numeric and
are assigned consecutively to staff members within that section.
Agency Engineer Number -
This is the same as the agency inspector field
except that it refers to the engineer who normally will analyze data
from this particular installation.
Update Code
This field is handled as indicated as the previous update
code field.
Source Description - This is a brief description of the type of instal-
lation-at this address~ such as:
petroleum refinery, electric utility
or heating plant.
32
-------
Line Code - This field is associated with the comments to be entered
below.
Please note that it is left blank except when a change is de-
sired in existing comments on the record.
In this case, sho~ the line
number printed on the form and enter this number.
Comments - Comments concerning the emission source can be entered here.
This might be a description beyond that included in the source description
field, or might pertain to specific items in the relationship between
the agency and the source.
Up to 495 characters or comments can be
entered.
Emission Point Entry Form - ,County Code, Source Number and Agency Code must
be the same as the source data form entry for which this emission point is
being made.
An emission point entry should be made for every point within a
particular source which is capable of emitting pollutants.
See Figure 3.3A.
Emission Point Number -
Number the emission point within a particular
source consecutively starting with 001 and continuing until all the
points are numbered.
Description - Indicate a brief description of the specific emission
points, such as grey iron cupola, nitric acid still, or oil-fired
boiler.
If there are many similar devices in a given source, word the
description so that the specific process being referred to can be un-
ambiguously identified, using manufacturers' serial numbers or numbers
assigned by the source.
Control Device - This field is for identification of any air pollutant
device associated with this emission point, such as a bag house, pre-
cipitator, fabric filter, scrubbers, cyclones, etc.
33
-------
SOURCE DATA ENTRY FORM
EMISSION POINT ENTRY FORM
I I
Agency Code
I .
County Code
. ,
Source No. -
~
Card Code
,
Emission
Point No.
Description
Control Device
-
Pollutants
Upda te Code- L-.J
N, C, or D
~
Card Code
~
Line Code
(Lv Blank
Except C)
Comments
" !.
Registration Number
I I
Permit Number
Update Code '----l
N, C, or D
Figure 3.3A. Source data entry form,
Emission point entry form.
34
-------
Pollutants - This field is used to identify qualitatively the pol-
lutants that are emitted from this emission point.
Update Code - The same as'that discussed under the Source Data Form.
Comments - Additional comments may be entered here regarding specific
points of description which may be required to describe the emission
point.
Any item of particular note may be entered.
Up to '495 characters
may be entered.
Note, however, that there is also a comments field on
the action card.
Specific comments related to agency actions concerning
this emission point should be entered there.
Line Code - This field should be blank unless already existing com-
ments from the file are being' modified.
In that case, the line number
of the comments being changed should be entered and the entire line
repeated.
Registration Number - Show the registration number assigned to this emis-
sian point.
Note that this number will appear on any letters going to
the source.
Permit Number -
Show a permit number that has been assigned to this
emission point.
The permit number is also printed on letters going to
a specific source.
Update Code - Update code is the same as that which has been previously
discussed.
Action Card
This 80-column card is prepunched with source - and point - identifying data
by the system so that this data need not be entered for keypunching a second
time.
This card is designed to be filled in by the person performing the action
35
-------
indicated.
In certain cases, items related to the next action may be filled
in by ? supervisor or coordinator.
Usually, all or most of the data will be
entered by the person whose name appears in the staff name field. See Fig. 3.4.
Action Results - This section of the card is used to indicate the status
of the action indicated.
If the staff member determines that his
activities have completed the agency's handling of this activity, he
circles the "1" next to the "No Further Action" printing.
If further
activity is indicated, he circles the "2" next to "Follow Next Step,"
and indicates the next step in the next action field, which is dis-
cussed below.
If the activity has been rescheduled, this is indicated
by circling the "3" next to "Reschedule Action" and the new date entered
in the next action date field.
"Data Not Recd." is used when the acti-
vity involved the receipt of. information which did not arrive from the
source.
Note that local agencies may add other action results to the
card, or may modify the wording of the individual items.
Hours Taken - This is the number of hours that were taken by agency
staff to complete this action.
Zero hours are shown if no actual
activity was performed, or if the action is rescheduled.
Next Action -
There are eight actions indicated here.
These may vary
from agency to agency based on local regulations and practices.
The
actions selected are typical of normal agency activities.
It should
be noted that each agency may vary the names of the actions, or the
number of actions to be included.
Date - This is the date by which the action should be completed.
Person - This is the code number of the staff member who will complete
the next action.
In some cases the person's name may be entered and
the data bank coordinator will supply the code.
No entry need be made
if the same staff member will perform the next ~ction.
36
-------
t-t-
Zz
~I &.1.1 ~
:E:iji&.l.l
1.\.J&..It-
c.:'IcrI~
a::cC~
C:Z:~
LA..C
~:E
Z
OQ
- a:
t-C
~c.:'I
IACTION
..l'J~XT ACTION
1 INSPECTION
STAFF NAME
SEND I"ETT{::.B-
1 REQUEST REGiS. e REGIS. APPROVAL
1 NO FURTHER ACTION 2 REGISTRATION DATE 2 REQUEST PLAN
2 FOllOW NEXT STEP :3 PLAN SUBMISSION PERSON 3 PERMIT APPLIC.
3 RESCHEDULE ACTION 4 REViElY WITH SO~RCE 4 ISSUE PERMIT
4 DATA NOT RECD 5 REGISTRATlQ~ nEVIEW HR. TO COMPLETE 5 155. CONDo PERMIT
HOURS TAKEN 6 PLAN REVIEW 6 APPEAR AT ASENCY
7 SOURCE TEST I NG 7 PLANNED VISIT
J rc 700"77
.___Lc~.-
I_NEXT ACTION
. 1 INSPECTION 6 AQ SURVEY
1 NO FURTHER ACTION
2 REGISTRATION
DATE'
SOURCE NAME
6 AQ SURVEY
COMMENTS:
I . l .
POINr ACT
.~:J I. :!:) .S~-~C~~~-
I- t- ACTIQ~LJit:.S_Uj,.~~.
Zz
r..I&.I.I:E
:E.r.u
1.S.I"",t-
c.:»c.D~
1".1: c: >i
Qz:cn
LA..C
~:E
'I;;:
eQ
- a:
t-c
c.:»u
C
COMMENTS:
2 FOLLOW NEXT STEP
3 PLAN SUbMISSION PE.RSON
~TAFF NAME
SEND LETTER
1 REQUEST REGIS. 0 REGIS. APPROVAL
---.--- --
2 REQUEST PLAN
3 PERMIT APPLIC.
4 ISSUE PERMIT
5 ISS. COND, PERMIT
6 APPEAR AT AGENCY
7 PLANNED VISIT
JTC 70C77
Figure 3.4 .
3 RESCHEDULE ACTION
4 ~EVIE'N YiliH SOURCE
4 DATA NOT RECD
HOURS TA.KEN
5 REGISIRAT.ION REVIEW
HRS 10 COMPLETE
G PLAU REVIEW
7 SOURCE TESTING
Action card.
keypunches.
Design at top is for installations with interpreting
The ~ower design is for 60-column interp~eters.
37
-------
Hburs to Complete - This is the estimated number of hours required to
complete the next action.
Send Letter - These are letters or certificates which are standardized
in format and routinely sent by the agency to various sources.
Eight
are shown on the sample card.
The number of letters or certificates
used by any particular agency and their text may be varied to suit local
practice.
Figures 3.11 through 3.18 show sample letters.
Each agency
may use a different set of letters, up to a total of 99 per agency.
For
practical purposes, however, only about 15 letter titles can be printed
on the action card.
Comments - The person completing the action should fill in any significant
comments in this portion of the card.
These comments will be keypunched
and entered into the system along with the action record.
They will appear
on the source action summary and elsewhere as appropriate.
Comments to be
written down should be helpful in analyzing the action that was taken and
what is expected of the subsequent action.
Up to 495 characters of data
may be entered.
Any unusual occurrences should also be recorded.
If the
new information relates to the emission point itself, however, the comments
should be entered on an Emission Point Entry Form so that they can be
associated with the emission point, not with the action.
Special Action Card -Data on the Special Action Card are the same as the mech-
anized card, except as indicated below.
See Figure 3.5.
The Special Action
Card is needed to supplement the Action Card.
It contains spaces to enter data
which is prepunched into the Action Card.
The Special Action Card is used to enter or to schedule the first action
38
-------
.- t-
.zz
.w 1M
$~~
-- ~4
. W l~ (!A
U IL'\ 1-
~ ~ft)
O~>
u.. Z tn
Z.~.
u.I~
Z"
OLai
-~
...~
Uu
-------
in what may be a series of actions. It is also used when a series of actions
relating to a particular source is entered at the same time as when a compli-
ance plan is drawn up. A separate sheet is required for each action in the
series.
It will atso substitute for a regular action card which has been lost
or destroyed.
Agency Code - Preprinted on the form.
County Code - The county code for the source must be entered so that the
record on the master file may be located.
Source Number
The source number is needed to locate the file on the
master record.
Emission Point Number - This field holds the emission point number for
the point relating to the particular action.
The special action card is
used to enter the first action in what may be a series of actions. In som~
cases, such as a complaint, the card can be used to enter a completed
action and a next action at the same time.
For example, a complaint and
the resultant air quality survey, which are two ~ctions, can both be
entered with one card.
In this case, the "next action" and the "next
action date" fields indicate the subsequent .action in the series.
Other-
wise these fields are left blank.
In this case, when the first action has
been completed, the actions and results are also filled in. . When a singler,'
.:A~'"
action is being entered, only the action number, action type, action date'Jr,"
and staff number fields are entered.
The estimated "hours to complete"
field refers to the second action if one is entered.
In this case, the
"send letter" to source number mayor may not be used depending upon whether
it is desired to send one of the standardized letters to the source.
The
special action card may also be used to modify an existing action on the
40
-------
master file by use of a "c" in the update code field.
The "c" or change
entry is normally used before the action is actually performed.
Normally
an "N" (new) is entered at that point.
Update code "D" is u'sed if an ac-
tion is to be deleted from the master file.
Other fields on the Special Action Card are the same as the action
card.
Note that the "Action Types" listed at the bottom are the entries
to be used in the "Action Type" field.
The "Action No." field is the
sequential action number.
41
-------
3.5
Output Reports
Shown on the pages follo~ing ~re sample output reports
from test
runs of the system.
Each report is described briefly.
At the erid of
the section
a number of filled in action cards (machine produced and
special) are shown to indicate typical entries that might lead to specific
printout data.
Overdue Action Report (Figure 3.6)
This report lists all actions which are overdue based on tneir
scheduled date.
Included in the report is the reason for an action being
overdue, e.g., information requested has not yet been received
so the
action can not be completed or the action card has not been returned
(action not accomplished or the card is lost).
For multiple agency use the report is prepared separately by agency.
Its principal use would be as a controlling report to:
a.
show which sources have not complied with an agency's request
for information
b.
indicate staff members who are over-scheduled
c.
prevent an action card from being misplaced
The report is under the control of the d'ata bank coordinator.
It
should be produced periodically.
Future Schedule Summary (Figures
3.7 and 3.8)
This report lists all actions which are scheduled in the future.
The
summary is subdivided into section and individual reports.
The section report compiles a summary of projected actions by calendar
42
-------
UVEtH1L[ Ar.TION 'UPIIRT
11121171
. .
.... . . .. . .... .. . . . .... .. . ... ... .. . .. . . ... . . ... . . . . . . . .. ...... . .. . . ... . .. .. ..... ... ...... .. . . . . . .... . . . . . . . . . . . . .. ....... . .. . ....... .'..
ENFf:RCEI'FNT /lhNAf.EMENT SYSTf"
AIK POLLUTION CGNTRUL AGtNCY
J!AGE
. . . . . 8.. . . . . . . . . . . . .'. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-"----..-.-..
~ T hFF f"EP.BE~
AND T I HI:
PlAN1\ED
hC Tl ON
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SULRCE NAt~E
liNe /lOI]I
.1'. 1'1 SI-'
INS"FCT(.R
It-JSP[CTICN
H. PIM(Ht.~,
INSPFCTliR
RFCISTPhTIU",
R. YCCCM
I NSI'EC T!1~
lUG I STRAT 1(;/\
A."'. P.CSTICK
INSf'f:CTOH
t(EGISTRATION
N.E. HI"'\jNE
ENGI'I£:[k
RI:VIH' W/SOUKCE
B. ~ROWN
INSPC:CTUP
REGIST. RF.VIt~
Figure 3. 6.
,
.
flMICCCK IkllNCUCER eOC65 10/20171 CARIJ NOT H[rUR~E:D C;1o
1531 LOCUST ST. GOO
"tiEl/l~ C T C7211 -- - .---
HA£JCCCK TRANDUCEH 00065 10130171 CAiW NOT RLTURNEO O:!
1531 LOCUST ST. C02
wHFL/\N cr C7211
Hl\PCCCK TRANDUClR 0()06~ m..lDll,>171 CIIRU NCT HE TURNEU. C3
1511 LOCUST ST. coe
WH[UN C1 cnll
Y(IKK fiNCH (.[NrkAL COCC5 lC/W/11 Ct.I-'U Nt:r Iq rURI,EO C2
2111 fINCH AV~ \oj CDI
~'Ak 1 HmU C 1 (,.&002
GOCDY!:AR fCSSt.GO LTD COCC9 lUJl171 u.~1.; NfJ1 kETl.R~[C 'J2
'\050 LAKI- 51-0"'" Blvn OOC
.\lflHTFrrW CT ObOO;!
WILCD PfllNT Cfl. CCC20 lC13J171 CflI
-------
FlJTUHE
SCHFCULE SU~~ARY
- .n -'-" --.".-.' .
.8[[[ ...... ~................................. .,-
PAGF
~
.j
11/71111
EN~URCE~ENT ~hNAGF~ENT
Alk rOLLUTICN CO~TRVL
S,(5TF~
AGENCY.
. ~....... .............. .... ................. ..... ..... ................... ............................... ....................... .....
ENGINEERI1';G
.SCHED.
DATE
. .... ... ................... ... ........ ..... ........... ........... [[[ ... ............
ACT.
~C.
)
rLAI\i\EC "CTlO'~
S ThH "'H~H F.R
SOURCl NAME
ANI) ACDRESS
SOURCE
f. PCINT
SOU~CE DESCRIPTION
POINT CFSCNIPTION
LAS T AC T!et<,
hN[ [liTE
12101111
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ., . . . . . . . . . . . . . . . . . . . . . . . . . .
O~
::J
.j:'-
.j:'-
PLhllj RfVIEW
N.r. nC\.;t-.1:
GRtU
COONOS.
~IDDLr-AlJf
-------
FLTURF.
SCIIEf'UL E
SlJIIII/lRY
.. ....... ........ .......... ................. .......... ....... ........ ..... ............................... .... ........... ............
11171111
ENFURC£"'FNT M~N/lGE"'ENT
hl~ POLLCTICN CONTRPL
SVS HM
AGL~CY
O/l(;E
N.E.
E!O~NE:
........ ..... ...... ......... ................... ........ ........... ........ .................................................. .........
. . .. . . . . . . . . . . . .>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
--__._SCHI:D. -
DATE
PLA~J'i[C
ACTICN
SOURCt NAI'E
ANr. AU1RF 5S
GRIU
CfJORDS.
SCURCE.
£., PCINT
SOURCE DESCRIPTION
PUINT OESr.RIPTIO~
LAST AtrIOf\
..."C r:~TF.
ACT.
f\C.
.. ....... .... ........... ... ... ........ ............ .... ...... ..... ........ ..... ..... .............. ...... ... .... .... ..... .............
12101/11 .
PLII!'i ~rVIH
~IOOL[nURV CGLL[C[
1 HLU£ HILLS AV
HARTFCKD NJ C912~
eCOb(,2 X
. 0048(;5
oeoei
ceo
COLLrr.F (JOPM t
I:f\TIRE srJt;~CE
lAH.
OTHR
O'lnC171
02
.. .-------.--.
~
VI
Fi"gure 3,8,
Future schedule summary prepared by computerized system.
.
-------
dates.
It contains the source location, emission point, previous action
against the source and its date, as well as the projected action and the
name of the staff member assigned to complete it.
The individual summary is similar to the section summary, except it
only lists actions to be performed by this individual and not the entire
section.
The section summary is distributed to agency and/or section manage-
ment.
Its main use is as a tool in the assignment of manpower, and for
management review of workloads.
The individual summary accompanies the individual's action cards.
It enables a staff member to review his upcoming schedule.
He could then
rearrange his trips 80 he would spend more time at a source and less time
traveling.
The source name and address serves to save valuable time for
the staff member by not having to reference any other report to find the
source address.
The production of these summaries is under the control of the data
bank coordinator.
Since this is such a valuable report and since the
entries are always changing, it probably would be required each cycle.
Geographic Locator (Figures
3.9 and 3.10)
This is a listing of all sources on the master file.
Two reports
are produced for each agency utilizing the system.
A locatqr by grid co-
ordinates lists sources by UTM gridding (or any consistent system of co-
ordinates).
A second locator l~sts sources by city and state.
Between these two locators, any complaint can be quickly verified to
see if the source is registered.
The grid coordinate locator can also be
46
-------
GFO~KAP~IC LOCATCR
...... ....... ..... ............... ................ ........................... .......................... .... .... ... ...... .............
11/71171
ENFuRCE~f:NT ~ANAG~~F~1 ~YSTE~
AI~ PULLUTILN £UNTKOL AGE~CY
PAGE
LOCATOR ~Y GRIU CUCPDI~6TFS
[[[ ......
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . e.- . . .
-------p ._. .-
. GR 10
CnrJRDINarr
SUURCE NAI'E
SGURCF ACC~F.SS
SOUKCE UESCRIPTION
POINT NO. A~C CFSCRIPTION
PCLLUTANf
TYPCS
SOLRCE
~U~ H I: R
... ......... .......................... ................ ........... ......... .... ... ...................... ...... ........... ............
000662 BY 004865 I-'J[;nL(f'UKY CIJLLEGC
lJTM 10 - "LlJl: HillS flV
-- -.-. .---. .._--. HA~TFOR[1 ~J (,>9123
o C6 lIW BY 048451: VORl< F I NCt' r.PIFRAL
UTI-' Zr. Z111 FINCH AVE W
HARTFORD CT C6002
+:-
'-J
-..-- .----- -- - .006210 I3Y OC3692 wlLcex PAINT to.
UH' n 15263 I'ETRr:I'QLE 6,V
UIXO/\ ~J ':'1123
OCb4~C p.Y 0l)ZZ11 wl1l TL PIG~[NT CORP
UTI' 15 35 OUCKEll:Y AV
WI'<;TFRN r-.J Of,QC 7
4118<)2 IIV 063<;12 IJh!lCr:CI< fl
INK MANUFACTUK~R
COI GAS .Vh TS
srz. ~C4
COC03
[L£CTRCNIC PARTS PRIlU.
000 ~NTIRl SOURCE
CO(,I,')
001 BUlLER
SU2 - PAlHIC.
003 ELECTRIC FLRNACE
HC - COl'i~ S .
-------
r;ror,i'API'IC LCC/lTfl{
11n1/11
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..8 . . . . . . . . . . . . . . . . '!' . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FNFIJI~cr "'1- N T t~MIM,H ,,/>, I ~ V S TF r-'
/IlK POLl~TION CO~TKUL AGlNCY
PIIGF
. .- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ". . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCATI.'R BY CITY, STHElT
GI{ ([)
CC(1RIJ INI\ IF
............. ........ ................. ... .... .... ..... ... .... .... .... .... ....... ............. ............ .... ..... ..... ... .~........
POL LU T A 'd
TYP[~
SCURCE Nfi~E
~fIIJPr:F Ar::Cl1f:SS
SUURCL DESCRIPIION
pn INT /I;(J. !It,[; [E')CR I PT IQ~
SOL"'.Cf
/>, U"', t\!:' R
. .8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
02&<'10 KY OC36Q2
UH' ?7
GCOb62 KY 0C4e~5
u T ~. 1 C
_... _u- --.--..- ..-.
~
00
OChlB8 HY 0484~~
UP'- 20
AY
---- --___~__n UP'
00&480 ~Y vOZZil
UTr- 1~
471Rq7 AY 063412
UT"- -10
---.---" -.- -'. ..-...
WILCCX PAINT CO.
I ') ., (, 3 ,.. [T R r! I' [LE /I V
01 )to/>, "JJ (.'11" I
~ I r. n L F rUin (I ~ LL E (i E
l-l'llJ~ HILL~ flV
H~'nrnPIJ ~,.J (.'1123
vnPK FINCH GF~~MI\~
2111 FINCH AVE W
HARTFGRO CT 06007
"'ILTLN SlfflM PLANT
31~Q W~lTE ST - -
HARTFnRD ~J 06002
WHITE PIG,..ENT CORP
35 RUCKELEv '.V
~[~T[RN ~J O~O~2
HARr:CCK TM/I~CUCER
15"1 LrCUST ST.
WHELAN CT 07L'11
~ATl~ UASE PAI~T "'A~Ur.
CO. PhINT "'IXFPS
COG2C
HC-PAPI
CCt' f URNhCt:
phI{T-~,rJ<'
CflLlf(iE IJCM~, LAn.
000 FNTIRE SCURCl
~ 0:-: 1
HIISPITAL
001 fU~L CO~BUSIION-GhS
SLL FIJII- /I~1t
C000~
NOT Kt\LhN YlT
"0";11
C01 SMOKE STACK
INK "'AM!FACTLREI~
001 GAS VATS
SOZ, HCI.
.OOCO 3
FLtCTRCNIC PARIS PROO.
000 fNTIRE SCU~r.[
():Je,hS
001 [IUIlER
SCZ - PM
-------
used to determine pollutant sources in a particular area which may be
causing air quality problems.
This report is under the direct control of the data bank coordinator.
Once the master file is created, there will be relatively few new sources
added, therefore these reports could be produced every 4 or 5 cycles.
Standardized Agency Letters, Certificates (Figure 3.11 through Figure 3.18)
The system produces standardized letters and other documents for
transmittal to sources.
The text is under control of the local agency,
and will reflect local practice and regulations.
The method used to
introduce particular textual material is described in the Appendix.
The letters are produced when an action card (either mechanized or
special) is submitted to the system with a "Send Letter" number circled.
The system responds by printing the letter with the source name and ad-
dress, contact, and other data at the top, and the standarized text as
the body.
A number of examples are shown in the following figures.
The letters may be printed on agency letterhead bond; by ordering
this paper with specifications appropriate to the computer printer used
at the local center.
Alternately, blank stock may be utilized and an agency
stamp used, to reduce costs.
In some cases, local situations may dictate that only the letter
title, plus .source name and address be printed.
For example, some local
computer centers may not accept the use of preprinted forms, such as
letterhead stock forms.
In this case, the letters must be prepared "off-
line", away from the computer.
This can be done in several ways.
The
standard letters can be multilithed, and the variable data typed in from
the computer printout.
49
-------
AIR POLLUTION ~NTROl AGENCY
- ---- _STATE OFFJCE BUJ~PLNG - -
301 E. 24TH STREET
CAPITAL CITY
12/01/71
MIDDLEBURY COLLEGE
1 RLUE HILLS AV
HARTFORD NJ 09123
. _.--' - ._--
- __-4"__' - .- ---- H - -
CO~TACT
J. JONES
SUBJECT
APPEAR AT AGENCY
COLLEGE
BOILER
SOURCE NO.
POINT NO.
REGIST. NO.
PERMIT NO.
00001
001
GENTLEtv'EN
A REVIE~ OF THE INFORMATION YOU HAVE SUBMITTED TO THIS AGENCY
INDICATES THAT A CONFERENCE BETWEEN A REPRESENTATIVE OF YOUR
FIRM AND THE AGENCY STAFF MEMBERS IS REQUIRED. PLEASE ARRANGE
TO HAVE A REPRESENTATIVE OF YOUR FIRM APPEAR AT THE ABOVE ADDRESS
WITHIN 21 DAYS FROM THE DATE INDICATED ON THIS LETTER.
SPECIFIC ARRANGEMENTS AS TO -THE TIMt: qOF--THIS ri1EETING CAN BE HADE
RY CALLING 301-249~4692 AND REQUESTING SUCH AN APPOINTMENT fROM
MISS A. WILSON. PLEASE NOTE THAT YOUR FIRM'S REPRESENTATIVE(S)
SHOULD BE _PREPARED TO DISCUSS THE AIR POLLUTANT EMISSIONS FROM
THE INSTALLATION AT THE ABOVE ADDRESS. HE SHOULD BRING WITH HIM
A~Y TECHNICAL OR ENGINEERING INFORMATION REGARDING PROCESSES Ok
DEVICES LOCATED AT THIS INSTALLATION. -
VERY TRULY YOURS.
A. J. KELLSTADT -
AIR PcrLLuTION CONTROL AGENCY
Figure 3.11.
Sample letter produced by system for mailing to source.
.50
-' ~- .------. ~-~ c--~ ,- ~~,~....
-------
- -.' -. -."~._-_._- .-----'----".---- --.'-"-"-.--------.- --.. -...-..--.-____'.4_'- -- .-.. -.-.
j
- - -.. ~.., {'.. h. .
. -_..- ---. -.- .-- .-.
-- -.4 -- -- ..-- .- _.- --- -_.- ~ - _u- 4-. .-.. - ,H -.. ..- .-... - -'.. .-
-- .- -- .-"'- . . -- U -.
/.:;: ~.-.._; ,.. -"! r' -"'-'''. '.~=:.':'Y
.------
~ T /-. T: 0 i'-i; ~:~: . - ~ ;..: ~ .J
3:;1 E. 24TH ST:::ET
-- -. -- -' -... - -.-'- --- -_.-- CAPr;~AL. (;11Y. --- .... ... -- --.. . - -- --. -. - _.... ..
-_. -.- -- -.-...
.._4.- --. -- -- . ... .
. . -..
- 4. -. -. -_..- -- .
- -' -.- - - --:- -- - -- ---- - -- - - . --121 0 1/71-
-- - ..' .-.. -
- + --..- -..- .
MADISON MFG~ CORP.
'-"-"2301" 'WH IT TAKE R -"$.. .
MADISONVILLE NJ 12300
-.. . 4 -..- - _...
.. --'- - -.-- -.- ~- --- - -- - -- _.- .--- --- -- - - ---. - - .-- . - -.. -.- -- - -_. -- -..--. .
CONTACT
L.V. WILLIAMS ---.--.
, -.- -- - - -- --.. .-- - -- .-- -..- - -- 4 - ..- .-- -- --. .-... .
--- .--. -. .-
-----'-"""---'sUnJECT---KEG I S',-- APPROVAr
LEAD CASTING PLANT
- LEAD MELTING CUPOLA
- . . .'- ..-. . -. .--- -. .
SOURCE'" NO;'--o0003
POINT NO. 001
. -- - .... REG 1ST. NO. A 4 12 6
PERMIT NO. Z4789
. . ._-- .-- ---. - -- -.
- -. .--- -..-
GENTLEMEN
-.. _.. ..--- .'-"'-'-- _n.__. .--.... - ...---.-.-..- --_..-..._.,_.__.~----
'.--.------..---'
WE RECEIVED YOUR REGISTRATION OF AN AIR POLLUTION SOuRCE
FOR THE ADDRESS INOICAT[D ABOV~. A TECHNICAL REVIE~ INDICATES
. .
THAT YOU ARE IN CO~PLIANCE AND ARE EXEMPT FROM EXISTING REGULATIONS
. AND NO FURTHER ACTION IS REOUIRED BY YOU AT THIS TIME.
.
U_-.-' """"'PLEASf NOT E-THAT" A NY"-S1 GNI FICA'~~I'MODTFICATrON -\-lH I-CH' ;.j I GHT AFFECr--'"
THE E;'iISSIONS FKO,\1 THIS INSTALLATION TO THE ATMOSPHEi~E, HEuUIRES
THAT YOU NOTIFY THIS AGENCY 30 DAYS PRIOR TO THE DATE OF TH~
1'v10DIFICI\TIOt~. SUCH ~~ODIFICATI();'JS P.jCLUDE ASIGNIFIcr,,;,:T CHAi~GE I,~
THE RATE OF OPERATION OF ANY PROCESS OR DEVICE AT TH!S LOCATIO~, .
ANY SIC,;UFICAin CH/,NGES HJ THE HOURS OF OPERATIONS, i-iODIFICATIOf-J
OF THE ~~OC[5S ITSELF-O~-THE-ADDITIO~-OF'''i:EW'DEVICES0R PROCESSES.
AT HilS t..[)Dr~ESS. SUCH r~ODIFICATIONS I\~AY REQUIRE THAT Your~ FIfW,
MAKE APPLICATION FOR A PERMIT TO CPERATE. IN 'THIS CASE, THE
i"iODIFICATIONS ~'.~AY NOT 9E ACCO;'.-jPLISHED UNTIL THE PER,\lIT HAS t3EEt'~
GRANTED BY THIS AGENCY. . ....... . .
. -----_..- .
..... ..." .' --_....- - ...- - '_.__..._-_.".~----------_._._...--
--vE'rrY--'TRULY -YOURS.-"""------'-'--------"-"
.-. - ... - _.
A. J. KELLSTADT
.. . AIR POLLUTION CONTROL AGENCY
. -... " ... --.._...,.... "-
- -,-'-'-....-.---
.-----.----.----. -..._----__._e__-.. ... -'''''''-.--'~'--'------ .._--_._~---..~....-... .-. .
-.-. ...... .
... ..'-.-.-' .. - -. ..".'-~--_._.._--------
.-.------ _. --.--.---- .-----.-..- - .
. - --- -- .
Figure 3. .12.
Sample letter produced by system for mailing to source.
. -'. -.... ..--.-.----...-.------------'----------
... .'._---_.~_._....._-----_._--_._. ... ... -
51
-------
-" - --". .... -.. -
. ..
.. -~. .-.-
".' - . .', "
- -- .~~~-~~---'- --------....4. - . . -
.,: \ E. 2,..,.; ::...
. i
Ct~?: ;':\~ ',':'.
12/01/71
~ADISON MFG. CORP.
2301 WHITTAKER ST.
MADISONVILLE NJ 12300
"~'------'
CO'H ACT
L . V. WILL I At'" S
SURJECT
PLANNED VISIT.
LEAD CASTING PLANT
ROlLER-NO.6 OIL
SOURCE NO.
POINT NO.
REGIST. NO.
PERMIT :\JO.
00135
002
G E ~! T L E ~.~ E N
AS A RESULT OF THE INFORMATION SUBMITTED BY YOU TO THIS AGENCY,
WE FEEL THAT A PERSONAL CONFERENCE BETWEEN A STAFF MEMBER OF
THE AIR POLLUTION CONTROL AGENCY AND A QUALIFIED REPRESENTATIVE
OF YOUR FIRM IS NECESSARY. AS A RESULT, A MEMBER OF OUR TECHNICAL
STAFF WILL PLAN TO VISIT YOU AT YOUR INSTALLATION INDICATED.
ABOVE IN THE NEAR FUTURE. YOU WICL BE CONTACTED BY TELEPHONE TO
ARRANGE A SPECIFIC TIME OF THI$ VISIT.
PLEASE NOTE THAT THIS CONFERENCE DOES NOT IMPLy .~IOLATION OF EXISTING
REGULATIONS BY YOUR FIRM. IN MANY CASES, THESE CONFERENCES SIMPLY
LEAD TO CLARIFICATION OF DATA YOU MAY HAVE SUBMITTED.
VERY TRULY YOURS,
A. J. KELLSTADT
AIR POLLUTION CONTROL AGENCY
Figure 3.).3.
Sample letter produced by system for mailing to source.
52
-------
AlIPOUIITIOICOtfTROLAGENCY
- - -.STATE OFfiCE BUllf>INft ..-
301 E. 24nf STREET
CAPITAL CI1Y
12/01/71
MADISON MFG. CORP.
2301 WHITTAKER ST.
MADISONVILLE NJ 12300
CONTACT
L.V. WILLIM.1S
SUBJECT
REQUEST REGISTRATION
LEAD CASTING PLANT
LEAD MELTING. CUPOLA
SOURCE NO.
POINT NO.
REGIST. NO.
PER;viIT NO.
00135
001
GENTLEr-1EN
AS YOU MAY BE AwARE. PUBLIC
POLLUTION SOURCES. REQUIRES
TO THE ATMOSPHERE APPLY FOR
CONTROL AGENCY.
LAW 341. TITLED REGULATION OF AIR
THAT ALL INSTALLATIONS CAUSING EMISSIONS
REGISTRATION WITH THE AIR POLLUTION
INFOR~ATION REACHING THIS OFFIC~. INDICATES THAT YOUR INSTALLATION
AT THE ABOVE ADDRESS MAY BE COVERED BY THIS LAW.
ENCLOSED WITH THIS LETTER ARE INSTRUCTIONS FOR FILLING OUT T~E
REGISTRATION FORM. BLANK FORMS AND A COpy OF THE REGULATIONS WHICH
APPLY. .
THE LAw REQUIRES THAT THIS FORM BE RETURNED WITHIN 30 DAYS FROM
THE ABOVE DATE WITH ALL REQUESTED INFORMATION COMPLETED IN FULL.
UPON RECEIPT OF YOUR REGISTRATION. THE DATA ~ILL BE EVALUATED FOR
CO~PLETENESS AND COMPLIANCE WITH EXISTING AIR POLLUTION CONTROL
REGULATIQNS.
IF YOU NEED ADDITIONAL FORMS, OR QUESTIONS ARISE CONCERNING THE
INFORMATION TO BE ENTERED, OR ITS FORMAT. .PLEASE DO NOT HESITATE
TO CO~TACT THIS OFFICE AT 301-692-3461.
VERY TRULY YOURS,
A. J. KELLSTADT
AIR POLLUTION CONTROL AGENCY
Figure 3.14.
Sample letter produced by system for mailing to source.
53
-------
. .-. --u- --.-.-
- ---- -_. - - --- - - -- .- - - --- ..
- .. - . - ...- .. - .. - .
l.jK fC~Ujnr' ~t C:.;J4~ ;'Gl .' (ff:tCY
- h- -- - .--.- .- --- ---- -._, - -- -S'~;~T£ Ci:Tif.[ - [~!~H.. srJi;
-- -- --- -.-.
30 t ~. ~~.:: r~ ~ s-:r: ~:':~1:
--.--.----
C"~'t-'" r."~
1:';.~!-~
. -. - --- - ----- ---- - ---. --. -- - --- --- --.
-- -.----- --- --.--- .-.- ----. --
. -. . -- --.-. -- - -.
- . -- -~- --
_..- - -. .
- -' -- .-
._- ----
n- ..- -- ----
----'------ '---.---12/01/71'-. -.
-.. - u .-. . --
WHITE PIGMENT CORP.
i -------:3"5 -gUCKE[EY"AV--.--_.
I
WESTERN NJ 06002
- -- -.---- -.---+-_.--"---.---'---'--- ------"___n-
--. --.- ---- - .- .~- --.--
- -.. --- --.- ----. ..
CONTACT
E. S/'.1ITH - ----
,-- - --------.-.------
.--- --. ..-- --, ---- -- _..+- - -..-. - - -.- .-_u
-SIJffJE C f-R ("QUE-ST-P[Arl
INK ~1ArWFACTURER
GAS VATS
- ... -..- -.- -.---- ...-.---.
sOlJrrC-E"-Nb-;- (j 0.0'03-
POINT NO. - 001
-----'-REGIST. NO. A4126
PERMIT NO. l4789
.--------.--. --. --- --- -- -'.- - - - ,-
GENTLEMEN
._~. ------.....-. - ---., -.--- -'---.--._--~"--'----------
_.._-----_.._~--~_.__. ----_._--~.
THE AIR POLLUTION AGENCY HAS REVIEWED THE REGISTRATION INFORMATION
SUBMITTED BY YOUR COMPANY RECENTLY. I~EVIEw BY OUR TECHNICAL STAFF
INDICATES THAT THE POLLuTANT EMISSIONS FROM YOUR INSTALLATION EXCEED
THE REGULATIONS OF THIS AGENCY. - -
---.'--'.-. ._---_.~ -WF'-'ARE','--THEREF'ORE,,--R'EQUE'S, TiiG-,HAIYOV-' -S'UB~rl T-- A-- 'P'LAN-' TO--"'(3R'I NG' ,,"-_u --.,-..---
THESE POLLUTANT EMISSIONS TO LEVELS W~jICH CONFORM TO THOSE STATED
-IN THE REGULATIONS. RECEIPT OF THIS PLAN AT THIS OFFICE IS DUE
1-20 DAYS FROM THE DATE INDICATED ON THIS LETTER.
. YOU ~1AY .\oJlSH TO REVIEw THE: CONTENTS OF YOUR PLAN Of~ ITS REQUIREt.1AJ-~TS
---------.---wTTH- ST AFF~J.Ef.l;RERS'OF--THTS-i\GEr~CY- PR 1 OR -.TO- sue~'11 55 I 0,''; OF HIE' PLAN.-
. IF SO, PLEASE CONTACT THE AGENCY AT 301-349-6932 FOR AN APPOINT~ENT.
IF YOU HAVE ALREADY BEEN IN CONTACT WITH A MEMBER OF THE AGENCY STAFF,
PLEASE CONTACT HI~ DIRECTLY.
PLEASE NOTE THAT THE PLAN YOU SUBMIT ~UST PROVIDE FOR REDUCTION OF
_.uo. - ...,.----.- EM I SS I ONSu Fr~OM -yOUR. J;"~S-T AL LA i I Off" TO'LE vE ls U,D rCA TED 1 N Tr-IE R£GU LA T 10:\
WITHIN A REASONABLE TIME.
n -... ...- -.- .
VERY TRULY YOURS,
- ..',. - ..~.._----_._--- ._--'-_.~--_._--~-------_.__.-.
..._-. ."'-."--'-"--'-'''--'--'-..''''-'.----'''-.--''---.,-_w- --- .
.. -.-. _. .-'- .-.
A. ..J. KELLSTADT
AIR POLLUTION CONTROL AGENCY
.-..- -.-. - -
-'.-.-.,-..-. .- .------.-.--.
--.---
----. .---------...-,----. -._, -,
Figure 3~15. San~le letter produced by system for ~ailing to
source.
. '..--------------------- .--.---. .--~.._. .------..-... ----- +.' -,~,--_. --~---. ...-.. .
"'---"'.----'.'..->+-"-'.
".- - .~._-. '"
54
-------
AIR POI.UITIOII COIfTIOl MilleY
- - - -~IA1LQEF'CE BUILDINQ
301 E. 24nt STREET
CAPITAL CITY
12/01/71
MIDDLEBURY COLLEGE
1 ~LuE H fLLS Ail
HARTFORD NJ 09123
-- _..~-- - -
CONTACT
J. JONES
SUBJE"CT
P"E"f
-------
AIR POWII1OII COITROl AQI(Y
STArr Of£JCE-BWlOtNG
301 E. 24TH STREET
CAPITAL CITY
12/01/71
WHITE PIGMENT CORP.
35 ~UCKElEY 'AV
wESTER;"~ NJ 06002
CONTACT
E. S:v1ITH
SLJRJECT
ISSUE PER1vlI T
I NK ~~l\NUFACTURER
GAS VATS'
SOURCE I\JO.
POINT NO.
REGIST. NO.
PERfv'IIT NO.
00135
001
A4126
l4789
GENTLE~EN
THE PEr~t"llT NUMBER HJDICATED ABOVE HAS BEEN ASSIGNED Tv YOUI<
INSTALLATION AT THE ABOVE ADDRESS FOR THE SPECIFIC PROCESS INDICATED.
rHIS PfR~IT IS VALID FOR A PERIOD OF TWO YEARS AND SrlOULD BE DISPLAYED
PRO~I~ENTLY IN THE AREA OF THE DEVICE ITSELF.
PLEASE NOTE THAT UNDER STATE LAW. THIS PERMIT BECOMES INVALID IF THIS
PROCESS OR DEVICE IS MODIFIED IN ANY SIGNIFICANT FASHION WHICH WILL
ALTER THE RATE OR COMPOST ION OF AIR POLLuTANT EMISSIuNS TO THE'
ATMOSPHERE. IF SUCH ACTION IS CONTEMPLAT~D. A NEW PERMIT
APPLICATION MUST BE SUBMITTED TO THIS AGENCY.
A NEW PERMIT MUST RE APPLIED -FOR -60 "DAYS 'PRIOR TO THE E(,m OF THE
TWO YEAR PERIOD COVERED BY THIS PERMIT.
VERY TRULY YOURS.
. 'A. J.KELLSTADT
AIR POLLUTION CONTROL AGENCY
Figure 3.17.
Sample letter produced by system for mailing to source.
,/
56
I______----~------------------------------
I
I
I
-------
AIR POLLUTION CONTROL AGElCr
- ,_. - .- _SrAIE~fICUUll.D1KG ,-,
301 E. 24TH STREEt
CAPITAL cln
~IDDLEBURY COLLEGE
1 BLUE HIllS AV .
HARTFORD NJ 09123
COf\JTACT
5UOJECT
GE !'JTLD1EN
THE ABOVE
INDICATED
INDICATED
VAll D FOR
. 0.__. .
J. JO;~E S
ISSUANCE CO~~ITIONAL PERMIT
COLLEGE
FURNACE
12/01/71
SOURCE NO.
POINT NO.
REGIST. NO.
PERi'''' IT NO.
OUOOl
003
T4b943
CONDITIONAL PERMIT NUMBER HAS BEEN ISSUED TO THE FIRM
AAOVE AT THE ADDRESS SHOWN FOR THE DEVICE OR PROCESS
IN THE HEADING'OF THIS LETTER. THIS CONDITIONAL PERMIT IS
A PERIOD OF 90 DAYS'FROM THE DATE INDICATED ON THIS PAGE.
--..' .
THIS CONDITIONAL PER~.1Tj- HAS' BEE'N--ISSuED 1'0 COVER OPERATIONS WHILE
MODIFICATIONS ARE BEING MADE IN THE PROCESS OR DEVICE TO BRING THE AIR
POLLUTION EMISSIONS IN LINE WITH THE APPLICABLE REGULATIONS. THIS
PER~1IT MAY BE REVOKED AT ANY TIME BY THIS AGENCY. THE PERMIT MUST BE
DISPLAYED PROMINENTLY IN THE VICINITY OF THE PROCESS OR DEVICE
INDICATED ABOVE. NO ALTERATIONS IN THE PROCESS OR DEVICE MAY BE'MADE
WITHOUT RE-APPL Y I NG FC-R TH 1$ PERM It EXCEP f F'OR PLANS TO BR I NG THE
PROCESS OR DEVICE INTO COMPLIANCE WITH THE APPLICABLE AIR POLLUTION
REGULATIONS. SUCH PLANS MUST BE aN FILE AT THE AIR POLLUTION CONTROL
AGENCY
VERY TRULY YOURS,
A. J. KELLSTADT
AIR POLLUTION CONTROL AGENCY
Figure 3.18.
Sample letter produced by system for mailing to source.
57
-------
Another method is to store the standard texts in a device using paper
or magnetic tape as a storage' medium and add the name and address through a
keyboard.
This alternate is reasonable only if the device is already
available, or can be justified by other applications.
Some machines
which could be used for this purpose are the IBM MT/ST, the Friden Flexo-
writer (Model 23031), and the Auto-Typist (Model 75).
Cost comparisions of the various methods will depend on local factors.
Costs of the separate machines run from $150 to $275 per month;
Cost to
prepare the letters on the computer will vary, particularly depending on
whether the entire computer configuration
is tied up while the letters
are printed.
Source Action Summary
(Figure 3.19)
The source action summary lists all actions that have been recorded'
for a particular source.
The actions are listed by emission point, to show
the current status of enforcement activities with respect to a particular
emission point.
Included on the report are actions that have been scheduled for dates
in the future.
These actions are flagged with the word "future" in the
report.
For each action that is shown, the system prints a variety of other
related data.
The action type, date scheduled, date performed, staff member
performing the action, and the agency section are printed adjacent to the
action number.
This report must be current at all times, in order for the staff members
58
-------
VI
\.0
.--.------.-.--.-----.
, 'J
.'
-. - ---_..._--.- -- _..,---------
_.....
SOU~CE ACTIUN SUMMARY
---... -.......
. . -. - -.-..
(...,
Q9.UQlU. -
.......................................... ..........,.................... ............. ......... ..... ...... .... .... .......... .....,..
'"'
. _.._-----
COUNTY 00011
EN~ORCE".ENT ~ANAr.EMHH_sYS n:M
AI~ POLLUTION CONTROL AGENCY
PA.GE
-----.--- - -..
.__._~----_....._---_. --.--.- -------- ~
. . . . . '.' . . . . ''!'.'!'. '.' .!_~_.~-~!.-~.!'_!-!. !"!"'-'.!-.'. '~-"-'--'-~-'-'.-'-'-' .'.' "0- . . .. '-'.',', '.~-'.-'-'-'-'-.!_~-'--'.'-'..'.'-' ~'-'-~. "'_'_'0' ',-.'.,',.' '.,'..'_t..'.L\.-,t t..e.....'_'_' '.'-!'_'~!-~_!'_~!_'_~_'_'-L'_t.-'_.t.'_'-LL8-!....!-!.-~Lt....!.... .
-_. .--' '. ~_'!'_! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . '-- ..- -
BABCOCK TRANOUC~~
i 5 31Ujc"US Ts.i. .--------.--..."'----P---------'
\/Hr:LAN CT 07211
, ;
SOURCE-NO.
OOOt;SU-
~-~ ,! .' ~ ! . '.. . . . . .'. . . , . . . . . . . . . . . . . . . . . . . . . . . . ! . . . . . . . !' . . . . . . . . . . . . . . . . . . . . . . . . . . . . .'. . . . . . . . . . . . . . . . . . . . . . . '.' . !'_'.'.. ~ ' . , . , , , . . . .' .'....!...~.'. ~ . . . . '!I '---.- .- 0
. POINT ACTION DATE DATE STAI'F L~tTEIt
N9....____Q.e~_~B.l!~J JO!'i_- -- .____N().._.____",C.T I O'(-_.___SCH_EOUL I' D.__. P. I' ~.f:OR.M.E.Q_~E MI:I.ER____.SE.CJ.1 01'1 C.D.ILE
.'"
. --- -. -- ..----.------.-------------
--
r"';
..-. -"'------..r"o
'.'
-__.<;_1\1 II . LJ1CAU.o1:L_.- ----..--.... SOU~CE. LJESCRI PHON - --.... --.--.--..-------
4713q2 6Y C63q12 ELECTRONIC PARTS PROOUCTI
,................... ............. ................ ... ..... ................ ...... .................. ......... ......... ....... ..........
"..
Q9!1.- - .J'II..' LR.E__5Jl~.(;'.~._-_.
- --- -...--...
-"-.----.
COMMENTS
O~
MRS.R~ SCHNEIDER
101 WILLOW RO
-. LA~S I NG. u!:;!LNN. -----.-_.
02
03
04
. --.- .-- - -- _. -.-.---.
FUTURE
FUTURE
-.---------_u.--. _.
001
BolLEIt
002
EVAPORATOR
.. . -.- - -.--.-.--- . _. - ----- .-_.. . ------- .. --_._- .__._.~---
COMPLAINT ~ECO 10130171 OQ/20/71 F. FISH INSPECTION
SOURCE TeSTING 10/30171 OQ/22171 L. KORN~E IC'H I'NGINHRING
INSPECT ION, 10/15171 1 1 F. FISH IN~PECrtON 01
I'I.Q. SURVEY 10/20171 1 1 L. KORN~EICH EN(;INHfHNG 02
10130171
ENGINEERING
OQ/30171
J. PELL
COMMENTS
01 A.Q. SURVEY
I:IECKMAN MUNITOR TO BE LOCATEO AT
PROPE~rv LINE -. -
FUTURE 02'
1210H71
.-.-. ._, ...- u. ---..
003
ELECTRIC. FURNACE
- --...-- __n..
004
PLATING BATH
. - -- ---- -.- --
_.- ..---.--.--
ENGINiiIi"ING'--'O'jU.'--'-. .-
INSPECT ION
1
J. PEll
. .-- --- ---. ..---. . ._... .-.
. _._.. ---
.'--"'--'-.---
.,
Figure
3.19.
Source action summary prepared by computerized system.
-------
using the system to be aware of the current enforcement status of indivi-
dual sources.
For this reason, we recommend that this report be produced
each time the system is run.
Action Summary Report (Figure 3.20)
This report is a management summary report, designed for line super-
visions.
It lists all the actions which have been performed by staff
members during a specified period of time.
The time period can be varied
(see Appendix) to suit immediate agency needs, or to conform with federal
reporting periods.
The actions are grouped by action type, as defined by the local agency.
This action type is the same as is used throughout the system.
Each action
type is assigned a number, which is shown on the action card.
The report is split up by 'agency sections.
This is done by grouping
the actions on the basis of the section responsibility of the one staff
member performing the specific actions.
Frequency of preparation of the action summary report will vary due
to local circumstances.
The report will be most usable for a large agency
with a low average experience level at the line staff level.
Smaller agencies
with stable staffing will need the report less frequently, perhaps on a
quarterly basis.
Source Registration Report (Figure 3.21)
This report lists 'basic source data maintained in the data base regarding
specific sources.
The data are grouped to show general company data, followed
by specific data concerning individual emission points at that company location.
Data shown in this report may be drawn from registration activities, emission
inventory questionnaires, and permit applications.
60
-------
~CTln~ SU~~AKY KEPOKI
.
................................................. ...................... ............... ..............................................
I'I'RIf.O COVEREO
-- ..')6/011.7'...TO 11120171
TYPE CF "CTIC~
FNF1Jfl.CF"'I'NT M~NAGF/IF/\T SYSTJ:M
AIK POLLUTION CUNTKCL. ~GENCY
I NSl'lC TIC'!
I~SP[CT 1!Hi
r IIG [ 1
11/21/H
...... .................... ....... .... .... ........ ........ .... ........ .... ......... ..... .......... ...... ... ... ..... ......... .........
-.- STAFF /lE"'13EP
A~O TITLF
'. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C(J~PLl\l~T
1t;t'!>>1 I TV
SCURCl ~An
I\~r. LOC II-T In,
"CTION RlSULTS
HUUR<, TAI<[N
[JATl Ot-
ACTlu~
NOT ACTIUN
ANU C"Tt.
SUURCE f)[SCK 11'1 ION
PDI:III 1:F.SC1'.-(r>flUi\
H. I' I~I
-------
. .,,'
SOURCE REGISTRATION REPORT
......'[[[
11121111
BABCOCK TRANDUCER
00065
COUNTY 0008
ENFORCEMENT MANAGEMENT SYSTEM
AIR'~QlLUTION CONTROL AGENC~
PAGE
1
-_. _._~.~. !-~ . -. . . . . . . . . . . . . . . . ~ . . . . . . . . . . . . . . . . . . . . . . . . .. ~ . .--~ ... ~.~ ,. . ~ . . . . . . . . . ~ .. ~ . . . 8_. . ~ . .. ~ .~..!.!. ~!-! !.~~.!.- 8. ~ ! .!.. .!~ 8 ~ . . . . 8 . . . . . . . . . . . . . . . . . . . . . ... . . .,. ...
~..~ ,~.. ~.. . . . . . . . . . . 8 . . . . . . . . . . . . . . . . . . . . . . . . . . ~ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ~.. . ~ . ~.. .- ~ .~.~_!.!.~.. . ,1J. . . . . . . . . . . . . . . . . . ~.- . . . ,... . . . . . . . . ~ . . .
-. ._. - "-'-------'-'-'
SOURCE NAME
ADDItESS
CITY, SUTE
DESCRIPTION
COMMENTS
8AACOCK TRANOUCER TELEPHONE 203 6585460
1531 LOtUST ST. CONTACT -- R.V.- MCINTOSti-
WHELAN CT 01211 SIC CODE 32421
ELECTRONIC PARTS PROD.' TIME FACT. 200
PLATING OPERATION UTILIZES RARE METALS - EMISSIONS
HAVE CAUSED NEIGHBORHOOD COMPLAINTS FOR YEAR~
..---..... ...
GRID COORD 411892 8Y
IN~P~CTOR 121 N.E~'
ENGINEER "E21 A.W.
063912,
BOWNE
,80ST,ICK"
...................................!........~..........~.~..~....................~~~.~~.....................~.~..~~.....~~...
POINT NO.
DESCRIPTION
CONTROL DEVICE
000
ENTIRE SOURCE
REGIS. NO.
PERMIT NO.
POLLUTANTS
[[[
_._-, -O'i ---- . . - --
N
POINT NO. 001
DESCRIPTION BOilER
CONTROL DEVICE NONE
COMMENTS USES NO.
REGIS. NO.
PERMIT NO.
POLLUTANTS
3662--
9461
--S02 ';;'
PARTIC.
-"--.-.-'-- "--'---'
.--- .h.. .. ~
6 Oil - SUlEUR
, . . .. .. , ., .. '., .,.
[[[~.............,.................
.,
POINT NO. 002
DESCRIPTION EVAPORATOR
CONTROL DEVICE FABRIC 'FilTER
COMMENTS THREE SI~ILAR DRYING CO~VEYORS WITH
. HOODS - TOTAl OUTPUT 50,000 CfM
OPFRAJES ONLY PARTIAL WEEKS 8ASED
ON DE MANU FOR PRODUCT.
R[GIS.NO~
PERMIT NO.
POLLUTANTS
3662.---
6146
HC :"'OOORS
..' 'H- ...-,-.' .' ..,. .
---"."......-.,
.'
._.__. -
.
~[[[~.~...........~...~..............~...............~.~~..~~~~~~~.~...~~..'
.
POINT NO. 003.
DESCRIPTION ELECTRIC
CONTROL OEVICE NONE
COMMENTS MATERIAL
ROOF VIA
USED. .
FURNACE
IS VAPORIZED AND VENTED TO
PIPING. VA~IOUS ALLOY~ ARE
REGIS. NO.
PERMIT NU.
POLLUT ANT S
3662
~461
HC -
DOORS
'.
..'..'.'-.-.,. ...n..-
. . . . . . . . ... . . ... . . . . . . . . . ~ . . . ~ . . . . . . . . . . . . . . . . .. . . . ~ it ..8 . ~ . . . . ~ .,~ . . . . . ~ ~ . .. . .. ~ . . ~.. . ..-. . ~ ~ . . ~ .. . . -,- . . ,. . . . . . . " . . ,. ~ . e: .. - . .~. . e: ,. .. ~ ~ ~ ._~ ..'
.
POI NT NO.
-------
The assignment of various types of processing and combustion units
as emission points will vary based on local regulations and practice.
Similar processes may be grouped together, or listed as individual points.
Generally speaking, assignment of emission points should follow 'the
permit unit concept, as practiced by the individual agency.
The report is printed in sequence by source number.
If several agencies
are utilizing the system on a combined basis, the report is grouped by
agency.
Edit and Update Report (Figure 3.22)
This is an audit trail and error correction report concerning the
details of system operation~
Normally, only the data bank coordinator will
deal with the entries
on the report.
They reflect the various types of
input to the system, and indicate the action the system has taken.
For
example, some input is rejected based on a failure to pass certain system
edits (explained in more detail in the Appendix).
The DBC should review the report, which is produced for every system
cycle.
It serves to record all input received of the system, and to show
errors in the input which the ,system has detected.
The DBC is expected to
take action to correct
and resubmit any input which failed to pass the
edits.
Action Cards (Figures 3.23 through 3.27)
A number of filled in action cards and special action cards are
shown in the attached figures.
The details of the cards are shown in
the Input Forms section (Section 3.4).
These are shown here to indicate
how they might appear in actual use in normal day-to-day activity.
63
-------
.... ......... ... ................. .... ..... ....... ...... ...... .... .............. ... ........ ............................... ...... .....
11/21111
ENFORCEMENT MANAGEMENT SYSTEM
AIR POLLUTION CONTROL AGENCY
~DIT AND UPPATE REPORT
ENFORCE~FNT MA~AGEMENT FILE INPUT SERIAL
000003
PAGE 1
WF.EK 1,'1
[[[
COUNTY
CODE
[[[
I:RROR
MESSAGE
SOURCE
NO.
AC T ION
NO.
EMISSION
POINT
CARl)
CODE
REMAINING DATA ON CARD
UPDAH
ACTION.
[[[
. 0-
~
OOOij
0008
0:)011
0000
OO:)ij
0010
001!!
0099
Oa99
0099
OG99
OCi9'J
OU91
009')
0099
aa9'}
009'1
0(J9'1
:)099
(;159
0159
0160
0110
0006')
0')065
Oa06')
0006')
00065
00009
00020.
00003
Oa003
00003
00003
00003.
OJ003
00003
00003
00003
00001
Ou003
00003
00001
00003
0000,.
00011
00
03
02
00
00
00
02
00
00
00
00
00
GO
00
00
CO
00
00
00
OZ
02
00
02
Figure 3.22.
000
000
002
003
004
000
007
000
000
000
000
000
001
001
001
002
002
002
002
000
001
001
001
3
1
7
6
6
5
7
1
2
3
4
4
5
6
6
5
6
6
6
1
1
5
1
ELECTRONIC PARTS PROD.
AAIICOCK TRANOUCfR INSPECTION
BABCOCK TRA~DUCER INSPECTION
2ROOF VIA PIPING. NUMEROUS ALLOYS
03
03
C
C
C
C
A1261 B11,7 C
ENTIRE SOURCE N
WILCOX PAINT CO. REGISTRATION 0203010302 C
0704613100600bRROWN MANU~ACTURING 1132MORSE AV ISO N
HARTFORD NJObl02203')274101MR. SHANKS 35123104E04 N
~OLDED PARTS FACILITY N
IPROOUCES PLASTic PARTS AN~ CABINETS FOR CONSUMER N
2APPLIANCF MANUFACTURES N
BOI LER NONE PART., S02 N
IHAS S~OKF DETECTOR ATTACHED TO A21,680 PI,689A N
2AUDIBLE ALARM N
,",OLDING PRESS ACT GIIAR ADSORP UNITHC N
IDEVICf INSTALLED OCI. 1910. ~IAS A327109 121,6321 N
2ELIMINATED NEIGHBORHOUD COMPLAINTS N
30F ODORS. N
MIDDLEBURY COLLEGE PLAN REVIEW 02020104 C
-------
',:vein' ~Bc:ocr11?~i'TDfjCfF--c:Q;-~rr---"rUR~SSrGNE1r-:"~- -,
POI!!! ~T r-
, S?,.' ';? ,~J~I.:E -'lAME -c. rt'::./ STA, F N"ft.Z
t- t- 1 ACT/ON !-;ESUI,. T5 J ~Q ICT/ON . SEi D LET" ER
~ ~ :: I' 1 /:';SPECTION 6 AQ SURVEY TR~QU£3-TR::GIS. e REGIS. APPROVAL
""""':':Lw
~ ...., t- , 1 NO FURTHER ACTION 2 REGISTRATION ~TE
c: ~ ~ I 0 "'" ./..
~ ~ en I 2 OLL:JW NEXT STEP 3 PLAN SUBMISSION :;.~o;'?J 3 PERMIT APPLIC.
Z....,..
..... ~ 3 RESCHE!)ULE ACTION
- ----------..------=
2 REQUEST PLAN
Z
aQ
- I:=:
t-<
Uu
C
4 DATA NOT RECD
4 F.~iicl 11TH SOIJR~: -
4 ISSUE PERMIT
~ RfG;~;jWJJ~ PEVlfW
5 ISS. CONDo PERM!T
HOURS TAKEN IYo!; 6 PLAN ?EV'EW
J J .r // "7 ~(;U:~CE TESTING
I COMMENTS: .$ () .l.. I~ /~" ..
i ~ Fi /4 ,:,. \"" ;:,-:Z 'l;q,- -
6 APPEAR AT AGENCY
~.
"'TC 70077
, :z=
C-~ e::t
- C?-.;
t-8:!:
Uu
c;:::
2}1JT~3rrt;::iDT:;Ort -1'tF'G:-CU: ----- rGT~T~f.fTTOt1"~r~:' SR~Nf(S - - - -.. . - .- -.- . , '- .
Ip01~!I\~!
/J.O-l,".1 ~.LI.:E NAME A;.r,:.1 S1...FF ,,"ME
to- to- /'1i9T10N RE;.s1'lT, ' "EX - ACIl< i'L SEND lE- : ];1'- I
~ ::c r-- 1 INSricTlorl S AQ Sur.VEY 1 R£CUEST REGIS. a REGiS. AP?ROYI.L
:5 l.~ :.:; I ,...... F' 'RTH -R ACTION
...., . I 11.., v .. 2 RE$ISTRAT/ON DATE 2 REQUEST PLAN
~ ~; ;;1 ' -
c ~~ ~ 2 FOLLOW NEXT STEP 3 PLAN SUBMISSlmJ LMff./:J.L i 3 PEP.~11T APPL/C.
~~ I
~ ~ 3 RESCHEDULE ACTION, 4 R:\:tI 'jjITH SGoJ,'cfl!L..oLr..1"v~ ISSUE PERMIT
, , I,
10"151""" if"" "'" ""'''IE I ' 155. CONO: PER" r
6 PLAN REVIEW ~ O."PPEAR AT AGENCY
7 SOURCE TESTI~~G 7 PLANm::D ViSiT
COM '" " TS, 0 ~----W.....~J-4 J.lJldn~~ ...-.L~
d) ~1-1V~ ~ ~~./;!~.d'. '
4 DATA NOT RECD
HOURS TAKEN
---
JTC 7C017 . -
. . DOIr)37'J~TT[-PTGMr~T
JFL!NT ~cd . N' ,
'j H? : ::: I ~')_RC..: ..... -
I I ACTION RESULTS' ...: iEXJ: - ! ~I~ : !.
. t- :-- --. ------ 1 INSF,,::TI')II
;;l: :
J:"'f!:;
~ ~,; w..!. i 1 NO FiJ"!THER :':;',ON 2 REGISTR')T!O~
L<.l -.
u ~., c..-: 3 P'_A-' S"3/'iSSIO:-l I ;:. PER~.nT APPLIC.
I oc: >- 2 FO:"LCW NEXT STEP .. .v " ?E~SO~'
:;.: VJ I 4 ISSUE PERMIT
...., ~ UJRESC!-!EDUL£ ACTIOIJ .. iiE,:tW liTH ~OUr.C: ,-" . , ...
:L: 4 :DATA NOT RECD/;; I 5 F.[";;SriH;J:~ iiE~![~ h~S TO CGi!'Lm 15 ..;.~, CO,.ND. PE~,1111
Q ~ D- I 1/ I ~ PLA" RE'v'::-W 6 APPE':'R AT AG£:;CY
- c. I H"'UR~ ..., KEt' ... ,. .-
t- r,: I ... ~ I 1--0 . . , '
~ oU I --L2-S0t!RCE TEST:~IG, - 7 ?LA~NE? Y'S:T
~~MMENTS: tvL'k/J'~;;=~~L£JA.~ --C--;It-::~ ~-f iLl/2r~pr/~
~~ . ----~- . 3 23 Sample action cards.
, F1gure..
----
55
..-. ~ -- --
CORP - - ~N ::;OBr1!SSIDi'~i N:T: BOtmE - --'-r 'H
ACTI0N I 51.., f N"ME I ,
I SI NDLE" TI B- !
S A:) ::;t;RVC:Y ., R-~~;J~3T REG:S. e REGIS. AF,.,ROVALI
2 REQUEST PLAN I
I
I
I
I
I
!
I
I
C~TE
I
. I
----
-----
-----~<-.- -------,--- ~...~----
..11: }':->,<;:".:- -,".
~~- ~---,-
---- ~ ~~,~ -
~ .~--- -
-------
~....
-.2
..... ". r=
~~~
~L4I""
c:: C.!:J Cool';
0<>-
&.:..Z",
-.. c:
..... --
aw.; -=
)O~3. ~JRITr.prGMrNT.CO~P.. R.SUBMrSSION N;r;BO~Rr-~
P0:~ 1 ACI
N') N~ !.J~RC':: NA..I- ACTION 51.... I N"'.IE
ACTIQNR~_SULT~ .I-,:EXT .' ;TlI II . 51 ND LEo TI R
I, 1 INS.PEC"T ION" - 8 AQ SURVEY 1" REQUEST RE:G;S:- S REGIS. APPROVAL
1 NO FURTHER ACTION 2 REGISTRATION CATE 2 RECUEST PLAN
o-Ul..LCW "IEXT STEP 3 PLAN SUBMISSION PE'!Sm' 3 PERMIT A?PLlC.
3 RESCHEDULE ACTION 4 R,V!fW 11TH SO~RCf 4 ISSU: PERMIT
l~.-
. - .- - -
z:
eel
- 0::
;-r::::
~C-)
4 DATA NOT RECD
HOURS 1.4KEN
I
CO~~MENTS: f k
5 P.:~:S"AI!ON .EVIE,
OLMI ReVIEW
o;iS 10 CONP! [T~
5 155. CONDo PERMIT
J'
6 APPEAR AT AGENCY
7 SOURCE TESTING
~o
7 PLANNED VISIT
I_-
I
I
JTC r0077 .. -
~J021rfll? .:~BC[Jt.K -TR:~r.DIJCEP-" °P[~r~
',.,pnl I
I' ~/j" I :j~. SJ....I..:'E NA~'~ . ' !t..C'T.':N
t-.... I ACTI9~_B~~!JJ.,.T~ : EXT &I!II-
~~;z: I 0N::PECTI:>~~ 8':'::: SU~VEY
..... H iT I .
~ .:.: Lo.o I 1 NO FURTHER ACTION 2 REGISTRATIO~I D4TE' 2 REQUEST PLAN
~ ~ E I /0";LL~W NEXT STEP 3 PLAN SUSMISSION 4'.g.~ 3 PERMIT APPLIC.
~ ;:~ t.;')1 l/' " .. n;, , 1/"\
~ ~ 3 RESCHEDULE ACTION 4 R:VI[W \'I:i~ SCURC, ~SSUE PERMIT
-~ 4 DATA NOT RECD 5 RfGISi~Am:; REm.. HRS TO C:14PlffE 5. ISS. CONDo PER.MIT
~~I +
;:: ~ ,HSURS TAK~ 'V~~ 6 ':>LAN P"VIEW '3 A?PEAP. AT AGENCY
~ r 17/ 7 ~(,!JF.CE TESTING. 7 PLMHIED VISIT
COM"'ENTS:-----b~~ ,~ ~-:;t.... /O"'-f1J- ~ ~~ -
-------
1-1-
22:
'W!!!
~- '
~~~
.&&1 LY~
U #~ e-
C~ ~U}
o ~>-
~ Z.n
7~
~ W ~
Ze
O~
-
I-
-------
1-1-
.zz
lUlU
~:E~
1&1 LU W
U "...
~ tet~
2 Z&n
,z .«
IU=:
ZC
Q~
'... c(
'UU
cs:
SPECIAL.ACTION CARD
County
Code t.l).0. I . 7.
No. I (). (} , o. ?.I I
Agency No.
,0,2.0,
Source
Emission Point No. I tJ 0
11...
ACI1O:. TYPES
i'-'::SGi..:i:5
Action No. If) . 7 I
Action Type ,0 I /.
Staff No. .E. /. '71
,
Day
I
Yr.
Action Date ~. 6. 1.1 ,0 t.?, J.J
Mo. Day Yr.
Action Results I
Hrs. Taken I
Update Code L..J
N. C. or D
n
E VAL I,.+T4:-
Next Action I
Next Action Date .
I
Mo.
01
02
03
04
05
. Inspection 01 No Further Action
Registration 02 Follow Next Step
Plan Submi3sion 03 Reschedule Action
Review witn Source 04 Data Xot Received
Registration 10 Other -- see
Review 'Comments
Plan Review
Source Testing
A. q. Survey
Complaint Received
Other -- see
Co~~e!1.ts
01
02
03
04
05
06
07
. 08
Est. Hours to Complete I
Send Letter No. I
to Source
06
07
0«3
09
10
Figure 3.26.
68
Comments JIJ..., JG;.I-t/ \.\ c ~"'.<:JKJ&n
L ()/~ DJ T' CAI
..
Li:.J.l.~c(""
Request Registration
Request Plan
Send Permit Application
. Issue Pendt
Issue Conditional Permit
Appear at Agency
Planned Visit
Registration Approval
Sample special action cards.
-------
1-1-
zz
. y.J 1&1 I
~~~,
(' ~~
.. , c;a
Ui-Mill
"I-
f:i ~~
II. Ztft
Z,«
, III ~
Zc
O~,
i=
01
02
03
04
05
06
07
08
Request Registration
Request Plan
Send Permit Application
- Issue Perr:ti t
Issue Conditional Permit
Appear at Agency
Planned Visit
Registration Approval
06
07
013
09
10
Figure 3.27.
Sample special action cards.
69
-------
.
3.6
Files Maintained by the Data Bank Coordinator
. Some of the output reports are maintained at a central point by the
data bank coordinator.
These are the source action file, the two sets of
geographic locators (by grid coordinates and by city and street addresses),
and the source registration report.
In additio~ other files containing
detailed calculations, correspondence, and other data not directly involved
in the system are required for each source.
In some cases, these manual
files may be split and retained by individual sections within the agency
which maintain jurisdiction over the particular source.
When the system
is being operated on a multi-agency or multi-office basis, the reports
that are maintained centrally are split between the agencies.
The system
groups the data in appropriate sequence for such a split.
Other reports such as the individual future schedules and the section
future schedules, the action summary, the overdue action reports and the
action card produced by the system are distributed to individual sections
or staff members as appropriate.
Figure 3.28 indicates the flow of the
various reports.
3.7
System Startup
Proper startup procedures are essential to the operation of the system.
Time invested in this initial activity will be well spent in terms of future
payoff by the system.
System procedures represent a significant departure
from previous practices and occasionally individuals may resist adapting their
day-to-day practices to conform with the system.
In each conversion, some
difficulties can be expected.
It will be important at these times to differ-
entiate between conversion
problems and any continuing problems.
The
70
-------
Geographic
Locators
i.
Carbons
of
Central
Files
Schedules
Source
Printout
File
DATA BANK COORDINATOR
CENTRAL AREA
Action
Summaries
OPERATING
SECTIONS
Figure 3.28. Flow of data.
71
';
Source
Manual.
Action
Files
n
~p",
Action
Cards
Misc.
Input
Data
-------
attached milestone chart, Figure 3.29, indicates a logical sequence of steps
to be followed to begin operation of the Standardized Computerized version
of the Enforcement Management System.
The milestone chart is arranged in
three vertical lines.
The right line indicates milestones of computer
oriented activities during the conversion period.
The middle line relates
to physical activities which must take place to obtain forms and establish
communications.
The left line involves personnel activities such as training
and conversion activity.
These activities have been numbered and are dis-
cussed below under the number indicated on the chart.
1.
Select EMS Project Leader.
This topic is discussed in detail in
Section 3.1.
2.
Make Arrangements for Computer Usage.
A suitable computer must
be located and arrangements made for time on the equipment.
System
requirements are the availability of a COBOL compiler, at least 40K
of core memory, 3 tape drives (or the equivalent) and sorting capability,
card reader, card punch, printer, modified keypunch (to interpret
action cards) or regular card interpreter.
3.
Select Data Bank Coordinator.
This topic is also discussed in
detail in Section 3.1.
4.
Designate Programmer to Install, Maintain System.
An individual
must be designated to set up the initial system from. the material
supplied and to maintain the program in operation.
He will also be
required to investigate occasional problems that will arise in the
operation of the system.
The problems mayor may not relate to the
72
-------
Computer
STAaT Oriented
Peraonnd Activities
Activities
.. .
Pbydcal Activities llake Arrange
Select E.M.S.
Project menU For
Leader Computer
Tim.
1 I ~.I_-
Select Data Desi8nate
Bank Prograreer
Coordinater to Install,
AdJU8t FOl'1ll5 tlaintai.n.
3 I. to Local " System
Practi.. 4
Prepare Data
For Internal ,
Computer
Tables
6 I
I f ~~
"able of Table I
;Agenc1es of Staff I . Title I nelude local
I in Actions Section;: Table able Data in
System Table I ; Computer
7T- Programs
81 9 10 I 14
.!r
Hold C~~" ra I I I
Heeting to
Describe Action ' Spedal Standardized
System Cards Action Agency
IS I (Hech.] Cards letters ,
I omplle Com-
Select Agency 11 I " I 13 uteI' ~ro6racs
Section rC'r I rom Source
nitial Syste' prder Decks
Uaage Supplies 17 I
18 f For Catalog
onverc Syatem Programs And
Source Files 16 .. Adapt JCl to
to Source t I I ocal
~au Fol'1lls reprinted Special Preprinted Standards
23 I echo Action Action Continuous "IT'
Cards Cards Form Keypunch
rain Section Initial Source
ersonnel in letterheads Data.Personne~
Syatem 19 I 2Q I 21 I ~etter Cards
Usage 24 I
lS I Build Initial
J(eview Systee Receiva Files. Correc t
Pperation Syatem Reported
Perform Supplies. Errors
~training 26 I
28 I 27 I
Establish
elect :iext Bind And No rms 1
Section For Distribute Cyele of .
Syatem Initial o1.erations
Expansion Reports
I 29
31 I 30 Conve rt 2nd
Train System ~stablish Staff Sectio
Personnel in h-iming, Means to .
System Iof Data-flow System
Usage k.rith Staff
. Jl I 33 I 34
.
Expand ~ystem Expand syste1
to All Croup' to Other
I~nvolved Wi~~~genCieS as
Sources Appropriat~
35
36
Figure 3.29.
Milestone chart.
73
-------
programs themselves.
This will not require a full-time person;
someone in the computer installation (rather than the air pollution
agency) may be assigned these duties.
5.
Adjust Forms to Local Practice.
The sample forms supplied with the
system represent generalized usage reflecting procedures in a variety
of agencies.
It is anticipated that virtually all agencies will want
to make changes to conform to local agency operation.
In particulart
the sample letters will probably be modified by every agency.
These
should be revised after consultation with appropriate agency personnel.
6.
Prepare Data for Internal Computer Tables.
These tasks must be
done in coordination with the maintenance programmer who will actually
install the system.
He will require certain data to make the system
responsive to the particular needs of the local agency.
7.
Table of Agencies in System.
InitiallYt only one agency will
utilize the system.
Howevert the system can handle a multiple-agency
situation and an agency table is contained in the runs themselves.
Note that a single agency can utilize the multi-agency system capability
to group
reports by "regional offices" or other divisions within the
agency itself.
8.
Table of Actions.
These are the actions which correspond to the
entries on the special and mechanized action cards required by the system
to operate properly.
9.
Agency Staff-section Table.
A deck of cards is preparedt one for
each staff member who will utilize the system.
Each staff member must
be assigned
a three-digit numbert the first digit of which is a
74
-------
letter indicating the section within the agency to which he belongs.
10.
Letter Title Table.
The standardized letters that have been made
up each have a descriptive title which is printed at the top of the
letter and also included on the right side of the action cards.
The
programs contain this information which must be supplied to the person
doing the programming maintenance of the system before startup.
11.
Action Card, Mechanized Format.
Standard aO-column machine proces-
sable cards should be obtained from a local supplier in the general for-
mat shown in Section 3.3.
Changes may be made under the "Next Actions"
heading in terms of description of actions which are normally performed
by the particular agency.
Do not change the action results field with-
out checking carefully as some of these codes trigger various routines
in the program.
Changes in. the next action entry should be coordinated
with the programming personnel involved to insure that the computer prq- .
gram and the cards are "in step."
12.
Special Action Cards.
Changes made in the mechanized action cards
should be reflected in the lower portion of the special action card since
they must correspond.
Note, however, that more actions may be printed
on the special action card than on the mechanized version.
This is to
permit the data bank coordinator more flexibility in entering data into
the system.
Such actions, as the receipt of a complaint, are not handled
in the field, and consequently need only appear on the special action
card.
Action numbers, however, cannot be duplicated.
75
-------
13.
Standarized Agency Letters.
Samples provided reflect general
~ractice in local agencies contacted.
The sample letters should be
carefully reviewed and modified for usage by each agency.
"It may be
that existing letters can be used without alterations by the system.
In gene!al, the more letters that are available to the staff members
using the system,
the more likely that clerical work will be reduced.
The object is to provide flexibility by having available a variety of
letters to meet all standarized situations that may occur.
The heading
of the letter cannot be altered without making programming changes.
14.
Include Local Table Data in Computer Programs.
A number of tables
in the program must be modified to adapt to local regulations and
practices.
All that is required is that the source cards be changed
to reflect local agency practice.
For example, the agency title(s)
must be entered into the program as well as the particular actions which
the agency expects to perform (see Appendix for details).
15.
Hold General Meeting to Describe System.
During a regular meeting
of agency personnel or during a specially scheduled meeting, the director
of the agency should describe the general outline of the system and in-
dicate the installation schedule.
16.
Order Supplies for System.
Some system items require fairly long
lead terms for delivery and should be ordered at once.
In addition
certain clerical supplies are required for use by the data bank co-
ordinator.
These are normally available through established supply chan-
nels within the state or governmental structure.
76
-------
17.
Compile Computer Programs from Source Decks.
The programs sup-
plied to the agency will be in the form of source decks for compilation
using the local computer.
The programs were tested on an IBM 360/30
under DOS and have also been run on a 360/50 under OS.
Generally
speaking, they should run from any COBOL compiler although occasional
differences may appear requiring minor modifications.
The system utilizes
standard sorting techniques;
,however, in some cases these may have to
be adapted to local procedures.
18.' Select Agency Section for Initial System Usage.
It is recommended
that one section of the agency, be selected for conversion to the system
at startup time.
This selection procedure should involve consideration
of the section leader - his flexibility and his interest in a system of
this type.
This section might well be one in which coordination and
scheduling problems arise from a large workload.
19.
Preprinted Mechanized Cards.
These cards should be ordered from a
supplier of tab cards who can assist in the forms design.
Costs run
from $1.00 to $1.25 per thousand, with a normal setup charge of ap-
proximately $75.00 payable one time only.
Most suppliers make available
a proof of the layout before the cards are printed.
This should be care-
fully reviewed to insure that the layout reflects what is actually wanted
by the agency.
Note that there are two types of action cards for use
depending on locally available equipment to print data across the top
of the cards (interpreting).
Standard interpreter devices generally
have a 60-co1umn line, whereas interpreting keypunch~s
utilize an 80-column
format.
Availability of local equipment to print the source and other data
77
-------
at the top of the card should be reviewed to make sure that the fields
.at the top of the card will match the available printing.
20. Special Action Cards. These so-called cards are actu~lly 8-1/2x 11
sheets which can be printed using standard processes or multilith.
21.
Preprinted Continuous Form Letterheads.
This form is designed
for use on the computer printer to print the standardized letters and
certificates to sources.
It should consist of two or more parts so
that a file copy may be retained in the agency files.
The actual
agency letterhead need only be printed on the first copy.
This should
reflect the normal letterhead used by the air pollution agency.
In
some cases an agency may not want to invest in these forms.
Standard
computer paper is available in letter size sheets and can be used for
this purpose.
Agency identification can then be supplied by means of
a rubber stamp designating the agency.
22.
Catalogue Programs and Adapt JCL to Local Standards.
The local
programmer should adapt the JCL (job control language) to meet the
local requirements or to conform to the peculiarities of the local equip-
mente
In particular, there may be differences in the way in which a
particular installation wishes to handle the operation of the series of
runs.
In most cases, all the programs will be catalogued on a disk and
the series will be executed from the job control language deck.
In
others, each program will be run from the object decks.
The latter
option is less desirable.
23.
Convert Source Files to Source Data Forms.
For sources which are
78
-------
currently interacting with the section of the agency selected for
initial conversion, it will be necessary to set up basic records on
magnetic tape reflecting. information already held in the files.
A
decision must be made concerning whether or not past actions should
be picked up for system purposes.
In general it is recommended that
only actions which are current or scheduled for the future should be
included, but local considerations may modify this recommendation.
24.
Keypunch Initial Source Data, Personnel, Letter Cards.
The
Appendix contains keypunch instructions for all forms which are normally
punched.
In addition card layouts are available for the personnel and
letter cards.
The local programmer should coordinate with the keypunch
personnel to make sure that these instructions are understood.
In
particular, the keypunch instructions for the action cards should be
carefully reviewed since the handling of these cards requires a
moderate amount of training of the keypunch operator.
Letter cards
and the personnel cards which are entered into the system are only
changed infrequently and as a result can be handled from the card
layout forms that are available.
25.
Train Section Personnel in System Usage.
The data bank coordinator
should address a meeting of the section and explain system operation,
the filling out of the various forms and, particularly, the use of the
action cards by individual section personnel.
The coordinator should
emphasize that initial unfamiliarity with the system may cause problems,
but that the overall result of its use will be to improve the availability
of information to staff members and reduce clerica~ work required.
79
-------
26.
Build Initial Files, Correct Reported Errors.
The initial system
'startup utilizes a dummy master tape (see Appendix), followed by the
update run itself.
Probably a limited amount of initial data should be
used for the first run.
Note that the complete cycle must be run on
every o~casion.
Otherwise, some data which only appears once (such
as Action Cards) may be missed.
On the initial pass, it is likely that
a certain number of errors of various types will appear on the edit list.
These should be carefully checked to determine their cause.
27.
Receive System Supplies.
Normal time to receive the mechanized
action cards is 4 to 6 weeks.
Other material can generally be obtained
more quickly.
The data bank coordinator should follow receipt of
supplies closely to make sure that undue delays do not occur.
28.
Review System Operation, Perform Retraining.
In second and sub-
sequent training sessions, the coordinator should review initial re-
suIts of the system and discuss problems that have occurred.
A likely
subject of discussion is the question of who makes what entry on the
action cards.
For example, when the next action is scheduled to be
performed by second group of staff members, the card may have to pass
through a number of hands before re-entry into the system.
This will
vary with local procedures and must be worked out on an individual basis.
29.
Establish Normal Cycle of Operations.
Working with the DBC to
determine normal run frequencies and input timing, the computer facility
(staff) should establish a regular operations schedule.
30.
Bind and Distribute Initial Reports.
Once initial reports are
available from the system, they should be bound and distributed.
Some
80
-------
files are maintained centrally;
these should be included in standard
computer printout binde~s available from many suppliers. Other reports,
such as the individual schedules, go directly to users.
Distribution
of such reports should include additional explanation of the use that
should be made of the data.
This will be true as the system is expanded
over time.
31.
Select Next Section(s) for System Expansion.
When the initial
system is operating smoothly, additional agency sections should be
chosen for conversion to the system.
Clearly the system will not be
effective until it includes most of the agency, since it involves
coordination between sections and the scheduling of activities on a
source-related. basis.
Hence, when a source involves several sections,
each must be a part of the system.
32.
Train Section Personnel in System Usage.
The various training
tasks that were performed for the first section should be repeated
for new people coming into the system.
Problems that occurred with
the first section should be corrected in subsequent training as the
system expands.
33.
Establish Timing And Means of Data Flow with Staff.
It is recom-
mended that the system be run on a weekly basis.
Certain agencies may
wish to vary this timing.
The frequency of system runs is based on
the agency's experience with the Enforcement Management System;
usually,
a larger agency will run the system more frequently than a smaller agency.
81
-------
34.
Convert Second Staff Section to System.
When the initial batch
'of data has been processed correctly for one agency staff section and
the data bank coordinator has determined that the system is running
relatively smoothly, the data for a second staff section should be
convert~d to system operations.
This will involve the same steps as
the first except that the data will be added to the existing master
file rather than starting a new master file from scratch.
35.
Expand System to All Groups Involved with Sources.
The objective
is to have all personnel in the agency who interact with pollution
sources operating and scheduling their actions through the Enforcement
Management System.
Once initial success has been achieved with first
groups, this aim should be pursued as soon as possible.
36.
Expand System to Other Agencies as Appropriate.
As discussed
elsewhere, this system can operate on a multi-agency or multi-office
basis.
In cases where coordination with another agency within the
state is required, the system can be of great help to standardize
actions that are being performed with various sources.
In addition,
in situations where a state agency cooperates with a number of local
agencies, state agency resources may be greater and computer avail-
ability may dictate that the state operate the system for the entire
group.
Such inter-agency coordination is desirable and should increase
the effectiveness of intraction between agencies.
Note that the system provides flexibility in order to acco~lodatc
varying local agency practices.
For example, an individual agency may
insert all the steps in a compliance schedule (dealing with a specific
source), even though these steps may extend over a period of years.
Con-
versely, the system will accept entry of a single step at a time.
In
82
-------
both cases, the various actions will be processed by the system and
maintained in the basic-data file.
Various reports and summaries
(including staff schedules) will list these anticipated actions, whether
they stretch far into the future, or cover only the next anticipated
action"
3.8
Resources Required
Certain resources will be required both to implement the Enforcement
Management System, and to maintain it.
Estimates of these resources have been
made in terms of man-days and computer time.
The estimates have been further
stratified for small, medium and large agencies.
Figure 3.30 indicates this
information.
No estimate has been made for supplies, such as action cards,
letterheads, etc., as these costs would normally fall within the established
office supplies budget.
In any case, the amount is not anticipated to be a
large one.
83
-------
I;
\
!I
I
I
\
I.
, '
!,
System Startup and Data Conversion
Computer Programming
Personnel
Systems Analyst and Other
Senior Personnel
Data Bank Coordinator
Other Technical Personnel
CD
.p..
Technical Personnel
(being trained)
Data Conversion - Clerical Time
Keypunch Time
Computer Time (Medium Scale Computer
i.e.,360/40 - CPU Time)
Continuing Costs.(Normal Operation)
Per Month Basis
Normal Computer Running Time
(assumes weekly processing with 360/~0)
Normal Program Maintenance
Data Bank Coordinator
Keypunching
Figure 3.30
ESTIMATED TIME FOR SYSTEM STARTUP AND OPERATION
(in Man-Days and Machine Hours)
Level 2 System
Small Agency
(10 to 25 Staff Members)
Medium Agency
(25 to 100 Staff Members)
t
Large Agency
(over 100 Staff Members)
7 8 9
8 10 14
12 20 32
3 5 10
6 10 22
8 12 28
4 6 15
2 1/2 hrs. 3 hrs. 3 1/2 hrs.
3 hrs. 4 1/2 hrs. 6 hrs.
2 2 4
7 14 21
1 2 5
-------
4.0
ADVANCED COMPUTERIZED SYSTEM
4.1
Description
The advanced computerized system is designed for the larger .agency
with acute scheduling problems.
It contains all the features of the
standard computerized system plus an automatic scheduling routine which
permits the system to schedule types of activity and personnel without
specific input from staff members.
For example, most agencies follow a standard pattern of action with
regard to a specific source.
Registration is followed by a registration
review which is in turn followed by the submission of a compliance plan,
a review of the compliance plan, and issuance of the permit.
The sequence
varies depending on local regulations and practice but the foregoing is
generally the pattern followed.
This sequence of events is entered into
a table in the program as explained in Section 4.2.
The computer will
automatically select the logical next step when an action card which indi-
cates that the first action has been completed is re-entered into the
sys tern .
The next step is then selected.
An appropriate new action card
is prepared by the system and the new action appears on the various reports.
A staff member is assigned to perform the next action (normally indicated
on the returned action card in the standardized computer system).
He is
selected from the information contained on the mechanized record for the
pollution source involved.
This information consists of a general assign-
ment of an inspector and engineer for each source.
These are the staff
members who would normally work with that particular source.
Figure 4.1
is a schematic representation of this scheduling function.
85
-------
Action
Sequence
. Table
Source
Difficult
Factor
System
Selects
Next Action
New
Action
With Tim
Estimate
System
Schedules
New Action
FiGure 4.1.
Schematic scheduling function.
o
Action
Card
86
Action
Card
Completes
Action
Schedule
Card
No Staff Time Available
Time is Available
New
Schedule
Staff
Schedules
o
-------
The question now arises concerning the date that should be assigned
to the next action.
Clearly, an inspector or engineer would normally
have a substantial number of sources assigned to him.
It is quite reason-
able to assume that many of these sources would require no action for a
period, but that suddenly a large number might require activity.
The
system utilizes a schedule card for each staff member involved, replacing
the personnel cards.
It tracks the work assigned to the specific individual
for a l3-week period into the future on a week-by-week basis.
When it is
determined that an action should be assigned to a specific staff member,
the system checks his schedule card for the next week.
It computes the
estimated amount of time the function will require and determines whether
time is available for that particular staff member from the data on the
schedule card.
The computation of the estimated time the job requires is accomplished
as follows.
Each task has a complexity factor assigned to it.
This is the
estimated amount of time the task will require for the average source.
Each
source record also contains a source factor which indicates the anticipated
degree of difficulty that is expected to be encountered in dealing with this
source.
This is entered based on factors such as distance from agency office,
degree of complexity of installation and the like.
This factor to account
for difficulty will change as experience is gained.
An average source in all
respects (the norm) would have a difficulty factor of 1.0;
a very dif ficul t
source, a higher number;
and an easy-to-deal-with source, a fractional number
such as 0.6.
To determine the estimated amount of time required for a specific
action, the system multiplies the difficulty factor for. the source involved
87
-------
times the complexity of the specific type of action.
If the schedule card for the next week indicates that the new action
plus actions already assigned total more than 30 hours, the system goes on
to the following week to determine if time is available during that week.
The 3D-hour maximum is an arbitrary figure and can easily be adjusted,
based on experience.
It was selected on the assumption that approximately
25 percent of the average staff member's 40-hour week is used up in ad-
ministrative tasks such as meetings, technical updating and so on.
When
the system encounters a week in which the task can be entered without
violating the 3D-hour maximum, it schedules the action for that week.
Estimated hours for the job are then added to that staff member's total
for the particular week, so that additional actions which would bring the
total over 30 hours are not scheduled during that period.
A ne~ schedule card is produced during each processing cycle for each
staff member.
It is recognized that events affecting individual staff
members can disrupt this schedule.
Disruption can arise from vacations,
sickness, technical school attendance, or other "interruptions" to normal
activities.
When such items are known in advance, they can be manually
keypunched onto the schedule card between update cycles.
If this is done,
the system retains this information and includes recognition of such
scheduled activities in its assignments of actions to individual staff
members.
If a scheduling adjustment must be made after the actions have
been assigned for that week, it can be done with action cards using the
"reschedule action" option.
When such actions are rescheduled, the times
on the schedule card must be modified by keypunch entry.
88
-------
It is recognized that estimating the amount of time for a particular
action and then applying these various estimates to schedule a specific
staff'member's available time is at best an inexact science.
Experience
in assigning a source difficulty factor and complexity factor for specific
jobs should improve the performance of this scheduling function.
We rec-
ommend
that, an agency planning to install the Advanced Computerized System
start out with the Standard System and work into the Advanced System at a
future date.
The computer programs are completely compatible.
The diffi-
culty factors and the task sequence for the specific agency can be entered
in advance of actual implementation.
When it is desired to begin the auto-
matic scheduling process, a minimum number of COBOL statements can be
changed and the appropriate routines will be brought into operation.
89
-------
4.2
Technical Details
This section describes in detail the mechanism of the scheduling
process.
We recommend that the, casual reader skip to the next section.
The advanced computerized system (ACS) is an expansion of the' basic
Enforcement Management System as shown in Figure 4.2
(note that only the
update program (framed area) has been altered).
To simplify the conver-
sion from the basic system to the advanced system two separate source decks
are available.
The advanced computerized system's update program includes
the same logict requires the same inputt and maintains the same files as
the standard computerized system.
This enables an agency to move up to
the ACS by simply exchanging the update source deckst slightly modifying
the personnel deck (explained below)t keypunching the week number into the
control card and executing the system as usual.
Due to changing requirementst local programming personnel may modify
the system from time to time.
In upgrading the system to level 3t local
personnel should be sure to incorporate any change made to the update pro-
gram locally.
4.2.1
Computerized scheduling within_update program
The automatic scheduling option may be, utilized or ignored depend-
ing upon whether the week number field (columns 11 and 12) of the control
card is used.
If left blank (no digits punched in either co1umn)t or if 00
is enteredt the system will perform exactly as the basic system.
If 01 to
52 are enteredt the system will automatically schedule actions; if a number
greater than 52 is entered, the program will abort (stop).
Additional in-
formation pertaining to the control card can be found in the Appendix at the
back of this manual.
90
-------
firs~ sort
sort
transaction
file
update
run
(Level III)
new
personnel /
chedule deck
control card
I
_J
run
Framed area (above) reflects
changes to basic system.
extract
\,
second
sort
deck
future.
schedu
action
summary
,
Figure 4.2.
System Schematic.
91
-------
The scheduling module utilizes four separate closed subroutines
which are executed from the main logic path.
The personnel deck repre-
sents the prime source of input to the scheduling logic.
At the end of
each cycle a new personnel deck is created, which reflects all actions
scheduled within the next 13 weeks.
This previously created personnel
deck is used ,as input for the next cycle (dotted arrow in Figure 4.2).
Before any scheduling can be accomplished the personnel deck must be ad-
justed by the computer program to reflect the new l3-week period (under para-
graph 850-SHIFT-WEEKS).
This is accomplished within the system by:
a.
dropping the first week on the personnel card (columns 41
and 42)
b.
shifting weeks 2 to 13 (columns 43 through 66) two positions
to the left (see Figure 4.3), and
c.
adding 1 week to the current week number (personnel card
columns 39 and 40).
Steps a, band c are repeated until the current week number is equal to the
week number from the control card.
During the shifting of the
personnel
deck,each week is validated for numeric contents.
If a week is not numeric
(contains a space or alphabetic
character), its contents are replaced with
zeros.
This enables the standard personnel deck (from level 2) to be used
without re-keypunching.
Any week number (01 to 52) must first be entered
into the personnel deck (co1urnns39 and 40) before running the system.
This
can be performed semi-automatically through any standard keypunch machine
by the use of a program card (control card used to duplicate data from one
card to another).
92
-------
/----.--.. --..- -. -.-. .. -. -
i./zzxxxxxxx ~l2l7l060l7lll207lENFORCEMENT MANAGEMENT FILE
1 r Control Card
i
Week Number
-. ..0___- ---
~_.~.._-.._-
INPUT SERIAL 000002
Past week Number
/~-~~;::::nn::D::::;: ---Inp::SPECTOR-SR. -}~303~;; - !5;/~;73 1;000000 -
! ! i
I l i ! i
i .I / ! /" Shift weeks over 6
I / I / / positions to left
- ---------- ---------------'-- ------c- -JJhlL-----~~e~e=~:~~e ~ three
(BB0011011. HEDGEPETH INSPECTOR- SR. - 4~2030302006oooooo000000
Personnel Card - Output Current Week Number
Figure 4.3.
Shifting weeks on personnel card.
93
-------
If an action card is returned to the system with the action results
field bearing the code for "Follow Next Step" (code 2), the next action
will be scheduled by the system.
This involves a table lookup in which
the current action from the action card (and agency) is matched with the
NEXT-ACT ION-TABLE entries.
The next action code is picked up and placed
within the next action field on the action card, and processing continues
as if the next action was entered by the data bank coordinator (paragraph
named 860-NEXT-ACTION-LOOKUP).
Scheduling of actions is accomplished within paragraph 920-SCHEDULE-ACTION.
The total time (in hours) needed to complete an action against a source is
computed by multiplying the source time factor from the master file (if none
is given,l.OO is assumed) by the action table factor (this is found during
830-ACTION-LOOKUP).
The total time needed to complete this action is com-
pared against the assigned staff member's personnel card (the correct staff
member was previously found within 820-PERSONNEL-LOOKUP and the relative
"address" saved in SUB-SCRIPT) week by week (in ascending order, 1 to 13)
until a week is found for which he has sufficient time left to accomplish
this action (time already scheduled plus time needed must be less than
30).
The week must next be translated into a calendar date.
This is
accomplished by adding the week number within the personnel card (SUB-SCRIPT-l)
to the week number (from control card);
this "generated address" is used to
select the correct month and day from the DATE-TABLE.
The correct year
(either current or current plus one) is picked up and the entire date is
placed within the scheduled date field.
Both the basic and the advanced computerized system have a hierarchy
of scheduling dates.
This method is used to prevent any action from not
94
-------
being scheduled (and, therefore, not being printed on reports) because a
date, was not provided.
It also enables the data bank coordinator to over-
ride any dates generated by the system.
1.
The dummy date has the lowest priority.
This is the run
date plus one month (see Section 2.1 of the Appendix).
This date will be used if step 2 and/or 3 (below) are not
required.
2.
The scheduled date is generated only within level 3.
This
date will replace the dummy date if the scheduling logic is
utilized
(Week number from control card is 01 to 52).
3.
The manual date has the highest priority and will replace
either the dummy date or scheduled date.
This date enters
the system from either the special action card or from the
returned action card.
The last subroutine punches out a new personnel deck (paragraph named 910-
PUNCH-SCHEDULE-CARDS).
TOTAL-PERSONNEL-CARDS (counter used when creating
the personnel table)is used to keep track of all personnel cards so that the
number of output cards will equal the input cards.
4.2.2
Initializing COBOL Tables
The Enforcement Management System requires that certain local data
be entered within the COBOL tables (see Tables
4.1 and 4.2) before the system
can be implemented.
Before any of the changes described below are made,
Section 3.0 of the Appendix should be fully read and implemented.
The Next Action Table is used to pick up the next action code which
will be used to schedule an action.
The table contains three levels; the
95
-------
agency and current action code (AGENCY-ACTION); a delay factor (DELAY-
SUBSCRIPT) for delaying the date next action can be scheduled; and the next
action code (NEXT-ACTION-TB).
Because each agency using the system could
require a different next action (e.g. registration following inspection, etc.),
the table is arranged in sequential order by agency and action code.
The
last entry should be agency 999 to stop the search.
The Date Table is used to pick up the month and day an action is to be
performed.
Since the schedule date represents a tentative date the action
can be performed (on or before), this table need not be changed.
If it is
desirable to change this table (e.g. all actions to be scheduled on Fridays,
etc.), all 52 entries must be changed.
Each entry should be one week (7 days)
apart.
Entries should be made in ascending order.
96
-------
.-. .
...--.-.-.- ...
.. ---.._-
43~(') 01
4-35 ()
4300
4370
43~O
43Q(\ ...
44:)0
441n
1..478
44,('0
444C
I..I..,~ ~,
441-,(',
447(1
44Q['\
4491')
45("\'"
- . --~ ---
FILLER.
03 N EXT --A C T -ION - r A 8 L E .
05 FILLER PICTURE 9(9) VALUE IS 001010102.
05 FILLE:R PICTURE 9(C) VALUE IS ooioz6ilY3-;----------
05 FILLER PICTURE 9(9) VALUE IS 001030104.
05 FILLEK PICTURE 9(9) VALUE IS 001040505.
05 FILLER PICTURE 9(9) VALUE IS 001050106.
05 F ILL E R F' I C T U R E 9 ( 9 1 V A L U E i S 00 106 -0107. - ---
05 FILLER PICTURE 9(91 VALUE IS 001070108.
~5 FILLER PICTURE 9(91 VALUE IS 001080103. -
05 FILLE~ PICTURE 9(9) VALUE IS 001090101.
.'-----ITS-rTll:tR- - "PITnJRr--gr9T'VALUE IS 999990197.
n3 RE-NEXT REDEFINES ~EXT-ACTION-TABLt.
05 FILLER OCCURS 10 TI~ES. -
07 AGE~CY-ACTIO~ PICTURE 9(51.
07 DELAY-SURSCRIPT PICTURE 99.
07 ~ExT-ACTION-TR PICTURE 99.
TRC4288
H' .- -----. - --. .- - .- . TRC4,,-S8
TRC4288
-fR C 42-88
TRC428~
TI-
-------
4560 01 FILLER.
4570 n3 DATE-TARLE.
-~-.f_~- () 5 F ILL E R
4590 05 FILLER
46nO 05 FILLER
4610 05 FILLER
462~ 05 FILLER
46~() 05 FILLER
4640 05 FILLER
. 46r;O'" - _. -- u_-05F ILLfR ..u_----o. ----
4660 05 FILLER
4670 05 FILLER
4o~n 05 FILLER
4690 05 FILLER
4700 05 FILLER
.---.--..- 47-1 fi"O-- -- .- ._-. "..-O~ILCER-~----"-" . --
47?0 05 FILLER
47~0 05 FILLER
474~ 05 FILLER
4750 05 FILLER
47~0 05 FILLER
4'770 - ----- -()5-'F-rILE;~-'
47~r 05 FILLER
47q~ 05 FILLE~
4R0~ 05 FILLER
4810 05 FILLE~
4820 05 FILLER
-q.' 4-8~n" ,------- --05--n-LLE'rr------- ,-
4840 05 FILLER
48~0 05 FILLER
48AnO; FILLE~
487~ 05' FILLER
I 4B'HI 05 FILLER
1---4R90--- -q---.- -05 FILLER--
49~~ 05 FILLER
4910 0; FILLER
4920 05 FILLER
4930 05 FILLER
4940 05 FILLER
491;-(') -,- 05 FI L L-r-~--" --, "
49~O 05 FILLER
4970 05 FILLER
49~O 05 FILLER
4990 05 FILLER
50no 05 FILLER
5-6 1 0 ------05FT L-LFR---
502(') 05 FILLER
5030 05 FILLER
5040 05 FILLER
50~0 ' 05 FILLER
50~O 05 FILLER
50 7 n 05 F I L L E R------ -'~-'..' - - -.- -- -
50~0 05 FILLER
5090 05 FILLER
5100 03 RE-DATE-TARLE REDEFI~ES
5110 05 TABLE-MONTH-DAY
- ----. - ___~_~RC~z.alo
TRC4288
TRC428f
TRC428f
TRC4286
-- - -- -- ..-
TRC428~
- -- - ___TB.c;~~_8J
TRC428l
, TRC4288
T- RC4288j
__T fiC~28~
TRC4288
TRC428f
- -- ---
TRC428i
TRC428t.
TRC428S
TRC428!
-.- ~ --- -
TRC428(
TRC4288
-.. -.-. -- ~-- ~- -
TRC42881
T RC428 8.
TRC4288
TRC428~
- .+.. ..----
TRC428i
TRC428l
T Rc-4-Z-S6
TRC4288
TRC4288
TRC4288
T RC'42tfF
TRC42BI
TRC428b
TRC42BA
TRC4281
TRC4281
- - T-RC4288
TRC4281
TRC428i
TRC428e
TRC42Sf
TRC4261
- - --- f R C 4-2 if!..
TRC4288
TRC-4281
TRC4281
Ti-\C4288
TRC428!
TRC4281
TRC428b
-.- -- ..- -- - -- ~_. -
,TRC42SP
TRC4281
TRC429L
TRC4288
--- -TRC-428-j
TRC4281
- nfRCi;za-B
PICTURE 9(4) VALUE 0102.
PICTURE 9(4) VALUE 0109.
PICTURE 9(4) VALUE 9116. .__n___-
PICTURE ~(4) VALUE,0123.
PICTURE 9(4) VALUE 0130.
- PICTU~E 9(4) VALUE 0206.
,----_:_£_~1~_~- 9.l.~-LY ALUE 0213.
PICTURE 9(4) VALUE 0220.
PICTURE 9 (4) VALUE 022I.,_u
PICTURE 9(4) VALUE 0306.
PICTURE 9(4) VALUE 0313.
PICTURE 9(4) VALUE 0320.
PICTURE 9(4) VALUE 0329.
_n'pTC-rURE-cn 4 ) VALUE 0403.
PICTURE 9(4) VALUE 0410.
. - - --- --- .-- --
PICTU~E 9(4) VALUE 0417.
PICTURE 9(4) VALUE 0424.
PICTURE 9(4) VALUE 050f.u--
PICTURE 9(4) VALUE 0508.
'--"-pTclu-r~( 9(4j--VALUE 0515.
PICTURE 9(4) V~LUE 0522.
PIC T U R E 9 ( 4) V A L U E 0 5 2 9'- ----
PICTURE 9(4) VALUE 0605.
PICTURE 9(4) VALUE 0612~-
PICTURE 9(4) VALUE 0619.
<---._. ----'---" --. pOI C TU RE ".9 -f4T-VALUE 0626.
PICTURE 9(4) VALUE 0703.
PICTURE 9(4) VALUE 0710.
PICTURE 9(4) VALUE 0717.
- -
PICTURE 9(4) VALUE 0724.
PICTURE 9(4) VALUE 0731.
-PICrURE-h-9T4-) VALUE 0807.
PICTURE 9(4) VALUE 0814.
PICTURE 9(4) VALUE 0821.
PICTURE 9(4) VALUE 0828.
PICTURE 9(4) VALUE 0904.
PICTURE 9(4) VALUE 0911.
PIcrmrr:-'}(4) VALUE 0918.
PICTURE 9(4) VALUE 0925.
PICTURE 9(4) VALUE,1002.
PICTURE 9(4) VALUE 1009.
PICTURE 9(4) VALUE 1016.
PICTURE 9(4) VALUE 1023.
'-'-----'---. P-ICTU~E---9-f4)' VALUE 1030.
PICTURE 9(4) VALUE 1106.
PICTURE 9(4) VALUE 1113.
PICTURE 9(4) VALUE 1120.
PICTURE 9(4) VALUE 1127.
PICTURE 9(4) VALUE 1204.
.pTCr-UR-E' 9-(4) VALUE 1211.
PICTURE 9(4) VAL~E 1218.
PICTURE 9(4) VALUE 1225.
DATE-TABLE.
PICTURE 9(4) OCCURS 52 TI~E~~
----- -
.-. --- --.
Table 4.2. Date table.
98
-. - --.
- .. - _.--
-------
5.0
MANUAL SYSTEM
5.1
'General Description
Some agencies may find it impractical to install either of. the
computerized systems described in the preceding sections.
A manual
version of the Enforcement Management System has been designed and is
presented in the following pages.
It is strongly urged, however, that
I
every effort be made to utilize the mechanized system, since the manual
system does not provide all the benefits available with the mechanized
system.
Valid reasons for installation of the manual system include:
o Non-availability of computer time.
o Lack of any qualified assistance to provide programming
maintenance for the computerized system.
o Turn-around time so slow at the only available computer
facility that use for this application is not feasible
at this time.
o A situation in which the agency has less than ten employees
and does not work closely with another air pollution agency
with whom the system can be shared
If the situation changes, making computerization possible, conversion
from the manual system will be readily accomplished.
The design of the
manual system is similar to that of the mechanized systems.
The data base
will be organized in suitable fashion for conversion to automated processing.
The manual system utilizes the same action card concept as the auto-
mated systems.
The "card," however, is changed to an 8-1/2 x II-inch sheet
for easy filing, and is printed in copy sets for easy handling.
The indivi-
dual source-oriented inputs are prepared manually and maintained in a file
book, one book per source.
Operational schedules are prepared for
I
I
'.
99
-------
individual staff members, and for organizational groups.
Some management
summaries are produced.
The source-oriented files should represent an
improvement over most presently-maintained systems.
Costs of the system are lower in the manual version, although certain
expenses for forms and filing devices are required.
The manual system re-
quires more vigorous management support to enable it to operate success-
fully.
Manual systems require a more experienced and/or qualified data
. bank coordinator than computer systems do, because the follow-up aspects
of the system are not automatic.
5.2
System Description
The system is best described in terms of its operation.
As an ex-
ample, assume an agency becomes aware of an unregistered source.
The data
bank coordinator (DBC) is advised and sets up a file for the source.
These
files are not ordinary file folders, but heavy-duty "sheet holders."
A
sheet holder is a holder with a heavy-weight board cover, rounded back,
steel spring clips, and an inner folder to facilitate insertion or removal
of inserts.
It holds pages up to 1 inch in thickness in a secure fashion,
and yet permits easy additions of pages at any point in the file (See
Figure 5.1).
Looseleaf notebooks may also be used, but the sheet holder
is preferred, because it is more compact and capable of accepting unpunched
sheets.
The source file book is set up with a number of standard sections,
delineated by pages with index tabs.
The sections are:
o Registration Data
o Current correspondence
100
-------
, "
Commercially available sheet holder
Files
Forms
Source File Books
Action Sheet Set
Individual Schedule Books
Emission Point Sheet
Section Schedule Books
Company Data Sheet
Suspense File
Overdue Action Form
Action Summary Form
Standard Letters
Source File Book Charge Out Sheet
Figure S.l.System files and recommended sheet holder.
101
-------
o
Past correspondence
o
Emission point sections
o
Cross references
This file is needed in any case, even with the computerized system,
but assumes vital importance with the manual system.
The sections are set up at once, and index tab divider sets are pre-
pared in advance so they can be "dropped in" as required.
These emission
point sections are included in each set, labled E-Point #1, #2 and #3.
These are for specific pollution emission activities at that source loca-
tion. . There may be more or less than three emission points for any given
source.
The number of sections can be adjusted to reflect the proper numbers.
When data are available, an index sheet is inserted in the Registration Data
section, indicating the emission point numbers assigned and the process re-
lated to each at the source location.
For example, E-point #1 might be a
boiler, E-point #2, a manufacturing process, and E-point #3, waste disposal.
Figure 5.2 shows an example of an emission point form, which can be varied
to reflect local usage.
Figure 5.3 shows an example of a company data sheet, which is placed in
the registration data section of the book.
The source file book is vital to the agency's operation.
Many staff
members will need to refer to the individual books, and may need to remove
them from the DBC's files.
50 that the books do not become lost, or mis-
placed for extended periods, it is recommended that a charge out system be
used.
A charge out sheet format is shown in Figure 5.4.
If a staff member
borrows a book, he fills out and leaves a charge out sl~p with the DBC, who
102
-------
AGENCY TITLE
EMISSION POINT DATA SHEET
I Emission Pt. No.
Source Nam~
Description of Emission Point
Registration No.
Permit No.
Fuel or Input Material
Annual Quantity
Pollutant Emissions
Type and Quantity
Control Device
Condition
Efficiency
(Show pollutant and
percentage)
Operational
pattern:
Hours per day
Days per week
Seasonal variation
Figure 5.2.
Emission point data sheet.
103
-------
AGENCY NAME
COMPANY DATA ~HEET
Source No.
Name of Company
Street Address at Emission Source
City
Zip Code
Area Code
Telephone
County
SIC Code
Person to Contact at this Address
Grid Coordinates
by NS
UTM Zone
EW
Description of Operation
st thi$ Address
Emission Points (use extra sheet if needed.)
1.
5.
2.
6.
3.
7.
4.
8.
Figure 5.3.
Company data sheet.
104
-------
CHARGE OUT SHEET
SOURCE FILE BOOK
Source Name
File Book User
Section
Date
Figure 5. 4.
Charge out sheet.
105
-------
monitors the length of time the books are retained by the various staff
members.
For the example of the unregistered source, the data bank coordinator
sets up the source file book, and puts in the company data sheet indicating
what information is known about the source.
The DBC then fills in an action
form, a sample of which is shown in Figure 5.5 through 5.9.
This is a five-
part carbon form with each sheet in the set a different color.
The five
parts are as follows:
o Action Copy (white)
o Source File Copy (blu~)
o Suspense Copy (yellow)
o Individual Schedule Copy (pink)
o Section Schedule Copy (green)
The form can be printed on pressure sensitive paper, which will reduce
the bulk of the form set.
Figure 5.10 shows the distribution of the various
copies of the form.
The action copy is sent to the staff member
(in this
case a girl in the clerical section) who will actually perform the action.
Her schedule book is also updated with the individual schedule copy.
The
source copy is entered in the source file books.
The section schedule copy
is filed in the Section Schedule Book, which is available to the Section
Head, and agency management at all levels.
The data bank coordinator retains
the suspense copy in the suspense file.
Several files were mentioned which have not been described.
The sus-
pense file consists of one or more sheet holders which serve as temporary 10-
cations for the suspense copy of the action sheet sets.
They hold a number of
106
-------
.CTr-N
Squrce Name
ACTION
iHEET
Address
COpy
t:NFORCEMENT
L..AGEr.'ENT
City
Telephone
Send Letter
SYS T E M
Action
I , I
Emission
Pt. No.
I I '/
to Source
Scheduled Date
Est. Hrs. to Complete
Today's Date
Staff Itember
Action Results
Section
Next Action
Staff Member
Estimated Hrs. to Complete
Section
Comments
ACTI01~S
RESULT3
No Further Action
Follow Next Step
Reschedule Action
Data Not Received
Other -- see
CO!!U!lents
LETTERS
Inspection
Registration
Plan Submissi,.on
Review with Source
Registration
Review
Plan Revie\v
. So~rce Tes tir.g
A. Q. Survey
Complaint Received
Other -- see Co~~cnts
01 Request Registration
02 Request Plan
03 Send Permit Application
04 Issue Permit
05 Issue Conditional Permit
06 Appear at Agency
07 Planned .Visit
08 . Registration Approval
Figure 5.5. Action Copy (white).
107
-------
ACTION
Source Name
SOU ICE r.1
COpy
SHEET
£NFORCEMENT
Address
MANAGEM ENT
Telephone
Send Letter
City
.--.SYSTEM
Ac tion
I " I
Emission
Pt. No.
f' I . ,
to Source
Scheduled Date
Est. Hrs. to Complete
Today's Date
Staff Uember
Action Results
Section:
Next Action
Staff Member
. Estimated Hrs. to Complete
Section
Comments
ACTIO:~S
RESULTS
LETTERS
01 Request Registration
02 Request Plan.
03 Send Permit Application
04. Issue Permit
05 Issue Conditional Permit
06 Appear at Agency
07 Planned Visit
08 . Registration Approval
Inspection
Registration
Plan Submission
Review with Source
Registration
Review
Plan Review
Source Testing
A. Q. Survey
Complaint Received'
Other -- see Comments
No Further Action
Follow Next Step
Reschedule Action
Data 'Not Received
Other-- see
Comments
Figure .5.6. Source File. Copy (blue).
108
-------
-t;I~G.n
SUSPENSE
Source Name
SHEET
~NFO!CCEMENT
COpy
Address
_-'NAGEM EN T
City
Telephone
Send Letter
. SYSTEM
I , I
Emission
" Pt. NQ.
I I 'I.
to Source
Action
Est. Hrs. to Complete
Scheduled Date
Today's Date
Staff l1ember
Action Results
Section
Next Action
Staff Member
Estimated Hrs. to Complete
Comments
Section
ACTIO:~S
Inspection
Registration
Plari Submissi~n
Review with Source
" Registration
Review
Plan Review
Sour~e Testing
A. Q. Survey
Complai11t Received
Other -- see Comments
RESULTS
LETTERS
No Further Action
Follow Next Ste~
Reschedule Action
. Data Not Received"
Other -- see
Comments
01
02
03
04
05
06
07
08
Request Registration
Request Plan
Send Permit Applicatio~
Issue Permit
Issue Conditional Permit.
Ap?ear at Agency
Planned Vi~it
. Registration Approval
Section 5.7,
Suspense Copy (yello11).
109
-------
- ACTION
INDIVIDUAL
SCHEDULE
SHEET
Source Name
ENFO~~E-M£'n
Address
. COpy
MANAGEMENT
City
Send Letter
__SYSTEM
Telephone
I. ,
Emission
Pt. NC).
I I ,
to Source.
Action
Est. Hrs. to Complete
Scheduled Date
Today's Date
Staff I!ember
Action Results
Section
Next Action
Staff Member
Estimated Hrs. to Complete
Comments
Section
ACTIO~~S
Inspection
Registration
Plan Submission
Review with Source
Registration
Review
Plan' Review
Source Testing
A. Q. Survey
Complaint Received
Other -- see C0mments
RESULTS
. LETTERS
No Further Action
Follow Next Step
Reschedule Action
Data Not Received
Other -- see
Comments
01 Request Registration
02 Request Plan
03 Send Permit Application
04 Issue Permit
05 Issue Conditional Permit
06 Appear at Agency
07Plann~d Visit
08 R~gistration Approval
Figure 5.8. Individual Schedule Copy (pink).
110
-------
[, dON
S ECT:Otf
Source Name
IE~ .
SCHEDULE
Address
COpy
ENFORC~MENT
-'AGEf~'ENT
City
Telephone
Send Letter
.iT E fd
Action
I , I
Emission
Pt. No.
, I i
to Source
Scheduled Date
Est. Hrs. to Complete
Today I S Date
Staff Hember
Action Results
Section
Next Action
Staff Member
Estimated Hrs. to Complete
Section
Counnents
ACTIO'{S
RESULTS
LETTERS
Inspection
Registration
Plan Submission
Review with Source
Regi~tration
Rev!e".,
Pl<:!!1 Review
Sour~e T\:!sting
A. Q. Survey
Complai~t Received
Other -- see Commen~s
No Further Action
Follow Next Step
Reschedule Action
Data ~ot Received
Other -'- see
Comments
01
02
03
04
05
06
07
08
Request Registration
Request Plan
Send Permit Application
Issue Permit
Issue C0nditional Permit
Appear at Ager.cy
Planned Visit
Registration App=o?al
Figure 5.9.
Section Schedule Copy (green).
111
-------
Data
Bank
Coordinator
Source File
Copy
c
Duplicate of
Act ion Copy
Originator
Action Copy
Suspense
Copy
Sched-
ule
Book
Sect ion
Schedule
Copy
o
Section
Schedule
Book
Figure ,5,10.
Action sheet set -distribution.
112
Section
Head
Source
File
Book
Copy to
Source Book
Letter to
Source
~
-------
dividers which are tagged by month for the 12 months of the year.
The
suspense copies are filed in sequence of schedule date under the proper
month.
The individual schedule books and the section books are similar.
There is one schedule book for each individual.
The pink schedule copy is
entered in the schedule book of the individual who will perform the action.
The green section copy goes in the Section Book.
The updating of the
schedule books is done by the data bank coordinator, who has regular access
to these books.
The question of who performs what function is a significant one.
In-
dividua1 agency practice will differ, based on personnel available, work-
load, and other factors.
The action sheet set may have been completely
filled out by the originator or the data, or he may have relied on the data
bank coordinator for assistance.
For a registration request to a source the.
data bank coordinator would probably know just how to proceed.
In other
cases, she might have to refer the matter to a section head or other admini-
strator for guidance concerning who should handle a particular action or what
the next step should be.
The source may respond to the request for registration within a reason-
able time, or it may not.
A reasonable time is d~fined as the scheduled date
established at the time the Action Set was filled out.
The clerical section
has the Action Copy, and should return it if the registration is not received.
Figure 5.11 shows this action copy as it is returned to the data bank coordinator,
including the additional correspondence from the cleri~a1 section.
113
-------
ACTION
R~.DAJOX hE 7AL5
Source Name
ACTION
SHEET
EnfOnCEMENT
MANAGEMENT
~?/ O.,,4.k AI/£"'
Address
. S/~rl3'4~I/.
City. ,
(( S(.,../J 7~ATI() AJ
Action
sc~~~~?J
If} // () /') I
Today's D!ite .
~ Nt,.
Staff l1ember
COpy
2QJ-~.5"tP- 9// /
Telephone
Send Letter
0/
Est. Hrs. to Complete
I ,. I
Emission
. Pt. No.
10. II
to Source
..SYSTEM
C ler,' CAL
Section
Action R~l~ ~~ -
121 .- _L ./ ~ -.A C-- T" .LV
.
Next Action
Staff Member
Estimated Hrs. to CORplete
Section
Conunents
l( ~ Jj JV d re
kf ~ s::.. f-' D~ A V ,J
,
r t'J~. F,orH) A.ShJ
a v '-HtJAl6-.
,
tJ AI J;;"
ACTIO:~S
RESULTS
LETTERS
--
Insp.ection
Registration
Plan Subtr.ission
Review with Source
Registration
Review
Plan Revi.=:,'
Source Testing
A. Q. Survey
Complaint Received
Other -- see CO~T.ents
No Further Action
Follow Next Step
Reschedule Action
Data Net Received
Other -- see
Comments
01 Request Registration
02 Reques~ ?lan
03 Send Permit Application
04 Issue Permit
05 Issue Co~jitio~al Permit
06 Appear at Agency
07 Plrtnned Visit
08 . Registration Approval
114
Figure 5.11.
Filled in action sheet.
-------
If the source responds by sending in the registration, the Action Copy
is returned and filled in as shown in Figure 5.12.
The following actions then
take place:
o A next action is scheduled on the form and assigned to a staff.
member as indicated.
o The data
Suspense
Suspense
bank coordinator matches the Suspense Copy (in the
file) with the returned Action Copy, and discards the
Copy.
o The data bank coordinator enters the scheduled action on the
Action Summary Form.
o The DBC matches the Source File Copy in the Source
with the returned Action Copy, and updates it with
Copy.
File Book
the Action
o The DBC fills out a new Action Sheet Set.
o The copies of the Action Sheet Set are distributed, as before.
In the case of the new Action Sheet Set, an engineer has been assigned
to review the registration form.
If the review indicates control action is
needed, he will probably schedule a "review with source."
Every action goes
through the same cycle.
For instance, in the example we have discussed, these
steps might be followed:
o Review with source
o Submission of compliance plan by source
o Review of plan by agency
o Issue conditional permit
o Inspection
o Issue permit
o Inspection (future)
Each action is tracked and monitored by way of the Action Sheet Set, and
the associated processing.
115
-------
ACTION
R~D/"JO/?
Source Name
/'1 &7~
ACTION
SHEET
ENFORCEMENT
4-?/
Address
(JAw
AVE.
COpy
MANAGEMENT
~ 1M r gU/f,V
ty
(? Jii.(_IL1 rIP A- TIO"I
Action
10 /2f/? /
Scpecfuled te
1e(it'Jh I
Tod 's D~te
l.o.} - 6 ~eP - '1// /
Telephone
Send Letter
- .SYSTEM
,. ,
Emission
. Pt. No.
IO,~,
to Source
n/
Est. Hrs. to Complete
~ k/IV ~
Staf l1ember
c.ll!Ail'~
Section
Action
R~lts '~
~-~41--:'. ~-d
Fa IldLtJ Ai L k-r STe/<,
Next Action .
J(~Cr'JJ~TION ;(~JE-I¥
~( 130 ~/4JG;
Staff r ember
D~ .
Estimated rs. to Complete
EN~NGb~/A/{,...
Section
Comments
ACTIO~{S
RESULTS
LETTERS
Inspection
Registration
Plan Submission
Review with Sou~ce
Registration
Review
Plan Review
Source Testing
A. Q. Survey
Complaint Received
Other -- see Comments
No Further Action
Follow l~ext Step
Reschedule Action
Data Net Received
Other -- see
Comments
01 Request Registration
02 Request Plan
03 Send Permit Application
04 Issue Permit
05 Issue Conditional Permit
06 Appear at Agency
07 Planned Visit
08 . Registration Approval
116
Figure 5.12.
Filled in action sheet.
-------
On a regular basis, the data bank coordinator prepares various forms
and reports to summarize agency activities.
The action summary report
(Form shown in Figure 5.13) is prepared for each section periodically and
records all actions for the individual section.
The reports are also re-
produced and made available to the agency director, who may make further
distribution after review.
The Action summary report is prepared entry-by-
entry as actions are completed and the returned action copy passes the desk
of the data bank coordinator.
The overdue action report format is shown in Figure 5.14.
This report
is prepared by the data bank coordinator on a periodic basis;
it is recom-
mended that this interval be biweekly.
The report is prepared by reviewing
the suspense book maintained by the DBC.
AnY,action which has passed its
scheduled date is listed.
Note that a rescheduled action is not listed on
the report.
However, a new action sheet set is required to reschedule an
action.
The report is reproduced, copies are sent to the agency director,
and individual pages are sent to section heads responsible for specific
activities.
5.3
Data Bank Coordinator
The position of data bank coordinator is a very significant one to the
success of the manual Enforcement Management System.
For all but the smallest
agencies, we recommend that this position be full-time.
This is not a net
addition to staff, since the system functions that will be performed by the
coordinator replace existing functions that would have been performed in any
case.
117
-------
AGENCY TITLE
ACTION SmNARY
Section
Period Covered
Date of Report
Staff :lember
Title
Source Name
Action
Result
Date of
Action
Next Action
Date
Figure c .13. Action s mmary report.
118
-------
Section
Scheduled
Date
Planned
Action
AGENCY TITLE
OVERDUE ACTION REPORT
Period Covered
Date of Report
Company
Name
Staff
Hember
Title
Figure 5.14. Overdue acticn report.
119
-------
The coordinator's qualifications should be as follows:
o Relatively experienced in air pollution control agency office
procedures. Experienced in dealing with people at all levels.
o High school graduate with some college or equivalent training.
o In a small agency, typing and general secretarial abilities
are also required.
The exact functions of the data bank coordinator will vary with agency
size and practice.
In the smaller agency, the coordinator may perform his
own typing task and do considerable file update.
In the larger agency this
will be done by others.
Generally speaking, however, we strongly recommend
that this individual not be assigned tasks, (such as routine correspondence,)
which are unrelated to operation of the Enforcement Management System.
The functions to be performed by the data bank coordinator will vary
as indicated above.
In general they are as follows:
o Provide training for new staff members and others in the use of
the Enforcement Management System.
o Maintain the source file books and control their use by staff
members.
o Maintain the suspense file containing the suspense copies of
the action sheet sets
o Prepare and distribute overdue action reports.
o Provide assistance to all staff members in filling out Action
Sheet Sets. Fill out these forms where appropriate without
assistance from other staff members.
o Review workloads with section heads, working with the schedule
book. This involves making available the workload assigned
(via a review of the Section's Schedule copies of the action
sheets). This interaction with the Section Heads should pro-
vide a clearer picture of the existing'and future workloads
so that these section heads can make informed management de-
cisions in the operatio~ of their sections. The time periods
assigned to actions that are being scheduled will be assigned
during the review.
120
-------
5.4
System Support
Operation of the manual version of the system will vary from agency to
agency.
In some cases only portions of the system will be utilized based
on local considerations.
Figure 5.15 indicates the general relationship of
the system operation within the agency and with pollution sources.
The performance of data bank coordinator is a very significant factor
in the d~gree of success the system will achieve within any particular agency.
His relationship with the various technical staff and the support he receives
from management are key factors.
A backup coordinator should be designated
since vacation or illness would remove the DBC from the scene from time to
time.
This person should be trained with the coordinator so that the system
continues to function during absences.
The section head must actively support the system to achieve benefits
from it.
The operation of the system provides a means for an individual
section head to improve management of his group.
If an individual section
head is not utilizing the system or feels it is not providing any advantage
to him or to his people, investigation should be made by the agency director
to make sure that proper usage is being made of the system features.
Some
smaller sections headed by individuals who prefer to operate on an ad-hoc
basis may never derive substantial benefits.
However, it is worthwhile to
include even these small sections in the system so that the source files
will contain compatible information about their interactions with the indivi-
dual sources.
The highest levels of agency management must believ~ in and support the
system if it is to succeed.
Periodically the progress and results should be
reviewed with the Section Heads.
When reports are produced, such as the
121
-------
......
N
N
.r;;;
L~k_-':J
I :
Figure 5.15. Gener~1ized system operation.
Source
-------
Overdue action report, or the action summary, the director should make it a
special point to refer to them, to ask questions about them and to utilize
them as official documents of the agency.
In this way, various Btaff personnel
will become familiar with these reports.
5.5
Start Up
Startup for the manual version of the Enforcement Management System is
somewhat easier than that for the computerized versions.
The milestone chart
in Figure 5.16 indicates the basic steps that should be followed in beginning
.the operation.
The following paragraphs describe each of 11 generalized
steps which when followed in sequence should bring an agency to operational
readiness in the use of the manual Enforcement Management System.
1.
Adjust forms to local' practice.
The design of the forms
may evolve within an agency and vary from agency to agency.
In
particular the Action Sheet will require modification to reflect
local practice.
Actions, results and letters (to be sent out)
will vary based on local regulations.
The local director and his
staff should review agency operations and select the actions and
letters that seem most appropriate to their own particular opera-
tion.
2.
Obtain forms and other supplies.
This activity involves ordering
the printing of the seven forms and obtaining other supplies neces-
sary for system operation.
Figure 5-1 indicates the necessary items.
The files are designed to utilize sheet holders described in an earlier
section.
Three ring binders can be substituted, but we feel that
the sheet holders make updatiug of the file easier and avoid punching
123
-------
6. Convert
Source Files ~
to EMS SourcE
. ~.. V File Books
1.. Adjust 2. Obtain 3. Select Data 4. Hold 5. Select
Forms To ~ Forms and Bank Coordinator- General Meet- Section For
Local Other Establish Won ing to DescribE ~ Initial Sys-
Practice Supplies Area System tern Usage ~
.--,- ...
7. Train Sec-
tion Person- ~
nel in System
Usage
t-'
N
.,..
-t!. Begln. 9. Review 10. Select Additiona 11. Expand System
System .System Ope- Section for System to all Agency Sec-
Operation ~ rations ,Per- Expansion tions Involved witt
form Retrain Sources
Figure 5.16.
Manual system start-up.
i.
I
-------
holes in the various forms.
Many of the forms can be produced using
simple xerographic or multilith techniques.
The Action Sheets Sets,
however, should be sent to a printer once the final format has been
agreed upon.
3.
Select data bank c.oordinator and establish work area.
The require-
ments for the person who is to become the data bank coordinator are
discussed above.
It is important to establish an appropriate work
area for the coorjinatoT.
The work area should be centrally located
with adequate filing space for a sheet holder for each major source
contacted by the agency.
The files which hold the Source File Books
should have locks for security purposes.
The central location of
the coordinator's work area encourages coordination and discussion
of problems with the various staff personnel of the agency.
In
addition, the Source File Books should be readily accessible to agency
personnel.
4.
Hold general meeting to describe system.
An agencywide meeting
should be held to describe the system and discuss the results that
are expected from it.
The system should be presented in a positive
fashion, as an aid to reducing confusion and improving control of
activities.
The system benefit of better availability of information
should be emphasized.
5.
Select section for initial system usage.
We recommend that the
system be installed in easy stages.
Operations can begin with a
single section, preferably one of the engineering sections (if there
are more
than one).
A section should be selected on the basis of
its need for a system of this type, to ease data handling and re-
trieval problems.
125
-------
\ ~--
6.
Convert Source Files to EMS Source File Books.
This involves
gathering the source related material relating to the sources by
the personnel of the selected section and converting it to the
Enforcement Management System source file book format.
For existing
sources this will mean taking the data and extracting the needed
information from the company data sheets and emission point
sheets.
The data are entered on the index sheet and included in
the registration data section.
The company data sheets are then
filed with the other material in the sheet holders which make up the
source file books.
7.
The data bank coordinator
Train section personnel in system usage.
trains the personnel of the section selected for the initial ap-
plication in the operation of the system.
This initial session should
last from 1 to 2 hours and should involve actual examples of how to
fill out the action sheets.
The various schedules should be ex-
plained and the availability of the schedule books should be
emphasized.
8.
Operation is ,begun by filling ou~ action
Begin system operation.
sheets for the activity schedule for the next week.
This can be
done at the end of the training session for some actions;
the
remaining actions can be filled out later.
9.
The operation of
Review system operation, perform retraining.
the system should be reviewed after implementation.
Any necessary
retraining should be performed and problems s~ould be resolved.
The details of system operation should be discussed.
During these
sessions, communication should be emphasized.
For example, in
126
-------
filling out a new Action Sheet an inspector may be unable to establish
a schedule date for the next action.
It may be that this type of
problem requires coordinating the action sheet set with another staff
member before it is handed in to the data bank coordinator.
10.
Select additional sections for system expansion.
The remaining
engineering sections can be brought into the system.
Sections
whose work relates to engineering (source inventory, source
monitoring) are added with time.
In this way, the system will
encompass a continually expanding portion of the agency operation.
11.
Expand system to all agency sections.
Since the entire agency
should eventually be included in the system operation.
Staff
members dealing primarily with air quality measurements should
be included to provide input from those activities which involve
specific sources.
127
-------
6.0
ALERT HANDLING
The computerized Enforcement Management System is designed to facili-
tate the activities to be accomplished during an air pollution episode or
alert.
Emission reduction plans are formulated in advance with the source
operators.
The plans require specific actions to be taken by various
people in the agency to ascertain the stage of the alert to intiate re-
qui red responses.
These activities fall into two general categories:
o Actions related to specific emission sources, such as surveil-
lance of operational shutdown or reduction in emissions during
an alert.
o Actions unrelated to emission sources but concerned with
activities such as issuance of news releases, contact with
public officials, special air quality monitoring assignments.
Handling of actions related to specific emission sources involves the
creation of an action record (using the manual action card form) on the
master file.
This action appears on the individual and group future
schedule summaries.
It is specially coded to indicate that the action is
only to be performed during an alert.
This is done by scheduling the action
for a date in the 1990's.
The comments entered with the action also specify
that it is associated with an alert.
There are different activities asso-
ciated with each level of alert.
These actions are assigned to different
years in the 1990's.
Examples are to code Forecast as 1995;
Alert as 1996;
Warning as 1997;
Emergency as 1998;
and All Clear as 1999.
The various
actions can be added to the system at different times as compliance agree-
ments are negotiated with various emission sources.
The planned actions for
that source become a part of the emissions reduction activity.
Similarly ~
source actions are updated by changes or deletions of specific activities.
128
-------
1-
Alert actions not associated with any specific source require dif-
ferent handling.
This consists of entering a special source into the
system files to provide a basic record for area-wide alert actio~s.
All
actions for a given area are entered under this source number which then
appears on the appropriate schedules, ,.,ith the title "Alert Center" in the
source name field.
This entry should be made using the normal forms.
Assignment of alert actions may vary from one agency to another.
In
some cases, the actions may be assigned to specific staff members.
Other
agencies may prefer to assign the actions to a title, such as "senior
alert officer."
In this case, the "senior alert officer" should be as-
signed a spot in the personnel deck, and carried as a staff member.
129
-------
t
Alert
Action
Data
Enforcement
Management
System
Forecast
Level
Schedule
All
Clear
Schedule
Figure 6.1.
Schematic, processing of alert data.
130
-------
7.0
COMPLAINT HANDLING
The Enforcement Management System is designed to process complaint
data, and to monitor and record these activities in order to improve the
effectiveness of complaint handing.
Complaints can be divided into two groups:
o Those concerned with a specific and known source whose acti-
vities are detailed in the agency's files, and in the system.
o Those dealing with generalized problems (such as an unidenti-
fied odor), with unregistered sources, or with emissions sources
so small and localized that they are exempt from regulations.
Handling of
complaints on known sources is similar to the handling of
normal source actions.
The receipt of the complaint is regarded as an
"action" in itself, and is so recorded in the system.
If it is quickly
resolved, such as by a phone response, the action is complete.
An action
card is fed into the system with the NO FURTHER ACTION option circled, and
any appropriate comments are entered.
For example, a complaint might deal
with a situation which is in the process of being corrected.
The person
making the complaint would be informed of the corrective action, and the
date that the corrective action would be complete.
If the complaint cannot
be quickly resolved, and an inspection or other activity is indi~ated, the
action card is fed to the system with the next action indicated and the name
of the staff member who is to perform the task.
From then on, of course,
the process takes on the form of normal activity.
An inspection may lead to
a source test, a registration, or other activity, which is monitored as in-
dicated in the system descriptions.
131
-------
The case of a complaint that is not directly connected with a known
source poses a different problem.
Figure 7-1 shows the steps to be fol-
lowed (availability of all system products is assumed).
After "the complaint
has been received, it is entered into the system associated with a "general
source," maintained in the system for this purpose.
A smaller agency may
maintain one such record, while a larger agency will have a larger number
of such "general sources," one for each major geographic subdivision. These
sources have a pre-assigned number for the emission point.
This number is
associated with each of these non-specific complaints as they are received.
Several complaints may be associated with this one number.
Complaints re-
lated to an apparently different source are associated with a different
emission point number.
Through the particulars of the complaint, or through knowledge of
events in the area, the agency may make a general assessment as to the
general validity of the complaint facts, and this is entered into the
system as "comments."
Next, the geographic locator is consulted for likely sources of the
problem.
The locator shows all registered sources in sequence by grid
square and also by street address.
Using a general knowledge of prevailing
meteorological conditions, the grid square or address upwind of the complaint
location is noted.
This step forms a review of the probable type of emis-
sions and the proximity of likely sources.
Next, an inspection of the complaint site is scheduled.
If a single
source is suspected, the inspection centers upon that source.
If the problem
132
-------
Review in
terms of general
abatement
strategy
no
rej ect
Receive Complaint and
all associated detail
(t
Review for
validity of
complaint
Discuss with
Complaint
Originator
valid
Consult Geographic
Locator for likely.,
Sources of Problem
'"
'-
Inspect site of
,complaint, perform
'quality survey if
indicated
air
t yes
Inspect Source,
Determine if
Violation
Figure 7.1.
General complaint handling schematic.
Review Problem
\.,i th Source
+
Receive and review
Source Compliance
Plan
~
/A ?"continue to monitorl
pprove or approve ,
. t PI Source Compl~ance I
re] ec an
Plan based on I
Submit.ted Schedule.
'" 133 --~
-------
is still undefined, an area survey is performed, perhaps supplemented
with actual air quality rea~ings by either mobile or stationary instru-
ments.
The results of the survey may lead to the discovery of an unregistered
source, may indicate an operational change in a known source, or may not
point to any specific emissions source.
In the case of a general problem
with multiple sources involved, a review of abatement strategy for the area
is indicated.
This may involve continuing air quality surveillance and
ultimate review of a large number of sources.
Such enforcement activities
are tracked and monitored by the system, still associated with the specific
complaint, until abatement of specific sources is undertaken.
General
strategy assessment is not monitored, although comments associated with
the complaint resolution may indicate that this assessment is taking place.
Where a particular point is identified as the cause of the problem, the
agency's role becomes more routine.
An inspection is scheduled with an
action card, and the results dictate the next actions, such as registration
(if a new source), correction of control device failure, submission of a
plan for additional emissions reduction, or legal action.
When the com-
plaint is matched to a specific source, the processing is closed out under
the general "dummy" source entry and further activity is coded with the
source number of the now-known emission source.
The original complaint
record stays with the general entry, and the comments specify the source
that was eventually associated with the complaint.
134
-------
In certain cases local agencies may handle a complaint on "quick re-
sponse basis."
For example, ~ phone complaint may be received reporting
a smoke problem and the local agency may dispatch an inspector by radio.
The inspector may resolve the problem on the spot, as in the case when a
simple adjustment is needed to an incinerator control device.
Since the
Enforcement Management SYstem does not operate in real-time, but rath€r
produces its various reports, action cards and schedules on a "batch" basis,
it is not possible to handle this type of complaint through the regular
scheduling routines of the system.
In most cases, however, such complaints
should be entered into the system for historical and reporting purposes.
This will be particularly true in cases where the pollution source is
being carried in the Data Base.
In other cases where the source is not
carried in the Data Base, local agencies may not want to enter such actions
into the system.
An example of this might be a complaint about emissions
from an individual house or small retail establishment not considered a
major source of pollution by the local agency.
When a complaint is to be
entered into the Data Base after the action has been completed, the special
action card format should be utilized.
This is described in detail in
Section
3.0 .
If the complaint activity is entered in this way, the system
will include the action on the various management oriented summaries that
are prepared, and in addition,will show the complaint on the source actions
summary for the individual pollution source.
In this way the agencies records
will be complete regarding both the staff activity and the action related to
135
-------
the specific source. A special action card can also be used to schedule a
future agency action to follow up on the activity which has already been
completed.
For example, an inspection might be scheduled 30 days later
to determine that the initial corrective action was adequate and was
still providing control of the problem which had caused the initial complaint.
If this additional inspection is entered into the system by means of the
special action card, the normal scheduling and reporting functions of the
system will track, monitor and record that action, just as is done in other
types of activity.
136
-------
8.0
AIR QUALITY RELATIONSHIP
The Enforcement Management System can be an aid to agency personnel
as they review air quality readings.
For example, in interpreting the significance of air quality levels
at a particular point, the agency staff may wish to review the sources which
are making a contribution to pollutant levels at that location.
Reference
to the geographic locater which is arranged by grid square would indicate
pollutant sources which are likely significant contributors to the air
quality at a particular point.
Reference to the source registration printout
will indicate the types of pollutant being emitted from the individual sources
known to the agency.
This will potentially eliminate some of the sources.
For example if the S02 level at a particular point is being analyzed, sources
emitting only particulates can be eliminated.
If a specific agency has not "gridded" the sources being processed by
the system, the geographic locator which lists sources by city and street
address will provide an indication of the potential contributor to pollutant
levels at a particular point.
Various types of simulation models can be utilized to further estimate
the contribution from the various sources that have already been jdentified
as described above.
If the emissions from these sources can be quantified
for the period covered by the air quality readings, single source models
can be used to calculate the downwind concentration from the specific source.
More comprehensive models can be utilized to incorporate all pertinent sources
into the calculation.
These can be of the manual model 'type or short-term
models which make predictions based on specific parameters, including
137
-------
meteorology, seasonal factors, heating load information, and diurnal
factors related to the individual sources.
Adding successful calibrated models of these types to the situation
so that the model predictions approximate the actual readings, the agency
can go on to simulate the effects of various abatement strategy.
For
example, the installation of various types of control equipment (with ap-
propriate percentage reduction of emissions) can be simulated by the model
and the improvement in air quality levels can be estimated.
Contribution from so-called area sources must also be considered in
these calculations.
Emissions from sources such as automobiles, home
heating and minor commercial activities can make a significant difference
in pollutant levels which are recorded.
Various models which are either
available or being developed take these factors into consideration in various
ways.
Entries may be made for the various types of area sources and adopted
to the periods being modeled, or, for the simpler model versions, a single
background concentration level may be included in either the mechanized or
subsequent manual calculations.
138
-------
APPENDIX
139
-------
APPENDIX
This appendix presents technical details of the computerized systems.
It consists of the following sections:
1.
System Narrative-Overview
2.
Program Narrative
1.
Program 1 - Update
2.
Program 2 - Extract
3.
Program 3 - Print run
4.
Description of Sort 1 and 2
3.
Startup Procedures
1.
Initializing COBOL Tables
2.
Building the Initial Master File
4.
Edit Descriptions
5.
Operating Instructions
1.
Request for computer processing
2.
JCL for IBM 360 DOS and OS
6.
Master File Record Layouts
7.
Control Card Layout
8.
Personnel and Letter Card Layout
9.
Keypunch Instructions
Source decks, program listings, and flow charts are available upon
request through the appropriate Regional Office or by writing to:
Lloyd M. Hedgepeth
Environmental Protection Agency
Office of Air Programs
Research Triangle Park, N. C.
27711
141
-------
1.0
SYSTEM NARRATIVE - OVERVIEW
The Enforcement Management System is under the direct control of the
Data Bank Coordinator.
His responsibilities will be to schedule computer
time and services;
review data input forms before keypunching;
and prepare
a current control card.
Once these functions have been completed and the
forms routed to their correct destinations (e.g. input-preparation. com-
puter center. etc.) the automated computer system will be activated.
Figure
1.1 depicts the complete system and the flow of data through it.
Transactions (new sources. manual action cards. changes to the master
file. deletions and returned action cards) are placed on magnetic tape by
using a standard card to tape utility.
This step may be eliminated if
input is produced by a key-tape~ key-disk or similar uevice.
The first sort arranges the random transactions into the same sequence
as the master file.
The sort key is the first 19 characters of the tran-
saction record.
It includes agency number. county. source number. emission
point. action number. card type. and comment line number.
The "low order"
(comment line number) will only affect the sort when there are "comment"
cards.
The sorted transaction file is used as "input" to the update program.
All transactions are validated and. if found to be error-free, will be
applied to the existing master file data.
The update program also schedules
new actions, assigns staff members to both sources and specific actions, re-
schedules appropriate actions, and prints an edit and error report. reflecting
all activities against the master file.
The extract program accepts the newly created master file as input.
142
-------
. '"'1
lactiu:1 ca~cs' I
. ~I'
misc(:lla:-:~"u';l
data -
first s~
sort - I
transactio:t
file
update
run
extract
run
. ~ sorted
lett~rs & J' . data .
ili~ri"
geograrhic ~-- . ~letter
locat
-------
The first record on the file is the control record which was created by
the update program from the control card.
This record contains the basic
information concerning which reports are required during this cycle.
Data
is taken off the master file and written on the extract file based on each
of the report requirements.
One master file field may appear on several
reports (e.g. source name);
therefore, as many as 10 different extract re-
cords could be created.
This requires adding a "prefix" to the basic data
records so that they can be sorted correctly.
The sort keys are discussed
under section 2.2 of this appendix.
The extract file is then used as input to the second sort.
The records
are arranged in the same sequence in which they are to appear within the
printed reports.
The output tape (known as the "extract tape") contains all
data necessary to produce the desired reports, letters and new action cards.
The sorted extract tape as well as the letter deck are inputed into
the print program.
The letter deck contains the body of the letters as
well as the names of the people who are to sign them.
Since the same letter
could be sent to different sources, one entire 1etfer is saved within memory
until a different letter is called for by the extract tape file.
In order
to accomplish this the letter deck must be sorted in agency, and letter type
order (columns 3 through 7).
The print tape information is "formatted" into
the individual report requirements and can be printed "on-line", or "spooled"
to be printed later.
Action cards are created using specially preprinted
punch cards.
The individual letters are generated (with necessary carriage
controls), and written as a separate file to magnetic tape.
At the conclusion
of the print run, the correct agency forms are placed on the printer and the
letters are produced using a standaru tape-to-print utility.
144
-------
The Action cards are interpreted, the reports separated, and the carbons
removed.
The entire package is sent back to the data bank coordinator who
will disseminate the reports and Action cards to the various agencies using
the system.
145
-------
2.0
PROGRAM NARRATIVES
2.1
Program 1 - Update
This is the first COBOL program of the Enforcement Management System.
Its basic functions are:
validating of all transactions entering the
system;
adding new sources to the master file;
changing existing records
on the master file;
removing (deleting) existing records from the master
file;
and assigning staff members to sources and specific actions.
All dates (date scheduled, date performed, today's date, etc.)
entering the system are checked for a valid month (1-12), a valid day
(1-31), and a valid year (not before 1960).
When dates are validated,
they are reversed from month, day, and year, to year, month, and day
(within paragraph named l04-DATE-FLOPPING).
The two reasons for "flopping"
the dates are:
a.
date compares can be one statement, and
b.
when used within a sort key, records will be arranged in
correct chronological order.
To prevent an action from being omitted from any of the reports be-
cause of an invalid or missing date, the system "plugs in" dates as needed.
If the returning action card does not have a performed date (date action
was accomplished), the program uses the run date (today's date from the control
card) in its place.
In the same manner, if the scheduled date (date the
next or current action is to take place) is omitted, the system schedules the
action 1 month into the future.
This is accomplished by using the run
date and adding one month to it;
for example, if today's date is 10-01-71,
146
-------
then the scheduled date is 11-01-71.
.When the action card is returned with a next action to be performed,
the results of the current action are placed on the current action record,
and any pertinent data for the next action will be put on a separate record.
Since action numbers are in ascending sequence, and since placing the next
action record immediately after the current one could duplicate the fol-
lowing action record's number, the next action data must be "stored" to be
used later
(See Figure 2.1).
The program will allow.up to three records
to be held in a "work area"
(TRANSACTION-HOLD);
any additional records will
overlay each other.
When there is a logical break within either the transaction
file or the master file, the "stored" action records are written out to the
updated master file.
Records on the master file can be removed by using a delete card
("D" in column 80 of transaction card).
Figure 2.2 describes the format of
a typical source on the master file.
Records may be deleted in one of three
ways:
a.
remove
the entire source (exhibit A) .
b.
remove one emission point and all actions related to it
(exhibit B)
c.
remove one action and all comments (exhibit C).
It is necessary to use the correct coding on the delete card to remove
the desired record(s).
Referring to F.igure 2.2, records can be deleted
as following:
a.
When emission point and action number fields are zeros the
entire source will be removed.
Exhibit A of Figure 2.2 depicts
this.
All records (emission point, action, comments, etc.)
pertinent to one source are removed.
147
-------
91o-NEW-ACTION-RECORD
From Change or Add
Logic
No )/ Yes
/ s .'.'."-.,.
.' switch /.
on? --
Yes
~
t
I
{
I
i
Format
output
record
Write'
new
\.
-- M/F
No ,
More
Stored? .
"
Figure 2.1.
Max. 3 Transactions
to be saved
Turn switch on
Break is new source,
new emission point, or
new transaction
Old M/F
Ac t. II
1
2 Next
3
.4 Next
5
New M/F
Ac t . II 1
Acti0:=1 ;,
~~tion~
Adding new action ~ecord to master file.
148
-------
E
Source Information
, 20
.
Source Comments
Line Number 1
Generated by Program
Source Comments
Line Number 2
Optional
Source Comments
Line Number 3
i' Optional 21 Emission, Actions
I
Emission Point
Information
34
Exhibit
Emission Comments A
Line Number 1
Optional 35
Emission Comments
Line Number 2
Optional 35
Actions Onl
Action Record 1 Exhibit
".", B
Exhibit
Action Comments
Line Number 1 .C
Optional
Action Comments
Line Number 2
Optional 37
Exhibit
Action Record 2 C
36
Action Record 3 Exhibit
C
36
Figure
2.2.
Master file format and
delete
logic.
149
-------
b.
When only the action number field is zero, one emission
point record will be removed.
Exhibit B of Figure 2.2
depicts this.
One entire emission point and its related
action and comment records are removed.
c.
When neither the emission point or action number fields are
zeros, but a "D" is in column 80 (update code), one action
will be deleted.
Exhibit C of Figure 2.2 depicts this.. One
action record and its related comment records (if any are
present) are removed.
To save excessive input preparation, the update program eliminates as
much of the redundant work as possible.
When a change is required, only
the desired field need be entered.
Any other fields should be left blank
and will not affect the file.
To eliminate (replace valid data by spaces)
a field within a record, one or more asterisks are inserted within the
field to be eliminated (change card).
The program translates asterisks to
non-printable characters (HEX 41) and replaces the existing field on the
master file with this "odd" field (this works only on alphabetic field;
numeric fields should be "zeroed out").
Before writing the new master file,
the "odd" characters are translated into spaces.
When new actions enter the system, they need not contain the correct
action number;
instead, they can be coded either 99 or 00.
The program
places the new action record at the end of a string of existing actions
(within agency, county, source, and emission point) and inserts the correct
action number within the record (one higher than the last action number on
the master file).
This procedure eliminates the need to cross-reference
150
-------
the source action report before entering a new action.
An action can be directed against an entire source, rather than a
specific emission point.
For this reason an emission point 000,. with
the term "entire source" as its description, is automatically generated
each time a new source is added to the Raster file.
Since the personnel file (card deck) onLY enters the system througt
the update run, the staff member's name and title must be saved for future
use.
For the source record, the name
of the inspector and the engineer
can be found on record t~pe 21.
Since record type 21 is used as a comment
record and the number of records is variable, the names are found only on
the first source comment record.
This means that there will always be a
record 21 (line number 1), whether or not there are source comments.
The
assigned staff member's name and title are stored on the action record
type 36 (this is done in case they are different from the assigned staff
members within record type 21).
Names stored by the system are not
accessible to the user through changes but will be changed when there is
a change to an assigned staff member.
This is accomplished through the
program and requires no special coding.
2.2
Program 2 - Extract
The second COBOL program of the Enforcement Management System is used
to extract data necessary to produce the required individual reports.
The
program is divided into two distinct logic paths:
Report Selection and
Data Selection.
2.2.1
Report Selection
The control card, which was read into the system via the update
151
-------
..
program, is carried as the first record on the newly-created master
file.
The "report sel~ction fields" (column three to eight of the control
card) are used to turn on corresponding switches (any character within
the control field will set a switch so as to create the desired report).
Each report could require some of the same data;
therefore, each master
file record must pass through the entire report selection logic (para-
graph named 102-MAIN-LOGIC) before it can be discarded.
This could re-
sult in the creation of up to 10 extract records for each master file
record.
2.2.2
Data Selection
Each of the data selection modules are closed subroutine (secondary
logic paths that are only executed from the main path).
Data is
either stored in work areas or written directly to the extract file
depending on the report requirements.
e.g.
The source registration report lists all sources;
therefore no data need be saved.
The future schedule summary
only reports actions to be performed in the future.
This
requires saving data until an action record is read.
Th:i,s is
then checked to verify if it is a future action, if not it is
bypassed.
Before any record can be written to the extract file, a 46-character
continuous sort key must be added.
This sort-key will be used to
arrange records in a chronological order within individual reports
(Records are created in random order, not in repor~ order).
The
sort keys for each report are (left to right in descending value):
152
-------
(0)
Action Cards
Agency, Staff Number
(1)
Source Registration
Agency, County, Source, Emission Point
(2)
Action Summary
Agency, County, Source, Action Number
(3)
Source Action Summary
Agency, County, Source, Emission Point
(4)
Overdue Action Report
Agency, County, Staff Number
(5)
Geographic Locator by grid coordinates
Agency, X-Grid Coc~dinate
(5)
Geographic Locator by city, street
Agency, City, Street Name, Street Number
(6)
Future Action Summary by section
Agency, Section, Date Schedule, Source, Action
Number
(6)
Future Action Summary by individual
Agency, Staff Number, Date Schedule, Source Number,
Action Number
(9)
Letter, Permits, etc.
Agency, Letter Type Code, Source Number, Emission
Point
153
-------
2.3
Program 3 - Print Run
The third and final COBOL program of the Enforcement Management
System is the print program.
Its main functions are to punch new action
cards and to produce the desired reports from the sorted extract tape.
The necessary logic is fairly simple.
Each input record (which is
part of an individual report) is tested to find the type of record it is
(first character of
sort key)
and "control" is passed to the appropriate
routine to print each report.
Data fields are saved internally (in WORK-ROLD-
AREAS) until there is a logic break (new source, new action,etc.), and then
a section of the desired report is printed.
There are three common subroutines performed by most report modules.
All dates on the file are in year, month, and day format (flopped in update
program).
Before they can be printed on individual reports they must be
reversed to month, day, year format and slashes (/) inserted between
subHelds
(paragraph named 8l5-DATE-FLOP).
For example:
On Master File:
711201 ;
On reports:
01/12/71
All report headings and subheadings are written from one closed subroutine
(paragraph name~ B10-READ-ROUTINE).
Parameters
(name of report, section
name, etc.) are setup before control is passed.
This en~bles the correct
headings to appear at the top of each page.
The last common subroutine con-
verts the fixed length street name and/or city, state, zip into a left-justified
variable length field (paragraph named 800-SQUEEZE-ADDRESS) by suppressing all
redundant spaces.
For example:
On file:
HARTFORD
CT06l02;
On report:
HARTFORD CT 06102.
154
-------
The production of "canned" letters requires that one complete letter be
saved until there is a need for another one.
This enables one letter to
be sent to more than one source without entering duplicate letter cards.
If there is no match between the print tape and the letter deck, an error
message is written on the printer and the next letter request (next record
on print tape) will be fulfilled.
This logic requires that the letter deck
must be in ascending sequence by agency and letter code.
Letters are se-
parated by line number 999 (see letter deck description under section 8.0
of this appendix) which signals the end of a letter and also provides the
name of the person who will sign it (name is left justified).
2.4
Description of Sort 1 and 2.
The first sort arranges all input transactions in the same sequence as
the master file.
The sort key consists of the first 19 characters of the
transaction card.
Assigning a work file is relatively simple, although
the size of the file will vary.
Each run usually will not contain more
than 1000 input records unless the system is being used by three or four
large agencies.
Therefore, one thousand 80-column records would require
less than 40 tracks or four cylinders.
The second sort arranges the extract output into a logical print
tape.
It uses a 49-character sort key (46-character key, record type, and
cumment line number).
Assigning a work file becomes much more difficult
because one master file (which is continuing growing in size) record
could create up to 10 extract records.
To avoid overflow problems always
155
-------
-
, --
assign a very large area.
One disk pack could be allocated to the En-
forcement Management System.
All three programs could be catalogued to
it and the remainder of the disk pack used as a sort
work file.
This
would take care of most requirements.
156
-------
3.0
STARTUP PROCEDURES
The Enforcement Management System is a collection of computer
programs which are to be used by state and local agencies to enforce
air pollution controls.
The system is written in COBOL to keep program
maintenance to a minimum.
In order to make the system completely flexible
to the changing demands of its users, a series of internal tables are
utilized.
They contain basic local information required by the computer
programs.
Since each agency using this system will make different entries
for each table, an explanation of table setups follows.
The tables are
arranged in ascending collating sequence for ease of expansion.
3.1
Initializing COBOL Tables
The system is divided into three programs.
Each program requires that
certain local data be entered before the system can be implemented.
3.1.1
Initial Entries in Update Program
Personnel Table
See Table 3.1.
The update program reads in personnel cards
(see section 8 for layout) and creates a table of all staff
members.
From this table staff members
are
assigned to
various sources and actions.
As supplied, the table has room
for 200 entries.
If additional entries are required the "OCCURS"
statement must be changed to reflect the increase in staff.
If
the table is expanded to more than 999 staff members,
TOTAL-PERSONNEL-CARDS (under Working-Storage) must also be en-
larged.
This field acts as a counter and terminates the table
search during the assigning segment of the program.
157
-------
O?01()() 01
07011n
0781::>0
C201".n
O?C140
n7\!lC;~
O?C)16~
.'
.. - - .__n .-.-- - ._-- -....' . ...- .~~ --
-.. ...0- . ..
PFRSO"INEL-TABLE.
03 FILLER OCCURS 2~O TIME~.
C? AGENCY-EMPLOYEE.
07 TB-AGENCY
07 TB-EMPLOYEE
f)'; TR-STAFF-NAME
0'; TR-TITL.E
'---_U.-...' ... .
. ._- -, ... - ..~ -- --~ - ~ - .n- -- .
PICTURE
PICTURE
PICTURE
PICTURE
9 (3).
X ( 3 ) .
X ( 15) .
X(15).
TRC428e
TRC428E
TRC42881
TRC428f'
TRC428E
TRC428o-
TRC42881
Table
3.1. Personnel Table.
158
-------
Agency Table
Table 3.2
contains the names of all agencies using the
system and their assigned number code.
The agency number
is compared with the stored agency number;
if they are equal,
the agency name is used in printing the standard heading
for the printed reports.
The first entry (AG-NUM) is the
agency number', in three digits:
001 to 998.
The second
entry is the agency's name (AGENCY-HEAD) which is centered
within 29 characters.
If the agency's name is too large, it
can either be abbreviated or the receiving field can be en-
larged.
,
The last agency number within the table must be 999;
this is used to stop the
search.
Action Table
See Table 3.3.
This table is used to validate actions and
supply English-language descriptions for various action codes.
The action code (TB-ACTION-CODE) is in two digits, 01 to 98,
in ascending order.
This is followed by the action name
(TB-ACTION), which is left-justified within 15 characters.
If
it should become necessary to increase the length of the action
field, all three programs must be changed.
An "acti'Jn 99"
must be the last
entry within the table;
this terminates the
search.
Possible COBOL Statements to be Changed
within Update
If "Reschedule Action" is no longer coded as 02 throughout the
system, statement l23-CHANGE-7 must be replaced with the correct
numeric value for the "Rl:.:schedule Action" option.
159
-------
01.'7.161 01
C??170
0??1~0
O?21QI')
O?2200
0?~01r
02~02~
o;no~o
02304('
0210';0
021C6n
023071')
0210~f)
C210C;O
0?~l:!n
C?'HIO
O?31?'")
:-231~'"
C73140
::'1? ~ 151')
o-u ".'" .... .._-.." .
- . - -- . R~ ..
.. -- ." -
VALUE IS 001.
PICTURE X(29) VALUE IS
, AIR POLLUTION CONTROL
PICTURE 9(3) VALUE IS 002.
PICTURE X(29) VALUE IS
.. ... CLEAN_AI ~- PROTECT ION
PICTURE'9(3) VALUE IS 004.
PICTURE X(29) VALUE IS
ANTI-POLLUTION AGENCY
PICTURE 9(3) VALUE IS 010.
PICTURE X(29) VALUE IS
ENVIRONMENT PROTECTION
01 FILLER ~'ICtURE 9i3) VALU~ IS 999.. . .
03 FILLER PICTURE X(29) VALUE IS SPACES.
02 i~f-T/\BLE REDEFINES AC,ENCY-TABLE.
03 FILLER OCCURS 05 TIMES.
05 AG-NUM PICTURE 9(3).
05 AGENCY-HEAD PICTURE X(29).
TRC42881
TRC42881
TRC42881
TRC42881
AGENCy'. TRC2881
TRC42881
TRC42881
I. TRC42881
TRC42881
TRC42881
'. TRC42881
TRC428B1
TRC42881
'. TRC42881
TRC42881
TRC42881
TRC42881
TRC42881
TRC42881
TRC42881
FILLER.
02 AGENCY-TABLE.
03 FILLER PICTuRE 9(3)
03 FILLER
en FILLER
~n FILLER
r)1 FILLER
;')3 FILLER
03 FILLER
03 FILLER
Table. 3.2.
Agency Table.
160
-------
0?316:1 01
.J? ~ 1 7 ,)
02'31RO
C?'HQ()
0231.:')'1
CJ24010
O?40?0
()?4a~O
D <' i. C' L. :1
C24C~0
I) 1. (. C 6 n
'-:11.4\:;7('
~, ;1 l. J q'l
:)?,40Qr'!
:'?4I00
S?411~
:",1.41.?('.
.") ? 4 1 ~ ('.
:"):"+1~4
C?41':3~
o 2 <. : i. '1
02415('.
~241~'"'
')?4170
\1?:.1Q~
27':'190
FILLER.
02 ACTION-TARLE.
1)4 FILLER PICTURE 99 VALUE 01.
1)4 FILLER PICTURE X(15) VALUE 'INSPECTION'.
)4 FILLER PICTURE 99 VALUE 02.
04 FILLER PICTURE XCI5) VALUE 'REGISH~ATIO,\j'.
04 FILLER PICTURE 99 VALUE 03.
~4 FILLER PICTURE XI1S) VALUE 'PLAN SUB"'1ISSIO,\j'.
04 FILLER PICTURE 99 VALUE 04.
~4 FIL.L[~ 0ICTURE XIIS) VALUE 'REVIEW W/SOURCE'.
04 FILLfR PICTURE 99 VALUE 05.
;. 4 F ILL F. R .) I C T U R f X ( I 5) V A L U E ' REG 1ST. REV I E W ' .
04 FILLE~ PICTURE 99 VALUE 06. .
"~4 FILLER PICTURE XIIS) VALUE 'PLAN REvIEw'.
04 FILLER PICTURE 99 VALUE J7.
04 FILLEq PICTURE X(15) VALUE 'SOURCE TESTING'.
04 FILLER PICTURE 99 VALUE 08.
14 FILL~R fJICTURE XIIS) VALUE 'A.Q. SURVEY'.
04 FILLER PICTURE 99 VALUE 09.
~4 FILLER PICTURE XI1S) VALUE 'COMPLAINT RECD'.
0.. FILLER PI~TUqE 99 VALUE 99.
r:: L. F! L. L E R PIC T U R f X I 1 5) V A L U E ' 0 Hi E R ' .
12 RE-ACT!C~-TABLE REDEFI~ES ACTION-TABLE.
84 FILLE~ OCCURS 09 TIMES.
06 T~-ACT!ON-CODE °ICTURE 99.
06 TB-ACTION PICTURE XI1S).
Table
3.3.
Action 'lclb1e.
161
TRC42881
TRC42881
T~C42881
TRC42881
TRC4288I
TRC42881
TRC42881
TRC42881
TRC42881
TRC42881
TRC428d1
TRC428S1
TRCt.2881
TRC42881
TRC42881
TRC42881
TRC42881
TRC42881
TRC42881
TRC42881
TRC42881
TRC42881
THC42881
TRC42881
TRC42881
TRC42881
-------
1-
3.1. 2
3.1. 3
Initial Entries Within Extract Program
There are no tables requiring initialization, but there is
one possible COBOL statement to be changed, located. in para-
graph named 118-REC-37-2.
If a complaint is no longer action
code 9, its correct numeric value must be substituted for the 9.
Initial Entries Within Extract Program
Section Table
See Table 3.4.
This table contains the names of all sections
using the system.
The entries are arranged in a hexadecimal
collating sequence (alphabetics followed by numerics).
The
first character of the staff member's number is checked against
the first entry within the table (SEC-TABLE).
When an equal
condition is encountered, the second entry (TITLE-TABLE) is
used
as the section name.
The last entry within the table
must be a 9 (high value);
for example, staff member E21 is
a member of the engineering section.
Results Table
See Table 3.5.
This table is used to translate the action
result code into its descriptive equivalent.
The table is broken
into two levels:
the Resul ts Code (TB-REST-CODE), w:,ich is 01 to
99;
and its accompanying description (TB-RESULTS) field
(maximum 15 characters left-justified).
The final entry
should be "Results Code 99."
This will end the search routine.
Agency Table
See Table 3.6.
This table is similar to the agency table ap-
pearing within the update program.
The agency's name field is
162
-------
534() 01
5350
53~n
537n
c;3Q~
'33QI')
540'"
5410
54.?n
. 5430
5441')
545('\
C:;4~('\
5470
'i4~f)
549(')
FILLFR.
03 S~CTION-TABLE.
05 FILLER PICTURE X VALUE 'E'.
0, FILLER PICTU~E X(23) VALUE 'ENGINEERING
05 FILLFR PICTuRE X VALuE 'I'.
n5 FILLER PICT~RE X(23) VALUE 'INSPECTION
~5 FILLER PICTU~E X VALUE I~'.
05 FILLER PICTURE X(23) VALUE I~JRTH ~EG:ON~L
05 FILLER ~ICTU~E X VALUE'S'.
05 FILLER PICTURE X(23) VALUE 'SOUTHERN DISTRICT
05 FILLER ~ICTURE X VALU~ '9'.
05 FILLER PICTURE X(23) VAL~E SPACES.
~~ ~E-SECTIO~-T~ALE ~EDEFINES SECTION-TABLE.
05 FILLER OCCURS 5 TI~FS.
07 SEC-TA9LE PICTURE X.
07 TITLE-TABLE PICTURE X(23).
Table 3.4.
Section Table.
163
TRC42683
TRC428S3
TRC42883
'.TRC428d3
TRC42883
'.TRC42883
TRC42883
E~CINEER'.TRC428d3
TRC42883
!t~5P.'. TRU..2883
T i< C 4 2 a E 3
TRC42a83
TRC42833
TRC42883
H
-------
')500 01
55 H)
5,,>?n
c;')~"
554n
555n
55~()
557C"
55A0
559n
5000
C;~ln
5f.?(')
5A~()
564()
565n
5F,F,O
5f-"7(')
FILLEq. TRC42883
n1 ~ESULTS-TA9L[. . TRC42883
05 FILLFR . PICTURE XX VALUE '00'. TRC42883
05 FILLER PICTURE X(15) VALUE SPACES. TRC42883
05 FILLER PICTURE XX VALUE '01'. TRC42883
05 FILLE~ PICTURE XIIS) VALUE 'NO FURT. ACTION'.TRC42883
05 FILLER PICTUi~E XX VALUE '02'. TRC42Sb3
05 FILLER PICTURE X(15) VALUE 'FOLLOW NXT STEP'.TRC42883
05 FILLER PICTURE XX VALUE '03'. TRC42883
05 FILLER PICTURE X(15) VALUE 'RESCHED. ACTION'.TRC42883
05 FILLER PICTURE XX VALuE '04'. TRC42383
05 FILLER PICTURE X115; VALuE 'DATA NOT RECD '.TRC42883
05 FILLFR PICTURE xx VALUE '99'. TRC42983
05 FILLER P[CTURE X(15) VALUE 'CT~ER '. TRC42883
03 RE-RFSULTS-TABLE REDEFINES RESULTS-TABLC. TRC42883
05 FILLER OCCURS 6 TIMES. TRC42883
07 TB-REST-CODE PICTURE xx. TRC42883
07 TA-RESULTS PICTURE XI151. TRC428S3
Table 3.5.
Results Table.
164
-------
i -
',;:>nr. :11
6?lf)
();'? t'\
r) ."' -; f)
~ ,'" 4 r:
.;;;.,n
" ) f, (',
6;'""':;
(, ? Q n
~70n
c,V'~
1.,~11
e, '3 :> ~i
<. ~ -:t,..
\'.' .
"1':'~
63';(;
S3'::i
f..:P~
f"Af)
n3Q')
f,4(')"'1
641 n
~.:.:>'"
~41r
~44('
(,45C1
f.4 t. r.
~J4 7("
!,I.. ~ '"
640'")
FIlLFR.
,j? AGFI\JCV-T/l9Lf..
~3 ~ILLFR PICTURE 9(3)
:)1 F;LLE~
VALUE IS 001.
PICTURE X(29) VALUE IS
I AIR POLLUTIO~ CONTROL
PICTURE X(29) VALUE IS
'A!R PCLLUTIO~ CONTROL
;)!CTUf~E 9(3) V/\LUE IS C;J2.
PICTURE X(29) VALUE IS
CL~AN AIR PROTECTION
PICTURE X(29) VALUE IS
'CLeAN AIR ?ROTECTION
PICTUR~ 9(3) VALUE IS 004.
PICTURE X(29) VALUE
ANTI-POLLUTION
PICTURE X(29) VALUE
'ANTI-i=10LLUTION
PICTU~E 9(3) VALUE IS 010.
PICTURE X(29) VALUt IS
. ENVIRONMENT PROTECTION
PIC7URE X(29) VALUE IS
'ENVIRONMENT PROTECTION
~1 FILLEQ PICTUR~ 9(3) VALUE IS 999.
C3 F!LLF~ ~ICTURE X(29) vALUE IS SPACES.
13 FILLER PICTU~E X(29) VALUE IS SPACES.
07 R~-T~RLE QEDFFINES ASENCV-TAALE.
03 FILLER OCCuRS 05 TI~ES..
05 M;-'..W." PICTURE
G5 AGENCY-HEAr, PICTURE
05 lETTER-AG-HfAD PICTURF.
TRC..2883
TRC42883
TRC42883
TRC42883
AGE~CY'. TRC4~883
TRC428!:J3
AGEiKV'. TRC428H3
TRC428B3
TRC42883
'. TRC42883
TRC429R3
'. TRC428H3
TRC42883
TRC4~~83
'. TRC428R3
TRC42883
'. TRC42883
TRC42883
TRC42883
'. TRC42883
TRC42883
'. TRC42883
TRC428R3
TRC42883
TRC42883
TRC42883
TRC42883
TRC42883 .
TRC42883
TRC42883
::1 FILLER
':;'3 FILLER
~; FILLEq
", FILLFD
".~ ;:-: L L E '(
T~ ;=rLLF.r.:
('3 FILLF.R
~3 FILLEq
03 FIL~F.R
:'3 FILLFR
IS
AGEI\;CV
IS
AGENCV
9 (3) .
X(29).
X(29).
Table 3.6. Agency TabJe.
165
-------
used to print both the standard heading which appears at the top
of each ~eport a~d the agency's name which appears on all letters.
To simplify this procedure the table is increased to three levels:
the agency number (AG-NUM), 001 to 998;
the agency's name
(AGENCY-HEAD) centered within 29 characters;
,
and the agency's
name (LETTER-AG-HEAD), left-justified within 29 characters.
Action Table
See Table 3.1.
This table is an exact duplicate of the Action
Table appearing within the update program.
It is used to trans-
late both the action code and the next action code to their ap-
propriate descriptions.
Letter Table
See Table 3.7.
This table is used to translate the letter code
(from the action card) into a subject heading describing the
contents of the letter.
There is room for 99 different letter
titles, arranged in ascending order by letter code.
The first
entry (TB-LETTER) is the stored letter code, 01 to 99, followed
by the subject description (TB-SUBJECT), 17 characters ~eft-justi-
fied.
The last entry within the Table must be 99 to terminate the
search.
Possible COBOL Statements to be Changed within Print Program
Under paragraph 127-REC-36-4, the contents of the results
field is tested for either a 3 or a 4, "Reschedule Action" or
"Data not Received", respectively.
Two stat~ments must be
altered if the above relat;onship has been changed and the
correct numeric value substituted.
166
-------
'iq",~ \11
5970
'i9Rn
'i90')
t,l')nn
Mlll')
AO?,.,
f,o,n
nOM)
60c;n
~Cf1n
f,('\7n
f,:iRn
nOq()
61(')(')
611n
6171"1
6130
Al'-()
~l~n
AlAn
6170
61RO
Alon
~ILLER.
03 LF.TTER-TABLE.
ns FILLER PICTURE XX VALUE '01'.
05 FILLF~ PICTURE x(17) VALU~ 'REOUEST REGISTR. '.
OC; FILLER PICTuRE XX VALUF '02'.
05 FILLE~ PICTURE X(I7) VALUF- 'REOUEST PLAN
05 FILLE~ PICTURE xx VALUE '03'.
05 F ILL E R PIC T U REX ( 1 7) V A L U E 'P E r~ ~I, I TAP P LIe AT. '.
05 FILL~R PICTURE XX VALUE '04'.
05 FrLLE~ PICTURE X(17) vALUE 'ISSUE PER~IT
05 FILLER PICTURE xx VALUE '85'.
05 FILLER PICTURE X(17) VALUE '155. CON~. PEQMIT'.
O'i FILL=R PICTURE xx VALUE '06'.
05 FILL::R PICTURE X(17) VALU::: 'APPEAf~ AT AGENCY'.
05 FILLER PICTURE XX VALUE 'C?'.
05 FILLER PICTUR~ X(17) VALUF 'PLA~NED VISIT
05 FILLER PICTURE XX. VALUE 'OE'.
05 FILLE~ PICTURE XII7) VALUE 'REGIS. APPROVAL '.
DC; FILLER PICTURE XX VALUE '99'.
05 FILLE~ .PICTUR~ X(17) VALUE IS SPACES.
01 RF-LETTER-TABLE RECEFINES LETTE~-T~BLE.
05 FILLER OCCURS 9 TI~ES.
07 TA-LETTER PICTURE xx.
07 TH-SUAJECT PICTURE X(17).
, .
, .
, .
Table
3.7.
Letter Table.
167
TRC42883
TRC4288~3
TRC42883
TRC428d3
TRC42883
TRC42883
TRC42883
TRC42383
TRC'-2883
TRC42883
T.~C428E3
TRC42333
TRC42883
H\C':'2883
TRCt.28b3
TRC4~t53
Ti~C42ei-l3
iRC42S83
TRC42883
H~C42883
Tr~C4~e>33
TRC428~3
TRC42883
TRC42383
-------
3.2
Building the Initial Master File
The update program of the Enforcement Management System requires as
input a transaction file, a personnel file and a previously created master
file.
Since the first running of the system does not have a previously created
master file, an initial file must be produced before the system can be imple-
mented.
The initial file contains only two records:
a control record (which is
the same as the control card (see 7.0 within this section) and a dummy last
record.
The last record format is all nines (9's) in positions 1 through
18.
This record ensures that the old master file will always contain an
agency, county, and source number greater than any incoming transaction.
The file is created through a standard card to tape utility.
The output is
l80-character records, with a blocking factor of 10 (same as master file).
The JCL (Job Control Language) for IBM 360 DOS is shown in Figure 3.1.
For IBM 360 08 the COpy or IEBGENER utility would be used to create an
initial file.
168
-------
1/ J"":R CA~I)TP
II A~~~~ SVS004.X'OOC' INPUT CARD READER
II AS;~~ SVS005.x'180' OUTPUT - TAPE DRIVE
II J~SI ~n101000 NO T~ BEFORE DATA. NO LABELS. TM AT END
II fX~C CDTP EXEC STA~DARC CARD TO TAPE UTILITY
!I UCT TQ~.~F.A=(qO.~a).~=(lAC.1BCO).Il.OR.Rl BLOCK WI. 160 CHARACTERS
1/ F.(; 1."r;.1
/.' f \; i"",
ZZXXXXXXXX 111:7106C171111C71ENFORCE~E~T ~ANAGEMENT FILE INPUT SEHIAL 000000
~9~~~~u9G99~~~~99 DU~~Y RECOPD - LAST RECORD ON MASTER FIL~
1*
Figure 3.1. Control car~s to
Maste...: File.
create IpitiaJ.
H19
-------
4.0
EDIT DESCRIPTIONS
The following errors are detected in the edit and error program and are
printed on the report.
All transaction cards accepted into the ,system are
also listed, for auditing purposes.
Note the use of the N, C, or D codes on the transaction cards.
These
codes, which stand for NEW, CHANGE, or DELETE, are used in the editing pro-
cess to help avoid various types of coding errors.
New records are defined as any transaction record that does not
have a like record on the master file.
Therefore if a source has only the
source name on the master file and the address and emission point (001)
information are to be added, the emission point data will come as new
(N) and the address data will be entered as a change (C), since there is
already a source record on the file.
Change records
can
be defined as any transaction record that has
a like record on the master file.
Only the fields that are to be changed
should be keypunched;
others can be left blank.
These blank fields will
not be put out to the master file.
To eliminate or blank out a field on
the master file, an asterisk (*) should be keypunched anywhere within the
field to be eliminated.
A delete card (D) can be used to delete an entire source (and all
emissions and actions pertaining to that source), one emission point record
(and all action records pertaining to that emission),
or one action--but
not the emission record for one emission point.
(Section 2.1 of this ap-
pendix discusses record deletions in more details.)
170
-------
NOTE
2.
A change may not correct a new record just entered.
1.
A new or changed record may not be deleted by a subsequent record.
The following are errors the system will detect:
Error
Card out of sequence
Key data not numeric
Record type not valid--
Code 1-8
Neither new, change or
delete record
Action and/or emission
record(s) without source
(which could have been re-
ject because of an error)
Month not 1-12
Day not 1-31
Year less than 60
No master file record for
change/delete transaction
No match on control fields
indicating either wrong
master file, no control
card, not current master
file
New record is equal to
existing record on
master file
171
Actual Message
Out of Seq
Not num field
Bad rec code
Bad rec code
No source info
Bad date
Not on file
No control card
Code incorrect
System Action
Stop run--abort
Reject record,
continue run
Reject record,
continue run
Reject record,
continue run
Reject record(s),
continue run
Reject date, make
date 00/00/00 and
continue with tran-
saction
Reject transaction,
continue run
Stop run--abort--re-
summit
Reject record,
continue run
-------
5.0
OPERATING INSTRUCTIONS
5.1
Request for Computer Pro~essing
Requests for computer time and services forms are normally available
from the user's computer installation.
But because of the possibility of
multiple users of the Enforcement Management System, it might become de-
sirable to design a special form.
The form should include:
All supplies necessary to run system.
This will enable operation personnel
to assemble special forms, cards, etc.
(e.g. action cards, preprinted
letterheads, personnel cards, letter cards, etc.).
Special number of input master file and retention factor.
Description of control card information.
Computer operations personnel
(tape librarian, lead operator, etc.) may keypunch this card instead
of the keypunch section.
This could be desirable if transactions are
on magnetic tape and there is the possibility of one card becoming
misplaced.
Number of report copies.
Print on 2-, 3-, or 4-ply paper.
Request for
bursting of report and interpret~ng of outputed action cards.
Location of transaction cards (or tape).
Any instructions for operation's personnel.
Figure 5.1 shows one example of a "run control" form.
Figure 5.2 depicts
the form completed to reflect scheduling of one cycle of the Enforcement
Management System.
172
-------
Date
~IRJrr[T'EIT r1';:t~r,pBIT crt~ fTER SOlmlll£
Computer/Hodel
Use:
Object Decks
E.M. S.
Level II t:J
Level III t:J
Disk Number
Estimate Running Time
JCL Deck Number
Charge Code
Services: 2 ply t::J
3 ply c::J
4 ply c::J
Bursting c::J
Interpreting t:J
Return to
Area/Section
Special Forms:
Action Cards Number
Letter Stock
Other Cards
Other Stock
Personnel Deck
Letter Deck
Other
Control Card:
ZZ~ t L ~ ~ "'FORCF'.!E'jT '.!:'~T~r:~fr."T "'-LF I':ur'" S.;:-t'T'L : L
--I reporr-r-I d~t~-I f~~~ I--t;-l~~~-~-~~~-~-~~u_-~-~--~l w- ~--~- -~~ -i~~~:-I --
Transaction File:
Card Deck
Tape Number
Retention in Days
Old 1-!ast.er File:
Seri.al Number (Internal)
Serial ~L::!'.ber
Updated Master File:
Serial ::u.~:ber
(:Lnr.en~al)..._.__._- Serial Nuu1:>cr
Retention in D2?s_-
.\,Jd i ti o:"!c' 1 (:;);::::'(;[1 rs :
.. ""___n._.__.--.. -_. .~_._.. -."-
-'--, . .....-----..,----.----.--......--.--..--.--.--..--..-.-.17..1.-.-. .-.-
.. "-'~.'----- .---.-.--.." ----..
,: .fC>T
L :::.~.c. c iITJ2
s,::'r-!,))-e:;~;-3 G
-------
Da te/:2. / f /7 /
. '
ENffiOC81] IT r'~ !~GE!E IT crtPHrER sri/EnillE
Computer/Model 3Ui - "7 () /) [' ~
E.M.S. Level II ~ Level III ~
Use:
Object Decks
Disk Number
/ d. 3'; s'- 6
Estimate Running Time
C. 7' ,')-
JCL Deck Number
(,. ;Z 7
Charge Code ---t1 '-I;l.. 7
Services:
2 ply
3 ply
c
~
Special Forms:
Action Cards Number
:l7&
Letter Stock
~-'ii:-7
4 ply
Interpreting
I::J
~
[:;3------
Other Cards
Bursting
Other Stock
Personnel Deck
;). '-j 1(, ;;2. <5- - 0
J
Return to
E
('2->'1, e v)
Letter Deck L.:2. '-l 'iJ .L'2 ':) 0
v
Area/Section G'JS/fJ' E ~ y
Other
Control Card:
( ~~~(.--- i-~- ~~'L1Lf£.3":'1~LL3£:i~~~QE(;;EUEtlI_M.~\l~GEMENI_ELLE~IKEUI_~ERIAL_~L...u.t.t..-- ---
I I report I I date I from I to \ I '1um. I
Transaction File:
Card Deck .¥'
Tape Number
Retention in Days
30
Old Master File:
Serial Number (Internal) (JOt. J. /0 Serial Number
<)'13;),0
Updated Master File:
Serial Number (Internal) eCI (; J..-LL Serial Number -'- Retention in Days
3c
Additional Com:nents: -:t; 1'17 y.
c
cJ i) & /" t. c
:<./ / / / Ii aJk{
Ae!Gu.z.v
/ 'J. ,.;;L - "/ / - ,If fY}.
HI C-
E.7"
':-""
,:2. /1" x'
.-:.. 7 ::.
Figure 5.2. Completed computer time request sheet.------
-------
Card to
Tape
!
!
I
----.----.-I
M/F
New
M/F
~J
Update
'-
I ~tract--l
Sort
2
.....-----
I pr:~ _J
Figure 5.3.
Enforcement Management System
using four devices.
175
-------
Card to
'_,e
Sort
1
_._-..._-~,_._--
f'ismount
use
new
tape
r--
Sort 2
Figure 5.4.
Use
same
tape
utilized
in card
to tape
Update
I
----
---------.
l1/F
Enforcement Management System using three devices.
176
Extract
r
Print
Run
'_____'n____n.____~_. .
-------
5.2
JCL for DOS and OS
The Enforcement Manageme~t System was written for a data processing
system with a minimum configuration of 40K byte CPU;
Card Reader/Punch,
Line Printer,
and three magnetic tape drives.
Optional hardware could in-
clude one disk pack for cataloging,
one additional tape drive to eliminate
mounting and dismounting of tapes during execution of the system.
If four
tape drives are not available, any combination of discs and tapes could be
used.
Figure 5.3 graphically explains how four devices can be used.
Figure 5.4 depicts the standard three-tape system.
5.2.1
Cataloging
The most effective method of utilizing the Enforcement Management
System is to first catalogue (place the programs in "executable"
form on a disk pack) all three programs and then execute the system
from a job stream.
If this is undesirable or not possible, section
5.2.3 of this appendix explains the procedures n~cessary to compile and
execute from an object deck.
The main advantages of executing from a
job stream are:
a.
Fewer cards to be handled (reducing chances of losing a
card)
b.
Less computer time required because the same operations
need not be done each cycle.
Figure 5.5 describes the JCL cards required to catalogue programs
for both IBM 360 DOS and IBM 360 OS.
The PHASE card (360 DOS) con-
tains the name of the program as it will later be referred to.
The
177
-------
, JOB
1*
SOURCE
DECK
COB. SYSIN
,'EXEC
360 OS '
Figure 5.5.
1*
I I EXEC LNKFDT
1*
SOln?CE
DECK
I I EXEC COBOL
PHASE Program Name
II OPTION CATAL
II JOB
360 DOS,
Cataloging. Linked Programs.
178
-------
EXEC card in the OS version contains the program name.
In
both computer environments this procedure will be initially
repeated three times (once for each COBOL program), changing
only the program name and source deck (original COBOL program
card deck).
5.2.2
Executing from a Job Stream
Figures 5.6 and 5.7 show the necessary JCL for executing the
Enforcement Management System from catalogued programs.
Both
exhibits utilize the four-device concept.
5.2.3
Operating System from Object Deck
The "compile, object deck and execute" method may be used on'IBM
360 DOS/TOS or with other computer systems.
For this reason the
description following will be general and will require some modifica-
tion on-site.
Figure 5.8 depicts the JCL needed for the following
operations:
compile, get an object deck (machine instructions with
unresolved addresses), link edit (resolve the unresolved addresses),
and execute one COBOL program.
This process would be repeated for
each of the three programs.
The sort parameters ,and the p'ersonne1
and letter decks would be integrated with the object decks and the
entire system executed (Figure 5.9).
179
-------
- - - - . -
-.. - - . .
. . - . - .-. ~- _. .. .-. .
. .. .- - ... -_.__._.~._._--._.
-.--- ..-... ..
---------------------------------------------
II J8q X~02~O DITTO PUT TRA~SACTIO~S CARDS O~ TAPE
--/7uo~1------------------~U8ELJvjPUT~LE----------
II ~X~C nITTO DITTO IS r~M UT1LITY
~5~ITT0 CT ~UTPuT=SYSJ1C CA~~ TC T~~~ ~AR~.
3~~ITT~ ~Tv Ou7;uT=SYSC1C wRITE TA~E ~A~< AT E~D OF FILE
--s-s-o!rn"-R~'iJ -oU'1?UT=SYS0T() - -----~~~!) CJT~uT"lAPT-----------
~SDITTn TO I~DUT=SYSQ10 PRINT OUTPUT TAPE
- - -~5Di t-t(" -c:cj--- - ------'---- ---- - - - - - -- ------- -- ---
II JC~ sn~TI~p SORT I~PUT ~ISC CARDS . .
II A5S~~ SYSOC2,X'193' I~?UT SC~T - OUTPUT FR0~ CAqu-TAu~
II ASS~N SYS001,X'lq:' CUT PUT SORTED T~A~SACTICNS .
--/7TxcC~SJ~T---------------ST~~A~Di~-~RT------------
SOQT FlcLDS=(l,lq,A) ,FCRVAT=8I,FILES=1,SIZE=500
---'r~J?l)iYDt=F91r~"G~ = rB: "ifCT- - ---- -- - -- - -- - ---- -----
I~DFIL VOLuYE=1,~L~SIZE=(S~,X),9YPASS,I\PUT=T
QUI"I~ "L,(~ILt=~:,)':';UI,-JUT=1
cprI'~\' LAQCL=:(U,U)
---T~----------------------------------------
I I JCQ EVSl FPST ;)ROGKl\.V, !F'J E:'JFC~CE'/::"T SYSTEY UPDATE PROG~A,\1
- - -/7 71 ~c:,-~'!~Y~C~r.x '1 ~T - - - r\ PuT "I ~-A ,\; Sl:;CiT(~'i-rrC;:: ~ 00;:;0 T r \~ ov -F1-;-~"5i SO£:~ T-
II AS5:,,\ SYS:-<~:J,X'lq:' r\~PU~ OLD \':,STER FILE'
I / A '" : , X I 1 :< 2 ' r: . P U T - " '- . ,.: A ~ T ::: ~ F rL.::. ;- ;:,-~.; ~ p ;.) .:, T :::
II t.SSr:,~IC;YS01':J.X'lR3' CUTo~T
-- -. --/7 ""[xc-CC:'VS 2' .-' ,,- -- -_. -------.-- -- ----- - - --- :::X2-(- p::rv:;-~-,;;~;'-F~C'rCC-~:;;~~GE "I.TEF,(~~ y
II J0° S~~T\PE S~CO\D SG~i, SQqr EXT~ACT FILE .
----7T7>. ~c;r,-\;---sy-.s-Cc ItXTr ~T--~lTT~"'OI-~c ~T'~T--rA ~t: - - - ---- ----- - -------
II A~S~~ SYS8J2,X'193' !~puT - CUToUT F~8~ ExTRACT ~J~
II ::YI:"r: ~S~':>T sr,',::DA':1D Ij" SC~T
S8~T FI=L~S=(1.4g,A) ,F:~';AT=3I,FILES=1,SIZE=5~C
-- - ~n:~~~-~ 'Y5E=Ftl::-'~if-C= D~:1,t2(J:JT------- -- - --- - -------- -- ---.
I~Dc:L V0LU~E=1,cL~SIZE=(2CCO,X) ,~YPASS,I\?UT=T
- -- -C:LJT =--TC --c [!(S:-ZE=7C'::J,-00T1Y;Ji=-r- - - - -- -:- --- -- - - -- ---- - - - ---
()DTI'~" !..ho~L=(U,U)
::. :.~ '..)
/ I J 'i q E \' 53 p :~ I 'j T r(:j ,': - r, f.J u T SO R T E ) D t\ T i;
- --. - nA-r:;<:..(". ,,- -SYSOT5.5< rDE' - - - -. -- - - -- - 1JRl.\JTEH- :;- -(;;~J-f.:: --;-J;PT- ---- - - - --
I I ASS {, " S Y SOl 2 . X I :: j ~ ' CAR D P U ..~ C r-+ - 1\ C T I J :\~ C III D 5
- - - n-A-r::;~':r 3YS~~7 9X 'l'::':P---------- --r,'TPur-.;;- JU""-;JUiTT:::r-STIi---- - - --
II AS5G~ SYS01S.X'1?l' c.uTPUT ScP~~ATE L::TTE( FILE
II ASc:,~~ SYSCll,x'C~C' (A~D ~~A~E~ - L~TT~~ JEC~
/I Ex=C C:"S~ ::XEC =:::::'.; C::::;E-r '.'AG:: Li B;~ARY
- -- ----/7 -'-j'")c-CT;:>"S'-- - -- -- -- -- - -- - - -- -- '.\;':("T,-:: -L2 rT=-.~- t-n::-~- f.::;-c~r';T:::.( - - -.-- --
II ASS~~ SYSa04.x'lol' I~puT LETT~~ FILE
-- - -/7 ASS(;\)- Sy socS-, x-'-jeYE'--- -- - - --- ou-fpu'f- -f3n;.-;-E:~-- -------------
II UDSI lr~~CGJ" \8 LA9E~ C~~C~I\G
II ~X~C TO:::;~ 51;',\;';;\.<; T",'"'t:. i0 :)"\.",,:'-<..)1 LoI iY
II UTD TL.FF,A=(133d3j),~=(132)tI~,8C,sc,Dd:n USE I"'3~C),)E:; CJ;';:Rc.LS
0- ---- -II-:=-'";r~-- -- - ---- - - --- -- --~--- _.- - -- - - --. ------ --...-.- -... - -- -- - -------- ---
- -- - - --- - -- -- - --. -.. --- -- - - .- - ....- .. -- .-- .--- ..- -.
.---.- --- --- --- - ------
-- --- -- -.
- - - - .!i~ure - 5.:6. Execute - IBM 360 DOS EMS Yersio_n fr_om_~~t~l_ogu~_~ J)r_~gram~
180
-- _._- -- .n-
.. -.- ---- -.- --
_. -- .- - --- --..
. ~ - - .- _.~ .-
-------
.IITRCEMS JOB (9224250,A,1),lMH.TIME=1.CLASS=A.REGION=lOOK
. II EXeC RINGIN,PARM=006561
IIJOBLIB DD DSN=USER.lINKlIB.DISPaSHR
II EXEC PGM=IEBGENER
IISYSPRINT DD SYSOUTaA
IISYSIN DD DUMMY.
IISYSUT2 DO DSN=TqANS,UNIT=TAPE.LABEL=(.SL..OISP-(,PASSI.
II VOl=SER=006561,DCB=(RECFM=FB,LRECl=80.BlKSIZE=800)
IISYSUTl DD *
TRANSACTION FILE
IISTEP! EXEC SORT
IISORT.SORTIN DD UNIT=TAPE,DSN=TRANS,VOl=SER=006S61,LABEL=(,SL),
II DCB=(RECFM=FB,LRECL=80,BLKSIZE=800),DISP=(OLD.PASS)
IISORT.SORTOUT D~ DSN=TRANIPT,UNIT=Z314,VOL=SER=RTCC02.DCB=(RECFM=FB.
II LQECL=80,BlKSIZE=80),DISP=OLD
IISORT.SORTWKOl DD UNIT=SYSDA,SPACE=(TRK.(lZO)"CONTIG) .
IISORT.SORT\~K02 DD UNIT=SYSDA,SPAC~=(TRK.(120).,CONTIG)
IISORT.SORTWko3 DD UNIT=SYSDA,SPACE=CTQK,(120)..CONTIG)
IISORT.SORT~ODS DD UNIT=SYSDA,SPACE=(TRK.(lO,))
IISORT.SYSIN DD *
SORT FIELDS=(1.19.A).FORMAT=CH
END
1*
IIUPT EXEC PGM=TRCUPT .
IISYS007 DD DSN=TRANIPT,DISP=OLD,UNIT=Z314.VOL=SER=RTCCOZ
IISYS008 DD .DSN=A,VOL=SER=TRC001,LABEL=(2,NL).UNIT=DDTAPE.DISP=OLD
II DCR=(DEN=2,LR~CL=180,BLKSIZE=leOO,RECF~=FB)
IISYS009 DD DSN=SYS009,VOL=SER=006561,LABEl=(1,SL),UNIT=TAPE.
II DISP=(.PASS) .
IISYS015 DD SYSOUT=A
IISYSOIO DD *
PERSONNEL DECK
1*
IIEXT EXEC PGM=TRCEXT
IISYS009 DD DSNAME=SYS009,VOLUME=SER=006561,LABEL=(,SL),
II UNIT=TAPE,DISP=OLD .
IISYSOIO DD DSN=+EXTRCT,
II DlSP=(NEW.PASS).UNIT=SYSDA.SPACE=C200.(500.S»)
1* .
IISORT2 EXEC SORT
IISORT.SORTIN DD DSN=+EXTRCT,UNIT=SYSDA,DCB=(RECFM=FB.LRECL=200,
II BlKSIZE=2000),D15P=(OLD,DELETE)
IISORT.SORTOUT DD DSN=+PRINTP.UNIT=SYSDA,DCB=(RECFM=FB,LRECL=200,
II BLKSIZE=2000),DISP=(NEW.PASS),S?ACE=(ZOOO,(500,5»)
IISORT.SORT~KCl DD UNIT=SYSDA.SPACE=(TRK.(12C)"CONTIG)
IISORT.SORTWK02 DD UNIT=SYSDA.SPACE=(TRK.(120)"CONTIG)
IISORT.SORTWK03 DD UNIT=SYSDA.SPACE=(TRK,(12C)"CONfIG)
IISORT.SORTMODS DD UNIT=SVSDA,SPACEa(TRK,(lO.3)
IISORT.SYSIN DD *
SORT FIELDS=(1.49,A),FORMAT=CH
END
1*
IIPRT EXEC PGM=TRCPTR
IISYS007 DD DSN=+PRINTP.UNIT=SYSDA,DCB=(RECFM=FB.LRECL=200,
II BLKSIZE=2000),DISP=(OLD.DELETE)
IISYS015 DO SYSOUT=A
IISYS012 DO SYSOUT=B
IISYS019 OD DSN=lTRS,UNIT=TAPE.LABEL=(.SL),DISP=(,PASS).
II VOL=SERc005661,DC8=tRECFM=FM.LRECL=133,8LKSIZE=133)
IISYSOll DD *
LETTER DECK IN AGENCY, LETTER TYPE ORDER
1*
II EXEC PGM=IEBPTPCH
IISVSPRI~T DD SYSOUT=A
IISYSUTl DD UNIT=TAPE,LABEl=(,Sl).VOLUME=SERc005661.
II DISP=(OlD,KEEP),DCA=(RECF~=F~,LRECL=133,BLKSIZE=133)
IISYSUT2 DD SVSOUT=A
IISYSI~ DD *
PRINT PREFORM=M
1*
Figure 5.7.. Execute D~ from 360 05 catalogued programs.
101
-------
OBJECT
DECK
SOURCE
DECK
II EXEC COBOL
I I OPTION LINK
II OPTION DECK
ASSIGN
CARDS.
I I JOB E..'{TRACT
II JOB EXTRACT
Compile, Deck
II EXEC
II EXEC LNKEDT
1*
. OBJECT
DECK
Execute from Object Deck
Figure 5.8. Compile, Deck, Link, Exe~ute.
182
-------
II EXEC LNKED
object
deck
INCLUDE
I OPTION LINK
Assign
Cards
II JOB EXTRCT
1*
persannel
deck
II EXEC
LNKED'fJ
I
II
object
deck
INCLUDE
OPTION LIN1--l
I
, .
.Assign
Cards
)/ JOB UPDATEI
Figure 5.9.
1&
letter
deck
II EXEC
/ / EXEC LNKED
1*
object
deck
INCLUDE
( I OPTION LI~ I
Assign
Cards UJ
JOB PRINT ~ I
Execute Enforcement Management System from Object decks.
183
-------
6.0
MASTER FILE RECORD LAYOUTS
The data base is maintained on magnetic tape (master file) and con-
sists of fixed length
blocked (10 to a block) records.
The file segments are as listed below.
They are 180 characters in
length and are in character format for ease in maintenance.
Fields are
neither packed nor in hexadecimal notation.
Record Type 1 (code 20) Source Header Record
Record Type 2 (code 21) Additional Source Data
Record Type 3 (code 34) Emission Point Header
Record Type 4 (code 35) Additional Point Data
Record Type 5 (code 36) Action Header
Record Type 6 (code 37) Additional Action Data
The file is in sequence as shown in the record sequence key diagram,
attached.
The key fields are:
Agency Code
County Code
Source Number
Emission Point
Action Number
Record Type
184
-------
Source Agency County Source Em
and Po
Emission Point Code Code No. (0
Records So
3 4 5
1 3 4 7 8 12 13
-
f-'
CP
VI
Action Agency County Source
Records Code Code Number
3 4 5
1 3 4 7 8 12
ission
int Numbe
OO)for
urce Rcds.
1----
---.
Emission
Point
Number
3
13
---
15
,----
Blank
(zeros)
15
.--L- 2
16 17 18
Re cord
Type
Record
Number Type
2
17 18
._----- --
Figure 6.l.
RECORD SEQUENCE KEY.
Action
2
16
Record Codes
20= Source Header
21= Additional Source Information
34= Emission Point Header
35= Additional Emission Point
19
-- ,----'--'------
fRecord Codes
36= Action Header
37= Additional Action
19
-------
~
...,-
()Q
(:
'1
(1)
:::0
(1)
n
o
'1
p...
r-'
I!J
'<:
o
(:
rt : 4
t-t> '.:)
o ,...
'1
I:7j
~
(J)
~
I!J
(/)
r-t
(1)
'1
t-.j
...,-
......
CP
.
PROPORTIONAL RECORD LAYOUT FORM
Application
Enforcement ManaR':..ment System
Page ~ 01
RECORD NAME AND REMARK'
~.::. '-'~
'::It \,J\J
90 ~"
9', 'Jf~
'00
Source Header
Inforr.lation
'"
(0",'
. ! " " I
I Suurce COllu:Lcnt
I Record
()
lObin.
100
Name
Eml~81on Point
Information
Emission and Action
Corrunent Record
Action Record
100
Hex. CJ tJO
o,.e,D('C
-Two numbering arrangements. each in hekddecimal and decimal notation, ale shown. Select the Jlf'lngcment and notation u~:J by checking In,. ~-,~~roj)ri....tc UI)X lO th~ Ide
t The numbef of torm\ per pad may vary slightlV.
-------
7.0
CONTROL CARD LAYOUT
A control card must be prepared for each run cycle.
The layout is
shown on the attached layout sheet.
The control card is used to:
1.
Enter today's date into the system.
The date is entered in columns
13 through 18 in month - day - year format, such as 10-01771 for Oct. 1st,
1971.
2.
Check that the correct master file is being used as input to the
series.
The old serial number from the last run is punched into columns
72 through 77.
The serial number begins with 000000, and is updated by
one number each cycle.
The current serial number is printed on the edit
and error list.
3.
Determine which reports are to be prepared this cycle.
Any character
in the correct column causes the report to be printed;
a blank omits the
report.
The columns are:
Column 3.
Source Registration Report
4.
Action Summary Report
5.
Source Action Summary
6.
Overdue Action Report
7.
Geographic Locator Report
8.
Future Action Summary
9.
Letters, Permits, etc.
4.
Enter dates for the selection of actions for the action summary
report.
These dates provide starting and ending dates for the period
to be covered in the report.
The start date is punched in columns 19
through 24, and the end date in columns 25 through 30.
187
-------
The phrase "Enforcement Management File Input Serial" is punched in
columns 31 through 71, to serve as run identification.
In the level 3 (advanced) system, the current week number is entered in
columns 11 through 12, to indicate to the scheduling routines
the week being
processed.
This
week number is from 1 to 52, starting with 1 at the beginning
of the year.
188
-------
. .------------.'-
. . -- - ---.~ .~ --.-- .~.- ~..._.--~--...-_.._---_.._..-~~.._--
---.-
DATA
CAfitO
LA YOUT,
CARD FORM NO.
5081
TITLE
Control Card
FILE
IDENT.
PRCX:;RM\ TITLE
Enforcement Management System
COM\~ENTS
C:ol11mn
1
SOllr'rf> Rf>giRtration peport
8.
Future Action SummarY
4.
Action Summarv Report
9.
Letters, permits, etc.
5.
Source Action Summarv Report
6.
Overdue Action Report
7.
Geographic Locator Report
t-' '
00
\0/
/
(
I
I
"
.
.
.
!., ,.
,.
"
,.
10
II
... II
"
M
.. I..
I.
,.
eo
., ..
..
..
I.
.. ..
'8 I.
80
..
..
..
.. ,..
? 7. 7. I.
~
---
><
H
z RUN START END
o
M DATE DATE DATE
. (ACTION (ACTION
:> MO. SUMMARY) SUMMARY
H
'-' DY.
. YR.
0
z
SYSTEM IDENT.
RUN,
SERIAL
NUMBER
_h -.. -- .- -'
. .-" ..---.-.------- '----"--'----,--,------
f tVE Q.ltC. S1jfL~ i JjB,fvJ10_&.l'Lf.ALLEJ L C
- - - ----. - - -
~ ~-_. "
- -"- -'---.;;""------=:- -'
-------
.
,
8.0
PERSONNEL AND LETTER CARD LAYOUT
A letter card deck is required to enter the standarized letters and
permits into the system.
One card in the deck equals one line on the letter.
These letters are maintained manually and must be in sequence.
The
last card of each letter must be numbered 999.
This is the signature, which
will be printed on the letter (left-justified starting in column 17).
For
coding line numbers (columns 8 to 10) on letter cards, it is suggested that
the numbers start at 010, and increment by ten (010):
010, 020, 030, etc.
This will enable additional cards (print lines) to be added in the future
without resequencing cards.
If a blank line(s) is required within the
body of the letter a card(s) must be provided bearing agency, letter type,
and line number (the remainder of the card will be blank).
See Figure 8.1.
Letter headings, including title, source address, permit information,
etc., are automatically printed by the print program.
A personnel card deck is also required for each run.
This deck is
made up of one card for each staff member expected to utilize the system.
It need not be in sequence by agency and employee number.
The first digit
of the employee number represents the section number.
Columns 39 to 66 of the personnel card are used only in the level
3 (advanced) system.
In the advanced system, the deck is repunched each
cycle.
Changes may be made to the scheduled hours fields by repunching the
cards.
For example, if a staff member is going to be away, a "30" may be
punched for that week, and the system will not assign any actions for that
period.
See Figure 8.2.
190
-------
--------r.-
--. .--.. -..--.--...----..-- ....
-.--.-
Figure 8.1.
Let~er Card.
DP~TA
CP~~D
LAYOUt.
CARD FORM NO.
5081
TITLE
Letter Card
FILE
IDE NT.
P;'~OGRAI.A ilTLE
Enforcement Management System
CC'i}.',U:::NTS
~
(-
;
I . . .
~.--
. ,
I Agen
r Coue
-.
.
!/J
"
I.
"
18
...
"
... ..
..
M
at
..
,.
..
...
..
..
..
..
I.
..
so
IS ..
..
..
..
..
..
,.,
..
7.
78 78
J>e
Letter Text [one line]
o
z
'"'
Q)
.j.J
.j.J
Q)
~
o
z
Q)
s::
"M
~
L
-------
t-'
\0 .
I
(
i
! .
r -r r-r
I
f
IBB
!
I
I
i
I
i
I
,
!
!
,
! ,
~ . _.- - -. ..-----.--.------.'
--_._...~.__.- _..... .--...u. -"' ,--"---,-~-,-~,,,,-----,'~'~""'-'--"'-----'Y-"--- ~
._-------_..,-
Figure 8.2.
Personnel Schedule Card.
DATA
LAYOUT.
C/'\ni0
vi. i~ ;".1
5081
FILE
IDE NT.
TITLE Personnel Schedule Card
CARD FORM NO.
Enforcement Management System
PR(X;RM\ TITLE
CQ.'.'.\\ENTS
. .
o -=1°
Z 0 Z
'M
""' -IJ .
u u ~
~ ~~
bO
~ I
-.----.--'Level 3
.
"'_.__.,",.~.. --- ...._.~
:.. ..---Weekly Hours. -----_. .
.. -.-.-.-.-.--
Name
1
o : 11 -12 13
2
3
4
5
6
7
8. 9
Title
~
~
,
I J
-------
9.Q
KEYPUNCH INSTRUCTIONS
The following description of transactions for the Enforcement
Management System is included to assist in keypunch training.
Input is
considered to be punch cards, but these instructions will work equally
well with either a key-disk or key-tape system if card-image format is used.
SOURCE DATA CARDS
Card Column
1.
1- 3
Agency Code must be present.
Numeric right justified,
zero filled.
ex.
001, 010, 321
2.
4- 7
County Code must be present.
Numeric right justified,
zero filled.
ex.
0009, 0013, 0169
3.
8-12
Source Number must be present.
Numeric, right justified,
zero filled.
ex. 00004, 00601
13-17
(not shown) will always be zeros for card codes 1, 2, 3, 4.
(see below).
4.
18
Card Code must be present.
Numeric with a range of 1 to 8
(0 and 9 are not valid).
5.
19-20
UTM Zone is optional.
Must be two (2) numeric digits
(otherwise blanks).
6.
21-26
EW-Grid Coordinates is optional.
If used should .be numeric,
right justified, zero filled.
ex. 000120
193
-------
I B 11
INTERNA TlONAL BUSINESS MACHINES CORPORATION
Form X24.6299.4
Pri"'ed in U. S. A.
CARD PUNCHING OR VERIFYING INSTRUCTIONS
JOB NAME JOB NO. CONTROl OPERATION NAME OP. CODE MACH. TYPE
PANEl NO.
Source Card - Code (/1
FREQUENCY DUE IN DUE OUT EST!MA TEe. VOLUME EST. TIME
D DAILY 0 MONTHLY TIME DATE TIME DATE HOURS TENTHS
0 WEEKLY 0 QUARTERLY I
0 BI.WEEKL Y 0 ANNUAL
0 SEMI.MONTHL Y 0 OTHi:R
PROGRAM CARD NO. CARD ELECTRO (FORM>" NO. I
SWITCH SETTINGS - ON SPECIAL FEATURES USED I
o PROGRAM UNIT 0 PRINT 0 CARD CORRECTION 0 AUXILIARY DUPLICATE (VERIFY)
1 2
00 PROGRAM SELECT 0 LEFT ZERO PRINT 0 CARD INSERTION 0 SElF CHECK NO.
CK PCH 0 SELF CHECK NO. GENERA TOR
0 AUTO FEED 00 SELF CHECK NO. 0 AUTO LEFT ZERO
INS ST
0 AUTO SKIP-AUTO 00 CARD INSERT 0 ALTERNATE PROGRAM 0 VARIABLE LENGTH FEED
DUPL (VER) 0 HI SPEED SKIP 0 INTERSPERSED GANG P'UNCH I
SOURCE DOCU"""ENTS USED: DISPOSITION OF CARDS:
~ ..:-.
RECEIVED FROM: DOCUMENTS
COlUMNS !
CARD FiElD FUNCTION' FROM I THRU TOTAL: REMARKS
Agency Code (1 ) 1 3 3 Numeric
-
County Code (2) 4 7 4 Numeric
Source 11/0. (3) 8 12 5 Numeric
13 17 Zeros I
-
Card Code (4) 18 18 1 Always 1
UTM Zone - (5) 19 20 2 Numeric or Blan~
EW' Grid coor( h ) 21 26 6 Numeric or Blank
NS Grid Coord (7) 27 32 I 6 ~umeric or Blank I
Source Name( 8) 33 52 20 I Alpha left justified
(C) ) i I i right justified
Street No. - 53 I 57 5 I Alpha leading SDaces
Nami.1oJ I I
Street 58 72 15 I Alpha
Time Factor Cu) 73 75 3 Numeric x.xx
COdeCn) I u
-. Update 80 80 1 N C 0 FUNCTIO/,P SY""SOL
---.
+ I DU?LlCA TE I D
PUNCti P
SKIP S
X.SKIP XS
VERIFY V
I j SELF 0:. NO. CK
TOT AL K!:Y ST~O~:S ?!:R ('\~D - ! . LEFT z~,o tZ
D:1fe:
19/)
Section
Page ----
-------
- ..-- - -
SOURCE DATA EHT~.Y FORl-1
SOURCE DATA FOr~~
I .G). I
County Code
,COO,rdina (Y)
EW
I I
Source Name. .
Street ~-----..:
~.
C0
Time F-1ctor I
Card Code ~
.1
sour~.
.0.
NS
G)
GQ)'
~
Card Code
~
Agency Code
...
UTM Zone (if used) ~
Update
.0.
~jame
Code C)
N .~or
j)
GiL- .
,1;2 L-~£L-,
State Zip Code
City
L \~-
Area Code
~lePhon,e
SIC Code
L-(iiL
Agency
Inspector ;';0.
Card Code
Ji)
~-------. .' r'
Source DeS~ion
Card Code ~~
Llne Code
Commen~s:
Contact
L-~
Agency
Engineer No.
~
(Leave blank except "e")
___.1
.J
Update
Code Q
:-J, (J, or
D
J -
Update
COdeG
N, C. or D
G)
---
-.- -------~-_._-
--.----------.
- ---------_.
195
-------
10.
11.
12.
7.
27-32
NS-Grid Coordinate
is optional.
8.
33-52
See entry number 6.
Source Name is optional.
If used should be alphanumeric,
9.
53- 5 7
left justified.
Street Number is optional.
If used should be numeric, right
58-72
73-75
80
justified, space filled.
ex.~~~22 not 00022
Street Name is optional.
If used should be alphanumeric,
left justified.
Time Factor is optional.
If used should be three
numeric digits.
Update Code must be present.
Only valid entry is N, C or D.
Second Card of Source Data.
Columns 1 thru 17 should be picked up from
first card, either duplicated or re-entered.
13.
14.
15.
16.
19-33
34-35
36-40
41-50
City is optional.
If used must be alphanumeric, left
justified.
State (abreviation) is optional.
When used should be
alphebetic.
Zip Code is optional.
When used should be five (5)
numeric digits.
Telephone Number is optional.
First three digits (4l,to 43)
is the area code, followed by local phone number with no
imbedded spaces or hyphens
ex. 2025274101
196
-------
... ';"1 "\ "
.\:) ~-(~
INT:RNATiONAl .;USINES5 MA':Hi:'-tS CO.::?OR:'TlON
Form X24.62?9.~
Prin'.d in U. S. A:
CARD PUNCHING OR VEP.It=YING INSTRUCTIONS
..
JOg NAN;E JOB NO. CONTROl OPERATION NAME OP. CODE MACH. TYPE.
PANEL NO.
Source Card - Code 2 .
. -
FREQUENCY DUE IN DUE OUT ESTIMATED VOLUME EST. TIME.
o DAilY 0 MONTHLY TIME DATE TIME DATE HOURS TENTHS
o WE:Kl Y a QUARfERl Y I
0 81. WE:Kl Y 0 ANNUAL
0 SEMI.io\ONTHl Y . 0 OTH~R
I PROGRAN. CARD NO. CARD ELECTRO (FORM) NO..
SWITCH SETTINGS - ON SPECIAL FEATURES USED
0 PROGRAM UNIT 0 PRINT 0 CARD CORRECTION .0 AUXILIARY DUPLICATE (VERIFY)
I '2
00 PROGRAM SELECT 0 LEFT ZERO PRINT 0 CARD INSERTION 0 SELF CHECK NO.
CK PCH 0 SELF CHEC;K NO.' GENERATOR
o AUTO FEE:) 00 SELF CHECK NO. 0 AUTO LEFT ZERO
INS Sf 0 ALTERNATE PROGRAM 0
0 AUTO SKIP.AUTO 00 CARD INSERT VARIABLE LENGTH FEED
DUPL (VER) 0 HI SPEED SKIP 0 INTERSPERSED GANG PUNCH
SOURCE DOCUMENTS USED: DISPOSITION OF CARDS:
",:,
RECEIVED FROM: DOCUMENTS
--
COLUMNS
CARD FIELD FUNCTION' REMARKS
FROM THRU TOTAL
.
Header Data 1-3 1 17 Dup from Code 1 card
- (4 )
Card Code 18 18 1 Always 2
City (13) 19 33 15 Alpha
-- (14)
State 34 35 2 Alpha
Zip ell)) 36 40 5 Numeric
-
Telephone (16) -
41 50 10 Numeric
Contact ~7) 51 65 15 Alpha
Source Code (SIC) -Gs ) - 66 70 5 NU1\leric or . Blank
Assigned Inspec t Code -c19) 71 73 3 Numeric or Blank
Assigned Engr. No{20 ) 74 76 '3 Numeric or Blank
\ Update Code (12) 80 80 1 ~ C or D
~.
FUNCTION< SYMSOL
"_. --
'. "------1 --L- DUPLICATE D
PUNCH P
S
I [;'::" XS
----- - - ---.---f-- ~- VERifY V
TOT AL ' , -.- CC> . SELF CK. NO. CI(
KE) STROKe:.:> P~X CAR~~J___- --- --- -___~_:f::v -- lZ
.---- -----
D.:: 1<:: --------------
197
Scct;on___- POSIt: --_..:..-
-------
IB~~
INTERNATIONAL BUSINESS MACHINES CORPORATION
Form X24.6299.4
Prin;ed in U. S. A.
CARD PUNCHING OR VERIFYING INSTRUCTIONS
I'
JOB NAME JOB NO. CONTROL OP~RA TION NAME OP. CODE MACH. TYPE
PANEL NO.
Source Card - Code 3
FREQUENCY DUE IN DUE OUT ESTJMA TED VOLUME EST. TIME
o DAILY 0 MONTHLY TIME DATE TIME DATE HOURS TENTHS
o WEEny 0 QUARTERLY I
0 BI.WEEKL Y 0 ANNUAL
0 SEMI.MONTHL Y 0 OTHER
PROGRAM CARD NO. CARD ELECTRO (FORM) NO.
SWITCH SETTINGS. ON SPECIAL FEATURES USED
0 PROGRAM UNIT 0 PRINT 0 CARD CORRECTION 0 AUXILIARY DUPLICATE (VERIFY)
1 2
DOPROGRAM SELECT 0 LEFT ZERO PRINT 0 CARD INSERTION 0 SELF CHECK NO.
CK PCH 0 SelF CHECK NO. GENERATOR
o AUTO FEE:::> 00 SELF CHECK NO. 0 AUTO LEFT ZERO
INS ST
0 AUTO SKIP.AUTO 00 CARD INSERT 0 ALTERNATE PROGRAM 0 VARIABLE' LENGTH FEED
DUPL (VER) 0 HI SPEED SKIP 0 INTERSPERSED GANG P'UNCH
SOURCE DOCUMENTS USED: DISPOSITION OF CARDS:
;
."
..
RECEIVED FRO,"\: DOCUMENTS
COLUMNS
CARD FIELD FUNCTION' REMARKS
FROM THRU TOTAL
Header Data 1-3 - 1 17 Dup from r.nr'lol Cr:Jrr'l
Card Code (4) 18 18 1 Always 3
Source Description ~1 19 I 43 25 Alpha
Update Code (12) 80 RO 1 ~ C or D
I
.,
FUNCTICW SYMBOL
. . ! DUPliCA H D
PUNCH ;>
E j
I I SKIP 5
I X.SK/P XS
VERIFY V
?E~ (ARD'-I i I SElF CK. NO. ':K
TOT AL KEY STROKES I lEFT ZOPO . 7
L-
L .
Dot!:': "_._~-
-~~- ~.- .
- .-
198
Section
Page --
-------
17.
18.
19.
20.
51-65
66-70
71-73
74-76
Contact is optional.
Alphanumeric left justified.
SIC Code is optional.
Numeric, right justified, zero
filled.
ex.
00022,
02460
Agency Inspector Number is optional.
First character
can b~ alphabetic, second and third are numeric.
ex.
121, N29.
Agency Engineer Number is optional.
First character
can be alphabetic, second and third are numeric.
ex.
E09, G24.
Third Card of Source Data.
Columns 1 thru 17 should be picked up from
first card, either duplicated or re-punched.
21.
19-43
Source Discription is optional.
Alphanumeric> left justified.
Fourth Card of Source Data.
Columns 1 thru 17 should be picked up from
previous card, either duplicated or re-punched.
22.
23.
19
20-79
Line Code must be present.
If Update Code is "C", this
field should already be coded.
Otherwise operator must
insert correct numeric value.
First card will be 1, next
2, etc.
See below for comments description.
Comments must be present if card code 4 is used.
Comments
are free-formed (starting at column 20 and continuing on)
with run-overs to next card, in which case the line code must
be incremented.
Words should not be broken (hyphenated) but
brought over to next comment card.
Maximum nine
cards.
199
-------
IB11
INTE~NATIONAl BUSINESS NACHINES CC~PORATION
Form X24.629'? 4
Prin'~d in U, S. A.
CARD PUNCHING OR VERIFYING INSTRUCTIONS
JOB NAME J06 NO. CONTROL OPERA nON NAME OP. CODE MACH. TYPE
PANEL NO.
Source Card - Code 4
FREQUENCY DUE IN DUE OUT ESTIMATED VOLUMJ: EST. TIME
o DAilY 0 MONTHLY TIME DATE TIME DATE HOURS TENTHS
o WEEKLY 0 QUARTERLY I
0 ill.WEEKl Y 0 ANNUAL
0 SEMI.MONTHl Y 0 OTHE~
PROGRAM CARD NO. CARD ELECTRO (FORM) NO.
SWITCH SETTINGS. ON SPECIAL FEATURES USED
0 PROGRAM UNIT 0 PRINT 0 CARD CORRECTION 0 AUXILIARY DUPLICATE (VERIFY)
1 2
00 PROGRAM SELECT 0 LEFT ZERO PRINT 0 CARD INSERTION 0 SElF CHECK NO.
C1< PCH 0 SElF CHECK NO. GENERATOR
o AUTO FEED 00 SELF CHECK NO. 0 AUTO LEFT ZERO
INS ST
0 AUTO SKIP-AUTO 00 CARD INSERT 0 ALTERNATE PROGRAM 0 VARIABLE LENGTH FEED
DUPL (VER) 0 HI SPEED SKIP 0 INTERSPERSED GANG PUNCH
SOURCE DOCUMENTS USED: DISPOSITION OF CARDS:
~ .:-,
RECEIVED FROM: DOCUMENTS
COLUMNS :
CARD FIELD FUNCTION' FROM I THRU i TOTAL I REMARKS
Header Data l-~ 1 17 Dup from Code 1 card
Card Code (4) 18 18 Always 4
". Comments Line Number( 22 ') 19 19 1 I Numeric
Comments G3)~ 20 74 55 Alpha
Update Code (]2) 80 80 N C or D
-
I I
I
I
I
I '
I
~._-- -.
.--
I FUNCTION* SYMBOL
I DUPLICATE C.
PUNCH P
I SKIP S
I X.SKIP XS
~---_. . VERIFY V
I SElF C1<. NO, (K
TOT AL I<::Y .sT~:O:<:S ?=~ CARO- I . LEFT ERO lZ
-. ' I
----'-
D(,!(': ---
200
Seclicn_____- Page ------
-------
. Permit ~ .
~ ~
Update ~ C)
l.;ode N~
, , or D
/
, ----
l@
Cou~ ty Co'de I
~4
. I
Em~s ~on
Point No.
SOURCE DAT\
EMISS I. ENTRY FORH
ION POT~ .--
, 'W ,T ENTRY FOR"
Sourc ' . ~ r\4°
.0. ,-M..}
Card Code
D",(i) .
esc.r;-pt' '
,,~~ "
Control D '. '
e 1ce
I " Ci2
Pollutan'ts . :
c~~L W
L1ne Code
(Lv Blank
Except C)
Comments
L '
R.giS~' .
1011 Number
j .
201
Updatd
~
Ag~~:t~ .
. , .
Code 0
N'tL.e:!
, , or
D
-------
Emission Point data card.
Entries 1, 2, 3 should be duplicated from Source
Data cards or re-entered.
24.
25.
26.
27.
13-15
16-17
19-43
44-63
64-79
Emission Point must
Three
numeric
be present.
digits 000 to 999.
(not shown)
Must be zeros 'for Card Code 5 and 6.
Description is optional.
Alphanumeric,
left justified.
Control Device is optional.
Alphanumeric,
left justified.
Pollutants is optional.
Alphanumeric, left justified.
Emission Point Comment record.
Entries 1, 2, 3, 24 should be duplicated from
previous card or re-entered.
28.
29.
20-54
55-66
Comments must be present if Card Code is 6 or 8.
All
comments are free-flowing and can continue on next card
if
too much data is provided.
When comments are continued on
another card, line code must be incremented.
Words may not.
be split (hyphenated) but should be carried over to next card.
Maximum 9 cards.
Registration Number is optional.
Alphanumeric or numeric,
left justified.
ex. AB246 ,
32167980
202
-------
-- -- - -
IB~~
I:-ITERNA TlONAl euS:NESS MACHINES CORPORATION
Form X24.6299.4
Prin'ed in U. S. A.
CARD PUNCHING OR VERIFYIN.G INSTRUCTIO~~S
JOB NAME JOB NO. CONTROL OPERATION NAME OP. CODE MACH. TYPE
EPt. Card - Card 5 PANEL NO.
FREQUENCY DUE IN DUE OUT ESTIMA TED VOlUME EST. TIME
o DAilY 0 MONTHLY TIME DATE TIME DATE HOURS TENTHS
o WEEKLY 0 QUARTERLY I
0 BI.WEEKL Y 0 ANNUAL
0 SEMI-MONTHlY 0 OTHER
PROGRAM CARD NO. CARD ELECTRO (FORM) NO.
SWITCH SETTINGS. ON SPECIAL FEATURES USED
0 PROGRAM UNIT 0 PRINT 0 CARD CORRECTION 0 AUXILIARY DUPLICATE (VERIFY)
I 2
00 PROGRAM SELECT 0 LEFi ZERO PRINT. 0 CARD INSERTION 0 SELF CHECK NO.
CK PCH
0 AUTO FEE:> 00 SELF CHECK NO. 0 AUTO LEFT ZERO 0 SELF CHECK NO. GENERA TOR
INS ST
0 AUTO SKIP.AUTO 00 CARD INSERT 0 ALTERNATE PROGRAM 0 VARIABLE LENGTH FEED
DUPL (VER) 0 HI SPEED SKIP 0 INTERSPERSED GANG PU N C H
SOURCE DOCUMENTS USED: DISPOSITION OF CARDS:
. "
u
RECEIVED FROM: DOCUMENTS
COLUMNS
CARD FIELD FUNCTION' FROM I THRU . REMARKS
TOTAL
Header Data 1-:) 1 12 I f)",... f",.nm ('. -' 1 ~ ~~,
E. Pt. No. (24') 13 15 3 Numeric
=
16 17 2 Zeros
Card Code (U) 18 18 1 . Always 5
Description (?C) 19 43 25 Alpha
Control DeVic~?h) 44 63 20 Alpha
Pollutants T27) 64 79 16 Alpha
Update Code ~) 80 80 1 .N C or D
I
i
I fUNCTlCW I SYMBOL
DUPLICATE D
PUNCH P
~ SKIP S
X.SKIP XS
VERIFY V
TOTAL K!:Y snOKES ?~R CARD- i SelF CK. NO. CX
LEFT ZEQO .LZ
DalE':
203
S.;clion
i'oge ---
-------
I B!Yt
INTERNATIONAL BUSINESS MACHINES CORPORATION
For", X24.6299.4
Printed in U. S. A.
CARD PUNCHING OR VERIFYING INSTRUCTIO~~S
JOB NAME JOB NO. CONTROL OPERATION NAME OP. CODE MACH. TYPE
PANEL NO.
E-PT Card - Card 6
FREQUENCY DUE IN DUE OUT ESTIMA TED VOLUM..E EST. TIME
o DAilY 0 MONTHLY TIME DATE TIME DATE HOURS TENTHS
o WEEKLY 0 QUARTERLY I
o BI.WEEKl Y 0 ANNUAL
0 SEMI.MONTHl Y 0 OTHeR
PROGRAM CARD NO. CARD ELECTRO (FORM) NO.
SWITCH SETTINGS. ON SPECIAL FEATURES USED
0 PROGRAM UNIT 0 PRINT 0 CARD CORRECTION 0 AUXILIARY DUPLICATE (VERIFY)
1 "2
oOPROGRAM SELECT 0 LEFT ZERO PRINT 0 CARD INSERTION 0 SElF CHECK NO.
CK PCH 0 SELF CHECK NO. GENERATOR
o AUTO FEE:> 00 SELF CHECK NO. 0 AUTO LEFT ZERO
INS Sf
0 AUTO SKIP.AUTO 00 CARD INSERT 0 ALTERNATE PROGRAM 0 VARIABLE' LENGTH FEED
DUPL (VER) 0 HI SPEED SKIP 0 INTERSPERSED GANG P'UNCH
SOURCE DOCUMENTS USED: DISPOSITION OF CARDS:
. '..
RECEIVED FROM: DOCUMENTS
COLUMNS
CARD FIELD FUNCTION' REMARKS
FROM THRU TOTAL
Header Data L 2/ 3/ 24 1 17 Dup from c:;ode 5 card
Card Code (4) 18 18 1 Always 6
Comments Line Number~ 19 19 1 Numeric
..
Comments G8) 20 54 35 Alpha
Registration Number ~9 55 66 12 A1pha/ Numeric
Permit Number (30) - 67 78 12 Alpha /Numeric
Update Code (12 80 80 1 N,C or D
I
FUNCTlON* SYMBOL
I DUr'liCA TE 0
PUNCH P
SKIP S
X-SKIP XS
- VERIFY V
SELF CK. NO. CK
TOTAL K::':' STROi<:S PER CARD- lEFT ZERO tZ
_.
Dot€':
204
Sc~ti.:)n
Page --
-------
'!." ...,"' .'~
30.
67-78
Manual Action Card.
I"I"~"'I~I..._.... -.... ---
- . . - _.
Permit Number is optional.
left justified.
ex.
PT324, 67831
Alphanumeric or numeric,
Entries 1, 2, 3, 24 must be keypunched before following
data can be entered.
31.
16-17
32.
52-53
33.
54-59
34.
60-65
35.
66-68
36 69-70
37. 71-72
38. 73-74
39. 75-76
40. 77-78
Action Number must be present.
Action Type is optional.
Two numeric digits 00 to 99.
digit is provided it should be right justify, preceded with a
Two numeric digits.
If one
zero.
ex.
2 is given, 02 is keypunched.
Numeric
in month, day, year format.
Action Date is optional.
Next Action Date is optional.
Staff Number is optional.
Numerics in month, day, year format
First character may be alphia,
second and third are numeric.
ex.
121, E46, 232
Action Results is optional.
Hours Taken is optional.
Next Action is optional.
Two numeric digits.
Two numeric digits.
Two numeric digits.
Estimated Hours to complete is optional.
Two numeric digits.
Two numeric digits.
Send Letter Number to Source is optional.
205
-------
0-'..,1..
. . ~ " -."..........
rorm )t14.6299..!
P,in'.d in U. S. A.
CARD PUNCHING OR VERIFYING. INSTRUCTIONS
-
JOB NAN.E JOB NO. CONTROL OPERA nON NAME OP, CODE MACH. TYPE
PANEL NO.
Action Card - .Card 7
FREQUENCY DUE IN PUE OUT ESTIMATED VOLUM..E EST. TIME
o DAILY 0 MONTHLY TIME DATE TIME DATE HOURS TENTHS
o WE:!(L Y 0 QUARTERLY I
0 BI.WEEKLY 0 ANNUAL
0 SEMI.MONTHL Y '0 OTHER
P.ROGRA,\\ CARD NO. CARD ELECTRO (FORM) NO..
SWITCH SETTINGS - ON SPECIAL F.EA TURES USED
0 PROGRAM UNIT 0 PRINT 0 CARD CORRECTION . 0 AUXILIARY DUPLICATE (VERIFY)
I 2
00 PROGRAM SELECT 0 LEFT ZERO PRINT 0 CARD INSERTION 0 SELF CHECK NO.
CK PCH 0 SELF CHECK NO,' GENERA.TOR
o AUTO FEE:J 00 SELF CHECK NO. 0 AUTO LEFT ZERO
INS ST OALTERNATE PROGRAMO
0 AUTO SKIP.AUTO 00 CARD INSERT VARIABLE LENGTH FEED
DUPL (VER) 0 HI SPEED SKIP 0 INTERSPERSED GANG PUNCH
SOURCE DOCUMENTS USED: DISPOSITION OF CARDS:
'"
RECEIVED FRON,: DOCUMENTS
COLUMNS
CARD FIELD FUNCTION' REMARKS
FROM THRU TOT AL
. (1)
Agency Code 1 3 3 Numeric
.. County Code (2 4 7 4 Numeric
Source No. 1) 8 12 5 Numeric
E. Point No. G4 13 15 3 Numeric
Action No. (31) 16 17 2 Numeric
- (4 _.
Card Code 18 18 1 Always 7
Action Code ~2) 52 53 2 Numeric or Blank
(TI I
Date Performed . 54 59 6 Numeric or Blank
- - --
.. Date Schedule (34) 60 65 6 Numeric or Blank
- Numb e.:.. Gs
Staff Member 66 68 3 Alpha
-- i3G)
Results 69 70 2 Numeric
_. --
HRS taken Q7 71 72 2 Numeric
- (30)
Next Action 73 74 2 Numeric FUNCTION * SYMBOL
-- ~
Hrs. to complt. _09 75 76 2 Numeric DUPLICATE D
PiJNCH P
-. Send Letter (40)' SXIP s
77 78 2 Numeric X.SKI? XS
-.---- -- VER!fY v
~Pda~~~~~~----- [0'--- '--- ~--~~-~ P SElF CK. NO. CK
or LEn ZE::O I LZ
..
0"1-::: -------------
~ecti0n~- ~----
PO<:J!'! c.
-------
"'.'Q".\.7
J' .i ,+
INTEilNATIONAL ;USINESS MACHI.~cS CO~?6~ATlON
form X2~.~2?,. 4
Pri"'ed on U. ,). A.
CARD PLJNCHING OR VERlcYING INSTRUCTIONS
JOB NAME JOB NO. CONTROL OPERATION NAME OP. CODE MACH. TYPE
PANEL NO.
Action .Card -'Card 8.
.'
FREQUENCY DUE IN DUE OUT ESTIMATED VOlUME EST. n.ME.
a DAILY D MONTHLY TIME DATE TIME DATE HOURS TENTHS
a WEEKLY D QUARTEilL Y . . f
a BI.WEEKL Y 0 ANNUAL
a SEMI.MONTHLY '0 OTHER
P.ROGRAM CARD NO. CARD ELECTRO (FORM) NO..
SWITCH SETTINGS - ON SPECIAL FEATURES USED
u PROGRAM UNIT 0 PRINT 0 CARD CORRECTION . 0 AUXILIARY DUPLICATE (VERIFY)
I 2
. . ':J PROGRAM SELECT 0 LEFT ZERO PRINT 0 CARD INSERTION 0 SELF CHECK NO.
CK PCH 0 SELF CHECK NO:: GENERATOR
U AUTO FEE:> 00 SElF CHECK NO. 0 AUTO LEFT ZERO
INS Sf 0 AL TERNA TE PROGRAM 0
0 AUTO SKIP-AUTO 00 CARD INSERT VARIABLE LENGTH FEED
DUPL (VER) 0 HI SPEED SKI? 0 INTERSPERSED GANG PUNCH
SOURCE DOCUMENTS USED: DISPOSITION .OF CARDS:
. -
..~..
RECEIVED fROM: DOCUMENTS
COlUMNS
CARD FIELD FUNCTION" REMARKS
FROM THRU TOTAL
I
Header Data 1. ? .3. ?4. '31 1 17 Dup. from Codp 7 (,Rrrl
Card Code '(4) 18 18 1 Always 8
Comments Line Number G2 19 19 1 Numeric
--
f Comment$ (41) 20 54 35 Alpha
t" Update Code (,?J 80 80' 1 N C or D
-
~. .
.
-
I
~-
FUNCTION> SYM30l
- I
1
- . ..__.J DUPLICATE D
Pl!NCH P
---- s
-c--~.+--i-~L_- - S.'(I?
X.Si
-------
~T'--
z~ ~,
'2'2:
.~ w ~
'"' - C"" G>
.~ ~~ !i1
MJ ";-5 C"-"'"
uOcn
i:>, /! ~
~-'. ~ ~
o 2 tff~
L~ <.!
'2 >
~J i
20
Q~
'p. IH t'~,'.'r"{ I
C;..~ .. ~ II -;- I -,.. .~_...... 'I
., . -" . I I
-_.-_.----.:_--_.=~~-~=~:_.._.----- .--... J .._::'.!..?Y.~~-~2.!:..'J.::'~~' C'--~--L2 P L.\ ~I:': f:.?_~~~~.__. -----.l--.. '"-
c01.n.~;:~~T5:
-----" ----~-==~--=-v-..~~_.._- -"---- -..- --.-......-.----.----.---------..
'11 . . -...-------..-.-.-.-.---...-.-----------
Lf ---.----..----..
--------------..--.. - -... .---- "'---..--- '--'-------"- ---..------. -- ----...-.
---~;; ~;:;:;:,-_.-- - .. --"- '--'- --'''--- -"" ---.. -"-. u_--..-..-.---.----...
..------.------.-----. --
208
-------
Computer Generated Action Card.
This card has been generated by the
system from a previous cycle.
It must re-enter the system with any
new information added to it.
Column 1 through 53 (entries 1,2,3,4,24,
31 and computer generated data) must be duplicated onto another card.
Columns 53 through 68 must be blank if entries 33, 34 or 35 are not used.
Column 80 (which must have a "C") is also duplicated.
Information for
entries 34 through 40 is punched into the second card as it is read off
the Action Card.
Once completed, the Action Card (old card) is discarded.
41.
20-54
If used, columns 1 through 17 must
Comments are optional.
be duplicated (from above mentioned card).
8 is used as Card
Code (entry 4), and an "N" used as Update Code (entry 12).
Instructions for Line Code and Comments are the same as entries
22 and 28 respectively.
209
-------
BIBLIOGRAPHIC DATA 11. Report. No.
SHEET
~&tTe and Su.bcnle
~nforcement Management System
f~
-
-'
Users' Guide
7. AUl:boc(8)
- .. ~
c::. r. Shanks,.R. R. Hipp.:..er and'E.
9. PcrfocmiDJ Or,gaDwtioD }.;ame aoei AeidtU8
'.
-
- .
Cohen
-
-
-.
TRC--The Research Corporation of
125 Silas Deane Highway
Wethersfie1d, Connecticut 06109
New England.
12. SeoD.oriog V1l\tUI&A&UOD ("'IDG.a.lld-~...-.
Environmental Protection Agency
Office of Air Programs
Research Triangle Park, N. C. 27711
15. SupplemeDcary Norea
16. Ab,cr.cra
3. RecipieDc's AccessioD No.
--
50 Report Date
: March, 1972
6.
-
-
.. Perf~minJt Or~.DizatioD Rept.
No. TRC 4 Z:"088-00
10. \ Pcoject/T ask/Wock Unit No.
.1 . - .. ,J-
11. C::0ntract/Gc.Dt No.
68-02-0079
13. Type of Report &. Peciod
Coycced
Users' System Guide
1...
A system was developed for use by air pollution agencies at the state and
local levels. The system records, monitors, summarizes agency actions in
the enforcement and survellience area. It provides staff members with
schedules of planned future actions and summaries of emission source ori-
ented data. The system is available in three versions, tailored to agencies
of different resource levels. Two of the levels are computerized and pro-
vide automatic monitoring of operational activities.
17. Key "ords .od Doeu_oc Analysis. 170. De,ccipcon
Scheduling of Activities
Emission Source Data
Action Scheduling & Management
Computerized Management Systems
Enforcement Data Handling
Air Pollution Enforcement Data
- .
17b." Iaen'[uiers-;Upen-EDc1ed TeftD8
Information Systems
Management Control
Operations Monit0ring
Air Pollution Agency
. Administration
17eo caSA TI Fie !d/Gtoup
18. Ani/acdICI ~Uteo
------- |