Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Concept of 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.

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

At least 757 records · Page 42

Pilot and Controller Evaluations of Separation Function Allocation in Air Traffic Management

Two human-in-the-loop simulation experiments were conducted in coordinated fashion to investigate the allocation of separation assurance functions between ground and air and between humans and automation. The experiments modeled a mixed-operations concept in which aircraft receiving ground-based separation services shared the airspace with aircraft providing their own separation service (i.e., self-separation). Ground-based separation was provided by air traffic controllers without automation tools, with tools, or by ground-based automation with controllers in a managing role. Airborne self-separation was provided by airline pilots using self-separation automation enabled by airborne surveillance technology. The two experiments, one pilot-focused and the other controller-focused, addressed selected key issues of mixed operations, assuming the starting point of current-day operations and modeling an emergence of NextGen technologies and procedures. In the controller-focused experiment, the impact of mixed operations on controller performance was assessed at four stages of NextGen implementation. In the pilot-focused experiment, the limits to which pilots with automation tools could take full responsibility for separation from ground-controlled aircraft were tested. Results indicate that the presence of self-separating aircraft had little impact on the controllers' ability to provide separation services for ground-controlled aircraft. Overall performance was best in the most automated environment in which all aircraft were data communications equipped, ground-based separation was highly automated, and self-separating aircraft had access to trajectory intent information for all aircraft. In this environment, safe, efficient, and highly acceptable operations could be achieved for twice today's peak airspace throughput. In less automated environments, reduced trajectory intent exchange and manual air traffic control limited the safely achievable airspace throughput and negatively impacted the maneuver efficiency of self-separating aircraft through high-density airspace. In a test of scripted conflicts with ground-managed aircraft, flight crews of self-separating aircraft prevented separation loss in all conflicts with detection time greater than one minute. In debrief, pilots indicated a preference for at least five minute's alerting notice and trajectory intent information on all aircraft. When intent information on ground-managed aircraft was available, self-separating aircraft benefited from fewer conflict alerts and fewer required deviations from trajectory-based operations.

Wing, David↗

Web Based Tool for Mission Operations Scenarios

A conventional practice for spaceflight projects is to document scenarios in a monolithic Operations Concept document. Such documents can be hundreds of pages long and may require laborious updates. Software development practice utilizes scenarios in the form of smaller, individual use cases, which are often structured and managed using UML. We have developed a process and a web-based scenario tool that utilizes a similar philosophy of smaller, more compact scenarios (but avoids the formality of UML). The need for a scenario process and tool became apparent during the authors' work on a large astrophysics mission. It was noted that every phase of the Mission (e.g., formulation, design, verification and validation, and operations) looked back to scenarios to assess completeness of requirements and design. It was also noted that terminology needed to be clarified and structured to assure communication across all levels of the project. Attempts to manage, communicate, and evolve scenarios at all levels of a project using conventional tools (e.g., Excel) and methods (Scenario Working Group meetings) were not effective given limitations on budget and staffing. The objective of this paper is to document the scenario process and tool created to offer projects a low-cost capability to create, communicate, manage, and evolve scenarios throughout project development. The process and tool have the further benefit of allowing the association of requirements with particular scenarios, establishing and viewing relationships between higher- and lower-level scenarios, and the ability to place all scenarios in a shared context. The resulting structured set of scenarios is widely visible (using a web browser), easily updated, and can be searched according to various criteria including the level (e.g., Project, System, and Team) and Mission Phase. Scenarios are maintained in a web-accessible environment that provides a structured set of scenario fields and allows for maximum visibility across the project. One key aspect is that the tool was built for a scenario process that accounts for stakeholder input, review, comment, and concurrence. By creating well-designed opportunities for stakeholder input and concurrence and by making the scenario content easily accessible to all project personnel, we maximize the opportunities for stakeholders to both understand and agree on the concepts for how their mission is to be carried out.

Boyles, Carole A.↗

ION Work Reduction Opportunity Realization Demonstration

