Search NASA⌕ Search

SEARCH · Search NASA

Results for “remote operations center”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS1999

NASA AMES Remote Operations Center for 2001

There is a Memorandum of Agreement between NASA Ames, JPL, West Virginia University and University of Arizona which led to funding for the MECA microscope and to the establishment of an Ames facility for science analysis of microscopic and other data. The data and analysis will be by agreement of the Mars Environmental Compatibility Assessment (MECA), Robotic Arm Camera (RAC) and other PI's. This facility is intended to complement other analysis efforts with one objective of this facility being to test the latest information technologies in support of actual mission science operations. Additionally, it will be used as a laboratory for the exploration of collaborative science activities. With a goal of enhancing the science return for both Human Exploration and Development of Space (HEDS) and Astrobiology we shall utilize various tools such as superresolution and the Virtual Environment Vehicle Interface (VEVI) virtual reality visualization tools. In this presentation we will describe the current planning for this facility.

Sims, M.↗
NASA NTRSDate not supplied

Where is the Human in the Loop? Human Factors Analysis of Extended Visual Line of Sight Unmanned Aerial System Operations within a Remote Operations Environment

Many envisioned technological and conceptual innovations focus on allocating more functions to automation, relegating the human as an afterthought if not a nuisance. Yet, until complete autonomy is realized, the human will remain “in the loop”. The National Aeronautics and Space Administration is supporting research for the development and maturation of automated technologies and architectures for the future of advanced air mobility. Standing up a remote operations center used to control, manage, and monitor multiple highly automated vehicles is an important step towards realizing the advanced air mobility vision. At the National Aeronautics and Space Administration’s Langley Research Center, a remote operation center exists and has been tested using humans piloting simulated vehicles. In this paper, we explore the human element within live flight operations that rely on increasingly automated technologies. Four ground control station operators performed multiple live flight operations. We employed a naturalistic approach and relied on qualitative data such as interviews and discussions with subject matter experts to help facilitate discovery. The present work evaluates the functions that the human and the automation had during the live operations, lists psychological constructs that may have promoted or reduced task performance, and provides recommendations on design of the remote operations environment and training of future ground control station operators.

Advanced Air Mobility↗
NASA NTRSDate not supplied

Where is the Human in the Loop? Human Factors Analysis of Extended Visual Line of Sight Unmanned Aerial System Operations within a Remote Operations Environment

Many envisioned technological and conceptual innovations focus on allocating more functions to automation, relegating the human as an afterthought if not a nuisance. Yet, until complete autonomy is realized, the human will remain “in the loop”. The National Aeronautics and Space Administration is supporting research for the development and maturation of automated technologies and architectures for the future of advanced air mobility. Standing up a remote operations center used to control, manage, and monitor multiple highly automated vehicles is an important step towards realizing the advanced air mobility vision. At the National Aeronautics and Space Administration’s Langley Research Center, a remote operation center exists and has been tested using humans piloting simulated vehicles. In this paper, we explore the human element within live flight operations that rely on increasingly automated technologies. Four ground control station operators performed multiple live flight operations. We employed a naturalistic approach and relied on qualitative data such as interviews and discussions with subject matter experts to help facilitate discovery. The present work evaluates the functions that the human and the automation had during the live operations, lists psychological constructs that may have promoted or reduced task performance, and provides recommendations on design of the remote operations environment and training of future ground control station operators.

Advanced Air Mobility↗
NASA NTRS2024

Concept, Design, & Implementation of a Remote Vehicle Operations Center for Autonomous Missions

The National Aeronautics and Space Administration is supporting research to develop a prototype remote vehicle operations center at Langley Research Center to explore current and future advanced air mobility operations using small unmanned aerial systems vehicles as surrogates for future, larger-scale passenger carrying vehicles. The prototype facility known as the Remote Operations for Autonomous Missions (ROAM) Unmanned Aerial Systems (UAS) Operations Center is being used to explore different roles and responsibilities of remote operators managing multiple autonomous vehicles, with the goal of exploring human-autonomy teaming concepts that enable m:N operations (i.e., m operators managing N vehicles). ROAM has developed into a world-class research, development, and technology (RD&T) environment that can support both the collection of human factors data and the command and control of remote vehicles in beyond visual line of sight conditions. ROAM provides a key capability to enable full end-to-end hardware- and human-in-the-loop simulation testing, connecting with simulated small-UAS and creating a seamless Live-Virtual-Constructive (LVC) environment. This report describes the development of the ROAM UAS Operations Center from concept through design, culminating in the current implementation at NASA’s Langley Research Center.

