Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “standard performance”

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 145 records · Page 8
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

ACES M and S: Unmitigated Factorial Encounter Study on DAA/TCAS Interoperability

Realization of the expected proliferation of Unmanned Aircraft System (UAS) operations in the National Airspace System (NAS) depends on the development and validation of standards for UAS Detect and Avoid (DAA) Systems. The RTCA Special Committee 228 is charged with leading the development of draft Minimum Operational Performance Standards (MOPS) for UAS DAA Systems. NASA, as a participating member of RTCA SC-228 is committed to supporting the development and validation of draft requirements for DAA alerting and guidance systems. This presentation contains the results of two combinatorial encounter analysis studies using NASA's SAA Control fast-time simulation capability for this purpose. In these studies, encounters between two aircraft were simulated one at a time for the full factorial combination of encounter geometries (e.g., encounter angle, CPA offset) and aircraft performance (e.g., ownership and intruder ground speeds and vertical rates). The first study analyzes the relationships (e.g., timeline) between the different alerting-safety regions in the SC-228 MOPS (in order of increasing severity): 1) DAA warning alert, 2) well clear recovery (WCR) guidance, 3) DAA-Collision Avoidance (CA), and 4) TCAS RA. This study will focus primarily on encounter situations in which TCAS RA occurs prior to any of the other alerting-safety boundaries. In particular, this study will investigate whether using vertical distance or vertical distance at closest point of approach (i.e., vertical miss distance or VMD) is more appropriate for the definition of the DAA-CA region. In addition, cases where transitions between different regions skip an intermediate region will be analyzed. The second study in this presentation explores a proposal to use an altitude rate error threshold to determine if vertical maneuvers are acceptable for DAA WCR guidance against non-cooperative intruders. This study incorporates the radar from the Honeywell sensor model and examines a series of pairwise encounters between a non-cooperative intruder and a UAS ownship, with different combinations of intruder states and ownship performance levels. The study uses SAA Control as a simulation platform and pilot model, and Omnibands to provide DWC recovery guidance. Two simulation sets, one that allows vertical DWC recovery guidance and one that does not, are compared to determine if encounters with altitude rate errors above 250 feet-per-minute are more likely to have more severe losses of well clear, as determined by the Loss of Well-Clear Severity metric.

SaaControl↗
NASA NTRS1991

Development of a calibration workstation for SIR-C

The paper describes the status of a comprehensive synthetic aperture radar (SAR) software package developed specifically to aid the calibration of a multifrequency and multipolarization radar like the Shuttle Imaging Radar, SIR-C. The primary data types processed are engineering telemetry, point targets (corner reflectors and polarimetric active radar calibrators), distributed targets (clutter), tone-generators, and ground receivers. The parameters derived to aid the calibration of the production processor include measurements of relative radiometric channel to channel imbalance, absolute calibration constants, antenna pattern corrections, noise levels, polarimetric cross-talk, and geometric offsets. The software reports standard performance measurements such as resolution, peak and integrated sidelobes, radiometric response accuracy, and geometrical distortions such as scale errors, position bias and standard deviation, and image skew. Furthermore, the inclusion of software to allow updates of the shuttle-state vector (position and velocity) is considered.

Madsen, S. N.↗
DOE OSTI2024

MVP: a modular viromics pipeline to identify, filter, cluster, annotate, and bin viruses from metagenomes

