Search NASA⌕ Search

SEARCH · Search NASA

Results for “plans”

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 145 records · Page 8

Impact of the 1985 Space World Administrative Radio Conference on frequency/orbit planning and use

The 1985 World Administrative Radio Conference (WARC-ORB-85) was held to determine which space radio services should be planned and which planning methods should be used. The second session of this Conference (WARC-ORB-88) will meet to develop the required plans. This paper presents the results of WARC-ORB-85, assesses the impact of those decisions, and identifies the intersessional work to be conducted by administrations and the CCIR (Consultative Committee on International Radio). The major decisions of WARC-ORB-85 were: (1) the restriction of additional planning to the fixed satellite service at identified frequencies; and (2) the selection of a planning method consisting of two parts (a) an allotment plan, and (b) improved procedures. The paper also discusses WARC-ORB-85 decisions relative to the Region 2 broadcast satellite service plans at 12 GHz, feederlink planning for Regions 1 and 3 broadcast satellites at 12 GHz, and sound broadcast satellite service.

Miller, E. F.↗

Impact of the 1985 space World Administrative Radio Conference on frequency/orbit planning and use

The 1985 World Administrative Radio Conference (WARC-ORB-85) was held to determine which space radio services should be planned and which planning methods should be used. The second session of this Conference (WARC-ORB-88) will meet to develop the required plans. This paper presents the results of WARC-ORB-85, assesses the impact of those decisions, and identifies the intersessional work to be conducted by administrations and the CCIR (consultative Committee on International Radio). The major decisions of WARC-ORB-85 were: (1) the restriction of additional planning to the fixed satellite service at identified frequencies; and (2) the selection of a planning method consisting of two parts: (a) an allotment plan, and (b) improved procedures. The paper also discusses WARC-ORB-85 decisions relative to the Region 2 broadcast satellite service plans at 12 GHz, feederlink planning for Regions 1 and 3 broadcast satellites at 12 GHz, and sound broadcast satellite service.

Miller, E. F.↗

Space Station Mission Planning System (MPS) development study. Volume 1: Executive summary

The basic objective of the Space Station (SS) Mission Planning System (MPS) Development Study was to define a baseline Space Station mission plan and the associated hardware and software requirements for the system. A detailed definition of the Spacelab (SL) payload mission planning process and SL Mission Integration Planning System (MIPS) software was derived. A baseline concept was developed for performing SS manned base payload mission planning, and it was consistent with current Space Station design/operations concepts and philosophies. The SS MPS software requirements were defined. Also, requirements for new software include candidate programs for the application of artificial intelligence techniques to capture and make more effective use of mission planning expertise. A SS MPS Software Development Plan was developed which phases efforts for the development software to implement the SS mission planning concept.

Klus, W. J.↗

Mission planning for autonomous systems

Planning is a necessary task for intelligent, adaptive systems operating independently of human controllers. A mission planning system that performs task planning by decomposing a high-level mission objective into subtasks and synthesizing a plan for those tasks at varying levels of abstraction is discussed. Researchers use a blackboard architecture to partition the search space and direct the focus of attention of the planner. Using advanced planning techniques, they can control plan synthesis for the complex planning tasks involved in mission planning.

Pearson, G.↗

Space Station Freedom operations planning

The Space Station Freedom program is developing an operations planning structure which assigns responsibility for planning activities to three tiers of management. The strategic level develops the policy, goals and requirements for the program over a five-year horizon. Planning at the tactical level emphasizes program integration and planning for a two-year horizon. The tactical planning process, architecture, and products have been documented and discussed with the international partners. Tactical planning includes the assignment of user and system hardware as well as significant operational events to a time increment (the period of time from the arrival of one Shuttle to the manned base to the arrival of the next). Execution-level planning emphasizes implementation, and each organization produces detailed plans, by increment, that are specific to its function.

Accola, Anne L.↗

Optimum-AIV: A planning and scheduling system for spacecraft AIV

