Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Standardization”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

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

At least 757 records · Page 42
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

Electrical, Electronic, and Electromechanical (EEE) Parts Management and Control Requirements for Space Flight Hardware and Critical Ground Support Equipment...aka... The NASA EEE Parts Standard, NASA-STD 8739.10

Describes development and content of a new NASA Standard for Electrical Electronic and Electromechanical (EEE) parts. This Standard reflects current practices, instead of changing them. Most NASA Centers utilize local documents, but there is minimal consistency across the Agency. A gap analysis clearly shows the differences that exist among the different centers and with respect to the NASA Parts Policy. Once approved, the new standard can be referenced in contracts and agreements with organizations outside of NASA.

Electronic↗
NASA NTRS2015

Commercialization and Standardization Progress Towards an Optical Communications Earth Relay

NASA is planning to launch the next generation of a space based Earth relay in 2025 to join the current Space Network, consisting of Tracking and Data Relay Satellites in space and the corresponding infrastructure on Earth. While the requirements and architecture for that relay satellite are unknown at this time, NASA is investing in communications technologies that could be deployed to provide new communications services. One of those new technologies is optical communications. The Laser Communications Relay Demonstration (LCRD) project, scheduled for launch in 2018 as a hosted payload on a commercial communications satellite, is a critical pathfinder towards NASA providing optical communications services on the next generation space based relay. This paper will describe NASA efforts in the on-going commercialization of optical communications and the development of inter-operability standards. Both are seen as critical to making optical communications a reality on future NASA science and exploration missions. Commercialization is important because NASA would like to eventually be able to simply purchase an entire optical communications terminal from a commercial provider. Inter-operability standards are needed to ensure that optical communications terminals developed by one vendor are compatible with the terminals of another. International standards in optical communications would also allow the space missions of one nation to use the infrastructure of another.

lasers↗
NASA NTRS2016

A Multi-Center Space Data System Prototype Based on CCSDS Standards

Deep space missions beyond earth orbit will require new methods of data communications in order to compensate for increasing Radio Frequency (RF) propagation delay. The Consultative Committee for Space Data Systems (CCSDS) standard protocols Spacecraft Monitor & Control (SM&C), Asynchronous Message Service (AMS), and Delay/Disruption Tolerant Networking (DTN) provide such a method. However, the maturity level of this protocol stack is insufficient for mission inclusion at this time. This Space Data System prototype is intended to provide experience which will raise the Technical Readiness Level (TRL) of this protocol set. In order to reduce costs, future missions can take advantage of these standard protocols, which will result in increased interoperability between control centers. This prototype demonstrates these capabilities by implementing a realistic space data system in which telemetry is published to control center applications at the Jet Propulsion Lab (JPL), the Marshall Space Flight Center (MSFC), and the Johnson Space Center (JSC). Reverse publishing paths for commanding from each control center are also implemented. The target vehicle consists of realistic flight computer hardware running Core Flight Software (CFS) in the integrated Power, Avionics, and Power (iPAS) Pathfinder Lab at JSC. This prototype demonstrates a potential upgrade path for future Deep Space Network (DSN) modification, in which the automatic error recovery and communication gap compensation capabilities of DTN would be exploited. In addition, SM&C provides architectural flexibility by allowing new service providers and consumers to be added efficiently anywhere in the network using the common interface provided by SM&C's Message Abstraction Layer (MAL). In FY 2015, this space data system was enhanced by adding telerobotic operations capability provided by the Robot API Delegate (RAPID) family of protocols developed at NASA. RAPID is one of several candidates for consideration and inclusion in a new international standard being developed by the CCSDS Telerobotic Operations Working Group. Software gateways for the purpose of interfacing RAPID messages with the existing SM&C based infrastructure were developed. Telerobotic monitor, control, and bridge applications were written in the RAPID framework, which were then tailored to the NAO telerobotic test article hardware, a product of Aldebaran Robotics.

Rich, Thomas M.↗
NASA NTRS2016

Modular Power Standard for Space Explorations Missions

Future human space exploration will most likely be composed of assemblies of multiple modular spacecraft elements with interconnected electrical power systems. An electrical system composed of a standardized set modular building blocks provides significant development, integration, and operational cost advantages. The modular approach can also provide the flexibility to configure power systems to meet the mission needs. A primary goal of the Advanced Exploration Systems (AES) Modular Power System (AMPS) project is to establish a Modular Power Standard that is needed to realize these benefits. This paper is intended to give the space exploration community a "first look" at the evolving Modular Power Standard and invite their comments and technical contributions.

