Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Multi-Mission Operations”

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS1991

Flight systems to facilitate deployment and on-orbit operations of the upper atmosphere research satellite

UARS flight systems are designed to ensure mission success during the NSTS Orbiter deployment of the UARS Observatory. The Orbiter and its crew capabilities allow the UARS project to take advantage of the on-orbit human presence. These capabilities include human intervention and correction of spacecraft anomalies. The UARS Observatory is based on the Multi-Mission Modular Spacecraft to allow for flexible monitoring and commanding of the observatory. The observatory's Solar Array and High Gain Antenna systems are designed to allow for manual release and/or deployment. The UARS Airborne Support Equipment are designed to support the observatory as an electrical and communication interface to the Orbiter; and as work platform to support Extra-Vehicular Activity (EVA). Tools and EVA equipment were designed and developed to assist the crewmember perform the required contingency tasks.

Griffin, Thomas J.↗
NASA NTRS1993

The GPS Topex/Poseidon precise orbit determination experiment - Implications for design of GPS global networks

Topex/Poseidon, a cooperative satellite mission between United States and France, aims to determine global ocean circulation patterns and to study their influence on world climate through precise measurements of sea surface height above the geoid with an on-board altimeter. To achieve the mission science aims, a goal of 13-cm orbit altitude accuracy was set. Topex/Poseidon includes a Global Positioning System (GPS) precise orbit determination (POD) system that has now demonstrated altitude accuracy better than 5 cm. The GPS POD system includes an on-board GPS receiver and a 6-station GPS global tracking network. This paper reviews early GPS results and discusses multi-mission capabilities available from a future enhanced global GPS network, which would provide ground-based geodetic and atmospheric calibrations needed for NASA deep space missions while also supplying tracking data for future low Earth orbiters. Benefits of the enhanced global GPS network include lower operations costs for deep space tracking and many scientific and societal benefits from the low Earth orbiter missions, including improved understanding of ocean circulation, ocean-weather interactions, the El Nino effect, the Earth thermal balance, and weather forecasting.

Lindqwister, Ulf J.↗
NASA NTRS1996

Re-Engineering JPL's Mission Planning Ground System Architecture for Cost Efficient Operations in the 21st Century

Work carried out to re-engineer the mission analysis segment of JPL's mission planning ground system architecture is reported on. The aim is to transform the existing software tools, originally developed for specific missions on different support environments, into an integrated, general purpose, multi-mission tool set. The issues considered are: the development of a partnership between software developers and users; the definition of key mission analysis functions; the development of a consensus based architecture; the move towards evolutionary change instead of revolutionary replacement; software reusability, and the minimization of future maintenance costs. The current status and aims of new developments are discussed and specific examples of cost savings and improved productivity are presented.

Fordyce, Jess↗
NASA NTRS1998

Overview of Future NASA Tether Applications

The groundwork has been laid for tether applications in space. NASA has developed tether technology for space applications since the 1960's. Important recent milestones include retrieval of a tether in space (TSS-1, 1992), successful deployment of a 20-km-long tether in space (SEDS-1, 1993), and operation of an electrodynamic tether with tether current driven in both directions-power and thrust modes (PMG, 1993). Various types of tethers and systems can be used for space transportation. Short electrodynamic tethers can use solar power to 'push' against a planetary magnetic field to achieve propulsion without the expenditure of propellant. The planned Propulsive Small Expendable Deployer System (ProSEDS) experiment will demonstrate electrodynamic tether thrust during its flight in early 2000. Utilizing completely different physical principles, long non-conducting tethers can exchange momentum between two masses in orbit to place one body into a higher orbit or a transfer orbit for lunar and planetary missions. Recently completed system studies of this concept indicate that it would be a relatively low-cost in-space asset with long-term multi-mission capability. Tethers can also be used to support space science by providing a mechanism for precision formation flying and for reaching regions of the upper atmosphere that were previously inaccessible.

Johnson, Les↗
NASA NTRS1966

A Modular Nuclear Vehicle System with Multi-Mission Capability for Mars Stopover Missions

