United States
Environmental Protection
Agency
Office of
Enforcement
Washington DC 20460
EPA-340/1-78-003
Revised May 1Q77
Stationary Source Enforcement Series
&EPA
Compliance
Data System
Users Guide
-------
COMPLIANCE DATA SYSTEM
USER'S GUIDE
This report was furnished to the Environmental Protection
Agency by TRC - THE RESEARCH CORPORATION of 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.
February 1978
TRC Project #82752
Contract #68-01-4145
REVISED February 1978
-------
The Stationary Source Enforcement Series of reports is
issued by the Office of Enforcement, U.S. Environmental Protection
Agency, to report enforcement related data of interest. Copies
of this report are available free of charge to Federal employees,
current contractors and grantees, and non-profit organizations -
as supplies permit - from the Air Pollution Technical Information
Center, Environmental Protection Agency, Research Triangle Park,
North Carolina 27711 or may be obtained, for a nominal cost,
from the National Technical Information Service, 5285 Port Royal
Road, Springfield, Virginia 22151.
-------
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 tne 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
8.0
9.0
7.1.1
8.1
8.2
8.3
8.4
8.5
8.6
9.1
9.
9.
9
9
9
9
9
9
9
2
3
.1.
.1.
.1.
.1.
.1.
.1.
.1.
1
2
3
4
5
6
7
9.3.1
9.3.2
9.3.3
9.3.4
9.3.5
9.4
9.5
10.0
10
1
10.1.1
10.1.2
10.1.3
10.1.4
10.1.5
10.1.6
10.2
10.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
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
Table Processing ' 10-1
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
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.
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.1.2
11.2
11.3
11.3.1
11.3.2
11.3.3
11.3.4
11.3.5
11.3.6
Recovery Procedures
Computer Program Modifications
NATIONAL GUIDANCE MATERIAL ....
CDS Input Preparation via ALPHA .
CDS/ALPHA Example
Formal Reporting
CDS Coding Guidance
Coding Card 3
Coding Related to Continuous
Monitoring
Coding Related to New Source
Review, Prevention of Significant
Deterioration, and Enforcement
Coding Related to Power Plants and
Coal-Fired Boilers
Example Coding of Industries into
CDS
Action Types for PSD/NSR Sources .
and Enforcement
PAGE
10-13
10-13
11-1
11-2
11-3
11-7
11-10
11-14
11-18
11-22
11-28
11-35
11-43
APPENDICES
A
B
CDS DATA ELEMENT DESCRIPTION
CONTACT LIST OF CDS USERS .
A-l
B-l
iii
-------
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 df 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 Alpha 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-34A
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 Sample ALPHA Session 11-6
11-2 Job Control for CDS/FRS Link 11-9
-------
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 Source Classification Codes (Partial List) . • . 11-31
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 formats are used to enter data into CDS
via the Edit Program. On each of these card formats there are a number
of data elements nationally defined and controlled; there are also a
number of data elements which can be defined according to each regional
•
user's needs. Since CDS can accommodate both types of data, it is a
highly flexible system able to meet both national and regional needs.
The Update Program uses each of the different input card formats
to add, change, or delete information on the CDS Masterfile. Once data
is placed on the CDS Masterfile, the Retrieval Program can be used to
create a wide variety of management reports based on the data on the
Masterfile.
CDS's retrieval capabilities are highly flexible. Users can obtain
reports based on all data on the CDS Masterfile or on only that portion
of the data which meets user selection criteria. There are four fixed-
format reports as well as 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.
2-4
-------
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
-------
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 tha.t 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 File containing all valid input transactions. With each
run of the Edit, additional valid transactions are stored here
until the update cycle applies these transactions to the Master-
file.
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 ALPHA data set for correction by
those users familiar with ALPHA 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
INPUT DATA
CARD TYPES
1-8
EDIT
PROGRAM
ALL TABLES ARE
MAINTAINED BY THE
NATIONAL DBC
CDS
PERSONNEL
TABLE
CDS
ISAM
TABLE
COUNTY
CODE/AQCR
TABLE
V
EDIT
LOG
MOD
FILE
TO
NATIONAL
DBC
TO
UPDATE
CYCLE
EDIT
REPORT
TO
REGIONAL
USER
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.
1
1
1
1
4
I
1
I
I
I
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
UPDATE
REPORT
10
REGIONAL
DISK
^STERFILES
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 60,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, 30, 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, Scacc, County,
and Source Number
Provide a Unique
Facility Identifier
Up to 10 Comments
Per Source
Up to 1800 points
per facility
Point. 000 contains
compliance Data
for the Entire Facility
Actions for
point 0(30 refer
to action for the
Up to
_jj 10 coaaencs
per action
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
3
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
_W
PRINT
PROGRAM
V
RETRIEVAL
OUTPUT
REPOR
I
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.EPAEXC.A026-CDS.SYSOUT
This data set shows the date, the time, and the output
serial numoer or 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
receded. 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
Air Program Code 65
Air Program Status 66
Regional Data Element 6 67-76
Staff Personnel Code 77-79
* These data elements should be filled in when a new transaction is
being added to the Masterfile.
6-1
-------
Company
Application
CDS INPUT LAYOUT
by
MULTIPLE-CARD LAYOUT FORM
TRC
Dale
MARCH 1976
Job No
Sheet No
I 2
3 4
O
CJ
5 6 7 6
o>
O
(J
O
CO
9 10 II 12 13
O
On
14 is is
U
17 IB 19
U
2021 22
X rl
O
a-
14 IS 16
City Name
7 18
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
O
•H
00
I 2
CO
3 4
C
O
96)8
0)
U
P
C
CO
9 10 11 12 13
O-i
14 IS IG
I 18 19
20 21
u Pollutant 1
i-i
c
a,
22 73
C X, li
«
E-H
00 4J
c a
•H O
30 31 3: !3
01
•a
O
U
State Registration
Number
IS 38 37 38 39 40 41 42 43 44 45 « 47 48 49 M SI 52 S3 54
4J Pollutant 2
3* 35
ooS
C CO
•H U
•O -H
j eg T3
•4 O C
* ,J H
-7 -.' ii -5
a
w
2
iS 56 57 58
uPollutant 3
n)
(-1
ori o
00 J-*
C A
•H u
T3 -H
HH
4J CO
r-( O
Oi hJ
J54 55
.C
5J
U
S9 60 61 62 63 64
•H -H
i-H O
•iH nj
U (X
CO CO
f"M O
I 59 SC 61 5? S3 64
RDE 6
p. a
16 67 H 69 70 71 72 73 74 75 76
77787!
tn
W
§
>5 66 67 M 69 70 71
M
2
72 73
4 75
777874
1 2
C
o
5676
0)
U
M
O
cn
9 10 II 12 13
.s
o
14 15 16
7 II 19
SCC Code
20 21 22 23 24 25 26 27
2829
3233
Federal/State/Local
Regulation Number
H 35 36 37 38 39 «0 41 42 43 44 45 46 47 48
Process Description
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
757677
U
§
ai
u
o
10 11 12 13
4J
a
o
PH
Optional
Short Action
Description
20 21 22 23 24 25 26 27 28 29 30 31 32 33 Ml 35
Filler
36 31 38 39 40 41 42 43 44 45 46 4) 48 49 50 51 51
4J
$
5354
Date
Achiev-
ed
55 56 57 58 59 60
Date
Sched-
uled
>1 62 63 64 65 66
CO
176863
CO
4J
H
CO
S
70 71
00
1
727]
Filler
74 75 76 77 78 79
1 2
3 4
4J
O
5678
01
U
t-l
O
CO
9 10 11 12 13
O
CH
14 15 16
CJ =»
7 II 19
Comments
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 46 47 48 49 50 51 52 53 M 55 56 57 SB 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
FIGURE 6-1
-------
Card Code 3
Card Column
Pollutant - ID
Delete Flag
Pollutant Compliance
Pollutant Emission Category
Pollutant Air Quality Main-
tenance Indicator
Pollutant Air Quality Con-
trol Indicator
Pollutant Loading
Facility Capacity
Regional Data Element 9
Regional Data Element 10
Regional Data Element 11
Regional Data Element 12
22, 34, 46
24, 36, 48
25, 37, 49
26, 38, 50
27, 39, 51
28, 40, 52
29-33; 41-45; 53-57
58-69
65-71
72-73
74-75
76
Card Code 4
Comment Line Number
Source Comments
Card Column
20
21-79
Card Code 5
SCC Code
Capacity Code
Compliance Status
SIP Code
Pollutant
Stste Regulation Number
Emission Category
Process Description
Multiple Cross Reference
Regional Data Element 7
Procedural Compliance
Card Code 6
Comment Line Number
Point Comments
Card Code 7
Penalty Amount
Action Type
Date Achieved
Date Scheduled
Staff
Results
Card Code 8
Comment Line Number
Action Comments
Card Column
20-27
28-29
30
31
32-33
34-48
49
50-74
75-77
78
79
Card Column
20
21-79
Card Column
46-52
53-54
55-60
61-66
67-69
70-71
Card Column
20
21-79
These data elements should be filled in when a new transaction
is being added to the Masterfile.
6-3
-------
si i cm in IY
liMEMimm.
o|o|o|6|o
IIUII.il
COMPLIANCE DATA SYSTEM CODING SHEET
iailliSLik b61 'jl l'illlMlliQI6ll6?ri3lli1|l.blb(- 16/1
11Tm1TnTmffl1ffl1^
0|0|0|0|0 4
I I M I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I M I I I I I M I I I I i I I I I I I M I I
IHIS5IUN.
Mi) 1111 mil
vc loin
SIAII Hir.iiiAimn
PROCISS DISCRIP11UN
MI!
t!Ii^l lf>\id!'!]Will*'|12I*JI*ll*5|1|iM/1111
"Jl.Ol'.ll'i?!1
f>iI'j?h4J'J
-------
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 N0x 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 J 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 Length Coding Considerations
Pollutant ID 2 Must be coded for each pollutant
produced by the facility. Valid
values are the same as for PLUT.
Pollutant Compliance 1 Must be coded for each applicable
pollutant. This compliance status
should represent the worst-case
compliance of all the emission
points producing that particular
pollutant. Valid values are the
same as for 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 'N1 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 'C' for adding,
changing, or deleting pollutant data. Because a facility can produce
numerous pollutants, the input punch card has room for three sets of
6-7A
-------
pollutant data. Multiple Card 3's may be used to enter pollutant compli-
ance data for facilities producing more than three different pollutants.
Up to ten different pollutants may be stored on the Masterfile for one
facility. The order in which pollutant data is entered into the system is
not important for the five pollutants subject to SIP regulations; PT, S02,
HC, CO, and 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 6 is a comment card used to add additional information
about an emission point which is different from the information supplied
by the data elements on Card Type 5. There are 10 comment line numbers
available on Card Type 6; up to 10 comments may be used to add informa-
tion. A point comment cannot be added to the 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 more than one new action number
to the Masterfile, Action Number 99 could be coded into columns
17-16. 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
-------
COMPLIANCE DATA SYSTEM COOING SHEET
I-1
NJ
IV SOURfI HUH ill
/ I I!|9|IO|IHI?|I
l7|43l«l'l 47HUM
Ml M~I
IACIIMV CAPACITY I RDt 9
.
^PITJ bisi i n M lEErm iTTilTll II11 ilTl TMTI ITTIi M li i IN
«l I |M|6r| MM
|0|2JO|OHO|2
I I I I I I I I I M M II M I I I I I I I I I I I
I I I I I I I I II I I » I M I I I I I I I I I I I I I I I I I I I I I I I I I i I I I I I I I II I I I I I I I
AC1ION RISUMS
I'lHAIM Aill I IYPI [ BAH ACMIIVID OAK bCIILDULID SIAIF KD| 8
IHISSIUII All Mill III'IIOIIAI A( 111)11 Blb( Rll'llll'l
'Ollll IIU IIU II^MI Ml III All'l fin
n i 11111 11 n n 11
Al Illlll (UWILNIS
LtLnhiM:
i n n i 111111 11 111 i 111 M 11 111 11 11 11 i
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.
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-14
-------
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
-------
MGIONi Sj I CUmilY
mr TK
a i
CAIIU IIIUI
0
(, 7 Ill-l
AIJIII
JK(I IIUII.il
IU II I? II
OCO I
uiv (HIM
COMPLIANCE DATA SYSTEM CODING SHEET
'.(JUUU NAIII
blRIM AllllKI'.S
Kill 4
Mill S
I U. LESS
rnv
blAll IIIC.IMRAIIUH
Nll)b XHII
SIC
RUI b
SIAII
H, 21 ?n 11 lit II 1? 13
1I!|3
refi
lyI4
w"
47
'ill
kip
111 AH I
bb b7IS|t
E
bfi
66
jjfl
ZSl
I'Oj IUIANI T
I III 111 AH I J
I ACM IIV rAI'ACIIV
KOC 9
ll'llblKill/IIB
._.___
b3|'j4IVj|S6lii7 llllrj9l6UI6llt?l03164.bllit'l6/|fiaib91>Ol>ll^iri
• LI III HO
MIUHII I Wf II Nib
4|l5|lf.|17IIH
00 000
ZS Ll
3?JLlIMiiJJfJiqjl!lii|!Ll|ill!/. ii ii !q!U47l4!J1a
73
/b
7b
78
79 1
|o|o
6|
I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I II I I 11 I I I I I I I I I II I II I I II
IHIbbKIN At HUM
|"omi nu iiu
III'IKIIIAI Al IIOII UlbCHM'IIIIN
DM II HUM All') W
11111II1111111
AC1ION RlbUI I.
I'INAIM AMI 1Vp( [)A|| AdUIVID I DAIl bClllDULLU SIAII LD( R
5J3
QhhlS|7i7|oh|||5|7|7
II
.EHlSMOH
IPOINI no
(irn-i
71 I I I I I I
i INI mi
11 i n i 11 srr
>d 1111 111111111 1111111
81
AI nun IUMIIIIMS
±ffl±ffiffl:H:fflBI
i OH HJ 03 OH ai ta ca en BO 0a B3 tu IB ra m t& ra m ea 10 E
I I I I I M M M I M M I I I I I
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 2<0
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
-------
COMPLIANCE DATA SYSTEM CODING SHEET
MIlillMiillil. i9['ii)li>lp?lbJh4
|0|0|0|0|3t^ II II II II II II I I I II
|?<|?!,^6l^pn|^ JO HI 3M)]IM)bl JfJUlJJil J9JIUI1I 1?J4JIM ^WffT Up bU UpHbT b4Tjsn6 S?rm|59p|bl|6?|i3l61l6S|t6p 6Blb9| ;0|7I|/?| 7J1MI'bl/6|//
MTl 111TI1 IT111111 111 II M111T1111TH Ml MTilTnllTnTt
|o|o|Q|o|oN I M I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I M I I I I I
CAPC \1|ii'!|6'jm|li/|6ll|
T i n i n~n~i~n n~n~ri i 111 M 11 M M 1
I I I M I I M I I
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
ON
I
NJ
fO
-------
TABLE 6-2
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 1
q
*
i
i
c
O OJ
•pf 4J
&Q a
tx; co
i
1214
>,
g
3
O
CJ
5 6 7 8
a
{j
M
9
O
CO
9 10 II 12 13
C
•rt
O
Pu
14 IS 16
-------
I
NJ
TABLE 6-3
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 2
OJ
Q
Q£
<
I
d
Q Q)
1-1 4J
oo a
a) jj
Oj CO
u
c
3
O
O
-------
TABLE 6-3A
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 3
I
DO
1 I
01
4J
a
j-
en
1 4
IK
- Cnuncy
= Source
u
5
£
14 It Ii
G
O
•H
II II
U
o
o
a
o
5
19
| 2 Filler |
| ~ Pollutant |
P
o
c
14
0
J
•H
j
11
4
Li
rt
u
<
i-
X
ri
ts
X
i
%
i
nt i s
00 2
c a
Tl U
u -o -H
1 30 11 12 U
u
e
a
3
~H
O
a.
>. »
PC
a
3
ul
a
K
>1
1
g
ll
s
c
It
i
u
i<
n
a
£
j
u
a
nt 2 u
o
BO U
c a
•H U
•0 -H
u a -a
r< o c
(-< iJ 1^
II 11 4] «4 41
4J P
§
U
3
^
•H
Ift 41
ol
E
:~t
r a
1
3
a
it
t-
a
>i
31
K
C
<
t-
5
.1
it 3 h
C.S
C CO
Tl U
•a TI
u a TJ
S3S
1 H U M 1)
u u
Tl -H
•H U
•s a
£3
« Jl U (1 6? U M
Id
3
,5 ii II U N 10 Jl
o
1-1
u
3
nil
r-l
U
2
«n
4 M
H 01
tH
1 f-t
i £
1 IJ7I J!
01
1
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
Alphanumer ic
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
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
in
a
a
5
J
O 0)
•H 4J
60 n)
0) 4J
Otf CO
1 2|J 4
5s
*J
O
u
9678
0)
U
3
0
co
9 10 11 12 13
4J
.5
O
PM
14 IS 16
(U
•a
=»= 0
c .u
O •
•H -3
u W
SCC Code
O fflj
< (J
1
17 18119
20 21 22 23 24 25 28 27
1
-4
y]
vi
O f.
r
282933
p.
1!
s
fc
3233
Federal/State/Local
Regulation Number
34 35 36 37 1C 39 <0 41 42 43 44 45 46 47 48
E-
p
*^
49
Process Description
50 91 52 U S4 55 56 57 58 59 60 61 62 S3 64 65 66 67 68 69 70 71 72 73 K
H ^
'
CN
0)
gj uj Uico*n
^ pM (Q'fS, 1^
797677 787980
I
to
Date Name
SCC Code
Capacity
Code
Compliance Status
SIP Code
Pollutant Code
State Regulation
Emission Category
Process Description
Multiple Cross-reference
Regional Data Element 7
Procedural Compliance
Card Column
20-27
28-29
30
31
32-33
34-48
49
50-74
75-77
78
79
Data Type
Numeric
Numeric
Numeric
Numeric
Alphanumeric
Alphanumeric
Numeric
Alphanumeric
Numeric
Alphanumeric
Alphanumeric
Data Element Length
8
2
1
1
2
15
1
25
3
1
1
Justified
»
Left
Left
Left
Left
Left
-------
TABLE 6-5
KEYPUNCH INSTRUCTIONS FOR CARD TYPE 7
U
> «
• u
\ (0
w
3 4
£»l
4J
C
3
3
S S 7 t
0)
u
l-l
3
O
to
9 10 II 12 13
4J
j3
•H
O
14 15 16
•0
=5* O
C U
0
•H -0
4J Jj
U CO*
< P!
17 IS1 19
T
Optional
Short Action
. . Description i
17 18' I9j» 21 22 23 24 2S 26 27 28 29 30 31 32 33 WJ35 38 37 38 19 40 41 42 43 44 45
.ler
42 43 44 45
Penalty
Amount
46 47 48 49 50 SI 5;
cu
X
4J
4J
u
S3S4
Date
Achiev-
ed
Date
Sched-
uled
55 56 57 SS 59 60 61 62 63 64 65 6C
U-l
CO
to
97 69 63
(A
r- (
3
co
CA
7071
co
Filler
U'
g.
72 731 74 75 7E 77 78 75
cu
CO
•a
a
3
90
Date Name
Short Action Description
Penalty Amount
Action Type
Date Achieved
Date Scheduled
Action Staff Code
Results Code
Card Column
20-34
46-52
53-54
55-60
61-66
67-69
70-71
Data Type
Alphanumeric
Numeric
Numeric
Numeric
Numeric
Alphanumeric
Numeric
Data Element Length
15
7
2
6
6
3
2
Justified
Left
Right
Left
Left
Left
Left
Left
ON
-------
TABLE 6-6
KEYPUNCH INSTRUCTIONS FOR CARD TYPES 4, 6, AND 8
oo
vC
4
•tj1
P
U
e
o
•rl
CX
0)
Pi
0)
CO
JJ
&2
^
4J
c
o
5J
<1J
u
3
O
tJ
a
o
CM
14 1! IS
=»:
C
0
•rl
U
^
17,8
•0'
OI-.
•3 31 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 53 SO 61 62 63 64 65 66 57 68 69 70 71 72 73 74 75 76 77 78 73
0)
4J
ca
•o
a
80
I
NJ
00
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
Stace
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 & 3
EMISSION POINT MUST BE NUMERIC
POINT MUST BE GREATER THAN ZERO
INVALID COMPLIANCE STATUS CODE
ACTION NUM MUST BE GREATER THAN ZERO
ACTION NUMBER MUST BE NUMERIC
INVALID ACTION TYPE
NO DATA IN COL 21-79 FOR DELETES
ACTION TYPE REQUIRED ON SEW 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-1A
A-3 3
A-9
A-7
A-7
A-37
A-8
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
Air Program
Status
Air Quality
Maintenance Area
AQCR Indicator
Pollutant
Emission Category
Procedural
Compliance
Message
* INCORRECT AQCR FOR COUNTY
* CITY CODE SHOULD BE NUMERIC
* ZIP CODE SHOULD BE NUMERIC
* SIC CODE SHOULD BE NUMERIC
For Detailed
Explanation,
See Page:
A-12
A-13
A-25
A-28
* INVALID FEDERAL FACILITY CODE
* INVALID AIR PROGRAM 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
* INVALID AIR PROGRAM STATUS
* INVALID AIR QUALITY MAINT AREA
* INVALID AQCR INDICATOR
* INVALID POLLUTANT EMISSION CATEGORY
* INVALID CMS 2 CODE
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
A-30A
A-32E
A-32F
A-32D
A-43A
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
-------
. |A( It IIAIA
bfSltr. LUIT
3-HMJLAUHHH1A
(if. o}/4< ill CM* S*Ct PNI »N HP
0 1
12 34 5b70 <»0l23 4Sb 70 V
o3 40 021)0 ooo 1 a 022 oi 7
03 4(J 20(10 000 1 1 (100 nil 1
SHfcfcANULAH
1)3 40 2080 1)0011 000 00 f
03 40 2080 0001 1 DUO 00 4
03 411 2000 0001 HO U Oil 4
03 48 28HO 0001 000 OH S
03 40 2BOil 0001 OlO DO S
03 40 2eOO 0001 Oil 00 5
03 40 2800 0001 014 00 5
o3 4o 2ddo ooni ooo oi 7
03 40 2080 0001 000 02 7
03 40 200(1 0001 000 03 7
o3 48 2000 oool nlo do b
Ul 40 2880 0001 (l2l) 00 b
Hi 34411 0001S 010 00 S
03 40 34411 0(1015 01S 00 S
03 40 3440 00015 OlO DO b
II 3 40 3440 00015 015 (Mi b
Ii3 40 3440 OU015 000 OS 7
03 4(1 3440 00015 Old US 7
n3 40 3440 (i. lii IS olS OS 7
CAHO
2 » 4
ol2J4bb/e<4Ul234bb70>tni2i4b
22b viUMN3»MANv ILLfc
HiiLiUSIlILK 22bb42o7b4
IbHtNANUUAH VALLE1 PLANT
2P.U. BUH 442
40
40PI
40S2
40N2
IHUI1 tHS bUHN • b OIL
IIIPIHAIIUNS INCL. PtNLIU
31N3ULAMUN bUAKO MILL
40VL
40P1
uovt
2F1M3MING tM)
2o7i4boPtNULtTUf» CUNST CO,
"MTlMtVlLLt 243B2IU034
IP. U. dux S49
40
40PI4.40
40Vt4.20
1 HUkNtH HAIfcO Al 460UOOOO
1 UUHNEH KAIEU AT 4b400000
LULU"i"iSl
S b 7
b 781(0 !234Sb78VOl234Sb78VO 123
05031772031772 ol
t*U Uf- HI 837 UKt- 1 |
2«fcAl PHllCESS BIJXNfcHSCm
2HtAl CHdCESS bUlM:kS(l7)
ihtAI PROCESS BUHNtKS(17)
2nEAI PHdCkSS bliKNtHSU7)
I4082373U02173 01
150105760105/fc 01
17U4o77b04077b 01
EXP., 3IAKTM MIXING, UkYtN,
oSu4o77bo4o77b u|
170105760105/6 01
OS04o77604o7/b 01
2HtAl HHULtSS bliHMfcK(l7)
2PKUCLSS UPfKAllUNS
2PHULkb3 UPkNATIUNS
!7uloS7boI057e o|
OS04o77b04077b o 1
I7olli5760l057b 01
05o4o77bo4077h ol
17010576010576 01
oSo4i)77b04077b ol
1 70105760105/6 0|
OSo4o77b04077b 01
17010576010576 01
0504077b04077b 0|
H13 |l 4 b49
29S2
'ASPHALT BATCHING PLANT
A
ChUILtK, »2 OUStL HKtl)
2bUlLEMi «2 UltStL FlHtO
HlU/HH
B lU/hh
ObOtt2b72U42b72 01
oS042»72042b72 01
obu4«!b72U42b/2 01
(.DDE. * BANNING - DAIA ELfc"tM htJtCltli
0 . *«» MIA|. . CAKII (.tJtCUD
4Sb789 0
^
i,
N
N
N
1,
h
010 N
oi n N
N
N
N
*
31L08 N
^
N
010 N
N
020 N
N
N
N
£
N
II
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
«•* INVALID UPUAU cLOt
• •• INVALID UPOAU CLUE
«»« INVALID UPUAFk C( Ot
• »* INVALID unjAit ccuE
• INVALID EMSSlLh CATEGCHT
Figure 7-1
CDS EDIT REPORT
-------
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 Edit
TASK NUMBER
TRC
JCL for using the CDS Edit with card input.
1
/
/
/
/
p
/
/
rti
2
*
/
/
/
^
/
*
1
3
P
E
C
E
> A
E
ihi
4
R
P
D
D
» '
O
ir<
5
1
A
S
1
1
F
f
6
O
•
l
E
T
in
fO
7
R
•
1
D
p
8
1
•
1
1
C
irt
9
T
T
A
g
10
Y
R
ne
sJi
11
D
QU
flh
•
i
a
n
12
J
E
S
••I
f\
•
1
a
13
0
X
1
hi
•
1
a
14
B
E
N
a
is
C
ll
16
4
(
»d
if?
17
a
c
D
fll
fj
.S
.S
18
a
D
D
f
f]
tl
tl
19
a
S
•F
rh
f
e
e
20
a
l
*
if
B
|fj
US
us
21
/
P
ay|i
PT
er
er
P
•
1
T
fi
s
S
23
•
1
n
hr
f
24
•
1
a
rh
1
re
gi
C
25
)
p
In
1C
>n
)S
26
/
ro
In
If
:o
n
?I
E
-1
27
<
If
nil
i\
mi
iml
;ui
)!'
28
U
j
f
Cj
I
ei
E
29
S
rfl
un
t
7-
OE
30
E
.J
Tc
36
th
2
C
31
R
i^»
:
t '
)N
32
•),
ra!
'R(
33
1
ne
ic
L
34
D
V
35
>
tl
36
/
ie
37
T
i i
38
\
Tf
39
M
1
40
E
t
*
41
:
ir<
42
1
UJ
43
h
44
L0
45
46
47
f\
48
49
50
51
52
53
54
55
56
57
i
!
.
vO
-------
AUTHOR TRC
Using
1
/
/
/
/
]
/
/
r
2
*
/
/
/
1P
/
*
IP
3
P
E
C
E
it
E
ft
4
R
P
D
D
t
O
Tfl
5
1
A
S
1
ar
F
jp
6
O
•
I
E
T
Si
fl
7
R
•
1
D
•
Ct
f\
8
1
•
1
1
C
.0
rfl
9
T
T
A
i i
•ri
PROGRAM NAME CDS EDIT
the CDS EDIT with the "DUMMY" mode; with this mode, no data is saved on the MOD
10
Y
R
ai
<
11
D
ds
hr
12
J
E
S
s
111
lift
•
1
a
n
13
O
X
1
10
•\
Bl"
•
1
a
M
B
E
N
ll(
If*
•
a
is
C
b
pi
a
16
4
(
D
a
flf
17
a
C
D
>l
Pfl
i
1
1
18
a
D
IC<
a
19
a
S
*
d
h<
hf
hi
I
20
a
I
in
hf
i
\
S]
21
/
P
me
f
se
SF
fif
NG
22
•
1
T
li
id
r1
r'
r'
T
23
•
1
n
it<
Q
i
i
j
IE
24
•
1
i
1)
|
•01
T(
El
25
)
T
i
tr
j
/
•\,
ut
ii
26
/
Y
ft
t-
ni
r*r
j|
E
'S
27
(
P
jr
ro
ti
mi
in
7_
D
21
U
E
tl
iq
il
ft"
ih
IMI
29
S
=:
e
n
Til
TC
K
30
E
«
ab
1r
mt
t
OP
31
R
D
3V
n
PI
hf
TI
32
U
HP
•\j
DN
33
1
M
c:
:k
il
34
D
M
(
rl
35
»
Y
ai
Vf
36
t
i
d.
1,
37
T
t
PS
38
1
a
39
M
•p
40
E
1
41
=
fh
42
1
ro
43
IP
44
45
o
TASK NUMBER
File.
46
47
48
49
50
51
52
53
54
••J
I
-------
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
£
4
R
P
D
D
O
5
1
A
S
1
F
6
O
•
1
E
T
7
R
•
1
D
•
8
1
•
1
1
C
9
T
T
A
10
Y
R
11
D
12
J
E
S
D
V
Wt
•
1
a
n
X
y
13
O
X
1
C
O
f T
•
1
a
X
Y
14
B
E
N
B
L
2 !
•
i
a
X
y
IS
C
:
=
a
X
Y
16
4
(
D
(
S
X
Y
17
a
C
D
R
E
X
IB
a
D
E
R
19
a
S
D
C
:
•f
ii
•f.
•f,
•),
20
a
l
S
F
Z
F:
21
»
P
N
M
Z
hf
he
hf
hf
hf
h.
Gl
22
•
1
T
i
Z
V.
11
t\
ti
RE
23
•
1
n
X
F
z
se
^p
if
In
n 1
7
24
•
1
X
B
Z
.1
.1,
•V
.4
25
1
X
/
z
26
/
X
L
r
NP
27
i
X
R
•i
a
In
J .
UT
21
U
X
E
^•f
:c
1
1
F
29
S
i
C
(••f
DU:
^111
-,f
101
30
E
U
L
lit
it
ihf
cl
*,
[ 1
31
R
N
:
ni
y
AI
32
1
8
mlp
t3
e.
E
33
\
T
0
ar
34
D
:
/
f.
35
*
2
B
1 ,
36
i
4
L
fcV
37
T
0
K
38
1
0
S
39
M
/
1
40
E
D
Z
i,
41
:
1
E
*
i .
42
1
S
z
43
P
y
.f
44
=
y
45
S
Y
f
46
H
y
47
R
y
rrl
48
f
)
J
49
50
ft(
51
52
53
54
1
I
(
-------
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 r
i\
/
1
1
/
1
1
/
np
/
I
ic
3
P
E
C
E
E
Lit
E
a
4
R
P
D
D
D
t
0
O'
5
1
A
S
1
1
ai
F
e
6
O
•
1
E
T
T
S(
tv
7
R
•
1
D
,
.
ct
3
8
1
•
1
1
R
C
Lo
:a
9
T
T
E
A
is
rdi
10
Y
J
R
st
!
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
ie
e:
•
1
a
is
C
D
P
=
=
l£
Pi
a
16
1
(
D
=
(
S
D
ce
ac
17
a
C
(
R
E
D
l
id
18
a
D
D
N
E
R
nn
31
19
a
s
20
a
I
S|N
EL
C
-
*
ec
F
W
ic
«
•f
j
^
9
21
/
P
=
?
M
0
te
e
rh
ht.
s
22
•
1
T
C
K
a
R
iy
id
• ]
w
23
•
1
n
N
E
F
K
a
o:
fif
9 1
:NI
24
•
1
B
E
B
5
tc
t
r'
,. i
T(
i
K
)
E
P
f
0
r
he
;
26
1
P
)
L
th
t
\m
HB R
i
27
U
A
f
R
k
:a
H
»
1-
!J
28
S
•
1
S
E
ib<
IS(
n1
Cv
il
:c
29
E
•
1
P
C
v«
Cl
fl
ou
ilU
]
30
R
•
I
A
L
*
io
al
II
31
•
C
s
CI
i
l
! t
E
32
1
a
E
8
C
le
33
D
a
:
0
ir<
:k
34
1
a
C
f
.
•
35
/
a
T
B
36
T
•
R
L
37
1
E
K
K
38
M
R
f
S
39
E
R
(
1
40
=
O
2
z
41
1
R
/
E
42
S
2
s
43
i
)
3
44
U
)
1
45
N
/
2
46
1
P
47
T
)
48
r
f
49
3
50
3
51
3
52
0
53
-
-------
AUTHOR TRC
PROGRAM NAME CDS EDIT
TASK NUMBER
Printing the optional REJECT file during a regular Edit run.
1
/
/
/
/
/
I
/
/
T
2
*
/
/
/
/
P>
/
)(
e
3
P
•
1
C
E
E
t
E
at
4
R
•
1
D
D
D
ti
o
ov
5
1
•
1
S
1
I
an
F
!
6
O
E
T
T
;a
W(
7
R
D
,
.
t:
c
8
1
1
R
C
OI
ai
9
T
T
E
A
C
ds
10
Y
J
R
ar
s
11
E
D
Is
101
12
J
E
C
S
st
lc
Wt
•
1
a
n
13
O
X
T
1
01
b
PT
•
1
a
14
B
E
N
Id
e
p •
•
1
a
15
C
D
b
>li
a
16
4
(
D
D
I
C(
17
a
C
D
If
d
18
a
0
S
ce
at
i
1
1
19
a
S
Y
*
1
t
i
j
20
a
i
S
m
e
h<
hi
hi
21
i
P
O
ie<
ei
i
i
PF
22
•
1
T
U
it
d
se
fif
f?^
IN
23
•
I
n
T
te
tjf
r1
r1
r>
n:
24
•
1
:
iy
f
;
j
'!(
IG
25
)
A
a
If
n:
n
Ul
n
26
/
j
t(
d
tJ
ni
•1 f
E
E
27
1
k
D
r
fln
al
nt
n
7-
IE
28
U
C
th
Sfl
i
n
iti
i
FE
29
S
B
\
•f
ini
ih
;T
30
E
%
ib<
01
PI
Fl
31
R
B
V«
t
LE
32
L
-
pr
33
1
K
CL
c
34
D
S
c
35
9
1
in
36
*
Z
.
37
T
E
38
1
s
39
M
8
40
E
0
41
=
42
1
43
44
45
46
47
48
49
50
51
52
53
54
~J
I-1
OJ
-------
AUTHOR TRC
PROGRAM NAME CDS EDIT
Using' ALPHA to submit both Job control
1
/
/
/
Al
tl
c
Tl
A]
2
/
/
/
,PF
e
o
e
J>1
3
E
C
E
A
ab
M
ab
1A
4
P
D
D
r]
JV
M
)V
w
5
A
S
1
if
A
i
1
6
•
1
E
T
e<
N
tLP
i
7
•
1
D
OI
D
HA
es
1
•
1
1
C
ds
po
9
T
A
?
:o
id
10
R
mi
w:
11
D
S
IK
tl
12
J
E
S
u
w
S
V
•
1
a
n
X
13
O
X
1
B
11
b
ie
•
1
a
X
14
B
E
N
M
L
it
:e
•
1
a
is
c
1
>1«
:h
a
16
(
D
T
ce
Jc
17
a
c
D
t
t
>
Iff
Is
1fi
18
a
D
M
ie
lu
f
f
f
19
a
s
*
o
ii
ib<
IP
IP
IP
20
a
I
D
P«
r
11'
u<
lU
21
r
P
E
t
ic
PT
PT
PT
IN
22
•
1
T
=
tr
r
's
's
i
'R
?u
23
•
n
B
in
:h
f,
]
* t
24
•
1
i
iai
> I
•61
'mi
I(
'0
and
25
t
R
t:
d:
•)!
at
ff
UP
CI
26
1
0
or
t
•ff
on
ti
E
S
data
27
)
£
U
3
Pr
if)
in
If
7-
Ji,
21
i
•h
T
o
>g
fl
\
on a ALPHA
29
1
Of
E
ei
ai
in
pi
fYI
30
U
l
~
he
.
hr
Pf
Bl
31
S
f*r
X
r
!•
f
i
32
E
D|"
X
*i
pr
33
R
h
i
:h
rf
data
34
^
P
tl
if)
35
1
<^f
R
e
f
36
D
f
T
J(
HIT
set in
37
1
IP
Y
j
IP
38
i
39
T
order to
40
1
INSERT
=
.n
B
4
0
f
tl
41
M
r
S
e
42
E
im
E
ja
43
=
nai
Q
:cl
run
44
1
d
U
45
rr
E
ot
TASK NUMBER
the Edit.
46
a
N
s
47
rlri
C
tr
48
E
:ai
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.
A
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 is not copied to
the output Masterfile.
4. For an action delete, input Masterfile records with the same
Region, State, County, Source, Point, and Action numbers as the
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. IRC 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
8-4
-------
03/23/78
StATt
cunt
0
34
33
33
33
Ji
33
33
33
33
33
33
33
33
33
33
33
33
33
» 33
1 _ .
Oi 33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
33
CMt
CUOb
5o7B
I62U
1620
1620
1620
I62U
1620
1620
16211
I62U
1620
1620
ti-20
1620
1 b2«
1620
1620
Ib2o
Ib2o
Ib20
162U
1620
1620
1620
1620
1640
1620
1620
Ie2n
Ib2o
I62o
1620
2000
2000
2POO
2000
2i>20
2020
2(i20
2020
2020
2o20
2020
2»2o
2020
2»?0
2020
SUURCE
CODE
1
9UI23
00033
OOOJU
00034
00036
HOOI6
00036
00040
OU04U
00041
HOU42
00042
00043
00043
00050
00058
oooen
00060
OOObl
00061
00062
00062
00064
00064
OOObb
00065
00066
00066
00070
00070
00074
00074
00004
00004
00037
00174
00001
00001
00001
00003
00003
00001
00004
00004
00004
0000%
00005
En
PI
4b6
000
nuo
000
ono
ooo
ono
noo
ooo
000
ooo
00(1
OHO
ono
(100
ooo
ono
ooo
ooo
ooo
01)0
000
ooo
000
000
000
000
000
ono
000
000
000
noo
000
000
ooo
000
000
000
ooo
000
000
000
ooo
000
nuo
ooo
hfblUN 2-'»t» TllHN
UUIPUl SkrtlAL OOU331
FACE e
AC1 CAKD IIPU1 I'PT.AlE EhkUK
NU CODE (.AMD CULUMNSl CLDE ALIIUN »tS3AbE
2 3 t •> 6 7 B
7B 9 (M«!34:>67B9(il?i4beffl'H)l234!>67B«»oi2J4b6;B90l2iMb6/«D
B063
Ib
410H2 42 I3b
240N2 4| 46
4
7
3()bN2 41 69
1
SBN2 44 b
30N2 44 2
1
33N2 44 10
1
1
5BN2 44 9
3bN2 44 2
1
1
S7N2 44 4
1
4n2 44 3
1
27N2 44 2
N2U
307
ION2 43 IB4b
CURH
ALLIED LHEXICAL/StHET 9ULVAY.
10
ICU 44
3SS2 42
run
82
4BS2D
CLI)
1
1093
3
227N2 41 47
2951
N2U
2B3I
1S22
2H34
N2D
C
C
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
c
I
c
c
c
c
c
c
c
c
c
c
c
N
c
c
c
c
c
c
c
c
c
I
c
c
c
CHANGE!,
CHANGED
ChANIiED
CHANGED
CHANGED
CHANGED
CHANbtU
CHANGED
CHANGED
CHANGED
CHANGED
CHANbt'D
CHANGED
APDEP
APliEli
AODFP
ADDED
ADDED
ADDED
ADDED
ADDED
ADDED
ADDED
ADDED
ADDED
AliUED
AP.DEO
ADDED
ADDED
ARDED
ADDED
CHANGED
REJECI ALhtADY CM ft
CHANGED
CHANGED
CHAfGED
IPAKbED
CHANGED
CHANGED
AOUED
ADDED
CHANGED
CHANGED
CHANGED 11
CHANGED
CHANGED
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 sane 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
ALREADY ON MF
98 ON MF
&(AMPERSAND)
S2 REJ
Explanation
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 Lhe following steps:
1. Follow the standard WCC sign-on procedures by typing in
the user account, initials, keyword, and terminal
identifier.
2. As soon as ALPHA gives the prompt, COMMAND?, type in
the following and then hit the carriage return:
LIST CN.EPAEXC.A026.CDS.SYSOUT
3. Figure 8-2 shows the contents of the log produced by fol-
lowing the above steps.
8-9
-------
00
I
wccalph
'REAPY-TO-WPP1
it
ALPHA System at COHNET
PI.FASE ENTER: user I rt, password, account, tprrn Id
FPAEXr/A026 on line 5 at 16:i»0:27, 02/27/78
2-21-78 JOBS WITH PATA SET CONTENTION
T
? Hst .crts. sysout
ooooooooooooonoooooo
UPPATF RFPORT PRINT-MMFS FOR
UPPATF RFPORT PRIMT-IINFS FOP
UPPATF REPOPT PRINT-IIMFS FOP
UPPATF REPORT pniMT-IIMFS FOR
UPPATF RFPOPT PPINT-MMFS FOR
UPPATF RFPORT PRIMT-I.INFS COR
UPPATF PFPOPT PPINT-LIMP«> FOR
UPPATF RFPORT PR I HT-I.INFS FOP
UPPATF RFPORT PRINT-IIMFS TOR
UPPATF PFPORT PRINT-IIMFS FOR
UPPATE FINIS»FP AT 022fi
MASTER FIIF OUTPUT SFRIAL 000325 ON 02/23/78
RFPION
REPION
RFPION
REPION
RFPION
RFPION
RFPION
RFRION
PFniON
RFPION
01 =
02 =
03 =
f)l| B
05 =
06 =
07 =
08 =
09 =
10 =
00000
00113
005R9
07122
0033U
00331
01598
0001)7
01268
00000
RFPORPS
PFPORPS
PFPORPS
PFCORPS
PETORPS
RFPORPS
PFCORPS
RFPORPS
PFPORPS
RFPORPS
IM PI IT
INPUT
INPUT
INPUT
INPUT
INPUT
INPUT
IMPIIT
INPUT
INPUT
= 00000
= 00089
= OOUH4
= 0561)6
= 00262
= 00259
= 01262
= 00035
= 01001)
° 00000
ACCFPTFP
APCEPTFP
APPEPTFP
APCFPTFP
ACPFPTFn
APPFPTF.P
APPFPTEP
APCFPTFP
ACP.FPTFP
ACCEPTEP
= 00000
= 00089
* OOU39
= 05555
<* 00220
° 0025U
= 00116
= 00033
= 0091)5
= 00000
RE.IEfB
RFJFC-B
REJCfl
RF.IFP1
RFJFP1
RFJEPl
RF.IFPl
RF.IFP1
RFJFC-B
REJECT
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
-------
on
I-1
ro
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 Che CDS Update Report for a given region.
7
R
•
P
1
1
i
T
9
T
10
Y
11
12
J
E
Wh
•
a
n
13
O
X
er
•
i
a
14
B
E
s:
•
i
a
15
C
a
16
4
(
17
a
C
Ls
is
is
18
a
D
t
t:
t
19
a
S
ie
te
ie
20
a
R
U!
U!
U!
21
i
P
ei
ei
ei
22
•
T
's
's
's
:D
23
•
1
n
r
; i
24
•
•K-
PI
25
)
it
a<
01
&1
26
1
it
cc
r
FI
E
27
i
La
Lin
urn
;u
IE
21
U
.s
>e
E
0
29
S
1UI
1
8-
T
30
E
be
tl
3
JO
31
R
r
e
J
32
va
:o
33
Li
III
34
D
>
01
35
t
a]
36
i
ue
37
T
s
38
1
ir
39
M
i '.
40
E
t
41
=
tir
42
1
>u
43
?h
44
1«
45
•
46
47
48
49
50
51
52
53
54
55
56
57
1
.
1
-------
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 ALPHA. 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 20,009 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 b£ used as a selection criteria.
Since the selection, sorting and printing criteria in the Retrieval
Program operate independently, the user may select a report on one set of
data elements, sort on another set of data elements, and select different
data elements for printing. Selection criteria cannot be based on infor-
mation found in comment records. If none of the nationally defined data
elements meet the user's selection criteria, one of the Regional Data
Elements should be used to facilitate retrieval selection.
Reports are printed in Region, State, County and Source Number
sequence unless the user selects his own sorting sequence. Up to six
data elements, other than comments, may be used to create the user sort
sequence.
The Source Data Report, the Questionnaire Report, the Action Summary
Report, and the Milestone Report will present user selected and sorted
information in a fixed format. The Quick Look Report allows the user
to design his own report format. All data elements other than comments
can be formatted for printing in a user selected sequence. A detailed
description of each Report is provided in the following paragraphs.
9.1.1 Quick Look Report
The Quick Look is the most widely used report type available from
the Retrieval. For each source, point, or action which meets the user's
selection criteria, a single line containing user-selected data elements
is formatted for printing. The user may specify what data elements are
printed, and also he may specify the spacing of these data elements.
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:
BLK1 produces a blank column five characters wide; BLK2 produces a blank
column 15 characters wide. These two data elements may be used repeatedly
for spacing as required. BLK1 and BLK2 are especially useful when the
Quick Look is used as a turnaround document.
If the user does not wish to see repeating data, the suppression
option can be used. Using this option, source level data will print
only when there is a change in data to be printed at the source level.
Point level data will print only when a new point is to print. Action
level data will always print.
Note that if only source and point information have been requested
on the Quick Look Report, only source level suppression will take place.
If only source level data has been requested no suppression will occur.
Figure 9-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 facilities which have had major
compliance actions.
Sorting was based on Source Name.
Pring line selection was based on the following data elements:
Source Name, City, State, Emission Category, Compliance Status, Action
Description, Date Scheduled, and Date Achieved.
9-5
-------
UUICn LUMi
"cnhPLiANLE'i>A1A'bYSUN
oj/21/78
PAI.E
ST CNIY
la 6100
la oiuo
la 6ioo
la 3HOu
la IMIO
11 1B10
la abao
la abao
la IMIII
|1 1B10
la aaau
la 4840
11 1B10
la IBIO
14 4B4U
la IBIO
la IBIO
li abao
vo la IBIO
^ ia aaao
li aaio
11 aaao
ia ieio
la aain
)1 UM10
11 1810
11 1(<10
la 1810
la abao
la IMIO
14 1810
14 4810
la ieio
|U 4810
la aaau
la abao
la aaao
11 IBIO
la IBIO
la 4810
ia 4H40
la abao
14 4010
la aaao
la aaio
la aaau
ia aauu
SHCt
OOOII
OOoll
00011
00003
80oo2
80002
80002
80002
80002
80002
80002
80002
80U02
80002
80002
80002
80002
80002
80002
80002
BOOU2
80002
80002
80002
80002
80002
80002
B0002
80002
80002
80002
00002
eooi'2
80002
800U2
B0002
8ooo2
euoo2
80002
80002
00002
80002
80002
80002
80002
80002
80002
tP AN bUUHLt NAHt
000 03 ASHLAM) CHEMICAL
000 oa A3hL»M> ChtnlLAL
000 05 ASHIAMJ CHt«IL»U
000 01 AIIHUHA PAPtHBUAHU
010 01 B F GUUUHRH
010 02 h f bUUUHlCH
010 Ii3 B F bUUUHlCH
010 II S B 1- bnuUHUH
020 01 B F GUIUIHICH
020 02 H F GUDUHICH
020 03 U F bUOUHlCrt
020 OS H F bUUUHlCH
030 (II B
050 03 H
030 oa a
030 06 U
oao iii H
oao 02 B
oao o3 B
oao oa B
OH HI B
OU| 02 B
Oil U3 B
on oa H
042 01 B
012 02 B
042 03 B
012 oa B
050 01 B
05o u2 H
OSfl 03 B
OSn oi B
060 ul B
060 02 B
060 03 B
060 1)4 H
07 II 01 H
070 02 B
070 03 H
070 oa B
08(1 Ul U
080 02 H
oeo 03 H
oeo oa B
04o 01 H
040 02 H
09u 03 I*
GllUDHICH
faUUOMICH
bOUUHlCH
bUUOHlCH
bUUUHlCH
bUUOHICH
GUUUHlCn
bUUUHlCH
bUUDhlCH
GllUOHICH
GUUUHICH
GOUUHILH
GUUUHICH
GOUDHICn
bUUUHlCH
GUUUHlCn
bUCUHICH
GUUURICH
GUUUHlCn
bUOUHIC'1
GUUUHICH
fiOliDklCH
GUOUHICH
GUUURICH
GUUUHlCn
bUUUHlCH
GUUUHICH
buUUHICn
GCUUHICH
GUUUHICH
GLODHICn
GOUOrtlCH
GUUUHICH
GOUlJRICH
GUUUMIC"
CITY NAHt
PAPLtTUN
MAHLt TUN
PAPLtlllN
AUHIJHA
HENHY
HENRY
HENHY
HENHY
HtNRY
HtNHY
HtNHY
HtNHY
HENHY
HENRY
HtNHY
HENHY
HENHY
HtNHY
HtNHY
HENHY
HtNHY
HtNHY
HENHY
HtNHY
HtNHY
HtNHY
HENHY
HtNHY
HENHY
HtNRY
HtNHY
HENHY
HtNHY
HtNHY
HtNHY
HtNHY
HtNHV
HENRY
HENHV
HfcNHV
HENHV
HENHV
HENRY
H£NKY
HENHV
HENHY
HtNHY
SI
IL
IL
IL
IL
IL
IL
U
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
U
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
31L
2894
2B9a
?B94
264b
2821
2821
2821
2821
2821
2821
2821
2821
2821
2821
2621
2821
2821
2821
2821
2821
2821
2821
2621
2821
2821
2821
2821
2821
2821
2821
2821
2H2I
2821
2821
2821
21*21
2621
2821
2821
2821
2821
2821
2821
2821
2621
2821
2821
tCAT
3
J
3
1
0
0
0
0
u
0
u
0
0
0
o-
u
0
u
u
0
0
0
0
0
0
u
0
u
u
u
0
u
u
u
u
0
0
u
0
0
0
u
0
u
0
u
0
C»>S1
1
1
1
a
0
u
0
0
0
0
u
0
0
0
0
0
0
0
0
u
0
0
0
u
u
0
0
0
0
0
u
u
0
0
0
0
0
u
u
0
0
0
0
0
a
0
0
ACIIllK I'tSCHIP
NEFEH 10 US ATT
114 HtPLY HLVO
114 LEITtR StNT
114 LtlTtH StNT
PUHCHASt EUUIP.
START CONST.
fcNU CO8TR.
FINAL COHPL.
PUHCHASt tOLIP.
STAHT CL-NST.
tNO CCNSIR.
FINAL COHPL.
PUHCHASt tUUIP.
START CONST.
tM) CLitSIK.
FINAL COHPL,
PUHCHASt tUUIP.
81AHT CONST.
ENU CUSTH.
FINAL CUHPL.
PUHCHASt tUUIP.
START CONST.
fcND CCNSIR.
FINAL COHPL.
PURCHASE tUtlP.
SlAHT CONSI.
END CCNSIH.
FINAL COHPL.
PURCHASE EUUIP.
STAHT CONST.
END CCNSIH.
FINAL COHPL.
PURCHASE tUUIP.
STAHT IUNST.
tM) CCNSTH.
FINAL CliHPL.
PUHCHASt tOUIP.
START CONST.
tNU CCK8TN.
FINAL CUHPL.
PUHCHASt EbUIP.
SlAHT CUN8I.
ENU CCNSIft.
FINAL CUHPL.
PURCHASE EUUIP.
STAHT CONST.
tM> CCNSIR,
cm sen
05/01/78
00/00/00
00/00/00
01/OB/7b
OE/OI/77
04/01/77
01/01/78
07/01/78
09/15/77
Ot/l'S/78
OS/01/78
10/21/78
07/01/77
11/01/77
04/01/78
Ot/01/78
04/01/77
05/01/77
12/31/77
12/31/77
10/01/77
02/01/78
07/01/78
07/01/78
10/01/77
02/01/78
07/01/78
04/01/78
12/01/76
02/01/77
Ot/01/78
Ot/01/78
12/01/76
01/01/77
04/01/78
1C/21/7H
11/15/76
12/01/76
01/01/77
Ot/OI/77
02/15/77
03/01/77
10/01/77
01/01/78
05/01/77
07/01/77
07/01/78
OATt ACh
/ /
1 1/16/77
10/06/77
/ /
04/05/77
Ob/|2/77
/ /
/ /
07/12/77
/ /
/ /
/ /
07/01/77
11/15/77
/ /
/ /
04/22/77
OB/01/77
12/31/77
12/31/77
10/15/77
02/01/76
/ /
/ /
IO/lb/77
02/01/76
/ /
/ /
04/JO/7t
09/26/76
/ /
/ /
12/111/76
01/01/77
/ /
/ /
11/15/76
12/01/76
01/01/77
05/12/77
oa/29/77
08/01/77
11/11/77
01/01/7*
OU/09/77
07/01/77
/ /
FIGURE 9-1
SAMPLE QUICK LOOK REPORT
-------
UUICH LIKIN HtPlJMl
US/2J/76
tOnPLlANCE DATA SYSItM
MAJOH ACTIUNS fUH FY7M
PAGE
SOURCE NAME CIIY NAME
ASHLAND CHEMICAL MAPLETON
AUMUMA PAHEHUUAHO AIJHOHA
B F GUOURICH HENRY
\o
1
o\
>
si aic HUNT PNULtss DESCRIPTION tCAi
IL 2b
-------
QUICK LOU* REPURI
03/23/78
ST CNTY
10 moo
10 6100
10 3800
la asao
10 0800
lo aeao
10 0800
la OBOO
la 0*00
10 0800
to oeon
|o aeao
la oeoo
la oeoo
la OBOO
to asao
la aeao
la aeao
14 0800
14 0800
la aeao
la oeoo
la aeao
la oeoo
SRCE
00011
OOOll
00003
80002
80002
80002
80002
80002
80002
80002
80002
80002
80002
80002
80002
80002
80002
80002
80002
B0002
B0002
80002
80002
80002
EP
000
000
000
010
010
010
010
020
020
020
020
030
030
030
030
000
000
000
000
041
001
001
001
002
AN
COMPLIANCE DATA SYSTEM
MAJOR ACMONS FOR FV7B
SOURCt NAME
00 ASHLAND CHEMICAL
OS ASHLAND CHEMICAL
01 AURC
01 R F
02 B F
03 B F
05 B F
01 B F
02 B F
03 B F
OS 8 F
01 B F
03 B F
00 B F
06 B F
01 B F
02 R F
03 H F
00 8 F
01 B F
02 B F
03 B F
04 B F
01 fl F
IRA PAPENBOARD
GOODRICH
GOODRICH
GOODRICH
GOODRICH
GOODRICH
GOODRICH
GOODR'ICH
GOODRICH
GOODRICH
GOODRICH
GOODHIIH
GOODRICH
GOODRICH
GOODHICH
GUODHICH
GOODRICH
GOODRICH
GOODRICH
GOODN1CH
GOODRILH
GOOOH1CH
CITY NAME
HAPLETON
MAPLbTUN
AURORA
HENRY
HENRY
HFNRY
HENRY
HENRY
HENRY
HENRY
HENRY
HENRY
HENRY
HENRY
HENttV
HENRY
HENRY
HENRY
HENRY
HENRY
HFNRV
HENRY
HENRY
HENRY
ST
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
IL
SIC ECAT CHST ACMOK OESCRIP
2894 3
289a 3
2605 1
2821 0
2H2I 0
2821 0
2821 0
2821 0
2821 0
2821 0
2821 0
2821 0
2821 0
?B2I 0
2B21 0
2821 0
2821 0
2821 0
2821 0
2821 0
2821 U
2821 0
?B2I U
P«2I 0
,
1
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
U
110 HEPIY RCVD
110 LETTER SENT
114 LETTER SENT
PURCHASE EQUIP.
START CONST,
END CCKSTR.
FINAL COMPL.
PURCHASE EQUIP.
START CONST.
END COS1R.
FINAL COHPL.
PURCHASE EQUIP.
STAR! CONST.
END CCK8TR.
FINAL COMPL,
PURCHASE FQL'IP.
START CONST,
END CO8TR.
FINAL COMPl ,
PURCHASE EQUIP.
STAHT C'lNST.
END CC^SIR.
FINAL Cl'MPL.
PliMCHASK E.UIMP.
cm sen
00/00/00
00/00/00
04/08/75
OP/01/77
09/01/77
04/01/78
07/01/78
09/15/77
06/15/76
01/01/78
10/21/78
07/01/77
11/01/77
00/01/78
06/01/78
04/01/77
fl«/fl|/77
12/31/77
12/31/77
10/01/77
02/01/76
07/01/7B
07/01/78
lfl/n|/77
PAGF. 3
DATE Act-
11/16/77
10/06/77
/ /
00/05/77
OB/12/77
/ /
/ /
07/12/77
/ /
/ /
/ /
07/01/77
11/15/77
/ /
/ /
00/22/77
OR/OI/77
12/31/77
12/31/77
10/15/77
n2/OI/7e
/ /
/ /
10/1S/7/
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
-------
IJAIA Ktl'uM)
03/22/7«i
SPMlNbF ItLU H.
IjNUHY HAJOh
r-AbbACnubET Ib bIJUKCbb HUl
UF CUfPl |ArtL
SIAIt MA LLUNTY PIONEfcM VALLEY
lUUNl* I79B sruHCE OUII3I AUCN UU2 Lilt 2lbll
SOUKCE NACE
AOOHESS
CITY, SIAIfc
SPP-iNtiFiEi o FUUNOHY
2<»b PASCL hi)
INDIAN
UKLHAHU
tbllNbS
FACILITY CAPACITY
POLLUIANl
PI PAHT. MAlltH
HC HYUMllCAND
MA oiubi
HUE «
CUMPLIANCt
3 IN COMPL-
(JNS • B NU APPLIl
CO CAhbON ML-NUllUE
PUlNl NUMBER
PULLUIANI
DbSLHIPTION
ACTION
ACTION
ACTION
VO
1 ACIION
\0
PUlNT NUMbEH
PULLUTANI
000
ENTIHE
III SCHU
02 SCHD
03 SCHU
Oil SCHU
001
PT
MULT
SLUNCE
b/H/7b
6/20/70
3/21/77
3/2b/77
MULT
b NU APPLIL
ACHV
ALMV
ACHV
ACHV
SlAie HtGISI
NEDb XKtF
PhluMlY
INSPtCIION
SIATE Ktli
SIAIE HtG
SOUHCb CMPL 1
SUUHCb-SIP
NEDS XM^F
b/12/76 ACT-TYPE
6/2H/76 ACr-lYHE
3/23/77 ACI-IYPE
1/2
b/77 ACI-TYPt
POINT CMPL b
PUINT-S1P 2
HUt 10
b^IbbluN
U UNKNUflN
0
U
NOT
UNKNUtiN
UNKNOIoN
SIC
HOE<4
hubb
CAIbGOHV
IN COMPL-NO SCHO
NUI SPECIFIED
07
07
52
u7
IN
STATE
STAFF
bl A It
STAFF
INbPbCllON
1NSPECIION
t FtDF
APCU
APST
3321 HDfcb
STAFF
LAST-
HOE It
ABCH IKOICATLK
N NllN-ATT AINKF NT
N KUN-ATTARUNT
STAU/LOC RbCUL
PAGE 9
KLN-FED won
0 S1F SOKNCt ROE2
HHES
f tfHtN
UPDAIE I!/ 7/77
HUE 12
AUPA INUICATOH
NO
KU
Ml
BOUNCE EPI3 CAT 2 100 TO 1000 TPY
SLCtl CODE
NtSLLTS
NEbLLTS
01 ACTION ACHIEVED
01 ACIION ACHIEVED
1
LLAI1JNG
A1K2
hUfc?
Hl/EO
HUED
EPA INbPECTION
SIAFF
STATE
STAFF
COMPL H
INSPbCTION
SCHEDULE
AHPKOVED STATE SCHED
HESLLTS
KESULTS
3IAIE/I.OC REGliL 2.S
HI ACTION ACHIEVED
01 ACTION ACHIEVED
PT EM1S CAT 0 UNHKUnK
NUtB
HDFO
A1R2
HUE?
UtSCHlPTION (.HAY 1HLIN CUPOLA NtDS XMEF SCCH CODE lOdOOJ
LUMMtNl | CUNIKUL EUUIP. INbTALLfcU & WILL BE OPERATIONAL 7/76
2 INUN.SCHAP STEEL,SILICON,COKE,LIMESTONE
3 SCMUbbbH IS PRESENTLY LPEMATIONAL
ACTION 01 bCHD 9/3U/73 ACHV 11/27/70 ACT-IYfE u|
ACIION Oi SCHD J/10//U ACHV / / ACT-TYPE U4
ACTION OJ SCHO V/JO/7<4 ACHV / / »CT«TYPt D3
AC HUN 01 SCHD i/ i/7b ALHV / / ACT-IYHE an
ACTION os 3CHO «/ 1/75 ACHV / / ACT-TYPE ob
SUUN1SS10N C> FINAL LCMHOl PLAN C
STAFt HESLLIS U
BlNUlsli COMMITMENT 10 (-UKCMA3E CCMHOL fcGUIFMbNl C
blAFF HESULTS 0
1NMIA1IOK 0^ ON SITE CONSTRUCT ICN/PHUCeSS CHANGEC
SIAKK KESULTS 0
COHPLkMUN 0>> ON SHE CONSTRUCMLK/HNUltSS CHANGEC
STAFF HEStLTS 0
FINAL COMPLIANCE C
STAFF htSULTS U
HUt* U
HUtB U
HUED 0
HUE« o
NUtt) 0
PUlNT NUMUEH 002 MULI 001
POLLUTANT Cll
UtSCHIPMUN bNAY IKON COPOLA
POINT CnPL
POINT-SIP
NEDS >HtF
6 NU APPLIC 31AIE NEC
NUT SPEC1FUU
SIAIE/LOC RtCLL
PT EMI3 CAT 0
SCCB CODE 100003
Alh2
HUE/
PUINI NUnutH no] ruLI
PULLUTANT PI
DLSCHIPIION SAND bLASTING
POINT CnPl.
POINT-SIP
NfcUb
3 IN COnpL-lNbPtdlLN
NUI bPEClFIEU
SIATE/LOC RECLL 2.S
PT tM|b CAT 0
SCCa CODE 3U40U3
A1H2
AUE7
FIGURE 9-3
SAMPLE SOURCE DATA REPORT
-------
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
-------
MILESTONE KtPOHT
>M*t*t*«i
03/22/78
COMPLIANCE DATA SYSTEM
REGION V NSPS COMPLIANCE MILESTONE
PAGE
COMPLIANCE STATUS
COMPL STATUS UNKNOWN
A UNK COMP w PROC ROTS
B IN VIOL OF PRCC ROTS
C IN COMP W PROC ROTS
0 COMPL STATUS UNKNOWN
1 NOT IN COMPL-NO SCHO
2 IN CUMPL-SOURCE TEST
3 IN COMPL-INSHECTION
4 IN COMPL»CERTIFICATN
5 IN COMPL w SCHEDULE
6 NOT IN COMPL ft SCHO
TOTALS FOR 2,3,4,9,9
TOTALS FOR 1 AND 6
TOTALS FOR 0 AND 7
GRAND TOTALS
REGION 5 ILLINOIS INDIANA MICHIGAN MINN
TOTAL 14 IS 23 24
FIGURE 9-4
SAMPLE STANDARD MILESTONE REPORT
OHIO WISCONSIN
36 91
16
11
37
1
73
5
1
116
12
16
144
11
4
10
0
17
3
0
30
«
11
45
a
4
0
1
21
0
0
22
4
4
30
0
0
17
0
9
0
0
26
0
0
26
1
0
5
0
5
U
0
10
U
1
11
0
2
5
0
13
0
0
1ft
2
0
20
0
1
0
0
e
s
t
10
2
0
12
-------
MILESTONE REPORT
03/23/76
ACTION DESCRIPTION
END CONSTR.
FINAL COMPL.
NOV ISSUED
PROG RPT TO EPA
PURCHASE EQUIP.
voREFER TO US ATT
£START CONST,
lid LETTER SENT
no REPLY RCVD
REGIONAL DAVM TOTALS
REGIONAL AOES ITEMS
MAJOR
REGION 5
TOTAL
33
37
36
39
16
30
35
«7
30
303
9
COMPLIANCE DATA
ACTIONS FOR FV78
DAYM
7710
2
3
10
16
5
1
6
5
6
54
DAYM
7711
9
3
9
2
6
2
10
7
4
52
SYSTEM
DAYM
7712
8
11
9
11
a
17
7
7
6
SO
DAYM
7801
6
13
6
e
0
7
5
9
6
60
DAYM
7602
6
6
1
2
1
3
a
17
5
45
PAGE
OAYK
7603
2
1
1
0
0
0
3
2
3
12
Figure 9-4A
Sample Variable Milestone Report
-------
9.1.5 Questionnaire Report
This report has been used by some regions for direct reporting
by State Agencies. The report format provides a turnaround document
used to report 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
r
r
—
i _
-
05/25/76
POINT SOURCE
IDENTIFICATION
TWIN FALLS
1460
AMALGAMATED SUGAR
STftTE REGISTRATION
TWIN FALLS
1460
AMALGAMATED SUGAR
BP_LEVUE CITY
NO CITY CODE
ANDERSON PAVING"
""CTA'TE "KEGrSTRATTON
01 80-0003
TWIN FALLS
1460
&EYMER PAVING
STftTE REGISTRATION
COMPLIANCE DATA SYSTEM QUESTIONNAIRE
FOR STATE OF
I L'HHu
STATUS CODES 1-AUI1UN ACHIEVED 2- ACT I ON NOT ACHIEVED
EMISSION POINT. STATE /LOCAL REGUL, SCHEDULE INCREMENTS
"POLLUTANT EMITTED CONTROL PROJECT, Of- l-'KUljKkSS
POINT SIP
CSF BOILER REGULATION G 6/30/76
UIMtK IVPE Avi IUN< Stt
-------
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 sample of the Compliance-Action Report. It is available
by coding "CA" on the Report Format 20 Card. The left side of the print-
out contains basic source information such as Source Name, AQCR, City, State,
and Staff Member for the sources selected by the retrieval. The middle
columns contain the Point Number, Compliance Status, and Emission Category
.of the points selected by the retrieval. The right side of the printout
contains the Date Achieved for nine specific action types:
o Federal Inspections
o State Inspections
o Federal Notices of Violation
9-14
-------
ACTION SUMMARY RETrtRT
05/25/76
TYPE OF ACTION
EPA INSPECTION
STAFF MEMBER
AND TITLE
R CELL AM ARE
ENGINEER
V PTTRUZZELLO
ENGINEER
V PURUZZELLO
ENGINEER
[V PITRUZZELLO
ENGINEER
V PITRUZZELLO
ENGINEER
COMMENTS
V PITRUZZELLO
vo ENGINEER
^ COMMENTS
Ul
rv PITRUZZELLO
ENGINEER
COMPLIANCE DATA EV-.TEM
ACTION SUMMARY FOR ACTION1?. > 50
SOURCE NAME DATE SCH
AND LOCATION DATE ACH ST ATI'S CODE
CERTAIN-TEED PROD INC 4/ «/75 01
WINSLOW TWP NJ 4/ 9/75 ACHIE';KD
SUSSEX ROAD MATERIAL 5/14/75 01
ANDOVER TWP NJ 5/14/75 ACHIEVKD
SUSSEX Ri'AD MATERIAL 9/30/75 01
ANDOVER TWP NJ 9/2«/75 ACHIEVED
SUSSEX ROAD MATERIAL 5/ 3/7«>
ANDOVER TWP NJ / / UNKNOWN
ANDOVER INDUSTRIES 5/14/75 01
ANDOVER TWP NJ 5/14/75 ACHIEVED
1 BORDERLINE COMPLIANCE
ANDOVEF INDUSTRIES
-------
t-ACI ILi'l ktPUKI
03/22/78
SUUHLb NAME
CITY bl
MILAN NM
HkMH.MCObE
bHANIS NM
niHbVNULUS LIINS1
IUIAVI NM
N.Kfc N SUUlHhbSl INC
CAHLbbAU NM
N.Ht N SUUlHKtSl INC
CAHLSbAU NM
NAVAJU FUHtST PHLIU,
NAVAJU NM
NAVAJU HtFlNING LO,
ANIESIA NM
UTEHU MILLS INC
ALAMUGUHUU NM
PtCUS HEFIMKb Cli
PHbLPS OUObb CLHP.
PLAYAS NM
PlUNEFH LOb'lilNbKMlLL
IAUS NM
PLAINS tLEt bEMIHAN
ALbUHQNbS NM
PUBLIC SbRv. OF N.M.
"AlbHFLU* NM
PUHLlC SbhvlLE»N.M.
MAlbHFLUx NM
HHUUkS PUMICE
SAKTA Fb NM
SILUHILU
"U AbUA NM
TMMIFT.At HbFIMNG
AUCH
AlMl
1*6
A
1*7
N
N
15S
N
014
N
N
IS}
N
N
012
N
157
N
01U
N
Old
N
1S7
N
N
OH
LilnPLIANlE DAlA SYSTEM PAbt 22
Fv7H LUnPLlANlt ALIliiNb
SIAFF PTNli CChPLIAfiLt blAluS INbPbCHUN MilICF. OF OhllbH CILM H Hl> Jl> A 1 IUI>
k»lbSI(.N LAlfcb'UHY VIULAMCn ISSUbC «C1ILN OF ItUV
SlAN bUHbbH
STAN bUHbbH
S. SPHUULL
b, SPHUibLL
SlAN BUKOtH
SlAN HUNbtH
3lAn bUHbbH
alAN BUHbbH
SlAN bUHbfcH
3IAN UUHbfcK
SlAN bUHbtH
alAN HUHCtH
S. SPHUULL
SlAN bUHbbH
SlAN bUHbbH
SlAN tlUHbbH
2
od o u
2
oOo 5
2
000 I
2
001 1
2
lion 3
2
000 S
1
000 9
2
ooo i
I
000 5
3
000 J
2
000 8
2
ooo i
i
001 H
2
oou 2
000 2
2
000 S
IUU Til 1000 TPV
IN CL'MPL-CfcKI IF
1UO TU 1000 IPY
IN CL'MPL H bCHfc
100 IU 1000 1PV
Mill IN LOMPL-NU
100 IU 100(1 TPl
NU1 IN CUMPL-NO
100 IU 1000 IPY
IN CCMPL-lNbPbC
100 TU 1000 IPY
IN CLnPL N 3CMt
LIVtH 1000 IPY
IN CLMPL-SHUl 1)
loo lu looo TPY
NUI IN LUMPL'NU
LESS IHAN 100 I
IN CQMPL » iLME
OVbH 1000 IPV
IN CCMPL-lNSHbC
100 IU 1000 TPY
NU APPL1L SIAIE
100 TU 1000 TPV
NUT IN CUMPL'NO
IIVEH 1000 TPY
101) IU IOOU TPY
IN COMPL»bUUP.CE
100 IU 1000 IHY
IN COMPL-bUuHCb
100 111 1000 TPY
IN LUMPL » ithb
SlATb
SlAlb
FtUbHAL
SlATf 12/22/7;
STATb
FEUtHAL
blATb
FbUbHAL
blAlb
FEObMAL
STATb
FEUbHAL
STATb 12/30/77
FEDbHAL
STATE 10/27/77
FEUbHAL
SlATb 1/30/78
(•tUt HAL
STATb
FEUbHAL
SlATb 1/31/70
FbUbHAL 12/16/77
SlAlb It/21/77
blAlb
FEDbHAL
SlATb
FfcObhAL
SlAlb
Fbl)EH*L
Figure 9-6A
Sample Compliance-Action Report
-------
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).
A. 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 "4(3" 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
I Oil I I i I II I ....
IJL 4 $ 7 f
TIN*
11,01 I.I.I 1_J I
I Z 4 7 I 11
U L
11.01 (_
11.01 i
J LJ U.
term mmus
I 2
13.01
124 7 S
UNIT sioonet
Dole-Submitted ^_
Return Report To.
Mail
2B
II
CONDITION CODES (10 CARD)
M - MOST EQUAL
A — ALTERNATE *
U - UHEQUAL
G" - EQUAL OR CHEATER THAN
L - EQUAL OK LESS THAU
P — PRESENT ANY EN'l'KX
B ••• BLANK OR ZEROS
*Used for onilciple values
of a data element
See reverse side for a
Use of all CDS data
fiburev lacioos •
?*rTi
REPORT FOSMATS (20 CARP)
QL - QUIC2C LOOK
SO - SOTJSCS DATA REPORT
AC - ACTION" SUMMARY
QT - QUEST10NNAXHE.
MS — MILESTONE
Q2. - DOUBLE SPACED QL
CA - COMPLIANCE-ACTION
LEVEL CODES fni
S - SOURCE ONLY
P - POBTT AND SOURCE
A.-ALL DAZA
C - i-ui'ivm* MATCH OHLY
LOOK IIWT OMIT
U.Ol l_j
1 2 4
I . t . I I . , , I
22 24 27 29 12 14 17 » 42 44 47 43
79 12. ' 14 17 19
Enter Data Elements left to right in the lame wquenee as required an report
Tk*. l*4«iratt ««OI NIUITOIC ItFOtT OMIT
15. Ol
124 7 * 12 14
tews COIUMMI
DATA OATA
IIIMINT lllMINt
17 19 22 24 27 29
OSIUMN VALUII
SINK urfD »«• VAUII "HANK*
FIGURE 9-7
RETRIEVAL REQUEST FORM
9-19
42 44
|
47 49 52
... I
S2
-------
r
M
>
\
DATA ELEMENT
REGION
^ STATE
V COUNTY CODE
~ SOURCE NUMBER
AQCR
CITY CODE
>-sninirK NAMF
•-t-lfY NAME
ZIP CODE
STATE REGISTRATION NUMBER
VSIC CODE
FEDERAL FACILITY
AIR PROGRAM CODE
AIR PROGRAM DESCRIPTION
AIR PROGRAM STATUS
STAFF PERSONNEL CODE (SOURCE)
NEDS SOURCE CROSS REFERENCE
STREET ADDRESS
STATE ABBREVIATION
STAFF NAME (SOURCE)
LAST UPDATE
FILLER (5 SPACES)
FILLER (IS SPACES)
REGIONAL DATA ELEMENT I
REGIONAL DATA ELEMENT 2
REGIONAL DATA ELEMENT 3
REGIONAL DATA ELEMENT 4
REGIONAL DATA ELEMENT 5
REGIONAL DATA ELEMENT 6
COUNTY NAME
x FACILITY CAPACITY
REGIONAL DATA ELEMENT 9
REGIONAL DATA ELEMENT 10
REGIONAL DATA ELEMENT 11
REGIONAL DATA ELEMENT 12
~ BASIC POLLUTANT INFORMATION
REPEATING POLLUTANT
POLLUTANT COMPLIANCE STATUS
--POLLUTANT EMISSION CATEGORY
POLLUTANT AIR QUAL MAINT AREA
POLLUTANT AIR QUAL CONT REGN
POLLUTANT LOADING
DATA
TYPE
S
S
S
S
S
S
S
b
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
SR
SR
SR
SR
SR
SR
ABBR.
REGN
STTE
CNTY
SRCE
AQCR
CYCD
SNME
CYNM
ZIPC
STRC
SICC
FEDF
APCD
APDS
APST
PERS
NEXS
STRT
STAB
STFS
UPDA
BLK1
BLK2
RDE1
RDE2
RDE3
RDE4
RDES
RDE6
CTNM
FCAP
RDE9
RD10
RD11
RD12
BPLT
PLLT
PCMS
PECT
PAQM
PAQC
LOAD
NO. OF DIGITS
10 & 30
CARD
2
2
4
5
3
It
'(1
lj
5
IS
4
1
1
20
1
3
4
20
2
15
6
1
1
1
5
5
10
17
7
7
2
2
1
60
2
1
1
1
1
5
40 CARD
5
5
5
6
5
5
21
lu
6
16
5
5
5
21
5
5
5
21
5
16
9
5
15
5
5
5
6
6
11
18
8
a
5
5
5
61
5
5
5
5
5
6
DATA ELEMENT
POINT NUMBER
SCC 3 DIGIT CODE
SCC 6 DIGIT CODE
SCC 8 DIGIT CODE
PROCESS DESCRIPTION
COMPLIANCE STATUS CODE
SIP CODE
POLLUTANT
STATE REGULATION
EMISSION CATEGORY
MULT CROSS REFERENCE
CAPACITY CODE
REGIONAL DATA ELEMENT 7
PROCEDURAL COMPLIANCE
EMISSION CATEGORY DESCRIPTION
COMPLIANCE STATUS DESCRIPTION
SIP CODE DESCRIPTION
OLD COMPLIANCE STATS -
B QUARTERS
OLD COMPL STAT - 1ST QUARTER
OLD COMPL STAT - 2ND QUARTER
OLD COMPL STAT - 3RD QUARTER
OLD COMPL STAT - 4TH QUARTER
OLD COMPL STAT - 5TH QUARTER
OLD COMPL STAT - 6TH QUARTER
OLD COMPL STAT - 7TH QUARTER
OLD COMPL STAT - 8TH QUARTER
ACTION TYPE
DATE SCHEDULED
DATE ACHIEVED
STATUS (RESULTS) CODE
STAFF PERSONNEL CODE (ACTION)
ACTION DESCRIPTION
•» STAFF MEMBER (ACTION)
STAFF TITLE
ACTION NUMBER
REGIONAL DATA ELEMENT 8
RESULTS DESCRIPTION
DATE ACHIEVED YEAa/tiONTH
DATE SCHEDULED YEAR/MONTH
PENALTY AMOUNT
DATA
TYPE
P
P
P
P
P
P
P
_VB
A
A
A
A
A
A
A
A
A
A
A
A
A
A
ABBR.
PTNO
SCC 3
SCC6
SCC8
PROS
CMST
SIPC
PLUT
SREG
ECAT
MULT
CAPC
RDE7
CMS2
ECDS
CMOS
SIDS
OCS0
OCS1
OCS2
OCS3
OCS4
OCS5
OCS6
OCS7
OCS8
ATPE
DTSC
DTAC
STAC
PERA
ADES
STFA
TITL
AHUM
RDES
RSTD
DAYrl
DSYft
PAMT
NO. OF
10 & 30
CARD
3
3
6
8
25
1
1
2
15
1
3
2
1
1
20
20
20
8
1
1
2
6
6
Z
3
15
15
15
2
2
15
It
4
7
DIGITS
40 CARD
5
5
7
9
26
5
5
5
16
5
5
5
5
5
21
21
21
9
5
5
5
5
5
5
5
5
5
9
9
5
5
16
16
16
5
5
16
3
5
8
VO
O
Ft
f
S.
SR Indicates a repeating source level data element.
-------
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 nn three separate 30 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 0
Data Element Cond. Value LEFTJUSTIF
lsrr-/j Id la*
lL£l \*.T.-rA Id \L£.
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.
I; ol ]JLC^ ty \0
Data Element Cond. Value LEFT JUSTIFIED
0 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 10-11. Start with the left-most
field. The available report formats are:
QL - Quick Look
SD - Source Data Report
AC - Action Summary
QT - Questionnaire
MS - Milestone
Q2 - Double Spaced QL
Certain data elements in CDS are password protected. If the user
wishes to obtain confidential data on his output report, he must place
his password on column 14 of the Card 20.
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 4^ digits. For example,
a sequence of Source Name (29 digits) and Process Description (25 digits)
would result in a fatal edit error as the sequence length is 45 digits.
However, in utilizing all six possible sequence entries with SIC Code
(5 digits), Federal Facility Code (1 digit), Active Passive Code (1 digit),
Compliance Status Code (1 digit), Pollutant (2 digits), and SIP Code
(1 digit), we only have a total of 11 digits, well within the 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 110 or less for the data elements on the 40 Card.
If the data elements on to 40 Card require more space than is avail-
able on the 132 character print line, the QL will not be produced. Data
elements are printed left to right in the same sequence as they are
coded.
If a Quick Look Report with data element suppression is desired, a
'!' 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 Repo'rt (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 CNTY 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
9-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
Pollutant
PT
S2
PT
S2
HC
PT
S2
HC
Pollutant
Compliance
4
1
4
4
1
4
4
4
The following selection criteria will extract data for Sources B, C,
and D
10 PLLT M PT
10 PCMS M 4
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 SO,, 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.
t
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
Dot* Submitted
Return Rnpax 7, __
io,ii \a\s\ LJ
»*M
11,01 uf.ru* ig|
124 7
Oof a llama
11-01 \AT.P £\
11 01 l*TP£l
11.01 \fl.T, f£\
11,01 &TP£\
1 1,01 \A,T.P.£\
ii.oi I^TT^^I
11,01 \ArP£\
11,01 |r*T,^«l
ii.oi lArrri
11.01 l 1
11. Ol 1 • 1
11.0) 1 1
11 01 1 1
11.0) 1 1
11, Ol !_; |
H.Oi i . . 1
11.01 1 . 1
|1.0| l . 1
11.01 1 . 1
REPORT FORMATS
|3.0| itfll 1 i
12 45 71
'|3,0| &/fS*&
124 7
REPORT SEQUENCE
FOR QQICH LOOK
|4.0| L^AfirM^I
124 7
Enter
Mail
k»»p«« niu
\A\ \ffJL, j
9 11 11
Cond. ValuaUaft Juitlilad)
Ml \0.2 I
i
\A i°l • • - • i
\A\ \GJS • . \
\A\ \t>8 . , l
bti i£i .1
|^jj Lfti. , , ,
|>9i \f*3 . • i
\A\ l/j7
UMI I/.4/ , 1
ill... 1
1 | | l
III. I
1 1 ! • • '
III- • • '
lit . . .1
| i i . 1
|ii. .1
III. . ,1
iii 1 ' • ' • ' • '
Stop
' M 4i M i]
1 .... . i ' . . . 1
51 !•
r 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 daca
elements and their
abbreviations .
It'll 14 21
1 , . 1 1 . 1 1 . , , 1 1 . . , 1 1 « . . 1
9 12 14 17 19
(Poaian. Itara, CaaMf, loam, an
22. 24 27 29 32
V •••
REPORT ONLY
9 ' 12 14 17 19 22 24 27 29 32 34 31
Data Elements left to right in the same sequence as required ai
Tha Uttmati portion al lha l,n* alwaft mcludal llala, Cauntf lavrca. Pom
Actlan Numbar union NOHO ll cadad in column 4 ihrav
71
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
SD - SOURCE' DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
Q2 - DOUBLE SPACED QL
CA - COMPLIANCE-ACTION
LEVEL CODES (01 CARD)
S - SOURCE ONLY
P - POINT AND SOURCE
A - ALL DATA
C - CRITERIA MATCH ONLY
Numbar al
l__l lubtoialllnf
39 data turnout*
J \DiT\£i£^ \D,T&-,C± 1...
10
39 42 44 47 49 52
' "P0rt 1 . . , , .1
1 "d 54 57 60
*k With NOHO Only Supprati
FOR MILESTONE REPORT OHIT
15, Ol 1 . , . 1 1 , . . 1 1 , • , 1 1 , , . 1 1 , , • 1 1 , , . 1 1 , . . 1 , , , 1 1 . . . 1 1 . , ,
124 7
IOW1
OAIA
llfMINT
|
9 12 14 17 19 22 24 27 29 32 34 37 39 42 44 47 49 52
COIUMNS COLUMN VALUI1
• IWIHt liN«UMO.O. VA1U.".LAN«- 1 . . . 1 1 . . , 1
FIGURE 9-8 S4 57 59 62
9-33
-------
COMPLIANCE DATA SYSTEM
Oat* Submitted
iQ.n igiSi LJ
12 4 S 7
ii.oi \&T,A&\
lT 4* 7
Data llam«ir
11.01 \A,T,P£\
11 01 \AT9£\
11,01 \A.T.fS\
11,01 \ArPf. i
n.oi ^-rPfii
11,01 \fl.T.ff\
11,01 uO.r^Z]
11,01 \Ar.PS\
n,oi tfr.P£\
11.01 i 1
11.01 1 . 1
11. 0| 1 1
U 01 1 1
11. 0| 1 1
11. 0| LJ |
U. 0| l . . 1
H .01 | |
ll.OI l . 1
11.01 1 1
REPORT FORMATS
|2.0| l«g«M i .
12 45 71
J3,oi \S/rsnA
124 7
DEPORT SEQOEMCE
Mail
r
l^fja*Vt»/i •9ifC, ^W . v| f\/ *&tAr —5 \r\ &,^L 1*1 y\J\9\ \ .
Step
» 20 ' 30 4* M S2
•^ .
9 U U
Cand. Valuo Uaf t Juitlllad )
U*i I«V .1
uti \0* l
Ufi \OS \
\A\ \Sl
1/9 1 i5i . , i
i/9l le^J?
I4*i i>7 . i
ill.. 1
I.I. i
ill.. . !
III. 1
1 | l . 1
ill . . J
III . , .1
III J
III. .1
III, . ^J
•ASSWOtO
II J 1 1 1 1 1 1 1 1
SI 10
t 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 cheir
abbreviations .
J
10 11 l« 21
1 . • 1 i . . l , • . 1 1 , . • 1
9 12 14 17 19 22. 24 27 29 32
70
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
Q2 - DOUBLE SPACED QL
CA - COMPLIANCE-ACTION
LEVEL CODES (01 CARD)
S - SOURCE ONLY
P - POINT AND SOURCE
A - ALL DATA
C - CRITERIA MATCH ONLY
Numbor oi
39 data otamantt
10
FOR QUICK LOOK REPORT ONLY
124 79 12 14' 17 19 22 24 27 29 32 34 37
Enter Data Elements left to right m the same lequence as required or
Iho loftmatl portion of «<• l.n> olwatt includol »!•••, County Saurca Poin
Action Numbar vrilait NOHO t> cadad in column 4 throu
39 42 44 47 49 52
i report 4
' 1 , . , 1 ill
h"nu 'a1- '£/ \?
9 With NOHO Only Suparoti
FOR MIIESTONE REPORT ONIT
IS.Ol 1 , , , 1 1 , , , 1 1 , . , 1 I , , , I I , , . I | , , , | i , , , | | , , , | | . . . | I . , ,
124 7
IOWI
DATA
IIIMINT
9 12 14 17 19 22 24 27 29 32 34 37
COIUMNS COLUMN VAIUCS
l!|AM.N, ""« UMO '« W*IUI ""*"« '
FIGURE 9-8A
1
39 42 44 47 49 52
1 ... 1 1 ... 1
54 57 59 62
9-33A
-------
COMPLIANCE DATA SYSTEM
Report Request Form
Oat* Submitted ^
Return Report To.
Mail Stap
.Tlnu
11,01
12
*X V.
,"—»x£»-
tanvod,
4 7 9 U 1*
Oota llonMnt Cand. Valuo (loft Juitlllod)
11.01 1 , ,
11-01 I
11,01 1 . ,
llL°J 1 . .
11,01 1 . ,
11,01 1 . ,
11,01 1 . .
11.01 1 ,
|1,0| 1 .
11 01 i
11. 01 1
11.0) 1
I.LPJ U
11.01 1
LLPJ u—
11. Oi | . .
I'.OI 1
ll.OI 1 .
11.01 1
• i I i i i
i i i i . . i
i i i 1 . . . i
,, i i i i , . i
. i i i i . i
.1111
i i i i .
iiii
i i i i . . i
iiii . 1
I I i 1 . i
l,ii.. . :
llil. i
MM • • 1
llii. . . _i
iiii . . . . J
1 I M • • '
.MM- • '
Mil.. . J
ItPOBT FORM.TS
i3.oi
12
71 19 II
j I , •
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE *
U - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANT 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.
j i
J3,0t |_,
124 79 12 14 17 19 22. 24
REPORT SEQUENCE (lo«lo*, Horn, Cowty, fa.no, or. otaoj.* MIOM
J I
27 29
70
• •
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
SO - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
Q2 - DOUBLE SPACED QL
CA - COMPLIANCE-ACTION
LEVEL CODES {01
S - SOURCE ONLY
P - POINT AND SOURCE
A - ALL DATA
C - CRITERIA MATCH ONLY
of
I—I tvbtoiollinf
39 doto oionionM
FOR QUICK LOOK REPORT ONLY
|4.0| !_!_.. I I . , . I
1 2
J I . ..I I ... I
17 19
4 79 12 14 17 19 22 24 27 29 32 14 17 19 42 44
Enter Data Elements left to right in the same sequence as required on report
Tk* l«ilm«ii portion ol Iho lilt* alwayi includoi Jloio, County Sourci Point and
Action Nuntbor union NOHO li codorf in column 4 through 7
47 49
52
I ... 1
54 57
With NOHO Only Suaoroii
U
U
FOR MILESTONE REPORT OBIT
IS.Ql I , . , I I , , , I I ,
124 79 12 14
IOW* COLUMNS
DATA DATA
IIIMINT IIIMINT
! ! I I . I ! I I I , • I I.I.I I t , M I
17 19 22 24 27 29 12 14 17 39
CCtUMN VALUIS
IINK UriD r"Ot VAIUI "llANf'
FIGURE 9-9
42 44 47 49 52
I ... I I ... I
54 57 59 62
9-34
-------
COMPLIANCE DATA SYSTEM
Oat* Submitted.
lS^01u*t*r*+ *<
cry^^jc fojt Fyy»
20 ' 30
Mail
Slap
40 aM t>
11,01 iAriff\ \A\ \0.2.
124 ; > 11
Oato llonMirt Coad. Vfelua
Coad. V»k.a(l«i» JmtHloa)
11.01
11-01
11,01
LLPj
11,01
IliOl
11.01
11.01
n.oi
11.01
LLflj
11,01
11.01
11. Ol
n.oi
ll.OI
11.01
tf,T,P£\ i/H
iArf£\ \A\
\AT.Pf\ (4)
\4T.f 'f\ \A\
\A.TP.£\ tf\
L*t9t ^ 0 £\ Udl
i4r ffi I**'
1 . . Ill
1 .III
1 III
1 III
1 . Ill
1 . , III
1 . .Ill
1 III
\#3, i
10 V . . ,l
\o.a . i
\O8 . . I
I.S / . . 1
LSI ...
latJ . . >
'?*
i ... i
1 ... 1
1 • '
1 . . !
1 . 1
1 . . 1
1 . . . 1
1 . , ,1
1 1
1 . .1
1 ]
, CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE *
0 - 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
list of all CDS data
elements and their
abbreviations.
a
REPORT FORMATS (20 CARD)
QL - QUICK LOOK
SD - SOURCE DATA REPORT
AC - ACTION SUMMARY
QT - QUESTIONNAIRE
MS - MILESTONE
Q2 - DOUBLE SPACED QL
CA - COMPLIANCE-ACTION
LEVEL CODES (01 CARD)
S - SOURCE ONLY
P - POINT AND SOURCE
A - ALL DATA
C - CRITERIA MATCH ONLY
•EPOIIT FORMATS
•Aiswoeo
I
I I L
12 » S
13,0) | .
7 1 10
, • 1 1 , ,
124 79
REPORT SEQHEHCC (la,
FOR QUICK
|4.0| I .
1 2 4
LOOK REPORT
, . 1 1 ,
7 9
11
1
12
K~. IN
ONLY
1 1 1
12
14 11
1 1 1 1 1 N««iba» o*
14 17 19 22. 24 Z7 29 32 39 data .um.*t.
1 . , , 1 1 , , , 1 1 . , , 1 1 , . , 1 1 , , , 1 1 , , , 1 1 , , , 1 1 , . . 1
14 17 19 22 24 27 29 32 34 37 39 42 44 47 49 52
Enter Data Elements left ta right in the same sequence as required en report
Tha laitmatt portion ol lha lino alooyi mcludoi Jrolo, County Source. Point and
Action Numbor unloti NOHO if codad >n column 4 through 7
54 57 «0
With HOHO Only Suparmi
FOR MILESTONE REPORT OHIT
15.ol \/9,D,e^\ \DJIty4t
124 7 9 7l2
lOWi COLUMNS
DATA DATA
IIIMINT IHMINt
14 17 19 22 24 27 29
CCIUMN VAIUIS
•INK UflO rOt VAiUI "llAMK
FIGURE 9-9A
9-34A
l\
32 34
37 39 42 44 47
49
52
I ... I I ... I
54 57 59 62
-------
COMPLIANCE DATA SYSTEM
Report Request Form
Date Submitted
Return Report To.
Mail Stop
.Time
12 4 S
M^leuel^Repotl
SOfemaltot.
Till.
n.oi
12
4 I 9 II II
Oolo (lament Cand Volu. htlt Jollified)
l/.«9!«,/.7,4
,
1 .....
1 I ....
1 ...
1
1 ....
1 .
1 . . . ,
1
1 . . . .
1 . . .
1
1
1 . ...
,
1
1 . .
1,1
*, , 1
• • 1
, . 1
I . 1
. . 1
1
I 1
. . 1
. 1
1 1 1
. 1
I . 1
1
. 1
. 1
. ! 1
. . 1
. 1
. . 1
CONDITION CODES (10 CARD)
M - MUST EQUAL
A - ALTERNATE *
U - UNEQUAL
C - EQUAL OR GREATER THAM
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.
11.01
REPORT FORMATS
|2,0| \QT
12 4 S It
124 19 12 14 17 19 22 24 27 29
REPORT SEQUENCE (H.g.on, Stole. Co»nly, Sowco, o.o olway. prei.nl)
10
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 of
lublololllne
39 dela elomenll
FOR QUICK 100K REPORT QUIT
ll.Ol
I 2 4
1 I U 14 17 19 22 24 11 29 12 14 17 19 42 44 47 49 52
Enter Data Elemenli left to right in the same sequence as required on report
Ihe l*llmati poilion ol Ih* l,n* alwayi include! Stale, Covnlv SowfCe Paint and
Action Nwmbof Mnlotk NOHD U coded In column 4 Ihrevah 7
U
54 57 60
w,ih NOHO Only Suaproil
FOR MILESTONE REPORT ONIT
124 79 12 14
IOWS COIUMNI
DAI* OA1A
EIIMINT IliMINI
17 19 22 24 27 29 12 14
CCIUMN VAIUI1
•INK USED FOR VAIUI "lLANi"
FIGURE 9-10
9-35
37 19 42 44
54
47 49 52
57 59
62
-------
COMPLIANCE DATA SYSTEM
Report Request Form
Dote Submitted
Return Report To.
Moil Slop
.Time
JOfon-oTcfcr,
10 ' 30 40
SI SO 70
SO S2(
so
'.*.«*
n.oi if>-w,cx CL
124 | 9 II U
Dal.il.m.nl Cond Voluo (loll Juillllod)
i*r.p.g. & t*» i
REPORT FORMATS
\/*.cJt.
45
IS 10 II
12
|3,0|
124 79
REPORT SEQUENCE (Ro
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.
_ __
12 14 17 19 22 24 27
n, Slol>, C.«m,, leo.i., or. olwoyl prn.nl)
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 ol
lubl.loNIng
39 t .„.",
FOR QUICK IOOK REPORT OMIT
|4.0| l.i.l l,i,l I , ; i I I i . . I I ... I I , . , I
124 79 12 14 17 19 • 22 24 27 29 32 34 37 39 42 44 47 49 52
Enter Data dementi left to right in the same sequence at required on report
Ih. l.llmo.l p.il.an .1 Iht l.n, .1.0,1 includti Hoi., Com, S...C. Point and
Action Nmnboi union NOHO ll cod.d In column 4 through 7
S4 57
With NOHO Onlr Sapptoii
FOR MILESTONE REPORT OMIT
|5,0| I . , , I I i , i I
124 79 12
•OWI COlUMNf
DA1A DMA
IIIMINf ElIMINT
17 19 22 24 27 29 32 34
CCIUMN VAIUII
IINX USED fOI VALUE "llANl"
FIGURE 9-11
37 39 42 44 47 49 52
54 57 59 62
9-36
-------
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
•
1
/
/
/
/
/
0
1
2
3
4
/
/
2
*
/
#
/
/
1
0
*
0
0
/
*
3
P
E
E
R
E
PROGRAM NAME RETRIEVAL JOB CONTROL
TASK NUMBER
4
R
P
X
T
O
5
1
A
C
V
F
67
OJR
i i
L U
*
S
8
1
•
S
Y
9
T
1
S
10
Y
V
(i
11
E
0
12
13
14
Jbb
E
5
rh<
•
1
X
re
•
i
E
D
:
i
is
C
D
olalala
i
16
4
17
18
19
»
21
(alalaU.
cb
c
*
is
•f f
\,
S • R
DJSR
t
i-
f
ie
10
IP
u
L
T
se
f°
iP
22
•
1
0
V
'!
'<
',
RI
23
•
1
G
n
a
f
TF
24
•
i
p**
PP
F
[E
25
)
i
Ml
In
:G
FA
26
i
ii
^f
1 i
IRl
i «
27
i
is
nt
1111
C
01
21
U
Is
mh
hf
_j
29
s
0V
r *
2
(JON
30
E
Vi
FR
31
R
i
>L
32
Til
Al
Nc
st
A]
fe
Tl
Tl
nl
l\
33
g
1
1
s
le
1
e
e
1r
Vfl
34
>r
D
re
>1
:t
:e
•f-
ie
>r
r
1 11
35
o
i
,r:
!C'
.01
:r:
Ci
1UI
.n
.n<
»fj
36
1t
»
e\
K
6'
1,
n<
lK
a
37
Y
T
a!
n
ai
al
rf
e
01
01
P
31
r,ft
1
5
ca
ds
s
In
se
ma
g
1
39
r<1
IV
QU
rd
m
nu
Le
rh
40
if
E
it
i i
1Y
it
:t
>0
'61
'ni
41
(i
=
h£
r«
be
hi
OI
Ci
P]
pt
42
Pt
1
ve
i
i
V6
r<
t
43
lo
a
eq
se
0
0
i
is
0.
44
la
i
ii
1.
ie
:a
>
s
45
11
•ei
2
•d
e
1'
46
t:
»
! (
is
u
ig
47
tl
up
ai
c
re
e<
41
e
c
d
Pt
d
49
:a
>
fo
Lo
Lf
50
d
:wi
la
a
51
nt
•
52
y
53
54
55
56
U)
00
-------
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)
Number of 20
Cards
REPORT SEQUENCE
DATA ELEMENT
SEQUENCE LENGTH
QUICK LOOK DATA
ELEMENT
QL Length
Number of 40
Cards
VARIABLE MILE-
STONE DATA
ELEMENT
Column Values
Relation to
other cards
Number of 50
Cards
General CARD
TYPE
Correct Possibilities
Blank, S,P,A,C
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, Q2, MS
Up to three reports are
available 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 Nf
(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
Hn
(1) QL FORMAT Request
Ignored
(2) QL FORMAT Assumed
(if only one 40 card)
FATAL - Processing stops
after EDIT
FATAL - Processing stops
after EDIT
FATAL - Processing stops
after EDIT
MS FORMAT Request
ignored
FATAL - Processing stops
after editing
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 condiClons 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 uata 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"
'FATAL - INVALID MS DATA
ELEMENT COMBO"
"FATAL - REPEAT AND POINT OR
ACTION ON QL"
"PASSWORD NOT ACCEPTED - NO
CONFIDENTIAL DATA WILL BE
PRINTED"
"PASSWORD HAS BEEN ACCEPTED -
CONFIDENTIAL REPORT - FOR EPA
INTERNAL USE ONLY"
No card type 20 was entered.
card type is required.
This
No card type 40 was entered, although
QL was entered on card type 20. QL
report format is ignored.
The total length of the QL line is
greater than 110 digits with the de-
fault header information or it is
greater than 132 digits with NOHD.
A level code 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 may specify only source
level data together with repeating
pollutant data on the Quick Look.
Either no password was used or an
incorrect password was used. No
confidential data will be selected,
sorted or printed on any output
report.
When a correct password is used, each
output report page is labeled as con-
fidential.
9-42
-------
RETRIEVAL EDIT REPORT
33/23/78 * ••••• • COMPLIANCE'DATA'SYSTEM
RESIGN OS LEVEL TITLE MAJOR ACTIONS FOR FV78
SELECTION CRITERIA
DATA ELEMENT CONDITION VALUE ERRORS
ACTION TYPE ALTERNATE 02
ACTION TYPE ALTERNATE 03
ACTION TYPE ALTERNATE 0«
ACTION TYPE ALTERNATE 05
ACTION TYPE ALlERNATE 08
ACTION TYPE ALTERNATE si
ACTION TYPE ALTERNATE 52
ACTION TYPE ALTERNATE 63
ACTION TYPE ALTERNATE 77
REPORT SEQUENCE REPORT FORMAT OL
STATE
SOURCE NAME
*8TATE
*COUNTY
*80URCE NUMBER
*EM1SSION POINT NUMBER
FACTION NUMBER
PAGE BREAK AFTER THE FIRST 1 DATA ELEMENTS
QUICK LOOK DEFAULT DATA ELEMENTS • STATE, COUNTY, SOURCE, EMISSION POINT* ACTION NUMBER
SOURCE NAME
CITY NAM.E
STATE ABBREVIATION
SIC CODE
POINT PROCESS DESCRIPTION
SOURCE EMISSION CATEGORY
COMPLIANCE STATUS CODE
ACTION DESCRIPTION
ACTION TYPE
DATE ACHIEVED
NQHD • DEFAULT OL ITEMS ARE SUPPRESSED
NO ERRORS DETECTED • CONTINUING WITH RETRIEVAL
PASSWORD NOT ACCEPTED • NO CONFIDENTIAL DATA HILL BE PRINTED
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 Cable-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 id 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-1(9
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 i
e r
(, ft
i r
e.
o
^f
Tr
01070265
0107,0425
O 1070478
0 107.0565
0107
O107
01.07
0107
O12O
01 2O
O12O
0120,
01 2O
O12O
O12O
Ol!2Q
O12O
O12O
Ol|20
Oli20
37O5
, ^ t
ry An>.
rAIRFIELD
HARTFORD
LITCHFIELD
1IDDLESEX
^EW HAVEN
3725JNEW LONDON
1155TOLLAND
15O5WINDHAM
:>027hNDROSCOGGIN
3045AROOSTOOK
3277
3445
34^5
5547
3595,
3645
3885
CUMBERLAND
rRANKLIN
HANCOCK
'ENNEBEC
100BENNINGTON
)160'PALEDONIA
)180CHITTENDEN
>200ESSEX
^240
>26O
)2Qfj
»36C|
)38Q
)420
>5od
rRANKLIN
3RAND ISLE
.AMOILLE
URANGE
ORLEANS
JUTLAND
WASHINGTON
>580WINDHAM
01 47^)6 2CJ WINDSOR
"„
c
A
I
O44
044
044
042
042
O41
042
041
1O7
103
110
111
109
1O7
107
107
a
**.
"g
2
042
042
042
041
041
111
107
11O107
109111
1O9
no
111
1O7
109
no
117
118
121
119
O42
111
107
120
121
149
121
1O7
149
121
121
121
121
121
120
12O
120!
12O
^
4
*Jj
3
042
111
120 1
159
221
221
159
221
159
159
221
221
221
159
221
221
221
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
Record-Identifier
Region
Personnel Code
8
9-23
24-38
39-80
1
15
15
42
Filler
Personnel Name
Personnel Title
Filler
Data
Type
Always "BB"
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
-------
OZPOIPREOB
ENGINEER
O2Olir'M TRICHON ENGINEER
02021R r.ELLAMARE ENGINEER
f» 20 2S3V...P IIRUZiELLQ. _Efc!
i:i ENGINEER
0206PD 9TQNE ENGINEER
0 ? 10 1A SQLPETER ENGINEER
o-2"io2P » AHN" ENGINEER"
O:"-'O?B TQRNICK ENGINEER
O 2C>0.'1R_.C|.GG _______ ENG I NE_ER_
O2ir'(")5o '-AMTELLA r^r. JNFER
o 21=>ir'1-'K 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 which do not match one
of the table values will cause the input transaction to be rejected with
a fatal error.
In the Update, the Action Table lookup is performed for every new
Card 7 transaction and for every Card 7 which changes the Action Type.
Both a long and a short Action Description are generated on the Master-
file based on the Action Type.
Entires on the Action Table have the following punchcard layout:
Card
Columns
1-2
3-4
5-6
7-8
9-23
24-73
74-80
Length
2
2
2
2
15
50
7
Data
Element
Record-Identifier
Region
Action Type
Filler
Short Action
Description
Long Action
Description
Filler
Data
Type
Always "CC"
Numeric, 01-10
Numeric
Always "00"
Alphanumeric
Alphanumeric
Must be blank
To change the Action Table, users should provide the national Data
Bank Coordinator with the necessary information to add, change, or
delete an entry on this table.
Figure 10-3 is the Action Table for a Region. Users are urged to use
ALPHA to list the most current action types for their region. The follow-
ing ALPHA commands will produce a printout of the current action types:
10-7
-------
Li
12
L3
l«
L5
Lr>
L7
L8
"•1
f-t
PI
R?
R5
Ke
R7
»«*
SI
S?
S3
87
SH
Tl
T?
T3
T<*
T5
Tb
T7
T6
XI
XZ
X3
xu
X7
XI
XV
Yl
Y2
vs
YU
Y5
Yto
V7
Yh
01 SL'H
05
Oh
07
STAlfc
STTfc CIVIL ACTC
SI C«IM ACTION
EPA MOV
EPA CIVIL ACT*
EPA CHI*' ACTU-*
RESERVED
NUT ICE CM DE^O
Cf SYSTE^ IN8P
EfcB SUBMISSION
CM UST RESULTS
EPA HCVC APPL1C
ADOIT INFO-EPA
E^A APP Cl"">PLET
EPA PHFLI* PET
EPA PtH
EPA Pl'H
tPA
EPA
SITE
STTfc
siTt
STTE
SUfc
STTE
5TTK
Silt
STTE
STTt
STTE
STTfc
EPA
DET
APPLC
ADIT
APP CUI-PLT
PKtLl^ RET
PUB NOTICE
PUB
TFFSET OfT
BACT DET
L*ER OET
J.ACT DET
OFFSET OFT
El-'A BACT DET
EFA 1.4ER UE1
EPA KACT DEI
STTE
STTE
FED CCUPT
sm: use
STTfc
STTH
STTfc
ISSU
DCWE
DC
nc
DC
PS
SP
HE
IT
CC
SCND
EPA
EPA
EPA
EPA
113C
11 3D
1130
ST 1 )9 SO
ST 119 SO
13A SIP til
PC 0
SIP DC
13A
13C
130
13C
\W
E^A
PPA
(C \
114
DC
SU
si;
EM>
FINAL
r.bv ISSUED HY STATE
IV1L ACTION hY STATf
STATE CRIMINAL ACTION
^C v ISSUtL) HY kPA
EPA CIVIL ACI1GN
ACTION
ADDITIONAL
APPLICATION
PUbLIC
UMAL
NCUMCATiriN OF CM ngffcNSTKATION DATE
CCNTPUIUJS ("L'MTO'lfcb S/STE* INSPECTION
osYSTk* TEST RESULTS
APPLICATION RECEIVED BY EPA
ADDITIONAL iNKjRhATION REQUESTED BY EPA
TC EPA Cl'^PLEU
DEItRflKAT ION BY EPA
PUhLlC NUTTCE BY EPA
PUBLIC HEAPING BY fcPA
DETEH'MNAT I UN BY EPA
HUM HY tPA
APPLICATION RECEIVED PY STATE
NFL'R.rAlTON REKUESUD BY STATfc
K STAU CCMPIF.TE
UEURMINAT1LN BY SJATfc
BY STATE
Nt, BY STATE
]NATIl> tY STATt
Y STATfc
1 ACCtPTAblLITY DETERMINATION BY STATE
OETfcKMlNATIUN HY STATE
DETERMINATION BY STATE
DETERhlNATICN BY STATE
ACCfcpTAhiLiTv CETER^INATION BY tPA
DETERMINATION BY fcPA
HY fcPA
B> EPA
ORDER ISSUED
LCIURT I'EtRfcE ISSUED
COURT DECREE IbSUED
13D STANDARD SIP DC CKl'fcM APPROVED bY EPA
130 REPLACEMENT DC OHPER APPHUvEO BY EPA
13D INN. TfcCH. OC CROER APPROVED BY EPA
130 CUAL LON'V, DC CRUER APPROVED BY EPA
IV SHELTER ORDER APPRUvfco bV fcPA
119 SMtLTFR ORDER APPROVED BY EPA
SIP VIULATIL'K ORDER ISSUED
NON-SIP VIOLATION1 CWDfcH ISSUED
STANDARD SIP I'C CWCfcR ISSUED
RfLACffc'NT CRDER ISSUED
INN. TELK, DC (JRDER ISSUED
CliAL CONV. DC CRDFR IbSUM-
)1V S^ELTEU I'RDEn ISSUED
BACT
SlATb
STATfc
STATE
STATE
SUTfc
STATfc
FIRST
SECONU
EPA
13A
13A
»3A
13I>
130
13C
130
F1WST fcPA
fePA
(•PA
EPA
SfcCf'ND fcPA
ISSUED
PLAN
J10 SHELTER
UF HN»L COTKUL
^llMfcNT Tf
UF IN SITE CONST hUC T K'M/PHOLfcSS C
I'F CN gjTf CTNST hUC 1 IL'\/PK(.'.Cfc SS
STATE INSPECTION
Figure 10-3: Sample Action Table
10-8
-------
ALPHA COMMAND
LOAD CN.EPAFCS.A026.ISAM.TABLE
DEL-7/CC01/
REP //,/ /,FIELD=l-4
REP. //,/ /,FIELD=7-8
REP //,/ /,FIELD=24
PRINT*, ROUTE=nn, NUMBER=NONE
EXPLANATION
Places all 10 regions actions
into working storage.
Deletes all entries for all regions
except for Region 1. Each region
should put their own region number
into this command.
Formats table for printing.
Generates spaces between col 24-25.
Users should route their printout
to their own terminal number.
10.1.4 Results Code Table
In the Edit, the Results Code found on the Card 7 in columns 70-71
is validated by the Results Code Table. If the input transaction entry
is valid, a Results Description is generated and passed to the Update,
where it is placed on the Masterfile. If the input transaction is not
on the Results Code Table, no Results Code is passed to the Update.
Entries on the Results Code Table have the following punchcard
layout:
Card
Columns
1-2
3-4
5-6
7-8
9-23
24-80
Length
2
2
2
2
15
57
Data
Element
Record-Identifier
Region
Results Code
Filler
Results Description
Filler
Data
Type
Always "DD"
Numeric, 01-10
Numeric
Always "00"
Alphanumeric
Must be blanks
10-9
-------
F
D6010C
_ _ P
(V:.O I OC
P
.. (V-.O10C
EC
01
~r
or-
rr
0 :
QRD 008S^
ACT TOM ACHIEVED
ORD OOS^O
NOT AC HE WED
ORD O03ir'l
ACTION RESCHED
FIGURE 10-4
SAMPLE RESULTS CODE TABLE
10-10
-------
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-10A
-------
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 ftLL RECORDS
i 1 1 1 1 1 1 i i if
» me m«n
IREGION
ISTATE
1 COUNTY
CODE
u°
w b L
Ss"2
ee ie,G
M U .U 0.' 4
S
!•>
U
tol
«
COMPLIANCE DATA SYSTEM
MASTER FILE LAYOUT
II»4Uf III I IIJIt I I to
*
SS
V.
X
SOURCE
5£g CODE
< uu
: Mi
=22 »DE9 i0U IFIL'.E
fe 'ssi
fc „. «B>
! Ill
I3
JC
SCC srJs
• .00 5
COOE iii
= § i
2»5 g S
P- « ! W M 1 Ul bb
W 'H P- = K E
« u * I * Ul
.« 0 VI 00.
. ^
— «
u a.
SS
REGULATION
NLViBER
I
5|E
S T
REET
ADDR
POLLUTANT
E
i
I'iTu! s
" •..j.1--
L ICtv^^iH
3 DE
ACTION ,
DESCRIPTION !
(SHORT) i
i
I
s
S
C 1 TY
POLLUTANT 2
POLLUTANT
PROCE SS.
SCR 1 PT 1 ON
A
J
> *°
i cr
e PE
iZ
S
TAF
F
ji
E'
NAME
I
it
"
M
3
1
ZIP
CODE
STATE JJ
REGISTRATION g.j,
NUMBER g||
POLLUTANT 4 POLLUTANT 5
[II
5«ts2i3
, E
waBJo S
v> u|KS in
POLLUTAN1 (
STAF F
NAME
0
kl H tf
K « O
ft
a ^ 5rl"
• POLLUTANT 7
POLLUTANT
RDE4
j
S
ROES
COUNTY '•
RDE6 1 •
NAME L
5
POLLUTANT 9
POLLUTANT 10 FILLER
; ; FILLER
' STAF F ACT
T
«a« COMMENT :
°-*
mil i iiiiiiiiin in
•
ITLE MLLER
ION DE SCR 1 P T 1
(LONG)
O
N
RESULTS
FILLER
DESCRIPTION <
FILLER
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 I 1
t 1 1 1 1 1 1 1 1 t 1 1 1 1 1 1 1 1 1 1
1
1 i 1
i I 1
1 1 1 < 1 1 1 1 . Mill 1 1 1 1 1 1 1 1 1 1 1 1 1 I ' t
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 date on which they
were used as input to CDS. Users should keep a log of all
ALPHA data sets, marking the creation date, the expiration
date, the approximate volume on the data set, and its use or
function.
o Edit Reports should not be discarded. The Edit Report provides
a record of what transactions were input to the system. Cor-
rections should be checked off as they are performed.
o All Update Reports must be kept on file. Since the Update
Reports provide the only audit trail of data placed on the CDS
Masterfile, they are very valuable for researching problems.
They should be filed in the order of the Masterfile's Output
Serial Number which appears on the heading of each page. If
users note any discrepancies or inexplicable errors on this
report, they should alert the national Data Bank Coordinator
or TRC. TRC maintains a complete inventory of all Update
Reports for all users.
10.2.2 National Responsibility for Backup
As part of the normal operation of CDS, the national Data Bank
Coordinator performs the following tasks to assure backup of the system:
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 ALPHA 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.
11-1
-------
11.1 CDS Input Preparation via ALPHA .
ALPHA is a powerful tool which can be used in conjunction with
the CDS retrieval to create input punch card formats for the CDS Edit.
ALPHA should not be used to prepare punch cards for new facilities or
highly changeable data.
When a uniform add, change, or delete must be made to one parti-
cular CDS punch card type, users should consider using ALPHA 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, ALPHA can be used to create the desired input.
Examples of successful ALPHA 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 checklist gives some of the advantages and disadvan-
tages of using ALPHA for input data preparation:
Advantages Disadvantages
Saves input data preparation Input data must be re-
coding time for uniform changes. trievable from the CDS
masterfile.
Provides "instant input" with no ALPHA sessions cost about
need to wait for keypunching. $30/hour; this is much more
than either coding or key-
punching costs for variable
data.
ALPHA commands, especially the Users must possess basic
REPLACE command, are powerful ALPHA knowledge to perform
tools for data manipulation. needed data manipulation tasks.
11-2
-------
The following steps outline how ALPHA might be used to perform
any of the above tasks:
A) Formulate the Retrieval Selection Cards which will create
a Quick Look Report which can then be manipulated and con-
verted into input punch card formats. The 40 Card used for
Printline formatting should contain NOHD, REGN, STTE, CNTY,
SRCE, and any other applicable data elements which will be
needed for each input transaction.
B) Change the EXEC statement of the Retrieval Run JCL as
follows:
//RTV EXEC CDSRTVn,A=P
The "n" at the end of CDSRTV must be the user's Region
Number. The "A=P" makes the output of this job retrievable.
This command will enable the user to manipulate the output
from the retrieval. Users must note the job identifier
of the job which will be retreived by ALPHA.
C) As an aid in converting Retrieval output into CDS input
transactions, users are urged to create the following two
data sets on their source libraries:
1) Input Job Control Language (JCL). The JCL described on
page 7-14, Figure 7-7 should be saved as a data set.
For the example used in Section 11.1.2, TRC used a data
set called IPT4JCL.
2) In order to know which columns the user is working on at
any given time, the user needs a data set called COL
which shows which columns are being used. The two lines
of this data set might consist of:
100 1 2 3 4 5
200 12345678901234567890123456789012345678901234567890
The command LIST COL will list this data set whenever the
user needs to know which columns his data is in.
11.1.2 CDS/ALPHA Example
Region IV wished to place the letter "M" in Regional Data Element 3
for each of its major sources. Instead of coding this character for each
of its 4,685 major sources, they used ALPHA to create one transaction
Card 1 for each facility. They did this by using the following steps:
11-3
-------
A) Formulated the following Retrieval selection cards:
01 04 Major SIP Facilities in Region IV.
10 APCD L 2
10 ECAT A 2
10 ECAT A 3
10 PTNQ M 000
20 QL
40 NOHD REGN SITE CNTY SRCE PTNO
B) Altered the EXEC statement of JCL cards to this format:
//RTV EXEC CDSRTV4,A=P
C) Submitted the retrieval request and waited until the job had
executed. They recorded the job id carefully since this in-
formation is necessary to retrieve the remote output for
ALPHA manipulation. The job id for this retrieval was "5U."
D) Used the following ALPHA commands to create input punch
card transactions for processing by the CDS Edit:
1) Sign on according to the proper WCC conventions.
2) RET 5U.SAVE
This command retrieves the output of job id 5U and allows
users to load the output into Working Storage.
3) LOAD *3,REC=80
The first 80 characters of each Retrieval Quick Look line
is loaded into Working Storage. Since this was a large
data set, ALPHA issued the warning:
046: WORKSPACE EXCEEDS LIBRARY SPACE
In the event of an abnormal termination, users will not
be able to continue the ALPHA session, but will have to
start from the top again.
4) PRINT *3,&OUTF=37,NUMBER=NONE,CONTROL=USE
This command lists the Retrieval output on the high speed
printer at Remote 37. Users should route their output to
their own remote number. If users are not sure of what
data was retrieved, they should consult this printout
before preceding further.
5) DEL-r/04/FIELD=2-3
This command deletes each Quick Look print line which does
not contain Region Code in columns 2-3. With one command
all heading lines are eliminated.
11-4
-------
6) LIST
Check out what is left in Working Storage.
7) REP / /,//
Eliminate all embedded spaces between Region, State, County,
Source, and Point numbers. Columns 1-16 of each punch card
are now ready.
8) LIST 1100-14 00 £ONTROL=NONE
Check out what is in Working Storage.
9) REP //,/001/,FIELD=17-19
Creates card columns 17-19.
10) LIST 1100-1400 ,CONTROL=NONE
Check out what is in Working Storage.
11) REP //,/M/, FIELD=68-69
Generates a "M" in column 69, RDE3.
12) LIST 1100-1200,CONTROL=NONE
Check out what is in Working Storage.
13) REP //,/C/,FIELD=80-80
Generates "C" in column 80, Update Code.
14) LIST 1100-1200,CONTROL=NONE
Check out what is in Working Storage.
15) INSERT IPT4JCL,10,10
Copies the data set IPT4JCL into Working Storage starting at
sequence number 10 and incrementing the copied file by 10.
Creates the run JCL for this file.
16) LIST 10-1200,CONTROL=NONE
Check out what is in Working Storage.
17) SUBMIT
Submit the job for processing by the CDS Edit.
18) BYE
Signoff after all ALPHA session is complete.
Figure 11-1 shows a sample ALPHA session used to convert Retrieval output
into input to the CDS Edit.
11-5
-------
? ret 5u,save
Remote Output - EPAEXC5U
•0 • System Messages
*1 " RTV.SYS006
• 2 • SORT.SYSOUT Figure 11-1: Sample ALPHA Session
•3 • STEP3.PRINTOUT
7 load *3,rec»80
0461 WORKSPACE EXCEEDS LIBRARY SPACE
7 print *3,route-37,number-none,control-use
139: 5X QUEUED
7 del -/OU/fleld-2-3
7 list
1100 Oil 01 021*0 00001 000
1200 Oil 01 02dO 00002 000
1300 04 01 0240 00003 000
1400 04 01 0240 06001 000
? rep / /,//
7 list 1100-liie6,control-none
1100 0401024000001000
1200 0401024000002000
1300 0401024000003000
IdOO OII0102U006001000
? rep //y/OOl/^leld-lT-lQ
? list 1100-liiOO/control-none
1100 Ofc0102l»000001000001
1200 01*010214000002000001
1300 01*01021*000003000001
ll»00 OI|0102I»006001000001
? rep //,/m/,fle1d«69-69
? list 1100-1200/control-none
1100 01*01021*000001000001 M
1200 0
-------
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
3AG NSPS sources violating or believed to be violating pro-
cedural or emission requirements.
3A3 Number of sources in compliance with procedural or emis-
sion requirements for NSPS.
AIR OUTPUT 6
6AA Number of sources in compliance with standards and
scheduled progress.
6AB Number of sources of unknown compliance status or in
violation.
6AC Number of enforcement actions.
AIR OUTPUT 12
12AA Number of non-transitory NESHAPS sources in violation
or of unknown status.
12A1 Number of non-transitory NESHAPS sources.
11-7
-------
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-2. 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-8
-------
AUTHOR TRC
1
/
/
/
/
2
/
/
/
I
3
E
E
4
p
O
5
A
F
6
i
PROGRAM NAME CDS/FORMAL REPORTING SYSTEM
TASK NUMBER
7
i
8
i
9
10
11
12
j
E
13
0
X
14
B
E
15
c
16
<
W
i
a
n
17
a
C
•
er
a
n
18
a
0
e:
i
a
19
a
S
a
20
a
F
21
1
R
22
i
s
23
i
n
1
1
1
a
24
i
n
S 1
5 t
5 I
re
25
)
the
the
O1
26
i
u
u
wo
27
i
se
se
d
hr
28
u
r1
r1
ig
ou
29
s
»
5
It
Jh
30
E
re
1C
31
*
1
a
91
.
32
ni
cc
on
33
i
t1.
OUI
Cl
34
0
ilS
35
f
it ni
Dde.
36
i
mb
V
37
T
38
i
er
a!1d
39
M
40
E
41
:
42
1
values
43
44
45
46
47
48
49
50
51
52
53
|
l
8
i!
-------
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 minimum 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 are included. These instructions are described briefly
below.
11-10
-------
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 and NESHAPS 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 re-
garding source self-monitoring. 11.3.2 establishes standard
action types to be used in tracking installation of continu-
ous types to be used in tracking installation of continuous
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 (poten-
tial) 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-11
-------
facilities, coal-fired industrial boilers (CFIB), and
major fuel-burning installations (MFBI) 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 four key coding requirements for fossil fuel-fired
steam generators are:
1. 6-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 sane ID amber as the source uses;
4. Capacity code wist be entered for CFIB and MFIB
to identify ranges of boiler capacity.
General coding 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 t-«»«-lm-g«-a1 liaison at DSSE or Franklin Smith at
(FTS) 755-0103.
11-12
-------
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.
11-13
-------
11.3.1 Coding Card 3
In order to support the FY'78 program plan requirements
to develop adequate SIPs for criteria pollutants in non-
attainment AQCRs, and to focus regional enforcement resources
on the most critical problem areas, specific data must be
compiled and made readily available to various offices
within the agency and within any given region. A separate
card has been established to satisfy these needs.
This card, Card Type 3, is used to add or change pollutant
compliance data on the CDS masterfile. The card is intended to
indicate worst-case compliance for each facility emitting any
criteria pollutant which may contribute to the non-attainment
status of an AQCR. The pollutant information on Card 3 replaces
the functions of AIR2 and RDEl as non-attainment indicators.
Card 3 data must be coded for all sources impacting on non-at-
tainment of an AQCR; i.e. , the source emits a non-attainment
criteria pollutant.
For each criteria pollutant emitted by a source in a
non-attainment AQCR, the following data elements have been
added to CDS:
Data Field Length
Pollutant ID (PLLT) 2
Pollutant Compliance 1
(PCMS)
Coding Considerations
Must be coded for each
criteria 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.
11-14
-------
Impacted AQCR
Indicator (PAQC)
Pollutant Emission 1 Must be coded for each
Category (PECT) applicable pollutant.
Valid values are the
same as for ECAT. This
field must represent the
potential uncontrolled
emissions for the
pollutant.
1 Must be coded as follows:
a. Code 'B1 if the
facility does not
contribute to the
non-attainment
status of the AQCR,
i.e. , a non-attain-
ment criteria
pollutant is not
emitted.
b. Code 'N' if the
facility impacts the
ambient air standards,
i.e. , a non-at-
tainment criteria
pollutant is emitted.
In addition to pollutant data, another data element we
would like entered on Card 3 is the facility capacity
(columns 58-64). Facility capacity is a seven-digit field
used to indicate the output or heat input capacity of an
entire source (including all Air Program Codes). However,this
is an optional entry which must be treated as confidential.
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.
11-15
-------
d. For incinerators (sewage sludge or municipal
refuse), use tons per day incineration rate.
e. For electric utilities, use total megawatt electrical
capacity.
f. For coal-fired boiler sources, use million British
Thermal Units per hour (MMBTUH) heat input capacity.
Besides normal information contacts used in
obtaining facility capacities, several other references are
available which contain such data for various facility
categories:
National Coal Association,
Steam Electric Plant
Factors 1976. This is an
annual NCA publication listing
plant-by-plant comparisons of
coal, oil and gas consump-
tion; cost, average
BTU and sulfur content;
plant capacity; net
generation and future
plant expansion programs
for electric utilities.
Call NCA at 202/628-4322
for copies.
York Research Corporation,
Air Pollution Control
Compliance Analysis Report
on Coal-fired Industrial
Boilers, December 27,
1976. This document
provides capacity informa-
tion on 931 sources (approxi-
mately 2740 boilers)
inventoried for a DSSE
contract. Each regional
enforcement division was
sent a copy on May
17, 1977.
11-16
-------
Energy Data System (EDS).
This is a data base
developed and maintained
by SASD at Research
Triangle Park, N.C. It
stores fuel quality and
consumption, plant design
and operating data, etc.
for power plants and
large industrial fuel
burners. Access infor-
mation, a user's manual,
etc. can be obtained by
calling Albert Wehe at
FTS-629-5345.
All other data elements identified in Attachment A of
the July 13, 1977 memo are also optional entries. Regional
discretion concerning the coding of these elements into
CDS is advised. A sample Card 3 coding sheet can be found
in Section 6 of the May, 1977 CDS User's Guide.
11-17
-------
11.3.2 Coding Related to Continuous Monitoring
Continuous monitoring (CM) requirements were originally
promulgated with the purpose of insuring that emission
control systems were properly operated and maintained, of
insuring that sources were properly operated and maintained
(for control of air pollution emissions), and to serve as
indicators of emissions. It has now been proposed to expand
the use of continuous monitoring data to directly determine
the compliance status of sources with present SIP emission
regulations. Through this expanded approach, it is believed
that more widespread and effective agency use of continuous
emission monitoring systems can enhance the likelihood that
sources will maintain their initial emission reduction
capabilities. Therefore, a more refined tracking system for
CM actions is necessary to monitor the installation, testing,
operation and reporting from sources affected by CM regulations.
CDS will contain continuous monitoring information,
entered on Card 7, for these source categories:
1. NSPS source category (APCD = 9)
Fossil-fuel fired steam generators
Refineries
Primary Copper
Primary Zinc
Primary Lead
Phosphate fertilizer
Coal preparation
Ferroalloy
Sulfuric acid
Nitric acid
Iron & Steel - Electric arc furnace
Iron & Steel - Basic oxygen furnace (proposed)
Kraft pulp (proposed)
Other categories, as required by future NSPS
regulations.
2. NESHAPS source category (APCD = 8)
Vinyl chloride
Beryllium (ambient)
Other categories, as required by future NESHAPS
regulations.
3. SIP source category (APCD = BLNK, 0,1)
as required by specific SIP or future regulations.
11-18
-------
To differentiate between NSPS, NESHAPS,and SIP sources,
please use the Air Program Code (APCD) entered in column 65,
Card 2. Similarly, any future source categories which may
be subject to CM requirements will be differentiated by the
Air Program Code.
The continuous monitoring action types are designated
by the letter prefix "M" followed by a number indicating the
specific action type. The following action types (entered
in columns 53-54, Card 7) are the CM codes to be used for
the appropriate sources. Please note the action types and
codes listed are changed somewhat from the July 13, 1977
memo.
1)
Action Type
Ml
2)
M2
Action Description
Notification of CM Specifi-
cation Test date.
Source must notify EPA of the
exact test date, but not less
than 30 days prior to such
test date. This date must be
entered in columns 61-66,
card 7.
Execution and submission of
CM Specification Test results.
Within 30 days after any
performance test (compliance
test), the owner or operator
shall conduct CM specification
tests and furnish EPA within
60 days thereof a written
report of the results. Use
this action type for both the
initial and subsequent CM
specification tests.
Use the following codes to
indicate results of test,
enter in columns 70-71, card
7:
11-19
-------
MC - CM equipment meets
requirements.
MV - CM equipment does not
meet requirements.
MU - Status of CM equipment
not currently determined,
due to no report or
insufficient information.
MR - CM equipment retest
required; include date
test rescheduled.
3) M3 Quarterly Excess Emission
Report (QEER) submission and
results.
Each owner or operator
required to install a CM
system shall submit a written
report on the occurrence of
excess emissions or CM mal-
function to EPA every calen-
dar quarter. The date for
the receipt of the initial
and subsequent, QEER must be
entered in columns 61-66,
card 7.
Use the following codes to
indicate adequacy of QEER
submission (content require-
ments of report identified
in Section 60.7, CFR), enter
in columns 70-71, card
7:
MA - QEER submission
adequate, No EPA action
required.
MV - QEER submission
adequate, however
enforceable excess
11-20
-------
emissions* found.
MO - QEER submission
adequate, however CM
system shutdowns and
malfunctions too numerous.
MD - QEER submission
adequate, however data
invalid and CM system
recertification required.
MI - QEER submission
inadequate or no submis-
sion reported, additional
information required.
A sample card 7 coding sheet can be found in Section 6
of the May, 1977 CDS User's Guide.
*(Enforceable excess emissions are excess emissions which
are not a result of malfunctions, and are above the
applicable standards.)
11-21
-------
11.3.3 Coding Related to New Source Review, Preven-
tion of Significant Deterioration, and En-
forcement
The Clean Air Act, as amended August 1977, created
several new enforcement tools, and expanded our role in New
Source Review and Prevention of Significant Deterioration.
Therefore, updating the CDS action type file is
required to reflect these new tools (e.g., DCOs, smelter orders,
civil actions, and non-compliance penalties). Also, with
regard to preconstruction review and approval of new sources,
more complete files must be maintained in CDS at the point
level to permit detailed tracking of affected units.
For sources subject to New Source Review (NSR) require-
ments (APCD=7), enter the facility into CDS if:
1. The subject source (or process) has a 100 tons per year
"potential" for emitting any regulated pollutant.
These would include any source in emission category
(ECAT) 2 or 3; 0£
2. The subject source must meet NSPS requirements. NSPS
source categories are:
Fossil Fuel-Fired Steam Generators
Municipal Incinerators
Portland Cement Plants
Nitric Acid Plants
Sulfuric Acid Plants
Asphalt Concrete Plants
Petroleum Refineries
Storage Vessels for Petroleum Liquids
Secondary Lead Smelters
Secondary Brass and Bronze Ingot
Production Plants
Iron and Steel Plants
(Basic Oxygen Furnace)
Sewage Treatment Plants
Phosphate Fertilizer Industry:
Wet Process Phosphoric Acid Plants
Superphosphoric Acid Plants
Diammonium Phosphate Plants
Triple Superphosphate Plants
Granular Triple Superphosphate
Storage Facilities
11-22
-------
Electric Arc Furnaces in the Steel
Industry
Primary Smelters:
Copper
Lead
Zinc
Coal Preparation Plants
Primary Aluminum Industry
Ferroalloy Production Facilities; or
3. A state or federal enforcement action occurs during NSR.
For example, a source began to construct before a
construction permit was issued, or it began operating
before an operating permit was issued, necessitating a
notice of violation.
All facilities and processes subject to Prevention of
Significant Deterioration (PSD) requirements (APCD=6) must
be entered and maintained in CDS. Any new source in an
attainment area, capable of emitting 100 TPY (uncontrolled),
and included in the following list is subject to PSD.
11-23
-------
Source Categories Subject to PSD requirements
1. Fossil-Fuel Fired Steam Electric Plants of more than 250
million B.T.U. per hour heat input.
2. Coal Cleaning Plants.
3. Kraft Pulp Mills.
4. Portland Cement Plants.
5. Primary Zinc Smelters.
6. Iron and Steel Mills.
7. Primary Aluminum Ore Reduction Plants.
8. Primary Copper Smelters.
9. Municipal Incinerators capable of charging more than
250 tons of refuse per 24 hour day
10. Sulfuric Acid Plants.
11. Petroleum Refineries.
12. Lime Plants.
13. Phosphate Rock Processing Plants
14. By-Product Coke Oven Batteries.
15. Sulfur Recovery Plants.
16. Carbon Black Plants (furnace process).
17. Primary Lead Smelters.
18. Fuel Conversion Plants.
19. Glass Fiber Processing Plants.
20. Hydrofluroic Acid Plants.
21. Nitric Acid Plants.
22. Sintering Plants.
23. Secondary Metal Production Facilities.
24. Chemical Process Plants.
25. Fossil-fuel Fired Boilers of more than 250 million
B.T.U. per hour heat input.
26. Petroleum Storage and Transfer Facilities with a
capacity exceeding 300,000 barrels.
27. Taconite Ore Processing Facilities.
28. Charcoal Production Facilities.
29. Any other source with the potential to emit 250 tons
per year or more of any air pollutant.
Each subject process must be entered and maintained for
NSR and PSD sources at the point level in CDS. A definitive
process description (PROS), SCC code (SCC8), emission
category (ECAT), and compliance status (CMST) must be listed
on Card 5 for each NSR and PSD emission point.
11-24
-------
It is possible that any given source or emission point
may be subject to the requirements of several programs, such
as NSR, PSD, NSPS, and SIP, therefore it is important that
the Air Program Code (APCD) be entered to adequately identify
the different processes associated with each program. However,
under each source, only the processes which are subject to a
particular program should be coded. That is, if emission
point "001" of source "ABC Industries" is subject to NSR and
PSD, an Air Program Code (APCD)=7 is entered on one Card 2
and as the first digit of the source number on source level
cards (cards 1-4) and any point level cards needed (cards
5-8)for NSR. On a similar set of cards, APCD=6 is entered in
the appropriate locations for emission point "001" to indi-
cate its PSD status. If emission point "002" of the same
source is subject only to SIP requirements, an APCD = J0 is
entered on card 2, and as the first digit of all source and
point level cards used for "002".(see Attachment E for
example)
The following list of action types for NSR, PSD, and
enforcement actions should be entered into CDS. Please note
this is a "bare-bones" list of action types reflecting only
essential information needs concerning PSD/NSR sources and
enforcement.
Mandatory Action Types for PSD/NSR Sources and Enforcement
Action Type Action Description
S8 Inspection by State
Rl Application Received by EPA
R3 Application to EPA Complete
R7** Final Determination by EPA
R8 Inspection by EPA
Tl Offset Determination by State
T5 Offset Determination by EPA
LI NpV Issued by State
L2 Civil Action by State
L3 Criminal Action by State
L5 NOV Issued by EPA
L6 Civil Action by EPA
L7 Criminal Action by EPA
** All processes with a final determination by EPA approving
a permit to operate should be duplicated (with appropriate
changes) and added to the SIP file (APCD=JJ).
11-25
-------
XI State Order Issued
X2 State Court Decree Issued
X3 Federal Court Decree Issued
X4 State 113d(1) SIP DC Order
Submtd to EPA
X5 State 113d(3) Replacement DC
Order Submtd to EPA
X6 State 113d(4) Inn. Technology
DC Order Submtd to EPA
X7 State 113d(5) Coal Conversion
DC Order Submtd to EPA
X8 1st State 119 Smelter Order
Submtd to EPA
X9 2nd State 119 Smelter Order
Submtd to EPA
Yl EPA 113a(l) SIP Order Issued
Y2 EPA 113a{3) Non-SIP Order Issued
Y3 EPA 113a(5) Stop Construction
Order Issued
Y4 EPA 113d(1) SIP DC Order Issued
Y5 EPA 113d(3) Replacement DC
Order Issued
Y6 EPA 113d(4) Inn. Technology
DC Order Issued
Y7 EPA 113d(5) Coal Conversion
DC Order Issued
Y8 1st EPA 119 Smelter Order Issued
Y9 2nd EPA 119 Smelter Order Issued
Results Code Results Code Description
01 Action Achieved
02 Action Not Achieved
03 Action Rescheduled
97 approved
98 disapproved
99 pending
A complete list of action types for coding NSR, PSD,
and enforcement actions (including the above mandatory types)
is summarized in Attachment F. Those actions listed in
Attachment F marked by an asterisk should be used in lieu
of regionally specified types. However, if the region has
already established a system for coding NSR, PSD, or such
enforcement actions, please send a list of your action
11-26
-------
types/descriptions to Headquarters as soon as possible
(Attention: Doug Carter, EN-341). Please equate HQ-defined
action types to those currently in use, e.g., R2 = 46, 51,
53.
Finally, several regions are currently entering fines and
penalties into CDS, however, uniform action types and proce-
dures at the national level have not been established. For
these reasons, we are officially creating nationally uniform
action types to be used in recording both civil as well as
non-compliance penalties. These action types are:
Action Type Action Description
Zl Non-compliance penalty hearing.
Z2 Notice of non-compliance.
Z3 State non-compliance penalty.
Z4 State civil penalty.
Z5 Federal non-compliance penalty.
Z6 Federal civil penalty.
The "Z" action types will be entered in columns 53-54,
card 7. The dollar amounts for all penalties will be
entered in columns 46-52, right justified, card 7 adjacent
to the appropriate "Z" action type entry. Penalty amounts
should be rounded to the nearest $100; do not enter commas,
dollar signs, periods, or cents. TRC will develop and
perform appropriate software modifications so penalty
amounts can be entered into CDS. The "date scheduled" and
"date achieved" columns for "Z" action type entries will
be used to record court-imposed payment schedules as well as
the actual date of penalty collection.
All other data elements identified in Attachment C of
the July 13, 1977 memo are optional entries. Regional
discretion concerning the coding of these elements
is advised.
11-27
-------
11.3.4 Coding Related to Power Plants and Coal-Fired
Boilers
The EPA Air Program Operation Guidance for FY'78 specifi-
cally identifies power plants and coal-fired boilers as priority
air pollution sources deserving close scrutiny. In an effort
to reduce the regional reporting burden for these sources, the
guidance emphasized generating most reports through detailed
information directly retrieved from the CDS file. This computer-
oriented approach also permits the regional offices to more
effectively use their limited resources to analyze compliance
information so that resources can be directed to those areas
where they will have the greatest impact.
The coding instructions for fossil-fuel fired steam
generators are concerned with power plants with capacities
of 250 million British Thermal Units per hour (MMBTUH) or
greater, and coal-fired boiler sources with capacities of 35
MMBTUH or greater. These size categories include sources
which potentially emit more than 100 tons per year of any
regulated pollutant; i.e. , emission category (ECAT) = 2 or 3.
The coding procedures that will be followed concerning
the above-sized steam generators are:
1. 6-digit Source Classification Codes (SCO must be
entered into CDS for steam generator sources.
This procedure will permit a convenient retrieval of steam
generator sources which the SIC code alone can not. Use columns
20-27 on Card 5, left justified, for this purpose. Please note
the SCC6 omits the facility capacity ranges identified by the
SCC8. (SCC8 is a confidential data element.) The following SCC6
codes are applicable to steam generator sources:
SCC ID SCC Category Names
101 001 Extcomb Boiler/Electric Generatn/Anthracite Coal
101 002 Bituminous Coal
101 003 Lignite
101 004 Residual Oil
101 005 Distillate Oil
101 006 Natural Gas
101 007 Process Gas
101 008 Coke
11-28
-------
101 Oil Bagasse
101 012 Solid Waste/Coal
101 999 Other/Not Class.
102 001 Extcomb Boiler/Industrial/Anthracite Coal
102 002 Bituminous Coal
102 003 Lignite
102 008 Coke
103 001 Extcomb Boiler/Commercl-Instutnl/Anthracite Coal
103 002 Bituminous Coal
103 003 Lignite
105 001 Extcomb Boiler/Space Heater/Industrial
105 002 Commercl-Instutnl
Most states already submit SCC codes to EPA for sources in
these categories, therefore minimum additional work is
required. Furthermore, on July 20, 1977, DSSE sent to the
following people the worksheets York Research Corporation
completed for the coal-fired boiler report. Air Pollution
Control Compliance Analysis Report on Coal-fired Industrial
Boilers (In these worksheets were the SCC codes for many of
the 931 sources identified):
Region I Thomas Hopper
Region II Jerry DeGaetano
Region III Nark Garrison
Region IV Janice Murphree
Region V George Hurt
Region VI Nary Kay Marusak
Region VII Patsy Burrell
Region VIII RoxAnn Varzeas
Region IX Marian Lundholm
Region X Betty Swann
2. Process description (PROS) must be completed in CDS for
each steam generator emission point.
This will be coded in columns 50-74 on card 5 for each
emission point. It is recommended that SCC terminology be
used as process descriptors. For instance, if a source
burned dry, pulverized bituminous coal in boiler #5, the
process description on card 5 would be coded as "PULV DRY
BIT COAL-BLR5".
11-29
-------
burned dry, pulverized bituminous coal in boiler #5, the
process description on card 5 would be coded as "PULV DRY
BIT COAL-BLR5".
3. Process description 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 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. Numerical values should be entered into CAPC, formerly
NEXP (columns 28-29 on Card 5), to identify boiler heat
input capacity for coal-fired boilers only (excluding
power plants). CAPC is the capacity code.
Presently, a retrieval can be performed only for wide
ranges of coal-fired boiler heat input capacity through the
use of the SCC code*. However, more exact source size data
are often needed for 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 boiler size will be entered as a 2-digit
number in columns 28-29, card 5, and be represented in tens
of MMBTUH heat input capacity per boiler (emission point).
For example, if boiler #1 at XYZ Industry is 150 million
BTU per hour, it would be entered as "15" on card 5.
All other data entries identified in Attachment D of
the July 13, 1977 memo are optional. Regional discretion
concerning the coding of these is advised.
11-30
-------
TABLE 11-1
SOURCE CLASSIFICATION CODES (partial list)
NATIONAL EMISSIONS DATA SYSTEM (NEDS)
SOURCE CLASSIFICATION CODE (SCC) REPORT
SCC 10
••••*•
1 It III IV 1
01 Otl *l EITCOHl BOJLCR
01 BOI 02 EXTCOMB HOILER
01 001 »3 EXTCONB BOILCil
oi ooi o« EXTCOMB bout.*
01 001 OS EXTCOMB BOlLtH
01 001 06 EXTCOHB HOILER
01 001 9« EXTCOMB BOILER
01 OOi 01 EXTCOMB BOILER
01 OOI 02 EXTCQMB BOILER
01 002 03 EXTCQMB BOILED
01 OOI 0* EXTCOM& riOlLEH
01 002 OS EXTCOMB BOILEM
01 00? 06 EXTCOMB BOlLtH
01 OOZ OT EITCONB BOILER
01 ooi oa EircAMB MOILEM
01 OOi Of ExTCOMB HOUER
01 00< 10 EXTCONB BOlLlH
01 OOZ II EXTCQNR BOILER
01 OOZ 12 IXTCOHB tfOILl'R
01 002 99 EXTCOMB HOILEM
01 001 01 EXTCOMB BOILER
01 003 02 EXTCOMB BOILER
01 003 03 EITCtlMB BO|LE«
01 003 04 CXTLUHB BOILER
01 003 OS EXTCUNB BOILEH
01 OOJ 06 EXTCOHB BOILER
01 003 OT rxTCOHB bOILER
01 003 01 EX1COMB bOILEt
01 003 01 EXICAMB BOILEH
oi ooj 10 CXTCOMB TOILER
01 OOJ II fXICOMB UOILLM
oi 003 iz EITCOMB BOILER
01 003 13 ElTCOMb BOILLR
01 003 14 EXICqMB'HOILLR
01 OOJ IS EXTCOMB BOUCM
01 004 01 OtC'HB HOILLR
01 004 02 MTCPMb nOlLlH
01 004 03 CiTCiMB dOKEH
01 00- 01 EXICilHB HOILER
01 101 OZ EXICliMU HOlLl"
01 00* 03 E*IC"MB tUILEil
01 006 01 EXTCUHB HOILEM
01 OOo 02 EMCQN6 HOILEM
01 006 OJ (XICUMB BOILE4
01 OOT 01 EXTCOHB HOILER
oi oor 02 EITCOMB BOILER
01 OO/ 03 EtlCOMB UOlLtil
01 00* 01 EtIC'IMh HOILER
01 Oil 02 ElTCOM* bfllLlH
01 on 03 r« icf.ua doilEc
SCC CXTEOORV NAMES
••••••§•••••••••••
II III
ItLECMIC OENtKtTNItNTHMtCirE COAL
ICLCCtHIC GENEdtTNIlNTHJtCITC COIL
IELECIMIC 6ENCH»TMI»NtMJiC|TE COAL
IELECIBIC mNCRiTNUNTM4«C|te COXL
IELEC1RIC CENEM*TNI»NTM4tCi;e COXL
IELECIRIC GENEKtTNIXNTHBiCltC COXL
IELECIMIC bENEHXTNIXNTrirfXCITE COXL
ICLECINIC OENCUXTNIOITUHIMOVS COXL
lELIClHlC CENEHXTNIBITUMINOUS COXL
IELECIMIC OEHEUXTNIHITUMlh'iUS COXL
IELECIMIC GENEHXINIdlTUHINOUS COXL
IELEC1NIC GENEM*TNIBITU4INOUS CO«U
IELECIHIC OENEMXTNIBITUMINOUS COXL
lELCCTMlC GENEk*TNIdllU4|NOuS COXL
IELECIMIC GENEuXTNIdllUMINOUS COXL
IELECIMIC bENC4XTNIblTU>i|NOUS COXL
IELECMIC GENEWXTNIBIIU'INOUS COXL
lELECtMJC GENEI*XTNIRITU>i|NOUS COXX.
IELEC1MJC GENEM.TNIhlTylNOuS COXL
(ELECTHtC uCNCMitNldltUxIHOUS COXL
ICLECTMIC GENERXTNIUGNI1E
(ELECTRIC GENEMXTNILIGNUE
(ELECTRIC OlNEMlfNILIGNllE
IELECTMIC GENEMiTNILlGSITE
lELECTMlC GENEMXTNILlGKITE
IELECTMIC GEnEHXlNILlGNIIE
lELfCtHIC GENEhiTNlLlGHItt
IELECTUIC GENEMtTNILIONITE
(ELECTRIC GENERXTNILIGNITE
(ELECTRIC fiENEfcXTNIllGHITE
IELECT4IC (lEiEMtfNIllGMMt
IELECTMIC GENEMXINILIGNIIE
IELECTRIC GLNEMXTNILIGNltE
IELECT4IC GENEHITNILIGNITE
ICLECTmt OENERXtNILtGMTE
IELECT4IC GENCRXTNIriESIOUXL OIL
(ELECTRIC GLSEMXTNIMESI9UXL OIL
IELECT4IC qENEHtTNlCESiqUXL OIL
IUECMIC GENEMXTNiniSIILLXTC OIL
(UECThlC GlNt-ilNIOIStlLLUE OIL
IELECNIC •ittEfXINIOISTlLLXTE OIL
IELECTMIC GENEMXTNINXIUUXL ftXS
IELECTMIC 3E»ENXTNINXTU!iXL GXS
(ELEClHlC OENERXTNINXTU>XL HXS
IELECTMIC uCMERxTNlfROCESS «XJ
lElCCtulC GFNEfcXtNI^ROCtSS «A
IELECTUIC GlNEkxTNIcilOCtSS *»»
(ELrCTMlC UlEMiTNICOKE
ICIECIHIC fitutiiXINIHXOXkSt
(tLECIiHC GCNirxINIdXGXHSC
IV UMITt
I»IOOMNBTU PULV1IOITONS BUMNEO
I»100MMHTU STOKERSITONS BUMNEO
IIO-IOOMMBTU PoLVOlTONS bUMNEO
IIO-IOOMMBTU STOARITOMS bUxhCO
(<10MMBTU PULVUEOlTONi BUiiuEO
HIOMMBTU STOKLM I TONS HUMMED
IOTHEM/NOT CLXSIFOITONS BUKNEO
(>IOONHrtTU PULV'ETIIONS bUHnEO
OIOOMMMTU PULVOhTIIONS BU4HEO
OlOOMIUtU CYCLONE (TONS BUhiEO
OIOOMMHTU SPOS.TKRITOMS dUMMEO
OIOOMMOTU/HH 0' SKI TONS bUMNEO
IIO-IOOMMdTU PUL»TIIONi HUMilEO
IIO-IOOMMBTU PuLOritONS UUHSEO
IIO-IOOMNBTU OfSlKITONS BUnNtO
IIO-IOOMMBIU UfStKltONS BUHSEO
KIOMMBTU OFSTUKLRlTONS dUHiEO
KIOMNHTU UFSTOKERITONS 8UKNEO
KIOMNBiu PULV-OMVITONS BU^».EO
1 OTHER/NOT CLXSIFOITONS BIMNEO
I»IOOMNMTU PULVHETlTONk BUMNEO
l»IOOMMuTU PULVONTIIONk BURMEO
(>IOONNi«TU CTCLONEITONS BUMPED
IMOOHMritU OF SKBITOMi BUMNEO
IHOOMNlTU OF STxRITONS BU4-EO
ItlOOMMnlU SfObTKRITONS bUMHEO
IIO-IOOMMBTU OTPbLITONS 4U-I..EO
IIO-IOOnMBIU klPULITONt BUN-.EO
UO-IOO-MrtTU OFSTRIIONS BUHiEO
IIO-IOOMMdTu WSTKITONb-BUMiiEO
110-100'MBTUSIT.bTKITONS BUnKEO
KIOMMBTU PbLV OMriTONS BUMnEO
MIOMMUIU OF MOKRITONi BUMNtO
KIONMBTU UP STO^RITONS BUMHEO
I|OOMHRTU/MR CINLIIOOOGXLLONS BUMNEO
1 1 0-1 OOMNAIU/MHGNL 1 1 OOGGXLLQKS BuRNEO
|<|OI«MBTU/H4 GINL I10006XLLONS BUMNEO
OlOONMHTU/Hri iiEhLIIOOOOXLLONS BUMNEO
IIO-IOONMOTU/MxbNLIIOOOMLLnNS MUMNlO
|c|OHMBTU/H» GiNL I1000CXLLONS HUHlCD
OlOOMMtTU/xM (MILLION CUBIC FEET BURNti)
IIO-IOOdTU/i
-------
TABLE 11-1 (Continued)
NATIONAL EMISSIONS DATA SYSTEM (NEDS)
SOURCE CLASSIFICATION CODE (SCCj
i
OJ
ho
SCC_IO
t II
01
01
•1
01
01
01
02
02
02
02
02
02
it
02
02
02
•2
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
•2
v*-^
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
00)
00)
00)
00)
00)
00)
00)
001
00)
001
OOJ
001
001
001
001
001
00*
00*
004
00*
DOS
(IV.
01
02
01
9T
9*
•9
01
02
01
04
OS
06
OT
99
01
02
01
04
OS
06
OT
00
0«
10
II
12
11
14
99
01
02
01
04
OS
06
OT
0*
09
10
II
12
11
14
IS
16
01
02
0)
01
02
SITCOMS
EXTCOMB
EXTCOHB
EUCOMB
EXTCOMB
EXTCOMB
flTCONB
EXTCOMB
EXICOMB
CXTCONB
CXTCONB
EXTCONB
EXICOMB
ExICONB
EUCOMB
EXICONB
EXTCOMB
EkICONb
EXICONB
EXTCOMB
EXICOHb
EXTCONB
EXTCONB
EAICOMb
EXTCOMB
kXTCONB
EUTCOMB
EATCOMb
EXTCOMB
EXIC'mB
EXTCOMB
EXICONb
EXTCONB
EXTCUNb
EXTCDHB
EXICONB
EXTCQNB
LX ICONS
ExTCuMb
k xTconb
EXTCONB
EXTCbMb
EXTCOMb
EXTCOMB
LxICDNb
txTCONB
tlTCOMM
ExTCOMt
ExTCrtMb
1
NOlLEM
BOILER
BOILEH
BOILCR
BOILER
BOILER
BOILER
•OILCN
BOILER
BOILER
bOILCR
BOILER
BOILER
BOILEH
BOIIiH
BOILER
MlLfR
BOILER
MOILEM
dOILER
BOILER
bOILEM
BOILEH
BOILER
dOlLEH
BOILER
BOILER
HOILlR
BOlLlR
BOILER
dOlLtx
BOILER
dOILEH
ROILEM
BOILER
BOILER
BOILEM
BOILEM
BOILEH
bOILE4
bUILEM
BOILEH
dOlLCM
BUILEM
BOILtH
faOILkH
BOILER
HOlLER
bOlLtM
dOILCH
SCC CATEGORY MANtS
II
III
ICLECTMIC GENERATNISOLIO dASTE/COAL
(ELECTRIC bENEHATNl SOLID HASTE/COAL
IELECTHIC GENERATNISOLIO »»STC/COAL
IfLCCMIC GENEAATNinTHFM/hOT
IELECIMIC GENEfcifNIOIHlM/NOT
IELEC1HIC GtNEHAlNIOTMEN NOT
(INDUSTRIAL
(INDUSTRIAL
ItNDUSTHIAL
1 INDUSTRIAL
IINOUSTMIAL
(INDUSTRIAL
IlkOUSlHlAL
llNdUSTHIAL
1 INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
IINOUSTUIAL
i INDUSTRIAL
I INDUSTRIAL
1 INDUSTRIAL
IINOUSTMlAL
(INDUSTRIAL
I INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
i INDUSTRIAL
1 INDUSTRIAL
(INDUSTRIAL
IINOUSTMlAL
IINOUSTMlAL
(INDUSTRIAL
(INDUSTRIAL
IINOUSTUIAL
IINOUSTMlAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
1 |NOu&T*IAt.
IINOUSTMlAL
IINOUSTNIAL
1 INDUSTRIAL
l|NDUSTIi|AL
llNOUSIklAL
(INDUSTRIAL
llhDUSI'IAL
(INDUSTRIAL
IANTHHACIIE
(ANTHRACITE
lANThWACITE
(ANTHRACITE
IANTH4ACIIE
IANTHMACITE
(AHlh.ACITC
(ANThRACIIE
IBITU'INOUS
(BITUMINOUS
IBITUNlNOUS
IdllUMlNOUS
|A|TU<*|NOJS
IRITUMINOUS
IKIIUR. INDUS
IR1TU-MNOUS
IBITUNlNOUS
(BITUMINOUS
|R|TU«INOUS
IMITUMlNflUS
ldITU»INOUS
(BITUMINOUS
(iIIU«INOUS
ILIGNITE
II IGNME
ILIGNITE
(LIGNITE
ILIGNITE
(LIGNITE
(LIGNITE
(LIGNITE
ILIGNITE
ILIGNITE
ILIGNITE
ILIGNITC
IL IGNITE
ILIGNITE
ILIGNITE
(LIGNITE
IV
IMOONNBTU/NM (TONS
110-lOONNOTU/Nw (TONS
|<|OMMBTU/HH (TONS
UNITS
bUMNEO
BUM(.EO
BUHNEO
CLASIFUISPECIFt |N HENARKlNlLLION CUBIC
CLAS|FO(SPECIFY IN MEMAHKJIOOO
CLASIFOISPECIFY IN MEHAHKIIONS
COAL
COAL
COAL
COAL
COAL
CUAL
COAL
COAL
COAL
CUAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
COAL
IHlSIOUAL OIL
IHESIOUAL OIL
I4ESIPUAL OIL
(DISTILLATE
IUISTILLAIE
OIL
OIL
IMOOMMflTU/HH fULVITONS
!>100NM«TU/nR STKRIIONS
IIO-IOVMMBTU CULVDITONS
IIO'lOONNdTU STUD (TONS
K|OMMhTU/HM PULVOITONS
KlUMMtttU/HH STUN (TONS
(tTU CfCLONElTONi
OIOOHMATU SPDblKRIIONS
MO-lOOMNbTU OF!,TKITONS
IIO-IOOMMBTU UFkTRITONS
IIO-IOOHMBIU PULdTITONS
110-lOOiNBTU PULOYITONS
( 10-1 OORMBTUSPuSTK ( TON*
(IOONNtIU OFSIKH (IONS
(>IOONH4IU UFSTKR (TONS
mOOHNiiTU SPOSTHRITONS
IIO-100MNBTU DfPULITONS
IIU-IOOXHBTU dTPULITONj
ilO-IOOMMRTU OfSTHITONS
IIO-IOOMMoTU UFSTKdONS
IIO-lOOtHBTUSPliSTKIIdNk
|«|OHNHTU PbLV dMVITDNV
(IU OrSIO'H (TONS
KIOMNblU UFbTUkN IIONJ
KIONNBTU FANDFIREITONS
|€|ONNBTU SPDSIKR (TONS
IMOOMM-UU/MH 11000
(Id-IOOMNBlU/HK (1000
KIOKMBTU/HK 11000
l>IOOMI>rilU/MU (1000
II. 100MMBTU/MM 11000
GALLON
BUKNEO
BUMNEO
BUMfcEO
BUNKED
BUNrfEO
BUMNEO
BUUNEO
BUriKEO
BUNNEO
dUMNEO
BUH»EO
BURNED
BURKED
HUMhEO
BURNED
bUMKEO
BUMkEO
bUNNEO
BUHNEO
BuArtEO
BURMEO
BUHAEO
dUMNEO
BUHNEO
BUMNEO
BUMI.EO
BUHMEO
BUMNEO
BURitEO
BUUNEO
BUHitEO
BUMNEO
BUMNEO
BUNKED
aUMhEO
bUMNEO
bUkMO
bUXMO
BURnEO
BUMNEO
GALLONS
GALLONS
GALLONS
bALLONS
GALLONS
FEET BURNEO
(LIQUID) BUMNEO
(SOLID)
BURNED
bUMNEO
HUMMED
BUMNED
bUMMO
-------
TABLE 11-1 (Continued)
NATIONAL EMISSIONS DATA SYSTEM (NEDS)
SOURCE CLASSIFICATION CODE (SCC) REPORT
i
u>
SCC 10
••QIC*
t II III IV
az OH 01
02 006 01
02 006 02
02 006 03
02 OOT 01
tt OOT 02
02 OOT 0)
02 OOa 02
02 000 01
02 00* 02
02 00« 03
02 010 02
02 010 03
02 Oil 02
02 Oil 03
02 999 9T
02 999 -90
02 99* 99
01 001 OS
03 001 06
01 001 OT
01 001 00
01 001 09
OJ 001 10'
01 001 99
01 002 OS
01 002 06
01 002 OT
01 002 0«
01 002 09
01 002 10
Ot 002 II
01 002 12
01 002 13
01 002 I*
01 002 9V
01 001 OS
01 001 06
01 001 OT
01 001 Ot
01 001 09
01 001 10
OJ 001
01 001
01 001 ._
01 001 I*
01 00* 01
01 004 02
OJ 00* 03
01 00» 01
scc CATEGORY NAMES
it
in
tv
UNITS
EXTCONff
EXTCOMB
CXTCOMB
EXTCOMB
EXTCOHB
EXTCOHB
EXTCQMB
CXTCOMB
EXTCONB
CUT COMB
EXICOMB
EXTCONB
EXTC4MB
EXTCiiNU
CXfCOHB
exTCQMB
EXfCOMB
EXTCOHB
ExrCOMB
EXTCOMB
EXTCOMB
EXTCOMB
EXTCOHB
EITCONB
EXTCflNB
EXTCOMB
EXTCONB
EXTCOMB
EXTCOMB
BOILER
BOILER
BOILER
EXTCQMB
(XTCOHB
CXTCOMB
EXTCONB
fllCONB
EITCQNB
II
12
II
CXTCiIMB
EXTCOMB
EXTCOMR
CITCOxft
EXTCDMB
EltCOMB
CXTCUNB
EXTCOMB
EXTCOMB
EUCOMB
BOILER
HOILCR
BOILEM
BOILER
bOlLER
90ILEO
dOlLEH
BOILER
bOlLER
dOlLEri
BOILER
BOILER
BOILER
BOILER
BOILER
HOlLER
BOILER
BOILER
BOILER
BOILER
BOILER
bOlLEM
BOILER
ROILCR
dOtLtN
HOIlEK
dOUEN
NOILCR
doum
nOlLEH
aOKER
BOILLH
NOIiEH
nOlLt'
HblltN
NOILE"
HOlLt"
El'COxb
tXTC'mb
ilOILE*
BOILEM
ROILCN
xOlltii
90lLl.li
HOILEI
(INDUSTRIAL
UNOUSTMIAL
HNOU»TI*IAL
IINOUM«I»L
(INDUSTRIAL
I INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
(INDUSTRIAL
IINOUSTMIAL
IINOUSlHlH
I INDUSTRIAL,
IINOUST-IUL
(INDUSTRIAL
(INDUSTRIAL
ICUNNEMCL-INSTUTNLIANTH4ACITE COAL
ICONNtxCL-INSTUTM.1 «NTM«»C(TE CO*L
ICONNCHCL-INSTUTNLIINTrihACITC COAL
ICOMNEMCL-|NSTUTNLI«NTMUtCITE COM.
ICQHNCMCL-|NSTUTNLI*NTHI.AC1TE CHAL
ICOMHEHCL-INSTUTNLIANTHRACITE COAL
ICOMNCHCL-INSTUTNLIANTMVACITE CO»L
ICOHNCrtCL-|N$TUTNLIMTUH|NOUS COAL
ICONNLMCL-INSTUTNLIBIIUMINOUS COM.
CONNEMCL-INSTUTNLIHITUXINOUS COAL
ICOMNENCL-INSTUTM.IBITUMINOUS COAL
ICONNEMCL-INSIUTNLIBITUIIMOUS COAL
ICOMNE4CL-INS TulNLIHITUMtNOUS COAL
ICONHEriCL-|NSIUTNLI4ITU»|NOUS COAL
ICOMMti(CL-|NSTUTNLI.-IITUM|NOUS COAL
ICONMEHCL-IMSTUTNLIHITU<>INOUS COAL
|COHNCHCL-|NSTU'NLIK|TUX|NOiIOONNHTU/MM (MILLION CUBIC FEET BURNED
IIO-IOOMNBTU/MM (MILLION CUBIC FEET BURNED
KIOMMBTU/NR (MILLION CUBIC FEET BURNED
IIO-IOOMMBTU/MH ITONS BUriNEO
I«IONNBTU/HR ITONS BUMnEO
IKOOO MASTE BOILER ITONS BURNED
i SMALL HANDFIRE ItONi BUMNEO
ILIO PETROLEUM OASIIO-IOOMMBTU/NH
ILIO PETHOLEUN 6AS«IONNBTU/Nil
(BAGASSE ||g-lOOHM8TU/»1il
(BAGASSE «IOMNBTU/rih
IIOOOGALLONS BUHNEO
IIOOOGALLONS BURNED
(TONS BUkNEO
ITONS BURNED
(OTMEM/NOT, CLASIFOISPECIFY IN REMARK I MILLION CUBIC FEET BURNED
lOtHEO/NOT CLASIFOISPECIFT IN REMARRIIOOO GALLON BURNED ILIOUIOI
ICUHMCIiCL-INSTulNLILIbHiTE
ICOMNCMCL-INSTUTNLILICNIIE
ICOHMLRCl-INSTUINLILlBIIIE
ICOMMEnCL-INSTUlMtU I6MI II
IC'MNEMCL-INSTbTKLI-'ESIOUAL OIL
ICOHorrfCL'linTbTNLIx'SfjUil OIL
ICOMMC-tCk-IHlTUlMLIkEtfOliAi. OIL
ICO«0«t«CL-|«*TUTM.IUISIlLL»tf
NOT; CLASIFDISPECIFV IN NEMARKITONS BURNED ISOLIOI
------- I IO-100«NBTU PbL*TITONS BURNED
IIO*IOO«MdTU PULDTITONS BURNED
IIO-IOOMMBTUSPOSTllllONS BUHNEO
|«|OMMBIU PULVIIEOITONS BUHNEO
I«IONMBIU STOKER ITONS BUHNEO
HIOMHblU SPOSIOKHITONS BUUMEO
IOIHER/NOT CLASIFUITONS BUMMED
IIO-IOOMMBTU PUL'TIIONS BUMMED
IIO-I004NBTU PULOY ItONi BUMNEO
IIO-IOOHMBTU OFSTKITONS BUMNEO
IIO-I004HBU UfSTKITONS BURkEO
(U-lOO-MiTUSPOSTiCIIONS HUMNEO
IIO-IOOfMRTU HtNFRITONS BUMPED
I«|OMN8TU OFSTOKER(TONS bUxMtO
KIONNdTU UFSTO«ER|tONS BUNfEO
KIONMBTU SPOSTOKRITONS BUHNEO
KIOHM8TU HANDFIAEITONS BURNED
IOTHEH/NOT CLASIFOIIONS BUMNED
llfl-IOO«M»ru PUL*T|TONS BUHNEO
ItO-IOOtMJTU PULOTIIONS BUMkEO
IIOrlOOMHiTU OFSTKIIONS BUMfcED
IIO»IOOMM0tU UFSTKITONS BUMNEO
110-IOOiMBTUSPUSTKITONt BUMPED
MIOMHBTU PUl»-OHT ITONI bUMNEO
KIOMMHIU OrSIUKERIIONS BUMNED
KIOMNHTU UFbT/MERITONS BU4»EO
KIONXRIU SPOSTOKRirONS BUillEU
IIO-IOOM(i4TU/hK
KIONHBTU/IM
I»IOO BUHNEO
1 1 000 bALLONk bUHNCO
1 1000 GALLONS blMNEO
-------
TABLE 11-1 (Continued)
NATIONAL EMISSIONS DATA SYSTEM (NEDS)
SOURCE CLASSIFICATION CODE (SCC) REPORT
i
to
SCC 10
••f•••
I II III IV
01 005 02
01 OOS 01
OJ 00k 01
01 006 OZ
01 006 01
01 00V 01
01 010 02
01 010 01
01 999 9?
01 9*9 90
01 999 99
01 001 01
•1 002 01
01 001 01
01 999 9T
01 499 98
02 001 01
02 001 02
02 002 01
02 002 02
02 001 01
02 00* 01
02 999 9T
02 999 98
01 001 01
01 999 9T
01 999 98
0* 001 01
01 001 01
01 001 99
01 002 01
01 002 02
01 001 01
01 003 02
01 001 01
01 001 99
01 00* 01
01 00* 99
01 00k 01
01 00» 02
01 OOS 01
01 OOS 0*
01 005 OS
01 OOS 99
01 006 01
01 006 99
01 OOT 01
01 OOt 99
01 008 01
01 00» 82
E1TCOMB BOILEU
IITCUMB 00ILLR
EITCONB dOKEtt
EITCONfi dOUER
EITCOMb JOILER
EXTCOMB aOILfH
£XtCOMB BOILER
EXTCOMB BOILER
EITCOMB KOILER
CItCUMB BOILER
EITCOMB BOILER
SCC CATEGONV NIMCS
••••••••••••••••a*
II III
ICONNEUCL-|NSTUUd.lUlSTILLAlE
ICUMMEriCf INSIUTNLIOISIlLLlTE
ICOMMEKL-INSTUTNLINilUrfAL 04$
ICOMHENCL-INSTUTNLIN1IU4AL «*S
UOMHEiiCL-INSTUlNLlNUUiiAL tfAS
ICOMNE4CL-INSIUTNLIHOOD
IW
110-IOOMHBIU/Mn
M10NMBTU/HM
l»IOONNhlU/KM
IIO-IOONNBTU/IM
I«ION*BTU/HW
KIOMMBIU/nU
UMflS
11000 liALLONS BURNED
11000 GALLONS BORNEO
(MILLION CUBIC FEET 6URNEO
(•ILLIOAJ CUBIC rtET. BURNtO
MILLION CUBIC HI! HUMNkl)
i TONS BUMKIO
11000 GALLONS BURKED
11000 OALLONS BURNED
»tTHULIUM OASIIO-IOOMNBIU/IM
PftHULEUM GASKIOMMUTU/HM
ICOMNEhCL-INSTUTNLIOlNEU/IIQT CL*SirOISPECIFV IN «••»«« I MILLION CUBIC FEET BURNTO
ICOMMEriCL-INStUTNLIOTNE^/IMI CL*SI'OISBECIf * |M REMAMMOOO CALLOW BU>NEO (LIQUID)
ICOMMEMCL-lNjTUTNtlOTME«/HOI CLASIFOISfECIFT IN RE"»«HOMS BUMMED I&OL)OI
INTERMLCOHBUSTlOMlELCCIulC GCNEIiAINIillSIILLAlE OIL HuktflNF 11000 atUONS BUMkEO
lNtPOCESICNEMICAL MFB
INDUSTRIAL PMKESICMCMIC4L «Tfi
INDUSTRIAL PMOCESICHIHICAL »«•
INDUSTRIAL PHOCCSICHENICAL MF«
(TONS PRODUCED
CLASIFOITONS PRODUCED
IAMMONIUM NITMATE (GENERAL (TONS PRObUCLO
(AMMONIUM NITRATE (OTHIR/NOT CLASIFOITONS PRODUCED
ICARHUH M.ACK (CHANNEL PUOCESS I TONS PRODUCED
ICAHBUN BLACK (THERMAL PROCESS (TONS PHOHUCtD
ICARBON BLACK IFuHNACf PROC OAS IIONS PRODUCED
ICIRdfN BLACK (FURNACE PROC OIL (TONS PRODUCED
(CARBON BLACK IFUHHACE M/GAS/OILIIONS PRODUCED
ICARBON BLACK (OTHER/NOT CLAbFO ITONS PRODUCT
ICMAPCOAL NFS (PTROL/UlSTlL/GENLITONS PRODUCED
ICHAkCO'L NFG IOIMER/NOT CLASFD IIONS PROOUCI
ICMLOHlNE (GENERAL (IONS MObUCEO
ICKLO'lNf IOTNER/MT CLASIFOITONS PRODUCED
ICNLlM-AL'ALI ILIOUIFIN>0|A*H«QN||00 TUNS CHLORINE LIOUEFIEO
ICNLna»IL«ALI ILIdUIFTN-KERC CELIIOO TONS CHLORINE
-------
11.3.5 Example Coding of Industries into CDS
The scenarios for which we developed our coding examples
are:
1. ABC Industry
a.. 5 coal-fired boilers.
b. heat input capacity - 1500 MMBTUH.
c. in non-attainment AQCR for S0_.
d. in attainment AQCR for TSP.
e. existing SIP sources - boilers #1,2.
f. operating NSPS sources - boilers #3,4.
g. subject to CM - boilers #3,4.
h. under construction NSR/NSPS source - boiler #5.
i. subject to PSD - boiler #5.
j. subject to Emission Offset Policy - boiler #5 (S0_).
2. XYZ Industry - existing SIP source new to CDS.
a. 1 coal-fired boiler.
b. heat input capacity - 300 MMBTUH.
c. in non-attainment AQCR for TSP.
d. in attainment AQCR for SO^.
The attached coding sheets (1-6) illustrate how the
above data are entered into CDS. However, we have included
several additional details listed below in an effort to
apply as many new coding requirements as possible. For
instance, ABC Industry SIP boilers are assumed already
in CDS, we only added more detail at the emission point
level, therefore a "C" is used as the update code. Because
ABC Industry is an existing CDS source, the 000 point
was already in the system. Conversely, XYZ Industry is a
new source to CDS , therefore the 000 point as well as
the "N" update code are entered for this source.
Other situations built into the examples are:
1. Pollutant loading (predicted actual emissions in tons
per year) was coded for all NSR sources, thereby
normally encompassing PSD and NSPS sources as
well. Entered in columns 29-33, 41-45, and 53-57,
Card 3.
2. NSPS sources under construction (APST=C) are coded
separately from those in operation (APST=0) or
planned (APST=P). Entered in column 66, Card 2.
11-35
-------
3. For ABC Industry, the state NOV issued on 11/23/77,
shown on coding sheet 2, required a construction
permit application to be submitted to the state
within 30 days. The state has 90 days to review the
permit application, including offset policy conside-
rations, prior to making a final determination oh
boiler 5 construction.
4. Because ABC Industry did not submit a PSD applica-
tion to EPA within the 30 days following the state
NOV, EPA issued its own NOV on 12/23/77, shown on
coding sheet 5 The source then has 30 days to submit
a PSD application for boiler 5 (particulate and SO-
emissions).
Finally, please note that the procedural compliance
status (CMS2) should now be entered on column 79, card 5 in the
space formerly known as AIR2. As is the case for CMST, the
worst-case boiler determines the procedural compliance
status for the entire source (000 point). The
A, B, C codes for CMS2 are explained on page A-37 of the
May, 1977 CDS User's Guide.
Sources subject to SIP, NSR, NSPS, PSD, and CM regula-
tions, in order to satisy Federal Register requirements,
must submit certain inforamtion to EPA. Therefore, regional
offices normally will have files containing such data as
outlined above in the example scenarios. Please see your
supervisors to determine the whereabouts of these files in
your office.
In case of difficulty locating the requisite information
for coding CDS, it is worthwhile noting that Federal Register-
required data submittals are frequently used to support
or instigate enforcement actions. These submittals are
generally directed to the Enforcement Division Director.
Therefore, your regional enforcement division would be a good
place to look for information not readily available.
11-36
-------
COUNTY I SOURCE Nimr.fr
I CARU CODETM AVCR I CITY CODE
1. COMPLIANCE DATA SYSTEM CODING SHEET 4*- Xlftc
-------
REGIONi ST
21J
COUIITT
CAUL) CODE TV
SOURCE
AUCR
JL COMPLIANCE DATA SYSTEM CODING SHEET 4U.A6Q. «J
' .^.i,">
I I CITY NAME
. ... M .... ^ -
lololololoMMMdJirM I I ITT
ROE 6
I STAFF
m ri n 1 1 1 1 1 1
1 1 1 1 1 1 1
I I hi'I
POIL
H .^*
POLIUIANI 13
da BI
: NO
SOURCE COMMENTS
w2^
|0|0|0|0|0|4| I I M I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I t I I I I I I I I I I I I I I I
OINTHOl I I SCC CODE MmCSI PlUll STATE REGULATION
MysPlopli.|ilaEflifl3 I I I1i3 EH I ~l I II I I ITTTTTT
PROCESS DESCRIPTION
PutV
68I69I70I/I
isns.
n.
13.
I I III II I I I I II I
Id.Ukl
I I
LO
00
I I I I I I I
i kl 11
11 III IIII11III
3|g|MNikkl Islolol^jclel I I I I I I I I I I I
I I
B|H
Q|oH I I I
I I I II II II I I II I
11 n 1111 n n 111111111 M M
J_L
HO
EMISSION POINT COWENTS
T71I2.
o|o
Jfi.
li
IS §0
59
60
67
68
ii
22.
72
75
76
77
Lu.
010
I I I I I I I I I I I I I I I I I I I I I I I I II I I I I I I I I I I I I I I I I I I I I I I I I I I I M | M I
EMISSION ACTION
NO I NO I I
OPTIONAL ACTION DESCRIPTION
USED WITH ATPE M
•
I
ACTION RESULTS
ITTPEI DATE ACHIEVED I DATE SCHEDULED I STAFF I |ROE B|
imaasaasKK^^
ShlrlEl WPlPlLfcl
1
m
HEU^|Hs|e|ilJ£HztetSfc$JM^^
nlih
NO.
ACTION COHNENTS
201
J 34 35 it 37138 39HOI4I 4Z 43 44 4546 47I4B149 50 51 Ki 53 5415b 56157 I5H59160 6116^ 6316416!) 66167 61! 69J70I71172
nm
-------
BCCIQN. «jT I COUIITt [SOURCE HUil!
Ill Zl 3 11 K Ifi I / 11)1 9IIOIIII!?
3. COMPLIANCE DATA SYSTEM CODING SHEET -f»v ABC
I *<
I CARD CODE "TM AUCR | CftT CODE |
|l«M|lt|i;|n'
|o|o|o|o|o
SOURCE NAIIE | STREET ADDRESS
bd/JlbWsHdyl I I I i I I I IstrisUffy/ylSIrr TI I I I
ROE 4 I ROE 5
l|/?|73[/i[i5[>M77[JI
! I 1 ill I I I TI cl
111111111 ri nrrn rrniM i rnTii i ii 111111111 minim rn
loloiololoN I I I I I I I I I I I I I ill I I I.I I I I I I I I I 11 i I 11 I I I I I I I I I I I I I I i I I I I I
---------
I LI I I
^LHfC, \
WSTcfts^
I I SCC CODE
STATE REGULATION
I I Mil ISI2J I I I II II I II II II ialPlulJx/l !3>lRlyl iBlihrf IdoULI IEIU/L|3| I I
PROCESS DESCRIPTION
ini
d
11
Ik
JpH
I I III Mill III I
Ibldylbl-.M LLULI iBLkbl I I
w
VO
I I III II II I I II I
bldvl Ifcl'.M IdoUld lekkkl I I
11
Jsk
I I I I I I I I I I I 11 I
Ibldvl iRliH HoUJLl
11
kfcl
EMISSION POINT COMMENTS
10.
111
45
47
29.
I I loio
I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I II M I I I I I I I I I I I I I I I I I I
EMISSION
IPQIMT NO
ACTION
NO.
OPTIONAL ACTION DESCRIPTION
USED WITH ATPE 00
ACTION . RESULT
TYPE DATE ACHIEVED I DATE SCHEDULED STAFF |RDE B
zom
zJKjua
FJ Is
ttltl ZDIZ9 ID 311
33130
31
^
60161 6ZI63
HK5166
IslPldcl
k^^^i^^^ 21317hf Ul? I2J3I7J7
M
/)]|gl I
nvj jfj
iM'Mr»
7|piEiaiFi ISIPIIEICJ
S^t^^SKH^iy^^
11
md i
-LINE NO
ACTION COMMENTS
,,...„.,,!<
nnnzmzngci Sa
30 3IIJZ 33131135136 31 381
JSBSIWHB 49150 MB< 53154 5b 5615? 5J59I60J6II
63164
DM
-------
2J31
COMPLIANCE DATA SYSTEM CODING SHEET fr ABC4*Jl*utw
° *
I CARD CODE TV) AUCR I CITY CODE I
SOURCE NWIE
I
STREET ADDRESS
RDE 4 I ROE 5
II II isldsi lnhliHI Ish-i I M M I
I II II II I II I |
M M M I I M M
I I M M M M I I
0|0|0|0|04 I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I
luiwirjinirara^HiwmKitMmwp^wrnHiFMoiwjHMraniiftiUQtijMmujtuwiutti
1111111111111111111111111 i 11
*>
o
I I I I I I I I I I I I I iBlPlulxJvl
bliM
leLlslsl I I \ttt\s
Jsjz
11 III IIII11III
3|p|uUvl
iBllM IdolAlxl
1 |
11
II || I I
I I Mill II I I II I
I I III M I MUM III I I I I II I I
I I I loiokl I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I
EMISSION ACTION
OINT NO I NO. I I
OPTIONAL ACTION DESCRIPTION
USED HUH ATPE N
I
ACTION RESULTS
I TYPE I DATE ACHIEVED I DATE SOIEDULED I STAFF ( |RDE 8|
I I M m M I I I M I I I M M I^^Rl^^^^ I I I I I II 1 M I I M I I I I i I
M
I I I I I I M I I I I I I
I I M I M
u 111 1111111
I I I I I I I I I I I I I
1C] ION
\
I I I M M
I I 111 11 I I 111
. ^•LINENO. ' ACTION CpmENTS
lli;6l27jZH|Z9[3n|3l|3Z|J3l34|35|J6l37|38|39j40l4l|4;|43[44|45M6|47|4BI49|50[ai 5^|53[54j5>|5i|S7|5HI59[60j6lj6^j63j64l6!i|46j67l6g|69|70l7H7Z[73l74j75l7f 17/1781
-------
COUHH
CARO CODC
SOURCE
10
AUCR
5. COMPLIANCE DATA SYSTEM CODING SHEET
cur cnof
SOURCE NAIIC
STREET ADDRESS
Ifl.
K
26127
ifl.
23.
30.
JO
55 5S
57
59 62 BUUMI&
BC
TRf
ST
I i
CITY NAME
ZIP I
STATE REGISTRATION
I NEDS xRtr I sic
lo|o|o|o|o|2|AiHhnc|i[riri I I I I I 11
. . POllUTANI 1
I I I I II II I I II kM0M2J9llllNflfclc| I I I II II II II MM
T?. cuiiuiAN! 3 ~r •: r
I I iMltftf&tiril LOADING l*"U!b&$rf# "»'« I *" l/MAA "»»"* | FAC1L1" CAMCITY I
ROE 9
)|o|o|o|o|3t^pm I(6i3l IBM I I I Isla] I»|3|Y|N| I II I II II I \_\_\ JILL I I I I I I I I I I I I I I I I
HO
SOURCE COHNENIS
14 T5 TF
o Q|QHI I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I
oioloioN I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I I 11 I I I I I I I I I I I I I I I I I I I I
H
*•
1i
I I III MM I III I
MRlYl iBlllTl IcIolAllI iBlvJriBl I I
Islz
I I III II III III I
splulUvl N^lYl bbJii IdoNLl
11
II I I
11 III IIIII III I
IIIII11II III I III 1111II11
11
U
. LM
HO
EMISSION POINT COWENTS
[te
ii;
26
17I2B
31
J6
1b
5?I5H
59|»0
66 67|6« 69170 11 f?
74 75 76 77 78
I loio
II I I I I I I I II I I I I I I I I I I I I I I I I I I I I I I I I I I I II I I I I I II I I I I I I I I I II I
EMISSION ACTION
" DINT NO NO
OPTIONAL ACTION DESCRIPTION
USED MITH AIPE OB
ACTION
-------
ST I COUNTY ISOUUCE NUir.fr
?|j|4 IMtTT
¥
119
CARD
AUCR
u
till CODE
«ni€lHlTl I I I IHI
-------
11.3.6 Action Types for PSD/NSR Sources
and Enforcement
A complete list of action types and descriptions for
coding NSR, PSD, and enforcement actions is summarized
below. Those action types marked by an asterisk should be
entered and used in CDS. (see Attachment C) All others
are suggested for regional use, especially where a region
does not currently have equivalent action types. For
mandatory action types (marked by asterisk), if a region
currently uses, and wishes continued use of -an equivalent
action type, such use is acceptable provided the region
supply headquarters with a list equating the HQ action
types with equivalent RO action types (Attention: Doug
Carter, EN-341).
HQ-defined Action Types for PSD/NSR Sources and Enforcement,
Action Type Action Description
SI Application Received by State
S2 Additional Info. Requested by State
S3 Application to State Complete
S4 Preliminary Determination by State
S5 Public Notice by State
S6 Public Hearing by State
S7 Final Determination by State
11-43
-------
S8* Inspection by State
Rl* Application Received by EPA
R2 Additional Info. Requested by EPA
R3* Application to EPA Complete
R4 Preliminary Determination by EPA
R5 Public Notice by EPA
R6 Public Hearing by EPA
R7* Final Determination by EPA
R8* Inspection by EPA
Tl* Offset Determination by State
T2 * BACT Determination by State
T3 LAER Determination by State
T4 RACT Determination by State
T5* Offset Determination by EPA
T6 BACT Determination by EPA
T7 LAER Determination by EPA
T8 RACT Determination by EPA
LI* NOV Issued by State
L2* Civil Action by State
L3* Criminal Action by State
L4 (Reserved)
L5* NOV Issued by EPA
L6* Civil Action by EPA
L7* Criminal Action by EPA
XI* State Order Issued
X2* State Court Decree Issued
X3* Federal Court Decree Issued
X4* State 113d(1) SIP DC Order submtd to EPA
X5* State 113d(3) Replacement DC Order submtd to EPA
X6* State 113d(4) Inn. Technology DC Order submtd to EPA
X7* State 113d(5) Coal Conversion DC Order submtd to EPA
X8* 1st State 119 Smelter Order submtd to EPA
X9* 2nd State 119 Smelter Order submtd to EPA
Yl* EPA 113a(l) SIP Order issued
Y2* EPA 113a{3) Non-SIP Order Issued
Y3* EPA 113a(5) Stop Construction Order Issued
Y4* EPA 113d(1) SIP DC Order Issued
Y5* EPA 113d(3) Replacement DC Order Issued
Y6* EPA 113d(4) Inn. Technology DC Order Issued
Y7* EPA 113d(5) Coal Conversion DC Order Issued
Y8* 1st EPA 119 Smelter Order Issued
Y9* 2nd EPA 119 Smelter Order Issued
Mandatory action types which must be entered and used in CDS.
11-44
-------
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 Capacity Code
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 Procedural Compliance
Card 7
A-43B Penalty Amount
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 State 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-64 Date Scheduled Year/Month
A-65 Date Achieved Year/Month
A-l
Revised: 2/78
-------
REGION
Definition:
REGION is a two position numeric region identifier.
Retrieval
Abbreviation
Card
Type
Card
Colwms
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
REGN
1-8
1-2
2
NUMERIC
LEFT
YES
YES
Valid Values:
01 through 10
See attachment showing the region
locations and the states associated
with each region.
Master file
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
SITE
1-8
3-4
1
4.
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:
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Alabama
Alaska
Arizona
Arkansas
California
Colorado
Connecticut
Delaware
District of Columbia
Florida
Georgia
Hawaii
Idaho
Illinois
Indiana
Iowa
Kansas
Kentucky
Louisiana
Maine
Maryland
Massachusetts
Michigan
Minnesota
Mississippi
Missouri
Montana
Nebraska
Nevada
New Hampshire
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.
Codes are derived from the SAROAD manual.
The County
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-3
4
NUMERIC
LEFT
YES
YES
Valid Values:
All county codes must he present on
the CDS County Code/AQCR Table.
Masterfile
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
A-5
-------
SOURCE :JUMBER
Definition: SOURCE NUMBER is a five digit numeric facility identifier.
Retrieval
Abbreviation
Card
Type
Cora
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
Mast erf He
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
Master file
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 'JUMBER
Definition: ACTION NUMBER is a two digit numeric sequential action identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
ANUM
1-8
17-18
2
NUMERIC
LEFT
YES
NO
Valid Values:
00 through 99
Mast erf He
Record Type
Mas ber file
Position
Mast erf He
Length
2(4-47
17-18
2
Edit Error Messages:
*** ACTION NUMBER MUST BE ZEROS
*** ACTION NUM MUST BE GREATER THAN ZERO
*** = Fatal Error * = Warning Error
Coding Considerations:
Actions should be assigned sequentially starting with 01. When adding
new actions to the data base, code 99; the system will convert
the 99 to the next highest sequential action number for that emission
point. 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. t
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 1-3
Data Element Sheet
Revised: 2/78
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 to do with other
data on the input transaction.
Retrieval N,
Abbreviation
Card
Type 1-8
Card
Columns 80
Data Element
Length ^
Data
Type ALPHA
Justified
Required
on flew Entry YES
Nationally
Controlled YES
Valid Values:
N - New
C = Change
D = Delete
Masterfile
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.
with an action.
Each action comment must be associated
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 'D' deletes one or more records on the CDS data
base. A card type 1 delete will delete all masterfile records for
a given source.
A card type 5 delete will delete a point together with all associ-
ated comments, actions, and action comments. Point 000 cannot be
deleted unless a card type 1 is used for the delete function.
A card type 7 delete will delete an action together with all
associated action comments.
A card type 4, 6, or 8 delete must have a valid line number. One
delete card is needed to delete each comment line number.
No data may be punched in columns 21 through 79 for deletes to
protect the data base against a mispunched delete update code.
A Card 2 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 i
Data
Type NUMERIC
Justified
Required
on New Entry YES
Nationally
Controlled YES
Edit Error Messages:
*** INVALID CARD CODE
*** = Fatal Error
Valid Values:
1 = source record
2 = source record
3 = pollutant record
4 = source comment
6 = emission point comment
7 = action record
8 = action comment
Master file
Record Type
Master file
Position
Master file
Length
* = Warning Error
Coding Considerations:
Card Type 1-3
Data Element Sheet
A-ll
-------
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.
Masterfile
Record Type 20
and the
also
entral
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 COD"
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.
Master file
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 NAME
Definition: SOURCE NAME is a 20 position alphanumeric facility identifier.
Retrieval
A bbrev ia tion
Card.
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
S1JME
1
27-46
20
ALPHANUMERIC
LEFT
YES
NO
Valid Values:
All alphanumeric characters.
Masterfile
Record Type 20
Masterfile
Position 28-47
Masterfile
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
Air Force Base
Asph
Al
Auth
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
Dlv
Foundry (i.e. General
Foundry)
General Motors Corporation
-Fisher Body
Generating
Goodyear Tire & Rubber
Great Lakes Steel-ZUG
Island
Grove land Mine Hanna
Grand Rapids
Hospital
%
Incinerator
Industries
International
Jones & Laugh1in Steel
Light & Power
Lumber
Malleable
Manufacturing
Michigan
Motor
North East (ern)
North West (ern)
Norther Michigan Electrical
Co-op
Name
Under Add Put Plant Name
Ford
Motor
Assembly Div
Spell out—do not abbreviate
Name Under St. Add Put Plant Name
CMC Fisher Body
Genr
Goodyear Tire&Rubber No blanks between "&"
Name Under St. Add Put Plant Name
Great Lakes Zug Island
Steel
Hanna Mining Groveland Mine
GD Rapids
Hosp
Incin
Indst
Intnl
Jones & Laughlin spell out, omit Steel
L&P
Lmbr
Malleb
Mfg
Mich
Mtr
NE
NW
Northern Mich Elec
A-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
Card
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.
Masterfile
Record Type 20
Masterfile
Position 48-67
Masterfile
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 1
Data Element Sheet
A-18
-------
REGIONAL DATA ELEMENT 1
Definition: User supplied.
Retrieval
Abbreviation RDEI
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.
Masterfile
Record Type 2$
Masterfile
Position 140
Masterfile
Length 1
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
Card Type 1
Data Element Sheet
A-19
-------
REGIONAL DATA ELEMENT 2
Definition: User supplied.
Retrieval
Abbreviation RDE2
Card.
Type i
Card.
Columns 68
Data Element
Length i
Data
Type ALPHANUMERIC
Justified
Required
on New Entry NO
Nationally
Controlled 110
Valid Values:
All alphanumeric characters.
Masterfile
Record Type 26
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 i
Card.
Columns 69
Data Element
Length 1
Data
Type ALPHANUMERIC
Justified
Required
on New Entry NO
Nationally
Controlled NO
Edit Error Messages:
*** = Fatal Error
Valid Values:
Masterfile
Record Type 20
Masterfile
Position 142
Masterfile
Length i
* = Warning Error
Coding Considerations:
Card Type 1
Data Element Sheet
A-21
-------
REGIONAL DATA ELEMENT 4
Definition: User supplied.
Retrieval
Abbreviation RDE4
Card
Type i
Columns 70-74
Data Element
Length 5
Data
Type ALPHANUMERIC
Justified
Required
on New Entry HO
Nationally
Controlled NO
Valid Values:
All alphanumeric characters
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
20
143-147
5
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
If there is a need to have a second SIC Code for a facility, this
field could be used since it appears next to the SIC Code on the
Source Data Report. If this data element is used for the SIC Code,
only the first four positions may be used; columns 70-73 must be
numeric and column 74 must be blank.
Card Type 1
Data Element Sheet
A-22
-------
Definition: User supplied.
REGIONAL DATA ELEMENT 5
Retrieval
Abbreviation RDE5
Card
Type 1
Card
Columns 75-79
Data Element
Length 5
Data
Type ALPHANUMERIC
Justified
Required
on New Entry HO
Nationally
Controlled NO
Valid Values:
All alphanumeric characters.
Masterfile
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 UAME 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 20
"Masterfile
Position 68-82
Masterfile
Length 15
* = Warning Error
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
Masterfile
Position
Master file
Length
NUMERIC
* = Warning Error
20
85-39
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
A0-54
15
ALPHANUMERIC
LEFT
NO
NO
Valid Values:
All alphanumeric characters.
Mast erf He
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.
Mast erf He
Record Type 20
Master file
Position 105-108
Master file
Length *
* = 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 the Standard Industrial Class Code. It refers to the
primary product produced or service performed by the facility.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
SICC
2
59-62
4
NUMERIC
LEFT
YES
YES
Valid Values:
All numerics.
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
20
109-112
4
Edit Error Messages:
* SIC SHOULD BE NUMERIC
1
*** = Fatal Error * = Warning Error
Coding Considerations:
Since many retrievals are based on industry categories, it is important
to code this field on a new card code 2. If a secondary SIC code is
needed, Regional Data Element 4 may be used. SIC codes may be obtained
from manufacturing directories or the most recent SIC directory.
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:
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
20
113
1
Edit Error Messages:
* INVALID FEDERAL FACILITY CODE
*** = Fatal Error * = Warning Error
Coding Considerations:
Valid Values:
1 - Source owned or operated by the federal government.
2 - Source owned or operated by the state.
3 - Source owned or operated by the county.
4 - Source owned or operated by the municipality.
5 * Source owned or operated by the district.
Blank/0 - All other facilities not owned or operated by a federal,
state, or local government.
Card Type 2
Data Element Sheet
A-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 YES
Edit Error Messages:
*INVALID AIR PROGRAM CODE
*** = Fatal Error
Valid Values:
0 = SIP Source
1 = federal jurisdiction ~ Active
4 = ESECA
5 = other
6 = PSD
7 = new SOUITCG rsvisw
8 = NESHAPS
9 = NSPS
c = closed/inactive
Masterfile
Record Type 20
Masterfile
Position 115
Masterfile
Length 1
* = l-tarning 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: 2/78
-------
AIR PROGRAM STATUS
Definition: AIR PROGRAM STATUS represents the status of a facility for a given
air program.
Retrieval
Abbreviation ATST
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:
* Invalid Air Program Status
*** = Fatal Error
Valid Values:
P ~~ Planned
C = Under Construction
0 = Operating
D = Demolition
R = Renovation
S = Spraying
Master'fil'e
Record Type 20
Masterfile
Position 180
Masterfile
Length l
* = Warning Error
Coding Considerations:
Card Type 2
Data Element Sheet
A-30A
Revised 2/78
-------
Definition: User supplied.
REGIONAL DATA ELEMENT 6
Retrieval
Abbreviation RDE6
Card
Type 2
Card
Columns 67-76
Data Element
Length 10
Data
Type ALPHA1IUMERIC
Justified
Required
on New Entry NO
Nationally
Controlled N0
Valid Values:
All alphanumeric values.
Masterfile
Record 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
Maeterfile
Record 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
Justified LEFT
Required
.on New Entry N0
Nationally
Controlled YES
Valid Values:
Same as for Pollutant Code. See
pages A- 39 for a list of all
valid codes
Masterfilo
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
Abbreviation
Card
Type
Card
Columns
Data Element
Length
N/A
3
24; 36; 48
1
2Vpe ALPHABETIC
Justified
Required
on Ne>j) Entry
Nationally
Controlled
NO
YES
Valid Values
Blank or '
Masterfile
Record Type
Masterfile
Position
Mas terfi le
Length
Edit Err>or Messages:
* INVALID POLLUTANT DELETE FLAG
* NO DATA TO FOLLOW DELETE FLAG
*** = Fatal Error * = Warning
D1
30
REPEATING
1
Error
Coding Considerations:
A 'D' in the Delete Flag signifies that the data entered for a given
pollutant should be completely eliminated. The pollutant compliance,
emission category, air quality mointenance indicator, air quality
control indicator, and loading are blanked out by the Update program
when a 'D1 is coded next to a pollutant or a Card 3.
Card Type 3
Data Element Sheet
A-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; 37; 49
Data Element
Length 1
Data
Tvpg 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
Master file ^vv^T&C.
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
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
PECT
3
26; 38; 50
1
NUMERIC
Justified
Required
on New Entry
Nationally
Controlled
NO
YES
Valid Values
See page /
all valid
codes .
Masterfilc
Record Type
Masterfile
Position
Mas terfi le
Length
Edit Error Messages:
'* INVALID EMISSION CATEGORY
*** = Fatal Error * = Warning
^-40A for a list of
Emission Category
30
Repeating
1
Error
Coding Considerations:
Card Type 3
Data Element Sheet
A-32D
-------
POLLUTANT AIR QUALITY MAINTENANCE
INDICATOR
Definition: pOLLUTANT AiR QUALITY MAINTENANCE INDICATOR indicates whether or not
the pollutant impacts AQMA standards or not
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Leng th
Data
Type
PAQM
3
27; 39; 51
1
ALPHANUMERIC
Justified
Required
on New Entry
Nationally
Controlled
NO
YES
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 whether or not
a source emits a criteria pollutant for which the AQCR is
non-attainment.
Retrieval PAOC
Abbreviation
Card
Type 3
Card
Columns 28; 40; 52
Data Element
Length 1
Daia
TlfpR ALPHANUMERIC
Justified
Required
on New Entry YES
Nationally
Controlled Ytb
Valid Values:
B - AQCR is attainment for the
given pollutant
N - AQCR is non-attainment for
the given pollutant
Mast erf He
Record Type 30
Masterfile
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
Abbreviation
Card
Type
Card
Columns
Data Element
Lergth
Data
Type
Justified
Required
.on New Entry
Nationa 1 ly
Controlled
LOAD
3
29-33
41-45
53-57
5
NUMERIC
RIGHT
HO
NO
Valid Values:
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
**•* = Fatal Error * = Warning
30
REPEATING
5
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
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
.on Neu Entry_
Nationally
Controlled
FCAP
30
58-64
7
NUMERIC
RIGHT
NO
NO
Valid Values:
Master file
Record Type
MasterfiLe
Position
Mas terfi le
Length
Edit Error Messages:
xx* - 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/incineration rate.
e. For electric utilities, use total megawatt capacity.
f. For coal-fired boiler sources, use Million British Thermal
Units per Hour (MMBTUH) heat input capacity.
Card Type 3
Data Element Sheet
A-32H
-------
REGIONAL DATA 9
Definition:
USER SUPPLIED
Retrieval
Abbreviation «^"
Card
Type
Card
Columns o:)~/J-
Data Element
Length ?
D£ta ALPHANUMERIC
Type
Justified
Required
on New Entry NO
Nationally
Controlled NO
Valid Values:
Masterfile
Record Type 30
Masterfile
Position 23-29
Masterfile 7
Length
Edit Error Messages:
* < x = Fatal Error * = Warning Error
Coding Considerations:
Card Type 3
Data Element Sheet
A-32I
-------
Definition: USER SUPPLIED
REGIONAL DATA ELEMENT 10
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:
Master file
Record Type
Masterfile
Position
Masterfile
Length
Edit Error Messages:
*** = Fatal Error * = Warning
30
30-31
2
Error
Coding Considerations:
Card Type 3
Data Element Sheet
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 Entrij
Nationally
Controlled
NO
NO
Valid Values:
Master file
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
Jus tified
Required
on New Entry
Nationally
Controlled
NO
NO
Valid Values:
Masterfile
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
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
*** LINE 11UMBER MUST
*** = Fatal Error
4, 6, 8
20
1
NUMERIC
YES
YES
Valid Values:
0 through 9
Master file
Record Type 21, 35. 47
Masterfile
Position 21
Masterfile
Length 1
BE NUMERIC
* = Warning Error
Codirig 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 flew Entry HO
Nationally
Controlled NO
Edit Error Messages:
*** = Fatal Error
Valid Values:
All alphanumeric values.
Master file
Record Type 21. 35. 47
Masterfile
Position 22-80
Masterfile
Length 59
* = 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 Source Classification Code which provides
a detailed analysis of the process creating the emission for
this point.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required
on New Entry
Nationally
Controlled
SCC3, SCC6,
sees
5
20-27
8
NUMERIC
LEFT
NO
YES
Valid Values:
Consult the NEDS coding
a list of valid values.
edit accepts blanks or a
tion numeric field.
manual for
The CDS
n 8 posi-
Masterfile
Record Type 34
Master file
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 nnsiti'onq nf srr. ToHe; tmA SCC ft re-
trievess on the first 8 positions of the SCC Code.
For some industries, DSSE has expanded on the values in the NEDS coding
manual; special guidance has been provided for these SCC codes.
SCC8 is at the present a confidential data element. Users must supply
the proper password to obtain SCC8 on output reports. SCC3 and SCC6
are not password protected.
Card Type 5
Data Element Sheet
A-35
Revised 2/78
-------
CAPACITY CODE
Definition: CAPACITY CODE identifies the boiler heat input capacity
in tens of MMBTUH. A boiler with a heat input cap-
ability of 150 million BTU per hour would have "15" in
Capacity Code.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Time
Required. on
New Entry
Justified
Nationally-
Controlled
CAPC
5
28-29
2
Numeric
No
Left
Yes
Valid Values:
00-99
Master file
Record Type
Master file
Position
Master file
Length
34
29-30
2
Edit Error Messages:
Coding Considerations:
This is required for coal-fired boilers for all industries other
than power plants provided that the boiler has a heat input ca-
pacity equal to or greater than 100 MMBTUH.
Users should note that this field was once used for tracking the
NEDS Point Cross Reference (NEXP).
Card Type 5
Data Element Sheet
Revised 2/78
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 CMST
Card
Type 5
Card
Columns 30
Data Element
Length 1
Data
/Tlj .«^
J»P'" MTIMWBTr1
jMstf'/ied
^eqMirec?
on New Entry YES
Mztiottffny
Controlled YES
Valid Values:
0 through 9
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
34
31
1
Edit Error Messages:
*** INVALID COMPLIANCE STATUS
*** = Fatal Error * = Warning Error
Coding Considerations:
Must be coded on the point
COMPLIANCE STATUS CODES:
; may be coded on the other emission points.
1
2
3
4
5
6
7
8
9
Unknown
Not in compliance
In compliance by source test
In compliance by inspection
In compliance by certification
In compliance with increments of ptogress
Not in compliance with increments of progress
Unknown compliance with increments of progress
No applicable state regulation
In compliance - closed down
With Regulation
With Schedule
The Compliance Status on Point 000 (entire source) should reflect the worst
case compliance of any process within the source. The Compliance Status on
all other points should reflect the worst case compliance of that particular
point.
Card Type 5
Data Element Sheet
A-37
revised: 2/78
-------
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
Abbrei>iation SIPC
Card
Tupe 5
Card
Columns 31
Data Klement
Length 1
Data
Type NUMERIC
Justified
Required
on New Entry N0
Nationally
Controlled YES
Edit Error Messages:
* INVALID SIP CODE
*** = Fatal Error
Valid Values:
Blank, 0 through 8.
Master file
Record Type 34
Masterfile
Position 32
Masterfile
Length 1
* = Warning Error
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
Master file
Position 33-34
Masterfile
Length 2
•
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
BZ - Benzene
N2
OD
OT
PT
S2
TS
VE
VC
- N02
- Odors
- Other
- Particulate
- SO,
Matter
Total Reduced Sulfur
Visible Emissions
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 N0
Nationally
Controlled NO
Edit Error Messages:
*** = Fatal Error
Valid Values:
All alphanumeric values.
Master file
Record Type 34
Masterfile
Position 35-49
Masterfile
Length 15
* = 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
Justified
Required
on New Entry
Nationally
Controlled
ECAT
5
49
1
NUMERIC
YES
YES
Valid Values:
0 = unknown
1 = Less than
2 = 100-1000 I
3 = over 1000
4 = Less than
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
100
PY
TPY
25
34
50
1
TPY potential
potential
potential
TPY potential
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
Revised: 2/78
-------
PROrF.SS DF.Sr.KTPTTOM
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 flew 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 34
Masterfile
Position 76-78
Masterfile
Length 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 RDS7
Card
Type 5
Card
Columns 78
Data Element
Length 1
Data
Type ALPHANUMERIC
Justified
Required
on New Entry N0
Nationally
Controlled NQ
Edit Error Messages:
*** = Fatal Error
Valid Values:
All alphanumeric values.
Master file
Record Type 34
Master file
Position 79
Master file
Length 1
* = Warning Error
Coding Considerations:
Card Typo 5
Data Element Sheet
A-43
-------
PROCEDURAL COMPLIANCE
Definition:
PROCEDURAL COMPLIANCE should be used for all NSR, PSD, NSPS,
NESHAPS, and SIP facilities under construction or subject to
performance tests, continuous monitors, and other procedural
requirements. This field indicates the compliance status of
a facility with respect to all applicable procedural require-
ments. Use CMST to indicate the compliance of an operating
facility.
Retrieval
Abbreviation
Card
Time
Card
Columns
Data Element
Length
Data
Type
Required on
New Entry
Justified
Nationally
Controlled
CMS 2
5
79
1
Alphanumeric
No
Yes
Valid Values:
Master file
Record Type
Master file
Position
Master file
Length
Edit Error Messages:
Coding Considerations:
Code Value
A Unknown compliance with procedural requirements.
B In violation of procedural requirements.
C In compliance with procedural requirements.
8 No applicable regulation or procedural requirement.
Blank No applicable regulation or procedural requirement.
Card Type 5
Data Element Sheet
revised: 2/78
A-43A
-------
PENALTY AMOUNT
Definition: PENALTY AMOUNT indicates the non-compliance penalty im-
posed on a facility.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Required. on
Hew Entry
Justified
Nationally -
Controlled
PLTY
7
46-52
7
Numeric
No
Right
No
Valid "Values:
All numeric
Master file
Record Type
Master file
Position
Master file
Length
values
46
93-99
7
Edit Error Messages:
Coding Considerations:
This field should be used in conjunction with the following action types:
Z3 State non-compliance penalty.
Z4 State civil penalty.
Z5 Federal non-compliance penalty.
Z6 Federal civil penalty.
Dollar amounts must be right justified; they should be rounded to the
nearest $100. No commas, dollar signs, or periods must be used.
Please refer to DSSE guidance documentation for additional details.
Card Type 7
Data Element Sheet
revised: 2/78
A-43B
-------
ACTIO:i TYPE
Definition:
ACTION TYPE is a two position alphanumeric action description
identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
ATPE
7
53-54
2
T " ALPHANUMERIC
Justified
Required
on Pew Entry
Nationally
Controlled
LEFT
YES
YES
Valid Values:
Must be on Action Table controlled
by national DEC.
Action Type 00 indicates an action
type which is user defined.
ifasterfile
Record Type 46
Masterfile
Position 21-22
Masterfile
Length 2
Edit Error Messages:
*** INVALID ACTION TYPE
*** ACTION TYPE REQUIRED ON NEW ENTRY
*** = Fatal Error * = Warning Error
Coding Considerations:
Please call the national 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".
Certain action types are required input to CDS. Please consult the
current FY air enforcement program plans and the most recent DSSE
guidance material for the most current requirements.
To obtain the most current version of a region's action .types,
please follow the procedures described on page 10-7 of this manual.
Card Type 1
Data Element Sheet
A-44
revised 3/78
-------
DATE ACHIEVED
Definition: DATE 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 acceptable. If
numeric other than zero, day must
be between 01 and 31, month must be
between 01 and 12, and year must be
greater than 60.
Masterfile
Record Type 46
foster file
Position 29-34
Masterfile
Length 6
- OUTPUT ZEROS
* = Warning Error
Coding Considerations:
If an error is encountered in the date field, the bad month 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
Mast erf He
Position
Master file
Length
acceptable.
be between 01
be between 01
st be greater
46
23-28
6
Edit Error Messages:
* INVALID DATE SCHED - OUTPUT ZEROS
* DATE SCHED REQUIRED ON HEW 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
Masterfile
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
70-71
2
NUMERIC
LEFT
NO
YES
Valid Values:
May be a blank; if not a blank, it
must be a two digit numeric field.
Must exist on the RESULTS-CODE
Table controlled by the national
DEC.
Master file
Record Type 46
Ifasterfile
Position 55-56
Masterfile
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
it indicates whether or not the action was carried out, or whether
another action should be referred to.
Please call the national DEC to add, change, or delete entries on the
Results-Code Table for your region.
Card Typs 7
Data Element Sheet
A-48
-------
Definition: User supplied.
REGIONAL DATA ELEMENT 8
Retrieval
Abbreviation
Card
RDE 8
7
Card
Columns
Data Element
72 - 73
2
Data
Justified
Required
on New Entry
ALPHANUMERIC
LEFT
NO
Nationally
Controlled
NO
Edit Error Messages:
*** = Fatal Error
Valid Values:
Masterfile
Record Typje_
Masierfile
Position
MasterfiTe
Length__
46
57 - 58
2
= 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
Required
on New Entry
Nationally
Controlled
Edit Error Messages:
*** -- Fatal Error
ADES
7
20-34
15
ALPHANUMERIC
LEFT
YES
Valid Values:
Please call the national DBC to add
or change action descriptions on
the regional Action Table.
Masterfile
Record Type 46
Masterfile 107-156
Position 40-54
Masterfile 50
Length 15
* = Horning 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
revised 5/76
-------
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
TUP*- ALPHABETIC
Justified
Required
on New Entry
Nationally
Con-trolled YES
Valid Values:
Appendix B contains a list
county names valid for each
state/county combination.
Maeterfile
Record Type 20
Masterfile
Position 163-179
Masterfile
Length 1 7
of
region/
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
This field is generated; it cannot be coded. The national
DEC maintains a table of COUNTY CODE/COUNTY NAME combinations.
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 flew Entry
Nationally
Controlled
Valid Values:
Master file
Record Type
Master file
Position
Master file
Length
20
134-139
6
Edit Error Messages:
*** = Fatal Error * = Warning Error
Coding Considerations:
This date is in year, month, day format on the CDS Masterfile. It
should be retrieved in month, day, year format on CDS RETRIEVAL
REQUEST FORMS.
Data Element Sheet
A-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
fto - Action
47 = Action comment
Masterfile
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
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
additions or changes to this table.
Mast erf He
Record Type ^6
Masterfile
Position 63-77
Masterfile
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
DEC.
Master file
Record Type 46
Mast erf He
Position 78-92
Master file
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 El&nent
Length
Data
Tyve ALPHANUMERIC
Justified
Required
on New Entry
Nationally
Controlled YES
Edit Error Messages:
*** = Fatal Error
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
Masterfile
Position 119-133
Masterfile
Lenjth 15
* = 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
-------
STATE1. ARRRFUTATTCIM
Definition: STATE ABBREVIATION is a two position alphabetic state code
used by the U. S. Post Office. It is generated for each
facility by CDS. It is useful for retrieval processing.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Required on
New Entry
Justified
Nationally-
Controlled
STAB
N/A
N/A
2
Alphanumeric
N/A
Yes
Valid Values:
Master file
Record Type
Master file
Position
Master file
Length
20
83-84
2
Edit Error Messages:
Coding Considerations:
AL - Alabama KY -
AK - Alaska LA -
AZ - Arizona ME -
AR - Arkansas MD -
CA - California MA -
CO - Colorado MI -
CT - Connecticut MN -
DE - Delaware MS -
DC - District of MO -
Columbia MT -
FL - Florida NE -
GA - Georgia NV -
HI - Hawaii NH -
ID - Idaho NJ -
IL - Illinois NM -
IN - Indiana NY -
IA - Iowa NC -
KS - Kansas ND -
Kentucky OH
Louisiana OK
Maine OR
Maryland PA
Massachusetts PR
Michigan Rl
Minnesota SC
Mississippi . SD
Missouri TN
Montana TX
Nebraska UT
Nevada VT
New Hampshire VA
New Jersey WA
New Mexico WV
New York wi
North Carolina WY
North Dakota' AS
Card Type
Data Element Sheet
Ohio
Oklahoma
Oregon
Pennsylvania
Puerto Rico
Rhode Island
South Carolina
South Dakota
Tennessee
Texas
Utah
Vermont
Virginia
Washington
West Virginia
Wisconsin
Wyoming
American Samoa
GU - Guam
VI - Virgin
Islands
TT - Trust
Territories
revised: 2/78
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
Type 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
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 DEC. It is not present
on any master file record. A change to CMST will result in a change to the
description.
Retrieval
Abbreviation CMOS
Card
Type
Card
Columns
Data Element
Length 20
Data
Tung Alphanumeric
Justified Left
Required
on New Entry No
Nationally
Controlled Yes
Edit Error Messages:
*** = Fatal Error
Valid Values: See Below
Masterfile
Record Type
Master file
Position
Mas terj'i le
Length
* = Warning Error
Coding Considerations:
CMST Value CMOS description
0 Compl Status unknown
1 Not in compl - No Schd
2 In Compl - Source test
3 In Compl - Inspection
A In Compl - Certification
5 In Compl w Schedule
6 Not in Compl w Schd
7 Unknown Compl w Schd
8 No Applic State Reg
9 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 CODE DESCRIPTION
Definition: Sip Code Description is the English language description of Sip Code
(SIPCj^It is generated by the computer based on the value of SIPC. This des-
cription is controlled by the national DEC. It is not present on the master file.
The description will automatically change when SIPC is changed.
Retrieval
Abbreviation 3 IDS
Card
Type
Card
Columns — .
Data Element
Length 20
Data
Type Alphanumeric
Justified Left
Required
on Neu Entry No
Nationally
Controlled Yes
Edit Error Messages:
*** = Fatal Error
Valid Values: See Below
Piaster file
Record Type
Masterfile
Position
Masterfile
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 RSTD
Card
Type
Card
Columns
Data Element
Length 15
Data
Type Alphanumeric
Justified Left
Required
on New Entry No
Nationally
Controlled Yes
Edit Error Messages:
*** = Fatal Error
Valid Values:
The Results Code (STAC) must exist
on the RESULTS CODE TABLE controlled
by the national DBC.
Masterfile
Record Type 46
Masterfile
Position 157
Masterfile
Length 15
•
* = Warning Error
Coding Considerations:
Card Type
Data Element 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
Columns '
Data Element
Length
D£** ALPHANUMERIC
Justified
Required /A
on New Entry
Nationally ygs
Controlled
Valid Values:
Masker file
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 Retrieval Abbreviation
Old Comp Status - 1st Quarter
2nd
3rd
4th
5th
6th
7th
8th
OCS1
OCS2
OCS3
OCS4
OCS5
OCS6
OCS7
OCS8
On October 1976, the Compliance Status found on each emission point record
was placed in OCS1. During each subsequent quarter, the current compliance
status is stored in OCS1, and all previous quarterly compliance statuses are
moved into the next higher DCS 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 Type System.
Data Element Sheet
A-62
revised 3/78
-------
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
A9-108
60
Error
Coding Considerations:
Card Type
Data Element Sheet
A-63
-------
DATE SCHEDULED YEAR/MONTH
Definition: DATE SCHEDULED YEAR/MONTH allows users to select and sort
reports by the scheduled month of an action. With this
data element, users can produce Milestone Reports or Quick
Look Subtotals for actions during a given month.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Required. on
New Entm
Justified
Nationally
Controlled
DSYN
N/A
N/A
4
Numeric
N/A
N/A
No
Valid Values:
Master file
Record Tyve
Master file
Position
Master file
Length
46
23-26
4
Edit Error Messages:
Coding Considerations:
This data element consists of the year (two digits) and month (two digits)
of the Date Scheduled. A Milestone Report totaling federal enforcement
actions by month for the third quarter will look like this:
ACTION TYPE
114 LETTER SENT
EPA INSPECTION
EPA VE EVALUATION
EPA CIV/CRIM ACTION
REGIONAL ADES TOTALS
REGION
TOTAL
46
109
190
26
371
DAYM
7804
12
42
48
7
DAYM
7805
18
39
62
15
134
DAYM
7806
16
28
80
4
128
Card Type
Data Element Sheet
A-64
revised: 2/78
-------
DATE ACHIEVED YEAR/MONTH
Definition: DATE ACHIEVED YEAR/MONTH allows users to select and sort
reports by the achieved month of an action. With this
date element, users can produce Milestone Reports or
Quick Look Subtotals for actions during a given month.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Required on
New Entry
Justified
Nationaily~_
Controlled
DAYM
N/A
N/A
4
Numeric
N/A
N/A
No
Valid Values:
Master file
Record Type
Master file
Position
Master file
Length
46
29-32
4
Edit Error Messages:
Coding Considerations:
This data element consists of the year (two digits) and month (two digits)
of the Date Scheduled and the Date Achieved. A Milestone Report totaling
federal enforcement actions by month for the third quarter will look like
this:
ACTION TYPE
114 LETTER SENT
EPA INSPECTION
EPA VE EVALUATION
EPA CIV/CRIM ACTION
REGIONAL ADES TOTALS
REGION
TOTAL
46
109
190
26
371
DAYM
7804
12
42
48
7
109
DAYM
7805
18
39
62
15
134
DAYM
7806
16
28
80
4
128
Card Type
Data Element Sheet
A-65
revised: 2/78
-------
APPENDIX B
CONTACT LIST
OF
CDS USERS
-------
Contact List of CDS Users
National Data Bank Coordinator
Franklin Smith
202-755-0103 FTS 755-0103
Region I - Boston
Frank Ciavattier
Paula C. Matos
617-223-5610
Region II - New York
Ken Eng
Jerry DeGaetano
212-264-4726
FTS 223-5610
FTS 264-4726
Region III - Philadelphia
Van Smith
215-597-4779
Connie Carr
215-597-9387 FTS 597-9387
Region IV - Atlanta
Vince Hellwig
404-881-4298 FTS 285-5291
Randall Davis, Mgmt., Div.
Barry Gilbert
Region V - Chicago
Eric Cohen
312-353-2090
Region VI - Dallas
Bob Hannesschlager
Mary Kay Marusak
214-749
FTS 353-8213
FTS 749-7675
U.S. Environmental Protection Agency
Division of Stationary Source
Enforcement EN-341
401 M Street S.W.
Washington, D.C. 20460
Enforcement Division
U.S. Environmental Protection Agency
J.F.K. Federal Building
Boston, Massachusetts 02203
Enforcement Division
U.S. Environmental Protection Agency
26 Federal Plaza
New York, New York 10007
Enforcement Division
U.S. Environmental Protection Agency
Curtis Building
6th and Walnut
Philadelphia, Pennsylvania 19106
Enforcement Division
U.S. Environmental Protection Agency
345 Courtland St.
Atlanta, Georgia 30308
Enforcement Division
U.S. Environmental Protection Agency
230 South Dearborn Street
Chicago, Illinois 60604
Enforcement Division
U.S. Environmental Protection Agency
1201 Elm St.
Dallas, Texas 75270
B-l
-------
Region VII - Kansas City
Patsv Burrell
Melinda Hall
816-374-2576
Enforcement Division
U.S. Environmental Protection Aqency
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 Aqency
1200 6th Avenue
Seattle, Washington 98101
TRC - The Research Corporation
of New England
Scott Shanks
Geza Serenyi
Sue Graves
JoAnn Hewett
Mike Bragg
Linda Tobiasz
Ann Killeen
125 Silas Deane Highway
Wethersfield, Connecticut 06109
B-2
-------
TECHNICAL REPORT DATA
(Please read Instructions on the reverse before completing)
1. REPORT NO
EPA 340/1-78-003
2.
3 RECIPIENT'S ACCESSION NO.
4. TITLE AND SUBTITLE
Compliance Data System User's Guide
5. REPORT DATE
March 1978
6. PERFORMING ORGANIZATION CODE
7 AUTHOR(S)
Mr. Geza Serenyi
8. PERFORMING ORGANIZATION REPORT NO.
9 PERFORMING ORGANIZATION NAME AND ADDRESS
The Research Corporation of New England
125 Silas Deane Highway
Wethersfield, CT 06109
10 PROGRAM ELEMENT NO
11. CONTRACT/GRANT NO
68-01-4145
12. SPONSORING AGENCY NAME AND ADDRESS
Division of Stationary Source Enforcement
Office of Enforcement
U.S. Environmental Protection Agency
Washington, D.C. 20460
13 TYPE OF REPORT AND PERIOD COVERED
14 SPONSORING AGENCY CODE
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 March 1978, which should be discarded.
The guide is organized to be used effectively by several groups of potential readers:
Managers and others wishing a basic description of CDS should read Sections 2 and 3,
Management Overview and System Applications. Current Users who generally understand
CDS will wish to skip to specific sections of interest, particularly Sections 7 and 9,
Edit Processing and Retrieval Processing, which reflect recent changes. New Users
may wish to read the text in its entirety, at least through Section 9 to obtain a
working knowledge of CDS. Those Preparing Input Data should read Section 6, Data In-
put Preparation.
17.
KEY WORDS AND DOCUMENT ANALYSIS
DESCRIPTORS
b IDENTIFIERS/OPEN ENDED TERMS
c. COSATI F leld/Ctoup
Air Pollution Facilities (Sources)
Compliance Status
Enforcement Actions
Surveillance Actions
13 B
IB DISTRIBUTION STATEMENT
Release Unlimited
19 SECURITY CLASS (This Report)
Unclassified
21 NO. OF PAGES
301
20 SECURITY CLASS (Thapage)
Unclassified
22. PRICE
EPA Form 2220-1 (Rev. 4-77) PREVIOUS COITION is OBSOLETE
•U.S. GOVERNMENT PRINTING OFFICE 197B 0-720-335/6089
-------
|