Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “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 847 records · Page 47

Software-Only Key Management and Cryptography (KMC) for Spacecraft Command Encryption

The Jet Propulsion Laboratory (JPL) Advanced Multi-Mission Operations System (AMMOS) in partnership with NASA’s Katherine Johnson Independent Verification and Validation (NASA IV&V) Jon McBride Software Testing and Research (JSTAR) laboratory have jointly developed a command encryption capability that provides a software-only encryption solution utilizing the CCSDS Space Data Link Security Protocol. This solution, named Key Management and Cryptography (KMC), incorporates JPL’s encryption service with the JSTAR open-source CryptoLib library, providing a solution for spacecraft command encryption, which is required per NASA standard NASA-STD-1006-A. This paper will focus on its design, usage, and operation for two SmallSat missions, along with its future expanded functionality of end-to-end spacecraft encryption.

command encryption↗

Adding "Missed" Science to Cassini's Ops Plan

The phenomenal success of the Cassini Mission at Saturn is largely due to flagship instruments, in a target rich environment, for a long period of time, executing almost error free complex mission operations. A smooth transition from cruise operations through the prime science mission and extended science (Equinox) mission culminating in the currently executing Solstice mission has folded in necessary procedural alterations due to improved understanding of the spacecraft, instruments, uplink and planning systems as well as additional science objectives. These have come with the maturation of the mission along with management of workforce reductions. One important set of operational changes has been initiated due to scientific findings highlighting "missed" science opportunities. This is the case for the Titan Meteorology Campaigns and Saturn Storm Watch Campaigns. These observations involve long term monitoring of the atmospheres of Titan and Saturn while the spacecraft and science teams are focused on other high priority targets of opportunity (like Enceladus). Our objective in this paper is to emphasize how a non-invasive strategy to get additional remarkable science was conceived and implemented in a mission with an already well defined operational plan. To illustrate this we will detail Titan Meteorology Campaign and Saturn Storm Watch Campaign integration and implementation strategies as well as the scientific goals and achievements of both.

Roy, Mou↗

Adding "Missed" Science to Cassini's Ops Plan

The phenomenal success of the Cassini Mission at Saturn is largely due to flagship instruments, in a target rich environment, for a long period of time, executing almost error free complex mission operations. A smooth transition from cruise operations through the prime science mission and extended science (Equinox) mission culminating in the currently executing Solstice mission has folded in necessary procedural alterations due to improved understanding of the spacecraft, instruments, uplink and planning systems as well as additional science objectives. These have come with the maturation of the mission along with management of workforce reductions. One important set of operational changes has been initiated due to scientific findings highlighting "missed" science opportunities. This is the case for the Titan Meteorology Campaigns and Saturn Storm Watch Campaigns. These observations involve long term monitoring of the atmospheres of Titan and Saturn while the spacecraft and science teams are focused on other high priority targets of opportunity (like Enceladus). Our objective in this paper is to emphasize how a non-invasive strategy to get additional remarkable science was conceived and implemented in a mission with an already well defined operational plan. To illustrate this we will detail Titan Meteorology Campaign and Saturn Storm Watch Campaign integration and implementation strategies as well as the scientific goals and achievements of both.

Roy, Mou↗

Automatic Command Sequence Generation

Automatic Sequence Generator (Autogen) Version 3.0 software automatically generates command sequences for the Mars Reconnaissance Orbiter (MRO) and several other JPL spacecraft operated by the multi-mission support team. Autogen uses standard JPL sequencing tools like APGEN, ASP, SEQGEN, and the DOM database to automate the generation of uplink command products, Spacecraft Command Message Format (SCMF) files, and the corresponding ground command products, DSN Keywords Files (DKF). Autogen supports all the major multi-mission mission phases including the cruise, aerobraking, mapping/science, and relay mission phases. Autogen is a Perl script, which functions within the mission operations UNIX environment. It consists of two parts: a set of model files and the autogen Perl script. Autogen encodes the behaviors of the system into a model and encodes algorithms for context sensitive customizations of the modeled behaviors. The model includes knowledge of different mission phases and how the resultant command products must differ for these phases. The executable software portion of Autogen, automates the setup and use of APGEN for constructing a spacecraft activity sequence file (SASF). The setup includes file retrieval through the DOM (Distributed Object Manager), an object database used to store project files. This step retrieves all the needed input files for generating the command products. Depending on the mission phase, Autogen also uses the ASP (Automated Sequence Processor) and SEQGEN to generate the command product sent to the spacecraft. Autogen also provides the means for customizing sequences through the use of configuration files. By automating the majority of the sequencing generation process, Autogen eliminates many sequence generation errors commonly introduced by manually constructing spacecraft command sequences. Through the layering of commands into the sequence by a series of scheduling algorithms, users are able to rapidly and reliably construct the desired uplink command products. With the aid of Autogen, sequences may be produced in a matter of hours instead of weeks, with a significant reduction in the number of people on the sequence team. As a result, the uplink product generation process is significantly streamlined and mission risk is significantly reduced. Autogen is used for operations of MRO, Mars Global Surveyor (MGS), Mars Exploration Rover (MER), Mars Odyssey, and will be used for operations of Phoenix. Autogen Version 3.0 is the operational version of Autogen including the MRO adaptation for the cruise mission phase, and was also used for development of the aerobraking and mapping mission phases for MRO.