The purpose of this research was to realize one of the advanced training work reduction opportunities first presented in the Idaho National Laboratory (INL) report, “Process for Significant Nuclear Work Function Innovation Based on Integrated Operations Concepts” (INL/EXT-21-64134) [1], with a nuclear power plant (NPP) research partner. Researchers modernized two trainings: (1) an accredited instructor-led training (ILT) overview course on Westinghouse DS 480-volt (V) circuit breakers to a multimedia-focused computer-based-training (CBT) learning module, and (2) an on-demand chaptered video on how to properly rack and un-rack a Westinghouse DS 480-V circuit breaker. These modernized work products were developed and implemented in a manner consistent with the industry guidelines found in Institution of Nuclear Power Operations (INPO) Teaching and Learning 23-001 [2]. Researchers calculated that the modernized accredited training course reduced the time necessary to prepare and deliver the training material by a factor of 8:1. The amount of time learners spend in class could be reduced by this same factor. In other words, if a course took 8 hours to deliver a class, the new CBT instruction would take just over 1 hour. The researchers noted that the requirement for any practicum training by the learners with the instructor(s) would remain in place. But through interviews with new and experienced learners, the researchers discovered that the confidence of these learners in performing the racking and un-racking of the circuit breaker improved as a result of using the new modernized CBT process. Additionally, the learners who tested the modernized work products enjoyed the modernized CBT and the learning video significantly more than current in-class learning methods. These are encouraging results for the nuclear industry, as this modernization of training can be applied to other classes and is scalable across the industry. In line with the Integrated Operations for Nuclear (ION) model, positive workload analysis supports the investment of resources in modernizing NPP training processes and infrastructure. Implementation of the advanced training technologies in this report is likely to result in substantive long-term workload benefits to instructors and learners and result in hard-dollar savings on contractor spends. Additionally, investment in these modernized training processes will result in improved learner proficiency. The results of this research can be applied to additional operator, technical, and general training topics to provide additional workload and learning benefits in addition to what was explored.

42 ENGINEERING↗

The development of the Canadian Mobile Servicing System Kinematic Simulation Facility

Canada will develop a Mobile Servicing System (MSS) as its contribution to the U.S./International Space Station Freedom. Components of the MSS will include a remote manipulator (SSRMS), a Special Purpose Dexterous Manipulator (SPDM), and a mobile base (MRS). In order to support requirements analysis and the evaluation of operational concepts related to the use of the MSS, a graphics based kinematic simulation/human-computer interface facility has been created. The facility consists of the following elements: (1) A two-dimensional graphics editor allowing the rapid development of virtual control stations; (2) Kinematic simulations of the space station remote manipulators (SSRMS and SPDM), and mobile base; and (3) A three-dimensional graphics model of the space station, MSS, orbiter, and payloads. These software elements combined with state of the art computer graphics hardware provide the capability to prototype MSS workstations, evaluate MSS operational capabilities, and investigate the human-computer interface in an interactive simulation environment. The graphics technology involved in the development and use of this facility is described.

Beyer, G.↗

Constellation's Command, Control, Communications and Information (C3I) Architecture

Operations concepts are highly effective for: 1) Developing consensus; 2) Discovering stakeholder needs, goals, objectives; 3) Defining behavior of system components (especially emergent behaviors). An interoperability standard can provide an excellent lever to define the capabilities needed for system evolution. Two categories of architectures are needed in a program of this size are: 1) Generic - Needed for planning, design and construction standards; 2) Specific - Needed for detailed requirement allocations, interface specs. A wide variety of architectural views are needed to address stakeholder concerns, including: 1) Physical; 2) Information (structure, flow, evolution); 3) Processes (design, manufacturing, operations); 4) Performance; 5) Risk.

constellation↗

Overview of a Preliminary Destination Mission Concept for a Human Orbital Mission to the Martial Moons

The National Aeronautics and Space Administration s Human Spaceflight Architecture Team (HAT) has been developing a preliminary Destination Mission Concept (DMC) to assess how a human orbital mission to one or both of the Martian moons, Phobos and Deimos, might be conducted as a follow-on to a human mission to a near-Earth asteroid (NEA) and as a possible preliminary step prior to a human landing on Mars. The HAT Mars-Phobos-Deimos (MPD) mission also permits the teleoperation of robotic systems by the crew while in the Mars system. The DMC development activity provides an initial effort to identify the science and exploration objectives and investigate the capabilities and operations concepts required for a human orbital mission to the Mars system. In addition, the MPD Team identified potential synergistic opportunities via prior exploration of other destinations currently under consideration.

Mazanek, D. D.↗

Real Time Metrics and Analysis of Integrated Arrival, Departure, and Surface Operations

