Search NASA⌕ Search

SEARCH · Search NASA

Results for “multi mission”

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.

At least 163 records · Page 9

A Sustained Proximity Network for Multi-Mission Lunar Exploration

Tbe Vision for Space Exploration calls for an aggressive sequence of robotic missions beginning in 2008 to prepare for a human return to the Moon by 2020, with the goal of establishing a sustained human presence beyond low Earth orbit. A key enabler of exploration is reliable, available communication and navigation capabilities to support both human and robotic missions. An adaptable, sustainable communication and navigation architecture has been developed by Goddard Space Flight Center and the Jet Propulsion Laboratory to support human and robotic lunar exploration through the next two decades. A key component of the architecture is scalable deployment, with the infrastructure evolving as needs emerge, allowing NASA and its partner agencies to deploy an interoperable communication and navigation system in an evolutionary way, enabling cost effective, highly adaptable systems throughout the lunar exploration program.

Soloff, Jason A.↗

Multi-Mission Strategic Technology Prioritization Study

This viewgraph presentation provides an overview of a pilot study intended to demonstrate in an auditable fashion how advanced space technology development can best impact future NASA missions. The study was a joint project by staff members of NASA's Jet Propulsion Laboratory (JPL), and Goddard Space Flight Center (GSFC). The other goals of the study were to show an approach to deal effectively with inter-program analysis trades, and to explore the limits of these approaches and tools in terms of what can be realistically achieved.

Weisbin, C. R.↗

Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being reengineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEiX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the reengineering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team s experiences with integrating multiple missions into a fleet-based automated ground system.

Madden, Maureen↗

Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being re-engineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the re-enginering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team's experiences with integrating multiple missions into a fleet-automated ground system.

Madden, Maureen↗

Multi-mission ground data systems - breakthroughs and challenges

Given the cost-constrained nature of JPL Flight Projects, especially Discovery Class missions, there is more and more pressure to reduce the costs associated with mission operations, particularly the costs for the Ground Data System. This paper explores the successes (and failures) of using the Mission Management Office (MMO) GDS team to provide a common set of services, tools, procedures, and products to JPL Flight Projects.

GDS↗

Science opportunity analyzer - a multi-mission approach to science planning

In the past Science Planning for space missions has been comprised of using ad-hoc software toolscollected or reconstructed from previous missions, tools used by other groups who often speak a different 'technical' language or even 'the backs of envelopes'. In addition to the tools being rough, the work done with these tools often has had to be redone or at least re-entered when it came time to determine actual observations. Science Opportunity Analyzer (SOA), a Java-based application, has been built for scientists to enable them to identify/analyze observation opportunities and then, to create corresponding observation designs.

Science opportunity analyzer science planning SOA ↗

Science opportunity analyzer - a multi-mission tool for planning

For many years the diverse scientific community that supports JPL's wide variety ofinterplanetary space missions has needed a tool in order to plan and develop their experiments. The tool needs to be easily adapted to various mission types and portable to the user community. The Science Opportunity Analyzer, SOA, now in its third year of development, is intended to meet this need. SOA is a java-based application that is designed to enable scientists to identify and analyze opportunities for science observations from spacecraft. It differs from other planning tools in that it does not require an in-depth knowledge of the spacecraft command system or operation modes to begin high level planning. Users can, however, develop increasingly detailed levels of design. SOA consists of six major functions: Opportunity Search, Visualization, Observation Design, Constraint Checking, Data Output and Communications. Opportunity Search is a GUI driven interface to existing search engines that can be used to identify times when a spacecraft is in a specific geometrical relationship with other bodies in the solar system. This function can be used for advanced mission planning as well as for making last minute adjustments to mission sequences in response to trajectory modifications. Visualization is a key aspect of SOA. The user can view observation opportunities in either a 3D representation or as a 2D map projection. The user is given extensive flexibility to customize what is displayed in the view. Observation Design allows the user to orient the spacecraft and visualize the projection of the instrument field of view for that orientation using the same views as Opportunity Search. Constraint Checking is provided to validate various geometrical and physical aspects of an observation design. The user has the ability to easily create custom rules or to use official project-generated flight rules. This capability may also allow scientists to easily impact the cost to science if flight rule changes occur. Data Output generates information based on the spacecraft's trajectory, opportunity search results or based on a created observation. The data can be viewed either in tabular format or as a graph. Finally, SOA is unique in that it is designed to be able to communicate with a variety of existing planning and sequencing tools. From the very beginning SOA was designed with the user in mind. Extensive surveys of the potential user community were conducted in order to develop the software requirements. Throughout the development period, close ties have been maintained with the science community to insure that the tool maintains its user focus. Although development is still in its early stages, SOA is already developing a user community on the Cassini project, which is depending on this tool for their science planning. There are other tools at JPL that do various pieces of what SOA can do; however, there is no other tool which combines all these functions and presents them to the user in such a convenient, cohesive, and easy to use fashion.

SOA science planning mission operations sequence s↗

Multi-Mission Suitability of the NASA Ames Modular Common Bus

The obvious advantages of small spacecraft - their lower cost structure and the rapid development schedule - have enabled a large number of missions in the past. However, most of these missions have been focused on Earth observation from low Earth orbits. In 2006, the Small Spacecraft Division at the NASA Ames Research Center began the development of the Modular Common Bus, a spacecraft capable of delivering scientifically and technically useful payloads to a variety of destinations within 0.1 AU around the Earth. The core technologies used in the Common Bus design are a composite structure with body-mounted solar cells, an integrated avionics unit, and a high performance bipropellant propulsion system. Due to its modular approach, the Common Bus can be adapted to fit specific mission needs while still using a standardized and qualified set of components. Additionally a number of low cost launch vehicles are supported, resulting in overall mission costs of around $150M including the launch vehicle but excluding the science payloads. This significant reduction in cost and the shorter development time would enable NASA to conduct more frequent exploration missions within its budget and timeframe constraints, compared to the status quo. In this paper the suitability of the Common Spacecraft Bus for four different exploration scenarios is analyzed. These scenarios include a lunar orbiter, a lunar lander, a mission to a Sun-Earth Libration Point, and a rendezvous mission to a Near Earth Object. For each scenario, a preliminary design reference mission is developed and key design parameters for the spacecraft are determined.

Tietz, Sascha↗