United States
Environmental Protection
Agency
Environmental Monitoring and
Assessment Program
Washington, DC 20460
Research and Development
EPA/620/SR-94/017 August 1994
EPA Project Summary
EMAP Information Management
Strategic Plan: 1993-1997
Robert F. Shepanek
The Information Management (IM)
Strategic Plan for the Environmental
Monitoring and Assessment Program
(EMAP) describes how EMAP informa-
tion will be managed from field sam-
pling through the delivery of products
to the user. This plan cuts across the
entire EMAP and explains the process
for developing an information manage-
ment infrastructure that will enable
EMAP to achieve its long-term objec-
tives. This plan provides a strategy for
meeting hardware, software, documen-
tation support, and system designs that
will meet EMAP Resource and Coordi-
nating Group requirements. Users of
EMAP data and information are dis-
cussed in the Plan as well as the pro-
cess 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 re-
search project that is fully documented
in a separate report of the same title
(see Project Report ordering informa-
tion at back).
EMAP Commitment
The EMAP represents a long-term com-
mitment by the U.S. Environmental Pro-
tection Agency (EPA) to assess and peri-
odically document the status and condi-
tion of the Nation's ecological resources.
EMAP's goal is to monitor and assess the
condition of those resources and to con-
tribute to decisions on environmental pro-
tection and management.1 EMAP will moni-
tor indicators of the condition of our
Nation's ecological resources to respond
to the growing demand for information
characterizing the condition of our envi-
ronment and the type and location of en-
vironmental 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 ecologi-
cal resource categories.
Strategic Plan
The EMAP IM Strategic Plan outlines
the implementation approach for develop-
ment of workable information systems that
will meet the requirements of EMAP sci-
entists, information managers, and gov-
ernment decision makers. The Plan pro-
vides EPA management with the scope,
the foundation of requirements and guid-
ing principles, the management and tech-
nical approach, and resource requirements
for EMAP information systems develop-
ment. The Plan also provides EPA envi-
ronmental 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 geo-
graphic distribution of such ecological re-
sources as estuaries, lakes, streams, wet-
lands, forests, grasslands, and deserts.
By integrating information from several
government agencies, assessments and
reports will become available on the pro-
portions of these resources that are de-
grading or improving, their location and
extent, and their rate of change. Reported
-------
ecological conditions and geographical
coverage will be available with known con-
fidence.
By 2002, EMAP plans to expand its
monitoring and assessment capability to
include information from virtually all appli-
cable federal sources. Degrading and im-
proving trends will be identified through
specific indicators of how adversely af-
fected ecosystems are responding to con-
trol and mitigation programs.
By 2012, EMAP should be a focused,
mature program that is integrated with sci-
entific information from key national and
international sources. Trending informa-
tion of all ecosystems will be available for
use in making decisions concerning na-
tional and international environmental man-
agement and economic development.
EMAPIM
EMAP IM is the vehicle with which the
total EMAP manages data and informa-
tion. EMAP objectives and corresponding
EMAP IM objectives are shown in Figure
1. Specifically, EMAP IM will provide ef-
fective and extensible information man-
agement systems for assessing and re-
porting on the condition of the Nation's
ecological resources. IM will provide the
tools for turning raw scientific measure-
ments (data) into useful information prod-
ucts that will serve to guide actions to
improve the quality of our environment.
EMAP IM will be an environmental "infor-
mation 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." Scien-
tists will have access to data distributed
across a national network2 and the compu-
tational tools needed to facilitate analyses.
EMAP IM systems will provide access to
data, metadata, and processed informa-
tion for a diverse set of users through a
network of dispersed databases.
The EMAP Enterprise
The technical and management ap-
proaches discussed in the Plan require an
explanation of the term "enterprise." The
EMAP Enterprise, when fully developed,
will include Resource Groups, Coordinat-
ing 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 or-
der for EMAP to accomplish its objec-
tives. EMAP IM will eventually involve all
these users and will consider their differ-
ing requirements for information manage-
ment systems.
EMAP is and will continue to be an
evolving enterprise with diverse user re-
quirements. 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, ana-
lyzing data, and publishing results within
their ecological areas of responsibility.
Conversely, the aspect of the EMAP En-
terprise least developed is the relation-
ship 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 Sys-
tem 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 com-
prised of similar users, with similar mis-
sions, and in similar stages of develop-
ment. These user groups are aggregated
into four components by level of maturity.
Figure 2 shows these user group compo-
nents with the phased IM processes that
are applicable to each component. The
cells within this map depict the level of
user involvement. The "Enterprise Com-
ponents" of EMAP are
• Planning, Research, Monitoring, and
Assessment - includes indicator re-
search, collection and analysis of data,
and distribution of data and informa-
tion related to an ecological area of
responsibility. This component is com-
prised 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 infor-
mation products derived from multiple
Resource Groups. This component
includes Coordinating Groups support-
ing assessment activity by EMAP
Central.
• EMAP National Program component
within EPA - defines the relationship
of EMAP to other relevant EPA pro-
grams. These programs include the
Great Lakes National Program, The
Gulf of Mexico Program, the STORET
Modernization within the Office of
Water, the Gateway/Envirofacts pro-
gram within the Office of Information
Resource Management and others.
This component also includes con-
nections to appropriate EPA adminis-
trative programs.
• EMAP as partner in an Interagency
Federation - defines the relationship
of EMAP to relevant programs out-
side of EPA that are not already in-
cluded in other EMAP Enterprise com-
ponents by virtue of their cooperative
partner status. Examples of the types
of programs targeted are NASA's
EOS/DIS and the Global Change Re-
search Program.
Each EMAP IM process includes an
execution of the systems development life
cycle (SDLC) and results with an opera-
tional information management system for
the designated user. For example, For-
ests 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 com-
munications 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 scien-
tific community actively participating in EMAP.
These principal users will be scientists in the
EMAP Resource and Coordinating Groups,
other EPA scientists, and such EMAP Coop-
erative Partners as the National Oceano-
graphic and Atmospheric Administration
(NOAA) and the U.S. Forest Service
(USFS). These users have primary re-
sponsibility for planning, designing, col-
lecting, 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 pri-
vate sector scientists and researchers
working on behalf of government, aca-
demic, 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 infor-
mation as an ecological report card.
Eventually, users of EMAP data and
information will range from scientists who
will extract crosscutting data sets for de-
tailed quantitative analyses to members
of Congress, the general public, and the
news media who require qualitative infor-
mation products. A histogram at Figure 4
depicts relative differences in user involve-
ment by EMAP Enterprise components.
The makeup of the groups representing
-------
Program Objectives
IM Objectives
Estimate the current status,
trends, and changes in selected
indicators of the condition of
the Nation's ecological
resources on a regional basis
with known confidence.
Estimate the geographic cover-
age and extent of the Nation's
ecological resources with
known confidence.
Seek associations between in-
dicators of natural and anthro-
pogenic stresses and indicators
of condition of ecological
resources.
Provide annual statistical
summaries and periodic as-
sessments of the Nation's
ecological resources.
Assist in structuring, developing, maintaining, operating,
and/or deploying:
Resource Group databases for research, monitoring,
and analysis;
- Access mechanisms to the databases;
Manipulation mechanisms (algorithms); and
Display mechanisms required for research, monitoring, and
analysis.
Assist in structuring, developing, maintaining, operating, or
deploying:
Access mechanism to EMAP Geographic Reference Data
(GRD);
Manipulation mechanisms (algorithms); and
Display mechanisms required to analyze this information.
Ensure a distributed database structure that allows integra-
tion of information internally, and with external sources al-
lowing responsibility for the data to reside with the "owners."
Assist in the development, maintenance, operation, and
deployment of crosscutting tools.
Ensure that all data, metadata, and information required to
meet the objective are available, in some cases by leveraging
the central node of the database system.
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 >w
Processes y^
Proof
of
Concept
Technology
Transfer
Enterprise
Implementation
Planning
Research
Monitoring &
Assessment
Forests
and
Estuaries
All
Resource
Groups
Integration
and
Assessment
Limited
Coordinating
Groups
All Resource
Groups/
Limited
Coordinating
Groups
All Resource
and
Coordinating
Groups
EMAP
National
Program
EPA
Interactions
EMAP
Interagency
Federation
Interagency
Interactions
System Development
Life Cycle
Figure 2. The EMAP enterprise.
-------
Public
Other
EMAP IM
Users
' Use information as an
ecological report card
' Policy Makers/
Management
Use information to determine policy
and guidance
"Other Scientists
Use data/info for educational, scientific,
and commercial purposes
r Other EPA
7
Use data/information for research
and analysis
'Coordinating Groups
Support scientists with data, info,
analysis tools and processes
' Resource Group
Scientists
Plan for, collect, validate, catalog,
and assess data
Figure 3. EMAP IM users.
the requirements of an EMAP Enterprise
component has been structured to exert a
leveling effect on the requirements gath-
ering process. For example, although the
POC is primarily driven by EMAP scien-
tists, some policy makers and other scien-
tists 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 imple-
mentation will be based on these guide-
lines:
• Use existing national infrastructure
and standards whenever possible;
• Concentrate on integration engineer-
ing rather than new system develop-
ment;
• Use a systems engineering approach
based on a formal design process
incorporating functional pilots and pro-
totypes; and
• Use emerging technology whenever
possible in meeting user needs.
Evolutionary Approach
EMAP IM is designed to use an "evolu-
tionary" systems engineering approach that
adapts to emerging user needs and tech-
nology. This approach will permit ongoing
use of operational systems while the de-
velopment process continues. The distin-
guishing 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 ac-
count current and projected user needs
and technology and incorporate user feed-
back 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 or-
derly approach for designing and building
systems. It provides system developers a
complete template against which to map
sequential and/or parallel steps for carry-
ing out development of technical and man-
agement solutions.
The Zachman Framework stresses that
the information system development pro-
cess requires several architectures. Fig-
ure 6 depicts the Framework architec-
tures: 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 Frame-
work. This iterative process will be ap-
plied to each subsequent Enterprise com-
ponent during the three IM implementa-
tion processes: POC, Technology Trans-
fer, and Enterprise Implementation.
Using such a checklist ensures that all
aspects of the system are addressed from
an "enterprise approach" and that all par-
ticipants in the development and imple-
mentation of the Enterprise have a com-
mon 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 technol-
ogy-independent model to accommodate
emerging hardware development and soft-
ware changes.
EMAP IM Architecture
Another view of the EMAP architecture
is provided by the seven layer model de-
picted in Figure 7. (It should be noted that
these architecture functions will be pro-
vided, to varying degrees, by dispersed
systems at multiple nodes.) Forming the
foundation of the architecture is the ca-
nonical data layer. It is comprised of data-
bases and data sets that can be accessed
by tools from the tool set layer.
-------
Public
Policy Makers
Other Science
Other EPA
Coord Gp
Resource Gp
Public
Policy Makers
Other Science
Other EPA
Coord Gp
Resource Gp
3
3
]
=
1
1
]
=
Planning, Research, Monitoring, and Integration and Assessment
Assessment
1
^=1
D
=1
1
1
I
^=1
=i
^
^
^
EMAP National Program EMAP Interagency Federation
Figure 4. Relative user involvement by EMAP IM component.
Resource Groups
Coordinating Groups
Resource Groups**
Coordinating Groups
Cooperative Partners
STORET, EnviroFacts
Other EPA Sources •'
• EOS/DIS, NBS
Other Data Sources
Annual
Statistical
Summaries
Integration &
Assessment
Reports
Administrative
Products
Figure 5. EMAP enterprise products.
Above the database layer is the Virtual
Repository layer. The components of the
Virtual Repository are model manage-
ment 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 direc-
tory and catalog components of the Vir-
tual Repository layer contain scientific
metadata that describe data sets and docu-
ments.
The security layer provides a means for
EMAP to ensure the long-term integrity of
its collection by controlling access. Secu-
rity procedures, in practice, can apply at
the user interface layer, the communica-
tions 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 con-
nects 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 vari-
ous 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 Manage-
ment, who heads one of the eight Coordi-
nating Groups, is responsible for EMAP
IM. The IM Coordinator relies on mem-
bers 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 man-
agement 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 ar-
chitecture, science direction, user inter-
action and planning, interagency data in-
terchange, advanced technology evalua-
tion, systems engineering, and systems
support and operations. Each of these
teams has specific roles within the man-
agement structure (Figure 9). Additionally,
ongoing coordination is required with fed-
eral and EPA information resources man-
agement programs and offices.
EMAP IM Implementation
Processes
EMAP IM development and implemen-
tation consist of three IM process
phases. First is the POC process that
identifies and applies standards, poli-
cies, tools, and procedures to the For-
-------
EMAP Process
Development
Life Cycle
~>»
Architecture Framework
Scope
Enterprise
Model
Information
System
Model
Technology
Model
Components
Functioning
System
Data
x
Function
\
\
Proof
/
/
/
Network
People
1
of Concept
(Technology Trar
1 1 "^
y
Time
sfer
1
\
Motivation
Figure 6. EMAP architecture framework.
Functions
User Interface
GIS and Modeling .
Modular Tool Set Visualization A
(Applications) Data Acquisition m
Report Generator ^
Statistical Analysis '
Software Back Plane Connection < ~>
Pointer/Browser/Access
Data Storage Database Systems k
Data Sets A
Archived Data V
Documents r
Architecture
User Interface
Tool Kit
Inter-Process
Communications
•••
Communication Access
Security
Virtual Repc
Data Dictionary
Config. Manager
Model Manager
CASE Tools
—
—
u
sitory
Directory
Catalog
—
• ••
—
Layers
User Interface Layer
Inter-process Comm Layer
Tool Set Layer
Comm Access Layer
Security Layer
Virtual Repository Layer
Canonical Data Layer
Figure 7. EMAP IM architecture.
est and Estuaries Resource Groups and
limited Coordinating Groups. The Tech-
nology Transfer phase consists of ex-
tending the environment validated dur-
ing the POC to the remaining Resource
Groups and an increasing number of
Coordinating Groups. The third process
is Enterprise Implementation, which en-
gages other EPA and non-EPA pro-
grams in the systems development pro-
cess. This phase re-engineers preced-
ing 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 pro-
gram function into general SDLC catego-
ries 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 par-
ticipation from other user categories. For
example, all Resource and Coordinating
Groups have been observing the Plan-
ning, Research, Monitoring, and /Assess-
ment 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 tech-
nical and management approaches speci-
fied 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, Geo-
graphic Information Systems (GIS), and
user interface capabilities commenced with
the 1993 POC.
1993-Research, Monitoring, and As-
sessment 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 per-
form internal data exchange adhering to
established OIRM data standards.
1995-lntegration and Assessment En-
terprise Implementation. This system
should provide improved data verification,
integration of improved data acquisition
tools, a fully capable model manager, en-
hanced user interface with visualization,
limited reporting across EMAP's ecologi-
cal resources, survey analysis methods
and interfaces, and internal data transfor-
mation methods.
1996-EMAP National Program within
EPA Enterprise Implementation. The sys-
tem will provide interoperability with other
EPA programs. This should include en-
hanced data acquisition tools, accessible
metadata and methods using a Virtual
Repository, enhanced analysis and ag-
gregation methods, a common user inter-
-------
Strategic
Tactical
Operational
Development
^
Developmental '
Planning
^
^^^
Development -.
and
Maintenance
Management
Strategic Planning
& Control
^^
\
^ \
1 ^**\^
Management \
•* Planning —A
<
<
JResource Planning
^r
1
^
' \
„ Resource Control
4
Administration
Service
^
- Requirements
[ Gathering
V-^
1
sA
Figures. EMAP IM structure.
Strategic
Tactical
Operational
Development
•User Interaction &
Planning
•Resource Groups
•CIS
•Systems Engineering
•System Support &
Operations
•Coordinating Groups
•Resource Groups
Management
•IM Coordinator
•Coordinating Groups
•Science Direction
•IM Coordinator
•System Architecture
•Technology Evaluation
•Coordinating Groups
•Resource Groups
•IM Coordinator
•Coordinating Groups
•Resource Groups
Service
•User Interaction &
Planning
•Interagency Data
Interchange
•Resource Groups
•User Interaction &
Planning
•Coordinating
Groups
•Resource Groups
1997 as the user base expands. These
users will impose increasingly demanding
requirements that will become more pro-
nounced as EMAP enters the EMAP In-
teragency Federation.
With the assimilation of increasing data
and information from other national and
international ecology-related programs,
EMAP IM is designed to become an "in-
formation highway." It will serve as a pow-
erful instrument for aggregating key envi-
ronmental information to assist policy mak-
ers and managers at all levels in effecting
the positive changes necessary to pre-
serve the global environment.
References
1. Environmental Monitoring and Assess-
ment Program: Program Guide, June
1993.
2. The National Information Infrastructure:
Agenda for Action, September 15,
1993.
3. Zachman, J.A., A Framework for In-
formation Systems Architecture, IBM
Systems Journal, Vol. 26, No. 3, 1987.
4. IBM: A Management System for the
Information Business, Vol. 1 — Man-
agement Overview, GE 20-0662-1,
1984.
Figure 9. EMAP IM functions.
face across many EPA platforms, an
enhanced user interface featuring multi-
media, and mechanisms for initial intra-
agency 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 Coor-
dinator 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
-------
Initiation/Concept
Strategic planning
Tactical planning
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/I mplement/Operate
Systems Engineering
Database development
User interface development
CIS
CIS development
Systems Operations
System testing
System demonstration
Operational Systems
Central
Forests
Estuaries
FY93
-±. Final Milestone
^, Intermediate/
Initiation
Milestone
Figure 10. EMAP IM implementation schedule - POC.
Initiation/Concept
Strategic planning
Tactical planning
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/l mplement/Operate
Systems Engineering
Database development
User interface development
CIS
CIS development
Systems Operations
System testing
System production
Operational Systems
Surface V\foter/Agroecosystems
Other Resource Groups
FY93
FY94
•A. Final Milestone
•A. Intermediate/
Initiation
Milestone
FY95
Figure 11. EMAP IM implementation schedule - Technology Transfer.
-------
Initiation/Concept
Strategic planning
Tactical planning
Definition/Design
User Interaction & Planning
JAD sessions
Requirement specifications
Enterprise modeling
Architecture
Standards
Data administration
QA planning
Configuration mgt planning
Security planning
Interagency Data Interchange
Directory/catalog
Adv Technology Evaluation
Pilots & prototypes
Develop/lmplement/Operate
Systems Engineering
Database development
User interface development
Distributed query manager
Virtual Repository
CIS
CIS development
Systems Operations
System testing
System deployment
EPA Systems
STORE!
Great Lakes/Others
Other Agency Systems
As Required
FY94
1
A A
\
&
j\
FY95
I I I
U J
^
A A
AL
A
^
FY96
I I I
-± Final Milestone
ivinesione
, ^
^
A A
A ^^^^A
A A A
FY97
1 1 1
Figure 12. EMAP IM implementation schedule - Enterprise.
FY93
FY94
FY95
FY96
FY97
I Field Support
I EMAP Central Support
I Hardware and Software
Figure 13. EMAP IM required budget.
-------
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
BULK RATE
POSTAGE & FEES PAID
EPA
PERMIT No. G-35
EPA/620/SR-94/017
------- |