vvEPA
            United States
            Environmental Protection
            Agency
           Office of Air Quality
           Planning and Standards
           Research Triangle Park NC 27711
EPA-340/1 -84-011
June 1984
            Air
Compliance Data
System Quality
Assurance Manual

-------
                                    EPA-340/1 -84-011
Compliance Data System Quality
           Assurance  Manual
                        by

              TRC Environmental Consultants, Inc.
                  800 Connecticut Blvd.
                  East Hartford, CT 06108

                  Contract 68-01-6315

              EPA Project Officer: Franklin G. Smith
              Project Manager: Gregory M. Fisher
                     Prepared for

           U.S. ENVIRONMENTAL PROTECTION AGENCY
             Stationary Source Compliance Division
            Office of Air Quality Planning and Standards
                 Washington, D.C. 20460

                     June 1984

-------
                                      DISCLAIMER
This report was furnished to the Environmental Protection Agency by TRC Environmental
Consultants, Inc. in partial fulfillment of Contract 68-01-6315.  The contents of this1
report are reproduced here in as received from'the contractor.  The opinions, findings,'
and conclusions expressed are not necessarily those of the Environmental Protection
Agency.
                                          11

-------
                                                       EFFECTIVE:  June 1, 1984
                               TABLE OF CONTENTS
SECTION
  1.0
      1.1
      1.2
  2.0
      2.1
      2.2
      2.3
  3.0
      3.1
          3.1.1
          3.1.2
          3.1.3
          3.1.4
            ,1.5
            ,1.6
          3.1.7
          3.1.8
          3.1.9
3.
3.
  4.0
      4.1
          4.1.1
          4.1.2
          4.1.3
            1.4
            ,1.5
            ,1.6
            .1.7
          4.1.8
          4.1.9
4.
4.
4.
4.
      4.2
      4.3
      4.4
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5

4.3.1
4.3.2
4.3.3
4.3.4

4'. 4.1
4.4.2
4.4.3
4.4.4
        INTRODUCTION.  .
          Purpose .  .  .
          Organization.
        SYSTEM OVERVIEW 	
          Background History. .  .  .
          System Functions	
          Data Processing Functions
INPUT CARD EXPLANATION.
  Data Fields ."....
    All Card Types. .   .
    Card Type 1 .  . .   .
    Card Type 2 .  . .   .
    Card Type 3 .  . .   .
    Card Type 4 .  . .   .
    Card Type 5 .  . .   .
    Card Type 6 .  . .   .
    Card Type 7 .  . .   .
    Card Type 8 .  . .   .
SCHEDULE OF DATA INPUT  	
  Quality Assurance Outline 	
    Status of Data to be Input	
    Status of Current Data on File	
    Code Data ..... 	
    Random Check of Coding Data 	
    Input to Edit	t	
    Validate Edit Results .	  .  .  .
    Enter into Update Cycle 	
    Validate Update Cycle Results 	
    Key Considerations	
  Methods of Entering Data	
    Data Submission Using 80-Column Keypunched Cards.
    Data Submission Using Special WYLBUR Techniques  ,
    Data Submission Using Minicomputer Packages  .  .  .
    EMS-to-CDS Converter	
    Interface Files from State CDS	
  Edit Processing 	
    Edit Program Usage	
    Edit Error Messages 	  ,
    Sample CDS Edit Report	
    Edit Job Control Language (JCL) 	
  Reading and Correcting Update. Cycles	,
    Update Processing  	  ,
    Update Program Description	
    Update Scheduling  	  ,
    Update Report 	
PAGE

  1
  1
  2

  3
  3
  3
  4

  8
  8
 11
 13
 15
 17
 21
 24
 28
 29
 32

 34
 34
 34
 34
 34
 35
 35
 35
 35
 36
 36
 37
 37
 39
 42
 48
 51
 51
 51
 53
 56
 58
 58
 58
 64
 66
 67
                                       111

-------
                                                       EFFECTIVE:  June 1, 1984



                         TABLE OF CONTENTS (continued)

SECTION                                                                    PAGE

            4.4.5     Update Report Messages	     73
            4.4.6     Update Status Log	     73
            4.4.7     Update Report Job Control Language	     74
            4.4.8     Critical Data Elements Report 	     74
       4.5          Keeping an Entry Log	     76

  5.0             ENTERING DATA - REQUIREMENTS	     79
       5.1          Adding New Sources	     79
            5.1.1     Multiple Air Programs	     79
            5.1.2     Identifying the Critical Sources for CDS	     80
       5.2          Specific Air Programs and Source or Industry Types      82
            5.2.1     SIP Sources	     32
            5.2.2     Data to be Tracked for All Sources	     84
            5.2.3     Data to be Tracked for Selected Sources	     87
       5.3          Maintaining Data	     89
            5.3.1     Changing Data on the CDS Masterfile	     89
            5.3.2     Deleting Data from the CDS Masterfile	     94
       5.4          CDS Coding Conventions	     98
            5.4.1     Emission Point "000"	     98
            5.4.2     Action Number  "99"	     98
            5.4.3     Action Type "00" - Optional Action Description.  .     98
            5.4.4     Multiple Cross Reference	     99
            5.4.5     NEDS Source Cross Reference  	     99
            5.4.6     Source Number/Air Program Code	     99

  6.0             DATA SOURCES	     100
       6.1          SIC Manual	     100
       6.2          Other Computer Systems	     100
            6.2.1     NEDS	     100
            6.2.2     SAROAD	     100
            6.2.3     EIS	     101
       6.3          Inspection Reports	     101
       6.4          Letters of Notification	     101
       6.5          Compatible State Systems	     101

  7.0  '           QUALITY ASSURANCE  REVIEW	     102
       7.1          Check of Exisiting  Data  for Validity	     102
            7.1.1     Card  1 Data	     102
            7.1.2     Card  2 Data	     102
            7.1.3     Card  3 Data	     103
            7.1.4     Card  5 Data	     104
            7.1.5     Card  7 Data	     105
            7.1.6     Other Data	     105
       7.2          QA  Reports  from  CDS	     105

  8.0             TECHNICAL STANDARDS	     Ill
       8.1           Programming  Standards  	     Ill
            8.1.1     General  COBOL  Guidelines	     Ill
            8.1.2      Identification Division Guidelines	     Ill
                                       IV

-------
                                                       EFFECTIVE:  June 1, 1984



                         TABLE OF CONTENTS (continued)

SECTION                                                                    PAGE

            8.1.3     Environment Division Guidelines 	    112
            8.1.4     Data Division Guidelines	    112
            8.1.5     Procedure Division Guidelines 	    113
       8.2          Testing Standards 	    115
            8.2.1     Test Plan (Overview)	    116
            8.2.2     Types of Failures	    116

  9.0             CURRENT HEADQUARTERS GUIDANCE  	    119

  10.0            USER COMMUNICATIONS	    135
       10.1         EPA Policy and Enforcement Matters	    135
       10.2         Enhancements or Modifications to CDS	    135
       10.3         Technical DP	    135
       10.4         User Training	    136
                                                                                            r
                                       V

-------
                                                       EFFECTIVE:  June 1, 1984



                                LIST OF FIGURES

FIGURE                                                                     PAGE


  2-1       CDS System Functions as used by Headquarters, Region, and
              State Regulatory Agencies 	      5

  2-2       CDS EDP Functions	      7

  3-1       Multiple-Card Layout Form	      9

  3-2       Sample Coding Sheet 	     10

  4-1       CDS Edit Job Control	     38

  4-2       Sample Edit Report	     57

  4-3       Using the Edit's Dummy Option 	     59

  4-4       Input from Tape	     60

  4-5       Saving the Reject File	     61

  4-6       Printing the Reject File	     62

  4-7       Sample WYLBUR Session to Convert Retrieval Output into
             Input to CDS Edit	     63

  4-8       CDS Update Report Job Control	     68

  4-9       Sample Update Report	     70

  4-10      Contents of Update Status Log	     75

  4-11      Sample Critical  Data Element Report  	     77

  4-12      Sample Data Entry Log	     78

  5-1       Enforcement Actions Required	     86

  5-2       Sample of Completed Coding Sheet for a New Facility  ....     92

  5-3       Sample of Completed Coding Sheet for Change  Transaction  .  .     93

  5-4       Sample of Completed Coding Sheet for Delete  Transaction  .  .     97
                                       VI

-------
                                                       EFFECTIVE:  June 1, 1984
                          LIST OF FIGURES (Continued)
FIGURE




  7-1




  7-2




  7-3




  7-4




  7-5
Report Request Form - QA Test 1




Report Request Form - QA Test 2




Report Request Form - QA Test 3




Report Request Form - QA Test 4




Report Request Form - QA Test 5
PAGE




106




107




108




109




110
TABLE




  4-1




  4-2
                                 LIST OF TABLES
Edit Error Messages  .




Update Error Messages
PAGE




 54




 71
                                       VII

-------
                                                       EFFECTIVE:  June 1, 1984
1.0 INTRODUCTION




1.1 Purpose




    The Compliance  Data  System (CDS) Quality Assurance  Manual is  designed to




aid the data  manager in maintaining the most valuable component of the system-




data quality.   The  utility of  any data system is  directly  proportional  to the




quality of  the  data contained in the  system, and CDS is no exception.  During




the ten years of operation, the compliance data has  slowly  but surely improved




to  the point where today CDS  reports are  routinely used for  top management




decision-making,  satisfying  congressional  queries,   and  providing  the  public




with  information  through the  Freedom of Information Act  channels.   With this




user base, it is clear that the maintenance  of  high quality data  in CDS is of




paramount importance.




    This  manual  provides four  services to  the  CDS  data  manager.   First,  it




serves  as  a  quick-reference  user's  guide  for  data  entry.   It  contains




instructions  and  definitions  for  all CDS data  elements.   Second,  it provides




an outline  for  effective data entry  procedures.   This outline helps to ensure




not only  that data  is correct before  it enters CDS, but  that  it  is checked for




accuracy  all  during  the  edit  and  update processes.   Third,  this  manual




explains  several  methods  of  checking existing  data on  CDS and  provides  a




step-by-step  approach for analyzing  and correcting  erroneous data.  Finally,




this manual contains a list of references and sources of information which can




help  the  data manager  in the search for accurate,  reliable  data.  The manual




contains  a complete  review of CDS communications  documents  and user assistance




staff  available  to  supply helpful information on all capabilities of CDS.  In




short,  the  CDS  Quality Assurance Manual  is designed  to be an  easy reference




guide  to  help the CDS data manager maintain data  reliability.

-------
                                                       EFFECTIVE:   June 1,  1984
1.2 Organization




    This manual  is  divided into nine chapters, with  each  chapter describing a




different procedure  or function.   Chapter  1  is  an introduction, stating  the




purpose and organization  of  the manual.  Chapter 2  is  a system summary, which




provides a historical background system functions charts.  Chapter 3 describes




the  data elements  in CDS and  provides  a  detailed look  at each  data type.




Chapter  4  covers the  typical  input  schedule  and  procedures  and  provides  a




model  for  an  effective   data  entry  job  log.   Chapter  5  presents  detailed




instructions  for   coding  data  for   specific   air  programs   and  critical




enforcement tracking  projects.   Chapter 6 lists various sources where data can




be obtained for  use in CDS.  Chapter 7  provides a post-entry quality assurance




procedure and contains pertinent examples of data quality retrievals.  Chapter




8 contains programming and testing  standards and is  designed for the technical




systems user.  Chapter 9  is a compendium of current EPA Headquarters guidance.




    Managers  can especially  benefit  from Chapters  1,  2,  and  9.   Data entry




staff  should  concentrate  on  Chapter  3,  4,  5,  6, and  7.   Data  processing




analysts and  programmers  should find Chapters  3,  4, and  8  most  pertinent to




their  needs.  All  users are  encouraged to read the CDS User's Guide, available




from  the  CDS  Coordinator  in  the Stationary  Source  Compliance  Division  of EPA




in Washington,  DC.

-------
                                                       EFFECTIVE:  June  1,  1984
2.0 SYSTEM OVERVIEW

2.1 Background History

    CDS  was developed  in  1972 by  the Stationary  Source  Compliance Division

(SSCD)   in   conjunction  with  TRC  to  assist  EPA's   regional   offices   in

implementing  their  enforcement  programs.   The  primary  objective  of  EPA's

stationary  enforcement  program is to bring  about compliance  with federal and

state  emission  requirements as stated  by  the State  Implementation Plans (SIP),

.the  Mew  Source  Performance  Standards  (NSPS),  and   the  National   Emissions

Standards  for  Hazardous  Air  Pollutants  (NESHAP).   State agencies and  EPA's

regional  offices  have  coordinated  their efforts  to  develop  an  enforcement

management  system which  will  ensure compliance  with the emission limitations

for all  regulated  pollutants.

    CDS  has been  in  operation for  nearly  nine years.   Experience with the

system has  led  to  modifications and refinements  of  CDS which are  described  in

detail in this  documentation.   During  the  eight years  of regular  production

runs,  CDS has  grown into a system  widely used by  all ten  regions and  nearly

half  the  states.



2.2 System  Functions

    There  is a variety  of  ways  in   which CDS  helps  EPA  Headquarters and

regional  offices,  as  well  as  state  agencies,  in managing  enforcement and

compliance  data.   The  following  paragraphs discuss  the  six  most  important

functions of CDS.
     1.   Inventory of  Ma-'Or  Sources.    .3DS  serves  as  an  inventory of  all
         major  stationary  sources of  air  pollution,  as  defined  by  the
         Alabama  Power decision of 1?8G.

-------
                                                       EFFECTIVE:   June 1,  1984
    2.   Enforcement Program Action Tracking.  CDS contains  information on
        a variety of  air  enforcement  programs,  such as the PSD,  NSPS,  and
        NESHAP programs.   It also allows  historical  event tracking  and
        scheduling  of future enforcement  milestones,  such as  compliance
        schedules.

    3.   Compliance  Analysis.   CDS   provides   statistics   used   in   the
        analysis  of  current compliance and the  evaluation  of  enforcement
        strategies.  CDS  statistics are  used by  upper EPA management  in
        their  Management  Accountability  System to  measure  enforcement
        program progress.

    4.   Resource Allocation.  CDS is used by Headquarters  in their annual
        allocation of funds for regional office  enforcement programs.

    5.   Reporting  Requirements.   CDS  is used  both by  state and regional
        offices  as  a  reporting  tool  to  meet   their   EPA   compliance
        reporting requirements.


Figure  2-1   shows   the  functions  of  CDS  as   they  are  utilized  by  the

Headquarters, Regional, and State Regulatory Agencies.
2.3 Data Processing Functions

    CDS  is  a  standard  three-function  system  featuring  edit,  update,  and

retrieval  procedures.   Each procedure  is a  separate  operation with  separate

controls.

    The  edit  function validates  data  with  regard  to   specific  definitions

included in  the CDS User's Guide  Data  Dictionary.   These definitions indicate

only  whether the  specified  codes are  valid for the  specified data  element.

For  example  State  Code  "XX" is  an invalid State Code and  would  not pass the

edit's  data  checking,  but State Code  "13"  is valid and  would be  accepted by

the  edit.    Edits  may  be run  anytime,  as  may  edit  corrections.   All valid

transactions  passed by  the  edit  are  stored  in  a  "holding file"  for  the

update.  This  "holding file" is referred  to  as the output  MOD file.
                                      -4-

-------
                                                        EFFECTIVE:   June 1,  1984
                                      EPA
                                  Headquarters
  Major
  Source
Inventory
Enforcement
Tracking
Compliance
 Analysis
 Resource
Allocation
Reporting
Requirements
                                  State and
                                  Regional
                                  Offices
                   Figure  2-1.   CDS  System Functions as used by
              Headquarters,  Region,  and  State Regulatory Agencies,
                                       -5-

-------
                                                       EFFECTIVE:   June 1,  1984











    The update is  a  weekly procedure which applies valid  edit  transactions  to




the  master  file.    The  update  checks  for  file  integrity and  will  reject




illogical master  file  applications  of edit  transactions.   For example,  if  a




valid  edit  "change" transaction  record to action  number "07" is  received  by




the  update,  the record will be  rejected  if there  is no  action number  "07"




already  on the  master  file.   The  update usually  is run  once  per  week and




accepts all valid  edit  transactions since the previous  update.  Updates  can  be




scheduled more frequently as the need arises.




    Once  information has  been  stored on  the master  file  by the update,  the




retrieval  procedure  may  be used  to  format  and  print  user reports.   The




retrieval may  be  run  at any time and includes  a  variety  of  user  selection,




sorting,  and  printing  options.   Information on  the  retrieval  is contained in




the  CDS User's Guide,  available  from  the CDS  Data  Base  Coordinator  in the




Stationary Source  Compliance Division in Washington, DC.




    The CDS EDP function chart is  pictured in Figure 2-2.
                                       -6-

-------
                               EFFECTIVE:   June 1,  1984
y
Edit
Transactions


Edit

^--.
     /
    Valid
JTransactionsI
                    Edit
                   Report
Figure 2-2.  CDS EDP Functions.
              -7-

-------
                                                       EFFECTIVE:  June 1, 1984
3.0 INPUT CARD EXPLANATION

    This  section explains  the  transactions  which  can be  input  to  CDS.   A

detailed  description  of each  item,  including  the  valid values and  their

meanings, can be found in the Appendix to this manual.



3.1 Data Fields

    All  input  data to  the  CDS  must  be prepared  in the format  of one of the

eight card  layouts  shown in Figures 3-1 and  3-2.   These are the  only formats

that the system will accept.

    Each  card  must have columns 1-19  (Region,  State, County,  Source, Point,

Action  Number,  Card Code) and column 80  (Update  Code) entered correctly.  The
                                                        •
following sections  define data  elements  that are  unique  for  each card code.

(Items  marked  with an asterisk  (*)  in  the  Remarks column are  required for new

entry.)
                                       -3-

-------
                                                MULTlPLfc-CARD LAYOUT FORM
                                                                                               EFFECTIVE:   June  1, 1984
  • Company
            CDS INPUT LAYOUT
TRC
                                                                            Dot
.June  1984    Job No.
                                                                                                               s(lnB, No.
r-
P)
K
O


PC
C




t uarj



O
|V|
3

i


oo
vO

•"
q
u
g
•r
bl
0
f<

'


•r
1
0
O




a
o
°M>
5

f
*r
g
pr
1 1

r
I
a
i i
c
o
f-
bl
01
<*«

1 1
01
u
nj
u
in

i


U
a




01
ri

01
s
(J
C/J
1 4

State
1 4

01
U
m

CO

4
t?
i
3

1 1 1

P..
a




c
o

u
0
o
o
till

0
5
9 I I 1
.
(|
0
o
o

III
•
M

1 10 II 11 1

01
LO




Source
>

01
u


m
i 10 n ii i)

Source
10 II 11 11
01
u
•I
o
in

10 II 11 11
4-1
o

14 It 1


3
0




M
o

u
•3
o
Pi
4 11 II

U
o
p.
4 11 II

M

O
P.

It II
1
u
u
O

III.

1
CJ



T*,
g
•H
i il M M *» II O 4J 44 41 41

01

1
a

UP(
o
(Q
i Pollut



3
-1



Street Address


41





















41 41 90 91 91 91 94 99 M 91 91 91 ko II 11 11 M 19 1C




State Registration
' Number
40 41 It I] W 44 41 41 ** *• ** *• ** **

lUutant 2 M
L_|


u
1
^

. '**


a j
H-' hi
0- L

w o
3 M U
-4 M d Tj
4 H 0 C
U P4 •-< M

M


u
3
1




d




Pollutant 3 M


P


Federal/State/Local
Regulation Number















H 19 M 11 M n <9 II 41 41 44 49



Optional
Short Action
Description


Filler
n n it n H n K n ii n 33 it 11 1) M it H n a n a 4i it «i « 4;

j
i

•r
*~





















4«4I 41




f
c
L,


Q


4i



1
a



dp
Hit- 4
J Ll r
o.lfc p

O
to u
: tiu
: Loadin
5 Indica








u
H


t>-,
Ii

t^*
Jj

0
T




-
^Ct
*?£{,
iP P
q < > Achiev-
; ed
94 tt M II 91 91 10






Data
Sched-
uled
SI 11 11 M 19 M





m
to
ilMI

U)
3
d 00
W W
5 S
10 11 II 13 K



r-l
r-4
S
1 IS


^
rj
L.


n ii n i







N
i


I*
(i
rt
Iw
UII I


|M
K
.



1 II


i M

! n-
1 M



1


7
p

1!

Filler
n n n ii n




Comments

























































JO n It 11 11 19 K 11 II » JO 11 » » M a 13 11 18 M <0 41 4J 41 M 49 41 41 48 41 90 91 91 91 94 99 K il 96 it U II 11 11 M Ii II II U II 10 II 11 11 H 19 II 11 M IS
Ol
U
n
T1
£

H

01
«J
a




s Update

01
M
0)


M

Update
H


41
u

•o
P
N




























I
VO
I
                                            FIGURE 3-1.   MULTIPLE-CARD LAYOUT FORM.

-------
                                                                                                EFFECTIVE:   June 1, 1984
         si | COUHIY
       CAHU coot—v
        6  / 0
                AqcR
               ICE HUHDER .

                  "FTIIJ
                     cut coot
                        25
                                COMPLIANCE  DATA SYSTEM CODING  SHEET
                                          SOURCE NAI1E
                             ifl.
                                      331341351 36
                                             37
                                                    3S
                                                                             STREET ADDRESS
                                     52]
                                                              II
                Efi]
                                                                                                       ROE 4
                                                                                                                  ROE5
                                                   2522
                          CITV NAME
                                             ZIP
                                                          STATE REGISTRATION
                                                                             NEDS XREF
                                                                                       sic
                                                                                                        ROE6
                                                                                                                    SIAIF
          HIE

          00
               70T71I22123124125126!
          [)|71l22l23l24[:
                            2/128 29 JOI3I132IJ3I34
       35I36I3M30 39
                40141142143
                                                           45
                                    i
                                    IM
                                                                            55J56157
                                                                  52pj
                                                                                          631P
                            Si 55
                                                                                57T6BI6J
                                                rmrm
                                                       ZZEa
                         POIIUIANT
        T5|T7

        p[o
      li
                                 IOADING  I PUT
                                               POILUIANI 2
                                                                   PlUTUTWII 3
                                                      IOA01NG
                        J
                        Isp
                                                                          IOABIHG
                                                                                  FACILIIV CAPACITY
nrmm
                                                                                            RD"     |ROIO|RDII
                                                                                 I6HU9170iri^tnh'ilTS ft 7/1/0
                  •LINE 110.
                                                        SOUHCE COHHENTS
          up

          00
                  Slli
HEEISIEm 36
giMjunius ^7i'
Trrrn
                                                                       57I53T54IRI56I57
                                                                             I56I5
                                                                       £2
                                                                                             65
                                                                                               66 16M6BI69I /UI7
21 7JIZJ,
                                            Zli
                                                                                                Ifil
                                                       lil
     0|0|0|0|0
            I  I  I I I  I  I  I I  I  I  I I  I  I I I  I  I I  I  I I  I  I I I I  I  I I  I  I I  I  I  I I I  I I I  I  I I I  I  I  I I I  I I I  I  I  I I
     tmssiuN,
     oiHTiio I
             sec CODE      ICAPC  cA«i>l PLUI
                                               STATE RtGUUTION
                                                                                    PROCESS DESCRIPTION
            18 JJjZfl Hpp|24|25p
!ffl
                       HD5 36p7[3B|39j4u
                                                     42I4J

                                                                                                            12
    I  I  I  |0|OJ5|  I I  I  I I I  I  I  I I
                              II
       I I  III II  II I  III I
                                                  I  I II  I I I  I  II III I  I  II I  I  I  I  II  I  I
o
 i
I  I
                      I  I I
       I I  III II  III  III I
                                                  I  I II  I I  I  I  II III I  I  I I I  I  I  I  II  I  I
    |o|oH I I  I  I I  I  I  I  I
                                         I  I  I I  I  II  I  I I  I  II  I
                                  I  I  I I  I  I  I  II  I  I I  I  I I I  I  I  I I  I  I  I I
                                                                                              11
                  HIHE NO.
                                                     EMISSION POINI COW1ENTS
                                                                                                                        .«
TmTTmTm
                                                         11
                                                           45146147
                                                                        53154 55
                                                                              56I5/
                                                                                 5BI59160
                                                                                61U2.
                                                                  69IWJI72
     JLlloio
            11111111111 IIII  11111111  111  1111111111  111111111  111  11111111  11  I
     IHISSIIIH ACIION
     mini no
     14 Will,
           riu.
                    OPTIONAL ACT 1011 OESCR1PIION

                       USED HI III ATPE 019
                        [Si
                          Qemnz
    331
                                                                  ACTION                          RISULI

                                                       PENALTY  AMT     TrP€  DATE ACHIEVED  DATE SCHEDULED   STAFF      RDEB
                                                    Em?
                                                                                           6/168169
                                         /an
                                                                                                  TTfTjins
     _L
        7l I  II  I M  I  I I  I  I  I I I
                           MUM
                                                                        111
                                11
           ETOi
LU-U_LIJLLI_LLI1

   DHL NO.
  I I  111


ACTION COMMENTS
                                                                         J.
                                                                       M  I M
                                                     Mill
                                                                                 M
                                      li
                             5|2B|29|jQ|3||j2|j3|34h5h6|3/|38|j9t
-------
                                                       EFFECTIVE:   June  1,  1984
    3.1.1  All Card Types

    To  enter  data  on any  card in CDS,  the following  data  fields must  have

correct and valid values coded:
1 2
REGION
CODE
3 4
STATE
CODE
5
(

6 7
:OUNTY
CODE
8


9 10 11 12 13
SOURCE NUMBER

        14 15 16
        EMISSION
        POINT NO.
                                 17 18   19
                                 ACTION CARD
                                 NUMBER CODE
                                                                            80
                                                                          UPDATE
                                                                           CODE
  Card         Data
Columns     Field Name
   Data
   Type
 1-2    Region
 3-4    State Code
Numeric
Numeric
 5-6    County Code     Numeric
 9-13   Source Number   Numeric
 14 - 16   Emission Point  Numeric
           Number
             Remarks
Refer to Appendix  Page  A-2 which shows
the  region  locations   and the  states
associated with each region.
*Required for new entry.

State  codes are  found  in the  SAROAD
manual.   Refer  to Appendix  Page  A-4
for a  list  of the  state abbreviations
associated with each State code.
*Required for new entry.

County  codes are found in the SAROAD
manual.   All  valid county codes  are
present  on  the  CDS  county  code/AQCR
table;  any  new  county codes  must  be
added to this table.  To obtain a copy
of  this  table,  follow  directions  in
Chapter 10 of the CDS User's Guide.
*Required for new entry.

Source    number    is    a    facility
identifier.   Refer  to Appendix  Page
A-6  to correctly  assign  a new source
number  to a  facility.
*Required for new entry.

For  card  codes  1,  2,   3,  and  4,  the
emission  point  number  is a  constant
"000".   Unique  emission point numbers
are assigned to  each pollutant emitted
from  a  physical  emission point.  Refer
to  Appendix Page  A-7  for  instructions
regarding    emission    point    number
assignments.
*Required for new  entry.
                                      -11-

-------
                                                       EFFECTIVE:  June 1, 1984
  Card         Data          Data
Columns     Field Name       Type       	Remarks	

17 - 18   Action Number   Numeric       Action numbers  must be  "00"  for cards
                                        types  1-6  and  greater  than  zero  for
                                        card   types   7-8,   the  action  data
                                        cards.  Refer to Appendix Page  A-8 for
                                        instructions    on    assigning   action
                                        numbers on card types 7-8.
                                        *Required for new entry.

   19     Card Code       Numeric       Valid  values  are  1, 2,  3,  4, 5, 6,  1,
                                        and 8.
                                        *Required for new entry.

   80     Update Code     Alphabetic    Valid  values  are  "N", "C",  or  "D".
                                        Refer  to  Appendix   Page A-10   for  an
                                        explanation on the use of these  values.
                                        *Required for new entry.
                                       -12-

-------
                                                      EFFECTIVE:  June 1, 1984




    3.1.2  Card Type 1

    This card is used to  enter source related information.  It  is necessary to

enter a card type 1 when entering a new source into CDS.
 ___   ___
 20 21 22   23 24 25 26
   AQCR      CITY CODE
                                                  _l_!_l_l
 27                                                       46
                       SOURCE NAME
 47                                                       66    67    68    69
                       STREET ADDRESS                          RDE   RDE   RDE
                                                                123
 70          74   75          79   80
     RDE4             RDE5       UPDATE
                                  CODE
  Card         Data          Data
Columns     Field Name       Type       	Remarks	

20 - 22   AQCR            Numeric       AQCR is the  air  quality  control  region
                                        for the  source.   Values  are  dependent
                                        on  counties  and  are listed  in  the
                                        county code/AQCR table in CDS.   Follow
                                        instructions in  Chapter  10 of the  CDS
                                        User's Guide to obtain  a  listing  of
                                        this table.
                                        *Required for new entry.

23 - 26   City Code       Numeric       City codes can be  found  in the  SAROAD
                                        manual.   SAROAD  manuals  are  available
                                        on  request  from  the  EPA's  Office  of
                                        Air Quality Planning and  Standards.
                                      -13-

-------
                                                       EFFECTIVE:  June 1, 1984
  Card         Data          Data
Columns     Field Name       Type       	Remarks	

27 - 46   Source Name     Alphanumeric  Source  name  is  used  to  identify  a
                                        facility.   Refer  to Appendix  Page B-3
                                        for  instructions  on naming  a  facility
                                        and  a  list  of  standard  and  useful
                                        abbreviations.
                                        *Required for new entry.

47 - 66   Street Address  Alphanumeric  Street  Address  is  the  actual  location
                                        of the facility.

   67     **RDE1          Alphanumeric  User supplied.

   68     **RDE2          Alphanumeric  User supplied.

   69     **RDE3          Alphanumeric  User supplied.

70 - 74   **RDE4          Alphanumeric  User supplied.

75 - 79   **RDE5          Alphanumeric  User supplied.

   80     Update Code     Alphabetic    Valid values are  "N", "C", or  "D".
**Note on Regional Data Element fields  (RDE_):   These are user-supplied fields
  and  their purposes  may differ  among regions.  Make  sure all  CDS  users  in
  your  region  are using the  fields for the  same purpose;  this  also  includes
  using uniform values for these fields.
                                       -14-

-------
                                                      EFFECTIVE:   June 1,  1984
    3.1.3  Card Type  2

    This card is used to  enter additional source related information.
 20
                  CITY NAME
                              34   35          39
                                      ZIP CODE
I_I_I_I_I_I_L
 S^ATE REGISTRATION
 40
              54   55        58    59       62
                    NEDS  XREF       SIC CODE
 64   65   66   67
FEDF APCD APST
                RDE6
              76   77    79    80
                    STAFF   UPDATE
                             CODE
  Card
Columns
   Data
Field Name
Data
Type
Remarks
20 - 34   City Name.



35 - 39   Zip Code


40 - 54   State
          Registration


55 - 58   NEDS XREF
              Alphanumeric  Abbreviations,   if  used,   should  be
                           consistent.
                           *Required  for new  entry.

              Numeric      If  unknown,  refer to a U.S. Postal Zip
                           Code  Directory.

              Alphanumeric  If  used  consistently,  this  can be used
                           to  sort  CDS  facilities  in  the  same
                           order as the state files are sorted.

              Alphanumeric  This  is a very  important   element  to
                           code  when  entering  a  new  source code
                           in  CDS.   If  the  NEDS  number  is  not
                           known,   please    consult    the   AEROS
                           contact  in your   area  to  get  a  NEDS
                           facility  number.   AEROS  contacts are
                           listed in  Appendix B of the CDS User's
                           Guide.
                           *Note -  If a  CDS  source   number  has
                           been  entered  properly,  the  last four
                           positions  of  the  source  number  should
                           correspond to  the  NEDS Cross-Reference.
                           *Required  for  new  entry.
                                      -15-

-------
                                                       EFFECTIVE:  June 1, 1984
  Card
Columns
     Data
  Field Name
   Data
   Type
Remarks
59-62   SIC Code
                Numeric
   64     Governmental
          Facility Code
          (FEDF)
   65     Air Program
          Code  (APCD)
   66     Air Program
          Status  (APST)
                Numeric
67 - 76   RDE6

77 - 79   Staff
    80
Update Code
              This is a  very important data  element
              to code when entering  a  new source;  it
              refers  to   the   primary   product   or
              service produced at the  facility.   SIC
              codes    may    be     obtained     from
              manufacturing  directories  or the  most
              recent  SIC  directory,  published  by:
              Government   Printing   Office,   Super-
              intendent  of  Documents,   Washington,
              DC  20402.
              *Required for new entry.'

              This   code   is   used   to   identify
              facilities  owned  or  operated  by  a
              government  unit.   Valid   values   are
              blank,  0-5.    Refer  to  Appendix  Page
              C-7 for an explanation of each value.
Alphanumeric  Valid  values are  0-9,  C.   Refer  to
              Appendix  Page  C-8  for an  explanation
              of each value.
              *Required for new entry.

Alphanumeric  Used mainly  for NSR,  PSD,  and NESHAPS
              sources;  this   code  represents   the
              status  of a facility  for a  given air
              program code.  Valid values are 0,  P,
              C, D,  R,  S, T,  X.  Refer  to Appendix
              Page C-9  for an  explanation  of  these
              values.

Alphanumeric  User supplied.

Alphanumeric  This  code is  a 3-position  code  which
              represents   the   person   or   group
              assigned   to  monitor   the  facility.
              These   codes   must   exist   on   the
              personnel   table  maintained   by   the
              national  Data  Base  Coordinator  (DEC).
              Please  call  the  DEC to add, change, or
              delete a code on this table.

Alphabetic    Valid value is "C".
                                       -16-

-------
                                                       EFFECTIVE:   June 1,  1984











    3.1.4  Card Type 3




    This card is used to add or change pollutant compliance data on  CDS master




file.  Multiple  card type 3's  may  be used to enter only  pollutant  compliance




data for facilities producing more than three different pollutants.




    Up to  ten different  pollutants  may be  stored on the master  file for one




facility.  The five  pollutants  subject to SIP regulations -  PT,  S02,  HC,  CO,




and  NOX  - are always stored in  this order  on  the  master  file.  There  are




five more  available  areas to which you may  enter pollutants  other  than those




subject  to SIP  regulations.  Again,  the  order or sequence in  which you enter




this information makes no difference.




    When adding  or changing  information  to a certain pollutant,  you  must use




the pollutant ID as the key or reference to the information you need to add or




change.  The  position the  pollutant has  in  the master file has  no impact on




how  you  enter the data on card type 3.   For example,  if  you  need to change




information  associated with  the pollutant  "HC"  which  appears  third  on  the




master  file,  you  need not  use  the  third  position  for  entering  pollutant




information on card type  3 - you may use the first set of boxes  on the card.




    When deleting information for a specific pollutant,  enter the  pollutant ID




and  code an  asterisk in the field  of information that you  want  deleted.  If




you want to delete all information from  a pollutant,  enter a "D"  in the field




labelled "DROP".   When using either method for deleting pollutant information,




the Update Code  in column 80 must be "C" for change.




    You  can never enter  a  "D"  in the Update  column,  column  80,  when deleting




data  on  card 3;  nor  will  you  be   able  to  enter an  "N"  in  column  30  when




entering data on this card.   Card type 3  is generated by the system when a new
                                      -17-

-------
                                                      EFFECTIVE:  June 1, 1984




source or a new  card  type  1 is entered in the master  file  regardless  if any

information is being added  on  card type  3  at  this time.   Also,  a card type 3

cannot be deleted unless a  card  type  1 delete is entered to remove an entire

source from the  master file.   All  information for  card type  3 must be entered

into the master file with a  "C" in column 80.

    Facility  Capacity,   RDE9-RD12,   Source  Classification   Code  '(CLAS)  and

Loading Derivation Code  (LDRC) are data  elements  on  card type 3  that are not

pollutant specific - only one  value per  source  for each  of  these elements can

be stored on the master  file at one time.

l_ l_l_l l_l  LJ  l_l  l_l LJ I_I_J_I_I_I
 21  22 23   24   25   26   27    28    29          33
PISA  PLLT  DROP PCMS RD14  PCLS PAQC      LOADING
              POLLUTANT  1
 34 35   36   37   38   39   40   41          45
  PLLT  DROP PCMS RD14 PCLS PAQC     LOADING
          POLLUTANT 2
 l_l_l  l_l l_l l_l l_l  LJ  I_LJ_LJ_J  l_l_l_l_l_l_l_l
 46 47   48   49   50   51   52   53          57   58                64
 . PLLT  DROP PCMS RD14 PCLS PAQC     LOADING         FACILITY CAPACITY
          POLLUTANT 3                             .
 l_l_l_l_l_l_l_l LJ_I  l_l_l  l_l  l_l_l  l_l l_l
 65                71   72 73   74 75    76   77 78   79   80
        RDE9            RD10    RD11    RD12   CLAS  LDRC UPDATE
                                                         CODE
  Card         Data          Data
Columns     Field Name       Type       	Remarks	

   21     Penalty Issue   Alphanumeric   See  Appendix page  D-l for  definition
          Addressed                     and  usage.
          Indicator
          (PISA)
                                      -18-

-------
                                                       EFFECTIVE:  June 1, 1984
  Card
Columns
   Data
Field Name
22 - 23   Pollutant ID
34 - 35   Identifier
46 - 47   (PLLT)
24,36,48  Pollutant
          Delete Flag
          (DROP)
25,37,49  Pollutant
          Compliance
          Code (PCMS)
26,38,50  RD14
Data
Type
Remarks
              Alphanumeric  Must  be   coded  for   each   pollutant
                            produced  by  a   facility.    Refer  to
                            Appendix  Page  D-2  for  a  listing  of
                            valid pollutant identifiers.

              Alphanumeric  Entering  a  "D"  in this  field  along
                            with  the  pollutant code  will  remove
                            all information on  the  master file for
                            that pollutant for the facility.

              Alphanumeric  Must  be   coded   for   each  applicable
                            pollutant.    This  compliance   status
                            should    represent    the    worst-case
                            compliance   status   of   all   emission
                            points   producing    that   particular
                            pollutant.  Refer to  Appendix Page D-4
                            for a  list  of  valid  codes   and  their
                            explanations.

              Alphanumeric  User supplied.
27,39,51  Pollutant       Alphanumeric  This  assigns  a  source  classification
          Classification                code  to  an  individual  pollutant  in
          (PCLS)                        the  repeating  pollutant area.   Valid
                                        values are 1, 2, B, U.
28,40,52  Pollutant Air   Alphanumeric
          Quality Control
          Indicator (PAQC)
                            This code  indicates whether  or not  a
                            source  emits  a criteria  pollutant  for
                            which  the  AQCR  is nonattainment.   It
                            must be coded as follows:
                                        1.  Leave 
-------
                                                       EFFECTIVE:  June 1, 1984
  Card
Columns
29
41
53
33
45
57
58 -  64
          Data
       Field Name
                   Data
                   Type
Pollutant
Loading (LOAD)
     Facility
     Capacity
Numeric
                Numeric
                           Remarks
4.  Code  "2"  if  the facility  impacts
    the  secondary  emission  standards
    only   for   pollutants   "PT"   or
    "S02" in a nonattainment AQCR.

5.  Code  "U"   if  the  impact  of  this
    pollutant   on   the   nonattainment
    status of the AQCR is unclassified.

This  represents  the actual  emissions
in  tons per year with no  decimals or
fractions.   It  is   coded   starting  to
the right of  the  field;  leading zeroes
may be used.

This   indicates   the   total   output
capacity of the products produced at a
plant.  Refer to  Appendix  Page D-9 for
the  units  of  measure  used  in  this
field.
 65  -  71

 72  -  73

 74  -  75

    76

 77  -  78
    79
     RD9

     RD10

     RD11

     RD12

     Source
     Classification
     Code  (CLAS)
     Loading
     Derivation
     Code  (LDRC)
    80
      Update  Code
                Alphanumeric  User supplied.

                Alphanumeric  User supplied.

                Alphanumeric  User supplied.

                Alphanumeric  User supplied.

                Alphanumeric  This  code  is  based  on  the  Alabama
                              Power  Decision definition  of  a  major
                              source   and   is    used  for   program
                              planning  purposes.   Refer  to Appendix
                              Page  D-14 for a  list of  valid values
                              and coding considerations.
                              *Required for new entry.

                Alphabetic    This  must be  coded for all  class Al
                              sources.    This  code   indicates   the
                              method  of emissions estimation used to
                              determine   the  source  classification
                              code for  the  source.   Valid values  are
                              A,  P,   I, and blank;  refer to Appendix
                              Page  D-15 for an explanation of these
                              values.
                              *Required for new entry.

                Alphabetic    Valid value is  "C".
                                       -20-

-------
                                                       EFFECTIVE:  June 1, 1984
    3.1.5  Card Type 4

    This is a  comment  card used  to  add additional  comments about  the  entire

source.  This  card  type  is also used for Mailing Label information.  Up to ten

lines  of  comments  may be  entered  (Line  Nos.  0-9)  for  an existing  source.

Mailing Label information if required is entered on separate Line Nos. A and B.

    Comment information will be entered  as  new,  an "N" in  column  80,  unless a

change to an  existing  comment line  is necessary.  Any line of comment entered

must have a valid line number.
 20
LINE
NO.
      21
                                SOURCE COMMENTS
                                           79   80
                                              UPDATE
                                               CODE
  Card
Columns

   20
21 - 79
   80
               Data
            Field Name

          Line Number
   Data
   Type
Numeric
             Remarks
Assign     comment     line     numbers
sequentially beginning  with 0.   Use  a
Source Data Report  or run a Quick Look
Report of  comments lines  to determine
if   a   source    has   had   previous
information entered.  A  line number of
"A"  or   "B"   indicates   the   mailing
address of a source if  it is different
from  the  street  and city on  cards  1
and 2; this  is used  primarily  for the
creation of mailing labels.
*Required for all entries.
                          Alphanumeric  Code  all  comment  information  related
                                        to the entire source (free-form).
          Update Code
Alphabetic
Valid values are "N", "C", or "D".
    Comment  cards  for  Mailing  Label  information  will  be  entered  in  the

following formats:
                                      -21-

-------
                                                       EFFECTIVE:  June 1, 1984
 20 21
LINE
NO.
     MANAGERS
       NAME
                       40   41
                           BLANK
                              79   80
                                 UPDATE
                                  CODE
  Card
Columns

   20
21 - 40

41 - 79
     Data
  Field Name

Line Number
   Data
   Type
             Remarks
Alphabetic
Value   'A'   for   Mailing   Label
Manager's Name.
Manager's Name  Alphanumeric  Manager's Name for Mailing Labels.

                Blank         No data entered here on line  'A'.
 20 21
LINE
NO.
    STREET NAME
       40   41   42
           BLANK
             BLANK
56   57
    BLANK
  58  59    60    61           65
  STATE  BLANK     ZIP CODE .
  ABBR.
                     66
                                       BLANK
                                            79   80
                                               UPDATE
                                                CODE
  Card
Columns

    20
     Data
  Field Name

Line Number
 21-40    Street Name


    41

 42  - 56    City Name

    57
   Data
   Type
             Remarks
Alphabetic    Value  'B1  for Mailing  Label  - Address
              Information.

Alphanumeric  Street   Name   (address)   for  Mailing
              Labels.

Blank         No data  entered here on line  'B'.

Alphanumeric  City Name  for Mailing Labels.

Blank         No data  entered here on line  'B'.
                                       -22-

-------
                                                       EFFECTIVE:  June 1, 1984



  Card         Data          Data
Columns     Field Name       Type       	Remarks	:	

58 - 59   State           Alphabetic    State Abbreviation for Mailing Labels.

   60                     Blank         No data entered here on line 'B'.

61 - 65   Zip Code        Numeric       Zip code for Mailing Labels.

66 - 79                   Blank         No data entered here on line 'B'.

   80     Update Code     Alphabetic    Entire source (free-form).
                                       -23-

-------
                                                       EFFECTIVE:  June 1, 1984
    3.1.6  Card Type 5

    This card  is  used to add emission point data for each pollutant emitted by

a  facility.    An   emission  point  represents  information  for  one  regulated

pollutant coming  from one process or stack.   Processes  which emit two or more

pollutants should  be  coded  with multiple  emission  point numbers.   One method

of assigning  emission point  numbers  is to use the  NEDS emission point number

for the first two digits  of  the  CDS emission point  number  and the third digit

of the  CDS emission  point  number being pollutant  specific (1=PT, 2=S2, 3=HC,

4=CO, 5=M2).

    Point 000  contains compliance status and emission category information for

the entire source.   The system generates  the  000  point when  a  new card  1 is

added,  so  if  any information is  entered  into the  master file  by card 5 for

point 000 after card  1 has been entered, it must have an Update Code of "C" in

column  80.
 14  15 16   17 18    19   20                   27   28 29       30
 EMISSION   ACTION CARD         SCC CODE         CAPACITY  COMPLIANCE
 POINT NO.   NO.     NO.      (SCC8, SCC6, SCC3)     CODE      STATUS
                                                   (CAPC)     (CMST)
  31      32 33     34                                        48     49
 SIP   POLLUTANT                 STATE REGULATION                  (RD15)
 CODE     CODE                       (SREG)
 (SIPC)   (PLUT)
 _______       __   _        _         _
 50                              74    75     77   73        79         30
         PROCESS DESCRIPTION           MULTIPLE   RDE7   PROCEDURAL   UPDATE
              (PROS)                   CROSS          COMPLIANCE   CODE
                                     REFERENCE          (CMS2)
                                      (MULT)

-------
                                                       EFFECTIVE:  June 1, 1984
  Card
Columns

 1-13
14 - 16


17 - 18

   19
     Data
  Field Name

Source
Identifier

Emission Point
Number

Action Number

Card Type
Number
   Data
   Type
             Remarks
20 - 27   SCC Code
Numeric


Numeric


Numeric

Numeric


Numeric
28 - 29
   30
Capacity Code
(CAPC)
Compliance
Status Code
(CMST)
Numeric
Numeric
    31      State  Imple-    Numeric
           mentation Plan
           Code  (SIPC)
Refer  to  "All  Card  Types"  (Section
3.1.1).

Valid values are 000-999.
Constant "00" for card type 5.

Constant "5".
This   code    is    the   NEDS   source
classification  code  which  provides  a
detailed   analysis   of    the   process
creating  the  emission  for  a  point.
Refer to  the  NEDS coding  manual  for  a
list  of   valid   values.    All  eight
positions   should  be  coded   on  all
points other than  000.

This   is   required   for   coal-fired
boilers     other     than    electrical
utilities provided that  the boiler has
a  heat   input  capacity   equal  to  or
greater than 100 MMBtuH.

This  code  indicates  whether  a source
is  in compliance, not  in  compliance,
or  whether  the  compliance  status  is
unknown.    The   compliance  status  on
point  000  should  reflect  the worst-
case  compliance of any  process within
the  source.  The  compliance status on
all  other  points  should  reflect  the
compliance  of  that  particular point.
Refer to  Appendix Page E-3  for a list
of valid  values and their  explanations.
*Required for new  entry.

This  codes  identifies   the   type  of
enforcement schedule  which  has  been
imposed    on    a   source    not   in
compliance.   Refer   to  Appendix  Page
E-5  for  a  list  of  valid  values  and
their explanations.
*Required for new  entry.
                                       -25-

-------
                                                       EFFECTIVE:  June 1, 1984
  Card
Columns

32 - 33
     Data
  Field Name
   Data
   Type
Remarks
Pollutant Code  Alphanumeric  Necessary   for    all    new   emission
(PLUT)                        points.   It   indicates   the   type  of
                              pollutant    which   that    particular
                              emission   point   emits.    Refer   to
                              Appendix Page  E-6 for a  list  of valid
                              pollutant codes.
                              *Required for new entry.
34 - 48
   49
50 - 74
State
Regulation
RD15

Process
Description
Alphanumeric  This  contains   the   state's  emission
              regulation  for  a  given point.   Refer
              to Appendix Page E-7 for valid values.

Alphanumeric  User supplied.

Alphanumeric  This  is   a  brief  description  of  a
              specific  physical  emission  point.   At
              point   000,  this   may  be   used  to
              describe  the  type of  facility.   Names
              and  abbreviations  should  be  concise
              and  uniquely   describe  the  emission
              point.
75 - 77
Multiple        Numeric
Cross-Reference
(MULT)
              When  one physical  emission  point  has
              several  CDS  emission  point  numbers,
              this  field  is  used to tie together the
              various   numbers   referring   to   one
              physical  point.   If  emission  points
              010,  Oil,  and   012   refer  to  three
              different   pollutants   being  emitted
              from   one   process    or   piece   of
              equipment,  points  Oil  and 012  should
              cross-reference.point 010.
    78
RDE7
Alphanumeric  User supplied.
                                       -26-

-------
                                                       EFFECTIVE:  June 1, 1984
  Card         Data          Data
Columns     Field Name       Type       	Remarks	

   79     Procedural      Alphanumeric  This  is  used for  all NSR,  PSD,  NSPS,
          Compliance                    NESHAP,   and   SIP   facilities   under
          (CMS2)                        construction or  subject  to performance
                                        tests,  continuous  monitors,  and other
                                        procedural requirements  under such air
                                        programs.   This  field  indicates  the
                                        compliance  status  of  a facility  with
                                        respect  to  all applicable  procedural
                                        requirements.    It   is   also  used  to
                                        indicate    the    compliance    of    an
                                        operating    facility     subject    to
                                        immediately      effective      emission
                                        regulations.  Refer  to  Appendix  Page
                                        E-12  for a  list  of valid  values and
                                        their explanations.

   80     Update Code     Alphabetic    Valid values are "N", "C", or "D".
                                      -27-

-------
                                                       EFFECTIVE:  June 1, 1984
    3.1.7  Card Type 6

    This  is  a comment  card  used  to  add additional  information  about  an

emission point.   Up to  ten comment  lines  (0-9)  may  be  entered  for  a single

emission point number.  New comments must be entered with an "N" in column 80.
 14 15 16   17 18   19   20   21
 EMISSION  ACTION  CARD LINE
  POINT      NO.    NO.  NO.
   NO.
                              EMISSION POINT COMMENTS
                                             79   80
                                                UPDATE
                                                 CODE
  Card
Columns

 1-13
14 - 16
   19
   20
 21  -  79
    80
     Data
  Field Name

Source
Identifier
   Data
   Type
Numeric
Emission Point  Numeric
Number
17 - 18   Action Number   Numeric
Card Number
Line Number
Numeric
Numeric
                                           Remarks
                              Refer  to  "All   Card  Types"   (Section
                              3.1.1).

                              Enter  the   specific  emission   point
                              number to which  the comment refers.

                              Constant  "00".

                              Constant  "6".

                              Each  line  of  comment  information must
                              have  a  valid   line   number.    Assign
                              comment   line   numbers   sequentially
                              starting   with  0.    If  comment  lines
                              have   already   been   entered  for   a
                              particular emission  point, refer to  a
                              Source Data  Report  or  a  Quick  Look
                              Comment  Line  Report  to determine  the
                              next  valid  sequential  comment   line
                              number.
                              *Required for new entry.

Emission Point  Alphanumeric  Code  all  comment  information  relating
Comments                      to  the  specific emission  point  number
                              (free-form).
Update Code
Alphabetic    Valid values are  "N
                                                          •M'«   "I"1"
                                                         or
                                       -28-

-------
                                                       EFFECTIVE:   June 1, 1984




    3.1.8  Card Type 7

    This card  is  used to add information regarding actions taken by the local,

state, or federal regulatory agencies.  Each region has its own table  of valid

action  types  and   is  responsible  for  informing  the  National  Data  Bank

Coordinator  of any  changes to  the  table.    Refer to  Headquarters  guidance

material for instructions on inclusion of specific actions.
 1                                   13
   REGION-STATE-COUNTY-SOURCE NUMBER
  14 15 16   17 18   19
  EMISSION  ACTION  CARD
  POINT NO.    NO.     NO.
20


| |
55
DATE

Card
Columns
34 46
OPTIONAL ACTION DESCRIPTION
USED WITH ATPE 00
1 1 1 1 1 II 1 1
1 1 1 1 1 II 1 1
60 61 66 67 68 69
ACHIEVED DATE SCHEDULED STAFF
CODE
t
Data Data
Field Name Type
52 53 54
PENALTY AMOUNT ACTION
TYPE

70 71 72 73 80
RESULTS RDE8 UPDATE
CODE CODE


Remarks
 1-13   Region-State-   Numeric
          County-Source

14 -  16   Emission Point  Numeric
          Number
 17 -  18   Action Number   Numeric
Refer  to  "All  Card  Types"  (Section
3.1.1).

Enter   the   'specific   emission   point
number  affected for  the action.   Use
000  for  actions  which apply  to  the
entire source.

Action  numbers   should  be   assigned
sequentially  starting  with  "01"  and
ending  with  "98".   Action  number "99"
may  be  used  if  the  next  sequential
action  number   is  not  known.    The
system  will   convert  the  "99"  to  the
next  action  number  for that  emission
point.
                                      -29-

-------
                                                       EFFECTIVE:   June 1, 1984
  Card
Columns

   19

20 - 34
     Data
  Field Name

Card Number

Optional
Action
Description
   Data
   Type
             Remarks
Numeric
Constant "7".
Alphanumeric  This field is  used  only when an action
              type "00" is  coded.   Action  type  "00"
              is  used  when no action  type  exists on
              the action table for  the action.   This
              description  is  optional;  action  type
              "00"  will  be  accepted  without  this
              description field entered.
46 - 52   Penalty Amount  Numeric
53 - 54   Action Type
                              This   indicates   the   civil   penalty
                              amount   imposed  on  a   facility  and
                              should only  be used with action types
                              Z4   (State  civil   penalty)  and   Z6
                              (Federal   civil    penalty).    Dollar
                              amounts  should be  right  justified  and
                              rounded   to   the   nearest   $100.    No
                              commas,  dollar signs,  or  periods  may
                              be used.
                Alphanumeric  This  is  a two  position identifier for
                              an  action  description.   Each  region
                              has  its  own action  type  table  which
                              can   be   obtained  by   following  the
                              procedures described  in Chapter  10 of
                              the  CDS  User's  Guide.    Please  inform
                              the national  DEC of any adds, changes,
                              or  deletes   needed  for  your  action
                              table.
                              *Required for new entry.
55 - 60   Date Achieved   Numeric
61 - 66   Date Scheduled  Numeric
                              This data  indicates  when an action has
                              been   performed   or  completed.    The
                              format  is  month,  day,  year,  in  which
                              month  must be  between  01-12, day must
                              be  between  01-31,  and  year must  be
                              greater than 60.

                              This  date  indicates  when an action is
                              to be  performed.   The format is month,
                              day,  and year,  in which month must be
                              between  01-12,  day must   be  between
                              01-31,  and  year must  be greater than
                              60.
                              *Required  for  new  entry.
                                       -30-

-------
                                                       EFFECTIVE:   June 1,  1984
  Card
Columns
   Data
Field Name
Data
Type
Remarks
67 - 69   Staff Code
70 - 71   Results Code
72 - 73   RDE8

   80     Update Code
              Alphanumeric  This  is a  three  position code  which
                            refers to the staff member assigned to
                            complete the  action.   All  valid  codes
                            must   be   on   the  personnel   table.
                            Please  inform  the national DEC  of any
                            additions,   changes,   or  deletions  to
                            this  table.   Follow  the  instructions
                            in Chapter 10 of  the  CDS  User's  Guide
                            to  obtain   a  current  copy  of  the
                            personnel table.

              Numeric       This code indicates whether or not an
                            action  has   been   achieved or  whether
                            another action  should be  referred to.
                            This  code  must exist  on  the  results
                            code table;  any additions, changes, or
                            deletions for your regional table must
                            be  made known  to the  national  DEC.
                            Refer  to  the  instructions in  Chapter
                            10 of the CDS User's Guide to  obtain a
                            current copy of the results code table.

              Alphanumeric  User supplied.

              Alphabetic    Valid values are "N",  "C", or "D".
                                       -31-

-------
                                                       EFFECTIVE:  June 1, 1984




    3.1.9  Card Type 8

    This card is used to enter additional information about  actions  already in

the master  file  or those actions that  are  being added with the comments.  Ten

lines of comments  (0-9) may be added for a specific action.
 1                                   13
   REGION-STATE-COUNTY-SOURCE NUMBER
                                14 15 16   17 18   19    20
                                EMISSION  ACTION  CARD  LINE
                                POINT NO.    NO.     NO. NUMBER
 21
                          ACTION COMMENTS
                                                     79   80
                                                        UPDATE
                                                         CODE
  Card
Columns

 1-13
14 - 16
     Data
  Field Name
Data
Type
Region-State-   Numeric
County-Source

Emission Point  Numeric
Number
17 -  18   Action Number    Numeric
    19      Card Number     Numeric

    20      Line Number     Numeric
Remarks
           Refer   to
           section).
"General  Coding"   (first
           Enter   the   three  position   emission
           point   number   to  which   the   action
           comment refers to.

           Enter the exact action  number  that you
           want  the  action  comment to refer to.
           Note:   If two  or more  actions   (card
           type  7) have been  entered as  New for
           the  same  point  number  with an action
           number   "99"   to  obtain   the   next
           sequential action number,   you  may not
           enter  a  comment  line  with an action
           number  "99"  -   the   comment   may  be
           entered on the wrong action number.

           Constant  "3".

           Assign     comment     line     numbers
           sequentially  starting with 0.   Use  a
           Source  Data  Report  or run a Quick Look
           Report  of comments lines  to determine
           if an  existing  action has had  previous
           information entered.
           *Required for new entry.
                                       -32-

-------
                                                       EFFECTIVE:  June 1, 1984
  Card         Data          Data
Columns     Field Name       Type       	Remarks	

21 - 79   Action          Alphanumeric  Code  all  comment  information relating
          Comments                      to    the    specific    action    type
                                        (free-form).

   80     Update Code     Alphabetic    Valid values are "N", "C", or "D".
                                       -33-

-------
                                                       EFFECTIVE:  June 1, 1984
4.0 SCHEDULE OF DATA INPUT

4.1 Quality Assurance Outline

    Eight Steps in Quality Assurance

    CDS  quality assurance  procedures can  be  thought  of  as  an eight  step

process.  CDS  data  managers are responsible for all  of the eight steps.  They

are as follows:



    4.1.1  Status of Data to be Input

    Examine  source  documents - when  possible  cross-reference source documents

to determine the validity of the documents.



    4.1.2  Status of Current Data on File

    Run  CDS  retrievals to  determine  what  data are on  the  CDS data file.  The

retrievals  should  reflect  data  elements  affected  by  the  information being

prepared for input.



    4.1.3  Code Data


    1.  Analyze and determine best input medium.

        -  Coding sheets.
        -  Data Entry Package on Minicomputer or WYLBUR.
        -  WYLBUR Entry Package.

    2.  Code  changes;  prior  to  making  changes  be  absolutely  sure  of
         results of changes; do not assume anything.

        -  New data.
        -  Change data.
        -  Delete  data (a  delation  of an  entire  record  will delete  any
           data elements under  ;t in  the file hierarchy).

-------
                                                   EFFECTIVE:  June 1, 1984
4.1.4  Random Check of Coding Data
1.  Verification.

    -  At  this   stage,   perform  verification  on  approximately  50
       percent of all data.

    -  Verification should be done by another employee.
4.1.5  Input to Edit


1.  Submit all transactions to CDS edit.

2.  Choose "dummy" or production mode of edit.

       Dummy Edit  will  edit data and produce  a report,  but not affect the
       actual master file.

       Production  (or  live)  edit  will edit  data, produce  a  report and
       create  a  file of  transactions  to be applied to  the master file  in
       the update  cycle.



4.1.6  Validate Edit Results


1.  Review Edit Reports.

2.  Make corrections  immediately.



4.1.7  Enter into  Update Cycle


1.  Review Update  Report.

2.  Correct errors immediately.
                                   -35-

-------
                                                       EFFECTIVE:   June 1,  1984
    4.1.8  Validate Update Cycle Results






    1.   Check before and after retrievals.




    2.   Check final retrievals against source documents.




           Verify 10 percent of all data worked on.






    4.1.9  Key Considerations




    4.1.9.1  Priorities in Quality Control




    Ideally, all  data in  the data base  should be  correct;  however, keep  in




mind that  some  data elements are more important than others.   These priorities




usually  involve   all   major  sources  and   selected  minor   sources  within




nonattainment areas.   After these priorities are met, an effort should be made




to standardize the following data elements:  company  name,  street  address, and




process  description.   There  is  some  guidance  on  abbreviations  in the CDS




manual.   The  key  to  standardizing  data  elements  is  consistency.   If you




abbreviate  "company" as  "CO" on one source, do not abbreviate it as "COMP." on




another  source.   After  these  data elements are  unified, other  data elements




should be  reviewed as  needed for specific enforcement programs.  Items in this




category might  include SIC code, MEDS  cross-reference,  procedural  compliance,




SIP code,  and Government Facility code.








    4.1.9.2  Understanding  the  Data




    When entering the  data into a  system,  you must  be careful to  follow the




rules  and  conventions  for  particular data  elements.   Often it maybe  necessary




to  consult  a  manual.   For  instance,  there  is  a  big  difference  in CDS  if




pollutant  loads are  reported  :n hundreds,  thousands,  or millions  of tons per




year.   Further,  there  are data  elements  that are  left  and  right   justified.

-------
                                                       EFFECTIVE:  June 1, 1984











There are  fields  where a  decimal point  in the  field  will be  meaningful and




fields where  it  is  not.   All conventions (e.g., number of implicit errors in a




field) are mentioned in the CDS User's Guide and the Appendix to this manual.




    When  dealing  with  source  documents,  make  sure  that you  understand what




data  are  on  these  documents.   For  example,    EIS  printouts contain  emission




headings  titled "allowable"  and "estimated."   It  is necessary to understand




the difference  between  these two sets of numbers and which set  is applicable




to CDS.









4.2 Methods of Entering Data




    All input data  to the CDS  must  be prepared in the  format of one  of the




eight card layouts.   These are the only formats the system will accept.   There




are several ways in which data  can be  input to  CDS.  Data may  be entered  using




actual  80-column  cards keypunched from coding  sheets,  modified coding sheets,




or   formatted   retrievals;    special   terminal   techniques    using   WYLBUR;




minicomputer  packages;  the EMS-to-CDS converter; or.interface  files from  state




CDS installations.









    4.2.1  Data Submission Using  30-Column  Keypunched Cards




    Data  is  either  coded on data entry  sheets, modified data  entry sheets, or




retrievals.




    These  are sent  to  be keypunched  and then  submitted through a card  reader




using the appropriate JCL for  running the  Edit Program.  The  JCL for  running




the  Edit   Program  is  shown  in  Figure 4-1.   Allow plenty  of  time to have  the




data  sent to the keypunch  service  and  ."turned for submission  to the  weekly

-------
                                                                              EFFECTIVE:  June  1, 1984
AUTHOR TRC
PROGRAM NAME CDS EDIT
TASK NUMBEH
JCL for using the CDS Edit with card input.
1
L
/

/
/
-
7
V
2
/
*

/
/



/
*
3
i
R

C
E
4
i
o

D
D
Pla<



E



0
S
i
u

s
1
:e



f
6

T

E
T
s




7

E

D
•
1




B



1
C
L




9



T
A
in




10

P


R
P




II

R


D
at




12
J
1

E
S
t




13
O
N

X
1
n




14
B
T

E
N
in




IS



C

sa




16
(
R



ct




17
a
M

C
D
i(




II
a
T

D
D
Dn




19
a
r

S

i




20
a
r

1
*
mi




21
C


P

ne




22
D


T

di




23
S


n

at




24
Y


/

e




25
P


P

iy




26
/


A






27
M


R

if




21
•


29
i


M.

1
ter








30
•


i

tt




31
)


n

ie




32
/


n

a




33
I


S

be




34
U


s

)V




35
S




e




36
E


i

JC




37
R




:L




31





c




39
1




ar




40
D




d




41
/









42










43










44










4$










46










47










4«
'.



—




49









SO










SI










52










S3










54










55










56










5?










SI










I
CO
oo
i
           The above two cards should be placed at the end of the input transactions.
                         Where:
                                iii  Is the  User's Identification.
                              aaaa  Is the  User's Account Number.
                                 rr  Is the  User's Remote Number.
                                  n  Is the  User's Region Number or State  Code;
                                     Valid Values are 1-10,  TN, SC, NE,  etc.
                                 nn  Is the  User's Region Number; Valid  values
                                     are 01-10.
                                 ss  Is the  User's State Code,  where applicable;
                                     valid values are SC, TN, NE, etc., contractor
                                     Identifier TR  or TRC  for TRC, GE  for GEOMET,  etc.
                                    Figure 4-1.  CDS Edit Job Control .

-------
                                                       EFFECTIVE:  June 1, 1984




CDS update.   Since  multiple runs  of  the  Edit  Program may  be made  between

update  runs,  it is best  to  submit  data in several  smaller  batches during the

week as the data is returned from keypunching.



    4.2.2  Data Submission Using Special WYLBUR Techniques

    WYLBUR can  be used  in  conjunction with the CDS  retrieval  to create input

punch card formats  for the CDS  edit.   It  is  not wise  to  use  this  method of

submission for  new facilities  or highly changeable data;   but  when a uniform

add, change, or delete must be made to a particular CDS  punch  card type, users

should  consider  using  WYLBUR   rather  than  ordinary coding  sheets.   If  the

selection logic  of  the CDS  retrieval can be  used to extract those CDS master

file  records  which must  be  changed,  WYLBUR can be  used to  create the desired

input.

    The following  steps  outline how WYLBUR might be  used to perform any of the

above tasks:
     1.  Formulate  the  retrieval   selection  criteria  cards  which  will
        create  a  Quick Look Report and  then  be manipulated and converted
        into  input punch  card formats.   The  40 card  used for printline
        formatting  should contain  NOHD,  REGN,  STTE,  CNTY, SRCE,  and any
        other  applicable  data elements  which  will  be  needed for  each
        input transaction.

     2.  If  the  retrieval  is submitted via punch cards, a special JCL card
        must be added after  the job card  to make it  possible to fetch the
        retrieval output  via WYLBUR:

                             /*ROUTE   PRINT     RMT255
        Card Columns         1          10       16

        If  the  user  creates the  retrieval  via WYLBUR,  he should submit
        the job using the following command:
                                       -39-

-------
                                               EFFECTIVE:  June 1, 1984
                    ? RUN UNN FETCH

This command will  enable the user  to  manipulate the  output from
the  retrieval.   Users  must  note  the  job  identifier of  the job
which will  be retrieved by  WYLBUR.   Be  sure to  note your job
number; it will  be used to  fetch  the  job into your work space on
WYLBUR.

An example of  input that can be prepared  by use of  a retrieval
and WYLBUR reformatting  is inspections.

If  a user  wishes  to schedule  inspections for all  sources that
have had an inspection the previous year, the  user  would submit a
retrieval selecting the  appropriate action  type and date range.

      10 ATPE M XX             Where  XX  is  the  action type for
                               the  inspection

      10 DTAC G 100181         or suitable  date range.

      10 DTAC L 093082

The user would  request a Quick  Look Report with any source  level
data  element  on  the  40 card to develop a line of  data  to work
with  on WYLBUR.   Be  sure   not  to use NOHD  on this  particular
retrieval.

      40 SNME

After  submitting the  retrieval  and allowing  a suitable time for
the  retrieval to have  been processed,  sign  on to WYLBUR and  enter
the  following commands.

FETCH nnnn CLEAR               Where   nnnn  is  the  job  number of
                               your retrieval

LIST LAST                      To   show  total  number  of   report
                               data lines

DELETE  NOT  '000  00' IN ALL     To   remove  other  than  data  lines
                               from your  work area   (this will
                               look  for  the  point  number  and
                               action  number on  the  report  lines
                               and delete everything  else)

NUMBER                         To  resequence file  and show  total
                               number   of   records.    Last   line
                               listed  on terminal  should  be  same
                               as   total  number  of  Quick  Look
                               Report   lines  shown  in  LIST  LAST
                               above.
                               -40-

-------
       CHANGE
To
NOLIST
       CHANGE  1 TO  'rr1

       CHANGE  17/133 TO  '997'
        CHANGE  53/54  TO 'aa'
        CHANGE 61/66  TO 'MMDDYY'
        CHANGE 80 TO 'N'
        COPY ALL TO .1 FROM //EDIT
        RUN UNN
                                                      EFFECTIVE:  June  1, 1984
To remove spaces  from  data in work
area

Where rr is region number

This  will  setup  the action number
to   assign   the   next  sequential
action  number  and  will  set  the
card code to 7 for actions

Where aa  is  the appropriate action
type  code for  the inspection being
scheduled

Where MMDDYY  is the date  scheduled
for  the  inspections,  in the format
of month, day, year

This will set  the update code to N
for new transactions

This  will   copy   your  edit  job
control (JCL)  to  the  front of your
transactions

Your  data set  is now  ready  to be
saved if you wish to save  it.
        This will  submit  input transactions  to schedule  inspections  for
        the  entire   source  (point  000)   for  all  sources   that   had
        inspections in the previous date period.
    As an  aid  in converting  retrieval output  into  CDS input  transactions,

users are  urged to create two  data  sets  on their WYLBUR  source  libraries  for

the input JCL and the retrieval JCL.
                                      -41-

-------
                                                       EFFECTIVE:  June 1, 1984
    4.2.3  Data Submission Using Minicomputer Packages

    This method  is an  automated  means for  entering data in CDS  by using the

Regional Office DEC  PDF 11/70  minicomputer.   The user enters the  data through

a CRT  terminal which then performs the CDS  edit and displays any errors.  All

edited data is stored in the PDP 11/70 master  file  and is then sent to NCC to

be submitted to the weekly CDS update.

    The following  explanation  covers  the  most common CDS  entry package in use

throughout  the  regions.  Small  differences  in  terminal  features  may be noted

from region to region.



    Description of Screens

    There are ten  separate screens in the CDS Data Entry Package.   They are:


    1)  KEYFORM -  This  is  the  first  screen.   It prompts  the  user for the
        state number, county number, and source  ID number.

    2)  CDSMENU1 - This  is the second screen which  comes up automatically
        after the  keyforra is filled.   It asks  the  user for the card  type
        (types 1-8)  that is needed.   The  "card type"  reflects  the eight
        separate cards which have always been used for CDS data entry.

    3)  FORM 1 -   Card Type 1:  Facility (source) level.data.

    4)  FORM 2 -   Card Type 2:  Additional facility data.

    5)  FORM 3 -   Card Type 3:  Pollutant compliance data  for the
                   facility.

    6)  FORM 4 -   Card Type 4:  Facility comment record.

    7)  FORM 5 -   Card  Type 5:  Emission point  data.

    8)  FORM 6 -   Card  Type 6:  Point comment data.

    9)  FORM 7 -   Card  Type 7:  Enforcement  actions for emission point.

    10)  FORM 8 -   Card  Type 3:  Action comment  record.
                                       -42-

-------
                                                       EFFECTIVE:   June 1,  1984
    There are  two Form No. 4  cards  used to code in mailing  label  information

which includes contact  name,  telephone number, address,  city,  state, and  zip

code.  This  information is coded using the  letters  "A" and "B" for the line

numbers.   Since this  information  is  not entered very often,  a  separate  screen

has  not   been written  to  facilitate  automatic entry into  the proper  card

columns.   It  is  therefore necessary to use  the  space  bar  and keep  track of

where the cursor is positioned in order to enter the data properly.


    Card A contains:  Manager's Name — Col. 21-40
                      Telephone Number — Col. 49-62

    Card B contains:  Street Name — Col. 21-40
                      City Name — Col. 42-56
                      State Abbreviation — Col. 58-59


    In order to enter mailing  label  data, the user must  do the following:


    1)  Sign onto the CDS  Data Entry Package and enter the  key items for
        the facility you want  to  enter label data for.

    2)  Select Card Type 4.

    3)  Enter accept code which is an asterisk  (*).

    4)  Enter  the letter  "A"  to the  prompt:   "ENTER  TEXT  LINE NUMBER";
        this will automatically put  the cursor  in column 21.

    5)  Enter  Card A data  using card  description  above, making  sure to
        keep track of columns.

    6)  Enter Update Code.

    7)  Card  B  data  is  processed  the same  way.   After  you  enter the
        letter  B to  the  prompt:   "ENTER  TEXT  LINE  NUMBER";  the  cursor
        will  be in  column 21.   Use the above  description  for Card B to
        place data  in the proper  columns.   Enter Update Code.

     3)  Send both cards to the PDF 11/70 master file using the  PF1 key.
                                       -43-

-------
                                                   EFFECTIVE:  June 1, 1984
Use of the Package
1)  Sign on to the PDF 11/70 computer.

2)  In  response  to PDS>,  type:   DEP CDS.   This brings  you into the
    CDS  Data  Entry  Package.   The  keyform  will appear  after a  few
    seconds to  enter the  state,  county,  and source  ID  codes  for the
    facility you want to enter data for.

3)  When  the  keyform  is  filled  in,  the   screen  will  automatically
    change  to  the CDSMENU1  form.   You then enter the  card type for
    the card you want to enter.

4)  After a card type is  entered,  the screen  automatically switches
    to  the  card  type you have selected.   You  can  then begin entering
    your data.   If you wish to  save data,  you must always  enter an
    asterisk (*) to the prompt:  "ENTER THE ACCEPT CODE".

5)  On  the  "card  type"  forms  (1-8), the  key  (from  the  keyform)  will
    always appear  at  the  top of the  screen.   The  form(s) will appear
    in  the middle  of  the  screen;  and  prompts,   notes,   and  error
    messages will  appear at the bottom of  the  screen.  As you fill in
    data  in response to  the prompts,  it  will  appear in the form in
    the middle of  the screen.   If you  enter an invalid  data element,
    an  error will  appear.

6)  Most card  type forms have "repeating  sections"  (cards 3, 4, 5, 6,
    7,  and 8) -  they will automatically repeat  the  card form you are
    in  until  you  send  the  data to  the  computer.   Sending the  data
    from  a  completed  form  is  accomplished   by  pressing  the  PF1
    (program  function   1)  key  on  the   upper  right   side  of  the
    keyboard.  If  a  form is missing  a  critical  data element,  it will
    not  be  sent.  An error message  will appear, and you must satisfy
    editing criteria  before you can  send the form.

7)  To  get  out  of the package, use  the tab key or  press  CONTROL Y.
    When you  reenter PSD> type LOGOUT, and you  will  be  signed off the
    system.
                                   -44-

-------
                                                   EFFECTIVE:  June 1, 1984
Special Function Keys Definitions
    PF2 Key - This key will  erase  the copy of  the  form from  the PDP
              11/70 master file.   When you  press  the PF2  key, the
              screen responds with,  "DO YOU REALLY WANT TO  ERASE THE
              CURRENT COPY OF THE  FORM?"  A response of "Y" (for yes)
              will initiate the erase.

    PF3 Key - Will duplicate  current fields  from a  previous  related
              field, if  the  field  is the  same size and  will accept
              the same data.

  LINE FEED - Accept current form and blank all  fields  but key fields
              (the  first  19  characters on the  card).   This permits
              more  data  with  the   same  key  values  to  be  entered
              without reentering the key fields.

     DELETE - This  key will  delete  the previously  entered character
              in current field  (if any).

RIGHT ARROW - Will advance to the  beginning of  the  next  field within
              a form.

 LEFT ARROW - Will  advance  to  the  beginning  of the  previous   field
              within a form.

   UP ARROW - Advances  to the  beginning  of  previous  line  (up)  or
              advance  to beginning  of  the next  line backwards, that
              has an input field.

 DOWN ARROW - Advances  to  the  beginning of the  next line  containing
              an input field.

  CONTROL P - Will  proceed  (skip)  to  the next  section  in the form
              (used on the card 3 form).

  CONTROL B - Proceed to the beginning  of  current secton or beginning
              of previous  section,  if already  at beginning  of current
              section.

  CONTROL F - Set to beginning  of the current form.

  CONTROL G - Erase  current  entries  on  this   form.   The  currently
              displayed  form is blanked and  restored to  its  original
              condition.

  CONTROL T - Return  to the  beginning of  the  next  less deeply  nested
              section.

-------
                                                       EFFECTIVE:   June 1, 1984
      CONTROL Y - Terminate the data entry session and exit  from  the data
                  entry  processor.   Answer  "Y"   (for  yes)  to  the  prompt
                  displayed after CNTL Y.
    Retrieving, Modifying, or Deleting Data

    The data entry processor for CDS  can also be used to  retrieve,  modify,  or

delete data on the  POP 11/70 master  file  at  any time before it is sent to NCC

by the Edit program.  If you enter a key for a facility and  then  select a card

type  (1-8),  you  will  automatically  bring up any  records on  the  PDF 11/70

master file for this same card which  may have  already  been entered  for this

facility.   The  key  will  appear  on  the  screen  in  the  card  form  you have

selected.   If   you  wish  to  modify  this  record,  simply  change   the  field(s)

desired and resend  the form by pressing the PF1 key.  You can step through any

form using the arrow  keys.   If  you wish to delete  this  record entirely, press

the  PF2  key,  answer  "Y"  to  the  prompt:   "DO YOU  REALLY WANT  TO  ERASE THE

FORM?", and this record will be deleted from the POP  11/70 master  file.

    For forms  with  multiple lines, you can delete any one line by deleting the

asterisk  (*)  in the first column  for the  line  you want  deleted  and pressing

the PF1  key.   This  sends the form back to the POP 11/70 master file, but does

not send the line without the asterisk.  For  example,  suppose  you entered five

lines  of  text  yesterday on  card 4 for a particular  facility, and you now want

to delete one  of those  lines of comments.   Sign onto  DEP,  enter  the key  fields

for  this facility,  and  select card  4.   All five  lines of text  which were

entered  the previous day  on  card  4  for this  facility  wall  appear  on the

screen.   Delete the asterisk (*)  from  the  card  YOU v/ant deleted and  chen press

-------
                                                       EFFECTIVE:  June 1, 1984
the PF1  key.   Four lines of text  (those  with the asterisk) will  be sent back




to the POP 11/70 master file.  The  line  without the asterisk  will  not be sent




and is deleted.









    Using the Line Feed Key




    If you need  to enter more data  than  a form will accept,  you can  use the




line feed key.   For example, if you have seven lines of text and the form only




provides for five  lines  of text, press the  line  feed  key and then enter the




remaining two  lines of text.  The  line  feed key, like the  PF1  key, will send




the complete form to the PDP 11/70  master file, but it will also regenerate a




fresh copy of  the  current form  for  you  to continue on.   You  can then type in




the remaining  two  lines  and send them to the PDP 11/70 master  file using the




PF1 key.









    Running a CDS Edit




    To run a CDS edit from the CRT  terminal,  the  following  instructions  should




be followed:







    1)  Sign onto the PDP 11/70 minicomputer.




    2)  Type in the following command:  RUN  CDS001.






    The  run  time will appear  on the screen, and the  program will  start.  The




number  of  transactions  being  sent  through  the edit will appear next  to the




words —  "TOTAL  RECORDS  SORTED"; the program will  continue; and the messages:




"YOUR JOB  HAS BEEN SUBMITTED TO  MCC,  A  TRANSACTION  REPORT  WILL  BE PRINTED"

-------
                                                       EFFECTIVE:  June 1, 1984




should appear on  the  screen.  This means  that  all  the transactions  that have

been entered through  the CDS Data Entry Package have been gathered up and sent

to NCC.   A  regular  CDS  Edit Report  will  be  generated  as well  as  a  local

transaction report called CDS.CDS.

    If any  error  messages appear on the  screen when you are running  this  CDS

edit,  notify the system manager, make  sure to write  them down.   If an edit

fails, do not try again.

    Once this Edit  Program  (CDS001) has been run, the POP 11/70 master file is

erased which means  you cannot retrieve, modify,  or  delete data with  the Data

Entry Package since it has already been sent to NCC.'


    4.2.4  EMS-to-CDS Converter

    The EMS-to-CDS Converter is a stand-alone  program which creates card-image

input  to  the CDS  based  on  data contained on  the EMS  master file.  Once data

has  been  prepared  for  the   Enforcement  Management  System,  it  is  no  longer

necessary  to recede  and  repunch  the  same  data for the Compliance  Data System.

The converter provides an automated link between the  two systems.

    The  converter is  run on  request  as often as necessary to copy data from

the EMS master  file to the CDS.   The basic  run  parameters  of the converter are

provided  by a  control  card  which indicates the  starting and ending dates of

data  eligibility on the  EMS  master file.
 '"Zemaitis,   Tom;   "Computing  Data   System,   Data   Entry  Package   and  Report
 Retrieval  Package  on POP 11/70  - User Documentation."  7-31.
                                       -4S-

-------
                                                       EFFECTIVE:  June 1, 1984




    Input to  the  program is the  EMS master  file  and converter  control  card.

After the control  card has passed the  syntax edits,  each detail record on the

EMS master file is processed.  Eligibility is determined by two criteria:


    1)  The presence  of an  "A"  or  "C"  in the  retrieval code  (refer to
        coding form) on the master file source record, and

    2)  The comparison  between the data on the master file record and the
        date on the control card.


    The  EMS  master file  contains two  data   elements  which are  not  found  in

CDS.  The  date-added  (columns  157-162 of the EMS  record)  represents the date

on which the  record was first  added to the master  file;  date-changed (columns

174-179  of  the  EMS record) represents the most recent date on which  the record

was changed.   If  the  retrieval code on  the   source  record  contains  an  "A"  or

"C",  and if  the  date-added on  a new  record or the  date-changed  on a change

record falls  within the control  card's reporting  period,  the  record will  be

formatted for conversion.

    When the  entire EMS master  file  has  been  read,  four  totals  are printed:

the  EMS  master  file  record  count,  the  output  punched card count,  and the

converter report line count and page count.

    The  converter  output report serves as an audit trail to indicate  which EMS

records  have  been  passed  to  CDS.   It  should be  reviewed by  the  Data Bank

Coordinator and  later by the  corresponding EPA regional office.  These reviews

are needed to ensure  that the  state agency is satisfied that  the data is  ready

to  pass  and that the  region is  satisfied that the  data is  ready to be added to

CDS.

-------
                                                       EFFECTIVE:   June 1,  1984
    The Control Card Layout

    The converter  control card  must be present  for the  converter  program to

begin processing.   This card  makes sure that  the  right  version of the  EMS

master file  is  being used for the  conversion  and it also provides the program

with the starting and ending dates for conversion eligibility.

    This card must be made out as follows:
  Card
 Column

 1-2

 3-12

13 - 18

   19

20 - 25
   26

27 - 32
33 - 35

36 - 55

56 - 63

64 - 73

   74

75 - 80
 1

 6
 3

20

 8

10

 1

 6
            Data Name
        Control Indicator
        Current Date
        Starting Date
Ending Date
Control Card ID
                                       Value
EMS Serial Number
"ZZ"

Spaces.

Today's Date; MMDDYY format.

Space.

This  is  the beginning  date for  the
converter.   Records   placed  on  or
after this date will  be eligible for
conversion.  The format is MMDDYY.

Space.

Records  placed  on  the  EMS  master
file  on  or before  this date will be
eligible  for conversion.   The  format
is MMDDYY.

Spaces.

"EMS-to-CDS Converter".

Spaces.

"EMS  Serial".

Space.

EMS Master Serial Number.
                                       -50-

-------
                                                       EFFECTIVE:   June 1, 1984
    Action Type Conversion




    Because the action  codes  for EMS and CDS are  not compatible, a conversion




table in the program must be created.  The program must  be  recompiled whenever




there are additions  or  changes to the action codes,  regardless of whether the




changes are to the state or regional action codes.








    4.2.5  Interface Files from State CDS




    States  which  have   their  own  version  of   CDS   installed  on their  state




computer have  an  interface program to report to  national CDS.   The  interface




program  selects  sources to be  reported  to CDS, converts the  state,  actions to




EPA actions  (similar to  the  EMS-to-CDS  Converter),  and  produces a  computer




tape of  CDS transactions.  This tape is  sent  to the EPA  regional  office and




entered into CDS using the JCL for running the Edit Program as  shown  in Figure




4-4 of this manual.








4.3 Edit Processing




    4.3.1  Edit Program Usage




    Once data  for the  CDS has been coded and  keypunched,  users must validate




the input transactions  by running the CDS Edit Program.  The edit can  be run




at any time,  and it can be run any number of  times between update cycles.  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 before the weekly update.




    When running  the CDS  edit  ,  users  may identify their data by the ORIGIN




Code, as indicated in Figure  4-1  by the  letters.  If data  being input is  from
                                      -51-

-------
                                                       EFFECTIVE:  June 1, 1984
a state  report, users  can identify  the  state as  the ORIGIN of  the data  by

coding the  region  number and state abbreviation in the "FARM" statement of the

Execute  card (Figure  4-1).   If  ORIGIN  code  is  not specified,  the data  is

identified as being entered by the region.

    Since the update  cycle is  usually run  on Wednesday nights,  users  should

schedule  their  data preparation,  edit runs,  and  corrections to  be ready for

the  update  cycle.  At  least  one   day  before  the  update  when  the  input

.transaction  volume is under 2000 cards per week, an ideal schedule would be:


    1.   Punch cards  are delivered to the  regional  CDS data manager or to
         the  operator of the communications terminal as soon as possible.

    2.   Input cards  together with appropriate JCL  cards  are  submitted to
         NCC  on  the day  that they are  received.

    3.   The  Edit Report is examined on the following  day.

    4.   Edit errors are corrected and resubmitted after being examined.


    If  the  volume  of   input  transactions  is  over  2000  cards per  week,  or if

keypunching  is  returned to the  user in multiple batches,  it  is  best to run the

edit  several   times   during  the  week   as  soon   as data   is  returned  from

keypunching.

    The  edit validates each of  the  seven  punched  card types  one  at a time.

Note  that some transactions  which pass  the  edit may  be  rejected  later.   If  a

new facility is  being  entered  into  CDS, the edit may  accept  as valid all of

the transactions  for  that facility  except  card  1  which contains  the Source

Name  and  Address.  In the  update   cycle,  all  of  the  transactions  for  that

facility will be  rejected since the  facility  level  data  was  not passed to the

update.   With  the hierarchial  relationship between  source, point, and action
                                       -52-

-------
                                                       EFFECTIVE:   June 1, 1984





transactions, an  error at a  higher  level can create additional  errors  in the

update cycle for  transactions accepted by  the  edit.  For  this reason,  it  is

very important to correct and resubmit edit errors as quickly as possible.




    4.3.2  Edit Error Messages

    All  transactions  are  validated  by  the  Edit  Program.   The  Edit  Report

produced   by  the  Edit   Program  lists  the  action   taken   on  each  input

transaction.  If an input transaction  has  no edit error message  next  to it  on

the Edit  Report,  it  is  a valid  transaction.  One or more  error messages are

printed  on  the  Edit  Report  next  to  transactions  in  error.    Errors  are

identified  as   either  "Warning"  or  "Fatal".   One or  more fatal  errors will

prevent the  transaction  from .being saved for the  update cycle.  A transaction

with only warning errors will  be saved  for the update,  but  the  data elements

in error  are blanked out.  The user  must  review the Edit Report  carefully  to
                                                  i
verify accepted data and to make appropriate corrections for rejected data.

    All of the  errors  identified  by  the  Edit Program are  listed  in Table 4-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 MOD

File.  Transactions with  no  errors or with only warning errors will be  placed

on the  MOD File for future processing by the update.  Keep in  mind that  a data

element flagged with a warning message is blanked out by the edit.
                                      -53-

-------
                         EFFECTIVE:  June 1, 1984
     TABLE 4-1
EDIT ERROR MESSAGES
Data Element Name
Region
State
State
County Code
Source Number
Card Code
Update Code
Emission Point Number
Action Number
Source Name
Line Number
Update Code
Emission Point

Compliance Status
Action Number

Action Type
Update Code
Action Type
Update Code
Update Code
Action Number
Source Name

AQCR
City Code
Zip Code
SIC Code
Government Facility Code
Air Program Code
Staff Personnel Code-Source
SCC Code
SIP Code
Pollutant Code
Emission Category
Multiple Cross Reference
Date Achieved
Date Scheduled

For Detailed
Explanation,
See CDS User's
Message Guide Page
*** INVALID REGION CODE
*** INVALID STATE CODE
***. STATE NOT IN REGION
*** INCORRECT COUNTY CODE FOR STATE
*** SOURCE NUMBER MUST BE NUMERIC
*** INVALID CARD CODE
*** INVALID UPDATE CODE
*** EMISSION POINT MUST BE ZEROS
*** ACTION NUMBER MUST BE ZEROS
*** SOURCE NAME REQUIRED ON NEW ENTRY
*** LINE NUMBER MUST BE NUMERIC
*** UPDATE CODE D INVALID FOR CARD 2 & 3
*** EMISSION POINT MUST BE NUMERIC
*** POINT MUST BE GREATER THAN ZERO
*** INVALID COMPLIANCE STATUS CODE
*** ACTION MUM MUST BE GREATER THAN ZERO
*** ACTION NUMBER MUST BE NUMERIC
*** INVALID ACTION TYPE
*** NO DATA IN COL 21-79 FOR DELETES
*** ACTION TYPE REQUIRED FOR NEW ENTRY
*** DO NOT DELETE POINT 000
*** UPDATE R ONLY FOR REVISED ACTION
*** ACTION NUM 99 VALID ONLY FOR A NEW
*** SOURCE NAME MUST BEGIN IN COL 27
*** INVALID REGION ON CONTROL CARD
* INCORRECT AQCR FOR COUNTY
* CITY CODE SHOULD BE NUMERIC
* ZIP CODE SHOULD BE NUMERIC
* SIC CODE SHOULD BE NUMERIC
* INVALID FEDERAL FACILITY CODE
* INVALID AIR PROGRAM CODE
* INVALID STAFF CODE
* SCC SHOULD BE NUMERIC
* INVALID SIP CODE
* INVALID POLLUTANT CODE
* INVALID EMISSION CATEGORY
* MULTIPLE XREF SHOULD BE NUMERIC
* INVALID DATE ACHVD - OUTPUT ZEROS
* INVALID DATE SCHED - OUTPUT ZEROS
* DATE SCHED SHOULD BE MEW - OP ZEROS
A-24
A-52
A-52
A-9
A-48
A-92
A-9 6
A-64
A-76
A-46
A-9 4
A-96
A-64
,
A-59
A-76
A-76
A-77
A-96
A-77
A-96
A-96
A-76
A-46
A-46
A-5
A-7
A-5 7
A-37
A- 12
A-l
A-50
A-71
A-72
A-18, 67
A-62
A-65
A-78
A-81
A-81
         -54-

-------
                                                       EFFECTIVE:  June 1, 1984
                             TABLE 4-1 (Continued)

                              EDIT ERROR MESSAGES
Data Element Name
                    Message
                                  For Detailed
                                  Explanation,
                                See CDS User's
                                   Guide Page
Results Code
Update Code
Action Type
Pollutant Delete
Flag
            *
            *
            *
            *
Pollutant Compliance         *
Air Program Status           *
AQCR Indicator               *
Pollutant Emission Category  *
Procedural Compliance        *
Penalty Amount               *
Penalty Amount               *
Capacity Code                *
Source Compliance Code       *
Source Emission Category     *
Loading Derivation Code      *
INVALID RESULTS CODE                  A-86
ASTERISKS FOR CHANGES                 A-96
ACT DESC IGNORED - ATPE NOT 00        A-77
INVALID POLLUTANT DELETE FLAG         A-22
NO DATA TO FOLLOW DELETE FLAG         A-22
INVALID POLLUTANT COMPLIANCE          A-19
INVALID AIR PROGRAM STATUS            A-3
INVALID AQCR INDICATOR                A-16
INVALID POLLUTANT EMISSION CATEGORY   A-20
INVALID CMS2 CODE                     A-68
PENALTY AMOUNT ONLY ON Z() ACTIONS    A-84
PENALTY AMOUNT SHOULD BE NUMERIC      A-84
CAPACITY SHOULD BE NUMERIC            A-6,
INVALID SOURCE COMPLIANCE CODE        A-41
INVALID SOURCE EMISSION CATEGORY      A-44
LOADING DERIVATION SHOULD BE A, P     A-13
                                                           58
                                       -55-

-------
                                                       EFFECTIVE:  June 1, 1984
    For a detailed  explanation of the  valid values for  each data  element  in

the  CDS,  consult  Appendix A.   Coding  instructions  are  given for  each data

element; edit  error messages by  data element are  repeated in  this Appendix.

Certain  data  elements  are  not  validated  by  the edit  and  may contain  any

alphanumeric characters.



    4.3.3  Sample CDS Edit Report

    A  sample  Edit  Report  is  shown  in  Figure  4-2.  Each  page of  the  report

contains the  report title, the region name,  the date, and the time  at which

the  edit  was  run  by  the  computer.   The  report  also  contains column headings

for  the  following  data  elements:   Region,  State,  County,  Source,   Point,
           •
Action, Card Type,  and Update Code.   Directly  beneath  these column headings

are  two rows of numbers indicating  card columns; the  position of any data on

the  card can be determined by  referring  to these  card column identifiers.

     Note  that for  each new card 1 accepted by the  edit, a county  name  is

generated  and printed  directly beneath  the  County Code;  this  county name is

passed  to the  update,  where  it is placed  on  the  master  file together with all

the  other input data.

     Error messages are  identified  on the right-hand  side of  the  report.   In

addition  to the error messages,  data elements  in  error  will  have  one or more

asterisks directly beneath the data  element  to  help  pinpoint the problem area

which needs  to be  corrected.
                                       -56-

-------
                                                                                                          EFFECTIVE:   June  1,  1984
                                                           un n/M STMIM Mil ii' n
                                                               nil.ION 4-«llMI1*
                                                            S i mi i MI ON v.'/\<". '<
Ui
^4
I
RO
0
12
04
"1
04
04
04
04
04
00
04
SI
54
01
01
01
01
01
01
04
01
44
CNII
M, ;r
0*140
014H
0'iin
OhOli
Of. (id
Ol.liO
OtflO
ci.cn
?2?0
SMI
1
•10 Ii.)
unoti /
0 1100 I
0100 1
UVHl
O'lOOl
o-.ool
O'JOOI
OMIUI
OI'OU}
PNI
4M,
000
000
001
000
000
(100
000
001
0011
AN
Ml
00
00
00
00
00
00
00
00
00
CHI)
HP CARD CI'UJMUS!
2 3 4 fj h % r
•> oi ::3vii. »n'nii:M4!i(.7c.>)iii?i4lji. ti i d l: !> 34 •Ji,/i>*)0l?.\4'.i 7i- '••.•if.
4
•b
5
1
3
4
5
s
1
ICOAl I'HM'Ak Al lull PLAHI

lOV.UlO')'!

I'l 02
0 P|
0 PI


IHAIIII M'UIOOUt.-CllflRI HI



0 I'l
0 I'l

?Cn«l PKI PtkAl IPH PI MM
2CUAI. I'RI PAPAIIllll PI. « 1:1


SI A IIIS .UNMIOUII
OCOAL UPPLt
2COU IOAOIKC

III'?' A II.. | M i.f* »'! • ;/,.-.
11. Ill « • uAHI. I M; - 1 A 1 A 1 II ••' 1 1- 1 .it I 1 1 1
i. . • •• l .Mil . r>°' . i ,•,::•,
4 • t r i " i'
n .
r .
N .
1) .
«.•• r .
i. .
c . ••• INVAI IP suit (.T:
h . ••• II.VAlin KLIIOK 1 Cl 1
t •
MAI, 1C), .
04
04
04
(14
04
04
04
04
04
04
04
44
44
44
44
44
44
44
44
44
44
44
2270
2220
22i'0
2220
2'J?ti
2 J?0
2220
2220
2220
2J?0
Icl'l)
0000}
OH 1)01
ai/noi
onon
OOCU}
11(1001
000(1}
Ol-Oli}
OUOO)
0000}
04100
000
000
000
000
001
00?
00}
004
005
006
000
00
00
00
00
00
00
00
00
00
00
00
2
}
4
fj
9
s
5
5
s
5
1
xiuiur.il.
PI 03
ICO»l I'RC

30SOI019
30*^0 1 0*4S






52 0?
CfBAI ION PLANI
0 PI
0 Pt
0 I'l
0 PI
0 I'l
0 PT
0 52




3COM. l-Bf PARAIION I'l AN 1
3CRUSIIIR
3COMVOORS 121
3Si;iNf.
3UA.1HING PIAKI
310ADINO
2ROILCR

c .
c .
h .
f .
N .
h .
N .
X .
• . ••• INVAtIO IJPOAtl COtf
N .
C .
IIAMIlli.N .
04
04
04
04
114
04
04
04
04

04
04
04
04
II 4
04
04
(14
04
04
04
(>4
P4
(14

44
44
44
44
44
44
44
44
44'

44
44
4
4








44
44

121.0
1 ?lt(l
I?r0
in ii
ll'I.O
12110
1 fil u
12'tO
1240
CKIIill
1240
1 240
I2«0
I2-.0
Clilii.l
OlM 0
01. 1.0
0 I.I. II
3 l.i. U
01.1,0
II I.I' II
01,1 0
Ol. -it
o i.i. :.
CIIM'.I
04100
(14100
04100
II'. 100
U '1 1 U U
(14100
041(10
(I4IDU
1,11(1.11
y
(I (1 0 } }
1,11 II. I1,
0 1- II .1 }
010.1}
1:1 .AMIi
0 U (i / 1.
lit II ft,
II '< tl 1 1. .
(Ill ATll
1. ., ..In
1. "Ii /I.
II 1 1. / u
I, .Oil.
:. .' . / }
H II..I
0(10
000
000
000
000
001
002
00}
1100

ooo
1100
000
001

000
!>00
uno
IIP 1
,ii,;'
i,l' 3
till 4
nii'j
•inu

00
00
00
00
00
00
00
00
00

00
00
00
00
00
00
00
00
no
III)
ItO
III)
uo
no

2
3
4
4
b
5
9
s
1

2
3
i
i
1
2
3
•l
•j
I,
•l
s
»l
1

0»IS!-II«LL»S
PI 03
Hill: IK
2rtii.HrN i

30AO 1 O')1
30*jOIO')'l
3 O'.O IOVV

M RAHRDAI) SI
r,l»IIIS IIIIKNIIUN
3 PI
0 PI
0 PI
0 II

DAVTON III 36327

3COAI IIPPLt
JCSUSHrd
3CONVCVOR
JSCRICIIS
001 UK.G IliS COAHIBKIHG fll.l

IHAI r en
I'l 02

.in'.oio'i'i
III
CKOr.'.v II I
p 1 (, .'.



.'.••.'. Oll.*"i
ji:* i. nr ••
101 III Til!,
0' 1 l"i


y 3M«»

0 II
o n
\ Cl< 1 t K r. R A 1 N S
1 JI.S'j'i

II I'l
II PI
1 I 1
0 1 1
U i 1
n i l
1 II 1 H|l|« HI S


0033121 1

croAi nrpit
7i-i:il$KCI>
iNrnAviuN SPI.I- Ron
on>6iill

3rn AI 1 1 PPL t
3ul4t 0 An 1 HC
.*. SIOCAIT IRAb CC'-'. 1 >
'.C.I'H.;HI 1-
.'- 1^ r.i.;.i ! 14 a c <»nv! l r*
3RAIIRUT. LOAOUII?


C .
PA1 t .
t| .
N .
r .
N .
N .
K .
II .
.
1; .
1 / 1 C .
n .
'i .
''
•4 .
:AI c .
«. .
«, .
• .
v .
•« .
.. •
t. .
-.
                                          Figure 4-2.   Sample  Edit Report .

-------
                                                       EFFECTIVE:  June I, 1984
    4.3.4  Edit Job Control Language (JCL)

    To execute  the  Edit Program, use the JCL shown in Figure 4-1.  A number of

options are available with the Edit Program:


    1.  Card input  on a "dummy" basis.  This option  enables the  user to
        see  the Edit  Report produced  by his input  transactions without
        actually placing the transactions  on the output  MOD  File.   The
        "dummy"  mode  is particularly  useful if  the  user is  expecting a
        considerable  number  of  errors  which  can  be  corrected  and
        resubmitted prior  to the update cycle.   The  user should remember
        that no valid transactions on the  Edit  Report  are passed  to the
        update  when the dummy  mode  is being used.  Use  the  JCL shown in
       , Figure  4-3.

    2.  Input from  tape or disk.  Input  from a  disk file or a  tape file
        can  be  processed  by  the edit just  as  easily as punchcard input.
        Use the JCL shown  in Figure 4-4.

    3.  Saving  the  Reject  File.  All fatal  errors  identified by the edit
        can  be  saved on a disk file  for  correction  via WYLBUR, or they
        can  be  printed out  for re-coding.   This  optional file  is  an 80
        character  card image of the rejected  input  transactions.  If the
        Reject  File is  placed on a WYLBUR  data  set  for  corrections, the
        corrected file  can be resubmitted  as input  to the edit.  Use the
        JCL shown in Figures 4-5 and 4-6.

    4.  Submitting  Input via Retrieval and  WYLBUR.   If  input data can be
        formatted with  WYLBUR from a Retrieval  Quick Look Report, JCL can
        be  added to  the data  set  in  order to run  the  edit.   Use the
        procedures  shown in Figure 4-7.  This option should be used only
        if  the  user  is  already  familiar with  basic.   JCL  and  WYLBUR
        concepts.


4.4 Reading and Correcting Update Cycles

    4.4.1  Update Processing

    The  update  cycle  consists  of  a  series  of programs  which  apply input

transactions  to the  master  file.   All  input  transactions  which  contain no

fatal  errors are   stored  on the  MOD  File by  each  run  of  the Edit  Program.
                                       -58-

-------
I
Ln
vo
          AUTHOR   TRC
                                                NAME
CDS EDIT
                                                                                     EFFECTIVE:  June 1,  1984


                                                                               I TASK NUMUEM
         I Using the CDS Edit with  the "DUMMY" mode; with  this mode, no data is saved on the MOD  File.
1
/
/

/
7



/
/
2
7
*

/
/



/
*
3
i
R

C
E




E
4
i
O

D
D




O
s
i
LI

S
1




F
s

T

E
T





1

E

D
.





I



1
C





9



T
A





to

p


R





II

R


D





17
J
1

E
S





13
O
N

X
1





14
B
T

E
N





IS



C






16
(
R








17
a
M

C
D





18
a
T

D
D





19
a
r

5






70
a
r

1
*





71
C


p






77
D


T






23
S


n






74
Y









7S
P


T






26
t


Y






21
M


P






71
•


E






79
•


:






30
•


\






31
)


D






37
i


u






33
\


M






34
U


M






35
S


Y






36
E









37
R


/






38










39
1









40
D









41
/









47










43










44










45










46










47










48










49










50



—





51










57


-






53



-





54










55










56



—





57










58










           The above two cards  should be placed at the  end of the transaction deck.
                            Where:
                                    iii   Is the User's Identification.
                                   aaaa   Is the User's Account Number.
                                     rr   Is the User's Remote Number.
                                      n   Is the User's Region Number or State Code;
                                          valid values are  1-10, SC,  TN, NE,  etc.
                                 Figure 4-3.  Using  the Edit's Dummy Option.

-------
                                                                                EFFECTIVE:  June 1, 1984
         AUTIIOU
                   THC
                                      PROGRAM NAME
                                                   CDS F.DIT
                                                                           TASK NUM11FR
                   Using  tape input instead of punch card input  to the CDS Edit.
?
/
*

/
/
/
/
/
*
3
i
R

C
E



E
<
i
o

D
D



O
5
i
u

S
1



F
S

T

E
T




J

E

D
«




1



1
C




9



T
A




10

P


R




11

R


D




17
J
1

E
S




13
O
N

X
1




U
D
T

E
N




15



C





16
(
R


D




17
a
M

C
D




18
a
T

D





19
a
r

S
D
D
V


70
a
r

1
S
C
O


21
C


P
N
B
L


22
D


T
-
-
-


73
S


n
X
(
S


74
Y



X
R
E


25
P



X
E
R


26
i



X
C
-


27
N\



X
F
z


21
i



X
M
z


79
i




-
z


30
•



U
F
z


3
)



N
B
z


37
/



1

z


33
i



T
L



34
U



-
R



35
S



T
E



36
E



A
c



37
R



P
L



31




.E
-



39
1



6
8



40
0



2
0



41
i








42




D
B



43




1
L



44




S
K



45




P
S



46




=
1



47




S
Z



41




H
E



49




R
-



50





y



51





y



52





y



53





y



54





y



55





)



56





t



57









58









59









I
a.
o
i
Where:
                                  ni
                                aaaa
                                   rr
                                    n

                              xxxxxx

                               yyyyy

                              zzzzzz
            Is the  User's Identification.
            Is the  User's Account Number.
            Is the  User's Remote Number.
            Is the  User's Region Number or State Code;
            valid values are 1-10, TN,  SC, NE, etc.
            Is the  data  set name of  the tape file of
            input card images.
            Is the  blocksize of the  tape file data  set;
            it must be a multiple of  80.
            Is the  volume serial number of the tape.
                                     Figure 4-4.   Input from Tape-

-------
                                                                          EFFECTIVE:  June 1,  1984
AUTMOH
          TRC
mOGIlAM NAME  CDS KDIT
                                                                     TASK NUMHEH
Saving the optional REJECT File during a  regular Edit run; this  file can then be corrected via WYLBUR.
1
/
/
7
/
/

/


/
/
i
/
*
/
/
/

/


/
*
3
i
R

C
E


E
I


E
4
i
o

D
D


D
"f


O
s
i
u

s
1


1
6

T

E
T
—
T
>Ut


F



1

E

D
•


•
1



1
R


C
9



T
E


A
10

p
—
J

R
11

R


E


D
12
J
1

E
C


S
13
O
N

X
T


1
14
B
T

E



N
IS



C
D



16
(
R


D



U
a
(V\

C



D
18
a
T

D
D
D
D
D
19
a
r

S
S
1
C

10
a
r

I
N
S
B
*
transactions should be










































21
C


p
z
P
-

22
D


T
i
j
(

23
S


n
i
(
R

24
Y



i
N
E

25
P



a
E
C

2E
t



a
W
F

27
M



a

M

21
•



•
K
=

29
•



E
E
F

30
i



R
E
B

31
)



R
P


32
/



0
)
L

33
i



R

R

34
U



s
s
E

)laced immediately after










































35
S



)
p
C

36
E



U
A
L

3)
R



N
C
:

31




1
E
8

39
1



T
-
0

40
D



I
(


the above


















41
r



D
T
B

42




1
R
L

43




S
K
K

44




K

S

45




>
(
1

46





2
2

47





i
E

JCL card.





















41





2
-





49





)
3





50





)
1





51





i
2





52





0





53






)




54






—




55












56












57

—









56

__







   The above two cards should be placed  at the end of the transaction deck.
               Where:
                      iii   Is the  User's  Identification.
                     aaaa   Is the  User's  Account Number .
                       rr   Is the  User's  Remote  Number.
                         n   Is the  User's  Region  Number or State  Code;
                            Valid Values are 1-10,  TN, SC, NE,  etc.
                          Figure 4-5.  Saving  the Reject File.

-------
                                                                      EFFECTIVE:  June  1, 1984
AUTHOR TRC
PIlOCnAM NAME CDS EDIT
TASK NUMDEJl
Printing the optional REJECT file during a regular Edit run.
1
/
/
7
/
7
J
/
2
7
*

/
/
/


/
*
3
i
R

C
E
£
I


E
4
i
O

D
D
D
np


O
5
i
u

s
1
1
ut


F
6

T

E
T
T




1

E

D
•
•
tr



1



1
R
C
an



9



T
E
A
s



10

P


J
R
ac



11

R


E
D
ti



12
J
1

E
C
S
01



13
O
N

X
T
1
i



14
B
T

E

N
ca



IS



C
D

re



18
(
R


D
D
Is



\1
a
M

C

D
s



II
a
T

D
S

he



19
a
r

S
Y
*
u



20
a
r

\
S

Ld



21
C


P
O

t



22
D


T
U

e



23
S


n
T

P



24
Y



-

la



25
P



A
c«



26
/





>d



27
M



D

i



21
•



C

mn



29
•



B

le



10
•



=

di



31
)



B

at



32
/



L

e



33
»



K

Ly



34
U



S

a



35
S



1

ft



36
E



Z

:e



37
R



E

r



31




:

tY



39
1



8

ie



40
D



0

a



41
/





be
—

42






V



43






3



44






JC



45






L



46






c



47






ai



41






d



49










50










51










52










53










54










55










56









57



-





58



—





The above two cards should be  placed at the end of the  transaction deck.
              Where:
                    iii   Is the User's  Identification.
                   aaaa   Is the User's Account Number.
                     rr   Is the User's Remote  Number.
                       n   Is the User's Region  Number or  State Code;
                          Valid Values are 1-10,  TN, SC,  NE,  etc.
                       Figure 4-6.   Printing  the Reject File.

-------
                                                      EFFECTIVE:  June- 1,  1984

           1426 .Mr
Cnii.-iAlli) 7 I Is
1. o:i.i3.5.3 .10 n 176A KAi:iiiiT: IISEI:»KTAKX<: I:I:I'=AO:>
2. Otl.13.53 .11)11 176A $HAS;t'373 KI'AKXCHS STAHTKIl -
.3. (1:1.13.57 JOll 1 76A WCCOO5I * .)<>it KI'AKXCHS KIJW.l)
4. OK. 13. 57 JOll I76A $IIA:;iM95 KI'AF.XC.ir» KIIUKI)
5. II //KPAEXCU5 .Kill (A026(;i)!iYI',;i...
CO.IIUiJO 7 .|i>l not "05' 2/3 in .-ill
co:i,u;:o 7 u.i
9O. O1 14 1 54O OO71 5 OOO
•II. 05 14 IViO 01039. OOD
•17. 05 14 1540 02124 (too
91. 05 14 16(X1 00003 OOO
CnriilAill) 7 sot lenr,tlt"HO
COtiiiAllli 7 s«t tcruliiul wldtli™132
CDIIIIAiJD 7 ch ' " to " in nil nol
Co:iili\:|j) 7 11:;
90. 0514154000715000
91. 0514154001039000
92. 0514154002124000
'13. 0314I6000O0030(»0
CnillAillt 7 ch DO to *c* In nil nol
COIIIIAI:I> 7 llu
90. 0514154000715000
91. 0514154001039000
92. 051 41 54002 1240OO
93. 0514160000003000
i.rm.iAiil) 7 oh 50/611 to 'electrical ocrvlceo* in all nol
1:011: IAHD 7 1 l;i
90. 0514154000715000
91. 0514154001039000
92. 0514154002124000
93. 0514160000003000
COHIIAIIU 7 ch 17/19 to '005' In nil nol
CO!t;Uill> 7 llu
90. 0 M 4 1 540007 1 5000005
91. 0514154001039000005
92. 0514154002124000005
93. 0514160000003000005
O>II;IA:II> 7 col .1
O.I 7 //upucxclS Job (n026c(luyp,inaxc) ,*in|mf. reu 5*
0.2 7 /*n«ite print r37
0.3 7 /*cntl cils5.exe
0.4 7 //eil it exec cilslpt5,type-'dnuiroy,',pario»'05tr'
0.5 7 //c.irHiiln dd *
0.6 7 ...
COIII1AIJI) 7 Us
0.1 //epncxclS Job (a026crlnyp,iuuxc) ,' input n-u 5"
n.2 /*rmitc print r37
H..3 /*cntl Cila5.exe
0.4 //edit cxoc cilointS, ty|x>»'iliiiiiny ,' ,|)nrr!i""05tr*
0.5 //car.lcln dd *
90. 0514154000715000005
91. 0514l5400103't000005
92 . 0 51 4 1 54002 1 24OOOO05
93. 0514160000003000005
CDr.llAIJI' 7 run unit

I. A"/i'.l26<:i)SYI' K;;».3i'i
HUT 12 - CI.AS:; A
12/31 AM AT Hi!: 1.1: 57,
























.ELECTRICAL SERVICES
KLECTItlCAL SERVICKS
ELECTRICAL SERVICES
ELECTRICAL SERVICES


ELECTRICAL SERVICES
ELECTRICAL SERVICES
ELECTRICAL SERVICES
ELECTRICAL SERVICES








'




ELECTRICAL SERVICES
ELliCTKICAI. SERVICES
ELECTRICAL SERVICES
EI.EUTIUOAL SERVICES

13H rs YOUK .101!
                   Figure 4-7.  Sample  WYLBUR Session to
              Convert Retrieval Output  into Input to CDS tdit
                                      -63-

-------
                                                       EFFECTIVE:  June 1, 1984




During the  update cycle,  all  transactions placed  on the  MOD File since  the

last update  cycle are applied to  the  master  file by the  Update Program.  The

update cycle  is usually  scheduled by  the  national  DBG to  run on  Wednesday

nights.



    4.4.2  Update Program Description

    Prior to the Update  Program,  all input transactions from  the MOD  File are

sorted into  the same sequence as the master file.  The output master file from

the previous update  cycle  becomes  the  input master file to the current cycle.

The  update applies  input  transactions to  the master  file  to produce  a new

version of  the master file as output.   There are  three major  logic  paths in

the update depending on the Update Code present on the transaction.

    To add a new  record  to the master  file,  the  update  performs the following

steps:


    1.  The  records  on  the  input master file  are copied to the output
        master file until  an  input master  file record is found  with  a
        record identifier   (Region,  State,  County,   Source,   Point,   and
        Action Numbers)  equal to or  greater than the  record identifier on
        the new transaction.

    2.  If  an  input master  file record  already exists  for  that record
        identifier,  the  input  transaction is  rejected  since  the  update
        cannot perform the  add logic.

    3.  If  an  input master  file  record  does  not  exist  for  that record
        identifier,  the  transaction is formatted  into  an  output master
        file  record.
                                       -64-

-------
                                                       EFFECTIVE:  June 1, 1984




    To change an  existing record on the master  file,  the update  performs  the

following steps:


    1.  The  records  on  the input  master  file  are  copied to  the output
        master  file until  the  record identifier on  the  input  master file
        is  equal  to  or  greater  than the record identifier on the change
        transaction.

    2.  If  there  is  an  input  master  file  record with  the   same record
        identifier as  the input  transaction, the  data on the  transaction
        is  applied to  the input  master  file.   After all  multiple change
        transactions have  been applied  to  the  input  master  file record,
        it  is then placed on the output master file.

    3.  If  there  is  no  input  master  file  record with  the   same record
        identifier as  the  input  transaction,  the change  transaction is
        rejected.  Special  logic  has  been  developed  to  allow  users  to
        create  a  new master file record with  a  Card 3 change transaction
        to  avoid  rejects.


    To delete an  existing record from the master file, the update performs the

following steps:


    1.  The  records  on  the input  master  file  are copied to  the output
        master  file until the  record identifier on the  input  master file
        is  equal  to or  greater  than the record identifier on the delete
        transaction.

    2.  If  there  is no  input master  file  record  with  the   same record
        identifier  as  the  input  transaction,  the  delete  transaction is
        rejected.

    3.  For a  comment  delete,  the  input master  file record which matches
        the record identifier of  the  input transaction  is not copied to
        the output master file.

    4.  For an action delete,  input master  file   records  with  the  same
        Region,  State,  County,  Source.  Point,  and  Action numbers as the
        delete  transaction  are not  copied to the output master  file.

    5.  For an  emission  point  delete,  input master file  records with the
        same Region,  State,  County,  Source,  and  Point numbers  as the
        delete  transaction  are not  copied to the output master  file.
                                      -65-

-------
                                                       EFFECTIVE:   June  1,  1984



    6.   For a  facility delete, input  master file  records  with the  same
        Region,  State,  County,   and  Source  numbers   as  the   delete
        transaction are not copied to the  output master file.


    The Update will reject  input transactions under the following  conditions:


    •   Because of  the master  file  hierarchy,  an action cannot  be added
        to the  master file without  a corresponding  emission  point, nor
        can  an emission  point be added  to the  master file  without  a
        corresponding  source  record.   Comments  cannot  be  added  without
        their corresponding source, point, or action records.

    •   A delete and  a change transaction for the  same  record  identifier
        cannot  be  applied  to  the  master  file during  the  same  update
        cycle.  The change  transaction will be rejected.


    In addition to  applying adds, change, and deletes to the  master file, the

update also  performs  a table  lookup on all  personnel  codes on the  master

file.  No  change  transactions  need  to be  coded  to  change personnel names on

the  CDS  master file.   Whenever a name  associated with a personnel  code  is

changed  by the national DEC,  the personnel name  and  the associated  table for

that  personnel  code  will  be  placed  by  the  update  cycle  onto  the   CDS

masterfile.   This  will be  accomplished for personnel at both source and action

levels.   Refer  to  Section  10.1.2  of  the  CDS  User's  Guide  for  a  full

description of the personnel code processing.

    Regional  users  should  call  the  national  DEC  to add,  change, or  delete

entries on personnel tables.



    4.4.3  Update Scheduling

    The  scheduling  and maintenance of the  update  cycle is the responsibility

of  the  national DEC.   Once a  week,  on Wednesday  night,  the valid transactions

on  the MOD File are applied to  the CDS master file  by the Update  Program.   The
                                      -66-

-------
                                                       EFFECTIVE:  June 1, 1984
update  is  scheduled  for  approximately  9:00  p.m.  EST.   Because  of  this




schedule,  it  is important  for users  to  have all of  their  weekly input ready




for keypunching on or before Tuesday noon.




    If  a  regional  user requests  an additional  update,  a  special  update  run




will be  scheduled.   When holidays  prevent a  Wednesday  night update  cycle or




when a  special  update cycle is scheduled, the national DBG will inform all CDS




users of the change.




    On Thursday mornings  and all mornings following an update cycle, an Update




Report  will be  routed  to  each  region  by  the  DEC.   If  the  report   is  not




available  by  noon,  users  should  verify  that  the  update  cycle  has  run




successfully by examining  the  Update Status  Log described  in  Section 4.4.6,




and  then users should  obtain  their Update Reports  by using the JCL described




in Section 4.4.6 or by contacting the CDS operations contractor, TRC.








    4.4.4  Update Report




    The  Update  Program produces an  Update Report which is stored  on a regional




file.   If  the  user had transactions which were entered into  the  update cycle




normally,  the  national  DBC will run the  Update Report for each user.  However,




if  the  report  is not available  by noon on the  day following an  update,  then




the  user  may  request his  Update  Report  by  submitting  the  Update  Report Job




Control  described  in Figure 4-8.  This  must  be done prior  to the next update




cycle.   As soon as the next update  cycle is  run, the  previous week's  report  is




no  longer  available.   A new report  replaces  the  previous  week's report on the




disk  file.  TRC keeps  copies  of weekly  Update  Reports  on  its files; however,




the  user should keep  his own file  of weekly update  Reports.
                                       -67-

-------
  


-------
                                                       EFFECTIVE:  June 1, 1984




    The Update  Report has  one  print  line  for  each transaction  sent to  the

Update  Program  by the Edit  Program.   Next to each  transaction  on the report,

there is an  Update Action column which  shows  that  the  transaction  was  either

added,  changed,  deleted,  or  rejected  from  the  CDS  master  file.   If  the

transaction was  rejected,  there will also be  an error  message  explaining  why

the transaction could not be added, changed, or deleted.

    All errors appearing  on  the Update Report should be  corrected,  coded,  and

then resubmitted to CDS via the Edit Program.

    A sample Update Report  is shown in Figure 4-9.  The  title,  region number,

and  output  serial  numbers  are recorded  at  the  top  of the  report.  Column

headings are  listed  across the top of the  page.  Update  Action is  located on

the  right  side  of the page with an accompanying message  if the transaction is

rejected.  Update  error  messages are listed in  Table 4-2.   The origin of  the

input transaction  is shown in the far right-hand column.  These  include:


     (blank)             The   transaction  was   entered   by  the   regional
                        office  or  by an  authorized  representative of the
                        region.

    HQ                  The transaction was entered  by  EPA Headquarters.

    GN                  The  transaction  was generated by the  Edit Program
                        for further processing in the Update.

    SC, TN, ME          A  state code is  placed  in  this column if  a state
                        entered the data into  CDS.

    TR, TRC             TRC

    GE, GEO             Geomet

     iii                 Regions may choose  to use  their staff personnel
                        codes.
                                       -69-

-------
                  UPDATE REPORT
                                                        EFFECTIVE:   June  1,  1984
04/09/8?
STATE
CODE
0
34
18
18
IB
IB
IB
IB
111
IB
ia
in
ia
IB
in
IB
18
in
IR
la
la
18
in
ia
ia
IB
Ih
ia
in
1 B
ia
IB
la
IN
IB
in
IB
11
IB
ia
is
IK
16
in
la
in
la
in
CNTY
CODE

56/n
0200
0200
0200
1340
93«li
0340
0340
0340
0340
0340
0340
0340
0340
0400
0400
0400
0620
0620
0620
06?0
0740
0740
0740
1240
1?40
1 210
1240
1240
1240
12)0
Ib40
1540
1540
1540
1540
15)0
I5»0
1540
1510
164Q
1640
1610
1643
1640
1640
1640
SOURCE
CODE
1
"0123
00040
00041
(.0010
000711
0007-)
OOOHl
60009
60009
60079
10079
•»007«J
9001)1
MOO 1)1
00009
00009
09015
moot
UCOU'.'
01)033
°0033
0001 7
6091)1
30017
OP010
00065
00124
60010
"0010
901 12
"0124
oooin
C0018
cooiP
00026
0002H
60001
t-0026
60028
7UOOI
70016
P0030
F0037
IMI045
000(13
0001.7
( r o •> i
EH
PT

4S6
000
000
000
000
000
oco
000
000
000
O'JO
oco
000
000
oco
O'JO
OPO
000
000
ODD
000
000
ouu
O'JQ
090
O'tO
000
030
000
000
000
POO
ouu
ODD
000
QUO
0110
ouo
oco
POO
Of 0
oco
OJO
U"'J
O'.'O
010
oi1 n
ACT
NO

7n
no
00
PO
CO
CO
00
00
00
00
00
00
00
PO
00
CO
PO
PO
PO
CO
00
PD
PO
?0
00
t?0
CO
?0
00
00
00
00
OP
re
00
to
?(l
PO
00
(<0
10
ro
"0
!'0
PO
00
?o
COMPLIANCE DATA SYSTEM
KENTUCKY DATA FOR REGION 4 - ATLANTA
OUTPUT SERIAL 584

PACE 2
CARD UPDT UPDATE ER10R
CODE CARD COLUMNS: CODE ACTION MESSAGE

9
3
3
3
3
3
3
2
3
3
1
3
3
3
3
3
3
2
3
3
3
3
V
3
3
2
3
3
3
3
•t
1
2
3
3
3
?
3
3
2
t
*>
\
3
t
3
j,
',
? 3 4 S 6 7
012 34567890 1234567B901234567B90I234567B901 23456Tfl90123456789
B
e
A2
n
B
B
2048
A2
n
RICHARD n. JOHNSON
B
B
B
B
B
A2
3251
B
B
n
A2
A2
A2
0
0000
B
B
B
B
n
IW). SUPPLY HOUSE
3295
B
B
B
51S1
R
n
5IS1
B
B
n
B
B
I)
•3
0
0
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C

1 = MULTIPLE CHANCE CHIG
CHANGED
CHANGED
CHANGED
CHANGED
CHANCED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANSED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANSEO
CHANGED
CHANGED
CHANGED
CHAN5CO
CHANGED
CHANGED
CHANSED
CHANSiD
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANGED
CHANSED
CHANGED
CHANGED
CHANGED
Figure 4-9.   Sample Update  Report

-------
                                                       EFFECTIVE:  June 1, 1984
                                   TABLE 4-2
                             UPDATE ERROR MESSAGES
Update Error Message
                      Explanation
SOURCE NOT ON FILE
POINT NOT ON FILE
ACT NUM NOT ON FILE
NEW 2 INVALID
Cards 2  through 8  cannot  be added to  the  master file
with an  Update Code  "N"  unless  the  Card  1 has  been
added  as  new  during  this  update  cycle  or during  a
previous  update cycle.   Make  ^sure  that  the  source
exists  on the  master  file;  verify  that  the  correct
State, County,  and  Source  Number is being  used  on the
transaction.

Cards 6  through 8  cannot  be added to  the  master file
with  an  Update   Code   "N"   unless    there   is   a
corresponding  Card  5  on the  master  file.   Make  sure
that the  emission point is being added as new  or has
already  been added as  new when  emission comment  or
action information is being added to the master file.

An action comment Card 8 cannot be added  to the• master
file  unless  a  corresponding action  (Card  7)  already
exists on the master file.

Card 2  can be  added to the  master file  as new  only
during the same update cycle as the Card 1 is added as
new.  Once the  source exists on the  master  file, use
an  Update Code  "C"  to change  the  data elements  found
on the Card 2.
DUPLICATE TRANS
NOT ON FILE
If  two  or  more  transaction  with  the  same  Region,
State, County,  Source, Point, and  Action numbers have
an Update  Code  "N",  the first transaction  is  added to
the   master  file   and  the  second   and  subsequent
transactions are rejected with this message.   A change
transaction  following  is   a new  transaction  for the
same   Record   ID   is   rejected.    Duplicate   delete
transactions are also rejected.

The  update  cannot   apply   a change  transaction  or  a
delete transaction against  a non-existent  master file
record.   Verify the State,  County,  Source, Point, and
Action numbers being used on the transaction.
                                      -71-

-------
                                                       EFFECTIVE:  June 1, 1984
                             TABLE 4-2 (Continued)

                             UPDATE ERROR MESSAGES
Update Error Message
                      Explanation
ALREADY ON MF
98 ACTIONS ON MF
&(AMPERSAND)
S2 REJ
ATPE  WRONG FOR PLTY
A  transaction  with an Update Code "N"  cannot  be added
to  the  master file  if a  master  file record  already
exists  with the  same Region,  State,  County,  Source,
Point, and  Action  numbers.   Also a new comment  cannot
be  added  if a comment with  the  same  record identifier
and line number already exists on the master file.

When the next sequential action number  is  not  known on
the  master file,  action  number 99  can be  coded;  the
update  will  convert  the   99   to   the  next   highest
sequential  action  number.    To prevent  the master file
from going  out of  sequence,  no  action number over 98
will be added to the master  file.

When  an ampersand appears  in the  Error Message  column
of  the  Update  Report, it  indicates  the presence  of a
multiple  change  transaction  to  the  master file.  This
is  not  an  error  message;   it  is only  a  warning that
multiple  changes  have been  applied  to the master file
in  chronological order.

If  one  or  more   sets  of   pollutant  compliance  data
cannot  be added to  the master  file  because there are
already  10 sets of  pollutant compliance  data  on the
master  file,  a  reject message  is  issued  for  each of
the rejected pollutants.   The Pollutant  Code  together
with  the  letters  "REJ" is  printed in the  Error Message
column.   Since the Card 3  has  room  for three  sets of
pollutant   compliance  data,  up  to   three  different
reject messages may  exist on one line.

On a  change transaction, Penalty amount can be  entered
only  for  certain action types such as Zl,  Z2, Z3, etc.
                                       -72-

-------
                                                       EFFECTIVE:  June 1, 1984




    4.4.5  Update Report Messages

    On the Update Report,  the  Update. Action column indicates  the action taken

by  the  Update  Program on each  transaction passed by  the edit.   The normal

Update Action message is ADDED, CHANGED, or DELETED.  An  ampersand  next to the

word  CHANGED indicates  that the  update has applied  multiple  changes  to the

same master file record in chronological order.

    The  word REJECT  in  the  Update  Action column  indicates that  the Update

Program could not perform the  appropriate add,  change,  or  delete indicated by

the  transaction's  Update  Code.   For each  rejected  transaction,  there  is  a

diagnostic  error message  printed  out.   Table  4-2 lists  all  of   the  errors

identified  by  the  update.  An explanation of  the corrective  procedures for

each update error message  is also given  in this table.



    4.4.6  Update Status Log

    The  Update  Program  produces  an Update  Status Log  which  shows  the most

recent  successful  run of  the   update  cycle.   This log  is  available  to  those

users having  access  to a  WYLBUR  computer  terminal.   This Update Log  shows the

date, the time,  and  the  output serial number of  the  most recent update cycle.

The  log  shows which regions participated  in the  update.  In addition,  it also

shows  the  number  of  transactions  input   to  the  update  and  the number  of

transactions  accepted and  rejected  by the update  for each region.

    To obtain the log, perform  the  following steps:


    1.   Follow  the  standard NCC sign-on procedures by  typing in the  user
         account, initials,  kevword,  and  terminal  identifier.
                                       -73-

-------
                                                       EFFECTIVE:   June 1,  1984
    2.   As soon as WYLBUR  gives the prompt, COMMAND?,  type  in the
        following and then hit the carriage return:

              USE $EXCA026.CDS.SYSOUT
              LIST

    3.   Figure  4-10  shows  the contents  of the   log  produced  by
        following the above steps.
    4.4.7  Update Report Job Control Language

    The user  may wish  to request  his  region's Update Report  for  each update

cycle  for  which  the region  had  input  data.   To execute  the program  which

produces the  Update  Report,  use the JCL shown in Figure 4-10.  This JCL should

be  submitted  immediately  after  each  update  cycle  for  which the  user  had

input.  Normally,  the  user  should submit  this JCL on  Thursday morning and on

mornings following special update cycles.

    If  the  user does not  submit  this  JCL  prior to the next  update cycle, the

information from the  update  run is overlaid by  the next  update cycle's Update

Report.

    The Update Report provides  the  only audit  trail of  all transactions placed

on  the CDS  master file; therefore, it is important to keep this report on file

so  that errors can be researched and corrected.



    4.4.8  Critical  Data Elements  Report

    To aid  the  CDS  user in the update  verification  process, CDS produces the

Critical  Data  Element  Report  during   each   update  cycle.    This  report  is

designed  to highlight significant  changes  in  a few data elements and  contains

one line  of data for each source that has had  a  critical  transaction applied

to  it.   Data elements  included  in  the report are  Source  Name,  Air Program
                                       -74-

-------
                                                                                                  EFFECTIVE:   Junl
                                                                                                              1984
PLEASE  TYPEL  YOJR TERMINAL  1DENTIFIFRF
-NMNIJ-PPP-
PLEASE  LOT-  IN!  1 L'MEP« 1 ', MCC (CR )
P KHIt
IHM5 IS ON  LIVE.
FNTEH TS3  OR  03S
CBSJCR)
OBS WYLHUR  b.A  AT EPA TERMINAL  TTYOF5

USER ID?  CDS
PASSWORD  (ClIKRt/NEUI) 7PASSKORDGGGGGGGG
ACCTUJD?  A02GCDSYT
KIM/BOX?  CDS.J
                                          HH:MM:SS  MM/DD/YY
  C2/26/B2:  LISTING ALL fJCC-IP.M  ME
  u3/i2/>i£:  COOL OPTION NOT  SUPPORTED UNDER OPS  WYLBUR
  03/15/82:  WYLUIIK DOCUMENTATION UPDATED

ClM.EPA:nS.AO?6. ClWIK NOT .'fi CATLG  2 LEVELS OK
CN.EPACDS.AO?r:-opT  PRIMT-LIN^S FOR  REGION it!= 00012

        RIKORT  PRlf!T-l. INKS FOR  ALL  REGUS= 0001191   RECf'RfS IN3l)T =

    UFDAIi" FP'ISHLI AT ?'. 1"
                       RECORPS  INPUT =

                       RECOPPS  IN3JT =

                       RECORPS  INPUT =

                       RECORPS  IN=JT =

                       RECORPS  INPUT =

                       RECORDS  IN»UT =

                       RCCORPS  INPUT =

                       RECORDS  INPUT =

                       RETORTS  INPUT =

                       PECORFS  INPUT =
30*71
00253
00537
00664
01005
P0?21
D0701
00000
00597
nOC42
03011^1
ACCEPTED
ACCEPTED
ACCEPTED
ACCEPTED
ACCEPTED
ACCEPTED
ACCF.PTEO
ACCEPTEP
ACCEPTED
ACTEPTEP
ACCEPTED
= 00465
= 00251
= 00531
= 00639
= 00966
= 00215
= 00467
= OOOOC
= 005 '31
= 00037
= 0001162
REJECTED =
REJECTEO =
REJECTED =
REJECTED =
REJECTED =
REJECTED =
REJECTED =
REJECTED =
REJECTED =
REJECTED =
REJECTED =
oooce
00002
00006
00025
00039
00006
OD234
OCOOO
00006
00005
0000329
                                 Figure 4-10.   Contents of  Update  Status Log.

-------
                                                       EFFECTIVE:   June 1,  1984
Code,  Source  Compliance   Status,   Source  Classification,   Source   Emission

Category, Action Type,  and Date Scheduled.  The origin  of  each transaction is

presented at the  end of each line.  Figure  4-11  is an  example of a  Critical

Data Element Report.



4.5 Keeping an Entry Log

    In order to ensure that all information  pertinent  to stationary sources of

air pollution  is  entered into CDS, it is  recommended that each CDS Coordinator

keep a log of that  information.  A log should contain:


    1)  A  description  of   the  information  (data  tape, printed   report,
        corrections  from a  previous update,  etc.).

    2)  The  origin of the  information  (contractor,  state system,  date of
        previous update, inspections, etc.).

    3)  Date received by CDS Coordinator.

    4)  Date prepared for  entry into CDS.

    5)  Date submitted  for entry into CDS.

    6)  Date edit  completed and reviewed.

    7)  Total number of  transactions input.

    3)  Number of  transactions accepted.

     9)  Number of  transactions generated.

    10)  Total number of transactions passed  to  update.

    11)  Date of quality assurance  (check  of  update  report).

    12)  Results of quality assurance  (number of errors).

        Note:  Correction   of  errors  found  in  quality assurance check
               should  reenter  log  as new  information.

 Figure  4-12  shows  a  sample  of  an  Entry Log  Format containing  the above

 information.
                                       -76-

-------
                                                                                                        EFFECTIVE:  June 1,  1984
                                                    CRITICAL DATA ELFMENT UPORT
    09/01/h2                                            cOIPLUNCE DMA SYSTEM                                            PA3E    1
                                           PENNSYLVANIA DATA FOR *EG|9^J  3 - "HILADELPHIA
                                                         OUTPUT SE31AL    f>05

STTE CVTY SKCf                                             APCO SCMS CL»S  SECT SVIO APTE    OTAC                        SUUIITiO JY
CODE COD: MRR   OLD SOURCE NAME       MEW  SOURCE  NAME       ONOMOM010NC-4  DEL CMG                         RG  ST  HJ OF


  39 0260 00037 FREEI'ORT  TERMINALS                              0 1  U< A2                                               •         SY

  39 0560 OOC10 CRUCIBLE  I NC                                    59                           *                          •         GY

  39 0560 00115 FABUAR KlYUS  EXCAVAT  FABIAN  LOU]S  EXCAVAt      0 4  UK 3                                                •         CM

  39 1520 0003i TUETCCRS-NEASE CHEM   RUET6ERS-MEASE CHEH                                                                •

  39 1460 OOOS1 LUDLOU FLEX PACK      GRAPHIC PACKAGING CO                                                               •

  39 1S60 00073 UTEIH LABORATORIES                              03                                                               CM

  39 2363 00313 PE - CHESTER                                                              •                              •

  39 2943 1016) MOTION CONTROL 1ND    MOTION  CONTROL IND                                                                 •

  39 3220 OOC60 MARSOLINO CON3TR CO                             0 1  UK O                                               •         GM

  39 4?<)3 00043 COLUMBIA  GAS  TRANS                              0 4  U< »1                                               •         CM

  39 1243 OOG4S COLUMfllA  GAS  TRAMS                              0 1  U< 42                                               •         GM

  39 4700 00110 HIGHUAY MATERIALS HP                   '         9 3                                                               G1

  39 4B4) 60U01 INMETCO                                         1 2                                                               3M

  39 5223 OOS7& UARLTTTA  A &  SONS                                                             •                          •

  39 5240 OUOhi ATLANTIC  RICHFIELD                                                            •

  39 5b«,] OOC21 GREENVILLE TBSNOV EM                            9 5                                                              CM

  39 5763 OOOn STANDARD  StfEL                                                            •                              •

  39 6J03 00045 LCHIGH VALLEY COOP    ATLANTIC  PROCESSING                                                                •

  39 630) OODb3 FLAGG STANLEY G 1 CO                                                      •                              •

  39 M63 02013 pRANKLIN  SMELTING                                                         •                              •

  39 8360 OOC30 CAHBO^E CQ=


-------
                                              EFFECTIVE:
 June 1, 1984

Line Number
                                                         Data
                                                         Description
                                                         Data
                                                         Source
                                                         Date Received
                                                              by
                                                         CDS Coordinator
                                                         Date
                                                         Submitted
                                                         Date Edit
                                                         Completed
                                                         Date Edit
                                                         Reviewed
                                                         Number of
                                                         Transactions
                                                         Input
                                                         Number of
                                                         Transactions
                                                         Accepted
                                                         Number of Trans-
                                                         actions Generated
                                                         Total Transactions
                                                         to Update
                                                         Date QA Check
                                                         of Update
                                                         Report
                                                         Results
                                                         (No. of Errors)
Figure 4-12:  Sample Data Entry Log.

                             -78-
                                                         Error Re-entry
                                                         Line Number

-------
                                                       EFFECTIVE:   June 1, 1984.




5.0 ENTERING DATA - REQUIREMENTS

5.1 Adding New Sources

    Card Type 1 with  an Update Code "N" is  used to add a new  facility  to the

master  file.   A  facility  in CDS  represents  all  the  site,  emission,  and

enforcement  action information  for one  particular  source   or plant.   If  a

source  is subject  to  several  air  programs,  such  as SIP,  NSPS,  and  NSR,  a

separate source number is assigned for each affected air program.

    To  establish a  new  facility  on  the  master  file, perform the  following

steps:


    1.  Request  a  Quick  Look  Report with  the CDS  Retrieval  Package  to
        verfity  that  the  facility being  added  is not  already  on  the
        master file.

    2.  Select  a   County  Code/Source  Number  combination  which   will
        identify  the  facility  by  a  unique  number.   The  NEDS  source
        numbering  convention  may   be  used  when  adding  a  new  source.
        Otherwise,  assign  the  next  highest  sequential  Source   Number
        within  the county.   A  County  Code  name  corresponding  to  the
        County  Code  number  is generated  by  CDS  when  a new  card  1  is
        submitted.

    3.  Code  columns  1-19  (Region,  State,  County,  Source Number,  Point
        Action  Number,  and Card Type) and the Update  Code  "N" in column
        80.  Region,  State, County, and Source Number together  identify a
        unique facility in the CDS.

    4.  Code  Source  Name,  columns  27-46.   If  additional data  elements
        unique  to  card type  1 (Appendix  A)  are  available,  they  should
        also be entered at this time.

    '5.  Additional  card  types with  the  same  source  identifier  may  be
        added for  this  update cycle or for  a  subsequent update cycle  as
        new transactions.


    5.1.1  Multiple Air Programs

    When  entering  data  for  a  facility  which  is  subject  to  multiple  air

programs,  the source must  be  entered once for  each air  program  that applies.
                                      -79-

-------
                                                       EFFECTIVE:   June 1, 1984




For  proper  identification,  follow  the  CDS  Coding  Convention  for  Source

Number/Air   Program  Code  source   numbering  (Sections  5.4.6).    For  each

applicable air  program code,  be  sure to  enter the Air  Program  Code  on card

type 2  and  follow  the rules  set  forth in Section  5.2,  Specific Air Programs

and Source or Industry Types.  Also, check sections  in  5.1.2  - Identifying the

Critical Sources for CDS Major 'Sources and Significant Violators.

    Following is a  list of the air programs reported in CDS:


    SIP       State Implementation Plan

    ESECA     Energy  Supply and  Environmental Coordination  Act   of  1974
              superceded  by FUA  (1978),  Power Plant and Industrial Fuel
              Use Act

    PSD       Prevention of Significant Deterioration

    NSR       New Source Review

    NESHAP    National Emission Standards for Hazardous Air Pollutants

    NSPS      New Source Performance Standards



    5.1.2  Identifying the Critical Sources for CDS

    5.1.2.1  Major  Sources

    Major  sources  defined in CDS per the Alabama Power decision  as being Class

Al  are:   any stationary source whose actual  emissions  or potential controlled

emissions  while operating at design capacity exceed 100 tons per year  for any

regulated  pollutant.   Class  A2  sources  are:   any  stationary   source whose

actual   emissions   are   less   than   100  tons   per   year  but  whose  potential

uncontrolled emissions exceed  100 tons per year for  any regulated pollutant.
                                       -80-

-------
                                                       EFFECTIVE:  June 1, 1984
    5.1.2.2  Significant Violators

    The following paragraphs  are  extracted from guidance sent  to all regional

data managers in 1982 concerning the definition of a "significant violator."

    "One of the objectives of the Administrator's Accountability  System for FY

1982 is that  resources  be used to address significant air violators and return

them to compliance.   This is designed to ensure that resources  are  used in the

most environmentally beneficial manner.   The  purpose of  this guidance  is to

assist regional offices and states in determining what the  agency considers to

be a significant violator.

    In  determining   whether  a  violation  is  significant,   the nature  of  the

pollutant  should  be considered,  as  well  as the magnitude  and duration of the

violation  and  the  population  exposed.    While  no  rigid  formula  need  be

followed, the following considerations should be kept in mind.


    1.  A  violation of  a hazardous  air  pollutant standard  resulting in
        emissions  above  the   standard   should  normally   be  considered
        significant  unless  the  magnitude  and  duration of  the violation
        are minimal  and the violation nonrecurring.

    2.  A  source  in violation  of a  State Implementation  Plan should be
        considered  significant  if the source is of sufficient  size and is
        located so  as  to impact a nonattainment  area.   Sources above 250
        tons  per  year  emission potential  as defined  in  the Alabama Power
        case  should be  considered  significant  violators  unless  the
        magnitude  and  duration  of   the  violation  are minimal   and the
        violation generally nonrecurring.   (To  the extent  that available
        data  do not permit  easy identification  of sources  in excess of
        250  tons/year potential,  sources  with more  than  100 tons/year
        actual  emissions  can be  used as  a reasonable surrogate.)  Other
        sources  in  nonattainment  areas  should  also   be  included  if the
        amount  of excess emissions  is considered jointly  by the regional-
        office  and  state  as having  an  important  impact on the continued
        nonattainment of  the area.
                                      -81-

-------
                                                       EFFECTIVE:   June  1,  1984
    3.   Sources in attainment areas and not  impacting  nonattainment  areas
        would not-  normally be considered significant because of  the lack
        of direct  health  impact.   While  states,  appropriately,  should
        take  action  to resolve  such  violations, EPA  will  not give them
        high priority consideration.

    4.   Sources in violation of new  source  requirements,  including NSPS
        and PSD/NSR permitting  requirements,  should also be considered to
        be significant violators unless the magnitude and duration  of the
        violation are minimal.
    As  provided  for  in  the  agency's  new accountability  system,  regional

offices should meet with  each  of their states to  jointly  prepare  an inventory

of known  significant  violators.   States should be encouraged  to take the lead

with respect  to  as much of the  universe  as possible.   Wherever possible,  EPA

should use  its  resources to supplement those of  the state rather than to take

the lead on cases itself.  This  technical assistance can be either in the form

of direct case  assistance  (if  requested)  or  through sponsoring  of technical

workshops and other program building/supporting activities.   EPA should assume

the lead  only where a state cannot or will not take the lead, despite whatever

assistance EPA can provide."1


5.2 Specific Air Programs and  Source or Industry Types

    5.2.1  SIP Sources

    The attainment and maintenance of  national  ambient air  quality standards

is  primarily the  responsibility of each  state  pollution  control agency,  and
 'Bennett,   Kathleen;   "EPA  Accountability   System   -  ORNR   Policy  Guidance,"
 12-29-81.
                                       -82-

-------
                                                       EFFECTIVE:   June 1, 1984




each state must have an adequate State Implementation Plan  (SIP)  for attaining

these standards on  a timetable acceptable to the U.S.  Environmental Protection

Agency (EPA).

    Each  approved  SIP requires  the  state to maintain a  complete  inventory of

all  major  and selected  minor  stationary  sources of   air  pollution.   This

inventory must include the following data:


    1.  Facilities that have permits to construct and permits to operate.

    2.  Facilities  that  are  affected by  existing  SIP regulations  or by
        proposed SIP regulations.

    3.  Facilities   that   impact   nonattainment  standards.  New   Source
        Review,  Prevention of  Significant Deterioration  (PSD),  National
        Emissions Standards  for  Hazardous Air  Pollutants  (NESHAP),  New
        Source  Performance   Standards   (NSPS),  and   other  enforcement
        programs.

    4.  Legal  steps  which  have  been  made  to  bring  a  non-compliant
        facility into compliance.

    5.  Enforcement  actions  which  must  be  taken  for  facilities  on  a
        court-ordered compliance schedule.

    6.  The  compliance category  each source  fits in as  a result  of  the
        state's most recent inspection.


    To code  SIP  sources  in CDS, after assigning  the appropriate  Region, State

and County codes and building  the  Source  number from the air program  code and

the  NEDS  Source number  if it  is  available,  follow  the  rules  found  below in

Section 5.2.2,  Data  to  be  Tracked  for  All  Sources,  to  enter   the  complete

information  for the  source.
                                      -83-

-------
                                                       EFFECTIVE:  June 1, 1984
    5.2.2  Data to be Tracked for All Sources

    The  following  list represents  the  recommended  minimum data  requirements

for all  SIP  sources  with potential uncontrolled emissions greater than 100 TPY

(i.e..  Class  Al   and  A2),  and  all NESHAP  and  new  source  program-subject

facilities  which   have  been  entered into  CDS.   Each  data element  should be

reviewed periodically to ensure completeness and accuracy.
            Data Element
               Remarks
    1. Source Name
    2. City
     3.  Zip  Code
     4.  Air  Program Code
Misspellings   should    be    corrected.
Abbreviations  must be  self-explanatory
and  consistent.   Name  changes must  be
accompanied    by    a    comment   record
indicating     the      former     name.
Multi-plant   corporations   should  have
the  same  corporate name  followed by  a
plant  name,   e.g.,  USS-Clairton.   The
naming  convention  documented  in  the
User's Guide  Data  Dictionary  should be
followed.

If no  city name  is available,  the name
of  the post  box  area  should  be used.
City   names   must   be   spelled   and
abbreviated  consistently.    If  a plant
is located  in a  specially named  section
of a  city,  the city name should  be used
whenever possible.

A zip code  of the actual plant location
should  be  available  from  a  zip code
directory.

This   code   is  used   only   for  those
portions   of  a    facility   which  are
subject    to    that     air     program's
requirements.    Accidental   changes  or
misinterpretations  of  Air  Program Code
can  allow  a  source  to  disappear from
important management reports.
                                       -84-

-------
                                                       EFFECTIVE:   June  1,  1984
            Data Element
               Remarks
    5.  SIC Code
    6.  Source Classification
    7.  Loading Derivation
    8.  Source Compliance Status
    9. Enforcement Actions
   10. Enforcement Dates
It is often  difficult to  determine  the
principal  industrial  activity or output
for  a  given  facility.    Every  effort
must be  made to  research  the principal
industrial activity or output for those
sources which have blanks in this field.

Categories   must   represent  actual   or
potential  controlled  emissions  on  the
basis  of  maximum operating  rates  per
the Alabama Power decision definition.

Indicates   the    method   of   emissions
estimation  (potential or   actual)  used
to determine the  source  classification
code above (only for Class Al sources).

This     must    represent     worst-case
compliance   of    any   point  within   a
source.   It  must  be  constantly updated
for    each    change    in    federally
enforceable  standards.   Order of worst-
case to  best-case is  SCMS 1-6-0-7-5-4-
3-2-8-9.

Figure   5-1   shows    each  enforcement
action  which  should  be  entered  into
CDS.  This  table  is  updated annually in
SSCD guidance materials to the regions.

Both  Date Scheduled  and  Date  Achieved
are  critical to  the  accurate  tracking
of enforcement actions.
    The  above  data  elements  represent  only  10  percent  of  the  total  data

elements  available  in  CDS.    The  first  seven are  relatively static  fields.

Once  they have been  entered  correctly  on  the  CDS  data base,  they are  not

likely  to change  frequently.   The  last three are  dynamic, likely  to  change

frequently,   especially  for   sources   out  of   compliance   with   emission

limitations.   If  users make an annual  effort to verify the  accuracy  of  the
                                      -85-

-------
                                                       EFFECTIVE:   June 1,  1984
                                                               Source of Action
                   Action Description
EPA INSPECTION
EPA SOURCE TEST CONDUCTED
OWNER/OPERATOR-CONDUCTED SOURCE TEST
NESHAP WAIVER OF COMPLIANCE ISSUED
EPA PRE-NOV LETTER SENT
EPA NOV ISSUED
NOTICE OF NONCOMPLIANCE (SECTION 120)
EPA 113(A) ORDER ISSUED
113(D) DELAYED COMPL. ORDER APPROVED/ISSUED BY EPA
113(D) (4) INNOV. TECH. ORDER APPROVED/ISSUED BY EPA
113(D) (5) COAL CONV. ORDER APPROVED/ISSUED BY EPA
1ST 119 SMELTER ORDER APPROVED/ISSUED BY EPA
EPA CIVIL ACTION
EPA CRIMINAL ACTION
FEDERAL COURT ORDER  ISSUED
EPA CIVIL PENALTY ASSESSED
EPA NONCOMPLIANCE PENALTY ASSESSED
E>A PSD APPLICABILITY DETERMINATION
EPA PSD APPLICATION  COMPLETE
EPA PSD PERMIT ISSUED
NEW SOURCE COMMENCE  CONSTRUCTION
NEW SOURCE START-UP
STATE INSPECTION
STATE SOURCE TEST CONDUCTED
STATE NOV ISSUED
STATE ADMINISTRATIVE ORDER ISSUED
STATE CIVIL ACTION
STATE CRIMINAL ACTION
STATE COURT ORDER ISSUED
STATE CIVIL PENALTY  ASSESSED
STATE NONCOMPLIANCE  PENALTY ASSESSED
STATE PSD APPLICABILITY DETERMINATION
STATE PSD APPLICATION COMPLETE
STATE PSD PERMIT  ISSUED
OFFSET APPLICABILITY DETERMINATION
OFFSET PERMIT  ISSUED
EPA

 X
 X

 X
 X
 X
 X
 X
 X
 X
 X
 X
 X
 X
 X
 X
 X
 X
 X
 X
 X
 X
STATE
  X
  X
  X
  X
  X
  X
  X
  X
  X
  X
  X
  X
  X
  X
  X
  X
                    Figure 5-1.  Enforcement Actions Required
                                       -86-

-------
                                                       EFFECTIVE:  June 1, 1984











first seven data elements for each source within their jurisdiction  and make a




quarterly  effort  to update  the last  three  data  elements,  the CDS  data base




will be more usable to states, regions, and headquarters.




    Data  elements other  than  those  described  above may  be critical  to the




internal management needs  of a specific region  or a specific  state;  however,




these  other  data elements  need  not  be  included  in  minimum national data




standards which are designed  to maintain the usefulness of  the  data base with




a minimal amount of data entry effort.




    In addition to  the above stated minimum  data  requirements  for CDS,  it is




recommended  that  the  State  Registration  Number  also be entered  whenever




possible.  The State Registration Number is an alphanumeric  identifier used by




the state to identify a facility.




    The above minimum national standards may be  augmented by regional or state




requirements  in order  to meet specific management objectives.  By entering the




above  process level  data  for selected  sources,   the  usefulness of  the  CDS




system will be maintained with a minimal amount  of data entry effort.








    5.2.3  Data to be Tracked for Selected Sources




    The  previous  section  described  the data  elements  which are  required for




all CDS  sources,  regardless of industry or compliance status.  A great deal of




the  system's  capabilities  have been designed  to  meet  the  needs of  tracking




special  industries,  special  air  program requirements,  and  special compliance




situations.   As  a general  rule, the  minimum data  requirements  for  selected




sources  is  greater than  for  all  sources.   The  following list of  selected




sources  is  accompanied by the  recommended  data  requirements of  these sources
                                      -37-

-------
                                                       EFFECTIVE:  June 1, 1984
in  addition to  the  previously mentioned  data elements.   Both the  list  of

selected  sources and the data requirements for  these  sources is  subject  to

guidance updates necessitated by program planning and regulation changes.
      Selected Source Category

    SIGNIFICANT VIOLATORS as
    defined in the Bennett
    memorandum of 12/29/81
    titled "EPA Accountability
    System - OANR Policy
    Guidance"
         Regional CDS Data
    Violating Class Al  SIP
    sources, NESHAP,  and
    NSPS
     Selected priority indus-
     tries  regardless  of
     compliance.
     New sources,  e.g.,  NSPS,
     PSD,  NSR
For each violating emission point enter:
Compliance Status (CMST)
Point-specific Enforcement Action
Process Description (PROS)
Pollutant Code (PLUT)
SIP Code (if on or negotiating a
compliance schedule)

At the source level in addition to the
data elements already mentioned, enter:
Pollutant Air Quality Control
Indicator (PAQC)
Pollutant Compliance (PCMS)
Pollutant (PLLT)

At the source level enter:
Pollutant Air Quality (PAQC)
Control Indicator
Pollutant Compliance (PCMS)
Pollutant (PLLT)
SIP Code (if on or negotiating a
compliance schedule)
Air Program Status  (APST)

All actions defined  in  the 8/2/83 memo
on the CDS National Action Conversion
Program.    Consult   the    latest   EPA
guidance for  a  current list of priority
industries  such as  power plants, steel
mills, smelters, etc.

Emission point data  should be entered
for the same data elements as for
significant   violators,   if   emission
points  have  differing  start-up  dates.
In  addition.  Air Program Status  (APST),
State  Regulation (SREG),  and Procedural
Compliance  (CMS2) should  be  entered.
                                       -88-

-------
                                                       EFFECTIVE:   June 1,  1984
      Selected Source  Category

    Commercial boilers,  insti-
    tutional boilers,  and coal-
    fired boilers for  indus-
    tries other than power
    plants (SIC 4911)

    VOC sources, sources
    emitting volatile
    organic compounds
         Regional CDS Data
The SCC Code and the Capacity Code
(heat input capacity in MMBtu's) should
be entered.
VOC sources are of primary importance to
the EPA.  It is important to have at a
minimum  a complete  inventory  of  Class
Al requested VOC sources.

Source level data should be entered
for the same data elements as for
violating sources.
5.3 Maintaining Data

    5.3.1  Changing Data on the CDS Masterfile

    Once a  record has  been  added to  the CDS Masterfile by  the  update cycle,

data on  the master  file record can be  changed  in subsequent update  cycles  by

using input transactions with an Update Code "C".

    During a given  update  cycle,  transactions with the  same  record identifier

(Region,  State,   County,  Source,  Point,  Action  Numbers  and  Card  Type)  are

applied  in  Update Code  order.   The Update Program  processes deletes  first,

then adds,  and finally  changes.   The  update will reject a  change transaction

if a delete  is being applied  for the  same card  type  during the  same update

cycle.    The  update will process  multiple changes for an existing master file

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 master file.
                                      -89-

-------
                                                       EFFECTIVE:  June 1, 1984
    Card columns  1-19, the  source  identification and card type  code,  must  be

coded when preparing a change transaction.  However, the  data  elements Region,

State, County,  Source, Point  Number and Action Number in  columns  1-18 cannot

be  changed  by processing  as  a  change  transaction.    If  transactions  with

incorrect  State,  County,  Source,  Point or Action  Numbers  have  been added  to

the  CDS  master  file,  those  records  in  error  must  be  deleted  and  the

corrections  reentered  with  an Update Code "N".  When  any of the data elements

in columns 20-79 need to be changed, only the data  element  that needs changing

is coded on the input coding sheet.

    The following steps should be performed for a change transaction:


    1.  Request a  Source  Data or Quick  Look  Report for  that  facility to
        determine what data values exist on the master file.

    2.  Decide what  data  elements need  to be changed and decide what card
        type should be used.

    3.  Code columns 1-19 on a coding sheet.  Code  a "C"  in column 80.

    4.  Code  only those  data  elements  which  need  changing.   The  Update
        Program will  change only those  data  elements  that  are entered on
        the  card;  other  data  elements  on the  master file  will  not be
        changed.

    5.  Have  coding  sheets keypunched  and  submit  punchcards  to the CDS
        Edit Program.

    6.  Use  a  change transaction  (not a  delete  transaction)  to remove one
        or more  data  elements from a  master file  record.   Data elements
        in columns  20 through 70 of any card type can be  blanked  out by
        placing one  or more asterisks  (*) in the data element  which  is to
        be eliminated.   An asterisk will  remove  only  the data element to
        be blanked out and will  not change  any other data element on the
        master file  record  for  that   card  type.   On  the  card  7,  an
        asterisk  on Date Scheduled  or  on Date Achieved will zero-fill  the
        data element  since  these  data elements  cannot  be  blanked out.  An
        asterisk  cannot  be  used  to   change  any  data   elements  in  card
        columns  1  through 18.   If a   record  with  an  incorrect  State,
                                       -90-

-------
                                                       EFFECTIVE:   June  1,  1984
        County,  Source Number, Point  or Action Number has been placed  on
        the  master  file,  the  incorrect  data must  be  deleted  with  an
        Update Code "D" and  the  corrected card  reentered with an  Update
        Code "N".

        Since asterisks are  used on  change transactions  to  blank out  a
        data element, asterisks may not be used  on new  transactions.   A
        warning message  (*ASTERISKS  FOR CHANGES)  is  issued  by the  Edit
        Program if asterisks are  found on any transaction with an  Update
        Code  "N".   Asterisks  are not  placed  on the  master  file  in  the
        update cycle.

    7.   An  Update  Code  "C"  should  be  used  for  adding  or  changing
        pollutant  data  on a card 3.    A delete . transaction  is not valid
        for a card  3.  If a user wishes  to delete  all  references to  a
        pollutant   on the  master  file, he  should  code  the  appropriate
        pollutant  code  followed   immediately  by  a  "D"  in the  Pollutant
        Delete Flag on the card 3.

        If  a  user  wishes  to  blank  out  one  or  more  data  elements
        associated with a  pollutant on a card 3, he  should place  one  or
        more asterisks(*)  in the field to be blanked out.   Because  data
        is  stored  on the  master  file  by  Pollutant Code  on  a  card  3,
        changes to Pollutant Compliance Status or other pollutant related
        fields must always be accompanied by a Pollutant Code.

        Users may  make changes   to  the Pollutant  Compliance  Status  of
        several pollutants regardless  of the order in which this  data was
        originally  entered;  all  changes  and additions  are  applied  by
        pollutant.
    5.3.1.1  Sample Completed Coding Sheet for Change Transactions

    Once a  facility has  been entered as  new on  the  CDS master  file,  change

transactions can be entered  for  records  existing on the  master  file.   Columns

1 through  19 must  be  the same on  the  change transaction as they were  on the

new transaction already  on the master file;  column  80  must  be a "C" for  each

change transaction.

    Figure 5-3 is a sample coding sheet  used  to change some of  the  data input

as  new in  Figure  5-2.   It  is  also used  to add new  records  which were  not

created in Figure 5-2.
                                      -91-

-------
                                                                                                                 EFFECTIVE:. June  1,
       lil-.IOII. si  I  COHIIIV  ISWIHCE NUMBER
 il-.IOII. si I
 ZTprmllL
 04|1 8{1
          CARU COOL
           0
       0
      DI-Jso
      TlTp]
      2IOJ9
                     09000
                     AgCR
          8
                               u
                          cnr CODE
                         ti 24 25
                         2£ ZL
                   COMPLIANCE   DATA SYSTEM  CODING  SHEET
                                                  SOURCE NAME
              D
                              n
      N
                          i?
          ii
                                  35
                                  K
                                          JO
                                            ^
                                                                     45
                                                                       m
                                                                                           STREET ADDRESS
                                                        49™ 511
                                                        JR@
                                                                 HUT
                                                                                              57
                                                                                                 £9 &2Jki 52 &j e S fit
                               CUT NAME
                                                     ZIP
                                             BITS
                                             JTIJ/
                                                       IM
                                                        STATE REGISTRATION         NEDS XREF
                                                4i|4;|4JI44[4i[4{lJ7J4ftJ4j[50[5l|52[53[54 SS[56|57b


                                                 2                PmiUIANI 3
                                                                                                      SIC
iiil
                 2K
                                                 72
                                                     40
                                                                              53f
                                                                              3|2
                                                                                                 4?
      mff
      pfo
       .j ,.        rw.iuiANT i
      '- ^|nti Iftf?^?^  FADING
                  t^plSE
                  3M T
                                                       PCI LU IAN I 2
                                                                                        LOADING
                                                                                                 FACILITY CAPACITY
                                                                                            56157 58I59I60I6II62 [63
                      -LINE NO.
                                                                  SOURCE COWENTS
                                                    43144145144
                                                                   J7l4nHal5dl5l
                                                         m
                                                                                     53
                                                            nn
       nrn
       op
     TS\
H
W
LT
15
HP
   l!
Tmvmrn
                   v UN now
?Bi29iani
32
IJM34»5I36
1
                                  LIN
       o|oiolo|o
               P|0|R|T|L|A|N|D| ICIEIMIEINITI iPiUAlNlTl I I I I I  I  I I  I  I I I I I I  I  I  I  I  I  I  i  I I  I  I  I  I  I  I  I  I  I  I  I  I I   M
                                . *$• o                                   jA                                                   Mil   _C^ ^V ^r
                       sec coot       CAPC \!il/f|L7lmp!
                                                                                                                    ippppi
    W
    CO
    Pd
    a
                                    Figure  5-2.   Sample  of Completed  Coding Sheet  for  a New Facility.

-------
                                                                               EFFECTIVE:  June i,  1984
       i i couinv
                         COMPLIANCE  DATA SYStEM CODING SHEET

Q|o|o|o|o|2| M |  | M | IN M 1 |  | I  | II I  M II  I 1  I   I I I  I II I  M II II II M II I II II II II  II
          .7  "      paiUlANI I            roUUIANI Z            POUUTANT 3                                      " .
                                                           I
                                                          NT

                                                                                         r
(                                                                                            ^..nX
                                                                                            za/JiLaJiiv
                                                                                            TLJC
     up.
      o
             ai
             - LIME NO.
                        l m t'Ji Ml tY4 til HI M t
                                             SOURCE COWEHTS
                                        '.[<] lll'.H t M [LI [H LMLU IU ^ tt'l HI W M HI I-W K1 tTJ till W [^il Ml 1+4 (41 H1M-1 Ml »j [^ [*J IP] U]W »*1 Ul Ifl U1 U4 Uf) til ti
             Ppfipi7|5l3l I  I LLI  I I  I I I I I  I I  I I  I I  I I  I I I  I I  I I  I I I I I  I I  I I  I I  I I I I 1  1 I  I I  I  IQ
  oloiololohl I  I I  I I  I I I I I  I I  I I  I I  I I  I I I  I I  I I  I I  I I  I I  I I I  I I  I II I I I I  I I  I I  I I  I I  I I I  I I  I I  I
              SCC CODE
                       CAPC
                                      STATE IKGUUTION
                                                                     PROCESS DESCRIPTION
              mm*
                               TtmrnrmT
                                                                           siTOffTOmT:
I  I I |0|0|5| |  | |  | |  | |
                          III!  Ill I III  Mil I  III I
                                                        III II II II MM III III  1 INI
i   I I  I \°M I I I I  I I  I
                                 I I  I l. I I I  1 I  l I  I 1  1
                                                      Illllll II Illlill III  1 III 1
'    U4
    .IHlSSH
  IMISSIUll

   I Ml IB
nun
i
                                 1 1  ill M M 1 1  ll  I
                                                      1  II 1  1 1  1 II III 1  1 II 1  1 1  1 II 1 1
              NO.
                                         EMISSION POINT COfftENTS
          61
           SINGLE
                                       38139 40pn«K3]44 145

                                       A|S| |F|I|R|E|D
                                                     49 SO
                                                          52
                                                                 57
                                                                       H|6?|63
                                                                                    70I7II72I73
                                                                                          74 75 76|77|78 79
  I I I loio
            1111111 1111  1111  11111  11  M n  i 111 111111 111111111 111  I 1111111 11
  mission ACTION     OPIIONAI ACTION DESCRIPTION
  POINT NO. NO.         USED HUH AIPE H
                                                         ACTION

                                                PENALTY AMT   T»Pt  DATE ACHIEVED  DATE SCHEDULED SfAFF
                                                                                       RDE8
          7 I  I I  I I  I I I  I I  I I  I i
                                                         5|3|0|4|1|5|8|00|4|1|5|8|0
          7! .M 1111 11 1111 11
                                                LLLIJ_L I  I I  I M I I I I II I

                                              ACIIUN COHHENIS
                                       I M I M I  M  I M I  M I I M M M I  I I I  I I I M M I
                                                                                    ESULI
w
a
                     Figure 5-3.   Sample of Completed Coding  Sheet for Change Transaction.

-------
                                                       EFFECTIVE:   June 1,  1984
    Card 4,  line  2,  a source comment that  exists  on the master file with  the




following  text:   PORTLAND CEMENT  PLANT.   A  change  for card  4,  line 2,  will




replace this text with the text on the change transaction:   PO BOX 753.




    Card 5,  point 000,  contains  a  "7"  in the Compliance  Status Code  on the




master file.  The change transaction will  replace  the Compliance Status  Code




and the Process  Description;  all  other data  on the  master file record will be




unchanged.    On  card  5,  point 001,  only  the  Compliance Status  Code will  be




changed on the master file.




    Since point  020  did not  have  any comments associated  with it,  comment 1




for point 020 is  entered as new.




    Action 01 for point 010 has no Date Achieved or Results Code  on  the master




file; a change  transaction will add these two fields to the master file record




created during a  previous update cycle.




    Point  020 did not have any actions on the master file.  Thus, an action 01




is added with an  Update Code  "N".








    5.3.2  -Deleting  Data from the CDS Masterfile




    A  delete transaction contains a "D"  in column 80,  the Update  Code; it is




used to delete one or more records from the master file.  A card  1  delete will




remove  all master  file  records for  a given  facility.   A card  5  delete will




remove  one emission point together  with  all  associated comments, actions,  and




action  comments.  A card 7  delete  will  remove  one action  together with  all




associated  action  comments.   A   card 4,  6,  or  8  delete  will  remove   one




comment.   A card 2  or a  card 3 delete is  invalid.   Remember,  if only  some of
                                       -94-

-------
                                                       EFFECTIVE:  June 1, 1984
the data elements  on a particular card  type  are  to be deleted, a  "C"  must be

entered in column 80 and asterisks placed in these fields.  A  "D"  in column 80

will delete the entire masterfile record.
    1.  Deleting  an  Entire Source,  Card  1.   An entire  source can  be
        deleted by using a  card  type  1  with an Update Code  "D".   Fill  in
        columns 1-19  and  code  a "D" in column 80.  Do not fill in columns
        21-79; no data  may be  coded in these  columns.   Before submitting
        this card, make certain that all the information on the source is
        no longer needed.   This transaction will  delete  the  entire source
        and all related points, actions, and comments.

    2.  Deleting  an   Emission  Point,  Card  5.   Fill  in columns  1-19  and
        place a "D" in  column  80.   Do not fill  in  columns 21-79;  no data
        is to  be added to these columns.  An emission  point  delete will
        remove  the  emission  points  and  all  associated  emission  point
        comments,  actions,  and action  comments.  A card  5  delete  for
        point 000 is  invalid.

    3.  Deleting an Action, Card 7.  An action  record  can be deleted  by
        using a card  7  with an Update Code "D".   Fill in columns 1-19 and
        place a  "D"  in  column 80.   Do not  fill  in column 21-79;  no data
        is to  be added. to these columns.   An action  delete  will remove
        the action record along with associated action comments.

    4.  Deleting a Comment, Cards   4,  6,  and  8.   A  source, emission,  or
        action comment  may be  deleted by using  the appropriate  card type
        4, 6, or  8  and placing  a "D"  in the Update  Code.   Columns  21-79
        must be  blank.   Card  column 20  must  contain the  line  number of
        the  comment  to be deleted.   A comment  delete transaction will
        delete only one comment  record.

        Use:  Card 4  to delete a Source comment.
              Card 6  to delete a Point comment.
              Card 8  to delete an Action comment.

    5.  Deleting  a   Pollutant.    Once   a  pollutant   record  has  been
        established on  the master  file by  card  3  transaction,  it cannot
        be  deleted unless  the  entire  source  is  deleted.  However,  all
        references to any particular pollutant can be  deleted by placing
        a  "D"  in the Pollutant  Delete Flag.   If all  data for a pollutant
        is  to be  deleted,  only the  Pollutant  Code  and  the  Pollutant
        Delete Flag may be  coded for that particular  pollutant.

        On one  card  3 transaction,  it is  possible to delete all data for
        one pollutant,  change  some  data for another,  and add new data for
        a third pollutant.
                                      -95-

-------
                                                       EFFECTIVE:   June 1,  1984
        Once a  pollutant  has a  "D" in  the  Pollutant  Delete  Flag,  that
        pollutant and  all  related data  will not  appear  on  any  output
        reports.   After  a   pollutant   has   been  deleted,  it  may   be
        reactivated by entering new data for  it.

        By  preventing  users  from  deleting  the  entire Pollutant  Record,
        the danger  of  accidentally losing  data  for  many pollutants  is
        eliminated.   Coding  errors can  still  be corrected, and unwanted
        data will not appear on any output report.
    5.3.2.1  Sample Completed Coding Sheet for Delete Transactions

    Master file  records may  be  deleted  from  the master  file  by placing  the

same numbers in  columns 1 through 19 as  the  new transaction used to establish

that record on the master file.   When an Update Code "D" is placed  in  column

80, no other data may be coded in columns 21 through 79.

    Figure 5-4 shows  three delete transactions  and  one  change  transaction.   A

delete  for  emission  point  040  will  remove  that  emission  point  and  all

associated point comments, actions, and action comments for that point.

    A delete for emission point 020, comment line 1, will delete only that one

particular comment record from the master file.

    A  delete  for  emission  point   101,  action  02,  will  delete  one  action

together with any associated action comments.

    To remove  some data from a master  file  record without removing the record

from the  master  file, use an Update  Code "C";  code an  asterisk  in  each field

which  is to be  removed.   In the example,  a  change  transaction  for emission

point 020,  action 01, will blank out the Results Code  01 on  the  master file

because   there   is  an   asterisk  in  the  Results  Code  field.   Because  Date

Scheduled  and  Date Achieved  cannot  be  blanked out,  an asterisk in  the  Date

Achieved  field will replace the existing  master  file with  zeros.
                                       -96-

-------
                                                                                                              EFFECTIVE:   June 1,  1984
                                                3536373B3J}JOil.42tli252
                                                                           J9505l5253M555fi57.bHbi6fltlfii6i6J65JiS[
                                                                  STATE REGISTRATION
                              2(;|2/||i»SIJ4l30l3ilJi!|l33l34
      pnjpnTp
      rO|o|o|o|o
                       PI LI
             SK3
                                                iwtri'tw inxii in ira iu tni it) emu w wi HI MI ».1 MJ ?s KI r.-ro MI m HI RI r« MI uj m m tut tirwu) i
                                                n  i i i i i i  i N  1111  j  11  i N i 11111  11111 i 11
                     • LINE KO.
                                                               SOURCE COW1ENTS
15
           000
                   sr
                           t*l Gil HI IJ:I sy in MM nj Ri) B'J EDI HI EM til ttl IH CHIU HUH U<1 HI »i Wl til 14) H1M aa TO RH Ml ItJ [« ffl C4d Ml UJ Lti [VJ Iffl Ml W Ml Ul tH N4 UJ U,l ril a
                           I  II II I  I  i  I  II  I  II  II  I I I  I II  M II  I  II  I  I  I II  I  II  II  II  II  I I II I I II  I
MD
       o|Q|o|o|oN  I  I  M  I  I  I  I  I M I  M I  I  i  I  I  I  I  I  I  I I II I I I  I  M  I  I  I  I  I i I I II  I  i  I  I  »  I  I  I  || I I  M I I\\
                                                                                                                                   '
I  I
           Ml  J  LUL
                             JIM
I  !  i  I  i  11 I I I  I 11  I
I  I  II  I  I  I I  II I I  I  I  I  I  i  I  I  I  I  M I I
                    M  M  M  I
                                      I  I  I  I  I  II  I  I  I  I I I  I
                                                                      !  I  I! I I  I  I  11  I  I  I  I  I I I I I I I I I  I  I
u
                    M  M  M  i
                                      I  I  I  I  I  11  I  i  I  I II  i
                                                                        I  11 I I  I  I  II  I  11  I  i I I I I I I 11  I  I
       WiSS
       I'UIIIT
       HTif

       02
          f HINC NO.
            20 *am
                                                       [MISSION POINT COMMENTS
             !pl2Jp}|l5 16M ?B ?9 J03I 33 J3 31^5 J6 3/38 J9H04M1? » 44 M5 MbN7 MB <9 50 51 53 53 54 55 56 57 M 59 60 61 6^ 63 64 6b 66 67 6B 69 /O /I 7^ /3 /•! 75 76 77 /B 79 p
             rl  m  rrnTTTll I MI  n  M M IM I Ml i M M  IMI Mill  M I M M M M M H
      I  I  I |o|Q
             11111111111111111111111111  1111111111  111111111  1111111111111  11
       IMISSION ACTION

       I'OINI 110.1 NO.
               OPTIONAL ACTION OESCRIPIIUN
                  USED HUM ATPE 00
                                                                            ACTION                             FSUll

                                                                PENALTY A>IT     TYPE  DATE ACHIEVED   DATE SCHEDULED  STAFF      ROEB
                 7l.ll  I.IJ_LU_LLL.LL
                 7l  I  I  I  I  I  II  I  I I i I II
                       11 lit. NO.
                                                                   ACTION COMMENTS
                                  2H i29|3n|3H32|33|34
                                             8[39|1
                                                                                        59l60l6ll61'l63|64|6b|66|67l6U|69|;0|7l|;?|73|/M75|/6l7/l7H|
  CO
  m
  a.
                               Figure 5-4.   Sample  of Completed  Coding Sheet for  Delete Transactions.

-------
                                                       EFFECTIVE:   June 1,  1984
5.4 CDS Coding Conventions




    5.4.1  Emission Point "OOP"




    Emission point  "000"  is reserved for the entire source.  Compliance status




of the point  000  must represent  worst-case  compliance of  any point within  a




source.  The  compliance  status of the point 000 must be constantly updated for




each change  in federally enforceable  standards.   If  an  appropriate  process




description cannot  be found  to describe  the  type of plant on  the  point 000,




the SIC code is placed in the  process description.  In the absence  of  the SIC




code,  "ENTIRE SOURCE" is placed in the point  '000'  process  description.  Any




additional  information entered on  point 000  should  represent the  point from




which the worst-case compliance was taken.




    The  compliance  status  entered on  a  point  000  will  be  automatically




recorded as the source compliance status.








    5.4.2  Action Number  "99"




    Action number "99" is used on an action level  card  7  input transactions to




assign the next available action number  for a given point.




    Example:   Point 010 for a  given source has actions on the  master file with




numbers  01,  02,  03, and  04.   A card 7  input transaction with an action number




99 would be added to  the  master file as  action number 05.








    5.4.3  Action Type "00" -  Optional Action Description




    When  a  specific  action  type is  not  listed  in  the  action  table  for the




region,  the action  type  is  entered  as  "00" in columns 53-54 of the card 7.




    The  description  of  the   action  is then  entered  in  the  optional  action




description  in columns 20-34 of  the card 7.






                                       -98-

-------
                                                       EFFECTIVE:  June 1, 1984











    5.4.4  Multiple Cross Reference




    The multiple cross-reference  field (card 5, columns 75-77)  is  used to tie




together  the  various emission  point numbers  to  one physical  emission point.




The emission point number of the first of the points would  be  entered into the




multiple  cross-reference field of  each of  the points from  the same physical




emission  point.  For example,  if CDS  points  010,  Oil,  012, and 013  all  refer




to  the  same physical  stack,  the multiple cross-reference  field for all those




.points would be 010.








    5.4.5  NEDS Source Cross Reference




    Whenever a new  facility  is being  added to CDS,,  the  NEDS cross-reference




field should be  coded.   If the NEDS number  is not known, please  consult the




AEROS contact  in your area to  get  a NEDS facility number.  AEROS contacts are




listed in Appendix B of  the CDS User's Guide.








    5.4.6  Source Number/Air Program Code




    NEDS  Source  Numbering Convention:   For  source  numbering  convenience, the




last four positions  of Source Number should  be the NEDS Cross-Reference Number




(NEDS plant  ID).   If this method is used, the  first digit of the Source Number




should be the  Air Program Code.




    Sources  subject  to several Air  Program Codes  must be entered with separate




source numbers, one  for  each program such as  SIP,  NSPS, etc.
                                       -99-

-------
                                                       EFFECTIVE:   June 1, 1984
6.0 DATA SOURCES




    There are  various  sources from which data can  be  extracted for input into




CDS.  Among these are the following:









6.1 SIC Manual




    The Standard  Industrial  Classification Manual is produced by the Office of




Management  and Budget.   The  SIC defines  industries  in  accordance with  the




composition  and  structure  of the  economy  and  covers  the  entire field  of




economic  activities.    It is revised  periodically  to  reflect  the  changing




industrial composition of the  economy.








6.2 Other Computer Systems




    6.2.1 ' NEDS




    The  National  Emission Data  System  (NEDS) is  a source/emissions data bank




which  is updated  semiannually from reports  from state agencies.   Source  and




emissions  data can be  taken  from  NEDS for  input  into CDS.   The  NEDS source




identification can be  carried  in  the  CDS  NEDS  Cross-Reference   Number  and




should  be  used in combination with  the  CDS Air Program Code for developing CDS




Source Numbers for new  sources.








    6.2.2   SAROAD




    The  Storage  and  Retrieval of Aerometric Data (SAROAD)  provides the codes




used  in  CDS  for identifying states  and  counties with  numeric   codes.   The




SAROAD  codes used to identify states  can  be  found in  the CDS User's Guide Data
                                      -100-

-------
                                                       EFFECTIVE:  June 1, 1984




Dictionary  or in  the Data  Dictionary  Appendix of  this manual.   The SAROAD

county codes  are  stored  in a table on  the computer and  can be  formatted for

print.  See the CDS User's Guide for instructions.



    6.2.3  EIS

    The Emissions Inventory System/Point Source  (EIS/PS)  is  a  subsystem of the

Comprehensive  Data  Handling System  (CDHS).   It  contains emissions data which

can  be  used  to  develop  input  into  CDS  for pollutants  and  emission points.

This system runs primarily at the state  level.



6.3 Inspection Reports

    Engineer's or  Inspector's  Reports  can be used  to develop  input  into CDS

for actions and for compliance data.



6.4 Letters of Notification

    Letters of Notification  such as  Notice of Violations,  Warning   Letters,

etc. can be used to develop input into CDS for actions.



6.5 Compatible State  Systems

    A  number  of  state  systems are  compatible  with CDS.   Some of  the states

using  the  Enforcement Management System  (EMS) or a state version of CDS have a

converter   program   which   reformats    state   data   to   meet   CDS   input

specifications.   With  the  EMS-to-CDS   Converter,  compliance  and enforcement

information from  a state is  placed  directly into  CDS with  little data  input

preparation needed on the  part  of  the region.  However,  the region  is  still

required  to perform the review functions  necessary to verify  the  accuracy of

the  reported  data.
                                      -101-

-------
                                                       EFFECTIVE:  June 1, 1984
7.0 QUALITY ASSURANCE REVIEW

7.1 Check of Existing Data for Validity

    Status Report of Data Quality

    After  reviewing  the  source  documents  and  running CDS  retrievals,  you

should  have a  good  idea  of  what data  elements need  special  attention.   A

Status Report on the current state of the data should be kept.

    In developing the report, the following items should be addressed:


*                    Status of Data Report - Questions

    7.1.1  Card 1 Data

           1.  AQCR

               - Should be present and complete.

           2.  Source Names

               - Consistency  of  names  and  abbreviations  used  per  CDS
                 Guidance.

           3.  Addresses

               - Alignment.
               - Completeness.

            4.  Regional Data Elements 1-5

               - Uniform usage in  each.


    7.1.2  Card 2 Data

            1.  City Name

               - Should be present and complete.

            2.  Zip  Code

               - Should be present and complete.

            3.  State Registration  Number

               - If present, should be uniform within  each  state.


                                      -102-

-------
                                                   EFFECTIVE:   June  1,  1984
       4.   NEDS  Cross  Reference

           - Completeness.
           - If  present, should be  combined with Air Program Code  for
             Source numbering.

       5.   SIC Code

           - Should be present and complete.

       6.   Air Program Code

           - Should be present and complete.
           - Should be  combined  with NEDS  Cross Reference for  Source
             numbering.

       7.   Air Program Status

           - Present for all new  source  program-subject facilities  at
             a minimum.

       8.   Regional Data Element  6

           - Uniform usage if present.

       9.   Staff Personnel Code  Source

           - Completeness.
7.1.3  Card 3 Data
       1.  Pollutant  information:   Compliance,   Pollutant,   and  Air
           Quality Control Indicator.

           - Should  be   kept  current  for  all  majors  and  minors  in
             non-attainment areas.

       2.  Loading Derivation Code

           - Should be present for all Class Al sources.

       3.  Source Classification Code

           - Should be present for all sources.
                                 -103-

-------
                                                   EFFECTIVE:   June 1,  1984
7.1.4  Card 5 Data

       1.  SCC Code
           - If  present,  should  be  complete  and  correct for  boiler
             sources at minimum.

       2.  Capacity Code

           - Should  be  present for  commercial boilers,  institutional
             boilers, and  coal-fired boilers for industries other than
             power plants  (SIC 4911).

       3.  Compliance Status

           - Should be current and correct for violating sources.
           - Should agree with Card 3 data.

       4.  SIP Code

           - Should be present and complete for sources with SCMS = 5.

       5.  Pollutant Code

           - Should agree with Card 3 data.

       6.  State Regulation

           - Uniform usage as per guidance for NSPS sources.

       7.  Process description

           - Should be accurate and complete.
           - At  "000"  point,  if  Process Description  contains   "ENTIRE
             SOURCE"  and  SIC  Description is  present,  replace   process
             description with SIC Description.

       8.  Multiple Cross  Reference

           - Proper  usage.

       9.  Regional  Data Element 7

           - Uniform usage if present.

       10. Procedural Compliance

           - Present on  NSR, PSD, and NSPS sources.
                                  -104-

-------
                                                      EFFECTIVE:  June  1,  1984



    7.1.5  Card  7  Data

          1.  Penalty Amounts

              - Present  for  Action Types Z4  and  Z6 only.

          2.  Action Type

              - Action  Description should be  correct and,  at a minimum,
                consistent  with the  8/2/83  memo and CDS National  Action
                Conversion Program.

          3.  Date Achieved

              - Should  be present  for all  completed  actions.

          4.  Staff Personnel  Code Action

              - Completeness.

          5.  Regional  Data  Element 8

              - Uniform usage  if present.


    7.1.6 Other Data

           1.  Comment Cards  (4, 6, and 8)

               - Should  be  numbered correctly.
               - Comments should make sense.

           2.  Closed Sources (APST = X)

            -  - Should  be  archived if closed for more than eight quarters.


7.2 QA Reports from CDS

    Reports  can be  run  to  duplicate the formats of  the CDS input card types as

Figure 7-1 through 7-5 illustrate.
                                     -105-

-------
                                                         EFFECTIVE: June 1, 1984
I
h-'
O

I
                         COMPLIANCE DATA SYSTEM
See reverse side for a
list uf all CDS data
elements and lliclr
.ililji evliilloiis.
|0,1| I i | U (QAJiAiLiliTiYi lA,
1215 7 9
Roglon Loci llopoil Till*
H.OI I ,,, I I I I ,,,,,,,
i * 4 / 9 ii
Elome°nl Cond. Value (L.IIJu.
|l,0l I , , , I I I ,,,,,,,

|l,0| | , , , | | | , i , , , , i
11,01 I , , , I I I ,,,,,,,
|t|0| 1 , , , 1 1 | ,,,,,,,
|l,0| | , , , | 1 | ,11111,
|l,0| 1 , , , 1 | | ,,,,ii.
|1,0| | , , | | | | | i i i i | i i

Report Request Form
SiSiU,R,A,NiCiE, iT,E,SJ, i1j ,-, ,CAR,D, ,1, .AMD, ,4, ,D,A,T,A|
20 • 30
i i i i i i 1 i i i i i I
mod)
.,41, ii|i,i|.
, i i i i i i i i i i i
, i i i i , i i i i i i
i , , i i , , , , i i i
, , i i i i i i i i i i
, , i i i i i i i , i i
i i i i i i i l i i i i
t i i i i i i i i i i i
(Limit - 100 "10" Cards)
nfiPOIIT FOHMATS PASSWORD (REQUIRED 10 ACCESS COftf IOINI IAI
I?,2J BlU I.I 1 ., I IP.A.S.SHMO.R.DI OAIAUIMINIS)
12 15 70 loTl 11 21
REPORT SEQUENCE
112J 1 . . l 1 1 1 I.I. J ( .1 1 1 1 . l . J 1 . . . J I j. l l J
121 7 'J 12 11 17 19 ZZ Z1 27 29 32
SCOI/tHU UHlltO 10 40 CIIADACIERS
QUICK LOOK nCPOnT FORMAT
LiSJ (AjQidRJ iqiYiCiPl ISiNiMiEJ
121 79 12 11 17
Enter D0
CONDITION CODES
(10 CARD)
M - WIST E()UAL
A - ALTERNATE (used fur
multiple values of a
given data element
U - UNEQUAL
G - EQUAL OR GREATER THAN
L - EQUAL OR LESS THAN
P - PRESENT ANY ENTRY
0 - DLANK OR ZEROS
Hv>»«r of
II lobtotillnf
-jn •>»'• •lemrntt
on QL

lSTiR.T| |R|D,E|1| |FfrDiE,2l |RjDtE|3J IR(DiEi4i QDjEiSj i ; , , j
19 22 21 27 29 32 31 3/39 12 11 47 19 52
llfporl i .1 .1 1 I 1 1 1 1. .1 1 1 1 1 1 1 1 1 1, 1 U_L_LJ I§IU
tiom 5/| 57 59 02 01 07 09 72 71 77 '^""s'tVi
cwt 5lTO,"
( i i i 1 L , , i 1 t i i | | 1 i l i | 1 i ii 1 I,, i | l_J_i_J_J
19 22 21 27 29 32 31 37 39 12 11 17 19 52
OF COLUMNS OAT A F.LEMEHT8 'SllIllSj' ^-^j M^M
1 lini-
Onto Sulj^il 1 1 pd


i i i i i i i i i i i i i i i 1
70 III)
LEVII. COOLS (01 CARD)
REQUIRED 101! SI) Rf.PORI ONLY.
VALID ARC:
S - SOURCE ONLY
1' - POINT * SOURCE
A - ALL IIAIA (default)
C - CRIIEHIA IVUCH ONLY

REPORT rilHMAfS (20 CARD)
QL-Quick Look
QD-Double Line QL
Q2-Doi
-------
                                                                                                      EFFECTIVE:    June  1,  1984
o
»4
 I
                  See reverse side for a
                  list uf nil CDS data
                  elements and their
                  iililirevlatluiis.
                            COMPLIANCE  DATA  SYSTEM
                                    Report  Request  Form
                  lajJ UJ U  iQAJiA.L.iiTiYi IA.S.SIU.R.A.N.C.EI .T.E.S.T. .2.
                  124579               /  20               30
                     Region Lotol lltpo.l Till*       '
                                                         jCiAjBiDi. |2| ,D|A|T.Ai.
        JLJ
        To
                                          ^ttV
                  ^ V—71  V \t
                                                                                   5J
                                                                              01)
                        D«ln
                       Elemonl Cond- VoluB
                  IL«J  I ... I  U
                  U.Ol  l.ii I  U
                  1 1. 01  I i  i i |  U
                  11.01  t .  . . I  U
                  H.Uj  t l  l i I  U
                  LL2J  lii i I  U
                  liiOJ  1 .  t i I  U
                  H.oi  I ... I  u
                  LUPJ  La_i_jU  U
                  (Limit -  101)  "10" Cards)
                  REPOIIT  FORMATS     PASSWORD («QUIMO 10 ACCESS CONFIUtMIM.
                  liwi  IQiU UJ  LiJ  |P|A.3i9WOiBiBl    •»«'«"«««
                  12  15  /  o  lull  u          2i
                  ncponf OEOUEIICE
i i i i i i i i i i i
iiii. ii. itii
i i i i i i i i i i i
i i i i i i i i i i i
i i i i i i i i i i i
i i i i i i i i i i i


i i i i i i i i i i i
|ii(iiii
iiifiiii
. . . i . . . i
i i i i i i i i
i i i i i i i i
i i i i i i i i
i i i i i i i i
i i i i l i i i
i l i i i i i l
                                                             CONDITION  COOLS
                                                                (10 CARD)
   M - MUST EQUAL
   A - ALTERNATE (used fur
      multifile values of o
      given data clement

   U - UNEQUAL
   G - EQUAL OR GREATER TIIAII
   L - EQUAL OR LESS TIIAN
   P - PRESENT ANY ENTRY

   D - OLANK OR ZEROS
                  121    79   12  11
                  SCqUCIIU I INI ICO 10 40 CIIARACIIKS
17 19   22 24   27 29
                                                   32
                                                                 Kwfcir gf
                                                             1 | i«btotiltn|
                                                              39
          dm llforntl
          on (K.
QUICK LOOK REPORT FORMAT

14.01
 I 2
                             l  iZiliPiCl ISiTiR.G|  ^E.X.S| LSil.C.CI IS. I.GDI IF.E.DtF( lA.P.SiTi iA,p.C.Di
                            79   IZ 11    17  1
-------
                                                                                                      EFFECTIVE:   June  1,  1984
o
00
 I
                  See inverse sl  SOURCE
                                                              A - AIL DAIA (default)
                                                              C - Cm U IDA IVMCII ONLY
                                                             HF.I'OIII rilKHATS (20 CARD)
                                                                                        QL-Quick Look
                                                                                        CD-Double Line gL
                                                                                        Q2-Double spaced QL
                                                                                        MS-Standard Milestone
                                                                                        Mi-single spaced Milestone
                                                                                        SD-Source Data
                                                                                        AC-Action Summary
                                                                                        QT-Questionaire
                                                                                        FL-Flex
                                                                                                           COMMENT cones (m CARD)
                                                            C - ALL COIN)(IIS
                                                            s - SOURCE CUMHIHIS ONLY
                                                            i> - romr COMMINIS unir
                                                            A - ACI ION comirnr. ONLY
                                              Figure 7-^^ Report Request Form - QA Test 3.

-------
                                                                                                     EFFECTIVE:   June  1,  1984
o
VO
 i
                   Sen reverse  side for a
                   list of all  CDS data
                   elements and their
                   aliljrevl.it Ions.
                            COMPLIANCE  DATA  SYSTEM
                                    Report Request  Form
                  IPijI li| U IQiUiAiL.l.TiYi lAiSiS.U.R.A^iCiEi  iTiEiS.Ti i4. .-. .CAR.D. .5. .A^Ly
                   1  Z   4 5   7   9                20              30               40,
                      Roglon L*«*l llvpo.l Till*                                            t.' I. I—I—
                               U |
                       EUrnVnl Cond- Valu* "-•" *"««•«»
UlSJ I.I.I U
Hi»i 1  1 1  i  i u
1'iQI l  i i  i  | U
li.oi l  . .  .  I U
     i  ...  i u
     I  i i  i  I U
lii2J I  . i  i  I U
H.oi |ii  i  | U
IM1 I  i i  i  I LJ
(Limit  - 100 "10" Cards)
REPOIIT POHMATS      PASSWORD (mquuto ID Man CMTIDENIIM.
               Li J   lP.AiS.SMHO.RiDj       '
               foil   14           Zl
HF.POnT OGQUCrtCE
L12J i.i i.ij i  - . . I I . .  .  i 1 1 • .
 I Z  4     79   1Z  14    17  19   ZZ Z4   Z7  Z9    3Z
scwriicc umrto to «o CIIAHACIIRS

1 1 1 1 1
1 1 1 1 1
1 1 1 1 1
1 1 1 1 1
1 1 1 1 1
,
I 1 1 1 1
F t ' 1 '

II. Illl Illlllll
1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 I 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 I 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1
                   I?,°J IQiU UJ
                   1  2  T5   J U
                                                                               CONDITION  CODES
                                                                                  (10 CARO)
                                                                           H - MUST EQUAL

                                                                           A - ALTERNATE (used fur
                                                                               multifile values of o
                                                                               given data element

                                                                           U - UNEQUAL

                                                                           G - EQUAL Oil GREATEII IIIAM

                                                                           L - EQUAL Oil LESS IIIAN

                                                                           P - PRESENT ANY ENIRY

                                                                           0 - DLANK OK ZEROS
                                           (lu.ttr of
                                        II trttolillnf
                                        -in tfltl tltmrnll
                                        •" on W.
                     lni«r Dm uinenti (o bt Includtd on «rport
                     ihicH if \» Chir.cifii »iih »«i» optlooi
                     U«IUd to .10 «'th SUndirtf Held In?
                                                                  T line	
                                                                  Uale Submitted	
                                                                  Return ltr|>ort lo4.	
                                                                  Hall Slop	
                   QUICK LOOK neronr  FODMAT
                   14,01 IS.GC.8I lCiA.PiCj ICfflS.J| lS.liP.CJ  IftlaUJJ  |S-PiE,G| lE.C.A^TI  IP.R.D.Si	
                   124     79   12 14   17 19    ZZ  Z4    Z7  Z9    32  34   37  39    4Z  44   47  49
                                          57 59   02  04   07 09    72  74    77  79110,'r
                                                                             (UN  Sl'T'
                                                                             coot ^i,1,,"
MIIESTONE neronT FOHMAT
|5iQl  1 i  i  i J I  . .1
124     79   IZ  14    17  19   ZZ Z4   21 29    32  34   37 39   4Z 44   47  49   52
                  .       nwi  i
                  15.11 II I  I  I
                  1  i 4     7
                                coiunns
VALURB OF COLUMNS DATA ELEMENTS
                                                      (use 'emu'ron
                                                           VM.UC)
I i I  I 1 |  . .  |_l
54    57 59   02
                                                                     I.EVI.I. CODES (01 CARD)
                                                                  REQUIRED 1011 SD III COM I ONLY.
                                                                  VALID ARE:
                                                                    S -  SOURCE ONLY

                                                                    I' -  I'OINT H SOURCE

                                                                    A -  ALL IIAIA (default)

                                                                    C -  CnlllRIA IWICII ONLY
                                                                   REPORT FORMATS (20 CARD)
                   QL-QuicK Look
                   QD-Double Lino QL
                   02-Double spaced  QL
                   MS-Standard Milestone
                   Mi-single spaced  Milestone
                   SD-Source Data
                   AC-Action Summary
                   QT-Questionalre
                   FL-Flex
                                                                                                           COMMI.HI CODES (40 CARD)
                                                                                                          C - ALL COMHLNIS

                                                                                                          S - SOURCE CUWINIS (ifll.Y

                                                                                                          P - I'OINI CDI1MINIS DULY

                                                                                                          A - ACIIUN tl»Blltlir. ONLY
                                               Figure  7-4.   Report  Request  Form -  QA Test  4.

-------
                                                                                                       EFFECTIVE:   June  1,  1984
o
                  Sp(! rnvursc side for a
                  llr>t. i.r all CDS data
                  elements nml Ihclr
                  abbreviations.
      COMPLIANCE  DATA  SYSTEM
               Report Request  Form
                 I2dl UJ U  IQAJ.A.L.I.T.Y. IA.SISIU.R.A.N.C.E. .T.E.S.T. .5.
                  I  ?.   4 5   /    Element* to b«  Includfld on Report
   Hotted to 1)2 (hiricten  xltri NOIID Option!
   llmHtd to 110 Kith SUndird lletdlnf
                                        IS,TiA.C|
                                     37 39   4Z  41
                                                                                                ia&!ifi|
                                                                                             47  4'»   !iZ
                                                                                        Ll.. I I.I
                                                                                        74    77 79tH»"t-
                                                                                               COM ,?*'S
                                                                                               COUE 5
-------
                                                       EFFECTIVE:  June 1, 1984
8.0 TECHNICAL STANDARDS

    In order to  maintain  CDS and provide enhancements to the current system of

computer programs,  it is  necessary  that  analysts  and programmers  providing

operation and maintenance  support  to the EPA be  able  to easily understand the

computer programs  that make up  the  Compliance  Data  System.   The  following

sections outline specific  Programming and Testing  Standards which  should be

adhered to when effecting a change to the CDS computer programs.



8.1 Programming Standards

    8.1.1  General COBOL Guidelines
    •  Use ANSI  Standard COBOL  as much as  possible.   This  will  greatly
       facilitate transporting the program between  computer facilities as
       well  as  improve  understanding  on the part  of programmers  from
       other installations.

    •  Division headers  should  appear at the  top of  the page  and should
       be  separated  from the body of  the  division by  one or more blank
       lines.

    •  There should  be at  least one  blank line  between a  section header
       and the body of a section.

    •  Use of  columns 1-6  and  73-80 should  be  consistent  throughout all
       programs and subroutines of a  system.
    8.1.2  Identification Division Guidelines
    •  This division  should include the PROGRAM-ID, AUTHOR, INSTALLATION,
       and DATE-COMPILED paragraphs.

    •  This division  should contain  a REMARKS  paragraph  describing  the
       purpose  and  functions   of   the  program  and the  sections  in  the
       procedure division.

    •  Once a program has been  placed  into production,  every modification
       should include comments  chat contain the following:
                                     -111-

-------
                                                   EFFECTIVE:  June 1, 1984



   -  An index of the current modification.

   -  A description of and the rationale for the changes made.

   -  The date and person making the change.

•  The AUTHOR paragraph should list the names of all  persons who have
   made changes to the program.



8.1.3  Environment Division Guidelines


«  Internal file names, the ASSIGN TO, and  external  file names within
   SELECT statements should be aligned in columns.

•  Each  clause  subordinate  to  a SELECT/ASSIGN  TO  statement  should
   appear on a separate line underneath the ASSIGN TO, as follows:

      SELECT MASTER-IN        ASSIGN TO MASS-STORAGE OLD-MASTER

      SELECT MASTER-OUT       ASSIGN TO MASS-STORAGE NEW-MASTER

      SELECT SUMM-RPT         ASSIGN TO PRINTER SUMMARY

      SELECT XREFFILE         ASSIGN TO MASS-STORAGE XREFFILE

                              ORGANIZATION  IS INDEXED

                              ACCESS IS RANDOM

                              ACTUAL KEY IS XREF-ID

8.1.4  Data Division Guidelines


«  Clauses within  an  FD should appear on  separate  lines under the FD
   file  name  and FD's   should  appear   in  the  same  order  as the
   corresponding SELECT statements.

      FD   MASTER-IN

           LABEL RECORDS ARE STANDARD

           RECORDING MODE  IS F

           BLOCK CONTAINS  153  RECORDS

           RECORD  CONTAINS 473 CHARACTERS
                                  -112-

-------
                                                   EFFECTIVE:   June 1, 1984
•  Each 01 level item should be preceded by one or more blank lines.

•  Item names, PICTURE, USAGE,  and VALUE claues for items at the same
   level should all be aligned in columns.

•  If  an  item  has both  USAGE  and VALUE  clauses,  align  the  VALUE
   clause beneath  the  USAGE.   If a VALUE  literal  will  not  fit on one
   line, it should be placed on a separate line beneath the item name.

•  Each level  in  a data structure definition  should be indented four
   spaces  from the  previous  level.   This  greatly facilitates  the
   understanding of the structure.

•  String lengths  within  PICTURE  clauses  should always  be  specified
   in  parentheses  - even  if  the length is a  single character.   This
   reduces the probability  of  error and  eases  the checking  of  group
   lengths.

•  The  use  of 88  level items is  highly  encouraged.   This simplifies
   the understanding of Procedure Division code.

•  The use of 77 level items should be avoided.

•  Constants should appear  at  the beginning of  WORKING-STORAGE  along
   with their  associated  VALUES.   Variables should not be initialized
   with VALUE clauses - they should be initialized by the program.

       01  PROG-VERSION     PIC X(4)          VALUE 'V3.21.
   *
       01  RECS-IN          PIC 9(10)         USAGE COMP.
   *
       01  RECS-OUT         PIC 9(10)         USAGE COMP.
   *
       01  HOLD-REG.
           02  HOLD-REC-ID       PIC 9(4).
           02  HOLD-REC-TYPE     PICX(l).
           02  HOLD-REC-DATE.
               03   HOLD-REC-YY      PIC 9(2).
               03   HOLD-REC-MMDD    PIC 9(4).
           02  HOLD-REC-QUANT    PIC 9(5)V9(1).
8.1.5  Procedure Division Guidelines
•  Multiple  objects  of  a  single  statement  should be  lined  up  in
   columns with one object per line.
                                 -113-

-------
                                                   EFFECTIVE:   June 1,  1984
       OPEN INPUT   MASTER-IN
                    PARM-FILE
                    XREF-ADDR-FILE.
       MOVE 0 TO REC-CNT
                 LINES-OUT
                 TAB-PTR.

•  Operators  and  operands  in  continued  statements  or  groups  of
   similar statements should be aligned in columns.

       MOVE OLD-ID          TO PRT-LINE-ID.
       MOVE ID-TOTAL        TO PRT-LINE-TOTAL.
       MOVE ZEROES          TO ID-TOTAL.

       COMPUTE YEARLY-TOTAL = QTR1-TOTAL + QTR2-TOTAL
                            + QTR3-TOTAL + QTR4-TOTAL.

•  IF  statements  should  not  be  nested  deeper  than  three  levels.
   Deeper nesting is usually very  difficult  to understand.   If deeper
   nesting  is  required  by the problem at hand,  then the lower level
   nesting should be performed elsewhere.

•  Each ELSE should be aligned with its corresponding IF.

•  Each condition  of  compound IF's should appear  on a separate line.
   Parentheses  should   be  used   to  simplify  understanding  of  the
   relationships between the conditions.

•  Subjects of IF's and  ELSE's should be aligned  in columns after the
   object conditions.

      , IF        (EMP-TENURE > 40)
          AND    (EMP-AGE    < 60)
                                      ADD  1  TO TYPE1-CNT
                                      PERFORM  PROCESS-TYPEA
       ELSE
                                      PERFORM CHECK-TYPES-B-F.

•  STOP RUN should appear  only in  the driver SECTION.

•  The VARYING FROM, BY, and UNTIL clauses on  a PERFORM should appear
   on separate  lines  aligned  under the  PERFORM  section  name.   The
   VARYING  index should not, of course,  be  altered  by the PERFORMed
   section.

       PERFORM LOAD-REC-BUFF
               VARYING BUFF-PTR FROM  1  BY  1
                 UNTIL BUFF-PTR >xBUFF-SIZE
                    OR REC-ID-CHANGE
                    OR END-OF-MASTER.
                                  -114-

-------
                                                       EFFECTIVE;  June 1, 1984
    •  All  I/O  operations  should  be  isolated  into  separate  SECTIONS.
       This makes the  details  of such operations more transparent to the
       program and simplifies the reading and modification of the program.

    •  All  arithmetic   computations   involving  more  than  one  operation
       should be performed  with the COMPUTE verb.  The  only exception is
       that the DIVIDE verb may be used  if  a  remainder  is  required.   In
       this case,  DIVIDE BY should be used and not DIVIDE INTO.

    «  Parentheses  should  be  used  to  simplify  the  understanding  of
       complex arithmetic statements  or  wherever  confusion may  arise as
       to the order of evaluation of a statement.

           COMPUTE ROOT = (DISC - B) / (A + A).

           COMPUTE ADJUSTED-INT = BASE-INT * (NUM-PDS - 1)
                                + BASE-VAL / (NUM-PDS +1).
8.2 Testing Standards

    CDS  is  a frequently  used,  highly visible  system.   Every  effort must  be

made  to  discover the existence of  errors  in the system when  changes are made

to CDS.


    •  Any change in the system is to meet the stated requirements.

    •  A change  in  one  part of the  system  is not to cause errors  in any
       other  part  of the  system.   All  other parts of the system are to
       operate  the  same  after a  change  as  they  operated  before  that
       change.

    •  The  assumption that  "no one will  ever make  that error"  is not
       valid and is not to be made.


    Test  Plan Standards  can be  found  in Section  6.2.2  of   the  ADP  System

Documentation Standards prepared by MIDSD.
                                     -115-

-------
                                                       EFFECTIVE:  June 1, 1984
    8.2.1  Test Plan (Overview)

    The ultimate objective  of any testing process during  implementation is to

attain  a  certain   level  of  confidence  that  the  subject  of  the  test  is

performing  according   to  specifications.   This  objective   is   reached  by

designing  a  set of  test procedures  that will  demonstrate  the existence of

errors.   Note  that a  test  does  not  try to  find all  errors  in a  program or

system  (that being much like trying to  catch the last fish in  a  lake without

knowing how many fish there are  or how  good our bait is); rather, it tries to

find those errors which are most  likely  to occur or which  would be  most costly

should they occur.

    In  light of the above comments, this  section should  describe  the overall

testing  strategy for  this  system as  well as which  kinds of  errors are  most

important  to detect for this  system.



    8.2.2  Types of Failures

    A  system may  fail (i.e., not satisfy user  requirements)  in the  following

ways:


    •   The System  Design (Functional Description, Draft User  Guide,  Data
        Dictionary)  does not accurately reflect requirements.

    •   The Detailed Design  is not a  faithful elaboration  of  the  System
        Design  (frequently referred to  as a specification error).

    •   The program within  the system fails  to  meet  its   specifications.
        This  failure  can occur  in two  ways:   (1)  wrong operations  are
        performed on program path; and  (2)  the path taken  is the wrong one
        for some data.

    •   The performance  (response time,  turn around  time,  etc.)  of .the
        system  may  not  be  as specified.

    •   The  system  design   may  not  be   implementable  in  the   chosen
        environment.
                                      -116-

-------
                                                       EFFECTIVE:  June I, 1984
This section should indicate those types of  failures  considered applicable and




the  following  subsections  should  discuss  the  steps taken  to  detect  these




errors.








    8.2.2.1  System Design Failures




    The  conformance  of the  system design  to  the  requirements  will have been




certified by  a  design review prior  to the  beginning of detail  design.   This




section  should discuss  the  findings  of  this design  review  in  terms  of the




robustness and simplicity of this system.








    8.2.2.2  Detailed Design Failures




    The  detailed  design can best be shown  to be  a faithful representation of




the  system design  by  a  technical  review team  made  up  primarily of  data




processing  personnel.  This section  will  describe  procedures  for  performing




that review and will dictate the makeup of  the team.








    8.2.2.3  Program Failures




    Of  the two kinds  of  program  failures  mentioned  above,  the first kind is




best  detected  through  the  use of  "coverage"  tests which  ensure  that  each




statement  of  the program  has  been  executed and  the results observed  (either




explicitly  or  implicitly).   Failures  of  the  second  kind are  best detected




through  a  formal  review of  the subject code by disinterested programmers  (also




ensuring adherence to coding guidelines).




    This  section  should,  therefore,  describe   all  applicable  test   cases




(including  how  to run them,  their  expected results,  and  procedures to follow




should they fail) and describe  the findings of the  code review.






                                     -117-

-------
                                                       EFFECTIVE:   June 1, 1984











    8.2.2.4  System Failures




    This section will  describe procedures for conducting the  system test.   It




will consist of three parts:   (1) a review of the user  documentation to ensure




that it  faithfully  represents the system design and the detailed design; (2) a




rerun of all  program tests on the completed system or version; and  (3)  a  set




of   randomly   selected  tests   to  determine  if  there  has been  a  gross




misunderstanding of  the  problem.   All test  cases will  be developed  from user




documentation  and  will  be  documented  prior  to  running  with  the  expected




results.  There must be a system test for every delivered version.








    8.2.2.5  Performance Failures




    This section will  describe procedures for doing a volume  test to determine




timings and to estimate operational costs.
                                      -113-

-------
                                                       EFFECTIVE:  June 1, 1984
9.0  CURRENT HEADQUARTERS GUIDANCE

     The  following  is  a  collection  of  currently  applicable  Headquarters

Guidance for CDS users.

DATE:     May 24, 1982

SUBJECT:  Guidance on State Reporting of Air Compliance Data to CDS

FROM:     Director
          Division of Stationary Source Enforcement

TO:       Directors, Air & Waste Management Divisions, Regions I-IV, VI-VIII, X
          Directors, Air Management Divisions Regions V and IX


    The  following  guidance presents  current EPA  policy on  the  reporting  of
stationary  source  air compliance  data by  states  for entry  into the agency's
Compliance Data System (CDS).

    To  provide  background, all  EPA Regional  Offices  receive  source-specific
compliance  information from  their states on a routine basis.  The frequency of
reporting varies from quarterly,  the  minimum  frequency acceptable,  to almost
daily  for  those states that have  direct  access  to CDS and  have  chosen to use
the  system  as  a management  tool.   The compliance information is  provided to
EPA  either manually  or  by an  automated mechanism,  usually a tape,  disk,  or
direct access.  The  information to be reported and  its  frequency typically is
established through the Section 105 grant machanism.

    Since  EPA  relies  heavily  on  state-reported  data  in  determining  the
compliance  and  enforcement action, information is critical.  Therefore,  it is
our  policy  to  require all. EPA  regions  to establish a mutually agreed to State
information and reporting protocol.  Such reporting  should be  no less frequent
than quarterly.

     In  an  effort to  improve  information flow while at  the  same  time reducing
manual data handling,  we  encourage automated data  linkups between EPA and the
states.   Such  linkups  minimize dup'licative data  handling and  thereby reduce
resource  expenditures and the  potential  for  error.  We  have made  available
contractor  support  as  well  as the  expertise of our Division  of Stationary
Source  Enforcement  (DSSE)  in facilitating  this  end.   For more  information on
this aspect of the program, please contact  Howard Wright of DSSE at 382-2833.

     Please  note  that there  is  no  requirement   that  states  use  CDS or  any
automated system.  While  it  is  encouraged  where it  can  be mutually benficial,
the manner of recording data is left to the state.
                                      -119-

-------
                                                       EFFECTIVE:  June 1, 1984
    As  more  and  more  data  are  electronically  transmitted to  EPA,  quality
assurance   practices   on   source-specific   state   submissions   become   an
increasingly  necessary activity  for EPA.   In  this  regard,  the  Division  of
Stationary Source  Enforcement  has provided several tools to the  regions which
enhance quality assurance  capabilities  and thus  the  subsequent  reliability  of
data submitted to CDS.  These tools should continue to be used.

    We  are continuing to review the level of information presently required to
be submitted,  particularly in the context of  the development of  the agency's
1983 Information  Collection  Budget.   Once that  exercise  is  completed,  we will
be providing any supplementary guidance which may be necessary.

    If  you have any questions or comments on this subject, please  feel  free  to
contact me at 382-2807  or John Rashic at 382-2826.
                                      -120-

-------
                                                       EFFECTIVE:  June 1, 1984
DATE:     March 10, 1982

SUBJECT:  John B.  Rasnic, Chief Compliance Monitoring Branch DSSE

TO:       Addressees
    It  is essential  for  federal  enforcement  against  significant  violators,
workload allocation, budgeting,  and  program evaluation  to be  able  to identify
violating  stationary  sources  by the pollutant(s)  for  which  these  facilities
are in  violation.   We will  rely on  the  Compliance  Data  System (CDS)  as the
mechanism  through  which  such  information  will be  obtained.   However,  it is
apparent  that,  in  some  cases,  reliable  information of  this nature   is  not
currently  available  in CDS.   This  memorandum is  intended  to  provide guidance
for correcting this situation.

    The  universe  of  violating  sources  that  must  have  pollutant-specific
compliance  status  maintained  are "significant  violators"  as defined  in the
Kathleen  M.   Bennett  memorandum "EPA  Accountability   System  -  OANR  Policy
Guidance"  dated December   29,   1981.   See  Attachment  1  for  the  appropriate
information extracted from this memorandum.

    For such  "significant  violators," in addition to enforcement  actions and
000-point  compliance  status,   the  following  pollutant-related,  source  level
information must be maintained:
    •   Pollutant                                          PLLT
    •   Pollutant Compliance                               PCMS
    •   Pollutant Air Quality Control Indicator            PAQC


    Information for  other than "significant violators"  and/or  additional Card
3 data should be maintained per past guidance.

    If  you have  any questions or  comments, please  call me at  8-382-2826 or
Howard Wright at 8-382-2833. .
                                      -121-

-------
                                                       EFFECTIVE:   June 1, 1984
                                  ATTACHMENT 1

    Extracted from:  Kathleen   M.   Bennett   Memorandum  "EPA   Accountability
                     System-OANR Policy Guidance," 12-29-81.

                       Definition of Significant Violator


    One of the  objectives of the Administrator's Accountability  System for FY

1982 is that resources be used to address significant air violators  and return

them to compliance.   This is designed to ensure that resources are used in the

most environmentally  beneficial manner.   The purpose  of  this guidance  is to

assist regional  offices  and states in determining what the agency considers to

be a significant violator.

    In  determining  whether  a   violation  is  significant,  the  nature  of  the

pollutant should be  considered, as well as  the  magnitude  and duration of  the

violation  and   the  population  exposed.   While  no   rigid  formula   need  be

followed, the following considerations should be kept in mind.


    1.  A violation  of  a hazardous air  pollutant  standard  resulting  in
        emissions  above   the  standard  should  normally  be  considered
        significant  unless the  magnitude  and duration of  the   violation
        are minimal and the violation nonrecurring.

    2.  A  source  in  violation  of  a  State Implementation Plan  should  be
        considered significant  if  the source  is  of  sufficient size and  is
        located  so as to  impact a  nonattainment area.   Sources  above  250
        tons  per year emission  potential as  defined  in the Alabama Power
        case  should  be  considered significant  violators  are minimal  and
        the   violation  generally   nonrecurring.    (To  the  extent   that
        available  data  do not  permit  easy  identification  of  sources  in
        excess  of 250  tons/year  potential,  sources  with  more  than  100
        tons/year  actual  emissions can  be as  a reasonable surrogate.)
        Other sources in nonattainment  areas  should also be included  if
        the   amount  of  excess  emissions   is  considered  jointly  by  the
        regional office  and  state as having an important  impact on  the
        continued  nonattainment of the area.
                                      -122-

-------
                                                    '   EFFECTIVE:  June 1, 1984



    3.  Sources in attainment areas and not  impacting nonattainment areas
        would  not  normally be considered significant  because  of the lack
        of  direct  health  impact.   While  states,  appropriately,  should
        take  action  to resolve  such violations, EPA will not  give them
        high priority consideration.

    4.  Sources in violation of  new source  requirements,  including NSPS
        and PSD/NSR  permitting  requirements, should also be considered to
        be significant violators unless the  magnitude  and  duration of the
        violation are minimal.

    As  provided  for  in  the  agency's  new  accountability   system,  regional

offices should meet  with  each of their states to jointly  prepare an inventory

.of  known  significant violators.   States should be  encouraged  to take the lead

with  respect  to  as much of  the  universe  as  possible.  Wherever possible,  EPA

should use  its resources  to supplement those  of  the  state rather than to take

the lead on cases itself.  This technical assistance can be either in the form

of  direct case assistance  (if requested) or  through sponsoring of technical

workshops and other  program  building/supporting  activities.   EPA should assume

the lead  only where  a state cannot or will  not take the lead, despite whatever

assistance EPA can provide.
                                      -123-

-------
                                                       EFFECTIVE:  June 1, 1984
DATE:     May 5, 1982

SUBJECT:  CDS Guidance for Tracking Sources on Compliance Schedules

FROM:     John B. Rasnic, Chief
          Compliance Monitoring Branch, DSSE

TO:       Addressees
    There has been some confusion about how to record  compliance  status in the
Compliance  Data  System  (CDS)  for  sources  on  schedules  to  install/modify
control equipment.   Some  regions are tracking sources on  federally enforcable
delayed compliance  orders  (DCOs)  as if  such  sources, if  meeting the interim
requirements  of  the DCO,  are in  compliance  with  the SIP.   The  Division of
Stationary Source Enforcement  (DSSE) disagrees with this approach.

    Despite the  fact that many DCOs are promulgated as SIP revisions,  they are
fundamentally different from Section 110 actions  that  revise  the  SIP.   A DCO
serves  to  insulate  the  source  from  further  state,  federal,  or  citizen
enforcement under Sections  113  and 304  of  the Clean  Air Act for subsequent
violation of  the SIP,  so long as  the  order  is  in effect and is being  met.  It
does  not  replace   the  original  SIP  requirements  as  does  a   Section  110
revision.  A  DCO is a  remedial  action which  corrects  a  violation rather than
excusing  it.    For  these   reasons,  we   believe   such  distinctions  warrant
different  approaches in  tracking the  compliance  status of  affected  sources.
Since  this  question was  raised,  DSSE  is  taking the  opportunity  to restate
guidance on  the  entire subject of  tracking  sources  on compliance  schedules in
CDS.

    Sources meeting  schedules  which, because of  a  Section  110  action,  are part
of  a  federally  approved  SIP should be  carried  in  CDS  as in  compliance and
coded  as  SCMS = 4.   The  SIP code (SIPC)  should be used  to designate  the  type
of  schedule (SIPC =  2).

    All  other sources  on compliance schedules  should be  tracked as  "Meeting
Compliance  Schedules"  (SCMS  =   5).   This  included  sources  with compliance
schedules established by  DCOs  and court orders.

    The. type  of  schedule for such  sources  should also be identified  by  using
the proper SIP code, e.g.,  "federally enforcable DCO"  (SIPC = 1).

    If  the need  exists  to track  sources on federally  approved SIP  schedules,  a
special report listing  such sources  can be established.
                                      -124-

-------
                                                       EFFECTIVE:  June 1, 1984



DATE:     February 2, 1982

SUBJECT:  Guidance on Establishing State and Regional Programs for VOC Sources

FROM:     Director
          Division of Stationary Source Enforcement

TO:       Air & Waste Management Division Directors, Regions I-X


    Because of the changes to State Implementation Plans in  response  to Part D
of  the  Clean Air Act, there  has  been a significant increase  in the  number of
VOC  sources   (sources  emitting   volatile   organic  compounds)   subject  to
regulation.  Some VOC sources are subject to immediately effective regulations
or  compliance  schedules  under Part D, while  others  will not  be  subject  until
the  1982 or  1987  attainment dates.   A large  part of our  future stationary
program  could  be  directed  towards  VOC  sources  and  it   will  require  a
substantial  effort  to establish  state and regional programs  to address these
sources.   VOC  sources will  need particular  attention  because  many  could  be
"initial compliance" problems.

    It  is  important for  us to  have  a  complete  inventory  of  Class Al  VOC
sources  (sources emitting  100  t/yr or  more actual  or  potential controlled
emissions),  and  it  appears  that  CDS is not yet complete.   Discussions with
regional otaff  over the past several  months  indicate  that CDS  inventories  of
VOC  sources  could be significantly  improved.  Estimates vary  on the number of
VOC  sources  nationally.   A  recent  PEDCO study .estimates  that  there  are 5400
Class A VOC sources; however, CDS shows only  3900.

    At  least one region has responded to the increase  in subject VOC sources
by  placing more  program emphasis on  these  sources.  Region  V has  written a
"Strategy"  for VOC  sources  and has  given  guidance to  their  states  to assist
them in building VOC  inventories  and establishing  procedures for effectively
monitoring the compliance of  these sources.

    Surveillance  of  VOC  sources   requires  a  different  approach  than  the
traditional compliance investigations we have been  doing.   Rather than relying
on  add-on controls  to achieve compliance,  the  general  trend  in regulation of
VOC  sources has  been  towards  the  development  of  substitute  materials  and
processes.   In. addition,  the  use  of  bubbles  and  longer  averaging periods,
prevalent  in  VOC regulations,  often  require  more extensive  record-keeping.
Surveillance  programs will  have  to  be  adapted to accomodate  these changes.
Both State and  federal  inspectors  will  have  to  learn about  new  industrial
processes  and  how  to  use  new  analytical   instruments.  The large  number of
minor VOC  sources will  require changes  in  surveillance  programs  at ,the stata
level.

     I encourage you  to focus  more attention on VOC sources:

     (1) Of  primary   importance   is   ensuring that  CDS  contains  a  complete
         inventory of Class Al VOC  sources.


                                      -125-

-------
                                                       EFFECTIVE:   June 1,  1984
    (2) The regions should  also  work closely with the states to assist them in
        building  inventories  of  VOC   sources   and  establishing   adequate
        compliance monitoring procedures.

    (3) Training of  personnel in  surveillance  techniques is  another priority
        task.

    I  would  be  interested  in hearing about  the progress  you  have made  in
addressing VOC  sources and  any  particular technical  or  programmatic problems
you have encountered in working in this area.
                                      -126-

-------
                                                       EFFECTIVE:  June 1, 1984
DATE:     October 30, 1980

SUBJECT:  Definition and Guidance  for CDS Actions Identified for Headquarters'
          Use.

FROM:     Director, Division of Stationary Source Enforcement (EN-341)

TO:       Lance C. Vinson
          Director, Enforcement Division, Region VII

          .RoxAnn Varzeas
          CDS Coordinator, Region VIII


    After  reviewing  regional  responses  (see Attachment 1)  to  our request for
regional  actions  equivalent  to those  identified  for Headquarters'  use (March
17,  1980  "Conversion Tape Memo"),  it  is  clear that  definitions and guidance
for  the  use  of  certain  action  types  are needed.   Therefore,  a  list  of
enforcement  actions  and appropriate definitions and guidance  are listed below
for your  evaluation, comparison, and comment.

    Headquarters' interest in  these actions  is  based on a wide  range of uses.
The  effort is necessary  for the management of stationary  source air programs
subject to the Clean Air Act as well as providing a  basis  for  program planning
and  budgeting.   The conversion  tape  will facilitate  statistical totalling of
actions taken by  the states  and regions, and will also  provide (by specifying
retrieval  criteria)  a  categorial breakdown of action  types  by industry (power
plant,  iron  and  steel,   etc.);   ownership  (industrial,   state,  federal,
municipal);  initiator  (EPA,  State);  and  dates  (initiated,   completed).   In
addition,  it will inform  the Assistant  Administrator for  Enforcement  of the
progress  of  the  additional   program,  areas  where delays  occur,  the  need for
additional "planning strategies.and shifting of resources.

    For these  reasons,  we  urge you to consider each definition carefully.  If
an  action^ does  not meet  the  definition well,  we would  appreciate  a brief
explanation  to  clarify  the  difference.   The  following   list  contains  the
definitions  of the actions identified for Headquarters' use:

    1.  Case  Development  Inspector  -  Any federally conducted site visit by EPA
        or  its  representative (contractor)  intended to  be  used  to  initite or
        support  ah enforcement  action.   This includes  an  inspection pursuant
        to  a  citizen's  complaint  or  congressional  request,  but  does  not
        include conducting or  observing an official stack test.

    2.  State  Inspection  -  A  site  visit  performed  by  a  State  or  its
        representative  to  determine or verify  the  compliance of  all emission
'        points   at   a   source   with   applicable   state   and   federal   air
        requirements.   It  does  not   include  conducting or  observing  a stack
        test by approved EPA  reference methods.
                                     -127-

-------
                                                   EFFECTIVE:   June 1, 1984
3.  Overview Inspection  -  Any federally conducted site  visit to  a  source
    reported by  the  State  to be in compliance for all regulated pollutants
    and  aemission  points  for  the  purpose   of  confirming  compliance,
    irrespective of  the inspection  result.   Any other  federal  site visit
    for  any  other purpose,  except stack  testing,  is  a case  development
    inspection.  Any  overview inspection which results in the discovery of
    a  violation  is  still  coded  in  CDS  as   an   overview  inspection.
    Subsequent site visits would be coded as case development inspections.

4."  NOV  Issued  -  A notice  sent  by  EPA or  the  State  pursuant  to  the
    authority  granted under  Section 113  of  the Federal  Clean  Air  Act
    Amendments of  1977  or  similar State authority,  informing a source that
    a violation of an applicable federal or state regulation has occurred.

5.  State Administrative Order - A State administrative  action (other than
    a  civil  or  criminal  "action)  against  a  source  pursuant   to  state
    authority that is not federally enforcable.

6.  Civil  Action -  Steps  planned and  taken  by  EPA  of  the  State  before
    referring  a  litigation  report  to  DSSE  pursuant  to   the  authority
    granted  under  Section  113(b) of the Federal  Clean Air  Act  Amendments
    of  1977  or similar State authority for violating  applicable federal or
    state  regulations.

7.  Criminal Action  - Steps planned and taken  by EPA or the State  before
    referring  a  litigation  report  to  DSSE  pursuant  to   the  authority
    granted  under  Section  113(c) of the Federal  Clean Air  Act  Amendments
    of  1977  or similar State authority for violating  applicable federal or
    state  regulations.

8.  EPA  113(a)(l) SIP Order Issued - An administrative order  issued  by EPA
    pursuant  to  the  authority  granted  under  Section  113(a)(l)  of  the
    Federal Clean Air Act Amendments of 1977.

9.  EPA  113(a>(3) Non-SIP Order  Issued  - An  administrative  order  issued by
    EPA  pursuant to  the authority granted under Section 113(a)(3)  of the
    Federal Clean Air Act Amendments of 1977.

10. EPA  113(a}(5) Stop Construction Order  Issued  -  An administrative order
    issued  by  EPA  pursuant   to  the authority  granted   under  Section
    113(a)(5)  of the  Federal  Clean Air  Act Amendments  of  1977.

11. EPA  113(d)(l)  Delayed Compliance  Order  Issued  -  An   administrative
   . order  issued by EPA and  promulgated in  the  Federal Register pursuant
    to  the authority granted under Section  113(d)(l)  of the Federal Clean
    Air  Act  Amendments of  1977.

12. 113(d)(2)  Delayed  Compliance Order  Issued  - An administrative order
    issued by the  State and approved  by EPA  pursuant to  the  authority
    granted   under  Section  113{d)(2)  of   the   Federal  Clean  Air  Act
    Amendments of  1977.
                                  -128-

-------
                                                   EFFECTIVE:   June  1,  1984
13.  113(d)(3)  Replacement/Shutdown Order  Issued - An administrative  order
    issued  by  EPA  or  submitted by  the   State,   approved  by  EPA  and
    promulgated in the  Federal  Register pursuant to the authority granted
    under Section 113  (d)(3)  of  the  Federal Clean  Air  Act Amendments  of
    1977.

14.  113(d)(4)  Innovative Technology Order Issued -  An administrative  order
    issued  by  EPA  or  submitted by  the   State,   approved  by  EPA  and
    promulgated in the  Federal  Register pursuant to the authority granted
    under Section 113  (d){4)  of  the  Federal Clean  Air  Act Amendments  of
    1977.

15.  113(d)(5)   Coal  Conversion  Order  Issued  - An  administrative  order
    issued  by  EPA  or  submitted by  the   State,   approved  by  EPA  and
    promulgated in the  Federal  Register pursuant to the authority granted
    under Section 113  (d)(4)  of  the  Federal Clean  Air  Act Amendments  of
    1977.

16.  Primary 119  Smelter Order  Issued - An administrative  order  issued by
    EPA or  submitted by the  State approved by EPA  arid  promulgated in  the
    Federal Register pursuant to the authority granted under Section  119
    of the Federal Clean Air Act Amendments  of  1977.

17.  Source Test Conducted - An EPA or a State representative has  conducted
    an  actual  measurement  of  emissions  at   the   point   of  release  for
    regulated  pollutants  within a facility,  using  EPA-approved  reference
    methods.   (Success  or  failure should be indicated by the results  code,
    and  the completion  of the  action indicated by  entering the  date  the
    test was finished in the date achieved (DTAC) action type.)

18.  Source Test Conducted  -  An EPA or  a  State  representative  has observed
    the  performance  of  a source  test  by  the   owner  or  operator  using
    EPA-approved reference methods.

19.  Certification  of  Compliance  -  Any  EPA  or  State  ascertainment  of
    compliance by methods other than an inspection  or source  test, usually
    by  source  supplied information.   Other methods  may   include visible
    emissions  observationa,  "windshield  inspections"  and  similar  less
    comprehensive or reliable compliance determination methods.

20.  Referred to  DSSE - A litigation  report has been prepared by the Region
    to  initiate  a  civil or criminal  action  against a  noncomplying source
    and   sent   to   tee  Division  of  Stationary  Source  Enforcement  for
    evaluation.

21.  PSD  Application  Complete -  The   owner of  the  proposed new  source  or
    existing   source  to  be  modified,  subject   to   the   Prevention  of
    Significant  Deterioration  regulations,  submits an  application  which
    contains  all  the information necessary  for  orocesing  the application.
    Designating an application  complete for purposes of permit processing
    does  not preclude additional  information.
                                 -129-

-------
                                                       EFFECTIVE:   June  1,  1984
    22.  PSD  Preliminary  Determination  -  The  permit  application  has  been
        processed  by  the  reviewing  authority,  and  the  proposed  approval/
        disapproval of  a  permit  is  announced  in  the  Federal  Register  and
        opened to public comment.

    23.  PSD Permit  Issued - A final  determination  to issue a permit  has  been
        made by the reviewing authority and the permit is issued to the owner.

    24.  Offset Determination - The  proposed new source  or  existing source  to
        be  modified  or   reconstructed,   subject   to  EPA's  Emission  Offset
        Interpretative  Ruling,   details   a   plan   for  obtaining   emission
        reductions  from  existing  sources  that are  more  than equivalent  to
        offset its new  emissions.   The reviewing agency will  examine  the  plan
        as  part   of  the   NSR   permit  review  process   to   determine   its
        acceptability. (Use the results code to indicate the acceptance  of the
        proposed  offset  plan.   The  date  approval/disapproval is  determined
        shoulkd be entered 'in the date achieved (DTAC) action type.)

    25.  NSR  Preliminary  Determination  -  The  permit  application  has  been
        processed  by  the  reviewing  authority,  and the  proposed  approval/
        disapproval  of  a  permit is  announced  in  the  Federal  Register  and
        opened to public comment.

    26.  NSR Permit  Issued - A final  determination  to issue a  permit  has  been
        made by the reviewing authority and the permit is issued to the owner.

    27.  EPA Review of MSR  Permit -  The proposed State issuance  of a  permit is
        reviewed by EPA to ensure that all federal requirements are  met.   The
        Date Achieved (DTAC) should indicate when the  EPA review is completed.

    When  EPA  or the  State issues  a  new source-related  permit, the  owner  or
operator  of a  proposed  new source  or  existing  source to be  modified  must
inform the appropriate reviewing authority of the following actions:

    28.  New Source  Commence Construction - EPA yr  the State  receives notice
        that the  owner  or operator of a proposed new source or existing source
        to  be  modified  has undergone a  continuous  program  of  construction or
        modification,  or  that  an  owner  or  operator  has  entered  into  a
        contractual obligation to  undertake and complete, within  a reasonable
        time,  a  continuous  program  of construction  or  modification.  Please
        note   this   action   is   differentiated   from   "Start   Construction/
        Modification  (Increment  3)" associated with violating existing sources
        on compliance schedules.

    29.  New Source  Start-up - The owner  or operator  of a  proposed new source
        or  existing source  to  be modified sets the  facility  in operation for
        any purpose.
                                      -130-

-------
                                                       EFFECTIVE:  June 1, 1984
    The  statutorily-established period  of  time fir  issuing NESHAP  wivers  to
sources emitting  currentlu regulated pollutants  has  expired.   Therefore,  all
NESHAP  sources   except   those   asbestos  sources  subject  to  Work  Practice
Standards  shold  be  in compliance  achieved  and  maintained,  shutdown.   Only
historic waivers  should be listed in CDS.

    Compliance  schedule   increments   if  progress   should  be  monitored  for
adherence to enforcable dates agreed to by the regulatory agency.   Each of the
following schedule  increment  action types (if applicable) should be entered in
CDS with an appropriate compliance date to track schedule progress  (DTSC),  and
the actual date compliance with the increment is verified (DTAC).

          Submission of Final Control Plan (Increment 1)
          Binding Commitment to Purchase Control Equipment (Increment 2)
          Start Construction/Modification (Increment 3)
          End Construction/Modification  (Increment 4)
          Final Compliance (Increment 5)

    These   definitions    have    been   provided   to   reduce   any   further
misinterpretation.   Moreover,   please   alert  Headquarters   to  any  special
procedures or  selection  criteria necessary to make complete  retrievals on the
above listed enforcement actions.

    In  regard  to your response  to  the March  17,  1980  memo  and subsequent
telephone  conversation,   are the   case  development  and overview  inspections
currently being conducted  tracked  in  CDS?  If so, what  action  types  are used?
Also,  Region  VIII  has not  differentiated  dually-coded actions  as requested.
When separating  dually-coded actions, please create a  new  action  type  if one
does not  exist and modify the action description.  All historical dually-coded
actions  can  remain unchanged.   Headquarters will note  that discrepancy when
performing  future  retrievals of  these  historical  actions.  However,  please
code all  future actions  using the  newly separated  action types.  Furthermore,
the following action types from your  response need clarification.

        52 - EPA  Inspections

        Are these inspections case  development inspections?

        X4 - State  113(d)  SIP DCO submitted to EPA

    Your  response informed us that this action is considered equivalent  to the
Headquarters action type  113(a) SIP  Order.   Section  113(a)  relates to issuing
an  administrative order  for  a  violation of  any  requirements  of an applicable
SIP  requiring  the  source  to comply  or face a  civil action.   Section  113(d)
relates  to  issuing an  administrative   order  which  specifies  a schedule  and
final date for attaining compliance  for any source  unable  to  comply  with an
applicable  SIP.   These   actions are not  equivalent  and  should  be  tracked
separately.

        X5 - State  113(d)  Replacement DC Order Approved by EPA
                                     -131-

-------
                                                       EFFECTIVE:  June 1, 1984
    Your response  informed  us that this action is considered equivalent to the
Headquarters action type 113{a)(3) Order Issued.  Section  113(a)(3)  relates to
issuing an  administrative order for a violation of Sections 111 (new sources),
112  (NESHAP)  amd  114  (inspections)  requiring  a  source to comply  or face  a
civil  action.   The supart  in Section 113(rt)  referring  to replacement delayed
compliance orders  is not equivalent to a 113(a)(3) order and  should  be tracked
separately.

    To stress  again,  the conversion tape effort does not entail any changes in
coding  practice   by  any  region  or  state   other  than   for  those  actions
dually-coded or where a  regionally equivalent action type currently does not
exist.  After  comparing  these definitions  to  your previous  responses,  return
the  reassessed action types  to DSSE by November 21, 1980 (use Attachment 2).
Any  questions  regarding the  above should  be  directed to Howard Wright  (FTS
755-0103) or Debra Favre (FTS 755-79827).
                                      -132-

-------
                                                       EFFECTIVE:  June I. 1984
DATE:     Setember 15, 1982

SUBJECT:  Significant Violator Tracking Using CDS

FROM:     Director
          Stationary Source Compliance Division

TO:       Directors, Air  & Waste Management Divisions, Regions II-IV, VI, VIII
          and X

          Directors, Air Management Divisions, Regions I, V and IX


    One  of  the  objectives  of  the  Administrator's  Management  Accountability
System  (MAS)  is  that resources  be used  to address  significant  air violators
and  return  them  to  compliance.   A  significant violator  was defined  in the
Kathleen  M.  Bennett  memorandum  December  29,  2981  and  further  guidance
presented  in another  Bennett memorandum dated June  24,  1982.   As  a result,
significant  violators have been  identified by all  regions and  lists  sent to
Headquarters.  Progress  on bringing these  sources back into compliance will be
reported to  the Administrator under the MAS.

    Compliance data  about  significant violators are  required  by  the MAS to be
reported  on a  quarterly  basis.   To  minimize  the  reporting burden  and more
easily maintain a historic  record of events  associated with these violators as
they  are  brought  back   into  compliance,  the  Administrator has  designated
Compliance   Data  System   (CDS)  as   the   stationary  source  air  enforcement
reporting  system  for the MAS.  Therefore,  pertinent  information on significant
violators shall be  transmitted to and retrieved  through CDS.   It is essential
that  such  information  be  compiled  and entered  in a  timely,  reliable and
expeditious  fashion.  Due to the weekly  update  cycle of CDS, these  goals can
all  be  achieved.   However, some  information in CDS on significant violators is
in  need  of enhancement   before  both   reporting  to the  MAS  and  tracking
instructions as  to  when, how, and  what  to report through CDS on these sources
are outlined below.

    To  facilitate  identifying significant violators,  SSCD  has developed a new
source-specific  code  in  CDS to flag   these  sources.    The code  identifies
significant  violators by  the acronym "SVIO."   Its  values  indicate  the  lead
enforcement  agency  responsible  for  bringing the  source   back  to compliance.
The values are:

        B =  Joint EPA/State action

        E =  EPA action

        S  =  State action
                                      -133-

-------
                                                       EFFECTIVE:   June 1, 1984
    Such  flagged sources can  be retrieved using  "SVIO" as  the  sole selction
criterion.   At  present,  only  Headquarters  can  flag  sources  identified  as
significant  violators.   However,  others can  retrieve such data  using  "SVIO"
code.

    The  following source-specific  information must  be maintained  in CDS  on
each significant violators:

            Information Type                     CDS CODES

            Source Size                          CLAS
            Air  Program                          APCD
            Source Compliance Status             SCMS
            Pollutant                            PLLT, PUTT
            Pollutant-Specific                   PCMS, CMST
              Compliance Status
            Enforcement Action                   ATPE
            Date Action Scheduled                DTSC
            Date Action Achieved                DTAC
            Comments                             	
             (as  may be appropriate)

Please  note  this is consistent  with  the John  Rasnic March 10, 1982, memorandum
concerning tracking significant  violators by pollutant (see attachment).

     It  is required  that  all  information  applicable  to  the  entire  source  be
entered at  the  source  level  (PTNO  M  000).   Any  other data  or enforcement
actions should  be  entered only at  the  appropriate  emission  point.   Do not
enter  the  same  data  at  both  the  source  level  and  point level  for a  given
source.   Redundant data  will  only  introduce  confusion and  necessitate  your
providing additional clarifying information.

In  order to track progress  on these sources,  the appropriate information must
be  entered  in timely manner  into  CDS.   This means the  information on sources
should   be   entered  on  the  first  weekly update, following  the  end  of the
quarter.    Because  of  this   time  frame  (necessitated   by   MAS   reporting
requirements),   flow  of  such  information from   the  State  and/or  EPA  field
personnel to  the regional  CDS manager must  also be timely.
                                      -134-

-------
                                                       EFFECTIVE:   June 1, 1984
10.0 USER COMMUNICATIONS




     In order to  derive  full  benefit from the use  of CDS, users must be  able




to receive answers  to  their problems or questions  as quickly as possible.  To




assist the CDS  User,  a  number of  common types  of  cummunication are  listed




below.








10.1 EPA Policy and Enforcement Matters




     For questions on EPA policy and enforcement matters,  users  should contact




EPA SSCD, Howard Wright, Chief of Compliance Section.








10.2 Enhancements or Modifications to CDS




     For  any user  communications,   new  features,   system  revisions,  the  CDS




Newsletter will  be produced on a quarterly  basis  and sent to CDS users.   Any




questions resulting from new  features  should be addressed to  either  EPA SSCD,




Franklin  C.  Smith,  CDS Data  Base  Coordinator,  or  to  the  CDS  Operation and




Maintenance Support Contractor, TRC Environmental Consultants, Inc.








10.3 Technical DP




     For   any   communication   dealing   with   Technical   Data   Processing




applications,   programming,   system   specification   changes,    minicomputer




interface  packages,  users  should  contact  their   regional  Data  Processing




Manager  (for minicomputer  applications)  or  the  CDS  Operation and Maintenance




Support Contractor, TRC Environmental Consultants,  Inc.
                                     -135-

-------
                                                       EFFECTIVE:   June 1,  1984
10.4 User Training




     For  training in  use of  CDS  or WYLBUR, users  should contact EPA  SSCD,




Franklin C. Smith, CDS Data Base Coordinator.
                                      -136-

-------
                    EFFECTIVE:  June 1, 1984
APPENDIX'.

-------
                                                       EFFECTIVE:  June 1, 1984
                            DATA ELEMENT DICTIONARY
Page
A-l
A-3
A-5
A-6
A-7
A-8
A-9
A-10
B-l
B-2
B-3
B-4
B-5
B-6
B-7
B-8
B-9
C-l
C-2
C-3
C-4
C-5
C-6
C-7
C-8
C-9
C-10
C-ll
 D-l
 D-2
 D-3
 D-4
 D-5
 D-6
 D-7
 D-8
 D-9
Data Element
A. COMMON TO ALL CARD TYPES 1-8

Region
State
County Code
Source Number
Emission Point Number
Action Number
Card Code
Update Code

B. SOURCE LEVEL - CARD 1

Air Quality Control Region
City Code
Source Name
Street Address
Regional Data Element 1
Regional Data Element 2
Regional Data Element 3
Regional Data Element 4
Regional Data Element 5

C. SOURCE LEVEL - CARD 2

City Name
Zip Code
State Registration Number
NEDS Cross-Reference Number
SIC Code
Priority Code
Government Facility Code
Air Program Code
Air Program Status
Regional Data Element 6
Staff Personnel Code-Source

D. SOURCE LEVEL - REPEATING POLLUTANT CARD 3

Penalty Issue Addressed Indicator
Pollutant ID
Pollutant Delete Flag
Pollutant Compliance
Regional Data Element 14
Pollutant Classification
Pollutant Air Quality Control  Indicator
Pollutant Loading
Facility Capacity
Abbr.
REGN
STTE
CNTY
SRCE
PTNO
ANUM
AQCR
CYCD
SNME
STRT
RDE1
RDE2
RDE3
RDE4
RDE5
CYNM
ZIPC
STRG
NEXS
SICC
PRIO
FEDF
APCD
APST
RDE6
PERS
PISA
PLLT
DROP
PCMS
RD14
PCLS
PAQC
LOAD
FCAP

-------
                                                       EFFECTIVE:   June 1,  1984

                      DATA ELEMENT  DICTIONARY  (Continued)

Page    Data Element                                        Abbr.

D-10    Regional Data Element 9                             RDE9
D-ll    Regional Data Element 10                            RD10
D-12    Regional Data Element 11                            RD11
D-13    Regional Data Element 12                            RD12
D-14    Source Classification Code                          CLAS
D-15    Loading Derivation Code                             LDRC

        E. POINT LEVEL - CARD 5

E-l     SCC Code                                            SCC3,
                                                          SCC6, SCC8
E-2     Capacity Code                                       CAPC
E-3     Compliance Status                                   CMST
E-5     SIP Code                                            SIPC
E-6     Pollutant Code                                      PLUT
E-7     State Regulation                                    SREG
E-8     Regional Data Element 15                            RD15
E-9     Process Description                                 PRDS
E-10    Multiple Cross-Reference                            MULT
E-ll    Regional Data Element 7                             RDE7
E-12    Procedural Compliance                               CMS2

        F. ACTION LEVEL - CARD 7

F-l     Action Description                                  ADES
F-2     Civil Penalty Amount                                PLTY
F-3     Action Type                                         ATPE
F-4     Date Achieved                                       DTAC
F-5     Date Scheduled                                      DTSC
F-6     Action Staff Code                                   PERA
F-7     Results Code                                        STAC
F-8     Regional Data Element 8                             RDE8

        G. COMMENTS

G-l     Line Number
G-2     Comments
                                     A(2)

-------
                                 EFFECTIVE:   June 1,  1984
A.  COMMON TO ALL CARD TYPES 1-8

-------
                                                       EFFECTIVE:   June  1,  1984

                                                                        REGION

Definition:  REGION is a two-position numeric region identifier.

Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
REGN
1-8
1-2
2
NUMERIC
LEFT
YES
YES
Valid Values:
01 through 10

See attachment showing the region
locations and the states associated
with each region.


Masterfile 2Q_47
Record Type
Masterfile ^_2
Position
Masterfile -
Length




 Edit Error Messages:

  ***INVALID REGION CODE

 *** = Fatal Error
* = Warning Error
 Coding Considerations;

   Region must  be present on  all input transactions.   State code  and  region
   are cross-validated;  the  user  may not use a  state  code which is  not  valid
   for his region.

   Region cannot  be  changed or blanked  out once it has been put on  the  data
   base.   If it  must  be  changed,  the  entire  source  must be  deleted  and
   reentered with the correct region code.
                              CDS DATA DICTIONARY

                                      A-l

-------
                                                   EFFECTIVE:   June  1,  1984
                              REGION CODE
           States have been assigned to regions as follows:
Region
                  States
01-Boston
Connecticut,  Maine,   Massachusetts,   New   Hampshire,
Rhode Island, Vermont
02-New York
New Jersey, New York, Puerto Rico,  Virgin Islands
03-Philadelphia     Delaware,     District     of    Columbia,     Maryland,
                    Pennsylvania, Virginia, West Virginia
04-Atlanta
Alabama,   Florida,   Georgia,  Kentucky,   Mississippi,
North Carolina, South Carolina, Tennessee
05-Chicago
Illinois, Indiana, Michigan, Minnesota,  Ohio,  Wisconsin
06-Dallas
Arkansas, Louisiana, New Mexico, Oklahoma, Texas
07-Kansas City      Iowa, Kansas, Missouri, Nebraska
08-Denver
Colorado,  Montana,  North  Dakota,  South Dakota,  Utah,
Wyoming
09-San Francisco    Arizona,  California,  Hawaii,  Nevada,  Guam,  American
                    Samoa, Trust Territories
10-Seattle
Alaska, Idaho, Oregon, Washington
                          CDS DATA DICTIONARY
                                  A-2

-------
Definition:
                                          EFFECTIVE:   June 1,  1984

                                                            STATE

STATE is a  two-position  numeric state code.  The State  codes  are
derived from  the  Storage and Retrieval  of  Aeromeric Data  Manual
(SAROAD) published by OAQPS.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
SITE
1-8
3-4
2
NUMERIC
LEFT
YES
YES
Valid Values:
01-56
See attached showing the states
associated with each state code.



Masterfile 20-47
Record Type *u-«i/
Masterfile - .
Position
Masterfile _
Length
 Edit Error Messages:

  ***INVALID 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 data  base.   If
   it must  be changed, the entire  source must be  deleted and reentered  with
   the correct state code.
                              CDS DATA DICTIONARY

                                      A-3

-------
                                               EFFECTIVE:   June 1,  1984
                          STATE CODE

The CDS system uses the following two-digit SAROAD  state  codes:
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Alabama
Alaska
Arizona
Arkansas
California
Colorado
Connecticut
Delaware
District of Columbia
Florida
Georgia
Hawaii
Idaho
Illinois
Indiana
Iowa
Kansas
Kentucky
Louisiana
Maine
Maryland
Massachusetts
Michigan
Minnesota
Mississippi
Missouri
Montana
Nebraska
Nevada
New Hampshire
                                         31     New Jersey
                                         32     New Mexico
                                         33     New York
                                         34     North Carolina
                                         35     North Dakota
                                         36     Ohio
                                         37     Oklahoma
                                         38     Oregon
                                         39     Pennsylvania
                                         40     Puerto Rico

                                         41     Rhode Island
                                         42     South Carolina
                                         43     South Dakota
                                         44     Tennessee
                                         45     Texas
                                         46     Utah
                                         47     Vermont
                                         48     Virginia
                                         49     Washington
                                         50     West Virginia

                                         51     Wisconsin
                                         52     Wyoming
                                         53     American Samoa
                                         54     Guam
                                         55     Virgin Islands
                                         56     Trust Territories
                       CDS  DATA DICTIONARY

                              A-4

-------
                                                       EFFECTIVE:   June  1,  1984

                                                                   COUNTY CODE
Definition:  COUNTY  CODE  is  a  four-digit  numeric  county  identifier.
             county codes are derived from the SAROAD manual.
                                  The
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
CNTY
1-8
5-8
4
NUMERI C
LEFT
YES
YES
Valid Values:
All county codes must be present on
the CDS County Code/AQCR Table.

s

Masterfile 20-47
Record Type
Masterfile .
Position
Masterfile ,
Length
 Edit Error Messages:
 *** = Fatal Error
* = Warning Error
 Coding Considerations;

   Please  contact  the National  DEC  to update  the county  code file.   County
   code must be  present  on all transactions; it  cannot  be changed  or  blanked
   out on the data base.
                              CDS DATA  DICTIONARY

                                     A-5

-------
                                                       EFFECTIVE:  June 1, 1984

                                                                SOURCE NUMBER
Definition;  SOURCE NUMBER is a five-digit numeric facility identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
SRCE
1-8
9-13
5
NUMERIC
LEFT
YES
NO
Valid Values:
All numeric values.




Masterfile
Record Type
Masterfile
Position
Masterfile
Length

20-47
9-13
5
 Edit Error Messages:

  ***SOURCE NUMBER MUST BE NUMERIC

 *** = Fatal Error
Warning Error
 Coding Considerations;

   The NEDS  source numbering convention may be used when  adding  a  new source.
   Otherwise,  assign  the  next  highest sequential  source  number  within  the
   county.   Usually,  the last  four  digits  of  source  number are  the  same as the
   NEDS Source  Identifier.   The  first  digit must  correspond to  the  Air Program
   Code.   Sources subject to  several  Air  Program' Codes  must be entered with
   separate  source  numbers,  one  for each program such as SIP, NSPS,  etc.
                              CDS DATA DICTIONARY

                                      A-6

-------
                                                       EFFECTIVE:   June 1,  1984

                                                         EMISSION  POINT NUMBER

Definition:  EMISSION  POINT  NUMBER  is a  three-digit numeric  emission  point
             identifier.   If  one  physical  emission  point  produces  several
             pollutants, each  pollutant is  assigned a separate emission  point
             number.  Emission point 000 refers to the entire source.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
PTNO
1-8
14-16
3
NUMERI C
LEFT
YES
NO
Valid Values:
000 through 999




Master file
Record Type
Masterfile
Position
Masterfile
Length

20-47
14-16

 Edit Error Messages:
  ***EMISSION POINT MUST BE ZEROS
  ***POINT MUST BE GREATER THAN ZERO
  ***DO NOT DELETE POINT 000
 *** = Fatal Error	* = Warning Error	

 Coding Considerations;

   When a card  type 1 is entered  as  a new transaction, an emission  point  000
   is generated  by the system;  however,  it is  possible  to enter  an emission
   point 000 as a new transaction at the same time  a  card  type  1  is entered as
   new.

   Point number  must be zero for  card types  1, 2,  and 4.  it may be greater
   than zero  for  cards 5, 6, 7, and  8.  An emission point cannot  be added to
   the data base as new unless a card  type  1 has been entered at  the same time
   or at a previous time.

   Point 000 cannot be deleted unless  the  source itself is deleted  with a card
   type 1.

   If  possible,   the  first  two  positions  of   the  CDS  emission  point  should
   correspond to  the  NEDS emission point; the  third  position can be pollutant
   specific.  For  example,  if  a  boiler has a NEDS point number of  02,  the  CDS
   point number  020  could  represent   the  particulate emissions  and  point  021
   could represent  the SO2 emissions.

                              CDS DATA DICTIONARY
                                      A-7

-------
                                                       EFFECTIVE:   June  1,  1984

                                                                 ACTION  NUMBER.

Definition:  ACTION NUMBER is a two-digit numeric sequential  action identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
A HUM
1-8
17-18
2
NUMERIC
LEFT
YES
NO
Valid Values:
00 through 99




Master file
Record Type
Master file
Position
Masterf ile
Length

20-47
17-18
2
 Edit Error Messages:

  ***ACTION NUMBER MUST BE ZEROS
  ***ACTION NUM MUST BE GREATER THAN ZERO

 *** = Fatal Error
Warning Error
 Coding Considerations:

   Actions  should be assigned sequentially starting with  01.   When adding new
   actions  to  the data base,  code 99; the system  will  convert the 99  to the
   next  highest sequential action number for  that  emission  point.   If several
   actions  and  action  comments  are entered  at  the same time  with Action Number
   99,  comments  will  not  be  associated with  the  proper action.   Therefore,
   users  must  not enter  multiple actions  and  comments  with Action Number 99
   simultaneously since these will produce  rejects  on  the Update Report.

   An action number  cannot  be  added  to the  data base unless  the emission point
   for  that action is also being added or  it already  exists  on the data base.
   Each action  number  must  be associated with an  emission point.

   Action number must be 00 for  card  types  1 through  6;  it  must  be greater
   than zero for card  types 7 and 8.

   Action numbers should have  no special meaning.  Action  number  ranges must
   not be used  to identify  certain types of actions.
                              CDS DATA DICTIONARY

                                      A-8

-------
Definition:
                                          EFFECTIVE:   June 1,  1984

                                                        CARD CODE

CARD CODE is  a  one-digit numeric field which  identifies  the  type
of fixed format information found on the CDS input punch card.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Valid Values:
1 = Source record.
2 = Source record.
3 = Pollutant record.
4 u SouLCe COflUltei'iL.
5 = Emission point record.
6 = Emission point comment.
7 = Action record.
8 = Action comment.
££ NIMERIC
Justified
Required on Y£S
New Entry
Nationally „
Controlled
Master file
Record Type
Masterfile
Position
Masterfile
Length
 Edit Error Messages:
  ***INVALID CARD CODE

 *** o Fatal Error
                             * = Warning Error
 Coding Considerations;
                              CDS DATA DICTIONARY

                                      A-9

-------
                                                       EFFECTIVE:  June  1,  1984

                                                                  UPDATE CODE

Definition;  UPDATE CODE tells the  update program  to  add,  change, or delete a
             transaction.  This data element  is  not carried on the masterfile
             but serves to tell the Update  Program what  to do with other  data
             on the input transaction.
 _ .  .    ,                                Valid Values:
 Retrieval
 Abbreviation	   N = New

 Card                   ,                 C = Change
                        A—o
      	   D = Delete
                        80
 Columns

 Data Element
 Length

                                          Masterfile
 Justified          	Record Type
 Required on                              Masterfile
 New Entry	Position
 Nationally                               Masterfile
 Controlled	Length
 Edit Error Messages:
  ***UPDATE CODE D INVALID FOR CARD TYPE 2 & 3
  **'INVALID UPDATE CODE
  ***DO NOT DELETE POINT  000
  ***NO DATA IN COL 21-79 FOR DELETES
 *** = Fatal Error	* ** Warning Error	

 Coding Considerations;

   The  CDS-EDIT only  validates  the existence  of  the update  code;  it  is  the
   Update Report which points out incorrect or illogical update codes.

   Each card type,  except card  type 2, has a corresponding  record  type  on the
   CDS data base.   If a card type 1, 4, 5, 6, 7, or  8 has  not already created
   a masterfile  record  type,  it must be added as New.   Each point,  action, or
   comment  record must  be associated with a corresponding source record.  Each
   point  comment  must  be  associated with  a  point.    Each action  must  be
   associated  with  a point.  Each  action comment  must  be  associated with an
   action.

   Key  data   elements   (region,  state,  county,  source,  point,  and  action
   numbers) cannot  be changed.   Other data elements can be  changed  by using
   the  update  code  'C'.  Only those  record  types which  have been successfully
   added  as new prior  to this  update  cycle  can be  changed.  Only  those data
   elements  which are  actually  being  changed need  to  be  added on  a  change


                              CDS DATA DICTIONARY
                                     A-10

-------
                                                      EFFECTIVE:   June 1,  1984

                                                                  UPDATE CODE

Coding Considerations; (Continued)

  transaction.  By  coding  an  asterisk  anywhere in  a data  field,  that  data
  field will be changed to spaces (date  values will be zeroed out).

  The update  code  'D1 deletes one  or more records on  the  CDS data  base.  A
  card type 1 delete will delete all masterfile records for  a given  source.

  A  card  type  5  delete  will delete a point  together  with all  associated
  comments, actions,  and action comments.  Point 000  cannot  be deleted unless
  a card type 1 is used for the delete function.

  A  card  type 7 delete  will delete  an action together  with all  associated
  action comments.

  A  card  type 4,  6,  or 8  delete  must have a  valid line number.   One delete
  card is needed to delete each comment  line number.

  No data may be punched  in columns 21  through 79 for deletes to protect the
  data base against a mispunched delete  update code.

  A card 2 or 3 delete is invalid.
                             CDS DATA DICTIONARY

                                    A-ll

-------
                            EFFECTIVE:  June 1, 1984
B.  SOURCE LEVEL - CARD 1

-------
                                                       EFFECTIVE:   June 1,  1984

                                                    AIR QUALITY CONTROL REGION

Definition;  AIR QUALITY CONTROL REGION (fQCR)  is a three-digit numeric value.

Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
AQCR
1
20-22
3
NUMERIC
LEFT
YES
YES
Valid Values:
Must be valid for
county codes used
valid. Please co
Code/AQCR Table.


Masterfile
Record Type
Masterfile
Position
Masterfile
Length
the state and the
Blank is also
ntact the central
tQCR to the County
20
21-23
3
 Edit Error Messages:
 *** - Fatal Error
Warning Error
 Coding Considerations;

   The  County Code/AQCR Table  containing  all  valid  AQCR's can  be listed  by
   following  the directions in Chapter 10.
                              CDS DATA DICTIONARY
                                      B-l

-------
                                                      EFFECTIVE:  June 1, 1984

                                                                    CITY CODE
Definition;   CITY CODE  is  a  four-digit  numeric city  identifier.   The  city
             codes can be found  in the  SAROAD manual.
Retrieval CYCD
Abbreviation
Card
Type
Valid Values:
If the field is being used, it should
be a four-digit numeric code found in
the SAROAD manual.
Card
, 23—26
Columns
Data Element .
Length
Data
Type NUMERIC
Justified LEFT
Required on
New Entry
Nationally NQ
Controlled
Edit Error Messages:
*** = Fatal Error
Masterfile 2Q
Record Type
Masterfile _. 27
Position
Masterfile 4
Length
* = Warning Error
 Coding Considerations;

   City codes are  available  from the Storage and Retrieval of Aerometric  Data
   (SAROAD), Volume V.

   SAROAD  Manuals  are  available  on request  from  the  EPA's  office  of  Air
   Quality Planning and standards.
                              CDS DATA DICTIONARY

                                      B-2

-------
                                                       EFFECTIVE:  June  1,  1984

                                                                  SOURCE NAME

Definition:  SOURCE NAME is a 20-position alphanumeric facility  identifier.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
SNME
1
27-46
20
ALPHANUMERIC
LEFT
YES
NO
Valid Values:
All alphanumeric characters.




Masterfile
Record Type
Masterfile 28-47
Position
Masterfile 2Q
Length
 Edit Error Messages:

  ***SOURCE NAME REQUIRED ON NEW ENTRY

 *** * Fatal Error
Warning Error
 Coding Considerations:

   The first position  of  facility  name  must  be filled on a  new  transaction to
   allow   for   source  name   sorting   on   the   retrieval.    Use   consistent
   abbreviations for facilities with the same company name,  i.e.,

                        US Steel - Pittsburgh
                        US Steel - Dayton
                        US Steel - Mansfield

   Abbreviate only when necessary and do not use  words  like  "The" or 'City of"
   as  the first word  in  a  facility name.   If  the  name of  the facility  is
   different from  that of the parent company, enter  the name of the facility
   as  the source name and enter  the name of  the parent  company as  a  source
   comment  (card code 4) .   Most  complete  source names,  addresses, and  SIC
   Codes  can be  found  in  manufacturing  directories published by  state commerce
   departments.   It would  be  wise for  each  region  to develop   a  list  of
   standard facility name abbreviations to be  used consistently  throughout the
   region.  See attached example developed by Region V.
                              CDS DATA DICTIONARY

                                      B-3

-------
Definition:
                                          EFFECTIVE:  June  1, 1984

                                                   STREET ADDRESS

STREET ADDRESS is the actual  location  of  the facility; it is NOT
the Headquarters address.
 Retrieval
 Abbreviation
 Card
 Type
 Card
 Columns
 Data Element
 Length
           STRT
          47-66
           20
 Edit Error Messages:
 *** = Fatal Error
Valid Values:

All alphanumeric characters.
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
ALPHANUMERIC
LEFT
NO
NO

Masterfile
Record Type
Masterfile
Position
Masterfile
Length

20
48-67
20
                             * « Warning Error
 Coding Considerations:

   If  the  mailing  address  of  the  facility  is different  from  the  street
   address,  the  mailing address  can  be coded  on  a  source  comment  record
   (Card 4),  Comment Line  A and  B.   There  are  special  input coding  sheets
   designed for mailing  address information.
                              CDS DATA DICTIONARY

                                      B-4

-------
                                                       EFFECTIVE:  June  1,  1984

                                                       REGIONAL  DATA  ELEMENT  1
Definition;  REGIONAL DATA ELEMENT 1 - user supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
RDE1
1
67
1
ALPHANUMERIC

NO
NO
Valid Values:
All alphanumeric characters.




Masterfile 2Q
Record Type
Masterfile .. Q
Position
Masterfile .
Length
 Edit Error Messages:
 *** - Fatal Error
                 Warning Error
 Coding Considerations;

   Typical usages of this field include identifiers for (as of March 1982)
         Region I
         Region II
         Region III
         Region IV
         Region V
         Region VI
         Region VII
         Region VIII
         Region IX
         Region X
Attainment/Nonattainment, Archiving
State delegation for NSPS, NESHAPS
Attainment/Nonattainment
MSEE Priority Sources
Attainment/Nonattainment
SIP-PSD
Attainment/Nonattainment
Attainment/Asphalt Plants
PSD NSR Applicability
Major Sources
                              CDS DATA DICTIONARY

                                      B-5

-------
                                                       EFFECTIVE:  June 1, 1984

                                                       REGIONAL  DATA ELEMENT 2
Definition:  REGIONAL DATA ELEMENT 2 - user supplied.
 Retrieval
 Abbreviation
 Data Element
 Length
RDE2
Card
Type
Card
Columns
1
68
 Edit Error Messages:
Valid Values:
All alphanumeric characters.
Data
Type ALPHANUMERIC
Justified
Required on
New Entry
Nationally
Controlled °
Mast erf ile
Record Type
Masterfile
Position
Masterfile
Length
20
141
1
 *** = Fatal Error
                  * = Warning Error
 Coding Considerations:

   Typical usages of this field include identifiers for (as of March 1982)
         Region I
         Region II
         Region III
         Region IV
         Region V
         Region VI
         Region VII
         Region VIII
         Region IX
         Region X
     Transitory/Non-transitory
     State Regional Offices
     State/Local Offices
     State/Local Offices
     SO2 Priority status
     NESHAP and PSD Application Numbers
     Not Subject to PSD but under Review
     Vapor Recovery
     Future Effective Permit Processing
     Indian Reservations
                              CDS DATA DICTIONARY

                                      B-6

-------
                                                       EFFECTIVE:  June 1, 1984

                                                       REGIONAL DATA ELEMENT 3
Definition;  REGIONAL DATA ELEMENT 3 - user supplied.
 Retrieval
 Abbreviation
 Card
 Type
 Card
 Columns
 Data Element
 Length	
 Data
 Type
     RDE3
     69
ALPHANUMERIC
                                          Valid Values:
 justified
                       Masterfile
                       Record Type
                                                               20
 Required on
 New Entry
     NO
Masterfile
position
142
 Nationally
 Controlled
     NO
Masterfile
Length
 Edit Error Messages:
 *** = Fatal Error
                           Warning Error
 Coding Considerations;

   Typical usages of this field include identifiers for  (as of March 1982)
         Region I
         Region II
         Region III
         Region IV
         Region VII
         Region VIII
         Region IX
         Region X
          Sources to be Archived
          PSD Status
          MSEE Identifier - State Tracking Information
          Major SIP Sources
          Continuous Monitoring
          Subject to State Audit
          Mobile Sources - Significant violators
                              CDS DATA DICTIONARY

                                      B-7

-------
                                                      EFFECTIVE:  June 1, 1984

                                                      REGIONAL  DATA ELEMENT 4
Definition:  REGIONAL DATA ELEMENT 4 - user supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Valid Values:
RDE4
1
70-74
5
Data
Type ALPHANUMERIC
Justified
Required on
New Entry
Nationally _
Controlled °
Masterfile
Record Type
Masterfile
position
Masterfile
Length
20
143-147
5
 Edit Error Messages:
 *** = Fatal Error
                 Warning  Error
 Coding Considerations;

   If  there  is a  need  to have a  second  SIC Code for  a facility, this  field
   could  be  used  since  it appears  next  to the  SIC  code on  the Source  Data
   Report.   If  this data  element  is used  for  SIC Code,  only the first  four
   positions may be  used;  columns  70-73 must be numeric and column 74 must  be
   blank.

   Other  typical usages of  this field include identifiers for  (as of  March
   1982):
         Region II
         Region III
         Region IV
         Region V
         Region VII
         Region VIII
         Region IX
Enforcement Docket Number,  PSD,  I.D.
Major Bulk Terminal
Additional Staff Codes
SIC Codes - Minnesota
Nebraska Case Numbers
Continuous Monitoring
VOC Numbers
of New source
                              CDS DATA DICTIONARY

                                      B-8

-------
                                                       EFFECTIVE:   June  1,  1984

                                                       REGIONAL DATA ELEMENT  5
Definition:  REGIONAL DATA ELEMENT 5 - user supplied.
 Retrieval
 Abbreviation
 Card
 Type
 Card
 Columns
 Data Element
 Length	
 Data
 Type
     RDE5
    75-79
ALPHANUMERIC
Valid Values:

All alphanumeric characters.
 Justified
                       Masterfile
                       Record Type
                                                               20
 Required on
 New Entry
     NO
Masterfile
Position
148-152
 Nationally
 Controlled
     NO
Masterfile
Length
 Edit Error Messages:
 *** = Fatal Error
                           Warning Error
 Coding Considerations;

   Typical usages of this field include identifiers for (as of March 1982):
         Region II
         Region III
         Region V
         Region IX
         Region X
          Multiple Docket Numbers, Federal Facility Types
          V=Violators
          Indiana Information
          State Cross-Reference Numbers
          Tertiary SIC Codes, Federal Facility Types
                              CDS DATA DICTIONARY

                                      B-9

-------
                            EFFECTIVE:  June 1, 1984
C.  SOURCE LEVEL - CARD 2

-------
                                                       EFFECTIVE:  June 1,  1984

                                                                     CITY NAME

Definition;  CITY NAME gives the location of the facility.
•
Retrieval CYNM
Abbreviation
Valid Values:
All alphanumeric characters.
Card 2
Type
Card 20-34
Columns
Data Element
Length
°ata ALPHANUMERIC
Type
T ,.!*• j LEFT
Justified
Required on
New Entry
Nationally „_
Controlled
Edit Error Messages:
*** = Fatal Error
Masterfile 2Q
Record Type
Masterfile ,.a a_
„ . ,_. 68-82
Position
Masterfile ^5
Length
* = Warning Error
 Coding Considerations;

   If  abbreviations  are  used, they  should  be used consistently  for  all input
   to  facilitate sorting and  retrievals.
                              CDS DATA DICTIONARY
                                      C-l

-------
                                                       EFFECTIVE:   June  1,  1984

                                                                      ZIP CODE

Definition;  ZIP  CODE is  the five-digit  numeric postal  zone of the actual
             location of the facility.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
ZIPC
2
35-39
5
NUMERI C
LEFT
NO
NO
Valid Values:
All numeric values.




Mast erf ile
Record Type
Master file
Position
Mast erf ile
Length

20
85-89
5
 Edit Error Messages:

  *ZIP CODE SHOULD BE NUMERIC

 *** = Fatal Error
Warning Error
 Coding Considerations;

   Code  whenever  possible  for  complete  address  capability  in  the  system.
   Consult  a state  published  manufacturer's  directory  for  accurate name  and
   address  information.
                              CDS DATA DICTIONARY

                                      C-2

-------
                                                       EFFECTIVE:   June 1,  1984

                                                     STATE REGISTRATION NUMBER

Definition;  STATE REGISTRATION NUMBER  is an  alphanumeric  identifier used  by
             the state to identify a facility.
Retrieval
Abbreviation u
Valid Values:
All alphanumeric characters.
Card
Type
Catd 40-54
Columns
Data Element
Length
Data
Type ALPHANUMERIC
Justified LEFT
Required on
New Entry
Nationally
Controlled
Edit Error Messages:
*** » Fatal Error
Masterfile 2Q
Record Type
Masterfile 90_1Q4
Position
Masterfile ,5
Length
* = Warning Error
 Coding Considerations;

   When  the  state  identifier  is consistently  entered into  this field,  CDS
   reports can be sorted in the same way as the state's files are sorted.
                              CDS DATA DICTIONARY

                                      C-3

-------
                                                      EFFECTIVE:  June 1, 1984

                                                  NEDS CROSS-REFERENCE NUMBER

Definition;  NEDS CROSS-REFERENCE NUMBER is  the  NEDS  facility identifier.
 Retrieval
 Abbreviation
     NEXS
Valid Values:

All alphanumeric values.
 Card
 Type
 Card
 Columns
    55-58
 Data Element
 Length	
 Data
 Type
ALPHANUMERIC
 Justified
                       LEFT
                       Masterfile
                       Record Type
                     20
 Required on
 New Entry
     YES
Masterfile
Position
105-108
 Nationally
 Controlled
     YES
Masterfile
Length
 Edit Error Messages:
 *** = Fatal Error
                       * = Warning Error
 Coding Considerations;

   Whenever  a  new facility  is  being  added as New,  this  field must be  coded.
   If  the  NEDS number is not known, please  consult  the AEROS contact in  your
   area  to  get  a  NEDS  facility  number.   AEROS  contacts  are  listed  in
   Appendix B  of this manual.

   For source  numbering  convenience,  the last four positions  of  Source  Number
   should  be  the NEDS  Cross-Reference Number.   If  this method  is used,  the
   first digit of the CDS Source Number should be the Air Program Code.
                              CDS DATA DICTIONARY

                                      C-4

-------
Definition:
                                          EFFECTIVE:   June 1,  1984

                                                         SIC CODE

SIC CODE is the Standard Industrial class Code.   It  refers  to the
primary product produced or service performed by the  facility.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
SICC
2
59-62
4
NUMERI C
LEFT
YES
YES
Valid Values:
All numerics.




Masterfile
Record Type
Masterfile
Position
Masterfile
Length

20
109-112
4
 Edit Error Messages:
  *SIC SHOULD BE NUMERIC
 *** = Fatal Error
                                 Warning Error
 Coding Considerations;

   Since many  retrievals  are  based on industry categories,  it  is  important  to
   code this  field  on a new card  code  2.   If a secondary SIC  code  is needed,
   Regional  Data Element  4 may  be  used.   SIC  codes  may  be obtained  from
   manufacturing directories or  the most recent SIC directory published by:

                        Government Printing Office
                        Superintendent of Documents
                        Washington, DC  20402

                        Stock Number 4101-0066
                              CDS DATA DICTIONARY

                                      C-5

-------
                                                       EFFECTIVE:   June 1,  1984

                                                                 PRIORITY CODE

Definition;  PRIORITY  CODE   is   a   field  reserved   for  Headquarters  only.
             Priority  Code   is   used  to  identify   facilities   falling  into
             numerous priority categories.
 Retrieval
 Abbreviation
                                          Valid Values:
      PRIO
 Card
 Type
 Card
 Columns
      63
 Data Element
 Length	
 Data
 Type
ALPHANtMERIC
 Justified
                        Masterfile
                        Record Type
                                                               20
 Required on
 New Entry
      NO
Masterfile
Position
113
 Nationally
 Controlled
      YES
Masterfile
Length
 Edit Error Messages:
 *** = Fatal Error
                            Warning Error
 Coding Considerations;
   The  edit will reject all input values to this  field  from regional or state
   personnel.   Headquarters uses  this field as follows:
   Value   Description

     M    Municipal  Incinerator
     N    Nuclear  Power  Plants
     R    Refinery
     I    Iron and Steel,  Non-priority
     P    iron and Steel,  Priority
     S    Smelter
     C    Coal-Fired Power Plant
     0    Oil-Fired  Power  Plant
     U    Undetermined Fuel-Fired
             Power  Plants
                        Value   Description

                          X     Coal- & Oil-Fired power Plant
                          Y     Coal- & Gas-Fired Power Plant
                          Z     Oil- & Gas-Fired Power Plant
                          G     Gas-Fired Power Plant
                          D     Diesel-Fired Internal
                                  Combustion Power Plant
                          T     Gas Turbine-Power Plant
                          A     All Fossil Fuel Fired Power
                                  Plants, i.e., C, O, & G
                              CDS DATA DICTIONARY

                                      C-6

-------
                                                       EFFECTIVE:  June 1, 1984

                                                    GOVERNMENTAL FACILITY CODE

Definition;  GOVERNMENTAL   FACILITY   CODE   identifies   facilities   owned   or
             operated by  a governmental unit.  This  code was  formerly  called
             the Federal Facility Code.
Retrieval
Abbreviation
Card
Type
Card 64
Columns
Data Element
Length
°ata NUMERIC
Type
Justified
Required on
New Entry
Nationally
Controlled
Edit Error Messages:
*** = Fatal Error
Coding Considerations:
Valid Values:
Valid Values:




Masterfile
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error


   1 - Source owned or operated by the federal government.

   2 - Source owned or operated by the state.

   3 - Source owned or operated by the county.

   4 - source owned or operated by the municipality.

   5 - Source owned or operated by the district.

   Blank/0 - All other facilities  not owned or operated  by  a federal state or
             local government.
                              CDS DATA DICTIONARY

                                      C-7

-------
                                                       EFFECTIVE:  June  1,  1984

                                                              AIR  PROGRAM CODE

Definition;  AIR  PROGRAM  CODE  is a  source indicator  used  to  separate  NSPS
             sources,  NESHAPS   sources,   sources  subject   to   federal  EPA
             jurisdiction, and sources subject  to state jurisdiction.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
APCD
2
65
1
ALPHANUMERIC

NO
YES
Valid Values:
0 = SIP Source
1 = SIP Source under
Jurisdiction
5 = OTHER
6 = PSD
7 = NSR
8 = NESHAP

Masterfile
Record Type
Masterfile
Position
Masterfile
Length
Federal
20
115
1
 Edit Error Messages:

  *INVALID AIR PROGRAM CODE

 *** = Fatal Error
Warning Error
 Coding Considerations;

   For  a  SIP  source,   the  State  has  primary  jurisdiction  for  enforcement
   activity, except for  sources under direct federal jurisdiction.

   If  a  given source is subject  to several air  program  regulations,  multiple
   source numbers should be assigned—one for each program.

   To  help  tie together  a facility subject  to several programs, use  the NEDS
   source number for  the last four positions of each source number.
                              CDS DATA DICTIONARY

                                      C-8

-------
                                                       EFFECTIVE:  June 1, 1984

                                                            AIR PROGRAM STATUS

Definition;  AIR  PROGRAM STATUS  represents  the  operational  condition  of  a
             facility for  a given  air program.   This  field  is  particularly
             applicable for NSPS, NSR,  PSD,  and NESHAP sources.   If  different
             points have different operating statuses/ the  APST  should reflect
             the most advanced operational status of all the points.
 Retrieval
 Abbreviation
     APST
Valid Values:

0, P, C, D, R, S, T, X
 Card
 Type
 Card
 Columns
     66
 Data Element
 Length	
 Data
 Type
ALPHANUMERIC
 Justified
                       Masterfile
                       Record Type
                                                               20
 Required on
 New Entry
     NO
Masterfile
position
180
 Nationally
 Controlled
     YES
Masterfile
Length
 Edit Error Messages:

  'INVALID AIR PROGRAM STATUS

 *** - Fatal Error
                           Warning Error
 Coding Considerations;

     Valid Values;

     O = Operating
     P = Planned  (has applied for a construction permit)
     C = Under Construction
     T = Temporarily Closed - Shutdown
     X » Permanently Closed - Dismantled
     D = NESHAP Demolition
     R = NESHAP Renovation \ Should be used only for sources with APCD=8.
     S = NESHAP Spraying
       M

        I
                              CDS DATA DICTIONARY
                                      C-9

-------
                                                       EFFECTIVE:   June  1,  1984

                                                       REGIONAL DATA ELEMENT  6.
Definition;  REGIONAL DATA ELEMENT 6 - user supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
RDE6
2
67-76
10
ALPHANUMERIC

NO
NO
Valid Values:
All alphanumeric characters.




Masterfile ..
Record Type
Masterfile ..
Position 153-162
Masterfile .Q
Length
 Edit Error Messages:
 *** - Fatal Error
             * = Warning Error
 Coding Considerations;

   Typical usages of this field include identifiers for (as of March 1982)
         Region V
         Region VI
         Region VII
         Region IX
         Region X
Additional Pollutants - Steel Information
PSD Permit Numbers
ESECA OFU Numbers
Stage II Non-Compliance - MSEE Number
GSA Federal Facility Number
                              CDS DATA DICTIONARY

                                     C-10

-------
Definition:
                                          EFFECTIVE:   June 1,  1984

                                    STAFF PERSONNEL CODE - SOURCE

STAFF  PERSONNEL  CODE  is  a  three-position  code  representing  the
person or group assigned to  monitor  the  facility.   It consists of
one alpha character followed by two numeric  characters.
Retrieval
Abbreviation .
Card 2
Type
Columns 77-79
Valid Values:
Must exist on the Personnel Table
maintained by the National DEC.
Please call the DBC to add, change,
or delete entries to this table.
Data Element ,
Length
Data
ALPHANUMERIC
Justified LEFT
Required on
New Entry
Nationally
Controlled
Edit Error Messages:
*INVALID STAFF CODE
*** * Fatal Error
Masterfile __
Record Type
Masterfile 116_U8
Position
Masterfile
Length
* = Warning Error
 Coding Considerations;

   The assigned person's name  is  generated  by the Update Program based  on the
   name found on the Personnel Table.
                              CDS DATA DICTIONARY

                                     C-ll

-------
                                      EFFECTIVE:  June 1, 1984
D.  SOURCE LEVEL - REPEATING POLLUTANT CARD 3

-------
                                                       EFFECTIVE:  June 1, 1984

                                             PENALTY ISSUE ADDRESSED INDICATOR

Definition;  PENALTY  ISSUE ADDRESSED  INDICATOR indicates  the  status of  the
             Penalty Issue  for  Significant Violators subject to  the  "Post 82"
             Enforcement Policy.   For  every Significant  Violator placed  on  a
             schedule  (Compliance Code  5), there  is  a  need  to address  the
             Penalty  Issue  before   full   resolution  of  the   violation  is
             considered achieved.  For sources placed on  a  schedule  which have
             had  the issue  addressed, code  a  "Y"  into  the  field.   If  the
             Significant Violator  is  not subject to the  "post  82" Enforcement
             Policy, code an  "X" into the  field.  If  the Significant Violator
             is on a schedule but  the  Penalty  Issue  has not been addressed, do
             not code anything into the field.
 Retrieval
 Abbreviation
     PISA
Valid Values:

X, Y, (Blank)
 Card
 Type
 Card
 Columns
      21
 Data Element
 Length	
 Data
 Type
ALPHANUMERIC
 Justified
                       Masterfile
                       Record Type
                                                               30
 Required on
 New Entry
     NO
Masterfile
Position
22
 Nationally
 Controlled
     YES
Masterfile
Length
 Edit Error Messages:  N/A
  ***  •* Fatal Error
                           Warning Error
 Coding Considerations;

         X = Not subject to  "Post 82" Policy.
         Y = Penalty  Issue Addressed.
    (BLANK) = Penalty  Issue not Addressed.
                              CDS DATA DICTIONARY
                                      D-l

-------
                                                       EFFECTIVE:  June  1, 1984

                                                                  POLLUTANT  ID

Definition;  POLLUTANT  ID  is  used  to  identify  the  pollutant  for  which
             pollutant compliance data is being entered.
 Retrieval
 Abbreviation
                                          Valid Values:
        PLLT
 Card
 Type
 Card
 Columns
22-23; 34-35; 46-47
 Data Element
 Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
ALPHANUMERIC
LEFT
NO
YES

Masterfile
Record Type
Masterfile
Position
Masterfile
Length

30
REPEATING
2
 Edit  Error Messages:

   *INVALID POLLUTANT CODE

 *** = Fatal Error
                          * = Warning Error
 Coding Considerations;

   This  field must be filled  in whenever repeating pollutant data  is  entered
   on  a  Card  3.   No  data for  any  of the repeating pollutant compliance  data
   elements  can be placed on the masterfile without a valid Pollutant ID.
    Valid  Values;

    AB - Asbestos
    AS - Arsenic
    BE - Beryllium
    BZ - Benzene
    CD - Cadmium
    CE - Coke  Oven Emissions
    CO - Carbon Monoxide
    PL - Fluorides
    HC - Hydrocarbons  (Volatile  Organic
                       Compounds)
    HG - Mercury
                            N2 - NO2
                            OD - Odors
                            OT - Other
                            PB - Lead
                            PT - Particulate Matter (total)
                            S2 - SO2
                            TS - Total Reduced Sulfur
                            VE - Visible Emissions
                            VC - Vinyl Chloride
                            ZN - Zinc
                              CDS DATA DICTIONARY

                                      D-2

-------
                                                       EFFECTIVE:   June 1,  1984

                                                         POLLUTANT DELETE FLAG

Definition;  POLLUTANT DELETE  FLAG  is used to  remove from the masterfile  all
             data related to a repeating pollutant.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
DROP
3
24; 36; 48
1
ALPHABETIC

NO
YES
Valid Values:
Blank or 'D1




Masterfile
Record Type
Masterfile
Position
Masterfile
Length

30
REPEATING
1
 Edit Error Messages:

  •INVALID POLLUTANT DELETE FLAG
  *NO DATA TO FOLLOW DELETE FLAG

 *** = Fatal Error
Warning Error
 Coding Considerations;

   A  'D'   in  the  Delete Flag  signifies that  the data  entered  for  a  given
   pollutant  should  be  completely  eliminated.   The  pollutant  compliance,
   emission category,  air quality  maintenance  indicator,  air  quality control
   indicator, and  loading are  blanked  out  by the Update Program when  a  'D'  is
   coded next to a pollutant or a Card 3.

   This data element is  valid for data entry only.
                              CDS DATA DICTIONARY

                                      D-3

-------
Definition:
                                          EFFECTIVE:  June  1,  1984

                                             POLLUTANT  COMPLIANCE

POLLUTANT  COMPLIANCE  indicates  the source  emissions  compliance
for  a  given  pollutant  based  on  the  worst-case  emission point
producing the indicated  pollutant.
 Retrieval
 Abbreviation
           PCMS
 Data Element
 Length	
                   ALPHANUMERIC
 Edit Error Messages:

   *INVALID COMPLIANCE STATUS
 *** = Fatal Error
Valid Values:
0-9
Card
Type
Card
Columns
3
25; 37; 49
Justified
Required on
New Entry
Nationally
Controlled
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
30
REPEATING
1
                                 Warning Error
 Coding Considerations;

   Valid Values;

   0 Unknown
   1 In violation - no schedule
   2 In compliance by source test
   3 In compliance by inspection
   4 In compliance by certification
   5 Meeting  compliance schedule
   6 In violation, not meeting schedule
   7 In violation, unknown with respect to schedule
   8 No applicable emission regulation
   9 In compliance - closed down

   Pollutant  compliance  (PCMS)  and Pollutant ID  (PLLT)  must  be maintained for
   all Class  A significant violators.

   Order of worst-case to best-case pollutant level compliance:
   PCMS =  1-6-0-7-5-4-3-2,8,9.
                              CDS DATA DICTIONARY

                                      D-4

-------
                                                       EFFECTIVE:   June 1,  1984

                                                      REGIONAL DATA ELEMENT 14
Definition;  REGIONAL DATA ELEMENT 14 - user supplied.
 Retrieval
 Abbreviation
 Col'lns
 Data Element
 Length

Card
Type
3
    50
                   ALPHANUMERIC
                  Valid Values:

                  All alphanumeric characters.
 Justified
                  Masterfile
                  Record Type
                                                               3Q
 Required on
 New Entry
N_
 Nationally
 Controlled

                  Masterfile
                  Length
 Edit Error Messages:
 *** =» Fatal Error
                  * « Warning Error
 Coding Considerations;
                              CDS DATA DICTIONARY

                                      D-5

-------
                                                       EFFECTIVE:  June 1, 1984

                                                      POLLUTANT CLASSIFICATION

Definition;  POLLUTANT CLASSIFICATION assigns a  source classification code to
             an individual pollutant in the repeating  pollutant area.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
PCLS
3
27; 39} 51
1

LEFT
NO
YES
Valid Values:
Input File
1 « Al
2 « A2
B - B
U * Unknown


Master file
Record Type
Master file
Position
Master file
Length

30
REPEATING
2
 Edit Error Messages:
   * =» INVALID POLLUTANT CLASSIFICATION

 *** = Fatal Error	
       Warning  Error
 Coding Considerations;

   The  single  character  code  on  the input  card  will  generate  a  one-  or
   two-digit code  on the  master  file.  The  generated master file  PCLS  values
   must be used for  selection card values on a CDS retrival.
                       Input
                       Values

                         1
                         2
                         B
                         U
Retrieval
 values

   Al
   A2
   B
   UK
                              CDS DATA DICTIONARY
                                      D-6

-------
                                                       EFFECTIVE:   June 1,  1984

                                       POLLUTANT AIR QUALITY CONTROL INDICATOR

Definition;  POLLUTANT AIR  QUALITY CONTROL  INDICATOR  shows whether  or not  a
             source  emits  a  criteria  pollutant  for  which  its  county  is
             nonattainment.   When  coupled with  the pollutant  ID  (PLLT),  the
             exact  nonattainment  status, by  pollutant,  is  indicated for  the
             county the source is located in.
 Retrieval
 Abbreviation
     PAQC
Card
Type
Card
Columns
3
28; 40; 52
Valid Values:

A, N, U, 1, 2
 Data Element
 Length	
 Data
 Type
ALPHANUMERIC
 Justified
                       Masterfile
                       Record Type
                                                               30
 Required on
 New Entry
     YES
Nasterfile
Position
REPEATING
 Nationally
 Controlled
     YES
Hasterfile
Length
 Edit Error Messages:
 *** = Fatal Error
                           Warning Error
 Coding Considerations;

   Blank - Attainment area for a given pollutant.
   A - Attainment area for a given pollutant.
   N - Nonattainment for primary and secondary standards for a given pollutant.
   1 - Nonattainment for primary standards only, for pollutant S02«
   2 - Nonattainment for secondary standards only, for pollutants PT or S2.
   U - Unclassified.

   Consult the  Federal  Register for a  complete listing of  all  attainment and
   nonattainment  areas.  This  list  is periodically  updated  in the  Federal
   Register.

   All  attainment designations  are  at the  county level.   System limitations
   preclude such designations at the sub-county level.
                              CDS DATA DICTIONARY

                                      D-7

-------
                                                       EFFECTIVE:  June  1,  1984

                                                             POLLUTANT LOADING

Definition:  POLLUTANT  LOADING  indicates  the annual  pollutant loading  of a
             given  pollutant.    The  pollutant   loading   shown   should   be
             compatible with the Source Classification Code (CLAS).
 Retrieval
 Abbreviation
                                          Valid Values:
        LOAD
 Card
 Type
 Card
 Columns
29-33; 41-45;  53-57
 Data Element
 Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
NUMERIC
RIGHT
NO
NO

Masterfile
Record Type
Masterfile
Position
Masterfile
Length

30
REPEATING
5
 Edit Error Messages:
 *** = Fatal Error
                              Warning Error
 Coding Considerations;

   If  this  field  is used,  it should be a  numeric value representing emissions
   in  tons per year.   No decimals  or  fractions  should be used.  Leading spaces
   are acceptable,  but not leading zeros, i.e., OdlSO.

   To  make  this  a meaningful  data  element,  a  source level  comment  (card
   code 4)  identifying the year of operation for the  emissions  listed should
   always  accompany this data  element.   However, please  note that  this  code
   (LOAD)  is not intended to track  annual emissions,  but  rather serve as  an
   indicator  of,   and  justification  for,  the  CLAS  code  indicated for  this
   source.
                              CDS DATA DICTIONARY

                                      D-8

-------
                                                       EFFECTIVE:   June 1,  1984

                                                             FACILITY CAPACITY

Definition;  FACILITY  CAPACITY indicates  the  total  output  capacity  of  the
             principal  product  produced  at   a   facility.   This  might   be
             expressed as barrels per day,  megawatts, etc.
Retrieval
Abbreviation
Card 30
Type
Card _a
58—64
Columns
Data Element _
Length
SS NUMERIC
Justified RIGHT
Required on
New Entry
Nationally
Controlled
Edit Error Messages:
*** - Fatal Error
Valid Values:




Mast erf ile
Record Type
Mast erf ile
Position
Mast erf ile
Length
* » Warning Error

30
43-49
7

 Coding Considerations;

  a.  For  general  processes,  use  tons  per  year  of  output product.   If  a
      facility  produces  over 10 million  tons per year, code all 9's  in this
      field.

  b.  For refineries, use barrels of petroleum processed per calendar day.

  c.  For  petroleum  storage   facilities,  use   thousands   of  barrels  total
      capacity.

  d.  For  incinerators  (sewage sludge  or  municipal  refuse),   use  tons  per
      day/incineration rate.

  e.  For electric  utilities, use total megawatt design capacity.

  f.  For  coal-fired boiler  sources,  use  Million British  Thermal  Units  per
      Hour (MMBTUH) heat input capacity.

  This  field  is a confidential data element.  An  appropriate password  must be
  used  to access  this field's data.
                              CDS DATA DICTIONARY

                                      D-9

-------
                                                       EFFECTIVE:  June 1, 1984

                                                       REGIONAL  DATA  ELEMENT 9
Definition;  REGIONAL DATA ELEMENT 9 - user supplied.
 Retrieval
 Abbreviation
 Card
 Type
 Card
 Columns
 Data Element
 Length
 Data
 Type
     RDE9
    65-71
ALPHANUMERIC
                                          Valid Values:
 Justified
                       Masterfile
                       Record Type
                                                               30
 Required on
 New Entry
     NO
Masterfile
Position
23-29
 Nationally
 Controlled
     NO
Masterfile
Length
 Edit Error Messages:
 *** = Fatal Error
                           Warning Error
 Coding Considerations;

   Typical usages of this field include identifiers for (as of March 1982):
         Region II
         Region III
         Region IV
         Region V

         Region VII
         Region IX
          NPDES Permit Numbers
          PSD Permit Numbers
          County Names
          PSD   Application   Number   -   General   Industry
          Catalogue
          Air Program Status of Points in NSPS
          Date Reported as Significant Violator
                              CDS DATA DICTIONARY

                                     D-10

-------
                                                       EFFECTIVE:   June 1,  1984

                                                      REGIONAL DATA ELEMENT 10
Definition:  REGIONAL DATA ELEMENT 10 - user supplied.
 Retrieval
 Abbreviation
 Card
 Type
 Card
 Columns
 Data Element
 Length	
 Data
 Type
     RD10
    72-73
ALPHANUMERIC
                                          Valid Values:
 Justified
                       Masterfile
                       Record Type
                                                               30
 Required on
 New Entry
     NO
Masterfile
Position
30-31
 Nationally
 Controlled
     NO
Masterfile
Length
 Edit Error Messages:
 *** - Fatal Error
                           Warning Error
 Coding Considerations;

         Region III
         Region IV
         Region V

         Region VIII
         Region IX
          District Offices
          State Inspection Year
          Lead Enforcement Role - All States;
          Lead Enforcement Role - Ohio
          Opacity Readings
          Assigned to-Project Officer
                              CDS DATA DICTIONARY

                                      D-ll

-------
                                                       EFFECTIVE:   June 1,  1984

                                                      REGIONAL DATA ELEMENT 11
Definition:  REGIONAL DATA ELEMENT 11 - user supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
RDll
3
74-75
2
ALPHANUMERIC

NO
NO
Valid Values:




Masterfile
Record Type
Masterfile
Position
Masterfile
Length

30
32-33
2
 Edit Error Messages:
 *** = Fatal Error
                 Warning Error
 Coding Considerations;

         Region III
         Region IV
         Region V
         Region VIII
Continuous Monitoring Code
B=Selected CLASS B Sources in Nonattainment Areas
Lead Enforcement
P=Primary Source
                              CDS DATA DICTIONARY

                                      D-12

-------
                                                       EFFECTIVE:   June 1,  1984

                                                      REGIONAL DATA ELEMENT 12
Definition;  REGIONAL DATA ELEMENT 12 - user supplied.
Retrieval
Abbreviation *UJ^
Card .
Type
Card 7g
Columns
Data Element
Length
Data
T ALPHANUMERIC
Justified
Required on
New Entry
Nationally
Controlled wu
Edit Error Messages:
*** =» Fatal Error
Valid Values:




Masterfile
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error

30
34
1

 Coding Considerations;

   Region V uses this  field  to indicate  Major  Source Enforcement Effort (MSEE)
   case delegation.
         Region IV
         Region V
         Region VI
         Region IX
V=VOC Sources
Indicator of Major SCC
NSPS & PSD=M for Continuous Monitoring
Actual/Potential Tons/Yr.
                              CDS DATA DICTIONARY

                                     D-13

-------
                                                       EFFECTIVE:   June 1,  1984

                                                    SODRCE CLASSIFICATION CODE

Definition;  SOURCE  CLASSIFICATION  CODE   -  designation  used   for   program
             planning purposes.  Categorizes  sources  according to the  Alabama
             Power decision's definition of major source.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
CLAS
3
77-78
2
Valid Values:
Al = Class Al
A2 = Class A2
UK = Unknown
B » Class B

°ata ALPHANUMERIC
Justified
Required on
New Entry
Nationally
Controlled
LEFT
YES
YES
Edit Error Messages:
*INVALID SOURCE CLASSIFICATION CODE
*** = Fatal Error
Masterfile
Record Type
Masterfile
Position
Masterfile
Length
* = Warning Error
30
50-51
2

Coding Considerations;
    Class  A  retrieval will  include Class Al plus Class A2.

       Class A   =•  Class Al  +  A2

       Class Al  =  Actual  or potential  controlled  emissions    100 t/yr  as per
                  Alabama Power

       Class A2  =  Actual  emissions     100  t/yr,  but  potential  uncontrolled
                  emissions   100 t/yr

       Class B   =  Potential uncontrolled emissions   100 t/yr

       Class UK  =  Unknown

       Class    =  Blank

    All operating  sources must be classified according to these categories.
                              CDS DATA DICTIONARY

                                      D-14

-------
                                                       EFFECTIVE:   June 1,  1984

                                                       LOADING DERIVATION CODE

Definition:  LOADING  DERIVATION  CODE   indicates   the  method   of   emissions
             estimation used  to  determine the  source classification code  for
             the source.
 Retrieval
 Abbreviation
LDRC
 Edit Error Messages:
 *** = Fatal Error
Valid Values:
A = Actual or estimated actual
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
3
79
1
ALPHABETIC
N/A
NO
NO
Jj
P » Potential controlled per Alabama
. Power decision

I - Incomplete source loading
information
Blank = Assumed potential controlled
per Alabama Power decision

Hasterfile
Record Type
Master file
Position
Masterfile
Length

30
52
1
                      Warning Error
 Coding Considerations;

   The Loading Derivation Code must be coded for all Class Al sources.

   If LDRC  is  equal to  'A1, at  least  one pollutant for that source  must have
   emissions in  the  pollutant  loading  field equal to or greater  than 100 tons
   per year.
                              CDS DATA DICTIONARY

                                     D-15

-------
                            EFFECTIVE:   June 1,  1984
E.  POINT LEVEL - CARD 5

-------
                                                       EFFECTIVE:   June 1,  1984

                                                                      SCC CODE

Definition;  SCC CODE is  the  NEDS Source Classification Code which  provides a
             detailed analysis  of the process creating  the  emission  for  this
             point.  The  SCC  code provides a  very  precise description  of  the
             process.   The   code  is  particularly  useful  for   identifying
             processes  which   cross   industrial  category  lines  (SIC),  e.g.,
             boilers, sulfuric acid plants.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
SCC3, SCC6, SCC8
5
20-27
8
NUMERIC
\
LEFT
NO
YES
Valid Values:
Consult the NEDS coding manual or
AP-42 for a list of valid values.
The CDS edit accepts blanks or an
8— rv»<3i !• i rtn numeric Field.



Masterfile
Record Type
Masterfile ,, ,0
» . * •»• "~^ O
Position
Masterfile „
Length
 Edit Error Messages:

  *SCC CODE SHOULD BE NUMERIC

 *** = Fatal Error
Warning Error
 Coding Considerations;

   Although all 8  positions  should be coded on all points other  than 000,  the
   retrieval  can  select  on  either  the  first  3  positions,  the  first  6
   positions, or all  8  positions.   SCC3  retrieves on the first 3 positions of
   the SCC Code; SCC6 retrieves on  the first  6  positions  of  SCC Code; and SCC8
   retrieves on the entire SCC Code.

   For  some industries, SSCD  has  expanded on  the values  in the  NEDS  coding
   manual; special guidance  has been provided for these SCC codes.

   SCC8 is  at  the  present  a confidential data  element.   Users  must supply  the
   proper  password  on  the  Retreieval   Card  20 to  obtain  SCC8  on  output
   reports.  SCC3  and SCC6 are not  password protected on output reports.
                              CDS DATA DICTIONARY
                                      E-l

-------
                                                       EFFECTIVE:   June 1,  1984

                                                                CAPACITY CODE

Definition;  CAPACITY  CODE   is   used  for  coal-fired   boilers   other   than
             electrical  utilities  and   identifies   the  boiler   heat  input
             capacity in tons of MMBTUH.   A boiler  with a heat input  capacity
             of 150 million BTU per hour  would  have  "15"  in Capacity  Code.
 Retrieval
 Abbreviation
   CAPC
Valid values:

00-99
 Card
 Type
 Card
 Columns
  28-29
 Data Element
 Length
 Data
 Type
NLMERIC
 Justified
                       LEFT
                     Masterfile
                     Record  Type
                     34
 Required on
 New Entry
   NO
Masterfile
Position
29-30
 Nationally
 Controlled
   YES
Masterfile
Length
 Edit Error Messages:
 *** = Fatal Error
                     * " Warning Error
 Coding Considerations;

   This is required  for  coal-fired boilers  for  all industries other than power
   plants  provided  that  the boiler  has a heat  input capacity  equal to  or
   greater than 100 MMBTUH.

   Users should note that this  field was once used for  tracking the NEDS Point
   Cross-Reference (NEXP).

   This  field  is  a   confidential data   element.   Users  must  supply  the
   appropriate password  on  the  Retrieval  Card 20 to obtain  a printout of this
   field.
                              CDS DATA DICTIONARY

                                      E-2

-------
                                                       EFFECTIVE:   June 1,  1984

                                                             COMPLIANCE STATUS

Definition;  COMPLIANCE  STATUS gives  the  regional office  an  indication  of
             whether a  source  is in  compliance,   not  in compliance,  or  its
             compliance status is unknown, with regard to  emission regulations
             at the point level.
 Retrieval
 Abbreviation
   CMST
Valid Values:
0 through 9
 Card
 Type
 Card
 Columns
   30
 Data Element
 Length	
 Data
 Type
NUMERIC
 Justified
                     Masterfile
                     Record Type
                                                               34
 Required on
 New Entry
   YES
Masterfile
Position
31
 Nationally
 Controlled
   YES
Masterfile
Length
 Edit Error Messages:

  ***INVALID COMPLIANCE STATUS

 *** « Fatal Error	
                     * » Warning Error
 Coding Considerations;

   Must be coded on the point 000; may be coded on the other emission points.

   Compliance  Status Code;
   0    Unknown
   1    In violation - no schedule
   2    In compliance by source test
   3    In compliance by inspection
   4    In compliance by certification
   5    Meeting compliance schedule
   6    In violation, not meeting schedule
   7    In violation, unknown with respect to schedule
   8    No applicable emission regulation
   9    In compliance - closed down

   The  Compliance  Status  on  Point  000  (entire  source)  should  reflect  the
   worst-case  emission compliance of  any  process  within  the source.   The
   Compliance  Status on all  other  points should reflect the compliance of that
   particular  point.
                              CDS DATA DICTIONARY

                                      E-3

-------
                                                      EFFECTIVE:  June 1, 1984

                                                            COMPLIANCE STATUS
                                                                   (Continued)

Coding Considerations  (Continued);

  At the 000 point, this is the same as SCMS.

  At a minimum, all significant  violators  (SCMS=1,5,6,7)  must have compliance
  status maintained at the point level.

  Order of worst-case to best-base point level compliance:

  CMST - 1-6-0-7-5-4-3-2-8-9.
                             CDS DATA DICTIONARY

                                     E-4

-------
Definition:
                                          EFFECTIVE:  June 1, 1984

                                                         SIP CODE

SIP  CODE   provides  the  regional   office   with  a   method  of
identifying  the  type  of  enforcement  schedule  which  has  been
negotiated  with a  source  not  presently  meeting enforceable SIP
emission limits.
 Retrieval
 Abbreviation
           SI PC
Valid values:

Blank, 0 through 9
 Card
 Type
 Card
 Columns
           31
 Data Element
 Length	
 Data
 Type
        NtMERIC
 Justified
                             Masterfile
                             Record Type
                                                               34
 Required on
 New Entry
           NO
Masterfile
Position
32
 Nationally
 Controlled
           YES
Masterfile
Length
 Edit Error Messages:

  *INVALID SIP CODE

 *** « Fatal Error
                                 Warning Error
 Coding Considerations;

   This  field must  be  coded for  all Class
   Compliance Status of 1, 5, 6 or 7.
                                  A  sources which  have  a  Source
   Blank
     0
     1
     2
     3
     4
     5
     6
     7
     8
     9
      No schedule
      Schedule status unknown
      Federally enforceable DCO
      Federally approved SIP schedule  (should have SCMS=4)
      Federal court order schedule
      Federally enforceable consent decree schedule
      Undergoing enforcement actions to develop a schedule
      State/local compliance schedule not federally enforceable
      Non-federally enforceable schedule being developed
      Reserved
      Subject to offsets
                              CDS DATA DICTIONARY

                                      E-5

-------
                                                       EFFECTIVE:   June 1,  1984

                                                                POLLUTANT CODE

Definition;  POLLUTANT  CODE  indicates  the  type  of pollutant  emitted  by  a
             particular emission point.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
PLUT
5
32-33
2
ALPHANUMERIC
LEFT
YES
YES
Valid Values:
See below for the table of valid
values.



Master file 34
Record Type
Masterfile , . .
Position J
Masterfile .
Length
 Edit Error Messages:

  *INVALID POLLUTANT CODE

 *** = Fatal Error
       Warning Error
 Coding Considerations;

   Should  be input on  all new emission points.   Use of one of  the following
   values:
   Valid Values;

   AB  - Asbestos
   AS  - Arsenic
   BE  - Beryllium
   BZ  - Benzene
   CD  - Cadmium
   CE  - Coke  Oven Emissions
   CO  - Carbon Monoxide
   FL  - Fluorides
   HC  - Hydrocarbons  (Volatile
        Organic Compounds)
   HG  - Mercury
N2 - NO
OD
OT
PB
PT - Particulate Matter (Total)
S2 - S02
TS - Total Reduced Sulfur
VC - Vinyl Chloride
VE - visible Emission
ZN - Zinc
Odors
Other
Lead
Particulate Matter
                              CDS DATA DICTIONARY

                                      E-6

-------
                                                       EFFECTIVE:   June 1,  1984

                                                              STATE REGULATION

Definition;  STATE REGULATION contains  the  state's emission  regulation  number
             for a given pollutant.  In the case of NSPS or  NESHAP facilities,
             use the Part 60  or  Part 61 Subpart notation  (letters B  thru  HH)
             found in the Code of Federal Regulations,  Title  40.
 Retrieval
 Abbreviation
      SREG
Valid Values:
All alphanumeric values.
 Card
 Type
 Card
 Columns
     34-48
 Data Element
 Length	
      15
 Data
 Type
ALPHANUMERIC
 Justified
                       LEFT
                        Masterfile
                        Record Type
                     34
 Required on
 New Entry
      NO
Masterfile
Position
35-49
 Nationally
 Controlled
      NO
Master file
Length	
 15
 Edit Error.Messages:
 **'* - Fatal Error
                            Warning Error
 Coding Considerations;

   NSPS and NESHAP  subpart  entries should be placed at  every  subject emission
   points.  Sources subject to only  one  subpart should enter  it  at  the triple
   zero point as  well.   Sources subject  to  several subparts  should  enter  the
   code "MULT" at the triple  zero  point  to indicate multiple applicability  and
   the appropriate subparts at the emission point level.

   Entries must be  left-hand justified,  with  consistent use  of  abbreviations
   and spacing to facilitate national as well as regional retrievals.
                              CDS DATA DICTIONARY

                                      E-7

-------
                                                       EFFECTIVE:  June 1, 1984

                                                      REGIONAL DATA ELEMENT 15
Definition;  REGIONAL DATA ELEMENT 15 - user supplied.
„_.. .    ,
Retrieval
Abbreviation
 Card
 Type
 Card
 Columns
 Data Element
 Length
 Data
                                          Valid Values:
                                          All alphanumeric characters.
                   ALPHANUMERIC
justified
                                          Masterfile
                                          Record Type
Required on
New Entry
Q
                                         Masterfile
                                         Position
                                                               _fl
Nationally
Controlled

                                          Masterfile
                                          Length
 Edit Error Messages:
*** - Fatal Error
                                          * = Warning Error
 Coding Considerations;
                              CDS DATA DICTIONARY

                                      E-8

-------
                                                       EFFECTIVE:   June 1,  1984

                                                           PROCESS DESCRIPTION

Definition;  PROCESS  DESCRIPTION  is  a  brief  description  of  the  physical
             emission point such as  a boiler or  cupola.   At the  000  Emission
             Point level,  this  should be used  to describe  the type  of  plant
             such as a generating station or a Portland cement plant.
 Retrieval
 Abbreviation
      PRDS
Valid Values:

All alphanumeric characters.
 Card
 Type
 Card
 Columns
     50-74
 Data Element
 Length	
      25
 Data
 Type
ALPHANWERIC
 Justified
                       LEFT
                        Masterfile
                        Record Type
                     34
 Required on
 New Entry
      YES
Masterfile
Position
51-75
 Nationally
 Controlled
      NO
Masterfile
Length
 25
 Edit Error Messages:
 *** • Fatal Error
                            Warning Error
 Coding Considerations;

   Abbreviations  should  be used  consistently  and  clearly  for  sorting  and
   retrieval purposes,  i.e.,  BLR-3 for Boiler 13.   If  several emission points
   have  similar  process  desciptions,  be sure  to identify  each point with  a
   unique process description,  such  as a boiler number or  a specific location
   for  the  process.   These  descriptions  must be  clear  enough  so that  an
   inspector or other  agency  official can readily identify  the  apparatus  at a
   facility to which the CDS record applies.

   If  no value is  entered for  Point 000 and  if the  source  has a  valid Sic
   Code, the  SIC  Code description is generated as the Process  Description on
   Point 000 when the source is  first placed on the CDS masterfile.
                              CDS DATA DICTIONARY

                                      E-9

-------
                                                       EFFECTIVE:   June  1,  1984

             '-•                                        MULTIPLE CROSS-REFERENCE.

Definition;  MULTIPLE CROSS-REFERENCE is used to tie  together  various emission
             points.  When  one physical  emission point  has several emission
             point numbers  (one for  each  pollutant or regulation), this  field
             should  be  used  to  tie  together   the  various  point   numbers
             referring to one physical point.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
MULT
5
75-77
3
NUMERIC
LEFT
NO
NO
Valid Values:
All numerics




Master file
Record Type
Master file
Position
Master file
Length

34
76-78
3
 Edit Error Messages:

  *MULTIPLE XREF SHOULD BE NUMERIC

 *** - Fatal Error     	
Warning Error
 Coding Considerations;

   If  emission points  010,  Oil and  012 refer  to three  different  pollutants
   being  emitted  from one process  or piece of  equipment,  points Oil  and 012
   should cross reference 010.
                              CDS DATA DICTIONARY

                                     E-10

-------
                                                       EFFECTIVE:  June 1, 1984

                                                       REGIONAL DATA ELEMENT 7
Definition;  REGIONAL DATA ELEMENT 7 - user supplied.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
RDE7
5
78
1
ALPHANUMERIC

NO
NO
Valid Values:
All alphanumeric values.
Masterfile 34
Record Type
Masterfile _.
Position
Masterfile
Length
 Edit Error Messages:
 *** » Fatal Error
* = Warning Error
 Coding Considerations;

   Typical usages of this field include identifiers for:

         Region I       State Compliance Status
                         (where it is different from CMST)

         Region III     Opacity Monitoring

         Region VII     Air Program Status of NSPS points
                              CDS DATA DICTIONARY

                                     E-ll

-------
                                                       EFFECTIVE:   June 1,  1984

                                                         PROCEDURAL COMPLIANCE

Definition;  PROCEDURAL  COMPLIANCE should  be used  for  all NSR,  PSD,  NSPS,
             NESHAP,  and  SIP  facilities  under  construction  or  subject  to
             performance  tests, continuous  emission monitoring  requirements,
             and other procedural  requirements  under such air programs.   This
             field indicates  the compliance  status  of a facility with respect
             to all  applicable procedural requirements.   Use CMST, PCMS,  and
             SCMS to  indicate the  compliance of an  operating facility subject
             to immediately effective emission regulations.
 Retrieval
 Abbreviation
      CMS2
Valid Values:

A, B, C, 8, V, I, N, Blank
 Card
 Type
 Card
 Columns
      79
 Data Element
 Length	
 Data
 Type
ALPHANUMERIC
 Justified
                        Masterfile
                        Record Type
                                                               34
 Required on
 New Entry
      NO
Masterfile
Position
80
 Nationally
 Controlled
      YES
Masterfile
Length
 Edit Error Messages:
  ***  « Fatal  Error
                        * = Warning Error
 Coding Considerations;
     I

     N
 Value
 Unknown compliance with procedural requirements
 In violation of procedural requirements
 In compliance with procedural requirements
 No applicable regulation or procedural requirement
 No applicable regulation or procedural requirement
 In  violation  of federally enforceable  compliance schedule;
 future effective regulation
 In   compliance   with   federally  enforceable   compliance
 schedule;  future effective regulation
 No  federally enforceable compliance  schedule but subject to
 future effective regulation(s)
                              CDS  DATA  DICTIONARY

                                      E-12

-------
                            EFFECTIVE:  June 1,  1984
F.  ACTION LEVEL - CARD 7

-------
                                                       EFFECTIVE:   June 1,  1984

                                                            ACTION DESCRIPTION

Definition;  ACTION DESCRIPTION  is  generated on  each action  record based  on
             Action Type.  Action Description may be coded on the card 7  for
             Action Type 00.
 Retrieval
 Abbreviation
      ADES
 Card
 Type
Valid values:

Please call the national DEC to add
or change action descriptions on the
regional Action Table.
 Card
 Columns
     20-34
 Data Element
 Length	
      15
 Data
 Type
ALPHANUMERIC
 Justified
                       LEFT
                        Masterfile
                        Record Type
                     46
 Required on
 New Entry
                        Masterfile
                        Position
                 40-54, 107-156
 Nationally
 Controlled
      YES
Masterfile
Length
15, 50
 Edit Error Messages:
 *** « Fatal  rror
                        * « Warning Error
 Coding Considerations;

   Two action descriptions are  generated  from Action Type; the first  is a 50-
   position long  action description available on  the Source Date  Report, and
   the second is a  15-position  short action description  retrievable on a Quick
   Look Report.

   When  Action Type  00  is  specified  in card  columns   53  and  54,  the  Edit
   Program will pick  up a 15-position  Action Description  from  card columns 20
   through 34 of  the  card 7 and  place  this description  on both  the  short and
   long Action Description on  the CDS  masterfile.  Action Type 00  is designed
   for  infrequently used actions which  are not  placed on  the  Action Table
   controlled by  the  National  DBC.  It can  be  a replacement for  the regional
   Action  Type   "OTHER  -   SEE  COMMENTS  BELOW".    Since  comments  are  not
   retrievable, but Action  Type  and  Action  Description are retrievable, the
   Action  Type  00 should be most useful  for  infrequently used  actions which
   are not on the Action Table.
                              CDS DATA DICTIONARY
                                      F-l

-------
                                                       EFFECTIVE:   June 1,  1984

                                                          CIVIL PENALTY AMOUNT

Definition;  CIVIL PENALTY AMOUNT indicates the civil penalty  assessed against
             a facility  in the  final,  legally binding  agreement between  the
             enforcement authority and the source.
 Retrieval
 Abbreviation
 PLTY
 Card
 Type
 Card
 Columns
46-52
 Data Element
 Length
 Edit Error Messages:
 *** • Fatal Error
Valid Values:
All numeric values.
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
NUMERIC
RIGHT
NO
NO

Master file
Record Type
Master file
Position
Master file
Length

46
93-99
7
                       Warning Error
 Coding Considerations;

   This field should be used  in conjunction with the following action types:

                              Z4    State Civil Penalty
                              Z6    Federal Civil Penalty

   Dollar  amounts  must  be  right justified;  they  should  be  rounded  to  the
   nearest $100.  No commas,  dollar signs, or periods must be used.
                              CDS DATA DICTIONARY

                                      F-2

-------
                                                       EFFECTIVE:   June  1,  1984

                                                                   ACTION TYPE

Definition;  ACTION TYPE  is  a  two-position  alphanumeric  action  description
             identifier.
 Retrieval
 Abbreviation
ATPE
Card
Type
Card
Columns
7
53-54
Valid Values:
Must be on Action Table controlled by
national DEC.

Action Type 00 indicates an action
type which is user defined.
 Data Element
 Length
Data
Type
Justified
Required on
New Entry
Na tionally
Controlled
ALPHANUMERIC
LEFT
YES
YES

Master file
Record Type
Master file
Position
Master file
Length

46
21-22
2
 Edit Error Messages:

  ***INVALID ACTION TYPE
  ***ACTION TYPE REQUIRED ON NEW ENTRY

 *** = Fatal Error	
                  * = Warning Error
 Coding Considerations;

   Please  call the  national DEC  to add,  change,  or  delete  entries on  the
   Action Table for your region.

   If  00  is coded in the Action  Type  field,  the Edit Program will  pick  up an
   Action  Description from  card  columns 20  through 34 of  the  card  7.   This
   capability  should  eliminate the  need  for  using  an  Action Type  meaning
   •OTHER - SEE COMMENTS BELOW*.

   Certain action types are  required  input  to CDS.  Please consult the current
   FY air enforcement program plans and  the most recent SSCD guidance material
   for the most current requirements.

   To  obtain  the  most current version  of  a  region's  action types,  please
   follow the procedures described in Chapter 10 of  this manual.

   Since  many  action types  are confidential, users  should use a  password on
   the Retrieval Card Type 20 to obtain action level information on retrievals.
                              CDS DATA DICTIONARY

                                      F-3

-------
                                                       EFFECTIVE:  June 1, 1984

                                                                 DATE ACHIEVED

Definition;  DATE  THIEVED is  the  date on  which an action  is completed  in
             month-day-year format.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
DTAC
7
55-60
6
NUMERIC
LEFT
NO
NO
Valid Values:
Blanks or zeros are
numeric other than
between 01 and 31,
greater than 60.


Master file
Record Type
Master file
Position
Master file
Length
acceptable.
zero, day must
month must be
and year must
46
29-34
6
If
be
be



 Edit Error Messages:

  *INVALID DATE ACHVD - OUTPUT  ZEROS

 *** » Fatal Error	
Warning Error
 Coding Considerations;

   If an  error  is encountererd in the date field, the  bad  month,  day, or year
   is zeroed out  by  the  Edit Program.   An asterisk on a change transaction for
   this field will zero  out the  field on  the masterfile.
                              CDS DATA DICTIONARY

                                      F-4

-------
Definition:
                                          EFFECTIVE:  June 1, 1984

                                                   DATE SCHEDULED

DATE SCHEDULED is the date on  which an action  is  scheduled to be
performed.  Use the month-day-year format.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
DISC
7
61-66
6
NUMERIC
LEFT
YES
NO
Valid Values:
Blanks or zeros are acceptable.
Otherwise, day
31, month must



Master file
Record Type
Master file
Position
Master file
Length
must be between 01 and
be between 01 and 12,
be greater than 60.
46
23-48
6
 Edit Error Messages:

  'INVALID DATE SCHED - OUTPUT ZEROS
  *DATE SCHED REQUIRED ON NEW ENTRY

 *** =• Fatal Error	
                                 Warning Error
 Coding Considerations;

   If an  error  is encountered in  the  date field, the bad month,  day,  or year
   is zeroed out.  If this field is left  blank  on a new transaction and if the
   Date Achieved  is  valid, the Date Achieved  is moved into this  field by the
   Edit Program.
                              CDS DATA DICTIONARY

                                      F-5

-------
                                                       EFFECTIVE:   June 1, 1984

                                                             ACTION STAFF CODE

Definition;  ACTION STAFF CODE is a  three-position code  referring to the staff
             member assigned to complete the action.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
PERA
7
67-69
3
ALPHANIMERIC
LEFT
NO
YES
Valid values:
Must exist on the Personnel Table
controlled by the National DEC. The
first position must be alpha; the
~~~~ next two numeric* When requesting
changes to this table, be sure to
give the DEC full title information
as well.

Master file 4g
Record Type
Master file -
Position
Master file 3
Length
 Edit Error Messages:

  *INVALID STAFF CODE

 *** • Fatal Error
* » Warning Error
 Coding Considerations;

   Please  call the National  DEC to make  additions, changes,  or  deletions to
   the Personnal Table.
                              CDS DATA DICTIONARY

                                      F-6

-------
Definition:
                                          EFFECTIVE:  June 1, 1984

                                                     RESULTS CODE

RESULTS CODE  indicates  the results of  an action,  such  as action
achieved, action not achieved, or action rescheduled.
Retrieval
Abbreviation
Card
Type
Card
Columns
Data Element
Length
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
STAC
7
70-71
2
NUMERIC
LEFT
NO
YES
valid Values:
May be a blank
must be a two-
Must exist on



Master file
Record Type
Master file
Position
Master file
Length
; if not a blank, it
digit numeric field.
the Results-Code Table
the National DEC.
46
55-56
2



 Edit Error Messages:

  'INVALID RESULTS CODE

 *** = Fatal Error
                                 Warning Error
 Coding Considerations;

   The results  code can indicate  the  success of an  action,  including whether
   or not the action was carried out.

   Please  call the  National  DEC  to  add,  change/  or delete  entries on the
   Results-Code Table for your  region.   See Chapter 10 for instructions on how
   to obtain the most current Results Code Table for your region.
                              CDS DATA DICTIONARY

                                      F-7

-------
                                                       EFFECTIVE:  June 1, 1984
                                                       REGIONAL DATA ELEMENT 8
Definition;  REGIONAL DATA ELEMENT 8 is user supplied.
Retrieval
Abbreviation
Valid Values:
Card
Type
Card
Columns 72-73
Data Element
Length
*JJ ALPHANIMERIC
Justified LEFT
Required on
New Entry
Nationally
Controlled
Edit Error Messages:
*** - Fatal Error
Master file
Record Type
Masterfile _
Position 57~58
Masterfile
Length
* = Warning Error
Coding Considerations;
   Typical usages of this  field  include  identifiers  for  (as of March 1982):
                      Region V      SO2  Compliance Status
                      Region VII   Opacity  Readings
                              CDS DATA DICTIONARY
                                      F-8

-------
                        EFFECTIVE:  June  1,  1984
 G.  COMMENTS
Source - Card 4
Point - Card 6
Action - Card 8

-------
                                                       EFFECTIVE:  June 1, 1984

                                                                   LINE NUMBER

Definition?  LINE NUMBER  is used  by  the computer  to distinguish one  comment
             line from another.
 Retrieval
 Abbreviation
                     Valid Values:

                     0 through 9, A and B
 Type
 Card
 Columns
   20
 Data Element
 Length
 Data
 *~
 Type
NUMERIC
Justified
Required on
New Entry
Nationally yfs
Controlled
Masterfile
Record Type
Masterfile
position
Masterfile
Length
21, 35,
21
1
47


 Edit Error Messages:

  ***LINE NUMBER MUST BE NUMERIC
 *** - Fatal Error	
                         Warning Error
 Coding Considerations;

   Assign line numbers sequentially.   Before  assigning  a  line number, refer to
   the source data report to be sure the number you code  is  not already on the
   date  base for  that  particular  emission  point.   Although  Line  Number  is
   carried on the masterfile, it is not a retrievable data element.

   Line Number A and B on Card  Code 4 have  been  set aside  for  mailing label
   information.   There  are  special  coding  sheets  available  for  entering
   mailing labels.
                              CDS DATA DICTIONARY

                                      G-l

-------
                                                       EFFECTIVE:  June  1, 1984

                                                                     COMMENTS

Definition;  COMMENTS can be  used to place on the CDS  masterfile  data which
             does not fit into any fixed card  format.
 Retrieval
 Abbreviation
Card
Type
Card
Columns
4, 6, 8
21-79
                 Valid values:
                 All  alphanumeric values.
 Data Element
 Length
59
Data
Type
Justified
Required on
New Entry
Nationally
Controlled
ALPHANUMERIC

NO
NO

Masterfile
Record Type
Masterfile
Position
Masterfile
Length

21, 35, 47
22-80
59
 Edit Error Messages:
 *** = Fatal Error
                      Warning Error
 Coding Considerations;

   All  comments can  be retrieved  on a  Source  Data  Report,  and only  action
   comments can be retreived on an  Action Summary  Report.   Any or all comments
   may be retrieved oh a Quick Look Report.

   Use:  Card 4 for a source comment;
         Card 6 for a point comment;
         Card 8 for an action comment.

   Do  not  use comment  records  to  carry  enforcement  action information  or
   compliance  status  information;  other  card types  are  available   for  these
   purposes.
                              CDS DATA DICTIONARY

                                      G-2

-------
                                   TECHNICAL REPORT DATA
                            (Please read instructions on the reverse before completing)
1. REPORT NO.
  EPA 340/1-84-003
                              2.
                                                            3. RECIPIENT'S ACCESSION NO.
4. TITLE AND SUBTITLE
                                                            5. REPORT DATE
                                                              September 1984
                                                            6. PERFORMING ORGANIZATION CODE
  Compliance  Data  System User's Guide
7. AUTHOR(S)
  Mr. Robert  Bowers
  Mr. Chris Mason
                                                            8. PERFORMING ORGANIZATION REPORT NO.
9. PERFORMING ORGANIZATION NAME AND ADDRESS

  The Research  Corporation of New  England
  800 Connecticut  Blvd.
  East Hartford,  Conn.  06108
                                                            10. PROGRAM ELEMENT NO.
             11. CONTRACT/GRANT NO.
                                                                68-01-4145
12. SPONSORING AGENCY NAME AND ADDRESS
  Stationary Source Compliance Division
  Office of Air  and Radiation
  U.S. Environmental  Protection Agency
  Washington,  D.C.   20460
              13. TYPE OF REPORT AND PERIOD COVERED
             14. SPONSORING AGENCY CODE
15. SUPPLEMENTARY NOTES
  A user's guide  describing the Quality Assurance of and  specific procedures to  be
  utilized by  operators of the Compliance Data System.
16. ABSTRACT
  This Compliance  Data System (CDS)  Quality Assurance Manual  is  designed to be the
  primary source of user documentation  regarding CDS.

  This manual.provides four services  to the CDS data manager.  :First:it serves as a
  quick-reference  user's guide for data entry.   It contains  instructions and defini-
  tions for all  CDS data elements.   Second, it  provides an outline for effective data
  entry procedures.  This outline helps to ensure not only that  data is correct before
  it  enters  CDS,  but that it is checked for accuracy all during the edit and update
  processes.   Third,  this manual explains several methods of checking existing data on
  CDS and provides a  step-by-step approach for  analyzing and correcting erroneous data.
  Finally, this manual contains a list  of references and sources of information which
  can help the data manager in the search for accurate, reliable data.  The manual
  contains a  complete review of CDS  communications documents and user assistance staff
  available to supply helpful information on all capabilities  of CDS.  In short, the
  CDS Quality Assurance Manual is designed to be an easy reference guide to help the
  CDS data manager maintain data reliability.
17.
                                KEY WORDS AND DOCUMENT ANALYSIS
                  DESCRIPTORS
                                              b.IDENTIFIERS/OPEN ENDED TERMS C.  COSATI Field/Group
  Air Pollution  Facilities (Sources)
  Compliance Status
  Enforcement Actions
  Surveillance Actions
     13  B
18. DISTRIBUTION STATEMENT


  Release Unlimited
19. SECURITY CLASS (This Report)
                                                                          21. NO. OF PAGES
20. STECu'RlTY" tLASS~(This page!
  Unclassified
22. PRICE

    \
EPA Form 2220-1 (Rev. 4-77)   PREVIOUS EDITION is OBSOLETE
                                                             .•U.S. COVEKHXSHr fURTIBC OFFICE: 1984—739—002/13,504

-------
  United States                              Office of Air Quality Planning and Standards
  Environmental Protection                    Stationary Source Compliance Division
  Agency                                    Washington DC 20460
Official Business
Penalty for Private Use
S300
                                                                         If your address is incorrect, please change on the above label;
                                                                         tear off; and return to the above address.
                                                                         If you do not desire to continue receiving this technical report
                                                                         series.  CHECK HERE D ; tear off label; and return it to the
                                                                         above address.

-------