EPfi 34O/1-76-O11
REVISED mflY 1977
Stationary Source Enforcement Series
U.S. ENVIRONfTlENTflL PROTECTION flGENCY
Office of Enforcement
Office of General Enforcement
Washington, D.C 2O46O
-------
COMPLIANCE DATA SYSTEM
USER'S GUIDE
This report was furnished to the Environmental protection
Agency by TRC - THE RESEARCH CORPORATION ol_New" England
in partial fulfillment of Contract #68-01-4145 The con-
tents of this report are reproduced herein as received
from the contractor. The opinions, findings, and conclu-
sions expressed are those of the author and not necessarily
those of the Environmental Protection Agency.
May 1977
TRC Project #82752
Contract #68-01-4145
REVISED May 1977
-------
The Stationary Source Enforcement Series of reports 1s
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 A1r 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.
-------
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:
-------
TABLE OF CONTENTS
SECTION PAGE
1.0 INTRODUCTION 1-1
2.0 MANAGEMENT OVERVIEW 2-1
2.1 Background History 2-1
2.2 System Purposes 2-2
2.3 System Capabilities 2-3
2.4 System Functions 2-4
2.5 System Relationship to Other EPA Systems .... 2-5
3.0 SYSTEM APPLICATIONS 3-1
3.1 General Applications 3-1
3.2 Examples of Specific Applications 3-2
4.0 SYSTEM OVERVIEW 4-1
4.1 Edit Program 4-2
4.1.1 Input Data Processed by CDS 4-3
4.1.2 Edits Performed by CDS 4-3
4.1.3 Edit Error Messages 4-5
4.1.4 CDS MOD File 4-7
4.2 Update Program 4-8
4.2.1 Update Actions to CDS 4-9
4.2.2 Update Cycle Steps 4-9
4.2.3 Update Report Messages 4-9
4.2.4 The CDS Masterfile 4-11
4.2.5 Regional CDS Masterfile 4-12
4.3 Retrieval Program 4-12
4.3.1 Description of Reports Available from
Retrieval Program 4-14
4.3.2 Retrieval Steps 4-17
5.0 DATA SUBMISSION PROCEDURES 5-1
5.1 Submission Steps 5-1
6.0 DATA INPUT PREPARATION 6-1
6.1 General 6-1
6.2 Adding New Records to the CDS Masterfile .... 6-5
6.2.1 Sample of a Completed Coding Sheet for a
New Facility 6-11
6.3 Changing Data on the CDS Masterfile 6-14
6.3.1 Sample Completed Coding Sheet for Change
Transactions 6-16
6.4 Deleting Data from the CDS Masterfile 6-17
6.4.1 Sample Completed Coding Sheet for Delete
Transactions 6-19
6.5 Keypunch Instructions 6-20
-------
TABLE OF CONTENTS (Cont.)
SECTION
7.0
7.1
7.2
7.3
7.4
7.1.1
8.0
8.1
8.2
8.3
8.4
8.5
8.6
9.0
9.1
9.1.1
9.1.2
9.1.3
9.1.4
9.1.5
9.1.6
9.1.7
9.2
9.3
9.3.1
9.3.2
9.3.3
9.3.4
9.3.5
9.4
9.5
10.0
10.]
10.1.1
10.1.2
10.1.3
10.1.4
10
10
10.2
10
1.5
1.6
.2.1
10.2.2
EDIT PROCESSING
Edit Program Usage
Warning and Fatal Errors .
Edit Error Messages ....
Sample CDS Edit Report .
Edit Job Control Language (JCL)
UPDATE PROCESSING
Update Program Description .
Update Report
Update Report Messages ....
Update Scheduling
Update Status Log
Update Report Job Control Language
RETRIEVAL PROCESSING
Reports Available from the Retrieval
Quick Look Report
Double Spaced Quick Look Report
Source Data Report
Milestone Report
Questionnaire Report ...
Action Summary Report
Compliance-Action Report
Check List for Request Submission
Preparing Retrieval Selection Cards
Special Considerations for Pollutant
Compliance Retrievals
Pollutant Compliance Logic Selection .
Pollutant Compliance Sorting
Printing Pollutant Compliance Data
Sample of a Filled in Retrieval Request .
Job Control Language for Using Retrieval Program.
Retrieval Edits Performed by System
SUPPORTIVE TECHNICAL INFORMATION. . .
Table Processing
County Code Table
Personnel Code Table
Action Table
Results Code Table
Other Table Lookup Procedures
CDS Masterfile Layout
Backup and Recovery Procedures.
User Responsibility for Backup .
National Responsibility for Backup.
PAGE
7-1
7-1
7-2
7-2
7-5
7-7
8-1
8-1
8-3
8-4
8-8
8-9
8-11
9-1
9-2
9-3
9-5
9-8
9-10
9-12
9-14
9-14
9-16
9-18
9-28
9-29
9-30
9-31
9-32
9-37
9-37
10-1
10-1
10-1
10-4
10-7
10-9
10-11
10-11
10-12
10-12
10-12
11
-------
TABLE OF CONTENTS (Cont.)
SECTION
10.2.3
10.3
11.0
11.1
11.2
11.3
11.3.1
11.3.2
11.3.3
11.3.4
APPENDIX
A
B
PAGE
Recovery Procedures 10-13
Computer Program Modification 10-13
NATIONAL GUIDANCE MATERIAL 11-1
CDS Input Preparation via WYLBUR 11-2
Form Reporting 11-8
CDS Coding Guidance 11-11
Coding Card 3 11-15
Coding Related to Continuous Monitoring . . 11-19
Coding Related to New Source Review
and PSD 11-21
Coding Instructions for Power Plants
and Industrial Boilers 11-26
CDS DATA ELEMENT DESCRIPTION A-l
CONTACT LIST OF CDS USERS B-l
m
-------
LIST OF FIGURES
FIGURE PAGE
4-1 Edit Program Flow Chart 4-6
4-2 Update Flow Chart 4-10
4-3 Masterfile Hierarchy 4-13
4-4 Retrieval Flow Chart 4-18
6-1 CDS Input Card Layouts 6-2
6-2 Sample Coding Sheet 6-4
6-3 Sample of Completed Coding Sheet for a .... 6-12
New Facility
6-4 Sample 6f Completed Coding Sheet for 6-18
Change Transaction
6-5 Sample of Completed Coding Sheet for 6-21
Delete Transactions
7-1 CDS Edit Report 7-6
7-2 CDS Edit Job Control 7-9
7-3 Using the Edit's Dummy Option 7-10
7-4 Input From Tape 7-11
7-5 Saving the Reject File 7-12
7-6 Printing the Reject File 7-13
7-7 Input to CDS Via Wylbur 7-14
8-1 Update Report 8-5
8-2 CDS Update Log 8-10
8-3 CDS Update Report Job Control 8-12
9-1 Sample Quick Look Report 9-6
9-1A Sample Quick Look Report with Data Suppression . 9-6A
9-2 Sample Double Spaced Quick Look Report .... 9-7
9-3 Sample Source Data Report 9-9
9-4 Sample Standard Milestone Report 9-11
iv
-------
LIST OF FIGURES (Cont.)
FIGURE PAGE
9-4A Sample Variable Milstone Report 9-11A
9-5 Sample Questionnaire 9-13
9-6 Sample Action Summary Report 9-15
9-6A Sample Compliance-Action Report 9-15A
9-7 Retrieval Request Form 9-19
9-8 Sample Quick Look Request 9-33
9-8A Sample Quick Look Request 9-33A
9-9 Sample Standard Milestone Request 9-34
9-9A Sample Standard Milsetone Request 9-34
9-10 Sample Questionnaire Request 9-35
9-11 Sample Action Summary Request 9-36
9-12 Retrieval Job Control 9-38
9-13 Retrieval Edit Report 9-43
10-1 County Code Table 10-3
10-2 Sample Personnel Table 10-6
10-3 Sample Action Table 10-8
10-4 Sample Results Code Table 10-10
10-5 CDS Masterfile Layout 10-11A
11-1 Collecting Retrieval Test 11-5
11-2 Preparing Load & Go 11-6
11-3 Using Retrieval Output for Load & Go 11-7
11-4 Job Control for CDS/FRS Link 11-10
H-5 Action Type for PSD and NSR 11-24
H-6 Sources Subject to PSD Requirements 11-25
-------
LIST OF TABLES
TABLE PAGE
6-1 Kaypuch Instructions 6-22
6-2 Keypunch Instructions for Card Type 1 6-23
6-3 Keypunch Instructions for Card Type 2 6-24
6-3A Keypunch Instructions for Gary Type 3 6-25
6-4 Keypunch Instructions for Card Type 5 6-26
6-5 Keypunch Instructions for Card Type 7 6-27
6-6 Keypunch Instructions for Card Types 4, 6, and 8 . 6-28
7-1 Edit Error Messages 7-3
8-1 Update Error Messages 8-6
9-1 Retrieval Package Edits 9-39
9-2 Retrieval Package Error Messages 9-41
11-1 Card 3 Format 11-18
11-2 Source Classification Codes (Partial list) . . . 11-29
vi
-------
1.0 INTRODUCTION
This Compliance Data System (CDS) Users' 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 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 Input
Preparation.
From time to time, revisions to the Users' Manual will be issued.
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.
1-1
-------
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 enables 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
2-1
-------
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 four years. Experience with
the system has led to modifications and refinements of CDS which are
described in detail in this documentation. During the three years of
regular production runs, CDS has grown into a system widely used by all
ten regions.
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 quantitites of parametric
emission data; instead, it is a management information system for tracking
compliance and enforcement information in an easily-accessible manner. In
effect, CDS is an automated tickler file which provides both historical
and current record keeping capabilities.
2-2
-------
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 forma_ts_are used to enter data intp^DS
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 one flexible format report 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
2-3
-------
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 (DBC)
to run once a week on Wednesday nights. 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 transaction's Update Code. The Update produces an Update Report
to show what action it took on each transaction. Because of computer
hardware limitations, the Update cannot automatically send each regional
user's Update Report to the appropriate computer terminal. After each
update cycle for which the user had input data, the user must request his
own 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
2-5
-------
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.
2-6
-------
3.0 SYSTEM APPLICATIONS
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.
3-1
-------
6. Anticipate future enforcement requirements. CDS has a great
deal of built-in flexibility, and also it 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
can be developed on any user-selected criteria.
o CDS can identify sources inspected by regional and/or state
personnel in both attainment and non-attainment AQCR's.
o 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.
o 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.
o CDS can be used to prepare milestone reports and lists of facil-
ities subject to SIP regulations, NSPS regulations and NESHAPS
regulations.
o CDS can be used to prepare industry studies or summaries based
on the Standard Industrial Class Code (SIC) on the Standard
Classification Code (SCC) for certain processes.
3-2
-------
The types of reports that CDS can generate in aiding management
in its enforcement activities is 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.
3-3
-------
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.
3-4
-------
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.
Activities which must be tracked include the issuance of Section 114
letters, the issuance of notices of violations, the follow-up of enforce-
ment orders, and the performance of source tests and conduct of periodic
inspection. CDS can assist Program Managers in assuring that these
activities are being carried out in an orderly, effective manner. For
example, if he wants to know the workload facing his staff during a
coming month, the Program Manager can obtain a CDS report on all EPA
actions scheduled during the month. This could be a listing of all
Section 114 responses, the number of scheduled conferences, the number
of inspections due, the persons responsible for these inspections, and
any other scheduled actions which have been input to the system. With
this information he can readily see what manpower requirements are
already committed for the month and can plan other activities accordingly.
3-5
-------
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.
-------
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-2
-------
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 seven 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.
4-3
-------
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 DBC 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 its limitations. The Edit
cannot detect valid but incorrect Update Codes; only the Update Program
can determine whether it is possible to add, change, or delete a record
on the CDS 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.
4-4
-------
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 Pile 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 seven 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
4-5
-------
FIGURE 4-1
EDIT PROGRAM FLOW CHART
INFORMATION
FROM FEDERAL,
STATE & LOCAL
AGENCIES
\f
\CODING AND
\ KEY-
PUNCHING
r
INPUT DATA
CARD TYPES
1-8
EDIT
PROGRAM
(
V
EDIT
MOD
FILE
TO
NATIONAL
DBC
TO
UPDATE
CYCLE
EDIT
REPORT
TO
REGIONAL
USER
ALL TABLES ARE
MAINTAINED BY THE
NATIONAL DBC
CDS
PERSONNEL
TABLE
CDS
ISAM
TABLE
COUNTY
CODE/AQCR
TABLE
ERRORS
(DUMMY)
CAN BE
PRINTED
OR SAVED
BY USER
4-6
-------
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
4-7
-------
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 perform 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-8
-------
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 two column headings, Update Action
and Error Message, which indicate what action has been taken by the
Update Program on each transaction passed by the Edit. A normal Update
4-9
-------
FIGURE 4-2
UPDATE FLOW CHART
THIS
CYCLE'S
OUTPUT
MASTERFILE
BECOMES
NEXT
CYCLE'S
INPUT
MASTERFILE.
L _
BACKUP OF
MOD FILE
COPY OF
MOD FIL
OLD
MASTER
FILE
SORTED
MOD FILE
PERSONNEL
FILE
UPDATE
PROGRAM
10 REGIONAL
UPDATE
REPORT
FILES
NEW
MASTER
FILE
COPY
MASTER TO
DISK
PRINT
REGIONAL
REPORT
/
I REGIONAL
I DISK
WASTERFILES
UPDATE
REPORT
ON USER
REQUEST
4-10
-------
Action Message is 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.
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
CDS. Over 34,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 six Masterfile record formats. These Masterfile record formats are
numbered 20, 21, 34, 35, 46, 47 for internal computer identification purposes.
The six 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.
4-11
-------
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.
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
4-12
-------
Region, Scace, County,
and Source Number
Provide a Unique
Facility Identifier
1
&l
Record 21
CoSSISt 0
1
2.
Up to 10 Conaents
Per Source
Up to 12100 points
per facility
Pouil 000 contains
compliance Data
for the Entire Facility
Up to 10 comments
per point
Actions for
point 000 refer
to action for the
FIGURE 4-3
MASTERFILE HIERARCHY
-------
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
4.3.1 Description of Reports Available from Retrieval Program
The retrieval capabilities of CDS are designed for maximum flexibility
so that the user may design the output format to fit his own particular
need. In addition, the amount of information retrieved for each source
is also 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 whereas the Source Data Report is designed to print all
data elements for selected sources. 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
4-14
-------
facilities should appear on a report, but also they can select the data ele-
ments to be printed for these selected sources. Up to ten 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.
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
4-15
-------
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
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.
This report provides a tally of the compliance status code of selected
emission points 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.
4-16
-------
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
Because this report has been designed to meet specific enforcement
action reporting requirements, all reportable totals are generated at
the end of the report.
4.3.2 Retrieval Steps
Each time a user requests a management report via the Retrieval,
the following steps are taken by the various computer programs 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.
4-17
-------
RETRIEVAL
LOG
FIGURE 4-4
RETRIEVAL FLOW CHART
(REGIONAL
CDS
MASTERFILE
RETRIEVAL
PROGRAM
EXTRACT
FILE
SORT
PROGRAM
SORTED
EXTRACT
FILE
PRINT
PROGRAM
RETRIEVAL
OUTPUT
REPORT
USER
SELECTION
CARDS
RETRIEVAL
EDIT
REPORT
4-18
-------
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
= 4). 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.
5-1
-------
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.
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 cycle is scheduled, the
national Data Bank Coordinator will inform all CDS users of
the schedule change.
6. Verify Update Run. On Thursday morning, the user 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.A026.EPAEXC.CDS.
SYSOUT. This data set shows the 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 trans-
actions accepted and rejected by the update for each Region.
5-2
-------
7. Obtain the Update Report. If the user had data which was entered
into the update cycle, 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.
8. 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.
9. 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
recoded. Corrections should be resubmitted to CDS via the Edit
Program.
10. Request Management Reports. CDS can produce the following manage-
ment reports:
o Quick Look Report
o Milestone Report
o Source Data Report
o Questionnaire
o Action Summary Report
The user should consult Section 9 for the procedures to obtain the
above reports.
5-3
-------
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 seven 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 COMNET 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
Active/Passive Code 65
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.
6-1
-------
Company
Application
CDS INPUT LAYOUT
MULTIPLE-CARD LAYOUT FORM
TRC Dote MARCH 1976 Job No
Sheet No
1 2
0)
4-1
cd
4J
co
3 4
S 6 7 8
0)
u
rl
o
CO
9 10 II 12 13
•S
o
PH
14 IS 16
17 18 19
Pi
U
Cf
2021 22
>, 01
4J -O
•H O
CJ CJ
23 24 25 26
Source Name
Street Address
27 28 29 30 31 32 33 34 35 36 37 38 39 « 41 42 43 44 45 46 47 48 49 SO 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66
MO
RDE 4
70 71 72 73 74
RDE 5
75 76 77 76 7! 80
CM
(J
C
v
0
a
cd
i I
CO
3 4
S 6 7 8
01
u
rl
O
CO
9 10 II 12 13
=S=
4J
C
•rl
O
14 15 16
City Name
I 18
20 21 72 23 24 25 26 27 28 29 30 31 32 33 34
01
T3
O
U
O.
•H
N
State Registration
Number
15 36 37 38 39 « 41 42 43 44 45 46 47 48 49 50 51 52 S3 W
1
iS 56 57 58
CJ
H
CO
» 60 61 62
Nw
M
6&
P. P.
RDE 6
» 67 68 69 70 71 72 73 74 75 78
CO
77 78 7! 80
C
O
•H
00
£
I 2
01
4-1
cd
4J
CO
3 4
4-1
5
C
CJ
5678
0)
U
t-i
C
CO
9 10 II 12 13
c
PH
4 IS 16
7 18 19
Pi
Pollutant 1
siy
g;
o
OH
r J
CPn
24
^
00 4-1
C td
•H 0
» 30 31 32 :
4J Pollutant 2
G _
iT-=-S
s
cd
cja<
X14
00 4J
c cd
•H O
•a -H
4-i td *o
rH O C
PH ,J H
I ii 43 44 45
4J Pollutant 3
1647
S J
ua«
5051
PnPM
00 JJ
•H O
•C -rl
33
t 55 56 57
4J 4-1
1-1 -rl
rH O
•H Cd
U (X
CO cd
pn CJ
A 59 60 61 62 63 64
[d
.5 66 67 68 69 70 71
&
72 73
W
to
n 78;
80
U1
1 2
01
u
cd
CO
3 4
e
o
S 6 J 8
0)
u
o
CO
9 10 11 12 13
=«=
•S
O
PH
14 IS 16
7 11 19
SCC Code
20 21 22 23 24 25 26 27
2829
f. X
S. H
30 31
3233
Federal/State/Local
Regulation Number
34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
Process Description
SO SI 52 S3 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74
757677
Si Si TJ
7 80
C
C
"o
0)
Pi
1 2
O
O
01
U
IH
O
CO
10 II 12 13
O
PH
4 15 16
7 1! 19
Optional
Short Action
Description
2021
I 26 29 I
3233 :
Filler
35 36 37 38 39 «fl 41 42 43 44 45 46 47 48 49 SO 51 K
4J
S3 54
Date
Achiev-
ed
55 56 57 58 53 60
Date
Sched-
uled
>l 62 63 64 65 66
14-1
14-1
Cd
4J
CO
57 6863
70 71
1
72 n
Filler
74 75 76 77 71 7! 80
c
1 2
3 4
O
CJ
9678
01
u
o
CO
9 10 11 12 13
4-1
.S
o
PH
14 IS IE
7 II IS
Comments
il 22 23 24 25 X 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80
FIGURE w-
-------
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
Card Code 4
* Comment Line Number
Source Comments
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 Column
20
21-79
Card Code 5
SCC Code
* NEDS Cross Reference
* Compliance Status
* SIP Code
* Pollutant
State Regulation Number
* Emission Category
Process Description
Multiple Cross Reference
Regional Data Element 7
Card Code 6
* Comment Line Number
Point Comments
Card Code 7
* 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
Card Column
21-79
Card Column
53-54
55-6Cf
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.
6-3
-------
L_
i! , =.•;..-.= :
-.
.
' •-••: •"'-'• TV
• : 1 .
o!o
0
0
0
0
0
00
0
0
0
o
o
0
0
0
0)0
o
0
0
0|0|0
"•:-'
-"./.'-• '.""-'
EM
.-:);
ss;
•, -
en
0
0
0
0
0
0
0
0
0
0
ojo
i
2
3
4
4
D
5
5
5
o
6
f
7
7
8
•f^a :;j>:r;:'
"<
;:':(-9 •
!i;
ii
li
i i
t:'!? CDL'E
;.. :
i:j
'/.(
COMPLIANCE DATA SYSTEM CODING SHEET
_ '. ._ . iu^cz :*•;:
,''"
"^
M
?,'•
53
cnv ;;A'!E
; :
--.-
|-
te
'
NJ
•-- it.
J
/
.".
''^
i .
LLU
^
f:
-
f
dii
Jl;
Jl
jd
JJ
: i
LOAD Hi"
J-
;R:r
ih
W
Lor,Qir:G
;-.H
'i1?1
W
~
~
SIC
"-Q
•SO
f, 1
f.?
T71
-' •.
V\N
t""'
V^
(,*;
- FACILITV CAPACITY
61
7T"
t
tf
~
' i
y.-
SEE 5
pT'
l^jV' ROE 6
f-'i
ft*
(,;
hf-,
ftC
7(1
M
KDE 9
T>
/ -i
//;
;.;
?y ..i^-.
T
7,;
1 ^7A! f
7 -
I'v1
^f
7M7-
sV
'••'•'-• "°- • SOURCE CGKHEKTS
•-.1C CCDE
f
•f
riEOX.F
Cf"
•!
PLJT
jj
i
U
STATE REGULATION
T
J'
O i
li:
•^ PROCESS DESCRIPTION
^1
^
bi
'—
— ~
D*
—-
~
—
bJ
~
ai
fcK
~
^
/ .5
/>:
/h
HUI.T
XHCF
~
Vn
<&
f4
-'^
-i±
-" i"-™. - E-'SSffiiPO^TCffiME'TS '
U
Oi'TiOIiAl. ACT G" DESCRIPTION
USED WITH ATPE 00
1
_LJ
__
^
^
\\
x:
X
\\
^
51
\x
0
[^^^w$33^
v
v|:
.>
r^^i^Ki
S
/b
^
b
v^\jsA/V\KM\\
kq<,vvKNXKlxXJ
C!
1:1.
/ ti
-^=L
-
ii
^^
—
-„£_
\
A
H|
V
,.s^
^v
^_
V
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 seven 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. To establish a new facility on the Masterfile, perform
the following steps:
6-5
-------
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 to the Master-
file. Card 2 can be entered with an Update Code N only when it is being
entered at the same time as a new Card 1. 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 at the same time 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.
6-6
-------
Card Type 3 is used to add or change pollutant compliance data on the
CDS Masterfile. In order to support the FY 78 program plan requirements
to develop adequate SIP's for TSP, S02, HC, CO, and NO in non-attainment
air quality control areas, the CDS system must carry a number of new 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 have been added to CDS:
Data Field
Pollutant ID
Pollutant Compliance
Coding Considerations
Must be coded for each pollutant
produced by the facility. Valid
values are the same as for PLUT.
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 CMST.
6-7
-------
Data Field
Length Coding Considerations
Pollutant Emission Category
Air Quality Maintenance
Indicator
Must be coded for each applicable
pollutant. Valid values are the
same as for ECAT. This field
must represent the potential un-
controlled emissions for the
pollutant.
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.
Impacted AQCR Indicator
Pollutant Loading
Must be coded as follows:
a. Leave blank if the facility
does not contribute to the
non-attainment status of the
AQCR for this pollutant.
b. Code 'Nf if the facility
impacts the emission standards
for this pollutant in a non-
attainment AQCR.
c. Code 'N1 if the impact of
this pollutant on the non-
attainment status of the AQCR
is unknown.
May be coded. If it is used, it
must be a numeric field representing
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 'C1 for adding,
changing, or deleting pollutant data. Because a facility can produce
numerous pollutants, the input punch card has room for three sets of
6-7 A
-------
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; FT, S02,
HC, CO, and N0x 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-RDE12 are not repeating data elements. Only one value for each of
these data elements can be stored on the CDS Masterfile at one time. If
several Facility Capacities are coded on multiple Card 3's for a facility
6-7B
-------
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.
Card Type 5 is used to add emission point data for each pollutant
emitted by a facility. For each facility, there can be up to 1,000
emission points. Point 000 contains compliance status and emission cate-
gory information 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. If point 000 is not added with a new
6-8
-------
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 starting with
001. 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.
When adding new additional point numbers for a facility, request
a Source Data Report for that 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 should
also be entered at this time.
Card Type ^ 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 Masterfile unless a corre-
sponding emission point already exists on the Masterfile.
6-9
-------
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
should assign a two-position Action Type corresponding to each action.
The central 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 sequentially
starting with 01. When adding only one new action number to
the Masterfile, Action Number 99 could be coded into columns
17-18. The system will convert 99 to the next highest sequen-
tial action number for that emission point. When several
actions are added for a given point, a Source Data Report for
that facility must be requested to determine which action numbers
already exist on the Masterfile.
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.
6-10
-------
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.
6-11
-------
I'OJ:ITY
If; !i 12 M
000 I
csir
COMPLIANCE DATA SYSTEM CODING SHEET
SUUKCf KA!1C
STREET ADDRESS
f'4|b5 _66_ fj_ bS_ 69. 20. V]_ 72173 /4|7ii| 76
0
0
0
0
ZIP
STATE REGIi'THATIOf!
-ij'"'. I ^Zl^ll44 liSJ-'loi 47 U3 14915015115215315';
5H 59 SO f: I fi? fi.'J (••'•• fv; bT
NEDS XREf
S!C
;': 'il ?2 ?j ?i Z1; ;6 2.' ??. 29 3C 31 32 ^
55 56 5/ 58
•^9 60
ojo[o[o|ol2|/<|gUUIgULpUUk
POLLUTANT i
KOLLJIAIi 2'
LOAD ICG
LOADING
•ULLUTAM 3
A -j^ ,&
LOADING
FACiLIT.V CAPACITY
ROE 9
<"9 5!) 51 52 55I54I55I 561 57
p" 59 bO 61 6? 63 ^'1
p5it? 67 68 69 70 ^•
00000
>*
SCUKCE COKMZ'ITS
0
OjOjOjOlO
C.CC CODE
STATE SEGULATIOI!
PROCESS CESr.RIM!CM
MULT
39
't-
53
flfl.
/U
>\L
ojo
• \o
< Tit
00
4te
V
0|0
f!eltj7J6«|fc9| 71) I? l
7« 1 75 I 76 I 7/
^u
0
s/
HI 15
I I IN i I I I 1 M I i I I II I I I I I I II I I I I I I I I I I I I I i II I I i I I M I I I I I I I I
OPTIONAL. ACT!0:i DESCRIPTIOfi
USED WITH ATPE fi'J
ACTION - RESULTS
TYPE DATE ACHIEVED DATE SCiiEDULC!) STA'T RI)f.
QJi.
Jli
/4 / L
7l M I I I I I I I M I I I
8
FIGURE 6-3
SAMPLE OF COMPLETED CODING SHEET FOR A NEW FACILITY
-------
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 001 since the Compliance Status and the SIP Codes of
the entire source represent the weakest compliance status of any of the
other emission points.
In this example, emission points 002 and 003 represent two different
regulated pollutants being emitted from the same smokestack. The 002 in
the Multiple Cross-reference field (columns 75-76) for emission point 003
indicates that emission point 003 represents another regulated pollutant
for the same process described in emission point 002.
Actions are entered at this time with a date scheduled but no date
achieved since they represent actions to be performed in the future.
6-13
-------
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.
All change transactions must have a "C" in the Update code column 80.
The Edit program no longer accepts the Update Code "R" which was previously
used. In addition, no automatic record generation will be performed by
using the Update Code C with a Card 7.
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.
6-U
-------
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.
6-15
-------
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.
6-16
-------
Since point 002 did not have any comments associated with it, comment
1 for point 002 is entered as new.
Action 01 for point 001 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 002 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.
1. 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; in order to reduce the possibility of keypunch
errors, no data may be coded in these columns. Before sub-
mitting 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. Deleting an Emission Point, Card 5. Fill in columns 1-19 and
place a D" in column 80. Do not fill in columns 21-79; no
data is to be added to these columns. An emission point delete
will remove the emission point, all associated emission point
comments, actions, and action comments. A Card 5 delete for
point 000 is invalid.
6-17
-------
..'• '•>
1
fl
si
^i
JJ
FLUT
—
—
ZIP
'5
PLLT
jt>
^
J/
-
JJ:
iy
POLLU
1
STATE RLG1STRATIOH
-0
ml
^
1
'! i
I i.
J
'U
1j!
•','i
LOADING
SO
rrn
URC
FT
4b
EC
"iU
PI
OM:
'M
:T
pT~
^b
s
STATt RtGULATIOH
:^
--"-
Ju
.:'/
.^H
1
,^
40
i
f> 1
s\£.
*l J
da
i|j
•-
^7
—
••y
,0
^i
$•
.:'-\
•JU
al
•OLLUT
~> <^ h
%
b/
ITT"
ITT"
^>
!)h
IW,
SIC
S^
6U
f, 1
ft?
bJ
^
!v^
fci:
FACiLITr CAPACITY
!iU
/
la.
f,D
Lb
^-
"
\
•£•
•T,
;>
•I'-e:
4
RDE 5
ROE 6
P7
hK
RDE
*lc
9
'(!
/U
/]
/V
^S?
PTT
/£
"i\
*&
i.
/4
rm
PROCESS DESCRIPTION
SO
f
bl
f>
Ti
^
r
b^
•*.
S"
ife
V
57
p
ll!i
b4
c
£
hi
?•
bi'
^
JJ
^/
M
r
6b
?
*,:-'
AC
^
/u
7*
/
—
/ J
—
7'V
\^
7f,
STP.FF
77
e%
(^
•WLI
/RET
—
7h
77
,'K
^
,?c
t'.',
7IJ
.
V>*
"H
"^Li':l HO. . ' EMHSIOli PD!::1 COME'^ ,- - ' • "
^
~
/
/V
t-1
6
^
3f-'T;c;wL
USED
.'!.
^s-
;'/
iCIIOfl
'.'K
£
J
-•y
A
:.')
f^i
ti
*i
DESCRIPTION
•.TPE SiO
;,'>
ft
I
v:;
ff
it
k
-;b
^
.10
^
11
G
^
•.(•
^
19
^
1
<>
••ii>
^
4 /
-h
I
^
^
~\>
•,il
'<
•>i
•A.
j'j
63161
DATE ACHIEVE!)
0
f,
O
f
7
^MT\?
1
f>Y
f,i
f.J
f.S
OATE SCUEOUL
fcii
J
Lsl>!7
!).'
:.:•;
f.1)
/'(;
1
STAfF
^ —
j S
t'e
/.;
ESULIS
.'(i
^
r
J
/'4
sN
1!,
^
N
;'f.
^
f^
/;
^
~'':'
7^
§
KN
^
i {
^
,:?
.J.r
^
C
"^
'i
f.
-$.
y
r
£
I
^
b
A
»-
^
•s
FIGURE 6-4
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 29
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.
6-19
-------
Figure 6-5 shows three delete transactions and one change trans-
action. A delete for emission point 004 will remove that emission
point and all associated point comments, actions and action comments
for that point.
A delete for emission point 002, comment line 1, will delete only
that one particular comment record from the Masterfile.
A delete for emission point 001 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 002, 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 five 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 all 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.
6-20
-------
-,-'.!0'i iT iO!j:ilY I SOIW,' liU'iii:.'
£00
COMPLIANCE DATA SYS f!M CODING SHEET
SUUSCE. liAM
STREET ADDRESS
47 aH 111 50151 52
RCE 5 p j
rr ::: rv "•: 3; ~.i 33 i> 35 3<= 5; 3? 39 -n 41 4?
00000
ZIP
STATE REGISTRATION
NEDS XREF
SIC
RDE 6
STAFF
?.' ?.- 29 it) 31 32 J3 3-
40 41 «2 43 44 45 46 47 48 49 50 bl 52 f>3
55 56 5/ 58
59 60 61 52
06 j56
67 68 69 70 /I 7^ 73 /'. 7b 76
0
0
0
POLLUTANT
,=•) A' ^-; r^
POLLUTANT 3
PLLT
LOADING
PUT
LOAD I KG
FACILITY CAPACITY
•iB|''.9J30|:iT ^ 5315415i I 561.5
RDE 9
59 aC jl 62 63 6
0)0,0 JO
SOURCE COMMENTS
0
0
0
0
0
0[0|0{0|0
II I I II I I II I II M I I ! I I I I I I I I I I Ml I I I I I I I I! I I! I I I I M
.- -
riLCXP O '-^ ?L'JT
ST(;TE REGULATION
PROCLSS DESCRIPTIOli
M'JLT
KRfF
35
3ft
'•9
50
5c
66
TT7T
LI
0
00
I
ISJ
0105
il
linn I'll iniiii i ii i MI i
-'9 =n 5i 52 53 51 35 'jb 57 br 59 GO f,l f;f f,
67 f,S 69
,i 7s 75 76 77 if. 79
! o|06
I I I M M I II i I M I II M M I I I I I I I I I I I I M I S I 1 M I I I 1 I I i M 1 I i I I 1 I I
L ' 1 i i i J- <
^
i?
^
^1W^
^V'l -
-^>
,xj
^
i
^
ks
^y
k">
\ \
d
k>
K^^m^^w^d
> i^ ^1^1 ^"1 ^ ^ j^y"] ^J^l \^j^
ACT 10
TYPE
DATE ACHIEVED
X
I
DATE SCHEOULE:D
t)^
F
STAFF
o;
0"s
ESUL1!
/O
/ 1
ROE 8
_1
1
\
^o
^
^
i r-
t "i
•X
;•) !-. .
^\K\K\h^\>
AC: -mi ca-iKEUTs
M
f r
-LzL,
J-l
.^_LL
—
t
4'
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
iH
g
5
t
j
c
O 0)
-i-( U
s? •?
0) 4J
OS w
i
1214
>%
4J
§
O
CJ
5 6 J 8
O
O
l-i
O
OT
9 10 11 12 13
4J
5
O
0.
U IS 16
t (U
4J »o
•H O
U U
23 24 25 2E
Source Name
27 28 29 30 31 32 33 M 35 3E 37 3t 59 10 41 42 43 44 45 4o
Street Address
47 48 49 M SI 52 53 54 55 56 57 58 59 60 61 62 63 M 65 6G
H
M
N
Ed
"1
i3
§33
HHHH
22
ROE 4
67168 69 [70 71 7273 74
RDE 5
7S 76 77 78 7!
a)
4J
«
•o
Q
5
80
hO
u>
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
CM
0
o£
<
u
i
(3
5 u
1-J 4J
eo (0
0) 4J
o£ co
1234
4J
5 S 7 8
0)
U
l-i
0
in
9 10 II 12 13
C
•H
O
O,
9»
c o
O 1
•H -0
4J (4
o ca
City Name
< u
14 15 IS J17 18 19*20 21 22 23 24 25 26 27 28 29 30 31 32 33 M
(U
"8
0
(X
•H
N
35 36 37 X 39
State Registration
Number
40 41 42 43 44 « 46 47 48 49 50 51 52 53 H
1
|»
55 56 57 58
U
H
59 SO SI 62
Un
Q)
-------
TABLE 6-3A
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 3
1
1 2
41
u
d
j_
1 4
>>
U
C
3
C
till
O
O
b
1
1 10 II II 11
u
5
c
14 IS l«
Vrtionff
ir is
a
u
5
19
V4
0)
iH
•H
rt
n?i
u Pollutant 1 *-
c *-»
CO
u
3
•H
i— t
C
'.' !1
0
C
21
n
j
:-*
1
d
I!
it
rfo! .. 9
g
<
pi
y
<:
-i
c a
•H U
*J "D -^
•9 VI )l r U
u Pollutant 2 u
c
Polluta
» n
-.
o
3
a
IK
!
it
-IHf
§
i-
fl
|
I]
IS
m
j
j
.1
o
00 U
Ic a
•rf 0
•o -H
u .) .1 - «
u Pollutant 3 u,
e
Polluta
U 47
,§
• tl
i .9
5
k,
d
» >>
•H -H
rH O
•H n
u o.
a a
(u U
4 SI 10 Gl U 6) U
Id
§
ii U Gl Cl C) 70 'I
0
i-t
U
2
III!
•H
r-<
U
3
< n
Filler
)7 II 11
tl
«4
5
n
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
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
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Numeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumer ic
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
6-25
-------
TABLE 6-4
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 5
m
Q
K
u
J
0 V
•H 4J
00 «
CO JJ
K( OT
,:|,4
4J
0
u
S 6 7 S
0)
U
3
O
co
9 10 11 12 13
4J
,Jj
O
PL,
14 is ie
0)
=*"§
Sj°
±j 'j_,
o cd
^j O
17 I8J19
SCC Code
70 21 22 23 24 25 2S 27
^
S ft
f4 NJ
28»13
31
H
3
1211
Federal/State/Local
Regulation Number
14 IS U 17 1C 19 <0 41 42 43 <4 45 4£ 47 48
E-
^
L.
U-
49
Process Description
50 51 52 U 54 55 56 57 SB 59 60 61 62 63 64 65 66 67 68 69 70 71 72 71 74
r^ r^
J [J
p^ M
7J7677
111
(U
K
Ui-4,-0
5-rt D
P"
78 71
S
80
Date Name
SCC Code
NEDS Emission Cross-
reference
Compliance Status
SIP Code
Pollutant Code
State Regulation
Emission Category
Process Description
Multiple Cross-reference
Regional Data Element 7
Card Column
20-27
28-29
30
31
32-33
34-48
49
50-74
75-77
78
Data Type
Numeric
Numeric
Numeric
Numeric
Alphanumeric
Alphanumeric
Numeric
Alphanumeric
Numeric
Alphanumeric
Data Element Length
8
2
1
1
2
15
1
25
3
1
Justified
Left
Left
Left
Left
Left
-------
TABLE 6-5
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 7
O
•H
W
a)
at.
1 2
u
4J
CO
U
CO
] 4
4J
C
3
O
U
! ( 7 S
0)
u
3
O
CO
9 10 11 12 13
4J
C
•H
O
PM
14 IS 1C
0)
•o
=S= 'O
C '0
O '
•H *O
•U M
U .10
17 18 19
. Optional
Short Action
Description
20 21 22 23 24 25 X 27 28 29 30 31 32 33 W
Filler
3S 36 37 38 19 40 41 42 43 44 45 46 17 48 « SO SI X
0)
c,
4J
4J
<
S3M
Date
Achiev-
ed
SS X S7 SE 59 CO
Date
Sched-
uled
61 62 63 64 GS 66
U
S
co
576863
CO
rH
a
(A
-------
TABLE 6-6
KEYPUNCH INSTRUCTIONS FOR CARD TYPES 4, 6, AND 8
3C
•
O
•
*^
3
u
Q
O 01
•Hj 4J
00 (0
w| ^^
M
1 2
CrJ
1 4
^
4J
e
o
o
1678
01
0
3
O
C/3
9 10 It 12 13
*J
c
•H
O
PN
14 IS 16
C
0
•H
4J
u
<2
17 .»
•o
O
t
•o
1-
a
=S:
41
rt
•H
1920
Comments
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 3o 39 «0 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 56 53 60 61 £2 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
4)
eg
•o
a
to
I
re
X
Date Name
Line Number
Comments
Card Column
20
21-79
Data Type
Numeric
Alphanumeric
Data Element Length
1
59
Justified
-------
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. When the input transaction volume is
under 2,000 cards per week, the following 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 OSI.
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
7-1
-------
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.
7-2
-------
TABLE 7-1
EDIT ERROR MESSAGES
Data Element
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
Number
Compliance
Status
Action Number
Action Type
Update Code
Action Type
Update Code
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
*** POINT MUST BE GREATER THAN ZERO
*** INVALID COMPLIANCE STATUS CODE
*** ACTION NUM MUST BE GREATER THAN ZERO
*** INVALID ACTION TYPE
*** NO DATA IN COL 21-79 FOR DELETES
*** ACTION TYPE REQUIRED ON NEW ENTRY
*** DO NOT DELETE POINT 000
For Detailed
Explanation,
See Page:
A-2
A- 3
A- 3
A-5
A-6
A-ll
A-9
A- 7
A- 8
A-14
A-33
A-9
A- 7
A-37
A-8
A-44
A-9
A-44
A-9
7-3
-------
TABLE 7-1 (Continued)
Data Element
Name
AQCR
City Code
Zip Code
SIC Code
Federal Facility
Code
Active/Passive
Code
Staff Personnel
Code-Source
SCC Code
SIP Code
Pollutant Code
Emission
Category
Multiple
Crossreference
Date Achieved
Date Scheduled
Results Code
Update Code
Action Type
Pollutant Delete
Flag
Pollutant
Compliance
Message
* INCORRECT AQCR FOR COUNTY
* CITY CODE SHOULD BE NUMERIC
* ZIP CODE SHOULD BE NUMERIC
* SIC CODE SHOULD BE NUMERIC
* INVALID FEDERAL FACILITY CODE
* INVALID ACTIVE/PASSIVE CODE
* INVALID STAFF CODE
* SCC SHOULD BE NUMERIC
* INVALID 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 REQUIRED ON NEW ENTRY
* 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
For Detailed
Explanation,
See Page:
A-12
A-13
A-25
A-28
A-29
A- 30
A- 32
A-35
A- 38
A-39
A-40(A)
A-42
A-45
A-46
A-46
A-48
A-44
A-32B
A-32B
7-4
-------
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. The report also contains
column headings for the following data elements: Region, State, County,
Source, Point, Action, Card Type, and Update Code. Directly beneath
these column headings are two rows of numbers indicating card columns;
the position of any data on the card can be determined by referring to
these card column identifiers.
For each new Card 1 accepted by the Edit, a county name is generated
and printed directly beneath the County Code; this county name is passed
to the Update, where it is placed on the Masterfile together with all the
other input data.
7-5
-------
COMPLIANCE DATA SYSTEM EDIT REPORT
REGION 9-SAi TONCISCO
TRANSACTIONS ENTERED ON /I9/76 AT 07:59
001
CKD
KG ST CNTY SRCE PNT AN TYP
Lg £
12 34 5678 90123 456 78
(>* 05 7760 OO403 000 00
09 05 7/60 00405 000 00
0<* '"'5 6700 00036 000 00
SAN B6.KNARDINO
EKERN
9 O5 3480 00540 000 00
KERN
09 05 0060 00400 000 00
E9 05 6820 00042 000 00
ii o:' oooo cioattf ouu no
09 03 0980 OO420 000 00
09 05 4200 OO978 000 00
09 05 6700 OO036 000 00
09 05 34 £0 00406 000 00
0
-------
Error messages are identified on the right hand side of the report.
In addition to the error messages, data elements in error will have one
or more asterisks directly beneath the data element to help pinpoint
the problem area which needs to be corrected.
7.4 Edit Job Control Language (JCL)
To execute the Edit Program, use the JCL shown in Figure 7-2.
Unless ALPHA is being used, a priority card should be the first card
of the run job stream. Because a job cannot receive this priority un-
less it uses less than one minute of CPU time and produces less than
10,000 lines of output, it is better to run two Edit jobs with 6,000
input cards rather than one job 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 ALPHA 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.
7-7
-------
Submitting Input via ALPHA. If input data exists on an ALPHA
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 ALPHA concepts.
7-8
-------
AUTHOR
PROGRAM NAME CDS Edlt
TASK NUMBER
TRC
JCL for using the CDS Edit with card input.
1
/
/
/
/
p
/
/
rh
-
2
*
/
/
/
/
*
O
3
P
E
C
E
E
ihi
4
R
P
D
D
5
1
A
S
1
4
o
VI
F
f
6
O
•
1
E
T
f n
JO
7
R
•
1
D
.
£
8
1
•
1
1
C
IT'
9
T
T
A
g_
10
Y
R
sh
11
D
nu
12
J
E
S
~ii
IH
•
1
a
n
•
1
a
13
O
X
1
hi
•
1
a
14
B
E
N
.[
T
a
15
C
In
16
4
(
r*ri
• £,
17
a
C
D
•
ft
.S
.S
IB
a
D
D
pi
f
t\
t\
t\
19
a
S
rh
P
e
e
20
a
I
*
P
is
us
us
21
i
P
°H'
pi-
er
er
22
•
1
T
I ^
ft
S
S
23
•
1
n
f
24
•
1
rh
r«
gi
C
25
)
p
1n
1C
>n
)S
26
/
jy
r
,o
n
FI
E
27
1
Tf
kiM
(\
mt
im]
;ui
>n
28
U
j
f
<;
i
ei
£
t
29
S
ITfl
un
•
»
7-
OE
30
E
rrJ
flS
56
th
2
C
31
R
IP
•
k
)N
32
•fr
^a!
:R<
33
1
QC
ic
L
34
D
V
35
i
il
36
/
ie
37
T
! i
38
i
-
re
39
M
l
40
E
t
41
:
ire
42
1
uj
43
h
44
10
45
46
47
\
48
49
50
51
52
'
1
53
1
54
55
56
1
57
1
•^J
I
-------
AUTHOR IRC
PROGRAM NAME CDS EDIT
Using the CDS EDIT with the "DUMMY" mode; with this mode, no data is saved on the MOD
1
/
/
/
/
]
/
/
r
-
2
*
/
/
/
nP
/
V
A
hp
3
P
E
E
Lit
E
fi
4
R
P
D
D
t
O
5
1
A
S
1
ai
F
rft
6
O
•
1
E
T
S£
fli
7
R
•
1
D
•
ct
f\
8
1
•
1
1
C
Lo
Pfl
9
T
T
A
i (
rrl
10
Y
R
ai
4
11
D
ds
hr
12
J
E
S
s
111
tJVi
•
1
a
n
13
O
X
1
10
ri
•
1
a
14
B
E
N
ilc
IP
•
1
a
15
C
b
p
a
16
4
(
D
a
flf
17
a
C
D
>l
rrl
i
1
i
18
a
D
1C(
f)
;
5
19
a
S
X
d
t
he
hf
h<
I
20
a
1
in
tif
t
i
SI
21
i
P
me
f
se
SF
NG
22
•
1
T
11
nri
r'
r1
r'
T
23
•
1
n
it<
Q
;
;
IE
24
•
1
r
15
'1C
El
25
)
T
a
]\f
i
f
If
UE
11
26
r
Y
ft
f
ni
rr
E
•s
27
i
P
;r
n\
ti
Oil
7-
Dl
28
U
E
tl
IS,
ill
If-
nhi
I
M
29
S
=
e
rl
ni
sr.
IY
30
E
i
ab
ic
m>
t
OP
31
R
D
QV
n
PT
hF
n
32
U
k
de
V
)N
33
1
M
rci
:k
il
34
D
M
c
d
35
i
Y
ax
v<
36
/
i
d.
In
37
T
i
as
38
1
..a
39
M
•e
40
E
1
41
=
rh
42
1
C£
43
IS
44
45
0
TASK NUMBER
File.
46
47
48
49
50
51
52
53
54
-------
AUTHOR TRC
PROGRAM NAME CDS EDIT
TASK NUMBER
Using tape input instead of punch card input to the CDS Edit.
1
/
/
/
/
/
/
/
/
-
2
*
/
/
/
/
/
/
*
3
P
E
C
E
E
4
R
P
D
D
O
5
1
A
S
1
F
6
0
•
1
E
T
7
R
•
1
D
•
8
1
•
1
1
C
9
T
T
A
10
Y
R
H
D
12
J
E
S
D
V
wi
•
I
a
n
X
y
z
13
0
X
1
C
O
er
•
i
a
X
y
z
14
B
E
N
B
L
e:
•
i
a
X
y
z
15
C
:
=
a
X
y
z
16
4
(
D
(
S
X
y
z
17
a
C
D
R
E
X
/
z
18
a
D
E
R
19
a
S
D
C
=
•[.
i!
•f!
•f <
1
•: ,
20
a
I
S
F
z
F:
21
i
P
N
M
z
hf
he
hf
hr
hf
Vir
Gl
22
•
1
T
=
:
Z
YJ
L
11
r\
h
RE
23
•
1
n
X
F
z
Sfi
se
SP
it
In
7
24
•
1
X
B
z
-ll
.1,
• ',
•k
-4
25
1
X
;
Z
l
nl
S'
]
26
/
X
L
pc
7f
NP
27
i
X
R
•f
a
•f n
n
28
U
X
E
l1
CC
1
f
4
UT| F
29
S
;
C
• •(
>U1
nil
,f
•hi
101
30
E
U
L
il r
it
ihf
> r
[ 1
31
R
N
=
ni
y
at
Af
32
1
8
mb
a
E
33
\
T
0
er
**
r»n
34
D
r
f
ri
35
i
2
B
P
36
/
4
L
ti
37
T
0
K
na
38
1
0
s
39
M
/
1
r
40
E
D
Z
mi
1 f
41
s
1
E
fit
An
42
1
S
r
h
43
P
y
i
44
r
y
T*4
I I
45
S
y
in i
*
46
H
y
H
47
R
y
pi
1
48
>
)
a
49
,f
1
50
8f
1
51
52
53
54
-------
AUTHOR TRC
PROGRAM NAME CDS EDIT
TASK NUMBER
Saving the optional REJECT File during a regular Edit run; this file can then be corrected via ALPHA
1
/
/
/
/
/
/
/
/
/
/
1
2
I
/
/
/
/
/
(/
/
np
/
1
le
3
P
E
C
E
E
ut
E
a
4
R
P
D
D
D
t
O
o-
5
1
A
S
1
1
ai
F
e
6
0
•
1
E
T
T
Si
tv
7
R
•
1
D
•
•
ct
0
B
1
•
1
1
R
C
io
ca
9
T
T
E
A
IS
rdi
10
Y
J
R
si
!
11
E
D
OL
he
12
J
E
C
D
D
V
S
Id
ul
W
•
|
a
n
13
O
X
T
1
C
O
1
b
i
lei
•
1
a
14
B
E
S
B
L
N
'• i
>e
e:
•
1
a
15
C
0
P
=
S
l£
Pi
a
16
1
(
D
:
(
S
D
ce
ac
17
a
C
(
R
E
D
d
>d
18
a
D
D
N
E
R
.mi
al
19
a
S
S
E
C
;
*
ec
t
1
i
20
a
1
N
W
F
W
if
he
R
B
21
f
P
=
i
M
O
te
e
rh
s
22
•
1
T
C
K
C
R
iy
id
> i
\ \
\v
23
•
1
n
N
E
F
K
a
o:
Sf
si
:N(
24
*
1
•
E
B
5
t<
t
r1
i
i
L
T(
I 1
25
)
E
P
/
0
r
he
s
>
Iff
TIE
26
r
P
)
L
th
t
LU
R
R
27
U
A
i
R
a
:a
1
<
ill
J-
2J
28
S
•
1
S
E
ib(
ISi
rrl
U
|
:e
29
E
•
1
P
C
v«
ct
f -f
I1U
1 I
30
R
•
1
A
L
J
io
al
mo
II
31
•
c
=
CL
1
;
n
E
32
1
a
E
8
c
de
33
D
a
;
0
ire
?k
34
i
a
(
J
.
35
/
a
T
B
36
T
•
R
L
37
1
E
K
K
38
M
R
i
S
39
E
R
(
1
40
s
O
2
z
41
1
R
i
E
42
S
2
B
43
/
)
3
44
U
J
1
45
N
/
2
46
1
0
47
T
)
48
:
f
49
3
50
3
51
3
52
0
53
-------
•*J
I
AUTHOR TRC
PROGRAM NAME CDS EDIT
TASK NUMBER
Printing the optional REJECT file during a regular Edit run.
1
/
/
/
/
/
I
/
/
T:
--
2
K
/
/
/
/
ipi
/
X
e
3
P
•
1
C
E
E
t
E
ab
4
R
•
1
D
D
D
tr
0
ov
5
1
•
1
S
1
I
an
F
»
6
O
E
T
T
;a
:w<
7
R
D
.
•
td
c
8
1
1
R
C
or
ai
9
T
T
E
A
c
ds
10
Y
J
R
ar
s
11
E
D
Is
101
12
J
E
C
S
si
1(
Wt
•
1
a
n
13
O
X
T
1
01
b
RT
•
1
a
14
B
E
N
Id
g
Pi
•
1
a
is
c
D
b
>lf
a
16
4
(
D
D
'- I
ct
17
a
C
D
It
•
d
18
a
0
S
ce
at
i
1
•i
19
a
S
Y
*
i
t
«
.
!
20
a
i
S
.m
le
h.
hf
hi
21
t
P
O
ie<
ei
i \
\
^
PR
22
•
1
T
U
±c
d
se
fiP
S€"
IN
23
•
I
n
T
te
of
r1
r1
r1
n
24
•
1
5
Ly
t
;
*
?K
IG
25
)
A
a:
ie
n:
PI
ai
U!
Tt
26
/
j
t«
f.i
ti
ni
-(f
E
E
27
i
>
D
r
an
al
nt"
n
7-
RE
28
U
C
th
ifl
5
p
111
)
FEi
29
S
B
»
>r
ITT
ih
:T
30
E
^
ibi
01
IA1
Fl
31
R
B
v<
f
LE
32
L
J
pr
33
1
K
CL
f ,
34
D
S
c
35
»
1
in
36
/
Z
< •
37
T
E
38
1
£
39
M
8
40
E
^
41
=
42
1
43
44
45
46
47
48
49
50
51
52
53
5<
-------
AUTHOR TRC
PROGRAM NAME CDS EDIT
Using* ALPHA to submit both job control and data on a ALPHA data set in order to run
1
/
/
/
AI
tl
/
Ir
c
TI
A]
-
2
/
/
/
,PH
e
/
se
0
e
J»ll
3
E
C
E
A
ab
rt
M
ab
A
4
P
D
D
d
3V
t
M
3V
W
5
A
S
1
ir>
ie
A
t
1:
6
•
1
E
T
ec
al
N
.LP
1
7
•
1
D
•
n
or
o\
D
HA
es
8
•
1
1
C
pa
ds
»
po
9
T
A
•d
re
?
:o
id
10
R
•ti
:o:
I7T1.
w:
11
D
iaf
d
S
nr
t\
12
J
E
S
PR
as
u
w
S
V
•
1
a
n
X
13
O
X
1
S
t
B
il
b
ie
•
1
a
X
14
B
E
N
10
ie
M
it
re
•
1
a
15
C
iir
li
1
>li
:h
a
16
(
D
b
st
T
ce
Jc
17
a
c
D
g
r
i
t
b
1s
1s
In
18
a
D
>r
ec
M
ie
ta
f
t
t
19
a
S
*
iC(
>r<
O
ii
ib<
P
p
e
20
a
I
H(
c
D
pi
r
ill1
11?
Ui
21
t
P
d
f
E
t
fc
PT
PT
ei
IN
22
•
1
T
">Y
th
=
tr
r
•R
•s
i .
•B
PU
23
•
n
r
k
B
in
th<
r.'
]
i r
24
•
IP
AL
i
:a<
• ]
:
:m<
K
'0
25
i
a|
?R
R
ti
di
1r
SLt
tt
UF
CI
26
1
0\
\.
O
on
t
u
e*r\
h
E
S
27
)
Q
da
U
s
Pr
1,
in
1R
j-
Vlt
28
i
•h
:a
T
:o
>g
1,
.
l-i
i
, \
29
i
p<
s<
E
;ei
ai
11T
P<
fYI
30
U
i
t.
z
he
•
hf
ec
BU
31
S
er
X
r
y
t
R
32
E
T
X
wi
er
33
R
is
i
:h
Till
34
\
P
tl
•
\A\
35
1
iSf
R
e
r
36
D
37
i
£
T
JC
11DI
Y
L
be
38
i
39
T
40
1
INSEFl
=
Ln
m
4
o
i
th
41
M
c
S
a
42
E
>m
E
>a
43
=.
na
Q
tcl
44
1
d
U
•
45
tc
E
ot
TASK NUMBER
the Edit.
46
a
N
s
47
rtd
C
tr
48
E
ia
49
=
i.
50
N
51
O
52
N
53
E
54
-------
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 DEC to run on
Wednesday nights.
8.1 Update Program Description
Prior to the Update Program, all input transactions from the MOD File
are sorted into the same sequence as the Masterfile. The output 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 in the Update depending on the Update Code present on the
transaction.
To add a new record to the Masterfile, the Update performs the
following steps:
1. The records on the input Masterfile are copied to the output
Masterfile until an input Masterfile record is found with a
record identifier (Region, State, County, Source, Point, and
Action Numbers) equal to or greater than the record identifier
on the input 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.
8-1
-------
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 input
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 input
transaction.
2. If there is no input Masterfile record with the same record
identifier as the input transaction, the input transaction is
rejected.
3. For a comment delete, the input Masterfile record which matches
the record identifier of the input transaction fs 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
input 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
input 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 input trans-
action are not copied to the output Masterfile.
8-2
-------
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.
Regional users should call the national Data Bank Coordinator to
add, change or delete entries on personnel tables. The user may consult
the Data Element Sheets in the Appendix for additional information.
8.2 Update Report
The Update Program produces an Update Report which is stored on a
Regional file. If the user had transactions which were entered into
the update cycle, then the user must request his Update Report by
8-3
-------
submitting the Update Report Job Control described in Section 8.2.1.
This must be done prior to the next update cycle. As soon as the next
update cycle is run, the previous week's report is no 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
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.
8.3 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
-------
UPDATE REPORT
03/27/76
STATE
CODE
0
34
39
3V
39
J9
3V
39
39
29
39
39
J9
39
39
3V
39
39
37
39
39
39
39
39
39
39
39
39
39
39
39
39
39
3)
39
39
39
39
39
39
39
39
39
39
39
3-J
39
39
CNTY
CODE
5678
0560
0160
0560
0560
0550
0560
0560
Ci>60
05 oO
0550
0560
0550
0560
05 cO
0560
0560
0550
0560
0560
0560
0560
05 tO
0560
0560
0560
0?60
0560
0560
OS CO
0560
0560
0550
0560
0550
0560
Oi60
0560
0560
0350
0560
0:60
0560
0560
C350
0560
0560
SOUFCE
CCCE
I
90123
OCC19
0001'
OOC19
00019
00019
00026
00025
OOC26
00026
00025
00026
00025
00026
00036
OOC36
OG036
00035
OC-036
0003*
00035
00336
0003'
00037
00043
OCC43
00043
00043
00043
00043
00043
00043
OOCO
00043
00043
00043
G0043
00043
OOC43
OCC«,3
OOC43
00043
OC043
30045
OOC45
GCC45
00045
EM
PT
456
000
010
010
015
015
012
012
012
012
022
022
022
022
030
030
031
031
031
031
031
031
010
015
010
010
010
010
010
010
015
015
015
015
020
020
020
020
020
025
025
025
025
O'JO
Oil
01 I
Oil
ACT
NO
78
00
00
05
00
05
01
02
03
05
01
02
03
05
00
05
00
00
02
03
04
05
05
05
00
Cl
02
03
04
05
00
00
05
05
01
02
03
04
05
00
CO
05
05
00
00
00
00
CARD
CODE
9
5
5
7
5
7
7
7
7
7
7
7
7
7
5
7
5
5
7
7
7
7
7
7
5
7
7
7
7
7
5
5
7
7
7
7
7
7
7
5
5
7
7
5
5
5
0
COMPLIANCE DATA SYSTFM
REGION 3- PHILADELPHIA
OUTPUT SFR1AL 000139
CARD COLUMNS:
234567
012345678901234567890123456739012345678901234567890123456739
4
4
122674 01
4
122674 01
070177
070177
5
063079
5
5
043079
063079
081275 01
031275 01
4
073175 01
4
4
091171 01
01
073175 01
4
4
091171 01
091175 01
5
5
5
5
UPDT
CODE
8
0
C
C
C
C
C
D
D
n
C
L)
D
D
C
C
C
C
C
D
D
C
C
C
C
C
D
D
D
D
C
C
C
C
C
0
D
0
D
C
C
C
C
C
C
C
C
C
PAGE 3
UPDATE ERROR
ACTION MESSAGE
C = MULTIPLE CHANGE
CHANGED
CHANGED
.CHANGfcD
CHANGED
CHANGED
C6LFTE
DELETE
DtLETE
CHANG CD
DEL£TE
DELETE
DtLETc
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED £
RCJcCT NOT ON FILE
REJECT NOT ON FILE
ChfJGFD
CHANGED
CHANGED
CHANGED
CHANGED
D1LETE
DLLETE
DELETE
DILUTE
CHANGED
CHANGED
CHANGED C
CHANGED
CHANGED c
UtLETE
DE.LET6
DtLcTE
ULLETE
CHANGED
CHANGED
CHANGED C
CrlA.MGcD
CHANGED C
CHANGED
CHANGED
CHtNGc.n C
CHANorlJ t
FIGURE 8-1
UPDATE REPORT
-------
TABLE 8-1
UPDATE ERROR MESSAGES
Update Error Message
Explanation
SOURCE NOT ON FILE
POINT NOT ON FILE
ACT NUM NOT ON FILE
NEW 2 INVALID
DUPLICATE TRANS
NOT ON FILE
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
8-6
-------
TABLE 8-1 (Continued)
Update Error Message
Explanation
ALREADY ON MF
98 ON MF
{.(AMPERSAND)
S2 REJ
Action Numbers being used on the
transaction.
A transaction with an Update Code "N"
cannot be added to the Masterfile if
a testerfile 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 Masterfile.
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 not an error message; it is only
a warning that multiple changes have
been applied to the Masterfile in
chronological order.
If one or more sets of pollutant compliance
data cannot be added to the Masterfile 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.
8-7
-------
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.4 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 on or
before Wednesday noon.
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 on all mornings following an update cycle,
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
8-8
-------
Language described in Section 8.6.
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 an ALPHA 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 OSI sign-on procedures for System "E" by
typing in the user account, initials, keyword, and terminal
identifier.
2. As soon as ALPHA gives the prompt, COMMAND?, type in the
following and then hit the carriage return:
LOAD CN.EPAEXC.A026.CDS.SYSOUT
3. As soon as ALPHA gives the next prompt, COMMAND?, type in
the following and then hit the carriage return:
LIST
4. Figure 8-2 shows the contents of the log produced by following
the above steps.
8-9
-------
o
1 n tr * f>'.'-"^- f *?*'. »
r I p»n fvstrr1 , ^ ro''vfr
ri| p «^rrvi7rr . nsp r ;^/ -;,->ssv'or'J, ^rroi'n t , t
^r^pj^^^fijpsjlj^pl J
~n<-;-/y v\?r nn lino " ,-t l':"":^, ?S/
*••*' -: .^ 7^77 i^ •* Mm i 'o j ( r> * v r:*- -".n o r ? ''i|| MPT "^
To? J rr . Tirrxc .nn'Hr . r''s . s vsotit
'rt • '
7rif •
00 v^ .- , nri .-iiTir. r ,o rrrip..' p_,_
rf"
r>r;."7 «p t ?•-- j I Mr c rpn n r r t .--'• op_ «. i 7 i ;'< r>rrr>"^- inni.T,_
......
pn t ..j.|_ i .!r^ r^- r,-r- i n" TO-
' ?t /.J:"t:nr, ^5/^7/77, or ^^r ? n'ru
FIGURE 8-2
CDS UPDATE LOG
-------
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.
8-11
-------
r
M
NJ
AUTHOR TRC
•
1
/
/
/
/
/
-
2
*
/
/
/
*
3
P
E
C
E
4
R
P
D
O
*
5
1
A
S
F
'
6
O
i
R
PROGRAM NAME CDS Regional Update Report
TASK NUMBER
JCL for obtaining the CDS Update Report for a given region.
7
R
•
P
8
1
i
T
9
T
•
10
Y
11
.,
'2
J
E
Wh
•
1
a
n
13
O
X
er
•
1
a
14
B
E
>:
•
1
a
15
C
a
16
4
(
17
a
c
is
is
is
18
a
D
t
t
t
19
a
S
ie
le
ie
20
a
R
U!
U!
U!
21
i
P
er
ei
ei
1
22
•
1
T
's
's
's
:D
23
•
1
n
r
S'l
24
•
1
!R:
PI
25
)
it
ac
01
AT
26
•
it
CO
ti
FI
E
27
i
La
un
mn
;u
IE
28
U
i
.s
; ;
>e
IE
01
29
S
•
IU1
1 •
9
8-
T
30
E
be
t\
3
JO
31
R
r
e
B
32
va
:o
33
1
Li<
JTI
34
D
•\
01
35
i
al
36
i
ue
37
T
s
38
1
ir
39
M
40
E
t
41
=
ir
42
1
>u
43
5h
44
It
45
•
46
47
41
49
50
51
52
-
53
54
•
55
56
57
-------
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 advantages:
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 10,000 lines of printout can be
met within one hour.
o Improved selectivity - Information can be selected from the
Masterfile t'o 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
9-1
-------
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 six 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.
9-2
-------
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
i
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.
9-3
-------
A standard Quick Look print line contains State, County, Source,
Point, and Action Numbers together with up to ten 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 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:
6LK1 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-1A 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
9-4
-------
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 and Indiana facilities which
have had Compliance Monitoring Evaluation Actions scheduled between
January 1, 1975, and March 31, 1976.
Sorting was based on State and Source Name.
Pring line selection was based on the following data elements:
Source Name, City, State, Action Description, Date Scheduled, and Date
Achieved.
9-5
-------
OUICK LOOK REPORT
05'25'76
COMPLIANCE DATA SYSTEM
ILLINOIS AND INDIANA COMPLIANCE MONITORING
PAGE
ONIT -EVAL"750212^750212~
CO.-IP VJNIT EVAL 740?3J
COMP MONIT EVAL 750407 75O407
COMP i>ONIT EVAL 750627 750627"
IN COMP i^ONIT EVAL 760331 760302
IN CUMP rONIT EVAL 750604 750604
IN COMP N1NIT FVAL 7<".O?n 750713 '
IN CUMP f.ONIT CVAL 7--.0213 750213
F.ICKIBE 9-1 .
SAMPLE QUICK LOOK REPORT
i»
"1,
J.
-------
SYSTEM
CK" L'X'fc' WITH
OOO '. OOO OO &R>;i-'--RT ''! 'ilC'€ !NC!N 06 ''02 ''
oo i oo
OOOi 000 0: s:'£^i"H'?1""i
02 OO/OO/OO 08 ''I?
OV Oi'>~' OOOO:: OOO OO '5 ILL L*1"'^ i;n>:c-OJvjv 06/1 0/7*.
. __ _ _ OOJ, £!>_ _ __ __ ____ _____ P.7/2^75 _p.7'"2£/7_!3
02 . 00 '00 /"OO tO/01 /7fj
0? ' . '. OO/OO/OO lO/Ol/7"5
. _________ .......... ____ 002. .00 ______ ..... _____________ _.__ ______________________________
OOO OO ly'ii" Tr,i\jj;_ r'73
_ cjj_ ______ j __ _ ________ _ _ _ OO i.''!0 '"O0_ I 1 /' 1 7 / 7T-
07/'l7/'7? O7/l7/7f5
Ol/'0?''76 '51 /'OS/7 -i
kO ' ('!•'- 04/.3O/76
^ ! 07 . o-3/l:i /7/, /
j> _ _ _ <;;£-. O6' 30' ~/:• __ /
0'-' 0'?' 30/76 /
10 12/31/76 /
00 1 00
002 OO
OOI O! /OO'OO
0=5 Od/'01''74 06 /"t 9
O02 OO
oo? oo
" r.'-00 01
.001 00
•17 o;"."^ 0000i: 000 Oi =ivj.p^.TMC._M">'_J::E'?>:t ..^vW.iiT _ i !J.__0_5£.20_i76 _______
001 00
.••7 o/-.::? OOOL t ooo Oi ^=-e£6To-; s^Lt^. iwi:.- • 03 /2 7 /7/r j? 1/02/7* 01/02/74
___ OOL_f.!0 ___ ____ j_ _ ________ ____ __ __ ___
ii~ >';'---^- 00012 '"'OO 01 ^O.f:i V SijfE^" 1?.-Kiki IS O3/27'7fc 10.^04/74 i
- 02 02/05/7^
OOA ..0.0. _______________ ^ _____________ , ________________ ..... _______________________
002 01 . . , io/QA/74 10/04/76
OO.J 01 io/04 '74 10/04/7*
_ . 00" 01 -_, - - - - ._ 10<£J4/174_.tO/04/7*_
:.':"• 0000:? T'^'O 01 •jr.M''1'IN'=- G:JL.Cvf 0^'20'7/:. 01 '02/74 01/02/71
02 .04/25/74 04/25/7-1
Figure 9-1A
.Quick Look Report witlx.Data .Suppressioii
-------
05/25/76
COMPLIANCE DATA SYSTEM
ILLINOIS AND INDIANA "COMPLIANCE MONfTOft'lNG
PAGE
ST CNTV SRCE EP AN
SOURCE NAME
CITY NAME
15 2640 00004 000 01 AMERICAN CAN
T5~5Tl
INDIANAPOLIS
OIL
15 27.60 00054 000 01 AMERICAN OIL CO
WHITING
HAMMOND
15 2?60 00004 000 01 AMERICAN STEEL FNDRY HAMMOND
T5~2*^0002£"00&"0~T~~ANACOND(S HiGjMTOX TERRE" HAU
15 2?*n 00008 OOP 03 ATLANTIC RICHFIELD EAST CHICAGO
15 3700 00004 000 01 BEND IV
15
ERIE~
5 3230 00001 000 01 CAN-TEX DIV
15 1«60 00003 000 01 CHRYSLER
15 "26*0 00012 "000" 01 CHRYSLER"
KOKOMO
"TNDIANAPOCIS"
15 2*40 000*1 000 02 CITIZENS GAS & COKE INDIANAPOLIS
15 2640 00065 000 01 ELI LILLY
60005"T>WlTl "SMt
15 2600 00003 000 01 GMC
15 3460 00003 000 01 INDIANA FARM BUR MOUNT VERNON
"15 "4266"00"06«~000~OT ^NDIA~NA~GAS~«nCHeM TERSE"HATjTE
15 2360 00015 000 03 INLAND STEEL EAST CHICAGO
ST ACTION DESCRIP D SCH D ACH
IN
IN
IN
O'lM? MONIT EVAL 751231 751017
"CTIM3~MONI i fcvAC~750930~"750S22~
COMP MONIT EVAL 760117 750S21
IN COM? MONIT EVAL 750226 750226
K1 CriM?-MONTT EVAC'750930—750829^"
IN COMP MONIT EVAL 750930 750819
SOUTH BEND IN COMP MONIT EVAL 750212 750212
~EVANS~V rtTJE Ifl CTiM?~MONI r"EWAC~750417"7504 \~r
CAN.MELTON IN COMP MONIT EVAL 750408 750408
IN COM? MONIT EVAL 750124 750124
TN COM?~MONIT EVAL~750506~~7505O6~
IN CfJMs MONIT EVAL 750904 750904
INDIANAPOLIS IN COMP MONIT EVAL 751231 751016
"ROFOMO IN CdMP"MONIT-EVAL'750129—750'129-
ANDERSON IN COMP MONIT EVAL 750122 750122
IN
15 26<0 00010 OOO 02 GMC INDIANAPOLIS
!" 15~07CO~OOOl 3~1)00~02 "HAAS~C AB tNET S'EL'LER~S'B"QftG: 1KT
j 15 37QO 00002 000 01 INDIANA ij, MICH ELEC MISHAUKA IN_
COMP MONIT EVAL 760331 760225
' C"OMP~MONI T~EV AL~7iO"331
MONIT EVAL 750218 750218
IN COMP MONIT EVAL 750422 750422
"TN COMP~MONIT "EVAC~ 750204"750204"
IN COMP HOIMIT EVAL 750829 000000
15 4220 0000* 000 01 INTERNATIONAL STEEL EVANSVILLE IN
~F"&p;f~~WA~YNE ITT
HAMMOND IN
j 15 0060 00009 000 01 INTNL HARVESTER
! 15 236O 00023 000 01 JONES & LAUGHLIN
COMP MONIT EVAL 750417 750417
-CCMP~MONTT~EVAL~~750Tl5~750Vf5~
COMP MONIT EVAL 750226 750226
'If
I:
FIGURE 9-2
SAMPLE DOUBLE SPACED QUICK LOOK REPORT
-------
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.
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. If no user sort key is specified, Source Data
Reports are printed in the Masterfile sort order: Region, State, County,
Source, Point, and Action Numbers.
Figure 9-3 gives a sample of a Source Data Report.
9-8
-------
INLAND STEEL
SOURCE DATA REPORT AS OF 05/25/76
PAGE
37
t
1
1
1
i....
i
j
vO
i
1
1
r~
l
Rf. ST HNTY SOURCE
05 15 2360 00015
IN LAKE
AdCR 067
N'EX1? 00 1 ^
C'/CD It c."">
C C'W.ENT l OVERDUE
PTNO ENTIRE SOURCE
000 PLUT PT
ACTION 01 SCHD
ACTION 02 SCHD
ACTION 03 SCHD
ACTION 05 SCHD
ACTION 0.5 SCHO
ACTION 07 SCHD
PTNC BLAST FURNACE
001 PLUT PT
PTNO BLAST FURNACE
002 PLUT CO
PT.MO BLAST FURNACE
003 PLUT PT
004 PLUT CO
FTNO BLAST FURNACE
005 PLUT PT
PTNO BLAST FURNACE
006 PLUT CO
PTNO "~ BLAST'PIJRNACE
Oil PLUT PT
COMPLIANCE DATA SYSTEM
ILLINOIS AND INDIANA COMPLIANCE MONITORING
RDE1 A RDE« SIC 3312 APCD 1 ACTIVE STRG 0015
RDE2 P.DE5 F'ELJF NL>N-f-tD STAFF F1U
RDE3 RDE6 PR 1C.
-FEDERAL ORDERS ISSUED
SOURCE CMST 1 NOT IN COMP-NO SCHED SREG
7/18/73 ACHV
7/31/75 ACHV
8/2*/75 ACHV
SOURCE SIP 1 SCHED SPEC I1- IN KkUS SUja
SOURCE ECAT 3 OVER 1000 TPY
7/18/73 TYPE 63 NOTICE OF VIOLATION ISSUtD
RESULTS 00
/ / TYPE 78 EPA INSPECTION
KtSULTS 01 ACTION AL'HlbVED
/ / TYPE 81 COMPLIANCE MONITORING EVALUATION
RESULTS 01 ACTION ACHIEVED
9/12/73 ACHV 9/12/75 TYPE 64 EPA ORDER ISSUED
RESULTS
-------
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.
9-10
-------
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-4A shows a sample Variable Milestone Report.
9-10A
-------
I ...
' ^
05/25/76 COMPLIANCE DATA SYSTEM
NEW SOURCE PERFORMANCE MILESTONE
i COMPLIANCE STATUS REGION 5 ILLINOIS INDIANA MICHIGAN MINN OHIO WISCONSIN
I TOTAL 14 15 23 24 36 51
i
0 COMPL STATUS UNKNOWN 10 2 3 14
i 1 NOT IN COMP-NO SC-HED 731 1 '2
1 2 IN COMPL-SOURCE TEST It 7 112
3 IN COMPL- INSPECT I ON
4 IN COMPL-CERTIFICATN 2<> 7 6 1 2 4 t>
i S IN CMP WITH SCHEDULE
A NOT IN CMP WITH SCHD
^7 LINK-MOM CMP WITH SCHD
li
!£« NO APPLIC STATE REG
o IN-COML-SHUT DOWN
, TOTALS FOR 2. 3f «• 3i 9 37 14 6 2 'J 6 ft
TOTALS FOR I AND 6 731 12
TOTALS FOR 0 AND 7 10 2 3 14
j GRAND TOTALS 54 19 10 2 4 9 10
!
i
1
1
i
FIGURE 9-4
1
SAMPLE STANDARD MILESTONE REPORT
1
i
I
!
i
-------
M I LE'=.TONE
NCE DATA C,V?TEM . 'PAGE
. Nl.ii_TIPLE REOION /" ACTION LEVEL '' PAC'C 6«EA*' /' 10
*TTF STTE STTE STTE STTE STTE STTE STTE STTE STTE
A.-TI.I>; TVPP TOTAL 07 20 22 3O 4l.«7 .'01 10 11 18
!•=> " 177 """ 12 "" «2 " "20" " "" '",'•; ' |-
_t 2 •_ •_ '
t I I '
6 . I "~".\ ' I . • ' |
•* _J7_
121 ' 54
.265L__:___.JL50.
i.3'7 136
2 2
2 2
7 7
E,,-,;, ri.,:siu;... ATSP TOTU(_'T- *77 . 4A9 102 • 2*1 SO 55
Figure 9-4A
3apple"17afIaBTe
-------
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-5 shows a sample Questionnaire for Region X. Selection
was based on actions scheduled but not achieved between June 1, 1976,
and October 1, 1976. Sorting was based on Source Name.
9-12
-------
ACTIONS SCHEDULED BUT NOT ACHIEVED
03/25/76
COMPLIANCE DATA SYSTEM QUESTIONNAIRE
FOR STATE OF
ITTAHO
r
_POINT SOURCE
IDENTIFICATION
CODES 1-AUI ION~BCHIEVED
EMISSION POINT. STATE/-LOCAL REGUL,
ToTDJTART EMITTED CONTROTTTR03ECT;
POINT SIP
2-flCTION"NOT ACHrEVED
SCHEDULE INCREMENTS
OF" PROGRESS
ACHIEVEMENT OF INCREMENTS
"OFPROGRESS
I TWIN'FACTS"
j 1440
( AMALGAMATED
AMALGAMATED SUGAR
STftTE REGISTRATION
TWIN FALLS
144,0
AMALGAMATED SUGAR
!f
GTLLEVUE CITY
NO CITY CODE
CSF BOILER
REGULATION G
PART MATTER
6/30/76 STATUS CODE COL 71
OTHER PYf-'E ACTIOnir^E£ CO— DATE ACHTEVECi—COL 53—60"
REPLACE BY A FOSTER— MMENTS) MO DAY YR
WHEELER BOILER
~TO~-T 3=1480-00X501 -002-05- 7 COMMENTS"
SI 13 ORDER-EPA ENFOR COL 30 - R
FOSTER-WHEELER B- NSPS REG 6/30/76 STATUS CODE COL 71
OILER QTI-'ER TYPE ACTIOWSEE CO- DATE ACHIEVED-COL 55-60
REPLACES" CSFT30TLER™~MMEMTS> MO DAY /R
PART MATTER SOURCE #00001 POINT
*002-REG CDS
10-13-1480-50001-001-04-7 COMMENTS
PEPVTENFOR COL"80 --"R"
G/15/75
FINAL COMPLIANCE
MANUFACTURER-BARBER
"STATUS"CODECOC7T~
DATE ACHIEVED-COL 55-60
MO DAY YR
«;TATE
0180-0003
ART — MATTER-
SCHED PEND/NOT APPRV
10-13-0180-00003-001-01-7 COMMENTS
COL 80 - R
-EPf. CC-CODE COL—3O
10-13-0180-00003-001-00-5
COL 30 - C
"TWiN FALLS"
1460
l
oEYMER PftVING
2100 I'NDUS'T AVENUE"
ASPHALT PLANT
REGULATION N
"FINft'J" COMPCFANCE"
_S_TfTE REGISTRATION
148l)-"0004
PART MATTER
MODIFY OR INSTALL NE-
W EOUIPMENT AS NECES-
"5ARY
SCHED PEND/-NOT APPRV
STATUS CODE COL 71
~DATE~ACH lEVtu-COL. 53-50"
MO DAY YR
~10-1T-r4BO=OO004=TT31-05-7—COMMENTS"
COL 30 - R
EPA CC CODE COL 30
"10- 1 •?-I480-00004^1-er-OCr-5
COL 30 - C
I
FIGURE 9-5
SAMPLE QUESTIONNAIRE
-------
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. As
opposed to the Quick Look Report, this report lists comments. If no
sequence is specified, the report will be sequenced first by Action
Type and then the Masterfile sequence.
Figure 9-6 shows a sample Action Summary Report for Region II.
Selection was based on actions applicable to the entire source (point 000).
Sorting was based on State and City.
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-6A is a__sjimpl_e_o£j:he Compliance-Action Report1_ 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
9-14
-------
ACTION SUMMARY REFfiRT
05 /25/76
TYPE OF ACTION
EPA INSPECTION
STAFF MEMBER
AMD TITLE
R CELL AM ARE
ENGINEER
V PITRIJZZELLO
ENGINEER
V PITRIJZZELLO
ENGINEER
V PITKUZZFLLO
ENGINEER
V PITRIJZZELLO
ENGINEER
CCM'tENTS
V PITRUZZELLC"
0 Ei^GINEEP
'_. COMMENTS
t\
V PITRIJZZELLO
ENGINEER
ACTION
SOURCE NAME
AND LOCATION
CERTAIN-TEED PRODINC
WINSLOW TWP NJ
SUSSE* ROAD MATERIAL
ANOOVER TUP N.J
SUSSEX Ri-iAD MATERIAL
ANDOVER TWP NJ
SUSSEX RfiAD MATERIAL
ANDOVER TWP NJ
ANDOVER INDUSTRIES
ANDOVER TWP NJ
1 BORDERLINE COMPLIANCE
ANDOVEP INDUSTRIES
ANDOVER TWP NJ
1 TEMPORARILY SHUT DOWN
ANDOVER INDUSTRIES
ANDOVER TWP NJ
COMPLIANCE DATA &V --TEM
SUMMARY FOR ACTIONS > 50
DATE SCH
DATE ACH STATUS CODE
4/ o/75 01
4/ 9/75 ACHIEVED
5/14/75 01
5/14/75 ACHIEVKD
9/30/75 01
9/2«/75 ACHIEVED
5/ 3/76
/ / UNKNC'/N
5/14/75 01
5/14/75 ACHIEVED
9/30/75 01
9/29/75 ACHIEVED
5/ 3/76
/ / UNKNOWN
PAGE 1
STATE NO SOURCE NO
COUNTY NO POINT NO POLLUTANT
31
0740
31
5300
31
5300
31
5300
31
5300
31
5300
31
5300
00038
000
00006
000
00006
000
00006
000
01004
000
01004
000
01004
000
1
1
1
. _J
i
1
FIGURE 9-6
SAMPLE ACTION SUMMARY
REPORT
-------
"•" ""09/0'zV7?r" —"".-"--•••' •-"• •" ' ••"-—••-• --—• •-—-.-•.-•-,:--•---• -• O.GMPL T-ftHCE DATA SYSTEM — "~ ' " :.'- " .- " —---.--.-.-. .:-,;PA3E
' ' -• ' -•*" ••."-"..•'' . ^NrL^ 'OK .A CH REPORT . ' - '' • • .
"SOURCE "NAMrF"~: Ac-hs""" :STAFF'. """PTNO COMPLIANCE STATUS ' INSPECTION " NOTICE-OF "ORDER'' ~ " COURT TERMINATION"
-CITY • ST ATMT - .'•'-. EMISSION CATEGORY . -• VIOLATION ISSUED ACTION OF NOV '
Al.i.TFO CHEMICAL 'CCiRP '.Of-. 1. ftCC O12 4 IN COMPL.-CERTI-F> ..FEDERAL -2/12/74
OE 7 SfiAR ~~ """"LAN .-.-.--•-..-.-—-- -. .j -LFrs.~ THAN 1OO T FEDERAL .V/27/74
' ' '"'.'"'"..', FEDERAL ' "9/ 5/75
. '~ . ' • ." ' STATE
AE; fr-r-UNioN TFX PFT.-ib1II..'ll'"- 'JO'S - CfTCC"""^,~""~"~01OO"4"."IN"COMPL-CERTIF " "FEDERAL""' " """
-. NrBMENTAU' I.A -,N '.'.' •• '."" >"'-... "'. '<''. " -2 ; ] OO TO. 10.OO . TPY , STATE 11/26/74 '
"-• -. • .''•• : . .'-.'. '; . '•' .'..'• ••'•'•.'•"•.: - ' - •- - "STATE .-'"10/31/75-••.
' CSJIIM RTCF SA'hF:1; ; .1 Oft ''. t ACC -. ' ' :; : ''.:.' -000.4 IN • COMP-L-CERT IF ! FECERAL . ' •-:.•,- "- - ' 0'
• i-i=>VI-IFMTAM ' -I A- N . .;:'/'• ./- -". ' '"/ 2 100 TO tOOO.TR'Y. STATE [1/2O/74 -" - ;'.. _-..--.
'"" T "''• ------ -;-- -'--.-:-•:'-:; .;-----—-- - —-- ~. ..--.. ^ - . -..- •_- STATE ""10/31/75 " '.' —'—-'-'. ;•—:
.^ ..,T,:M-^ r,.r,. t-I.^Ts CO. . IO'S LftCC-'• .- , OOO t. IN" COWPL-CF.RTIF - F£.riEPAL . - S/ fc/75 . .
ruf" 'OHURCH^'POTNT—;L:A""Nv""""~--•--•--.--~^—--—------—2;"ioo';To ;ioo'o TPY"' STATE ~ '2/27/7& • •---~
• ,;.p !i-.;uiiSTRIFS, JiV.:. J.0fc .i.AC.C.v-: :;-:.' :• '•' OO5 4 IN CONPL-CERTIF FgDERfiL • .'.-
:-.",-1\!AI Ti^i-'ii'-i'VP'LF—TftTM """•~: -"""~ -.__-—. 3"OVER 1OOO TRY "STATE 4/25/75
.-";" ' -' •- - -.'.: - . , . . c;TftTE 8/31/75
.'. - . : •-..-' - ':.,'-- .'-'." • . • STATE 9/30/75..
•--•— '-'- -"- :-- -:•'—'—'.'- ;• ".—.-:.-' •-•-; - - " .' STATE 3/31/76"- -'
r' .-'-.-':.-- '..;•"•'''.• ":" -'•- • - " STATE - "4/30/76
. J.OA .'""•i.-'Arr::"" "-:'••":'"• •-~OG5" 4-• TI\KCONPL-CERTIF FE-DERAL":- -9/10/74
I .A N • .-''-•'• '-.-••• ;' '.' 2 100 TO 1 OOO TP-V. .STATE ' . •.
r-r^-—-----:—;-OOO--4"-IN"'CONPL-CERTIF 'FEGERAt" J'"; "*
i.'.A'M.''.'.-'•• ""'. •'• ' ' . .2,100 TO 1OOO TPY-' STATE 11/21/74
-'• ' '''. ' - -. -•' ,,^&- , ' " - STATE 1O/31/75
": ; ;" : ~. '~ ' ' ~~ ' ' " : - .STATE" "9/30/75
isnN-RiCr MI;..! io/-- Lscc" ."- . op& 5 -IN. COMPL w SCHE. FEDERAL 9/10/74
F- :----.-•---.-•- T;ff p.; '--• -• -.- ;- '•% ;ioO" TO 1 OOO -ff\ ' ' STATE 9/30/75 ' ~ - ; -" '" 4'/;-6/76-- "-.--—
i.i|-,o;; f-,-T ,":F =fti >-.•' 106 I..AC.O -' .-- .OOO 4 ]M COMPL-CERTIF "FEDERAL . • ' ' -
FR-W'inn" -.'. ' -.A." N 1- ' ". '•-••-:~. •-•;.- ". ":2"1OO TO'IOOO'TPY" STATE 11/18/74- --'--••- --- --••":. ""
="vA!-.!Cr=l.INp r;FF i NI Nf-. < Of-. LAi'Vp '. OOO 4 IN COHPL-CF.hlT IF FEDERAL . ' • ' -
-ViWrtFi.IMF - —
-------
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
Because each region has a different set of action types to represent the
above actions, the CA report is operational only for Region 6. If other
regions wish to utilize this report, they must specify the action types
which correspond to the above actions.
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.
9-15B
-------
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.
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.
9-16
-------
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 (OSI) 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.
9-17
-------
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-7. 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
10 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.
9-18
-------
COMPLIANCE DATA SYSTEM
Report Request Form
Dote Submitted
Return Report To.
Mail Stop
.Time
12 4 S
Reg.<
11.01 |_|
I 2 4
9
Report Tlllo
20
1..
S3
30
, i i i . . . .
60
40
i I,...,, i .
70
SO
,"|
. to
Data EUmont
11,01 I i . . I
|_j I ,,,,,., ^J
9 U U
Cond Value (loll Juitllled)
|_| I .. . .... I
J U L
1,01 1 ,
1
11,01 I . , , I
|1,0| I ... I
11,01 I ... I
I ... I
U-L
U L
11,01 I ... I [_j L
i . , , I l_j L
J U L
11.01 I ,
11,01 I . . I LJ U_
ii.oi L: I LJ < i1
I
!
11,01 I I
11,01 I ... I
U U.
U LL.
U L^.
.1
jl.Ol I ... I
i>,01 u ,_!
LJ L^.
11.01 I ... I LJ La.
REPORT FORMATS
LLOJ |__J
12 45
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE *
U - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - BLANK OR ZEROS
*Used for multiple values
of a data element
See reverse side for a
list of all CDS data
elements and their
abbreviations.
71 10 11
|3.0| I...I I ... I I , . . | I ... I | . . . I I ... I
124 79 12 14 17 19 22 24 27 29 12
REPORT SEQUENCE (Region, Stale, County, Source, are always pro tent)
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
Q2 - DOUBLE SPACED QL
LEVEL CODES (01 CARD)
S - SOURCE ONLY
P - POINT AND SOURCE
A - ALL DATA
C - CRITERIA MATCH ONLY
U
Number of
— lublalolllng
FOR QUICK LOOK REPORT ONLY
U.Ol I . . . I I ... I I ... I I ... I I ... I | . . . I I ... I | . , , I L
124 79 12 14 17 19 22 24 27 29 12 34 17 19 42 44
Enter Data Element! lefl to right in the same sequence at required on report
The leltmoil portion el the line always includei Slate, County. Source. Pain I and
Action Number unleti NOMD li coded In column 4 through 7
47 49
. . I
52
y
54 S7
With NOHO Only Supproi*
FOR MILESTONE REPORT ONIT
LSiPj | . , . I | , . , I | , '. . I I ... I I ... I I ... I I . . M I , ,
124 79 12 14 17 19 22 24 27 29 12 14 17 19
ROWS COLUMNS CCIUMN VALUIS
DATA DATA
EliMINT ItlMENT
(INK USIO rot VAIUI BLANK
42 44 47 49 52
I . . . I I ... I
54 57 5» 62
FIGURE 9-7
RETRIEVAL REQUEST FORM
9-19
-------
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-50> 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
9-20
-------
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:
1*7-7*1 |A| 12.3
T ™ ' . _» . H .. .
Data Element Cond. Value
bzcd Id
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 50*, and equal to or below 70. More importantly,
it can be used with the "date scheduled" or "date achieved"
9-21
-------
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 1974.
li.ol
.1.7.+.
Data Element Cond. Value
d yy i
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.
9-22
-------
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 1(9-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
9-23
-------
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 49 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 4jO-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
9-24
-------
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 is 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:
30 STTE CMST SNME 1
Columns 1 4 9 14 39
The above card will provide page breaks with
subtotals by state.
30 STTE AQCR CMST SNME 2
Columns 1 4 9 14 19 39
The above card will provide page breaks with
subtotals by state and by AQCR.
9-25
-------
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-7.
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-40 CARD column of the Report Request Form
must be 119 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 desired, a
"I1 must be coded in column 60 of the 40 card. Using this option,
source level data will print only on a change in source. Point level
data will print only on a change in point. Action level data will
always print.
9-26
-------
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,
'BLNK1 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:
50 CHTY ATPE 01 02 03 04 05
Card Column 14 9 14 19 24 29 34
This request will produce five columns of numbers, one column for each of
the selected action types. On the right hand side of the page, totals are
generated for all actions for a given county. One line is produced for
q-27
-------
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.
9-28
-------
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
D
The following selection criteria will extract data for Sources B, C,
and D
10 PLLT M PT
10 PCMS M 4
Pollutant
PT
S2
PT
S2
HC
PT
S2
HC
Pollutant
Compliance
4
1
4
4
1
4
4
4
9-29
-------
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
10 PCMS M 1
because each of those sources has one pollutant out of compliance.
The following selection criteria will extract Sources C and D
10 PLLT M HC
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:
10 PLLT M PT
10 PLLT M S2
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:
9-30
-------
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
9-31
-------
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 a Filled in Retrieval Request
The Quick Look Report shown in Figure 9-1 and the Source Data
Report shown in Figure 9-3 were obtained by filling out the Retrieval
Request Form shown in Figure 9-8.
The Quick Look Report shown in Figure 9-1A was obtained by filling
out the Retrieval Request Form shown in Figure 9-8A.
The Milestone Report shown in Figure 9-4 was obtained by filling
out the Retrieval Request Form shown in Figure 9-9.
The Variable Milestone Report shown in Figure 9-4A was obtained by
filling out the Retrieval Request Form shown in Figure 9-9A.
The Questionnaire shown in Figure 9-5 was obtained by filling out
the Retrieval Request Form shown in Figure 9-10.
The Action Summary shown in Figure 9-6 was obtained by filling out
the Retrieval Request Form shown in Figure 9-11.
9-32
-------
COMPLIANCE DATA SYSTEM
Report Request Form
Dota Submitted
Return Report To.
Moil Stop
.Time
lO.ll
I/.
12 45 7 9
••gion lOKoi^Report Fill*
SO Farmal
^lovol^Reporl
I Formal Only
l/.V.
124 7 9 II IS
Data lUm.nl Cond Valu. licit Juillflad)
11.01
i«?./
|l|0|
I ... I |_J L
I ... I |_J L
I . . , I LJ L
I , . , I LJ L
11.01
11.01
I ... I U L
Li_ I U L
I
I_LPJ
n.oi
L. J U L
I ... l U L
I . l LJ L
I ... I U L
i ... i U L
I ... 'I U L
L, L_| LJ L
H.oi I ... I U L
REPORT FORMATS
20
30
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE *
U - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - BLANK OR ZEROS
*Used for multiple values
of a data element
See reverse side for a
list of all CDS data
elements and their
abbreviations.
1 2 4 5 7 S 10 II
13.01 \*T,'A l-S.^'-.gl I ... I L,
124 79 12 14 17 19 22 24 27
REPORT SEQUENCE (d.g.on, Slal«, Ceunly, Source, ara olwayl praunl)
I I
29
32
40
SO 52
70
SO
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
Q2 - DOUBLE SPACED QL
LEVEL CODES (01 CARD)
S - SOURCE ONLY
P - POINT AND SOURCE
A - ALL DATA
C - CRITERIA MATCH ONLY
\4\ Number at
1=1 lublotalllng
FOR QUICK LOOK REPORT ONLY
|4.o|
124
I
79 12 14 17 19 • 22 24 27 29 12 14 17 19 42 44
Enter Data Elements left to right in the same sequence as required on report
The- l«l.moil pail.an ol IKt lino olwoyt inclwdot Slate, County, Satire*. Foinl and
Action Numb.r unltll NOHD It cadad In column 4 through 7
J I ... I I . . .
47 49
I
52
J
54 57 60
With NOHD Only tupproit
FOR MIIES10NE REPORT ONLY
is.ol I . , . I I i . . I I . '. . I I ... I I .
124 79 12 14 17 19 22 24
ROWS COLUMNS COLUMN VALUIS
... I I ... I I ... I
27 29 32 14 1} 39 42 44 47 49 52
UHO 101 VAlUi
' FIGURE 9-8
9-33
S4
57 59
62
-------
COMPLIANCE DATA SYSTEM
Report Request Form
Dole Submitted
Return Report To.
Mail Stop
|0.»l
I 2
4 S
legion
ID Format
.Unt^R..*.!
farmatOHrf
Tlllo
11.01
I I
11,01
11,01
11.01
11,01
|1|OI
11,01
4 I 9 II It
Oala llemenl Cand Value (lall Juilllled)
I ... I |_| I • . • • . • • I
I ... I |_| L
I i . I LJ L
J U
I ... I LJ L
I ... I U L
LLPJ
11,01
IliPj
lipj
1
J LJ l_^
11,01
n.oi
i ... i u L
i ... i U L
I ... I U L
_a_J LJ l_,_a-
I . . . i U L
REPORT FORMATS
12.01 lCjt.1 | . |
12 4 S 7 S 10 11
|3,0|
I 2
, I
J U I , . .
I , , . I _
I ... I LJ | • . .
l ... I LJ i , . .
I . . I U I . . .
.1
si
to
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE *
U - UNEQUAL
C - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - BLANK OR ZEROS
*Used for multiple values
of a data element
See reverse side for a
list of all CDS data
elements and their
abbreviations.
4 79 12 14 17 19
REPORT SEQUENCE (Region, State, Counly, Source, are alwayi preienl)
I ... I I ... I
22 24 27 29 32
40
SO 52
70
10
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
Q2 - DOUBLE SPACED QL
LEVEL CODES (01 CARD)
S - SOURCE ONLY
P - POINT AND SOURCE
A - ALL DATA
C - CRITERIA MATCH ONLY
U Number el
lubtololllng
39 data tlomonlt
FOR QUICK IOOK REPORT ONLY
|4.o| IJvf*.d \uPJA\ \D>T.*C\ Inr.s.d I ... I I ... I I ... I I , , . I I ... I I ... I
121 79 12 14 17 19 22 24 27 29 32 34 37 39 42 44 47 49 SI
Enter Data Elements left to right in the same sequence as required on report
Ih« leltmoil portion ol In. l.ne olwoyi includol Slat*, County. Source Point and
Action Number union NOHO ll codod In column 4 through 7
I ... I ll|
54 5. SO
With NOHD Only Supprail
FOR MILESTONE REPORT ONIV
is.ol I . . . I I ... I
124 79 12 14
ROWS COIUMNS
OAIA DATA
fllMINI IIIMINT
jj I . . . I I ... I I I . . I I ... I I . ,
17 19 22 24 27 29 32 34 37 39
CCIUMN VAIUIS
•INK usio FOI VAIUI "HANK"
Figure" '9-8A
9-33A
jj I ... I I ... I
42 44 47 49 52
I ... I I ... I
54 57 59 62
-------
COMPLIANCE DATA SYSTEM
Report Request Form
Dale Submitted.
Return Report T
Mail Stop
.Time
l°jjj
1 2
\»& i i i/**,*-, .**w
4 S 79
Region Irrtl ftipeil Title
SOrMMtO.1,
*.€,£ f f^A^p-O &.S*Al"'tf'& pit f. If £ r-0~"f (
20 30 40 50 S2
SI (0 70 10
ft! \o*,0>
9 It
4 ; 9 II II
Data llement Cond Value (left Juitlf led )
11,01 wfr.P.C
11.01 1 . .
11.01 1 , .
11.01 | . ,
|1,0| 1
11,01 1 , .
11.01 1 . ,
11,01 1 . ,
|1|0| I , ,
11.01 1 , ,
ll,0| 1 , ,
11 iO| | . .
U, 01 1 . .
11,01 1
|1,0| 1 , ,
n.oi i . .
1' ,01 1 , ,
11,01 1 . .
'.PI 1*1
.III
III
. 1 1 1
I 1 1 1
•Ml
_U U
,l|i
-U U
i i i
.MI
.lii
.MI
i I i
.MI
_i_l U
. 1 1 J
,111
_U U
if. 1
I ,
1 1
, , 1
1 1
1 ....... 1
1 1
1 1
1 .... . 1
1 1
1 1
1 1
1 1
1 1
1 , 1
1 , J
1 . . . . . 1
1 .... , . 1
I I
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE *
U - UNEQUAL
G - EQUAL OR GREATER THAU
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - BLANK OR ZEROS
*Used for multiple values
of a data element
See reverse side for a
list of all CDS data
elements and their
abbreviations.
REPORT FORMATS
|2.0| |/%S| I . I I . I
12 45 I S 10 II
13.01 I . . , I I ...
124 79 12 14 17 19 22 24
REPORT SEQUENCE (Region, State, County, Source. art olwor> proient)
I I
. I I ...
27 29
12
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
Q2 - DOUBLE SPACED QL
LEVEL CODES (01 CARD)
S - SOURCE ONLY
P - POINT AND SOURCE
A - ALL DATA
C - CRITERIA MATCH ONLY
U Number el
lublalalllng
39 dale element!
FOR QUICK IOOX REPORT ONU
|4,0| I ... I I ... I
I 2
. . . I I ... I I ... I I ... I I ... I L
17 19
4 79 12 14 17 19 22 24 27 29 32 34 37 39 42 44
Enter Data Element! left to right in the lame tequence 01 required on report
Ihe lellmeti peilien el 'he lint olwart iniludet Hole. Count, Source Pelnt end
Action Number unlen NOHD li ceded In column 4 through 7
J I ... I I . . .
47 49
SI
I . . . i LJ
54 57 60
With MONO Only Suppretl
FOR MILESTONE REPORT ONIT
15.01 I ... I I ... I L_
124 79 12 14
ROWS COLUMNS
DATA DATA
ItlMINI IIIMENT
L
L
J I
j ._
17 19 22 24 27 29 12 34 37 39 42 44 47 49 52
CCIUMN VAIUIS
SINK uiio FOR VAIUI "SIANK" , i i i
54
57 59
62
' FIGURE 9-9
9-34
-------
COMPLIANCE DATA SYSTEM
Dole Submitted
r
|0,l|
1 2
11.01
1 2
Return Rnpor. T, .,..._
. Moil Slap
lfl/1 1 1 i/***,*-; +»4.tf (\%&tt"S /t-e^ri e^ <.£-|//r«. />/t.^e QA.G
4 S 7 » 20 30 40
6*,**^ » . -J° . »•
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
4 7 9 11 , II
-<*•,»< / &
SO 52
SO
* ' * • . .*
Data Elemont Cend Value (loll Juitlfled)
11)01 | ,.
11.0) | ,
11,01 1 ,
11,01 1 .
|1|0| | ,
11,01 1 .
11,01 | .
11,01 1 .
|1,0| | ,
11.01 I-,
11,01 1 ,
11.01 1
11.01 |
H,0| |_L
U. 0| | ,
|1.0| 1 ,
|1.0| | ,
11.01 I .
.. 1 1 1 1 ....... 1
..III) 1
, , 1 1 1 1 . , 1 . . . . 1
..III), 1
. . 1 1 1 1 . 1
..III! 1
..III! ..... 1
, , 1 1 1 1 1
,, 1 1 1 1 .... . 1
1 1 1 1 ! , 1
..III) 1
. 1 1 1 1 , 1
..III! 1
. 1 1 1 1 . , . 1
..lilt. . . . . J
.,1111 1
, ,-( 1 1 1 1
.Mil ...... 1
, . 1 1 1 1 . 1
REPORT FORMATS
HL°J I/*J3 I . I I . I
12 45 7 S 10 11
13.01 I ... I I ... I LJ
124 79 12 14
17 19
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE *
U - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - BLANK OR ZEROS
*Used for multiple values
of a data element
See reverse side for a
list of all CDS data
elements and their
abbreviations.
I I
22 24
27
I ... I
29 »
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
Q2 - DOUBLE SPACED QL
LEVEL CODES (01 CARD)
S - SOURCE ONLY
P - POINT AND SOURCE
A - ALL DATA
C - CRITERIA MATCH ONLY
REPORT SEQUENCE (legion. State, County, Source, are alwayi pre.ont)
UNumbif el
tublololllng
39 data •lom«nll
FOR QUICK LOOK DEPORT ONLY
|4,0| I ... I I ... I I ... I
. . I I ... I I ... I I ... I I ... I I ... I I ... I
12 14 17 19 • 22 24 27 29 32 34 37 39 42 44 47 49 SI
124 79
Enter Data Elements left to right in the same lequence as required on report
Th« Ivf.fnot. portion ol >h« l.n« alwayt mclwdvt Slat*, County. Sowco. Poml and
Action Numboi unUit NOHO Ii codod In column 4 through 7
U
60
54 S7
With NOHD Only Supproll
FOR MILESTONE REPORT ONLY
is.ol
124 79 12 14 17 19 22 24 27 29 32 34 37 39 42 44 47 49 52
ROW! COlUMNt CCIUMN VAlUfl
« VAIUI ""
54 57 59 62
Figure 9-9A
9-34A
-------
COMPLIANCE DATA SYSTEM
Report Request Form
Dole Submitted
Return Report To.
Moil Stop
.Time
|0.l|
12 4 S
i 7 9
SO formal O*T7
20
...
30
51 60
40
'0
". .",
. 30
4 7 9 II 11
Data llemtnt Cond Valuo (loll JuillMod)
1 1 1 o | iR 77 J
11,01 iP.TV?
11,01 1 , ,
11,01 | .
11 0| I
11,01 | . .
11.01 I .
H.oi i
11.01 1 , ,
|1.0| | . .
11.0! 1
U, 0| 1 , .
n.oi i , .
|1.0| | ,
»/C.| \L\ 1 /.£>«/. 2*. . 1
, 1 1 1 1 , . 1
, 1 1 1 1 , 1
, 1 1 1 1 , 1
.1111 1
. 1 1 1 1 1 1
.1(11 1
, 1 1 1 1 .... . 1
1 1 1 1 , . 1
1 1 1 1 1
.III), 1
1 1 1 1 1
1 1 I 1 1
. 1 1 ! | , ... .1
.III! .1
,'l 1 II , ,1
, 1 1 1 1 . . . . 1
.III!..... , . 1
CONDITION CODES (10 CARD)
M - MUST EQUAL
U - UNEQUAL
G - EQUAL OR GREATER THAN
L — EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - BLANK OR ZEROS
*Used for multiple values
See reverse side for a
list of all CDS data
elements and their
abbreviations.
REPORT FORMATS
|2.0| \QT\ I . I I . I
12 45 78 10 II
124 7
REPORT SEQUENCE
\ I
9 12 14 17 19 22 24
(Region, Slot*, County, Sourco, oro always prasont)
27 29
12
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
Q2 - DOUBLE SPACED QL
LEVEL CODES (01 CARD)
S - SOURCE ONLY
P - POINT AND SOURCE
A - ALL DATA
C - CRITERIA MATCH ONLY
U
Numb.r of
lublatalllng
FOR QUICK IOOK REPORT OMIT
|4.0| I ... I I ... I I ... I I ... I I ... I I ... I I.I.I I ... I I ... I LL
t 2 4 79 12 14 17 19 22 24 27 29 32 34 37 39 42 44 47 49
Enter Data Elements leFl to right in the same sequence as required on report
Iht Ullmail pailian al 'h« lint always in
-------
COMPLIANCE DATA SYSTEM
Dole SubmiMgd
Return Rnport T, __ ____
, Mail Stop
Li. Ql
1 2
11,01
11.01
11,01
LLPJ
|1|0|
11,01
11,01
11,01
|1,0|
LL£I
11,01
I.LOJ
LL°I
11.01
11 O i
1 ' 1 w 1
11.01
ll.OI
H.ei
REPORT
|2,0|
1 2
|3.0|
1 2
REPORT
Rtg.an lavaU
SOfotma
l/l7P*;c51
4 I
}ota El*m*nl
1 . . . 1
1 , . . 1
| . , , 1
1 . . , 1
| . . . 1
1 . . . 1
1 . . . 1
1 , . , 1
I-, . . 1
1 . . . 1
1 . . . 1
1 . , . 1
1 1
1 . . . 1
1 , , .'1
1 . . 1
1 . . . 1
FORMATS
Afi l_l_
45 It
\£,TJ fi\
4 1
SEQUENCE
^(•porl Till*
r»i i*.*.^. ....
9 U II
Cand. Volu. (l»ll Juillllad)
|V| b9 &
1 1 r • i . . , i .
Ill
| 1 | .......
Ill
|ll
111
| 1 1 , .
III,., • . •
III
Ill
L! 1 . ...
Ill
|ll i
III.. .
J L^_J
10 II
20
|
|
|
|
!
|
(
1
|
I
I
|
|
|
|
|
|
I
1
AP
' 30
SI .60
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE *
U - UNEQUAL
G - EQUAL OR GREATER THAR
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
B - BLANK OR ZEROS
*Used for multiple values
of a data element
See reverse side for a
list of all CDS data
elements and their
abbreviations.
. i i • i i >.ii...
40 SO S2
70 .go
9 12 14 17 19 22 24 27 29 32
(lUgian, Slat*, Caunly, Saurc*, ar* alwayt praunt)
FOR QUICK IOOK REPORT ONLY
U.o| I , , . 1 I . . . I I , , . I
1 2
REPORT FORMATS (20 CARD)
QL
SD
AC
QT
MS
Q2
- QUICK LOOK
- SOURCE DATA REPORT
- ACTION SUMMARY
- QUESTIONNAIRE
- MILESTONE
- DOUBLE SPACED QL
LEVEL CODES (01 CARD)
S
P
A
C
U
39
1 ,., 1 1 ... 1 1 ... 1 1 ... 1
4 79 12 14 17 19 22 24 27 29 32 34 37 39
Enter Data Element* left to right in the same sequence at required on rep
Th* Ullmat. portion al III* l,n« alnari mclvdti Slot*, County . Sau'C*. Pain 1 and
At 11 on Nvmb*r unlan NOHO ll cad*d In column 4 ihraugh 7
- SOURCE ONLY
- POINT AND SOURCE
- ALL DATA
- CRITERIA MATCH ONLY
Numbir 0»
-------
9.4 Job Control Language for Using Retrieval Program
The CDS Retrieval Package operates on a Remote Job Entry (RJE) basis
at COMNET. Input must be submitted from a high speed terminal (frequent
and complicated requests might be stored on an ALPHA 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-12. 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 10,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.
9.5 Retrieval Edits Performed by System
The Retrieval Program edits the request cards, 01, 10, 20, 30, and
40, 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.
9-37
-------
AUTHOR TRC
i
1
/
/
/
[/
r
l
2
3
4
/
/
2
*
/
/
/
1
0
4
4
4
/
+
3
P
E
R
4
R
P
T
1
5
1
A
V
EdF
k-
•
•
6
M
•
•
PROGRAM NAME RETRIEVAL JOB CONTROL
7
R
•
S
••
8
1
•
Y
•
9
T
S
10
Y
4
11
0
i
•
1213
JP
EX
5
fh<
•
1
rt
i
14
B
E
15
C
DD
•
•
i
a old a
,_ l
fr
16
4
(
17
a
c
*
it
1<
1f
18|l9J2o|21
WJMR* .
3sP;
t
f
t
ie
HP
IP
u
n
11
ie:
IP'
ie
22
•
1
V
t'(
• «
'f
RI
23
•
1
n
a
T
TF
24
•
1
rr
Pip
F
[E
25
)
i
in
n
[G
/A
26
i
iH
>r
i i
IR]
« •
27
i
±s
ni
un
S
01
2129
.
u
Is
mti
be
H
S
pr
r;
^
OON
30
E
Yi
rR<
31
R
ii
)L
32
Til
•
Al
Nc
sc
A]
T"l
Tl
Tl
Pi
d
33
P
1
l
s
le
1
Pft
e
e
"If
va
34
>t-
D
re
>1
ct
re
•j-
ic
>r
^
In
35
0'
i
:r:
!C
.01
:r:
fit
1U(
n
iOl
IS,
36
•jl
*
e\
i<
e
Ii
n<
i]<-
a
37
Y
T
a!
3839
card
IN
s
n lea
adds
a.
c t
e
01
01
'e
8
1n
se
ma
p
nu
:d
m
DU
^ ,
Le
t
f
1 L
40
1,
E
it
i <
1Y
it
:t:
>0
•PI
:oi
41
c
=
he
re
be
hi
or
Cf
01
Bl
42
pr
1
ve
i
u
ve
r(
t
43
In
a
eq
se
o
0
i
iff
f).
44
la
i
ii
1.
ie
:a
>
<^
TASK NUMBER
45
•
H
e<
2
d
7
•
46
ti
i
(
if
u:
rl
•
47
tl
"I
ai
c
re
PC
48
e
t
d
Pt
d
•
49
:a
>
Eo
Lo
Lf
•
SO
•d
:wi
ia!
a
51
nt
. •
52
-
y
53
•
54
55
56
vO
I
W
GO
-------
TABLE 9-1
RETRIEVAL PACKAGE EDITS
Card
Type
01
10
20
30
40
50
ALL
Item Checked
Level
Region Number
Number of 01
Cards
Data Element
Condition
Value
Number of 10
Cards
REPORT FORMAT
(LEVEL ON 01
CARD)
Bomber 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
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, STTE,
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, QR, MS
Up to three reports are
fva-tlahle from one retrieval
2) If SD requested, LEVEL
on 01 card required
1
List on Input Form
Total 40
List on Input Form
Total length (Including one
blank between each item)
112 with NOHD; 110 without! NP
(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
(2) SD FORMAT request
ignored
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
HD
(1) QL FORMAT Request
ignored
(2) QL FORMAT Assumed
(if only toe 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
9-39
-------
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-13
shows a typical Retrieval Edit Report.
9-40
-------
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.
9-41
-------
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 - SD TYPE DELETED,
LEVEL MISSING"
"WARNING - LEVEL FOR SD
FORMAT ONLY"
"FATAL-DUPLICATE FORMAT
(20) CARD"
"FATAL - DUPLICATE SEQUENCE
(30) CARD"
"FATAL - SEQUENCE KEY TOO LONG"
No card type 20 was entered.
card type is required.
This
"FATAL - INVALID MS DATA
ELEMENT COMBO"
"FATAL - REPEAT AND POINT OP.
ACTION ON QL"
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 of S, P, A, or C was
not entered on card type 01. This
code is required for the SD report
format.
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 nay specify only souico
level data together with repeating
pollutant data on the Quick look.
9-42
-------
I
05/25/76
RETRIEVAL EDIT REPORT
COMPLIANCE DATA SYSTEM
PACE 001
RFCION 05
LEVEL
TITLE NEW SOURCE PERFORMANCE MILESTONE
j SELECTION CRITERIA
| DATA ELEMENT
EMISSION POINT NUMBER
P/P COPE
"REPORT
*STATE
*EMI=SION POINT NUMBER
*ACTION NOMBE.R
I MILES'1
CONDITION
VALUE
ERRORS
MUST EQUAL
MUST EQUAL
OOO
MILESTONE REPORT ROWS DATA ELEMENT IS CMST
ER5QRS™DETeCTED - CONTINUING WITH RETfTlEVAL
COLUMNS DATA ELEMENT IS STTE
VO
I
V- --------
r~
J'O
9
FIGURE 9-13
RETRIEVAL EDIT REPORT
-------
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 IGf 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.
10-1
-------
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.
10-2
-------
A
e
(r
0,
01
01
01
Ol
01
01
01
01
01
01
01
01
01
Ol
01
Ol
Ol
Ol
01
Ol
01
Ol
01
01
Ol
Ol
01
5
T
>9
r
07
071
c
o
"jj
?
0265
0425
07J0478
O7O565
07
07
07
07
20'
201
2O
2Q
20
2d
2O
2O
20
2O
20
20
3705
3725
LI 55
1505
3027
3045
3277
3445
3495
3547
3595
3645
3885
39O7
3935
L065
20J1125
2CJhl83
2OJ1205
20J325
22D187
27J3369
224274
Ol|22tt291
O1J221798
Olt2igl21
0130
Ol
Ol
01
Ol
Ol
Ol
Ol
01
3O
30
30
30
^*i//vry /***«* ft
' 580RQCKINGHAM 121
>6405TRAFFQRD 121
>660SULLIVAN 121
)060BRISTOL 120
)14QKENT 120
)200NEWPORT 120
)320PROVIDENCE 120
)380WASHINGTON 120
>020ADDISON 159
)100BENNINGTON 221
\
)180
)200
0147J!>24d
Ol?47£>26q
O l'i47p28ci
01,47p36o'
Ol47p38q
O147
0147
O147
0147
)420
>5OO
>58CJ
CALEDONIA 221
;HITTENDEN 159
ISSEX 221
rRANKLIN 159
iRAND ISLE 159
-AMOILLE 221
GRANGE 221
ORLEANS 221
JUTLAND 159
WASHINGTON 221
WINDKAM 22 i
)62C|VINDSOR 221
/»
*
M
2.
043
042
042
041
041
111
1O7
107
111
111
1O7
#
t
**.
3
042
111
. . -
... ..
FIGURE 10-1
COUNTY CODE TABLE
10-3
-------
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 "BB"
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.
10-4
-------
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.
10-5
-------
02006M fc'ANTZ ENGINEER
O2O07G MARC TANTE ENGINEER
0201^1 TRICHON ENGINEER
O2021R CELLAMARE ENGINEER
02023V PITRIJZZELLO ENGINEER
! O2053PUCCI ENGINEER
02068D STONE ENGINEER
O2101A SQLPETER ENGINEER
021O2P k'AHN ENGINEER
02-=>03B TQRNICK ENGINEER
OQG
2050 «ANTELLA RNGINFF.R
ENG ENGINEER
FIGURE 10-2
SAMPLE PERSONNEL TABLE
10-6
-------
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 wHlch 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
f
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. It was obtaineu from
COMNET under the name CN.EPAFCS.A026. ISAM.TABLE. Users should document
any table changes on this figure.
10-7
-------
'. .040 1 or.
R
O*oior
R
040 I Of
R
040 IOC
R
O4OIOO
R
O401OC
R
O4O1OC
R
O4O1OO
R
O4O1OC
R
04OIOC
F
040 ioc
R
04O10C
R
040 IOC
R
040 tOC
I.EBT
1 R
040 IOC
OOO1OC
R
040 IOC
R
! 0401 Or
R
040 1 or
F
| 040 I or
R
04 o tor
R
O4O.KX
• 04OIOI
K
R
040 tor
R
R
0*oiOr
R
04O t or
R
0*01 or
R
O4Olor
61
i=r
-r
34
=:c
-jr.
-jr.
57
EC
1C
EC
It
-f
12
14
EC
15
17
EC
f=
EC
51
rr
5'
5«
EC
5C
rr
Ff
57
5=
F.r
SC
El-
6r
EI-
67
F.r
f-.a
Ef
=.UJ3 .CONTROL. PU>
3RD OO460
PURCHASE EC'UIP
1RD 00461
-iRD OO462
END ClONSTR
rINAi_ COMPL
:OMPLAINT RECVC
=TTE INS^ECTIOh
3RD OO466
^lOLAT OBSERVEC
=T SOURCE TEST
3RD OO468
aMB AIR TEST
^DMIN IS HEAR INC
3RD OO47O
3RD OO471
5.T LEGAL ACTIC^
3RD OO472
^LAN REVIEW
1 EPA026 TABl
3RD 00473
'VEGISTRATION
"iRD OO474
3BATE PROG REP1
3RD 00475
1TMER ACTION
3RD 00476
=.TATE NQV
tRO 00477
114 LETTER SENT
EPA SOURCE TES1
3RD 004J3O
VISIB EMIS EVAL
3RD 00431
Mi'iTC OF VIOLfiTh
3RD 004J32
ABATE ORDER IS^
T'RD O04S3
CIV/CRIM ACTIC^
ORD O04S-4
REVIEW SOURC SC
TiRD OO4S35
CONF W/ OPERAT
ORO 004S6
VERIFY SOURC Ai
ORD OO487
REPORT TO EPA
ORD 004:33
(^E-ATE PROG REPT
ORD OO4i3*>
CASE CLOSED
^UBMISJION OF FINAL CONTROL PLAN
BINDING COMMITMENT TO PURCHASE CONTROL EQUIPMENT
INITIATION ~OF 'ON~TiTE CONSTRUCTION/PROCESS "CHANGE*
:£>MPLE.TION OF ON_SITE CCINSJRUCTICIN/FPOC.ESS CHANGE __. ._
FINAL COMPLIANCE
IOMPLAINT RECEIVED
STATE INSPECTION
VIOLATION OBSERVED
STATE SOURCE TEST
AMBIENT AIR TEST
ADMINISTRATIVE HEARING
=.TATE ENFORCEMENT ACTION
5.TATE LEGAL ACTION
:-LAN REVIEW
i 05/26/76
REGISTRATION
ABATEMENT PROGRESS REPORT
CITHER ACTIOWSEE COMMENTS BELOW)
STATE NOV
114 LETTER SENT
EPA INSPECTION
EPA SOURCE TEST
VISIBLE EMISSIONS EVALUATION
MOT ICE OF VIOLATION
ABATEMENT ORDER ISSUED
7IVIL/CRIMINAL ACTION
REVIEW SOURCE SUBMISSION
CONFERENCE WITH OPERATOR
VERIFY SOURCE ACTION
REPORT TO EPA
ABATEMENT PROGRESS REPORT TO EPA
CASE O ri^Fn TTTritor- in o
SAMPLE ACTION TABLE
in_a
-------
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 Data Data
Columns Length Element Type
1-2 2 Record-Identifier Always "DD"
3-4 2 Region Numeric, 01-10
5-6 2 Results Code Numeric
7-8 2 Filler Always "00"
9-23 15 Results Description Alphanumeric
24-80 57 Filler Must be blanks
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.
10-9
-------
FIEC
01
Ft=T
o:
ORD 00389
ACTION ACHIEVED
ORD OOS90
06OIOCIO7NOT AC HE WED
RECORD 008-=>l
OfeOlOClOACTION RESCHED
FIGURE 10-4
SAMPLE RESULTS CODE TABLE
10-10
-------
10.1.5 Other Table Lookup Procedures
For both editting and report 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
State Compliance Status
Federal Facility Code SIP Code
Active/Passive Code Pollutant Code
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.
10-11
-------
COMMON DATA
FOR ALL RECORDS
i 1 1 1 1 1 1 i i it
I?
2, «
>»
v»
COUNTY I
III4K
Ul
a
8
Id
U
K
1
1 1
»•«• i
Ul
e
e
u
•ON NOI19V
ITJioii
NOIS&IW3
£
t-
3
«
1 1 1 1 1 i i 1 1
11< I i > 1 >0
COMPLIANCE DATA SYSTEM
MASTER FILE LAYOUT
1 1 I II 1 111 111 I 111 1111 11 I 1111 I 1111 11 11 111 111 I I 111 11111 111 I I 111III 1111 I 11 I' 11 11 I I • I 11
ii»iii'4<44<«4t5>i»>si)iii«it«ttitrri>rrrrrTiiiiiiiiiifi9iiii>iii']44i444i<44i>si>i>s>iti«4i4i«7H«H34itTHOI»l4J>TI10m45«FHelH4|mtOi|J4»»>HOIH4i»ri»OIH4H7HO»1145tm01H4St7l«OIH434fHOII14»t;i»eiH4|«fH»
SOURCE
CODE
•STREET
ADDRESS
'C I TY
ZIP
CODE
, STATE |
REGISTRATION
NUMBER
all
STAFF
NAME
RDE4 RDESi RDE6
COUNTY
NAME
I
=
b sgS; »DM
H £ id,
o|- (FILLER
it
U
POLLUTANT 1
POLLUTANT 2
POLLUTANT 3
POLLUTANT 4
POLLUTANT 5
POLLUTAN1 6
POLLUTANT 7
POLLUTANT 8
POLLUTANT 9
POLLUTANT 10
FILLER
sec
CODE
STATE
REGULATION
NUMBER
P ROC ESS,
DE SCR IPT I ON
FILLER
.8 Si,
ACTION
DESCRIPTION
(SHORT)
STAFF
NAME
FILLER
ACT ION DE SCR I P TION
(LONG)
RESULTS
DESCRIPTION
FILLER
jr.,1
5s
COMMENT
FILLER
111111111111111111111111111111111111111111111111111 • 1111.. 11111 1111111111111 • • i
lllflllIIIII||]|||I4444444444StlSll»ill<«t»«t«4777r777777tl>lllllllfttTtt«tlt«CeeC»IC«IIIIIIIIIIIll|ll>llIllJlIl||II44<4444444S»S>llll>!tll»4tl««-'''77T>7ri
I:i4>«>lteill41t>lt0lll41t7lt011l4l»7l«0ll>4>t7lt«lll4lt7lt01»4l»7ltlll>4,5l7lftriftlll4]«7ll0ll>4>l7l<0lll4l«7l«ll|14lt7l«0ll|4l>1lt.'7)««7ri»
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 ALPHA data sets which are used as input transactions must be
kept for a minimum of one month from the~d~ate on which they
were used as input to CDS. Users should keep a log of all
ALPHA data sets, marking the creationjlate, 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:
10-12
-------
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.
10-13
-------
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.
10-14
-------
11.0 NATIONAL GUIDANCE MATERIAL
All national guidance material should be filed in this section
as it is made available from the Division of Stationary Source Enforce-
ment.
Note:
The information on pages 11*2 thru llr-7, CDS Input Preparation
via HYLRUR. no longer applies. Due to the lack of similar capabilites
at COMNET, CDS input preparation via ALPHA cannot be implemented at
this time. However, development of this capability is pending and it
will be made available to the user when developed.
11-1
-------
11.1 CDS Input Preparation via WYLBUR
WYLBUR is a powerful tool which can be used in conjunction with
the CDS retrieval to create input punch card formats for the CDS Edit.
WYLBUR should not be used to prepare new facilities or highly change-
able data as input to CDS.
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 should 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, 1974.
o Change the Compliance Status for all sources which meet
certain retrieval 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 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 convert-
ed into input punch card formats. The 40 Card used for print-
line formatting should contain NOHD, REGN, SITE, CNTY, SRCE,
and any other applicable data elements which will be needed
for each input transaction.
11-2
-------
B) Execute the retrieval by Issuing the following command:
RUN HOLD UNNUMBERED
This command will enable the user to manipulate the output
from the retrieval. Users must note the job number return-
ed by WYLBUR.
C) Collect and save a data set which can be used as a Load &
Go for this retrieval and other retrievals containing similar
formats. The following WYLBUR commands should be used in
this Load & Go:
Command Purpose
1. PAUSE Allows the user to fetch
the retrieval output
2. SET TERSE Shortens WYLBUR responses
3. DELETE NOT "Og" 1/2 IN ALL Eliminates all heading and
non-data lines in the
Quick Look
4. SET LENGTH = 133 Eliminates unnecessary
messages when using the
CHANGE command.
5. CHANGE ' ' TO" IN ALL Eliminates all spaces on
NOLIST the remaining Quick Look •
6. CHANGE 80/80 to 'C1 IN ALL Generates an Update Code in
NO LIST Column 80
7. SET LENGTH = 80 Creates an 80 column record.
8. LIST 1/15 Lists the first few data
lines.
9. LIST L Lists the last line.
10. SAVE CDS. INPUT ON TS0016 Saves the formated data
set for backup.
The above WYLBUR commands will transform the print layout of the
Quick Look report into card formats usable as input to CDS. All Region,
("
State, County, Source, Point, and Action Numbers are guaranteed to match
masterfile records.
11-3
-------
D) Once the retrieval has been executed, use the saved Load & Go
Data set as follows:
1. LOAD USER.LOAD ON TS0016 GO LIST
The PAUSE command in the Load & Go will allow the user
type in the following command:
FETCH JOBNUMBER DDNAME=PRINTOUT
As soon as this fetch command is issued, all the other
commands in the Load & Go are executed.
2. User must now create the card type for all records with
the following command:
CHANGE 19/19 TO '7' IN ALL NOLIST
3. Replace with spaces any unnecessary data columns.
4. Add new data as appropriate. To add a Date Achieved,
use the following command:
CHANGE 55/60 TO '06076' IN ALL NOLIST
5. Insert or copy the appropriate EDIT JCL to the beginning
of this data set.
6. Insert two slashes as the last record of this data set.
7. Execute the CDS Edit with the following command:
RUN REMOTE 37 UNNUMBERED
WYLBUR will return a Job number for the Edit Program. Once
the Edit has been executed, the Edit Report must be examined
to make sure that all input has been prepared properly.
The following checklist gives some of the advantages and disadvan-
tages of using WYLBUR for input data preparation:
Advantages Disadvantages
Saves input data preparation
coding time for uniform changes.
Provides "instant input" with no
need to wait for keypunching.
WYLBUR commands, especially the
CHANGE command, are powerful tools
for data manipulation.
Input data must be re-
trievable from the CDS
masterfile.
WYLBUR sessions cost about
$30/hour; this is much more
than either coding or key-
punching costs for variable
data.
Users must possess basic
WYLBUR knowledge to perform
needed data manipulation tasks.
11-4
-------
HP
'RFADY-TO-OSI '
Figure 11-1
COLLECTING RETRIEVAL TEXT
OSI/UYLRI'R
VJFLP.OMF TO
IMITI AI.S?
Rl
051
OC/n7/7f) 7:56:33
Anr.oiJMT?
KFYWORP? 6JMM
TFRHNAL
rof'F-WP
l.
2.
3.
*t.
5.
6.
7.
8.
q.
10.
11.
12.
COf 'M-A.MP
7
7
7
7
7
7
7
7
7
7
7
?
7
7
7
nil
r
//p.xc j
// PXPC
oh (a026
cdsrtv6
//rtv.sysOOS Hd *
01 Of>
10 dtsc *
10 dtsc 1
10 dtac h
20 ql
30 dtsc
UO nohd r
//
***
run hold
net ' ons
OH0176
070176
pr;n stte
unnumhpr
6 rtv tost'
hut not
- 7/1/7F
cnty srcp ptno pnun
010 IS YOUR ,IOR MIJMRFR.
rOf'MAMP ? logoff rlp?ir
FHITIMP TlfF'- O.OIt SFCOMPS
WYI Rl!R FXrPS = 1(7
M! ! TFN F.XPPS = R5
'RFSOURPF Tlf'F = h. hi
F!..APf>PP TIMF = 00:08
nr SPSS I ON
03
11-5
-------
Figure 11-2
PREPARING LOAD & GO
he
•RFADY-TO-OSI '
OSI/WYI.RIIR 3(4 OR/07/7F. 11:15:3U A.M.
WF.LCOMF TO OSI AtJP TMF 1 Pf 370/158 'F1 SYST'
INITIALS?
ACCOUNT? £
KFYWORn? *
TFRMINAL?
OPF^MAfin ?
1. ?
2. ?
3. ?
U. ?
5. ?
6. ?
7. ?
.8. ?
9. ?
10. ?
COMMAND ?
1.
ALTFRS ?
1.
ALTFRS ?
COMMAND ?
"MKLOAP" f
COMMAND ?
COMMAND ?
1.
2.
3.
'» .
5.
fi.
7.
8.
3.
COMMAND ?
exe
all '• _ - -T-^-JC
col 1 ect i"4~
puase
set terse
Helete not 'OB' 1/2 'nail
set lpnr-th = 133
chanpe ' ' to '' in all nol'st
change 80/80 to ' c ' in all nol 1st
set length = 80
1 1st 1/15
1 1st 1
***
nodify 1
PL' ASP
rpause
PA USe
save mkloaH on tsoOl?. jS/?«^^
JAVPn ON TS0012
use nkloaH on tso012 clear
1
PALISF
SFT TFRSP
DPI.PTF NOT 'OR1 1/2 IN ALL
SFT I.FNPTH = 133
PMAMCF ' ' TO !l If ALL NO LIST
CHAMC-P 80/80 TO 'r» IM ALL NO|. 1ST
SFT I.FMCTM = 80
LIST 1/15
LIST L
HAVr A NICC r
11-6
-------
Figure 11-3
USING RETRIEVAL OUTPUT FOR LOAD & GO
on tso012 fro l»st
r1r1n? PC) FTP r«"T "OF1 I/? I" All' '*
-> ?rT l.cfirT"1 = 131
-> r"ANrp ' ij"11 IM M.I MOIIST
-> r"AfTF RO/80 TO 'r1 If All HOI 1ST""
-> SfT ITMRTH = PO
-> LIST 1/15
10. ofiiooRhnonfimnnninn?
11. nfi373n?nn«;nfiTnnnn]n28nnoniPR • r
is. nr>it5?2°oo5in3onnniP8 r
-> I IST i.
i-iii. nnusT>nonsininnno?pR
l°/2n to '7 ' In all nollst
55/fiO to '060776' !n all nollst
? insert 1,7,3
" 1. ' //pxr joh (fl02fi/pxr, !,<«), 'rrts test1
' ?. ? //
3. ? //pHlt.rardsin riH R
? Insert
1U2. ? //
? 1 1/12
1. //FXr .inn O02R,Fyr,l/q)/'rns TFST"
3. //Fr>IT.P»nnsl»' no p*
10. f»61°08l»00000300ni07 OP077R
11. nP373020050830000l7 Ofin77fi
17. nfia505An0510U000017 ORP77B
? rorMfy 3
3. //miT.r.ApnsiP n" fi*
*|.TFRS ? r*
3. //FniT.rAP^SIM r>n *
AI.TFPS ?
? 1 UO/1
ll»0. OPU53finnn50
1U2. //
? run remote 37 unnunhprefl
U36 IS YOUR .10" HUMPFP.
/'t-/> ci.fi
-------
11.2 Formal Reporting
On a quarterly basis, each region must submit certain reports to
the Program Reporting Division. Several of these reporting require-
ments 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.
At the present, the specific output units/activity indicators linked
from CDS to FRS are:
AIR OUTPUT 3
o To date number of identified point sources in final compliance
with emission regulations.
o To date number of identified point sources out of compliance
with final emission regulations.
o To date number of identified point sources of unknown compliance
with final emission regulations.
o To date number of identified point sources in compliance with
scheduled increments.
o To date number of identified point sources overdue in meeting
increments of progress in a schedule.
o To date number of identified point sources of unknown status
with scheduled increments.
AIR OUTPUT 5
o Number of operating sources subject to NSPS determined to be in
compliance.
o Number of operating sources subject to NSPS of unknown compliance.
o Number of operating sources subject to NSPS in violation.
o Number of NSPS sources for which construction has commenced.
AIR OUTPUT 10
o Number of sources subject to NESHAPS.
o Number of NESHAPS sources in compliance with standards or waivers.
11-8
-------
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 re-
gion must submit the job control described in Figure 11-4. 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.
11- 9
-------
AUTHOR TRC
1
/
/
/
/
2
/
/
/
*
3
E
E
4
P
O
5
A
F
6
i
7
i
,
8
i
9
10
t
11
12
j
E
13
0
X
14
B
E
15
c
16
<
Wh
i
a
n
17
a
C
•
er
i
a
n
18
a
D
e:
i
a
19
a
S
a
20
a
F
PROGRAM NAME CDS/FORMAL REPORTING SYSTEM
.
21
R
22
i
s
23
i
n
1
24
i
n
S 1
25
)
:he
26
f
u
27
'
se
28
u
r'
29
s
5
is the user's
1s a two digit
are 01 through
30
E.
31
*
i
32
ni
33
i
ti
34
0
al«
35
'
36
,-
37
T
38
i
account number
region code. Valid
10.
39
M
40
E
41
:
42
1
values
t
43
44
45
TASK NUMBER
46
47
48
49
50
51
52
53
CH
O
W
I
O
70
CO
-------
11.3 CDS Coding Guidance
Appendix B of the EPA Air Program Operation Guidance
for FY 78 defines terms, outputs, and activity indicators
associated with program planning and reports to head-
quarters. Section 5A of Appendix B relates directly to CDS
and defines minimal requirements for the encoding of CDS.
This memo is intended to assist you in implementing Section
5A by explaining these requirements as they relate to three
program areas. This memo also conveys additional instruc-
tions relating to coding industrial boilers.
The specific areas addressed below are: coding CDS for
sources in non-attainment AQCRs, coding continuous moni-
toring information, coding sources subject to new source
review (NSR) and prevention of significant deterioration
(PSD) requirements, and coding industrial boiler information
It is recommended that this memo, as well as Appendix B, be
circulated to personnel involved in air enforcement, air
program liaison with State agencies, and to CDS personnel.
In most regions, states are currently submitting
information needed to meet the requirements of Appendix
B. However, depending on current working agreements
with States, some regions may find it necessary to acquire
different or additional data from their State agencies. If
at all possible, these arrangements should be part of the
work plans now under preparation by States and regional
offices.
Detailed explanations and instructions for coding
CDS in four areas are included. These areas are described
briefly below.
ll-ll
-------
Coding sources in non-attainment areas
CDS "card 3" provides a group of new data fields
which resulted from modification to the basic CDS pro-
gram. Card 3 is to be completed for any source impacting
non-attainment in a non-attainment AQCR (and for any other
source for which the region wishes to enter data). Card 3
provides the capability of retrieving compliance status
information for several pollutants at the facility level.
It also has the capability to store data such as the facility
production rate (capacity), although entry of this rate data
is not required. Card 3 can be of significant use in stra-
tegy development for non-attainment AQCRs. It should be
noted that to code card 3, regions will need access to
compliance status information by pollutant (information you
may not be receiving from your states at this time). See
11.3.1 for additional information.
Coding related to continuous monitoring
Continuous monitoring is currently required for several
NSPS source categories and will be required for SIP sources
by FY 79. Currently very few monitors have been installed
and there is virtually no information in CDS regarding
source self-monitoring. 11.3.2 establishes standard
action types to be used in tracking installation of continu-
ous monitors and recording results of excess emission reports.
Coding related to new source review(NSR)
Procedures for coding NSR related activities into CDS
have been standardized to some extent. All 100-TPY (allow-
able) sources, NSPS sources and sources incurring an enforce-
ment action while undergoing NSR must be entered into CDS
via Air Program Code 7, New Source Review; all sources
subject to PSD requirements must be entered via Air Program
Code 6. Sources subject to both should be entered one for
each program. Application review actions at the State(s)
level need be tracked only for those programs delegated to
the state for the source in question and only if the source
has been monitored or audited by EPA. See 11.3.3 for further
details.
Coding power plants and industrial boilers
Fossil fuel-fired steam generators have long been
identified as significant sources of air pollution.
These sources include public utility steam-generating
11-12
-------
facilities, coal-fired industrial boilers (CFIB), and
major fuel-burning installations (MFBI) and power
plants affected by gas curtailment programs or prohibition
orders. Coding instructions to enhance the quality,
reliability, and utility of CDS data for such sources are
included in 11.3.4.
The five key coding requirements for fossil fuel-fired
steam generators are:
1. 8-digit source classification codes (SCC) must be
encoded for all CFIB and MFBI;
2. Process descriptions must be encoded for all steam-
generator emission points;
3. Process descriptions of all boilers must be identified
by the same ID number as the source uses;
4. Flagging symbols must be entered for CFIB and MFIB
to identify ranges of boiler capacity;
5. Individual boiler capacity by emission point must
be entered for all sources.
General cod ing guidance
Page 266 of the program planning document outlines the
minimal data required for every source in CDS. For the
19 source categories listed in Table 2 of the guidance
package (p.268-269), additional data required includes
process description, SCC code, and emission category.
Hence, for these 19 source categories, process level informa-
tion will be needed, and obtaining this information, particu-
larly the SCC code, may require modification of current
information agreements with States. Except where explicit
coding instructions are issued for a source category (such
as that issued for iron and steel industry), these process
level requirements apply only to sources in violation or of
unknown compliance status.
Although guidance for coding NSR activities and continu-
ous monitoring information will not be resource-intensive,
the non-attainment AQCR encoding and process level coding for
19 major source categories could be. In order to minimize
the impact on regional office personnel, DSSE contract funds
have been made available for initial implementation of this
coding guidance. Regions interested in assistance should
contact their technical liaison at DSSE or Franklin Smith at
(FTS) 755-0103.
11-13
-------
Coding of all federal enforcement and surveillance
into CDS is required by current guidance. Specifically
Federal inspections, stack test, V.E. observations,
NOV's, orders, criminal/civil actions, and Section 114
letters must be recorded in CDS. Regions should also
code past actions into the system, although the
priority is less than for coding current actions. Con-
tract assistance is available to assist in coding these
past actions.
Please refer to Table 3 (p. 270 of the operational
guidance package for FY 78) for additional actions which
are to be tracked in CDS.
For consistent reporting throughout the Fiscal Year,
it generally will be necessary to implement these coding
instructions by October 1, 1977. Coding of past enforcement
and surveillance actions is not subject to this critical
time constraint.
11-14
-------
11.3.1.
Coding Card 3
Background
In order to support the FY 78 program plan requirements
to develop adequate SIPs for TSP, SO-, HC, CO, and NO in
non-attainment areas, the CDS system must carry a numoer of
new data elements which indicate the compliance status of a
facility for each of the pollutants produced by the facility.
Since these new data elements relate to source-level infor-
mation on the CDS masterfile, they will be input to CDS by a
new card type associated with source level data and they
will be stored on the CDS masterfile next to the existing
source record. Card 3, the new card type, will replace
AIR2 and RDEl non-attainment functions.
Data Field
Source Pollutant Code
Length
2
Pollutant Compliance Status 1
Pollutant Emission Category 1
Impacted AQCR Indicator 1
Air Quality Maintenance Area
Indicator
Pollutant Loading
Valid Value
Same as for PLUT
Same as for CMST
Same as for ECAT
Blank for attainment
"N" for non-attainment
Blank for not an AQNA
"Y" if the source is
in AQMA for the
pollutant
Numeric
Because a facility can produce numerous pollutants, the
input punch card has room for three sets of pollutant data,
and multiple punch cards are needed for entering data for
those facilities producing more than three different pollu-
tants. The CDS masterfile will store all pollutant compliance
data on one masterfile record; up to 10 sets of pollutant
data will fit on one masterfile record. In addition to
pollutant related data, several other data elements, such as
plant capacity and more regional data elements, have been
added to the system.
With these new data elements users are able to produce
Milestone Reports and Quick Look Reports which meet all of
the reporting requirements related to compliance status by
pollutant.
11-15
-------
Input Procedures
Card Type 3, which is not being used by CDS at the
present, will be designated as the Pollutant Card. This
card contains the following elements:
For a new card 3, users roust code columns 1-19 with the
key record identifier data, and they must code "C" in
column 80, the Update Code. For each pollutant information
being added to CDS, users must code the two-position Pollu-
tant Code and whatever other data are available for that
pollutant. Pollutant compliance must be coded for each
applicable pollutant. The pollutant compliance status
should represent the worst-case compliance of all the
emission points producing that particular pollutant. The
Air Quality Control Region Indicator must be blank if this
pollutant from the facility does not impact the non-attain-
ment AQCR standards; it must be "N" if the facility does
impact the emission standards for this pollutant in a
non-attainment AQCR or if the impact of the facility is
unknown. Pollutant emission category must be coded for each
applicable pollutant. This field must represent the poten-
tial uncontrolled emissions for the pollutant from the
entire facility. The Air Quality Maintenance Area Indicator
should show whether the area in which the facility is
located has been designated as a maintenance area for that
pollutant. AQMA's are identified in the Federal Register
(40 CFR 52). There is a separate subpart in Part 52 for
each State. AQMA's are listed in these subparts under the
heading "Maintenance of national standards". If a pollutant
loading factor is used, it should be a numeric value repre-
senting actual tons per year.
If a facility produces several pollutants, compliance
information for the second and third pollutants may be
coded in columns 37-40 and 49-52 in the same manner as
for the first pollutant in column 25-28.
Facility capacity and new regional data elements may
also be input on card 3 (optional). Facility capacity
indicates the total output capacity of a source;
appropriate units are set forth on page A-32H of the CDS
User's Guide.
Users should note that pollutant data on card 3
may be entered many times since it is a repeating data
element. However, Facility Capacity and the regional
data elements 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 a different
Facility Capacity is coded on multiple card 3's for a
facility, only the value on the last card will be placed
on the CDS masterfile by the Update.
11-16
-------
Finally, it should be emphasized that the only required
coding of card 3 is for those sources which affect (contri-
bute to) the non-attainment status of an AQCR. This
requirement includes both major (Class A) and minor (Class
B) sources and will assist us in evaluating not only the
causes of non-attainment for a specific pollutant in an
area but also the progress we are making toward attainment.
Sources meeting this criterion should have all regulated
pollutants they emit coded, not merely the non-attainment
pollutant(s). This will allow the region to evaluate all
aspects of the facilities compliance problems (at the
facility level) and assist in prioritizing enforcement
actions. However, unregulated pollutants or pollutants
not emitted by the facility should not be entered. Finally,
please note that although card 3 coding is required only
for SIP sources, regions may find the available data fields
useful for NSPS and NESHAPS sources, as well.
Add it ion a1 Info r ma t i on
Additional information relating to changing pollutant
compliance data, deleting compliance data, and retrieving
data can be found in the 6/77 CDS User's Guide.
11-17
-------
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
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
Table 11-1
Card 3 Format
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
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Numeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
Length
2
2
1
1
1
5
2
1
1
1
5
2
1
1
1
5
7
7
2
2
1
3
Justified
Right
00
iH
I
Right
Right
-------
11.3.2.
CODING RELATED TO CONTINUOUS MONITORING
Background
Continuous monitoring (CM) is currently required for
several NSPS source categories (e.g., nitric acid plants).
Additional CM regulations applying to existing SIP sources
are expected to be promulgated in FY 78. As the name
implies, CM regulations require source owners to monitor
their own emissions continuously. They are also required to
report results periodically in an Excess Emissions Report
(EER). The EER is required even if there are no excess
emissions for the reporting period.
In the event there are excess emissions, there still
could be circumstances which would convince EPA that enforce-
ment action would be inappropriate. For lack of a better
term, these excess emissions will be called "unenforceable
excess emissions".
Coding Procedures
CDS will be coded for the following CM action types:
1« Notification of CM system demonstration date.
Use action type Ml. Code dates as appropriate. The
initial inspection to verify a properly functioning
system should be encoded as all other inspections
(see #2, below).
2. Continuous monitoring system inspection. Use action
action type M2. Code dates as appropriate. Code
results as follows:
- CM equipment properly operated = MC
- CM equipment not properly operated = MV
State of CM equipment not determined = MU
3. EER submission. Use action type M3. Code dates,
as appropriate. Code results as follows:
Enforceable excess emissions not found = MC
Enforceable excess emissions found = MV
State of compliance not determined = MU
(Enforceable excess emissions are excess emissions which are
significant and not beyond the ability of the source owner/
operator to prevent).
11-19
-------
4. CM system test results. (Required currently by
60.13 (c).) Use action type M4. Code date
schedule as 30 days after performance test is
required. Code results as follows.
- CM equipment meets requirements = MC
- CM equipment does not meet requirements = MV
- Status of CM equipment not determined = MU
5. To differentiate between SIP and NSPS sources, use
the Air Program Code (column 65, card 2).
11-20
-------
11.3.3.
CODING RELATED TO NEW SOURCE REVIEW AND PSD
Program Background
Several air pollution control regulations require
preconstruction review and approval of new sources. These
include:
1. Section 51.18-Review of new sources and modifications
(subject to state implementation plans). In most cases the
Federal function is one of oversight activity. The offset
policy is an interpretative ruling of Section 51.18.
2. Section 52.21-Signifleant deterioration of air quality
(19 major source categories emitting either PM or SO-).
This section defines allowable levels of air quality deterio-
ration (in ug/m ) resulting from new source construction
in counties which did not pervasively exceed NAAQS during
1974. BACT is required for all sources in the 19 categories
(attached). Although delegable to States, this task is
generally a Federal responsibility at this time.
Background For Coding
For facilities subject to New Source Review (NSR)
requirements, the facility and associated processes should
be entered into CDS if:
(a) the subject process (or subject facility) will
be capable of emitting 100 tons per year of any
regulated pollutant, or
(b) the subject process (or subject facility) will
be required to meet NSPS requirements, or
(c) a State or Federal enforcement action occurs in
the course of the NSR of the subject process (or
subject facility).
As with NSPS facilities, each subject process should be
entered and maintained at the point level in CDS with a
definitive process description, SCC code, emission category,
and compliance code. Since the NSR (and PSD) program can
logically be broken into two distinct functions, the permit
application review and permit enforcement, the actions
listed below for NSR that relate to permit enforcement (LI
throught L8) should definitely be tracked. However, since
EPA will only monitor or audit selected permits reviewed by
States, the actions involving state application review
process (SI through S8) need be tracked only for these
11-21
-------
selected sources. If a permit is granted and specific
conditions are set that must be enforced, COS should contain
a description in a comments field of the permit conditions,
and if appropriate, new action types (e.g., progress reports
due) should be established by calling the National COS Data
Bank Coordinator at (FTS)-755-0103.
All facilities and processes subject to Prevention of
Significant Deterioration (PSD) requirements must be entered
and maintained in CDS regardless of size. The general coding
requirements for PSD sources are the same as for NSR sources.
At a minimum, the actions listed below should be tracked in
CDS where applicable. Where PSD has been delegated, only
those applications monitored or audited by EPA should be
tracked at the state level.
Since it is possible that any one facility may be
subject to the requirements of several programs, such as
SIP, NSR, and NSPS, it is important to ensure that the
same facility is entered into CDS once for each of these
programs, each time with the appropriate Air Program Code.
Since most of the information remains the same from program
to program, it should require less effort to enter the data
at one sitting via duplication. The CDS User's Manual and
operating guidance for CDS detail how the source coding
should be conducted. The result is that the same facility
will occur several times in CDS. However, under each faci-
lity, only the points (processes) which are subject to a
particular program should be coded.
The action types and descriptions listed below are
suggestions. If you have already established a system
for coding NSR or PSD actions, please list your action
type(s) and descript ion(s) which correspond to those of HQ on
a copy of the action type page and return it to HQ as soon
as possible. If you do not yet have a system, we prefer
that you use the one listed below
Specific Coding Instructions
Data Element NSR Entry PSD Entry
Source Number (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.
11-22
-------
Air Program Code 7 6
Air Program Status (P, C, and 0 will all apply; even
a 100- TPY source may escape
detection and begin construction
and even operation prior to
agency analysis).
11-23
-------
Figure 11-5 Action Types for PSD and NSR
Action Type Action Description
SI
S2
S3
S4
S5
S6
S7
S8
Rl
R2
R3
R4
R5
R6
R7*
R8
Tl
T2
T3
T4
T5
T6
T7
T8
LI
L2
L3
L4
L5
L6
L7
L8
Results Code
01
02
03
Application Received by State
Additional Info. Requested
by State
Application to State Complete
Preliminary Determination by
State
Public Notice by State
Public Hearing by State
Final Determination by State
Inspection by State
Application Received by EPA
Additional Info. Requested
by EPA
Application to EPA Complete
Preliminary Determination by
EPA
Public Notice by EPA
Public Hearing by EPA
Final Determination by EPA
Inspection by EPA
Offset Determination by State
BACT Determination by State
LAER Determination by State
RACT Determination by State
Offset Determination by EPA
BACT Determination by EPA
LAER Determination by EPA
RACT Determination by EPA
NOV Issued by State
Order Issued by State
Civil/Criminal Action by State
(Reserved)
NOV Issued by EPA
Order Issued by EPA
Civil/Criminal Action by EPA
(Reserved)
Results Code Description
Action Achieved
Action Not Achieved
Action Rescheduled
*A11 processes with a final determination by EPA
approving a permit to operate should be duplicated
(with appropriate changes) and added to the SIP file.
11-24
-------
Figure 11-6
Sources Subject to PSD Requirements
(i) Fossil-Fuel Steam Electric Plants of more
than 1000 million B.T.U. per hour heat input.
(ii) Coal Cleaning Plants.
(iii) Kraft Pulp Mills.
(iv) Portland Cement Plants.
(v) Primary Zinc Smelters.
(vi) Iron and Steel Mills.
(vii) Primary Aluminum Ore Reduction Plants.
(viii) Primary Copper Smelters.
(ix) Municipal Incinerators capable of charging
more than 250 tons of refuse per 24 hour day
(x) Sulfuric Acid Plants.
('xi) Petroleum Refineries.
(xii) Lime Plants.
(xiii) Phosphate Rock Processing Plants
(xiv) By-Product Coke Oven Batteries.
(xv) Sulfur Recovery Plants.
(xvi) Carbon Black Plants (furnace process).
(xvii) Primary Lead Smelters.
(xviii) Fuel Conversion Plants.
(xix) Ferroalloy production facilities commencing
construction after October 5, 1975.
11-25
-------
11.3.4
CODING INSTRUCTIONS FOR POWER PLANTS AND INDUSTRIAL BOILERS
Background
Fossil fuel-fired steam generators have long been
identified as significant sources of air pollution.
However, in the past, EPA has focused principally on
public utility steam generating facilities with capacities
of 25 megawatts (MW) or greater. These sources are identi-
fied and updated in the Compliance Data System (CDS) on a
routine facility-by-facility basis. Retrievals of power
plant data can be accomplished by selecting the proper
Standard Industrial Classification (SIC) code. While
compliance information on entire sources is generally
up-to-date such data on a boiler-by-boiler basis are much
less reliable.
Another significant fossil fuel-fired source of air
pollution is coal-fired industrial boilers (CFIB). This
source is identified as any coal-fired boiler with heat
input capacity of 35 million British Thermal Units per hour
(MMBTUH) or greater, excluding public utility steam generating
plants (SIC 4911). CFIB are of particular concern
because they make up nearly 17% of the total coal consumption
by coal-fired stationary sources in the USA, including the
largest power plants and coke ovens. Additionally, it has
been estimated that 8% of TSP and 11% of SO emissions
result from coal-fired industrial and commercial boilers
(Emission Reduction Study, DSSE,1976). Some CFIB are
currently entered in CDS. However, they fall into numerous
SIC categories, making a convenient retrieval by this
selection criterion impossible.
As a result of national energy conservation programs,
special emphasis on fossil fuel-fired major fuel-burning
installations (MFBI) and power plants affected by gas
curtailment and the Energy Supply and Environmental
Coordination Act (ESECA) activities is also necessary.
Additional guidance relating to coding sources subject to
gas curtailments or ESECA actions will be issued in the
near future.
Coding Procedures
Special care in coding fossil fuel-fired steam genera-
tors (public utility power plants and CFIB) can enhance the
quality, reliability, and utility of data in CDS. Much of
the required information for existing CFIB can be found in
the York Report on CFIB or in the report's background
documentation. To achieve this objective, the following
activities will be necessary:
11-26
-------
1. 8 - digit SCC codes must be entered in CDS for MFBI
and CFIB steam-generator sources
Use columns 20-27 on card 5 for this purpose. A
partial listing of SCC codes is included as Table 11-2.
This table provides the SCC ID and SCC category
names for those sources for which emission factors are
available. Please note that four levels of source
identification (Roman numerals I, II, III, IV) are used.
These four levels are sufficient to define a general
category, and subcategories within the general category.
The subcategories define classifications as to fuels,
industrial processes, products, equipment types used, etc.
2. Process description must be completed in CDS for
each steam-generator emission point.
Use SCC level III and IV terminology as process
descriptors. This will be coded in columns 50-74 on
card 5 for each emission point for CFIB, power plants,
and MFBI. For instance, if a source burned dry, pul-
verized bituminous coal in boiler number 5, the
process description on card 5 might be coded as
"PULV DRY BIT COAL-BLR#5."
3. Process decription must identify steam generating
units (boilers) entered in CDS by the same ID
number as the source uses.
This instruction is intended to rectify identification
problems which have occurred when sources (power plants,
CFIB, and MFBI) do not operate sequentially numbered
steam generation units. For instance, if a source identifies
its boilers as 1, 3 and 7, they must similarly be identified
in the process description of card 5.
4. Flagging symbols must be entered into NEXP (columns
28-29, card 5) to identify
capacity for CFIB and MFBI
28-29,^ card 5) to identify ranges of boiler heat input
At present, for those sources identified by SCC code,
a retrieval can be performed only for wide ranges of
boiler heat input capacity. However, more exact source
size data are often needed for such purposes as calculating
emissions, identifying boiler capacity by emission point,
and estimating coal demand. Because of the lack of data
field space on CDS coding sheets, the exact boiler size
can only be accommodated in the emission point comments of
card 6 (see Activity #5 below). However, retrieval by
comment level data cannot be executed nor are such data
11-27
-------
available on Quick Look Reports. Therefore, flagging
symbols narrowing SCC-defined boiler capacity ranges
have been established for encoding into NEXP (columns
28-29, card 5) as follows:
SCC-defined Flagging symbol Flagging symbol
capacity (to be inserted capacity range
range (in in col. 28-29, (in MMBTUH)
MMBTUH) card 5)
<10 Bl <10
10-100 B2 10-34
B3 35-64
B4 65-100
>100 B5 101-250
B6 251-650
B7 651-1000
B8 >1000
5. Individual boiler heat input capacity per
emission point must be entered in CDS for all
steam generator sources.
Use columns 20-79 of card 6. Please enter the
exact boiler heat input capacity for each emission point,
identified by the source's boiler ID number. Boiler
capacity should be identified in terms of MW for
public utility steam generators and in MMBTUH for CFIB
and MFBI.
11-28
-------
I
to
Table 11- 2
• SOURCE CLASSIFICATION CODES (partial list)
NATIONAL EMISSIONS DATA SYSTEM (NEDS)
SOURCE CLASSIFICATION CODE (SCC) REPORT
SCC 10
••••••
I II III IV I
I oi 001 oi EITCOMB BOJLER
i 01 ooi 02 EXTCOMB HOILER
01 001 03 EXTCQMB 80ILEX
01 001 0* EXTCOMB BOlLl.il
01 001 OS EXTCOMB BOtlEx
01 001 06 EITCOMB HOILER
01 001 99 EITCOMB BOILER
01 002 01 EXTCOMB BOILER
01 002 02 IXTC'IMB BOILER
01 002 03 EXTCOMB BOILEX
01 002 0* EXTCOMB BOlLEM
01 002 OS EXTCnnB BOIlEN
01 00? 06 EXTCOMB 90ILEH
01 002 OT EXTCOMB BOILER
01 002 OB EITCOMB MOILEx
oi 002 09 EATCOMB HOILER
oi 002 10 E»TCOMB BOILER
01 002 II EXTCOMB BOILER
01 002 12 EXTCOMB tfOILCR
01 002 99 EXTCOMB BOILEN
01 003 01 EXTCOMB BOILER
01 003 02 EXTCOMB BOILER
01 003 03 EXTC1MB BOILEN
01 003 0* EXTLUMB BOILER
01 003 OS EXTCOMB BOILER
01 OOJ 06 EXTCQMB BOILER
01 003 OT FXTCOMB bOILER
01 003 Oh EXTCOMB bOILEX
01 OOJ 09 EXTCOMB BOILEM
01 ooj 10 F.ITCI>M(I HOILER
01 OOJ II FXTCDMB BOILLM
oi 003 12 EXTCQNB BOILER
01 OOJ 13 FATCOXb BOILLR
01 001 I* exTCIMB'MOlLLR
01 OOJ IS EXTCOMB BOILEX
01 004 01 EATC'HB HOILLR
01 004 02 tATCPMb ROILIN
01 00* 03 EATCnMB dOKEM
01 OOi 01 EXTCOMB HOILER
01 OO-l 02 FXlCliMII HOlLl"
01 00k 03 EXTCnMb •WILE*
01 00t> 01 EXTCOMB HOILER
01 OOe 02 EATCQMFj rtOILEM
01 006 03 EXTCOMB BOlLtX
01 007 01 EXTCOMB MOILER
oi oo i 02 EXTCOMB BOILER
01 OOf 03 E»tCOMfl MOlLEi*
01 OOo 01 EtTC'lMh HOILER
01 Oil 02 F.«TCOM6 hOlLLM
01 Oil 01 FAlCCiNB MILE*
SCC CATEGORY NAMES .
••••••••••••••CM*
II HI
IELECTMIC OENEMATNIANTMXACITC COAL
IELECTHIC GENEdATNIANTM'ACI'E COAL
IELEC1NIC GENENATNIANTHXACITg COAL
IELEC1RIC (itNERATNIANTMHACITE COAL
IE.LEC1RIC GENEHATNIANTHVACITE COAL
•ELECTRIC GCNEXATNIANTHRACITE COAL
IELEC1HIC blNEHATNItNTHXACITE COAL
IELEC1NIC OENEHATNIOITUNINOUS COAL
ICLECIMIC GENEMATNIBITUMINOUS COAL
IELECTMIC OENEHATNIHITUMINOUS COAL
ICLECTNIC GENElUTNIllttMINOUS COAL
IELECTNIC GENCMATNIBITUHINOUS COAL
IELECTXIC GENEVA TNI 81 TUMI NOUS COAL
IELECTNIC GENEMATNIDITUMINOUS COAL
IELECTHIC GENEHATNmlTUXINOUS COAL
IELECTHIC UENE-UTNIblTUMlNOUS COAL
IELECIXIC GENEWATNIBITu'INOUS COAL
IELECTH C GENEKATNIAITUMINOUS COAL
IELEC1NJC GENERA TN IK I TU»I NOUS COAL •
lELECTHtC toENEHATNtdtTUHlNOUS COAL
IELECTHIC GENERATNIl IGNITE
(ELECTRIC GENEHATNILIGNITE
IELECTNIC btNEHATNIl IGNITE
IELECTMIC GENCfctTNILlGNITE
(ELtCTHlC GENEMATNlLlGMTE
IELECTMIC GENEHATNILIGNITE
IELFCTXIC GENEHATNlLtGNITE
IELECTHIC GENEMATNILIONITE
(ELECTRIC GENERATNJI.IGNITC
IELECTXIC GENEfcATNlCIGKtTE
IELECTXIC liENEHATNILlGNITt
IELECTNIC GENEHATNUIGNITE
(ELECTRIC 6LNEHATNILIONITE
IELECT4IC GENERATNILIGNITE
IELECTXIC OENERATNILIGNITE
IELECMIC GENERATNIUESIDUAL OIL
IELECMC Gl*iEHATN|iiESI9UAL OIL
IELECT-UC (lENEPATNIkEStlUAL ML
IUECMIC GENEUATNintSTlLLATC OIL
IlLECfi-IC GlNE'ATNIOISTILLATE OIL
IELECT-IC .itNEiiATNIOISTlLlATE OIL
IELECTMIC GENEHATNINATUUAL PAS
IELECTHIC 3CNEHATNIN«Tu"AL GAS
lELECInlC OENERATNIHATU'AL 'US
IELECTXIC UENERATNIi>ROCESS GAS
IELECTMIC GFNEkATNIiiROCtSS fiA
IELECTHIC GLNEHATNIi-AOCcSS «iA5
IELFCTXIC GLNCUATNICOKE
ICICCIHIC AtfJCXATNIIIAGASSC
ItLECTiMC (iENCPArNI4AGASfE
IV UNITS
IMOOMMBTU PUL VI 101 TONS BUM«EO
O100NMHTU STO»ERSITONS BUMNEO
HO-lOOMM8fU POL VDI TONS bUxnED
IIO-100MM8TU STOXRITONS bUxNEO
KIOMMBTU PULVUIO ITONi BUHHCO
K10MNBTU STOKLX ITONi RUXNEO
IOTHEN/NOT CLASIFOITONS OUMNEH
OlOOMNriTU PULV.CTITONS bUHnEO
OIOOMMHTU PULVnNYITONS BUMnEO
OICOHMdTU CYCLONE 1 TONS BUh'MEO
OIOOMMHTU SPOiTKRITON< dUkriEO
OIOOMM4TU/HH uFSKlTONS bUMXEO
IIO-IOOMMdTU PULlTlTONS UUxuEO
IIO-IOONMBTU PULOr ITONi BUMNtO
I10-100MMBTU OFSTKITONS BUMNtO
IIO-1COMMBTU UFSTXITONS BUHNEO
KIOMMBTU OFSTUKLRITONS riUHNEO
K10MNHTU UFSTOKERITONS BUxuEO
KIOMMBTU PULV-OHYITONS HUXKEO
IOTMEH/NOT CLASIFOITONS BUHNEO
OlOOMMiTU PULWET ITONi BUHNEO
OIOOXMHTU PULVOHY ITONi BURnED
OIOOMMHTU CTCLONEITONS BUMoED
OlOOMMriTU OF STKRITONi bUMNCO
OIOOMMHTU UF STXRITONS bU««EO
OlOOMMnTU SCDSlKRITONS bUMSEO
HO-100MM8TU OYPULITONS riU*iEO
IIO-IOOMMBTU klRULITONS JIUM^ED
IIO-IOO«MATU OFS1KITONS BUHNEO
HO*100XMaTU -U» STK 1 TONi -bUUkEO
110-100— BTUS»r,iTKITONS BU.HEO
KIOMMBTU PULV UXYITONS BUMNEO
KIOMHbTU OF STOXR ITON» HUxNtO
KIOMMBTU UF STOlRITONS BUMNEO
KIOMMBTU SPDSTOXRITONS BUxNED
OlOOMMRTU/hR GtNLIlOOOGALLUNS BUHNEO
IIO-IOOMMATU/MHGNLIIOOCGALLOXS BURNED
KIOKMBTU/HX GINL II0004ALLONS BUHNEO
OIOOMMHTU/HX bENLIIOOOGALL^NS HUHNEO
1 1 0-1 OOMMQTU/HMiiNL 1 1 OOor.ALL»NS HUHNlO
KIOMHBTU/H. GcNL IIOOOFALL^NS HUNTED
OlOONMMTU/XK (MILLION CUBIC FEET BURNtO
IIO-IOOIMBTU/HH (MILLION cubic FEET nuHneu
KIOXMRIU/H* IMILLION CUBIC FEET BURNLO
OlOONMHTU/iH (MILLION CUBIC FEET BUHNCU
I10-IOO"M8TU/H« (MILLION CUBIC FIET VUHMtO
I«|O»MHTU/MH (MILLION CUHIC FEET UUMNLD
OlflOMH-TU/nx (TONS DUNKED
HO-lOOfHBTU/HK ITONi ilUNtEO
|<|V*MHTU/^4 (TONS IIUHNCD
-------
I
LU
O
NATIONAL EMISSIONS DATA SYSTEM (NEDS)
SOURCE CLASSIFICATION CODE (SCO REPORT
sec_io
i 11
01
01
01
01
01
01
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
It
02
02
02
02
02
02
02
02
W"»»
III
012
012
012
999
999
999
001
001
001
001
001
001
001
001
002
002
002
002
002
002
002
002
002
002
002
002
002
002
002
003
003
001
003
003
003
001
003
003
003
OOJ
001
003
003
003
003
00*
00»
004
OOb
DOS
'lIV.
01
02
03
97
9B
99
01
02
03
04
05
06
07
99
01
02
03
04
Ob
06
07
OB
09
10
11
12
13
14
99
01
02
03
04
OS
06
OT
04
09
10
11
12
13
14
IS
16
01
02
03
01
02
• 1 I
| |
EXTCONB
EXTCOHB
EXTCOHB
EXTCOMB
EXTCUMB
EXTCOMB
LXTCOMB
FXTCOMB
EXTCOMB
EXTCOMg
EXTCOHB
EXTCOMB
EXTCOMB
EXTCUMB
EXTCOMB
EXTCOMB
EXTCOMB
CXTCOMB
EkICQHB
EXTCOMB
EXTCOMB
EXTCOMb
EXTCOMB
EXTCOMB
EXTCOMb
EXTCOMB
fcXTCONB
EkTCOMB
EXTCOMb
EXTCOMB
EXTCOMB
EXTCOMB
EXTCOMb
EXTCOMB
EXTCOMb
EXTCOMB
EXTCOMB
EXTCOMB
tXTCOMB
EXTCUMb
tXTCUMb
EXTCOMB
EXTCOMb
EXTCOMb
EXTCOMB
LXTCOMB
tXTCriMB
tXTCQMb
EXTC'IMb
EXTCOMB
r
I..--
BOILER
HOILER
BOILEH
BOILER
BOILEM
BOILER
BOILER
aOILEH
BOILER
BOILER
BOILER
BOILER
HOILEK
BOIItM
dOILER
BOILER
BOUER
BOILEH
BOILER
BOILER
bOILEM
BOILEH
BOILER
BOILEH
BOILER
BOILEH
riOILEH
BOILLR
BOILER
BOILLM
BOILER
BOILEH
BOILER
BOILER
BOILER
BOILEM
BOILEH
BOILEH
BOILER
bUILER
BOILEM
BOILER
BOILEM
BOILER
bOILLR
rtOILER
HOILER
BOILEM
oOlLEM
SCO CATEGORY NAMES
II
1
III
{V UNITS
IELECTMIC GENEHATNISOLID tfASTE/COAL
(ELECTRIC liENEHATNISOLlO HASTE/COAL
(ELECTRIC GENERA TNI SOL 10 HASTE/COAL
IELECTMIC GENENATNinTHFR/NOT
(ELECIMIC GENEhA TNI OTHER/NOT
(ELECTRIC GtNENATNIOTNER NOT
(INDUSTRIAL
(INDUSTRIAL
1 INDUSTRIAL
1 INDUSTRIAL
1 INDUSTRIAL
1 INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
1 INOUSTHlAL
(INDUSTRIAL
1 INDUSTRIAL
1 INDUSTRIAL
IINDUSTMIAL
• (INDUSTRIAL |
II NOUS TRIAL
i INDUSTRIAL • '
(INDUSTRIAL
(INDUSTRIAL
1 INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
1 INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
i INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
1 INOUSTHlAL
1 INDUSTRIAL
1 INOUSTHlAL
(INDUSTRIAL
i INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(ANTHRACITE
(ANTHRACITE
lANThUAGITE
(ANTHRACITE
IANTHRACME
(ANTHRACITE
lANTh.ACITE
(ANTHRACITE
IBITURINOUS
(BITUMINOUS
IHITUHINOUS
(BITUMINOUS
IH|Tu«|NOJS
(BITUMINOUS
IrilTUHINOUS
(BITUMINOUS
(BITUMINOUS
IBITURINOUS
IfUTURlNOUS
IHITU'INOUS
ltHTU»|NOJS
1 BITUMINOUS
ltITU«INOUS
ILIGNITE
II IGNITE
ILIGNITE
ILIGNITE
ILIGNITE
ILIGNITE
(LIGNITE
ILIGNITE
ILIGNITE
ILIGNITE
ILIGNITE
(LIGNITE
IlIGNITE •'
IL1GMTF
ILIGNITE
ILIGNITE
IMOOMHMU/MM ITONS
110-IOOMNDTU/HR ITONS
KIONHBTU/MR ITONS
bURNED
BURNED
BURNED
CLXSIFOISPECIFY IN HENAHKINILLION CUBIC FEET BURNFD
CLASIFOISPECIFY IN ftCMAMKIIOOO
CLASIFOISPECIFY IN MEMAKKITONS
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
IBIS I DUAL OIL
IRESIOtiAL OIL
1 RESIDUAL OIL
(OISTILLATE
IUISTILLATE
OIL
OIL
IMOOMM8TU/HH cut VI TONS
!>100«IOOMMHTU PULVHETITONS
I>IOOMHHTU »ULVOkV|TONS
IMOOMNMTU CYCLONE ITONS
IOOOMMRTU SPOSIXHITONS
IIO-100MMBTU OFStKITONS
IIO-100MM8TU UFSTKITONS
IIO-IOOMMBTU POL* T ITONS
IIO-IOOMHBTU PULOYITONS
1 10-lOOMNBTuSPuSIIC 1 TONS
M10HMBTU OFO STKMITONS
KlOMHbTU UFO STXRITONS
M10MMBTU PULV DRY ITONS
IclOMNBTU SPO STXRITONS
KIOHMBTu HANOFIREITONS
(OTHER/NOT CLASIFOITONS
mOOMMnTU PULVtfETITONS
I>IOOMMHTU UULVDMY ITONS
mOONMHTU CYCLONE (TONS
(>100MNtTU OFSTKH ITONS
IMOOHN4TU UFSTKR ITONS
OlOONMitTU SPOSTXRITONS
I10-100MNBTU OtPUL ITONS
IIU-100<4MBTU MTMULITONS
ilO-IOOM4RTU OFSTKITONS
IIO-lOOMMaTU UFSTKITONS
IIO-lOOMMBTUSPuSTKIIONS
HtOMMHTU PULV ORYITONS
KlOMNblU OFSTO«« (TONS
KIOMMbTU UFSTUKM ITONi
I100MH!llU/nh 11000
lld-lOOMMBTU/HS 11000
KIOMMBTU/HR 11000
IMOtMPrilU/MH 11000
II. 100MMBTU/MR 11000
GALLON
BUKNEO
BUMNEO
BURNED
BUHNEO
BUXrtED
BURNED
BURNED
BURNED
BUHNED
BURNED
BUH-.EO
BURNED
BURNED
BUMNEO
BURNED
BURNED
BUMNEO
BUKNEO
BUHNED
BURNED
BURNED
BUMNEO
BURNED
BURNED
BURRED
bUMI.EO
BUHi«EO
BURNED
BURNED
BUMNEO
BUHNEO
BURNED
BUHNEO
BURNED
BUKNEO
bUMNEO
bUNNtO
bURNk.0
BURNED
BURNED
GALLONS
GALLONS
GALLONS
bALLONS
GALLONS
ILIOUIDI BURNED
(SOLID)
1
BURNED
BUMNED
BURNED
BUHNED
bUMNEO
r
-------
NATIONAL EMISSIONS DATA SYSTEM (NEDS)
SOURCE CLASSIFICATION CODE (SCC) REPORT
SCC 10
••o«*»
I II III IV
02 005 03
02 006 01
02 006 n
02 006 03
02 oor oi
02 007 02
02 DOT 03
02 OOa 02
02 008 03
02 009 02
02 004 03
02 010 02
02 010 03
02 Oil 02
02 Oil 03
02 999 9T
02 999 -98
02 999 99
OJ 001 OS
03 001 06
03 001 07
03 001 06
03 001 09
03 001 10
03 001 99
03 002 OS
03 002 06
03 002 07
03 002 08
03 002 09
03 002 10
01 002 II
03 002 12
03 002 13
03 002 M
03 002 9V
03 003 05
OJ 003 06
01 003 07
03 003 06
0] 003 09
03 003 10
OJ 00J II
03 003 12
03 003 13
OJ 003 I*
03 00* 01
0} 004 02
OJ 00* 03
OJ 00% 01
SCC CATEGORY NAMES
EXTCONBT
EXTCOHB
EXTCOMB
CXTCOMB
CXTCON8
EXTCONb
EXTCOMB
EITCONB
EXTCOMB
EXTCOMB
EXICONB
EXTCOMB
EXTCOMB
EXTCciMtt
EXTCOMB
EXTCOHB
EXTCOMB
EXTCOMB
EXTCOMB
EXTCONB
EXTCOMB
EXTCOMB
EXTCOMB
EXTCQMB
CXTCOMB
EXTCONB
EXTCONB
EXTCQMB
EXTCOMB
EKTCOMB
EXTCOMB
EXTCOHB
CXTCOMB
EXTCOMB
EHTC1MB
EXTCONB
riTCQNB
EXTCiIMB
CXTCOMB
CXTCOMB
CXTCHNR
EXTCOMB,
CXTCOMB
EXTCOMB
EXTCOMB
EXTCONB
EltCOMB
E'TC'IMB
t
BOILER
BOILER
BOILER
BOIL Erf
BOILER
BOILER
DOILER
80ILEK
BOILER
dOlLER
BOILER
dOILEK
BOILER
BOILER
BOILEM
BOILEN
BOILER
BOILER
BOILEM
BOILER
MOILER
BOILER
BOILER
BOILER
BOILER
BOILER
bOUEN
BOILER
BOILER
dOILfcH
BOILEM
40ILER
dOUlH
BOILER
HOILLH
NOIUM
HlllLl*
noil I*
HOILE"
10ILIP
HUILEH
aOlLER
HOIlER
BOILEN
HOILCN
NOII t»
-OlLth
BOILER
II
IINDUSTMIAL
IINOUSTHIAL
in
(DISTILLATE OIL
(NATURAL OAS
I NATURAL OAS
(NATURAL 8AS
(PROCESS GAS
(PROCESS GAS
(PROCESS GAS
ICOKF
(COKE
1*000
1*000
IINOU&TUIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
I INDUSTRIAL
i INDUSTRIAL
IINOUSTHIAL
IINDUSTMIAL
IINOUSTHIAL
•INDUSTRIAL
IINDUSTMIAL
IINOUSTMIAL
(INDUSTRIAL
I INDUSTRIAL
IINOUSTMIAL
ICUNMEMCL-INSTUTNLIANTM4ACITE CO»L
ICOMNExCL-INSTUTNLKNTMaACITE COAL
ICONMEHCL-INSTUTNLIANTriKAClTE COAL
ICOMMEMCL-INSTUTNLKNTMWtCITE COAL
ICOMMEMCL-INSTUTNLONTHI-ACITE COAL
ICOMMEMCL-INSTUTNLIANTNtfACITE COAL
ICOMMERCL-INSTUTNLIANTMUACITC COAL
ICOMMErfCL-INSTUTNLIDITUMINOUS COAL
ICONNtHCL-INSTUTNL I BITUMINOUS COAL
I CONNEMCL-INSTUTNL i H i TU«INOUS COAL
ICOMMEMCL-INSTUTM. i BITUMINOUS COAL
ICONMEHCL-INSTUTNLIHITUINOUS COAL
ICOMMCKCL-INSTU'NLIXITUMINOJS COAL
ICOMNtNCL-lVSruTNLIHITUxINOUS COAL
ICOMNEHCL-INSTUT>iLILIGN|TC
ICUMMExCL-INSTUTNL (LIGNITE
ICOMMEfCL-I'iSTUTNLILIGNI If
ICONMErfCL-INSTttTULlLl&NITC
IV
KIOMMBTU/HH
OIOONNBTU/MM
IIO-IOOMNBTU/HK
KIOMMBTU/MH
IMOONNHTU/HW
I10-100MHBTU/MU
KIOMM8TU/MR
I10-100MNBTU/MN
KIOMM8TU/HR
IHOOD BASTE BOILCRITONS BURNED
UNITS
11000 GALLONS BURNED
(MILLION CUBIC FEET BURNED
(MILLION CUBIC FEET RURNtO
(MILLION CUBIC FEET BURNED
(MILLION CUBIC FEET BURNED
(MILLION CUBIC FEET BURNED
(MILLION CUBIC FEET BURNED
(TONS BUMNEO
(TONS BUrtnEO
(SMALL HANOFIRE
ILIO PETROLEUM OASI10-100MMBTU/NH
ILIO PETROLEUM GASKlONMBTU/Mrf
IRAGASSE IIO-lOOMHBTU/Mi*
(BAGASSE KIOMNBIU/Mh
(TONS BURNED
IIOOOGALLONS BURNED
IIOOOGALLONS BURNED
I TONS BURNED
(TONS BURNED
IOTMEH/NO^CLASIFDISPECIFY IN RENARKIMILLION CUBIC FEET BURNED
(OTHER/NOT! CLASIFOISPECIFV IN REMAPRIIOOO GALLON BURNED (LUUID)
ICOMNE-CL-INSTUTNL ILIGNITE
ICUMMCtiCL-INSruTNL (LIGNITE
ICOMNfMCL-INSTUTNLILIGNITC
I COMMtRCL-INSTUINl (LIGNITE
ICOMhENCL-INSrutNLlLlGNITt
IOTHEi« NOTJ CLASIFOISPECIFV IN HEMARKITONS BURNED ISOLIOI
I10-100MMBTU PbLfTITONS BURNED
I10-100-H8TU PULDYITONS BURNED
IIO-100MMBTUSPDSTKITONS BUHNEO
K10MMBTU PULVI2EDITONS BUMNEO
KIOMNBTU STOKER I TONS BURNED
K10MMHTU SPOSTOHRITONS BUMNEO
IOTMER/NOT CLASIFUITONS BUKNEO
110-IOOMMBTU PULlTITONS BUNNED
iio-iooMMBTu PULDYITONS BU-NEO
110-IOOMMBTU OFSTRITONS BUHNEO
I10-I004MBTU UFSTKITONS BUHhEO
I10-100«M8TUSPDSTK|TONS MUwNEO
IIO-100MMRTU H4NFRITONS BUMNEO
KIOMN8TU Or STOKER I TONS bUNNEO
IclOMNBTU UFSTOKERITONS BUKNEO
KIONMBTU SPOSTOKRITONS HUKNEO
KIOHMBTU MANDFIAEITONS BURNED
I OTHER/NOT CLASIFOITOMS BU^NCO
IIO-JOO«HBTU PULiTITONS HUMNCD
llU-IOOHMATU PULOTITONS BUNKED
IIOrlOOMM4TU OFSTKITONS BUNKED
IIO-lOOMMbTU UFSTKITONS BUitNEO
IIO>IOO«MBTUSPUSTKITONS BUH«EO
KIOMHBTU PULV*ONV|TONS bUMNEO
KlbHMHTU OrSTUKERHONS BUrtsED
KIOMMHTU UrSTonERITONS BU4KEO
K10NHRTU SPOSTOKRITONS BUMlEU
ICOM«-CL-|NMUTWLI-«5rjU»l
OIL --•
OIL v
OIL '
«10Mri0TU/Hi«
11000 6ALLON& BUMNEO
11000 OALlONs BUUNEO
11000 bALLON* bUUNEO
11000 GALLON* bUMNEO
-------
NATIONAL EMISSIONS DATA SYSTEM (NEDS)
SOURCE CLASSIFICATION CODE (SCC) REPORT
I
CO
to
scc to
••••••
I II III IV
01 OOS 02
01 OOS 03
OJ 006 01
03 00k 02
03 006 03
03 OOS 03
03 010 02
03 010 03
03 999 97
03 999 98
03 999 99
01 001 01
01 002 01
01 003 01
01 999 97
01 499 98
02 001 01
02 001 02
04 002 01
02 004 02
02 003 01
02 00* 01
02 999 97
02 999 98
03 001 01
03 999 47
03 999 98
0* 001 01
01 001 01
01 001 99
01 002 01
01 002 02
01 003 01
01 003 02
01 003 03
01 003 99
01 00* 01
01 004 99
01 OOS 01
01 OOS 02
01 OOS 03
01 OOS 0*
01 OOS OS
01 OOS 99
01 006 01
01 006 99
01 007 01
01 001 99
01 000 01
01 OOb 02
EXTCOJia MILCH
CXTCUMB riOlLlR
EXTCUNB HOILE4
EXTCOH& tfOiLCR
EXTCONB 40ILER
CXTCONB 80ILCH
EXICOMl BOILER
EX7COM8 BOILER
EXTCONB BOILER
EXTCUMB BOILER
EXTCONB BOILER
SCC CATCGOMV NAMCS
••••••••••••••••o«
II III
ICONMENCL-INSTUTNl.inlSTILI.ltE
ICONNEilCL-IMSTUTNLIOISTILLATE
ICOXNCPCL-INSTUTNLINATU4AL GAS
ICOMMCHCL-lNSTbTNLINAIUilAL »AS
ICQNMEMCL>INSTUTNIINATU>AL <•*$
ICOHNEiCL-INSTUTNLI"000
IV
I10-100NMBTU/HM
K10NNBTU/HM
OlOOMHhlU/HN
(10-IOOMMBTU/HK
I<10NMBTU/HK
KlOHMBTU/nU
UNITS
11000 bALLONS BURNED
11000 GALLONS BUBNEO
tHiLiioN CUBIC FEET BURNED
(MILLION CUBIC FEET. HURNIO
IMILLION CUBIC fUl BUNNtO
(TON* BUHNEO
IIOOC GALLON!, BURKED
11000 GALLONS BURNED
ICOHMErfCL-INSTuTNLILIO »ET«OLEU« flASIlO-lOflMMBTU/MJ
ICOMNERCL-INSTUTNLILIO PFTHULEUN GASK10MNUTU/HH
ICONMEKCL-INSTUTNLinTHEn/KOT CLAS1FOISPECIFY IN REMAUXINILLION CUBIC FEET BURNTO
ICOMMEMCL-INSTUTNLIOTNE'/HflT CLASirOISPECIF* IK REMAkKIIOOO GALLON BU-NEO (LlOUIOl
|COHNEilCL»INSTUTNLIOTHE>/UOT CLAS1FOISPECIFT IN REMARKITONS BUHNEO (iOLlDI
INTERNLCOHBUSTIOfllELECTiMC GEN£KATNH>IST|LLATE OIL ITuMtflNF 11000 liALlONS BOHKED
lNTe4NLCONUUSTI«NIELECTS 1C GtNtRATNINATU'AL C.AS ITuHBlNt IMILLION CUBIC FIEI
INTCUNLCONBUSTIONIELECTNIC OEHEPATNIOIESEL IRECIPMOCATIKO iTHOUSANDS or GALLONS
INTEriNLCONbUSTlONIELECTRIC OENEhArNIOTMEa/NOT CLASIFOISfECIFt !N RENAHKINILLIUN CUBIC FEET HURNfO
INTERNLCnHdUSTIONICLECTRIC GCNEHATNIOTHEa/imT CL*SIFOISPEC1FV IN HEKiRKIlOOO GALLONS BURNED
INTtHHLCONBUSTIONIINOUSTKIAL
INTEQHLCONHUSTIONIINDUSTRIAL
INTtaNLCUNMUSTIONIlNOUSTMIAL
IHTEKNLCONBUSTIONlINDUSTRIAL
INTEBNLCONRUSTIONIINDUSTRIAL
lNTEi>NLCONBUSTIONI INDUST4IAL
INTERNLCOMUUSTIONIlKOUSThUL
INTCRNLCOHbUSTIONIiNUUSTrtlAL
(DISTILLATE OIL ITURBINI
(DISTILLATE UlL (RECIPROCATING
IKATU-AL GAS I TURBINE
(KATUfAL GAS (RECIPROCATING
IGASOlilHf (RECIPROCATING
(DIESEL FUEL IHlCIPHOCiTlNO
IOTHE4/NOT CLASIFOISPECIFt IN MEHAHXINILLION CUBIC FEET BURNED
(OTHER/MOT CLASIFDISPECIFT IN REMARKIIOOO GALLONS BURNED
IIUOO GALLONS BURNED
11000 GALLONS BUHNEO
("ILL10N CUBIC FEET
(MILLION CUBIC FEET
11000 GALLONS BUbNCO
11000 GALLONS BURNED
INTtWNLCONbUSTIONICilMMEMCL-INSTUTNLIDIESEL IMICIPMOCATING I THOUSAND* OF GALLONS
INTERNLCONHUSTIONICONHEilCL-INSTUTNLinTHEx/NOT CLASIFDISPECIFT IN NEMARXINILL10N CUBIC FEET BURNED
INTEMNLCOMVUSTIONICOMMErtCL-INSTUTNLIdTHEi'/linT CLASI'OISPECIFV IN REMARK! IOOU GALLONS HURNEO
INURNLCONBUSTIONIENGINE TESTING
INDUSTRIAL PROCESICrtENICAL MFb
INDUSTRIAL PROCESI CHEMICAL MFC
INDUSTRIAL UtOCESlCMEMlCAL MFb
INDUSTRIAL PROCtSICnENICAL MTG
INDUSTRIAL PHOCCSICHEMICAL MFG
INDUSTRIAL PROCESICHENICAL MFG
INDUSTRIAL PROCESICHtMICAL MFG
INDUSTRIAL PROCESICHENICAL NFG
INDUSTRIAL PNOCESICHINICAL NFii
INDUSTRIAL PHOCESICHEMICAL MFG
INDUSTRIAL PROCES(CHEMICAL MFO
INDUSTRIAL PROCESICHEMICAL NFG
INDUSTRIAL PMOCESICHENICAL MFC
INDUSTRIAL PROCESICHENICAL MFC
INDUSTRIAL CNOCISICPEMICAL NFG
INDUSTRIAL PNOCESICHENICAL MFC
INDUSTRIAL vROCESICHEMICAL NFO
INDUSTRIAL PROCESICHENICAL MFG
INDUSTRIAL PPOCESICHENICAL «FG
INDUSTRIAL PNOCESICHCM1C»L «FG
INDUSTNIAL PNOCCSICHEHlCAL *f6
INDUSTRIAL PNOCCSICHEMICAL MFG
(TURBOJET I THOUSANDS OF GALLON/FUEL
IADIMC ACID PROD IGENERAl-CVCLOMEX (TONS PRODUCED
IAPIPIC ACIO PROD IOIMER/KOT CLASIFOITONS fROOUCED
IAMNOMIA I/METHNTRIPURGC GAS (IONS PRODUCED
IANNONU •/HETHNTRISIOHAGE/LOAOHG (TONS PRODUCED
IAHMONIA n/COABShBIREGCNERATOR EXIT (IONS PRODUCED
(AMNONK. tf/COA8SRdlPuMGE GAS (TONS PAOOUCED
IAHHONU (/COABSUBISIOMAGE/LOADlNG (TONS PRODUCED
(ANMOxiA iOTHER/NOT CLASIFDITONS PRODUCED
(AMMONIUM NITNATE (GENERAL (TONS PRuUUCtO
IOIHER/NOT CLASIFOITONS PHUOUCCO
(CHANNEL PROCESS (TONS PRODUCED
(THERMAL PROCESS (TONS PROdUCtO
IFUNNACF PROC bAS (TONS PkOOUCEO
(FURNACE PROC OIL (TONS PRODUCED
IFURNACE H/GAS/UILITONS PRODUCED
I OTHER/NOT CLASFb (TONS PRODUCT
(PTROL/uISTtL/GENLITONS PROUUCEO
IOTHCR/NOT CLASFD ITONS PRODUCT
(GENERAL ITONS PRODUCED
IOTMCR/NOT CLASIFOITONS PRODUCED
ICHLIm-ILKALI IIIOUIFTN-0|ABH«GM||00 TUNS CHLORINE LIQUEFIED
ICHLD4-IL«ALI ILIdUlFTN-MCRC CELI100 TONS CHLORINE LlUUfFIFIt
(INNONIUN NITRATE
ICAMHIIN 8LACK
ICAHBUN BLACK
(CARBON BLACK
ICARdrN BLACK
(CARBON BLACK
ICARBOK HLACK
ICHAPCOtL MFG
(CMAbCO'L MFC
ICHLOUINC
-------
NATIONAL EMISSIONS DATA SYSTEM (NEDS)
SOURCE CLASSIFICATION CODE (SCO REPORT
References:
1. Compilation of Air Pollutant Emission Factors. U.S. Environmental Protection Agency,
Office of Air Programs. OAP Publication No. AP-42. Research Triangle Park, NC.
2. Guide for Compiling Comprehensive Emission Inventory. U.S. Environmental Protection
Agency, OAQPS.Publication No. APTD-1135.Research Triangle Park, NC. March 1973.
i
OJ
U)
-------
APPENDIX A
CDS
DATA ELEMENT DESCRIPTION
-------
DATA ELEMENT DIRECTORY
The CDS Data Element Description sheets in this appendix are arranged
in the following order:
Data Element
Page Data Required on All Cards
A-2 Region
A-3 State
A-5 County Code
A-6 Source Number
A-7 Emission Point Number
A-8 Action Number
A-9 Update Code
A-ll Card Code
Card 1
A-12 AQCR
A-13 City Code
A-14 Source Name
A-18 Street Address
A-19 Regional Data Element 1
A-20 Regional Data Element 2
A-21 Regional Data Element 3
A-22 Regional Data Element 4
A-23 Regional Data Element 5
Card 2
A-24 City Name
A-25 Zip Code
A-26 State Registration Number
A-27 NEDS Cross Reference
A-28 SIC Code
A-29 Federal Facility Code
A-30 Air Program Code
A-30A Air Program Status
A-31 Regional Data Element 6
A-32 Staff Personnel Code-Source
Card 3
A-32A Pollutant
A-32B Pollutant Delete Flag
A-32C Pollutant Compliance
A-32D Pollutant Emission Category
A-32E Pollutant Air Quality Maintenance
Indicator
A-32F Pollutant Air Quality Control
Indicator
A-32G Pollutant Loading
A-32H Facility Capacity
A-32I Regional Data Element 9
A-32J Regional Data Element 10
A-32K Regional Data Element 11
A-32L Regional Data Element 12
Cards 4, 6, 8
A-33 Line Number
A-34 Comments
Card 5
A-35 SCC Code
A-36 NEDS Emission Cross Reference
A-37 Compliance Status
A-38 SIP Code
A-39 Pollutant Code
A-40 State Regulation
A-40A Emission Category
A-41 Process Description
A-42 Multiple Cross Reference
A-43 Regional Data Element 7
A-43A Air Program 2
Card 7
A-44 Action Type
A-45 Date Achieved
A-46 Date Scheduled
A-47 Action Staff Code
A-48 Results Code
A-48A Regional Data Element 8
Generated Data
A-49 Action Description
A-50 County Name
A-51 Date Last Updated
A-52 Record Type
A-53 Staff Name (Action)
A-54 Staff Title
A-55 Staff Name (Source)
A-56 Staff Abbreviation
A-57 Emission Category Description
A-58 Compliance Status Description
A-59 SIP Code Description
A-60 Results Code Description
A-61 Air Program Description
A-62 Old Compliance Status
A-63 Basic Pollution Information
A-l
Revised: ±2/76
-------
REGION
Definition:
REGION is a two position numeric region identifier.
Retrieval
Abbreviation
Card
Type
Cora
Columns
Data Element
Length
Data
Type
Justified
Required
on Neu> 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-2
Masterfile
Length 2
Edit 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-2
-------
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-3eattle
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.
A-2A
-------
STATE
Definition: STATE is a two-position numeric state code.
are derived from the SAROAD manual.
The State codes
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
STTE
1-8
3-4
O
i.
NUMERIC
LEFT
YES
YES
Valid Values:
01 through 56
See attachment showing the states
associated with each state code.
Masterfile
Record Type 20-47
Masterfile
Position 3-4
Masterfile
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 i-s
Data Element Sheet
A-3
-------
State Code. The CDS System uses the following two digit SAROAD state codes:
STATE CODE:
01
02
03
04
05
06
07
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Alabama
Alaska
Arizona
Arkansas
California
Dolorado
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
New Jersey
New Mexico
New York
North Carolina
North Dakota
Ohio
Oklahoma
Oregon
Pennsylvania
Puerto Rico
Rhode Island
South Carolina
South Dakota
Tennessee
Texas
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
A-4
-------
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 Code/AQCR Table.
Master file
Record Type 20-47
Masterfile
Position 5-3
Masterfile
Length 4
CODE FOR STATE
* = Warning Error
Coding Considerations:
Please contact the Central DBC 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
-------
SOURCE NUMBER
Definition: SOURCE NUMBER is a five digit numeric facility identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
SRCE
1-8
9-13
5
NUMERIC
LEFT
YES
110
Valid Values:
All numeric values
Master file
Record Type
Masterfile
Position
Masterfile
Length
20-47
9-13
5
Edit Error Messages:
*** SOURCE NUMBER MUST BE NUMERIC
*** = Fatal Error * = Warning 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. No meaning should be given to
Source Number; Source Number ranges must not be used to identify certain
types of sources. Other data elements are available for this purpose.
Card Type 1-3
Data Element Sheet
A-6
-------
EMISSION POINT NUMBER
Definition: EMISSION POINT NUMBER is a three digit numeric emission
point identifier, if One physical emission point produces
several pollutants, each pollutant is assigned a separate
emission point number. Emission point 000 refers to the
entire source.
Retrieval
Abbreviation
Card
Type
Card.
Columns
Data Element
Length
Data
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
Record Type 20-47
Masterfile
Position 14-16
Masterfile
Length
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.
Emission Point Numbers other than 000 should have no special meaning.
Point number ranges must not be used to identify certain types of points.
Other data elements are available for this purpose.
Card Type 1-8
Data Element Sheet
A-7
-------
ACTION NUMBER
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 Neu Entry
Nationally
Controlled
ANUM
1-8
17-18
2
NUMERIC
LEFT
YES
NO
Valid Values:
00 through 99
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
20-47
17-18
2
Edit Error Messages:
*** ACTION NUMBER MUST BE ZEROS
*** ACTION NUM MUST BE GREATER T11AN ZERO
*** = Fatal Error * = Warning Error
Coding Considerations:
Actions should be assigned sequentially starting with 01. When adding
only one new action to the data base, code 99; the system will convert
the 99 to the next highest sequential action number for that emission
point. When adding several actions for a given point, one must consult
a source data report to see what action numbers are already being used
on the data base.
An action number cannot be added to the data base unless the emission
point for that action is also being added or it already exists on the
data base. Each action number must be associated with an emission
point.
Action number must be 00 for card types 1 through 6; it must be greater
than zero for card types 7 and 8.
Action numbers should have no special meaning. Action, number ranges
must not be used to identify certain types of actions.
Card Type i-s
Data Element Sheet
A-8
-------
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 fio do with other
data on the input transaction.
Retrieval .,,.
Abbreviation
Card
Type 1-8
Card
Columns 80
Data Element
Length *
Data
Type A1*1**
Justified
Required
on flew Entry YES
Nationally
Controlled YES
Valid Values:
N - New
C = Change
D = Delete
Master file
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*** UPDATE CODE D INVALID FOR CARD TYPE 2 & 3
*** INVALID UPDATE CODE
*** DO NOT DELETE POINT 000
*** NO DATA IN COL 21-79 FOR DELETES
*** = Fatal Error * - Warning Error
Coding Considerations:
The CDS-EDIT only validates the existence of the update code; it is the
Update report which points out incorrect or illogical update codes.
Each card type, except card type 2, has a corresponding record type on
the CDS data base. If a card type 1, 4, 5, 6, 7,'or 8 has not already
created a masterfile record type, it must be added as Hew. 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 'C1. 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 1-8
Data Element Sheet
A-9
-------
CODING CONSIDERATIONS (Continued)
The update code 'Df 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 delete is invalid.
A-10
-------
CARD CODE
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
Type 1-8
Card
Columns 19
Data Element
Length 1
Data
Type NUMERIC
Justified
Required
on New Entry YES
Nationally
Controlled YES
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
Master file
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*** INVALID CARD CODE
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type 1-8
Data Element Sheet
A-ll
-------
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
DBC to add a new AQCR to the
County Code/AQCR Table.
and the
also
entral
Master file
Record Type 2$
Masterfile
Position 21-23
Masterfile
Length 3
COUNTY
* = Warning Error
Coding Considerations:
The County Code/AQCR Table containing all valid AQCR's can be found
in Appendix B. Please consult the SAROAD manual or the NEDS Guide to
find out the correct AQCR for each county.
Card Type i
Data Element Sheet
A-12
-------
CITY CODE
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.
Mast erf He
Record Type 20
Masterfile
Position 24-27
Masterfile
Length 4
•
•
BE NUMERIC
* = Warning Error
Coding Considerations:
City codes are available from the SAROAD manual.
Card Type 1
Data. Element Sheet
A-13
-------
SOURCE 1IAME
Definition: SOURCE NAME is a 20 position alphanumeric facility identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on Nei) Entry
Nationally
Controlled
SUME
1
27-46
20
ALPHANUMERIC
LEFT
YES
NO
Valid Values:
All alphanumeric characters.
Mast erf He
Record Type 20
Masterfile
Position 28-47
Master file
Length 20
Edit Error Messages:
*** SOURCE NAME REQUIRED ON NEW ENTRY
*** = Fatal 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. 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-14
-------
** 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
Co mm
Can
Com Ed
Con
Cem
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
Detroit
Edison
Div
Equip
Under Address put plant name
River Rouge Pit
A-15
-------
Full Name
Abbreviation
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
Name
Under Add Put Plane Name
Ford
Motor
Assembly Div
Spell out—do not abbreviate
Name
GMC
Under St. Add Put Plant Name
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-16
-------
Full Name
Abbreviation
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
Op
Packaging Corp AM
Pav
Pit
Pwr
Prj
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-17
-------
STREET ADDRESS
Definition:
STREET ADDRESS is the actual location of the facility; it is
not the headquarters address.
Retrieval
Abbreviation
Card
Type
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
STRT
1
47-66
20 '
ALPHANUMERIC
LEFT
NO
NO
Valid Values:
All alphanumeric characters.
Master file
Record Type 20
Master file
Position 48-67
Master file
Length 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
(Card 4).
Card Type i
Data Element Sheet
A-18
-------
REGIONAL DATA ELEMENT 1
Definition: User supplied.
Retrieval
Abbreviation RDE1
Card
Type i
Card
Columns ' 67
Data Element
Length 1
Data
Type ALPHANUMERIC
Justified
Required
on New Entry NO
Nationally
Controlled NO
Valid Values:
All alphanumeric characters.
Master file
Record Type 20
Masterfile
Position 140
Masterfile
Length 1
Edit Error Messages:
*** = Fatal Error * - Warning Error
Coding Considerations:
A "1" in this field has temporarily been specified by the central DEC
as a designator for facilities impacting an ambient standard in a non-
attainment AQCR.
Card Type 1
Data Element Sheet
A-19
-------
REGIOIIAL DATA ELEMENT 2
Definition: User supplied.
Retrieval
Abbreviation RDE2
Card
Type i
Card
Columns 68
Data Element
Length 1
Data
Type ALPHANUMERIC
Justified
Required
on flew Entry NO
Nationally
Controlled NO
Valid Values:
All alphanumeric characters.
Master file
Peaord Type 2$
Masterfile
Position 141
Masterfile
Length i
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type i
Data Element Sheet
A-20
-------
REGIONAL DATA ELEMENT 3
Definition: User supplied.
Retrieval
Abbreviation RDE3
Card
Type 1
Card
Columns 69
Data Element
Length 1
Data
Type ALPHANUMERIC
Justified
Required
on New Entry NO-
Nationally
Controlled NO
Valid Values:
Mast erf He
Record Type
Master file
Position
Master file
Length
20
142
1
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type 1
Data Element Sheet
A-21
-------
REGIONAL DATA ELEMENT 4
Definition: User supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
RDE4
1
70-74
5
ALPHANUMERIC
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
NO
NO
Valid Values:
All alphanumeric characters
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error
20
143-147
5
Coding Considerations:
If there is a need to have a second SIC Code for a facility, 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.
Card Type l
Data Element Sheet
A-2 2
-------
REGIONAL DATA ELEMENT 5
Definition: User supplied.
Retrieval
Abbreviation RDE5
Card
Type 1
Card
Columns 75-79
Data Element
Length 5
Data
Type ALPHANUMERIC
Justified
Required
on New Entry NO
Nationally
Controlled NO
Valid Values:
All alphanumeric characters.
Master file
Record Type 20
Masterfile
Position 148-152
Masterfile
Length 5
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type 1
Data Element Sheet
A-23
-------
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
Masterfile
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-24
-------
ZIP CODE
Definition: ZIP CODE is the five digit numeric postal zone.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
* ZIP CODE SHOULD BE
*** = Fatal Error
ZIPC
2
35-39
5
NUMERIC
LEFT
NO
NO
Valid Values:
All numeric values.
Masterfile
Record Type
Master file
Position
Master file
Length
NUMERIC
* = Warning Error
20
85-89
5
Coding Considerations:
Card Type 2
Data Element Sheet
A-25
-------
STATS REGISTRATION
Definition: STATE REGISTRATION NUMBER is an alphanumeric identifier
used by the state to identify a facility.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
STRG
2
40-54
15
ALPHANUMERIC
LEFT
NO
NO
Valid Values:
All alphanumeric characters.
Masterfile
Record Type 20
Masterfile
Position 90-104
Masterfile
Length 15
* = Warning Error
Coding Considerations:
Card Type 2
Data Element Sheet
A-26
-------
NEDS CROSS REFERENCE NUMBER
Definition:
NEDS CROSS REFERENCE is the NEDS facility identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
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.
Card Type 2
Data Element Sheet
A-27
-------
SIC CODE
Definition:
SIC is Che 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
Master file
Position
Master file
Length
20
109-112
4
Edit Error Messages:
* SIC SHOULD BE NUMERIC
*** = 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.
Card Type 2
Data Element Sheet
A-28
-------
FEDERAL FACILITY CODE
Definition:
FEDERAL FACILITY CODE identifies facilities owned or operated by
the federal government. Federal facilities such as army bases
fall into a separate jurisdiction than private industry.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
FEDF
2
64
1
NUMERIC
Justified
Required
on New Entry
Nationally
Controlled
NO
YES
Valid Values
blank or zer
Master file
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
* INVALID FEDERAL FACILITY CODE
*** = Fatal Error * = Warning
•
•
o = sources not owned
or operated by the
f ede ral government .
1 = sources owned or
operated by the
federal government.
20
113
1
Error
Coding Considerations:
Card Type 2
Data Element Sheet
A-29
-------
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 EPA 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 V£S
Edit Error Messages:
* INVALID AIR PROGRAM CODE
*** = Fatal Error
Valid Values: __ _
blank or 9 = SIP Source
1 = federal jurisdiction — Active
4 = ESECA
5 ~ other
6 = non-significant deterioration
8 = NESHAPS
9 = NSPS
c = closed/inactive
Masterfile
Record Type 20
Masterfile
Position 115
Masterfile
Length 1
* = Warning Error
Coding Considerations:
For a SIP source, the State has primary jurisdiction for enforcement activity.
For an Active facility, the Federal EPA has primary jurisdiction for enforcement.
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 fiscal year in which the facility was closed.
Card Type 2
Data Element Sheet
A-30
revised 12/76
-------
AIR PROGRAM STATUS
Definition: AIR PROGRAM STATUS represents the status of a facility for a given
air program.
Retrieval
Abbreviation APST
Card
Type 2
Card
Columns 66
Data Element
Length 1
Data
Type Alphanumeric
Justified
Required
.on New Entry No
Nationally
Controlled Yes
Edit Error Messages:
i
* Invalid Air Program Status
*** = Fatal Error
Valid Values:
— Planned
C — Under Construction
0 - Operating
D - Demolition
S = Spraying
Master'fil'e
Record Type 20
Masterfile
Position 180
Masterfile
Length i
* = Warning Error
Coding Considerations:
Card Type 2
Data Element Sheet
A-30A
Revised ]2/7f>
-------
Definition: User supplied.
REGIONAL DATA ELEMENT 6
Retrieval
Abbreviation RDE6
Card
Type 2
Card
Columns 67-76
Data Element
Length 1$
Data
type ALPHANUMERIC
Justified
Required
on New Entry N0
Nationally
Controlled N0
Valid Values:
All alphanumeric values.
Mast erf He
Reaord Type 20
Masterfile
Position 153-162
Masterfile
Length 10
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type 2
Data Element Sheet
A-31
-------
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
Type
Justified
Required
on New Entry
Nationally
Controlled
•PERS
2
77-79
3
ALPHANUMERIC
LEFT
NO
YES
Valid Values
Must exist
maintained
Please call
or delete e
Master file
Reaord Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
* INVALID STAFF CODE
*** = Fatal Error * - Warning
•
on the Personnel Table
by the national DBC.
the DBC to add, change
ntries to this table.
20
116-118
3
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-32
-------
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
Jus tified LEFT
Required
.on New Entry®0
Nationally
Controlled YES
Valid Values:
*
Same as for Pollutant Code. See
pages A- 39 for a list of all
valid codes
Masterfile
Record Type 30
Masterfile
Position REPEATING
Masterfile
Length 2
Edit Error Messages:
* INVALID POLLUTANT CODE
*** = Fatal Error * = Warning 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.
Card Type 3
Data Element Sheet
A-32A
-------
POLLUTANT DELETE FLAG
Definition: POLLUTANT DELETE FLAG is used to remove from the Masterfile all
data related to a pollutant.
Retrieval u/A
Abbreviation
Card
Type 3
Card
Columns ™> 36' 48
Data Element
Length
SS ALPHABETIC
Justified
Required NQ
.on New Entry
Nationally ^g
Controlled
Valid Values:
Blank or 'D1
•
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
* INVALID POLLUTANT DELETE FLAG
* NO DATA TO FOLLOW DELETE FLAG
*** = Fatal Error * = Warning
30
REPEATING
1
Error
Coding Considerations:
A 'D1 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 'D' is coded next to a pollutant or a Card 3.
Card Type 3
Data Element Sheet
A-32B
-------
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 PCMS
Abbreviation
Card
Type 3
Card
Columns 25; 27; 49
Data Element
Length 1
Data
^2 ALPHANUMERIC
Justified
Required
.on New Entry N0
Nationally
Controlled YES
Valid Values:
Same, as CMST, see page A-37 for
a complete listing of values
and meanings.
Masterfile
Record Type 30
Masterfile m™-*,™,,
Position REPEATING
Masterfile
Length
Edit Error Messages:
* INVALID COMPLIANCE STATUS
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type 3
Data Element Sheet
A-32C
-------
POLLUTANT EMISSION CATEGORY
Definition: POLLUTANT EMISSION CATEGORY represents the total potential uncon-
trolled emission of a given pollutant for a source.
Retrieval PECT
Abbreviation
Card
Type 3
Card
Columns 26; 38; 50
Data Element
Length 1
Data
Type NUMERIC
Justified
Required
.on New Entry
Nationally
Controlled YEJ>
Valid Values:
*
See page A-40A for a list of
all valid Emission Category
codes .
Master file
Record Type
Masterfile _ .
Position Repeating
Masterfile
Length
Edit Error Messages:
'* INVALID EMISSION CATEGORY
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type 3
Data Element Sheet
A-32D
-------
Definition:
POLLUTANT AIR QUALITY MAINTENANCE
INDICATOR
POLLUTANT AIR QUALITY MAINTENANCE INDICATOR indicates whether or not
the pollutant impacts AQMA standards or not
Retrieval
Abbreviation PAO-M
Card
Type 3
Colwnns 27' 39' 51
Data Element
Length
^p" ALPHANUMERIC
Justified
Required NQ
on New Entry
Nationally „_„
Controlled
Valid Values:
Blank - NO
Y - YES
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
30
REPEATING
1
Edit Error Messages:
\
*** = Fatal Error * = Warning Error
Coding Considerations:
The default value is blank indicating 'NO*.
Card Type 3
Data Element Sheet
A-32E
-------
POLLUTANT AIR QUALITY CONTROL INDICATOR
Definition: POLLUTANT AIR QUALITY CONTROL INDICATOR shows the AQCR status
of a given pollutant.
Retrieval PAQC
Abbreviation
Card
Type 3
Card
Columns 28; 40; 52
Data Element
Length 1
Data
Tlir)e ALPHANUMERIC
Justified
Required
.on New Entry N0
Nationally
Controlled YES
Valid Values:
Blank - not applicable
N - non-attainment
1 - attained primary standards
2 - attained secondary standards
Masterfile
Record Type 30
Master file RFPEATING
Position REPEATING
Masterfile
Length
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type 3
Data Element Sheet
A-32F
-------
POLLUTANT LOADING
Definition: POLLUTANT LOADING indicates the loading factor for a given
pollutant.
Retrieval man
. i i . , i JjUALJ
Abbreviation
Card
Type 3
Card 29-33
Columns 41-45
Data Element 53-57
Length 5
*£ NUMERIC
Justified RIGHT
Required
.on New Entry
Nationally M_
Controlled NU
Valid Values:
*
Masterfile ,n
Record Type
Masterfile ^mTING
Position
Masterfile ,.
Length
E#tt 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.
Card Type 3
Data Element Sheet
A-32G
-------
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 FCAP
Abbreviation
Card
Type 30
Card
Columns 58~64
Data Element
Length 7
Data
Type NUMERIC
Justified RIGHT
Required
.on New Entry N0
Nationally
Controlled NO
Valid Values:
Master file
Record Type
Master file
Position
Master file
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 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.
Card Type 3
Data Element Sheet
A-32H
-------
REGIONAL DATA 9
Definition:
USER SUPPLIED
Retrieval
Abbreviation RDE9
Card
Type
Card
Columns °3
Data Element
Length ^
^ta ALPHANUMERIC
Type
Justified
Required
.on New Entry NO
Nationally
Controlled NO
Valid Values:
Master file
Record Type
Master file
Position
Master file
Length
Edit Error Messages:
*** = Fatal Error * = Warning
30
23-29
7
Error
Coding Considerations:
Card Type 3
Data Element Sheet
A-32I
-------
REGIONAL DATA ELEMENT 10
Definition: USER SUPPLIED
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
RD10
3
72-73
2
ALPHANUMERIC
Justified
Required
.on New Entry
Nationally
Controlled
NO
NO
Valid Values:
*
Masterfile 3Q
Record Type
Masterfile 30-31
Position
Masterfile 2
Length
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type 3
Data Element Sheet
A-32J
-------
REGIONAL DATA ELEMENT 11
Definition: User suppiied
Retrieval
Abbreviation
Card
Type
Card
Columns
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
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*** = Fatal Error * = Warning
30
32-33
2
Error
Coding Considerations:
Card Type 3
Data Element Sheet
A-32K
-------
REGIONAL DATA ELEMENT 12
Definition: User supplied
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
RD12
3
76
1
ALPHANUMERIC
Justified
Required
.on New Entry
Nationally
Controlled
NO
NO
Valid Values:
Master file
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type 3
Data Element Sheet
A-32L
-------
LINE NUMBER
Definition: LINE NUMBER is used by the computer to distinguish one comment
line from another.
Retrieval
Abbreviation
Card
Type 4, 6, 8
Card.
Columns 20
Data Element
Lertgth 1
Data
Type NUMERIC
Justified
Required
on New Entry YES
Nationally
Controlled YES
Valid Values:
0 through 9
Masterfile
Record Type 21, 35, 47
Masterfile
Position 21
Masterfile
Length 1
Edit Error Messages:
*** LINE NUMBER MUST BE NUMERIC
*** = Fatal Error * = 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.
Card Typo 4,6,
Data Element Sheet
A-33
-------
COMMENTS
Definition: COMMENTS can be used to place on the CDS masterfile data which
does not fit into any fixed card format.
Retrieval
Abbreviation
Card
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.
Mast erf He
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
A-34
-------
SCC CODE
Definition: SCC CODE is the NEDS Standard 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
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
sees, scc6,
SCC8
5
20-27
8
NUMERIC
LEFT
NO
YES
Valid Values:
Consult the NEDS coding
a list of valid values.
edit accepts blanks or
tion numeric field.
Masterfile
Record Type 34
manual for
The CDS
an 8 posi-
Masterfile
Position 21-28
Masterfile
Length 8
Edit Error Messages:
* SCC CODE SHOULD BE NUMERIC
*** = Fatal Error * = 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 nf sr.f. T.oHe; and SCC fl 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 will be provided for these SCC codes.
Card Type 5
Data Element Sheet
A-35
-------
NEDS EMISSION CROSS REFERENCE
Definition: NEDS EMISSION CROSS REFERENCE is the NEDS emission point number.
NEDS assigns emission point numbers based on physical emission
points. If the CDS emission point number is different from the
NEDS point number, this field should be filled in.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Itota
Type
Justified
Required
on Neu Entry
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
NEXP
5
28-29
2
NUMERIC
LEFT
NO
YES
Valid Values:
01-99
Master file
Record Type 34
Master file
Position 29-30
Master file
Length 2
* = Warning Error
Coding Considerations:
Card Type 5
Data Element Sheet
A-36
-------
COMPLIANCE STATUS
Definition: 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
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
CMST
5
30
1
WTTMTTPTr
YES
YES
Valid Values:
Blank, 0 through 9. A, B, C.
Masterfile
Record Type 34
Masterfile
Position 31
Masterfile
Length *
Edit Error Messages:
*** INVALID COMPLIANCE STATUS
*** = Fatal Error * = Warning Error
Coding Considerations:
Must be coded on the point 000; may be coded on the other emission points.
COMPLIANCE STATUS CODES:
Blank Unknown
0 Unknown
1 Not in compliance
2 In compliance by source test —
3 In compliance by inspection
4 In compliance by certification
5 In compliance with increments of progress "^
6 Not in compliance with increments of progress
7 Unknown compliance with increments of progress
8 No applicable state regulation —
9 In compliance - closed down
A Unknown compliance with procedure requirements
B In violation of procedure requirements
C In compliance with procedure requirements
With regulation
With Schedule
Card Type 5
Data Element Sheet
A-37
revised 5/76
-------
SIP CODE
Definition: SIP CODE provides the Regional Office with a method of
separating facilities, points, or actions under schedules
by identifying the type of compliance schedule that the
facility is on.
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 8.
Maeterfile
Record Type
Master file
Position
Masterfile
Length
Edit Error Messages:
* INVALID SIP CODE
*** = Fatal Error * - Warning Error
34
32
1
Coding Considerations:
SIP CODES:
Blank Not specified
0 Regulation effective before 1/31/74
1 Schedule specified in control regulation
2 Schedule approved by EPA
3 State/local enforcement order (admin)
4 State/local Court order - consent decree
5 SEC 113 order; active EPA Enforcement
6 FED promulgation of SIP schedule
7 Schedule not yet approved - under review
8 EPA approved, state revised schedule
Card Type 5
Data Element Sheet
A-38
-------
POLLUTANT CODE
Definition: POLLUTANT CODE indicates the type of pollutant which the
compliance schedule is intended to abate.
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
i
CODE
* = Warning Error
Coding Considerations:
Should be input on all new emission points.
Use one of the following
values:
VALID VALUES
AB - Asbestos
BE - Beryllium
CO - Carbon Monoxide
FL - Fluorides
HC - Hydrocarbons
HG - Mercury
N2 - N02
OD - Odors
OT - Other
PT - Particulate Matter
S2 - S02
TS - Total Reduced Sulfur
VE - Visible Emissions
VC - Vinyl Chloride
Card Type 5
Data Element Sheet
A-39
-------
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
Card
Type 5
Card
Columns 34-48
Data Element
Length 15
Data
Type ALPHANUMERIC
Justified
Required
on New Entry N°
Nationally
Controlled NO
Valid Values:
All alphanumeric values.
Master file
Record Type 34
Masterfile
Position 35-49
Masterfile
Length 15
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type 5
Data Element Sheet
A-40
-------
EMISSION CATEGORY
Definition: 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
Card
Type
Card
Columns
Data Element
Length
Data
Type
ECAT
5
49
1
NUMERIC
Justified
Required
on New Entry
Nationally
Controlled
YES
YES
Valid Values:
Blank = unknown
0 = unknown
1 = Less than
2 = 100-1000 T
3 = over 1000
4 = Less than
Master file
Record Type
Master file
Position
Master file
Length
100 TPY potential
PY potential
TPY potential
25 TPY potential
34
50
1
Edit Error Messages:
* INVALID EMISSION CATEGORY
•*** = Fatal Error * = Warning Error
Coding Considerations:
Must be coded on point
; may be coded on the other emission points.
For Point
the Emission Category must reflect the potential emission
of the entire source according to the Regional Air Program Guidance. The
EC code should be filled out after consulting the NEDS emission inventory
output and then determining potential emissions for the entire source.
Card Type 5
Data Element Sheet
A-40A
-------
PROCESS
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
PRDS
5
50-74
25
ALPHANUMERIC
LEFT
YES
NO
Valid Values:
All alphanumeric characters.
Masterfile
Record Type 34
Masterfile
Position 51-75
Masterfile
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.
Card Type 5
Data Element Sheet
A-41
-------
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
Type
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 001 through 003 refer to three different pollutants
being emitted from one process or piece of equipment, points 002 and
003 should cross-reference 001.
Card Type 5
Data Element Sheet
A-42
-------
Definition: User supplied.
REGIONAL DATA ELEMENT 7
Retrieval
Abbreviation RDE7
Card
Type 5
Card
Columns 78
Data Element
Length 1
Data
Type ALPHANUMERIC
Justified
Required
on New Entry N0
Nationally
Controlled NO
Valid Values:
All alphanumeric values.
Masterfile
Record Type 34
Masterfile
Position 79
Masterfile
Length 1
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type 5
Data Element Sheet
A-43
-------
AIR TWO
Definition: AIR TWO is a one position compliance indicator used to show compliance
with SIP emission limitations for TSP, S02, HC, CO, and NOX in non-attainment
AQCR's.
Retrieval
Abbreviation AIR2
Card
Type 5
Card
_Colurrms 79
Data Element"
Length i
Data
Type Alphanumeric
Justified
Required
.on New Entry NO
Nationally
Controlled Yes
Edit Error Messages:
*** = Fatal Error
Valid Values:
isianK, v through y.
These codes have the same values
QO PMCT
as I/MO i •
Master file
Record Type 34
Masterfile
Position 80
Masterfile
Length 1
* = Warning Error
Coding Considerations:
This field must be used to indicate the compliance status of a facility at the
Point 000 level if the following two conditions are met:
1. The facility is located in a non-attainment AQCR.
2. The facility has been designated as a source which impacts the
non-attainment standards for that AQCR as indicated by a "1"
in RDE1.
If a facility is in compliance with all applicable federal, state, and local regula-
tions, both CMST and AIR2 must contain the same value. • However, a facility may be
in compliance with the particular pollutant for which the AQCR is non-attainment,
and yet it may be of unknown compliance or out of compliance with regulations for
other pollutants. In such a situation, CMST might be a blank, 0, 1, or 6, and
AIR2 will indicate in compliance, (2, 3, 4, 5, or 9).
If an AQCR is designated as non-attainment for more than one pollutant, and if the
facility is out of compliance with any one of these non-attainment pollutants,
AIR2 must reflect the worst case compliance status. For instance, if an AQCR
is non-attainment for TSP and S02, and if the facility is of unknown compliance
with S02 regulations and not in compliance with TSP regulations, AIR2 must contain
a 1 for not in compliance. For further clarification, refer to the FY77 regional op-
erating guidance for AIR2 outputs. Card Type 5
Data Element Sheet
•1 8/76
A-43A
-------
ACTIO:i TYPE
Definition:
ACTION TYPE is a two position action description identifier.
There are at the present 100 possible action types; the first
five are the basic increments of progress federally defined;
the rest are regionally defined.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on Pew Entry
Nationally
Controlled
ATPE
7
53-54
2
NUMERIC
LEFT
YES
YES
Valid Values:
Must be on Action Table controlled
by national DBC.
Action Type 00 indicates an action
type which is user defined.
Master file
Record Type 46
IJasterfile
Position 21-22
Master file
Length 2
Edit Error Messages:
*** INVALID ACTION TYPE
*** ACTION TYPE REQUIRED ON NEW ENTRY
*** = Fatal Error * = Warning Error
Coding Considerations:
Please call the national DBC to add, change, or delete entries on
the Action Table for your region.
If 00 is coded in the Action Type field, the Edit program will pick up
an Action Description from card columns 20 through 34 of the Card 7.
This capability should eliminate the need for using an Action Type
meaning "OTHER - SEE COMMENTS BELOW".
Card Type 7
Data Element Sheet
A-44
revised 5/76
-------
DATE ACHIEVED
Definition: DAT£ ACHIEVED is the date on which an action is performed or
completed in month, day, year format.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
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
numeric other than
be between 01 and
between 01 and 12,
greater than 60.
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
- OUTPUT ZEROS
* = Warning Error
acceptable. If
zero, day must
31, month must be
and year must be
46
29-34
6
Coding Considerations:
If an error is encountered in the date field, the bad month or day or
year is 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
A-45
-------
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
Type
Justified
Required
on New 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.
Master file
Record Type
Master file
Position
Master file
Length
acceptable.
be between 01
be between 01
ist be greater
46
23-28
6
Edit Error Messages:
* INVALID DATE SCHED - OUTPUT ZEROS
* DATE SCHED REQUIRED ON NEW ENTRY
*** = Fatal Error * = Warning Error
Coding Considerations:
If an error is encountered in the date field, the bad month or day or
year is zeroed out. The Update Program no longer generates any value
for this field if it is left blank.
Card Type 7
Data Element Sheet
A-46
-------
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 DBC.
The first position must be alpha;
the next two numeric.
Master file
Record Type 46
Master file
Position 35-37
Masterfile
Length 3
* = Warning Error
Coding Considerations:
Please call the national DBC to make additions, changes, or deletions
to the Personnel Table.
Card Type 7
Data Element Sheet
A-47
-------
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
7(9-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
DBC.
Master file
Record Type 46
faster file
Position 55-56
Master file
Length 2
Edit Error Messages:
* INVALID RESULTS CODE
*** = Fatal Error * = Warning Error
Coding Considerations:
The results code does not indicate the success of an action, but rather
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.
Card Type i
Data Element Sheet
A-48
-------
REGIONAL DATA ELEMENT 8
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
RDE 8
7
72 - 73
2
ALPHANUMERIC
LEFT
NO
NO
Valid Values:
Masterfile ,,
Record Type
Masterfile _7 _ c«
__ • . • J / ™ J O
Position
Masterfile _
Length
* = Warning Error
Coding Considerations:
Card Type 7
Data Element Sheet
A-48A
revised 5/76
-------
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
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
ADES
7
20-34
15
ALPHANUMERIC
LEFT
Required
on New Entry
Nationally
Controlled
Edit Error Messages
*** = Fatal Error
YES
Valid Values:
Please call the national DBC to add
or change action descriptions on
the regional Action Table.
Master file
Record Type 46
Masterfile 107-156
Position 40-54
Masterfile 50
Length 15
* = 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 DBC. 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-49
-------
COUNTY NAME
Definition: COUNTY NAME is generated by the Edit from the COUNTY CODE.
Retrieval
Abbreviation CTNM
Card
Type
Card
Columns
Data Element
Length
Data
Type ALPHABETIC
Justified
Required
on New Entry
Nationally
Controlled YES
Valid Values:
Appendix B contains a list
county names valid for each
state/county combination.
of
region/
Master file
Record Type 20
Masterfile
Position 163-179
Masterfile
Length 17
Ed-it Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
This field is generated; it cannot be coded. The national
DBC maintains a table of COUNTY CODE/COUNTY NAME combinations.
Data Element Sheet
A-50
-------
DATE LAST UPDATED
Definition: DATE LAST UPDATED represents the most current date on which
an input transaction was added or changed for any part of a
facility on the masterfile.
Retrieval
Abbreviation 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
2(8
134-139
6
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
This date is in year, month, day format.
Data Element Sheet
A-51
-------
RECORD TYPE
Definition: RECORD TYPE is a two position numeric masterfile record identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type NUMERIC
Justified
Required
on New Entry
Nationally
Controlled
Valid Values:
20 = Source
21 = Source comment
34 = Emission Point
35 = Point comment
46 = Action
47 • Action comment
Master file
Record Type
Masterfile
Position
Masterfile
Length
20-47
19-20
2
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
Each Card Type has a corresponding masterfile Record Type.
Data Element Sheet
A-52
-------
STAFF NAME (ACTION)
Definition: STAFF NAME (ACTION) is a fifteen position name generated from
the Staff Code found on Card 7, positions 67-69.
Retrieval
Abbreviation STFA
Card
Type
Card
Columns
Data Element
Length
Data
^2 ALPHANUMERIC
Justified
Required
on New Entry
Nationally
Controlled YES
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.
Master file
Record Type 46
Master file
Position 63-77
Master file
Length 15
Edit Error Messages:
*** = Fatal Error * - Warning Error
Coding Considerations:
During each update cycle, the Staff Name is generated based on the
Action Staff Code. By changing the staff name associated with a
staff code on the Personnel Table, all input transactions and masterfile
records will carry the new staff name.
Data Element Sheet
A-53
-------
STAFF TITLE
Definition: STAFF TITLE is a fifteen position title generated from the
Staff Code found on Card 7, positions 67-69.
Retrieval
Abbreviation TITL
Card
Type
Card
Columns
Data Element
Length
Data
Type ALPHANUMERIC
Justified
Required
on New Entry
Nationally
Controlled
Valid Values:
All titles are on the Personnel
Table maintained by the national
DBC.
Master file
Record Type 45
Masterfile
Position 78-92
Masterfile
Length 15
Edit Error Messages:
*** = 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-54
-------
STAFF NAME (SOURCE)
Definition: STAFF NAME (SOURCE) is a fifteen position name generated from
the Staff Code found on Card 2, positions 77-79.
Retrieval
Abbreviation STFS
Card
Type
Card
Columns
Data Element
Length
Data
Type ALPHANUMERIC
Justified
Required
on New Entry
Nationally
Controlled YES
Valid Values:
All names are on the Personnel Table
maintained by the national DBC.
Please call the DBC to make addi-
tions or changes to this table.
Master file
Record Type 20
Master file
Position 119-133
Mast erf He
Length 15
Edit Error Messages:
*** = Fatal Error * = Warning 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.
Data Element Sheet
A-55
-------
STATE ABBREVIATION
Definition: STATE ABBREVIATION is generated from STATE CODE. It is the
standard two position alpha abbreviation set by the Post
Office.
Retrieval
Abbreviation STAB
Card
Type
Card
Columns
Data Element
Length
Data
Type ALPHABETIC
Justified
Required
on New Entry
Nationally
Controlled
Valid Values:
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
20
83-84
2
Edit Error Messages:
*** = Fatal Error * - Warning Error
Coding Considerations:
Data Element Sheet
A-56
-------
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 DEC. 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
Tupe Alphanumeric
Justified Left
Required
on New Entry No
Nationally
Controlled Yes
Valid Values: See Below
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*** = Fatal Error * - Warning Error
Coding Considerations:
ECAT Value ECDS Description
Blank Unknown
0 Unknown
1 Less than 100 TPY
2 100 to 1000 TPY
3 Over 1000 TPY
4 Less than 25 TPY
9 Dummy
Note: If ECAT is not one of the above values, "Unknown" will appear as the
description.
Care Type
Data Element Sheet
A-57
Revised 8/76
-------
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 DBG. It is not present
on-any master file record. A change to CMST will result in a change to the
description.
Retrieval
A bbrev ia tion CMD S
Card
Type
Card
Columns
Data Element
Length 2°
Data
Type Alphanumeric
Justified Left
Required
on New Entry No
Nationally
Controlled Yes
Edit Error Messages:
*** = Fatal Error
Valid Values: See Below
Masterfile
Record Type
Masterfile
Position
Mas terfi le
Length
* = Warning Error
Coding Considerations:
CMST Value
Blank
0
1
2
3
4
5
6
7
8
9
CMOS description
Compl Status unknown
Compl Status unknown
Not in compl - No Schd
In Compl - Source test
In Compl - Inspection
In Compl - Certification
In Compl w Schedule
Not in Compl w Schd
Unknown Compl w 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-58
Revised 8/76
-------
SIP CODF DESCRIPTION
Definition: Sip Code Description is the English language description of Sip Code
(SIPC)~It is generated by the computer based on the value of SIPC. This des-
cription is controlled by the national DBC. It is not present on the master file.
The description will automatically change when SIPC is changed.
Retrieval
Abbreviation 5 IDS
Card
Type
Card
Columns
Data Element
Length 20
Data
Type Alphanumeric
Justified Left
Requirea
on New Entry No
Nationally
Controlled Yes
Edit Error Messages:
*** = Fatal Error
Valid Values: See Below
Master file
Record Type
Master file
Position
Mast erf He
Length
* = Warning Error
Coding Considerations:
SIPC Value
Blank
0
1
2
3
4
5
6
7
8
9
SIPS description
Not Specified
No Schedule
Sched Specif in Regs
Approved State Sched
State Enf/Adm Orders
Court Ord/Consnt Dec
S113 Order - EPA Enfor
EPA Prom of Sched
Sched Pend/Not Apprv
Revised Apprvd Sched
Not Specified
NOTE: If SIPC is not any of the above values, "Not Specified" will appear as
the description.
Card Type
Data Element Sheet
A-59
Revised 8/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
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required.
on New Entry
Nationally
Controlled
RSTD
__
^^
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 46
Masterfile
Position 157
Masterfile
Length 15
Edit Error Messages:
*** = ratal Error * = Warning Error
Coding Considerations:
Card Type
Data Klfinent Sheet
A-60
Revised 8/76
-------
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 APDS
Card
Type N/A
Card
Columns N/A
Data Element
Length 20
Data
Type ALPHABETIC
Justified LEFT
Required
.on New Entry NO
Nationally
Controlled YES
Edit Error Messages:
\
*** = Fatal Error
Valid Values:
Masterfile
Record Type N/A
Masterfile
Position N/A
Masterfile
Length 20
* = Warning 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
Non-Significant Deterioration
New Source Review
NESHAPS
NSPS
Card Type
Data Element Sheet
A-61
revised 12/76
-------
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.
Retrieval
Abbreviation ocs0
Card
Type N/A
Card N/A
Columns '
Data Element
Length
^*^ ALPHANUMERIC
Justified
Required -A
.on New Entry
Nationally YES
Controlled
Valid Values:
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*** = Fatal Error * = Warning
34
81-88
8
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
In April 1977, the Compliance Status found on each emission point record will
be 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 will be able to
compare current compliance status with previous compliance status sent to the
Formal Program Reporting Card Typo System.
Data Element Sheet
A-62
-------
BASIC POLLUTANT INFORMATION
Definition: BASIC POLLUTANT INFORMATION is designed to provide a single
Quick Look print line data element showing data for the
following Card 3 pollutants; Particulates, S02, HC, CO, NO^
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
BPLT
N/A
N/A
61
ALPHANUMERIC
Justified
Required
.on New Entry
Nationally
Controlled
NO
YES
Valid Values:
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*** = Fatal Error * = Warning
30
49-108
60
Error
Coding Considerations:
Card Type
Data Element Sheet
A-63
-------
APPENDIX B
CONTACT LIST
OF
CDS USERS
-------
Contact List of CDS Users
National Data Bank Coordinator
Franklin Smith
202-755-0103 FTS 755-0103
U.S. Environmental Protection Agency
Division of Stationary Source
Enforcement EN-341
401 M Street S.W.
Washington, D,C, 20460
Region I - Boston
Larry Goldman
Paula C. Matos
617-223-3479
FTS 223-3479
Enforcement Division
U.S. Environmental Protection Agency
J.F.K. Federal Building
Boston, Massachusetts 02203
Region II - New York
Stuart Roth
Jerry DeGaetano
212-264-4726
FTS 264-4726
Enforcement Division
U.S. Environmental Protection Agency
26 Federal Plaza
New York, New York 10007
Region III - Philadelphia
Lee Marshall
215-597-4779
Mark Garrison
215-597-9387 FTS 597-9387
Enforcement Division
U.S. Environmental Protection Agency
Curtis Building
6th and Vial nut
Philadelphia, Pennsylvania 19106
Region IV - Atlanta
Janice Murphree
404-881-4253 FTS 285-5291
Randall Davis, Mgmt., Div.
Barry Gilbert
Enforcement Division
U.S. Environmental Protection Agency
345 Courtland St.
Atlanta, Georgia 30308
Region V - Chicago
George Hurt
312-353-2090
FTS 353-8213
Enforcement Division
U.S. Environmental Protection Agency
230 South Dearborn Street
Chicago, Illinois 60604
Region VI - Dallas
Carl Edlund
Mary Kay Marusak
214-749-7675
FTS 749-7675
Enforcement Division
U.S. Environmental Protection Agency
1201 Elm St.
Dallas, Texas 75270
B-l
-------
Region VII - Kansas City
Patsy Burrell
816-374-2576
Enforcement Division
U.S. Environmental Protection Agency
1735 Baltimore Street
Kansas City, Missouri 64108
Region VIII - Denver
RoxAnn Varzeas
303-837-2361 FTS 327-2361
Martha Nicodemus
Lance Vinson
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
100 California Street
San Francisco, California 94111
Region X - Seattle
Betty Swan
206-442-1387
FTS 399-1387
Enforcement Division
U.S. Environmental Protection Agency
1200 6th Avenue
Seattle, Washington 98101
TRC - The Research Corporation
of New England
Scott Shanks
Geza Serenyi
Sue Graves
Rita Reimer
Cathy Morse
Gary Crosse
203-563-1431
125 Silas Deane Highway
Wethersfield, Connecticut 06109
B-2
-------
TECHNICAL REPORT DATA
i I'leme read Instructions on the reverse before completing)
i REPOSTNO
EPA 340/1-76-011
,2
3 RECIPIENT'S ACCESSION-NO.
, TITLE A.\'D SUBTITLE
Compliance Data System User's Guide
5 REPORT DATE
December 1976
6 PERFORMING ORGANIZATION CODE
7 AUTHORIS)
Ms. Rita Reimer
Mr. Geza Serenyi
B PERFORMING ORGANIZATION REPORT NO.
9 PERFORMING ORGANIZATION NAME AND ADDRESS
The Research Corporation of New England
125 Silas Deane Highway
Wethersfield, Connecticut 06109
10 PROGRAM ELEMENT NO.
11. CONTRACT/GRANT NO.
68-01-3173
13. 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
15 SUPPLEMENTARY NOTES
A user's guide describing the general operation of and specific procedures to be
utilized by operators of the Compliance Data System.
16 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 December 1976, which should be discarded.
The guide is organized to be used effectively by several groups of potential readers:
Managers and others wishing a basic descriprion of CDS should read Sections 2
and 3, Management Overview and System Applications. Current Users who generally
understand CDS will wish to skip tp 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 Input Preparation.
REVISED MARCH 1977 - Includes all
revisions and changes since
December 1976
17.
KEY WORDS AND DOCUMENT ANALYSIS
DESCRIPTORS
b.lDENTIFIERS/OPEN ENDED TERMS
c COSATI Field/Group
Air Pollution Facilities(Sources)
Compliance Status
Enforcement Actions
Surveillance Actions
13 B
• •: OlSTRIBUriO'\ STA CEMENT
Release Unlimited
19 SECURITY CLASS (Tint Hf
Unclassified
21 NO OF
20 SECURITY CLASS Cl
TTnol aaaH f "tpH
.-___
72 PRICE
EPA Form 2220-1 (9-73)
------- |