CERTAIN↗
NASA NTRS2023

A Remote Vehicle Operations Center’s Role in Collecting Human Factors Data

The National Aeronautics and Space Administration is supporting research to develop a prototype remote vehicle operations center at Langley Research Center to explore current and future advanced air mobility operations using small unmanned aerial systems vehicles as surrogates for future, larger-scale passenger carrying vehicles. Data collected within the Remote Operations for Autonomous Missions (ROAM) Unmanned Aerial Systems (UAS) Operations Center will be used to explore different roles and responsibilities of remote operators managing multiple autonomous vehicles, with the goal of exploring human-autonomy teaming concepts that enable m:N operations (i.e., m operators managing N vehicles). ROAM has developed into a world-class research, development, and technology (RD&T) environment that can support both the collection of human factors data and the command and control of remote vehicles in beyond visual line of sight conditions. Presented in this paper is an overview of ROAM, with a focus on the design components that support human factors data collection and a review of initial usability results of the facility.

Human factors↗
NASA NTRS2023

A Remote Vehicle Operations Center’s Role in Collecting Human Factors Data

The National Aeronautics and Space Administration is supporting research to develop a prototype remote vehicle operations center at Langley Research Center to explore current and future advanced air mobility operations using small unmanned aerial systems vehicles as surrogates for future, larger-scale passenger carrying vehicles. Data collected within the Remote Operations for Autonomous Missions (ROAM) Unmanned Aerial Systems (UAS) Operations Center will be used to explore different roles and responsibilities of remote operators managing multiple autonomous vehicles, with the goal of exploring human-autonomy teaming concepts that enable m:N operations (i.e., m operators managing N vehicles). ROAM has developed into a world-class research, development, and technology (RD&T) environment that can support both the collection of human factors data and the command and control of remote vehicles in beyond visual line of sight conditions. Presented in this paper is an overview of ROAM, with a focus on the design components that support human factors data collection and a review of initial usability results of the facility.

Human factors↗
NASA NTRSDate not supplied

Preliminary Development of Multi-Vehicle (m:N) Operations with NASA Langley’s Remote Vehicle Operations Center

To achieve the vision of Advanced Air Mobility (AAM), a transition from localized operations of aircraft to remote operations is being pursued across many use cases. This transition will allow fewer human operators to manage more increasingly autonomous aircraft (i.e., m operators managing N vehicles, or m:N). To study this operational concept, the National Aeronautics and Space Administration (NASA) Langley Research Center (LaRC) has developed a prototype remote vehicle operations center and ground control station (GCS) software to conduct research with simulated and real flight operations. To date, flight operations at LaRC have been limited to one vehicle per operator. However, the current paper describes initial development and considerations for enabling m:N flight operations at LaRC. Further, the research described in this paper provides the foundation for a concept of operations (ConOps) that will be developed to support remote operators managing multiple increasingly autonomous vehicles, with the goal of exploring human-autonomy teaming (HAT) concepts that enable more advanced m:N operations. Two key enablers have been identified to facilitate successful m:N operations: GCS software updates for multi-vehicle management and procedural updates for vehicle handoffs during off-nominal events. Additionally, specific modifications were identified across five key areas: technology and software, team structure, inter-team communication, contingency plans, and operator decision flows. Next steps in forming the LaRC m:N ConOps will include working with subject-matter experts to identify off-nominal scenarios, implementing the recommended GCS functionality for m:N operations, and performing integration testing of facility capabilities and new operational procedures. Although the future m:N ConOps will be tailored to the NASA LaRC remote operations facility and flight range, it is intended to be a transparent, accessible, and reality-based exemplar for external organizations seeking to create or evaluate their own m:N operational concepts.