While numerous computational frameworks and workflows are available for recovering prokaryote and eukaryote genomes from metagenome data, only a limited number of pipelines are designed specifically for viromics analysis. With many viromics tools developed in the last few years alone, it can be challenging for scientists with limited bioinformatics experience to easily recover, evaluate quality, annotate genes, dereplicate, assign taxonomy, and calculate relative abundance and coverage of viral genomes using state-of-the-art methods and standards. Here, we describe Modular Viromics Pipeline (MVP) v.1.0, a user-friendly pipeline written in Python and providing a simple framework to perform standard viromics analyses. MVP combines multiple tools to enable viral genome identification, characterization of genome quality, filtering, clustering, taxonomic and functional annotation, genome binning, and comprehensive summaries of results that can be used for downstream ecological analyses. Overall, MVP provides a standardized and reproducible pipeline for both extensive and robust characterization of viruses from large-scale sequencing data including metagenomes, metatranscriptomes, viromes, and isolate genomes. As a typical use case, we show how the entire MVP pipeline can be applied to a set of 20 metagenomes from wetland sediments using only 10 modules executed via command lines, leading to the identification of 11,656 viral contigs and 8,145 viral operational taxonomic units (vOTUs) displaying a clear beta-diversity pattern. Further, acting as a dynamic wrapper, MVP is designed to continuously incorporate updates and integrate new tools, ensuring its ongoing relevance in the rapidly evolving field of viromics. MVP is available at https://gitlab.com/ccoclet/mvp and as versioned packages in PyPi and Conda.

59 BASIC BIOLOGICAL SCIENCES↗
NASA NTRS1980

Project FIRES. Volume 1: Program Overview and Summary, Phase 1B

Overall performance requirements and evaluation methods for firefighters protective equipment were established and published as the Protective Ensemble Performance Standards (PEPS). Current firefighters protective equipment was tested and evaluated against the PEPS requirements, and the preliminary design of a prototype protective ensemble was performed. In phase 1B, the design of the prototype ensemble was finalized. Prototype ensembles were fabricated and then subjected to a series of qualification tests which were based upon the PEPS requirements. Engineering drawings and purchase specifications were prepared for the new protective ensemble.

Abeles, F. J.↗
NASA NTRS2006

ISO 15859 Propellant and Fluid Specifications: A Review and Comparison with Military and NASA Specifications

This work presents an overview of the International Organization for Standardization (ISO) 15859 International Standard for Space Systems Fluid Characteristics, Sampling and Test Methods Parts 1 through 13 issued in June 2004. These standards establish requirements for fluid characteristics, sampling, and test methods for 13 fluids of concern to the propellant community and propellant characterization laboratories: oxygen, hydrogen, nitrogen, helium, nitrogen tetroxide, monomethylhydrazine, hydrazine, kerosene, argon, water, ammonia, carbon dioxide, and breathing air. A comparison of the fluid characteristics, sampling, and test methods required by the ISO standards to the current military and NASA specifications, which are in use at NASA facilities and elsewhere, is presented. Many ISO standards composition limits and other content agree with those found in the applicable parts of NASA SE-S-0073, NASA SSP 30573, military performance standards and details, and Compressed Gas Association (CGA) commodity specifications. The status of a current project managed at NASA Johnson Space Center White Sands Test Facility (WSTF) to rewrite these documents is discussed.

Greene, Ben↗
NASA NTRS2015

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The engineering development of the new Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these spacecraft systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex system engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in specialized Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model based algorithms and their development lifecycle from inception through Flight Software certification are an important focus of this development effort to further insure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. NASA formed a dedicated M&FM team for addressing fault management early in the development lifecycle for the SLS initiative. As part of the development of the M&FM capabilities, this team has developed a dedicated testbed that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. Additionally, the team has developed processes for implementing and validating these algorithms for concept validation and risk reduction for the SLS program. The flexibility of the Vehicle Management End-to-end Testbed (VMET) enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS. The intent of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software development infrastructure and its related testing entities. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test cases into flight software compounded with potential human errors throughout the development lifecycle. Risk reduction is addressed by the M&FM analysis group working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses that can be tested in VMET to ensure that failures can be detected, and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes.

Trevino, Luis↗
NASA NTRS2015

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The development of the Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large complex systems engineering challenge being addressed in part by focusing on the specific subsystems handling of off-nominal mission and fault tolerance. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML), the Mission and Fault Management (M&FM) algorithms are crafted and vetted in specialized Integrated Development Teams composed of multiple development disciplines. NASA also has formed an M&FM team for addressing fault management early in the development lifecycle. This team has developed a dedicated Vehicle Management End-to-End Testbed (VMET) that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. The flexibility of VMET enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the algorithms utilizing actual subsystem models. The intent is to validate the algorithms and substantiate them with performance baselines for each of the vehicle subsystems in an independent platform exterior to flight software test processes. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test processes. Risk reduction is addressed by working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and detection and responses that can be tested in VMET and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM. The plan for VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗
NASA NTRSDate not supplied