To address the Integrated Arrival, Departure, and Surface (IADS) challenge, NASA is developing and demonstrating trajectory-based departure automation under a collaborative effort with the FAA and industry known Airspace Technology Demonstration 2 (ATD-2). ATD-2 builds upon and integrates previous NASA research capabilities that include the Spot and Runway Departure Advisor (SARDA), the Precision Departure Release Capability (PDRC), and the Terminal Sequencing and Spacing (TSAS) capability. As trajectory-based departure scheduling and collaborative decision making tools are introduced in order to reduce delays and uncertainties in taxi and climb operations across the National Airspace System, users of the tools across a number of roles benefit from a real time system that enables common situational awareness. A real time dashboard was developed to inform and present users notifications and integrated information regarding airport surface operations. The dashboard is a supplement to capabilities and tools that incorporate arrival, departure, and surface air-traffic operations concepts in a NextGen environment. In addition to shared situational awareness, the dashboard offers the ability to compute real time metrics and analysis to inform users about capacity, predictability, and efficiency of the system as a whole. This paper describes the architecture of the real time dashboard as well as an initial proposed set of metrics. The potential impact of the real time dashboard is studied at the site identified for initial deployment and demonstration in 2017: Charlotte-Douglas International Airport (CLT). The architecture of implementing such a tool as well as potential uses are presented for operations at CLT. Metrics computed in real time illustrate the opportunity to provide common situational awareness and inform users of system delay, throughput, taxi time, and airport capacity. In addition, common awareness of delays and the impact of takeoff and departure restrictions stemming from traffic flow management initiatives are explored. The potential of the real time tool to inform users of the predictability and efficiency of using a trajectory-based departure scheduling system is also discussed.

integrated arrival departure surface operations↗

Operational Impact of the Baseline Integrated Arrival, Departure and Surface System Field Demonstration

To address the Integrated Arrival, Departure, and Surface (IADS) challenge, NASA is developing and demonstrating trajectory-based departure automation under a collaborative effort with the FAA (Federal Aviation Administration) and industry known Airspace Technology Demonstration 2 (ATD-2). ATD-2 builds upon and integrates previous NASA research capabilities that include the Spot and Runway Departure Advisor (SARDA), the Precision Departure Release Capability (PDRC), and the Terminal Sequencing and Spacing (TSAS) capability. As trajectory-based departure scheduling and collaborative decision making tools are introduced in order to reduce delays and uncertainties in taxi and climb operations across the National Airspace System, users of the tools across a number of roles benefit from a real time system that enables common situational awareness. A real time dashboard was developed to inform and present users notifications and integrated information regarding airport surface operations. The dashboard is a supplement to capabilities and tools that incorporate arrival, departure, and surface air-traffic operations concepts in a NextGen environment. In addition to shared situational awareness, the dashboard offers the ability to compute real time metrics and analysis to inform users about capacity, predictability, and efficiency of the system as a whole. This paper describes the architecture of the real time dashboard as well as an initial proposed set of metrics. The potential impact of the real time dashboard is studied at the site identified for initial deployment and demonstration in 2017: Charlotte-Douglas International Airport (CLT). The architecture of implementing such a tool as well as potential uses are presented for operations at CLT. Metrics computed in real time illustrate the opportunity to provide common situational awareness and inform users of system delay, throughput, taxi time, and airport capacity. In addition, common awareness of delays and the impact of takeoff and departure restrictions stemming from traffic flow management initiatives are explored. The potential of the real time tool to inform users of the predictability and efficiency of using a trajectory-based departure scheduling system is also discussed.

air traffic optimization↗

Silent Aircraft Initiative Concept Risk Assessment

A risk assessment of the Silent Aircraft Initiative's SAX-40 concept design for extremely low noise has been performed. A NASA team developed a list of 27 risk items, and evaluated the level of risk for each item in terms of the likelihood that the risk would occur and the consequences of the occurrence. The following risk items were identified as high risk, meaning that the combination of likelihood and consequence put them into the top one-fourth of the risk matrix: structures and weight prediction; boundary-layer ingestion (BLI) and inlet design; variable-area exhaust and thrust vectoring; displaced-threshold and continuous descent approach (CDA) operational concepts; cost; human factors; and overall noise performance. Several advanced-technology baseline concepts were created to serve as a basis for comparison to the SAX-40 concept. These comparisons indicate that the SAX-40 would have significantly greater research, development, test, and engineering (RDT&E) and production costs than a conventional aircraft with similar technology levels. Therefore, the cost of obtaining the extremely low noise capability that has been estimated for the SAX-40 is significant. The SAX-40 concept design proved successful in focusing attention toward low noise technologies and in raising public awareness of the issue.

