Search NASA⌕ Search

SEARCH · Search NASA

Results for “mission sequencing”

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 307 records · Page 17
All sourcesNASA NTRSDOE OSTI
NASA NTRS2000

Autonomy Architectures for a Constellation of Spacecraft

This paper describes three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals of command sequences for each spacecraft. A fleet of self-commanding spacecraft would autonomously coordinate itself to satisfy high level science and engineering goals in a changing partially-understood environment-making feasible the operation of tens of even a hundred spacecraft (such as for interferometer or magnetospheric constellation missions).

Barrett, Anthony↗
NASA NTRS2005

Preliminary Report on Mission Design and Operations for Critical Events

Mission-critical events are defined in the Jet Propulsion Laboratory s Flight Project Practices as those sequences of events which must succeed in order to attain mission goals. These are dependent on the particular operational concept and design reference mission, and are especially important when committing to irreversible events. Critical events include main engine cutoff (MECO) after launch; engine cutoff or parachute deployment on entry, descent, and landing (EDL); orbital insertion; separation of payload from vehicle or separation of booster segments; maintenance of pointing accuracy for power and communication; and deployment of solar arrays and communication antennas. The purpose of this paper is to report on the current practices in handling mission-critical events in design and operations at major NASA spaceflight centers. The scope of this report includes NASA Johnson Space Center (JSC), NASA Goddard Space Flight Center (GSFC), and NASA Jet Propulsion Laboratory (JPL), with staff at each center consulted on their current practices, processes, and procedures.

Hayden, Sandra C.↗
NASA NTRS1985

Voyager flight engineering - Preparing for Uranus

Two Voyager spacecraft are currently engaged in exploration of the outer solar system with Voyager 2 scheduled to conduct the first close-up investigation of the planet Uranus during the period November 4, 1985 through March 3, 1986. Flight engineering for the Voyager project has the objectives of delivering a functioning spacecraft containing observing sequences to the right places at the right times. Due to the changing environment as the mission has progressed outward from Jupiter to Saturn to Uranus (and on to Neptune), this engineering task has included the development of significant new capabilities. The paper utilizes the case-study method to examine some new spacecraft capabilities in three subsystems: data, attitude and articulation control, and power. The implementation of a new navigational data-type, delta DOR, is also reviewed. An overview is given of the Voyager sequencing process for the cruise and encounter phases with a case study focusing on late updating of part of the near encounter sequence. The prospective mission to Neptune is previewed.

Mclaughlin, W. I.↗
NASA NTRSDate not supplied

Genesis Solar Wind – Capture, Return, Curate and Analyze: Looking Backward and Creating a Timeline

