Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Risk Management Space Projects”

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 163 records · Page 9

Tool Use Within NASA Software Quality Assurance

As space mission software systems become larger and more complex, it is increasingly important for the software assurance effort to have the ability to effectively assess both the artifacts produced during software system development and the development process itself. Conceptually, assurance is a straightforward idea - it is the result of activities carried out by an organization independent of the software developers to better inform project management of potential technical and programmatic risks, and thus increase management's confidence in the decisions they ultimately make. In practice, effective assurance for large, complex systems often entails assessing large, complex software artifacts (e.g., requirements specifications, architectural descriptions) as well as substantial amounts of unstructured information (e.g., anomaly reports resulting from testing activities during development). In such an environment, assurance engineers can benefit greatly from appropriate tool support. In order to do so, an assurance organization will need accurate and timely information on the tool support available for various types of assurance activities. In this paper, we investigate the current use of tool support for assurance organizations within NASA, and describe on-going work at JPL for providing assurance organizations with the information about tools they need to use them effectively.

software assurance↗

A risk management approach to CAIS development

The proposed DoD standard Common APSE Interface Set (CAIS) was developed as a framework set of interfaces that will support the transportability and interoperability of tools in the support environments of the future. While the current CAIS version is a promising start toward fulfilling those goals and current prototypes provide adequate testbeds for investigations in support of completing specifications for a full CAIS, there are many reasons why the proposed CAIS might fail to become a usable product and the foundation of next-generation (1990'S) project support environments such as NASA's Space Station software support environment. The most critical threats to the viability and acceptance of the CAIS include performance issues (especially in piggybacked implementations), transportability, and security requirements. To make the situation worse, the solution to some of these threats appears to be at conflict with the solutions to others.

Hart, Hal↗

Reducing the complexity of software systems - A strategic software perspective

The results of a combined management and technical initiative aimed at reducing the size and complexity associated with developing operations planning, scheduling, and resource management software systems are presented. The initiative has produced operations concepts, functional requirements, system architectures, a comprehensive lexicon, and software tools to revolutionize the traditional software technology and development practices for planning, scheduling, and resource management systems used in space operations control centers. Examples of technology and practices to reduce complexity include a method for projecting design consequences from an operations concept, a universal architecture for heuristic algorithms, an object-oriented framework for describing large classes of problems that parametrically adapt to all domain peculiarities, the identification of general approaches which respond to changes with minimum impact on systems implementations, and a management structure for prototyping to minimize the risks of ill-conceived designs.

Hornstein, Rhoda S.↗

STS-114: Discovery Day 6 Post MMT Meeting

Wane Hill, Deputy Manager of the Space Shuttle Program, and Steve Poulos, Manager, Orbiter Project Office discussed damage assessments caused during ascent. Steve further detailed the damage analysis and assessments with chart presentation of composite tile damage and gap filler sites evaluation, protruding ceramic shim, left wing tile damage, comparisons of ground test results versus FD5 focused inspection, and the window 1 blanket. Gap fillers, the STS-73, thermal protection, temperature range, heating and heating range, aerodynamics, aerothermodynamics, risk, foam damage, tile adhesions, and extravehicular activities are topics covered with the News media.

Source record↗

Radiation Hardness Assurance (RHA): Challenges and New Considerations

Radiation Hardness Assurance (RHA) challenges associated with the use of commercial-off-the-shelf (COTS) components and emerging technologies are cause for risk acceptance in space flight missions. The RHA flow includes environment definition, hazard evaluation, requirements definition, evaluation of design, and design trades to accommodate the risk a project or program takes. The varied missions profiles and environments don't necessarily benefit from the same risk reduction efforts or cost reduction attempts. The level of effort within the RHA flow can be tailored to minimize risk based on the environment or design criticality.

Space Technology↗

Requirement Metrics for Risk Identification

The Software Assurance Technology Center (SATC) is part of the Office of Mission Assurance of the Goddard Space Flight Center (GSFC). The SATC's mission is to assist National Aeronautics and Space Administration (NASA) projects to improve the quality of software which they acquire or develop. The SATC's efforts are currently focused on the development and use of metric methodologies and tools that identify and assess risks associated with software performance and scheduled delivery. This starts at the requirements phase, where the SATC, in conjunction with software projects at GSFC and other NASA centers is working to identify tools and metric methodologies to assist project managers in identifying and mitigating risks. This paper discusses requirement metrics currently being used at NASA in a collaborative effort between the SATC and the Quality Assurance Office at GSFC to utilize the information available through the application of requirements management tools.

Hammer, Theodore↗

Tailoring Systems Engineering Processes in a Conceptual Design Environment: A Case Study at NASA Marshall Spaceflight Center's ACO

This paper provides an overview of Systems Engineering as it is applied in a conceptual design space systems department at the National Aeronautics and Space Administration (NASA) Marshall Spaceflight Center (MSFC) Advanced Concepts Office (ACO). Engineering work performed in the NASA MFSC's ACO is targeted toward the Exploratory Research and Concepts Development life cycle stages, as defined in the International Council on Systems Engineering (INCOSE) System Engineering Handbook. This paper addresses three ACO Systems Engineering tools that correspond to three INCOSE Technical Processes: Stakeholder Requirements Definition, Requirements Analysis, and Integration, as well as one Project Process Risk Management. These processes are used to facilitate, streamline, and manage systems engineering processes tailored for the earliest two life cycle stages, which is the environment in which ACO engineers work. The role of systems engineers and systems engineering as performed in ACO is explored in this paper. The need for tailoring Systems Engineering processes, tools, and products in the ever-changing engineering services ACO provides to its customers is addressed.

Mulqueen, John↗

What You Need to Know about Planetary Protection Categorization for Your Mission

Planetary protection mission categorization helps to define the risk posture for requirements definition and implementation practices on space flight projects with planetary protection considerations. NASA has recently updated it’s planetary protection policy (NPR 8715.24), and with the update comes a major change in how the planetary protection categorization process is performed for NASA missions. Previously, projects would request the NASA Planetary Protection Officer (PPO) provide a categorization letter documenting the planetary protection category assigned to the proposed mission. Under the new policy the project manager (PM) proposes the planetary protection category for their mission. Depending on the level of the category, the PPO either concurs or recommends concurrence to the Chief of Safety and Mission Assurance (SMA) before forwarding to the Mission Directorate Associate Administrator (MDAA) for final approval prior to the system requirements review (SRR). But what topics must be considered for categorization? This presentation will provide key considerations for planetary protection mission categorization including the target solar system body to be explored, the trajectory to get to the target body, and the operations to be performed at the target body. Additional unique scenarios such as secondary and auxiliary payloads, encountering other solar system bodies on the way to the target body, and sample return missions will also be discussed to share lessons learned from missions that have been through the new categorization process.

Elaine Seasly↗

Cassini Information Management System in Distributed Operations Collaboration and Cassini Science Planning

Launched on October 15, 1997, the Cassini-Huygens spacecraft began its ambitious journey to the Saturnian system with a complex suite of 12 scientific instruments, and another 6 instruments aboard the European Space Agencies Huygens Probe. Over the next 6 1/2 years, Cassini would continue its relatively simplistic cruise phase operations, flying past Venus, Earth, and Jupiter. However, following Saturn Orbit Insertion (SOI), Cassini would become involved in a complex series of tasks that required detailed resource management, distributed operations collaboration, and a data base for capturing science objectives. Collectively, these needs were met through a web-based software tool designed to help with the Cassini uplink process and ultimately used to generate more robust sequences for spacecraft operations. In 2001, in conjunction with the Southwest Research Institute (SwRI) and later Venustar Software and Engineering Inc., the Cassini Information Management System (CIMS) was released which enabled the Cassini spacecraft and science planning teams to perform complex information management and team collaboration between scientists and engineers in 17 countries. Originally tailored to help manage the science planning uplink process, CIMS has been actively evolving since its inception to meet the changing and growing needs of the Cassini uplink team and effectively reduce mission risk through a series of resource management validation algorithms. These algorithms have been implemented in the web-based software tool to identify potential sequence conflicts early in the science planning process. CIMS mitigates these sequence conflicts through identification of timing incongruities, pointing inconsistencies, flight rule violations, data volume issues, and by assisting in Deep Space Network (DSN) coverage analysis. In preparation for extended mission operations, CIMS has also evolved further to assist in the planning and coordination of the dual playback redundancy of highvalue data from targets such as Titan and Enceladus. This paper will outline the critical role that CIMS has played for Cassini in the distributed ops paradigm throughout operations. This paper will also examine the evolution that CIMS has undergone in the face of new science discoveries and fluctuating operational needs. And finally, this paper will conclude with theoretical adaptation of CIMS for other projects and the potential savings in cost and risk reduction that could potentially be tapped into by future missions.

Equils, Douglas J.↗

National Aeronautics and Space Administration Marshall Space Flight Center Space Transportation Directorate Risk Management Implementation Program

The US civil aerospace program has been a great contributor to the creation and implementation of techniques and methods to identify, analyze, and confront risk. NASA has accomplished mission success in many instances, but also has had many failures. Anomalies have kept the Agency from achieving success on other occasions, as well. While NASA has mastered ways to prevent risks, and to quickly and effectively react and recover from anomalies or failures, it was not until few years ago that a comprehensive Risk Management process started being implemented in some of its programs and projects. A Continuous Risk Management (CRM) cycle process was developed and has been promoted and used successfully in programs and projects across the Agency.

Duarte, Luis Alberto↗

Risk Management for the International Space Station

The International Space Station (ISS) is an extremely complex system, both technically and programmatically. The Space Station must support a wide range of payloads and missions. It must be launched in numerous launch packages and be safely assembled and operated in the harsh environment of space. It is being designed and manufactured by many organizations, including the prime contractor, Boeing, the NASA institutions, and international partners and their contractors. Finally, the ISS has multiple customers, (e.g., the Administration, Congress, users, public, international partners, etc.) with contrasting needs and constraints. It is the ISS Risk Management Office strategy to proactively and systematically manages risks to help ensure ISS Program success. ISS program follows integrated risk management process (both quantitative and qualitative) and is integrated into ISS project management. The process and tools are simple and seamless and permeate to the lowest levels (at a level where effective management can be realized) and follows the continuous risk management methodology. The risk process assesses continually what could go wrong (risks), determine which risks need to be managed, implement strategies to deal with those risks, and measure effectiveness of the implemented strategies. The process integrates all facets of risk including cost, schedule and technical aspects. Support analysis risk tools like PRA are used to support programatic decisions and assist in analyzing risks.

Sebastian, J.↗

Techniques for Assuring NASA Mission Success Using Redundancy and Multi-Functionality Designs

Topics include NASA centers around the country; 2009 highlights of significant successes in space transportation, exploration, and science; significant accomplishments; places to explore include Lagrange points, near-Earth objects, Mars and the Moon, and International Space Station research; Marshall's missions include propulsion and transportation systems, life support systems, and earth and space science spacecraft, systems, and operations; project lifecycle management model; motivation of avionics fault-tolerance, redundancy needs and concerns, redundancy versus reliability; parallel-series configurations; effect of adding redundancy on mission success; example of rules-based approach where reliability and safety interaction impacts design; impact of common cause failure; approach ot bottom-up reliability analysis; three factors that lead to redundant system failure; Apollo 13 multi-functional reliability and example; and mitigating the risk of single string spacecraft architecture;.

Shivers, Herb↗

Lessons Learned in Systems Engineering Availability and Recommendations for Mission Technical Leaders

In spaceflight missions at Goddard Space Flight Center (GSFC), the Mission System Engineer (MSE) is the technical leader of the overall engineering team and also is the Independent Engineering Technical Authority. The responsibility of this role includes the definition of the mission design architecture, concept of operations, and mission requirements, management of risk throughout the development, and verification and validation of the final system performance and function amongst other duties. This responsibility inherently requires time management, enabling focus on a balanced development with appropriate risk. Time is the most valuable resource of the MSE. The system engineer’s availability to interact with the development team (often product or component design leads and technicians, often in different worksites) to discover and mitigate mission risks during development is key to mission success. This paper presents examples from Lunar Reconnaissance Orbiter, Landsat 9, and Neutron star Interior Composition ExploreR (NICER) which represent in-house and out-of-house hardware builds. These examples demonstrate how interactions between the Mission Systems Engineers and other project and partner engineers result in discovery of critical risks, leading to early mitigation with significant cost and performance savings. These three missions would have suffered test failures or on-orbit failures had their MSEs not set aside time to visit engineers and technicians that were working on key pieces of space flight hardware. Availability is more than just time; it is openness to listen to concerns and questions. It begins by building a level of trust in the team that it is safe to ask questions or share concerns without the fear of blame or additional workload. It also requires enabling informal conversations (over lunch, coffee, in the clean room, or at the team members desk, etc.) where key information can be exchanged, and team members may even provide an easy-to-implement mitigation idea for another subsystem. Availability is a highly valuable commodity and completely non-obvious to protect and optimize. The natural tendency of engineers is to keep themselves busy with solving problems that they know about. This paper is encouraging MSEs to resist this tendency to try and solve all the complex problems themselves and actively devote daily time to learning and solving problems that are found with informal communications with other team members.

Lessons Learned↗

DARHT : Enduring Lessons from a Technical Project in a National Laboratory Context [Slides]

The Dual-Axis Radiographic Hydrodynamic Test (DARHT) facility at Los Alamos National Laboratory (LANL) is the world’s first flash x-ray facility able to take multiple high-resolution radiographs of the interior features of fast-moving dense objects during a single experiment. DARHT’s radiography and complimentary diagnostics makes it an important diagnostic tool in support of the US Department of Energy’s (DOE)/National Nuclear Security Administration (NNSA)’s stewardship of the US nuclear deterrent. The project to construct DARHT ran from 1988 through 2003. Initial Operating Capability along a single axis began in 1999. A technical issue delayed Critical Decision 4 for the full dual-axis capability until 2008. DARHT was characterized by several directed changes resulting from an environmental impact study, changes to the global security context resulting from the end of underground nuclear testing, and rapid evolution of applicable technology. Conventional building and lab-space construction were part of the project, but the project was dominated by Special Facility Equipment that, together with the mission to support the nuclear weapons program, required the project to be completed by national laboratories. Although the project pre-dated implementation of DOE Order 413.3, several important lessons for national laboratory projects remain applicable today and will be discussed here, including projects appropriate for the national laboratory environment, scope stability, risk acceptance and mitigation, communication, and collaboration. Finally, considerations for DOE contractor project managers are offered based upon the DARHT experience.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

ISS Technology Demonstrations for Future Spaceflight Medical Systems

Throughout the history of human spaceflight, crewmembers have experienced various in-flight medical conditions including illness and injury. Planned missions to the Moon and Mars will require capabilities to maintain the health of future space travelers. Mass, power, and volume available in the vehicles and habitats for these missions will be severely constrained; resupply of resources will be limited or non-existent, as will opportunities for evacuation to Earth. Furthermore, ground-based support will be hampered by communication latencies and blackouts. These vehicle and mission constraints will necessitate a medical system that has been efficiently planned, providing on-board procedural guidance in addition to a variety of medical devices and consumable resources. Medical capabilities required for the diagnosis and treatment of potential medical conditions during future spaceflight missions may include real-time health monitoring, medical imaging, and biomarker analyses ( e.g., blood or urine). Terrestrial medicine shares these needs, thus many of these medical capabilities could likely be satisfied by Commercial-Off-The-Shelf (COTS) devices and methodologies; however, in some cases the unique space environment and increased mission duration will drive the need to modify technologies and the way care is provided. NASA’s Human Research Program (HRP) Exploration Medical Capability (ExMC) Element and Mars Campaign Office’s Exploration Medical Integrated Product Team (XMIPT) are working together to decrease medical risk during exploration missions. Flight-tested medical diagnostic and treatment technologies are necessary to effectively manage medical conditions relevant to exploration missions while meeting vehicle constraints, integrating with medical decision-support tools, and enabling increasingly Earth-independent operations. Several projects have leveraged the ISS as a testbed for exploration, including 1) i n- situ blood analysis, 2) medical inventory, 3) intravenous fluid generation, and 4) autonomous medical procedure guidance. Management of several in-flight medical conditions, such as bacterial and viral infections and acute radiation syndrome, is dramatically improved with ability to assess blood cell populations, electrolytes, and metabolites. I n December 2020 and January 2021 ExMC performed an ISS technology demonstration (Tech Demo) of the HemoCue® WBC DIFF analyzer (HemoCue, Brea, CA), a COTS device that was modified to enable functionality in a spaceflight environment. This Tech Demo marked the first time that hematology measurements were successfully performed real-time in microgravity. Also modified and demonstrated was the reusable Handheld Electrolytes and Lab Technology for Humans (rHEALTH) ONE analyzer (rHEALTH, Bedford, MA), which uses flow cytometry and sheath-based hydrodynamic focusing methodologies. The rHEALTH ONE ISS Tech Demo in May 2022 demonstrated test results obtained in-flight matched those on the ground. NASA currently relies on crew self-reporting to manage and maintain medical inventory on ISS.The ability to maintain an accurate inventory becomes more critical during long duration missions since the crew will need to be increasingly autonomous in finding and utilizing medical items, including those scenarios when alternative treatments need to be considered due to limited or no resupply. HRP’s Medical Consumables Tracking (MCT) project was developed by ZIN Technologies, Inc. (Cleveland, OH), and demonstrated real-time tracking of medical supplies aboard the ISS between December 2016 and July 2018. The MCT system design utilized Radio Frequency Identification Device (RFID) technology to perform automated inventory and was installed in the Crew Health Care System (CHeCS) Resupply Stowage Rack (RSR). The challenge of limited shelf life, exacerbated by the lack of resupply opportunities, affects a plethora of medical system components including consumables, pharmaceuticals, and intravenous (IV) fluid. In 2010, ExMC funded ZIN Technologies, Inc. (Cleveland, OH), to develop the Intravenous Fluid Generation (IVGEN) system. IV fluids were successfully generated with IVGEN using the potable water supply on ISS during ISS Expedition 23. The XMIPT is in the process of developing a miniaturized version of the original IVGEN hardware for a future Tech Demo aboard the ISS. Current ISS medical operations rely heavily on preflight training and real-time remote guidance, both of which become impractical or impossible for exploration missions. The primary goal of the Autonomous Medical Officer Support (AMOS) Software Tech Demos on ISS was to confirm telemedical proof-of-concept for autonomous medical imaging in an operational setting. This novel software tool shifts emphasis from preflight training and real-time remote guidance to in-flight just-in-time instruction, a new and necessary paradigm for crew medical autonomy. AMOS introduces a novel, streamlined skill management concept for exploration missions featuring comprehensive training and guidance modules for ultrasound examinations using the ISS Ultrasound 2 (a modified GE Vivid-q™; General Electric HealthCare, Chicago, IL). With no prior crew training or remote guidance, two Tech Demos on the ISS (April 2020 and June 2022) resulted in high quality, clinically useful image sets. We will provide a review of historical, current, and planned medical devices and technologies considered for inclusion within future spaceflight medical systems and summarize hardware development activities and medical device tech demos conducted on the ISS.

