Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “conops”

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 217 records · Page 12

An in-Time Aviation Safety Management System Concept of Operations and Modernization of the National Airspace System

The National Airspace System (NAS) is growing in complexity of aircraft, missions, and operations. In response, many organizations have published papers and concepts of operations (ConOps) for new and enhanced safety systems. The National Academies’ vision for an In-time Aviation Safety Management System (IASMS) is integral to Federal Aviation Administration (FAA) modernization efforts. The National Aeronautics and Space Administration (NASA) System-Wide Safety (SWS) project is conducting safety research, exploring solutions, and defining the safety needs of future missions, such as Advanced Air Mobility (AAM) and autonomous aircraft operating in a more connected, flexible, and dynamic airspace. IASMS enables and provides a path for bringing FAA’s operational vision to fruition through increasingly automated safety systems that integrate services, functions, and capabilities (SFCs). These SFCs provide the necessary responsiveness to monitor, assess, and mitigate known hazards and emergent risks. This paper describes how safety in today’s air transportation system will need to evolve, identifies key points regarding in-time safety, and explores the criticality of IASMS in the future NAS.

IASMS↗

An In-time Aviation Safety Management System Concept of Operations and Modernization of the National Airspace System​

The National Airspace System (NAS) is growing in complexity of aircraft, missions, and operations. In response, many organizations have published papers and concepts of operations (ConOps) for new and enhanced safety systems. The National Academies’ vision for an In-time Aviation Safety Management System (IASMS) is integral to Federal Aviation Administration (FAA) modernization efforts. The National Aeronautics and Space Administration (NASA) System-Wide Safety (SWS) project is conducting safety research, exploring solutions, and defining the safety needs of future missions, such as Advanced Air Mobility (AAM) and autonomous aircraft operating in a more connected, flexible, and dynamic airspace. IASMS enables and provides a path for bringing FAA’s operational vision to fruition through increasingly automated safety systems that integrate services, functions, and capabilities (SFCs). These SFCs provide the necessary responsiveness to monitor, assess, and mitigate known hazards and emergent risks. This paper describes how safety in today’s air transportation system will need to evolve, identifies key points regarding in-time safety, and explores the criticality of IASMS in the future NAS.

Airspace↗

Provider of Services for Urban Air Mobility (PSU) Prototype Simulation (X5) Final Report

Urban Air Mobility (UAM) is a new air transportation service concept to carry passengers or cargo in metropolitan areas, leveraged by innovative aircraft and air traffic automation technologies. NASA has conducted a series of simulations, called the X-series simulation, to evaluate the UAM concept of operations and support the development of airspace procedures and services for UAM operations. The simulation called “X5” was conducted in 2023 to test a Provider of Services for UAM (PSU) prototype developed by NASA for UAM flight planning, strategic conflict management support, and data exchange between UAM operators. In this simulation, two strategic conflict management capabilities, Demand-Capacity Balancing and Sequencing and Scheduling, were further investigated. This document describes the UAM system architecture modeled, the X5 simulation environment to be executed (e.g., traffic scenario and UAM airspace construct), and the strategic conflict management processes developed and evaluated in this study. Then, the simulation results are provided using several system performance metrics, such as the number of operations planned and activated, demand-capacity imbalances detected and resolved, and pre-departure delays. Based on these metrics, the test findings and lessons learned from this simulation are discussed. NASA developed a PSU prototype as part of a reference implementation of UAM system architecture and evolved strategic conflict management capabilities for UAM operations from the previous collaborative simulations with industry partners. Below is the summary of the achievements: - Aligned NASA’s UAM reference architecture with the FAA’s UAM ConOps notional architecture - Extended UAM airspace management capabilities to include 1) Demand-Capacity Balancing (DCB) to ensure operators coordinate planned usage of shared vertiports, and 2) Sequencing and Scheduling (S&S) at UAM corridor entry and exit points to help facilitate an orderly flow of traffic - Defined the PSU information exchange APIs and requirements towards informing industry standards - Developed and tested a NASA PSU prototype as reference implementation to validate the requirements and APIs - Developed a prototype service connecting NASA’s PSU and the FAA system for testing future PSU-ATM interface requirements - Tested NASA-developed assumptions for UAM operations such as airspace design, procedures, vehicle performance, and strategic conflict management methods to inform future Cooperative Operating Practices (COPs) development with industry - Evaluated system performance metrics such as number of simultaneous operations and ground delays that can help define system-level requirements. The simulation results showed that the UAM traffic demand could be managed to minimize the needs of tactical separation provision with ground delays assigned by DCB and S&S. These accomplishments and the lessons learned from the PSU Prototype X5 simulation activities will be valuable inputs for the Air Mobility Pathfinders (AMP) project, which is NASA’s new project to create and evaluate a reference architecture for safe, secure, and scalable UAM operations.

