SEARCH · Engineering Papers

Results for “supplier quality”

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.

SourceResearch connectionFrom yearThrough year

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

70 records · Page 4

All sources NASA NTRS DOE OSTI

NASA NTRS2018

Use of Open Networks and Delay-Tolerant Protocol to Decrease WAN Latency of EOS near Real-Time Data

Since 1999, NASA's Earth Observing System Data Operations System (EDOS) project at Goddard Space Flight Center (GSFC) has provided high-rate data capture, level zero processing, and product distribution services for a majority of NASA's EOS (Earth Observing System) high-rate missions, including Terra, Aqua, Aura, ICESat, EO-1, SMAP, and OCO-2. EDOS high-rate science and engineering (150-300 Mbps) data-driven capture systems are deployed at 7 worldwide ground stations which are connected via both private (closed) and public (open) wide area networks (WANs) to the centralized EDOS Level Zero Processing Facility (LZPF) located at GSFC, where the data is processed and Level 0 products are distributed to users worldwide. All data transferred over the open networks to GSFC traverse an IPSec tunnel, providing the same level of security as a VPN connection. EDOS produces both time-based and near real-time products (session-based). Near real-time data products are produced from a single ground station contact; time-based products are produced from multiple ground station contacts. EDOS is the primary supplier of EOS Level 0 data to the NASA near real-time user community known as the Land, Atmosphere Near real-time Capability for EOS (LANCE). For the past few years, EDOS has streamlined its systems to reduce WAN latency for near real-time data delivery, including implementing Quality of Service (QoS), expanding closed network bandwidth, adding open network connections with more bandwidth, and implementing a delay-tolerant protocol to mitigate long round-trip times to remote ground stations.

Delay-Tolerant Protocol↗

NASA NTRS1980

Completion of evaluation of manufacturing processes for B/Al composites containing 0.2mm diameter boron fibers

Four fabricators produced a total of 54 B/1100 Al, B/6061 Al, and B/2024 Al panels for evaluation. The 8 ply unidirectional, 45 to 50 volume percent, panels were made using 0.20 mm diameter boron fibers which were obtained from a single supplier. Hot press consolidation was carried out in vacuum except for one set of dry woven tape panels which were hot pressed in air. A single testing contractor conducted nondestructive inspection, metallography, fractography and mechanical property tests. The mechanical property tests included 21 and 260 C tensile tests and 21 C shear tests. Panel quality, as measured by nondestructive evaluation, was generally good as were the 21 C tensile properties. The panels hot pressed in air delaminated in the shear tests. Shear strength values were lower in these panels. But tensile strengths were not affected by the delaminations because of the relation between the tensile loading direction and the delaminations. Composite tensile strength was found to be proportional to the volume percent boron and the aluminum matrix rather than to the tape used or fabrication technique. Suitability of these composites for 260 C service was confirmed by tensile tests.

Moore, T. J.↗

NASA NTRS1995

Requirements for effective use of CFD in aerospace design

This paper presents a perspective on the requirements that Computational Fluid Dynamics (CFD) technology must meet for its effective use in aerospace design. General observations are made on current aerospace design practices and deficiencies are noted that must be rectified for the U.S. aerospace industry to maintain its leadership position in the global marketplace. In order to rectify deficiencies, industry is transitioning to an integrated product and process development (IPPD) environment and design processes are undergoing radical changes. The role of CFD in producing data that design teams need to support flight vehicle development is briefly discussed. An overview of the current state of the art in CFD is given to provide an assessment of strengths and weaknesses of the variety of methods currently available, or under development, to produce aerodynamic data. Effectiveness requirements are examined from a customer/supplier view point with design team as customer and CFD practitioner as supplier. Partnership between the design team and CFD team is identified as an essential requirement for effective use of CFD. Rapid turnaround, reliable accuracy, and affordability are offered as three key requirements that CFD community must address if CFD is to play its rightful role in supporting the IPPD design environment needed to produce high quality yet affordable designs.

Raj, Pradeep↗

NASA NTRS1995

Exchange, interpretation, and database-search of ion mobility spectra supported by data format JCAMP-DX

