Advanced Automation for Space Missions
The feasibility of using machine intelligence, including automation and robotics, in future space missions was studied.
Freitas, R. A., Jr.↗
SEARCH · Engineering Papers
Results for “mission automation”
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.
CEO Sites Mission Management System (SMMS)
Late in fiscal year 2011, the Crew Earth Observations (CEO) team was tasked to upgrade its science site database management tool, which at the time was integrated with the Automated Mission Planning System (AMPS) originally developed for Earth Observations mission planning in the 1980s. Although AMPS had been adapted and was reliably used by CEO for International Space Station (ISS) payload operations support, the database structure was dated, and the compiler required for modifications would not be supported in the Windows 7 64-bit operating system scheduled for implementation the following year. The Sites Mission Management System (SMMS) is now the tool used by CEO to manage a heritage Structured Query Language (SQL) database of more than 2,000 records for Earth science sites. SMMS is a carefully designed and crafted in-house software package with complete and detailed help files available for the user and meticulous internal documentation for future modifications. It was delivered in February 2012 for test and evaluation. Following acceptance, it was implemented for CEO mission operations support in April 2012. The database spans the period from the earliest systematic requests for astronaut photography during the shuttle era to current ISS mission support of the CEO science payload. Besides logging basic image information (site names, locations, broad application categories, and mission requests), the upgraded database management tool now tracks dates of creation, modification, and activation; imagery acquired in response to requests; the status and location of ancillary site information; and affiliations with studies, their sponsors, and collaborators. SMMS was designed to facilitate overall mission planning in terms of site selection and activation and provide the necessary site parameters for the Satellite Tool Kit (STK) Integrated Message Production List Editor (SIMPLE), which is used by CEO operations to perform daily ISS mission planning. The CEO team uses the SMMS for three general functions - database queries of content and status, individual site creation and updates, and mission planning. The CEO administrator of the science site database is able to create or modify the content of sites and activate or deactivate them based on the requirements of the sponsors. The administrator supports and implements ISS mission planning by assembling, reporting, and activating mission-specific site selections for management; deactivating sites as requirements are met; and creating new sites, such as International Charter sites for disasters, as circumstances warrant. In addition to the above CEO internal uses, when site planning for a specific ISS mission is complete and approved, the SMMS can produce and export those essential site database elements for the mission into XML format for use by onboard Earth-location systems, such as Worldmap. The design, development, and implementation of the SMMS resulted in a superior database management system for CEO science sites by focusing on the functions and applications of the database alone instead of integrating the database with the multipurpose configuration of the AMPS. Unlike the AMPS, it can function and be modified within the existing Windows 7 environment. The functions and applications of the SMMS were expanded to accommodate more database elements, report products, and a streamlined interface for data entry and review. A particularly elegant enhancement in data entry was the integration of the Google Earth application for the visual display and definition of site coordinates for site areas defined by multiple coordinates. Transfer between the SMMS and Google Earth is accomplished with a Keyhole Markup Language (KML) expression of geographic data (see figures 3 and 4). Site coordinates may be entered into the SMMS panel directly for display in Google Earth, or the coordinates may be defined on the Google Earth display as a mouse-controlled polygonal definition and transferred back into the SMMS as KML input. This significantly reduces the possibility of errors in coordinate entries and provides visualization of the scale of the site being defined. CEO now has a powerful tool for managing and defining sites on the Earth's surface for both targets of astronaut photography or other onboard remote sensing systems. It can also record and track results by sponsor, collaborator, or type of study.
Trenchard, Mike↗
The last grand tour opportunity to Pluto
An automated mission design program permits a thorough examination of gravity-assist trajectories such as the Voyager II flight to Jupiter, Saturn, Uranus and Neptune. The program is applied to the automated design of multiple encounter trajectories to the far outer planets. The most significant result is that the last four-planet grand tour opportunity occurs in 1996 and includes encounters with Jupiter, Uranus, Neptune and Pluto. Other mission designs include Jupiter and one or two other planets and have characteristically short flight times.
Longuski, J. M.↗
Deep-Space Conjunction Assessment: Recent Developments and Future Evolution
The Multi-mission Automated Deep-space Conjunction Assessment Process (MADCAP) is a NASA Jet Propulsion Laboratory (JPL) capability used to perform conjunction assessment in shared deep-space environments. MADCAP began performing conjunction assessment at Mars and the Moon in 2011, with the Sun/Earth libration points added to its functionality in 2020. There has been an increasing number of missions operating in these environments in recent years, leading to an elevated frequency of close conjunction events, especially in the Lunar orbital environment. MADCAP provides this service not only to NASA missions, but to any operator who is willing to share ephemerides. Since there is no space surveillance network for deep space environments, ephemeris sharing is the only way in which spacecraft operators can ensure the safety of their spacecraft from collision in these orbit regimes. NASA published a set of conjunction assessment best practices in 2020 that cover the MADCAP process. This paper details recent MADCAP operational experience in the deep space environments, including statistics and process improvements. Updates to the MADCAP software and automation framework implemented to handle the recent growth in the number of deep space missions are also discussed. Future enhancements planned in anticipation of increasingly crowded deep-space environments, such as non-standard runs based on exploratory scenarios, are also discussed.
conjunction assessment↗
Computational needs survey of NASA automation and robotics missions. Volume 1: Survey and results
NASA's operational use of advanced processor technology in space systems lags behind its commercial development by more than eight years. One of the factors contributing to this is that mission computing requirements are frequently unknown, unstated, misrepresented, or simply not available in a timely manner. NASA must provide clear common requirements to make better use of available technology, to cut development lead time on deployable architectures, and to increase the utilization of new technology. A preliminary set of advanced mission computational processing requirements of automation and robotics (A&R) systems are provided for use by NASA, industry, and academic communities. These results were obtained in an assessment of the computational needs of current projects throughout NASA. The high percent of responses indicated a general need for enhanced computational capabilities beyond the currently available 80386 and 68020 processor technology. Because of the need for faster processors and more memory, 90 percent of the polled automation projects have reduced or will reduce the scope of their implementation capabilities. The requirements are presented with respect to their targeted environment, identifying the applications required, system performance levels necessary to support them, and the degree to which they are met with typical programmatic constraints. Volume one includes the survey and results. Volume two contains the appendixes.
Davis, Gloria J.↗
Computational needs survey of NASA automation and robotics missions. Volume 2: Appendixes
NASA's operational use of advanced processor technology in space systems lags behind its commercial development by more than eight years. One of the factors contributing to this is the fact that mission computing requirements are frequency unknown, unstated, misrepresented, or simply not available in a timely manner. NASA must provide clear common requirements to make better use of available technology, to cut development lead time on deployable architectures, and to increase the utilization of new technology. Here, NASA, industry and academic communities are provided with a preliminary set of advanced mission computational processing requirements of automation and robotics (A and R) systems. The results were obtained in an assessment of the computational needs of current projects throughout NASA. The high percent of responses indicated a general need for enhanced computational capabilities beyond the currently available 80386 and 68020 processor technology. Because of the need for faster processors and more memory, 90 percent of the polled automation projects have reduced or will reduce the scope of their implemented capabilities. The requirements are presented with respect to their targeted environment, identifying the applications required, system performance levels necessary to support them, and the degree to which they are met with typical programmatic constraints. Here, appendixes are provided.
Davis, Gloria J.↗
A software architecture for automating operations processes
The Operations Engineering Lab (OEL) at JPL has developed a software architecture based on an integrated toolkit approach for simplifying and automating mission operations tasks. The toolkit approach is based on building adaptable, reusable graphical tools that are integrated through a combination of libraries, scripts, and system-level user interface shells. The graphical interface shells are designed to integrate and visually guide a user through the complex steps in an operations process. They provide a user with an integrated system-level picture of an overall process, defining the required inputs and possible output through interactive on-screen graphics. The OEL has developed the software for building these process-oriented graphical user interface (GUI) shells. The OEL Shell development system (OEL Shell) is an extension of JPL's Widget Creation Library (WCL). The OEL Shell system can be used to easily build user interfaces for running complex processes, applications with extensive command-line interfaces, and tool-integration tasks. The interface shells display a logical process flow using arrows and box graphics. They also allow a user to select which output products are desired and which input sources are needed, eliminating the need to know which program and its associated command-line parameters must be executed in each case. The shells have also proved valuable for use as operations training tools because of the OEL Shell hypertext help environment. The OEL toolkit approach is guided by several principles, including the use of ASCII text file interfaces with a multimission format, Perl scripts for mission-specific adaptation code, and programs that include a simple command-line interface for batch mode processing. Projects can adapt the interface shells by simple changes to the resources configuration file. This approach has allowed the development of sophisticated, automated software systems that are easy, cheap, and fast to build. This paper will discuss our toolkit approach and the OEL Shell interface builder in the context of a real operations process example. The paper will discuss the design and implementation of a Ulysses toolkit for generating the mission sequence of events. The Sequence of Events Generation (SEG) system provides an adaptable multimission toolkit for producing a time-ordered listing and timeline display of spacecraft commands, state changes, and required ground activities.
Miller, Kevin J.↗
Using Automated Scheduling for Mission Design: A Case Study for EMIT
The Earth Surface Mineral Dust Source InvesTigation (EMIT) is an Earth Ventures-Instrument (EVI-4) mission to map the surface mineralogy of arid dust source regions. EMIT used automated scheduling technology to analyze aspects of the mission design. The automated scheduling technology was used to construct schedules which were then automatically analyzed with respect to science acquired. These analyses can be performed for a range of spacecraft hardware configurations, observation strategies, and science requirements. By studying the effects of changes on the above inputs, better hardware configurations, observation strategies, and science requirements can be formulated. The use of a pointing mirror on EMIT was under consideration, and this analysis aided in determining whether or not to keep it as part of the design of the instrument. Clouds will also have a large impact on the coverage of science targets achievable by the mission. Analysis was done on how clouds could impact the coverage achievable as well as the data volume. This analysis with clouds also aided in determining the coverage criteria for the mission. It was necessary to find a criteria that was achievable with some margin as well as satisfies the science goals of the mission.
Thompson, David R.↗
A cursory look at shuttle flight operations.
The purpose of the shuttle system is to permit us to do more useful and necessary things in space at minimum cost. The flight operation subsystem must be consistent with these goals. This review of the predicted payload and mission types reveals a ground facility functionally similar to the Skylab Control Center is needed to provide trajectory control and system management services for the spacecraft and payloads and to provide rapid, effective payload data acquisition and distribution to the user. An automated mission management system must be added to translate user requirements into specific missions, directives, schedules, and plans.
Tindall, H. W., Jr.↗
Future Model-Based Systems Engineering Vision and Strategy Bridge for NASA
A vision for the future of model-based systems engineering (MBSE) at NASA in 2029 and a strategy bridge towards that future are presented. Strategic thinking and leading change concepts were used to analyze reports and presentations on global trends and visionary thinking about the future of systems and digital engineering. The context, strategic time horizon, stakeholders, strategic challenges, strategic advantages, driving forces, and opportunities were considered. The analysis resulted in a future vision of MBSE that shows what NASA systems engineers and digital machines will do to perform rapid, extraordinary, and unprecedented missions. The NASA systems engineer, in this future vision, works with a global project team in a virtual and collaborative environment, engineers the system, and uses digital approaches as the routine and default way of working. The digital machines provide data-driven and automated mission designs; have a backbone of program and project management, systems engineering, and product life-cycle management; and are a knowledge-sharing infrastructure. The NASA systems engineer and the systems engineering team are envisioned to use digital machines to plan and perform rapid exploration missions, develop a digital twin that lasts across the life cycle, and develop enduring and adaptable systems. NASA has an engineering enterprise and a life-cycle management framework that endure, adapt, and respond. A strategy bridge based on the Baldrige Criteria for Performance Excellence Framework and lessons learned from a recent MBSE initiative illuminates a way forward from today to this desired future. The bridge lays out a strategy for leaders and recommends investments of today for immediate benefits and for benefits in 2029.
model-based systems engineering, digital engineeri↗
Automated Mars surface sample return mission/ system concepts
Automated mars surface sample return /AMSSR/ mission, discussing Saturn 5 chemical and nuclear approach
Odom, P. R.↗
Web Design for Space Operations: An Overview of the Challenges and New Technologies Used in Developing and Operating Web-Based Applications in Real-Time Operational Support Onboard the International Space Station, in Astronaut Mission Planning and Mission Control Operations
The International Space Station (ISS) Operations Planning Team, Mission Control Centre and Mission Automation Support Network (MAS) have all evolved over the years to use commercial web-based technologies to create a configurable electronic infrastructure to manage the complex network of real-time planning, crew scheduling, resource and activity management as well as onboard document and procedure management required to co-ordinate ISS assembly, daily operations and mission support. While these Web technologies are classified as non-critical in nature, their use is part of an essential backbone of daily operations on the ISS and allows the crew to operate the ISS as a functioning science laboratory. The rapid evolution of the internet from 1998 (when ISS assembly began) to today, along with the nature of continuous manned operations in space, have presented a unique challenge in terms of software engineering and system development. In addition, the use of a wide array of competing internet technologies (including commercial technologies such as .NET and JAVA ) and the special requirements of having to support this network, both nationally among various control centres for International Partners (IPs), as well as onboard the station itself, have created special challenges for the MCC Web Tools Development Team, software engineers and flight controllers, who implement and maintain this system. This paper presents an overview of some of these operational challenges, and the evolving nature of the solutions and the future use of COTS based rich internet technologies in manned space flight operations. In particular this paper will focus on the use of Microsoft.s .NET API to develop Web-Based Operational tools, the use of XML based service oriented architectures (SOA) that needed to be customized to support Mission operations, the maintenance of a Microsoft IIS web server onboard the ISS, The OpsLan, functional-oriented Web Design with AJAX
Khan, Ahmed↗
Mission Operations Planning and Scheduling System (MOPSS)
MOPSS is a generic framework that can be configured on the fly to support a wide range of planning and scheduling applications. It is currently used to support seven missions at Goddard Space Flight Center (GSFC) in roles that include science planning, mission planning, and real-time control. Prior to MOPSS, each spacecraft project built its own planning and scheduling capability to plan satellite activities and communications and to create the commands to be uplinked to the spacecraft. This approach required creating a data repository for storing planning and scheduling information, building user interfaces to display data, generating needed scheduling algorithms, and implementing customized external interfaces. Complex scheduling problems that involved reacting to multiple variable situations were analyzed manually. Operators then used the results to add commands to the schedule. Each architecture was unique to specific satellite requirements. MOPSS is an expert system that automates mission operations and frees the flight operations team to concentrate on critical activities. It is easily reconfigured by the flight operations team as the mission evolves. The heart of the system is a custom object-oriented data layer mapped onto an Oracle relational database. The combination of these two technologies allows a user or system engineer to capture any type of scheduling or planning data in the system's generic data storage via a GUI.
Wood, Terri↗
Expert systems and advanced automation for space missions operations
Increased complexity of space missions during the 1980s led to the introduction of expert systems and advanced automation techniques in mission operations. This paper describes several technologies in operational use or under development at the National Aeronautics and Space Administration's Goddard Space Flight Center. Several expert systems are described that diagnose faults, analyze spacecraft operations and onboard subsystem performance (in conjunction with neural networks), and perform data quality and data accounting functions. The design of customized user interfaces is discussed, with examples of their application to space missions. Displays, which allow mission operators to see the spacecraft position, orientation, and configuration under a variety of operating conditions, are described. Automated systems for scheduling are discussed, and a testbed that allows tests and demonstrations of the associated architectures, interface protocols, and operations concepts is described. Lessons learned are summarized.
Durrani, Sajjad H.↗
Extremely Low Passive Microwave Brightness Temperatures Due to Thunderstorms
Extreme events by their nature fall outside the bounds of routine experience. With imperfect or ambiguous measuring systems, it is appropriate to question whether an unusual measurement represents an extreme event or is the result of instrument errors or other sources of noise. About three weeks after the Tropical Rainfall Measuring Mission (TRMM) satellite began collecting data in Dec 1997, a thunderstorm was observed over northern Argentina with 85 GHz brightness temperatures below 50 K and 37 GHz brightness temperatures below 70 K (Zipser et al. 2006). These values are well below what had previously been observed from satellite sensors with lower resolution. The 37 GHz brightness temperatures are also well below those measured by TRMM for any other storm in the subsequent 16 years. Without corroborating evidence, it would be natural to suspect a problem with the instrument, or perhaps an irregularity with the platform during the first weeks of the satellite mission. Automated quality control flags or other procedures in retrieval algorithms could treat these measurements as errors, because they fall outside the expected bounds. But the TRMM satellite also carries a radar and a lightning sensor, both confirming the presence of an intense thunderstorm. The radar recorded 40+ dBZ reflectivity up to about 19 km altitude. More than 200 lightning flashes per minute were recorded. That same storm's 19 GHz brightness temperatures below 150 K would normally be interpreted as the result of a low-emissivity water surface (e.g., a lake, or flood waters) if not for the simultaneous measurements of such intense convection. This paper will examine records from TRMM and related satellite sensors including SSMI, AMSR-E, and the new GMI to find the strongest signatures resulting from thunderstorms, and distinguishing those from sources of noise. The lowest brightness temperatures resulting from thunderstorms as seen by TRMM have been in Argentina in November and December. For SSMI sensors carried on five DMSP satellites examined so far, the lowest thunderstorm-related brightness temperatures have been from Argentina in November - December and from Minnesota in June-July. The Minnesota cases were associated with spotter reports of large hail, significant severe wind, and tornadoes. Those locations have the record-holders for each satellite. The lowest AMSR-E 36.5 GHz brightness temperatures associated with deep convection have been in Argentina; the lowest 89.0 GHz brightness temperatures were from Typhoon Bolaven in the Philippine Sea. This paper will show examples of cases with the lowest brightness temperatures, and map the locations of these and other storms with brightness temperatures nearly as low. The study is largely motivated by the new GMI sensor on the Global Precipitation Mission core satellite, launched in February 2014, with its high resolution expected to reveal unprecedented low brightness temperatures when extreme events are encountered.
Cecil, Daniel J.↗
Exploration of the outer planets
Automated mission requirements for outer planets, discussing flyby spacecraft, orbiters, atmospheric entry and grand tour missions
Long, J. E.↗
Evaluation of the MSFC facsimile camera system as a tool for extraterrestrial geologic exploration
Utility of the Marshall Space Flight (MSFC) facsimile camera system for extraterrestrial geologic exploration was investigated during the spring of 1971 near Merriam Crater in northern Arizona. Although the system with its present hard-wired recorder operates erratically, the imagery showed that the camera could be developed as a prime imaging tool for automated missions. Its utility would be enhanced by development of computer techniques that utilize digital camera output for construction of topographic maps, and it needs increased resolution for examining near field details. A supplementary imaging system may be necessary for hand specimen examination at low magnification.
Wolfe, E. W.↗
Design, capability, and cost of a Versatile Upper Stage /VUS/ family of vehicles.
Trade-off studies and a preliminary design were accomplished to investigate the Versatile Upper Stage (VUS) concept. This concept entails the development by one contractor of a family of stages with a great deal of commonality to perform a spectrum of potential unmanned automated missions planned through 1990. The trade studies and analyses revealed areas where the penalty for commonality between stages was excessive in weight and performance loss. This occurred in the selection of the vehicle structural shell. In many of the expensive subsystems, especially astrionics, it was found that establishing the requirements for all family members and the application of commonality in subsystem selection could result in significant savings.
Haltermann, R. L.↗