A project undertaken for the European Space Agency (ESA) is presented. The project is developing a knowledge based software system for planning and scheduling of activities for spacecraft assembly, integration, and verification (AIV). The system extends into the monitoring of plan execution and the plan repair phase. The objectives are to develop an operational kernel of a planning, scheduling, and plan repair tool, called OPTIMUM-AIV, and to provide facilities which will allow individual projects to customize the kernel to suit its specific needs. The kernel shall consist of a set of software functionalities for assistance in initial specification of the AIV plan, in verification and generation of valid plans and schedules for the AIV activities, and in interactive monitoring and execution problem recovery for the detailed AIV plans. Embedded in OPTIMUM-AIV are external interfaces which allow integration with alternative scheduling systems and project databases. The current status of the OPTIMUM-AIV project, as of Jan. 1991, is that a further analysis of the AIV domain has taken place through interviews with satellite AIV experts, a software requirement document (SRD) for the full operational tool was approved, and an architectural design document (ADD) for the kernel excluding external interfaces is ready for review.

Arentoft, M. M.↗

A planning language for activity scheduling

Mission planning and scheduling of spacecraft operations are becoming more complex at NASA. Described here are a mission planning process; a robust, flexible planning language for spacecraft and payload operations; and a software scheduling system that generates schedules based on planning language inputs. The mission planning process often involves many people and organizations. Consequently, a planning language is needed to facilitate communication, to provide a standard interface, and to represent flexible requirements. The software scheduling system interprets the planning language and uses the resource, time duration, constraint, and alternative plan flexibilities to resolve scheduling conflicts.

Zoch, David R.↗

Strategic plan, 1991: A strategy for leadership in space through excellence in space science and applications

In 1988, the Office of Space Science and Applications (OSSA) developed and published a Strategic Plan for the United States' space science and applications program during the next 5 to 10 years. The Plan presented the proposed OSSA program for the next fiscal year and defined a flexible process that provides the basis for near-term decisions on the allocation of resources and the planning of future efforts. Based on the strategies that have been developed by the advisory committees both of the National Academy of Sciences and of NASA, the Plan balances major, moderate, and small mission initiatives, the utilization of Space Station Freedom, and the requirements for a vital research base. The Plan can be adjusted to accommodate varying budget levels, both those levels that provide opportunities for an expanded science and applications program, and those that constrain growth. SSA's strategic planning is constructed around five actions: establish a set of programmatic themes; establish a set of decision rules; establish a set of priorities for missions and programs within each theme; demonstrate that the strategy can yield a viable program; and check the strategy for consistency with resource constraints. The outcome of this process is a clear, coherent strategy that meets both NASA's and OSSA's goals, that assures realism in long-range planning and advanced technology development, and that provides sufficient resiliency to respond and adapt to both known and unexpected internal and external realities. The OSSA Strategic Plan is revised annually to reflect the approval of new programs, improved understanding of requirements and issues, and any major changes in the circumstances, both within NASA and external to NASA, in which OSSA initiatives are considered.

Source record↗

CRI planning and scheduling for space

Computer Resources International (CRI) has many years of experience in developing space planning and scheduling systems for the European Space Agency. Activities range from AIT/AIV planning over mission planning to research in on-board autonomy using advanced planning and scheduling technologies in conjunction with model based diagnostics. This article presents four projects carried out for ESA by CRI with various subcontractors: (1) DI, Distributed Intelligence for Ground/Space Systems is an on-going research project; (2) GMPT, Generic Mission Planning Toolset, a feasibility study concluded in 1993; (3) OPTIMUM-AIV, Open Planning Tool for AIV, development of a knowledge based AIV planning and scheduling tool ended in 1992; and (4) PlanERS-1, development of an AI and knowledge-based mission planning prototype for the ERS-1 earth observation spacecraft ended in 1991.

Aarup, Mads↗

Architecture for Payload Planning System (PPS) Software Distribution

The complex and diverse nature of the pay load operations to be performed on the Space Station requires a robust and flexible planning approach, and the proper software tools which tools to support that approach. To date, the planning software for most manned operations in space has been utilized in a centralized planning environment. Centralized planning is characterized by the following: performed by a small team of people, performed at a single location, and performed using single-user planning systems. This approach, while valid for short duration flights, is not conducive to the long duration and highly distributed payload operations environment of the Space Station. The Payload Planning System (PPS) is being designed specifically to support the planning needs of the large number of geographically distributed users of the Space Station. This paper problem provides a general description of the distributed planning architecture that PPS must support and describes the concepts proposed for making PPS available to the Space Station payload user community.

Howell, Eric↗

Mission to Planet Earth Strategic Enterprise Plan 1996-2002