To assist peak assignment in ion mobility spectrometry it is important to have quality reference data. The reference collection should be stored in a database system which is capable of being searched using spectral or substance information. We propose to build such a database customized for ion mobility spectra. To start off with it is important to quickly reach a critical mass of data in the collection. We wish to obtain as many spectra combined with their IMS parameters as possible. Spectra suppliers will be rewarded for their participation with access to the database. To make the data exchange between users and system administration possible, it is important to define a file format specially made for the requirements of ion mobility spectra. The format should be computer readable and flexible enough for extensive comments to be included. In this document we propose a data exchange format, and we would like you to give comments on it. For the international data exchange it is important, to have a standard data exchange format. We propose to base the definition of this format on the JCAMP-DX protocol, which was developed for the exchange of infrared spectra. This standard made by the Joint Committee on Atomic and Molecular Physical Data is of a flexible design. The aim of this paper is to adopt JCAMP-DX to the special requirements of ion mobility spectra.

Baumback, J. I.↗

NASA NTRS2009

Modeling Guidelines for Code Generation in the Railway Signaling Context

Modeling guidelines constitute one of the fundamental cornerstones for Model Based Development. Their relevance is essential when dealing with code generation in the safety-critical domain. This article presents the experience of a railway signaling systems manufacturer on this issue. Introduction of Model-Based Development (MBD) and code generation in the industrial safety-critical sector created a crucial paradigm shift in the development process of dependable systems. While traditional software development focuses on the code, with MBD practices the focus shifts to model abstractions. The change has fundamental implications for safety-critical systems, which still need to guarantee a high degree of confidence also at code level. Usage of the Simulink/Stateflow platform for modeling, which is a de facto standard in control software development, does not ensure by itself production of high-quality dependable code. This issue has been addressed by companies through the definition of modeling rules imposing restrictions on the usage of design tools components, in order to enable production of qualified code. The MAAB Control Algorithm Modeling Guidelines (MathWorks Automotive Advisory Board)[3] is a well established set of publicly available rules for modeling with Simulink/Stateflow. This set of recommendations has been developed by a group of OEMs and suppliers of the automotive sector with the objective of enforcing and easing the usage of the MathWorks tools within the automotive industry. The guidelines have been published in 2001 and afterwords revisited in 2007 in order to integrate some additional rules developed by the Japanese division of MAAB [5]. The scope of the current edition of the guidelines ranges from model maintainability and readability to code generation issues. The rules are conceived as a reference baseline and therefore they need to be tailored to comply with the characteristics of each industrial context. Customization of these recommendations has been performed for the automotive control systems domain in order to enforce code generation [7]. The MAAB guidelines have been found profitable also in the aerospace/avionics sector [1] and they have been adopted by the MathWorks Aerospace Leadership Council (MALC). General Electric Transportation Systems (GETS) is a well known railway signaling systems manufacturer leading in Automatic Train Protection (ATP) systems technology. Inside an effort of adopting formal methods within its own development process, GETS decided to introduce system modeling by means of the MathWorks tools [2], and in 2008 chose to move to code generation. This article reports the experience performed by GETS in developing its own modeling standard through customizing the MAAB rules for the railway signaling domain and shows the result of this experience with a successful product development story.

Ferrari, Alessio↗

NASA NTRS2010

Comparison of Traditional and Innovative Techniques to Solve Technical Challenges

Although NASA has an adequate food system for current missions, research is required to accommodate new requirements for future NASA exploration missions. The Inadequate Food System risk reflects the need to develop requirements and technologies that will enable NASA to provide the crew with a safe, nutritious and acceptable food system while effectively balancing appropriate resources such as mass, volume, and crew time in exploratory missions. As we go deeper into space or spend more time on the International Space Station (ISS), there will be requirements for packaged food to be stored for 3 5 years. New food packaging technologies are needed that have adequate oxygen and water barrier properties to maintain the foods' quality over this extended shelf life. NASA has been unsuccessful in identify packaging materials that meet the necessary requirements when using several traditional routes including literature reviews, workshops, and internal shelf life studies on foods packaged in various packaging materials. Small Business Innovative Research grants were used for accelerating food packaging materials research with limited success. In order to accelerate the process, a theoretical challenge was submitted to InnoCentive resulting in a partial award. A similar food packaging challenge was submitted to Yet2.com and several potential commercial packaging material suppliers were identified that, at least partially, met the requirements. Comparisons and results of these challenges will be discussed.

