|
|
 |
ESnet is a highly collaborative venture that involves the participation
of technical experts, scientific users, and governmental liaison
personnel. This broad spectrum of experts participates fully in
the management, operation, and planning of ESnet. The collaborative
quality of these processes ensures that user requirements are addressed
as equably as possible, given ESnet's finite resources.
Because of its collaborative nature, ESnet must function within
a framework of committees that facilitate user and technical participation
in ESnet processes. The committees and the relationships they
embody serve to focus the forces that are responsible for ESnet's
success. These committees also provide the framework within which
the ESnet community interacts, articulating its evolving vision
of network support for scientific endeavor.
Most of ESnet's planning processes are driven by the networking
requirements defined by the ER programs that participate in ESnet.
These requirements may originate from a variety of sources, but
all are eventually reviewed by the ESnet Steering Committee. In
general, new requirements are generated either by the introduction
of new computer applications or by the establishment of major new
scientific projects or facilities.
The march of technology spawns new computer and network applications
that frequently challenge prevailing conceptions of network operation.
In addition, new applications often generate increased network traffic
loads that need to be evaluated. As new applications are introduced,
they are assessed by ESnet personnel. If an application is deemed
sufficiently demanding, ESnet initiates an evaluation/planning process,
which may involve the participation of various ESnet individuals
and committees. Many application-driven plans require the participation
of technical experts who may reside at national laboratories or
universities. The ability to form teams or task forces to plan for
the implementation of new applications is the key to ensuring an
effective response by ESnet.
Major new projects and new scientific facilities usually generate
additional network demands that require ESnet to initiate a planning
process. Through its ESSC representative, a DOE program identifies
its networking requirements for evaluation by the Steering Committee
as a whole. Once these requirements are validated by the ESSC, responsibility
for evaluation and implementation is passed on to ESnet management.
If the new requirements have a major impact on the network, ESnet
management will generally forward its implementation plans to the
ESSC for review.
ESnet reviews its requirements periodically through the process
of revising its Program Plan, which identifies new applications,
services, and operational parameters. Between Program Plan revisions,
new services and requirements are usually documented in white papers,
which are approved by the ESSC with the concurrence of the OSC and
the ESnet management staff at NERSC.
The ESSC and the ESCC may collaborate to address an emergent situation
that requires a cross-organizational response. Such a response usually
entails leadership by a member of either the ESSC or the ESCC. That
committee member becomes that committee's designated liaison and
attends the other committee's meetings to report on activity and
to discuss issues.
Ad hoc subcommittees are formed within the ESSC and the ESCC
to address specific issues and services. The chairpersons of the
ESSC and the ESCC determine the need for such subcommittees and
appoint their leaders. If there are support issues to be resolved,
a representative of ESnet management will usually participate
in the subcommittee.
Operational processes are generally defined by the ESnet staff,
with complex processes documented in advance and reviewed by a subcommittee
or an interest group. There are special technology committees associated
with several specific ESnet services, such as videoconferencing,
directory services, and Open Systems Interconnection (OSI) implementation.
Appropriate ESnet staff members participate in these working groups,
which make it possible for service providers, end users, and facility
management personnel from national labs and universities to work
together very closely. This direct interaction optimizes the provision
of services and expedites changes in operational processes.
Situations occasionally arise that require focused administrative
and/or technical attention. Historically, ESnet has responded to
these situations by forming task forces or term-limited subcommittees.
If the issue is requirement driven or is a policy or administrative
matter, the subcommittee may include members from the ESSC. If the
issue is technical, the subcommittee is likely to include members
of the ESCC. If necessary, membership can include members of both
committees or noncommittee personnel. Generally, a task force will
either produce a white paper or present its findings in person to
the pertinent committee(s).
Through its Steering Committee, ESnet operations are reviewed periodically
to assure that management, technology, and capabilities are adequate
to meet the requirements detailed by the participating ER programs.
As a result of both technical and administrative reviews, ESnet
has modified its plans to accommodate new services and utilize new
technology. The most recent review has defined the basis on which
ESnet will move forward into the NII era.
As a result of the February 1994 review, it has been determined
that ESnet management will provide a yearly report of objectives
and goals by which ESnet accomplishments can be measured. This
report, along with the ESnet Annual Report produced
by the ESCC, will document the progress and deployment of new
technology, services, and capabilities.
ESnet also generates several performance measurements that are
used for network management. These measurements are made publicly
available on file servers. Alternatively, they may be electronically
distributed on a periodic basis. These measurements are useful
in determining whether network traffic patterns are changing.
They also document the effects of new users, programs, and facilities.
Go to the next section, Networking Committees
Go to the preceding section, ESnet History
Go to the Table of Contents
|
|
