Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “technical”

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
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 NTRS2005

Vehicle Integrated Performance Analysis, the VIPA Experience: Reconnecting with Technical Integration

Today's NASA is facing significant challenges and changes. The Exploration initiative indicates a large increase in projects with limited increase in budget. The Columbia report has criticized NASA for its lack of insight and technical integration impacting its ability to provide safety. The Aldridge report is advocating NASA find new ways of doing business. Very early in the Space Launch Initiative (SLI) program a small team of engineers at MSFC were asked to propose a process for performing a system level assessment of a launch vehicle. The request was aimed primarily at providing insight and making NASA a "smart buyer." Out of this effort the VIPA team was created. The difference between the VIPA effort and many integration attempts is that VIPA focuses on using experienced people from various disciplines and a process which focuses them on a technically integrated assessment. Most previous attempts have focused on developing an all encompassing software tool. In addition, VIPA anchored its process formulation in the experience of its members and in early developmental Space Shuttle experience. The primary reference for this is NASA-TP-2001-210092, "Launch Vehicle Design Process: Characterization, Technical Integration, and Lessons Learned," and discussions with its authors. The foundations of VIPA's process are described. The VIPA team also recognized the need to drive detailed analysis earlier in the design process. Analyses and techniques typically done in later design phases, are brought forward using improved computing technology. The intent is to allow the identification of significant sensitivities, trades, and design issues much earlier in the program. This process is driven by the T-model for Technical Integration described in the aforementioned reference. VIPA's approach to performing system level technical integration is discussed in detail. Proposed definitions are offered to clarify this discussion and the general systems integration dialog. VIPA's capabilities and process can now be used to significantly enhance the development and monitoring of realizable project requirements. This is done through the use of VIPA's V-model. Starting with a given concept, VIPA's assessment validates the concept's stated performance, identifies significant issues either with the concept or the requirements, and then re-integrates these issues to determine impacts. This process is discussed along with a description of how it may be integrated into a program's insight and review process. The VIPA process has been employed successfully on several projects including SLI, Orbital Space Plane (OSP), and several heavy lift concepts for Exploration. It has also been proposed for use on the Jupiter Icy Moon (JIMO) spacecraft. The VIPA process has gained favor with both engineering and project organizations for being responsive and insightful. Selected results from these assessments will be presented.

McGhee, David S.↗
NASA NTRS2009

TurboTech Technical Evaluation Automated System

TurboTech software is a Web-based process that simplifies and semiautomates technical evaluation of NASA proposals for Contracting Officer's Technical Representatives (COTRs). At the time of this reporting, there have been no set standards or systems for training new COTRs in technical evaluations. This new process provides boilerplate text in response to interview style questions. This text is collected into a Microsoft Word document that can then be further edited to conform to specific cases. By providing technical language and a structured format, TurboTech allows the COTRs to concentrate more on the actual evaluation, and less on deciding what language would be most appropriate. Since the actual word choice is one of the more time-consuming parts of a COTRs job, this process should allow for an increase in quantity of proposals evaluated. TurboTech is applicable to composing technical evaluations of contractor proposals, task and delivery orders, change order modifications, requests for proposals, new work modifications, task assignments, as well as any changes to existing contracts.

Tiffany, Dorothy J.↗
NASA NTRS2009

An Effective Health and Medical Technical Authority

The NASA Governance model directed the formation of three Technical Authorities, Engineering; Safety and Mission Assurance; and Health and Medical, to ensure that risks are identified and adjudicated efficiently and transparently in concert with the spaceflight programs and projects. The Health and Medical Technical Authority (HMTA) has been implemented at the Johnson Space Center (JSC) and consists of the Chief Medical Office (CMO), the Deputy CMO, and HMTA Delegates. The JSC HMTA achieves the goals of risk identification and adjudication through the discharge of the appropriate technical expertise to human space flight programs and projects and the escalation of issues within program and technical authority boards. The JSC HMTA relies on subject matter experts (SMEs) in the Space Life Sciences Directorate at JSC as well as experts from other Centers to work crew health and performance issues at the technical level, develop requirements, oversee implementation and validation of requirements, and identify risks and non-compliances. Once a risk or potential noncompliance has been identified and reported to the programs or projects, the JSC HMTA begins to track it and closely monitor the program's or project's response. As a risk is developed or a non-compliance negotiated, positions from various levels of decision makers are sought at the program and project control boards. The HMTA may support a program or project position if it is satisfied with the decision making and vetting processes (ex. the subject matter expert voiced his/her concerns and all dissenting opinions were documented) and finds that the position both acknowledges the risk and cost of the mitigation and resolves the issue without changing NASA risk posture. The HMTA may disagree with a program or project position if the NASA risk posture has been elevated or obfuscated. If the HMTA does disagree with the program or project position, it will appeal to successively higher levels of authority so that risk acceptance and risk trades will be acknowledged and sanctioned at the highest appropriate level; this includes Program Managers, Mission Directorate Associate Administrators and the Agency Administrator.