Simulation↗

Moon Base Transportation - Deliveries to the Lunar Surface

Development of the Moon Base will enable a home away from home for astronauts who will live and work at humanity’s first lunar outpost. In this effort, NASA’s Moon Transportation Office is responsible for enabling the transformational missions required to deliver habitats, supplies, science payloads, and all other elements needed to cultivate a permanent presence on the Lunar Surface. The Mission Concept (MC) is characterized through evaluation of an end-to-end architecture that can successfully deliver a generalized heavy large-volume payload, in excess of 4000 kg, to a precision landing and touchdown on the lunar surface. The mission architecture utilizes a single launch configuration of a Lunar Lander (LL) with a unique propellant system. The LL has an integral orbital transfer capability and features jettisonable elements. The design circumvents the need for prop transfer on orbit and multiple launch configurations. The launch vehicle (LV) for this work will assume the capability to deliver a payload in excess of 40,000 kg to orbit, affording multiple LV solutions. Considerations for the LL and payload deployment from the fairing are assumed to be handled through compliance with a launch providers’ Interface Requirements Document (IRD). The MC will span from launch at Kennedy Space Center (KSC) to terminal descent and touchdown on the lunar surface, requiring a total ΔV on the order of 6 km/s beyond what is required to get the vehicle stack to a 200 km circular Low Earth Orbit (LEO). Major mission phases include: launch and launch vehicle separation, transfer operations, pre-landing navigation, and lunar descent and touchdown. A Concept of Operations (ConOps) is used as the primary design driver for defining architecture of the vehicles necessary to achieve final payload delivery. Numerous ground rules and assumptions will be provided for each phase of the mission. Concept designs for the LL is presented. An emphasis of the design maximizes a feasible path for maturation, manufacturing, and operation. A self-imposed practical consideration for this effort is the incorporation of legacy designed hardware to minimize expensive, time-intensive, and high-risk hardware development cycles. The propulsion system of the LL adopts a conventional storable bipropellant configuration of monomethyl hydrazine (MMH) and mixed oxides of nitrogen (MON3). This effort will showcase a unique propellant delivery system to minimize the reliance on propellant management devices (PMDs) during descent. Numerous key constraints have been considered, across the multiple segments of the mission. These include the unique aspects of center of gravity (CG) management, thruster plume effects including self-impingement, propulsion system hardware limitations, navigation during multiple mission phases, and landing gear geometry for uneven terrain. These constraints shape the trades necessary for precision landing of heavy cargo and ensure compatibility with broader Moon Base Transportation concepts. The resulting insights inform future transportation strategies for the Moon and beyond; directly contributing to the development of cargo‑delivery standards that will support the long‑term buildup of a sustainable, continuously inhabited Moon Base.

Lunar Habitat↗

Spectra-to-exposure conversion using polynomial response models for gamma-ray field characterization

Accurate measurement of exposure rate from gamma-ray spectral data remains a critical challenge during radiological emergency response operations. Conventional methods rely on pre-defined static conversion factors derived from fixed geometries and isotopic compositions, which often fail to capture real-world environmental variability. This study presents a generalized approach as a "next-step" for converting gamma-ray spectral data into exposure rate using polynomial response models. The method introduces a flexible weighting scheme based on the in-situ detector response to distributed sources, enabling a pathway towards improved correspondence between measured spectra and "ground-truth" exposure rates. Experimental data from sodium iodide NaI(Tl) detectors were used to validate the approach as, at least equivalent to the current count-to-exposure method employed in emergency response CONOPS. Results show that the polynomial weighting model is sufficiently equal to the count-to-exposure method and may help improve accuracy given its adaptability to real-world conditions.

61 RADIATION PROTECTION AND DOSIMETRY↗

Desert Research and Technology Studies (D-RATS) 2022 Test Report