Mission to Planet Earth's (MTPE's) first Strategic Enterprise Plan, issued in May 1995, defined the Agency's major goals and objectives as well as constraints. This update of the Strategic Enterprise Plan identifies the following major changes: a focused Science Research Plan that integrates space-based and in situ observational critical science to address critical science uncertainties; a technology infusion plan to reduce the cost of future missions; a series of flight opportunities to infuse new science into the overall program; and a tighter coupling between NASA and NOAA to reduce costs and to improve the overall program. Three important new initiatives are also under development and are described briefly in this plan: MTPE Education Strategy, MTPE Commercial Strategy, and an emerging concept for an Integrated Global Observing Strategy. This first update to the MTPE Strategic Enterprise Plan captures these new developments, and takes a significant step forward in planning this complex Earth system science endeavor. The plan and other information on MTPE may be viewed via the Internet at http://www.hq.nasa.gov/office/mtpe/.

Source record↗

Runway Operations Planning: A Two-Stage Solution Methodology

The airport runway is a scarce resource that must be shared by different runway operations (arrivals, departures and runway crossings). Given the possible sequences of runway events, careful Runway Operations Planning (ROP) is required if runway utilization is to be maximized. Thus, Runway Operations Planning (ROP) is a critical component of airport operations planning in general and surface operations planning in particular. From the perspective of departures, ROP solutions are aircraft departure schedules developed by optimally allocating runway time for departures given the time required for arrivals and crossings. In addition to the obvious objective of maximizing throughput, other objectives, such as guaranteeing fairness and minimizing environmental impact, may be incorporated into the ROP solution subject to constraints introduced by Air Traffic Control (ATC) procedures. Generating optimal runway operations plans was approached in with a 'one-stage' optimization routine that considered all the desired objectives and constraints, and the characteristics of each aircraft (weight class, destination, Air Traffic Control (ATC) constraints) at the same time. Since, however, at any given point in time, there is less uncertainty in the predicted demand for departure resources in terms of weight class than in terms of specific aircraft, the ROP problem can be parsed into two stages. In the context of the Departure Planner (OP) research project, this paper introduces Runway Operations Planning (ROP) as part of the wider Surface Operations Optimization (SOO) and describes a proposed 'two stage' heuristic algorithm for solving the Runway Operations Planning (ROP) problem. Focus is specifically given on including runway crossings in the planning process of runway operations. In the first stage, sequences of departure class slots and runwy crossings slots are generated and ranked based on departure runway throughput under stochastic conditions. In the second stage, the departure class slots are populated with specific flights from the pool of available aircraft, by solving an integer program. Preliminary results from the algorithm implementation on real-world traffic data are included.

Anagnostakis, Ioannis↗

Scoping Planning Agents With Shared Models

In this paper we provide a formal framework to define the scope of planning agents based on a single declarative model. Having multiple agents sharing a single model provides numerous advantages that lead to reduced development costs and increase reliability of the system. We formally define planning in terms of extensions of an initial partial plan, and a set of flaws that make the plan unacceptable. A Flaw Filter (FF) allows us to identify those flaws relevant to an agent. Flaw filters motivate the Plan Identification Function (PIF), which specifies when an agent is is ready hand control to another agent for further work. PIFs define a set of plan extensions that can be generated from a model and a plan request. FFs and PIFs can be used to define the scope of agents without changing the model. We describe an implementation of PIFsand FFswithin the context of EUROPA, a constraint-based planning architecture, and show how it can be used to easily design many different agents.

Bedrax-Weiss, Tania↗

Planning of reach-and-grasp movements: effects of validity and type of object information

Individuals are assumed to plan reach-and-grasp movements by using two separate processes. In 1 of the processes, extrinsic (direction, distance) object information is used in planning the movement of the arm that transports the hand to the target location (transport planning); whereas in the other, intrinsic (shape) object information is used in planning the preshaping of the hand and the grasping of the target object (manipulation planning). In 2 experiments, the authors used primes to provide information to participants (N = 5, Experiment 1; N = 6, Experiment 2) about extrinsic and intrinsic object properties. The validity of the prime information was systematically varied. The primes were succeeded by a cue, which always correctly identified the location and shape of the target object. Reaction times were recorded. Four models of transport and manipulation planning were tested. The only model that was consistent with the data was 1 in which arm transport and object manipulation planning were postulated to be independent processes that operate partially in parallel. The authors suggest that the processes involved in motor planning before execution are primarily concerned with the geometric aspects of the upcoming movement but not with the temporal details of its execution.