Human Capabilities Assessments for Autonomous Missions: A Multi-Team Research Effort to Reduce Risk in the Human-System Integration Architecture for Future Deep-Space Missions

In future exploration missions beyond low earth-orbit, crew will have to execute complex operations and respond to off-nominal events, without real-time support from Mission Control. It is anticipated that increased reliance on automated systems, including human-centric vehicle and information architecture, will need to be designed to support the crew; increased risk to performance, health, and safety may occur if these are not implemented appropriately. The Human Factors and Behavioral Performance Element (HFBP) in the NASA Human Research Program supports research to characterize and mitigate such human health and performance risks, including the Risk of Adverse Outcome Due to Inadequate Human Systems Integration Architecture (HSIA). The HSIA risk addresses the integration of onboard capability and the crew roles and responsibilities necessary to enable the crew to respond effectively and efficiently in the increasingly autonomous mission operations environment. In 2017, HFBP released the “Human Capabilities Assessments for Autonomous Missions” (HCAAM) research topic to address HSIA related questions. HCAAM is a major NASA research effort that has assembled a multidisciplinary team from seven institutions to work closely with design and engineering efforts on research towards developing and refining human performance standards, guidelines and automation tools. The scientific focus is on quantitative assessment of human capabilities relevant to future deep-space missions during which earth/spacecraft communication is so delayed and intermittent that the crew must be able to function autonomously. The integrated strategy of the HCAAM project characterizes human capabilities and limitations related to potential performance decrements during long duration exploration mission spaceflight as relevant to both routine and complex task performance; defines system characteristics that reduce the likelihood or impact of potential decrements in human performance capabilities; performs integrated assessment of intelligent system responses within the context of an operational environment with relevant NASA tools, systems, and data structures in order to determine positive or negative interactions and validate recommended approaches; and proposes specific updates to existing standards and guidelines for inclusion in NASA handbooks for the design of future spacecraft intelligent systems that provide crew performance assessment/feedback, and to also serve as decision-support aids for the onboard crew (i.e., NASA-STD-3001, and NASA/SP-Human Integration Design Handbook (HIDH)). The scientific research vectors being addressed by the seven HCAAM teams include: - crew task performance (accuracy, efficiency) (crew + automation) - crew performance (accuracy, efficiency) - crew Situation Awareness - procedure design and multi-modal enhancement - concurrent tasking (mixed manual + some level of autonomy) - task handover - crew self-planning and time-lining - task design - trust in automation, real-time calibration - human multi-sensory feedback and guidance - human trust in on-board software-based intelligent assistants - virtual assistants The presentation will highlight plans and progress made in each of these research areas as well as the methods by which surrogate astronaut crews in the NASA JSC HERA spaceflight analog facility will function as human test subjects for all of the HCAAM research projects.

HCAAM VNSCOR↗
DOE OSTI2022

Environmental design of low-head run-of-river hydropower in the United States: A review of facility design models

We state that the goal of run-of-river hydropower is to produce cost-competitive renewable electricity with minimal disruption of the natural riverine ecosystem. Modeling and feasibility analysis of alternative design options are crucial for developing new run-of-river hydropower projects. Our review shows that existing run-of-river hydropower design models focus on maximizing economic potential at high-head diversion schemes with limited consideration of environmental outcomes. Since nearly three-quarters of new hydropower potential in the United States is found at low-head sites and environmental performance standards are imperative to project success, new models are needed to address the multi-dimensional design challenges at these sites. To aid in formulating holistic models, we synthesize the performance objectives and design variables related to early-stage run-of-river facility design. The objectives span six potential impact areas, including hydrologic alteration, sediment continuity, water quality, aquatic species passage, social, and economic. Based on these reviews, we identify three key areas to enhance the capabilities of run-of-river hydropower design models. These are 1) expanded model formulations, 2) assessment of barrier effects, and 3) explicit environmental objectives. The resulting modeling improvements would accelerate the identification of run-of-river hydropower designs that minimize environmental impacts, promote economic competitiveness, and incorporate the value of non-power benefits.

