United States Environmental Monitoring and

Environmental Protection Assessment Program

Agency Washington, DC 20460

E AP Project Summary

Research and Development EPA/620/SR-94/017 August 1994

EMAP Information Management

Strategic Plan: 1993 – 1997

The Information Management (IM)

Strategic Plan for the Environmental

Monitoring and Assessment Program

(EMAP) describes how EMAP information will be managed from field sampling through the delivery of products

to the user. This plan cuts across the

entire EMAP and explains the process

for developing an information management infrastructure that will enable

EMAP to achieve its long-term objectives. This plan provides a strategy for

meeting hardware, software, documentation support, and system designs that

will meet EMAP Resource and Coordinating Group requirements. Users of

EMAP data and information are discussed in the Plan as well as the process and technology with which they

can access EMAP data and other data

sources.

This Project Summary was developed

by EPA’s Environmental Monitoring and

Assessment Program, Washington, DC,

to announce key findings of the research project that is fully documented

in a separate report of the same title

(see Project Report ordering information at back).

EMAP Commitment

The EMAP represents a long-term commitment by the U.S. Environmental Protection Agency (EPA) to assess and periodically document the status and condition of the Nation’s ecological resources.

EMAP’s goal is to monitor and assess the

condition of those resources and to contribute to decisions on environmental protection and management.1 EMAP will monitor indicators of the condition of our

Nation’s ecological resources to respond

to the growing demand for information

characterizing the condition of our environment and the type and location of environmental changes. The EMAP project,

when implemented, will provide the ability

to integrate information from multiple

sources across environmental media within

the context of the National Information

Infrastructure2 and provide assessments

of environmental impacts across ecological resource categories.

Strategic Plan

The EMAP IM Strategic Plan outlines

the implementation approach for development of workable information systems that

will meet the requirements of EMAP scientists, information managers, and government decision makers. The Plan provides EPA management with the scope,

the foundation of requirements and guiding principles, the management and technical approach, and resource requirements

for EMAP information systems development. The Plan also provides EPA environmental scientists and collaborators with

a common set of expectations and the

EPA information management staff with a

systems engineering road map that can

be used to direct activities over the next 5

years.

EMAP IM Vision

By 1997, EMAP is expected to monitor

and assess the current status and geographic distribution of such ecological resources as estuaries, lakes, streams, wetlands, forests, grasslands, and deserts.

By integrating information from several

government agencies, assessments and

reports will become available on the proportions of these resources that are degrading or improving, their location and

extent, and their rate of change. Reported

Robert F. Shepanek
2

ecological conditions and geographical

coverage will be available with known confidence.

By 2002, EMAP plans to expand its

monitoring and assessment capability to

include information from virtually all applicable federal sources. Degrading and improving trends will be identified through

specific indicators of how adversely affected ecosystems are responding to control and mitigation programs.

By 2012, EMAP should be a focused,

mature program that is integrated with scientific information from key national and

international sources. Trending information of all ecosystems will be available for

use in making decisions concerning national and international environmental management and economic development.

EMAP IM

EMAP IM is the vehicle with which the

total EMAP manages data and information. EMAP objectives and corresponding

EMAP IM objectives are shown in Figure

1. Specifically, EMAP IM will provide effective and extensible information management systems for assessing and reporting on the condition of the Nation’s

ecological resources. IM will provide the

tools for turning raw scientific measurements (data) into useful information products that will serve to guide actions to

improve the quality of our environment.

EMAP IM will be an environmental “information highway” allowing analysis of EMAP

data across heterogeneous networks of

personal and scientific computers by 1997.

EMAP IM systems will provide interfaces

for new analysis methods and integration

of related scientific information across a

“national information infrastructure.” Scientists will have access to data distributed

across a national network2

 and the computational tools needed to facilitate analyses.

EMAP IM systems will provide access to

data, metadata, and processed information for a diverse set of users through a

network of dispersed databases.

The EMAP Enterprise

The technical and management approaches discussed in the Plan require an

explanation of the term “enterprise.” The

EMAP Enterprise, when fully developed,

will include Resource Groups, Coordinating Groups, EPA and non-EPA related

programs, and administrative activities that

support the program. Collectively, EMAP

as an enterprise is made up of these user

groups, each of which has differing but

complementary missions to perform in order for EMAP to accomplish its objectives. EMAP IM will eventually involve all

