Search NASA⌕ Search

SEARCH · Search NASA

Results for “Execution Plan”

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 217 records · Page 12
All sourcesNASA NTRSDOE OSTI
NASA NTRS1993

A Generalized-Compliant-Motion Primitive

Computer program bridges gap between planning and execution of compliant robotic motions developed and installed in control system of telerobot. Called "generalized-compliant-motion primitive," one of several task-execution-primitive computer programs, which receives commands from higher-level task-planning programs and executes commands by generating required trajectories and applying appropriate control laws. Program comprises four parts corresponding to nominal motion, compliant motion, ending motion, and monitoring. Written in C language.

Backes, Paul G.↗
NASA NTRS2017

Integrated Extravehicular Activity Human Research Plan: 2017

Multiple organizations within NASA as well as industry and academia fund and participate in research related to extravehicular activity (EVA). In October 2015, representatives of the EVA Office, the Crew and Thermal Systems Division (CTSD), and the Human Research Program (HRP) at NASA Johnson Space Center agreed on a formal framework to improve multi-year coordination and collaboration in EVA research. At the core of the framework is an Integrated EVA Human Research Plan and a process by which it will be annually reviewed and updated. The over-arching objective of the collaborative framework is to conduct multi-disciplinary cost-effective research that will enable humans to perform EVAs safely, effectively, comfortably, and efficiently, as needed to enable and enhance human space exploration missions. Research activities must be defined, prioritized, planned and executed to comprehensively address the right questions, avoid duplication, leverage other complementary activities where possible, and ultimately provide actionable evidence-based results in time to inform subsequent tests, developments and/or research activities. Representation of all appropriate stakeholders in the definition, prioritization, planning and execution of research activities is essential to accomplishing the over-arching objective. A formal review of the Integrated EVA Human Research Plan will be conducted annually. Coordination with stakeholders outside of the EVA Office, CTSD, and HRP is already in effect on a study-by-study basis; closer coordination on multi-year planning with other EVA stakeholders including academia is being actively pursued. Details of the preliminary Integrated EVA Human Research Plan are presented including description of ongoing and planned research activities in the areas of: physiological and performance capabilities; suit design parameters; EVA human health and performance modeling; EVA tasks and concepts of operations; EVA informatics; human-suit sensors; suit sizing and fit; and EVA injury risk and mitigation. This paper represents the 2017 update to the Integrated EVA Human Research Plan.

Abercromby, Andrew↗
NASA NTRS2010

Collective Intelligence and Three Aspects of Planning in Organizations: A NASA Example

For many complex sociotechnical systems, planning seems to require explicit coordination; certainly, in executing a plan the activities of different actors must be tightly coupled. However, distributing the needed planning information can be very burdensome and error prone, because different groups need different collections of information, updated or kept current on different time cycles. Further, the information needed to form successful plans is often highly distributed, and while feedback about the success of prior plans may exist, it may not be available to those in a position of using this to improve plans or to detect and resolve other problems in the system (Weick, 1995). Tools to support various aspects of planning have been developed, and can provide a huge benefit to the individuals working on that aspect. To be tractable, most solutions address a quite bounded slice of work, isolating it from the larger context. Prospective planning takes place over multiple, nested cycles of decision making. This builds a plan that specifies activities of different granularity. "Subplans" may specify multiple parallel activities by different groups and individuals, as well as sequential, nested actions by a single actor. Planning produces valuable, sharable, external, representations: in addition to prospective use, plans support retrospective assessment and also action in the present. Viewing planning in a larger context - both temporal and organizational -- enables noticing what one does not know and generating more systemic and effective solutions. Viewing a problem as one of collective intelligence invites thinking about the larger organizational context. Many approaches to supporting collective intelligence do not support execution of highly contingent actions, distributed across many players, and hence provide incomplete support for planning. However, CI technology maybe helpful in managing the processes of gathering information for decision making in planning and of distributing plan information to various actors, needed on various time cycles.

Billman, Dorrit↗
NASA NTRS2000

Autonomy Architectures for a Constellation of Spacecraft