m:N↗
NASA NTRS1986

Remote Science Operation Center research

Progress in the following areas is discussed: the design, planning and operation of a remote science payload operations control center; design and planning of a data link via satellite; and the design and prototyping of an advanced workstation environment for multi-media (3-D computer aided design/computer aided engineering, voice, video, text) communications and operations.

Banks, P. M.↗
NASA NTRS1978

Ground based simulation of life sciences Spacelab experiments

The third in a series of Spacelab Mission Development tests was a joint effort of the Ames Research and Johnson Space Centers to evaluate planned operational concepts of the Space Shuttle life sciences program. A three-man crew conducted 26 experiments and 12 operational tests, utilizing both human and animal subjects. The crew lived aboard an Orbiter/Spacelab mockup for the seven-day simulation. The Spacelab was identical in geometry to the European Space Agency design, complete with removable rack sections and stowage provisions. Communications were controlled as currently planned for operational Shuttle flights. A Science Operations Remote Center at the Ames Research Center was managed by simulated Mission Control and Payload Operation Control Centers at the Johnson Space Center. This paper presents the test objectives, describes the facilities and test program, and outlines the results of this test.

Rummel, J. A.↗
NASA NTRS1979

Engineering and simulation of life sciences Spacelab experiments

The third in a series of Spacelab Mission Development tests was conducted at the Johnson (correction of Johnston) Space Center as a part of the development of Life Sciences experiments for the Space Shuttle era. The latest test was a joint effort of the Ames Research and Johnson Space Centers and utilized animals and men for study. The basic objective of this test was to evaluate the operational concepts planned for the Space Shuttle life science payloads program. A three-man crew (Mission Specialist and two Payload Specialists) conducted 26 experiments and 12 operational tests, which were selected for this 7-day mission simulation. The crew lived on board a simulated Orbiter/Spacelab mockup 24 hr a day. The Orbiter section contained the mid deck crew quarters area, complete with sleeping, galley and waste management provisions. The Spacelab was identical in geometry to the European Space Agency Spacelab design, complete with removable rack sections and stowage provisions. Communications between the crewmen and support personnel were configured and controlled as currently planned for operational shuttle flights. For this test a Science Operations Remote Center was manned at the Ames Research Center and was managed by simulated Mission Control and Payload Operation Control Centers at the Johnson Space Center. This paper presents the test objectives, description of the facilities and test program, and the results of this test.

Biological Sciences/instrumentation/methods↗
NASA NTRS2017

Application of the Core Flight System to a Lunar Rover

Resource Prospector (RP) is a lunar mission sponsored by NASAs Advanced Exploration Systems (AES) division, that aims to study in-situ resource utilization (ISRU) feasibility and technologies on the surface of the moon. The RP missions lunar surface segment includes a rover equipped with with a suite of instruments specifically designed to measure and map volatiles both at the surface and in the subsurface. Of particular interest is the quantity and state of volatiles in permanently shadowed regions. To conduct the mission, ground system operators will remotely drive the rover, directing it to waypoints along the surface in order to achieve measurement objectives. At selected locations, an onboard drill will be deployed to collect material and obtain direct measurements of the subsurface constituents. RP is currently planned for launch in 2022. RP is managed at NASA Ames Research Center. The RP Rover is being designed and developed by NASA Johnson Space Center (JSC) in partnership with NASA Ames. NASA Kennedy Space Center (KSC) is responsible for the Honeybee drilling system and science payload.In order to better understand the technical challenges and demonstrate capability, in 2015 the RP project developed a rover testbed (known as RP15). In this mission in a year, a rover was designed, developed, and outfitted with science instruments and a drill. The rover was operated from a remote operations center, and operated in an outdoor lunar rock yard at Johnson space center. The study was a resounding success meeting all objectives. The RP Rover software architecture and development processes were based on the successful Lunar Atmosphere and Dust Environment Explorer spacecraft. This architecture is built on the Core Flight System software and an interface to MatlabSimulink auto-generated software components known as the Simulink Interface Layer (SIL). The application of this lunar satellite inspired framework worked well for the rover application, and is currently being planned for the mission. This presentation provides an overview of the architecture and processes, and describes some of the changes and challenges for the rover application.

