SEARCH · Search NASA
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
The paper will then propose extending this multi-mission philosophy to skeleton timeline development, science sequencing, and spacecraft sequencing. Finally, the paper will investigate a multi-mission approach to MOS development.
Explore the source record for details and available documents.
The Multimission Three-Axis Stabilized Spacecraft (MTASS) Flight Dynamics Support System (FDSS) has been developed in an effort to minimize the costs of ground support systems. Unlike single-purpose ground support systems, which attempt to reduce costs by reusing software specifically developed for previous missions, the multimission support system is an intermediate step in the progression to a fully generalized mission support system in which numerous missions may be served by one general system. The benefits of multimission attitude ground support systems extend not only to the software design and coding process, but to the entire system environment, from specification through testing, simulation, operations, and maintenance. This paper reports the application of an MTASS FDSS to multiple scientific satellite missions. The satellites are the Upper Atmosphere Research Satellite (UARS), the Extreme Ultraviolet Explorer (EUVE), and the Solar Anomalous Magnetospheric Particle Explorer (SAMPEX). Both UARS and EUVE use the multimission modular spacecraft (MMS) concept. SAMPEX is part of the Small Explorer (SMEX) series and uses a much simpler set of attitude sensors. This paper centers on algorithm and design concepts for a multimission system and discusses flight experience from UARS.
The Operations Engineering Lab (OEL) at JPL has developed the multimission command system as part of JPL's Advanced Multimission Operations System. The command system provides an advanced multimission environment for secure, concurrent commanding of multiple spacecraft. The command functions include real-time command generation, command translation and radiation, status reporting, some remote control of Deep Space Network antenna functions, and command file management. The mission-independent architecture has allowed easy adaptation to new flight projects and the system currently supports all JPL planetary missions (Voyager, Galileo, Magellan, Ulysses, Mars Pathfinder, and CASSINI). This paper will discuss the design and implementation of the command software, especially trade-offs and lessons learned from practical operational use. The lessons learned have resulted in a re-engineering of the command system, especially in its user interface and new automation capabilities. The redesign has allowed streamlining of command operations with significant improvements in productivity and ease of use. In addition, the new system has provided a command capability that works equally well for real-time operations and within a spacecraft testbed. This paper will also discuss new development work including a multimission command database toolkit, a universal command translator for sequencing and real-time commands, and incorporation of telecommand capabilities for new missions.
The Mission Design and Navigation (MDNAV) Section at the Jet Propulsion Laboratory (JPL) supports many deep space and earth orbiting missions from formulation to end of mission operations. The requirements of these missions are met with a multimission approach to MDNAV ground data system (GDS) infrastructure capable of being shared and allocated in a seamless and consistent manner across missions. The MDNAV computing infrastructure consists of compute clusters, network attached storage, mission support area facilities, and desktop hardware. The multimission architecture allows these assets, and even personnel, to be leveraged effectively across the project lifecycle and across multiple missions simultaneously. It provides a more robust and capable infrastructure to each mission than might be possible if each constructed its own. It also enables a consistent interface and environment within which teams can conduct all mission analysis and navigation functions including: trajectory design; ephemeris generation; orbit determination; maneuver design; and entry, descent, and landing analysis. The savings of these efficiencies more than offset the costs of increased complexity and other challenges that had to be addressed: configuration management, scheduling conflicts, and competition for resources. This paper examines the benefits of the multimission MDNAV ground data system infrastructure, focusing on the hardware and software architecture. The result is an efficient, robust, scalable MDNAV ground data system capable of supporting more than a dozen active missions at once.
This paper will discuss the design and implementation of the command software, especially trade-offs and lessons learned from practical operational use in JPL's Advanced Multimission Operations System.The command system provides an advanced multimission environment for secure, concurrent commanding of multiple spacecraft. The lessons learned have resulted in a re-engineering of the command system, especially in its user interface and new automation capabilities. This paper will also discuss new development work including a multimission command database toolkit, a universal command translator for sequencing and real-time commands, and incorporation of telecommand capabilities for new missions.
The development of a multimission military aircraft would be highly desirable both from the standpoint of easing the strain on the national budget by reducing the number of aircraft types and of providing versatility which would increase the effectiveness of the aircraft in the performance of a given mission. Some of the capabilities which might be required of such an aircraft are shown in figure 1 along with their respective aerodynamic and configuration requirements. The first three capabilities are grouped together since they all require good subsonic characteristics. The first, a long loiter capability for combat air patrol and the second, a long ferry range for efficient aircraft deployment both require a high subsonic lift-drag ratio. The third capability, STOL, is desirable for carrier and short-field operation and requires the development of high lift. All three of these capabilities can best be obtained with a high-aspect-ratio wing having a large span and a low-sweep angle. The fourth capability is that of a high-altitude supersonic attack or intercept and requires a high lift-drag ratio at supersonic speeds which dictates a rather slender configuration with a moderate-span wing which is either very thin or highly swept. The fifth capability listed in figure 1 is that of a low-altitude high-speed attack that would increase the probability of long-range penetration of antiaircraft defenses. The high dynamic pressures encountered on the deck at high speeds require a low-lift-curve slope to reduce the gust-induced normal accelerations, and low friction and wave drag (drag due to lift is insignificant at high dynamic pressures) to assure sufficient speed and range. In order to best satisfy these requirements, a slender aircraft having little or no wing is required. It is apparent from figure 1 that these five capabilities are highly incompatible and that an efficient multimission aircraft will require a means of varying its aerodynamic characteristics. This can be best accomplished with some type of variable-wing geometry. There are, of course, several types of variable wing geometry. However, in view of the extremely large variations in wing span desired, variable wing sweep, as indicated In the lower right sketch of figure 1, appears to provide the best method. The Langley Research Center of the National Aeronautics and Space Administration has therefore initiated a research program to provide the aerodynamic information needed for the development of a variable-sweep multimission military aircraft, and it is the purpose of this paper to briefly describe some of the results of this program.
JPL's Multimission Operations Systems Office (MOSO) provides a multimission facility at JPL for processing science instrument data from NASA's planetary missions. This facility, the Multimission Image Processing System (MIPS), is developed and maintained by MOSO to meet requirements that span the NASA family of planetary missions. Although the word 'image' appears in the title, MIPS is used to process instrument data from a variety of science instruments. This paper describes the design of a new system architecture now being implemented within the MIPS to support future planetary mission activities at significantly reduced operations and maintenance cost.
Servicing economics for LANDSAT are examined. The following objectives of the multimission modular spacecraft are outlined: retrieval; multimission capability; standard flight support system; standard hardware; repair and refurbishment on orbit; instrument replacement; standard ground support system; and standard software.
As part of the Network Consolidation Program, the 26-meter Tracking and Communication Subnet was transferred to JPL. Along with this transfer JPL assumed responsibility for tracking and navigation support for Earth orbiter missions normally tracked by the 26-meter sites. The High Earth Orbiter (HEO) Multimission Navigation Facility was formed as a component of the Deep Space Network (DSN) Tracking System for the purpose of supporting Earth orbiter missions and certain classes of deep space missions. This facility has been implemented on a dedicated VAX 11/780 minicomputer within the Network Operations Control Center (NOCC). The primary function of the system is to process radio metric data and estimate the orbit of a spacecraft in near-Earth or deep space environment. The system is capable of processing radio metric data in near-real time and providing the quick turnaround required for Earth orbiter operations. It is also capable of generating precision spacecraft ephemeris for use by the NOCC Support Subsystem and external agencies. This article discusses the implementation and functional operation of the Multimission Navigation Subsystem and describes the support that has been provided for an array of missions.
As baselined, the Cassini Ground Data System (GDS) will be composed of Project specific and multimission elements. The former will be developed by the Cassini Project and the latter by two JPL institutional organizations, the Telecommunications and Data Acquisition Office (TDA) and the Multimission Operations Systems Office (MOSO). The GDS will be developed in three principal phases: Spacecraft Test, Launch-cruise, and Science Tour, with a significant part of the development deferred until the post-launch period. New capabilities are being introduced that are key to the achievement of more cost effective operations. Successful development of the system will require careful planning and will involve participation of diverse disciplines. This paper introduces the Cassini Project from the Ground Data System perspective and discusses development approaches expected to produce systems which meet functional and performance requirements and which will be delivered on schedule and within budget.
The Extreme Ultraviolet Explorer (EUVE) was launched June 7, 1992 by an expendable Delta 2 launch vehicle. The Flight Dynamics Facility (FDF) at NASA Goddard Space Flight Center used a multimission three-axis stabilized spacecraft (MTASS) Flight Dynamics Support System (FDSS) to support the EUVE launch and mission operations. For EUVE, MTASS has been used to monitor attitude sensor performance, study OBC attitude determination performance, and study attitude perturbations. The current status of these efforts are summarized. After its successful implementation for EUVE, the Upper Atmosphere Research Satellite (UARS), and the Solar Anomalous and Magnetospheric Particle Explorer (SAMPEX), MTASS has demonstrated multimission flight dynamics support systems can effectively bridge the gap between single-mission support systems of the past and future generic systems.
JPL's Multimission Operations System Office (MOSO) provides a multimission facility at JPL for processing science instrument data from NASA's planetary missions.
The Multimission VICAR Planner (MVP) system is an AI planning system which constructs.
The Multimission VICAR Planner (MVP) system is an AI planning system which constructs.
This paper will describe lessons learned in adapting JPL's Multimission Ground Data System (MGDS) to fly the Voyager, Galileo, and Mars Observer missions. We will explain how powerful, existing ground data systems can be adapted and packaged in a cost effective way for operations of small and large planetary missions. We will also describe how the MGDS was adapted to support operations within the Galileo Spacecraft Testbed. The Galileo testbed provided a unique opportunity to adapt MGDS to support command and control operations for a small autonomous operations team with a handful of engineers flying the Galileo Spacecraft flight system model.
JPL's Multimission Operatins Systems Office (MOSO) provides a multimissin facility at JPL for processing science instrument data from NASA's planetary missions.
Scientific payloads integration with multimission electric propulsion interplanetary spececraft, discussing possible contamination effects due to solar electric propulsion system