SEARCH · Engineering Papers

Results for “operability”

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 1,531 records · Page 85

All sources NASA NTRS DOE OSTI

NASA NTRS2012

Initial Investigations of Controller Tools and Procedures for Schedule-Based Arrival Operations with Mixed Flight-Deck Interval Management Equipage

NASA's Air Traffic Management Demonstration-1 (ATD-1) is a multi-year effort to demonstrate high-throughput, fuel-efficient arrivals at a major U.S. airport using NASA-developed scheduling automation, controller decision-support tools, and ADS-B-enabled Flight-Deck Interval Management (FIM) avionics. First-year accomplishments include the development of a concept of operations for managing scheduled arrivals flying Optimized Profile Descents with equipped aircraft conducting FIM operations, and the integration of laboratory prototypes of the core ATD-1 technologies. Following each integration phase, a human-in-the-loop simulation was conducted to evaluate and refine controller tools, procedures, and clearance phraseology. From a ground-side perspective, the results indicate the concept is viable and the operations are safe and acceptable. Additional training is required for smooth operations that yield notable benefits, particularly in the areas of FIM operations and clearance phraseology.

Callantine, Todd J.↗

NASA NTRS2011

Extended Operation of Stirling Convertors at NASA Glenn Research Center

Glenn Research Center (GRC) is supporting life and reliability database for free-piston Stirilng conversion via extended convertor operation Ongoing convertor operation: 18 convertors (4 TDCs from Infinia, 14 ASCs from Sunpower). 350,000 total convertor hours of operation. 218,000 on Infinia units and 132,000 on Sunpower units. Demonstrating steady convertor performance requires precise maintenance of operating conditions. Sources of disruption : Investigative tests: Varying operating frequency, hot-end temp, cold-end temp. Hot end control method: Constant heat input mode requires more user-adjustment than constant temperature mode. Long-term transients in hot end insulation were observed. Support facility: Open-bath circulator fluid concentration drifting. Nuisance shutdowns (instrumentation failure, EMI, power outages). Ambient temperature fluctuations due to room HVAC.

Oriti, Salvatore↗

NASA NTRS2012

Distributed Motor Controller (DMC) for Operation in Extreme Environments

This paper presents an extreme environment capable Distributed Motor Controller (DMC) module suitable for operation with a distributed architecture of future spacecraft systems. This motor controller is designed to be a bus-based electronics module capable of operating a single Brushless DC motor in extreme space environments: temperature (-120 C to +85 C required, -180 C to +100 C stretch goal); radiation (>;20K required, >;100KRad stretch goal); >;360 cycles of operation. Achieving this objective will result in a scalable modular configuration for motor control with enhanced reliability that will greatly lower cost during the design, fabrication and ATLO phases of future missions. Within the heart of the DMC lies a pair of cold-capable Application Specific Integrated Circuits (ASICs) and a Field Programmable Gate Array (FPGA) that enable its miniaturization and operation in extreme environments. The ASICs are fabricated in the IBM 0.5 micron Silicon Germanium (SiGe) BiCMOS process and are comprised of Analog circuitry to provide telemetry information, sensor interface, and health and status of DMC. The FPGA contains logic to provide motor control, status monitoring and spacecraft interface. The testing and characterization of these ASICs have yielded excellent functionality in cold temperatures (-135 C). The DMC module has demonstrated successful operation of a motor at temperature.

SiGe↗

NASA NTRS2012

Onboard Autonomy and Ground Operations Automation for the Intelligent Payload Experiment (IPEX) CubeSat Mission

The Intelligent Payload Experiment (IPEX) is a cubesat manifested for launch in October 2013 that will flight validate autonomous operations for onboard instrument processing and product generation for the Intelligent Payload Module (IPM) of the Hyperspectral Infra-red Imager (HyspIRI) mission concept. We first describe the ground and flight operations concept for HyspIRI IPM operations. We then describe the ground and flight operations concept for the IPEX mission and how that will validate HyspIRI IPM operations. We then detail the current status of the mission and outline the schedule for future development.

project data planning↗

NASA NTRS2014

The ISS 2B PVTCS Ammonia Leak: An Operational History