these users and will consider their differing requirements for information management systems.

EMAP is and will continue to be an

evolving enterprise with diverse user requirements. Currently, the Resource

Groups are the most “mature” group of

users. For several years the Resource

Groups have been actively engaged in

indicator research, collecting data, analyzing data, and publishing results within

their ecological areas of responsibility.

Conversely, the aspect of the EMAP Enterprise least developed is the relationship of EMAP to other EPA and non-EPA

programs. For example, such questions

as “What information does EMAP have

that would assist NASA in accomplishing

the objectives of the Earth Observing System Program?” are difficult to answer at

this stage of EMAP development.

Enterprise Components

The size and diversity of the collective

EMAP user group and the evolving nature

of EMAP require a systems engineering

approach that is stratified by groups comprised of similar users, with similar missions, and in similar stages of development. These user groups are aggregated

into four components by level of maturity.

Figure 2 shows these user group components with the phased IM processes that

are applicable to each component. The

cells within this map depict the level of

user involvement. The “Enterprise Components” of EMAP are

• Planning, Research, Monitoring, and

Assessment - includes indicator research, collection and analysis of data,

and distribution of data and information related to an ecological area of

responsibility. This component is comprised of Resource Group users.

• Integration and Assessment - provides

direction on the composition of EMAP

information products that are derived

from data available within individual

Resource Groups, as well as information products derived from multiple

Resource Groups. This component

includes Coordinating Groups supporting assessment activity by EMAP

Central.

• EMAP National Program component

within EPA - defines the relationship

of EMAP to other relevant EPA programs. These programs include the

Great Lakes National Program, The

Gulf of Mexico Program, the STORET

Modernization within the Office of

Water, the Gateway/Envirofacts program within the Office of Information

Resource Management and others.

This component also includes connections to appropriate EPA administrative programs.

• EMAP as partner in an Interagency

Federation - defines the relationship

of EMAP to relevant programs outside of EPA that are not already included in other EMAP Enterprise components by virtue of their cooperative

partner status. Examples of the types

of programs targeted are NASA’s

EOS/DIS and the Global Change Research Program.

Each EMAP IM process includes an

execution of the systems development life

cycle (SDLC) and results with an operational information management system for

the designated user. For example, Forests and Estuaries, as well as the EMAP

Center, will have operational systems upon

completion of the Proof-of-Concept (POC).

An operational system is the computer

hardware, software, databases, and communications links that are required to share

data, metadata, and information among

users.

EMAP Users

The collective EMAP user community is

reflected in Figure 3. The first category–and

highest priority EMAP user from a strategic

and implementation perspective–is the scientific community actively participating in EMAP.

These principal users will be scientists in the

EMAP Resource and Coordinating Groups,

other EPA scientists, and such EMAP Cooperative Partners as the National Oceanographic and Atmospheric Administration

(NOAA) and the U.S. Forest Service

(USFS). These users have primary responsibility for planning, designing, collecting, managing, researching, validating,

analyzing, and interpreting environmental

data for a multitude of purposes.

The second user category includes other

EMAP participants such as public and private sector scientists and researchers

working on behalf of government, academic, and commercial interests; policy

makers and government managers who

use EMAP information to determine policy

and guidance; and the general public and

media, all of whom may use EMAP information as an ecological report card.

Eventually, users of EMAP data and

information will range from scientists who

will extract crosscutting data sets for detailed quantitative analyses to members

of Congress, the general public, and the

news media who require qualitative information products. A histogram at Figure 4

depicts relative differences in user involvement by EMAP Enterprise components.

The makeup of the groups representing
3

 Program Objectives IM Objectives

Estimate the current status, • Assist in structuring, developing, maintaining, operating,

trends, and changes in selected and/or deploying:

indicators of the condition of - Resource Group databases for research, monitoring,

the Nation’s ecological and analysis;

resources on a regional basis - Access mechanisms to the databases;

with known confidence. - Manipulation mechanisms (algorithms); and

- Display mechanisms required for research, monitoring, and

analysis.

Estimate the geographic cover- • Assist in structuring, developing, maintaining, operating, or

age and extent of the Nation’s deploying:

ecological resources with - Access mechanism to EMAP Geographic Reference Data

known confidence. (GRD);

- Manipulation mechanisms (algorithms); and

- Display mechanisms required to analyze this information.