The primary purpose of the 2022 Desert Research and Technology Studies (D-RATS 22) analog mission field test was to provide data and recommendations regarding how pressurized rover (PR) design, cabin configuration, driving modes, timeline constraints, and mission operations can be acceptably implemented to support future Artemis missions that include a PR. The goal of these evaluations was to provide first order feedback and data on design concepts currently being traded as options for future pressurized rover flight prototypes. The Japan Aerospace Exploration Agency (JAXA) may provide a PR for future Artemis missions. One of the primary objectives of D-RATS 2022 was to share with the JAXA PR team the processes and protocols by which NASA has learned to successfully evaluate rover concepts through integrated HITL evaluations over the past 20+ years, so that JAXA could apply any applicable lessons learned to their PR design, development, testing, and evaluation.

analog↗

Update - Concept of Operations for Integrated Model-Centric Engineering at JPL

The increasingly ambitious requirements levied on JPL's space science missions, and the development pace of such missions, challenge our current engineering practices. All the engineering disciplines face this growth in complexity to some degree, but the challenges are greatest in systems engineering where numerous competing interests must be reconciled and where complex system level interactions must be identified and managed. Undesired system-level interactions are increasingly a major risk factor that cannot be reliably exposed by testing, and natural-language single-viewpoint specifications areinadequate to capture and expose system level interactions and characteristics. Systems engineering practices must improve to meet these challenges, and the most promising approach today is the movement toward a more integrated and model-centric approach to mission conception, design, implementation and operations. This approach elevates engineering models to a principal role in systems engineering, gradually replacing traditional document centric engineering practices.

The Concept of Operations (ConOps)↗

Air Traffic Management Technology Demonstration - 3 (ATD-3) Dynamic Weather Routes Domestic En Route Concept of Operations Synopsis Version 1.0

NASA conducted a survey in 2015 of stakeholders in industry, flight operators, and others to collect data on the most pressing air traffic management (ATM) issues impacting en route operations. Weather related delays and interruptions were identified as the most significant and costly problem impacting en route operations in today's system. Additionally, future traffic demands will place greater demands on the FAA's air traffic control system, necessitate a more efficient and integrated traffic management system and provide controller tools to leverage human productivity. Consequently, NASA is assembling a suite of integrated ground and aircraft-based technologies and decision-making aids under the Airspace Technology Demonstrations 3 (ATD-3) project to continuously search for more efficient weather-avoidance routes and to rapidly respond to weather changes and associated traffic management initiatives. These route efficiency enhancements are targeted at en route airspace and will enable continued use of en route and arrival metering in the presence of weather. NASA's Dynamic Weather Routes (DWR) concept represents a subset of those technologies and focuses primarily on the cruise phase of flight. It leverages existing air traffic weather, airspace, and traffic data, as well as improvements in navigation, surveillance, communication and digital network technologies, and builds upon existing ATM automation to address the shortcomings associated with strategic traffic flow management initiatives and weather forecasting uncertainties. The potential benefits in the form of time, fuel, and cost savings are significant. This concept of operations synopsis provides a detailed description of DWR, its potential benefits and notional implementation paths.

DWR↗

Air Traffic Management Technology Demonstration - 3 (ATD-3) Multi-Flight Common Route (MFCR) Concept of Operations Version 1.0

NASA's Multi Flight Common Route (MFCR) automation represents one element of those technologies focusing primarily on delay recovery in the en route phase of flight. Delay recovery is an attenuation of flight-time delay, accomplished by periodically revising weather-avoidance routing as the convective weather system evolves. MFCR is intended for use by Traffic Management Coordinators (TMCs) in Air Route Traffic Control Centers (ARTCCs, or Centers) and traffic management specialists (TMSs) in the Air Traffic Control System Command Center (ATCSCC). MFCR leverages existing weather, airspace, and traffic data, as well as improvements in navigation, surveillance, communication, and digital information technologies, to build on existing ATM automation and address some of the shortcomings associated with strategic traffic flow management initiatives and weather forecasting uncertainties. These capabilities provide significant potential benefits in the form of time, fuel, and cost savings. The concept of operations described in this document describes MFCR functionality as delivered by NASA to the FAA in December 2017, including a list of potential enhancements that may be realized when the system is fielded.

conops↗

Air Traffic Management Technology Demonstration - 3 (ATD-3): Operational Concept for the Integration of ATD-3 Capabilities Version 1.0

