Earth observing system (EOS) data and information system (EOSDIS) — evolution update and future

NASA develops and utilizes a variety of large and small scale data systems to meet its Earth science objectives. Generally, the data systems are considered “Core Capabilities” providing the basic infrastructure needed to capture data from space–borne instruments as well as process, archive and distribute science data products to the user community. The Earth Observing System (EOS) Data and Information System (EOSDIS) is an example of NASA’s Core Capabilities. Another class of capabilities, which may be called “Community Capabilities”, is generally selected through peer review to support NASA’s Earth science programs. Both Core and Community Capabilities are necessary not only to serve the basic needs of the broad and diverse community of over 200,000 users of NASA’s Earth science data but also to improve and enhance the science insight for a variety of research and science applications. As information technology changes at a quick pace and new capabilities become readily available, users’ expectations increase as well. Data systems’ organizations need to be dynamic and adapt to these changes. While both Core and Community Capabilities must be adaptive, the pace at which adaptation occurs generally differs between the two. Core Capabilities typically have stricter operations and performance requirements serving a large community. These systems tend to be slower in changing whereas the Community Capabilities can be early adopters of new technologies since any impacts affect a much smaller community. Evolution of EOSDIS, based on a NASA–established vision for circa 2015 has been in implementation since early 2006. The vision emphasizes increased end–to–end data system efficiency and operability; increased data usability; improved support for end users; and decreased operations costs. Due to concurrent operations, the transition of operations to newer systems is being carried out incrementally. This paper provides a summary of the implementation, transition to operations and the lessons learned.