Seek associations between in- • Ensure a distributed database structure that allows integradicators of natural and anthro- tion of information internally, and with external sources alpogenic stresses and indicators lowing responsibility for the data to reside with the “owners.”

of condition of ecological • Assist in the development, maintenance, operation, and

resources. deployment of crosscutting tools.

Provide annual statistical • Ensure that all data, metadata, and information required to

summaries and periodic as- meet the objective are available, in some cases by leveraging

sessments of the Nation’s the central node of the database system.

ecological resources. • Assist in the development, maintenance, operation, and

deployment of access mechanisms and display mechanisms

useful in meeting this objective.

Figure 1. EMAP IM objectives.

The EMAP Enterprise

Component

IM

Processes

Planning

Research

Monitoring &

Assessment

Integration

and

Assessment

EMAP

National

Program

EMAP

Interagency

Federation

Proof

of

Concept

Forests

and

Estuaries

Limited

Coordinating

Groups

Technology

Transfer

All

Resource

Groups

All Resource

Groups/

Limited

Coordinating

Groups

All Resource

and

Coordinating

Groups

Enterprise

Implementation

EPA

Interactions

Interagency

Interactions

System Development

Life Cycle

Figure 2. The EMAP enterprise.
4

Public

Policy Makers/

Management

Other Scientists

Other EPA

Coordinating Groups

Resource Group

Scientists

Other

EMAP IM

Users

Principal

EMAP IM

Users

Use information as an

ecological report card

Use information to determine policy

and guidance

Use data/info for educational, scientific,

and commercial purposes

Use data/information for research

and analysis

Support scientists with data, info,

analysis tools and processes

Plan for, collect, validate, catalog,

and assess data

Data - Information

Figure 3. EMAP IM users.

the requirements of an EMAP Enterprise

component has been structured to exert a

leveling effect on the requirements gathering process. For example, although the

POC is primarily driven by EMAP scientists, some policy makers and other scientists are involved in the process.

EMAP Products

EMAP will provide three products that

the EMAP IM system must support during

the Plan period:

• Databases and derived information;

• Annual statistical summaries; and

• Integration and assessment reports.

Additionally, EMAP IM is designed to

provide for administrative products that

will be important to support EMAP as a

National Program within EPA (Figure 5).

EMAP IM Technical Guidelines

The technical approach used to define

EMAP IM system development and implementation will be based on these guidelines:

• Use existing national infrastructure

and standards whenever possible;

• Concentrate on integration engineering rather than new system development;

• Use a systems engineering approach

based on a formal design process

incorporating functional pilots and prototypes; and

• Use emerging technology whenever

possible in meeting user needs.

Evolutionary Approach

EMAP IM is designed to use an “evolutionary” systems engineering approach that

adapts to emerging user needs and technology. This approach will permit ongoing

use of operational systems while the development process continues. The distinguishing difference between the EMAP

evolutionary approach and more traditional

system engineering approaches is EMAP’s

greater involvement of users throughout

the SDLC. The SDLC elements include

concept, analysis, design, development,

test, and operation. Activities during each

element of the SDLC will take into account current and projected user needs

and technology and incorporate user feedback and new technology into the system

development process.

EMAP IM Framework

To assist in system development, EMAP

IM uses the Zachman Framework3 as an

architectural guide during the Enterprise

process. This framework allows for an orderly approach for designing and building

systems. It provides system developers a

complete template against which to map

sequential and/or parallel steps for carrying out development of technical and management solutions.

The Zachman Framework stresses that

the information system development process requires several architectures. Figure 6 depicts the Framework architectures: Data, Function, Network, People,

Time, and Motivation. The levels of each

architecture in the Framework are Scope,

Enterprise Model, Information System

Model, Technology Model, Components,

and Functioning System.

Each Framework architecture (e.g.,

data) develops as the process progresses

though the Framework’s life cycle from

Scope through Functioning System. This

process development life cycle is applied

to each architecture within the Framework. This iterative process will be applied to each subsequent Enterprise component during the three IM implementation processes: POC, Technology Transfer, and Enterprise Implementation.

Using such a checklist ensures that all

aspects of the system are addressed from

an “enterprise approach” and that all participants in the development and implementation of the Enterprise have a common reference. (This framework has been

adopted for use by the EPA Office of

Information Resources Management

[OIRM] as a basis for all EPA systems.)