In 2006, the Photovoltaic Thermal Control System (PVTCS) for the International Space Station's 2B power channel began leaking ammonia at a rate of approximately 1.5lbm/year (out of a starting approximately 53lbm system ammonia mass). Initially, the operations strategy was "feed the leak," a strategy successfully put into action via Extra Vehicular Activity during the STS‐134 mission. During this mission the system was topped off with ammonia piped over from a separate thermal control system. This recharge was to have allowed for continued power channel operation into 2014 or 2015, at which point another EVA would have been required. Without these periodic EVAs to refill the 2B coolant system, the channel would eventually leak enough fluid as to risk pump cavitation and system failure, resulting in the loss of the 2B power channel - the most critical of the Space Station's 8 power channels. In mid‐2012, the leak rate increased to approximately 5lbm/year. Once discovered, an EVA was planned and executed within a 5 week timeframe to drastically alter the architecture of the PVTCS via connection to a dormant thermal control system not intended to be utilized as anything other than spare components. The purpose of this rerouting of the TCS was to increase system volume and to isolate the photovoltaic radiator, thought to be the likely leak source. This EVA was successfully executed on November 1st, 2012 and left the 2B PVTCS in a configuration where the system was now being adequately cooled via a totally different radiator than what the system was designed to utilize. Unfortunately, data monitoring over the next several months showed that the isolated radiator was not leaking, and the system itself continued to leak steadily until May 9th, 2013. It was on this day that the ISS crew noticed the visible presence of ammonia crystals escaping from the 2B channel's truss segment, signifying a rapid acceleration of the leak from 5lbm/year to 5lbm/day. Within 48 hours of the crew noticing the leak, an EVA was in progress to replace the coolant pump - the only other replaceable leak source. This paper will explore the management of the 2B PVTCS leak from the operations perspective. It will discuss the methodology of performing the STS‐134 refill, the considerations and contingency plans which went into the architectural overhaul of the system in 2012, and the unprecedented effort which went into the EVA response to the visible leak of May 2013. In particular the paper will focus on the techniques utilized by flight controllers to monitor the system health and to respond to such instances as the rapid May 2013 leak by putting the electrical system in a safe configuration for loss of cooling, and will use recorded telemetry of these events to describe system response to EVA crew and ground actions. It will discuss the innovative design for redundancy of the integrated truss structure's cooling systems which allowed for this leak to be managed with minimal impact to other ISS operations and electrical services, contrasted against the real unintended operations consequences of utilizing the flexibility of the spacecraft's design in this manner. The paper will discuss how the training of the crew and flight controller personnel has adapted to the changing architecture of the power system and the unpredictable nature of the 2B leak.

Vareha, Anthony↗

NASA NTRS2012

VML 3.0 Reactive Sequencing Objects and Matrix Math Operations for Attitude Profiling

VML (Virtual Machine Language) has been used as the sequencing flight software on over a dozen JPL deep-space missions, most recently flying on GRAIL and JUNO. In conjunction with the NASA SBIR entitled "Reactive Rendezvous and Docking Sequencer", VML version 3.0 has been enhanced to include object-oriented element organization, built-in queuing operations, and sophisticated matrix / vector operations. These improvements allow VML scripts to easily perform much of the work that formerly would have required a great deal of expensive flight software development to realize. Autonomous turning and tracking makes considerable use of new VML features. Profiles generated by flight software are managed using object-oriented VML data constructs executed in discrete time by the VML flight software. VML vector and matrix operations provide the ability to calculate and supply quaternions to the attitude controller flight software which produces torque requests. Using VML-based attitude planning components eliminates flight software development effort, and reduces corresponding costs. In addition, the direct management of the quaternions allows turning and tracking to be tied in with sophisticated high-level VML state machines. These state machines provide autonomous management of spacecraft operations during critical tasks like a hypothetic Mars sample return rendezvous and docking. State machines created for autonomous science observations can also use this sort of attitude planning system, allowing heightened autonomy levels to reduce operations costs. VML state machines cannot be considered merely sequences - they are reactive logic constructs capable of autonomous decision making within a well-defined domain. The state machine approach enabled by VML 3.0 is progressing toward flight capability with a wide array of applicable mission activities.

VML (Virtual Machine Language)↗

NASA NTRS2013

An Operational Safety and Certification Assessment of a TASAR EFB Application