ATD-3 has developed four capabilities to address its goal and objectives. The four ATD-3 capabilities include: Dynamic Weather Routes (DWR), Multi-Flight Common Routes (MFCR), Traffic Aware Strategic Aircrew Requests (TASAR), and Dynamic Routes for Arrivals in Weather (DRAW). This document describes the long-term, mature vision for the use and incorporation of the ATD-3 capabilities into the National Airspace System (NAS). This vision describes their complementary interaction and the benefit capture that accrues from use. Recognizing that all capabilities are unlikely to be implemented in unison, each of the capabilities is designed and able to be implemented independently. As discrete portions of the integrated capabilities are planned, additional integration efforts should be undertaken to validate the complementary interactions and benefit pool are realized from the selected subset.

ConOps↗

Concept of Operations for Management by Trajectory

This document describes Management by Trajectory (MBT), a concept for future air traffic management (ATM) in which every flight operates in accordance with a four-dimensional trajectory (4DT) that is negotiated between the airspace user and the Federal Aviation Administration (FAA) to respect the airspace user's goals while complying with National Airspace System (NAS) constraints. In the present-day NAS, the ATM system attempts to predict the trajectory for each flight based on the approved flight plan and scheduled or controlled departure time. However, once the aircraft starts to move, controllers tactically manage the aircraft to implement traffic management restrictions, separate otherwise conflicting aircraft, and address arising NAS constraints. Tactical controller actions are not directly communicated to the automation systems or other stakeholders. Furthermore, the initial trajectory prediction does not anticipate these disruptions or how they will impact the flight. Consequently, and compounded by gaps in required data and models, trajectory predictions are less accurate than possible, which affects Traffic Flow Management (TFM) performance. A cornerstone of the MBT concept is that all air vehicles have, at all times, an assigned 4DT from their current state to their destination. These assigned trajectories consist of trajectory constraints and descriptions. Pilots and air traffic controllers, with the aid of automation, operate the aircraft to comply with the assigned trajectory, unless first negotiating a revision. Equipped aircraft have substantial responsibility for complying with the assigned trajectory without controller intervention. To maximize the operational flexibility available to the airspace user, the assigned trajectory only imposes trajectory constraints as required to achieve the ATM goals of NAS constraint compliance and aircraft separation. Trajectory descriptions are added to the assigned trajectory to ensure sufficient predictability. To further improve trajectory prediction accuracy, airspace users supplement the assigned trajectory by broadcasting intent information and updating it as necessary. Air vehicle intent is a more detailed description of the airspace user's plan for how the flight will fly the assigned trajectory. Air vehicle intent can change freely, without negotiation, as long as it remains in compliance with the assigned trajectory. Aircraft assigned trajectories, air vehicle intent, and predicted trajectories are shared, creating a common view among stakeholders. A NAS Constraint Service gathers and publishes information about all known NAS constraints, enabling airspace users to be informed participants in trajectory negotiation. Trajectory constraints in the assigned trajectory are mapped to NAS constraints to facilitate identifying which aircraft are affected when NAS constraints change. To support efficient trajectory negotiation, all aircraft provide current information about air vehicle capabilities. Assigned trajectories are constructed to satisfy all known NAS constraints, improving trajectory stability and predictability. Uncertainty and disruptions are handled by modifying the assigned trajectory as far in advance as possible. By proactively negotiating changes to the assigned trajectory, rather than relying on controller-selected tactical actions such as vectors to resolve traffic conflicts or implement miles-in-trail restrictions, MBT keeps aircraft on closed trajectories that are fully known to all stakeholders. Since reactive air traffic control actions cannot be predicted in advance, the downstream trajectory cannot be accurately predicted until they happen. Reliable trajectory predictions allow the system to identify needed modifications to trajectories further in advance, where they can be negotiated and communicated as amendments (i.e., additional or altered trajectory constraints) to the assigned trajectory. Decision Support Tools (DSTs) aid controllers in rapidly defining and communicating closed trajectories to the aircraft and support all stakeholders in trajectory negotiation. Anticipated MBT benefit mechanisms include more accurate trajectory predictions, improved ATM performance and robustness to off-nominal conditions, increased flexibility and operational efficiency, reduced impediments to emerging classes of airspace users accessing NAS resources, reduced environmental impacts, and enhanced safety.

ConOps↗

UTM Concepts and Use Cases