In depth studies conducted over the past two years have established a modular nuclear stage concept which offers multi-mission capability with a maximum of hardware commonality, i.e., a concept which minimizes total hardware development effort and investment in facilities while providing a logical development evolution from ground test systems to flight test and from initial to more ambitious space applications. Recent results oriented toward the definition and application of such a vehicle concept for the manned Mars landing mission are presented. The basic modular concept employing NERVA nuclear rocket engines is reviewed and the mission peculiar factors affecting the module sizes and number of modules required are discussed. Specific results presented are restricted primarily to the 1982 Mars landing mission via the opposition class mission mode since this is the earliest anticipated date for such a mission. The realistic effects of orbital launch windows are considered and brief discussions of orbital assembly and packaging options with a modular approach are given. Typical ground launch and orbital assembly operations are defined assuming an uprated Saturn V class launch vehicle and the connecting mode of orbital assembly, in which all modules are orbited fully loaded with propellant. The effect of a significant increase in nuclear engine specific impulse is discussed.

Harris, Ronald J.↗
NASA NTRS2000

EOSDIS: Archive and Distribution Systems in the Year 2000

Earth Science Enterprise (ESE) is a long-term NASA research mission to study the processes leading to global climate change. The Earth Observing System (EOS) is a NASA campaign of satellite observatories that are a major component of ESE. The EOS Data and Information System (EOSDIS) is another component of ESE that will provide the Earth science community with easy, affordable, and reliable access to Earth science data. EOSDIS is a distributed system, with major facilities at seven Distributed Active Archive Centers (DAACs) located throughout the United States. The EOSDIS software architecture is being designed to receive, process, and archive several terabytes of science data on a daily basis. Thousands of science users and perhaps several hundred thousands of non-science users are expected to access the system. The first major set of data to be archived in the EOSDIS is from Landsat-7. Another EOS satellite, Terra, was launched on December 18, 1999. With the Terra launch, the EOSDIS will be required to support approximately one terabyte of data into and out of the archives per day. Since EOS is a multi-mission program, including the launch of more satellites and many other missions, the role of the archive systems becomes larger and more critical. In 1995, at the fourth convening of NASA Mass Storage Systems and Technologies Conference, the development plans for the EOSDIS information system and archive were described. Five years later, many changes have occurred in the effort to field an operational system. It is interesting to reflect on some of the changes driving the archive technology and system development for EOSDIS. This paper principally describes the Data Server subsystem including how the other subsystems access the archive, the nature of the data repository, and the mass-storage I/O management. The paper reviews the system architecture (both hardware and software) of the basic components of the archive. It discusses the operations concept, code development, and testing phase of the system. Finally, it describes the future plans for the archive.

Behnke, Jeanne↗
NASA NTRS2005

MSAP Hardware Verification: Testing Multi-Mission System Architecture Platform Hardware Using Simulation and Bench Test Equipment

The Multi-Mission System Architecture Platform (MSAP) project aims to develop a system of hardware and software that will provide the core functionality necessary in many JPL missions and can be tailored to accommodate mission-specific requirements. The MSAP flight hardware is being developed in the Verilog hardware description language, allowing developers to simulate their design before releasing it to a field programmable gate array (FPGA). FPGAs can be updated in a matter of minutes, drastically reducing the time and expense required to produce traditional application-specific integrated circuits. Bench test equipment connected to the FPGAs can then probe and run Tcl scripts on the hardware. The Verilog and Tcl code can be reused or modified with each design. These steps are effective in confirming that the design operates according specifications.

Crossin, Kent R.↗
NASA NTRS2003

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↗
NASA NTRS2003

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 ↗
NASA NTRS2002

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↗
NASA NTRS2006

Lessons Learned from Daily Uplink Operations during the Deep Impact Mission