Introduction: In 1997 NASA’S Discovery Program selected the Genesis mission proposal to return solar wind samples to Earth for laboratory analyses. Principal Investigator Donald S. Burnett and the science team defined the purity of collector materials and ability to analyze solar wind composition to the precision required for planetary science. As a small mission, focused on a well-defined science goal, yet needing careful attention to engineering details, the communication among scientists and engineers, nurtured by Don Burnett, was exceptional. Genesis Mission and Curation Legacy: Genesis, as the first U. S. spacecraft to return astromaterial samples since Apollo, not only integrated the mission planning and flight teams, but also the science and sample curation teams during the mission development period. Since Genesis is a sample return mission, the Science Team was essential in certifying the collectors (sample containers for solar atoms). From inception, Genesis established mission funding for returned sample curation. JSC was lead in contamination control during mission preparation, including establishment of an ISO 4 cleanroom facility and use of ultrapure water (UPW) for cleaning flight hardware (and, as it turned out, for cleaning collectors after the mishap). Reliable, fast communication among scientists, engineers and curators at the hands-on level established deep respect among team members and efficient decision-making. JSC’s 50-years of astromaterial sample curation provided experienced sample processors onsite during recovery in Utah (a deep bench for emergency response). Post-recovery curation included iterative collaboration with science sample users to clean or verify cleanliness of samples. The science legacy from Genesis is addressed by Burnett and Jurewicz, this volume. In The Beginning: After Apollo sample return, Burnett and Marcia Neugebauer at JPL began discussing a solar wind sample return, with Neugebauer arguing that separate collection of solar wind regimes was essential science. By 1992 a solar wind sample return mission was presented at a workshop, and by 1994 a mission was proposed named Suess-Urey. The mission was re-proposed under a new name GENESIS and selected in 1997. Susan Niebur captured the Genesis mission history and stories, from high level management documents and from many interviews with participants [2]. Her account lets readers glimpse personality of participants in quotations from interviews. Need and Scope for Detailed Technical Timeline: A timeline constructed from lower level task documents has been initiated to document the resources and skills actually used, as well as task sequence or concurrency. Timelines for high level mission events are captured in two documents [1] [2] and for detailed re-entry events in [3]. A detailed technical timeline for Genesis mission and curation activities will provide data points for lower level tasks, such as ISO 4 curation facility construction time, preparation for nominal sample field recovery, mishap recovery, and UPW expansion. Changes in technology context 1990-2024: Semiconductor technologies were easily accessible in the U.S.A. (1990-1999), and the Genesis team used those resources for cleanroom design and UPW system expansion. Image documentation was changing from film to digital during cleanroom construction and payload cleaning (1997-2001). Engineering design was done using computer aided design proprietary software, making more difficult the archiving of payload configuration and materials. Email of documents, tracked delivery service and virtual meeting capability greatly improved communication efficiency. Information sources – Pre-launch mission preparation: Examples of mission science, engineering and contamination control are collector purity testing, payload design/fabrication and ISO 4 cleanroom construction. Information on timing of these activities comes from facility readiness reviews, management reviews, shipping documents, procurement documents, test reports, travel documents, laboratory logs, Quality Assurance documents, dates on images, participant notebooks and emails. Information sources – Sample return re-entry and field recovery activities: Information comes from event timelines produced by Mid-Air Recovery team, Lockheed team lead notes and from chase video, JPL Quality Assurance. Information also comes from images and logbooks from UTTR cleanroom operations and from curatorial documents. Information sources – Resulting science and sample cleaning processes: Agendas from the annual gatherings of the science team initially trace testing for collector purity/cleanliness, and after sample recovery, include collector cleaning and cleanliness assessment. Post-recovery documents include curatorial orders and procedures, sample allocation documents and LPSC abstracts. Timeline Objectives: A simple spreadsheet timeline with headers DATE, EVENT, PEOPLE, COMMENT, INFORMATION SOURCE has been initiated and currently has over 90 entries. While this is not definitive historical research, it is a quick look at the evolution of Genesis curation with pointers to documents or people with information. Engineers for future missions may find useful points of comparison for development of facilities. References:[1] Genesis Mission Reference Document, (2011) JPL D-62382.[2] Niebur S. M., edited by Brown D. W. (2023) NASA’s Discovery Program: The First 20 Years of Competitive Planetary Exploration, NASA-SP-2023-4238.[3] Genesis Mishap Investigation Board Report, Vol. 1 (July 2005).

solar wind↗
NASA NTRS1994

(abstract) Science-Project Interaction in the Low-Cost Mission

Large, complex, and highly optimized missions have performed most of the preliminary reconnaisance of the solar system. As a result we have now mapped significant fractions of its total surface (or surface-equivalent) area. Now, however, scientific exploration of the solar system is undergoing a major change in scale, and existing missions find it necessary to limit costs while fulfilling existing goals. In the future, NASA's Discovery program will continue the reconnaisance, exploration, and diagnostic phases of planetary research using lower cost missions, which will include lower cost mission operations systems (MOS). Historically, one of the more expensive functions of MOS has been its interaction with the science community. Traditional MOS elements that this interaction have embraced include mission planning, science (and engineering) event conflict resolution, sequence optimization and integration, data production (e.g., assembly, enhancement, quality assurance, documentation, archive), and other science support services. In the past, the payoff from these efforts has been that use of mission resources has been highly optimized, constraining resources have been generally completely consumed, and data products have been accurate and well documented. But because these functions are expensive we are now challenged to reduce their cost while preserving the benefits. In this paper, we will consider ways of revising the traditional MOS approach that might save project resources while retaining a high degree of service to the Projects' customers. Pre-launch, science interaction can be made simplier by limiting numbers of instruments and by providing greater redundancy in mission plans. Post launch, possibilities include prioritizing data collection into a few categories, easing requirements on real-time of quick-look data delivery, and closer integration of scientists into the mission operation.

