BACT/LAER INFORMATION SYSTEM
CBLIS) USER'S MANUAL
FOR THE IBM 3090
by
PEI Associates, Inc. '
505 South Duke Street, Suite 503
Durham, North Carolina 27701-3196
Contract No. 68-02-4394
Work Assignment No. 6
PN 3759-6
Project Manager
Fred Dimmick
EMISSION STANDARDS AND ENGINEERING DIVISION
OFFICE OF AIR QUALITY PLANNING AND STANDARDS
U.S. ENVIRONMENTAL PROTECTION AGENCY
RESEARCH TRIANGLE PARK, NORTH CAROLINA 27711
April 1988
-------
DISCLAIMER
This report was prepared for the U.S. Environmental Protection Agency by
PEI Associates, Inc., Cincinnati, Ohio, under Contract No. 68-02-4394, Work
Assignment No. 6. The contents of this report are reproduced herein as re-
ceived from the contractor. The opinions, findings, and conclusions expressed
are those of the author and not necessarily those of the U.S. Environmental
Protection Agency.
-------
CONTENTS
_ . i u
Figures .
Tables lv
Acknowledgment v
1. Introduction 1
2. Information in BLIS 5
Organization of BLIS data 5
Level 0 data • 5
Level 1 data H
Level 2 data 12
3. Gaining Access to BLIS
14
Getting registered for the IBM 3090 14
Means of access to IBM 15
Telecommunications procedures 16
Using crosstalk on an IBM PC 21
Using System 2000 (S2K} language 23
4. Printing Output 30.
Obtaining copies of standard tables 30
Creating printed tables 32
5. Submitting Data to BLIS 40
Submitting BACT/LAER determination forms 40
"Computerized BACT/LAER determination report 42
Appendices
A. Source Type Names and Codes 46
B. Abbreviations for Process, Capacity, and Emission Units . . 51
C. Sample Form N258 - EPA ADP IBM, LMF, Sperry, and VAX
Account and User Registration 55
D. Contents of Crosstalk File IBM-TSO.XTK 58
E. Annotated Example of a Terminal Session 59
F. Example of Printed Tables Using LIST Command 66
G. References for Further Assistance 68
H. Blank BACT/LAER Determination Form 70
I. EPA Regional Office Bin Number Assignments 72
m
-------
FIGURES
Number Page
1 Relationship between BLIS records . . 6
2 An example of establishing communications with IBM
through TYMNET 17
3 Crosstalk status screen showing settings from a standard
file 22
4 Crosstalk status screen showing settings from file
IBM-TSO.XTK 24
5 ISPF/PDF primary option menu 33
6 ISPF-EDIT entry panel . 33
7 Copy of JSECONS.BLIS.BATCH tEXAMPLE) 35
8 BACT/LAER determination form 41
TABLES
Number Page
1 Numbers, Names, and Characteristics of BLIS Data
Components „ 7
2 Two-Letter State Abbreviations 10
3 Hypothetical Example of Computerized BACT/LAER Deter-
mination Report 44
iv
-------
ACKNOWLEDGMENT
This report was prepared for the U.S. Environmental Protection Agency
(EPA) by PEI Associates, Inc., Cincinnati, Ohio. Mr. Fred Gimmick was the
EPA Project Manager. Mr. David Dunbar served as the Project Director and
Mr. Joe Steigerwald was the Project Manager. The principal authors were
Mr. Joe Steigerwald and Mr. Roy Paul.
-------
SECTION 1
INTRODUCTION
The Clean Air Act C the Act) of 1970 gave the U.S. Environmental Protec-
tion Agency (EPA) the responsibility and authority to control air pollution
in the United States and its territories. One of the responsibilities given
to EPA under Section 108 of the Act is to publish information on air pollution
control techniques. This includes, among other things, data on available
technology and alternate methods of prevention and control of air pollution.
Section 110 of the Act requires States to adopt and submit to EPA their
State Implementation Plans CSIP's) for attaining and maintaining the National
Ambient Air Quality Standards (.NAAQS) in all regions of the State. Each
State, therefore, must decide which existing emission sources should be con-
trolled and to what extent. Quite often this existing source control repre-
sents Reasonably Available Control Technology (RACT).
Section 111 of the Act gives EPA the authority to establish performance
standards at a national level that apply to both new and modified sources.
New Source Performance Standards CNSPS) must reflect the degree of emission
reduction achievable through the application of the best system of continuous
emission reduction (.taking into consideration the cost of achieving such
emission reduction; any nonair quality, health, and environmental impact; and
energy requirements) that the EPA Administrator determines has been adequately
demonstrated for a source category.
The Clean Air Act Amendments of 1977 gave EPA some additional authority
and requires that certain control technologies be imposed by the States in
given situations. Section 165 requires that no major stationary sources may
be constructed in an area subject to the Prevention of Significant Deteriora-
tion (PSD) requirements unless the source is subject to Best Available Control
Technology (BACT) for each pollutant subject to regulation under the Act.
Best Available Control Technology means an emission limitation based on the
maximum degree of reduction of each pollutant subject to regulation under the
Act and applies to emissions resulting from any major sources that the permitting
-------
authority determines is achievable on a case-by-case basis (taking into ac-
count energy, environmental, and economic impacts, and other costs). In no
event shall the application of BACT result in emissions of any pollutants in
excess of the emissions allowed by any applicable NSPS.
Section 172 states that each SIP for an area that does not currently
attain NAAQS must require, among other things, permits for the construction
and operation of new or modified stationary sources. One of the stipulations
that must be met before permits to construct may be issued is that the pro-
posed new source complies with the Lowest Achievable Emission Rate (LAER).
The LAER for any source refers to the emission rate that reflects the most
stringent emission limitation contained in any SIP for such class or category
of source (unless the source demonstrates that such limitations are not achiev-
able) or the most stringent emission limitation that is achieved by such class
or category of source, whichever is more stringent. In no event shall the
emission limitation be less stringent than that stipulated in an applicable
NSPS for that source or source category.
Although the specific criteria governing BACT, LAER, or NSPS vary, the
general underlying approach is to require "best control" on all major new
or modified sources. Because the complexity and workload of making new
source review (NSR) decisions has increased over the past several years and
more State and local programs are accepting the complete responsibility for
issuing PSD and nonattainment permits, it is extremely important that infor-
mation be provided to assist control agencies in making the necessary control
technology determinations in a nationally consistent manner. The BACT/LAER
Clearinghouse was established to assist State and local air pollution con-
trol agencies in making control technology determinations and in sharing
control technology information.
The basic purposes of the BACT/LAER Clearinghouse are 1) to provide
State and local agencies with current control technology determinations,
2) to summarize recent determinations for sources of a similar size and nature,
and 3) to provide data on the specific emission limits imposed on new or
modified sources across the country. The information contained in the clear-
inghouse represents an abstract of control technology determinations made by
EPA Regional Offices and State and local agencies. The information contained
-------
in the clearinghouse is intended to serve as a reference or a starting point
for State and local agencies when making BACT/LAER determinations.
Initially, the BACT/LAER Clearinghouse was a manual system, and EPA
Regional Offices and State and local agencies submitted summaries of their
determinations to the Control Programs Development Division (CPDD). The CPDD
then categorized the determinations by source type or category and compiled
and duplicated the determinations for periodic transmittal to the State and
local agencies.
.Subsequent meetings and discussions with several State and local agencies,
EPA Regional Offices, and representatives of the Association of Local Air
Pollution Control Officials CALAPCO) and the State and Territorial Air Pollu-
tion Program Administrators CSTAPPA) resulted in the development of an automated
system to provide more rapid and up-to-date information regarding BACT and LAER
determinations. This automated system called for the creation of the BACT/LAER
Information System (BLIS), a data base system that performs the following
three functions:
1. Allows rapid updating of BACT/LAER determinations.
2. Allows more rapid production of BACT/LAER Clearinghouse reports.
3. Allows EPA Regional Offices (RO's) and State and local agency repre-
sentatives to have more direct computer access to the data in the
BACT/LAER Clearinghouse.
With these objectives in mind, a data base software system called System
2000 was put to use. Originally, a central EPA computer, the UNIVAC 1100,
was chosen to house the BLIS data base and to provide access to EPA RO's and
State and local agencies. In 1986, however, EPA decided to transfer all of
its computer usage and applications to the IBM 3090 computer system located at
the National Computer Center CNCC). This decision necessitated the transfer
of the BACT/LAER Clearinghouse from the UNIVAC to the IBM computer system, where
the System 2000 software was also available. The System 2000 software program
allows the various agencies to access BACT/LAER information from remote lo-
cations by the use of short, simple commands. Computer programming languages
such as FORTRAN, COBOL, etc., are not necessary to access data from BLIS.
The purpose of this manual is to explain how to access BLIS and how to
write lists, tables, and reports with a minimum effort. Users with more
-------
sophisticated BLIS needs are referred to other sources of information for
advanced instructions that go beyond what is provided in this manual.
Section 2 describes the data stored in BLIS and the organization of these
data. Section 3 instructs the user in how to gain access to BLIS. Section 4
lists the procedures for obtaining printed reports, and Section 5 instructs
the user on data submission.
-------
SECTION 2
INFORMATION IN BLIS
The primary product of the BACT/LAER Clearinghouse is a report of infor-
mation that has been obtained from BACT/LAER determinations made by various
control agencies. The report contains information on source size and type;
the name and location of the company that applied for the construction permit;
whether the determination was for BACT or LAER; pertinent source operating
parameters such as capacity, pollutant emission rates, and control technology;
and the name of a control agency person who can be contacted for further
information.
2.1 ORGANIZATION OF BLIS DATA
Information in the BLIS data base is organized in a manner similar to a
file drawer, where dividers are used to group records under major and minor
headings. System 2000 software permits this kind of grouping.- The major
heading is the industrial plant tsource), and the major record under this
heading contains information about the source, such as company name, address,
and agency contact person.
The first minor record concerns the permitted process within the source.
A process may be a unit such as a boiler, a heater, or a liquid storage tank.
One source may have many process units and associated process records. A
record for any one process contains information such as process description
and throughput capacity.
The second minor record concerns the pollutant emitted from each process.
This record contains information such as applicable emission limits and the
kind of control equipment used to control the given pollutant. In System 2000
terminology, the source record is Level 0, the process record is Level 1, and
the pollutant record is Level 2 CFigure 1 shows the relationship between these
levels). Because each record branches into subsidiary records, one record and
its subsidiaries are said to comprise a "tree." The following sections describe
the data items within each record (Levels 0, 1, and 2).
-------
LEVEL 0
LEVEL 1
LEVEL 2
Figure 1. Relationship between BLIS records.
2.2 LEVEL 0 DATA
Table 1 lists the name and number of each data component stored in the
BLIS data base. The first component at Level 0 is "ID number." The notation
"char X(7)" indicates that the component may consist of up to seven of any
typewriter keyboard character A to Z, 1 to 9, or special characters (e.g., ?,
!, or blank). By convention, ID numbers consist of a two-character initial
for the State, followed by a dash, followed by a four-digit integer assigned
by the BACT/LAER Clearinghouse. For example, ID number OH-0012 identifies
the twelfth data entry (.source record) received from the State of Ohio. Be-
cause each ID number is unique, it provides a short reference name for acces-
sing a particular source record and its subsidiary records.
The next two data components or items are the Source Type Code and the
Source Type Name, component numbers 2 and 3, respectively. Standardized
source type codes were developed after studying the classes of industries
currently being permitted. The source type code consists of a two-digit major
classification code followed by a period, followed by a minor classification
-------
TABLE 1. NUMBERS, NAMES, AND CHARACTERISTICS OF BLIS DATA COMPONENTS
Component
number
1
2
3
4
5
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
32
33
34
35
36
Component description
ID number
Source type code
Source type name
Source size
Source size units
Company name
Address
City
County
State initials
Zip code
EPA region
BACT/LAER determ.
New/modi f i ed
Date permit issued
Permit number
Region file number
Estimated startup date
Agency name
Agency contact person
Agency phone number
Notes
Notes continued
Code 1
Code 2
ID suffix
Last data entry
Initial review
Initial return
Post startup review
Post startup return
Component
characteristics or format
Char X(5)
Char X(7)
Char X(50)
Decimal number
9(10). 99
Char X(20)
Char X(50)
Char X(30)
Char X(30)
Char X(30)
Char X(2)
Char X(5)
Char X(2)
Char X(4)
CHAR X(8)
Date3
Char X(30)
Char X(20)
Datea
Char X(40)
Char X(30)
Char X(20)
Char X(250)
Char X(250)
Integer 99
Integer 99
Char X(2)
Date3
Date3
Date3
Date3
Date3
(continued)
-------
TABLE 1 (continued)
Component
number
100
101
102
103
104
105
200
201
202
203
204
205
206
207
208
209
210
Component description
Permitted Process
Process type code
Name of process
Throughput capacity
Throughput units
SORT code TBL2A
Pollutant
Pollutant name
Emission limit
Emission units
Alternate limit
Alternate units
Basis for limits
Control equipment
Process modification
Percent efficiency
CAS number
Component
characteristics or format
Record
Char X(5)
Char X(50)
Decimal number
9 (10). 99
Char X(20)
Decimal number
9(10). 99
Record
Char X(20)
Decimal number
9(8). 9999
Char X(20)
Decimal number
9(8). 9999
Char X(20)
Char X(4)
Char X(50)
Char X(50)
Decimal number
999.999
Char X(10)
code. For example, source type code 6.52 contains major code "6" (indicating
chemical process industry) and minor code "52" (Indicating sulfur recovery).
The source type names are standardized to facilitate coding. A full listing
of standard source type names and codes is presented in Appendix A.
The next two components, numbers 4 and 5, are source size and source size
units. Source size is stored in the computer as a number that permits arithme-
tic operations such as sums and standard deviations to be carried out on these
data. [The notation "9(.10).99" indicates the maximum size number that can be
8
-------
stored: 10 digits before the decimal and 2 digits after the decimal. The
smallest number possible is 0.01 and the largest is 9,999,999,999.99.]
Source size units may be T/YR (tons/yr) or some other measure of source size.
Because it is often useful to compare information for sources of similar
size, standard abbreviations for source size units have been adopted for SLIS.
Appendix B lists standard abbreviations for source size units. Note: Standard
abbreviations are different from standardized units; therefore, the engineer
submitting data to BUS may use any units that he/she considers appropriate.
Component number 10 is Company Name. Although the maximum size company
name is 50 characters, many company names in BUS have been shortened by using
common abbreviations known throughout the United States. For example, company
may be shortened to Co., and corporation may be abbreviated to Corp; however,
"ut." is not substituted for utilities because it is not widely used. Short
names are desirable because printed tables often have limited space, which
results in the truncation of long names.
The address of the source is composed of a number of individual data
items. Component number 11, address is primarily intended for the street
address, such as 1728 Prospect St; however, a post office box is sometimes
used. If the source is an electric utility, the Address component is an ap-
propriate place for the name of the generating plant, e.g., Big Island Gener-
ating Plant. City and County (where applicable) are separate components,
numbers 12 and 13. For consistency, city and county are spelled out in full.
Component number 14, State Initials, is two characters in length and uses the
standard State abbreviations developed by the U.S. Postal Service. Table 2
lists these two-letter abbreviations. The zip codes in Component number 15,
contain only 5 digits; they do not include the new zip code suffixes. Compon-
ent number 16, EPA Region, is a two-digit character component that may have
values "1" to "10."
Component number 17, BACT/LAER Determ., is the level of technology that
best characterizes the determination for the entire source and its processes.
This component may indicate "BACT," "LAER," "RACT", "NSPS", or simply "blank"
if no determination was made for the whole source. Component 18 indicates
whether the determination is for a new or modified source. Component number 19,
Date Permit Issued, is described as a "Date." It is composed of three 2-digit
integers indicating month, day, and year (e.g., 08/21/81). Component 20, Permit
-------
TABLE 2. TWO-LETTER STATE ABBREVIATIONS
Alabama
Alaska
American Samoa
Arizona
Arkansas
Cal ifornia
Canal Zone
Colorado
Connecticut
Delaware
District of Columbia
Florida
Georgia
Guam
Hawa i i
Idaho
Illinois
Indiana
Iowa
Kansas
Kentucky
Louisiana
Maine
Maryland
Massachusetts
Michigan
Minnesota
Mississippi
AL
AK
AS
AZ
AR
CA
CZ
CO
CT
DE
DC
FL
GA
GU
HI
ID
IL.
IN
IA
KS
KY
LA
ME
MD
MA
MI
MN
MS
Missouri
Montana
Nebraska
Nevada
New Hampshire
New Jersey
New Mexico
New York
North Carolina
North Dakota
Ohio
Oklahoma
Oregon
Pennsylvania
Puerto Rico
Rhode Island
South Carolina
South Dakota
Tennessee
Texas
Utah
Vermont
Virginia
Virgin Islands
Washington
West Virginia
Wisconsin
Wyoming
MO
MT
NE
NV
NH
NJ
NM
NY
NC
ND
OH
OK
OR
PA
PR
RI
SC
SD
TN
TX
UT
VT
VA
VI
WA
WV
WI
WY
Number, provides up to 30 characters to accommodate any permit numbering
system used by a State or local agency. Component 21, Region File Number, is
a number or code used by an EPA Regional Office to identify a particular
source. This number may be used when the permit number is not available.
Component 22, Estimated Startup Date, is a date item and must have a number
for month, day, and year Ulthough only the year is printed in the detailed
listing).
Component number 23, Agency Name, identifies the agency that submitted
the information to BLIS or the agency of the contact person. Components 24
and 25, Agency Contact Person and Telephone Number, are important items to
the BACT/LAER Clearinghouse. Telephone numbers are placed in a standard
format, beginning with the area code, e.g., C999)-888-7777.
Component numbers 26 and 27, Notes and Notes Continued, provide up to 250
characters each. These notes provide additional information or clarify other
10
-------
data items. Two components are required for notes because the System 2000
software limits any one data item to 250 characters.
Component numbers 28 and 29, Code 1 and Code 2, are integers that
are used to allow BLIS data to be listed in numerical order of source code.
Component number 30, ID Suffix, is a letter code used when more than one
determination is submitted by the same facility or when a determination is sub-
mitted by a facility already in the BACT/LAER Clearinghouse. The second de-
termination submitted by a specific plant is denoted by an "A"; the tnird by a
"B" and so on.
Component numbers 32 through 36 are dates used in tracking the determina-
tions through initial entry and quality assurance procedures. Component num-
ber 32, Last Data Entry represents the date the determination was first
entered into the system. Component numbers 33 and 34 represent the dates the
determination was returned to the submitting agency for quality assurance and
the date the submitting agency returned the determination to EPA for correction,
Component numbers 35 and 36 are similar to numbers 33 and 34 but these dates
represent a post-startup review process.
2.3 LEVEL 1 DATA
As indicated in Table 1, the first subsidiary record' at Level 1 has five
components. This record may be referenced by its name, Permitted Process, or
its identification number, "100." As explained in a later section, all data
in this record and all data in subsidiary records may be called out (and
printed out) by naming the record identification number.
Component number 101, Process Type Code, has characteristics identical to
those of the source type code. In fact, the source type codes listed in
Appendix A are also used as process type codes. Both codes are needed, how-
ever, because the type of process permitted may be different from the type of
source. For example, a vinyl chloride plant (source type code 6.59) may con-
tain an oil-burning industrial boiler (process type code 1.2). Currently,
process type codes only provide for external combustion processes such as
boilers.
11
-------
Component number 102, Name of Process, Is the name given the process by
the submitting agency. The format of this entr: is:
Equipment type, modifers, fuel usage, number of units
For example, four coal firing fluidized-bed combuster (FBC) boilers would be
coded as:
Boiler, FBC, coal-fired, 4
Component number 103, Throughput Capacity, and Component number 104, Throughput
Units, are analogous to components for source size and source size units.
Throughput capacity refers to the capacity of a particular process, whereas
source size refers to the capacity of all processes combined. If a source
i
were to contain only one process, source size and throughput capacity could be
the same. Component number 105, the Sort code TBL2A, represents the throughput
capacity of each industrial boiler in MM Btu/h and is calculated using the in-
formation provided by the submitting agency. This component is not printed in
any output table, but it is used to order the boilers in output Table 2A within
each source category.
2.4 LEVEL 2 DATA
As indicated in Table 1, there are 10 components in the second subsidiary
record has 10 components. This record may be identified by its name, Pollutant,
or its identification number, "200." Each process record contains one pollutant
record for each pollutant that'is emitted.
Component number 201, Pollutant Name, may have up to 20 characters to
spell out pollutant or chemical names. Standard abbreviations are used for the
most common pollutants Ce.g., CO, NOX, PM, PM1Q, S02, and VOC); chemical
names should be used for all other pollutants. Note that HC (hydrocarbons) is
replaced by the term VOC (volatile organic compounds) to indicate more spe-
cifically those hydrocarbons that are subject to regulation. Note also that
numeral "2" in S02 is a normal 2 rather than subscript 2 because most terminals
and printers do not print subscripts.
Component number 202, Emission Limits, and Component number 203, Emission
Units, are items of special interest in the BLIS data base. Because some
agencies use multiple expressions of emission limits, the next two items,
12
-------
Component numbers 204 and 205, are Alternate Limits and Alternate Units (i.e.,
alternate emission limits and alternate emission limit units). The standard
abbreviations listed in Appendix B also apply to emission units and alternate
units. When several processes have the same emission limits, just one record
200 may be used. For example, an emission limit and emission unit may be "1.3
Ib/MMBTU EA," which means that each individual process (named in data item
102) has an emission limit of 1.3 Ib per million Btu for this pollutant
(named in component 201).
Component number 206, Basis for Limits, uses the same terminology as
Component number 17, BACT/LAER Determ. Although Component number 17 is a
determination for the source as a whole, the determinations for a particular
process and a particular pollutant may be different. For example, a source
might consist of five different industrial processes that, as a whole, are
classified "BACT" for data item 17. One or more of the processes could,
however, emit a pollutant that would be subject to the new source review non-
attainment requirements. For this one pollutant, the emission limit would
be classified as "LAER" in data item 206.
Component numbers 207 and 208, Control Equipment and Process Modifica-
tion, are names of processes and equipment that make up the control technology
for a particular process and a particular pollutant. Electrostatic precipi-
tators (.ESP's) and. cyclones are examples of control equipment. The use of
2 percent sulfur fuel to control S02 is an example of a process modification.
If names of equipment or processes exceed the 50 characters allowed for them,
reference can be given to notes (.Component numbers 26 and 27), which describe
the equipment or process in more detail.
Component number 209, Percent Efficiency indicates the efficiency of the
specified control equipment or process modification for a particular pollutant
emitted from a particular process. If a range of control efficiencies is
given or several pieces of equipment are listed and each is associated with a
different efficiency, the maximum percent efficiency for that pollutant should
be inserted into component number 209.
Component number 210, CAS Number, is the final component. This component
lists the Chemical Abstract Service (CAS) registry number of the pollutant (if
one exists and if the pollutant name is specific enough for a CAS number to be
assigned).
13
-------
-------
SECTION 3
GAINING ACCESS TO BLIS
Use of the BLIS data base involves using a computer terminal to connect
to the IBM 3090 computer at the EPA National Computer Center (NCC). Simple
commands will cause the needed information to be printed on the terminal
screen. Although performing this task is easy for an experienced user, the
beginner must take a number of preliminary steps.
3.1 GETTING REGISTERED FOR THE IBM 3090
Currently, the BLIS data base is available on the IBM 3090 computer lo-
cated at NCC, Research Triangle Park, North Carolina. Each new user must
obtain a user ID and an account number to gain access to this computer. Many
potential users may already have a user ID and an account number because they
are participating in the National Air Toxics Information Clearinghouse (NATICH).
Users who already have these items and know how to use them at their own termi-
nals may proceed immediately to Subsection 3.4. Note: Account numbers and
passwords for other EPA computers will not work on IBM.
Registration for the IBM computer at NCC involves a certain amount of
program planning and financial accounting. Information required by NCC is
submitted on EPA Form N258, whether or not the new user is an EPA employee.
A sample Form N258 is included in Appendix C.
For EPA users, the form is signed and submitted by the Automatic Data Pro-
cessing (ADP) Coordinator of your EPA organization and sent to the Time Sharing
Services Management System (TSSMS) Office at the addresses shown on the form.
Non-EPA users must be in an organization that has established an Inter-
agency Agreement (IAG) with EPA. If the IAG is with a Regional Organization
(RO), the form is submitted to one of the following 10 regional ADP Coordinat-
ors:
1. Mike MacDougall (617) 565-3377
2. Robert Messina (212) 264-9850
3. A.J. Hamilton (215) 597-8046
4. Clifford R. Davis (404) 347-2316
14
-------
5. Stephen Goranson (312) 353-2306
6. David White (214) 767-6540
7. Paul Hirth (913) 236-2827
8- Al Vigil (303) 293-1423
9. David Jones (415) 454-9551
10. James Peterson (206) 442-2977
If the central office of EPA is handling the IAG, Linda Garrison, EPA PM-211M,
WSM, 401 M Street, S.W., Washington, D.C. 20460, at (202) 382-2405 or (FTS)
382-2405, should be contacted.
When the request has been approved by TSSMS, the new user will be sent a
personal letter containing his or her account number and user ID.
3.2 MEANS OF ACCESS TO IBM
The IBM computer at NCC may be accessed from anywhere in the United States
through a computer terminal, a modem, and a telephone. Most computer terminals
sold in the United States are compatible with the IBM system, and many micro-
computers have programs that allow them to be used as low-speed terminals.
Also many word processors (e.g., IBM Display Writer, Lexitron, or Wang) can be
used as low-speed terminals. If one of these types of terminals is available,
it can be used to access the BLIS data base. The vendor can be contacted to
find out whether a particular terminal requires any adaptations or modifica-
tions. If a new terminal is to be purchased, it would be wise to ensure that
it does not have to be modified to communicate with IBM.
In addition to a terminal, a modem is also required. This device receives
messages over telephone lines from the computer and converts them into codes
that a terminal uses to create words on the cathode ray tube (CRT): It also
converts messages from the terminal into electrical patterns, which are sent
back to the computer over the telephone line. An acoustical modem receives
messages as sounds through a standard telephone receiver. An electrical modem
bypasses the telephone receiver and receives electrical impulses directly from
the telephone line.
Modems commonly available from computer stores operate at relatively low
transmission rates (300, 1200, or 2400 bps). If a user needs the IBM computer
at NCC for other applications besides BLIS (e.g., running dispersion models,
creating graphical displays, or developing programs), a high-speed (9600 bps
or higher) communications system is recommended to make more efficient use of
15
-------
full-screen editing, dialogue management, and rapid exchange of data at re-
mote locations. High-speed communications require an IBM 3270 or equivalent
type terminal, a special high-speed telephone line, an IBM 3470 series cluster
controller or equivalent, and high-speed modems. Establishment of such an
"interactive" terminal system requires authorization from the National Data
Processing Division (.NDPD) of EPA. A user interested in establishing a high-
speed system should contact the Telecommunications Network Support Group at
(FTS) 629-3182 or (.919) 541-3182. Because low-speed transmission is sufficient
for most BLIS users, this type of transmission is assumed in this manual.
To determine whether a terminal is compatible with IBM (for low-speed
transmissions), the vendor will require certain technical data about the IBM
system, e.g., that communications are coded ASCII, are asynchronous, and use 8
bit words. One of these bits is a parity bit, and there are 7 bits per character,
»
Parity is even, and there is one stop bit. Communications are in half-duplex,
and a carriage-return signal is sent to the terminal after each signal is trans-
mitted. For additional data concerning the IBM computer, the user should call
Telecommunications at NCC, phone (919) 541-4506 or CFTS) 629-4506.
3.3 TELECOMMUNICATIONS PROCEDURES
The EPA uses a special telephone service to connect computers to users at
low-speed terminals. This service consists of a telephone network supplied by
a contractor, TYMNET . TYMNET serves computers and terminals at many govern-
ment agencies and businesses located throughout the world.
To communicate with IBM, the user must first connect into TYMNET. Each
city has a local telephone number that allows a user to connect to a distant
computer with no long distance fee. The currently available telephone number
for your city or town can be obtained by calling NCC Network Control Facility
at (800) 334-0741 or CFTS) 629-4506. Users should also use this number to
report any communications problems they may encounter.
To communicate with the IBM 3090 at NCC, the user should first make sure
that his/her terminal or PC is set to the correct communication parameters
(even parity, 7-bit word length, 1 stop bit, etc.) and then begin carrying out
the following procedure, using the example in Figure 2 as a guide.
16
-------
xxx^xase type your terminal identifierA
-2613-010-
please log in: EEPAPA11
p 13
NODE 3157 HOST 1038: EPA IS ON LINE
Welcome to the Environmental Protection Agency National Computer Center
Please enter one of the following selections:
IBM for IBM
UNI for SPERRY
TCP for 3270 EMULATION
FMO for FMO POP
VAX for VAX
PRIME for PRIME
Enter selection:ibmpsi
i
Connected.
connected 310600908827/100508
U.S. EPA (TTY-X25-IBM)
A TSO - NCC
B NY
C NEIC
D WIC
N Chicago
SELECTION ?A
IKJ56700A ENTER USERID -
USR
ICH70001I USR LAST ACCESS AT 13:12:14 ON TUESDAY, FEBRUARY 9, 1988
IKJ56700A ENTER ACCOUNT NUMBER -
acct
IKJ56700A ENTER PROCEDURE NAME -
$epatso
IKJ56455I RPB LOGON IN PROGRESS AT 13:15:26 ON FEBRUARY 9, 1988
01/25/88: THE NCC-IBM 3090 AVAILABILITY SCHEDULE - SEE NEWS ALERT1
02/01/88: SAS EXPIRATION WARNING 341 - SEE NEWS ALERT2
ENTER FIMAS ID -
blisp
READY
Figure 2. An example of establishing communications with IBM
through TYMNET.
17
-------
1. From your terminal/PC, dial your local TYMNET access number. You
will receive the message "Please type your terminal identifier".
This message is frequently garbled or even illegible, because
TYMNET does not yet know the kind of equipment with which it is
communicating with.
2. Type the character "a" to tell TYMNET the type of terminal you
are using. [If "a" does not work, call the Network Control
Facility at (800) 334-0741 or (FTS) 629-4506.]
3. The next statement is "Please log in:". This means that TYMNET
wants to know to what computer it should connect, as the TYMNET phone
system serves thousands of computers. The correct response is
EPA1 if your modem operates at 1200 baud or EPA2 if your model
operates at 2400 baud. TYMNET then connects you to the EPA com-
munications node for all EPA computers at NCC. Take note of the
node number (shown as NODE 3157 in Figure 2) because you may need
it if any problems emerge.
4. The next statement declares that you are connected to NCC and
asks for a computer selection. The correct response is "IBM".
After the word "connected" appears, press the carriage return
(CR) key. You are now connected to the IBM 3090.
5. The next statement is "enter TSO". This requests the user to se-
lect a software for communicating with the IBM system (there is
only one choice). Enter "TSO" and carriage-return (CR).
6. The IBM now prompts the user to log on with certain identification
and accounting codes,.by printing the statement "enter user ID",
where user ID is the user identification code obtained from the
TSSMS office.
7. The user is prompted for a password (a character string) estab-
lished by the user in a previous terminal session. A new user
establishes his password by entering
USR/USR/PASS
in which USR is the user ID and PASS is the new password.
8. The user is prompted for an account number. This is the four-
character code provided by the TSSMS Office, as described in Section
3.1. Enter account number and (CR).
9. The user is prompted for a procedure name. A correct response is
$EPATSO and (CR).
10. The system shows that a LOGON is taking place. Several one-line
bulletins may be shown at this time, and the user is prompted for
a "FIMAS ID". This prompt is sometimes hidden among the bulletins.
FIMAS is an abbreviation for Facility Impact Monitoring and Analy-
sis System. The FIMAS identifier is a code for classifying the type
of work taking place on IBM. A correct response to this prompt is
"BLISP" and (CR).
18
-------
After the ISO "READY" prompt is shown, the user is connected to
IBM and is ready to begin using the BLIS data base.
Users sometimes encounter problems establishing communications. Many
problems can be corrected by checking the following:
o FAST BUSY SIGNAL
A fast busy signal indicates a temporary overload in local tele-
phone circuits. Please try your call again. If this condition
persists, notify your local telephone company.
o SLOW BUSY SIGNAL
A slow busy signal is a normal telephone-station busy signal. It
indicates that the rotary group you are dialing has reached capa-
city. Hang up and try the number again in a few minutes. If this
condition persists, please report the problem.
o RING-NO-ANSWER
Check to see that you dialed the number correctly and then place
the call again. Please notify the Network Control Facility if
you have this problem while using the correct number.
o TONE-NO-RESPONSE
Before reporting this problem, check your terminal and coupler
switch settings, cable connections, and power-on settings to be
sure the -terminal is in the "on-line mode.
If the same equipment has been successfully used before in con-
junction with the same telephone access number, and if you can
dial other areas and log in, please report the problem.
o RANDOM "GARBAGE" CHARACTERS
The many possible sources of "garbage" characters include, for ex-
ample, the use of a telephone line that goes through a switch-
board, a noise source close to an acoustic coupler, or problems
in a modem, a terminal, telephone company hardware, or TYMNET
hardware. See the next section for troubleshooting procedures
related to your own equipment.
If you can use more than one local access telephone number to
connect to TYMNET, try to eliminate the garbage characters by
disconnecting from the network and then dialing a different
number from the one you used during your preceeding log in.
19
-------
The most important piece of information you can supply when you
report garbage characters is the number of the port with which you
connected when you first logged in. That number is the second of
the two numbers that appear in the line of hyphens and numbers that
TYMNET displays immediately af.ter you enter your terminal.
o DROPS (DISCONNECT/LOSS OF CARRIER)
Drops have the same kinds of causes and solutions as garbage
characters. If you cannot correct them, please report drops as
soon as possible after they occur. Be prepared to report whether
you received a message when you were dropped and, if so, what
that message was.
The telephone equipment you use with TYMNET can cause errors, disconnects,
and other problems. The following precautions are recommended:
o Use a telephone with a direct outside line, rather than going
through a switchboard.
o Be sure the telephone you use does not have an extension.
o If the quality of telephone service in your area is poor, you may
need to use a data set rather than an acoustic coupler.
o If you are using an acoustic coupler, keep it away from the ter-
minal if possible. If the coupler has a lid, keep it closed.
o Hang up the telephone when your terminal is not in use. (This can
prevent the telephone's speaker and receiver elements from crystal-
izing and decreasing signal strength.)
o Be sure that there is a piece of cotton baffling inside the ear-
piece behind the receiver in your telephone handset. (Most tele-
phone companies put cotton baffling in the earpiece before instal-
ling a telephone.)
o Be sure the terminal and modem have a circuit of their own.
•
o If error rates are a problem, try a different telephone handset.
(Transmitter and receiver elements in one handset may perform bet-
ter than in another.)
To report unmanageable communication problems, call NCC Network Control
Facility at one of the following numbers:
(919) 541-4506
(FTS) 629-4506
(800) 334-0741
20
-------
Compile the following information before calling to report a problem:
o The telephone access number in use (or to be used) and the
city and State in which that number is located.
o The type of terminal and modem or coupler in use.
o The speed and type of service in use (i.e., 300 bps, 1200 bps
Vadic, 1200 bps 212, 2400, etc.)
o The number of the port in the connection (if possible).
3.4 USING CROSSTALK ON AN IBM PC
One of the more common machines in business offices is the personal com-
puter. Because the IBM PC is the type most commonly used in EPA offices, this
section describes how to use a readily available software product, "Crosstalk",
to communicate with the IBM 3090 at NCC.
Crosstalk versions for either an IBM XT or an IBM AT model can be in-
stalled by following directions from the Crosstalk manual. This primarily
consists of copying files from the Crosstalk diskette to a hard disc or
making a backup copy of the diskette files. Many people place all Crosstalk
files in a special directory (usually called XTALK) to keep them separated
from other files on a hard disc. The file containing the executable program
has a name extension of EXE. Communication files containing communication
settings for a specific mainframe computer have a name extension of XTK.
Using Disc Operating System (DOS) commands, a user enters the XTALK dir-
ectory and executes the Crosstalk program as follows
> CD \XTALK
> XTALK
After a pause, a Crosstalk status screen is presented, as shown in Figure 3.
The first line after the heading shows the name of the program and the name
of the command file. File name STD.XTK has been placed into effect auto-
matically. All information on this screen is taken from this file. Other
command files (all files with extension XTK) are listed on the bottom line
with reference numbers and without file extensions.
21
-------
|_ CROSSTALK - XVI Status Screen »
NAme CROSSTALK defaults Hayes Smartmodem 2400 LOaded CrSTD.XTK
NUmber 5410700 CApture Off
1- Communications parameters » §• Filter settings »
*SPeed 2400 PArity Even DUplex Full DEbug Off LFauto Off
DAta 7 STop 1 EMulate VT-100 TAbex Off BLankex Off
POrt 1 MOde Call INfliter On OUtfiltr On
f. Key settings » | SEnd control settings --»
"ATten Esc COmmand ETX ("C) CWait None
SWitch Home BReak End LWait None
i Available command files -
1) IBM-TSO 2) NEWUSER 3) SETUP 4) STD
Enter number for file to use ( 1 - 4 ):
Figure 3. Crosstalk status screen showing settings from a standard file.
22
-------
Below the bottom line of the screen display is a panel for entering in-
structions to the Crosstalk program. The user is prompted for a file to use.
In this example, file 1, called IBM-ISO.XTK, already has all the necessary
settings for communicating with IBM. Entering T causes this file to take
effect. If the Status screen were rewritten by using this file, it would
appear as shown in Figure 4. (A complete list of settings from this file can
be found in Appendix D.) Note that a particular phone number is shown. A
different phone number will be usually required for your particular city,
including "1" and the area code, e.g., 18005551212. Also note that speed is
set as 2400-baud rate; if a 1200-baud modem is used, this setting should be
changed accordingly.
One of the commands in the IBM-ISO.XTK file is "GO". This causes the
telephone number to be dialed immediately upon putting this command file into
effect (e.g., when "1" is entered at the prompt for a file). When a connec-
tion is made with the NCC, the screen should clear. Press (CR) key and the
main menu for selecting a computer should appear. At this point, you should
follow the instructions for logging on the IBM computer as described in the
preceding section.
3.5 USING SYSTEM 2000 (S2K) LANGUAGE
The IBM 3090 uses an executive program to keep track of the activities
of hundreds of users, to bill them, and to carry out their orders. The
standard language used to communicate with the executive program is IBM's
Time Sharing Option (TSO). The only TSO command needed is
EXEC 'JSECON5.8LIS.CLIST(BLIS)' and (CR).
This should be entered exactly as stated here, including single quotes.
It is a command to execute (EXEC) a command list (CLIST) located within the
file that is named after the EXEC command. This CLIST will automatically al-
locate a number of different files needed for this BLIS data base by using
System 2000 (S2K) commands. After this point, the user will issue S2K commands
rather than TSO commands. At the end of this session the user will free the
data base files and issue one more TSO command, "LOGOFF", which will close files
and tally the computing bill for the user.
23
-------
CROSSTALK - XVI Status Screen
NAme CROSSTALK defaults Hayes Smartmodem 2400 LOaded C:IBM-TSO.XTK
NUmber 5410700 CApture Off
» I- Filter settings
| Communications parameters
SPeed 2400 PArity Even DUplex Half
DAta 7 STop 1 EMulate VT-100
POrt 1 MOde Call
1"
1) IBM-TSO
DEbug Off
TAbex Off
INfilter On
LFauto Off
BLankex Off
OUtfiltr On
ATten Esc
Switch Home
Key settings
COmmand ETX (AC)
BReak End
m SEnd control settings --»
CWait None
LWait None
2) NEWUSER
Available command files -
3) SETUP 4) STD
Command?
Figure 4. Crosstalk status screen showing settings from file IBM-TSO.XTK.
24
-------
The syntax of commands in S2K consists of verbs, modifiers., and objects
and always ends in a colon. If a colon is not used at the end of a command
line(s), the computer assumes that the command is continued on the next line.
If a statement is entered and nothing occurs, the colon may be missing. Be-
cause any number of extra blanks can be used between words, however, the omit-
ted colon can be entered on the next line and the command will be executed.
After issuing the EXEC 'JSECON5.BLIS.CLIST(BLIS)' command, the first S2K
command is a password statement, as follows:
USER, ANY:
The name of the user, ANY, is also the password to allow entry Into the S2K
program. With this password, a user can retrieve any data desired from
BLIS and can write tables, lists, and reports. ANY user, however, is not
authorized to change data or add data to the data base. Changing the data base
can introduce errors or even destroy a data file. Use of the password ANY pro-
vides protection both for the data base and for the user. After each S2K state-
ment, a message, a printout of data, or simply a line pointer will appear to
indicate that one statement has been received and S2K is ready for another.
The next S2K statement is as follows:
DATA BASE NAME IS BLIS: or DBN-IS BLIS: '
The S2K program will check to see if the password is authorized for the data
base. If it is, the user will be allowed access to the BLIS data base. If
the message "data base not available" is received, the data files are either
being updated or they are damaged. The user should exit the system by enter-
ing the command
EXIT:
and answer YES when asked if the data base files may be freed. The user may
then enter any valid TSO command or sign off the IBM system and should try
accessing the BLIS data base later. If the user continues to receive the
"data base not available" message, he/she should notify Fred Dimmick in the
Emission Standards Division USD) of the Office of Air Quality Planning and
Standards of the problem at (919) 541-5432 or (FTS) 629-5432.
Once the user is allowed access into the BLIS data base, the commands to
be issued depend on the requirements of the user and these commands will be de-
signed by the user. One of the simplest statements is the PRINT command, which
25
-------
causes data to be printed out on the screen. Table 1 can be used as a handy
menu of .data items that can be PRINT1ed. For example, the command
PRINT COMPANY NAME:
would cause the names of all companies in the data base to be printed on the
screen in a single column; however, because the data base currently has more
than 1400 entries, the user would have to wait a long time for all of the com-
pany names to appear. This is not an effective way to use the data base.
An effective way to view limited parts of the data base would be to use
a command to print only the data needed and only the amount of data that will
fit on a screen. If a long list of data is needed, it could be printed on
paper (see next section). An effective way to use the PRINT command is to
modify it with a WHERE clause. For example, the following command
PRINT COMPANY NAME WHERE STATE INITIALS EQ OH:
will -cause only companies in the State of Ohio to appear on the screen. In the
S2K syntax, the verb PRINT comes first, followed by the object (company name),
followed by a modifying (WHERE...) clause. Note that this statement is an
understandable English.
If the lines of data exceed the number that will comfortably fit on a
particular screen, the command should be further modified. Tor example, each
of the following statements should cause no more than 15 lines to be printed
at one time:
PRINT COMPANY NAME WHERE STATE INITIALS EQ OH AND ID NUMBER LT
OH-0016:
PRINT COMPANY NAME WHERE STATE INITIALS EQ OH AND ID NUMBER SPANS
OH-0016*OH-0032:
Note that LT is an abbreviation for "less than." By using similar key
words in the WHERE clause [AND, OR, LT, GT (greater than), EQ (equal to),
LE (less than or equal to), GE (greater than or equal to), and SPANS], the
user can retrieve just the information he/she desires and can leave the rest
of it in the data file.
For users that have an IBM PC that use Crosstalk software as a terminal,
the following is a convenient method for capturing data from the screen.
26
-------
First press the ESCAPE key. This causes the terminal session to be suspended
momentarily and the cursor positioned within the Crosstalk command panel.
Issue the following command to Crosstalk
CA FILE.DAT
where FILE is a name for a file to be created on the IBM PC to contain BLIS
from the screen and CA is short for CAPTURE. After this command, the terminal
session with the IBM 3090 is resumed automatically, and the cursor returns to
the main portion of the screen. Now enter a PRINT or LIST command to show
BLIS data on the screen. A duplicate of these data will be written into
FILE.DAT on the PC. To terminate writing to the file, press the ESCAPE key
and give the following command to Crosstalk
CA OFF
you can then resume the terminal session.
Long S2K commands can be cumbersome and error-prone. Commands may be
shortened by using data numbers (listed on Table 1) rather than data names.
When data numbers are used in a statement, they must be preceded by the letter
"C" (component). The word PRINT can be shortened to PR and WHERE, to WH.
The following commands are equivalent to those just given:
PR CIO WH C14 EQ OH AND Cl LT OH-0016:
PR CIO WH C14 EQ OH AND Cl SPANS OH-0016*OH-0032:
Another shortcut is the use of SAME. For example, PR C24 WH SAME: means
to print agency contact person names under the same WHERE conditions as the
previous command. Small tables (called lists) can be printed on the user's
screen or onto a diskette by use of the command LIST. LIST is used when the
user wants more than one data item printed, with each item in a different
column. For example,
LIST C12, C14, CIS WH C14 EQ OH AND C17 EQ LAER:
will print a table of addresses (city, State, and zip code) where an overall
determination of LAER was made for a company in Ohio. The syntax of S2K
requires a comma after each component (data item) except the component just
before the WHERE clause, which must not have a comma. Any number of blanks
may be used between words.
27
-------
If a long list of data items is to be printed on the screen, the result-
ing table may not be legible. Most screens can accommodate 80 characters on
a single line; if the listed data require more than 80 characters, "wraparound"
occurs. Data items at the end of the line would be printed on the next line,
so that different data items appear to be printed in the same column. If the
microcomputer screen being used has a line width of 40 or 60 characters, wrap-
around is an even greater problem.
To avoid wraparound, the user must know in advance how many columns and
how many characters per column are needed for each line of the table. For
each data item, the user should allow the greater of (a) the data length shown
in Table 1, or (b) the length of the title, including blanks. He/she should
also allow three spaces at the beginning of each line and three spaces after
each data item. For example, in the last LIST command, "city" requires 30
characters (data length), State initials require 14 characters (title length),
and the zip code requires 8 characters (title length). Total line length
equals 30 +14 +8+3+3+3+3= 64 characters. This table will fit on an
80-character screen with no wraparound.
A useful command to survey the whole data base is the verb TALLY. For
example, if the user wants to know the number of entries in the data base as
of today, he/she can enter
TALLY/ALL/C1:
which causes the number of ID numbers (one per entry) to be summed, the maxi-
mum value, and the minimum value to be printed on the screen. The expression
"/ALL/" is a modifier telling what kind of tally to do. The other type of
tally is "/EACH/." For example,
TALLY/EACH/C3:
will cause a table to be printed that shows the names of the different source
types that occur in the data base and the number of times each occurs. If ALL
or EACH is not specified, the S2K system defaults to EACH. Also, the TALLY
command cannot be used with a WHERE clause.
Several other functions are built into the S2K program so that key in-
formation can be presented succintly. These functions are MIN (lowest value),
MAX (highest value), SUM (total of all values), COUNT (number of values, as in
TALLY), AVG (arithmetic average), and SIGMA (standard deviation). For example,
28
-------
if a user wants to know the lowest, highest, and average emission limits for
a certain pollutant when control technology is LAER, he/she can enter the
following:
PR WIN C202, MAX C202, AVG C202 WH
C201 EQ S02 AND C203 EQ PPM:
Note that emission units (C203) are specified in the WHERE clause as
well as the pollutant (C201). If mixed emission units were used, the minimum
values would have little meaning.
The S2K commands presented in this section provide sufficient capability
for users who need to summarize data at their terminal. Appendix E provides
an annotated example of a terminal session using the commands described in
this section. If more detailed tables or data summaries are needed, the user
should proceed to Section 4 to learn how to obtain printed outputs.
29
-------
SECTION 4
PRINTING OUTPUT
With a few commands and an understanding of the data base, a user can
obtain the latest BLIS information at a computer terminal. This section
describes how to obtain a printout from BLIS.
4.1 OBTAINING COPIES OF STANDARD TABLES
One type of printed report that may be obtained is entitled "A Compilation
of Control Technology Determinations." This report, updated to include all of
the determinations submitted prior to May 1985, was distributed in June 1985.
Annual updates containing only the determinations inserted since the June 1985
printing or since the previous year's update were distributed in May 1986 and
June 1987. Currently, EPA plans to update the original report every 5 years
and to publish annual updates in the off years.
The 1985 edition of A Compilation of Control Technology Determinations,
dated June 1985, contains Table 1, Table 2, Table 2A, and a detailed listing
of all the determinations in the 'data base at that time. Table 1, entitled
"Index of Control Technology Determinations", lists the source type, company
name, State, date the permit was issued, agency, name of contact, telephone
number, and an index to Table 2 for every entry in the data base. Table 2,
entitled "Control Technology Determinations by Type of Source", is an abbre-
viated summary of each determination. This table lists company name, State,
permit number or regional file number, source size, whether the source is new
or modified, a description of each process permitted, names of the pollutants
controlled, their emission limits, and the basis for the emission limit.
Table 2A, entitled "Control Technology Determinations for Sources with Indust-
rial or Utility Boilers (External Combustion Sources)" repeats the same infor-
mation found in Table 2, but only for entries with industrial or utility boil-
ers. Appendix G of the initial report provides a detailed listing of each
determination in the data base at that time.
30
-------
The tables in the 1986 and 1987 updates to the June 1985 report were
altered slightly to improve their usefulness. Table 1 was changed in several
ways. First, it was reordered; it is now ordered by source type and by
company name within each source type. Second, the year of the volume that con-
tains the detailed listing of that determination appears in parentheses in
front of the company name; i.e., "(86)" indicates that the detailed listing
of that determination is contained in the 1986 update to the June 1985 re-
port. The third and final change involves the printing of the ID number for
each determination to aid in locating the entry in Appendix G of the updates,
i.e., a detailed listing of all new determinations. Table 2 was omitted in
the updated reports because it repeated the information found in the detailed
listing. Table 2A was altered to include the ID number of each source and
was ordered first by process code (i.e., the type of fuel used) and second,
by the size of the unit in MM Btu/h. The detailed listing, Appendix G, re-
mained unchanged from the original report.
To obtain additional copies of the June 1985 report or any of the
existing updates, the user should contact Fred Dimmick in ESD of the EPA at
(919) 541-5432 or (FTS) 629-5432. Copies of each table are also available
in electronic form in the IBM computer at the NCC; for information on these
files, call Joe Steigerwald at PEI Associates, Inc., at (919) 688-6338.
Note: The electronic form of Tables 1 and 2A and of the Detailed Listing
contain all of the determinations contained in the data base, not just those
listed in the June 1985 report, the May 1986 update, or the June 1987 update.
Once the file names are obtained, the files can be printed and sent
to the users bin number by exercising the PRINTOFF command. The format of the
PRINTOFF command, in a TSO environment, is described below, and the information
is produced on standard computer paper:
PRINTOFF 'file.name' Bin* DEST(RMT#) COPIES=c
where Bin # = EPA bin number for receiver
RMT # = Remote Printer ID
c = number of copies desired
To use the high-speed NCC printer, substitute "LOCAL" for RMT# in the above
command. To generate a copy of the desired output table on three-hole punched
8% in. x 11 in. paper, printed with the NCC laser printer, the following command
should be entered in a TSO environment:
31
-------
PRINTOFF 'file.name1 BIN# TEXT FORM(6371) CLASS(F) BURST COPIES=c
Where Bin# = Appropriate EPA computer bin number
c = number of copies
Appendix I lists the standard bin numbers and addresses for each EPA RO.
If the user is not an EPA employee, he/she may obtain a bin assignment by
calling NCC Data Processing Support at (919) 541-2385; NCC will automatically
mail any printout identified by bin number to the address associated with that
bin.
4.2 CREATING PRINTED TABLES
Creating BLIS information tables in an interactive environment requires a
rudimentary knowledge of computer commands from two software systems:
o Interactive System Productivity Facility (ISPF)
o IBM Job Control Language (JCL)
With knowledge of these systems, the user can generate any of the standard BLIS
tables (Table 1, Table 2A, and a detailed list of all determinations). To
create user-defined tables, the user needs to be familiar with the LIST command
options in the S2K access language.
4.2.1 Standard BLIS Tables
The ISPF is a full-screen processor and requires the use of a 3270 termi-
nal or PC emulation equipment. The user must first initiate a TSO session
(see Section 3 of this report for instructions). Once in TSO, the user enters
ISPF via the command:
>ISPF (CR)
A menu similar to the one depicted in Figure 5 will appear. The user should
select option 2, EDIT, by inserting a 2 on the COMMAND line and hitting car-
riage return (CR). This will cause a menu similar to Figure 3 to appear,
except that the ISPF LIBRARY section of the screen may contain other informa-
tion or be blank. The user must then insert the correct PROJECT, GROUP, TYPE,
and MEMBER in the ISPF LIBRARY section of the screen, as shown in Figure 6.
The following information should be inserted:
32
-------
OPTION —>
0 ISPF PARMS -
1 BROWSE
2 EDIT
3 UTILITIES
4 FOREGROUND -
5 BATCH
6 COMMAND
7 DIALOG TEST -
8 LM UTILITIES-
C CHANGES
T TUTORIAL
X EXIT
E EPA
G Group
U User
Userid - JSE
Specify terminal and user parameters Prefix - JSECONS
Display source data or output listings Terminal - 327B
Create or change source data PF Keys - 12
Perform utility functions Time - 10i22
Invoke language processors in foreground Date - 37/12/09
Submit job for language processing Julian - 37.343
Enter TSO command or CLIST Proc - *EPATSO
Perform dialog testing Applid - ISR
Perform library management utility functions
Display summary of changes for this release
Display information about ISPF/PDF
Terminate ISPF using log and list defaults
EPA/NCC Application Option Menu
Group Application Option Menu
User Defined Application Option Menu
Enter END command to terminate ISPF.
Esc for ATtention, Home to SWitch
Capture Off
i Appli cati on
Figures. ISPF/PDF Primary Option Menu.
COMMAND —>
ISPF LIBRARYi
PROJECT -"-> JSECON5
GROUP — > BLIS
TYPE — > BATCH
MEMBER «=> EXAMPLE
(Blank for member selection list)
OTHER PARTITIONED OR SEQUENTIAL DATA SETi
DATA SET NAME — >
VOLUME SERIAL —>
DATA SET PASSWORD -«->
PROFILE NAME — >
INITIAL MACRO —>
MIXED MODE —> NO
FORMAT NAME — >
(If not cataloged)
(If password protected)
(Blank defaults to data set type)
(SPECIFY YES OR NO)
Esc for ATtention, Home to SWitch
Capture Off
i Application
Figures . ISPF - EDIT ENTRY PANEL.
33
-------
PROJECT ==> JSECON5
GROUP ==> BLIS
TYPE ==> BATCH
MEMBER ==> EXAMPLE (return)
This data set, JSECON5.BLIS.BATCH(EXAMPLE), will appear on the screen
(Figure 7). It contains an example of the JCL and S2K code needed to generate
any of the standard BLIS tables. The user then replaces the information on
the job control card (lines 1 and 2) and the routing card (line 3) with the
appropriate information, i.e., user ID, account number, FIMAS ID, bin number,
name, and printer number.
The user then enters the code name of the standard BLIS table desired in
place of the question marks on the line that reads:
COMMAND FILE IS ??????:
where ?????? = S2KCOM1 for a detailed listing of
all determinations
S2KCOM2 for a copy of Table 1
S2KCOM3 for a copy of Table 2A
Note: All S2K commands must end in a colon; if this colon is missing the job
will not execute correctly. If the user does not wish to generate one of the
standard BLIS tables and has sufficient "knowledge of S2K ACCESS language, he/
she may write their own S2K code and copy it into the example file in place
of the COMMAND FILE IS ??????: line. More information on user-defined tables
is given in Section 4.2.2 of this manual.
When the correct user information and table code name or user-written
S2K code have been inserted into the example file, the user returns to the
COMMAND line and enters:
>SUBMIT (CR)
This enters the batch job into the NCC IBM system and a job number will appear
at the bottom of the screen. Make a note of this job number, as it identifies
your job and will appear on the printout that will be printed at the site
noted on line 3 and sent to the bin number inserted on line 1 of the EXAMPLE
data set. Then enter the command:
>CANCEL (CR)
34
-------
COMMAND
******
OO0001
000002
OO0003
000004
000005
000006
000007
OO0008
OOO009
000010
OOOO11
000012
OOOO13
000014
000015
OOOO16
000017
000018
OOOO19
000020
000021
OOO022
OO0023
000024
000025
000026
000027
000028
000029
000030
000031
000032
000033
OO0034
000035
000036
******
TOP OF DATA
,NAME,PRTY=4,TIME'
SCROLL — > PAGE
*************»**************.».
//DID JOB ,DISP-OLD
DSN-JSECON5.BLIS.PROG(TABLE2A),DISP-OLD
//S2KCOM1
//S2KCOM2
//S2KCOM3
//SYSIN
DD
DD
USER,ANYiDBN IS BLIS:
COMMAND FILE IS ???????»
EXITi
//*
//BLISXXX1 DD
//BLISXXX2 DD
//BLISXXX3 DD
//BLISXXX4 DD
//BLISXXX5 DD
//BLISXXX6 DD
DSN-J SECON5.BLIS.BLISDB1,DISP-OLD
DSN-JSECON5.BLIS.BLISDB2,DISP-OLD
DSN-JSECON5.BLIS.BLISDB3,DISP-OLD
DSN=JSECON5.BLIS.BLISDB4,DISP-OLD
DSN-JSECON5.BLIS.BLISDB5,DISP-OLD
DSN-JSECON5.BLIS.BLISDB6,DISP-OLD
*******#»******+*»**#*##**#* BOTTOM OF DATA"
E»c for ATtention, Horn* to Switch
C*ptur» 0-f-f
i Application
Figure 7. Copy of JSECON5.BLIS.BATCH(EXAMPLE)
35
-------
on the COMMAND line. This deletes all of the changes made to the file and
returns the user to the menu depicted in Figure 3. If the user tries to exit
the example code without canceling the changes, an error message will appear
and prevent the user from exiting the file and returning them to the example
JCL (Figure 7).
The EDIT mode (.Figure 6) may be exited by entering the command:
>END (CR)
on the command line. This returns the user to the ISPF Primary Option Menu.
By entering the command:
>END (CR)
on the COMMAND line once more, the user can exit ISPF and return to a TSO
environment. Entering the command:
>LOGOFF (CR)
terminates the session.
4.2.2 User-Defined Tables
To create a user-defined BLIS table, the user should follow the instruc-
tions in Section 4.2.1 and substitute the appropriate LIST command for the
COMMAND FILE IS ??????: statement in the example JCL file. The LIST command
options allow the user to specify a title for each page of the table, to
place names at the head of each column, to specify the width of columns, and
to list data in the columns in a desirable order. He/she may even specify
a footnote to appear at the bottom of each page. The LIST command has the
following general format:
LIST/(options,) TITLE (title specs,) (footing specs,) (column specs)/
data list (., ordering clause) WHERE clause:
The statement always begins with the command LIST, always contains a
list of data to b& printed out, always ends with a colon, and should always
have a where clause. Specifications in parentheses are optional; the
command will work if they are missing.
Options that may be useful are DOUBLE SPACE & REPEAT OR REPEAT SUPPRESS
(REPEAT is the default option). Each option that is used must be followed by
36
-------
a comma. The meaning of DOUBLE SPACE is obvious; REPEAT SUPPRESS means that
data items on a higher level will not be repeated for every occurrence of a
related data item at a lower level. For example, the user may want to print
out the names of pollutants controlled (from Level 2) for a certain process
(from Level 1).
With the REPEAT option, the following is printed:
Process Pollutant
Ki 1 n PM
Kiln S02
Kiln N0v
/\
With the REPEAT SUPPRESS option, the following is printed:
Process Pollutant
Ki 1 n PM
so2
N0x
The word TITLE must occur prior to any title specifications, footing
specifications, or column specifications. If title or footing is left out,
there will be none. If column specifications are left out, the names of data
items printed in each column will be used as column headings (same as in Sec-
tion 3). A number in parentheses following TITLE indicates the number of
characters (including blanks) that will occur on each line of the table. De-
fault is 131.
Title specifications have the following format:
D(100)TITLE1 (+TITLE2) (+TITLE3),
The letter "D" indicates a title and date because the date of the report
is automatically centered under the title. Number 100 (or some other number)
specifies the column number for the first letter in the title. The title may
occur on 1, 2, or 3 lines. The portion of the title that occurs on each line
is separated by "+" in the title specification. For example, title specifi-
cation D(25)POLLUTANTS LISTED + BY PROCESS, would result in the following
title, beginning in column 25:
37
-------
POLLUTANTS LISTED
BY PROCESS
08/25/82
Footing specifications have the following format:
F(50)Footnote,
where F identifies a footing specification, 50 (or some other number) indi-
cates the number of lines per page, and "footnote" indicates the message to
be printed on the last line of each page.
Specifications for a single data column in the table have the following
format:
L(10)Headl(+ Head2)(+ Head3),
One of these specifications should be provided for each data item in the data
list and in the same order as the data list. The letter "L" indicates that
both the heading and the data in the column are to be left-justified. The
number 10 (or some other number) indicates the width of the column for both
the heading and the data. The user is responsible for providing sufficient
space for the data. Otherwise, character data will be truncated on the right
and the character "*" will be printed in the last space of the column. Numeric
data will be truncated on the left with no warning symbol. To get a right-
justified column, the user should substitute R for L in the specification.
Numeric data and dates will always be right-justified regardless of specs.
Inserting the letter B instead of R or L means a blank column with no heading
or data, and it may be used as spacing between the other columns. Column
headings may occur on more than one line, just as page titles can.
A data list follows the second slash (/) in the statement. For example,
Cl, CIO, C102, C201 could represent a list of data to be printed.
Data may be printed in ascending alphabetical or numeric order by using
an ordering clause. The format is:
.ORDERED BY...data list
For example, ORDERED BY C102, C201 would cause data to be listed alphabetically
by process name. Within each process name, pollutant name would be listed
alphabetically, as follows:
38
-------
PROCESS POLLUTANT
Process 1 CO
N02
PM
Process 2 CO
PM
VOC
The format and usage of WHERE clauses were discussed in Section 3.
Appendix 'F provides an example of the instructions and outputs for a
table written by extended LIST commands. The LIST command and its options
provide the user with an ability to write formatted tables with relatively
little programming knowledge and with relatively short statements. For more
advanced formatting, a different S2K language, called Report Writer, should
be used. Report Writer specifications can be found in a manual published by
the SAS Institute, Inc. Some examples of Report Writer outputs are the
standard tables distributed by ESD. More advanced users (computer programmers)
with knowledge of FORTRAN or COBOL may also write programs from the BLIS data
base. The Program Language Extension (PLEX) program of S2K allows access to
S2K data bases from a FORTRAN or COBOL program. For further references, see
Appendix G.
39
-------
SECTION 5
SUBMITTING DATA TO BUS
The performance of a BACT/LAER Clearinghouse depends on State and local
cooperation and participation. Data may be submitted manually by filling
out a standard form and sending it to the Clearinghouse, or data may be
entered directly into the IBM computer. Both methods will result in con-
tinued expansion of information.
5.1 SUBMITTING BACT/LAER DETERMINATION FORM
Figure 8 presents an example of a BACT/LAER Determination form overlaid
with data names and numbers. A blank form is provided in Appendix H. Each
number in Figure 8 is the component number for the data sheets described in
Section 2 of this manual. The first data item, ID number, is not shown on the
form because it is provided by the BACT/LAER Clearinghouse. The first data
item to be provided by the State or local agency is the source type code
selected from the list of standard codes in Appendix A. Name is not neces-
sary because the standard source code name is provided by the BACT/LAER
Clearinghouse. Source size and source size units should be provided when
available.
On the second line of the form, the user should always provide company
name, address, and State initials. City, county, and zip code should be
provided wherever applicable.
The type of determination for the overall source may be indicated by
circling BACT or LAER, New or Modified. Date of permit issuance is the date
of the most recent permit that pertains to the determination.
The permit number follows the numbering system of the submitting agency.
If it is EPA, a regional file number may be substituted. The startup date is
an estimate. If only the year is given, January 1 will be used as a dummy
variable to compose an S2K data item. If month and year are given, the 1st
will become the dummy day for the data item.
40
-------
Hall Toi
BACT/LAER DETERMINATION REPORT
Source Type/size. Source category (3) Source size (4) Units (5)
(2)
Source Category
Date of This Report
Company Name/site Locations Name (10) Street adress (11) City (12)' County (13) State initials (14) Zip (15)
Determination 1st ( 17) BACT/LAER for New/Modified Source t (13) Date of Permit Issuances
(circle appropriate
definition) Permit No.t (20) or (21) _ Date of Estimated start-ups (22)
Determination Made Bys
(100)
(23)
(24)
(25)
(Agency) (2QQ)
(Person Directly Knowledgable About Permit)
(Phone)
Permit Parameter as
(List all
processes subject
to this permit)
Process name (102]
Throughput
capacity,
weight rate,
Btu Input, etc.
Throughput (103)
& units (104)
Pollutant(a)
emitted (SOj
partlculate, etc.)
Pollutant name (201)
BACT/LAER emission
limit(s) and basis
for the limits*
(units of emissions/
units of Input
Emission limit (202) &
units (203)
Alternate limit (204) a
units (205)
CAS numbers (210)
Basis (206)
Control equipment
or process
modification description**
Equipment (207)
Process (203)
eff.%
(209)
Notes*
(26) and (27)
•Indicate btsli of Missions Unit. l.t.. BACT determined slnply by technology and economics. DSPS. IAER. or determined by NAAQS or PSD
Increment constraints, (Example: O.OS pounds parttcuUte per million Btu Input limit needed to protect CUss I Increment.) to promote
consistency, please use NSPS emission Units where possible.
"to the extent possible In the space available, describe basic control or process equipment design details. Indicate unique or Innovative
features.
•••Notes are optional and can address special Items, unusual circumstances, or other clarifying Information such as SIC codes.
11/82
Page
of
Figures. BACT/LAER determination form.
-------
Agency name, contact person, and phone number (.including area code) are
'important data. The first permit parameter to be provided is the name of
the process. As an option, the user may select a process code from Appendix
A. Note: Process codes frequently differ from source type codes. If a code
for a combustion source (.boiler) is left out, it will be supplied by the
BACT/LAER Clearinghouse. When specifying throughput capacity, the user should
use the standard abbreviations for capacity units listed in Appendix B.
For each process listed in the first column, the user should list one
or more pollutants in the third column and provide an emission limit and
emission limit unit for each (.Appendix B). As an option, one alternate emis-
sion limit may be given. Currently, only one alternate limit is defined in
BLIS; additional limits cannot be input to the data base. For each pollutant,
a brief name of control equipment and/or process modification is highly de-
sired. Efficiency data may be provided when such data are available.
Space for notes is provided at the bottom of the form. Copies of the
form may be used as continuation sheets for additional notes or processes.
The policy of the BACT/LAER Clearinghouse is to encourage and accept all
entries, regardless of size and regardless of whether a BACT/LAER determination
was actually made. (.Some of the more innovative technologies may allow a
company to escape official BACT/LAER determinations.)
5.2 COMPUTERIZED BACT/LAER DETERMINATION REPORT
If the individual submitting the data is well versed in the use of the
ISPF on the IBM computer, or with the IBM Editor, he/she may find that enter-
ing data directly into the computer is almost as easy as completing a form.
To submit a computerized BACT/LAER Determination Report, the individual should
know how to create and edit a file on the IBM computer system.
First, the user must initiate a terminal session (described in Section
3). Second, he/she must create a file using ISPF or the TSO ALLOCATE com-
mand. The process of file creation is left to the user because the character-
istics of the file will depend on how it will be used and the amount of
data to be entered.
Once the file is created, the user may begin entering data into it via
the EDIT option of ISPF or the INPUT option of the IBM Editor. A blank S2K
form copied from Appendix H may be used to organize notes prior to entering
42
-------
data into the computer file. Previous comments concerning data items on the
standard BACT/LAER report form also apply to data items in the computerized
report form.
The format of the computerized BACT/LAER report consists of a data item
number followed by an asterisk (.*)» which is followed by the data and a second
asterisk. For example, 10*EWING O'lL CO.* demonstrates the correct format for
entering a company name. For readability, each data item may be entered on a
separate line, as suggested in Table 3. The computer, however, will accept
multiple data on a single line.
Data must be listed in a particular order. Data on level 0 (.component
numbers 1 through 36) are listed first (in any order). Then the term "100*"
is used to indicate the beginning of data in a process record (components 101
through 105). This term may be placed on a separate line, as shown in Table
3, or it may be placed on the same line as the first data item in the record.
The term "200*" precedes the beginning of data for a pollutant record (com-
ponents 201 through 210). It may be placed on a separate line or simply pre-
cede the first data item in the pollutant record. All pollutant records must
be listed before the user proceeds to the next process record. After all
records and all data are listed for a particular source, the term "END*" is
used to indicate the end of a BACT/LAER report for one source. More than
one report may be listed in one computer file.
Data in Notes (.Item 26) and Notes Continued (Item 27) require particular
care. Regardless of screen size, the S2K program will only read data lines
that are no more than 80 characters (columns) long. If notes require more
than 80 characters, writing should be discontinued after the 80th column,
even if this causes a break in the middle of a word. It is good practice to
avoid word breaks by adjusting spaces at the beginning of the line. For
example, if a sentence contains a four-letter word beginning in column 79,
place two blank spaces preceding the data item number of that line and begin
the word on the following line.
The process of placing data into a IBM file completes the computerized
BACT/LAER Determination Form. The user should exit from the file and the
TSO session (LOGOFF), and then notify the BACT/LAER Clearinghouse of the data_
file that was created. These data are not a part of the BLIS data base until
further actions are taken.
43
-------
TABLE 3. HYPOTHETICAL EXAMPLE OF COMPUTERIZED BACT/LAER DETERMINATION REPORT
Data entry
Explanation
2*5.5*
4*130.0*
5*MBPSD*
10*Ewing Oil Co.*
11*100 Dollar Blvd.*
12*Dallas*
13*Dallas*
14*TX*
16*6*
17*BACT*
18*M*
19*12/08/83*
21*PSD-TX-999
23*EPA Region VI*
24*A.C. Current*
25*(214)-767-9999*
26*H25 LIMITED TO 0.1 GRAIN/SDCF.
100*
101*Heaters, GAS FIRED, 12 EA*
102*144.0*
103*MMBTU/H*
200*
201*NOX*
202*0.12*
203*LB/MMBTU*
206*BACT*
208*Low NOX burners*
200*
201*502*
202*0.03*
(continued)
Source type code
Source size
Source size units
Company name
Street address
City
County
State initials
EPA region
B/L determination
New/Modified
Date permit issued
Region file no.
Agency name
Agency contact person
Agency phone number
Notes
First process record
Process name
Throughput capacity
Throughput units
First pollutant record
.Pollutant name
Emission limit
Emission units
Basis for limits
Process modification
Second pollutant record
Pollutant name
Emission limit
44
-------
TABLE 3 (continued)
Data entry
Explanation
203*LB/MMBTU, GAS FIRED*
206*NSPS*
100*
101*Sulfur Recovery Unit*
102*1000.0*
103*LT/D
200*
201*S02*
202*250.0*
203*PPM*
206*NSPS*
207*3-stage claus unit*
209*99.9*
END*
Emission units
Basis for 1imits
Second process record
Process name
Throughput capacity
Throughput units
First pollutant record
Pollutant name
Emission limit
Emission un.its
Basis for limits
Control equipment
Efficiency
End of data entry
Once the BACT/LAER Clearinghouse has been notified of the creation of a
data file, three actions will be taken:
1.
2.
3.
The data file will be reviewed for completeness and ID numbers will
be assigned. This is the same action as for manual data sub-
missions.
A quality control program will be run to ensure correct format.
(This does not ensure correct data—only the Individual submitting
the data knows what is accurate.)
An S2K program will be run to insert the data into the data base.
These are routine procedures for all data submitted to the BACT/LAER
Clearinghouse, both computerized and manual. The advantage of a user enter-
ing his/her own data into a computer file is that it reduces the opportunity
for errors and speeds up the data entry process.
45
-------
APPENDIX A
SOURCE TYPE NAMES AND CODES
46
-------
SOURCE TYPE CODE
1. External Combustion j Q
Coal combustion i ,
Oil combustion ^'o
Natural gas combustion ^'3
Wood waste combustion i'd
Multiple fuels :, ?
Other Jj
2. Solid Waste Disposal 2 0
Refuse incineration 2 i
Sewage sludge incineration ?'' ?
Other 23
3. Internal Combustion 3 Q
Natural gas turbines , 3 ,
Natural gas compressors ,'9
Other 33j
4. Organic Evaporation Loss 4 Q
Surface coating of cans and coils 4 i
Surface coating of paper and fabrics 4*2
Surface coating of automobiles and light-duty trucks 4*3
Surface coating of metal furniture 44
Surface coating of magnet wire -4*5
Surface coating of large appliances 4*5
Surface coating of miscellaneous metal parts and products 4*7
Surface coating of flatwood paneling 4*0
Solvent degreasing 4"n
Waste solvent reclamation 4'n
Graphic arts 4':i
Dry cleaning 4';t
Furinture refinishing 4^4
Other 4.15
5. Petroleum Refining, Oil and Gas Production, and
Related Industries 5.0
Petroleum refining - separation processes (distillation and
light ends recovery) 5.1
Petroleum refining - conversion processes (cracking,
reforming, alkylation, polymerization, isomerization, and
coking) 5_2
Petroleum refining - treating processes (hydrodesulfurization,
hydrotreating, chemical sweetening, acid gas removal, and
deasphalting) 5.3
47
-------
SOURCE TYPE CODE
Petroleum refining - feedstock (storage, blending, loading,
and unloading) 5.4
Petroleum refining - auxiliary (boilers, wastewater treatment,
hydrogen production, sulfur recovery, cooling towers, blow-
down system, compressor engines, heaters, and incinerators) 5.5
Petroleum refining -entire operation 5.6
Bulk terminals 5.7
Bulk plants 5.8
Storage of petroleum liquids 5.9
Transportation and marketing of petroleum products 5.11
Natural gas/gasoline processing plants 5.12
Asphalt and associated products manufacturing and processing 5.13
Crude petroleum and natural gas production including oil shale 5.14
Oil and gas field services 5.15
Other 5.16
6. Chemical Process Industry 6.0
Acrylonitrile 6.1
Acetic acid 6.2
Acrylic acid 6.3
Acetic anhydride . 6.4
Acrolein 6.5
Acetaldehyde 6.6
Adipic acid 6.7
Aniline ' 6.8
Alky!benzene 6.9
Butadiene 6.11
Carbon black 6.12
Charcoal 6.13
Chioroalkali 6.14
Chlorobenzene 6.15
Chloromethane 6.16
Chloroprene 6.17
Caprolactam 6.18
Cyclohexanol, cyclohexane 6.19
Cumene . 6.21
Dimethyl terephthalate 6.22
Ethylene dichloride 6.23
Ethylene and polyethylene 6.24
Ethylene oxide 6.25
Ethylene glycols 6.26
Ethylbenzene/styrene 6.27
Ethyl acetate 6.28
Epichlorohydrin 6.29
Fluorocarbons 6.31
Formaldehyde 6.32
Glycol ethers 6.33
Hydrochloric acid 6.34
Hydrofluoric dCid 6.35
(continued)
46
-------
SOURCE TYPE CQDE
Maleic anhydride c. •se
Methanol 53°
Methyl ethyl ketone g'«
Nitric acid - 5 30
Nitrobenzene g'4i
Paint and varnish g'42
Pharmaceutical g*43
Phosphoric acid 5*44
Phthalic anhydride g'45
Proylene oxide g'46
Phenol/acetone g'47
Soap and detergents 5*42
Sodium carbonate 5*49
Sulfuric acid g'gi
Sulfur recovery g'^2
Synfuels and fuel conversion other than oil shale 6*53
Synthetic fibers g 54
Synthetic rubber/rubber tires g'55
Toluene diisocyanate g'gg
Trichloroethane • g*57
Terpthalic acid g'58
Vinyl chloride and polyvinyl chloride 5*59
Alcohol fuel production *'ci
Other |;g
7. Food and Agricultural 7>0
Alfalfa dehydrating 71
Roasting 7*2
Feed and grain mills and elevators 7^3
Fermentation and alcoholic beverages 7*4
Fish processing 7*5
Fertilizer plants 7*g
Starch manufacturing 7*7
Sugar cane processing 7*3
Fats and vegetable oils 7*9
Fruit and vegetable processing 7*11
Other 7^2
8. Metallurgical g Q
Primary aluminum production 3 ]_
Coke production 3*2
Primary copper smelting 3*3
Ferroalloy production 3*4
Iron and steel production 3*5
Primary lead smelting g'6
Zinc smelting 3*7
Secondary aluminum 3'3
Secondary copper smelting and alloying 3*9
Gray iron foundaries 3JH
(continued)
49
-------
SOURCE TYPE CODE
Secondary lead smelting 8.12
Secondary magnesium smelting 8.13
Steel foundaries 8.14
Secondary zinc processing 8.15
Storage battery production/reclamation 8.16
Lead oxide and pigment production 8.17
Miscellaneous lead products 8.18
Ore crushing and grinding 8.19
Sintering 8.21
Other 8.22
9. Mineral Products Industry ' 9.0
Asphalt batching plants 9.1
Bricks, ceramic, and related clay products 9.2
Refractories 9.3
Portland cement manufacturing 9.4
Cement manufacturing - other than portland 9.5
Coal cleaning 9.6
Coal cleaning (thermal dryer) 9.7
Glass fiber manufacturing 9.8
Frit manufacturing 9.9
Glass manufacturing 9.11
Gypsum manufacturing 9.12
Lime manufacturing 9.13
Mineral wool manufacturing 9.14
Perlite manufacturing 9.15
Phosphate rock processing 9.16
Stone quarrying, sand and gravel processing 9.17
Taconite ore processing 9.18
Mining operations 9.19
Other 9.21
10. Wood Products 10.0
Kraft pulp mills 10.1
Wood pulping other than kraft . 10.2
Hardboard 10.3
Plywood plants 10.4
Woodworking 10.5
Other ' 10.6
11. General Manufacturing and Fabrication 11.0
12. Institutional/Commercial 12.0
50
-------
APPENDIX B
ABBREVIATIONS FOR PROCESS, CAPACITY, AND
EMISSION UNITS
51
-------
ABBREVIATIONS FOR PROCESS AND EMISSION UNITS
ADD
AL
AM
ASSOC
ATMOS
CALC
CO
COLL
COOP
CORP
DECARB
DESULF
DISTIL
DISTN
DIV
E
EA
ELECT
FAC
FCC
FCCU
FURN
GEN
HAND
I.C.
INCIN
INDEPEN
INTERNAT
LAB
LDOUT
LIQ
LT
MATL
MFG
MISC
MODIF
NAT
NATL
PREP
PROD
PWR
REC
RECIP
additive
aluminum
American
association
atmospheric
catalytic
company
collection
cooperative
corporation
decarbonization
desulfurization
distillation
distribution
division
eastern
each
electric
facility
fluid catalytic cracking
fluid catalytic cracking unit
furnace
generator
handling
internal combustion
incinerator
independent
international
laboratory
loadout
liquid
light
material
manufacturing
miscellaneous
modification
natural
national
preparation
production
power
recovery
reciprocating
52
-------
RECLAM
REFIG
REFIN
REG
REGEN
RESID
ROT
SCRUB
SECOND
SHIP
STOR
SUP
SYS
TRANS
UNIV
VAC
VERT
reclamation
refrigeration
refinery
regular
regenerator
residual
rotary
scrubber
secondary
shipping
storage
supplementary
system
transmission
university
vacuum
vertical
ACF
ACFM
ADP
AV
BBL
BLS
BPSD
BTU
CF
CFM
CU YD
D
D FEED
DACF
DIST
DSCF
F
G
G/HP-H
G/0
GAL/M
GR
H
HP
J
KG
KW
LB
LT
M
MM
MG/L
MW
actual cubic feet
actual cubic feet per minute
air-dried pulp
average
barrels
black liquor solids
barrels per stream day
British thermal units
cubic feet
cubic feet per minute
cubic yard
day
dry feed
dry actual cubic feet
distillate
dry standard cubic feet
feet
gram
grams per horsepower - hour
gas/oil
gallons per minute
grains
hour
horsepower
joule
kilogram
kilowatt
pound
long ton ,
thousand (10 )
million (10°)
milligram per liter
megawatt
53
-------
N natural
NG nanogram
PPM parts per million
PPH parts per hundred
RDF refuse-derived fuel
RESID residual
S sulfur
SB subbituminous
SCF standard cubic feet
SCFD standard cubic feet per day
SCFM standard cubic feet per minute
SEC second
SQF square feet
T ton
VOL volume
WKS weeks
YR year
54
-------
APPENDIX C
SAMPLE FORM N258 - EPA ADP IBM, IMF, SPERRY,
AND VAX ACCOUNT AND USER REGISTRATION
55
-------
EPA ADP IBM. LMF. SPERRY. & VAX ACCOUNT AND USER REGISTRATION
THIS DEQUES
. ESTABLISHES A NEW ACCOUNT
, ADOS. DELETES, « CHANGES USER(S) ON EXISTING ACCOUNT f
TSSMS USE ONLY
DATE RECEIVED:
(NOTE: FORM H ?51 HIST BE COMPETED TO MODIFY INFORMATION OTHER THAN USER DATA ON AN EXISTING ACCOUNT.)
1
HARDWARE (CHECK ONLY ONE)
IBM 3090 IBM 4341 MASH.. DC SPERRY
LMF (SPECIFY)
MAO VAX NCC VAX CLUSTER
OTHER (SPECIFY)
POP 1I/7C HARDWARE ONLY: FORM N 2S8A
MUST BE COMPLETED.
SOURCE OF TIME5HARE FUNDS (CHECK ONLY ONE)
U.S. EPA _ INTERAGENCY/INTERGOVERNMENTAL AGREEMENT (IAG)
OTHER (SPECIFY)
TO BE COMPLETED BY EPA 1A6 COORDINATOR
IS ACCOUNT TO BE CHARGED IAG 101 SURCHARGE? YES NO
I EM IAS COOBDIMArBR'S 5] SUTURE)
PURPOSE OF ACCOUNT OR BRIEF DESCRIPTION OF ACTIVITY ACCOUNT KILL SUPPORT
EPA OR6ANI2ATION CODE (8-DIGIT CODE)
FMS CODE (10-BIGIT CODE)
ACCOUNT TITLE (LIMIT: 60 CHARACTERS. INCLUDING SPACES)
ACCOUNT MANAGER'S NAME (LAST. FIRST. H.I.). MUST BE EPA EMPLOYEE.
MAIL CODE (OR ROOM) OFFICE OR LOCATION
ADDRESS (STREET OR P.O. BOX)
CITY
PHONE
FTS
PHONE (INCLUDE AREA CODE)
STATE
ZIP CODE
REFERENCE
INITIALS
(TSSMS-
ASSIGNED!
TO BE A USER ON THIS ACCOUNT. ACCOUNT MANAGER MUST BE INCLUDED ON REVERSE SIDE.
EPA ADP COORDINATOR'S NAME (PLEASC PRINT OR TYPE)
EPA ADP COORDINATOR'S SIGNATURE (REQUIRED)
DATE
USER INITIALS CODE
(TSSMS-ASSIWED)
(SUPPLY IF KNOWN)
COOES USED M ASS1QMNO USERS ON REVERSE SIDE
SPECIAL FEATURES COOES
(CHEu. out fOR EACH USSR LISTED)
(DEFAULT IS IBM SPF)
RETURN FORM TO:
U.S. ENVIRONMENTAL PROTECTION AGENCY
NATIONAL DATA PROCESSING DIVISION
TSSMS OFFICE (MO-34C)
79 ALEXANDER DRIVE. BUILDING 4501
RESEARCH TRIANGLE PARK. NC 27711
S - IBM STORET (AASTORET)
R - SPERRY AUTOMATIC RUN CARD
(FORM N 252 MUST BE ATTACHED.)
I - NCC VAX CLUSTER (INFORM/BUILDER)
0 - OTHER (PLEASE SPECIFY.)
USER STATUS CODES
(CHECK On. FOR EACH U5LR LISTED)
E - EPA EMPLOYEE
C - CONTRACTOR/COMMERCIAL
F . FEDERAL NON-EPA
S • STATE OR LOCAL GOVERNMENT
U - UNIVERSITY
0 - OTHER
(SEE REVERSE SIDE FOR ASSIGNING USERS TO ACCOUNT)
N 258 (PAGE 1)
56
-------
USERS ASSIGNED TO ACCOUNT
(Please Print or Type)
USER INITIALS
TSSMS-ASSIGNEO
(LAST, FIRST. H.I.)
SPECIAL FEATURES
PHONE (INCLUDE AREA
OFFICE AKO/OR COMPAN1
HAIL CWE (OR ROOH)
ADDRESS (STREET OR P. 0. BOX)
CHANGE USER INFORMATION AS LISTED ABOVE
UPDATE ACTION:
NAHE (LAST, FIRST, H.I.)
TSSMS-ASSIGNEO
SPECIAL FEATURES
PHONE (INCLUDE AREA
CODE)
OFFICE AND/OR COMPAN1
MAIL CODE (OR ROOM)
ADDRESS (STREET OR P. o. BOX)
CHANGE USER INFORMATION AS LISTED ABOVE
UPDATE ACTION:
NAME (LAST. FIRST. H.I.)
T^MS-ASSIGNED
SPECIAL FEATURES
PHONE (INCLUDE AREA
OFFICE AND/OR COMPANY
MAIL CODE (OR ROOM)
ADDRESS (STREET OR P. 0. BOX)
CHANGE USER INFORMATION AS LISTED ABOVE
UPDATE ACTION:
NAME (LAST. FIRST. H.I.)
TSSMS-ASSIGNED
SPECIAL FEATURES
PHONE (INCLUDE AREA
OFFICE AND/OR COMPANt
MAIL CODE (OR ROOH)
ADDRESS (STREET OR P. 0. BOX]
CHANGE USER INFORMATION AS LISTED ABOVE
UPDATE ACTION:
NAME (LAST. FIRST. H.I.)
T5SMS-ASSIGNEC
SPECIAL FEATURES
PHONE (INCLUDE AREA
OFFICE AKO/OR COMPANY
MAIL CODE (OR ROOM)
ADDRESS (STREET OR P. 0. BOX)
CHANGE USER INFORMATION AS LISTED ABOVE
USER(S) UPDATE
SIGNATURE REQUIRED
ACCOUNT NUMBER (PLEASE SPECIFY) EPA ACCOUNT MANAGER
OR
EPA ADP COORDINATOR
N 258 (PAGE 2)
57
-------
-------
APPENDIX D
CONTENTS OF CROSSTALK FILE IBM-TSO.XTK
l:*NAme
2: NUmber
3: ACcept
4: ANswback
5: APrefix
6: ATten
7: BReak
8: Switch
9: CWait
10: LWait
11: DEbug
12: DPrefix
13: DSuffix
14: EMulate
15: EPath
16: Filter
17: INfliter
18: LFauto
19: MOde
20: POrt
21: PWord
22: RDials
23: Timer
24: TUrnarnd
25: BKsize
26: DNames
27: CApture
28: COmmand
29: Flow
30: PArity
31: DAta
32: DUplex
33: OUtfiltr
34: PMode
35: PRinter
36: SPeed
37: Slop
38: TAbex
39: BLankex
40: UConly
41: FK 1 ""
IBM 3090/TSO
5410700
Everything
On
ATSO=1 !
Esc
End
Home
None
Char '*J'
Off
ATDT
None
On
Off
Call
1
H H
10
On
Enter
1
200
Off
ETX CC
Even
7
HALF
On
2 (DOS)
Off
2400
1
Off
On
Off
FK
FK
42:
43: FK 3 ""
44: FK 4 CROSSTALK - XVI
45: FK 5 SCApture /',
46: FK 6 @PRinter /j
47: FK 7 STYpej
48: FK 8 @CApture <24j
49: FK 9 @SNap|
50: FK 10 eSNap 24j
51: FK SI ""
52: FK S2 ""
53: FK S3 ""
54: FK S4 ""
55: FK S5 ""
56: FK S6 ""
57: FK S7 ""
58: FK 58 M"
59: FK S9 ""
60: FK S10 ""
61: FK Cl ""
62: FK C2 ""
63: FK C3 ""
64: FK C4 ""
65: FK C5 ""
66: FK C6 ""
67: FK C7 ""
68: FK C8 ""
69: FK C9 ""
70: FK CIO ""
71: FK Al ""
72: FK A2 ""
73: FK A3 ""
74: FK A4 ""
75: FK A5 ""
76: FK A6 ""
77: FK A7 ""
78: FK A8 ""
79: FK A9 ""
80: FK A10 ""
81: GO q45/45
58
-------
-------
APPENDIX E
ANNOTATED EXAMPLE OF A TERMINAL SESSION
59
-------
The following is an example of a session at a terminal using the commands
described in Section 3. Statements preceded by ">" were entered on a terminal
screen by a user, whereas the computer issued the other statements and data
to the screen. Statements in boxes suggest a user's thoughts that might
motivate his/her actions. They are not part of the terminal session, but help
explain why various actions were taken.
The example terminal session assumes that the user has already dialed the
appropriate telephone number, is connected with the NCC IBM computer, and is
in a TSO environment.
READY
>EXEC 'JSECON5.BLIS.CLIST(BLIS)'
** ALLOCATING BLISXXX FILES NOW
**BLISXXX DATA BASE FILES ALLOCATED
**ALLOCATING S2KPARMS FILE
**S2KPARMS FILE ALLOCATED
**ALLOCATING SORT/PADOO FILES
**SORT/PADOO FILES ALLOCATED
S2K0104/00 - SYSTEM 2000 INITIALIZATION PARAMETERS FOLLOW -
SDBS=1
SDBSIZE=430
LDBSIZE=1000
POOLO=6216/20/D
POOL1=15456/20/S
PADOO=750/3
RW=YES .
DISK=3380
LIST=YES
EXITS=NO
CONVERT=NO
CORECOV=NO
S2K0131/01- S2KPADOO NOW BEING FORMATTED -
S2K0212/01- SYSTEM 2000 RELEASE 11.5 : -
S2K0213/00- COYPRIGHT (C) 1985 SAS INSTITUTE INC., GARY, N.C. 27511, U.S.
.A. - ::
12/16/87 11:44:17 BEGIN SYSTEM 2000 - RELEASE 11.5
COPYRIGHT (C) 1985 SAS INSTITUTE INC., CARY, N.C. 27511, U.S.A. -
>USER;ANY
USER;ANY:
>DATA BASE NAME IS BLIS:
DATA BASE NAME IS BLIS:
-556- OPENED BLIS 1 286 11/24/87 14:22:29
60
-------
"Looks like I'm connected to the BLIS data base. I wonder
how much data is in the system today."
>TALLY/ALL/ Cl:
TALLY/ALL/C1:
**************************************
ITEM- ID NUMBER
**************************************
MINIMUM- AK-0001
MAXIMUM- WY-0018
1340 DISTINCT VALUES
1460 TOTAL OCCURRENCES
"This tally shows 1460 data entries but only 1340 ID numbers.
There must be a lot of facilities with more than one determi-
nation in the system. I wonder how many determinations were
entered during 1985?"
>PRINT COUNT Cl WH C32 SPANS 01/01/85*12/31/85:
PRINT COUNT Cl WH C32 SPANS 01/01/85*12/31/85:
CNT1*127
'Now, how many determinations are in the data base per State?"
>TALLY/EACH/ C14:
TALLY/EACH/ C14:
**************************************
ITEM- STATE INITIALS
**************************************
OCCURRENCES VALUE
19
23
14
2
5
231
14
4
6
AK
AL
AR
AS
AZ
CA
CO
CT
DE
61
-------
40
22
3
21
6
28
26
16
48
63
6
14
8
52
10
7
7
3
50
4
6
8
20
11
12
157
20
6
40
3
12
24
185
22
91
2
3
21
38
8
18
50
1460
FL
GA
HI
IA
ID
IL
IN
KS
KY
LA
MA
MD
ME
MI
MN
MO
MS
MT
NC
ND
NE
NJ
MN
NV
NY
OH
OK
OR
PA
RI
SC
TN
TX
UT
VA
VI
VT
WA
WI
WV
WY
DISTINCT VALUES
TOTAL OCCURRENCES
"This tally ran off my 20-line screen. I'll have to watch
that. I see that California has the largest number of de-
terminations in the system (231). I wonder how much data
has been permitted since the end of 1985?"
62
-------
>PRINT COUNT Cl WHERE C19 GT 01/01/86:
PRINT COUNT Cl WHERE C19 GT 01/01/86:
CNT 1 * 238
"That's a lot of entries. I wonder how many of those are
LAER?"
>PR COUNT Cl WH C19 GT 01/01/86 AND C17 EQ LAER:
PR COUNT Cl WH C19 GT 01/01/86 AND C17 EQ LAER:
CNT 1* 11
"Now I'll print company names and the ID numbers to see
where these LAER entries came from."
>PR CIO, Cl WH SAME:
PR CIO, Cl WH SAME:
10* GMC-CENTRAL FOUNDRY DIV., SAGINAW GREY IRON PLANT
1* MI-0042
10* FRITO-LAY
1* CA-0085
10* OGDEN MARTIN SYSTEMS OF INDIANAPOLIS
1* IN-0026
10* THE SPECIALTY PAPERS CO.
1* OH-0016
10* STOW & DAVIS FURNITURE CO.
1* MI -0043
10* SHELL CALIFORNIA PRODUCTION, INC.
1* CA-0161
10* DUPONT
1* VA-0045
10* SHELL CALIFORNIA PRODUCTION, INC.
1* CA-0161
10* PETRO-LEWIS CORP.
1* CA-0116
10* J.W. FERGUSSON & SONS, INC.
1* VA-0060
10* KIMSTOCK
1* TN-0020
"This is hard to read and I forgot the ID suffixes. I'll
need those to pull up an entry. I know; I'll use the LIST
command."
63
-------
>LIST C10,C1,C30 WH SAME:
LIST C10.C1.C30 WH SAME:
* COMPANY NAME
***
* GMC-CENTRAL FOUNDRY DIV., SAGINAW GREY IRON PLANT
* FRITO-LAY
* OGDEN MARTIN SYSTEMS OF INDIANAPOLIS
* THE SPECIALTY PAPERS CO.
* STOW & DAVIS FURNITURE CO.
* SHELL CALIFORNIA PRODUCTION, INC.
* DUPONT
* SHELL CALIFORNIA PRODUCTION, INC.
* PETRO-LEWIS CORP.
* J.W. FERGUSSON & SONS, INC.
* KIMSTOCK
ID NUMBER ID SUFFIX
MI-0042
CA-0081
IN-0026
OH-0016
MI-0043
CA-0161
VA-0045
CA-0161
CA-0116
VA-0060
TN-0020
A
B
B
C
"Now I'd like to see a range of emission limits for VOCs,
but first I need to find out what emission units people are
using."
>PRINT C203 WH SA:
PRINT C203 WH SA:
203* LB/H
203* LB/H
203*
% OVERALL CONTROL EFF.
203* T/YR, SEE NOTE
203* LB/T SOLVENT
LB/H
LB/H
LB/H
203*
203*
203*
"I see that LB/H is the most common unit specified.
I pull up the range of values for LB/H."
I think
>PRINT COUNT C202, MIN C202, AVG C202, MAX C202 WH C19 GT 01/01/86 AND
PRINT COUNT C202, MIN C202, AVG C202, MAX c202 WH C19 GT 01/01/86 AND
>C17 EQ LAER AND C201 EQ VOC AND C203 EQ LB/H:
C17 EQ LAER AND C201 EQ VOC AND C203 EQ LB/H:
CNT 202* 5
MIN 202* 3.0700
AVG 202* 33.196
MAX 202* 140.9000
64
-------
"Some of these emissions look pretty low. I'd like to see the
kinds of equipment and efficiencies they used. I have a case
in my jurisdiction where we need to get under 10.0 LB/H. I'll
list the ID number, too, to see which entry I'm looking at."
>LIST C1,C30,C207,C209 WH SAME AND C202 LT 10.:
LIST C1,C30,C207,C209 WH SAME AND C202 LT 10.:
* ID NUMBER ID SUFFIX CONTROL EQUIPMENT
***
* CA-0085 A VENTURI SCRUBBER
* IN-0026
* VA-0060
"The California determination looks interesting. I think
I'll call them up and get more information; but first I
need to get the contact person's name and number."
>PR C23,C24,C25 WH Cl EQ CA-0085 AND C30 EQ A:
PR C23,C24,C25 WH Cl EQ CA-0085 AND C30 EQ A:
23* KERN COUNTY APCD
24* TOM PAXSON
258 (805)-861-3682
"Thanks for the information, BLIS! OH yea, can't forget
to free the data base files,!"
>EXIT:
EXIT:
11:58:10 12/16/87 END SYSTEM 2000 - RELEASE 11.5
COPYRIGHT (.0 1985 SAS INSTITUTE INC., GARY, N.C. 27511, U.S.A. -
ALL DATA BASE FILES AND SYSTEM 2000 WORK FILES ARE STILL ALLOCATED. DO
YOU WISH TO FREE THEM?
>YES
** ALL DATA BASE AND S2K FILES ARE FREED**
** END OF S2K**
65
-------
APPENDIX F
EXAMPLES OF PRINTED TABLES USING LIST COMMAND
66
-------
In this appendix, an example of an extended LIST command is given,
followed by a sample page from the resulting table.
12/17/87 16U7M3 BBG1B STSTXB 2000 - BEiEASE 11.5
(Q 1»»5 sis USTJ.TUTE me., CABT, i.e. 27511, U.S.A. -
OSXB,ABI:OBB IS BL1S:
-*>i- OPEBKD BUS 1 286 11/2V1987 1»:22:2»
LIST/BEPtflT SOPPBESS,
TITLE D (32) BUS BO1LBB UST BI PBOCESS CODE & CAPACITI - OHlO,
7(50)PBOCaSS CODE— 1.1*COA1. 1.2*OJLL 1.3*K 1.H-HOOD 1.5-BULT 1.6-OTHEfi,
L(5)PBOC^OOOB, B(13> BOOl.BB*CAPACiTI, L (15) , L(35) * OOBPABI BABk,
I. (5) »ST*TE, 1(6) EPA+BBSIOB, L («*) BJiFBEBCB* BOBBEB/
ciui,ciOJ,cio*,cio,ci«,ci«»,ci,oia)EajsD BI cioi,cio3
• HEBE C104 BU BBBTQ/B ABO C101 SPAMS 1.1*1.6 ABO C14 EU Ott:
PBOC
COOB
1.2
1.2
K.2
1.2
1..2
llj
\^
1.J
1^
PBOCSSS COOB — 1.1-CDAL
B01LXB
CAPAdTT
11.00
18.10
Jb.OO
b^.00
»8.00
150.00
2JB.OO
b«7.00
10. JO
27.00
«0.00
71.50
118.00
1*4.00
I.Ob
k.OU
1o.80
68.00
J.12
2*0.00
boy.oo
««.oo
Bflan/H
BBBTU/H
BBHTU/H
BBBTU/H
BBBTU/H
BBBTU/H
BBBTU/H
BUTU/H
BBBTU/H
BBBTU/I
BBBTU/H
BBBTU/H
BflBTO/B
BBBTU/H
BBBTU/H
BBBTU/H
BBBTU/B
BBBTU/H
BBBTU/H
BBBTU/H
BBBTU/H.
BBBTU/V
BL15 BU1UI LIST BI PIOCBSS COUB k CAP *C ITT - OHIO
1IC.
COBPABT BiKB
BODEPOBL BBniBfi CU.
SCHAAf UBB ttlUUttOa
KBBBT I»DOSr»IBS
FUBO HO TO! CU.. LIB* EKlIB PLAIT
OIlfEBSlTI HOSPITAL
bB DBLCO PBOOOCTS U1T
B.F. 600OB1CH CU.
CAB GILL, 1»C.
0«B»S-ILLU01S 1JIC.
SBC-CPC BABlLTOa-PAlBFlfLO
T1BIBI CO.
6KIBBAL BILLS, IBC.
6EOIU6A*PAC1/1C COBP.
DELCO BOBAIBB DIf .. tBC
BALB CHBOBB SBBIxCB
BABOB DBA** STKKL
KA1SBB ALOBJUIOB » CHBB1CAL COBP.
SOB BBP1B1B6 k BAUBTIBb CO.
PEBBO CHBH1CAL 1)1 1 OF JTEBMJ COBP.
C1TI OP COLUBBOb
STOBf COBT1IBBB COBP.
CZBTBAL SOIA CO.. IBC.
1.4-46 1.4- HOOD 1.S-COLT l.k-OTHKB
STATE
OH
UH
OH
OH
OH
OH
OH
OU
OH
OH
OH
OH
OH
OU
OH
OB
OH
OH
OH
OH
OH
Oil
SPA
BaGlOB
5
5
3
5
5
3
5
5
5
5
5
3
5
5
5
5
5
5
S
b
5
S
UFBEBCB
BOBSBB
OB-O08J
OH -005 4
OH -001 3
OH-OOOo
OH -002 9
OH -00 10
OH -002 J
OH-O011
OH-O117
OH -0088
OH -002 2
OH -0112
OH-OO94
OH -0071
OH-010*
OH-009*
OH-0107
OH -O lib
OB -0025
OH -0Mb
OB -000 3
OH-OOJ7
67
-------
APPENDIX G
REFERENCES FOR FURTHER ASSISTANCE
68
-------
1. For assistance concerning the BACT/LAER Clearinghouse and its
policies and procedures, contact:
Fred Dimmick
Emission Standards Division (MD-13)
U.S. Environmental Protection Agency
Research Triangle Park, N.C. 27711
Phone (919} 541-5432 or (FTS) 629-5432
2. For assistance concerning the BACT/LAER Information System (BLIS)
and its applications, contact:
Joe Steigerwald
PEI Associates, Inc.
505 South Duke Street
Durham, North Carolina 27701
Phone (919) 688-6338
3. For assistance concerning the operation of IBM, NCC reference manuals,
System 2000 software problems, or user training contact:
User Services
EPA National Computer Center
Research Triangle Park, NC 27711
Phone (919). 541-7862 or (FTS) 629-7862
4. For assistance in obtaining System 2000 user manuals, contact:
Publications Sales Department
SAS Institute Inc.
Box 8000, SAS Circle
Gary, North Carolina 27511-8000
Phone (919) 467-8000
5. For assistance concerning technical problems in establishing com-
munications with IBM, contact:
National Computer Center
Network Control Facility
Phone (919) 541-4506 or (FTS) 629-4506 or
(800). 334-0741
69
-------
APPENDIX H
BLANK BACT/LAER DETERMINATION FORM
70
-------
Mall to: Fred Dimmick
BACT/LAER Clearinghouse
OAQPS, MD-13
RTF, N.C. 27711
BACT/LAER DETERMINATION INPUT SUMMARY SHEET
Source Code
Date of This Report
Source Type/Size:
Company Name/Site Location:
Determination 1s: BACT/LAER For New/Modified Source:
(circle appropriate
definition) Permit No.:
Determination Made By:
Date of Permit Issuance:
Date of Estimated Start-up:
(Agency)
(Person directly Knowledgeable
About Permit)
(Phone)
Permit Parameters:
(List all
processes subject
to this permit)
Maximum
Design
Capacity
*
Pollutant
Regulated
Emission
I1m1t(s) units
of emissions/
units of Input
,**
Reg.
reqmts .
assoc.
w/!1m1t
Control equipment
of process
modification
description
Efficiency
%
Notes:
*Use the following abbreviations wherever possible:PM=part1culate matter, S02=sulfur dioxide, N0x=n1trogen oxides,
C0=carbon monoxide, VOC=volat1le organic compounds, VE=vis1ble emission, TRS=total reduced sulfur, F=fluoride,
Be=beryll1um, H2S=hydrogen sulflde, Hg=mercury, ,VC=vinyl chloride.
**Please use the following abbreviation: B=BACT, L=LAER, N=NSPS, H=NESHAP, A=NAAQS or PSD constraints, S=SIP,
R=RAri. ll=Unreaulated. Page of
-------
APPENDIX I
EPA REGIONAL OFFICE BIN NUMBER ASSIGNMENTS
Region
1
8
10
Bin
81
82
83
84
85
86
87
88
89
90
Address
EPA - Region 1
JFK Federal Building
Room 1007 B
Boston, Massachusetts 02203
EPA - Region 2
26 Federal Plaza
New York, New York
10007
EPA - Region 3
6th & Walnut Streets
Philadelphia, Pennsylvania 19106
EPA - Region 4
345 Court!and Street
Atlanta, Georgia 30308
EPA - Region 5
230 South Dearborn Avenue
Chicago, Illinois 60604
EPA - Region 6
1201 Elm Street
First International Building
Dallas, Texas 75270
EPA - Region 7
324 East llth Street
Kansas City, Missouri 64106
EPA - Region 8
1860 Lincoln Street
Denver, Colorado 80203
EPA - Region 9
215 Fremont Street
San Franscisco, California 94111
EPA - Region 10
1200 Sixth Avenue
Seattle, Washington 98101
Phone
617/223-5885
212/264-9578
212/264-9850
215/597-3530
404/257-2864
312/353-2061
312/353-2303
312/353-2205
214/729-2641
816/758-4285
303/327-2226
415/556-2326
206/399-1580
72
------- |