;;, :.,. .., -United States, 4i ,
OH Ion, of
' , '..*:•;•"'. •';; r, ' v"l''',(1, -['Environmental rPfijWctlofi ;',^;- , Enforcement'
!;'.'""':',V'?/-'.";1.:.'' !.•'!,. .'•'';••-''p.) i'A&Bncy ""• ,;V ',..,".•:'!•''."'*'!'' Washington DC 20460
EPA-340/1-80Q03 '
February 1980
-------
UPDATES AND REVISIONS TO THIS MANUAL
The Compliance Data System (CDS) User's Guide is updated periodically
to document changes to the system. These changes occur whenever reporting
requirements are altered or expanded; changes also occur whenever programming
enhancements are made to the system.
If you would like to receive all updates and revisions to this manual,
please make a copy of this page and mail it to:
Mr..Franklin Smith
U.S. Environmental Protection Agency
Division of Stationary Source Enforcement
EN-341
401 M Street S W
Washington, D. C. 20460
Manual holder's name:
Address:
Mail stop:
Telephone:
-------
The Stationary Source Enforcement Series of reports is
issued by the Office of Enforcement, 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 nominal cost,
from the National Technical Information Service, 5285 Port Royal
Road, Springfield, Virginia 22151.
-------
TABLE OF CONTENTS
SECTION PAGE
1.0 INTRODUCTION 1
2.0 MANAGEMENT OVERVIEW 2
2.1 Background History 2
2.2 System Purposes 3
2.3 System Capabilities 4
2.4 System Functions 5
2.5 System Relationship to Other EPA Systems 6
3.0 SYSTEM APPLICATIONS 8
3.1 General Applications 8
3.2 Examples of Specific Applications 9
4.0 SYSTEM OVERVIEW 13
4.1 Edit Program 14
4.1.1 Input Data Processed by CDS 15
4.1.2 Edits Performed by CDS 15
4.1.3 Edit Error Messages 17
4.1.4 CDS MOD File 19
4.2 Update Program 20
4.2.1 Update Actions by CDS 21
4.2.2 Update Cycle Steps 21
4.2.3 Update Report Messages 21
4.2.4 The CDS Masterfile 24
4.2.5 Regional CDS Masterfile 26
4.3 Retrieval Program 26
4.3.1 Description of Reports Available from Retrieval 26
Program
4.3.2 Retrieval Steps 30
5.0 DATA SUBMISSIONS PROCEDURES 32
5.1 Submission Steps 32
6.0 DATA INPUT PREPARATION 35
6.1 General 35
6.2 Adding New Records to the CDS Masterfile 39
6.2.1 Sample of a Completed Coding Sheet for a New 47
Facility
6.3 Changing Data on the CDS Masterfile 50
6.3.1 Sample Completed coding sheet for Change 52
Transactions
6.4 Deleting Data from the CDS Masterfile 53
6.4.1 Sample Completed Coding Sheet for Delete 55
Transactions
6.5 Keypunch Instructions 56
6.6 Quality Assurance Considerations 65
6.6.1 Define the Problem 65
6.6.2 Status of Current Data 65
6.6.3 Code Data 65
6.6.4 Random Check of Coding 66
-------
TABLE OF CONTENTS
SECTION PAGE
6.6.5 Computer Operation 66
7.0 EDIT PROCESSING 68
7.1 Edit Program Usage 68
7.1.1 Warning and Fatal Errors 69
7.2 Edit Error Messages 69
7.3 Sample CDS Edit Report 72
7.4 Edit Job Control Language (JCL) 74
7.5 CDS Input Preparation via WYLBUR 81
7.6 CDS/WYLBUR Example 83
8.0 UPDATE PROCESSING 86
8.1 Update Program Description 86
8.2 Update Scheduling 88
8.3 Update Report 89
8.4 Update Report Messages 90
8.5 Update Status Log 91
8.6 Update Report Job Control Language 97
9.0 RETRIEVAL PROCESSING 98
9.1 Reports Available from the Retrieval 99
9.1.1 Quick Look Report 100
9.1.2 Double Spaced Quick Look Report 103
9.1.3 Source Data Report 105
9.1.4 Milestone Report 107
9.1.5 Questionnaire Report 111
9.1.6 Action Summary Report 113
9.1.7 Compliance-Action Report 113
9.2 Check List for Request Submissions 117
9.3 Preparing Retrieval Selection Cards 124
9.3.1 Special Considerations for Pollutant 135
Compliance Retrievals
9.3.2 Pollutant Compliance Logic Selection 136
9.3.3 Pollutant Compliance Sorting 137
9.3.4 Printing Pollutant Compliance Data 138
9.3.5 Sample of a Filled-in Retrieval Request 139
9.4 Job Control Language for Using Retrieval 148
Program
9.5 Retrieval Edits Performed by System 152
10.0 SUPPORTIVE TECHNICAL INFORMATION 158
10.1 Table Processing 158
10.1.1 County Code Table 158
10.1.2 Personnel Code Table 161
10.1.3 Action Table 164
10.1.4 Results Code Table 165
10.1.5 Other Table Lookup Procedures 169
10.1.6 CDS Masterfile Layout 169
-------
TABLE OF CONTENTS
SECTION PAGE
10.2 Back-up and Recovery Procedures 171
10.2.1 User Responsibility for Back-up 171
10.2.2 National Responsibility for Back-up 171
10.2.3 Recovery Procedures 172
10.3 Computer Program Modifications 172
10.4 Microfiche Considerations 174
10.5 Minicomputer Edits 180
10.6 Archiving 180
10.7 Formal Reporting 181
11.0 STATE ENFORCEMENT SYSTEMS 186
11.1 State Enforcement System Options 187
11.2 State Enforcement System Usage 189
11.3 Summary of State Enforcement System Options 200
12.0 DOCUMENTATION UPDATES 205
13.0 HEADQUARTERS GUIDANCE 206
APPENDIX A - CDS DATA ELEMENT DICTIONARY
APPENDIX B - CONTACT LIST OF CDS USERS
-------
LIST OF TABLES
SECTION PAGE
6-1 Keypunch Instructions Data Required on all 58
Cards
6-2 Keypunch Instructions for Card Type 1 59
6-3 Keypunch Instructions for Card Type 2 60
6-3A Keypunch Instructions for Card Type 3 61
6-4 Keypunch Instructions for Card Type 5 62
6-5 Keypunch Instructions for Card Type 7 63
6-6 Keypunch Instructions for Card Type 4, 6, & 8 64
7-1 Edit Error Messages 70
8-1 Update Error Messages 92
9-1 Retrieval Package Edits 153
9-2 Retrieval Package Error Messages 156
11-1 Region I's Enforcement Systems 190
11-2' Region II's Enforcement Systems 191
11-3 Region Ill's Enforcements Systems 192
11-4 Region IV's Enforcements•Systems 193
11-5 Region V's Enforcements Systems 194
11-6 Region VI's Enforcements Systems 195
11-7 Region VII's enforcements Systems 196
11-8 Region VIII's Enforcements Systems 197
11-9 Region IX1s Enforcements Systems 198
11-10 Region X's Enforcements Systems 199
-------
LIST OF FIGURES
FIGURE t PAGE
4-1 Edit Program Flow Chart 18
4-2 Update Flow Chart 22
4-3 Masterfile Hierarchy 25
4-4 Retrieval Flow Chart 31
6-1 Card Layout Format 36
6-2 Sample Coding Sheet 38
6-3 Sample of a Completed Coding Sheet for a 48
New Facility
6-4 Sample Completed Coding Sheet for Change 54
Transactions
6-5 Sample completed Coding Sheet for Delete 57
Transactions
7-1 Sample Edit Report 73
7-2 CDS Edit Job Control 75
7-3 Using Edits Dummy Option 76
7-4 Input from Tape 77
7-5 Saving the Reject File 78
7-6 Printing the Reject File 79
7-7 Submitting Input via WYLBUR 80
7-8 Sample WYLBUR Session to Convert Retrieval 85
Output into Input to CDS Edit
8-1 Sample Update Report 94
8-2 Contents of Update Status Log 95
8-3 CDS Update Report Job Control 96
9-1 Quick Look Report with Data Suppressions 102
9-2 Double Spaced Quick Look 104
9-3 Source Data Report 106
9-4 Sample Milestone Report 108
9-5 Variable Milestone Report 110
9-6 Sample Questionnaire 112
9-7 Action Summary Report 114
9-8 Sample Compliance Action Report 115
9-9 Sample PSD Report 118
-------
LIST OF FIGURES
FIGURE #
9-10 Report Request Form 120
9-10A Mailing Label Job Control 123
9-11 Retrieval Request Form to Obtain Quick Look 140
Report
9-12 Retrieval Request Form to Obtain Source Data 141
Report
9-13 Retrieval Request Form to Obtain Milestone 142
Report
9-14 Retrieval Request Form to Obtain Variable 143
Milestone Report
9-15 Retrieval Request Form to Obtain Questionnaire 144
9-16 Retrieval Request Form to Obtain Action Summary 145
9-17 Retrieval Request Form to Obtain Compliance 146
Action Report
9-18 Retrieval Request Form to Obtain PSD Report 147
9-19 Retrieval Job Control 149
9-20 Retrieval Job Control for Multiple Copies 150
9-21 Retrieval Job Control for 100,000 Lines of 151
Output
9-22 Retrieval Edit Report 155
10-1 County Code Table * 160
10-2 Sample Personnel Table 163
10-3 Sample Action Table 167
10-4 Sample Results Code Table 168
10-5 Masterfile Layout 170
10-6 Micrographics User Information for CDS 175
10-7 CDS Microform Input 176
10-8 CDS Microform Output 177
10-9 CDS Microform Page Breaks 178
10-10 Microfiche Job Control 179
10-11 Job Control for CDS/FRS Link 184
10-12 Sample Milestone Report Produced by CDS/FRS 185
Processing
-------
1.0 INTRODUCTION
This Compliance Data System (CDS) User's Manual is designed to be
the primary source of user documentation regarding CDS. It replaces
previous documentation, which should be discarded.
The 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 and System Applications.
Current Users who generally understand'CDS will wish to skip to
specific sections of interest, particularly Sections 7, 9, 10, and 11,
Edit Processing and Retrieval Processing, which reflect recent changes
due to changes at the Washington Computer Center.
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
Preparation.
From time to time, revisions to the User's Manual will be issued,
e.g. an addendum for headquarter guidance revisions, new SIGNON 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 the Manual wish to thank the National Data Bank
Coordinator (Franklin Smith) and other members of the DSSE and EPA
region Offices who provided valuable assistance. Comments and
suggestions should be directed to Franklin C. Smith at 202-755-0103.
Revised 12/79
-------
2.0 MANAGEMENT OVERVIEW
The Compliance Data System (CDS) was developed for the Division of
Stationary Source Enforcement (DSSE) by The Research Corporation of New
England (TRC). The primary purpose of CDS is to assist the Environmental
Protection Agency in carrying out its enforcement and surveillance pro-
grams.
CDS provides users with an effective tool for managing large quan-
tities 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 enforce-
ment activities of all major and many minor sources of stationary air
pollution. Output reports from the system enable management to:
(1) Maintain a complete inventory of facilities emitting regulated
pollutants, (2) Assess enforcement strategies, (3) Monitor state and
regional enforcement activities, and (4) measure compliance and enforce-
ment progress.
2.1 Background History
CDS was developed by TRC for the Division of Stationary Source
Enforcement in 1972 to assist EPA's Regional Offices in implementing
their enforcement programs. The primary objective of EPA's stationary en-
forcement program is to bring about compliance with Federal and State emis-
sion requirements as stated by the State Implementation Plans (SIP), the New
Source Performance Standards (NSPS), and the National Emissions Standards
for Hazardous Air Pollutants (NESHAPS). State Agencies and EPA's Regional
-------
Offices have coordinated their efforts to develop an enforcement manage-
ment system which will ensure compliance with the emission limitations
for all regulated pollutants.
CDS has been in operation for nearly seven years. Experience with
the system has led to modifications and refinements of CDS which are
described in detail in this documentation. During the six years of
regular production runs, CDS has grown into a system widely used by all
ten regions and numerous states.
2.2 System Purposes
Regional offices are using CDS in a number of ways in their enforce-
ment 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 regula-
tions and their compliance status with respect to these
regulations.
2. Develop enforcement strategies by providing summaries of
the compliance status of facilities tracked by CDS.
3. Provide a means for tracking numerous federal, state, and
local enforcement actions both for historical purposes and
for future scheduling purposes.
4. Assist the region in the preparation of various national
reporting requirements.
5. Provide various turnaround reports to be used by states in
fulfilling 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.
Revised 12/79
-------
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; it provides
information about the compliance status of these facilities; and it helps
to track the enforcement 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 elements which can be defined according to each regional
user's needs. Since CDS can accommodate 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.
CDS's retrieval capabilities are highly flexible. Users can obtain
reports based on all data on the CDS Masterfile or on only that portion
of the data which meets user selection criteria. There are four fixed-
format reports as well as two flexible format reports which can be
designed to fit any particular 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
* Hevie~- 12/79
-------
appear in any desired sequence. Because of this flexibility, CDS has
been able to adapt easily 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 Computer Network Corporation (COMNET). All
regional users have computer terminals connected via telephone lines to
COMNET's computers.
Input transactions prepared by regional users can be transmitted at
any time to the central computer facility. Once there, transactions are
validated by the Edit program. Valid transactions are stored for further
use in the Update Cycle, and an Edit Report showing the Edit's action on
each input transaction is returned to the user's terminal once the com-
puter has executed the Edit program. Under normal operating conditions,
one hour turnaround is available for the-data submission procedure util-
izing 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 Data Bank Coordinator (DEC)
to run once a week on Wednesday nights. During periods of very high data
entry activity,especially at the end of each quarter, more frequent updates
may be scheduled at the discretion of the DBC.
Revised 12/79
-------
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's 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 had input data, the DBC will run each region's Update
Report, as described in Section 8.
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 conditions, quick turnaround is available for short
retrievals.
Regional users are responsible for data submission and retrieval
requests. 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.
2.5 System Relationship to Other EPA Systems
Although CDS has a coding structure compatible with a number of EPA
systems 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
parametric emission data for sources of air pollution; CDS contains compliance
and enforcement data for facilities. CDS uses the NEDS facility numbering
Devised 12/79
6
-------
for a majority of its facilities and the SAROAD geographic codes for all of
its facilities. In addition, the NEDS source number is carried as a retriev-
able 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
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.
-------
3.0 SYSTEM APPLICATIONS - What can CDS do for you?
CDS is a management information system designed to track large quan-
tities of 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 respon-
sible 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 cap-
ability for details about them.
2. Develop counts of various types of facilities which are in
compliance, out of compliance, and of unknown compliance
status with state, local and federal regulations. CDS
provides both milestone (summary) reports and listings of
facilities falling into the various compliance categories.
3. Monitor a wide variety of enforcement actions. CDS can track
enforcement actions scheduled into the future and also it
can provide an 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 New Source Performance
Standards, 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 pro-
vide highly effective turnaround documents used by states for
providing the region with new or additional enforcement infor-
mation.
8
-------
6 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.
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:
o 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.
o 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. Sub-totals and totals
:an be developed on any user-selected criteria.
CDS can identify sources inspected ty regional and/or state
personnel in both attainment and non-attainment AQCR s.
CDS can list the enforcement actions taken, or about to be taken,
by the 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 region has determined
what actions it wishes to track in CDS, CDS can provide users
with a history of past actions and also a schedule of actions
to be performed.
CDS can be used to prepare milestone reports and lists of facil-
ities subject to SIP regulations, NSPS regulations, NESHAPS
regulations and PSD regulations.
CDS can be used to prepare industry studies or summaries based
on the Standard Industrial Class Code (SIC) or on the Standard
Classification Code (SCC) for certain processes.
o
-------
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.
In one retrieval, sources can be selected by State, AQCR, City,
and/or County, industrial category, emission size, pollutant, SIP regu-
lation 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 com-
pliance 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 information.
For example, if he needs to have a list of major sources of air pollution
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.
10
-------
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 1,000. 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 Region 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 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 overview 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.
H
-------
CDS can also print out a special list of facilities of unknown
Compliance status. A State can be sent a printout for further informa-
tion on the listed sources. If the State does not provide the informa-
tion in the requested reporting time, EPA can use the same list to
initiate a field inspection program to resolve the Compliance status.
CDS can be used to follow-up on sources out of Compliance. CDS
can provide a printout of the .problem facilities. EPA can then assign
a priority ranking to these facilities for future actions.
When an order is issued by EPA or a court, follow-up is essential
to ensure that the required steps in the order are achieved. CDS's
tracking system can be used for monitoring State Compliance schedules
to relieve Program Managers of the burden of increasing numbers of
Enforcement actions and increments of progress.
By entering all enforcement actions and scheduled field activities, CDS
becomes a tool that can assist personnel at all levels of environmental
enforcement. Project managers can determine the workload facing their staff
during a coming month by obtaining a CDS report on all EPA actions 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 turn-around documents, eliminating the
need for special reporting forms.
Revised 1/80
-------
4.0 SYSTEM OVERVIEW
The Compliance Data System provides regional users with the ability
to store, update, and retrieve large quantities of data necessary for
running an enforcement program. To meet these objectives, CDS has been
designed 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 headquarter responsibilities include the following:
o Developing and maintaining all CDS programs, data sets, and
table values.
o Scheduling all update cycles.
o Providing definition and usage of all nationally controlled data
elements.
o Establishing retrieval guidelines for meeting national reporting
requirements.
o Providing user training for any region requesting training.
o Responding to regional requests for system modifications.
o 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.
13
-------
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 accept-
able to the Edit Program. There are eight fixed card formats available
to the user for preparing 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 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. One or more fatal errors will prevent
a transaction from being saved for the Update Program. A transaction
with only warning 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 that 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, des-
cribed in detail in Section 6, that are validated by the Edit Program.
These cards provide the following general information:
o Cards 1 and 2 provide facility (source) level data for this system.
o Card 3 provides pollutant compliance data for the facility.
o Card 4 is a facility comment record which provides additional
information about the source.
o Card 5 provides descriptive emission point data for various
pollutants.
o Card 6 is a point comment record which provides additional
information for a given emission point.
o Card 7 describes specific enforcement actions for a given
emission point.
o Card 8 is an action comment 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
processed 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 asterisk preceding the error message; for example,
*INVALID POLLUTANT CODE. Fatal errors will have three asterisks preceding
the error message; for example, ***INVALID STATE CODE. The data element
in error will have asterisks directly beneath it on the Edit Report print-
out line. A transaction with multiple errors will have multiple error
messages.
is
-------
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. 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 con-
tain the new value. Other data elements, such as Region, State, Compliance
Status, Emission Category, etc., are validated by internal computer tables.
These edits can be changed only by changing the Edit Program logic. Only
the national DBC has the authority to change these edits.
Although the Edit examines all input transactions for possible key-
punching and coding errors, the program has i'ts 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 Masterfile. The Edit cannot detect certain errors caused by
punching data into the wrong card columns; if a valid date is placed in
the Date Achieved columns, but the user meant to place the value in the
Date Scheduled columns, the Edit will accept the data element as valid.
16
-------
Even those transactions containing 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
consists of the various input card formats together with the appropriate
Job Control Language 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:
o The Edit Report.
o The MOD Hie 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.
o An Edit Log showing statistics, such as cards input, cards
accepted, and cards rejected. These numbers are printed at the
end of the Edit Report.
o An optional Error File containing 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.2.2. Typical error messages
are listed below.
FATAL WARNING
*** INVALID STATE CODE * SIC CODE SHOULD BE NUMERIC
*** LINE NUMBER MUST BE NUMERIC * INVALID SIP CODE
*** DO NOT DELETE 000 * INVALID POLLUTANT CODE
Revised 12/79
17
-------
FIGURE 4-1
EDIT PROGRAM FLOW CHART
INFORMATION
FROM FEDERAL,
STATE & LOCAL
AGENCIES
\f
VCODING AND
\ KEY-
PUNCHING
INPUT DATA
CARD TYPES
1-8
EDIT
PROGRAM
\/
ALL TABLES ARE
MAINTAINED BY THE
NATIONAL DEC
CDS
PERSONNEL
TABLE
CDS
ISAM
TABLE
COUNTY
CODE/AQCR
TABLE
V
EDIT
LOG
MOD
FILE
EDIT
REPORT
ERRORS
(DUMMY)
TO
NATIONAL
DEC
TO
UPDATE
CYCLE
TO
REGIONAL
USER
CAN BE
PRINTED
OR SAVED
BY USER
-------
Valid values which can be entered on the card formats for each data
element are listed in Appendix A. Each Data Element Sheet lists the
appropriate coding values and coding considerations necessary for pre-
paring 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 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 submis-
sion adds additional data to the MOD file. At the beginning of the next
update cycle, the data on the MOD File is copied to magnetic tape. Then
the transactions on the file are sorted into Region, State, County,
Source, Point, and Action Number order. Within this major sort key,
transactions are also sorted by Update Code and by chronological order.
For transactions with the same record ID (Region, State, County, Source,
Point, and Action Numbers), delete transactions are applied first, then
new transactions, and finally change transactions. For transactions with
the same record ID and the same Update Code, transactions 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 submission. With the MOD File, input transactions do not overlay
19
-------
previous submissions; 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
necessary to resubmit the transaction again when additional transactions
are being submitted for the same update cycle. However, the user should
keep input transactions on cards or other information storage devices for
at least one 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 Data Bank
Coordinator (DEC). Input to the update is the old (preceding week's)
Masterfile and the week's input transactions placed on the MOD File by
the Edit Program from all regional users. Output from the Update is an
updated Masterfile and ten regional Update Reports.
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 trans-
action 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 trans-
actions perform the following functions:
NEW When an Update Code "N" is used in the Update Code Column,
the input transaction will add a new facility, point,
action, or comment record to the CDS Masterfile.
CHANGE The Update Code "C" is used to change one or more data
elements on an existing Masterfile record.
DELETE The Update Code "D" is used to delete one or more Master-
file records for a given facility.
4.2.2 Update Cycle Steps
In addition to applying input transactions to the CDS Masterfile,
a number of other steps are taken in each update cycle:
o Input transactions from the MOD File are saved on tape.
o Input transactions are sorted into the same sequence as the
Masterfile.
o A number of table lookups are performed during the Update.
o The CDS Masterfile is copied to ten regional disk Masterfiles.
o The MOD File transactions are erased to make room for the next
cycle's input transactions.
Figure 4-2, Update Flow Chart; 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
Revised 12/79
-------
FIGURE 4-2
UPDATE FLOW CHART
THIS
CYCLE'S
OUTPUT
MASTERFILE
BECOMES
NEXT
CYCLE'S
INPUT
MASTERFILE.
L _
COPY
MASTER TO
DISK
/ :
10
REGIONAL
I DISK
MASTERFILES
10 REGIONAL
UPDATE
REPORT
FILES
I
I
PRINT
REGIONAL
REPORT
ON USER
REQUEST
UPDATE
REPORT
-------
ADDED, CHANGED, or DELETED and indicates 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.
o SOURCE NOT ON FILE
o POINT NOT ON FILE
o DUPLICATE TRANS
o ALREADY ON MASTERFILE.
When an ampersand appears in the Error Message column, it indicates
that multiple changes have been applied to the Masterfile in chrono-
logical 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 trans-
action. The following values are used:
ORIG Origin
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.
Revised 12/79
23
-------
4.2.4 The CDS Masterfile
The CDS Masterfile resides on magnetic tape. It contains data for
stationary sources of air pollution for each of the ten EPA regions using M
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 card type is placed
on one of 7 Masterfile record formats. These Masterfile record formats are
numbered 20, 21, 30, 34, 35, 46, 47 for internal computer identification purpos
The 7 Masterfile record formats contain the following general information-
o Record 20 contains facility level data from Cards 1 and 2.
Each facility has one Record 20. Region, state, county,
and source numbers identify a unique facility.
o Record 21 contains comment information for the facility
record. Up to ten comments may be used for each facility.
Each Card 4 added to the Masterfile creates a corresponding
Record 21.
o 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.
o Record 34 is an emission point record created from the Card 5
input transaction. For a given facility there may be up to
1,000 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.
o Record 35 contains comment information for an emission point.
Each emission point may have up to ten comments. Each card 6
added to the Masterfile creates a corresponding Record 35.
o Record 46 is an action record created from the Card 7. For a
given emission point there may be up to 98 actions; each is
identified by a sequential Action Number.
o 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.
Revised 12/79
24
-------
Region, State, County,
and Source Number
Provide a Unique
Facility Identifier
Coanents
Point 00£ contains
compliance Data
for the Entire Facility
Up to lfS0fJ point
per facility
\ctions for
point 000 refer
to action for the
eiitJ e factU
FIGURE 4-3
MASTERFILE HIERARCHY
-------
4.2.5 Regional CDS Masterfile
In one of the last steps of the Update Program, the update CDS
Masterfile is copied to create 10 separate regional Masterfiles, 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 region. All
retrieval requests are based on the data contained on the regional
Masterfiles.
Users should note that input transactions processed by the Edit are
not retrievable until after the transactions have been applied to the
regional Masterfiles by the update cycle.
4.3 Retrieval Program
The CDS Retrieval Program is used to prepare management reports
based 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 available on request from the Retrieval Program.
These requests may be made at any time since they are processed
independently of the Update Program. The Retrieval Program will pro-
duce the following management reports:
o Source Data Report
o Action Summary
o Questionnaire
o Milestone
o Quick Look Report
o Double Spaced Quick Look Report
o Compliance Action Report
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
Revised 12/79
£6
-------
is also determined by the user to meet his needs. This section briefly
describes the principal 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
reports 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 elements. For example, management
may need a report showing only the name, address, and compliance status of
all the 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. Not only can users select via the Retrieval's selection logic what
facilities should appear on a report, but also they can select the data ele-
ments to be printed for these selected sources. Up to fourteen specified
source» point and action data elements for a facility may be included on a single
print line so long as this print line 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 particular problem. The Quick
Look Report can be used as a forecast report, a turnaround document, or what-
ever management report the user has a need for. This report can produce
totals, subtotals, and pagebreaks as needed.
A variation of this report is the Double Spaced Quick Look which
is identical to the Quick Look except that the user obtains double
spacing. This feature is especially useful when the Quick Look is
used as a turnaround document.
Revised 12/79
-------
Because of space limitations, comment level data is not available
on Quick Look reports.
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.
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. The
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 six-month period is selected,
the actions summarized on the report will include only those which were
scheduled during 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 Regional Office.
Questionnaire Report
The Questionnaire Report was designed for Regional 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
Revised 12/79
28
-------
which is then sent to the State Agency for completion. 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 Compliance 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 Milestone Reports provide Regional managers with a
means to meet National Reporting requirements. The variable Milestone
provides a tally of any two user-specified data elements in the system.
For example, users may need a count of all action types by month
achieved, a count of all SIC descriptions by AQCR, and a count of sources
within a county by major and minor emission categories. 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 Masterfile. Source
level information and compliance information is listed on one print line
with the date achieved for the following actions:
o Inspections
o Notices of Violation
o Orders Issued
o Court Actions
o Terminations of NOV's
Revised 12/79
-------
Because this report has been designed to meet specific enforcement 4
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 consti-
tuting the Retrieval:
o Retrieval selection cards are checked for validity. An Edit
Report page is printed to show the logic used in preparing
the Retrieval.
o CDS regional Masterfile records which satisfy all of the user's
selection criteria are placed on a temporary extract file.
o Extracted records are sorted into a user-specified sort order.
o Sorted records are formatted for printing into user-specified
print formats.
Figure 4-4, Retrieval Flow Chart, shows this process graphically.
30
-------
FIGURE 4-4
RETRIEVAL FLOW CHART
/
REGIONAL
| CDS
\ MASTERFILE
RETRIEVAL
OUTPUT
REPORT
L USER
SELECTION
CARDS
RETRIEVAL
EDIT
REPORT
31
-------
5.0 DATA SUBMISSION PROCEDURES
5.1 Submission Steps
The following ten steps describe the procedures for using the •
Compliance Data System. 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.0. Have the coding sheets keypunched.
2. Run the Edit Program. After the CDS punch cards have been
returned, prepare the appropriate Job Control Language (JCL)
cards for running the Edit Program. The JCL for running the
Edit is shown in Figure 7-2 on page 7-9. Submit the JCL
and input punch cards to the computer. Submissions should
be made on a priority basis since the Edit is inexpensive
to run (approximately $2.00 per 1,000 cards with PRIORITY
=5 ). With a priority, the Edit will run prior to the
update cycle, and thus the input data will be applied to
the current 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 errors on the input data. All transactions submitted
to the Edit are listed on the Edit Report; transactions which
are error-free 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 on page 7-6. 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 pro-
cessing 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
preceded by three asterisks (such as "*** INCORRECT COUNTY
CODE FOR STATE"). One or more fatal errors on a transaction
will prevent that transaction from being placed on the MOD
File, and consequently, the transaction will not reach the
update cycle.
.32
Revised 12/79
-------
Table 7-1 gives a complete list of all errors identified by
the Edit Program.
For both warning and fatal errors, asterisks are placed direct-
ly underneath the data element found to be in error. These
asterisks are designed to identify the data element which needs
to be corrected.
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, key-
punched, 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 are 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. Once 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 impor-
tant for users to have all of their weekly input ready on or
before Wednesday noon.
The scheduling and the maintenance of the update cycle is the
responsibility of the national Data Bank Coordinator. Under
unusual circumstances, the update cycle may be run more often
than once a week. When holidays prevent a Wednesday night up-
date cycle or when a special update cycla is scheduled, the
national Data Bank Coordinator will inform all CDS users of
the schedule change.
6. Verify Update Run. The national DEC will route a copy of the
Update Report to the user's terminal by noon on Thursday. If
the user has not received his report by noon, he should verify
that the update cycle has run successfully and that the Update
Report is available for this Region. Figure 8-2 shows the data
set retrievable via COMNET under the name CN.EPAEXC.A026.CDS.SYSOUT
This data set sho«s tbe date, the time, and the output serial
number of the most recent update cycle. It shows which Regions
participated in the update, and also it shows the number of
transactions input to the update and the number of transactions
accepted and rejected by the update for each Region.
Revised 12/79
33
-------
7* Examine Update Report. 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
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-1 for a sample Update Report.
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- Req"est Management Reports. CDS can produce the following manaee
ment reorts: &
ment reports:
o Quick Look Report
o Milestone Report
o Source Data Report
o Questionnaire
o Action Summary Report
o Compliance Action Report
s: "u"sult section 9 f°r
34 Revised 12/79
-------
6.0 DATA INPUT PREPARATION
6.1 General
All input data to the Compliance Data System (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 following data elements are unique for each card code:
Card Code 1 Card Column
* AQCR 20-22
City Code 23-26
* Facility Name 27-46
Street Address 47-56
Regional Data Element 1 67
Regional Data Element 2 68
Regional Data Element 3 69
Regional Data Element 4 70-74
Regional Data Element 5 75-79
Card Code 2 Card Column
* City Name 20-34
Zip Code 35-39
State Registration Number 40-54
* NEDS Cross Reference 55-58
* SIC Code 59-62
Federal Facility Code 64
Air Program Code 65
Air Program Status 66
Regional Data Element 6 67-76
Staff Personnel Code 77-79
* These data elements should be filled in when a new transaction is
being added to the Masterfile.
35
-------
CARD 4.6.8
Region
State
" County
s
- Source
PO
s Point
I! Action
o Line //
M
•0
-J
—
S
g
£
s o
ft 3
S rt
£ *
u>
s
a
SC
S
S
u
s
s
s
5
a
"
s
8 Update
CARD 7
~ Reeion
„ State
" County
f Source
s; Point
s
^ Action*
SO co o
hi fl) 13* *T3
*** CD O rr
-j O H»
S
8
S
S
«
£ H-
* fe1
£
a
£
^ B m
S §3
£ c (1)
g 3 H4
u*
a
zAct type
a >
K 0
s 3*0
(D H- PI
s a, rt) rt
s J
m CO
M C 0 «
S M ET* (b
*" G. Q. (D
s Staff
^Results
tn r**
» ^
a
8 Update
CARD 5
.«•. Regdon
" State
" County
0
~ Source
= Point
r Action*
"s Card code
-—
S S*
St fP
-J
*
y I^MST
- slP
5 PLUT
pd h^
b! (B (B
u TO a.
c n>
=3 t-1 M
S rt HJ
u> H- .
^ 3 rt
B
S B5 rt
£ §• r?
a mo
0j
£ ECAT
S
C
* S
01 CO
S en
O)
""I O
S (D
2 H-
S "S
. »
S
a
5 MULT
3 XREF
-S— KDE / _
8 Update
" **
Z Region
" State
» County
o
- Source
Kl
s Point
~ Action*
H Filler
E Prap -a
a JfLT" CMSTo"
a iU.T ECJATf
3 EH AQMAe
s PLT'TOCR'^
UJ 2
s Plut rt
a Indicator
t:
a Pollutant
s urop g»
5 PLT CMST^
* FJLT ECAT^r1
» i-J_T AUMAS.
*> PLT AytKw
I Pit rt
*sl
£ Loading to
f Indicator
s
i Pollutant
s ]j 'pp ^
asrji
3p1i-j
= PLT AQMA£
£ Pit S
s Loading <-°
* Indicator
£
S
s Facility
~ Capacity
s
E
"•
K
S RDE 9
s
2 RI'E 10
a M^E 11
- KJ)JJ Li
~ Filler
3
8 Update
"Region
"State
" County
~ Source
s Point
r Action*
-§
a
K
x o
» rt
^3 r^
s i
8 m
S
K
j;
Si
8
a Zip code
g
s
& CO
e fl>
* §?.
£ (D 00
* M M
S "^
^ 0
X O
K
* NEDXR
if
8
z SIC
S
S Mil OT
2FSD-FACIL
«* APrTD
K AP5T
S
S
S —
s g
**» o\
V
»
a
" STAFF
I Region
" State
Ot
" County
(O
f Source
5 Point
r Action*
s ^ara cooe
i! AQCR
S3
B
•-> tdty
st Code
a
*v
w O
" H
iS 0
K ">
S §
" fl>
K
Si
&
iS
fi
£
ft
ft
^j
g
s co
S f*
2 H
K S
i I
u> (^
!£ S
S 0)
£
S
s
s
S!
Sri
S RDE 1
S RDE ^
0
S w
^ ^
S g
a B
w
3
jj Cn
n
o
CO
»
o
§
O
O
i
-------
Card Code 3
Card Column
Pollutant - ID
Delete Flag
Pollutant Compliance
Pollutant Emission Category
Pollutant Air Quality Main-
tenance Indicator
Pollutant Air Quality Con-
trol Indicator
Pollutant Loading
Facility Capacity
Regional Data Element 9
Regional Data Element 10
Regional Data Element 11
Regional Data Element 12
22, 34, 46
24, 36, 48
25, 37, 49
26, 38, 50
27, 39, 51
28, 40, 52
29-33; 41-45; 53-57
58-69
65-71
72-73
74-75
76
Card Code 4
* Comment Line Number
Source Comments
Card Column
20
21-79
Card Code 5
SCC Code
Capacity Code
* Compliance Status
* SIP Code
* Pollutant
State Regulation Number
* Emission Category
Process Description
Multiple Cross Reference
Regional Data Element 7
Procedural Compliance
Card Code 6
* Comment Line Number
Point Comments
Card Code 7
Penalty Amount
* Action Type
Date Achieved
* Date Scheduled
Staff
Results
Card Code 8
* Comment Line Number
Action Comments
Card Column
20-27
28-29
30
31
32-33
34-48
49
50-74
75-77
78
79
Card Column
20
21-79
Card Column
46-52
53-54
55-60
61-66
67-69
70-71
Card Column
20
21-79
These data elements should be filled in when a new transaction
is being added to the Masterfile.
37
-------
i i. 'HI
mn
olo
imc iw":||
COMPLIANCE DATA SYSTEM CODING SHEET
ill !U U
liltilvtKl iMi/|Hi|MHn[ii
M[«ll1ll4?IH['11|4lifu"
T2I1I
simif i
sqjr
vipi
ti ii k'
(I // n yii ii
liiTiT
T5EH1IJM1 3
WlliflJ
Kii.isiKAlioN
0
0
'7?M
fafl
63JZ1
ifl&llii
LL
l£Jlf niiyiiB:
OlO 010
;V ii!
IM)IU\
wluft
'•'"
IT
IAUI l|« rAI'AI lir I RDI 9
c
~ ji it n u
00000
I'1" '« smwu nimiiiis
yi<^iJia|2^2yd?I?!i|^w|i!i:tfl^iJ.^.ffiIlZJw|^
J0|0|0|0|0
I I H I I HI I H II H H I H H I H I I I IIN I I I I I n I I I ii II I I I I I i i i I ii I I
•.re u»i( fAPc j]-?i PIUI
SIAll Klf.lllMIOH
fen
ffli
TTIS
I I
11
Ii
11
niiin MIIIII
11
ii nun
11
IIII'A Hill
•Dim n»
Q|oH I I I I I t I
11
Lij?jJ;j!ppjiZ
l!H','jKill I'unii < mm
IminmniniiiiiiiHi
iJUlliliijlillillJil^'^iLill^^^ibMiiJylijMEr
.U 11 t. It !i JS 3i !!! 11 !ilU
f^ "ST 57
)(,|;>|;u|/.
11J^
nn i mi ii in i in ii n 11 n i ii i n ii 11 n ni nn ii 111111111 ii
I HIS',Hill A( 11(111
•Ollll IK) IW
.f MlSSIOli
B
iTTir
(H'tiunfit A( i Kin i
IIMIl HUH All'l
I I I I I I I I I I I I Ii
J M I I
" ll'"'l I <\
_\V_\ I I , ^-
I I I I I I I I I M
I I tit (HI
I I'lllAII)
mam
M.I ION BI'.IJIIS
I'lllAlir Wll ,„., DAI I AUMIVID OAlf SCIIIUUIIU SIAII
xi i
3T3
'.i: 'j9 'M
II I I II I
1 1 1
11
TuFT
77m
'i|;j,
^J^1
IT
FIGURE 6-2
SAMPLE CODING SHEET
-------
Actual data preparation is performed using coding sheets or a special
data entry form. Data preparation techniques will vary from one regional
office to another, and a variety of input formats will be developed. A
suggested 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 formats only, depending on the frequency of specific
types of input data.
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 the user is urged to familiarize himself
with the complete listing provided in Appendix A.
The sections which follow describe the specific procedures to be
followed 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 80 for each card
type needed to create a Masterfile 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 New 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
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
separate source number is assigned for each affected air program.
Revised 12/79
-------
To establish a new facility on the Masterfile, perform the following
steps:
1. Request a Quick Look Report with the CDS Retrieval Package to
verify that the facility being added is not already on the
Masterfile.
2. Select a County Code/Source Number combination which will iden-
tify the facility by a unique number. The NEDS source numbering
convention should be used wherever possible 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 generated 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 system.
4. Code Source Name, columns 27-46. If additional data elements
unique to Card Type 1 (See 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 Masterfile 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.
2. Code columns 20-34 (City Name) and columns 59-62 (SIC codes).
If additional data elements unique to Card 2 (see Appendix A)
are available, 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.
Revised 12/79
40
-------
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, S02, HC, CO, and N0y in non-attainment
air quality control areas, the CDS system must carry a number of data
elements which indicate worst-case compliance for each pollutant produced
by a facility contributing to the non-attainment status of an AQCR. The
pollutant information on the Card 3 replaces the functions of AIR2 and
RDE1 as non-attainment indicators.
Card 3 data must be coded for all SIP sources impacting or of unknown
impact on non-attainment standards. Both major (Class A) and minor
(Class B) sources contributing to the non-attainment status of an AQCR
must have Card 3 information for all regulated pollutants they emit. It
is not enough to code in only the non-attainment pollutant(s). However,
unregulated pollutants or pollutants not emitted by the facility should
not be entered.
For each pollutant produced by a facility in a non-attainment AQCR,
the following data elements should be added to CDS:
Data Field Length Coding Considerations
Update Code 1 Must be a "C" for all Card-3
transactions, whether a user
is adding or changing data on
this card.
Pollutant ID 2 Must be coded for each pollutant
produced by the facility. Valid
values are the same as for the
Pollutant code on Card-5.
Pollutant Compliance 1 Must be coded for each applicable
pollutant. This compliance status
should represent the worst-case
compliance of all the emission
points producing that particular
pollutant. Valid values are the
same as for Compliance Status on
Card-5.
Revised 12/79
-------
Data Field
Pollutant Emission Category
Length Coding Considerations
1 Must be coded for each applicable
pollutant. Valid values are the
same as for Emission Category
on Card 5. This must re-
present the potential uncontrolled
emissions for the pollutant.
Air Quality Maintenance
Indicator
May be coded for facilities af-
fecting AQMA standards as
defined in 40 CFR, Section 52.22
entitled, "Maintenance of National
Standards". Code "Y" if source is
located within an AQMA, Otherwise
leave blank.
Inpacted AQCR Indicator
Must be coded as follows:
a. Leave blank or enter on "A"
if the facility does not
contribute to the non-attainment
status of the AQCR for this
polluntant.
b. Code "N" if the facility im-
pacts the emission standards
for this pollutant in a non-
attainment AQCR.
c. Code "U" if the impact of this
pollutant on the non-attain-
ment status of the AQCR is
unclassified.
Pollutant Loading
May be coded. If it is used, it
must be a numeric field represent-
ing actual tons per year.
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 "C" for adding,
changing, or deleting pollutant data. Because a facility can produce
numerous pollutants, the input punch card has room for three sets of
Revised 1/80
-------
pollutant data. Multiple Card 3's may be used to enter pollutant compli-
ance data for facilities producing more than three different pollutants.
Up to ten 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, S02,
HC, CO, and NO are always 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 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 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-KDE12 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.
See Table 6-3A for a complete list of all data elements on the Card 3.
Refer to the appropriate pages of Appendix A for detailed definition and
guidance on each individual data element on the 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 Masterfile.
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 a Source Data Report for that facility to determine what
line numbers have already been used. A Card Type 4 comment must
have a valid line number. The update code N can be used only
when the comment line number is not on the Masterfile. Keep
in mind that comments are not retrievable and cannot be printed
on a Quick Look Report.
3. Code "A" or "3" in line number to indicate a mailing address
if it is different from the street and city on Cards 1 and 2.
Revised 12/79
44
-------
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 correspond to the NEDS emission point number
while the third digit is pollutant specific. Thus, if a boiler produces
both particulates and sulphur dioxide and has a NEDS point number 01,
the CDS point number for particulates might be 010 and the SO point
number might be 011. For each facility, there can be up to 1,(
emission points.
Point 000 contains compliance status and emission category inform-
ation for the entire source. A point 000 transaction can be entered into
the CDS with an Update Code "N" only at the same time that Card Type 1
is entered as new. Card Type 1, the system will generate this point number
automatically. Consequently, point 000 information added to the Masterfile
after Card Type 1 has been added must use an Update Code "C" in column 80.
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
physical 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 third
digit. When adding new additional 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 (See Appendix A) are available, they sho'uld
also be entered at this time.
45 Revised 12/79
-------
Card Type 6 is a comment card used to add additional 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 informa-
tion. A point comment cannot be added to the Master file unless a corre-
sponding 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 respon-
sible for defining the actions which will be tracked by CDS. Regions must
obtain clearance from the National Data Bank Coordinator for new Action Types
codes and descriptions. The National Data Bank Coordinator maintains a table
which relates the Action Type to the Action Description.
1. Code columns 1-19 (Region, State, County, Source Number, Point,
Action Number, and Card Type) and the Update Code "N" in
column 80.
Action Numbers (columns 17-18) should be assigned seauentially
starting with 01. When adding a new action to the Masterfile,
Action Number 99 could 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
number must be associated with a specific emission point.
I/SO
46
-------
2. Code columns 53-54 and 61-66, Action Type and Date Scheduled.
Consult the regional action table for Action Type. If neces-
sary, call the central Data Bank Coordinator 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 (See
Appendix A) if they are available.
Card Type 8 is a comment card used to add additional 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 avail-
able on Card Type 8; up to ten 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. However, an action' comment cannot be
added to the system unless there is a corresponding action record already
in the Masterfile.
1. Code columns 1-19 (Region, State, County, Source Number, Point,
Action Number, 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 that facility to determine what
line numbers 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 New Facility
Figure 6-3 is a sample coding sheet used to enter a facility for the
first time on the Masterfile.
47
-------
51 I CUIllllV
5
H-
B>
s.
COMPLIANCE DATA SYSTEM CODING SHEET
ML|*NT| I I I I I I I I i i I I i i i i i
MC (01)1
-------
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 Master-
file for this 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
regulated pollutants being emitted from the same smokestack. The 020 in
the Multiple Cross-reference field (columns 75-76) for emission point 021
indicates that emission point 021 represents another regulated pollutant
for the same 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.
49
-------
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 iden-
tifier (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 other than a Card 3 if a delete or a new is being
applied for the same card type during the same update cycle. However,
the Update will process multiple changes for an existing Masterfile re-
cord. Multiple changes are 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.
Card columns 1-19 and 80 must be coded when preparing a change trans-
action. However, 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 Numbers have been added to the CDS Master-
file, 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.
50
-------
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
program 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
Edit Program.
6. Use a Change transaction, and not a Delete transaction, to
remove 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 or 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.
On the Card 7, an asterisk on Date Scheduled or on Date Achieved
will zero-fill the data element 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 Number, Point, or Action Number
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.
7. An Update Code C should be used for adding or changing pollutant
data on a Card 3. A delete transaction is not valid for a Card
3. If a user wishes to delete all references to a pollutant on
the Masterfile, he should code the appropriate pollutant code
followed immediately by a 'D' in the Pollutant Delete Flag on
the Card 3.
51
-------
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
several pollutants regardless of the order in which this data
was originally entered; all changes and adds 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 through 19 must be the same on the change transaction as they
were on the new transaction already on the Masterfile; column 80 must be
a "C" for each change transaction.
Figure 6-4 is a sample coding sheet used, to change some of the data
input 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
following text: PORTLAND CEMENT PLANT. A change for Card 4, line 4,
will replace this 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 Master-
file record will be unchanged. On Card 5, point 001, only the Compliance
Status Code will be changed on the Masterfile.
-------
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".
6'4 Deleting Data from the CDS Masterfile
A delete transaction contains a "D" in column 80, the Update Code; it
is used to delete one or more records from the Masterfile. A Card 1 delete
will remove all Masterfile records for a given facility. A Card 5 delete
will remove one emission point together with all associated comments, ac-
tions, and action comments. 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 or a Card 3 delete is invalid. Remember that if
only some of the data elements on a particular card type are to be deleted,
a "C" must be entered in column 80 and asterisks placed in these fields.
A "D" in column 80 will delete the entire card type.
ls Deleting an Entire Source. Card 1. An entire source can be
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 and all related points, actions, and comments.
2' Destine 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 point, all associated emission point
comments, actions, and action comments. A Card 5 delete for
point 000 is invalid.
Revised 12/79
53
-------
JI
SHE
0
ilia
0
0
0
HI mil :i I
oco \
COMPLIANCE DATA SYSTEM CODING SHEET
lEEai
illl J2
jl Jil«ljM»Rtlji?lto|i. iliiTBplg
OK)
MIltllLUi^Uy^l^J^l—I J!!U4 -
0
VjlifrlDIH'.pir
SlilliiMT
33
TFTfl
lOADIIC. I"!1
I p" '
q^
IOAUING
Ul'iU'&l
(•CIIIIV CAIWIIY
MBIKll IUHHINIS
omotolo
El E
nis
IB
urn
jiyiiiiiijilivijiiiaiJiUilJIil^liilte
Ppl |B|o|x| |7pP>| | | | | | | I I I I 1 I I I I I I I 1 I I I I i i i i i i i i i i i i i i i » ' i i i i i i i i pi
I II I II I I II II Ml I II I I M I II I II MM M ill llll ill I III MM II II
vt um r piui SIAII mr.iiiAiio» k! ^ PDOCISS DISOIPIIOH m ^JL^M
0|0|0|0|0
IMEIZ
Sly
ORT
iiiiiiniiiiiniiiiiniiiiiiiMiiiMiii
Jl
IMH II IMIMI III I Mi I
CA
HI-
II II M I I II I
1 I II I I I I II III I I II I I I I 111 I
11
U
a
a
SI
it
MB
I I
mi n n 1111 HIM ii i in i in MUM HIM i in 1111 in ii 11 ii I
IHIbSIIIII
flllll IK)
All lull lirllOII/U Al Illlll DIM HI I'11 (IN
iw IIMIP HUH Am
[H'SMOK
TTIiT
IL
')! 101111)2111111
JJJJ-
JirvM M I I I I I I I I I I I I
MlllW
l»l'l OAK Aril 1 1 VI D
5]5
.1.1 I
Will SCHIDUUI)
11
fill
s
Al Illlll IIIMIIIIIIS
TTIirtrT
01
S.
FIGURE 6-A
SAMPLE COMPLETED CODING SHEET FOR CHANGE TRANSACTION
-------
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 columns
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. This
is a new capability in the system and does not require the use
of asterisks.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 established
on the Masterfile by a Card 3 transaction, it cannot be deleted
unless the entire source is deleted. However, all references to
any particular pollutant can be deleted by placing a D in the
Pollutant Delete Flag. If all data for a pollutant is to be
deleted, only the Pollutant Code and the Pollutant Delete Flag
may be coded for that particular pollutant.
On one Card 3 transaction it is possible to delete all data for
one pollutant, change some data for another, and add new data
for a third pollutant.
Once a pollutant has a D in the Pollutant Delete Flag, that
pollutant and all related data will not appear on any output
reports. After a pollutant has been deleted, it may be reacti-
vated by entering new data for it.
By preventing users from deleting the entire Pollutant Record,
the danger of accidentally losing data for many pollutants is
eliminated. Coding errors can still be corrected, and unwanted
data will never appear on any output report.
6.4.1 Sample Completed Coding Sheet for Delete Transactions
Masterfile records may be deleted from the Masterfile by. placing
the same numbers in columns 1 through 19 as the new transaction used
to establish that record on the Masterfile. When an Update Code "D"
is placed in column 80, no other data may be coded in columns 21
through 79.
55
-------
Figure 6-5 shows three delete transactions and one change trans-
action. A delete for emission point 040 will remove that emission
point and all associated 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 0 10 action 02 will delete one action
together with any associated action comments.
To remove some data from a Masterfile record without removing the
record from the Masterfile, use an Update Code "C"; code an asterisk
in each field which is to be removed. In the example, a change trans-
action for emission point 020, action 01 will blank out the Results
Code 01 on the Masterfile because there is an asterisk in the Results
Code field. Because Date Scheduled and Date Achieved cannot be blanked
out, an asterisk in the Date Achieved field will replace the existing
Masterfile value with zeros.
6.5 Keypunch Instructions
There are six different card layouts which must be typed by the
keypunch operator for input transactions to CDS. The operator is
responsible for typing only the information which is coded on the
coding sheets or forms submitted by the user. However, card columns
1-19 and 80 must always be filled in by the operator on alj. card types.
This section contains a listing of the data elements on each of
the card types which will be used by the operator to enter transactions
onto the data base. Table 6-1 lists the data elements, 1-19 and 80,
which must be coded on all card types. Tables 6-2 through 6-6 list the
data elements unique to each card type.
Revised 12/79
56
-------
(.Aim i uui
0
zloia o o
O I
I M T (001
COMPLIANCE DATA SYSTEM CODING SHEET
Jtt 11
inn
'.limit I IIAIK
H
'(.h>pi|'
333
az r
7M.b|;ii»i/grre
rnm
ST/III MCIMIUIION
iaim
3
bit
6UH.II6?
55 66
iRirr
tHADING
IACIIIIY CAI'ACIH I ROt 9
• ^
1**
ulai^j
mr
m
f—' 11 III 110
idilliUblJiJJlIii
iiMijji Mii!, i jjjjji jiiiijiiii biKgiy;
>ah\Hii-Jwn>aii
0|0|0|0|0
4I I I I I I I I I I I I I I I I I I I I I I I 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 | | | | | 1 | | | I
m
PKOtlSS DtSCRIPIION
HII.T
XRll
w.
•fflg
I I I K>K>M
11
11
Mil Mil Ill
ISSHII
TT
'iiini in
JOJ!
005
ll
IIIIMH innim iniiiii
OKI
unz
H I I I I I II I I Mil I II H II I I II I II I Ml I II II HI Illl II I I III M I I M II
I MISS Kill I'L I Mill
'(IINI IP) IKI
(IMIUIIfll Al Illlll 1'ISlHlrilllH
II'.I « Ul III All'l
PI IIAI IV A'H
AC1ION my,,,
ivri I*H Aciinvii) BAH scmouuo SIAII RDI ,,
LL
!lM|,,Ut
H
LL
7TP7
f HISS (OH
J,MMI M in it M M tt^fc
Hi I I f.^ LI III Illl
I
P-
(0
n>
(X
l(,bU
FIGURE 6-5
SAMPLE COMPLETED CODING SHEET FOR DELETE TRANSACTIONS
-------
TABLE 6-1
KEYPUNCH INSTRUCTIONS
DATA REQUIRED ON ALL CARDS
Data Name
Region
State
County Code
Source Number
Emission Point Number
Action Number
Card Code
Update Code
Card Column
1-2
3-4
5-8
9-13
14-16
17-18
19
80
Data Type
Numeric
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 6-2
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 1
r-
g
S
n
0
o
01
1 2
a
4-1
CO
1 4
^
4J
3
o
0
J 1 7 1
0
O
t-l
3
O
CO
9 10 II 12 1]
4J
a
•H
O
M IS It
t)
s>te O
d o
o !
•H T3
4J K
u ca
•a! O
17 18JU
B:
0
Of
2021 22
X <1)
•H O
0 0
23 24 25 2«
Source Name
2J 21 2S 39 31 32 J3 34 3S X 37 JS 39 40 41 42 4) 44 « 46
Street Address
47 « 49 M 51 52 5J 54 55 SS 57 M 59 (8 SI 82 « M 65 6J
r-l
M
1
M'MW
§Qp
,22
tJJSS
69
RDE 4
70 71 72 73 74
RDE 5
75 7« 77 7» 7!
11
4J
•c
r
so
(A
Date Name
AQCR
City Code
Source Name
Street Address
Regional Data Element 1
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
Alphanumeric
Data Element Length
3
4
20
20
1
1
1
5
5
Justified
Left
Left
Left
Left
-------
TABLE 6-3
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 2
(N
O
C£
•^
VJ
!
|
a
-93
60 OS
fl) J-J
Od CO
1234
4-1
0
U
S 8 7 1
0)
O
o
en
9 10 II 12 1]
a
•ri
id)
1°
=S5= 0
ti ;u
O 1
•H -a
U lj
o Otd
CL, !•< 0
City Name
14 15 16 J17 1! 19-20 21 22 23 24 2S 26 27 28 » X 31 32 33 M
0)
-d
0
u
9*
N
State Registration
Number
35 IS 37 X }!j40 41 « 43 44 45 44 47 41 49 50 SI 52 S3 54
n
pd
*3
55 5C 57 M
O
M
C/l
59 CO 61 (2
vvj |
\N*~^
^fl
ClMrflj
^NW'<^
63>65
1 t
E-H
rti
*
esc
RDE 6
M 69 70 71 72 73 74 75 7E
&
<
H
CO
77717!
(U
4-1
«
T3
p
n
BO
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
Alphanumer i c
Alphanumeric
Numeric
Numeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Data Element Length
15
5
15
4
4
1
1
1
10
3
Justified
Left
Left
Left
Left
Left
Left
-------
TABLE 6-3A
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 3
~ Region 1
" State 1
- County
s
= Source
£ Point j
- Action* j
5 Indicator
s Pollutant 1
PC
3.
3
1
I
H
X
IT
lut
a
ff
a
l
_4
nt 2 u
Q
00 U
C (0
•H U
4J (B T3
£3£
11 .1 .1 U «
t
• Pollutant 1
Pol
1
1
t
j
i:
*•
Jt
a
ii
ai
X
£
i!
it 3 b
o
00 U
•H U
•O »4
U (3 *O
£3.5
4 M U it it
rf U
•H a
a a.
a a
a. u
it U « fl U 11 U
i
auait a n "
o
a
U1J
»H ^
¥ '•
in
j s Filler
I s Update
Data Name
Blank
Pollutant 1
Delete Flag 1
Pollutant Compliance 1
Pollutant Emission
Category 1
Pollutant Air Quality
Maintenance Indicator
1
Pollutant Air Quality
Control Indicator 1
Pollutant Loading 1
Pollutant 2
Delete Flag 2
Pollutant Compliance 2
Pollutant Emission
Category 2
Pollutant Air Quality
Maintenance Indicator
2
Pollutant Air Quality
Control Indicator 2
Pollutant Loading 2
Pollutant 3
Delete Flag 3
Pollutant Compliance 3
Pollutant Emission
j Category 3
Pollutant Air Quality
Maintenance Indicator
3
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
Blank
Card Column
20-21
22-23 ,
24
25
26
27
28
29-33
34-35
36
37
38
39
40
41-45
46-47
48
49
50
51
52
53-57
58-64
65-71
72-73
74-75
76
77-79
Data Type
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Numeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Numeric
Alphanumeric
Alphanumeric
Alphanumer ic
Alphanumeric
Alphanumeric
Alphanumeric
Numeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Length
2
2
1
1
1
1
1
5
2
1
1
1
1
1
5
2
1
1
1
1
1
5
7
7
2
2
1
3
Justified
Right
Right
Right
i
i
[
61
-------
TABLE 6-4
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 5
m
q
<"
o
I
L
•H 4J
4> U
PS CO
« JJJ 4
g
9
O
0
5 t 7 1
01
U
g
CO
9 10 11 1] 1)
a
•H
o
Oi
14 IS 16
(U
•o
5>fe O
§1°
•H "O
W 'l-i
17 18119
SCC Code
20 21 22 23 24 K K 27
^Crtft
O
2823
S
•^
30
^>
.^
3
32*
Federal/S tate/Local
Regulation Number
J4 39 it J7 3C M 40 41 42 43 44 4S 46 47 41
E-
t:
K
49
Process Description
SO 51 52 U 54 55 56 57 U 59 CO 61 S2 63 S4 U 66 (7 U 69 70 71 72 71 74
y y
' 1 J"
§!»"§
737(77 71 74 M
—
10
Date Name
SCC Code
Capacity
Code
Compliance Status
SIP Code
Pollutant Code
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
-------
«
jj
at
4J
CO
) 4
^
4-1
§
O
o
Sill
cdl
-------
TABLE 6-6
KEYPUNCH INSTRUCTIONS FOR CARD TYPES 4, 6, AND 8
CO
•*
A
o
egion
ji.
1 2
(U
4J
td
4J
C/3
1 4
4-1
O
U
i i 7 1
0)
O
£
CO
9 10 11 12 13
4-1
O
EH
14 IS IS
* fq
5 n*
lira?}
-4
II
17 !8|l9J2tl
Comments
21 22 23 24 25 X 27 21 29 30 31 32 33 34 35 3S 37 3i 19 40 41 42 « 44 45 46 47 « 49 U 51 52 53 54 55 56 57 M ii SO (1 62 63 64 55 (t 87 U ti 70 71 72 73 74 73 16 77 71 79
-------
6.6 Quality Assurance Considerations
6.6.1 Define the Problem
Understand the problem of what data needs to be entered and your
role in solving it. Misunderstandings can come from poor instructions
as well as from poor listening. Ask as many questions of your manager
as necessary until you are sure of what must be done. A few extra
hours at this step can save a lot of time and work at a later date.
At this step, it is a good idea to outline your analysis of the problem.
This way, any inconsistencies in your analysis can be corrected.
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 correct or complete. An example
is cross-checking state EIS reports with the York Report for data
on coal-fired boilers. Ask as many questions as necessary to
ensure that the documents being worked on 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 as the basis of a before/after comparison
of the data. Usually it will be more beneficial to run five or
six Quick Look reports instead of a single source data report.
Quick Look reports have the advantage of allowing the user to view
only those data elements in which he is interested and format the
report lines such that all of the same data elements are lined-up.
This last advantage 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, an analysis should be done to determine
the best input medium. There are three kinds of input mediums:
coding sheets, modified coding sheets, and retrievals. A modified
coding sheet is one in which some data elements are 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.
Revised 12/79
65
-------
b. Data from source documents
Code data from source documents carefully. There are four basic
source documents that are coded from:
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. New
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 manager 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 approxi-
mately 50% of the data should be checked against the source documents.
The verification should not be done by the original coder. A more
thorough verification will be performed at a later date. After the
random check has been completed, an analysis of whether the coding has
met the objectives of the problem definition should be done with your
manager. When the coding is correct, send it to keypunching.
6.6.5 Computer Operations
a. Input to edit
Log out coding sheets as they are sent to keypunching. When the
coding is returned from keypunching, 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 made immediately.
Revised 12/79
66
-------
b. Enter into the Update Cycle
Thursday mornings after the update has run, you should check
the update report for errors. Any errors 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% of the coded data with
the source documents.
d. Involve your Manager in Validation Work
After Step C has been completed, give your manager the retrievals
run in Step C. These retrieval reports will allow your manager
to recognize the quality and quantity of your work.
Revised 12/79
-------
7.0 EDIT PROCESSING
7.1 Edit Program Usage
Once data for the CDS System has been coded and keypunched, users
must validate the input transactions by running the CDS Edit Program.
The Edit can be run at any time, and it can be run any number of times
in between update cycles. However, it is best to coordinate the sched-
uling of Edit runs to correspond to the scheduling of the update cycle.
Allow time to correct any errors that may be detected by the Edit before
the weekly update.
Since the update cycle is usually run on Wednesday nights, users
should schedule their data preparation, Edit runs, and corrections to
be ready for the update cycle. At least one day before the update when
the input transaction volume is under 2,000 cards per week, the follow-
ing would be an ideal schedule:
1. Punch cards are delivered to the regional CDS Data Bank
Coordinator or to the operator of the communications terminal
on Tuesday afternoon.
, 2. Input cards together with appropriate JCL cards are submitted
on Tuesday night to COMNET.
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 2,000 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 keypunching.
The Edit validates each of the seven punched card types one 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
Revised 12/79
€8
-------
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 facility will be rejected since the facility
level data was not passed to the Update. With the hierarchial relation-
ship between source, point, and action transactions, an error at a higher
level can create additional errors in the update cycle for transactions
accepted by the Edit. For this reason it is very important to correct
and resubmit Edit errors as quickly as possible.
7.1.1 Warning and Fatal Errors
All transactions are validated by the Edit Program. The Edit Report
produced by the Edit Program lists the action taken on each input trans-
action. If an input transaction has no edit error message next to it on
the Edit Report, it is a valid transaction. One or more error messages
are printed on the Edit Report next to transactions in error. Errors
are identified as either "Warning" or "Fatal". One or more fatal errors
will prevent the transaction from being saved for the update cycle. A
transaction with only warning errors will be saved for the update, but
the data elements in error are blanked out. The user must review the
Edit Report carefully to verify accepted data and to make appropriate
corrections for rejected data.
7.2 Edit Error Messages
All of the errors identified by the Edit Program are listed in
Table 7-1. All error messages preceded by three asterisks indicate a
fatal error. Error messages preceded by one asterisk indicate a warning
error.
69
-------
TABLE 7-1
EDIT ERROR MESSAGES
Data Elements
Name
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
Action Type
Update Code
Action Type
Update Code
Update Code
Action Number
Source Name
AQCR
City Code
Zip Code
SIC Code
Federal Facility
Code
Active/Passive
Code
***
***
***
***
***
***
***
***
***
***
***
***
***
***
***
***
***
***
***
***
***
***
***
***
***
*
it
*
*
*
*
Message
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 NUMERIC
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 NUMERIC
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 NEW
SOURCE NAME MUST BEGIN IN COL 27
INVALID REGION ON CONTROL CARD
INCORRECT AQCR FOR COUNT
CITY CODE SHOULD BE NUMERIC
SIP CODE SHOULD BE NUMERIC
SIC CODE SHOULD BE NUMERIC
INVALID FEDERAL FACILITY CODE
INVALID AIR PROGRAM CODE
For Detailed
Explanation,
See Page:
A-22
A-45
A-45
A-9
A-42
A-80
A-84
A-55
A-67
A-41
A-82
A-84
A-55
A-51
A-67
A-67
A-68
A-84
A-68
A-84
A-84
A-67
A-61
A-61
A-5
A-7
A-49
A-34
A-12
A-l
-------
TABLE 7-1 (Continued)
Data Element
Name
Staff Personnel
Code-Source
SCC Code
SIP Code
Pollutant Code
Emission
Category
Mulitple
Crossreference
Date Achieved
Date Scheduled
Results Code
Update Code
Action Type
Pollutant Delete
Flag
Pollutant
Compliance
Air Program
Status
Air Quality
Message
* INVALID STAFF CODE
* SCC SHOULD BE NUMERIC
* INVLAID SIP CODE
* INVALID POLLUTANT CODE
* INVALID EMISSION CATEGORY
* MULTIPLE XREF SHOULD BE NUMERIC
* INVALID DATE ACHVD - OUTPUT ZEROS
* INVALID DATE SCHED - OUTPUT ZEROS
* DATE SCHED SHOULD BE NEW - OP ZEROS
* INVALID RESULTS CODE
* ASTERISKS FOR CHANGES
* ACT DESC IGNORED - ATPE NOT 00
* INVALID POLLUTANT DELETE FLAG
* NO DATA TO FOLLOW DELETE FLAG
* INVALID POLLUTANT COMPLIANCE
* INVALID AIR PROGRAM STATUS
For Detailed
Explanation,
See Page:
A-44
A-62
A-63
A-17
A-53
A-56
A-69
A-71
A-71
A-75
A-84
A-68
A-21
A-21
A- 18
A-3
* if
Maintenance Area
AQCR Indicator
Pollutant
Emission Category
Procedural
Compliance
Penalty Amount
Penalty Amount
Capacity Code
Source Compliance
Code
Source Emission
Category
* INVALID AIR QUALITY MAINT AREA
* INVALID AQCR INDICATOR
* INVALID POLLUTANT EMISSION CATEGORY
* INVALID CMS2 CODE
* PENALTY AMOUNT ONLY ON 2() ACTIONS
* PENALTY AMOUNT SHOULD BE NUMERIC
* CAPACITY SHOULD BE NUMERIC
* INVALID SOURCE COMPLIANCE CODE
* INVALID SOURCE EMISSION CATEGORY
71
A-14
A-15
A-19
A-59
A-73
A-73
A-6
A-36
A-39
-------
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 ele-
ment in the CDS System, please consult Appendix A. Coding instructions
are given for each data element; edit error messages by data element are
repeated in this appendix. Certain data elements in Appendix A contain
no edit error messages; these data elements are not validated by the
Edit and may contain any alphanumeric characters.
7.3 Sample CDS Edit Report
A sample Edit Report is shown in Figure 7-1. Each page of the
report contains the report title, the region name, the date, and the time
at which the Edit was run by the computer. Thfe 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.
-------
COMPLIANCE DATA SYSTEM EDIT REPORT
HEUION 4>ATL*MA
TRANSACTIONS ENTERED ON 11/14/79 AT 13133
PAGt 001
RG 8T CNTY SHCE PUT AN
0 1
12 34 5678 901?) dSfc 78
04 25 0600 60002 000 00
04 25 1920 6001 t 000 00
23 18 0420 10300 000 00
• *
04 01 2120 60024 000 00
04 01 2570 6"027 000 00
04 01 1920 60030 Oflo 00
04 |8 0420 10300 000 00
04 01 21JO 60U33 000 00
04 01 1H?0 6003« 000 00
04 01 1460 6004; 000 00
04 01 2100 70012 000 00
04 18 2600 llllt 000 00
04 01 1980 8000| 000 00
04 01 22^0 80001 000 00
04 01 2400 8000| 000 00
04 It 0">80 8000| 000 00
04 18 2600 !1|B| 000 00
• »<*•
04 1| 1120 8000) 000 00
04 It 1640 80001 000 00
04 || aj?o eooot ooo oo
04 11 4340 80001 000 00
04 11 5120 80001 Oflo 00
o« 11 5320 eooot ooo oo
04 id 2600 80001 000 00
04 34 0480 60001 OOQ 00
04 34 0540 80001 000 00
04 34 I860 80001 000 00
04 34 1900 80001 000 00
04 II 1640 80002 OOfl 00
04 18 2600 80002 OOo 00
04 tl 1640 80003 OOo 00
04 It 2380 8C003 000 00
04 01 2400 80004 OflQ 00
04 It 1|AO 80007 000 00
04 It 0460 80009 OOo 00
04 34 0480 80011 OOo 00
04 11 0980 Bflfllt OOo 00
'14 || 2?60 HU01H 000 00
04 H 38|,0 BD029 ,)00 00
04 34 0?ftO 80032 000 00
04 11 09ftU 80036 000 00
04 it ii 40 acua
-------
Error messages are identified on the right hand side of the report. ^j
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.
7.4 Edit Job Control Language (JCL)
To execute the Edit Program, use the JCL shown in Figure 7-2.
Because a job cannot receive this priority unless it uses less than
30 seconds of CPU time and produces less than 20,000 lines of output,
it is better to run two Edit jobs with 12,000 cards.
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 resubmitted 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 or 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 an 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 an 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 and WYLBUR concepts.
Revised 12/79
74
-------
CA
AUTHOR
TRC
PROGRAM NAME CDS EDIT
TASK NUMBER
ATE
JCt for uaiiig the CDS Edit with card Input.
1 }
//
/*
/*
//
//
//
/*
1
E
R
C
c
E
I
E
Th
4
P
O
N
0
D
c
O
5
A
U
T
S
1
1
F
b<
«
i
T
L
E
T
i
Vf
7
i
E
O
.
1
t
i
1
;
P
O
f
U
T
A
t
c
P
D
R
t
ri
R
S
D
ar
8
J
1
E
S
s«
Stl
i
a
r
n
p
O
N
E
X
1
t
u
i
a
T
n
B
T
X
E
N
01
d
i
a
c
C
1
b<
a
n
it?
a
! M
C
D
i id
[ la
1
1
1
1
_j
1
a
T
D
D
A
e
n
a
r
S
ft'
i
h«
h<
h<
20
a
r
i
*
6
(
t
i
t
21
P
af
t(
HI
9t
Si
Hi
n
M
T
e.
r1
i
i
i
n
i
n
n
74
i
hi
'
n
c<
CI
_e]
•
»2C
)
1 >C
tl
al
t nt
le;
t n
t
>'. I
77
e
n
B
n
G
DI
in
u
L
u
i e
f
r
t :
0
ID
S
a
i
B'
ni
7
1
11
E
rd
rj
rf
F
ot
12
R
IS
1
n
2
TR
13
c
-
e
L
H
1
lc
r.
iX
>'
t .
1 f
(
17
1
T
M
T
S
e
140
V
,f
1 11
1
•
e
I 41
1
3 e
1 U
44
ni
s
S4S
•R
1 er
t >
47
T
41 45
Y:
h 01
JS1K
1 p
- -
t 11.
S3
A
s
l»
S
-
• H,
iS7
,0
E e
f|
R
c
H
D
111
f
62 S3
P P
*4tt
P
Page
of CI
m
a H n TO 7i 7J 7i
IRD
JMBER
4 7S 7f 77 71 73 U
-------
AUTHOa TRC PROGRAM NAME CDS EDIT
Using the CDS Edit with the "DUWT" node; with this node, no data li savi
'15 1 1 1 1 1 1 1 1 I I i ! ] | I ] 1 a J ! 1 3 ! 1 1 ] 3 ! ! J
' / E PA i i 1 JOB ( oaoo v 1 1 > < 1 S E 1 1 | • ; |
/*ROUT E PRINT RMTrr
/*CNTL CDS EXC
//CDSEDJr EXEC CDSIPIr lipis'livii '
//EDIT. CARDS IN » D *
/*EOF
"n : ib v i tit c ir s s) ot Ld b j li :e t tt e ml f t) e r n a t 01 d c
Wlei M
ill ii t le u e S 1 il 1 li
00 a a j, tleuie -s ,:c,u t m nt.r
l<^i»iiejiij;w£j.Ui.IucU^I[.B.lJita
n
~ J-tieije.ij_£Lga~iufli£ u:aala.^ia^Qji_Ea
_ _ pp.p|»_U-tieue.i<_siflHti
I K ra ! 7-3
I >I 1C Tl E an 'S D MH IP I N
Page
TASK NUMBER DATE of CARD
>d on the HOD File. NUMBER
»|4l|42|d«|4s|«|d«|«|M|il|s2y^
i =i j ii i =- PAS SACRD:IBBB
£E it ' 11 t rt
J 1 a_ ;__ici L 'i_,i!^ ;ttu
,
-------
AUTHOR TRC
//
/*
/*
//
y/
//
N
//
/*
E
R
C
C
E
E
P
0
N
D
D
O
~-
-
A
U
T
S
1
r
i
T
L
E
T
-
•-
_
PROGRAM NAME CDS EDIT | TASK NUMBER [ IATE
Using tape Input Instead of punch card input to the COS Edit
i
E
D
f
-
-
i
1
C
-
C
T
A
-
10
P
D
R
II
R
S
O
12
J
1
E
S
Vi
i
a
r
n
X
p
y
z
13
O
N
E
X
1
ie
i
a
r
X
p
y
z
14
B
T
X
E
N
e
i
a
X
p
y
z
15
C
C
a
X
p
y
z
IE
(
R
O
X
z
II
a
VI
C
D
X
i
tl
a
T
D
-
19
a
r
S
D
D
V
i!
il
ii
1f
li
i:
|l
l!
n
a
r
1
S
C
0
1
1
11
P
N
B
L
he
\f
he
it
K
hf
h«
77
V
T
:
~
u
u
u
11
d
u
h
V
n
i
n
X
(
S
ie
;e
ie
it
ie
il
H
i
X
R
E
•i
<,
.,
I ,
.,
V
m
-
n
i
X
E
R
i
i
i
T
1:1
[
n
)
X
C
:
nl
cc
en
r?
i
at
Ef
ei
77
\
X
r
z
1
bu
>t
ifl
un
IW
0
l»
It
n
u
X
M
z
i
t
»r
"U
»
S
:
Z
nt
IB
f
h
UI
'T
-
30
E
U
F
z
mf
e
hf
b(
ill
R(
31
R
N
B
z
T
n
it
r
R
M
32
1
Z
;u
ir
n
?o
7
T/
33
1
T
L
e
a
m
m
„
?E
34
D
:
R
L
u
91
tl
A
35
/
3
E
A
-i
?
n
3t
4
C
B
£
;°
t?
tt
37
T
0
I
E
>r
Ie
>e
:
31
1
0
:
L
a
a
-
39
M
-
8
:
I:
t
e
40
E
5
0
R
at
nt
li
-
41
z
E
O
it
>e
42
1
D
B
T
b
43
1
L
P
ei
44
P
S
K
D
Ot
I
4S
A
-
P
S
:
e
ul
-
4i
S
-
:
1
1
m
ti
47
S
-
S
z
5
ib
>1
41
M
H
E
t!
-
49
O
R
:
ni;
f
-
M
R
y
B»
S(
-
il
D
y
$2
*
y
S3
p
y
H
p
y
55
P
)
Si
P
-
SI
M
n
-
it
(2
U
P»ge
of
U
in
CARD
NUMBER
73
4
17!
71
910
-------
A
union TEC
PROGRAM NAME CBS mT
TAfflC NUMBER bATE
Saving Che optional REJECT rile during a regular Edit run; this file can than be corrected via WYLBUH
i t
/ /
/*
/*
/ /
/ /
f f
/ /
/ /
/*
J 4 S
EPA
ROl
CN I
CDS
EDI
EDI
t pit
E9F
T e rt
111!
i i i
IE
L C
EDI T
r . RE
r . CA
r n a ti
V r W( (
1 II II U
JO
PRI N
DS E
EX
1 ECT
IDS 1
ni h u
r Is a 01
M BJ
i i
aa
r r
n
PP
M
B
T
K
E
N
d
41
<•;
i
a
p
IS
C
C
D
»e
b
a
p
ti
(
R
0
p
1
a
M
C
D
a<
I;
1
1
It
ll
t,
tl
a
1
D
D
D
D
0
e<
C1
t
r
t
!
-4
IH
• e
r r
SI
i S
1 S
:B
t
i •
t
e i
t jj
e u
e u
i -^
n»
,M
»1
:C
l»:
:(
i a
t e
S '
, ',
i •
k ~
824
i i
n
N .
( M
RE
el |r
ei 1
11
Li u
lei
I ?8
— f a<
2S»
i >
EP
E N
CF
f e
>f t
1 1
HI t.
Mi
01
Ui «
;»
2 2 2
' U
Ai i
KE
Y:F
M i
e ti m
Jlmt a
fie Cl
A!! feC.
F: n
11 G n
i i 1 Mi
SIR ID
i . aa a B
EP) SP
1 IRE C
o e J( L :a 4
» t o ( ;c ..
i t li -( f it
c fi i s. LS !s
E 7-5
E El I '1 .E
3 I 1
' T
. ED
ACE
L:8
a 1 at
1
1
II
;
z
o
W
K
D
(
«H?
E =
1 t
1 R
BL
n ol
UMtt
1 P
1 s
(
«SI
iu ib
K4741
1 1
1 s
5
CE :
«SiS
: i
2 33
) )
31 2
!2S1
PA
0 -
e )
M
S
-
1
K
S
If »
*c
H n II 12 13
D: GDP
rv»
at CAR
HUM
M K M H M H
n
11111
0
BER
rs K n n n
N
-------
/
/
AUTHOR TRC PRC
Pt
J 4 S 1 7 1
EPAJ TI
ROUTE
CNT I
CDS EDI
EDIT.R
EDI T . C
Ei >u n nt ic
EOF
n s it v, tut
WRAM NAME CDS EDIT
TASK NUMBER
IATE
intlnn the optional REJECT (lie during a regular Edit run.
Illll 1
JO
PHI N
CDS E
— *- —
T EX
E J ECr
ARD5I
1 in f-i n 3
c ir s at 711
Bit
i i
a a
r r
n
PP-
is it I? n is » n n
( aaa a V
RUTr r
C
C CDSIPT
DD SrSOU
DD *
u. d >e £ 4< e i am
b< s la :e t tl e
1, h ,«r-
fl 1, h ..r'
lLb_SjrJ
P _ Ii h s«r'
Fl
n»2S»»M21J01
Ml) 'USE
n
T: A DCBsB
:n f tl : r n a( tj
i n t a' i
> ic 01 nt n tin te
L.!£ig.£.j-£lgirj
i >a si 01 d
1 K,I; ?"-
n ij IG T E RI IE ;T F
»n
R
LK
)0 ^<
on d
-1 '-
J
'*
M
1
S
J
c
c
»
D
1
!,
•
3
d<
111
IE
i J
M
T
:
«
N
1
8
404
ME
0
f rp
— r
4243
= 1
no e
44
nt
(S
P
nl
K47
111
E I
41
Y
ts
:
at
1
$2
P
k1S4
\5
- -
»
S
-
*»
10
u
R
HI
D
»i
• n
R
D
13M
nn
M
rr
Pag»
of
t
N
n
n
n
n
CARD
NUMBER
7}
74
75
71
77
71
71
N
-------
WYL: NOT AN ACTIVE SYSTEM
SYSTEM? wylbur
WYLBUR: NOT AN ACTIVE SYSTEM
SYSTEM? wylbur
WYLBUR: NOT AN ACTIVE SYSTEM
SYSTEM? wylbur
SPECIFY GLOBAL FORMAT FOR SAVE COMMANDS
REPLY - DEFAULT, EDIT, TSO, CARD, OR PRINT
ct 1.1
exc job (a026,mexc),'cdsrtv reg4',time=l,prty=4
te print hold
1 cds,exc
4 exec cdsrtv
//sysOOS dd *
FORMAT?
COMMAND
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
2.
2.1
2.2
2.3
2.4
COMMAND
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
2.
2.1
2.2
2.3
de
?
?
7
7
7
7
7
7
?
?
?
?
7
?
?
7
tfau
col
//e
/*r
/*c
//i
//£
01
10
10
10
10
20
40
//
**j
lij
//I
1*1
/*(
//I
//!
01
10
10
10
10
20
40
//
04
aped
ecat
ecat
ptno
ql
nohd
major sip facilities in region iv
1 2
a 2
a 3
m 000
regn stte cnty srce ptno
//EPAEXC JOB (A026,MEXC),'CDSRTV REG4',TIME=1,PRTY=4
TE PRINT HOLD
L CDS,EXC
4 EXEC CDSRTV4
//SYS005 DD *
04 MAJOR SIP FACILITIES IN REGION IV
APCD L 2
ECAT A 2
ECAT A 3
10 PTNO M 000
i
40 NOHD REGN STTE CNTY SRCE PTNO
//
COMMAND ? run unn priority=5
743 IS YOUR JOB NUMBER.
COMMAND ? loc 743
JOB 743 EPAEXC AWAITING EXECUTION A ANY
COMMAND ?
FIGURE 7-7
80
-------
7.5 CDS Input Preparation via WYLBUR
WLYBUR 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.
When a uniform add, change, or delete must be made to one parti-
cular CDS punch card type, users should consider using WYLBUR rather
than ordinary coding sheets. If the selection logic of the CDS re-
trieval can be used to extract those CDS masterfile records which must
be changed, WYLBUR can be used to create the desired input.
Examples of successful WYLBUR applications are:
o Create a new action record with the same action type
and date scheduled for all NSPS facilities.
o Generate a new action for all action which have been re-
scheduled within a certain time.
o Delete all actions which have been scheduled and performed
prior to January 1, 1978.
o Change the Compliance Status for all sources which meet
certain retrival selection criteria.
o Change a Regional Data Element for sources which meet cer-
tain retrieval selection criteria.
o Change the AQCR for all facilities within certain counties.
The following checklist gives some of the advantates and disadvan-
tages of using WYLBUR for input data preparation:
Advantages Disadvantages
Saves input data preparation Input data must be re-
coding time for uniform changes. trievable from the CDS
masterfile.
Provides "instant input" with no WYLBUR sessions cost about
need to wait for keypunching. $30/hour; this is much more
than either coding or key-
punchingcosts for variable
data.
Revised
81
-------
WYLBUR commands, especially the Users must possess basic
change command, are powerful WYLBUR knowledge to perform
tools for data manipulation. needed data manipulation tasks.
The following steps outline how WYLBUR might be used to perform
any of the above tasks:
A) Formulate the Retrieval Selection Cards which will create
a Quick Look Report which can then be manipulated and con-
verted into input punch card formats. The 40-Card used for
Printline formatting should contain NOHD, REGN, STTE, CNTY,
SRCE, and any other applicable data elements which will be
needed for each input transaction.
B) 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:
1*ROUTE PRINT HOLD
C**d I 10 16
Column
If the user creates the retrieval via WYLBUR, he should submit
the following command:
? RUN HOLD
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
number as it will be used to fetch the job into your workspace
on WYLBUR.
As an aid in converting Retrieval output into CDS input
transactions, users are urged to create the following two
data sets on their WYLBUR source libraries:
1) Input Job Control Language (JCL). The JCL described
in Figure 7-7 should be saved as a data set. For
the example used here, TRC used a data set called
IPT4JCL.
2) Retrieval Job Control Language (JCL). The JCL described
in Figure 9-19 should be saved as a data set. For the
example used here, TRC saved a data set called RTV4JCL.
Revised 1/80
82
-------
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 4,685 major sources, they used WYLBUR to create one trans-
action Card-1 for each facility. They did this by using the following
steps:
A) 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
B) Submitted this retrieval with the following command:
? RUN HOLD UNN
C) Wait until the job had executed. Record the job ID number
carefully since this information is necessary to retrieve
the remote output for WYLBUR manipulation. The job ID for
this retrieval was "1357"
D) Used the following WYLBUR commands to create input punch
card transactions for processing by the CDS Edit:
1) Sign on according to the proper WCC conventions.
2) Fetch 1357
This command retrieves the output of job ID 1357 and
allows users to load the output into Working Storage.
3) LIST OFFLINE REMOTE=37 UNN CC
This command lists the Retrieval output on the high
speed printer at Remote 37. Users should route their
output to their own remote number. If users are not
sure of what data was retrieved, they should consult
this printout before proceeding further.
4) DELETE NOT '04' 2/3 IN ALL
This command deletes each Quick Look print line which
does not contain Region Code in columns 2-3. With one
command, all heading lines are eliminated.
5) SET LENGTH=80
6) SET TERMINAL WIDTH=132
Revised 12/79
83
-------
7) 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.
8) LIST
Check out what is in Working Storage.
9) CHANGE 80/80 TO 'C1 IN ALL NOLIST
Generates "C" in column 80, update code.
10) LIST
Check out what is in Working Storage.
11) CHANGE 69/69 TO 'M' IN ALL NOLIST
Generates a "M" in column 69, RDE3.
12) CHANGE 17/19 TO '001' IN ALL NOLIST
Creates card columns 17-19.
13) COPY ALL TO .001 BY .001 FROM IPT10JCL
Copies the data set IPT10JCL into Working Storage
starting at sequence number .001 and incrementing the
copied file by .001. Creates the run JCL for this file.
14) LIST
Check out what is in Working Storage.
15) RUN UNN
Submit the job for processing by the CDS Edit.
16) LOGOFF
Sign off after all WYLBUR session is complete.
Figure 7-8 shows a sample WYLBUR session used to convert Retrieval
output into input to the CDS Edit.
84
Revised 12/79
-------
79
""••""••' •' tuLcll MJ
CUiUiAc00 :•!
344. 040l02i*U00003000 il
3«5. 0401020000004000 ii
346 . .% . . . I .
CUMimll) 7 change 17/19 to '001' in all nolist
CO.-UiAnU 7 list
.j42. 0401024000001000001 11
343. 0401024000002000001 M
344. 0401024000003000001 U
34i. . 040...
CuJiilAl.D 7 coyy ail to .001 by .001 £rota i|,t 4jcl
O.OO4 - LAST' Lli.t.
CUi.lbit.U 7 lis
U.001 //liPAEXOLO JOU (A026,ItEXC),'HtC 0 CLCi 1K1" ,MSULEVliL-(l, 1 ) .PRTY-4
0.002 /*KOUTli. _PRINT .ktIiOTK37.
0.003 //LD1T EXEC CLiSIPTlO ~"
O.OU4 //lilJlT.CAkllSIN UD * , . ,
342. 0401024U00001000001 , .,
343. 0401024U000020U0001 ..;
344. U401U24UUUUU3000001 ti
345. 0401026000004000001 u
346. U4...
CO.ii'uvilL) ? run unit
tj I'j VOUu Job iJUiioEh.
:3b, fUIOUlTY 5/5/5
JOB
C
C
l.
C
c
c
c
c
c
c
c
00000100
00000200
00000300
00000400
c
I,
0
L
743
CLL/ui OK7 yea
lajllINU TlilL - 22.54 SLCUMJS
CONNtCI lltlt - 0:12:2d
ClbVKUcl • $O.OO
iitiU OF Smi>10i< TuUliUUAY 11/29/79
11:32:02 A.il.
FIGURE 7-8
85
-------
8.0 UPDATE PROCESSING
The update cycle consists of a series of programs which apply input
transactions 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 DBC 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 Master-
file 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 version of the Masterfile as output. There are three major
logic paths :J.n 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 Numbers) equal to or greater than the record identifier
on the new transaction.
2. If an input Masterfile record already exists for that record
identifier, 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
identifier, the transaction is formatted into an output Master-
file record.
86
-------
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
identifier as the input transaction, the data on the trans-
action is applied to the input Masterfile. After all multiple
change transactions 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
identifier 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 trans-
action to avoid rejects.
To delete an 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 greater than the record identifier on the delete
transaction.
2. If there is no input Masterfile record with the same record
identifier as the input transaction, the delete transaction is
rejected.
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 an 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 Masterfile.
6. For a facility delete, input Masterfile records with the same
Region, State, County, and Source numbers as the delete trans-
action are not copied to the output Masterfile.
Revised 12/79
87
-------
The Update will reject input transactions under the following
conditions:
1. 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 corresponding source, point, or action
records.
2. A new 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.
3. A delete and a change transaction for the same record iden-
tifier 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 Master-
file, 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 Data Bank Coordinator,
the personnel name and the associated table for that personnel 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 Data Ban> Coordinator to
add, change or delete entries on personnel tables.
8.2 Update Scheduling
The scheduling and maintenance of the update cycle is the responsi-
bility of the national Data Bank Coordinator. Once a week, usually on
Wednesday night, 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 to have all of their weekly input ready for key-
punching on or before' Tuesday noon.
Revised 12/79
88
-------
If a sufficiently large number of regional users request an addi-
tional update, a special update run will be scheduled. When holidays
prevent a Wednesday night update cycle or when a special update cycle
is scheduled, the national Data Bank Coordinator will inform all CDS
users of the change.
On Thursday mornings and an all mornings following an update cycle,
an Update Report will be routed to each region by the DEC. If the report
is not available 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
Job Control Language described in Section 8.6.
83 Update Report
The Update Program produces an Update Report which is stored on a
Regionr.1 file. If the user had transactions which were entered into
the update cycle normally, the national D3C 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.3.
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 longer on the disk
file. A new report replaces the previous week's report on the disk
file. TRC keeps copies of weekly Update Reports in its files; however,
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
Revised 1/80
89
-------
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.
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-1. The title, region
number, and output serial number are recorded at the top of the report.
Column headings 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 was rejected. Update error messages are listed in
Table 8-1. Th£ origin of the the input transaction is shown in the
far right hand coluan. 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, etc. A state code is placed in this
column if a state entered the
data into CDS.
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
Revised 1/80
SO
-------
next to the word CHANGED indicates that the Update has applied multiple
changes to the same Masterfile 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 diagnostic error message printed out. Table 8-1 lists all of
the errors identified 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 transactions accepted and rejected by the update for
each region.
To obtain the log, perform the following steps:
1. Follow the standard WCC sign-on procedures by typing in
the user account, initials, keyword, and terminal identifier.
2. As soon as WYLBUR gives the prompt, COMMAND?, type in the
following and then hit the carriage return:
USE $CN.EPAEXC.A026.CDS.SYSOUT
LIST
3. Figure 8-2 shows the contents of the log produced by
following the above steps.
Revised 12/79
-------
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
Cards 2 through 8 cannot be added to the
Masterfile 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 corresponding 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, and
Action numbers have an Update Code "N"
the first transaction is added to the
Masterfile; and the second and subsequent
transactions are rejected with this message.
A change transaction following a new trans-
action for the same Record ID is rejected.
Duplicate delete transactions are also re-
jected.
The Update cannot apply a change trans-
action or a delete transaction against
a non-existent Masterfile record. Verify
the State, County, Source, Point, and
-------
TABLE 8-1 (Continued)
Update Error Message
ALREADY ON MF
98 ON MF
&(AMPERSAND)
S2 REJ
ATPE WRONG FOR PCTY
Explanation
Action Numbers being used on the
transaction.
A transaction with an Update Code "N"
cannot be added to the Masterfile if
a Misterfile record already exists with
the same Region, State, County, Source,
Point, and Action numbers. Also a new
comment cannot be added if a comment
with the same record identifier and line
number already exists on the Masterfilc.
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 se-
quential 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 presence of a multiple
change transaction to the Masterfile.
This is noj: an error message; it is only
a warning that multiple, changes have
been applied to the Masterfile in
chronological order.
I£ one or more sets of pollutant compliance
data cannot be added to the Masterfile be-
cause 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 21, 22, 23, etc.
Revised 12/79
S3
-------
uPl'Alf: KtPUHl
PUERTO RICC DATA FOR REGION 2 • Nth YORK
OUTPUT SEKIAL «38
cunt
0
31
40
10
40
40
4(1
40
4(1
40
411
411
40
40
4(1
41)
4(1
40
40
411
40
40
40
40
40
40
40
40
40
40
«0
40
40
40
40
40
40
40
40
40
40
40
40
40
40
40
411
40
coot
5b78
1240
1280
1280
1280
1280
128(1
128(1
1280
1280
1280
1280
1320
1 370
13?o
1370
1370
132H
1370
1320
1320
13?"
1370
1320
1370
1380
1380
1380
1b?0
1b20
Ih20
1b20
Ib70
|6?M
1*20
lh?0
162<>
Ib20
1b?0
Ib2l?.3
00004
00003
00003
00oo3
ooon3
00005
OOOflS
00005
0 II 0 0 7
QOOA7
00007
ooooi
OOOfll
ooooi
00003
00003
00003
ooool
OOOpA
00006
oonnb
00007
00007
00(lfl7
07001
07on2
07002
ooooi
oooni
00002
00002
00002
000o5
ooooS
oooos
000(0
000)0
oooin
oooi i
0(10) 1
000) 1
000)3
000 | 3
000( ]
00003
001)03
PT
«5b
000
ovo
poo
000
ooo
ooo
00(1
flOO
ooo
000
ooo
OOP
ooo
ooo
00(1
0<>o
ooo
00(1
ooo
poo
ooo
oflo
00(1
ooo
ooo
ooo
ooo
0«0
1)00
000
000
400
000
ooo
00(1
(lOfl
ooo
ooo
ooo
0
-------
TO UCC ON GOO
ILLEGAL TER41HAL TYPE
ajb32
AUDLllSON-JACOUSUU AJ832
WYLUOR SYSTEM AT COIINET POKT3 TllURiiDAY 11/01/79 9:39:54 A.M.
10/31/79: ARCHIVING TO RESUME HUVEilBEH 11 - SEE NEWS ALEKT
10/2W/9: ONE NLWS FILE FOR ALL TERMINAL USERS - SEt NEWS HVS110
10/22//9: NbW SPACEL I'KOC FOR TSO AtlU WYLBUR USEUS- SEE NEWS FA120
10/31//9: RESTRICTION ON MVT SETUP JObS -SEE NEWS ALERT
10/26/79: ALPHA NEWS FILE TO BE DISCONTINUED - SEE NEWS MVSI10
10/31/79: VtTLRANS OAY AND THANKSGIVING SCHEDULE - SEE NEWS SE030
USERIO 7 upaexc
ACCOUNT ?
PASSWORD?
SPECIk* GLOBAL FOKilAT FOR SAVE COMMANDS
REPLY - DEFAULT, EDIT, TSO, CARD, Oil PRIIIT
FU1UIAT? card
COtlt-UND 7 use .cdB.sysout
COitllAWU ? lie
C0
en
i.
2.
3.
4.
5.
6.
7.
a.
9.
10.
a.
12.
13.
14.
16.
17.
18.
19.
20.
21.
22.
2J.
24.
25.
26.
CU1I1AND 7
FIRST VALUE/91031
OOOOOOOOOOOOOOOOUOOO
CDS HAbTEIt FILL OUTPUT SERIAL OOO*3/ O{< iU/31/79
/911J1
UPDATE HEP01IT PRINT-LINES FOR REGION 01- 00113
UPDATE REPORT PRINT-LINLS FOR KEGIOU 02- OOUO6
UPDATE REPORT PRINT-LIMES FOR REGIOW 03- 01356
UPDATE REPORT PRINT-LINES FOR REGIUN 04- 01543
UPDATE RKPORT PRINT-LINES FOR REGlOli 05- 00056
UPDATE REPORT PRINT-LINES FOR REGION 06- 00267
UPDATE REPORT PRINT-LIMES FOR REGION 07- 00848
UPUATE REPORT PRINT-LINES FOR REGION 08- 00030
UPDATE REPORT PRINT-LINES FOR REGION 09- 02364
UPUATE REPORT PRINT-LINES FOR REGION 10- 00007
UPDATE FINISHED AT 2123
RECORDS
RECORDS
KMXIRUS
RECORDS
RECORDS
RECORDS
RECORDS
RECORDS
RECORDS
RECORDS
INPUT
INPUT
INPUT
INPUT
INPUT
INPUT
INPUT
INPUT
INPUT
INPUT
- 00113
- U0006
- OU56
- 01543
- UU050
- OU267
- 00848
- 00030
- 02364
- 00007
ACCbPTLU
ACCEPTED
ACCEPTED
ACCEPTED
ACCEPTED
ACCEPT UD
ACCEPTED
ACCEPTED
ACCEPT El)
ACCEPTED
- 00105
- 00006
- 012//
- 01319
- 00054
- 0026!)
» 00799
- UOUJO
- 02316
- OOOUb
KbJECTCO
KLJECTEU
KEJLCTEU
REJECTED
KtJ^ClEU
KC.JECTLU
REJECTED
KLJECTCU
KEJUCTLU
KEJECTEU
- OOOOB
- 00000
- 00079
- 00024
- 00002
- 00002
- 00049
« 00000
- UOOO8
- 00002
FIGURE 8-2
-------
AUTHOR TRC
PROGRAM NAME CM Regional Update Report
TASK NUMBER
DATE
P»g«
of
JCL for obtaining the CDS Update Reprot (or « given region.
/
/
i
t
1
*
2 1 4 S i
/EPAi
*ROUT
> C N T L
/CDSR
/
*EOF
1 1 10 II II
i J
PR 1
COS
T I
u
i
a
r
n
p
i n is K i; u » n
DB (aoao
ST R VTr r
EXC
KEC CDSR
ii i «., t
!aa_i jtaa
[___4Jb,a
1 lu i
» HP _ i Jbi j
M 22 a H » n n n » M
vi i i ) 'us
PTn
e ' ii .1 il
E ' i c< a it nj ml ei _
e' Jeoi£i;ae.Li[ii
e ' e£ lo i ui b< r 3t
eljaiiiu:
i IG IR g -
C S U( DA t| R *i R'
)IU13MMK»Iin«4l«
ER ID' T 1 VE:
>
^ldJlijlSJ^_£2
S a e cc le T e ve :1 a
j
. )B C N- R( .
44««««WKil«MHii«5;
PRTYS4 PASSAC
HI ib !r
i ir : hi 01 sh 1 i S( ,1 1, IE e
il H il U U M
DS uppp
ts
N
t
M
a
n
;in
CARD
NUMBER
ri M is ;
77J171
tt
-------
8.6 Update Report Job Control Language
The user is responsible for requesting his region's Update Report
for each update cycle for which the region had input data. To execute
the program which produces the Update Report, use the JCL shown in
Figure 8-3. 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 mornings and on mornings following special update
cycles.
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 Report.
The Update Report provides the only audit trail of all transactions
placed on the CDS Masterfile; therefore, it is important to keep this
report on file so that errors can be researched and corrected.
97
-------
9.0 RETRIEVAL PROCESSING
The Compliance Data System Retrieval is used to prepare management
reports based on information 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 the Update Cycle. The Retrieval provides users with
the capability of seeing what data is on the Masterfile in a format that
meets the user's needs.
To obtain reports from the Retrieval Program, the user must care-
fully prepare a Retrieval request form and submit this form to have the
selection cards keypunched. The keypunched selection cards and appro-
priate Job Control Language cards are used to run the Retrieval. The
user submits this input to the central computer site via the terminal or
by WYLBUR. Output from the Retrieval Program consists of a Retrieval
Edit Report and the management reports requested by the user.
The Retrieval Program provides the following features:
o 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,
requests requiring less than 20,000 lines of printout can be
met within one hour.
o Improved selectivity - Information can be selected from the
Masterfile to meet the specific needs of the user so that smaller
more pertinent reports can be prepared. For example, if the user
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.
o Selection logic - Each user can select from his entire Regional
Masterfile only that data which is of interest to him for his
particular needs. The user can select data based on the pres-
ence or absence of information on the Masterfile depending on
the type of selection criteria he specified on the logic selec-
tion input card.
o Variable sequence - The Retrieval program permits the user to
select the sequence in which he would like to view the data he
has selected.
o Variable output format - Regions can select from seven print for-
mats depending on need. One 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 CDS' retrieval capability,
users should place data on the Masterfile in a manner which will permit
efficient retrievals. At the present, comment information cannot be
used in the retrieval's selection or sorting criteria. When preparing
input data for CDS, users should be aware of the validation procedures
for each data element performed by the CDS Edit as well as the selection,
sorting, and printing criteria available in the Retrieval.
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 user must determine what information available on the Regional
Masterfile is of interest to him. The user may obtain all of the infor-
mation on the Masterfile or a limited amount based on his needs.
S9
-------
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 infor-
mation 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 Region, 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, the Questionnaire Report, the Action Summary
Report, and the Milestone Report will present user selected and sorted
information in a fixed format. The Quick Look Report allows 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 provided in the following paragraphs.
9.1.1 Quick Look Report
The Quick Look is 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 also he may 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 fourteen other user-selected
data elements. The only restriction is the print line length of 132
characters. Users may suppress State, County, Source, Point, and
Action Numbers on each Quick Look line by using the No-header (NOHD) option.
This option allows the full use of 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 user may select one of the two special data elements:
BLK1 produces a blank column five 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.
If the user does not wish to see repeating data, the suppression
option can be used. Using this option, 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 always print.
Note that if only source and point information have been requested
on the Quick Look Report, only source level suppression will take place.
If only source level data has been requested no suppression will occur.
Figure 9-1 shows a Quick Look Report with data suppression.
At the end of the Quick Look Report, a total is given for the
number of lines printed. This total represents the sum of all items
meeting the user's selection criteria. A page-break and subtotals are
also available on the user-selected data elements. The user is cautioned
-------
^ tz
j a
. u.
O
•xj -> — -.
SSSSSSS3sS££;~;5Ss;";s;;"SEl~™£™::"TT~
i/>ip«393«-c',n
a: s.
— z
2 tt
3. a. i aj
r x
W OT
• u. tt &
a: ^. x «•; ^ ib
** ^ ^ -*j a jr
— err
35 u. 5. •« W «
2 »- ^
triQ.
-«<<
ifc I I
* j -i ->
X(ccrv> co
1C2
-------
to request page-breaks and subtotals only for those data elements which
produce logical groupings, such as State, AQCR, Action Type, etc.
The user may select his own sequencing for the Quick Look Report.
Often two Quick Look Reports with the same selection criteria provide the
user with a great deal of insight when the reports are sequenced differ-
ently.
Since three different Retrieval report formats can be requested
from the 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.
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 simultane-
ously.
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 criteria.
Logic selection was based on Illinois facilities which have had major
compliance actions.
Sorting was based on Source Name.
Print line selection was based on the following data elements:
Source Name, City, State, Emission Category, Compliance Status, Action
Description, Date Scheduled, and Date Achieved.
P,ovlcoc! 12/79
iro
-------
UJUK
«
SIIIIRCf N»Mf
AMFKRAM MHJCK
»l.fHKA» HK1CK
AMtKItAN HHICK
AMfcMtAN HHRH
AHMIIAN ,)W|CK
AMFHR4N HHK*
*HfH ICA( HHH K
AMFKICAN bHKn
AMOCIJ (.MFIMCAL
AMOtU (Ml
AMlltU H|l
AMtJtO 111!
AMOCO (Ml
A M| !(.(.' UK
AMOCO OH
AMI ICO 'Ml.
AMOCO OH.
AMOCO OR
AMMIHIk |i|A|.
ANMUUK MAI
AkMlJUt- |)|»l
AlJfUWA f'A PF I/HI. Afcl'
H r Gimiii, ir.H
LOhFlPtniUI htPflhl - Fl'k FPA INtfHNAl L'3F LM Y "
>'A,IOH ACIRf.S Fllfc F »79
CITY NAhf SI
CHlCACf. II
r.HlCAtil' R
CHKAGL R
CHItAPIJ II
CHICAGI! (I
CHICAGC II.
CMICAKC R
CHir.A6C 11.
jniiti R
HPun NIVEH it
*r,u,> KI^R R
*ron Kivtri u
^DUO KIVF« R
t>otjo HIVEM R
MOUM W(«f;M IL
*nun M»F« R
Kioon fjvFK R
hfl(JI) t.IVF'H J|
MtlMl.niFHY U
"l!N1(j( ^•^ WY n
HHNIUtl-f ((» 1|
MlCI H* ||
HFM«» ||
811. PDNl fhl.tESi UE3CHIP1R1N tcAT CMST ATPf nAU ACH
3»/u'l/flll
1i!l| KRN It (.hllSMJNG OPS 0 II 0" IIU/llll/OU
Jnii PEiHULkt'' KEI-IMNG i « hi os/u7/7s
?9'la 6SIFA»' HCILFH3 tl 5 05 00/00/00
?<*«/i ia pwrcfss HF,AIF:HS o s 05 o«/03 0 a 01 0«/17/7«
?H'I| IMIHF. Suinf.t I 5 5^1 nri/us/r;
?t)«l fKHMf Sllihff ? b SI U//HI/7;
?H«1 H-IIKt- StUHCI- (> S 0>j / /
?fc''s ^'•ll^'l suMct i o si / / FIGURE 9—2
»)M'>I 1 hF.Atlld I.PiMhG o 'I i,J oii/i>S/7/
-------
9.1.3 Source Data Report
The Source Data Report is the most comprehensive report available
from the Retrieval. All data elements for a facility are included on
this report; this is the only report which gives complete source infor-
mation, source comment information, point information, point comment
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 Master-
file, Source Data Reports 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.
There are four level options available, and one of these four levels
must be specified in the selection criteria. Level A provides a print-
out 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 provides 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 elements 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 Date 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.
Revised 1/80
-------
SMUKCfc DMA
SIAIt 11 CCUNTY COOK
CUNHl.l-NtlAI htPUHl . K,H
FCH
USE <1NLY
COUNTY
• • • f I
AIH.« oh/ my
•UOHC88 l?iST I UiHREKCt AVfc
C1T». 8TATF CHICAGIJ 1
FH'F MH-Ff.n
APCD (I SIP SliOHft
APST
LASl-UFf.AJE
o
>..>.>...,.
POINT NUKKFS ono Mi,t J
PULLIJIANI
uiSCRIPTICN FNTJHE
NO ac
scce cni
Idl)0
AC MO HI SCHM / / ACHV 10/ 1/77 ACT-TYFE SU | I $2
to
ID
O.
FIGURE 9-3
00
O
-------
9.1.4 Milestone Report
Two different types of Milestone Reports are available to the user.
The first is the Standard Milestone Report, which tallies Compliance
Status Code by State. The second is the Variable Milestone Report. It
is similar to the Standard Milestone Report, but tallies are based on the
two data elements chosen by the user. The presence of a 50 card in the
retrieval selection cards indicates that the report will be a Variable
Milestone Report rather than a Standard Milestone Report.
Standard Milestone Report
To facilitate National Reporting requirements by managers, the Stan-
dard Milestone Report was designed to provide a tally of the Compliance
Status Code of selected emission points within a 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 as 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 selection
criteria included only New Source Performance sources in Region V.
1O7
-------
SOT
**•«•»• ji a
i r;
J> -J> CB I -O
-* •Di-
o T 11 -n p- _
-» e e c i n
» i z i o>
c
2
-< Tl -4
5
T-
w m
c, e-
iv a, «
H
o
«* " <=
e o M -
.0 c
CB
O
n
o
r r«
CO T
T T
oe r
R •>
i n
3 «
M CB
-------
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 retrievable data
elements at the source, point or action level may be chosen. One data
element determines the rows that will be produced. The other data element
determines the columns that will be produced. Note that the user 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 for the column data element are to be
printed, the user supplies the column data element and the specific values
for that data element. A maximum of ten values will be accepted.
As in the Standard Milestone Report, the totals produced by the Vari-
able 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.
Revised 12/79
109
-------
"ILESTOM-. MFPflHT
8
0
1
9
3
"
5
6
7
«
«
11/21/79
COMPLIANCE STATUS
LUMPL STATUS UNKNOWN
LOCPt STATUS UNHMlMN
11" VJM.-NO acHEOuLE
IN CUMPL-SCUBCJ TEST
IH CUKPl- INSPECT I ON
in CtlKPt -CERTIFICATE
IN VHiL-HfETlNG sCHfl
IN VIOL-NOT KTC SCHD
IN VIOL-UNK kM »CHO
NO APPLIC STATE REG
IN COPPL-3HUT OIlHN
UMALS F(J» ?, J, «, 9
10TALS FUH ) , 5, 6
TlilALfl FfjO n AND 7
bKANO IOTAL3
COMPLIANCE DATA SYSTEM
CUNHOENTIAI. BkPOHl . FOR tPA INTERNAL USE (JN( Y
WtGinN 3 NSHS COMPLIANCE MIUSTUNt
HF6IUN 3 UELAhARE YASHIN OC MAHYLANO Pt*NS VIRGINIA b
TOTAL OS 09 21 .39 afl *
t 0 n
2? 0 o
« 00
20 o 0
to o o
• 55 I S
1 0 0
200
1*7 1 5
in o o
?2 0 0
220 t S
1 0
0 9
I S
t 12
2 7
14 09
0 t
t t<
ie 68
t 6
e 9
2« fl3
0
2
0
,
0
61
0
t
6ft
0
2
68
PACK 1
SO
n
3
,
3
1
25
0
0
24
3
3
J5
-------
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 the 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.
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 Questionnaire 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, 1979.
and November 1, 1979. Sorting was based on Source Name.
Revised 12/79
111
-------
ACTIONS SCHEDULE!) Hut NUT ACH1EVFU
M/?1/71 CONMntNUAL PEPdM . FOH EPA INfEHNAL USt UN|
."cri^u^ct'uAu'srstf
FOH SlATfe UF
CALIFfWNIA
STATUS CUOtS (.ACTION ACHIEVED J-ACUCN NOT ACHlEVtn
j
' •
; ; • '.
. I'UUM.A.t r,JL . TAK.K3 . ' ... a-,..
. I«7"H r>U»N;E» AVF ' ' • STATUS CUOfc CCL 71
I ' • . HNAL CUHPUANCE HFPOM . UATF ACHIEVED!^ 55-*o
. SfAlE BEGIS!»AlJ(>N ) [ ' • "0 P»» Y«
• . 09.0S-fliOO-«nu29.(IO|.!r-7.'
NO SlHEfJULE CUL flU • N «
' • • . EPA CL CCOt COL 10 .
* • • i n»-o5-«ioo»oooa9.oni.uo.5.
.. IFHISNII .* ' . COL 80 - c .
r? . T cirv erne |
f* . ^'C C(IH>'(IMAriCN . PESHCIDE FURMUf. SJ 79-118 ' 9/17/79 '
~ : "ol 8UNL4NU *vt- • *"NB *• - : ^i«Zt%iUK COME.CW :
, STAIt HtGlSTHATllJN ! ) ' • Mt) "*» Y«
' SIIUHCf 8IF ' ' • "*-<'5-»8?0. CLDF. ' '
rL^: ^,rfiAS Fxf":SJ "•** : i-i;*-^ t. 81U UKS RL: — ^ „,,,
• « STAkl CF IK.siTfc LIKSlKli.. OAIE ACHIkvF.li.Lni Si-fcO
RtKISIHATJOK, ." ; • CT/PHtj"SS CHANGE RtPMRI . ^P t)AV VW
SIP ' • «9-0
FOHU . Ct'L
!>f * •
FIGURE 9-6
-------
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 lists comments as opposed to the Quick Look Report. If no
sequence is specified, the report will be sequenced 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 Name.
9.1.7 Compliance-Action Report
A new report format has been developed for the CDS Retrieval Package.
This report, called the Compliance-Action Report, summarizes the compliance
status and enforcement actions for selected facilities on the CDS master-
file.
Figure 9-8 is a sample of the Compliance-Action Report. It is available
by coding "CA" on the Report Format 20 Card. The left side of the print-
out contains basic source information such as Source Name, AQCR, City, State,
and 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 Date Achieved for nine specific action types:
o Federal Inspections
o State Inspections
o Federal Notices of Violation
3.1.3 Revised 1/80
-------
ACTION 8UMMAHY REPUHt
11/21/79
ACTION
trpt of ACTION
NF.SHAPS SUUHCE TfST
STAFF HEfHER SUUKCF NAME
AND TITLE AND IttCAlILN
AfL-HM CLAYTON SIP
ATLANTA GA
ATL-HM CLAYtQN STP
AILANTA GA
ATL-UTflY C»EEK STP
ATLANTA GA
ATL-UTOY CREEK STP
ATLANTA GA
CITY tlF SAVANNAH 3TP
SAVANNAH GA
ntKAia cnuNiY UHT PC
OECATUH GA
flEKALH CUUMY UwT PC
OECATUB GA
CIIHPL1ANLE DATA SYSTEM
SUHfAKY fUH NESHAPS
DATE. SCh.
DAU ACH. STATUS CODE
inn/it,
2/10/76
2/10/76
2/10/76
2/U/76
2/ll/Tb
2/11/76
2/11/76
5/11/76
5/l«/76
2/15/77
2/15/77
2/15/77
2/15/77
STATE NO.
COUNT* NO.
11
22AO
11
2260
11
7260
11
2260
1 1
0"»«0
It
1640
11
1640
scifcce NO.
P01M Nil.
BU26H
000
00268
001
anJTS
000
ao37S
oni
80016
001
PO««U
000
eno^ti
001
PAUE 1
PULLLTAM
H(>
HG
HG
HG
US
FIGURE 9-7
-------
cn
SliUKCt **"t AUCk
CUV si AIPI
AkK P*L-lNI>EPFKOtNCt 020
NFhAHK AH
AI'K. P«L. INDEPENDENCE. 021)
NfnAHK «H
AUK fKL-L. LATfFHjME III*
JCnM MILL AH N
AKH F*L-L, CAlHtklNt olfc
JtN»s MILL AH
AUK I'kL'MJLLEAR UNF 016
KUNSF.LLVILLf A«
A«r PM-MICHIF PLANI nan
MFI.FNA AH N
AUK P*L»«HII£ (M.liFF 016
KFI-FIFLU A« N
»*K Ptt.KHtlf BLUFF ftl>>
Htl.FTe.LI) AH K
AUK PRL>>-HITE BLUFF 016
Htl;F|FLP iH N
AUK Mv VALLEY liWA|N nlh
AUK "KECKING CT.'lNt Dlfc
Hill SPH|N6S AH h
AKK. Cl"tNI CUBF. 118?
CIIMFI. 1«''CF OAIA 3Y3UM '••'•F 1
ClINF lOtNTlAI. HtPUHl - FL'H tPA JNIF.HNAI. USt t)Nl Y
FY7t CCIMPLIANCF. *tIICU8
SIAFF flue cCMpLlANtt sfAios iMS^trr fist r Kdiict HSI i rwrfw i-si i riin H.M i
E^'issiuh CATFGOHY ' cii't CF viii runt T.ssiim n «t ALHIK LIDI
S. SPHUIELI. DPI
3. SPHHTIil.L 002
000
MARTIN HkUTAIN 000
oun
ono
oun
S. SPWUICIL I'D)
3. SPUuitlL <'U?
Oun
H^UNHHIMAIN «„„
S. SPHUIfll. OOfl
a
3
3
8
3
a
3
1
e
3
3
2
ft
2
e
2
3
2
ti
u
3
2
IN rCHPL-Ltdl If
IIVtK IKUU IPY
Nil APPLIL SIAU
(IVtH 1(1011 IPY
Ml) APPL1C SIA1E
IIVFH |l)i)« IPY
IN CCKfL-CFHI |F
n»n i(j louo IPY
LESS (HAN ItIO T
Nil APPLIC S1A1E
IIVFK \IIOII IPY
IN CI>Pl«|N3PtC
loo IL I'lon IPV
M|i APJ-LJC SIAIE
loo IL l FIGURE 9—8
3l*Tt <»/i.i/7S >
SIAIt 2/?i/7« i
SI»H 7/lu/7»- '
SIAlh I/ 7/77
Sl»l» 't./ 7/77 >
SIAIF 7/t?/77 '
SIAU. 7/11/7" '1
-------
o State Notices of Violation
o Federal Orders Issued
o State Orders Issued
o Federal Court Actions
o State Court Actions
o 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:
o The retrieval selection logic is the same as for any other
retrieval. Users should be careful to specify in their selec-
tion 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 Date Scheduled.
o 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.
o 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.
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).
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 Determined 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.
Revised 12/79
116
-------
Since the report lists seven different action dates side by side,
Regions VI has found this report extremely useful in tracking the progress
of the permit 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. (Gee Saaplo PSD Report,
Figure 9-9).
9.2 Check List for Request Submission
The following list of steps is provided as a guide for users sub-
mitting requests for retrievals. The list is roughly sequential, in
that an inexperienced user would proceed in chronological order.
A. Determine what you want.
1. 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 requirements?
B. Code the form.
1. 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.
2. 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.
3. 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).
4. Select the sequence of the items in the report, and fill in the
"30" card line on the form.
5. Review entries on the form to see that all data element abbre-
viations are correct.
6. 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 abbrevi-
ations.
34.7 Revised 1/80
-------
SIUNIHCANT \>t
HEPOKT
OD
04/18/79
SOURCE NAMf
LOCATION
AIM PRODUCTS AND CHE
CHANNtLVItW TX
AMf TUBOSCOPE
HOUSTON TX
AMOCO TEXAS REFINING
TEXAS CITY TX
AMOCO TEXAS REFINING
TEXAS CITY TX
AMOCO TEXAS HEFlMNG
TEXAS CITY TX
AKCO CHEMICAL CO^PAN
BAYTOhN TX
ARMCO STEEL CORPORA!
HOUSTON TX
AUSTIN WHlTt Lift CO
MCNEIL TX
BOARD OF TRUSTEES
GALVtSTON TX
CAM COMPANY
TEXAS CITY TX
CAPITOL CEMENT
SAN ANTONIO TX
CENTRAL POKER 1 LIGH
FANNIN TX
CHAMPLIN PETROLEUM
CORPUS CHRIST! TX
CHAMPLIN PETROLEUM
CARTHAGE TX
CHAMPLIN PETROLftM C
APPLICATION
NUKHER
PSD-TX-I lb
PSO-TX-207
A
PSD-TX-02i
P SO - 1 X « 1 0 7
P80.TX-H9
PSD-TX-116
P3D-TX-027
PSO-TX-114
PSD-TX»|69
A
P3D-1X.UO
P8D-TX-1?0
PSO-TX-009
PSD-TX-096
P3D-TX-H06
P3D-TX-Ole
CClHPLlANCa DATA
LOKF JDtNl J»L HtK)tO»-FltK EHA
lExAb P3U FACILITY
PSO APPLIC P8D *PPLIC P3D RfVTE«
SUHMIITtO r,HO COMHL KECUVFO
08/03,78
02/16/79
05/10/77
08/01/78
08/04/78
08/01/78
05/19/77
06/01/78
10/02/78
08/02/78
08/04/78
02/01/77
07/24/78
02/20/79
07/22/77
09/07/76
02/21/79 N/A
09/07/78 01/11/79
09/11/78 01/21/79
09/06/78
09/DE/7S 01/05/79
11/06/78 N/A
09/01/78
09/07/78 01/02/79
09/06/78 01/21/79
SYSTEM
INUHNAL
STATUS
HSD NOIICt
DKAFTtD
02/21/79
06/01/77
01/11/79
01/26/79
06/15/77
01/06/79
11/16/78
01/05/79
01/01/77
02/21/79
ll/0«/77
USE CHLY
PSD PIIHLIt F-SO PUBLIC P8I) PEfcHT
NOTICE htANING lasifcll
04/09/79
06/14/77 07/27/77
01/13/79 uI/04/99
06/29/77 09/26/77
11/28/78 01/19/79
04/01/77 Ob/lfl/77
01/28/79
11/16/77 01/16/78
PAGt 1
rO^ftNTS
CHANKELvIkk
HUUSHN
TEXAS CITY
TEXAS CITY
TtXAS CIIY
BAYICttN
HUU8MN
MCKEH
GALVESTLN
TtXAS CITY
SAN ANTLNK
FANNH
CORPUS CHK1S
CARThAGt
CORPUS CMhIS
FIGURE 9-9
-------
C. Verify the completed form.
1. Review the request form to see that all needed entries have been
made.
2. If the selection logic to be used is fairly complex, mentally
"walk through" several cases and see if the logic meets user
requirements.
D. Punch retrieval cards.
1. Arrange to have punched cards prepared from the request form.
2. Check the cards to ensure that the data was punched correctly.
E. Build your retrieval deck of cards.
1. Add a job card priority card, and any routing 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.
2. Add the two JCL cards described in Section 9.4. They go just
before the "01" card,
Add/*EOF card as the last card in the deck.
3. Review the sequence of cards.
F. Submit job and wait.
1. Submit the deck to the central computer facility (WCC) via the
locally available terminal.
G. Review output.
1. The printout should be returned within a few hours, or at most
on an overnight basis. Check with the terminal operator if not
received.
2. 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.
3. Review the decoded parameters on the edit page to see if the
instructions (request cards) were decoded as the requestor
intended.
4. 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.
5. Call TRC (203-563-1431) if you are having difficulties getting
the desired output.
Revised 12/79
-------
COMPLIANCE DATA SYSTEM
TIME.
Report Request Form RETURN REPORT i
rn
11,01 1 . , , 1 I_J 1 . . . u^..l,,_t-,,l
1_IJJ I,,,I_J..1_I I§,J 1nl IU
Dm limn*** CM* VMwIuft JmtlfM)
HiP) 1 , ,..,. 1 LI I ..-L..! . i . i 1 rni^iTinN rnnps (in r.ARn)
M.Ol 1 . , . I 1 1 1 . . . i_..i_,i u-
.1.0. ..,.!,,. M - MUST EQUAL
H.Oi 1 . , , 1 1 || , , , , , , . A - ALTERNATE (Used for
.. a, , .lit Multiple Values of a
ll.OI lit . 1 l J 1 . , . . . 11 r - n . rl 1
1 ' ' '— •— ' — L- • ' *—' '-<--•— i — i--*— .I—*.— . Given Data Element.)
11.01 1 , . , 1 1 1 1 , . . i.j ,i .1.
n.o, ..,,1111 U - UNEQUAL
11.01 i ,,, i 1 | | ,,,,,.,,, R . FQIIAI nn GHFATF.R THAN
|1|O| 1 , i I 1 1 1 1 i . i,..j,_l_JUJ.J , rn,in, nn i pee TUAHI
"— *— ' ' ' *-•"•-' •-' I~J '•"*•»'"-*-'— >•- L _ £(juAL OR LESS THAN
W.Ol 1 . , , 1 1 J | | , |_i. |,,i_j.J
., ai . ..it P - PRESENT ANY ENTRY
11,01 i i , . J 1 J | , , |, ,,,, if R . Bl F>W n" 7frRn5
11,01 1 , , , 1 1 J t .j, |,|, | t.,,1
1 i , o| | , , i i i i i , , i .1,1
See reverse side tor a
liiO. i , . , i i., ) LJ L_J i_,.i-j._i— list of all CDS data
H.oi . , , , i 1 | i i i i i i i elements and their
abbreviations.
I* .ci i , , , i I j | | , | | . ,,i , ,
It, 0| 1 , , , I I 1 ,,,,,,,
I'i0| I , i , 1 I J | | , , , ,, ,
tINIT fORMkTS
12, CM ! . J I , 1 1 . 1 1 ,..,,,, 1
1245 It 1* U i« i'
IIFOIT SCOUIUCE ^»Jiv»oto ;5E5u:sE3 TO ACCESS CONF!:E:IT:;I :ATA -:LE«:;TS)
acuESCE UIII-ES ro v CHARACTERS
i« tt
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
Q2 - DOUBLE SPACED QL
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
LEVEL CODES (01 CARD)
REQUIRED FOR SD REPORT ONLY.
VALID ARE:
A - ALL OATA
C - CRITERIA MATCH ONLY
P - POINT & SOURCE
S - SOURCE ONLY
31 491 m •(•m*M»
OUICX lOOK ItrORT FORMAT
IT 4' ' '? »' ' '» 14 ' 'l7 I» 22 24 17 2f 32 34 37 39 42 44 47 49 S<
Enter DIM Elcwntl to tw InclwM M Meort
llmUrt to 131 Oiwtcttn »HI> HW« fl»t1w, I , , , I I , , , J I . i , I | , , , | I i i i I LJ
tl«U»d to 110 Kltt Stir«d«rd HeM
-------
VO
I-1
o
DATA ELEMENT
AIR PROGRAM CODE
AIR PROGRAM DESCRIPTION
AIR PROGRAM STATUS
AIR PROGRAM STATUS DESCR
AIR qOALlTY CONTROL REGION
BLAHS (5 SPACES)
BLUBS (15 SPACES)
CAPACITY - FACILITY
CITY CODE
CITY RAKE
COUITY CODE
COUNT! NAME
DATE LAST UPDATED
FEDERAL FACILITY
REDS SOURCE CROSS-REFERENCE
FOLLUTAn AIR QUAL MAIMT AR
POLLUTANT AIR QUA! CONT REG
POLLUTANT - BASIC SUMMARY
POLLBTAirr CODE - SOURCE
" POLLUTANT EMISSION CATEGORY
FOLLDTAn LOADING
PRIORITY CODE
REGION
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 CLEMENT 10
REGIONAL DATA ELEMENT 11
REGIONAL DATA ELEMENT 12
SIC CODE
SIC CODE DESCRIPTION
SOURCE COMPLIANCE STATUS
SOURCE COMPLIANCE STAT DESC
SOURCE COMP STATUS - > QTRS
SOURCE COMP STATUS - 1ST OTR
SOURCE COMP STATUS - 2ND QTR
SOURCE COMP STATUS - 3PD OTR
SOURCE COMP STATUS - *TH QTR
SOURCE COMP STATUS - 5TH QTR
SOURCE COMF STATUS - 618 QTR
SOURCE COMP STATUS - 7TH QTR
SOURCE COMP STATUS - STB QTR
SOURCE EMISSION CATEGORY
SOURCE EMISSION DESCR
SOURCE NAME
ABBR
AFCD
APDS
APST
APSD
AqCR_
BLU
BLE2
FCAP
CYCD
CYNM
CNTY
CTNM
UFDA
FEDF
NEIS
PAQM
FAQC
BPLT
FLLT
rcHS
PECT
LOAD
FRIO
REGN
RDE1
RDE2
RDE3
RDE4
RDE5
RDE6
' RDE9
RD1*
RD11
RD12
SICC
SICD
sots
SCSD
SCS*
SCSI
SCS2
SCS3
SCS*
SCS5
SCS6
SCS7
SCS8
SECT
SECD
SNME
DATA
TYPE
S
S
S
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
SPECIAL
CHARS
C
NUMTER-0
10 I JO
CARD
1
10
1
10
3
7
4
15
4
17
6
1
4
" I
1
60
2
1
1
5
1
2
1
1
1
5
5
10
7
2
2
1
4
30
1
20
I
1
1
1
1
1
1
1
1
1
13
20
DIGITS
40 CARD
5
12
5
11
5
5
15
>
5
5
18
9
5
5
5
5
61
5
5
5
6
5
5
5
5
5
6
6
11
8
5
5
5
_ 5 ..
31
i
21
9
5
5
5
5
}
5
5
5
5
14
21
DATA ELEMENT
SOURCE NUMBER
STAFF NAME - SOURCE
STAFF PERSONNEL CODE - SOURCE
STATE
STATE ABBREVIATION
STATE REGISTRATION NUMBER
STREET ADDRESS
ZIP CODE
CAPACITY CODE
COMPLIANCE STATUS CODE
COMPLIANCE STATUS DESCR
EMISSION CATEGORY
EMISSION CATEGORY DESCR
EMISSION POINT NUMBER
"MULTIPLE CROSS-REFERENCE
OLD COMP STATUS - 8 QTRS
OLD COMP STATUS - 1ST QTR
OLD COMP STATUS - 2ND QTR
OLD COMP STATUS - 3RD ^TR
OLD COMP STATUS - 4TH QTR
OLD COMP STATUS - 5TH QTR
OLD COMP STATUS - 6TH QTR
OLD COMP STATUS - 7TH QTR
OLD COMP STATUS - 8TH QTR
POLLUTANT CODE - POINT
PROCEDURAL COMPLIANCE
PROCESS DESCRIPTION
REGIONAL DATA ELEMENT 7
SCC THREE-DIGIT CODE
" 'SCC SIX-DIGIT CODE
SCC EIGHT-DIGIT CODE
SIP CODE
SIP CODE DESCRIPTION
ACTION DESCRIPTION
ACTION NUMBER
ACTION TYPE
DATE ACHIEVED
DATE' ACHIEVED" YEAR/MONTH
DATE SCHEDULED
DATE SCHEDULED YEAR/MONTH
PENALTY AMOUNT
REGIONAL DATA ELEMENT 8
RESULTS CODE
RESULTS DESCRIPTION
STAFF NAME - ACTION
STAFF PERSONNEL CODE - ACTION
STAFF TITLE
ABBR
SRCE
STFS
PERS
SITE
STAB
STRC
STRT
ZIPC
CAPC
CMST
CMOS
ECAT
ECDS
FTNO
MULT
OCS«
OCS1
OCS2
OCS3
OCS4
OCS5
OCS6
OCS7
OCS8
PLUT
CMS2
PROS
RDE7
SCC3
SCC6
SCC8
SIPC
SIDS
SREG_
ADES
AHUM
ATPE
DTAC
DAYM
DTSC
DSYM
FLTY
RDE8
STAC
RSTD
STFA
PERA
TITL
DATA
TYPE
S
S
s
s
s
" s
s
s
p
A
A
A
A
A
A
A
A
A
A
A
A
A
A
SPECIAL
CHARS
C
,
C
C
NUMBER 0
10 4 30
CARD
5
15
3
2
2
IS
20
5
2
1
20
I
13
3
3
8
1
1
1
1
1
1
1
1
2
1
25
1
3
6
8
1
20
15
15
2
2
6
4
6
4
7
2
2
15
15
3
15
! DIGITS
40 CARD
6
16
5
5
5
21
6
5
5
21
5
14
5
5
9
5
S
5
5
5
5
5
5
5
5
26
5
5
7
9
5
21
16
16
5
5
9
"5
9
5
11
5
5
16
16
5
16
ID anneta! characteristic, colu
• reputing data •IcMot.
"C"
a coaMd.ntl.l
-------
Mailing Label Option
This option 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 processing are the standard 3-up, self-sticking labels which
can be printed on 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 procedures developed for this purpose. There is a cata-
logued job control procedure available to all CDS users.
Each mailing level will carry five lines:
o Managers Name
o Facility Name
o Street Address (if available)
o City, State, Zip Code
Two new source level comment lines on card type 4 have been pro-
vided 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-10A)
Revised 12/79
-------
FORTRAN CODING FORM
AUTHOR TRC
„ STMT
NO
1 ill
/At
/4
/Jc
//
II
01
10
20
30
//
II
/*
c
R
S
E
4
P
O
M
D
T
S
T
O
S
A
U
T
S
V
D
E
F
S
U
t
i
T
L
m
P
FBOORAM NAME MAILING LABEL JOB CONTROI
TASK NUMBER
FORTRAN STATEMENT
7
i
E
S
tf
U
yi
i
3
I
i
E
y
1!
)
i:
1C
S
C
X
s
t
s
1
L
n
P
D
E
0
k1
LI
!<
A
II
J
R
S
C
O
a
e
fi
q
B
II
0
1
5
VI
11
E
13
B
SI
E
C
i
a
:n
L
14
T
X
D
D
a;
o;
h
c
S
IS
(
c
s
D
1
1
•1
If
a
R
L
0
C
s
s
O
17
a
M
A
#
11
n
M
O
II
a
T
B
T
d
it
e
u
a
n
E
Lt
s
f"
:t
D
20
n
L
1
a
i
C
21
M
2
h)>
31
B
a
i
R
C
"
23
i
E
a
r
r
3
(
»
i
3
•c
»c
IT
1
R
n
)
N
u
c
E
»
*
.1
tv
11
C
j
a
P
n
r
n
T
&
d
f
i
a
P
n
r
a
U
r
d
fl
\f
\
a
P
n
s
e
s
;
a
P
10
E
R
f
It
R
E
!c
>F
B
i
i
i
i
i
f
32
3
n
t
s
s
s
s
s
5
13
|
•r
.£
t
t
t
t
t
t
D
R
f
n
R
h
h
h
w
h
a
**
•
E
1
i'.
E
>
*
i
;
-
•I
3
a
c
u
u
u
d
u
i
G
IT
T
r
I
3(
3f
5<
M
3(
3
JI
3t
1
;
r
i
r
i
r
E
31
M
L
R
9
i,
r
i ,
-
r |
)
«
E
0
>j
4
r
-
41
*
3
n
i
a
P
a
r
J
L
4}
1
;
M
B
i:
u
U
si
:n
W
43
R
L
t
0
s
o
0
0
44
p
G
F(
K
L«
n
«
t
;<
:«
4S
R
r
1
S
1
t
r
o
t
4t
T
r
m
1
s
1
-
11
47
4
L
It
Z
ii
£
e
in
41
"
O
E
m
C
e
b
4
G
;
>«
It
f
!1
9
r
e
i
s
ii
P
f
4
1
;v
A
O
O
o
r
S3
S
R
)
1
%
M
S
M
1
S
A
"
3
M
O
2
\j
6
R
3
a
D
O
2
d
DATE
IP
^
• p
, ,e
s
f
Page
of CAR
i
1
S
^
HUM
n n n 74
cmti_
n , n
D
HER
7S 71 71 71
11 -
» '* -*
n M
CO
-------
9.3 Preparing Retrieval Selection Cards
To request reports from the Reporting Program, the Regional user must
prepare 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
to the central data center. In addition, the Report Request Form con-
tains 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
!0 Logic Selection Card
20 Report Format Card
30 Report Sequence Card
40 Quick Look Data Selection Card
50 Variable Milestone Data Selection Card
Card Ql - Title Card
Card 01 has entry spaces for the Card Code Number, Region, Level and
Report Title. The Card Code Number, 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 a Source Data Report. This column
may be left blank when 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".
Revised 12/79
-------
S - Source Only
Only source level information is included in the report—no
point or action data.
P - Point + Source
No action data is included in the report. Only those points
which match point and/or action level selection criteria are
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 included.
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 "19" cards) should include action record data
elements, or this level code will result in the same report
level as an S or a P level code.
The Report Title (columns 9-8i8> 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 identify 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 twenty 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
Revised 12/79
1:25
-------
are identified by the abbreviations shown in the box in the center of
the request form. For example, the abbreviation 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:
o 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 18.
o 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 con-
dition code of 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:
Data Element Cond. Value «" JUSTIFIED
M Lsrrsl Id
|l.°i \S.T.7.4
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 - Equal 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 5tf, 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.
1 7
Data Element Cond. ' Value
h.pj to.rsd l4l
o 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 alpha-
betic or blank, the results will depend on the exact entries
found in the data base. Letters will compare lower than num-
bers, and blanks will compare the lowest.
o P - Present-Any-Entry - 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-18.
o 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-18) 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 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 on up 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.
±27
-------
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 value may be made on the selection card
beyond column 18.
Note 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 entered. 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 region 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 input form. Entries
should be made in columns 4-5, 7-8, and 10-11. Start with the left-most
field. The available report formats are:
QL - Quick Look
SD - Source Data Report
AC - Action Summary
QT - Questionnaire
MS - Milestone
Q2 - Double Spaced QL
CA - Conpliancc Action
REPORT FORMATS
12 TT" ~r~r TS~TT M
PASSWORD (REQUIRED TO ACCESS CONFIDENTIAL DATA ELEMENTS)
±28
-------
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 his
password on column 14 of the Card 20.
Comments at all levels (source, point and action levels) will no
longer appear on any Source Data Report 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 four
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
In addition to these, certain other action types are confidential
for specific regions:
REGION ADDITIONAL CONFIDENTIAL ACTION TYPES
01 NONE
02 61, 62, 79, 80
03 65
04 B5, B6
05 26, 27, 31, 75, 77
06 A7, A^, E3, G3
07 32, 57
08 58
09 33
10 14, 22
Please be aware that confidential action types will no longer
appear on any reports when no password is supplied. Quick Look Reports
will not snow confidential action types. Milestone Reports requesting
action level data on the 50 card will not include any actions which have
confidential action types. Confidential action types will be missing from
all Source Data Reports. When confidential 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.
- p* Revised 12/79
-------
Card 30 - Report Sequence Card
The report sequence card permits the user to select the sequence of
entries on the reports he has selected. For example, sources might be
alphabetized 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 sequence—Action type (Action Summary
Report only) or Region, 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 block in the center of the page. For example,
to sequence by source name, "SNME" is entered. Care must be used in
limiting the length of the sequence elements to 4? digits. For example,
a sequence of Source Name (29 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 Code (1 digit), Active Passive 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 4/)-digit
limit.
It is important to note that in certain cases it is possible to
request a meaningless report because of illogical sequencing. For
example, 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 requesting a sequence of Source (Name or
±30
-------
Number) 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 Name).
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 problem.
Page breaks and subtotals are available on the QL report by placing
a number ranging from 1 to 6 in column 39 of the 30 card. For example,
if column 39 of the 30 card is left blank, no page breaks are produced.
A 1 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. A 3 in column 39 will produce a page
break on the first three data elements of the 30 card. Page breaks can
be obtained on a maximum of 6 data elements.
Example:
REPORT SEQUENCE
U.oj Ijjr.r.d K/n^.TJ \s,Mne\ I .
12 V 7 9 12 14 17 19
. I I . . . I \ i i i 1
22 24 27 29 32
SEQUENCE LIMITED TO 40 CHARACTERS
The above card will provide page breaks with
subtotals by state.
REPORT SEQUENCE
h.ol ISr.T,£|
12 4 7 9
12 14
SEQUENCE LIMITED TO 40 CHARACTERS
17 19
22 24
27 29
32
Number ol
111 tub»«l«lling
31 data alamantt
Number ol
|<4 iubtatalling
39 data •l»m»nt>
The above card will provide page breaks with
subtotals by state and by AQCR.
Revised 12/79
131
-------
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 action, 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:
|3,0| JJS r, T £| U*X/»g|
124 79 12
14
17 19
22. 24
27 29
32
39 dot. .|.m.M
Date Achieved (DTAC) may be substituted for Date Scheduled (DISC)
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
format 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 users desire the special sorting on
actions.
Revised 12/79
132
-------
Card 40 - Quick Look Data Selection Card
Card 40 provides a means to request specific data elements for inclu-
sion 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 required on the report. Data element abbreviation 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 QL print line length
is determined as follows:
o 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.
o 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 next to each selected data element in
the NUMBER OF DIGITS-4QT 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 to 40 Card require more space than is avail-
able on the 132 character print line, the QL will not be produced. Data
elements are printed left to right in the same sequence as they are
coded.
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,
source level data will print repeatedly for each point and action. Point
level data will print.
Revised 12/79
±33
-------
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.7. 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,
'BLNK.1 should be entered as the corresponding value on the 50 card.
Note that the 50 card will be rejected if a Milestone Report (MS) was
not requested on the 20 card. It is the presence of the 50 card that de-
termines that the Variable Milestone Report should be produced. If a
Milestone Report (MS) 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' an 01 Card.
2. Use a 10 Card to select the appropriate state.
3. Use 10 Cards to select the desired action types.
4. Code MS on the 20 Card.
5. Code the 50 card as follows:
MILISTONI REPORT FORMAT
[.LSI i^xr./l [&*&& UP.I. . I I*.** . i U7.3. . i i«Mi i 1 iffii i I 1 i i i I I i ' '
12 4 » 9 12 14 17 19 22 24 27 29 32 34 37 39 42 44
„
47 49 52
ROWS COLUMNS VALUES Of COLUMN DATA ILEMINTS (USE "SLNK" FOR BLANK VALUE)
DATA DATA
HEMENT CLEMENT
I . - . I I • • . I
54 57 59 «
This request will produce five columns of numbers, one column for each of
the selected action types. Or. the right hand side of the page, totals are
generated for all actions for a given county. One line is produced for
Revised i*/79
134
-------
each value of 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.
Up to ten 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 less
than four positions, the values must be left justified. If the data ele-
ment values to be totaled are greater than four positions, totals are pro-
duced 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 Regional
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 selec-
tion or the report printing of non-repeating data elements. The following
sections describe the changes to the selection, sorting, and printing of
repeating data elements such as Pollutant Compliance.
135
-------
9.3.2 Pollutant Compliance Logic Selection
Associated with each pollutant are the following data elements:
Retrieval
Name Abbreviation
o Pollutant PLLT
o Pollutant Compliance Status PCMS
o Pollutant Emission Category PECT
o Pollutant AQMA Indicator PAQM
o Pollutant AQCR Indicator PAQC
o Pollutant Loading LOAD
Whenever one of the above repeating data elements is used on a 10 Card,
each of the ten 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:
Source Source Compliance
A 4
B 1
C 1
Pollutant
PT
S2
PT
S2
HC
PT
S2
HC
Pollutant
Compliance
4
1
4
4
1
4
4
4
The following selection criteria will extract data for Sources B, C,
and D
10 PLLT M PT
10 PCMS M 4
136
-------
because each of those sources has the selected pollutant and the selected
compliance status.
The following selection criteria will extract data for Sources B and
C
11,01 j/.^n^i |/al |*i ...... '
because each of those sources has one pollutant out of compliance.
The following selection criteria will extract Sources C and D
ll.OI I fll. l.n lo| 1^.^. . i . . i I
since those two sources contain hydrocarbon data.
Because the selection criteria for repeating data elements are applied
independently to each group of data associated with a pollutant, the
Condition 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 regu-
lations and are also out of compliance with S02 regulations. Users will get
no hits with the following selection criteria:
|l.0| \Ptt-tt.tri fct| \f\fj i f • ' ' I
H , oj [
9.3.3 Pollutant Compliance Sorting
Quick Look Reports may be sorted by whatever data elements the user
needs. Page breaks and sub-totals 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:
137
-------
1. Facility Capacity and Regional Data Elements.
2. If any data exists for particulates, SO-, hydrocarbons, CO, or
NOX, the data will always be printed in the following order:
PT, S2, HC, CO, N2.
3. 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; otherwise,
changes to 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
pollutant 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.
The restriction of not printing point or action level data when
pollutant data is printed 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
138
-------
in one direction and repeating pollutants in the other direction. Also,
requests may be made for repeating pollutant data items in both directions.
For instance, users may need a milestone with pollutants as the row data
element and pollutant compliance as the column data element.
Due to the fact that 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 to-
gether 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,^ Filled-in Retrieval Request
The Quick Look Report shown in Figure 9-2 were obtained by filling
out the Retrieval Request Form shown in Figure 9-11.
The Source Data Report shown in Figure 9-3 was obtained by filling
out the Retrieval Request Form shown in Figure 9-12.
The Milestone Report shown in Figure 9-4 was obtained by filling
out the Retrieval Request Form shown in Figure 9-13.
The Variable Milestone Report shown in Figure 9-5 was obtained by
filling out the Retrieval Request form shown in Figure 9-14.
The Questionnaire shown in Figure 9-6 was obtained by filling out
the Retrieval Request Form shown in Figure 9-15.
The Action Summary shown in Figure 9-7 was obtained by filling out
the Retrieval Request Form shown in Figure 9-16.
The Compliance Action Report shown in Figure 9-8 was obtained by
filling out the Retrieval Request Form shown in Figure 9-17.
The special PSD Report shown in Figure 9-9 was obtained by filling
out the Retrieval Request From in Figure 9-18.
. , Revised 12/79
\ *
-------
uu
Rs
|0|1
1 2
LJ,oj
1 2
1* |O|
HiO|
11.01
II.QI
•11,01
n,o|
H.QI
U.QJ
LLL2J
|i,Q|
HL£J
I'.QI
L ' i o.l
REPORT
[3,01
I 2
REPOR1
1 2
Cf -'•£>
QUICK
1 2
MPLIAWUt DATA SYSTEM
port Rsquest Form 8MSS
4.5 J S 20 '20' ' ' ' ' '
t»ii«» .U»«4. I.pm fit|. 1 — t_j_ i . i i i
S) (1
LSTTift&l Mi iTL, , , , | , |
4 7 S 11 U
Data EUm.nl Cond. Volu» !l«lt Jui.l f i.d )
IHiliJrjC 1 1^1 iQT-i | ijj.il rnMDTTTPM rnnrc Mn rflnn>
1 •*•""' -*™J LUnLU 1 lbft tUULi ^IU UAKU/
lA.rr.P.g'i iKi ioM. , , , i M - MUST EQUAL
lAiT.P.Fl l^sJ (0,^, . i , i i | A - fi| TFPNATF {Used for
lAiT.P.gi IM 10 ,5, .,,,,! Multiple Values of a
A pp. » -. Given uata tlement)
Arr.pgi to fill. i u - UNEQUAL
'A1 M^l5l IM 'UrtSt L l i i i J G FOIIAI DP nRP/\7FR THAN
&TJ?.e'i IM n.l, , , , , , j
L - EQUAL OR LESS THAN
1- ... I 1 J i ,,,,,, I
1 . . , IM ,,,,,,,( P - PRESENT ANY ENTRY
1 ' ' ' 1 U 1 i i i i t i i 1 B - BLANK OR ZEROS
' ' ' ' 1 1 J ' . i i j, i i J
1 - 1 . i J 1 J i . i . . . . 1
.... , See reverse side for a
i.,..i ,.i ..L ,,.,_j nst of all COS ddta
1 . i i 1 1 1 i i . i j i i 1 elements and thpii*
. , , , i abbreviations.
1 1 l i 1 1 1 1 l > 1 i ! L 1
1 < i i | 1 1 1.1'JliJ
1 1 1 1 | 1 J 1 l I t 1 , 1 |
FORMATS
&Ll LJ_| L^J 1 , |
4 S 7 S 10 U i« " 21
r SEQUENCE PASSWOIO (REcuiREO re ^cciss ccr:c::E;riAL OATA ELEMEKTSJ
iSiSJ^E 1 , , , J I , , , i l , , , j i L , , | [ , , , i
4 75 12 14 17 19 22. 24 27 29 12
CE LIl'ITij TO -0 CHARACTERS
LOOK KEPO2T fOAMAT
lS'Q\.£>J !Sn4r i > i . i i . ..I i i i 1
40 50 52
7t jo
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
Q2 - DOUBLE SPACED QL
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
LEVEL CODES (01 CARD)
REQUIRED FOR SD REPORT ONLY.
VALID ARE:
A -'ALL DATA
C - CRITERIA MATCH ONLY
P - POINT & SOURCE
S - SOURCE ONLY
Numb.r of
1 j iub.olol 1 in,
39 data .l.m.nli
_
« 7 9 " M " IS 22 24 27 29 32 34 37 39 42 44 47 49 52
Enter ;»ti E1e~nts to be Included on «eport
LiXted to 13? Ch«r«ctrrs xlth *MI rtptton: I II 1 I II . . t ,-J ,
H^tr* fn IIP Ulfh 'f.nrtiril H..H'n. IJlIltlllllllll 1 i I . 1 1 1 . i 1 1 *-i
"" """ "" ' 54 57 51 O (4 S7 S9 72* 74 77 19"
With NOHD Only !u;cre
-------
COMPI1AMCE DATA SYSTEM ^9-12
_ r ' DATE SUBMITTED_ TIME.
Pi0 p0rt Request rOrm RETURN REPORT TO
KAIL STOP
i.3>».R. A.C.T.XI
i j
12 4. S 7 I
tt-'ten mlr~r*l. C*f~*rt Ti.U
n.oi iA.T,P,gj i&j Q2
TZ 4 7 9 11 , }l
Dcto EUm.nl Cond. Volu« U«lt Juitill.d)
n.oi ift.r.p.a ift
11,01 ftrr.fi.gi i&]
20
1..J—I—U
1 • I 1 L_J—J L I 1
40
Q I&J h.K. ..... I
ii.oi lA.T.9,gl iftj l*Tl I
3 tftl LC2. , . . . . J
n.oi for.P.gl ifil tos3. i.
n.oj iftrr.P.gi [ft] QTL •_ • • • •
J LJ L1
I LJ I i
iijQj i i i . i LJ I i i i . i • i
n.oi i .... i U I i . i i i i i
I . i i j 1 I I i . i i ' . .
i . . . l U I • < - -
. i U 1
, , i u i • ....... -l
I'.QI i . . . i LJ 1 i i i i i i i .J
i , i U I., .-j
RtFORT (CRVITS
la oi £a£
12 1 S 71 10 11
REPORT SEQUENCE
| i . . i l . i - 'I—I L_l—I 1—I—L.
10
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE (Used for
Multiple Values of a
Given Data Element)
U - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - BLANK OR ZEROS
See reverse side for a
list of all CDS data
elements and their
abbreviations.
14 Jl
PASS wo ID (;;;L';?.i3 TO ;:CESS c;i.r;criTiAi. DATA cU"£.',TS)
i ii i i l . >
, I I I I I I 1 I I 1-1 L
T" S TT 14 17 19 22 24 27 29 32
; TC 43 CH--irc=.S
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
Q2 - DOUBLE SPACED QL
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
LEVEL CODES (01 CARD)
REQUIRED FOR SD REPORT ONLY.
VALID ARE:
A - ALL DATA
C - CRITERIA MATCH ONLY
P - POINT & SOURCE
S - SOURCE ONLY
Number ef
| j sub.»letIt ng
39 d.l» ...m.t.11
GUICX ICCK 1IPCST FORMAT
III
i . i
ill! I i i i
I I I I I I I I
1 24 79 12 14
En'.fr Citl El^~-nt5 to b« Incluirtf on f-oort
U^Hfd to 13? "'jriclers "Hh *X> fiptlon;
It 19 22 24 27 29 32 34 37 39 42 44 47 49 52
I ... I I . . . .1 LJ
EJ 7} 74 77 *«
W.lkNOMD Only :.::-».£-3.'
54 S7 SI
(4
MILESTONE ZIPC4T
!J_9J
TT 1 r T U T4~ 17 19 22 24 27 29 32 34 37 35 42 44 47 49 52
«0wi CO1UMNS VALUES C» COLUMN CATA ELEMENTS (l!« "iC-'." r" =.:•.» ,;_'.£' , i i
I 1 i i I I . . . .
CATA DATA
141
-------
COMPLIANCE DATA SYSTEM
Report Request Form
FIGURE 9-13
DATE SUBMITTED_
RETURN REPORT TO.
MAIL STOP
.TIME.
1 2
LI, P|
1 Z
45.7
IA.P.C.PI
4 J
t
*f
S
20 30 40
*• Ti"» ' i ' ' i ' --" J J ,.,.,,,,
5J (0 }«
fl. ..,,,, 1
n ft
-V-'S2
K
|1,0| | , ,
11.01 I , ,
U, 0| L , ,
U, 0| | , ,
11. 0| I , ,
LI.OJ i , ,
H.Ol I , j
11,01 [ , ,
•|1,0| L , ,
H,01 | , ,
11.01 f , ,
11,0] i i ,
|1,0| 1 , ,
l«.0| 1 , ,
il.Oj L , i
11. OJ L . ,
r,ci , , .
H.OI | , ,
I'.oi j , ,
_jJ U
•II!
.Ill
.ill
,ill
,lli
-j-J U
-U LJ
.j-J U
, j i j
, i i I
jJ U
-U U
' J LJ
,iii
, i i i
.ill
-L_J U
-LJ LJ
1 , I
,
,
t 1 f
1 1 1
1
' . t
\ 1 ,
1 I 1
1 1 1
I , t
t 1 .
1 1 1
1 1 1
1 1 , , 1
• . , ' J
1
1 , , . j
, , , , J
1 , , , J
1 , . , 1
1
i , . ,J
, . . , 1
, . . 1 1
, . , , 1
, . . . 1
, . , . 1
1 , , , J
1 , . , 1
REPORT FORMATS
LltPJ
y, z
i^W W
REPORT SEQUENCE
Ii2l I ... I I ... I I ... I
12
7
LINITE: TO «o :HA
12 U
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE (Used for
Multiple Values of a
Given Data Element)
U - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - BLANK OR ZEROS
See reverse side for a
list of all CDS data
elements and their
abbreviations.
j
17 13
J I . . .
ELE»E;;TS)
-
n. 2*
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
Q2 - DOUBLE SPACED QL
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
LEVEL CODES (01 CARD)
REQUIRED FOR SD REPORT ONLY.
VALID ARE:
A - ALL DATA
C - CRITERIA MATCH ONLY
P - POINT & SOURCE
S - SOURCE ONLY
27 29
Sumb.r el
.ub..,.llin,
QUICK LOOK XEPORT FORMAT
Lliil
12
1 ' j I I I I I I I > I I I I . , J I J 1 I J 1,1,1 Ll 1 I I [..1.1 I I I 1
7 9 12 1417 1} 22 24
Enter Oati Clmnts to be Included on Report
Limited to 132 Characters with WHO Option;
Ltilted to 110 With Standard Htidtn*,
...
27 2» 32 J4
I
I i . ,
17
42 44
47 49
54
57 51
ST («
I ... J I . , , I
<> 72 74 77
WithNOHD Only
MILESTONE REPORT FORMAT
[JLPJ I • • .J I ... I I ... I I ... I I , , . I I ... I I
7
ItlMENT
12 14
17 19
22 24
27 29
32 34 37 3$
COiUMNS VALUES OF COLUMN DATA ELEMENTS (.SE "5i.:,r ?:? " ;; K VA'L"'
OAtA
lllMINt
42 44 47 49
I ... I L_
54
59
-------
COMPLIANCE DATA SYSTEM
_ -. . r DATE SUBMITTED_
Report Request Form RETURN REPORT TO.
FIGURE 9-14
TIME.
MAIL STOP.
iQ,i| igjji LJ
12 4. 5 _ 7
t»fi*« .IffwC
ti.oi IA.F.C.PI
124 7
Omit fl«m«nl
H.OI I ... I
11.01 \ , , 1 I
.E.E..S.I.O.H. 3. .H.s.p.s. .c.o.rt.p.L.i.M.c.e. .M.
t 20 » -
..
. .11 I
9 11 it
C.n4. V.lu. (l^t Ju.tlH.i)
IlPJ I • - •
Ll.0.1 L
n.oi L
li.oi L
M.OI i_t y
11,01 I_j _,
|i.oi l . .
11,01 L
11,01 L
H.ot L
li.oi I . .
U,QI | , i
i.oj l.i.
li.QJ L
LLiPJ ' • '
U (_•_
Ill,
III,
U Li_
U Li_
U LL,
U U.
LJ U.
U U.
LJ LJL
U LL.
U LL.
U La.
U U.
LJ U.
U U.
U U
U U
III.
t i t t i i I
.,.,,, 1
i
, i t . i . l
I
...,.,i
i i i i i i 1
L_. , , , , 1
LJ . , , , 1
, 1
1
, 1
. . , . , 1 1
1
1
...... 1
it),,,!
...... 1
l 1 L i i 1 1
REPORT FORMATS
lllPJ l^S
12 45 7 I
REPORT SEQUENCE
w
S3
• ' '
(I
...
»•
i— i — i
. I I I 1-1 I
i — i
I — I
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE (Used for
Multiple Values of a
Given Data Element)
U - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY .
B - BLANK OR ZEROS
See reverse side for a
list of all CDS data
elements and their
abbreviations.
KU>.S, . . '. . -I
14 21
PASSWOIO (REQUIRED TO ACCESS CONFIDENTIAL OATA ELEMENTS)
124 J
StCUEMCE UNITED TO
I ... I I . . , I I . . t 1 I ... I I . . . I
22- 24 27 21 32
t 12 14
ao CHARACTERS
17 IS
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
Q2 - DOUBLE SPACED QL
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
LEVEL CODES (01 CARD)
REQUIRED FOR SD REPORT ONLY.
VALID ARE:
A - ALL DATA
C - CRITERIA MATCH ONLY
P - POINT & SOURCE
S - SOURCE ONLY
Nwmb«v •!
I I lubtellM.af
U 4ml* >Um«nU
QUICK LOOK REPORT FORMAT
I ... I I . t . I I . . .
1 2
4 79 12 14 17 19
filter D»t» Elownts to be Included en ««port
to 132 Chiricters with HOMO Option;
to 110 With Stindard He»41nf
J I
22 24
J I
27 29
J L
32 34
37 39
J I
42 44
J_! La.
47 49
52
54
, . . I I . . .I I ... I I ... I I ... I LJ
57 S9^ ST 14 «7 19 72 74 77 Tl
2 Stocs
with NOHD Only Sucpression
MILESTONE REPORT FORMAT
|5,0| 1 , , , I I , , , I
1 2
4 7
tows
DATA
EllMI NT
I ... I I , . , I I ... I I i i , I I . , , I I i l I J I i J,.. I
27 29 32 34 37 39 42 44 47 49 52
9 12 14 17 19 22 24
COLUMNS VALUES OF COLUMN DATA ELEMENTS (USE "SL.'iK" FOR SLAtiK VALUE)
DATA
IUMINT J^g
54
_
S9
•J
-------
COMPLIANCE DATA SYSTEM
Report Request Form
FIGURE 9-15
DATE SUBMITTED_
RETURN REPORT TO,
MAIL STOP
.TIME.
LO.II
12 4.5^7
«•*«• .
30
LJ iA.C.T.t.O.N.S. .S.C.H.6.P.U.L.6.P. .B.U.T. .N.O.T. .A.C.H.I.e.V.E.D.
nil*
|C.A. . . .
' ' ' •
' • ' * '
i
n.oj iS.T.A.Bl [t*
124 7 ] 11 U
Data tUm.nl Cond. Vllu* licit Jultlfl.d )
il
40
' ' • ' ,
|I,0| |P,1
11,01 |P,1
H,O| [0,1
H,oi i ,
M,O| | i
H, O| | ,
n,oi i ,
H, 0| | ,
L',0| LL
It iO| I ,
11,01 | ,
11,0) | i
11,01 | ,
H, 0| | ,
11,0) | ,
L'.oj t ,
r.ei , ,
I', 0| | ,
l«,oi i ,
",s,cl
',s,c(
f,A,C|
, . l
i i i
i i I
i i 1
i i 1
< , l
1 i j
• > J
, i ]
> ' J
i t (
i , j
i , }
i
i i l
i , j
Lftl 10,6,0, 1, ?.q. , 1
LL| |j,| ,9,|. •?,
-------
COMPLIANCE DATA SYSTEM
Report Request Form
FIGURE 9-16
DATE SUBMITTED__
RETURN REPORT TO.
MAIL STOP
.TIME.
.0,11 MJ LJ ift.t.T.I.O.N. .S.U.A
12 4.5.7 »
.R.Y. .F.O.*. ,N,E,S,H,fl,P.5.
TilU
ii.oi ifVr.P.E.1 ifij
124 79
U
FT
20
30
, i i
S3
40
i I i,.i i. l
si 42
10
|i ,0| HVT.T-.&I |«-| |W,4 |
11,01 I , ,
H, 01 i , ,
|1,01 | , ,
H, 0| | , ,
H. 0| I , ,
H, 01 | , ,
H, 0| I , ,
H, 0| | .
,,,0| | , ,
ll,0| | , ,
11)0] | , ,
|1,0| | , ,
M,0| | , ,
LllOJ 1 , .
M,0| ! , ,
r.ci i , ,
I'.oj i , ,
I'.of | , ,
.MM 1
.Mil i
M 1 1 I ,.,,,,, 1
Mill 1
, | 1 I 1 1
Mill
i | 1 1 1 ,,,,,,, 1
M 1 1 1 i ...... 1
M ' 1 1 1
± | L J 1 1
Mill , 1
ij 1 1 1 i , , i . , i J
M 1 J 1 • . • i - ' - 1
Mill, 1
, M 1 1 , 1
Mill I
M 1 1 1 , , , , , , M
Mill,,,,,.,!
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE (Used for
Multiple Values of a
Given Data Element)
U - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - BLANK OR ZEROS
See reverse side for a
list of all CDS data
elements and their
abbreviations.
REPORT FORMATS
LliSJ ift.Cl I . I I . I !C.P.S
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
Q2 - DOUBLE SPACED QL
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
LEVEL CODES (01 CARD)
REQUIRED FOR SD REPORT ONLY.
VALID ARE:
A - ALL DATA
C - CRITERIA MATCH ONLY
P - POINT & SOURCE
S - SOURCE ONLY
12 4 5 7 J 10 11
REPORT SEQUENCE
h.al IS.T.T.BI |S,N.W,6|
124 79 12
St:ilE:iCE LIMITED TO 40 CHARACTERS
QUICK LOOK »IJ>0«rfORMAT
l«,o| 1 , , , 1 I , , , I
124 79 12
14 Jl
PASSWORD (REQUIRED TO ACCESS CONFIDENTIAL DATA ELEMENTS)
1 , , , 1 1 ... 1 1 ... 1 1 ... |
14 17 19 22 24 27 29 32
1 . i i 1 1 i . ,J 1 . . . M i , i J 1 , i
14 17 19 22 24 27 29 32 34
u
39
jj L_J
37 39
Xumk.i of
lubt*l«ll i«f
da.a •|«m«nt»
1 1 1 1 1 1 1 1 1 , , , 1
42 44 47 49 52
Enter 0«ti n*-»nts to b* Included on leoort
U»U*d to 132 Ch«r«cten with IOO Option;
U«Hrt to 110 MUti Standird
54 57 SI
R
I . i . I I . i . I I , . . I LJ
14 »7 «9 J2 74 77 IT
"i" Stoos
WHhNOHO Only Succress-cr.
MIlISTONt REPORT FORMAT
lL£J I • • i.J l.i.l I ... I I ... l I ... I I . . . I i , , , l L_t
124 79 12 14 17 11 22 24 27 29 32 34 37 39
ROW* COIUMHS VAIUU OP COLUMN DATA ILIMINTS (USE "SLSIT FOR BLANK VALUE)
DATA DATA
ElIMfNT [LIWENT
jj I ... I I . . . I
42 44 47 49 S2
I . . . J | , . .
54
57 S9
-------
COMPLIANCE DATA SYSTEM
Report Request Form
FIGURE 9-17
DATE SUBMITTED_
RETURN REPORT TO.
KAIL STOP
.TIME.
to.yj
12 4.5'
LJ
7
i iii i
i i it i
Till.
IT.OI i ...
124 7
LJ I I
9 11
II
Dole |ttm«n« Cond. Volu« U«lt juitlfi«4)
i.Ql I . .
ii,or L
H.oi L
HiQ] L
i.oj 1.L
H.oi L
1
tllOJ I l l
11,01 L
P.OI La.
li.oi I . .
1
1 1
1 ]
I 1
1 1
1 I
1 1
1 1
1 1
I 1
1 1
1 1
1 1
1 1
1 i
1 I
I 1
1 I
! I
U
1 i i i t t t t 1
i i
! l
1 . 1
i i
1 ,..,,,, 1
1 ,.,,,., 1
1 , , I
1 1 i t i 1 l 1 I
1 ,,.,,., 1
1 , 1
l'i .,,.., 1
1 . . . i . .it
1 ,,,,,,, 1
1 1
1 i i . . i . j 1
1 ,,,,.,, 1
1 i i < i i i i 1
1 i i i i . i i i
REPORT FOFK»TS
L?aOI CAl
12 * S 7 *
REPORT SEQUENCE
U.ol terra
124 7
20
38
40
I I i J_ I 1
SB 52
i J I I t I I
SI
(I
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE (Used for
Multiple Values of a
Given Data Element)
U - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - BLANK OR ZEROS
See reverse side for a
list of all CDS data
elements and their
abbreviations.
10 11 14
FASSVv'olO (SEC
12 J4
71
:R-; TO ,=:CESS cc:.f;:£;rr:Ai OATA ELi
I I ... I I ... I
17 19
70
10
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
Q2 - DOUBLE SPACED QL
SO - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
LEVEL CODES (01 CARD)
REQUIRED FOR SD REPORT ONLY.
VALID ARE:
A - ALL DATA
C - CRITERIA MATCH ONLY
P - POINT & SOURCE
S - SOURCE ONLY
22. 24
27 29
Hu
I ] tuh
29 <*«<
CUICX t-CCK *£?ORTfCRMAT
«,OJ ! , j , I I I II I I I I I I I f . i J I ...
J I
J J . .
I I I I
124 79 12 14 17 19 22 24 27 29 32 34 37 39 42 44 47 49 52
i*!ttS to 13? C^^^^ctf^s .ltd IOC Option;
-!t-4 to 110 "Hh SUr-iird Kr.dlnj
I , . . 1 I . , . I I ... I I ... I I . . . I U
54 S/ £1 S2 J4 S7 £9 72 74 77 ,»«c
With HOMO Only J_.:;~-s.s•;,-
MILESTONE
JS.OJ I ... I 1 i , j.J I , . , I I . , , I I ... I I , . , I I i i . I I i i , I I , .
124 79 12 14 17 19 22 24 27 29 32 34 37 39 42 44 47 49 52
1 . . . 1
»OWi C01UMHJ VMUES OF C3lli'MSbATA{UMENTS (C~- "EL1.'.- ?Cf ELAM' Vi' L">
.»*!*... .B.V.!.. 146
-------
COMPLIANCE DATA SYSTEM
Report Request Form RETURN^?™
io,ti i^^i iii.. .TTSX/f;^. ,A^L£
1 2 4 5 7 » 21
R*»MII ,1ml IqMrt mi*
124 7 9 11 U
Data ll»m«nt C*«4. V«li>« fu«» Ju»lll»d )
I'|O| 1/^,-nAi'! 1/41 UC2t ,iii,l
n.oi i^,Tv»,iri 1^1 1.77.3 i
n.oi i/ftTfy,*i i>fl br*/. ..... i
it ,01 i/-,r,p,i| l*l LTTfi . , , , , 1
n,oi \A-\r ij><£{ \A\ \y,A* , , , , , I
n.oi uf,r;j»i£| Wi Lrijr, . i , , , i
l'jO| l/ftTTAtfl 1*1 Ltf*, , i , , i 1
li.oi \ptr,^&t IP! 1 i
LLO] l ,,, i 1 1 L ,,,,,,, 1
H,0| 1 , , , ] 1 1 1 , , , , , , , I
n,er l , , , i 1 1 1 1
1 1 jO| | i , , ] | | | i , , , , , , |
n.of t , , , i i i i , , , , , , i i
[>,0| I , , , I 1 I I , , , , , , , I
|1,0| | , , , | | | | ,,,,,,, I
1' ,O| | , , , | I | | , , , , , , , |
n iOt i , , , i i i i , , , i , , , 1
l',o| l , , , i t ! I , , , , , , , 1
n,oi i , , , i i i i ,,,,,., i
REPORT FORMATS
FIGURE 9-18
TIMF
rn
> s?*e~/±,'rv Jirs+ruf* , , , i
I (30 40 U »i
i,ii,,,(..iii,tiiii,,,ittii,l
S3 «l 7* tO
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE (Used for
Multiple Values of a
Given Data Element)
U - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - BLANK OR ZEROS
See reverse side for a
list of all CDS data
elements and their
abbreviations.
. 1
12 45 71 10 II M JF
REPORT SEQUENCE PASSV»O«0 (REQUIRED TO ACCESS CONFIDENTIAL 3ATA ELEMENTS)
[3.0! \Srt~d 1 , . L 1 1 , , , 1 1 , , , I 1 . , , 1 1 . . , 1
1 2 « 79 12 14 17 19
SMUEHCE LIMITED TO 40 CHARACTERS
QUICK LOOK RIPOXT FORMAT
!4,o| i^^^iS} |e,yiVi/^l iSiTw^ifli \&f
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
Q2 - DOUBLE SPACED QL
SO - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
CA - COMPLIANCE-ACTION
LEVEL CODES (01 CARD)
REQUIRED FOR SO REPORT ONLY.
VALID ARE:
A - ALL DATA
C - CRITERIA MATCH ONLY
P - POINT & SOURCE
S - SOURCE ONLY
Mvmb.r •!
tvk«*t«llm«
h«r,/& \A,r,f
124 7 9 ' 12 14 17 19 22 24 27 29 32 34' 37 39 42 44 47 4J 52
Entsr Data Elements to t)e Included on Seport i III
Limited ta 132 Characters with NOHO Option; Limited to 110 mth Standard Heading 5^ ' 'jj ^ffi~
•2" Stoos
WlthNOHOOnly Sjccress'or.
MIIISTONI IMPORT FORMAT
U,oi 1 , , , 1 I , , , | | , , , 1 I ,
i i I 1 . , , 1 1 i . . 1 1 i i > 1 , , , 1 1 , , r 1 I , , , 1
124 79 12 14 17 19 22 24 27 29 32 34 3
lows COlUMNS VALUIS OP COLUMN PATA fUMINTS (USE "BLrtt" FOR 3U«K MLU
DATA DATA
lltMtHT IKMtNr
r 39 42 44 47 49 52
E) 1 1 1 1
1 , i , | 1 . i , 1
54 57 59 5}
147
-------
9.4 Job Control Language for Using Retrieval Program
The CDS Retrieval Package operates on a Remote Job Entry (RJE) basis
V
at COMNET. Input must be submitted from a high speed terminal (frequent
and complicated requests might be stored on a WYLBUR data set). To sub-
mit a job request, only two JCL cards are needed in addition to the
COMNET job cards and the necessary, 01, 10, 20, 30, and 40 cards. No
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 COMNET
Users Manual for additional routing information.)
To execute the Retrieval Program, use the JCL as shown in Figure
9-19. In addition to the two JCL cards shown, 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. Re-
quests for multiple reports and Source Data Reports are likely to need
more time and more lines. Refer to the COMNET User's Manual for detailed
information about the Job Card. Figure 9-20 shows a job card for multi-
ple copies; Figure 9-21 shows a job card for 100,000 lines of output.
148 Revised 1/80
-------
AUTHOR
//
/¥
/*
//
//
a i
1 9
2Q
30
40
//
/*
E
R
C
R
E
P
O
N
T
0
A
U
T
V
F
1
T
L
,
TRC
i
E
S
i
Y
C
S
Ml
10
P
D
:R
II
R
S
1!
J
1
E
5
i
a
r
n
13
O
N
E
X
i
a
r
n
14
B
T
X
E
D
i
a
p
IS
C
C
D
a
li
(
R
II
a
V
C
¥
it
a
T
D
I
I
I
I:
VI
fi
II
a
r
S
l
LI
N
a
r
R
Ml
HI
III
III
D
i\
PROGRAM NAME RETRIEVAL JOB CONTROL
21
T
t
I
I
I
VA
li
n
M
V
SE
SE
IE
IE
.U
ir.
n
i
n
i1
l1
c
I1:
S
,
14
i
At
Nl
SI
Al
Rl
T
II
If
SI
V
C
El
1
R
•
11
E
U
111
K
41
1
LI
I
U
3f
>C
12
R
;i
iY
il
Cl
$
IR
S
11
H/
.Rl
HI
Hi
0
U
01
A
N
M
1
Vf
1
|
VI
HI
I
0-
E
1
^
D
t
.(.
V
I
f
1
IS
6
C(
ft
1C
/
«
II
1
It
C/
S
a
)E
E
Tl
n
11
it
i!
«
IL
1
;
C
F
I
u
T
Tl
•
1 1
I
U.
Cl
l
G
V
M
1
Tl
Ul
At
(
HI
EC
S
IR
IL
«
V
1
J
p
)
41
E
:A
)
0
K
f
F
?-
jj,
1
42
:
0
U
(A
A
Rf
41
1
Nl
«
-19
t
01
44
V
rE
T
45
P
N
;0
TASK NUMBER
«
R
H
.
41
T
El
41
Y
s.
4!
:
l
»
2
r
SI
a
»
P
1
»JS4
AS
y
l
ssjst
sjy
s
»l
»
O
t
44
RiD:
0
1*
lid
r
12
p
U
P
M
P
CS
M
i;
M
ts
n
71
12
11
-
14
75
TS
n
n
nm
t
-------
AUTHOR
//
/*
/*
//
//
//
/*
E
tf
C
R
Bf
E
P
O
N
T
0
A
U
T
V
F
i
T
L
.
A
IRC
PROGRAM NAME ....RETRIEVAL JO" COHTROL
TASK NUMBER | 3ATE
JCL for obtaining 3 copies of retrieval output
i
E
S
1
i
y
e<
-
C
S
|e
It
P
D
a
>t
it
R
S
0
r
it
i
1
E
5
r<
YD
i
a
r
n
U
O
N
E
X
ft
ei
i
a
T
-
14
B
T
X
E
D
In
B:
i
a
|i
IS
C
C
D
ip<
a
__
tl
(
R
ii
-
II
a
V
C
*
Cf
i.
ti
e
U
V
V
tl
.,
Ij
,,
1
1
n
i
n
e
i
t
I
1
M
1
lb
ii
:c
!U
eR
na
Rl
H
i
V
;1
>u
)t
.0
IV
n
2C
.
1
e
>r
LE
2?
CI
ni
R«
in
F
'A
It
c
nb
p
be
C
n
ir
•r
M
c
Rl
01
38
Ml
>r
(
11
3
e
s
9
»
»
)
u
a
_
:R
U
-6
e
2
IL
H
»
f
:o
n
FC
If
U
»r
.e
I
N
S
a
Hi
.17
E
i
y
,T
11
R
st
11
r
JD
0
i
E
40
1
ra
;o
41
D
ei
u
'I
42
0
B
:s
43
e
ar
44
T
in
IS
1
b
«
V
r
h
-------
AUTHOR
TRC
JCL
WCC
f 2
//
A
/*
If
( /
II
1*
3
E
R
C
R
le
E
4
P
0
N
T
;r
b
s
A
U
T
V
C'
F
1
i
T
L
f
a!
;
i
E
S
>
I
i
Y
«t
i
C
S
le
PROGRAM NAME RETRIEVAL JOB CONTROL
TASK NUMBER >ATE
p»g»
of
for allowing up to 100,000 llnee of printed output. Without thla (pedal Job card, the
default value la 20,000 lines.
II
P
D
t
II
R
S
E
rt
Cl
n
1
I
'
X
•
re
Wi
i
a
r
n
p
I)
0
N
E
E
1
!T
i
a
r
p
H
B
T
X
C
D
m
!t
i
a
^
»
<
C
D
e<
a
p
II
a
R
C
*
it
i;
a
V
D
ce
1
1
t
t
II
a
T
S
y
II
a
r
R
a
h<
hi
hi
hi
29
a
r
T
t<
i
(
\
II
V
r
0i
BE
CM
n
V
N
:h
,
r'
i
a
I
ff
24
1
b<
n.
c<
p(
Tl
n
I
v<
t;
Ol
1,
1
II
»
J
al
nt
n
1C
VI
2?
:L
1
n
Ml
1
IR
»
I
C
n
ih
n
N
PI
r<
ei
f
r
30
n
PI
q
nt
11
r
fl
^
n
w
1
rn
?
H
u
•
f
1
H
U
|
Cf
^
S
f
III
(2
.•
o
:t
43
T
V
a
44
t
Y
I
1
M
if
nl
1
||
E
0
rli
4;
s
>*
•o
41
t
01
ill
41
7
a'
H
P
ffi
I)
R
8
«
T
,
S3
Y
fl
H
••
Nl
H
4
,e
M
:?
$;
P
SI
A
-
H M II 12 13 H 1
SS\ORD:
- - •
1 N 17 II M n 71
P p pp
CARD
NUMBER
73
4
75
!77
71
TIM
-------
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 possibil-
ities, and the action taken by the system if an error is detected.
Revised 12/79
152
-------
TABLE 9-1
RETRIEVAL PACKAGE EDITS
Card
Type
01
10
20
30
40
50
AL
Item Checked
Level
Region Number
Number of 01
Cards
Data Element
Condition
Value
Number of 10
Cards
REPORT FORMAT
Number of 20
Cards
REPORT SEQUENCE
DATA ELEMENT
SEQUENCE LENGTH
QUICK LOOK DATA
ELEMENT
QL Length
Number of 40
Cards
VARIABLE MILE-
STONE DATA
ELEMENT
Column Values
Relation to
other cards
Number of 50
Cards
General CARD
TYPE
Correct Possibilities
Blank, S,P,A,C (Default = A)
Required for Standard Mile-
stone
One or none
Listed on Input Form
M.A,U,G,L,P,B
(1) Anything
(2) Numeric for "numeric"
items, i.e., REGN, SITE,
CNTY, SRCE, PTNO, ATPE,
DTSC, DTAC, STAC
(3) Number of Digits less
than or equal to num-
ber of digits on Input
form
0-20
(1) QL, SD, AC, QT, Q2, MS CA
Up to three reports are
available from one retrieval
1
List on Input Form
Total 40
List on Input Form
Total length (including one
blank between each item)
1^2 with NflVmr 110 without N(
(1) 1 if QL FORMAT requested
(2) 0 if no QL FORMAT
List on Input Form (BLK1,
BLK 2 EXCLUDED)
must be present
(1) MS not requested on 20
One or none
01, 10, 20, 30, 40, 50
Action if in Error
If SD format requested,
it is ignored if blank
or other
Fatal - Processing
stops after EDIT
Only first 01 card ac-
cepted
FATAL - Processing stops
after EDIT
FATAL - Processing stops
after EDIT
(1) Ignored if not blank
for condition P or B
(2) FATAL - Processing
stops after EDIT
(3) Fatal if the wrong
length is used
FATAL - Processing stops
after EDIT
(1) Processing will con-
tinue if at least one
valid FORMAT
FATAL - Processing stops
after EDIT
FATAL - Processing stops
after EDIT
FATAL - Processing stops
after EDIT
QL Format Request ig-
nored
QL Format Request ig-
nored
HT)
(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
-------
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-22
shows a typical Retrieval Edit Report.
154
-------
X
a.
X
w
c
i
UJ
M*
X
w
•X
•a
a
UJ
99
*•••
«4
aJ
U)
«t
_J
a.
X
o
u
9
<\,
^
-
89
U.
X
UJ
al
•a.
" - ~ c _
z
.J *• "•
uJ < Z •-
U/ DC Jt *~
_J U- U. > U.
*• < 9
I/* z< ZZ^^ZZZZZ U.'U»'
— u >-L>UUUUUUUU a c •-
C£< ^J ^ *
X
a.
z
z
o
»» •«
z w
»4 CL
0 0-
a. <
z •-
a s
«o
to _j
I C «~
W UJ f
. z co
UJ "* **,
X 0. —
2 ^*
en x ^
* ™J a"J
>• «J *l
Z -J i »-
3 •*• Z
J > « jj
. c a c u.
U. UJ >- i.
>- CO u^ _) Z
« x r — a
a. r- z z
• 3. <-i J- <
CO CO « CO
f- C5 u. *-
Z UJ Z Z Z
^ "j* *"^ ^ ^
X Z « 3 0 Z
Un M ^ >_
j ta*^-CO tfS1"^^ —
uJ >- a: z; x>-zu
3 0. O >- UJ Z
UJ « >-U« l-C.ll
I •- Z UJ »- 1-1 U
I < 2 U«- 09 3
3 c C cr. •* _ilu>
Z — u. U UJ 3 +•
«- •- a u c. a.
B^K = >-. »5l_« C_l — U
UJ»**UJ < > CT*-t»M UJD (-> U
XOC U.OJ *fc) jJCO^IUJ^^ UJ <
r a. i U.T x unaauJu. —
3 3 24UJX ^. — I >• •" uJ UJ —
ZZZ ZX.Xu.XZCi-XO O C
O 4. ««3O.OJU.U ^
>-U.»-Z Cu.Z w iT«« W ^
c a w> — _i a >- ^- z z z -< u- c c x
StelXLV KO^^^VM^QQ^^tC X 2
UQOul^ •^t/3«J3OJ3u^&&4OZ uJ 9}
5 z a.
tN
CM
1
3
8
H
Ft,
155
-------
TABLE 9-2
RETRIEVAL PACKAGE ERROR MESSAGES
ERROR MESSAGE
CAUSE
"FATAL - INVALID RETRIEVAL CARD"
"WARNING - DUPLICATE TITLE (01)
CARD"
"FATAL - OVER 20 SELECTION
CRITERIA"
"FATAL - INVALID DATA ELEMENT"
"WARNING - BAD LEVEL,
SD FORMAT DELETED"
"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:
Card type not 01, 10, 20, 30, or 40
More than one 01 card type entered,
the first one is accepted.
Limit of twenty card type 20 cards
exceeded.
4-digit data element abbreviation does
not correspond to any on list on input
form. This error can occur on card
types 10, 30, or 40.
The level code entered on card type 01
is not S, P, A, or C. If SD format is
requested, it will be ignored.
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.
156
-------
TABLE 9-2 (Continued)
RETRIEVAL PACKAGE ERROR MESSAGES
ERROR MESSAGE
CAUSE
"FATAL - REPORT FORMAT (20)
CARD REQUIRED"
"WARNING - QL (40) MISSING,
QL DELETED"
"WARNING - QL TOO BIG,
QL DELETED"
"WARNING - LEVEL FOR SD
FORMAT ONLY"
"FATAL-DOTLICATE FORMAT
(20) CARD"
"FATAL - DUPLICATE SEQUENCE
(30) CARD"
"FATAL - 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"
No card type 20 was entered.
card type is required.
This
No card type 40 was entered, although
QL was entered on card type 20. QL
report format is ignored.
The total length of the QL line is
greater than 110 digits with the de-
fault header information or 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 20 was
entered.
More than one card type 30 was
entered.
The sum of the number of digits of
the 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. No
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 con-
fidential.
157
-------
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 corresponds to the input code. There are four data elements
which have separate table-lookup procedures for each of the ten EPA
Regions using CDS. Each of the 10 regions may specify the descrip-
tion 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 retriev-
able data element.
For a Card 1, the Air Quality Control Region (AQCR) on the input
transaction is validated against the AQCR on the County Code Table.
±58
-------
Entries on the County Code Table have the following punchcard
layout:
Card
Columns
1-2
3-4
5-8
9-25
26-28
29-31
32-34
35-80
Length
2
2
4
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-55
Numeric
Alphanumeric
Numeric
Numeric
Numeric
Must be blank
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 Data Bank Coordinator
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.
159
-------
FIGURE 10-1
COUNTY CODE TABLE
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
04
STTF
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
TNTY
0240
0260
0280
0360
0400
0520
0540
0560
0580
0600
0660
0680
0720
0740
0760
0780
0800
0820
C.NTf NAtfF.
AUTAUGA
BALDWIN
BARBOUR
BIBB
BLOUNT
BULLOCK
BUTLER
CALHOUN
CHAMBERS
CHEROKEE
CHILTON
CHOC TAW
CLARKE
CLAY
CLEBURNE
COFFEE
COLBERT
CONECUH
AOCR
002
005
006
004
004
002
002
003
003
003
004
001
001
003
003
006
007
001
160
-------
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 the output Masterfile based on each personnel code.
Entries on the Personnel Code Table have the following punchcard
layout:
Card
Columns
1-2
3-4
5-7
Length
2
2
3
Data
Element
Data
Type
Record-Identifier Always "BB1
Region
Personnel Code
8
9-23
24-38
39-80
1
15
15
42
Filler
Personnel Name
Personnel Title
Filler
Numeric, 01-10
The first position
may be alphabetic;
the second and
third must be nu-
meric.
Always "0"
Alphanumeric
Alphanumeric
Must be blank
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.
161
-------
To change the Personnel Code Table, users should provide the
national Data Bank Coordinator 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 document any table changes on this figure.
162
-------
FIGURE 10-2
SAMPLE PERSONNEL TABLE
PERSONNEL NAME
CODE
A01 LEGROS
A02 BLOOM
A03 WYNNE
A04 ZEHNTNER
A05 STONELAKE
A06 BLACKWELL
A07 BUFFINGTON
A08 JOSEPH
A09 GOLD
A10 HANDZEL
All LASKOW
A12 GREENE
A13 VACCARO
A14 SMITH P
A15 SERRITELLA
A16 MARTIN
A17 COLLINGS
A18 DONOVAN
A19 BRENNAN
A20 ROGERS
A21 FRYE
A22 AJL
A23 BAKER
A24 CALLEN
A25 EARLY
A26 HEENAHAN
A27 KALKSTEIN
A28 KOEGEL
A29 MELVIN
A30 SISKIND
C01 WALKER
C02 LOWRY
C03 BUI
C04 BURROWS
E01 MARSHALL
±63
-------
10.1.3 Action Table
In the Edit, the Action Type found on the Card 7 in columns 53-54
is validated 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 Master-
file based on the Action Type.
Entires 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
Region
Action Type
Filler
Short Action
Description
Long Action
Description
Filler
Data
Type
Always "CC"
Numeric, 01-10
Numeric
Always "00"
Alphanumeric
Alphanumeric
Must be blank
To change the Action Table, users should provide the national Data
Bank Coordinator 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
WYLBURto list the most current action types for their region. The follow-
ing WYLBUR commands will produce a printout of the current action types:
±64 Revised 12/79
-------
WYLBUR COMMAND
USE $CN.EPAFCS.A026.ISAM.TABLE CLEAR
DEL NOT 'CC061 IN ALL
CHANGE 1/4 TO ' 'IN ALL NOLIST
CHANGE 7/8 TO ' 'IN 'ALL NOLIST
CHANGE 25 TO ' ' IN ALL NOLIST
LIST OFFLINE REM»3 UNN BOX=REG6
EXPLANATION
Places all 10 regions actions
into working storage.
Deletes all entries for all regions
except for Region 6. Each region
should put their own region number
into this command.
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
Data
Type
Always "DD"
Numeric, 01-10
Numeric
Always "00"
Results Description Alphanumeric
Filler
Must be blanks
165
Revised 12/79
-------
To change the Results Code Table, users should provide the national
Data Bank Coordinator 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
document any table changes on this figure.
166
-------
FIGURE 10-3
SAMPLE ACTION TABLE
ACTION SHORT DESCRIPTION LONG DESCRIPTION
Al 307 CHALLEGES
A2 SIP NOTICE CMSD
A3 SIP CMSD DATE
A4 SIP GMSDRPT SUB
A5 SIP EE RPT SUB
A6 SIP CMS INSP
A7 SIP DOFEA/STATE
A8 SIP S/UUDER 306
A9 NSPS CONST COMM
Bl NSPS NOTICECMSD
B2 NSPS 114 LETTER
B3 NSPS INSP-EPA
B4 NSPS ORDER/EPA
B5 NSPS CIV/CRM
B6 NSPS MOR NOTICE
B7 NSPS CMSDRPTSUB
B8 NSPS N/MALF'N
B9 NSPS CMSTRESULT
Cl NSPS CMS INSP
C2 NSPS DEA STATE
C3 NSPS S/UNDER306
C4 NESHAPS S/CNS'N
C5 NESHAPS E/CONSR
C6 NESHAPSFINALCOM
C7 NESHAPS SUB CP
C8 NESHAPS PUREQP
C9 REGISTRA'N RCVD
Dl PERMIT APPN RCD
D2 NESHAPSINSP'N
D3 NESHAPS S/T SUB
D4 NESHAPS STARTUP
D5 NESHAPSEPAORDER
D6 NESHAPSCIV/CRIM
D7 NESHAPS PwTG'T
307 CHALLENGES
SIP NOTICE OF CM SYSTEM DEMONSTRATION
SIP CM SYSTEM DEMONSTRATION DATE
SlP 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 DEMONSTRATION
NSPS SI14 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
NSPSCONTINUOUS 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
NLSHAPS INSPECTION
NESHAPS SOURCE TEST SUBMISSION
NESHAPS START-UP
NESHAPS ORDER BY EPA
NESHAPS CIVIL/CRIMINAL ACTION BY EPA
NESHAPS PERMIT GRANTED
167
-------
FIGURE 10-4
SAMPLE RESULTS CODE TABLE
RESULTS SHORT DESCRIPTION LONG DESCRIPTION
AB STTE NOV
AC STTE REC'D APP
AD STTE CIV ACT
AE STTE CRIM ACT
AF ST AD INFO REQ
AG APP TO ST COMP
AH ST PRE DETERMN
BA EPA NOV
Bl NOT DT CONS/MO
B2 NOT PHYS/OPERC
CA EPA REC'D APPL
Cl NOT INIT STRTU
C2 NOT ACT STUP D
DA EPA CIV ACT
Dl REP INFO REQ
D2 REQ COM WAIVER
STTE NOTICE OF VIOLATION
STATE RECEIVED APPLICATION
STATE CIVIL ACTION
STATE CRIMINAL ACTION
STATE ADD. INFORMATION REQUESTED
APPLICATATION TO STATE COMPLETE
STATE PRELIMINARY DETERMINATION
EPA NOTICE OF VIOLATION
NOTIFICATION OF DATE CONSTR. OR MODIFICATION IS COMMENCED
NOTIFICATION OF ANY PHYSICAL OR OPERATIONAL CHANGE
EPA RECEIVED APPLICATION
NOTIFICATION OF ANTICIPATED INITIAL STARTUP
NOTIFICATION OF ACTUAL STARTUP DATE
EPA CIVIL ACTION
REPORTED INFORMATION REQUIRED BY 61.10
REQUESTED COMPLIANCE WAIVER
168
-------
10.1.5 Other Table Lookup Procedures
For both editting 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 Data Bank Coordinator.
The following data elements have table lookups for converting a
code to an English-language description:
Region Emission Category Source Compliance
State Compliance Status Source Emission Cat.
Federal Facility SIP Code SIC Code
Code Active/Passive Code Pollutant Code
In addition to having a table lookup procedure for SIC Code during
retrievals, the CDS Update Program uses the SIC lookup to place the SIC
description 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 former 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 Data Bank Coordinator.
Each change involves a number of computer program modifications.
10.1.6 CDS Masterfile Layout
Figure 10-5 shows the format of the CDS Masterfile. This file
is resident on 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.
1.89 Revised 12/79
-------
COM
roR
s?
B'S
MOM
Ski
SB
o o
O 'J
PAT*
RECORDS
i 1 1 1 1 1 1 i i
- W!
S«fea5
«* t* ~- » M
c o E c, 5
«."> ej ;w&'ft
i 1 1 i i i t i i
1 1
I
o
Ul
«
i i
COMPLIANCE DATA SYSTEM
MASTER FILE LAYOUT
>J JU1,.:H1U>1»»144.44 44444 I II,,,,,,,,..,.....,„,,„,,,,,,''''•'' ''l| ' J »« ' '!''''!' ' !' '' ' ' J ' " ' ' ' ' " '""I I ' »• • I I I I , I I I I ,.,,,, I I , I I I
ujj^^i£iiu^-jg^^."M.".M.A^^
SOURCE
CODE
STREET
ADDRESS
U IFILLE
z.,
on
S
CODEi'Ci^
f^*
... ^Jl.—n
"POLLUTANT i
m
STATE
REGULATION
gi -si "s~F"T~"i
I, I, BI I -, |c OES"
*- •». I w u; I u* K **:j
" I.T t = t H 5 - (S
:c i TY
POLLUTANT 2
POLLUTANT 3
PROCESS,
DE SCR IPT I ON
ZIP
CODE
• ; STATE j
REGISTRATION
NUMBER
POLLUTANT 4
ACTION
CRIPTION
(SKCRT I
COMMENT
|]«4444<«
S TAFF
NAME
POLLUTANT S
STAFF
NAME
5
O -J S|
POLLUTAN1 «
POLLUTANT 7
ROE4
ROES
POLLUTANT
ItDE*
POLLUTANT •
COUNTY
NAME
POLLUTANT 10
FILLER
FILLER
FILLER
ACT ION DE SCR I P TION
(LONG)
RESULTS
DESCRIPTION
riLLE*
FILLER
I I I I I I I I I I ' I I I I .. t I I I I I I I I I I I I I I I ! I ! Ill
FIGURE 10-5
-------
10.2 Backup and Recovery Procedures
Both the user and the national Data Bank Coordinator have responsi-
bilities 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 operation of CDS, users should perform the
following tasks to assure proper backup:
o All input punchcards must be kept for a minimum of one 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 identi-
fied and used as backup.
o WYLBURdata sets which are used as input transactions must be
kept for a minimum of one month from the date on which they
were used as input to CDS. Users should keep a log of all
WYLBURdata sets, marking the creation date, the expiration
date, the approximate volume on the data set, and its use or
function.
o Edit Reports should not be discarded. The Edit Report provides
a record of what transactions were input to the system. Cor-
rections should be checked off as they are performed.
o 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 of the Masterfile s Output
Serial Number which appears on the heading of each page. If
users note any discrepancies or inexplicable errors on this
report, they should alert the national Data Bank Coordinator
or TRC. TRC maintains a complete inventory of all Update
Reports for all users.
10.2.2 National Responsibility for Backup
As part of the normal operation of CDS, the national Data Bank
Coordinator performs the following tasks to assure backup of the system:
171
Revised 12/79
-------
o 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 one month's worth of input transactions.
o Five cycles of the CDS Masterfile are kept at the central com-
puter facility.
o On a quarterly basis, the CDS Masterfile is copied and sent to
TRC for archiving.
o Since the ten regional disk Masterfiles are created each week
from the CDS Masterfile, the Masterfile provides the only backup
of regional files.
o The County Code, Personnel, Action, and Result Code Tables can
be recreated from punchcards or from WYLBUR data sets.
o All other CDS data sets and computer programs are maintained at
TRC with punchcard backup available at all times.
10.2.3 Recovery Procedures
If any backup procedures are needed to recover from hardware diffi-
culties at the central computer site, the national Data Bank .Coordinator
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 hard-
ware difficulties.
10.3 Computer Program Modifications
If any of the computer programs in the CDS system produce erroneous
results, it is the user's responsibility to notify the national Data Bank
Coordinator 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 one
week. Major changes may take several weeks or months, depending on the
complexity of the change.
173
-------
10.4 Microfiche Considerations
Facilities for producing both microfilm and microfiche output
are currently available through the Micrographics Department at WCC in
Washington, B.C. Users of CDS should consider the use of microfiche
to facilitate the storage and handling of lengthy reports such as a
regional Source Data Report.
Any user who wishes to utilize this service is required to submit
a WCC Request for Micrographics Form. Figures 10-6 through 10-9 include
a complete sample of the forms which are used to establish job processing
parameters for an individual user indicating a reduction factor compatible
with their own microfiche reader, as well as an appropriate title which
is eye-readable for identification purposes.
Once a user's completed form has been received by WCC, processing
with requested microfiche output may be submitted at any time. The user
will request a regular CDS retrieval with a Source Data Report format.
However, as further processing of this data is required, the output will
be written to a tape data set for subsequent micrographics processing.
Microfiche output is processed on the basis of 48 hour turnaround with
the completed output mailed directly to the initiator of the request.
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-10.
Revised
-------
WCC REQUEST FOR MICROGRAPHICS
MICROGRAPHICS CENTER USE ONL.Y-
DATE RECEIVED'
CONTROL Mo.:
FIGURE 10-6
MICROGRAPHICS USER INFORMATION FOR CDS
DATE: ' 5-30-78
re
-o
NAME OF APPLICATION
NDIVIDUAL USER:
USER INFORMATION
. MICROCDS (Not longer than 8 characters)
RESEARCH CORPORATION OF New England
•o
0)
o
01
O.
ADDRESS 125 Silas Heane Highway
Wethersfield, Connecticut
ATTN: JoAnn Hewett
PHONE No. (203) 563-1431
ZIP CODE 06109
ROOM No.
USER 1.0. EPAEXC
ACCOUNT NO
A026
TYPE OF APPLICATION
CHANGE TO EXISTING PRODUCTION APPLICATION
TEST Of NEW APPLICATION
SERVICE REQUESTED
ORIGINAL MICROFICHE
ORIGINAL ROLL FILM
SOURCE DOCUMENT MICROFILMING
DUPLICATION OF MICROFICHE
DUPLICATION OF ROLL FILM
SPECIAL INSTRUCTIONS
SAMPLE FORM
175
PAGE I OF -*
-------
WCC MICROFORMS INPUT/OUTPUT SPECIFICATIONS
INPUT
MAGNETIC TAPE CHARACTERISTICS'
IBM '"'''
SL
9
1600
FIGURE 10-7
CDS MICROFORM INPUT
IBM OR OTHER (SPECIFY)
LABELED OR UNLABELED
TRACK (7 OR 9)
BPI (SS6, BOO, I6OO)
PARITY (ODD OR EVEN - REQUIRED FOR 7-TRACK TAPES ONI?)
.133. RECORD LENGTH
41 23 BLOCK SIZE
EBCDIC,.. CHARACTER SET (EBCDIC, ASCII OR OTHER)
132 NUMBER OF PRINT POSITIONS
3_ CARRIAGE CONTROL POSITION
2_ POSITION NUMBER OF FIRST PRINT CHARACTER
. ASA. CARRIAGE CONTROL TYPE (ASA, MACHINE, OTHER)
64 LINES PER FRAME/PAGE
VERTICAL TABBING •-
CHANNEL
LINE NUMBER
1
2
3
4
5
6
7
8
9
A
B
C
FORMS OVERLAY:
OPEN BOX
LINED BOX
SPECIAL (MICROGRAPHICS FORMS OVERLAY SPECIFICATIONS ATTACHED)
OUTPUT
MICROFORMS REQUIREMENTS:
^-* -Ui NUMBER OF COPIES REQUESTED
EIHHF MICROFICHE OR ROLL FILM
COMIC IMAGE (COMIC OR CINE)
RflW. FORMAT (ROW OR COLUMN)
FRAMES/ROW
FRAMES/COLUMN
24 REDUCTION FACTOR (24X, 42X, 48X}
SAMPLE FORM
DEPENDENT ON INDIVIDUAL USER'S
MICROFICHE READER
PAGE 2 OF
-------
OUTPUT (CONTINUED FROM PAGE 2)
FIGURE 10-8
CDS MICROFORM OUTPUT
MICROFICHE TITLE FORMAT'
SPECIFY HOW TITLE SHOULD APPEAR. CIRCLE AND NUMBER EACH EXTRACT.
REGION II - SOURCE DATA REPORT (unique to individual user)
2 L-v_ ^J—
-------
OUTPUT (CONTINUED FRO* PAGE S)
INDEXING REQUIREMENTS:
FIGURE 10-9
CDS MICROFORM PAGE BREAKS
PRINT UNE POSITION FOR KEY
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
10
2
5
5
SUBKEY 2
10
4
6
6
SUBKEY 3
3
35
4
4
SUBKEY 4
\
MASK CHARACTERS • NUMERIC'S-, ALPHABETIC**; ALPHANUMERIC • x; SPECIAL* CHARACTER * s
FICHE BREAK REQUIREMENTS:
BREAK ON MATCH OR CHANGE 7
BREAK FIELD ON CURRENT OR NEW RftSE ?
UNE TO BEGIN SEARCH
LINE TO STOP SEARCH
BEGINNING PRINT PCS. OF BREAK FIELD
LENGTH IN CHARACTERS OF BREAK FIELD
BREAK EVERY OCCURRENCE OF MATCH ?
MATCH FIELD 1
MATCH FIELD Z
MATCH FIELD 3
MATCH FIELD 4
MATCH FIELD 5
MATCH FIELD 6
CONDITION 1
M
CURRENT
5
5
10
2
NO
NJ^
NY •>
PR v
VI /
CONDITION 2
Z, fi<.i ' /
-------
FORTRAN CODING FORM
AUTHOR TRC | PROGRAM NAME CDS MICROHCHE JCL
„ STMT
N0,™
1 2
//
/*
//
//
0 1
20
30
//
//
//
/
HE
3
E
C
R
S
o
-
4
P
SI
T
O
S
S
T
r
-
S
A
T
V
2
D
M
E
-
-
1
u
1
i
I
•
VI
P
-
-
TASK NUMBER
DATE
Page
of
FORTRAN STATEMENT
7
I
S
A
E
3
-
-
1
i
r
-
S
c
5
P
10
D
O
R
11
S
O
1
12
J
E
5
R
N
L
D
13
O
E
X
E
T
A
C
-
14
B
X
E
0
G
P
O
B
B
-
IS
C
C
D
1
A
U
E
;
i
a
r
n
P
is
(
O
S
T
L
(
i
a
r
P
-
-
U
A
C
*
N
S
:
R
i
a
P
II
A
D
A
D
(
E
a
P
13
A
S
1
o
D
1
C
20
A
R
1
R
f
i
i
t
1
1
21
T
D
D
S
M
22
W
V
M
S
L
h<
hi
111
h<
hi
n
i
in
1
N
f
,
i
t
t
24
i
C
;
R
B
te
1C
itf
JP
25
i
R
C
E
A
.
,
.,
,
i
K
)
O
0
T
l
. i
27
f
N
P
L
nl
C(
en
ef
n
'
1
D
R
tl
311
nl
fr
29
C
c
E
™
E
a
it
i
30
O
H
P
1
C
n
3
Mi:
I
31
S
E
A
5
L
ml
e
h.
- 1
32
i
)
el
n
r
14
33
M
j
1
en
or
KC
34
1
j
U
3
:e
R
-
'i
n
K
C
f
N
3
i
a
X
•M
X
R
A
1
H
e
E
37
O
A
T
B
r.<
-
K
01
31
F
A
2
L
or
ilp
-1
t
39
|
A
T
K
_»
>
IN
40
C
^
A
S
1
ra
R
41
H
M
P
i
SI
ii
1.
42
E
1
E
Z
C
\
43
•
C
9
E
.ii
-
-
44
R
*•
•e
IP
45
T
O
4
10
46
1
C
1
-
e
t<
-
47
V
D
2
m
-
41
E
S
3
nh
r
-
49
Z
•T
ir
U
5
D
D
iUj
SI
£
E
ih.
52
P
S
N
1C
-
S3
A
P
;
S
S4
S
:
3
55
S
(
)
•N
st
w
N
Nl
S7
O
E
,C
-
U
R
A
1C
-
s>
o
(0
;
C
(1
P
A
(2
P
T
(3
P
L
(4
P
5
(SS
)
it?
U
n
70
11
72
CARD
NUMBER
71
74
i
C
77
71
71
to
-------
10.5 Minicomputer Edits
Dennis Shur of EPA Region X has developed an on-line 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.
This 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 processing.
CDS users wishing more information about this on-line edit should
call Denis at (206) 442-1580.
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.
±80
Revised 1/80
-------
Archiving is beneficial because it reduces the cost of retrievals
and it simplifies retrieval criteria needed to produce management reports.
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 Masterfile in the same sequence as they existed prior to
archiving. If the user feels that there are too many obsolete actions
on the masterfile, he should delete those actions. Since each CDS Master-
file 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 of the historic masterfile.
10.7 Formal Reporting
On a quarterly basis, each region must submit certain reports to
the Program Reporting Division. Several of these reporting requirements
can be met by using the procedure which makes CDS data available to the
Formal Reporting System. The link between CDS and FRS uses the standard
milestone report together with other computer programs to provide data
for the Formal Reporting System.
Revised 12/79
181
-------
At present, the specific output units/activity indicators
linked from CDS to FRS are:
AIR OUTPUT 3
SAG NSPS sources violating or believed to be violating pro-
cedural or emission requirements.
3A3 Number of sources in compliance with procedural or emis-
sion requirements for NSPS.
AIR OUTPUT 6
6AA Number of sources in compliance with standards and
scheduled progress.
6AB Number of sources of unknown compliance status or in
violation.
6AC Number of enforcement actions.
AIR OUTPUT 12
12AA Number of non-transitory NESHAPS sources in violation
or of unknown status.
12A1 Number of non-transitory NESHAPS sources.
182
-------
At a later date, other outputs may also be subject to the
direct link between CDS and FRS.
During the third week following the end of each quarter, each
region must submit the job control described in Figure 10-11. This
computer job creates a data set containing all of the numbers for the
Air Outputs described above.
In order to get a preview of what numbers will be sent from CDS
to FRS, regional users are urged to submit this job at the end of each
quarter. If changes are desired, input transactions can be prepared
for the CDS Masterfile in time for the Formal Reporting. Each time the
region runs the CDS/FRS link program, old data is replaced by the latest
data from the CDS Masterfile. The Formal Reporting System only uses the
most current data from the CDS/FRS link available on the 20th or 21st
of the month following the end of the quarter.
Figure 10-12 shows a sample of the Milestone Report produced by the
CDS/FRS processing.
183 Revised 12/79
-------
1
>
/
V
/
/
/
-
AUTHOR TRC
1 )
/ E
*R
*C
/
/
*E
4 S 1 7 I »
PAi I i
OUTE
NTL C
3F
it i i; i t t!
JOB
PRINT
OS EXC
EXEC
Wee
i ii
ooaa
r r
_ nn _
_ _ p ppp
•
(11
( a
KM
C
l
I
i
*
1
II
a
T
D
i
.1
II
a
r
S
ii
K
h<
t
IU
»
a
r
F
\
\
t
w<
!
•
PROGRAM NAME CDS/FORMAL REPORTING SYSTEM TA
Jl
R
ie
if
ie
•i
ae
•
Jl
nx
' i
in
( '
. _i
: IN'
ta
i i
i
: :]
1 Ml
J r»r
< i1
( L
»
)
•1
It
!i
in
ir
11
17 Jin
1 II
u mlej
2 £ f
c d< <
F C HI
D /
K >in J3
SER
, e I -(
it t <
!)••!
K : .1 IK
» 1
1 D
f >r
0< i.
I )
a 1
Ta
11
1
•
t<
a
T
C
\
4*41
V E
r te
QIC
no
: l
o e
rt
««
PA
ib it
h
^K NUMBER
7414)
Sc ju
. ?i i
H
f%
);
i]
D
• '
MM
= P
N Jl
UN
PP
e c
S
P
H
HM
JATE
II H
M g|
9 fit
P««»
of
(
M
n
171
CARD
NUMBER
7174
SKI
nn
K
-------
REPURT
0«/09/7«»
COMPLIANCE DATA flYSlfM
KFtiTON 06 Ct>a MILFSTUME (UTA 8hNT TO FHS
3AG
3A3
bAA
bAH
6AC
1?AA
12A1
FHfl AIR PRPIiRAM RtQ REGION 06 /"
NgPS Vim. PROC/SMI3 HEO 170
NSPS SOURCES IN COMPL 2SS
3TP COMPL WITH 8TANORD8 27«7
8TP UNKN CUMP/IN VJflL 220
ENFORCE ACT ACH FI3C YH 10
NF3HAP3 MXTRAN3 UN/3TAT 3b
NF0HAP3 KDN-THANS 3RCEB 197
OHANO TOTALS U7«
ARKANSAS LC
7
3
130
^2
0
2
3
177
JtJiaiANA K
17
36
410
73
b
Itf
5B
Mtt
1 MEXICO I
10
12
65
46
0
0
1
157
OKLAHOMA
10
22
27b
13
1
1
11
335
T fc X A S
l?6
162
1HSV
•56
1
12
1?1
?SS7
w
FIGURE 10-12
-------
11.0 STATE ENFORCEMENT SYSTEMS
Part of DSSE'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.
1S6
Revised 12/79
-------
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 for the follow-
ing areas:
o Which facilities are affected by SIP regulations. Which facilities
have permits to construct and permits to operate.
o Which facilities impact non-attainment standards, New Source Review,
Prevention of Significant Deterioration, NESHAPS, NSPS, etc.
o Which compliance category each source is in as a result of the state's
most recent inspection.
o What legal steps have been made to bring a non-compliant source into
compliance. What enforcement schedule must each non-compliant source
follow.
Once the state has gathered this information through its team of inspectors,
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 affort to spend anywhere from
$50,000 to $150,000 to develop a smoothly working data system.
3- Use an EPA-developed state computer system such as a state version
of the Compliance Data System (CDS). This option is ideal for
states which want to track all of the major and minor facilities
within their jurisdiction.
4. Use the national Compliance Data System (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 Washington Computer
Center, and if the state needs to track mainly major facilities.
Revised 12/79
187
-------
The option a state chooses depends on a wide variety of factors such as:
o The level of detail required by internal management needs as well
as external reporting requirements.
o 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.
o 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.
o The rate at which information needs change from year to year. With
every new EPA fiscal year, a new set of reporting requirements are
negotiated between the region and the state. Often a state data center
cannot keep up with a new set of computer programs to meet these
requirements.
The Division of Stationary Source Enforcement and the regional enforcement
divisons are committed to helping states meet the challenge of attaining compli-
ance for all stationary sources of air pollution. DSSE will support
feasibility studies and state enforcement system installations in order to
further the efforts of the states to monitor the compliance status and enforce-
ment activity of any state enforcement agency.
Revised 12/79
188
-------
11.2 State Enforcement System Usage
The following ten tables describe the types of enforcement systems
used in each of the fifty (50) states. This listing is on a region by
region basis. The tallies of major sources are estimates as of December
1979 and need to be upgraded on a continuing basis.
189
-------
REGION I - BOSTON
STATE
CONNECTICUT
MAINE
MASSACHUSETTS
NEW HAMPSHIRE
RHODE ISLAND
VERMONT
TOTALS
MAJOR SIP
SOURCES
241
155
587
105
67
63
1211
MAJORS OUT OF
COMPLIANCE OR
UNKNOWN
8
18
6
3
4
4
43
ENFORCEMENT
SYSTEM TYPE*
STATE
EMS
YEAR SYSTEM
INSTALLED '
1974
INSTALLATION
COST TO EPA
$45,000
OTHER SYSTfiM.fi
EMISSION AIR
INVENTORY QUALITY
STATE SYSTEM
EIS BEING
INSTALLED
AQDHS
INSTALLED
AQDHS
INSTALLED
AQDHS BEING
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 CDS System Running at State Installation
NATIONAL CDS - Direct User of National CDS at EPA's Washington Computer Center
TABLE 11-1
REGION I's ENFORCEMENT SYSTEMS
'ORCEMEK
-------
.EGION
REGION II - NEW YORK
STATE
NEW JERSEY
NEW YORK
PUERTO RICO
VIRGIN ISLANDS
TOTALS
MAJOR SIP
SOURCES
1104
1157
179
13
2473
MAJORS OUT OF
COMPLIANCE OR
UNKNOWN
63
87
20
0
170
ENFORCEMENT
SYSTEM TYPE*
CDS INSTALLED
IN NEW YORK CIT1
YEAR SYSTEM
INSTALLED
1977
INSTALLATION
COST TO EPA
$67,000
OTHER SYSTEMS
EMISSION AIR
INVENTORY QUALITY
STATE
STATE
EIS INSTALLED
AQDHS
INSTALLED IN
NEW YORK CITY
AQDHS
INSTALLED
* EMS • EPA'a 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 Washington Computer Center
TABLE 11-2
REGION II's ENFORCEMENT SYSTEMS
-------
REGION III - PHILADELPHIA
STATE
DELAWARE
DISTRICT OF
COLUMBIA
MARYLAND
PENNSYLVANIA
VIRGINIA
WEST VIRIGINIA
TOTALS
MAJOR SIP
SOURCES
44
36
215
1523
573
248
2633
MAJORS OUT OF
COMPLIANCE OR
UNKNOWN
2
10
35
105
22
43
209
ENFORCEMENT
SYSTEM TYPE*
STATE CDS
STATE
YEAR SYSTEM
INSTALLED
1977
INSTALLATION
COST TO EPA
$47,000
OTHER SYSTEMS
EMISSION AIR
INVENTORY QUALITY
EIS INSTALLED
STATE
EIS INSTALLED
AQDHS
INSTALLED
ro
* EMS - EPA'a 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 Washington Computer Center
TABLE 11-3
REGION Ill's ENFORCEMENT SYSTEMS
-------
REGION IV - ATLANTA
S
CO
* 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 Washington Computer Center
TABLE 11-4
REGION IVs ENFORCEMENT SYSTEMS
STATE
ALABAMA
FLORIDA
GEORGIA
KENTUCKY
MISSISSIPPI
NORTH CAROLINA
SOUTH CAROLINA
TTTNNir^^FF
TOTALS
MAJOR SIP
SOURCES
516
484
333
913
185
955
303
742
4551
MAJORS OUT OF
COMPLIANCE OR
UNKNOWN
5
24
18
32
10
42
6
82
219
ENFORCEMENT
SYSTEM TYPE*
EMS
STATE CDS
' EMS
STATE
NATIONAL CDS
EMS AND
NATIONAL CDS
.
YEAR SYSTEM
INSTALLED
1973
1978
EMS/1974
CDS/1978
INSTALLATION
COST TO EPA
$32,000
$26,000
$ 2,000
$30,000
$ 1.000
QT11F.R SYSTEMS
EMISSION AIR
INVENTORY QUALITY
IS INSTALLED
ESS INSTALLED
2IS INSTALLED
SIS INSTALLED
SIS INSTALLED
SIS INSTALLED
Hl^LmO
INSTALLED
AQDHS
INSTALLED
AQDHS
INSTALLED
AQDHS
INSTALLED
AQDHS
TNQTAT.T.F.n
-------
REGION - CHICAGO
STATE
ILLINOIS
INDIANA
MICHIGAN
MINNESOTA
OHIO
WISCONSIN
TOTALS
MAJOR SIP
SOURCES
1757
774
417
401
1057
276
4682
MAJORS OUT OF
COMPLIANCE OR
UNKNOWN
52
51
14
31
230
5
383
ENFORCEMENT
SYSTEM TYPE*
STATE
STATE
STATE CDS
NATIONAL CDS
YEAR SYS1
INSTALLS
1979
1979
INSTALLATION
COST TO EPA
$35,000
$ 2,000
OTHER SYS.TKMS
ION AIR
TORY QUALITY
re
ALLED
AQDHS
INSTALLED
AQDHS
INSTALLED
AQDHS
INSTALLED
* EMS - EPA1a 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 Washington Computer Center
TABLE 11-5
REGION V's ENFORCEMENT S
JY^EMS
-------
REGION VI - DALLAS
STATE
ARKANSAS
LOUISIANA
NEW MEXICO
OKLAHOMA
TEXAS
TOTALS
MAJOR SIP
SOURCES
156
514
129
268
1452
2919
MAJORS OUT OF
COMPLIANCE OR
UNKNOWN
31
16
42
9
38
136
ENFORCEMENT
SYSTEM TYPE*
STATE CDS
STATE CDS
EMS
STATE
YEAR SYSTEM
INSTALLED
1979
1977
1974
1977
INSTALLATION
COST TO EPA
$35,000
$32,000
$45,000
OTHER SYSTEMS
EMISSION AIR
INVENTORY QUALITY
AQDHS
INSTALLED
AQDHS
INSTALLED
tn
* 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 Washington Computer Center
TABLE 11-6
REGION VI's ENFORCEMENT SYSTEMS
-------
REGION VII - KANSAS CITY
CT5
STATE
IOWA
KANSAS
MISSOURI
NEBRASKA
TOTALS
MAJOR SIP
SOURCES
445
797
307
383
1962
MAJORS OUT OF
COMPLIANCE OR
UNKNOWN
29
2
19
23
73
ENFORCEMENT
SYSTEM TYPE*
EMS
STATE CDS
NATIONAL CDS
YEAR SYSTEM
INSTALLED
1974
1980
1978
INSTALLATION
COST TO EPA
$28,000
$35,000
$ 2,000
SIS INSTALLED
OTHER S7STirMft
EMISSION
INVENTORY
* EMS - EPA1a 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 Washington Computer Center
TABLE 11-7
REGION VII's ENFORCEMENT SYSTEMS
AIR
QUALITY
AQDHS
INSTALLED
AQDHS
INSTALLED
-------
REGION VIII - DENVER
STATE
COLORADO
MONTANA
NORTH DAKOTA
SOUTH DAKOTA
UTAH
WYOMING
TOTALS
MAJOR SIP
SOURCES
251
65
61
83
102
111
673
MAJORS OUT OF
COMPLIANCE OR
UNKNOWN
6
2
6
1
11
2
28
ENFORCEMENT
SYSTEM TYPE*
EMS
YEAR SYSTEM
INSTALLED
1974
INSTALLATION
COST TO EPA
$26,000
OTHER SYSTEMS
EMISSION AIR
INVENTORY QUALITY
EIS INSTALLED
EIS INSTALLED
EIS INSTALLED
AQDHS
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'9 CDS System Running at State Installation
NATIONAL CDS - Direct User of National CDS at EPA1s Washington Computer Center
TABLE 11-8
REGION VIII's ENFORCEMENT SYSTEMS
-------
REGION IX - SAN FRANCISCO
STATE
ARIZONA
CALIFORNIA
HAWAII
NEVADA
GUAM
TOTALS
MAJOR SIP
SOURCES
369
1609
121
98
11
2208
MAJORS OUT OF
COMPLIANCE OR
UNKNOWN
8
26
8
3
1
46
ENFORCEMENT
SYSTEM TYPE*
NATIONAL CDS
NATIONAL CDS
YEAR SYSTEM
INSTALLED
1977
1978
INSTALLATION
COST TO EPA
$2,000
OTHER SYSTEMS
EMISSION AIR
INVENTORY QUALITY
EIS INSTALLED
EIS INSTALLED
AQDHS
INSTALLED
AQDHS
INSTALLED
GO
* EMS - EPA1a 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'a Washington Computer Center
TABLE 11-9
REGION IX's ENFORC
lEME^E
SYSTEMS
-------
REGION X - SEATTLE
STATE
ALASKA
IDAHO
OREGON
WASHINGTON
TOTALS
MAJOR SIP
SOURCES
42
119
301
278
740
MAJORS OUT OF
COMPLIANCE OR
UNKNOWN
2
3
6
23
34
ENFORCEMENT
SYSTEM TYPE*
STATE CDS
YEAR SYSTEM
INSTALLED
1978
INSTALLATION
COST TO EPA
$32,000
OTHER SYSTEMS
EMISSION AIR
INVENTORY QUALITY
EIS INSTALLED
AQDHS BEING
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 Washington Computer Center
TABLE 11-10
REGION X's ENFORCEMENT SYSTEMS
-------
H-3 Summary of State Enforcement System Options
States have the following four options for tracking all the
information needed to manage a successful enforcement program:
1. Manual system
2. In-house state system
3. EPA developed state CDS system
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
or Texas, which have very special in-house processing requirements and
which have strong EDP groups available for the development and maintenance
of a complex computer system. This option is also recommended for states
which need to develop a comprehensive multi-media data base which tracks
emission inventory data, compliance data, and enforcement data for sources
of air, water, solid waste, and other hazardous pollutants. The cost for
such a system will vary from $50,000 to $150,000, arid will take anywhere
from one to two years to develop.
The third option is recommended for states which have over 200 major
sources of air pollution. These states can take advantage of the
assistance provided by the EPA in developing and installing effective
state enforcement systems. Although the EPA has a tradition of refusing to
purchase computer hardware for states, they are willing to assist states
in the installation and training of EPA-developed systems.
I
Revised 1/80
-------
During the early and mid 1970's, nine states requested and received
EPA assistance in the installation of the Enforcement Management System.
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
sufficient EDP and enforcement staff for supporting the system. The EPA
spent an average of $32,000 for installing EMS in the following states:
o Alabama
o Colorado
o Georgia
o Iowa
o Massachusetts
o Mississippi
o North Carolina
o Tennessee
o Texas
Eight 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 the 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 ten regional enforcement divisions.
Revised 12/79
201
-------
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 minor sources of air pollution. Prerequisites
for a state installation are the following:
o 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 equipment.
o Availability of programming and operational support from
the state's EDP staff.
o A manpower commitment on the part of the enforcement division
to keep the data in the system current and accurate.
The EPA will analyze and possibly underwrite the installation cost of a
state CDS system; this has been averaging $35,000 for a six-month contract with an
environmental consulting firm such as TRC. The states underwrite the
operating 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 state with 500 major and 500 minor
sources, typical costs might include an annual budget of $2,000 for
computer runs, $500 for data storage, and $750 for keypunching.
Currently, the following enforcement agencies are using or are
getting the state CDS system:
o Arkansas o Oregon
o Georgia o Missouri
o Louisiana o Nebraska
o Maryland o Kansas
o New York City
202
Revised 1/30
-------
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
following criteria:
o Have access to the EPA's Washington Computer Center
via a computer terminal.
o Have no need to track large numbers of minor sources.
o Have no need for special processing requirements not
already available in CDS.
Since the EPA underwrites the cost of operating and maintaining
CDS, 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. The 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 $2,000 training budget is adequate for bringing a state on-line.
The following five states have made a commitment to be direct CDS users:
o Nebraska o California
o Ohio
o South Carolina
o Tennessee
Revised 12/79
203
-------
Each of these states has found that they can meet EPA reporting
requirements and all internal management reporting requirements at a
very low cost by being direct users of the national CDS system.
204
-------
12.0 DOCUMENTATION UPDATES
Major changes to the CDS System are issued periodically. The
EPA's data center publication, SIGNON, usually contains an article
describing current enhancements. DSSE issues additional information as
appropriate concerning CDS. Please file copies of CDS articles from
SIGNON and DSSE material in this chapter of the CDS User Manual.
If you do not already receive the SIGNON magazine, please call
the WCC User Support Team at 1-800-424-9067 to have your name placed
on the mailing list. Be sure to fill out the Revisions Form at the
front of this manual in order to receive DSSE's documentation updates.
Revised 12/79
205
-------
13.0 HEADQUARTERS GUIDANCE
All national policy guidance material will be released later in
a separate packaged section as soon as it is finished by the
Division of Stationary Source Enforcement.
Revised 1/80
2C6
-------
APPENDIX A
CDS
DATA ELEMENT DICTIONARY
-------
DATA ELEMENT DICTIONARY
Abbr. Data Type
A-l Air Program Code
A-2 Air Program Description
A-3 Air Program Status
A-4 Air Program Status Description
A-5 Air Quality Control Region
A-6 Capacity - Facility
A-7 City Code
A-8 City Name
A-9 County Code
A-10 County Name
A-ll Data Last Updated
A-12 Federal Facility
A-13 NEDS Source Cross-Reference
A-14 Pollutant Air Qual. Maint. Ar.
A-15 Pollutant Air Quality Cont. Reg.
A-16 Pollutant - Basic Summary
A-17 Pollutant Code - Source
A-18 Pollutant Compliance Status
A-19 Pollutant Emission Category
A-20 Pollutant Loading
A-21 Pollutant Delete Flag
A-22 Region
A-24 Regional Data Element 1
A-25 Regional Data Element 2
A-26 Regional Data Element 3
A-27 Regional Data Element 4
A-28 Regional Data Element 5
A-29 Regional Data Element 6
A-30 Regional Data Element 9
A-31 Regional Data Element 10
A-32 Regional Data Element 11
A-33 Regional Data Element 12
A-34 SIC Code
A-35 SIC Code Description
A-36 Source Compliance Status
A-37 Source Compliance Stat. Desc.
A-38 Source Comp. Status - 8 Qtrs.
A-39 Source Emission Category
A-40 Source Emission Description
A-41 Source Name
A-42 Source Number
A-43 Staff Name - Source
A-44 Staff Personnel Code - Source
A-45 Priority Code
A-46 State
A-47 State Abbreviation
APCD
APDS
APST
APSD
AQCR
FCAP
CYCD
CYNM
CNTY
CTNM
UPDA
FEDF
NEXS
PAQM
PAQC
BPLT
PLLT
PCMS
PECT
LOAD
REGN
RDE1
RDE2
RDE3
RDE4
RDE5
RDE6
RDE9
RD10
RD11
RD12
SICC
SICD
SCMS
SCSD
SCS0
SECT
SECD
SNME
SRCE
STFS
PERS
PRIO
STTE
STAB
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
-------
DATA ELEMENT DICTIONARY
(continued)
Data Element
State Registration Number
Street Address
Zip Code
Capacity Code
Compliance Status Code
Compliance Status Description
Emission Category
Emission Category Description
Emission Point Number
Multiple Cross-Reference
Old Compliance Status - 8 Qtrs.
Pollutant Code - Point
Procedural Compliance
Process Description
Regional Data Element 7
SCC Code
A-64 SIP Code
A-65 SIP Code Description
A-66 State Regulation
A-67 Action Description
A-68 Action Number
A-69 Action Type
A-70 Date Achieved
A-71 Date Achieved Year/Month
A-72 Date Scheduled
A-73 Date Scheduled Year/Month
A-74 Penalty Amount
A-75 Regional Data Element 8
A-76 Results Code
A-77 Results Description
A-78 Staff Name - Action
A-79 Staff Personnel Code - Action
A-80 Staff Title
A-81 Card Code
A-82 Comments
A-83 Line Number
A-84 Record Type
A-85 Update Code
Abbr. Data Type
STRG
STRT
ZIPC
CAPC
CMST
CMOS
ECAT
ECDS
PTNO
MULT
OCS0
PLUT
CMS 2
PROS
RDE7
SCC3
SCC6
SCC8
SIPC
SIDS
SREG
ADES
ANUM
ATPE
DTAC
DAYM
DTSC
DSYM
PLTY
RDE8
STAC
RSTD
STFA
PERA
TITL
S
S
S
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
P
A
A
A
A
A
A
A
A
A
A
A
A
A
A
-------
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. It can also be used to
denote a facility which has been closed down.
Retrieval
Abbreviation APCD
Card
Type 2
Card
Columns 65
Data Element -—•---
Length 1
Data
Type ALPHANUMERIC
Justified
Required
.on New Entry N0
Nationally
Controlled YES
Edit Error Messages:
*INVALID AIR PROGRAM CODE
*** = Fatal Error
Valid Values:
0 = SIP Source
l ~ SIP Source under federal juriudi
4 = ESECA
6 - PSD
7 — MSP
/ ~ W^iv
8 - NESHAPS
9 = NSPS
c = closed/inactive
Master file
Record Type 20
Masterfile
Position 115
Masterfile
Length 1
* = Warning Error
ttion
Coding Considerations:
For a SIP source, the State has primary jurisdiction for enforcment activity.
For an Active facility, the Federal EPA has primary jurisdiction for enforcene-r
of this SIP facility. ' " "
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.
If a facility has been closed down, Active/Passive Code "C" must be used to
indicate that the facility is closed. This code is to be used only after
the end of the Federal fiscal year in which the facility was closed.
Card Type 2
Data Element Sheet
A-l
Revised 1/80
-------
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
Type
Justified
Required
.on New Entry
Nationally
Controlled
APDS
N/A
N/A
20
ALPHABETIC
LEFT
NO
YES
Valid Values:
Mast erf He
Record Type
Masierfile
Position
Master file
Length
Edit Error Messages:
*** - Fatal Error * - Warning
N/A
N/A
20
Error
Coding Considerations:
APCD
blank
C
0
1
2
3
4
5
6
7
8
9
AIR PROGRAM DESCRIPTION
SIP Source
Closed/Inactive
SIP Source
SIP Active
APCD 2
APCD 3
ESECA
Other
PSD
NSR
NESHAPS
NSPS
Card Type
Data Element Sheet
Revised 12/79
A-2
-------
AIR PROGRAM STATUS
Definition: AIR PROGRAM STATUS represents the status of a facility for a given
air program. This field is mainly used for NSR, PSD, and NESHAPS
sources.
Retrieval
Abbreviation APST
Card
Type 2
Card
Columns 66
Data Element
Length l
Data
Type Alphanumeric
Justified
Required
.on New Entry No
Nationally
Controlled Yes •
Valid Values:
Master fite
Record Type 20
Master file
Position 180
Master file
Length i
Edit Error Messages: ~~~-
* Invalid Air Program Status
*** - Fatal Error * = Warning Error
Coding Considerations:
Valid Values:
blank - Operating
0 - Operating
- Planned (has applied for a construction permit)
- Under Contruction
- NESHAPS Demolition
- NESHAPS Renovation
- NESHAPS Spraying
P
C
D
R
S
Card Type 2
Data Element Sheet
A-3
Revised 1 /80
-------
AIR PROGRAM STATUS DESCRIPTION
Definition: AIR PROGRAM STATUS DESCRIPTION is the English language description
of the Air Program Status, generated for Quick Look Reports.
rte-neval
Abbreviation
Cora,
Tyve
Cora
Col'jxms
Data Element
L&nath
Required, on
Wev Entry?
Confidential
Data Element?
Passed to
National CDS?
Nationally
Controlled?
Edit Error Messages:
*** * Fatal Error
APSD
N/A
N/A
10
N/A
NO
NO
NO
Valid Values: —7
System-generated from APST. See AIR
PROGRAM STATUS for a list of air program
status descriptions.
Master jile
Record Tuve N/A
Master File ' "
Position N/A
Vaster -File
Lenath N/A
N/A
— * » Homina Error
Coding Considerations:
CDS Data Dictionary
A-4
-------
AQCR
Definition:
AQCR is the Air Quality Control Region, a three digit numeric value.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
* INCORRECT AQCR FOR
*** = Fatal Error
AQCR
1
20-22
3
NUMERIC
LEFT
YES
YES
Valid Values:
Must be valid for the state
county codes used. Blank is
valid. Please contact the c
DBG to add a new AQCR to the
County Code/AQCR Table.
Masterfile
Record Type 20
Masterfile
Position 21-23
and the
also
entral
Masterfile
Length 3
COUNTY
* = Warning Error
Coding Considerations:
The County Code/AQCR Table containing all valid AQCR's can be listed by
following the directions in Chapter 10,
Card Type i
Data Element Sheet
A-5
Revised 12/79
-------
FACILITY CAPACITY
Definition:
FACILITY CAPACITY indicates the total output capacity of the
products produced at a facility. This might be expressed in
several types of units such as barrels, kilowatt-hours, etc.
Retrieval
Abbreviation
Card
Type
Uard
Columns
Data Element
Length
Data
Type
Justified
Required
.on N&j Entry
Nationally
Controlled
FCAP
30
58-64
7
NUMERIC
RIGHT
NO
NO
Valid Values:
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
**<=.- Fatal Error * = Warning
30
42-48
7
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 per 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.
Card Type 3
Data Element Sheet
Revised ]/80
A-6
-------
CITY CODS
Definition:
CITY CODE is a four digit numeric city identifier. The City Codes
can be found in the SAROAD manual.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages
* CITY CODE SHOULD
*** = Fatal Error
CYCD
1
23-26
4
NUMERIC
LEFT
NO
NO
Valid Values:
If the field is being used, it
should be a four digit numeric
code found in the SAROAD manual.
btosterfile
Record Type 20
Masterfile
Position 24-27
Master file
Length 4
•
•
BE NUMERIC
* = Warning Error
Coding Considerations:
City codes are available from the Storage and Retrieval of Aerometric
Data (SAROAD), Volume V.
SAROAD Manuals are available on request form the EPA's Office of Air
Quality Planning and Standards.
Card Type i
Data Element Sheet
A-7
Revised 12/79"
-------
CITY NAME
Definition: CITY NAME gives the location of the facility.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
CYNM
2
20-34
15
ALPHANUMERIC
LEFT
NO
NO
Valid Values:
All alphanumeric characters
Uasterfile
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error
20
68-82
15
Coding Considerations:
If abbreviations are used, they should be used consistently for all
input to facilitate sorting and retrievals.
Card Type 2
Data Element Sheet
A-9
Revised 12/79
-------
COUNTY CODE
Definition:
COUNTY CODE is a four digit numeric county identifier. The County
Codes are derived from the SAROAD manual.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
*** INCORRECT COUNTY
*** = Fatal Error
CNTY
1-8
5-8
4
NUMERIC
LEFT
YES
YES
Valid Values:
All county codes must be present on
the CDS County Cpde/AQCR Table.
Master file
Record Type 20-47
Masterfile
Position 5-S
Masterfile
Length 4
CODE FOR STATE
* =* 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.
Card Type 1-8
Data Element Sheet
Revised 1/80
A-9
-------
COUNTY NAME
Definition: COUNTY NAME is generated by the Edit from
the COUNTY CODE.
Retrieval
Abbreviation
Columns
Data Element
Length
Data
Justified
Required"
on New Entry
CTNM
iLPHABETTP
Nationally
Controlled YES
Edit Error Messaged:
= Fatal Error
Coding Considerations:
™~«»
7
-------
DATE LAST UPDATED
Definition: D^TE 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 UPDA
Card
Type
Card
Columns
Data Element
Length
Data
Type NUMERIC
Justified
Required
on New Entry
Nationally
Controlled
Valid Values:
Masterfile
Record Type
Masterfile
"Position
Masterfile
Length
20
134-139
6
Edit Error Messages:
*** = Fatal Error * « Warning Error
Coding 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.
Data. Element Sheet
A-ll
Revised 12/79
-------
FEDERAL FACILITY CODE
Definition:
FEDERAL FACILITY CODE identifies facilities owned or operated by
a governmental unit. Federal facilities such as army bases
fall into a separate jurisdiction than private industry.
Retrieval
Abbreviation
Card
Card
Columns
Data~Elernent
Length
~Data
64
NUMERIC
Justified
~Required~
on New Entry
Nationally
Controlled
NO
YES
Edit Error Messages:
* INVALID FEDERAL FACILITY CODE
Valid Values'.
~Masterfile
Record Type
~Masterfile
Position
Master file
Length
20
113
*** _
= 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.
Card Type 2
Data Element Sheet
A- 12
Revised 1/80
-------
NEDS CROSS REFERENCE NUMBER
Definition: NEDS CROSS REFERENCE is the NEDS facility identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Lenqth
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
NEXS
2
55-58
4
Alphanumeric
LEFT
YES
YES
Valid Values:
All' alphanumeric values.
Masterfile
Record Type 20
Masterfile
Position 105-108
Masterfile
Length 4
* = Warning Error
Coding Considerations:
Whenever a new facility is being added as New, this field must be coded.
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.
If the CDS Source Number has been coded properly, the last four positions
of Source Number should correspond to the NEDS Cross Reference Number.
Card Type 2
Data Element Sheet
A-13
Revised 1/80
-------
POLLUTANT AIR QUALITY MAINTENANCE
INDICATOR
Definition: POLLUTANT AIR QUALITY MAINTENANCE INDICATOR indicates whether or not
the pollutant impacts AQMA standards or not
Retrieval
Abbreviation PAQM
Card
Card
Columns
27; 39; 51
Data Element
Length
Dat.a
ALPHANUMERIC
Justified
Required
.on New Entry
NO
Nationally
Controlled
YES
Edit Error Messages:
*** - Fatal Error
Valid Values:
Blank - NO
Y - YES
Masterfile
Record Time
30
Masterfile
"Position
REPEATING
Masterfile
Length
* = Warning Error
Coding Considerations:
The default value is blank indicating 'NO'.
Card Type 3
Data Element Sheet
Revised 12/79
-------
POLLUTANT AIR QUALITY CONTROL INDICATOR
Definition: POLLUTANT AIR QUALITY CONTROL INDICATOR shows whether or not
a source emits a criteria pollutant for which the AQCR is
non-attainment.
Retrieval PAOC
Abbreviation
Card
Type 3
Card
Columns 28; 40; 52
Data Element
Length 1
Data
j-ypg ALPHANUMERIC
Justified
Required
.on New Entry YES
Nationally
Controlled YES _,
Valid Values:
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*** = Fatal Error * = Warning
3
REPEATING
1
Error
Coding Considerations:
blank - Attainment area for a given pollutant
- Attainment area for a given pollutant
A
N
U
- Non-Attainment for primary and secondary
standards for a given pollutant
- Unclassified
Consult the Federal Register for a complete, listing of all attain-
ment and non-attainment areas. This list is periodically
updated in more recent Federal Registers.
Card Type 3
Data Element Sheet
A-15
Revised 1/80
-------
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, S07, HC, CO, NO .
^ X
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
BPLT
N/A
N/A
61
ALPHANUMERIC
Justified
Required
.on Hew Entry
Rationally
Controlled
NO
YES
Valid Values:
Master file
Record Type
Masterfile
Position
Master file
Length
Edit Error Messages:
*** = Fatal Error * = Warning
30
49-108
60
Error
Coding Considerations:
Card Type
Data Element Sheet
A-16
Revised 12/79
-------
POLLUTANT ID
Definition: POLLUTANT-ID is used to identify the pollutant for which pollutant
compliance data is being entered.
Retrieval
Abbreviation PLLT
Card
Type 3
Card
Columns 22-23; 34-35; 46-47
Data Element
Length 2
Data
type ALPHANUMERIC
Justified LEFT
Required
.on New Entry™
Nationally
Controlled YES
Valid Values:
Masterfile
Record Type
Master file
Position
Masterfile
Length
Edit Error Messages:
* INVALID POLLUTANT CODE
*** = Fatal Error * = Warning
30
REPEATING
2
Error
Coding Considerations:
This field must be filled in whenever repeating pollutant data is
entered 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
AB - Asbestos
AS - Arsenic
BE - Beryllium
BZ - Benzene
CD - Cadmium
CE - Coke Oven Emissions
CO - Carbon Monoxide
FL - Fluorides
HC - Hydrocarbons
HG - Mercury
N2 - NO
OD - Odors
OT - Other
PB - Lead
PT - Particulate Matter
S2 - SO
TS - Total Reduced Sulfur
VE - Visible Emissions
VC - Vinyi Chloride
ZN - Zinc
Card Type 3
Data Element Sheet
Revised 12/79
A-17
-------
POLLUTANT COMPLIANCE
Definition:
POLLUTANT COMPLIANCE indicates the worst case source compliance
for a given pollutant based on all of the emission points pro-
ducing the indicated pollutants.
Retrieval
Abbreviation
Ca
Type
Car,
Columns
25; 37; 49
Data Element
Length
ALPHANUMERIC
NO
Data
Type
Justified
Required
_.on New Entry
Nationally
Controlled YES
Edit Error Messages.
* INVALID COMPLIANCE STATUS
_* •* * = Fatal Error
Master file
Record Type
Masterfile
Position
Masterfile
30
REPEATING
= Warning Error
Coding Considerations:
Valid Values;
0 Unknown
1 In violation •
2 In compliance
3 In compliance
4 In compliance
5 In violation,
6 In violation,
7 In violation,
8 No applicable
9 In compliance
• no schedule
by source test
by inspection
by certification
meeting schedule
not meeting schedule
unknown with respect to schedule
state regulation
- closed down
Card Type 3
Data Element Sheet
A-18
-------
POLLUTANT EMISSION CATEGORY
Definition: POLLUTANT EMISSION CATEGORY represents the total potential uncon-
trolled emission of a given pollutant for a source.
Retrieval
Abbreviation
Card
Type
Card
Colwrms
Data Element
Length
Data
Type
PECT
3
26; 38; 50
1
NUMERIC
Justified
Required
.on Neu Entry
Nationally
Controlled
NO
YES
Valid Values
Master fi,le
Record Type
Master file
Position
Master file
Length
Edit Er-ror Messages:
'* INVALID EMISSION CATEGORY
*** = Fatal Error * = Warning
30
Repeating
1
Error
Coding Considerations:
ECAT Value ECDS Description
0
1
2
3
4
Unknown
Less than 100 TPY
100 to 1000 TPY
Over 1000 TPY
Less than 25 TPY
Card Type 3
Data Element Sheet
A- 19
-------
POLLUTANT LOADING
Definition: POLLUTANT LOADING indicates the loading factor for a given
pollutant.
Retrieval
Abbreviation
Card
Type
Card
Colwnns
Data Element
Length
Data
Type
Justified
Required
.on New Entry
Nationally
Controlled
LOAD
3
29-33
41-45
53-57
5
NUMERIC
RIGHT
NO
NO
Valid Values:
Master/tie
Record Type
Masterfile
Position
Masterfile
Length
30
REPEATING
5
Edit Error Messages:
**•* = Fatal Error * = Warning Error
Coding Considerations:
If this field is used, it should be a numeric value representing actual
emissions in tons per year. No decimals or fractions should be used. Leading
spaces are acceptable.
Card Type 3
Data Element Sheet
Revised 12/79
A-20
-------
POLLUTANT DELETE FLAG
Definition:
POLLUTANT DELETE FLAG is used to remove from the Masterfile all
data related to a pollutant.
Retrieval N/A
Abbreviation
Card
Type J
Card o/ . ifi. AS
Columns 24; 36» 48
Data Element
Length
^ta ALPHABETIC
Type
Justified
Required NQ
on Neij Entrif
Nationally ^g
Controlled
Valid Values
Blank or
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
* INVALID POLLUTANT DELETE FLAG
* NO DATA TO FOLLOW DELETE FLAG
*** = Fatal Error * = Warning
'D1
30
REPEATING
1
Error
Coding Considerations:
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 coded next to a pollutant or a Card 3.
Card Type 3
Data Element Sheet
A-21
Revised 1/80
-------
REGION
Definition:
REGION is a two position numeric region identifier.
Retrieval
Abbreviation
uard
Type
(,ard
Columns
Data Element
Length
~l>aia
Type
Justified
Required
on New Entry
Nationally
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.
Masterfile
Record Type 20-47
Masterfile
Position 1-9
Masterfile
Length 2
Edi,t 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-validated; the user may not use a state code which
is not valid 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.
Card Type 1-8
Data Element Sheet
A-22
Revised 12/79
-------
Region Code. States have been assigned to regions as follows:
REGION
01-Boston
02-New York
03_Philadelphia
04-Atlanta
05-Chicago
06-Dallas
07-Kansas City
08-Denver
09-San Francisco
10-5eattie
STATES
Connecticut, Maine, Massachusetts
New Hampshire, Rhode Island, Vermont.
New Jersey, New York, Puerto Rico, Virgin
Islands.
Delaware, District of Columbia, Maryland,
Pennsylvania, Virginia, West Virginia.
Alabama, Florida, Georgia, Kentucky,
Mississippi, North Carolina, South Carolina,
Tennessee.
Illinois, Indiana, Michigan, Minnesota, Ohio,
Wisconsin.
Arkansas, Louisiana, New Mexico, Oklahoma,
Texas.
Iowa, Kansas, Missouri, Nebraska.
Colorado, Montana, North Dakota, South Dakota,
Utah, Wyoming.
Arizona, California, Hawaii, Nevada, Guam,
American Samoa, Trust Territories.
Alaska, Idaho, Oregon, Washington.
Revised 12/79
A-23
-------
Definition: User suppiied.
REGIONAL DATA ELEMENT 1
Retrieval
Abbreviation
RDE1
Type
Card
Columns
67
Data Element
Length
~
ALPHANUMERIC
Valid Values:
All alphanumeric characters.
Justified
NO
Required'
on New Entry
Nationally
Controlled NO_
Edit Error Messages:
Masterfile
Record
Masterfile
Position
20
140
Masterfile
Length
*** = Fatal Error
= Warning Error
Coding Considerations:
Typical usages of this field include identifiers for:
Region I
Region II
Region III
Region IV
Region V
Region VI
Region VII
Region VIII
Region IX
Region X
Attainment/Non-Attainment, Archiving
State delegation for NSPS, NESHAPS
A11 ainmen t/Non-At tainment
MSEE Priority Sources
Attainment/Non-Attainment
Attainment/Asphalt Plants
Major Sources
Card Type l
Data Element Sheet
A-24
Revised 12/79
-------
Definition: User supplied.
REGIONAL DATA ELEMENT 2
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Tupe
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
*** s Fatal Error
RDE2
1
68
1
ALPHANUMERIC
NO
HO
Valid Values:
All alphanumeric characters.
Master file
Record Type ?,fl
Masterfile
Position 141
Masterfile
Length l
* w Warning Error
Coding Considerations:
Typical usages of this field include identifiers for:
Region I
Region II
Region III
Region IV
Region V
Region VI
Region VII
Region VIII
Region IX
Region X
Transitory/Non-Transitory
State Regional Offices
State/Local Offices
State/Local Offices
SO- Priority Status
Not subject to PSD but under review
Vapor Recovery
Indian Reservations
Card Type j_
Data Element Sheet
Revised 12/79
A- 25
-------
Definition: User supplied.
REGIONAL DATA ELEMENT 3
Retrieval
Abbreviation
RDE3
Card
Card
Columns
Datd~EZement
Length
~
69
ALPHANUMERIC
Valid Values:
justified
Required
on New Entry
Nationally
Controlled
Edit Error /
NO
Masterfile
Record Type
Mast&rf^le~~
Position
NO
'Masterfile'
Length
*** -
= Fatal Error
Warning Error
Coding Considerations:
Typical usages of this field include identifiers for:
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 Status
MSEE Identifier
Major SIP Sources
Continuous Monitoring
Subject to State Audit
Mobile Sources
Card Type 1
Data Element Sheet
A-26
Revised 12/79
-------
Definition: User supplied.
REGIONAL DATA ELEMENT 4
Retrieval
Abbreviation RDE4
Card
Type l
Card
Columns 7^74
Data Element
Length 5
Data
Type ALPHANUMERIC
Justified
Required
on New Entry ^°
Nationally
Controlled ' N0
Valid Values:
All alphanumeric characters
Masterfile
Record Type 20
Masterfile
Position 143-147
Masterfile
Length 5
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
If there is a need to have a second SIC Code for a facility, this
field could be used since it appears next to the SIC Code on the
Source Data Report. If this data element is used for the 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:
Region II
Region III
Region IV
Region VII
Region VIII
Region IX
Enforcement Docket Number
Major Bulk Terminal
Additional Staff Codes
Nebraska Case Numbers
Continuous Monitoring
VOC Numbers
Card Type 1.
Data Element Sheet
A- 27
Revised 12/79
-------
Definition: User supplied.
REGIONAL DATA ELEMENT 5
Retrieval
Abbreviation RDE5
Card.
Type i
Card
Columns 75-79
Data Element
Length 5
Data
Type . ALPHANUMERIC
Justified
Required
on New Entry NO
Nationally
Controlled NO
Edit Error Messages:
*** = FataZ £m»»
FaZid 7a£wes:
All alphanumeric characters.
Masterfile
Record Type 20
Masterfile
Position 148-152
Masterfile
Length 5
* = Warning Error
Coding Considerations:
Typical usages of this field include identifiers for:
Region II
Region IX
Region X
Multiple Docket Numbers, Federal
facility types
State Cross Reference Numbers
Tertiary SIC Codes, Federal facility
types.
Card Type 1
Da-ta Element Sheet
A- 28
Revised 12/79
-------
REGIONAL DATA ELEMENT 6
Definition: User supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
RDE6
2
67-76
10
ALPHANUMERIC
NO
NO
Valid Values:
All alphanumeric values.
Masterfile
Record Type 20
Masterfile
Position 153-162
Masterfile
Length W
* = Warning Error
Coding Considerations:
Typical usages of this field include identifiers for:
Region V Additional Pollutants
Region VI PSD Permit Numbers
Region VII ESECA OFU Numbers
Region IX Stage II Non-Compliance
Region X GSA Federal Facility Number
Card Type 2
Data Element Sheet
A-29
Revised 12/79
-------
REGIONAL DATA 9
Definition:
USER SUPPLIED
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Req^red
.on New Entry
Nat't,onally
Controlled
RDE9
3
65-71
7
ALPHANUMERIC
NO
NO
Valid Values
Masterfile
Record Ti/pe
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*** - Fatal Error * = Warning
30
23-29
7
Error
Coding Considerations:
Typical usages of this field include identifiers for:
Region II NPDES Permit Numbers
Region III PSD Permit Numbers
Card Type 3
Data Element Sheet
Revised 12/79
A-30
-------
Definition: USER SUPPLIED
REGIONAL DATA ELEMENT 10
Retrieval KD1Q
Abbreviation
Card
Type 3
CaTd 79 71
Columns 7Z"73
Data Element
Length
^_g ALPHANUMERIC
Justified
Required NO
.on .Vew Entry
Nationally NQ
Controlled
Valid Values:
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*** = Fatal Error * = Warning
30
30-31
2
Error
Coding Considerations:
Card Type 3
Data Element Sheet
Revised 12/79
A- 31
-------
REGIONAL DATA ELEMENT 11
Definition: User suppiied
Retrieval
Abbreviation
Card
Type
Card
Cclvmns
Data Element
Length
Data.
Type
RD11
3
74-75
2
ALPHANUMERIC
Justified
Required
.on New Entry
Nationally
Controlled
NO
NO
Valid Values:
Masterfile
Record Type
I4asterfile
Position
Masterfile
Length
Edit Error Messages:
*** = Fatal Error * = Warning
30
32-33
2
Error
Coding Considerations:
Card Type 3
Data Element Sheet
Revised 12/79
A-32
-------
Definition: User supplied
REGIONAL DATA ELEMENT 12
Retrieval RD12
Abbreviation
Card
Type 3
Card
Columns ?*>
Data Element
Length ^
Do.ta
y^g ALPHANUMERIC
Justified
Required
on New Entry N0
Nationally
Controlled N0
Valid Values:
Masterftle
Reaord Type
Masterfile
Position
Masierfile
Length
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
Region V uses this field to indicate Major Source Enforcement Effort
(MSEE^case delegation.
Card Type 3
Data Element Sheet
12/79
A-33
-------
SIC CODE
Definition:
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
Type
Justified
Required
on New Entry
Nationally
Controlled
SICC
2
59-62
4
NUMERIC
LEFT
YES
YES
Valid Values:
All numerics.
Master-file
Record Type
Masterfile
Position
Masterfile
Length
20
109-112
4
Edit Error Messages:
* SIC SHOULD BE NUMERIC
1
*** =• Fatal Error * = Warning Error
Coding Considerations:
Since many retrievals are based on industry categories, it is important
to 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 pub-
lished by:
Government Printing Office
Superintendant of Documents
Washington, D.C. 20402
Price $8.80
Stock Number 4101-0066
Card Type 2
Data Element Sheet
A-34
Revised 12/79
-------
Definition:
SIC DESCRIPTION
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
Abbreviation SICD
Card
'type
Card
Columns
Data Element
Length 30
Data
Type ALPHABETIC
Justified
Required on
New Entru
Nationally
Controlled YES
Valid Values:
Master File
Record Type'
Master File
Position
Master File
Lenath
Edit Error Messages:
*** = FATAL Error * = 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 Decription in the Process Description field on the
Point
Card Type
Data Element Sheet
A-35
Revised 12/79
-------
SOURCE COMPLIANCE STATUS
Definition:
SOURCE COMPLIANCE STATUS gives the Regional Offices an indication
of whether or not a source is in compliance, not in compliance,
or whether its compliance status is unknown.
Retrieval
Abbreviation SCMS
Card
Type
Card
Columns
'Data Element
Length 1
Data
TbP& XTTTMTTPTr
Justified
Required
on New Entry
Nationally
Controlled YES
Valid Values:
0 through 9
Masterfile •
Record Type
Masterfile
Position
Masterfile
Length
30
21
1
Edit Error Messages:
*** INVALID COMPLIANCE STATUS
*** = Fatal Error * - Warning Error
Coding Considerations:
COMPLIANCE STATUS CODES:
0 Unknown
1 In violation -
2 In compliance
3 In compliance
4 In compliance
5 In violation,
6 In violation,
7 In violation,
8 No applicable
9 In compliance
• no schedule
by source test
by inspection
by certification
meeting schedule
no meeting schedule
unknown with respect to schedule
state regulation
- closed down
With Regulation
The Source Compliance Status should reflect the worst
case compliance of any process within the source. The Compliance Status on
all other points should reflect the worst case compliance of that particular
point.
Card Type 5
Data Element Sheet
A- 36
Revised 12/79
-------
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 DEC. It is not present on any
master file record. A change to SCMS will result in a change
to the description.
Retrieval
Abbreviation SCSD
Card
Type
Card
Columns
Data Element
Length 2°
Data
Type Alphanumeric
Justified Left
Required
on Net} Entry No
Nationally
Controlled Yes
Edit terror Messages:
*** = Fatal Error
Valid Values: See Below
Masterfile •
Record Type
Masterfile
Position
Masterfile
Length
* — Warning Error
Coding Considerations:
SCMS Value SCSDdescription
0 UNKNOWN COMPL STATUS
1 IN VIOL-NO SCHEDULE
2 IN COMPL-SOURCE TEST
3 IN COMPL-INSPECTION
4 IN COMP-CERTIFICATN
5 IN VIOL-MEETING SCHD
6 IN VIOL-NOT MTG SCHD
7 IN VIOL-UNK WRT SCHD
8 NO APPLIC STATE REG
9 IN COMPL-SHU1 DOWN
NOTE: If SCMS is not any of the above values, "Unknown Compliance Status" will
appear as the description.
Card Type
Data Element Sheet
A-37
Revised 12/79
-------
SOURCE COMPLIANCE STATUS - 8 QTRS
Definition: SOURCE COMPLIANCE STATUS represents a historic record of previous
quarterly compliance statuses 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 scs^
Card
Type N/A
Cafd W/A
Columns W/A
Data Element
Length 8
j^pp ALPHANUMERIC
Justified
Re^rei ^ N/A
.on New Entry
National ly VEg
Controlled
Valid Values:
Master file
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*** - Fatal Error * = Warning
30
49-56
8
Error
Coding Considerations:
Users cannot input this value. The entire field is also subdivided into
the following eight retrievable data elements:
Name
Source Comp Status - 1st Quarter
2nd
3rd
4th
5th
6th
7th
8th
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 statuses are
moved into the next higher SGS field. After eight quarters, the oldest com-
pliance 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 sent to the Formal Program
Reporting System. Card Typo
Data Element Sheet
Revised 1/RO
A-38
-------
SOURCE EMTSST"N CATEGORY
Definition: SOURCE EMISSION CATEGORY provides the Regional Offices with a
'" method of ranking or grouping sources by broad emission level
categories to assist in the evaluation of state enforcement
progress.
Retrieval
Abbreviation SECT
Card
Tvve
Card
Columns
Data Element
length 1
Sue NUMERIC
Justified
Required
on New Entry IE
-------
Definition:
SOURCE EMISSION CATEGORY DESCRIPTION
SOURCE EMISSION CATEGORY DESCRIPTION is the English lanaguage des-
cription associated with Emission Category (SECT). It is generated
by the computer based on the value of ECAT. The description is
controlled by the national DEC. It does not reside on the master
file. SECD will automatically change when SECT is updated.
Retrieval
.Abbreviation
SECD
Card
•type
Car'd
Columns
Data Element
Length
Data
Tyr>e
Justified
Required on
JVew Rntr-jj
Nationally
Controlled
20
ALPHANUMERIC
LEFT
NO
YES
Valid Values:
Master F-ile
Record Type
Master File
Position
Master File
Lenoth
Edit Error Messages:
*** = FATAL Error * = WARNING Error
Codina Considerations:
SECT Value
0
1
2
3
4
SECD Description
Unknown
Less then 100 TPY
100 to 1000 TPY
Over 1000 TPY
Less than 25 TPY
Note: If SECD is not one of the above values, "Unknown" will appear
as the description.
Card Type
Data Element Sheet
A-40
Revised 12/79
-------
SOURCE 1TAME
.Definition: SOURCE NAME is a 20 position alphanumeric facility identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Tuve
Justified
Required
on New Entry
Nationally
Controlled
SHME
1
27-46
20
ALPHANUMERIC
LEFT
YES
NO
Valid Values:
All alphanumeric characters.
Mastevfile
Reoord Tyve 20
'Masterfite
Position 28-47
Mast erf -Lie
Lenqth 20
Edit Error Messages:
*** SOURCE NAME REQUIRED ON NEW ENTRY
*** - ratal Error * = Warning Error
Coding Considerations:
The first position of facility name must be filled in on a new trans-
action to allow for source name sorting on the retrieval. Use consis-
tent 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, ad-
dresses, and SIC 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 the attached example developed
by Region V.
Card Type i
Data Element Sheet
A-41
Revised 12/79
-------
** No punctuation unless specified on sheet
Region V Coding Convention for Michigan
Full Name Abbreviation
Asphalt
Aluminum
Authority
Asph
Al
Auth
Air Force Base AFB
Board of Public Light & Power Detroit—Detroit BD Publ L&P
Center
Commission
Cannon
Commonwealth Edison
Concrete
Cement
Consumers Power
Chemical
County
Chicago & Northwestern
Railroad
Construction
Company or Inc. at end of
name
Central Illinois Light
Company
City of Detroit
Central Wayne
Department
Detroit Edison—River
Rouge Plant
Division
Equipment
Ctr
Comm
Can
Com Ed
Con
Gem
Do not Abbrev.
Chem (abbreviate only if necessary)
Co
Chicago & NW RR
Const
Eliminate, do not use
CILCO
Detroit City—use name first followed by city, if
public or municipal company
Wayne C
Dept
Name Under Address put plant name
Detroit River Rouge Pit
Edison
Div
Equip
A- 41A
Revised 12/79
-------
Full Name
Ford Motor Company-Assembly
Div
Foundry (i.e. General
Foundry)
General Motors Corporation
-Fisher Body
Generating
Goodyear Tire & Rubber
Great Lakes Steel-ZUG
Island
Groveland Mine Hanna
Grand Rapids
Hospital
Incinerator
Industries
International
Jones & Laughlin Steel
Light & Power
Lumber
Malleable
Manufacturing
Michigan
Motor
North East (ern)
North West (ern)
Norther Michigan Electrical
Co-op
Abbreviation
Name Under Add Put Plant Name
Assembly Div
Spell out—do not abbreviate
Ford
Motor
Name Under St. Add Put Plant Name
CMC Fisher Body
Genr
Goodyear Tire&Rubber No blanks between "&"
Name Under St. Add Put Plant Name
Great Lakes Zug Island
Steel
Hanna Mining Groveland Mine
GD Rapids
Hosp
Incin
Indst
Intnl
Jones & Laughlin spell out, omit Steel
L&P
Lmbr
Malleb
Mfg
Mich
Mtr
NE
NW
Northern Mich Elec
A-41B
Revised 12/79
-------
Full Name
Operation
Packaging Corporation of
America
Paving
Plant
Power
Project
Products
Public
Railroad
Refractories
Refining
Sanitation
Sewage Treatment Plant
(Wastewater)
State-Street
Station
Southside Foundry
Southeast-Southwest (ern)
Terminal
Training
Transportation
Township
United States Steel
University
Warehouse
Water & Power
Water Treatment Plant
Wholesale
Abbreviation.
Op
Packaging Corp AM
Pav
Pit
Pwr
Prod
Publ
RR
Ref
Re fin
Sani
Stp
St
Sta
Spell out, do not abbreviate
SE-SW
Term
Trn
Trans p
Twp
US Steel no spaces
Univ
Whse
W&P
WTP
Whsl
A-41C
Revised 12/79
-------
SOURCE NUMBER
Definition: SOURCE DUMBER is a five digit numeric facility identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Lenqth
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
SRCE
1-8
9-13
5
NUMERIC
LEFT
YES
UO
Valid Values:
All numeric values
Masterfile
Record Type
Masterfile
Position
Mas terfHe
Length
20-47
9-13
5
Edit Error Messages:
*** SOURCE NUMBER MUST BE NUMERIC
*** = Fatal Error * = Morning Error
Coding Considerations:
The NEDS source numbering convention should be used wherever possible
when adding a new source. Otherwise, assign the next highest sequen-
tial source number within the county. Usually, the last four digits
of Source Number are the sama 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.
Card Type 1-3
Data Element Sheet
A-42
Revised 1/80
-------
STAFF NAME (SOURCE)
Definition:
STAFF NAME (SOURCE) is a fifteen position name generated from
the Staff Code found on Card 2, positions 77-79.
Card "
Colunr/is
"Data'Element'
Length
~l)ata
Retrieval
Abbreviation
Card
Justified
Required"
on New Entry
Nationally
Controlled
STFS
ALPHANUMERIC
Valid Values:
All names are on the Personnel Tabl
maintained by the national DEC.
Please call the DBC to make addi-
tions or changes to this table.
Masterfile
Record Type
Masterfile
Position
20
119-133
YES
Masterfile
Length
15
Edit Error Messages:
*** _
* Fatal Error
Horning Error
Coding Considerations:
During each update cycle, the Staff Name is generated based on the
source's Staff Code. By changing the staff name associated with a
staff code on the Personnel 'Table, all input transactions and master-
file records will carry the new staff name.
Revised 12/79
Data Element Sheet
A-43
-------
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
Card
Columns
Data Element
Length
Data
Justified
Required
on New Entry
^Nationally
Controlled
PERS
2
77-79
3
ALPHANUMERIC
LEFT
NO
1 '
YES
Valid Values:
Must exist on the Personnel Table
maintained by the national DBC.
Please call the DBC to add, change
or delete entries to this table.
Master file
Record Type 20
Master file
Position 116-118
Master file
Length 3
Edit Error Messages:
* INVALID STAFF CODE
*** - Fatal Error * - Warning Error
Coding Considerations:
The assigned person's name is generated by the Update Program based
on the name found on the Personnel Table.
Card Type 2
Data Element Sheet
A-44
Revised 12/79
-------
Definition:
PRIORITY CODE
categories.
numerous priority
Nationally
Controlled
YES
Master File
Record Type
faster File
Position
—
taster File
= FATAL Error
Coding Considerations:
value
0
M
N
R
I
P
S
U
c
0
X
Description
Accelerated Envorcement program
Municipal Incinerator
Nuclear Power Plants
Refinery
Iron and Steel, non-priority
Iron and Steel, Priority
Smelter
Undetermined Power Plants
Coal Fired Power Plant
Oil Fired Power Plant
Coal 6, Oil-Fired Power Plant
Y
Z
G
A
Coal & Gas-Fired Power Plant
Oil & Gas-Fired Power Plant
Gas-Fired Power Plant
Power
Card Type
Data Element Sheet
A- 45
Revised
-------
STATE
Definition;
STATE is a two-position numeric state code. The State codes
are derived from the Storage and Retrieval of Aerometric
Data Manual (SAROAD) published by OAQPS.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Jii «? 'hi fied
Required
on Net) Entry
Nationally
Controlled
STTE
1-8
3-4
2
NUMERIC
LEFT
YES
YES
Valid Values:
$1 through 56
See attachment showing the states
associated with each state code.
Master f^le
lleaord Type 20-47
Masterfile
Position 3-4
Master file
Length 2
Edit Error Messages:
*** INVALID STATE CODE
*** STATE HOT IN REGION
«** Fatal Error *= Warning Error _
Coding 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.
Card Type 1-3
Data Element Sheet
A-46
Revised 1/80
-------
C°de-
STATE CODE:
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
CDS
tm uses the following two digit SAROAD state codes:
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Alabama
Alaska
Arizona
Arkansas
California
Colorado
Connecticut
Delaware
District of Columbia
Florida
Georgia
Hawaii
Idaho
Illinois
Indiana
Iowa
Kansas
Kentucky
Louisiana
Maine
Maryland
Massachusetts
Michigan
Minnesota
Mississippi
Missouri
Montana
Nebraska
Nevada
New Hampshire
46
47
48
49
50
51
52
53
54
55
56
Utah
Vermont
Virginia
Washington
West Virginia
Wisconsin
Wyoming
American Samoa
Guam
Virgin Islands
Trust Territories
New Jersey
New Mexico
New York
North Carolina
North Dakota
Ohio
Oklahoma
Oregon
Pennsylvania
Puerto Rico
Rhode Island
South Carolina
South Dakota
Tennessee
Texas
Revised 1/80
A-46A
-------
Definition:
STATE ABBREVIATION is a two position alphabetic state code
used by the U. S. Post Office. It is generated for each
facility by CDS. It is useful for retrieval processing.
Retrieval
Abbreviation
Card
Card
Columns
Data Element
Length
Data
Tvoe
Required on
New Entry
Justified
Nationally •
Controlled
STAB
N/A
N/A
Alphanumeric
N/A
Yes
Edit Error Messages:
Valid Values:
Master file
Record Type
20
Master file
Position
83-84
Master file
Length
Coding Considerations:
AL - Alabama KY
AK - Alaska LA
AZ - Arizona ME
AR - Arkansas MD
CA - California MA
CO - Colorado MI
CT - Connecticut MN
DE - Delaware MS
DC - District of MO
Columbia MT
FL - Florida NE
GA - Georgia NV
HI - Hawaii NH
ID - Idaho NJ
IL - Illinois NM
IN - Indiana NY
IA - Iowa NC
KS - Kansas ND
Kentucky
Louisiana
Maine
Maryland
Massachusetts
Michigan
Minnesota
Mississippi
Missouri
Montana
Nebraska
Nevada
New Hampshire
New Jersey
New Mexico
New York
North Carolina
North Dakota'
OH - Ohio
OK - Oklahoma
OR - Oregon
PA - Pennsylvania
PR - Puerto Rico
RI - Rhode Island
SC - South Carolina
SD - South Dakota
TN - Tennessee
TX - Texas
UT - Utah
VT - Vermont
VA - Virginia
WA - Washington
WV - West Virginia
WI - Wisconsin
WY - Wyoming
AS - American Samoa
GU - Guam
VI - Virgin
Islands
TT - Trust
Territories
Card Type
Data Element Sheet
Revised 1/80
A-47
-------
u
used
N NUMBER is an alphanumeric
the state to identify a facility.
Gara
-^E*
C"a?a
Columns
Data Element
Length
^Datd "
Justified
Required
on New Entry
STRG
40-54
15
ALPHANUMERIC
• mil .•»•• i
LEFT
NO
Nationally
Controlled NO
Edit Error Messages:
Valid Values:
All alphanumeric characters.
Masterfile
Position
Masterfile
Length
90-H
15
*** =
= Fatal Error
Coding Considerations:
* =
= Warning Error
When the state identifier is consistantly entered into this field,
CDS reports can be sorted in the same way as the state's files are
sortsd •
Card Type 2
Data Element Sheet
A-48
Revised 1/80
-------
STREET ADDRESS
Definition: STREET ADDRESS is the actual location of the facility; it is
not the headquarters address.
~~Cara
Columns
~T)ata
Type
Retrieval
Abbreviation
Type
Hata Element
Length
Justified
Required
m New Entry
Nationally
Controlled
STRT
47-66
20
ALPHANUMERIC
LEFT
NO
Edit Error Messages:
*** = Fatal Error
Valid Values:
All alphanumeric characters.
Masterfile
__
'Masterft,le
Position
Masterfile
Length
48-67
20
* = Warning Error
Coding Considerations:
If the mailing address of the facility is different from the street
address the mailing address can be coded on a source comment record
tcarH) .Comment Line A and B. There are special input coding sheets
designed for mailing address information.
Card Type 1
Data Element Sheet
A-49
Revised 1/80
-------
ZIP CODE
Definition: ?rp rnrn? .,0 ... c,
ZIP CODE is the five digit numeric postal zone.
Retrieval
Abbreviation
_Type
Card
Columns
uata Element
Length
— n — ~
Data
Type
Justified
Kequired
on New Entry
National ly
Controlled
tictit Error Messages:
* ZIP CODE SHOULD BE
*** ~ Fatal Error
ZIPC
••
2
—
35-39
5
NUMERIC
LEFT
NO
NO
— — — -
Valid Values:
All numeric values.
Masterf^le
Record Type
Masterfile
Position
Masterfite
Length
NUMERIC
*_~_ Warning Error
20
85-39
5
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.
Card Type 2
Data Element Sheet
A-50
Revised 1/80
-------
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 cap-
ability of 150 million BTU per hour would have 15 in
Capacity Code.
Valid Values
00-99
Abbreviation
Card
Columns
Data Element
Length
Master file
Record Type
Master file
Position
Required.on
New En
Justified
Nationally--.
Controlled
Edit Error Messages:
Master file
th
Coding Considerations:
-
pacity equal to or greater than 100 MMBTUH.
Users should note that this field was once used for tracking the
NEDS Point Cross Reference (NEXP) .
of this field.
Card Type 5
Data Element Sheet
A-51
Revised 1/80
-------
Definition:
COMPLIANCE STATUS
COMPLIANCE STATUS gives the Regional Office an indication
or whether > ^ * *™^ is in compliance, not in compliance,
or whether its compliance status is unknown, at the point level
Retrieval
AVhfo.viaticm
Card
'type
Card
Columns
Data Element
Length
Data
CMST
5
30
1
NUMERIC
Justified
Required on
Nationally
Controlled
YES
YES
VaHd Values:
0 through 9
Master File
Record Type
Master File
Position
Master File
Lenath
34
31
1
&dit Error Messages:
*** INVALID COMPLIANCE STATUS
*** = FATAL Error * = WARNING Error
Coding Considerations:
Must be coded on the point 000; raay be coded on the other emission
points. COMPLIANCE STATUS CODE: emission
0
1
2
3
4
5
6
7
8
9
Unknown
In violation •
In compliance
In compliance
In compliance
In violation,
In violation,
In violation,
No applicable
In compliance
- "no schedule
by source test
by inspection
by certification
meeting schedule
not meeting schedule
unknown with respect to schedule
state regulation
- closed down
The Compliance Status on Point 000 (entire source) should reflect the
|orsj: compliance of any process within the source. The Compliance
Status on^all other points should reflect the worst case compliance of
that particular point.
At the 000 point, this is the same as SCMS.
Card Type
Data Element Sheet
A-52
Revised 1/80
-------
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 DEC. It is not present on any master file record. A
change to CMST will result in a change to description.
Retrieval _ cms
A"hhr>0.i)i,Thion
Card
'type
Card
Columns . . _.
Data Element
Length **
^*° ALPHANUMERIC
'tfyg '
Justified LEFT
Required on
Wei,! F,n1-ru
Nationally
Controlled ^^
Valid Values:
See Below
Master File
Record Type
Master File
Position
Master File
Lenath
Edit Error Messages:
*** = FATAL Error * = WARNING Error
Coding Considerations;
CMST Value
0
1
2
3
A
5
6
7
8
9
CMDS Description
UKNOWN COMPL STATUS
IN VIOL-NO SCHEDULE
IN COMPL-SOURCE TEST
IN COMPL-INSPECTION
IN XOMPL-CERTIFICATN
IN VIOL-MEETING SCHD
IN VIOL-NOT MTG SCHD
IN VIOL-UNK WRT SCHD
NO APPLIC STATE REG
IN COMPL-SHUT DOWN
Note: If CMST is not any of the above values, "Compl Status unknown"
will appear as the description.
Card Type
Data Element Sheet
A-53
Revised 1/80
-------
EMISSION CATEGORY
Definition:
/rewieuat.
~Cafa~
L'dta Element
Length
Data
Type
ECAT
" , — _
5
— • — • — __
49
1
NUMERIC
Justified
on New Entry
Controlled
YES
YES
Valid Values:
0 = unknown
1 = Less than
2 = 100-1000
3 = over 1000
4 = Less than
Mast erf ile
Record Type
Masterfile
Position
Master file
Length
100 TPY potential
TPY potential
TPY potential
25 TPY potential
34
50
1
Edit Error Messages: " — —
* INVALID EMISSION CATEGORY"
__*** = Fatal Error * „ Vcuming ^^
Coding Considerations:
Must be coded on point
; nay be coded on the other emission points.
o?thf entire 'so ^ ^--Category n,ust reflect the potential emission
ECAT cJ!T E K «f ° 8 t0 the ReSional Mr P"gram Guidance. The
?nvLory o±ut a'd « \ ^ ***** COnsultin8 the NEDS emission
source? ? ^ determinlnS Potential emissions for the entire
At the
point, this is the same as SECT.
Card Type 5
Data Elznent Sheet
A-54
Revised 1/80
-------
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 DBG. It
does not reside on the master file. ECDS will automatically change when ECAT
is updated.
Retrieval
Abbreviation ECDS
Card
Type
Card
Columns
Data Element
Length 20
Data
Fwe Alphanumeric
Justified Left
"Required
on Neu Entry No
Nationally
Controlled Yes
Edit Error Messages:
*** = Fatal Error
Valid Values: See Below
Master file '
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error
Coding Considerations:
*
ECAT Value ECDS Description
0
1
2
3
4
Unknown
Less than 100 TPY
100 to 1000 TPY
Over 1000 TPY
Less than 25 TPY
Note: If ECAT is not one of the above values, "Unknown" will appear as the
description.
Care' Type
Data Element Sheet
A-55
Revised 1/80
-------
EMISSION POINT NUMBER
Definition:
EMISSION POINT NUMBER is a three digit numeric emission
point identifier. If one physical emission point duces
several pollutants, each pollutant is assigned a separate
emission point number. Emission point 000 refers to the
entire source.
4
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
PTNO
1-8
14-16
3
NUMERIC
LEFT
YES
NO
Valid Values:
000 through 999
Mast erf He
Reaord Type
Masterfile
Position
Masterfile
Length
20-47
14-16
Edit Error Messages:
*** EMISSION POINT MUST BE ZEROS
*** POINT MUST BE GREATER THAN ZERO
*** DO NOT DELETE POINT 000
*** - Fatal Error * = Warning Error
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 must 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 pointj the third position can be
pollutant specific. For example, if a boiler has a NEDS point number
02, the CDS point number 020 could represent the particulate emissions
and point 021 could represent the S00 emissions.
Card Type 1-8
Data Element Sheet
A-56
Revised 1/30
-------
MULTIPLE CROSSREFERENCE
Definition: MULTIPLE CROSSREFERENCE 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
Type
Card
Columns
Data Element
Length
Data
Tune
j-yit"* — _ .1
Justified,
Required
on New 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 Error Messages:
* MULTIPLE XREF SHOULD BE NUMERIC
*** - Fatal Error * = Warning Error
Coding Considerations:
If emission points 010, 011, and 012 refer to three different pollutants
being emitted from one process or piece of equipment, points 011 and.
0 12 should cross-reference 010,
Card Type 5
Data Element Sheet
Revised 1/80
A-57
-------
OLD COMPLIANCE STATUS
Definition: OLD COMPLIANCE STATUS represents a historic record of previous
quarterly compliance statuses for the past eight quarters. It
is generated on a quarterly basis by the Update Program based
on information found in the CMST field.
4
Retrieval
Abbreviation
Card
Card
Colwnns
Data Element
Length
~Data
Type
Justified
Required
pn New Entry
ocs0
N/A
N/A
ALPHANUMERIC
Valid Values:
Masterfile
Record Type
34
Nationally
Controlled^
Edit Error
N/A
YES
Messages:
- Fatal Error
Masterfile
Position
81-88
Masterfile
Length
* = Warning Error
Coding Considerations:
Users cannot input this value. The entire field is also subdivided into
the following eight retrievable data elements:
Name
Old Comp Status -
1st Quarter
2nd
3rd
4th
5th
6th
7th
8th
Retrieval Abbreviation
OCS1
OCS2
OCS3
OCS4
OCS5
OCS6
OCS7
OCS8
On October 1976, the Compliance Status found on each emission point record
was placed in OCS1. During each subsequent quarter, the current compliance
status is stored in OCS1, and all previous quarterly compliance statuses are
moved into the next higher OCS field. After eight quarters, the oldest com-
pliance status will be dropped to make room for the next quarterly historic
compliance status.
With these eight historic compliance status fields, users aan
compare current compliance status with previous compliance status sent to the
Formal Program Reporting Card Type System.
Data Element Sheet
Revised 1/80
-------
POLLUTANT CODE
Definition: POLLUTANT CODE indicates the type of pollutant which that
particular emission point emits.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages
* INVALID POLLUTANT
*** = Fatal Error
PLUT
5
32-33
2
ALPHANUMERIC
LEFT
YES
YES
Valid Values:
See below for the table of valid
values .
Masterfile
Record Type 34
Masterfile
Position 33-34
Masterfile
Length 2
.
CODE
* = Warning Error
Coding Considerations:
Should be input on all new emission points.
values:
VALID VALUES
N2
OD
OT
P3
PT
S2
Use one of the following
A3
AS
BE
BZ
CD
CE
CO
FL
HC
HG
- Asbestos
- Arsenic
- Beryllium
- Benzene
-r Cadmium
- Coke oven Emissions
- Carbon Monoxide
- Fluorides
- Hydrocarbons
- Mercury
TS
VC
VE
- -102
- Odors
- Other
- Lead
- Particulate Matter
- SO
- Total Reduced Sulfur
- Vinyl Chloride
- Visible Emissions
ZN - Zinc
Card Type 5
Data Element Sheet
Revised 1/80
-------
PROCEDURAL COMPLIANCE
Definition- PROCEDURAL COMPLIANCE should be used.for all NSR, PSD, NSPS, NESHAPS
i Uand SIP facilities under construction or subject to performance t-°~*-
continuous monitors, and other procedural requirements under such
programs. This field indicates the compliance status of a facility
with respect to all applicable procedural requirements. Use CMST to
indicate the compliance of an operating facility subject to immediatelj
effective emission regulations.
Retrieval
Abbreviation
Card
•Type
Car'd
Columns
Data Element
Length
Data
CMS 2
5
79
1
Alphanumeric
Justified
Required on
flew Entry
Nationally
Controlled
No
Yes
Valid Values:
Master File
Record Type
Master File
Position
Master File
Lenath
34
80
1
Edit Error Messages:
*** = FATAL Error * = WARNING Error
Coding Considerations:
Code
A
B
C
8
Blank
V
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).
Card Type
Data Element Sheet
A-60
Revised 12/79
-------
PROCESS- D?.S.. .1 PTTnisT
Definition:
PROCESS DESCRIPTION is a brief description of the physical
emission point such as a boiler or a 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
Card
Type
Card
Columns
Data ^Element
length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
PROS
5
50-74
25
ALPHANUMERIC
LEFT
YES
NO
Valid Values:
All alphanumeric characters.
Masterfil&
Record Type 34
Masierfile
Position 51-75
Mast erf He
Length 25
* = Warning 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 descriptions, 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.
Cord Type 5
Data Element Sheet
A-61
Revised 1/80
-------
REGIONAL DATA ELEMENT 7
Definition: User supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages
*** = Fatal Error
RDS7
5
78
1
ALPHANUMERIC
NO
NO
Valid Values:
All alphanumeric values.
Master file
Record Type 34
I4asterfile
Position 79
Master file
Length 1-
•
* = Warning Error
Coding Considerations:
Typical usages of this field include identifiers for:
Region I
Region III
Region VII
State Compliance Status
(where it is different from CMST)
Opacity Monitoring
Air Program Status of NSPS points
Card Type 5
Data Element Sheet
Revised 1/80
A-62
-------
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.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
tiata
Type
Justified
Required
on flew Entry
Nationally
Controlled
Edit Error Messages:
* SCC CODE SHOULD BE
*** =r Fatal Error
SCC3, SCC6,
SCC8
5
20-27
8
NUMERIC
LEFT
NO
YES
Valid Values:
Consult the NEDS coding
a list of valid values.
manual for
The CDS
edit accepts blanks or an 8 posi-
tion numeric field.
Masterfile
Record Type 34
Masterfile
Position 21-28
Masterfile
Length 8
NUMERIC
* = Warning Error
Coding Considerations:
Although all 8 positions must be coded on all points other than 000, the
retrieval can select on either the first 3 positions, the first 6 positions,
or all 8 positions. SCC 3 retrieves on the first 3 positions of the SCC
Code; SCC6 retrieves on. the first 6 positions of sr.n HoHe; *nd SCC 8 re-
trievess on the first 8 positions of the SCC Code.
For some industries, DSSE has expanded on the values in the NEDS coding
manual; special guidance has been provided for these SCC codes.
SCC8 is at the present a confidential data element. Users mn
-------
SIP CODE
Definition: SIP CODE provides the Regional Office with a method of
identifying the type of enforcement schedule which has been
imposed on a source not in Compliance.
Retrieval
Abbreviation SIPC
Card
Type 5
'Card
Columns 31
Data Element
length 1
Data
Type NUMERIC
Justified
Required
on new Entry NO
Nationally
Controlled YES
Valid Values:
Blank, 0 through 9.
Master file
Record Type
Masterfile
Position
Masterfile
Length
34
32
1
Edit Error Messages:
* INVALID SIP CODE
*** = Fatal 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).
blank
0
1
2
3
4
No Schedule
Schedule Status Unknown
Federally enforceable DCO
Federally Approved SIF Schedule
Federal Court Decree 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
Revised 1/80
Card Type 5
Data Element Sheet
A-64
-------
SIP CODK DESCRIPTION
Definition:
^finiti
SIPC).
Sip Code Description is the English language description of Sip Code
Tt is generated by the computer based on the value of SIPC. This des-
It is not present on the master file,
(SIPC)
B cription is controlled by the national DEC.
The description will automatically change when SIPC is changed.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required.
on New Entry
Nationally
Controlled
SIDS
20
Alph anume r i c
Left
No
Yes
Valid Values: gee Below
Masterfile '
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*** = Fatal 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 cr unknown).
blank
0
1
2
3
4
5
6
7
8
9
No Schedule
Schedule Status Unknown
Federal/State DCO
Federal SIP Schedule
Federal Court Order
Federal Consent Decree
Federal Schedule Being Developed
Non-Federal Schedule
Non-Federal Schedule Being Developed
Reserved
Subject to offsets
Card Type
Data Element Sheet
Revised 1/80
A-65
-------
STATE REGULATION
Definition:
STATE REGULATION contains the state's emission regulation
number for a given pollutant. In the case of NSPS or NESHAPS
facilities, use the federal or state regulation number found in
the Federal Register. CFR 60.XX.
Retrieval
Abbreviation SREG
Type 5
Card
Columns 34-48
Data Element
Length 15
Data
Type ALPHANUMERIC
Justified
Required
on New Entry NO
Nationally
Controlled NO
Valid Values:
All alphanumeric values.
Master file
Reaord Type 34
Masterfile
Position 35-49
Master file
Length 15
Edit Error Messages:
*** ~ Fatal Error * - Warning Error
Coding Considerations:
Card Type 5
Data Element Sheet
A-66
Revised 1/80
-------
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
Type
Card
Columns 20~34
Data Element
Length 15
Data
•type ALPHANUMERIC
Justified LEFT
Required
on New Entry
Nationally
Controlled YES
Valid Values:
Please call the national DEC to add
or change action descriptions on
the regional Action Table.
Masterfile
Reoord Type 46
Masterfile 107-156
Position 40-54
Masterfile 50
Length 15
Edit Error Messages:
*** - Fatal Error * - 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 Edit pro-
gram 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 con-
trolled by the National DEC. It can be a replacement for the regional
Action Type "OTHER - SEE COMMENTS BELOW". Since comments are not re-
trievable 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.
Data Element Sheet
A-67
Revised 1/80
-------
ACTION_HUMBCR
Definition: ACTION NUMBER is a two digit numeric sequential action identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
ANUM
1-8
17-18
2
NUMERIC
LEFT
YES
NO
Valid Values:
00 through 99
Maaterfile
Record Type
Master file
Position
Master file
Length
20-47
17-18
2
Edit Error Messages:
*** ACTION NUMBER MUST BE ZEROS
*** ACTION NUM MUST BE GREATER THAN ZERO
*** = Fatal Error * = Warning Error
Coding Considerations:
Actions should be assigned sequentially starting "ith 01. When ad
-------
ACTION TYPE
Definition:
ACTION TYPE is a two position alphanumeric action description
identifier.
Retrieval
Abbreviation ATPE
Card
Type 7
Card
Columns 53-54
Data Element
Length 2
y?*a ' ALPHANUMERIC
2ype
Justified LEFT
Required
on flew Entry YES
Nationally
Controlled ^s
Valid Values:
Must be on Action Table controlled
by national DBG.
Action Type 00 indicates an action
type which is user defined.
toaster file
Record Type 46
Masterfile
Position 21-22
Masterfile
Length 2
Edit Error Messages:
*** INVALID ACTION TYPE
*** ACTION TYPE REQUIRED ON NEW ENTRY
*** « Fatal Error * = Warning Error
Coding Considerations:
Please call the national DEC 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.
This capability should eliminate the need for using an Action Type
meaning "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 DSSE
guidance material 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 nany action types are confidential, users should use a password
on the Retrieval Card Type 20 to obtain action level information en
Retrievals.
Card Type 7
Data Element Sheet
Revised 1/80
-------
DATE ACHIEVED
Definition:
DATE ACHIEVED is the date on which an action is performed or
completed in month, day, year format. rrormed or
Retrieval
Abbreviation
Card
Type
Uard ~~ "
Columns
Data Kl&tnent
Length
~ Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages
* INVALID DATE ACHVD
,. *** - Fatal Error
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.
Master file
Record Type 46
Master file
Position 29-34
Masterfile
Length 6
- OUTPUT ZEROS
* = Warning Error
Coding Considerations:
If an error is encountered in the date field, the bad month, day or
year zs zeroed out by the edit program. An asterisk on a change trans-
action for this field will zero out the field on the masterfile
Card Type 7
Data Element Sheet
Revised 1/80
A-70
-------
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
date element, users can produce Milestone Reports or
Quick Look Subtotals for actions during a given month.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Required. on
New Entry
Justified
Nationally--.
Controlled
DAYM
N/A
N/A
4
Numeric
N/A
N/A
No
Valid Values:
Master file
Record Type
Master file
Position
Master file
Length
46
29-32
4
Edit Error Messages:
Coding 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
EPA VE EVALUATION
EPA CIV/CRIM ACTION
REGIONAL ADES TOTALS
REGION
TOTAL
46
109
190
26
371
DAYM
7804
12
42
48
7
109
DAYM
7805
18
39
62
15
134
DAYM
7806
16
28
80
4
128
Card Type
Data Element Sheet
A-71
Revised
-------
DATE SCHEDULED
Definition:
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
Length
Data
Typt
Justified
Required
on flew Entry
Nationally
Controlled
DTSC
7
61-66
6
NUMERIC
LEFT
YES
NO
Valid Values:
Blanks or zeros are
Otherwise, day must
and 31; month must
and 12 , and year mu
than 60.
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
acceptable.
be between 01
be between 01
st be greater
46
23-28
6
Edit Error Messages:
* INVALID DATE SCHED - OUTPUT ZEROS
* DATE SCHED REQUIRED ON NEW ENTRY
*** _ patai Error * = Warning Error
Coding Considerations:
If an error is encountered in the date field, the bad month or day or
year is zeroed out. If this field is lef-t blank on s new transaction
and if the Date Achieved is valid, the Date Achieved is moved into
this field by the Edit Program.
Card Type 7
Data Element Sheet
Revised 1/80
A-72
-------
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
Tupe
Card
Columns
Data Element
Length
Data
Tirpe
Required, on
Jfl&tA fi'wf'yiij
Justified
Nationally--
Controlled
DSYN
N/A
N/A
4
Numeric
N/A
N/A
No
Valid Values:
Master file
Record Tyve
Master file
Position
Master file
Length
46
23-26
4
Edit Error Messages:
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
DAYM
7804
12
42
48
7
109
DAYM
7805
18
39
62
15
134
DAYM
7806
16
28
80
4
128
Card Type
Data Element Sheet
Revised 1/80
A-73
-------
CIVIL PENALTY AMOUNT
Definition:
PENALTY AMOUNT indicates the civil penalty im-
posed on a facility.
Retrieval
Abbreviation
PLTY
Card
Card
Columns
46-52
Data Element
Length
Data
Numeric
Required, on
New Entry
No
Valid Values:
All numeric values
Master file
Record Time
46
Justified
Right
Natzonally--
Gontrolled
No
Edit Error Messages:
Master file
Position
93-99
Master file
Length
Coding Considerations:
This field should be used in conjunction with the following action types:
Z4 State civil penalty.
Z6 Federal civil penalty.
Dollar amounts must be right justified; they should be rounded to the
nearest $100. No commas, dollar signs, or periods must be used.
Please refer to future DSSE quidance documentation for additional details,
which will be an addendum to this manual.
Card Type 7
Data Element Sheet
A-74
Revised 1/80
-------
Definition: User supplied.
REGIONAL DATA ELEMENT 8
Retrieval
Abbreviation
Card
Type
Card
Columns
~Data Element
Length
Data
Tifpe
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages
*** « Fatal Error
RDE 8
7
72 - 73
2
ALPHANUMERIC
LEFT
NO
NO
Valid Values:
Mast erf He ^
Record Type
Master file 57 _ 5g
Position
Master file 2
Length
•
* = Warning Error
Coding Considerations:
Typical usages of this field include identifiers for:
Region V
Region VII
S0? Compliance Status
Opacity Readings
Card Type 7
Data Element Sheet
Revised 1/80
A-75
-------
RESULTS CODE
Definition:
RESULTS CODE indicates the results of an action such as action
achieved, action not achieved, or action rescheduled.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
STAC
7
70-71
2
NUMERIC
LEFT
NO
YES
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
DBG.
Master file
Record Type 46
Mast erf He
Position 55-56
Masterfile
Length 2
Edit Error Messages:
* INVALID RESULTS CODE
*** j= Fatal Error * = Warning Error
Coding Considerations:
The results code does not indicate the success of an action, but rather
it indicates whether or not the action was carried out, or whether
another action should be referred to.
Please call the national DBC to add, change, or delete entries on the
Results-Code Table for your region. Hee Chapter 10 for instructions
on how to obtain the.jnost current Results Code Table for your region.
Card Type 7
Data Element Sheet
Revised 1/80
A-76
-------
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 master file and is updated
when STAC is changed.
Retrieval
Abbreviation
RSTD
Card
Type
Card
Colianns —
Data Element
Length
Data
Type
_ *nf~
Justified
""Required.
on New Entry
Nationally
Controlled
15
Alphanumeric
Left
No
Yes
Valid Values:
The Results Code (STAC) must exist
on the RESULTS CODE TABLE controlled
by the national DBC.
Master file '
Record Type
Masterfi-le
Position
Masterfile
Length
Edit Error Messages:
*** = Fatal Error * = Vanning
46
157
15
Error
Coding Considerations:
See Chapter 10 for instructions for listing the most current
Results Code Table.
Car? Type
Data Element Sheet
A-77
Revised 1/80
-------
STAFF NAME (ACTION)
STAFF NAME (ACTION)is . f.fteen
the Staff Code found on Card 7, positions 67-69.
Car
Columns
Retrieval
Abbreviation
STFA
Card
Data Element"
Length
ALPHANUMERIC
Justified
Required
on flew Entry
Nationally
Controlled YES
Edit "Error Messages:
Valid Values:
All names are on the Personnel
Table maintained by the national
DBG. Please call the DEC to make
additions or changes to this table,
Maaterfile
Record
Masterflle
Position
46
63-77
MastevfCTe~
Length
15
*** = Fatal Error
Coding Considerations:
Warning Error
Act ffris 8ene^ted based on the
Action Staff Code. By changing the staff name associated with a
r^f a ^r thS P"Sonnel Table' a11 ^P"t transactions and masterfile
records will carry the new staff name.
See Chapter 10 for instructions for listing the most current Staff
Table.
Data Element Sheet
A-78
Revised 1/80
-------
ACTION STAFF CODE
Definition:
ACTION STAFF CODE is a three position code referring to the
staff member assigned to complete the action.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages,
* INVALID STAFF CODE
*** = Fatal Error
PERA
7
67-69
3
ALPHANUMERIC
LEFT
NO
YES
Valid Values:
Must exist on the Personnel Table
controlled by the national DEC.
The first position must be alpha;
the next two numeric. When re-
questing changes to this table,
be sure to give the DEC full title
information as well.
Masterfile
Record Type 46
Masterfile
Position 35-37
Master file
Length 3
* » Warning Error
Coding Considerations:
Please call the national DEC to make additions, changes, or deletions
to the Personnel Table.
Card Type 7
Data Element Sheet
Revised 1/80
A-79
-------
STAFF TITLE
Definition:
STAFF TITLE is a fifteen position title generated from the
Staff Code found on Card 7, positions 67-69.
Retrieval
Abbreviation
tara
Card
Columns
Data Element"
Length
Data
TITL
ALPHANUMERIC
Valid Values:
All titles are on the Personnel
Table maintained by the national
DBG. Whenever making any changes
to this table, be sure to give
the DEC full title information.
justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
faster file
Record Type
Masterfile
Position
46
78-92
MasterfiTe"
Length
15
*** = Fatal Error
- Warning Error
Coding Considerations:
During each update cycle, the Staff Title is generated based on the
Action 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.
Data Element Sheet
A-80
Revised 1/80
-------
CARD CODS
Definition:
CARD CODE is a one digit numeric field which identifies the type
of fixed format information found on the CDS input punch card.
Retrieval
Abbreviation
Card
Tiipe 1-8
Card
Columns 19
Data Element
Lenath 1
"~t)ata
Tuna NUMERIC
Justified
Required
on flew Entry YES
Nationally
Controlled YES
Edit Error Messages:
*** INVALID CARD CODE
*** - Fatal Error
Valid Values:
1 = source record
2 = source record
3 = pollutant record
4 = source comment
5 = emission point record
6 = emission point comment
7 = action record
8 = action comment
Masterfile
Record Type
Master file
Position
Master file
Length
* - Warning Error
Coding Considerations:
Card Type 1-8
Data Element Sheet
Revised 1/80
v-31
-------
COMMENTS
Definition:
COMMENTS can be used to place on the CDS masterfile data which
does not fit into any fixed card format.
Retrieval
Abbreviation
vara
Type 4, 6, 8
Card
Columns 21-79
Data Element
Length 59
Data
Type ALPHANUMERIC
Justified
Required
on New Entry NO
Nationally
Controlled NO
Valid Values:
All alphanumeric values.
Masterfile
Record Type 21. 35. 47
Masterfile
"Position 22-80
Masterfile
Length 59
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
Comments are not retrievable on a Quick Look Report; therefore, it is
better to use a fixed-format data element on Cards 1, 2, 5, or 7
whenever possible.
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 action information on compliance status
information; other card types are available for these purposes.
Card Type 4,6,8
Data Element Sheet
Revised 1/80
A-82
-------
LINE NUMBER
Definition: LINE NUMBER is used by the computer to distinguish one comment
line from another.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
4, 6, 8
20
1
NUMERIC
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
*** LINE NUMBER MUST
*** = Fatal Error
YES
YES
Valid Values:
0 through 9, A and B
Master file
Record Type 21, 35. 47
Master file
Position 21
Masterfile
Length 1
BE NUMERIC
* <* Warning Error
Coding Considerations:
Assign line numbers sequentially. Before assigning a line number, refer
to the source data report to be sure the number you code is not already
on the data 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 entering
mailing labels.
Card Type 4, 6, 8
Data Element Sheet
Revised 1/80
A- 83
-------
RECORD TYPE
Definition: RECORD TYPE is a two position numeric masterfile record identifier.
Retrieval
Abbreviation
Card
Card
Columns
Data Element
Length
Data
NUMERIC
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
Valid Values:
20 = Source
21 = Source comment
34 » Emission Point
35 = Point comment
46 = Action
47 - Action comment
Masterfile
Record
Masterfile
Position
20-47
19-20
Masterfile
Length
*** = Fatal Error
* — Warning Error
Coding Considerations:
Each Card Type has a corresponding masterfile Record Type.
Data Element Sheet
A-84
Revised 1/80
-------
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 N /A
Abbreviation
Card
Type 1-8
Card
Columns 80
Data Element
Length
Data
Twe A^HA
Justified
Required
on New Entry Ia&
Nationally
Controlled YES
Valid Values:
N - New
C » Change
D * Delete
Master file
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages: r „
*** 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 action.
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 success-
fully 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 transaction. By coding an asterisk anywhere in a data field,
that data field will be changed to spaces (date values will be zeroed out.)
Card Type l-S
Data Element Sheet
A-85
Revised 1/80
-------
CODING CONSIDERATIONS (Continued)
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 associ-
ated 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
associated 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 the data base against a mispunched delete update code.
A Card 2 or 3 delete is invalid.
Revised 1/80
A-35A
-------
APPENDIX B
CONTACT LIST
OF
CDS USERS
-------
Contact List of CDS Users
National CDS Data Bank Coord ma tor
Franklin Smith
202-755-0103 FTS 755-0103
Region I - Boston
Frank Ciavattier
Nancy Sidlik
617-223-5610
Region II - New York
Ken Eng
Jerry DeGaetano
212-264-4726
FTS 223-5610
FTS 264-4726
Reaion III - Philadelphia
Abe Ferdas
215-597-9401
Connie Carr
215-597-9387
FTS 597-9387
Region IV - Atlanta
Vince Hellwig
404-881-4253
FTS 285-5291
U.S. Environmental Protection Agency
Division of Stationary Source
Enforcement EN-341
401 M Street S.W.
Washington, D.C. 20460
Enforcement Division
U.S. Environmental Protection Agency
J.F.K. Federal Building
Boston, Massachusetts 02203
Planning and Management Divis ion
U.S. Environmental Protection Agency
26 Federal Plaza
New York, New York 10007
Enforcement Division
U.S. Environmental Protection Agency
Curtis Building
6th and Walnut
Philadelphia, Pennsylvania 19106
Enforcement Division
U.S. Environmental Protection Agency
345 Courtland St.
Atlanta, Georgia 30308
Region V - Chicago
Eric Cohen
312-353-2090
Region VI - Dallas
Bob Hannesschlager
Mary Kay Marusak
214-749-2755
FTS 353-8213
FTS 749-2755
Enforcement Division
U.S. Environmental Protection Agency
230 South Dearborn Street
Chicago, Illinois 60604
Enforcement Division
U.S. Environmental Protection Agency
1201 Elm St.
Dallas, Texas 75270
fe visd 12/79
B-l
-------
Region VII - Kansas City
Melinda Kreissler
816-374-5955
Enforcement Division
U,S. Environmental Protection Agency
324 East llth Street
Kansas City, Missouri 6410
Region VIII - Denver
RoxAnn Varzeas
303-837-2361
FTS 327-2361
Enforcement Division
U.S. Environmental Protection Agency
1860 Lincoln Street
Denver, Colorado 80203
Region IX - San Francisco
Chuck Seeley
Marian Lundholm
415-556-0970 FTS 556-0970
Enforcement Division
U.S. Environmental Protection Agency
215 Freemont Street
San Francisco, California 94111
Region X - Seattle
Betty Swan
Cecil Drotts
206-442-1387
FTS 399-1387
Enforcement Division
U.S. Environmental Protection Aqency
1200 6th Avenue
Seattle, Washington 98101
TRC - The Research Corporation
of New England
203-563-1431
125 Silas Deane Highway
Wethersfield, Connecticut 06109
Scott Shanks
Greg Fisher
Colleen Sullivan
Christine Neligon
Rita Reimer
B-2
Revised 1/80
-------
Contact List of CDS Users
at States
Arkansas
Robert Gage
501-371-1136
Arkansas Dept. of Polluction
Control and Ecology
8001 National Drive
Little Rock, Arkansas 72209
California
Gerald H. White
916-322-2895
Air Resources Board
1102 Q Street
P.O. Box 2815
Sacramento, California 95812
Georgia
Jim Mull ins
404-656-7410
Department of National Resources
4291 Memorial Drive, Suite M
Decatur* Georgia 30032
Louisiana
Atley Brasher
504-568-5129
Office of Health Services
Air Quality Section
P.O. Box 60603
New Orleans, Louisiana 70160
Mary!and
Doug Proctor
301-383-3245
Maryland BAQNC
201 West Preston Street
Baltimore, Maryland 21201
B-3
Revised 1/80
-------
Contact List of CDS Users
at States
Minnesota
John Morrill
612-296-7738
Minnesota Pollution Control Agency
1935 West County Road B-2
Roseville, Minnesota 55113
Missouri
Randall E. Raymond
314-751-3241
Missouri Dept. of Natural Resources
P.O. Box 1368
2010 Missouri Blvd.
Jefferson City, Missouri 65102
Nebraska
Dick Varner
402-471-2186
Division of Air Pollution
Department of Environmental Control
P.O. Box 94653, State House Station
Lincoln, Nebraska 68509
New Mexico
David Duran
505-827-5271 Ext. 356
Air Quality Section
P.O. Box 968
Santa Fe, New Mexico
87503
New York
Dick Joseph
212-482-6217
New York City Environmental Control
Board
120 Wall Street
New York, New York 10005
Ohio
Tomas E. Crepeau
614-466-6040
Ohio Environmental Protection Agency
Box 1049
361 East Broad Street
Columbus, Ohio 43216
Oregon
Ed Woods
503-229-6480
Oregon Dept. of Environmental Quality
P.O. Box 1760
Portland, Oregon 97209
South Carolina
Bob Betterton
803-758-5406
South Carolina Dept. of Health
2600 Bull Street
Columbia, South Carolina 29201
Tennessee
Stan Lodl
615-741-3931
B-4
Division of Air Pollution Control
301 Seventh Avenue
Nashvill, Tennessee 37219
Revised 1/80
-------
AEROS CONTACTS
II
III
IV
VI
vn
vni
IX
NEDS
!!r. John Courcier (A."1!.'!}
EPA, Region I
John F. Kennedy Bldg.
Boston, >!A 03203
(FTS) 223-4448
Mr. Mike Davis (F4T)
EPA, Region II
26 Federal Plaza
Hew York, HY 10007
(FTS) 264-9578
Dr. Sandor Kovacs (ASHH)
EPA, Region III (3AH11)
6th end Walnut Streets
Philadelphia, PA 1910S
(FTS) 597-8133
Mr. Barry Gilbert (ASHM)
EPA, Region IV
345 Courtland Street, M.E.
Atlanta, GA 30308
(FTS) 257-2854
?ir. Barry Bolka (S4A)
EPA, Region V
230 S. Dearborn, 26th FT.
Chicago. IL 60604
(FTS) 353-2303
Mr. Tim Hatzke (S1A)
EPA, Region VI
1201 Elra Street
Dallas, TX 75270
(FTS) 729-2724
Mr. Seynour Shuster (AiHM)
EPA, Region VII
1735 Baltimore Avenue
Kansas City, MO 64103
(FTS) 758-3791
Kr. Oave Lewis (SJA)
EPA, Region VIII
1860 Lincoln. Street
Denver, Colorado 80295
(FTS) 327-2226
Kr. Shun Obinata (Hgat)
EPA, Region IX
215 Fremont Street
San Francisco, CA 94105
(FTS) 556-2326
Hs. Shirley Towns (SiA)
EPA, Region X
1200 6th Avenue O'./S 345)
Seattle, UA 93101
(FTS) 399-1]OS
SAROAD
Kr. tioraan 0. Beloin (SIA)
EPA, Region I
60 Uestvi&w Street
Lexington. (tA 02173
(617) 861-6700
Mr. Ed Finfer (Air Branch)
EPA, Region II
26 Federal Plaza
New York, NY 10007
(FTS) 254-9300
Dr. Sandor Kovacs (ASHH)
EPA, Region III (-3AH11)
6th and Walnut Streets
Philadelphia, PA 1910S
(FTS) 597-8133
Mr. William Snider (A4HM)
EPA, Region IV
345 Courtland Street, tl.E.
Atlanta, GA 30308
(FTS) 257-2864
Kr. Steve Goranson (S&A)
EPA. Region V
230 S. Dearborn. 26th FT.
Chicago, IL 60604
JFTS) 353-2303
Mr. Tin ftatzfce (S&A)
EPA, Region VI
1201 Elm Street
Dallas, TX 75270
(FTS) 729-2724
Mr. Seymour Shuster (A&KH)
EPA, Region VII
1735 Baltimore Avenue
Kansas City, KO 64108
(FTS) 753-3791
Hr. Dave Lewis (S&A)
EPA, Region VIII
1850 Lincoln Street
Denver, Colorado 80295
(FTS) 327-2226
Kr. Shun Obinata (Kgnt)
EPA, Region IX
215 Fremont Street
San Francisco, CA 941Q5
(FTS) 536-2326
Ms. Shirley Towns (SSA)
EPA, Region X*
1200 6th Avenue (tl/S 345)
Seattle,, 1IA 98101
(FTS) 399-1106
OTHEB CONTACTS
Kr. HMlisarSerovy (I'.got)
EPA, Region I
john F. Kennedy Bldg.
Room 2207-B
Boston. IM. 02203
(FTS) 223-588S
Kr, Ted Standlsh (Karat)
EPA. Region III
6th 2nd Walnut Streets
Philadelphia, PA 19106
(FTS) 597-8045
Hs, Kathryn Kamallck (SARO;
Kr. Urry Lehrman (NEDS) (!
EPA, Region V
230 S. Dearborn, 26th Fl.
Chicago, IL 60505
(FTS) 36J-2303
Hs. Ginger Siailey (Kgmt)
EPA. Region VI
1201 Elo Street
Dallas, TX 75270
(FTS) 72J-2S4J
Hr. Ton Entznringer (SSA)
EPA'. Rejion VIII
1860 Lincoln Street
Denver. Colorado 80295
(FTS) 327-2225
Hs. Caroline Ireson (S4A)
EPA. Region IX
215 Freaoat Street
San Francisco, CA 94105
(FTS) 556-2270
-------
Regional
Tficc
II
in
IV
VI
VH
VIII
Mr. Killiaai Serovy (Kgnt)
EPA, Region I
John F. Kennedy Cldg.
Rooa 2207-B
Boston, KA 02203
(FTS) 223-5885
Kr. Lew Hecicnan .(Mr Branch)
EPA, Region II
26 Federal Plaza
Kew York, HY 10007
(FTS) 264-9300
Dr. Sandor Kovacs (A4KM)
EPA. Region III (3AHH)
6th and Walnut Streets
Philadelphia.^ 1910S
(FTS) 597-8133
Mr. Barry Gilbert (AiKa)
EPA, Region IV
345 Couptland Strset, M.E.
Atlanta, GA 33303
(FTS) 257-2864
Kr. Steve Coranson (SSA)
EPA, Region V •
230 S. Dearborn, 2gth Fl.
Chicago, IL 60604.
(FTS) 353-2303
Kr. Dave White
EPA, Region VI
1201 Elm Street
Dallas, TX 75270
(FTS) 749-3761
Kr. Seymour Shuster (ASH.'l)
EPA. Region VII
1735 Baltimore Avenu»
Kansas City. KO 64103
(FTS) 7S3-379T
Kr. Dave Lewis (SSA)
EPA, Region VIII
1860 Lincoln Street
Denver, CO 80235
(FTS) 327-2225
Ks. Caroline Ireson (SSA)
EPA, Region U
215 Freaont Street
San Francisco. CA 94105-
(FTS) 556-2270
Ks. Shirley Towns (SM)
EPA. Region X
1200 6th Avenue (M/S 345)
Seattle. WA 93101
(FTS) 399-1105
CDHS CONTACTS
AQOHS-II
Kr. Ed Finfer (Air Branch)
EPA, Region 1J
26 Federal Plaza
Hew York, NY 10007
(FTS) 264-9800
Kr. William Snider (AJH.M)
EPA, Region IV
34S Court!and Street, f/.E.
Atlanta, GA 30308
(FTS) 257-2864
Kr. Steve Coranson (S4A)
EPA, Region V
230 S. Dearborn, 26th FI.
Chicago, IL 60604-
(FTS) 353-2303
Ks.- Ginger Sniley (Host)
EPA, Region VI
1201 Elm .Street
Dallas, TX 75270
(FTS) 749-3761
Kr. Shun Obinata (Kent)
EPA, Region IX
215 Frenont Street
San Francisco, CA 94105
(FTS) 556-2325
Kr. Kike Davis (FST)
EPA, Region II
26 Federal Plaza
Kew York, NY 10007
(FTS) 264-9578
Mr. Barry Gilbert (AWIH)
EPA, ?.egion IV
345 Courtland Street, N.
Atlanta. GA 30303
{FTS) 257-2864
Kr. Bsrry Bolka (SiA)
EPA, Region V
230 S. Dearborn, 26th F7.
Chicago. IL 60S04
(FTS) 353-2303
Ks. Ginger Sniley (llgnt)
EPA, Region VI
1201 Elm Street
Dallas. TX 75270
(FTS) 749-3751
Kr. Shun Cbinata (Kgat)
EPA, Region IX
215 Frecont Street
San Francisco, CA 941C5
(FTS) 556-2326
-------
TECHNICAL REPORT DATA
(Please read Instructions on the reverse before completing)
1. REPORT NO,
EPA 340/1-78-003
3. RECIPIENT'S ACCESSION NO.
4. TITLE AND SUBTITLE
Compliance Data System User's Guide
5. REPORT DATE
December 1979
6. PERFORMING ORGANIZATION CODE
7. AUTHOR(S)
Mr. Geza Serenyi
8. PERFORMING ORGANIZATION REPORT NO.
3. PERFORMING ORGANIZATION NAME AND ADDRESS
The Research Corporation of New England
125 Silas Deane Highway
Wethersfield, CT 06109
10. PROGRAM ELEMENT NO.
11. CONTRACT/GRANT NO.
68-01-4145
12. SPONSORING AGENCY NAME AND ADDRESS
Division of Stationary Source Enforcement
Office of Enforcement
U.S. Environmental Protection Agency
Washington, D.C. 20460
13. TYPE OF REPORT AND PERIOD COVERED
14. SPONSORING AGENCY CODE
!5. SUPPLEMENTARY NOTES
A user's guide describing the general operation of and specific procedures to be
utilized by operators of the Compliance Data System.
lo. ABSTRACT
This Compliance Data System (CDS) User's Guide is designed to be the primary source
of user documentation regarding CDS. It replaces all documentation dated prior
to March 1978, which should be discarded.
The guide 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 and 3,
Management Overview and System Applications. Current Users who generally understand
CDS will wish to skip to specific sections of interest, particularly Sections 7 and 9,
Edit Processing and Retrieval Processing, which reflect recent changes. New Users
may wish to read the text in its entirety, at least through Section 9 to obtain a
working knowledge of CDS. Those Preparing Input Data should read Section 6, Data In-
put Preparation.
17.
KEY WORDS AND DOCUMENT ANALYSIS
DESCRIPTORS
b.IDENTIFIERS/OPEN ENDED TERMS
c. COSATI Field/Group
Air Pollution Facilities (Sources)
Compliance Status
Enforcement Actions
Surveillance Actions
13 B
18. DISTRIBUTION STATEMENT
Release Unlimited
19. SECURITY CLASS (ThisReport)
Unclassified
21. NO. OF PAGES
301
20. SECURITY CLASS /This page)
Unclassified
22. PRICE
EPA Form 2220-1 (R«v. 4-77) PREVIOUS EDITION is OBSOLETE
*US. GOVERNMENT PRINTING OFFICE: 1980 311-132/12 1-3
------- |