This paper presents an overview of a Traffic Aware Strategic Aircrew Requests (TASAR) Electronic Flight Bag application intended to inform the pilot of trajectory improvement opportunities while en route that result in operational benefits. The results of safety analyses and a detailed review of Federal Aviation Administration (FAA) regulatory documents that establish certification and operational approval requirements are presented for TASAR. The safety analyses indicate that TASAR has a likely Failure Effects Classification of “No Effect,” and at most, is no worse than “Minor Effect.” Based on this safety assessment and the detailed review of FAA regulatory documents that determine certification and operational approval requirements, this study concludes that TASAR can be implemented in the flight deck as a Type B software application hosted on a Class 2 Portable Electronic Device (PED) Electronic Flight Bag (EFB). This implementation approach would provide a relatively low-cost path to certification and operational approval for both retrofit and forward fit implementation, while at the same time facilitating the business case for early ADS-B IN equipage. A preliminary review by FAA certification and operational approvers of the analyses presented here confirmed that the conclusions are appropriate and that TASAR will be considered a Type B application.

Koczo, Stefan↗

NASA NTRS2014

Performance Comparison Between a Head-Worn Display System and a Head-Up Display for Low Visibility Commercial Operations

Research, development, test, and evaluation of flight deck interface technologies is being conducted by NASA to proactively identify, develop, and mature tools, methods, and technologies for improving overall aircraft safety of new and legacy vehicles operating in Next Generation Air Transportation System (NextGen). Under the Vehicle Systems Safety Technologies (VSST) project in the Aviation Safety Program, one specific area of research is the use of small Head-Worn Displays (HWDs) as an equivalent display to a Head-Up Display (HUD). Title 14 of the US Code of Federal Regulations (CFR) 91.175 describes a possible operational credit which can be obtained with airplane equipage of a HUD or an "equivalent" display combined with Enhanced Vision (EV). If successful, a HWD may provide the same safety and operational benefits as current HUD-equipped aircraft but for significantly more aircraft in which HUD installation is neither practical nor possible. A simulation experiment was conducted to evaluate if the HWD, coupled with a head-tracker, can provide an equivalent display to a HUD. Comparative testing was performed in the Research Flight Deck (RFD) Cockpit Motion Facility (CMF) full mission, motion-based simulator at NASA Langley. Twelve airline crews conducted approach and landing, taxi, and departure operations during low visibility operations (1000' Runway Visual Range (RVR), 300' RVR) at Memphis International Airport (Federal Aviation Administration (FAA) identifier: KMEM). The results showed that there were no statistical differences in the crews performance in terms of touchdown and takeoff. Further, there were no statistical differences between the HUD and HWD in pilots' responses to questionnaires.

Arthur, Jarvis J., III↗

NASA NTRS2014

Cost Analysis in a Multi-Mission Operations Environment

Spacecraft control centers have evolved from dedicated, single-mission or single mission-type support to multi-mission, service-oriented support for operating a variety of mission types. At the same time, available money for projects is shrinking and competition for new missions is increasing. These factors drive the need for an accurate and flexible model to support estimating service costs for new or extended missions; the cost model in turn drives the need for an accurate and efficient approach to service cost analysis. The National Aeronautics and Space Administration (NASA) Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center (MSFC) provides operations services to a variety of customers around the world. HOSC customers range from launch vehicle test flights; to International Space Station (ISS) payloads; to small, short duration missions; and has included long duration flagship missions. The HOSC recently completed a detailed analysis of service costs as part of the development of a complete service cost model. The cost analysis process required the team to address a number of issues. One of the primary issues involves the difficulty of reverse engineering individual mission costs in a highly efficient multi-mission environment, along with a related issue of the value of detailed metrics or data to the cost model versus the cost of obtaining accurate data. Another concern is the difficulty of balancing costs between missions of different types and size and extrapolating costs to different mission types. The cost analysis also had to address issues relating to providing shared, cloud-like services in a government environment, and then assigning an uncertainty or risk factor to cost estimates that are based on current technology, but will be executed using future technology. Finally the cost analysis needed to consider how to validate the resulting cost models taking into account the non-homogeneous nature of the available cost data and the decreasing flight rate. This paper presents the issues encountered during the HOSC cost analysis process, and the associated lessons learned. These lessons can be used when planning for a new multi-mission operations center or in the transformation from a dedicated control center to multi-center operations, as an aid in defining processes that support future cost analysis and estimation. The lessons can also be used by mature service-oriented, multi-mission control centers to streamline or refine their cost analysis process.

