Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Standards Development”

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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

NASA's Initial Artemis Human Landing System

In April 2020, NASA announced the selection of three companies to begin the initial phase of development of human landing systems to take the first woman and the first person of color to the lunar surface through NASA’s Artemis lunar exploration program. The selected companies were a Blue Origin-led team with Lockheed Martin, Northrup Grumman, and Draper; Dynetics (a Leidos company); and SpaceX. Contracts were awarded shortly after, kicking off a ten-month base period during which NASA worked closely with each company to finalize functional and performance requirements, confirm lander development standards, and establish baseline designs, schedules, and management plans for contract execution and human spaceflight certification. At the end of the base period, in the Spring of 2021, NASA awarded a single follow-on Option A contract to SpaceX to continue their work on Human Landing System (HLS) Starship development. Currently NASA and SpaceX are working collaboratively on Option A which will ultimately culminate in one uncrewed and one crewed mission to the lunar surface under Artemis III. This paper will provide a look at the Option A phase of development for the Human Landing System Program, including publicly available information on SpaceX’s HLS Starship design as well as near-term and future milestones for HLS and the Artemis program.

Lisa Watson-Morgan↗
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 NTRS1999

Examining Mars with SPICE

The International Mars Conference highlights the wealth of scientific data now and soon to be acquired from an international armada of Mars-bound robotic spacecraft. Underlying the planning and interpretation of these scientific observations around and upon Mars are ancillary data and associated software needed to deal with trajectories or locations, instrument pointing, timing and Mars cartographic models. The NASA planetary community has adopted the SPICE system of ancillary data standards and allied tools to fill the need for consistent, reliable access to these basic data and a near limitless range of derived parameters. After substantial rapid growth in its formative years, the SPICE system continues to evolve today to meet new needs and improve ease of use. Adaptations to handle landers and rovers were prototyped on the Mars pathfinder mission and will next be used on Mars '01-'05. Incorporation of new methods to readily handle non-inertial reference frames has vastly extended the capability and simplified many computations. A translation of the SPICE Toolkit software suite to the C language has just been announced. To further support cartographic calculations associated with Mars exploration the SPICE developers at JPL have recently been asked by NASA to work with cartographers to develop standards and allied software for storing and accessing control net and shape model data sets; these will be highly integrated with existing SPICE components. NASA specifically supports the widest possible utilization of SPICE capabilities throughout the international space science community. With NASA backing the Russian Space Agency and Russian Academy of Science adopted the SPICE standards for the Mars 96 mission. The SPICE ephemeris component will shortly become the international standard for agencies using the Deep Space Network. U.S. and European scientists hope that ESA will employ SPICE standards on the Mars Express mission. SPICE is an open set of standards, and all related specifications and software are freely distributed around the world. This poster describes the current state of SPICE system development, with special emphasis on current and planned support for Mars exploration missions.

Acton, Charles H.↗
NASA NTRSDate not supplied

Having a Come-Apart: Lessons Learned from Additively Manufactured Hardware Failures

NASA has been engaged with additively manufactured (AM) process and component development since the 2000’s. AM offers various technical advantages, such as enhanced hardware design complexity, part consolidation, and processing of novel alloys in addition to programmatic advantages for reduction in processing time and cost. The focus of much of the AM development at NASA has been to mature the various processes, characterize material properties, develop standards, produce demonstrator parts, and integrate AM hardware in liquid rocket engines. These aspects have been demonstrated through process and design iterations using a methodical characterization, test-fail-fix cycles, as well as application and dissemination of lessons learned. In addition to these fundamental demonstrations of the AM process and hardware development, alloys that provide performance advantages in the high temperature and high-pressure environments have been matured for use in rocket engines. These environments are challenging for any alloy and any design, and the AM process is required to fully meet the intended design requirements. The importance of proper AM process was made evident in the failure of a Laser Powder Bed Fusion (L-PBF) copper-alloy combustion chamber during a hot-fire test due to a degraded material quality resulted from an AM process issue. The hot-fire test aimed to demonstrate high duty cycle under a risk-tolerant development project, where consequences of component failure would be minimal. However, the unintentional component failure emphasized the necessity of robust material characterization and rigorous process control procedures for the safe use of AM components in critical applications. In part, such concerns motivate the AM certification approach that NASA has recently adopted in NASA-STD-6030 “Additive Manufacturing Requirements for Spaceflight Systems”. This presentation provides an overview of the previously mentioned failure, a discussion on the evaluation of the failed chamber and supplemental chambers produced at the same time, a representative material samples that included intentional build witness lines, and a summary of the key results and recommendations from the evaluations. NASA continues to approach AM processes and designs with a level of risk and acceptance of failures that is appropriate for the project objectives, with the overall goal of safe implementation of AM technology and transferring AM technology into commercial space applications. The objective of this presentation is to provide awareness to the community working critical and non-critical AM components and the lessons learned on proper implementation of AM.