Fogarty, Jennifer A.↗
NASA NTRS1974

The NASA/JPL 64-meter-diameter antenna at Goldstone, California: Project report, technical staff, tracking and data acquisition organization

The significant management and technical aspects of the JPL Project to develop and implement a 64-meter-diameter antenna at the Goldstone Deep Space Communications Complex in California, which was the first of the Advanced Antenna Systems of the National Aeronautics and Space Administration/Jet Propulsion Laboratory Deep Space Network are described. The original need foreseen for a large-diameter antenna to accomplish communication and tracking support of NASA's solar system exploration program is reviewed, and the translation of those needs into the technical specification of an appropriate ground station antenna is described. The antenna project is delineated by phases to show the key technical and managerial skills and the technical facility resources involved. There is a brief engineering description of the antenna and its closely related facilities. Some difficult and interesting engineering problems, then at the state-of-the-art level, which were met in the accomplishment of the Project, are described. The key performance characteristics of the antenna, in relation to the original specifications and the methods of their determination, are stated.

Source record↗
NASA NTRS1977

Technical assistance and the transfer of remote sensing technology

The transfer of technology from industrialized countries to the third world is a very complicated process and one that requires a great deal of research and development. The political and social obstacles to this transfer are generally greater than the technical obstacles, but technical assistance programs have neither the competence nor the inclination to deal with these factors adequately. Funding for technical assistance in remote sensing is now expanding rapidly, and there is a growing need for institutions to study and promote the effective use of this technology for economic development. The United Nations, the Food and Agriculture Organization, the World Bank, the United States Agency for International Development and the Canadian technical assistance agencies take different approaches to the problem and deal with the political pressures in different ways.

Chipman, R.↗
NASA NTRS1981

Technical Writing: Past, Present and Future

The training of technical writers and the objectives of such education are discussed. Special emphasis was placed on the communication between technical personnel and non-technical personnel. The liabilities that affect technical writers were also discussed.

Mathes, J. C.↗
NASA NTRS1981

Applied tagmemics: A heuristic approach to the use of graphic aids in technical writing

In technical report writing, two needs which must be met if reports are to be useable by an audience are the language needs and the technical needs of that particular audience. A heuristic analysis helps to decide the most suitable format for information; that is, whether the information should be presented verbally or visually. The report writing process should be seen as an organic whole which can be divided and subdivided according to the writer's purpose, but which always functions as a totality. The tagmemic heuristic, because it itself follows a process of deconstructing and reconstructing information, lends itself to being a useful approach to the teaching of technical writing. By applying the abstract questions this heuristic asks to specific parts of the report. The language and technical needs of the audience are analyzed by examining the viability of the solution within the givens of the corporate structure, and by deciding which graphic or verbal format will best suit the writer's purpose. By following such a method, answers which are both specific and thorough in their range of application are found.

Brownlee, P. P.↗
NASA NTRS1981

Technical communication. Perspectives for the Eighties, part 2

The importance of technical writing as a separate discipline is suggested. Some specific areas addressed were: technical writing skills industry needs, definitions of technical writing, the hows and whys of inhouse writing, and the nature of the composing process in technical comunication.

Mathes, J. C.↗
NASA NTRS1981

Some technical writing skills industry needs

It is suggested that engineers and other technical students be taught three classes of skills in technical writing. First, "Big Picture Things", which includes: the importance of clear writing, the wide scope of writing, the wide scope of writing tasks that will be faced in industry, and the principles of organization of technical materials such as; how to analyze, classify, partition, and interpret. Second, "Writing Procedures", which encompasses: how to get words on paper efficiently and team-write. Third, "Writing Details", in which two considerations are important: how to achieve precision in the use of language and the aspects of style. Three problems in style are cited: the problem of sentence transition, overuse of attributive adjectives, and verbosity in paragraph structure. The most important thing in technical writing is considered to be functionality, economy and clarity.

Smith, F. R.↗
NASA NTRS1981

Teaching audience analysis to the technical student