mission operation science community interaction co↗
NASA NTRS2004

Using RSVP for analyzing state and previous activities for the Mars Exploration Rovers

Current developments in immersive environments for mission planning include several tools which make up a system for performing and rehearsing missions. This system, known as the Rover Sequencing and Visualization Program (RSVP), includes tools for planning long range sorties for highly autonomous rovers, tools for planning operations with robotic arms, and advanced tools for visualizing telemetry from remote spacecraft and landers. One of the keys to successful planning of rover activities is knowing what the rover has accomplished to date and understanding the current rover state. RSVP builds on the lessons learned and the heritage of the Mars Pathfinder mission This paper will discuss the tools and methodologies present in the RSVP suite for examining rover state, reviewing previous activities, visually comparing telemetered results to rehearsed results, and reviewing science and engineering imagery. In addition we will present how this tool suite was used on the Mars Exploration Rovers (MER) project to explore the surface of Mars.

Mars Exploration Rover (MER)↗
NASA NTRS2017

Pressure-Fed LOX/LCH4 Reaction Control System for Spacecraft: Transient Modeling and Thermal Vacuum Hotfire Test Results

An integrated cryogenic liquid oxygen, liquid methane (LOX/LCH4) reaction control system (RCS) was tested at NASA Glenn Research Center's Plum Brook Station in the Spacecraft Propulsion Research Facility (B-2) under vacuum and thermal vacuum conditions. The RCS is a subsystem of the Integrated Cryogenic Propulsion Test Article (ICPTA), a pressure-fed LOX/LCH4 propulsion system composed of a single 2,800 lbf main engine, two 28 lbf RCS engines, and two 7 lbf RCS engines. Propellants are stored in four 48 inch diameter 5083 aluminum tanks that feed both the main engine and RCS engines in parallel. Helium stored cryogenically in a composite overwrapped pressure vessel (COPV) flows through a heat exchanger on the main engine before being used to pressurize the propellant tanks to a design operating pressure of 325 psi. The ICPTA is capable of simultaneous main engine and RCS operation. The RCS engines utilize a coil-on-plug (COP) ignition system designed for operation in a vacuum environment, eliminating corona discharge issues associated with a high voltage lead. There are two RCS pods on the ICPTA, with two engines on each pod. One of these two engines is a heritage flight engine from Project Morpheus. Its sea level nozzle was removed and replaced by an 85:1 nozzle machined using Inconel 718, resulting in a maximum thrust of 28 lbf under altitude conditions. The other engine is a scaled down version of the 28 lbf engine, designed to match the core and overall mixture ratios as well as other injector characteristics. This engine can produce a maximum thrust of 7 lbf with an 85:1 nozzle that was additively manufactured using Inconel 718. Both engines are film-cooled and capable of limited duration gas-gas and gas-liquid operation, as well as steady-state liquid-liquid operation. Each pod contains one of each version, such that two engines of the same thrust level can be fired as a couple on opposite pods. The RCS feed system is composed of symmetrical 3/8 inch lines that tap off of the main propellant manifold to send LOX and LCH4 outboard to the RCS pods. A Thermodynamic Vent System (TVS) is used to condition propellants at each pod by venting through an orifice and then routing the cold expansion products back through tubing that is welded along a large portion of the main RCS feed lines. Prior to final installation on the ICPTA, the RCS engines were tested in a small vacuum chamber at the Johnson Space Center (JSC) Energy Systems Test Area (ESTA) to verify functionality of the new COP ignition system and check out operation of the vacuum nozzles. After engine-level testing, the RCS engines were installed on the vehicle and a series of integrated hot-fire tests were performed at JSC consisting of various pulsing and steady-state firings as well as integrated main engine/RCS operation. The ICPTA was then integrated into the Plum Brook B-2 facility for vacuum and thermal/vacuum testing. Testing in the B-2 facility was composed of multiple thermal and pressure environments. The first set of tests were performed under ambient temperature and altitude pressure conditions. These tests consisted of a range of minimum impulse bit (MIB) pulsing sequences with low duty cycle, analogous to a coast phase in which the RCS is primarily used for station keeping. The primary goal of this sequence is to understand how propellant conditions were effected without an active TVS. In this scenario, consistent gas-gas operation is desirable since it results in a smaller MIB and more efficient propellant consumption. Multiple skin thermocouples are mounted on the feedlines, in addition to a submerged thermocouple on each commodity, in order to gather thermal data on the system. Higher duty cycle pulsing tests were then performed, analogous to an ascent or landing mission phase. The primary goal of this sequence was to examine how well the engines self-conditioned without active TVS when starting from a quiescent state. The TVS was then activated during some tests to demonstrate the capability to quickly condition the engines for higher pulsing demand scenarios. A thermocouple at the TVS outlet allows for the calculation of energy absorbed by the vented propellant. Lastly, tests with longer pulses and multiple engines firing either in sequence or simultaneously were run in order to gather transient system response data on waterhammer. Six total high-speed pressure transducers are installed on the RCS system, one sensor at the end of each propellant manifold line on the pods, and one at the tap-off location for each commodity. This will allow for the accurate characterization of waterhammer in the system under various propellant conditions and firing sequences. Other instrumentation for this test series includes nozzle throat thermocouples, chamber pressure measurement, heat soakback measurement, and tank wall plume impingement temperature measurement. The next set of tests were performed to demonstrate simultaneous main engine and RCS operation. Data from this test will be used to examine if there is any change to nominal operation of the RCS as a result of feed system interaction or other phenomenon. Some of these tests began under high vacuum conditions (target ambient pressure less than 1x10(exp -3) torr) and others began at altitude conditions. The last set of tests were performed with the B-2 cold wall active. Under these tests, many of the same low duty cycle MIB tests were repeated in order to characterize how propellant conditions changed with the lower heat leak. In this scenario the RCS manifold experiences much less heat leak, resulting in a change to how well the engines self-condition. As a result, an increase in maximum waterhammer pressures and a change in natural frequency of the system was expected due to higher density propellants. The lower heat leak should also result in a change to the MIB pulse profile, and data will be examined to understand how MIB repeatability is affected in the different operating environments. Parallel to the test efforts, a set of transient model development efforts were made to predict RCS performance. The primary effort was aimed at producing a SINDA/FLUINT model to predict propellant conditioning up to the engine inlet as a function of different environmental and operating parameters, with the goal of predicting chamber pressure, TVS performance, and propellant consumption over time. Preliminary results for this effort will be presented in comparison with test data. Additional modeling efforts were made using SINDA/FLUINT to predict waterhammer in the system since the software is capable of handling multiphase transient fluid dynamics. These results will be compared with the high-speed pressure transducer test data for validation purposes.

