u -,:te;i S>
Prptectknn
Agt;r
Cfiica of Air Quality
Planning and Standards
Washington DC 20460
Stationary Source Compliance Series
Compliance Data
System User's
Guide
EPA-340/1-83-020
August 1983
-------
EPA-340/1-83-020
Compliance Data System
User's Guide
Prepared by
Gregory M. Fisher
Project Manager
Robert D. Bowers
Systems Analyst
J. Chris Mason
Senior Programmer'Analyst
TRC Environmental Consultants, Inc.
800 Connecticut Boulevard
East Hartford. Connecticut 06108
Contract No. 68-01-6315
John R. Busik, EPA Project Officer
Franklin Smith, EPA Task Manager
Prepared for
U.S. ENVIRONMENTAL PROTECTION AGENCY
Stationary Source Compliance Division
Office of Air Quality Planning and Standards
Washington, D.C. 20460
August 1983
-------
DISCLAIMER
This report was furnished to the Environmental Protection Agency
by TRC Environmental Consultants, Inc. in partial fulfillment of
Contract 68-01-6315. The contents of this report are reproduced
here in as received from the contractor. The opinions, findings,
and conclusions expressed are not necessarily those of the
Environmental Protection Agency.
ii
-------
The Stationary Source Compliance Division Series of reports is issued
by the Division of Air/ Noise and Radiation Enforcement of the U.S.
Environmental Protection Agency, to report enforcement related data
of interest. Copies of this report are available free of charge to
Federal employees, current contractors and grantees, and non-profit
organizations - as supplies permit - from the Air Pollution Technical
Information Center, Environmental Protection Agency, Research
Triangle Park, North Carolina, 27711 or may be obtained, for a nomi-
nal cost from the National Technical Information Service, 5285 Port
Royal Road, Springfield, Virginia 22151.
-------
TABLE OF CONTENTS
SECTION PAGE
1.0 INTRODUCTION
2.0 MANAGEMENT OVERVIEW 2
2.1 Background History 2
2.2 System Purposes 3
2.3 System Capabilities 3
2.4 System Functions 4
2.5 System Relationship to Other EPA Systems 6
3.0 SYSTEM APPLICATIONS 7
3.1 General Applications 7
3.2 Examples of Specific Applications 8
4.0 SYSTEM OVERVIEW 12
4.1 Edit Program 13
4.1.1 Input Data Processed by CDS 13
4.1.2 Edits Performed by CDS 14
4.1.3 Edit Error Messages 17
4.1.4 CDS MOD File 17
4.2 Update Program 18
4.2.1 Update Actions to CDS 19
4.2.2 Update Cycle Steps 19
4.2.3 Update Report Messages 20
4.2.4 The CDS Masterfile 22
4.2.5 Regional CDS Masterfile 23
4.3 Retrieval Program 23
4.3.1 Description of Reports Available from Retrieval
Program 25
4.3.2 Retrieval Steps 27
5.0 DATA SUBMISSION PROCEDURES 29
5.1 Submission Steps 29
6.0 DATA INPUT PREPARATION 32
6.1 General 32
6.2 Adding New Records to the CDS Masterfile 35
6.2.1 Sample of a Completed Coding Sheet for a New
Facility 45
6.3 Changing Data on the CDS Masterfile 47
6.3.1 Sample Completed Coding Sheet for Change
Transactions 49
6.4 Deleting Data from the CDS Masterfile 51
6.4.1 Sample Completed Coding Sheet for Delete
Transactions 52
6.5 Keypunch Instructions 53
6.6 Quality Assurance Considerations . 61
6.6.1 Define the Problem 61
6.6.2 Status of Current Data 61
-------
TABLE OF CONTENTS
(Continued)
SECTION PAGE
6.6.3 Code Data 61
6.6.4 Random Check of Coding 62
6.6.5 Computer Operations 62
7.0 EDIT PROCESSING 64
7.1 Edit Program Usage ..... 64
7.1.1 Warning and Fatal Errors 66
7.2 Edit Error Messages 66
7.3 Sample CDS Edit Report 69
7.4 Edit Job Control Language (JCL) 71
7.5 CDS Input Preparation via WYLBUR 71
7.6 CDS/WYLBUR Example 73
8.0 UPDATE PROCESSING 82
8.1 Update Program Description 32
8.2 Update Scheduling 84
3.3 Update Report 85
8.4 Update Report Messages 87
8.5 Update Status Log 91
8.6 Update Report Job Control Language 91
3.7 Critical Data Elements Report 95
9.0 RETRIEVAL PROCESSING 95
9.1 Reports Available from the Retrieval 96
9.1.1 Quick Look Report 97
9.1.2 Double Spaced Quick Look Report 100
9.1.3 Source Data Report 100
9.1.4 Milestone Report 102
9.1.5 Questionnaire Report 10-
9.1.6 Action Summary Report 107
9.1.7 Compliance Action Report 107
9.1.8 Special PSD Report Hi
9.2 Checklist for Request Submission 112
9.3 Preparing Retrieval Selection Cards 118
9.3.1 Special Considerations for Pollutant Compliance
Retrievals 130
9.3.2 Pollutant Compliance Logic Selection 130
9.3.3 . Pollutant Compliance Sorting 132
9.3.4 Printing Pollutant Compliance Data 132
9.3.5 Sample of a Filled-in Retrieval Request 132
9.4 Job Control Language for Using Retrieval Program . 133
9.5 Retrieval Edits Performed by System 142
9.6 Special Retrieval Features 142
9.6.1 String Search 142
9.6.2 Quick Look Comments 151
9.6.3 Retrievals Available Through TRC 152
9.6.4 CDS Query 152
9.7 WYLBUR Execs 152
9.7.1 Input 152
9.7.2 Report 158
9.7.3 Tables 158
VI
-------
SECTION
10.0
11.0
12.0
13.0
14.0
15.0
TABLE OF CONTENTS
(Continued)
10. 1
10.1. 1
10.1.2
10.1.3
10.1.4
10.1 .5
10.1.6
102
10.2.1
10.2 2
10. 2.3
10.3
10.4
105
10.6
User Responsibility for Backup
Recovery Procedures ....
Microfile Considerations .
11.1
11.2
11.3
13.1
13.2
13.3
13.4
13.5
STATE ENFORCEMENT SYSTEMS
State Enforcement System Options
State Enforcement System Usage
Summary of State Enforcement System Options
DOCUMENTATION UPDATES
HEADQUARTERS GUIDANCE AND QUALITY CONTROL MEASURES
Sources to be Tracked
Data to be Tracked for All Sources .
Data to be Tracked for Selected Sources
Quality Control for Required Data Elements . . .
Summary of Data Standards Recommendations . . . .
CDS GRAPHICS
CONTINUOUS MONITORING SUBSET
PAG_E
161
161
161
162
164
166
168
170
170
170
172
172
172
173
180
180
182
182
183
194
198
199
199
200
203
204
207
208
209
APPENDICES
INDEX
CDS DATA ELEMENT DICTIONARY
A.I Source Level Data Elements
A.2 Point Level Data Elements
A.3 Action Level Data Elements
A.4 Common To All Cards Data Elements
CONTACT LIST OF CDS USERS
V1T
-------
LIST OF FIGURES
FIGURE PAGE
4-1 Edit Program Flow Chart 16
4-2 Update Flow Chart 21
4-3 Masterfile Hierarchy 24
4-4 Retrieval Flow Chart 28
6-1 Multiple-Card Layout Form 33
6-2 Sample Coding Sheet 36
6-3 Sample of Completed Coding Sheet for a New Facility .... 46
6-4 Sample of completed coding Sheet for Change Transaction . . 50
6-5 Sample of Completed Coding Sheet for Delete Transactions . 54
7-1 CDS Edit Job Control 65
7-2 Sample Edit Report 70
7-3 Using the Edit's Dummy Option -72
7-*4 Input from Tape 73
7-5 Saving the Reject File 74
7-6 Printing the Reject File .75
7-7 Sample WYLBUR Session to Convert Retrieval Output into
Input to CDS Edit 76
7-8 Retrieval JCL for Edit Input 79
8-1 CDS Update Report Job Control 36
8-2 Sample Update Report 88
8-3 Contents of Update Status Log 92
3-4 Sample Critical Data Element Report 94
9-1 Quick Look Report with Data Suppression 99
9-2' Double Spaced Quick Look 101
9-3 Source Data Report 103
IX
-------
LIST OF FIGURES (Cont.)
FIGURE PAGE
9-4 Standard Milestone Report 105
9-5 Variable Milestone Report 106
9-6 Sample Questionnaire 108
9-7 Action Summary Report 109
9-8 Sample Compliance-Action Report 110
9-9 Sample PSD Report 113
9-10 Report Request Form 115
9-11 Mailing Label Job Control 119
9-12 Retrieval Request Form to Obtain Quick Look Report 134
9-13 Retrieval Request Form to Obtain Source Data Report .... 135
9-14 Retrieval Request Form to Obtain Milestone Report 136
9-15 Retrieval Request Form to Obtain Variable
Milestone Report 137
9-16 Retrieval Request Form to Obtain Questionnaire 138
9-17 Retrieval Request Form to Obtain Action Summary 139
9-18 Retrieval Request Form to Obtain Compliance
Action-Report 140
9-19 Retrieval Request Form to Obtain PSD Report 141
9-20 Retrieval Job Control
142
9-21 Retrieval Job Control for Multiple Copies 144
9-22 Retrieval Job Control for 100,000 Lines of Output 145
9-23 Retrieval Edit Report 150
9-24 Sample WYLBUR Exec REPORT' 159
10-1 County Code Table 163
10-2 Sample Personnel Table 165
10-3 Sample Action Table 167
-------
LIST OF FIGURES (Cont.)
FICURE PAGE
10-4 Sample Results Code Table 169
10-5 Masterfile Layout 171
10-6a WCS Request for Micrographics
(Micrographics User Information for CDS) 174
10-6b WCS Request for Micrographics
(CDS Microform Input) 175
10-6c WCS Request for Micrographics
(CDS Microform Output) 176
10-6d WCS Request for Micrographics
(CDS Microform Output - Continued) 177
10-6e WCS Request for Micrographics
(CDS Microform Page Breaks) 178
10-7 Microfiche Job Control 179
13-1 Enforcement Actions Required for F\ 1981 202
13-2 Sample Critical Data Element Report 206
-------
LIST OF TABLES
TABLE PAGE
6-1 Keypunch Instructions for Card Type 3 42
6-2 Keypunch Instructions for Data Required on All Cards ... 55
6-3 Keypunch Instructions for Card Type 1 56
6-4 Keypunch Instructions for Card Type 2 57
6-5 Keypunch Instructions for Card Type 5 58
6-6 Keypunch Instructions for Card Type 7 59
6-7 Keypunch Instructions for Card Types 4, 6, and 8 60
7-1 Edit Error Messages 67
8-1 Update Error Messages 89
9-1 Retrieval Package Edits 146
9-2 Retrieval Package Error Messages 148
11-1 Region I's Enforcement Systems
Region I - Boston 184
11-2 Region II's Enforcement Systems
Region II - New York 185
11-3 Region Ill's Enforcement Systems
Region III - Philadelphia 136
11-4 Region IV's Enforcement Systems
Region IV - Atlanta 187
11-5 Region V's Enforcement- Systems
Region V - Chicago 133
11-6 Region VI's Enforcement Systems
Region VI - Dallas 189
11-7 Region VII's Enforcement Systems
Region VII - Kansas City 190
11-8 Region VIII's Enforcement Systems
Region VIII - Denver 191
XTM
-------
LIST OF TABLES (Cont. )
TABLE PAGE
11-9 Region IX's Enforcement Systems
Region IX - San Francisco 192
11-10 Region X's Enforcement Systems
Region X - Seattle 193
XIV
-------
1.0 INTRODUCTION
This Compliance Data System (CDS) User's Manual is designed to be the pri-
mary source of user documentation regarding CDS. It replaces previous docu-
mentationr which should be discarded.
This manual is organized to be used effectively by several groups of
potential readers:
Managers and others wishing a basic description of CDS should read
Sections 2, 3 and 4 (Management Overview, System Applications and
System Overview).
Current users who generally understand CDS will wish to skip to
specific sections of interest, particularly Sections 7, 9, 10, 11
and 13 (Edit Processing, Retrieval Processing, Supportive Techni-
cal Information, State Enforcement Systems and Headquarters Guid-
ance and Quality Control Measure) which reflect recent changes due
to changes at the National Computer Center, and available quality
control measures.
New users may wish to read the text in its entirety to obtain a
working knowledge of CDS.
Those preparing input data should read Section 6 (Data Input Pre-
paration) .
?rom time to time, .revisions to the User's Manual will be issued, ?. q. , =n
addendum for headquarters guidance revisions, new NCC articles, etc. It is
important that these revisions be entered and the old material discarded, as
the new sections will reflect major changes.
The authors of this manual wish to thank the National Data Bank Coordina-
tor (DBC) Franklin C. Smith, and other members of the Environmental Protection
Agency (EPA) and its regional offices who provided valuable assistance. Com-
ments and suggestions should be directed to Mr. Smith at 202-382-2833.
-1-
-------
2.0 MANAGEMENT OVERVIEW
The CDS was developed for the Stationary Source Compliance Division, by
TR.C Environmental Consultants, Inc. The primary purpose of CDS is to assist
EPA in carrying out its enforcement and surveillance programs.
CDS provides users with an effective tool for managing large quantities of
non-parametric stationary source information in an efficient and expeditious
manner. The system can store, update and retrieve large quantities of data
describing the compliance status and the enforcement activities ci: all ~ajci:
and many minor stationary sources of air pollution. Output reports t'rcrn the
system enable management to: 1) maintain a complete inventory of faeil ir. ic-3
emitting regulated pollutants; 2) assess enforcement strategies; 3) monitor
State and regional enforcement activities; and 4) measure compliance and en-
forcement progress.
2.1 Background History
CDS was developed by TRC for the Stationary Source Compliance Division in
1972 to assist EPA's regional offices in implemerttn*; "r'-eir ~ ' ---- - --
programs. The primary objective of EPA's stationary enforcement program is to
bring about compliance with Federal and State emission requirements as stated
by the State Implementation Plans (SIP), the New Source Psrf c-r.anci* ='-..?.:<'a :-':-
(MSPS) and the rational Emissions Standards for Hazardous Air Pollutants
(NESHAP). State agencies and EPA's regional offices have cc/ord indeed their
efforts to develop an enforcement management system which will encv.re C-JIP.C! :.-
ance with the emission limitations for all regulated pollutants.
CDS has been in operation for nearly 9 years. Experience with the system
has led to modifications and refinements of CDS which are described in detail
in this documentation. During the 7 years of regular production runs, CDS has
grown into a system widely used by all 10 regions and nearly half the States.
-2-
-------
2.2 System Purposes
Reqional offices are using CDS in a number of ways in their enforcement
programs. CDS is used primarily for the following reasons:
1. Provide an accurate and easily-accessible inventory of facilities
subject to Federal and State emission regulations and their com-
pliance status with respect to these regulations.
2. Develop enforcement strategies by providing summaries of the com-
pliance status of facilities tracked by CDS.
3. Provide a means for tracking numerous Federal, State and local
enforcement actions both for historical and future scheduling pur-
poses.
4. Assist the region in the preparation of various national reporting
requirements.
5. Provide various turnaround reports to be used by States in ful-
filling their reporting requirements to the region.
CDS is not designed to store large quantities of parametric emission data;
instead, it is a management information system for tracking compliance and
enforcement information in an easily-accessible manner. In effect, CDS is an
automated tickler file which provides both historical and current record-
keeping capabilities.
2.3 System Capabilities
CDS provides users with the capability to store, update and retrieve
information about all of the facilities placed on the CDS Masterfile. CDS is
used to record information on identified major polluters, provide information
about the compliance status of these facilities and help to track the enforce-
ment actions taken by regulatory agencies against these facilities.
Eight different punched card formats are used to enter data into CDS via
the Edit Program. On each of these card formats there are a number of data
elements nationally defined and controlled; there are also a number of data
-3-
-------
elements which can be defined according to each regional user's needs. Since
CDS can accomodate both types of data, it is a highly flexible system able to
meet both national and regional needs.
The Update Program uses each of the different input card formats to add,
change or delete information on the CDS Masterfile. Once data is placed on
the CDS Masterfile, the Retrieval Program can be used to create a wide variety
of management reports based on the data on the Masterfile.
The CDS retrieval capabilities are highly flexible. Users can obtain
reports based on all data on the CDS Masterfile or on only that portion of
data which meets user selection criteria. There are- four fixed-format repcr.s
as well as two flexible report formats which can be designed to fit any par-
ticular user requirements. Once a user has determined which report format
will fit his needs and has determined what portion of the Masterfile he wishes
to include on the report, he can specify the sorting criteria for his report.
Thus, the data can appear in any desired sequence. Because of this flexibil-
ity, CDS has been able to easily adapt to changing reporting requirements.
2.4 System Functions
A number of computer programs have been developed to input, update and
retrieve CDS data. These computer programs as well as all associated data
files are available at the EPA central computer facility. Currently, this
facility is operated by the" ffetional Computer Center (NCC). All regional
users have computer terminals connected via telephone lines to NCC computers.
Input transactions prepared by regional users can be transmitted at any
time to central computer facility. Once there, transactions are validated by
the Edit program. Valid transactions are stored for further use in the update
-4-
-------
cycle/ and an Edit Report showing the Edit's action on each input transaction
is returned to the user's terminal once the computer has .executed the Edit
Program. Under normal operating conditions, 1-hour turnaround is available
for the data submission procedure utilizing the CDS Edit.
Users may submit CDS input data via the Edit any number of times in
between runs of the Update Cycle. At the central computer site edited data is
stored for use by the Update. Under normal operating conditions, the Update
Cycle is scheduled by the national DBC to run once a week on Wednesday
nights. During periods of very high data entry activity, especially at the
find of each quarter, more frequent updates may be scheduled at the discretion
of the DBC. All valid transactions saved since the last Update are applied to
the CDS Masterfile.
The Update adds, changes or deletes data on the Masterfile based on each
transactions' Update Code. The Update produces an Update Report to show what
action it took on each transaction. After each update cycle for which the
user has input data, the DBC will run each region's Update Report as described
i. n Section 3 .
Once data has been applied to the CDS masterfile by the Update, users may
request management reports via the Retrieval. The Retrieval extracts, sorts
and prints data from the most current version of the CDS Masterfile. Requests
for retrievals may be made as often as necessary. Under normal operating con-
ditions, quick turnaround is available for short retrievals.
Regional users are responsible for data submission and retrieval re-
quests. The national DBC is responsible for scheduling update cycles and for
maintaining adequate backup and security for computer programs and files
stored at the central computer facility.
-5-
-------
2.5 System Relationship to Other EPA Systems
Although CDS has a coding structure compatible with a number of EPA sys-
tems and can accept input data prepared by related systems, it is basically an
independent management information system.
The inventory of facilities in CDS should correspond to the facilities
registered in the National Emission Data System (NEDS). NEDS contains the
parametric, relatively static emission data for sources of air pollution; CDS
contains the considerably more dynamic compliance and enforcement data for
facilities. CDS uses the NEDS facility numbering for a majority of its facil-
ities. In addition, the NEDS source number is carried as a retrievable data
element on all CDS facilities.
A number of State systems are compatible with CDS. Some of the States
using the Enforcement Management System (EMS) or a State version of CDS have a
converter program which reformats EMS data to meet CDS input specifications.
With the EMS-to-CDS Converter, compliance and enforcement information from a
f
State is placed directly into CDS with little data input preparation needed on
the part of the region. However, the region is still required to perform the
review functions necessary to verify the accuracy of the reported data.
-6-
-------
3.0 SYSTEM APPLICATIONS - What can CDS do for you?
CDS is a management information system designed to track large quantities
of dynamic compliance and enforcement information for stationary sources of
air pollution. With the flexible retrieval capability, CDS can produce
reports for a wide variety of users.
3.1 General Applications
A great deal of information must be readily available to those responsible
for conducting a successful enforcement program for stationary sources of air
pollution. Management must be able to:
1. Identify those sources of pollution which are affected by Federal,
State or local emission regulations. CDS provides an inventory of
these facilities and a fast retrieval capability for details about
them.
2. Develop" counts of various types of facilities which are in compli-
ance, out of compliance and of unknown compliance status with
State4 Federal and local regulations. CDS provides both milestone
(summary) reports and 'listings of facilities falling into the var-
ious compliance categories.
3. Monitor a wide variety of enforcement actions. CDS can track
enforcement actions scheduled into the future and can also provide
a historical record of actions scheduled or achieved in the past.
4. Prepare special reports. With the retrieval capability, CDS can
be used to prepare special reports based on standard industrial
class (SIC) codes, on NSPS or on any other criteria based on user
needs.
5. Coordinate with State and local enforcement programs. In some
States, enforcement and compliance information can be fed directly
from the State into CDS. In all States, CDS can provide highly
effective turnaround documents used by States for providing the
region with new or additional enforcement information.
5. Anticipate future enforcement requirements. CDS has a great deal
of built-in flexibility, and also is being constantly upgraded to
meet current and anticipated user requirements.
-7-
-------
3.2 Examples of Specific Applications
Once a regional user has an accurate inventory of his region's facilities
registered on the CDS Masterfile, he can obtain a wide variety of management
reports. The following is a partial list of some specific user needs met by
CDS:
CDS can produce a milestone report showing the number of major
facilities determined to be in compliance with SIP standards or
scheduled increments of progress by State, or other geographic
breakdown.
CDS can produce lists of all major sources of air pollution.
Listings can be broken down by a wide variety of criteria such as
major/minor, compliance status code, attainment/non-attainment,
Federal/non-Federal, etc. Subtotals and totals can be developed
on any user-selected criteria.
CDS can identify sources scheduled to be or inspected by regional
and/or State personnel in both attainment and non-attainment Air
Quality Control Regions (AQCR's).
« CDS can list the enforcement actions taken, or about to be taken,
by EPA to ensure compliance in both attainment and non-attainment
AQCR's.
CDS can be used to track a large number of actions, such as formal
inquiries (114 letters), field surveillances, notices of violation
abatement orders, etc. Once a reaion has determined what ac-iors
it wishes to track in CDS, CDS can provide users with a history .:>!'
past actions and also a schedule of actions to be performed.
CDS can be used to prepare milestone reports and lists of facili-
ties subject to SIP, NSPS, NESHAP and PSD regulations.
CDS can be used to prepare industry studies or summaries based on
the SIC or on the Source Classification Code (SCC) for certain
processes.
The types of reports that CDS can generate in aiding management in its
enforcement activities are virtually limitless. Once a user has determined
what his information needs are, he can use a large number of both fixed format
and user-defined data elements as input to the system. After the data has
been placed on the CDS Masterfile, the user can select, sort and format the
data on the Masterfile according to his needs.
-8-
-------
In one retrieval, sources can be selected by State, AQCR, city and/or
county, industrial category, emission size, pollutant, SIP regulation number,
Federal or non-Federal facility, compliance status or any combination of
retrievable data elements. The user, by matching the selection criteria which
he has chosen, could get a Source Data Report which provides all data stored
in the system. This might include compliance information with respect to all
applicable SIP regulations for all emission points within the facility. Or,
since such an extensive report is seldom needed by program managers except
perhaps for special studies, he could request a Quick Look Report to obtain a
concise listing of sources displaying only a few pieces of needed informa-
tion. For example, if he needs to have a list of major sources of air pollu-
tion within a particular State or AQCR, he could get a Quick Look Report which
displays each of these facilities and information he wants to know such as
name, location or compliance status on a single line. The program manager can
quickly scan the list to obtain his desired information.
The process of obtaining compliance information is long and tedious. The
number of point source facilities in a State may range from as few as 10 to
over 1000. Data is subject to constant change. With the help of CDS, the
initial data base can be established and future processing will be simplified
since needed reports can be generated quickly, and since only new or changed
information need be entered or updated.
Inspections, legal actions, monitoring of compliance schedule progress and
other agency actions are reported to regional offices by the .State. These
actions are entered into the CDS data base and may be summarized by State,
AQCR or any other basis for review by regional management. In addition,
compliance schedules may be entered into the data base in their entirety,
including events which are scheduled for the future. CDS can print out a
-9-
-------
Quick Look Report for the State giving the current status of compliance and
Listing actions scheduled to occur during a reporting period. The report can
be formatted as a means for State reporting on the schedule status or as a
means of monitoring of State scheduled enforcement.
Besides monitoring State progress in assuring that sources meet schedules,
CDS can be used to review State inspection programs for sources already in
compliance. Reporting can be accomplished in the same way as reporting on
compliance schedules. If, for example, a State is committed to inspecting
major facilities at least once a year, the regional office can periodically
send the State a CDS listing of those facilities scheduled for inspection.
The State would indicate on the printout whether or not the inspection
actually was conducted. Reporting on source tests and other actions can be
handled in the same manner.
CDS can also print out a special list of facilities of unknown compliance
status. A State can be sent a printout for further information on the listed
sources. If the State does not provide the information in the requested
r°oortinq time, EPA can use the same list to initiate a field inspection pro-
gram to resolve the compliance status.
CDS can be used to follow-up on sources out of compliance. It can provide
a printout of the problem facilities that can. be assigned a priority ranking
for future actions. When an order is issued by EPA, a State or a court, the
CDS tracking system can be used for monitoring the facility to ensure that
required steps in the order are achieved.
By entering all enforcement action and scheduled field activities, CDS
becomes a tool that can assist personnel at all levels of environmental regu-
latory enforcement. Project managers can determine the workload facing their
staff during a coming month by obtaining a CDS report on all EPA actions
-10-
-------
scheduled during the month. Inspectors can be provided with reports of the
date and results of the last inspection of all sources in their assigned
area. Another useful report is a complete date sequenced list of scheduled
source tests, facility start-ups, control equipment installations and
inspections. Some jurisdictions use CDS printouts as turnaround documents,
eliminating the need for special reporting forms.
-11-
-------
4.0 SYSTEM
The CDS provides regional users with the ability to store, update and
retrieve large quantities of data necessary for running an enforcement pro-
gram. To meet these objectives, CDS has been desiqned to perform three
distinct functions: edits, updates and retrievals.
Regional users are responsible for preparing data for CDS in order to
maintain an up to date Masterfile. Data preparation involves both coding of
information and the preparation of turnaround documents which can be used by
State and local enforcement agencies. Once input data has been updated,
regional users are responsible for the preparation of all retrieval requests
from the system.
National Headquarters responsibilities include:
Producing guidance to insure consistent national understanding and
approach to Stationary Source Air Program information requirements.
Developing and maintaining all CDS programs, data sets and table
values.
Scheduling all update cycles.
» Providing definition and usaqe of all nationally controlled data
elements.
Establishing retrieval guidelines for meeting national reporting
requirements.
Providing user training for any region or State requesting train-
ing.
Responding to regional requests for system modifications.
Coordinating State data input procedures, especially with the EMS-
to-CDS Converter.
The following paragraphs describe the edit, update and retrieval
functions; subsequent sections of this manual will describe in detail the
operational usage of the computer programs which perform these functions.
-12-
-------
4.1 Edit Program
Stationary source data is initially processed for the Masterfile by the
CDS Edit Program. Regional users gather data concerning stationary sources of
air pollution and then prepare this data in a format acceptable to the Edit
Program. There are eight fixed card formats available to the user for prepar-
ing data as input transactions to the Edit Program. Whenever the user has a
sufficient amount of data to be submitted, he initiates the Edit Program by
submitting the keypunched input transactions together with the appropriate Job
Control Language (JCL) to his region's computer terminal.
The Edit Program examines every input transaction prepared for the system
and produces an Edit Report for each Edit Program that is run. If an input
transaction has no edit error messages next to it on the Edit Report, it is a
valid transaction. Transactions in error will have one or more edit error
messages next to it on the Edit Report. Errors are identified as either
"Warning" or "Fatal".
The Edit Program stores all valid transactions on a MOD File until the
next scheduled Update Program. Cne or more fatal errors will prevent a trans-
action from being saved for the Update Program. A transaction with only warn-
ing errors will be saved for the weekly update, but the data elements in error
are blanked out.
The Edit Program can be run as often as necessary in between update
cycles. Each time the Edit is run, an Edit Report is immediately produced and
sent to regional users for review.
4.1.1 Input Data Processed by CDS
Data is input to the Edit Program on punched cards or 80-character card
images on tape or disk. There are eight fixed card formats, described in
-13-
-------
detail in Section 6, that are validated by the Edit Program. These cards pro-
vide the following general information:
Cards 1 and 2 provide facility (source) level data for this system.
Card 3 provides pollutant compliance data for the facility.
Card 4 is a facility comment record which provides additional in-
formation about the source.
Card 5 provides descriptive emission point data for various
pollutants.
Card 6 is a point comment record which provides additional infor-
mation for a given emission point.
Card 7 describes specific enforcement actions for a given emission
point.
Card 8 is an action record which provides additional information
for an action record.
4.1.2 Edits Performed by CDS
The CDS Edit Program examines and validates all input transactions pro-
cessed on the eight fixed card formats. Errors are classified as either
"Warning" or "Fatal" and will appear on the right side of the Edit Report next
to the transaction containing the error. Warning errors will have one aster-
isk preceding the error message; for example, *IWALID POLLUTAOT CODE. Fatal
errors will have three asterisks preceding the error message; for example,
**.*IWALID STATE CODE. The data element in error will have asterisks directly
beneath it on the Edit Report printout line. A transaction with multiple
errors will have multiple error messages.
If an input transaction has no edit error messages next to it on the Edit
Report, it is a valid transaction and will be stored on the MOD File for
processing in the next update cycle. One or more fatal errors next to a
transaction will cause the transaction to be rejected by the Edit Program.
-14-
-------
Consequently, a transaction with one or more fatal errors will not be stored
on the MOD File for processing by the update cycle. A transaction with only
warning errors will be acceptable and stored on the MOD File, but the data
elements in error will be blanked out.
Each card type has its own validation procedure within the Edit Program.
Certain data elements, such as County Code, AQCR, Action Type, Results Code
and Personnel Code are validated by external table look-up procedures. 'To
make a new code valid for any of these data elements, the national DEC must
update the appropriate table so that it will contain the new value. Other
data elements, such as Region, State, Compliance Status, Emission Cataacry,
etc., are validated by internal computer tables. These edits can be chanqed
only by changing the Edit Program logic. Only the national DEC has the
authority to change these edits.
Although the Edit examines all input transactions for possible keypunching
and coding errors, the program has its limitations. The Edit cannot detect
valid but incorrect Update Codes; only the Update Program can determine
whether it is possible to add, change or delete a record on the CDS Master-
file. The Edit cannot detect certain errors caused by punching data into the
wrong card columns; if a valid date is placed in the Date Scheduled columns,
the Edit will accept the data element as valid. Even those transactions con-
taining no Edit errors should be examined by new users to make sure that they
are preparing data for the system properly.
Figure 4-1 is a flow chart of the Edit Program. Input to the Edit con-
sists of the various input card formats together with the appropriate JCL
needed to run the program. During the program a number of external table
files are used for validating changeable data elements, such as Action Type.
These are four outputs from the program:
-15-
-------
INFORMATION
FROM FEDERAL,
STATE & LOCAL
AGENCIES
\CODING AND
\ KEY-
PUNCHING
x_
V
7
INPUT DATA
CARD TYPES
1-8
EDIT
PROGRAM
ALL TABLES ARE
MAINTAINED 3" THE
NATIONAL DEC
CDS /
PERSONNEL !
"ABLE
\
CDS
ISAM
TABLE
CODE/AQCR
TABLE
i
\
/ N
/
rEDIT 1 | MOD (
LOG \ \ FILE I
\
/
EDIT
REPORT
^
\
/
r" /
/ ERRORS |
1 (DUMMY) 1
TO
NATIONAL
DEC
TO
UPDATE
CYCLE
TO
REGIONAL
USER
CAN 3E
PRINTED
OR SAVED
BY USER
Figure 4-1. Edit Program Flow Chart
-16-
-------
1. The Edit Report.
2. The MOD File containing all valid input transactions. With each
run of the Edit, additional valid transactions are stored here
until the update cycle applies these transactions to the Master-
file.
3. An Edit Loq showing statistics, such as cards input, cards
accepted and cards rejected. These numbers are printed at the end
of the Edit Report.
4. An optional Error File containinq all records with fatal errors.
This file may be placed on a WYLBUR data set for correction by
those users familiar with WYLBUR usage.
4.1.3 Edit Error Messages
The Edit Program identifies the two kinds of errors, warning and fatal,
made on the eight fixed card formats submitted as input data transactions. An
error message describing the cause of the error will appear on the right hand
side of the Edit Report preceded by one or three asterisks as explained in
Section 4.1.2. Typical error messages are listed below:
FATAL WARNING
***INVALID STATE CODE *SIC CODE SHOULD BE NUMERIC
''"LINE MfJMBER MUST 3E NUMERIC *INVALID SI? CODE
***DO NOT DELETE 000 *INVALID POLLUTAOT CODE
Valid values which can be entered on the card formats for each data ele-
ment are listed in Appendix A. Each Data Element Sheet lists the appropriate
coding values and coding considerations necessary for preparing card formats
and for making corrections.
4.1.4 CDS MOD File
The CDS MOD File resides on a disk storage device. Input transactions
validated by the Edit Program are saved on this file for use by the weekly
update cycle. At the end of the update cycle, the data on the MOD File is
-17-
-------
erased to make room for input transactions for the next update cycle. As Edit
Programs are run by the numerous regional users, transactions with non-fatal
errors are added to this file. Any number of data submissions may be made to
the Edit in between one update cycle and the next. Each submission adds addi-
tional data to the MOD File. At the beginning of the next update cycle, the
data on the MOD File is copied to magnetic tapes. Then the transactions on
the file are sorted into Region, State, County, Source, Point and Action Num-
ber order, within this major sort key, transactions are also sorted by Update
Code and by chronological order. Transactions with the same record ID and the
same Update Code are applied chronologically.
In the past, only the last input submission via the Preliminary Edit would
reach the Update since each input submission overlaid the previous input sub-
mission. With the MOD File, input transactions do not overlay previous sub-
missions; instead, input transactions are added to the file and are saved
until the update cycle.
Once a transaction has been added to the MOD File, it is no longer neces-
sary to resubmit the transaction again when additional transactions are being
submitted £or the same update cycle. However, the user should keep inpuc
transactions on cards or other information storage devices for at least 1
month for security and backup purposes.
4.2 Update Program
The CDS Masterfile is updated once a week by the Update Program. All
transactions stored on the MOD File by the various runs of the Edit Program
are processed by the Update Program. This is usually scheduled to run once a
week on Wednesday nights by the national DEC. Input to the Update is the old
(preceding week's) Masterfile and the week's input transactions placed on the
-18-
-------
MOD File by the Edit Proqram from all regional users. Output from the Update
is an updated Masterfile, 10 regional Update Reports and the Critical Data
Element Report.
Once the update cycle is complete, each regional user who had input data
for the Update Program must request his regional Update Report. This report
shows what action the Update Program took on each transaction passed to it by
the various Edit runs. Whenever the Update Program cannot process the add,
change or delete transaction specified by the user, a reject message will
explain why the transaction was not applied to the Masterfile.
4.2.1 Update Actions to CDS
Card types 1 through 8 processed by the Edit Program are used to add,
change or delete information on the CDS Masterfile. The Masterfile contains
records which correspond to the input card types. Input transactions perform
the following functions:
t
NEW When an Update Code "N" is used in the Update Code Column,
the input transaction will add a new facility, point, action
ii' ~ :>rn:ri-?nt rucoro no the CDS Masterfile.
CHANGE The Update Code "C" is used to change one or more data ele-
ments on an existing Masterfile record.
DELETE The Update Code "D" is used to delete one or more Masterfile
records for a given facility.
4.2.2 Update Cycle Steps
In addition to applying input transaction to the CDS Masterfile, a number
of other steps are taken in each update cycle:
Input transactions from the MOD File are saved on tape.
9 Input transactions are sorted into the same sequence as the
Masterfile.
-19-
-------
A number of table lookups are performed during the Update.
The CDS Masterfile is copied to regional and State disk
Masterfiles.
The MOD File transactions are erased to make room for the next
cycle's input transactions.
Figure 4-2 shows this process.
4.2.3 Update Report Messages
On the Update Report there are several column headings which indicate what
action has been taken by the Update Program on each transaction passed by the
Edit. A normal Update Action Message is ADDED, CHANGED or DELETED and indi-
cated a successful Update Action. The word REJECT in the Update Action column
indicates that the Update Program could not perform the appropriate add,
change or delete as indicated in the Update Code column. For each rejected
transaction, there is a diagnostic error message printed out under the Error
Message column.
Typical Update Error Messages are listed here.
* SOURCE NOT ON FILE
» POINT NOT ON FILE
DUPLICATE TRANS
ALREADY ON MASTERFILE
When an ampersand appears in the Error Message column, it indicates that
multiple changes have been applied to the Masterfile in chronological order.
A complete listing of Update Error Messages and their causes is given in
Section 8.
A column marked "ORIG" indicates the origin of the input transaction. The
following values are used:
-20-
-------
THIS
CYCLE'S
OUTPUT
MASTZRFTLE
BECOMES
NEXT
10 REGIONAL
DISK
IMASTERFILES
/ /
'10 REG TONAL? [
!:?D..T" '
Figure 4-2. Update Flow Chart
-21-
-------
ORIG
Blank Regional Input
HQ Headquarters
GN System generated
SC, TN, NE, etc. For those States who have direct
access to CDS, the State code is
displayed to indicate the State
entering the data.
TR TRC Environmental Consultants, Inc.
GE GEOMET Technologies
4.2.4 The CDS Masterfile
The CDS Masterfile resides on magnetic tape. It contains data for sta-
tionary sources of air pollution for each of the 10 EPA regions using CDS.
Over 50,000 facilities exist on the Masterfile. For each facility there are a
number of Masterfile records containing facility, emission, point, action and
comment information. Data from each tyoe is placed on one of seven Masterfile
record formats. These Masterfile record formats are numbered 20, 21, 30, 34,
46 and 47 for internal computer identification purposes. The seven Masterfile
record formats contain the following general information:
1. Record 20 contains facility level data from Cards 1 and 2. E..--.T.
facility has one Record 20. Region, State, County, and source
numbers identify a unique facility.
2. Record 21 contains comment information for the facility record.
Up to 10 comments may be used for each facility. Each Card 4
added to the Masterfile creates a corresponding Record 21.
3. Record 30 is the pollutant compliance record. One of these
records is present whenever Card 3 input is submitted to CDS.
Data for up to 10 pollutants can be placed on this record.
4. Record 34 is an emission point record created from the Card 5
input transaction. For a given facility there may be up to 1000
emission points; each is identified by a sequential Emission Point
Number. Emission Point 000 contains compliance data for the
entire facility. The use of this special point is described in
more detail in Section 3.
5. Record 35 contains comment information for an emission point.
Each emission point may have up to 10 comments. Each Card 6 added
to the Masterfile creates a corresponding Record 35.
-22-
-------
6. Record 46 is an action record created from the Card 7. For a
qiven emission point there may be up to 98 actions; each is iden-
tified by a sequential Action Number.
7. Record 47 contains comment information for an action record. Each
action may have up to 10 comments. Each Card 8 added to the
Masterfile creates a corresponding Record 47.
Figure 4-3 shows the hierarchical relationship between the various Master-
file record types.
4.2.5 Regional CDS Masterfile
In one of the last steps of the Update Program, the update CDS Masterfile
L.-i cooiad to create separate regional Masterfiles and several State
Ma :;terf lies, each of which resides on a disk storage device. Each of these
files contains the most current version of the CDS Masterfile for only one
r^'-jion or State. All retrieval requests are based on the data contained on
the individual Masterfiles.
4.3 Retrieval Program
".-_ 'I'^/.i Retrieval Program is used to prepare management reports bases on
the CDS Masterfile and was designed to meet the specific requests of regional
users. All output reports,, other than the Edit Report and the Update Report,
.are .v/.-jilaole on request from the Retrieval Program. These requests may be
made at any time since they are processed independently of the Update Pro-
gram. The Retrieval Program will produce the following management reports:
Source Data
Action Summary
Questionnaire
Milestone
Qu ick Look
Double Spaced Quick Look
Compliance Action
-23-
-------
*ci Ions [or
l>olne Pllfl r«fjr
to ati Icn for Ilii
R-uorJ «6
ACT lull
Huco
AC I
»'
Uu to 10 Couai<:iU0
ftr Source
Up to 1001) pulnlo
per facility
il
ACT(UN
ClUL'lENT
itcCOl'J ^/
ACTION
COMMENT u PJ
Figure -}- , Masteifile llicr.irdiy
-------
4.3.1 Description of Reports Available from Retrieval Program
The retrieval capabilities of CDS are designed for maximum flexibility so
that the user may design the output format to fit his own particular need. In
addition, the amount of information retrieved for each source is also deter-
mined by the user to meet his needs. This section briefly describes the prin-
cipal reports which Region Management can request from CDS. Complete details
regarding content of the reports and the means to obtain them can be found in
Section 9.
Quick Look Report
The Quick Look Report is designed to print only some data elements
for selected sources. This report is the most widely used of the
seven report formats available. Although all the data for a
selected source is valuable, report requirements can often be met
with a short report which shows only a few user-selected data ele-
ments. For example, management may need a report showing only the
name, address and compliance status of all major facilities within
a State. With the Quick Look Report, a user can easily format a
report which contains only name, address and compliance status.
Jtot only can users select via the Retrieval's selection logic what
facilities should appear on a report, but can also select the data
elements to be printed for these sources. Up to 14 specified
source, point and action data elements for a facility may be in-
cluded on a single print line so long as this print occupies 132
or fewer print positions.
Because of its flexibility and versatility, the Quick Look Report
is the most commonly used CDS report format. It enables the user
to see only those data elements which he needs to deal with a par-
ticular problem. The Quick Look Report can be used as a forecast
report, a turnaround document.
Source Data Report
The Source Data Report is a complete listing of all data in the
system regarding a specific facility. The report includes all
facility, point and action data for those facilities selected in
the retrieval. In addition, comments at any of the three levels
(facility, point or action) are printed on the report. The Source
Data Report can be sequenced in any user-specified order such as
Source Name, State, City, etc.
-25-
-------
Action Summary Report
The Action Summary Report provides two lines of printed data about
specific actions for which the user requires information. This
report summarizes action data recorded on the Masterfile by Action
Type. Tire user may vary the kind and amount of information
printed on the report by his choice of selected criteria. For
example, actions to be included on the report can be varied by
dates. If a 6-month period is selected, the actions summarized on
the report will include only those which were scheduled durinq
that period. The Action Summary Report can also be used as a
turnaround document which can be sent to a State, filled in by the
State and then returned to the reqional office.
Questionnaire Reports
The Questionnaire Report was designed for reqional offices to be
used as a turnaround document. Its primary use is to show the
status of various actions which are expected to be performed by a
State within a specified period. Identifying data is printed on
the Questionnaire which is then sent to the State agency for com-
pletion. After the State returns the filled-in report, the data
can be keypunched for re-entry into CDS to update the Masterfile.
Milestone Report
The Milestone Report is a statistical report which enables regions
to evaluate the progress and effectiveness of State enforcement
programs. The Standard Milestone provides a tally of the compli-
ance status codes for each State, within a region based on the
selection criteria specified on the input cards. This report can
be used in conjunction with the Quick Look Report to substantiate
the numbers on the Milestone Report. In this manner, the Mile-
stone Reports provide reqional managers with a means to sie»t
national reporting requirements. The variable Milestone provides
a tally of any two user-specified data elements in the system.
For example, a count of all SIC descriptions by AQCR, and a count
of sources within a county by major and minor emission categor-
ies. The Milestone can provide each of these totals for the user.
Compliance Action Report
The Compliance Action Report summarizes the compliance status and
enforcement actions for selected facilities on the CDS Master-
file. Source level information and compliance information is
listed on one print line with the date achieved for the following
actions:
Inspections
Notices of Violation
Orders Issued
Court Actions
Terminations of
-26-
-------
Because this report has been designed to meet specific enforcement
action reporting requirements, all reportable totals are generated
at the end of the report.
4.3.2 Retrieval Steps
Each time a user requests a management report via the Retrieval, the
following steps are taken by the various computer programs constituting the
Retrieval:
Retrieval selection cards are checked for validity. An Edit
Report page is printed to show the logic used in preparing the
Retrieval.
CDS regional Masterfile records which satisfy all of the user's
selection criteria are placed on a temporary extract file.
Extracted records are sorted into a user-specified sort order.
Sorted records are formatted for printing into user-specified
print formats.
Figure 4-4 shows this process.
-27-
-------
1
f REGIONAL /
CDS 1
MASTZRFILE \
\
' 4?^
RETRIEVAL
PROGRAM
V v
rtg /
f01 USER J
SELECTION /
1 CARDS /
^
f \/
: RETRIEVAL f / EXTRACT / / RETRIEVAL /
LOG 1 1 FILE 1 EDIT
\ \ \ \ REPORT \
\
f
SORT
PROGRAM
\
f -
(SORTED /
EXTRACT
mi \
\
/
PROGRAM
\
/
I
RETRIEVAL
OUTPUT
REPORJS. Y
f
'
/
Figure 4-4. Retrieval Flow Chart
-28-
-------
5.0 DATA SUB MISS ION PROCEDURES
5.1 Submission Steps
The following 10 steps describe the procedures for using the CDS. These
steps outline in chronological order a general summary of how CDS should be
used by regions. A detailed description of each step is provided in Sections
6, 7, 8 and 9.
1. Prepare Data. Fill out the appropriate coding sheets as described
in Section 6. Have the coding sheets keypunched.
2. Run the Edit Program. After the CDS punch cards have been
returned, prepare the appropriate JCL cards for running the Edit
Program. The JCL for running the Edit Program is shown in
Figure 7-2. Submit the JCL and input punch cards to the com-
puter. Submissions should be made on a priority basis since the
Edit is inexpensive to run (approximately S4.00 per 1000 cards
with PRIORITY=4) . With a priority, the Edit will run prior to the
update cycle, and thus the input data will be applied to the cur-
rent week's update cycle.
Since multiple runs of the Edit Program can be made in between
update runs, experience indicates that it is best to submit data
in several smaller batches during the week as soon as data is
returned from keypunching.
3. Examine Edit Report. When the Edit Program is completed, the user
must examine the Edit Report to determine if there were any edit
= rror3 on cne input data. AIL transact ions submi t--3d to c.ifi '.-:6 .-.
are listed on the Edit Report; transactions which are error-Eras
have no error messages printed on the right hand column labeled
"Error Messages". The format of the Edit Report is given in
Figure 7-1. It should be noted that the County Name generated by
the Edit appears directly beneath the County Code for error-free
Card 1 transactions with an Update Code "N".
The Edit Program identifies two types of errors, "Warning" and
"Fatal". Warning errors are identified on the report by an error
message preceded by a single asterisk (such as "*INVALID STAFF
CODE"). The Edit will blank out the data element in error but the
transaction will be passed to the output MOD File for processing
in the Update cycle. One warning message is issued for each data
element containing a non-fatal error.
Fatal errors are identified on the report by an error message pre-
ceded by three asterisks (such as "***INCORRECT COUOTY CODE FOR
STATE"). One or more fatal errors on a transaction will prevent
that transaction from being placed on the MOD File and, conse-
quently, the transaction will not reach the update cycle.
-29-
-------
Table 7-1 gives a complete list of all errors identified by the
Ed it Program.
For both warning and fatal errors, asterisks are placed directly
underneath the data element found to be in error. These asterisks
are designed to identify the data element which needs to be cor-
rected.
4. Correct Edit Errors. Once edit errors have been located on the
Edit Report, they must be corrected and resubmitted in another run
of the Edit Program. All errors should be coded, keypunched and
submitted to CDS by repeating steps 1, 2 and 3 described above.
Keep in mind that all valid data from the previous run of the Edit
Program is saved on the CDS MOD File. Once valid data has been
accepted by the Edit, the data does not have to be resubmitted
again. Only corrections and data not yet submitted to the Edit
should be entered after steps 1, 2 and 3 have been performed.
5. The Update Cycle. All valid transactions submitted by the Edit in
between update cycles are stored on the MOD File. Or.ce a week,
usually on Wednesday night around midnight, the valid transactions
on the MOD File are applied to the CDS Masterfile by the Update
Program. Because of this schedule, it is important for users cc
have all of their weekly input ready on or before Wednesday noon.
The scheduling and the maintenance of the update cycle is en-
responsibility of the national DBC. Under unusual circumstances,
the update cycle may be run more often than once a wee*. '.vhen
holidays prevent a Wednesday night update cycle or when a special
update cycle is scheduled, the national DBC will inform all CCc
users of the schedule change.
6. Verify Up'date Run. The national DBC will route a copy of th=!
Update Report to the user's terminal, by noon on Thurstiav . ,: ".....
user has not received his report by noon, he should verity thac
the update cycle has run successfully and that the Update Report
is available for this Reqion. Figure 8-3 shows the data set
retrievable via NCC under the name CN.EPAEXC.A026.CDS.SYSOUT.
This data set shows the date, time and output serial number of the
most recent update cycle. It shows which reqions part icioac.c?c".
the update and also the number of transactions input to the update
and number of transactions accepted and rejected by the update for
each region.
7. Examine Update Report. The Update Report has one print Line for
each transaction sent to the Update Program by the Edit Pcoqram.
Next to each transaction on the report there is an Update Action
which shows that the transaction was either added, changed,
deleted or rejected from the CDS Masterfile. If the transaction
was rejected, there will also be an error message explaining why
the transaction could not be added, changed or deleted. See
Figure 8-2 for a sample Update Report.
-30-
-------
8. Correct and Resubmit Update Errors. Transactions passing all of
the validation routines of the Edit Program may still be rejected
by the Update Program. The Update rejects all logic errors caused
by an incorrect Update Code on the transaction; for example, the
Update cannot apply a change transaction to a record which does
not exist on the Masterfile. Table 8-1 shows the Update Error
Messages generated by the Update.
All errors appearing on the Update Report must be researched and
receded. Corrections should be resubmitted to CDS via the Edit
Program.
9. Request Management Reports. CDS can produce the following manage-
ment reports:
Qu ick Look
Milestone
Source Data
Questionna ire
Action Summary
Compliance Action
The user should consult Section 9 for the procedures to obtain the above
reports.
-31-
-------
6.0 DATA INPUT PREPARATION
6.1 General
All input data to the CDS must be prepared in the format of one of the
eight card layouts shown in Figure 6-1. These are the only formats that the
system will accept. The data may be punched onto actual 80-column cards or
prepared through special techniques such as WYLBUR or the EMS-to-CDS Converter.
Each card must have columns 1-19 (Region, State, County, Source, Point,
Action Number, Card Code) and column 80 (Update Code) punched. The followina
data elements are unique for each card code:
Ca rd Cod e I
*AQCR
City Code
"Facility Name
Street Address
Regional Data Element 1
Regional Data Element 2
Regional Data Element 3
Regional Data Element 4
Regional Deta Element 5
Card Code 2
Zip Code
State Registration Number
*NEDS Cross Reference
*SIC Code
Federal Facility Code
*Air Program Code
Air Program Status
Regional Data Element 6
Staff Personnel Code
Card Code 3
Pollutant ID
Delete Flag
Pollutant Compliance
Pollutant Emission Category
Pollutant Air Quality Control Indicator
Pollutant Loading
Facility Capacity
Card Column
20-22
23-26
27-46
47-56
67
68
69
70-74
75-79
Card Column
35-39
40-54
55-53
59-62
64
6 i;
66
67-76
.77-79
Card Column
22, 34, 46
24, 36, 48
25, 37, 49
26, 38, 50
28, 40, 52
29-33; 41-45;
53-57
58-64
-32-
-------
MULTIPIE-CARD LAYOUT FORM
A,,(,iKu,io.> _C»S INPUT LAYOUT
TIU:
ai. MARCH TJtil Job No
Sh««l No.
jFl
2
PI
"5
<
CJ
f*'
p
p
to
f)
o
(---
O
or.
*'
-j
j j
o
c
0
r-
01
01
p<
1 2
(.
C
r
t
0
CX
1 I
B
o
H
M)
1 2
c
T
It.
0
PC
\ I
(-
c
n
bl
01
«
1 2
r:
o
H
w
OJ
(X
1 2
01
U
n)
u
CO
1 4
01
4J
IJ
CO
) 4
01
t-l
n)
01
u
ro
u
CO
1 4
01
(-1
n)
U
CO
01
4.1
m
11
0-3
3 4
f^
9
o
o
Silt
^
JJ
§
o
o
till
f^
u
c
o
IJ1
£J
o
o
5 < 1 1
^\
M
g
0
o
i'.
11
(1
O
u
i 6 1 1
01
O
14
0
CO
9' 10 II 12 11
01
o
o
co
t 10 II II 11
01
o
IH
n
C
CO
01
o
3
o
CO
9 10 II 12 11
01
o
rH
O
co
01
0
3
o
M
9 10 II 12 11
4-1
O
PH
14 li 16
4-1
3
O
PH
14 li 16
4-1
.^
C
PH
14 li 16
4-1
rl
O
|li
14 li 16
t-l
O
14 1 1
IJ
.5
o
PH
14 li U
^tt-
C
o
H
4-1
(J
-<
11 1
"c
o
rl
11
O
-a
u u
o
H
1-1
C
II Ib
O
rl
U
(J
-3j
II Ib
O
-H
IJ
(J
<
1 u
:;;
CJ
O
U
U
-ll
1 ll
II
a
o
u
a
H
01
J
19
U
a
o
o
a
d
.3
1!
0)
a
o
o
o
H
U
o
o
o
a
a
j
li
a
o
j
-i
nl
J
'r
o
O
c.
n
1
U!
'J
8
o-
.'0 21
2!
P
I
r
> 01
J T3
4
O
U O
23 24
2i
:t
Source N.nne
?l 29 29 10 11 12 11 M li 1« 11 It 19 40 41 42 41 44 4i J
01
City Name ,0
20 21 2> 11 24
&
rH
11
MH
rQ 2)
n
o
p.
rl
26 21 21 » W 11 12 M 14 u to 11 11 19
u Pollutant 1 *
c
n)
u
3
rH
iH
C
PH
2 71
sec
Nil
22
P
O
r-
Cl
21 24
§
4
IH
tLAT
i.
oLai u
-jir; oo u
co G n)
<< ^^ H
«P Tj *H
's 331
3. c^ A^ *-* 'T'
^ ^fl ft W 11 )? )J
du
2i
r^ ^ ^ ( i
^* J J) PH
» Jl 28 29 10 II 12 11
Street Address
k> 41 4<
49 iO
il i2 il M
State Registration
Number
10 41 42 » 44 45 46 41 41 49 M
M 'ollutant 2 n
C HHl«
1) CO <£
" 21 j:
0 ° del
1-1 P H rH -
° b j -i -
P. ^ PL, IH 1
M JL ib ll 4 1!
ig °
J D- a «
:< -ri o
T3 -H
^ -* W (TJ *O
1 -4 rH O C
U) II 42 43 44 4i
il S2 13 W
*j Pollutant
ra
4J
3
li
rSt
Fu> eral/State/Local
Uej;ulation Number
H K k 37 11 39 40 41 42 43 U 4i
Optional
Short Action
Fil ler
Rescript on
D 21
Q
('
'0 (1 22
41
21 24 2i
Comnu;
K 41 4t
-H
/I
r
£
49
fr-
C_
49
J
^
oc
< <
Ht-
E p
il .2
3
c
ii i6 il 58 i9 60 61 62 61 64 ii 6t
rt
o
^
.5 J« SI ii
3 VH
O
CO U
C ra
H CJ
O -rl
^ 4-1 ra TJ
j i-i o c
H PH ,J M
1 i4 »A ^ m
O
H
if
1
1 19 60 61 62
H
rH
H
U
O P.
cu nj
CM O
1 i9 60 bl b2
1
0
r-
J^
bl
61
,-)
M
O
<
i
W
u.
it
64
P
<
>i
t-
P
<
*
H
jj
«
61
W
2
68
1
13.
3
69
RDE 4
m ii 12 n i
RDE 5
ii it n 11 it
RDE 6 »>
rM
i! i
a 19 60 61 62 61 64 6i ii il U S9 10 II 12 1) 1
Date
Achiev-
ed
"
ii it il in i9 bll
Date
Sched-
uled
ijl 62 6) M £!i
bl 62
CC
<4-4
"4-1
n)
U
CO
il 64 63
61 b4 6i 66 il
u
U)
4-1
rH 00
01 M
01 O
W PH
10 ii 12 r i
rH ^1
W ^ 2i C
& 2 0V
1 li 'S 11 II 7!
iJ LJ Wl^
S 2 ^y^
2 R 2f-
4 IS li 71 llll!
Filler
1 IS 16 11 11 I
69 10 11 12 11 14 li 16 11 II I
01
4-1
ra
u
W
01
CO
o
p
J3
w
01
4-1
n)
T3
5
to
01
cd
TJ
H
01
U
(0
o
p
U3
BO
01
u
nl
T3
S
80
Figure 6 i. Multiple-Card Layout Form
-------
Card Code 3 (Continued) Card Column
Regional Data Element 9 65-71
Regional Data Element 10 72-73
Regional Data Element 11 74-75
Regional Data Element 12 76
*Class Code 77-78
*Loading Derivation Code 79
Card Code 4 Card Column
*Comment Line Mimber 20
Source Comments 21-79
Card Code 4 (Used for Mailing Label) Card Column
*Comment Line Number (A)
Managers' Name 21-40
'Comment Line Number i3)
Street Name 21-40
C i ty Na me 42-56
State Abbreviation 58-59
2ip Code 61-65
Card Code 5 Card Column
SCC Code 20-27
Capacity Code 23-29
Compliance Status 30
*SIP Code 31
'Pollutant 32-33
State Regulation Mimber 34-43
*Emission Category ?
rr-:c = S3 C-t-cripc ion 5.- '
Multiple Cross Reference 72-77
Regional Data Element 7 73
Procedural Compliance 79
Card Code 6 Card Column
*Conunent Line Number 20
Point Comments 21-79
Card Code 7 ' Card Column
Optional Action Description 20-34
(used with Action Type 00)
Penalty Amount 46-52
Action Type 53-54
Date Achieved . 55-60
*Date Scheduled 61-66
Staff 67-69
Results 70-71
Regional Data Element 8 72-73
-34-
-------
Card Oode 8 Card Column
*Comment Line Number 20
Action Comments 21-79
*These Data elements should be filled in when a new transaction
is being added to the Masterfile.
Actual data preparation is performed usinq coding sheets or a special data
entry form. Data preparation techniques will vary from one regional office to
another, and a variety of input format will be developed. A suqgested entry
form is shown in Figure 6-2. This form includes space for the entry of all
eight card types. Some regions will develop forms for specific card type for-
mats only, depending on the frequency of specific types of inpuc data. Other
regions may utilize direct terminal screen data entry.
A complete Data Element Description which lists CDS data names, values,
edit error messages and coding considerations for each card type is given in
Appendix A. Some of this information is included in the following description
but not in detail, so users are urged to familiarize themselves with the com-
plete listing provided in Appendix A.
The sections which follow describe the spec i:: i-.j ~~^c-;-~~.': ^-:, -, . .;,-: ..11. : ._ :
to add, change or delete records on the CDS Masterfile. The first step in
adding a new record to the CDS Masterfile is to code an input transaction with
an Update Code "N" in column 30 for each card type needed to create 2. Master-
file record. Once a record has been added as new, a transaction with an
Update Code "C" can be used to change the record or a transaction with an
Update Code "D" can be used to delete the record.
6.2 Adding Nsw Records to the CDS Masterfile
Card Type 1 with an Update Code "N" is used to add a new facility to the
Masterfile. A facility in CDS represents all the site, emission and
-35-
-------
Illllllll
boo
o
o
ooboo
ilTi!.]i7Tj7j!|i
ojojojojo
00
000
ojpjo|q|o
iitr.siiui.
IMlllll 111
IJJJ°1P.
JJJ919
nT'.vinii
in
r'niul liO
'' ii
Ai|l II
COMPLIANCE DATA SYSTEM CODING SHEET
MXIIill IIAIM
fill NAfll
n>k'
!L
hii I III Mil
.I -1 ..' .!
4"Ji!|U'ffil!ire;[U
Irii i|fi;''i;; jA'lNV HIADII*; I '"' J/J^VY.V'
?u5in|a|ffij!i\?\$ilqifpii^iT! i'nnn r? »|F
XI I II I IJJJ I II I -1 I I I-L
~~ I Illl Illl
,:inrn
SUM I'll.IVIKAI Illll
mil i AMI
wrafVM:'
IHII MI^
ffllll
fi
til
DIM ',
WKS
ZupJppppp
ilAII
11*111116
I Al II IK I.AI'Al III
MHIIIII II'VIIIIIS
TfflHrarriDI
zzrn
TBTTI
I I I I I I I I I I I II LLLLLLI-1 IJJJJJJJ. 1J.LJJJJJ_LIJJ.LLIJJJJJJLUJJJJJJ
I.JJ
II I i I I
I II I I I I
JJJJJJJ
Jl
J.L
J_L
li
Jj.
.I_LLLLIJJ..IJ_LLI_L
.IJJ_UJ±I.UJJJ_L
JjJJJJJJji
-i mi
JLJ/*|^|^nTT:!!|.'-l|i!!|iijiJ|L||H|i;:
IHI'.MUI! Al Illlll
uiiii mi in
IH
LL
IM'I 11)11^1 Al I It'll HI '..I KH'I Illll
U.lll hi III All) I'rf
J..IJ LLIJ I IJJJJJ
| I I I I I I I I I I I I I
Ai mm
LUJJJ.I I.MJLLJ1J.1
I I I II I I I I^LLLLJ-LLL
_L
HAM Auiiivin
JJJJ.L
AI 11 uiiinr.
Illll
r.
r.,5 l>
I
jj
i
i
it
I
n
F
!"
ft
1
,,
TIT
1 1
i
i
J
iS|₯
1
UAH Miiinuiiu
T
1
JU_L
JJ_L
1 1
fT
jj
J_U
n
Mi
-2
ilAII
'!.'
-
J_
itl
I.)
ts
L
177
'u
Til
n
i.i
/j
'
nu i
ikl
-
-
7?
1
1
,11
-
*3
n
II Sill 1
!!!
-
>\
ir
1?
u
j
a
III,
//
IH
-
,
Kill U
rr
r
L
TT
'4
\
\
\ '
?
m
\m$
~\i>
TLZI'Li:
}r
i
?
'4
\
Sli
x5
S
--'
n
1
J
v«.
-
Ill
-
*
Fiynre ti . Sample Coding Sheet
-------
enforcement action information for one particular source or plant. If a
source is subject to several air programs, such as SIP, NSPS and NSR, a separ-
ate source number is assigned for each affected air program.
To establish a new facility on the Masterfile, perform the following steps:
1. Request a Quick Look Report with the CDS Retrieval Package to ver-
ify that the facility being added is not already on the Masterfile.
2. Select a County Code/Source Number combination which will identify
the facility by a unique number. The NEDS source numbering con-
vention may be used when adding a new source. Otherwise, assign
the next highest sequential Source Number within the county. A
County Code name corresponding to the County Code number is gener-
ated by CDS when a new Card 1 is submitted.
3, Code columns 1-19 (Region, State, County, Source Number, Point
Action Number and Card Type) and the Update Code "N" in column
80. Region, State, County and Source Number together identify a
unique facility in the CDS.
4. Code Source Name, columns 27-46. If additional data elements
unique to Card Type 1 (Appendix A) are available, they should also
be entered at this time.
5. Additional card types with the same source identifier may be added
for this update cycle or for a subsequent update cycle as new
transactions.
Card Type 2 is used to add additional source level data such as City, SIC,
Air Program, etc., to the Masterfile. Card 2 can be entered with an Update
Code " N" only during the same update cycle as a new Card 1 for a given
source. If any field on Card 2 is entered at a later date, use Update Code
"C". Update Code "N" on Card 2 is valid only when Cards 1 and 2 are entered
during the same update cycle since the Card 2 is not used to create a Master-
file record. Perform the following steps to add a new Card 2:
1. Code columns 1-19 (Region, State, County, Source Number, Point,
Action Number and Card Type) and the Update Code " N" column 80.
-37-
-------
2. Code columns 20-34 (City Name) and columns 59-62 (SIC Codes). If
additional data elements unique to Card 2 (Appendix A) are avail-
able, they should also be entered at this time. If a Staff Code
is placed in columns 77-79, a Staff Name associated with this
Staff Code will be generated on the Masterfile.
Card Type 3 is used to add or.change pollutant compliance data on the CDS
Masterfile. In order to support the current program plan requirements to
develop adequate SIP's for TSP, SO , HC, CO and NO in non-attainment air
quality control areas, the CDS must carry a number of data elements which in-
dicate worst-case compliance for each pollutant produced by a facility contri-
buting to the non-attainment status of AQCR.
Card 3 data must be coded for all SIP sources impacting or of unknown im-
pact on non-attainment standards. Both major (Class A) and minor (Class 3)
sources contributing to the non-attainment status of an AQCR must have Card 3
information for all regulated pollutants they emit. It is not enouqh to code
in only the non-attainment pollutant(s) ; however, unregulated pollutants not
emitted by the facility should not be entered.
For each pollutant produced by a facility in a non-attainment AQCR, the
collowing data elements should be added to CDS:
Data Field
-Jodate Code
Pollutant ID
Coding Considerations
Must be a "C" for all Card 3
transactions, whether a user
is adding or changing data on
this card.
Must be coded for each pollu-
tant produced by the facil-
ity. Valid values are the
same as for the pollutant
code on Card 5.
-38-
-------
Data Field
Pollutant Compliance
Pollutant Emission Cateqory
Impacted AQCR Indicator
Pollutant Loading
Coding Considerations
Must be coded for each appli-
cable pollutant. This com-
pliance status should repre-
sent the worst-case compli-
ance of all the emission
points producinq that partic-
ular pollutant. Valid values
are the same as for compli-
ance status on Card 5.
Must be coded for each appli-
cable pollutant. valid
values are the same as for
emission category on Card 5.
This must represent the Po-
tential uncontrolled emission
for the pollutant.
Must be coded as follows:
a. Leave Blank or enter on
"A" if the facility does
not contribute to che non-
attainment status of t'r.-i
AQCR for this pollutant.
b. See Appendix A if the
facility impacts the emis-
sion standards for this
pollutant in a non-
attainment AQCR.
c. Code "U" if the impact of
this pollutant on the non-
attainment status of the
AQCR is unclassified.
May be coded. If it
it must be a numeric field
representing actual tons per
year of emitted pollutant.
To enter pollutant compliance data on the CDS Masterfile, users should
code card columns 1-18 to match the data used for Cards 1 and 2 for a given
facility. Column 19 must be a "3" and Column 80 must be a "C" for adding,
changing or deleting pollutant data. Because a facility can produce numerous
-39-
-------
pollutants, the input punch card has room for three sets of pollutant data.
Multiple Card 3's may be used to enter pollutant compliance data for facili-
ties producing more than three different pollutants. Up to 10 different
pollutants may be stored on the Masterfile for one facility. The order in
which pollutant data is entered into the system is not important for the five
pollutants subject to SIP regulations; PT, SO , HC, CO and NO are always
£ X
stored on the CDS Masterfile in the same order. Other pollutants are stored
on the Masterfile in the order in which they were input.
In addition to pollutant data, the Card 3 contains four new source level
regional data elements and it also contains Facility Capacity. Facility
Capacity is a seven-digit field used to indicate the output capacity of a
plant. The following units of measurement should be used:
a. For general processes, use tons per year of output produce. If a
facility produces over 1 million tons per year, code all nines in
this field.
b. For refineries, use barrels of petroleum processed per day.
c. For petroleum storage facilities, use thousands of barrels total
capacity.
d. For incinerators (sewage sludge or municipal refuse), use tons per
day.
e. For electric utilities, use total megawatt capacity.
Users should note that pollutant data on the Card 3 may be entered many-
times since it is a repeating data element. However-, Facility Capacity and
RDE9-RDE12 are not repeating data elements. Only one value for each of these
data elements can be stored on the CDS Masterfile at one time. If several
Facility Capacities are coded on multiple Card 3's for a facility during one
update cycle, only the value on the last card will be placed on the CDS
Masterfile.
-40-
-------
See Table 6-1 for a" complete list of all data elements on the Card 3.
Refer to the appropriate pages of Appendix A for detailed definition and guid-
ance on each individual data element on Card 3.
Card Type 4 is a comment card used to add additional information about a
facility which is different from the information supplied by the data elements
on Card Types 1 and 2. There are 10 comment line numbers available on Card
Type 4; up to 10 comments may be used to add information for each facility.
New comments may be processed at the same time or after a Card Type 1 for a
facility is added to the Masterfile. However, a source comment cannot be
added to the Masterfile unless the source record already exists on the Master-
file.
1. Code columns 1-19 (Region, State, County, Source Number, Point,
Action Number and Card Type) and Update Code "N" in column 80.
2. Code comment information in columns 21-79. Assign comment line
numbers (column 20) sequentially starting with number one or
zero. If a facility has been previously added to the Masterfile,
request of Source Data Report for that facility to determine what
line numbers have already been used. A Card Type 4 comnient must
have a valid line number. The Update Code N can be used only when
the comment line number is not on the Masterfile.
3. Code "A" or "B" in line number to indicate a mailing address if it
is different from the street and city on Cards 1 and 2.
Card Type 5 is used to add emission point data for each pollutant emitted
by a facility. A CDS emission point represents information for one regulated
pollutant coming from one process or smoke stack. Processes which emit two or
more pollutants will be coded with multiple emission point numbers. Often
regions will assign the first two digits of the CDS emission point to
-41-
-------
TABLE 6-1
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 3
Data Name
Blank
Pollutant 1
Delete Flag 1
Pollutant Compliance 1
Pollutant Emission
Category 1
Blank
Pollutant Air Quality
Control Indicator 1
Pollutant Loading 1
Pollutant 2
Delete Flag 2
Pollutant Compliance 2
Pollutant Emission
Category 2
Blank
Pollutant Air Quality
Control Indicator 2
Pollutant Loading 2
Pollutant 3
^e Le.e Flag 3
Pollutant Compliance 3
Pollutant Emission
Category 3
Blank
Pollutant Air Quality
Control Indicator 3
Pollutant Loading 3
Facility Capacity
Regional Data Element 9
Regional Data Element 10
Regional Data Element 11
Regional Data Element 12
CLASS Code
Loading Derivation Code
Card Column
20-21
22-23
24
25
26
27
28
29-33
34-35
36
37
38
39
40
41-45
46-47
43
49
50
51
52
53-57
58-64
65-71
72-73
74-75
76
77-78
79
Da ta Type
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Numeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Numeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Numeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Length
2
2
1
1
1
1
5
2
1
1
1
. 1
5
2
1
1
1
1
5
7
7
2
2
1
2
1
Justified
Right
Right
Right
-42-
-------
correspond to the NEDS emission point number while the third digit is pollut-
ant specific. Thus, if a boiler produces both particulates and sulphur diox-
ide and has a NEDS point number 01, the CDS point number for particulates
miqht be 010 and the SO. point number might be Oil. For each facility,
there can be up to 1000 emission points.
Point 000 contains compliance status and emission category information Cor
the entire source. A point 000 transaction should be entered into CDS with an
Update Code "N" at the same time that a Card Type 1 is entered as new. Con-
sequently, point 000 information added to the Masterfile after Card Type 1 fias
been added must use an Update Code "C" in column 80.
1. Code columns 1-19 (Region, State, County, Source Number, Emission
Point Number, Action Number and Card Type) and the Update Code " N"
in column 80. An emission point cannot be added to the Masterfile
unless a corresponding source record is being added or has been
added previously to the Masterfile.
Emission point 000 is reserved for the entire source. All other
emission point numbers are assigned sequentially. When one physi-
cal emission point (Process) needs several emission point numbers
(one for each pollutant or regulation) , use the multiple cross-
reference field (Card 5, columns 75-77) to tie together the
various emission point numbers to one physical emission point, or
use the NEDS point number together with a pollutant specific -.,::.:
digit. When adding new point numbers for a facility, request a
Source Data Report for the facility to make sure that the new
point number does not already exist on the Masterfile.
2. Columns 30-33, Compliance Status, SIP Code and Pollutant, should
be coded if information is available at the time Card Type 5 is
prepared. Compliance Status must be coded for point 000; SCC must
be coded for all other points. If additional data elements unique
to Card 5 (Appendix A) are available, they should also be entered
at this time.
Card Type 6 is a comment card used to add information about an emission
point which is different from the information supplied by the data elements on
Card Type 5. There are 10 comment line numbers available on Card Type 6; up
to 10 comments may be used to add information. A point comment cannot be
-43-
-------
added to the Masterfile unless a corresponding emission point already exists
on the Masterfile.
1. Code columns 1-19 (Region, State, County/ Source Number, Point,
Action NUmber, and Card Type) and the Update Code "N" in column 80.
2. Code comment information in columns 20-79. Assign comment line
numbers (column 20) sequentially starting with number one or
zero. If an emission point has been previously added to the
Masterfile, request a Source Data Report for that facility to
determine what line numbers have already been used. A Card Type 6
comment must have a valid line number. The update code "N" can
only be used when the comment line number is not on the Masterfile.
Card Type 7 is used to add information describing actions taken by the
local, State or Federal regulatory agencies. Each region is responsible for
defining the actions which will be tracked by CDS. Regions must obtain clear-
ance from the national DBC for new Action Type codes and descriptions. The
national DBC maintains a table which relates the Action Type to the Action
Description.
1. Code columns 1-19 (Region, State, County, Source Number, Point
Action Hjmber and Card Type) and the Update Code "N" in column 80.
Action Numbers (columns 17-18) should be assigned sequentially
starting with 01. When adding a new action to the Masterfile,
Action Number 99 can be coded into columns 17-18. The system will
convert 99 to the next highest sequential action number for that
emission point.
New action numbers cannot be added to the Masterfile unless the
emission point for that action is also being added to the Master-
file or has been added during a previous cycle. Each action num-
ber must be associated with a specific emission point.
2. Code columns 53-54 and 61-66, Action Type and Date Scheduled.
Consult the regional action table for the Action Type. If neces-
sary call the national DBC to add or change values on the action
table. When entering scheduled and achieved dates, enter them in
month, day and year format.
3. Code additional data elements unique to Card Type 7 (Appendix A)
if they are available.
-44-
-------
Card Type 8 is a comment card used to add information about an action
which is different from the information supplied by the data elements on Card
Type 7. There are 10 comment line numbers available on Card Type 8; up to 10
comments may be used to add information. New action comments may be processed
at the same time that a new action record is added to the Masterfile. How-
ever, an action comment cannot be added to the system unless there is a cor-
responding action record already in the Masterfile.
L. Card Columns 1-19 (Reqion, State, County, Source Number, Point,
Action Mjmber and Card Type) and Update Code "N" column 80.
2. Code comment information in columns 20-79. Assign comment line
numbers (column 20) starting sequentially with number 01 or zero.
If an action has been previously added to the Masterfile, request
a Source Data Report for tnat facility to determine what line num-
bers have already been used. A Card Type 8 comment must have a
valid line number. The Update Code "N" can be used only when the
comment line number is not already on the Masterfile.
6.2.1 Sample of a Completed Coding Sheet for a tew Facility
Figure 6-3 is a sample coding sheet used to enter a facility for the first
time.
Card Columns 1 through 13 are the same for all cards for this facility;
these columns need to be coded only once at the top of this coding sheet.
Zeros in columns 14 through 18 are preprinted on the coding sheet for Cards 1
through 4. For the Card 1, only columns 1 through 19, columns 26 through 46
(Source Name) and column 80, Update Code, must be coded for a new facility.
This is the minimum amount of information which will establish the facility on
the Masterfile. Other information for this facility is also available, so it
is coded in the appropriate card type and card columns.
If the emission point 000 data were not available at this time, the Update
Program would generate an emission point 000 record on the Masterfile for this
-45-
-------
ill.MIII. si I imilin IMHIKII uin:|i
"
t fll(]l I UNI
LnnntliZfiii
gjojojojo
ipiirraiE
qjqjqjo|q
one
MilMllMIJ
o|ojojj
COMPLIANCE DA; A SYSTEM CODING SHEET
m
(in IIAJII
.vi/iirviiiiiriii \.Miiii-:
MIIJHtl IIAIII
vJo
rrmriHUinr
0|Q|Q|6|0
ojojojqjo
IMI'.SIIIII
ll'llllll Nil
, bl/Mojofe
5
llnl
i>lll> UN I i
!l|E !! |17|!!!|!5
75
i n.r.liMi inn
ill,
,
;i, niAlilllt.
N 1 ">
J ,-J-
UIH
Kill '.
J2IMS
;i, niAlilt. in , ;. ,'),''i Illuli
fe illl.lf! H1C KIT? JfrJEJii h L 7jiaj2rjifj
IAI II III (AI'AI III
(
» I ,, N
I ,''
CsnojTj CID
ni3iHraRnR-P.'i'/ii|J8|ii'ii|T?i'PiF]!'iF'niii«ri3 i»in i;- iiiniiri'i f l-i
5SJI
.' 'I Illl Nil
ILL
i rollil ( mill 'i
duse K a os E
!i
THTT mTh]",] .nl sillily l^rAl^ray|^l!niO6!fIIIi.'.IM|5Z|!:!!|SS|ZL>|i!r
:LjlLLLLlJzllnJllmHI I\
MINI I I I I I II I I I I I I I I I I I II I I I I I I I I I I I I I I I I I I I I I I I III I I I I I I I
0| /
Oil |p
Uil .Mini
rrrnr
lll'IIIIIIAI Al Hull 1.1 Ml, ll'l Inn
ir.in nun AIM w
JJJ_LLLI.U_Q.LLI.
7| I I I I I I I I I I I I I I
HUM II AMI
I I I txlll ir^LL|..IJ.J_LL
elf
P|3
IIAII AIIIIIVIII
_LLJJ_i_
IIAII Mill HUM II
&\o
Ul bill I
u I (Mil III .
! M'jir-m
/!il)9 3
03
H-
(/>
m
a.
Figure 6-3. Sample of Completed Coding Sheet for a New Facility
-------
facility. However, the emission point 000 can be coded as new when it is
entered at the same time as the new Card 1. In this example the Compliance
Status and the SIP Codes for point 000 are the same as for point 010 since the
Compliance Status and the SIP Codes of the entire source represent the worst-
case compliance status of any of the other emission points.
In this example/ emission points 020 and 021 represent two different requ-
lated pollutants being emitted from the same smokestack. The 020 in the mul-
tiple cross-reference field (columns 75-76) for emission point 021 indicate:-:
that emission point 021 represents another regulated pollutant for the sa:r,e
process described in emission point 020.
Actions are entered at this time with a Date Scheduled but no Date
Achieved since they represent actions to be performed in the future.
6.3 Changing Data on the CDS Masterfile
Once a record has been added to the CDS Masterfile by the update cycle,
data on the Masterfile record can be changed in subsequent update cycles by
using input transactions with an Update Code "C".
During a given update cycle, transactions with the same record identiciar
(Region, State, County, Source, Point, Action Numbers and Card Type) are
applied in Update Code order. The Update Program processes deletes first,
then adds, and finally changes. The Update will reject a change transaction
if a delete if being applied for on the same card type during the same update
cycle. However, the Update will process multiple changes for an existing
Masterfile record. Multiple changes ace applied in chronological order; if a
given data element is being changed by several input transactions, all input
transactions are printed out on the Update Report, but only the latest change
will be found on the Masterfile.
-47-
-------
Card columns 1-19 must be coded when preparing a change transaction. How-
ever, the data elements in columns 1-18 cannot be changed by processing as a
change transaction. If transactions with incorrect State, County, Source,
Point or Action Mimbers have been added to the CDS Masterfile, those records
in error must be deleted and the corrections re-entered with an Update Code
"N". When any of the data elements in columns 20-79 need to be changed, only
the data element that needs changing is coded on the input coding sheet.
The following steps should be performed for a change transaction:
1. Request a Source Data or Quick Look Report for that facility to
determine what data values exist on the Masterfile.
2. Decide what data elements need to be changed and decide what card
type should be used.
3. Code columns 1-19 on a coding sheet. Code a "C" in column 80.
4. Code only those data elements which need changing. The update
orogram will change only those data elements that are entered on
the card; other data elements on the Masterfile will not be
changed.
5. Have coding sheets keypunched and submit punchcards to the CDS
B3it Program.
6. fJse a Change transaction and not a Delete transaction to :*-'.-
one or more data elements from a Masterfile record. Data elements
in columns 20 through 79 of any card type can be blanked out by
placing one ore more asterisks(*) in the data element which is to
be eliminated. An asterisk will remove only the data element to
be blanked out and will not change any other data element on the
Masterfile record for that card type. Or, the Card 7, an aster i.-!"
on Date Scheduled or on Date Achieved will zero-fill the data ele-
ment since these data elements cannot be blanked out. An asterisk
cannot be used to change any data elements in card columns 1
through 18; if a record with an incorrect State, County, Source
Hjmber, Point or Action {Umber has been placed on the Masterfile,
the incorrect data must be deleted with an Update Code "D" and the
corrected cards re-entered with an Update Code "N".
Since asterisks are used on change transactions to blank out a
data element, asterisks may not be used on new transactions. A
warning message ('ASTERISKS FOR CHANGES) is issued by the Edit
Program if asterisks are found on any transaction with an Update
Code "N". Asterisks are not placed on the Masterfile in the
update cycle.
-48-
-------
7. An Update Code "C" should be used foe adding or changing pollutant
data on a Card 3. A delete transaction is not valid foe a
Card 3. If a user wishes to delete all references to a pollutant
on the Master file, he should code the appropriate pollutant code
followed immediately by a "D" in the Pollutant Delete Flag on the
Card 3.
If a user wishes to blank out one or more data elements associated
with a pollutant on a Card 3, he should place one or more
asterisks(*) in the field to be blanked out. Because data is
stored on the Masterfile by Pollutant Code on a Card 3, changes to
Pollutant Compliance Status or other pollutant related fields must
always be accompanied by a Pollutant Code.
Users may make changes to the Pollutant Compliance Status of sev-
eral pollutants regardless of the order in whicn this data was
originally entered; all changed and additions are applied by
pollutant.
6.3.1 Sample Completed Coding Sheet for Change Transactions
Once a facility has been entered as new on the CDS Masterfile, change
transactions can be entered for records existing on the Masterfile. Columns 1
tnrough 19 must be the same on the cnange transaction as they were on the new
transaction already on the Masterfile; column 80 must be a "C" for each change
transaction.
?i:^r-e ';-': is i sample Todir.g .sheet used to -j.-.a.-. -:e jo;r.e or cr.e da "a incu;
as new in Figure 6-3. It is also used to add new records which were not
created in Figure 6-3.
Card 4, line 2, a source comment exists on the Masterfile with the follow-
ing text: PORTLAND CEMENT PLANT. A change for Card 4, line 2, will replace
tnis text with the text on the change transaction: PO BOX 753.
Card 5, point 000, contains a "7" in the Compliance Status Code on the
Masterfile. The change transaction will replace the Compliance Status Code
and the Process Description; all other data on the Masterfile record will be
unchanged. On Card 5, point 010, only the Compliance Status Code will be
changed on the Masterfile.
-49-
-------
Ol
o
I
73
O>
I.lull. S| l CIHIMII ISUIHC
Til imqFmm-
04 i 819
00
i/ra
ojo
OOOOO
10000
ooooo
|o|pjpjo]o
nin
01
Cllr inni
Iff
COMPLIANCE P'.TA SYSTEM CODING SHEET
ana
FilK'h'IH
(.111 KAMI
PIXIUIAHI I
1 <- ' riUHISS DI'^IIIIP
iffiffillBIl^^
1LLLLL LI JJJJJJ.LLLLLJJ J JJJ_LLI _L .LL1 J_I±LLLLL
_LL
I 1
liiissluN
NV4IH
i] i5|U
ojajo
Q|Q|S| n 11111
olofeLLLLLLIJ.
Jllli.
of
0106
(MISSION AC 1101
I'D IIII IHJ
1311111?
oj2|o
fiiiumii
IS
I I
ID.
o
/-^UHt HO.
WZJT
S ElElKll
_LLIJ_[JJ1L11JJ_LL|JJJ_LLLLLLLLLLL[ I I I I LLLU,
I I 111 11 11 I l 11 I 11 I 11 I I I I 11 111 I I 11 I I I I 111 I
JJJ
JJ.
'«|W|!I
c
JJ
n
2ifini^JiimiiT|jj|!5|in« nn«ns|!u H
MIT FOR CO
IHISSIOH PUIIIJ cr«fi(nis
it
A L
VERSION.
II I I I I I I I I I II I I I I I I I I Ml II I II I II I II I II I I I I I I I I I I I II I I I I I I I
OPIIOIIAl AC 11 Oil OfSCRIPIIOIt
in i (i UIIH Airt n
IE
[»inp
\s\s
TH)?
I I.I IIII11111II
7\ ILLLLLLLLLLI II
3*M^;
m
.;bk
PfHAlll /Vll
AC I ION
Tlli?
c^l^l^M I^RR]
i IN IM.MiM^-t-'. l^lAhM>M_
SIS^^I>t'>lS^1 I I I I.I J
ITPl
op
fill
DAK AfMilHII
isIiFlhlWR?^
o|6|3Jj|l8jo
o|7|o|5|8|o
_LLLLI.
UAIf SI IIIIHII (U
66
o|7|o|5|8|o
JJJJJJJJLLL
r,ll|b9
11
am
[TTpLE
:,bM
mN^K
IIKI HO
SB]7i|?n?7iisiy ii?rn'|]i|n|i?nnjin/ni!|u|!ii|'! T? n]in^ni:[.i7pj|r'(yi|5!|v|r'|^[5i]i;t wp ^|^^|H|si[MK5|w|^[^F'|Ei|7n??ni|p|5|'tnn!eni
in
CD
Q.
Figure 6-4. Sample of a Completed Coding Sheet for a Change Transaction.
-------
Since point 020 did not have any comments associated with it, comment 1
for point 020 is entered as new.
Action 01 for point 010 has no Date Achieved or Results Code on the
Masterfile; a change transaction will add these two fields to the Masterfile
record created during a previous update cycle.
Point 020 did not have any actions on the Masterfile. Thus, an action 01
is added with an Update Code "N".
5 . 4 .'^L.-.-'cini; Data from the (JDS Masterfile
A del-»ts cransao tier, contains a " D" in column 80, the Update Code; it is
used to !-; Lets one or mere records from the Masterfile. A Card 1 delete will
remove ;ili. Masterfile records for a given facility. A Card 5 delete will
remove or.-; emission point together with all associated comments, actions and
action cements. A Card 7 delete will remove one action together with all
associated action comments. A Card 4 , 6 or 8 delete will remove one comment.
A Card 2 oc a Card 3 delete is invalid. Remember, if only some of the data
elements on a oarticular card type are to be deleted, a "C" must be entersd in
coluir.n 30 and asterisks placed in these fields. A "D" in column 30 will
delete the entire card type.
o'.ircq, Card 1. An entire source can
deleted by using a Card Type 1 with an Update Code "D". Fill in
columns 1-19 and code a " D" in column 80. Do not fill in columns
21-79; no data may be coded in these columns. Before submitting
this card, make certain that all the information on the source is
no longer needed. This transaction will delete the entire source
anc) ull r&l.itsc points, actions and comments.
2. Deleting an Emission Point, Card 5. Fill in columns 1-19 and
place a "D" in column 80. Do not fill in columns 21-79; no data
is to be added to these columns. An emission point delete will
remove the emission points, all associated emission ooint com-
ments, actions and action comments. A Card 5 delete for point 000
is invalid.
-51-
-------
3. Deleting an Action, Card 7. An action record can be deleted by
using a Card 7 with an Update Code "D". Fill in columns 1-19 and
place a "D" in column 80. Do not fill in column 21-79; no data is
to be added to these columns. An action delete will remove the
action record along with associated action comments.
4. Deleting a Comment, Cards 4, 6 and 8. A source, emission or
action comment may be deleted by using the appropriate Card Type
4, 6 or 8 and placing a " D" in the Update Code. Columns 21-79
must be blank. Card column 20 must contain the line number of the
comment to be deleted. A comment delete transaction will delete
only one comment record.
Use Card 4 to delete a Source comment
Card 6 to delete a Point comment
Card 8 to delete an Action comment
5. Deleting a Pollutant. Once a pollutant record has been estab-
lished on the Masterfile by Card 3 transaction, it cannot be
deleted unless the entire source is deleted. However, all c?-i
-------
Figure 6-5 shows three delete transactions and one change transaction. A
delete for emission point 040 will remove that emission point and all associ-
ated point comments, actions and action comments for that point.
A delete for emission point 020, comment line 1, will delete only that one
particular comment record from the Masterfile.
A delete for emission point 010 action 02 will delete one action together
with any associated action comments.
To remove some data from a Masterfile record without removing the *?co":
c:o:-, -;: e Mas tec file.. use an Update Code "C"; code an asterisk in -:-;.;.-. - - -:. .
vr Lvr. :..; to oe removed. In trie example, a change transaction for .--"'. .;;' ?,
point 020, action 01 .» i 11 olank oat the Results Code 01 on the M-i:.-.' ': -..-.
r ~ i. a u .= e there ^.o an asterisk in tne Results Code fielc. 3ecau^--'' .''..
-J'."!edL.ifed and bate Achieved cannot be blanked out, an asterisk in tne '5 -'-_
Achieved field will replace the existing Masterfile witn zeros,
6.5 Sevpunch Instructions
i!-.ere -2re six different card layouts which must be typed by th<= k--.\:.u.--:;
^^'..-itor SOL input -.: aiisaccions to CDb. The operator is r^apons .c_e ::!.'
ing only the information wnich is coded on the coding sheets or forms 311;:-
mif-ted by tne user. However, card columns 1-19 and 80 must always be- fill?:
. ;. .":-y the operator o;; i". i card types.
1'hi.s section contains a listing of tne data elements on eacn or :':-.;r .;.u-
':'.'I:--'-- which will oe used by the operator to enter transactions onto the :q..i:-':
oc.3;i. Table 6-2 lists tha data elements 1-19 and 80, which must be ccosa o;;
all card types. Tables 6-3 through 6-7 list the data elements unique to each
card type.
-52-
-------
K.IUII, ii i muni; l'..i mil ""i !
;T»
TFFIi,
00
lo
HTura m\«
ojojoojo
qjo|p|o|o
2|0|8
A.PII
COMPLIANCE DATA SYSTEM CODING SHEET
i!j
'Jji-
-.^rTrroiwiT1
f II
I;];!" DJuijK1
* ' Urn
ninnHi7;
iiinsi
HID 4 I KOI '
}mi\u\r.
0|!l|53| 5)
I I
U
Inn Ilii'i:'."'{,) loAuiiii. I "in r|i'*Vi;; ; IIIAUIIU. |"-'ii|Ai'*
Mfflffll^lfflm''^!!!!!!!!!
I , ,>' ( .' .< A I lAtimi IAIAUIK | HUI »
IIIAUIIU. I"'"" IjM.'^ji'jilJ UtfillMl _. I _- - -|T
!.
S/JJjj
U
IMI'.SIUII,
Illlllll l«l I I I i(l I'1"'
liiri4"nthjn«|F.|;i'|u|2^.!j|fin;
loljjom5! ill IL
LLLLJ LLLLUJJJJJJJJ IJJJJJJJJJLU-LLLLJ-LLLLLU I I I I I I I I IJJ I M I J
* * (III 1 V, j ? \i^
id iimi (Ai-i -Jjvj elm ^>i*" HII.IIIAIIIIM ^ fiiiHi'.'. mumriiim ikii <_|^. _^j
i
LLIJ°|o|5LUJ_LiJJj
lli^lllLLLLL
Ll iMLLLLIJJI
.HUM lull
110
I !I>1XM ( I I U I
Tr-TTTTrv)
J
UAH AlllllVIU
J-LLLL
UAll MIIIUUIIU
44.
I I I I I
11
M
inn i.
IKS
t'.'l!l!
7iI7i|/f177
7IIIJ
u»'V
I'iyure .-.-5. Sainplt; .,f Coni|jleted Coding Sheet for IVilele Transactions
-------
TABLE 6-2
KEVl'UNCH INSTITUTIONS DATA REQUIRED ON ALL CARDS
Date Net me
Region
State
County Code
Source Number
Emission Point Number
Action Number
Card Code
i
ul Update Code
Card Column
1-2
3-4
5-8
9-13
14-16
17-18
19
80
Data Type
Numer ic
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Alphanumeric
Data Element Length
2
2
4
5
3
2
1
1
Justified
Left
Left
Left
Left
Left
Left
-------
TABLE b 3
KEYWJf-.-.';i INSTRUCTIONS FOR CARD TYPR 1.
Date Name
AQCR
City Code
Source Name
Street Address
t'n Regional Data Element 1
i
Regional Data Element 2
Regional Data Element 3
Regional Data Element 4
Regional Data Element 5
Card Column
20-22
23-26
27-46
47-66
67
68
69
70-74
75-79
Data Type
Numeric
*
Numeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumer ic
Data Element Length
3
4
20
20
1
1
1
5
5
Justified
Left
Left
Left
Left
-------
TABLE 6-4
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 2
i
ui
Date Name
City Name
Zip Code
State Registration Number
NEDS Cross-reference
SIC Code
Federal Facility Code
Air Program Code
Air Program Status
Regional Data Element 6
Staff Personnel Code-Source
Card Column
20-34
35-39
40-54
55-58
59-62
64
65
66
67-76
77-79
Data Type
Alphanumeric
Numeric
Alphanumeric
Alphanumeric
Numeric
Numeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumric
Data Element Length
15
5
15
4
4
1
1
1
10
3
Justified
Left
Left
Left
Left
Left
Left
-------
. TABLE 6-5
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 5
Date Name
SCC Code
Capacity Code
Compliance Status
SIP Code
i pollutant Code
Ul
CD
1 State Regulation
Emission Category
Process Description
Multiple Cross-reference
Regional Data Element 7
Procedural Compliance
Card Column
20-27
28-29
30
31
32-33
34-48
49
50-74
75-77
78
79
Data Type
Numeric
Numeric
Numeric
Numeric
Alphanumeric
Alphanumeric
Numeric
Alphanumeric
Numeric
Alphanumeric
Alphanumeric
Data Element Length
8
2
1
1
2
15
1
25
3
1
1
Justified
Left
Left
Left
Left
Left
-------
TABLE 6-6
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 7
Date Name
Short Action Description
Penalty Amount
Action Type
Date Achieved
Date Scheduled
U1
f Action Staff Code
Results Code
Regional Data Element 8
Card Column
20-34
46-52
53-54
55-60
61-66
67-69
70-71
72-73
Data Type
Alphanumeric
Numeric
Numeric
Numeric
Numeric
Alphanumeric
Numeric
Alphanumeric
Data Element Length
15
7
2
6
6
3
2
2
Justified
Left
Right
Left
Left
Left
Left
Left
Left
-------
TABLE 6-7
KEYPUNCH INSTRUCTIONS FOR CARD TYPES 4, 6, AND 8
a\
o
i
Date Name
Line Number
Comments
Card Column
20
21-79
Data Type
Numeric
Alphanumeric
Data Element Length
1
59
Justified
Comment Line Number
Managers1 Name
Comment Line Number
Street Name
City Name
State Abbreviation
Zip Code
(A)
21-40
(B)
21-40
42-56
58-59
61-65
Card Types 4A & 4B
20
20
15
2
5
-------
6.6 Quality Assurance Considerations
6.6.1 Define the Problem
As the user, you must understand what data needs to be entered and your
role in defining it. Misunderstandings can come from poor instructions as
well as from poor listening. Ask your manager as many questions as necessary
until you are sure of what must be done. Spending a few extra hours can save
a lot of time and work at a later date. At this step, outline your analysis
of the problem. This way, any inconsistencies in your analysis can be cor-
rected.
6.6.2 Status of Current Data
a. Evaluate the source documents. When possible, cross-reference the
source documents to determine the validity of the documents. Do
not assume that documents supplied by the States are always cor-
rect or complete. For example, cross-check State EIS reports with
the York Report for data on coal-fired boilers. Ask questions to
ensure that the documents being used are the most accurate and
up-to-date documents available.
b. Run CDS retrievals to determine what data is already in CDS. Use
retrieval reports to compare before/after data. It may be better
to run five or six Quick Look Reports instead of a single Source
Data Report. Quick Look Reports allow the user to view unl'y z'r.o :?
data elements of interest and in a format where all of the same
data elements are lined-up. This makes it much easier to spot
gaps in the data.
6.6.3 Code Data
a. Analyze data entry method. Before any coding is done, determine
the best input medium, There are four kinds of incut mediums:
coding sheets, modified coding sheets, retrievals and terminal
screens. On a modified coding sheet some of the data elements ar-*
preceded. Whenever possible, use a double spaced Quick Look as
input documents. The fewer pen strokes needed to enter the data,
the fewer mistakes that can be made.
b. Data from source documents. Code data from source documents care-
fully. Code from the four basic source documents.
-61-
-------
1) Data already in CDS (e.g., developing AQCR from County Codes)
2) Source documents supplied by the States
3) Another computer system's printout (e.g., NEDS or EIS)
4) Source documents in the EPA files
There are three types of coding changes that can be made.
data can be added, data already in the system can be changed to a
different value and data can be deleted. Be aware that when you
delete a record, all subsequent data elements under it in the file
hierarchy are also deleted. Make sure that you consult your man-
ager if there are going to be delays in your time estimate as soon
as you know about them.
6.6.4 Random Check of Coding
Once all of the data has been coded, a "random check" of approximately 50
percent of the data should be performed against the source documents. Th.5 CDmouter Operations
a. Input to edit. Log out coding sheets as they are sent to key-
punching, the cards should be logged in and marked with the date
and your initials. As soon as the cards are marked, they should
be placed in the computer. The edit report should be checked for
keypunch errors and any necessary corrections should be ma^e i.im-
mediately.
b. Enter into the update cycle. Thursday mornings after the update
has run, you should check the update report for errors. Any er-
rors should be corrected at once. The correct data will not be
placed on the masterfile until the next scheduled update.
c. Validate the update cycle results. Run a second set of retrievals
in the same format of those that were run in Step 6.6.2(b). These
two sets of retrievals should be compared to ensure that the data
you wanted have been posted correctly. As a final check, compare
100 percent of the coded data with the source documents.
-62-
-------
d. Involve your manager in validation work. After step (c) has been
completed, qive your manager the retrievals run in step (c) .
These retrieval reports will allow your manager to recognize the
quality and quantity of your work.
-63-
-------
7.0 EDIT PROCESSING
'.1 Edit Program Usage
Once data Cor the CDS has been coded and keypunched, users must validate
the input transactions by running the CDS Edit Program. The Edit can be run
it ar.y time, and it can be run any number of times in between update cycles.
However, it is best to coordinate the scheduling of Edit runs to correspond uo
the scheduling of the update cycle. Allow time to correct any errors that may
be detected by the Edit before the weekly update.
When running the CDS Edit Program, users may identify their d^ta bv -..:-.
ORIGIN Code, -is indicated in Figure 7-1. (S3) . if data being in.pi.i1: j.£ -"::M ~.
State report, users can identify the State as the ORIGIN of ths data by -:.-: ir.g
tn;j region number and State abbreviation in the Parm statement of che ^xsci.co
:»::d. (Figure 7-1) .
Siix:a the update cycle is usually run on Wednesday nights, users ::r.t>:Io
schedule their data preparation. Edit runs and corrections to be rer.dy ccc .'/:-
update cycle. At least one day before the update when the input transaction
-." --..T:-- : -. -:-'*r 2000 cards o°r w.;^> ar. i-i=al :-'-=>'':' ^ ......'> -
1. Punch cards are delivered to the regional CDS DBC or to the oper-
ator of the communications terminal on Tuesday afternoon.
2. Inout cards together with apnrooriate Jr', cards ar1? -utmi ':v. z~\. -. -
".^-isday niqric to tCC.
3. The Edit Report is examined on Wednesday morning.
4. Edit errors -are corrected Wednesday morning and resubmitted with a
high priority on Wednesday afternoon.
When the volume of input transactions is over 2000 cards per week, or when
keypunching is returned to the user in multiple batches, it is best to run the
Edit several times during the week as soon as data is returned from keypunch-
ing.
-64-
-------
AUTHOR me
.ICI. for us
1
z
7
-
2
2
/
*
/
/
/
*
3
E
R
C
E
i
E
Th
4
P
O
D
D
1C
O
5
A
U
S
1
F
ibi
6
i
T
E
T
n
Ve
i
E
D
.
i
i
8
i
1
C
U!
uo
9
T
A
1C
c
10
P
R
t
n
II
R
D
,11
9
1?
J
1
E
S
sa
sh
W
In ;
13
O
N
X
1
it
le
U
B
T
E
n
01
d
re
li.
15
C
1
-
...
bl
CHS Killt u
16
R
imi
P
U
a
M.
C
D
cd
a
IB
a
T
D
D
a
e<
19
a
r
S
e
-
'
20
a
r
1
-
t
pin
21
C
F'
nf
II
:i
1
.;
-
II
.1
.0
S
"
-
11
AM NAME CMS KDIT
J Inpul .
24
Y
f
In
1
25
P
P
f
26
1
A
JO
tl
2)
M,
R
.*
21
i
M
ji
n
29
i
;;
L
Ul
30
i
i
c;
1
31
)
-
n
nl
rn
32
-
n
16
33
t
S
1C
34
U
S
it
35
S
r
-
nr
36
E
31
R
31
-
3S
1
40
D
-
TASK NUMURH
41
4?
-
-
43
44
45
-
46
-
4;
41
49
-
50
51
52
-
53
-
54
55
56
-
5J
5B
-
Ul
i
iii Is the User's Initials
aaaa Is t.he User's Account Number
rr Is l:he User's Remote Number
n Is the User's Region Number or State Code;
Valid Values are 1-10, TN, SC, NE, etc.
nn Is ihe User's Region Number; Valid values
arc 01-10.
ss Is the User's State Code, where applicable;
VM.lid values are SC, TN, N:i, etc.
Figure / :. CDS Ldit Job Control
-------
The Edit validates each of the seven punched card types ona at a time.
Note that some transactions which pass the Edit may be rejected later. If a
new facility is being entered into CDS, the Edit may accept as valid all of
the transactions for that facility except Card 1 which contains the Source
Name and Address. In the update cycle, all of the transactions for that fac-
ility will be rejected since the facility level data was not passed to the
Update. With the hierarchial relationship between source, point and action
transactions, an error at a higher level can create additional errors in the
update cycle cor transactions accepted by the Edit. For this reason, i'- is
very important to correct and resubmit Edit errors as quickly as possible.
7.1.1 Earning and Fatal Errors
All transactions are validated by the Edit Program. The Edit P.epcrc pro-
duced by the Edit Program lists the action taken on each input t--..-sa..:t :or.,
If an input transaction has no edit error message next to it on the Edit
Report, it is a valid transaction. Oie or more error messages are printed on
the Edit Report next to transactions in error. Errors ar-e Lc?;n;:if i,?d ^:-:
eitner "vjarning" or "Fatal". One or more fatal errors will pro-. -.::... ^ .:.-re-
action from being saved for the update cycle. A transaction wiuh -jnly war\iir.q
errors will be saved for the update, but the data elements in error are
blanked out. The user must review the Edit Secort oar . J jl 1; ..; /^j:^/
accepted data and to make appropriate corrections cor rejectee!
-------
TABLE 7-1
EDIT ERROR MESSAGES
Data Element
Name
Message
For detailed
explanation,
see page:
Region
State
State
County Code
Source Number
Card Code
Update Code
Emission Point Number
Action Number
Source Name
Line Number
Update Code
Emission Point
Compliance Status
Action Number
Pet ion Type
Update Code
Action Type
Update Code
Update Code
Action Number
Source Name
AQCR
City Code
Zip Code
SIC Code
Government Facility Code
Air Program Code
*** INVALID REGION CODE
*** INVALID STATE CODE
*** STATE NOT IN REGION
*** INCORRECT COUNTY CODE FOR STATE
*** SOURCE NUMBER MUST BE NUMERIC
*** INVALID CARD CODE
*** INVALID UPDATE CODE
*** EMISSION POINT MUST BE ZEROS
*** ACTION NUMBER MUST BE ZEROS
*** SOURCE NAME REQUIRED ON NEW ENTRY
*** LINE NUMBER MUST BE NtMERIC
*** UPDATE CODE D INVALID FOR CARD 2 & 3
*** EMISSION POINT MUST BE NUMERIC
*** POINT MUST BE GREATER THAN ZERO
*** INVALID COMPLIANCE STATUS CODE
*** ACTION NUM MUST BE GREATER THAN ZERO
*** ACTION NUMBER MUST BE NrjMERI C
*** INVALID ACTION TYPE
*** NO DATA IN COL 21-79 FOR DELETES
*** ACTION TYPE REQUIRED ON NEW ENTRY
*** DO NOT DELETE POINT 000
*** UPDATE R ONLY FOR REVISED ACTION
*** ACTION NUM 99 VALID ONLY FOR A
*** SOURCE NAME MUST BEGIN IN COL 27
*** INVALID REGION ON CONTROL CARD
* INCORRECT AQCR FOR COUNTY
* CITY CODE SHOULD BE NUMERIC
ZIP CODE SHOULD BE NUMERIC
SIC CODE SHOULD BE NIMERIC
INVALID FEDERAL FACILITY CODE
INVALID AIR PROGRAM CODE
A-24
A-52
A-52
A-9
A-48
A -9 2
A-9 6
A -6 -\
A-76
A -4 6
A-94
A-9 6
A-64
A-59
A-76
A-9 6
A-77
A-9 6
A-9 6
A-76
A-46
A-4n
A-5
A-7
A-5 7
A-37
A-12
A-l
-67-
-------
TABLE 7-1 (Continued)
EDIT ERROR MESSAGES
Data Element
Name
Message
For detailed
explanation,
see page;
Staff Personnel Code-Source
SCC Code
SIP Code
Pollutant Code
Emission Category
Multiple Cross reference
Date Achieved
Date Scheduled
Results Code
Update Code
Action Type
Pollutant Delete Flag
Pollutant Compliance
Air Program Status
AQCR Indicator
Pollutant Emission Category
Procedural Compliance
Penalty Amount
Penalty Amount
Capacity Code
Source Compliance Code
Source Emission Category
Loading Derivation Code
INVALID STAFF CODE A-50
SCC SHOULD BE NUMERIC A-71
INVALID SIP CODE A-72
INVALID POLLUTANT CODE A-18, 67
INVALID EMISSION CATEGORY A-62
MULTIPLE XREF SHOULD BE NUMERIC A-65
INVALID DATA ACHVD - OUTPUT ZEROS A-73
INVALID DATA SCHED - OUTPUT ZEROS A-31
DATE SCHED SHOULD BE NEW - OP ZEROS A-81
INVALID RESULTS CODE A-8 6
ASTERISKS FOR CHANGES A-9 6
ACT DESC IGNORED - ATPE NOT OO A-77
INVALID POLLUTANT DELETE FLAG A-22
NO DATA TO FOLLOW DELETE FLAG A-22
INVALID POLLUTANT COMPLIANCE A-19
INVALID AIR PROGRAM STATUS A-3
INVALID AQCR INDICATOR A-16
INVALID POLLUTANT EMISSION CATEGORY A-20
INVALID CMS2 CODE A-68
PENALTY AMOUNT ONLY ON 2 () ACTIONS A-84
PENALTY AMOUNT SHOULD BE NUMERIC A-84
CAPACITY SHOULD BE NUMERIC A-5, 53
INVALID SOURCE COMPLIANCE CODE A-41
INVALID SOURCE EMISSION CATEGORY A-4 4
LOADING DERIVATION SHOULD BE A, P A-13
-68-
-------
Transactions with one or more fatal errors will not be placed on the MOD
File. Transactions with no errors or with only warning errors will be placed
on the MOD File for future processing by the Update. Keep in mind that a data
element flagged with a warning message is blanked out by the Edit.
For a detailed explanation of the valid values for each data element in
the CDS, consult Appendix A. Coding instructions are given for each data ele-
ment; edit error messages by data element are repeated in this appendix. Cer-
tain data elements are not validated by the Edit and may contain any alphanum-
eric characters.
7.3 Sample CDS Edit Report
A sample Edit Report is shown in Figure 7-2. Each page of the report con-
tains the report title, the region name, the date and the time at which the
Edit was run by the computer. The report also contains column headings for
the following data elements: Region, State, County, Source, Point, Action,
Card Type and Update Code. Directly beneath these column headings are two
rows of numbers indicating card columns; the position of any data on the card
can be determined by referring to these card column identifiers.
For each new Card 1 accepted by the Edit, a county name is generated and
printed directly beneath the County Code; this county name is passed to the
Update, where it is placed on the Masterfile together with all the other input
data.
Error messages are identified on the right hand side 'of the report. In
addition to the error messages.- data elements in error will have one or more
asterisks directly beneath the data element to help pinpoint the problem area
which needs to be corrected.
-69-
-------
I
~4
O
no
u
1 2
01
01
(11
01
01
01
UO
01
111
(11
01
01
01
01
(11
01
01
01
01
01
01
01
(11
01
01
01
til
01
(11
I'l
ul
f, 1
b 4
ul
SI
1 4
01
01
01
ul
01
01
III
t*
4*
44
44
44
44
44
44
44
44
44
44
44
44
44
44
44
44
44
44
44
44
4 0
12'. 0
t,. . 1
1. I|I» l
01.. II
Ul,' il
On li
li.i i,
(i
01,' 0
Oi..-
ll.ll- 1
1
'i C 1 . \
0 III] b f
i- ii ii o r
u VjJ 1
O-.-lbl
0 ' 1) u 1
(1* t II 1
il '.< U 0 1
ir.iidl
OlibOl
onnii
u II 0 0 1
onudi
UI'Oli.)
OlOOl
01,001
01)00
1 1 fl
01100
1. 1 1 II 0
O..IUO
1. 1 1 0 0
OilUd
0 S 1 Jil
1. 0011
I
1' C 11 1 1
<>ui, i :
b .. II '. J
010 1
I.I, 1.
'Ill'
bi'l. ,.
-I II L
1. ' II t.
" " >
.,
Ill .t
I'H 1
1 -' 1.
LUO
000
001
I'OO
000
too
000
001
000
000
000
001
002
001
001
005
OOb
000
000
000
000
001
1/02
Oil 1
llOO
000
000
000
001
lit 0
000
flOO
nno
II' 1
' no
*"
II-
no
00
00
liO
LO
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
110
00
110
bO
00
LO
no
',0
no
1 IT
1
b
'J
1
1
1
i
5
5
s
5
5
1
2
1
1
!»
5
b
1
;>
1
^
s
1
/
J
]
1
HUM run
-*0!.lil U 'I '1
1 1 0.'
IMAIIK SMI
PI 01
'iir r"
lo^o'o"
1
i Ann 1 1-1 i,"ii:. : i'i.. ..** i i . - i ' i ' t ' ' i ..i i 1 1 1
At. Al lull >! Al.l tl .
0
0
|-| .''(OAl Pill 1- th A 1 I.-F. I-IAI.I 1 .
I'l 2(LUI I'll! l-Af A 1 (I'll t'lAI.I N .
' 1 .
1 III.UH-I t'l-M l.-l SIAIII'j IINMIUMII '. .
0
0
0
0
0
0
0
C» 1 SI -UALL AS
ri 01
HAIL: MI.
1 0 '- b 1 0 'i 'I
in-ioioiy
00 / ull.
ii. n i mi
I'l bi>
.'O'lOIO'l-l
( ) 1 n r
1 -"I .-.»!( II
I' 1 L .',
- 1 II- '
b 1 Mr. 1
N
1
0
0
0 1
0
n
1
I,
'
b
II
- :
S2 or c .
AIIOHHIANI fc.
n icnAi i-nffASA i ion I-IAI, i i .
I'l ICilHVCrPAS 121 h
fl JSIMNG h .
II lUtSHIDC PLAKI » .
PI liotolhc . IIKAIIO UFCAII rou
52 JROIltK >. .
c .
c .
P«l C .
htllRilAli SI OAVIIiH in 1&12I N .
il ICOAI HUH i r .
t'l ICHIISHCH N .
(1 istmciis K.
l:\ COAI 1 IRK INC HI. 1 'I .
.
l/l^l 11(1111211 ' .
I'l C .
il rroAi i if PLI .-. .
If ?iKUMi(l' 'i.
'lift r.h'J|ri<; INfpAIIiir, s?l.l KL'tn '. .
.li -.' UIIIHll 1 s .
: A | c .
II lfl><( IIPI-Ll .
II SliMKinillC S .
. .1 .
l i- -i.;.t ! " i i 'i-iv -ii" -. .
' ',,,, , ., . n.«H«»(.- tuAniii,' . .
Figure 7 '. Sample Edit Report
-------
7.4 Edit Job Control Language (JCL)
To execute the Edit Program, use the JCL shown in Figure 7-1.
A number of options are available with the Edit Program:
1. Card input on a "dummy" basis. This option enables the user to
see the Edit Report produced by his input transactions without
actually placing the transactions on the output MOD File. The
"dummy" mode is particularly useful if the user is expecting a
considerable number of errors which can be corrected and resub-
raitted prior to the update cycle. The user should remember that
no valid transactions on the Edit Report are passed to the update
when the dummy mode is being used. Use the JCL shown in
Figure 7-3.
2. Input from tape oc disk. Input from a disk file or a tape file
can be processed by the Edit just as easily as punchcard input.
Use the JCL shown in Figure 7-4.
3. Saving the Reject File. All fatal errors identified by the Edit
can be saved on a disk file for correction via WYLBUR, or they can
be printed out for re-coding. This optional file is an 80
character card image of the rejected input transactions. If the
Reject File is placed on a WYLBUR data set for corrections, the
corrected file can be resubmitted as input to the Edit. Use the
JCL shown in Figures 7-5 and 7-6.
4. Submitting Input via WYLBUR. If input data exists on a WYLBUR
data set, JCL can be added to the data set in order to run the
Edit. Use the procedures shown in Figure 7-7. This option should
be used only if the user is already familiar with basic JCL ir.u
WYLBUR concepts.
7.5 CDS Input Preparation via WYLBUR
WYLBUR is a powerful tool which can be used in conjunction with the CDS
retrieval to create input punch card formats for the CDS Edit. WYLBUR should
not be used to prepare punch cards for new facilities or highly changeable
data.
-71-
-------
I
-J
to
I
A\I KAMI: e
I-.-; wl.iii thi
1
/
I
-
/
/
1
7
*
/
/
-
/
t-
3
E
R
C
E
E
n
4
P
o
D
D
O
b
A
U
S
1
F
b
S
i
T
E
T
-
Vt
1
i
E
D
-
i
i
1
C
-
-
9
T
A
-
C
10
P
R
-
ir
II
R
D
-
s
1?
J
1
E
S
-
si
13
O
N
X
1
-
Oil
14
B
r
E
N
-
(i
15
C
-
b.
16
(
R
-
-
1
U
a
M
C
D
-
In
11
a
T
D
D
:c
19
a
r
S
-'
70
a
r
1
*
-
c
21
C
P
M
V
D
T
-
_
i
n
*r.
74
Y
f_
-
i
75
P
-
T
-
f
76
/
Y
-
ii
?;
M
P
-
c
71
i
-
E
-
r
79
i
:
n
30
i
-
\
a<
31
)
-
D
ti
3?
i
-
U
-
-Ill
33
V
M
(i
34
U
M
-
rl
35
S
-
Y
-
-
36
E
-/
-
-
3)
R
/
-
3i
-
39
1
-
-
40
D
-
-
41
/
-
-
...
4?
-
-
-
43
-
-
--
44
-
-
-
-------
AUTIIOIl
TKC
<;ilAM NAMF.
COS K.I)IT
TASK NUMnrn
tape Input Instead of pum li card InjniT to the CDS Edit
7
/
>;<
/
/
/
/
*
3
E
R
C
E
E
4
P
O
D
D
O
5
A
U
S
1
F
G
i
T
E
T
7
i
E
D
1
i
1
C
9
T
A
10
P
R
11
R
D
12
J
1
E
S
13
O
N
X
1
M
B
T
E
N
IS
C
16
(
R
D
17
a
M
C
D
18
a
T
D
19
a
T
5
D
D
V
20
a
r
1
S
C
O
21
C
P
N
B
L
??
D
T
-
-
73
S
n
X
(
S
n
Y
X
R
E
25
P
X
E
R
26
i
X
C
:
27
rv\
X
F
21
i
X
M
29
30
i
U
F
31
)
N
B
32
i
\
33
i
T
L
34
U
-
R
35
S
T
E
36
E
A
c
3)
R
P
L
31
E
1
39
1
6
8
40
D
2
o
41
/
-
42
D
B
43
1
L
44
S
1C
45
P
5
46
.
1
41
S
z
41
H
E
49
R
Z
50
-
y
51
y
52
-
y
53
y
54
-
y
55
)
56
-
5)
-
se
-
UJ
I
iii is the User's Initials
aaaa Is the User's Account Number
rr Is the User's Remote Number
n Is the User's Region Number or State Code;
valid values are 1-10, TN, SC, NE, etc.
xxxxxx Is the data set name of the tape file of
input card images
yyyyy Is the blocksize of the tape file data set;
it must be a multiple of 80.
zzzzzz Is the volume serial number of the tape.
Ficjino 7-4. Input from Tape
-------
i,;.;ula|- l-ltl I ill , 11,1-, Illr
2
/
'*
/
/
/
/
/
*
J
E
R
C
E
E
ii
E
Tl
4
P
o
D
D
D
PI
O
e
5
A
U
S
1
1
t
F
ab
6
i
T
E
T
T
: r
V
/
i
E
I)
.
B
in
s
1
R
C
.11
Wi
9
T
E
A
ti
C
10
P
J
R
on
ar
II
R
E
D
s
17
J
1
E
C
S
in
si
13
O
N
X
T
1
U
0»
Ii
T
E
N
i
,11
ib
C
D
>c
b
1C
(
R
D
p
;
i;
a
M
C
D
31
1<
18
a
T
D
D
D
D
D
eiJ
ce
19
a
r
S
S
1
C
1
21
n
r
1
N
S
B
5f
im
t
i
;
C
p
p
-
:d
t
» ,
r
c
;
(
ai
.»
i ]
s
n
N
(
R
el
er
H
Y
,
N
E
y
J
25
P
E
E
C
if
f
26
i
P
i/V
F
e
cl
?)
M
A
M
i
c
21
i
i
K
-
it
CI
?9
i
E
F
a
an
30
i
i
E
0
10
a
II
)
,
P
e
C
V
i
a
)
L
Ji
01
3J
i
a
R
L
d
34
U
a
S
E
:a
JC
35
S
a
P
C
d
36
t
.
A
L
3;
R
E
C
:
38
R
E
8
39
1
R
;
O
,0
D
O
(
41
1
R
T
D
42
S
R
L
43
K
K
44
U
s
45
N
(
1
4G
1
2
Z
47
T
1
E
41
:
2
:
49
D
)
3
y\
\
)
1
SI
S
l
2
52
K
O
S3
i
)
i4
55
56
5)
SB
Where:
iii is the User's Initials
aaaa Is the User's Account Number
rr Is the User's Remote Number
n Is the User's Region Number or State Code;
Valid Values are 1-10, TN, SC, NE, etc.
Figure 7-5. Saving the Reject File
-------
1 AUTIIOIl TRC
I'IIIK;IIAM NAMI: CDS run-
TASK NUMDEIl
1 Prlntlor I In- optlnii.il IllillXT 111.- .luring .1 ri:|;nUr F.,11 t run.
I
'L
L
L
L
7
/
I
-t
l_
/
/
*
3
E
R
C
E
E
In
E
Tl
4
P
o
D
D
D,
XI
O
e
5
A
U
S
1
1
-
F
b
6
i
T
E
T
T
I .
Vi
1
i
E
D
t:
1
1
i
-
1
R
C
1C
ut
$
-
T
E
A
,
C
10
P
J
R
n
r>
M
R
E
D
c;
a
1?
J
1
E
C
S
.t
-
si
n
O
N
X
T
1
Mi
14
B
T
E
N
h
cl
15
-
C
D
n
in
16
(
R
D
D
j
i
I)
a
M
C
D
>e
a
11
Q
T
D
S
_E
e
19
a
r
S
Y
*
a.
.
20
a
r
\
S
e.
t
21
C
P
o
1
tl
n
0
T
U
23
S
-
n
T
>i
n
24
Y
^
a
25
P
A
e
-
f
26
/
*-
y
-
tl
?l
M
D
if
e
21
i
C
e
r
29
i
B
n
30
i
-
in
ai
31
)
B
i
1 1
32
/
L
)O
on
33
I
K
'U
(i
34
U
S
J(
cl
35
S
1
L
3E
E
Z
c ,
31
R
E
r,l
31
-
;
19
1
8
40
D
0
41
/
42
-
-
43
-
44
45
-
46
-
4;
-
41
49
SO
-
51
-
5?
51
54
55
-
56
-
-
5)
-
51
-
-
c_n
I
iii Is the User's Initials
aaaa Is the User's Account Number
rr I:, the User's Remote Number
n Is the User's Key ion Number or State Code;
V.i I id Values are .1-10, TN, SC, NK, etc.
-------
,:,>,, .,/,, in
i:n.i:,.Min
1 .
> t
1.
/i.
5.
CO. II IA, III
<:O:I;IA;:I>
fli).
')| .
'12.
Jl.
or i:i\; m
ilikuiAim
COnillilll
CO.IilA'lil
'».
Jl.
92.
11.
cmnAMii
OmilAI.II
HI.
01.
')!.
Ji.
<:m,iAui>
1:011 IAIIII
)o.
>l.
'ti.
9.1.
COIIIIAIIII
COII.IA.IIl
'JO.
01 .
92.
91.
OIII:I.\:MI
0. I
0.2
0.1
0.4
0. 5
,1.1,
l.'Olil IAIIII
0. 1
II. .
II. \
U.4
0. 5
'III.
Jl.
'».!.
Jl.
CII..IIAIIII
1 III I:. V
/
7
7
7
7
7
7
7
7
V
7
7
7
7
7
?
7
7
7
7
7
7
7
(.:! 1426 .:lr
II:.
11:1.11.51.1011 I76A iiAi:tn[T: IIM i:^i:i'\i:,,i <ri5 rr.\i:xcii5 runr.n
1 1 //i.i'Ai:x(:i:5 .inn <,vi2i.i:ii:;Yi',,i. . .
l.'l li.lt '05' 2/1 III .ill
Ihi
05 14 15/ni 00/15 011.1
05 14 1540 01 mo on,)
05 14 1540 O.M24 mio
05 14 I60O 1)0001 oOii
H^I Idnc.tli-HO
^.:t turulllill iildlli-112
t:li * ' Co * ' in nl 1 nol
II:,
O5I4I54O007I 50DU
O5I4I54OI)|01')O(M)
051 41 54002124000
0 51 4 lf> 0001 1001(100
ch 110 to 'c' In nl 1 nol
llu
05141 5400O7I 500(1
051 41 54001 OT)O(H)
05141 54002124001)
05I4I6OOUOOOIUOO
r.h 5O/6II to ','leclrlcul uurvlcuo' In all nol
llu
051415400071 SIMM)
D5I4I y.OOIOVIooo
05141 54 0021 2400O
oil ', ir.ooooooiniio
ch 17/19 to '01)5' In nil nol
llu
0 51 4 1540O07 15000005
051 41 54 OOI01ni)()OlK)5
05I4I54002I24000II05
D5i4ir.oiiooooio(iix>n5
C.ll .1
//i:|i.iuxi:lS J,,h (n02riciliiyi>.i,ii!xi:),'lii|iut rcu 5'
/route |>rlnt r!7
/r.nll C.I05.UXC
//.:.llt CX..-C , ,lol|-l 5,ty|K.--',l.i,an,y,' ,|.ario-'05tr'
//IMT'lulll J.l '
Ihi
//..f.;ii;xc-|5 Jnli (;iOJ6L-,l:iyp.i:,.!x.r) , ' hipnl r,.,; 5'
/''[.Mile print il/
/'cull c.lu5,i:xc
//u.lH uxuc r.liil|ilS.ty|K. '.liun.iy1' .|iarii-"05tr'
//,:.,r,h;li, .1,1 *
il'il 41 54OOO7I 'in, 1(1005
O5I '.1 54OOI01'ioi 1111105
051 ',1 5'iOO2l2',0(n KI.I5
U5I 4l(,OIIOOIlOIOOiMIO5
run nun
.inn .ioi! uiiiiiiKii. Figure 7-7.
( n i:' - I.I..A:;:: v
I.I/II/.M Al Hii:l1: 57.
I.I.CCTKICAL SERVICES
I I.I-CTIIICAI. SKIIVICKS
I I.KCTIMCAL SKIIVICKS
I I KCTIIICAI. SEHVICKS
I irCTIUCAI. SKHVICtS
MCCTIIICAI. SKKVICES
I I.CCTHICAL SCKVICKS
M.I.CTIIICAL SKKVICKS
i i I i IKICAI !jl'.l(VICI'S
11 I:I:HIICAI. si IIVICKN
11 KCIIIICAI. SI;KVICI:S
i 11 ,:IK|(:AI. SKKVICI'.S
Retriev^
Sample WYLBUR Session to Convert
Output into Input to CDS Edit
-------
When a uniform add, change or delete must be made to one particular CDS
punch card type, users should consider using WYLBUR rather than ordinary cod-
ing sheets. If the selection logic of the CDS retrieval can be used to ex-
tract those CDS raasterfile records which must be changed, WYLBUR can be used
to create the desired input.
Examples of successful WYLBUR applications are:
Create a new action record with the same action type and date
scheduled for all NSPS facilities.
» Generate a new action for all actions which have been rescheduled
within a certain time.
» Delete all actions which have been scheduled and performed prior
to January 1, 1981.
9 Change the Compliance Status for all sources which meet certain
retrieval selection criteria.
» Change a Regional Data Element for sources which meet certain
retrieval selection criteria.
Change the AQCR for all facilities within certain counties.
The following checklist gives some of the advantages and disadvantages of
usiriq rt'YlBUtt for input data preparation:
Advantages
Saves input data preparation
coding time for uniform
changes.
Provides "instant input"
with no need to wait for
keypunching.
WYLBUR commands, especially
the change command, are
powerful tools for data
manipulation.
Disadvantages
Input data must be retrievable
from the CDS raasterfile.
WYLBUR sessions cost about $30 an
hour; this is much more than
either coding or keypunching costs
for variable data.
Users must possess basic WYLBUR
knowledge to perform needed data
manipulation tasks.
-77-
-------
The following steps outline how WYLBUR might be used to perform any of the
above tasks:
1) Formulate the Retrieval Selection Cards which will create a Quick
Look Report which can then be manipulated and converted into input
punch card formats. The 40 Card used for Printline formatting
should contain NOHD, REGN, STTE, CNTY, SRCE and any other applica-
ble data elements which will be needed for each input transaction.
2) If the Retrieval is submitted via punch cards, a special JCL card
must be added after the Job card to make it possible to fetch the
retrieval output via WYLBUR:
/ROUTE PRINT FETCH
Card
Column 1 10 16
If the user creates the retrieval via WYLBUR, he should submit the
following command:
? RUN FETCH
This command will enable the user to manipulate the output from
the retrieval. Users must note the job identifier of the job
which will be retrieved by WYLBUR. Be sure to save your job num-
ber as it will be used to fetch the job into your workspace on
WYLBUR.
As an aid in converting Retrieval output into CDS input trans-
actions, users are urged to create the following two data sets on
tneir WYLBUR source libraries:
ij Input JCL. The JCL described in Figure 7-1 should be saved as
a data set. For the example used here, TRC used a data set
called IPT4JCL.
b) Retrieval JCL. The JCL described in Figure 7-8 should be saved
as a data set. For the example useo here, TRC saved a data set
called RTV4JCL.
7.6 CDS/WYLBUR Example
Region IV wished to place the letter "M" in Regional Data Element 3 for
each of its major sources. Instead of coding this character for each of its
4685 major sources, they used WYLBUR to create one transaction Card-1 for each
facility. They did this by using the following steps:
-78-
-------
COMMAND ? collect 1.1
1.1 ? //epaexc job (a026CDSYP,mexc),'cdsrtv reg4*
1.2 ? /*cntl cds4,exc
1.3 ? //rtv4 exec cdsrtv4
1.4 ? //sysOOS dd *
1.5 ? 01 04 major sip facilities in region iv
1.6 ? 10 aped 1 2
1.7 ? 10 ecat a 2
1.8 ? 10 ecat a 3
1.9 ? 10 ptno m 000
2.0 ? 20 ql
2.1 ? 40 nohd regn stte cnty srce ptno
2.2 ? //
2.3 ? *** (break)
COMMAND ? lis
1.1\ //EPAEXC JOB (A026CDSYP,MEXC),'CDSRTV REG4 '
1.2 /*CNTL CDS4,EXC
1.3 //RTV4 EXEC CDSRTV4
1.4 //SYS005 DD *
1.5 01 04 MAJOR SIP FACILITIES IN REGION IV
1.6 10 APCD 1 2
1.7 10 ECAT A 2
1.8 10 ECAT A 3
1 .9 10 PTNO M 000
2.0 20 QL
2.1 40 NOHD REGN STTE CNTY SRCE PTNO
2.2 //
JwMMrtND ? run unn fa ten
743 IS YOUR JOB NUMBER
COMMAND ? loc 743
JOB 743 EPAEXC AWAITING EXECUTION A ANY
FIGURE 7-8. Retrieval JCL for Edit Input
-79-
-------
1) Formulated the following Retrieval selection cards:
01 04 Major SIP Facilities in Region IV.
10 APCD L 2
10 ECAT A 2
10 ECAT A 3
10 PTNO M 000
20 QL
40 NOHD REGN STTE CNTY SRCE PTNO
2) Submitted this retrieval with the following command:
? RUN UNN FETCH
3) Waited until the job had executed. Recorded the job ID number
carefully since this information was necessary to retrieve the
remote output for WYLBUR manipulation. The job ID for tr.io
retrieval was '743*.
4) Used the following WYLBUR commands to create input punch c^rc
transactions for processing by the CDS Edit:
a) Sign on according to the proper NCC conventions.
b) Fetch 743
This command retrieves the output of job ID 743 and allows
users to load the output into Working Storage.
c) LIST OFFLINE DEST RMT37 UNN CC .
This command lists the Retrieval output on the high speed
printer at Remote 37. Users should route their output to trss.-*
own remote nuine^r. If users are noc 3ure or vr,.:: .:.:: .; . ..:
retrieved, they should consult this printout before proceeding
further.
d) DELETE NOT '04' 3/4 IN ALL
This command deletes each Quick Look print line wnich ^ce3 :I.T:
contain Region Code in columns 3-4. With one command, all
heading lines are eliminated.
e) SET LENGTH=80
f) SET TERMINAL WIDTH=132
g) CHANGE ' ' TO " IN ALL NOLIST
Eliminate all embedded spaces between Region, State, County,
Source and Point numbers. Columns 1-16 of each punch card are
now ready.
-80-
-------
h) LIST
Check out what is in Working Storage.
i) CHANGE 80/80 TO 'C1 IN ALL NOLIST
Generates "C" in column 80, update code.
j) LIST
Check out what is in Working Storage.
k) CHANGE 69/69 to 'M1 IN ALL NOLIST
Generates a "M" in column 69, RDE3.
1) CHANGE 17/19 TO '001' IN ALL NOLIST
Creates card columns 17-19.
m) COPY ALL TO .001 BY .001 FROM IPT10JCL
Copies the data set IPT10LCL into Working Storage starting at
sequence number .001 and incrementing the copied file by .001.
Creates the run JCL for this file.
n) LIST
Check out what is in Working Storage.
o) RUN UNN
Submit the job for processing by the CDS Edit.
p) LOGOFF
Sign off after all WYLBUR session is complete.
Figure 7-7 shows a sample WYLBUR session used to convert Retrieval output
into input to the CDS Edit.
-81-
-------
8.0 UPDATE PROCESSING
The update cycle consists of a series of programs which apply input trans-
actions to the Masterfile. All input transactions which contain no fatal
errors are stored on the MOD File by each run of the Edit program. During the
update cycle, all transactions placed on the MOD File since the last update
cycle are applied to the Masterfile by the Update Program. The update cycle
is usually scheduled by the national DEC to run on Wednesday nights.
8.1 Update Program Description
Prior to the Update Program, all input transactions from the MOD File are
sorted into the same sequence as the Masterfile. The output Masterfile from
the previous update cycle becomes the input Masterfile to the current cycle.
The Update applies input transactions to the Masterfile to produce a new ver-
sion of the Masterfile as output. There are three major logic paths in the
Update depending on the Update Code present on the transaction.
To add a new record to the Masterfile, the Update performs the following
steps:
1. The records on the input Masterfile are copied to the output
Masterfile until an input Masterfile record is found with a record
identifier (Region, State, County, Source, Point and Action Num-
bers) equal to or greater than the record identifier on the new
transaction.
2. If an input Masterfile record already exists for that record iden-
tifier, the input transaction is rejected since the Update cannot
perform the add logic.
3. If an input Masterfile record does not exist for that record iden-
tifier, the transaction is formatted into an output Masterfile
record.
-82-
-------
To change an existing record on the Masterfile, the Update performs the
following steps:
1. The records on the input Masterfile are copied to the output
Masterfile until the record identifier on the input Masterfile is
equal to or greater than the record identifier on the change
transaction.
2. If there is an input Masterfile record with the same record iden-
tifier as the input transaction, the data on the transaction is
applied to the input Masterfile. After all multiple change trans-
actions have been applied to the input Masterfile record, it is
then placed on the output Masterfile.
3. If there is no input Masterfile record with the same record iden-
tifier as the input transaction, the change transaction is
rejected. Special logic has been developed to allow users to
create a new Masterfile record with a Card 3 change transaction to
a vo i ! re j ec 1 3 .
To delete ar. existing record from the Masterfile, the Update performs the
following steps:
1. The records on the input Masterfile are copied to the output
Masterfile until the record identifier on the input Masterfile is
equal to or qreatsr than the record identifier on the delate
transaction.
2. If there is no input Masterfile record with the same record iden-
'.',"'. --- - - :.-.= l~p-:^ transaction, the delete cr^n::act-o:'- . :
r e "
3. For a comment delete, the input Masterfile record which matches
the record identifier of the input transaction is not copied to
the output Masterfile.
4. For aii action delete, input Masterfile records with the same
Region, State, County, Source, Point and Action numbers as the
delete transaction are not copied to the output Masterfile.
5. For an emission point delete, input Masterfile records with the
same Region, State, County, Source and Point numbers as the delete
transaction are not copied to the output M
6. For a facility delete, input Masterfile records with the same
Region, State, County and Source numbers as the delete transaction
are not copied to the output Masterfile.
-83-
-------
The Update will reject input transactions under the following conditions:
Because of the Masterfile hierarchy, an action cannot be added to
the Masterfile without a corresponding emission point, nor can an
emission point be added to the Masterfile without a corresponding
source record. Comments cannot be added without their correspond-
ing source, point or action records.
A delete and a change transaction for the same record identifier
cannot be applied to the Masterfile during the same update cycle.
The change transaction will be rejected.
In addition to applying adds, changes and deletes to the Masterfile, the
Update also performs a table lookup on all personnel codes on the Masterfile.
No change transactions need to be coded to change personnel names on the CDS
Masterfile. Whenever a name associated with a personnel code is changed by
the national D8C, the personnel name and the associated table for that per-
sonnel code will be placed by the update cycle onto the CDS masterfile. This
will be accomplished for personnel at both source and action levels. Refer to
Section 10.1.2 for a full description of the personnel code processing.
Regional users should call the national DBC to add, change or delete en-
tries on personnel tables.
8.2 Update Scheduling
The scheduling and maintenance of the update cycle is the responsibility
of the national DBC. Once a week, on Wednesday night, the valid transactions
on the MOD File are applied to the CDS Masterfile by the Update Program. The
Update is scheduled for approximately 10:00 p.m. Because of this schedule, it
is important for users to have all of their weekly input ready for keypunching
on or before Tuesday noon.
If a sufficiently large number of regional users request an additional
update, a special update run will be scheduled. When holidays prevent a
-84-
-------
Wednesday night update cycle or when a special update cycle is scheduled, the
national DBC will inform all CDS users of the change.
On Thursday mornings and all mornings following an update cycle, an Update
Report will be routed to each region by the DBC. If the report is not avail-
able by noon, users should verify that the update cycle has run successfully
by examining the Update Status Log described in Section 8.5, and then users
should obtain their Update Reports by using the JCL described in Section 8.6.
3.2 Update Report
The Update Program produces an Update Report which is stored on a regional
file. If the user had transactions which were entered into the update cycle
normally, the national DBC will run the Update Report for each user. However,
if the report is not available by 12 noon following an update, then the user
must request his Update Report by submitting the Update Report Job Control
described in Figure 8-1. This must be done prior to the next update cycle.
As soon as the next update cycle is run, the previous week's report is no
looqor on the disk file. A new report replaces the previous week's report on
the disk file. TRC keeps copies of weekly Update Reports on its files; hew-
ever, the user should keep his own file of weekly Update Reports.
The Update Report has one print line for each transaction sent to the
Update Program by the Edit Program. Next to each transaction on the report,
there is an Update Action column which shows that the transaction was either
added, changed, deleted or rejected from the CDS Masterfile. If the trans-
action was rejected, there will also be an error message explaining why the
transaction could not be added, changed or deleted.
-85-
-------
AIITIIOII TRC
JCL for obtnlnlng Ihv
1 i
/ +
/ 7
77
/*
J 4
E P
no
CD
E O
--
J
A
U
S
F
-
-
1
i
T
R
-
-
-
I 1
i i
E
PT
-
I
-
10
P
-
n
R
-
1)
J
1
E
w
1)
O
N
X
-
e
14
B
T
E
e:
It
C
It
(
R
-
iii
aaaa
rr
n
-
-
-
-
n
a
M
C
-
I'llWHAM I4AME tl)s »'-K''-"
1 llpdnte R.-|Kill
TASK
NUMDKII
1)
ATE
of
COS Update Rr|irnt (or a given legl »
II
U
T
D
11
a
r
S
n
a
r
R
n
C
P
n
D
T
n
S
n
14
Y
»
P
H
,
11
VI
II
i
n
i
a
t
it
)
H
,
11 n
i
i i
Is the User's Initia .
Is the User's Account
Is the User's Remote-
Is the User's Region
Valid Values are 1-10
-
-
_
15
S
Jt
E
n
R
it
)i
1
W
D
41
'
41
S
Number
Number
Number or
, TN, SC,
-
-
-
-
-
-
4J
44
(i
U
4>
41
41
50
SI
5?
n
State Code;
ND, etc.
-
--
-
14
-
-
-
~
-
»
-
M
-
-
-
-
-
S
-
-
-
11
-
-
il iO
l(? U
(4
-
-
(S
-
M
-
-
-
J
-
11
-
-
-
(I
-
-
-
-
-
(0
-
-
-
-
-
n
-
-
-
-
-
-
u
;
-
-
-
CAIII)
HUMIIP.H
1)
-
-
-
-
-
-
-
14
-
-
-
-
-
15
-
-
-
-
-
-
It
-
-
-
-
-
-
-
JI
-
-
-
-
-
-
-
-
II
-
-
-
-
-
-
-
-
Ji
-
-
-
-
-
-
-
-
10
-
-
-
-
-
I
03
cn
i
i (jure
CDS
-------
All errors appearing on the Update Report should be corrected, coded and
then resubmitted to CDS via the Edit Program.
A sample Update Report is shown in Figure 8-2. The title, region number
and output serial numbers are recorded at the top of the report. Column head-
ings are listed across the top of the page. Update Action is located on the
right side of the page with an accompanying message if the transaction is
rejected. Update error messages are listed in Table 8-1. The origin of the
input transaction is shown in the far right hand column. These include:
(blank) The transaction was entered by the
regional office or by an authorized
representative of the region.
HQ The transaction was entered by EPA
Headquarters.
GN The transaction was generated by the
EDIT Program for further processing in
the Update.
SC, TN, NE A State code is placed in this column
if a State entered the data into CDS.
TR TRC
JE Geomet
8.4 Update Report Messages
On the Update Report, the Update Action column indicates the action taken
by the Update Program on each transaction passed by the Edit. The normal
Update Action message is ADDED, CHANGED, OR DELETED. An ampersand next to the
word CHANGED indicates that the Update has applied multiple changes to the
same wasterfile record in chronological order.
The word REJECT in the Update Action column indicates that the Update
Program could not perform the appropriate add, change or delete indicated by
the transaction's Update Code. For each rejected transaction there is a
-87-
-------
it w run i
I1 1 1 D 1 / 8 ."'
o 1 A If
( our
u
31
IH
1 H
1 B
IB
1 R
1 8
1 l<
IH
1 R
III
IH
1 6.
i n
1 R
IB
1 R
1 '«
l» IH
?
IR
1 II
If)
IH
ie
I h
i n
in
1 H
IH
i -i
1 R
IH
IH
IH
IH
11
1 8
1 H
1 1
1 l<
i e
\ H
1 n
III
1 II
1 H
cult
C01E
5f,7R
0200
0200
02110
1340
0341*
0340
0340
0340
0340
034U
0340
0310
0340
0400
0400
0100
Od JO
0620
9620
Ofc?0
0 740
074Q
3 740
I 210
1210
1 210
1 240
1240
1 2'<0
1 210
I'j40
IS'lO
I5'i0
1540
1540
i rn n
1 5'< 1
1510
1 ')10
I f,«0
1 Ij4 0
11.10
11,1 1
H. 'i n
i (.'HI
I f, i n
SnllRCf
coat
« n i 2 3
00040
00041
M>0 1 0
(1 0 0 7 H
0 0 0 / 9
OOGH1
l.OOO'J
(. n o o i
(.1)079
nno /i
'<00 79
4no»i
'lOUbl
110004
10309
09010
modi
uco oil
OD033
°0033
(1001 '
frooo i
900U
GP01 0
0(1060
00124
(.0010
"0010
901 12
90124
000 1 H
C 0 1) 1 H
r o o i H
00021.
OOU2R
i.auj i
' 00211
I.002M
710UI
': o 0 I f.
00030
r o o 3 7
l'l'34'j
c n o h J
(illll I. 7
i ' 3 n
EH
PI
ooo
000
OGO
ooo
ooo
01 0
000
0110
000
O'JO
Ol'fl
000
ooo
ono
0 111
000
000
ooo
ooo
Ono
O'JO
Ouu
0 jO
000
ooo
ooo
0 JO
000
uco
OOb
POO
Obd
ooo
uco
OHO
QUO
QUO
ncu
POO
Ul 0
DC 0
Oui'l
U 'i '1
01 II
1110
0: o
ATI CARD
NO CODE
?
ll\ 1 01?.','
I'O 3
" '! 3
no 3
00 3
ro \
an 3
no 2
CO 3
TO 3
no 1
"0 3
CO 3
00 3
(10 3
"0 3
ni) 3
00 ?
ni 3
ro 3
10 3
C3 3
MI ;
" 0 3
OU 3
"0 2
ra 3
?0 3
on 3
on 3
on :
no i
I'C 2
'-(. 3
(; 0 3
I'O 3
' ii 2
I' 0 5
'" 3
(.11 2
' 0 '
"n
'(1 i
'"1 .'
" II 3
'' .1 .'
' ':
CIIHI'L lAfJCt' D«1A StSILI
KfNIIi.'-l IIA1A K'll HtC. |(IN 4 - AILANIA
ouirui st.RKl. ii5f>7R9
n
p
A2
R
n
B
204B
A?
B
HI CHART! H. JOHNSON
B
n
B
B
B
A?
3251
B
0
(1
A2
A2
A2
D
0000
9
B
B
B
n
IND. SUPPLY HOiliE
3215
B
II
p
51S1
II
n
51 S 1
II
H
H
J
II
II
n
Ui'DI
COIlf
n
0
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
I
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
I
c
c
c
c
f
c
I'AGE 2
UI'DAIE EmOH
ACIIOKI MESSAGE
& = MULTIPLE CHANGE CHIG
CHANGED
CHANGED
CHANGED
CHANSED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGCD
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHAN3ED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANSED
C-IAN3i3
CHANGED
CHANGED
C'fANGSO
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
ciiANjEn
CM Ann CD
CHANGE 0
riiAnr.r o
Figure ti-2. 'Jample Ifpdate Report
-------
TABLE 8-1
UPDATE ERROR MESSAGES
Update Error Message
Explanation
SOURCE NOT ON FILE
POINT NOT ON FILE
ACT NUM NOT ON FILE
NEW 2 INVALID
DUPLICATE TRANS
NOT ON FILE
ALREADY ON MF
Cards 2 through 8 cannot De added to the Master file
with an Update Code "N" unless the Card 1 has been
added as new during this update cycle or during a
previous update cycle. Make sure that the source
exists on the Masterfile; verify that the correct
State, County and Source Number is being used on the
transaction.
Cards 6 through 8 cannot be added to the Masterfile
with an Update Code "N" unless there is a corres-
ponding Card 5 on the Masterfile. Make sure that
the emission point is being added as new or has
already been added as new when emission comment or
action information is being added to the Masterfile.
An action comment Card 8 cannot be added to the
Masterfile unless a corresponding action (Card 7)
already exists on the Masterfile.
Card 2 can be added to the Masterfile as new only
during the same update cycle as the Card 1 is added
as new. Once- the source exists on the Masterfile,
use an Update Code "C" to change the data elements
found on the Card 2.
If two or more transactions with the same Region,
State, County, Source, Point ana Action numbers have
an Update Code "N" the first transaction is added to
the Masterfile; and the second and subsequent trans-
actions are rejected with this message. A change
transaction following a new transaction for the same
Record ID is rejected. Duplicate delete trans-
actions are also rejected.
The Update cannot apply a change transaction or a
delete transaction against a non-existent Masterfile
record. Verify the State, County, Source, Point and
Action numbers being used on the transaction.
A transaction with an Update Code "N" cannot be
added to the Masterfile if a Masterfile record
already exists with the same Region, State, County,
Source, Point and Action numbers. Also a new com-
ment cannot be added if a comment with the same
record identifier and line number already exists on
the Masterfile.
-89-
-------
TABLE 8-1 (Continued)
UPDATE ERROR MESSAGES
Update Error Message
Explanation
98 ON MF
&(AMPERSAND)
32 REJ
ATPE WRONG FOR PLTY
When the next sequential action number is not known
on the Masterfile, action number 99 can be coded;
the Update will convert the 99 to the next highest
sequential action number. To prevent the Masterfile
from going out of sequence, no action number over 98
will be added to the Masterfile.
When an ampersand appears in the Error Message
column of the Update Report, it indicates the pre-
sence of a multiple change transaction to the
Masterfile. This is not an error message; it is
only a warning that multiple changes have been
applied to the Masterfile in chronological order.
If one or more sets of pollutant compliance data
cannot be added to the Masterfile because there are
already 10 sets of pollutant compliance data on the
Masterfile, a reject message is issued for each of
the rejected pollutants. The Pollutant Code
together with the letters "REJ" is printed in the
Error Message column. Since the Card 3 has room for
three sets of pollutant compliance data, up to three
different reject messages may exist on one line.
On a change transaction. Penalty amount can be
entered only for certain action types such as zl,
Z2, Z3, etc.
-90-
-------
diagnostic error message printed out. Table 8-1 lists all of the errors iden-
tified by the Update. An explanation of the corrective procedures for each
update error message is also given in this table.
8.5 Update Status Log
The Update Program produces an Update Status Log which shows the most
recent successful run of the update cycle. This log is available to those
users having access to a WYLBUR computer terminal. This Update Log shows the
date, the time and the output serial number of the most recent update cycle.
The log shows which regions participated in the Update. In addition, it also
shows the number of transactions input to the Update and the number of trans-
actions accepted and rejected by the Update for each region.
To obtain the log, perform the following steps:
1; Follow the standard NCC sign-on procedures by typing in the user
account, initials, keyword and terminal identifier. .
2. As scon as WYLBUR gives the prompt, COMMAND?, type in the follow-
ing and then hit the carriage return:
USE $CN.EPAEXC.A026.CDS.SYSOUT
LIST
3. Figure 8-3 shows the contents of the log produced by following the
above steps.
8.6 Update Report Job Control Language
The user may wish to request his region's Update Report for each update
cycle for which the region had input data. To execute the program which pro-
duces the Update Report, use the JCL shown in Figure 8-1. This JCL should be
submitted immediately after each update cycle for which the user had input.
Normally, the user should submit this JCL on Thursday morning and on mornings
following special update cycles.
-91-
-------
PL t 'V.I ITI'I Y.'iJl. II.I-: li. .'.L I'M 'll« Iff"
i Lt a ,i li'. I' : P': F I'M ;iv i 11 I- i
I'lH I ' I ' I I '''I
( 1)11 ' I j."' 'JK ' lo
; i ;. i i. i. )
"i.o I.YLI.UK ' . . AT Fi'i Tfr-'iir.i i T r. "'. Mh:-ir:r.S MN/'T/IV
MSu'l I ) .' ' r All o
i /.£',U'(!> ( tin' I/ r w» I ?F A 5 SU.il iir,'.,0!,(,r.' T>
CL nil'i? : :ipf.r').. Y I
: i M/I n« ? t.i,'...i
;L-/ './.?: Lisii'.'r. '.LL Nfc-i .1 iFsir" SEE
li/i?/1-:-: ''m I'l'TUN '-MI M'i-pu»if!' ui.rtv ins UYLF-UI< SLE NE'Vf AIE^T*,
;J/|D/'-.-: "YL :IPK (. citti' 'JIT i T I CM UfPeifr SEE NEWS Al(RT7
f H.I.- '.:nr>. A . ,j'j| K '.oi fin raiin ~ Livris P.K
''I. fl'JCII" A'" .-'"IIV '(''pT iir' f S I L'" ° I f VC L 5 OK
(O'ir'.'.Mi ' iir.i it I..FT ' xr .'.o;'i.. ci"~. :'-v'.f-uT
i. r n. j i VAI.IT h.' i: i'
:'. '..jj'. 'j^.'T'- TO-.[ ro: ^insTfi1 Fur '.JTPIM SCKI'L o:ofc?r UN IP/ID/SI
i.
'> Mi'D^T1 K^.'fiM i'|. I .[-I. IIM . F(i^ ^EGlOfl r.li 001/1 R( (i>K!S I^^UI = CC171 ACCrpTFO r OOlf.i RFJECTEP = 000(16
li .
7. iHO^Ii IM' "Ot- I I'M I-MM1: hfl t.r.G|!)n T= OPc" RTI.KFS I N * J T = 002^3 «C C f P TI P = T02M REJECTED = OOOP?
(- f
i'i'3.ii; i'!(! i 11.1 n-Limc FUI. H:I',M'. r.j= o::.1/ Rfrji RFJECTEP = oooot
i o.
ii- uij»ii ": : 01-1 11-1 i-L r*i :. M)I-
-------
If the user does not submit this JCL prior to the next update cycle, the
information from the update run is overlaid by the next update cycle's Update
Repor t.
The Update Report provides the only audit trail of all transactions placed
on the CDS Master file; therefore, it is important to keep this report on file
so that errors can be researched and corrected.
8.7 Critical Data Elements Report
To aid the CDS user in the update verification process, CDS produces the
Critical Data Element Report during each update cycle. This report is
designed to highlight significant changes in a few data elements and contains
one line of data for each source that has had a critical transaction applied
to it. Data elements included in the report are Source Name, Air Program
Code, Source Compliance Status, Source Classification, Source Emission Cate-
gory, Significant Violator Flag, Action Type and Date Scheduled. The origin
of each transaction is presented at the end of each line. Figure 8-4 is an
example of a Critical Data Element Report.
-93-
-------
/:'./'. i cimi'i. i A;I
'i » 'it- -".o onn '> I
.', ' nun nun I S
/, ' | :>no nun I 1
/, ' i -.IHI ni'ii id
', | '(in nim:':!
t, > i inn oon 1 '1
'i > ' 1 1, do nnpn/i
/, ? | (. -:n non Vt
'. :; IP.M) nun if.
iil.n soni!
tll'STVACn
I-TIIF.KAI.
mii'iiHT.r.
STKVIJHB.
HM. CAKII I
STKVEM.'i.
lir.lilllTAC
!i PI! I NCS
AI'Cli SCtlS CI.AS Si:C7 S>T 1. AI'Ti: I1TAC
<'.!' IIAMF I.T.W SOIIKCK I.'AIII O 11 n N n I' (I 1: ill 1) 'II. U <'.>' nl'.l CMC;
: n 1.1:01:11 1:11 nv A1 u
.'incill, A 1 ii
1 : I'MIIIF.MCI-: II All?
.H'-rARiT.i: ii AI
IT. : coin' .nv . i n A11
.II'-TAYI.OI(S.12 Al II *
i: COTTON mi. ii
I NP: IIIIITIUS ' I ?
CAROLINA FORF. ST I MO (1 0 Al 1
IT AN nnii'sr.Y I.MIHIKK n o n . \
siMinrrrn uv
I!C ST ll'l IIT
<
*
.::.
t;
f:
ft
r.n
I'll
* I:M
* <:ii
I /, i "(iii iinn 17 ii'HiAKF. n cnilPAr'Y
vO
i /, I'lno (inn us c 1.1 in-: iron «, r.Ti:i:i.
', i"no (KIM -\n cm,nun i A Ni:iisi'Ari:i!S
'.;' | "(id lino'il III.VTIIF. I NliHSTR I I'.S
/. I "iin "no/it III.YTIIi: lliiii'STKI rs no A°
'. ' >i'(.'i onoo7 Ki iii'SToni: r.Tr. 1:1, rr.oo si'AiiTi.'iiRr HTI:F.I "iton
/. ' MK.O l|i|l\7'i II Ml 1)11 CAIII' rlllll.T IKAI.I. I! 'II O;i C. All : CAM l'CI:u FT
'. ' ",'ill OIKiO'' PIIAI!!! YAK'IS A I A ~"
''' '", 'ill O(Kl/i'i TI'AYIIOK Clli:ilIOAI CO. I I
8--'i. Sanipli' i:riLii.:al li.it.a !'101110111 Keport
-------
9.0 RETRIEVAL PROCESSING
The CDS Retrieval is used to prepare management reports based on informa-
tion on the Masterfile. The Retrieval has been developed to provide a great
deal of flexibility to users in selecting and formatting management reports.
Data can be formatted, sequenced and selected based on criteria developed to
meet specific needs.
All output reports other than the Edit Report and the Update Report are
produced on request from the CDS Retrieval Program. Requests for management
reports may be made at any time since they are processed independently of ths
update cycle. The Retrieval provides users with the capability of seein^1 ';hat
data is on the Masterfile in a format that meets the user's needs.
To obtain reports from the Retrieval Program, the user must carefully pre-
pare a Retrieval request form and submit this form to have the selection cards
keypunched.. The keypunched selection cards and appropriate JCL cards ace used
to run the Retrieval. The user submits this input to the central computer
site via a terminal or by WYLBUR. CXitput from the Retrieval Program consists
of a Retrieval Edit Report and the management reports requested by th-= user.
The Retrieval Program provides the following features:
* Quick Turnaround - The package operates on a "demand" basis and
will usually provide overnight or faster turnaround, depending on
the backlog of work at the computer center. In many cases, re-
quests requiring less than 20,000 lines of printout can be ;r,et
within 1 hour.
Improved Selectivity - Information can be selected from the
Masterfile to meet the specific needs of the user so that smaller,
more oertinent reports can be prepared. For example.- if che ijsor
needs to have a list of point source facilities within a state or
AQCR, he could get a Quick Look Report which shows only these
facilities and the particular information he wants to know (Name,
Size, Compliance Status, etc.) on a single line.
-95-
-------
Selection Logic - Each user can select from his entire Regional
Masterfile only that data which is of interest to him for his par-
ticular needs. The user can select data based on the presence or
absence of information on the M&sterfile depending on the type of
selection criteria he specified on the logic selection input card.
Variable Sequence - The Retrieval Program permits the user to
select the sequence in which he would like to view the data he has
selected.
Variable Output Format - Regions can select from seven print for-
mats depending on need. Cue of the formats is a single line
report with a user option allowing inclusion of any specific data
elements desired.
Since all management reports are based on the CDS retrieval capability,
users should place data on the Masterfile in a manner which will permit effi-
cient retrievals. When preparing input data for CDS, users should be aware or
the validation procedures for each data element performed by the CDS Edit as
well as the selection, sorting and printing criteria available in the Re-
trieval.
9.1 Reports Available from the Retrieval
Management reports are not automatically generated; the user must request
reports from the Retrieval system to suit his own particular needs. The 1:3 a.r
must determine what information available on the Regional Masterfile is of
interest to him. The user may obtain all of the information on the Masterfile
or a limited amount based on his needs.
Any of the defined data elements can be used as a selection criteria.
Since the selection, sorting and printing criteria in the Retrieval Program
operate independently, the user may select a report on one set of data
elements, sort on another set of data elements, and select different data
elements for printing. Selection criteria cannot be based on information
-96-
-------
found in comment records. If none of the nationally defined data elements
meet the user's selection criteria, one of the Regional Data Elements should
be used to facilitate retrieval selection.
Reports are printed in Reqion, State, County and Source Number sequence
unless the user selects his own sorting sequence. Up to six data elements,
other than comments, may be used to create the user sort sequence.
The Source Data Report, Questionnaire Report, Action Summary Report and
the Milestone Report will present user-selected and sorted information in a
fixed format. The Quick Look Report allow the user to design his own report
format. All data elements other than comments can be formatted for printing
in a user-selected sequence. A detailed description of each report is pro-
vided in the following paragraphs.
9.1.1 Quick Look Report
The Quick Look i^ the most widely used report type available from the
Retrieval. For each source, point or action which meets the user's selection
criteria, a single line containing user-selected data elements is formatted
for printing. The user may specify what data elements are printed, and may
also specify the spacing of these data elements.
A standard Quick Look print line contains State, County, Source, Point and
Action numbers together with up to 15 other user-selected data elements. The
only restriction is the print line length of 132 characters. Users may sup-
press State, County, Source, Point and Action numbers on each Quick Look line
by usinq the No-Header (NOHD) option. This option allows the full use o£ the
132 character print line for user-selected data elements.
Data elements are printed on the Quick Look line in the same order as they
are requested on the print-format selection card. For spacing purposes, the
-97-
-------
user may select one of the two special data elements: BLK1 produces a blank
column 5 characters wide; BLK2 produces a blank column 15 characters wide.
These two data elements may be used repeatedly for spacing as required. BLK1
and BLK2 are especially useful when the Quick Look is used as a turnaround
document.
Suppression of redundant data on the Quick Look Report is standard, Under
this standard feature, source level data will print only when there is a
change in data to be printed at the source level. Point level data will print
only when a new point is to print. Action level data will airfays ^rint,.
Note that if only source and point information have be-ir. rerruestid on ch-s
Quick Look Report, only source level suppression will take place. In only
source level data has been requested no suppression will occur. -r'igur-a S-l
shows a Quick Look Report with data suppression.
At the end of the Quick Look Report, a total is given for trie number of
lines printed. This total represents the sum of all items meetinq the user's
selection criteria. A page break and subtotals are also available on the
user-selected data elements. The user is cautioned to request p*ge breaks and
subtotals only for chose data elements which produce logical group ir.i:;j sue." an
State, AQCR, Action Type, etc.
The user may select his own sequencing for the Quick Lock Report. Of tan
two Quick Look Reports with the same selection criteria provide tne user witli
a great deal of insight when the reports are sequenced differently.
Since three different Retrieval Report formats can be requested from ths
same Retrieval, the Quick Look Report can serve as a summary or index to one
of the longer report formats such as the Source Data Report.
-98-
-------
OUICK LOOK REPORT
ID
I
09/07/H2
SDIHCE NAIL CITY NAME
AflHOTT LABORATDh IES NORTH CHICAGO
AHER ICAIJ UR ICK CHITAGO
AMERICAN MCKELOID PERU
AMOCO 3IL OES PLAINES
AMOCO DIL roRrsi VIEU
P
AMDCO 31. UOO!) RIVER
ARGoiJ'lE NATIONAL LAB ARGPNNf
CA< A|N ? 4
IL 4911 COAL-FRO ' 1 11 S I 2 0 5
IL 4-Ml fLtCIPICAi "JERVICft n 4
IL tsii riErinifii SERVICES o i
FLUf SAS I'' SULFUR f Oli I V j 4
IL <.91iri.rClr'ICM SERVICES ' S
n. ,""s
'-> \
SI
'Jri
S 1
M
'''
wi
OI/21/fl
10/30/80
02/2 //111
o 7 / 1 r, / n i
1 I/&5/80
lo/is/po
OI/OP/HI
04/0 1/81
07/ 1 K/P 1
10/10/C 1
10/14/80
01 /06/8 1
04/08/81
07/10/81
10/10/81
04/15/fil
10/10/80
01/lh/Rl
C 4 / 0 3 / 8 1
07/ 1 0/P1
1 O/ 1 H/f 1
0 1 / 0 f / fl ?
03/20/81
01/15/82
02/OP/HI
09/ 1">/81
C 3 / 2 H / 8. 1
?4/l 0/81
f S/2C/P 1
06/17/81
07/17/81
OR/1 0/81
0 1 / 2 h / H 2
1 O/? VPI
1 1 / 2 .V 8 1
Ol/ lr/8?
(ll / Ih/H?
0 ? / l H / 8 ;
C 5/^li/H?
r i / ? i / R i
Pll/Pl- /8 1
; / o / " i
;> /or/ c i
1 / 2 4 / 0
i / r > / " o
;' /(. i n i
0', /.J'-.'t. 1
th
Data Suppression
-------
9.1.2 Double Spaced Quick Look Report
This report is identical to the Quick Look Report except that a double
space is provided between print lines. This feature is especially useful when
the report is to be used as a turnaround document. The Quick Look and Double
Spaced Quick Look Reports cannot be requested simultaneously.
Figures 9-1 and 9-2 are samples of the Quick Look Report and the Double
Spaced Quick Look obtained by using the same selection, sorting and printing
cri teria.
Logic selection was based on Illinois facilities which have had major com-
pliance actions.
Sorting was based on Source Name.
Print line selection was based on the following data elements: Source
Name, City, State, SIC Code, Process Description, Emission Category,
Compliance Status, Action Type and Date Achieved.
9.1.3 Source Data Report
The Source Data Report is the most comprehensive reoort available from the
Retrieval. All data elements for a facility are included on this report; this
is the only report which gives complete source information, action information
and action comment information.
Each new facility is printed on a new page. Facilities with many points
and actions use multiple pages per facility.
For those in charge of maintaining the accuracy of the CDS Masterfile,
Source Data Reports sorted by State provide an essential coding tool. For
those interested only in a part of the Masterfile, report selection criteria
can be based on any retrievable data elements.
-100-
-------
09/OH/M?
SJLHCE NAIL
ABaOTT LABOR A13H ILS
AMERICAN IH1C<
AMERICAN BRICK
AMERICAN -JRIC*
AMERICAN NICK^LUIU
AMOCO 31.
AMJCO 31.
AMOCO 3IL
AMOCO 31.
AM3CO 3IL
AM3CO 3I_
AMOCO 01.
AM3CO 31.
AM3CO 31.
AMOCO 31.
A 113 CO 31.
AMjCO 3IL
AMOC3 31.
AM3CO 31.
A M J C 0 3 1 L
(. 1 3 C 3 31.
AMJCO 31L
AHiONN: MMIO'ML LAB
A ( j J\'M; >IAl 1"'(AL LAfl
C 1 1 V MAMC
NOIIIH CHICAGO
CHICAGO
CM 1C AGO
CHICAGO
PEHU
(IE 3 I'l A INtS
Oi'.i PLAlMES
OE S I'L A 1. ME S
tES PLAINES
HE 5 I'LAIMES
F O.R E s i v l E u
FORES! VIEW
f 0 R f :: i v l r u
FOREST VIEW
F 0 R f S I V 1 E U
UOI.3 HIvrR
wood RIVER
UOO." R 1 VR
woor o i VR
UOOV RIVR
JOOl- ;< 1 Vr R
WOO" !'. I ur H
Air.ON.E
ARC.O'nr
SI
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
1 L
IL
IL
1 L
IL
IL
IL
IL
It
CUMt'L 1 .
IA JOR A; i IONS ,
sic POINT pqn
JB31 PHARIAC-ril 1
J251 P»03R:S5 R
5251 PROGRESS R
J25I PROGRESS i.
J1J1 PLAlING 1-j
51 Jl M3NI 101 IN.,
5171 M3NIIOR1VJ',
5171 MONITOR INC.
5IJ1 MONlIO^lM.
51J1 M3NITORI-II,
MONITOR I «lr.
M 3 N 1 I 0 1 I "i ,
MON! i OR i M,
MOM TOR 1 Ni;
MJNI TOR 11. !.
?9ll V4POR HCCu
J911 M3M 1 1 3R 1 !,
?9i i MON! TOR i !'.
?91 1 M3NI IOR I -t"
29 | 1 '
OP.
OB
OB
n.
on
OH
on
OH
D5
0 H
OH
OH
OH
on
i.
0 «
C".
PAGE 1
CAP: A c M
01/21 /HI
1 0/50/80
02/2 J/11
07/ 10/fll
1 1 /0?/HO
10/15/RO
o i / o " / n i
01/01 /HI
0 7 / 1 1) / K 1
10/ 1 0/81
1 0 / 1 1 / B 0
01 /0>,/H 1
D«/0«/H1
0 7 / 1 0 / H 1
10/10/81
!U/I5/RI
10/1 1/HO
Cl/l«./fl
a i / o 5 / 1> i
o ; / 1 o / (i i
i n / 1 p / !< i
'.< 1 / U ' / H 2
0 1 / ? D / M 1
PI / 1 '>/!','
n<]u. 9-2. Double Spaced Quick Look
-------
There are four level options available and one of these four levels must
be specified in the selection criteria. Level A provides a printout of all
data for a facility. Level S provides only source and source comment data.
Level P provides all data except action and action comment data. Level C pro-
vides data for only those source, point or action levels which meet the user's
selection criteria. If no level code is specified, the default is Level A.
Although Source Data Reports can be sorted by any user-selected data ele-
ments retrievable on the Masterfile, users should not select point or action
level data elements as their major sort key; in order to produce a meaningful
report, users should keep all of the records for a given facility together by
sorting on the source level. If no user sort key is specified, Source Data
Reports are printed in the Masterfile sort order: Region, State, County,
Source, Point and Action Numbers.
Figure 9-3 gives a sample of a Source Data Report.
9.1.4 Milestone Report
Two different types of Milestone Reports are available to the user. The
iirst is the Standard Milestone Report which tallies Compliance Status Cede by
State. The second is the Variable Milestone Report. It is similar to the
Standard Milestone Report but tallies are based on any two data elements
chosen by the user. The presence of a 50 card in the retrieval selection
cards indicates that the report will be Variable Milestone Report rather than
a Standard Milestone Report.
Standard Milestone Report
To facilitate National Reporting requirements by managers, the
Standard Milestone . Report was designed to provide a tally of the
Compliance Status Code of selected emission points within a
-102-
-------
SOURIi DATA REPORT
09/OB/S?
AMERICAN CRYSTAL SUG
SIAt-: MN COUNTY POLK
COUNTY 28flC SOURCE OOOD2
COMPLIANCE DATA SYSTEM
MAJOR ACIJONS H>* FYHl
AOCR 132 CITY 1060
PAGl I
FEDf MOM-FED BOM S
APCO o SIP snuRCt tor? 3
APSI OPCRATING Rt)E», J
SOURCE NAME
ADDRESS
CITYt STAT£
AMERICAN CRYSTAL SUG
E.HIGHWAY 2 PROCESS
t GRANT' FORKS MN 5t721
STATE RE. f. I SI
NCOS XREF
PRIOR 1TY
298
OOC2
SIC 20S3
ROE4
ROE?
ROEf.
ni»fc MEMBER
LAS I -Ua04TE
R/l1/H2
DUN I URAOSIRECT NO.
SOURCE COMPLIANCE SIAIjS
FAC 1L ITY CAPACITY
POLLJIANI
F'T PAl|T|CULAIE MAlTfR
S2 SJLFUR OXIDES
HC HYDROCARBONS
CO CARBON MONOX IDC
N2 MlIROUEY OXIDES
MNO&C6I718C9
1 IN VIOL-N3 SCHEDULE
RDf "
COMPLIANTE
1 IN V IOL-NO SCHEDULE
1 IN VIOL-NO SCHEDULE
H NO iPPLlC STATE REG
". NO tPPLIC STATE REG
1 IN COMPL-CERT IF ICATN
SIGNIFICANT VI3LAIION I N3
SOURCE EMISSION CATEGORY 3 OVlR 1000 TPY
RUE 10 S ROE II S
EMISSION CATESORY AQCR INOICSTOR
2 100 TO 1000 TPY i ATTAINMENT AREA
3 OVER 1000 TPY A ATTAINMENT AREA
? 100 TO 1000 TPV A ATTAINMENT AIU.A
? 100 TO 1000 IPY A ATTMNMFNT AREA
2 100 10 1000 IPY t ATTAIN ME NT UREA
LOAD OPV A-ACTUAL
R3C I?
CLASS A I
L 'J « (J I M 'J
C 1691
?C ICO
o
tA>
I
POINI NUMtHR 000 MI/LT SOURCE CMPL 1
poLLjiANi PI SOURCE-SIP
DESCRIPTION SUGAR PROCESS-2 EOILER5 CAPACITY
ACTION 01 SCHD 5/ 1/79 ACHV / / »CT-!tl'r
ACTION 02 SCHD 5/ 1/79 ACHV / / ACT-TVrT
ACTIOM Q3 SCHO / / ACHV 9/ 6/79 ACT-TYPE
ACTION 01 SCHO 2/ 1/81 ACHV / / ACT-TYIT
ACTION Ob SCHD / / ACHV H/ 7/ftl ACT-TYPt
ACTION 06 SCHD / / ACHV 9/21/H1 ACl-lYPI"
IN VIOL-NO SCHEDULE
NO SCHLUULE
05
05
52
66
FINAL COMPLIANCE
SUFF
FINAL COHPLI4NCE
ll
-------
Region. The report shows the number of emission points broken
down by Compliance Status for the States within a Region and for
the Region as a whole. Subtotals are produced for emission points
In Compliance, Out of Compliance and of Unknown Compliance.
Regional totals are developed for only those States included in
the selection criteria.
Since the numbers developed by the Milestone Report represent the
totals of all emission points selected by the Retrieval, great
care must be exercised in preparing the appropriate retrieval
selection cards in order to create a meaningful report. For most
Milestone Reports, selection will be based on point number 000.
For specific reports, such a count of all Federal Facilities, the
selection criteria must be based on the Federal Facility Code.
Figure 9-4 gives a sample Standard Milestone Report. The selec-
tion criteria included only NSPS in Region V.
Variable Milestone Report
The Variable Milestone Report produces a tally of data based on
two data elements which are selected by the user. Any two retrie-
vable data elements at the source, point or action level may be
chosen. One data element determines the rows that will be pro-
duced. The other data element determines the columns that will be
produced. Note that the usex chooses the row data element and the
Variable Milestone Report will produce one line of output for each-
different value found on the file for that data element. To
determine which values Cor the column data element are to be
printed, the user supplied the column data element and the speci-
fic values for that data element. A maximum of 10 values will be
accepted.
As in the Standard Milestone Report, the totals produced oy t.-.-;
Variable Milestone report reflect only data selected by the
retrieval. Care should be taken in preparing retrieval selection
cards so that the report produced is meaningful. Figure 9-5 shows
a sample Variable Milestone Report.
9.1.5 Questionnaire Report
This report has been used by some regions for direct reporting by State
agencies. The report format provides a turnaround document used to report c.ne
status of various actions. Identifying data is printed on the Questionnaire
and it is then sent to the State agency for completion. After the State
returns the filled-in report, the data is keypunched for re-entry to the CDS
data base.
-104-
-------
Ill I.I.STOIIK IIF.POKT
o
Ul
I
o
1
T
1
4
'
r.
1
f
o
""'"
COIIPI.IAIICF. STATUS
COMIM. STATUS UNKNOWN
coiiPi. STATUS curiinun
i -i "lor -no scnrniii.r.
in COIIPI. -soiinci; TKST
1 II COIIPI.- I NSPF.CTIO'I
IN CIIIIPL-CF.IITIFICATH
MF.F.TiriC COIIPI. SCHI.O
IN VIOI.-liOT IITH SClin
IN VIOI.-||.|>; UKT SCIIH
'10 APPI. 1C STATi: II RC
IN roMPL-SIMIT DOWN
TOTALS FOK ?. . i. /, , 'i
TOTALS FOII 1 , 6
TOTALS FOP -i
TOTALS FOIt II AMI) 7
cr.Allll TOTALS
COtlPl.l A tier DATA .SYSTF.M
F : AMPLE OF A STANDARD MII.FSTONF. .!( FT 1! I F V A 1. KF.POKT
ItFCION 1 CONII II A IMF MASS NF.II II AM I' l:HO!)i: IS
TOTAL "7 ?0 ??. ID '. 1
110 15 -t (,'l 1 ;'.
'if, 1 ' -'i '1 1 4
7 HO ? 70 7K >/,<) | f] 70
',455 771 50 1,101 n54 1511
0 , ni? 107 416 1 , 5 '1 4 'III I/, 'l
1H 15 0 47 1 \r<
*7. 11 ? ') 1 1
4 0 l) l> I 1
II 51 ? 75 1P.O 72 155
'ili*i 52 Illfi 110 211 P.'i
(.,471 1.411 (.79 1,07'. '.04 620
h H Vi r, | /, /, 5
"II 15 O 47 1 15
114 25 5 60 4 II
7,'(,ru, 1,512 7(>5 1.5 '11 525 1.0 of,
PACF. I
VFIUIOIIT
47
H
0
7. 1
1 I"
5(.
o
o
II
10
<
105
o
II
o
205
ignre 'J-/i Sl:uiularil Mi leal one: Report:
-------
i :>Nf
COMPLI ANI : DATA SrSlE1!
M.1.IORS MILISIO^E
PftSt
SRCE C.ASSIFIC4I ION CODE
fiLANK
Al
t)
REGION J
10UL
2
1 04
12
STAB
PI
1
37
Sl»9
uv
SI «B
VI
0
?7
3
1
SIA3
in
SI A3
DC
0
I
0
0
sr*n
KCSIONAL CLAS ITEMS
122
4
25
31
O
CTv
Firjure 9-5. Variable Milestone Report
-------
The Questionnaire indicates all increments of progress that have been
scheduled during a period specified by the region. Status Code and Date
Achieved should be listed in the appropriate columns. Although the Quick Look
Report may serve the same purpose as the Questionnaire Report, the Question-
naire provides more information about the source and has additional room for
comments.
Figure 9-6 shows a sample Questionnaire for Region IX. Selection was
based on actions scheduled but not achieved between June 1, 1981 and
November I/ 1981. Sorting was based on Source Name.
9.1.6 Action Summary Report
This report is a summary report of what actions are in the system and
lists these actions by action type. The report gives two lines of information
for each action which satisfies the selection criteria. This report also
lists action comments. If no sequence is specified, the report will be se-
quenced first by Action Type and then the Masterfile sequence.
Figure 9-7 shows a sample Action Summary Report for Region IV. Selection
was based on a specific range of actions. Sorting was based on State and
Source tfeme.
9.1.7 Compliance Action Report
The Compliance Action Report summarizes the compliance status and enforce-
ment actions for selected facilities on the CDS Masterfile.
Figure 9-8 is a sample of the Compliance Action Repott. It is available
by coding "CA" on the Report Format 20 Card. The left side of the printout
contains basic source information such as Source Name, AQCR, City, State and
-107-
-------
ACTIONS SCHEDUI-!) 3UT NOT
CONK IDC»TI*L UCDKI - cOI r('A IMTE*N»L USE INLY
03/0-l/M^ PAGE 1
COMPLIANCE |1A I A SYSU1 D Jt S I I ONN« li»E
fJR STATE 0 =
CAL IFORNIA
SIATUS COOCS I-ACIION ACHICVfD 2-ACTION MOT ACHIEVED
I
.POINT SOURCE . [MISSION POINT, . SIAIf/LOCAL HEGUL, . SIHEDJL£ INCREMENTS . ACHIEVEMENT OF INCREMENTS.
. i OENI m CATIDN . POLLUTANT CHITTED. CONTROL pRDJECit . OF ?RDGUSS . OF PROGRESS
. . . POINT SIP
.CARSON ... . .
ND Cl IT CODE ...
. ARCO . PETROLEU1 REF1NI-. LA 7B-17 . S/I8/9I . STATUS CD3E COL 71
. JAIS3N REFIMRY . »if, . . PF * - OR 1A>JC E TEST . DATE 4CHIEVEO-COL 55-f.D
. . . . 'lO CAY YR .
. STAIi USIST^ATION . SULFUR OXIDES .
. 09-05-^200-05707-000-06-7. COMHENTS
SOURCE SIP COL 8D - R
. NO SCHEDULE ... . .
.RICH^N) ...
MD CITY CODE ... .
. CHLVIOM U.S.A. INC . Htjoi PLA.-^T . sun IGI . p/ e/si . STATUS CDOE COL 7i
. rtlCHIO*:) REFINERY . . . VERIFICATION NOT RECflWE-. DATE ACHIEVtO-COL 55-60
.0 .10 GAY YA
. STAi: UGISXATIOH . NITROGEN OXIDES . .
. 09-05-1620-50006-000-01-7. C011ENTS
, SOURCE SIP COL 80 - R
. . M3 SCM-IDULE ...
g.LONG JE«t>l
I . » IC. 0 . . . .
. DAVIS, M3RT COMPANY . SOLVENT SPRAr ST-. RULE 112(A)I3» . 7/ I/ql . STATUS C30i COL 71
. 1^5 PHR j AVE. . Aiion . . FINAL CSMPLIANCE REPORT . DATE ACHIEVEO-COL 55-60
. 10 OAY YR
. SIAI-: )£Glr.nAT IDN . HYDROCARBONS . .
. 09-05-1200-00615-200-01-7. fOHMENTS
NO SdltOUI.f COL 90 - *
. EPA CC CODE COL 3C
. 05-05-1500-00615-200-00-5.
. C3L BO - C
.1Ah I I*[I .
ND CITY CODE ...
. 3tr. FU:L SU-TLY CIR. ?oo . RET, (, ^UL-: i . 7/ i/si . STATUS CODE COL 7i
. 020L TtHTJt. . . . FINAL C3HPLIAHCE REPORT . OATE ACHIEVCO-COL 65-60 .
.MO f)«Y Y^»
N.
. 0°-05-lS20-Ui)025-?OD-0 1-7 . TOMMTNTS
FED SCM BEING DEV CPL »0 - R
. EOA CC CODE CDL ^0
. 0=)-05-l620-0002':i-300-00-5.
. COL H3 - C .
figure 9-6. Sample Questionnaire
-------
AC! I -,.'l f J11A1Y Rf
roHi'i i AMCE DA i /. SYS if M
M 1'ENT I AL RfPO''! - ;0^ I'M INlf.^'L US: ^NL
AfllON SUHMATt -J
I Y P : DF ACIION
NfSHA^S INSPECTION
SIACF
AMD II ILf
SOi/hCl" UAMt
A .V r: L 0 C A I I 0 N
s:. 'i.
DA IE till.
si AIDS cn:
SI4IE MO.
SOUKff UO.
PdlM NO.
> 3LL II I AMI
o
U3
I
S CO INC
r,A
in
«C I I3N A:-IIEV:0
I 1
1 120
"0036,
000
A3
fNGINTER
L I 'JPiN CHE1 i PL AS
T1UUSUICK G4
? / I ! / " 0
2/1 ?/ ->0
01
ACII3N A C -11 E V C 0
?09
HG
MAG raiLlA PL »S 1|CS
CHAMI'LEf GA
J / 2 "( / .' H
I 1
1 610
"017"
000
A3
MO HULL CO.
C.rt I FF I N 6 A
H / 1 "i / ' 0
fl/ 1 " / '10
01
AC i ION A:HIr
11
IbOO
ROO'iO
Figure 9-7. Action Summary Report
-------
C01PL I A 'Ji -4CI 10^
SOUHC: M4.1l
cur si
ACMt 3R|C«
FOR 1 SMI III AR
ACMt 9RIC< CO
PCHLA «R
ASRICD CHEMICAL co
BLYIllEVILLE AR
A^COA
9AUKIIE AH
ALCOA
BAUX1U AN
, ALCOA
_. 9tU« 1 1C AR
? ALLIED CHEMICAL
HfLlN* AR
ALLIED CHEMICAL COHP
HLLiNA AR
A M f & : Y A N A 1 1 o co
URVtNl AR
AMHLllSE«-3IISCH RICE
JD4ES33RO Afl
API C5NS1RUC11UN 2
N 'tU I H 1 lilt' H n AD
rj u K 1 M LIlILl " ',' ** K
FYH 1
AOfR SIAFF
01 7 JANIS FOHLHAND
N
Olf,
N
020
N
016 GEORGE KELLF.Y
N
Olb GEORGE KELLEY
N
016 S. SPRUIELL
N
020
M
023 r.AH I IN HR | I 1 A |M
Olb
N
02C OfORGE KILLCY
OlK
COMPL 1 i i.. £ UAI A SYS UM
C0.1PL 1 ANCE '. ( 1 IOMS
PlUO C01DL I AN( t SI»IUS
iMISSIS'j :. a TEGo"*
000
000
000
000
001
000
000
000
000
000
oro
3
P
3
3
3
3
J
3
3
2
2
2
3
3
0
4
i
3
3
2
1
IN Cr>1''L - 1 MSPEC
100 10 1000 I P Y
IN CQ1I L -1 'JSPEC
OVFR 1 U 0 5 IPT
IN COII'L- INSPEC
OVE* 1C30 IP»
IN C01IL-INSPEC
OVER inuo IPT
IM C01PL -INSPEC
100 10 1000 TPY
IN CDii>L-somcE
100 10 1000 |PY
IN CDMi'L-INSPEC
OVER i r oo IP*
COM^L '..IAIUS UN
LESS PiAM 25 1D
IN CotPl -INEP-C
OVCR I'OO IPY
IM COMHU-INSPEC
100 I y iQCO IPY
IN VI 01 -'JO SCHE
sr Air
s i A i :
FEDERAL
SIAU
STAU
"FEDERAL
SIAU
STAIi
FEDERAL
SIAU
5 I A I -;
ST»1E
FEDMA.
SIAU
ctDEi»AL
SIAIE
FEDERAL
siAir
SIAIE
SIAU
FEDERAL
STAIi
FEDr'»L
5 i A i :
FEDTRAL
SIAU
STATE
FE1E1AL
C f f -
:> 1 ft 1 t
SIA |r
5 I 4 I C
si AIT
CAGE 1
INSPECT RSLT NOIICE RSLI ORDER RSLI COUXI ^SLI
CODE OF VI 01. Cull!: ISSUED COIC ACII3M C35:
2/27/81
?/lb/82
1 1 /I 3/40
1/19/92
2/17/91
1/20/82
12/ 3/90
5/ 5/81
f,/ 9/82
f./ 9/92
3/ 1/81
3/11/81
3/30/92
4/22/9?
i/ I/HI
If 2/91
>/ 1 7/R1
1 i) / 2 1 / B 0
10/1-i/Bl
JC/31/90
i/ I:/BI
S / 1 1 / B 1
7/IW82
MC
MC
MC
MC
MC
MC
1/27/81 Ul
IV
MC
MC
1C
01
MC
MC
MC
01
01
MC
MC
MC
1 V
MC
MC
MC
A3 I C3N5MIIC II ^N CO 0 1 f> .1
NORIM LI T TLi 10 AH N
300 3 l»l C3MIM
? IOJ in 13 J C IP»
SMI: I ?/l»/8D IV
SIAU 1 / I/SI 1C
Figure 9-8- Sample Compliance-Action Report
-------
Staff Member for the sources selected by the retrieval. The middle columns
contain the Point Number, Compliance Status and Emission Category of the
points selected by the retrieval. The right side of the printout contains the
Data Achieved for nine specific action types:
Federal Inspections
State Inspections
Federal Notices of Violation
State Notices of Violation
Federal Orders Issues
State Orders Issued
Federal Court Actions
State Court Actions
Federal Terminations of Notices of Violation
When multiple actions with the same action type are selected by the
retrieval, multiple lines are printed, one for each Date Achieved.
In using this report, the following items should be kept in mind:
The retrieval selection logic is the same as for any other
retrieval. Users should be careful to specify in their selection
criteria only those sources and points of interest to them. No
selection cards are needed to limit the report to the nine
specific action types available on the report, but selection
criteria may be used on other action level data elements such as
Da tie Schediiied.
The report is produced only in one sort order: alphabetical by
Source Name within a State. If other reports are selected on the
20 Card at the same time as the CA, the other reports will be
printed in the order specified on the Report Sequence card.
Totals for each of the nine action types are produced at the end
of the report. These totals are designed to meet a number of
reporting requirements.
9=1=3 Special PSD Report
At the request of EPA Region VI, there is a new report format designed to
show the status of facilities undergoing the permit review steps associated
with Prevention of Significant Deterioration (PSD).
-Ill-
-------
For each facility selected via the retrieval, two lines of output are
created. The first line contains the following data elements:
Source Name
Application Number
Date of PSD Application Submission
Date of PSD Application Determine Complete
Date of PSD Review Received
Date of PSD Notice Drafted
Date of PSD Public Notice
Date of PSD Public Hearing
Date of PSD Permit Issued
The second line contains only facility location information.
Since the report lists seven different action dates side by side, Region
VI has found this report extremely useful in tracking the progress of the per-
mit review process for all of their PSD facilities.
Although this report is currently available only for Regions IV, VI and
VII, other CDS users can obtain this report if they inform TRC of the action
types associated with each of the actions which are being tracked in the
region's PSD permit review process. (See Figure 9-9).
9.2 Checklist for Request Submission
The following list of steps is provided as a guide for users submitting
requests for retrievals. The list is roughly sequential, in that an inexper-
ienced user would proceed in this order.
1. Determine what you want.
a. Review the need for information from the data base. Determine
the best way to respond using the Retrieval Package. what
information does the ultimate user need to meet his require-
ments?
-112-
-------
Com i i Anfi DA I» '. r- M r
i A r:.n H i n 11 * t.Hi-i i *i i» M i LI i
nfhl lift hi COR III' Mifl'l I '. l.< f |» i
n-, i MX i i i Ai. i -iir : tut im 11 / Tun vi
IPC H<-l A-Af* ll/lli/l I
MOAClllJli:.! I * 11 I A
IPC M'fr MM li III H. I l'Mi-| > - 20b Or/0 J/ /4 u'i/0| /T** |?/|f/IS
St'H lln.lt III I A
JAnti CUM* t,i ui u on
lUMbVUll I A
I All [ Ctt'l l I * HI. l'S|i-l i -t)01
PSIt-IA-OIJ
t
IOU1SIAN* IKIII^IHUS riO-l *-^* 0|MS/)9 Ol/30/?t 03/05/71 OI/M/bO 02/OI/AO li'/Ql/ f* tlS'lli'.ivIC II. COrl 1 I Alt
coi i. OCR i* E li/u/ca u/ii/«o e; /jo/^c ru»f»'t/ ffi C1/I4/1K 0*/01/1° 0*/0*/ M Ot./?* / 1* I'l' *l » H.v|| I N ( (j^ri | (h
Uf ill nOhKtit I A I 10/Oh/f.a 02/7A/BO 0?/?C/ttO 05
nctniKH i.nn. i ice c;n-i«-?o» OI./M/79 ot/oi/M LI**-! i* ai
I DM SI »l LA A
Hit 1.KIH I Ul. PSn-lA-lAI OJ/2?/l9 III SC I I.IJ 0
HI U OMl I iUS I A A
o?/?./'^ n?/?vu O'/ri/'f .^itcvir it.
HI. *IKI IA
hum n i nit C..HI . f:n-L>-ol* o<./o>/7r
1*1 AC lit hi I I »«M,(. (0. PSI'-li-OH* 0«/l'-/7')
It AIC h| I (It Ml r. . I A
n*r ID M i iiJHH, fo, rtf -i A -«i i o:'/ lit/ » 7
I'ttk I Al ( I U t A
Figurt: 9-9. Sample PSD Keport
-------
2. Code the form. (See Figure 9-10) .
a. Formulate a meaningful title for the report(s) and enter it on
the "01" card line. It will be printed on each output page.
Also, code the region code, and the level code only if the
Source Data Report is requested.
b. Create the selection logic (the "10" cards) to be used to
extract needed data items. This is the most complex part of
the job and it is suggested that the instructions be reviewed
the first few times the package is used.
c. Select the best format from those available. Use more than one
if appropriate. Put the correct format on the "20" card line,
using the proper 2-digit abbreviation (SD, QL, MS, AC or Q2).
d. Select the sequence of the items in the report and fill in the
"30" card line on the form.
e. Review entries on the form to see that all data element abbre-
viations are correct.
f. If the Quick Look Report format is being requested, add the
data elements needed on the "40" line so they will appear on
the output. Do not exceed the print line size. Check the
abbreviations.
3. Verify the completed form.
a. Review the request form to see that all needed entries have
been made.
b. If the selection logic to be used is fairly complex, mentally
"walk through" several cases and see if the Logic meets th=
user requirements.
4. Punch retrieval cards.
a. Arrange to have punched cards prepared from the request form.
b. Check the cards to ensure that the data was punched correctly.
5. Build your retrieval deck of cards.
a. Md a job card priority card and any routine or hold cards to
the deck of cards. Check for appropriate account number,
printing class, output line count and execution time. Terminal
operations personnel can provide assistance.
b. A3d the two JCL cards described in Section 9.4. They go just
before the "01" card.
Md /*EOF card as the last card in the deck.
-114-
-------
tn
I
Sec.1 rovL'rsc side Im-
list of .ill COS J.n.i
eliMiicnls and Ihuli
iihhrnv I at Ions.
COMPLIANCE DATA SYSTEM
Re; ort Request Form
ISlJJ LU LJ Lj-l-.l_Ul_l_l_i.l_l..l_L_L.l_l_LJ.:..)._i_l_l_.l_
12
45 7
ii level n»|H. .
t_L
30
Till*
7
V",i
Data
Element Cond. Vulue (lei! Justified)
-L I I J i
t J -(._..
lil9J 1-1 I I I LJ LL..l.J_i_l_l_J_LJ
IMJ l_i_L_U LJ L.LJ_!_i_i_i_uj,i_i_i_i
I i i i I LJ Li_t-L_i i i i i. i i i i
I I I I I LJ L-L-.LI .1 I I_1..J.J I I I
IllPl 1,1,1 LJ IjL-l-l-l I I I l-L-LJL-i
LJ I i i i i i i i i i i i i i i i i
.U
_J_L.I _
I 1 I...
L. i i I LJ L
. i i i i i
I I I I I I i
I i i i I LJ LI-JLX
IMJ Lo_i_iJ LJ Lo_j_i_
(Limit - 100 "10"Cards)
l ii i i i I
I I I I
l i I I. i I I I I l i i 1 I I I
REPORT rOHMAlS
PASSWORD (ACQUIRED 10 ACCISS COnflDlNMAl.
L
12 15 7 0 lOll 14
REPORT BEQUEIICI:
li2J l.i i ij Lxa_jJ LLJL
121 79 12 14
SCIJUMCE tlHIKO 10 4D ClUHAClCBS
I
OAIA ftfiUNIS)
10
(10 CAKH)
1.0 '.2
i_I._J.-t_l_. L-J_«-
M*
II - flllST E()OAL
l\ - ALTEHMAIF. (used for
ll«l)tl|l|t! Y3 11/1:5 Of 0
ylvnn diita elwiiont
U - ONKIJt/AL
G - EIJUAL OH CKErtTEK THAN
L - EIJUAL Oil LESS THAU
P - PHESEMT Afir IIITIIY
0 - BLANK OH ZEI10S
U Li i i.J I i i i I LJL
17 1'.) 22 21 ;'/ 29
32
Hunfecr
| |
-in dill t
" on Qt
QUICK LOOK REF'OriT FORMAT
U.I I .1 L.L1.1.J Lj.
4 79 12 11
j.J t j-i i.J La_i..i,! Lt-JL-i-J i j i i J _.
l/ I'l 22 24 ,' , 29 32 34 37 39
U-J
41
U-J_I_J
Inter Dili Dementi lu It Included on Re|>t)rt
Unite.) (o IJ2 Cturtam with NOIIU Op(l.>.i|
llnlttJ to 110 Mlth St^i.l.rd lltldlnq
LI_I_L' I I i i J-J LJ.J_I_| L.J_i_i.J Li_i-iJ LIL.I
51
fi? 01 G7 69 72
MILESTOHf REPOnr fUHMAT
t?i2J Li_JL_jJ LLJ-I.J LXJ_J._.J I i_i_j_J U
I 2 4 79 '.?. 11 I/ !') 22 24
I.I..I-L.J Ll-_l.jJ Ll_J_t_J Ll. I.!.) Ll.i.._l_J
29 )2 31 3/ 39 42 44 47 -19 !i2
(un Bi.hVro* U.i.Lj L.i_t..uJ
T l
Siiliml t (CM! ________________
Rcltirn llopurt to _______
Mn 1 1 51 up __________________________
,1-Ji-i j....t_j..i_l_l_l._i_i_LJ
;o no
LEVI.I. COI)[.S (01 tAHO)
IIEIJUIIILIi 1011 SI) KU-Olll ONLY.
VALID Alii!:
S - SOIIIICE ONLY
r - roiHi n soiMcn
A - ALL DAIA(default)
C - CRITERIA I1AICII ONLY
IIEPORT FOItMATS (20 CARD)
fll. - (JHICK LOOK
(|2 - IJOUIILE
SU - SOURCE DAIA IILPORT
AC - AC1IOH SOWIARY
(|l - (JIILSMONAIRi;
MS - HII.LSIOIIE
CA - coni'LiAiicr-AcrioH
COMHLHI COHIS (4(1 CARD)
C - ALL COMMIIIIS
S - SOIIIICE COMMIHIS ONLY
r - roiNi COMMIHIS OHI.Y
A - AC I ION COMMINIS ONLY
-------
a\
DATA ELEMENT
AIR PROGRAM CODE
AIR PROGRAM DESCRIPTION
AIR PROGRAM STATUS
AIR PROGRAM STATUS OESCRIPIU.il
AIR QUALITY CONTROL REGION
BLANKS (S SPACES)
BLANKS (IS SPACES)
CAPACITY - FACILITY
CITY CODE
CIIY NAME
COUNTY CODE
COUNTY NAME
DATE OF LAST INSPECTION
DATE OF LASI UPDATE
DUN i BRAOSIREET NUMBER
FEDERAL FACILITY
LOADING DERIVATION CODE
MONTHLY HISTORIC COMPLIANCE (AIL)
MONTHLY HISTORIC COMPLIANCE - 1ST MONTH
through
MONTHLY HISTORIC COMPLIANCE - 24TH MONTH
NEDS SOURCE CROSS-REFERENCE
POLLUTANT AIR QUALITY CONTROL INDICATOR
POLIUTANT - BASIC SUMMARY
POLLUTANT CLASSIFICATION
POLLUTANT CODE SOURCE
POLLUIANI COMPLIANCE STAIUS
POUUIANI EMISSION CATEGORY
POLLUIANI LOADING
COMBINED PLLT i PAQC
PRIORITY CODE
REGION
REGION - STATE - COUNTY
REGION - SIAIE - COUIITY - SOURCE
REGIONAL DATA ELEMENT 1
REGIONAL DATA ELEHENI
REGIONAL DAIA EIEHENI
REGIONAL DATA ELEMENT
REGIONAL DATA ELEMENT
REGIONAL DATA ELEMENT
REGIONAL OAIA ELEMENT
REGIONAL DATA ELEMENT 10
REGIONAL DATA ELEMENT n
REGIONAL DAIA ELEMENT 12
SIC CODE
SIC CODE DESCRIPTION
SIGNIFICANT VIOLATOR FLAG (ALL)
SIGNIFICANT VIOLATOR FLAG - CURRENT
through
SIGNIFICANT VIOLATOR FLAG - 3RD OLDEST
SOURCE CLASSIFICATION CODE
SOURCE CLASSIFICATION GROUP
SOURCE COMPLIANCE STAIUS
SOURCE COMPLIANCE STAIUS DESCRIPTION
SOURCE COMPLIANCE SIATUS - 8 QUARTERS
SOURCE COMPLIANCE STAIUS ISI QUARTER
through
SOURCE COMPLIANCE STATUS - Bill QUARTER
SOURCE EMISSION CATEGORY
SOURCE EMISSION DESCRIPTION
SOURCE NAME
SOURCE NAME - SHORT
SOURCE NUMBER
SIAIF KAME - SOURCE
SIAFF PERSONNEL CODE - SOURC1
488H
Al'>:0
APOS
APST
AI'SO
AOCR
em
BU:
FCAP
CYCO
C»NH
CNIY
CTHM
OTLI
UPOA
DtllO
FEOF
LDRC
Hlil
MMdl-
MII24
NEXS
PAQC
BPLI
PCLS
PLLT
PCMS
PECT
LOAD
PLPQ
PRIO
REGN
RGSC
RSCS
ROE)
RDE2
RD£]
RDE-I
RDES
RDE6
RDE9
ROM
RDM
R012
SICC
SICD
SVIL
Svll-
SVI4
CIAS
CLAG
SCHS
SCSD
SCSa
SCS1-
SCS8
SECT
SECD
SNME
SUMS
SRCE
STFS
PEP.S
DATA
ItPE
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
10 i 30
CARD
1
10
1
10
3
7
4
IS
4
17
6
6
12
1
1
24
1
1
4
1
20 i 40
2
2
1
5
3
2
a
13
1
1
S
5
10
7
2
2
1
4
30
4
1
1
2
1
1
20
8
1
1
1
13
20
10
S
IS
1
. .
-------
c. Review the sequence of cards.
6. Submit lob.
Submit the deck to the central computer facility (NCC) via the
locally available terminal.
7. Review output.
a. The printout should be returned within a few hours or, at most,
on an overnight basis. Check with the terminal operator if not
received.
b. When the printout is returned, check the edit list to determine
if any error was detected. If necessary, correct the cards and
resubmit the deck.
c. Review the decoded parameters on the edit list to determine if
any error was detected. If necessary, correct the cards and
resubinit the deck.
d. If possible, check the retrieval package processing of a source
known to the requestor to verify that the select logic worked
as anticipated. In any case, review the results to determine
if the desired information was extracted.
e. Call TRC (203) 289-8631 if you are having difficulties getting
the desired output.
Mailing Label Option
This cot ion provides individual users with the capability to request
printed mailing labels as the output from CDS retrieval processing. A print
program has been developed for this purpose. The labels produced in this pro-
cessing are the standard 3-up, self-sticking labels which can be printed en
facilities currently available to CDS users.
The mailing label option has been designed to use source level information
available on a standard CDS Source Data Report. The user will request a
Source Data Report, level S, with the mailing label print feature. This
special print feature will be invoked through the use of job control proce-
dures developed for this purpose. There is a catalogued job control procedure
available to all CDS users.
-117-
-------
Each mailinq level will carry five lines:
State Code, County Code, Source Number
Manager's Name
Facility Name
Street Address (if available)
City, State, Zip Code
Two new source level comment lines on card type 4 have been provided for
the entry of information that does not already exist at the source level.
Comment line number "A" will be used for entry of the name of the manager
receiving the correspondence. If the facility address information entered on
card types 1 and 2 is not the correct mailing address, comment line number "B"
should be used for coding this information. If address information is coded
on comment line "B", the print program will use this as the mailing address,
otherwise source level address information is printed. (See Figure 9-11).
9.3 Preparing Retrieval Selection Cards
To request reports from the Reporting Program, the Regional user must pre-
pare a Report Request Form as shown in Figure 9-10. The Report Request Form
contains a layout of the standardized cards which will be submitted ;o ir.tr
central data center. In addition, the Report Request Form contains pertinent
information necessary to fill out the form.
The standardized cards used for requesting reports are listed here and
described in detail in the following paragraphs.
' CARD TITLE
01 . Title Card
10 Logic Selection Card
20 Report Format Card
30 Report Sequence Card
40 Quick Look Data Selection Card
50 Variable Milestone Data Selection Card
-118-
-------
fflrJi^ i" f.nni.rn'l
-------
Card 01 - Title Card
Card 01 has entry spaces for the Card Code Number, Region, Level and
Report Title. The Card Code Nimber, 01 must be put into columns 1 and 2. The
Region Code, columns 4 and 5, is the numeric region number of the EPA Region
requesting the report. A leading 0 must be placed before all numbers less
than 10. The level code (column 7) determines the level of data that will be
included for a Source Data Report. However, the level code is necessary only
when requesting certain Source Data Reports. This column may be left blank
wh»n requesting the remainder of the six types of reports.
Level codes which may be used when requesting a Source Data Report are
shown in the upper right-hand corner of the Report Request Form and are listed
here. If no level code is specified, the default value is "A".
S - Source Only
Only source level information is included in the report no
point or action data.
? - Point + Source
No action data is included in the report. Only those points
which match point and/or action level selection criteria ^r'j
included.
A - All Data
If a match is made on the selection criteria anywhere in the
source, point and/or action data, all the data for that source is
given.
C - Criteria Match Only
Only the information satisfying the selection criteria is inclu-
ded. This level code would be used when only the actions (plus
their respective points and sources) which meet the selection
criteria are desired in the report. It should be noted that the
selection criteria (type "10" cards) should include action record
data elements, or this level code will result in the same report
level asanSoraP level code.
-120-
-------
The Report Title (columns 9-80) is the user specified title which will
appear on every page of the output report. Titles should be carefully chosen
and include an English language description of the selection criteria to iden-
tify various printouts which are produced. Experience has shown that if a
number of reports are prepared without adequate titles, it is difficult to
remember the specific criteria for each report and information may be misused.
Card 10 - Logic Selection Card
Card 10 provides the user with entry spaces for the Card Code Number, Data
Element, Condition Code and Value. Specific data records to be selected for
inclusion in the output reports are obtained by using card 10. Up to 100
cards can be submitted in a given retrieval. The Data Element (columns 4-7)
field is used to specify a particular data element to be used in the logic
selection of records. The data elements are identified by the abbreviations
shown in the box on the back of the request form. For example, the abbrevia-
tion for "region" is "REGN". Use of other abbreviations will cause an error
and the run will be aborted. Only the data elements indicated in the table
can be used for logic selection purposes.
The Condition Code (column 9) is used to specify how the data element is
selected. The entry is a single alphabetic character selected from the codes
shown on the right side of the form. A brief explanation of the codes follows:
M - Must Equal - A record will be excluded unless it equals the
value specified in the value field. When testing for a value
of blank, use the condition code M with no value entry in
columns 11 through 30, or use condition code B to select
blanks or zeros.
A - Alternate - This code provides the capability of including
records with different values' for the same data element. For
example, three States might be selected and all given the
condition code A on three separate 10 cards. The output
report would include the data for all three States. If an M
had been used, no output would be received because clearly no
record will match all three State codes. For example:
-121-
-------
10 STTE A 07
10 STTE A 30
10 STTE A 47
U - Unequal - This code excludes records of the value specified in
the value field. It would be used where specific values are
not wanted on the report but all other data is desired.
G - Efrual or Greater Than - This code can be used to include
values greater than or equal to a specified value. Or this
code may be used in combination with the L code (Equal or Less
Than) to provide a range of values, such as all the action
types equal to or above 50, and equal to or below 70. More
importantly, it can be used with the "Date Scheduled" or "Date
Achieved" field to provide a chronological range. The date
should be entered in month, day, year, sequence. For example,
the following entries would provide a range between January 1
and the end of 1980.
10 DTAC G 010180
10 DTAC L 123180
L - Equal or Less Than - This code is the opposite of the G code
and includes items which are equal or less than the value
specified. If a comparison is made using a field which is
either alphabetic or blank, the results will depend on the
exact entries found in the data base. Letters will compare
lower than numbers, and blanks will compare the lowest.
P - Present-Any-Eh try - This condition code will qualify an entry
if the entire field is not blank or zero. That is, if any
entry has been made, the record will qualify for inclusion on
the output. No "value" entry is required in columns 11-30.
B - Blank - This is the opposite of the P code and will qualify an
entry where the specified field is completely blank or zero.
No "value" entry is required. Use the condition code "M" to
select only blanks or only zeros.
Value Field (columns 11-30) is used to enter the actual value to be used
for comparison with the data base. In some cases, this is the coded data
actually carried in the data field. It is not used if the condition code does
-122-
-------
not call for a value. Entries should be made beginning in column 11, the
left-most portion of the field.
The number of digits for each data element is given on the Retrieval
Request Form immediately to the right of the Retrieval abbreviation for that
data element. If a data element has fewer than eight positions, the number of
digits in columns 11 through 30 must correspond exactly to the number of
digits on the data element. For example, if a selection is based on State
Code, only columns 11 and 12 may be used on the selection card.
If a data element, such as Source Number, has five digits, users must code
00069 in columns 11 through 15; the retrieval logic will not work if only 69
is coded into columns 11 and 12.
If a data element, such as Source Name, has more than eight digits, the
Retrieval will base its selection logic only on the first eight positions of
Source Name, no entry may be made on the selection card beyond column 30.
ftote that entries in the value field must be exactly as shown in' the data
base. For example, if a State code is desired, the numeric code must be
= r;t?red. If a regulation has been entered in several ways, such as REG 31 or
REG-31, two alternate entries must be made to obtain both results.
Card 20 - Report Format Card
This card allows the user to select up to three output formats in a given
run, and must be included. The codes to be used are shown in the "report
formats" block at the lower right of the request forms. Entries should be
made in columns 4-5, 7-8 and 10-11. Start witft the left-most field. The
available report formats are:
QL - Quick look
SD - Source Data Report
AC - tetion Summary
-123-
-------
QT - Questionnaire
MS - Milestone
Q2 - Double Spaced QL
CA - Compliance Action
CDS Confidentiality
Certain data elements identified on the back of the Retrieval Request Form
in CDS are password protected. If the user wishes to obtain confidential data
on his output report, he must place the regional password in columns 14-21 of
the Card 20.
Comments at all levels (source, point and action levels) will no longer
appear on Source Data Report and will not appear on Quick Look Reports unless
a password is supplied and accepted. This will mean that Source Data Reports
may be considerably shorter. If comment information is desired, you must
supply the appropriate password, and all comments will be included in the
Source Data Report.
Certain action types have been determined to be confidential and will not
be retrievable without a proper password. The following six action types are
confidential for all regions:
ACTION TYPE ACTION TYPE DESCRIPTION
L2 CIVIL ACTION BY STATE
L3 STATE CRIMINAL ACTION
L6 EPA CIVIL ACTION
L7 EPA CRIMINAL ACTION
X2 STATE COURT DECREE ISSUED
X3 FEDERAL COURT DECREE ISSUED
In addition to these, certain other action types are confidential ior
specific regions:
REGION ADDITIONAL CONFIDENTIAL ACTION TYPES
01 AD, AE, DA, EA, Gl, H8, 29, 92
02 57, 61, 62, 64, 65, 66
03 27, 28, 29, 30, 43, 44, 90, 92
04 B5, B6, D8, CA, Cl, F3, G7,
K2, V8, 5B, 60, 64
-124-
-------
REGION ADDITIONAL CONFIDENTIAL ACTION TYPES
05 26, 27, 31, 75, 77, 92, 28, 95, 97
06 78, 79, A7, A8, E3, G3, A3, Wl, 15, K5, 11, 19, 24, 57
07 32, 57, L4, 96
08 58, 21
09 83, 33, A7, B5, C2, D6, E3, H8, KO, M5, 20, 32, 44, 57, 59
10 14, 22, 54
Be aware that confidential action types will not appear on any reports
when no password is supplied. Quick Look Reports will not show confidential
action types. Milestone Reports requesting action level data on the 50 card
will not include any actions which have confidential action types. Confiden-
tial action types will be missing from all Source Data Reports. When con-
fidential action type data is required, supply the correct password for your
region, and all confidential action type data will be extracted and supplied
as part of the reports.
Card 30 - Reoort Sequence Card
The report sequence card permits the user to select the sequence of
entries or. the report he has selected. For example, sources might be alpha-
betized within a State or grouped by pollutant code. In every case, reports
will be sequenced by the following elements after (or in the absence of) the
selected user sequenceAction Type (Action Summary Report only) or Reqicn.
State, County, Source, Point and Action Number for all other reports.
Entries are made using the four-digit abbreviation for individual data
elements shown in the blocks on the back of the retrieval form. For example,
to sequence by source name, "StS-iE" is entered. Cars must be used in limiting
the length of the sequence elements to 40 digits. For example, a sequence of
Source Name (20 digits) and Process Description (25 digits) would result in a
fatal edit error as the sequence length is 45 digits. However, in utilizing
all six possible sequence entries with SIC Code (5 digits), Federal Facility
-125-
-------
Code (1 digit) , Air Program Code (1 digit) , Compliance Status Code (1 digit) ,
Pollutant (2 digits) and SIP Code (1 digit) , we only have a total of 11
digits, well within the 40-digit limit.
It is important to note that in certain cases it is possible to request a
meaningless report because of illogical sequencing. For examplef a user
sequence of Date Scheduled, especially on a Source Data Report, would result
in the action records of several sources being separated and grouped away from
their sources. However, the same user intent may be achieved by reauasting a
sequence of Source (tome or Mimber) followed by Date Scheduled. This would
keep all the actions with the correct source. A rule of thumb to follow would
be to ensure that the primary or first sequencing element is on the source
level, and that it is unique to each source (such as Source Number or Source
tfeme) . This rule mainly applies to Source Data Reports. Quick Look Reports,
being one-line reports where no line must be related to any other line, may be
sequenced in any manner with no difficulty.
Page breaks and subtotals are available on the Quick Look Report by plac-
ing a number ranging from 1 to 6 in column 39 of the 30 card. For 3x.-;mnlf=.- if
column 39 of the 30 card is left blank, no page breaks are produced. A '!" in
column 39 will produce a page break on the first data element of the 30 card.
A "2" in column 39 will produce a page break on the first two data elements of
the 30 card. Page breaks can be obtained on a maximum of 6 data elements.
Example:
30 STTE AQCR SNME 2
The above card will provide page breaks with subtotals by State and by AOC3.
-126-
-------
Currently, CDS users who need to sequence their enforcement actions
receive Quick Look or Source Data Reports with actions listed in order from
the earliest to the most recent. With this standard ascending sort sequence,
the presence and importance of the most recent enforcement action is often
lost.
In order to highlight the most recent enforcement action for facilities
with numerous actions, TRC has developed two parameters which allow users to
list first the most recent action for a given facility. Previous actions will
be listed from the most current to the oldest.
A Quick Look Report which lists the most current actions first must have
the following Report Sequence card:
30 STTE SNME CNTY SRCE DTSC
Date Achieved (DTAC) may be substituted for Date Scheduled (DTSC) if
desired.
In addition to this special report sequence card, users must also insert a
Job Control (JCL) card after all of the Retrieval parameters. The foc-nat of
this card is as follows:
//SORT.SYSIN DD DSN=CN.EPAEXC.A026.ACTNSORT,DISP=SHR
The above card should be used only if the user desires the special sorting
on actions.
Card 40 - Quick Look Data Selection Card
Card 40 provides a means to request specific data elements for inclusion
on the single line printed for each match on the Quick Look Report output.
Data elements should be entered from left to right in the same sequence as
-127-
-------
required on the report. Data element abbreviations used should be the same as
those shown in the block of Figure 9-10.
Note that State, County, Source Number, Emission Point Number and Action
Number Codes will automatically be placed at the left most side of the line by
the system. However, if the user does not wish to have these data elements on
the Quick Look Report, these data elements can be suppressed by coding NOHD in
columns 4-7. The total Quick Look print line length is determined as follows:
With the NOHD option, up to 132 print positions are available.
The sum of the digits listed in the NUMBER OF DIGITS-40 CARD
column of the Report Request Form must be 132 or less for the data
elements on the 40 card.
With the regular heading of State, County, Source, Point and
Action Numbers, up to 110 print positions are available. The sum
of the digits listed in the NUMBER OF DIGITS40 CARD column of
the Report Request Form must be 110 or less for the data elements
on the 40 card.
If the data elements on the 40 Card require more space than is available
on the 132 character print line, the Quick Look will not be produced. Data
elements are printed left to right in the same sequence as they are coded.
A standard Quick Look Report is printed with data element suppressor1..
Source Level information is printed only once on the first print line for each
source. Point Level data will print only on each change of Point Number.
Action Level data will always print for all lines.
If comments are desired, the comment level code should be placed in column
79 of the 40 card. Comment codes used should be the same as those in the
block of Figure 9-10.
If a Quick Look Report with data element suppression is not desired, a '2'
must be coded in column 80 of the 40 card. Using this option all levels of
data will print repeatedly for each print line.
-128-
-------
Card 50 - Variable Milestone Data Selection Card
The 50 card provides a means to request the row and column data elements
to be shown on the Variable Milestone Report. Data element abbreviations
should be the same as shown in Figure 9-10. The first data element supplied
determines the rows for the report. The second data element determines the
columns. Column data element values should be entered from left to right in
the sequence desired on the report.
If the user desires to have all blanks as one of his column values, 'BLNK1
should be entered as the corresponding value on the 50 card.
Note that the 50 card will be rejected if a Milestone Report was not
requested on the 20 card. It is the presence of the 50 card that determines
that the Variable Milestone Report should be produced. If a Milestone Report
was requested on the 20 card and no 50 card is found, the Standard Milestone
Report will be generated.
To produce a Variable Milestone Report showing the number of actions for
Action Types 01, 02, 03, 04, 05 for all the counties within a State, perform
the following steps:
1. Choose an appropriate title on 01 Card.
2. Use a 10 Card to select the appropriate State.
3. Use 10 Cards to select the desired action types.
4. Code Milestone Report on the 20 Card.
5. Code the 50 Card as follows:
50 CNTY ATPE 01 02 03 04 05
This request will produce five columns of numbers one column for each of the
selected action types. On the right hand side of the page, totals are gener-
ated for all actions for a given county. One line is produced for each value
of the County Code selected by the retrieval. At the end of the report,
totals are produced for each action type and for the number of counties
selected.
-129-
-------
Up to 10 values may be coded on the 50 Card, one value for each column to
be totaled. If the data element values to be totaled are mere than four posi-
tions, totals are produced only on the first four positions of the specified
data element values.
9.3.1 Special Considerations for Pollutant Compliance Retrievals
Once pollutant compliance and other pollutant data is placed on the
Masterfile, it is stored as a repeating data element which can occur up to 10
times. The processing for data such as Facility Capacity or ;}.=gional Data
Element 9, each of which occurs only once per facility on the Master file, is
different from the processing of repeating data elements such as Pollutant
Compliance Status. There will be no changes to the report selection or the
report printing of non-repeating data elements. The following sections des-
cribe the changes to the selection, sorting and printing of repeating data
elements such as Pollutant Compliance.
9.3.2 Pollutant Compliance Logic Selection
Associated with each pollutant are the following data elements:
Retrieval
Name Abbreviations
Pollutant PLLT
Pollutant Compliance Status PCMS
Pollutant Emission Category PSCT
Pollutant AQCH Indicator PAQC
Pollutant Loading LOAD
Whenever one of the above repeating data elements is used on a 10 Card,
each of the 10 groups of pollutant data is examined independently to see if
the information should be selected for further processing. For example,
assume that the Masterfile contains the following four sources:
-130-
-------
Source Source Compliance Pollutant Pollutant Compliance
A 4 -
B 1 PT 4
S2 1
C 1 PT 4
S2 4
HC 1
D 4 PT 4
S2 4
HC 4
The following Selection criteria will extract data for Sources B, C and D
because each of those sources has the selected pollutant and the selected com-
pliance status.
10 PLLT M PT
10 PCMS M 4
The following selection criteria will extract data for Sources B and C
because each of those sources has one pollutant out of compliance.
10 PCMS M 1
The following selection criteria will extract Sources C and D sinca tncaa
two sources contain hydrocarbon data.
10 PLLT M HC
Because the selection criteria for repeating data elements are applied
independently to each group of data associated with a pollutant, the Condi-
tions Code "A" must be used to select a range of values for pollutants or for
pollutant compliance status. The alternate logic does not allow users to
select only those sources which are in compliance with particulate regulations
and are also out of compliance with SO_ regulations. Users will get no hits
with the following selection criteria:
10 PLLT M PT
10 PLLT M S2
-131-
-------
9.3.3 Pollutant Compliance Sorting
Quick Look Reports may be sorted by whatever data elements the user
needs. Page breaks and sub-total can be developed for any user selected data
elements.
On a Source Data Report users may not sort on any of the repeating data
elements present for each pollutant. Pollutant data will print on a Source
Data Report as follows:
Facility Capacity and Regional Data Elements.
If any data for particulates, SO2» hydrocarbons CO, or NOX,
the data will always be printed in the following order: ?T, S2,
HC, CO, N2.
Pollutants other than PT, S2, HC, CO and N2 will be printed in the
order in which the pollutants were originally input.
A separate line is printed for each pollutant entered via the Card 3.
9.3.4 Printing Pollutant Compliance Data
The presence of repeating pollutant data elements on a Quick Look 40 Card
and a Milestone 50 Card require certain restrictions; orh*>/; ---. ~'.:-~-T-:? "-.-.
output formats will be minor.
If a source has pollutant compliance data, the pollutant data will print
on a Source Data Report directly after the source or source comment data and
before the point 000 data. One line will be produced per pollutant. No
changes to the Source Data Report will be noticed if there is no pollutant
record for the Source.
The Quick Look Report will be significantly affected when repeating pollu-
tant data is requested on the 40 Card. At the present, only source level and
pollutant data may be printed on one line. One line will be printed for each
pollutant. Suppression of redundant source data will be helpful on this type
of report.
-132-
-------
Point or action level data cannot be printed when pollutant data is
printed. This restriction may be lifted at a later date.
Similarly, a variable milestone report which specifies repeating pollutant
data on one axis cannot have point or action level data on the other axis.
Milestone Reports may be requested with source level data items on one axis
and repeating pollutant data items on both axes. For instance, users may need
a milestone with pollutants as the row data element and pollutant compliance
as the column data element.
Since repeating pollutant data elements are not directly related to any
point or action level data elements, neither Milestone Reports or Quick Look
Reports may be produced with repeating pollutant data together with action and
point data. This restriction is necessary because there is no meaningful way
to cross-reference multiple pollutants with multiple points and actions.
9.3.5 Sample of a Filled-in Retrieval Request
The Retrieval Reports shown in Figures 9-1 through 9-9 were obtained by
fillinq out Retrieval Request Forms shown in Figures 9-12 through 9-19.
9.4 Job Control Language for Using Retrieval Program
The CDS Retrieval Package operates on a Remote Job Entry (RJE) basis at
NCC. Input must be submitted from a high speed terminal (frequent and compli-
cated requests might be stored on a WYLBUR data set) . To submit a job
request, only two JCL cards are needed in addition to the MX job cards and
the necessary, 01, 10, 20, 30 and 40 cards. ?fc action is required to receive
the output printout as it will be routed back to the original terminal as soon
as it is presented. (See NCC-IBM User's Manual for additional routing infor-
mation) .
-133-
-------
Si'p revprsi' Lie lor a
list of all > li'> .l.ilj
elements .iii.l I In'11
abbreviation..
COMPLIANCE DATA SYSTEM
Hoijort Rctiuest Form
HAM SI/IIMIIIEII
III IIIIIN RLCOni TO.
MAIL SI Or
i°.u iQ& L_I ftAI.Q.£uJL^J-fl.li5.-.F.P.R-,E.t.M i-y-ui
I I I I I I II ' *° ",
C-^-^. ._l_i|<_LJ_._LJ-J...L-._,li.J_UJ_l-
l^-'--'-1- d
li'ioj
i'i°i ilT'P'fcj lAi (0.5. . . , . . i L . . . . . i ....... i . . >
1 ' . °l lATiPid In' iSiZ. ,. i i i i i . ....... i i ...... . 1
I'.OI 1 . 1 1 1 1 1 1 i ...... i i i ... . I ... i .. . . . . I I
(LIMIT - 100 IU CARUS)
iron IOIM.II
I'.oj |Qtl L.J 1 I 1 . . , . ,.^_J
LEVEL COOES (01 CARD)
REQUIRED fOR SO REPORT ONLY.
VALID ARE:
A - ALL DATA
C - CRITERIA MATCH ONLY
P - POINT t SOURCE
S - SOURCE ONLY
U.eJ
i i i
fftllwolD iMijUIHIO 10 AtCtSl L0«* Iflhl 1*1 DAI* ll[l'[Nll)
t '"^i ir1"""1!) \il~L~n n "^i ii' 11
LJ -
H '
OMT fOBM*|
'^ ii.f-A.ft
14 I) I« ' I/ 11 U M If M 12 14 Jf 11 41 44 4) || U
I (Piled tn |).' ' f I'lclr-l -l|h MHO
Lx-L^J !.,_*_. J LLJ-J L.uo_J
II U SI (I II II II II
'i«'
"?" Slopl
MUISIOHI IfQII fODMAT
I'.OJ Li_,_lJ I. I .I..LJ l._l_i_lJ I I-J-U l_L_,_iJ I ,_X_lJ I..|_I_J.J L.1-.-I.J L..1. i I.J L.._i_1J
I I 4 I > II H II II IJ M If 1) ]| 14 I/ 11 41 44 U 41 U
Ornt i .>!-.« MI VAIUI1 Of COIUMM OAFA III MINIS t".« ftlti*' IOH 6i tfit V*LI'| J
0*1* I'-|» l..i_l i J L.i. ,j,_t I
IIIMI Nl I .1 MI r.i SI SI SJ El
RLCORT FORHATS (20 CAIIO)
QL - QUICK LOOK
02 - DOURLE SCACEO QL
SD - SOURCE DATA HECOIII
AC - ACTION SUMMARY
1)1 - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
CONUI1IOM CODES (10 CARD)
M -
-V -
II -
Ii -
1 -
C -
II
MUST EQUAL
ALIERHATE (Used (("-
Multiple Valnos of a
r.iven Data Clement)
UNEQUAL
EQUAL OR GKEAIEK 1IIAN
EQUAL OR LESS IIIAN
CW.SEN1 ANY I.HIKY
(IIAHK OR /UIOS
Figure 'J--12. Retrieval Request Form to
U! Lain Quick Look Report
-------
Ul
Lfl
See reverse side for a
list of alI CDS data
elements ami (heir
alilircvi.il ions.
COMPLIANCE DATA SYSTEM
Report Request Form
_ 06
t i i
..i-
.r.o.*. AC.T.I.Q.N.S. .P.OR. >.Y.g.i.
i;,»J Mftf
lli°J Bin
LUSJ lALf..L Al
L!.°J ifl.
L'.tPJ fliliJltl tU P.fa i. i.1-1.-i-i i . .... i...... ... . . . .... . J
ll^ej lD.liAi!Lj IGil 11.0,01.6,0 .,,. i I
Itll H.1/ I
11.9J Lu-i_.-J U LL-LJ.
Lii5J L_i_i_»_J U Li ._!
(LIMIT - 100 III CARIIS)
iron lonuiii
ll.PJ &0j L...I LJ I ....... I
II IS II II II 14 II
troll liguilKCI KIIWOIO H((XJIB(C 10 «C(isi COMIDHHIHI D»i« i
Li_o_J Li_i_LJ I L. . i i ... I
r i n M n it n II :i
l IIPM'.J '0 4.1 IMAflllllB't
REQUIHED FOR SO REPOHI ONLY.
VALID ARE:
A - ALL DATA
C - CRITERIA MATCH ONLY
P - POIIIT & SOURCE
S - SOURCE ONLY
| | ..ki...111-1
QUICK IOOK IIIPOMT fORMAI
TIME.
DATE SUBHITTtn
RtTIIIIN REPORI TO.
HAIL STOP
'l I II II ''I' II II II It II II II II II II II II II II
f«lrr D«l. llr-vnll 10 b« lnclvdr.1 on i n r'
MIIISIONI IIPOII I OH Mil
l'l5J I l_J_J-l I ._L-I.J I L_l-.l I I ... I L^. ...J I ... I l_L_l_l_J l_i_._i.J I . . I I Lj-i^J
ill ii U n i; ii 11 M n II it ii >i )< ii '< i' ! si
ov.,1 lOiUMNt VAIIJI1 01 COLUMN 0*1* UIMIHK (uil -«»>- 101 lulli »i|,'t |
D*.*U«I«
...MIM. I.IM.HI
.
._... I J !__. _ . _ 1 I
" » » «
REPOm FORIWTS (20 CARD)
QL - QUICK LOOK
02 - ClOUIILE SPACED OL
SO - SOURCE DATA REPORT
AC - ACTION SIIIIHAHY
()T - QUESTIONNAIRE
(IS - MILESTONE
CA - COMPLIANCE-ACTION
CONDITION COOES (10 CARD)
M - MUST EQUAL
A - ALTERNATE (Used for
Multiple Values nf a
Given Data Element)
U - UNEQUAL
G - EQUAL OR GREATER THAN
I. - EQUAL OR LESS THAN
P - PRESENT AIIY fNIRY
n - DLAHK OR /rims
i1' 9-13. Retrieval Request Form to
Obtain Source Data Report.
-------
S.;o reverse side for a
Abbreviations.
io_jj Q5) u iR.g.q.'.o.H. V. .K5.P.S .
i i i i i ii
COMPLIANCE DATA SYSTEM
Rupert Request Form
'lAM^iCiiH I.J-iC.3.T .O.M£ ..... 1 .1 . I
TIMI
DATE SUBMITTED
REIIIRN REPORT TO.
HAIL STOP
l'l°J 1
I'.OI |_.
l'.0| | ,
l'.o| I .
i'i°J U
I'.OI 1 ,
M ,0) i ,
I'.oj l_i_
l'l°J 1 1
i . 1 1 1
, , i 1 1
..III
..III
.III
..ill
.III
i_i_J U
1 I 1 1 1
1 1 1 1 1 1 1 1 1 1 1 . 1 1 1 . 1 1 1 ... 1 1 , 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 ... 1 1 .. 1 I 1 1
1 1 1 1 1 1 I 1 1 1 1 1 1 1 1 I . 1 t, . 1 1 t 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 t 1 1 4 1 . 1 1 1 1
(LIMIT - 100 10 CARDS)
iron loiMtu
13,9J IM.5) L..J L,J
I I II II II II
1IOUIICI
i
. . 1
JT
LEVEL COOES (01 CARD)
REQUIRED FOR SO REPORT ONLY.
VALID ARE:
A - ALL DATA
C - CRITERIA MATCH ONLY
P - POINT J SOURCE
S - SOURCE ONLY
rtllwoio
, (wnomrui O»T» (LtKi«u|
l^i°J l_iiij l-i_,.-iJ l_ji_i__l LJi_i.) I»_.i J LJ1i.J
III II II II II II M II II II II
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
Q2 - DOUIJLE SPACED QL
SO - SOURCE DATA REPORT
AC - ACTION SUMHARi
QT - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
MfliilK'l llnlllu 10 4.1 nu.j»tfl»r>
QUICK IOOK UPOm lOHMAf
\*i°\ U_LaJ L.j_J_iJ Li.-1-L.J 1 i i .J Ui_i_._J l_i i I.J 1 i i ij 1 III! 1.1 I |_J 1 i i i..l
III II II 14 II II II M II II It II II 11 41 44 41 41 tl
I ....... J l.i i .J I ... I L,_i_J Lu_._vJ LJ
«i u ii n i« u U n ii ii tf
I' llopi
with HOMO Onlt | la
MuitfONi mpoai roRMAT
I'.yl 1. ._i_i J l..j.-i_Lj L.j-i-i.1 Li 1 I 1 L_i_i_. J Lj_a_iJ 1 I.I I-J Li . iJ L-i 1 l.J LJ i .J
III II II 14 1) II It II 11 II II 11 II 11 II 14 41 *l SI
owl ILMiiMNt VAtUM Of COIUMN DAfA ILIMIMri (USC 'BLNi1.' (UR BtAfli VAI I'l I
DA I A UA,A
I, I Ml HI f IIMINI
. ,
1 1 _»_. 1 1 . . I
CONDITION COOES (10 CARD)
M - MUST EQUAL
A - ALTERNATE (Used for
Mul tlple Values of a
Given Data Element.)
U - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
II - ni.ANK OR Zf DOS
Figurv: c)-14. Retrieval Request Form to
Obtain Milestone Report
-------
COMPLIANCE DATA SYSTEM
I
^
LJ
I
ice reverse 'aide for a
Xlus'l^r' Report Request Form
.0 ij i&3 i I i^fc,<>- lolJ 3 US PS MrtT °ft-£ M/ l 6 J To W £ , ,
i i i i i i ii ' > »° "
SI II li II
|i,o| \Atf>,clt>i \t-\ |ICUIHO 10 MUSS CO.HIII-IIM ptu iiffi.in
K°I i ... i i ,.. 1 1 , , 1 1 i , 1 1 1 1 ... i i ... i ii r.viti.ir.'..,
>.»!» 1 1 Irl III) '0 4.1 (.i*t»( |(Mi
QUICK IOOK mpoiir IORMAT
l*i?] 1 . i i-i-J l_i_l_iJ 1 i i iJ 1 i i i.J t i i i 1 L i t i 1 1 i i i J 1 1 i 1 1 1 1 l i J 1 i i 1
III US II M 1' U U 11 || M ]2 II JI 11 11 II If II SI
Intrr D*tt |U-yrU lo be Indudrd on *r|-ifl
It*l|p4 lo I)? (t.«rttlrrt i.|lh M^I<1) n,.|lm>. | II ( 1 II II III
"**' ilopl
Wild NOHO O«l,
-------
COMPLIANCE DATA SYSTEM
Ul
00
I
A
.ir.s^i'U11" Hcport Request Form
JAII SIIIIMIIHII
KCIIIIIN RfPORI III
HAH i;nin
1 I
ij-Ji
LL£J 1
lii£J
iJjOj |
lil°J
I 'u°J 1
(LIMIT
iron
r i
IfOI
i 'T
Ti i i u ' *° "
' n \i IB ij ii
4 7 9 if 30
D.r.S.Ci IM ll.^jjtLfti. 1
tXT,A,Ci fl| , , , . , , , . i . i . i , i . , , , , , i
.... 1 J 1 LEVEL COOES (01 CARU)
_, , , l 1 1 .......... i ... i .......... ,| RFQIIIPFII rn» <;n RFnnnr ran v
... I 1 ., 1 VALID ARE:
, i i I M ......................... .1 A - ALL DATA
. i , 1 1 | ... . ..,,,.....,....,..,.. .1 C - CRITERIA MATCH ONLY
- 100 10 CARDS) p - POINT J SOURCE
nVI",' , , , ,^c . S- SOURCE ONLY
lUTll il 1 i 1 (L.Di£i , 11 i I
I t f | || || |< Jl .. .- , ,..-,
REPORT FOItltATS (20 CARD)
QL - QUICK LOOK
Q2 - DOUBLE SPACED QL
SO - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
«Aiii»ri r All WO 10 ItfOOHKO 10 *£CtVi COnf lUMItAl OAIA (ItKlNllJ
II VUI It 1
liMHiJ 1 . . . 1 1 . . . 1 Li_i_Lj 1 . . . 1 l . . . l LJ ""k'tliin!.,
>l iiniim 10 ") OUHKIII;
i«,«i
4 1 l' II II II II 11 II II II II II II II 1} II II II 11
Inter OaU llfwi.li 10 bt liKlwdfd on Nrporl
lUIIrd I* I)) Ihiriclrri .Ilk mil IVIInn; 1 II 1 II II III
...i..< i. ... «UI..M..|lo/l
MIII1IOHI liroil IOIMAI
f1! rJ~l~Ji i' ii u' '11 ii ii ii ri ii u ii n ii 11 11 11 n ii
IOMI (OIUUHI VAIUU O» COIUMN DAIA ItlMINII lull Tim- I0« BlAlll »«U1|
OAIAOAIA 1 « . . 1 1 ^ | 1
CONDITION CODES (10 CARD)
M - HUST EQUAL
A - ALTERNATE (Used for
Multiple Values of a
Given Da Id Element)
1) - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
0 - OI.ANK OR ZEROS
Figure 9-16. Retrieval Request Form to
Obtain Questionnaire
-------
COMPLIANCE DATA SYSTEM
<£>
I
See reverse side for a . i . w - i-* . . . . w.w.i-,,. T|H£
el^L'ln/ttr' ^port Request Form
io.ii ,ii,Mi i i iA.C.T.IO.M .S.U-MMAR.^. .F.o.R. .Ht.S.HJl.P.S. i .,, i
ii ri i i n ' " it « «
/ ^ V it iJ i»
n.oi w.TP.Ei i£tl nil. i ... . ..... , ........ i
YJJ "y !";' '9* n*' -'' -' ' --'-'-1 '» ^
I'.oj | , , , , i 1 , LEVEL COOES (01 CARD)
II. o, , , , . i | 1 | VALID ARE:
|i.0| I , , , | | 1 ,.,,.,.,. , ,| A - ALL DATA
M.0| Li I . 1 1 1 ........,) C - CRITERIA MATCH ONLY
(LIMIT - 100 10 CARDS) P - POINT & SOURCE
;""Tc'" , , , irnC I S- SOURCE ONLY
li.oi iA>i i . I 1 . I IC.D.Sk .... 1
llfOHI IIOUKCI fAIIKOID IKQUIMC 10 ACCHi COWIOlllll*L MIA ClIKKISI
|J.Q| fiLLf £\ l-Lmifi Lt i i I I i i . i i . . . 1 I . . '. I LJ -"'.""'"i
ill li ii it "" ii li Jl ti IT li Ji it t> "..
M0>.ll>(l IIMII1.;) >0 40 (HABlCllfii
QUICK IOOK tlPOHI lOHMAI
1 T r*""'"1! 1 II H " II II II II II II 11 II Jl 11 II H II II 11
IMti lull llr**"!! to tor Int.uJ'd en Krporl
!:::!::i: is ir'^rxx*11- L^^ u_^ L^ L^ L.-^ y
WHkNOHOOnlf «u(l|il * ! 1 lort
MI1I1IO.II IIPOII IOIMAI
iJ/ i ' ' ''i rL~t~Ltt ii' ii II n ii'~' II ii ll II n ii «i «< i' ii si
0.-.1 (OIUMHl VAUJII Of COtUMN DAIA ILIMINM (OSt SltlK" fOD 61 Allk VA(U( | . . .
o«i« OAIA si1'1"1!! *~JiTJ
DA1E SimHITiril
RETURN RFPOnr TO
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
Q2 - DOUliLE SPACED QL
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE (Used for
Multiple Valims nf a
Given Data Element)
U - UNEQUAL
G - EQUAL Oil GREATER THAN
L - EQUAL OR LESS THAN
P - PRESLNT ANY ENTRY
II - DLANK Oil ZEROS
n<: re 9-17. Retrieval Request form to
01)tain Ac(. ion Summary
-------
COMPLIANCE DATA SYSTEM
O
I
See reverse side for a
llsl of all CDS data RpnOTt RPflllP
elements and their M I, |J U I I M C l| U L
10^ fifa t i iF.Y&.l, ,c,o>iP.u,A.H.c.e. ju.r.i.oHS,
1 1 1 1 1 1 II »
** "* ii la
|i,o| |D,f,A,Ci iQl |J|O.QlJBrt. . i ...,,. ,|
II 0| | | | | I
llioj , _ _ , , , i
I'.O) | | 1 . 1 t | i . . 1 . . i l 1 ... . . i ,. 1
I'.Oj l.i.lll i i . i . i i i 1 . i i i i i . i , i . . . i i i , 1
(LIMIT - 100 10 CARDS)
(iron IIIMIII
li.ol lC.Al 1 . 1 1 . 1 1 ....... 1
IPOIf SiaUIHCf PAIIWOIO (MbUIMD 10 ACCISS COlHDtHllAL OAIA UfK(Nfl)
Lii£j IVr.rgj |5,H,»VEI 1 . , , l 1 . . . i l . . . 1 l . . . i
1101111*1 null!" 10 *ri!ltri .Ich NCM« Oplloni 1 ... 1 1 1 1 1
ll.llrd I<1 110 WHh Sl»dl.d ll,.dln« Y) If H~ Vr II II
MIIISIONI UPOH IOIMAI
f'i rt~'~'' i ~ it ir'~"'~'ii ii ti ii ' ii ii it ii ii
0*1 * 0*1 *
st Form
II 10 I]
JO ||
LEVEL CODES (01 CARD)
REQUIRED FOR SO REPORT ONLY.
VALID ARE:
A - ALL DATA
C - CRITERIA MATCH ONLY
P - POINT & SOURCE
S - SOURCE ONLY
u 7:»"'::in..
i i . 1 1 I., i i 1 1 i i i
u u u u u ii
"n^ u1 !, W W
T Slop*
F Pf
11 It II II II SI
1...-,-. 1 1 . . . 1
TIME
DATE SUOMITTFI)
RE1URN REPORT TO
REPORT FORMATS (?.0 CARD)
QL - QUICK LOOK
Q2 - DOUIJLE SPACED QL
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE (Used for
Multiple Valims of a
Given Data Element)
U - UNEQUAL
G - EQUAL OH GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - flLAHK OR /FHOS
Figure 9-18. Retrieval Request Form to
Oi.tain Compliance Action-Report
-------
Sen ri'vrrio '-Ido fur ,1
COMPLIANCE DATA SYSTEM
nut.
elell^/'tU111 Hoport Request Form
alilirpvl.il Inn}
,0.1, 4,fc, . , ,M. .PAD. T-E.RAI.T: .CPA^././IAIC^. .Rt.rf.K.r. ,
1 1 « > i 1 ll i* Id 11
n.oi i3.tv», i .... i 1
L'-i°J l43j£r£j HJ l§£i_j_L_i J-LJ L, j LI u i i_i LL..^ ..1,1 LEV£L C(l()ts '"' Cfl|1">
I'.Oj |4.7".^,£| 141 £3' . . > ' > . . i . i , . . i , i| RF',ll|nr(i f"P r-0 ',,iit .oMinixui OAUIIII-IMM
I!I>'I t 1^1 1' '0 «'l ' »«-, MI
QUICK lOtIK IroHriOKMil
|<,o| ^0,ll,Dj IS^^EJ (CLVi^Ali iSiT.A.Bi ipi^^ifc) i/j.TiP,Ej |t>iT,AiCj tD,T|SiC.| (JJi^jEiJj iy,S|T,pj
IT i ; i ii fi ' ii n u 11 M n u n u u "u u ii u u
!!"M'?!" !m LM;"-!"H "i'» "7," °"'""; l^JlRAJ Ll. i L) lj_J_lJ LL-l_lJ l_l_._vl U
| l.l|,4 , lin UMk ,,,^..i »..,,., ^j -s» H .-Jj fJ- (f ^j (j- (| -^ -j,
MIIISION, RIPOII IOIMAT
l»,0| | . , , 1 1 , , , 1 1 , , , 1 1 . . 1 1 1 , , , 1 | . . . 1 1 . . 1, 1 1 . , 1 1 1 , 1 1 1 1 1 , . 1
ii« ii i) H ii ii 11 ii ii n u i< H )i ii ii ii ii u
DAH SUOMMItll
RE1URN REPORI TO
rlAIL STOP
REPORT FORMATS (20 f.AMO)
01. - QUICK LOOK
02 - DOUBLE SPACED QL
SO - SOURCE DATA RCPOIil
AC - ACTION SllfUARY
01 - QUISIIONHAIRT.
MS - MILESTONE
CA - COMPLIANCE -AC. 1 ION
CONDITION CODES (10 CARD)
H - iniSI EQUAL
A - Al IERNATE (Used for
- Multiple Valiios nf n
Given Data Element)
U - UNEQUAL
(, - IIJUAI. Oil C.REAKR 1IIAN
L - EQUAL OR LESS IIIAN
P - PHrSI.HI ANY IHIRY
. , . .
'« ' 'si1 Hr-'-M
'J-19. Ketrioval K.
Obt.i in PSD Report
onii to
-------
To execute the Retrieval Program, use the JCL as shown in Figure 9-20.
Use a Job Card which allows for a sufficient amount of time and print lines.
One minute and 20,000 lines should be adequate for most Quick Look Reports.
Requests for multiple reports and Source Data Reports are likely to need more
time and more lines. Refer to the NCC-IBM User's Manual for detailed informa-
tion about the Job Card. Figure 9-21 shows a job card for multiple copies;
Figure 9-22 shows a job card for 100,000 lines of output.
9.5 Retrieval Edits Performed by System
The Retrieval Program edits the request cards, 01, 10, 20, 30, 40 and 50
to determine if they are convertible into logic which the system can process.
Errors on the request card will appear as Error Messages on the Edit Report.
These Error Messages are classified as "WARNING" or "FATAL".
Table 9-1 lists the type of edits performed, the correct possibilities and
the action taken by the system if an error is detected. Table 9-2 contains a
list of all possible Error Messages and the errors which are the cause of
their appearance on the Edit Report. Figure 9-23 shows a typical Retrieval
Edit Report.
9.6 Special Retrieval Features
9.6.1 String Search
The Character String Search is available as a selection option for CDS
retrievals. This option is most useful for the data element Source Name
(SNME). To initiate Character String Search, the string of characters must be
enclosed by "@" on the 10 card on the retrieval. The user should keep in mind
that the maximum number of digits for the value field on the 10 card remains
at 20 including the "@".
-142-
-------
AU i nun
i 2
/ /
'*
/ *
/ /
//
O 1
1 O
20
30
40
' V
/*
1
E
R
C
R
E
4
P
O
N
T
-
O
i
A
U
T
V
-
I
i
i
r
i
TRC
i
i
E
S
1
i
Y
-
-
i
C
5
-
10
P
D
O
-
-
-
HI
fi:
S
0
-
-
12
J
r
t
5
-
-
i]
O
N
i
X
14
B
T
E
E
D
-
15
X
C
D
;
-
IS
(
R
C
-
-
i;
a
M
C
*
-
-
II
a
T
D
-
-
li
a
r
S
-
?o
a
r
R
-
-
1'iu.iHAM NAME REIRIEVAL JOB CONTROL
21
C
T
-
TASK NUMIIEII
2!
D
V
-
-
n
S
n
24
Y
Al
HI
SI
Al
hi
n
TF
ft!
n
P
-
u.
fi
t
if
-
H
I
It
.1
;i
V
u
SI
>R
-
2)
M
-
R
r
a
R
.5
'in
u
.0
21
i
-
t
Ti
_l
r
L
II
K
-
n
i
-
Al
ir
01
Al
L
[
01
01
M
i
s
/'
pi
r
11
SI
V
1
Jl
)
kill
:T
H
i!
1.
11
r
-
i?
/
1
>i
,7
|
J
;[
-
])
V
Mi
151
ei
IT
II)
a
m
-
M
U
VI
f
.1
«
W
r
)S
S
-
;.
ii
7
f
1
15
3S
E
-
<
IT
L
IT
c;
^
31
R
n
IF
7
ID
sr
L
11
-
-
1
;
i
1
II
C
li
-
n
Ul
ST
1
RE
tl
40
D
T
tr
pi
r
41
/
-
A
3
'!)
It
r
42
--
:0
K
IA
A
41
-
-
0
-
-------
AIITIKill
1 1
/ /
/ *
/*
//
//
//
/*
1
E
R
C
R
Ik
E
<
P
O
N
T
Ll
0
s
A
U
T
V
L-
F
me
11:1.
f
i
T
I
a
1
i
E
S
!
1
i
Y
i
C
S
lie ohlalnli
10
P
0
a
i
n
R
S
0
II
J
r
E
5
t
1)
O
N
i
X
-
14
B
T
E
E
0
li
X
C
D
1 r.o
li
(
R
C
i.
ll
a
M
C
*
itra til
II
a
T
D
\y
i>
a
r
S
.-
20
a
r
R
t
IIKKUIAM NAML «tl«lfVAI
rrli li'Vjl n.ilpul
21
C
f
1
21
D
V
1 1
23
S
n
?<
Y
J
n
P
r
21
/.
-
-
J7
V
-
CI
-
21
i
-
n
i
-
10
i
-
ii
.t
-
-
V
i
-
3)
/
IOH oONVKlll.
>4
I
IS
l
-
34
3
-
})
)
-
11
i_
-
3)
X
-
40
U
-
-
41
S
-
-
42
E
-
-
43
R
-
44
-
45
1
-
TASK NUM1IKH
46
D
-
41
/
-
41
-
-
4)
-
-
U
SI
-
S2
-
-
-
»
-
-
11
55
16
SI
-
-
SI
-
iS
-
OATt
U
--
-
(1
-
(2
-
()
-
(4
1 Page
lot
IS
w
-
-
o
-
M
--
-
(3
-
)0
-
II
-
-
12
-
-
CAI1I)
NIIMIIEI1
13
-
-
14
-
-
IS
-
-
II
-
i;
-
11
-
n
-
-
-
1C
-
4-
I
Where:
ill
aaaa
rr
r
n
Is
I .s
Is
Is
the User1
the User1
s Initials
H Account Number
the User's Remote Number
the User's Region Numbcr
Is the User's Region Number or State Code;
Valid Values are 1-10, TN, SC, NE, etc.
. Retrieval Joh Cont.ro 1 for
MuHiple Copies
-------
Ul
I
AUTIKUt
1 2
)'/
/*
/*
//
//
u
/*
3
E
R
C
R
t>> Ulll.llllll llu'H of prlnlfd ,,nl ; U . Willii.ul II.
default v.ilni: U .'O.lli ll III,
10
P
0
3
t
II
R
S
E
0
-
i?
J
1
r
X
5
I)
C
N
/
E
14
a
T
E
C
0
>ll
IS
(
X
D
16
a
n
C
c
*
i..
i/
a
M
D
II
a
T
S
V
IS
a
r
K
-
»
C
r
T
'.:
21
D
V
1
a
S
n
i
i)
Y
14
P
li,
n
i
-
2C
V
.1
2J
i
:i.
21
-
21
i
r.
K>
L
-
Jl
»
i!
1
))
0
-
34
0
3i
)
M
I
}l
\
-
-
11
U
-
-
-
b spi'i
39
S
-
40
E
(i
R
-
"
42
-
-
TASK N1JMDKI1
>ATK
|,,l <-.irri, II,,:
(J
-
-
44
D
-
4i
(
4C
4)
41
-
4j
-
Ml
-
-
SI
-
S?
...
5J
U
-
-
51
-
S6
-
bJ
-
!>l
1>
-
4
ci
-
-
62
-
-
(3
-
(4
-
U
-
-
-
(6
-
-
Pago
of
i/
-
(4
~
-
E»
-
-
10
-
-
II
-
H
-
-
-
CAIII)
NIIMIIL'II
/)
-
-
-
14
-
:
IS
-
K
-
II
-
-
II
-
-
/J
-
-
Id
;
-
Where:
aaaa
r r
r
n
the User ' s In i t.ials
the User's Account Number
fs
Is
Is
Is
Is the User's Region Number or State Code;
Valid Values are .1-10, TN, SC, NE, etc.
the
the
User1s
User's
Remote Number
Re<) i on Number
Figure 9-22. Retrieval Job Control
100,000 Lines of Output
for
-------
TABLE 9-1
RETRIEVAL PACKAGE EDITS
Card
Type
Item Checked
Correct Possibilities
Action if in Error
01
Level
Blank, S,P,A,C (Default = A)
If SO format requested, it
is ignored if blank or other
Region Number Required for Standard Milestone Fatal - Processing stops
after EDIT
Number of 01
Cards
One
Only first 01 card accepted
10
Data Element
Listed on Report Request Form
FATAL - Processing stops
after EDIT
Condition
M,A,0,G,L,P,B
FATAL - Processing stops
after EDIT
Value
1) Anything
1) Ignored if not blank for
condition P or B
2) Numeric for "numeric" items 2) FATAL - Processing stops
i.e., REGN, STTE, CNTY, SRCE, after EDIT
PTNO, ATPE, DTSC, DTAC, STAC
3) Number of Digits less than or 3) Fatal if the wrong length
equal to number of digits on is used
Report Request form, max of
20 characters.
Number of 10
Cards
0 - 100
FATAL - Processing stops
after EDIT
20
REPORT FORMAT
1) QL, SD, AC, OT, Q2, MS CA
Up to three reports are
available from one retrieval
1) Processing will continue
if at least one valid
FORMAT
Number of 20
Cards
FATAL - Processing stops
after EDIT
-146-
-------
TABLE 9-1 (Continued)
RETRIEVAL PACKAGE EDITS
Card
Type Item Checked Correct Possibilities
30 REPORT SEQUENCE List on Report Request Form
DATA ELEMENT Total 40
SEQUENCE LENGTH
40 QUICK LOOK List on Report Request Form
DATA ELEMENT
QL Length Total length (including one
blank between each item)
132 with NOHD: 110 without NOHD
Nur.ir.er of 40 1) 1 if QL FORMAT requested
Cards
2) 0 if no QL FORMAT
50 VARIABLE MILE- List on Report Request Form
STONE DATA (BLK1, BLK2 EXCLUDED)
Column Values Must be present
Relation to 1) MS must be requested on 20
other cards
Number of 50 One
Cards
ALL General CARD 01, 10, 20, 30, 40, 50
TYPE
Action if in Error
FATAL - Processing stops
after EDIT
FATAL - Processing stops
after EDIT
QL Format Request ignored
QL Format Request ignored
1) QL FORMAT Request ignored
2) QL FORMAT ASSUMED (if
only one 40 card)
FATAL - Processing stops
after EDIT
FATAL - Processing stops
after EDIT
FATAL - Processing stops
after EDIT
MS FORMAT Request ignored
FATAL - Processing stops
after editing
-147-
-------
RETRIEVAL
TABLE 9-2
PACKAGE ERROR MESSAGES
ERROR MESSAGE
CAUSE
"FATAL - INVALID RETRIEVAL CARD"
"WARNING - DUPLICATE TITLE (01)
CARD"
"FATAL - OVER 100 SELECTION
CRITERIA"
"WARNING - BAD LEVEL,
SD DEFAULT - ALL"
Card type not 01, 10, 20, 30, or 40.
More than one 01 card type entered,
the first one is accepted.
Limit of one hundred card type 10
cards exceeded.
The level code entered on card type 01
is not S, P, A or C. If SD format is
requested, code will default to level
'A1 .
'FATAL - INVALID CONDITION"
"WARNING - VALUE NOT USED
FOR COND P OR B"
'FATAL - THIS VALUE MUST BE
NUMERIC"
"WARNING - VALUE TOO LONG
(TRUNCATED)"
"WARNING - INVALID REPORT FORMAT
WILL CONTINUE IF ANY VALID
FORMATS"
"WARNING - QL FORMAT ASSUMED:
"FATAL - REPORT FORMAT (20)
CARD REQUIRED"
"WARNING - QL (40) MISSING,
QL DELETED"
The condition code entered on card
type 10 was not M, A, U, G, L, P or B.
An entry was made in the VALUE portion
of card type 10 with a CONDITION of P
or B. These conditions do not utilize
any VALUE.
An alphabetic digit (other than 0-9)
was entered in the VALUE portion of
card type 10 for a data element which
must be numeric, e.g., the value for
DTSC must be a date consisting of 6
digits (0-9).
The number of digits entered in the
VALUE portion of card type 10 was
larger than the number of digits
specified for that data element on the
list on the input form.
A code other than QL, SD, AC or QT was
entered on card type 20.
A card type 40 was entered, but QL was
not requested on card type 20. QL
will be assumed as entered.
No card type 20 was entered. This
card type is required.
No card type 40 was entered, although
QL was entered on card type 20. QL
report format is ignored.
-148-
-------
TABLE 9-2 (Continued)
RETRIEVAL PACKAGE ERROR MESSAGES
ERROR MESSAGE
CAUSE
"WARNING - QL TOO BIG,
QL DELETED"
"WARNING - LEVEL FOR SD
FORMAT ONLY"
'FATAL-DUPLICATE SEQUENCE
(30) CARD"
'ITATAL - SEQUENCE KEY TOO LONG'
'FATAL - INVALID MS DATA
ELEMENT COMBO"
'FATAL - REPEAT AND POINT OR
ACTION ON QL"
PASSWORD NOT ACCEPTED - NO
CONFIDENTIAL DATA WILL BE
PRINTED"
"PASSWORD HAS BEEN ACCEPTED -
CONFIDENTIAL REPORT - FOR EPA
INTERNAL USE ONLY"
The total length of the QL line is
greater than 110 digits with the
default header information oc it is
greater than 132 digits with NOHD.
A level code was entered on card type
01, but SD report format was not
requested. The level code is for SD
reports only.
More than one card type 30 was entared.
The sum of the number of digits of tha
data elements requested for the user
sequence (card type 30) was greater
than 40. (38 for AC, 39 for QT).
Only source level data elements may be
requested on a Milestone together with
repeating pollutant data on a 50 Card.
The Card 40 may specify only source
level data together with repeating
pollutant data on the Quick Look.
Either no password was used or an
incorrect password was used. "c
confidential data will be selected,
sorted or printed on any output report.
When a correct password is used, each
output report page is labeled as
confidential.
-149-
-------
Ln
O
I
I.I II II XI IUII 111 I ,,t I
I fiiM'l I tin i pill M-.II n
cii.x u'> n vi i i in i ui (M-,
ll I l| oil I III UK U
DAI* Minim i.niir. 1 1 1 UN
CAII SI I.I Till if. lUMAl OH I I S S
0*11 S( rl rill I fi (I1IIAL llh CHIAII
Heron) ''.rntiiMi HiriiKi inh^Ai ui KS
S(-
-------
Example:
10 SNME A @EXXON@
10 SNME A QDUPONT8
These will allow the retrieval to find all the following names:
Garden Mall Exxon
Sports Complex Exxon
Exxon Rsrch & Engnr
Exxon Terminal
El Dupont
Dupont/Chemicals
Dupont Company
SI Dupont/Pigments
No other retrieval features are affected by this function. All other
features (selection, sorting, or printing) work in their original manner.
9.6.2 Quick Look Comments
The availability of comments on a quick look has been added to the CDS
Retrieval. Comments are accessed by placing a level code, S for Source level
comments, p for Point level comments, A for Action level comments and C for
Comments from all levels, in column 79 of the Quick Look Format 40 Card.
Users are cautioned that a data element from each level from which comments
are requested be present on the Quick Look Format card. Users are further
cautioned that illogical sort requirements may cause comments to appear at
inappropriate locations within the report. For example, do not select source
level comments for a QL sorted by action type.
-151-
-------
9.6.3 Retrievals Available Through TRC
Uninspected Source Retrieval
This is a retrieval report listing all the Uninspected Sources in a
region.' TRC needs the following information to create this retrieval report;
1. The inspection action type(s) (the action not performed).
2. The period of time during which the retrieval report is for.
3. The other selection criteria i.e., CLAS, APCD APST .... etc.
4. The Quick Look report line data elements. Once TRC has this
information. TRC will run the programs necessary and print tne
Uninspected Source retrieval report on the regions printer. TRC
will also call the region to give them the Job number of the
special report.
9.6.4 CDS QUERY
The CDS Query is now available to regions having a T£0 o- '*'('..'&;
-------
WELCOME TO CDS/QUERY -
THIS SESSION MILL PROVIDE CDS SOURCE DATA REPORTS AT YOUR TERMINAL YOU
WILL BE PROMPTED FOR AN 11 DIGIT (STATE, COUNTY & SOURCE AFTER EACH SCREEN
YOU MAY END BY ENTERING "E" OR CONTINUE BY HITTING THE (RETURN/ENTER) KEY
ONCE YOU HAVE FINISHED WITH A FACILITY, YOU MAY BEGIN ANOTHER.
ENTER A VALID 11 DIGIT (STATE, COUNTY & SOURCE) OR "E"
19126060381
FEDF NON-FED RDE1
STATE LA COUNTY IBERIA APCD 6 PSD RDE2
COUNTY 1260 SOURCE 60381 AQCR 106 CITY APST P PLANNED RDE3
SOURCE TEXACO-RABBIT ISL A STATE REGIST IN VIOLATION
SIC RDE6 PSD-LA-381
ADDRESS APPROX 11 MILES SE NEDS XREF
RDE4 STAFF MEMBER E31 S. SPRUIELL
CITY, STATE IBERIA PARISH LA PRIORITY
RDE5 LAST-UPDATE 10/13/82
** TO CONTINUE ST CNTY SRCE - 19 1260 60381- HIT (RET/ENT) - TO END - ENTER "E"
COMMENT 1 GARY GIORDANO, BOX 60252, NEW ORLEANS, LA.
COMMENT 2 504-524-8511, EXT. 1165
COMMENT 3 CONSULTANT: KEITH TIMBRE, METEOROLOGIST
COMMENT 4 KEMRON ENVIRONMENTAL SERVICES
COMMENT 5 16550 HIGHLAND ROAD
COMMENT 6 BATON ROUGE, LA. 70808.
SOURCE COMPLIANCE STATUS 1 IN VIOL-NO SCHEDULE
SOURCE EMISSION CATEGORY 0 UNKNOWN LOAD DRV
FACILITY CAPACITY ROE 9
RDE 10 RDE 11 RDE 12 CLASS A2
POLLUTANT - N2 NITROGEN OXIDES
COMPLIANCE - 1 IN VIOL-NO SCHEDULE
EMISSION CATEGORY - 2 100 to 1000 TPY
AQCR INDICATOR -
LOADING -
** FOR NEXT REPEATING POLLUTANT - HIT (RET/ENT) - TO END - ENTER "E"
** TO CONTINUE ST CNTY SRCE - 19 1260 60381- HIT (RET/ENT) - TO END - ENTER "E"
POINT NUMBER 000 MULT SOURCE COMPL 1 IN VIOL-NO SCHEDULE
STATE/LOG REGUL CMS2
POLLUTANT SOURCE-SIP NO SCHEDULE
SOURCE EMIS CAT 0 UNKNOWN RDE?
DESCRIPTION ENTIRE SOURCE CAPACITY
SCC8 CODE
QUERY 1 of 4
-153-
-------
** TO CONTINUE ST CNTY SRCE - 19 1260 60381 - HIT (RET/ENT) -TO END- ENTER "E"
COMMENT 1 NATURAL GAS COMPRESSOR STATION EXPANSION.
ACTION 01 SCHD 11/25/80 ACHV 11/25/80 ACT-TYPE Jl
PSD DETERMINED APPLICABLE
STAFF C07 TRW RESULTS 01 ACTION ACHIEVED RDE8
ACTION 02 SCHD 11/25/80 ACHV 11/25/80 ACT-TYPE J2
PSD APPLICATION SUBMITTED
STAFF ALL CAROL LINDSEY RESULTS 01 ACTION ACHIEVED RDE8
ACTION 03 SCHD 12/26/80 ACHV 2/9/81 ACT-TYPE J3
PSD APPLICATION DETERMINED COMPLETE
STAFF C07 TRW RESULTS 01 ACTION ACHIEVED RDE8
COMMENT 1 INCOMPLETENESS LTR SENT 1/19/81.
COMMENT 2 COMPLETENESS LTR. SENT 3-18-81.
ACTION 04 SCHD 6/17/81 ACHV 6/17/81 ACT-TYPE J6
PSD PUBLIC NOTICE PUBLISHED
STAFF ALL CAROL LINDSEY RESULTS 01 ACTION ACHIEVED RDE8
ACTION 05 SCHD 7/23/81 ACHV 7/27/81 ACT-TYPE J8
PSD PERMIT ISSUED
STAFF RESULTS 01 ACTION ACHIEVED RDE8
ACTION 06 SCHD 9/15/81 ACHV 9/15/81 ACT-TYPE 03
INITIATION OF ON SITE CONSTRUCTION/PROCESS CHANGE
STAFF E31 S. Spruiell RESULTS 01 ACTION ACHIEVED RDE8
** TO CONTINUE ST CNTY SRCE - 19 1260 60381-HIT (RET/ENT) -TO END- ENTER "S"
ACTION 07 SCHD 2/17/82 ACHV 2/17/82 ACT-TYPE J9
PSD FACILITY STARTUP
STAFF MO 2 MARY TUCKER RESULTS 01 ACTION ACHIEVED RDE8
ACTION 08 SCHD 4/6/82 ACHV 4/6/82 ACT-TYPE G4
SIP REQUEST TO S&A TO OBSERVE SOURCE TEST
STAFF RESULTS 01 ACTION ACHIEVED RDE8
ACTION 09 SCHD 4/26/82 ACHV 5/1/82 ACT-TYPE 53
SOURCE TEST OBSERVED BY EPA
STAFF C04 PEDCO RESULTS 01 ACTION ACHIEVED RDE8
COMMENT 1 COMPRESSORS TESTED WERE 1-2-6-7
ACTION 10 SCHD / / ACHV / / ACT-TYPE G6
TRIP REPORT
STAFF RESULTS RDE3
ACTION 11 SCHD 6/26/82 ACHV 8/24/82 ACT-TYPE 58
EPA SIP SOURCE TEST SUBMISSION
STAFF MO2 MARY TUCKER RESULTS 99 PENDING RDE8
ACTION 12 SCHD 6/26/82 ACHV 8/25/82 ACT-TYPE Gl
REQUEST FOR REVIEW OF SIP SOURCE TEST
STAFF RESULTS 99 PENDING RDE3
ACTION 13 SCHD / / ACHV / / ACT-TYPE G7
TEST REPORT TO CONTRACTOR
STAFF RESULTS RDE8
QUERY 2 Of 4
-154-
-------
** TO CONTINUE ST CNTY SRCE - 19 1260 60381 - HIT (RET/ENT) -TO END- ENTER "E"
ACTION 14 SCHD / / ACHV / / ACT-TYPE G8
TEST REPORT FROM CONTRACTOR
STAFF RESULTS RDE8
ACTION 15 SCHD / / ACHV / / ACT-TYPE G9
TEST REPORT TO ENFORCEMENT
STAFF RESULTS RDE8
ACTION 16 SCHD 9/25/82 ACHV 9/20/82 ACT-TYPE G2
S&A REVIEW OF SIP SOURCE TEST
STAFF C04 PEDCO RESULTS 98 DISAPPROVED RDE8
ACTION 71 SCHD 10/7/82 ACHV 10/7/82 ACT-TYPE 55
EPA SIP NOTICE OF VIOLATION
STAFF E54 GEORGE KELLEY RESULTS 01 ACTION ACHIEVED RDE8
COMMENT 1 CO LIMITS AT COMPRESSOR f6 WERE EXCEEDED. NOX LIMITS FROM
COMMENT 2 GENERATOR fl and f2 WERE EXCEEDED ALSO.
ACTION 73 SCHD / / ACHV / / ACT-TYPE 59
EPA CONFERENCE WITH FACILITY
STAFF RESULTS RDE3
POINT NUMBER 001 MULT POINT CMPL 1 IN VIOL-NO SCHEDULE
STATE/LOG REGUL CMS2 C
POLLUTANT N2 POINT-SIP NO SCHEDULE
PT EMIS CAT 2 100 TO 1000 TPY RDE7
DESCRIPTION 1650 HP 1C COMP ENG (6) CAPACITY
SCC8 CODE
** TO CONTINUE ST CNTY SRCE - 19 1260 60381 - HIT (RET/ENT) -TO END- ENTER "E"
POINT NUMBER 002 MULT POINT CMPL 2 IN COMPL-SOURCE TEST
STATE/LOG REGUL CMS2 C
POLLUTANT N2 POINT-SIP NO SCHEDULE
PT EMIS CAT 2 100 to 1000 TPY RDE7
DESCRIPTION 1650 HP 1C COMP ENG (7) CAPACITY
SCC8 CODE
** TO CONTINUE ST CNTY SRCE - 19 1260 60381 - HIT (RET/ENT) -TO END- ENTER "E"
POINT NUMBER 003 MULT POINT CMPL 1 IN VIOL-NO SCHEDULE
STATE/LOG REGUL CMS2 C
POLLUTANT N2 POINT-SIP NO SCHEDULE
PT EMIS CAT 1 LESS THAN 100 TPY RDE7
DESCRIPTION 360 HP GEN DRIVER (1) CAPACITY
SCC8 CODE
** TO CONTINUE ST CNTY SRCE - 19 1260 60381 - HIT (RET/ENT) -TO END- ENTER "S"
POINT NUMBER 004 MULT POINT CMPL 1 IN VIOL-NO SCHEDULE
STATE/LOG REGUL CMS2 C
POLLUTANT POINT-SIP NO SCHEDULE
PT EMIS CAT 1 LESS THAN 100 TPY RDE7
DESCRIPTION 360 HP SB GEN DRIVER (2) CAPACITY
SCC8 CODE
QUERY 3 of 4
-155-
-------
** TO CONTINUE ST CNTY SRCE - 19 1260 60381 - HIT (RET/ENT) -TO END- ENTER "E"
** END PROCESSING SOURCE: 19 1260 60381
ENTER A VALID 11 DIGIT (STATE, COUNTY & SOURCE) OR "E"
*** CDS/QUERY SESSION SUCCESSFULLY COMPLETED
QUERY 4 of 4
-156-
-------
This exec will prompt the user to create card types 1-8 (new, change, or
delete) and will submit a live or dummy edit. The following is an example of
"INPUT":
? INPUT
THIS EXEC WILL PRODUCE FORMATTED CDS EDIT TRANSACTIONS AND SUBMIT A CDS EDIT RUN
- HIT CARRIAGE RETURN - FOR NO DATA ENTERED
- ENTER 'END1 - FOR NO MORE DATA TO BE ENTERED
- HIT ATTN OR BREAK - FOR NO MORE DATA FOR PRESENT CARD
- ENTER 'EXEC *' - IN RESPONSE TO 'EXEC BREAK1
ENTER CDS EDIT TRANSACTION CARD TYPE (1-8) ->1
ENTER TRANSACTION TYPE - N FOR NEW
C FOR CHANGE
D FOR DELETE ->N
E;;TZ?. 2 DIGIT REGION CODE ->04
E!!TER 2 DIGIT STATE CODE ->42
ENTER 4 DIGIT COUNTY CODE ->0220
ENTER 5 DIGIT SOURCE CODE ->60021
ENTER 3 DIGIT AQCR CODE ->
ENTER 4 DIGIT CITY CODE ->
ENTER SOURCE NAME ->
SOURCE NAME REQUIRED ON NEW ENTRY...
ENTER SOURCE NAME ->NEW SOURCE NAME
ENTER STREET ADDRESS ->***
ENTER CDS EDIT TRANSACTION CARD TYPE (1-8) ->2
ENTER 2 DIGIT STATE CODE ->42
ENTER 4 DIGIT COUNTY CODE ->220
ENTER 5 DIGIT SOURCE CODE ->60021
E;;TSR is DIGIT CITY NAME ->COLUMBIA
ENTER 5 DIGIT ZIP CODE ->END
ENTER CDS EDIT TRANSACTION CARD TYPE (1-8) ->END
WILL THIS BE A LIVE EDIT OR A DUMMY EDIT?
ENTER LIVE IF YOU WISH TO SUBMIT A LIVE EDIT ->
ENTER DUMMY IF YOU WISH TO SUBMIT A DUMMY EDIT ->DUMMY
ENTER ACCTUID? A026CDSYP
ENTER BIN/BOX? M EXC
ENTER YOUR REMOTE NUMBER (NNN), DEFAULT 20
REMOTE NR? 37
THIS IS A DUMMY EDIT THIS IS A DUMMY EDIT
JOB 4766 EPACDS SUBMITTED
? LOC 4766
JOB 4766 EFACD366 AW EXEC C=A POS=83 PRI=07
-157-
-------
9.7.2 REPORT
The REPORT exec allows a CDS user to run a CDS retrieval on WYLBUR without
extensive WYLBUR or JCL knowledge. The program prompts the user for all the
necessary retrieval card types and will run the retrieval and/or save the
retrieval cards in a data set. Figure 9-24 is a sample of the exec "REPORT"
which may be invoked by logging onto WYLBUR and entering the command 'REPORT'.
9.7.3 TABLES
The CDS user may get one or more copies of the Action, Results, and/or
Staff tables by using the TABLES exec. After typing in 'TABLES', the user
will be prompted for region/ table types desired, and number of copies
desired. The exec will submit a job which will print at the user's remote
printer with the 4 letter box code entered when logging onto WYLBUR.
-158-
-------
REPORT
IF YOU ENCOUNTER " EXEC 3REAK "
ENTER - EXEC *
TO CONTINUE THE EXECUTE PROGRAM
ENTER YOUR REGION CODE (00 THRU 11)
REGION CODE? 01
ENTER PASSWORD FOR RGION 01 OR RETURN FOR NONCONFIDENTIAL
PASSWORD?
CARD 01 - REPORT IDENTIFICATION
ENTER THE REPORT LEVEL (S FOR SOURCE LEVEL ONLY, P FOR POINT AND SOURCE,
C FOR CRITERIA MATCH AND A FOR ALL LEVELS)
REPT LEVEL? S
ENTER REPORT TITLE (0-61 CHARACTERS)
TITLE? REPORT EXAMPLE
CARD 10 - LOGIC SELECTION CRITERIA
ENTER THE 4 CHARACTER MNEMONIC OF EACH SELECTION OR RETURN
MNEMONIC? STAB
ENTER SELECTION CONDITION - A (OR), U (UNEQUAL), M (EQUAL),
G (GREATER THAN), L (LESS THAN), P (PRESENT), 3 (BLANK OR ZERO)
CONDITION? A
ENTER 1-20 CHARACTER SELECTION VALUE
VALUE? cr
MNEMONIC? STAB
CONDITION? A
VALUE? RI
MNEMONIC? SNME
CONDITION? M
VALUE? (?EXXON@
MNEMONIC?
CARD 20 REPORT FORMAT(S)
ENTER REQUIRED REPORT - QUICKLOOK (QL OR Q2), MILESTONE (MS),
ACTION SUMMARY (AC), QUESTIONNAIRE (QT),
OR SOURCE DATA (3D)
REPORT? SD
REPORT? QL
REPORT? MS
CARD 30 - REPORT SEQUENCE
ENTER THE 4 CHARACTER MNEMONIC OF EACH SORT FIELD, MAJOR TO MINOR, OR RETURN
SORT MNEMONIC? STAB SRCE
MNEMONIC MUST 3E 4 CHARACTERS, PLEASE RE-ENTER
SORT MNEMONIC? STAB
SORT MNEMONIC? SRCE
SORT MNEMONIC?
ENTER SORT PAGE BREAKS (1-6) OR RETURN
PAGE BREAK?
ENTER '2' TO CANCEL STANDARD SUPPRESSION OF SOURCE INFO
OR RETURN
2 OR CAR RET?
ENTER THE 4 CHARACTER MNEUMONIC FOR EACH QUICKLOOK FIELD OR RETURN
QL MNEMONIC? SNME
QL MNEMONIC? STRT
QL MNEMONIC? CYJIM
QL MNEMONIC? STAB
QL MNEMONIC? APCD
QL MNEMONIC?
FIGUHE 9-24. Sample WyLbur EXEC "REPORT "
-159-
-------
ENTER THE 4 CHARACTER MILESTONE ROW MNEMONIC
ROW MNEMONIC? APCD
ENTER THE 4 CHARACTER MILESTONE COLUMN MNEMONIC
COL MNEMONIC? STAB
ENTER EACH COLUMN VALUE (UP TO 4 CHARACTERS) OR RETURN
VALUE? CT
VALUE? RI
VALUE?
DO YOU WISH TO LIST THE RETRIEVAL CARDS, Y OR N?
Y/N? Y
1. 01 01 REPORT EXAMPLE
2. 10 STAB A CT
3. 10 STAB A RI
4. 10 SNME M @EXXON
-------
10.0 SUPPORTIVE TECHNICAL INFORMATION
10.1 Table Processing
All of the programs in CDS perform a number of table-lookups in order to
validate an input data value and/or to generate a description which corres-
ponds to the input code. There are four data elements which have separate
table-lookup procedures for each of the 10 EPA Regions using CDS. Each of
the 10 regions may specify the description for the following codes: County
Code, Personnel Code, Action Type and Results Code.
10.1.1 County Code Table
In the Edit, the State and County Codes on every card are validated by
the Region's County Code Table. An input transaction is rejected with a
fatal error if the State and County Codes on the input do not match one of
the entries on this table.
For each valid Card 1 entered with an Update Code "N", the County Name
associated with the County Code is generated and passed to the Update. The
Update places the County Name on the Masterfile as a retrievable data element.
For a Card 1, the Air Quality Control Region (AQCR) on the input trans-
action is validated against the AQCR on the County Code Table.
Entries on the County Code Table have the following punchcard layout:
Card
Columns
1-2
3-4
5-3
9-25
26-28
29-31
32-34
35-80
Length
2
2
4
*t
17
3
3
3
46
Data
Element
Region Code
State Code
County Code
County Name
First AQCR
Second AQCR
Third AQCR
Filler
Data
Type
Numeric, 01-10
Numeric, 01-56
Numeric
Alphanumeric
Numeric
Numeric
Numeric
Must be blank
-161-
-------
The county codes and the county names have been developed from the SAROAD
Coding Manual. Users may wish to add additional County Codes, especially for
special facilities such as portable asphalt batching plants which are not
always located in the same county. To change the County Code Table, users
should provide the national DBC with the necessary information to add, change
or delete an entry on this table.
Figure 10-1 is the County Code Table for a region. Users should document
any table changes on this figure.
10.1.2 Personnel Code Table
In the Edit, the Personnel Code found on the Card 2 in columns 77-79 and
on the Card 7 in columns 67-79 are validated by the Region's Personnel Code
Table. Input values which do not match one of the table values cannot be
passed to the Masterfile and are blanked out.
In the Update, the Personnel Code Table lookup is performed for every
source and action record on the input Masterfile and on the input transaction
file. A personnel name and a personnel title are generated for th.e output
Masterfile based on each personnel code.
Entries on the Personnel Code Table have the following punchcard layout:
Card Data Data
Columns Length Element Type
1-2 2 Record-Identifier Always "BB"
3-4 2 Region Numeric, 01-10
5-7 3 Personnel Code The first position may
be alphabetic; the second
and third must be numeric.
8 1 Filler . Always "0*
9-23 15 Personnel Name Alphanumeric
24-38 15 Personnel Title Alphanumeric
39-80 42 Filler Must be blank
-162-
-------
REGN
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
SITE
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
V"
CNTY
0240
0260
0280
0360
0400
0520
0540
0560
0580
0600
0660
0680
0720
0740
0760
0780
0800
0820
CNTY NAME
AUTAUGA
BALDWIN
B ARBOUR
BIBB
BLOUNT
BULLOCK
BUTLER
CALHOUN
CHAMBERS
CHEROKEE
CHILTON
CHOCTAW
CLARKE
CLAY
CLEBURNE
COFFEE
COLBERT
CONECUH
AQCR
002
005
006
004
004
002
002
003
003
003-
004
001
001
003
003
006
007
001
Figure 10-1. County Code Table
-163-
-------
By changing the Personnel Name for a given Personnel Code on this table,
all occurrences of the old Personnel Name on the Masterfile will be replaced
with the new Personnel Name.
To change the Personnel Code Table, users should provide the national DBC
with the necessary information to add, change or delete an entry on this
table.
Figure 10-2 is the Personnel Code Table for a Region. Users should docu-
ment any table changes on this figure.
10.1.3 Action Table
In the Edit, the Action Type found on the Card 7 in columns 53-54 is val-
idated by the Action Table. Input values which do not match one of the table
values will cause the input transaction to be rejected with a fatal error.
In the Update, the Action Table lookup is performed for every new Card 7
transaction and for every Card 7 which changes-the Action Type. Both a long
and a short Action Description are generated on the Masterfile based on the
Action Type.
Entries on the Action Table have the following punchcard layout:
Card
Columns
1-2
3-4
5-6
7-8
9-23
24-73
74-80
Length
2
2
2
2
15
50
7
Data
Element
Record- Identifier
Reg ion
Action Type
Short Action Description
Short Action Description
Long Action Description
Filler
Data
Type
Always "CC"
Numeric, 01-10
Numeric
Alphanumeric
Alphanumeric
Alphanumeric
Must be blank
-164-
-------
PERSONNEL
CODE NAME
A01 LEGROS
AO 2 BLOOM
A03 WYNNE
A04 2EHNTER
A05 STONELAKE
A06 BLACKWELL
A07 BUFFINGTON
A08 JOSEPH
A09 GOLD
A10 HANDZEL
All LASROW
A12 GREENE
A13 VACCARO
A14 SMITH P
A15 SERRITELLA
A16 MARTIN
A17 COLLINGS
A18 DONOVAN
A19 BREENAN
A20 ROGERS
A21 FRYE
A22 AJL
A23 BAKER
A24 CALLEN
A25 EARLY
A26 HEENAHN
A27 KALKSTEIN
A23 KOEGEL
A29 MELVIN
A30 SISKIND
C01 WALKER
CO2 LOWRY
CO 3 BUI
CO4 BURROWS
E01 MARSHALL
Figure 10.2. Sample Personnel Table
-165-
-------
To change the Action Table, users should provide the national DBC with
the necessary information to add, change or delete an entry on this table.
Figure 10-3 is the Action Table for a Region. Users are urged to use
WYLBUR to list the most current action types for their region. The following
WYLBUR commands will produce a printout of the current action types:
WYLBOR COMMAND
EXPLANATION
USE SCN.EPAFCS.AO 2 6. FRANK. ISAM. TABLE CLEAR Places all 10 regions action into
working storage.
DEL NOT 'CC061 IN ALL
CHANGE 25 TO ' ' IN ALL NOLIST
CHANGE 7/8 TO ' 'IN ALL NOLIST
CHANGE 1/4 TO ' 'IN ALL NOLIST
LIST OFFLINE REM=*3 UNN BOX=»REG6
Deletes all entries for all
regions except for Region 6.
Each region should put their own
region number into this cciwnand .
Formats table for printing.
Generates spaces between columns
for printing.
Users should route their printout
to their own terminal number.
10.1.4 Results Code Table
In the Edit, the Results Code found on the Card 7 in columns 70-71 is
validated by the Results Code Table. If the input transaction entry is
valid, a Results Description is generated and passed to the Update, where it
is placed on the Masterfile. If the input transaction is not on the Results
Code Table, no Results Code is passed to the Update.
Entries on the Results Code Table have the following punchcard layout:
Card
Columns
1-2
3-4
5-6
7-8
9-23
24-80
Length
2
2
2
2
15
57
Data
Element
Record-Identifier
Region
Results Code
Filler
Results Description
Filler
Data
Type
Always "DD"
Numeric, 01-10
Numeric
Always "00"
Alphanumeric
Must be blanks
-166-
-------
ACTION
Al
A2
A3
A4
A5
A6
A7
AS
A9
Bl
B2
B3
B4
B5
B6
B7
B8
B9
Cl
C2
C3
C4
C5
C6
C7
C3
C9
Dl
D2
D3
04
D5
06
07
SHORT DESCRIPTION
307 CHALLENGES
SIP NOTICE CMSD
SIP CMSD DATE
SIP CMSDRPT SUB
SIP EE RPT SUB
SIP CMS INSP
SIP DOFEA/STATE
SIP S/UNDER 306
NSPS CONST COMM
NSPS NOTICEMSD
NSPS 114 LETTER
NSPS INSP-EPA
NSPS ORDER/EPA
NSPS CIV/CRIM
NSPS MOR NOTICE
NSPS CMSDRPTSUB
NSPS N/MALF'N
NSPS CMSTRESULT
NSPS CMS INSP
NSPS DEA STATE
NSPS S/UNDER306
NESHAPS S/CNS'N
NESHAPS E/CONSR
NESHAPSFINALCOM
NESHAPS SUB CP
NESHAPS PURSQ.P
REGISTRA'N RCVD
PERMIT APPN RCD
NESHAPS INSP 'N
NESHAPS S/T SUB
NESHAPS STATRUP
NESHAPSEPACRDER
NESHAPSCIV/CRIM
NESHAPS PMTG'T
LONG DESCRIPTION
307 CHALLENGES
SIP NOTICE OF CM SYSTEM DEMONSTRATION
SIP CM SYSTEM DEMONSTRATION DATE
SIP CM SYSTEM DEMONSTRATION REPORT SUBMITTAL
SIP EXCESS EMISSIONS REPORT SUBMISSION
SIPCONTINUOUS MONITORING SYSTEM INSPECTION
DEFERRAL OF ENFORCEMENT ACTION OF STATE
SOURCE LISTED UNDER SECTION 306
NSPS CONSTRUCTION COMMENCEMENT
NSPS NOTIFICATION OF CM SYSTEM DEMONSTRATION1
NSPS S114 LETTER
NSPS INSPECTION BY EPA
NSPS ORDER BY EPA
NSPS CIVIL/CRIMINAL ACTION BY EPA
NSPS MODIFICATION OF RECONSTRUCTION NOTIFICATION
NSPS CM SYSTEM DEMONSTRATION REPORT SUBMITTAL
NOTIFICATION OF MALFUNCTION
NSPS CONTINUOUS MONITORING SYSTEM TEST RESULTS
NSPS CONTINUOUS MONITORING SYSTEM INSPECTION
DEFERRAL OF ENFORCEMENT ACTION TO STATE
SOURCE LISTED UNDER SECTION 306
NESHAPS START OF CONSTRUCTION
NESHAPS END OF CONSTRUCTION
NESHAPS FINAL COMPLIANCE
NESHAPS SUBMISSION OF CONTROL PLAN
NESHAPS PURCHASE OF EQUIPMENT
NESHAPS REGISTRATION RECEIVED
NESHAPS PERMIT APPLICATION RECEIVED
NESHAPS INSPECTION
NESHAPS SOURCE TEST SUBMISSION
NESHAPS START-UP
NESHAPS ORDER BY EPA
NESHAPS CIVIL/CRIMINAL ACTION BY EPA
NESHAPS PERMIT GRANTED
Figure 10-3. Sample Action Table
-167-
-------
To change the Results Code Table, users should provide the national DEC
with the necessary information to add, change or delete an entry on this
table.
Figure 10-4 is the Results Code Table for a Region. Users should docu-
ment any table changes on this figure.
10.1.5 Other Table Lookup Procedures
For both editing and reporting formatting purposes, there are a large
number of table lookups for values which are used consistently by all
regions. For example, there are nine possible values for Compliance Status
Code. Each value has a corresponding definition which appears on the Source
Data Report. These definitions must be used by all users and can be changed
only by the national DEC.
The following data elements have table lookups for converting a code to
an English-language description:
Emission Category Source Compliance
Compliance Status Source Emission Category
Air Program SIC Code
SIP Code Air Program Status
In addition to having a table lookup procedure for the SIC Code during
retrievals, the CDS Update Program uses the SIC lookup to place the SIC -ins-
cription on the Process Description of the Emission Point 000 for any new
source which has no user coded value in the Process Description field and
which has a valid SIC Code. Thus, the SIC Description replaces the fornie:
message "ENTIRE SOURCE" in the Process Description on Point 000.
Any additional values to these codes or changes in the definitions of
these codes must be approved by the national DEC. Each change involves a
number of computer program modifications.
-163-
-------
RESULTS
CODE
MA
MC
MO
MI
MO
MR
MU
MV
Rl
R2
R3
R4
R5
R6
R7
R8
R9
RA
RB
RC
RO
RE
RF
RG
01
02
03
04
05
DESCRIPTION
QEER ADEQUATE
IN COMPLIANCE
CM RECERTIF REQ
QEER INADEQUATE
NUMEROUS SHUTDN
RETEST REQ
UNKNOWN CMST
IN VIOLATION
SUBJECT
NOT SUBJECT
APPLIC INCOMPL
APPLIC COMPLETE
REVIEW COMPLETE
REVIEW PENDING
PRELIM APPROVE
PRELIM DISAPPRV
COMMENTS REC'D
NO COMMENTS
RESPONDS REC'D
NO RESPONSE
HEARING GRANTED
HEARING DEFINED
FINAL APPROVE
FINAL DISAPPRV
ACTION ACHIEVED
NOT ACHIEVED
ACTION PENDING
RESPONSE COMPLETE
RESPONSE INCOMPLETE
Figure 10-4. Sample Results Code Table
-169-
-------
10.1.6 CDS Masterfile Layout
Figure 10-5 shows the format of the CDS Masterfile. This file resides on
a tape and is used in each of the Update Cycles. This format is also used
for each of the disk masterfiles from which retrievals are performed.
10.2 Backup and Recovery Procedures
Both the user and the national DBC have responsibilities to make sure
that CDS can survive hardware malfunctions as well as occasional human error
in the course of system usage.
10.2.1 User Responsibility for Backup
As part of the normal CDS operation, users should perform the following
tasks to assure proper backup:
All input punchcards must be kept for. a minimum of 1 month from
the date on which they were used as input to CDS. Card batches
should be labelled by date so that they can be identified and used
as backup.
WYLBUR data seta which are used as input transactions must be kept
for a minimum of 1 month from the date on which they were used as
input to CDS. Users should keep a log of all WYLBUR data sets,
marking the creation date, the expiration date, the approximate
volume of the data set and its use or function.
Edit Reports should not be discarded. The Edit Report provides a
record of what transactions were input to the system. Corrections
should be checked off as they are performed.
All Update Reports must be kept on file. Since the Update Reports
provide the only audit trail of data placed on the CDS Masterfile,
they are very valuable for researching problems. They should be
filed in the order to the Masterfile1s Output Serial Number which
appears on the heading of each page. If users note any discrepan-
cies or inexplicable errors on this report, they should alert the
national DBC or TRC. TRC maintains a complete inventory of all
Update Reports for all users.
-170-
-------
COMMOfl l*f«
>« ill »c«ies
i§
COMPLIANCE DATA SYSTEM
MASTER FILE LAYOUT
;::;:;;::
i:
I M t*J * * * j 1 1 * * * ' * * * 1 1 *« 1
SOURCE
NAME
if
sec it
CODE
: : : :V
1
STREET
ADORE SS
cc
01
rfilai
sn
rotivuNt I
Mil
1U1MIBN
N M1UI
HCflON
PROCE S S
DE SCR 1 V T 1 ON \\
IX
«t
MICIirillH 2
OHOII) a
§3
STAFF
NAME
1 1 1 1 1 i 1 1 1 1 1 * 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 < 1 1 i i 1 1 1 1 1 1 1 1 1 1 * ri 1 1 1 1 1 1 1 1 1 1 1 ' i * 1 1 1 1 1 1 1 1
tl*«»t|»tttl**IM|llltll||ll'tllll|*'***>t*«4ll»**t*ll||Mllll*t4l*t|||l''*"MM
l*t *H 1 1 » ill t 11*11^1 » M_|J I II ItlM^IOI Ml* I I Mjlfll* IIM l_tX**« I 5J! tl_
rmuuni 4
i FILLER i
I - :. I I
STAFF
TiTIE!
COMMENT
M.i
ER
J_
: AC TION DE SCR I P TION
' '( (LONG) !
HlUlfl
bttdiriiM
FILLER
I t I I I I I I I t I t I I I I I III III I t I I I I I I I I I I I I I I I I It I M I I t I * I I I I I I M I I I I
Ml4ltMt''M*'|'!!!!M!i)"il!i!!t!!!!*Ml4»t*«IOMI^^
Mcjur 10-5. Masterfile Layout
-------
10.2.2 National Responsibility for Backup
As part of the normal CDS operation, the national OBC performs the follow-
ing tasks to assure backup of the system:
During the update cycle, the MOD File containing all transactions
submitted since the previous update cycle is copied to a magnetic
tape. Five cycles of tape are maintained so that backup exists
for 1 month's worth of input transactions.
Eight cycles of the CDS Masterfile are kept at the central
computer facility.
On a quarterly basis, the CDS Masterfile is copied and sent to TRC
for archiving.
Since the 10 regional disk Masterfiles are created each week from
the CDS Masterfile, the Masterfile provides the only backup of
regional files.
The County Code, Personnel, Action and Results Code Tables can be
recreated from punchcards or from WYLBUR data sets.
All other CDS data sets and computer programs are maintained at
TRC with NCC backup available at all times.
10.2.3 Recovery Procedures
If any backup procedures are needed to recover from hardware difficulties
at the central computer site, the national DBC will inform each user about the
specific backup procedure to be used. In most recovery procedures involving
user participation, users will be asked to resubmit input transactions which
were destroyed during the hardware difficulties.
10.3 Computer Program Modifications
If any of the computer programs in the CDS produce erroneous results, it
is the user's responsibility to notify the national DBC of the problem. In
addition to describing the problem in detail, users may be asked to rerun the
program in error so that the printout can be routed to TRC for a detailed
analysis.
-172-
-------
Computer program errors can usually be corrected within a short time.
Minor problems and modifications can be made in less than 1 week. Major
changes may take several weeks or months, depending on the complexity of the
change.
10.4 Microfile Considerations
Facilities for producing both microfilm and microfiche output are current-
ly available through the Micrographics Department at NCC in Research Triangle
Park, North Carolina. CDS users should consider using microfiche to facili-
tate storage and handling of lengthly reports such as a regional Source Data
Report.
Any user who wishes to utilize this service must submit a WSC Request for
Micrographics Form. Figure 10-6 (a through e) includes all the forms needed
to establish job processing parameters to indicate a reduction factor compat-
ible with the user's microfiche reader, as well as an appropriate eye-readable
title for identification purposes.
Once a user's completed form has been received by NCC, the requested
microfiche output may be submitted for processing at any time. The user can
request a regular CDS retrieval with a Source Data Report format. However,
since the data requires further processing, the output will be placed on a
tape data set for subsequent micrographics processing. Microfiche processing
requires a 48-hour turnaround time. The output is then mailed directly to the
requester.
Additional job control cards in the retrieval request deck are necessary
to direct the retrieval output to a tape rather than to a printer. Sample
retrieval JCL showing these additional cards is shown in Figure 10-7.
-173-
-------
WSC REQUEST FOR MICROGRAPHICS
I I RETURN COMPLETED REQUEST TO: I
I MICROGRAPHICS CENTER USE ONLY Washington Support Center |
I DATE RECEIVED I 401 M. St., SW, Suite 201 I
I CONTROL NO.: I Attention: Skip Pettiford |
I I Washington, DC 20460 |
I I
USER INFORMATION
DATE:
NAME OF APPLICATION: MICRQCDS (Not longer Chan 3 characters)
INDIVIDUAL USER: NAME TRC-Environmental Consultants, Inc.
ADDRESS 800 Connecticut Boulevard
East Hartford, CT 06108
Attn: ** ZIP CODE ufa-LL>s
PHONE NO. (203) 289-8631 ROOM NO.
USER I.D. EPAEXC ACCOUNT NO.
** CDS Field Support Coordinator
TYPE OF APPLICATION
.NEW APPLICATION (TEST STATUS) CURRENT STATUS: TEST
CHANGE APPLICATION PRODUCTION
SERVICE REQUESTED
.ORIGINAL MICROFICHE x DUPLICATION OF MICROFICHE
.ORIGINAL ROLL FILM DUPLICATION OF ROLL FILM
SOURCE DOCUMENT MICROFILMING
SPECIAL INSTRUCTIONS
Figure 10-6a. WCS Request for Micrographics
(Micrographics User Information for CDS)
MICROGRAPHICS -174-
-------
WSC MICROFORMS INPUT-OUTPUT SPECIFICATIONS
'UT (Required for microfiche or roll film request)
MAGNETIC TAPE CHARACTERISTICS:
IBM IBM OR OTHER (SPECIFY)
SL LABELED OR UNLABELED (L or U)
9 TRACK (7 or 9)
16QQ BPI (556,300,1600 ONLY)
PARITY (ODD OR EVEN-REQUIRED FOR 7-TRACK TAPES ONLY)
133 RECORD LENGTH (MAX 256)
4123 BLOCK SIZE (MAX 9000 CHARACTERS)
EBCDICCHARACTER SET (EBCDIC, ASCII, OR OTHER)
132 NUMBER OF PRINT POSITIONS
I CARRI AGE CONTROL POSITION (if exist, usually pas. 1 )
' 2 POSITION NUMBER OF FIRST PRINT CHARACTER (if
carriage control exist, usually pos. 2)
ASA CARRIAGE CONTROL TYPE (ASA, MACHINE, OTHER)
64 LINES PER FRAME/PAGE (INCLUD. PAGE HEADERSMMAX 36)
VERTICAL TABBING: Used
only for special formatting of page frames.
("Channel" number is found in carriage control
postion; when channel number is detected,
related lines will print on line number
s pec i f i ed . )
CHANNEL
I 1
I
LINE NUMBER I
4|5l6|7|8|9l"A-|B!C
= T = M S 0 V F R L '- '
.OPEN BOX (DEFAULT)
.LINED BOX
.SPECIAL (MICROGRAPHICS
ATTACHED)
FORMS OVERLAY SPECIFICATIONS
OUTPUT
MICROFORMS REQUIREMENTS:
2 NUMBER OF COPIES REQUESTED
FICHEMICROFICHE OR ROLL FILM
COMIC I MAGE (COMIC OR CINE) (NORMALLY COMIC FOR FICHE)
ROW FRAMES/ROW (HORIZONTAL)
9 FRAMES/COLUMN (VERTICAL)
REDUCTION FACTOR (24X,42X,43X )
24
Figure 10-6b. WCS Request'for Micrographics
(CDS Microform Input)
MICROGRAPHICS
-175-
-------
WSC MICROFORMS INPUT-OUTPUT SPECIFICATIONS
OUTPUT(cont i nued from page 2)
MICROFICHE TITLE FORMAT:
SPECIFY HOW TITLE SHOULD APPEAR CIRCLE AND NUMBER EACH EXTRACT
I I
I REGION II - SOURCE DATA REPORT (Unique to individual user) |
I
m \
TITLE EXTRACT FIELDS DATA
FIELD 1
LINE NUMBER
BEGINNING PRINT
POSITION
FIELD LENGTH
EXAMPLE FROM YOUR
DATA
HOLD/NORMAL
3
3
8
11/77
5
10
2
MY
6
10
4
0140
6
23
5
00037
1
I
1
1
1
1
1
1
|
1
1
1
PAGE HEADER FORMAT:
ELEMENT
BEGIN
PRNT FOS
HEADER ELEMENT DESCRIPTION
LIME 1
Skip lines
after linel
(BLANK LINES)
LINE 2
Skip lines
after 1 i ne2
(BLANK LINES)
LINE 3
Skip 1 i ri es
after 1 i ne 3
(BLANK LINES)
LINE 4
Skip lines
after Iine4
(BLANK LINES)
1
2-
3
4
1
2
3
4
1
2
3
4
1
2
3
4
MICROGRAPHICS
Figure 10-6c. WCS Request for Micrographics
(CDS Microform Output)
-176-
-------
WSC MICROFORMS INPUT-OUTPUT SPECIFICATIONS
OUTPUT(continued from page 3)
INDEXING REQUIREMENTS:
BEG PRINT POSITION FOR fcE
KEY LENGTH IN CHARACTERS
LINE TO BEGIN KEY SEARCH
LINE TO END KEY SEARCH
KEY MASK CHARACTER
PRINT LINE POSITION FOR
MASK
MASK LENGTH IN CHARACTERS
SUBKEY 1 SUBKEY 2
SUBKEY 3
LITERAL STRING
CHAR MAX)
I
10
10
35
SUBKEY
MASK CHARACTERS: Numeric = 9; "Alphabetic = A; Alphanumeric =X,
Special Character = 5; Literal = L.
SOURCE DOCUMENT MICROFILMING:
TITLE OF DOCUMENT
NUMBER OF PAGES
PAGE DIMENSIONS
NUMBER OF MICROFILM COPIES DESIRED
SPECIFY FILM CARTRIDGE TITLE, IF ANY
FORMAT REDUCTION RATIO
COMIC 24X
CINE 25X
27X
CARTRIDGE TYPE
3M
KODAK
REEL
Figure 10-6d. WCS Request 'for Micrographics
(CDS Microform Output - Continued)
MICROGRAPHICS
-177-
-------
WSC MICROFORMS INPUT-OUTPUT SPECIFICATIONS
iREAK REQUIREMENTS:
BREAK ON MATCH OR
CHANGE?
START NEW FICHE WITH
CURRENT OR NEXT
FRAME
LINE TO BEGIN SEARCH
LINE TO STOP SEARCH
BEGINNING PRINT POS.
OF BREAK FIELD
LENGTH IN CHARACTERS
OF BREAK FIELD
BREAK EVERY OCCURRENCE
OF MATCH?
MATCH FIELD 1
MATCH FIELD 2
MATCH FIELD 3
MATCH FIELD A
MATCH FIELD 5
MATCH FIELD 6
COND 1
COND 2 COND 3 COND
M
CURRENT
5
5
10
2
NO
NJ
NY
PR
VI
i
SPECIFY
OWN
STATE
CODE
1
Figure 10-6e. WCS Request for Micrographics
(CDS Microform Page Breaks)
MICROGRAPHICS
-178-
-------
''! liHITIIAN Ciimm: Id II I.I
AH nil Hi
STM i
NI i
i :
/ /
/*
II
I/
O 1
3 O
30
I/
/'/
II
'//
/*
i
E
C
R
S
E
P
N
r
0
s
s
r
0
A
T
V
J
D
'J
E
_f
e
O
1
i
I
/
P
1
IKC
IOIITIIAH
1
i
I
A
E
3
1
1
i
r
»
c
s
P
-
II
c
0
R
-
n
S
o
1
-
i;
j
i
1
5
II
' i
1
0
-
A'
E
*
X
t
T
A
C
I Ml N
14
n
E
E
i)
G
P
O
0
D
li
X
C
D
1
A
U
E
;
li
/
C
Ci
s
T
L
(
II
u
C
'I-
N
S
:
R
II
n
{)
Ai
D
(
E
II
o
S
1
O
D
1
C
10
a
H
1
n
F
r
ji
C
r
0
D
S
Ai
Uh^llAM flAMt. '
))
D
V
M
S
L
I
11
S
1
1
N
i
F
14
Y
-
C
:
R
U
n
P
R
C
E
A
;.
i
0
I
11
VI
F
t 1
P
L
11
i
-
i
D
R
n
i
c
E
I
E
,
i
i<
i1
1
C
:i'.l Hill ICIlt HI JTA'JK IIUMIIt
i
)
i
A
5
L
11
/
i
)
-
))
t
-
i
J
14
C
-
i
u
3
D
-
t
N
3
li
S
a
1
i
il
a
T
B
II
N
-
a
;
L
-
»
1
-
a
I
K
-
u
C
A
S
li
K
M
P
1
II
Cl
1
E
Z
O
f
C
9
I
(i
1
-
R
i
It
C
^
4
K
il
£
1
-------
10.5 Minicomputer Edits
Dennis Shur of EPA at NCC has developed an online data entry and edit
program for the regional PDP-11/70 minicomputer. This program should be of
great interest to regional CDS users who have access to a PDP-11.
The program performs many of the same functions of the CDS Edit; however/
it provides error checking instantaneously as the data is keyed in via the
CRT terminal used for data entry. In addition to performing basic validation
routines, the program also displays the Facility Name of the source for which
various data items are being entered. Thus, certain Update Errors can also
be identified during the edit programming.
CDS users wishing more information about this online edit should call
Dennis Shur at NCC in Research Triangle Park, North Carolina.
10.6 Archiving
With constant additions and changes to the CDS Masterfile, the amount of
data carried in the system eventually becomes very cumbersome. When users
determine that there are too many obsolete sources on the Masterfile, they
should consider archiving rather than deleting the unwanted sources. This is
especially useful for minor sources or sources with no applicable regulations.
After a user has carefully defined the criteria to be used for archiving,
he should write a letter to TRC requesting the archiving. TRC will remove
the sources from the active CDS Masterfile and will place the sources on a
tape file which can be used for retrievals or it can be merged with the
Masterfile at a later date.
Archiving is beneficial because it reduces the cost of retrievals and it
simplifies retrieval criteria needed to produce management reports.
-180-
-------
Archiving must be done on a source by source basis; the archiving of only
partial information, such as inspection actions for a source, cannot be done
effectively since it is impossible to replace obsolete actions on the Master-
file in the same sequence as they existed prior to archiving. If the user
feels that there are too many obsolete actions on the Master file, he should
delete those actions. Since each CDS Masterfile is copied to a permanent
storage facility on a quarterly basis, users can safely delete obsolete
actions without losing all record of the historic action since actions
deleted from the current Masterfile can be retrieved off the historic
Masterfile.
-181-
-------
11.0 STATE ENFORCEMENT SYSTEMS
Part of SSCD's efforts have been in the area of providing States with
computerized management information systems which will enable the States to
track all enforcement activities and also meet regional reporting
requirements for sources subject to SIP regulations as well as other portions
of the Clean Air Act which have been delegated to the States.
The following sections describe, in general terms, what options States
have available to them for enforcement systems.
11.1 State Enforcement System Options
As part of the grant conditions from the regional enforcement division,
each State must provide a great deal of information to the region foe the
following areas:
Which facilities are affected by SIP regulations. Which facili-
ties have permits to construct and permits to operate.
Which facilities impact non-attainment standards, New Source
Review, Prevention of Significant Deterioration, NESHAPS, NSPS,
etc.
Which compliance category each source is in as a result of the
State's most recent inspection.
What legal steps have been made to bring a non-complaint source
into compliance. What enforcement schedule must each non-
complaint source follow.
Once the State has gathered this information through its team of in-
spectors, this information can be organized by one of the following methods:
1. Maintain a manual system. This is very cost effective for States
with relatively small numbers of facilities and with small numbers
of violators.
2. Develop an in-house computer system. Only the largest States with
unique processing requirements can afford to spend anywhere from
$75,000 to $200,000 to develop a smoothly working data system.
-182-
-------
3. Use an EPA-developed State computer system such as a State version
COS. This option is ideal for States which want to track all of
the major and minor facilities within their jurisdiction.
4. Use the national CDS to enter data directly on the region's data
base and to produce management reports from the region's data
base. This option is particularly cost effective if the State has
a computer terminal connected to EPA's NCC, and if the State needs
to track mainly major facilities.
The option a State chooses depends on a wide variety of factors such as:
The level of detail required by internal management needs as well
as external reporting requirements.
» The manpower and the skills needed to implement the option. No
State should consider a computerized management system unless they
have strong support from the State's data processing group.
The availability of various types of computer hardware. Often
States which already process STORET data and other EPA systems are
familiar with the hardware constraints which must be resolved
before a new computer system can work effectively.
9 The rate at which information needs change from year to year.
With every new EPA fiscal year, a new set of reporting require-
ments are negotiated between the region and the State. Often a
State data center cannot keep up with a new set of computer pro-
grams to meet these requirements.
The Stationary Source Compliance Division and the regional enforcement
personnel are committed to helping States meet the challenge of attaining
compliance for all stationary sources of air pollution. SSCD will support
feasibility studies and State enforcement system installations in order to
further the efforts of the States to monitor the compliance status and
enforcement activity of any State enforcement agency.
11.2 State Enforcement System uauge
Tables 11-1 through 11-10 describe the types of enforcement systems used
in each of the 50 States. This listing is on a region by region basis. The
tallies of major sources are estimates as of February 1982 and need to be
upgraded on a continuing basis.
-183-
-------
TABLE 11-:
Ri'XHON I'S ENFORCEMENT SYSTEMS
REGION I - BOSTON
State
Connecticut
Maine
Massachusetts
New Hampshire
Rhode Island
Vermont
TOTALS
Major SIP
Sources
241
143
492
102
ao
51
I07y
Majors Out of
Compliance or Enforcement Year System Installation
Unknown System Type* installed Cost to EPA
27 State
3
7 EMS 1974 $45,000
5
2
0
44
Other Systems
Emission Air
Inventory Quality
State System AQDHS installed
AQDHS Installed
EIS AQDHS Installed
AQDHS installed
AQDHS Installed
*EMS = EPA's Enforcement Management System
State = System Designed and implemented by State
CDS State = Modified version of EPA's CBS System Running at State installation
National CDS = Direct user of National CDS at EPA's National Computer Center
-------
TABLE 11-2
KB.; I .IN fl'S ENFORCEMENT SYSTEMS
KEG[ON II - NEW YORK
Major SIP
State Sources
New Jersey 1111
New York 1451
Puerto Rico 166
Virgin Islands 14
TOTALS 2742
Majors Out of Other Systems
Compliance or EnC-u'cement Year System Installation Emission Air
Unknown System Type* Installed Cost to EPA .Inventory Quality
117 State
198 CDS installed 1977 $67,000 State AQHDS Installed
in New York City in New York
City
12 EIS Installed AQHDS Installed
3
330
*EMS = EPA's Enforcement Management System
State = System Designed and Implemented by State
CDS State = Modified version of EPA's CDS System Running at State Installation
National CDS = Direct User of National CDS at EPA's National Computer Center
-------
TABLE 11-3
REGION HI'S ENFORCEMENT SYSTEMS
REGION III - PHILADELPHIA
State
Delaware
District of
Columbia
Maryland
Pennsylvania
Vi rg inia
West Virginia
TOTALS
Major SI I'
Sources
48
20
258
1480
644
229
2599
Majors Out o£
Compliance or Enforcement
Unknown System Type*
0
3
19 State CDS
107 State
11 State CDS
17
159
Other Systems
Year System Installation Emission Air
Installed Cost to EPA Inventory Quality
EIS Installed
1977 $47,000
State
1981 $37,945 BUS Installed AQDHS Installed
*EMS = EPA's Enforcement Management System
State = System Designed and Implemented by State
CDS State = Modified version of EPA's CDS System Running at State Installation
National CDS = Direct User of National CDS at EPA's National Computer Center
-------
TABLE 11-4
REGION IV'S ENFORCEMENT SYSTEMS
REGION IV - ATLANTA
Majors Out of Other Systems
State
Alabama
Florida
Georgia
Kentucky
Mississippi
, North Carolina
1-*
7' South Carolina
. Tennessee
TOTALS
Major SIP
Sources
431
491
372
1062
148
859
374
785
4522
Compliance or Enforcement Year System Installation Emission Air
Unknown System Type* Installed Cost to EPA inventory Quality
13
18
13
237
2
9
1
92
385
EMS 1973 AQDHS Installed
AQDHS installed
State CDS EIS Installed AQDHS installed
State EIS Installed
EMS $26,000 EIS Installed
State EIS installed
National CDS $ 2,000 EIS Installed AQDHS Installed
EMS and National EMS/1974 $30,000 EIS Installed AQDHS Installed
CDS CDS/1978 $ 1,000
*EMS = EPA's Enforcement Management System
State = System Designed and implemented by State
CDS State = Modified version of EPA's CDS System Running at State installation
National CDS = Direct User of National CDS at El'A's National Computer Center
-------
TABLE 11-5
REGION V'S ENFORCEMENT SYSTEMS
REGION V - CHICAGO
State
Illinois
Indiana
Michigan
Minnesota
Ohio
i- Wisconsin
CO
03
1
TOTALS
*EMS
State
CDS State
National CDS
Major SIP
Sources
1599
774
622
588
1149
483
5215
Majors Out of
Compliance or Enforcement Year System Installation
Unknown System Type* Installed Cost to EPA
101
45 State
148 State
161 State CDS 1979 $35,000
173 National CDS 1979 $ 2,000
29
657
Other Systems
Emission Air
Inventory Quality
AQDHS installed
State AQDHS Installed
EIS installed
AQDHS installed
= EPA's Enforcement Management System
= System Designed and Implemented by State
= Modified version of EPA's CDS System Running at State Installation
= Direct user of National CDS at EPA's national Computer Center
-------
TABLE 11-6
VI'S ENFOKCKMKNT SYSTEMS
REGION VI - DALLAS
State
Arkansas
Louisiana
New Mexico
Oklahoma
Te xa s
TOTALS
Major SIP
Sources
16J
553
236
275
1532
275U
Majors out of
Compliance or Enforcement Year System installation
Unknown System Type* installed Cost to EPA
14 State CDS 1979 $35,000
42 State CDS 1977 $32,000
13
6
11 EMS 1974 $45,000
State 1977
86
Other Systems
Emission Air
Inventory Quality
AQDHS Installed
AQDHS Installed
*EMS = EPA's Enforcement Management System
State = System Designed and implemented by State
CDS State = Modified version of EPA's CDS System Running at State installation
National CDS = Direct user of National CDS at EPA's National Computer Center
-------
TABLE 11-7
REGION VI I'S ENFORCEMENT SYSTEMS
REGION VII - KANSAS CITY
Major SIP
State Sources
Iowa 542
Kansas 780
Missouri 306
Nebraska 760
^ TOTALS 2388
o
Majors Out of
Compliance or Enforcement
Unknown System Type*
19 EMS
13
20 State CDS
15 State CDS
67
Year System Installation
installed Cost to EPA
1974 $28,000
1980 $35,000
1981 $38,000
Other Systems
Emission Air
Inventory Quality
AQDHS Installed
BIS installed AQDHS installed
*EMS = EPA's Enforcement Management System
State = System Designed and Implemented by State
CDS State = Modified version of EPA's CDS System Running at State installation
National CDS = Direct user of National CDS at EPA's National Computer Center
-------
TABU: li-u
viri's ENFORCEMENT SYSTEMS
KKuION VIII - DENVER*
State
Colorado
Montana
North Dakota
South Dakota
Utah
i
ti Wyoming
i.
TOTALS
Major SIP
Sources
284
13 'I
86
100
117
15 :i
874
Majors Out of
Compliance or Enforcement
Unknown System Type*
6 EMS
34
2
14
10
5
71
Other Systems
Year System Installation Emission Air
Installed Cost to EPA Inventory Quality
1974 $26,000 EIS Installed AQDHS Installed
EIS Installed
EIS Installed AQDHS Installed
AQDHS Being
Installed
AQDHS Installed
'
*EMS = EPA's Enforcement Management System
State = System Designed and implemented by State
CDS State = Modified version of EPA's CDS System Running at State installation
National CDS = Direct user of National CDS at EPA's National Computer Center
-------
TABLE 11-y
REGION IX'S ENFORCEMENT SYSTEMS
REGION IX - SAN FHANC1SCO
State
Arizona
California
Hawaii
Nevada
Guam
TOTALS
Major SIP
Sources
322
1756
113
118
14
2323
Majors Out of
Compliance or Enforcement
Unknown System Type*
13
78 National CDS
7
6 National CDS
4
108
Other Systems
Year System installation Emission Air
Installed Cost to EPA Inventory Quality
EIS installed
1977 EIS Installed AQDHS Installed
1978 $2,000 AQDHS Installed
EMS = EPA's Enforcement Management System
State = System Designed and Implemented by State
CDS State = Modified version of EPA's CDS System Running at State Installation
National CDS = Direct User of National CDS at EPA's National Computer Center
-------
TABLE 11-10
REGION X'S ENFORCEMENT SYSTEMS'
REGION X - SEATTLE
State
Alaska
Idaho
Oregon
Washington
Major SIP
Sources
68
196
301
278
Majors Out of
Compliance or Enforcement
Unknown System Type*
19
11
6 State CDS
23
Other
Year System installation Emission
Installed Cost to EPA Inventory
EIS installed
1978 $32,000
Systems
Air
Quality
AQDIIS Installed
TOTALS
843
59
*EMS = EPA's Enforcement Management System
State = System Designed and Implemented by State
CDS State = Modified version of EPA's CDS System Running at State Installation
National CDS = Direct User of National CDS at EPA's National Computer Center
-------
11.3 Summary of State Enforcement System Options
States have the following four options for tracking all the information
to manage a successful enforcement program:
1. Manual system
2. In-house State system
3. EPA developed State CDS
4. National CDS
The first option is ideal for States which have a very small number of
sources to be tracked and none of these sources are on a complex enforcement
schedule. A separate automated system is difficult to justify for States
with fewer than 200 major sources of air pollution.
The second option is best suited for large States such as California oc
Texas, which have very special in-house processing requirements and which
have strong EDP groups available for the development and maintenance oi: a
complex computer system. This option is also recommended for States which
need to develop a comprehensive multi-media data base which traci-is emission
inventory data, compliance data and enforcement data for sources of air,
water, solid waste and other hazardous pollutar.rn. Tr.^ c-'-::: : - i .:: a
system will vary from $75,000 to 3250,000 and will take anyvhera from 1 to 2
years to develop.
The third option is recommended for States which have over 2 ;0 .-sajoc
sources of air pollution. These States can take advantage of .-.he -is si stance
provided by EPA in developing and installing effective State jnforce^ent
systems. Although EPA has a tradition of refusing to purcna^e ccraputsr hard-
ware for States, they are willing to assist States in the installation and
training of EPA-developed systems.
During the early and mid 1970's, nine States requested and received EPA
assistance in the installation of the Enforcement Management System (EMS):
-194-
-------
Each of the Air Pollution Control divisions of these States had access to a
large IBM, Univac, Control Data or Honeywell computer. Each State had suffi-
cient EDP and enforcement staff for supporting the system. EPA spent an
average of $32,000 for installing EMS in the following States:
Alabama
Georgia
Colorado
Iowa
Massachusetts
Mississippi
North Carolina
Tennessee
Texas
Six of the nine States are currently using EMS. Texas replaced EMS with
its own system; Georgia and Tennessee have switched to the newer CDS system.
Since 1976 EPA has been recommending a State CDS system or direct entry
CDS for States needing an enforcement system. The State CDS system is a much
more effective system than EMS for .meeting current and anticipated
information requirements of State enforcement agencies. Each State
installation is a custom-designed version of the national system used by the
Division of Stationary Source Enforcement and by each of the 10 regional
enforcement divisions.
States which need to track a large number of minor sources, as well as
all of their major sources, should consider a State CDS installation.
.Generally, it is necessary to have a State system for tracking over 200 major
sources and over 400 ninor sources of air pollution. Prerequisites for a
State installation are the following:
Availability of a suitable medium-sized or large-sized computer
with a COBOL compiler. State CDS systems have been installed on
IBM System 3, IBM 370, Honeywell, Univac and Control Data equip-
ment.
Availability of programming and operational support from State's
EDP staff.
-195-
-------
A manpower commitment of the part of the enforcement division to
keep the data in the system current and accurate.
EPA will analyze and possibly underwrite the installation cost of a State
CDS system; this has been averaging $35,000 for a 6-month contract with an
environmental consulting firm such as TRC. The States underwrite the operat-
ing costs of running the system. These costs vary from State to State
depending on the number of facilities tracked and the number of management
reports requested. For a Stata with 500 major and 500 minor sources, typical
costs might include an annual budget of 32,000 for computer runs, 3500 for
data storage and $750 for keypunching.
Currently, the following enforcement agencies are using or are getting
the State CDS system (as of January, 1982):
Arkansas
Georgia
Louisiana
Maryland
New York City
Oregon
Missouri
Nebraska
Minnesota
Virginia
Each of these States has examined the features and costs associated with
a State CDS installation and has determined that this option is the most
cost-effective method of meeting their enforcement information needs.
The fourth option of becoming a direct user of the national CDS system is
the best data processing solution for States which meet the f oilo-Ji :-.'.]
criteria:
Have access to the National Computer Center via a computer ter-
minal.
Have no need to track large numbers of minor sources.
Have no need for special processing requirements not already
available in CDS.
-196-
-------
Since the EPA underwrites the cost of operating and maintaining COS,
States which use the national system have very low costs associated with
using the system. Generally, an annual budget of $2,000 for computer runs
and $750 for keypunching is very adequate. These States automatically
benefit from all programming improvements and new features installed for
regional users. EPA benefits from allowing States to use the national system
by having accurate up-to-date data in CDS for that State and by having very
low costs associated with State participation in CDS. Normally a $5,000
training budget is adequate for bringing a State on-line.
The following four States have made a commitment to be direct CDS users:
* Ohio
« California
South Carolina
Tennessee
Each of these States has found that they can meet EPA reporting require-
ments and all internal management reporting requirements at a very low cost
by being direct users of the national CDS system.
-197-
-------
12.0 DOCUMENTATION UPDATES
Hajoc changes to the COS system are issued periodically. Since EPA's
data center publication, SIGNON, was cancelled it has been replaced by a
memo-type newsletter entitled CDSNEWS. This newsletter will contain articles
on COS enhancements and also any other information issued by EPA concerning
CDS.
To receive the CDSNEWS newsletter, please call Franklin C. Smith at EPA
headquarters i" "ashingten, DC, area cede (202) 332-2333, GE contact
Wisher or Bob Bowers at TRC in East Hartford, Connecticut (203) 289-8631.
-198-
-------
13.0 HEADQUARTERS GUIDANCE AND QUALITY CONTROL MEASURES
Accurate data entry is critical to the continued success of CDS. This
section recommends techniques users can follow to meet the minimum require-
ments of accurate data for all sources and outlines the special data require-
ments for sources which are out of compliance with applicable emission
regulations and for sources which fall under special industry groupings or
special air regulations.
13.1 Sources to be Tracked
The first step in implementing a set of quality control procedures at the
State or regional level is to make sure that each facility which should be
tracked in CDS is actually registered with a valid Region, State, County and
Source Number. At a minimum, the following types of facilities should be in
the system:
Class A SIP Sources. Sources which emit or have the potential to
emit 100 tons per year or more of any regulated criteria pollutant
(particulates, S02, hydrocarbons, NOx, CO, and lead}.
« NSPS Sources
NESHAP Sources
PSD Sources
Regional CDS managers should review their current CDS inventory of each
of the above source categories to make sure that all sources which should be
in the system are actually entered correctly in the system. On a quarterly
basis the manager should review the inventory witn State Enforcement
Officials, Regional Enforcement Engineers and with Regional Air Branch
Staff. Additions and changes should be made as appropriate. In addition to
the regular reviews, the manager should make an annual review of current
-199-
-------
sources in order to archive sources which are not needed on the current CDS
Masterfile.
13.2 Data to be Tracked for All Sources
The following list represents the recommended minimum data requirements
for all sources with potential uncontrolled emissions greater than 100 TPY
which have been entered into CDS. Each data element should be reviewed per-
iodically to insure comoleteness and accuracv.
Data Element
1. Source Name
2. City
3. Zip Code
4. Air Program Code
5. SIC Code
Remarks
Misspellings should be corrected.
Abbreviations must be self-explanatory
and consistent. Name changes must be
accompanied by a comment record indicat-
ing the former name. Multi-plant cor-
porations should have the same corporate
name followed by a plant name, i. = .,
USS-Clairton. The naming convention
documented in the User's Guide Data
Dictionary should be followed.
If no city name is available, the name
of the post box area should be used.
City names must be spelled and abbrevi-
ated consistently. If a plant is
'located in a specially named section c:
a city, the city name should be used
whenever possible.
A zip code of the actual plant location
should be available from a zip code
directory.
This code is used only for those por-
tions of a facility which are subject to
that air program's requirements. Acci-
dental changes or misinterpretations of
Air . Program Code can allow a source r.c
disappear from important management
reports.
It is often difficult to determine the
principal industrial activity or output
for a given facility. Every effort must
be made to research the principal
industrial activity or output for those
sources which have blanks in this field.
-200-
-------
6. Source Classification Categories must represent actual or
potential controlled emissions on the
basis of maximum operating rates per the
Alabama Power decision definition.
7. Source Compliance Status This must represent worst case compli-
ance of any point within a source. It
must be constantly updated for each
change in Federally enforceable stand-
ards.
3. Enforcement Actions Figure 13-1 shows each enforcement
action which should be entered into
CDS. This table is updated annually in
SSCD guidance materials to the regions.
9. Enforcement Dates Both Date Scheduled and Date Achieved
are critical to the accurate tracking of
enforcement actions.
The above data elements represent only 10 percent of the total data ele-
ments available for retrievals in the system. The first six are relatively
static fields. Once they have been entered correctly on the CDS data base,
, they are not likely to change frequently. The last three are dynamic, likely
to change frequently especially for sources out of compliance with emission
limitations. If users can make an annual effort to verify the accuracy of
the first seven data elements foe each source within their jurisdiction and
make a quarterly effort to update the last three data elements, the CDS data
base would be more usable to States, regions and headquarters.
Data elements other than those described above may be critical to the
internal management needs of a specific region or a specific State; however,
these other data elements need not be included in minimum national data
standards designed to maintain the usefulness of the data base with a minimal
amount of data entry effort.
-201-
-------
Source of Action
' Action Description EPA STATE
Case Development Inspection X
State Inspection X
Overview Inspection X
NOV Issued X X
State Administrative Order X
State Consent Agreement X
State Court Order X
Civil Action X
Civil Penalty Assessed X X
Civil Penalty Collected X X
Criminal Action X
Federal Consent Agreement Signed X
Federal Court Order X
EPA 113a (1) SIP Order Issued X X
EPA 113a (3) Order Issued X
EPA 113a (5) Stop Construction Order Issued X X
113d (1) Order X
113d (2) Order X
113d (3) Replacement/Shutdown Order X X
113d (4) Innovative Technology Order X X
113d (5) Coal Conversion Order X X
Primary 119 Smelter Order X X
Civil Referral to SSCD X
Criminal Referral to SSCD X
Submission of Final Control Plan - Increment IX X
Binding Commitment of Purchase Control Equipment - X X
Increment 2
Start Construction - Increment 3 XX
End Construction - Increment 4 XX
Final Compliance - Increment 5 XX
Source Test Conducted X X
Source Test Observed X X
Certification of Compliance X X
State Permit Issued X
EPA Permit Issued X
Start of Construction for New Source Programs X X
Date of Start-up for New Source Programs X X
Applicability Determination X X
Application Complete X X
Figure 13-1. Enforcement Actions Required for FY 1981
-202-
-------
13.3 Data to be Tracked for Selected Sources
The previous section described the data elements which are required for
all COS sources, regardless of industry or compliance status. A great deal
of the system's capabilities have been designed to meet the needs of tracking
special industries, special air program requirements and special compliance
situations. As a general rule, the minimum data requirements for selected
sources is greater than for all sources. The following list of selected
sources is accompanied by the data requirements of these sources in addition
to the previously mentioned data elements. Both the list of selected sources
and the data requirements for these sources is subject to guidance updates
necessitated by program planning and regulation changes.
Selected Source Category Regional CDS Data
SIGNIFICANT VIOLATORS as defined For each emission point enter:
in the Bennett memorandum of Compliance Status (CMST)
12/29/81 titled "EPA Account- Point-specific Enforcement Action
ability System - OANR Policy Process Description (PDRS)
Guidance" Pollutant Code (PLUT)
SIP Code (if on or negotiating a com-
pliance schedule).
At the source level in addition to
the data elements already mentioned,
enter:
Pollutant Air Quality Control Indi-
cator (PAQC)
Pollutant Compliance (PCMS)
Pollutant (PLLT)
New sources, e.g., NSPS, PSD, Emission point data should be entered
NSR for the same data elements as for
significant violators. In addition,
Air Program Status (APST) and Pro-
x cedural Compliance (CMS2) should be
entered *
Commercial boilers, institutional Emission point data should be entered
boilers and coal fired boilers for the same data elements as for
for industries other than power significant violators. In addition,
plants (SIC 4911) the SCC Code and the Capacity Code
(heat input capacity in MMBTU's)
should be entered.
-203-
-------
The above minimum national standards may be augmented by regional or
State requirements .in order to meet specific management objectives. By
entering the above process level data for selected sources, the usefulness of
the CDS system will be maintained with a minimal amount of data entry effort.
13.4 Quality Control for Required Data Elements
Each regional CDS manager has the responsibility of managing all the data
entered on the CDS data base and for providing an ongoing quality assurance
program to maintain the accuracy of the data base. In order to fulfill these
responsibilities, the regional Enforcement Division must have manual proce-
dures and an information flow network to make sure that the CDS manager is
aware of all new information for stationary sources and air pollution coming
into the regional office. The CDS data manager should decide what
information is applicable to CDS and what is not.
For information which is applicable and required for CDS, the regional
manager should keep records of all documents crossing his/her desk through
the use of a CDS Log Book. A Log Book can be used to record the type of
information received, the date it is received, the date it is coded, the data
it is run through the CDS Edit, and the date it is checked out through a
retrieval report. With this log, the CDS manager can show that the
information which should be entered into CDS is actually placed on the CDS
data base.
Once CDS data has been coded, the CDS manager needs a tool for monitoring
the data which is being added, changed or deleted on the CDS data base. This
tool is currently available in the Critical Data Element Report generated by
the Update process. This report tallies up additions, changes and deletions
of selected data elements.
-204-
-------
Figure 13-2 shows a sample Critical Data Element Report. On this report
activity for key data elements such as Source Name, Source Compliance, Source
Emission Category and enforcement actions are shown for the current update
cycle as well as a cumulative total for the fiscal year.
3y reviewing this report after each weekly update cycle, the CDS manager
can research any unexpected changes and will have a record of his
achievements and the achievements of his staff. If this report shows any
unexpected changes, the manager can run a retrieval using the Date Updated as
a selection criterion to list each of the changes.
The above report is especially useful if there are several different or-
ganizations within the region entering data into the system. For exampla,
the region can easily detect changes in compliance status, emission category
and schedule date foe data directly entered by a State or by a contractor.
The manager should monitor all significant changes to his data base and
follow up on any problem areas before minor problems escalate into major
problems.
In addition to keeping a log to make sure that all data which should be
e.icered is actually entered into CDS, and to monitoring changes to !
-------
.ICAI. DATA rl.l'.ltr.NT
1
M
0
CT1
1
n'/;'r./ii coiiri.l ANCF. PAIA SYSTI.II
Suirril CAIMI.INA IIATA FOR RF.CIOH ', - ATLANTA
oitTi'nr sr.iii AI. <. i
STTI'. CIJTY SUCK APCII ''.CMS CI.AS f.LCT S" 1 1. APTi: IITAC
cinii: emu. mil: OLD somici IIAMF in.u nouiiCF NAIII on ON o i1 n i: ni.n m:» en ni.i. cue
>,:'. o'if.ii onif. s ursTi'ACOMH.rnciiF.ii nv A? n
', ) ')( ".II noil-)) KKIIF.RAI linclll. AI n
/, > |O'iO OniM1! nllPONT.i: 1 : FI.OIIF.HCK n AI 1 2
/,' |?00 HOII II STKVI'.HH, .IP-I'ARKKII II AI
/, ' i:-n(i nfoin nii.CARni ni: sconp.nv. i H A?
/,- | ion ni|o;>2 STF.VENS , 1 P-TAYI.OR S « 2 AI B *
/,? 11.0(1 00(119 IIF.HIIITACK COTTON II I L 1 1
', if. r,n (innn/, SP 111 lies I iu> : inii.i. ins 1 ?
/, j if, no ooni/i CAROLINA FOHF.ST IHD on AI i
A.I IfU.O Olldlf, I'l.AN DI'.MPSr.Y I.I'IIIIER 0 0 It 1
/, i ("on nnn 1 7 r.'HlAltr. l) COIIPAIIY 1 4
/i > I'lno (inn in II, INK IIIOH f. HTFRL ? 1
/.7 |"cl(l nnilio Cdl.llMIIIA Mi;USPAPF.RS AJ R
'.;: r'ou (KHI61 iii.YTiiF. uiniisTRiKS A?
/. - |''i|i> ooo'i 1 HI.YTIir. llllil'STHIKS n n A .
', " ~"'l.<\ 0011(17 riKKflTONF. STRTI. I'liOH SP.MtTMIHIC STP.F.I. PIUII)
/, ' Mil. II (|i|H7r) UNION CAIIT iMIU.TIUAI.I. II'IION C AM : CAN PCItn I'T
/. ? ".'ill Olioil? PIIARR YAliriS AI A?
'. ' ",/,(! 0(>ll6'i TIIAYHOK CIII.III CAI. CO. 1 I
1' AC L ? 1
MlimilTII 11 Y
IK: KT ni IIT
*
*
* r.u
*
*
A
CM
rn
* CN
* r.n
en
A
A
fc
A
lY
r.n
13-2. Sample Critical Data Element Report
-------
steps described above will encourage an accurate data flow, allowing manage-.
ment at every level access to accurate CDS reports which will enable them to
measure the success of their enforcement programs, identify problem areas
early and schedule activities to optimize the use of available resources and
budget.
13.5 Summary of Data Standards Recommendations
Complete, accurate and timely data entry techniques are the most critical
elements of a successful CDS. Enforcement personnel at the regions, Statas
and headquarters should make sure that:
* The CDS manager receives adequate on-going training in enforcement
issues, CDS operations and data processing concepts.
« Quality assurance techniques are being followed on a regular basis.
All technicians, engineers and contractors who use CDS are
properly trained.
The local procedures and information flow network are reviewed
periodically in an effort to eliminate bottlenecks and to minimize
the effort needed to meet CDS data standards.
If all users follow the steps outlined above, the system will continue to
be one of the best national EPA systems.
-207-
-------
14.0 CDS GRAPHICS
Although SSCD together with all regions and selected States has been
highly successful in using various CDS reports such as the Milestone Report
and the Quick Look Report in managing the stationary source enforcement pro-
gram, SSCD management realized that they needed improved methodologies during
the 1980's for depicting the large quantities of data contained on the CDS
data base. Computer-generated maps and graphs of CDS data are designed to
convey a great deal of information about conspliar.ca analysis in a format: rsuct!
more easily understood than traditional CDS reports.
Computer graphics output of CDS data provides clear and effective depic-
tions of trends, relationships and comparisons.
Currently, the following graphic outputs are available to CDS users:
Bar charts, pie charts and line graphs of source distributions,
compliance distributions and enforcement action distributions.
Bar charts, pie charts and line graph's of historic trends and
changes in compliance and in enforcement activity.
National, regional and State maps showing the location of selected
sources such as power plants in violation, steel mills in comoli-
ance, all sources in non-attainment areas and any other logical
grouping of sources which can be selected by the CDS retrieval.
CDS graphics such as bar charts or maps are not direct replacements for
detailed CDS reports such as the Source Data Report or the Quick Loo::
Report. Users who need detailed, specific data for a certain source of
pollution or a group of sources should continue to rely on these reports for
the day to day handling of compliance and enforcement information.
-208-
-------
15.0 CONTINUOUS MONITORING SUBSET
CDS is primarily designed for the storage and retrieval of non-pararaetric
stationary source enforcment information. This enforcement and compliance
history information can sometimes be combined with other kinds of control
equipment and emission level data for more effective monitoring of the air
enforcement programs' effectiveness. To that end, SSCD supports a separate
Continuous Monitoring Subset of CDS, designed to handle emission data not
normally found in CDS. Information on the entry and retrieval of data in
this system can be found in the Continuous Monitoring Subset User's Guide,
available from Mr. Franklin C. Smith at FTS 382-2833.
-209-
-------
APPENDIX A
CDS
DATA ELEMENT DICTIONARY
A.I SOURCE LEVEL DATA ELEMENTS
A.2 POINT LEVEL DATA ELEMENTS
A.3 ACTION LEVEL DATA ELEMENTS
A.4 COMMON TO ALL CARDS DATA ELEMENTS
-------
DATA ELEMENT DICTIONARY
A-l
A-2
A-3
A-4
A-5
A-6
A-7
A-8
A-9
A-iO
A-ll
A-I:
A-l 3
A-I 4
A-15
A-iS
A-I7
A-ia
A-19
A-20
A-21
A-22
A-2 3
A-24
A-25
A-26
A-2 7
A -23
A-30
A-31
A-32
A-33
A-3 4
A-35
A-2 6
A-37
A-33
A-39
\--;G
A-41
A-4 2
A-43
A-44
A-45
A-46
A-47
A-48
Data Element
SOURCE LEVEL
Air Program Code
Air Program Code Description
Air Program Status
Air Program Status Description
Air Quality Control Region
Facility Capacity
City Code
City Name
County Code
County Name
Date of Last Inspection
Date Last Updated
Governmental Facility Code
Loading Derivation Code
NEDS Cross-Reference Number
Pollutant Air Quality Maintenance Indicator
Pollutant Air Quality Control Indicator
Basic Pollutant Information
Pollutant ID
Combined Pollutant & Pollutant Air Quality
Control Indicator
Pollutant Compliance
Pollutant Emission Category
Pollutant Classification
Pollutant Loading
Pollutant Delete Flag
Pollutant Delete Flags - BPLD
Region
Region, Seate, County
Region State County Source
Regional Data Element 1
Regional Data Element 2
Regional Data Element 3
Regional Data Element 4
Regional Data Element 5
Regional Data Element 6
Regional Data Element 9
Regional Data Element 10
Regional Data Element 11
Abbr.
Data Tvoe
P.ag
Data Element 12
SIC Code
SIC Description
Source Classification Code
Source Classification Group
Source Compliance Status
Source Compliance Status Description
Source Compliance Status - 8 Qtrs.
Monthly Historic Compliance - 24 Mos.
APCD
APDS
APST
APSD
AQCR
FCAP
CYCD
CYNM
CNTY
CTNM
DTLI
UPDA
FEDF
LDRC
NEXS
PAQM
PAQC
BPLT
PLLT
PLPQ
PCMS
PECT
PCLS
LOAD
DROP
BPLD
REGN
RGSC
RSCS
RDE1
RDE2
RDE3
RDE4
RDE5
RDE6
RDE9
RD10
RD11
RD12
SICC
5ICD
CLAS
CLAG
SCMS
SCSD
SCSO
MSOO-24
S
S
S
S
S
S
S
S
S
S
c
S
S
s
S
S
S
S
S
S
S
S
S
S
S
S
c
S
S
S
S
S
S
S
S
S
S
S
o
S
5
S
S
S
S
S
S
A-l
-------
DATA ELEMENT DICTIONARY
Page Data Element
A-49 Source Emission Category
A-50 Source Emission Category Description
A-51 Significant Violator Flag
A-53 Source Name
A-58 Source Name (Short)
A-59 Source Number
A-60 Staff Name (Source)
A-61 Staff Personnel code - Source
A-62 Priority Code
A-63 State
A-65 State Abbreviation
A-66 State County Source
A-67 Source Number (Last 4 Digits)
A-68 State County Source (Last 4 Digits)
A-69 State Registration Number
A-70 Street Address
A-71 Zip Code
POINT LEVEL
A-72 Capacity Code
A-73 Compliance Status
A-75 Compliance Status Description
A-76 Dun 4 Bradstreet Number
A-77 Emission Category
A-78 Emission Category Description
A-79 Emission Point Number
A-80 Multiple Cross-Reference
A-81 Old Compliance Status
A-32 Pollutant Code
A-33 Procedural Compliance
A-34 Process Description
A-85 Regional Data Element 7
A-36 Repeating Violator Flag
A-87 Repeat Violation Date
A-88 SCC Code
A-89 SIP Code
A-90 SIP Code Description
A-91 State Regulation
A-92 Turnover Compliance Flag
ACTION LEVEL
A-93 Action Description
A-94 Action Number
A-95 Action Type
A-96 National Action Type
A-97 National Action Description (Long)
A-98 National Action Description (Medium)
A-99 National Action Description (Short)
Abbr.
Data Type
SECT
SECD
SVIL,
SNME
SNMS
SRCE
STFS
PERS
PRIO
STTE
STAB
STCS
SRC 4
SCR4
STRG
STRT
ZIPC
CAPC
CMST
CMDS
DBNO
ECAT
ECDS
PTNO
MULT
OCSO
PLUT
CMS2
PROS
RDE7
RPTV
REDT
SCC3
SIPC
SIDS
SREG
TORN
ADES
ANUM
ATPE
ACNL
ADNL
ADNM
ADNS
S
S
SVI1-4 S
S
S
S
s
s
s
s
s
s
s
s
s
s
s
p
a
P
P
P
?
P
P
P
o
z
p
P
?
P
3
?
P
P
P
A
A
A
A
A
A
A
A-2
-------
DATA ELEMENT DICTIONARY
Page Data Element Abbr. Data Type
COMMON TO ALL CARDS
A-100 Date Achieved DTAC A
A-101 Date Achieved Year DAYY A
A-102 Date Achieved Year/Month DAYM A
A-103 Date Scheduled DTSC A
A-104 Date Scheduled Year DSYY A
A-105 Date Scheduled Year/Month DSYM A
A-106 Civil Penalty Amount PLTY A
A-107 Regional Data Element 8 RDE8 A
A-108 Results Code STAC A
A-109 Results Code Description RSTD A
A-liO Staff Name (Action) STFA A
A-lll Action Staff Code PERA A
A-112 Staff Title TITL A
A-113 State County Source Point Action SCSA A
A-114 Card Code
A-115 Comments
A-116 Line Number
A-117 Record Type
A-118 Update Code
A-120 Five Position - Filler BLKl
A-121 Fifteen Position - Filler BLK2
A-3
-------
A.L SOURCE LEVEL DATA ELEMENTS
-------
AIR PROGRAM CODE
Definition: AIR PROGRAM CODE is a source indicator used to separate NSPS
sources, NESHAPS sources, sources subject to federal EPA
jurisdiction, and sources subject to state jurisdiction.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Lenath
Data
Tupe
Justified
Required on
New Entry
Nationally
Controlled
APCD
2
65
1
ALPHANUMERIC
N/A
NO
YES
Valid Values:
0 - SIP Source
1 - SIP Source under
jurisdiction
5 * other
6 - PSD
7 - NSR
8 - NESHAP
Master file
Record Tupe
Master file
Position
Masterfile
Length
federal
20
115
1
Edit Error Messages:
INVALID AIR PROGRAM CODE
*** = Fatal Error
Warning Error
Ceding Considerations:
For a SIP source, the State has primary jurisdiction for enforcement
activity, except for sources under direct federal jurisdiction.
If a given source is subject to several air program regulations, multiple
source numbers should be assigned, one for each program.
To help tie together a facility subject to several programs, use the NEDS
source number for the last four positions of each source number and the air
program code as the first position of the source number.
CDS DATA DICTIONARY
A.1-1
-------
AIR PROGRAM CODE DESCRIPTION
Definition: AIR PROGRAM CODE DESCRIPTION is the English language description
of the Air Program Code. It is generated by the computer for
Quick Look Reports based on the value of APCD.
Retrieval
Abbreviation
Card
_Type_
Card
Columns
Data Element
Length
Data
_Tupe
Valid Values:
APDS
N/A
N/A
20
ALPHABETIC
Justified
N/A
Masterfile
Record Type
N/A
Required on
Entry
NO
Masterfile
Position
N/A
Nationally
Controlled
YES
Masterfile
Lenqth
20
Edit Error Messages:
_*** = Fatal Error
* = Warning Error
Ceding Considerations:
APCD
0
1
4
5
6
7
3
9
AIR PROGRAM DESCRIPTION
SIP Source
SIP Federal
ESECA
Other
PSD
NSR
NESHAPS
NSPS
CDS DATA DICTIONARY
A.1-2
-------
AIR PROGRAM STATUS
Definition: AIR PROGRAM STATUS represents the operational condition of a
facility for a given air program. This field is particularly
applicable for NSPS, NSR, PSD and NESHAP sources. If different
points have different operating statuses, the APST should
reflect the most advanced operational status of all the points.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
-Type
Justified
Required on
i'/ew Entry
Nationally
Controlled
APST
2
66
1
ALPHANUMERIC
N/A
NO
YES
Valid Values:
0, P, C, D, R, S, T, X
Master file
, _ 20
Record Type
Masterfile
Position
Masterfile
Lencjth
Zdit Error Messages:
INVALID AIR PROGRAM STATUS
*** = Fatal Error
* = Warning Error
Ceding Considerations:
Valid Values:
C
T'
X
D
- Operating
- Planned (has applied for a construction permit)
- Under Construction
- Temporarily Closed - Shutdown
- Permanently Closed or Dismantled
- NESHAP Demolition \
- NESHA? Renovation \ Should be used only for sources wir.h A?CD=
- NESHAP Spraying )
CAS DATA DICTIONARY
A.1-3
-------
Definition:
AIR PROGRAM STATUS DESCRIPTION
AIR PROGRAM STATUS DESCRIPTION is the English language descrip-
tion of the Air Program Status, generated for Quick Look Reports.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Tune
Justified
Required on
New Entry
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
APSO
N/A
N/A
1Q
N/A
N/A
NO
YES
Valid Values:
Master file
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error
N/A
N/A
10
-
Coding Considerations:
Valid Values:
0 - Operating
P - Planned (has applied for a construction permit)
C - Under Construction
T - Temporarily Closed - Shutdown
X - Permanently Closed or Dismantled
D - NESHAP Demolition \
R - NESHAP Renovation \ Should be used only for sources with APCD=3.
S - NESHAP Spraying I
CDS DATA DICTIONARY
A.1-4
-------
AIR QUALITY CONTROL REGION
Definition: AQCR is the Air Quality Control Region, a three digit numeric
value.
Retrieval
Abbreviation ^"
Card
Type
Card _ _
Columns 2°-22
Data Element
Length
Data
NUMERIC
Type
T * ' * J LEFT
Justified
Required on
YES
Ne" Entry
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
Valid Values:
Must be valid for
county codes used
valid. Please co
Code/AQCR Table.
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error
the state and the
Blank is also
ntact the central
AQCR to the County
20
21-23
3
Coding Considerations:
The County Code/AQCR Table containing all valid AQCR's can be listed by
following the directions in Chapter 10.
CDS DATA DICTIONARY
A.1-5
-------
FACILITY CAPACITY
Definition: FACILITY CAPACITY indicates the total output capacity of the
principal product produced at a facility. This might be
expressed as barrels per day/ megawatts, etc.
Retrieval pCAp
Abbreviation
Valid Values:
Card
Type
Card
Columns 58'64
Data Element
Lencrth '
Data
Type NUMEMC
Justified RIGHT
Required on
New Entry
Nationally
Controlled NO
Edit Error Messages;
*** = Fatal Error
Masterfile
Record Tgpe
Masterfile . ., . 0
Position 42-48
Masterfile
Length
* = Warning Error
Coding Considerations:
a. For general processes, use tons per year of output product. If a
facility produces over 10 million tons per year, code all 9's in this
field.
b. For refineries, use barrels of petroleum processed per calendar day.
c. For petroleum storage facilities, use thousands of barrels total
capacity.
d. For incinerators (sewage sludge or municipal refuse), use tons osr
day/incineration rate.
e. For electric utilities, use total megawatt design capacity.
f. For coal-fired boiler sources, use Million British Thermal Units per
Hour (MMBTUH) heat input capacity.
This field is a confidential data element. An appropriate password must be
used to access this field's data.
CDS DATA DICTIONARY
A. 1-6
-------
CITY CODE
Definition: CITY CODE is a four
Codes can be found in
Retrieval CYCD
Abbreviation
Card
Type
Card 23-26
Columns " "
Data Element
Length
Data
NUMERIC
Type
Justified LEFT
Required on
Nev Entry
Nationally
Controlled NO
Edit Error Messages :
*** = Fatal Error
digit numeric city identifier.
the SAROAD manual.
Valid Values:
If the field is being used,
be a four digit numeric code
the SAROAD manual.
Masterfile
Record Type
Masterfile ^_^
Position
Masterfile
Length
* = Warning Error
The City
it should
found in
Coding Considerations:
City codes are available from the Storage and Retrieval of Aerometric Data
(SAROAD), Volume V.
SAROAD Manuals are available on request from the EPA's Office of Air
Quality Planning and Standards.
CDS DATA DICTIONARY
A.1-7
-------
CITY NAME
Definition: CITY NAME gives the location of the facility.
Retrieval
... . . C iNM
Abbreviation
Valid Values:
All alphanumeric characters.
Card
Type
Collns 2°-34
Data Element
Length
Data
ALPHANUMERIC
Justified LEFT
Required on
Vew &:try
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
Masterfile
Record Type
Masterfile ^_^
Position
Masterfile ._
Length
* = Warning Error
Coding Considerations:
If abbreviations are used, they should be used consistently for
to facilitate sorting and retrievals.
CDS DATA DICTIONARY
A.1-8
-------
COUNTY CODE
Definition:
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
COUNTY CODE is a four
County Codes are derived
CNTY
1-8
5-8
4
NUMERIC
LEFT
YES
YES
digit numeric county identifier.
from the SARD AD manual.
Valid Values:
All county codes must be present
the CDS County Code/AQCR Table.
»*sterfile 2Q_47
Record Type
Master file
Position
Master file
4
Length
The
on
Edit Error Messages;
*** = Fatal Error
* = Warning Error
Coding Considerations:
Please contact the National DEC to update the county code file. County
code must be present on all transactions; it cannot be changed or blanked
out on the data base.
CDS DATA DICTIONARY
A.1-9
-------
COUNTY NAME
Definition: COUNTY NAME is generated by the Edit from the COUNTY CODE.
Retrieval
_ , . ... \- inn
Abbreviation
Card
Type
Valid Values:
See Chapter 10 for instructions for
listing the county names valid for
each region/state/county combination.
Card
Columns
Data Element
Length
Data
Type ALPHABETIC
Justified
Required on
New Entry
Nationally
Controlled
Master file
Record Type
Masterfile I63_l?9
Position
Masterfile
Length
Edit Error Messages:
*** = fatal Error
* = Warning Error
Coding Considerations:
This field is generated; it cannot be coded. The national DEC maintains a
table of COUNTY CODE/COUNTY NAME combinations.
CDS DATA DICTIONARY
A.1-10
-------
DATE OF LAST INSPECTION
Definition: DATE OF LAST INSPECTION is generated by the system using
specially identified regional action types and .the date achieved
for these actions. This field is available for retrieval only.
The inspection actions to affect this field are each region's
actions that correspond to the National Actions for inspection:
1A - EPA Inpsection
2A - EPA Source Test Conducted
3A - Owner/Operator-Conducted Source Test
5C - State Inspection
6C - State Source Test Conducted
Retrieval
Abbreviation
Card
Tuoe
Card
Columns
Data Element
Length
Data
T:jr,e
Justified
Required on
Vev Entry
Nationally
DTLI
N/A
N/A
6
NUMERIC
N/A
N/A
N/A
Valid Values:
National Actions:
Master file
Record Type
Masterfile
Position
Masterfile
Length
20
181-186
6
Sdit Srror Messages-.
*** = Fatal Error
* = Warning Error
Coding Consider ations :
CDS DATA DICTIONARY
A.1-11
-------
DATE LAST UPDATED
Definition: DATE LAST UPDATED represents the most current date on which an
input transaction was added or changed for any part of a
facility on the masterfile.
Retrieval
Abbreviation
Card
Type
Card
Columns
Length
NUMERIC
Edit Error Messages-.
Valid Values:
Justified
Required on
.V«w Entru
Ua cionally
Controlled
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
20
134-139
6
_*** = Fatal Error
* = Warning Error
eding Considerations:
This date is in year, month, day format on the CDS Masterfile. It should
be retrieved in month, day, year format on CDS RETRIEVAL REQUEST FORMS.
CDS DATA DICTIONARY
A.1-12
-------
GOVERNMENTAL FACILITY CODE
Definition: GOVERNMENTAL FACILITY CODE identifies facilities owned or
operated by a governmental unit. This code was formerly called
the Federal Facility Code.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
FEDF
2
64
1
NUMERIC
NO
YES
Valid Values:
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
20
113
1
Edit Error Messages-.
*** = Fatal Error
* = Warning Error
Coding Considerations:
Valid Values;
1 - Source owned or operated by the federal government.
2 - Source owned or operated by the state.
3 - Source owned or operated by the county.
4 - Source owned or operated by the municipality.
5 - Source owned or operated by the district.
Blank/0 - All other facilities not owned or operated by a federal state, or
local government.
CDS DATA DICTIONARY
A.1-13
-------
LOADING DERIVATION CODE
Definition: LOADING DERIVATION CODE indicates the method of emissions
estimation used to determine the source classification code for
the source.
Retrieval
Abbreviation
Card
Columns
Data Element
Length
LDRC
79
Valid Values:
A * Actual or estimated actual
P Potential controlled per Alabama
Power decision
I * Incomplete source loading
information
Blank = Assumed potential controlled
per Alabama Power decision
Data
Tuoe
Justified
Required on
New Entry
Nationally
Controlled
ALPHABETIC
N/A
NO
NO
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
30
52
1
Sdit Error Messages:
_*** = Fatal Error
Warning Error
Coding Considerations:
The Loading Derivation Code must be coded for all Class Al sources.
If LDRC is equal to "A1 at least one pollutant for that source must have
emissions in the pollutant loading field equal to or greater than 100 tons
per year.
CDS DATA DICTIONARY
A.1-14
-------
NEDS CROSS-REFERENCE NUMBER
Definition: NEDS CROSS-REFERENCE is the NEDS facility identifier.
Retrieval
Abbreviation
Card
Tupe
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
tJev Entry
Nationally
Controlled
NEXS
2
55-58
4
ALPHANUMERIC
LEFT
YES
YES
Valid Values:
All alphanumeric values.
Masterfile
Record Type
Masterfile ,
. . 105-108
Position
Masterfile
Lenqth 4
Edit Error Messages-.
Fatal Error
_* = Warning Errot
Coding Considerations:
Whenever a new facility is being added as New, this field must be ceded.
If the NEDS number is not known, please consult the AEROS contact in your
area to get a NEDS facility number. AEROS contacts are listed in
Appendix B of this manual.
For Source numbering convenience, the last four positions of Source Number
should be the NEDS Crcss-Reference Number. If this method is used, the
first digit of the CDS Source Number should be the Air Program Code.
CDS DATA DICTIONARY
A.1-15
-------
POLLUTANT AIR QUALITY MAINTENANCE INDICATOR
Definition: POLLUTANT AIR QUALITY MAINTENANCE INDICATOR indicates whether or
not the pollutant
Retrieval
Abbreviation
Card
Tupe 3
inpacts AQMA standards or not.
Valid Values:
Blank - NO
Y - YES
c"Ls 27; 39; 5l
Data Element.
Length
Data
ALPHANUMERIC
Tupe
Justified
Required on
NO
Wew Entru
Nationally Y£S
Controlled
3d it Error Messages;
*** = Fatal Error
tfasterfile
Record Type
Masterfile wonm
Position
Masterfile
Length
* = Warning Error
Coding Considerations:
The default value is blank indicating 'NO1.
Note: This data element is no longer used as of 10/1/82.
CZ5S DATA DICTIONARY
A.1-16
-------
POLLUTANT AIR QUALITY CONTROL INDICATOR
Definition: POLLUTANT AIR QUALITY CONTROL INDICATOR shows whether or not a
source emits a criteria pollutant for which its county is
nonattainment. When coupled with the pollutant ID (PLLT), the
exact nonattainment status, by pollutant, is indicated for the
county the source is located in.
Retrieval
Abbreviation
Valid Values:
A, N, U, 1, 2
Card
Type
^f 28; 40; 52
Columns
Data Element
Length
Data
ALPHANUMERIC
Type
Justified
Required on
Nev Entry YES
Nationally
VP^
Controlled
Edit Error Messages;
*** = Fatal Error
Masterfile
Record Tupe
Masterfile
_ .. . REPEATING
Position
Masterfile
Length
* = Narnina Error
Coding Considerations:
blank - Attainment area for a given pollutant
A - Attainment area for a given pollutant
N - Nonattainment for primary and secondary standards for a given poiiuca.-.^
1 - Nonattainment for primary standards only, for pollutant SO2
2 - Nonattainment for secondary standards only, for pollutants PT or S2
U - Unclassified
Consult the Federal Register for a complete listing of all attainment and
nonattainment areas. This list is periodically updated in the FeJaral
Register,
All attainment designations are at the county level. System limitations
preclude such designations at the sub-county level.
CDS DATA DICTIONARY
A.1-17
-------
BASIC POLLUTANT INFORMATION
Definition: BASIC POLLUTANT INFORMATION is designed to provide a single
Quick Look print line data element showing data for the
following Card 3 pollutants: Particulates, S02, VOC, CO,
NO.
Retrieval
... . .
Abbreviation
Card
N/A
Data Element
Length
61
Data
Type
ALPHANUMERIC
Valid Values:
Justified
Masterfile
Record Type
Required on
Entry
NO
Position
Nationally
Controlled
Masterfile
Length
Edit Error Messages:
** - Fatal Error
* = Warning Error
Coding Considerations:
BASIC PLUT- PLUT(2) DROP PCMS PECT
PAQC (1 EACH) LOAD (5)
PT 3 IN
PT 14N
PT 22N
PT 44N
2S2 42
1S2 44
12S2 02
3S2 42
22HC 04N
3HC 04N
40HC 01N
25HC 04N
ICO 01N
ICO 04N
35
ICO 04N
1N2 02
2N2 01
12
23
1N2 01 19
CDS DATA DICTIONARY
A.1-18
-------
POLLUTANT ID
Definition: POLLUTANT ID is used to identify the pollutant
pollutant compliance data is being entered.
foe which
Retrieval
Abbreviation
Valid Values:
PLLT
Card
Tune
Card
Columns
22-23; 34-35; 46-47
Data Element
Length
Data
Tuoe
ALPHANUMERIC
Justified
LEFT
Masterfile
Record Tgpe_
30
Required on
Entry
NO
Masterfile
Position
REPEATING
Wacionally
Controlled
YES
Masterfile
Lencrth
Edit Error Messages;
INVALID POLLUTANT CODE
_*'** = fatal Error
* = Harning Error
Coding Considerations:
This field must be filled in whenever repeating pollutant data is er.tsrsd
on a Card 3. No data for any of the repeating pollutant compliance data
elements can be placed on the Masterfile without a valid pollutant ID.
Valid Values:
AS - Asbestos
AS - Arsenic
BE - Beryllium
BZ - Benzene
CD - Cadmium
CZ - Coke Oven Emissions
CO - Carbon Monoxide
FL - Fluorides
HC - Hydrocarbons (volatile organic
compounds)
t:G - Mercury
N2 - N02
OD - Odors
OT - Other
PB - Lead
PT - Particulate Matter (total)
32 - SO2
TS - Total Reduced Sulfur
VE - visible Emissions
VC - Vinyl Chloride
2N - Zinc
CDS DATA DICTIONARY
A.1-19
-------
COMBINED POLLUTANT S PLUT AIR QUALITY CONT IND
definition: This data element combines two repeating pollutant data
elements: Pollutant (PLLT) and Pollutant Air Quality Control
Indicator (PAQC). This data element is foe retrievals only.
Retrieval
Abbreviation
PU?Q
Card
Tupe_
N/A
Valid Values:
Valid values for pollutants
combined with valid values for PAQC
Card
Columns
N/A
Data Element
^Length
Data
JType
ALPHANUMERIC
Justified
LEFT
Masterfile
Record Type
30
Required on
New Entry
N/A
rtasterfile
Position
N/A
Nationally
Controlled
YES
Masterfile
Length
Edit Error Messages;
Fatal Error
_* = Warning Error
Coding Considerations:
PLPQ is a 3 character field: the left 2 characters are formed from the
PLLT code (HC, PT, S2 ... Etc.), the right character is formed from the
PAQC code (A, 1 ... Etc.). In order to have a Quick Look or Milestone
Report of this data element, the data element must be used for selection.
CDS DATA DICTIONARY
A.1-20
-------
POLLUTANT COMPLIANCE
Definition: POLLUTANT COMPLIANCE indicates the source emissions compliance
foe a given pollutant based on the worst case emission point
producing the indicated pollutant.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Tyoe
Justified
Required on
tlew Entry
Nationally
Controlled
PCMS
3
25; 37; 49
1
ALPHANUMERIC
NO
YES
Valid Values:
0-9
Masterfile
Record Type
Masterfile ^WIXG
Position
Masterfile
Lenqth
Edit Error Messages-.
* INVALID COMPLIANCE STATUS
*** = Fatal Error
* = Warning Error
Coding Considerations:
Valid Values:
0 Unknown
1 In violation - no schedule
2 In compliance by source test
3 In compliance by inspection
4 In compliance by certification
5 Meeting compliance schedule
6 In violation, not meeting schedule
7 In violation, unknown with respect to schedule
8 No applicable emission regulation
S In compliance = closed down
Pollutant compliance (PCMS) and Pollutant ID (PLLT) must be maintained for
all Class A significant violators.
Order of worst case to best case pollutant level compliance:
PCMS = 1-6-0-7-5-4-3-2,8,9.
CDS DATA DICTIONARY
A.1-21
-------
Definition:
POLLUTANT EMISSION CATEGORY
POLLUTANT EMISSION CATEGORY represents the total potential
uncontrolled emissions of a given pollutant for a source.
Retrieval
Abbreviation
PECT
Data Element
LenaP.h
Data
NUMERIC
Edit Error Messages-.
INVALID EMISSION CATEGORY
_*** = Fatal Error
Valid Values:
0-4
Card
Type
Card
Columns
3
26; 38; 50
Justified
Required on
New Entry
Nationally
Controlled
Masterfile
Record Type
rtaster.fi.Ze
Position
Masterfiie
Length
30
REPEATING
1
* = Warning Error
Coding Considerations;
ECAT VALUE
0
1
2
3
4
SCAT DESCRIPTION
Unknown
Less than 100 TPY
100 to 1000 TPY
Over 1000 TPY
Less than 25 TPY
CDS DATA DICTIONARY
A.1-22
-------
POLLUTANT CLASSIFICATION
Definition:
POLLUTANT CLASSIFICATION assigns a source classification code
to
an individual pollutant in the repeating pollutant area.
Retrieval p<;LS
Abbreviation
Card
Type
'af 27, 39, 51
Columns
Data Element
Length
Data
ALPHANUMERIC
Type
.,. , LEFT
justified
Required on
New Entry N°
»Va tionallg
vpc
Controlled x"
Valid Values:
Input File
1 = Al
3 Az
B = B
U = Unknown
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
30
REPEATING
2
Edit Error Messages-.
* = INVALID POLLUTANT CLASSIFICATION
*** = fatal Error
_* = Warn ing Error
Coding Considerations:
This single character code on the input card will generate a one- or
two-digit code on the master file. The generated master file PCLS values
must be used for selection card values on a CDS retrieval.
Input
Values
1
2
B
U
Retrieval
Values
Al
A2
B
UK
CDS DATA DICTIONARY
A.1-23
-------
POLLUTANT LOADING
Definition: POLLUTANT LOADING indicates the annual pollutant loading of. a
given pollutant. The pollutant loading shown should be
compatible with the Source Classification Code (CLAS).
Retrieval
Abbreviation
Valid Values:
LOAD
Card
Type
Card
Columns
29-33; 41-45; 53-57
Da ta E 2.
Length
Data
Tuoe
NUMERIC
Justified
RIGHT
Masterfile
Record Type
30
Required on
New Entry
NO
Masterfile
Position
REPEATING
Nationally
Controlled
NO
Masterfile
Length
Edit Error Messages;
*** = Fatal Error
* = Warning Error
Coding Considerations:
If this field is used, it should be a numeric value representing emissions
in tons per year. No decimals or fractions should be used. Leading spaces
are acceptable, but not leading zeros, i.e., 00150.
To make this a meaningful data element, a source level comment (card
code 4) identifying the year of operation for the emissions listed should
always accompany this data element. However, please note that this code
(LOAD) is not intended to track annual emissions, but rather serve as an
indicator of, and justification for, the CLAS code indicated for this
source.
CDS DATA DICTIONARY
A.1-24
-------
Definition:
POLLUTANT DELETE FLAG
POLLUTANT DELETE FLAG is used to remove from the Masterfile all
data related to a repeating pollutant.
Retrieval DRQp
Abbreviation
Card
Tupe_ _
C"d 24; 36; 48
Columns
Data Element
Lenoth
Data
ALPHABETIC
Tt..' oe
Justified
Required on
, c. N0
Mew Entry
iVa tionalli)
YES
Controlled
3dit Error Messages:
INVALID POLLUTANT DELETE FLAG
NO DATA TO FOLLOW DELETE FLAG
*** = Fatal Error
T vC " p cr ^ 3nji ~< ' ' j r3 ~'"r ^t j on ^ *
Valid Values:
Blank or 'D1
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error
30
REPEATING
1
A 'D' in the Delete Flag signifies that the data entered for a given
pollutant should be completely eliminated. The pollutant compliance,
emission category, air quality maintenance indicator, air quality control
indicator, and loading are blanked out by the Update program when a 'D1 is
c-:dcc ;-.,?:;-. -c .: pollutant oc a Card 3.
This data element is valid for data entry only.
CDS DATA DICTIONARY
A.1-25
-------
POLLUTANT DELETE FLAGS - BPLD
Definition: POLLUTANT DELETE FLAGS for the Basic Pollutants is designed for
selection purposes to select combinations of Basic Pollutants by
testing various combinations of Pollutant Delete Flags.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Tupe
Justified
Required on
Mew Entry
Nationally
Controlled
BPLD
N/A
N/A
N/A
ALPHANUMERIC
NO
YES
Valid Values:
Blank or 'D1
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
30
66-70
5
Edit Error Messages-.
*** = Fatal Error
* - Warning Error
Coding Considerations:
CDS DATA DICTIONARY
A. 1-26
-------
REGION
Definition: REGION is a two position numeric region identifier
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Lenoth
Data
Tupe
Justified
Required on
iV-3v Entry
Wa tionall'j
Controlled
REGN
1-8
1-2
2
NUMERIC
LEFT
YES
YES
Valid Values:
01 through 10
See attachment showing the region
locations and the states associated
with each region.
Hasterfile ^
Record Type
Masterfile ,
Position
Masterfile
Length
Sdit Error Messages-.
***INVALID REGION CODE
*** = Fatal Error
* = Warning Error
Coding Considerations:
Region must be present on all input transactions. State code and region
are cross-validatad; the user may not use a state code which is not vails
for his region.
Region cannot be changed or blanked out once it has been put on the data
base. If it must be changed, the entire source must be deleted and
re-entered with the correct region code.
CDS DATA DICTIONARY
A.1-27
-------
REGION CODE
States have been assigned to regions as follows:
Region
States
01-Boston
Connecticut, Maine, Massachusetts, New Hampshire,
Rhode Island, 'Vermont
02-New York
New Jersey, New York, Puerto Rico, Virgin Islands
03-Philadelphia Delaware, District of Columbia, Maryland
Pennsylvania, Virginia, West Virginia
04-Atlanta
Alabama, Florida, Georgia, Kentucky, Mississippi,
North Carolina, South Carolina, Tennessee
05-Chicago
Illinois, Indiana, Michigan, Minnesota, Ohio, Wisconsin
06-Dallas
Arkansas, Louisiana, New Mexico, Oklahoma, Texas
07-Kansas City Iowa, Kansas, Missouri, Nebraska
08-Denver
Colorado, Montana, North Dakota, South Dakota, Utah,
Wyoming
09-San Francisco Arizona, California, Hawaii, Nevada, Guam, America
Samoa, Trust Territories
10-Seattle
Alaska, Idaho, Oregon, Washington
CDS DATA DICTIONARY
A.1-28
-------
REGION STATE COUNTY
Definition: REGION STATE COUNTY is a combined data element for retrieval
selection
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Lenath
Data
Tune
Justified
Required on
Wew Entry
Nationally
Controlled
Edit Error Messages-.
*** = Fatal Error
purposes.
Valid Values:
RGSC
N/A
N/A
8
N/A
N/A r^f^6 20, 30, 34, 46
Record Type
N/A Masterfile
Position
Masterfile
N/A Lenath 8
* = Warning Error
Coding Considerations:
See individual data elements "region, state, and county".
Format is Region Code 2 positions, State Code 2 positions, County Code 4
positions.
2xample: Fairfield County in Connecticut would be County Code 0265 in
State Code 07 in Region Code 01; so, REGION STATE COUNTY (RGSC) would be:
01070265.
CDS DATA DICTIONARY
A.1-29
-------
Definition:
REGION STATE COUNTY SOURCE
REGION STATE COUNTY SOURCE combines those four data elements for
selection purposes only.
Retrieval RQCS
Abbreviation
Valid Values:
Card
Type
Card
Columns
Data Element ^ ^
Length
Data
rupe NUMERIC
.^. - N/A
Justified
Required on
New Entry
nationally
Controlled N/A
Masterfile
, 20, 30, 34, 46
Record Tifoe
Masterfile
Position
Masterfile
Lenctn
Edit Error Messages:
*** = Fatal Error
* = Warning Error
Coding Considerations:
format is Region Code 2 positions. State Cede 2 positions, County Ccce -5
positions and Source Number 5 positions.
Example: To select Source Number 10003 in County Code 0265 in State
Code 07, Region 01, REGION STATE COUNTY (RCSC) would be: 0107026510003.
CDS DATA DICTIONARY
A.1-30
-------
REGIONAL DATA ELEMENT 1
Definition: REGIONAL DATA ELEMENT 1 - user supplied.
Retrieval ^^
Abbreviation
Valid Values:
All alphanumeric characters.
Card
Type
Card
Columns
Data Element
Lenath
Data
ALPHANUMERIC
Type
Justified
Required on
;Vew Entry
Nationally
Controlled
Masterfile
Record Tyoe
Masterfile
14°
Position
Masterfile
Length
Edit Error Messages-.
_*** = Fatal Error
* = Warning Error
Coding Considerations:
Typical usages of this field include identifiers for (as of March, 1982}:
Region I Attainraent/Nonattainraent, Archiving
Region II State delegation for NSPS, NESHAPS
Region III Attainment/Nonattainment
Region IV MSEE Priority Sources
Region V Significant Violators code-Id of orig. & new sources
Region VI SIP-PSD
Region VII Attainraent/Nonattairunent
Region VIII Attainment/Asphalt Plants
Region IX PSD NSR Applicability
Region X Major Sources
CDS DATA DICTIONARY
A.1-31
-------
REGIONAL DATA ELEMENT 2
Definition: REGIONAL DATA ELEMENT 2 - user supplied.
Retrieval
Abbreviation
RDE2
Carrf
Tijpe
Card
Columns
Data Element
Length
1
68
1
Data
ALPHANUMERIC
Valid Values:
All alphanumeric characters.
Justified
Required on
tVew Entry
Nationally
Controlled
Edit Error Messages^
_*** = Fatal Error
Master file
Record Type
Waster file
Position
Masterr"ile
Length
* = Warning Error
20
141
1
Coding Considerations:
Typical usages of this field include identifiers for (as of March, 1922)
Reqion I
Region II
Region III
Region IV
Region V
Region VI
Region VII
Region VIII
Region IX
Region X
Transitory/Nontransitory
State Regional Offices
State/Local Offices
State/Local Offices
SO2 Priority Status
NESHAP and PSD application numbers
Not subject to PSD but under review
Vapor Recovery
Future Effective Permit Processing
Indian Reservations
C£S DATA DICTIONARY
A.1-32
-------
REGIONAL DATA ELEMENT 3
Definition: REGIONAL DATA ELEMENT 3 - user supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Tupe
Justified
Required on
New Entry
Nationally
Controlled
RDE3
1
69
1
ALPHANUMERIC
NO
NO
Valid Values:
Hasterfile
Record Type
Master file
Position
Master file
Length
20
142
1
Edit Error Messages'.
*** = Fatal Error
Warning Error
Coding Considerations:
Typical usages of this field include identifiers for (as of March, 1932):
Region I
Region II
Region III
Region IV
Region V
Region VI
Region VII
Region VIII
Region IX
Region X
Sources to be Archived
PSD Regulations Flag
MSEE Identifier - State Tracking Information
Major SIP Sources
Significant violator enforcement responsibility
Continuous Monitoring
Subject to State Audit
Mobile Sources - Significant Violators
CDS DATA DICTIONARY
A.1-33
-------
REGIONAL DATA ELEMENT 4
Definition: REGIONAL DATA ELEMENT 4 - user supplied.
Retrieval
Abbreviation
Valid Values:
RDE4
Card
Type
1
Card
Columns
70-74
Oat a Element
Length
ZJata
Type
ALPHANUMERIC
Justified
Required on
New Entry
Nationally
Controlled
Edit Error Messages-.
*** = Fatal Error
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error
20
143-147
5
Coding Considerations:
If there is a need to have a second SIC Code for a facility, i.-.is field
could be used since it appears next to the SIC code on the Source Data
Report. If this data element is used for SIC Code, only the first four
positions may be used; columns 70-73 must be numeric and column 74 must be
blank.
Other typical usages of this field include identifiers for (as of Maich.
1982):
Region II Enforcement Docket Number, PSD, applicability source type flag
Region III Major Bulk Terminal
Region IV Additional Staff Codes
Region V SIC Codes - Minnesota
Region VII Nebraska Case Numbers
Region VIII Continuous. Monitoring
Region IX VOC Numbers
CDS DATA DICTIONARY
A.1-34
-------
REGIONAL DATA ELEMENT 5
Definition: REGIONAL DATA ELEMENT 5 - user supplied.
Retrieval
, .. . . KUCO
Abbreviation
Valid Values:
All alphanumeric characters.
Card
Type l
Card
r- i 75~79
Columns
Data Element
Length
Data
ALPHANUMERIC
_Type
Justified
Required on
NO
Wew Entry
Nationally
Controlled N0
Masterfile
20
Record Type
Masterfile ^Q_152
Position
Masterfile
Length
Edit Error Messages:
_*** = Fatal Error
* ~ Warn inQ Error
Coding Considerations:
Typical usages of this field include identifiers for (as of !'ar"h, !?37.;:
Region II
Region III
Region V
Region IX
Region X
Multiple Docket Numbers, Federal facility types
Docket System Flags
Indiana Information
State Cross-Reference Numbers
Tertiary SIC Codes, Federal facility types
CDS DATA DICTIONARY
A.1-35
-------
REGIONAL DATA ELEMENT 6
Definition: REGIONAL DATA ELEMENT 6 - user supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Lenoth
Data
Type
Justified
Required on
tie* Entry
Nationally
Controlled
RDE6
2
67-76
10
ALPHANUMERIC
NO
NO
Valid Values:
All alphanumeric characters.
Masterfile
Record Tyoe
Masterfile ^^
Position
Masterfile
Length
£c?it Error Messages:
*** =-Fatal Error
_* = Warning Error
Coding Considerations:
Typical usages of this field include identifiers for (as of March. I?"
Region V
Region VI
Region VII
Region IX
Region X
Additional Pollutants - Steel Information
PSD Permit Numbers
ESECA OFU Numbers
Stage II Noncompliance - MSEE Number
GSA Federal Facility Number
CDS DATA DICTIONARY
A.1-36
-------
REGIONAL DATA ELEMENT 9
Definition: REGIONAL DATA ELEMENT 9 - user supplied.
Retrieval
Abbrevia tion
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
RDE9
3
65-71
7
ALPHANUMERIC
NO
NO
Valid Values.-
Masterfile
.Record Type
Masterfile
Position
Masterfile
Length
30
23-29
7
fidit firror Messages:
*** = Fatal Error
* = Marning Error
Coding Considerations:
Typical usages of this field include identifiers for (as of March, 1982):
Region III
Region IV
Region V
Region VII
Region IX
PSD Permit Numbers
County Names
PSD Application Number
catalogue
Air Program Status of Points in NSPS
Date reported as significant violator
General Industry
CDS DATA DICTIONARY
A.1-37
-------
REGIONAL DATA ELEMENT 10
Definition: REGIONAL DATA ELEMENT 10 - user supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
RD10
3
72-73
2
ALPHANUMERIC
NO
NO
Valid Values:
Masterfile
Record Type
Master file
Position
Masterfile
Length
30
30-31
2
Edit Error Messages:
_*** = fatal Error
_* = Warning Error
Coding Considerations:
Region IV
Region V
Region VIII
Region IX
State Inspection Year
Lead Enforcement Role - All States;
Lead Enforcement Role - Ohio
Opacity Readings
Assigned to project officer
CDS DATA DICTIONARY
A.1-38
-------
REGIONAL DATA ELEMENT 11
Definition: REGIONAL DATA ELEMENT 11 - user supplied.
.
Abbreviation
Card
Tye
Columns
Data Element
Length
Data
Type
RD11
74~75
ALPHANUMERIC
Valid Values:
Justified
Masterfile
Record Type_
Required on
New Entry
NO
Master file
Position
32-33
Nationally
Controlled
Masterfile
Length
Edit Error Messages-.
*** = Fatal Error
* = Warning Error
Coding Considerations:
Region IV
Region V
Region VIII
B-Selected CLASS B Sources in Nonattainment areas
Lead Enforcement
P=Primary Source
CDS DATA DICTIONARY
A.1-39
-------
REGIONAL DATA ELEMENT 12
Definition: REGIONAL DATA ELEMENT 12 - user supplied.
Ketrieval ^
Abbreviation
Valid Values:
Card
Tupe
Card
_ , 76
Columns
Cata Element
Length
Data
ALPHANUMERIC
Type
Justified
Required on
NO
New Entry
Nationally
NO
Controlled
Edit Error Messages-.
*** = 'fatal Error
Master file
Record Tupe
Masterfile
Position
Masterfile
Length
* = Warning Error
Coding Considerations:
Reqion V uses this field to indicate Major Source Enforcement Effort
case delegation.
Region II
Region IV
Region V
Reqion VI
Reqion IX
V=«VOC Sources
V=VOC Sources
Indicator of Major SCC
NSPS & PSD=M for Continuous Mcnitorinq
Actual/Potential Tons/Yr.
CDS DATA DICTIONARY
A.1-40
-------
Definition:
SIC CODE
SIC is the Standard Industrial Class Code. It refers to the
primary product produced or service performed by the facility.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Tupe
Justified
Required on
New Entry
Nationally
Controlled
SICC
2
59-62
4
NUMERIC
LEFT
YES
YES
Valid Values:
All numerics.
Masterfile
Record Tupe
Masterfile
Position
Masterfile
Length
20
109-112
4
Sdit Error Messages:
*SIC SHOULD BE NUMERIC
*** = Fatal Error
* = Warning Error
Coding Considerations:
Since many retrievals are based on industry categories, it is important tc
code this field on a new card code 2. If a secondary SIC code is needed,
Regional Data Element 4 may be used. SIC codes may be obtained from
manufacturing directories or the most recent SIC directory published by:
Government Printing Office
Superintendent of Documents
Washington, DC 20402
Stock Number 4101-0066
CDS DATA DICTIONARY
A.1-41
-------
SIC DESCRIPTION
Definition: The SIC DESCRIPTION is a 30 character definition of each valid
SIC Code. It can be printed on a Quick Look or a Milestone for
each source with a valid SIC Code.
Retrieval c Valld Values'
.. . . SICD
Abbreviation
Card
Type
Card
Columns
Data Element
jLength 30
Data
ALPHABETIC
jrupe
Masterfile
Justified _ Record Type
Required on Masterfile
Sntru Position
Nationally Masterfile
YES
Controlled Length
Edit Error Messages-.
_*** = Fatal grror _ * = Warning Error _ .
Coding Considerations:
If no Process Description is coded on a new Emission Point 000 record and
if the source has a valid SIC Code, the Update Program will place the SIC
Description in the Process Description field on the Point 000.
CDS DATA DICTIONARY
A.1-42
-------
SOURCE CLASSIFICATION CODE
Definition: SOURCE CLASSIFICATION CODE - designation used for program
planning purposes. Categorizes sources according to the Alabama
Power decision's definition
Retrieval
Abbreviation
Card
Type
^ 77-78
Columns
Data Element
Length
Data
ALPHANUMERIC
Tu se
LEFT
Justified
Reauired on
YES
;Vev En Cry
nationally
Controlled
Edit Error Messages:
INVALID SOURCE CLASSIFICATION CODE
_*** = Fatal Error
of major source.
Valid Values:
Al - Class Al
A2 =» Class A2
UK = Unknown
B =» Class B
Masterfile
30
Record Type
Master/lie
Position
Masterfile
Length
* = Warning Error
Coding Considerations:
Class A retrieval will include Class Al plus Class A2.
Class A = Class Al + A2
Class Al = Actual or potential controlled emissions 100 t/yr as per
Alabama Power
Class A2 = Actual emissions 100 t/yr, but potential uncontrolled
emissions 100 t/yr
Class B = Potential uncontrolled emissions 100 t/yr
Class UK » Unknown
Class = Blank
All operating sources must be classified according to these categories.
CDS DATA DICTIONARY
A.1-43
-------
SOURCE CLASSIFICATION GROUP
Definition: SOURCE CLASSIFICATION - designation used for program planning
purposes. Consists of first position of Source Classification
Code.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
7-jr>e
Justified
Required on
.Ve'v 2V; try
A' a cionally
Controlled
CLAG
3
77
1
ALPHANUMERIC
YES
YES
Valid Values:
A * Class A
B = class B
U » Unknown
See CLAS for input.
Masterfile
Record Tuoe
Master £ He
Position
Hasterfile
Length
30
50
1
Edit Error Messages-,
* INVALID SOURCE CLASSIFICATION CODE
*** = Fatal Error
* = Warning Error
Considerations:
See Source lassification Code under Coding Considerations.
CDS DATA DICTIONARY
A.1-44
-------
SOURCE COMPLIANCE STATUS
Definition: SOURCE COMPLIANCE STATUS gives the Regional Offices an
indication of whether a source is in compliance, not in
compliance, or whether its compliance status is unknown with
regard to emission regulations.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
Valid Values:
sens
0 through 9
5 (Point '000' only)
30
1
NUMERIC
Master file
Record Type
Masterfile
Position
Masterfile
X£>:s Length
30
21
1
Edit Error Messages-.
***INVALID COMPLIANCE STATUS
*** = Fatal Error
* = Warning Error
Coding Considerations:
See Source Compliance Status Description.
SCMS is generated from the Point 000 CMST.
CMST on card 5 for Point 000.
SCMS is changed by changing
The Source Compliance Status should reflect the worst case emission
compliance of any process within the source. The Compliance Status (CIST)
on all other points should reflect the worst case compliance of that
particular point.
Order of worst case to best case source level compliance:
SCMS- 1-6-0-7-5-4-3-2-8-9. -:"-..
CDS DATA DICTIONARY
A.1-45
-------
SOURCE COMPLIANCE STATUS DESCRIPTION
Definition: SOURCE COMPLIANCE STATUS DESCRIPTION is an English language
description of Compliance Status (SCMS). It is a computer
generated field which is determined by SCMS. The description is
controlled by the National DBC. It is not present on any
Masterfile record. A change to SCMS will result in a change to
the description.
_ _ ."Valid Values:
Retrieval srsn
Abbreviation See below.
Card
Card
Columns
Data Element
20
Length
Data
ALPHANUMERIC
Type
Masterfile
-r . f i * ^ , _
^ us t if led _ Record Type
Required on Masterfile
_New Entry _ Position
Nationally ' «asterfiie-
^Controlled _ Length
Edit Error Messages-.
_*** = Fatal Error _ * = Warning Error _
Coding Considerations:
SCMS Value SCMS Description
0 UNKNOWN COMPLI STATUS
1 IN VIOL-NO SCHEDULE
2 IN COMPL-SOURCE TEST
3 IN COMPL-INSPECTION
4 IN COMP-CERTIFICATN
5 MEETING COMPL SCHEDULE
6 IN VIOL-NOT MEETING SCHED
7 IN VIOL-UNK WRT SCHED
8 NO APPLIC EMISSION REG
9 IN COMPL-SHUT DOWN
NOTE: If SCMS is not any of the above values, "Unknown Compliance Status"
will appear as the description.
CDS DATA DICTIONARY
A. 1-46
-------
SOURCE COMPLIANCE STATUS - 8 QTRS
Definition: SOURCE COMPLIANCE STATUS represents a historic record of
previous quarterly emission compliance status for the past eight
quarters. It is generated on a quarterly basis by the Update
Program based on information found in the SCMS field.
Retrieval
Abbreviation
Card
Tupe_
Card
Columns
Data Element
Length
Data
Tuoe
Valid Values:
SCSO, SCS1-SCS8
N/A
N/A
ALPHANUMERIC
Justified
Masterfile
Record Type
30
Required on
New Entry
Masterfile
Position
35-42
Nationally
Controlled
YES
Masterfile
Length
Edit Error Messages-.
_*** = Fatal Error_
Warning Error
- ens JL sera c.:ons :
Users cannot input this value. The entire field is also subdivided into
the following eight retrievable data elements:
Source Compliance Status
1st Quarter (most recent)
2nd
3rd
4th
5th
6th
7th
3th
Retrieval Abbreviation
SCSI
SCS2
SCS3
SCS4
SCS5
SCS6
SCS7
SCS8
On October 1976, the Compliance Status found on each emission point record
was placed in SCSI. During each subsequent quarter, the current compliance
status is stored in SCSI, and all previous quarterly compliance status
codes are moved into the next higher SCS field. After eight quarters, the
oldest compliance status will be dropped to make room for the next
quarterly historic compliance status. With these eight historic compliance
status fields, users can compare current compliance status with previous
compliance status.
CVS DATA DICTIONARY
A.1-47
-------
MONTHLY HISTORIC COMPLIANCE
Definition: MONTHLY HISTORIC COMPLIANCE represents an historic record of
previous monthly compliance statuses for a two-year period. It
is generated on a monthly basis in the update program using
information from the SCMS field.
MHOO - MH24
Card
N/A
- , N/A
Columns
Data Element
Length
Data
ALPHANUMERIC
Tnoe
-r ^-f-^ N/A
Justified
Required on
r- N/A
.Vew Entry
Nationally
N/A
Controlled '
Sdit Error Messages-.
*** = Fatal Error
Valid Values:
Compliance Codes
Waster file
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error
20
188-211
24
Z.z-iLna Considerations:
Users cannot input data to this field. It is divided into 24 retrievable
data elements: MH01 - MH24. The data element MHOO is used to retrieve the
entire field.
CDS DATA DICTIONARY
A.1-48
-------
SOURCE EMISSION CATEGORY
Definition: SOURCE EMISSION CATEGORY provides the Regional Offices with a
method of ranking or grouping sources by broad emission level
categories.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
_Tuj>e
Justified
Required on
New Entry
Nationally
Controlled
Valid Values:
SECT
0 « Unknown
* ,~ , ^ , , , 1 * Less tnan 100 TPY potential
5 (Point '000' only) . , , ,
uncontrolled
2 - 100-1000 TPY potential
uncontrolled
3 =» over 1000 TPY potential
uncontrolled
NUMERIC 4 - less than 25 TPY potential
uncontrolled
Masterfile
Record Type
YES Masterfile 22
Position
- Masterfile
YES Length ' 1
Edit Error Messages:
INVALID EMISSION CATEGORY
_*** = Fatal Error
Warning Error
Ceding Considerations:
The Source Emission Category must reflect the potential uncontrolled
emission of the "worst case" pollutant from the entire source.
SECT is generated from Point 000 ECAT. SECT is changed by changing SECT on
card 5 for Point 000.
CDS DATA DICTIONARY
A.1-49
-------
SOURCE EMISSION CATEGORY DESCRIPTION
Definition: SOURCE EMISSION CATEGORY DESCRIPTION is the English language
description associated with Emission Category (SECT). It is
generated by the computer based on the value of SECT. The
description is controlled by the National DBC. It does not
reside on the masterfile. SECD will automatically change when
SECT is updated.
Valid Values:
Retrieval
. , , ^ .
Abbreviation
Card
Card
Columns
Data Element
Length
ALPHANUMERIC
Type
Justified
Required on
New Entry
Nationally
Controlled
LEFT
NO
YES
Wasterfile
Record Tupe
Masterfile
Position
Masterfile
Length
Edit Error Messages;
_*** = Fatal Error * = Warning Error
Coding Considerations:
SECT Value SECT Description
0 Unknown
1 Less than 100 TPY
2 100 to 1000 TPY
3 Over 1000 TPY
4 Less than 25 TPY
NOTE: If SECT is not one of the above values, "Unknown" will appear as the
description.
CDS DATA DICTIONARY
A.1-50
-------
SIGNIFICANT VIOLATOR FLAG
Definition: SIGNIFICANT VIOLATOR FLAG - This indicates major sources that
are considered "significant violators" and it identifies the
lead enforcement agency. SVI1 is the position which carries
information concerning the initial time a source qualifies as a
Significant Violator. If the violator comes into compliance and
subsequently becomes a repeat violator, the current original
status in SVI1 is moved to SVI2 and the new violation is
recorded in SVI1. SVI1 always shows the status of the current
violation. SVI2, SVI3 and SVI4 contain the last recorded status
for each of the three most previous separate incidents of
violation.
The 4 characters of SVIL are made up of SVI1, SVI2, SVI3 and
SVI4 left to right.
Retrieval
Abbreviation
Card
Tijpe
Card
Columns
Data Element
Length
Data
Type
^r~ ~~ ~ ~ ~ .°Ci
Required on
New Entry
Nationally
Controlled
SVIL SVI1-SVI4
N/A
N/A
4
ALPHANUMERIC
N/A
NO
YES
Valid Values:
E, F, G
S, T, U
B, C, D
Masterfile
Record Tn oe
Masterfile
65-68
Position
Masterr"i2e
Length
Edit Error Messages:
*** = Fatal Error
* - Warning Error
E « EPA has Lead Enforcement
S = State has Lead Enforcement
B = EPA/STATE shared enforcement
X « Lead Enforcement not determined
CDS DATA DICTIONARY
A.1-51
-------
SIGNIFICANT VIOLATOR FLAG
(Continued)
Comments (Continued):
C Source w/SVIL-B that changed compliance status code from 1 or 6 to 5,
7, oc 0.
D > Source w/SVIL*B that changed compliance status from 1 or 6 to 2, 3, 4,
8 or 9.
F » Source w/SVIL-E that changed compliance status code from 1 or 6 to 5,
7, or 0.
G = Source w/SVIL*E that changed compliance status code from 1 or 6 to 2,
3, 4, 8 or 9.
T = Source w/SVIL»S that changed compliance status code from 1 or 6 to 5,
7, or 0.
U = Source w/SVIL«S that changed compliance status code from 1 or 6 to 2,
3, 4, 8 or 9.
CDS DATA DICTIONARY
A.1-52
-------
SOURCE NAME
Definition: SOURCE NAME is a 20 position alphanumeric facility identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
_Type
Justified
Required on
New Entry
Nationally
Controlled
SNME
1
27-46
20
ALPHANUMERIC
LEFT
YES
NO
Valid Values:
All alphanumeric characters.
Masterfile
Record Tupe
Masterfile
28-47
Position
Masterfile
Length
Edit Error Messages-.
***SOURCE NAME REQUIRED ON NEW ENTRY
_*** = Fatal Error * = Warning Error
Coding Considerations:
The first position of facility name must be filled on a new transactic.r. ; :
allow for source name sorting on the retrieval. Use consistent
abbreviations for facilities with the same company name, i.e.,
US Steel - Pittsburgh
US Steel - Dayton
US Steel - Mansfield
Abbreviate only when necessary and do not use words like "the" or "city of
as the first word in a facility name. If the name of the facility is
different from that of the parent company, enter the name of the facility
as the source name and enter the name of the parent company as a source
comment (card code 4). Most complete source names, addresses, and S ;c
Codes can be found in manufacturing directories published by state commerce
departments. It would be wise for each region to develop a list of
standard facility name abbreviations to be used consistently throughout the
region. See attached example developed by Region V.
CDS DATA DICTIONARY
A.1-53
-------
REGION V CODING CONVENTION FOR MICHIGAN
Full Name
Asphalt
Aluminum
Authority
Air Force Base
Board of Public Light
& Power Detroit
Center
Commission
Cannon
Commonwealth Edison
Concrete
Cement
Consumers Power
Chemical
County
Abbreviation*
Asph
Al
Auth
AFB
Detroit BD Publ L&P
Ctr
Co mm
Can
Com Ed
Con
Cera
(Do not abbreviate)
Chera (Abbreviate only if necessary)
Co
Chigago & Northwestern Railroad Chicago & NW RR
Construction
Company or Inc. at end of name
Central Illinois Light Company
City of Detroit
Central Wayne
Department
Const
(Eliminate, do not use)
CILCO
Detroit City (use name first followed .by
city, if public or municipal
company)
Wayne C
Dept
No punctuation unless specified on sheet.
CDS DATA DICTIONARY
A.1-54
-------
REGION V CODING CONVENTION FOR MICHIGAN
Full Name
Detroit Edison
River Rouge Plant
Division
Equipment
Ford Motor Company
Assembly Div.
Foundry (i.e. General Foundry)
General Motors Corporation
Fisher Body
Generating
Goodyear Tire & Rubber
Great Lakes SteelZUG Island
Groveland Mine Hanna
Grand Rapids
Hospital
Incinerator
Industries
International
Jones & Laughlin Steel
Light & Power
Lumbar
Malleable
Abbreviation*
Under name; Detroit Edison
Under address put plant name;
River Rouge Plant
Div
Equip
Under name; Ford Motor
Under address put plant name; Assembly Div
(Spell out, do not abbreviate)
Under name; CMC
Under street address put plant name:
Fisher Body
Genr
Goodyear Tire&Rubber (No blanks between "&")
Under name: Great Lakes Steel
Under street address put plant name;
Zug Island
Under name; Hanna Mining
Under street address put plant name;
Groveland Mine
GD Rapids
Hosp
Incin
Indst
Intnl
Jones & Laughlin (Spell out, omit Steel)
La?
Lmbr
Malleb
* No punctuation unless specified on sheet.
CHS DATA DICTIONARY
A.1-55
-------
REGION V CODING CONVENTION FOR MICHIGAN
Full Name
Manufacturing
Michigan
Motor
North East(ern)
North West(ern)
Northern Michigan Electrical
Co-op
Operation
Packaging Corporation of
America
Paving
Plant
Power
Project.
P redacts
Public
Railroad
Refractories
Refining
Sanitation
Sewage Treatment Plant
Abbreviation*
Mfg
Mich
Mtr
NE
NW
Northern Mich Elec
Op
Packaging Corp AM
Pav
Pit
Pwr
Prj
Prod
Publ
RR
Ref
Refin
Sani
Stp
(Wastewater)
State-Street
Station
Southside Foundry
St
Sta
(Spell out, do not abbreviate)
* No punctuation unless specified on sheet.
CDS DATA DICTIONARY
. A.1-56
-------
Full Name
Southeast(ern)
Southwest(ern)
Terminal
Training
Transportation
Township
United Statas Steel
University
Warehouse
Water 4 Power
Water Treatment Plant
Wholesale
REGION V CODING CONVENTION FOR MICHIGAN
Abbreviation*
SE
SW
Term
Trn
Transp
Twp
US Steel (No spaces)
Univ
Whse
W&P
WTP
Whol
* No punctuation unless specified on sheet.
CDS DATA DICTIONARY
A.1-57
-------
SOURCE NAME (SHORT)
Definition: SOURCE NAME (SHORT) is the first 10 positions of SOURCE NAME -
SNME, for Retrieval sorting and printing purposes only.
Retrieval
SNMS
Abbreviation
Valid Values:
Card
N/A
Type
Card
Columns
Data Element
r _-uu 10
j-nzjjy i_U
Data
_ ALPHANUMERIC
Type
Justified
Required on
N/A
New Sntry
Nationally
, , j N/A
controlled
£dit Error Messages-.
*** = Fatal Error
Hasterfile
Record Type
Masterfile
_ . . .
-------
SOURCE NUMBER
Definition: SOURCE NUMBER is a five digit numeric facility identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Lencth
Oat a
Tu ce
'us- if led
Required on
!!<=./ Entry
Va tionally
Controlled
SRCE
1-8
9-13
5
NUMERIC
LEFT
YES
NO
Valid Values:
All numeric values.
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
20-47
9-13
5
S-Jit Error Messages-.
»*'SOURCE NUMBER MUST BE NUMERIC
_*** ~ Fatal Error * = Harning Error
Coding Considerations:
The NEDS source numbering convention may be used when addinq a new source.
jc.-.iirwi3e, assign the next highest sequential source number wic:iin '..^'^
county. Usually, the last four digits of Source Number are the same as the
NEDS Source Identifier. The first digit must correspond to the Air Program
Code. Sources subject to several Air Program Codes must be entered with
separate source numbers, one for each program such as SIP, NSPS, etc.
CDS DATA DICTIONARY
A.1-59
-------
Definition:
STAFF NAME (SOURCE)
STAFF NAME (SOURCE) is a fifteen position name generated from
the Staff Code found on Card 2, positions 77-79.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
STFS
ALPHANUMERIC
*** = Fata2 Error
Valid Values:
All names are on the Personnel Table
maintained by the national DBC.
Please call the DBC to make additions
or changes to this table.
Justified
Required on
New Entry
Nationally
YES
Controlled
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
20
118-133
15
Edit Error Messages-.
* = Warning Error
Coding Considerations:
During each update cycle, the Staff Name is generated based on tne source:s
Staff Code. By changing the staff name associated with a staff code on the
Personnel Table, all input transactions and masterfile records will carry
the new staff name.
CDS DATA DICTIONARY
A.1-60
-------
STAFF PERSONNEL CODE - SOURCE
Definition: STAFF PERSONNEL CODE is a three position code representing the
person or group assigned to monitor the facility. It consists
of one alpha character followed by 2 numeric characters.
Retrieval
Abbreviation
Card
Type
Columns
Valid Values:
Must exist on the Personnel Table
maintained by the National DEC.
Please call the DEC to add, change,
Data Element
Lenath
Data
ALPHANUMERIC
Tyoe
.c. , LEFT
Justified
Required on
, NO
iVew entry
Nationally
Controlled
Masterfile
20
Record Type
Masterfile
Position
Masterfile
Lenqth
Edit Error Messages'.
'INVALID STAFF CODE
*** = Fatal Error
* = Warning Error
".-di~7 Considerations :
The assigned person's name is generated by the Update Program based on the
name found on the Personnel Table.
CDS DATA DICTIONARY
A.1-61
-------
PRIORITY CODS
Definition: PRIORITY CODE is a field reserved for Headquarters only.
Priority Code is used to identify facilities falling into
numerous priority categories.
Retrieval
Abbreviation
Card
Type
Card
Columns
B»t,1 F.lomdlf-
1
Data
ALPHANUMERIC
Justified
Required on
-, NO
.Vew Sntru
tV -U C Z C /"* c^ .Z 2 LJ
"" V^»*^
Controlled "
Valid Values:
Master file
Record Tijpe
Masterfile
Position
Masterfile
Length
20
113
1
Edit Error Messages-.
_»** = Fatal Error
Warning Error
CodJ.ng Considerations :
The Edit will reject all input values to this field from Regional or Scata
personnel. Headquarters uses this field as follows:
Value Description
M Municipal Incinerator
N Nuclear Power Plants
R Refinery
I Iron and Steel, nonpriority
P Iron and Steel, priority
S Smelter
C Coal Fired Power Plant
O Oil Fired Power Plant
U Undetermined Fuel Fired
Power Plants
Value Description
X Coal & Oil Fired Power ?!:.;.:£
Y. Coal & Gas Fired Power Plant
2 Oil & Gas Fired Power Fiar.c
G Gas Fired Power Plant
D Diesel-Fired Internal
Combustion Power Plaint
T Gas Turbine Power Plant
A All Fossil Fuel Fired Power
Plants, i.e., C, 0, 4 G
CDS DATA DICTIONARY
A.1-62
-------
STATE
Definition: STATE is a two-position numeric state code. The State codes ace
derived from the Storage and Retrieval of Aerometric Data Manual
(SAROAD) published by OAQPS.
Retrieval
Abbreviation
Card
Type
Card
Co 1 umn s
Data Element
L-ensth
Data
T:;oe
Justified
Required on
.Vev Sncry
Nationally
Controlled
STTE
1-8
3-4
2
NUMERIC
LEFT
YES
YES
Valid Values:
01-56
See attached showing the states
associated with each state code.
Hasterfile ^
Record Tape
Hasterfile
3-4
Position
Masterfile
Lenqth
Edit Error Messages-.
***INVALID STATE CODE
***STATE NOT IN REGION
*** = Fatal Error
* =
Warning Error
Ceding Considerations:
State code must be present on all transactions. State must be valid for
the region. State cannot be changed or blanked out on the data base. If
it must be changed, the entire source must be deleted and re-entered with.
the correct state code.
CDS DATA DICTIONARY
A.1-63
-------
STATE CODE
The CDS System use the following two digit SAROAD state codes:
01
02
03
04
05
06
07
08
09
10
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
23
29
30
Alabama
Alaska
Arizona
Arkansas
California
Colorado
Connecticut
Delaware
District of Columbia
Florida
Hawaii
Idaho
Illinois
Indiana
Iowa
Kansas
Kentucky
Louisiana
Maine
Maryland
Massachusetts
Michigan
Minnesota
Mississippi
Missouri
Montana
Nebraska
Nevada
New Hampshire
31 New Jersey
32 New Mexico
33 New York
34 North Carolina
35 North Dakota
36 Ohio
37 Oklahoma
38 Oregon
39 Pennsylvania
40 Puerto Rico
41 Rhode island
42 South Carolina
43 South Dakota
44 Tennessee
45 Texas
46 Utah
47 Vermont
48 Virginia
49 Washington
50 West Virginia
51 Wisconsin
5 2 Wyoming
53 American Samoa
54 Guam
55 Virgin Islands
56 Trust Territories
CDS DATA DICTIONARY
A.1-64
-------
Definition:
STATE ABBREVIATION
STATE ABBREVIATION is a two position alphabetic state code used
by the U.S. Post Office. It is generated
CDS.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Tupe
Justified
Required on
Wew Entry
iV-a tionally
Controlled
'Edit Error Messages
*** = Fatal Error
for
each facility by
It is useful for retrieval processing.
STAB
N/A
N/A
2
ALPHANUMERIC
N/A
:
Valid Values:
Masterfile
Record Tyoe
Masterfile
Position
Masterfile
Length
20
83-84
2
* = Warning Error
Cc -finer Considerations:
AL - Alabama
AK - Alaska
AZ - Arizona
AR - Arkansas
CA - California
CO - Colorado
CT - Connecticut
DS - Delaware
DC - District of
Columbia
?L - Florida
GA - Georgia
HI - Hawaii
ID - Idaho
IL - Illinois
IN - Indiana
IA - Iowa
KS - Kansas
KY - Kentucky
LA
ME
MD
MA
MI
MN
MS
MO
MT
NE
NV
NH
NJ
NM
NY
NC
ND
OH
OK
- Louisiana
- Maine
- Maryland
- Massachusetts
- Michigan
- Minnesota
- Mississippi
- Missouri
- Montana
- Nebraska
- Nevada
- New Hampshire
- New Jersey
- New Mexico
- New York
- North Carolina
- North Dakota
- Ohio
- Oklahoma
OR
PA
PR
RI
SC
SD
TN
TX
UT
VT
VA
WA
WV
WI
WY
AS
GU
VI
TT
- Oregon
- Pennsylvania
- Puerto Rico
- Rhode Island
- South Carolina
- South Dakota
- Tennessee
- Texas
- Utah
- Vermont
- Virginia
- Washington
- West Virginia
- Wisconsin
- Wyoming
- American Samoa
- Guam
- Virgin Islands
- Trust
Territories
CDS DATA DICTIONARY
A.1-65
-------
Definition:
STATE COUNTY SOURCE
STATE COUNTY SOURCE combines those three data elements for
selection purposes only.
Retrieval
... . . .
Abbreviation
Columns
S 1 v,S
3-13
J "
Valid Values:
This combines the 3 data elements of
STATE (STTE) & COUNTY (CNTY) & SOURCE
NUMBER (SRCE) into a single data element
in the form of AABBBBCCCCC.
AA - 2 digit state code
BBBB =* 4 digit county code
Data Element 1 ,
Lenath
Data
NUMERIC
Tune
Justified
Required on
New Entry
Nationally
Controlled
CCCCC - 5 digit
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
source number
20, 30, 34, 46
3-13
11
Edit Error Messages-.
*** = Fatal Error
* = Warning Error
Coding Considerations:
If a retrieval was requested for 2 specific sources:
STATE COUNTY SOURCE
14
23
1540
2720
02103
00167
Without STCS the Selection Cards would be:
10 STTE A 14
10 STTE A 23
10 CNTY A 1540
10 CNTY A 2720
10 SRCE A 02103
10 SRCE A 00167
With STCS the Selection Card would be:
10 STCS A 14154002103
10 STCS A 23272000167
CDS DATA DICTIONARY
A.1-66
-------
SOURCE NUMBER (last 4 digits]
Definition: Last 4 dibits of Source Number.
selection purposes only.
This data element is for
Retrieval
Abbreviation
Valid Values:
SRC 4
The last 4 digits of the Source Number.
Exclude the first digit (Air Program Code)
N/A of the Source number.
Co 2 Limn s
Data Element
Data
Justified
Required on
.Vew Entry
Nationally
Controlled
4
NUMERIC
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages
*** = Fatal Error
* = Warning Error
This will help retrievals by retrieving the portion of the source number
not connected with the Air Program Code. Use the last 4 numbers of the
Source.
Selection (10 Card) Examples:
10 SRC4 A 0613
10 SRC4 A 0021
CDS DATA DICTIONARY
A.1-67
-------
STATE COUNTY SOURCE
(Last 4 digits of Source Number)
Definition: STATE COUNTY SOURCE (last 4 numbers of Source) combines STTE,
CNTY, SRC4 for selection purposes only.
Retrieval
Abbreviation
Card
N/A
Type
Card
Columns
Data Element
Length
Data
Type NUMERIC
Justified
Required on
New Entry
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
Valid Values:
Combine STTE, CNTY and the last 4
digits of the Source
the first digit (Air
Waster.fi .Ze
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error
Number. Exclude
Program Code)
Conrnencs :
This will help retrievals by retrieving the portion of the source number
not connected with the Air Program Code. Use the last 4 numbers of the
Source.
Selection (10 Card) Examples:
10 SCR4 A 3306000613
10 SCR4 A 3107080021
CDS DATA DICTIONARY
A.1-68
-------
Definition:
STATE REGISTRATION NUMBER
STATE REGISTRATION NUMBER is an alphanumeric identifier used by
the state to identify a facility.
.Retrieval
STRG
Abbreviation
Valid Values.-
All alphanumeric characters.
Card
Tupe
ar 40-54
Columns
Data Element
Length
Data
ALPHANUMERIC
Tupe
LEFT
Justified
Required on
NO
New Entry
Na tionally
Controlled
Edit Error Messages-.
*** = Fatal Srror
Masterfile
Record Tupe
Masterfile
Position
Masterfile
Length
* = Warning Error
Coding Considerations:
When the state identifier is consistently entered into this field, CDS
reports can be sorted in the same way as the state's files are sorted.
CDS DATA DICTIONARY
A.1-69
-------
STREET ADDRESS
Definition: STREET ADDRESS is the actual location of the facility;
the headquarters address.
it is NOT
Retrieval
Abbreviation
STRT
Valid Values:
All alphanumeric characters.
Card
Type
Card
_ ,
Columns
47-66
Data Element
Data
Tuoe ALPHANUMERIC
._. , LEFT
Justified
Required on
, NO
New Entry
Nationally
, , ~, N0
Controlled
Edit Error Messages:
_*** = fatal Error
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error
20
48-67
20
Coding Considerations:
If the mailing address of the facility is different from the streec
address, the mailing address can be coded on a source comment record
(Card 4) , Comment Line A and B. There are special input coding sheets
designed for mailing address information.
CDS DATA DICTIONARY
A.1-70
-------
ZIP CODE
Definition: ZIP CODE is the five digit numeric postal zone of the actual
location of the facility.
Retrieval
Abbreviation
Card
rVJ°e
Card
Columns
Data Element
Length
Data
Tupe
Justified
Required on
New Entry
Nationally
Controlled
ZIPC
2
35-39
5
NUMERIC
LEFT
NO
NO
Valid Values:
All numeric values.
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
20
85-89
5
Edit Error Messages:
*2IP CODE SHOULD BE NUMERIC
*** = Fatal Error
* = Warning Error
Coding Considerations:
Code whenever possible for complete address capability in the system.
Consult a state published manufacturer's directory for accurate name and
address information.
CDS DATA DICTIONARY
A.1-71
-------
A.2 POINT LEVEL DATA ELEMENTS
-------
CAPACITY CODE
Definition: CAPACITY CODE is used for coal-fired boilers other than
electrical utilities and identifies the boiler heat input
capacity in tens of MMBTUH. A boiler with a heat input capacity
of 150 million BTU per hour would have "15" in Capacity Code.
Retrieval
Abbreviation
Card
Type
Card
Columns
Dae a 3 lament
Lenath
Daca
Tuoe
Justified
Required on
:Vst/ Entry
Ma tionallg
Controlled
CAPC
5
28-29
2
NUMERIC
LEFT
NO
YES
Valid Values:
00-99
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
34
29-30
2
Edit Error Messages-.
*** = Fatal Srror
* = Warning Error
Ceding Considerations:
This is required for coal-fired boilers for all industries other than power
plants provided that the boiler has a heat input capacity equal to or
greater than 100 MMBTUH.
Users should note that this field was once used for tracking the NEDS Point
Cross-Reference (NEXP).
This field is a confidential data element. Users must supply the
appropriate password on the Retrieval Card 20 to obtain a printout of this
field.
CDS DATA DICTIONARY
A.2-1
-------
COMPLIANCE STATUS
Definition: COMPLIANCE STATUS gives the Regional Office an indication of
whether a source is in compliance, not in compliance, or its
compliance status is unknown, with regard to emission
regulations at the point level.
Retrieval
Abbreviation
Card
Type
Card
Cn 1 iimns
Data Element
Length
Oaca
Type
Justified
Required on
.Vew Entry
Nationally
Controlled
CMST
5
30
1
NUMERIC
YES
YES
Valid Values:
0 through 9
Master file
34
Record Tupe
Masterfile
Position
Masterfile
Length
Edit Error Messages:
***INVALID COMPLIANCE STATUS
*** = Fatal Error
* = Warning Error
Coding Considerations:
Must be coded on the point 000; may be coded on the other emission points.
Compliance Status Code;
0 Unknown
1 In violation - no schedule
2 In compliance by source test
3 In compliance by inspection
4 In compliance by certification
5 Meeting Compliance Schedule
$ In violation, not meeting schedule
7 In violation, unknown with respect to scnedule
8 No applicable emission regulation
9 In compliance - closed down
The Compliance Status on Point 000 (entire source) should reflect the worst
case emission compliance of any process within the source. The Compliance
Status on all other points should reflect the compliance of that particular
point.
CDS .DATA DICTIONARY
A.2-2
-------
COMPLIANCE STATUS
(Continued)
Coding Considerations (Continued):
At the 000 point, this is the same as SCMS.
At a minimum, all significant violators (SCMS»1»5,6,7) must have compliance
status maintained at the point level.
Order of worst case to best base point level compliance:
CMST - 1-6-0-7-5-4-3-2-8-9.
CDS DATA DICTIONARY
A.2-3
-------
COMPLIANCE STATUS DESCRIPTION
Definition: COMPLIANCE STATUS DESCRIPTION is an English language description
of Compliance Status (CMST). It is a computer generated field
which is determined by- CMST. The description is controlled by
the National DBC. It is not present on any master file record.
A change to CMST will result in a change to description.
Retrieval
Abbreviation
CMOS
Valid Values:
See below.
Card
Card
Columns
Data Element
Lenath
20
Data
Tyoe
ALPHANUMERIC
Justified
LEFT
Masterfile
Record Type
Required on
Entry
NO
Masterfile
Position
Nationally
Controlled
YES
Masterfile
Length
adit Error Messages-.
*** = Fatal Error
Error
Coding Considerations;
CMST Value
0
1
2
3
4
5
6
7
8
9
CMST Description
UNKNOWN COMPL STATUS
IN VIOL-NO SCHEDUL
IN COMPL-SOURCE TEST
IN COMPL-INSPECTION
IN COMPL-CERTIFICATN
MEETING COMPL SCHED
IN VIOL-NOT METG SCHED
IN VIOL-UNK WRT SCHE
NO APPLIC EMISSION REGULATION
IN COMPL-SHUT DOWN
NOTE: If CMST is not any of the above values "Compliance Status Unknown'
will appear as the description.
CDS DATA DICTIONARY
A.2-4
-------
DUN & BRADSTREET NUMBER
Definition: DUN & BRADSTREET NUMBER
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
Wew Entry
Nationally
Controlled
DBNO
9
12
ALPHANUMERIC
LEFT
NO
YES
Valid Values:
Hasterfile
Record Type
Master file
Position
Master file
Length
30
53-64
12
Edit Error Messages:'
*** = Fatal Error
* = Warning Error
Coding Considerations:
Card type 9 is currently restricted to SSCD Headquarters use only,
CDS DATA DICTIONARY
A.2-5
-------
EMISSION CATEGORY
Definition: EMISSION CATEGORY provides the Regional Offices with a method of
ranking or grouping sources at the point level by broad emission
categories.
Retrieval
Abbreviation ^x
Card
Type 5
Card
o , 49
Columns
Da. ca clement
Length
Data
NUMERIC
Type
Justified
Required on yES
.Vesv entry
Nationally
Controlled .
Edit Error Messages-.
INVALID EMISSION CATEGORY
_*** = Fatal Error
Valid Values:
0 « Unknown
1 « Less than 100
uncontrolled
2 - 100-1000 TPY
uncontrolled
TPY potential
potential
3 » Over 1000 TPY potential
uncontrolled
4 => Less than 25
uncontrolled
Waster file
Record Type
Masterfile
Position
Masterfile
Lentjth
* = Warning Error
TPY potential
34
50
1
C.:~:.r.g Considerations:
The Emission Category reflects the potential uncontrolled emission of the
pollutant identified by the point-level Pollutant Code (PLUT).
Should be coded on point 000; may be coded on the other emission points.
For Point 000, the Emission Category must reflect the potential
uncontrolled emission of the entire source.
At the 000 point, this is the same as SECT.
CDS DATA DICTIONARY
A.2-6
-------
EMISSION CATEGORY DESCRIPTION
Definition: EMISSION CATEGORY DESCRIPTION is the English language
description associated with Emission Category (ECAT). It is
generated by the computer based on the value of ECAT. The
description is controlled by the National DBC. It does not
reside on the masterfile. ECDS will automatically change when
ECAT is updated.
Valid Values:
Retrieval
... . .
Abbreviation
Card
Card
Columns
Data Element
20
Length
Data
ALPHANUMERIC
Tuoe
LEFT Masterfile
justified Record Type
Required on Masterfile
New Entry Position
Nationally . Masterfile
Controlled Length
Edit Error Messages-.
_*«* = Fatal Error * = Warning Error ;
Coding Considerations:
ECAT value ECAT Description
0 Unknown
1 Less than 100 TPY
2 100-1000 TPY
3 Over 1000 TPY
4 Less than 25 TPY
NOTE: if ECAT is not one of the above values, "Unknown" will appear as tne
description.
CDS DATA DICTIONARY
A.2-7
-------
EMISSION POINT NUMBER
Definition: EMISSION POINT NUMBER is a three digit numeric emission point
identifier. If one physical emission point produces several
pollutants, each pollutant is assigned a separate emission point
number. Emission point 000 refers to the entire source.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Tyoe
Justified
Required on
Wev Entry
Nationally
Controlled
PTNO
1-8
14-16
3
NUMERIC
LEFT
YES
NO
Valid Values:
000 through 999
Masterfile
_, m 20-47
Record Type
Masterfile , . , ,
14-16
Position
Masterfile
Length
Edit Error Messages-.
"EMISSION POINT MUST BE ZEROS
***POINT MUST BE GREATER THAN ZERO
***DO NOT DELETE POINT 000
*** = ratal Error
= Warnincr Srror
Coding Considerations:
When a card type 1 is entered as a new transaction, an emission point 000
is generated by the system; however, it is possible to enter an emission
point 000 as a new transaction at the same time a card type 1 is entered as
new.
Point number must be zero for card types 1, 2 and 4. It may be greater
than zero for cards 5, 6, 7, and 8. An emission point cannot be added to
the data base as new unless a card type 1 has been entered at the same time
or at a previous time.
Point 000 cannot be deleted unless the source itself is deleted with a card
type 1.
If possible, the first two positions of the CDS emission point should
correspond to the NEDS emission point; the third position can be pollutant
specific. For example, if a boiler has a NEDS point number of 02, the CDS
point number 020 could represent the particulate emissions and point 021
could represent the S02 emissions.
CDS DATA DICTIONARY
A.2-8
-------
MULTIPLE CROSS-REFERENCE
Definition: MULTIPLE CROSS-REFERENCE is used to tie together various
emission points. When one physical emission point has several
emission point numbers (one for each pollutant or regulation)
this field should be used to tie together the various point
numbers referring to one physical point.
Retrieval
Abbreviation
Card
Tiij>e
Card
Columns
Data Element
Lenath
Data
Tuoe
Justified
Required on
Wew Entry
Nationally
Controlled
MULT
5
75-77
3
NUMERIC
LEFT
NO
NO
Valid Values:
All numerics
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
34
76-78
3
Edit Srror Messages;
*MULTIPLE XREF SHOULD BE NUMERIC
>+ ' = ?~tsI error
Coding Considerations:
If emission points 010, Oil and 012 refer to three different pollutants
being emitted from one process or piece of equipment, points Oil and 012
should cross-reference 010.
CDS DATA DICTIONARY
A.2-9
-------
OLD COMPLIANCE STATUS
Definition: OLD COMPLIANCE STATUS represents a historic record of previous
quarterly emission compliance status for the past eight
quarters. It is generated on a quarterly basis by the Update
Program based on information found in the CMST field.
Retrieval
Abbreviation
Card
Card
Columns
Data Element
Length
Data
Tune
Valid Values:
OCSO, OCS1-OCS8
ALPHANUMERIC
Justified
Required on
i'/ew Entry
Nationally
VT!*Q
Control 1 ed
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
34
81-88
8
Edit Error Messages-.
*** = Fatal Error
* = Warning Error
Coding Considerations:
Users cannot input this value. The entire field is also subdivided into
the following eight retrievable data element:
Source Compliance Status
1st Quarter (most recent)
2nd
3rd
4th
5th
6th
7th
3th
Retrieval Abbreviation
OSC1
OSC2
OSC3
OSC4
OSC5
OSC6
OSC7
OSC8
On October 1976, the Compliance Status found on each emission point record
was placed on OCS1. During each subsequent quarter, the current compliance
status is stored on OCS1, and all previous quarterly compliance status are
moved into the next higher OCS field. After eight quarters, the oldest
compliance status will be dropped to make room for the next quarterly
historic compliance status. With these eight historic compliance status
fields, users can compare current compliance status with previous
compliance status.
CDS DATA DICTIONARY
A.2-10
-------
POLLUTANT CODE
Definition:
POLLUTANT CODE indicates the type of pollutant emitted by a
particular emission point.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
tie* Entry
Nationally
Controlled
PLUT
5
32-33
2
ALPHANUMERIC
LEFT
YES
YES
Valid Values:
See below for the table of valid
values.
Masterfile
Record Type
Masterfile 33_34
Position
Masterfile
Length
Edit Error Messages-.
*INVALID POLLUTANT CODE
*** = Fatal Error
* = Harning Error
Coding Considerations:
Should be input on all new emission points.
values:
Use of one of the ioL^c-.
Valid Values;
AB - Asbestos
AS - Arsenic
BE - Beryllium
32 - Benzene
CD - Cadmium
CE - Coke Oven Emissions
CO - Carbon Monoxide
FL - Fluorides
HC - Hydrocarbons (volatile
organic compounds)
HG - Mercury
N2 - NO2
OD - Odors
OT - Other
PB - Lead
PT - Particulate Matter (Total)
S2 - S02
TS - Total Reduced Sulfur
VC - Vinyl Chloride
VE - Visible Emission
ZN - Zinc
CDS DATA DICTIONARY
A.2-11
-------
PROCEDURAL COMPLIANCE
Definition: PROCEDURAL COMPLIANCE should be used for all NSR, PSD, NSFS,
NESHAP and SIP facilities, under construction or subject to
performance tests, continuous emission monitoring requirements,
and other procedural requirements under such air programs. This
field indicates the compliance status of a facility with respect
to all applicable procedural requirements. Use CMST, POMS and
SCMS to indicate the compliance of an operating facility subject
to immediately effective emission regulations.
Retrieval
Abbreviation
Data Element
Length
Data
CMS 2
Card
Type
Card
Columns
5
79
Valid Values.-
A, B, C, 8, V, I, N, Blank
ALPHANUMERIC
Justified
Required on
Nev-Entrg
Nationally
Controlled **^
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
34
80
1
Edit Error Messages-.
**» = fatal Error
Warning Error
Coding Considerations:
I
N
Value
Unknown compliance with procedural requirements
In violation of procedural requirements
In compliance with procedural requirements
No applicable regulation or procedural requirement
No applicable regulation or procedural requirement
In violation of federally enforceable compliance schedule;
future effective regulation
In compliance with federally enforceable compliance
schedule; future effective regulation
No federally enforceable compliance schedule but subject to
future effective regulation(s)
CDS DATA DICTIONARY
A.2-12
-------
PROCESS DESCRIPTION
Definition: PROCESS DESCRIPTION is a brief description of the physical
emission point such as a boiler or cupola. At the 000 Emission
Point level, this should be used to describe the type of plant
such as a generating station or a portland cement plant.
Retrieval
Abbreviation
PROS
Valid Values:
All alphanumeric characters.
Card
Type
Card
Columns
50-74
Data Element
Length
25
Data
ALPHANUMERIC
Justified
Required on
New Entry
Nationally
Controlled
LEFT
YES
NO
Masterfile
Record Type
Masterfile
Position
Masterfiie
Length
34
51-75
25
Edit Error Messages-.
*** = Fatal Error
* = Harning Error
Coding Considerations:
Abbreviations should be used consistently and clearly for sorting and
retrieval purposes, i.e., BLR-3 for Boiler #3. If several emission points
have similar process desciptions, be sure to identify each point with a
unique process description, such as a boiler number or a specific location
for the process. These descriptions must be clear enough so that an
inspector or other agency official can readily identify the apparatus at a
facility to which the CDS record applies.
If no value is entered for Point 000, and if the source has a valid SIC
Code, the SIC Code description is generated as the Process Description on
Point 000 when the source is first placed on the CDS Masterfile.
CDS DATA DICTIONARY
A.2-13
-------
REGIONAL DATA ELEMENT 7
Definition: REGIONAL DATA ELEMENT 7 - user supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
-------
REPEATING VIOLATOR FLAG
Definition: REPEATING VIOLATOR FLAG identifies the quarter in which an Al
SIP, NESHAP, or NSPS source is assigned the "In Violation'
source compliance or "I" or '6.' The initial quarter was 1/1/82
- 3/31/82.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Lenath
Data
T'JOe
Justified
Required on
Nev Entru
Nationally
Controlled
RPTV
N/A
N/A
2
NUMERIC
RIGHT
NO
YES
Valid Values:
01 - 99
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
34
94-95
2
Edit Error Messages-.
*** = REPEATING VIOLATOR MUST BE NUMERIC
*** = Fatal Error * = Warning Error
Coding Considerations:
The value of "1" will be assigned to any source that had a source
compliance of '!' or *6' during the quarter 1/1/82 - 3/31/82. The value of
"2* will be assigned to the sources changed to SCMS of '!' or "6" during
the quarter 4/1/82 - 6/30/82. This table shows the value of RPTV for
quarters from 1/1/82 - 12/31/84:
?.;-7V QT?. SCMS 1/6 RPTV QTR SCMS 1/6 RPTV QTR SCMS 1/6
I -- 1/1-3/31/52 - 5 = 1/1-3/31/83 9 = 1/1-3/31/84
2 = 4/1-6/30/82 6 = 4/1-6/30/83 10 = 4/1-6/30/84
3 = 7/1-9/30/82 7 = 7/1-9/30/83 11 = 7/1-9/30/84
4 = 10/1-12/31/32 8 = 10/1-12/31/83 12 = 10/1-12/31/34
CDS DATA DICTIONARY
A.2-15
-------
REPEAT VIOLATION DATE
Definition: REPEAT VIOLATION DATE is the date that an Al SIP, NESHAP, or
NSPS source completes the cycle of: 1) Out of Compliance, 2) In
Compliance, and 3} Out of Compliance. REOT is the date of the
most recently completed cycle. The form of the date is MMYY.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Slsnsent
Lenath
Data
Tuoe
Justified
Required on
New Entry
Ha tionally
Controlled
REDT
N/A
N/A
4
NUMERIC
N/A
NO
YES
Valid Values:
Month (MM) -
Year (YY) -
Masterr"i.Ze
Record Type
Masterfile
Position
Masterfile
Length
01 - 12
00 - 99
34
90-93
4
Edit Error Messages;
*** = REPEATING VIOLATION DT MUST BE NUMERIC
*** = fatal Error ' * = Warning Error.
Codir.o Considerations:
CDS DATA DICTIONARY
A.2-16
-------
SCC CODE
Definition: SCC CODE is the NEDS Source Classification Code which provides a
detailed analysis of the process creating the emission for this
point. The SCC code provides a very precise description of the
process. The code is particularly useful for identifying
processes which cross industrial category lines (SIC), e.g.,
boilers, sulfuric acid plants.
Retrieval
Abbreviation
Card
Type
Card
Coldmns
Data Element
uenqtr.
Da t a
Type
Justified
2eq£
the SCC Code; SCC6 retrieves on the first 6 positions of SCC Code; and SCC8
.':a::rieves on the entire SCC Code.
For some industries, SSCD has expanded on the values in the NEDS coding
manual; special guidance has been provided for these SCC codes.
SCC3 is at the present a confidential data element, users must supply the
proper password on the Retreieval Card 20 to obtain SCC8 on output
reports. SCC3 and SCC6 are not password protected on output reports.
CDS DATA DICTIONARY
A.2-17
-------
SIP CODS
Definition: SIP CODE provides the Regional Office with a method of
identifying the type of enforcement schedule which has been
negotiated with a source not presently meeting enforceable SIP
emission limits.
Retrieval
^Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Tupe
Justified
Required on
Hew Entr'J
iVa tionally
Controlled
SIPC
5
31
1
NUMERIC
NO
YES
Valid Values:
Blank, 0 through 9
Masterfile
Record Tupe
Masterfile
Position
Masterfile
Length
34
32
1
Edit Error Messages-.
INVALID SIP CODE
*** = Fatal Error
* = Warning Error
This field must be coded for all Class
Compliance Status of 0, 1, 5, 6 or 7.
A sources which have a Source
Blank
0
1
2
3
4
5
6
7
8
9
No schedule
Schedule Status Unknown
Federally Enforceable DCO
Federally Approved SIP Schedule (should have SCMS=4)
Federal Court Order Schedule
Federally Enforceable Consent Decree Schedule
Undergoing enforcement actions to develop a schedule
State/Local Compliance Schedule not Federally Enforceable
Non-Federally Enforceable schedule being developed
Reserved
Subject to offsets
CDS DATA DICTIONARY
' A.2-18
-------
SIP CODE DESCRIPTION
Definition: SIP CODE DESCRIPTION is the English language description of SIP
Code (SIPC). It is generated by the computer based on the value
of SIPC. This description is controlled by the National DEC.
It is not present on the masterfile. The description will
automatically change when SIPC is changed.
~~~ ! ' Valid Values:
Retrieval
Abbreviation
Card
Type
i-.arc
Columns
Data Element
20
ALPHANUMERIC
Just ified
Required on
.'/=« Sntry
Wa tionally
Controlled
LEFT
NO
YES
WasterfiJe
Record Type
Masterfile
Position
Masterfile
' Length
3d it Scror .Messages;
.*** = ?a~*L Error * = Warning Error
Coding Considerations:
This field must be coded for all major sources which have a Source
Compliance Status of 0, 1, 5, 6 or 7 (in violation or unknown).
No schedule
Schedule Status Unknown
Federal/State DCO
2 Federal SIP Schedule
3 Federal Court Order
4 Federal Consent Decree
3 Federal Schedule Being Developed
6 Non-Federal Schedule
7 Non-Federal Schedule Being Developed
8 Reserved
9 Subject to offsets
CDS- DATA DICTIONARY
A.2-19
-------
STATE REGULATION
Definition: STATE REGULATION contains the state's emission regulation number
for a given pollutant. In the case of NSPS or NESHAP
facilities, use the Part 60 or Part 61 Subpart notation (letters
B thru HH; found in the Code of Federal Regulations, Title 40.
Retrieval
Abbreviation
Card
Type
Card
Co 1 umn s
Data Element
Length
SREG
5
34-48
15
Valid Values:
All alphanumeric values.
Data
ALPHANUMERIC
._T:;r>e
Justified
Required on
«/ay Sntr'J
iV-a tionally
Controlled
LEFT
NO
NO
Masterfile
3 4
Record Tune
Masterfile ^_^
Position
Masterfile
Length
Edit Error Messages-.
_*** = Fatal Error
* = Warning Error
NSPS and NESHAP subpart entries should be placed at every subject emission
points. Sources subject to only one subpart should enter it at the triple
zero point as well. Sources subject to several subparts should enter the
code "MULT" at the triple zero point to indicate multiple applicability..
and the appropriate subparts at the emission point level.
Entries must be left-hand justified, with consistent use of abbreviation?;
and spacing to facilitate national as well as regional retrievals.
CDS DATA DICTIONARY
A.2-20
-------
TURNOVER COMPLIANCE FLAG
Definition: TURNOVER COMPLIANCE FLAG is a count of the number of times an Al
SIP, NESHAP, or NSPS source goes through a cycle of out of
compliance ... in compliance ... then out of compliance. Out of
compliance codes are "1 or 6." The in compliance codes are "2,
3, 4, 5, 8, and 9."
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
_Tupe
Justified
Required on
Mew Entru
Nationally
Controlled
TURN
N/A
N/A
1
NUMERIC
N/A
NO
YES
Valid Values:
1-9
Masterfile
Record Type
Masterfile
_ 89
Position
Masterfile
Length
Edit Error Messages:
*** = TURNOVER COMPLIANCE MUST BE NUMERIC
*-»* = Fatal Error * = ffarnina Error
Coding Considerations:
Anytime TURN is changed, the data element REDT will also record the date of
the update in the form of MMYY.
CDS DATA DICTIONARY
A.2-21
-------
ACTION DESCRIPTION
Definition: ACTION DESCRIPTION is generated on each action record based on
ACTION TYPE. Action Description may be coded on the card 7 for
Action Type 00.
Retrieval
Abbreviation
ADES
Card
Valid Values:
Please call the national DBC to add
or change action descriptions on the
regional Action Table.
Card
Columns
20-34
Data Element
Length
Data
ALPHANUMERIC
Tuoe
.... LEFT
Justified
Required on
New Entry
Ma tionally
YES
Controlled
Wasterfile
Record Type
Master file
Position
Hasterfile
Length
46
40-54, 107-156
15, 50
£dit Error Messages-.
*** = Fatal Srror
Warning Error
Coding Considerations:
Two action descriptions are generated from Action Type; the first is a 50
position long action description available on the Source Date Report, and
the second is a 15 position short action description retrievable on a Quick
Look Report.
When Action Type 00 is specified in card columns 53 and 54, the Ed if.
program will pick up a 15 position Action Description from card columns 20
through 34 of the card 7 and place this description on both the short and
long Action Description on the CDS Masterfile. Action Type 00 is designed
for infrequently used actions which are not placed on the Action Table
controlled by the National DBC. It can be a replacement for the regional
Action Type "OTHER - SEE COMMENTS BELOW". Since comments are not
retrievable but Action Type and Action Description are retrievable, the
Action Type 00 should be most useful for infrequently used actions which
are not on the Action Table.
CDS DATA DICTIONARY
A.2-22
-------
A.3 ACTION LEVEL DATA ELEMENTS
-------
ACTION NUMBER
Definition: ACTION NUMBER is a two digit numeric sequential action
identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Da t a
TV ne
Justified
Required on
Wew S.n try
'la tionally
Controlled
ANUM
1-8
17-18
2
NUMERIC
LEFT
YES
NO
Valid Values:
00 through 99
Masterfile
20-47
Record Tijoe
Hasterfile ^^
Position
Master file ^
Length
Edit Error Messages-.
***ACTION NUMBER MUST BE ZEROS
***ACTION NUM MUST BE GREATER THAN ZERO
*** = fatal Error
* = Warning Error
?'"f;T~ Considerations:
Actions should be assigned sequentially starting with 01. When adding new
actions to the data base, code 99; the system will convert the 99 to the
next highest sequential action number for that emission point. If several
actions and action comments are entered at the sane time with Action Number
99, comments will not be associated with the proper action. Therefore,
liters must not enter multiple actions and comments with Action iUiiUC^; ?;
simultaneously since these will produce rejects on the Update Report.
An action number cannot be added to the data base unless the emission poi»ir.
for that action is also being added or it already exists on the data base.
Each action number must be associated with an emission point.
Action number must be 00 £uc card types 1 throuyh 6; it must be greater
than zero for card types 7 and 8.
Action numbers should have no special meaning. Action number ranges must
not be used to identify certain types of actions.
CDS DATA DICTIONARY
A.3-1
-------
ACTION TYPE
Definition: ACTION TYPE is a two position alphanumeric action description
identifier.
Retrieval ^
Abbreviation
Card
Card 53-54
Columns
Data Element
Length *
Data
ALPHANUMERIC
Type
T ^ f j LEFT
Justified
Required on
., =. YES
New Entry
fJa tionally
YES
Controlled
Edit Error Messages;
*** INVALID ACTION TYPE
***ACTION TYPE REQUIRED ON NEW ENTRY
_*** = Fatal Error
Valid Values:
Must be on Action Table controlled by
national DBC.
Action Type 00 indicates an action
type which is user defined.
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error
Ceding Considerations:
Please call the national DBC to add, change, or delete entries on the
Action Table for your region.
If 00 is coded in the Action Type field, the Edit program will pick up an
Action Description from card columns 20 through 34 of the card 7. Tr; ;
capability should eliminate the need for using an Action Type mearM.-i'j
"OTHER - SEE COMMENTS BELOW".
Certain action types are required input to CDS. Please consult the current
FY air enforcement program plans and the most recent SSCD guidance materi?.i
for the most current requirements.
To obtain the most current version of a region's action types, please
follow the procedures described in Chapter 10 of this manual.
Since many action types are confidential, users should use a password on
the Retrieval Card Type 20 to obtain action level information on Retrievals.
CDS DATA DICTIONARY
A.3-2
-------
NATIONAL ACTION TYPE
Definition: NATIONAL ACTION TYPES are nationally defined, two character
values representing groups of related action types for all
regions. This data element is confidential and is for retrieval
only.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
Wew Entry
(Ja tionally
Controlled
Edit Error Messages-.
*** = Fatal Error
ACNL
N/A
N/A
N/A
N/A
N/A
N/A
YES
Valid Values:
Masterfile
Record Tupe
Masterfile
Position
Masterfile
Length
* = Warning Error
N/A
N/A
2
Coding Considerations:
Always be sure to put the date selection card before the ACNL selection
card as this will reduce the job run time.
CDS DATA DICTIONARY
A.3-3
-------
NATIONAL ACTION DESCRIPTION (LONG)
Definition: NATIONAL ACTION DESCRIPTION is generated for a retrieval based
on the National Action Type. This is the full length (50
character) description and is confidential.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Tyoe
Justified
Required on
.Vew Entry
Va tlonallu
Controlled
ADNL
N/A
N/A
N/A
N/A
N/A
N/A
YES
Valid Values:
Masterfile
N/A
Record Tupe
Masterfile
Position
Masterfile
Length
Edit Error Messages-.
*** = Fatal Error
* = Warning Error
CrAing Considerations:
Always be sure to put the date selection card before the ADNL selection
card as this will reduce the job run time.
CDS DATA DICTIONARY
A.3-4
-------
NATIONAL ACTION DESCRIPTION (MEDIUM)
Definition: NATIONAL ACTION DESCRIPTION is generated for a retrieval based
on the National Action Type. This is the medium length (30
character) description and is confidential.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
ADNM
N/A
N/A
N/A
N/A
N/A
N/A
YES
Valid Values:
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
N/A
N/A
30
Edit Error Messages-.
_*** = Fatal Error
Warning Error
Ceding Considerations:
Always be sure to put the date selection card before the ADNM selection
card as this will reduce the job run time.
CDS DATA DICTIONARY
A.3-5
-------
NATIONAL ACTION DESCRIPTION (SHORT)
Definition: NATIONAL ACTION DESCRIPTION is generated for a retrieval based
on the National Action Type. This is the short length (20
character) description and is confidential.
Retrieval
Abbreviation
Card
Type
Card
Columns
Da t, a £ j. c///t?j ( c
Length
Data
_Tuce
Justified
Required on
?Jev Entry
Ma tionally
Controlled
Edit Error Messages-
_*** = Fatal Brror
ADNS
N/A
N/A
N/A
N/A
N/A
N/A
YES
Valid Values:
Masterfile
Record Tupe
Masterfile
Position
Masterfile
Length
* = Warning Error
Coding Considerations:
Always be sure to put the date selection card before the ADNS selection
card as this will reduce the job run time.
CDS DATA DICTIONARY
A.3-6
-------
DATE ACHIEVED
definition.- DATE ACHIEVED is the date on which an action is completed in
month-day-year format.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
-Type
Justified
Required on
New Sntry
Nationally
Controlled
DTAC
7
55-60
6
NUMERIC
LEFT
NO
NO
Valid Values:
Blanks, zeros are acceptable. If
numeric other than zero, day must be
between 01 and 31, month must be
between 01 and 12, and year must be
greater than 60.
Masterfile
Record Type
Masterfile 2g_34
Position
Masterfile
Length
Edit Error Messages:
INVALID DATE ACHVD - OUTPUT ZEROS
*»* = fatal Srror
* = Warning Error
Coding Considerations:
If an error is encountererd in the date field, the bad month, day or year
is zeroed out by the edit program. An asterisk on a change transaction for
this field will zero out the field on the masterfile.
CDS DATA DICTIONARY
A.3-7
-------
DATS ACHIEVED YEAR
Definition: DATE ACHIEVED YEAR allows users to select and sort reports by
the year of date achieved and also provides more flexibility in
Milestone Reports.
Retrieval
Abbreviation
Card
Type
Card
Columns
Oata Element
Length
Data
Tupe
Justified
Required on
Hew Entry
Nationally
Controlled NO
Valid Values:
flasterfile
Record Tupe
Masterfile
Position
Masterfile
Length
46
29-30
2
Edit Error Messages-.
*** = Fatal Error
* = Warning Error
CodLia Considerations:
Valid Values are: 60 through current year (two digits)
CDS DATA DICTIONARY
A.3-3
-------
DATE ACHIEVED YEAR/MONTH
Definition: DATE ACHIEVED YEAR/MONTH allows users to select and sort reports
by the achieved month of an action. With this data element,
users can produce Milestone Reports or Quick Look Subtotals for
actions during a given month.
Retrieval
Abbreviation
Card
Tupe
Card
Columns
Data Element
Length
Dst a
Tuoe
Justified
Required on
flaw Entry
Nationally
Controlled
DAYM
N/A
N/A
4
NUMERIC
N/A
N/A
NO
Valid Values:
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
46
29-32
4
edit Error Messages-.
_*** = Fatal Error
* = Warning Error
'-'o'Ji;7<7 Considerations :
This data element consists of the year (two digits) and month (two digits)
of the Date Scheduled and the Date Achieved. A Milestone Report totaling
federal enforcement actions by month for the third quarter will look like
this:
ACTION TYPE
114 LETTER SENT
EPA INSPECTION
£?A VE EVALUATION
EPA CIV/CRIM ACTION
REGIONAL ADES TOTALS
REGION
TOTAL
46
109
190
26
371
DAYM
7804
12
42
48
109
134
DAYM
7806
16
28
80
4_
128
CDS DATA DICTIONARY
A.3-9
-------
Definition:
DATE SCHEDULED
DATE SCHEDULED is the date on which an action is scheduled to be
performed. Use the month-day-year format.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
T,£>rtn1*h
Data
Tupe
Justified
Required on
New Entry
Nationally
Controlled
DTSC
7
61-66
6
NUMERIC
LEFT
YES
NO
Valid Values:
Blanks or zeros are acceptable.
Otherwise, day must be between 01 and
31, month must be between 01 and 12,
and year must be greater than 60.
Masterfile
Record Tupe
Masterfile 2^Q
Position
Masterfile
Length
Edit Error Messages:
*INVALID DATE SCHED - OUTPUT ZEROS
*DATE SCHED .REQUIRED ON NEW ENTRY
*** = Fatal Error
* = Warning Error
Ceding Considerations:
If an error is encountered in the date field, the bad month or day or year
is zeroed out. If this field is left blank on a new transaction and if the
Date Achieved is valid, the Date Achieved is moved into this field by the
Edit Program.
CDS DATA DICTIONARY
A.3-10
-------
DATE SCHEDULED YEAR
Definition: DATE SCHEDULED YEAR allows users to select and sort reports by
the year of date scheduled and also provides more flexibility in
Milestone Reports.
Retrieval Dsyy
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
NUMERIC
Type
Justified
Required on
Wet* Entry
Nationally
Controlled NO
Edit Error Messages-.
*** = Fatal Error
Valid Values:
Master file
Record Type
Master file
Position
Masterfile
Length
* = Warning Error
46
23-24
2
Ceding Considerations :
CDS DATA DICTIONARY
A.3-11
-------
DATE SCHEDULED YEAR/MONTH
Definition: DATE SCHEDULED YEAR/MONTH allows users to select and sort
reports by the scheduled month of an action. With this data
element, users can produce Milestone Reports or Quick Look
Subtotals for actions during a given month.
Retrieval
Abbreviation
Card
Type
Card
\ 7 ?»mn
Data Element
^Length
Data
Type
Valid Values;
DSYM
N/A
N/A
NUMERIC
Justified
N/A
Masterfile
Record Type
46
Required on
Hew Entry
N/A
Masterfile
Position
23-26
iVa tionally
Controlled
NO
Masterfile
Length
Edit Error Messages-.
_*** = fatal Error
* = Warning Error
Coding Considerations:
This data element consists of the year (two digits) and month (two digits)
of the Date Scheduled. A Milestone Report totaling federal enforcement
actions by month for the third quarter will look like this:
ACTION TYPE
114 LETTER SENT
EPA INSPECTION
EPA VE EVALUATION
EPA CIV/CRIM ACTION
REGIONAL ADES TOTALS
REGION
TOTAL
46
109
190
26
371
DSYM
7804
12
42
48
7
109
134
DSYM
7806
16
28
SO
4
128
CDS DATA DICTIONARY
A.3-12
-------
CIVIL PENALTY AMOUNT
Definition: CIVIL PENALTY AMOUNT indicates the civil penalty assessed
against a facility in the final, legally binding agreement
between the enforcement authority and the source.
Retrieval
Abbr evia t ion
Card
Type
Card
Columns
Data Element
Length
Data
Tuoe
Justified
Required on
New Entry
Nationally
Controlled
PLTY
7
46-52
7
NUMERIC
RIGHT
NO
NO
Valid Values:
All numeric values.
Master file
Record Type
Masterfile
Position
Masterfile
Length
46
93-99
7
Edit Error Messages-.
*** = Fatal Error
* = Warning Error
ing Considerations:
This field should be used in conjunction with the following action types:
24 State Civil Penalty
26 Federal Civil Penalty
Dollar amounts must be right justified; they should be rounded to the
nearest 3100. No commas, dollar signs, or periods must be used.
CDS DATA DICTIONARY
A.3-13
-------
REGIONAL DATA ELEMENT 8
Definition: REGIONAL DATA ELEMENT 8 is user supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Tyoe
Justified
Required on
New Entry
Nationally
Controlled
RDE8
7
72-73
2
ALPHANUMERIC
LEFT
NO
NO
Valid Values:
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
46
57-58
2
Edit Error Messages :
*** = Fatal Error
* = Warning Error
Coding Considerations:
Typical usages of this field include identifiers for (as of March, 193:1) :
Region III A - Active Enforcement Actions
VR - Vapor Recovery
NJ/NY - Demolition location
Also, pollutant code is sometimes
used with inspections, notices, orders
Region V
Region VII
114 letters sent indicator
Opacity Readings
CHS DATA DICTIONARY
A.3-14
-------
Definition:
RESULTS CODE
RESULTS CODE indicates the results of an action such as action
achieved, action not achieved, or action rescheduled.
R^rleVal STAC
Abbreviation
Card
Type
?f 7°-71
Columns
Valid Values:
May be a blank; if not a blank, it
must be a two digit numeric field.
Must exist on the RESULTS-CODE Table
controlled by the National DBC.
Data Element
Length
ata NUMERIC
T * f * LEFT
Justified
Required on
» NO
New Entry
Nationally
Vff.Q
Controlled
Edit Error Messages:
* INVALID RESULTS CODE
*** = Fatal Error
Masterfile
46
Record Type
Masterfile ^
Position
Nasterfile
Length
* = Warning Error
Coding Considerations:
The results code can indicate the success of an action, including wn.\.-ch.--:
or not the action was carried out.
Please call the National DBC to add, change, or delete entries on the
Results-Code Table for your region. See Chapter 10 for instructions on how
to obtain the most current Results Code Table for your region.
CDS DATA DICTIONARY
A.3-15
-------
RESULTS CODE DESCRIPTION
Definition: RESULTS CODE DESCRIPTION is an English language description of
the results code (STAC). It is computer generated based on the
region and the STAC. It is not input by the user. It is stored
on the masterfile and is updated when STAC is changed.
*e*rleVal . RSTD
Abbreviation
Card
Type
Valid Values:
The Results Code (STAC) must exist
on the RESULTS CODE TABLE controlled
by the National DBC.
Card
Columns
Data Element
Length 15
Data
ALPHANUMERIC
T * * j LEFT
Justified
Required on
New Entry
Nationally
Controlled
Edit Error Messages-.
*** = Fatal Error
Masterfile
Record Type
Masterfile
Position
Masterfile ,
Length
* = Warning Error
Coding Considerations:
See Chapter 10 for instructions for listing the most current Results Code
Table.
CDS DATA DICTIONARY
A.3-16
-------
STAFF NAME (ACTION)
Definition: STAFF NAME (ACTION) is a fifteen position name
the Staff Code found on card 7. positions 67-69.
generated from
^f ieVal . STFA
Abbreviation
Card
Type
Card
Columns
Valid Values:
All names are on the Personnel Table
maintained by the National DBC.
Please call the OBC to make additions
- or changes to this table.
Data Element
Length
Data
ALPHANUMERIC
_7ype
Justified
Required on
-------
Definition:
ACTION STAFF CODE
ACTION STAFF CODE is a three position code referring to the
staff member assigned to complete the action.
Retrieval
... . . PERA
Abbreviation
Card
Type
J"d 67-69
Columns
Data Element
Length 3
Valid Values:
Must exist on the Personnel Table
controlled by the National DEC. The
first position must be alpha; the
next two numeric. When requesting
changes to this table, be sure to
give the DEC full title information
as well.
Data
T ALPHANUMERIC
_ +.f.. LEFT
Justified
Required on
NO
New Entry
Ma tionallu
YES
Controlled
Edit Error Messages-.
* INVALID STAFF CODE
*** = Fatal Error
Masterfile
46
Record Type
Masterfile
Position
Masterfile
Length
* ~ Warning Error
Coding Considerations:
Please call the National DBC to make additions, changes, or deletic
the Personnal Table.
s to
CDS DATA DICTIONARY
A.3-18
-------
STAFF TITLE
Definition: STAFF TITLE is a fifteen position title generated from the Staff
Code found on card 7, position 67-69.
Retrieval
Abbreviation
TITL
Card
Type
Card
Columns
Data Element
Length
Data
Type
ALPHANUMERIC
Valid Values:
All titles are on the Personnel Table
maintained by the National DBC.
Whenever making any changes to this
table, be sure to give the DBC full
title information.
Justified
Masterfile
Record Type
46
Required on
New Entry
Masterfile
Position
78-92
Nationally
Controlled
Masterfile
Length
15
Edit Error Messages:
_*** = Fatal Erro'r
* = Warning Error
Coding Considerations:
During each update cycle, the Staff Title is generated based on the Ac.-....:
Staff Code. By changing the title associated with a staff code on the
Personnel Table, all input transactions and masterfile records will carry
the new title.
CDS DATA DICTIONARY
A.3-19
-------
STATE COUNTY SOURCE POINT ACTION
Definition: STATE COUNTY SOURCE POINT ACTION combines those five data
elements for selection purposes only.
Retrieval
Abbreviation
Card
Type
Card
Columns
£»ata Element
Data
Type NUMERIC
T * J N/A
Justified
Required on
., r, N/A
Mew Entry
Nationally
N/A
Controlled
Valid Values:
Master file
Record Type
Masterfile
Position
Masterfile
Length
46
3-18
16
Edit Error Messages:
*** = Fatal Error
Warning Error
Coding Considerations:
N/A
CDS DATA DICTIONARY
A.3-20
-------
A.4 COMMON TO ALL CARDS DATA ELEMENTS
-------
CARD CODE
Definition:
of
Retrieval
Abbreviation
Card
Tupe
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
nationally
Controlled
fixed format information found on the CDS input punch card.
Valid Values:
1 = source record
2 = source record
1-9 3 = pollutant record
5 = emission point record
6 = emission point comment
7 = action record
1 8 = action comment
9 - additional emission point record
NUMERIC
Master file
Record Tupe
Vaster file
XiLO _
Position
, - Master file
Y-'S r , ,
LI en a tfi
Edit Error Messages-.
***INVALID CARD CODE
>»* = Fatal Error
* = Warnina Error
Coding Considerations
CDS DATA DICTIONARY
A.4-1
-------
Definition:
COMMENTS
COMMENTS can be used to place on the CDS raasterfile data which
does not fit into any fixed card format.
Retrieval
Abbreviation
Card
Type
Card
Columns
4, 6, 8
21-79
Data Element
Length
Data
Type
59
ALPHANUMERIC
Valid Values:
All alphanumeric values.
Justified
Required on
NO
Nev Entry
Nationally
NO
Controlled
Master-file
Record Type
Master file
Position
Masterfile
Length
21, 35, 47
22-80
59
Edit Error Messages:
*** = Fatal Srror
* = Warning Error
Coding Considerations:
All comments can be retrieved on a Source Data Report and only action
comments can be retreived on an Action Summary Report. Any or all comments
may be retrieved on a Quick Look Report.
Use Card 4 for a source comment;
Card 6 for a point comment;
Card 8 for an action comment.
Do not use comment records to carry enforcement action information or
compliance status information; other card types are available for these
purposes.
CDS DATA DICTIONARY
A.4-2
-------
LINE NUMBER
Definition: LINE NUMBER is used by the computer to distinguish one comment
line from another.
Retrieval
Abbreviation
Card
Tvoe
4' 6' 8
Columns
20
Justified
Edit Error Messages-.
***LINE NUMBER MUST BE NUMERIC
*** = Fatal Error
Valid Values:
0 through 9, A and B
Data Element
Length
Data
Type
1
NUMERIC
Record Type_
Required on
, YES
New Entry
Nationally
Controlled
Masterfile
Position
Masterfile
Lenath
21
1
* = Warning Error
Coding Considerations:
'-..:3i:;r, line numbers sequentially. Before assigning a line number,
the source data report to be sure the number you code is not already on tfce
date base for that particular emission point. Although Line Number is
carried on the masterfile, it is not a retrievable data element.
Line Number A and B on Card Code 4 have been set aside for mailing label
information. There are special coding sheets available for
mailing labels.
CDS DATA DICTIONARY
A.4-3
-------
RECORD TYPE
Definition: RECORD TYPE is a two position numeric masterfile record
identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
m NUMERIC
Justified
Required on
New Entry
Nationally
Controlled
Sdit Error Messages*
_*** = Fata 1 Error
Valid Values:
20 - Source
21 * Source comment
34 » Emission Point
35 » Point comment
46 - Action
47 Action comment
tfasterfi-Ze
Record Type
Masterfile
Position
Masterfile
Length
* = Harnincr Error
20-47
19-20
2
Coding Considerations:
Each Card Type has a corrasconding raasterfil-3 Record 'rype.
CDS DATA DICTIONARY
A.4-4
-------
UPDATE CODE
Definition: UPDATE CODE tells the update program to add, change, or delete a
transaction. This data element is not carried on the masterfile
but serves to tell the update program what to do with other data
on the input transaction.
Retrieval
Abbreviation
Card
Tupe
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
N/A
1-8
80
1
ALPHA
YES
YES
Valid Values;
N - New
C * Change
Masterfile
Record Type
Masterfile
Position
Masterfile
Lencfth
Edit Error Messages-.
***UPDATE CODE D INVALID FOR CARD TYPE 2 & 3
*** INVALID UPDATE CODE
***DO NOT DELETE POINT 000
***NO DATA IN COL 21-79 FOR DELETES
_*** = Fatal Error _ * = Warning Error _
Coding Considerations:
The CDS-EDIT only validates the existence of the update code; it is the
Update report which points out incorrect or illogical update codes.
Each card type, except card type 2, has a corresponding record type on the
CDS data base. If a card type 1, 4, 5, 6, 7, or 8 has not already created
a masterfile record type, it must be added as New. Each point, action, or
comment record must be associated with a corresponding source record. Each
point comment must be associated with a point. Each action must be
associated with a point. Each action comment must be associated with an
Key data elements (region, state, county, source, point, and action
numbers) cannot be changed. Other data elements can be changed by using
the update code 'C'. Only those record types which have been successfully
added as new prior to this update cycle can be changed. Only those data
elements which are actually being changed need to be added on a change
CHS DATA DICTIONARY
A. 4-5
-------
UPDATE CODE
Coding Considerations: (Continued)
transaction. By coding an asterisk anywhere in a data field, that data
field will be changed to spaces (date values will be zeroed out).
The update code 'D' deletes one or more records on the CDS data base. A
card type 1 delete will delete all masterfile records for a given source.
A card type 5 delete will delete a point together with all associated
comments, actions, and action comments. Point 000 cannot be deleted unless
a card type 1 is used for the delete function.
A card type 7 delete will delete an action together with all associate.
action comments.
A card type 4, 6, or 8 delete must have a valid line number. One delete
card is needed to delete each comment line number.
No data may be punched in columns 21 through 79 for deletes to protect th-^
data base against a mispunched delete update code.
A card 2 or 3 delete is invalid.
CDS DATA DICTIONARY
A.4-6
-------
FIVE POSITIONS BLANK - FILLER
Definition: FIVE POSITIONS BLANK - FILLER - used on Quick Look Report to
provide proper spacing of report.
Retrieval
Abbreviation
Valid Values:
Card
Type
Card
Columns
Data Element
Length 5
Data
Tu oe
Justified
Required on
Wet" Entry
Nationally
Controlled
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
__**" = Fatal Error * = Harning Error
Coding Considerations:
?:GU input - used only on Retrieval Quick Look Reports for proper spacing.
CDS DATA DICTIONARY
A.4-7
-------
FIFTEEN POSITIONS BLANK - FILLER
Definition: FIFTEEN POSITIONS BLANK - FILLER - used on Quick Look Report to
provide proper spacing of report.
Retrieval
Abbreviation
Valid Values:
Card
Type
Card
Columns
Data Element , c
Length *"'
Data
Type
_Justir"ied
fleguired on
New Entry
Nationally
Controlled
Wasterfile
Record Type
Waster file
Position
Masterr"ile
Length
Edit Error Messages:
_*** = Fatai Error * = Warning Error '
Coding Considerations:
Not input - used only on Retrieval Quick Look Reports foe proper spacing,
COS DATA DICTIONARY
A. 4-8
-------
APPENDIX B
CONTACT LIST OP CDS USERS
-------
CONTACT LIST OF CDS USERS AT STATES
Arkansas
Robert Gage
501-562-7444
Arkansas Dept. of Pollution
Control and Ecology
8001 National Drive
Little Rock, AR 72209
California
Gerald H. White
916-322-2895
Air Resources Board
1102 Q Street
P.O. Box 2815
Sacramento, CA 95812
Delaware
Ron Malenfant
302-736-3462
Natural Resources and Environmental Control Dept,
89 Kings Highway
P.O. Box 1401
Dover, DE 19903
Georgia
Jim Mullins
404-656-7410
Department of National Resources
4291 Memorial Drive, Suite M
Decatur, GA 30032
Hawaii
Kazuo Shishido
808-548-6355
State Health Department
Pollution Investigation and Enforcement Branch
Box 3378
Honolulu, HI 96801
Idaho
Jim Boylan
2Co-334-5360
450 W. State Street
5bh Floor
Boise, ID 83720
Iowa
John Vedder
515-231-8940
Iowa Department of Environmental Quality
Henry A. Wallace Bldg.
Des Moines, IA 50319
Kansas
Terry Denker
913-862-9360
Bureau of Air Quality and Occupational Health
Dept. of Health and Environment
Building 740 Forbes
Topeka, KS 66620
Louisiana
Atley Brasher
504-342-1206
Louisiana Department of Natural Resources
Air Quality Division
P.O. Box 44066
Baton Rouge, LA 70804
B-l
-------
Maryland
Ron Lipinski
301-383-2776
CONTACT LIST OF CDS USERS AT STATES
(Continued)
Maryland BAQNC
201 West Preston Street
Baltimore, MD 21201
Minnesota
John Morrill
612-296-7740
Minnesota Pollution Control Agency
1935 West County Road B-2
Roseville, MN 55113
Missouri
Mike Mueller
314-751-3241
Missouri Dept. of Natural Resources
P.O. Box 1363
2010 Missouri B1_vd .
Jefferson City, MO 65102
Nebraska
Dick Varner
Dennis Burling
402-471-2186
Division of Air Pollution
Department of Environmental Control
P.O. Box 94653, State House Station
Lincoln, NE 63509
New Mexico
David Duran
505-827-5271 Ext. 356
Air Quality Section
P.O. Box 968
Santa Fe, NM 87503
New York
Gordon Howe
518-457-7611
Bureau of Abatement Planning
Division of Air
50 Wolf Road
Albany, MY 12233
Ohio
Clara Dailey
614-466-6040
Ohio Environmental Protection Agency
Box 1049
361 East Broad Street
Columbus, OH 43216
Oregon
Peter Prey
503-229-6070
Oregon Department of Environmental Quality
P.O. Box 1760
Portland, OS 97209
Puerto Rico
Ms. Nitza Pinzon
809-722-0077
Environmental Quality Board
P.O. Box 11488
Santurce, PR 00910
South Carolina
Bob Betterton
803-758-5406
South Carolina Department of Health
2600 Bull Street
Columbia, SC 29201
B-2
-------
South Dakota
Joel Smith
605-773-3329
CONTACT LIST OF CDS USERS AT STATES
(Continued)
Department of Hater & Natural Resources
Joe Foss Bldg.
Pierre, SD 57501
Tennessee
Stan Lodl
615-741-3931
Division of Air Pollution Control
150 Ninth Avenue
Nashville, TN 37219
Virginia
Paul Pitts
804-786-4867
Air Pollution Control Board
Richmond, VA
B-3
-------
COS REGIONAL MANAGERS
National CDS Data Bank Coordinator
Franklin C. Smith
202-382-2881 FTS 382-2833
U.S. Environmental Protection Agency
Office of Air, Noise and Radiation
EN-341
401 M. Street, SW
Washington, DC 20460
Region I - Boston
Cheryl Brown
617-223-5137
Enforcement Division
U.S. Environmental Protection Agency
J.P. Kennedy Federal Building
Boston, MA 02203
Ration II New York
Ken Eng
Jerry DeGaetano
212-264-4726
FTS 264-4726
Planning and Management Division
U.S. Environmental Protection Agency
26 Federal Plaza
New York, NY 10007'
Region III - Philadelphia
Abe Ferdas
215-597-9401
Connie Carr
215-597-0803 FTS 597-0803
Enforcement Division
U.S. Environmental Protection
Curtis Building
6th and Walnut Street
Philadelphia, PA 19106
Agency
Region IV - Atlanta
Zylphia Murphy
404-881-4253
FTS 285-5291
Enforcement Division
U.S. Environmental Protection Agency
345 Courtland Street
Atlanta, GA 30308
Region V - Chicago
George Hurt
312-886-6794
FTS 353-2088
Enforcement Division
U.S. Environmental Protection Agency
230 South Dearborn Street
Chicago, IL 60604
Region VI - Dallas
Mary Kay Maruaak
214-767-9855
FTS 767-9855
Enforcement Division
U.S. Environmental Protection Agency
1201 Elm Street
Dallas, TX 75270
Region VII - Kansas City
JoAnn Heiman
816-374-2576
Enforcement Division
U.S. Environmental protection Agency
324 East Eleventh Street
Kansas City, MO 64106
Region VIII - Denver
Judy Laverdure
303-837-3471
FTS 327-3471
Enforcement Division
U.S. Environmental Protection Agency
1860 Lincoln Street
Denver, CO 80203
B-4
-------
CDS REGIONAL MANAGERS
(Continued)
Region IX - San Francisco
Chuck Seeley
Marian Lundholra
415-974-7646 FTS 974-7646
Enforcement Division
U.S. Environmental Protection Agency
215 Fremont Street
San Francisco, CA 94111
Region X - Seattle
Betty Swan
John Heller
206-442-2876
FTS 399-2876
Enforcement Division
U.S. Environmental Protection Agency
1200 6th Avenue
Seattle, MA 98101
National Operations Contractor
TRC Environmental Consultants
Greg Fisher
Bob Bowers
Chris Mason
Jill Keane
Jennifer Hovey
Michael Kelly
203-289-8631
800 Connecticut Boulevard
East Hartford, CT 06108
B-5
-------
CDHS CONTACTS
Regional
Office CDHS
I Mr. William Secovy (Mgmt)
EPA, Region I
John F. Kennedy Bldg.
Room 2207-B
Boston, MA 02203
(FTS) 223-5885
II Mr. Lew Heckman (Air Branch)
EPA, Region II
26 Federal Plaza
New York, NY 10007
(FTS) 264-9800
III Or. Sandor Kovacs (A&HM)
EPA, Region III (3AH11)
6th and Walnut Streets
Philadelphia, PA 19105
(FTS) 597-8133
IV Mr. Barry Gilbert (A&HM)
EPA, Region IV
345 Courtland Street, NE
Atlanta, GA 30308
(FTS) 257-2864
V Mr. Steve Goranson (S&A)
EPA, Region V
230 S. Dearborn, 26th Fl.
Chicago, IL 60604
(FTS) 353-2303
VI Mr. Dave White (Mgmt)
EPA, Region VI
1201 Elm Street
Dallas, TX 75270
(FTS) 749-3761
VII Mr. Seymour Shuater (ASHM)
EPA, Region VII
1735 Baltimore Avenue
Kansas City, MO 64108
(FTS) 758-3791
VIII Mr. Dave Lewis (S&A)
EPA, Region VIII
1860 Lincoln Street
Denver, CO 80295
(FTS) 327-2226
AQDHS-II
BIS/P&R
Mr. Ed Finfer (Air Branch)
aPA, Region II
26 Federal Plaza
New York, NY 10007
(FTS) 264-9800
Mr. Mike Davis (F&T)
EPA, Region II
26 Federal Plaza
New York, NY 10007
(FTS) 264-9578
Mr. William Snider (A&HM)
EPA, Region IV
345 Courtland Street, NE
Atlanta, GA 30308
{FTS) 257-2864
Mr. Steve Goranson (S&A)
EPA, Region V
230 S. Dearborn, 26th Fl.
Chicago, IL 60604
(FTS) 353-2303
Ms. Ginger Smiley (Mgmt)
EPA, Region VI
1201 Elm Street
Dallas, TX 75270
(FTS) 749-3761
Mr. Barry Gilbert (A&HM)
EPA, Region IV
345 Courtland Street, NE
Atlanta, GA 30308
(FTS) 257-2864
Mr. Barry Bolka (S&AJ
EPA, Region V
230 S. Dearborn, 26th Fl.
Chicago, IL 6050-;
(FTS) 353-2303
Ms. Ginger Smiley (Mgmt)
EPA, Region VI
1201 Elm Street
Dallas, TX 75270
(FTS) 749-3761
B-6
-------
CDHS CONTACTS
(Continued)
Reg ional
Office CDHS AQDHS-II EIS/PSR
IX Ms. Caroline Ireson (S&A) Mr. Shun Obinata (Mgrat) Mr. Shun Obinata (Mgmt)
EPA, Region IX EPA, Region IX EPA, Region IX
215 Fremont Street 215 Fremont Street 215 Fremont Street
San Francisco, CA 94105 San Francisco, CA 94105 San Francisco, CA 94105
(FTS) 556-2270 (FTS) 556-2326 (FTS) 556-2326
X Ms. Shirley Towns (S&A)
EPA, Region X
1200 6th Avenue (M/S 345)
Seattle, WA 98101
(FTS) 399-1106
B-7
-------
CDHS CONTACTS
Regional
Office
NEDS
SAROAD
OTHER CONTACTS
Mr. John Courcier (A&HM) Mr. Norman J. Beloin (S&A) Mr. William Serovy (Mgrat)
EPA, Region I
John F. Kennedy Bldg.
Boston, MA 02203
(FTS) 223-4448
EPA, Region I
60 Westview Street
Lexington, MA 02173
(617) 861-6700
EPA, Region I
John F. Kennedy Bldg.
Room 2207-B
Boston, MA 02203
(FTS) 223-5885
II Mr. Mike Davis (F&T)
EPA, Region II
26 Federal Plaza
New York, NY 10007
(FTS) 264-9578
III Dr. Sandor Kovacs (A&HM)
EPA, Region III (3AH11)
6th and Walnut Streets
Philadelphia, PA 19106
(FTS) 597-8133
Mr. Ed Finfer (Air Branch)
EPA, Region II
26 Federal Plaza
New York, NY 10007
(FTS) 264-9800
Dr. Sandor Kovacs (A&HM)
EPA, Region III (3AH11)
6th and Walnut Street
Philadelphia, PA 19106
(FTS) 597-8133
Mr. Ted Standish (Mgrat}
EPA, Region III
6th and Walnut Streets
Philadelphia, PA 19106
(FTS) 597-8046
IV Mr. Barry Gilbert (A&HM)
EPA, Region IV
345 Courtland Street, NE
Atlanta, GA 30308
(FTS) 257-2864
V Mr. Barry Bolka (S&A)
E?A, Region V
230 S. Dearborn, 26th Fl.
Chicago, IL 60604
(FTS) 353-2303
VI Mr. Tim Matzke (S&A)
EPA, Region VI
1201 Elm Street
Dallas, TX 75270
(FTS) 729-2724
Mr. William Snider (A&HM)
EPA, Region IV
345 Courtland Street, NE '
Atlanta, GA 30308
(FTS) 257-2864
Mr. Steve Goranson (S&A)
EPA, Region V
230 S. Dearborn, 26th Fl.
Chicago, IL 60604
(FTS) 353-2303
Mr. Tim Matzke (S&A)
EPA, Region VI
1201 Elm Street
Dallas, TX 75270
(FTS) 729-2724
Ms. Kathryn Karaalick (SAROAD)
Mr. Larry Lahr.T.a;i ,'''.i-u,
EPA, Region V
230 S. Dearborn, 26th Fl.
Chicago, IL 60605
(FTS) 353-2303
Ms. Ginger Smiley (Mgmt)
EPA, Region VI
1201 Elm Street
Dallas, TX 75270
(FTS) 729-2641
VII Mr. Seymour Shuater (A&HM)
EPA, Region VII
1735 Baltimore Avenue
Kansas City, MO 64108
(FTS) 758-3791
VIII Mr. Dave Lewis (S&A)
EPA, Region VIII
1860 Lincoln Street
Denver, CO 80295
(FTS) 327-2226
Mr. Seymour Shuster (A&HM)
EPA, Region VII
1735 Baltimore Avenue
Kansas City, MO 64103
(FTS) 758-3791
Mr. Dave Lewis (S&A)
EPA, Region .VI11
1860 Lincoln Street
Denver, CO 80295
(FTS) 327-2226
Mr. Tom Entzminger (S&A)
EPA, Region VIII
1860 Lincoln Street
Denver, CO 80295
(FTS) 327-2226
B-8
-------
Regional
Office
IX
NEDS
Mr. Shun Obinata (Mgmt)
EPA, Region IX
215 Fremont Street
San Francisco, CA 94105
(FTS) 556-2326
Ma. Shirley Towns (S&A)
EPA, Region X
1200 6th Avenue (M/S 345)
Seattle, WA 98101
(FTS) 399-1106
CDHS CONTACTS
(Continued)
SAROAD
Mr. Shun Obinata (Mgmt)
EPA, Region IX
215 Fremont Street
San Francisco, CA 94105
(FTS) 556-2326
Ms. Shirley Towns (S&A)
EPA, Region X
1200 6th Avenue (M/S 345)
Seattle, WA 98101
(FTS) 399-1106
OTHER CONTACTS
Ms. Caroline Ireson (S&A)
EPA, Region IX
215 Fremont Street
San Francisco, CA 94105
(FTS) 556-2270
B-9
OV.S. GOVERNMENT PRINTING OFFICE 1983-639-001/3001
-------
INDEX
-------
INDEX
A - Action Summary Report; 107
Action Table; 164
Applications
- general; 7
- specific; 8
B -
C - Coding Sheet, Input
- change; 50
- delete; 54
- new facility; 46
Compliance
- Retrievals; 110
- Status Action Reports; 107
Confidentiality; 124
Continuous Monitoring Subset; 209
Critical Data Element Report; 93
County Code Table; 161
CDS Query; 152
D - Data Input Preparation; 32
- general; 32
Data Submissions; 29
- s-eps; 29
Dummy Option, (Edit); 71
E - Edit Program; 13
- Dummy Option; 71
- Edit Error Messages; 17, 67
- Edit Flow Chart; 16
- Edit Job Control Language; 65
- Edit Processing; 64
- Edit Program Usage; 64
- Sample Edit Report; 70
Execs? 152
F -
G - Graphics; 208
1-1
-------
INDEX
(Continued)
H - Headquarters Guidance & Quality Control Measures; 199
I - Input Data; 13, 32
Input Instructions
- Card 1; 35
- Card 2; 37
- Card 3; 38
- Card 4; 41
- Card 5; 41
- Card 6; 43
- Card 7; 44
- Card 3; 45
INPUT Exec; 152
J - Job Control Language
- Edit; 65
- Retrieval; 143
- Update; 86
K - Keypunch Instructions; 42, 55-60
L - Logic Selection Card - Card 10; 121-123
M - Mailing Label Option; 117
Management
- Overview; 2
- Background; 2
Masterfile
- Changing Data,- 47
- Deleting Data; 51
- Hierarchy; 24
- Layout; 171
- New Records; 35
- Regional; 23
Modfile; 17
- multi-card layout form; 33
Milestone Report; 102-104
- standard; 105
- variable; 106
1-2
-------
INDEX
(Continued)
Microfiche
- consideration; 173
- request; 174-179
N -
0 -
P - Personnel Code Table; 162
PSD Report; 111-113
Q - Quality Assurance Considerations; 61
Query; 152
Questionnaire Report; 104
Quick Look Report
- Example; 99
- Data Selection Card - Card 40; 127-128
R - Report Request Form; 115 ,
REPORT Exec; 158
Report Sequence Card - Card 30; 125
: -r 3 i- - "- 3 '". C C '<- T a C I ^ ; i 6 6
Retrieval Program; 23
- Available Reports; 25, 96
- Flow Chart; 28
- Pollutant Compliance Retrievals; 130-133
- Processing,- 95
- Report Format Card - Card 20; 123
- Retrieval Edits performed by the system; 142
- Selection Cards; 118
- Steps; 27
Re-rievai, General Instructions; 113
- Card 01; 120
- Card 10; 121
- Card 20; 123
- Card 30; 125
- Card 40; 127
- Card 50; 129
S - Source Data Reports; 103
Standard Milestone Report; 105
1-3
-------
INDEX
(Continued)
Supportive Technical Information; 161
System Application; 7
- Capabilities; 3
- Functions; 4
- Overview; 12
- Purposes; 3
- Relationship to other systems; 6
T - TABLES Exec; 158
U - Update Processing
- Critical Data Element Report; 93-94
- Cycle; 19
- Error Messages; 20, 89
- Flow Chart; 21
- Job Control Language; 86
- Overview; 18
- Program; 18, 82
- Report Messages; 20, 87
- Sample Report; 88
- Scheduling; 84
- Status Log; 91
V - Variable Milestone Data Selection Card - Card 50; 129
W WYL3UR
- CDS/WYLBUR Example; 78, 79
- Input; 71
- Preparation to WYLBUR; 76, 78
- Execs; 152
tMJ.S GOVERNMENT PRINTING OFFICE l?-'?-">;'--''C'
1-4
------- |