Search NASA⌕ Search

SEARCH · Search NASA

Results for “planning and scheduling”

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 379 records · Page 21
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

Project M: Scale Model of Lunar Landing Site of Apollo 17

The basis of the project was creating a scale model representation of the Apollo 17 lunar landing site. Vital components included surface slope characteristics, crater sizes and locations, prominent rocks, and lighting conditions. The model was made for Project M support when evaluating approach and terminal descent as well as when planning surface operations with respect to the terrain. The project had five main mi lestones during the length of the project. The first was examining the best method to use to re-create the Apollo 17 landing site and then reviewing research fmdings with Dr. Tim Crain and EO staff which occurred on June 25, 2010 at a meeting. The second step was formulating a construction plan, budget, and schedule and then presenting the plan for authority to proceed which occurred on July 6,2010. The third part was building a prototype to test materials and building processes which were completed by July 13, 2010. Next was assembling the landing site model and presenting a mid-term construction status report on July 29, 2010. The fifth and final milestone was demonstrating the model and presenting an exit pitch which happened on August 4, 2010. The project was very technical: it needed a lot of research about moon topography, lighting conditions and angles of the sun on the moon, Apollo 17, and Autonomous Landing and Hazard Avoidance Technology (ALHAT), before starting the actual building process. This required using Spreadsheets, searching internet sources and conducting personal meetings with project representatives. This information assisted the interns in deciding the scale of the model with respect to cracks, craters and rocks and their relative sizes as the objects mentioned could interfere with any of the Lunar Landers: Apollo, Project M and future Landers. The project concluded with the completion of a three dimensional scale model of the Apollo 17 Lunar landing site. This model assists Project M members because they can now visualize approach phase, terminal descent phase, and surface phase operations on the physical model. The project had an additional requirement that was also satisfied: the granite table the model was placed on must be returnable to its original condition if needed in the future.

O'Brien, Hollie↗
NASA NTRS1989

Space applications of artificial intelligence; Proceedings of the Annual Goddard Conference, Greenbelt, MD, May 16, 17, 1989

Theoretical and implementation aspects of AI systems for space applications are discussed in reviews and reports. Sections are devoted to planning and scheduling, fault isolation and diagnosis, data management, modeling and simulation, and development tools and methods. Particular attention is given to a situated reasoning architecture for space repair and replace tasks, parallel plan execution with self-processing networks, the electrical diagnostics expert system for Spacelab life-sciences experiments, diagnostic tolerance for missing sensor data, the integration of perception and reasoning in fast neural modules, a connectionist model for dynamic control, and applications of fuzzy sets to the development of rule-based expert systems.

Rash, James L.↗
NASA NTRS2005

Coordinated Science Campaign Scheduling for Sensor Webs

Future Earth observing missions will study different aspects and interacting pieces of the Earth's eco-system. Scientists are designing increasingly complex, interdisciplinary campaigns to exploit the diverse capabilities of multiple Earth sensing assets. In addition, spacecraft platforms are being configured into clusters, trains, or other distributed organizations in order to improve either the quality or the coverage of observations. These simultaneous advances in the design of science campaigns and in the missions that will provide the sensing resources to support them offer new challenges in the coordination of data and operations that are not addressed by current practice. For example, the scheduling of scientific observations for satellites in low Earth orbit is currently conducted independently by each mission operations center. An absence of an information infrastructure to enable the scheduling of coordinated observations involving multiple sensors makes it difficult to execute campaigns involving multiple assets. This paper proposes a software architecture and describes a prototype system called DESOPS (Distributed Earth Science Observation Planning and Scheduling) that will address this deficiency.

Edgington, Will↗
NASA NTRS2006

Scheduling with Automatic Resolution of Conflicts

DSN Requirement Scheduler is a computer program that automatically schedules, reschedules, and resolves conflicts for allocations of resources of NASA s Deep Space Network (DSN) on the basis of ever-changing project requirements for DSN services. As used here, resources signifies, primarily, DSN antennas, ancillary equipment, and times during which they are available. Examples of project-required DSN services include arraying, segmentation, very-long-baseline interferometry, and multiple spacecraft per aperture. Requirements can include periodic reservations of specific or optional resources during specific time intervals or within ranges specified in terms of starting times and durations. This program is built on the Automated Scheduling and Planning Environment (ASPEN) software system (aspects of which have been described in previous NASA Tech Briefs articles), with customization to reflect requirements and constraints involved in allocation of DSN resources. Unlike prior DSN-resource- scheduling programs that make single passes through the requirements and require human intervention to resolve conflicts, this program makes repeated passes in a continuing search for all possible allocations, provides a best-effort solution at any time, and presents alternative solutions among which users can choose.

