SEARCH · Search NASA

Results for “Mission Operations”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 649 records · Page 36

All sources NASA NTRS DOE OSTI

NASA NTRS2001

Human Centered Autonomous and Assistant Systems Testbed for Exploration Operations

The Engineering and Mission Operations Directorates at NASA Johnson Space Center are combining laboratories and expertise to establish the Human Centered Autonomous and Assistant Systems Testbed for Exploration Operations. This is a testbed for human centered design, development and evaluation of intelligent autonomous and assistant systems that will be needed for human exploration and development of space. This project will improve human-centered analysis, design and evaluation methods for developing intelligent software. This software will support human-machine cognitive and collaborative activities in future interplanetary work environments where distributed computer and human agents cooperate. We are developing and evaluating prototype intelligent systems for distributed multi-agent mixed-initiative operations. The primary target domain is control of life support systems in a planetary base. Technical approaches will be evaluated for use during extended manned tests in the target domain, the Bioregenerative Advanced Life Support Systems Test Complex (BIO-Plex). A spinoff target domain is the International Space Station (ISS) Mission Control Center (MCC). Prodl}cts of this project include human-centered intelligent software technology, innovative human interface designs, and human-centered software development processes, methods and products. The testbed uses adjustable autonomy software and life support systems simulation models from the Adjustable Autonomy Testbed, to represent operations on the remote planet. Ground operations prototypes and concepts will be evaluated in the Exploration Planning and Operations Center (ExPOC) and Jupiter Facility.

Malin, Jane T.↗

NASA NTRS2017

Progress of Crew Autonomous Scheduling Test (CAST) On the ISS

The United States space policy is evolving toward missions beyond low Earth orbit. In an effort to meet that policy, NASA has recognized Autonomous Mission Operations (AMO) as a valuable capability. Identified within AMO capabilities is the potential for autonomous planning and replanning during human spaceflight operations. That is allowing crew members to collectively or individually participate in the development of their own schedules. Currently, dedicated mission operations planners collaborate with international partners to create daily plans for astronauts aboard the International Space Station (ISS), taking into account mission requirements, ground rules, and various vehicle and payload constraints. In future deep space operations the crew will require more independence from ground support due to communication transmission delays. Furthermore, crew members who are provided with the capability to schedule their own activities are able to leverage direct experience operating in the space environment, and possibly maximize their efficiency. CAST (Crew Autonomous Scheduling Test) is an ISS investigation designed to analyze three important hypotheses about crew autonomous scheduling. First, given appropriate inputs, the crew is able to create and execute a plan in a reasonable period of time without impacts to mission success. Second, the proximity of the planner, in this case the crew, to the planned operations increases their operational efficiency. Third, crew members are more satisfied when given a role in plan development. This presentation shows the progress done in this study with a single astronaut test subject participating in five CAST sessions. CAST is a technology demonstration payload sponsored by the ISS Research Science and Technology Office, and performed by experts in Mission Operations Planning from the Flight Operations Directorate at NASA Johnson Space Center, and researchers across multiple NASA centers.

Healy, Matthew↗

NASA NTRS2012

EO-1/Hyperion: Nearing Twelve Years of Successful Mission Science Operation and Future Plans

The Earth Observing One (EO-1) satellite is a technology demonstration mission that was launched in November 2000, and by July 2012 will have successfully completed almost 12 years of high spatial resolution (30 m) imaging operations from a low Earth orbit. EO-1 has two unique instruments, the Hyperion and the Advanced Land Imager (ALI). Both instruments have served as prototypes for NASA's newer satellite missions, including the forthcoming (in early 2013) Landsat-8 and the future Hyperspectral Infrared Imager (HyspIRI). As well, EO-1 is a heritage platform for the upcoming German satellite, EnMAP (2015). Here, we provide an overview of the mission, and highlight the capabilities of the Hyperion for support of science investigations, and present prototype products developed with Hyperion imagery for the HyspIRI and other space-borne spectrometers.

Middleton, Elizabeth M.↗

NASA NTRS2000

NASA Goddard Space Flight Center