The Framework also provides a technology-independent model to accommodate

emerging hardware development and software changes.

EMAP IM Architecture

Another view of the EMAP architecture

is provided by the seven layer model depicted in Figure 7. (It should be noted that

these architecture functions will be provided, to varying degrees, by dispersed

systems at multiple nodes.) Forming the

foundation of the architecture is the canonical data layer. It is comprised of databases and data sets that can be accessed

by tools from the tool set layer.
5

Public

Policy Makers

Other Science

Other EPA

Coord Gp

Resource Gp

Planning, Research, Monitoring, and

Assessment

Public

Policy Makers

Other Science

Other EPA

Coord Gp

Resource Gp

Integration and Assessment

EMAP National Program EMAP Interagency Federation

Figure 4. Relative user involvement by EMAP IM component.

Figure 5. EMAP enterprise products.

EMAP Planning, National Program

Research,

Monitoring &

Assessment

Information System

Integration &

Assessment

Interagency

Federation

Processed

Information

Annual

Statistical

Summaries

Integration &

Assessment

Reports

Administrative

Products

Requirements

Resource Groups

Coordinating Groups

Cooperative Partners

Resource Groups

Coordinating Groups

STORET, EnviroFacts

Other EPA Sources EOS/DIS, NBS

Other Data Sources

Above the database layer is the Virtual

Repository layer. The components of the

Virtual Repository are model management tools, Computer Aided Software

Engineering (CASE) tools, configuration

management tools, the data dictionary,

the directory, and catalog. The first three

tools mentioned in this layer and the data

dictionary pertain to computer science

metadata that describe data stored in a

relational database structure. The directory and catalog components of the Virtual Repository layer contain scientific

metadata that describe data sets and documents.

The security layer provides a means for

EMAP to ensure the long-term integrity of

its collection by controlling access. Security procedures, in practice, can apply at

the user interface layer, the communications access layer, and the canonical data

layer.

The communications and user access

layer represents the means by which data

may be entered and retrieved from the

data layer using the Virtual Repository.

Note that the software back plane connects at this level and that access is

provided to users of the back plane

through the Virtual Repository. A user

entering through the tool set layer has

the option of directory or catalog access,

or access through the flexible set of tools

that are provided to the user community

to facilitate their use of the data. The

inter-process communication layer allows

the individual tools to communicate by

passing data from one to another for

processing. Finally, the user interface

layer provides easy invocation of the various tools available as part of the EMAP

suite and other tools available on the

client platform.

EMAP IM Management

The EMAP Director has overall program

responsibility. The Director of the EMAP

Center directs eight Coordinating Groups

and is responsible to the EMAP Director.

The Coordinator of Information Management, who heads one of the eight Coordinating Groups, is responsible for EMAP

IM. The IM Coordinator relies on members of the eight Resource Group IM teams

for coordination and implementation of

EMAP IM.

EMAP IM is using an adaptation of an

IBM Corporation information systems management process model4 as the basis for

project management as shown in Figure

8. This model has strategic, tactical, and

operational levels that are sectioned into

development, management, and service

missions. The evolutionary approach of

EMAP IM engages all levels and missions

virtually simultaneously since operation

implementation must continue to occur

within the Resource Groups while tactical

and strategic events are evolving.

The EMAP IM functional organization

consists of teams focused on systems architecture, science direction, user interaction and planning, interagency data interchange, advanced technology evaluation, systems engineering, and systems

support and operations. Each of these

teams has specific roles within the management structure (Figure 9). Additionally,

ongoing coordination is required with federal and EPA information resources management programs and offices.

EMAP IM Implementation

Processes

EMAP IM development and implementation consist of three IM process

phases. First is the POC process that

identifies and applies standards, policies, tools, and procedures to the For-
6

Architecture Framework

EMAP Process

Development

Life Cycle Scope

Enterprise

Model

Information

System

Model

Technology

Model

Components

Functioning

System

Data Function Network People Time Motivation

Proof of Concept

Technology Transfer

Enterprise

Figure 6. EMAP architecture framework.

Figure 7. EMAP IM architecture.

est and Estuaries Resource Groups and

limited Coordinating Groups. The Technology Transfer phase consists of extending the environment validated during the POC to the remaining Resource

Groups and an increasing number of

Coordinating Groups. The third process

is Enterprise Implementation, which engages other EPA and non-EPA programs in the systems development process. This phase re-engineers preceding implementation activities from an