Additive Manufacturing↗
NASA NTRS2009

Case Study: Using The OMG SWRADIO Profile and SDR Forum Input for NASA's Space Telecommunications Radio System

The Space Telecommunication Radio System (STRS) standard is a Software Defined Radio (SDR) architecture standard developed by NASA. The goal of STRS is to reduce NASA s dependence on custom, proprietary architectures with unique and varying interfaces and hardware and support reuse of waveforms across platforms. The STRS project worked with members of the Object Management Group (OMG), Software Defined Radio Forum, and industry partners to leverage existing standards and knowledge. This collaboration included investigating the use of the OMG s Platform-Independent Model (PIM) SWRadio as the basis for an STRS PIM. This paper details the influence of the OMG technologies on the STRS update effort, findings in the STRS/SWRadio mapping, and provides a summary of the SDR Forum recommendations.

Briones, Janette C.↗
NASA NTRS2004

Spaceflight Operations Services Grid (SOSG)

In an effort to adapt existing space flight operations services to new emerging Grid technologies we are developing a Grid-based prototype space flight operations Grid. This prototype is based on the operational services being provided to the International Space Station's Payload operations located at the Marshall Space Flight Center, Alabama. The prototype services will be Grid or Web enabled and provided to four user communities through portal technology. Users will have the opportunity to assess the value and feasibility of Grid technologies to their specific areas or disciplines. In this presentation descriptions of the prototype development, User-based services, Grid-based services and status of the project will be presented. Expected benefits, findings and observations (if any) to date will also be discussed. The focus of the presentation will be on the project in general, status to date and future plans. The End-use services to be included in the prototype are voice, video, telemetry, commanding, collaboration tools and visualization among others. Security is addressed throughout the project and is being designed into the Grid technologies and standards development. The project is divided into three phases. Phase One establishes the baseline User-based services required for space flight operations listed above. Phase Two involves applying Gridlweb technologies to the User-based services and development of portals for access by users. Phase Three will allow NASA and end users to evaluate the services and determine the future of the technology as applied to space flight operational services. Although, Phase One, which includes the development of the quasi-operational User-based services of the prototype, development will be completed by March 2004, the application of Grid technologies to these services will have just begun. We will provide status of the Grid technologies to the individual User-based services. This effort will result in an extensible environment that incorporates existing and new spaceflight services into a standards-based framework providing current and future NASA programs with cost savings and new and evolvable methods to conduct science. This project will demonstrate how the use of new programming paradigms such as web and grid services can provide three significant benefits to the cost-effective delivery of spaceflight services. They will enable applications to operate more efficiently by being able to utilize pooled resources. They will also permit the reuse of common services to rapidly construct new and more powerful applications. Finally they will permit easy and secure access to services via a combination of grid and portal technology by a distributed user community consisting of NASA operations centers, scientists, the educational community and even the general population as outreach. The approach will be to deploy existing mission support applications such as the Telescience Resource Kit (TReK) and new applications under development, such as the Grid Video Distribution System (GViDS), together with existing grid applications and services such as high-performance computing and visualization services provided by NASA s Information Power Grid (IPG) in the MSFC s Payload Operations Integration Center (POIC) HOSC Annex. Once the initial applications have been moved to the grid, a process will begin to apply the new programming paradigms to integrate them where possible. For example, with GViDS, instead of viewing the Distribution service as an application that must run on a single node, the new approach is to build it such that it can be dispatched across a pool of resources in response to dynamic loads. To make this a reality, reusable services will be critical, such as a brokering service to locate appropriate resource within the pool. This brokering service can then be used by other applications such as the TReK. To expand further, if the GViDS application is constructed using a services-based mel, then other applications such as the Video Auditorium can then use GViDS as a service to easily incorporate these video streams into a collaborative conference. Finally, as these applications are re-factored into this new services-based paradigm, the construction of portals to integrate them will be a simple process. As a result, portals can be tailored to meet the requirements of specific user communities.