The NASA SLR Operational Center is responsible for: 1) NASA SLR network control, sustaining engineering, and logistics; 2) ILRS mission operations; and 3) ILRS and NASA SLR data operations. NASA SLR network control and sustaining engineering tasks include technical support, daily system performance monitoring, system scheduling, operator training, station status reporting, system relocation, logistics and support of the ILRS Networks and Engineering Working Group. These activities ensure the NASA SLR systems are meeting ILRS and NASA mission support requirements. ILRS mission operations tasks include mission planning, mission analysis, mission coordination, development of mission support plans, and support of the ILRS Missions Working Group. These activities ensure than new mission and campaign requirements are coordinated with the ILRS. Global Normal Points (NP) data, NASA SLR FullRate (FR) data, and satellite predictions are managed as part of data operations. Part of this operation includes supporting the ILRS Data Formats and Procedures Working Group. Global NP data operations consist of receipt, format and data integrity verification, archiving and merging. This activity culminates in the daily electronic transmission of NP files to the CDDIS. Currently of all these functions are automated. However, to ensure the timely and accurate flow of data, regular monitoring and maintenance of the operational software systems, computer systems and computer networking are performed. Tracking statistics between the stations and the data centers are compared periodically to eliminate lost data. Future activities in this area include sub-daily (i.e., hourly) NP data management, more stringent data integrity tests, and automatic station notification of format and data integrity issues.

Carter, David↗

NASA NTRS1992

Cognitive engineering models in space systems

NASA space systems, including mission operations on the ground and in space, are complex, dynamic, predominantly automated systems in which the human operator is a supervisory controller. The human operator monitors and fine-tunes computer-based control systems and is responsible for ensuring safe and efficient system operation. In such systems, the potential consequences of human mistakes and errors may be very large, and low probability of such events is likely. Thus, models of cognitive functions in complex systems are needed to describe human performance and form the theoretical basis of operator workstation design, including displays, controls, and decision support aids. The operator function model represents normative operator behavior-expected operator activities given current system state. The extension of the theoretical structure of the operator function model and its application to NASA Johnson mission operations and space station applications is discussed.

Mitchell, Christine M.↗

NASA NTRSDate not supplied

HelioSwarm: The Swarm is the Observatory

HelioSwarm will transform our understanding of space plasma turbulence by being the first-of-its-kind simultaneous, multiscale observatory comprising multiple spacecraft. HelioSwarm was competitively selected under the Heliophysics Explorers Program 2019 Medium-Class Explorer (MIDEX) Announcement of Opportunity. The central powered-ESPA hub spacecraft is co-orbited by eight SmallSat Node spacecraft, together moving through a High Earth Orbit to obtain data in various solar wind regimes. The mission architecture is that of hub-and-spoke, with the larger hub serving as a communications relay between the nodes and DSN. Mission operations, management, and technical oversight are provided by NASA Ames Research Center; the spacecraft are provided by Northrop Grumman and BCT. The instrument suite includes foreign-contributed instruments and U.S. ones, all under the oversight of University of New Hampshire (which is also the Principal Investigator’s home institution and Science Operations Center). The mission timeline from launch through conclusion of the one-year science mission is provided along with a summarized concept of operations, with particular emphasis on placing the nodes in their proper relative orbit loops to form the geometry needed for science collection at apogee. A brief discussion of how a combination of legacy tools and custom-created swarm analysis tools are used to design the swarm and sort and visualize the collected science data and telemetry in context is provided. Finally, an exploration of the pathfinding nature of HelioSwarm and some implications for future large scientific swarms is offered.

Heliophysics↗

NASA NTRSDate not supplied

HelioSwarm: The Swarm is the Observatory

The HelioSwarm Mission will transform our understanding of space plasma turbulence by being the first-of-its-kind simultaneous, multiscale observatory comprising multiple spacecraft. HelioSwarm was competitively selected under the Heliophysics Explorers Program 2019 Medium-Class Explorer (MIDEX) Announcement of Opportunity. The central powered-ESPA Hub spacecraft is co-orbited by eight SmallSat Node spacecraft, together moving through a High Earth Orbit to obtain data in various solar wind regimes. The mission architecture is that of hub-and-spoke, with the larger hub serving as a communications relay between the Nodes and DSN. Mission operations, management, and technical oversight are provided by NASA Ames Research Center; the spacecraft are provided by Northrop Grumman and BCT. The instrument suite includes foreign-contributed instruments and U.S. ones, all under the oversight of University of New Hampshire (which is also the Principal Investigator’s home institution and Science Operations Center). The mission timeline from launch through conclusion of the one-year science mission is provided along with a summarized concept of operations, with particular emphasis on placing the Nodes in their proper relative orbit loops to form the geometry needed for science collection at apogee. A brief discussion of how a combination of legacy tools and custom-created swarm analysis tools are used to design the swarm and sort and visualize the collected science data and telemetry in context is provided. Finally, an exploration of the pathfinding nature of HelioSwarm and some implications for future large scientific swarms is offered.