Astronaut health and performance↗

Integrated Research Plan to Assess the Combined Effects of Space Radiation, Altered Gravity, and Isolation and Confinement on Crew Health and Performance: Implementation Strategy

This document supplements the white paper titled CBS Integrated Research Plan: Problem Statement. The Problem Statement describes why it is important to implement a fully integrated research plan to derive risk estimates for the combined, potentially synergistic, effects of the three major spaceflight hazards (space radiation; isolated, confined, and extreme environments; altered gravity). These risk estimates will help establish acceptable maximum decrement or change in a physiological or behavioral parameter during or after spaceflight, and the acceptable limit of exposure to the combined spaceflight hazards. This Implementation Strategy describes how the research plan will accomplish the CBS Integrated Research Plan goals. The Implementation Strategy includes approaches to evaluate relationships among biological responses underlying three risks that are managed by three of NASA’s Human Research Project (HRP) organizational “elements”. This CBS (Acute effects of radiation on CNS, BMed, Sensorimotor) Integrated Research Plan also identifies strategies to monitor and mitigate decrements to operationally relevant performance. Currently, the strategy that was initiated in 2018, includes an eight-year research plan and a four-year validation plan that extend to the year 2030. Once the monitoring tools and countermeasures are developed, they will be validated and refined during four years of early exploration missions. The planned tasks and their associated research products and deliverables have been mapped to the individual research emphases to clearly demonstrate how each research area helps ensure crew health and safety during exploration missions.

