Search NASA⌕ Search

SEARCH · Search NASA

Results for “sequencing mission operations system”

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 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
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 NTRS1994

Simplifying operations with an uplink/downlink integration toolkit

The Operations Engineering Lab (OEL) at JPL has developed a simple, generic toolkit to integrate the uplink/downlink processes, (often called closing the loop), in JPL's Multimission Ground Data System. This toolkit provides capabilities for integrating telemetry verification points with predicted spacecraft commands and ground events in the Mission Sequence Of Events (SOE) document. In the JPL ground data system, the uplink processing functions and the downlink processing functions are separate subsystems that are not well integrated because of the nature of planetary missions with large one-way light times for spacecraft-to-ground communication. Our new closed-loop monitoring tool allows an analyst or mission controller to view and save uplink commands and ground events with their corresponding downlinked telemetry values regardless of the delay in downlink telemetry and without requiring real-time intervention by the user. An SOE document is a time-ordered list of all the planned ground and spacecraft events, including all commands, sequence loads, ground events, significant mission activities, spacecraft status, and resource allocations. The SOE document is generated by expansion and integration of spacecraft sequence files, ground station allocations, navigation files, and other ground event files. This SOE generation process has been automated within the OEL and includes a graphical, object-oriented SOE editor and real-time viewing tool running under X/Motif. The SOE toolkit was used as the framework for the integrated implementation. The SOE is used by flight engineers to coordinate their operations tasks, serving as a predict data set in ground operations and mission control. The closed-loop SOE toolkit allows simple, automated integration of predicted uplink events with correlated telemetry points in a single SOE document for on-screen viewing and archiving. It automatically interfaces with existing real-time or non real-time sources of information, to display actual values from the telemetry data stream. This toolkit was designed to greatly simplify the user's ability to access and view telemetry data, and also provide a means to view this data in the context of the commands and ground events that are used to interpret it. A closed-loop system can prove especially useful in small missions with limited resources requiring automated monitoring tools. This paper will discuss the toolkit implementation, including design trade-offs and future plans for enhancing the automated capabilities.

Murphy, Susan C.↗
NASA NTRS2013

Advanced Strategic and Tactical Relay Request Management for the Mars Relay Operations Service

This software provides a new set of capabilities for the Mars Relay Operations Service (MaROS) in support of Strategic and Tactical relay, including a highly interactive relay request Web user interface, mission control over relay planning time periods, and mission management of allowed strategic vs. tactical request parameters. Together, these new capabilities expand the scope of the system to include all elements critical for Tactical relay operations. Planning of replay activities spans a time period that is split into two distinct phases. The first phase is called Strategic, which begins at the time that relay opportunities are identified, and concludes at the point that the orbiter generates the flight sequences for on board execution. Any relay request changes from this point on are called Tactical. Tactical requests, otherwise called Orbit - er Relay State Changes (ORSC), are highly restricted in terms of what types of changes can be made, and the types of parameters that can be changed may differ from one orbiter to the next. For example, one orbiter may be able to delay the start of a relay request, while another may not. The legacy approach to ORSC management involves exchanges of e-mail with "requests for change" and "acknowledgement of approval," with no other tracking of changes outside of e-mail folders. MaROS Phases 1 and 2 provided the infrastructure for strategic relay for all supported missions. This new version, 3.0, introduces several capabilities that fully expand the scope of the system to include tactical relay. One new feature allows orbiter users to manage and "lock" Planning Periods, which allows the orbiter team to formalize the changeover from Strategic to Tactical operations. Another major feature allows users to interactively submit tactical request changes via a Web user interface. A third new feature allows orbiter missions to specify allowed tactical updates, which are automatically incorporated into the tactical change process. This software update is significant in that it provides the only centralized service for tactical request management available for relay missions.

Allard, Daniel A.↗
NASA NTRS1990

The resupply interface mechanism RMS compatibility test

Spacecraft on-orbit servicing consists of exchanging components such as payloads, orbital replacement units (ORUs), and consumables. To accomplish the exchange of consumables, the receiving vehicle must mate to the supplier vehicle. Mating can be accomplished by a variety of docking procedures. However, these docking schemes are mission dependent and can vary from shuttle bay berthing to autonomous rendezvous and docking. Satisfying the many docking conditions will require use of an innovative docking device. The device must provide fluid, electrical, pneumatic and data transfer between vehicles. Also, the proper stiffness must be obtained and sustained between the vehicles. A device to accomplish this, the resupply interface mechanism (RIM), was developed. The RIM is a unique device because it grasps the mating vehicle, draws the two vehicles together, simultaneously mates all connectors, and rigidizes the mating devices. The NASA-Johnson Manipulator Development Facility was used to study how compatible the RIM is to on orbit docking and berthing. The facility contains a shuttle cargo bay mockup with a remote manipulator system (RMS). This RMS is used to prepare crew members for shuttle missions involving spacecraft berthing operations. The MDF proved to be an excellant system for testing the RIM/RMS compatibility. The elements examined during the RIM JSC test were: RIM gross and fine alignment; berthing method sequence; visual cuing aids; utility connections; and RIM overall performance. The results showed that the RIM is a good device for spacecraft berthing operations. Mating was accomplished during every test run and all test operators (crew members) felt that the RIM is an effective device. The purpose of the JSC RIM test and its results are discussed.