Nickol, Craig L.↗

Landsat Instrument Suite (LandIS) Sensor Design for the Landsat 10 Mission

Landsat 10 will be the upcoming mission in the 50+ year Landsat series of Earth observation platforms. The centerpiece of the observatory will be a super-spectral imager known as the Landsat Instrument Suite (LandIS). The sensor will feature 26 spectral channels from the visible through near-, short-wave, and thermal infrared wavelengths with spatial resolutions of 10, 20, and 60 meters on the ground, depending on the band. These enhancements over the legacy Landsat instruments will ensure data continuity with the existing archive and will expand upon the core Landsat capabilities to enable new applications in Earth science. After a competitive procurement, NASA selected the design submitted by the Raytheon Company for the LandIS instrument. The innovative Raytheon instrument concept utilizes an advanced whiskbroom architecture to fulfill the strict radiometric, spatial, and geometric image quality requirements demanded by the Landsat 10 mission and fits within restrictive mass, volume, and power constraints. The instrument will continue the Landsat directive to image all daylit land and near-shore water areas, along with select nighttime imaging. On-board calibration source data will ensure high radiometric and geometric accuracy and stability consistent with previous missions to enable continuity in data products available to users. This paper discusses the driving requirements for LandIS and provides a description of the chosen design and operations concept of the instrument.

Requirements↗

Development of a Ground Test and Analysis Protocol to Support NASA's NextSTEP Phase 2 Habitation Concepts

The NASA Next Space Technologies for Exploration Partnerships (NextSTEP) program is a public-private partnership model that seeks commercial development of deep space exploration capabilities to support extensive human spaceflight missions around and beyond cislunar space. NASA first issued the Phase 1 NextSTEP Broad Agency Announcement to U.S. industries in 2014, which called for innovative cislunar habitation concepts that leveraged commercialization plans for low Earth orbit. These habitats will be part of the Deep Space Gateway (DSG), the cislunar space station planned by NASA for construction in the 2020s. In 2016, Phase 2 of the NextSTEP program selected five commercial partners to develop ground prototypes. A team of NASA research engineers and subject matter experts have been tasked with developing the ground test protocol that will serve as the primary means by which these Phase 2 prototype habitats will be evaluated. Since 2008, this core test team has successfully conducted multiple spaceflight analog mission evaluations utilizing a consistent set of operational products, tools, methods, and metrics to enable the iterative development, testing, analysis, and validation of evolving exploration architectures, operations concepts, and vehicle designs. The purpose of implementing a similar evaluation process for the NextSTEP Phase 2 Habitation Concepts is to consistently evaluate the different commercial partner ground prototypes to provide data-driven, actionable recommendations for Phase 3.

Beaton, Kara H.↗

Automating Maneuvers: Considerations for Collision Avoidance

As more space operators implement large constellations of spacecraft, automating orbit maintenance maneuvers becomes a key feature of their operations concept to ensure that the workload is manageable. However the practice of performing a maneuver without sharing the plan with other nearby spacecraft causes a risk that two spacecraft will collide, not only destroying the spacecraft involved, but creating debris that will affect all other spacecraft using that orbit regime. In order to share the maneuver plan, a predicted ephemeris file containing the maneuver must be sent to a central authority to screen against predicted trajectories of all other on-orbit objects to determine where and when close approaches may occur that need to be mitigated. Currently the screening authority used by US operators is the 19th Space Defense Squadron. However the conjunction screening process in use by the 19th was developed over 30 years ago and was not designed with automation in mind, so screenings are performed once every 8 hours, meaning that spacecraft using automated maneuvering need to allow 16 hours to share their maneuver plan via the screening process. Many operators assume that automated maneuver planning must be real-time; however this time between planning and execution to allow for screening is possible if planned for during system design. In an effort to speed up the screening process, NASA has developed a prototype system for performing near-real-time screenings. This prototype system was necessitated to support the NASA Starling mission, a constellation of 4 cubesats that planned to fly at the same altitude as the SpaceX Starlink constellation, both performing automated maneuvering. Without screening of the planned maneuvers, the two constellations risked a collision. Once converted from a prototype to an operational system, this capability will greatly help smallsats, for example those that are planning to test propulsive capabilities, by allowing fast turnaround feedback to ensure safety form collision with other objects. This paper describes the existing CA process, the prototype real-time capability, and results from the experiment that tested the prototype.