Bradford, Robert N.↗
NASA NTRS2012

Validation and Verification of Operational Land Analysis Activities at the Air Force Weather Agency

The NASA developed Land Information System (LIS) is the Air Force Weather Agency's (AFWA) operational Land Data Assimilation System (LDAS) combining real time precipitation observations and analyses, global forecast model data, vegetation, terrain, and soil parameters with the community Noah land surface model, along with other hydrology module options, to generate profile analyses of global soil moisture, soil temperature, and other important land surface characteristics. (1) A range of satellite data products and surface observations used to generate the land analysis products (2) Global, 1/4 deg spatial resolution (3) Model analysis generated at 3 hours. AFWA recognizes the importance of operational benchmarking and uncertainty characterization for land surface modeling and is developing standard methods, software, and metrics to verify and/or validate LIS output products. To facilitate this and other needs for land analysis activities at AFWA, the Model Evaluation Toolkit (MET) -- a joint product of the National Center for Atmospheric Research Developmental Testbed Center (NCAR DTC), AFWA, and the user community -- and the Land surface Verification Toolkit (LVT), developed at the Goddard Space Flight Center (GSFC), have been adapted to operational benchmarking needs of AFWA's land characterization activities.

Shaw, Michael↗
NASA NTRS2022

National Campaign (NC)-1 Strategic Conflict Management Simulation (X4) Final Report

Urban Air Mobility (UAM) enables highly automated, cooperative, passenger or cargo-carrying air transportation services in and around urban areas. UAM is a subset of the Advanced Air Mobility (AAM) concept under development by the National Aeronautics and Space Administration (NASA), the Federal Aviation Administration (FAA), and industry. The Strategic Conflict Management (SCM) Simulation, dubbed “X4”, was conducted between July 2021 and June 2022 by NASA with the FAA and industry to evolve the Provider of Services for UAM (PSU) that will be needed to ensure initial UAM operations can scale in the National Airspace System (NAS). The FAA UAM Concept of Operations (ConOps) v1 [1] served as an initial guiding document for the X4 airspace management system design to ensure the architecture supports testing of services provided by third-party service providers. To that end, the X4 architecture leveraged concepts and technologies developed for Unmanned Aircraft System (UAS) Traffic Management (UTM) while also developing and testing new capabilities and services needed for UAM. The architecture included an initial prototype of the FAA-Industry Exchange Protocol (FIDXP), third-party services such as the PSUs, and Discovery and Synchronization Service (DSS), and other new services such as Demand-Capacity Balancing (DCB) to facilitate UAM strategic conflict management. During X4, NASA led discussions and collaborated with seven industry airspace partners to develop initial airspace management concepts for UAM that drove what would be tested and evaluated during the simulations. The initial capabilities defined for PSU leveraged UTM UAS Service Supplier (USS) as a starting point and evolved to meet UAM requirements. These discussions were also an opportunity for NASA to collaborate with industry to develop a set of initial Community-Based Rules (CBRs). These CBRs enabled how UAM traffic would be cooperatively managed among UAM operators. The collaborative, iterative process of developing CBRs with industry during X4 provided insight into the challenges involved and identified the need for a suitable and effective forum for future CBR development. In parallel with these discussions, NASA conducted a series of seven software sprints and two collaborative simulations with the airspace partners that built up in complexity. Over the course of the year, all seven partners successfully completed all the sprints by demonstrating the required capabilities. They also participated in the two collaborative simulations to demonstrate how multiple PSUs could work together in a collaborative, more complex environment with higher traffic density. The X4 simulation accomplished NASA's objectives and helped advance the development of the seven participating PSUs. The lessons learned provided insight into key elements of the UAM Notional Architecture from the FAA ConOps v1 [1] and UTM technologies when applied to UAM: - Having a Concept of Use (ConUse) defined prior to the activity would accelerate the time and effort from concept development to testing. - While the UAM Notional Architecture provided a starting point for a federated architecture that support services provided by third-party providers, the USS and PSU differed in their capability definitions for operational intent submission and sharing, conformance monitoring, airspace authorization, strategic conflict management, airspace constraints and dynamic replanning. - While existing DSS developed for UTM provided a way for PSU and other UAM services (such as DCB) to discover relevant operations from each other, additional complexity and challenges were found during X4 testing and illuminated the need for a more suitable solution for UAM. Industry can leverage the results of this demonstration to accelerate UAM requirements, CBRs, and standards development. The FAA and other government municipalities and agencies will be able to leverage results to inform future policies and identify additional gaps that require further analysis, moving toward operationalization of UAM.

