KEYWORDS: James Webb Space Telescope, Space operations, Observatories, Databases, Systems modeling, Space telescopes, Device simulation, Instrument modeling, System integration, Data modeling
The James Webb Space Telescope (JWST) Project has an extended integration and test (I&T) phase due to long
procurement and development times of various components as well as recent launch delays. The JWST Ground
Segment and Operations group has developed a roadmap of the various ground and flight elements and their use in the
various JWST I&T test programs. The JWST Project's building block approach to the eventual operational systems,
while not new, is complex and challenging; a large-scale mission like JWST involves international partners, many
vendors across the United States, and competing needs for the same systems. One of the challenges is resource
balancing so simulators and flight products for various elements congeal into integrated systems used for I&T and flight
operations activities.
This building block approach to an incremental buildup provides for early problem identification with simulators and
exercises the flight operations systems, products, and interfaces during the JWST I&T test programs. The JWST Project
has completed some early I&T with the simulators, engineering models and some components of the operational ground
system. The JWST Project is testing the various flight units as they are delivered and will continue to do so for the
entire flight and operational system. The JWST Project has already and will continue to reap the value of the building
block approach on the road to launch and flight operations.
KEYWORDS: James Webb Space Telescope, Ka band, Space operations, Databases, Satellites, Data processing, Space telescopes, Antennas, Observatories, Data communications
The James Webb Space Telescope (JWST) is the first NASA mission at the second Lagrange point (L2) to identify the
need for data rates higher than 10 megabits per second (Mbps). The JWST will produce approximately 235 gigabits (Gb)
of science data every day. In order to get this data downlinked to the Deep Space Network (DSN) at a sufficiently
adequate date rate, a Ka-band 26 gigahertz (GHz) frequency (as opposed to an X-band frequency) will be utilized. To
support the JSWT's utilizations of Ka-band, the DSN is upgrading its infrastructure. The range of frequencies in the Kaband
is becoming the new standard for high data rate science missions at L2. Given the Ka-band frequency range, the
issues of alternative antenna deployment, off-nominal scenarios, NASA implementation of the Ka-band at 26 GHz, and
navigation requirements will be discussed in this paper. The JWST is also using the Consultative Committee for Space
Data Systems (CCSDS) standard process for reliable file transfer using CCSDS File Delivery Protocol (CFDP). For the
JWST mission, the use of the CFDP protocol enables level zero processing at the DSN site. This paper will address
NASA implementation of ground stations in support of Ka-band 26 GHz and lessons learned from implementing a file
based protocol (CFDP).
KEYWORDS: James Webb Space Telescope, Databases, Space operations, Data archive systems, Standards development, Software development, Data centers, Space telescopes, Interfaces, Observatories
The James Webb Space Telescope (JWST) is part of a new generation of spacecraft acquiring large data volumes from
remote regions in space. To support a mission such as the JWST, it is imperative that lessons learned from the
development of previous missions such as the Hubble Space Telescope and the Earth Observing System mission set be
applied throughout the development and operational lifecycles. One example of a key lesson that should be applied is
that core components, such as the command and telemetry system and the project database, should be developed early,
used throughout development and testing, and evolved into the operational system. The purpose of applying lessons
learned is to reap benefits in programmatic or technical parameters such as risk reduction, end product quality, cost
efficiency, and schedule optimization. In the cited example, the early development and use of the operational command
and telemetry system as well as the establishment of the intended operational database will allow these components to be
used by the developers of various spacecraft components such that development, testing, and operations will all use the
same core components. This will reduce risk through the elimination of transitions between development and
operational components and improve end product quality by extending the verification of those components through
continual use. This paper will discuss key lessons learned that have been or are being applied to the JWST Ground
Segment integration and test program.
KEYWORDS: James Webb Space Telescope, Space telescopes, Mirrors, Sensors, Telescopes, Space operations, Stars, Observatories, Hubble Space Telescope, Galactic astronomy
The JWST project at the GSFC is responsible for the development, launch, operations and science data processing for the James Webb Space Telescope. The JWST project is currently in phase B with its launch scheduled for August 2011. The project is a partnership between NASA, ESA and CSA. The U.S. JWST team is now fully in place with the selection of Northrop Grumman Space Technology (NGST) as the prime contractor for the telescope and the Space Telescope Science Institute (STScI) as the mission operations and science data processing lead. This paper will provide an overview of the current JWST architecture and mission status including technology developments and risks.
KEYWORDS: Sensors, Satellites, Data processing, Data modeling, Earth observing sensors, Space operations, Data communications, Earth sciences, Antennas, Data centers
NASA's Earth Science Mission Operations and Systems (ESMOS) Project is responsible for developing and operating sensor data capture, processing and delivery systems on behalf of NASA's Earth Science Enterprise (ESE). As the volume of sensor data being collected by the next generation of Earth observing satellites continues to dramatically increase, the demand for timely data delivery has correspondingly increased. The ESMOS Project has utilized a variety of techniques and methodologies to provide sensor data to the end user, and has collected a series of lessons learned with regard to the most efficient implementations based on the needs of the end user. This paper discusses the successes achieved and the pitfalls encountered by NASA, NOAA and ESA and makes recommendations for changes and enhancements to maximize future mission sensor data processing.
Access to the requested content is limited to institutions that have purchased or subscribe to SPIE eBooks.
You are receiving this notice because your organization may not have SPIE eBooks access.*
*Shibboleth/Open Athens users─please
sign in
to access your institution's subscriptions.
To obtain this item, you may purchase the complete book in print or electronic format on
SPIE.org.
INSTITUTIONAL Select your institution to access the SPIE Digital Library.
PERSONAL Sign in with your SPIE account to access your personal subscriptions or to use specific features such as save to my library, sign up for alerts, save searches, etc.