Search NASA⌕ Search

SEARCH · Search NASA

Results for “COMPONENT REPORTS”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS1981

Energy efficient engine fan component detailed design report

The fan component which was designed for the energy efficient engine is an advanced high performance, single stage system and is based on technology advancements in aerodynamics and structure mechanics. Two fan components were designed, both meeting the integrated core/low spool engine efficiency goal of 84.5%. The primary configuration, envisioned for a future flight propulsion system, features a shroudless, hollow blade and offers a predicted efficiency of 87.3%. A more conventional blade was designed, as a back up, for the integrated core/low spool demonstrator engine. The alternate blade configuration has a predicted efficiency of 86.3% for the future flight propulsion system. Both fan configurations meet goals established for efficiency surge margin, structural integrity and durability.

Halle, J. E.↗
NASA NTRS1983

Energy efficient engine. Fan and quarter-stage component performance report

The fan configuration for the general Electric/NASA Energy Efficient Engine was selected following an extensive preliminary design study. The fan has an inlet radius ratio of 0.342 and a specific flowrate of 208.9 Kg/sec/sq. m (42.8 1bm/sec/sq. ft). The design corrected tip speed is 411.5 m/sec (1350 ft/sec) producing a bypass flow total-pressure ratio of 1.65 and a core flow total-pressure ratio of 1.6. The design bypass ratio is 6.8. The aerodynamic design point corresponds to the maximum climb power setting at Mach 0.8 and 10.67 Km (35,000 ft) altitude. The fully-instrumented fan component was tested in the Lynn Large Fan Test Facility in 1981. The overall performance results, reported herein, showed excellent fan performance with the fan meeting all of its component test goals of flow, efficiency and stall margin.

Cline, S. J.↗
NASA NTRS1983

High pressure compressor component performance report

A compressor optimization study defined a 10 stage configuration with a 22.6:1 pressure ratio, an adiabatic efficiency goal of 86.1%, and a polytropic efficiency of 90.6%; the corrected airflow is 53.5 kg/s. Subsequent component testing included three full scale tests: a six stage rig test, a 10 stage rig test, and another 10 stage rig test completed in the second quarter of 1982. Information from these tests is used to select the configuration for a core engine test and an integrated core/low spool test. The test results will also provide data base for the flight propulsion system. The results of the test series with both aerodynamic and mechanical performance of each compressor build are presented. The second 10 stage compressor adiabatic efficiency was 0.848 at a cruise operating point versus a test goal of 0.846.

Cline, S. J.↗
NASA NTRS1984

Energy Efficient Engine: Control system component performance report

An Energy Efficient Engine (E3) program was established to develop technology for improving the energy efficiency of future commercial transport aircraft engines. As part of this program, General Electric designed and tested a new engine. The design, fabrication, bench and engine testing of the Full Authority Digital Electronic Control (FADEC) system used for controlling the E3 Demonstrator Engine is described. The system design was based on many of the proven concepts and component designs used on the General Electric family of engines. One significant difference is the use of the FADEC in place of hydromechanical computation currently used.

Beitler, R. S.↗
NASA NTRS1975

Reliability data for electronic and electromechanical components: A report

Ten classes of parts covered in report: capacitors, crystals, diodes, fuses, inductors, microcircuits, relays, fixed resistors, transformers, and transistors. Each class is contained in separate section and includes discussion of inherent failure modes, screening rationale, general screening requirements, derating criteria, and stress-analysis data.

Scott, W. R.↗
NASA NTRS1996

NASA/DOD Aerospace Knowledge Diffusion Research Project: Survey of Reader Preferences Concerning the Format of NASA Langley-Authored Technical Reports - Paper 58