Urban Air Mobility↗
NASA NTRS2008

Cluster Inter-Spacecraft Communications

A document describes a radio communication system being developed for exchanging data and sharing data-processing capabilities among spacecraft flying in formation. The system would establish a high-speed, low-latency, deterministic loop communication path connecting all the spacecraft in a cluster. The system would be a wireless version of a ring bus that complies with the Institute of Electrical and Electronics Engineers (IEEE) standard 1393 (which pertains to a spaceborne fiber-optic data bus enhancement to the IEEE standard developed at NASA's Jet Propulsion Laboratory). Every spacecraft in the cluster would be equipped with a ring-bus radio transceiver. The identity of a spacecraft would be established upon connection into the ring bus, and the spacecraft could be at any location in the ring communication sequence. In the event of failure of a spacecraft, the ring bus would reconfigure itself, bypassing a failed spacecraft. Similarly, the ring bus would reconfigure itself to accommodate a spacecraft newly added to the cluster or newly enabled or re-enabled. Thus, the ring bus would be scalable and robust. Reliability could be increased by launching, into the cluster, spare spacecraft to be activated in the event of failure of other spacecraft.

Cox, Brian↗
NASA NTRS2018

UAS Integration in the NAS: Detect and Avoid

This presentation will cover the structure of the unmanned aircraft systems (UAS) integration into the national airspace system (NAS) project (UAS-NAS Project). The talk also details the motivation of the project to help develop standards for a detect-and-avoid (DAA) system, which is required in order to comply with requirements in manned aviation to see-and-avoid other traffic so as to maintain well clear. The presentation covers accomplishments reached by the project in Phase 1 of the research, and touches on the work to be done in Phase 2. The discussion ends with examples of the display work developed as a result of the Phase 1 research.

unmanned aircraft systems↗
NASA NTRSDate not supplied

A Deeper Dive Into the Meaning and Implications of Interoperability for LunaNet Communications and Navigation Services

As part of planning efforts for cislunar exploration and science missions, space agencies have been collaborating with each other to enable communications, networking, Position, Navigation, and Timing (PNT) systems to exchange information and provide services to spacecraft and space systems in transit, in orbit, and on the surface, thus helping each other to achieve their common goals. To achieve commonality and lower cost for mutual benefit, the strategy of interoperability is being adopted to help all the pieces fit together and function smoothly. Interoperability gives cislunar users the ability to operate in a collaborative environment similar to the terrestrial Internet, allowing them to share information, navigate safely despite increasing radio frequency congestion, and follow common processes and procedures for effective joint operations. Unlike prior government-dominated efforts, this ecosystem is expected to include commercial for-profit businesses, non-profit organizations, and academic institutions. Ultimately, the goal is to enable a cislunar ecosystem of service providers and users to contribute and/or utilize infrastructure and capabilities to accomplish mission objectives spanning the full range of human endeavours while supporting a variety of business models. This paper reports on the results of an effort to assist in efforts to frame the development of the international LunaNet architecture by providing a canonical definition of interoperability broad enough to meet these needs, examine architectural and operational implications of the definition, and explore interoperability strategies and tactics for deploying and evolving these services. It describes key systems-of-systems (SoS) (Network-of-Networks) interoperability concepts in the context of sustainment of the ecosystem over time as systems evolve in technologies, standards and Standards Development Organizations, component and subsystem upgrades, and user applications

LunaNet↗
NASA NTRS2015

Experimental Design for Pre-Clinical Animal Model Study in Microgravity

The Rodent Research program at NASAs Ames Research Center (ARC) has pioneered a new research capability on the International Space Station in less than four years and has progressed toward translating research to the ISS utilizing commercial rockets, collaborating with academia and science industry, and training crew for research purposes on-orbit. Animal models are the foundation of pre-clinical research to understand human diseases and evaluate new therapeutics. Advancement in alleviating ground diseases such as muscle atrophy and osteoporosis can come from the study of similar conditions that are known to occur as a result of exposure to the spaceflight environment. During the completion of the flight phase of two missions, our practices, hardware and operations evolved from tested to developed standards, which successfully translated the studies from ground to space. Results from these studies contribute to the science community via both the primary investigation and banked samples that are shared in publicly available data repository such as GeneLab. Every completed mission sets a foundation to build and design greater complexity into future research and answer questions about common human diseases on ground and in space. Here, we present methods developed for the translation of a rodent experiment to the ISS including a description of hardware and kits available for investigators and a discussion of operational constraints.

Rodent Research↗
NASA NTRS1987

Algorithms and programming tools for image processing on the MPP:3

This is the third and final report on the work done for NASA Grant 5-403 on Algorithms and Programming Tools for Image Processing on the MPP:3. All the work done for this grant is summarized in the introduction. Work done since August 1986 is reported in detail. Research for this grant falls under the following headings: (1) fundamental algorithms for the MPP; (2) programming utilities for the MPP; (3) the Parallel Pascal Development System; and (4) performance analysis. In this report, the results of two efforts are reported: region growing, and performance analysis of important characteristic algorithms. In each case, timing results from MPP implementations are included. A paper is included in which parallel algorithms for region growing on the MPP is discussed. These algorithms permit different sized regions to be merged in parallel. Details on the implementation and peformance of several important MPP algorithms are given. These include a number of standard permutations, the FFT, convolution, arbitrary data mappings, image warping, and pyramid operations, all of which have been implemented on the MPP. The permutation and image warping functions have been included in the standard development system library.

Reeves, Anthony P.↗
NASA NTRS1992

HSCT high lift system aerodynamic requirements

The viewgraphs and discussion of high lift system aerodynamic requirements are provided. Low speed aerodynamics has been identified as critical to the successful development of a High Speed Civil Transport (HSCT). The airplane must takeoff and land at a sufficient number of existing or projected airports to be economically viable. At the same time, community noise must be acceptable. Improvements in cruise drag, engine fuel consumption, and structural weight tend to decrease the wing size and thrust required of engines. Decreasing wing size increases the requirements for effective and efficient low speed characteristics. Current design concepts have already been compromised away from better cruise wings for low speed performance. Flap systems have been added to achieve better lift-to-drag ratios for climb and approach and for lower pitch attitudes for liftoff and touchdown. Research to achieve improvements in low speed aerodynamics needs to be focused on areas most likely to have the largest effect on the wing and engine sizing process. It would be desirable to provide enough lift to avoid sizing the airplane for field performance and to still meet the noise requirements. The airworthiness standards developed in 1971 will be the basis for performance requirements for an airplane that will not be critical to the airplane wing and engine size. The lift and drag levels that were required to meet the performance requirements of tentative airworthiness standards established in 1971 and that were important to community noise are identified. Research to improve the low speed aerodynamic characteristics of the HSCT needs to be focused in the areas of performance deficiency and where noise can be reduced. Otherwise, the wing planform, engine cycle, or other parameters for a superior cruising airplane would have to be changed.

Paulson, John A.↗
NASA NTRSDate not supplied

Metal Additive Manufacturing for Rocket Engines: Successes and Failures

NASA has been developing additive manufacturing (AM) for various technical and programmatic advantages for complex rocket engine and aerospace components. This maturation has focused on various AM processes, new alloys, characterizing material properties, developing standards, producing demonstrator parts, and integrating AM hardware in liquid rocket engines through test-fail-fix cycles, as well as application and dissemination of lessons learned of the AM lifecycle. The importance of proper AM processing was made evident in the failure of a Laser Powder Bed Fusion (L-PBF) copper-alloy combustion chamber during a hot-fire test due to a degraded material quality. The hot-fire test aimed to demonstrate high duty cycle under a risk-tolerant development project, where consequences of component failure would be minimal. However, the unintentional component failure emphasized the necessity of robust material characterization and rigorous process control procedures for the safe use of AM components in critical applications. This presentation provides an overview of the development failure, a discussion on the evaluation of the failed chamber and supplemental chambers produced at the same time, a representative material samples that included intentional build witness lines, and a summary of the key results and recommendations from the evaluations. NASA continues to approach AM processes and designs with a level of risk and acceptance of failures that is appropriate for the project objectives, with the overall goal of safe implementation of AM technology and transferring AM technology into commercial space applications. This presentation with provide critical awareness to the community lessons learned on proper implementation of AM.

L-PBF↗
NASA NTRSDate not supplied

Successes and Failures of Metal Additive Manufacturing for Rocket Engines

NASA has been developing additive manufacturing (AM) for various technical and programmatic advantages for complex rocket engine and aerospace components. This maturation has focused on various AM processes, new alloys, characterizing material properties, developing standards, producing demonstrator parts, and integrating AM hardware in liquid rocket engines through test-fail-fix cycles, as well as application and dissemination of lessons learned of the AM lifecycle. The importance of proper AM processing was made evident in the failure of a Laser Powder Bed Fusion (L-PBF) copper-alloy combustion chamber during a hot-fire test due to a degraded material quality. The hot-fire test aimed to demonstrate high duty cycle under a risk-tolerant development project, where consequences of component failure would be minimal. However, the unintentional component failure emphasized the necessity of robust material characterization and rigorous process control procedures for the safe use of AM components in critical applications. This presentation provides an overview of the development failure, a discussion on the evaluation of the failed chamber and supplemental chambers produced at the same time, a representative material samples that included intentional build witness lines, and a summary of the key results and recommendations from the evaluations. NASA continues to approach AM processes and designs with a level of risk and acceptance of failures that is appropriate for the project objectives, with the overall goal of safe implementation of AM technology and transferring AM technology into commercial space applications. This presentation with provide critical awareness to the community lessons learned on proper implementation of AM.

Additive Manufacturing↗
NASA NTRS2000

Comparison of Commercial Electromagnetic Interface Test Techniques to NASA Electromagnetic Interference Test Techniques

This report documents the development of analytical techniques required for interpreting and comparing space systems electromagnetic interference test data with commercial electromagnetic interference test data using NASA Specification SSP 30237A "Space Systems Electromagnetic Emission and Susceptibility Requirements for Electromagnetic Compatibility." The PSpice computer simulation results and the laboratory measurements for the test setups under study compare well. The study results, however, indicate that the transfer function required to translate test results of one setup to another is highly dependent on cables and their actual layout in the test setup. Since cables are equipment specific and are not specified in the test standards, developing a transfer function that would cover all cable types (random, twisted, or coaxial), sizes (gauge number and length), and layouts (distance from the ground plane) is not practical.

Smith, V.↗