Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operations Standards”

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

Project Profile: Hydrogen Fuel Cell Mobile Lighting Tower (HFCML)

NASA is committed to finding innovative solutions that improve the operational performance of ground support equipment while providing environment and cost benefits, as well. Through the Hydrogen Fuel Cell Mobile Lighting Tower (HFCML) project, NASA gained operational exposure to a novel application of high efficiency technologies. Traditionally, outdoor lighting and auxiliary power at security gates, launch viewing sites, fallback areas, outage support, and special events is provided by diesel generators with metal halide lights. Diesel generators inherently contribute to C02, NOx, particulate emissions, and are very noisy. In 2010, engineers from NASA's Technology Evaluation for Environmental Risk Mitigation Principal Center (TEERM) introduced KSC operations to a novel technology for outdoor lighting needs. Developed by a team led by Sandia National Laboratory (SNL), the technology pairs a 5kW hydrogen fuel cell with robust high efficiency plasma lights in a towable trailer. Increased efficiency, in both the fuel cell power source and lighting load, yields longer run times between fueling operations while providing greater auxiliary power. Because of the unit's quiet operation and no exhaust fumes, it is capable of being used indoors and in emergency situations, and meets the needs of all other operational roles for metal halide/diesel generators. The only discharge is some water and warm air. Environmental benefits include elimination of diesel particulate emissions and estimated 73% greenhouse gas emissions savings when the hydrogen source is natural gas (per GREET model). As the technology matures the costs could become competitive for the fuel cell units which are approximately 5 times diesel units. Initial operational . concerns included the hydrogen storage tanks and valves, lightning safety/grounding, and required operating and refueling procedures. TEERM facilitated technical information exchange (design drawings, technical standards, and operations manuals) necessary for KSC hydrogen system experts to approve use of the HFCML unit, including initiating the environmental checklist (i.e. exterior lighting waiver due to sea turtles), and development of operations and maintenance instructions. TEERM worked with SNL to establish a bailment agreement for KSC to utilize a Beta unit as part of normal Center Operations for a period of twelve months.

McLaughlin, Russell↗

Alternative Aviation Fuel Experiment (AAFEX)

The rising cost of oil coupled with the need to reduce pollution and dependence on foreign suppliers has spurred great interest and activity in developing alternative aviation fuels. Although a variety of fuels have been produced that have similar properties to standard Jet A, detailed studies are required to ascertain the exact impacts of the fuels on engine operation and exhaust composition. In response to this need, NASA acquired and burned a variety of alternative aviation fuel mixtures in the Dryden Flight Research Center DC-8 to assess changes in the aircraft s CFM-56 engine performance and emission parameters relative to operation with standard JP-8. This Alternative Aviation Fuel Experiment, or AAFEX, was conducted at NASA Dryden s Aircraft Operations Facility (DAOF) in Palmdale, California, from January 19 to February 3, 2009 and specifically sought to establish fuel matrix effects on: 1) engine and exhaust gas temperatures and compressor speeds; 2) engine and auxiliary power unit (APU) gas phase and particle emissions and characteristics; and 3) volatile aerosol formation in aging exhaust plumes

Anderson, B. E.↗

Validation of Minimum Display Requirements for a UAS Detect and Avoid System

The full integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS), a prerequisite for enabling a broad range of public and commercial UAS operations, presents several technical challenges to UAS developers, operators and regulators. A primary barrier is the inability for UAS pilots (situated at a ground control station, or GCS) to comply with Title 14 Code of Federal Regulations sections 91.111 and 91.113, which require pilots to see and avoid other aircraft in order to maintain well clear. The present study is the final in a series of human-in-the-loop experiments designed to explore and test the various display and alerting requirements being incorporated into the minimum operational performance standards (MOPS) for a UAS-specific detect and avoid system that would replace the see and avoid function required of manned aircraft. Two display configurations were tested - an integrated display and a standalone display - and their impact on pilot response times and ability to maintain DAA well clear were compared. Results indicated that the current draft of the MOPS result in high-level performance and did not meaningfully differ by display configuration.

unmanned aircraft systems↗

HPC ODA Commons [SWR-26-003]

HPC ODA Commons is a community-driven platform for standardizing HPC operational data analytics. HPC sites generate enormous volumes of operational data - scheduler logs, accounting records, monitoring streams - but turning that data into actionable insight is needlessly hard. Each site builds bespoke parsers, schemas, and evaluation pipelines. Results can't be compared across institutions. Promising analytics ideas stay siloed because there's no shared language for describing the data, the experiments, or the outcomes. HPC ODA Commons fixes this by establishing community-governed contracts - versioned schemas, canonical artifacts, and benchmark recipes - that make ODA workflows discoverable, reproducible, and comparable. It pairs these standards with a practical, CLI-first toolkit that lets operators and researchers go from raw logs to standardized results without sending data off-cluster.