Atwell, Matthew J.↗
NASA NTRS2005

Designing and Implementing a Distributed System Architecture for the Mars Rover Mission Planning Software (Maestro)

Distributed systems allow scientists from around the world to plan missions concurrently, while being updated on the revisions of their colleagues in real time. However, permitting multiple clients to simultaneously modify a single data repository can quickly lead to data corruption or inconsistent states between users. Since our message broker, the Java Message Service, does not ensure that messages will be received in the order they were published, we must implement our own numbering scheme to guarantee that changes to mission plans are performed in the correct sequence. Furthermore, distributed architectures must ensure that as new users connect to the system, they synchronize with the database without missing any messages or falling into an inconsistent state. Robust systems must also guarantee that all clients will remain synchronized with the database even in the case of multiple client failure, which can occur at any time due to lost network connections or a user's own system instability. The final design for the distributed system behind the Mars rover mission planning software fulfills all of these requirements and upon completion will be deployed to MER at the end of 2005 as well as Phoenix (2007) and MSL (2009).

Goldgof, Gregory M.↗
NASA NTRS2006

Cassini-Huygens Engineering Operations at Saturn

On 30th June 2004 the Cassini spacecraft fired its main engine to maneuver into orbit around Saturn. This paper describes the engineering operations that have contributed to the unprecedented scientific success of the Cassini and Huygens missions, and how engineering operations are planned and implemented in concert with the required sequence of science observations.