Felton, Larry↗

NASA NTRS2014

Space Mission Operations Ground Systems Integration Customer Service

The facility, which is now the Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center in Huntsville, AL, has provided continuous space mission and related services for the space industry since 1961, from Mercury Redstone through the International Space Station (ISS). Throughout the long history of the facility and mission support teams, the HOSC has developed a stellar customer support and service process. In this era, of cost cutting, and providing more capability and results with fewer resources, space missions are looking for the most efficient way to accomplish their objectives. One of the first services provided by the facility was fax transmission of documents to, then, Cape Canaveral in Florida. The headline in the Marshall Star, the newspaper for the newly formed Marshall Space Flight Center, read "Exact copies of Documents sent to Cape in 4 minutes." The customer was Dr. Wernher von Braun. Currently at the HOSC we are supporting, or have recently supported, missions ranging from simple ISS payloads requiring little more than "bentpipe" telemetry access, to a low cost free-flyer Fast, Affordable, Science and Technology Satellite (FASTSAT), to a full service ISS payload Alpha Magnetic Spectrometer 2 (AMS2) supporting 24/7 operations at three operations centers around the world with an investment of over 2 billion dollars. The HOSC has more need and desire than ever to provide fast and efficient customer service to support these missions. Here we will outline how our customer-centric service approach reduces the cost of providing services, makes it faster and easier than ever for new customers to get started with HOSC services, and show what the future holds for our space mission operations customers. We will discuss our philosophy concerning our responsibility and accessibility to a mission customer as well as how we deal with the following issues: initial contact with a customer, reducing customer cost, changing regulations and security, and cultural differences, to ensure an efficient response to customer issues using a small Customer Service Team (CST) and adaptability, constant communication with customers, technical expertise and knowledge of services, and dedication to customer service. The HOSC Customer Support Team has implemented a variety of processes, and procedures that help to mitigate the potential problems that arise when integrating ground system services for a variety of complex missions and the lessons learned from this experience will lead the future of customer service in the space operations industry.

Roth, Karl↗

NASA NTRS2014

Designing an Alternate Mission Operations Control Room

The Huntsville Operations Support Center (HOSC) is a multi-project facility that is responsible for 24x7 real-time International Space Station (ISS) payload operations management, integration, and control and has the capability to support small satellite projects and will provide real-time support for SLS launches. The HOSC is a service-oriented/ highly available operations center for ISS payloads-directly supporting science teams across the world responsible for the payloads. The HOSC is required to endure an annual 2-day power outage event for facility preventive maintenance and safety inspection of the core electro-mechanical systems. While complete system shut-downs are against the grain of a highly available sub-system, the entire facility must be powered down for a weekend for environmental and safety purposes. The consequence of this ground system outage is far reaching: any science performed on ISS during this outage weekend is lost. Engineering efforts were focused to maximize the ISS investment by engineering a suitable solution capable of continuing HOSC services while supporting safety requirements. The HOSC Power Outage Contingency (HPOC) System is a physically diversified compliment of systems capable of providing identified real-time services for the duration of a planned power outage condition from an alternate control room. HPOC was designed to maintain ISS payload operations for approximately three continuous days during planned HOSC power outages and support a local Payload Operations Team, International Partners, as well as remote users from the alternate control room located in another building.

Montgomery, Patty↗

NASA NTRS2014

Cost Analysis In A Multi-Mission Operations Environment