The presentation provides an overview of the UTM Research Transition Team (RTT) and the role of the Concepts and Use Cases Working Group (CWG) as part of the joint NASA-FAA effort. The deliverables, role in tests/demonstrations, future work, and summary impact of the CWG are the main areas covered.

UTM↗

NASA CARA Prelaunch Analysis and Process

NASA implemented an official Procedural Requirement (NPR) 8079.1 in June 2023, establishing the minimum collision avoidance requirements and associated operational protocols for NASA space flight programs, projects, and spacecraft to protect the space environment by reducing the risk of collision to an acceptable level. Part of the requirement employs a two-fold approach to analyze the satellite design process with conjunction assessment and risk mitigation in mind, during the pre-launch process, led by the Conjunction Assessment Risk Analysis (CARA) Program for non-Human Space Flight (HSF) Missions. This presentation outlines CARA coordination with missions, informed by the NPR, that spans early mission development to operations. CARA is an Agency-level resource that provides support to all NASA non-HSF missions. CARA protects the orbital environment from collision between NASA non-HSF missions and other tracked on-orbit objects. During the pre-formulation and formulation phases, NASA missions undergo a series of conjunction assessment analyses captured in the Orbital Collision Avoidance Plan (OCAP) prior to transitioning to the implementation phase (typically at the Preliminary Design Review (PDR) or equivalent). The OCAP analyses consist of a thorough review of the spacecraft(s) orbit selection and placement, deployment, cataloguing performance, trackability, ephemeris generation, conjunction mitigation options, autonomous maneuvering, and risk assessment parameters which are performed by a dedicated CARA Analysis Team. The results of these analyses, CARA’s formal recommendations, and the mission’s methods for implementing them, are documented in the OCAP. The intent of engaging in this process so early in the mission design phase, is to ensure that conjunction assessment is considered from the outset, thus mitigating costly design changes and operational risks down the road. NASA missions are also required to coordinate their operational processes and conjunction mitigation procedures with CARA in a Conjunction Assessment Operations Implementation Agreement (CAOIA). The aim of this process is to document the conjunction assessment screening process, conjunction risk assessment parameters, conjunction mitigation steps, flight dynamics operations concepts and maneuvers, and the communication and coordination process between the mission’s project manager and CARA. The intent of the CAOIA document is for it to be completed iteratively, and as missions update these elements, corresponding changes are made in the CAOIA. With this process in place, the engagement and coordination between the missions and CARA from early in the design process into mission operations, helps to ensure that missions not only have a robust conjunction assessment concept of operations to reduce conjunction risk for space sustainability, but are also able to achieve their science goals and have a successful mission.

conjunction assessment↗

NASA CARA Prelaunch Analysis and Process

NASA implemented an official Procedural Requirement (NPR) 8079.1 in June 2023, establishing the minimum collision avoidance requirements and associated operational protocols for NASA space flight programs, projects, and spacecraft to protect the space environment by reducing the risk of collision to an acceptable level. Part of the requirement employs a two-fold approach to analyze the satellite design process with conjunction assessment and risk mitigation in mind, during the pre-launch process, led by the Conjunction Assessment Risk Analysis (CARA) Program for non-Human Space Flight (HSF) Missions. This presentation outlines CARA coordination with missions, informed by the NPR, that spans early mission development to operations. CARA is an Agency-level resource that provides support to all NASA non-HSF missions. CARA protects the orbital environment from collision between NASA non-HSF missions and other tracked on-orbit objects. During the pre-formulation and formulation phases, NASA missions undergo a series of conjunction assessment analyses captured in the Orbital Collision Avoidance Plan (OCAP) prior to transitioning to the implementation phase (typically at the Preliminary Design Review (PDR) or equivalent). The OCAP analyses consist of a thorough review of the spacecraft(s) orbit selection and placement, deployment, cataloguing performance, trackability, ephemeris generation, conjunction mitigation options, autonomous maneuvering, and risk assessment parameters which are performed by a dedicated CARA Analysis Team. The results of these analyses, CARA’s formal recommendations, and the mission’s methods for implementing them, are documented in the OCAP. The intent of engaging in this process so early in the mission design phase, is to ensure that conjunction assessment is considered from the outset, thus mitigating costly design changes and operational risks down the road. NASA missions are also required to coordinate their operational processes and conjunction mitigation procedures with CARA in a Conjunction Assessment Operations Implementation Agreement (CAOIA). The aim of this process is to document the conjunction assessment screening process, conjunction risk assessment parameters, conjunction mitigation steps, flight dynamics operations concepts and maneuvers, and the communication and coordination process between the mission’s project manager and CARA. The intent of the CAOIA document is for it to be completed iteratively, and as missions update these elements, corresponding changes are made in the CAOIA. With this process in place, the engagement and coordination between the missions and CARA from early in the design process into mission operations, helps to ensure that missions not only have a robust conjunction assessment concept of operations to reduce conjunction risk for space sustainability, but are also able to achieve their science goals and have a successful mission.