Huygens↗
NASA NTRS2022

Feedback-Directed Random Sequence Generation for Verifying Spacecraft Flight Rule Violations

The Psyche: Journey to a Metal World mission will be launched in 2022 to study the largest metal asteroid in the main asteroid belt, (16) Psyche. The spacecraft will perform a Mars Flyby in 2023 and enter (16) Psyche’s orbit in 2026. Throughout the mission, safely operating the spacecraft will require abiding by a set of flight rules that can be defined at any point in the mission lifecycle. These flight rules ensure that the spacecraft is operating within allowed regimes and a discrete event simulation tool, SEQGEN, will be used to model all command sequences prior to uplink. One of SEQGEN’s responsibilities is to determine if a command sequence violates any flight rules. For each flight rule, the necessary logic to determine if a violation has occurred is implemented in the SEQGEN adaptation, which is maintained by the mission. This adaptation must be tested thoroughly to ensure that the flight rule logic was interpreted and implemented correctly. This work describes a tool, RandSEQ, that autogenerates a suite of flight rule violating test sequences for each flight rule implemented in SEQGEN, and can be used by any mission using SEQGEN. The Psyche SEQGEN adaptation is still being developed, but so far, RandSEQ has been used to generate 532 test cases, that can be reviewed by various stakeholders, for 40 flight rules. The ability to autogenerate these test cases has significantly reduced the amount of time required to implement and test each flight rule.

Su, Laura↗
NASA NTRS1972

Manned space flight nuclear system safety. Volume 3: Reactor system preliminary nuclear safety analysis. Part 2A: Accident model document, appendix

The detailed abort sequence trees for the reference zirconium hydride (ZrH) reactor power module that have been generated for each phase of the reference Space Base program mission are presented. The trees are graphical representations of causal sequences. Each tree begins with the phase identification and the dichotomy between success and failure. The success branch shows the mission phase objective as being achieved. The failure branch is subdivided, as conditions require, into various primary initiating abort conditions.

Source record↗
NASA NTRS2010

Reactive Sequencing for Autonomous Navigation Evolving from Phoenix Entry, Descent, and Landing

