Search NASA⌕ Search

NASA NTRS · 20060051689

Implementing Distributed Operations: A Comparison of Two Deep Space Missions

Abstract

Two very different deep space exploration missions--Mars Exploration Rover and Cassini--have made use of distributed operations for their science teams. In the case of MER, the distributed operations capability was implemented only after the prime mission was completed, as the rovers continued to operate well in excess of their expected mission lifetimes; Cassini, designed for a mission of more than ten years, had planned for distributed operations from its inception. The rapid command turnaround timeline of MER, as well as many of the operations features implemented to support it, have proven to be conducive to distributed operations. These features include: a single science team leader during the tactical operations timeline, highly integrated science and engineering teams, processes and file structures designed to permit multiple team members to work in parallel to deliver sequencing products, web-based spacecraft status and planning reports for team-wide access, and near-elimination of paper products from the operations process. Additionally, MER has benefited from the initial co-location of its entire operations team, and from having a single Principal Investigator, while Cassini operations have had to reconcile multiple science teams distributed from before launch. Cassini has faced greater challenges in implementing effective distributed operations. Because extensive early planning is required to capture science opportunities on its tour and because sequence development takes significantly longer than sequence execution, multiple teams are contributing to multiple sequences concurrently. The complexity of integrating inputs from multiple teams is exacerbated by spacecraft operability issues and resource contention among the teams, each of which has their own Principal Investigator. Finally, much of the technology that MER has exploited to facilitate distributed operations was not available when the Cassini ground system was designed, although later adoption of web-based and telecommunication tools has been critical to the success of Cassini operations.

Explore related subjects

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Mishkin, Andrew, Larsen, Barbara. 2006-01-01. Implementing Distributed Operations: A Comparison of Two Deep Space Missions. https://ntrs.nasa.gov/citations/20060051689

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related reports

Cassini's Test Methodology for Flight Software Verification and Operations

The Cassini spacecraft was launched on 15 October 1997 on a Titan IV-B launch vehicle. The spacecraft is comprised of various subsystems, including the Attitude and Articulation Control Subsystem (AACS). The AACS Flight Software (FSW) and its development has been an ongoing effort, from the design, development and finally operations. As planned, major modifications to certain FSW functions were designed, tested, verified and uploaded during the cruise phase of the mission. Each flight software upload involved extensive verification testing. A standardized FSW testing methodology was used to verify the integrity of the flight software. This paper summarizes the flight software testing methodology used for verifying FSW from pre-launch through the prime mission, with an emphasis on flight experience testing during the first 2.5 years of the prime mission (July 2004 through January 2007).

Cassini Mission↗

The Atmospheres of Saturn and Titan in the Near-Infrared: First Results of Cassini/VIMS

The wide spectral coverage and extensive spatial, temporal, and phase-angle mapping capabilities of the Visual Infrared Mapping Spectrometer (VIMS) onboard the Cassini-Huygens Orbiter are producing fundamental new insights into the nature of the atmospheres of Saturn and Titan. For both bodies, VIMS maps over time and solar phase angles provide information for a multitude of atmospheric constituents and aerosol layers, providing new insights into atmospheric structure and dynamical and chemical processes. For Saturn, salient early results include evidence for phosphine depletion in relatively dark and less cloudy belts at temperate and mid-latitudes compared to the relatively bright and cloudier Equatorial Region, consistent with traditional theories of belts being regions of relative downwelling. Additional Saturn results include (1) the mapping of enhanced trace gas absorptions at the south pole, and (2) the first high phase-angle, high-spatial-resolution imagery of CH4 fluorescence. An additional fundamental new result is the first nighttime near-infrared mapping of Saturn, clearly showing discrete meteorological features relatively deep in the atmosphere beneath the planet's sunlit haze and cloud layers, thus revealing a new dynamical regime at depth where vertical dynamics is relatively more important than zonal dynamics in determining cloud morphology. Zonal wind measurements at deeper levels than previously available are achieved by tracking these features over multiple days, thereby providing measurements of zonal wind shears within Saturn's troposphere when compared to cloudtop movements measured in reflected sunlight. For Titan, initial results include (1) the first detection and mapping of thermal emission spectra of CO, CO2, and CH3D on Titan's nightside limb, (2) the mapping of CH4 fluorescence over the dayside bright limb, extending to approximately 750 km altitude, (3) wind measurements of approximately 0.5 ms(exp -1), favoring prograde, from the movement of a persistent (multiple months) south polar cloud near 88 deg S latitude, and (4) the imaging of two transient mid-southern-latitude cloud features.

Cassini Mission↗