Susan Steinberg↗

HERO CarbonSAFE Phase 2 Project in the Columbia River Basalt Group

The Hermiston, Oregon Basalt CarbonSAFE Phase II project (HERO CarbonSAFE) seeks to accelerate the deployment of commercial carbon dioxide (CO2) storage projects in basaltic rocks. Basalt CO2 storage has several advantages to conventional saline storage reservoirs including 1. The potential for rapid mineralization of CO2, 2. Associated decreases in pressure and CO2 migration risks, 3. Reduced long-term monitoring requirements with respect to plume tracking, 4. Widespread geographic distribution and, 5. Large storage potential due to thickness, porosity, and CO2 interactions with basalt. And for locations such as the Pacific Northwest, Hawaii, Iceland, India and Japan, basalts may offer the only economically feasible option for local CO2 storage. However, there are limited field-scale assessments of CO2 storage in basalt, and current carbon capture utilization and storage (CCUS) permitting and regulatory frameworks were developed for conventional saline reservoirs. HERO CarbonSAFE is designed to address research gaps and uncertainties associated with basalt storage. Specifically, the project will assess the feasibility of CO2 injection in the deep layered basalts, long-term storage (mineralization), practical approaches for large-scale implementation (50+ million metric tons of CO2 over 30 years), lithology-specific risks, and the technoeconomic potential for CO2 storage in basalts. The HERO CarbonSAFE project will assess feasibility of developing a commercial-scale (50+ million metric tons of CO2) geological storage complex within the Columbia River Basalt Group (CRBG), a layered continental flood basalt complex that underlies Calpine’s natural gas-fired Hermiston Power Project (HPP) in Hermiston, OR (Figure 1). Under this 2-year CarbonSAFE Phase II project, the HERO team will conduct a data acquisition campaign that includes drilling a stratigraphic well to a total depth of ~1,500 m into the thick layered basalts proximal to HPP. A comprehensive well logging and hydrologic testing program will be augmented with new core collected from flow zones and sealing units, and comprehensive laboratory testing to help refine the kinetic rates of mineralization. The newly acquired information will be integrated with existing data from regional wells to correlate basalt injection zone properties to develop storage hub/commercial-scale models. Using these models, the project team will evaluate injection scenarios to define the technical and economic potential for storing a minimum of 50 million metric tons of CO2 over a 30-year period, along with a robust sensitivity analysis on key parameters governing reservoir viability for sustainable injection over a commercial project lifetime. Specific technical objectives of HERO are: (1) assessing the reservoir response of a series of stacked layered reservoir flowtop sequences occurring in this area of the CRBG to commercial-scale injection volumes; (2) extending prior efforts by the project team to characterize the deep layered basalts encountered in regional studies, to leverage prior investments by U.S. Department of Energy’s (DOE) Carbon Storage program; (3) leveraging DOE’s mineralization characterization efforts to advance model parametrization for commercial scale injection of CO2 in basalts; (4) conducting risk assessments associated with scaling up to commercial storage hub injection goals, while validating DOE’s National Risk Assessment Partnership (NRAP) tools, to identify potential constraints that would prevent the CRBG from serving as a commercial-scale storage complex; (5) developing mitigation plans to address identified risks; (6) developing a commercial-scale injection and monitoring, verification and accounting (MVA) strategy; (7) utilizing computational models to define and minimize, if possible, the Area of Review (AoR) under Class VI regulations; and (8) developing a robust CO2 management strategy for CRBG that also considers a regional source/sink approach that is responsive to stakeholder needs and industrial demand. Specific institutional objectives are: (1) identifying and developing plans to mitigate the nontechnical challenges associated with the build-out of a commercial-scale storage complex within the CRBG with integrated CO2 sources; (2) implementing the community outreach plan; (3) conducting regulatory research, including a survey of issues related to pore space ownership, MVA and long-term assurance of mineralization-based storage, to support an eventual application for a UIC Class VI permit; (4) advancing the project’s plan for CO2 liability management; and (5) continuing to refine and update the project’s economic model. The final objective is the preparation of a comprehensive Site Characterization Plan that draws upon the technical and institutional feasibility assessments to prepare the project for future commercialization efforts.