Jackson, Stewart W.↗
NASA NTRS1994

Joint operations planning for space surveillance missions on the MSX satellite

The Midcourse Space Experiment (MSX) satellite, sponsored by BMDO, is intended to gather broad-band phenomenology data on missiles, plumes, naturally occurring earthlimb backgrounds and deep space backgrounds. In addition the MSX will be used to conduct functional demonstrations of space-based space surveillance. The JHU/Applied Physics Laboratory (APL), located in Laurel, MD, is the integrator and operator of the MSX satellite. APL will conduct all operations related to the MSX and is charged with the detailed operations planning required to implement all of the experiments run on the MSX except the space surveillance experiments. The non-surveillance operations are generally amenable to being defined months ahead of time and being scheduled on a monthly basis. Lincoln Laboratory, Massachusetts Institute of Technology (LL), located in Lexington, MA, is the provider of one of the principle MSX instruments, the Space-Based Visible (SBV) sensor, and the agency charged with implementing the space surveillance demonstrations on the MSX. The planning timelines for the space surveillance demonstrations are fundamentally different from those for the other experiments. They are generally amenable to being scheduled on a monthly basis, but the specific experiment sequence and pointing must be refined shortly before execution. This allocation of responsibilities to different organizations implies the need for a joint mission planning system for conducting space surveillance demonstrations. This paper details the iterative, joint planning system, based on passing responsibility for generating MSX commands for surveillance operations from APL to LL for specific scheduled operations. The joint planning system, including the generation of a budget for spacecraft resources to be used for surveillance events, has been successfully demonstrated during ground testing of the MSX and is being validated for MSX launch within the year. The planning system developed for the MSX forms a model possibly applicable to developing distributed mission planning systems for other multi-use satellites.

Stokes, Grant↗
NASA NTRS2011

Developing a Prototype ALHAT Human System Interface for Landing

The goal of the Autonomous Landing and Hazard Avoidance Technology (ALHAT) project is to safely execute a precision landing anytime/anywhere on the moon. This means the system must operate in any lighting conditions, operate in the presence of any thruster generated regolith clouds, and operate without the help of redeployed navigational aids or prepared landing site at the landing site. In order to reach this ambitious goal, computer aided technologies such as ALHAT will be needed in order to permit these landings to be done safely. Although there will be advanced autonomous capabilities onboard future landers, humans will still be involved (either onboard as astronauts or remotely from mission control) in any mission to the moon or other planetary body. Because many time critical decisions must be made quickly and effectively during the landing sequence, the Descent and Landing displays need to be designed to be as effective as possible at presenting the pertinent information to the operator, and allow the operators decisions to be implemented as quickly as possible. The ALHAT project has established the Human System Interface (HSI) team to lead in the development of these displays and to study the best way to provide operators enhanced situational awareness during landing activities. These displays are prototypes that were developed based on multiple design and feedback sessions with the astronaut office at NASA/ Johnson Space Center. By working with the astronauts in a series of plan/build/evaluate cycles, the HSI team has obtained astronaut feedback from the very beginning of the design process. In addition to developing prototype displays, the HSI team has also worked to provide realistic lunar terrain (and shading) to simulate a "out the window" view that can be adjusted to various lighting conditions (based on a desired date/time) to allow the same terrain to be viewed under varying lighting terrain. This capability will be critical to determining the effect of terrain/lighting on the human pilot, and how they use windows and displays during landing activities. The Apollo missions were limited to about 28 possible launch days a year due to lighting and orbital constraints. In order to take advantage of more landing opportunities and venture to more challenging landing locations, future landers will need to utilize sensors besides human eyes for scanning the surface. The ALHAT HSI system must effectively convey ALHAT produced information to the operator, so that landings can occur during less "optimal" conditions (lighting, surface terrain, slopes, etc) than was possible during Apollo missions. By proving this capability, ALHAT will simultaneously provide more flexible access to the moon, and greater safety margins for future landers. This paper will specifically focus on the development of prototype displays (the Trajectory Profile Display (TPD), Landing Point Designation (LPD), and Crew Camera View (CCV) ), implementation of realistic planetary terrain, human modeling, and future HSI plans.

Hirsh, Robert L.↗
NASA NTRS2007

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