13 HYDRO ENERGY↗
NASA NTRS1985

On orbit mission planning using the shuttle trajectory and launch window expert system

With the Space Transportation System (STS) entering the operational era, the need for standardized, automated, mission planning computer tools has become apparent. In order to support an increased flight rate without an increase in manpower, quicker and more efficient methods are needed to perform standard tasks. The Shuttle Trajectory and Launch Window Expert System (STALEX) was developed to automate many aspects of early mission planning for space shuttle missions carrying geosynchronous communications satellites. Most of the commercial Shuttle missions planned for the next 3 years will carry at least one of this type of satellite. The applications of STALEX include payload deployment scheduling, launch window analysis, orbital trajectory determination, and landing opportunity selection.

Ahlf, P. R.↗
NASA NTRS2019

Terminal Area Test Vector Development

This presentation provides an overview of work being done to develop test vectors for the terminal area, in coordination with RTCA Special Committee 228, an organization developing the Minimum Operational Performance Standards (MOPS) for Unmanned Aircraft Systems (UAS) Detect and Avoid (DAA) systems. The work leverages existing encounter data to develop a set of encounters to be used to define and refine both performance-based and functionally-based terminal area MOPS requirements. The encounter set would be used across various organizations supporting MOPS terminal area requirements development to provide some level of consistency in terms of terminal area assumptions. The work will investigate other potentially applicable data sets and make any similarly needed adjustments to arrive at a consolidated set of terminal area encounters.

terminal area↗
NASA NTRS2017

Progress on the Development of the UAS C2 Link and Supporting Spectrum - from LOS to BLOS

In order to provide for the safe integration of unmanned aircraft systems (UAS) into the National Airspace System, the control and non-payload communications (CNPC) link connecting the ground-based pilot with the unmanned aircraft must be highly reliable and robust, based upon standards that enable certification. Both line-of-sight (LOS) links using terrestrial-based communications and beyond-line-of-sight (BLOS) links using satellite communications are required to support UAS operations. The development of standards has been undertaken by RTCA Special Committee 228 (SC-228), with supporting technical data developed by NASA under the UAS in the National Airspace (NAS) Project. As a result of this work minimum operational performance standards (MOPS) have been completed and published for the LOS CNPC system. The second phase of work, for both NASA and RTCA involves the BLOS CNPC systems. The development of technical data to support MOPS development for UAS BLOS satellite-based CNPC links has now been initiated by NASA, and RTCA SC-228 has organized itself to begin the MOPS development process. This paper will provide an overview of the work that has been completed to date by the Communications Subproject in support of LOS C2 communications for UAS followed by an update of plans and progress for the BLOS phase of the project, with the focus on the UAS C2 spectrum aspects.

Pilotless aircraft↗
NASA NTRS2016

System Performance of an Integrated Airborne Spacing Algorithm with Ground Automation

The National Aeronautics and Space Administration's (NASA's) first Air Traffic Management (ATM) Technology Demonstration (ATD-1) was created to facilitate the transition of mature ATM technologies from the laboratory to operational use. The technologies selected for demonstration are the Traffic Management Advisor with Terminal Metering (TMA-TM), which provides precise time-based scheduling in the Terminal airspace; Controller Managed Spacing (CMS), which provides controllers with decision support tools to enable precise schedule conformance; and Interval Management (IM), which consists of flight deck automation that enables aircraft to achieve or maintain precise spacing behind another aircraft. Recent simulations and IM algorithm development at NASA have focused on trajectory-based IM operations where aircraft equipped with IM avionics are expected to achieve a spacing goal, assigned by air traffic controllers, at the final approach fix. The recently published IM Minimum Operational Performance Standards describe five types of IM operations. This paper discusses the results and conclusions of a human-in-the-loop simulation that investigated three of those IM operations. The results presented in this paper focus on system performance and integration metrics. Overall, the IM operations conducted in this simulation integrated well with ground-based decisions support tools and certain types of IM operational were able to provide improved spacing precision at the final approach fix; however, some issues were identified that should be addressed prior to implementing IM procedures into real-world operations.