Perchonok, Michele↗

NASA NTRS2013

Visit from JAXA to NASA MSFC: The Engines Element & Ideas for Collaboration

System Design, Development, and Fabrication: Design, develop, and fabricate or procure MB-60 component hardware compliant with the imposed technical requirements and in sufficient quantities to fulfill the overall MB-60 development effort. System Development, Assembly, and Test: Manage the scope of the development, assembly, and test-related activities for MB-60 development. This scope includes engine-level development planning, engine assembly and disassembly, test planning, engine testing, inspection, anomaly resolution, and development of necessary ground support equipment and special test equipment. System Integration: Provide coordinated integration in the realms of engineering, safety, quality, and manufacturing disciplines across the scope of the MB-60 design and associated products development Safety and Mission Assurance, structural design, fracture control, materials and processes, thermal analysis. Systems Engineering and Analysis: Manage and perform Systems Engineering and Analysis to provide rigor and structure to the overall design and development effort for the MB-60. Milestone reviews, requirements management, system analysis, program management support Program Management: Manage, plan, and coordinate the activities across all portions of the MB-60 work scope by providing direction for program administration, business management, and supplier management.

Greene, William D.↗

NASA NTRS2017

UTM UAS Service Supplier Specification

Within the Unmanned Aircraft Systems (UAS) Traffic Management (UTM) system, the UAS Service Supplier (USS) is a key component. The USS serves several functions. At a high level, those include the following: Bridging communication between UAS Operators and Flight Information Management System (FIMS) Supporting planning of UAS operations Assisting strategic deconfliction of the UTM airspace Providing information support to UAS Operators during operations Helping UAS Operators meet their formal requirements This document provides the minimum set of requirements for a USS. In order to be recognized as a USS within UTM, successful demonstration of satisfying the requirements described herein will be a prerequisite. To ensure various desired qualities (security, fairness, availability, efficiency, maintainability, etc.), this specification relies on references to existing public specifications whenever possible.

UTM↗

NASA NTRS2019

UAS Service Supplier Specification

Rios, Joseph L.↗

NASA NTRS1999

Investigation Into The Effects of Microsecond Power Line Transients On Line-Connected Capacitors

An investigation was conducted into the effect of power-line transients on capacitors used by NASA and installed on platform primary power inputs to avionics. The purpose was to investigate whether capacitor voltage rating needs to be derated for expected spike potentials. Concerns had been voiced in the past by NASA suppliers that MIL-STD-461 CS06-like requirements were overly harsh and led to physically large capacitors. The author had previously predicted that electrical-switching spike requirements representative of actual power-line transient potentials, durations and source impedance would require no derating. This investigation bore out that prediction. It was further determined that traditional low source impedance CS06-like transients also will not damage a capacitor, although the spikes themselves are not nearly as well filtered. This report should be used to allay fears that CS06-like requirements drive capacitor voltage derating. Only that derating required by the relatively long duration transients in power quality specification need concern the equipment designer.

Javor, Ken↗

NASA NTRS2000

Investigation into the Effects of Microsecond Power Line Transients on Line-Connected Capacitors

An investigation was conducted into the effect of power-line transients on capacitors used by NASA and installed on platform primary power inputs to avionics. The purpose was to investigate whether capacitor voltage ratings needs to be derated for expected spike potentials. Concerns had been voiced in the past by NASA suppliers that MIL-STD-461 CS06-like requirements were overly harsh and led to physically large capacitors. The author had previously predicted that electrical-switching spike requirements representative of actual power-line transient potentials, durations. and source impedance would require no derating. This investigation bore out that prediction. It was further determined that traditional low source impedance CS06-like transients also will not damage a capacitor, although the spikes themselves are not nearly as well filtered. This report should be used to allay fears that CS06-like requirements drive capacitor voltage derating. Only that derating required by the relatively long duration transients in power quality specification need concern the equipment designer.

Javor, K.↗

NASA NTRS2010

The Assurance Challenges of Advanced Packaging Technologies for Electronics