Clement, Bradley↗
NASA NTRS2004

Argumentation for coordinating shared activities

There is an increasing need for space missions to be able to collaboratively (and competitively) develop plans both within and across missions. In addition, interacting spacecraft that interleave onboard planning and execution must reach consensus on their commitments to each other prior to execution.

scheduling↗
NASA NTRS2009

Peer-to-Peer Planning for Space Mission Control

Planning and scheduling for space operations entails the development of applications that embed intimate domain knowledge of distinct areas of mission control, while allowing for significant collaboration among them. The separation is useful because of differences in the planning problem, solution methods, and frequencies of replanning that arise in the different disciplines. For example, planning the activities of human spaceflight crews requires some reasoning about all spacecraft resources at timescales of minutes or seconds, and is subject to considerable volatility. Detailed power planning requires managing the complex interplay of power consumption and production, involves very different classes of constraints and preferences, but once plans are generated they are relatively stable.

Barreiro, Javier↗
NASA NTRS2001

Test oracle automation for V&V of an autonomous spacecraft's planner

We built automation to assist the software testing efforts associated with the Remote Agent experiment. In particular, our focus was upon introducing test oracles into the testing of the planning and scheduling system component. This summary is intended to provide an overview of the work.

testing test oracles verification validation analy↗
NASA NTRSDate not supplied

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol(Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.

activity planning↗
NASA NTRSDate not supplied

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol(Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.

activity planning↗
NASA NTRS2022

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol (Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.

Kanefsky, Bob↗
NASA NTRS2005

Software for Optimizing Plans Involving Interdependent Goals

A computer program enables construction and optimization of plans for activities that are directed toward achievement of goals that are interdependent. Goal interdependence is defined as the achievement of one or more goals affecting the desirability or priority of achieving one or more other goals. This program is overlaid on the Automated Scheduling and Planning Environment (ASPEN) software system, aspects of which have been described in a number of prior NASA Tech Briefs articles. Unlike other known or related planning programs, this program considers interdependences among goals that can change between problems and provides a language for easily specifying such dependences. Specifications of the interdependences can be formulated dynamically and provided to the associated planning software as part of the goal input. Then an optimization algorithm provided by this program enables the planning software to reason about the interdependences and incorporate them into an overall objective function that it uses to rate the quality of a plan under construction and to direct its optimization search. In tests on a series of problems of planning geological experiments by a team of instrumented robotic vehicles (rovers) on new terrain, this program was found to enhance plan quality.

Estlin, Tara↗
NASA NTRS2018

Playbook for UAS: UX of Goal-Oriented Planning & Execution

We are evaluating the tool Playbook, a mission planning and scheduling tool used for analog missions and research experiments at NASA. We are adapting Playbook to support an unmanned aerial vehicle (UAV) demonstration that will simulate a "search and recover" mission. To support this demonstration, we need to test this software and its usability with human subjects. Playbook will be used to plan, edit, and monitor simulated UAV swarms, and we are interested in evaluating these capabilities. Allocation of roles and responsibilities between human-automation systems is key to promoting productive cooperation between these two agents. When guiding swarms the user should not be concerned with moving waypoints, adjusting heading and altitude or any other small actions that traditional pilots control. Providing situational awareness through sensor data including radar, heat, live camera feed, and topographic information are key when managing multiple UAVs together. First responders need a good picture of disaster areas in order to make informed decisions. These sensors can initiate movements in the mission that indicate when the human should take control of single aircraft.

UAV swarms↗
NASA NTRS1976

Formulation of detailed consumables management models for the development (preoperational) period of advanced space transportation system: Executive summary

Formulation of models required for the mission planning and scheduling function and establishment of the relation of those models to prelaunch, onboard, ground support, and postmission functions for the development phase of space transportation systems (STS) was conducted. The preoperational space shuttle is used as the design baseline for the subject model formulations. Analytical models were developed which consist of a mission planning processor with appropriate consumables data base and a method of recognizing potential constraint violations in both the planning and flight operations functions. A flight data file for storage/retrieval of information over an extended period which interfaces with a flight operations processor for monitoring of the actual flights was examined.

Torian, J. G.↗
NASA NTRS2008

Spatial Coverage Planning and Optimization for Planetary Exploration

We are developing onboard planning and scheduling technology to enable in situ robotic explorers, such as rovers and aerobots, to more effectively assist scientists in planetary exploration. In our current work, we are focusing on situations in which the robot is exploring large geographical features such as craters, channels or regional boundaries. In to develop valid and high quality plans, the robot must take into account a range of scientific and engineering constraints and preferences. We have developed a system that incorporates multiobjective optimization and planning allowing the robot to generate high quality mission operations plans that respect resource limitations and mission constraints while attempting to maximize science and engineering objectives. An important scientific objective for the exploration of geological features is selecting observations that spatially cover an area of interest. We have developed a metric to enable an in situ explorer to reason about and track the spatial coverage quality of a plan. We describe this technique and show how it is combined in the overall multiobjective optimization and planning algorithm.

autonomy↗
NASA NTRS2010

Adapting ASPEN for Orbital Express

By studying the Orbital Express mission, modeling the spacecraft and scenarios, and testing the system, a technique has been developed that uses recursive decomposition to represent procedural actions declaratively, schema-level uncertainty reasoning to make uncertainty reasoning tractable, and lightweight, natural language processing to automatically parse procedures to produce declarative models. Schema-level uncertainty reasoning has, at its core, the basic assumption that certain variables are uncertain, but not independent. Once any are known, then the others become known. This is important where a variable is uncertain for an action and many actions of the same type exist in the plan. For example, if the number of retries to purge pump lines was unknown (but bounded), and each attempt required a sub-plan, then, once the correct number of attempts required for a purge was known, it would likely be the same for all subsequent purges. This greatly reduces the space of plans that needs to be searched to ensure that all executions are feasible. To accommodate changing scenario procedures, each is ingested into a tabular format in temporal order, and a simple natural-language parser is used to read each step and to derive the impact of that step on memory, power, and communications. Then an ASPEN (Activity Scheduling and Planning Environment) model is produced based on this analysis. The model is tested and further changed by hand, if necessary, to reflect the actual procedure. This results in a great savings of time used for modeling procedures. Many processes that need to be modeled in ASPEN (a declarative system) are, in fact, procedural. ASPEN includes the ability to model activities in a hierarchical fashion, but this representation breaks down if there is a practically unbounded number of sub-activities and decomposition topologies. However, if recursive decomposition is allowed, HTN-like encodings are enabled to represent most procedural phenomena. For example, if a switch requires a variable (but known at the time of the attempt) number of attempts to switch on, one can recurse on the number of remaining switch attempts and decompose into either the same switching activity with one less required attempt, or not decompose at all (or decompose into a dummy task), resulting in the end of the decomposition. In fact, any bounded procedural behavior can be modeled using recursive decompositions assuming that the variables impinging the disjunctive decomposition decision are computable at the time that the decision is made. This enables one to represent tasks that are controlled outside of the scheduler, but that the scheduler must accommodate, without requiring one to give a declarative model of the procedural behavior.

Chouinard, Caroline↗
NASA NTRS2018

Innovative Development of a Cross-Center Timeline Planning Tool

The Payload Operations Integration Center (POIC) at Marshall Space Flight Center (MSFC) is the United States focal point to support operations controllers and payload developers conducting payload science operations for the National Aeronautics and Space Administration (NASA) aboard the International Space Station (ISS). Some of the key functions are planning, coordination and scheduling of science activities. This effort occurs in coordination with other NASA centers, international partners, and payload developers. The ability to efficiently plan and re-plan in response to change is critical to the flight planning teams. Additionally, in Fall 2017, NASA will increase its ability to perform payload science operations aboard the ISS with a fourth crew member. In order to support this, there will be an increasing need to quickly plan and schedule more activities. In the past, it was cumbersome and time-consuming to consolidate copious amounts of planning and change request data from various sources. Planners would summarize information from the Johnson Space Center (JSC) Operations Planning Timeline Integration System (OPTIMIS) and manually integrate it with other data in order to produce a Timeline Planning Summary (TPS). This lengthy process of updating static documents while planning and re-planning was cumbersome, introduced human error, and was inflexible to last minute changes. There was a need for a dynamic, more efficient, less erroneous, and more concise way of building a report that could be readily updated as fast as payload science plans change.

Pedoto, Ramon W.↗