|The EOSDIS Core System (ECS) must evolve and change through time in order to keep pace with new user requirements, new technologies, and new paradigms for data acquisition and distribution.
The ECS architecture has been designed to allow expansion of data providers to include any number of external sites. Realization of this capability was originally planned for ECS Release B (available in late 1997 in support of the AM-1 mission).
| Several options exist for interoperability with ECS, as described below in the "ECS Evolution" section.|
In determining the evolutionary path for ECS, the interoperability challenges of incorporating external data providers has recently been coupled with issues related to the role of ECS in a federated environment. In particular, what is the potential for re-use of ECS software components by ESIPs and other extended data providers? More detailed design information is provided below.
Points of Contact: Joe Senftle, email@example.com and Cheryl Croft, firstname.lastname@example.org
Curator: Karinn Hassan, email@example.com
Revised: May 8, 1997