Exploration↗
NASA NTRS2017

Using CCSDS Standards to Reduce Mission Costs

NASA's open source Core Flight System (cFS) software framework has been using several Consultative Committee for Space Data Systems (CCSDS) standards since its inception. Recently developed CCSDS standards are now being applied by NASA, ESA and other organizations to streamline and automate aspects of mission development, test, and operations, speeding mission schedules and reducing mission costs. This paper will present the new CCSDS Spacecraft Onboard Interfaces Services (SOIS) Electronic Data Sheet (EDS) standards and show how they are being applied to data interfaces in the cFS software framework, tool chain, and ground systems across a range of missions at NASA. Although NASA is focusing on the cFS, it expected that these technologies are well suited for use in other system architectures and can lower costs for a wide range of both large and small satellites.

Wilmot, Jonathan↗
NASA NTRS2019

A Proposal for Standardized MMOD Shielding for Robotic Spacecraft

NASA robotic spacecraft are required to assess the potential for small debris induced failure for all disposal-critical components. Additional shielding might then be necessary in order to meet the acceptable risk requirement for the overall mission. Traditionally this requirement had been met with little or no additional shielding. Since the introduction of a high density debris population in ORDEM 3.0, some missions, especially those in higher portions of Low Earth Orbit, have needed additional MMOD-specific shielding in order for the mission to meet the requirement. This is a costly design effort when performed late in the project life cycle, which adds unexpected mass to the spacecraft components during the integration phase, and could disrupt thermal management.A proposal is discussed to develop a more cost-effective approach to MMOD-shielding, which can be employed earlier in the hardware design phase. The development and adoption of standardized shielding assemblies allows early tailoring of the shielding around a component, so that the mass is accounted for, as well as the small particle penetration risk, at a point in the design phase when the cost and schedule impact are more manageable. A set of several assemblies can be developed with a range of protection thresholds, in order to control mass where less shielding is needed. Such shielding assemblies would be developed in collaboration with blanket assembly specialists and thermal control engineers to ensure manufacturability and thermal performance challenges are known and acceptable. One clear benefit of such an approach is that hypervelocity testing can be performed on each of the standard shield assemblies to refine and confirm their performance prior to use.The challenges inherent in designing supplemental MMOD shielding will be discussed, including variations in the orbital debris environment and performance prediction. The benefits of a standardized shielding approach and example applications will also be presented.

Hull, Scott M.↗
NASA NTRS2019

A Proposal for Standardized MMOD Shielding for Robotic Spacecraft

NASA robotic spacecraft are required to assess the potential for small debris induced failure for all disposal-critical components. Additional shielding might then be necessary in order to meet the acceptable risk requirement for the overall mission. Traditionally this requirement had been met with little or no additional shielding. Since the introduction of a high density debris population in ORDEM 3.0, some missions, especially those in higher portions of Low Earth Orbit, have needed additional MMOD-specific shielding in order for the mission to meet the requirement. This is a costly design effort when performed late in the project life cycle, which adds unexpected mass to the spacecraft components during the integration phase, and could disrupt thermal management. A proposal is discussed to develop a more cost-effective approach to MMOD-shielding, which can be employed earlier in the hardware design phase. The development and adoption of standardized shielding assemblies allows early tailoring of the shielding around a component, so that the mass is accounted for, as well as the small particle penetration risk, at a point in the design phase when the cost and schedule impact are more manageable. A set of several assemblies can be developed with a range of protection thresholds, in order to control mass where less shielding is needed. Such shielding assemblies would be developed in collaboration with blanket assembly specialists and thermal control engineers to ensure manufacturability and thermal performance challenges are known and acceptable. One clear benefit of such an approach is that hypervelocity testing can be performed on each of the standard shield assemblies to refine and confirm their performance prior to use.The challenges inherent in designing supplemental MMOD shielding will be discussed, including variations in the orbital debris environment and performance prediction. The benefits of a standardized shielding approach and example applications will also be presented.

Hull, Scott M.↗
NASA NTRS2019

Advancing the Standards for Unmanned Air System Communications, Navigation and Surveillance