Until the past few years, missions typically involved fairly large expensive spacecraft. Such missions have primarily favored using older proven technologies over more recently developed ones, and humans controlled spacecraft by manually generating detailed command sequences with low-level tools and then transmitting the sequences for subsequent execution on a spacecraft controller. This approach toward controlling a spacecraft has worked spectacularly on previous missions, but it has limitations deriving from communications restrictions - scheduling time to communicate with a particular spacecraft involves competing with other projects due to the limited number of deep space network antennae. This implies that a spacecraft can spend a long time just waiting whenever a command sequence fails. This is one reason why the New Millennium program has an objective to migrate parts of mission control tasks onboard a spacecraft to reduce wait time by making spacecraft more robust. The migrated software is called a "remote agent" and has 4 components: a mission manager to generate the high level goals, a planner/scheduler to turn goals into activities while reasoning about future expected situations, an executive/diagnostics engine to initiate and maintain activities while interpreting sensed events by reasoning about past and present situations, and a conventional real-time subsystem to interface with the spacecraft to implement an activity's primitive actions. In addition to needing remote planning and execution for isolated spacecraft, a trend toward multiple-spacecraft missions points to the need for remote distributed planning and execution. The past few years have seen missions with growing numbers of probes. Pathfinder has its rover (Sojourner), Cassini has its lander (Huygens), and the New Millenium Deep Space 3 (DS3) proposal involves a constellation of 3 spacecraft for interferometric mapping. This trend is expected to continue to progressively larger fleets. For example, one mission proposed to succeed DS3 would have 18 spacecraft flying in formation in order to detect earth-sized planets orbiting other stars. A proposed magnetospheric constellation would involve 5 to 500 spacecraft in Earth orbit to measure global phenomena within the magnetosphere. This work describes and compares three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals or 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 or even a hundred spacecraft (such as for interferometry or plasma physics missions). The easiest way to adapt autonomous spacecraft research to controlling constellations involves treating the constellation as a single spacecraft. Here one spacecraft directly controls the others as if they were connected. The controlling "master" spacecraft performs all autonomy reasoning, and the slaves only have real-time subsystems to execute the master's commands and transmit local telemetry/observations. The executive/diagnostics module starts actions and the master's real-time subsystem controls the action either locally or remotely through a slave. While the master/slave approach benefits from conceptual simplicity, it relies on an assumption that the master spacecraft's executive can continuously monitor the slaves' real-time subsystems, and this relies on high-bandwidth highly-reliable communications. Since unintended results occur fairly rarely, one way to relax the bandwidth requirements involves only monitoring unexpected events in spacecraft. Unfortunately, this disables the ability to monitor for unexpected events between spacecraft and leads to a host of coordination problems among the slaves. Also, failures in the communications system can result in losing slaves. The other two architectures improve robustness while reducing communications by progressively distributing more of the other three remote agent components across the constellation. In a teamwork architecture, all spacecraft have executives and real-time subsystems - only the leader has the planner/scheduler and mission manager. Finally, distributing all remote agent components leads to a peer-to-peer approach toward constellation control.

Barrett, Anthony↗
NASA NTRS1989

Automating Space Station operations planning

The development and implementation of the operations planning processes for the Space Station are discussed. A three level planning process, consisting of strategic, tactical, and execution level planning, is being developed. The integration of the planning procedures into a tactical planning system is examined and the planning phases are illustrated.

Ziemer, Kathleen A.↗
NASA NTRS2016

Mission Planning for Robotic and Human Exploration

Mission planning for spaceflight is a complex challenge for ground operators managing robotic or human missions. It requires integrating the needs of various disciplines and creating an effective, efficient, and safe plan to execute. NASA uses specialized tools to meet planning requirements and constraints. This talk will provide an overview of spaceflight mission planning as well as the software tools the Human-Computer Interaction Group has built to support scheduling and planning. Also, it identifies the future scheduling and planning challenges for human Mars missions and how we leverage Earth Analogs to learn about Mars operations.

Scheduling and planning↗
NASA NTRS2007

Implementation of a Collision Probability Prediction Technique for Constellation Maneuver Planning