Menear, Kevin [National Laboratory of the Rockies ↗

Consultative Committee for Space Data Systems recommendation for space data system standards: Telecommand. Part 2.1: Command operation procedures

This recommendation contains the detailed specification of the logic required to carry out the Command Operations Procedures of the Transfer Layer. The Recommendation for Telecommand--Part 2, Data Routing Service contains the standard data structures and data communication procedures used by the intermediate telecommand system layers (the Transfer and Segmentation Layers). In particular, it contains a brief description of the Command Operations Procedures (COP) within the Transfer Layer. This recommendation contains the detailed definition of the COP's in the form of state tables, along with definitions of the terms used. It is assumed that the reader of this document is familiar with the data structures and terminology of part 2. In case of conflict between the description of the COP's in part 2 and in this recommendation, the definition in this recommendation will take precedence. In particular, this document supersedes section 4.3.3.1 through 4.3.3.4 of part 2.

Source record↗

Simulation and Flight Test Data Collection to Support Phase 1 Detect-and-Avoid MOPS

The UAS Integration into the NAS (UASNAS) project is studying the minimum operational performance standards for unmanned aerial system (UAS) detect-and-avoid (DAA) systems in order to operate in the National Airspace System (NAS). The project is executing a series of fast-time simulation, human-in-the-loop experiments, and flight tests in support of this effort. Armstrong Flight Research Center is hosting a VIP Day in conjunction with the UAS-NAS Project's Flight Test 4 activity, and the Ames Project Engineer (or designate) will be presenting a briefing. This briefing will review the data collection and analysis activities for Flight Test 4 within the Separation assurance-Sense-and-avoid Interoperability (SSI) team.

data analysis↗

Validation of Minimum Display Requirements for a UAS Detect and Avoid System

The full integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS), a prerequisite for enabling a broad range of public and commercial UAS operations, presents several technical challenges to UAS developers, operators and regulators. A primary barrier is the inability for UAS pilots (situated at a ground control station, or GCS) to comply with Title 14 Code of Federal Regulations sections 91.111 and 91.113, which require pilots to “see and avoid” other aircraft in order to maintain well clear. UAS pilots’ removal from the flight deck of the aircraft necessitates the development of a UAS-specific system for detecting nearby traffic and displaying traffic information to the pilot to support their ability to maintain an objectively defined “DAA well clear” threshold from other aircraft. This new UAS-specific function of remaining DAA well clear is called traffic avoidance. The resulting Detect and Avoid (DAA) system, however, will be subject to a collection of requirements that manufacturers will be obligated to meet in order to certify their equipment. RTCA Special Committee 228 (SC-228), a consortium of representatives from government, industry and academia, is responsible for developing and documenting the Minimum Operational Performance Standards (MOPS) for UAS DAA systems. The present study is the final in a series of human-in-the-loop (HITL) experiments designed to explore and test the various display and alerting requirements being incorporated into the DAA MOPS. Whereas the prior DAA HITLs examined a wide variety of DAA display features and concepts, the current experiment aims to validate the latest minimum display requirements for Phase 1 of the DAA MOPS. Rather than test different display concepts, this study tests two configurations of a MOPS-compatible DAA display: a version that is integrated into the primary navigation and control display of the GCS and a version that is physically separated from the primary display. This manipulation tests the draft minimum requirement that allows the DAA traffic display to be a separate, or standalone, configuration. This type of configuration is a more achievable near-term technology solution since it does not stipulate additional certification or integration requirements on UAS manufacturers. However, a standalone display configuration has the potential to result in pilot performance issues resulting from the cognitive costs of switching between the primary DAA display and the primary navigation and control display. This configuration is also particularly susceptible to errors if the displays are in different orientations (e.g., north-up versus track-up). Both the integrated and standalone display configurations were presented to 16 active UAS pilots in a medium-fidelity simulation, which included confederate air traffic controllers and pseudo pilots operating simulated manned traffic. Pilots were tasked with navigating two different mission routes while maintaining DAA well clear with scripted conflicts. Pilot response times (i.e., measured response) and ability to remain DAA well clear are reported. Primary results indicate that both display configurations resulted in favorable response times and well clear rates. While there were clear trends of pilots objectively performing better in the integrated display condition, with several measured response metrics reaching statistical significance, the differences between the two displays were typically moderate. While the primary variable of DAA display location did not have an especially large impact on pilot performance on its own, when examined alongside the type of DAA threat the pilot was facing (a caution-level versus a warning-level alert), the response time benefits associated with the integrated display were amplified. The implications of these American Institute of Aeronautics and Astronautics 2 results on the Phase 1 DAA MOPS and the connection of this data to previous studies is also discussed.

detect and avoid↗