Matthew Hejduk↗

Concepts, requirements, and design approaches for building successful planning and scheduling systems

Traditional practice of systems engineering management assumes requirements can be precisely determined and unambiguously defined prior to system design and implementation; practice further assumes requirements are held static during implementation. Human-computer decision support systems for service planning and scheduling applications do not conform well to these assumptions. Adaptation to the traditional practice of systems engineering management are required. Basic technology exists to support these adaptations. Additional innovations must be encouraged and nutured. Continued partnership between the programmatic and technical perspective assures proper balance of the impossible with the possible. Past problems have the following origins: not recognizing the unusual and perverse nature of the requirements for planning and scheduling; not recognizing the best starting point assumptions for the design; not understanding the type of system that being built; and not understanding the design consequences of the operations concept selected.

Hornstein, Rhoda Shaller↗

Automating Maneuvers: Considerations for Collision Avoidance

As more space operators implement large constellations of spacecraft, automating orbit maintenance maneuvers becomes a key feature of their operations concept to ensure that the workload is manageable. However, the practice of performing a maneuver without sharing the plan with other nearby spacecraft causes a risk that two spacecraft will collide, not only destroying the spacecraft involved, but creating debris that will affect all other spacecraft using that orbit regime. In order to share the maneuver plan, a predicted ephemeris file containing the maneuver must be sent to a central authority to screen against predicted trajectories of all other on-orbit objects to determine where and when close approaches will occur that may need to be mitigated. Currently the screening authority used by US operators is the 19th Space Defense Squadron; screenings are performed once every 8 hours, meaning that spacecraft using automated maneuvering need to allow 16 hours to share their maneuver plan via the screening process in advance of maneuver execution in case one screening is missed and the next needs to be used. In an effort to speed up the screening process to benefit spacecraft using automated maneuvering, a prototype system for performing near-real-time screenings has been developed in support of the NASA Starling mission, a constellation of four cubesats that fly at the same altitude as the SpaceX Starlink constellation. Both of these constellations perform automated maneuvering, so without screening the planned maneuvers before execution, the two constellations would risk a collision. This paper describes the traditional conjunction assessment (CA) process, the prototype real-time CA screening capability, plans for the experiment to test the prototype, and next steps.

conjunction assessment↗

Automating Maneuvers: Considerations for Collision Avoidance

As more space operators implement large constellations of spacecraft, automating orbit maintenance maneuvers becomes a key feature of their operations concept to ensure that the workload is manageable. However, the practice of performing a maneuver without sharing the plan with other nearby spacecraft causes a risk that two spacecraft will collide, not only destroying the spacecraft involved, but creating debris that will affect all other spacecraft using that orbit regime. In order to share the maneuver plan, a predicted ephemeris file containing the maneuver must be sent to a central authority to screen against predicted trajectories of all other on-orbit objects to determine where and when close approaches will occur that may need to be mitigated. Currently the screening authority used by US operators is the 19th Space Defense Squadron; screenings are performed once every 8 hours, meaning that spacecraft using automated maneuvering need to allow 16 hours to share their maneuver plan via the screening process in advance of maneuver execution in case one screening is missed and the next needs to be used. In an effort to speed up the screening process to benefit spacecraft using automated maneuvering, a prototype system for performing near-real-time screenings has been developed in support of the NASA Starling mission, a constellation of four cubesats that fly at the same altitude as the SpaceX Starlink constellation. Both of these constellations perform automated maneuvering, so without screening the planned maneuvers before execution, the two constellations would risk a collision. This paper describes the traditional conjunction assessment (CA) process, the prototype real-time CA screening capability, plans for the experiment to test the prototype, and next steps.

conjunction assessment↗

Common Lunar Lander vehicle propulsion system conceptual design

The Common Lunar Lander (CLL) is a concept for a small, unpiloted vehicle which would provide a low-cost capability to land any of a variety of payloads in the 200 kg class at any point on the surface of the moon. Initiated as a precursor mission for the First Lunar Outpost, it also has considerable potential for use by the scientific community at large. A series of studies has been conducted at the NASA Johnson Space Center to define initial requirements and to initiate the design process. This paper describes the propulsion subsystem design as it existed at the CLL System Design Review. The propulsion subsystem design is described in detail along with the planned operations concept, including the unique concept of using pulsing of main engines for thrust modulation. Design options and trades considered and the verification process philosophy which was being planned for the program are discussed.