On March 22, 2006, the Space Technology 5 (ST5) constellation spacecraft were successfully delivered to orbit by a Pegasus XI, launch vehicle. An unexpected relative motion experienced by the constellation after orbit insertion brought about a problem. Soon after launch the observed relative position of the inert rocket body was between the leading and the middle spacecraft within the constellation. The successful planning and execution of an orbit maneuver that would create a fly-by of the rocket body was required to establish the.formation. This maneuver would create a close approach that needed to conform to predefined collision probability requirements. On April 21, 2006, the ST5 "155" spacecraft performed a large orbit maneuver and successfully passed the inert Pegasus 3rd Stage Rocket Body on April 30, 2006 15:20 UTC at a distance of 2.55 km with a Probability of Collision of less than 1.0E-06. This paper will outline the technique that was implemented to establish the safe planning and execution of the fly-by maneuver. The method makes use of Gaussian distribution models of state covariance to determine underlying probabilities of collision that arise under low velocity encounters. Specific numerical examples used for this analysis are discussed in detail. The mechanics of this technique are explained to foster deeper understanding of the concepts presented and to improve existing processes for use in future constellation maneuver planning.

Concha, Marco a.↗
NASA NTRS2024

Smallsat 2024 - Starling Cubesat Swarm Technology Demonstration Flight Results

The Starling swarm of four 6U CubeSats launched in July 2023 to test four key technologies to enable future swarm missions: 1) Mobile Ad-Hoc Networking (MANET) over a crosslink radio network 2) Autonomous onboard decision-making for operations 3) Optical-based absolute and relative navigation 4) Autonomous maneuver planning and execution The Starling team implemented the Better Approach to Mobile Ad-hoc Networking (B.A.T.M.A.N.) protocol to automatically manage the crosslink network of four satellites. The B.A.T.M.A.N. protocol uses a decentralized approach to managing a multi-hop mesh network of devices, in this case, a satellite swarm. The four satellites were able to successfully establish a network at multiple data rates and demonstrate file transfer and command issuance between spacecraft over the network. Starling incorporated Distributed Spacecraft Autonomy's (DSA) software to demonstrate onboard decision-making. The DSA software takes L1/L2 band GPS measurements and uses them to estimate the relative Total Electron Count (TEC) in the ionosphere. The onboard software then determines if there are any features of interest and provides that information to the other satellites over the crosslink network. The swarm of satellites then reaches a consensus on the optimal TEC observation strategy and adjusts its measurement collection tactics autonomously. The Starling Formation-Flying Optical Experiment (StarFOX), produced by Stanford's Space Rendezvous Laboratory, uses the onboard star trackers to collect images of the other swarm spacecraft and produce angles-only navigation estimates. This system is envisioned to be valuable in applications in which Global Navigation Satellite Systems (GNSS) are not available, such as in cis-lunar or deep space. StarFOX successfully applied its algorithms to multiple simultaneous spacecraft targets using the star tracker imagery. Finally, Starling used Emergent Space's Cluster Flight Application (CFA) software suite for the Reconfiguration and Orbit Maintenance Experiments Onboard (ROMEO) demonstration of autonomously planning and executing propulsive maneuvers. Large swarms will need to be able to maintain formation requirements with minimal operator involvement, especially as the size of the swarm scales up. Results from the ROMEO experiment are presented. Starling is funded by the Small Spacecraft Technology (SST) program out of NASA's Space Technology Mission Directorate (STMD).

distributed systems↗
NASA NTRS1987

Systems autonomy technology: Executive summary and program plan

The National Space Strategy approved by the President and Congress in 1984 sets for NASA a major goal of conducting effective and productive space applications and technology programs which contribute materially toward United States leadership and security. To contribute to this goal, OAST supports the Nation's civil and defense space programs and overall economic growth. OAST objectives are to ensure timely provision of new concepts and advanced technologies, to support both the development of NASA missions in space and the space activities of industry and other organizations, to utilize the strengths of universities in conducting the NASA space research and technology program, and to maintain the NASA centers in positions of strength in critical space technology areas. In line with these objectives, NASA has established a new program in space automation and robotics that will result in the development and transfer and automation technology to increase the capabilities, productivity, and safety of NASA space programs including the Space Station, automated space platforms, lunar bases, Mars missions, and other deep space ventures. The NASA/OAST Automation and Robotics program is divided into two parts. Ames Research Center has the lead role in developing and demonstrating System Autonomy capabilities for space systems that need to make their own decisions and do their own planning. The Jet Propulsion Laboratory has the lead role for Telerobotics (that portion of the program that has a strong human operator component in the control loop and some remote handling requirement in space). This program is intended to be a working document for NASA Headquarters, Program Offices, and implementing Project Management.