Heliophysics↗

NASA NTRS2018

Preparing to Assure Mission Success

Space flight missions are inherently risky. The mission operations assurance discipline grew out of strategies to control error and evolved into what today is an independent technical authority dedicated to achieving mission success. After the Mars Climate Orbiter loss, NASA made a set of recommendations for missions. Two of those recommendations led to the creation of today’s Mission Operations Assurance Manager role: (1) require an independent Mission Assurance representative during the operational phase of every flight project, and (2) require all flight projects to report and track post-launch anomalies. Since then, the MOAM role has been continually refined by lessons learned from its practice on more than 20 concurrent missions. The MOAM role requires significant operations experience as well as an additional set of skills. In the interests of developing a cadre of potential MOAMs, the MOAM training program was developed. It is a 14-unit set of presentations/discussions covering the 11 categories of MOAM tasks. It is offered to new MOAMs and interested systems engineers with an eye to preparing both types of personnel for present and future assignments, as well as building relationships among personnel of different organizations. MOAM training sessions include presentations on the various tools and processes employed by MOAMs, interspersed with mindset lessons illustrated via “war story” discussions of previous missions.

Bryant, Larry↗

NASA NTRS2014

LADEE Multi-Domain Simulation

The Lunar Atmosphere Dust Environment Explorer (LADEE) was a small explorer class spacecraft that was launched on Sept 7, 2013 and that was de-orbited and successfully impacted the Moons surface on April 17, 2014 after completing all of the mission objectives. The low-cost rapidly prototyped hardware design used for the spacecraft was extend to the development of the software base. To achieve this goal, a Model Based Design approach was utilized to develop the onboard flight software, and out of this development a model based multipurpose simulator was created of the LADEE spacecraft and its mission environment. This simulator extended the traditional function of propagating the vehicle's kinematic and rotational states and included the electrical and thermal states propagation. Traditionally, these domains are handled by domain specific high fidelity simulations that use the states histories from other domains as input. By reducing the fidelity and abstracting the relevant features being monitored and controlled by the flight software, it was possible to model the coupling across these domains resulting in more accurate overall system behavior. A faster than real-time workstation (WSIM) version of the LADEE simulator was used to develop and test the software control algorithms in the Simulink environment. To maximize the performance of the simulation, modeling knobs were introduced to reduce the resolution of the some of the domains models when the effects of that domain were not significant for the scope of that simulation. The automatic code generation feature in Simulink was used to port the simulation to several real-time environments to support Processor-in-the-Loop (PIL) and Hardware-in-the-Loop (HIL) testing, verification and validation. The real-time environment required that the design of each of the domain models be deterministic as possible in the time required to perform all of the calculations to update its states. The simulation interface was designed to be compatible with the command interface employed by the LADEE mission operation team. The WSIM, PIL, and HIL simulators thus used a common interface and thus were used for flight software testing, for mission operations personnel training (nominal and off-nominal operations) prior to the mission and to perform command sequence verification during the mission. This presentation will look at the modeling strategies used to create a common interface to the simulator and to model and couple multiple domains within the simulation, the results of those strategies, and the lessons learned.

Multi-Domain↗

NASA NTRS1993

Commonality of flight control systems for support of European telecommunications missions

This paper is concerned with the presentation of mission-independent software systems that provide a common software platform to ground data systems for mission operations. The objectives of such common software platforms are to reduce the cost of the development of mission-dedicated software systems and to increase the level of reliability of the ground data systems for mission operations. In accordance with this objective, the Multi-Satellite Support System (MSSS) was developed at the European Space Operations Center (ESOC). Between 1975 and 1992, the MSSS provided support to 16 European Space Agency (ESA) missions, among them very demanding science missions such as GEOS, EXOSAT, and Giotto. The successful support of these missions proved the validity of the MSSS concept with its extended mission-independent platform. This paper describes the MSSS concept and focuses on the wide use of MSSS as a flight control system for geosynchronous telecommunications satellites. Reference is made to more than 15 telecommunications missions that are operated from Western Europe using flight control systems with an underlying MSSS concept, demonstrating the benefits of a commonly used software platform. Finally, the paper outlines the design of the new generation of flight control systems, which is being developed at ESOC for this decade, following a period of more than 15 years of MSSS support.