The U.S. government technical report is a primary means by which the results of federally funded research and development (R&D) are transferred to the U.S. aerospace industry. However, little is known about this information product in terms of its actual use, importance, and value in the transfer of federally funded R&D. Little is also known about the intermediary-based system that is used to transfer the results of federally funded R&D to the U.S. aerospace industry. To help establish a body of knowledge, the U.S. government technical report is being investigated as part of the NASA/DOD Aerospace Knowledge Diffusion Research Project. In this paper, we summarize the literature on the U.S. government technical report and present the results of a survey of U.S. aerospace engineers and scientists that solicited their opinions concerning the format of NASA Langley Research Center (LaRC)-authored technical reports. To learn more about the preferences of U.S. aerospace engineers and scientists concerning the format of NASA LaRC-authored technical reports, we surveyed 133 report producers (i.e., authors) and 137 report users in March-April 1996. Questions covered such topics as (1) the order in which report components are read, (2) components used to determine if a report would be read, (3) those components that could be deleted, (4) the placement of such components as the symbols list, (e) the de-sirability of a table of contents, (5) the format of reference citations, (6) column layout and right margin treatment, and (7) and person and voice. Mail (self-reported) surveys were used to collect the data. The response rates for report producers (i.e., authors) was 68% and for users was 62%.

Pinelli, Thomas E.↗
NASA NTRS1997

NASA/DOD Aerospace Knowledge Diffusion Research Project. Paper 65: Survey of Reader Preferences Concerning the Format of NASA Langley-Authored Technical Reports

The U.S. government technical report is a primary means by which the results of federally funded research and development (R&D) are transferred to the U.S. aerospace industry. However, little is known about this information product in terms of its actual use, importance, and value in the transfer of federally funded R&D. Little is also known about the intermediary-based system that is used to transfer the results of federally funded R&D to the U.S. aerospace industry. To help establish a body of knowledge, the U.S. government technical report is being investigated as part of the NASA/DoD Aerospace Knowledge Diffusion Research Project. In this article, we summarize the literature on the U.S. government technical report and present the results of a survey of U.S. aerospace engineers and scientists that solicited their opinions concerning the format of NASA Langley Research Center (LaRC)-authored technical reports. To learn more about the preferences of U.S. aerospace engineers and scientists concerning the format of NASA LaRC-authored technical reports, we surveyed 133 report producers (i.e., authors) and 137 report users in March-April 1996. Questions covered such topics as: (a) the order in which report components are read; (b) components used to determine if a report would be read; (c) those components that could be deleted; (d) the placement of such components as the symbols list; (e) the desirability of a table of contents; (f) the format of reference citations; (g) column layout and right margin treatment; and (h) writing style in terms of person and voice. Mail (self-reported) surveys were used to collect the data. The response rates for report producers (i.e., authors) was 68% and for users was 62%.

Pinelli, Thomas E.↗
NASA NTRS1981

The technical report as an effective medium for information transmittal

The NASA technical report is evaluated to determine its effectiveness as a medium for information transmittal. Empirical data was compiled through a survey of report producers and through an assessment of report components, format, and organization found in current style manuals. It was found that little documented research exists to support or suggest criteria for assessing the effectiveness of a technical report. The survey showed that wide variances in the technical report exist: ninety-nine report producers generated ninety-eight different structural components, only five of which were used by 50% or more of the respondents. Moreover, 33% of the respondents claimed to use no style manual at all. Future research is planned to assess the adequacy of a reduced set of report components, clearly defining the purpose and evaluating the criteria for each component.

Stohrer, F. F.↗
NASA NTRS1983

Polymeric Applications in Electronics

Training manual shows how to use polymeric materials in fabrication electronic components. Report discusses polymeric applications in fabrication of electronic components and equipment. Intended as training manual for 6-day quality assurance and technician certification course in use of polymeric materials.

Read, W. S.↗
NASA NTRS2015

Using Publish-Subscribe Messaging for System Status and Automation

The NASA Goddard Mission Services Evolution Center (GMSEC) system is a message-based plug-and-play open system architecture used in many of NASA mission operations centers. This presentation will focus on the use of GMSEC standard messages to report and analyze the status of a system and enable the automation of the system's components. In GMSEC systems, each component reports its status using a keep-alive message and also publishes status and activities as log messages. In addition, the components can accept functional directive messages from the GMSEC message bus. Over the past several years, development teams have found ways to utilize these messages to create innovative display pages and increasingly sophisticated approaches to automation. This presentation will show the flexibility and value of the message-based approach to system awareness and automation.

Enterprise↗