Bull, John S↗
NASA NTRS1994

A software architecture for hard real-time execution of automatically synthesized plans or control laws

The design of a flexible, real-time software architecture for trajectory planning and automatic control of redundant manipulators is described. Emphasis is placed on a technique of designing control systems that are both flexible and robust yet have good real-time performance. The solution presented involves an artificial intelligence algorithm that dynamically reprograms the real-time control system while planning system behavior.

Schoppers, Marcel↗
NASA NTRS2009

Aerobot Autonomy Architecture

An architecture for autonomous operation of an aerobot (i.e., a robotic blimp) to be used in scientific exploration of planets and moons in the Solar system with an atmosphere (such as Titan and Venus) is undergoing development. This architecture is also applicable to autonomous airships that could be flown in the terrestrial atmosphere for scientific exploration, military reconnaissance and surveillance, and as radio-communication relay stations in disaster areas. The architecture was conceived to satisfy requirements to perform the following functions: a) Vehicle safing, that is, ensuring the integrity of the aerobot during its entire mission, including during extended communication blackouts. b) Accurate and robust autonomous flight control during operation in diverse modes, including launch, deployment of scientific instruments, long traverses, hovering or station-keeping, and maneuvers for touch-and-go surface sampling. c) Mapping and self-localization in the absence of a global positioning system. d) Advanced recognition of hazards and targets in conjunction with tracking of, and visual servoing toward, targets, all to enable the aerobot to detect and avoid atmospheric and topographic hazards and to identify, home in on, and hover over predefined terrain features or other targets of scientific interest. The architecture is an integrated combination of systems for accurate and robust vehicle and flight trajectory control; estimation of the state of the aerobot; perception-based detection and avoidance of hazards; monitoring of the integrity and functionality ("health") of the aerobot; reflexive safing actions; multi-modal localization and mapping; autonomous planning and execution of scientific observations; and long-range planning and monitoring of the mission of the aerobot. The prototype JPL aerobot (see figure) has been tested extensively in various areas in the California Mojave desert.

Elfes, Alberto↗
NASA NTRSDate not supplied

Automating Maneuvers: Considerations for Collision Avoidance

As more space operators implement large constellations of spacecraft, automating orbit maintenance maneuvers becomes a key feature of their operations concept to ensure that the workload is manageable. However the practice of performing a maneuver without sharing the plan with other nearby spacecraft causes a risk that two spacecraft will collide, not only destroying the spacecraft involved, but creating debris that will affect all other spacecraft using that orbit regime. In order to share the maneuver plan, a predicted ephemeris file containing the maneuver must be sent to a central authority to screen against predicted trajectories of all other on-orbit objects to determine where and when close approaches may occur that need to be mitigated. Currently the screening authority used by US operators is the 19th Space Defense Squadron. However the conjunction screening process in use by the 19th was developed over 30 years ago and was not designed with automation in mind, so screenings are performed once every 8 hours, meaning that spacecraft using automated maneuvering need to allow 16 hours to share their maneuver plan via the screening process. Many operators assume that automated maneuver planning must be real-time; however this time between planning and execution to allow for screening is possible if planned for during system design. In an effort to speed up the screening process, NASA has developed a prototype system for performing near-real-time screenings. This prototype system was necessitated to support the NASA Starling mission, a constellation of 4 cubesats that planned to fly at the same altitude as the SpaceX Starlink constellation, both performing automated maneuvering. Without screening of the planned maneuvers, the two constellations risked a collision. Once converted from a prototype to an operational system, this capability will greatly help smallsats, for example those that are planning to test propulsive capabilities, by allowing fast turnaround feedback to ensure safety form collision with other objects. This paper describes the existing CA process, the prototype real-time capability, and results from the experiment that tested the prototype.

Matthew Hejduk↗
NASA NTRSDate not supplied

Decision Support Tool for Risk Assessment & Maneuver Planning in Collision Avoidance