Debatin, Kurt↗

NASA NTRS1994

Designing an autonomous environment for mission critical operation of the EUVE satellite

Since the launch of NASA's Extreme Ultraviolet Explorer (EUVE) satellite in 1992, there has only been a handful of occurrences that have warranted manual intervention in the EUVE Science Operations Center (ESOC). So, in an effort to reduce costs, the current environment is being redesigned to utilize a combination of off-the-shelf packages and recently developed artificial intelligence (AI) software to automate the monitoring of the science payload and ground systems. The successful implementation of systemic automation would allow the ESOC to evolve from a seven day/week, three shift operation, to a seven day/week one shift operation. First, it was necessary to identify all areas considered mission critical. These were defined as follows: (1) The telemetry stream must be monitored autonomously and anomalies identified. (2) Duty personnel must be automatically paged and informed of the occurrence of an anomaly. (3) The 'basic' state of the ground system must be assessed. (4) Monitors should check that the systems and processes needed to continue in a 'healthy' operational mode are working at all times. (5) Network loads should be monitored to ensure that they stay within established limits. (6) Connectivity to Goddard Space Flight Center (GSFC) systems should be monitored as well, not just for connectivity of the network itself but also for the ability to transfer files. (7) All necessary peripheral devices should be monitored. This would include the disks, routers, tape drives, printers, tape carousel, and power supplies. (8) System daemons such as the archival daemon, the Sybase server, the payload monitoring software, and any other necessary processes should be monitored to ensure that they are operational. (9) The monitoring system needs to be redundant so that the failure of a single machine will not paralyze the monitors. (10) Notification should be done by means of looking though a table of the pager numbers for current 'on call' personnel. The software should be capable of dialing out to notify, sending email, and producing error logs. (11) The system should have knowledge of when real-time passes and tape recorder dumps will occur and should know that these passes and data transmissions are successful. Once the design criteria were established, the design team split into two groups: one that addressed the tracking, commanding, and health and safety of the science payload and another group that addressed the ground systems and communications aspects of the overall system.

Abedini, Annadiana↗

NASA NTRS2014

Opals: Mission System Operations Architecture for an Optical Communications Demonstration on the ISS

In April of 2014, the Optical PAyload for Lasercomm Science (OPALS) Flight System (FS) launched to the International Space Station (ISS) to demonstrate space-to-ground optical communications. During a planned 90-day baseline mission, the OPALS FS will downlink high quality, short duration videos to the Optical Communications Telescope Laboratory (OCTL) ground station in Wrightwood, California. Interfaces to the ISS payload operations infrastructure have been established to facilitate activity planning, hazardous laser operations, commanding, and telemetry transmission. In addition, internal processes, such as pointing prediction and data processing, satisfy the technical requirements of the mission. The OPALS operations team participates in Operational Readiness Tests (ORTs) with external partners to exercise coordination processes and train for the overall mission. The ORTs have provided valuable insight into operational considerations for the instrument on the ISS.

Technology Demonstration↗

NASA NTRS1990

Long duration mission support operations concepts

It is suggested that the system operations will be one of the most expensive parts of the Mars mission, and that, in order to reduce their cost, they should be considered during the conceptual phase of the Space Exploration Initiative (SEI) program. System operations of Space Station Freedom, Lunar outpost, and Mars Rover Sample Return are examined in order to develop a similar concept for the manned Mars mission. Factors that have to be taken into account include: (1) psychological stresses caused by long periods of isolation; (2) the effects of boredom; (3) the necessity of onboard training to maintain a high level of crew skills; and (4) the 40-min time delays between issuing and receiving a command, which make real-time flight control inoperative and require long-term decisions to be made by the ground support.

Eggleston, T. W.↗

NASA NTRS1993

Influence of a new generation of operations support systems on current spacecraft operations philosophy: The users feedback