A Review of Current and Prospective Factors for Classification of Civil Unmanned Aircraft Systems

While progress is being made on integrating unmanned aircraft systems (UAS) into our national airspace on a broad scale, much work remains to establish appropriate certification standards and operational procedures, particularly with respect to routine commercial operations. This paper summarizes research to examine the extent to which today's civil aircraft taxonomy applies to UAS, and, if needed, how that taxonomy could be amended to better cover different UAS designs and operations. Factors that shape the current taxonomy, as defined in the Federal Aviation Regulations, were assessed for applicability to UAS, potential incompatibilities were identified, and additional factors were proposed that might be useful for an updated aircraft taxonomy intended to cover UAS. The results suggest the possibility of constructing new groups in the taxonomy for UAS under a restricted category that share common airworthiness standards. Establishing distinct groups for UAS and associated standards that enable low risk operations for compensation or hire could be a timely step toward full integration. Such a step would allow the civil aviation industry and regulators to gain valuable experience with UAS while carefully controlling access and potential harm to the aviation system as a whole.

Hayhurst, Kelly J.↗

Determination of the Critical Parameters for Remote Microscope Control

As part of a program to determine the capabilities of Telescience as applied to Microgravity Materials Science the need for a remotely controlled microscope was recognized. For this purpose we equipped a microscope with an X-Y-Z positioning device and motors on the zoom and focus controls. Computer control of these devices allowed remote operation. A standard TV camera was mounted to the computer controlled video board which could compress the image in resolution and grey scale. The operator control console was programmed to display three still video pictures as well as provide command access. A standard data transfer network was used to transmit the video data files and the command interaction was via a high speed phone modem. This system, with the microscope in the Microgravity Materials Science Laboratory (MMSL) at LeRC and the control at RPI, was used to determine the accuracy of setting, time required to achieve setting and the operator ease factor. It was found that the focus setting could be established well within the resolution limit of the TV system and that each motion took about 50 seconds and approximately 12 minutes was required to reach ?best? focus. These times could be reduced significantly with operator experience. The operators were provided with ancillary equipment which provided assistance in making the necessary decisions and they reported satisfaction with the control.

Hahn, R. C.↗

Final Overview of ACES Simulation for Evaluation SARP Well-Clear Definitions