As the quantity of orbital debris continues to grow, so too does the rate of conjunction messages that suggest possible collisions between high value payloads and debris. The abundance of these conjunction messages, and eventual misses, has led to a culture of ignored alerts, and an increase in satellite operation costs as a result of the frequent need to plan resources for maneuver planning and execution. The loss of “trust” in conjunction alerts is due to the poorly characterized evolution in probability of collision (Pc) as time approaches the time of closest approach (TCA) between two objects, as well as the interpretation of Pc in the context of maneuver planning. To address these problems, and in collaboration with the NASA Conjunction Assessment Risk Analysis (CARA) program, the Industrial Sciences Group has developed a novel Maneuver Decision Support System (MDSS) to assist satellite operations in conjunction assessment and Maneuver planning. It provides a meaningful and intuitive Urgency metric for actionable maneuver decisions, based on the physical dynamics of conjunctions. It is based on a forecast of the evolution of Pc over time and represents an advance over current methods that are in use for satellite conjunction monitoring and planning. The result is to give satellite operators a validated decision support systems to plan for maneuver execution or mitigation or monitoring up to 3 days before TCA.

Decision Support Tool↗
NASA NTRS2008

ATHLETE's Feet: Mu1ti-Resolution Planning for a Hexapod Robot

ATHLETE is a large six-legged tele-operated robot. Each foot is a wheel; travel can be achieved by walking, rolling, or some combination of the two. Operators control ATHLETE by selecting parameterized commands from a command dictionary. While rolling can be done efficiently with a single command, any motion involving steps is cumbersome - walking a few meters through difficult terrain can take hours. Our goal is to improve operator efficiency by automatically generating sequences of motion commands. There is increasing uncertainty regarding ATHLETE s actual configuration over time and decreasing quality of terrain data farther away from the current position. This, combined with the complexity that results from 36 degrees of kinematic freedom, led to an architecture that interleaves planning and execution at multiple levels, ranging from traditional configuration space motion planning algorithms for immediate moves to higher level task and path planning algorithms for overall travel. The modularity of the architecture also simplifies the development process and allows the operator to interact with and control the system at varying levels of autonomy depending on terrain and need.

Smith, Tristan B.↗
NASA NTRS2006

Integrated System for Autonomous Science

The New Millennium Program Space Technology 6 Project Autonomous Sciencecraft software implements an integrated system for autonomous planning and execution of scientific, engineering, and spacecraft-coordination actions. A prior version of this software was reported in "The TechSat 21 Autonomous Sciencecraft Experiment" (NPO-30784), NASA Tech Briefs, Vol. 28, No. 3 (March 2004), page 33. This software is now in continuous use aboard the Earth Orbiter 1 (EO-1) spacecraft mission and is being adapted for use in the Mars Odyssey and Mars Exploration Rovers missions. This software enables EO-1 to detect and respond to such events of scientific interest as volcanic activity, flooding, and freezing and thawing of water. It uses classification algorithms to analyze imagery onboard to detect changes, including events of scientific interest. Detection of such events triggers acquisition of follow-up imagery. The mission-planning component of the software develops a response plan that accounts for visibility of targets and operational constraints. The plan is then executed under control by a task-execution component of the software that is capable of responding to anomalies.

Chien, Steve↗
NASA NTRS2005

Distributed network scheduling

We investigate missions where communications resources are limited, requiring autonomous planning and execution. Unlike typical networks, spacecraft networks are also suited to automated planning and scheduling because many communications can be planned in advance.

scheduling↗
NASA NTRS2020

Event-Driven Modeling and Execution of Robotic Activities and Contingencies in the Europa Lander Mission Concept Using BPMN

TRACE (Traceable Robotic Activity Composer and Executive) is a tool designed to address the model-ing, verification, and execution of planned and con-tingent activities during robotic space missions. These activities can be modeled (i.e., planned) graph-ically in TRACE using the Business Process Model and Notation (BPMN) language. This standardized language is used to model a sequence of robotic ac-tivities tied together by logical constructs, events, and time. TRACE includes verification tools to en-sure feasibility before mission models are executed by TRACE’s executive, which is integrated into the autonomy subsystem via a connector. In this paper, we describe TRACE in detail as it would apply to a conceptual Europa Lander surface mission with planned excavation and sample collection activities, as well as, contingency activities when execution is off-nominal—all highlighting our novel use of BPMN as a lingua franca for the pipeline from mis-sion planning to autonomous execution.

Lim, Grace↗