Current trends in the spacecraft mission operations area (spacecraft & mission complexity, project duration, required flexibility are requiring a breakthrough for what concerns philosophy, organization, and support tools. A major evolution is related to space operations 'informationalization', i.e adding to existing operations support & data processing systems a new generation of tools based on advanced information technologies (object-oriented programming, artificial intelligence, data bases, hypertext) that automate, at least partially, operations tasks that used be performed manually (mission & project planning/scheduling, operations procedures elaboration & execution, data analysis & failure diagnosis). All the major facets of this 'informationalization' are addressed at MATRA MARCONI SPACE, operational applications were fielded and generic products are becoming available. These various applications have generated a significant feedback from the users (at ESA, CNES, ARIANESPACE, MATRA MARCONI SPACE), which is now allowing us to precisely measure how the deployment of this new generation of tools, that we called OPSWARE, can 'reengineer' current spacecraft mission operations philosophy, how it can make space operations faster, better, and cheaper. This paper can be considered as an update of the keynote address 'Knowledge-Based Systems for Spacecraft Control' presented during the first 'Ground Data Systems for Spacecraft Control' conference in Darmstadt, June 1990, with a special emphasis on these last two years users feedback.

Darroy, Jean Michel↗

NASA NTRS1994

Increases in efficiency and enhancements to the Mars Observer non-stored commanding process

The Mars Observer team was, until the untimely loss of the spacecraft on August 21, 1993, performing flight operations with greater efficiency and speed than any previous JPL mission of its size. This level of through-put was made possible by a mission operations system which was composed of skilled personnel using sophisticated sequencing and commanding tools. During cruise flight operations, however, it was realized by the project that this commanding level was not going to be sufficient to support the activities planned for mapping operations. The project had committed to providing the science instrument principle investigators with a much higher level of commanding during mapping. Thus, the project began taking steps to enhance the capabilities of the flight team. One mechanism used by project management was a tool available from total quality management (TQM). This tool is known as a process action team (PAT). The Mars Observer PAT was tasked to increase the capacity of the flight team's nonstored commanding process by fifty percent with no increase in staffing and a minimal increase in risk. The outcome of this effort was, in fact, to increase the capacity by a factor of 2.5 rather than the desired fifty percent and actually reduce risk. The majority of these improvements came from the automation of the existing command process. These results required very few changes to the existing mission operations system. Rather, the PAT was able to take advantage of automation capabilities inherent in the existing system and make changes to the existing flight team procedures.

Brooks, Robert N., Jr.↗

NASA NTRS1993

A ground-based memory state tracker for satellite on-board computer memory

The TOPEX/POSEIDON satellite, currently in Earth orbit, will use radar altimetry to measure sea surface height over 90 percent of the world's ice-free oceans. In combination with a precise determination of the spacecraft orbit, the altimetry data will provide maps of ocean topography, which will be used to calculate the speed and direction of ocean currents worldwide. NASA's Jet Propulsion Laboratory (JPL) has primary responsibility for mission operations for TOPEX/POSEIDON. Software applications have been developed to automate mission operations tasks. This paper describes one of these applications, the Memory State Tracker, which allows the ground analyst to examine and track the contents of satellite on-board computer memory quickly and efficiently, in a human-readable format, without having to receive the data directly from the spacecraft. This process is accomplished by maintaining a groundbased mirror-image of spacecraft On-board Computer memory.

Quan, Alan↗

NASA NTRS1973

Design of Mariner 9 Science Sequences using Interactive Graphics Software

This paper discusses the analyst/computer system used to design the daily science sequences required to carry out the desired Mariner 9 science plan. The Mariner 9 computer environment, the development and capabilities of the science sequence design software, and the techniques followed in the daily mission operations are discussed. Included is a discussion of the overall mission operations organization and the individual components which played an essential role in the sequence design process. A summary of actual sequences processed, a discussion of problems encountered, and recommendations for future applications are given.

Freeman, J. E.↗

NASA NTRS2017

Sharing Telemetry across Organizations and Systems

The XTCE (XML Telemetric and Command Exchange) standard provides a way to describe space mission telemetry and command “databases” (or dictionaries) to be exchanged across centers and space agencies. Having a standard format for describing the telemetry and command formats allows for the development or adoption of compatible tools and significantly reduces the amount of custom software development often needed to ensure all system components have access to consistent format definitions. The main objective of this paper is to show how powerful XTCE is in terms of interoperability across organizations. This paper summarizes work which entailed converting the mission telemetry database for a current NASA mission, in XTCE format, into several target mission operation databases associated with different telemetry and command toolchains, and then, comparing the results of the telemetry processing and display. The target toolchains selected were Ball Aerospace/COSMOS, NASA-GSFC/ITOS (Goddard Space Flight Center/Integrated Test and Operations System), and NASA-AMMOS/AMPCS (Advanced Multi-Mission Operations System/Mission Data Processing and Control System) – all real-time telemetry and command processing systems.

Jones, Ron↗