The daily preparation of uplink products (commands and files) for Deep Impact was as problematic as the final encounter images were spectacular. The operations team was faced with many challenges during the six-month mission to comet Tempel One of the biggest difficulties was that the Deep Impact Flyby and Impactor vehicles necessitated a high volume of uplink products while also utilizing a new uplink file transfer capability. The Jet Propulsion Laboratory (JPL) Multi-Mission Ground Systems and Services (MGSS) Mission Planning and Sequence Team (MPST) had the responsibility of preparing the uplink products for use on the two spacecraft. These responsibilities included processing nearly 15,000 flight products, modeling the states of the spacecraft during all activities for subsystem review, and ensuring that the proper commands and files were uplinked to the spacecraft. To guarantee this transpired and the health and safety of the two spacecraft were not jeopardized several new ground scripts and procedures were developed while the Deep Impact Flyby and Impactor spacecraft were en route to their encounter with Tempel-1. These scripts underwent several adaptations throughout the entire mission up until three days before the separation of the Flyby and Impactor vehicles. The problems presented by Deep Impact's daily operations and the development of scripts and procedures to ease those challenges resulted in several valuable lessons learned. These lessons are now being integrated into the design of current and future MGSS missions at JPL.

uplink↗
NASA NTRS2010

Energy Management of the Multi-Mission Space Exploration Vehicle Using a Goal-Oriented Control System

Safe human exploration in space missions requires careful management of limited resources such as breathable air and stored electrical energy. Daily activities for astronauts must be carefully planned with respect to such resources, and usage must be monitored as activities proceed to ensure that they can be completed while maintaining safe resource margins. Such planning and monitoring can be complex because they depend on models of resource usage, the activities being planned, and uncertainties. This paper describes a system - and the technology behind it - for energy management of the NASA-Johnson Space Center's Multi-Mission Space Exploration Vehicles (SEV), that provides, in an onboard advisory mode, situational awareness to astronauts and real-time guidance to mission operators. This new capability was evaluated during this year's Desert RATS (Research and Technology Studies) planetary exploration analog test in Arizona. This software aided ground operators and crew members in modifying the day s activities based on the real-time execution of the plan and on energy data received from the rovers.

Braman, Julia M. B.↗
NASA NTRS2010

Planetary Image Geometry Library

The Planetary Image Geometry (PIG) library is a multi-mission library used for projecting images (EDRs, or Experiment Data Records) and managing their geometry for in-situ missions. A collection of models describes cameras and their articulation, allowing application programs such as mosaickers, terrain generators, and pointing correction tools to be written in a multi-mission manner, without any knowledge of parameters specific to the supported missions. Camera model objects allow transformation of image coordinates to and from view vectors in XYZ space. Pointing models, specific to each mission, describe how to orient the camera models based on telemetry or other information. Surface models describe the surface in general terms. Coordinate system objects manage the various coordinate systems involved in most missions. File objects manage access to metadata (labels, including telemetry information) in the input EDRs and RDRs (Reduced Data Records). Label models manage metadata information in output files. Site objects keep track of different locations where the spacecraft might be at a given time. Radiometry models allow correction of radiometry for an image. Mission objects contain basic mission parameters. Pointing adjustment ("nav") files allow pointing to be corrected. The object-oriented structure (C++) makes it easy to subclass just the pieces of the library that are truly mission-specific. Typically, this involves just the pointing model and coordinate systems, and parts of the file model. Once the library was developed (initially for Mars Polar Lander, MPL), adding new missions ranged from two days to a few months, resulting in significant cost savings as compared to rewriting all the application programs for each mission. Currently supported missions include Mars Pathfinder (MPF), MPL, Mars Exploration Rover (MER), Phoenix, and Mars Science Lab (MSL). Applications based on this library create the majority of operational image RDRs for those missions. A Java wrapper around the library allows parts of it to be used from Java code (via a native JNI interface). Future conversions of all or part of the library to Java are contemplated.

Deen, Robert C.↗
NASA NTRS2009

Using XML Configuration-Driven Development to Create a Customizable Ground Data System

The Mission data Processing and Control Subsystem (MPCS) is being developed as a multi-mission Ground Data System with the Mars Science Laboratory (MSL) as the first fully supported mission. MPCS is a fully featured, Java-based Ground Data System (GDS) for telecommand and telemetry processing based on Configuration-Driven Development (CDD). The eXtensible Markup Language (XML) is the ideal language for CDD because it is easily readable and editable by all levels of users and is also backed by a World Wide Web Consortium (W3C) standard and numerous powerful processing tools that make it uniquely flexible. The CDD approach adopted by MPCS minimizes changes to compiled code by using XML to create a series of configuration files that provide both coarse and fine grained control over all aspects of GDS operation.

Nash, Brent↗