Swieringa, Kurt A.↗
NASA NTRS2016

A Cognitive Systems Engineering Approach to Developing HMI Requirements for New Technologies

This document examines the challenges inherent in designing and regulating to support human-automation interaction for new technologies that will deployed into complex systems. A key question for new technologies, is how work will be accomplished by the human and machine agents. This question has traditionally been framed as how functions should be allocated between humans and machines. Such framing misses the coordination and synchronization that is needed for the different human and machine roles in the system to accomplish their goals. Coordination and synchronization demands are driven by the underlying human-automation architecture of the new technology, which are typically not specified explicitly by the designers. The human machine interface (HMI) which is intended to facilitate human-machine interaction and cooperation, however, typically is defined explicitly and therefore serves as a proxy for human-automation cooperation requirements with respect to technical standards for technologies. Unfortunately, mismatches between the HMI and the coordination and synchronization demands of the underlying human-automation architecture, can lead to system breakdowns. A methodology is needed that both designers and regulators can utilize to evaluate the expected performance of a new technology given potential human-automation architectures. Three experiments were conducted to inform the minimum HMI requirements a detect and avoid system for unmanned aircraft systems (UAS). The results of the experiments provided empirical input to specific minimum operational performance standards that UAS manufacturers will have to meet in order to operate UAS in the National Airspace System (NAS). These studies represent a success story for how to objectively and systematically evaluate prototype technologies as part of the process for developing regulatory requirements. They also provide an opportunity to reflect on the lessons learned from a recent research effort in order to improve the methodology for defining technology requirements for regulators in the future. The biggest shortcoming of the presented research program was the absence of the explicit definition, generation and analysis of potential human-automation architectures. Failure to execute this step in the research process resulted in less efficient evaluation of the candidate prototypes technologies in addition to the complete absence of different approaches to human-automation cooperation. For example, all of the prototype technologies that were evaluated in the research program assumed a human-automation architecture that relied on serial processing from the automation to the human. While this type of human-automation architecture is typical across many different technologies and in many different domains, it ignores different architectures where humans and automation work in parallel. Defining potential human-automation architectures a priori also allows regulators to develop scenarios that will stress the performance boundaries of the technology during the evaluation phase. The importance of adding this step of generating and evaluating candidate human-automation architectures prior to formal empirical evaluation is discussed.

human systems integration↗
DOE OSTI2023

PV Validation Hub

The Validation Hub will be a clearinghouse for the transfer of novel algorithms and software from the PV research community to industry. Potential algorithms tested in the Hub could include the estimation of various PV loss factors and the detection of various operational issues. The primary function of the Hub will be for developers to submit executable code which will run on hosted data sets. Developers will receive private reports on the accuracy and performance (e.g., run-time) of the submitted algorithms, and public high level summaries will be hosted. These summaries will indicate the organization who submitted the algorithm (e.g., links to GitHub pages, documentation websites, etc.), high-level accuracy metrics, and standardized performance metrics. These results will be stored in a publicly available database, accessible through the Hub, with the ability for users to sort and filter the results. In short, the Hub will be presented to public users as a collection of interactive leaderboards, organized around specific analysis tasks pertinent to the PV data science community. These tasks include things such as the estimation of various PV loss factors and the detection of various operational issues. We will present progress on the development of this hub, including preliminary results of comparative validation of PV data science algorithms and progress towards building the platform itself.

algorithm↗
DOE OSTI2026

Digital Assurance for Grid Reliability in the Era of Large Load Growth