Spacecraft control centers have evolved from dedicated, single-mission or single missiontype support to multi-mission, service-oriented support for operating a variety of mission types. At the same time, available money for projects is shrinking and competition for new missions is increasing. These factors drive the need for an accurate and flexible model to support estimating service costs for new or extended missions; the cost model in turn drives the need for an accurate and efficient approach to service cost analysis. The National Aeronautics and Space Administration (NASA) Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center (MSFC) provides operations services to a variety of customers around the world. HOSC customers range from launch vehicle test flights; to International Space Station (ISS) payloads; to small, short duration missions; and has included long duration flagship missions. The HOSC recently completed a detailed analysis of service costs as part of the development of a complete service cost model. The cost analysis process required the team to address a number of issues. One of the primary issues involves the difficulty of reverse engineering individual mission costs in a highly efficient multimission environment, along with a related issue of the value of detailed metrics or data to the cost model versus the cost of obtaining accurate data. Another concern is the difficulty of balancing costs between missions of different types and size and extrapolating costs to different mission types. The cost analysis also had to address issues relating to providing shared, cloud-like services in a government environment, and then assigning an uncertainty or risk factor to cost estimates that are based on current technology, but will be executed using future technology. Finally the cost analysis needed to consider how to validate the resulting cost models taking into account the non-homogeneous nature of the available cost data and the decreasing flight rate. This paper presents the issues encountered during the HOSC cost analysis process, and the associated lessons learned. These lessons can be used when planning for a new multi-mission operations center or in the transformation from a dedicated control center to multi-center operations, as an aid in defining processes that support future cost analysis and estimation. The lessons can also be used by mature serviceoriented, multi-mission control centers to streamline or refine their cost analysis process.

Newhouse, M.↗

NASA NTRS2014

An Overview of the Concept of Operations for Assembly, Integration, Testing and Ground Servicing Developed for the MPCV-ESM Propulsion System

A concept of operations for the Assembly, Integration and Testing (AIT) and the Ground Systems Development Operations (GSDO) of the European Service Module (ESM) propulsion system has been developed. The AIT concept of operations covers all fabrication, integration and testing activities in both Europe and in the United States. The GSDO Program develops the facilities, equipment, and procedures for the loading of hypergolic propellants, the filling of high-pressure gases, and contingency de-servicing operations for the ESM. NASA and ESA along with the Lockheed Martin and Airbus Space and Defense are currently working together for the EM-1 and EM-2 missions in which the ESM will be flown as part of the Orion Multi-Purpose Crew Vehicle (MPCV). The NASA/ESA SM propulsion team is collaborating with the AIT personnel from ESA/Airbus and NASA/Lockheed Martin to ensure successful integration of the European designed Service Module propulsion system, the Lockheed Martin designed Crew Module Adapter and the heritage Space Shuttle Orbital Maneuvering System Engines (OMS-E) being provided as Government Furnished Equipment (GFE). This paper will provide an overview of the current AIT and GSDO concept of operations for the ESM propulsion system.

Propulsion↗

NASA NTRS2014

An Overview of the Concept of Operations for Assembly, Integration, Testing and Ground Servicing Developed for the MPCV-ESM Propulsion System

Ground Servicing↗

NASA NTRS2013

Modeling Operations Costs for Human Exploration Architectures

Operations and support (O&S) costs for human spaceflight have not received the same attention in the cost estimating community as have development costs. This is unfortunate as O&S costs typically comprise a majority of life-cycle costs (LCC) in such programs as the International Space Station (ISS) and the now-cancelled Constellation Program. Recognizing this, the Constellation Program and NASA HQs supported the development of an O&S cost model specifically for human spaceflight. This model, known as the Exploration Architectures Operations Cost Model (ExAOCM), provided the operations cost estimates for a variety of alternative human missions to the moon, Mars, and Near-Earth Objects (NEOs) in architectural studies. ExAOCM is philosophically based on the DoD Architecture Framework (DoDAF) concepts of operational nodes, systems, operational functions, and milestones. This paper presents some of the historical background surrounding the development of the model, and discusses the underlying structure, its unusual user interface, and lastly, previous examples of its use in the aforementioned architectural studies.

cost estimating↗

NASA NTRS2012

Launch Pad Closeout Operations for the Mars Science Laboratory's Heat Rejection System