conjunction assessment↗

SysML Success Tree for DAVINCI In-Situ Campaign Requirements Validation and Redundancy Assessment

The DAVINCI mission will scientifically study the Venusian atmosphere to better understand the current state of the planet and its evolutionary history. This will be accomplished by deploying a descent probe to collect in-situ atmospheric dynamic and spectroscopic measurements, characterize ambient temperatures and pressures during descent, and surface imaging below the cloud layer. To better characterize the DAVINCI In-Situ Campaign, a success tree, developed in the SysML tool, MagicDraw, was created to define the events necessary to have a successful in-situ campaign, for each phase of the campaign. This success tree was also used to validate DAVINCI Program, Mission, and Element level requirements. In addition, because DAVINCI is a single-string mission, the success tree was also used to identify areas of redundancy and resiliency throughout the campaign. The initial redundancy assessment recommended further on-orbit evaluation of the probe’s communication system, as well as further evaluation of the ability of the mass spectrometer turbo-molecular pump to handle the expected decent environment. During the integration and test phase of the overall mission, the success tree will be used to guide the mission validation process, helping to ensure that the in-situ mission elements can perform in accordance with the DAVINCI In-Situ Concept of Operations document.

model-based↗

SysML Success Tree for DAVINCI In-Situ Campaign Requirements Validation and Redundancy Assessment

The DAVINCI mission will scientifically study the Venusian atmosphere to better understand the current state of the planet and its evolutionary history. This will be accomplished by deploying a descent probe to collect in-situ atmospheric dynamic and spectroscopic measurements, characterize ambient temperatures and pressures during descent, and surface imaging below the cloud layer. To better characterize the DAVINCI In-Situ Campaign, a success tree, developed in the SysML tool, MagicDraw, was created to define the events necessary to have a successful in-situ campaign, for each phase of the campaign. This success tree was also used to validate DAVINCI Program, Mission, and Element level requirements. In addition, because DAVINCI is a single-string mission, the success tree was also used to identify areas of redundancy and resiliency throughout the campaign. The initial redundancy assessment recommended further on-orbit evaluation of the probe’s communication system, as well as further evaluation of the ability of the mass spectrometer turbo-molecular pump to handle the expected decent environment. During the integration and test phase of the overall mission, the success tree will be used to guide the mission validation process, helping to ensure that the in-situ mission elements can perform in accordance with the DAVINCI In-Situ Concept of Operations document.

ConOps↗

Dynamic Anomaly Response and Integrated Analysis (DARIA): A Fault Investigation Toolset Supporting Earth-Independent Operations in Future Crewed Mars Missions

NASA's Moon to Mars Objectives outline a strategic vision for human spaceflight culminating in crewed missions to Mars. A critical component of this objective is the development of systems that are capable of being Earth-Independent Operated (EIO). A key aspect of EIO is the ability to rapidly detect, diagnose, and respond to anomalies in crew-supporting habitat and connected systems. To address this, the Dynamic Anomaly Response and Integrated Analysis (DARIA) architecture has been developed. DARIA incorporates a network of compact, wireless sensing devices called the System for Telemetry Amalgamation of Multimodal PrognosticS (STAMPS) for increased state awareness of EIO habitats. Able to perform on-the-fly data acquisition, STAMPS are connected to integrated anomaly data dashboards for crew visualization. DARIA is designed to seamlessly integrate into various off-world environments, including the International Space Station, Lunar Gateway, Artemis Base Camp, and future Mars habitats. By leveraging Commercial Off-The-Shelf (COTS) hardware, the NASA Internet of Things (NASA IoT) framework, and EIO fault detection methods, DARIA provides a cost-effective and adaptable solution for anomaly detection and response in EIO habitats.

Diagnostics↗