Under NASA program NNA16BD84C, new architectures were identified and developed for supporting reliable and secure Communications, Navigation and Surveillance (CNS) needs for Unmanned Air Systems (UAS) operating in both controlled and uncontrolled airspace. An analysis of architectures for the two categories of airspace and an implementation technology readiness analysis were performed. These studies produced NASA reports that have been made available in the public domain and have been briefed in previous conferences. We now consider how the products of the study are influencing emerging directions in the aviation standards communities. The International Civil Aviation Organization (ICAO) Communications Panel (CP), Working Group I (WG-I) is currently developing a communications network architecture known as the Aeronautical Telecommunications Network with Internet Protocol Services (ATN/IPS). The target use case for this service is secure and reliable Air Traffic Management (ATM) for manned aircraft operating in controlled airspace. However, the work is more and more also considering the emerging class of airspace users known as Remotely Piloted Aircraft Systems (RPAS), which refers to certain UAS classes. In addition, two Special Committees (SCs) in the Radio Technical Commission for Aeronautics (RTCA) are developing Minimum Aviation System Performance Standards (MASPS) and Minimum Operational Performance Standards (MOPS) for UAS. RTCA SC-223 is investigating an Internet Protocol Suite (IPS) and AeroMACS aviation data link for interoperable (INTEROP) UAS communications. Meanwhile, RTCA SC-228 is working to develop Detect And Avoid (DAA) equipment and a Command and Control (C2) Data Link MOPS establishing LBand and C-Band solutions. These RTCA Special Committees along with ICAO CP WG/I are therefore overlapping in terms of the Communication, Navigation and Surveillance (CNS) alternatives they are seeking to provide for an integrated manned- and unmanned air traffic management service as well as remote pilot command and control. This paper presents UAS CNS architecture concepts developed under the NASA program that apply to all three of the aforementioned committees. It discusses the similarities and differences in the problem spaces under consideration in each committee, and considers the application of a common set of CNS alternatives that can be widely applied. As the works of these committees progress, it is clear that the overlap will need to be addressed to ensure a consistent and safe framework for worldwide aviation. In this study, we discuss similarities and differences in the various operational models and show how the CNS architectures developed under the NASA program apply.

Ponchak, Denise S.↗
NASA NTRS2020

NASA ESDIS Standards Office

This poster describes the function of the NASA ESDIS Standards Office, lists the findable, interoperable, accessible and the reusable standards that have been reviewed and endorsed for broader use in NASA data and information systems, and the impacts of these endorsed standards.

Lynnes, Chris↗
NASA NTRS2005

Nutrition Requirements, Standards, and Operating Bands for Exploration Missions

The challenge was brought forward in early 2005 to define the nutritional requirements for Exploration missions, and to define the relevant standards and associated operating bands related to nutrition. This document is the result of this charge. An extensive review of existing knowledge was conducted with participation of intramural and extramural experts, and the findings are summarized herein. In short, the approach taken was to define the nutrient intake requirements, that is, the amount of each nutrient expected to be available in the food system. The standards are defined as markers of nutritional status, with optimal (green), sub-optimal (yellow), and critical (red) levels for each. For many of the nutrient requirements, it is not known if they are altered during space flight. Furthermore, in many cases the intake of a nutrient may act as a countermeasure to one or more negative effects of space flight, but these potential countermeasures, too, are not well defined. Thus, we have also documented herein the areas where further research is required. Accordingly, while this document is intended as a comprehensive summary of our knowledge to date, it is expected that this is the first edition of these requirements and standards. As we learn more about space-flight nutrition, and as relationships between disease and nutrients are further defined in Earth-based populations, this document, and the approach to nutrition in the space rogram, will need to be updated accordingly.

Neubek, Deborah J.↗
NASA NTRS2020

Leveraging ASTM Industry Standard F3269-17 for Providing Safe Operations of a Highly Autonomous Aircraft

This paper expands upon the ASTM industry standard F3269-17 to outline a run-time assurance (RTA) network architecture for use in ensuring safe flight operations of a highly autonomous aircraft. An RTA network architecture is proposed and critical features discussed to implement functions where automation is primarily responsible for the safety of the aircraft instead of a pilot. This shift in responsibility, made possible by the proposed architecture, is key to highly resilient automation and is a core enabler for future “pilotless” transportation concepts. The findings in this paper stem from the researcher’s experiences with ASTM in the generation of the standard and some seven years of RTA system development on various flight programs leveraging the RTA concepts outlined in the ASTM standard.

autonomous systems↗
NASA NTRSDate not supplied