CFS↗
NASA NTRS2017

Application of CFS to a Lunar Rover: Resource Prospector (RP)

Resource Prospector (RP) is a lunar mission sponsored by NASA's Advanced Exploration Systems (AES) division, that aims to study in-situ resource utilization (ISRU) feasibility and technologies on the surface of the moon. The RP mission's lunar surface segment includes a rover equipped with with a suite of instruments specifically designed to measure and map volatiles both at the surface and in the subsurface. Of particular interest is the quantity and state of volatiles in permanently shadowed regions. To conduct the mission, ground system operators will remotely drive the rover, directing it to waypoints along the surface in order to achieve measurement objectives. At selected locations, an onboard drill will be deployed to collect material and obtain direct measurements of the subsurface constituents. RP is currently planned for launch in 2022. RP is managed at NASA Ames Research Center. The RP Rover is being designed and developed by NASA Johnson Space Center (JSC) in partnership with NASA Ames. NASA Kennedy Space Center (KSC) is responsible for the Honeybee drilling system and science payload. In order to better understand the technical challenges and demonstrate capability, in 2015 the RP project developed a rover testbed (known as RP15). In this mission in a year, a rover was designed, developed, and outfitted with science instruments and a drill. The rover was operated from a remote operations center, and operated in an outdoor lunar rock yard at Johnson space center. The study was a resounding success meeting all objectives. The RP Rover software architecture and development processes were based on the successful Lunar Atmosphere and Dust Environment Explorer spacecraft. This architecture is built on the Core Flight System software and an interface to Matlab/Simulink auto-generated software components known as the Simulink Interface Layer (SIL). The application of this lunar satellite inspired framework worked well for the rover application, and is currently being planned for the mission. This presentation provides an overview of the architecture and processes, and describes some of the changes and challenges for the rover application.

RP↗
NASA NTRS2003

Tracking capability for entry, descent and landing and its support to NASA Mars Exploration Rovers

This paper described a new capability recently deployed in the NASA Deep Space Network to support the entry, descent and landing of the two Mars Exploration Rovers - Spirit and Opportunity. This final segment of a 7-month journey was critical step in enabling successful mission operation. The EDL Data Analysis (EDA) equipment processed the open loop recording samples from the existing radio science receivers, extracted the MFSK-modulated tones, and provided information on the occurrence of associated events happened onboard spacecraft. The EDA software supported real-time as well as post pass processing. The design flexibility allowed the track to be divided into different segments, each could be processed with a configuration optimized for its signal conditions and uncertainties. The use of dynamic lock state concept enabled signal detection be done with minimum required computing power - less was spent when signal was steadily detected and more when signal fluctuated. With the server-client design, the EDA supported connections to different remote operation centers for monitor purpose. The paper also presented the field results from both Spirit and Opportunity landings. The detection were much better than anticipated. All critical event tones were seen in real time. Surprising detection of LCP signal was found with Spirit landing, resulted in a reconfiguration for Opportunity landing to maximize signal detection.

tracking↗
NASA NTRSDate not supplied

Upper Class E Traffic Management: NASA's Collaborative Research and Technical Development to Enable Routine, Safe, and Scalable High Altitude Operation

In the past, operations at high altitudes have been limited in number and largely conducted for defense/security purposes. However, with broad technological advances, a growing number of commerical and public good use cases, and a significant rise in the number of capable platforms, the demand for operating in high altitude airspace - known as upper Class E in the United States - is increasing. With that increase in demand comes the need for a means to manage the airspace in a way that does not burden current air traffic services and infrastructure given that provisions for commercial operations are limited. NASA, in collaboration with other government agencies and strong representation from industry, has developed a cooperative approach to airspace management referred to as Upper Class E Traffic Management (ETM). Key aspects of the ETM concept are the ability to exchange information through services that enable the operators to share airspace in cetain areas by adhering to cooperative operating practices (COPs) and by having shared situation awareness. To advance the concept, NASA recently developed and formally tested the first dedicated reference ETM system and supportin architecture. The test involved real-time simulation of high altitude operations with a diverse set of aircraft and encourter situations that included industry partners connected to the system from their remote operating centers. This presentation will provide attendees with an understanding of the ETM concept, the details and importance of the system that has been developed, an overview of the groundbreaking simulation, and a glimpse of things to come in our next steps.

