Lunar orbital mission plans.
Lunar orbital mission plans intended to optimize spacecraft procurement, flight schedules, science objectives and available funds
SEARCH · Engineering Papers
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.
Lunar orbital mission plans intended to optimize spacecraft procurement, flight schedules, science objectives and available funds
Mission planning for a series of atmospheric probe missions to Saturn and Uranus using a modified Pioneer spacecraft launched in 1979 and 1980 was examined. The operational options and the associated systems requirements consistent with the major scientific goals and spacecraft constraints of the missions is summarized. It is feasible to obtain in-situ atmospheric measurements in the atmosphere of Saturn and Uranus down to a pressure level of 10 bars using a common probe and spacecraft design. Spacecraft can be launched to both objectives with an adequate launch window in 1979 and 1980 using a Titan/Centaur launch vehicle with a TE-364-4 upper stage. Other scientific objectives can be accomplished by the flyby spacecraft. Encounters with the satellite Titan and RF occultations of Saturn, the ring system of Saturn, and Uranus can be obtained.
An architecture for the control of an autonomous aircraft is presented. The architecture is a hierarchical system representing an anthropomorphic breakdown of the control problem into planner, navigator, and pilot systems. The planner system determines high level global plans from overall mission objectives. This abstract mission planning is investigated by focusing on the Traveling Salesman Problem with variations on local and global constraints. Tree search techniques are applied including the breadth first, depth first, and best first algorithms. The minimum-column and row entries for the Traveling Salesman Problem cost matrix provides a powerful heuristic to guide these search techniques. Mission planning subgoals are directed from the planner to the navigator for planning routes in mountainous terrain with threats. Terrain/threat information is abstracted into a graph of possible paths for which graph searches are performed. It is shown that paths can be well represented by a search graph based on the Voronoi diagram of points representing the vertices of mountain boundaries. A comparison of Dijkstra's dynamic programming algorithm and the A* graph search algorithm from artificial intelligence/operations research is performed for several navigation path planning examples. These examples illustrate paths that minimize a combination of distance and exposure to threats. Finally, the pilot system synthesizes the flight trajectory by creating the control commands to fly the aircraft.
As NASA looks toward longer duration missions, there will inevitably be a stronger emphasis on crew autonomy, particularly in the domains of mission planning. Ensuring that astronauts, while subject to lengthy periods of communication delay with Earth-based mission support personnel, are able to independently adapt their schedules to rapidly changing environments is a critical aspect of deep-space exploration. This task will likely require the assistance of computer support systems, as the task of mission planning is complex and currently requires dedicated console operators. A mixed-initiative approach can help alleviate some of the more workload-heavy aspects of planning by offloading the intricate task of constraint management to a computer, while still allowing the crew member to maintain overall control of the plan. Playbook is a mission planning tool that has been developed specifically to support this type of mixed-initiative scheduling. This paper examines: 1) the operational evidence of the challenges and viability of autonomous crew planning, and 2) the novel scheduling capabilities in Playbook that are meant to address those findings.
Mission concepts and technology advancements that can be used in the exploration of the outer planet satellites were examined. Titan, the seventh satellite of Saturn was selected as the target of interest. Science objectives for Titan exploration were identified, and recommended science payloads for four basic mission modes were developed (orbiter, atmospheric probe, surface penetrator and lander). Trial spacecraft and mission designs were produced for the various mission modes. Using these trial designs as a base, technology excursions were then made to find solutions to the problems resulting from these conventional approaches and to uncover new science, technology and mission planning options. Several mission modes were developed that take advantage of the unique conditions expected at Titan. They include a combined orbiter, atmosphere probe and lander vehicle, a combined probe and surface penetrator configuration and concepts for advanced remote sensing orbiters.
Plan Specification Tools (PST) are tools that allow the user to specify satellite mission plans in terms of satellite activities, relevent orbital events, and targets for observation. The output of these tools is a set of knowledge bases and environmental events which can then be used by a Planning And Resource Reasoning (PARR) shell to build a schedule. PARR is a reactive planning shell which is capable of reasoning about actions in the satellite mission planning domain. Each of the PST tools and PARR are described as well as the use of PARR for scheduling computer usage in the multisatellite operations control center at Goddard Space Flight Center.
The mission planning processor is a user oriented tool for consumables management and is part of the total consumables subsystem management concept. The approach to be used in developing a working model of the mission planning processor is documented. The approach includes top-down design, structured programming techniques, and application of NASA approved software development standards. This development approach: (1) promotes cost effective software development, (2) enhances the quality and reliability of the working model, (3) encourages the sharing of the working model through a standard approach, and (4) promotes portability of the working model to other computer systems.
An operational approach to shuttle mission planning during high flight frequency years (20 or more flights per year) is described wherein diverse mission planning functions interface via an interactive computer system and common data base. The Vehicle Management and Mission Planning System (VMMPS) is proposed as a means of helping to accomplish the mission planning function. The VMMPS will link together into an interactive system the major mission planning areas such as trajectory, crew, vehicle performance, and launch operations. A common data base will be an integral part of the system and the concept of standard mission types and phases will be used to minimize mission to mission uniqueness. The use of this system will eliminate much redundancy and replanning, shorten interface times between functions, and provide a means to evaluate unplanned events and modify schedules.
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.
The Cassini F-Ring & Proximal Orbits (FRPO) is a new and unique mission; to ensure the highest priority science gets implemented, the POST (Proximal Orbit Science Team) was created to pre-allocate the time around periapse for all 22 proximal orbits. The F-ring orbits, and proximal time outside of POST, were handled similar to Cassini’s Solstice Mission using the Pre-Integrated Event (PIE) process. The new and unique properties of the spacecraft’s trajectory required much forethought to be flown safely while still planning for the most and best science return possible. Some ring-plane crossings (RPX) will be protected against dust impacts by turning the high gain antenna (HGA) to the dust RAM direction (HGA2RAM). If on the first proximal RPX higher than expected dust readings are seen then the Project Office may choose to require more (all) subsequent RPX to be HGA2RAM, implemented via a real-time command overlay for uplinked sequences. The pointing uncertainties will be larger than usual after the final targeted flyby; some of the process changes to address this include adding extra orbit trim maneuvers (OTMs) (fuel permitting) to resync to the reference trajectory and reduce pointing uncertainties; and movable blocks of commands to be used for some periapses where atmospheric drag may cause large timing shifts Changes made for FRPO to address perceptions that these sequences will be hard to implement include requiring early pointing designs (during integration) for certain types of observations, requiring teams to check early on that they can turn to and from their observation attitude, and that their attitude is safe, and adjusting the Implementation process to give more time for science observation designers. This paper will discuss these process changes and lessons learned so far.
The scheduling algorithm for mission planning and logistics evaluation (SAMPLE) is presented. Two major subsystems are included: The mission payloads program; and the set covering program. Formats and parameter definitions for the payload data set (payload model), feasible combination file, and traffic model are documented.
SPIKE is a mission planning software system developed by a team of programmers at the STScI for use with the Hubble Space Telescope (HST). SPIKE has been developed for the purpose of automating observatory scheduling to increase the effective utilization and ultimately, scientific return from orbiting telescopes. High-level scheduling strategies using both rule-based and neural network approaches have been incorporated. Graphical displays of activities, constraints, and schedules are an important feature of the system. Although SPIKE was originally developed for the HST, it can be used for other astronomy missions including ground-based observatories. One of the missions that has decided to use SPIKE is ASTRO-D, a Japanese X-ray satellite for which the U.S. is providing a part of the scientific payload. Scheduled to fly in Feb. 1993, its four telescopes will focus X-rays over a wide energy range onto CCD's and imaging gas proportional counters. ASTRO-D will be the first X-ray imaging mission operating over the 0.5-12 keV band with high energy resolution. This combination of capabilities will enable a varied and exciting program of astronomical research to be carried out. ASTRO-D is expected to observe 5 to 20 objects per day and a total of several thousands per year. This requires the implementation of an efficient planning and scheduling system which SPIKE can provide. Although the version of SPIKE that will be used for ASTRO-D mission is almost identical to that used for the HST, there are a few differences. For example, ASTRO-D will use two ground stations for data downlinks, instead of the TDRSS system for data transmission. As a consequence ASTRO-D is constrained by limited on-board data storage capacity to schedule high data-rate observations during periods of frequent high bit rate observations accordingly. We will demonstrate the ASTRO-D version of SPIKE to show what SPIKE can provide and how efficiently it creates an observational schedule.
Mission planning for manned, circular, synchronous orbit missions
During SpaceOps 92 the idea of generic mission planning concepts for space astronomy missions, that could be applied to future missions in order to simplify software development, was introduced. It was proposed that mission planning systems could be decomposed into functional elements that could be standardized and then organized into optimal functional flows for each individual mission. In addition, it was further suggested that these flows themselves could be reduced to a small set of possibilities by describing them in terms of generic mission type, such as manned, unmanned, high orbit, low orbit, etc. The Advanced X-ray Astrophysics Facility (AXAF), planned for launch in the latter part of '98, represents the first application of this idea on an unmanned mission. This paper examines the AXAF Mission Planning and Scheduling concept in light of the generic system theory. Each functional element is evaluated according to AXAF characteristics and requirements and then compared to its generic counterpart. Functional flow considerations are then derived from the overall AXAF mission planning concept to determine the viability and sensitivity of the generic flow to actual requirements. The results of this analysis are then used to update the generic system concept and to define the level of commonality and core system components that are practical to achieve across multiple missions.
During SpaceOps 92 the idea of generic mission planning concepts for space astronomy missions, that could be applied to future missions in order to simplify software development, was introduced. It was proposed that mission planning systems could be decomposed into functional elements that could be standardized and then organized into optimal functional flows for each individual mission. In addition, it was further suggested that these flows themselves could be reduced to a small set of possibilities by describing them in terms of generic mission type, such as manned, unmanned, high orbit, low orbit, etc. The Advanced X-ray Astrophysics Facility (AXAF), planned for launch in the latter part of 1998, represents the first application of this idea on an unmanned mission. This paper examines the AXAF Mission Planning and Scheduling concept in light of the generic system theory. Each functional element is evaluated according to AXAF characteristics and requirements and then compared to its generic counterpart. Functional flow considerations are then derived from the overall AXAF mission planning concept to determine the viability and sensitivity of the generic flow to actual requirements. The results of this analysis are then used to update the generic system concept and to define the level of commonality and core system components that are practical to achieve across multiple missions.
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.