The UAS in the NAS project is studying the minimum operational performance standards for unmanned aerial systems (UAS's) detect-and-avoid (DAA) system in order to operate in the National Airspace System. The DoD's Science and research Panel (SARP) Well-Clear Workshop is investigating the time and spatial boundary at which an UAS violates well-clear. NASA is supporting this effort through use of its Airspace Concept Evaluation System (ACES) simulation platform. This briefing presents the final results to the SARP, which will be used to judge the three candidate well-clear definitions, and for the selection of the most operationally suitable option.

detect and avoid↗

Overview of Sense and Avoid/Separation Assurance Interoperability (SSI)

The UAS in the NAS project is studying the minimum operational performance standards for unmanned aerial systems (UAS's) detect-and-avoid (DAA) system in order to operate in the National Airspace System. The project is executing a series of fast-time simulation, human-in-the-loop experiments, and flight test in support of this effort. Officials of the Swiss Government (Peter Winter, Director of Aeronautical Systems, and Michel Godinat, Head of the Certification Office) are visiting NASA to become more familiar with the advances being made to integrate UAS into civilian airspace. This briefing will review the activities and results over the past 3 years within the Separation AssuranceSense-and-Avoid Interoperability team.

Santiago, Confesor↗

ACES Preliminary Results Supporting Selection of SARP Well-Clear Definitions

The UAS in the NAS project is studying the minimum operational performance standards for unmanned aerial systems (UAS's) detect-and-avoid (DAA) system in order to operate in the National Airspace System. The DoD's Science and research Panel Well-Clear Workshop is investigating the time and spatial boundary at which an UAS violates well-clear. NASA is supporting this effort through use of its Airspace Concept Evaluation System (ACES) simulation platform. This presentation reviews how the simulation was used to support this work, lessons learned during the experiment, and introduces preliminary results.

well-clear↗

Range Flight Safety Requirements

The purpose of this NASA Technical Standard is to provide the technical requirements for the NPR 8715.5, Range Flight Safety Program, in regards to protection of the public, the NASA workforce, and property as it pertains to risk analysis, Flight Safety Systems (FSS), and range flight operations. This standard is approved for use by NASA Headquarters and NASA Centers, including Component Facilities and Technical and Service Support Centers, and may be cited in contract, program, and other Agency documents as a technical requirement. This standard may also apply to the Jet Propulsion Laboratory or to other contractors, grant recipients, or parties to agreements to the extent specified or referenced in their contracts, grants, or agreements, when these organizations conduct or participate in missions that involve range flight operations as defined by NPR 8715.5.1.2.2 In this standard, all mandatory actions (i.e., requirements) are denoted by statements containing the term “shall.”1.3 TailoringTailoring of this standard for application to a specific program or project shall be formally documented as part of program or project requirements and approved by the responsible Technical Authority in accordance with NPR 8715.3, NASA General Safety Program Requirements.

Flight↗

Interoperable Services to Mitigate Lunar Position, Navigation, and Timing Challenges

Across the Earth, both civilian and government endeavors enjoy a built-in reliance on a position, navigation, and timing (PNT) infrastructure to which they are largely blind. Whether walking, driving, flying, or orbiting, Earth-centric PNT systems that have evolved over decades provide a core functionality to which we have grown accustomed for these pursuits. As NASA joins with other government space agencies and commercial partners to return humans to the Moon in a sustained manner within the current decade, expectations for PNT knowledge and timeliness at the Moon rival those on Earth. The need exists to develop a viable lunar-centric PNT infrastructure to support the planned human and robotic exploits. Navigating within the influence of the Moon presents its own set of challenges. Identification, understanding, and use of a unified reference frame and time system on which navigation is based becomes a fundamental need at the Moon. In addition to the unified foundational elements, measurement liability, dynamic conditions that require Earth-independent autonomous operations, and standards for PNT signals and message-based data exchange each represent distinct challenges to navigation in a burgeoning operational lunar environment. The PNT services planned as part of the lunar communications and navigation relay architecture known as LunaNet aid in surmounting the challenges. LunaNet interoperability specifications stipulate standards for signal parameters, messages, and lunar reference systems for PNT services. Within LunaNet’s defined interoperability resides the concept of a Reference Signal to provide communication signals specifically structured to enable measurement of pseudorange, Doppler, and time transfer by the recipient. One such signal type, the Augmented Forward Signal (AFS), functions as the mainstay for LunaNet PNT, while also serving the data needs for ubiquitous broadcast of network access and rapid unscheduled dissemination of alerts and messages. The presence of a geometrically distributed network of orbiting nodes transmitting the AFS forms the basis for the Lunar Augmented Navigation System (LANS), that delivers both radio navigation and data to multiple users in the lunar environment simultaneously. After reviewing the challenges associated with lunar navigation, this paper will describe the concepts and rationale behind the LunaNet PNT services. By borrowing techniques from Earth-centric Global Navigation Satellite Services (GNSS), the Tracking and Data Relay Satellite System, and the Consultative Committee for Space Data Standards, PNT from LunaNet aids to overcome challenges faced for accurate lunar navigation.

LunaNet↗

Interoperable Services to Mitigate Lunar Position, Navigation, and Timing Challenges

Across the Earth, both civilian and government endeavors enjoy a built-in reliance on a position, navigation, and timing (PNT) infrastructure to which they are largely blind. Whether walking, driving, flying, or orbiting, Earth-centric PNT systems that have evolved over decades provide a core functionality to which we have grown accustomed for these pursuits. As NASA joins with other government space agencies and commercial partners to return humans to the Moon in a sustained manner within the current decade, expectations for PNT knowledge and timeliness at the Moon rival those on Earth. The need exists to develop a viable lunar-centric PNT infrastructure to support the planned human and robotic exploits. Navigating within the influence of the Moon presents its own set of challenges. Identification, understanding, and use of a unified reference frame and time system on which navigation is based becomes a fundamental need at the Moon. In addition to the unified foundational elements, measurement liability, dynamic conditions that require Earth-independent autonomous operations, and standards for PNT signals and message-based data exchange each represent distinct challenges to navigation in a burgeoning operational lunar environment. The PNT services planned as part of the lunar communications and navigation relay architecture known as LunaNet aid in surmounting the challenges. LunaNet interoperability specifications stipulate standards for signal parameters, messages, and lunar reference systems for PNT services. Within LunaNet’s defined interoperability resides the concept of a Reference Signal to provide communication signals specifically structured to enable measurement of pseudorange, Doppler, and time transfer by the recipient. One such signal type, the Augmented Forward Signal (AFS), functions as the mainstay for LunaNet PNT, while also serving the data needs for ubiquitous broadcast of network access and rapid unscheduled dissemination of alerts and messages. The presence of a geometrically distributed network of orbiting nodes transmitting the AFS forms the basis for the Lunar Augmented Navigation System (LANS), that delivers both radio navigation and data to multiple users in the lunar environment simultaneously. After reviewing the challenges associated with lunar navigation, this paper will describe the concepts and rationale behind the LunaNet PNT services. By borrowing techniques from Earth-centric Global Navigation Satellite Services (GNSS), the Tracking and Data Relay Satellite System, and the Consultative Committee for Space Data Standards, PNT from LunaNet aids to overcome challenges faced for accurate lunar navigation.

Navigation↗