Teaching audience analysis, as practiced in a technical writing course for engineering students, is discussed. Audience analysis is described as the task of defining the audience for a particular piece of writing and determining those characteristics of the audience which constrain the writer and effect reception of the message. A mature technical writing style that shows the tension produced when a text is written to be read and understood is considered in terms of audience analysis. Techniques include: (1) conveying to students the concept that a reader with certain expectations exist, (2) team teaching to preserve the context of a given technical discipline, and (3) assigning a technical report that addresses a variety of readers, thus establishing the complexity of audience oriented writing.

Debs, M. B.↗
NASA NTRS1984

FY 1984 scientific and technical reports, articles, papers and presentations

This bibliography lists formal NASA technical reports, papers published in technical journals, and presentations by MSFC personnel. Abstracts are presented for 56 technical memorandum, and 13 technical papers. Six publications, over 260 contractor reports, and more than 300 papers cleared for publication are cited.

Turner, J. E.↗
NASA NTRS1988

Exploration Studies Technical Report - Volume 2: Studies Approach and Results

The NASA Office of Exploration has been tasked with defining and recommending alternatives for an early 1990's national decision on a focused program of human exploration of the solar system. The Mission Analysis and System Engineering (MASE) group, which is managed by the Exploration Studies Office at the Johnson Space Center, is responsible for coordinating the technical studies necessary for accomplishing such a task. This technical report describes the process that has been developed in a case study approach. The four case studies that were developed in FY88 include: 1. Human expedition to Phobos 2. Human expeditions to Mars 3. Lunar observatory 4. Lunar outpost to early Mars evolution The final outcome of this effort is a set of programmatic and technical conclusions and recommendations for the following year's work. Volume 2 describes the case study process, the technical results of each of the case studies, and opportunities for additional study. Included in the discussion of each case study is a description of the mission key features and profile. Mission definition and manifesting are detailed, followed by a description of the mission architecture and infrastructure. Systems concepts for the required orbital nodes, transportation systems, and planetary surface systems are discussed. Prerequisite implementation plans resulting from the synthesized case studies are described and in-depth assessments are presented.

Interplanetary flight↗
NASA NTRS1989

Technical communication in aeronautics - Results of an exploratory study

A study was undertaken that explored several aspects of technical communications in aeronautics. The study utilized survey research. A self-administered mail questionnaire was sent to 2,000 randomly selected members of the American Institute of Aeronautics and Astronautics (AIAA) in the U.S. with academic, government, or industrial affiliations. Six hundred and six (606) usable questionnaires were received. The findings add considerable information to the knowledge of technical communications among aeronautical engineers and scientists; reinforce some of the conventional wisdom about technical communications and question other widely-held notions; and hold significant implications for technical communicators, information managers, research and development managers, and curriculum developers.

Pinelli, Thomas E.↗
NASA NTRS1989

[NASA/DOD Aerospace Knowledge Diffusion Research Project. Report 2:] Technical communications in aeronautics: Results of an exploratory study. An analysis of managers' and nonmanagers' responses

Data collected from an exploratory study concerned with the technical communications practices of aerospace engineers and scientists were analyzed to test the primary assumption that aerospace managers and nonmanagers have different technical communications practices. Five assumptions were established for the analysis. Aerospace managers and nonmanagers were found to have different technical communications practices for three of the five assumptions tested. Although aerospace managers and nonmanagers were found to have different technical communications practices, the evidence was neither conclusive nor compelling that the presumption of difference in practices could be attributed to the duties performed by aerospace managers and nonmanagers.

Pinelli, Thomas E.↗
NASA NTRS1989

[NASA/DOD Aerospace Knowledge Diffusion Research Project. Report 3:] Technical communications in aeronautics: Results of an exploratory study. An analysis of profit managers' and nonprofit managers' responses

Data collected from an exploratory study concerned with the technical communications practices of aerospace engineers and scientists were analyzed to test the primary assumption that profit and nonprofit managers in the aerospace community have different technical communications practices. Five assumptions were established for the analysis. Profit and nonprofit managers in the aerospace community were found to have different technical communications practices for one of the five assumptions tested. It was, therefore, concluded that profit and nonprofit managers in the aerospace community do not have different technical communications practices.

Pinelli, Thomas E.↗
NASA NTRS1990

[NASA/DOD Aerospace Knowledge Diffusion Research Project. Paper 1:] The value of Scientific and Technical Information (STI), its relationship to Research and Development (R&D), and its use by US aerospace engineers and scientists

The relationship between scientific and technical information (STI), its use by aerospace engineers and scientists, and the aerospace R&D process is examined. Data are presented from studies of the role of STI in the performance and management of R&D activities and the behavior of engineers when using and seeking information. Consideration is given to the information sources used to solve technical problems, the production and use of technical communications, and the use of libraries, technical information centers, and on-line data bases.

Pinelli, Thomas E.↗