Applying NASA-STD-7009 Standard for Models and Simulations to Surrogate and Other Statistical Models

NASA-STD-7009A, Standard for Models and Simulations, contains a worthy and insightfully-crafted credibility assessment. That set of metrics is intended to accumulate and communicate information that can be critical for users and their customers in evaluating findings due to a model or simulation. Was the model designed for the present use? Is it validated in the domain it’s being applied to? And so on. The standard was originally focused on physics-based models, but it can be applied more generally. It can – and should – be applied to high-impact statistical models, including surrogate models based on larger models and sims and regression models based directly on data. A key issue with many of such models is their relative simplicity compared to most M&S despite their use in high-risk engineering decisions. This report will make a case for using this Standard for a wider class of models, and how it might actually add value in excess of its cost for not only stakeholders, but modelers themselves. A rough example showing compliance for a statistical model is included.

K L Johnson↗
NASA NTRS1995

Incorporating CCSDS Telemetry Standards and Philosophy on Cassini

The Cassini project at the Jet Propulsion Laboratory (JPL) is implementing a spacecraft telemetry system based on the Consultative Committee for Space Data Systems (CCSDS) packet telemetry standards. Resolving the CCSDS concepts with a Ground Data System designed to handle time-division-multiplexed telemetry and also handling constraints unique to a deep-space planetary spacecraft (such as fixed downlink opportunities, small downlink rates and requirements for on-board data storage) have resulted in spacecraft and ground system design challenges. Solving these design challenges involved adapting and extending the CCSDS telemetry standards as well as changes to the spacecraft and ground system designs. The resulting spacecraft/ground system design is an example of how new ideas and philosophies can be incorporated into existing systems and design approaches without requiring significant rework. In addition, it shows that the CCSDS telemetry standards can be successfully applied to deep-space planetary spacecraft.

CCSDS↗
NASA NTRSDate not supplied

Development of Lunar EVA Fitness for Duty Standards for Aerobic Capacity and Muscle Strength

Current aerobic Fitness Standards for NASA astronauts are based on peak aerobic capacity (i.e. VO2peak (ml/kg/min))and are related to aerobic metabolic requirements for Extravehicular Activity (EVA) in microgravity and in 1 g operational environments. Standards for muscle strength need to be developed. Fitness for Duty Standards for partial gravity EVA (e.g. 1/6 g EVA on the Lunar surface) are not developed in terms of aerobic fitness and muscle strength. Defining thresholds for aerobic fitness and muscle strength will help to provide guidance in determining recommendations for optimal fitness necessary for partial g EVA success.

D Frisco↗
NASA NTRS2021

HAPI: An API Standard for Accessing Heliophysics Time Series Data

Heliophysics data analysis often involves combining diverse science measurements, many of them captured as time series. Although there are now only a few commonly used data file formats, the diversity in mechanisms for automated access to and aggregation of such data holdings can make analysis that requires intercomparison of data from multiple data providers difficult. The Heliophysics Application Programmer's Interface (HAPI) is a recently developed standard for accessing distributed time series data to increase interoperability. The HAPI specification is based on the common elements of existing data services, and it standardizes the two main parts of a data service: the request interface and the response data structures. The interface is based on the REpresentational State Transfer (REST) or RESTful architecture style, and the HAPI specification defines five required REST endpoints. Data are returned via a streaming format that hides file boundaries; the metadata is detailed enough for the content to be scientifically useful, e.g., plotted with appropriate axes layout, units, and labels. Multiple mature HAPI-related open-source projects offer server-side implementation tools and client-side libraries for reading HAPI data in multiple languages (IDL, Java, MATLAB, and Python). Multiple data providers in the US and Europe have added HAPI access alongside their existing interfaces. Based on this experience, data can be served via HAPI with little or no information loss compared to similar existing web interfaces. Finally, HAPI has been recommended as a COSPAR standard for time series data delivery.

Robert S. Weigel↗
NASA NTRSDate not supplied

Using Open Standards and NASA Open Source Simulation Tools to Model Artemis Base Camp Mission Timelines