Space robotic system for proximity operations

Key to an efficient accomplishment of space station servicing operations is the development of a scenario where the presence of man in space is well integrated with the capability of teleoperated and automatic robot system outside the stations. Results focusing on mission requirements, trajectory sequences, propulsion subsystem features, and manipulative kit characteristics relevant to proximity servicing during a Man Tended Free Flyers Robotic Mission (MTFF-RM) are illustrated.

Magnani, P. G.↗
NASA NTRS2011

Project Report: Automatic Sequence Processor Software Analysis

The Mission Planning and Sequencing (MPS) element of Multi-Mission Ground System and Services (MGSS) provides space missions with multi-purpose software to plan spacecraft activities, sequence spacecraft commands, and then integrate these products and execute them on spacecraft. Jet Propulsion Laboratory (JPL) is currently is flying many missions. The processes for building, integrating, and testing the multi-mission uplink software need to be improved to meet the needs of the missions and the operations teams that command the spacecraft. The Multi-Mission Sequencing Team is responsible for collecting and processing the observations, experiments and engineering activities that are to be performed on a selected spacecraft. The collection of these activities is called a sequence and ultimately a sequence becomes a sequence of spacecraft commands. The operations teams check the sequence to make sure that no constraints are violated. The workflow process involves sending a program start command, which activates the Automatic Sequence Processor (ASP). The ASP is currently a file-based system that is comprised of scripts written in perl, c-shell and awk. Once this start process is complete, the system checks for errors and aborts if there are any; otherwise the system converts the commands to binary, and then sends the resultant information to be radiated to the spacecraft.

sequencing↗
NASA NTRS2012

Agile Science Operations: A New Approach for Primitive Exploration Bodies

Primitive body exploration missions such as potential Comet Surface Sample Return or Trojan Tour and Rendezvous would challenge traditional operations practices. Earth-based observations would provide only basic understanding before arrival and many science goals would be defined during the initial rendezvous. It could be necessary to revise trajectories and observation plans to quickly characterize the target for safe, effective observations. Detection of outgassing activity and monitoring of comet surface activity are even more time constrained, with events occurring faster than round-trip light time. "Agile science operations" address these challenges with contingency plans that recognize the intrinsic uncertainty in the operating environment and science objectives. Planning for multiple alternatives can significantly improve the time required to repair and validate spacecraft command sequences. When appropriate, time-critical decisions can be automated and shifted to the spacecraft for immediate access to instrument data. Mirrored planning systems on both sides of the light-time gap permit transfer of authority back and forth as needed. We survey relevant science objectives, identifying time bottlenecks and the techniques that could be used to speed missions' reaction to new science data. Finally, we discuss the results of a trade study simulating agile observations during flyby and comet rendezvous scenarios. These experiments quantify instrument coverage of key surface features as a function of planning turnaround time. Careful application of agile operations techniques can play a significant role in realizing the Decadal Survey plan for primitive body exploration

Agile science↗
NASA NTRS2008

Cassini Information Management System in Distributed Operations Collaboration and Cassini Science Planning

Launched on October 15, 1997, the Cassini-Huygens spacecraft began its ambitious journey to the Saturnian system with a complex suite of 12 scientific instruments, and another 6 instruments aboard the European Space Agencies Huygens Probe. Over the next 6 1/2 years, Cassini would continue its relatively simplistic cruise phase operations, flying past Venus, Earth, and Jupiter. However, following Saturn Orbit Insertion (SOI), Cassini would become involved in a complex series of tasks that required detailed resource management, distributed operations collaboration, and a data base for capturing science objectives. Collectively, these needs were met through a web-based software tool designed to help with the Cassini uplink process and ultimately used to generate more robust sequences for spacecraft operations. In 2001, in conjunction with the Southwest Research Institute (SwRI) and later Venustar Software and Engineering Inc., the Cassini Information Management System (CIMS) was released which enabled the Cassini spacecraft and science planning teams to perform complex information management and team collaboration between scientists and engineers in 17 countries. Originally tailored to help manage the science planning uplink process, CIMS has been actively evolving since its inception to meet the changing and growing needs of the Cassini uplink team and effectively reduce mission risk through a series of resource management validation algorithms. These algorithms have been implemented in the web-based software tool to identify potential sequence conflicts early in the science planning process. CIMS mitigates these sequence conflicts through identification of timing incongruities, pointing inconsistencies, flight rule violations, data volume issues, and by assisting in Deep Space Network (DSN) coverage analysis. In preparation for extended mission operations, CIMS has also evolved further to assist in the planning and coordination of the dual playback redundancy of highvalue data from targets such as Titan and Enceladus. This paper will outline the critical role that CIMS has played for Cassini in the distributed ops paradigm throughout operations. This paper will also examine the evolution that CIMS has undergone in the face of new science discoveries and fluctuating operational needs. And finally, this paper will conclude with theoretical adaptation of CIMS for other projects and the potential savings in cost and risk reduction that could potentially be tapped into by future missions.