Advances in microelectronic parts performance are driving towards finer feature sizes, three-dimensional geometries and ever-increasing number of transistor equivalents that are resulting in increased die sizes and interconnection (I/O) counts. The resultant packaging necessary to provide assemble-ability, environmental protection, testability and interconnection to the circuit board for the active die creates major challenges, particularly for space applications, Traditionally, NASA has used hermetically packaged microcircuits whenever available but the new demands make hermetic packaging less and less practical at the same time as more and more expensive, Some part types of great interest to NASA designers are currently only available in non-hermetic packaging. It is a far more complex quality and reliability assurance challenge to gain confidence in the long-term survivability and effectiveness of nonhermetic packages than for hermetic ones. Although they may provide more rugged environmental protection than the familiar Plastic Encapsulated Microcircuits (PEMs), the non-hermetic Ceramic Column Grid Array (CCGA) packages that are the focus of this presentation present a unique combination of challenges to assessing their suitability for spaceflight use. The presentation will discuss the bases for these challenges, some examples of the techniques proposed to mitigate them and a proposed approach to a US MIL specification Class for non-hermetic microcircuits suitable for space application, Class Y, to be incorporated into M. IL-PRF-38535. It has recently emerged that some major packaging suppliers are offering hermetic area array packages that may offer alternatives to the nonhermetic CCGA styles but have also got their own inspectability and testability issues which will be briefly discussed in the presentation,

Sampson, Michael J.↗

DOE OSTI2026

From Bricks to Clicks: Mapping the White Space in Building Innovation

It is a critical national imperative to transform the buildings sector, yet innovation is impeded by deployment failures that leave promising technologies stranded. Conventional market reports and techno-economic analysis provide an insufficient understanding of markets and resource allocation for emerging building technologies. They omit crucial commercialization factors such as ecosystem maturity and adoption friction, where the coordinated participation of a network of suppliers, contractors, financiers, regulators, and integrators is required to scale solutions. This study addresses these gaps by introducing an evaluation framework grounded in front-line data from six years of the DOE's IMPEL incubator, comprising experience from 300 building-sector innovators and the adjacent, complex ecosystem. Our methodology synthesizes top-down market analysis with bottom-up, practitioner-level data across five megatrends: (M1) Affordable materials and industrialized construction; (M2) Healthy and efficient mechanical systems; (M3) Intelligent building operations; (M4) Buildings as grid assets; and (M5) High-density power and cooling for data centers and therein identify twelve "white space" technology opportunities. Next, we develop a multi-criteria scoring rubric to rank these opportunities based on parameters, i.e., Affordability, Quality of Life, Reliability, and Security, yielding composite ‘Demand’ and ‘Maturity’ indices. Our results indicate that the most significant white spaces may not be incremental products but a new class of ‘Ecosystem Enablers’, such as logistics platforms, orchestration layers, and automated compliance software that solve structural deployment gaps. This paper summarizes this transparent, evidence-based, practitioner-informed evaluation framework for policymakers and investors to re-evaluate policy and resource allocation and unlock scalable market transformation.

Singh, Reshma↗

NASA NTRS2000

CSP Manufacturing Challenges and Assembly Reliability

Although the expression of CSP is widely used by industry from suppliers to users, its implied definition had evolved as the technology has matured. There are "expert definition"- package that is up to 1.5 time die- or "interim definition". CSPs are miniature new packages that industry is starting to implement and there are many unresolved technical issues associated with their implementation. For example, in early 1997, packages with 1 mm pitch and lower were the dominant CSPs, whereas in early 1998 packages with 0.8 mm and lower became the norm for CSPs. Other changes included the use of flip chip die rather than wire bond in CSP. Nonetheless the emerging CSPs are competing with bare die assemblies and are becoming the package of choice for size reduction applications. These packages provide the benefits of small size and performance of the bare die or flip chip, with the advantage of standard die packages. The JPL-led MicrotypeBGA Consortium of enterprises representing government agencies and private companies have jointed together to pool in-kind resources for developing the quality and reliability of chip scale packages (CSPs) for a variety of projects. This talk will cover specifically the experience of our consortium on technology implementation challenges, including design and build of both standard and microvia boards, assembly of two types of test vehicles, and the most current environmental thermal cycling test results.