The Mars Science Laboratory (MSL) rover was launched on an Atlas V on November 26, 2011. Preparations were carried out prior to launch in order to closeout the spacecraft's complex heat rejection system (HRS), which consists of two mechanically pumped CFC-11 fluid loops. The first HRS loop, onboard the Curiosity rover, was fully integrated, filled with CFC-11, and successfully operated prior to launch pad operations; however, the second thermal loop, called the cruise HRS loop, required final mechanical and thermal integration activities to occur while on the launch pad in order to accommodate the last minute installation of the rover's Multi-Mission Radioisotope Thermoelectric Generator (MMRTG) power source. In order to prevent overheating of propellant tanks and critical avionics equipment buried deep within the spacecraft's aeroshell, the MMRTG needed to be pre-cooled using a separate non-flight mechanically pumped fluid loop prior to and during the final closeout and subsequent startup of the flight loop. This paper outlines the various steps that took place to safely install the MMRTG while carefully transitioning from the pre-cooling operation to the final startup and operation of the flight cruise HRS loop. Temperature data of the launch pad thermal transition from the ground support loop activity to the final flight loop operation is presented. Some background development of the ground support loop and lessons learned are also discussed. This successful launch pad integration activity required a close-knit coordination between NASA KSC, JPL, the Department of Energy, Idaho National Labs, Pratt and Whitney Rocketdyne Inc., Teledyne Technologies Inc., ULA, and Advanced Thermal Sciences Corp.

thermal↗

NASA NTRS2010

Moving Toward Space Internetworking via DTN: Its Operational Challenges, Benefits, and Management

The international space community has begun to recognize that the established model for management of communications with spacecraft - commanded data transmission over individual pair-wise contacts - is operationally unwieldy and will not scale in support of increasingly complex and sophisticated missions such as NASA's Constellation project. Accordingly, the international Inter-Agency Operations Advisory Group (IOAG) ichartered a Space Internetworking Strategy Group (SISG), which released its initial recommendations in a November 2008 report. The report includes a recommendation that the space flight community adopt Delay-Tolerant Networking (DTN) to address the problem of interoperability and communication scaling, especially in mission environments where there are multiple spacecraft operating in concert. This paper explores some of the issues that must be addressed in implementing, deploying, and operating DTN as part of a multi-mission, multi-agency space internetwork as well as benefits and future operational scenarios afforded by DTN-based space internetworking.

Delay Tolerant Networking↗

NASA NTRS2016

Analog Testing of Operations Concepts for Mitigation of Communication Latency During Human Space Exploration

OBJECTIVES: NASA Extreme Environment Mission Operations (NEEMO) is an underwater spaceflight analog that allows a true mission‐like operational environment and uses buoyancy effects and added weight to simulate different gravity levels. Three missions were undertaken from 2014‐2015, NEEMO's 18‐20. All missions were performed at the Aquarius undersea research habitat. During each mission, the effects of varying operations concepts and tasks type and complexity on representative communication latencies associated with Mars missions were studied. METHODS: 12 subjects (4 per mission) were weighed out to simulate near‐zero or partial gravity extravehicular activity (EVA) and evaluated different operations concepts for integration and management of a simulated Earth‐based science backroom team (SBT) to provide input and direction during exploration activities. Exploration traverses were planned in advance based on precursor data collected. Subjects completed science‐related tasks including presampling surveys, geologic‐based sampling, and marine‐based sampling as a portion of their tasks on saturation dives up to 4 hours in duration that were to simulate extravehicular activity (EVA) on Mars or the moons of Mars. One‐way communication latencies, 5 and 10 minutes between space and mission control, were simulated throughout the missions. Objective data included task completion times, total EVA times, crew idle time, translation time, SBT assimilation time (defined as time available for SBT to discuss data/imagery after it has been collected, in addition to the time taken to watch imagery streaming over latency). Subjective data included acceptability, simulation quality, capability assessment ratings, and comments. RESULTS: Precursor data can be used effectively to plan and execute exploration traverse EVAs (plans included detailed location of science sites, high‐fidelity imagery of the sites, and directions to landmarks of interest within a site). Operations concepts that allow for presampling surveys enable efficient traverse execution and meaningful Mission Control Center (MCC) interaction across long communication latencies and can be done with minimal crew idle time. Imagery and information from the EVA crew that is transmitted real‐time to the intravehicular (IV) crewmember(s) can be used to verify that exploration traverse plans are being executed correctly. That same data can be effectively used by MCC (across comm latency) to provide further instructions to the crew from a SBT on sampling priorities, additional tasks, and changes to the plan. Text / data capabilities are preferred over voice capabilities between MCC and IV when executing exploration traverse plans over communication latency. Autonomous crew planning tools can be effective at modifying existing plans if the objectives and constraints are clearly defined.

Chappell, Steven P.↗