Planning in interplanetary space: theory and practice

Ari Jónsson, Paul Morris, Nicola Muscettola, Kanna Rajan, Ben Smith

2000 · 280 citations · 11 references

Concepts

TL;DR

NASA activated an AI‑based planner on May 17, 1999 as part of the Remote Agent Experiment, demonstrating closed‑loop planning, execution, state inference, and failure recovery. The paper presents the RAX Planner/Scheduler, detailing its planning framework and its deployment in a fielded system. RAX‑PS constructs constraint‑network plans incrementally from a spacecraft dynamics model, producing temporally flexible plans while addressing engineering concerns such as programmable search control, knowledge acquisition, and planner validation. The planning procedure is formally well defined and provably complete, and the system can build concurrent plans of over a hundred tasks within operational performance limits.

Abstract

On May 17th 1999, NASA activated for the first time an AI-based planner/scheduler running on the flight processor of a spacecraft. This was part of the Remote Agent Experiment (RAX), a demonstration of closed-loop planning and execution, and model-based state inference and failure recovery. This paper describes the RAX Planner/Scheduler (RAX-PS), both in terms of the underlying planning framework and in terms of the fielded planner. RAX-PS plans are networks of constraints, built incrementally by consulting a model of the dynamics of the spacecraft. The RAX-PS planning procedure is formally well defined and can be proved to be complete. RAX-PS generates plans that are temporally flexible, allowing the execution system to adjust to actual plan execution conditions without breaking the plan. The practical aspect, developing a mission critical application, required paying attention to important engineering issues such as the design of methods for programmable search control, knowledge acquisition and planner validation. The result was a system capable of building concurrent plans with over a hundred tasks within the performance requirements of operational, mission-critical software.

References

11