58 GEOSCIENCES↗

Incorporating UAS Traffic Management into Wildland Firefighting Operations: Initial Findings of Subject Matter Expert Interviews

Uncrewed Aircraft Systems (UASs) are being utilized throughout the disaster and emergency response domain, including in wildland firefighting operations. While UASs can offer safety benefits in comparison to crewed aircraft, such as removing the human pilot from the vehicle so that they are not exposed to the same risks and the ability to operate in low-visibility conditions, they are not without tradeoffs. For example, it can be challenging for UAS pilots (UASPs) to build situation awareness of the airspace in which their UAS is operating. In order to address some of the challenges associated with using UASs and provide greater assistance to the firefighters and incident personnel in the wildland firefighting environment, the National Aeronautics and Space Administration (NASA) launched the Advanced Capabilities for Emergency Response Operations (ACERO) project. Building on previous NASA research, ACERO will explore the implementation of a traffic management system in the wildland fire environment to enhance safety and support situation awareness. ACERO draws on the UAS Traffic Management (UTM) system previously demonstrated in an urban environment. However, a traffic management system implemented in the wildland fire environment is expected to look and function much differently in order to meet the unique needs of this domain. At the outset of the ACERO project, interviews were conducted with five UASPs who operate UASs at wildland fire incidents. The interviews focused on exploring UASPs’ initial insights about the application of a traffic management system in wildland firefighting and understanding the unique needs of this environment. The UASPs discussed a range of topics including, the shape, size, and organization of UAS operations in the wildland fire environment, information needs for a user interface, such as traffic and map information, an alerting function when other traffic nears their operation area, and the importance of conformance monitoring. The UASPs also discussed their willingness to share operational information to support safety. In this paper, we describe the foundational work upon which ACERO will build and summarize the information and insights gathered during the UASP interviews, some of which have already informed the development of the ACERO work.

Uncrewed Aircraft System (UAS)↗