Equils, Douglas J.↗
NASA NTRS1994

Re-engineering the Multimission Command System at the Jet Propulsion Laboratory

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.

Alexander, Scott↗
NASA NTRS1991

Information Flow Analysis of Level 4 Payload Processing Operations

The Level 4 Mission Sequence Test (MST) was studied to develop strategies and recommendations to facilitate information flow. Recommendations developed as a result of this study include revised format of the Test and Assembly Procedure (TAP) document and a conceptualized software based system to assist in the management of information flow during the MST.

Danz, Mary E.↗
NASA NTRS1994

Simplifying Operations with an Uplink/Downlink Integration Toolkit

The Operations Engineering Lab (OEL) at JPL has developed a simple, generic toolkit to integrate the uplink/downlink processes (often called closing the loop) in JPL's Multimission Ground Data System. This toolkit provides capabilities for integrating telemetry verification points with predicted spacecraft commands and ground events in the Mission Sequence of Events (SOE) document. This toolkit is designed to greatly simplify the user's ability to access and view telemetry data, and also provide a means to view this data in a context of the commands and ground events that are used to interpret it. This paper will discuss the toolkit implementation, including design trade-offs and future for enhancing the automated capabilities.

ground↗
NASA NTRS2016

Safety Characteristics in System Application of Software for Human Rated Exploration Missions for the 8th IAASS Conference

NASA and its industry and international partners are embarking on a bold and inspiring development effort to design and build an exploration class space system. The space system is made up of the Orion system, the Space Launch System (SLS) and the Ground Systems Development and Operations (GSDO) system. All are highly coupled together and dependent on each other for the combined safety of the space system. A key area of system safety focus needs to be in the ground and flight application software system (GFAS). In the development, certification and operations of GFAS, there are a series of safety characteristics that define the approach to ensure mission success. This paper will explore and examine the safety characteristics of the GFAS development. The GFAS system integrates the flight software packages of the Orion and SLS with the ground systems and launch countdown sequencers through the 'agile' software development process. A unique approach is needed to develop the GFAS project capabilities within this agile process. NASA has defined the software development process through a set of standards. The standards were written during the infancy of the so-called industry 'agile development' movement and must be tailored to adapt to the highly integrated environment of human exploration systems. Safety of the space systems and the eventual crew on board is paramount during the preparation of the exploration flight systems. A series of software safety characteristics have been incorporated into the development and certification efforts to ensure readiness for use and compatibility with the space systems. Three underlining factors in the exploration architecture require the GFAS system to be unique in its approach to ensure safety for the space systems, both the flight as well as the ground systems. The first are the missions themselves, which are exploration in nature, and go far beyond the comfort of low Earth orbit operations. The second is the current exploration system will launch only one mission per year even less during its developmental phases. Finally, the third is the partnered approach through the use of many different prime contractors, including commercial and international partners, to design and build the exploration systems. These three factors make the challenges to meet the mission preparations and the safety expectations extremely difficult to implement. As NASA leads a team of partners in the exploration beyond earth's influence, it is a safety imperative that the application software used to test, checkout, prepare and launch the exploration systems put safety of the hardware and mission first. Software safety characteristics are built into the design and development process to enable the human rated systems to begin their missions safely and successfully. Exploration missions beyond Earth are inherently risky, however, with solid safety approaches in both hardware and software, the boldness of these missions can be realized for all on the home planet.

capability↗
NASA NTRS1973

Design of Mariner 9 Science Sequences using Interactive Graphics Software

This paper discusses the analyst/computer system used to design the daily science sequences required to carry out the desired Mariner 9 science plan. The Mariner 9 computer environment, the development and capabilities of the science sequence design software, and the techniques followed in the daily mission operations are discussed. Included is a discussion of the overall mission operations organization and the individual components which played an essential role in the sequence design process. A summary of actual sequences processed, a discussion of problems encountered, and recommendations for future applications are given.

Freeman, J. E.↗
NASA NTRS2010

Trade Spaces in Crewed Spacecraft Atmosphere Revitalization System Development

Developing the technological response to realizing an efficient atmosphere revitalization system for future crewed spacecraft and space habitats requires identifying and describing functional trade spaces. Mission concepts and requirements dictate the necessary functions; however, the combination and sequence of those functions possess significant flexibility. Us-ing a closed loop environmental control and life support (ECLS) system architecture as a starting basis, a functional unit operations approach is developed to identify trade spaces. Generalized technological responses to each trade space are discussed. Key performance parameters that apply to functional areas are described.

Perry, Jay L.↗