Fisher, Forest↗

Automated Commanding of the SMAP Spacecraft Enables Efficient, Reliable, and Responsive Operations

The Soil Moisture Active Passive (SMAP) mission developed and deployed a system to autonomously handle most routine commanding of the observatory. This system of ground software is able to build commands, validate them, and radiate the commands to the spacecraft, all without human interaction. In the case of an off -nominal scenario, the system will abort gracefully and notify the mission operations team of the problem. The system was phased into operations during the first three months of the SMAP mission and handles over 90% of the weekly commanding of the vehicle. The gradual introduction of the automation in flight, along with an extensive test campaign, was instrumental in the success of the software. The automation has enabled substantial efficiencies in operations team staffing and has improved reliability by removing the potential for human error. The system also allows the SMAP project to be more responsive which has shown significant benefits in areas of data latency and science accuracy.

automation↗

Modular space station, phase B extension. Program operations plan

An organized approach is defined for establishing the most significant requirements pertaining to mission operations, information management, and computer program design and development for the modular space station program. The operations plan pertains to the space station and experiment module program elements and to the ground elements required for mission management and mission support operations.

Source record↗

The Cassini Spacecraft Design and Operations

Designed and funded in the pre-'better, faster, cheaper' era, Cassini was built to be the one mission to Saturn for many years to come. Its complement of twelve Orbiter science instruments and the Huygens Probe make Cassini one of the most complex missions ever flown. With a seven-year cruise and Saturn Orbit Insertion now over, Cassini is settling in to perform a very ambitious prime mission over the next four years. This paper provides an overview of the spacecraft design and the mission operations to date.

mission operations↗

STS flight operations - Concept versus reality

The NASA Lyndon B. Johnson Space Center Mission Operations Directorate (MOD) has the responsibility for planning, training, and implementing of flight operations in support of the National Space Transportation System (STS) Program. In this role, MOD has responsibility for the operational interface with customers and the translation of customer requirements into operating plans to satisfy their objectives. The basic objectives of flight operations are to maximize mission success, to minimize risks to the Orbiter and the crew, to decrease operating costs, and to achieve an effective balance in the application of all operational resources. In the National STS Program, to date, 20 missions have been flown and the process for planning, training, and flight operations has been thoroughly exercised. In this paper, MOD's performance is assessed, and those areas in which our initial operating concepts have been successful as well as those in which significant additional work is required are identified.

Kranz, E. F.↗

A Space Data System Standard for Telerobotic Operations

The Telerobotics Working Group of the Mission Operations and Information Management Services Area of the Consultative Committee for Space Data Systems is drafting a document that will help bound the scope of an eventual international standard for telerobotic operations services. This paper will present the work in progress and provide background for how the international community is beginning to define standards in telerobotic operations that will help ensure the success of complex missions to explore beyond Earth orbit.

Mittman, David S.↗

Spitzer Operations: Scheduling the Out Years

Spitzer Warm Mission operations have remained robust and exceptionally efficient since the cryogenic mission ended in mid-2009. The distance to the now exceeds 1 AU, making telecommunications increasingly difficult; however, analysis has shown that two-way communication could be maintained through at least 2017 with minimal loss in observing efficiency. The science program continues to emphasize the characterization of exoplanets, time domain studies, and deep surveys, all of which can impose interesting scheduling constraints. Recent changes have significantly improved on-board data compression, which both enables certain high volume observations and reduces Spitzer's demand for competitive Deep Space Network resources.

Spitzer↗

Beacon Spacecraft Operations: Lessons in Automation

A new approach to mission operations has been flight validated on NASA's Deep Space One (DS1) mission that launched in October 1998. The beacon monitor operations technology is aimed at decreasing the total volume of downlinked engineering telemetry by reducing the frequency of downlink and the volume of data received per pass.

spacecraft operations automation beacon↗

Ideas on the NASA Senior Review and Mission Extension Process