Hyatt, C. D.↗

TPSAS-NF1676L-12387-DND

Fast-time wake prediction models are semi-empirical, and are designed to predict aircraft wake vortex information behind a generating aircraft. They are developed using theoretical concepts and often calibrated with data obtained from field measurements, laboratory studies, or numerical simulations. They rely upon inputs representing the generating aircraft (such as weight, airspeed, wingspan, lateral position, and altitude) and atmospheric environment (such as ambient winds, turbulence, and temperature lapse rate). Other input may include the type of aircraft (e.g., B-747- 400). Output from these models may include time histories of the wake vortex strength, and position, as well as a prediction of the uncertainties in strength and position. Fast-time models should provide solutions in a fraction of a second, and hence is an enabling technology able to perform in a real-time operational system, such as dynamic spacing systems envisioned by the Aircraft Vortex Spacing System or other Super Density Operations concepts. Other applications of fast-time models include 1) guidance for wake separation standards for new aircraft, 2) optimization of separation standards for existing aircraft, 3) guidance for setting vertical separation standards during cruise, 4) accident reconstructions, and 5) testing of new concepts for safe increases in airport capacity for both single and multiple runway configurations. Fast-time models are based on a number of assumptions which limit their accuracy and range of application. For example, they do not predict the meandering vortex paths that can result from the wake interaction with atmospheric turbulence. However, these models should account for the mean vortex position and may predict the level of uncertainty. This presentation describes a study in which comparative evaluations of fast-time wake transport and decay models were conducted using data sets from previous field programs taken at MEM (1995), DFW (1997, 1999, 2000), and Denver (2005, 2006) airports. These data sets contain, meteorological data, lidar measurements of wake vortices, and the aircraft parameters associated with these vortices.

Fred H Proctor↗

Large Interferometer For Exoplanets (LIFE) XIII. The value of Combining Thermal Emission and Reflected Light for the Characterization of Earth Twins

Context. Following the recommendations to NASA (in the Astro2020 Decadal survey) and ESA (through the Voyage2050 process), the search for life on exoplanets will be a priority in the next decades. Two concepts for direct imaging space missions are being developed for this purpose: the Habitable Worlds Observatory (HWO) and the Large Interferometer for Exoplanets (LIFE). These two concepts operate in different spectral regimes: HWO is focused on reflected light spectra in the ultraviolet, visible, and near-infrared (UV/VIS/NIR), while LIFE will operate in the mid-infrared (MIR) to capture the thermal emission of temperate exoplanets. Aims. In this study, we aim to assess the potential of HWO and LIFE to characterize a cloud-free Earth twin orbiting a Sun-like star at a distance of 10 pc, both as separate missions and in synergy with each other. We aim to quantify the increase in information that can be gathered by joint atmospheric retrievals on a habitable planet. Methods. We performed Bayesian retrievals on simulated data obtained by an HWO-like mission and a LIFE-like one separately, then jointly. We considered the baseline spectral resolutions currently assumed for these concepts and used two increasingly complex noise simulations, obtained using state-of-the-art noise simulators. Results. An HWO-like concept would allow one to strongly constrain H 2 O, O 2 , and O 3 in the atmosphere of a cloud-free Earth twin, while the atmospheric temperature profile is not well constrained (with an average uncertainty ≈100 K). LIFE-like observations would strongly constrain CO 2 , H 2 O, and O 3 and provide stronger constraints on the thermal atmospheric structure and surface temperature (down to ≈10 K uncertainty). For all the investigated scenarios, both missions would provide an upper limit on CH 4 . A joint retrieval on HWO and LIFE data would accurately define the atmospheric thermal profile and planetary parameters. It would decisively constrain CO 2 , H 2 O, O 2 , and O 3 and find weak constraints on CO and CH 4 . The significance of the detection is in all cases greater than or equal to the single-instrument retrievals. Conclusions. Both missions provide specific information that is relevant for the characterization of a terrestrial habitable exoplanet, but the scientific yield can be maximized by considering synergistic studies of UV/VIS/NIR+MIR observations. The use of HWO and LIFE together will provide stronger constraints on biosignatures and life indicators, with the potential to be transformative for the search for life in the Universe.

E Alei↗