Virtual Machine Language (VML) is an award-winning advanced procedural sequencing language in use on NASA deep-space missions since 1997, and was used for the successful entry, descent, and landing (EDL) of the Phoenix spacecraft onto the surface of Mars. Phoenix EDL utilized a state-oriented operations architecture which executed within the constraints of the existing VML 2.0 flight capability, compatible with the linear "land or die" nature of the mission. The intricacies of Phoenix EDL included the planned discarding of portions of the vehicle, the complex communications management for relay through on-orbit assets, the presence of temporally indeterminate physical events, and the need to rapidly catch up four days of sequencing should a reboot of the spacecraft flight computer occur shortly before atmospheric entry. These formidable operational challenges led to new techniques for packaging and coordinating reusable sequences called blocks using one-way synchronization via VML sequencing global variable events. The coordinated blocks acted as an ensemble to land the spacecraft, while individually managing various elements in as simple a fashion as possible. This paper outlines prototype VML 2.1 flight capabilities that have evolved from the one-way synchronization techniques in order to implement even more ambitious autonomous mission capabilities. Target missions for these new capabilities include autonomous touch-and-go sampling of cometary and asteroidal bodies, lunar landing of robotic missions, and ultimately landing of crewed lunar vehicles. Close proximity guidance, navigation, and control operations, on-orbit rendezvous, and descent and landing events featured in these missions require elaborate abort capability, manifesting highly non-linear scenarios that are so complex as to overtax traditional sequencing, or even the sort of one-way coordinated sequencing used during EDL. Foreseeing advanced command and control needs for small body and lunar landing guidance, navigation and control scenarios, work began three years ago on substantial upgrades to VML that are now being exercised in scenarios for lunar landing and comet/asteroid rendezvous. The advanced state-based approach includes coordinated state transition machines with distributed decision-making logic. These state machines are not merely sequences - they are reactive logic constructs capable of autonomous decision making within a well-defined domain. Combined with the JPL's AutoNav software used on Deep Space 1 and Deep Impact, the system allows spacecraft to autonomously navigate to an unmapped surface, soft-contact, and either land or ascend. The state machine architecture enabled by VML 2.1 has successfully performed sampling missions and lunar descent missions in a simulated environment, and is progressing toward flight capability. The authors are also investigating using the VML 2.1 flight director architecture to perform autonomous activities like rendezvous with a passive hypothetical Mars sample return capsule. The approach being pursued is similar to the touch-and-go sampling state machines, with the added complications associated with the search for, physical capture of, and securing of a separate spacecraft. Complications include optically finding and tracking the Orbiting Sample Capsule (OSC), keeping the OSC illuminated, making orbital adjustments, and physically capturing the OSC. Other applications could include autonomous science collection and fault compensation.

asteroid↗
NASA NTRS1993

The Mars mapper science and mission planning tool

The Mars Mapper Program (MOm) is an interactive tool for science and mission design developed for the Mars Observer Mission (MO). MOm is a function of the Planning and Sequencing Element of the MO Ground Data System. The primary users of MOm are members of the science and mission planning teams. Using MOm, the user can display digital maps of Mars in various projections and resolutions ranging from 1 to 256 pixels per degree squared. The user can overlay the maps with ground tracks of the MO spacecraft (S/C) and footprints and swaths of the various instruments on-board the S/C. Orbital and instrument geometric parameters can be computed on demand and displayed on the digital map or plotted in XY-plots. The parameter data can also be saved into files for other uses. MOm is divided into 3 major processes: Generator, Mapper, Plotter. The Generator Process is the main control which spawns all other processes. The processes communicate via sockets. At any one time, only 1 copy of MOm may operate on the system. However, up to 5 copies of each of the major processes may be invoked from the Generator. MOm is developed on the Sun SPARCStation 2GX with menu driven graphical user interface (GUI). The map window and its overlays are mouse-sensitized to permit on-demand calculations of various parameters along an orbit. The program is currently under testing and will be delivered to the MO Mission System Configuration Management for distribution to the MO community in 3/93.

Lo, Martin W.↗
NASA NTRS2002

MO and DA on the SWIE Instrument on the Wind Spacecraft

The construction of the Faraday Cup portion of the SWIE instrument on the Wind spacecraft, participation in Mission Operations, and Data Analysis (MO and DA) of observations of the solar wind has been supported by a sequence of grants. This 'final' Report represents work done on Mission Operations and Data Analysis for the Faraday Cup portion of the SWE. The work reported here was supported under NASA Grant NAG5-7359 (OSP 6701100) from June 1998 to October 2001. It should be noted that this work is continuing under NASA Grant NAG-10915, and therefore this report is 'final' only in the sense that the Grant has changed its number; a future report will cover the entire period of work. We have two types of obligations under these contracts: (1) To provide and assure the validity of "Key Parameters" which describe the basic properties of the solar wind on a daily basis. We have provided our 92 second observations daily via plots and parameters available from our Web site: http://web.mit.edu/space/www/wind/wind.html (2). To carry out scientific studies based on our observations. To document the extent of our research, we are including below a list of publications and presentations related to this project. The observations from Wind have made a major contribution to the study of the solar wind, and have every indication of continuing to do so.

