United States
Environmental Protection
Agency
Office of Air Quality
Planning and Standards
Washington DC 20460
EPA-340/1 -87-003
May 1987
Stationary Source Compliance Series
CEMSS*
User's
^Continuous Emission
Monitoring Systems
Subset
-------
EPA 340/1-87-003
Continuous Emission Monitoring
System Subset
User's Guide
U.S. ENVIRONMENTAL PROTECTION AGENCY
. Stationary Source Compliance Division
Office of Air Quality Planning and Standards
Washington DC 20460
May 1987
-------
UNITED STATES ENVIRONMENTAL PROTECTION AGENCY
WASHINGTON, D.C. 20460.
OFFICE OF
AIR AND RADIATION
MEMORANDUM
SUBJECT: Continuous Emission Monitoring System Subset
(CEMSS) Guidance
FROM: John Rasnic,
Compliance Monitor ng Branch
Stationary Source Compliance Division
TO: Regional CDS Managers
Regional CEMS Coordinators
In April we revised the CEMSS and sent the new User’s
Guide to all Regional CDS managers and CEMS coordinators.
Because reviewers agreed that the changes represent major
improvement, the revisions should be considered final with an
implementation date of July 31, 1987.
The revisions respond to suggestions made at the CEMS
technical forum in January, and input received when prelimi-
nary system revisions were tested. The major deficiencies
addressed are: inappropriate focus on monitor rather than
compliance information, unclear description of several data
elements, no specification of minimum national reporting
requirements, and weak reporting capabilities. Corrections
are briefly described below:
STRONGER FOCUS ON COMPLIANCE RATHER THAW MONITOR INFORMATION
The most important change in the CEMSS is the partial
incorporation of the Region V conventions, specifically, use
of the ‘channel’ field to separate information concerning
different pollutants, and to distinguish between compliance
and comment information. We believe that this change will
have minimal impact on data input and maintenance while
making it much easier for users to query the database for
nationwide data for any source—type and/or pollutant (see
attached examples of the use of the ‘channel’ convention)
Another Region V convention, identification of CEMSS data by
1
-------
—2 -
using special point numbers, was not incorporated as a
requirement for two reasons. One, the system can work as
desired without this convention; and two, several users found
the convention conflicted with agreements they had reached
with State and local agencies concerning CEMSS data input.
The Region .V point convention facilitates description of
the emissions points covered by a single EER. Those not
using the Region V point convention will need to note via a
comment (on card 60) when data for multiple units are
combined in one EER.
IMPROVED DOCUMENTATION OF DATA ELEMENTS AND REQUIREMENTS
Other important improvements include clear definition of
data elements and specification of required data elements. A
brief description of required elements follows. For details
see the User Guide and the attached list of mandatory data
elements:
Card type 10 should only be submitted the first time ‘a
source is entered into CEMSS. The data elements which must
be entered on this card are source ID and update code.
Card types 70, 71 and 72 are mandatory. The data
elements which must be maintained on these card types are
source ID, action number, action type, date achieved, update
code, emission point, report quarter, channel, periods code,
operating time, reasons values, number of incidents of excess
emissions and monitor downtime.
‘For the optional card types, i.e., 51, 52, 60,, and 80,
the data elements which must be maintained to make the
information useful are source ID, emission point, channel,
update code, quarter, and line number.
REPORTING CAPABILITIES
The upgrade ‘also includes a Statistics (Stat) Report
which reports on monitor downtime normalized to total
operating time. However, the Stat Rep’ort does not yet
display data from a number of user selected sources in the
most effective fashion. It is recommended therefore, that the
Stat Report be used on only one source at a time. Your
suggestions on improving the Stat Report are requested.
MISCELLANEOUS
In response to multiple requests, we have agreed to
reload the existing CEMSS data into the new ‘channel’ format.
This will be done on a State by State basis subject to veto
by the Regional CEMS coordinator. ,The reload will make about
50—60 percent of the EER data meaningful and useful to all
users. The data which had been entered.more than once (e.g.
11
-------
—3—
for several units reporting in a single EER), and the data
ich has an indeterminate time period (‘P’ in. the time
riod field), probably are not meaningful now and will not
be meaningful after the upgrade implementation. Bob Bowers
at TRC will beavailable for consultation on procedures for
saving this data; but it will be up to each Region to support
conversion of this historic data. We do not encourage
spending significant resources on correcting historic data.
The EER Review and Use Guidance of October, 1984, allows
for engineering judgement of how much process or control
equipment failure time is “unacceptable.” Accordingly, the
revised CEMSS allows for evaluation of “unacceptable”
downtime “reasons.” While the technical forum reviewers
requested removal of these fields, we have since been asked
to maintain them for use in coding Da source reports. We
have therefore retained the fields while noting, both in the
data dictionary and on the coding forms, that use of these
fields is optional.
Reviewers noted that the User’s Guide is oriented to the
Wylbur environment rather than the TSO environment, even
though the Agency is moving to TSO in fiscal year 1988.
Rather than addressing this concern under the CEMSS
development project, SSCD is developing TSO routines for
CEMSS as a part of the larger process of preparing TSO
utines for the entire CDS user community. You will receive
structions for use of CEMSS in a TSO environment as part of
that larger task.
In summary, the upgraded CEMSS responds to many of your
requests while remaining, as-designed, fundamentally a system
to track EE.R data not used directly for determining
compliance.
Please continue to refer questions and comments on CEMSS
to Mark Antell at (FTS) 382—2878 or E—Mail Box 6266.
cc: F. Smith, National CDS Manager
L. Paley, National CEMS Coordinator
Attachments: 1. CEMSS Required Data Elements
2. Sample Retrievals Using the ‘Channel’
Convention
3. CEMS Coordinators (list)
111
-------
cn s PEQJIRED _ MEN]B 3/87
(re uite tds)
A ruxtter of fi 1 is nust be t1y cucki to ter any data £i u an ss i iai rqx rt (E R) to
ti QntinDJs i ia bütarii Syst t & et ( ). se fi 1 c1 are:
RD FIELD S WL CDEU W FIELD IS REQ ED
10 — This c zd is a 1y i iz to or c 1ete a sa to :
10 Sa ID 1—13 Defii saz e.
Ps icn REX 1—2
State 3—4
C zity QUY 5-8
Swrce ximb 9-13
10 t1 x1ate O e 60— Update irdicator.
70- O p1 e history rd:
70 Scurce ID 1—13 See a e.
70 ktia i No# Nr. }1 18—21 Irdi t cxiip1iar history.
70 ctiai ¶L ’pe 57—58
70 I te diieve D 59-63
70 U x ate —80— See a}x,ve.
71 — E ess eiiissia i r s s rd:
71 Sc,.1r ID 1—13 See alx,ve.
71 Hnissia t Ibint PIN) 14—17
71 Qiarter PQIR 18—21 Irxlic’at tbe perirx hith t1 EER ers.
71 thanrel CHPJN 24—26 See
71 E .ricx s Qxè !I 1E —27— I uirE to interpret reescz va1i. .
71 Cperatirx Thte OPER 28—33 I ir 1 to rxintelize EER data to % q:eratirg
tine. t fau1ts to 1e quarter.
71 I asa Ls 34—75 Captzzes rep rte E va1t s. t fau1t.s to 0.
Start/shut SrAR 34-39 Startiip/shu jn.
C eanin 40-45 Cnin/soc b1cx irg.
TJr iJ ri 46—51 tri xss enissia
o1 Fail !QPT 52-57 Ontrol s ii ent failure.
Qtrl Fail tk n FQRJ 58-63 Cptiaal &igii ±z ji.x e it.
Process Pri±s H )C 64—69 Process prthlais.
s Prths U n N. 70—75 Cpticm]. &giresrir jiñ it.
71 Nunb Ircidaits EELN 76—78 Nu er of anissiai ircij1Blts.
71 Up te —80- See a ,E.
.i V
-------
S 1 JIPED Th EEE IS — 3/87
(r ds -
RD FlEW S’ L CDtIIRS V f FLEW IS REQJIRED
72 — F s i i n
72 Sa ID
72 i icn mint
72 Q.iarter
72 tharr 1
72 Ièascrs
Ft 1 Px s
Oth PL . _
itar 1f __
Na 1f _
OU ] ‘ _
72 Rmber Ircide*s
-- U ate
r s ( tira ) ard mz,ithr th iti e ieas cmd:
1—13 See alx,ve.
PIN) 14—17
R 1R 18—21
24—26
27-68
27—32 Ft ]. i ir aai iai.
E r 33—38 Ot1 c i
1C Q 39—44 I!thitar n 1f. car ee naiit d i.
45-50 O ip nt e nu itar th .
I1 51—56 libtaticn es i itor thin.
57-62 tkila n c ” nrnitar thin.
?t OP 63-68 O u e mnitar thin.
69—71 Nuirber ir i z*s na itar jn.
-80- See a .
V
-------
S R Jfl _ EEEMENIS — 3/87
ia 1 cards)
FlEW
S L
ff FlEW IS RET JIRED
60 — This curti ts card is r
60 Sa ’ ID
60 U ate
80 — This antExts card is rx,t
80 Sc,.irce ID
80 Ehdssiai rtint
80 Quarter QIR
80 tharirel (BAN
80 Lire No#
80 U x ate
1—13
14—17
18—21
24—26
—27—
-80-
If nitte , it ni.Et have:
See a .
I,
I,
I,
Q o ica1 m t
See ab e.
51 — This iia iithr c3escriptia card is rr t
51 Scurce ID 1—13
51 Ekuissim Int 14—17
51 thalTel 24—26
5]. tJ x te -80—
recpired. If suk nitta1, it iiust have:
See a .
t fir enissim pint.
fb data jpe.
Update flag.
52 — This re u1aticn S 1ptim card is r .rB xix . If atinittal,
52 Scurce ID 1—13 See a ve.
52 Eknissia lnt PIN 14—17
52 thanrel ( N 24—26
52 tJ x3ate —80—
it in. t have:
re jiired. If. sulznittal, it uLet have:
1—13 See a e.
-80- ‘I
vi
-------
SAMPLE RETRIEVALS USING THE ‘CHANNEL’ CONVENTION
EXAMPLE 1
QUICK LOOK - CONTROL FAILURE CAUSED EXCESS EMISSIONS
01 00 502 EXCESS EMISSIONS CUASED BY CONTROL FAILURE
1OAPSTA
10 APST A 0
10 CHAN M 299
2OQL
40 SNME RQTR EQPT PEQP
EXAMPLE 2
MILESTONE REPORT -. NSPS COAL FIRED POWER PLANTS WITH S02 CEMS
01 00 NSPS COAL FIRED POWER PLANTS WITH S02 CEMS
1OAPCD M 9
1OAPSTAO
1OAPSTA
10 SCC6 A 101001
10 SCC6 A 101002
10 SCC6 A 101003
10 CHAN G 200
10 CHAN L 299
20 MS
50 STTE CLAS Al A2 B UK
v i •j
-------
REGIONAL CEMS COORDINATORS;
REGION .01 TOM ELTER
REGION 02, DENNIS SANTELLA
REGION 03 GLEN HANSEN
REGION 04 MARX ARNENTROUT
REGION 05 PAT MCCOY
REGION 06 STAN SPRUIELL
REGION 07 TONY WAYNE
REGION 08 DENNIS WOLJAN
REGION 09 MARC Sfl S
REGION 10 MARK HOOPER
viii
-------
TABLE OF CONTENTS
SECTION PAGE
1.0 INTRODUCTION
2.0 MAJ1AG JT
System Purposes
System.Capabi]itjeg
SystemFunctions
2.1
2.2
2.3
3.0 sysm.i VERVIE ..
3.1 Edit Program
3.1.1 Input Data Processed by the C 4SS
3.1.2 Edits Performed by the cE24SS
3.1.3 Edit Error Messages
3.1.4 C 24SSMod File
3.2 Update Program
3.2.1 Update Actions to the CE2 SS
3.2.2 Update Cycle Steps
3.2.3 Update Report Messages . .
.3.2.4 The c 4SS Masterfi].e . . . •
3.2.5 CE24SS Retrieval Masterfile
3.3 Retrieval Program
3.3.1 Retrieval Steps . . . . . .
4.0 DATA SUBMISSION PROCEDURES . .
1—i
2—1
2—2
2—3
2—8
3—1
3—i
3—2
3—3
3—6
3—6
3—7
3—8
3—8
3—10
3—10
3—il
3—13
3—24
41
5.0
6.0
DATAINPUTPREpARATI O N
5.1
General
5.2
Excess nissions Report
5—1
5—1
5.3
Adding New Records to the C 4SS Masterfile
5—11
5.3.1
Adding New CD4 Source That Does Not Exist
. .
in
. .
CDS
5—11
5.3.2
Adding New C 1 Source That Already Exists
in
CDS
5—11
5.3.3
Card Types 5—1 and 5—2
.
5.3.4
Card Types 6—0
5—14
5.3.5
Card Types 7—0
5—14
5.3.6
Card Types 7—1
5.3.7
Card Types 7—2
5—29
5.3.8
Card Types 8—0
5.4
Changing Data on the D SS Masterfile
5.5
WILBUR Interactive Data Entry Technique
.
5—31
5_33
6.1
EDIT PROCESSING . . . . . . . . . . . •
Edit Program Usage
6—1
6.2
Edit Error Messages . .
6.3
fl4SS Edit Reports
6.4
Edit Job Control Language
6—5
ix
-------
TABLE OF CONTENTS (cont)
SECTION PAGE
7.0 UPDATE PROCESSING 7-:
7.1 Update Program Description 7—1
7.2 . Update Scheduling . 7—1
7.3 Update Report . 7—2
7.4 Update Report Messages • 72
8.0 RETRIEVALPROCESSING 8 -1
8.1. . Reports Available from the Retrieval 8—2
8.1.1 CENSS Detail Report .... 8—3
8.1.2 Quick Look Report 8—3
8.1.3 Double—Spaced Quick Look Report 8—8
8.1.4 Two—Line Quick Look Report 8—8
8.1.5 Source Data Report .“ 8—8
8.1.6 Milestone Report . . . 8—11
8.1.7 Single—Spaced Milestone Report 8—15
8.1.8 Three Element Milestone Report 8—15
8.1.9 E24SS Statistical Report 8—15
8.1.10 Questionnaire Report 8—21
8.2 Checklist for Request Submission 8—21
8.3 Preparing Retrieval Selection Cards 8—24
8.4 Job Control Language for Using Retrieval Program . 8-34
8.5 Retrieval Edits Performed by System 8—34
8.6 WYLBUR Interactive Retrieval Technique . 8—39
APPENDICES
A CENSS Data Element Dictionary
B 1ORANDUM: GUIDANCE CONCERNING EPA’ S USE OF CONTINUOUS
ENISSION MONITORING DATA; KATHLEEN H.. BENNETT. AUGUST 12,
1982
C Final Technical Guidance on the Review and Use of
Excess nission Reports
D Suggested Continuous flnission Monitoring Excess
niss ions Report Format
E EPA Regional CENS Contacts
F Changes Incorporated in CD S Under the CENSS Upgrade Task
G Continuous ission Monitoring System Subset Coding
Conventions as Developed for U.S. EPA Region V
x
-------
LIST OF, FIGURES
PAGE
FIGURE
3—1
3—2
3—3
3—4
51
5—2
5—3
5—4
5—5
5—6
5—7
Edit Flow Chart
3—5
Update Flow Chart
CD4SS Masterfile Hierarchy
•
.
3—12
Retrieval Flow Chart
3—26
Sample Coding Sheet
5-2
EER Submitted for, First Quarter of 1981
5—4
EER’That Shows No Specific.Magnitude or Excesses
5—9
EER With No Corrective Action Information
.
5—10
Reviewers Checklist for an EER
5—12
CEMS Coding Sheet With New Data
5-28
CEMS Coding Sheet With Change Transactions
. .
5-35
5—8
WILBUR Interactive Data Entry
5—36.
6—1
Sample Edit Report
6—6
6-2
CEMSS Edit Job Control
.
6-7
6-3
Using CDISEDIT with Dummy Mode
6—7
7—1
Sample Update Report
7 3
8-1
CEMSS Detail Report
8—4
8—2
Quick Look Report
8—7
8-3
Double-Spaced Quick Look Report . .
8—9
8—3.1
Two—Line Quick Look Report
8—10
8—4
SourceDataReport .....•••
.
.8—12
8—5
MilestoneReport ....
8—16
8—5.1
Single—Spaced Milestone Report
8—17
8—5.2
Three Element Milestone Report . . . . . . . .
. . I
I
8—18
xi
-------
LIST OF FIGURES (cont)
8—6 8—20
8—6.1 . . . . 8—22
8—7 . . 8—25
8—8 • . 8 35
8—9 . . . 8—35
8—10 • . . 8—36
8—10.1 . . 8—36
s—n. . . . . 8—40
TABLE ____
5—1
5—2 5—23
6—1 6—3
7— i.
8—1 8—37
8—2 8—42
FI3URE
P1i
CEMSS Stat Report
Questionnaire Report
Report Request Form .
Retrieval Job Control Language . ...
CEMSS Detail Report Job Control Language
CEMSS Stat Report Job Control Language
CEMSS Questionnaire Report Job Control Language
AF1LBUR Interactive Retrieval
LIST OF TABLES
PAGE
Action Types
Results Codes
Edit Error Messages.
Update Error Messages
Retrieval Package Edits
Retrieval Package Edits - .. .
xii
-------
ACKNOWLEDGEMENT
This User’s Guide was prepared for the U.S. Environmental
Protection Agency by TRC Environmental Consultants, East Hartford,
Connecticut. Mr. Mark Antell was the EPA Task Manager. Mr. Robert
Bowers served as TRC’s Project Manager. The principal author is Mr. -
Robert Bowers. The author would like to thank the Continuous Emission
Monitoring Systems (CEMS) Program Coordinators and the Compliance Data
System (CDS) Managers in the EPA Regions and Headquarters for their
review. -
xiii
-------
SECTION 1.0
INTRODUCTION
-------
,O INTRODUCTION
Continuous Erniss ions Monitoring System (C 1S) programs provide the basis
£or the most comprehensive source surveillance networks available to the U.S.
Environmental Protection Agency (EPA)., The Stationary Source Compliance
Division (SSCD). EPA’s Regional Offices, and State and local agencies must
implement an effective and successful CEMS program for numerous categories of
pollutant source. These consist of several New Source Performance Standards
(NSPS) sources categories and four categories of State Implementation Plan
(SIP) sources. The SIP sources include fossil fuel—fired steam generators.
sulfuric and nitric acid plants, and petroleum refineries. A partial listing
of CEMS regulations can be found in Pate.*
The CEMS programs will help ensure the necessary reductions of emissions
mandated by the Clean Air Act and its amendments. Proper CEMS procedures will.
contribute to the attainment and maintenance of National Ambient Air Quality
- andards.
As part of the CEMS process, stationary sources subject to CEMS
requirernent,s submit Excess Emission Reports (EERs). These EERs are submitted
generally on a quarterly basis to the appropriate Federal, State, or local
enforcement agency. These reports allow enforcement staff to do the following:
• Determine the adequacy of the source’s monitoringsystems
• Track proper operation and maintenance procedures
• Indicate the procedural compliance of a source with all applicable
monitoring requirements.
•Pate, W.J. Regulation and Resource File of Continuous Monitoring
Information . Kilkelly Environmental Associates, Inc. EPA Contract
No. 68—01—008. January 1983.
1—1
-------
EERs provide vital information to the enforcement staff about rnalfunctio s
of control equipment, and they monitor the performance and the duration
emissions that. exceed legal limits.
Enforcement staff use the following strategies, which depend on EER data:
• Identify t rgets for potential enforcement actions by using
frequency and’duration of excess emissions.
• Measure source compliance by monitoring emissions results.
• Use ‘historic EER data as a basis for changes in source
performance. such as the reduction in the number of excesses, the
increase in monitor up—time, and the improvement of control
equipment.
SSCD has utilized technical reviews of EERs to determine the level of
continuous compliance with applicable standards achieved by subject sources.
Within the last few years, SSCD has placed an increased emphasis on continuous
compliance. Because of the increased number of sources subject to CEMS
regulations and the volume and complexity of the data, a subset of I
Compliance Data System (CDS) was developed. This system, called the C 1S
Subset (CEMSS), provides the capability to maintain and report monitor
inventory and summarized LER data. The organization of data in the CE24SS is
identical to that in CDS. In addition, the C 4S data is linked to CDS through
the same source and point numbers used in CDS. The CD 1S data are stored
separately from the CDS Masterfile, but the CDS data on the Cfl4SS Masterfile
are always identical to the data on the DS Masterfile. The CD4SS provides
most of the capabilities provided by the basic CDS.
This C 4SS User’s Guide is designed to provide EPA management with the
information needed to operate and use the C 2 SS. Users not already familiar
with CDS should review the Compliance Data System User’s Guide
(EPA—340/l—80—020) , as well as this entire manual. Engineers and managers who
need to obtain management reports should refer to Section 8.0. Retrie
1—2
-------
Processing, and to Appendix A, the C 1SS Data Dictionary. Data analysts
should refer to Section 5.O . Data Input Preparation, and to Appendix A, the
EMSS Data Dictionary. Other helpful portions of this document include
Appendix B, Memorandum: Guidance Concerning EPA’s Use of Continuous Emission
Monitoring Data. Kathleen M. Bennett, August 12, 1982. Appendix C, Final
Technical Guidance on the Review and Use of Excess Emissions Reports; Appendix
D, Suggested Continuous. Emission Monitoring Excess Emissions Report Format;
Appendix E, EPA Regional C 4S Contacts, and Appendix F, Changes Incorporated
in CEMSS Under the C 4SS Upgrade Task.
Comments and suggestions regarding this manual should be directed to Mr.
Mark Antell, the National Continuous Emission Monitoring System Subset
Coordinator at FTS 382—2878.
1—3
-------
SECTION 2.0
MANAGEMENT OVERVIEW
-------
2.0 MP NAGEMENT’ OVERVIEW
The C 4S Subset was originally developed for the SSCD by TRC,
_nvirorunental Consultants, Inc. In 1981, GEOMET Technologies, Inc., was asked
to make this system operational and to provide data analysis services for EERs.
In 1985 the CEMS Subset was returned to TRC Environmental Consultants,
Inc. at the request of SSCD. TRC’s task was:
• To identify and eliminate problems in the operational areas of the
CEMS Subset;
• To review “Technical Guidance on Review and Use of Excess Emission
Reports (EPA—3410/1—84—0l5)” to document the information
requirements relating to Subpart D sources and modify the CEMSS
pursuant to this guidance.
• To modify the CEMS Subset’s COBOL programs to track Subpart D, and
other sources incorporating the new information requirements;
• To Design an updated Continuous Emission Monitoring Data Form
which will contain a new card type (card 72) to allow space for
the additional data;
• To design a new CEMSS Report (Retrieval) Request Form consistent
with the changes herein;
• To develop new WYLBtJR input and Rerieval Exec programs to
acconui odate the additional data in CEMSS;
• To modify the CEMSS data element, “TIME”, to allow for several one
letter codes which will represent the time period in which source
operating time, durations of excess emissions, and monitor down
times are records;
• To modify the CEMS ‘Subset to track number of incidents for excess
emissions and monitor down time;
• To modify the STAT Report;
• To add a three element milestone capability;
• To revise the titles and content of “compliance”, fields on the
DETAIL Report tà eliminate the term “compliance”;
• To provide documentation explaining the special handling and
interpretation of Subpart D data; and
• To provide documentation of the changes made to the subset.
2—1
-------
This revised user’s guide is the resulting documentation of the abov
changes.
The primary purpose of the C 4SS is to assist the EPA and other agencies
in carrying out their enforcement and surveillance programs. The C 4SS
provides users with an effective tool for promptly. and efficiently managing
large quantities of CE24S—related stationary source information. Output
reports from the system enable an agency to (1) maintain a complete inventory
of facilities emitting regulated C S pollutants (2) assess compliance and
enforcement Strategies, (3) monitor the success of continuous emissions
monitors in detecting excess emissions, arid (4) assess the effectiveness of
corrective actions.
2.1 System Purposes
Regional Offices will use CDSSS in a number of ways in their enforcement
programs. The CE24SS is used primarily for the following reasons:
• To provide an accurate and easily accessible inventory of
facilities subject to CEMS regulations and their compliance status
with respect to these regulations.
• To develop enforcement strategies by providing summaries of the
compliance status of facilities tracked by the CEMSS.
• To determine the effectiveness of different types of pollution
control and continuous monitoring equipment.
• To identify trends in control of emissions and maintenance of
monitoring equipment.
• To provide various turnaround reports to be used by states in
fulfilling their reporting requirements to the regions.
Appendix B is a memorandum from Kathleen Bennett that addresses EPA’s use
of CEMS data in enforcement of NSPS and SIP emission and operating arid
maintenance (O&M) provisions and in other general EPA activities.
2—2
-------
2.2. System Capabilities
The CEMSS provides users with the, capability to store, update, and
.... trieve information about all of the facilities placed on the CD S
Masterfile. The CEMSS is used to record information on identified major
polluters; it provides information about the various types of monitors used at
these facilities; it records the reason arid duration for excess emissions; and
it helps to track the enforcement actions taken by regulatory agencies against
these facilities.
Multiple input record formats are used to enter data into the CEMSS by the
Edit Program. The CEMSS tracks specific CEMS data, as well as facility,
emission point, and action data maintained by the CDS. All facility data must
be entered into CDS, but only monitoring and excess emissions data can be
entered into the CEMSS. However, the CEMSS retrieval can print data entered
into either CDS or CEMSS for sources subject to CEMS requirements.
The Update Program uses each of the different input record formats to add,
cnange, or delete information on the CEMSS Masterfile. Once data is placed on
the CEMSS Masterfile, the Retrieval Program can be used to create a wide
variety of management reports ‘based on the data on the Masterfile.
The CEMSS retrieval capabilities are highly flexible. Users can obtain
reports based on all data on the CEMSS Masterfile or on only that portion of
the data that meet user selection criteria. Four fixed—format reports aswe]l
as 2 flexible format reports can be designed to fit any particular user
requirements. After a user determines a suitable report format and the
portion of the Masterfile that should be included on the report, he or she can
specify the sorting criteria for the report. Thus, the data can appear in any
desired sequence. Because of this flexibility, the CEMSS adapts easily to
changing reporting requirements.
2—3
-------
2.3 System Functions
A number of computer programs have been developed to input, update,
retrieve C S data.. These computer programs and all associated data files are
available at the EPA central computer facility. Currently, this facility is
operated at the National Computer Center’s IBM computer. All regional users
have computer terminals connected by telephone lines to the EPA computer in
Research Triangle Park, N.C.
Input transactions prepared by regional users or Headquarters can be
transmitted at any time to the central computer facility. The Edit Program
validates these transactions, and valid transactions are stored for further
use in the Update Cycle. An Edit Report showing the Edit’s action on each
input transaction is returned to the user’s terminal after the computer
executes the Edit Program. Under normal operating conditions, the national
DBC (Data Base Coordinator) schedules the Update Cycle to run weekly. During
periods of high data entry activity, especially at the end of each quart
more frequent updates may be scheduled at the discretion of the DBC. All
valid transactions saved since the last update are applied to the CEMSS
Masterfile during the Update Cycle.
The Update adds, changes, or deletes data on the Masterfile, based on the
Update Code of each transaction. The Update produces an Update Report to show
what action it took on each transaction. After each Update Cycle for which
the user had input data, the DBC runs the C 24SS Update Report to show which
transactions were successfully applied to. the C 4SS Masterfile and which had
Update errors.
Once data has been applied to the C 4ZS Masterfile by the Update, users
may request management reports through the Retrieval Program. The Retrieval
extracts, sorts, and prints data from the most current version of the CEMSS
Masterfile. Requests’for retrievals may be made as often as necessary. Un
2—4
-------
ormal operating conditions, quick turnaround is available for short
retrievals.
Regional users are responsible for data submission and retrieval
requests. For those regions that have an inadequate staff to perform’ the data
reduction and data entry of EERs, contractor assistance is available. 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.
The C SS is closely associated with the CDS. Both systems use the’
source, emission point, and action data structure. All current source, point
action, and comment data from CDS are picked up during the CEMSS Update Cycle
and are merged with the data unique to the CEMSS. Thus, CEMSS retrievals
represent a combination of the most recent CDS data together with the excess
emission data submitted to the CEMSS. Regular source, point, and CDS action
data should be entered directly to CDS; only CEMS action data, monitoring
ata, and excess emission data should be entered into the CEMSS.
Users are urged to become familiar with the CDS User’s Guide (EPA
Publication 340/1—87—001) in order to •obtain the necessary background
information on CDS. Users already familiar with CDS will find the CEMSS easy
to use. This user’s manual is designed to supplement the CDS User’s Guide
with features unique to CEMSS data handling problems.
2—5
-------
SECTION 3.0
SYSTEM OVERVIEW
-------
3.0 SYST 4 OVERVIEW
The C 4SS provides users with the ability to store, update; and retrieve
_arge quantities of data useful to an enforcement program. To meet these
objectives, the CE24SS has been designed to perform three distinct functions:
edits, updates, and retrievals.
Users are .responsible for preparing data for the C 4SS in order to
maintain an up-to—date. Masterfile. Once input data have been updated,
regional users are responsible for the preparation of all retrieval requests
from the system.
National Headquarters’ responsibilities include the following:
• Developing and’ maintaining all CEMSS programs, data sets, and
table values
• Scheduling all Update Cycles
• Providing definition and usage of all nationally controlled data
elements
• Establishing retrieval guidelines for meeting national reporting
requirements
• Providing user training for any region requesting training
• Responding to regional requests for system modifications
• Coordinating the transfer of data between the CEMSS and the CDS.
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.
3.1 Edit Proqram
CE S data are initially processed for the Masterfile by the C 24SS Edit
Program. Regional , users gather data concerning sources subject to C S
requirements, and then prepare this data in a format acceptable to the Edit
ogram. Multiple fixed—card formats are available to the user for preparing
3—1
-------
data as input transactions to the Edit Program. Whenever users have ‘a
sufficient amount of data to be submitted, they initiate the Edit Program
submitting the keypunched input transactions together with the appropriate Job
Control Language (JCL) to their .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 wi]]. 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 disk file until the
next scheduled Update Program. One or more fatal errors will prevent a
transaction from being saved for the Update Program. A transaction with only
warning errors will be saved for the weekly update, but the data elements in
error are blanked out.
The Edit Program can be run’ as often as necessary in between update
cycles. Each time that the Edit is run, an Edit Report is immediately
produced and sent to regional users for review.
3.1.1 Input Data Processed by the C 4S
Data is input to the Edit Program on punched cards or 80—character card
images on tape or disk. There are five card types extended by a level to
provide maximum data entry capacity for monitoring and excess emissions data.
The five card type groups are cards 1(10), 5(51,52), 6(60), 7(70,71,72), and
8(80). Section 5.0 describes the card formats available to the CEMSS.
The cards provide the following general information:
• Card 10 copies a source from the CDS to the C 4SS or deletes a
source from the C 4SS.
3-2
-------
• Cards 51 and 52 provide descriptive monitor data for various
continuous emission monitors.
• Card 60 is a monitor comment record, which provides additional
information for a given monitor.
• Card 70 describes specific CEMS enforcement actions.
• Cards 71 and 72 provide EER summary data for a given monitor.
• Card 80 is an action comment record, which provides additional
information for information contained on a Card 70, 71 or 72.
3.1.2 Edits Performed by the CEMS
The CEMSS Edit, Program examines and validates all input transactions
processed on the multiple fixed—card, formats. Errors, classified as either
warning or fatal, 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, •P 5ON CODE MUST BE NUMERIC. 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 printout line. A transaction with multiple
errors will have multiple error messages.
If an input transaction has no edit error messages next to it on the Edj.t
Report, it is a valid transaction and will be stored on the CEMSS 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
for processing by the Update Cycle. A transaction with only warning errors
will be’ stored for processing, but the data elements in error will be blanked
out.
3—3
-------
All valid CE SS transactions are stored on the CE 4SS Mod File. Only an M3
Action Type ( submitted) is transferred to the CDS Mod File for updating.
Each card type has its own validation procedure within the Edit Program.
Certain data elements, such as County Code, Air Quality Control Region (AQCR),
Action Type, Results Code, and Personnel Code, are validated by external table
lookup 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 contain the
new value. Other data elements, such as Region, State, Reason Code, 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 keypunching
and coding errors, the program has its limitations. The Edit àannot 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 CE
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. Even those transactions
containing no edit errors should be examined by new users to make sure that
they are properly preparing data for the system.
Figure 3—1 is a flow .chart of the Edit Program. Input to the Edit
consists of the varioi.is input card formats together with the appropriate TCL
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.
There are four outputs from the program:
• The Edit Report
3—4
-------
Figure 3- 1. EdIt Flow Chart
3-5
-------
• • The C 4SS Mod File containing all valid input transactions (With
each run of the’ Edit, additional valid transactions are stored
here until the Update Cycle applied these transactions to the
Masterfile.)
• The CDS Mod File containing a].]. valid CDS transactions (M3 Action
Type) ‘
• 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).
3.1.3 Edit Error Messages
The Edit Program identifies the two kinds of errors, warning and fatal,
made on the multiple 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’ 3.1.2. Typical etror messages are listed as follows:
FATAL ‘ WARNING
INVALID STATE CODE * REASON FIELD MUST BE NUMERIC
*** LINE NUMBER MUST BE NUMERIC ‘* INVALID RESULTS CODE.
Valid values that can be entered on the card formats for each data element
are listed in Appendix B. Each data element sheet lists the appropriate
coding values and coding’ considerations necessary for preparing •card format s
and for making corrections.
3.1.4 C 4S Mod File
The SS 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 nonfat -
3—6
-------
e’rrors are added to this file. Any number of data submissions may be made to
the Edit inbetween one Update Cycle and the next. Each submission adds
ditional data to the Mod file. At the beginning of the next Update Cycle.
the data on the Mod file are copied to magnetic tape. Then the transactions
on the file are sorted into order by region, state, county, source, point, and
action number. 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, action number, and channel number),
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.
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 in a file on cards or other information storage device for
least 1 month for security and backup purposes.
3.2 Update Program
The C 4SS is updated periodically by the Update Program. All transactions
stored on the CEMSS Mod File by the various runs of the Edit Program •are
processed by the Update Program. Input to the Update is the current CDS
Masterfile, the old C}24SS Masterfile, and the current input transactions
placed on the C 24SS Mod File by the .Edit Program from all regional users.
Output from the Update is an updated C 4SS Masterfile and the Update Reports.
Once the Update Cycle is complete, each regional user who had input data
for the Update Program should review the Update Report. This report shows
what action the Update Program took on each transaction passed to it by the
various Edit runs. Whenever the Update Program cannot process the add,
3—7
-------
change, or delete a transaction specified by the user, a reject message will
explain why the transaction was not applied to the Masterfile.
Transactions stored on the CDS Mod File prior to Wednesday night will be
processed by the CDS Update. The CEMSS Update uses the CDS Masterfile to
update all related sources on the C 4SS Masterfile.
3.2.1 Update Actions to the CEMS
Card types 51’ through 80 processed by the Edit Program are used to add,
change, or. delete information on the C!24SS Masterfile. The Masterfile
contains records that correspond to the input card types. Input transactions
perform the following functions: -
NEW When an Update Code ‘N’ is used in the Update Code column,
the input transaction will add a new channel, action, EER,
or comment’ record to the CEMSS 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 çne or more
Masterfile records fora given facility.
3.2.2 Update Cycle Steps
In addition to applying input transactions to the C 4SS Masterfile, a
number of other steps are taken in each Update Cycle:
• Inpu transactions from the Mod File are saved on tape.
• Input transactions are sorted into the same sequence as the
Masterfile.
• CEMSS data are copied from,- or updated, by the CDS Masterfile.
• The Mod File transactions are erased to make room for the next
cycle’s input transactions.
Figure 3—2, Update Flow Chart, shows this process.
3—8
-------
FLgure 3.2. Update Flow Chart
3—9
-------
3.2.3 Update:Report Messages
On the UpdateReport are several column headings that indicate what acti
has been taken by the Update Program on each transaction passed by the Edit.
A normal update action’ message of ADDED. CHANGED, or DELETED will indicate a
successful Update’, Action. The word REJECT in the Update Action column
indicates that ‘the Update Program could not perform the appropriate add,
change. copy, or delete as indicated in the Update Code column. For each
rejected transaction, a diagnostic error message is printed out under the
Error Message column. Typical Update error messages are as follows:
• SOURCE NOT ON FILE
• POINT NOT ON FILE
• DUPLICATE TRANS
• ALREADY ON MASTERFILE.
An ampersand appearing in the Error Message column indicates that multii
changes have been applied to the Masterfile in chronological order. Section
7.0 lists Update error messages and their causes.
3.2.4 The CEMSS Masterfile
The CEMSS Masterfile resides on computer disc and magnetic tape. It
contains data for stationary sources of air pollution for the 10 EPA regions.
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. seven Masterfile record formats. These
Masterfile record formats are numbered 20, 21, 30, 34, 35, 46, or 47 for
interna 1’ computer identification purposes. The seven Masterfile record
formats contain information as follows:
• Record 20 contains facility—level data from CDS Cards 1 and 2.
Each facility, has one record 20. Region, state, county, and
source numbers identify ‘a unique facility. This data can be
3—10
-------
entered on].y through CDS. This data is added to CEMSS by use of a
card 10 add transaction.
• Record 21 contains comment information for the facility record.
Up to 10 comments may be used for each facility. Each CDS Card 4
added to the’ Masterfile creates corresponding Record 21. This
data can only be entered through CDS.
• Record 30 is the pollutant compliance record. One of these
records is present whenever CDS Card 3 input is submitted to CDS.
Data for up to 10 pollutants can be placed on this record. This
data can be entered only through CDS.
• Record 34 is an emission point record created from the Card 51 and
Card 52 input transactions. Each emission point identifies a
unique physical point/pollutant/monitor. All emission point
records defined for additional pollutants and/or monitors related
to a single physical point may be associated ,by use of the
multiple XREP field on a CDS Card 5.
• Record 35 contains comment information for an emission point or
monitor. Each may have up to 10 comments. Each Card 60 added to
• the Masterfile creates a corresponding Record 35.
• Record 46 is an action record created from the Card 70. Card 7Ô
is used to record CEMS/CDS actions; Cards 71 and Card 72 with an
action number Quarter Date greater than 0099 record EER summary
data.
• Record 47 contains comment information for an action record. Each
action may have up to 10 comments. Each Card 80 added to the
Masterfile creates a corresponding Record 47.
Figure 3-3 shows the hierarchical relationship between the various’ Masterfjle
record types.
3.2.5 CEMS Retrieval Masterfile
In one of the last steps of the Update Program, the updated EMSS
Masterfile tape is copied to create a retrieval Masterfile, which resides on a
disk storage device. This file contains the most current version of the CEMSS
Masterfile. All retrieval requests are based on the data contained on the
retrieval Masterfiles. •
Users should note that input transactions processed by the Edit are not
retrievable until after the transactions have been applied to the retrieval
. sterfile by the Update Cycle.
3—11
-------
Region, State, County..
and Source Nialber -
Provide a UniQue
Facility Identifier
Record 34
CHANNEL LEVEL DATA
Monitor Manufacture,
Installation Data, Etc.
Record 48
CEMS ACTION
CONMENTS*
I Recorø e
I QUARTE .(
EER
COMMENTS*
FIgure 3-3. CEMS Masterfile Hierarchy
Up to 10 c i ents per point/action
3—12
-------
3.3 Retrieval Program
The CEMSS Retrieval Program is used to prepare management reports based on
he Cfl4SS Masterfile and was designed to meet the specific requests of
regional users. Alloutput 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 because they are processed independently of the Update
Program. The Retrieval Program will produce the following management reports:
• Quick Look Report
• Double—Spaced Quick Look Report
• CEMSS Detail R :ort
• Source Data Report
• Milestone Report
• CEMSS Statistical (Stat) Report.
These six reports are described in detail in Section 8.1. with examples of
ach report type.
3.3.1 Retrieval Steps
Each time a user requests a management report through the Retrieval, the
following steps are taken by the various computer programs constituting the
Retrieval:
• Retrieval selection cards are checked for validity. An Edit
Report page is printed to show the logic used in preparing the
Retrieval.
• CEMSS Retrieval Masterfile records that satisfy all of the users
Selection criteria are placed on a temporary extract file.
• Extracted records are sorted into a user—specified sort order.
• Sorted records are formatted for printing into user—specified
• print formats.
igure 3—4, Retrieval Flow Chart, shows this process graphically.
3—13
-------
User
Sel ection
Cards
PIgur. 34 RethevalFlow Chart
3-14
-------
SECTION 4.0
DATA SUBMISSION PROCEDURES
-------
4.0 DATA SUBMISSION PROCEDURES
The following steps describe the procedures for using the C 4SS. These
:eps outline in chronological order a general sunu ary of how the CE2ISS should
be used by the regions. A detailed description of each step is provided in
Sections 5.0, 6.0, 7.0, and 8.0.
1. Prepare the Data . Fill out the appropriate coding. sheets as
described in Section 5.0. Have the coding sheets keypunche.d or
use the WILBUR Interactive data—entry technique (Section 5.5).
2. Run the Edit Proqran . After the CBMS records have been entered,
prepare the appropriate JCL cards for running the Edit Program.
Submit the JCL and input transactions to the computer.
Submissions should be made with a “TI =(0,3)”, because the Edit
is both quick and inexpensive to run (approximately $2.00 per
1,000 cards with time = 3 seconds). The Edit will run within 1
hour.
Because multiple runs of the Edit Program can be. made between
Update runs, experience indicates that it is best to submit data
in several smaller batches during the week as soon as data are
entered.
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 that are error—free
have no error messages printed on the right—hand column labeled
Error Messages. These error—free entries should still be checked
for validity.
The Edit program identifies two types of errors—-warning and
fatal. Warning errors are identified on the report by aw error
message preceded by a single asterisk (such as *INtJ J Ib STAFF
CODE). The Edit will.blank out the data element in error, but the
transaction will be passed to the output Mod File for processing
in the Update Cycle. One warning message is issued for each data
element containing a nonfatal error.
Fatal errors are identified on the report by an error message
preceded by three asterisks (such as ***INCOP,p,ECT 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 6—1 gives a complete list of all errors identified by the
Edit Program.
4-1
-------
For both warning and fatal errors, asterisks are placed directly
underneath the data element found to be in error. These asterisks
are designed to identify the data element that 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, keypunched, and
submitted to the C 1SS 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 Mod Files. 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. The valid
transactions on the Mod File are applied to the CE24SS Masterfi].e
by the Update Program. The scheduling and the maintenance of the
Update Cycle is the responsibility of the national DBC.
6. Verify Update Run . The national DBC will route a copy of the
Update Report to the users terminal (Remote Printer Site).
7. Examine Update Report. . The Update Report has one print line for
each transaction sent to the Update Program by the Edit Program.
Next to each transaction on the report there is an Update Action,
which shows that the transaction was either added, changed,
deleted, or rejected from the CF2 SS Masterfile. If the
transaction was rejected, there will also be an error message
explaining why the transaction could not be added, changed, or
deleted.
8. Correct and Resubmit Update Errors . Transactions passing all of
the validation routines of the Edit Program may still be rejected
by the Update Program. The Update rejects all logic errors caused
by an incorrect Update Code on the transaction; for example, the
Update cannot apply a change transaction to a record that does not
exist on the Masterfile. Table 7—]. shows the update error
messages generated by the Update.
All errors appearing on the Update Report must be researched and
recoded. Corrections should be resubmitted to the CE 4SS through
the Edit Program.
9. Request Management Reports . The C 4SS can produce the following
management reports:
• CE iSS Detail Report
• Quick Look Report
• Double-Spaced Quick Look
4—2
-------
• Milestone Report
• Three Element Milestone Report
• • Source Data Report
• CE24SS Sta’t Report
• Questionnaire Report.
The user should consult Section 8.0 for the procedures to obtain
the above reports. •
4—3
-------
SECTION 5.0
DATA INPUT PREPARATION
-------
5.0 DATA INPUT PREPARATION
5.1 General
All input data to the CEMSS must be prepared in the format of one of the
card layouts shown in Figure 5—1. These are the only formats that the system
will accept. The data may be entered into actual 80—column records or
prepared through.a special WYLBIJR screen—prompting data-entry technique.. Each
record must have columns •l—26 (region, state, county, source, point, action,
channel, and card code) and column 80 (Update Code). The other data lements
are unique for each card code.
The CDISS card code consists of two characters. The first character (5—8)
indicates the relationship to CEMSS Masterfile records. The second character
(0—9) permits multiple. input cards to be applied to each CEMSS Masterfile
record. The following documentation usually refers only to the first
character. The relation:of card codes to Masterfile records is outlined below.
Record Record Code Card Code
Monitor Description 34 51, 52
PointComment 35 60
Action Summary 46 70
EER Summary 46 71, 72
Action Comment 47 80
The following sections will describe the transfer of data from the EERs to
the C 24S coding sheet and the specific procedures used to add new records,
change records, or delete existing records from the CD SS.
5.2 Excess nissions Report
As mandated by 40 CFR 60, Paragraph 60.7(c), and by 40 CFR 51, Appendix P.
all sources subject to CEMS requirements must submit an EER on a quarterly
basis. The EER should include at a minimum the following items as stated by
e CEMS regulations:
5—1
-------
‘•I • I (Ipfl . ‘j... lfl.I*
l,,icc lo,’ cIl c*ao r,.*
rni*l 00 00 ‘,mI 00
4 IS 16 i1 I;o13i 23 fl34 )
0 010_il 7J0 I
010Jl1 1 0111
IiSS uIWS ((*tIP0 lI
roll, im 1 I SI
IfN ’
Q *alIa D II
I* 1 .’INI t(ltIll l*l
roll, 141 ,
‘till’;
QUISSIP rail
11 1 0le14’•’ I
ruins 550
S0 0i
4 Ii 16 51
o 11
01
I I I I
1
—
I I
L
. -
13
l
—
lI . I M36I3 1 1 1t’ ‘±
D
Figure 5—I. Sample Coding Sheet
5—2
(410
‘14’1
CONTINUOUS E ISSION MONITORING
INPUT CODING SHEET
USE CARl) IWF 10 WILY W1I(II ADDING OR 01(1 )1 11 1 ’ , A SOURCE
i I II91 ‘: i’
,nRcit ss (?*0
101151 I I I ( ( WI .
II IS 16 17 Ij 7 0 7l 77 33
o ___ 0101019 I
i,.i%cIn s,
rai..s •‘ ) I. , , .
14 1316 I?l,f430 131 ‘‘
0j J9I05l2
Ifl IS ION
(f i Sh N fl
16 I?
oj
67 II79I3OI3I 33 33I3 343. 3, IJ(4c44I
i;JW ’LT ’
43444441
—
44 l7
‘f
4449 S
(TflT
S3! 3 3
IS
7
-
4
t1
S
1 -(1
4746
— —
4714149 i .A ,i 72 ‘3 ,sI ,el, , 17S, ,
T I . . 1 I i ’
SO
..--.
U
A
n, hhh,
11’
(N1W45
• I •1•
--1—1—
llON pI lIu l(ftgI l
00551101 114141 550
TIl_n99i91irI1 1911?
(INIld0*( 114 15 aU I 0 -
I • .; ..iua •l01,14 PI C
nisMaLa D1ss u uiu?
._I_ J _
I
191 I9
II
I
1 J 1 i1’ft
CII S ( A 5I01
141 N
! ‘— •,I.. 1.I..J,,I,A,3 174 7,1,. 17 70 79
I 11111 II I I I ;II .
I
¼
o]o
1N14 1 100 11 11*1 00. ¼
¶19 1 I19111 i1’ r
‘ ‘l
!!
7•3 33143! 3631 35 79 3I [ ?_ 33
60 III
i1! .
3 ’I3fl
—
19 4 11 r
UlO
( 574
p
(lI l(t
—I
.h
II00 ( I(NIS
144141
zr
146141
-&-
4S 1491R11 1131
i r’i’ i
2’ 1i 1 119 110 13’ 13 113 3
I-
I0
—
i l I i - --—iiiiiiiiiiiiiiii_i_iiiII
11311 413 51361, ,lSiI19 I6 1I6i6164I6 1I66I67I6SIe9I7
( 0 * 5
‘ . 5 54
—
I I
‘lilt 305(1
WI0 1 1I00 5114
1 111*5545
NO
11171
I. I I;l Il I I II l II l Ii!l!I i! i li.
7 3174173
‘ (: 104 0155 1455(145 01 15 01540615 N1 013015 1141
3313êI3Pi3SI3 1 141 4 l 1a I1 .k (4 14iIic4 ,I3,I,3k4 ,sIi . I.;I i; i (4 I 4ii (ñ .j ’ o
7617,I,II79 SO
RI ASIIII roi’
%i’U PIONIIl
I I
XCESS (111551011
04? 0657 (I
II
(045001
lI lt 10111
—I I I I I I 1_ —
11i! l
‘I” 24143631
L2J
C
(*00 1100*111 V
lrq 157
32 33II4I3
c .t t 1q01 10651 ,
ImaccI1TIJLZ I P’O ’liS PMi 5’$
(0’ ¶1006)
I
I
*.I
.._
NO
. -
1 0 O N*( 5% —
1
11141 p
-_Sat in I llS
REASON
00 11 1041101
ron 110111 1OR LIDWIIHII(
r I isti
_ M31*141
:: : ;:
._!! 5Isl4
II (!
• (l sSIl* *1 3 11
1343713’
I I ;i
39
11111
10 14 1
, ISI p IL14U
US CC IPT8NJ
(*1104* L)
II
)3 14 3
80
36 17
Ill
514,,
I,
I1! ..!I! I I I’ 1* ‘. 1±
II
liii iIIiIIIi
I I I I I
I k!1’.!It!1!4 721’ 3I’ I’ ‘ I7’I”I7’I 7 ’ ‘!
II I IIIIII
MitOl (000113
4 ’1’ I “I’ l S i36I 1 1 . 1 6 I o2 . i l . 4 Io .I’,Io.Iocl 7 ’1it’3I’ 4I ‘ 1’oI”1 ’.I ”
II 11111111 I_I 1_ t_ J 1111 I-I
So
11111111
-------
• The magnitude, duration, and date of the excess emission period
(see Appendix A for period definition)
• The identification of each excess period that can be attributed to
startups, shutdowns, and malfunctions
• The cause of any malfunction and the corrective action or
prevent ive measures adopted
• The date, time, and duration of any monitor outage for reasons
other than zero checks and span checks
• The reason for monitor o itage and corrective action taken
• If there are no exóess emissions and no monitor outages, zero
excess periods :can be coded to indicate full compliance.
Appendix C shows a CU4S. .EER form that. includes all of the information
listed above. Unfortunately, not all EERs are submitted in a comprehensive
format, as shown in Appendix C.
An example of a relatively complete EER submitted for the first quarter of
1981 is shown in Figure 5—2.
The EER contains all the needed background information on the monitoring
equipment, describes all excess emission periods, gives reasons for the excess
emissions, and documents all àorrectiv actions. When coding EERs, the user
may find that not all formats are as easy to follow as the example shown.
Often the EER submitted is technically incorrect or has vital information
missing. Some common errors include the following:
• Excess emissions were not reported for each period as defined by
the regulations. Figure 5—3 is an LER that does not show specific
magnitude or excesses.
• Information such. as cause for excess emission and/or corrective
actions are not reported for each excess emission period.
Figure 5—4 is an EER with no corrective action information.
Some other conmon errors not shown in those particular EERs include the
following:
• Monitor outage information not reported
• Failure to monitor all required pollutants
5—3
-------
lof 5
Illustration A — Example Report Format (Rev. 4, 12/80)
CONTINUOUS F24ISSION MONITORING REPORT (CE24R)*
I. General Report Information *60.7(c)*
A. Date report submitted April 27,1981
B. Number of days in reporting period days
C. Period ending (check one): year of 1981
X Mar. 31 Jun. 30 — Sept. 30 — Dec.’ 31 — Other Specify _________
II. Company/Facility Data *(60.7(c) Some implied*
A. Owner/Operator Getty Refining and Marketing Company
1. Name Getty Refining and Marketing Company
2. Mailing Address P.O. Bo x 1121, El Dorado, KS 67042
3. Contact Name R.B. Miller
Title Pollution C ntrol& Energy Conservation Director
4. Phone Number AC (316) — 321—2200 ext. 329
B. Facility description
1. Plant Name El Dorado Refinery
Unit or process name and number (etc.) Boiler B—l07 and Boiler B—] .08
• 2. Mailing Address p.o. Box 1121, El Dorado, KS 67042
3. Plant Location El Dorado, Kansas
4. Type of product (steam, acid, etc.) Steam
5. Major input material(s) Water
6. Total hours of on—line production during reporting period See Below
7. Control device(s) operated None
**Brackets include citation of applicable regulation*
On—Line Production Tin e: January-March, 1981
B—107 2134 Hours
B—108 2126 Hours (Continued)
Figure 5—2. EER Submitted for First Quarter of 1981
5—4
-------
2 of 5
III. CEMS Operational Data *60.7 (b), 60.7 (d),* implied background)
:A. Parameters monitored (specify) Opacity Opacity _______
B. Equipment. description (use. foootnotes
if needed) B—107 B—108 _______
1. Manufacturer LSI LSI ______
2. Model number RZ 4 RM4 _______
3. Serial numbers: main chasis 1070 1646 _______
control unit — —
4. Basis of measurement (wet ordry) NA NA ______
5. Instrument span (range value,
specify units) 100% 100% _______
6. Span level check for daily
calibration (ppm) 25% 25%
C. Program information
1. Units of emission limit % _______ _______
2. Applicable emission limit 20% 20% _______
3. Averaging time of.limit
(hrs, days, ext.) 6 Mm. 6 Mm . ______
4. Reason(s) C 4S installed
(NSPS, SIP, permit, etc.) NSPS NSPS ______
5. Original installation date 1975 1977 _______
6. Last equipment start—up date -
7. Last PST date.(attempt
(include results of in this quarter) 1978 1978 _______
8. Last successful PST date 1978 1978 _______
NOTE: Only fuel gas was fired in B—107 and B—l08 during this reporting
period, so no SO 2 limits were applicable (4OCFR 60.43).
(Continued)
Figure 5—2. EER Submitted for First Quarter of 1981 (Continued)
5—5
-------
3 of 5
IV. Excess issions Report (EER ) *60.7 (c)(1) & (2)*
Illustion B is an example format for reporting these data. Table I may be
uSed to format reports when using automatic-data handling equipment in CEMS..
Attach: a listing of cause codes to Table I. Causes must be explained in
detail i for each specific excess emission if Table I (a) is used to format
reports prepared manually from hourly data.
V. Data Assessment Report (DAR ) *New, 60.7(c)(8)*
When reportiri quality assurance checks during the reporting period, Table
II in I1lustrati4 :1 C may be used as a guide. Minimum information to be
i cludEd applies to precision and accuracy checks, traceability/certification
of caLibration materials, and maintenance actions for excessive calibration
drift : or error. Requirements are as specified either in the general
provisions or the specific regulation for a •specific industry.
VI. Monitor Status Report (MSR ) *607(c)(3)*
Table III of Illustration D may be used to format reports of CEMS upsets,
málfunàtions, and downtime. Complete for each parameter monitored, including
dSluent and/or volumetric flow rate, as applicable.
VII. Certificaton of Report Integrity (by supervisory person, responsible for
CEMS data validity) *60.7(c) .*
• THIS IS TO CERTIFY THAT TO THE BEST OF MY KNOWLEDGE, THE INFORMAT
PROVIDED IN THE ABOVE REPORT IS COMPLETE AND ACCURATE.
A. On—site person completing
report
Signature
R.B. Miller Name
Poll. Cont & Enrg Cons Direct Title
P.O. Box 1121 Address
El Dorado, KS 67042
AC (316)—321—2000 ext. 329 Phone
__________ ,19__
B. Environmental Program
( on—site) Manager
R.B. Miller
Poll. Cont & Enrg Consrv. Director
P.O. Box 1121
El Dorado, KS 67042 .
AC ( 316)—321—2200 ext. 329
(Continued)
Figure 5—2. EER Submitted for First Quarter of 1981 (Continued)
_____ , 19
5—6
-------
4 of• 5
CCESS EMISSI1 TU Q ARY (by week)
Reporting Date(s) 2—15 to 21 , 1981
Affected Facility’ B—108
Parameter Monitored
ge 1 of
Conversion Factor Method 1 N.A. -
Number of on-line production hours during week 168
Value of Conversion Fa:
Used
ission Period
Date Beqin
Reason for Excess Emission(s)
Action Taken (if excess is
caused by malfun:tion)
Unknown - None
2—15 1317 1323 0.1 23.8% Unknown None
0.2 Total Excess Emission Hours During Week
1 State that the factor was developed from plant test data or that a-published conversion
2 To be reported in the units of applicable standard, e.g. lbs/10 6 BTU, lb./ton, etc.
‘Be specific, e.g., Boiler No. 7, Acid plant E, etc.
2—15
End
1311
Duration
(Hours) Maanitude 2
1317
0 . 1
21.4%
factor was used.
(Continued)
Figure 5—2k EER Submitted for First Quarter of 1981 (Continued)
-------
5of 5
VI. MONITOR STATUS REPORT
B— 107
Opacity meter out of service for a period of 101 hours from 3—13—81 to
3—17—81 to obtain and install a new blower motor. This opacity meter was
out of service 4.7%’of the boiler operating time during the quarter.
B—108
(1) Opacity meter out of service.or giving unreliable data for a period of
- 44 hours from ‘2—10—81 ‘to 2—12—81 dur to malfunctioning shutter.
(2) Opacity meter out of service for a period of 2 hours on 2—25—81 due to
malfunctioning shutter.
(3) Opacity meter out of service for 57 hours from 3—28—81 to 3—30—81 due
to foreign material blocking sight tubes.
This opacity meter was out of service 4.8% of the boiler operating time’durirtg,
-. th. guart.r.
Figure 5—2. EER Submitted for First Quarter of 1981 (Concluded)
5—8
-------
SIRtIAIT (I? or*cin VI0$ATI(1I
P.iurth r’
STAT tOUt
‘ InrS*s’Irs cIeanSn
( . 5 Iu,rs.
aSh pIs foul In. itaslon (-5 .IIi• rh,n Inr h,,rnc,q. 4t$U!It Soft
precipitator r .ppr . •nJ •saIli.ry equlp.rnl
Flpure 5-3. EER That Shows No SpecIftc.Ma nhtuJe or Exceocs
5-. 9
NTSTIC
U I
,1,Ix
•
i .
1
- . .
70.4C 1 >40 1
70 40t
4O1
70601
)4o1
70-401 J
)sot
10 .401 i
>
.
fliNtIfI.%
NIwurs.s
lI,rI.%
NIIU!TES
•
. N$ I U tJ1tS
—
CA ft$
.
Gc.tbI ts
i
so
u
9e
e
e
i
St.stvp.
too
0
4
30
73
s
es
.
t4Swn
9
35
1
.
6$
26
.7
75
3 )
56
51
.tr.I PeslIs..
1
30
I
0
1
Other’
3
l0 -
I
2
VALS
166
556
(.6
104
96
I
55
lBS
Tl to
lI ..t .
99.16
9901
99.0)
99.05
(AU Oec w: )
.
.
—
ZTS..h,
C.,.,.ISa,ue
99.66
99.95
99.90
1W!!) %.sutI .Inwln,
-
-------
My t.1c Ill: Indicated Excens Visible n1sslona
- JIHIE 29, 1980 THROUCH SEPTEMBER 27, 1980
DURATION
DATE TIME Hr Mn c MACNI’1 JDE
8—18 1:20 PM 00:05:00 45%
8—18 1:35 PM 00:03:00 50%
8—18 1:40 PM 00:08:00 86%
8—18 2:07 PH 00:01:00 43%
8-18 2:10 PH 00:11:00 90%
8—18 2:20 PM 00:09:00 69%
8—18 2:30PM 00:07:00 41%
8—18 2:45 PH 00:15:00 31%
8—18 3:20 PH 00:09:00 33%
8—18 4:00 PM 01:00:00 57%
8—18 5:02 PM 00:20:00 32%
8—18 5:50PM 00:45:00 35%
8—18 7:03 PM 00:29:00 26%
8—18 8:40 PM 01:06:00 44%
• That period during which the opacity monitor indicated that emissions
The magnitude listed Is the maximum reading for that time period.
0
CAUSE
Soot Blowers
Soot Blowers
Soot Blowers
Soot Blowing
Soot Blowing
Soot Blowing
Soot Blowing
Soot Blowing
Soot Blowing
Soot Blowing
Soot Blowing
Soot Blowing
Soot Blowing
UI A.H.
exceeded 20%.
FIgure 5-4. EER wIth N r e Action Information
-------
Figure 5—5 provides a reviewer’s checklist for an excess emission report.
The checklist will assist in evaluating •the completeness of the EERs.
complete EERs should be analyzed and coded as completely as possible and the
missing information obtained for later entry into the CEMSS.
5.3 Adding New Records to the CEMS Masterfile
5.3.1 Adding New C 4 . Source That Does Not Exist in CDS
Entries for all facilities subject to CEMS regulations should already
exist in the CDS Masterfile. If not, the new facility must be coded and
entered into CDS before the user performs any CEMSS coding for that facility.
The following procedure should be followed to verify that the source is in CDS.
1. Request a CDS Quick Look Reprt to verify that the facility does
not already exist on the CDS Masterfile.
— Be sure to check different deviations of •the facility’s name
and address. Because a].]. CEMS—regulated facilities are major
facilities, the source should exist on CDS in some form.
— If a check of all apparent deviations of the facility’s name
and address does not locate the facility, in CDS, a Quick Look
Report can be run for the entire state. The facility may be
entered in CDS in the wrong county or with the name or address
spelled incorrectly.
2. If a CDS match cannot be. found, before entering CEMS data, code
and entfr the facility into CDS; code and enter the necessary
emission point for the CEMS data, Including:
1. Identification of the pollutant being monitored
2. description of the emission source or combination of sources
being monitored/reported in the CDS point process description;
then follow instructions in Section 5.3.2.
5.3.2 Adding New CEM Source that Already Exists in CDS
A facility may be added to the CEMSS Masterf lie with or without any
‘-hannel—level information (monitor background information, reduced EER, etc.).
5—11
-------
EXCESS E 4ISSiCU E?0RT - vlZ’ jERS C IC::U3T
Source:
eporting period: ___________________ Required monitors: S0 , NO , opacity,
02, or C (cir: e)
Reviewer S signatire: ________________________ Date: __________________
Yes No NR NA
o o C 0 1. Is the excess enission report postmarked by the 30th day
following the end of the reporting quarter?
C C C 0 2. Were all riquf red pol1i tants reported?
C 0 0 0 3. If no excess enissions oc:urred during the quarter, has
this been stated?
C C C 0 4. If conversion factors are requir ’ed to convert monitor
data to units of the standard, is the method anc value
given?
C C 0 0 5. If the continuc s nonitoring system as been ocerative
and o repairs or adjus nents were maca, nas this infer—
nation been stated?
o 0 0 0 6. 4as plant opirating time been stated?
C 0 C 0. 7. Is the megnituda of the excess emission(s) reported in
units f the applicable standard?
C C 0 0 8. is data and time of commencement and completion of each
per cd of excess emission stated?
0 0 C 0 9. s eac period of excess emission, whicn oc: r d;rir.g
star: o, shutdown, and malfunction i er.cifiec?
C 0 0 0 10. Es the nature and :auie of the malfunction(s) in
tion a ac ressed?
0 0 0 C 12.. Es the ::rrec:ive action taken or preven:a:ive measures
acoptec for 9 above acdressac?
C C C 0 12. Es th data for opacity re or:ed in the plicabie time
per a averages (i.e., either S minutes or 1 cur)?
C C 0 0 :3. is the cata for SC. reocrtad in the a:o :able time
perioa averages (i.e., 2 sour, 3 cur, moving average)?
C C C 14. Es the data for NC reported in the :Y:a: e time
period averages (ire. , 3 hcurs, moving average)?
C C C C .S. Is the data and time of each period of the continuous
monitoring s::stam inocerativeness, axon; zero a .d
span c ecx.s, stated?
C 0 C C :s. : the tyae(s) of continuous .mcnit rin; system repair(s)
and/or ao ustment(s) ac ressed?
C C C C J. Is the monitoring system unc an;ed since the last :‘.S.
test?
Recommended action: __________________________________________________________
NR • ot• eoorteo ‘1A Not oplicab1e
Source: John P. Wood and Ralph L Roberson. Review of Excess Emission Reports (EERs) from
Statiànary Sources . Research Triangle Institute, EPA Contact No. 68-01-4141, Task 43. EPA
Report No. 34013-81-003, June 1981.
FIgure 5-5. RevIewer’s Checklist for an EER
5—12
-------
) . Code columns 1—13 (region, state, county, source number) with the
codes obtained from the CDS report; enter zeros in columns 14—21
and enter ‘10’ for Card Code and ‘A’ for Update Code.
2. All CDS information will appear on the C 4SS Masterfile after the
next CEMSS Update.
To copy a facility onto the CEMSS Masterfile from the CDS Masterfile, with
channel—level data:
1. Code columns 1—21 (region, state, county. source number, emission
point number, and action number) with the codes obtained from the
CDS report; enter an ‘N’ in the Update Code for all transactions
to be entered (51, 52, 60. 70, 71, 72, and 80). The emission
point number coded must be in the range of 0500 through 0599. See
Appendix C for an explanation of this requirement.
2. All CDS and CD S information will appear on the C 4SS Masterfile
after the next CD SS Update.
5.3.3 Card Types 51 and 52
These cards are used to add descriptive pollutant monitoring data for an
isting emission point. A continuous emission monitor consists of a single
device or group of devices monitoring an emission point; each monitor is
pollutant—specific. Note that there may be more than one monitor for an
emission point for three reasons:
• The same pollutant is being monitored separately for more than one
unit vented by a particular stack.
• Duplicate monitors or multiple monitors of different manufacturers
and/or types may be installed.
• The CDS emission point may not be pollutant—specific.
In: addition to the data describing the characteristics of the monitor,
Cards : 5]. and 52 contain information fields pertaining to Performance
Specification Tests (PST). for the monitor. In particular, the PST status
field is used by the Update Program to create counters in the monitor record.
? counters maintain cumulative counts of reported tests, passes, and fails.
5—13
-------
5.3.4 Card Type 60
Card 60 is a comment card used to add additional information about
particular channel (monitor) that is different from the information supplied
by the. monitor data on Cards 51 or 52. There are 10 comment line numbers
available on Card Type 60; up to 10 comments may be used to add information.
A channel comment cannot be added to the Masterfile unless a corresponding
channel. already exists on the Masterfile.
5.3.5 Card Type 70
Card Type 70 is. used to add information describing CE24S—related actions CM
actions) taken by the local, state, or Federal regulatory agencies on a
particular monitor. All non-Cfl4S actions should be entered through CDS. All
M3 actioü types (EER submission) will be transferred to the appropriate CDS
emission point.
CDSSS User’s
Guide Card 51
Data Field Number Coding Considerations
Th ission Point A.1—7 Each emission point number refers to pollu—
Numbe.r (PTNO) tant type emitted from one emission point
(stack or production process).
The first digit (Column 14) is always
coded ‘0’. In the next three columns
(15—17). code the three-digit CDS/CD SS
emission point number. This emission
point number must be in the range of 0500
through 0599.,. See Appendix G for an
explanation of this requirement. If the
emission point does not exist in
CDS/CD4SS, the point must be entered and
updated through CDS before C 24S
transactions can be applied. C 4S
information can be attached to all
CDS/ fliS emission points except the ‘000’
point central facility.
5—14
-------
Channel Number A.l—4 In order to properly identify, store, and
(CHAN) retrieve multiple—monitor data, a channel
number is part of the key identification
(see Appendix A). This. three-character
code uniquely identifies a pollutant being
monitored, single— or multiple—units
points, and each monitor (up to 10
monitors are possible). The structure was
designed to simplify certain routine
retrievals expected as part of the CEMS
process.
Data that create a nonzero channel number
must be entered only when a corresponding
emission point already exists on the CEMSS
Masterfile. Nonzero channels for Point
‘0000’ are not permitted, because they
have no meaning in the CEMSS.
For data referred to specific monitors,
the following rules apply:
Column 24 identifies the pollutant being monitored and is numeric
with the following allowable codes:
1 = Opacity (PT)
2 = SO 2 (sulfur dioxide)
3 = NOX (oxides of nitrogen)
4 = Diluent (oxygen (02) or carbon
dioxide (C0 2 )
5 = HC (hydrocarbons)
6 TRS (total reduced sulfur)
7 = H2S (hydrogen disulfide)
8 CO (carbon monoxide)
9 =.Coal Sampling and Analysis
Column 25 indicates the type of data being entered, is
numeric, and is limited to the following codes:
1 - Monitor data
9 — Excess emission reports (EER)
data or
percent reduction (% RDX) data
Column 26
a. If column 25 = 1, column 26 represents a particular
monitor in a multiple monitor installation and is
numeric. For example, if a unit has two opacity monitors
on the same emission point, the first would be coded “111”
and the second coded as “112.”
b. If column 25 = 9, column 26 indicates the type of emission
data being entered/present in CEMS, is numeric, and, at
present. is limited to the following codes:
5—15
-------
5= Percent reduction(% RDX) for SO 2 and NO
9 Excess emission reports (EER) for all pollutants.
Point Number/Channel Number (PTNO/CHAN) coding examples are
PTNO
PRDS
•
0500
OPAC EER;
BOILERS 1 & 2
CEMS
CDS
PTNO
PRDS
0501 S02 EER;
BOILERS 1 & 2
A source sends in three EERs (opacity, SO 2 , and
NOR) per quarter for two boilers venting to one
stack. There are two opacity monitors, one on
each duct• to the stack. A combined SO 2 /NO
monitor and COz monitor are installed on the
stack. In CDS there will be three PTNOs
established for tracking this CEM/EER data in CEMS:
... .
ill -
Opacity monitor on one duct
112 —
Opacity monitor on other duct
199 —
Opacity EER for Boilers 1 & 2
CEMS .
CH N
211 —
SO 2 monitor on stack
295—
%S 2 RDX
299—
SO 2 EER for Boilers *1 & 2 .
411 -
CO 2 monitor on stack
CEMS.
CHAN
0502
NOX
EER;
311 — NO
monitor
on stack
BOILERS1&2
395-%N 2
RDX
.
399 — NO
EER for
Boilers
*1 & 2
.
411 — CO 2
monitor
in stack
.
A source sends in four EERs for two separate
boilers, one of which is subject to SUBPART Da.
One boiler (Boiler *1) has only an opacity monitor
units stack. The SUBPART Da boiler (Boiler *2)
has two opacity monitors: one on each section of.
the split breeching between the lectrostatic
precipitator (ESP) and the flue gas
desulfurization (FGD) unit. Two SO 2 monitors
are present: one on the stack and the other
monitoring the two inlet ducts to the FGD. One
CO 2 monitor is on the stack and the other on the
inlet to the. ESP. In CDS, there will be four
emission points coded: .
follows
Example 1:
CEMS
CEMS
PTNO
CDS
PRDS
Example 2 :
5—15.1
-------
CEMS
PTNO
.0500
CEMS
PRDS
0501
Cfl4S
PTNO
CEMS
PTNO
CDS
PRDS
CEMS.
CHAN
111
-.
Opacity
monitor
on boiler *1
199
—
Opacity
EER
for
Boiler l
OPAC EER;
BOILER ;l
cDs
PRDS
OPAC EER;
BOILER *2
CDS
PRDS
0502 S02 EER:
BOILER *2
.. CEMS
.
.
CHAN
.
.
.
111 — Opacity monitor, boiler
ductA
*2,
,
112 — Opacity monitor, boiler
ductB ..
*2,
199 — Opacity EER Boiler *2
.
CEMS. .
:c
.
.
211 — SO 2 monitor, boiler *2,
stack
212 — SO 2 monitor, boiler *2,
ducts .
295 — SO 2 % reduction report
299 — SO 2 EER, boiler *2
411 — CO 2 monitor, boiler *2
stack
CEMS
CHAN
CDS
PRDS
0503 NOX EER;
BOILER #2
311 — NO monitor on Boiler *2,
stack
312 — NO monitor on Boiler *2,
ESP duct
395 — NO % reduction report
399 - NO EER for Boiler *2
411 — CO 2 monitor on boiler #2
stack
Data Dictionary
5—15.2
-------
dioxide monitors and one opacity monitor.
Also, assume unit’ 3 has only an opacity
monitor. The correct channé]. codes wou
be:
Monitor Manu-
facturer (MANF)
Monitor Model
Number, (MCDL)
Monitor Serial
Number (SERL)
Update Code A.3—lO
(UPDT)
C 4SS User’s
Guide
Date Field Number
CEMS Enforcement A.l-l.
Agency (AGCY)
All the channel numbers may be assigned at
the user’s discretion, , but should be
assigned sequentially in order to ensure,
correctness. When adding , new channel
numbers for a point. request a Souráe Data
Report or a Quick Look Report to make sure
that the new channel number does not
already exist on the Masterfile.
These three alphabetic fields ‘identify the
manufacturer, ‘serial ,‘number, and model
number of the principal components ‘of the
monitoring unit. Obtain this information
either from the EER or, from data, provided
by the !lan Manager. ,
Code an ‘N’ in column ‘80 if Card 51 is
new channel number on the CEMSS Masterfile;
code a ‘C’ if information is being changed
on an existing channel. Because basic
monitor information usually is constant
throughout the history of the source. Card
51 should only be entered during the
initial coding for that particular source.
Card 52
Coding Considerations
This one—digit code indicates the Federal
or state agency with enforcement
jurisdiction for the continuous emission
monitor at the facility. ,The valid codes
1 - EPA-HEADQTRS
2 - EPA-REGION
3 — STATE
4 — LOCAL.
ill
121
131
231
212
221
Unit 1, ‘1 opacity monitor
Unit 2. 1 opacity monitor
‘Unit 3. 1 opacity monitor
Unit 3. SO 2 monitor *1
‘Unit 1, SOz monitor *2
Unit 2, SO 2 monitor *1.
A.1-9
A. 1—10
A.1—l3
are:
5—16
-------
Data Field
guirement Code
.(REQT)
CEMSS User’s
Guide
Number
A. 1—11
Card 52
Coding Considerations
Code the Clean Air Act regulation requiring
the continuous monitoring (NSPS or SIPS).
In some cases a facility may be instructed
to install Continuous monitoring equipment
by court order by a 114 Letter. In this
case code either the air program (PSD) or
enforcement action (ENF). If this data
element cannot be filled by examining the
EER, check the air program code listed in
CDS for that facility. The valid codes
are:
1 — SIP — STATE 4PLEMENTATIQN PLAN
3 - ENF - ENFORCEMENT ACTION
5—OTHER
6 - PSD — PREVENTION OF SIGNIFICANT
DETERMINATION
9 - NSPS - NEW SOURCE PERFORMANCE
STANDARD.
Permissible
nission Limit
(D IS)
Installation
Date (MIND)
Performance
Specification
Test Date
(PSTD)
Performance
Specification
Test Status
(PSTS)
A. 1—17
A.1-8
A.1—19
Code the units andvalues noted by the CEMS
regulation number. Examples for a fossil—
fuel power plant are:
0.3 LBS/MBTU NOX
20% OPAC/6 MIN PERD.
Some of the regulated values for CEMS
sources can be found in Appendix C or Pate
(1983).
Code the first two digits with the year the
monitor was installed and the last two
digits with the month of installation
(01—12).
This four—digit field indicates the date
or year/month format that the latest PST
occurred. The first PST is run within 60
days after achieving the maximum
production rate or 180 days after the
initial startup. Afterwards, a PST occurs
if required by the Administrator under
Section 114 of the Clean Air Act (Pate
1983).
Code the results (PASS/FAIL) of the latest
PST. The Update Program uses this data
field to keep running total of PST passes
and PST fails.
5—17
-------
CE?ISS User’s
Guide Card 52
Data Field Number Coding Considerations
Certification A.l—3 This six—digit field indicates in
Date (CERF) month/day/year format the date that the
monitor was certified.
Update Code A.3—l0 Code a ‘N’ in column 80 if Card 52 is
(UPDT) adding a new emission point to the
Masterfile and being entered
simultaneously with Card 51. If Card 52
is being entered after Card 51 was
previously updated, code a ‘C’ in column
80.
All data elements on Card 52 should only
be entered during the initial update
except PST date and PST status, which are
updated after every PST.
C 4SS User’s
Guide Card 70
Data. Field Number Coding Considerations
Emission Point A.1—7 Each action must be associated with the
Number (PTNO) corresponding four—digit emission poi’-
number on Card 51.
Action Number A.2—7 When adding numerous actions during the
(ANUM) same Update Cycle, code the action numbers
in chronological order 0001—0098. If this
is the facility’s first entry into the
CEMSS, start numbering at 0001. To add
additional actions to an existing
facility, examine a CDS/CEMSS retrieval
and code the actions in sequential order,
starting from the last action entered. If
you are adding a new action, you may use
action number 0099 to place the action on
the Masterfile. The action number 0099
will automatically assign the next
available action number in CDS/C 2 ’1SS.
New action numbers cannot be added to the
Masterfile unless the channel for that
action has been added to the Masterfile
during a previous CEMSS Update Cycle.
Each action number must be associated with
a specific channel except an M3 action,
which is associated with a specific CDS
emission point.
5—18
-------
CEMSS User’s
Guide Card 70
___ Number ___ ,__Codinçpn erations
hañnelNumber A.1—4 Enter the corresponding three-digit channel
( HAN) number of the monitor for which the
particular action (Ml , M2, M$, MA, etc.)
is being taken. Enter ‘000’ for an action
type M3.
Action Type A.2—]. The two—character alphanumeric code
(ATPE) outlines the history of the continuous
emissions monitors at a facility. The CDS
Action Table is accessed to determine the
validity of each region’s C S actions.
Each region is responsible for defining
the C 4S actions to be tracked by the
C 4SS. Table 5—i is the current list of
C 4S actions by region.
The national DBC, in coordination with TRC
maintains the CDS/CEMS Action Table.
Regions must obtain clearance from both
before changes are made to maintain
national consistency, at least with the
CEMS actions. .
All M actions (except M3) will only appear
on the CEMSs Masterfile. They can only be
retrieved by a CEMSS Retrieval and entered
by a CEMSS Edit Program. A Card 70 with
action type M3 should be submitted for
each EER received. Action type M3 is
transferred to the CDS Masterfile as an
emission point action. For this reason,
be careful if two or more CEMSS exist
under one CDS emission point. In that
case, only one M3 action should be entered
to indicate that all EERs have been
submitted for, all monitors existing at
that CDS emission point.
Date Achieved A.2—2 The six—digit data field displays the date
(DTAC) an action is performed or completed. The
date is given in month, day, and year
format. The year must be >60, the month
between 01—12, and the day between 01—31.
When recording date achieved, refer to the
EPA receiving stamp on the document.
5—19
-------
TABLE 5-1
ACTION TYPES
ACTION SHORT LONG
TYPES DESCRIPTION DESCRIPTION
NOTICE CM TEST
adS EVAL RSLT
SUB QRTLY RPT
PER TST RSLT
adS EVAL CONDUCT
NOT PER? TST DT
PER TST EPA RQD
PER TST WAIVED
CON MON INSP
NOTICE CM TEST
SUBMIT CM RESLT
EER SUBMISSION
CM TEST RESULTS
EPA MEET’W/S&C
• EPA MEET W/COM
EPA MEET W/ST
XS E24ISSN’ RPT
EPA OBSRV ’ PST
76 ST OBSRV PST
77 C 24S PST
CM REL ACC TST
NOTICE CM TEST
SUBMIT CM RESLT
EER SUBMISSION
CM TEST RESULTS
INSTALL DATE
PLAN SUBMIT
CM UP/MAL DUR
ad UP/MAL REPT
AWRD ad CONTRCT
BEGIN CM INSTAL
CCMPLZrE ad iws
COMPLETE Q4 CER
GAS MON SHIP?IT
OP MON SHIP D’
ad INSPECTION
NOTICE CM TEST
M2 SUBMIT CM RESLT
M3 EER SUBMISSION
REGIONO1
Mi
M2
M3
M4
M5
M6
P 17
•
M8
M9
REGION 02
Mi
M2
P13
P14
REGION: 03
MB
.
MC
MS
.
74’
75
SPECIFICATION
REGION 04
78
Mi
M2
M3
P14
P15
P16
M8
P19
Ni
N2
N3
.
N4
N5
N6
N7
REGION 05
H]
NOTIFICATION OF CM SPECIFICATION TEST DATI
adS EVALUATION RESULTS FURNISHED
SUBMISSION OF QUARTERLY REP
PERFORMANCE TEST RESULTS
Q4S EVALUATION CONDUCTED (60.13)
NOTIFICATION OF PERFORMANCE TESTING
PERFORMANCE TEST EPA REQUIRED
PERFORMANCE TEST WAIVED
COMPLIANCE MONITORING INSPECTION
NOTIFICATION 0? CM SPECIFICATION TEST DATJ
ECECUTION AND SUBMISSION OF CM SPEC TEST
RESULT
EER SUBMISSION
CMSYST 4 TEST RESULTS
EPA MEETING WITH SATE AND COMPANY
EPA MEETING WITH COMPANY
EPA MEETING WITH STATE
E CCESS 4ISSION REPORT
EPA OBSERVED CE24S PERFORMANC
TEST
STATE OBSERVED CEMS PERFORMANCE
SPECIFICATION TEST
CEMS PERFORMANCE SPECIFICATION TEST
(UNOBSERVED)
CE2IS RELATIVE ACCURACY TEST
NOTIFICATION OF CM SPECIFICATION TEST DAT
DCECUTION AND SUBMISSION OF CM SPEC
TEST RESULT
EER SUBMISSION
CM SYSTEM TEST RESULTS
INSTALLATION DATE
PLAN SUBMITTED
CM UPSET/MALFUNCTION DURATION
CM UPSET/MALFUNCTION REPORT
AWARD MONITOR CONTRACT
BEGIN MONITOR INSTALLATION
COMPLETE’ MONITOR INSTALLATION
COMPLETE MONITOR CERTIFICATION TESTS
GAS MONITOR SHIPMflJT
OPACITY MONITOR SHIPMENT DATE
CM INSPECTION
MODIFICATION OF ad SPECIFICATION TEST
DATE
DCECT.rrION AND SUBMISSION OF CM SPEC TEST
• RESULT
EER SUBMISSION
5—20
-------
TABLE 5—1
ACTION
TYPES
SHORT
pEscRIP’rIoN
ACTION TYPES (Continued)
CM TEST RESULTS
MS LTR OF INQUIRY
P 16 LTR NONCCMPL
Mi PER APPLICATION
P18 PER RELEASE
M l NOTICE CM TEST
M2 SUBMIT CM RESLT
P13 EER SUBMISSION
P14 CM TEST RESULTS
M5 REV C 4S TST RES
P16 REV CDiS DATA
Mi CEMS AUDIT
Ml NOTICE CEMS TEST
P12 DCC CD4S SPEC TS
P13 EER SUBMISSION
P14 CP24SSYSTESTAUDIT
MS SUB CE2IS SPEC TR
QA EVAL OF EER
CE24S PERF AUDIT
NOT CONDUCT PST
D C OF PST
ZER SUBMISSION
C 4S SYS AUDIT
PST RPT RECVD
AP AIR QA CORD
M7 NOT PST SCHEDULE
M8 PST REV COMPLETE
P19 TRAN PST RCZ4 AP
Ml NOTICE CM TEST
P12 SUBMIT CM RESLT
P13 EER SUBMISSION
P 14 CM TEST RESULTS
CM SYSTEM TEST RESULTS
LETTER OF INQUIRY
LETTER OF NONCOMPLIANCE
PERMIT APPLICATION
PERMIT RELEASE
NOTIFICATION OF CM SPECIFICATION TEST DATE
DCECUTION AND SUBMISSION OF CM SPEC TEST
RESULT
EER SUBMISSION
Q4SYSTEM TEST RESULTS
REVIEW OF CEMS TEST RESULTS
REVIEW CD S DATA
CEMS AUDIT
NOTIFICATION OF CM SPECIFICATION TEST DATE
DCECUTION OF CEMS SPECIFICATION TEST
EER SUBMISSION
CEMS SYSTEM TEST AUDIT
SUBMISSION OF CEMS SPECIFICATION TEST
RESULTS
QA EVALUATION OF EER
CE2 1S PERFORMANCE AUDIT
NOTICE OF INTENT TO CONDUCT PST
EXECUTION OF PST
EER RECEIVED BY AP
CE74S SYSTE2I TEST AUDIT
PST REPORT RECEIVED
APPROVAL AIR QA CORD PST PROTOCOL
AND OP QA PLAN
NOTICE (30 DAY MINIMUM) OF PST SCHEDULE
PST REPORT REVIEW COMPLETE
TRANSMITTAL OF PST RECO JDATIONS TO ,AP
NOTIFICATION OF CM SPECIFICATION TEST DATE
EXECUTION AND SUBMISSION OF CM SPEC TEST
RESULT
EER SUBMISSION
CHSYSTE24 TEST RESULTS
FILE REFERRED TO ATB
NOTIFICATION OF CM SPECIFICATION TEST DATE
• EXECUTION AND SUBMISSION OF CM SPEC TEST
RESULT
• SUBMISSION
Q4SYSTD4 TEST RESULTS
LONG
DESCRIPTION
REGION 06
REGION 07
REGION 08
REGION 09
REGION 10
MA
MO
Ml
P12
M3
P14
M5
P16
P13
P14
MS
Ml
M2
EER SUBMISSION
CM TEST. RESULTS
REFERRED TO ATE
NOTICE CM TEST
SUBMIT CM RESLT
5—21
-------
• CEMSS User’s
Guide Card 70
Data Field Number Coding Considerations
Date Scheduled A.2—3 The six—digit code gives the date on which
(DTSC) an action is scheduled to be performed or
completed in month, day, and year format.
EER submissions (M3) are scheduled to be
submitted 30 days after the end of each
quarter.
Quarterly reports are due on the following
dates:
Quarter Scheduled Due Date
05/01
2 07/31
3 10/30
4 01/31
Staff Code The three—digit code indicated the staff
(PERA) member involved in completing the action
(use CDS Staff Codes).
Results Code • The two digit data field indicates whether
(STAC) an action has been carried out. The
results code may also indicate the n
logical action. It does not, howevt..
infer the success of the action. Each
action entered into the CEMSs need not
have a results code. Use the CEMS Results
Code Table to determine a valid results
code. Changes to the CEMS Results Codes
must be cleared through TRC and the
national DBC. Table 5—2 is the current
list of CEMS Results Codes.
Update Code A.3-lO Enter an ‘N’ for a new action record not
(UPDA) existing on the CEMSS Masterfile, and a
‘C’ to change a data element for a record
- already on file. Enter an ‘A’ On a card
10 on]y to add a new source to C 4S from
CDS.
5.3.6 Card Type 71
Card Type 71 is used to add EER summary data. One record will be
generated from each EER, recording seven of the nine basic reasons for excess
emissions. • •
5—22
-------
TABLE 5-2
RESULTS CODES
RESULTS RESULTS
CODES DESCRIPTION
REGION 01 MA QEER ADEQUATE
MC IN COMPLIANCE
MD CM RECERTIF REQ
MI QEER INADEQUATE
MO NUMEROUS SHUTDN
MR RETEST REQ
MU UNKNOWN CMST
MV IN VIOLATION
REGION 02 MA QEER ADEQUATE
• MC IN COMPLIANCE
MD CM RECERTIF REQ
MI QEER INADEQUATE
MO NUMEROUS SHUTDN
MR RETEST REQ
• MU UNKNOWN CMST
MV INVIOLATION
REGION 03 MA QEER ADEQUATE
MC IN COMPLIANCE
MD CM RECERTIF REQ
MI QEER INADEQUATE
MO NUMEROUS SHUTDN
MR RETEST REQ
MU UNKNOWN CMST
MV IN VIOLATION
M l INCREMENTS MET
M2 ICRMTS NOT MET
REGION 04 MA QEER ADEQUATE
MC INCOMPL lANCE
MD CM RECERTIF REQ
MI QEER INADEQUATE
MO NUMEROUS SHUTDN
MR RETEST REQ
MU UNKNOWN CZ4ST
MV INVIOLATION
REGION 05 MA QEER ADEQUATE
MC IN COMPLIANCE
• MD CM RECERTIF REQ
• MI QEER INADEQUATE
MO NUMEROUS SH TrDN
MR RETEST REQ
• MU INKNOWN O4ST
MV IN VIOLATION
REGION 06 MA QEER ADEQUATE
ME SEE STAFF PERSON
MC IN COMPLIANCE
MD • • CM RECERTIF REQ
5—23
-------
TABLE 5-2
RESULTS CODES (Continued)
ME IN VIOL-LEGAL
IN VIOL-STATE
MG IN VIOL—FILE
MG IN COMP-LEGAL
MR IN COMP-LEGAL
MI QEER INADEQUATE
MJ IN COMP-STATE
• IN COMP-FILE
UNKNOWN-LEGAL
MR UNKNOWN-STATE
MR UNKNOWN-FILE
MO NUMEROUS SHUTDN
MP RETURNED TO S&A
MR RETEST REQ
MS ADDL INFO REQ
MA QEER ADEQUATE
MC IN COMPLIANCE
MD CM RECERTIF REQ
MI QEER INADEQUATE
MO NUMEROUS SHIJTDN
MR RETEST REQ
MU UNKNOWN CMST
MV IN VIOLATION
• MA QEER ADEQUATE
MC IN COMPLIANCE
MD CM RECERTIF REQ
MI QEER INADEQUATE
MO NUMEROUS SHUTDN
MR RETEST REQ
MU UNKNOWN CMST
MV IN VIOLATION
MA QEER ADEQUATE
MC IN COMPLIANCE
MD CM RECERTIF REQ
1*’ FAIL
MI QEER INADEQUATE
MO NUMEROUS SHUTDN
MP PASS
MR RETEST REQ
MU UNKNOWN CMST
MV IN VIOLATION
MA QEER ADEQUATE
MC IN COMPLIANCE
MD CM RECERTIF REQ
MI QEER INADEQUATE
MO NUMEROUS SHUTDN
RESULTS
CODES
RESULTS
DESCRIPTION
REGION 07
REGION 08
REGION 08
REGION 09
5—24
-------
TABLE 5-2
RESULTS CODES (Continued)
MR RETEST REQ
MU UNKNOWN CMST
MV IN VIOLATION
REGION 10 MA QEER ADEQUATE
MC IN COMPLIANCE
MD CM RECERTIF REQ
MI QEER INADEQUATE
MO NUMEROUS SHUTDN
MR RETEST REQ
MU UNKNOWN CMST
MV IN VIOLATION
5—25
-------
CEMSS User’s
Guide Card 71
Data Field Number Coding Considerations
Emission Point A.l—7 Each action must be associated with the
Number (PTNO) corresponding four—digit Emission Point
Number on Card 51.
Quarter Date A.2—8 Enter in the four—digit field in year/
(Calendar Year) quarter format the ,quarter for which the
EER was submitted.
Quarter Time Period
01 01/01 — 03/31
02 04/01 — 06/30
03 07/01 — 09/30
04 10/01 ‘— 12/31
Time Period Code :A .244 Enter either ‘M’ (minutes) or the
(Time) appropriate alphabetic time period code:
‘A’ (6 minute period).
‘B’ (15 minute period),
‘C’ (30 minute period),
‘D’ (1 hour period — 60 minutes),
‘E’ (2 hour period — 120 minutes),
‘F’ (3 hour period — 180 minutes).
‘G’ (24 hour period 1440 minutes)
or ‘M’ (minutes)
depending on how the following excess
emissions information has been
summarized. The definition of an excess
emission period is defined in the CEMS
regulations (see either Appendix A, B, and
C or Pate (1983)).
Total Source A.2—47 Code the time (periods or minutes) that
Operating the source was operating during the quarter
Time in question. This information is either
(OPER) given the EER or derived by subtracting
the time the unit or process was shut down
or off line (nonoperational time) from the
total time in the quarter. Although this
information is not required to be coded,
elimination will result in inaccurate
monitor availability, monitored operating
source compliance, and overall operating
source compliance. Maximum quarter times
follow:
5—26
-------
Quarter Minutes _____________ ___________ ___________
01 129,600
(leap year) 01 131,040
02 131.040
03 131,040
132,480
The next eight data elements record seven of the nine basic reasons for
quarterly excess emissions and •the number of incidents of excess emission.
For each reason,: enter the number of excess emission periods or minutes in a
right—justified format (see Figure 5—6). If none are reported for a
particular reason, leave it blank. The number of total excess emission
periods is determined by adding the nine basic reasons. For this reason, be
sure to. categorize every excess emission period or minutes during the quarter
into one of the .nine basic reason categories.
Card 71
______________ _______ - Coding Considerations
Enter the number of excess emission periods
or minutes due to startup or shutdown.
Enter the number of excess emission periods
or minutes due to cleaning or soot blowing.
Enter the number of excess emission
periods or minutes due to an unknown
reason.
Enter the total number of excess emission
periods or minutes due to a unit/control
equipment malfunctions.
Enter the number of excess emission periods.
or minutes due to control equipment:
malfunctions that one unacceptable excess
emissions, as deemed by theengineers.
CEMSS User’s
Guide
Data Field Number
Card 71
Coding Considerations
6—mm Periods 1-h Periods 3-h Periods
21,600 2,160 720
21,840 2,1e4 72.8
21,840 2,184 728
33,080 2,208 . 736
33,080 2,208 736
04
CEMSS User’s
Guide
Data Field Number
Start up/Shut A.2-23
down (STAR)
Cleaning/Soot A.2—13
Blowing (SOOT)
Unknown (EQUN) A.2—25
Control Equipment A.2-15
Failure — Total
(EQPT)
Control Equipment A.2-17
Unacceptable
(optional)(EQPU)
5—27
-------
I i iI% ION ( 1 5
ron., in, V
II 13 I I IU 9 30212133
os_p 000051
lnIS.IflN (a••
I•llI . . I nfl ,.wI
,, 12
2I
20
—
CONTINUOUS E SSION MONITORING
INPUT CODING SHEET
USE (API) IYI’I $0 DIlLY Wiltil ADDING Ofl 01(11 lUG A SOURCE _______
3,13iI 4 33136 311 513,140(4 ‘14314 l1i141P71I,t1 1 1slso1s,Is.1s j oI , e lAA 6 IL.I7d7ih I7 317417117617 ‘(‘SI’, 50
3,
I I I 1 I I I I I . I I I I I I
* Il ,ImI KI tS
(In I Ein (l uI l l
‘ “I’0 ‘Wt “0
p.,.i, u.n.i .
E M11’1
¶tft Ir*’M M91?
:‘i’il
I TNUSUS si ,un uI c II$ *((IlI pu sail
N 1UI0W LIMIT
u•IIfS(*Il
I_ li if
IM,csl0hI acuoa (AJØ (NN11I I
rot.., H 0 ‘ 11W 10 I
16 l ;• 93 0j2 1 I I’ 2413 136127
9L5o312I0_I4 7100101
(app rKa ,uifI
“NW 10
2930(3133 333 33 3ej37(3$ 39 41 4 4 45 49 3(1(11132 “1’ I i l 1715 $96 1 I I 36344 S [ 4a I l eSIS, 70(7. 74731
[ I I I lilT 11 T _____ I I I
17
lSNll IOINWNIS
37 2S
i WoIiil ii a,Ii 1iI 1 { 3 s 3 (44 4sIiRifriI4447I4SH 1ií111 4(1 SIS61i kiIS9I6OIè Ik o1l 441. S [ 6 oI 6 l1iIe ‘ ,1i 3l 73(74(7317417 7(7 sI, 9 IC
II
L “I3°
II
I I I I 11111111111 11111 .J I _ I I I I I I J_I_L_l......I...i Ill _ I .
1 i::r 1 KNll’0p
u u u
III
3113113313
iiI3 6 1 3 13
4j3k 4 I 4519 ‘ 64 ‘i
i ,sIis I7i
7 isI’i
950
•I i’(.i;I”i
•I.’ I•”I I I1
tOl ( %O ’ (l
lI&lluC 1119
i 1 WIIS0 l*
. I
1I3S 39
33133 24 1311361,2 1 139 13 ________
Ii n i i i
II
RIASIIII roy
(IlS ’SlN ’
aiI p,. ’aI ’a
. 1 :44 I 43 43
1/ 7
I•.•i •I .i I
3IoI d I91l
t Ik1
II
‘a?
A
IXCESS LHISSIOI
v.al Vi I I
ii’r’r 3 ii’i i ___
‘I.,
, 1—
III
1
SC
IN
L
(0.1 101
I I7jI 19NI
1111 11 111
ccutw.. 17 IJIMUP?
U5*CCIPIAII.1
(Orf 1011.1.) IlIlil
, us pW01 .
IMACCIP?flLI
(01 10 1AL)
U,.
‘ m c ’,
II
I 113
( 1 1U 101 1 1
NO
‘WI
•Pl i nftM V .
1119’ 110
II(Ifl mu
I ll.,, .,
•0u 1 1m 1 I
Plt!.! : o .u_ — —
REASON E
I(9 1719n1
IW I (uiQU -
lIft 110111 IOU (JUWNI 1111
• I ‘ ‘ . ‘r n
•U Il’’ I mcni tOq l (’
— 4SSW$U(I 1. __ !!.uui I I l ( •.I l
ui,
lEtS
w I
46 14 714 1 149 (S( sti S3 1S3 1 54 1 55136b 71 5SIS9I60I6hI43l63I64te st .olo ,Ies a ,( c4 t I72I, 31741’ S 176 1 ‘.‘I”I” •
‘. 1’ II Onflil, ‘lull Iprinhi
I P 5
V n i
14 ,j .J3012l 11 [ i3 4J , iji ,
0 0 )O J [ 110 III
I l T 1V f
in IS’ IIin
‘01111 Nfl
I4 [ 13 Sb
I,
I. ’.,
“lW
7 3JiI
o Ic
0101010
I OIUIIIS sill
tniccin .i I (IM(NO”I
Ff1 11, lIVI
VS I 1)11
‘ ,I’si ’ F 1 i 119I!I
o [ aoj3 A/LOII
QiUIlN Oil.
niaaltal ((aulimili
o •, I o.
‘41” 161 ,7 ‘;pH;
) I5 0j3 EIôIi
,2I I 3412513627
iJ aJiI ? ______
33
0 fliP
II iS lb IF iS!,’ 4 7011 I 13’
O5o3 I1O !8
4343
I i
44
45
i I I I —i 111111111 112111111 I
MilaN (IPIWuiS
Figure 5—6. CEMS Coding Sheet with New Data
5—28
-------
Card 71
Coding Considerations
Enter the total number of excess emission
periods or minutes due to process problems.
Enter the total number of excess emission
periods or minutes due to process problems
that are unacceptable excess emissions, as
deemed by the engineers.
Enter the total number of incidents of
excess emissions.
5.3.7 Card Type 72
Card Type 72 is used to add the remaining EER summary data. A card type
71 must be entered for each card. 72. The first two data elements are used for
the last two of the basic nine reasons for excess emissions.
The remaining six data elements are used to classify the quarterly monitor
down—time into five basic reasons and to record the number of incidents of
nitor downtime above. For each reason, enter the number of periods or
minutes the monitor was not operating. The data must be entered in a
right—justified format (see Figure 5—6).
If none are reported for a particular reason, leave it blank. The total
monitor down-time is calculated by adding the five basic reasons. Therefore,
be sure to categorize every monitor down—period or minute into one of the five
basic reason categories.
C 74SS User’s
Guide Card 72
Data Field Number Coding Considerations
Fuel Problems A.2—27 Enter the number of excess emission periods
(FUEL) or minutes due to fuel problems.
Other Known A.2—29 Enter the number of excess emission periods
Excess Emissions or minutes due to other known reasons.
(EEOT)
CE SS User’s
Guide
Data Field Number
ocess Problems A.2—l9
Total (PROC)
Process Problems A.2—2l
Unacceptable
( ptional)(PRUN)
Number of Incidents A.2—31
of Excess Emissions
(EEIN)
5—29
-------
CEMSS User’s
Guide Card 72
Data Field Number — Coding Cor.siderations
Monitor ‘Equipment A.2-35 Enter the number of periods or minutes the
Malfunction monitor did not operate due to a’ monitor
(MOEQ) equipment malfunction while the source’was
operating.
Nonmonitor Equip- A.2—37 Enter the number of periods or minutes the
ment Malfunction monitor did not operate due to a monitor
(NMEQ) equipment malfunction while the source was
operating.
Calibration (CALl) A.2—33 Enter the number of periods or minutes the
(Quality Assurance) monitor did not operate due to calibration
while the source was operating.
Unknown (MOUN) A.2—41 Enter the number of periods or minutes the
monitor did not operate due to an unknown
reason while the source was operating.
Other, Known Monitor A.2—39 Enter the number of periods or minutes the
Downtime (MOOT) monitor did not operate due to, other known
reasons.’
Number of Incidents A.2—43 Enter the total number of incidents of
of Monitor monitor downtime.
Downtime (MOIN)
In addition, Update Code must be properly
entered. Enter an ‘N’ for a new record
that does not exist on the C 4SS file, a
‘C’ to change an element already on file,
and a ‘D’ to delete an existing quarterly
excess emission summary.
5.3.8 Card Type 80
Card Type 80 is a comment card used to add additional information about an
action that is different from the information supplied by the data elements on
Card Type 70 or Card Types 71 and 72. There are 10 comment line numbers
available on Card Type 80; up to 10 comments may be used to add information.
New action comments may be processed at the same time that a new action record
is added to the Masterfile. However, an action comment cannot be added to the
system unless there’is a corresponding action record already in the Masterfil
5—30’
-------
Code columns 18—21 with the corresponding action number (Card 70) or
quarter date (Card 71, 72) to which the action comment should be attached.
Code comment ‘ information in columns 28—79. Assign comment line numbers
(column 27) starting sequentially with number 1 or 0. 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.
Use the action comments especially when existing reasons do not fully
explain a specific reason why excess emissions have occurred or’ why a monitor
is down. An example of a completed coding sheet’is shown in Figure 5—6.
5.4 Changing Data on the CEMS Masterfile
Once a record has been added or copied to the CEMSS Masterfile by, the
update Cycle, data on the Masterfile record can be changed in subsequent
Jpdate Cycles by using input transactions with an Update Code ‘C’ (M3 action
types can be changed only through a CDS edit).
During a given Update Cycle, transactions with the same record identifier
(region, state, county. source, point, action numbers, card type, and channel
number) are applied in Update Code order. The Update will reject a change
transaction if a delete or a new transaction is being applied for the same
card type during the same .Update Cycle. However, the Update will process
multiple changes for an existing Masterfile record. 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 11—26 and 80 must be coded when preparing a change
ransactjon. However, the data elements in columns 1—26 cannot be changed by
5—31
-------
processing as a change transaction. If transactions with incorrect state.
county. source, point, action, or channel numbers have been added to the CEZ
Masterfile, those records in error can be deleted and the corrections
reentered with an Update Code ‘N’, or the user can contact TRC to have the
data elements in columns 1-26 changed by the CEMS SWAP programs. When any of
the data elements in columns 24-70 need to be changed, only the data element
that needs changing is coded on the input coding sheet.
The following steps should be performed for a change transaction:
1. Request a Source Data or Quick Look Report for that facility to
determine what data values exist on the Masterfile.
2. Decide what data elements need to be changed, and decide what card
type should be used.
3. Code columns 1—26 on a coding sheet. Code a ‘C’ in column 80.
4. Code only those data elements that 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 entered and submit the transaction records to
the CEMSS Edit Program or use the WYLBUR Interactive data-entry
technique.
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 24—70 of Card Types 51, 52, 71, 72 or columns 27—70 can
be blanked out be placing one or more asterisks (*) in the data
element that is to be eliminated. An asterisk will remove only
the data element to be blanked out and will not change any other
data elements on the Masterfile record for that card type. On the
Card 70, an asterisk on “date scheduled” or on “date achieved”
will zero—fill the data element, because these data elements
cannot be blanked. An asterisk cannot be used to change any data
elements in card columns 1—21 and 24—26; if a record with an
incorrect state, county, source number, point, channel, or action
number has been placed on the Masterfile, the incorrect data must
either be deleted with an Update code ‘D; and the corrected cards
reentered with an Update Code’N’. or the error must be reported to
TRC for correcting through the CEMS SWAP.
Because 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.
5—32
-------
Figure 5—7 is an example of change transactions for Cards 51, 52. 70. 71,
and 72.
On Card 51 the monitor model was coded incorrectly when this source was
initially entered, and the proper model number is being reentered.
Because many PSTs can occur during the history of a source, the data
elements PST Date, PST Status, and PST Status, and PST Report Date will be
changed periodically. In this case, a recent PST was conducted successfully
on 2/15/81. The changes reflecting the new PST are shown in Figure 5—7 on
Card 5—2. Also the date achieved was incorrectly coded and is being modified
with a change command on Card 70.
The SOOT (cleaning/soot blowing) was coded incorrectly for that data
element on Card 71. An asterisk is employed to delete the data element from
the CEMSS Masterfile. Finally, the number of incidents of Monitor Down Time
was coded incorrectly for that data element on Card 72. The correct value is
ing entered to replace the incorrect value on the CEMSS Masterfile.
5.5 WYLBUR Interactive Data Entry Technique
In some cases, the amount of CEMS data entry work may not justify the
creation of a data entry routine on the regional or state minicomputer. For
those users, a WILBUR Interactive data entry technique is available.
The interactive features are as follows:
• Screen prompting for input of Card Types 10, 51, 52, 60, 70, 71,
72, and 80.
• Edit capabilities
— Internal edits
— After each card is entered
— After all cards are entered
• Default operating times
• Restart capability if dropped from NCC
5—33
-------
• Capability to add to or change an already created WYLBUR file
• Save data on WYLBUR file
• Automatic live edit and duii my edit capabilities
• Automatic assigning of proper edit JCL (USER ID, account, box).
To enter data using the WYLBtJR Interactive technique. perform the following.
An example of data entry for a 51 card is shown in Figure 5—8.
1. Sign on to the appropriate user ID and account.
2. Type CEMSINPUT
3. the screen prompting will begin.
5—34
-------
Figure 5—7. CEMS Coding Sheet with Change Transactions
5—35
“1 1 (IP’7II I ..IVWI I lurmi,
c I1 oWI;
CONTINUOUS E 1 1 iSSION MONITORING
INPUT CODING SHEET
USE CARl) i rr Ii) WILY WHUI ADDIIIG Of! orttttnr. A SOuRCE
(A,,
i i i I’_ ______
o o oI J M 1 o ___ __
up,
•11N, All
,s , Jsi “i!! ,4,,
°S i3 010010 51’ ___ ___ ___ _____ _____ ___ ___
IMuccinhl ( Au,
Ifl l I lt urn
4 ‘1g. ,, ii _ i j _‘i_ _________________________
Oj Ol0I05I2 ____________________ ___ ___ ___ _____________
—
rnhuuu An
s [ sI ; ‘i j “ r 2 r : i1Tn rf P191919 4 11191TM11’ rM M911. 4 1 ‘ Ii :
‘ H
1 l
91
1
t h 1
I2i
uuwuIt M I(IfS
IllU u,AuI 55
AlIl 5 1 5 101 55.
:‘fl1199 i19 1
l 9 ’I i !1__I i1 1 1 4 !I J i1 t I
M1!19!1 1111!
“ °
(fl o 5 1
iT
(IN
I
t I
‘:‘ ‘
IAlflflIuNUl aci
PIUSISSAJU IMIS$IOU LIMIT
‘i1 I .MlJfll!!Hh19111119± 1
ius,a ats
14 11
,
i4i
. ,
,
1 [ 1
s a n I
I (SI
u,
thl I i%
tIItft IDtIAn
1 4U
u, 14, p
1t1I6+.1!
.
SO
U1 5
“54
(NlqI
55
—-
t,14 ( 55N?S
-_- .-_
_L
I (Au 5
• flINl 55 ‘ 54 I IN
4 IS IA S7IIS ,, 3Of1t
0 _J 1 LL 7.I 1j 11I’I
7
I I
“Ii I oI”I 4i
(555 fuIIIN4
“U I , NI ).
A,.
‘ ,uIu Sail
Ipu lcc lnu, ((a liPII AI
(01111 I I I)
QIAuIIP •0I•
•sic Il* )(attP ’ 5l
“ II - lIP
J.-I&i. I I I 11111
tills S ((
lWIu$uIw WI,
77 73
71
%IMIUI
5’5550 ’NI
I atulI 5s I
“1
I Au,
“Al!
RIASIIII 10$! 111(155 tifissloIf
(,Iru$w.’
1155 PIAuIA
111*144 1
urn
Salt 1( 14141 1 1
AnANIAlI It
4.14141 4 K4 5,l,, ,3(,i_51 36 37 SS , 3OI6lI67I. 44 65 66 67 6I 6 ‘t47t 7 1 (73 1I” 7. 177 7h174ISO
iI t IoTqI IiIøIi — I I I ] [ ]T c
1 1551
I IIPD ‘55urn
IPI sINS hUll 11111
I
LriT
• 1 4 1
(a ll’,,’
IW Ir IPU’
(aft 51111
I OUT5OL S InC4T
U44CC1flA .r
(orno L)
P 5I) I%% ?? 1Al 1 155
‘Ala’
14 ( 1 1 1 114
t.II,.•.. u,
1155
RIIASOI
P iII 155
1141(1 1 151
, ,_
rOR
I
111011 fOR IJUW II!
15514 15( 1
lilt
r l l . Ac. s
, ,,,, , ‘
( I )d I IIS4
‘‘ I ’
“a
5( 1 1
II
p CtS1 Psou. S ’
UPACCIPTAPI
(OPTIOSAL)
HP
‘3
-
Pr T t
OsNIIP hail
KIlIPlIAPI
TI .0 ’!..
Jfwi1’t 1i!iii 11!P11 V ‘1 i111
1 ViPri E H9EE i11 EE!
¶cj s I 1it”U”r
111 1511114
tap,
._
‘5
V
—_ .__ .
5(1114 (1I,NIS
74(3 if 9TMh1 111ii111t 5
‘C
C
11I110 •Al.’l
p,I,. It..
(I,%%I l l
P ’ s
15(1S
1 1 1 5 1
44 14 .14,Iscl ,IIs3 ¶434l”I56
.111111
-—. - - - — - — - .. - -a- - — - - - - — —
‘IC
57l,sIs ,I .O($ 116316*4 16 5166 6716. 6117€
It 1111111 I
II
0
SO
-------
3 JJ I:L- J ;_‘E
E>PEP!Er4.ED ‘JERS . .
HIS E>:EC PILL PODJ::E FO M TTED CEM t’IT
TRAr4 F CTICNS FriD IJF1IT s CE EDIT S.L .. .
— HIT C R IA E RETU 34 FOR NO D TA ENTERED
— ENTER END FOR rn MORE DATA TO BE E’dTEPED
— ENTER KILL FOP O T OFE DATA FOP FPE ENT CARL’
— ENTER E:x;EC IN RESPONSE TO ‘E EC BRER; ’ ? ESSAGE
- ENTER EECT TO FE_ECT THIS CARD AND START AGAIN
ARE YOU RESTARTING THIS ROUTINE
AFTER 1 E SYSTEM HAS cPPED ‘0U (DROP)
DO YOU L?ISH TO ADD TO A DATA FILE
SAVED LURING A PREVICUS SESSION ADD::’....
OR ARE THESE YOUR INITIAL ENTRIES (FIRST)....
ENTER DROP. FIRST OR ADD —>FIRST
ENTER CEM EDIT TRANSACTION CARD TYPE (10.51.52,60.70,71 .80) —>52
IS TRANSACTION SIMILAR TO THE PRVIOUS TRANSACTION AT THE
SOURCE, POINT AND CHA;-;-EL LE’?°EL (ENTER ‘c’:
SOURCE AND POINT LEVEL OILY (ENTER ‘P’
SOURCE LEVEL ONLY (ENTER ‘5’)
[ P IS TRANSACTION FOR A EW SOURCE (ENTER ‘N’)
ENTER C.P,S OR N —>N
ENTER TRANSACTION TYPE — N FOR NEW
C FOR CHANGE
D FOR DELETE —
ENTER 2 DIGIT REGION CODE —>07
ENTER 2 DIGIT STATE CODE —>17
ENTER 4 DIGIT COUNTY CODE —>2222
ENTER 5 DIGIT SOURCE CODE —>901)01
ENTER 4 DIGIT EIIMISSIOr4 POINT NO CODE —>00001
EMMISSIUN POINT ND IS A 4 DIGIT NUMERIC CODE...
ENTER 4 DIGIT EMIISSION POINT NO CODE —>0001.
ENTER 3 DIGIT CHANNEL NUMBER —>001
ENTER CEM EN ORCEMENT AGENCY —>1
ENTER REQUIREMENT CODE FOR MONiTOR —>9
ENTER 20 CHARACTER PERMIS EMISSION LIMIT —>20 GDAC,6 Miti PEP.D
ENTER MONITOR INSTALLATION DATE (YYM 1) —>7901
ENTER PSI DATE .YYMM) —>8601
ENTER PST STATUS (PASS OR FAIL) ->PPSS
ENTER MONITOR CERTIFICATION DATE (MMDDYY) —>123181
0717222290O010001000O520011920 OPAC’6 MIF’4 PERD 79018601PASS123
C
DO au WISH TO MODIFY OR DELETE THE TRANSACTION JUST CREATED...
ENTER MDD “DZLETE OR r10 ->MQ
ENTER CEM EDIT TRANSACTION CARD TYPE (10,51.52,60.70,71.80) —>EMD
DO YOU WISH TO LIST THE DRIP JUST ENTERED (YES DR NO) —>YES
1. 071722229000100010000520011920C O AC’6 MIN PERD 79018601PR5 5123
C
DO YOU WISH TO MODIFY OR DELETE THE TRANSACTION(S) JUST CREATED...
ENTER “MOD DELETE OR N0 —>NO
JO YOU WISH TO SAVE THIS DATA? —>VES
PLEASE ENTER A DATASET NAME TO SAVE 11415 DATA UNDER —>ED110886
EDITOB.96 SAVED AND CRTLG’D Oil USRO13
DO YOU WISH TO SUBMIT All EDIT (YES OR liD) ->VES
ENTER THE 2 DIGIT REGION CODE (E) . 07)
OR STATE ABBREVIATION (E><. IA) —>07
JO YOU WISH TO SUBMIT A LIVE OR DUMMY EDIT?
ENTER LIVE OR DUIMY —>DU14rn’
ENTER PRIORITY •:DEF tJLT ) —:
jOB. 5374 CDS’)3 ‘2.!JBMI ED
... OB :‘JBM:TTED CEMINP JT CO?1PLETE
Figure 5-8. WYLBUR Interactive Data Entry
5—36
-------
SECTION 6.0
EDIT PROCESSING
-------
6.0 EDIT PROCESSING
6.1 Edit Program Usage . .. . .. S
Once data for the CEMSS has been coded and entered, users must. validate
the input transactions by running the CEMSS 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 scheduling 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.
The Edit validates each of the punched card types one at a time. Note
that some transactions that pass the Edit may be rejected later by the
Update. In the Update Cycle, all of the transactions for a given facility
will be rejected if the facility and emission point level data are not already
present in the CEMSS. With the hierarchical relationship among sources,
point, and action transactions, an error at a higher leve.l 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 errors as quickly
as possible.
Valid transactions related to CDS—associated data are stored on the CDS
Mod File; all other valid transactions are stored on the CEMSS Mod File. The
CDS Masterfile is updated on Wednesday night.
Transactions that meet the following criterion are passed to the CDS Mod
File: .
• Action type is M3 for a Card Type 70.
• Changes to the CDS-C 4S Indicator (C 4I) for sources added to or
deleted from CEMS.
All transactions are validated by the Edit Program. The Edit Report
produced by the Edit Program lists the action - taken on each input
6—1
-------
transaction. If an input transaction has no edit error messages next to iton
the Edit Report, it is a valid transaction. One or more error messages
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.
6.2 Edit Error Messages
All of the errors identified by the Edit Program are listed in Table 6—1.
All error messages preceded by three asterisks indicate a fatal error. Error
messages preceded by one asterisk indicate a warning error.
Transactions with one or more fatal errors will not be placed on the C 2 SS
Mod File. Transactions with no errors or with only warning errors will
placed on the Cfl4SS Mod File for future processing by the Update. Keep in
mind that a data element flagged with a warning message is blanked by the Edit.
For a detailed explanation of the valid values for each data element in
the CE2IS system, see 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 alphanun eric
characters. . 0
6.3 CE24S Edit Report
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, St
6—2.
-------
TABLE 6-1
EDIT ERROR MESSAGES
DATA ELEMENT NAME MESSAGE
REGI ON
STATE
COUNTY CODE
SOURCE NUMBER
CARD CODE’
CARD 1—0
UPDATE CODE
EMISSION POINT
ACTION NUMBER
QUARTER DATE (ANUM)
CHANNEL NUMBER
AGENCY CODE
REQUIREMENT
PST STATUS
LINE NUMBER
*** INVALID REGION CODE
*** INVALID STATE CODE
*** INCORRECT COUNTY CODE FOR STATE
*** COUNTY CODE MUST BE NUMERIC
***SOIJRCE NUMBER MUST BE NUMERIC
*** CARD TYPE AND/OR LEVEL IS INVALID
* CARD 10 CEMSI TRANSFERRED TO CDS
*** NO DATA IN COL. 24-79 FOR CARD 10
* INVALID UPDATE CODE
INVALID UPDATE CODE FOR CARD 10
*** EMISSION POINT MUST BE ZEROS
*** EMISSION POINT MUST BE NUMERIC
*** POINT MUST BE GREATER THAN ZERO
*** EMISSION POINT MUST BE NUMERIC
*** POINT NO. MUST BE LESS THAN 1000
*** ACTION NUMBER MUST BE ZEROS
*** ACTION NUMBER MUST BE > THAN ZERO
ACTION NUMBER MUST BE ZEROS
*** ACTION NUMBER MUST BE NUMERIC
*** ACTION NUMBER MUST BE LESS THAN 0099
* ANUM 0099 ON M3 NEW — 0099 ASSUMED
INVALID QUARTER DATE
*** CHANNEL MUST BE GREATER THAN 100
CHANNEL NUMBER MUST BE NUMERIC
* AGENCY CODE MUST BE 1, 2, 3, or 4
* REQ. CODE MUST BE 0, 3, 5, 6, or 9
* PST STATUS MUST BE PASS OR FAIL
LINE NUMBER MUST BE NUMERIC
6—3
-------
DATA ELE2 ENT NAME
TABLE 6—i
EDIT ERROR MESSAGES (Continued)
MESSAGE
ACTION TYPE
EER DATA (M3 ACTION)
DATE FIELDS
DATE ACHIEVED
DATE SCHEDULED
STAFF CODE
RESULTS CODE
ACTION DELETE
USE OF ASTERISKS
TIME PERIOD
SOURCE OPERATING TIME
REASON FIELDS
DCCESS 4ISSIONS
MONITOR DOWNTIME
DELETES
INVALID ACTION TYPE
*** ACTION TYPE REQUIRED ON NEW ENTRY
* INVALID DATE VALUE - OUTPUT SPACES
* CARD 70 DATA TRANSFERRED TO CDS
* CHAN 000 ON M3 NEW - ZEROS ASSUMED
1 13 CHANGE NOT VALID ON CHAN > 000
* INVALID DATE VALUE - OUTPUT ZEROS
* INVALID DATE ACHVD - OUTPUT ZEROS
* INVALID DATE SCHED - OUTPUT ZEROS
* INVALID STAFF CODE
* INVALID RESULTS CODE
*** INVALID ACTION DELETE
* DT SCHED SHOULD BE ON NEW-OP ZEROS
* ASTERISKS ONLY FOR CHANGE TRANS
*** TIME PERIOD MUST BE A-G OR M
* OPER TIME CHANGED TO EER DEFAULT
*** OPERATING TIME MUST BE NUMERIC
* SOURCE OPERATING TIME IS ZERO
* SOURCE OPERATING TIME IS BLANK
* OPERATING TIME CHANGED TO ZERO
* OPERATING TIME NOT IN PERIODS
*** REASON FIELD MUST BE NUMERIC
* REASON NOT IN PERIODS
* TOTAL CCESS E2IIS > OPERATING TIME
* TOTAL CCESS E2IIS > MONITOR UPTIME
* MONITOR DOWNTIME > OPERATING TThT
*** NO DATA IN COL. 27-79 FOR DELETES
NO DATA IN COL. 28-79 FOR DELETES
6—4
-------
Count’y, Source, Point, Action, Channel Number, Card Type, Card Level, and
Update Code. Directly beneath these column headings are two rows of numbers
ndicating card columns; the position of any data on the card can be
determined by referring to these card column identifiers.
Error messages are identfied on the right—hand side of the report. In
addition, data elements in error will have one or more asterisks directly
beneath the data element to help pinpoint the problem area that needs to be
corrected.. Figure 6—1 is a sample of the Edit Report produced by the Edit
Program.
6.4 Edit Job Control Language
To execute the Edit: Program, use the JCL shown in Figure 6-2. 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 the 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 type of JCL
shown in Figure 6-3.
2. Input form tape or disk . Input:from a disk or a tape file .can be
processed by the Edit just as. easily as punchàard input.
6—5
-------
CONTINUOUS EMISSIONS MONITORING EDIT REPORT
REGION 1—BOSTON
TRANSACTIONS ENTERED ON 08/14/86 AT 20:33 3 30.
C C CT CARD TYPE/CL.CARD LEVEL UPDATE. ERROR MESSAGES
PG ST CNTY SRCE PTNO ANUN I L CMAN CARD COLUMNS: C3DE. 4 WARNING — DATA ELEMENT REJ:T
O 1 2 3 4 5 6 7 8 • 6*6 FATAL — CARD REJECTED
12 34 5678 90123 4567 8301 2 3 45678901234567890123456789012345678901234S67890223456789 0
01
01
01
01
01
01
01
01
01
01
01
01
01
20
20
20
20
20
20
20
20
20
20
20
20
20
0885
0835
0885
0885
0885
0885
0885
0885
0885
0885
0385
0885
0885
60005
60005
60005
60005
60005
60005
60005
60005
60005
60005
60005
60005
60005
0001
0001
0001
0001
0001
0001
0001
0001
0001
0001
0001
0001
0001
8502 7 1 I I1M13L000000000000000000000000I860000260 0000000000000 S
8502 7 2 111000000000000000000000186000024000000000000003
8502 7 1 21 IML3 I0000000000000000000000000000000000 0 0 0 3 000000000 S
8502 7 2 211000000000000000000000000000000000030000000003
8502 7 1 511M1310000000000000000000000000000000000008640 0 0 0 0 0005
8502 7 2 5110 00000000000000000000000000000000864000000003
8503 7 1 111M1237300001560000000000000008100008100000000 0 0 0 000 05
8503 7 2 111000156 000000000000000810000810000000000000003
8503 7 1 2 I1M1Z373000000000000000000000100SOO100 S000000000000005
8503 7 2 21100000000000000000000100500100500000000000 0003
8503 7 1 SI1M1237300007Z00000000000000000000000000 0063000000000 S
8503 7 2 51100072000000000000 0000000000000000630000000003
8504 7 1 111M132078000000000000000000000084000084000 000000000005
C
C
C
C
C
C
C
C
C
C
C
C
C
.
.
.
.
.
.
.
.
.
.
.
•
•
*66*6* -. ‘
•
01
20
0885
60005
0001
8504 7 2 111000000000000000000000084000084000000000000003
C
•
01
20
0885
60005
0001
8506 7 1 211N1320780000000000000000000010650010650124200 0 00 00005
*6*6*6
C
:
.
01
20
0885
60005
0001
8504 7 2 211000000000000000000001065001065012420000000003
C
.
01
20
0885
60005
0001
0504 7 1 511M13207800000000000000000000000000000000143500000 0 005
*66*6*
C
.
.
01
20
0885
60005
0001
8504 7 2 5110000000000000000000000000000 00001435000000003
C
•
01
20
0885
60005
0001
8601 7 1 111N12960000000000000000000000036000034800000000000 0 00 5
C
•
01
01
20
20
0885
0885
60005
60005
0001
0001
8601.7 2 111000000000000000000000348000348000000000000003
8601 7 1 211M129600000000000000000000000000000000000000000 000005
C
C
.
.
01
01
20
20
0885
0885
60005
60005
0001
0001
8601 7 2 211000000000000000000000000000000000000000000003
8601 7 1 5I IM1Z960000000000000000000000000000000000 I8 3 00 0 0 00000 S
C
C
.
.
01
20
0885
60005
0001
8601 7 2 511000000000000000000000000000000001830000000003
C
•
01
22
1291
00010
0501
8601 7
1 14 IM00000000000000000000000000000000000000000000000 0 0 0 5
C
•
01
01
22
22
1231
1291
00010
00012
0501
0501’
8o01 7 2 141000000000000000000000000000000000000000000003
8403 7 1 111M04206000001000005700000000000000000000000000000 000 5
C
C
.
•
01
01
22
22
1291
1291
00012
00012
0501
0501
8603 7
8404 7
2 111000010000057000000000000000000000000000000003
1 111M006320 00000100000 1000000000000000000000000000000005
C
C
.
.
01
01
22
22
1291
1291
00012
00012
0501
0501
8404 7 2 111000001000001000000000000000000000000000000003
3501 7 1 111M083760000173000149000000000007000007000000000000005
C
C
•
•
01
01
22
22
1291
1291
00012
00012
0501
0501
8501 7
8502 7
2 1110001?3000149000000000007000007000000000000003
1 111M125040000181000717000000000010000010000000000000005
C
C
•
•
01.
01
22
22
1291
1291
00012
00012
0501
0501
8502 7 2 111000181000717000000000010000010000000000000003
8503 7 1 111M13248O00O110O0066O0000020000190000190000O000’ 000O5
*6*06*
C
C
•
.
.
01
22
1291
00012
0501
8503 7 2 111000110000460000002000019000019000000000000003
C
.
01
22
1231
00012
0501
8504 7
1 111M132480000022000357000002000023000023000000000000005
*6*66*
C
.
01
22
1291
00012
0501
8504 7 2 111000022000357000002000023000023000000000000003
C
.
01
•
00012
0501
8601 7
1 111M1266000000190016610000000 ‘ 00069000000000000005
01
00012
0501
8601 7 2 11100001900166100000000006900 J000000000003
Figurc.’ 6-1. Simple Edit Report
C
.
OPERATING TIME ) MAX Fj
CARD 7—2 REQUIRES VALID CA 7—1
OPERATING TIME ) MAX F R J .E TR
CARD 7—2 REQUIRES VALID CA : 7— i
OPERATING TIME ) MAX FOR 0 E TR
CARD 7—2 REQUII ES VALID CL 7—1
*4* OPERATING TIME ) MAX FOR .E TR
*0* CARD 7—2 REQUIRES VALID CA 7—1
*6* DPERATIN TIME ) MAX .0R C.E .TR
04* CARD 7—2 R€QUI 5S VALID ‘—1
-------
FIGURE 6-2
CEMSS EDIT JOB CONTROL
/1 1 11 JOB (AMAUID,MIII),’USER ID’,TIME=(O,3),PRTY=2
/*RO JTE PRINT RMTRR
//CEMSEDIT D EC C 1SEDIT
//STEP1.SORTIN DD *
— - Input Transactions --
//
where: RR is the user’s remote number or RMTRR is replaced with
the user’s N number designation for the new printers
where available.
III is the user’s initials.
AAMUIDIs the user’s account number and user ID.
FIGURE 6—3
USING CEMSEDIT WITH DUMMY MODE
I/Ill JOB (AAMUID.MIII),’User ID’,TIME=(O,3),PRTY=2
/*ROUTE PRINT RMTRR
//CEMSEDIT D EC CEMSEDIT,TYPE=’DtJ? 24Y,’
//STEP1.SORTIN DD *
— — Input Transactions ——
//
where: RR is the user’s remote number or RZ4TRR is replaced
the user’s N number designation for the new printers
where available.
with
III is the user’s initials.
AMAUID is the user’s account number and user ID.
6—7
-------
SECTION 7.0
UPDATE PROCESSING
-------
7, ) UPDATE PROCESSING
The Update Cycle applies input transactions to the Masterf lie. All input
transactions that contain no fatal errors are stored on the Mod File by the
Edit Program. During the Update Cycle, all transactions placed on the Mod
File since the last update are applied to the Masterfile by the Update Program.
7.1 Update Program Description
Prior to the Update Program, all input transactions from the Mod File are
sorted into the same sequence as used in the Masterfile. The output
Masterfile from the previous Update Cycle becomes the input Mastérfile on the
current cycle. The Update applies input transactions to the Masterfile to
produce a new version of the Masterfile as output.
The Update Program performs the following functions:
1. Copies entire CDS sources subject to C 4S regulations to the CE 4SS
Masterfile, automatically updating all CDS—associated data on the
CEMSS Masterfile.
2. Adds monitor, EER summary data, and comments
3. Changes monitor, EER summary data, and comments
4. Deletes monitors, actions, EER summaries, and comments.
Delete transactions are allowed for Card Type 51, 60, 70 (except for M3
actions), 71, and 80 records. In addition, a Card 10 delete is valid if a
user wishes to remove a source from the C SS Masterfile; a Card 1 delete has
no effect on the CDS Masterfile other than to clear the CE 4S Indicators at all
levels and will not remove any data from CDS.
7.2 Update Scheduling
The scheduling and maintenance of the update cycle is the responsibi-
lity of the National Compliance Data System DBC, Franklin C. Smith. The valid
7—1
-------
transactions on the Mod File are applied to the C ’iSS Masterfile by the Update
Program. Call the national CDS .DBC at FTS 382—2881 or• 1—202—382—2881 if
need a special Update Cycle in order to apply your transactions to the
CDS/CEMSS Masterfiles.
7.3 Update Report ’
The Update Program produces an Update Report, which is stored on a
computer file. If the user had transactions that were entered into the Update
Cycle, the National CDS DBC will have the Update Report run for each user, and
it will print at the user’s remote printer.
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 C 4SS Masterfile. If the
transaction was rejected, there will also be an error message explaining y
the transaction could not be added, changed, or deleted.
All errors appearing on the Update Report should be corrected, coded, and
then resubmitted to the C 24SS through the Edit Program.
Figure 7—1, is a sample of the Update Report produced by the Update Cycle.
7.4 Update Report Messages
On the Update Report, the Update Action column indicates the action taken
by the Update Program on each transaction passed by the Edit. The normal
Update Action message is ADDED, CHANGED, COPIED, OR DELETED.
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 transactions Update Code. For each rejected transaction, a diagnostic
error message is printed out. Table 7—1 lists all of the errors identifiE y
the Update. An explanation of the corrective procedures for each Update error
message is also given in this table.
• 7—2
-------
UPDATE R -
Oa/14/86 CONTINUOUS MONITORING SYSTEM PAGE 001
REGION 1—BOSTON
OUTPUT SERIAL 000197
ST CNTY SOURCE EMIS tHAN ACT CARD UPOT UPDATE ERROR
CODE CODE CODE PT NO NO CODE—LEVEL CARD COLUMNS: CODE ACTION MESSAGE
0 1 2 3 4 3 6 7 6
3 5676 90123 6567 890 1234 5 6 0
Figure 7—I. Sample Update Report
20
0277
00016
0011
111 esoi
7
1
M 1 296 0 0 0 000 00 0 0 0 00 0 0 0 00 00 0 0 06, 0 0 0 0 01200 0 0 00 0 0 0 00 0 0
C
CHANGED
20
0277
00016
0011
111 esoi
7
2
00000000000 000 0 0 0 0 00 069 0 0 00 01 1 0 0 00 00 0 0 00 0 0 00000000
C
CHANGED
20
0277
00016
0011
211 8501
7
1
M129600000000000000000 0000 026$000 261 0 0 031 02 0 0 0 0 0 0 0
C
CHANGED
20
0277
00016
0011
211 8503
7
2
0000000000000 00 00 0 0 02s8 0 0 0218 0 0 031 02 00 00 0 0 00000000
C
CHANGED
20
0277
00016
0011
311 6501
7
1
M12960000000000000000000 000054 0 00054 0 0 031 07 0 0 0 00 0 0
C
CHANGED
20
0277
00016
0011
311 esoi
7
2
000000000000000000000 5600 0 05400 031 02 00 0 0 0 0 00000000
C
CHANGED
20
0277
00016
0011
111 8502
7
1
M13104 0 000 0 00 0 00 000 0 0 00 06 0 0 0 0 16 0 0 0012 0 0 0744 000 0 0 0 0
C
*REJECT
20
0277
00016
0011
111 esoz
7
2
00 00 00 0 0 0 0 000 0 0 006 0 00016 0 0 0 012 0007440 000 0 0 00000000
C
AREJECT
20
0277
00016
0011
311 6502
7
1
N131060000000000000000000 00 00 0 0 00 0 0 00 00 024 0 0 00 00 0 0
C
CHANGED
20
0277
00016
0011
311 8502
7
2
0000000000000000000000000000000 00240 00 000 0 00000000
C
CHANGED
20
0277
00016
0011
111 5503
7
1
M123960 000696 0 0 00 06 0 00 0 06 0 0 2622 0 02622 0 0 0 0 00 0 00 00 0 0
C
AREJECT
20
0277
00016
0011
111 8503
7
2
000696000006000006002622 0 026220 0 0 0 0 0 0 0 0 0 0 0 00000000
C
*REJECT
20
0277
00016
0011
311 8503
7
1
M123960000000 000 000 0 00 00 0 00426 0 0 04260 0 093 0 0 0 0 0 0 0 0 0
C
CHANGED
20
027?
00016
0011
311 8503
7
2
00000000000000000 000426 000626 0 0 093 0 0 00 0 0 0 0 00000000
C
CHANGED
20
0277
00016
0011
111 8601
7
1
M1296000000000 0 00 000 0 0012 0 0 0006 0 0 0 0 06 0 0 0 0 00 0 0 0 0 0 0 0
C
*R(JECT
20
0277
00016
0011
111 8601
7
2
000OO0O000000OOO12O00OO6OQO0O6OOOOgOO00 Oø 00000000
C
aREJECT
20
0277
00016
0031
311 8601
7
1
N1296000000000 0000000000 0 0 0 00 0 00 0 0 0 0 0 0 0272 0 0 0 00 0 0 0
C
CHANGED
20
0277
00016
0011
311 8601
7
2
000000000000000 0 0 0 000 0 0 0 00 0 0 0 0 0 0ZZZ 0 0 0 0 0 0 0 00000000
C
CHANGED
20
0277
90004
0001
111 6501
7
1
M0576600023880002 62 000 0 00 0 033 01 0 03 231 0 0 01 740 00 516 0
C
CHANGED
20
0277
90004
0001
111 8501
7
2
002388000262000 0 0 00 033 01 0 03231 0 0 0174 0 00516 00000000
C
CHANGED
20
027?
90004
0001
311 8501
7
1
N05766 00 0 0 00 0 0 0 0 0 0 0 0 0 0 000 0 0090 00 0 0900 0 0019,001,18 0
C
CHANGED
20
0277
90004
0001
311 8501
7
2
0000000000000 0000 000 0900 0 0 090 00 00198001515 00000000
C
CHANGED
20
0277
90004
0001
111 8502
7
1
M0306600055140 00 0 00 00 0 0 0 0 0 0 08460 0 06460 01 093 0 0 00 0 0 0
C
*REJECT
20
0277
90006
0001
111 8502
7
2
00 55140000000 0 0 0 0 00 0 0846 0 0 08460 01 0930 0 0 00 0 00000000
C
*REJECT
20
0277
90004
0001
111 8503
7
1
M05124000 5307000006 00 0 0160 02 064 0 02 064 00 0460 0 01842 0
C
*REJECT
20
0277
90004
0001
111 8503
7
2
005307000 0 06 0 0 0 038 0 020640 02 064 0 0 0480 0 01842 00000000
C
*REJECT
20
027?
30004
0001
111 8504
7
1
M109140002844000 0000 0 0000 0 0 0732 0 0 0732 00 0 06 0 0 0 0558 0
C
*REJECT
20
0277
90004
0001
111 8506
7
2
0D28640000000 000 0 0 00 0732 00 0732 0 0 0 06 00 0055 6 00000000
C
*REJECT
20
0277
90004
0001
111 6601
7
1
M107640002016 0 0 0 0 00 0 0 0 0 0 0 0 00342 0 0 034200 018 0 0 0 0,1 0 0
C
*REJECT
20
0277
90004
0001
111 8601
7
2
D020160000000000000003420003420 00180000510 00000000
C
*PEJECT
20
0277
90004
0003
311 8502
7
1
N0306600000000000 00 00 00 00 00 056 00 0 0560 0 0 2233 0 0 0 0 0 0 0
C
CHANGED
20
0277
90004
0003
311 8502
7
2
00000000000000000 00 00 54 0 0 0084 0 0 02 233 00 0 00 0 00000000
C
CHANGED
20
027?
90004
0003
311 6503
7
1
MD5124000 000 00 00 00 0 0 0 0 0 0 00 0300 0 003 0 0 00 0216 0 0 01642 0
C
CHANGED
20
0277
90004
0003
311 8503
7
2
0 00000000 000 0 00 00 0 0 03 0 0 0 0 03 0 0 0 0 0216 0 0 01842 00000000
C
CHANGED
20
0277
90004
0003
311 8506
7
1
M109140002100 00 0000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 00 0 003 00 001122 0
C
CHANGED
NO MATCP4—CNT/COS
NO MATCH—CMT/CDS
NO MATC —CMT/CD5
ND MATCW—CMT/CDS
NO MaTC —CMT,CDS
NO MATCH—CMT/CDS
NO MATCW—CMT/(O5
NO MATCN-CNT/CQ5
NO H*TC’ I—CMT/(O5
NO MATCN—CMT D5
NO M*TC’l—CMTICQS
NO MATCI4-CMT,COS
NO MATC’l-CMI/COS
NO MATCH-CMT/tD
7—. 1
-------
TABLE 7—1
UPDATE ERROR MESSAGES
. Update Error Message Explanation
NO MATCH-CMT/CDS Card 10 and Cards 51 through 80 cannot
be applied to the Masterfile as change
or delete transactions if a
corresponding Masterfile record does
not exist. Make sure that the source
exists on the Masterfile; verify that
the correct state, county. and source
number are being used on the
transaction. .
INVALID NEW CO?.2 ENT An emission point comment Card.. 60
cannot be added to the Masterfile
unless the corresponding point and
channel numbers already exist on the
Masterfile. An action comment Card 80
cannot be added to the Masterfile
unless the corresponding point,
channel, and action numbers already
exist on the Masterfile.
DUPLICATE TRANS If two or more transactions with the
same region, state, county, source,
point, and action numbers have an
‘Update code ‘N’, the first transaction
is added to the Masterfile; and : the
second and subsequent transactions are
rejected with this message. A change
transaction following a new trans-
action for the same record IDis re-
jected. Duplicate delete transactions
are also rejected.
ALREADY ON FILE . A transaction with an Update Code ‘N’
cannot be added to the Masterfile if a
Masterfile record already exists with
the same region, state, county,
source, point, and action numbers.
Also a new comment cannot be added if
a comment with the same record iden-
tifier line number already exists on
the Masterfile.
ANUMS DEPLETED This message occurs when the user
attempts to add a C 4S •action and’ the
system—generated action number fot .e
point and channel number has excL ._d
98.
7 ;_4
-------
TABLE 7-1
UPDATE ERROR MESSAGES (Concluded)
Update Error Message Explanation
INVALID NEW CH-ADD-l Card 51 cannot be added to the
Masterfile with an Update Code’N’
unless there is a corresponding
emission point already on the
Masterfile. Make sure that the
• emission point exists on the
Masterfile if channel number
information is being added to the
Masterfi] .e.
INVALID NEW CH-ADD-2 Card 52 cannot be added to the
Masterfile with an Update Code ‘N’
unless there is a corresponding
emission point already on the
Masterfile or the channel number has
already been established on the
Masterfi].e. Check to see that the
emission point already exists on the
Masterfile.
INVALID NEW ACTN-ADD-0 • Card 70 cannot be added to the
Masterfile with Update Code ‘N’ unless
there is a corresponding emission
point and channel number that already
exist on the Masterfile. Check to see
that the emission point and channel
number already exist on the Masterfile.
INVALID NEW ACTN—ADD-l Card 71 cannot be added to the
Masterfile with Update Code N’ unless
there is a corresponding emission
point and channel number that already
exist on the Masterfile. Check to see
that the emission point and channel
number already exist on the Masterfile.
7—5
-------
SECTION 8.0
RETRIEVAL PROCESSING
-------
8.0’ RETRI EVAL PROCESSING
The CEMSS Retrieval is used to prepare management reports based on
i ilmiii ti ii on the Ma ter1ile. The keti-ieva 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 on the basis of
criteria developed to meet specific needs.
All output reports other than the Edit Report and the Update Report are
produced on request from the Retrieval Program. Requests for management
reports may be made at any time, because 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 carefully
prepare a Retrieval request form and submit this form to have the selection
cards entered and submitted to the National Computer Center computer through
WYLBUR. The selection cards and appropriate 3d cards are used to run the
Retrieval. The user submits this input to the central computer site through
the terminal using WYLBUR. Output from the Retrieval Program consists of a
Retrieval Edit Report and the management reports requested by the user;
The Retrieval Program provides the following features:
• Quick turnaround — the Retrieval operates on a “demand” basis and
will usually provide overnight or faster turnaround, depending on
the backlog of work at the computer center.
• Improved selectivity — Information can be selected from the
Masterfile to meet the specific needs of the user so that smaller,
more pertinent reports can be prepared. For example, a user who
needs a list of point source facilities with a monitor
installation date between 10/1/80 and 9/30/81 could get a Quick
Look Report that shows only these facilities and the particular
information wanted (name, size, monitor emission limits, etc,) on
a single line.
• Selection logic — Each user can select from the CE 4SS Masterfile
only the data of interest for a particular need. The user can
select data based on the presence or absence of information on the
8—1
-------
Masterfije, depending on the type of selection criteria specified
on the logic.selection input card.
• Variable sequence — The Retrieval program permits the user to
select the sequence for viewing the selected data.
• Variable output format The users can select from nine print
formats, depending on need. One format is a single—line report
with a user option allowing inclusion of any specific data
elements desired.
Because all management reports are based on the CEMSS retrieval
‘capability, users should place data on’ the Masterfile in a manner that permits
efficient retrievals. Comment information cannot be used in the Retrieval’s
selection or sorting criteria. When preparing input data for the Cfl4SS , users
shoul,d be aware of the validation procedures for each data element performed
by the C 4SS Edit as we]] as the selection, sorting. and printings criteria
available in the Retrieval.
8.1 Reports Available from the Retrieval
Management reports are not automatically generated; users must request
reports from the CEMSS Retrieval system to suit their particular needs. Only
sources subject to CEMS regulations are stored on the CEMSS Masterfi].e. From
these sources, users must determine what information available on the CE24SS
Masterfile is. of interest. Users may obtain all of the information on the
Masterfile or a limited amount based on their needs.
Any of the defined data elements can be used as a selection criteria.
Because the selection, sorting, and printing criteria of the Retrieval Program
operate independently, users may select a report on one set of data elements,
sort on another set of data elements, and select different data elements for
printing. Selection criteria cannot be based on information found in comment
records.
8—2
-------
R?ports are printed in region, state, county, and source number sequence
unless users elect their own sorting sequences. Up to six defined data
.ernents may be used to create the user sort sequence.
The CEMSS Detail Report, the Source Data Report, the Statistical Report,
the Questionnaire Report, and the Milestone Report will present user—selected
and sorted information in a fixed format. The Quick Look Report allows users
to design their own report formats. All data elements other than comments can
be formatted. for printing in a user—selected sequence. The CEMSS Stat Report
will present elementary statistics on a user—specified portion of the
Masterfile (region, state, source, etc.). A detailed description of each
report is provided in the following paragraphs.
8.1.1 CEMS Detail Report
This report provides a complete, detailed listing of all monitor and
excess emission data for CEMS sources only. This report is similar to a
urce Data Report, but it: presents only source—level data such as facility
name and address together with a complete listing of monitor manufacturers,
model number, emission limits, PST dates, CEMS actions, monitor comments, and
excess -emission periods. No information for emission point data or
enforcement data from CDS appears on this report. Users interested in the
complete CDS and the CEMSS data for a given source should request a Source
Data Report as described in Section 8.1.4. Figure 8—1 is.a sample of a CEMSS
Detail Report.
8.1.2 Quick Look Report .
The Quick Look is the. most widely used report type available from the
Retrieval. For each CEMS source, point, action, or channel that meets the
user’s selection criteria, a single ‘line containing user—selected CDS/CEMSS
8—3
-------
SOURCE DETAIL REPORT
. • . .......... . .S.. . . .S .. .SSSeS • • •eS•S•SS • ••SS* • • •e ••eS •Se•• •• • • • •
08/14/86 CONTINUOUS MONITORING PAGE 1
CONFIDENTIAL REPORT — FOR EPA INTERNAL USE ONLY
DETAIL REPORT OF CEM SOURCES IN CEN SUBSET AS OF A/14F86
CONN LIGHT t POWER
STATE CT COUNJY FAIRFIELD
COUNTY 0265 SOURCE 00142 AQCR 043
.... .. .e •...••........•S.....•.......... .....e..... • .••t •e. ••..e.e .
SOURCE NAME CONN LIGHT L POWER
ADDRESS W000WARO AV
CITY. STATE NORWALk CT 06854
.•.. .... •.•.....e.... .••.....e...........•S.....•.SS.e....••.•..e•..SS..........•.......•...
SOURCE COMPLIANCE STATUS: 3 IN COMPL—INSPECTION
AIR PROGRAM DESCRIPTION: 0 SIP SOURCE SOURCE CLASSIPICATIOPU Al
POLLUTANT LOADING *0CM INDICATOR
PT PARTICULATE MATTER 524 2 ATTAINED SECONDARY
52 SULFUR OXIDES 9623 A
HC HYDROCARBONS 47 N NON—ATTAINMENT
CO CARBON MONOXIDE 304 N NON—ATTAINMENT
N2 NITROGEN OXIDES 4061 A
I I e• • I • 0 •• S I S • • I ••• • e • ••Se• • ••e ... . . S.. S SI ISS Se S• • S 0 •SS • IS • S S•• S S • • • • S SC • I• 0 Se
. SS.IS..e...•.......eI.........SS.SI.........S....•.•...e..........
....SS.e...e.....e.......••........I..e.eI.......I............
. • • ..ee...S...e..S•. 5S..e.......SSI•.SI.•....S.......
POINT NUMBER 0002
POLLUTANT PT
DESCRIPTION STEAM BLR BRNNG RES OIL
** CHANNEL NUMBER2 111
TYPE OF MONITOR: OPACITY MO
MONITOR MANUFACTURER: BAILEY CERTIFICATION DATE LATEST PST DATE:
MONITOR MODEL NUMBER: MONITOR REQUIRED FOMI LATEST PST RESULTS:
MONITOR SERIAL NUMBER: ENFORCEMENT AGINCY8 TOTAL PST PASSES: 00
MONITOR INSTALLED /60 PERMISSIBLE EMIS LINIfl TOTAL PST FAILS: 00
S 55 .S...S.e...e...e.SIS.....•.....e..I...........e..... 5•5555 SI S
_.... ..••........• •I. .••SSSS .5.55e0 .5 •_
5• ..S.I. .S CISSS •5 •• S... .SSS• SS S•• • SS See SS SS•I • S
S S. S•e •eSSSIe• •SS • ••e • • • • •••• • • • • • • • • • SeeS
POINT NUMBER 0005
POLLUTANT PT
DESCRIPTION STEAM BLR BRNNG RES OIL
Figure 8—1. CEMS Detail Report
8—4
-------
SOURCE OETAIL Mt
•... .
OR/14/86 CONTINUOUS MONITORING PA 2
CONFIDENTIAL REPORT — FOR EPA INTERNAL US! ONLY
DETAIL REPORT OF CEN SOURCES IN CEN SUBSET AS OF 8/14F16
COHN LIGHT t POWER
STATE CT COUNTY FAIRPIFLO
COUNTY 0263 SOURCE OO1 2 10CR 043
•..S.... . S. •SS•S•• .•S•.See.e •S•SS•SS•SeSe• .•SeS .e .. .e ..e....S.......................... S..... S.... S Se
e* CHANNEL NUMBER: iii
TYPE OF MONITOR: OPACITY MO
MONITOR MANUFACTURER: BAILEY CERTIFICATION DATE! LATEST PST.DATE:
MONITOR MODEL NUMBER: MONITOR REQUIRED FOR! LATEST PSI RESULTS!
MONITOR SERIAL NUMBER: ENFORCEMENT AGENCY! TOTAL PST PASSES: 00.
MONITOR INSTALLED: /60 PERMISSIBLE EMIS LIMIT! TOTAL PST FAILS: 00
-------
data elements is formatted for printing. The user may specify what data
elements are printed and also the spacing of these data elements.
A standard Quick Look print line contains state, county. source, point,
action number, and channel number together with up to 14 other user—selected
data elements. The only restriction is the print line length of 104
characters. Users may suppress state, county, source, point, action number,
and channel number on each Quick Look line by using the no-header (NOIW)
option. This option allows the full use of the 132 character print line for
user—selected data elements. Figure 8—2 is a sample Quick Look showing
monitor data for CEMS sources in Maine and Massachusetts.
Data elements are printed on the Quick Look line in the same order 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. 1
and BLK2 are especially useful when the Quick Look is used as a turnaround
document. -
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 to request page breaks and
subtotals only for those data elements that produce logical groupings, such as
State, AQCR, Action Type, etc.
Users may select their own sequencing for the Quick Look Report. Often
two Quick Look Reports with the same selection criteria provide users with a
great deal of insight when the reports are sequenced differently.
8—6
-------
QUICK LOOK REPORT.
08/15/86 CONTINUOuS EMISSION MONITORING SYSTEM PAGE 2
CONFIDENTIAL REPORT — FOR EPA INTERNAL USE ONLY
SOURCES IN CEM SUBSET AS OF 8/14/06
S.....
ST CNTY SOURC PTNO CMA ANUM PTNO MONITOR REQD AGCD MONITOR MANUFACTURER CERT DIE MIND P 510 PERMIS EMIS LIMIT
S S • • • 5. .• • • • • St.•.••• •SsI . S • • •S • • • • • • • •.. • • • . . S
0011 311 0000 0011 NOX NSPS EPA—RGN. LEAR SIEGLER 11/02/82 82/02 82/11 0.7 LBS/MBTu NOX
20 0277 90004 0000 000 0000 0000 UNKNOWN UNKNOWN / / / /
0001 000 0000 0001 UNKNOWN UNKNOWN . / / / /
0001 111 0003 0001 OPACITY NSPS EPA—RGN ENV. DATA CORP(EDC) 03/20/30 78/11 79/07 20 OPACITy
0001 311 0000 0001 NOX NSPS EPA—RGN ENV. DATA CORP(EDC) 03/20/80 78/11 79/07 0.3 LBS/MSTU NOX
0002 000 0000 0002 UNKNOWN UNKNOWN . / / / /
0003 000 0000 0003 UNKNOWN UNKNOWN . / / / /
0003 311 0000 0003 NOX NSPS UNKNOWN / / / / 0.7 L /MBTU 3 MR PRO
20 0885 60005 0000 000 0000 0000 UNKNOWN UNKNOWN / / / /
0001 030 0000 0001 UNKNOWN UNKNOWN / / / /
0001 111 0000 0001 OPACITY NSPS EPA—RGN LEAR SIEGLER 06/11/81 81/04 81/06 35 X OPACITY
0001 211 0000 0001 502 NSPS EPA—RGN LEAR SIEGLER 11/17/81 81/03 81/11 3 GRAMS/SEC.
0001 511 0000 0001 MC NSPS EPA—RGN ITT BARTON 08/14/84 81/04 / 5 PPM/12 HR PERIOD
0002 000 0000 0002 UNKNOWN UNKNOWN / / / /
22 12 1 00010 3000 000 0000 0000 UNKNOWN UNKNOWN / / / /
0001 000 0000 0001 UNKNOWN UNKNOWN / / / /
0002 000 0000 0002 UNKNOWN UNKNOWN. / / / /
0501 000 0000 0501 UNKNOWN UNKNOWN / / / /
0501 141 0000 0501 OPACITY ENFORCE UNKNOWN PHOTOMATION / / 77/ 77/ 20 OPAC/6 MIN PERD
0501 151 0000 0501 OPACITY ENFORCE UNKNOWN PHOTOMATION / / 77/ 77/
0501 1 1 0000 0501 OPACITY ENFORCE UNKNOWN PHOTOMATTON / / 77/ 77/
0502 000 0000 0502 UNKNOWN UNKNOWN . / / / /
0999 000 0000 0999 UNKNOWN UNKNOWN / / / /
22 1291 00012 0000 000 0000 0000 UNKNOWN UNKNOWN / / / /
0001 000 0000 0001 UNKNOWN UNKNOWN / / / /
0002 000 0000 0002 UNKNOWN UNKNOWN . / / / /
0501 000 0000 0501 UNKNOWN UNKNOWN S / / / /
0501 111 0000 0501 OPACITY OTHER EPA—RGN PHOTOMATION / / 77/03 77/ 20Y OPACITY
0502 000 0000 0502 UNKNOWN UNKNOWN / / / /
0502 111 0000 0502 OPACITY OTHER EPA—RGN PHOTOMATION / / 77/03 77/ 2O OPACITY
0999 000 0000 0999 UNKNOWN UNKNOWN / / / /
22 1291 00128 0000 000 0000 0000 UNKNOWN UNKNOWN / / / /
0001 000 0000 0001 UNKNOWN UNKNOWN / / . / /
0002 000 0000 0002 UNKNOWN UNKNOWN / / / /
0003 000 0000 0003 UNKNOWN UNKNOWN / / / /
0004 000 0000 0004 UNKNOWN UNKNOWN / / / /
0005 000 0000 0005 UNKNOWN UNKNOWN. / / / /
0006 000 0000 0006 UNKNOWN UNKNOWN / / S/S /
0007 000 0000 0007 UNKNOWN UNKNOWN / / / /
0008 000 0000 0008 UNKNOWN UNKNOWN . I. / / /
Figure. 8—2. Quick Look Report
8—7
-------
Three different Retrieval report formats can be requested from the same
Retrieval. Thus, the Quick Look Report can serve as a. summary or index to one
of the longer report formats such as the Source Data Report.
8.1.3 Double—Spaced Quick Look Report
This report is identical to the Quick Look Report, except that a double
space is provided.between print lines. This feature is especially useful when
the report is to be used as a turnaround document. The Quick Look and
Double-Spaced Quick Look Reports cannot be requested simultaneously.
Figure 8—3 is a sample of a Double—Spaced Quick Look Report.
8.1.4 Two-Line Quick Look Report
The ‘Two—Line Quick Look Report prints “the source’name (SNME), ‘street
address (STRT), city name (CYNM), state abbreviation (STAB), air program code
(APCD), air program status (APST), SIC code (SICC), source classification c”,
(CLAS), and source compliance code (SCMS) on the first line of a ‘Quick Looi
Report. The items selected by the user on the “40” card appear on the second
line of the report. The first line, containing only source information, will
print only once per source and is available both with and without suppression
and the use of the NOHD options.
Use “QD” (Quick Look Double Line) on the “20” card in place of “QL” or
“Q2.” Figure 8—3.1 shows a Two—Line Quick Look Report.
8.1.5 Source Data Report
The Source Data Report is the most comprehensive report available from the
Retrieval. All CDS/CEMSS data elements are included on this report for CEMS
sources only; this is the only report that gives complete source information,
source comment information, point information, point comment informat:
8—8
-------
QUICK LOOK REPORT
••......... . ....
OR/16/86 CONTINUOUS EMISSION MONITORING SYSTEM PAGE 3
CONFIDENTIAL REPORT — FOR EPA INTERNAL USE ONLY
SOURCES IN CEM SUBSET AS OF 0/14/86
S. ••S•• ........ •................S.. .e...............
ST CNTY SOURC PTNO CMI ANUM PTNO MONITOR REQO AGCO MONITOR MANUFACTURER CERT DYE MIND PSTD PERNIS EMIS LIMIT
...... ••........ • 5 •...e..........S..S... .......ee....S..e......
0011 311 0000 0011 MDX NSPS £PA—RGN LEAR SIEGLER 11/02/12 02/02 02/11 0.7 LIS/MOTU MDX
20. 0277 90006 0000 000 0000 0000 UNKNOWN UNKNOWN / / / /
0001 000 0000 0001 UNKNOWN UNKNOWN / / / /
0001 111 0000 0001 OPACITY NSPS EPA—RGN ENY. DATA COIPCEDC) 03/20/00 70/11 79/07 20 * OPACITY
0001 311 0000 0001 NOR NSPS EPA—RGN ENY. DATA CORP(EDC) 03/20/80 70/11 79/07 0.3 LBS/MBTU NOR
0002 000 0003 0002 UNKNOWN UNKNOWN / / /
0003 000 0000 0003 UNKNOWN UNKNOWN / / / /
0003 311 0000 0003 NOR NSPS UNKNOWN / / F / 0.7 LB/MSTU 3 HR PRO
20 oees 60005 0000 000 0000 0000 UNKNOWN UNKNOWN / / / /
0001 000 0000 0001 UNkNOWN UNKNOWN / / / /
0001 111 0000 0001 OPACITY NSPS EPA—RGN LEAR SIEGLER 06/11/81 81/04 81/06 33 * OPACITY
0001 211 0000 0001 SO2 NSPS EPA—RGN LEAR SIEGLER 11/17/81 01/03 lI/i l 39 GRAMS/SEC.
0001 511 0000 0001 MC NSPS EPA—RGN ITT BARTON 08/14/14 01/06 / S PPM/12 MR PERIOD
0002 000 0000 0002 UNKNOWN UNKNOWN / / / /
22 1291 00010 0000 000 0000 0000 UNKNOWN UNKNOWN / / . / F
0001 000 0000 0001 UNKNOWN UNKNOWN / / /
0002 000 0000 0002 UNKNOWN UNKNOWN / / / /
0501 000 0000 0501 UNKNOWN UNKNOWN / / F /
0301 141 0000 0301 OPACITY ENFORCE UNKNOWN PHOTOMATION / / 77/ 77/ 20* OPIC/6 MIN PERD
0501 151 00000501 OPACITY ENPORCE UNKNOWN PHOTONATION / / 77/ 77/
Fic ure R—3. 1)ot,ble-Snaced Quick Look Report
8—9
-------
OUICK LOOK REPORT
.... .. ..... ....
0 #â6 CONTINUOUS EMISSION
CONFIDENTIAL REPORT — FOR
MONITOR INFORMATION IN
. .. . ....
lOPING SYSTEM PACE 2
- INTERNAL USE ONLY
NEW JERSEY(TwO—LINE 01)
0 •••••••••••S••• • • . . . .e. . •• .S . • 0 ••
UNKNOWN
UNKNOWN
EPA—RGN LEAR SIEGLER
EPA—RGN LEAR SIEGLER
EPA—RGN LEAR SIEGLER
WYMAN STA.UNIT 4 CENTRAL
UNKNOWN
UNKNOWN
cPA—RGN £NV. DATA CORP(EOC)
tPA—RGN ENV. DATA CORPCEDC)
UNP NOWN
UNKNOWN
UNKNOWN
BOISE—CASCADE CORP.
UNKNOWN
UNKNOWN
EPA—RGN LEAR SIEGLER.
EPA—RGN LEAR SIEGLER
EPA—RGN ITT BARTON
UNKNOWN
BOSTON E0—L STREET
UNKNOWN
UNKNOWN
UNKNOWN
UNKNOWN
UNKNOWN PHOTOMATION
UNKNOWN PHOTOMATION
UNKNOWN PNOTOMAT ION
UNKNOWN
UNKNOWN
BOSTON ED—NEW BOSTON
UNKNOWN
UNKNOWN
UNKNOWN
UNKNOWN
EPA—RGN PP$OTOMATION
UNKNOWN
EP4— GN PP$OTOMATION
UNKNOWN
S IR—8B
SIR—88
S I R—88
ME 6
/
/ /
/ /
03/20/80
03/20/80
/1
/ /
/ /
/ / /
/ / /
I, / /
/ / /
77/ / /
71/ / /
77/ / /
/ / /
/ / /
/ /
/ / /
/ / /
/ / /
/ /
/ /
/ /
/ /
UNKNOWN
UNKN3 WP .
NSPS
NSPS
NSPS
2
UNKNOWN
UNKNOWN
OPACITY NSPS
NOX NSPS
UNKNOWN
UNKNOWN
NSPS
4
UNKNOWN
UNKNOWN
NSPS
NSPS
NSPS
UNKNOWN
UNKNOWN
UNKNOWN
UNKNOWN
UNKNOWN
ENFORCt
ENFORCE
ENFORCE
UNKNOWN
UNKNOWN
UN FM 0 UN
UNKNOWN
UNKNOWN
UNKNOWN
OPACITY OTPiER
UNKNOWN
OPACITY OThER
UNKNOWN
Figure 8—3.1. Two-Line Quick Look Report
T CNTT sOuRC ö TNO CHA ANUM SOURCE NAME STREET ADDRESS CITY NANC ST APCD APST SICC CLAS SCMS
AGCO MONITOR MANUFACTURER MONITOR MODEL MONITOR SERIAL MIND CUT OTE MONITOR REOD
...... 0 •
RM4 I
02011b6
5M810
0214470
SM8LO
0214470
MAINE
POWER
YUMOUTII
O lGA
SERIES
253d—1
DIGA
SERIES
2538—1
/
82/02
8 2/02
82/0 2
ME 9
/
/
/ /
., /
11/02/82 OPACITY
11/02/82 502
11/02/82 NOX
O 4911 Al
20 0211 ‘ 00O4
20 Odd, 60005
2 1291 00010
22 12’il 00012
0010
0011
0011
0011
0011
0000
000
000
111
211
311
000
0000
0000
0000
0000
0000
0000
3001
0 ( 101
3001
0002
0003
0003
u000
000
111
311
000
000
311
000
0000
0000
0000
0000
0000
0000
0000
0001
0001
3001
0001
0002
0000
000
111
211
511
000
000
0000
0030
0000
0000
0000
0000
3001
0002
0501
0501
0501
0501
0502
0999
0000
000
000
000
141
151
161
000
000
000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0001
0002
0501
0501
0502
0502
0999
000
000
000
111
111
0 0
0000
0000
0000
0000
000.0000
0000
0000
OXFORD PAPER DIV. RUMFOR&
78/11
78/11
/
/
RM4 1
S MB 10
411
0301534
04 036 5U
129
776 SUMMER ST BOSTON
NOX
0 2621 Al
/ /
/ / /
81/04 06/11/81
81/03 11/17/81
81/04 08/14/84
/ / ,.
MA 0 0 4911 Al
PACITY
S02
NC
3
OPACITY
OPACITY
OPACITY
776 SUMMER ST BOSTON
SIR—B
SIR—B
0 4911 Al 3
MA 0
/
11/03
/
71/03
/
8-10
-------
action comment information, and monitor and excess emission information.
Figure 8—4 presents a three page sample of a Source Data Report with both CDS
nd CEMSS data on it.
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 CEMSS Masterfile,
Source Data Reports by state provide an essential coding tool. For those
interested only in part of the Masterfile, report selection criteria can be
based on any retrievable data elements.
Although Source Data Reports can be sorted by any user—selected data
elements retrieval on the Masterfile, users should not select point or
action—level data elements as their major sort key. To produce a meaningful
report, users should kee.p all of the records for a given facility together by
sorting on the source level. If no user sort key is specified, Source Date
Reports are printed in the Masterfile sort order: region, state, county,
;ource, point, action number, and channel number.
8.1.6 Milestone Report
The Milestone Report produces a tally of data based on two data elements
selected by the user. Any two retrievable CDS/C 24SS data e.le’ments at the
source, point, or action level may be chosen. One data element determin the
rows produced; the other data element determines, the columns produced. Note
that the user chooses the row data element and that the 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 must supply the column data element and the specific values
for that data element. A maximum of 10 values will be accepted.
8—11
-------
SOURCE DATA REPORT
.....
03/14/86 CONTINUOUS EMISSION MONITORING SYSTEM PA ,E
CONFIDENTIAL REPORT — FOR EPA INTERNAL USE ONLY
DETAIL REPORT OF CEN SOURCES IN CEM SUBSET AS OF 8/14/86
COHN LIGHT I. PO 4!R FEOF NON—FED ROEI 1
STATE CT COUNTY FAIRFIELD APCO 0 SIP SOURCE OE
COUNTY 0265 SOURCE 00142 AQCR 043 CITY 0820 APST 0 OPERATING RD€3
...... ........• .
SOURCE NAME CONN LIGHT POWER - STATE REGIST 137—014 SIC 4911 ROE6
ADDRESS WOODWARD AV NEOS XREF 4214 RDE4 STAFP MEMBER
CITY, STATE NORWALK CT ooes PRIORITY 0 ROES LAST—UPDATE 1/24/86
COMMENTS: 1 HARBOUR STATION
2 ELECTRIC CO
3 FACILITY BURNS SOME PROPANE
........•.• .. ..e.•• .•••••••• •• .•••.. .•• ... ..•.•.• .
DUN & BRAOSTREET NO. CT09 10191407 SOURCE CL*SSIPICATION. Al SIGNIFICANT VIOLATION INO
SOURCE COMPLIANCE STATUS 3 IN COMPL—INSPECTION LOAD ORV A—ACTUAL
FACILITY CAPACITY ROE 9 ROE 10 ROE 11 ROE 12
POLLUTANT COMPLIANCE AQCR INDICATOR LOADING
PT PARTICULATE MATTER 2 IN COMPL—SOURCE TEST 2 NON—ATTAINMENT—SEC
S2 SULFUR OXIDES 2 IN CONPL—SOURCE TEST A ATTAINMENT AREA
NC HYDROCARBONS 0 COMPL STATUS UNKNOWN N NON—ATTAINMENT
CO CARBON MONOXIDE 0 COMPL STATUS UNKNOWN N NON—ATTAINMENT
N2 NITROGEN OXIDES 2 IN CONPL—SOURCE TEST A ATTAINMENT AREA
. .....• .......................S.................•......
POINT NUMBER 0000 MULT SOURCE CMPL 3 IN CONPL—INSPECTIDN STATE/LOC REGUL
PCLLUTANT SOURCE—SIP NO SCHEDULE ROET
DESCRIPTION ELECTRIC SERVICES CAPACITY SCCS CODE
COMMENTS: 1 STATE REGIS No:ooze,0030.OOIL
ACHV 2/ 3/77 ACT—TYPE AS
STAFF
NOV 86472 — 19—500—22(A)(2)
ACHY 10/ 3/77 ACT—TYPE 13
STAFF
ACHY 1/12/79 aCT—TYPE 13
STAFF
ACHY 2/16/79 ACT—TYPE 63
STAFF
ACHY 3/20/80 ACT—TYPE AS
STAFF
87613 — 19—500—20(A)(3)
ACHY 6/15/81 ACT—TYPE 13
STAFF
ACHY 5/ 7/82 ACT—TYPE 13
STAFF
ACHy 7/ 6/53 ACT—TYPE 13
Figure 8—
ource Data Report
CEM ACTION 0004
CEM
tEN
CEM
CEM
ACTION
ACT ION
ACTION
ACTION
SCP’O 2/ 3/77
COMMENTS: I
SCP4D 10/ 3/77
SCHD 1/12/79
SCHO 2/16/79
SCHO 3/20/80
COMMENTS: 1 NOV
SCHO 6/15/81
SCHO 5/ 7/82
0006
0007
0008
0009
0010
0011
CEM ACTION
CEM ACTION
STTE NOTICE OF VIOLATION
RESULTS
STATE INSPECTION
RESULTS
STATE INSPECTION
RESULTS
EPA INSPECTION OVERVIEW
RESULTS
STTE NOTICE OF VIOLATION
RESULTS
CEM acTioN 0012
SCHD 7/ 6/83
01 ACTION ACHIEVED
01 ACTION ACHIEVED
01 ACTION ACHIEVED
01 ACTION ACHIEVED
01 ACTION ACHIEVED
STATE INSPECTION
STATE INSPECTION
STATE INSPECTION
RESULTS
RESULTS
-------
.
05/14 , oo
MONITOR MANUFACTURER: BAILEY CERTIFICATION DATES LATEST PS, DATE:
MONITOR MODEL NUMBER: MONITOR REQUIRED FOR: UNRNOWN LATEST PST RESULTS
MONITOR SERIAL NUMBER: ENFORCEMENT AGENCY! UNKNOWN TOTAL PST PASSES: 00
MONITOR INSTALLED: /60 PERMISSIBLE (MIS LIMIT: TOTAL PST FAILS: 00
•..................e...S................. ...... .......... • ••
POINT NUMBER 0003 MULT 001 POINT CMPL 2 IN COMPL—SOURCE TEST STATE/LOC REGUL 19—S0S—22(*)C2)
POLLUTANT N2 POINT—SIP NO SCHEDULE ROE?
DESCRIPTION STEAM SIR BRNNG PES OIL CAPACITY SCCB CODE *0100403 -
••••............ ... ••...•....... . •.....................
SOURCE OSTA * T
••e•••SI••S•• .S•. .............. .. .S.... ....S.S...... ....................e............................... ......s..
CONTINUOUS EMISSION NO iiuRING SYSTEM PAGE 2
CONFIDENTIAL REPORT — FOR EPA INTERNAL USE ONLY
DETAIL REPORT O CEM SOURCES IN CEM SUBSET AS OF 9/14/86
CO’4N LIGHT C POWER FEOF NON—FED ROFI I
STATE CT COUNTY FAIRFIELD APCO 7 UNkNOWN RDEZ
COUNTY 0265 SOURCE 00142 40CR 043 CITY 0820 £PST 0 OPERATING RDE3
•.........e...e.............
STAFF RESULTS
CEM ACTION 0013 SCHO 3/20/86 ACHY 3/20/86 ACT—TYPE 13 STATE INSPECTION
STAFF RESULTS
CEM *CTIC* 0014 SCHO 3/ 6/83 ACHY 3/ 6/83 ACT—TYPE 13 STATE INSPECTION
STAFF RESULTS
.. . ... ..... .. ••••e•••••••••e••••S•ee••e .S . . . . . .S .......SS.S.. ••••.•.•................... ...
POINT NUMBER 0001 MULT POINT CMPL 4 IN CONPL—C(RTIFICATN STATE/LOC REGU!. 19—SOB—19(A)(2)
POLLUTANT SZ POINT—SIP NO SCHEDULE ROE?
DESCRIPTION STEAM SIR BRNNG RES OIL CAPACITY SCCS CODE 10100403
COMMENTS: 2 $6 OIL
. ••........... .........
POINT NUMBER 0002 MULT 001 POINT CMPL 2 IN COMPL—SOURCE TEST STATE/bC REGUL 19—SO8—18(D)(1)
POLLUTANT PT POINT—SIP NO SCHEDULE ROE?
DESCRIPTION STEAM SIR BRNNG RES OIL CAPACITY SCCS CODE 10*00403
COMMENTS: 2 CYCLONE C ELECTROSTATIC PRECIPITATOR
. .. S. •tS S .•e• •......S......................
**O CHANNEL NUMBER! 111
TYPE OF MONITOR: OPACITY
Figure 8—4. Source Data Report (Continued)
8-13
-------
SOURCE DATA U
0 •0•••00•. •0e••••0 0 0 0 0 0 0 0•• 0 0 1 0 0 0 0... 0••S
) . /14/86 CONTINUOUS EMISSION MONITORING SYSTEM PAGE 3
CONFIDENTIAL REPORT — FOR EPA INTERNAL USE ONLY
DETAIL REPORT OF CEM SOURCES IN CEM SUBSET AS OF 0/14/86
CONP4 iIGHT C POWER FEOF NON—FED ROE
STATE CT COUNTY FAIRFIELD APCO SIP SOURCE R0E2
COUNTY 0265 SOURCE 00142 AQCR 063 CITY 0820 APST 0 OPERATING RDE3
.. 0 • ..e...•e . 0S . .S .•••••• ........... . ..........................
POINT NUMBER 0004 NULT POINT CNPL 4 IN COMPL—CERTIFICATN STATE/bC REGUL 19— 508—19(A)(2)
POLLUTANT $2 POINT—SIP NO SCHEDULE ROE?
DESCRIPTION STEAM BLQ BRNNG RES OIL CAPACITY SCCS CODE 10100403
.
POINT NUMBER 0005 NULT 004 POINT CMPL 2 IN CONPL—SOURCE TEST STATE/LOC REGUL 1 —S0I—1$CD)(1)
POLLUTANT PT POINT—SIP NO SCHEDULE ROE?
• DESCRIPTION STEAM BLR BRNNG RES OIL CAPACITY SCCS CODE 10100603
COMMENTSI 2 ELECTROSTATIC PRECIPITATOR
*** CHANNEL NUMBER: 111
TYPE OF MONITOR: OPACITY
MONITOR MANUFACTURER: BAILEY CERTIFICATION DATE: LATEST PST DATE:
MONITOR MODEL NUMBERZ MONITOR REQUIRED FOR UNKNOWN LATEST PST RESULTS:
MONITOR SERIAL NUNB€RZ ENFORCEMENT AGENCY: UNKNOWN TOTAL PST PASSES: 00
MONITOR INSTALLED: /60 PERMISSIBLE ENIS LIMIT: TOTAL PU FAILS: 00
.. . .0Se• . . .S . .e• 0 0 .eS• . . . . . 0 0 0 0 0 0ee . .ee .............. 0 0 0 0 0. 0 0 0.....e.......
POINT NUMBER 0006 MULT 004 POINT CMP . 2 IN COMPL—SOURCE TEST STATE/LOC REGUL 19— 508—22(A)CZ)
POLLUTANT N2 POINT—SIP NO SCHEDULE ROE?
DESCRIPTION STEAM BLR BRNNG RES OIL CAPACITY • SCCI CODE 10100603
Figure 8—4. Source Data Report (Concluded)
8—14
-------
The totais produced by the Milestone Report reflect only data selected by
the retrieval. Users care should carefully prepare retrieval selection cards
so that the report produced is meaningful.
Figure 8—5 shows a tally of various monitor manufactuers state—by—state
basis in EPA Region VII.
8.1.7 Single—Spaced Milestone Report
The Single-Spaced Milestone Report provides the same information as the
normal Variable Milestone Report. The lines are single—spaced, which allows
for twice as many printed lines per page. To obtain this report, use “M l” on
the “20” card in place of “MS”. Figure 8.5—1 gives a sample of the
Single—Spaced Milestone Report.
8.1.8 Three Element Milestone Report
A third or controlling data element is available for use on the Milestone
Report. A page break will occur each time the values of this third
controlling data element changes.
To request a Three Element Milestone Report, enter “MS’ on the “20” card,
the same as for a regular Milestone Report. Enter the “SO’ ‘card as - for a
regular Milestone Report, and enter the third or controlling data element in
Columns 4 through 7 of the new “51” card (after the “50” card) to get the
Three Element Milestone Report.
Figure 8—5.2 gives a sample of the Three Element Milestone Report.
8.1.9 cE24S Statistical Report
The Cfl(SS Stat Report is a fixed—format report that provides elementary
statistical analysis for a selected portion of the CE24SS Masterfile. The
CI2 SS
8—15
-------
NILESTONt REPORT
. . . S
08/14/86 CONTINUOUS EMISSION MONITORING SYSTEM PAGE 2
CONFIDENTIAL REPORT — FOR EPA INTERNAL USE ONLY
SOURCES IN CEN SUBSET AS OP 8/14/86
.. . • .e..S.S. ..S . . .S•S.eS• .•ee .•Se•eS .S .. ••SS•Se••SS••eSSS•eS•••S•*e• S••S•••SS• . .. . ...e....S.S...
REGION 7 STAB STAR STAB STAB
MONITOR MANUFACTURER TOTAL IA kS MO NE
LEAR SIEGLER 53 33 13 7 0
LEEDS C NORTHRUP 1 0 0 0 1
ISI 18 0 3 11 4
M ASURU 10 2 S 0 0
NONE 2 0 0 2 0
TECO 2 1 O 1 ‘0
TELEDYNE a o o 2 , 0
THEMOELECTRON 1 0 0 1. 0
THERMOELECTRON 2 0 0 2 0
THERMOX 3 2 0 1 0
UNKNOWN 3 0 0 3 0
WATER TO FUEL RATIO 1 0 0 1 0
WESTERN RESEARCH 2 2 0 0 0
REGIONAL STAR TOTALS 2.249 747 izo 1,300 12
REGIONAL MANF ITEMS 3S
Figure 8—5. Milestone Report
8- [ 6
-------
v 1:STrN
.... .
(JItT UiL j’ c. I N M NIT 1N 5Y)T M 1
Z: —. F3D P II T PNAL us: 3 i1Y
S0U Ct 5 IN CCM SU SET AS O. 8/14/d
Rft 13P1 MtP4 v MINY MINT MINT MINT MINY MINT MINT MINT
MONITOR MANU ACTUR€R TOTAL P5 84 ‘ .3 82 81 ‘ .0 7 , .7.
2 0 :0 0 0 0 2 0 3
1 0 0 0 0 0 0 0 1
EOC 1 0 0 0 0 0 0 0 0 0
EUC/IsERMO LICTR0N 2 0 0 0 0 2 0 0 0 0 1’
ENV. DATA CORP(EDC) 2 0 0 0 0 0 0 0 0 2
ENv!RUNM NTAL DATA 2 0 0 .0 0 C 0 0 3
ITT AkTcjt 1 0 0 0 0 .0 1 0 0
LeAd It.l . 11 0 0 0 0 3
MONITUk LAô0RMT0RL S 2 0 0 0 0 0 2 0 0 ‘3
PPIOTQMAT ION 10 0 0 0 0 . 0 0 0 0 0 Ii
• :c,tG’ AL Mfl iY TOTAL) 34 0 0 0 j 7 0 7 ii
t0LuNAL MAN ITEMS 10
Figure 8—5.1. Single Spaced Milestone Report
8—17
-------
MILESTONE REPORT
....... S... ..
ud o CONTINUOUS EMISSION NI IRING SYSTEM PA&E 1
CONFIDENTIAL REPORT — FOR NT€RNAL USE ONLY
MONITOR INSTALLATION BY MANUFACTURER BY CHANNEL (3 ELE. MS)
S ••e••••S• S••••• .•••e••• .ee• S••• . . . ..... S S
LrI. N dEL DESCRIPTION OPACITY MINT MINT MINY MINT MINT MINT MINT PlINY MINT MINT
M )NITjR MAP4UF CTURER TOTAL 86 85, 84 83 82 81 80 7 1 78 77
BLANK 2 0 0 0 0 0 2 0 0 0 0
1 0 0 0 o o 0 1 0 0
EOC 1 0 0 0 0 0 0 0 0 0 1
EOC/Tpi RMJ ELCCTRON 2 0 0 0 0 2 0 0 0 0
NV. ..ATA CORP(cDC) 1 0 0 0 0 0 0 0 0 1 u
ENVIRONMENTAL CATA 2 0 0 0 0 0 0 0 0 2 0
Lt 8 0 0 0 0 1 1 0 6 ‘ 0
PPIcJTOMATIDN 10 0 0 0 0 0 0 0 0 0 Li
Ci14I NEL OMINY TuTALS 27 0 0 0 0 3 3 0 7 ‘ 3
CIi iNcL DMANF ITEMS 8
Figure 8—5.2. Three Element Milestone Report
8-18
-------
Stat Report provides ranges and mean of monitor unavailability, monitored
operation without exceedances, and reported operating time with exceedances.
Ranges, means, and percent of operating time. are available for total excess
emissions, monitor downtime, and their corresponding reason codes. The number
of sources, emission points, monitors, and EERs used to calculate these
statistics are included.
The above statistics are calculated for the entire country and for each
region by Source Classification Code and by each Cr24 monitor.
The user is allowed to select any portion of the CEMS Masterfile to be
examined. Following are examples of such selection criteria:
• Selection by monitor manufacturer (Lear Seigler)
• Selection by a specific Source Classification Code
• Selection by a specific monitor (opacity, SO 2 , etc.)
• Selection by state
• Selection by source.
Because the CEMS Stat Report is fixed—format, the 20 and 40 cards are
fixed format. A 30 card is not needed. The standard formats are shown below.
[ *101 LSiTi LII LLI 1$I 1OI 4 t’i
12 42 7s ion 21
[ 4101 FiLi qi&i r EiRj i crn P PkDI lXICJPi V OfNJPl LPIMIOIM IPiE Xj j , P ciPm
124 79 i214 17 22 4 27 3224 3739 4214T 47
[ II I I L1 j ( I I J i i III Li I I I IFI I U
49 12 J7j 62M 67e 7274 77 $0
Remember that the accuracy of the statistics produced arf in direct
relationship to the quality of the data entered.
Figure 8—6 shows an example of the CEMS Stat Report for electrical
services and opacity monitors throughout the nation.
8—19
-------
PAGE
CONTINUOUS EMI NS MON1TORIN SYSTEM
SAMPLE CEM STAT REPORT TESTINL (NEW)
REt !ONAL , nATIONAL REPORT
SUURCtS ACTIVELY SUE.MITTING ERRS
AS Of 08/15/86
REGION 11
TuTAL S. URCES 11 TCT L CHANNELS : 30
TOTAL !MISSION POINTS : TOTAL QUARTERS 121
CJI .TROL. :
TfPi MONITOR OPACITY MONITOR
NUM ER SOURCES 9 NUMcER CHANNELS : 15
NUMbEN CMISSIOP4 POINTS : 15 NUMbER QUARTERS 72
SOUwCE MONITOR MONITORED OPER. REPORTED DP R.
OPERATION (N) UNAVAILABILITY u/a ExC€ o. WI EXCtED.
3360— 165780 .100— .100
97442 .100
E xCE. s STAPTUP/ CLEANING/ CONTRCL E UIP PROCESS FUEL CTH R kNOW’
cIISSIONS SHUTDOWN SOOT BLOWING UNkNOWN €E FAILU —T3TAL PRO8LEMS PROBLEMS EXCESS MI5.
. ANGt : 9,9 99 0— •55140 0— 8 90O 0— 79001 0— 30000 0— 18420 0— 7 0- 3O J
McAN 2b64 10198 1819b 264184 58o 233073
TIME 2.939 10.4 *6 13.673 271.113 .601 23 .19)
M ONITJR MC NITOR NON—MONITOR UNkNOWN OTHER KNOWN
COwNTIME EQUIP MALF EQUIP MALF MONITOR DOWN CALIBRATION MONITOR DOWN
4ANGE 0— 3200 0— 65005 9— 10 0— 4800 999 9
H:AN : 290354 16175 18065 36615
TIME : 287.712 16.600 18.539 37.578
Figure 8—6. CEMS Stat Report
8— 20
-------
8.1.10 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
Report, and it is then sent to the state agency for completion. After the
state returns the coded report, the data is keypunched for reentry to the CDS
data base. Figure 8—6.1 shows an example of the Questionnaire Report.
8.2 Checklist for Request Submission
The following list of steps will guide users submitting requests for
retrievals. The list is sequential in that an inexperienced user would
proceed in chronological order. Section 8—3 provides details for each item in
this checklist.
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 user ultimately need?
B. Code the form.
1. Formulate a meaningful title for the report(s) and enter it on
the card line 01. The title will be printed on each output
page.
2. Create the selection logic (on Card 10) 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. If no selection is used, all facilities
on the Masterfile will be selected.
3. Select the best format from those available. Use more than one
if appropriate. Put the correct format on card line 20, using
the proper two—digit report abbreviation (QL for Quick Look, Q2
for Double Spaced Quick Look, QD for Two Line Quick Look, SD
for Source Data Report, MS for Milestone Report and Three
Element Milestone Report, Ml for Single Spaced Milestone
Report, ST for Statistical Report, DT for Detail Report, and QT
for Questionnaire Report).
4. Select the sequence of the items in the report, and fill in the
card line 30 on the form. If no sequence is specified, the
report will be in region, state, county order.
8—21
-------
u:STIONAIRt REPfl. T — REGION 2
CNTIt UDUS EN JN MONITORING U ScT 3
•...........................e.....e.... .•......... •••••••••.•.....................
* LEVEL DATA a • sCOS 10 •: 02—31—3060—00003 *
NAML: CIL CIEMICALS INC. STATc OF NJ COUNTY OF NI0QLE5 X AIR PROGRAM CODE:
ALi;.( SS: VALI R AV Ut
SAY vRLE NJ 08d72 AIR PROGRAM DESCRIPTION: N$P )TATE EGISTRLTI:N: lSdlI
AV YOU KCCEIVEU EERS FOR THIS SOURCE? YES — NO (CIRCLE ONE)
. .
POINT LEVtL DATA * a CEMS ID i: POZNT—0001 *
r JCESS L.c CRI?TIGN NSP SULFURIC ACID PLANT EMISSION POINT •: 0001 STATE REGULATION: SU8PT H,60.80
tHISSION POINT COMMENTS ADDITIONAL EMISSION POINT COMMENTS?
S • • • S • • S S S S • • • • • • • • •
-* MONiTOR LEVEL DATA * $ CENS ID •: CHAN—Zil *
i t .. aia
a D SC IPTION: 502 : MONITOR INSTALL. DATE (Yy/Ms): /
.jCrM aT A,,! .CY: STATE : PcQUjREMEP f FOR MONiTOR: P4SPS
l u . CrU ck: DUPONT : LATcST PST OATF yY/MM: 75/04
MONITOR MOJEL a: 460 1 LATEST PST STATUS (PASS/FAIL); PASS
MONITOR SLRIAL a: E73..31014—20 CERTIFICATION DATE (MM/OD/YY): / /
MONITC CC 4M NTS ADDITIONAL MONITOR COMMENTS?
UNIT NO. 1
S • S • S • S S S • S • • S S S • I S
$ POINT LEVEL DATA a $ CENS ID e: POINT—0002 *
oC s CRIPTLON: NSPS SULURIC ACID PLANT EMISSION POINT a: 00J2 STATc RE UL TION: SUBPT H,60.8O
Er 1 S.i P 1NT COMM_NTS ACOITIONAL EMIss:ON POINT CGMM NTS?
L _A 1a
Figure 8-6.1. Questionnaire Report
8-22
-------
tJzSIIUN3 : EP :’ 1 —
Cj at!4ujul tMI;ST: 1 acN;;:DI ; .st’ s ’
• . . . • • •0 •
.cos to s: Oz—3t—3060—00003
• • .
* MJN ITJa LEVEL DATA u * CUSS t O i: (HAW—211 C ’
tnFUkCEMENLA E’iCv: STATE
M’iITJR H uFMt7 i EK: :u?s1
: ‘.:n 4: . j
MJNITOa S :kIAL, .:tlJ.ij’)1A—13
El. . 1 IL IJE . I L — 1Q.. QQIII Q L I QEflII NL.. .S
£LIã 1LU _ 1Iâ
M.NITIQ I TALt. UAT! (VT /MM): /
Ré3UIREMENT C•3Q MDNIT R: NSPS
L. T:SI PSI TE CVT/ vlfl T5/0
— LàTf S T P$T JTAT.S (3A S/taTL): P35
: CEQTI&!CATION SAtE (MM//VT): /
• J iT C MM. NTS ‘J t1 :’ AL M NIT’Jc C JMMENTS?
i&CL@ UNIT NC.
* END OF DATA FOR C I I CHEMICALS INC. A * END OF DA l I F0 00003
Figure 8—6.1 Questionnaire Report (Concluded)
8—23
-------
5. Review entries on the form to see that all data element
abbreviations are correct.
8.3 Preparing Retrieval Selection Cards
To request reports from the Reporting Program, you should prepare a Report
Request form as shown in Figure 8—7. The Report Request form contains a
layout of the standardized retrieval card formats that will be submitted to
the central data center. In addition, the Report Request form contains
pertinent information needed in filling 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(s)
20 Report Format Card
30 Report Sequence Card
40 Quick Look Data Selection Card
50 Milestone Data Selection Card
51 Three Element Milestone Control
Data Element
Card 01 — Title Card
Card 01 has entry spaces for the card code number, region, -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. All users should use ‘00’ in this field. Currently,
unlike CDS retrievals, C 24SS retrievals are run for the entire country. To
get a regional retrieval, users must specify the region using the selection
criteria (Card 10).
The report title (columns 9—80) is the user—specified title, which will
appear on every page of the output report. Titles should be carefully ci n
8—24
-------
CONTINUOUS EMISSION MONITORING SUBSET REPORT REQUEST FCR,,1
I
(U
I
FT J
II
USTIF
II
1(D)
II
I I
II
I I
I I
-.
30
ill
LI
I I
I I
I I
I I
I I
I I
I I
I I
I I I
[ 1
II
II
II
1111
II
II
II
III
II
I I
it
If
liii
I I
II
II
ill
I I
I I
I I
II
liii
II
II
I I
III
[ 1 I I
I I
I I
I I I I
II I I I I
I I]
liii
Ii
111111
111111111
liii Ii
III I I
I
111111111
111111
11111
I
111111111
11111111111
I
111111111
I I I
11111111
I
11111
liii
I_Il
111111
II
I
III
II
I I
II
ill
ii
liii
II
I
III
II
II
II
III
II
lii i
II
I
III
II
Ii
II
(UNIT - 40 10 CARDS)
REPORT FORMATS
L2IOI t I I I I I I I I I I I I 1111
12 45 7$ loll
14
PASSWORD (Requ;red to Access
Confidential Data Liesents)
REPORT SEQUENCE
I3 _ IOI I 111111 I I I [ 1 111.11 IlillIllIll I I
124 79 1214 1719 2224 2729 32
(SEOU(NCE LIMITED TO 40 CNMACTUS)
QUICK LOOK REPORT FORMAT
14101 liii I I 111111111 II l 1111111111111 I II If I I LI I I I
124 79 1214 171 2224 2729 3234 3739 4244 47
1IIIIfIIlI IIIHIIIJ [ If liIIIlI U
49 1214 1759 6244 6769 7274 77 $0
ENTER DATA ELEMENTS TO SE INCLI CD ON REPORT 2 STOPS
LIMITED TO 132 CHARACTERS WITH MONO OPTION SUPPRESSION
LIMITED 10 104 WITH STANDARD HEADING
REPORT FORMAT
_______ 1111111 I 1111111111111111111111 Iii I 111111
12 14 17 19 22 24 27 29 32 34 37 39 42 44 47
COLUSeIS VALUES OF COLUNN DATA ELEMENTS I I I I I I I I I I I I I I I
CLEMENT (USE SLNK FOR BLANK VALUE) 49 52 54 17 59 62
Figure 8—7. Report Request Form
8—25
S’ee reverse side for a list of all CEM/CDS
data elements and their abbreviations.
DATE S BMI:E
RETURN REPORT TO ____________
J.J JJ [ J I I I I I I I I I I I I I I I I I I I I I I I I If I i
12 41 79 20 30
R(GIONLEV(LREPORTT ITI.( IiIfIItIiIiiiiii
51
REPORT LOGIC SELECTION
‘I
1I!III 1II IIII )I
40 50
J L1 I I I I I I I I I I I I
70
I0
LEVEL CODES (01 CARD)
REQUIRED FOR SD REPORT ONLY.
VALID ARE:
S - SOURCE ONLY
P POINT AND SOURCE
A - ALL DATA (Default)
C - CRITERIA MATCH ONLY
- I1If I
12 4 OATA 7
CLEMENT
W iiIIl
WQMI II I
[ lip, I I I I I
11101 I I I I I
11101 LI _ I I I
I _ ! _ I J 11 I I I
L _ ! _ 1.OJ I I I I I
I 11OI I I I I I
11101 I 1 I I I
[ 1101 LI I I I
11111
[ 1101 11 I I I
11101 1 I I I I
U”,
9 Ii
COND. VALUE
UI ’
U
U
U
U
U
U
U
U
U
U
U
U
CONDITION CODES (10 CARD)
N *JST EQUAL
A - ALTERNATE (used for multiple
values of a given data element)
U UNEQUAL
6 - EQUAL OR OREATER THAN
L EQUAL OF LESS THAN
P - PRESENT ANY ENTRY
B BLANC OR ZEROS
L1LOI IIIIIU
REPORT FORMATS (20 CARD)
flOC for all
reports is CDWTVL
QL - QUICI LOOX
Q2 - DOUBLE SPACW QL
QD - NO LIII! QL
SD - SOUBCE DAZA REPORT
1 15 — KLL TON! REPORT
Ml — SIIIGL! SPA LRETONE
ST — STATISTICAL IDORT
DT - DETAIL REPORT
QT — QUI$TIQP A1I1 REPORT
21
N er of Subtotaling Data
Elesents on Qu)ck Look
ST ONE
1,111 ,
12 4 7
ROWS
DATA
ELEMENT
15111 11111
12 4 7
-------
ICeS IOTA 11.1110 11
lIMItS UI lihi I )
DATA 50 6 )S Sp,rlAs.
ANSI 5Th 0*01 60 LASS CIIANS
t.n,rflt Ins ties...
11111105 OP 016 111
5*0* 500)0
AIU 1 10 1 CASO 00 CANt 11,051
I
8*15 COOl
0*18 COOS DSICSIPTIOP
• 1 1 PUOSIAII sTATUS
m ,taTui Dc$cIIpT Ioa
all *1.ITT COUTTOI. 510100
I oNIC 101.1.111*1 1 ? IaIONJIATIOU
iv CODS
CI0 1 5AIlE •
C0 t! CODE
(OONTI PAIlS
0*11 LAST UPDATED
005 * SIAOSTNIIT 11.55015
PACILITT CAPCITT
GOVI IENTAL IACILIT? CODE
lOADING DIIIVATIOS COOS
5501 CIOSI-SI11511CI 5181115
PO4.LVYAPT All QUALITI COlOSSI. INDICATOI
POU. IITANT COOS - SOASCI
P01 .UITAPT C18IPLIADCE STATUS
POU.VTANT LOADING
05105 1 ? ? CODS
101105 COO!
IUICS-STAT E-COU STT
*01:0
*roi
AP I?
* ,so
* Cl
SPLT
cyco
CT01
COT?
CT01
UODA
DING
PCAP
P OOP
LDSC
HESS
PAQC
PLLT
00 53
1.0*0
OSlO
1161
SCSC
5
a
a
a
S
3
I
S
1
S
S
S
•
S
S
5
I
S
1
S
S
5
1
I
so
I
ii
I
20 1 60
I I
4
1.)
0
IS
I
I
I
I.
2
I
1
I
2
6
S
3
I
ii
S
61
9
101
S
18
9
I
H
S
S
S
‘
S
S
6
S
5
9
- SIGIOP-DTATI-C 00 0 0 0-SOUSC E
UGI L DATA 11.11110? I
510 155*1 DATA 11.0511? 2
UOI L DATA SLEIUIT 3
ISCS
IDES
IDES
IDE)
3
S
S
$
3
I
I
I
I .
S
S
S
110IIIAL DATA 11. 11510?
8006
$
2
6
55550011. DATA ILCUST S
SOS ?
N
S
6
11116011. DATA 51. 05151 6
50 5*
0
10
II
S10I 1. DATA 01.0111? 5
SDE
I
1
850155*1. DATA IL NT 50
SOlO
5
2
5
U01 I. DATA SI0110T II
S OIl
S
2
5
NI L DATA 11.051111 Il
EDIT
S
I
HIC COOS
5 5CC
5
6
5
SIC 0001 DISCIIPTIOI
IICD
1
30
3 5
CLASSIPICATIOO S
CLAD
0
2
5
could CLA3SIOICATI 20 GNGUP
CLAC
S
I
3
bliNd C11IPLIANCI STATUS
5085
5
I
SOUlCE C11SPLIAJCE STATUS DISCIIPTIOU
ACID
1
20
21
SOUSCE C11IPLIAICE STATUS — I 051*11180
5650
5
I
11
1011561 CEIPLIASICS STATUS I I ? QUAITU
DCI I-
$
I
S
TN IOU O O
SCONCE C11IPLIAICI STATUS - STI QUAITTI
SCSI
I
I
SOUSCI 52151
51111
5
20
7I
5061CI 52311 $ 101?
$1515
$
10
II
50USd 0 111515
lICE
3
5
6
SlAP? 12111 — 500565
STPI
I
0
‘6
STAY, 0 551081111. C C CI — SCOOtS
0113
$
3
STATE AISSITIATIOI
STAN
1
STATS COOS
SITE
1
2
S
STATE-COU I 1T—SOUICI
ITCI
3
II
- -
STATS SSGISTSATIOU 5188551
flOG
$
IS
IA
STUIT *005111
fliT
5
20
21
TIP COOS
ZIPC
I
5
6
CAPACITY CODS
CASt
P
5
COMPLIANCE STATUS COOl
CIIST
P
I
S
COMPLIANCE STATIJA DEOCEIPT 100
0505
P
20
25
511111100 POSIT 5511111
OTTO
P
6
5
IIS1.TIPLI CAOS 5-5IP1IIICE
I0.ILT
P
3
S
OLD COMPLIANCI STATUS - S QUASTESS
OCSO
P
I
9
OLD COMPLIANCE $TAWI - IS! QUAIT II
OCII
P
I
S
111 100501
OLD COMPLIANCE STATUS - 5111 QUAIT$N
OC$I
P
I
S
POLLUTAIV COOS - POINT
PLUT
P
5
S
PSOC 1 511IAL COIPLIANCI
COlDS
P
I
S
0 5O ct55 DSSCIIPTIOU
PODS
P
20 23
26
ISCIOIAI. DATA 11.0111? 1
P 507
P
I
3
DCC S-DIGIT CODS
ICC)
P
5
ICC A-DIGIT COOS
ICCA
r
a
DCC a-DIGIT COOS
SCCI
P
I
9
SIP COOS
SSPC
P
I
S
SIP COOSDSSCIIP IIOU
$105
P
SO
SI
-TOTS SIGULASIOA
SILO
P
I I
IS
A. TIOP 0 51CSIPTIUP
*011
2
I ?
IN
l.T ION 811155 1
*11111
A
6
1101 $TAOP COOl
PlEA
A
5
5
TISI TYPO
*111
A
2
• lolL PENALTT II01VPT
PITT
A
0
II
AT! £0811050
OTAC
A
a
UATE ACII5N5D YEAS
DAT!
*
I
S
SlATS ACII IVIO TEAL 051055
Dal I
DAlI 50110111.1$
5050
A
6
9
DAYS SCIIDULU TIAI
IS IS
A
2
5
DATE VL11 TEAIfl51Sm
55
a
6
5
UGIOIAL DATA 51 I
ISPOIT OOAS1jl
0510
A
A
S
o
S
S
$5 551.11 CODS
HSSULTS COOS DSICSIPTIOP
ITAC
5550
A
A
5
IS
3
6
STAPP PAlS — ACTION
Sift
A
IS
.6
STAPP TITLE
CON 1l ?OICDJI INT ACING!
TIT1.
ACCT
A
CP
5
I
IS
S
CON INFOICESIENT ACIICT DISCSIPT IOI
AGCO
CO
I
H
CIITIPICATIOI DATE
ClIP
CP
0
9
CISTIPICATION 010Th
CS11I
C,
2
5
CISTIPICATIOII 11*1
COST
CP
2
5
(11*11511. 1551111
CHAP
CO
3
3
CHANNEL 51.11058 DSSCNIPTION
CHAD
CO
1
9
CHANNEL 5111515 58051
CHAD
CP
I
S
TINS 01 1100 - *1.1. CHA151LS
TCSC
CA
3
•
lIMO P1 5100 - CHANSIL I
TCNI
CA
3
.
TINE 01 5 100 - CHANNIL S
TCN2
CA
3
.
TINS 0 ( 5100 - CIlASIlI. S
SCS I
CA
3
.
TINS 0 1 1100 - CHAJINIL 6
TCHO
CA
3
i
TINE P1 1100 — CHALISIL S
TCSS
CA
3
•
TIllS P1 1100 - CHANIII. A
TIIIA
CA
3
•
TINE 01 1100 • CHAIIPSL 7
?CN7
CA
5
.
TINS 011 100 - CAAPUEL $
TCIS
CA
3
-
TIllS 0 15 100 - CNAIISL V
TCNH
CA
S
•
IPSTALLAT0OS OATS
HIND
C,
A
INSTALLATIOP 15 )0Th
111158
CO
S
S
ISITALLATION TEAS
MINT
CO
2
5
lTQI IIANS AC!I1II$
SAP,
CO
20
2
0155105 NOOSL SOSIIIS
l OSS.
C,
IS
IA
0151T0 1 SIIIAL 015155*
1551.
CP
IS
6
5111505 OP TESTS
PSIC
CO
2
3
1105151 00 PASSES
PSI?
CO
2
3
1151151 OP PAILS
P151
CP
2
3
PSSSSIIL.I 01155100 LIMIT
0111
CO
20
2’
PIT 5511
PITT
CO
6
6
PIT NSNTI
P1155
CO
2
5
OS? TIAS
PITT
CO
2
5
PAT STATUS
POTS
CO
6
5
NGUIIO5 EIQUIIIIIEIST CODE
110?
CO
I
S
I10I UQUIIDUNT COOS 01 5CIIPTIOM
NZ$0
CO
7
H
0100105 *VAII.ASILIT? PISCES?
0015
CA
6
A
l 05 TI51 SOO ISCO 5DA PEI 5T
POP?
CA
4
6
& ATINS SOM 5Oi ’*It 110085 !
PIS.C
CA
6
A
A5 PUS NECSU 1N$tOM 5
SOCT
. CA
54
55
fla .01 1T 0..
ITAS
CA
6
7
PTAIT-UP/SNUTOO.I, PIECIS?
PITA
CA
A
I
C1.$*0ING/ 100? 51.00111
SOOT
CA
A
S
CLIADIPG/ 500T 11.01 156 PENCIl?
PSOO
CA
A
S
I UCEIS 01111105
SlIP
CA
6
7
UCEIS 01151105 01SCSNT
Polls
CA
A
S
?11S . S$IJIIlSIT PAIL TOTAl.
£QYT
CA
6
‘
000505*. EQUI15UI? FAIl. TOTAL PUCINT
01$?
CA
6
8
P I1I P5051.0 13 IISACCEPT TOTAL
USC
CA
6
7
0 0 0 6*13 P0051.015 IIACCIPT TOTAL OUtSIT
P001
CA
A
H
I58 5rf P I15 050 5 1.018
CA
4
7
015001 ? VIACCEPT PIOCSS5 P0151.055
0000
CA
6
I
P1 05055 .13 1 1
.
CA
6
7
P . 00001.011 PISCES?
0105
CA
6
H
01105 EXCESS 011131055
CA
a
OTOU 501*55 011*51015
.
CO
I
S
IQ5II T I55LD10C?IIU
Ca
a
:
I10S I$0I11 ? I55& ?10U PIICUT
1515-01PITOM S$UI 1T P .ALPTJNCTIUN
8005
11110
C i
--
A
S
—Im0ltOI S$01 T 55U TI0I PSICEST
CA
A
I
CALI SS*TIOU
CAtS
Ca
A
CALISSATOON P10101?
SCAt
ca
6
9
111011031 0011 lIDS T 051
lOll
CA
6
•
15101105 IOSITOS X05TINS PISCES?
-
CA
6
9
0151* 150031 IOIITOS 001015501
CA
6
7
P 5501ST OTISS S I IOIITOS 00 111TII11
CA
6
9
OOUITCI 000SITINE IPCI118T
•I•
CA
S
•
STAT 1-CO IJ ITT-SOU IC I-POIPT-C I SANS IL
5C
c
ii
..
TUS 015100 IPSIIOD/NIIDTISI
CA
I
7
TUS CONVEISIOP hUG
IL lS
CA
1
7
TOTAL EICSSS 01111100
SIC,
CA
•
TOTAL ITOS ?I111
CA
a
‘
TOTAL *00011 OPWTING TINS
CA
S
NL& 1 IS NPACIS)
$LA01 I III SPACU)
11*1
51.52
.
C
In the Data Type COIUSIS . S indicat.. Source Level Dala P. indicat.. Point Level Data. “A indicates Action lav.l Data,
CP” indicates ChannelPoint Level Data, and CA indicate. Chann.l Action Level Data. In the Speciet Characters co uThn.
0 C” tndicates a Confidential Data Element and 0 R” indicates a Repeating Date Element.
Figure 8-7. Report Request Form (Concluded)
0 -
-------
and should include an English—language description of the selection criteria
to identify the various printouts produced. Experience has shown that if a
number of reports are prepared without adequate titles, it is difficult to
remember the specific criteriafor 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 40 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 condition codes are identified by the abbreviations shown in
the box in the center of the request form. For. example, the abbreviation for
region is “REGN.” The use of other abbreviations will cause an error, and the
run will be aborted. Only the data elements indicated in the table can be
used for logic selection purposes.
The condition code (column 9) is used to specify how the data element is
selected. The entry is a single alphabetic character selected from the codes
shown on the right side of the form. A brief explanation of the codes follows:
• M — Must Equal. A record will be excluded unless it equals the
val ie specified in the value field. When testing for a value of
blank, use the condition code M with no value entry in columns 11
through 30.
• A — Alternate. This code provides the capability of including
records with different values for the same data elements. For
example. three states might be selected and all given the
condition code of A on three separate 10 cards. The output report
would include the data for all three states. If an M had been
used, no output would be received because clearly no record will
match all three state codes. For example,
8—27
-------
• 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 are desired.
• G — Equal or Greater Than. Use this code 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 important, it can be
used with the date scheduled or date achieved file to provide a
chronological range. The date should be entered in month, day,
year sequence. For example, the following entries would provide a
range between January 1 and the end of 1980.
11101
12
i 1qcj
4 7
L J
9
I I I
liii I I i_•I •I
11
(!i J
DATA
T
COND.
z-
VALUE (Left Justified)
ib2&.31, ..ii.,iiiiii
i
• L — Equal or Less Than. This code is the opposite of the G code
and includes items equal or less than the value specified. If a
comparison is made using a field that is either alphabetic or
blank, the results will depend on the exact entries found in the
data base. Letters will compare lower than numbers, and blanks
will compare the lowest.
• P - Present—Any—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—30.
• B — Blank. This is the opposite of the P code and will qualify an
entry if the specified field is completely blank or zero. No
value entry is required. Use the condition code M to select only
blanks or only zeros.
Value field (columns 11—30) is used to enter the actual value to be used
for comparison with the data base. In some cases, this is he 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 iztm ediately to the right of the retrieval abbreviation for that
data element. If a data element has fewer than eight positions, the number of
digits in columns 11 through 30 must correspond exactly to the number
8—28
-------
digits on the data element. For example. if a selection is based on state
code, only columns 11 and ‘12 may be used on the selection card.
If a data element, such as Source Number, is a five—digit field, 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 has ‘more than 20 digits, the Retrieval will base its
selection logic only on the first 20 positions of Source Name. No value may
be made on the selection card beyond column 30.
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—3l, two alternate entries must be made to obtain both results.
Card 20 - Report Format Card
This card, which allows the region to select up to three output formats in
a given run, must be included. The codes to be used are shown below. Entries
should be made in columns 4—5, 7—8, and 10—11. Start with the left most
field. The available report formats are as follows:
QL - QUICK LOOK
Q2 - DOUBLE SPACED QL
QD - TWO LINE QL’
SD - SOURCE DATA REPORT
MS — MILESTONE REPORT
Ml - SINGLE SPACED MILESTONE
ST — STATISTICAL REPORT
DT - DETAIL REPORT
QT - QUESTIONNAIRE REPORT
The cataloged procedure “CF2.ISRTVL” is executed for all CD4SS Retrieval
Reports desired C 4SS report.
8—29
-------
The same password valid for CDS is also valid for the CEMSS. Passwords
must be used for all SD reports and for obtaining confidential data on Q
Look and Milestone Reports. The back of the Retrieval Request form and
Appendix A specify which data elements are confidential and which are not. To
obtain the appropriate password, contact the national DBC at FTS 382—2881.
Card 30 — Report Sequence Card
The report sequence card permits the user to select the sequence of
entries on the selected reports. 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: region, state, county, source, point, action number, and
channel number for all reports’ (a 30 card is not needed for a CEMSS Stat
Report).
Entries are made using the four-digit abbreviation for individual a
elements shown on the second side of the Retrieval Request form. For example,
to sequence by source name, ‘SNME’ is entered. Care must be used in limiting
the length of the sequence elements to 40 digits. For example, a sequence of
source name (20 digits) and process description (25 digits) would result in a
fatal error because the sequence length is 45 digits. However,, the use of all
six possible sequence entries with SIC Code (5 digits), Federal Facility Code
(1 digit), Pollutant (2 digits), and SIP Code (1 digit), would total 11
digits, well within the 40—digit limit.
Note that in certain cases it is possible to request a meaningless report
because of illogical sequencing. For example. a user sequence of data
scheduled, especially on a Source ‘Data Report, would, results in the action
records of several sources being separated and grouped away from their
sources. However, the date schedule sorting within a source may be ach d
8—30
-------
by requesting a sequence of source number followed by date schedule. This
request would keep all the actions with the correct source. A rule of thumb
is 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 is critical for Source Data Reports and CEMS Detail
Reports. Because Quick Look Reports are one—line reports for which no line
must be related to any other line, they may be sequenced in any manner with no
problem.
Page breaks and subtotals are available on the Quick Look Report by
placing a number ranging from 1 to 6 in column 39 of Card 30. For example, if
column 39 of the Card 30 is left blank, no page breaks are produced. A ‘1’ in
column 39• will produce a page break on the first data element of Card 30. A
2’ in column 39 will produce a page break on the first two data elements of
Card 30. A ‘3’ in column 39 will produce a page break on the first three data
elements of Card 30. Page breaks can be obtained on a maximum of six data
elements.
REPORT SEQUENCE
t3101 SiTiTiEj is iQiCjRi 111111111 i i i I I I I Number of Subtotaling Data
124 7 1214 171w 2224 272 32
(SEOU(NCE LIMITED TO 40 CI4ARACT(RS)
The above card will provide page breaks with subtotals by state and by AQCR.
Card 40 — Quick Look Data Selection Card
Card 40 provides a means of requesting specific data elements for
inclusion on the single line printed for each selected source, point, or
action on the Quick Look Report output. Data elements should be entered from
left to right in the same sequence as required on the report. The data
8—31
-------
element abbreviations used should be the same as those shown on the second
page of Figure 8—7 (use the standard card 40 shown in 8.1.6 for a C 4SS S
Report).
Note that state, county, source number, emission point number, action
number, and channel number will automatically be placed at the leftmost side
of the line by the system. However, if the user does not wish to have these
elements on the Quick Look Report, these data elements can be suppressed by
coding ‘NOHD’ in columns 4-7. The total Quick Look print line length is
determined as follows:
• With the NOHD option. up to 132 print positions are available.
The sum of the digits listed in the column for number of digits —
Card 40 of the Report Request form must equal 132 or less for the
data elements.
• . With the regular heading of state, county, source, point, action
number, and channel number, up to 104 print positions are
available. The sum of the digits listed next to each selected
data element in the number of digits — Card 40 column of the
Report Request form must equal 104 or less for the data elements.
If the data elements on Card 40 require more space than is available on
the 132,—character print line, the Quick Look Report will not be’ produced.
Data elements are printed left to right in the same sequence they are coded,.
Card 50 — Milestone Data Selection Card
Card 50 provides ‘a means of requesting the row and column data elements to
be shown on the Milestone Report. Data element abbreviations should be the
same as shown on the second page of Figure 8—7. The first data element
determines the columns. Column data element values should be entered from
left to right in the sequence desired on the report.
8—32
-------
If users desire to have all blanks as one of the column values, they
should enter ‘BLNK’ as the corresponding .value on Card 50.
Note that Card 50 will be rejected if a Milestone Report was not requested
on Card 20. It is the presence of Card 50 that causes the Milestone Report to
be produced. If a Milestone Report was requested on Card 20 and no Card 50 is
found, no Milestone will be produced.
To produce a Milestone Report showing the number of actions for action
types Ml, ML and M3 for all the counties within a state, perform the
following steps:
1. Choose an appropriate title on a Card 01
2. Use a Card 10 to select the appropriate state
3. Use Card 10 to select the desired action types
4. Code MS onCard 20
5. Code Card 50 as follows:
rCit4iT1Y, 11 q 1 r P 1 E 1 iMiji i i iMi2i I i urli3i i i r i i i i i i i i r i i i i i i i t i
I 2 4 7 9 12 14 17 $9 22 24 27 29 32 34 37 39 42 44 47
ROWS COLUI9IS VALU(S COLIJ N DATA (L N(NTS I I I
(LtNEJIT (L(N(NT 49 52 54 37 59 42
This request will produce four columns of numbers — one column for each of
the selected action types. On the left—hand side of the page, totals are
generated for all actions for a given county. One line is produced for 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 10 values may be coded on Card 50 — 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 element values to
be totaled are greater than four positions, totals are produced only on the
Eirst four positions of the specified data element values.
8—33
-------
Card 51 — Three Element Milestone Data Control Card
The 51 card selects the third controlling data element on the Miles
Report. A page break occurs for each value of the controlling data element.
Only one data element may be selected on the 51 card.
8.4 Job Control Language for Using Retrieval Program
The CDS Retrieval Package operates on a Remote Job Entry basis at the
EPA ’s National Computer Center. Input must be submitted from a high—speed
terminal. Frequent and complicated requests should be stored on a WILBUR data
set. To submit a job requests add the JCL cards shown in Figure 8-8 or 8—9 to
Cards 01.. 10, 20, 30, 40, 50, and 51 on the Retrieval Request..
Use the JCL in Figure 8-8 for producing all CEMSS Reports. Figure 8-9
shows an example of this JCL for producing a CEMSS Detail Report and
Figure 8-10 shows an example for producing a C 4SS Statistical Report.
8.5 Retrieval Edits Performed by System
The Retrieval Program edits the request Cards 01, 10, 20, 30, 40, 50, and
51 to determine if they are convertible into logic that the system can
process. Errors on the request cards will appear as error messages on the
Edit Report. These error messages are classified as warning’or fatal.
Table 8—1 lists the type of edits performed, the correct possibilities,
and the action taken by the system if an error is detected.
Table 8—2 contains a list of all possible error messages and causes of
their appearance on the Retrieval Edit Report.
8—34
-------
FIGURE 8-8
1.
2.
3.
4.
5.
6.
7.
8.
9.
‘10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
/ / 111CM
/ *RO JTE
/1*
/1*
//*
/1*
/1*
/1*
I/a
‘20
30
40
50
51
FIGURE 8-9
CEMSS DETAIL REPORT JOB CONTROL LANGUAGE
1.
/ 1 1 1 1CM JOB (MAACDSYP,MIII), ‘USER NAME’ ,TIME=2
2.
/*ROUTE PRINT RMTNN
3.
/ /*
.
4.
// USE THIS JCL ONLY FOR CM DETAIL REPORT
5.
// CHANGE
III TO YOUR USERID
6.
.
/ / * ., ‘ MM TO YOUR ACCOUNT
7
//* •, MIII TO YOUR BOX
8.
/ / * USER NAME TO YOUR, NAME IN
9.
1
/1* NN TO YOUR R 4OTE NUMBER IN LINE 2
or replace RMTNN with your N
number designation for the new
printers where available
10.
//*
11.
//GATRTVL D EC CEMSRTVL
12.
//SYSOO5 DD *
13.
01 00 RETRIEVAL REQUEST CARDS
14.
10
15.
20 DT
16.
30
RETRIEVAL JOB CONTROL , LANGUAGE
JOB (AACDSYP.MIII),’USERNAME’,TI . (O7)
PRINT RMTNN ‘
USE THIS JCL ONLY’FOR QL’s, MS’s AND SD ’s
CHANGE III TO YOUR USERID
AMA TO YOUR ACCOUNT
MIII TO YOUR BOX
USER NAME TO YOUR NAME IN LINE 1
NN TO YOUR REMOTE NUMBER IN LINE 2
or replace ’RMTNN with your N
number designation for the new
printers where available
//a
//CMTRTVL EXEC C 4SRTVL
//SYSOO5 DD *
01 00 RETRIEVAL REQUEST CARDS
10
-------
FIGURE 8—10
CEMSS STAT REPORT JOB CONTROL LANGUAGE
.1. / 1111CM JOB (AAMCDSYP.MIII),’USER NAME’ .TIME=(0 ,7)
2. ./*ROIJTE PRINT RNTNN
3 //*
4. // USE THIS JCL ONLY FOR QL’s, MS’s AND SD’s
5. // CHANGE III TO YOUR USERID
6. J/* AMA TO YOUR ACCOUNT
7. /1* MIII TO YOUR BOX
8. //* USER NAME TO YOUR NAME IN LINE 1
9. // NN TO YOUR REMOTE NUMBER IN LINE 2
or replace RMTNN with your N
number designation for the new
printers where available
10. //*
1.1. / /CEMSRTVL REPORT EXEC CDISRTVL
12. //SYSOO5 DD *
13. 01 00 RETRIEVAL REQUEST CARDS
14. 10
15. 2OST PASSWORD
16. 40 TIME OPER ROCT BPMD EXCP MONP MOAV OOSC MOSC
FIGURE 8—10.1
CEMSS QUESTIONNAIRE REPORT JOB CONTROL LANGUAGE
1. //1 11CM JOB (AAAACDSYP,MIII),’USER NAME’ ,TIME=2
2.. / *ROIJTE PRINT RMTNN
3 //*
4. /I . USE THIS JCL ONLY FOR CM QUESTIONNAIRE REPORT
5• // CHANGE III TO YOUR USERID *
6. / / * AMA TO YOUR ACCOUNT
7. /1* MIII TO YOUR BOX
8. //* USER NAME TO YOUR NAME IN LINE 1
9. //* NN TO YOUR REMOTE NUMBER IN LINE 2
or replace RZ4TNN with your N
number designation for the new
printers where available
10. //*
11. //CE24SRTVL EXEC CEMSRTVL
12. //SYSOO5DD *
13. 01 00 RETRIEVAL REQUEST CARDS
14. 10
15. 20 QT
16. 30
8—36
-------
TABLF °-l
RETRIEVAL PA - E EDITS
Correct Possibilities
One or None
Listed on input form
M,A,U,G,L.P,B
1. Anything
2. Numeric for numeric items,
i.e., REGN, SSTE, CNTY,
SRCE, PTNO, ATPE, DTSC,
DTAC, STAC
3. Number of digits less than or
equal to number of digits on
input form
0 to 40
Table 8—1. Retrieval Package Edits
8—37
Card
Type
01
10
Item Checked
Number of 01 Cards
Data Element
Condition
Value
Number of 10 Cards
Action in Error
Only first Card 01 accepted
Fatal — processing stops after Edit
Fatal — processing stops after Edit
1. Ignored if not blank for
condition
2. Fatal — processing stops after
• Edit
3. Fatal if the wrong length is used
Fatal — Processing stops after Edit
20
Report Format
1. QL, Q2, QD, MS, Ml, SD,
DT
1.
Processing will
continue if at
ST. QT. Up to three reports
at
least one
valid format
are available from one
retrieval
Number of 20 Cards
one •
Fatal — Processing
stops after
Edit
30
Report sequence
Valid abbreviations from the
Report Request form
Fatal — Processing
stops after
.
Edit
Data element
Total of 40
Fatal — Processing
stops after
Edit
sequence length
-------
TABLE
RETRIEVAL PACKAGE wj.a S (Continued)
Correct Possibilities
One or None
Valid abbreviations from the
Report Request form
Total length (including one
blank between each item) is
132 with NOHD, 104 without NOHD
1. One if QL format requested
2. Zero if no QL format
requested
50 Milestone data
elément
Column values.
Relation to other
cards
Number of 50 Cards
51 Milestone Control
data element.
List on input form (BLK1, BLK2)
excluded
Must be present
1. MS must be requested on
20 card
One or none
List on input from (BLK1, BLK2)
excluded
Fatal — processing stops after Edit
at least one valid format
Fatal — processing stops after Edit
Fatal — processing stops after Edit
MS format request ignored
Fatal — processing stops after Edit
All General card type 01, 10, 20, 30, 40, 50, 51 Fatal — processing stops after Edit
Table 8—1. Retrieval Package
Edits (Concluded).’
Card
Type
01
40
Item Checked
Number of 01 Cards
Quick Look Data
element
Length
Number of 40 Cards
Action in Error
Only first Card 01 accepted
QL format request ignored
QL format requested ignored
1. QL format requested ignored
2. QL format assumed (if only one
40 Card)
8-38
-------
8.6 W1 LBUR Interactive Retrieval Technique
In sowe cases, the amount of C 4S retrievals may not justify the creation
an interactive retrieval program for regional or state minicou puters. For
those users, there is available a W?LBUR Interactive retrieval technique;
The interactive features are as follows:
• Screen prompting for all retrieval cards
• Edit capabilities
— Internal edits
— After each card is entered
— After all cards are entered
• Restart capability if dropped from NCC
• Capability to add to or change an already created WYLBUR file
• Save data on WYLBUR file
• Automatic job submission.
An example of the retrieval prompting is shown in Figure 8—11. To use the
BUR Interactive to create a Retrieval Program. perform the following:
• Sign on to the appropriate user ID and account
• Type CE24SRTVL
• The screen prompting begins.
8—39
-------
7-415 E>EC ‘ILL avip R r: M PETPIE%’i
ErfrEP E C I 1 PE O iE TO E iC 1ES A 3E
j: .RETRIEV L .TATE ir S), REGID 1A .. ‘R) O N TIO1 L R
EI4TER REPORT TITLE <0—72 CHARACTERS)....
TITLE —: CE!’1S SUBSET 0IJICV LOOK REPORT
1. 01 00 A CEMS SUBSET QUICK LOOK REPORT
IS THIS LINE CORRECT (YES DR tiO) —>YES
CaRD 10 S.ELECTIQI CRITERIA
ENTER DATA ELEI4ENT ABBREVIATION DR RETIJRN —> TAB
ENTER 5ELECTIO”1 COIDITIUN — A (OR), U (U:4EOUAL). M ‘ EOUAL).
G (GREATER T F;M), L (LESS TH 1i), F (PRESENT), B (BLAt-K CR ZERO)....
ENTER 1 CHARACTER C ’JrIDITIO9 —>M
ENTER 1—20 DIGIT SELECTIO i VALUE —>IA
3. 10 STAB M IA
IS THIS LINE CORRECT (YES OR MO) —>YES
DO YOU WISH TO ENTER Rr4OTHER SELECTIOr4 CRITERIA (YES OR 140) —>110
CRRD 20 REPORT FORMAT(S)
ENTER THE REQUIRED REFCRT
QUICKLOOK REPORT (QL OR 02)
2 LINE QUICKLDOK (OD)
MILESTONE REPORT (M5)
SI1iC-LE SPACED MILESTONE (Ml)
CEll DETAIL REPORT (DT)
SOURCE DATA (SD)
STAT REPORT (ST)
QUESTIDt4RIRE REPCRT (QT)
ENTER REPORT TYPE —>QL
ENTER ANOTHER REPORT TYPE OR RETURN —>
4. 20 QL SUBSET
————+————1 ———— ————2————+————3————+————4———— ———— ————+——— ————+—
DO YOU !I5H TO ‘JDIFY THIS LINE? —>110
Figure 8—11. WYLBUR Interactive Retrieval
8—40
-------
:A D 30 - REPORT CEOJENCE
TER ‘HE ‘. C’4A ACTER DATA ELEMENT RBBRE IATIDN
EACH SORT FIELD. MAJOR TO MINOR. DR RETURN —>STAB
iiTER THE 4 CHARACTER DATA ELEMENT ABBREVIATION
OF EACH SORT FIELD. MAJOR TO flINOR. OR RETURN —>SMME
ENTER THE 4 CHARACTER DRTR ELEMENT ABBREVIATION
0F EACH SORT FIELDS MAJOR TO MINOR. OR RETURN —>
ENTER SORT PR5E BREAMS (1—6) DR RETURN —>
5. 30 STAB SN E
DO YOU P,IISH TO MODIFY THIS LINE? — NO
CARD 40 — QUICK LOOK REPORT FCR 1AT
ENTER NDHD ID SUPRESS THE STAN Rpr4 HERDING REGION,
STATE. COUNTY, SOURCE NUMBER. POINT NUM ER. CHANNEL
NUMBER AND ACTION NUMBER DR RETURN —>NDHD
ENTER THE 4 CHARACTER DATA ELEMENT ABBREVIATION (EXCLUDING NOHD)
OF EACH ABBREViATION QF EACH QUICK LOOK FIELD. DR RETURN — >STAB
ENTER THE 4 CHARACTER DATA ELEMENT ABBREVIATION (EXCLUDING NOHB)
OF EACH ABBREVIATION CF EACH QUICK LOCK FIELD. OR RETURN —>SNME
ENTER THE 4 CHARACTER ORTA ELEMENT ABBREVIATION (EXCLUDING NOHD)
J EACH ABBREVIATION OF EACH QUICK LOOK FIELD, OR RETURN —>APDS
ENTER THE 4 CHARACTER DATA ELEMENT ABBREVIATION (EXCLUDING NDHD)
OF EACH ABBREVIATION OF EACH QUICK LOD FIELD, OR RETURN ->MANF
ER THE 4 CHARACTER DATA ELEMENT ABBREVIATION (E CLUDIMG MOHD)
EACH ABBREVIATION OF EACH QUICK LOOK FIELD. OR RETURN —>P1IHD
ENTER THE 4 CHARACTER DATA ELEMENT ABBREVIATION (EXCLUDING NDHD)
OF EACH ABBREVIATION O EACH QUICK LOOK FIELD. OR RETURN —>
ENTER ‘2 TO CANCEL STANDARD....
CJJPPPES IO OF SOURCE IN O DR RETURN —>
6. 40 NDHD STAB SMME R DS MANE MIND
JO YOU L’ISH TO MODIFY THIS LIME? —>
ENTER YES OR NO
DO YOU ISH TO MODIFY THIS LINE? —>MO
DO YOU 1SH TO LIST THE DATA JUST ENTERED (VES OR HO) ->YES
01 00 A CEMS SUBSET QUICK LOOK REPORT
10 REGN N 0?
3. 10 STAB N JR
4. 20 QL SUBSET
5. 30 STAB SNME
6. 40 NOHD STAB SMME ARDS NA 4 MIND
EnTER 4 DIGIT ACCOUNT NUMBER (E>. Ao 6)—>Aoa6
ENTER RD IDENTIFIER (EX. CDSYP)—>CDSYP
ENTER 4 DIGIT BIM’BD (EX. MGEO)—>MCDS
ENTER PRIORITY (DEFRU T IS 4) —>2
ENTER EST. TIME (FORMAT NIN.SEC). DEFAU .T 30 SECS ->
ENTER YOUR RE 1OTE NUMBER (NNN). DEFAULT 20 —>37
JO YOU L ISN TO SUBMIT A LIVE FETRIEVAL (YES OR NO) —>YES
JOB 3784 CDSCM SUBMITTED
JO YOU L!ICH TO SAVE THIS D TR? (YEs DR tiJ) ->YEC
ER DATASET NAME TO :A E RE DRT ON — >RT\ Q
! . 1A\ ED AID CATL ’D ON J5R013
Figure 8—11. WYLZUR Interactive Retrieval (Concluded)
8—41
-------
TABLE 8-2
RETRIEVAL PACKAGE ERROR MESSAGES
Error Message Cause
FATAL — INVALID RETRIEVAL CARD Card Type not 01, 10, 20, 30, 40, 50,
or 51.
WARNING — DUPLICATE TITLE (01) CARD More than one 01 Card entered; only the
first one is accepted.
FATAL — OVER 40 SELECTION CRITERIA Limit of forty Type 10 Cards exceeded.
FATAL — INVALID DATA EL 4ENT Four-digit data element abbreviation
does not correspond to any listed on
input form. This error can occur on
Card Types 10, 30, 40, or 50.
FATAL - INVALID CONDITION The condition code entered on Card Type
- 10 was not M, A, U, G, L, P. B.
WARNING - VALUE NOT USED FOR An entry was made in the value portion
COND P OR B of Card Type 10 with a condition of P
or B. These conditions do not utilize
any value.
FATAL — THIS VALUE MUST BE NUMERIC An alphabet letter was entered in ti
value portion of Card Type 10, which
requires a numeric value, e.g., the
value for DTSC must be a date
consisting of six digits (0—9).
WARNING - VALUE TOO LONG The number of digits entered in the
(TRUNCATED) value portion of Card Type 10 was
larger than the number of digits
specified for that data element on the
list on the input form.
WARNING - INVALID REPORT FORMAT A code other than QL, Q2, SD, or MS
WILL CONTINUE IF ANY VALID FORMATS was entered on Card Type 20.
WARNING - QL FORMAT ASSUMED A Card Type 40 was entered, but QL was
not requested on Card Type 20. Qi will
be assumed as entered.
8—42
-------
TABLE8—2
RETRIEVAL PACKAGE ERROR MESSAGES (Continued)
Error Message Cause
FATAL — REPORT FORMAT (20) CARD No Card Type 20 was entered. This
REQUIRED card type is required.
WARNING - QL (40) MISSING, QL No Card Type 40 was entered, although
DELETED QL was entered on Card Type 20. QL
report format is ignored.
WARNING — QL TOO BIG, QL DELETED The total length of the QL line is
greater than 104 digits with the
default header information, or it is
greater than 132 digits with NOHD.
FATAL - DUPLICATE FORMAT (20) CARD More than one Card Type 20 was entered.
FATAL - DUPLICATE SEQUENCE (30) More than one Card type 30 was entered.
CARD
FATAL - SEQUENCE KEY TOO LONG The sum of the number of digits of the
data elements requested for the user
sequence (Card Type 30) was greater
than 40.
[ AL — INVALID MS DATA ELEMENT Only source-level data elements may
cvc BO be requested on a Milestone together
with repeating pollutant data on a Card
50.
FATAL - REPEAT AND POINT OR The Card 40 may specify only source-
ACTION ON QL level data together with repeating
pollutant data on the Quick Look.
PASSWORD NOT ACCEPTED - NO Either no password was used or an
CONFIDENTIAL DATA WILL BE PRINTED incorrect password was used. No
confidential data will be selected.
sorted, or printed on any output report.
PASSWORD HAS BEEN ACCEPTED — When a correct password is used, each
CONFIDENTIAL REPORT — FOR EPA output report page is labeled as
INTERNAL USE ONLY confidential.
FATAL - *NOHD* USED ONLY FOR NOHD was used as other than the first
QL REPORT data element on the QL Card Type 40.
8—43
-------
TABLE 8-2
WARNING
ONLY
RETRIEVAL PACKAGE ERROR MESSAGES (Continued)
Error Message Cause
FATAL - *BPLT* CAN NOT BE IN
SORT KEY
4ARNING - BAD LEVEL, SD FORMAT
DELETED
WARNING - SD TYPE DELETED, LEVEL
MISSING
- LEVEL FOR SD FORMAT
WARNING - DUPLICATE QL (40),
QL DELETED
FATAL - ROWS DATA ELEM 4T INVALID
FATAL - COLU 4S DATA ELEMENT
INVALID
FATAL - COLU JS DATA ELEMENT
INVALID
FATAL - NO X VALUES SUPPLIED
FATAL - MS NOT REQUESTED 50 INVALID
FATAL - MS NOT REQUESTED 51 INVALID
BPLT (55 Char. Length) is larger than
the maximum 40 characters allowed for
the sort key.
An invalid SD report level code was
entered the SD report will not be
produced.
No level was specified for the SD
report, the report will not be produced.
The SD level code was entered with no
SD report requested, report requested
will be produced.
Multiple QL 40 cards were entered, no
QL report will be produced.
An invalid data element (not in CDS or
CEMS data element table) was requested
for the MS rows data element. The 1
report will not be produced.
An invalid data element (not in CDS or
CEMS data element table) was requested
for the MS rows data element. The MS
report will not be produced.
An invalid data element (not in CDS or
CEMS data element table) was requested
for the MS cOlumns data. element. The
MS report will not be produced.
No data element was requested for the
rows data element on the MS 50 card.
The MS report will not be produced.
A MS Card Type was entered with no MS
report requested. The MS report will
not be produced.
A MS Card Type 51 was entered with no
MS report requested. The MS report
will not be produced.
8—44
-------
TABLE 8-2
RETRIEVAL PACKAGE ERROR MESSAGES (Continued)
Error Message Cause
FATAL - CONTROL DATA ELEMENT INVALID An invalid data element (not in CDS or
CEMS data element table) was requested
for the MS control data element. The
MS rAport will not be produced.
FATAL — STANDARD MILESTONE NOT MS report was requested with no Card
AVAILABLE Type 50. This CDS standard MS report
is not available in CD S. The MS
report will not be produced.
MASTER FILE OUT OF SEQUENCE- The master file records are not in the
PREVIOUS KEY IS proper order. The last record in
sequence is displayed. The reports
will not be produced.
WARNING — DUPLICATE MS (50), MS Multiple card type 51’s were requested
DELETED for a MS report. The MS report will
not be produced.
WARNING — DUPLICATE MS (51), MS Multiple card type 51’s were requested
IETED for a MS report. The MS report will
not be produced.
WARNING — CONFIDENTIAL, MS A confidential data element was
DELETED . requested on the MS report with no
password entered. The MS report will
not be produced.
WARNING — CONFIDENTIAL, WILL A confidential data element was
BE IGNORED requested on the Card Type 30
(sequence) or the card •type 40 (QL).
The data element will not be used on
this report.
WARNING - INVALID TIME CHANNEL An invalid time period code has been
PERIOD requested in the card type 10
selection. The selection will not be
used for this report.
FATAL - CONDITION MUST BE N A channel time period was used in the
FOR MUST EQUAL card type. 10 selection with a condition
code other than “N” for “Must Equal”.
The report will not be produced.
8—45
-------
TABLE 8-2
RETRIEVAL PACKAGE ERROR MESSAGES (Continued)
Error Message
.
.
Cause
WARNING — DUPLICATE TIME
•
Multiple card type 10 selection cards
CHANNEL CARD
were requested for the same channel.
Only the last selection entered will be
used.
•
FATAL - TIME CHANNEL VALID
ON
A selection channel time period code was
CARD 10 ONLY
.
•
used on a report request card other
than a card type 10. The report will
not be produced.
WARNING - CHANNEL TIME OF
NOT COVERED
P
.
.
The time period code is “P’. The EER
data for time period “P” has not been
converted. The EER data is printed as
entered.
8—46
-------
APPENDIX A
CEMS DATA ELEMENT DICTIONARY
A.l Point Level Data Elements
A.2 Action Level Data Elements
A.3 Other Data Elements
-------
APPENDIX A
CE2 S. DATA EL JT DICTIONARY
Data Element Abbr. Data Type
Point Level
CEM Enforcement Agency
CEM Enforcement Agency Description
Certification Date
Channel Number
Channel Number Description
Emission Point Number
Installation Date
Monitor Manufacturer
Monitor Model Number
Monitor Requirement Code
Monitor Requirement Code Description
Monitor Serial Number
Number of Tests
Number of Fail
Number of Pass
Permissible Emission Limit
PST Date
PST Status
Action Level
A. 1-1
A. 1-2
A.l-3
A. 1-4
A.l-6
A. 1-7
A. 1-8
A. 1-9
A.1—lO
A.1—1].
A. 1—12
A. 1—13
A. 1—14
A. 1—15
A. 1—16
A. 1—17
A. 1—18
A. 1—19
A.2
A.2-3
A.2-4
A.2-5
A.2-6
A.2-7
A.2-8
A.2-9
A.2—1O
A.2—11
A.2—].2
A.2—13
A.2—14
A.2—15
A.2—].6
A.2—].7
A.2—18
A.2—19
A.2—12
A. 2—21
A.2—22
A.2—23
A. 2—24
A. 2—25
26
AGCY
AGCD
CERF
CHMJ
CHAD
PTNO
MIND
MANF
MODL
REQT
REQD
SERL
Y ’ r ”
PSRF
PSRP
EMI S
PSTD
PSTS
ATPE
DTAC
DTSC
PERA
STAC
RDE8
AN
RQTR
PMON
POPT
P cC
ROCT
SOOT
PSOO
EQPT
PEQP
EQPU
PEQU
PROC
PPRO
PRUN
PPRU
STAR
PSTA
ENUN
PEXU
P (Point
P Level)
P
P
P
p
P
P
P
p
P
P
p
V
P
P
P.
P.
A (Action
A Level)
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
Action Type
Date Achieved
Date Scheduled
Action Staff Code
Results Code
Regional Data Element 8
Action Number
Report Quarter
Monitor Unavailability
Monitored Operation without Exceedances
Reported Operating Time with Exceedances
Reasons for Excess Emissions
Cleaning/Soot Blowing
Cleaning/Soot Blowing (Percent)
Control Equipment Malfunction Total
Control Equipment Malfunction Total (Percent)
Control Equipment Malfunction Unacceptable
Control Equipment Malfunction Unacceptable
(Percent)
Process Problems Total
Process Problems Total (Percent)
Process Problems Unacceptable
Process Problems Unacceptable (Percent)
Startup/Shutdown
Startup/Shutdown (Percent)
Unknown Excess Emissions
Unknown Excess Emissions (Percent)
—ii—
-------
APPENDIX A
CEMS DATA ELEMENT DICTIONARY
Data Element Abbr. Data Type
Action Level (Continued)
A.2-27 Fuel Problems FUEL A
A.2—28 Fuel Problems (Percent) PFUE A
A.2—29 Other Known Excess Emissions EEOT A
A.2—30 Other Known Excess Emissions (Percent) PEEO A
A.2—31 Number of Incidents of Excess Emissions EEIN A
A.2-32 Reasons for Monitor Downtime BPMD A
A.2—33 Calibrations (Quality Assurance) CAL l A
A.2—34 Calibrations (Percent) PCAL A
A.2-35 Monitor Equipment Malfunctions MOEQ A
A.2-36 Monitor Equipment Malfunctions(Percent) PMOE A
A.2-37 Non-monitor Equipment Malfunctions NMEQ A
A.2-38 Non—monitor Equipment Malfunctions (Percent) PNNE A
A.2—39 Other Known Monitor Downtime MOOT A
A.2-40 Other Known Monitor Downtime (Percent) PMOO A
A.2-4 1 Unknown Monitor Downtime MOUN A
A.2-42 Unknown Monitor Downtime (Percent) PMOU A
A.2-43 Number of Incidents of Monitor Downtime MOIN A
A.2—44 Time Period Code TIME A
A.2—45 Total Excess Emission xc A
A.2-46 Total Monitor Downtime MONP A
A.2—47 Total Source Operating Time OPER A
Other Data Elements
A.3-l Region Code REGN SP,A
A.3-3 State Code STTE S.P,A
A.3—5 County Code CNTY S.P,A
A.3-6 Source Number SRCE S.P,A
A.3-7 Card Code -- SP,A
A.3-8 Comment Line Number S,P,A
A.3—9 Comments S,P.A
A.3-lO Update Code S.P,A
(S=Source Level)
(P=Point Level)
(A=Action Level)
(S,P,A,=All Levels)
—iii—
-------
A.1
POINT LEVEL DATA ELEMENTS
-------
CEM ENFORCEMENT AGENCY
inition: CEM’ ENFORCEMENT AGENCY is the state or Federal agency with
enforcement jurisdiction for the continuous emissions monitoring
installation.
52
27
. 1
Justified
Required
on New Entry
t iona ily
Controlled
Edit Error Messages:
* AGENCY CODE MUST BE 1-4
= Fatal Error
Coding Considerations :
Code one of the following values:
blank UNKNOWN
1 EPA-HQ
2 EPA—RGN
3 STATE
4 LOCAL
Data Dictionary
A.1-1
AGCY
Valid Values:
1—4, blank
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
ALPHANUMERIC
NO
.
•
Masterfile
Record Type
34
.
.
.
Masterfile
NO
Position
96
•
Masterfile
:
N/A
Length
1
* = Warning Error
-------
• C 4 D rORCEMEN’r AGENCY DESCRIPTION
English language
Retrieval
Abbreviation
Data
Type
1
2
3
4
blank
AGCD
EPA-HQ
EPA-RGN
STATE
LOCAL
Valid Values:
Data Dictionary.
A. 1-2
Definition :
C D I ENFORCE2 JT GENCY’ DESCRIPTION ,‘is the
translation of the enforcement agency code.
Card
Type
‘
N/A
Card
Columns
N/A
Data Element
Length
7
ALPHABETIC
‘
‘Justified
LEFT
‘ Masterfile
Record Type
N/A
‘
;
Required • •
on New Entry
N/A
Masterfile
Position
N/A
•
•
:
,‘
Nationally
Controlled
•
N/A
Masterfile •
Length
,
N/A.
‘
Edit Error Messages:
,
•
•
‘
= Fatal Error
* = Warning
Error
Coding Considerations :
-------
CEM POINT DATA IDENTIFIER
Definition:
CEMS POINT DATA IDEMTIFIER is a system generated identifier to
indicate that there isCEMS datapresent at aCDS point.
Retrieval
Abbreviation
C 4P
Card
Type
N/A
Card
.
Columns
N/A
Data Element
Length
1
Data
Type
ALPHANUMERIC
Valid Values:
System—generated for CDS points
with CEMS data (cards 51, 52, 70,
71. 72) associated with them.
CE2IS points will be indicated by
a ‘C’ in the CEMS POINT DATA
IDENTIFIER.
Justified
N/A
•
Masteruile
Record Type
34
Required
Masterfile
New Entry
N/A
Position
87
Nationally
Masterfile
Controlled
N/A
Length
1
.
Edit Error Messages:
.
= Fatal Error
= Fatal Error
* = Warning Error
Coding Considerations :
Data Dictionary
A.1—2.l
-------
Definition :
CERTIFICATION DATE is’: the
certification.
CERTIFICATION DATE
date the monitor ‘receivé5
Valid Values:
Must be numeric and a valid
date “MMDDYY” DD = DAY
MM = MONTH YY = YEAR -
Data Dictionary
A.l-3
Retrieval
Abbreviation
CERF, CERM,
CERY
Card
Type
.
52
.
Card
Columns
61—66
-
.
Data Element
Length
.
6
Data
Type
NUMERIC
Justified NO
Masterfile
Record Type
34
.
.
Required
Masterfile
.
on New Entry NO
Position.
250-255
Nationally
Masterfile
.
.
Controlled NO
Length
6
Edit Error Messages:
* INVALID DATE VALUE
= Fatal Error
* =Warnirig
Error
Coding Considerations:
CERF — refers to the
entire
six—character field
CERM — refers to the
month
field
CERY — refers to the
year field
-------
Definition :
CHANNEL NUMBER
CHANNEL NUMBER is a three digit numeric code used to uniquely
identify a CEM monitor.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Fatal Error
Coding Considerations :
For data referred to specific monitors, the following rules apply:
Column 24 identifies the parameter being monitored and is numeric.
= Opacity Monitor
2 = SO 2 Monitor
3 = N0 Monitor
• 4 — Diluent Monitor
• 5 = Hydrocarbon
6 = Tot reduced SO 2
7 = Hydrogen disulf
8 = Carbon monoxide
9 = Coal Sampling and Analysis
Column 25 is numeric and identifies the type of data being entered.
1 = Monitor data
9 = Excess Emission Reports (EER) data
= Warning Error
Data Dictionary
A.l-4
CHAN
Valid Values:
51,
52,
60,
70,
71,
72, 80
24—26
3
NUMERIC
Justified
N/A
Masterfile
Record Type
34, 35, 46, 47
Required
on New Entry
YES
.
Masterfile
Position
18-20
Nationally
Controlled
YES
Masterfile
Length
3
it Error Messages:
-------
CHANNEL NUMBER (Continued)
Column 26 is numeric (1—9) and is dependant on the value of column 25:
D AMPLE: See Section 5.3.5 for examples of proper point/channel
assignment.
a. If column 25 = 1, column 26 represents a particular monitor
in a multiple monitor installation and is numeric. For
example, if a unit has two opacity monitors on the same
emission point, the first would be. coded “111” and the
second coded as “1l2” . . . .
b. If column 25 = 9, column 26 indicates the type of emission
data being entered/present in CEMS, is numeric, and, at
present, is limited to the following codes:
5 = Percent reduction (% RDX) for SO 2 and NO
9 = Excess emission reports (EER) for all pollutants.
Data Dictionary
A.1-5
-------
Definition :
CHANNEL NUMBER DESCRIPTION
CHANNEL NUMBER DESCRIPTION is the. English language translation
of the first digitof thechannel number.
Coding Considerations:
Column 24
1 =Opacity Monitor
2 = SO 2 Monitor
3 = NO Monitor
4 — Diluent Monitor
5 = Hydrocarbon
6 = Tot reduced SO 2
7 = Hydrogen di8ulf
8 = Carbon monoxide
9 = Coal Sampling
If column 25 = I.
Column 26 = a particular
monitor in a multiple
monitor installation.
1 = first monitor
‘2 = second monitor etc.
If column 25 =
26 = type of
data entered.
5 = Percent
(%RDX) for
NOR.
9 = Excess Emission
Reports (EER) for all
pollutants.
Retrieval
Abbreviation CHAD
Valid Values:
Card
Type
N/A
Card
.
Columns
N/A
Data Element
•
Length
15
• Data
Type ALPHANUMERIC
Masterfile
•
• Justified
LEFT
Record Type
N/A
.
.,
Required
on New Entry
N/A
Masterfile
Position
N/A
Nationally
Masterfile
Controlled
N/A
Length
N/A
it Error Messages:
.
= Fatal Error
.
* = Warning Error
Column 25 Column 26
1 = Monitor data
9 = EER data
Data Dictionary
A.l-6
9, column
emissions
Re duct ion
So 2 and
-------
EMISSION POINT NUMBER
Definition :
EMISSION POINT NUMBER is a four digit numeric emission’ point
identifier. If one physical emission point produces several
pollutants, each pollutant is assigned to separate emission’
point number. Emission point 0000 refers to the entire
source. S
Retrieval
Abbreviation
PTNO
Card
Type
‘
,
10, 51,
70, 71,
52,
72,
60,
80
Card
Columns
14—17
Data’ Element
Length
4
Data
Type
NUMERIC
Valid Values:
0000, 0500 through 0599
Justified. LEFT
Masterfile
Record Type
20—47
‘
.
Required
on New Entry ‘ YES
Masterfile
Position
14-17
.
‘
Nationally
Controlled NO
Masterfile
Length
‘
4
Edit Error Messages:
‘
‘
“ EMISSION POINT MUST BE ZEROS
POINT NO. MUST BE GREATER THAN
*** EMISSION POINT MUST BE NUMERIC
ZERO
0
= Fatal Erro’r
* = Warning
Error
Coding Considerations :
Point number must be zero for card type 10. It must be greater than zero
for cards 51, 52. 60, 70, 71, 72, and 80.
Enter the CDS emission point. If an emission point does not exist’ incDS
for the EER being entered, an emission point must be entered through CDS.
An emission point cannot be added to CD I, see pages 5—14 through 5—16 for
an explanation of how the point number should be matched to the channel
number.
Data Dictionary
A.1-7
-------
init ion :
INSTALLATION DATE
INSTALLATION DATE is the date on which the monitor was installed
and is in year/month format. :
Valid Values:
Numeric and a valid date
? 24 MONTH YY = YEAR
Data Dictionary
A1—8
Retrieval
Abbreviation
.
.
MIND, MINM, MINY
Card
Type :
.
52
Card.
:
Columns
49—52
Data Element
Length
4
Data
.
Type
NUMERIC
u.y j.s
.
Justified NO
Masterfile
Record Type
.
34
.
Required
on New Entry YES
Masterfile
Position
102—105
.
tionally
ntrolled NO
.
Masterfile
Length
4
Edit Error Messages:
.
.—
A INVALID DATE VALUE
= Fatal Error
* Warning
Error
Coding Considerations:
MIND — refers to the
MINM — refers to the
MINY — refers to the
.
entire four—character field
month field
year field
-------
MONITOR MANUFACTURER
Definition :
MONITOR MANUFACTURER identifies the manufacturer of the primary
component of the monitoring unit.
Retrieval
Abbreviation
MANF
Card
:TYPe
51
Card.
Columns
27—46
Data Element
Length
20
Data
Type
ALPHANUMERIC
Valid Values:
Al]. alphanumeric characters.
Justified
N/A
.
Masterfile
Record Type
34
‘
Required
on New Entry
N/A
.
Masterfile
Position
.
186—205
‘
Nationally
Controlled
N/A
Masterfile
Length
:
20
.
Edit Error Messages:
= Fatal Error
* = Warning Error
Coding Considerations :
When one or more monitors is attached to a physical emission point,
separate channel numbers should be assigned for each pollutant monitored.
Data Dictionary -
A.1-9
-------
finition :
MONITOR MODEL NUMBER
MONITOR MODEL NUMBER identifies the type àf monitor in use.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
= Fatal Error
Coding Considerations :
See Monitor Manufacturer for applicable comments.
Data Dictionary
A.1—l0
MODL
51
Valid Values:
All alphanumeric characters
47—61
15
ALPHANUMERIC
Justified
N/A
Masterfile
Record Type
34
Required
on New Entry
N/A
.
•
Masterfile
Position
206-220.
.
Nationally
)ntrolled
N/A
Masterfile
Length
15
Edit Error Messages:
. * = Warning Error
-------
Definition :
MONITOR REQUIREMENT. CODE
the continuous monitor.
MONITOR REQUIREMENT CODE
states the regulation type requirinc’
52
28
1
.
.
Mast e rf i 1 e
Record Type
Masterfile
Position
YES
Masterfile
Length 1
Justified LEFT
Required —
on New Entry NO
Nationally
Controlled
Edit Error Messages
* REQUIREMENT CODE MUST BE 1—5
= Fatal Error * = Warning Error
Coding Considerations :
Code on the following values:
blank UNIQ4OWN
o SIP
3 ENFORC NT ACTION COMPLIANCE ORDER OR CONSENT DECREE
5 OTHER
6 PSD
9 NSPS
34
97
Data Dictionary
A.l—11
REQT
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Valid Values:
0, 3, 5, 6,9, BLANK
ALPHANUMERIC
-------
MONITOR REQUIR ENT CODE DESCRIPTION
Definition: MONITOR REQUIR rr CODE. DESCRIPTION ‘is ‘an English language
description of the’;requirement code.
Retrieval . . Valid Values:
Abbreviation REQD
Card ,‘
Type
:,
N/A
Card
.
Columns ‘
N/A
Data Element
Length
7
Data
Type ‘ ALPHANUMERIC
.
Justified
LEFT
Masterfile
Record Type
N/A
Required
on New Entry , ,
N/A
Másterfile
Position
N/A
,
‘ T t’ionally.
r trolled
N/A
Masterfile
Length
N/A
,
Edit Error Messages:
,
= Fatal Error
‘
* = Warning Error
Coding Considerations :
o — State Implementation Plan
3 — Enforcement Action
S — Other
6 — Prevention of Significant
Deterioration
9 — New Source Performance
Standard
Data Dictionary
A.l— 12
-------
Definition :
Retrieval
Abbreviation
Card
Type
Ca rd
Columns
Data Element
Length
Data
Type
• MONITOR SERIAL NUMBER
MONITORSERIAL NUMBER positively identifies a unit.
May be used to determine replacements.
= Fatal Error
Coding Considerations :
See Monitor Manufacturer for applicable comments.
= Warning Error
Data Dictionary
A.l— 13
SERL
51
Valid Values:
All alphanumeric characters
62—76
: 15
ALPHANUMERIC
Justified
N/A
.
Masterfile
Record Type
34
.
Required
on New Entry
N/A
Masterfile
Position
.
221—235
.
•
‘•
Nationally
Controlled
N/A
•
Masterfile
Length
.
15
.
Edit Error Messages:
-------
NUMBER OF TESTS
i nit ion :
NUMBER OF TESTS is the cumulative
specification tests performed for
installation. Normally, such a test is
installation of the monitor.
total of performance
a monitor since its
performed atthe initial
Retrieval
Abbreviation
PSRC
Card.
.
Type
N/A
Card
Columns
N/A
Data Element
Length
2
Data
Type
NUMERIC
Valid Values:
Justified
N/A
Masterfile
Record Type
34
.
quired
:
Masterfile
New Entry
N/A
Position
118—119
.
,
Nationally
.
Masterfile
Controlled
N/A
Length
2
.
Edit Error Messages:
.
:
= Fatal Error
* = Warning
Error
Coding Considerations :
This data is generated by the
user but can be retrieved
incremented, each time a ‘PASS”
update program; it cannot be input by the
from the C 4 masterfile. This field is
or “FAIL is coded in the PST STATUS field.
Data Dictionary
A. 1—14
-------
NUMBER OF FAIL .
Definition :
NUMBER OF FAIL is the total number of’performance
tests. reported with a result of “FAIL” since
installation.
specificatic—
the monitor
Retrieval
Abbreviation
PSRF
Card
Type
N/A
Card
Columns
N/A
Data Element
Length
2
Data
Type
NUMERIC
Valid Values:
.
Justified
N/A
Masterfile
Record Type
34
.
.
Required
Masterfile
on New Entry
N/A
.
.
Position
122-123
•,
Nation ally
Masterfile
.
.
Controlled
N/A
.
Length
2
.
Edit Error Messages:
.
= Fatal Error
* = Warning
Error
Coding Considerations :
Tjhis data is generated by the
user but can be retrieved
i’ncremented each time a “FAIL”
update program; it cannot
from the C 1 masterfile.
is coded in the PST STATUS
be input by the
This field is
field.
Data Dictionary
A.1—15
-------
NU? ER OF PASS
Definition:
Data
Type
NUMEER OF PASS is the total number of performance
tests reported with a. result of ‘PASS” since
installation.
specification
the monitors
Coding Considerations :
This data is generated by the
user but can be retrieved
incremented each time a “PASS”.
update program; it cannot
from the C 24 masterfi]e.
is coded in the PST STATUS
be input by the
This field is
field.
Data Dictionary
A.1— 16
Retrieval
Abbreviation
PSRP
Valid Values:
Card
Type
N/A
Card .
.
Columns
N/A
•
Data Element
Length .
2
NUMERIC
.
.
Masterfj le
Justified
N/A
Record Type
34
.
,
.
.
.
Required
Masterfile
•
on New Entry
N/A
Position
120-121
:ionally
Masterfile
.
ntrolled
N/A
Length
2
.
Edit Error Messages:
.
.
.
= Fatal Error
* = Warning Error
•
-------
Definition :
PERMISSIBLE ISSION LIMIT
PERMISSIBLE EMISSION LIMIT is the units and values specifiedb
the regulation noted by the CEM Regulation Number
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Data Dictionary
A.].— 17
EMI S
52
Valid Values:
All alphanumeric characters
29—48
20
ALPHANUMERIC
Masterfile
Justified NO
Record Type
34
.
Required
Masterfi]e
.
on New Entry N/A
Position
256—275
Nationally
Masterfile
.
Controlled N/A
Length
15
.
Edit Error Messages:
Fatal Error
* Warning
Error
Coding Considerations:
Typical values might include:
20% OPAC/6 MIN PERD
0.8 LBS/MBTU S02
Code the EMIS the same for every
monitor subject
to the same
regulation.
-------
PST DATE
Definition : PST DATE is the date the latest Performance Specification Test
was performed and is coded in year/month format .
Retrieval
Abbreviation
Data
Type
Coding Considerations :
PSTD——refers to the entire four character field
PSTM——refers to the month field
PSTY——refers to the year field
Retrieval selection of PSTD data should be in year/month format.
select October 1981, enter 8110.
Data Dictionary
A.1—18
To code or
PSTD, PSTM, PSTY
Valid Values:
Z 2 = MONTH
Card
Type
52
•
Card
Columns
53—56
Data Element
Length
4
YY = YEAR
NUMERIC
.
Justified NO
Masterfile
Record Type
•
34
.
Required
.
Masterfile
on New Entry NO
Position
•
106-109
Nationally
.
Masterfile
.
ntro lled NO
Length
4
,
Edit Error Messages:
...
* INVALID DATE VALUE
= Fatal Error
* = Warning
Err r
.
-------
PST STATUS
Definition : PST STATUS is the result of the latestperformancespecificati
test.
Retrieval Valid Values:
Abbreviation PSTS
_______________________________________ “PASS”
Ca rd
Type 52 “FAIL”
Card
Columns 57—60 blank
Data Element
Length 4
Data
Type ALPHANUMERIC
Justified NO
Masterfile
Record Type 34
.
Required
on New Entry NO
Masterfile
Position 110-113
.
Nationally
Controlled NO
Masterfile
Length 4
Edit Error Messages:
.
*PST STATUS MUST BE PASS OR FAIL
.
= Fatal Error
* = Warning Error
Coding Considerations:
When either “PASS” or “FAIL” is entered,
(PSRP or PSRF) and the cumulative test
UPDATE program.
the appropriate pass or fail
counter (PSRC) are incremented
counter
by the
Data Dictionary
A.1—19
-------
A.2
ACTION LEVEL
DATA ELEMENTS
-------
ACTION TYPE
Definition:
ACTION TYPE is a two-position alphanumeric actior description
identifier.
Retrieval
Abbreviation
ATPE
Card
Type
70
Card
.
Columns
57—58
Data Element
Length
2
Data
Type
ALPHANUMERIC
Valid Values:
Must be on Action Table controlled
by National CDS DBC.
Action Type 00 indicates an action
type which is user defined.
Justified LEFT
Masterfile
Record Type
46
.
Required
on New Entry YES
Masterfile
Position
.
27-28
Nationally
“ontrolled YES
-
Masterfile
Length
2
Ldit Error Messages:
***flJ JALID ACTION TYPE
***ACTION TYPE REQUIRED ON
*ACT DESC IGNORED - ATPE
NEW
NOT
ENTRY
00
= Fatal Error
* = Warning Error
Coding Considerations :
Please call the National CDS DBC to add, change, or delete entries on the
Action Table for your region.
Certain action types are required to input to CDS. Please consult the
current FY air enforcement program plans arid the most recent SSCD guidance
material for the most current requirement.
To obtain the most current version of a region’s action types, please
contact TRC.
Since many action types are confidential, users should use a password on
the 20 card of the Retrieval Request Form to obtain action level
information on retrievals.
Data Dictionary
A.2-].
-------
DATE ACHIEVED
Definition :
DATE ACHIEVED is the date on which an action is completed in
month/day/year format.
Retrieval
Abbreviation DTAC
Blanks or 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 greater than 60.
Coding Considerations :
If an error is encountered in the date field, the bad month, day, or year
is zeroed out by the Edit Program. An asterisk on a change transaction
for this field will zero out the field on the Masterfile.
Data Dictionary
A.2-2
Valid Values:
Card
Type
.
70
.
Card
Columns
.
59—64
.
Data Element
Length
6
Data
Type NUMERIC
Justified LEFT
Masterfile
Record Type
.
46
Required
Masterfile
.
.
.
on New Entry NO
Position
29-34
,
Nationally
Masterfile
Controlled NO
Length
6
Edit Error Messages:
.
*I J LID DATE ACHVD - OUTPUT
SPACES
= Fatal Error
* = Warning Error
-------
DATE SCHEDULED
cjnjtion:
DATE SCHEDULED is the date which an action is scheduled to be
performed. Use the month/day/year format.
Retrieval
Abbreviation DTSC
Blanks or zeros are not acceptable.
Day must be between 01 and 31,
month must be between 01 and 12,
and year must be greater than 60.
tionally
ntrolled NO
Masterfile
Length
6
Edit Error Messages:
.
.
*DT SCHED SHOULD BE
*I j J ID DATE SCHED
ON NEW -
- OUTPUT
OP ZEROS
SPACES
= Fatal Error
.
* = Warning Error
Coding Considerations: .
If an error is encountered in the date field. the bad month, day, or year
is zeroed out. If this field is left blank on a new transaction and if
the Date Achieved is valid, the Date Achieved is moved into this field by
•the Edit Program.
Data Dictionary
A.2-3
Valid Values:
Card
-______________
Type
70
.
Card
.
Columns
65—70
Data. Element
Length
6
Data
Type
NUMERIC
Required
on New Entry
Masterfile
Justified LEFT Record
Type 46
YES
Masterfile
Position 35—40
-------
ACTION STAFF CODE
Definition :
ACTION STAFF CODE is a three—position code: referring to the
staff member assigned to complete the action.
Retrieval
Abbreviation PERA
Data
Type ALPHANUMERIC
The Staff Code must exist on the
Personnel Table controlled by the
National CDS DBC. The first
position must be alphabetic; the
next two numeric. When requesting
changes to this table, be sure to
give CDS the DBC full title
information as well.
Coding Considerations :
• Please call the National CDS DBC to make additions, changes or deletions
to the Personal Table.
Data Dictionary
A.2—4
Valid Values:
Card
Type
70
Card •
•
Columns
•
71—73
Data Element
Length
.
3
.
Justified LEFT
Masterfile
Record Type
46
.
•
:
Required
on New Entry NO
•
Masterfile
Position
41-43 •
•
•
Nationally
Controlled YES
Masterfile
Length
3
•
.
Edit Error Messages:
*I J\IALID STAFF CODE
= Fatal Error
* = Warning
Error
-------
RESULTS CODE
rjflition :
RESULTS CODE indicates the results of an action, such as action
achieved, action not achieved, or action rescheduled.
Coding Considerations :
May be a blank. If not a blank,
it must be a two—digit numeric,
field. The Results Code must
exist on the Results Code Table
controlled by the National CDS
DBC.
The results code can indicate the success of an action, including whether
or not the action was carried out.
Please cal ]. the National. CDS DEC to add, change, or delete entries on the
Results Code Table for your region. Please contact TRC to obtain most
currentResults Code Table for your region.
Data Dictionary
A.2-5
Retrieval
Abbreviation
STAC
Valid Values:
Card
Type
70
Card
.
Columns
74—75
Data Element
Length
2
Data
Type
NUMERIC
Masterfile
Justified
LEFT
Record Type
46
.
Required
.
.
Masterfile
on New Entry
NO
Position
61-62
.
itionally
Masterfile
)ntrolled
YES
Length
,
2
Edit Error Messages:
*flJ\J ID RESULTS
CODE
= Fatal_Error
* =_Warning_Error
-------
REGIONAL_DATA ELEMENT 8
Definition : REGIONAL DATA ELEMENT 8 is user supplied.
Retrieval Valid Values:
Abbreviation RDES
Card
Type
S
70
Card
.
Columns
76—77
Data Element
Length
2
Data
Type ALPHANUMERIC
•
Justified
LEFT
Masterfile
Record Type
46
Required
.
Masterfile
•
on New Entry
NO
Position
63-64
Nationally
Masterfile
Controlled
NO
Length
2
•
Edit Error Messages:
S
= Fatal Error
* = Warning Error
Coding Considerations :
Data Dictionary
A.2-6
-------
ACTION NUMBER
Definition:
ACTION NUMBER is a four digit numberic sequential action
identifier.
Retrieval
Abbreviation
Data
Type YES NUMERIC
Coding Considerations :
For Card types 10, 51, 52, and 60 : the action number is 0000 .‘
For a 70 Card type :
Actions should be assigned sequentially starting with 0001. When adding a
new action to the data base, code 0099, the system will convert the 0099
to the next highest sequential action number for that emission point. If
several actions and action conm ents are entered at the same time with
action Number 0099, comments will not be associated with the proper
action. Therefore, users must not enter multiple actions and comments
with Action Number 0099 simultaneously since these will produce rejects on
the Update Report.
An action number cannot ‘be added to the data base unless the emission
point and channel number for that action are also being added or already
exist on the data base. Each action number must be associated with an
emission point and channel number. This channel number should be “000”
for entry of “M3” action types which are passed to CDS.
Data Dictionary
Valid Values:
0000 through 0099
Card
Type
‘
10, 51,
70
52, 60,
Card
Columns
18—21
Data Element
Length
4
.
.
Justified
NO
Masterfile
Record Type
20-47
Required
on New Entry
NO
Masterfile
Position
21-24
.
‘
‘ tionally
ntrolled
NO
Masterfile
Length
4
Edit Error Messages:
.
***Action Numbers
must
be
zeros (card type 10—60)
***Actjofl Numbers
must
be
greater than zero (card
type
70)
S
= Fatal Error
* = Warning Error
-------
REPORT QUARTER (QUARTER DATE )
Def nition:
REPORT QUARTER (QUARTER L)ATE) is a four digit numberic date
identifying the year and quarter of the excess emission report.
Retrieval
Abbreviation
Coding Considerations:
For a 71, 72 or 80 Card type :
In the case of the 71, 72 and 80 card .coding, the Report Quarter is •in
columns 18—21 where tha action number is found on the two last digits of
the year are recorded in columns 18—19 and the two digit quarter is
recorded in columns 20—21.
Report Quarter is the Calendar quarter (year/quarter) in which the excess
emission took place on the 71, 72 card, and if any comments apply to the
71, 72 card data, that same quarter number is used on the 8—0 card
comment, in order to match it up.
Data Dictionary
A.2-8
RQTR
Card
Type
71,72,80
Card
Columns
18—21
•
•Data Element
Length
4
Valid Values:
7001 through 9904
YYQQ
1? = Calendar Year
QQ = Calendar Quarter
Data
Type
YES NUMERIC
Masterfile
.
Justified NO
Record Type
20—47
.
.
Required
Masterfile
on New Entry NO
.
Position
•
21-24
Nationally
Masterfile
Controlled NO
Length
4
Edit Error Messages:
***Action Numbers must
be
greater
than zero (card
type
70)
= Fatal Error
.
*. = Warning
Error
-------
flefinition:
MONITOR UNAVAILABILITY :
MONITOR UNAVAILABILITY is the percent that the monitor is
unavailable as a percent of the total plant operating time.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
= Fatal Error
Coding Considerations :
Percent of source operating time that the monitor was unavailable.
Total Monitor Downtime Minutes
_________________________________ x 100
Total Source Operating Minutes
= Warning Error
Data Dictionary
A.2—9
PMON
N/A
Valid Values:
000.000 — 100.000
N/A
6
NUMERIC
Justified
N/A
Masterfile
Record Type
46
Required
on New Entry
N/A
Masterfile
Position
379—384
‘itionally
ntrol1ed
N/A
Masterfile
Length
6
Edit Error Messages:
-------
MONITORED OPERATION WITHOUT EXCEEDANCES
Definition :
MONITORED OPERATION WITHOUT EXCEEDANCES is the percent of time
that the source was operating, monitored, and with no incidents
of excess emissions.
Retrieval
Abbreviation
Data
Type
POPT
Valid Values:
Coding Considerations :
Percent of monitored time that the source
excess emission.
‘was able
to operate with no
100% - (% of Reported Operating Time. With
Unavailability)
Excèedances
& Monitor
Data Dictionary
A.2—lO
Card
Type
N/A
Card
Columns
N/A
Data Element
Length
4
NUMERIC
Justified
N/A
Masterfile
Record Type
46
Required
on New Entry
N/A
‘
Masterfile
Position
.
391-396
Nationally
Masterfile
Controlled
N/A
Length
4
Edit Error Messages:
= Fatal Error
* = Warning
Error
-
-------
REPORTED OPERATING TIME WITH EXCEEDANCES
Definition : REPORTED OPERATING TIME WITH EXCEEDANCES is the total amount of
time that the source was operating and had exceedances.
Retrieval Valid Values:
Abbreviation PEXC
Card
Type N/A
Card
Columns N/A
Data Element
Length 4
Data
Type NUMERIC
.
Justified .N/A
Masterfile
Record Type
46
.
Required
Masterfile
S
on New Entry N/A
Position
281-284
Nationally
.
Masterfile
:
ntrolled N/A
Length
4
Edit Error Messages:
= Fatal Error
a = Warning Error
Coding Considerations:
S
Percent of source operating
time
that the monitor was
operational
and
the
source had excess emissions.
Total Excess Emission Minutes
______________________________ x 100
Total Source Operating Minutes
Data Dictionary
A.2—11
-------
REASONS FOR EXCESS EMISSIONS
Definition : REASONS FOR EXCESS EMISSIONS is designed to provide a single
quick look data element showing all 7 excess emission reasons,
the equipment malfunction (unacceptable), the process problems
unacceptable and the number of incidents of excess emissions.
Retrieval Valid Values:
Abbreviation ROCT
Card
Type
71, 72
Card
Card
71=34—78
Columns
Card
72=28—38
Data Element
.
Length
57
Data
Type NUMERIC
Justified
N/A
Masterfile
Record Type
46
.
Required
on New Entry
N/A
•
Masterfile
Position
193—249
:
Nationally
Controlled
N/A
Masterfile
Length
57
.
Edit Error Messages:
= Fatal Error
* = Warning Error
Coding Considerations :
STAR — startup/shutdown
SOOT — cleaning/soot blowing
E’CUN - unknown
EQPT — equipment malfunction (total)
EQPU — equipment malfunction (unacceptable)
PROC — process problems (total)
PPRO — process problems (unacceptable)
FUEL — fuel problems
EEOT — other known causes of excessemissions
EEIN — number of incidents of excess emissions
Data Dictionary
A.2—12
-------
Definition:
CLEANING/SOOT BLOWING
CLEANINGISOOT BLOWING is a count of the .:number of excess
emission periods/minutes due. to cleaning/soot blowing.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
71
40—45
6
Masterfile
Justified RIGHT Record Type 46
Required Masterfile
on New Entry NO Position 199-204
tionally Masterfile
ntrolled NO Length 6
Edit Error Messages: —
*P 5ON FIELD MUST BE NUMERIC
= Fatal Error * = Warning Error
Coding Considerations :
Data Dictionary
A.2—13
SOOT
Valid Values:
Must be numeric
NUMERIC
-------
CLEANING/SOOT BLOWING’ (Percent )
Definition:
CLEANING/SOOT BLOWING (Percent) is the percent
quarterly excess emission’ periods/minutes due to
blowIng.
of the total
cleaning/soo
Retrieval
Abbreviation
PS00
Card
Type
N/A
‘
Card
Columns
6
Data Element
Length
NUMERIC
Data
Type
N/A
Valid Values:
000.000 — 100.000
Justified
N/A
Masterfile
Record Type
‘
46
Required .
on New Entry
N/A
.
,
Masterfile
Position
2.95-300
‘
Nationally
Controlled
N/A
Masterfile
Length
•
6
‘
Edit Error Messages:
•
,
= Fatal Error
* = Warning
Error
Coding Considerations:
CLEANING/SOOT BLOWING (SOOT ) x 100
PSOO = TOTAL NUMBER OF D CESS
4ISSION PERIODS (D CP)
Data Dictionary
A.2—14
-------
EQUIPMENT FAILURE TOTAL
Definition: CONTROL EQUIPMENT FAILURE (TOTAL) is the sum of excess
periods/minutes both•• acceptable and unacceptable
unit/control equipment failure or malfunction.
Retrieval
Abbreviation
EQPT
Card
Type
71
Card
Columns
52—57
Data Element
Length
6
Data
Type
NUMERIC
Valid Values:
Must be numeric
Justified RIGHT
Masterfile
Record Type
.
46
Required
on New Entry NO
•
‘
Masterfile
Position
.
211-216
tionally
ntro11ed NO
Masterfile
Length
,
6
Edit Error Messages:
.
*P SQN FIELD MUST BE
NUMERIC
Fatal Error
* = Warning
Error
Coding Considerations :
Includes——control equipment malfunction
——unit equipment malfunction
Data Dictionary
A.2—15
emission
due.. t0
-------
CONTROL EQUIPMENT FAILURE TOTAL (Percent )
Definition :
CONTROL EQUIPMENT
the total excess
unacceptable, due
malfunction.
FAILURE (TOTAL) percent is the percent. of
emission periods/minutes, acceptable ani
to unit/control equipment failure o
Retrieval
Abbreviation
PEQP
Card
Type
N/A
Card
Columns
N/A
Data Element
:
Length.
6
Data
Type
NUMERIC
Valid Values:
000.000 — 100.000
Justified
N/A
Masterfile
Record Type
46
Required
on New Entry
N/A
.
Masterfile
Position
307-312
Nationally
Control led
N/A
Masterfile
Length
6
Edit Error Messages:
= Fatal Error
* = Warning Error
Coding Considerations :
Data Dictionary
A.2—16
-------
Definition :
CONTROL EQUIPMENT
excess emission
malfunctions that
• I!9
MALFUNCTION (UNACCEPTABLE) is the sum of
periods/minutes due to control equipment
were deemed unacceptable.
Retrieval
Abbreviation
EQPU
Card
Type
71
.
Card
Columns
58—63
Data Element
Length
6
Data
Type
NUMERIC
Valid Values:
Must be numeric
Justified RIGHT
Masterfile
Record Type
46
Required
on New Entry NO
Masterfile
Position
217-222
•
itionally
ntrolled NO
Masterfile
Length
6
.
Edit Error Messages: •
•
*p IASQN FIELD MUST BE
NUMERIC
= Fatal Error
.
* = Warning Error
Coding Considerations :
Used only if the control Equipment malfunctions are a large portion of the
total excess emissions, and a breakdown to acceptable malfunctions and
unacceptable malfunction s is deemed necessary.
This field is not required and is included as an option for those who
desire to enter this information.
Data Dictionary
A.2—l7
-------
CONTROL EQUIPMENT MALFUNCTION UNACCEPTABLE (Percent)•
Definition :
CONTROL EQUIPMENT
percentage of
periods/minutes
The use of the
optional:.
• :MALFUNCTION (UNACCEPTABLE) PERCENT is the
the total quarterly excess emissioi
that are equipment malfunction (unacceptable).
equipment malfunction (unacceptable) field is
Retrieval
Abbreviation
PEQU
Card
Type
.
N/A
Card
.
Columns
N/A
Data Element
Length
6
Data
Type
NUMERIC
Valid Values:
000. 000—100 . 000
Masterfile
.
Justified
N/A
Record Type
46
.
Required
-
Masterfile
on New Entry
N/A
Position
313-318
Nationally
.
Masterfile
Controlled
N/A
•
Length
•
6
Edit Error Messages:
= Fatal Error
* = Warning
Error
Coding Considerations :
Data Dictionary
A.2—18
-------
PROCESS PROBLEMS ‘TOTAL ’
Definition:
Data
Type
PROCESS PROBLEMS ‘TOTAL is the sum of excess’ emission
periods/minutes both ‘acceptable and unacceptable due to process
problems.
Coding Considerations :
Data Dictionary
A.2—19
Retrieval
Abbreviation
PROC
Valid Values:
Must, be numeric
Card ‘ ‘
,
‘
.
Type
‘
71
Card :
Columns
‘ ‘
,
64—69
‘
Data Element
:
Length
‘
‘
6 ‘
‘
,
NUMERIC
Justified RIGHT
‘
Masterfile
Record Type
‘
46 ,
,
0
Required
on New Entry NO
‘
Masterfile
Position
.
235-240
‘
ionally
ontrolled 0 NO
Masterfile
Length
6
‘
Edit Error Messages:
*? SQN FIELD MUST
BE
NUMERIC
= Fatal Error
* = Warning Error
‘
-------
PROCESS PROBLEMS TOTAL (Percent )
Definition :
• PROCESS’, PROBLEMS
quarterly excess
problems.
TOTAL (Percent) is the percent of the total
emission periods/minutes due . to procesE
Retrieval
Abbreviation
PPRO
Card
.
Type
N/A
Card
Columns
N/A
Data Element.
Length
6
Data
Type
NUMERIC
Valid Values:
000.000—loo.000
.
Masterfile
.
.
.
.
Justified
N/A
Record Type
46
.
Required . .
.
.
.
Masterfile
.
on.New Entry
N/A
Position
319—324
Nationally
•
Masterfile
.
Controlled
N/A
Length
6
Edit Error Messages:
.
•
= Fatal Error
•
* = Warning Error
Coding Considerations :
Data Dictionary
A. 2—20
-------
Definition:
Pna cc€ptahle)
PROCESS PROBLEMS (Unacceptable) is the sum of excess emission
periods/minutes due to process problems that were deemed
unacceptable.
Retrieval
Abbreviation
PRUN
Valid Values:
Card
Type
.
71
Card
.
Columns
70—75
Data Element
Length
6
Data
Type
NUMERIC
Justified RIGHT
Masterfile
Record Type
46
.
Required
on New Entry NO
Masterfile
Position
•
241-246
ional1y
. trolled NO
Masterfile
Length
6
Edit Error Messages:
.
*P 5ON FIELD MUST
BE
NUMERIC
= Fatal Error
* = Warning
Error
Coding Considerations :
Used only if the process problems are a large portion of the total excess
emissions, and a breakdown to acceptable process problems and unacceptable
process problems is deemed necessary.
Data Dictionary
A. 2—21
-------
PROCESS PROBLEMS UNACCEPTABLE (Percent)
Definition : PROCESS PROBLEMS UNACCEPTABLE (Percent) is the percent of the
total quarterly excess emission periods/minutes due to process
problems that were deemed unacceptable. The use of the process
problems (unacceptable) ‘field. is optimal.
Retrieval Valid Values:
Abbreviation PPRU
000.000—100.000
Card
Type
N/A
•
Card
Columns
N/A
Data Element
Length
6
Data
Type - NUMERIC
Justified
N/A
Masterfile
Record Type
46
Required
on New Entry
N/A
Masterfile
- Position
,
325-330
Nationally
Controlled
N/A
Masterfile
Length
6
Edit Error, Messages:
.
.
= Fatal Error
* = Warning
Error
Coding Considerations :
Data Dictionary
A.2—22
-------
STARTUP / SHUT DOWN
Definition :
STARTUP/SHUTDOWN is
periods/minutes due
source.
a count of the number of excess emissIon
to the starting up or shutting down of the
Retrieval
Abbreviation
STAR
Card
Type
71
.
Card
Columns
34—39
Data Element
Length
6
‘
Data
Type
NUMERIC
Valid Values:
M ist be numeric
Justified RIGHT
Masterfile
Record Type
46
.
Required
Masterfile
•
on New Entry NO
Position
193-198
ionally
Masterfile
ntrolled NO
.
Length
6
.
Edit Error Messages:
= Fatal Error
* = Warning
Error
Coding Considerations :
Data Dictionary
A. 2—23
-------
STARTUP/SHUTDOWN (Percent )
Definition :
STARTUP/SHUTDOWN’(Percent) is the percent of the total quarterly
exceSs emission periods/minutes due’ to startup or shutdàwn of
the source.
Retrieval
Abbreviat ion
Data
Type
***.= Fatal Error * = Warning Error
Coding Considerations :
Data Dictionary
A.2—24
PSTA
Valid Values:
000 . 000—100. 000
Card
Type
N/A
Card
‘
Columns
N/A
Data Element
‘
Length
6
NUMERIC
‘
‘ Masterfile
‘
Justified
N/A
Record Type
46
‘
‘
Required
.
Masterfile
‘
ón New Entry
N/A
Position
289-294
‘
Nationally
‘
Masterfile
‘
Controlled
N/A
Length
6
.
Edit Error
Messages:
-------
‘ init ion :
UNKNOWN EXCESS EMISSIONS .
UNKNOWN EXCESS EMISSIONS is the percent of the total number of
periods/minutes the monitor recorded excess emissions due to
unknown reasons.
Retrieval
Abbreviation
Card
Type
.
71
Card
Columns
46—51
Data Element
Length
6
Data
Type
NUMERIC
Valid Values:
must be numeric
Justified RIGHT
Masterfile
Record Type
.
46
:
Required
on New Entry No
Masterfile
Position
.
205-210
.
,
tionally
Controlled No
Masterfile
Length
6
.
Edit Error Messages:
.
* = Reason field must
be
numeric
= Fatal Error
* = Warning
Error
Coding Considerations :
Data Dictionary
A. 2—25
-------
Definition :
UN Q4OWN DCCESS EMISSIONS (Percent) .
U?.Th0 OWN ‘CCESS EMISSIONS (Percent) is - the percent of the tota’
-. quarterly excess emission periods/minutes due to unknown reasons.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
= Fatal Error
Coding Considerations :
* = Warning Error
Data Dictionary
A.2—26
P cU
N/A
Valid Values:
000.000—100.000
N/A
6
NU RIC
Justified
N/A
Masterfile
Record Type
•
46
Required
on New Entry
N/A
Masterfile
Position
.
301-306
Nationally.
Controlled
N/A
Masterfile
Length
.
6
Edit Error Messages:
,
.
.
-------
Definition:
FUEL PROBLEMS
FUEL PROBLEMS is the number àf periods/minutes the monitor
recorded excess emissions due to fuel problems.
Retrieval
Abbreviation
Card
Type
Card
Columns
• Data Element
Length
Data
Type
: 27—32
6
Masterfile
Justified RIGHT Record Type 46
Required Masterfile
on New Entry NO, Position 223-228
“ ionally Masterfile
itrolled NO Length 6
Edit Error Messages:
*P ASQN FIELD MUST BE NU? RIC
= Fatal Error * = Warning Error
Coding Considerations :
Data Dictionary
A.2—27
FUEL
72
Valid Values:
Must be numeric
NUMERIC
-------
Definition :
FUEL PROBLE2IS
PUEL PROBLE24S (Percent) is the percent ôf the total
excess emissions periods/minutes due to fuel problems.
(Percent)
quarterly.
Retrieval
Abbreviation
PFUE
Card
Type
N/A
•
Card
Columns
.
N/A
Data Element
.
Length
.
6
Data
Type
NUMERIC
Valid Values:
000.000—100.000
Justified
N/A
,
Masterfile
Record Type
46
•
Required
on’ New Entry
N/A
Masterfile
Position
331-336
.
Nationally
Controlled
N/A
Masterfile
Length
.
Edit Error Messages:
= Fatal Error
* = Warning Error
Coding Considerations :
Data Dictionary
A.2—28
-------
Definition:
OTHER KNOWN EXCESS EMISSIONS
OTHER KNOWN EXCESS EMISSIONS is the number of periods/mInutes
the monitor recorded excess emissions due to other known reasons.
Data
Type
NUMERIC
Must be numeric
Justified RIGHT
Masterfile
Record Type
.
46
Required
on New Entry NO
Masterfile
Position
229-234
Nationally
ontrolled NO
Masterfile
Length
6
.
Edit Error Messages:
*PP SON FIELD MUST
BE
NUMERIC
= Fatal Error
* = Warning
Error
Coding Considerations :
Data Dictionary
A.2—29
Retrieval
Abbreviation
EEOT
Valid Va1ue :
Card
Type
72
Card
Columns
33—38
Data Element
Length
6
-------
OTHER }OJOWN DCCESS EMISSIONS (Percent )
Definition :
OTMEW. IGIOWN CCESS EMISSIONS (Percent) is the percent of the
total quarterly excess emissions periods/minutes due to other
known reasons.
Retrieval
Abbreviation
Data
Type
Coding Considerations :
Data Dictionary
A.2—30
PEEO
Valid Values:
000.000—loo.000
Card.
.Type
N/A
‘
Card
Columns
N/A
Data Element
Length
6
NUMERIC
Justified N/A
Masterfile
Record Type
46
.
.
‘
Required
on New Entry ‘N/A
Masterfile
Position
337-342
‘
.
Nationally .
Controlled N/A
Masterfile
Length
6 ‘
Edit Error Messages:
‘
‘
.
= Fatal Error
* = Warning
Error
,
-------
NUMBER OF INCIDENTS OF EXCESS EMISSIONS
Definition:
NUMBER OF INCIDENTS OF EXCESS EMISSIONS is the total
incidents of excess emissions. recoidecl by the monitor.
number of
Retrieval
Abbreviation
Data
Type
Coding Considerations :
Data Dictionary
A.2—3].
EEl N
Valid Values:
Must be numeric
Card
Type
.
71
.
Card
Columns
76—78
Data Element
Length
3
Nt.Th RIC
Justified RIGHT
Masterfile
Record Type
46
Required
.
Masterfile
Position
.
on New Entry NO
.
247-249
Nationally
.
Masterfile
ntrolled NO
Length
3
Edit Error Messages:
* J1JMBER OF INCIDENTS
NOT
NUMERIC
.
= Fatal Error
* =_Warning_Error
-------
REASONS FOR MONITOR DOWN TIME
Definition : REASONS FOR MONITOR DOWN TIME is designed to provide a singlE
quick look data element showing all reasons •the monitor 1!
down. These are the 5 most common reasons, and the number ot
incidents of monitor downtime.
Retrieval Valid Values:
Abbreviation BPMD
Card
Type.
72
Card
Columns
39—71
Data Element
Length
33
Data
Type NUMERIC
.
Justified
N/A
Masterfile
Record Type
.
46
Required
on New Entry
N/A
•
.
Masterfile
Position
250-282
:
•
Nationally
Controlled
N/A
Masterfile
Length
33
Edit Error Messages:
.
= Fatal Error
* = Warning Error
Coding Considerations :
The 5 reasons are:
MOEQ - monitor equipment malfunction
NMEQ - non-monitor equipment malfunction
CAL l — calibration
MC(JN - unknown
MOOT — other Imown monitor downtime
MOIN - number of incidents of monitor downtime
Data Dictionary
A.2—32
-------
Definition:
CALIBRATION
CALIBRATION is the number of monitor downtime periods/minutes
due to calibration of the monitor.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
51—56
. 6
Masterfile
Justified RIGHT Record Type 46
Required Masterfile
on New Entry NO Position 262-267
T tionally Masterfile
ntrolled NO Length 6
Edit Error Messages:
*p EASQN FIELD MUST BE NUMERIC
= Fatal Error . * = Warning Error . . . ..
Coding Considerations :
Data Dictionary
A. 2—33
CALl
72
Valid Values:
Must be numeric
NUMERIC
-------
CALIBRATION (Percent )
Definition :
CALIBRATION (Percent) is the percentage of the total qiarterly
monitor down time periods/minutes due to monitor calibration.
Retrieval
Abbreviation
PCAL
Card
Type
N/A
Card
Columns
•
N/A
Data Element
Length
6
Data
Type
NUMERIC
Valid Values:
000 . 000—100. 000
Justified N/A
Masterfile
Record Type
.
46
.
.
Required
on New Entry
N/A
.
Masterfile
Position
361-366
.
Nationally
Controlled
N/A
Masterfile
Length
6
Edit Error Messages:
.
= Fatal Error
;
* = Warning
Error
‘ CodingConsiderations :
Data Dictionary
A.2—34
-------
fl finition:
MONITOR EQUIPMENT MALFUNCTION
MONITOR EQUIPMENT MALFUNCTION is’ the number of monitor downtime
periods/minutes due to malfunctionof the monitor equipment.
Retrieval
Abbreviation
Card
Type
Card
Col uinns
Data Element
Length
Data
Type
72
39—44
6
Masterfi].e
Justified RIGHT Record Type 46
Required Masterfile
on New Entry NO Position 250-255
-- itionally Masterfile
ntrolled NO Length 6
Edit Error Messages:
*P ASON FIELD MUST BE NUMERIC
= Fatal Error * = Warning Error
Coding Considerations :
Data Dictionary
A.2—35
MOEQ
Valid Values:
Must be numeric
NUMERIC
-------
Definition :
MONITOR EQUIPMENT MALFUNCTION (Percent) .
MONITOR EQUIPMENT MALFUNCTION (Percent) is the percentage of. thø
total quarterly monitor down time periods/minutes resulting: froi
monitor equipment failure.
Retrieval
Abbreviation
PMOE
Card
Type
.
.
N/A
Card
Columns
.
N/A
.
.
Data Element
L gth
6
Data
Type
NUMERIC
Valid Values:
000.000—loo.000
•Justified
N/A
Masterfile
Record Type
46
:
:
Required
on New try
N/A
.
Masterfile
Position
349-354
:
•
..
.
•
Nationally
Controlled
N/A
Masterf lie
Length
6
Edit Error Messages:
.
= Fatal Error
* = Warning
Error
Coding Considerations :
Data Dictionary
A.2—36
-------
Retrieval
Abbreviation
Card
Type
Card
Col uxuns
Data Element
Length
Data
Type -
. 45—50
6
Justified
Required
on New Entry
Nationally
ntrol led
Edit Error Messages:
*REASON FIELD MUST BE NUMERIC
= Fatal Error
Coding Considerations :
Non-monitor equipment malfunctions include:
— data processor malfunction
- running out of paper
- running out of ink
Data Dictionary
A. 2—37
Definition:
NON-MONITOF EQUI PMF.NT MALFUNCTI ON
NON-MONITOR EQUIPMENT MALFUNCTION is the number of monitor down
time periods/minutes due to non—monitor equipment malfunction
• •NMEQ
72
• Valid Values:
Must be numeric
NUMERIC
•
.
Masterfile
•
•
RIGHT
Record Type
46
NO
•
Masterfile
Position
•
256—261
Masterfile
•
NO
Length
•
•
* = Warning
Error
-------
NON-MONITOR EQUIPMENT MALFUNCTION (Percent )
Definition:
NON-MONITOR EQUIP? IT MALFUNCTION (Percent) is the percentage of
the total quarterly monitor down time periods/minutes due to
non-monitor equipment failure.
Retrieval
Abbreviation
Card
Type
N/A
Card
Columns
.
N/A
Data Element
Length
6
Data
Type NUMERIC
Coding Considerations :
Data Dictionary
A.2—38
Valid Values:
000 . 000—100 . 000
Justified
N/AS
Masterfile
Record Type
.
46
.
Required
on New try
N/A
Masterfile
Position
355-360
.
Nationally
Controlled
N/A
Masterfile
Length
.
6
S
Edit Error Messages:
= Fatal Error
* = Warning Error
-------
Definition:
OTHER KNOWN MONITOR DOWN TIME
OTHER KNOWN MONITOR DOWNTIME is the number of monitor downtime
periods/minutes due to other known reasons..
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
63—68
6
Masterfile
Justified RIGHT Record Type 46
Required Masterfile
on New Entry NO Position 274-279
‘tionally Masterfile
r trolled NO Length 6
Edit Error Messages:
*P SON FIELD MUST BE NUMERIC -
= Fatal Error * = Warning Error
Coding Considera€ions :
Data Dictionary
A.2—39
MOOT
72
Valid Values:
Must be numeric
NUMERIC
-------
OTHER IQ4OWN MONITOR DOWN TIME (Percen i .
Definition :
OTHER1GIOWN MONITOR DOWN TIME (Percent) is the percentage. of th
total quarterly monitor down time periods/minutes for othe
known reasons.
Data
Type . NUMERIC
Coding Considerations :
Data Dictionary
A.2—40
Retrieval
Abbreviation PMOO
Valid Values:
‘OOO.OOO—].OO.OOO
Card
Type
N/A
Card
Columns
N/A
Data Element
Length
6
Justified
N/A
Masterfile
Record Type
46
.
.
Required
.
.
Masterfile .
.
on New Entry
N/A
Position
.
373-378
Nationally
Masterfile
•
.
Controlled
N/A
Length
6
.
.
•
Edit Error Messages:
.
.
.
.
= Fatal Error
.
* = Warning Error
.
-------
IJ1JVNOWfI MF N 1i1 11)t’flJ 11 M I
D fjnjtjon: UNKNOWN MONITOR DOWN TIME is the number of monitor down time
periods/minutes due to unknown reasons.
Retrieval
..
Abbreviation
MOUN
Card
Type
72
Card
Columns
57—62
Data Element
Length
6
Data
Type
NIJ RIC
Masterfile
Justified RIGHT Record Type 46
Required Masterfile
on New Entry NO Position 268-273
“ationally Masterfile
Dntrolled NO Length 6
Edit Error Messages:
* ASON FIELD MUST BE NUMERIC
= Fatal Error - * = Warning Error
Coding Considerations :
Data Dictionary
A.2—41
Valid Values:
Must be numeric
-------
UN1 ’JOWN MONITOR DOWN TIME (Percent)
Definition : UN)O 1OWN MONITOR DOWN TIME (Percent) is the percentage of the
total quarterly monitor down time periods/minutes for reason!
unknown.
Retrieval Valid Values:
Abbreviation PMOU
ooo.000—loo.000
Card
Type
.
N/A
Card
Columns
N/A
Data Element
Length
6
Data
Type NUMERIC
•
Masterfile
.
Justified :
N/A
Record Type
46
Required
Masterfile
on New Entry
N/a
Position
367—372
Nationally
Masterfile
.
Controlled
N/A
Length
6
Edit Error Messages:
.
= Fatal Error
* = Warning Error
Coding Considerations :
Data Dictionary
A.2—42
-------
NUMBER OF INCIDENTS OF MONITOR DOWN TIME
Definition : NUMBER OF INCIDENTS OF’MONITOR ‘DOWN TIME is the ‘total number àf
incidents of monitor down time.
Retrieval ‘ Valid Values:
Abbreviation MOIN
_________________________________________ Must be numeric
Card
Type’ ‘ 72
Card
ColUmns 69—71
Data Element
Length 3
Data’
Type NUMERIC
Masterfile
Justified ‘ RIGHT Record Type 46
Required ‘, ‘ Masterfile
on New Entry , , NO Position 280-282
M 4 - .ona1ly Masterfile
:ro lled NO Length 3
Edit Error Messages:
*MTJMBER OF INCIDENTS NOT NUMERIC
= Fatal Error ‘= Warning Error
Coding Considerations :
Data Dictionary
A.2—43
-------
D €init ion:
Data
Type
TIME PERIOD
TIME PERIOD i a 1—digit. cod indica’in -j whethr: the excess
emissions from the ELk’s re reduced and coded for a. specified
period of tiii e, or in minutes.
Coding Considerations :
M = Minutes.
A = 6 minutes
B = 15 minutes
C = 30 minutes
D = 1 hour (60 minutes)
E = 2 hours (120 minutes)
F = 3 hours (180 minutes)
G = 24 hours (1440 minutes)
Data Dictionary
A.2—44
Retrieval
Abbreviation
TIME
Valid Values:
M,A,B,C,D,E,F,G
Card
Type
. 71
Card
.
Columns
27
.
Data Element
Length
1
ALPHABET IC
.
Justified . NO
.
Masterfile
Record Type
46
.
.
Required V
on New Entry YES
Masterfile
Position
.
.
186
.
Nationally
Controlled NO
Masterfile
Length
1
Edit Error Messages:
.
.
..
*TIME PERIOD MUST BE P OR
M
V
= Fatal Error
* = Warning
Error
-------
Definition :
TOTAL CCESS DIISSION is
quarter that the source
pollutant.
TOTAL EXCESS EMISS:ON
the number of periods/minutes during a
had excess emissions of a specific
Coding Considerations :
System—generated from
reasons for excess emission (ROCT)
“Period’ is a duration of time specified by
emissions for the specified pollutants (PATE
Data Dictionary
A.2—45
the regulation defining excess
1983).
Retrieval
Abbreviation
ECCP
Valid Values:
Card
N/A
Type
Card
Columns
N/A
Data Element
Length
6
Data
Type
NUMERIC
Justified
N/A
Masterfile
Record Type
.
4€
.
.
Required
on New Entry
N/A
.
.
Masterfilé
Position
.
•
2E3-288
“ ionally
trolled
N/A
Masterfile
Length
6
.
Edit Error Messages:
= Fatal Error
* = Warning
Error
-------
ToTAL. MoNITOR DOWN TIME
Definition :
TOTAL MONITOR DOWN TIME
monitor has malfunctioned
quarter.
is the number of periods/minutes a
and is out of service during a given
Retrieval
Abbreviation MONP
Coding Considerations :
System—generated from reason for
monitor down time (BPMD).
See comment for total excess emission.
Data Dictionary
A.2—46
Valid Values:
Card
Type
N/A
Card
Columns
.
N/A
Data Element
.
.
Length
6
Data
Type
NUMERIC
.
Justified
N/A
.
Masterfile
Record Type
.
46
Required
.
.
Masterfile
on New Entry
N/A
Position
343-346
Nationally
Masterfile
Controlled
N/A
Length
6
Edit Error Messages:
.
= Fatal Error
* = Warning Error
-------
Definition:
TOTAL SOURCE OPERATING TIME
TOTAL SOURCE OPERATING TIME is the total number of minutes/
periods that a source is operating.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
OPER
71
Valid Values:
Must be numeric.
Not required, but important.
. 28—33
6
NUMERIC
.
Masterfile
:
RIGHT
Record Type
46
N/A
Masterfile
Position
187—192
NO
Masterfile
Length
6
Justified
Required
on New Entry
M ,tional ly
nt rolled
Edit Error Messages
*OPERATING PERIODS MUST BE NUMERIC.
= Fatal Error
Coding Considerations :
Enter the number of operating periods in periods or minutes.
The total number of operating periods is a function of the definition of a
period as defined in 40 CFR 60.7. This unit varies depending on the
pollutant. (PATE 1983)
* = Warninq Error
Data Dictionary
A.2—47
-------
A.3
OTHER
DATA ELEMENTS
-------
i nit ion :
REGION CODE is a two-position numeric region identifier.
REGION CODE
Retrieval
Abbreviation REGN
Coding Considerations :
01 through 10
See attachment showing the region
locations and the states
associated with each region.
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
database. If it must be changed, the entire source must be deleted and
reentered with the correct region code.
Data Dictionary
A.3-l
Valid Values:
Card
Type
10,51,52,60.70,71
72,80
Card
Columns
•
1-2
Data Element
Length
2
• Data
Type
NUMERIC
Masterfile
.
.
Justified LEFT
Record Type
20,
21,
30, 34,
35,
46,
47
:
.
Required
Masterfile
New Entry YES •
Position
1-2
Nationally
Masterfile
Controlled • YES
Length
2
Edit Error Messages:
,
***I?J ID REGION CODE
.
***flJ J ID REGION ON CONTROL
CARD
,
•
= Fatal Error
* = Warning
Error
.
-------
REGION CODE
States have been assigned to regions as follows:
01 — Boston Connecticut. Maine, Massachusetts,
New Hampshire, Rhode Island, Vermont
02 - New York New Jersey, New York, Puerto Rico,
Virgin Islands
03 — Philadelphia Delaware, District of Columbia, Maryland,
Pennsylvania, Virginia, West Virginia
04 — Atlanta Alabama, Florida, Georgia, Kentucky,
Mississippi, North Carolina,
South Carolina, Tennessee
05 — Chicago Illinois, Indiana, Michigan, Minnesota,
Ohio, Wisconsin
06 — Dallas Arkansas, Louisiana, New Mexico,
Oklahoma, Texas
07 — Kansas City Iowa, Kansas, Missouri, Nebraska
08 — Denver Colorado, Montana, North Dakota,
South Dakota, Utah
09 — San Francisco Arizona, California, Hawaii, Nevada,
Guam, American Samoa, Trust Territories
10 — Seattle Alaska, Idaho, Oregon, Washington
DATA DICTIONARY
Data Dictionary
A.3-2
-------
ninit ion:
STATE CODE
STATE CODE is a two-position numeric field. The state codes are
derived from the Storage and Retrieval of Aerometric Data Manual
(SAROAD) publishedby OAQPS.
Card
Type
10,
70,
51,
71,
52,
72,
60,
80
Card
.
Columns
:
3 4
Data Element
Length
•
2
•
Masterfi] .e
.
..
.
Justified LEFT
Record Type
20,
21,
30,
34,
.
.
35,
46,
47
.
.
guired
.
Masterfile
on New Entry YES
Position
3—4
Nationally
Masterfile
•
Controlled YES
Length
2
Edit Error Messages:
.
***I J J ID STATE CODE
•
***STATE NOT 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 database. If
it must be changed, the entire source must be deleted and reentered with
the correct state code.
Data Dictionary
A.3-3
Retrieval
Abbreviation STTE
Valid Values:
01—56
See attached list showing the
states associated with each state
code.
Data
Type
NUMERIC
-------
STATE CODE
The CDS System use the following two-digit SAROAD state codes:
01 Alabama
02 Alaska
03 Arizona
04 Arkansas
05 California
06 Colorado
07 Connecticut
08 Delaware
09 District of Columbia
10 Florida
21 Maryland
22 Massachusetts
23 Michigan
24 Minnesota
25 Mississippi
26 Missouri
27 Montana
28 Nebraska
29 Nevada
30 New Hampshire
31 New Jersey
32 New Mexico
33 New York
34 North Carolina
35 North Dakota
36 Ohio
37 Oklahoma
38 Oregon
39 Pennsylvania
40 Puerto Rico
51 Wisconsin
52 Wyoming
53 American Samoa
54 Guam
55 Virgin Islands
56 Trust Territories
DATA DICTIONARY
Data Dictionary
A.3-4
11
12
13
Georgia
Hawaii
Idaho
‘
41
42
43
Rhode Island
‘South Carolina
South Dakota
14
15
Illinois
Indiana
44
45
Tennessee.
Texas
16
Iowa
46
Utah
17
Kansas
‘
47
Vermont
18
19
20
Kentucky
Louisiana ,
Maine
48
49
50
Virginia ,
Washington
West Virginia
-------
rt cjnjtjon:
COUNTY CODE
COUNTY CODE is a four-digit numeric county ‘identifier.
county codes are derived fromthe SAROAD Manual.
The
10,
51,
52,
60,
70,
71,
72,
80
Card
.
Columns
5-8
Data Element
Length
4
.
.
Masterfile
Justified LEFT
Record Type
20.
21.
30.
34,
.
.
35,
46,
47
Required
.
Masterfile
.
New Entry YES
.
Position
5—8
•
Nationally
Masterfile
Controlled YES
Length .
4
:
Edit Error Messages:
***INCOP P CT COUNTY
CODE
FOR
STATE
.
= Fatal Error
* = Warning
Error
.
Coding Considerations :
Please contact the National DBC to update the county code file. County code
must be present on all transactions; it cannot be changed or blanked out on
the database.
Data Dictionary
A.3-5
Retrieval
Abbreviation
Card
Type
CNTY
Valid Values:’
All county codes must be present
on the ‘CDS County Code/AQCR table.
Data
Type . NUMERIC
-------
SOURCE NUMBER
Definition :
Retrieval
Abbreviation
Data
Type
SOURCE NU ER is,a five-digit numeric facility identifier;
Coding Considerations :
The first digit of the CDS Source Number must correspond to the Air Program
Code. For sources subject to more than one air program, the last four digits
of the CDS Source Number must be entered the same. This can be done easily by
using the NEDS source numbering convention: use the NEDS Cross—Reference
Number (NEDS Plant ID). If the NEDS Cross—Reference Number is not available,
the next hghest sequential number within the county can be assigned.
Data Dictionary
A.3-6
SRCE
Valid Values:
All numeric values
Card
Type
10,
70,
51,
71,
52,
72,
60,
80
Card
Columns
9—13
•
Data Element
Length
5
NUMERIC
:
Justified
LEFT
.
Masterfile
Record Type
.
20,
35,
.
21,
46,
30,
47
.
34,
•
Required
on New Entry
YES
Masterfile
Position
9-13
..
.
Nationally
Controlled
NO
Masterfile
Length
.
5
Edit Error Messages:
.
***SOU E NUMBER
MUST
BE NUMERIC
Fatal Error
* = Warning
Error
-------
Definition:
CARD CODE
CARD CODE is a one—digit numeric field which identifies the type
of fixed-format informationfound on the CDS input punch card.
Retrieval
Abbreviation N/A
Valid Values:
10 = Source Record
51 = Monitor Record
52 = Monitor Record
60 = Monitor Comments
70 = Action Record
71 = Action Record (Excess
Emissions Report)
72 = Action Record (Excess
Emissions Report)
80 = Action Comment
Coding Considerations :
Card Colums 14—21 must contain zeros for card 10.
Card Columns 18—21 must contain zeros for cards 51,52 and 60.
Data Dictionary
A.3-7
Card
Type
10, 51, 52, 60,
Card
Columns
22—23
Data Element
Length
2
Data
Type. NUMERIC
Justified
N/A
Masterfile
Record Type
N/A
.
Required
New Entry
YES
Masterfile
Position
N/A
.
N tional1y
Controlled
YES
Masterfile
Length
N/A
Edit Error Messages:
.
.
INVALID CARD
CODE
= Fatal Error
* = Warning
Error.
-------
LINE NUMBER
Definition :
LINE NUMBER is used by the computer to distinguish one comment
line from another.
Retrieval
Abbreviation
N/A
Card
Type :
60,
80
Card
Columns
27
Data Element
Length
.
1
Data
.
Type
NUMBRIC
Valid Values:
0 through 9
Justified N/A
•
Masterfile
Record Type
.
35, 47
.
Required
•
Masterfile
.
on New Entry YES
Position
27
.
Nationally
Masterfile
Controlled YES
Length
1
Edit Error Messages:
S
•
***LINE NUMBER MUST
BE
NUMERIC
.
= Fatal Error
* = Warning Error
Coding Considerations :
Assign line numbers sequentially. Before assigning a line number, refer to
the Source Data Report to be sure the number you code is not already on the
database for that particular emission point. Although Line Number is carried
on the Masterfile, it is not, a retrievable data element.
Data Dictionary
A.3-8
-------
CO? 4ENTS
inition : CO .2 ITS can be used to place on the C 4 Masterfile data which
does not fit into any fixed card format.
Retrieval
Abbreviation
Coding Considerations :
All comments can be retrieved on a Source Data Report and only action
comments can be retrieved on an Action Summary Report.
Use: Card 60 for a point comment.
Card 80 for an action coiTment.
Do not use comment records to carry enforcement action information or
compliance status information; other card types are available for these
purposes.
Data Dictionary
A.3-9
N/A
Valid Values:
All alphanumeric values.
Card
Type
60. 80
Card
.
.
Columns
28
Data Element
Length
52
Data
Type
ALPH NU RIC
Justified
LEFT
Masterfile
Record Type
•
35. 47
Required
on New Entry
:
NO
.
Masterfile
Position
•.
•
28-79
.
.
Ltionally
ntrolled
NO
Masterfile
Length
,
52
Edit Error Messages:
.
= Fatal Error
* = Warning
Error
-------
Definition :
UPDATE CODE
UPDATE CODE tells the update program to add, change, or’ delete a
transaction. This data element is not carried on the masterfile
but serves to tell the update program what’ to do with other data
on the input transaction.
Retrieval
Abbreviation
Data
Type
Coding Considerations :
The Cr24 EDIT only validates the existence of the update code; it is the
report which points out incorrect or illogical update codes.
Each card type has a corresponding record type on the C 4 data base. If a
card type 51. 60, 70, 71 or 80 has not already created a masterfile record
type, it must be added as New. Each point,, action, or comment record must be
associated with a corresponding source record. Each point comment must be
associated with a point. Each action must be associated with a point. Each
action comment must be associated with an action. A new source is added to
C D I with a card type 10, with an update code of “A”.
Key data elements (region, state, county, source, point ‘and action numbers
cannot be changed. Other data elements can be changed by using the updat’
code “C”. Only those record types which have been successfully added as new
Data Dictionary
A 3—10
N/A
Card
Type
10,
51, 52, 60,
Card
‘
Columns
80
Data Element
.
Length
1
Valid Values:
N = New
C = Change
D = Delete
A = Add (Card 10 only)
ALPHA
.
Justified
Masterfile
Record Type
N/A
,
‘
.
Required
on New Entry YES
Masterfile
Position
N/S ‘
‘
‘
Nationally
Controlled ‘ YES
Masterfile
Length
N/A
‘
‘
Edit Error Messages:
‘
‘
***I JALID UPDATE CODE
***DO NOT DELETE POINT
***NO DATA IN COL 27-79
000
FOR
‘
DELETES
= Fatal Error
= Warning
Error
‘
Update
-------
prior to tnis update cycle can be changed. Only those data elements which are
ac ua]ly 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
a:values will be zeroed out).
The update code ‘D’ deletes one or more records on the Cfl4 data base. A:..card
type°:lO delete will delete all masterfjle records for a given source.
A card type 51 will delete a point together with all associated comments,
actions, and action comments. Point .0000 cannot be deleted unless a card type
10 is used for the delete function.
A card type 70 or 71 will delete an action together with all associated action
comments.
A card type 60 or 80 delete must have a valid line number. One delete card is
needed to delete each comment line number.
If a ‘D’ is entered in column 80, no data may be punched in columns 27 through
79. This protects the data base against a mispunched delete update code.
Data Dictionary
A.3—11
-------
APPENDIX B
? MORNJDUM: GUIDANCE CONCERNING EPA’S USE OF CONTINUOUS
D4ISSION MONITORING DATA; KATHLEEN M. BENNET,
AUGUST 12, 1982
-------
• UNITED STATES EN.V R NvENT P E:: A z y
____ WASHINGTON C C 2O46
ocr,cr oc
A.13 I 2 AIR, NOISE A RADIATID,,.
MEI ORA?:DUM
SUB3ECT: Guidance Concerning EPA’s Use of Continuous
Emission Monitoring Data
FROM: Kathleen M. Bennett J_tR) ”
Assistant Administr or for Air, Noise and Radiation
TO: Directors, Air and Waste Management Divisions,
Regions II—IV, VI—VIII, and X
Directors, Air Management Divisions,
Regions I, V and IX
This memorandum addresses EPA’S use of Continuous Emission
Monitoring (CEM) data in enforcement of I2SPS and SIP emission and
operating and maintenance (OEM) provisions and in other general EPA
activities. It provides guidance as to when, as a legal matter,
continuous emission monitoring constitutes the test method associated
with an emission limitation. It is not intended to preclude the
exercise of reasoned discretion by an enforcing agency based on a
review of the representativeness of the data and the circumstances
giving rise to the excess emissions.
Use of CEMs that are Specified as the Source Compliance Test Method
In each instance where CEMs have been promulgated or approved by
the Agency as an official method to determine source compliance with
the applicable emission limitations, the Agency can rely upon CEM data
when making compliance determinations. CEMs have been specifically
prescribed as the method to establish emission violations for one or
more pollutants in the following instances:
• NSPS electric utility steam generating units,
regulated by 40 CFR Part 60 Subpart Da;
• NSPS primary nonferrous smelters, regulated by
40 CFR Part 60 Subparts P. Q and R;
• NSPS stationary gas turbines, regulated by 40
CFR Part 60 Subpart GG;
• various sources regulated by permits, orders, or consent
decrees in which CEM has been specifically designated as
the test method;
(Coi thued)
Memorendum Descnbing Uses of M Data
B-i
-------
—2—
various types of sources which are regulated by S!Ps
(e.g., Nevada SIP, 40 CFR 552.1475(d)) where the State
has specified CEll as the test method.
,Some sources object to EPA’S reliance upon CEll data to enforce SIP
•mision provisions for source categories for which EPA has not
specified the us. of CElls in comparable NSPS regulations. Such an
objection is not legally supportable, since States have th. right to
specify their own methods in their sIps, even if they are different
from thos. imposed by EPA for NSPS sources. Section 1.0 of Appendix P
to 40 CFR Part 51 delineates that SIPS may specify that CEll data be
used ‘directly or indirectly for compliance determinations or any other
purpose deemed appropriate by the State.’ The Agency can rely upon CFM
data for complianc, determinations whsnever such methods are specified
in the EPA-approved SIP.
Use of CElls in SIPs where an Emission Compliance Test Method is Not
Specified
There are some instances when SIPs do not specify a compliance
test method. When that occurs, the applicable regulation, 40 CFR
552.12(c)(1), states that for the purpos. of Federal enforcement:
‘sources subject to plan provisions which do not
specify a test procedure.., will be tested by means
of the appropriat. procedures and methods prescribed
in Part 60 of this chapt.r; unless otherwise specified
in this part.’
G.n.rally, Part 60 does not specify CEll as the compliance test method
and therefore EPA cannot us. CEll data to determine source compliance
with a SIP emission limitation. However, in-accordance with
S52.12(c)(1), CEll data would be the applicable test method for the two
categories of sources for which it is th• NSPS performanc. test method,
nonferrous smelters (as in Subparts P. 0 and R); and stationary gas
turbines (as in Subpart GG).
The Agency .hallrely upon CEll data to determine a source’s
compliance status with a SIP emission limit for nelters (for so 2 )
and for stationary gas turbines (for Since CEll is the only
compliance test method specified in Part 60 for these sourc•
categories, CEll is clearly the ‘appropriat. method underPart 60 for
purposes of S52.12(c)(l).
In addition, ther. is some ambiguity regarding the appropriate
procedures for fossil—fuel—fired steam generators prescribed in Part 60
because Part 60 contains two significantly different types of SO 2 and
NOx performance test methods. Specifically, Subpart D specifies
(C3uZl nued
Memorandum Describing Uses of CEM Data (C ed)
B- 2
-------
—3
Refüence (stack test) Methods 6 and 7 as the performance test t o s
for .SQ and NO emissions, respectively. However, Subpart Da
specifies use of CEM data to determine cor pliance with the SO 2 and
NO emission standards.
The Agency shall rely upon the performance test methods specified
in Subpart D (Reference Methods 6 and 7) to determine a source’s com-
pliance status with SIP $02 and NO emission limits for fossil—
fuel—fired steam generators. For this category of sources, it is more
consistent with the development of the SIPs to use these methods since
they are the traditional compliance test methods for this source
category. (For new sources actually subject to Subpart Da, we would
not expect this issue to arise since new source permits should specify
the applicable test method.)
Use of CEM ’s where State Regulations Contain Discretionary Authority as
to Corpliance Test Methods
A problem in interpreting the SIP continually arises because most
SIPs specify test methods (often adopting EPA methods by reference) but
a’ - allow for discretionary acceptance of an equivalent or an
ai priate alternative by the State. Relying on such language, many
States have accepted CEM data as an adequate demonstration of com-
pliance and have used such data to determine the existence of a
violation.
Since EPA’s enforcement authority is guided by State regulations
specifically approved in the SIP, questions have been raised as to
whether EPA will independently apply State discretionary authority and
interpret what is reasonable as an equivalent or alternative
compliance test method, or, if not, whether EPA may follow the State’s
lead, if the State chooses to allow CEM as the test method.
The answer is that EPA will not independently exercise such
authority. Only when the State has exercised such authority to adopt
CEM as a test method and when the exercise of that authority has been
reflected in the SIP, will EPA use CEM as the test method.
Use of CEM Data for Determining Potential Operations and Maintenance
( O&M) Violations
NSPS regulations (40 CFR 60.11(d)) specify that at all times,
including periods of startup, shutdown, and malfunction, owners and
operators shall, to the extent practicable, maintain and operate any
affected facility including associated air pollution control equipment
in a manner consistent with good air pollution control practice for
- Ttizing emissions. Determination of whether acceptable operating
ai naintenance procedures are being used will be based on information
(C o tj ued)
MernoraDdun Describing Uses of CEM Data (Co ti ue )
B- 3
-------
— 4 —.
available to the Administrator which may include, b t is not limited
to, monitoring results, opacity observations, review of operating and
maintenance procedures, and inspection of the source. Many SIP’S have
sim 1 ar provisions requiring proper operation and maintenance. Use of
CEM data, while not necessarily conclusive, is a valid indicator of
compliance with requirements such as 560.11(d) and can be used as such.
Use of CEMs as a General Compliance Monitoring Tool
CEMs can provide the Agency with useful data for circumstances
other than those delineated above. For instance, CEM data can be used
to: (1) screena source’s compliance status (with both emission
limitations and O&M requirements); (2) select which sources should be
inspected or compliance (stack) tested; (3) document the severity
(e.g., duration, magnitude and frequency) of a source’S excess
emissions; and (4) document that acomp]iance test was performed during
.non—representati ve operating conditions. S
Memorandum Describing Uses of CEM Data (Concluded)
8-4
-------
APPENDIX, C
FINAL TEC} JICAL GUIDANCE ON
THE REVIEW AND USE OF EXCESS
4ISSION REPORTS
-------
s I•’,s
UNITED T TES E VIRU \1E\T.AL P} (lTECTJ(j\ (;F\(
• HL\GT . D L. 204 u
f. , .
4 ‘t
ocr 5 j
OFflCEOF
MEMORANDUM
SUBJECT: Final Technical Guidance on the Review and Use of
Excess Emission Reports
FROM: Director
Stationary Source Compliance Division
Office of Air Quality Planning and Standards
TO: Directors, Air and Waste Management Division
• Regions II, IV, VI-Vill, and X
Directors, Air Management Divi8ion
• Regions I, III, V, and IX
This memorandum presents final technicalguidance on the
eview and use of Excess Emission Reports (EERs) being submitted
y NSPS Subpart D sources and others where the monitoring data
are not used directly to determine compliance with the emission
limits. This guidance is in direct support of the Agency’s
Continuous Compliance Strategy and SPMS items A/ER-8 thru 10
for FY 1985. The guidance may be helpful to State/local agencies
as well and may be forwarded at the discretion of each Region.
On August 3, 1984, a draft of this guidance was distributed
to the Regional Offices arid interested Headquarters Offices.
Comments were received from six Regional Offices, three Headquarters
offices, and the State of Wisconsin. In general, these comments
were very supportive of the draft, included a number of detailed
suggestions for improvement, and encouraged the expeditious
issuance of final guidance. We recognize that the FY 1985
continuous emission monitoring system (CEMS) program is a major
initiative for many of the Regions and is based to a large
extent on the availability of this guidance. Therefore, we
have judged it appropriate to issue the guidance now and to
supplement the guidance as appropriate in an EER “Users Handbook”
dvring F! 1985.
A discussion of the major areas of comment and the responses
received to the questions posed in the August 3rd memorandum is
presented in the following sections.
C-’
-------
—2—
I. MAJOR COMMENTS
A. Form of Guidance/Regional Office Responsibilities
The sub)ect document is intentionally being issued as
Ntechnical guidancew rather than as program guidancew,
providing a great deal of detailed information, forms, and
example decision criteria adaptable to a wide range of
circumstances. We recognize that since the CEMS program is a
relatively new program for most Regional Offices, program—related
issues will also arise. Such issues are outside the scope of
this guidance and will be addressed separately.
B. Importance of EER Review and Use
Based upon the experience of some Regional Offices,
particularly Region V’s 1 SSCD revised the text of the draft
to emphasize the three primary EER activities of: (1) inventory
development; (2) assessment of source compliance with the
CEMS installation and operation requirements; and (3) review
and use of EERs. This doesn’t mean that other elements of
the program to acquire valid, representative data are unimportant.
It’s just that such activities (e.g., performance specification
testing) are solely the responsibility of the source, not the
Agency. By the Agency primarily concentrating its CEllS program
resources on EER5 review and follow—up, most sources will find
that it is in their own best interest to achieve all of the
CEMS requirements. and to verify the quality of their data
before submitting it to the Agency.
II. RESPONSES TO SSCD’s LER QUESTIONS
A. Dual Reporting of EERs to State and Federal Agencies
In general, commenters supported the need for a ]imited period
of dual reporting. They stressed that EPA should initially obtain
and (at least) spot—check duplicate copies of EERS from sources in
States which have received NSPS delegation in order to conduct
effective oversight audits of the State’s enforcementof the CEMS
regulations. Furthermore, they strongly supported the concept of
reducing the quantity of dual reporting and the level of oversight
audits once the State had demonstrated its ability to implement
the program. Subsequent oversight could be achieved by receiving
and reviewing a small, random fraction of a State’s EER5 or by
receiving summary reports from the State. (Regional Offices and
their States are free to establish any mutually—acceptable arrange-
ment consistent with assuring, at a minimum, accomplishment of
the FY 1985 SPMS requirements.)
C— 2
-------
-3-
B. Source Submission of Summaries of Their Excess Emissions
Commenters strongly supported the concept of reqt iring the
sources to include summaries of their excess emissions in their
quarterly EERs. They also supported the idea of specifying a
standard format, content, and reason codes for the summaries
as well as the traditional EER data in order to minimize the
burden upon agencies and sources. The coinmenters also strongly
supported our recommendations that: (1) all CEMS-affected sources
should initially submit both the summaries and the traditional
EERs; and (2) once a source demonstrated its commitment and
capability to implement a high quality CEMS program, their
reporting burden might be reduced to submission of only the
summary data portion of the EER report.
The comments included a wide range of recommendations on
how the Agency should proceed to obtain source submission of
the summary data from the sources. These included: (1) use of
S114 letters on a case-by-case basis or in a national promulgation;
(2) a regulatory revision; and (3) simply thorough implementation
of this guidance.
SSCD intends to work with ESED and other parts of the Agency
to develop a consensus on which changes should be made to the
reporting requirements and how to proceed most effectively.
Careful consideration of the requirements of the Paperwork
- duction Act is an essential element of this review.
C. Applicability of Guidance to Subpart Da Sources
Most respondents to our question on this subject indicated
that, based on their limited experience, they thought that the
proposed guidance would assist them in reviewing CEMS compliance
reports from Subpart Da and other sources where the monitor
provides compliance data. A few commenters volunteered their
assistance and recommended that the Agency obtain some additonal
experience before it attempts to develop a guideline -on this subject.
One Regional Office with considerable CEMS program experience
stated that, “We do not think the discretionary, probabilistic,
comparative philosophy of this screening strategy is appropriate
for sources subject to clear requirements for self-documenting
their continuous compliance status”. We agree with this statement
and with the need to obtain additional experience before guidance
is developed. Accordingly, the draft guidance was not changed
with respect to its inapplicability to Subpart Da or other 8ources
where the CEMS is the compliance method.
In summary, the comments received on the draft guidance urged
that final guidance be issued as soon as possible, incorporating
relatively few major changes to the draft. SSCD intends to
C- 3
-------
- 4 -
continue to support the program by issuing supplementary inforni
tion and program guidance. Furthermore, SSCD plans to work with
other elements of the Agency to try to address the remaining
issues such as revision of the EER reporting requirements and
possible applications of CEMS as the compliance method on addi-
tional source 'categories.
Edward E. Reich
Attachment
cc: J. Fanner, Director, ESED
D. Tyler, Director, CPDD
E. Salo, OGC
M. Alushin, OECM
Air Branch Chiefs, Regions I-X
.Air Compliance Branch Chiefs, Regions II, III, V, VII, IX
Directors, Environmental Services Division, Regions I-X
C-4
------- |