The United States’ National Aeronautics and Space Administration (NASA) has announced that the Artemis Program will return humans to the Moon, establishing a persistent presence with the Artemis Base Camp (ABC), and extend human exploration to Mars. The NASA Exploration Systems Simulations (NExSyS) team at NASA’s Johnson Space Center is using internationally developed simulation interoperability standards and NASA open source simulation tools to support Artemis concept, analysis, designs, development, training, and ultimately operations. The NExSyS team has been tasked to support early ABC architecture and mission analysis using mission time lines developed by the crew operations mission planning team. The NExSyS team is developing a distributed simulation framework with initial Artemis element implementations to model the ABC mission timelines using the international simulation interoperability standard High Level Architecture (HLA), the Simulation Interoperability Standards Organization’s Space Reference Federation Object Model (SpaceFOM), the NASA open source Trick Simulation Environment, and another NASA open source interface package called TrickHLA. The ABC architecture is composed of a number of key surface elements and resources. Some examples of modeled elements (also known as entities) are landers, habitats, rovers, logistics carriers, and astronauts. Some examples of modeled transferable and consumable resources are power, water, oxygen, nitrogen, scientific samples, and food. These entities and resources are modeled in a collection of individual simulations called Federates. A coordinated collection of interoperable federates is called a Federation and when these federates are tied together in a coordinated simulation run, it is referred to as a Federation Execution. The federates communicate through HLA using data exchange formats defined by a collection of machine readable files called Federation Object Models (FOMs). These FOM files are based on extensions to the SpaceFOM. This enables the instantiation and sharing of objects and interactions between federates in the federation. These provide for entity and resource tracking, object transfer, and data collection. Federate interactions are used to trigger events and notify federates of entity or resource transfers. For the initial implementation, the constituent federates are Trick-based simulations that use TrickHLA to provide the required HLA-base interoperability. These Trick-based simulations provide the required modeling for the individual Artemis elements along with the associated element resources. These federates provide a means to explore traverses between surface elements and exploration sites as scheduled in a mission timeline and explore the affects traverse times have on the overall mission timeline. The mission time lines are modeled using a Trick input file event handling capabilities. Each timeline operation is handled as individual simulation events, and triggered based on previous event status, time of operation, and simulated task completions. In addition, the ABC Federation can be used to perform Monte Carlo analysis. The Monte Carlo tool can vary the inputs, timings, and malfunctions to show how various contingencies in the mission can affect the mission timeline.

Keaton Craig Dodd↗
NASA NTRSDate not supplied

The Use of Atmospheric Composition Variable Standard Names in Airborne and Field Data Products

The number of variables measured during airborne field campaigns has increased more than tenfold over the last thirty years. With this increase in measurements, the complexity for distributed active archive centers (DAACs) to distribute the data and for data users to search for and find measurements of interest has also increased. Part of this complexity arises from the unique variable names in suborbital atmospheric composition field studies. With limited guidelines related to variable naming, variable names and structures can vary significantly, even for the same type of variable. It is common for instrument scientists to use their intended measurable quantity as the data variable name. This can make it difficult for users to locate and interact with a particular variable across multiple data sets. One effective solution to this problem, identified by the Earth Science Data System (ESDS) ICARTT Refresh Working Group [1], was to introduce variable standard names that can be used as tags for each data variable. This allows similar measurements (e.g., dew point) to be categorized and located across field campaigns, regardless of what variable name the instrument scientist has used. From this the atmospheric composition variable standard names were developed with the goal to use Findable, Accessible, Interoperable, and Reusable (FAIR) principles [2] and provide context for all users, while remaining connected to those in the subject area. These standard names have been successfully implemented in FIREX-AQ, CAMP 2EX, ACTIVATE, and DCOTSS field campaigns.

metadata↗
NASA NTRSDate not supplied

Evaluation of Aerobic Standards for Lunar Surface Extravehicular Activities

As NASA prepares to return to the Moon, astronauts will need to be physically primed to successfully execute Extravehicular Activities (EVA) on the Lunar surface. Compared to past Apollo missions, Artemis missions will include EVAs of increased physical demand, frequency, intensity, and duration, thus requiring adequate fitness to successfully and safely complete mission objectives. The physical demand associated with partial gravity (g) EVAs on the Moon is expected to be greater compared to microgravity EVAs based on initial workload estimation. Currently, aerobic fitness standards for partial g EVAs are not well supported by high-fidelity data and require further research for establishing standards to protect crew health and performance during Lunar surface missions. Therefore, the aim of this investigation is to characterize metabolic data from Lunar analog simulations and in-flight crew population aerobic capacity data to validate the current NASA 3001 standard for celestial partial g aerobic fitness (aerobic capacity (VO_2pk) ≥36.5ml/kg/min).

Nicole Strock↗