enterprise perspective.

The implementation schedules for each

process are shown in Figures 10, 11, and

12. The schedules are arranged by program function into general SDLC categories titled Initiation/Concept, Definition &

Design, and Implementation/Operation.

Each of these categories then lists IM

functional areas and planned deliverables.

It is important to note that each step of

the implementation process includes participation from other user categories. For

example, all Resource and Coordinating

Groups have been observing the Planning, Research, Monitoring, and Assessment POC in order to facilitate their role in

the Technology Transfer process.

EMAP Schedule (1993 – 1997)

The schedules discussed below are

based on the assumption that required

resources will be available as depicted in

Figure 13. If, however, constraints are

placed on EMAP IM resources, the technical and management approaches specified in the Plan are sufficiently flexible to

permit implementation to occur, but over

a longer period of time. Also, it should be

noted that capabilities scheduled for

completion in the “out-years” are already

in development to varying degrees. For

example, the Virtual Repository, Geographic Information Systems (GIS), and

user interface capabilities commenced with

the 1993 POC.

1993–Research, Monitoring, and Assessment POC. This demonstration was

designed to enable two Resource Groups

to collect, manage, and share distributed

data.

1994–Planning, Research, Monitoring,

and Assessment Technology Transfer.

This process will share the activities and

technology from the POC with the other

Resource Groups and Coordinating

Groups. The system will include the initial

data dictionary, perform basic analysis,

provide initial user interface, provide GIS

and initial report generation tools, and perform internal data exchange adhering to

established OIRM data standards.

1995–Integration and Assessment Enterprise Implementation. This system

should provide improved data verification,

integration of improved data acquisition

tools, a fully capable model manager, enhanced user interface with visualization,

limited reporting across EMAP’s ecological resources, survey analysis methods

and interfaces, and internal data transformation methods.

1996–EMAP National Program within

EPA Enterprise Implementation. The system will provide interoperability with other

EPA programs. This should include enhanced data acquisition tools, accessible

metadata and methods using a Virtual

Repository, enhanced analysis and aggregation methods, a common user interFunctions Architecture Layers

User Interface

User Interface Tool Kit

Inter-Process

Communications

User Interface Layer

Inter-process Comm Layer

Modular Tool Set

(Applications)

GIS and Modeling

Visualization

Data Acquisition

Report Generator

Statistical Analysis

Software Back Plane Connection

Pointer/Browser/Access

Database Systems

Data Sets

Archived Data

Documents

Data Storage

Comm Access Layer

Security Layer

Virtual Repository Layer

Canonical Data Layer

Communication Access

Security

Virtual Repository

Data Dictionary

Config. Manager

Model Manager

CASE Tools

Directory

Catalog

Tool Set Layer
7

face across many EPA platforms, an

enhanced user interface featuring multimedia, and mechanisms for initial intraagency data exchange.

1997—EMAP Interagency Federation

Enterprise Implementation. System

interoperability among EMAP, EPA and

other agencies should provide external

data exchange.

EMAP IM Budget (1993 – 1997)

The budget estimates provided in this Plan

include requirements for Resource Group

field support teams, support for the IM Coordinator and EMAP Central, and hardware

and software costs. Using FY 93 as a

baseline, the figures for FY 94 - FY 97

include resources anticipated for EMAP from

all supporting Cooperative Partners and other

federal agencies.

Summary

The scope of this Plan extends from FY

93 through FY 97. However, EMAP IM

systems will continue to operate beyond

Figure 8. EMAP IM structure.

1997 as the user base expands. These

users will impose increasingly demanding

requirements that will become more pronounced as EMAP enters the EMAP Interagency Federation.

With the assimilation of increasing data

and information from other national and

international ecology-related programs,

EMAP IM is designed to become an “information highway.” It will serve as a powerful instrument for aggregating key environmental information to assist policy makers and managers at all levels in effecting

the positive changes necessary to preserve the global environment.

References

1. Environmental Monitoring and Assessment Program: Program Guide, June

1993.

2. The National Information Infrastructure:

Agenda for Action, September 15,

1993.

3. Zachman, J.A., A Framework for Information Systems Architecture, IBM

Systems Journal, Vol. 26, No. 3, 1987.

4. IBM: A Management System for the

Information Business, Vol. 1 — Management Overview, GE 20-0662-1,