The rapid expansion of large electric loads is reshaping the operational and regulatory landscape of the U.S. electric grid. These facilities are reaching new scales of expansion, now exceeding a gigawatt per site, and their highly sensitive, digitally driven behaviors introduce new reliability risks. Recent grid events, including large load losses following routine transmission disturbances, highlight the consequences of limited ride-through capability, inconsistent protection settings, inadequate modeling, and lack of behind-the-meter visibility. Parallels to earlier integration challenges of new grid technologies suggest that the grid’s existing processes, standards, and interconnection frameworks are no longer adequate for emerging large loads. This brief synthesizes lessons from the evolution of inverter-based resource regulation and applies them to large-load integration. It identifies critical gaps in modeling accuracy, interconnection processes, performance standards, and compliance mechanisms. Technical recommendations emphasize advanced monitoring, improved modeling, coordinated communication protocols, modernized substations, and structured behind-the-meter control schemes. Collectively, these measures provide a roadmap to maintain bulk power system reliability while enabling the continued growth of large, electrified digital infrastructure.

24 - POWER TRANSMISSION AND DISTRIBUTION↗
NASA NTRS2021

Detect-and-Avoid Surveillance Range Requirements for Electro-Optical/Infra-Red Sensors

A detect-and-avoid (DAA) system provides surveillance, alerting, and maneuver guidance (referred to as guidance in this report) that are critical to an unmanned aircraft system’s (UAS) ability to maintain separation from manned aircraft and other unmanned aircraft. The last decade has seen significant progress in the development of DAA requirements, spearheaded by RTCA Special Committee 228 (SC228) and subsequently by other standards organizations such as EUROCAE and ASTM. SC-228’s development of DAA requirements assumes the UAS follows instrument flight rules (IFR) and has a remote pilot or operator in the loop. As of the publication of this document, the SC-228’s latest Minimum Operational Performance Standards (MOPS) for DAA, versioned as DO-365B [1], DAA systems use onboard and/or ground surveillance systems to detect traffic. The surveillance systems must detect both cooperative and non-cooperative air traffic. Cooperative traffic are vehicles that have a broadcasting transponder, while non-cooperative traffic do not, and so must be detected via radar or other sensors. A DAA system’s alerting and guidance functions alert the pilot/operator in the loop of potential hazards, such as intruder aircraft, and provide maneuver solutions which help the pilot/operator avoid or mitigate observed hazards. A UAS pilot is expected to coordinate with air traffic control (ATC) before executing a conflict avoidance maneuver if the type of alert is not urgent enough to require an immediate maneuver.

uncrewed aviation systems↗
NASA NTRS2016

FT4 Data Analysis Summary (SSI-ARC)

Standards for Unmanned Aircraft System (UAS) Detect-and-Avoid (DAA) systems are currently being developed under the auspices of the RTCA Special Committee 228 (SC-228). To support the development of these standards, a series of flight tests has been conducted at NASAs Armstrong Flight Research Center (NASA-AFRC). The fourth in this series of flight test activities (Flight Test 4, or simply FT4) was conducted during the Spring and Summer of 2016. FT4 supported the objectives of numerous organizations working toward UAS DAA Minimum Operational Performance Standards (MOPS) and UAS DAA Radar MOPS. The summary provided herein is limited to the objectives, analysis and conclusions of the NASA Ames Research Center (NASA-ARC) SSI team toward the refinement of UAS DAA MOPS. This document provides a high-level overview of FT4 and the SSI-ARC objectives, a summary of the data analysis methodology and recommendations for UAS DAA MOPS refinements based on the data analysis results. A total of 72 encounters were flown to support SSI-ARC objectives. Test results were generally consistent with acceptable UAS DAA system performance and will be considered in broader SC-228 requirements validation efforts. Observed alert lead times indicated acceptable UAS DAA alerting performance. Effective interoperability between the UAS DAA system and the Traffic Alert and Collision Avoidance System (TCAS) was observed with one notable exception: TCAS Resolutions Advisories (RA) were observed in the absence of any DAA alert on two occasions, indicating the need for alert parameter refinement. Findings further indicated the need for continued work in the areas of DAA Well Clear Recovery logic and alert stability for Mode-C-only intruders. Finally, results demonstrated a high level of compliance with a set of evaluation criteria designed to provide anecdotal evidence of acceptable UAS DAA system performance.

UAS Test Flight↗