United States
Environmental Protection
Agency
Industrial Environmental
Research Laboratory
Research Triangle Park,
NC 27711
EPA-600/8-80-031
June 1980
Research and Development
Environmental Assessment
Data Systems
User Guide
Project
Profile
System
-------
RESEARCH REPORTING SERIES
Research reports of the Office of Research and Development, U.S. Environmental
Protection Agency, have been grouped into nine series. These nine broad categories
were established to facilitate further development and application of environmental
technology. Elimination of traditional grouping was consciously planned to foster
technology transfer and a maximum interface in related fields.
The nine series are:
1. Environmental Health Effects Research
2. Environmental Protection Technology
3. Ecological Research
4. Environmental Monitoring
5. Socioeconomic Environmental Studies
6. Scientific and Technical Assessment Reports (STAR)
7. Interagency Energy-Environment Research and Development
8. "Special" Reports
9. Miscellaneous Reports
This report has been assigned to the INTERAGENCY ENERGY-ENVIRONMENT
RESEARCH AND DEVELOPMENT series. Reports in this series result from the effort
funded under the 17-agency Federal Energy/Environment Research and Development
Program. These studies relate to EPA's mission to protect the public health and
welfare from adverse effects of pollutants associated with energy systems. The goal of
the Program is to assure the rapid development of domestic energy supplies in an
environmentally-compatible manner by providing the necessary environmental data
and control technology. Investigations include analyses of the transport of energy-
related pollutants and their health and ecological effects; assessments of, and
development of, control technologies for energy systems; and integrated assessments
of a wide range of energy-related environmental issues.
EPA REVIEW NOTICE
This report has been reviewed by the participating Federal Agencies, and approved for
publication. Approval does not signify that the contents necessarily reflect the views
and policies of the Government, nor does mention of trade names or commercial
products constitute endorsement or recommendation for use.
This document is available to the public through the National Technical Information
Service, Springfield, Virginia 22161.
-------
EPA-600/8-80-031
June 1980
ENVIRONMENTAL ASSESSMENT DATA SYSTEMS
USER GUIDE:
PROJECT PROFILE SYSTEM
J. P. Reider, Editor
Midwest Research Institute
425 Volker Boulevard
Kansas City, Missouri 64110
Prepared for
EPA Project Officer - Gary L. Johnson
U.S. Environmental Protection Agency
Office of Research and Development
Industrial Environmental Research Laboratory
Research Triangle Park, North Carolina 27711
Contract No. 68-02-3177
Work Assignment No. 3
-------
DISCLAIMER
This report has been reviewed by the Industrial Environmental Research
Laboratory, U.S. Environmental Protection Agency, and approved for publica-
tion. Mention of trade names or commercial products does not constitute en-
dorsement or recommendation for use.
-------
This page contains the publication and revision record of the PPS User Guide.
The current revision status is indicated by the Schedule of Document Control.
As the guide is revised, the affected pages are dated. Changes and additions
to the guide are shown by vertical lines in the margins. A bar near the page
number indicates a new pagination rather than change of content. New pages
are indicated by a dot near the page number.
SCHEDULE OF DOCUMENT CONTROL
Revision
Description
June 1980
Original issue.
ill
-------
PREFACE
In the course of fulfilling its charter, EPA performs multimedia envi-
ronmental assessments of stationary sources of pollution and conducts R&D pro-
grams to develop and demonstrate feasible control technology. Such programs
generate voluminous data, often according to different reporting protocols
and sampling and analysis practices. The Environmental Assessment Data Sys-
tems (EADS) has been developed to consolidate the results of these programs
and others into one comprehensive information system.
The EADS is composed of four waste stream data bases and a number of
reference and support data bases. The waste stream data bases include the
Fine Particle Emissions Information System (FPEIS), the Gaseous Emissions
Data System (GEDS), the Liquid Effluents Data System (LEDS), and the Solid
Discharge Data System (SDDS). One of the reference data bases of the EADS
is the Project Profile System (PPS). The PPS contains information that de-
scribes projects in various R&D program areas. In contrast to the EADS waste
stream data bases, the PPS tells "what" was measured, not "how much." The
PPS has been developed primarily to support the Conventional Combustion Envi-
ronmental Assessment (CCEA) program to identify, catalog, and manage informa-
tion on conventional combustion processes.
This document, the PPS User Guide, gives instructions for the encoding
of PPS data sets and defines procedures for submitting and retrieving data.
It also describes available software packages for analysis of PPS data.
-------
CONTACTS
EADS Program Manager
EADS Technical Staff
General PPS Information,
Documentation
Software
Gary L. Johnson (MD-63)
Industrial Environmental Research Laboratory
U.S. Environmental Protection Agency
Research Triangle Park, North Carolina 27711
919-541-2745
J. Patrick Reider
Midwest Research Institute
425 Volker Boulevard
Kansas City, Missouri 64110
816-753-7600
Nick Young
Acurex Corporation
Route 1, Box 423
Morrisville, North Carolina
919-781-9704
27560
or
CCEA Program Manager
CCEA-PPS Technical Staff
Data Base Contents (CCEA)
Richard E. Welch
Acurex Corporation
Route 1, Box 423
Morrisville, North Carolina
919-781-9704
27560
Wade H. Ponder (MD-62)
Industrial Environmental Research Laboratory
U.S. Environmental Protection Agency
Research Triangle Park, North Carolina 27711
919-541-3997
Mary C. Aldridge
Research Triangle Institute
P.O. Box 12194
Research Triangle Park, North Carolina
919-541-5886
27709
VI
-------
CONTENTS
Preface v
Contacts vi
Figures viii
Tables viii
1 Introduction 1.0-1
2 Data Base Description 2.0-1
2.0 PPS Structure 2.0-1
2.1 PPS Organization and Contents 2.1-1
3 Data Acquisition and Organization 3.0-1
3.0 Introduction 3.0-1
3.1 How to Build a Profile 3.1-1
3.2 Data Input Form Structure 3.2-1
4 Encoding Instructions for PPS Input Forms 4.0-1
4.0 General Rules 4.0-1
4.1 Labor Saving Feature 4.1-1
4.2 Encoding Instructions 4.2-1
5 Data Submittal 5.0-1
5.0 Introduction 5.0-1
5.1 Data Input Form Processing 5.1-1
5.2 Submittal Procedures 5.2-1
5.3 Review and Corrective Action Procedures 5.3-1
5.4 EDIT/LOAD Programs 5.4-1
6 Data Retrieval 6.0-1
6.0 Introduction 6.0-1
6.1 Data Retrieval Using the Program Library 6.1-1
6.2 Special Data Retrieval Requests 6.2-1
6.3 Key/Non-Key Data Elements 6.3-1
6.4 On-Line Request Procedures 6.4-1
6.5 NCC User Qualifications and Services Registration . 6.5-1
6.6 Interactive Terminal Operation 6.6-1
6.7 Remote Batch Terminal Operation 6.7-1
6.8 PPS User Support 6.8-1
7 Program Library 7.0-1
7.0 Introduction 7.0-1
7.1 Profile Report 7.1-1
7.2 Chemical Search Program (CHEM-SEARCH) 7.2-1
7.3 Profile Summary Information Program (SNAP-SHOT) . . 7.3-1
7.4 Profile Abstract Program (ABSTRACT) 7.4-1
Appendix A.I - List of Error Messages A. 1-1
Appendix A.2 - Data Definitions A.2-1
Appendix A.3 - PPS Date Base Glossary A.3-1
Appendix A.4 - PPS Data Encoding Forms A.4-1
Appendix A.5 - Tables of Standard Nomenclature A.5-1
vii
-------
FIGURES
Number Page
2-1 PPS data base organization and structure 2.0-3
3-1 PPS structure 3.1-2
5-1 Sample data submittal letter 5.2-2
5-2 Sample data submittal acknowledgement letter 5.2-3
5-3 QA procedure 5.3-2
6-1 NCC application 6.5-2
6-2 Request for batch terminal support form 6.7-2
Number
TABLES
3-1 PPS Data Elements and Their Levels 3.2-2
6-1 List of Key Data Elements 6.3-2
6-2 Remote Interface Control Statements 6.6-3
6-3 NCC Demand Access Telephone Numbers 6.6-6
6-4 NCC Remote Batch Access Telephone Numbers 6.7-3
viii
-------
SECTION 1
INTRODUCTION
The Environmental Assessment Data Systems (EADS) are a group of indepen-
dent computerized data bases which are interlinked to provide common accessi-
bility to data produced by a variety of EPA projects. One of the reference
data base components of the EADS is the Project Profile System (PPS).
The Project Profile System (PPS) is a project management information sys-
tem that has been developed primarily to support a single program: the Con-
ventional Combustion Environmental Assessment (CCEA). The PPS is not, how-
ever, limited to application only to the CCEA, but may be applied to any R&D
program area, such as synfuels production, coal cleaning, iron and steel,
etc.
The data stored in the PPS are compiled on the basis of projects instead
of test sites as is the case of the EADS waste stream data bases. For exam-
ple, the environmental assessment project for a particular industrial process
may involve the sampling of many multimedia test sites, each of which would
be reported separately in FPEIS, GEDS, LEDS, or SDDS. In the PPS, however,
there would be only one entry for the overall project.
The PPS presently contains data on projects conducted by EPA, DOE, etc.,
that pertain to the broad category of conventional combustion. These proj-
ects are grouped into nine different types as follows:
Fuels
Emissions/Effluents Monitoring
Sampling and Analysis Methods Development
Control Technology
Transport, Transformation, and Fate
Health Effects
Ecological Effects
Socio-economic Factors
Integrated Assessments
For the appropriate project types, much of the same terminology from the
EADS waste stream data bases is used. The principal difference is that the
PPS does not contain any numerical data; that is, the PPS may identify what
pollutant was measured, but it will not report any concentration values. The
PPS is used by the CCEA program to identify, catalog, and manage information
on conventional combustion processes.
1.0-1
-------
The origin of the PPS is the CCEA program. To understand the utility of
the PPS, it is appropriate to examine briefly the CCEA and the rationale for
the development of the PPS.
The CCEA program demonstrates a comprehensive approach to identify, ac-
quire, and analyze all information relevant to the environmental assessment
of conventional combustion processes. The purpose is to provide to EPA, other
federal and state agencies concerned with environmental protection, combus-
tion and control equipment designers and users, and other interested parties,
valid, comprehensive information to form the basis for specifying those activ-
ities and procedures that will enable operation of such processes in a manner
protecting human health and welfare, and the nation's air, water, and land re-
sources .
Because of the fundamental importance and widespread use of combustion
devices for energy production, industrial processing, space heating, and many
other purposes, identification of potentially harmful substances released
from combustion and ancillary equipment and processes is essential. Quanti-
fication of amounts released under various operating conditions is equally as
important. This identification and quantification requires the application
of, and quite often the development of, reliable and accurate techniques for
sampling and analysis. The transport of pollutant species, distribution, and
possible transformation of such species must be understood and quantified.
The acute and chronic effects of pollutants on human health and on the ecosys-
tem must be understood and quantified. Criteria for the quality of the media
must be developed and specified as environmental goals set with due regard
for human health, ecological integrity, and the realization that a careful
balance must be maintained between a thriving, technology-based society and
its natural environment.
Comparing these environmental goals with the types and rates of emission
of pollutant species from combustion sources burning various fuels provides a
measure of the degree of control that must be employed to attain the desired
goals. The availability of effective control devices and processes must be
ascertained, and the necessary research and development stimulated to produce
more effective controls where needed. Among the important outputs of the
CCEA program are recommendations for environmental standards. These recom-
mendations are based on the perceived scope of the environmental impact, the
types of pollutants involved, and the state-of-the-art of the control technol-
ogy available with quantification of its cost, energy usage, and effective-
ness .
Because of the complexity of the CCEA program and the large amount of in-
formation and data that must be assembled and analyzed to direct the program
toward its objectives, it was hypothesized that a computer-based management
information system could be a cost-effective tool for program management.
Accordingly, a pilot-type demonstration using only a few projects to illus-
trate the method was proposed, authorized, and conducted. The demonstration
proved the feasibility of the concept and the development of the PPS ensued.
1.0-2
-------
The PPS provides a guide or "road map" to combustion data stored in the
EADS waste stream data bases. While the PPS identifies what work was done,
the EADS waste stream data bases contain the actual results. In the context
of the CCEA, the PPS will provide important initial information about proj-
ects relating to a particular aspect of conventional combustion (e.g., who
did the work, were there any reports, what pollutants were measured, etc.).
If there are sampling data in the EADS from that particular project, refer-
ences to the EADS Test Series Number (TSN) will be given in the Project Pro-
file. In this way, the user can obtain the actual data if he wishes.
Of course, not all project types reported in the PPS will be relevant to
the EADS waste stream data bases. An attempt has been made, however, to uti-
lize the standard EADS terminology protocol described in the EADS Terminology
Reference Manual, EPA-600/8-80-011, February 1980.
The design of the PPS allows its application to industrial source cate-
gories other than conventional combustion. For the present, however, the PPS
will continue to support only the CCEA.
A uniform protocol for units and terminology has been developed along
with standard data input forms, output report formats, and analytical soft-
ware. Each data element in the system has been defined in detail for clarity.
These standards and definitions will allow all data in the system to be stored
and retrieved on a common basis.
The PPS has been implemented at the Environmental Protection Agency (EPA)
National Computer Center (NCC) at Research-Triangle Park, on the UNIVAC 1100
computer, using SYSTEM 2000 . SYSTEM 2000 is a data base management system
developed by the Commercial Systems Division of INTEL, Inc. Features of SYSTEM
2000 include sorting, comparing, and retrieving information from the PPS data
base in a variety of arrangements and provides users with a virtually unlimited
potential for data analysis.
Section 2 through 7 of this document provide detailed information on the
PPS. Section 2 describes the structure, organization, and contents of the
PPS. Section 3 demonstrates an application of a project to the structure and
how data should be organized for an encoding effort. Encoding instructions
are given in Section 4. Section 5 describes procedures required after data
have been encoded and are being submitted for inclusion in the PPS. Section 6
describes the steps for on- and off-line data retrievals. User output analysis
packages are enumerated in Section 7 -- Program Library. Users should become
thoroughly familiar with the contents of this document before attempting to en-
code data.
1.0-3
-------
SECTION 2
DATA BASE DESCRIPTION
2.0 PPS STRUCTURE
The discussion in this section is intended to introduce the new EADS user
to the PPS data base. The main objective is to familiarize the user with the
fundamental structural components of the data base and how they are assembled
to form a structural hierarchy. While the four emissions data bases within
EADS are structured in an identical manner, the PPS data base, being a refe-
rence data base, has its own unique structure.
The structure of the PPS data base presents and organizes a comprehen-
sive set of data which describes the conduct, techniques, and objectives of
R&D projects. Only nonemissions data is contained within this data base.
Each variable or bit of data or information concerning the project is defined
as a data element. The completeness of information for any given project
within the data base is limited only by the completeness of the test report
or original data source from which the PPS input was derived.
Before continuing on this section, the user should become familiar with
certain terms used throughout the EADS document. Many of the terms will prob-
ably be familiar, but others such as "test" may, in the context of PPS, have
definitions that are slightly different from the typical definition. In order
to maintain the integrity of the data, it is imperative that these definitions
are understood and properly used.
media—
source--
stream—
control device/
treatment process-
Used in reference to an effluent stream from a station-
ary source. May be either gas, liquid, or solid.
A source may be either an industrial or energy conversion
facility. It is an origin of one or more multimedia efflu-
ent streams. An oil refinery and a coal-fired power plant
would each be examples of a source.
Any multimedia effluent discharging to the environment
from a stationary source.
A device or process designed to remove or treat a specific
pollutant or pollutants in an effluent stream.
2.0-1
-------
control system-- Frequently a discharge stream is controlled by a number
of control devices which may be in either a series or par-
allel arrangement. The total group of control devices on
that stream is referred to as the control system.
level-- A data base structural term used to differentiate group-
ings of data within the data base. The PPS contains five
structural levels: the administrative level, the activity
level, the test level, the analysis level, and the pollut-
ant level.
test-- A set of various types of samples taken to characterize
a source waste stream(s) under one set of source and con-
trol device/treatment process operating conditions.
sample-- The measurement or group of measurements taken with a
single measurement method or instrument to describe the
composition of a stream at a given point in time and at a
specific location.
Several data elements or information items are required to adequately
describe the groups of information which are contained within the PPS. These
groups are discussed in the EADS Systems Overview Manual and in greater de-
tail in this section. Also, the reader may wish to refer to the Data Base
Definition (a computer listing of all data elements) and the Data Base Tree
(a graphical presentation of the major groups of information contained in the
data base) in Figure 2.1. From an organizational standpoint, the various ele-
ments are grouped into one of five levels: the administrative level, the activ-
ity level, the test level, the analysis level, and the pollutant level. These
levels and their relationship within the Data Base Tree are shown in Figure
2-1.
2.0-2
-------
EADS PROFILE
(A)
Report S«quence Number
Report Title
Report Authors
Sponsor Report Number
NTIS Number
Report Published Dot*
Issue Date
EADS Profile Number
Program Name
Project Type Code
Project Sponsor
Sponsor Branch Code
Sponsor Division Code
Sponsor Laboratory Code
Project Start Date
Project Finish Date
Sponsor Street Address/P.O. Box
Sponsor City
Sponsor State
Sponsor Zip/Mail Code
Sponsor Country
Agency Inventory Number
Date of PPS Entry
Project Officer
Project Officer Telephone
Contract No./Grant No.
Fiscal Year
Funding (KS)
Project Title
Contractor Name
Contractor Street Address/P.O.Box
Contractor City
Contractor State
Contractor Zip/Mail Code
Contractor Country
Contractor Project Manager
Contractor Project Manager Telephone
Line Number
Abstract as Text
| . ADMINISTRATIVE LtVtl
~~ —— . ~~~ ~~~ - I
ACTIVITY
(D)
Activity Number
Task Order/TD Number
Activity Start Date
Duration
FPEIS TSN
GEDS TSN
LEDS TSN
SDDS TSN
FEIS TSN
Primary Activity
Activity Frequency
Source Name
Activity Location
Source Category
Source Type
Product/Device
Process Type
Feed Material Category
Feed Material Type
Line Number
Comments
L ACTIVITY LEVbL
TEST/CONTROL
SYSTEMS
(E)
Test ID Number
Project Topic
Methods
Issues
Approach
Factors
Media
Pollutant Control Generic Device
Pollutant Control Design Type
Pollutant Control Process
Line Number
Test Comments
|
TEST LEVEL
ANALYSIS
(F)
Analysis Number
Analysis Designation
Analysis Location
Test Type
Test Description
Serial Number
Test Strains/Organisms/£cosystems
Line Number
Analysis Comments
ANALYSIS LEVEL
POLLUTANTS
(G)
Pollutant Number
Pollutant Media
Pollutant Type Code
Pollutant Code
Sampling Technique Code
Analytical Technique Code
Sampling Location Code
POLLUTANT LEVEL
Figure 2-1. PPS data base organization and structure.
2.0-3
-------
2.1 PPS ORGANIZATION AND CONTENTS
The PPS data base structure contains five levels progressing from general
information to specific information. These levels are simply an organizational
tool—enabling the data to be arranged in a manner which is logical from the
user's viewpoint. Each level contains specific types or groups of data. Fig-
ure 2-1 shows the relationship between these general groups into the following
general categories (levels): (a) general administrative, reference information,
and profile abstract (adminstrative level); (b) source description and activity
information (activity level); (c) information on specific tests and control
systems or techniques (test level); (d) information on various analytical proto-
cols and analysis techniques used (analysis level); and (e) information on
specific pollutants assessed (pollutant level).
2.1.1 Administrative Level
This is the uppermost level in the data base structure and contains data
elements which should completely profile one project of a given type.
Typical information found at this level includes the project title, spon-
sor and contractor names and addresses, funding information, important project
dates, responsible persons, and a complete project abstract. Information con-
cerning all reports generated by a specific project is also included. All
information related to the conduct or administration of the contracted project
would be found at this level.
2.1.2 Activity Level
A specific project might include a number of different sampling activi-
ties at different locations over a long period of time. All administrative
and reference information common to all these activities would be found at
the Administrative Level. Information at the activity level would refer to
the sampling activities performed at a single site over a specified period of
time (usually continuous). It is likely that the results of such activities
would have been entered into one or more of the emissions data bases of EADS;
therefore, the appropriate cross-reference test series number(s) would be en-
tered as data elements of this level. Other information found at this level
includes source type and category, feed material category and type, the process
type, product or device, the duration of testing, and the activity location.
Basically, all information needed to completely specify the site and source
are included at this level.
2.1.3 Test Level
As was noted before, administrative and reference information concerning
an entire project would be found at the Administrative Level. Such a project
might include sampling activities at many different sites during many different
periods. Reference information concerning these activities at any one site
on any one source would be found at the activity level. The purpose of the
activity identified at the activity level is described at the test level.
2.1-1
-------
Information found at this level include the primary issues considered in the
assessment, the general methods or approach used, and the factors analyzed by
the project.
For any single source, many different control devices or techniques might
be employed. All of the reference information concerning any one of these
control devices, systems, or techniques would be found at this level. Infor-
mation contained at this level include the generic type of control or treatment
system or device, an identification of the media being studied, and the design
type of the generic device. Any information pertinent to the control system
or technique would be found at this level.
2.1.4 Analysis Level
Many different sampling and analysis protocols and techniques might be
employed at any particular source. The Analysis Level isolates on one samp-
ling or analysis method and contains all the information pertinent to such an
activity. Information found at this level include the type of analysis using
an analysis designator and the location of the analytical laboratory. Biologi-
cal and ecological assay information is also contained at this level with the
test type, test description, and the test strains/organisms/ecosystems included
In general, all information concerning a bioassay will be found at this level.
2.1.5 Pollutant Level
The Pollutant level has the narrowest focus of the five levels and is
concerned solely with specific pollutants sampled and analyzed. Information
included at the Pollutant Level consists of the pollutant type and code, samp-
ling and analytical techniques codes, plus the sampling location code. All
information concerning identified pollutants will be found at this level.
2.1-2
-------
SECTION 3
DATA ACQUISITION AND ORGANIZATION
3.0 INTRODUCTION
The purpose of this section is to demonstrate how an encoder would use
the structural concept discussed in Section 2 to prepare data for encoding
into the PPS. Although peculiar situations and special problems may occur
during the encoding process, the general guidelines and techniques given here
should greatly facilitate the task. Feel free to call the EADS Program Manager
or the EADS Technical Staff listed on page vi if any questions arise during
the encoding process.
3.0-1
-------
3.1 HOW TO BUILD A PROFILE
This section describes the techniques and the thought processes that the
user should employ when encoding data onto the PPS data input forms. The tech-
niques described here will be of particular benefit to the user who is not
familiar with the PPS system and its underlying concepts.
In most cases, the encoder will have either a test report or perhaps proj-
ect abstracts obtained from the contracting organization. The problem that
confronts the user is how to efficiently and accurately transfer the data onto
the PPS data input forms. Experience has shown that the most efficient thing
to do is organize the information before encoding. The key to the organiza-
tion of data is the tree structure of the PPS, shown in Figure 3-1. The first
step is to determine the project type which describes the project to be pro-
filed. There are nine project types as follows: Fuels; Sampling and Analysis;
Emissions/Effluents Monitoring; Controls; Transport, Transformation, and Fate;
Health Effects; Ecological Effects; Integrated Assessment; Socioeconomic Fac-
tors.
Data are arranged so that general information items, such as the admini-
strative data, reference information, and profile abstract, are located at
the top of the tree (Administrative Level). The next level (Activity Level)
contains the source description and the sampling activity information. The
tree continues by including the tests performed on the source and the control
device(s) applied to that source (Test Level). The next to last level in the
tree contains data on the analytical results of samples taken during each test
(Analysis Level). The final level (Pollutant Level) is where the most specific
information is contained in the data base. This level includes the pollutant
media, specific pollutants, sampling and analysis techniques, and sampling
locations. It is helpful to think of the tree structure as descending from
the general or administrative level to the specific or pollutant level.
How then does the user arrange the information into the structure? The
user should lay out a structure on paper similiar to that shown in Figure 3-1.
There will be one box at the first level to represent the general information.
The activity level will contain as many boxes as there are activities performed
or sources tested. In a like manner, the test level will contain one box for
each test performed on each source or at each activity. Next, at the analysis
level, each test will contain as many boxes as there are analytical results
reported. And finally, the pollutant level will contain one box for each pol-
lutant identified in the analytical results. The user should then assign ap-
propriate labels, according to the data, to the activity, tests, analyses,
and pollutants, and enter those labels in the corresponding boxes of the tree.
This approach has two major benefits. One, it forces the user to understand
and organize his data, and two, it structures the data in a manner that aids
tremendously in encoding and proper ordering of the forms. You will recall
that the data forms are organized in a manner similar to the data base itself.
They proceed from the general to the specific.
Section 4 contains detailed encoding instructions which, when used in
conjunction with the above organization methods, make the encoding task
straightforward.
3.1-1
-------
Administrative Level
EADS
Profile (A)
Profile
Elements (A)
Test Level
Test/
Control
Systems (E)
Analysis Level
Pollutant Level
Pollutants
(G)
Figure 3.1. PPS structure
3.1-2
-------
3.2 DATA INPUT FORM STRUCTURE
The PPS data elements (see Table 3-1) are entered on seven data input
forms. The layout of the seven forms is such that the data elements in any
one project profile that are least likely to change, are located on Form 1,
and the most likely to change are on Forms 6 and 7. It becomes apparent that
the input forms one arranged according to the hierarchial structure of the
data base as shown in Figure 2-1.
The administrative data group, which includes detailed information on
the project sponsor, contractor organization, project dates, and fiscal in-
formation, are contained on Form 1 (see Appendix A.4 for input data forms).
The profile element codes are also included at the bottom of Form 1.
The reference information pertaining to reports issued for a project are
on Form 2. The data elements for cards B01 through B04 are repeated on the
bottom half of Form 2. It is permissible to use as many Form 2's as necessary
to list all reports published for a project.
A text abstract of the project is contained on Form 3. The abstract should
be complete without being too wordy. Additional forms may be used, if required,
to complete the abstract.
The activity level data group, which includes the activity description,
source classification, feed material categorization, and the EADS multimedia
cross-reference numbers for quantified emission values, are contained on Form
4. The comments section is available for any pertinent information concern-
ing the activity described.
The test data and control system identification data are found on Form
5. The description of the test conducted includes the project topic, sampling/
analysis methods used, primary issues considered, and the general approach
used in the project. The control system data includes the media classifica-
tion, and the specific identification of the control device/process. The test
comments section is available for any remarks regarding the test conducted.
Form 6 includes analytical information from biological or ecological assays.
The test results identify the type of analysis, test description, test type,
and the test strains/organisms/ecosystems used. For each F03 card only one
test strain/organism/ecosystem may be entered. However, it is permissible to
use additional Form 6's, if necessary, in order to list all test strains/organisms/
ecosystems reported.
The pollutant(s) identification, sampling technique, analytical technique,
and sampling location are contained on Form 7. Because some test plans may
be extensive and cover multimedia sampling and analysis, Form 7 is expected
to be the most frequently used form.
3.2-1
-------
TABLE 3-1. PPS DATA ELEMENTS AND THEIR LEVELS
NJ
Admin 1st ratI ve Level
Admlnlstrat lyc_ l)a ta
EABS Profile Number
Program Name
Pro Joe r Type Code
Project Sponsor
Sponsor Branch Cotlc
Sponsor Division Code
Sponsor Laboratory Code
Project Stair Date
Pro|ect Finish Date
Sponsor Street A.ldress/P.O. Box
Sponsor City
Sponsor Stale
Sponsor Zip/Mall Code
Sponsor Country
Agency Inventory Number
Date of PPS Entry
Project Officer
Project Officer Telephone-
Contract No./Grant No.
Fiscal Year
Funding (K$)
Project Title
Contractor Nam
-------
SECTION 4
ENCODING INSTRUCTIONS FOR PPS INPUT FORMS
This section presents detailed, card-by-card, encoding instructions for
each PPS data element on the Standard Data Input Forms. The instructions are
separated into seven groups (identified by the letters A, B, C, D, E, F, and
G) corresponding to the major groupings of PPS data elements. The PPS Data
Input Form number (1 through 7) is given for each group. While reading these
instructions, it would be beneficial to refer to the blank input forms in Ap-
pendix A. 4.
4.0 GENERAL RULES
General instructions that apply to data coding include the following:
The letter "0" is to be encoded "0" and zero is encoded "0".
Zeros are treated as numbers. Blank spaces in a field indicate either
a lack of data, or that the pertinent data have been coded for the
preceding test conditions or sampling activity. (See the discussion
on the repetitive data feature in Section 4.1.) To blank out a data
field, or to prevent data from being automatically repeated by the
EDIT program, encode 9999... in all columns in the field for numeric
fields, and NA in the first two columns of the field for alphanumeric
fields.
All numeric data shall be right-justified and all alphanumeric data
shall be left-justified, except where noted otherwise.
Only specified alphabetical or numerical characters and a few sym-
bols (%, &, #, /• +, -, <, >, and all punctuation marks except the
colon) are allowed to be entered in the columns where allowed. No
unusual marks are to be made in the spaces. No data field headings
are to be changed and only data appropriate to the field are to be
entered. This rule prevents unnecessary keypunching errors in pro-
cessing the forms. No colons are permitted anywhere.
The small triangle between columns on the forms represents the decimal
point. Enter the fractional decimal digits to the right of the triangle
Leave all the shaded portions on the forms blank.
4.0-1
-------
The following identification data elements must be entered on the
first card of every section (data group) where they appear.
Data element
EADS profile number
Activity number
Test ID number
Analysis number
Pollutant number
Card columns
1-5
9-11
12-13
14-15
16-17
Instructions
Enter on all forms.
Enter only on Forms 4 through
Enter only on Forms 5 through
Enter only on Forms 6 and
Enter only on Form 7.
7.
Note that if encoding instructions are not given for card columns 1
through 8 for any card, the instructions are the same as those for
the previous card.
In several instances, more cards than allotted on the forms may be
added by the user if needed to encode all the data. The detailed
encoding instructions indicate which data elements have unlimited
use.
Whenever the data exceed the available space on the forms, use the
available space completely, then finish the discussion by using the
comments section of the appropriate level (i.e., activity, test, or
analysis comment sections).
Whenever there are pertinent data for which no data elements exist,
use the comments section of the appropriate level.
Make the comment text as brief as possible through the use of abbre-
viations, precise words, and elimination of redundant words. The
text should always start at the leftmost column (i.e., left-justified),
After all the forms are encoded and put in order paginate the forms
in the indicated spaces to keep them organized and to prevent
loss.
• It is critical to include all cards which start a data group. Spe-
cifically, these cards are A01, B01, C01, D01, E01, F01, and G01.
These cards initialize indices which are used to load the data into
the data base. These indices are the EADS Profile Number, the Activ-
ity Number, the Test ID Number, the Analysis Number, and the Pollutant
Number, for the above cards, and the asterisked entries below indicate
where they first occur.
The information that is REQUIRED on these cards is as follows:
4.0-2
-------
Card A01-- *EADS profile number
Program name
Project type code
Project sponsor
Card B01-- EADS profile number
^Report sequence number
Card C01— EADS profile number
*Line number
Card D01— EADS profile number
*Activity number
Card E01— EADS profile number
Activity number
*Test ID number
Card F01— EADS profile number
Activity number
Test ID number
"'Analysis number
Analysis designator
Card G01-- EADS profile number
Activity number
Test ID number
Analysis number
"'Pollutant number
These cards and data elements must be included even if no other data are en-
coded.. The initial card must be included whenever any of the indices are re-
initialized; that is, whenever the encoder returns to the start of a data group.
For example, when a second analysis is reported, the encoder must include another
F01 card with a new analysis number.
4.0-3
-------
4.1 LABOR SAVING FEATURE
In developing the data input forms and the data processing programs, a
labor saving feature is introduced to reduce time, labor, and cost on the part
of the encoder. However, misunderstanding of this feature may result in the
entering of erroneous data. If the explanation is not clear, the safe rule to
remember is "if in doubt, fill it out."
4.1.1 Repetitive Data Feature
The "Repetitive Data Feature" frees the encoder from having to enter repet-
itive data. In general, this means that asterisked (*) fields on the data
input forms need only be filled out when there is a change in the value of
that field from the previous data element value. For example, a testing pro-
gram may have many data elements which do not change from the first value en-
coded. Once the data element value has been initialized, the remaining data
element values do not have to be encoded (or keypunched) for that particular
value. The PPS EDIT program will automatically duplicate that data element
value when the test profile is being processed for loading into the data base.
In many instances, a particular data element may not be constant for all
its occurrences. It may have one value for its first few occurrences, then
change values or not be known for other occurrences. In these situations,
the value of the data element must be reinitialized to the new value each time
the value changes. If the data is not known, the correct way to reinitialize
the value is to enter "NA" in the first two columns of the field for alphanu-
meric data or "9" in every card column for numeric data.
4.1-1
-------
4.2 ENCODING INSTRUCTIONS
This section presents detailed, card-by-card encoding instructions for
each PPS data element. The instructions are separated into the major group-
ings of the PPS data base.
Specific encoding instructions are outlined for each project type (i.e.,
1 through 9). Since some of the project types have similiar data, the encod-
ing instructions have been grouped together for commonality. Project types
1, 3, and 4; 2 and 5; 6 and 7; 8 and 9 have been combined in the following
instructions.
Data groups A, B, and C, the Administrative Data, Reference Information,
and Profile Abstract, respectively, are general information which will apply
to all project types. Specific encoding instructions have been detailed for
groups D, E, F, and G which are Activity Level, Control Systems Data, Analy-
sis Level, and Pollutants, respectively, for all project type groups.
Many data elements, identified in the detailed encoding instructions,
require standard nomenclature. The user must use data from the tables given
in the EADS Terminology Reference Manual or Appendix A.5 of this report to
encode these data elements. All standard nomenclature is left-justified.
4.2-1
-------
4.2.1 Detailed Encoding Instructions for All Project Types
GROUP A - ADMINISTRATIVE DATA - FORM 1
Card column
Data element
Encoding instructions
Card API - Required Card
1-5 EADS Profile Number
6-8 Card Number
9-16 Program Name
17-18 Project Type Code
19-48 Project Sponsor
49-52 Sponsor Branch Code
53-57 Sponsor Division Code
58-66 Sponsor Laboratory Code
67-72 Project Start Date
73-78 Project Finish Date
J9-80
Blank
Enter as a right-justified integer number
the permanent project profile number, as-
signed by the EADS/PPS data base admini-
strator.
Do not change.
Enter as text the name of initials of the
overall program in which the specific proj-
ect profile is included (e.g., CCEA,
Synfuels).
Enter a two-digit code denoting the project
type selected from standard codes in
Table A.5.1.
Enter as text the name of the project
sponsor.
Enter the code or the abbreviation for the
branch of the agency sponsoring the project
as text. An example is PRTB for Process
Technology Branch.
Enter the code or the abbreviation for the
division of the agency sponsoring the pro-
ject as text. An example is UIPD for Util-
ity and Industrial Power Division.
Enter the code or abbreviation for the
agency laboratory sponsoring the project
text. An example is IERL-RTP for Indus-
trial Environmental Research Laboratory
at Research Triangle Park.
Enter the project starting date as MM-DD-YT.
Enter the project finishing date as
MM-DD-YY.
Leave blank.
4.2-2
-------
GROUP A (contiaued)
Card column
Card A02
9-28
29-48
49-50
51-56
57-63
64-70
71-76
Data element
Encoding instructions
39-58
Sponsor Street Address/P.O. Box
Sponsor City
Sponsor State
Sponsor Zip/Mail Code
Sponsor Country
Agency Inventory Number
Date of PPS Entry
Blank
Project Officer
Project Officer Telephone Number
Enter the number and name of the sponsor's
street address or P.O. Box number as text.
Enter the name of the city, township, or
area where the sponsor is located.
Enter the two-letter code for the state or
Canadian Province in which the sponsor is
located. Use the standard nomenclature in
Table A-3 in the EADS TRM.*
Enter the sponsor's zip/mail code.
Enter as text a code or an abbreviation
for the country in which the sponsor is
located. Use standard nomenclature pro-
vided in Table A-3 in the EADS TRM.
Enter as a right-justified integer number
the unique ID number assigned by the agency
performing the inventory.
Enter the date the information was recorded
for entry into the PPS data base, as
MM-DD-YY.
Leave blank.
Enter the name of the sponsoring organiza-
tion's main project officer with a first
name, middle name, and last name format.
Enter as text the entire telephone number
of the project officer including area code
and extension (e.g., 816-753-7600 Ext. 587)
Enter FTS number, if known as FTS-555-9000.
Larkin, K., B. Ballard, Editors, EADS: Terminology Reference Manual, EPA-600/8-80-001,
February 1980.
4.2-3
-------
GROUP A (continued)
Card column
Data element
Encoding instructions
59-80
Card A04
Contract Number/Grant Number
Fiscal Year
9-12,
20-23,
31-34, 42-45, 53-56, and
64-67
13-19, Funding (K$)
24-30,
35-41, 46-52, 57-63, and
68-74
75-80 Blank
Cards A05 and A06
9-80
Card A07
9-38
39-58
59-78
79-80
Project Title
Contractor Name
Contractor Street
Address/P.O. Box
Contractor City
Contractor State
Enter the number of the sponsoring organi-
zation contract as text with the inclusion
of blank spaces and hyphens.
Enter the fiscal year funds were allocated
as FY . A maximum of 6 values may be
entered on a single card and additional
cards may be used as needed.
Enter the level of funding for the fiscal
year indicated in the previous data item in
thousands of dollars with decimal notation
for fractional amounts. Multiple entries
may be encoded on a single card as needed
Leave blank.
Enter as text the complete title of the
project without using any abbreviations.
Use both cards when necessary.
Enter the name of the contractor organiza-
tion as text. Standardized abbreviations
and symbols are given in Table A.5.2.
Enter the number and name of the contrac-
tor's street address or P.O. Box as text
or the department or lab, if the contractor
is a university.
Enter the name of the city, township, or
area where the contractor is located.
Enter the two-letter code for the state Or
Canadian Province in which the contractor
is located. Use the standard nomenclatur~
in Table A-3 in the EADS TRM.
4.2-4
-------
GROUP A (concluded)
Card column
Data element
Encoding instructions
Card A08
9-14
15-21
22-51
52-71
72-80
Card-A09
9-12,
13-16,
17-20,
Contractor Zip/Mail Code
Contractor Country
Contractor Project Manager
Contractor Project Manager
Telephone Number
Blank
Profile Element Codes
,77-80
Enter the contractor's zip/mail code.
Enter as text a code or an abbreviation
for the country in which the contractor
is located. Use standard nomenclature
provided in Table A-3 in the EADS TRM.
Enter the name of the contractor's main
project manager.
Enter as text the telephone number, includ-
ing area code and extension, of the con-
tractor's project manager (e.g.,
215-323-8020 Ext. 112).
Leave blank.
Enter the code(s) which appropriately iden-
tify objectives achieved in the project us-
ing Table A.5.3 for standard nomenclature.
A maximum of 18 profile codes may be entered
on a single card. Additional cards may be
used as needed.
4.2-5
-------
GROUP B - REFERENCE INFORMATION - FORM 2
Card column
Data element
Encoding instructions
Card BQ1 and BQ2
9-10 Report Sequence Number
11-80 Report Title
Card B03
11-80 Report Authors
Card B04
11-31 Sponsor Report Number
32-51 NTIS Number
52-66 Report Published Date
67-72 Issue Date
73-80 Blank
Enter a sequential integer number for each
each reference to be encoded.
Enter the complete title of the report
(which may be continued on the B02 card)
as text with no abbreviations in the title
Enter the name(s) of the author(s) of the
report. The main author is listed by last
name, first name, and middle initial.
Enter as test the number, as assigned bv
the sponsoring organization, of the report
in which the data are reported.
Enter the National Technical Information
Service (NTIS) publication number of the
report as text.
Enter the publications date printed on th
report in text form as month and year fp
May 1980). -8
Enter the date as MM-DD-YY in which the
report was actually issued.
Leave blank.
4.2-6
-------
GROUP C - PROFILE ABSTRACT - FORM 3
Card column
Data element
Encoding instructions
Card C01
9-11 Line Number
12-80 Abstract or Text
Enter a sequential integer number for each
line of abstract text recorded.
Enter as text an abstract of the project
including any pertinent keywords.
Unlimited cards may be added as needed.
4.2-7
-------
Specific Encoding Instructions for Project Types 1, 3, and 4
(Fuels; Emissions/Effluents Monitoring; and Controls)
GROUP D - ACTIVITY LEVEL - FORM 4
Card column
Data element
Encoding instructions
Card DPI
9-11 Activity Number
12-45 Task Order/T.D. Number
46-51 Activity Start Date
52-55 Duration
56-60 FPEIS TSN
61-65
66-70
GEDS TSN
LEDS TSN
Enter a sequential, integer number for each
sampling activity reported.
Enter the task order or technical directive
number as text.
Enter the sampling project start date as a
right-justified integer in the form of
MM-DD-YY.
Enter the length of testing in months as a
decimal number with an implied decimal
point indicated for fractional amounts.
Enter the EADS/FPEIS Test Series Number per
taining to fine particle sampling informa-
tion which was collected from the same
source.
Enter the EADS/GEDS Test Series Number per.
taining to gaseous emissions information
which was collected from the same source
Enter the EADS/LEDS Test Series Number ner.
taining to liquid effluents information
which was collected from the same source
71-75
76-80
SDDS TSN
FEIS TSN
Card D02 - Not Required
Enter the EADS/SDDS Test Series Number a
ciated with solid discharge sample and SS°
analysis from the same source.
(Data elements to be completed at a lat*»
date.) r
4.2-8
-------
GROUP D (continued)
Card column
Data element
Encoding instructions
Card DQ3
9-11
12-46
47-80
Card D04
9-11
12-31
32-51
52-80
Activity Number
Source Name
Activity Location
Activity Number
Source Category
Source Type
Product/Device
Card DOS
9-11 Activity Number
12-31 Process Type
32-41 Feed Material Category
42-51 Feed Material Type
52-80 Blank
Same as Card D01.
Enter the name of the source as text.
Enter as text the source location of the
sampling activity reported.
Same as Card D01.
Enter the code for the major grouping of
generic industries or source classes as
from Table A-l in the EADS TRM. Example:
COMBUST-ENERGY.
Enter as text the code for the source type
as found in Table A-l in the TRM. This
identifies the kind of source within the
source category. Example: INDUSTRIAL.
Enter the code for the product or device
type as text from Table A-l in the TRM.
This identifies the general process or
specific product. Example: BOILER.
Same as Card D01.
Enter the code for the unique process or
specific type of boiler or engine being
tested as text from Table A-l. Example:
FIRETUBE.
Enter as text the code for the general
categorization of the process feed material
or fuel from Table A-2 in the EADS TRM.
Enter the code for the specific type of
feed material or fuel as text using
Table A.5.6.
Leave blank.
4.2-9
-------
GROUP D (concluded)
Card column
Data element
Encoding instructions
Card D06
9-11
12-13
14-80
Activity Number
Line Number
Comments
Same as Card D01.
Enter a sequential, integer number for each
line of activity level comments.
Enter any pertinent comments on the sampling
at the site as text. Additional cards may
be used as needed.
4.2-10
-------
GROUP E - CONTROL SYSTEMS DATA - FORM 5
Card column
Data element
Encoding instructions
Card E01
9-11
12-13
14-28
29-80
37-54
55-80
Card £03
9-11
12-13
14-18
Activity Number
Test ID Number
Project Topic
Methods
Activity Number
Test ID Number
Issues
Approach
Factors
Activity Number
Test ID Number
Media
Same as Card D01.
Enter a sequential, integer number for each
test conducted.
Enter the code as text for the project topic
per site, either SAMPLING or ANALYSIS for
project type 2. For project type 5, enter
TSF for transfer, TSP for transformation,
and F for fate, or any combination of these
three.
Enter as text each sampling/analysis method
or name of equipment used in obtaining a
sample or analyzed results. Use the
standard nomenclature in Table A.5.7.
Same as Card D01.
Same as Card E01.
Enter as text the primary issues considered
in the assessment. Use Table A.5.8 for
standard nomenclature.
Enter as text the general method or approach
used in the assessment. Use Table A.5.9 for
standard nomenclature.
Enter as text the factors analyzed in the
project using Table A.5.10 for standard
nomenclature.
Same as Card D01.
Same as Card E01.
Enter as text the code for the generalized
name of the media in which the sample was
extracted. Use the standard nomenclature
in Table A.5.11.
4.2-11
-------
GROUP E (concluded)
Card column
Data element
Encoding instructions
19-38
39-70
71-80
Card £04
9-11
12-13
14-80
Card EQ5
9-11
12-13
14-15
16-80
Pollutant Control Generic Device
Pollutant Control Design Type
Blank
Activity Number
Test ID Number
Pollutant Control Process
Activity Number
Test ID Number
Line Number
Test Comments
Enter as text the code for the type of
generic pollutant control device. Use the
standard nomenclature provided in Table A-4
of the EADS TRM.
Enter the code for the control device design
type as text. Use Table A-4 in the EADS TRM
for standard nomenclature.
Leave blank.
Same as Card D01.
Same as Card E01.
Enter the code for the specific control de-
vice or treatment process as text. Use the
standard nomenclature provided in Table A-4
of the EADS TRM.
Same as Card D01.
Same as Card E01.
Enter a sequential, integer number for each
line of test comments.
Enter comments as text pertaining specifi-
cally to the activity conducted. Additional
cards may be used as needed.
4.2-12
-------
GROUP F - ANALYSIS LEVEL - FORM 6
Card column
Data element
Encoding instructions
Card F01
9-11
12-13
14-15
16
17-51
52-80
Card F03
9-11
12-13
Activity Number
Test ID Number
Analysis Number
Analysis Designation
Analysis Location
Test Type
Activity Number
Test ID Number
Analysis Number
Test Description
Activity Number
Test ID Number
Same as Card D01.
Same as Card £01.
Enter a sequential, integer number for each
analysis reported.
Enter the letter code which designates the
type of analysis reported. Enter the
letter "B" for biological, "E" for
ecological, or "P" for pollutant.
Enter the name and location of the
laboratory that performed the analysis
as text. Use standard nomenclature in
Table A.5.2.
Enter as text the name of the broad
category of biological or ecological test
type used in the analysis. Use Table
A.5.12a for biological or Table A.5.12b for
ecological standard nomenclature.
Same as Card D01.
Same as Card E01.
Same as Card F01.
Enter the code for the description or the
name of the biological or ecological test
used in the analysis performed. Use
Table A.5.13a for biological or Table A.5.13b
for ecological standard nomenclature.
Same as Card D01.
Same as Card E01.
4.2-13
-------
GROUP F (concluded)
Card column
18-80
Card F04
9-11
12-13
14-15
16-17
18-80
Data element
Encoding instructions
14-15 Analysis Number
16-17 Serial Number
Test Strains/Organisms/Ecosystems
Activity Number
Test ID Number
Analysis Number
Line Number
Analysis Comments
Same as Card F01.
Enter a sequential, integer number to
identify each biological or ecological
test strain, organism, or ecosystem used
in the analysis.
Enter as text the name of the specific test
strain, organism, or ecosystem used in the
analysis reported. Use Table A.5.l4a for
biological or Table A.5.l4b for ecological
standard nomenclature.
Same as Card D01.
Same as Card E01.
Same as Card F01.
Enter a sequential, integer number for each
line of analytical comments reported.
Enter comments as text pertaining specifi-
cally to the analysis reported. Additional
cards may be used as needed.
4.2-14
-------
GROUP G - POLLUTANT LEVEL - FORM 7
Clrd column
Data element
Encoding instructions
Card G01
9-11
12-13
14-15
16-17
18-25
26
27-56
63-65
Activity Number
Test ID Number
Analysis Number
Pollutant Number
Pollutant Media
Pollutant Code Type*
Pollutant Code
57-60 Sampling Technique Code
61-62 Analytical Techniques Code
Sampling Location Code
66-80 Blank
Same as Card D01.
Same as Card E01.
Same as Card F01.
Enter a sequential, integer number for each
pollutant identified.
Enter the name of the media in which samp-
ling or analysis was performed, using the
standard nomenclature given in Table A.5.11.
Enter the pollutant entry code which desig-
nates the type of pollutant ID used. Enter
the letter "C" for CAS number, "M" for MEG
number, "R" for radionuclide, and "T" for a
general text value.
Enter the identification code of the pollu-
tant sampled at the site using standard
nomenclature provided in Table A.5.15.
Enter the appropriate code that describes
the sampling technique using the standard
nomenclature from Table A.5.16.
Enter the two-character code for the analy-
tical method used in determining the pollu-
tant. Use the standard nomenclature in
Table A.5.17.
Enter the three-character code for identify-
ing the sampling location using standard
nomenclature in Table A.5.18.
Leave blank.
Chemical Abstracts Services (CAS) Registration Numbers—Chemical Substance Index, American
Chemical Society. Multimedia Environmental Goals (MEG) for Environmental Assessment, EPA
600/7-77-136a, November 1977.
4.2-15
-------
Specific Encoding Instructions for Project Types 2 and 5
(Sampling and Analysis; Transport, Transformation, and Fate)
GROUP D - ACTIVITY LEVEL - FORM 4
Card column
Data element
Encoding instructions
Card DPI
9-11 Activity Number
12-45 Task Order/T.D. Number
46-51 Activity Start Date
52-55 Duration
56-60 FPEIS TSN
61-65 GEDS TSN
66-70 LEDS TSN
71-75 SDDS TSN
76-80 FEIS TSN
Card DQ2
9-11 Activity Number
Enter a sequential, integer number for each
sampling activity reported.
Enter the task order or technical directive
number as text.
Enter the sampling project start date as a
right-justified integer in the form of
MM-DD-YY.
Enter the length of testing in months as a
decimal number with an implied decimal
point indicated for fractional amounts.
Enter the EADS/FPEIS Test Series Number per-
taining to fine particle sampling informa-
tion which was collected from the same
source.
Enter the EADS/GEDS Test Series Number Per.
taining to gaseous emissions information
which was collected from the same source
Enter the EADS/LEDS Test Series Number per.
taiuing to liquid effluents information
which was collected from the same source
Enter the EADS/SDDS Test Series Number asso-
ciated with solid discharge sample and
analysis from the same source.
(Data elements to be completed at a later
date.)
Same as Card D01.
4.2-16
-------
GROUP D (continued)
Card column
Data element
Encoding instructions
12-46
47-80
Card D03
9-11
12-46
47-80
Card D04
9-11
12-31
32-51
52-80
Card DOS
9-11
Primary Activity
Activity Frequency
Activity Number
Source Name
Activity Location
Activity Number
Source Category
Source Type
Product/Device
Activity Number
Enter the code as text for the primary
activity at the site or, in the case of
studies or model development, the type
of study or model. Use Table A.5.4 for
standard nomenclature.
Enter the code for the frequency of the
sampling activity as text using standard
nomenclature in Table A.5.5.
Same as Card D01.
Enter the name of the source as text.
Enter as text the source location of the
sampling activity reported.
Same as Card D01.
Enter the code for the major grouping of
generic industries or source classes as
from Table A-l in the EADS TRM. Example:
COMBUST-ENERGY.
Enter as text the code for the source type
as found in Table A-l in the TRM. This
identifies the kind of source within the
source category. Example: INDUSTRIAL.
Enter the code for the product or device
type as text from Table A-l in the TRM.
This identifies the general process or
specific product. Example: BOILER.
Same as Card D01.
4.2-17
-------
GROUP D (concluded)
Card column
Data element
Encoding instructions
12-31 Process Type
32-41 feed Material Category
42-51 Feed Material Type
52-80 Blank
Card DQ6
9-11 Activity Number
12-13 Line Number
14-80 Comments
Enter the code for the unique process or
specific type of boiler or engine being
tested as text from Table A-l. Example-
FIRETUBE.
Enter as text the code for the general
categorization of the process feed material
or fuel from Table A-2 in the EADS TRM.
Enter the code for the specific type of
feed material or fuel as text using
Table A.5.6.
Leave blank.
Same as Card D01.
Enter a sequential, integer number for each
line of activity level comments.
Enter any pertinent comments on the sampling
it" ^ Vi a r> -i 4- rt or« + f^ift- Ay-4/^^^^A**,-.! __._J ™
at the site as text. Additional cards
be used as needed.
may
4.2-18
-------
GROUP E - CONTROL SYSTEMS DATA - FORM 5
Card column
Data element
Encoding instructions
14-28
Activity Number
Test ID Number
Project Topic
29-80
Card_E02
Card E03
Card E04
Card E05
9-11
12-13
14-15
16-80
Methods
Not Required
Not Required
Not Required
Activity Number
Test ID Number
Line Number
Test Comments
Same as Card D01.
Enter a sequential, integer number for each
test conducted.
Enter the code as text for the project topic
per site, either SAMPLING or ANALYSIS for
project type 2. For project type 5, enter
TSF for transfer, TSP for transformation,
and F for fate, or any combination of these
three.
Enter as text each sampling/analysis method
or name of equipment used in obtaining a
sample or analyzed results. Use the
standard nomenclature in Table A.5.7.
Same as Card D01.
Same as Card E01.
Enter a sequential, integer number for each
line of test comments.
Enter comments as text pertaining specifi-
cally to the testing activity conducted.
Additional cards may be used as needed.
4.2-19
-------
GROUP F - ANALYSIS LEVEL - FORM 6
Card column
Card F01
9-11
12-13
14-15
Data element
Activity Number
Test ID Number
Analysis Number
Encoding instructions
Same as Card D01.
Same as Card E01.
Enter a sequential, integer number for
—
each
16
17-51
Analysis Designation
Analysis Location
52-80 Test Type
Card F02 - Not Required
Card F03 - Not Required
Card FQ4
9-11
12-13
14-15
16-17
18-80
Activity Number
Test ID Number
Analysis Number
Line Number
Analysis Comments
analysis reported.
Enter the letter code which designates the
type of analysis reported. Enter the
letter "B" for biological, "E" for
ecological, or "P" for pollutant.
Enter the name and location of the
laboratory that performed the analysis
as text. Use standard nomenclature in
Table A.5.2.
Leave blank.
Same as Card D01.
Same as Card E01.
Same as Card F01.
Enter a sequential, integer number for each
line of analytical comments reported.
Enter comments as text pertaining specif-
cally to the analysis reported. Addition~i
cards may be used as needed.
4.2-20
-------
GROUP G - POLLUTANT LEVEL - FORM 7
Card column
Data element
Encoding instructions
18-25
26
27-56
57-60
61-62
63-65
66-80
Activity Number
Test ID Number
Analysis Number
Pollutant Number
Pollutant Media
Pollutant Code Type"
Pollutant Code
Sampling Technique Code
Analytical Techniques Code
Sampling Location Code
Blank
Same as Card D01.
Same as Card E01.
Same as Card F01.
Enter a sequential, integer number for each
pollutant identified.
Enter the name of the media in which samp-
ling or analysis was performed, using the
standard nomenclature given in Table A.5.11.
Enter the pollutant entry code which desig-
nates the type of pollutant ID used. Enter
the letter "C" for CAS number, "M" for MEG
number, "R" for radionuclide, and "T" for a
general text value.
Enter the identification code of the pollu-
tant sampled at the site using standard
nomenclature provided in Table A.5.15.
Enter the appropriate code that describes
the sampling technique using the standard
nomenclature from Table A.5.16.
Enter the two-character code for the analy-
tical method used in determining the pollu-
tant. Use the standard nomenclature in
Table A.5.17.
Enter the three-character code for identify-
ing the sampling location using standard
nomenclature in Table A.5.18.
Leave blank.
Chemical Abstracts Services (CAS) Registration Numbers—Chemical Substance Index, American
Chemical Society. Multimedia Environmental Goals (MEG) for Environmental Assessment, EPA
600/7-77-136a, November 1977.
4.2-21
-------
Specific Encoding Instructions for Project Types 6 and 7
(Health Effects and Ecological Effects)
GROUP D - ACTIVITY LEVEL - FORM 4
Card column
Data element
Encoding instructions
Card DPI
9-11 Activity Number
12-45 Task Order/T.D. Number
46-51 Activity Start Date
52-55 Duration
56-60 FPEIS TSN
61-65 GEDS TSN
66-70 LEDS TSN
71-75 SDDS TSN
76-80 FEIS TSN
Card DQ2 - Not Required
Card D03 - Not Required
Enter a sequential, integer number for each
sampling activity reported.
Enter the task order or technical directive
number as text.
Enter the sampling project start date as a
right-justified integer data in the form of
MM-DD-YY.
Enter the length of testing in months as a
decimal number with an implied decimal
point indicated for fractional amounts.
Enter the EADS/FPEIS Test Series Number per-
taining to fine particle sampling informa-
tion which was collected from the same
source.
Enter the EADS/GEDS Test Series Number per.
taining to gaseous emissions information
which was collected from the same source
Enter the EADS/LEDS Test Series Number per.
taining to liquid effluents information
which was collected from the same source
Enter the EADS/SDDS Test Series Number asso-
ciated with solid discharge sample and
analysis from the same source.
(Data elements to be completed at a later
date.)
4.2-22
-------
GROUP D (continued)
Card column
Data element
Encoding instructions
32-51
52-80
32-41
42-51
52-80
Card D06
9-11
Activity Number
Source Category
Source Type
Product/Device
Activity Number
Process Type
Feed Material Category
Feed Material Type
Blank
Activity Number
Same as Card D01.
Enter the code for the major grouping of
generic industries or source classes as
from Table A-l in the EADS TRM. Example:
COMBUST-ENERGY.
Enter as text the code for the source type
as found in Table A-l in the TRM. This
identifies the kind of source within the
source category. Example: INDUSTRIAL.
Enter the code for the product or device
type as text from Table A-l in the TRM.
This identifies the general process or
specific product. Example: BOILER.
Same as Card D01.
Enter the code for the unique process or
specific type of boiler or engine being
tested as text from Table A-l. Example:
FIRETUBE.
Enter as text the code for the general
categorization of the process feed material
or fuel from Table A-2 in the EADS TRM.
Enter the code for the specific type of
feed material or fuel as text using
Table A.5.6.
Leave blank.
Same as Card DOl.
4.2-23
-------
GROUP D (concluded)
Card column
Data element
Encoding instructions
12-13
14-80
Line Number
Comments
Enter a sequential, integer number for each
line of activity level comments.
Enter any pertinent comments on the sampling
at the site as text. Additional cards may
be used as needed.
4.2-24
-------
GROUP E - CONTROL SYSTEMS DATA - FORM 5
Card column
Card E01
9-11
12-13
14-28
29-80
Card E02 -
Card EQ3 -
Card E04 -
Card_E05
9-11
12-13
14-15
Data element
Activity Number
Test ID Number
Project Topic
Methods
Not Required
Not Required
Not Required
Activity Number
Test ID Number
Line Number
Encoding instructions
Same as Card D01.
Enter a sequential, integer number for each
test conducted.
Leave blank.
Leave blank.
Same as Card D01.
Same as Card £01.
Enter a sequential, integer number for each
16-80
Test Comments
line of test comments.
Enter comments as text pertaining specifi-
cally to the testing activity conducted.
Additional cards may be used as needed.
4.2-25
-------
GROUP F - ANALYSIS LEVEL - FORM 6
Card column
Data element
Encoding instructions
Card F01
9-11
12-13
14-15
16
17-51
52-80
Card FQ2
9-11
12-13
14-15
16-80
Activity Number
Test ID Number
Analysis Number
Analysis Designation
Analysis Location
Test Type
Activity Number
Test ID Number
Analysis Number
Test Description
Card F03
9-11
Activity Number
Same as Card D01.
Same as Card E01.
Enter a sequential, integer number for each
analysis reported.
Enter the letter code which designates the
type of analysis reported. Enter the
letter "B" for biological, "E" for
ecological, or "P" for pollutant.
Enter the name and location of the
laboratory that performed the analysis
as text. Use standard nomenclature in
Table A.5.2.
Enter as text the name of the broad categorv
of biological or ecological test type used
in the analysis. Use Table A.5.12a for bio-
logical or Table A.5.12b for ecological
standard nomenclature.
Same as Card D01.
Same as Card E01.
Same as Card F01.
Enter the code for the description or the
name of the biological or ecological test
used in the analysis performed. Use
Table A.5.13a for biological or Table
A.5.13b for ecological standard nomencla-
ture.
Same as Card D01,
4.2-26
-------
GROUP F (concluded)
Card column
Data element
Encoding instructions
12-13
14-15
16-17
18-80
Card F04
9-11
12-13
14-15
16-17
18-80
Test ID Number
Analysis Number
Serial Number
Test Strains/Organisms/Ecosystems
Activity Number
Test ID Number
Analysis Number
Line Number
Analysis Comments
Same as Card E01.
Same as Card F01.
Enter a sequential, integer number to
identify each biological or ecological
test strain, organism, or ecosystem used
in the analysis.
Enter as text the name of the specific test
strain, organism, or ecosystem used in the
analysis reported. Use Table A.5.l4a for
biological or Table A.5.l4b for ecological
standard nomenclature.
Same as Card D01.
Same as Card E01.
Same as Card F01.
Enter a sequential, integer number for each
line of analytical comments reported.
Enter comments as text pertaining sepcifi-
cally to the analysis reported. Additional
cards may be used as needed.
4.2-27
-------
GROUP G - POLLUTANT LEVEL - FORM 7
Card column
Data element
Encoding instructions
Card G01
9-11
12-13
U-15
16-17
18-25
26
27-56
57-60
61-62
63-65
66-80
Activity Number
Test ID Number
Analysis Number
Pollutant Number
Pollutant Media
Pollutant Code Type*
Pollutant Code
Sampling Technique Code
Analytical Techniques Code
Sampling Location Code
Blank
Same as Card D01.
Same as Card E01.
Same as Card F01.
Enter a sequential, integer number for each
pollutant identified.
Enter the name of the media in which samp-
ling was performed, using the standard
nomenclature given in Table A.5.11.
Enter the pollutant entry code which desig-
nates the type of pollutant ID used. Enter
the letter "C" for CAS number, "M" for M£G
number, "R" for radionuclide, and "T" fOr a
general text value.
Enter the identification code of the
tant sampled at the site using standard
nomenclature provided in Table A.5.15.
Enter the appropriate code that describes
the sampling technique using the standard
nomenclature from Table A.5.16.
Enter the two-character code for the analy-
tical method used in determining the pollu-
tant. Use the standard nomenclature in
Table A.5.17.
Enter the three-character code for iderxtifv-
ing the sampling location using standard
nomenclature in Table A.5.18.
Leave blank.
* Chemical Abstracts Services (CAS) Registration Numbers—Chemical Substance Index, America
Chemical Society. Multimedia Environmental Goals (MEG) for Environmental Assessment, EPA
600/7-77-136a, November 1977.
4.2-28
-------
Specific Encoding Instructions for Project Types 8 and 9
(Integrated Assessment and.Socio-Economic Factors)
GROUP D - ACTIVITY LEVEL - FORM 4
Card column
Data element
Encoding instructions
Card DPI
9-11 Activity Number
12-45 Task Order/T.D. Number
46-51 Activity Start Date
52-55 Duration
56-60 FPEIS TSN
61-65 GEDS TSN
66-70 LEDS TSN
Enter a sequential, integer number for each
sampling activity reported.
Enter the task order or technical directive
number as text.
Enter the sampling project start date as
right-justified integer data in the form of
MM-DD-YY.
Enter the length of testing in months as a
decimal number with an implied decimal
point indicated for fractional amounts.
Enter the EADS/FPEIS Test Series Number per-
taining to fine particle sampling informa-
tion which was collected from the same
source.
Enter the EADS/GEDS Test Series Number per-
taining to gaseous emissions information
which was collected from the same source.
Enter the EADS/LEDS Test Series Number per-
taining to liquid effluents information
which was collected from the same source.
71-75
76-80
SDDS TSN
FEIS TSN
Card D02 - Not Required
Card D03 - Not.Required
Enter the EADS/SDDS Test Series Number asso-
ciated with solid discharge sample and
analysis from the same source.
(Data elements to be completed at a later
date.)
4.2-29
-------
GROUP D (continued)
Card column
Data element
Encoding instructions
Card DQ4
9-11
12-31
32-51
52-80
Card DOS
9-11
12-31
32-41
42-51
52-80
Card D06
9-11
Activity Number
Source Category
Source Type
Product/Device
Activity Number
Process Type
Feed Material Category
Feed Material Type
Blank
Activity Number
Same as Card D01.
Enter the code for the major grouping of
generic industries or source classes as
from Table A-l in the EADS TRM. Example-
COMBUST-ENERGY.
Enter as text the code for the source type
as found in Table A-l in the TRM. This
identifies the kind of source within the
source category. Example: INDUSTRIAL.
Enter the code for the product or device
type as text from Table A-l in the TRM.
This identifies the general process or
specific product. Example: BOILER.
Same as Card D01.
Enter the code for the unique process or
specific type of boiler or engine being
tested as text from Table A-l. Example-
FIRETUBE.
Enter as text the code for the general
categorization of the process feed material
or fuel from Table A-2 in the EADS TRM.
Enter the code for the specific type of
feed material or fuel as text using
Table A.5.6.
Leave blank.
Same as Card D01
4.2-30
-------
GROUP D (concluded)
Card column
Data element
Encoding instructions
12-13
14-80
Line Number
Comments
Enter a sequential, integer number for each
line of activity level comments.
Enter any pertinent comments on the sampling
at the site as text. Additional cards may
be used as needed.
4.2-31
-------
GROUP E - CONTROL SYSTEMS DATA - FORM 5
Card column
Card E01
9-11
12-13
14-28
29-80
Card E02
9-11
12-13
14-36.
Data element
Activity Number
Test ID Number
Project Topic
Methods
Activity Number
Test ID Number
Issues
Encoding instructions
Same as Card D01.
Enter a sequential, integer number for each
test conducted.
Leave blank.
Leave blank.
Same as Card DOl.
Same as Card E01 .
Enter as text the primary issues
considered
37-54
55-80
Approach
Factors
Card E03 - Not Required
Card E04 - Not Required
Card E05
9-11 Activity Number
12-13 Test ID.Number
14-15 Line Number
16-80
Test Comments
in the assessment. Use Table A.5.8 for
standard nomenclature.
Enter as text the general method or approach
used in the assessment. Use Table A.5.9 for
standard nomenclature.
Enter as text the factors analyzed in the
project using Table A.5.10 for standard
nomenclature.
Same as Card DOl.
Same as Card E01.
Enter a sequential, integer number for each
-line of test comments.
Enter comments as text pertaining specifi-
cally to the testing activity conducted.
Additional cards may be used as needed.
4.2-32
-------
GROUP F - ANALYSIS LEVEL - FORM 6
Card column
Data element
Encoding instructions
Card F01
9-11
12-13
14-15
16
17-51
18-80
Activity Number
Test ID Number
Analysis Number
Analysis Designation
Analysis Location
Test Type
Not Required
Not Required
Activity Number
Test ID Number
Analysis Number
Line Number
Analysis Comments
Same as Card D01.
Same as Card E01.
Enter a sequential, integer number for each
analysis reported.
Enter the letter code which designates the
type of analysis reported. Enter the
letter "B" for biological, "E" for
ecological, or "P" for pollutant.
Enter the name and location of the
laboratory that performed the analysis
as text. Use standard nomenclature in
Table A.5.2.
Leave blank.
Same as Card D01.
Same as Card E01.
Same as Card F01.
Enter a sequential, integer number for each
line of analytical comments reported.
Enter comments as text pertaining sepcifi-
cally to the analysis reported. Additional
cards may be used as needed.
4.2-33
-------
GROUP G - POLLUTANT LEVEL - FORM 7
Card column Data element Encoding instructions
Card G01 - Not Required
4.2-34
-------
SECTION 5
DATA SUBMITTAL
5.0 INTRODUCTION
The purpose of this section is to provide users of the PPS with instruc-
tions for submitting new data for entry to the PPS data base and to describe
the quality assurance and quality control activities which will be performed
on all data submitted. Previous sections in this User Guide have discussed
how the project data are to be organized and encoded on the PPS Data Input
Forms. This section will provide the protocol for transferring the data from
the data sheets to a form that can be read by the computer. Once this step
is completed, instructions are given regarding to whom the data should be sent
and what documentation should be provided. Next, the review cycle by the EADS
Technical Support Staff is described. The function of the EDIT program and
LOADER program is discussed, and the output of each program is described and
interpreted.
5.0-1
-------
5.1 DATA INPUT FORM PROCESSING
The PPS data input forms are designed to be entered into the computer
initially as 80-character records either as computer cards or card images that
can be interpreted by the UNIVAC U-1100 computer. It is the responsibility
of the submitter to ensure that the data are keypunched and verified. The
character set to be used should be compatible with the IBM 029 set.
No project profile should be submitted until it has been assigned a unique
Project Profile Number (PPN) by the EADS Program Manager. As described in
Section 4, the PPN must be encoded in colums 1-5 on each card submitted. If
a permanent PPN has not been assigned, then the encoder should write or call
the EADS Program Manager prior to submitting the data.
Cards should be segregated by PPN and should be packaged in boxes (if
they are to be mailed). Data may be submitted on magnetic tape; however, be-
fore attempting to do so, the user should contact the EADS Program Manager
for guidance. The manner in which computer tapes are formatted and read var-
ies widely; thus, each tape submittal must be handled differently. The EADS
Technical Support Staff will coordinate information between the user and the
National Computer Center staff to ensure that the user's tape will be compati-
ble with the UNIVAC U-1100. Magnetic tapes to be mailed should be packaged
properly in specially-designed tape containers for shipment. Such containers
are generally available in most data centers.
When the data input forms have been converted into a machine-readable
format for the computer, the submitter should retain the data forms for ref-
erence until each profile has been loaded into the data base.
5.1-1
-------
5.2 SUBMITTAL PROCEDURES
All data in machine-readable format (usually cards) should be sent to
the EADS Program Manager (or his designee) accompanied by a cover letter that
describes each profile submitted. A sample cover letter is given in Figure
5-1. The complete address is as follows:
Gary L. Johnson
EADS Program Manager
Industrial Environmental Research Laboratory
U.S. Environmental Protection Agency
Mail Drop 63
Research Triangle Park, North Carolina 27711
Once the data have been received, the encoder will be sent a letter acknowl-
edging receipt of the data and notifying him that EDIT processing of the data
has commenced. A sample acknowledgement letter is given in Figure 5-2.
In some cases, EADS users will have the facilities available to directly
submit the profile cards to the National Computer Center. This is allowed;
however, the submittor should contact the EADS Program Manager for technical
guidance prior to doing so.
5.2-1
-------
Gary L. Johnson
EADS Program Manager
Industrial Environmental Research Laboratory
Mail Drop 63
Research Triangle Park, North Carolina 27711
Dear Mr. Johnson:
Enclosed you will find punched cards for Project Profiles 201 through 210
These profiles represent ten environmental contracts currently under way
at this laboratory.
Very truly yours,
John A. Doe, Ph.D.
Ozone National Laboratory
Enclosure
Figure 5-1. Sample data submittal letter.
5.2-2
-------
Dr. John A. Doe
Ozone National Laboratory
1234 Anystreet Drive
Hometown, California 99999
Dear Dr. Doe:
This letter is to acknowledge our receipt of source testing data for PPS PPN
201-210.
In a short time, you will be contacted by the EADS Technical Staff regarding
any corrections to the data that may be required prior to loading the data
into the appropriate media data base.
Thank you very much for your support of the EADS. If you have any questions,
please feel free to call me at (919) 541-2745.
Very truly yours,
Gary L. Johnson
EADS Program Manager (MD-63)
Figure 5-2. Sample data submittal ackowledgement letter.
5.2-3
-------
5.3 REVIEW AND CORRECTIVE ACTION PROCEDURES
The responsibility for determining the validity of the data submitted
lies with the encoder; however, the EADS Technical Staff will assist the, en-
coder by identifying errors that must be corrected before the data can be
loaded into the data base.
Upon receipt of the card deck (or decks) submitted by the encoder, the
EADS Program Manager's office will load the cards into a card-image file on
the UNIVAC U-1100 computer at Research Triangle Park, North Carolina. The
appropriate EADS Technical Staff persons will be notified that a new profile
has been received and the quality assurance (QA) activities may begin for that
profile.
The PPS QA activities are shown schematically in Figure 5-3. The proj-
ect profile received will be processed through the PPS EDIT program which will
produce a profile report format listing of the input data, a list of all errors
detected, and a list of all cards contained in the profile. The EDIT program
is described in detail in Section 5.4. Initially, the EADS Technical Staff
will review the EDIT report and will identify any obvious errors. These errors
will be corrected by the Technical Staff and a new EDIT report will be produced.
It should be noted that by "obvious errors" we are referring to errors such
as encoding, keypunching, or spelling errors, etc. The Technical Staff cannot
and will not attempt to correct any data with respect to accuracy or validity,
or otherwise pass engineering judgment on the submitted data, etc. Any errors
in descriptive data must be identified and corrected by the encoder of the
data.
The corrected EDIT report will be mailed to the encoder for his review.
Any changes to the data should be marked legibly on the printout. Telephone
interaction with the EADS Technical Staff to answer questions or to clarify
data as they are encoded, is encouraged. The marked EDIT report with the cor-
rections should be returned to the Technical Staff promptly. The Technical
Staff will implement the recommended changes and will produce another EDIT
report. If no errors are detected, the EDIT report will be returned to the
encoder for final verification. If the encoder is satisfied that the data
are correct (and valid) as submitted, then he should notify the Technical
Staff that the data are ready to load into the data base. If any errors re-
main after reveiw by the encoder, the changes should again be marked on the
EDIT report and it should be returned to the Technical Staff. This correc-
tive action QA cycle will be repeated until the submittor okays the data for
data base entry. No data will be loaded until encoder approval is obtained.
Once final approval of the data is received from the submittor, the proj-
ect profile is processed through the LOAD program, which actually loads the
sampling activity results into the SYSTEM 2000 data base management struc-
ture described in Section 2. The specific details of the LOAD program are
given in Section 5.4.
5.3-1
-------
Cards
t t
Edit
Program
(Data File
Storage )
7
V
Loader
-------
When the test series has been loaded into the data base, a copy of the
profile report (see Section 7) will be sent to the submitter to acknowledge
the event. At this point, the contents of the project profile are available
to be compared with any other data contained in the data base; that is, only
now will the profile be available for public access.
5.3-3
-------
5.4 EDIT/LOAD PROGRAMS
5.4.1 EDIT Program
The PPS EDIT program provides three functions on the data being submit-
ted for entry to the EADS data base. First, the program processes and lists
all input cards for a project profile, duplicating or filling data fields on
cards as instructed by the Repetitive Data Feature protocol (described in Sec-
tion 4). Second, the EDIT program produces a report that is formatted similarly
to the profile report, which allows visual editing to be done in a format famil-
iar to the user. Third, the program performs values and range checks on input
data fields, such as those fields that require standard nomenclature, and lists
any errors detected. The EDIT program does not replace actual reviewing of
the data by the EADS Technical Staff or, more importantly, by the submitter
of the data.
Each page in the profile report format has the form number given in the
upper right corner that identifies the data input form on which the data were
encoded. It should be noted that in the profile report format most analytical
codes have been translated into the full description and all chemical ID's
have been expanded to report both the MEG ID and the CAS number, the chemical
preferred name and any synonyms, and the chemical formula. The EDIT report
reflects the data as they are encoded, that is, the format follows the pyramid
structure form by form. The PPS user should refer to Section 7 for more details
on the profile report.
Following the listing of the input in the profile (EDIT) format, a sum-
mary of administrative data is presented on the project profile. The submit-
tor is identified as well as the sponsor, contract number, etc. The principal
milestones in the EDIT review cycle are documented.
After the administrative data, all of the input cards are listed and num-
bered sequentially as received. This provides an easy reference to the card
images when errors are found. The EADS Technical Staff will correct any errors
in this card image file using the UNIVAC Text Editor, which allows on-line
changes to be made.
Following the listing of the input data cards, the ERROR file is printed.
The ERROR file contains a list of all of the errors detected by the EDIT pro-
gram. For each input card on which an error is found, the card number and
entire card text are printed, the error number is given, the type of error (F
= fatal or W = warning) is given, the data base component number affected is
shown, and the error message is listed. The complete list of error messages
is given in Appendix A.I. The format for the ERROR file data is shown below:
5.4-1
-------
15 00125A01CCEA 02
No. Type Component Message
001 F C110 Project Sponsor Name Missing
The user may refer to the Glossary of Data Elements in Appendix A.3 for
a complete description of the component number. It should be noted that the
ERROR file will only identify those fields left out or those having standard
nomenclature to which comparisons may be made. As stated previously, the ERROR
file does not replace visual checking of the data by the Technical Staff or
validation of the data by the submitter.
5.4.2 LOAD Program
After the data have been reviewed completely and have been approved for
data base entry, the LOAD program is used to enter the project profile into
the data base. Loading of the data base is accomplished by the EADS Technical
Staff. The LOAD program has no specific output like the EDIT program. Verifi-
cation of data loading is made by the Technical Staff by checking the data
base. Successful completion of the loading process will be acknowledged to
the submitter of the data by his receipt of the profile report print-out.
The operation of the LOAD program is basically simple. The expanded EDIT-
LOAD file is the input file to the LOAD program. The file is segmented into
blocks of data which represent the principal levels of the data base structure
Using the project profile number, activity number, test ID number, analysis
number, and pollutant number as indices, the data are loaded into the SYSTEM
2000 structure through a mechanism called Procedure Language Interface (PLI)
a major feature of SYSTEM 2000 . The reader is referred to the appropriate '
SYSTEM documentation for a complete discussion of the PLI feature.
5.4-2
-------
SECTION 6
DATA RETRIEVAL
6.0 INTRODUCTION
The purpose of this section is to provide users with instructions for
submitting new data for entry to the PPS and for retreiving existing data from
the PPS. In particular, Section 6 discusses direct interactions with the com-
puter and procedures for those users who do not have direct access to the EPA
National Computer Center (NCC) at Research Triangle Park, North Carolina.
It is likely that many users of the PPS will have neither the time nor
the inclination to pursue the direct access methods. Since Federal regula-
tions do not permit the sale of computer services by government data centers
like the NCC, most users will not be authorized to access the NCC unless they
are under EPA contract. For this reason, procedures have been established
which will enable those "off-line" users to retrieve information by written
or telephone request.
It should be noted that there is no charge for "off-line" data retrieval;
however, EPA makes no guarantee regarding the completeness of the data or the
promptness of the response. In all likelihood, simple data requests will be
processed quickly, but the staff response will depend upon their current work-
load and on the complexity of the request. Special data requests which require
computer program development will take longer. Requesters will be appraised
of any expected delays.
6.0-1
-------
6.1 DATA RETRIEVAL USING THE PROGRAM LIBRARY
The simplest method of retrieving data for an off-line user is to re-
quest a program from the Program Library. Section 7 presents the programs
available which may be utilized to retrieve PPS data in a specified manner.
Each program is described separately and has its own requirements for data
input or qualification by the user.
Programs may be requested by off-line users by telephone or in writing.
The requester should supply all information in accordance with the require-
ments of the program and send the completed request to the following address:
EADS Program Manager
Special Studies Staff (MD-63)
Industrial Environmental Research Laboratory
U.S. Environmental Protection Agency
Research Triangle Park, North Carolina 27711
Users should send separate requests for different runs even if the same
program is being used repeatedly. For example, if a user wishes to interro-
gate the data base according to a specific access criteria, any change to that
criteria must be shown in a separate request. Receipt of the request will be
acknowledged to the requester in writing. If there are any errors in the re-
quest or some information is missing, the requester will be contacted to clarify
the problem. When the request has been processed, the output will be sent to
the requester for verification.
6.1-1
-------
6.2 SPECIAL DATA RETRIEVAL REQUESTS
It is recognized at the outset that the Program Library is not likely to
be diverse enough to satisfy all user needs for data. For this reason, a spe-
cial data retrieval request category was established. There is no specific
form to be used for special requests; there is merely a set of general guide-
lines to follow in preparing the request. These guidelines are as follows:
1. Be explicit. Be thoroughly familiar with the PPS data base struc-
ture. Identify each data base element to be sorted and/or retrieved
by name. Should additional work on the request be required, con-
sultation with the requestor will be initiated, and, upon comple-
tion, the printout will be sent to the requestor for verification.
2. Plan the request. Be sure that the access criteria applies to the
proper type of data element. Remember that only key values may be
retrieved directly and that non-key values must be qualified for
data access (see Section 6.3). Specify all needed qualifications
and identify all input data for comparative evaluation.
3. Define the output. Determine how you wish the data to be displayed
on output. Identify how data elements are to be ordered. Specify
column headings. Define any calculations to be performed on the
accessed data.
The completed definition of the request should be sent to the EADS Pro-
gram Manager at IERL-RTP. The user should be sure to include an appropriate
telephone number with the request. If there are any problems encountered with
the request, the user will be contacted by telephone to resolve the problem.
When the request has been received, a letter of acknowledgement will be
sent to the requestor. The letter will include a preliminary estimate of the
length of time required to process the request. As emphasized previously,
the length of time needed to process a special request will depend upon the
complexity of the request.
If no problems are encountered that require consultation with the requestor,
the results will be sent to the requestor when the processing is completed.
The requestor should review the output to verify that it satisfies the request.
If it does not, the printout should be returned with corrections to IERL for
reworking. If the printout is satisfactory, the requestor should notify the
EADS Program Manager of his acceptance.
6.2-1
-------
6.3 KEY/NON-KEY DATA ELEMENTS
®
Data elements in a SYSTEM 2000 data base may be either KEY or NON-KEY.
This designation determines whether a particular data element may be accessed
directly or must be qualified by including additional information. KEY ele-
ments may be selected directly; NON-KEY elements require qualification by a
KEY element. Table 6-1 lists the key data elements, along with their SYSTEM
2000 component numbers. For example, the data element PROJECT SPONSOR is
KEY (as indicated in Table 6-1) and may be used to access the data of interest
directly, such as in the following:
PRINT PROFILE NUMBER WHERE PROJECT SPONSOR EQ US EPA
If, however, the data element is NON-KEY, as in the case of PROJECT
OFFICER, then qualification will be required:
IF PROJECT OFFICER EQ JOE DOE THEN PRINT PROFILE NUMBER
WHERE CONTRACTOR NAME EQ XYZ LABORATORY:
In this case, the KEY element, CONTRACTOR NAME, is used to qualify the request
regarding a NON-KEY data element.
6.3-1
-------
TABLE 6-1. LIST OF KEY DATA ELEMENTS
100* Profile Number 674*
102* Program Name 680*
110* Project Sponsor . 681*
120* Contract/Grant Number 682*
130* Project Start Date 683*
140* Project Finish Date 684*
150* Funding 685*
155* Fiscal Year 686*
180* Sponsor State 691*
190* Sponsor Country 710*
210* Sponsor Branch Code 715*
220* Sponsor Division Code 720*
230* Sponsor Lab Code 730*
260* Date of PPS Entry 740*
265* Agency Inventory Number 750*
268* Project Type Code 760*
280* Contractor Name 770*
310* Contractor State 775*
320* Contractor Country 780*
370* Profile Elements Code 791*
410* Report Sequence Number 801*
450* Sponsor Report Number 802*
460* NTIS Number 805*
470* Report Published Date 810*
480* Issue Date 820*
510* Line Number 835*
610* Activity Number 840*
615* Task Order/TD Number 851*
620* Source Category 905*
630* Source Type 910*
640* Product/Device 920*
650* Process Type 930*
660* Feed Material Category 940*
670* Feed Material Type 950*
672* Activity Start Date 960*
Activity Duration
FPEIS TSN
LEDS TSN
GEDS TSN
SDDS TSN
FEIS TSN
Activity Frequency
Primary Activity
Activity Line Number
Test ID Number
Project Topic
Media
Pollutant Control Generic Device
Pollutant Control Design Type
Pollutant Control Process
Factors
Approach
Issues
Methods
Test Line Number
Analysis Number
Analysis Designator
Analysis Location
Test Type
Test Description
Serial Number
Strains/Organisms/Ecosystems
Analysis Line Number
Pollutant Number
Pollutant Media
Pollutant Code Type
Pollutant Code
Sampling Techniques Code
Analytical Techniques Code
Sampling Location Code
6.3-2
-------
6.4 ON-LINE REQUEST PROCEDURES
The phrase "on-line request" implies that the user intends to establish
direct communication with the PPS data base through some type of terminal-to-
computer link. The procedure described in this section may be used by a quali-
fied user of EPA's NCC to access the PPS directly through an interactive data
communications (demand) terminal or a remote job entry terminal. The specific
qualifications for NCC user access are discussed in Section 6.5.
On-line users of the EADS are presumed to have a working knowledge of
UNIVAC 1100 series computers and, in some cases, of SYSTEM 2000 natural lan-
guage. Special data retrieval procedures (see Section 7) have been developed
to minimize the data processing knowledge required to use the^PPS. Any user
unsure of his familiarity with the UNIVAC 1100 or SYSTEM 2000 is urged to re-
quest information through the off-line procedures described previously in this
section.
On-line users are granted READ-ONLY access to the PPS data base. No up-
dating of data is permitted. New data must be submitted through the EPA proj-
ect officer. In the READ-ONLY mode, the user may retrieve, for sorting and
evaluation, any data stored in the system. The user may take advantage of
the wide array of features offered by SYSTEM 2000 for data sorting and re-
trieval.
6.4-1
-------
6.5 NCC USER QUALIFICATIONS AND SERVICES REGISTRATION
Qualified users are defined as those who have valid accounts with the
NCC at Research Triangle Park, North Carolina. In most cases, NCC users are
either EPA personnel or contractors who are under EPA contract. The NCC is
not available to public subscribers. Federal regulations prohibit the market-
ing of computer time by government data centers which may be in competition
with commercial computer services vendors. Thus, it is not usually possible
for PPS users who are not under EPA contract to obtain account numbers in order
to access the NCC directly. Exceptions to this may be found with user access
through interagency agreements or grants. The qualifications of a potential
NCC user are determined by EPA's Management Information and Data Systems Divi-
sion (MIDSD).
Any questions regarding the qualification of a user should be addressed
to:
MIDSD TSSMS Office
U.S. Environmental Protection Agency
National Computer Center (MD-34B)
Research Triangle Park, North Carolina 27711
or by telephone to 919-541-3629 (FTS: 629-3629).
6.5.1 Registration Procedures
All users of the NCC UNIVAC 1100 must be registered for accounting and
security purposes. Application for NCC services is made by submitting a com-
pleted EPA Form 2800-3 (Figure 6-1) to the appropriate Automated Data Process-
ing (ADP) coordinator for approval and signature. Each EPA office or labora-
tory which uses the NCC or other computing facilities has a designated person
(or persons) who serves as the ADP coordinator. All procedural matters pertain-
ing to the use of the NCC should be directed to the ADP coordinator. The MIDSD
Time Sharing Services Management System (TSSMS) Office is located at the National
Computer Center. Requests for EPA user account modifications processed through
the ADP coordinators to authorize new accounts or add new users to existing
accounts, normally submitted using the EPA Form 2800-3, should then be forwarded
to the following address:
MIDSD TSSMS Office
U.S. Environmental Protection Agency
National Computer Center (MD-34B)
Research Triangle Park, North Carolina 27711
In instances where a user organization requires immediate access to com-
puter facilities, temporary authorization can be achieved by telephone contact
with the TSSMS Office. Requests for temporary authorization should be directed
to 919-541-3629 (FTS: 629-3629). Upon receiving temporary authorization, a
completed Form 2800-3 must be forwarded to the TSSMS Office. The temporary
authorization obtained by telephone is valid for a 2-week period pending receipt
6.5-1
-------
EDP SERV
IPlec
StRVICE (Cneck one) SUPPLIER (SO
Q TIME SHARING
.—.TECHNICAL
'-'ASSISTANCE
D OTHER
'ICES REGISTRATION
ie Prim or Type)
ecily) SOURCE OF FUNDS
Q U.S. EPA
Q REIMBURSIBLE
D SPONSORED
MIDSD USE ONLY
DATE RECEIVED
PROJI n LNVIRONMI N I ivi
COOl bvsl 1 M iut NT if i
CAT ION NUWfU n
PROJECT TITLE (Limit: 60 cnancterl, Including ipicei)
PROJECT DESCRIPTION
ORGANIZATION
PROGRAM ELEMENT TITLE
DOLLAR AMOUNT DATE TO BEGIN
PROGRAM ELEMENT CODE
DURATION SYSTEM DAILY
Q RETRIEVAL ONLY STORAGE
D FI-ILL ACCESS
PROJECT MANAGER JNAME (Lait. Flnt. M.l.) PHONE (Include >ru code]
MAIL CODE (or room) OFFICE OR L
ADDRESS (Street or P.O. Box)
USER |NAM£ Building)
Research Triangle Park, NC 2771]
OCATION
CITY STATE ZIP CODE
OCATION
CITY STATE ZIP CODE
PHONE (Include area Code)
OCATION
CITV STATE ZIP CODE
ORIGINATED BY DATE
CONCURRENCE (Funding) DATE
CONCURRENCE (Otner) DATE
MIDSD USE ONLY
POSTED UPDATEC
EPA Fern 2800-3 (Re.. 4-78)
PROOFED
DISTANCE REFER- LOGON
INITIALS
MAILING LIST CODE
M n s D
P D T Q
c D u n
f D N D
INITIALS
MAILING LIST CODF.
M Q S Q
P D TQ
c Q u Q
f D NO
INITIALS
MAILING LIST CODE
MAILING LIST KEY
M — MANAGEMENT PANEL
P — PROPERTY
C - CONTRACTOR
F - FEDERAL NON- EPA
S - STATE OR LOCAL GOVT
U - UNIVERSITY
N — SYSTEM NEWS
PREVIOUS EDITION IS OBSOLETE tcontmulO on bac*i
Figure 6-1. NCC application.
6.5-2
-------
PLEASE PRINT OR TYPE
(Additional users)
USEH,[NAME (Hit, Firll. M.I.)
MAIL CODE (or room) C
ADDRESS (Streel or P.O. B0»)
USfBJNAME TATE ZIP CODE
•HONE (Include «ru code)
3FFICE OR LOCATION
CITY
STATE ZIP CODE
PHONE (include «rM code)
OFFICE OH LOCATION
CITY
STATE ZIP CODE
PHONE (include eree code)
OFFICE OR LOCATION
CITY
STATE ZIP CODE
PHONE (Include erei cod*)
OFFICE OR LOCATION
CITY
iTATE ZIP CODE
PHONE (Include ere< code)
OFFICE OR LOCATION
CITV
STATE ZIP CODE
PHONE (Include eree code
OFFICE OR LOCATION
CITY
STATE ZIP CODE
PHONE (Include erea code
OFFICE OR LOCATION
ADDRESS (Street or P.O Boxl CITY
STATE ZIP CODE
STANCE '
ODE f
1
aEFER- L
NCE
NITIALS
MAILING LIST CODE
M Q S D
P D TO
C Q U D
F D N D
DISTANCE
ODE
REFER-
ENCE
NITIALS
»OGON
MAILING LIST CODE
M Q s n
p D TQ
c D u n
F n NQ
DISTANCE
ODE
REFER-
ENCE
INITIALS
LOGON
MAILING LIST CODE
MQ s a
p a T n
c n U D
FH ND
DISTANCE
CODE
MAI
P r
DISTANCE
CODE
MAI
M L
c I
DISTANCE
CODE
MAI
M |
P
DISTANCE
CODE
MA
M 1
p 1
DISTANCE
CODE
REFER-
ENCE
INITIALS
LOGON
LING LIST CODE
] s D
3 T D
3 LI n
3 N n
REFER-
ENCE
INITIALS
LOGON
LING LIST CODE
3 s n
D T D
D ^ a
D N n
REFER.
ENCE
INITIALS
LOGON
LING LIST CODE
3 s D
D T a
3 re
REFER.
ENCE
INITIALS
LOGON
LING LIST CODE
D S O
D T D
3 LI D
REFER-
ENCE
INITIALS
LOGON
MAILING LIST CODE
MQ s n
c a ^ a
F D N C
(PA Firm 2100-J (Rev. 6-7t] IR...i»> " ' ' '
Figure 6-1. (concluded)
6.5-3
-------
of the Form 2800-3 for processing permanent authorization. Users must specify
an EPA employee as Project Manager who, in all cases, becomes responsible for
the utilization of the account. Requests for cancellation of specific users
authorized under a given account or changes in user address/telephone numbers
will be processed by telephone using the TSSMS telephone number listed above.
Non-EPA users (e.g., contractors, grantees, etc.) should submit all re-
quired forms to their EPA project officer, who in turn will forward the infor-
mation to the ADP coordinator. Account authorizations/modifications for Inter-
agency Agreement User Accounts (non-EPA users) should be forwarded for approval
to:
W. G. Allen, Computer Specialist
U.S. Environmental Protection Agency
National Computer Center (MD-34)
Research Triangle Park, North Carolina 27711
Upon approval of Interagency requests, the TSSMS Office will complete
implementation of the authori2ation and notify the respective project manager
Any questions concerning the above should be directed to the TSSMS Office at
919-541-3641 (FTS: 620-3641). Please note that, in regard to EPA Form 2800-3
the organization titles and codes and the EPA DIPS organization titles and '
codes, and the program element titles and codes are assigned by the Office of
Planning and Programming. The account number will be assigned to the user bv
MIDSD and must appear on all transactions attempted with the NCC UNIVAC 1100.
6.5.2 User ID and Password
The NCC UNIVAC 1100 has a comprehensive, multi-level security system which
is designed to prohibit unauthorized use of the computer. A feature of this
security system is the TSSMS which requires that all users be identified by a
unique USERID and PASSWORD before access to the computer is granted. The USERTn/
PASSWORD must appear on all demand and batch job requests. This will be dis-
cussed in detail later in Sections 6.6 and 6.7, respectively.
The USERID/PASSWORD is assigned to each individual user of the NCC by
MIDSD. Requests for a USERID/PASSWORD should be submitted to the appropriate
ADP coordinator (through the EPA project officer, if necessary) for approval
and signature.
6.5.4
-------
6.6 INTERACTIVE TERMINAL OPERATION
Demand processing or interactive terminal operation, is defined as a mode
of operation in which processing is dependent on manual interface with the
central processor during processing. Basically, demand processing is a conver-
sational mode of operation requiring a demand and response type of activity.
Conversational operation via a remote terminal causes the Executive System, a
demand processor, or an active program to immediately react and respond. De-
mand processing terminals are generally thought of as being remote from the
computer site and as having a printer or a cathode-ray tube and keyboard. An
example of a demand terminal is the teletype writer keyboard and printer.
The distinction between batch-mode processing and demand processing lies
in the frequent interaction with the user that occurs during demand processing.
The terminal user is considered to be in conversation with the Executive System,
special demand function, user programs, or the batch functions of the Executive
System on a unit basis.
Tasks executed by the demand terminal user normally have frequent but
short bursts of computation. To process a substantial amount of computation
may require a long period of time. Access to computation is a percentage of
the total computing facility and is scheduled in small increments of time at
frequent intervals to provide immediate responses. This action gives the ap-
pearance of total system control to the user and the impression of being the
only user currently running. The more a user is required to interact with a
demand program the shorter the bursts of computation required to service a
given request. The bursts of computation are time-shared within the Executive
System to provide an apparent immediate response, with the program placed in
a dormant mode during idle periods awaiting response from the user.
While a demand program is in a dormant mode, it may be necessary to swap
the program from main storage. Normally, this transfer happens only when main
storage is full and another program currently on mass storage has work to do.
The demand has three distinct modes of operation. They are described
below:
Terminal Inactive Mode—The initial mode of the terminal following
the sign-on procedure. The terminal will return to this mode at
the completion of the other two modes.
Demand Run Mode--This mode is achieved by submitting a @RUN control
statement (see Section 6.6.1) from the primary input device; that
is, the keyboard. The terminal operator must wait until the date
and time message is displayed at the tsrminal before submitting the
run stream data. In demand mode, the input will be solicitated when
input is desired by the Executive System. The terminal is returned
to the inactive mode by submitting 0 @FIN control statement (see
Section 6.6.2).
6.6-1
-------
Batch Mode—The demand terminal may be switched from demand mode to
batch mode for input or output. The "B" sub-option on the @RUN con-
trol statement (@RUN,/B) will place the terminal in batch input mode
Input will not be solicited as in demand run mode. The terminal
will be returned to the terminal inactive mode following a @FIN con-
trol statement. Another @RUN control statement will be accepted
while in the remote batch run whether it contains a "B" option or
not. Output files generated by the batch run, as well as those SYM'd
(via @SYM) to the terminal can be displayed at the terminal by en-
tering the statement, @@SEND. The terminal is returned to the inac-
tive mode when the output process of the file is complete.
Interactive (or demand) processing with the NCC UNIVAC 1100 is supported
for a variety of low-speed data communications terminals. Generally speaking
most 30 character/second (CPS) terminals which have ASCII character sets will'
be able to access the NCC. The NCC does not support any terminals which oper-
ate at 10 CPS or 15.5 CPS. Also, the NCC doe not support IBM 2741 or similar
EBCIDIC code set terminals.
A partial list of terminals supported by the NCC for demand processing
include the following:
Anderson-Jacobson Models 630, 840, 830, and 832
UNIVAC UNISCOPE 100
UNIVAC DCT 500 or equivalent
Texas Instruments Silent 700 series
Hazeltine (most models)
LA36 DECwriter II
If you are uncertain about the compatability of a particular terminal
with the NCC UNIVAC 1100, you should contact the following:
NCC User Services
919-541-3649
FTS: 629-3649
All UNIVAC supported demand terminals use a common interface (device routines
providing the user interface with unit record peripherals) for input and outn
processing. This provides several controls and features to all demand terrain
in a uniform manner. Control of remote symbionts is regulated by control stai-
ments prefixed with a double master space (@@). These control statements do 6
not require the input solicitation. They may be entered after an output
rupt (break-key) or any other time the terminal operator finds the need.
control statements are given in Table 6-2.
6.6-2
-------
TABLE 6-2. REMOTE INTERFACE CONTROL STATEMENTS
Statement
Mode
Description
@@X TIOC
@@SKIP n
@@SEND
@@RQUE
@@CONT
@@CQUE
@@INQ
Demand Run
Demand Run
Demand Run
Demand Run
Demand Run
Terminal
Inactive
Remote Batch
All
Demand Run
All
The @@X statement directs the Executive Sys-
tem to take action on any or all of the four
possible action parameters. The @@X defaults
to {a@X 0.
T--terminate the demand run's present execu-
tion.
I—discard all backed-up input.
0--discard all backed-up output.
C--generate a "BRK" contingency.
Skip n lines of output where n is a value of
0 to 63. The SKIP may be reset by a @@SKIP 0.
The @@SKIP n defaults to @@SKIP 0.
Send a queued batch output file to the
terminal.
Stop the present batch output file and re-
queue it for a later @@SEND request. Return
to terminal inactive mode.
Directs the symbiont to continue. Useful
after a BRK-KEY when no action is desired.
Circumvent input solicitation requirement.
Allow several input images to be buffered in
memory before the terminal is placed in the
wait condition.
Directs the Executive System to buffer all in-
put to mass storage until the @@END control
statement is received. If the @@INQ state-
ment is entered in terminal inactive mode,
the next input should be a @RUN statement.
All @RUN statements entered while in @@INQ
mode will be considered remote batch and not
demand.
6.6-3
-------
TABLE 6-2. Concluded
Statement
Mode
Description
@@END
@@ESC
All
Demand Run
@@TERM
All
@@TTY W, n All
Terminates special input mode, i.e., @@CQUE
or @@INQ. The @@END returns the terminal to
demand run from @@CQUE and will process the
mass storage buffered input of @@INQ.
Allows the input to be passed to the re-
quester unaltered from the format of which it
was entered; that is, all communication
envelope characters are not removed nor is
the image translated.
Directs the Executive System to terminate the
terminal. It is recommended that the remote
Operator enter @@TERM only while in the termi-
nal inactive mode. However, if entered while
a run is active, the run and terminal will be
terminated. @@TERM is equivalent to sign off,
Changes the maximum character width of page
from the default 80 characters to n charac-
ters wide. In most cases, the maximum page
width should be set to 132.
6.6-4
-------
For more details on demand processing, the user should refer to the
National Computer Center User Reference Manual. This manual may be obtained
from NCC User Services at the telephone numbers listed above. The remainder
of this section will address demand processing as it applies to the EADS.
6.6.1 Initiating a Demand Processing Session
Communications are established with the NCC UNIVAC 1100 through data com-
munication modems or couplers over voice-grade telephone lines. Users should
follow the steps given in the equipment user manual for their terminal in order
to establish the data link to the computer. A list of nationwide telephone
access numbers for the NCC is given in Table 6-3. Once the data link is estab-
lished, the following sequence of commands should be entered (for clarity,
the information printed by the computer is shown in capital letters; the input
required from the user in small letters).
Note that the pound sign (#) denotes a carriage return:
Command
#nccdemd#
Description
This identifies the NCC to the com-
munications network.
READY TO NCC ON 9E
ENTER USERID/PASSWORD
>xxx/xxxxxx#
*DESTROY USERID/PASSWORD
ENTRY
*UNIVAC 1100 OPERATING SYSTEM
LEV. 36R2B-80-18A
>@@tty w, nn#
-@@ COMPLETE
Response indicates that communication
is established on Port 9E.
Enter the approved USERID and PASSWORD
following the input solicitation
symbols (>).
This header mesage is usually fol-
lowed by several lines of text in-
dicating special news which can be
obtained. When the solicitation sym-
bol (>) is received you are ready to
enter a valid @RUN card.
Where nnn = the maximum width of the
page in characters (usually 132).
This command may be omitted if terminal
is limited to 80 characters.
Indicates that the @@TTY command has
been executed.
6.6-5
-------
TABLE 6-3. NCC DEMAND ACCESS TELEPHONE NUMBERS
State
City
Telephone
Alabama
California
Colorado
Connecticut
District of Columbia
Georgia
Illinois
Louisiana
Massachusetts
Michigan
Minnesota
Missouri
Nevada
New York
North Carolina
Ohio
Pennsylvania
South Carolina
Tennessee
Texas
Washington
All other locations
(toll free)
Montgomery
San Francisco
Denver
Wethersfield
Washington
Athens
Athens
Chicago
New Orleans
Boston
Grosse lie
Lansing
Minneapolis
Kansas City
Las Vegas
New York
Raleigh/Durham
Cincinnati
Philadelphia
Columbia
Nashville
Dallas
Seattle
205/277-9390
415/546-1395
303/837-0843
203/529-3378
202/966-9510
404/549-3882
404/873-6431
312/663-1640
504/566-0041
617/742-0420
313/675-8936
517/485-3220
612/861-7451
816/474-3540
702/736-1988
212/233-1604
919/541-2000
513/751-5800
215/925-4407
803/256-1018
615/244-8020
214/651-1723
206/682-6456
800/424-3690
6.6-6
-------
>@run nnxxx,account
number, eads,15//
DATE:
>
011580 TIME: 135248
Where nnxxx = the RUNID. Usually this
begins with a number that designates
an output receiving bin at the NCC
User Reference Manual or call User
Services for more information.
Account No. = the NCC account number
as given.
eads = the project code which enables
access to the PPS data base and soft-
ware. No other project code may be
used.
This is the system response if a
valid @RUN card has been entered,
followed by the >. NOTE: If your
terminal can print more than 80
characters across the page, you may
wish to expand the page width as
shown above.
At this point, the computer is ready to receive instruction for access-
ing the data base or for executing PPS retrieval or analytical software. For
users who are knowledgeable in SYSTEM 2000 natural language, Section 6.6.3
describes the acessing procedure.
6.6.2 Terminating a Demand Processing Session
Two commands are required to end a demand processing session—the @FIN
and the @@TERM. The @FIN command ends the run and results in the printing of
summary usage and accounting data, and places the terminal in the inactive
mode. The @@TERM command ends the session by disconnecting the terminal from
the computer. A typical sequence is as follows (# denotes carriage return):
>@fin#
XXXXX
(Enter the @FIN command)
PROJECT: EADS
TIME:
SRUS: 00:01:41.027
IMAGES READ: 78
START: 13:52:47
^TERMINAL INACTIVE*
>@@term#
ACCT: XXXXXXXXXX
TOTAL: 00:00:35.510
CPU: 00:00:00.177
CC/ER: 00:00:26.509
COST: $005.05
PAGES: 3
JAN 15, 1980 FIN: 13:57:50 JAN 15, 1980
CBSUPS:
I/O:
WAIT:
001854139
00:00:08.822
00:02:36.079
(Enter the @@TERM command)
6.6-7
-------
6.6.3 Accessing the PPS
Read-only access to the data base is granted to users of the PPS who use
this procedure. Users are cautioned not to attempt to use this procedure unless
they are familiar with SYSTEM 2000 natural language. The sequence is as fol-
lows (//denotes carriage return):
>@add PPS.start// (Enter the @ADD command.)
01/15/80 17:09:07 BEGIN SYSTEM 2000 VERSION 2.SOD
-556- ASSIGNED...EADS-PPS 12 28443 01/15/80 11:44:14
At this point, the system is ready to accept valid SYSTEM 2000 commands.
The session may be ended by using the EXIT: command, which produces the trailer
banner and returns to control mode with the input solicitation character (>)
given.
> exit://
01/15/80 17:14:52 END SYSTEM 2000 VERSION 2.SOD
>
The demand processing session may be terminated by using the. procedure
given in Section 6.6.2.
Any attempts to change or modify the data base in any way will result in
the following diagnostic message:
-846- COMMAND NOT AVAILABLE IN SHARED MODE-
6.6-8
-------
6.7 REMOTE BATCH TERMINAL OPERATION
Batch processing, whether remote or local submittal, implies that dis-
crete jobs are submitted to the NCC UNIVAC 1100 from cards or some similar
form. If local, card decks are submitted to the I/O Control Clerk and then
loaded into the computer; if remote, cards are read into the computer through
a high-speed remote job entry (RJE) terminal which has been connected to the
computer via telephone data link.
Remote batch terminal operation with the NCC UNIVAC 1100 is currently
supported under the UNIVAC 1004 and NTR (9000 Remote) terminal protocols.
This means that a variety of commercial RJE terminals which are capable of
emulating (or looking like) a U-1004 or NTR terminal may be used to access
the NCC UNIVAC 1100. A partial list of RJE terminals which satisfy one or
more of these conditions includes the following:
DATA 100 Models 74, 76, and 78
COPE RJE Terminals
Harris RJE Terminals
UNIVAC 1004
UNIVAC 9200 NTR
If you are uncertain regarding the compatibility of a particular termi-
nal with the NCC UNIVAC 1100, you should contact the following:
NCC User Services
919-541-3649
FTS: 629-3649
All RJE terminals are identified to the NCC UNIVAC 1100 by a unique SITE
ID which is assigned by the MIDSD TSSMS Office at Research Triangle Park,
North Carolina. Figure 6-2 gives an example of the form required for batch
terminal support. The completed form is submitted to the appropriate ADP co-
ordinator (through the EPA project officer if required) for approval and sig-
nature .
The batch SITE ID is of the form DATAXX and must be transmitted to the
NCC UNIVAC 1100 at sign-on before any processing can be initiated.
£.7.1 Initiating a Remote Batch Processing Session
Communications are established with the NCC UNIVAC 1100 through data com-
munication modems over voice-grade telephone lines. The NCC UNIVAC 1100 will
support RJE processing only at 4800 bits/second (EPS) transmission rate. A
list of nationwide RJE telephone access numbers for the NCC is given in Table
6-4-
Batch processing through an RJE terminal essentially means that the terminal-
to-computer data link must be established and the computer card deck must be
read into the computer in a prescribed manner. Since this procedure varies
6.7-1
-------
Organization:
Terminal manufacturer and model number:
If programmable, what UNTVAC terminal does the terminal emulate?
Hours of operation: From
Person responsible:
Name
Title
To
EOT
Mailing Address
Telephone: FTS
Commercial
Comments
Ext.
Ext.
ADP Coordinator
Date
THE FOLLOWING TO BE COMPLETED BY NCC
SITE-ID
Telephone numbers to use:
FTS
Commercial
Contacts:
User Services
FTS 629-3649
919/541-3649
Comments:
Central Computer Operations:
Day:
Night! ~~~
Mailing Address:
National Computer Center
U.S. EPA
Research Triangle Park
North Carolina 27711
Hours available for operation:
Weekdays: to
Saturday: to
Sunday: to _ £DT
Holidays: to grjf
Figure 6-2. Request for batch terminal support form.
6.7-2
-------
TABLE 6-4. NCC REMOTE BATCH ACCESS TELEPHONE NUMBERS
Location
Transmission rate (BPS)
Telephone
Continental U.S.
(toll outside RTF)
Continental U.S. (except NC)
(toll free)
4800
4800
919/541-2094
(3 lines)
800/334-9761
(8 lines)
NOTE: 4800 BPS transmission requires Bell 208B dataset or equivalent.
6.7-3
-------
dramatically among terminal vendors, the user should refer to his terminal
hardware operating manual for the appropriate procedure. If any problems or
questions arise, the user should contact NCC User Services.
6.7.2 Terminating a Remote Batch Processing Session
The termination of a remote batch processing session depends upon which
UNIVAC RJE terminal is being used (or emulated). The user should consult his
terminal hardware operations manual for the correction procedure.
6.7-4
-------
6.8 PPS USER SUPPORT
IERL/RTP is committed to the on-going support of the PPS and its asso-
ciated software. The administrative functions relative to the PPS are pro-
vided by the Special Studies Staff in IERL. Technical development and main-
tenance is provided by the EADS Technical Support Staff, which is composed of
government contractors under the direction of the EADS Program Manager. The
EADS Technical Support Staff has the responsibility for conducting the data
QA program, updating documentation, developing analytical software specifica-
tion, conducting information transfer activities, etc. This function is being
provided by Acurex Corporation in Mountain View, California, and Midwest Research
Institute, Kansas City, Missouri. Data processing activities are also performed
by Acurex Corporation in its offices located at Research Triangle Park,
North Carolina.
Any questions regarding the EADS should be directed to the EADS Program
Manager or the EADS Technical Support Staff. Their names, addresses, and phone
numbers are listed on page v.
Problems relating to the operation of the NCC UNIVAC 1100, to data com-
munications, etc., are not the responsibility of the EADS Technical Support
Staff. These questions should be addressed to:
User Services
National Computer Center (MD-34B)
U.S. Environmental Protection Agency
Research Triangle Park, North Carolina 27711
FTS: 629-3649
Commercial: 919-541-3649
6.8-1
-------
SECTION 7
PROGRAM LIBRARY
7.0 INTRODUCTION
The usefulness and usability of project description data which have been
compiled into a computerized information system are limited if the data cannot
be retrieved and utilized to answer questions that a^user might have. As dis-
cussed previously, the employment of the SYSTEM 2000 data base management
system provides a flexible set of commands that can often answer many ques-
tions. SYSTEM 2000 Natural Language, as this command language is called, is
a powerful tool for the knowledgeable user; that is, the user who is familiar
with or has received training in the use of SYSTEM 2000 . The Natural Lan-
guage commands are limited, however, especially when there is a need to per-
form calculations using the data or when a special formatted report is required.
In addition, most PPS users are not likely to undertake training in the use
of SYSTEM 2000 Natural Language, nor should these users be expected to have
any particular expertise in the use of computers or computer programs. This
means that no user of the PPS should be required to have any special computer-
related training in order to use the PPS data base.
In order to provide greater flexibility to the user and to simplify the
retrieval of data, an extensive program library is being developed for the
PPS. The programs described in the following subsections are applicable to
one or more of the waste stream data bases contained in the PPS.
Each entry in the program library is described by a brief abstract which
identifies in general terms the input required from the user and the output
to be expected. Some programs will be applicable to both demand (interactive)
processing and batch processing, and step-by-step instructions for executing
the program in both modes are given when appropriate. For demand processing,
it is assumed that the user has successfully established communications with
the UNIVAC U-1100 computer as described in Section 6 of this user guide. In
like manner, batch users are assumed to have established communications with
the UNIVAC U-1100 through a remote terminal device or have the capability of
submitting run requests locally at the EPA National Computer Center at Research
Triangle Park, North Carolina. All input requirements for each program are
listed and a sample (or representative) output is provided. Any comments per-
taining to the use of the program which may be helpful to the user are also
given.
As new user programs are developed and made available to the PPS user
community, this section will be expanded.
7.0-1
-------
7.1 PROFILE REPORT
7.1.1 Abstract
The PROFILE Report is the basic report for the EADS Project Profile Sys-
tem (PPS). This report lists all of the data contained in the profile by ac-
tivity, test ID, analysis, and pollutant. The length of the PROFILE Report
will depend upon the quantity of data contained in the project profile.
The format of the PROFILE Report follows the structure of the PPS data
base. The first page of the report describes the administrative aspects of
the project. This includes identification of the sponsor organization and
project officer, contractor organization and project manager, project title,
and funding history. The first page also contains the profile elements which
have been found to be applicable to this project. The second page in the
PROFILE Report lists the references or publications produced by or pertaining
to this project, including the author(s), publication number, etc. Page three
contains the project abstract, a narrative description of the project, its
objectives, and its accomplishments.
The fourth page introduces the activity level data. Succeeding pages
will list the data for the test level, analysis level, and pollutant level in
order. The data actually printed on each page will depend upon the project
type. At the pollutant level, the use of the MEG ID or CAS Number for chemi-
cal compounds will result in complete compound identification in the PROFILE
Report with the preferred name, synonyms, empirical formula, and molecular
weight being printed. Also, the analysis method code will be translated into
the descriptive text on output.
The PROFILE Report may be run by inputting the PPN and the Project Type
Number. The Report may be initiated only through a "demand" terminal session
even though the PROFILE program is only executed as a batch job. The demand
session gives complete instructions for using the PROFILE Report program.
7.1-2 User Data Required
• Valid Project Type Code
• Valid Project Profile Number (or range of Project Profile Numbers)
7.1.3 Data Qualification Required
None.
7,1.4 Limitations/Restrictions
The PROFILE Report program user has several printing options available,
including the NCC local printers, remote high-speed terminal printers, and
low-speed time-sharing (demand) terminals. Because of the length of the
PROFILE Report for most of the project profiles, it is recommended that the
low-speed terminal option be avoided where possible.
7.1-1
-------
7.1.5 Functional Description
Using the PPS project type code and the Project Profile Number (PPN) ,
the selected profile is retrieved and printed in its entirety. Multiple
PROFILE Reports may be initiated during one session.
7.1.6 User Instructions—Demand File Name: E ADS. PPS-PROFILE
The PROFILE Report program may be accessed through a "demand," or time-
sharing, terminal (see Section 6.6), which can access the U-1100 computer.
User access through the demand terminal allows the program to be executed as
a batch job. The user should initiate the demand session by following the
procedures outlined in Section 6.6.1. When the session is completed, the de-
mand session may be ended by following the instructions given in Section 6.6.2
(In the following computer-generated instructions, the response by the
user is underlined.)
>@ADD EADS.PPS-PROFILE (Enter the file name)
CTS 6R1 16:21:01
THE ASSUMED MODE IS FIELDATA
DO YOU NEED INSTRUCTIONS?> YES (Enter YES or NO)
THIS MODULE IS DESIGNED TO RUN THE PROFILE REPORT FOR ANY VALID PROFILE
NUMBER AND PROJECT TYPE ENTERED. INFORMATION REQUIRED TO RUN THIS ROUTINE
WILL BE ENTERED BY THE USER AS PROMPTED BY THIS MODULE.
(If the answer to the preceding question had been NO, the above state-
ments would be skipped.)
ENTER YOUR ACCOUNT NUMBER:> (Enter a valid NCC Account Number)
ENTER THE PROJECT TYPE NUMBER:> (Enter the Project Type as an integer number
If no specific type is desired, press return")
IS THE PROFILE NUMBER IN A RANGE (YES OR N0)?> YES
YOUR REQUEST IS A CONTINUOUS RANGE
ENTER THE FIRST PROFILE NUMBER:> (Enter the first PPN)
ENTER THE LAST PROFILE NUMBER:> (Enter the last PPN)
(If the response to the range question is NO, the above statements are
skipped. The computer will prompt the user with the following question.)
7.1-2
-------
ENTER THE PROFILE NUMBER:> (Eater the PPN)
ENTER THE NUMBER OF COPIES (Enter the number of copies wanted)
IF 1, JUST PRESS RETURN:>
DO YOU REQUEST SPECIAL FORMS?> NO (Enter YES or NO)
(If YES had been entered, the program would request the forms ID.
Please consult the NCC User Reference Manual or the EADS Program Manager
before attempting to use this feature. The NO response means that standard,
one-part computer paper will be used.)
ENTER THE PRINT DESTINATION IF IT IS
TO BE OTHER THAN THE MAIN PRINTER:>
(If there is no preference, press the return key. If the output is to
be a remote, high-speed terminal, enter the site ID of the terminal. If a
user demand terminal is to receive the output, enter the user ID for that
terminal user.)
ARE YOU FINISHED (YES OR N0)?> (Enter YES or NO)
(If additional selections are to be made, enter NO and the program will
prompt for the project type code selection. If YES, there will be a normal
exit.)
Please refer to Section 7.1.8 for sample runs of the demand PROFILE Report
program. An example of the PROFILE Report is given in Section 7.1.9.
7.1.7 User Instructions—Batch
Batch (card input) processing of the PROFILE Report program is not avail-
able.
7.1.8 Sample Demand Runs
(To be added later.)
7.1.9 Sample PROFILE Report
(To be added later.)
7.1-3
-------
7.2 CHEMICAL SEARCH PROGRAM (CHEM-SEARCH)
7.2.1 Abstract
The Chemical Search Program (CHEM-SEARCH) enables the user to search all
or part of the PPS data base to determine the presence of a particular chemi-
cal species. The user may identify the chemical species by its Chemical Ab-
stracts Services (CAS) Number, its Multimedia Environmental Goals (MEG) Num-
ber, or its empirical formula. If a search is to be made of part of the data
base, the range of PPNs must be specified. Both demand and batch versions of
the program are available to the user. The demand version provides complete
instructions on the use of the program through an interactive interface with
the user. A "Help" command is also available to users who encounter problems.
The output from the CHEM-SEARCH program provides additional information
on the chemical species selected, including the MEG ID Number, CAS Number,
empirical formula, preferred name, molecular weight, other names by which the
chemical is known, and whether or not the chemical is designated as a priority
pollutant, hazardous pollutant, or both. The Profile Number and Project Type
are listed for those priorities in which the chemical of interest is reported.
the selection criteria requires only that the chemical species be found once
in a given profile even though multiple occurrences of the chemical may be
present. It is recommended that the user request the PROFILE Report for each
identified in order to get more information.
7.2.2 User Data Required
• Valid Chemical ID Code (MEG ID or CAS Number) or Empirical Formula
• Range of PPNs (optional)
7.2.3 Data Qualification Required
None.
7.2.4 Limitations/Restrictions
The user is cautioned to use care when selecting the empirical formula
format option for organic compounds. Since several organic compounds of the
same class may have the same formula (e.g., isomers), it would likely be safer
to search on the basis of the MEG ID or the CAS Number.
7.2.5 Functional Description
Using the user-supplied data on a particular chemical species, the CHEM-
SEARCH program initially checks the EADS Chemical Data Table (CDT) to verify
that a valid species has been requested. If so, both the MEG ID and CAS Num-
ber are retrieved. The program next scans all of the data bases specified
using both the MEG ID and the CAS Number to search for the chemical. If at
least one occurrence of the species is found within a project profile, that
profile and the project type are listed in the output. If no data are found
in the entire data base, this fact is also listed in the output.
7.2-1
-------
7.2.6 User Instructions—Demand File Name: EADS.PPS/CHEM-SEARCH
The CHEM-SEARCH program may be accessed through a "demand," or time-sharine
terminal (see Section 6.6), which can access the U-1100 computer. User access
in demand mode enables the program to be run in "real time"; that is, the results
are returned directly to the user.
The user shall initiate a demand session by following the procedures out-
lined in Section 6.6.1. When the session is completed, the session may be
ended by following the procedures given in Section 6.6.2.
(In the following computer-generated instructions, the response by the
user is underlined.)
>@ADD EADS.PPS/CHEM-SEARCH (Enter the file name)
DO YOU NEED INSTRUCTIONS? (Enter YES or NO)
>YES
INSTRUCTIONS WILL BE LISTED SEVERAL LINES AT A TIME AND THEN STOP. TO CON-
TINUE DEPRESS CARRIAGE RETURN.
THIS PROGRAM WILL LIST PROFILE NUMBERS FROM THE PPS DATA BASE WHICH HAVE USER
SPECIFIED CHEMICALS REPORTED. THE USER MUST IDENTIFY THIS CHEMICAL TO THE
PROGRAM BY USING MEG, CAS ID NUMBERS OR EMPIRICAL FORMULA.
>(CR)
THE FORMAT USED IS:
M/MMMMMM - FOR THE MEG NUMBER — OR --
C/CCCCC-CC-C - FOR THE CAS NUMBER — OR --
F/XXXXXXX... - FOR THE EMPIRICAL FORMULA.
>(CR)
THE USER MAY LIMIT THE PROFILE LIST TO SPECIFIC RANGES. "STOP" AND "HELP"
MAY BE ENTERED AT ANY TIME. "STOP" WILL EXIT THE PROGRAM. "HELP" WILL
BRIEFLY LIST THE MAJOR QUERY RESPONSE FORMATS. (IMPORTANT -- ANY QUERY
LISTED PRIOR TO A "HELP" REQUEST WILL NOT BE SHOWN AGAIN AFTER THE "HELP"
PROGRAM.)
>(CR)
(If the reply to the above question is NO, the preceding statements are
skipped.)
7.2-2
-------
ENTER THE CODE/CHEMICAL ID (FORMULA) (Use the format described above)
>C/00067-66-3
DO YOU WISH TO SELECT WITHIN A (Enter YES or NO)
RANGE OF PPS PROFILES
>YES
ENTER THE MINIMUM NUMBER IN THE RANGE (Enter the PPN)
xn
ENTER THE MAXIMUM NUMBER IN THE RANGE
XH)
(If a range is not requested by the user, the last two queries are
skipped, and the entire data base is scanned.)
ENTER "END" OR CARRIAGE RETURN IF COMPLETE:
>END
(If a correction or addition is required, enter "YES" and the program
will again ask if a range is requested and the ensuing steps are repeated.
If END is entered, the program starts to execute. Typical output is as
follows.)
CHLOROFORM (TRICHLOROMETHANE)
MEG- 02A100 CAS: 00067-66-3 FORMULA: CHCL3
MOLECULAR WEIGHT: 119.38 PRIORITY POLLUTANT
HAZARDOUS POLLUTANT
OTHER NAMES: METHANE TRICHLORIDE
TRICHLOROMETHANE
PPS PROFILE PROJECT TYPE
00001 01
00002 01
00003 05
00004 02
00005 05
00006 06
00007 03
00008 01
00009 01
00010 02
*** NORMAL END ***
7.2-3
-------
At this point, the terminal is returned to the Control Mode; that is, the pro-
gram has finished and the user may now enter additional commands.
The CHEM-SEARCH program is very flexible and has a number of options avail-
able to users. This flexibility is best seen through the sample demand runs
given in Section 7.2.8. Use of the "HELP" option is also shown there.
7.2.9 User Instructions--Batch
The CHEM-SEARCH program may also be executed as a batch job on the UNIVAC
U-1100 using punched card input. It is assumed that the user has card input
access to the U-1100 computer either through "across the counter" submitted
at Research Triangle Park, North Carolina, or through a remote batch terminal
In order to run the CHEM-SEARCH program in batch mode, the user should
submit the following cards:
@RUN,R/RS Run ID,Account Number,EADS,5,50/50
@ASG,A EADS.
@XQT,BHZ EADS.PPS-CHEMSRCH
. . . parameter cards . . •
@FIN
There are three types of parameter cards defined for CHEM-SEARCH, and
they are used to drive the program. The Type 1 Parameter Card identifies the
chemical to be requested in terms of its MEG ID Number, CAS Number, or empiri-
cal formula. The Type 2 Parameter Card identifies the data base to be select
(PPS) and specifies the range of PPNs to be searched. The Type 3 Parameter
Card is the END card which indicates to the program that the input data have
been completed.
The formats for the parameter cards are as follows:
Card Col. 12345678
Type 1: M/AAAAAA
or C/BBBBB-BB-B
or F/DDDDD...
where all data begin in column 1 of the card and:
M identifies the MEG Number AAAAAA;
C identifies the CAS Number BBBBB-BB-B; and
F identifies the Empirical Formula DDDD...
1 2
7.2-4
-------
Type 2: Card Col. 12345678901234567890
PPS MINXX-MAXZZ
where PPS is entered in columns 1-3
Leave columns 4-6 blank
MINXX is the starting PPN in the range of PPNs to be
specified. The PPN should be entered as a right-
justified integer number in card columns 7-11,
(enter a dash in card column 12)
MAXZZ is the last PPN in the range of PPNs to be specified.
The PPN should be entered as a right-justified integer
number in card columns 13-17.
*NOTE* If no range of PPNs is requested (that is, if the entire data base
is to be searched), leave card columns 7-17 blank.
Also, if one end of the PPN range is entered, the other is required also.
A Type 2 parameter card must be included for each data base requested. The or-
der of the Type 2 cards is not important.
Xype3: Card Col. 123
END
This card signifies the end of the data. It should be the last parameter
card included in the card deck.
*Caution* The parameter cards must be entered into the card deck in the
following order:
Type 1
All Type 2
Type 3
Sample print-outs from CHEM-SEARCH are included in Section 7.2.9.
7.2.8 Sample Demand Runs
(1) MEG ID Number Format:
>@ADD EADS.PPS/CHEM-SEARCH
DO YOU NEED INSTRUCTIONS?
>NO
ENTER THE CODE/CHEMICAL ID (FORMULA)
>M/02A065
7.2-5
-------
CHEMICAL DATA NOT FOUND FOR: M/02A065
WOULD YOU LIKE TO TRY AGAIN?
>YES
>M/02A10Q
DO YOU WISH TO SELECT WITHIN A RANGE OF PPS PROFILES?
>NO
ENTER "END" OR CARRIAGE RETURN IF COMPLETE:
>END
CHLOROFORM (TRICHLOROMETHANE)
MEG: 02A100 CAS: 00067-66-3 FORMULA: CHCL3
MOLECULAR WEIGHT: 119.38 PRIORITY POLLUTANT
HAZARDOUS POLLUTANT
OTHER NAMES: METHANE TRICHLORIDE
TRICHLOROMETHANE
PPS PROFILE PROJECT TYPE
00001 01
00002 01
00003 01
00004 05
00005 05
00006 04
00007 05
00008 05
00009 06
00010 04
00011 04
00143 01
00144 01
00145 01
00147 02
00148 04
00150 07
00151 09
00152 03
00153 02
*** NORMAL END ***
(2) Chemical Formula Format:
Caution: Be careful using this format for organic chemicals
where isomers may be encountered.
7.2-6
-------
XgADD EADS.PPS/CHEM- SEARCH
DO YOU NEED INSTRUCTIONS?
>NO
ENTER THE CODE/CHEMICAL ID (FORMULA)
>F/CHCL3
DO YOU WISH TO SELECT WITHIN A RANGE OF PPS PROFILES?
>YES
ENTER THE MINIMUM NUMBER IN THE RANGE
ENTER THE MAXIMUM NUMBER IN THE RANGE
>5
ENTER "END" OR CARRIAGE RETURN IF COMPLETE:
>END
CHLOROFORM (TRICHLOROMETHANE)
MEG: 02A100 CAS: 00067-66-3
MOLECULAR WEIGHT: 119.38
FORMULA: CHCL3
PRIORITY POLLUTANT
HAZARDOUS POLLUTANT
OTHER NAMES:
PPS PROFILE
METHANE TRICHLORIDE
TRICHLOROMETHANE
PROJECT TYPE
00001
00002
00003
00004
00005
05
05
06
06
06
*** NORMAL END ***
>
(3) Use of HELP Command:
>@ADD EADS.PPS/CHEM-SEARCH
DO YOU NEED INSTRUCTIONS?
>NO
ENTER THE CODE/CHEMICAL ID (FORMULA)
>HELP
"STOP" WILL EXIT PROGRAM
"M/MMM..,C/CCCCC-CC-C,F/XXXXX...
WILL SEARCH BY CHEMICAL
>F/C2CL4
7.2-7
-------
DO YOU WISH TO SELECT WITHIN A RANGE OF PPS PROFILES?
>YES
ENTER THE MINIMUM NUMBER IN THE RANGE
M
ENTER THE MAXIMUM NUMBER IN THE RANGE
>5
ENTER "END" OR CARRIAGE RETURN IF COMPLETE:
>END
TETRACHLOROETHENE
MEG: 02B080 CAS: 00127-18-4
MOLECULAR WEIGHT: 165.83
OTHER NAMES:
PPS PROFILE
ETHYLENE TETRACHLORIDE
PERCHLOROETHYLENE
TETRACHLOROETHYLENE
PROJECT TYPE
FORMULA: C2CL4
PRIORITY POLLUTANT
HAZARDOUS POLLUTANT
00005
00006
00007
00008
00009
00010
05
05
06
05
07
02
*** NORMAL END ***
>
(4) CAS Number Format:
>@ADD EADS.PPS/CHEM-SEARCH
DO YOU NEED INSTRUCTIONS?
>NO
ENTER THE CODE/CHEMICAL ID (FORMULA)
>C/Q0127-18-4
DO YOU WISH TO SELECT WITHIN A RANGE OF PPS PROFILES?
>YES
ENTER THE MINIMUM NUMBER IN THE RANGE
>29
ENTER THE MAXIMUM NUMBER IN THE RANGE
>39
ENTER "END" OR CARRIAGE RETURN IF COMPLETE:
>END
7.2-8
-------
TETRACHLOROETHENE
MEG: 02B080 CAS: 00127-18-4 FORMULA: C2CL4
MOLECULAR WEIGHT: 165.83 PRIORITY POLLUTANT
HAZARDOUS POLLUTANT
OTHER NAMES: ETHYLENE TETRACHLORIDE
PERCHLOROETHYLENE
TETRACHLOROETHYLENE
NO PPS PROFILES FOUND BETWEEN PROFILES 00029 AND 00039
*** NORMAL END ***
(5) Example of User Aborted Run:
>@ADD EADS.PPS/CHEM-SEARCH
DO YOU NEED INSTRUCTIONS?
>NO
ENTER THE CODE/CHEMICAL ID (FORMULA)
>M/02P101
CHEMICAL DATA NOT FOUND FOR: M/02P101
WOULD YOU LIKE TO TRY AGAIN?
>NO
(6) Invalid Data Format/Data Not Found:
>@ADD EADS.PPS/CHEM-SEARCH
DO YOU NEED INSTRUCTIONS?
>NO
ENTER THE CODE/CHEMICAL ID (FORMULA)
>C/01A001
INVALID CAS FORMAT (01A001 )
CHEMICAL DATA NOT FOUND FOR: C/01A001
WOULD YOU LIKE TO TRY AGAIN?
>YES
ENTER THE CODE/CHEMICAL ID (FORMULA)
>M/001A001
CHEMICAL DATA NOT FOUND FOR: M/001A001
WOULD YOU LIKE TO TRY AGAIN?
>YES
ENTER THE CODE/ CHEMICAL ID (FORMULA)
>M/01A100
7.2-9
-------
DO YOU WISH TO SELECT WITHIN A RANGE OF PPS PROFILES?
>NO
ENTER "END" OR CARRIAGE RETURN IF COMPLETE:
>END
PENTANES
MEG: 01A100 CAS: FORMULA: C5H12
MOLECULAR WEIGHT: 72.15
NO PPS PROFILES FOUND IN ENTIRE DATA BASE
*** NORMAL END ***
7.2.9 Sample Batch Runs
The sample batch run outputs demonstrate the flexibility of the CHEM-
SEARCH program in satisfying user needs. The user input cards (which are
listed in the output) are underlined.
(1) MEG ID Format:
@RUN,D/RS Run ID, Account Number ,EADS, 10 ,20
@ASG,A EADS.
@XQT,BHZ EADS.PPS-CHEMSRCH
ENTER THE CODE/CHEMICAL ID
M/48A100
ENTER THE PROFILE RANGE TO BE SELECTED
PPS 00001-00100
ENTER THE PROFILE RANGE TO BE SELECTED
END
ELEMENTAL PHOSPHORUS
MEG: 48A100 CAS: 07723-14-0 FORMULA: P
MOLECULAR WEIGHT: 30.97 HAZARDOUS POLLUTANT
OTHER NAMES: BLACK PHOSPHORUS
RED PHOSPHORUS
WHITE PHOSPHORUS
YELLOW PHOSPHORUS
7.2-10
-------
PPS PROFILE
00083
00089
00092
00093
PROJECT TYPE
04
04
04
04
*** NORMAL END ***
@FIN
(2) CAS Number Format:
@RUN.R/RS Run ID,Account Number,EADS,8,10
@ASG,A EADS.
FAC WARNING 040000100000
@XQT EADS.PPS-CHEMSRCH
ENTER THE CODE/CHEMICAL ID (FORMULA)
C/00076-44-8
ENTER THE PROFILE RANGE TO BE SELECTED
PPS
ENTER THE PROFILE RANGE TO BE SELECTED
END
HEPTACHLOR
MEG: 16PN03 CAS: 00076-44-8
MOLECULAR WEIGHT: 373.35
OTHER NAMES:
PPS PROFILE
DRINOX
HEPTAGRAN
VELSICOL-104
PROJECT TYPE
FORMULA: C10H5CL7
PRIORITY POLLUTANT
HAZARDOUS POLLUTANT
00058
00074
00076
00082
00089
00103
00113
00115
00116
00134
00140
04
04
04
04
05
01
01
01
01
04
05
7.2-11
-------
*** NORMAL END ***
@FIN
(3) Empirical Formula Format:
@RUN,R/RS Run ID,Account Number^ADS.8,10
@ASG,A EADS.
FAC WARNING 040000100000
gXQT EADS.PPS-CHEMSRCH
ENTER THE CODE/CHEMICAL ID (FORMULA)
F/C10H5CL7
ENTER THE PROFILE RANGE TO BE SELECTED
PPS
ENTER THE PROFILE RANGE TO BE SELECTED
END
HEPTACHLOR
MEG: 16PN03 CAS: 00076-44-8
MOLECULAR WEIGHT: 373.35
OTHER NAMES:
PPS PROFILE
DRINOX
HEPTAGRAN
VELSICOL-104
PROJECT TYPE
FORMULA: C10H5CL7
PRIORITY POLLUTANT
HAZARDOUS POLLUTANT
00058
00074
00076
00082
00089
00103
00113
00115
00116
00134
00140
02
01
01
01
01
05
05
04
04
04
06
*** NORMAL END ***
@FIN
7.2-12
-------
(4) Invalid Data/Input Error Format:
(ciRUN.R/RS Run ID,Account Number,EADS,8,10
@ASG,A EADS.
@XQT EADS.PPS-CHEMSRCH
ENTER THE CODE/CHEMICAL ID (FORMULA)
C/00076-44-8
ENTER THE PROFILE RANGE TO BE SELECTED
PPS
ENTER THE PROFILE RANGE TO BE SELECTED
1104A NO DATA AVAILABLE ON ACCEPT (Missing END Card)
ERROR ADDR: 015514 BDI: 000013
EXEC8 ERROR: CONTINGENCY TYPE-12 ERROR TYPE-03 CODE-00 AT PROG
ADD 012165
BDI'S: M-I=000013 M-D=000012 U-I=000000 U-D=000000
-800- SYSTEM ERROR CODE 816 xll = 007255-
**** PLEASE NOTIFY DATA BASE ADMINISTRATOR ****
7.2-13
-------
7.3 PROFILE SUMMARY INFORMATION PROGRAM (SNAP-SHOT)
7.3.1 Abstract
The PROFILE Summary Information Program (SNAP-SHOT) is a brief report
which summarizes the contents of a PPS project profile. The report gives an
indication of "what" is contained in the profile without getting into details.
It will provide the user with an overview of the profile in a brief format
that would ordinarily require the obtaining of a more detailed and lengthy
PROFILE Report (see Section 7.1).
The formation of the SNAP-SHOT Report follows the PROFILE Report very
closely; it is as if a "snap-shot" had been made of the PROFILE Report. The
first page of the SNAP-SHOT Report is the same as the first page of the PROFILE
Report; that is, the project sponsor and contractor are identified, the con-
tract number and funding history are given, and the Profile Element Codes are
listed. The second page lists the reports or publications generated by or
pertaining to the project. The third page contains the project abstract.
This provides the user with the general overview of the project and limits
the output to three pages in most cases.
The SNAP-SHOT program may be initiated either through a "demand" (time-
sharing) session or through submitting a batch job. The demand version of
the program prompts the user with complete instructions for its use.
7.3.2 User Data Required
• Valid Project Type Code (optional)
• Valid Profile Number (or range of profile numbers)
7.3.3 Data Qualification Required
None
7.3,4 Limitations/Restrictions
The SNAP-SHOT program user has several printing options available includ-
ing the NCC local printers, remot high-speed terminal printers, and low-speed
time-sharing (demand) terminals. While the SNAP-SHOT Report itself is not
long (usually two to three pages), the volume of output could become voluminous,
particularly if the Project Type Option is selected and the subsequent retrieval
involves many project profiles. Unless the user is selecting a specific proj-
ect profile, it is recommended that the low-speed terminal option be avoided
where possible.
7.3.5 Functional Description
Using the PPS Project Type Code (if selected) and the PPN(s), the selected
profile(s) is(are) retrieved from the PPS data base and the summary information
is printed.
7.3-1
-------
7.3.6 User Instructions — Demand File name: EAD.PPS/SNAP-SHOT
The SNAP-SHOT program may be accessed through a "demand", or time-sharing
terminal (see Section 6.6), which can access the U-1100 computer. User access'
through the demand terminal allows the program to be executed as a batch job.
The user should initiate the demand session by following the procedures out-
lined in Section 6.6.1. When the session is completed, the demand session
may be ended by following the instructions given in Section 6.6.2.
(In the following computer-generated instructions, the response by the
user is underlined.)
>@ADD EAJS.PPS/SNAP-SHOT (Enter the file name)
CTS 6R1 16:21:01
THE ASSUME MODE IS FIELDATA
DO YOU NEED INSTRUCTIONS?:> YES (Enter YES or NO)
THIS MODULE IS SESIGNED TO RUN THE SNAP-SHOT REPORT FOR ANY VALID PROFILE
NUMBER AND PROJECT TYPE. INFORMATION REQUIRED TO RUN THIS ROUTINE WILL
BE ENTERED BY THE USER AS PROMPTED BY THIS MODULE.
THE USER MAY ENTER A SINGLE PROJECT PROFILE NUMBER OR A RANGE OF PROJECT
PROFILE NUMBERS.
>(Press carriage return to continue)
(If the answer to the instructions question was NO, the above statements would
be skipped.)
ENTER YOUR ACCOUNT NUMBER:> (Enter a valid NCC Accound Number)
DO YOU WISH TO SELECT THE PROJECT TYPE OPTION?
>YES (Enter YES or NO)
IF NO DATA TO BE INPUT FOR THIS PARAMETER, PRESS RETURN.
PROJECT TYPE:> (CR) (Enter value for the Project Type
Code or press return.)
ENTER THE NUMBER OF COPIES (Enter the number of copies wanted)
IF 1, JUST PRESS RETURN:> (CR)
DO YOU REQUIRE SPECIAL FORMS?> NO (Enter YES or NO)
(If YES has been entered, the program would request the forms ID.
consult the NCC User Reference Manual or the EADS Program Manger before
ing to use this feature. The NO response means that standard, one-part
paper will be used.) P
ENTER THE PRINT DESTINATION IF IT IS TO BE OTHER
THAN THE MAIN PRINTER:> (CR)
7.3-2
-------
(If there is no preference, press the return key. If the output is to
be a remote high-speed terminal, enter the site ID of the terminal. If a user
demand terminal is to receive the output, enter the user ID for that terminal
user.)
ARE YOU FINISHED (YES OR N0)?> (Enter YES or NO)
(If additional selections are to be made, enter NO and the program will
prompt for the Project Type selection. If YES, there will be a normal exit.)
Please refer to Section 7.3.8 for sample runs of the demand SNAP-
SHOT program. An example of the SNAP-SHOT Report is given in Section 7.3.10.
It should be emphasized that SNAP-SHOT does not actually execute as a
demand (time-sharing) job. The demand routine creates a job stream which is
processed as a batch job by the U-1100.
7,3.7 User Instructions -- Batch
The SNAP-SHOT program may also be executed as a batch job on the UNIVAC
U-1100 using punched card input. It is assumed that the user has card input
access to the U-1100 computer either through "across the counter" submitted
at Research Triangle Park, NC, or through a remote batch terminal.
In order to run the SNAP-SHOT program in batch mode, the user should sub-
mit the following cards:
@RUN,R/RS RUN ID,Account Number, EADS,5,50/50, no blank
@ASG,A EADS.
@XQT,BHZ EADS.PPS/SNAPSHOT
. . . parameter cards . . .
@FIN
Two types of parameter cards are used to identify the options selected
and to drive the program. If the user wishes to print the SNAP-SHOT report
for a specific PPN (or range of PPN's), the following Type 1 parameter card
is used:
1 2
Type 1: Card Col. 12345678901234567890
-^ PPSXX MINXX-MAXZZ
where XX identifies the Project Type Code beginning in column 4,
MINXX is the starting PPN in the range of PPN's to be specified.
The PPN should be entered as a right-justified integer
number in card colums 7-11,
7.3-3
-------
(enter a dash in card column 12)
MAXZZ is the last PPN in the range of PPN's to be specified.
The PPN should be entered as a right- justified integer
number in card columns 13-17.
"NOTE" If no range of PPN's is requested (that is, if a single Profile
Number is selected), leave card columns 12-17 blank.
Following the Type 1 card, the Type 2 card is entered to indicate the
end of the data. It should be the last parameter card in the deck before the
@FIN card. The card has the following format:
Type 2: Card Col. 123
END
•'^CAUTION* The parameter cards must be entered into the card deck in the
following order:
Type 1
Type 2
Examples of batch runs of SNAP-SHOT are given in Section 7.3.9.
7.3.8 Sample Demand Runs
(1) SNAP-SHOT for a Specific PPN:
>@ADD EADS.PPS/SNAP-SHOT
DO YOU NEED INSTRUCTIONS?
>NO
ENTER YOUR ACCOUNT NUMBER :> Account Number
DO YOU WISH TO SELECT THE PROJECT TYPE OPTION?
>NO
DO YOU WISH TO SELECT WITHIN A RANGE OF PROFILES?
>NO
ENTER THE PROFILE NUMBER :> 225
ENTER THE NUMBER OF COPIES
IF 1, JUST PRESS RETURN :> 2
DO YOU REQUIRE SPECIAL FORMS? > NO
ENTER THE PRINT DESTINATION IF IT IS TO BE OTHER THAN THF
MAIN PRINTERS
ARE YOU FINISHED (YES OR N0)?> YES
*** NORMAL EXIT ***
(2) SNAP-SHOT for a Range of PPN's:
7.3-4
-------
>(3ADD EADS.PPS/SNAP-SHOT
DO YOU NEED INSTRUCTIONS?
>NO
ENTER YOUR ACCOUNT NUMBER:> Account Number
DO YOU WISH TO SELECT THE PROJECT TYPE OPTION?
>NO
DO YOU WISH TO SELECT WITHIN A RANGE OF PROFILES?
>YES
ENTER THE MINIMUM NUMBER IN THE RANGE
>29
ENTER THE MAXIMUM NUMBER IN THE RANGE
>39
ENTER THE NUMBER OF COPIES
IF l.JUST PRESS RETURN:> 2
DO YOU REQUIRE SPECIAL FORMS?:> NO
ENTER THE PRINT DESTINATION IF IT IS TO BE OTHER THAN THE
MAIN PRINTERS (CR)
ARE YOU FINISHED (YES OR N0)?> YES
*** NORMAL EXIT ***
7.3.9 Sample Batch Runs
(To be added later.)
7.3.10 Sample Output
(To be added later.)
7.3-5
-------
7.4 PROFILE ABSTRACT PROGRAM (ABSTRACT)
7.4.1 Abstract
The ABSTRACT program is a brief report which identifies the project and
prints the project abstract contained in the PPS data base. The information
provided includes the project type, profile number, sponsor and contractor
identities, and the title. Usually, the abstract will be one page or less,
but some project profiles do have abstracts which run to two pages. This re-
port, like SNAP-SHOT, will give the user an overview of the project. If more
details are needed, the user should obtain the PROFILE Report.
The ABSTRACT program may be initiated either through a "demand" (time-
sharing) session or through submitting a batch job. The demand version of
the program prompts the user with complete instructions for its use.
7.4.2 User Data Required
Valid Project Type Code (optional)
• Valid Project Profile Number (or range of PPN's)
7.4.3 Data Qualification Required
None
7.4.4 Limitations/Restrictions
The ABSTRACT program user has several printing options available includi-
ng the National Computer Center local printers, remote high-speed terminal
printers, and low-speed time-sharing (demand) terminals. While the ABSTRACT
Report itself is not long (usually 1-2 pages), the volume of output could be-
come voluminous, particularly if the subsequent retrieval involves many pro-
files. Unless the user is selecting a specific profile, it is recommended
that the low-speed terminal option be avoided where possible.
7.4.5 Functional Description
Using the Project Type Code and the Project Profile Number(s) specified,
the ABSTRACT program retrieves the abstract and prints a brief report.
7,4.6 User Instructions - Demand File name: EADS.PPS/ABSTRACT
The ABSTRACT program may be accessed through a "demand", or time-sharing,
terminal (see Section 6.6), which can access the U-1100 computer. User access
through the demand terminal allows the program to be executed as a batch job.
The user should initiate the demand session by following the procedures out-
lined in Section 6.6.1. When the session is completed, the demand session
may he ended by following the instructions given in Section 6.6.2.
7.4-1
-------
(In the following computer-generated instructions, the response by the
user is underlined.)
>@ADD EADS.PPS/ABSTRACT (Enter the file name)
CTS 6R1 16:21:01
THE ASSUME MODE IS FIELDATA
DO YOU NEED INSTRUCTIONS?:> YES (Enter YES or NO)
THIS MODULE IS DESIGNED TO RUN THE ABSTRACT REPORT FOR ANY VALID PROFILE
NUMBER AND PROJECT TYPE ENTERED. INFORMATION REQUIRED TO RUN THIS ROUTINP
WILL BE ENTERED BY THE USER AS PROMPTED BY THIS MODULE.
THE PROJECT TYPE OPTION ALLOWS THE USER TO SEARCH THE ENTIRE DATA BASE
FOR ALL PROFILES WHICH SATISFY THE SELECTION CRITERIA.
>(Press carriage return to continue)
OTHERWISE, THE USER MAY ENTER A SINGLE PROFILE NUMBER OR A RANGE OF PROFILE
NUMBERS.
>(Press carriage return to continue)
(If the answer to the instructions question had been NO, the above
statements would be skipped.)
ENTER YOUR ACCOUNT NUMBER:> (Enter a valid NCC Account Number)
DO YOU WISH TO SELECT THE PROJECT TYPE OPTION?
>YES (Enter YES or NO)
ENTER THE VALUE FOR THE PROJECT TYPE AS PROMPTED.
IF NO PROJECT TYPE IS TO BE SPECIFIED, PRESS RETURN.
PROJECT TYPE CODE:> (CR) (Enter value as an integer
number or press return.)
ENTER THE NUMBER OF COPIES (Enter the number of copies
IF 1, JUST PRESS RETURN:> (CR)
DO YOU REQUIRE SPECIAL FORMS?> NO (Enter YES or NO)
(If YES has been entered, the program would request the forms ID. Piea
consult the NCC User Reference Manual or the EADS Program Manger before att ^
ing to use this feature. The NO response means that standard, one-part mmerapt~
paper will be used.) P computer
7.4-2
-------
ENTER THE PRING DESTINATION IF IT IS TO BE OTHER THAN THE
MAIN PRINTERS (CR)
(If there is no preference, press the return key. If the output is to
be a remote high-speed terminal, enter the site ID of the terminal. If a user
demand terminal is to receive the output, enter the user ID for that terminal
user.)
ARE YOU FINISHED (YES OR N0)?> (Enter YES or NO)
(If additional selections are to be made, enter NO and the program will
prompt for the project type code. If YES, there will be a normal exit.)
Please refer to Section 7.4.8 for sample runs of the demand ABSTRACT pro-
gram. An example of the ABSTRACT Report is given in Section 7.4.10.
It should be emphasized the ABSTRACT does not actually execute as a demand
(time-sharing) job. The demand routine creates a job stream which is processed
as a batch job by the U-1100.
7.4.7 User Instructions - Batch
The ABSTRACT program may also be executed as a batch job on the UNIVAC
U-1100 using punched card input. It is assumed that the user has card input
access to the U-1100 computer either through "across the counter" submitted
at Research Traingle Park, NC, or through a remote batch terminal.
In order to run the ABSTRACT program in batch mode, the user should submit
the following cards:
@RUN,R/RS RUN ID,Account Number,EADS,5,50/50
@ASG,A EADS.
@XQT,BHZ EADS.PPS-ABSTRACT
. . . parameter cards . . .
@FIN
Two types of parameter cards are used to identify the options selected
and to drive the program. If the user wishes to print the ABSTRACT report
for a specific Profile Number (or range of Profile Numbers), the following
Type 1 parameter card is used:
1 2
Type 1: Card Col. 12345678901234567890
-** PPSXX MINXX-MAXZZ
7.4-3
-------
WHERE XX identifies the project type code beginning in column 4
MINXX is the starting Profile Number in the range of PPN's
to be specified. The Profile Number should be entered
as a right-justified integer number in card columns
7-11,
(enter a dash in card column 12)
MAXZZ is the last Profile Number in the range of PPN's to be
specified. The Profile Number should be entered as a
right-justified integer number in card columns 13-17.
*NOTE* If no range of Profile Numbers is requested (that is, if a
single Profile is selected), leave card columns 12-17 blank.
Following the Type 1 card, the Type 2 card is entered to indicate the
end of the data. It should be the last parameter card in the deck before th
@FIN card. The card has the following format: fte
Type 2: Card Col. 123
END
"CAUTION"" The parameter cards must be entered into the card deck in the
following order:
Type 1
Type 2
Examples of batch runs of ABSTRACT are given in Section 7.4.9.
7.4.8 Sample Demand Runs
(1) ABSTRACT for a specific Profile Number:
>@ADD EADS.PPS/ABSTRACT
DO YOU NEED INSTRUCTIONS?
>NO
ENTER YOUR ACCOUNT NUMBER:> Account Number
DO YOU WISH TO SELECT THE PROJECT TYPE OPTION?
>NO
DO YOU WISH TO SELECT WITHIN A RANGE OF PROFILES?
>NO
ENTER THE PROFILE NUMBER:> 225
ENTER THE NUMBER OF COPIES
IF 1, JUST PRESS RETURN:> 2
DO YOU REQUIRE SPECIAL FORMS:> NO ~
7.4-4
-------
ENTER THE PRINT DESTINATION IF IT IS TO BE OTHER THAN
THE MAIN PRINTERS (CR)
ARE YOU FINISHED (YES OR N0)?> YES
*** NORMAL EXIT ***
(2) ABSTRACT for a Range of Profile Numbers:
>@ADD EADS.PPS/ABSTRACT
DO YOU NEED INSTRUCTIONS?:
>NO
ENTER YOUR ACCOUNT NUMBER:> Account Number
DO YOU WISH TO SELECT THE PROJECT TYPE OPTION?
>NO
DO YOU WISH TO SELECT WITHIN A RANGE OF PROFILES?
>YES
ENTER THE MINIMUM NUMBER IN THE RANGE
>29
ENTER THE MAXIMUM NUMBER IN THE RANGE
>39
ENTER THE NUMBER OF COPIES
IF I, JUST PRESS RETURN:> 2
DO YOU REQUIRE SPECIAL FORMS:> NO
ENTER THE PRINT DESTINATION IF IT IS TO BE OTHER THAN
THE MAIN PRINTERS (CR)
ARE YOU FINISHED (YES OR N0)?> YES
*** NORMAL EXIT ***
7.4.9 Sample Batch Runs
(To be added later.)
7.4.10 Sample Output
(To be added later.)
7.4-5
-------
APPENDIX A.I
LIST OF ERROR MESSAGES
A.1-1
-------
To be added later.
A.1-2
-------
APPENDIX A.2
DATA BASE DEFINITIONS
A.2-1
-------
Profile
Elements (A)
C50
EADS
Profile (A)
Administrative Level
C600
Activity
(D)
Activity Level
C700
Test/Control
Systems (E)
Test Level
C800
Analysis
(F)
Analysis Level
C900
Pollutants
(G)
Pollutant Level
Figure A.2-1. PPS Data Base Tree
A.2-2
-------
DATA BASE NAME IS EADS-PPS
50* PROFILE (RG)
100* PROFILE NUMBER (INTEGER NUMBER 9(5) IN 50)
102* PROGRAM NAME (NAME X(8) IN 50)
268* PROJECT TYPE CODE (INTEGER NUMBER 99 IN 50)
110* PROJECT SPONSOR (NAME X(30) IN 50)
210* SPONSOR BRANCH CODE (NAME XXXX IN 50)
220* SPONSOR DIVISION CODE (NAME X(5) IN 50)
230* SPONSOR LAB CODE (NAME X(9) IN 50)
130* PROJECT START DATE (DATE IN 50)
140* PROJECT FINISH DATE (DATE IN 50)
160* SPONSOR ADDRESS (NON-KEY NAME X(20) IN 50)
170* SPONSOR CITY (NON-KEY NAME X(20) IN 50)
180* SPONSOR STATE (NAME XX IN 50)
200* SPONSOR ZIP/MAIL CODE (NON-KEY INTEGER NUMBER 9(6) IN 50)
190* SPONSOR COUNTRY (NAME X(7) IN 50)
265* AGENCY INVENTORY NUMBER (INTEGER NUMBER 9(7) IN 50)
260* DATE OF PPS ENTRY (DATE IN 50)
240* PROJECT OFFICER (NON-KEY NAME X(30) IN 50)
250* PROJECT OFFICER TELEPHONE (NON-KEY NAME X(20) IN 50)
120* CONTRACT/GRANT NUMBER (NAME X(U) IN 50)
145* FISCAL INFORMATION (RG IN 50)
155* FISCAL YEAR (NAME XXXX IN 145)
150* FUNDING (DECIMAL NUMBER 9(6).9 IN 145)
270* PROJECT TITLE-1 (NON-KEY NAME X(72) IN 50)
271* PROJECT TITLE-2 (NON-KEY NAME X(72) IN 50)
280* CONTRACTOR NAME (NAME X(30) IN 50)
290* CONTRACTOR ADDRESS (NON-KEY NAME X(20) IN 50)
300* CONTRACTOR CITY (NON-KEY NAME X(20) IN 50)
310* CONTRACTOR STATE (NAME XX IN 50)
330* CONTRACTOR ZIP/MAIL CODE (NON-KEY INTEGER NUMBER 99 IN 50)
320* CONTRACTOR COUNTRY (NAME X(7) IN 50)
A.2-3
-------
340-- CONTRACTOR PROJECT MGR (NON-KEY NAME X(30) IN 50)
350- CONTRACTOR PROJECT MGR TELEPHONE (NON-KEY NAME X(20) IN 50)
360* PROFILE ELEMENTS (RG IN 50)
370» PROFILE ELEMENTS CODE (NAME XXXX IN 360)
400* REPORTS (RG IN 50)
410* REPORT SEQUENCE NUMBER (INTEGER NUMBER 99 IN 400)
420* REPORT TITLE-1 (NON-KEY NAME X(70) IN 400)
430* REPORT TITLE-2 (NON-KEY NAME X(70) IN 400)
440* REPORT AUTHORS (NON-KEY NAME X(70) IN 400)
450* SPONSOR REPORT NUMBER (NAME X(21) IN 400)
460* NTIS NUMBER (NAME X(2l) IN 400)
470* REPORT PUBLISHED DATE (NAME X(15) IN 400)
480* ISSUE DATE (DATE IN 400)
500* ABSTRACT (RG IN 50)
510* LINE NUMBER (INTEGER NUMBER 999 IN 500)
520* ABSTRACT TEXT (NON-KEY TEXT X(69) IN 500)
600* ACTIVITY LEVEL (RG IN 50)
610* ACTIVITY NUMBER (INTEGER NUMBER 999 IN 600)
615* TASK ORDER/TD NUMBER (NAME X(34) IN 600)
672* ACTIVITY START DATE (DATE IN 600)
674* ACTIVITY DURATION (DECIMAL NUMBER 999.9 IN 600)
680* FPEIS TSN (INTEGER NUMBER 9(5) IN 600)
682* GEDS TSN (INTEGER NUMBER 9(5) IN 600)
681* LEDS TSN (INTEGER NUMBER 9(5) IN 600)
683* SDDS TSN (INTEGER NUMBER 9(5) IN 600)
684* FEIS TSN (INTEGER NUMBER 9(5) IN 600)
686* PRIMARY ACTIVITY (NAME X(35) IN 600)
685* ACTIVITY FREQUENCY (NAME X(34) IN 600)
687* SOURCE NAME (NON-KEY NAME X (35) IN 600)
676* ACTIVITY LOCATION (NON-KEY NAME X(34) IN 600)
620* SOURCE CATEGORY (NAME X(20) IN 600)
630* SOURCE TYPE (NAME X(20) IN 600)
640* PRODUCT/DEVICE (NAME X(20) IN 600)
650* PROCESS TYPE (NAME X(20) IN 600)
660* FEED MATERIAL CATEGORY (NAME X(10) IN 600)
A.2-4
-------
670* FEED MATERIAL TYPE (NAME X(10) IN 600)
690* ACTIVITY LEVEL COMMENTS (RG IN 600)
691* ACTIVITY LINE NUMBER (INTEGER NUMBER 99 IN 690)
695* ACTIVITY COMMENTS (NON-KEY TEXT X(67) IN 690)
700* TEST LEVEL (RG IN 600)
710* TEST ID NUMBER (INTEGER NUMBER 99 IN 700)
715* PROJECT TOPIC (NAME X(15) IN 700)
780* METHODS/ISSUES (NAME X(52) IN 700)
775* ISSUES (NAME X (23) IN 700)
770* APPROACH (NAME X(18) IN 700)
760* FACTORS (NAME X(26) IN 700)
720* MEDIA (NAME X(5) IN 700)
730* POLLUTANT CONTROL GENERIC DEVICE (NAME X(20) IN 700)
740* POLLUTANT CONTROL DESIGN TYPE (NAME X(32) IN 700)
750* POLLUTANT CONTROL PROCESS (NAME X(67) IN 700)
790* TEST LEVEL COMMENTS (RG IN 700)
791* TEST LINE NUMBER (INTEGER NUMBER 99 IN 790)
795* TEST COMMENTS (NON-KEY TEXT X(65) IN 790)
800* ANALYSIS LEVEL (RG IN 700)
801* ANALYSIS NUMBER (INTEGER NUMBER 99 IN 800)
802* ANALYSIS DESIGNATOR (NAME X IN 800)
805* ANALYSIS LOCATION (NAME X(35) IN 800)
810* TEST TYPE (NAME X(29) IN 800)
820* TEST DESCRIPTION (NAME X(65) IN 800)
830* TEST STRAINS/ORGANISMS/ECOSYSTEMS (RG IN 800)
835* SERIAL NUMBER (INTEGER NUMBER 99 IN 830)
840* STRAINS/ORGANISMS/ECOSYSTEMS (NAME X(63) IN 830)
850* ANALYSIS LEVEL COMMENTS (RG IN 800)
851* ANALYSIS LINE NUMBER (INTEGER NUMBER 99 IN 850)
855* ANALYSIS COMMENTS (NON-KEY TEXT X(63) IN 850)
900* POLLUTANT LEVEL (RG IN 800)
905* POLLUTANT NUMBER (INTEGER NUMBER 99 IN 900)
910* POLLUTANT MEDIA (NAME X(8) IN 900)
920* POLLUTANT CODE TYPE (NAME X IN 900)
930* POLLUTANT CODE (NAME X(30) IN 900)
A.2-5
-------
940* SAMPLING TECHNIQUES CODE (NAME XXXX IN 900)
950- ANALYTICAL TECHNIQUES CODE (NAME XX IN 900)
960» SAMPLING LOCATION CODE (NAME XXX IN 900)
A.2-6
-------
APPENDIX A.3
PPS DATA BASE GLOSSARY
A.3-1
-------
The following table is a glossary of all the data elements in the PPS/
data bases. The table lists the name of the data element (in the order it
appears on the input forms), the data base variable name (as it is defined
in the data base definition), the corresponding component number(s) and
field size or format (from the data base definition), and a description of
the data element. For further clarification on these definitions, refer
to Section 4, the detailed encoding instructions.
In the field size or format, X(20) means an alphanumeric field 20 char-
acters long. The format 9(5) means an integer field, five numbers long, and
9(3).9(2) represents a decimel number field with three numbers before the
decimal point and two after.
The exponential format requires two data elements, a decimal number for
the mantissa, and an integer number for the exponent. In the description of
the data element, the exponential format is written nn.nn E ± nn.
A.3-2
-------
FORM 1 - ADMINSTRATIVE DATA
a>
i
Data Element Name
Profile Number
Program Name
Project Type Code
Project Sportsor
Sponsor Branch Code
Sponsor Division Code
Sponsor Laboratory Code
Project Start Dale
Project Finish Date
Sponsor's Street Address/
p n nA«
Component No.
Data Base Variable Kame in t)lt
Profile Number HOO
Program Name CIH2
Project Type Code C268
Project Sponsor Cl 10
Sponsor Branch Code C2 10
Sponsor Division Code C22ft
Sponsor f,ab Code C2.1<>
Project Start Date C130
Project finish Date CI40
Sponsor's Street Address CI60
Field Si?"/Fori«al
Integer 9(5)
N.ime X(fi)
Integer Number 99
Name X(3D)
Name XXXX
Name X(5)
Name X(9)
Pate
Date
Non-Key Name X(20)
Description
A number identifying the specific project.
The n.tme or initials nf the ftver.il! program in
(e.g. , CCF.A, Synfuels).
A two-digit cnde denoting the project type.
The n.'iine of the organization who sponsored the
sampling program fe.g., F.PA).
Tho four-character abbreviation for the brnncli
nf tbf sponsoring organization funding the pro-
ject as text (e.g. PTRB for Process Technological
Brancli) .
The five-character abbreviation for the division of
the sponstiring organization funding the project as
text. An example is U1PD for Utility and Industrial
Power Division.
The code or abbreviation for the agency laboratory
sponsoring the project, fin example is IERI./RTP for
for Industrial Environmental Research Laftoratory at
Research Triangle Park.
The starting date of tho project (MH-DD-VY) .
The finishing date of the project (MH-DD'-YY).
The nnnher and name of the sponsoring organ i-
Sponsor City
Sponsor State
Sponsor Zip/flail Code
Sponsor Country
Sponsor City
Sponsor Stale
Sponsor Zip/Hail Code
Sponsor Country
C170
CI80
CITO
Non-Key Name X(20)
Nam? XX
Won-Key fnleger Number "(6)
Name X(7)
gallon's street address or P.O. box.
The name of Iho city, tovmship, or area in whicli
sponsoring organisation is lorated.
The two-Letter code for the Mate or Canadian pro-
vince in which sponsoring org.ini7.at i
-------
FORM 1 (Continued)
Component No.
Data Element Name
Agency Inventory No.
Date of PPS Entry
Project Officer
Project Officer Telephone
Number
Contract No. /Grant No.
Fiscal Yr.
Funding (K$)
Project Title
Contractor Name
Contractor Street Address/
P.O. Box
Contractor City
Contractor State
Contractor Zip/Hail Code
Contractor Country
Data Base Variable Name
Agency Inventory No.
Date of PPS Entry
Project Officer
Project Officer Telephone
Number
Contract No. /Grant No.
Fiscal Yr.
Funding (K$)
Project Title
Contractor Name
Contractor Street Address/
P.O. Box
Contractor City
Contractor State
Contractor Zip/Mail Code
Contractor Country
in DB
C265
C260
C240
C250
C120
C155
C150
C270
C271
C280
C290
C300
C310
C330
C320
Field Size/Format
Integer Number 9(7)
Date
Non-Key Name K(30)
Non-Key Name X(20)
Name X(K)
Name XXXX
Decimal Number 9 (6). 9
Non-Key Name X(72)
Name X(30)
Non-Key Name X(20)
Non-Key Name X(20)
Name XX
Non-Key Integer Number 9(6)
Name X(7)
Description
The unique ID number assigned by the agency perform-
ing the inventory.
The date the PPS information was recorded, entered
as DD/MM/YY.
The name of the sponsoring organization's project
officer with a first name, middle name, and last
name format.
The telephone number, including area cede and ex-
tension, of the project officer. Include the FTS
number, if known.
The number of the sponsoring organization contract,
with the inclusion of blank spaces and hyphens.
The fiscal year that the funds were allocated, as
FY . A maximum of six values m.iy be entered
on a single card and additional cards may be used
as needed.
The level of funding for the fiscal year indicated
in the previous data item in thousands of dollars
with decimal notation for fractional amounts.
Multiple entries may be encoded on a single card
as needed.
The complete title of the project without abbrevia-
tions. Use both cards when necessary.
The name of the contracting organi?.ation.
The number and name of the street address or P.O. Box
of the contractor.
The name of the city, township, or area where the
contractor is located.
Tile two-letter code for the state or Canadian pro-
vince in which the contractor is located.
The zip/mail code of the contractor.
The abbreviation for the country in which the
contractor is located.
-------
FORM 1 (Concluded)
HiL.i Elewnt Na*
D.iL.i B.ise Variable N.imc
Contractor Project Manager Contractor Project Manager
Contractor I'roject Manager Contractor Project n.inaf>rr
Telephone Number Telephone Numlier
Profile Element Corte
Profile Flpment Code
Comvionent No.
in OR
C340
TWO
C170
Field Si^p/Kormat
Non-Key Name X(301
Non-Key N.inf X(20)
N;imr XXXX
Descri pLion
Tho name of the contractor's main project msn.-iRer
The telephone mmber, including area code and ex-
tension of the contractor's project manaRpr.
The code which uniquely identifies objectives
achieved in tlie project.
I
Ln
-------
FORM 2 - REFERENCE INFORMATION
Data Element Name
Report Sequence Number
Report Title
Report Title
Report Authors
Sponsor Report Number
NTIS Number
Report Published Date
>. Actual Report Date
•
U>
1
Data Base Variable Name
Report Sequence Number
Report Title- 1
Report Title-2
Report Authors
Sponsor Report Number
NTIS Number
Report Published Date
Issue Date
Data Base
Component
Numbers
C410
C420
«30
CMC
C450
C460
C470
C480
Field Size/Format
Integer Number 99
Non-Key Name X(70)
Non-Key Name X(70)
Non-Key Name X(70)
Name X(21)
Name X(21)
Nane X(15)
Date
Description
The sequential integer nunber identifying
eaclv reference to he encoded.
The complete title of the report in which the data
is reported with no abbreviations in the title.
Continuation, if necessary, of the title
of the report from which the data are reported.
The names(s) of the author(s) of the report. The
main author is listed by last name, first name,
and middle initial.
The number, as assigned by the sponsoring
organization, of the report in which the d.it.i
are reported.
The National Technical Information Service (NTIS)
number of the report.
The publication date printed on the report,
as month and year (e.g., May 1980).
The date the report was actually issued, entered
as MM-DD-iY.
-------
FORM 3 - ABSTRACT
Data R.i Re
Data F.lenent Name Data Base Variable Name Nimhrr Field Si?.e /Format
Line Number Line Number Cr>10 Integer Nnmlior
Abstract as Text Abstract Text CS20 Non-Key Tr»t X(6<»)
Description
The sp^upntial number for each line of abstract
trxt recorded.
An abstract of the project including any perl inent
keywords. Unlimited cards way be added as needed.
U>
I
-------
FORM A - SITES/ACTIVITIES
00
0,1 t.i Element Name
Art ivity Number
Task Order/T.D. Number
Activity Start Date
nur.il ion
FPF.IS TSN
GEDS TSN
LF.OS TSN
SDOS TSN
FEIS TSN
Data Base Variable Namp
Activity Number
Task Ordcr/TD Number
Activity Start Date
Duration of Testing
FPEIS TSN
GEDS TSN
LCDS TSN
SDDS TSN
FF.IS TSN
D.ila Rise
Component
Numbers
CMC
C6I5
Ch72
C674
C6RO
C6R2
C6B1
C6S3
Field S i zo/ Formal
llltPRnr Numlifr 999
Name X(^i.)
Date
Decim.il 991.1
Df-srri |>t ^on
Integer )
Inlpgrr
Integer
The KPniienti.il integer coHe nnmlier For each scrupling
arLivily reported.
The EPft tnsV orfler or technical directive number.
The sampling project start date in Tor™ MM-PP-YY.
The lengtl! of testing, in months, as a decini.il
ninrine r.
The Fine Particle Emissions Information System Test
Series Number associated vith the fine, part i nil ;ile
information, whirli was re-lleeted from the K.IIIIP sonri e
ami at tlie same IJmc as the dale for the test sprier.
heing encoded.
The Gnserms EminBionK Data System Test Series Mnmtter
associated vith the gaseous information, whuh was
collected from the same source and at the same time
as the data for the Lest series being encoded.
The U<|iiid Effluents Data System Test Series Nmnhcr
associated with the liquid effluent information,
which was collected from the same source and ;»L
the same time as the date for the test series
lining encoded.
The Solid Discharge Data System Test Series Nimber
associated with the solid discharge information,
which vap collected from the same source ami al M»e
same time as the ilita for the test series heing en-
rodr.l.
The Fugitive Emissions Information System T^st
Series Nuniher associated vith the fugitive emissions
information, which was collected from the same
source and at the same time as the data for the
test series heing encoded.
-------
TORM 4 (Concluded)
Dat.i Element Name
Primary Activity
Activity Frequency
Source Name
Activity Location
Source Category
Data Rase Variable N.mf
Primary Activity
Activity Frequency
Source Name
Activity Location
Source Category
Oat» fcaso
Component
Biwhcrs
r.fiS6
MB
Cf>R7
CfrW
C620
field Size/Format
Name XO5)
d.ime X(34)
Hen-Key Name XO5)
Non-Key Ns
Description
The r X(lfl)
Hane X(10)
Non-Key Text K(67)
source classes, i.e., the broadest
of a source (e.g., combustion, iron, steel, and
rood nnd agricultural products... ).
The kind of so«rce. vithin a source category
(e.g., utility, primary, ferrous, rubber, and
wood, etc.).
The general device or specific product (e.g.,
boiler, natural rubber, and sterl, etc.).
The unique process being tested (e.R.,
tangenti.il, stoker, electric, arc furnace,
roasting, and line kilns, etc.).
The general category of the process, f>ed naif-rial
or fuel (e.jt-, coal, oil, gas, wood, solid wasf,
and metal scrap, etc.).
Ttie specific type of feed material or fwl.
A sequential, intff^r number for earh line r?t
activity lewl comments.
The coM»ei»ts on the test scries, entered
-------
FORM 5
>
U)
t
M
O
Data Element Name
Test ID Number
Project Topic
Methods
Issues
Approach
Factors
Media
Pollutant Control Generic
Device
Pollutant Control Design
Type
Pollutant Control Process
Line Number
Data Base Variable Name
Test ID Number
Project Topic
Methods
Issues
Approach
Factors
Media
Pollutant Control Generic
Device
Pollutant Control Design
Type
Pollutant Control Process
Line Number
Data Rase
Component
Numbers
C710
C715
C780
C775
C770
C760
C720
C730
C740
C750
C79I
Field Size/Format
Integer Number 99
Name X(15)
Name X(52)
Name X(23)
Name X(18)
Name X(26)
Name X(5)
Non-Key Name X(20)
Non-Key Name X(32)
Non-Key Name X(67)
Integer Number 99
Description
The sequential integer number for each test
conducted.
The code for the project topic per site, either
sampling or analysis.
Each sampling/analysis method or name of equipment
used in obtaining a sample or analyzed results.
The primary issues considered in the assessment.
The general method or approach used in the
assessment.
The factors analyzed in the project.
The generalized name of the media from which
the sample vas extracted.
The type of generic control device or treatment
process.
The control device design type.
The specific control device or treatment process.
A sequential integer number for each line of
comments text.
Test Comments
Test Comments
C795
Non-Key Text X(67)
Any pertinent comments on the testing activity.
-------
FORM 6 - POLLUTANTS
Data Element Name
Analysis Number
Analysis Designation
Analysis Location
Test Type
Test Description
Serial Number
, Straiiis/Organisnis/EcosysteiKS
Line Number
Analysis Comments
Data Base Variable N.inte
Analysis Number
Analysis Designation
Analysis Location
Test Type
Test Description
Serial Number
Strains/Organisms /Ecosystems
Line Number
Analysis Comment s
"Data R-ise
Component
Numbers
CROI
CRUZ
CSO.-i
C810
C82II
C8TV
C840
C8r) 1
C85S
Field Size/Format
Integer Number 99
Name X
Name X(35)
Name X(29)
Name X(n5)
Integer Number 9")
Name X{63)
Integer Nnmber 99
Non-Key Text X(63)
Description
A sequential, integer number for each analysis
reported.
The letter code designating the type of analysis
reported. The letter "B" for biological, "F." for
ecological, or "P" for polfntanL.
The name and location of the laboratory that
performed the analysis.
The name of the broad category of biological or
ecological test type used in the analysis.
The code for the description name of the biologi-
cal or ecological test used in the analysis per-
formed.
A sequential integer number to identify each bio-
logical or ecological test strain, organism, or
ecosystem used in the analysis.
The name of the specific test strain, organism, or
ecosystem used in the analysis (e.g., TA-15.18,
TA-9S, etc.)
A sequential integer number for each line of
comments text.
Any pertinent comments on the analysis reported.
-------
FORM 7
n.ita Base
Component
Data Element Name Data Rase Vari.ihlp Name Numbers FieM Sizo/Formal
Pollutant. Number Pollutant Number C90S Integer Nuntlirr 99
Pollutant Media Media Class C9IO Name X(K1
Pollutant Code Type Pollutant Code Type C020 N.ime X
Pollutant Code Pollutant f.orte mitt Nnmr> XO<))
S.irapliiiR Terhniijue Code Sampling Technique Cndn C940 Namr- XXXX
>
. Analytical Techniques Code Analytical Techniques Code CQSO Name XX
u>
1
Description
The sequential integer number uniquely itlenli fy i ng
a po Mut .int.
The n.ime of the media in ulifrli Hie sampling was
performed .
The pollutant entry code number which ilesign.ites
the type of pollutant used. C for CAS mimhrr, M
for MEG number, R for radiomiclide, anfl T for
Rpneral text value.
Th*1 i dent i f iration cotle of the pollutant sampled.
The text entries describing the pollutant. [f
code type C, pollutant code is CAS number. If
M, pollutant rode is MEfi number. If R. pollutant
i ode is a radionuclide, and if 1\ pollutant ro<]e is
a general code.
The code identifying the sampling technique used.
The two-character code identifying the analytical
method used to determine the specific pollut.int.
NJ
Sampling Location Code
Sampling Location Code
Name XXX
The three-character code identifying the sampling
location.
-------
APPENDIX A.A
PPS DATA ENCODING FORMS
A.4-1
-------
&EPA EADS
U.S. ENVIRONMENTAL PROTECTION AGENCY
ILKL-KIP Kun-ui..!, riiungk- Puik NX. 2/VI1
D) D
PROJECT PROFILE SYSTEM
FORM 1
9/80
A
DATAINPUTFORMS ffo
- ADMINISTRATIVE DATA 1
EADS
Profile
Number
-
|
1
Card
No.
Al
0
Card
No.
i
A
e
0 2
Card
No.
o
LA.
7 8
0 3
Card
No.
6
A
7 a
U 4
Card
No.
6
"A"
7 8
0 5
0 6
Card
No.
6
A
C
r-
6
IA
7 8
0 7
ard
-lo
7 8
0 8
j Card
J No.
6 7 |e
* 0(9
* 0/9
Program Name
'4 1
i •
—
'd i
'roject Type Code
'reject Sponsor
v 2U
21
2J 2
3 24
25
26
2'
28
Sponsor Street Address/P.O. Sox
= '•;
« I
< u
4
j 16
i;
18 1
9 2(j
21
22 2
3 24
25
26
27
Project Officer
9 '0
II
Fisca
Year
9 10
1
2 l>
14
5 16
17
16
Funding (K$)
2 13
14 1
D 16
17
18 1
9 20
21
22 2
Fiscal
Year
9 20
21
22 2
3 24
25
26
27
28
tf
29
30
Jl
32
33
4c
Sponsor City
29
30
31
32
33
34
2:
36
37
38
39
40
4 ;
4.
4 >
44
.--
-,-
4
->•
Sponsor
Branch
Code
4T "~
I
.;•
—
Sponsor
Division
Code
i
>< ,. ,c
Sponsor State
Sponsor Zip/
Mail Code
3 .
j
4
J.
~±_
Sponsor
Laboratory Code
e
• f) (•'•
(,?
'.•
Sponsor Country
,t
J Project Officer Te ephone
*
1 1
30
Funding (K$)
3 24
25
26
27
28
29
30
31
32
33
34
Fiscal
Year
31
32
33
34
35
36
37
38| 39
1
40
Funding (K$)
35
36
37
38
39
40
4
Fisca 1
Year | Funding (KS)
Fiscal
Year
^'•M
61
62
63
•*
to
66
rm C
>mi
Dieted by
Project
Start Da
Mo 1 Da
c'U
69 /,!
Agency
Inventory Number
>•
CO
66
c.-
60
69
70
te
Yr
71 '2
1
D<
Pf
Mo
7i
•2
Pro
Fir
Mo
73
4
ite of
S Ent
Da
73
,~4
ject
ish D
Do
1
ry
Yr
ate
Yr
" 7t :?[>K
L ±
i>\ (»| ;*:eo
j J [
Contract No./Grant No.
Funding (K$)
58
5V
6C
61
62
63
Fiscal
Year
64
65
66
67
Funding (KS)
68 69
70
71
72 73
74
7S 74
77 78 7.9 80
Project Title
9 10
1 1
2 13
14
5 16
17
IB
9 20
21
22 2
3 24
25
26
27
28
29
30
31
32
33
34
3l
36
37
38
Contractor Name
9 Uj,
i 1
2 13
14 1
Contractor
Zip/Mail Code
9 10
II 1
Profile E
9 10 II 12
2 13
14 1
5 lo.
17
18 1
9 20
2
Contractor
lountry
5 16
17
18
9 20
21
22 2
3 24
2;
26
2:
2B
29
30
31
32
33
34
35
36
37
36
39
40 Ml
42
Contractor Street Address/P.O Box
39
40 4
42
4!
46
48
49
,0
5!
Contractor Project Manager
22 2
3 24
ement Code
r i i
13
M :
16/17
18 1!
20/71
22 2"
74
25
26
27
28
29
30
3!
32
J
25
26
27
28/29
30 31
32
33
34
35
36
33
34
35
16
37
38
39
40
37
38
39
40
41
42
43
44
J
41
42
43
44
4 j
46
47
48
45
46
47
40
4'J
.0
51
33
'2
73
74
.0 76
•-' 7b ' t
Contractor State — i
Contractor City I 1
oO
6l
t>4|:>;
66
=e
69
~c
'<
Contractor Project Manager Telephone
52
49
.'0
51
J2
,3
.4
1,3
54
55
:!
56
^.
58
39
60
1
jf
jt
59
60|6I |
1
0263 64
Jl:
62J63~y<>4]
a
6J
q
66
t
66
1 1 1
67
68
69
?j
"
~2
1
09
70
71
1
*]
73
"lipli;
IT
74
"h
/5J7
1
7717* "MBO
1 1.
-P
±J
SlOTf - When uncodiita data, use a 0 lot aloha cnorocter ond 0 for numeric zero. Paae 0|
ro
-------
&EPA EADS
U.S. ENVIRONMENTAL PROTECTION AGENCY
|[KL-KlP Kts«ucli Triangle Poik . N.C. 27711
PROJECT PROFILE SYSTEM
DATA INPUT FORMS
FORM 2
9/80
B - REFERENCE INFORMATION
Form Completed by
EADS
Profile
Numbe
I
r
"
Cord
No.
B 0
B 0 2
Card
No.
4789
B 0 3
Card
No.
6789
B 0 4
Card
No.
6789
B 0 1
& 0 I!
Card
No.
41] 11
BjOjJ
Card
No. J
mrrv »
>l°h
1 Report Sequence Number
* Report Title
10 II 12 13 1
Report A
" ± ~
Repc
Sponsor
10 11 12 13 14
Report Ti
10 II 12 11 14
4 15 I6|I7| IB) 19 20 21 22 23 24 25 26 27 It 29 30 31 32
I
Ill
>rt Sequence Number
uthors
r
i 1' 20 21 22 23 24 25 26 27 28 29 30 3> 31
rt Sequence Number
ieport Number N]
15 16 17
ie
19 20 21 22 23 24 25 26 27 28 29 30 31 11
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
48 49
50 51 s:
53 54 55 56 57
5* 59 60
61
62
63 64 65 U
13 34 35 36 37 38 19 40 4 42 43 44 45 46 47
18 49
SO 51 52
FIS Number R
33 34 3SJ 36 37 38 31 40 41 42 43 44 45 46 47 4
1
18 49
50 51 52
53 54 55 56 i
58 59 60
F
62
63 44 65 66
eport Published Date
53 54 55 56 57
58 59 6^
61
62
63 64 65 66
67 68 69 70 71 72 73 J
67 68 69 1 70 71 72 73 7
1
Issue Date
Mo Da Yr
67 68 69 70 7] 72 » 7
4 75 76 77 76 -"9 &C
4 ,'i 76 77 7« 79 80
i n H rr n /» w
rt Sequence Number
tie
15 16 17
ie
19 20 21 22 23 24 25 26 27 28 29 30 31 32 1
3 14 35 36 37 18 39 40 41 42 43 44 45 46 47 4J
9 49
^0 51 52
53 54 55 56 57
56 59 60
61
62
63 M 65 66
67 68 69 70 71 72 73 74
75 76 77 78 79 60
— • Report Sequence Number
Report Authors
10 II 12] 3JI4
D
15 6 17
Report Sequel
Sponsor Report Ni
10 II [ll 13 14
±
15 16 17
ia|l9 20 21 22 23 24 25 26 27 21 29 30 31 32 3.
J
tct
mb
II
Number
«r NT
19 20 21 22 23 24 25 26 27 28 29 10 31 32 33
] 34 35 36 37 36 39 40 4 1 42 43 44 45 46 47 41
i 49
50 5l|52
S Number ' ' R<
34 35 36 37 38 39 40 41 42 43 44 45 46 47 41
49
50 51 52
53 54 55 56 57
58 59 60
;port Published Dote
53 54 55 56 57
» 59 60)1
61
62
TTSTi
63 64 65 66
JJJW 65 66
TIM
67 68 69 70 71 72 73 74
Issue Date
Mo 1 Da I Yr
a 68[6S 70171 72 n M
1 (
75 76 77 78 79 80
71 76 77 7» 7*]»0
|
I
u>
NGT6: When encoding data, use afl for alpha character and 0 for numeric zero.
Poge of
-------
&EPA EADS
U.S. ENVIRONMENTAL PROTECTION AGENCY
IERL-RTP Reseorch Tiiongle Porl. N.C. 27711
PROJECT PROFILE SYSTEM
FORM 3
I2//9
DATA NPUT FORMS
C - PROFILE ABSTRACT
EADS
Prof il<
Numb
IF
1
er
T7!5
11
Card
No.
6 7j
C j
C
C
c .,
C
c
c :•
C j
C 0
c ;•
c o
c ~.
C j
j
C J
C 0
c :
C 0
c ;
C j
c ,
C 0
C 0
C 0
C 0
C 0
C 0
C 0
C 0
- o
a
;
1
1
II
I£J4
~nlL
o I
,"/••/
1
Line
No A
10
,!_ 12
Form Completed by
>stroct as Text
13 14
I
1
~
1
I
16 1
7 IB
19
20
1
-t
1
21
22
-
23
24 2
I
1
1
5 26
i
27
i
28
29
30
31
32
33
34
35
36
37
38
39
t
40
i
41
-
42
43
44
45
46
47
48
[
49 ]50
L
-H
51
"
_(..,
1
[
1
52
S3
i
1
1
-
54
-
50
56
!
-
^
1
57
-
58
59
\
60
61
-1
-
62
-
-
63
64
65
-
66
1
1
67
-
-
6B
-:
-1
t
'\
69
70
]
i
71
li
72
73
74
75
t
(
76
-
i
t
-
-1
-
77
7tl
[
— -f- »>
i L
n
bu
— i—
1
-•*-
_L
NOTE: When encoding dolo t/te o 0 lot alpha charactti and (l for numeric leio.
-------
r/EPA EADS
.S. ENVIRONMENTAL PROTECTION AGENCY
RL-RTP Re«arch triangle Park, N.C. 27711
PROJECT PROFILE SYSTEM
FORM 4
9/80
DATA NPUT FORMS
) - ACTIVITY LEVEL
EADS
Profile Cord Acliviij
Number No. No. Task Order,
^F
1
D 0
Card lAcfivitJ
No. JNo. 1 Primary Ac
< 7 «lt 13 IIJIZ fj M 11 1
Deal I
Activity
Start Date* 0
/T.D. Number Mo Da Yr M
t 17 II It M 11 Zl n 24 2i 1*]27 2*1*1031 1333»4»3*»»3t*04l4J 40 44 «! « 47 4» •» ]»>) S3 J
It
ivity Activity Frequent
t 17 14) l» 10 21 U » Z4 U 16 1? n » 36 31 31 a M 3S 3t V 3» J» 40 41 « 43 44 4i 41 47 41 » 10 St U 1
I Cord (Activity) 1
[No. f4o. 1 Source Nome | Activity Location
|l| t «]t Ift ll|l> 1} 14 15 1
laoiL ± :
Card lAclivitJ
No. .JNo. fSource Care
* 1 *[» 10 111 It U 14 15 U
D 0 «| |
Card Activit)f
No. No. 1 Procesi Type
1 J • t 10 III II 11 M 19 14
£°L- _L_
Cord lAclivit Line
No. No. No. Corrnne
t J f t It II 11 II 14 15 U
' J! *
C 04
C 0 6
C 0 o _i
C 0 6
C 0 o
[ 0 o
:7«
: o «
) a 6
i F i
ML" r
gory* Source Type* Proc
i;[ll It 1» }t U 73 J4 2i J4 J7 2» J» JO 31 31 30 14 B jt 37 3» J» 40 ttitn7innr4ni*nn n\n>
: ±
IN » ft » j# ^ •#» 41 •*? 4 « if # *"•' 4j^4» ii ii n » * » w '») i* >i ii
E:III^:I ^nx : ~-":"'~:
54US*17St»JD»IUUMUU
-------
EPA EADS
D) D
U.S. ENVIRONMENTAL PROTECTION AGENCY
IERL-RTP Research Triangle Park, N.C. 27711
PROJECT PROFILE SYSTEM
FORM 5
9/80
E -
UAIAINKUIhUKMi
CONTROL SYSTEMS DATA 1
EADS
Profile
Number
-
2
1
I
Card
No.
4
E
7
0
1
1
Activity
Number
»
10
11
Card |Ac ivity
No. |N umber
1
7
0
•iL
2|
10
II
Card (Activity
No. JNumbei
4
E
7
0
1 |9
3|
Card
No.
6
E
7
0
I
4
Card
No.
t
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
£
E
7
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
5
i
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
10
II
Test
ID
No.
11
1]
Project Topic
14
15
It
17
It
n
20
71
2}
2;
24
Ji
26
27
21
Methods
2»
30
31
3]
33
34
35
36
Test
ID 1
No. I Issues
12
I3[l4
Test
ID
No
12
1]
Test
ActivilyJlD
Number) No.
9
10
Il|l2
Activity
Number
9
10
II
1}
Test
ID
No.
12
13
15
It
17
II
Media"
4
15
14
17
IB
19
20
21
n
21
24
25
It
27
28
29
30
31
32
33
34
3S
3*
37
31
3*140
Approach
37
31
»
40
41
4)
42] 43
1
42
441 451 16147
i_U
<3] 44 Us
46
4S
49
50
5,1
5jTs3
Form Completed by
54
47
48
«|50J5l|i2
Pollutant Control Generic Device* I Pollutant Control Design Type
19
20
21
n
23
21
25
26
27
21
29
30
31
32
33
34
15
3*
37
3*1 39
•so
41
4J
43
44
4SI44J47
Pollutant Control Process*
14
15
Line
No.
14
15
16
17
II
1»
20
21
22
23
24
25
26
27
21
29
30
31
32
13
34
35
14
37
31
39
40
41
12
43
44J 45
L
46
48
11
LiJ
•
50
il
53
53
S3
54
55
56
57
51
5»
60
61
a
6)
64
a
66
67
61
69
7
61
62
63
64
65
66
67
61
69
70
71
7J
n
74
75
76
77
7»
7»
n
S4|55
\ 1 1
56
5?
56
5»
60
61
62
63
64
65
66
67
68
69
?o[^
n
T\
?4
»
»»
7?
7»p»S
47
41
49
50
SI
52
i3
54
55
56
57
58
59
60
61
62
6J
64
65
66
6/
68
69
70
71
n
73
74
75
76
77
71
79
BO
Test Comments
16
17
II
IV
20
21
22
21
24
25
26
27
21
29
30
31
32
33
34
35
16
17
31
39
40
41
42
43
44
45
46
47
48
49
-
X
SI
S2
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
7
n
n
74
75
74
77
Tt
79
Si
I
ON
* Denotes Repetitive Data Feature
NOTE: When encoding data, use a0 lor alpha character and 0 for numeric zero.
Page of _
-------
&EPA EADS
u.s. ENVIRONMENTAL PROTECTION AGENCY
URL-RIP Reveoich Mangle Pa.k. NX. 27711
PROJECT PROFILE SYSTEM
DATA INPUT FORMS
FORMS
9/80
f - ANALYSIS LEVEL
Foim Completed by
•^J
EADS Test
Profile Card Activity I.D
Number No. Number No.
1 2
1
3 4 ; c 7 9 9 10 II 12 13
F 0 1
Tesr
Card A.ctivi Jl.D,
No. NumberlNo.
6 7 B 1 10 I|||2 13
f 0 2 \
lea
Card *iclivil/ I.D.
No. Number No.
f 0 3
F 0 3
f 0 3
f 0 3
F 0 3
F 0 1"
F 0 3
f 0 3
F 0 3
Te.r
Card Uctivil I.D.
No. Numbei No.
c i t t it i i. i:
F 0 4
F 0 4
F 0 4
F 0 4
F 0 4
0 4
F 0 4
F J 4
F 0 4
> '
p Analys s No.
1 i— Anaiytis Designation *
* * Analysis Location*
l« 15 It 17 IB If 20 21 22 2] 24 25 ?6J27 2t W 30 31 32 33 M 3i|jd 37 M 39 40 41 42 43 44 4i 46 47 48 49 bO
x ±: ~
rAnal^is No.
Veil Description*
H 15 16 17 18 19 20 21 22 23 24 2i] 2« 27 28 29 JO 31 32J33 34 35 3* 37 38 39 40 41 42 43 44 41 46 47 48 4f 50
IE ±
rAnalysii No.
f- Serial No.
Test Slroins/Orgonisim/Ecosystems*
U 15 16 17 18 » 2O 21 23 23 24 25 26 27 28 2» 30 11 32 33 14 35 36 37 38 39 40 41 12 43 44 45 46 4.- 48 49 X
rAnalysii No.
Line
No. Analysts Comments
Test Type*
SI 52 53 54 $5 56 57 5* 59 60 61 63 63 64 65 66 67 68 69 7(f 71 72 73 74 75 76 /7 7fi '9
31 52 53 54 55 56 57 5« 59 40 4 4? 63 64 65 66 67 A8|69 70J7||72J73 74 75 76 77 ,'6 ~9
";:." : 1 1 1 1
SI 52 S3 54(55 5* 57 SB 59 60 61 62 63 44 43 45 47 88 69 70 71 72 ?3 74 75 74 77 78 !9 iJ
.
5; i: i. I! 31 S: 51 5' * 61 6. 6: * »! 4 67 6 6( « 71 7 ?! 7. 7: 76 .' ' /. '' f
-
•Denolei Repetitive Data Feat
NOTE: When encoding auto
u&e a 0 for alpha character and 0 For numeric zero.
Page of
-------
oEPA EADS
U.S. ENVIRONMENTAL PROTECTION AGENCK
IlKL-RJP Research Triangle Park. N.C. 2/711
PROJECT PROFILE SYSTEM
FORM 7
9/80
DATA INPUT FORMS Techni'oe
G - POLLUTANT LEVEL Code*
EADS Te
Profile Cord ^ctivil; 1.
Number No. No. Nc
'IN
3| 4| 5 6 7 8 9 10 II 12
_lLl_L_Gof- 7
1
0 ]
G 0 1
G ( I
5 I
G 0 I
G 0 1
G 0 1
; C 1
G 0 I
G fj
-------
APPENDIX A.5
TABLES OF STANDARD NOMENCLATURE
A.5-1
-------
TABLE A.5.1 - PROJECT TYPE CODES
ENCODE PROJECT TYPES
01 FUELS
02 SAMPLING AND ANALYSIS
03 EMISSIONS/EFFLUENTS MONITORING
04 CONTROLS
05 TRANSPORT, TRANSFORMATION, AND FATE
06 HEALTH EFFECTS
07 ECOLOGICAL EFFECTS
08 INTEGRATED ASSESSMENT
09 SOCIOECONOMIC FACTORS
A.5-2
-------
TABLE A.5.2 - STANDARD ABBREVIATIONS AND SYMBOLS
ENCODE DEFINITION
& AND
LAB LABORATORY
FD FOUNDATION
NATL NATIONAL
ST STATE
SW SOUTHWEST
NW NORTHWEST
SE SOUTHEAST
NE NORTHEAST
MED MEDICINE
RAD RADIATION
BIOL BIOLOGY
ECOL ECOLOGY
ENV ENVIRONMENTAL
RES RESEARCH
POLL POLLUTION
CORP CORPORATION
CO COMPANY
TECH TECHNOLOGY
SCI SCIENCE
DEPT DEPARTMENT
UNIV UNIVERSITY
A.5-3
-------
TABLE A.5.3 - PROFILE ELEMENT CODES
CODE DESCRIPTION
AOOO COMBUSTION PROCESSES AND EFFLUENT CHARACTERIZATION
A100 COMBUSTION PROCESSES TECHNOLOGY CHARACTERISTICS
Alll UTILITY SECTOR
A112 INDUSTRIAL SECTOR
A113 COMMERCIAL OR INSTITUTIONAL SECTOR
A114 RESIDENTIAL SECTOR
A120 PROCESS STATE-OF-THE-ART OVERVIEW
A130 PROCESS ECONOMICS
A140 PROCESS ENERGY BALANCE
A200 FUELS CHARACTERIZATION
A210 TYPE AM) SOURCE OF FUELS
A220 PHYSICAL PROPERTIES OF FUELS
A230 CHEMICAL ANALYSIS OF FUELS
A240 ENERGY CONTENT OF FUELS
A250 PREPARATION AND/OR BENEF1CIATION OF FUELS
A260 AVAILABILITY OF FUELS
A300 INPUT-OUTPUT CHARACTERIZATION
A311 MATERIAL BALANCE COMBUSTION PROCESS
A312 MATERIAL BALANCE CONTROL PROCESS
A320 STEADY-STATE POLLUTANT LOADINGS
A330 TRANSIENT OPERATION POLLUTANT LOADINGS
A340 FUGITIVE EMISSION POLLUTANT LOADININGS
A400 FIELD TESTS AND SURVEYS
A410 COMBUSTION PROCESS TESTING
A420 CONTROL SYSTEMS TESTING
A430 WASTE STREAM CHARACTERIZATION
A431 LEVEL 1- SAMPLING AND ANALYSIS
A432 LEVEL 2- SAMPLING AND ANALYSIS
A433 LEVEL 3- SAMPLING AND ANALYSIS
A434 EPA STANDARD PROCEDURES
A435 CONTINUOUS MONITORING
A436 OTHER - SAMPLING AND ANALYSIS (SPECIFY):
A437 MEASUREMENT QUALITY ASSURANCE
A500 DEVELOPMENT OF SAMPLING AND ANALYSIS TECHNIQUES
A510 SAMPLING TECHNIQUES DEVELOPMENT
A520 ANALYTICAL TECHNIQUES DEVELOPMENT
A530 BIOASSAY TECHNIQUES DEVELOPMENT
A540 CONTINUOUS MEASUREMENT DEVELOPMENT
BOOO CONTROL TECHNIQUES EVALUATION
B100 CONTROL SYSTEMS EVALUATION
B110 RESEARCH AND DEVELOPMENT
B120 FULL-SCALE DEMONSTRATION
B130 ECONOMICS
B140 ENERGY REQUIREMENTS
A.5-4
-------
TABLE A.5.3 - PROFILE ELEMENT CODES (Continued)
CODE DESCRIPTION
B150 POLLUTANT REMOVAL EFFICIENCY
B160 AVAILABILITY
B200 CONTROL SYSTEMS ENVIRONMENTAL IMPACT
B210 WASTE DISPOSAL OPTIONS
B220 SECONDARY ENVIRONMENTAL IMPACTS
B230 CROSS-MEDIA IMPACTS
B240 SOURCE ANALYSIS MODELS (SAM)
B300 CONTROL ALTERNATIVES
B310 ADD-ON DEVICES
B320 COMBUSTION MODIFICATION
B330 FUEL SWITCH/MIXING
B400 CONTROL TECHNOLOGY DEVELOPMENT RECOMMENDATIONS
B410 TECHNOLOGY MODIFICATION
B420 QUANTIFIED R&D NEEDS
B430 CRITERIA FOR PRIORITIES
B440 RECOMMEND SCHEDULE FOR DEVELOPMENT
COOO HEALTH AND ECOLOGICAL IMPACTS EVALUATION
C100 ECOLOGICAL IMPACT
C110 AIR, WATER AND LAND QUALITY CRITERIA
C120 QUANTIFIED MEDIA DEGRADATION
C130 LABORATORY FLORA STUDIES
C140 FIELD FLORA STUDIES
C150 LABORATORY FAUNA STUDIES
C160 FIELD FAUNA STUDIES
C200 BIOASSAY EVALUATION
C210 CRITERIA DEVELOPMENT
C220 TECHNIQUES DEVELOPMENT
C230 LABORATORY STUDIES
C300 DOSE-RESPONSE DATA
C310 THRESHOLD LIMIT VALUES (TLV)
C320 CHRONIC EXPOSURE EFFECTS
C330 ACUTE EXPOSURE EFFECTS
C400 EPIDEMIOLOGICAL DATA
C410 INDUSTRY-RELATED HEALTH DATA
C420 MORBIDITY CORRELATION STUDIES
C430 MORTALITY CORRELATION STUDIES
DOOO QUANTIFY POLLUTION IMPACTS
D100 TRANSPORT, TRANSFORMATION AND FATE
DUO METEOROLOGICAL AND HYDROLOGICAL DATA
D120 MODEL DEVELOPMENT
D130 TRANSFORMATION CHEMISTRY
D140 EXPOSURE LEVEL CALCULATIONS
D150 AMBIENT POLLUTANT CONCENTRATION MEASUREMENTS
D200 TOTAL POLLUTANT LOAD CALCULATIONS
D210 PROCESS LOADING (STATIONARY)
D220 OTHER SOURCE LOADING (FOR EXAMPLE, MOBILE SOURCES)
A.5-5
-------
TABLE A.5.3 - PROFILE ELEMENT CODES (Concluded)
CODE DESCRIPTION
D230 NATURAL BACKGROUND
D300 SYNERGISTIC AND MULTIMEDIA IMPACTS
D310 MULTIMEDIA POLLUTANT DISTRIBUTION
D320 ADDITIVE, TRANSFORMATION AND ENHANCEMENT EFFECTS
D400 POLLUTANT PRIORITY RANKING
D410 TOTAL POLLUTANT LOAD
D420 DEGREE OF HAZARD (SEVERITY INDICES)
D500 COMBUSTION PROCESS USE PROJECTIONS
D510 CURRENT MARKET SIZE
D520 FUTURE MARKET PROJECTIONS
D530 FUEL SUPPLY/DEMAND PROJECTIONS
D540 DEMOGRAPHIC AND LAND USE PATTERNS AND TRENDS
EOOO ENVIRONMENTAL GOALS AND OBJECTIVES DEVELOPMENT
E100 EXISTING POLLUTANT LEVELS
E200 EMISSION OR AMBIENT LEVEL GOALS
E210 EST OF PERMISSIBLE POLLUTANT CONG (AIR, WATER, OR LAND)
E220 CRITERIA FOR ESTABLISHING PRIORITIES
E230 CONTROL TECHNOLOGY LIMITATIONS
E240 MINIMUM ACUTE TOXICITY EFFLUENT
E300 SOCIAL, ECONOMIC, POLITICAL,
E310 NON-POLLUTANT GOALS
E320 QUANTIFIED NON-POLLUTANT IMPACTS
E330 SITING CRITERIA
E340 CRITICAL MATERIALS IMPACTS
E400 STATUTORY CONTRAINTS
E410 FEDERAL/STATE STANDARDS AND REGULATIONS
E420 RESEARCH DATA BASE FOR STANDARDS
E500 STANDARDS DEVELOPMENT RECOMMENDATIONS
E510 STANDARDS MODIFICATIONS
E520 STANDARDS DEVELOPMENT
E530 CRITERIA FOR PRIORITIES
E540 RECOMMENDED SCHEDULE
A.5-6
-------
TABLE A.5.4 - PRIMARY ACTIVITY NOMENCLATURE
COLLECTION
EVALUATION
QUAL ANALYSIS
QUANT ANALYSIS
STANDARDIZATION
SURVEY REPORT
TECHNIQUE DEV
A.5-7
-------
TABLE A.5.5 - ACTIVITY FREQUENCY NOMENCLATURE
CONTINUOUS
GRAB
INTERMITTENT
A.5-!
-------
TABLE A.5.6 - FEED MATERIAL TYPE NOMENCLATURE
PULVERIZED
CRUSHED
STOKER
LIGNITE
NATURAL
SYNTHETIC
DIESEL
DISTILLATE
RESIDUAL
GASOLINE
KEROSENE
RESIDENT
COAL/MSW
COM/OIL
A.5-9
-------
TABLE A.5.7a - METHODS NOMENCLATURE FOR SAMPLING AND
ANALYSIS PROJECT TYPES
AA
AMBIENT AIR MONITORING ANALYZERS
ANODIC STRIPPING VOLTAMETRY
A/D CONVERTER
BACK SCATTER DEPOLARIZATION ANALYSIS
BALLOONS
BAROMETERS, SOLID STATE
BOUNDARY LAYER DILUTION PROBE
CAMERA TUBES
CATHODIC STRIPPING VOLTAMETRY
CHEMILUMINESCENCE TECHNIQUES
COLORIMETRY
CONTACT ELECTRICAL TECHNIQUES
CONTROL TECHNOLOGY EVALUATION
CONTROLLED TEMPERATURE SAMPLER
CONTROLLED CONDENSATION METHODS
CRYOCONDENSATION
DEWPOINT MONITOR
DICHOTOMOUS SAMPLER
DICHOTOMOUS VIRTUAL IMPACTOR
DIFFUSED SCRUBBER
DIFFUSION PROCESSOR
DIFFUSION SAMPLING TECHNIQUES
DIFFUSION TUBE SCRUBBER
DIONEY ION CHROMATOGRAPHY
DIRECT INLET MASS SPECTROSCOPY
DYE LASER TECHNIQUES
ELECTRON CAPTURE GAS CHROMATOGRAPHY
ELECTRON DIFFRACTION TECHNIQUES
ELECTRON MICROPROBE
EPA REFERENCE METHOD 5
ESCA
EXTRACTIVE IMPACTOR
FI
FILTERS
FILTERS, AgNOs TREATED
FILTERS, LiOH TREATED
FILTERS, MICROSCORBAN
FILTERS, NUCLEOPORE
FILTERS, POLYCARBONATE
FILTERS, TEFLON
FLAME PHOTOMETRIC DETECTOR
FLAMELESS ATOMIC ABSORPTION SPECTROPHOTOMETRY
FLUORESCENCE TECHNIQUES
FT
GAS ANALYZER
A.5-10
-------
TABLE A.5.7a - METHODS NOMENCLATURE FOR SAMPLING AND
ANALYSIS PROJECT TYPES (Continued)
GAS PHASE SULFURIC ACID GENERATOR
GC
GC-EC
GC-MS
HIGH RESOLUTION GAS CHROMATOGRAPHY
HIGH RESOLUTION MASS SPECTROSCOPY
HIGH VOLUME CASCADE IMPACTOR
HOLOGRAPHY
HOT WIRE TECHNIQUES
HPLC
HYDRIDE GENERATION-FLAME ATOMIC ABSORPTION SPECTROSCOPY
HYGROMETER, SOLID STATE
IMAGE ANALYSIS TECHNIQUES
IMPACTOR TECHNIQUES
IMPINGERS
INFRARED TECHNIQUES
INORGANIC ANALYSIS
INSTRUMENT SURVEY
ION EXCHANGE CHROMATOGRAPHY
ION MICROPROBE
ION PAIR DETECTION
IR
ISOPROPANOL ABSORPTION METHOD
LASER DOPPLER VELOCIMETER
LASER-RADAR TECHNIQUES
LC-MS
LIDAR
LIGHT AMPLIFIERS
LIGHT SCATTERING SPECTROMETRY
LIQUID CRYSTAL GAS CHROMATOGRAPHY
LITERATURE SURVEY
LONG PATH HIGH RESOLUTION INFRARED SPECTROSCOPY
LOW RESOLUTION MASS SPECTROSCOPY
MACRORETICULAR SORBENT RESINS
MASS EMISSION RATE MONITOR
METABOLIC BALANCE
METEOROLOGY
METHYLTHYMOL BLUE METHOD
MICROCOMPUTER
MICROWAVE RESONANCE SPECTROSCOPY
MICRO-RAMAN SPECTRA
MODELING
MS
MULTIDETECTOR ARRAYS
A.5-11
-------
TABLE A.5.7a - METHODS NOMENCLATURE FOR SAMPLING AND
ANALYSIS PROJECT TYPES (Continued)
NEPHELOMETRY
NMR
NONEXTRACTIVE ELECTRO-OPTICAL INSTRUMENT
NUCLEAR GAMMA RAY SPECTROSCOPY
OPTICAL ABSORPTION TECHNIQUES
OPTICAL EMISSION SPECTROSCOPY
OPTICAL INSTRUMENTATION
OPTO-ACOUSTIC TECHNIQUES
ORGANIC ANALYSIS
OXIDATION TECHNIQUES
PARR ACID DIGESTION BOMB PRETREATMENT TECHNIQUE
PARTICULATE SULFUR ANALYZER
PH MONITOR
PHOTOELECTRON SPECTROMETRY
PIEZO-ELECTRIC MICROBALANCE
PLASMA SOURCE EMISSION SPECTROMETRY
PLUME OPACITY INSTRUMENTS
POLARIZED LIGHT MICROSCOPY
PROTON BEAM-PROTON SPECTRA
PROTOTYPE
PULSED FLUORESCENCE MONITOR
RADIONUCLIDE MEASUREMENTS
RAMAN SCATTERING
RAYLEIGH SCATTERING
SAMPLE HANDLING EVALUATION
SAMPLING EVALUATION
SASS LEVEL 1 ANALYSIS
SCANNING COULOMETRY
SCANNING ELECTRON MICROSCOPY
SEDIMENT CORES
SELECTIVE SOLUBILITY
SERIES CYCLONE
SHAPE SENSITIVE AEROSOL PATICLE SIZE SPECTROMETRY
SIMULATION TECHNIQUES
SOLID SORBENTS
S03 ANALYSIS
SPECIFIC ION ELECTRODE
SPECTRAL ANALYSIS
SPECTROSCOPY
STANDARD METHODS EVALUATION
SULFURIC ACID MIST MONITOR
SUN PHOTOMETER
TAPERED ELEMENT OSCILLATING MICRO BALANCE
TEC
A.5-12
-------
TABLE A.5.7a - METHODS NOMENCLATURE FOR SAMPLING AND
ANALYSIS PROJECT TYPES (Continued)
TECHNICAL MANUAL DEVELOPMENT
TECHNIQUES DEMONSTRATION
TELEPHOTOMETERS
TELEVISION TECHNOLOGY
TETHERSONDE
THIN LAYER CHROMATOGRAPHY
TOC-COD
TRANSMISSION ELECTRON MICROSCOPY
TRANSMISSOMETER
TRANSMISSOMETER, FOUR WAVELENGTHS
TRANSMISSOMETER, TWO WAVELENGTHS
TUNDGREN IMPACTORS
TURBIDIMETRY
UV
VERTICAL IMPACTOR
VOLTAMETRIC METHODS
WIND TUNNEL ANALYSIS
X-RAY ABSORPTION
X-RAY DIFFRACTION
X-RAY EXCITED OPTICAL LUMINESCENCE
X-RAY FLUORESCENCE
X-RAY TECHNIQUES
AIRCRAFT ASSISTED TECHNIQUES
ATMOSPHERIC STUDIES
BALLOON ASSISTED TECHNIQUES
BASELINE DATA
BIOGEOCHEMISTRY
CHEMICAL-METEOROLOGICAL DATA
CLIMATOLOGY
CORING TECHNIQUES
ELECTRON SPECTROSCOPY
FIELD STUDY
GAS PHASE TITRATION
GEOCHEMICAL STUDY
IMPROVED CALIBRATION TECHNIQUES
IN SITU MEASUREMENTS
KINETICS STUDY
LABORATORY ANALYSIS
LITERATURE SURVEY
MASS SPECTROSCOPY
METEOROLOGY
MICROMETEOROLOGY
A.5-13
-------
TABLE A.5.7a - METHODS NOMENCLATURE FOR SAMPLING AND
ANALYSIS PROJECT TYPES (Concluded)
MOBILE GROUND UNITS
MODELING
MOMENTUM TRANSFER STUDIES
PHOTOCHEMICAL STUDIES
PHOTOMETER
RADIONUCLIDE MEASUREMENTS
SMOG CHAMBER
STATISTICAL ANALYSIS
TOPOGRAPHY
WET/DRY FALLOUT COLLECTORS
WIND TUNNEL ANALYSIS
A.5-14
-------
TABLE A.5.8a - ISSUES NOMENCLATURE FOR INTEGRATED ASSESSMENT
PROJECT TYPES
AESTHETICS
AMBIENT AIR DATA
BIOMEDICAL EFFECTS
COAL TECH ASSESSMENT
COMPARATIVE ASSESSMENT
CONTROL TECHNOLOGY
DEMOGRAPHIC FACTORS
ECOLOGICAL FACTORS
ECONOMIC FACTORS
EMISSIONS DATA
ENERGY USE
ENVIRONMENTAL ASSESS
HUMAN HEALTH
INSTITUTIONAL FACTORS
LAND USE
LEGAL FACTORS
POLITICAL FACTORS
POLLUTANT DISTRIBUTION
RADIOACTIVE WASTES
REGULATORY FACTORS
SOCIAL FACTORS
SOCIOECONOMIC FACTORS
TECHNICAL FACTORS
TRANS TRANSF FATE
WATER USE
A.5-15
-------
TABLE A.5.8b - SCO (ECONOMIC PROJECT TYPES
AESTHETICS
BIOINDIGATORS
CULTURAL FACTORS
DEMOGRAPHIC FACTORS
ECOLOGICAL FACTORS
ECONOMIC FACTORS
ENERGY USE
ENVIRONMENTAL ANALYSIS
HUMAN HEALTH
IMPACT ASSESSMENT
INSTITUTIONAL FACTORS
LAND USE
LEGAL FACTORS
POLITICAL FACTORS
RECREATIONAL FACTORS
REGULATION DEV
REGULATORY FACTORS
SOCIAL IMPACT
SOCIOECONOMICS
WATER USE
A.5-16
-------
TABLE A.5.9a - APPROACH NOMENCLATURE FOR INTEGRATED ASSESSMENT
PROJECT TYPES
CASE STUDIES
CHEMICAL ANALYSIS
DATA ANALYSIS
DATA BASE ESTAB
DATA BASE MAINT
DATA COLLECTION
EPIDEMIOLOGY
FIELD STUDIES
INFORMATION SYST
LITERATURE SURVEY
MAIL SURVEYS
METHODS DEV
MODEL ANALYSIS
MODEL ADAPTATION
MODEL DEVELOPMENT
QUAL EVALUATION
QUANT EVALUATION
RECORDS SURVEY
REPORT GENERATION
STATISTICAL ANAL
TELEPHONE SURVEYS
TECH ASSESSMENT
WORK PLAN
A.5-17
-------
TABLE A.5.9b - APPROACH NOMENCLATURE FOR SOCIOECONOMIC
PROJECT TYPES
CASE STUDIES
COMPUTER GRAPHICS
CONFERENCE
DATA ANALYSIS
DATA BASE ESTAB
DATA BASE MAINT
DATA COLLECTION
ENERGY MODELS
ENGINEERING EVAL
FIELD STUDIES
INFORMATION SYST
INTERVIEWS
LITERATURE SURVEY
METHODS DEV
MODEL ADAPTATION
MODEL ANALYSIS
MODEL DEVELOPMENT
QUAL EVALUATION
QUANT EVALUATION
RECORDS SURVEY
REMOTE SENSING
REPORT GENERATION
SITE VISITS
SLUDGE STUDY
STATISTICAL ANAL
SURVEYS
A.5-18
-------
TABLE A.S.lOa - FACTORS NOMENCLATURE FOR INTEGRATED ASSESSMENT
PROJECT TYPES
ALTERNATIVE STRATEGY DEV
ENERGY PLANNING
ENERGY POLICY
ENERGY SUPPLY
ENVIRONMENTAL POLICY
ENVIRONMENTAL QUALITY
GOVERNMENT PLANNING
GOVERNMENT COORDINATION
GOVERNMENT POLICY
IMPACT IDENTIFICATION
LOCAL DEVELOPMENT
MANPOWER UTILIZATION
MITIGATION PLANNING
POLLUTION ABATEMENT
R & D POLICY
REGIONAL DEVELOPMENT
REGIONAL POLICY
RESOURCE UTILIZATION
SITE SELECTION
SOCIAL IMPACTS
A.5-19
-------
TABLE A.S.lOb - FACTORS NOMENCLATURE FOR SOCIOECONOMIC
PROJECT TYPES
AGRICULTURAL IMPACTS
ALTERNATIVE STRATEGY DEV
CULTURAL IMPACTS
ECONOMIC ASSESSMENT
ENERGY SUPPLY
GOVERNMENT COORDINATION
GOVERNMENT POLICY
IMPACT IDENTIFICATION
LOCAL DEVELOPMENT
LOCAL PLANNING
MITIGATION PLANNING
PLANNING
POLICY ALTERNATIVES
PUBLIC ATTITUDES-VALUES
REGIONAL DEVELOPMENT
RESOURCE UTILIZATION
SITE SELECTION
SOCIAL IMPACTS
WASTE DISPOSAL
WASTE UTILIZATION
A.5-20
-------
TABLE A.5.11 - MEDIA NOMENCLATURE
GAS
LIQUID
SOLID
A.5-21
-------
TABLE A.5.12a - TEST TYPE NOMENCLATURE FOR BIOLOGICAL
PROJECT TYPES
ACUTE EXPOSURE
ACUTE-CHRON EXPOSURE
ANTIOXIDANT POTENTIAL
BEHAVIOR RESPONSE
BIOASSAY DEVELOPMENT
BIOCHEMISTRY
BIOLOGICAL UPTAKE
BODY BURDEN
CARCINOGENICITY
CHRON EXPOSURE
CHARACTERIZATION STUDY
CO-CARCINOGENICITY
CYTOTOXICITY
DOSE RESPONSE
EPIDEMIOLOGY
GENETIC EFFECTS
HEALTH EFFECTS
IMMUNE RESPONSE
INTERMOLECULAR REACTIONS
IRRITANT POTENTIAL
METABOLIC STUDY
MOLECULAR TOXICOLOGY
MORPHOLOGICAL EFFECTS
MUTAGENICITY
MODELING
NEUROPHYSIOLOGIC RESPONSE
ONCOGENICITY
OXIDATIVE MECHANISM
PHYSIOLOGIC EFFECTS
PRESCREENING ASSAY DEV
SUBACUTE EXPOSURE
SUBLETHAL EXPOSURE
TERATOGENICITY
TOXICITY
A.5-22
-------
TABLE A.5.12b - TEST TYPE NOMENCLATURE FOR ECOLOGICAL
PROJECT TYPE
ACUTE-SUBLETHAL EXPOSURE
ACUTE-CHRON EXPOSURE
ACUTE-SUBACUTE EXPOSURE
AMBIENT EXPOSURE
BIOACCUMULATION
BIOLOGICAL IMPACT
BODY BURDEN
CARCINOGENICITY
CHARACTERIZATION STUDY
CHRON EXPOSURE
CHRON-SUBLETHAL EXPOSURE
DOSE RESPONSE
ECOLOGICAL IMPACT
ENERGY-RELATED DEV
ENVIRONMENTAL IMPACT
IMPINGEMENT STUDY
INTERMITTENT EXPOSURE
METABOLIC STUDY
MODELING
MUTAGENICITY
PHYSIOLOGIC EFFECTS
PRODUCTIVITY EVALUATION
RESISTIVITY
SUBACUTE EXPOSURE
TEMPERATURE SHOCK
TERATOGENICITY
THERMAL STRESS
TOXICITY
A.5-23
-------
TABLE A.5.13a - TEST DESCRIPTION NOMENCLATURE FOR BIOLOGICAL
PROJECT TYPES
ACUTE CHRONIC EXPOSURE
AEROSOL GENERATION TECHNIQUES
AHH INDUCIBILTTY
ALA-PBB ANALYSIS
AMES TEST
ANTIBODY TITRATION
ANTIGEN RESPONSE
ATP CONCENTRATION
AUTORADIOGRAPHY
AUTOPSY
BASELINE DATA DEV
BEHAVIORAL ANALYSIS
BIOCHEMICAL CRITERIA DEV
BIOINDICATOR DEV
BIOLOGICAL MODELS
CARDIOPULMONARY EFFECTS
CELL DIFFERENTIATION
CELLULAR ADAPTATION
CFU TECHNIQUES
CHEMICO-PHYSICAL ANALYSIS
CHEMILUMINESCENCE
CHEMOTACTIC ABILITY
CHROMOSOMAL ABNORMALITIES
CLARK OXYGEN ELECTRODE
COLLAGEN-ELASTIC INDUCTION
COLONY FORMING ABILITY
CONTROLLED RELEASE TECHNIQUES
CORD
CRITICAL ION ANALYSIS
CYTOCHROME P-450 ACTIVITY
CYTOLOGICAL CRITERIA DEV
CYTOPATHOLOGICAL CRITERIA DEV
DEFENCE REACTIONS
DEN RESPONSE
DESENSITIZATION ANALYSIS
DNA POLYMERASE INHIBITION
DOMINANT LETHAL TEST
DOSE-RESPONSE
DOUBLE BLIND STUDY
DROSOPHILA TEST SYSTEM
ELECTRON MICROSCOPY
ELECTRON PROBE MICROANALYSIS
ELECTRON SPIN RESONANCE
ENDOGENOUS TUMOR VIRUS
A.5-24
-------
TABLE A.5.13a - TEST DESCRIPTION NOMENCLATURE FOR BIOLOGICAL
PROJECT TYPES (Continued)
ENDONUCLEASE ASSAY DEV
ENZYME ASSAY
ENZYME INDUCTION
ENZYME ACTIVITY
ENZYME/TRACER METHODS
EPITHELIAL SCREENING TEST
EXERCISE EFFICIENCY
FEASIBILITY ANALYSIS
FLOW RESISTANCE MEASUREMENTS
FLUORESCENCE TECHNIQUES
FLUORESCENT ANTIBODY TECHNIQUES
GENE MUTATIONAL ASSAY
GERM CELL LETHALITY
GLUCAGON BINDING
GROWTH HORMONE ANALYSIS
GUT LAVAGE
HEMATOPOIESIS
HERITABLE TRANSLOCATION TEST
HISTOLOGICAL TECHNIQUES
HISTONE KINASE ACTIVITY
HISTOPATHOLOGICAL CRITERIA DEV
HISTOPATHOLOGICAL TEST
HOLLOW FIBER DIALYSIS
HORMONE SYNTHESIS
HOST-PARASITE RESPONSE
HUMORAL RESPONSE
HYPERTENSIVE RESPONSE
IMMUNOCOMPETENCE
IMMUNOGLOBULIN RESPONSE
INDICATOR DEV
INFORMATION SYSTEM
INHALATION CHAMBERS
INTERFERON PRODUCTION
INTRANASAL HOMEOSTASIS
INTRATRACHEAL INJECTION
IN VITRO CELL TRANSFORMATION
KARYOTYPE ANALYSIS
KINETIC MODEL
LATENCY DETERMINATION
LESION FORMATION
LIPID PEROXIDATION
LITERATURE SURVEY
LIVE HUMAN EXPOSURE
A.5-25
-------
TABLE A.5.13a - TEST DESCRIPTION NOMENCLATURE FOR BIOLOGICAL
PROJECT TYPES (Continued)
LONGEVITY
MACROMOLECULAR BINDING
MACROPHASE MIGRATION
MAGNETIC RESONANCE
MEMBRANE BINDING
METABOLIC ACTIVATION BIOASSAY
METABOLISM INTERFERENCE
METABOLITE ASSAY
MICROBE MUTATION
MITOGEN RESPONSE
MOBILIZATION STUDY
MODELING
MORBIDITY-MORTALITY
MORPHOMETRIC ANALYSIS
MORTALITY
MULTIGENERATIONAL EXPOSURE
NEFA-INDUCED LESION
NEOPLASTIC CELL TRANS ASSAY
NITROGEN INDUCED TRANSFORMATION
NONINVASIVE TECHNIQUES
NORADRENALINE BINDING
NO-EFFECT LEVEL
NUCLEIC ACID RESPONSE
NUCLEOSIDE REACTIVITY
NUTRIENT ABSORPTION ANALYSIS
OCCUPATIONAL EXPOSURE
OLFACTORY FUNCTION
OXIDANT-ANTIOXIDANT ACTIVITY
PARTICULATE DEPOSITION
PATHOLOGICAL EFFECTS
PATHOPHYSIOLOGICAL ANALYSIS
PHAGOCYTIC ABILITY
PHARM BLOCKING ABILITY
PHOSPHOLIPID BINDING
PHYSIOLOGICAL INDICES
PLETHYSMOGRAPH
PNEUMONECTOMY
POLLUTANT TRANSPORT
PRECURSOR INCORPORATION
PROLIFERATIVE CAPACITY
PROMOTOR ANALYSIS
PROTEIN SULFHYDRYL LEVEL
PROTEIN SYNTHESIS
PROTON INDUCED X-RAY EMISSION
A.5-26
-------
TABLE A.5.13a - TEST DESCRIPTION NOMENCLATURE FOR BIOLOGICAL
PROJECT TYPES (Concluded)
PROTOZOAN SCREENING TEST
PSYCHOPHYSIOLOGICAL ANALYSIS
PSYCHOLOGICAL EFFECTS
PULMONARY CLEARANCE MECHANISM
RADIOCHEMICAL ANALYSIS
RADIOIMMUNOASSAY
RADIOLABLE ASSAY DEV
RADIONUCLEI PROBE
RAM
RENIN-ANGIOTENSIN ACTIVITY
REPRODUCTIVE PERFORMANCE
RISK ASSESSMENT
SCANNING ELECTRON MICROSCOPE
SCREENING TEST DEV
SEA URCHIN EMBRYOGENIC ASSAY
SENSITIVITY ANALYSIS
SPIROMETRY
STATISTICAL MODEL
STEROL HYDROPEROXIDE ANALYSIS
STOMATIC EFFECTS
SUBJECTIVE PERCEPTION INDEX
SULFITE OXIDASE ASSAY
SYNAPTOGENESIS
SYNERGISTIC EFFECTS
TERATOGENIC POTENTIAL
THYMIDINE UPTAKE
TIME LAPSE PHOTOGRAPHY
TRANSMITTED MUTATIONS
TRIER ASSAY
TUMORIGENIC ENHANCEMENT
TYROSINCE AMINO TRANSFERENCE
VIABILITY
VIRAL GENOME ANALYSIS
WI-38
X-CHROMOSOME LOSS TEST
A.5-27
-------
TABLE A.5.13b - TEST DESCRIPTION NOMENCLATURE FOR ECOLOGICAL
PROJECT TYPES
A Q STANDARDS EVALUATION
ACCUMULATIVE IMPACT
ALTERNATIVES DEV
ANTAGONISM
ANTAGONISM-SYNERGISM
ANTIGEN RESPONSE
APPEARANCE EVALUATION
BASELINE DATA DEV
BEHAVIORAL ANALYSIS
BENEFICIAL EFFECTS
BINDING MECHANISM
BIOCHEMICAL INDICES
BIOINDICATOR DEV
BIOINDICATORS
CATION TRANSPORT MODELS
CHEMICAL INDICES
CLOSED CHAMBER
COMPARATIVE EVALUATION
CRITERIA DEV
CYTOLOGIC INDICES
DATA BASE DEV
DEPOSITION MODEL
DEPOSITION STUDY
DETRITUS FORMATION
ELECTRON SPIN RESONANCE
ENTRAPMENT PERCENTAGES
ENZYME ACTIVITY
EVOLUTIONARY RESPONSE
FIELD-LABORATORY ASSAY
FOLIAR DAMAGE MODEL
FREE RADICAL ACTIVITY
GENETIC EFFECTS
GENETIC SUSCEPTIBILITY
GROWTH-REPRODUCTION
HOSE-PARASITE RESPONSE
IMPACTS EVALUATION
INJURY EVALUATION
INSECT DEFENCE MECHANISM
LATENT MORTALITY
LC50
LEAF PENETRATION TECHNIQUES
LESION FORMATION
LIGAND KINETICS
LITERATURE SURVEY
A.5-28
-------
TABLE A.5.13b - TEST DESCRIPTION NOMENCLATURE FOR ECOLOGICAL
PROJECT TYPES (Concluded)
MODELING
METABOLIC ACTIVITY
MONITORING/TECHNIQUES DEV
MORTALITY
NEEDLE DEVELOPMENT
NITRITE METABOLISM
NUTRIENT CYCLE
NUTRITIONAL QUALITY
OPEN TOP CHAMBER
PHENOLOGY
PHOTOSYNTHETIC RESPONSE
PHYSICO-CHEMICAL RESPONSE
PHYSIOLOGICAL INDICES
PLANT SOIL INTERACTIONS
POLLUTANT CYCLING
POPULATION DENSITY
POPULATION DYNAMICS
PREDICTIVE MODELS
PRODUCTIVITY
RADIAL GROWTH ANALYSIS
REPRODUCTION INHIBITION
RESEARCH NEEDS ASSESSMENT
RESISTANCE MECHANISM
ROLE DETERMINATION
ROOT DEVELOPMENT
SCAVAGING CAPACITY
SENSITIVITY ANALYSIS
SOIL-CROP MANAGEMENT DEV
SPECIES COMPOSITION CHANGES
STOCHASTIC MODELS
STRUCTURAL DYNAMICS
SUBLETHAL PARAMETERS
SUCCESSIONAL TRENDS
SURVIVAL
SYNERGISM-ANTAGONISM
SYNERGISTIC EFFECTS
THERMAL LIMITS
THERMOREGULATION MODELS
THRESHOLD MEASUREMENTS
TISSUE DEGENERATION
TISSUE TOXICANT LEVEL
TOLERANCE LIMITS
TROPHIC RELATIONSHIPS
UPTAKE-TRANSLOCATION
VOLATILE ORGANICS PRODUCTION
YIELD MEASUREMENTS
HOUR LC50
A.5-29
-------
TABLE A.5.l4a - TEST STRAINS/ORGANISMS NOMENCLATURE FOR BIOLOGICAL
PROJECT TYPES
ABDOMINAL FAT/HUMAN
ALVEOLAR EPITHELIAL CELLS/NSD
ALVEOLAR MACROPHASE/NSD
ALVEOLAR MACROPHAGE/RABBIT
ANIMAL
ANIMAL CELLS
ANIMAL POPULATIONS
B LYMPHOCYTES/MAN
BACTERIA
BALB C 3T3
BIOLOGICAL MEMBRANES/MODEL
BIOLOGICAL MEMBRANES/NSD
BIOLOGICAL MEMBRANES/RAT
BLOOD PLASMA/RAT
BRAIN CELLS/NSD
BRAIN MITOCHONDRIA/RAT
BRAIN/RAT
CARDIOPULMONARY SYSTEM/DOG
CARDIOPULMONARY SYSTEM/GUINEA PIG
CARDIOPULMONARY SYSTEM/MAN
CARDIOPULMONARY SYSTEM/RODENT
CATE CHOL-0-METHYL TRANSFERASE/RODENT
CELLS/DOG
CELLS/MAMMAL
CELLS/MAN
CELLS/NSD
CELLS/RODENT
CENTRAL NERVOUS SYSTEM/ANIMAL FETUS
CENTRAL NERVOUS SYSTEM/HUMAN
CENTRAL NERVOUS SYSTEM/MAN
CENTRAL NERVOUS SYSTEM/RABBIT
CENTRAL NERVOUS SYSTEM/RODENT
CHICK
CHILDREN
CHLOROPLASTS/PLANTS
CHROMATIN/MAMMAL
CHROMOSOMES/NSD
CHROMOSOMES/SWINE EMBRYO
DNA/MAN
DNA/NSD
DOGS
DROSOPHILA
EMBRYO/ANIMAL MODEL
EMBRYO/HAMSTER
EMBRYO/MAMMAL
A.5-30
-------
TABLE A.S.Ua - TEST STRAINS/ORGANISMS NOMENCLATURE FOR BIOLOGICAL
PROJECT TYPES (Continued)
EMBRYO/MOUSE
ENZYMES/NSD
EPITHELIAL CELLS/MAN
EPITHELIAL CELLS/MOUSE
EPITHELIAL CELLS/NSD
EPITHELIAL TISSUE/NSD
E. COLI
GLYCEROLIPIDS/NSD
GOAT
GUINEA PIG
HAMSTER
HEART TISSUE/MAN
HEART TISSUE/NSD
HEART TISSUE/RAT
HEART TISSUE/RODENT
HEMATOPOIETIC SYSTEM/MAMMAL
HEPATOMA CELLS/NSD
HISTONE KINASE/ANIMAL
IMMATURE NEPHRON/RABBIT
IMMATURE NEPHRON/RAT
IMMUNOGLOBULIN/RABBIT
INSECTS
KIDNEY MITOCHONDRIA/RAT
KIDNEYS/MAN
KIDNEYS/RODENT
LATENT TUMOR VIRUSES/CHICKEN
LEUKEMIA VIRUS/BIRDS
LIPIDS/NSD
LIPOPROTEIN/NSD
LIVER HEPATOCYTES/RAT
LIVER MICROSOMES/NSD
LIVER MITOCHONDRIA/RAT
LIVER/MAN
LIVER/NSD
LIVER/RAT
LOBSTER
LUNG CELLS/MOUSE
LUNG CELLS/NSD
LUNG FIBROBLASTS/MAN
LUNG MONOCYTES/NSD
LUNGS/ANIMAL
LUNGS/DOG
LUNGS/HAMSTER
LUNGS/MAN
LUNGS/MOUSE
A.5-31
-------
TABLE A.5.l4a - TEST STRAINS/ORGANISMS NOMENCLATURE FOR BIOLOGICAL
PROJECT TYPES (Continued)
LUNGS/NSD
LUNGS/RABBIT
LUNGS/RAT
LUNGS/RODENT
LYMPH NODES/NSD
LYMPHOCYTES/BABOON
LYMPHOCYTES/NSD
L-2 LUNG CELLS/RAT
MACROPHAGE/BABOON
MACROPHAGE/NSD
MAMMALS
MAN
MICROSOMES/MOUSE
MITOCHONDRIA/NSD
MONKEY
MONOAMINE OXIDASE/RODENT
MOUSE
NASAL MUSCOSA/CHICKEN
NEUTROPHILES/MAN
NORADRENALINE/RODENTS
NUCLEIC ACID/MAMMAL
NUCLEIC ACID/NSD
OVARY CELLS/CHINESE HAMSTER
PANCREAS/MAN
PLASMA MEMBRANE/ALGAE
PLASMA/MAN
PLASMA/PRIMATES
POLYMORPHONUCLEAR LEUKOCYTES/NSD
POSTNATAL ANIMAL MODEL
PRIMATES
PROTOZOAN
PSOAS MUSCLE/MAN
RABBIT
RAT
RED BLOOD CELLS/MAN
RESPIRATORY DEFENCE SYSTEM/RODENT
RESPIRATORY SYSTEM/DONKEY
RESPIRATORY SYSTEM/GUINEA PIG
RESPIRATORY SYSTEM/HAMSTER
RESPIRATORY SYSTEM/MAN
RESPIRATORY SYSTEM/MONKEY
RESPIRATORY SYSTEM/MOUSE
RESPIRATORY SYSTEM/NSD
RESPIRATORY SYSTEM/RAT
RESPIRATORY SYSTEM/RODENT
RESPIRATORY TRACT/MAN
A.5-32
-------
TABLE A.5.14a - TEST STRAINS/ORGANISMS NOMENCLATURE FOR BIOLOGICAL
PROJECT TYPES (Concluded)
RNA/E. COLI
RNA/NSD
RODENT
SALMONELLA TYPHIMURIUM
SALMONELLA TYPHIMURIUM TA-1533
SALMONELLA TYPHIMURIUM TA-98
SEA URCHIN
SKIN/MOUSE
SKIN/RAT
SPERM/MAMMAL
SWINE
T LYMPHOCYTES/MAN
TESTES/RAT
TISSUE/ANIMAL
TISSUE/MAN
TRACHEA/NSD
TRACHEA/RAT
URINE/MAN
WHITE BLOOD CELLS/MAN
A.5-33
-------
TABLE A.5.145 - TEST STRAINS/ORGANISMS/ECOSYSTEMS NOMENCLATURE FOR
ECOLOGICAL PROJECT TYPES
ACER SACCHARUM
ALFALFA
ALGAE
ALLIGATORS
ANIMALS
AQUATIC ECOSYSTEM
AQUATIC ORGANISMS
ARTHROPODS
ASH
ATMOSPHERE
BACTERIA
BEANS
BENTHIC ALGAE
BIRDS
BLUE GREEN ALGAE
BROADLEAF PLANTS
CARROTS
CONIFEROUS FOREST
CONIFEROUS SEEDLINGS
CONIFERS
COTTON
CRAYFISH
CROP PLANTS
CRYPTOGRAMS
DESERT ECOSYSTEMS
DESERT PLANTS
DETRITUS
DOMESTIC LIVESTOCK
DOUGLAS FIR-DWARF MISTLETOE
ESTUARINE ECOSYSTEM
ESTUARINE ORGANISMS
ESTUARINE SHELLFISH
FATHEAD MINNOWS
FINFISH
FINFISH LARVAE
FISHES
FLOUNDER
FOREST VEGETATION
FRAXINUS PENNSYLVANIA
GRASSES
GRASSLAND
ICHTHYOPLANKTON
INSECTS
INVERTEBRATES
INVERTEBRATES LARVAE
A.5-34
-------
TABLE A.5.l4b - TEST STRAINS/ORGANISMS/ECOSYSTEMS NOMENCLATURE FOR
ECOLOGICAL PROJECT TYPES (Continued)
KENLAND RED CLOVER
KIDNEY BEAN
LARK BUNTING
LARK SPARROW
LARVAE
LENTIC ECOSYSTEMS
LETTUCE
LICHENS
LOCAL FLORA
LOTIC ECOSYSTEMS
MACROALGAE
MAMMALS
MANGROVE LEAF DETRITUS
MARINE ORGANISMS
MESOPHYTIC TREES
MOUSE
MICRO ALGAE
MINT
MOURNING DOVE
MUMMICHOG
NITRIFYING BACTERIA
NONTARGET ESTUARINE ORGANISM
OAKS
ONIONS
PEAS
PHYTOPLANKTON
PINE BARK BEETLE
PLANKTON
PLANTS
PLATANUS OCCIDENTALS
PONDEROSA PINE-DWARF MISTLETOE
POPLARS
POSTTHERMAL AQUATIC HABITAT
POTATOES
PUMPKINSEED
QUERCUS ALBA
RADISHES
RAINBOW TROUT
RED ALDER
RED ALDER-DWARF MISTLETOE
RIVULUS
SALMONID FISHES
SHRIMP
SHRUBS
SHRUB-STEPPE ECOSYSTEM
SOIL DECOMPOSERS
A.5-35
-------
TABLE A.5.l4b - TEST STRAINS/ORGANISMS/ECOSYSTEMS NOMENCLATURE FOR
ECOLOGICAL PROJECT TYPES (Concluded)
SOIL MICROFLORA
SOYBEANS
SUGAR MAPLE
TEAM ALFALFA
TERRESTRIAL ECOSYSTEM
THALASSIA TESTUCINUM
THERMAL AQUATIC HABITATS
TREES
TROUT
TUNDRA ECOSYSTEMS
TURFGRASS
TURTLES
VEGETATION
VESPER SPARROW
WEEDS
WESTERN MEADOWLARK
WESTERN WHEATGRASS
WETLANDS ECOSYSTEM
WILDLIFE
ZIPHOPHORUS
ZOOPLANKTON
A.5-36
-------
TABLE A.5.15 - POLLUTANTS NOMENCLATURE
ACID AEROSOL
ACID RAIN
ACIDITY
ACROLEIN
ADDITIVES
AEROSOLS
AIR POLLUTANTS
ALCOHOLS
ALDEHYDES
ALDEHYDES-NOX
ALKANES-NOX
ALKENES
ALKENES-NOX
ALKYLPEROXY RADICALS
AKLYLATING HYDROCARBONS
ALUMINUM
ALUMINUM SULFATE
AMERICIUM-241
AMINES
AMMONIA
AMMONIUM SULFATE
ANIONS
ANTIMONY
ARGON
AROMATIC ALDEHYDES
AROMATIC HYDROCARBONS
AROMATICS-NOX
ARSENIC
ASBESTOS
BARIUM
BENZ[A]ANTHRACENE
BENZIDINE
BENZO[A]PYRENE
BERYLLIUM
BERYLLIUM-7
BETA-PROPIOLACTONE
BIOCIDES
BISULFITE
BOD
BROMINE
CADMIUM
CALCIUM
CALCIUM CARBONATE
CALCIUM SULFATE
CARBON
CARBON DIOXIDE
A.5-37
-------
TABLE A.5.15 - POLLUTANTS NOMENCLATURE (Continued)
CARBON MONOXIDE
CARBON OXIDES
CARBONATES
CARBONYLS
CARCINOGENS
CESIUM
CHEMICAL EFFLUENTS
CHEMICAL KINETICS
CHLORIDE
CHLORINE
CHLORINE-COMPOUNDS
CHROMIUM
CLO RADICAL
COAL COMBUSTION BY-PRODUCTS
COAL EXTRACTION BY-PRODUCTS
COAL PILE DRAINAGE
COAL PROCESSING BY-PRODUCTS
COBALT
COD
COMBUSTION BY-PRODUCTS
CONDENSATION NUCLEI
COOLING TOWER PLUMES
COOLING WATER
COOLING WATER INTAKES
COPPER
COPPER OXIDES
CORROSIVENESS
CYANIDES
DEUTERIUM
DICHLORODIFLUOROMETHANE
DIBROMODIFLUOROMETHANE
DIEPOXYBUTANT
DIMETHYLBENZANTHRACENE
7,12-DIMETHYLBENZANTHRACENE
DISINFECTANTS
DUST
EPOXIDES
ETHYLENE
FINE PARTICULATES '
FLUORIDES
FLUORINE
FLYASH
FORMALDEHYDE
FOSSIL FUEL POLLUTANTS
FREE RADICALS
GALLIUM
A.5-38
-------
TABLE A.5.15 - POLLUTANTS NOMENCLATURE (Continued)
GASEOUS EMISSIONS
GROUND STATE OXYGEN
GUANIDINE
GYMNODINIUM
HALOCARBONS
HALOGENATED ACIDS
HAZARDOUS MATERIALS
HEAT
HEAVY METAL
HUMIDITY
HYDROCARBONS
HYDROCARBON-NOX
HYDROCARBON-NOX-OXIDANT
HYDROCARBON-NOX-SULFUR DIOXIDE
HYDROGEN DISULFIDE
HYDROGEN FLUORIDE
HYDROGEN PEROXIDE
HYDROGEN SULFIDE
HYDROPEROXY RADICALS
HYDROXIDE RADICAL
HYDROXYURETHANE
INDIUM
INERT TRACER
INORGANIC IONS
INORGANIC POLLUTANTS
INSOLUBLE SILICATES
IODINE
IONIZING RADIATION
IRON
IRON OXIDES
IRON SALT-ORGANICS
ISOGUTYLENE
KETONES
KRYPTON
KRYPTON-85
LANTHANUM
LEACHATE
LEAD
LEAD FLUORIDE
LIGHT METALS
LIME
LIMESTONE
LITHIUM
MAGNESIUM
MAGNESIUM OXIDE
MANGANESE
MASS TRANSFER
A.5-39
-------
TABLE A.5.15 - POLLUTANTS NOMENCLATURE (Continued)
MERCURY NITRATE
MERCURY
METAL CATIONS
METAL SULFATES
METALLIC NUCLEI
METALS
METHANE
3-METHYLCHOLANTHRENE
METHYL MERCURY
MOLYBDENUM
MULTI ELEMENTS
MUTAGENS
NICKEL
NICKEL COMPOUND
NICKEL CHLORIDE
NICKEL COBALT
NICKEL SULFIDE
NICKEL [III] SULFIDE
NICKEL SELENIDE
NICKEL [III] SELENIDE
NITRATE AEROSOLS
NITRATES
NITRIC ACID
NITRITES
NITROARMATICS
NITROGEN
NITROGEN DIOXIDE
NITROGEN MONOXIDE
NITROGEN OXIDES
NITROQUINOLINE OXIDE
NITROSOAMINES
NITROUS ACID
NITROUS OXIDE
NMHC
NOISE
NONMETHANE HYDROCARBONS
NO -N02-N03
NUTRIENTS
N205 RADICAL
OH-OXYGEN-AROMATICS
ONCOGENIC POLLUTANTS
OPACITY
ORGANIC ACIDS
ORGANIC AEROSOLS
ORGANIC COMPOUNDS
ORGANOBROMIDES
ORGANOCADMIUM
A.5-40
-------
TABLE A.5.15 - POLLUTANTS NOMENCLATURE (Continued)
ORGANOCHLORIDES
ORGANOMERCURY
ORGANOMETALLICS
ORGANONITROGEN
ORGANOTIN
OXIDANTS
OXIDIZED SPECIES
OXYGEN
OXYGEN-16
OXYGEN-18
OZONE
PAH
PAN
PARTICLE MASS
PARTICULATE MATTER
PARTICULATE NITRATES
PARTICULATE SIZING
PARTICULATE SULFATE
PB-210
PCB
PCH
PERFLUOROCARBON TRACERS
PEROXYACETYL NITRATE
PH
PHENOLIC COMPOUNDS
PHOSPHATE
PHOSPHORUS
PHOTOCHEMICAL OXIDANTS
PHOTOCHEMICAL REDUCTANTS
PHOTOCHEMICAL SMOG
PHYSICAL PROPERTIES
PLATINUM
PLUME KINETICS
PLUMES
PLUTONIUM
POLLUTANT REMOVAL TECHNIQUES
POLLUTANTS
POM
POTASSIUM
PO-210
PRIMARY POLLUTANTS
PROCESS WATER WITHDRAWAL
PROPYLENE
PROPYLENE SMOG
PU-239
A.5-41
-------
TABLE A.5.15 - POLLUTANTS NOMENCLATURE (Continued)
PU-240
PYRENE
RADIATION
RADIOACTIVE MATERIALS
RA-226
REACTANT HYDROCARBONS
REACTIVE POLLUTANTS
REDUCED SPECIES
RESPIRABLE PARTICULATES
R02
RUBIDIUM
SALINITY
SALTS
SECONDARY POLLUTANTS
SELENIUM
SETTLEABLE MATTER
SF6
SILICA
SILICON
SILVER
SINGLET OXYGEN
SLUDGE
SMOG
SMOKE
SODIUM
SODIUM SULFIDE
SOLUBLE SULFATE
S02-NACI AEROSOLS
S02-N0 -METAL ION
STRONTIUM
SULFATE PARTICLES
SULFATE
SULFIDE
SULFITE
SULFUR
SULFUR COMPOUNDS
SULFUR DIOXIDE
SULFUR DIOXIDE-NOX
SULFUR DIOXIDE-SULFATE
SULFUR DIOXIDE-OZONE-OLEFIN
SULFUR OXIDES
SULFUR OXIDES-SULFUR DIOXIDE
SULFUR TRIOXIDE
SULFUR TRIOXIDE-SULFURIC ACID
SULFURIC ACID
TEMPERATURE
A.5-42
-------
TABLE A.5.15 - POLLUTANTS NOMENCLATURE (Concluded)
THALLIUM
THALLIUM-230
THERMAL EFFLUENTS
TIN
TITANIUM
TOC
TOTAL DISSOLVED SOLIDS
TOTAL SUSPENDED SOLIDS
TOXIC SUBSTANCES
TRACE CONTAMINANTS
TRACE ELEMENTS
TRACE ORGANICS
TRANSITION METALS
TRANSURANIC ELEMENTS
ULTRAVIOLET LIGHT
URANIUM
URANIUM-234
URANIUM-238
URETHAN
VANADIUM
VANADIUM OXIDES
VINYL CHLORIDES
VINYL RADICALS
VIRUSES
WASTE TO ENERGY
WATER POLLUTANTS
WATER VAPOR
XENON
ZINC
ZINC AMMONIUM SULFATE
ZINC SULFATE
ZIRCONIUM
A.5-43
-------
TABLE A.5.16 - SAMPLING TECHNIQUES NOMENCLATURE
CW CONTINUOUS WITHDRAWAL THROUGH NON-REACTIVE LINE
IG GRAB SAMPLE OF GAS (BAG OF BULB)
ST ' SEPARATE WET CHEMICAL TRAIN TO COLLECT GAS, SUCH
AS METHOD 6
SASS SASS TRAIN
GS GRAB SAMPLE OF SOLID OR LIQUID
MASS MASS TRAIN FOR PARTICULATE
CASC CASCADE IMPACTOR TRAIN FOR PARTICLE SIZING
HVSS HIGH - VOLUME SAMPLING SYSTEM
FAST FUGITIVES ASSESSMENT SAMPLING TRAIN
OPC OPTICAL PARTICLE COUNTER
CNDB CONDENSATION NUCLE: COUNTER/DIFFUSION BATTERY
FRN FEDERAL REGISTER METHOD WHERE N DENOTES METHOD
NUMBER (I.E., FR5 = METHOD 5, FR10 = METHOD 10)
GOKS GOLSOYR - ROSS
ZZZZ OTHER - SEE COMMENTS
A.5-44
-------
TABLE A.5.17 - ANALYTICAL METHOD CODES
CODE ANALYTICAL METHOD
AA ATOMIC ABSORPTION SPECTROMETRY
AM AMPEROMETRY
AS ALPHA-SCAN SPECTROMETRY
BS BETA-SCAN SPECTROMETRY
CA CARBON ANALYZER
CD CONDUCTIMETRY
CL CHEMILUMINESCENCE
CM COULOMETRY
CO COLORIMETRY
DI DISTILLATION
EX EXTRACTION
FI FLAME IONIZATION DETECTOR GC
FT FOURIER TRANSFORM IR
GA GAMMA-SCAN SPECTROMETRY
GC GAS CHROMATOGRAPHY (NON-SPECIFIED DETECTION)
GE GAS EVOLUTION
GL ELECTRON-CAPTURE GC
GR GRAVIMETRIC ANALYSIS
GS GAS CHROMATOGRAPHY/MASS SPECTROMETRY
GT THERMAL CONDUCTIVITY CELL GC
HP HIGH PERFORMANCE LIQUID CHROMATOGRAPHY
1C ION CHROMATOGRAPHY
IP INDUCTIVELY COUPLED ARGON PLASMA SPECTROSCOPY
IR INFRARED SPECTROMETRY
LC LIQUID CHROMATOGRAPHY
LI GENERAL LEVEL 1 ANALYSIS
L2 GENERAL LEVEL 2 ANALYSIS
MS MASS SPECTROMETRY
NA NEUTRON ACTIVATION ANALYSIS
ND NONDISPERSIVE INFRARED SPECTROMETRY
NM NUCLEAR MAGNETIC RESONANCE SPECTROMETRY
NS NOT SPECIFIED
OA ORSAT ANALYSIS
OS OPTICAL EMISSION SPECTROSCOPY
PM PARAMAGNETIC OXYGEN ANALYSIS
PO POLAROGRAPHY
RA RADIOCHEMICAL ANALYSIS
RS RAMAN SPECTROSCOPY
SE ION SELECTIVE POTENTIOMETRY
SM SCANNING ELECTRON MICROSCOPY
SS SPARK SOURCE MASS SPECTROSCOPY
TA THERMAL ANALYSIS
A.5-45
-------
TABLE A.5.17 - ANALYTICAL METHOD CODES (Concluded)
CODE ANALYTICAL METHOD
TI TITRIMETRY
TL THIN LAYER CHROMATOGRAPHY
TU TURBIDIMETRY
UV ULTRAVIOLET SPECTROMETRY
VO VOLTAMETRY
WC WET CHEMICAL ANALYSIS (NOT SPECIFIED)
XD X-RAY DIFFRACTION
A.5-46
-------
TABLE A.5.18 - SAMPLING LOCATION NOMENCLATURE
FUL FUEL
SPL STORAGE PILE LEACHATE
BCS BEFORE CONTROL SYSTEM
ACS AFTER CONTROL SYSTEM
STK STACK
PLM PLUME
SLG SLUDGE
APD ASH POND
WWS WASTE WATER STREAM
CWS COOLING WATER STREAM
ECO ECOLOGICAL SYSTEM
IRM WORK OR LIVING SPACE
AMB AMBIENT AIR
TWR COOLING TOWER
APL ASH POND LEACHATE
CPR COAL PILE RUNOFF
NSD NOT SPECIFIED
A.5-47
-------
TECHNICAL REPORT DATA
(Please read Inunctions on the reverse before completing)
1 REPORT NO. 2.
EPA-600/8-80-031
4. TITLE ANOSUBTITLE
Environmental Assessment Data Systems User Guide:
Project Profile System
7. AUTHOR(S)
J. P. Reider, Editor
g. PERFORMING ORGANIZATION NAME AND ADDRESS
Midwest Research Institute
425 Volker Boulevard
Kansas City, Missouri 64110
12. SPONSORING AGENCY NAME AND ADDRESS
EPA, Office of Research and Development
Industrial Environmental Research Laboratory
Research Triangle Park, NC 27711 '
3. RECIPIENT'S ACCESSION NO.
5. REPORT DATE
June 1980
6. PERFORMING ORGANIZATION CODE
8. PERFORMING ORGANIZATION REPORT NO.
10. PROGRAM ELEMENT NO.
EHE624A
1 1. CONTRACT/GRANT NO.
68-02-3177, Work Assignment
No. 3
13. TYPE OF REPORT AND PERIOD COVERED
Task Final: 8/79-4/80
14. SPONSORING AGENCY CODE
EPA/600/13
^.SUPPLEMENTARY NOTES IERL-RTP project officer is Gary L. Johnson, Mail Drop 63,
919/541-2745.
is. ABSTRACT The report is a yggy guide to the Project Profile System (PPS), a compu-
terized data base on projects of various types that pertain to specific industrial cate-
gories. PPS is one of five data bases which are components of the Environmental
Assessment Data Systems (EADS), designed to aid researchers in environmental
assessment, emissions characterization, and control technology development. PPS
contains data from nine general projects: source monitoring; integrated assessment;
transport, transportation, and fate; socioeconomics; sampling methods development;
fuels; control technology; ecological effects; and health effects. Each project descri-
bed in the PPS is identified by its sponsor, contractor, and other administrative in-
formation. The PPS contains an abstract of each project reported in text form and
lists pertinent references. The specific data in the PPS depends largely on the type
of project being reported; however, sufficient detail is available to report on a parti-
cular pollutant being sought or identified during the project. The PPS does not give
results (e.g. , pollutant concentrations, process data): it tells what the project invol-
ved. The guide gives detailed instructions for encoding PPS datasets, defines proce-
dures for submitting and retrieving data, and contains standard nomenclature to fa-
cilitate data encoding. The guide also discusses procedures to access PPS.
KEY WORDS AND DOCUMENT ANALYSIS
DESCRIPTORS
b.IDENTIFIERS/OPEN ENDED TERMS
COSATi Field/Croup
Pollution Fuels
Assessments Ecology
Information Systems
Industries Environmental Bi-
Monitors ology
Sampling
Pollution Control
Stationary Sources
Environmental Assess-
ment
Project Profile System
Socioeconomics
13B 21D
14B 06F
05B,09B
05C
14 G
13. 3ISTRIBUTION STATEMENT
Release to Public
19. SECURITY CLASS (This Report)
Unclassified
21. NO. OF PAGES
20. SECURITY CLASS (This page)
Unclassified
22. PRICE
EPA Form 2220-1 (9-73)
------- |