Lazarus, Alan J.↗
NASA NTRS2012

VML 3.0 Reactive Sequencing Objects and Matrix Math Operations for Attitude Profiling

VML (Virtual Machine Language) has been used as the sequencing flight software on over a dozen JPL deep-space missions, most recently flying on GRAIL and JUNO. In conjunction with the NASA SBIR entitled "Reactive Rendezvous and Docking Sequencer", VML version 3.0 has been enhanced to include object-oriented element organization, built-in queuing operations, and sophisticated matrix / vector operations. These improvements allow VML scripts to easily perform much of the work that formerly would have required a great deal of expensive flight software development to realize. Autonomous turning and tracking makes considerable use of new VML features. Profiles generated by flight software are managed using object-oriented VML data constructs executed in discrete time by the VML flight software. VML vector and matrix operations provide the ability to calculate and supply quaternions to the attitude controller flight software which produces torque requests. Using VML-based attitude planning components eliminates flight software development effort, and reduces corresponding costs. In addition, the direct management of the quaternions allows turning and tracking to be tied in with sophisticated high-level VML state machines. These state machines provide autonomous management of spacecraft operations during critical tasks like a hypothetic Mars sample return rendezvous and docking. State machines created for autonomous science observations can also use this sort of attitude planning system, allowing heightened autonomy levels to reduce operations costs. VML state machines cannot be considered merely sequences - they are reactive logic constructs capable of autonomous decision making within a well-defined domain. The state machine approach enabled by VML 3.0 is progressing toward flight capability with a wide array of applicable mission activities.

VML (Virtual Machine Language)↗
NASA NTRS2010

Cassini's Solstice Mission

With the recent approval of NASA's flagship Cassini mission for seven more years of continued operations, dozens more Titan, Enceladus and other icy moon flybys await, as well as many occultations and multiple close passages to Saturn. Seasonal change is the principal scientific theme as Cassini extends its survey of the target-rich system over one full half-season, from just after northern winter solstice at arrival back in 2004, to northern summer solstice at the end of mission in 2017. The new seven-year mission extension requires careful propellant management as well as streamlined operations strategies with smaller spacecraft, sequencing and science teams. Cassini's never-before-envisioned end of mission scenario also includes nearly two dozen high-inclination orbits which pass between the rings and the planet allowing thrilling and unique science opportunities before entry into Saturn's atmosphere.

Seal, David↗
NASA NTRS2021

Sailing Towards an Expressive Scheduling Language for Europa Clipper

The mission planners for NASA's Europa Clipper deep-space mission use automated scheduling software to generate activity plans and command sequences for multiple instruments and subsystems before sending the sequences for execution on board. Both science and engineering planners must translate their intents into expressions of mission constraints, goals, and preferences that the scheduling engine understands. This paper describes the ongoing development of a dedicated domain-specific java-embedded language that can efficiently and accurately capture such concerns for the Europa Clipper mission, along with a user-interface companion for the language.

Schaffer, Steve↗
NASA NTRS1992

An advanced environment for spacecraft engineering subsystem mission operations

The Engineering Analysis Subsystem Environment (EASE) is under development at the JPL with a view to prospective small and large space missions. EASE is a modular multimission/multisystem architecture for spacecraft analysis that encompases monitoring and sequence support; its collection of software analysis modules is specific to a given mission, thereby easily accommodating mission scale. An EASE subsystem analysis module can be developed in modular program sets or packages, and a level of automation can then be introduced within such sets to achieve intramodule automation.

Bahrami, K. A.↗