1984.

Development Management Service

Strategic

Tactical

Operational

Developmental

Planning

Development

and

Maintenance

Strategic Planning

& Control

Management

Planning

Resource Planning

Resource Control

Administration

User Interaction

Requirements

Gathering

Development Management Service

Strategic

Tactical

Operational

•User Interaction &

Planning

•Resource Groups

•GIS

•Systems Engineering

•System Support &

Operations

•Coordinating Groups

•Resource Groups

•IM Coordinator

•Coordinating Groups

•Science Direction

•IM Coordinator

•System Architecture

•Technology Evaluation

•Coordinating Groups

•Resource Groups

•IM Coordinator

•Coordinating Groups

•Resource Groups

•User Interaction &

Planning

•Interagency Data

Interchange

•Resource Groups

•User Interaction &

Planning

•Coordinating

Groups

•Resource Groups

Figure 9. EMAP IM functions.
8

Figure 10. EMAP IM implementation schedule - POC.

Figure 11. EMAP IM implementation schedule - Technology Transfer.

Strategic planning

Tactical planning

Initiation/Concept

Definition/Design

User Interaction & Planning JAD sessions

Requirement specifications

Architecture

Standards

Data administration

QA planning

Configuration mgt planning

Security planning

Virtual Repository

Interagency Data Interchange

Directory/catalog

Develop/Implement/Operate

Systems Engineering

Database development

User interface development

GIS

GIS development

Systems Operations

System testing

System demonstration

Operational Systems

Central

Forests

Estuaries FY 93 FY 94

Final Milestone

Intermediate/

Initiation

Milestone

Strategic planning

Tactical planning

Initiation/Concept

Definition/Design

User Interaction & Planning

JAD sessions

Requirement specifications

Architecture

Standards

Data administration

QA planning

Configuration mgt planning

Security planning

Virtual Repository

Interagency Data Interchange

Directory/catalog

Systems Engineering

Database development

User interface development

GIS

GIS development

Systems Operations

System testing

System production Operational Systems

Develop/Implement/Operate

Surface Water/Agroecosystems

Other Resource Groups

Final Milestone

Intermediate/

Initiation

Milestone

FY 93 FY 94 FY 95
9

Figure 12. EMAP IM implementation schedule - Enterprise.

Figure 13. EMAP IM required budget.

Strategic planning

Tactical planning

Initiation/Concept

Definition/Design

User Interaction & Planning JAD sessions

Requirement specifications

Architecture

Standards

Data administration

QA planning

Configuration mgt planning

Security planning

Interagency Data Interchange

Directory/catalog

Develop/Implement/Operate

Systems Engineering

Database development

User interface development

GIS

GIS development

Systems Operations

System testing

System deployment

EPA Systems

STORET

Great Lakes / Others

As Required

Enterprise modeling

Adv Technology Evaluation

Pilots & prototypes (As Required)

Distributed query manager

Virtual Repository

Other Agency Systems

FY 94 FY 95 FY 96 FY 97

Final Milestone

Intermediate/

Initiation

Milestone

Expressed in Million $ 16.0

14.0

12.0

10.0

8.0

6.0

4.0

2.0

8.2 9.0

2.0

2.2

4.0

FY 93 FY 94 FY 95 FY 96 FY 97

1.8

2.2

11.4

1.5

4.5

12.9

1.0

5.6 4.9

1.0

12.2

Field Support EMAP Central Support Hardware and Software

5.0 5.4 6.3 6.3

0.0
10

The EPA author, Robert F. Shepanek, (also the EPA Project Officer, see below)

is with the Environmental Monitoring and Assessment Program, Washington,

DC 20460.

The complete report, entitled “EMAP Information Management Strategic Plan:

1993 – 1997,” (Order No. PB94-176823, Cost: $27.00, subject to change) will

be available only from:

National Technical Information Service

5285 Port Royal Road

Springfield, VA 22161

Telephone: 703-487-4650

The EPA Project Officer can be contacted at:

Environmental Monitoring and Assessment Program

U.S. Environmental Protection Agency

Washington, DC 20460

• •

United States

Environmental Protection Agency

Center for Environmental Research Information

Cincinnati, OH 45268

Official Business

Penalty for Private Use $300

EPA/620/SR-94/017

BULK RATE

POSTAGE & FEES PAID

EPA

PERMIT No. G-35