Cues↗

PlanWorks: A Debugging Environment for Constraint Based Planning Systems

Numerous planning and scheduling systems employ underlying constraint reasoning systems. Debugging such systems involves the search for errors in model rules, constraint reasoning algorithms, search heuristics, and the problem instance (initial state and goals). In order to effectively find such problems, users must see why each state or action is in a plan by tracking causal chains back to part of the initial problem instance. They must be able to visualize complex relationships among many different entities and distinguish between those entities easily. For example, a variable can be in the scope of several constraints, as well as part of a state or activity in a plan; the activity can arise as a consequence of another activity and a model rule. Finally, they must be able to track each logical inference made during planning. We have developed PlanWorks, a comprehensive system for debugging constraint-based planning and scheduling systems. PlanWorks assumes a strong transaction model of the entire planning process, including adding and removing parts of the constraint network, variable assignment, and constraint propagation. A planner logs all transactions to a relational database that is tailored to support queries for of specialized views to display different forms of data (e.g. constraints, activities, resources, and causal links). PlanWorks was specifically developed for the Extensible Universal Remote Operations Planning Architecture (EUROPA(sub 2)) developed at NASA, but the underlying principles behind PlanWorks make it useful for many constraint-based planning systems. The paper is organized as follows. We first describe some fundamentals of EUROPA(sub 2). We then describe PlanWorks' principal components. We then discuss each component in detail, and then describe inter-component navigation features. We close with a discussion of how PlanWorks is used to find model flaws.

Daley, Patrick↗

Flight Planning Branch Space Shuttle Lessons Learned

Planning products and procedures that allow the mission flight control teams and the astronaut crews to plan, train and fly every Space Shuttle mission have been developed by the Flight Planning Branch at the NASA Johnson Space Center. As the Space Shuttle Program ends, lessons learned have been collected from each phase of the successful execution of these Shuttle missions. Specific examples of how roles and responsibilities of console positions that develop the crew and vehicle attitude timelines will be discussed, as well as techniques and methods used to solve complex spacecraft and instrument orientation problems. Additionally, the relationships and procedural hurdles experienced through international collaboration have molded operations. These facets will be explored and related to current and future operations with the International Space Station and future vehicles. Along with these important aspects, the evolution of technology and continual improvement of data transfer tools between the shuttle and ground team has also defined specific lessons used in the improving the control teams effectiveness. Methodologies to communicate and transmit messages, images, and files from Mission Control to the Orbiter evolved over several years. These lessons have been vital in shaping the effectiveness of safe and successful mission planning that have been applied to current mission planning work in addition to being incorporated into future space flight planning. The critical lessons from all aspects of previous plan, train, and fly phases of shuttle flight missions are not only documented in this paper, but are also discussed as how they pertain to changes in process and consideration for future space flight planning.

Price, Jennifer B.↗

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 Flight Planning Branch Space Shuttle Lessons Learned

Planning products and procedures that allowed the mission Flight Control Teams and the Astronaut crews to plan, train and fly every Space Shuttle mission were developed by the Flight Planning Branch at the NASA Johnson Space Center in Houston, Texas. As the Space Shuttle Program came to a close, lessons learned were collected from each phase of the successful execution of these Space Shuttle missions. Specific examples of how roles and responsibilities of console positions that develop the crew and vehicle attitude timelines have been analyzed and will be discussed. Additionally, the relationships and procedural hurdles experienced through international collaboration have molded operations. These facets will be explored and related to current and future operations with the International Space Station and future vehicles. Along with these important aspects, the evolution of technology and continual improvement of data transfer tools between the Space Shuttle and ground team has also defined specific lessons used in improving the control team s effectiveness. Methodologies to communicate and transmit messages, images, and files from the Mission Control Center to the Orbiter evolved over several years. These lessons were vital in shaping the effectiveness of safe and successful mission planning and have been applied to current mission planning work in addition to being incorporated into future space flight planning. The critical lessons from all aspects of previous plan, train, and fly phases of Space Shuttle flight missions are not only documented in this paper, but are also discussed regarding how they pertain to changes in process and consideration for future space flight planning.

Clevenger, Jennifer D.↗