Extended mission budgets fund a significant part of our community, particularly young scientists who in a relatively short time are exposed to a broad range of experiences and opportunities available in space science and other STEM fields. In particular, mission-funded science offers a relatively stable funding stream that enables meaningful mentoring efforts and interactions, including apprenticeships ranging from project management, to mission operations, to data processing and analysis, to hardware and software development, to STEM-related education and outreach. It moreover provides professional contacts that fuel diversity in mission leadership and in the science and technical workforce at-large. Last but not least, it sustains the scientific productivity of NASA’s missions, which constitute major national investments meriting their full exploitation. Budgets cuts, however, are exercising pressure on the science and operations of the extended mission fleet despite being only a small portion of the overall Division budget. The history of Heliophysics has demonstrated that maintaining the operation of missions beyond their prime phase invariably leads to a much deeper knowledge of the original mission science goals, together with new applications often not foreseen during their original design. Their operation as part of the Heliophysics System Observatory (HSO)---a coordinated, 1eliophysics, multipoint observing system of the heliosphere, is a prime example. Some of the first activities undertaken by the Parker Solar Probe and Solar Orbiter missions required recreating the larger context of their new observations by using the diversity of HSO mission capabilities. The marginal cost of maintaining this valuable, working science resource, in the form of both continuing high quality data access and expertise, is small compared to the cost of the original missions or of new missions to achieve similar objectives, making the operation of extended missions, the best “science per dollar” investment in Heliophysics. We argue that reducing both extended mission operations and science budgets will have a ripple effect across the community, including reducing employment and training opportunities for young scientists, to lowering the quality/impact of the Heliophysics Systems Observatory. Instead, we suggest that the proposal process for mission extension should be re-examined. We offer several ideas for reducing costs of extended missions toward maintaining science output and streamlining the management process.

A. Vourlidas↗

Space transfer concepts and analysis for exploration missions. Implementation plan and element description document (draft final). Volume 6: Lunar systems

NASA's two Office of Space Flight (Code M) Space Transfer Vehicle (STV) contractors supported development of Space Exploration Initiative (SEI) lunar transportation concepts. This work treated lunar SEI missions as the far end of a more near-term STV program, most of whose missions were satellite delivery and servicing requirements derived from Civil Needs Data Base (CNDB) projections. Space Transfer Concepts and Analysis for Exploration Missions (STCAEM) began to address the complete design of a lunar transportation system. The following challenges were addressed: (1) the geometry of aerobraking; (2) accommodation of mixed payloads; (3) cryogenic propellant transfer in Low Lunar Orbit (LLO); (4) fully re-usable design; and (5) growth capability. The leveled requirements, derived requirements, and assumptions applied to the lunar transportation system design are discussed. The mission operations section includes data on mission analysis studies and performance parametrics as well as the operating modes and performance evaluations which include the STCAEM recommendations. Element descriptions for the lunar transportation family included are a listing of the lunar transfer vehicle/lunar excursion vehicle (LTV/LEV) components; trade studies and mass analyses of the transfer and excursion modules; advanced crew recovery vehicle (ACRV) (modified crew recovery vehicle (MCRV)) modifications required to fulfill lunar operations; the aerobrake shape and L/D to be used; and some costing methods and results. Commonality and evolution issues are also discussed.

Source record↗

Large Unmanned Aircraft System Operations in the National Airspace System - the NASA 2007 Western States Fire Missions

The National Aeronautics and Space Administration (NASA) Dryden Flight Research Center (DFRC) Ikhana (ee-kah-nah) project executed the 2007 Western States Fire Missions over several of the western United States using an MQ-9 unmanned aircraft system (UAS) in partnership with the NASA Ames Research Center, the United States Forest Service, and the National Interagency Fire Center. The missions were intended to supply infrared imagery of wildfires to firefighters on the ground within 10 minutes of data acquisition. For each of the eight missions, the NASA DFRC notified the Federal Aviation Administration (FAA) of specific flight plans within three or fewer days of the flight. The FAA Certificate of Waiver or Authorization (commonly referred to as a COA ) process was used to obtain access to the United States National Airspace System. Significant time and resources were necessary to develop the COA application, perform mission planning, and define and approve emergency landing sites. Unique aspects of flying unmanned aircraft created challenges to mission operations. Close coordination with FAA headquarters and air traffic control resulted in safe and successful missions that assisted firefighters by providing near-real-time imagery of selected wildfires.

Buoni, Gregory P.↗

Agile: From Software to Mission Systems

To maximize efficiency and flexibility in Mission Operations System (MOS) design, we are evolving principles from agile and lean methods for software, to the complete mission system. This allows for reduced operational risk at reduced cost, and achieves a more effective design through early integration of operations into mission system engineering and flight system design. The core principles are assessment of capability through demonstration, risk reduction through targeted experiments, early test and deployment, and maturation of processes and tools through use.

Trimble, Jay↗

Mission Control Center operations for the Space Transportation System

Orbital flight tests of the Space Shuttle Program involved three types of activities, including classic flight testing of the vehicle hardware and software, operational procedures evaluation and development, and performance of payload mission operations. This combination of activities required a capability of the Mission Control Center (MCC) to provide thorough support to the Orbiter and its crew across a broad spectrum of activities. Attention is given to MCC organization, the general functions performed by the MCC teams, a flight support description, the motivation for a change in MCC operations, support elements, orbit phase functions, and dynamic flight phase functions. It is pointed out that the MCC facilities for the operational mode of support will not be fully implemented until 1984.

Frank, M. P.↗