Conrad Dang-Gabriel↗
NASA NTRS2004

Remote Operations and Ground Control Centers

The Payload Operations Integration Center at the Marshall Space Flight Center supports the International Space Station (ISS) through remote interfaces around the world. The POI$ was originally designed as a gateway to space for remote facilities; ranging from an individual user to a fullscale multi-user environment. This achievement was accomplished while meeting program requirements and accommodating the injection of modem technology on an ongoing basis to ensure cost operations. This paper will discuss the open POIC architecture developed to support similar and dissimilar remote operations centers. It will include technologies, protocols, and compromises which on a day to day basis support ongoing operations. Additional areas covered include centralized management of shared resources and methods utilized to provide highly available and restricted resources to remote users. Finally, the effort of coordinating the actions of participants will be discussed.

Bryant, Barry S.↗
NASA NTRS2004

Remote Operations and Ground Control Centers

The Payload Operations Integration Center (POIC) at the Marshall Space Flight Center supports the International Space Station (ISS) through remote interfaces around the world. The POIC was originally designed as a gateway to space for remote facilities; ranging from an individual user to a full-scale multiuser environment. This achievement was accomplished while meeting program requirements and accommodating the injection of modern technology on an ongoing basis to ensure cost effective operations. This paper will discuss the open POIC architecture developed to support similar and dissimilar remote operations centers. It will include technologies, protocols, and compromises which on a day to day basis support ongoing operations. Additional areas covered include centralized management of shared resources and methods utilized to provide highly available and restricted resources to remote users. Finally, the effort of coordinating the actions of participants will be discussed.

Bryant, Barry S.↗
NASA NTRS2015

Telescience Resource Kit (TReK)

Telescience Resource Kit (TReK) is one of the Huntsville Operations Support Center (HOSC) remote operations solutions. It can be used to monitor and control International Space Station (ISS) payloads from anywhere in the world. It is comprised of a suite of software applications and libraries that provide generic data system capabilities and access to HOSC services. The TReK Software has been operational since 2000. A new cross-platform version of TReK is under development. The new software is being released in phases during the 2014-2016 timeframe. The TReK Release 3.x series of software is the original TReK software that has been operational since 2000. This software runs on Windows. It contains capabilities to support traditional telemetry and commanding using CCSDS (Consultative Committee for Space Data Systems) packets. The TReK Release 4.x series of software is the new cross platform software. It runs on Windows and Linux. The new TReK software will support communication using standard IP protocols and traditional telemetry and commanding. All the software listed above is compatible and can be installed and run together on Windows. The new TReK software contains a suite of software that can be used by payload developers on the ground and onboard (TReK Toolkit). TReK Toolkit is a suite of lightweight libraries and utility applications for use onboard and on the ground. TReK Desktop is the full suite of TReK software -most useful on the ground. When TReK Desktop is released, the TReK installation program will provide the option to choose just the TReK Toolkit portion of the software or the full TReK Desktop suite. The ISS program is providing the TReK Toolkit software as a generic flight software capability offered as a standard service to payloads. TReK Software Verification was conducted during the April/May 2015 timeframe. Payload teams using the TReK software onboard can reference the TReK software verification. TReK will be demonstrated on-orbit running on an ISS provided T61p laptop. Target Timeframe: September 2015 -2016. The on-orbit demonstration will collect benchmark metrics, and will be used in the future to provide live demonstrations during ISS Payload Conferences. Benchmark metrics and demonstrations will address the protocols described in SSP 52050-0047 Ku Forward section 3.3.7. (Associated term: CCSDS File Delivery Protocol (CFDP)).

Lippincott, Jeff↗