Ghaffarian, Reza↗

NASA NTRS2020

TCL4 UTM (UAS Traffic Management) Nevada 2019 Flight Tests, Airspace Operations Laboratory (AOL) Report

The Unmanned Aircraft Systems (UAS) Traffic Management (UTM) research project has been developing and testing concept ideas for enabling small UAS (sUAS) operations in low altitude airspace (ground to 400 feet). To do this, NASA has organized a series of flight test demonstrations. Technology Capability Level-4 (TCL4) flight tests were conducted at a Nevada, USA test site, during June 2019. The testing resulted in over 300 data collection flights using eight live rotorcraft, 15 simulated vehicles, involving six flight crews and five Unmanned Aerial System (UAS) Service Suppliers (USS). The TCL4 approach was designed to demonstrate five scenarios that set up five diverse sets of UAS events and activities. The Nevada test site focused on three of these scenarios: an incoming weather front, a concert event with an incident requiring an emergency response, and a scenario where multiple vehicles experienced Communication, Navigation, and Surveillance (CNS) issues. The test site created their scenarios to each have three phases and were required to complete three executions of each scenario, for a total of nine missions per Nevada vehicle per scenario. This document presents data collected from participants during the TCL4-Nevada flight test that provides information about how much and how well operators were able to make use of UTM functions and information, with the goal of exploring what the minimum information requirements and/or best practices might be in TCL4 operations. The driving enquiry was: how do UTM tools and features support (human) operators leading to safe and effective conduct of large-scale beyond visual line of sight (BVLOS) sUAS operations in “urban canyon” environments? As with the data collected during previous similar tests (e.g., TCL3, Martin et al., 2019), the quality of the UTM information exchanged, and the meaningfulness and therefore usefulness of this information, were all focal points of the questions asked and the data collected. Data aligned with five human-system attributes to indicate that UTM provided information that contributed to users’ ability to operate safely and effectively within UTM, but that information was not always complete and was sometimes unclear.

UTM↗

NASA NTRS1998

Issues and Methods for Assessing COTS Reliability, Maintainability, and Availability

Many vendors produce products that are not domain specific (e.g., network server) and have limited functionality (e.g., mobile phone). In contrast, many customers of COTS develop systems that am domain specific (e.g., target tracking system) and have great variability in functionality (e.g., corporate information system). This discussion takes the viewpoint of how the customer can ensure the quality of COTS components. In evaluating the benefits and costs of using COTS, we must consider the environment in which COTS will operate. Thus we must distinguish between using a non-mission critical application like a spreadsheet program to produce a budget and a mission critical application like military strategic and tactical operations. Whereas customers will tolerate an occasional bug in the former, zero tolerance is the rule in the latter. We emphasize the latter because this is the arena where there are major unresolved problems in the application of COTS. Furthermore, COTS components may be embedded in the larger customer system. We refer to these as embedded systems. These components must be reliable, maintainable, and available, and must be with the larger system in order for the customer to benefit from the advertised advantages of lower development and maintenance costs. Interestingly, when the claims of COTS advantages are closely examined, one finds that to a great extent these COTS components consist of hardware and office products, not mission critical software [1]. Obviously, COTS components are different from custom components with respect to one or more of the following attributes: source, development paradigm, safety, reliability, maintainability, availability, security, and other attributes. However, the important question is whether they should be treated differently when deciding to deploy them for operational use; we suggest the answer is no. We use reliability as an example to justify our answer. In order to demonstrate its reliability, a COTS component must pass the same reliability evaluations as the custom components, otherwise the COTS components will be the weakest link in the chain of components and will be the determinant of software system reliability. The challenge is that there will be less information available for evaluating COTS components than for custom components but this does not mean we should despair and do nothing. Actually, there is a lot we can do even in the absence of documentation on COTS components because the customer will have information about how COTS components are to be used in the larger system. To illustrate our approach, we will consider the reliability, maintainability, and availability (RMA) of COTS components as used in larger systems. Finally, COTS suppliers might consider increasing visibility into their products to assist customers in determining the components' fitness for use in a particular application. We offer ideas of information that would be useful to customers, and what vendors might do to provide it.

Schneidewind, Norman F.↗