Search NASA⌕ Search

SEARCH · Search NASA

Results for “TECHNICAL WRITING”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2003

The Technical Work Plan Tracking Tool

The Technical Work Plan Tracking Tool is a web-based application that enables interactive communication and approval of contract requirements that pertain to the administration of the Science, Engineering, Analysis, and Test (SEAT) contract at Johnson Space Center. The implementation of the application has (1) shortened the Technical Work Plan approval process, (2) facilitated writing and documenting requirements in a performance-based environment with associated surveillance plans, (3) simplified the contractor s estimate of the cost for the required work, and (4) allowed for the contractor to document how they plan to accomplish the work. The application is accessible to over 300 designated NASA and contractor employees via two Web sites. For each employee, the application regulates access according to the employee s authority to enter, view, and/or print out diverse information, including reports, work plans, purchase orders, and financial data. Advanced features of this application include on-line approval capability, automatic e-mail notifications requesting review by subsequent approvers, and security inside and outside the firewall.

Chullen, Cinda↗
NASA NTRS2018

UTM UAS Serivce Supplier Development: Sprint 1 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density and large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider(ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the first step in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and the underlying specifications for them, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and proposed specifications for USSs to participate in TCL4. This report describes Sprint One. In this Sprint, the focus was on establishing a baseline for the Application Programming Interfaces (APIs) and their associated data models. In addition, the concept of UAS Volume Reservations (UVR) (areas that impose restrictions on sUAS that are allowed to operate) was tested. NASA provided the specifications and iterated on them with partners while implementers developed to those specifications. NASA then tested each partner's implementation to ensure compatibility with all other implementers. This process helped all stakeholders gain confidence that the foundation for future Sprints was solid.

UAS service supplier↗
NASA NTRS2018

UTM UAS Service Supplier Development: Sprint 2 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the UTM Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density environments, large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider (ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the second of four planned steps in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and their underlying specifications, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and develop proposed specifications for USSs in order to to participate in TCL4. This report describes Sprint Two. In this Sprint, there was a major theme with four goals. The theme was the development and testing of a new USS discovery system, to better enable USSs to find and communicate with each other. The goals supporting this theme were: participants needed to implement and exercise the discovery service for USS-USS communications; USSs needed to demonstrate strategic deconfliction through operation sharing; the systems were to use discovery to aid in handling off-nominal operations; and finally, there was an investigation of an initial off-nominal reporting capability.

software engineering↗
NASA NTRS2012

KSC Tech Transfer News, Volume 5, No. 1

In October 2011, the White House released a presidential memorandum titled "Accelerating Technology Transfer and Commercialization of Federal Research in Support of High-Growth Businesses." It emphasized the importance of technology transfer as a driver of successful innovation to fuel economic growth, create jobs, and make U.S. industries more competitive in a global market. In response to this memorandum, NASA developed a 5-year plan for accelerating its own technology transfer activities. This plan outlines key objectives for enhancing NASA's ability to increase the rate, volume, and quality of technology transfers to industry, academia, and other Government agencies. By doing so, we are increasing the economic impact and public benefit of Federal technology investments. In addition, NASA established technology transfer as a key element of one of its Agency High Priority Performance Goals: "Enable bold new missions and make new technologies available to Government agencies and U.S. industry."What does this mean to you? In the broadest sense, NASA defines technology transfer as the utilization of NASA's technological assets- technologies, innovations, unique facilities and equipment, and technical expertise- by public and private sectors to benefit the Nation. So, if your job involves developing new technologies, writing new software, creating innovative ways to do business, performing research, or developing new technical capabilities, you could be contributing to Kennedy Space Center's (KSC) technology transfer activities by creating the technological assets that may one day be used by external partners. Furthermore, anytime you provide technical expertise to external partners, you're participating in technology transfer. The single most important step you can take to support the technology transfer process is to report new technologies and innovations ro the Technology Transfer Office. This is the critical first step in fueling the technology transfer pipeline. This is also a requirement for all Federal employees (see NPD 2091.1 B) and most NASA contractors. Detailed information on when, where, and how ro report new technology is provided on the following page. In addition, it's important that all detailed-oriented discussions about technology between NASA and external partners are documented or that they occur under formal agreements such as Space Act Agreements and Nondisclosure Agreements. Our office can assist you in putting these agreements into place, protecting NASA's interests, and providing the means to accurately measure the Agency's technology transfer activities. Technology transfer is everyone's responsibility. We need your help to ensure that NASA remains the leader in Federal technology transfer, and that the great work done at KSC provides the maximum economic and societal benefit to the Nation.

Buckingham, Bruce↗
NASA NTRSDate not supplied

Writing Good Risk Statements and Critical Thinking in Risk

The term risk is used ubiquitously in the space community, but more often than not it is used in a counterproductive way. Furthermore, risks are often written to convey some type of concern, but the risk statements are often more emotional in nature than technically substantive. In this talk, we will provide a rigorous view and definition of risk, along with some structured guidelines for writing risk statements centered on critical thinking, which will combine to provide effective risk management tools when dealing with complex space systems.

risk↗
NASA NTRS1999

TFaNS Tone Fan Noise Design/Prediction System: System Description, CUP3D Technical Documentation and Manual for Code Developers - Volume 1

TFaNS is the Tone Fan Noise Design/Prediction System developed by Pratt & Whitney under contract to NASA Lewis (presently NASA Glenn). The purpose of this system is to predict tone noise emanating from a fan stage including the effects of reflection and transmission by the rotor and stator and by the duct inlet and nozzle. These effects have been added to an existing annular duct/isolated stator noise prediction capability. TFaNS consists of: The codes that compute the acoustic properties (reflection and transmission coefficients) of the various elements and write them to files. Cup3D: Fan Noise Coupling Code that reads these files, solves the coupling problem, and outputs the desired noise predictions. AWAKEN: CFD/Measured Wake Postprocessor which reformats CFD wake predictions and/or measured wake data so it can be used by the system. This volume of the report provides technical background for TFaNS including the organization of the system and CUP3D technical documentation. This document also provides information for code developers who must write Acoustic Property Files in the CUP3D format. This report is divided into three volumes: Volume I: System Description, CUP3D Technical Documentation, and Manual for Code Developers; Volume II: User's Manual, TFaNS Vers. 1.4; Volume III: Evaluation of System Codes.

Topol, David A.↗
NASA NTRS1999

Summary of Research Report

This report describes a project to predict ducted fan noise using massively parallel computers. The investigators are part of a larger team of researchers, most of whom are working at NASA Langley Research Center. The portion of the project described below not only stands alone as an individual research project, it also compliments the NASA Langley work. The write-up included in this report is relatively brief, since the details are described in technical papers.

Long, Lyle N.↗
NASA NTRS2023

The Trash Compaction Processing System (TCPS) Technology Demonstrations Science Objectives and Requirement Definitions

Throughout the Next STEP Phase A and Phase B, the Trash Compaction Processing System (TCPS) is being developed for a technology demonstration (TD) on the International Space Station (ISS) in 2025. For Phase A, two contractors built proof-of-concept hardware. One contractor was chosen to build the TD hardware for Phase B. Both Phase A lessons learned and risk reduction activities at Ames Research Center (ARC) were used to write the TD science objectives, scope, and requirements. The work at ARC aims to retire technical risks and provide design data to TCPS developers and the ISS system integrators. This paper will summarize the lessons learned from the proof-of-concept hardware, the risk reduction activities, and how these lessons learned form the basis of the TD requirement matrix.

TCPS↗
NASA NTRS1994

1993 Technical Paper Contest for Women. Gear Up 2000: Women in Motion

The NASA Ames Research Center Advisory Committee for Women (ACW) sponsored the second ACW Technical paper Contest for Ames women in order to increase the visibility of, and to encourage writing for publication by Ames women scientists, engineers, and technicians. The topics of the contest paper mirrored in the topics of the 1993 Society for Women Engineers (SWE) National Convention, which included technological, workplace, global, and family issues.

Orans, Robin↗
NASA NTRS1984

Report format preferences of technical managers and nonmanagers

A survey of engineers and scientists concerning the format of NASA technical reports indicates that a summary as well as an abstract should be included, that the definitions of symbols and glossary of terms should be located in the front of the report, and that the illustrative material should be integrated with the text rather than grouped at the end of the report. Citation of references by number, one-column, ragged-right-margin layout, and third-person writing style are also preferred by a majority of the respondents. The preferences of managers and nonmanagers are very similar for all aspects of technical report format covered by the survey.

Pinelli, T. E.↗
NASA NTRS1995

The Capabilities of Space Stations

Over the past two years the U.S. space station program has evolved to a three-phased international program, with the first phase consisting of the use of the U.S. Space Shuttle and the upgrading and use of the Russian Mir Space Station, and the second and third phases consisting of the assembly and use of the new International Space Station. Projected capabilities for research, and plans for utilization, have also evolved and it has been difficult for those not directly involved in the design and engineering of these space stations to learn and understand their technical details. The Committee on the Space Station of the National Research Council, with the concurrence of NASA, undertook to write this short report in order to provide concise and objective information on space stations and platforms -- with emphasis on the Mir Space Station and International Space Station -- and to supply a summary of the capabilities of previous, existing, and planned space stations. In keeping with the committee charter and with the task statement for this report, the committee has summarized the research capabilities of five major space platforms: the International Space Station, the Mir Space Station, the Space Shuttle (with a Spacelab or Spacehab module in its cargo bay), the Space Station Freedom (which was redesigned to become the International Space Station in 1993 and 1994), and Skylab. By providing the summary, together with brief descriptions of the platforms, the committee hopes to assist interested readers, including scientists and engineers, government officials, and the general public, in evaluating the utility of each system to meet perceived user needs.

Source record↗
NASA NTRS2014

pFUnit 3.0 Tutorial Advanced

This tutorial will introduce Fortran developers to unit-testing and test-driven development (TDD) using pFUnit. As with other unit-testing frameworks, pFUnit, simplifies the process of writing, collecting, and executing tests while providing clear diagnostic messages for failing tests. pFUnit specifically targets the development of scientific-technical software written in Fortran and includes customized features such as: assertions for multi-dimensional arrays, distributed (MPI) and thread-based (OpenMP) parallellism, and flexible parameterized tests.These sessions will include numerous examples and hands-on exercises that gradually build in complexity. Attendees are expected to have working knowledge of F90, but familiarity with object-oriented syntax in F2003 and MPI will be of benefit for the more advanced examples. By the end of the tutorial the audience should feel comfortable in applying pFUnit within their own development environment.

Test Driven using pFUnit↗
NASA NTRS1994

NASA/DOD Aerospace Knowledge Diffusion Research Project. Report 26: The technical communication practices of aerospace engineering students: Results of the phase 3 AIAA National Student Survey

This report describes similarities and differences between undergraduate and graduate engineering students in the context of two general aspects of the educational experience. First, we explore the extent to which students differ regarding the factors that lead to the choice of becoming an engineer, current satisfaction with that choice, and career-related goals and objectives. Second, we look at the technical communication practices, habits, and training of aerospace engineering students. The reported data were obtained from a survey of student members of the American Institute of Aeronautics and Astronautics (AIAA). The survey was undertaken as a phase 3 activity of the NASA/DoD Aerospace Knowledge Diffusion Research Project. Data are reported for the following categories: student demographics; skill importance, skill training, and skill helpfulness; collaborative writing; computer and information technology use and importance; use of electronic networks; use and importance of libraries and library services; use and importance of information sources and products; use of foreign language technical reports; and foreign language (reading and speaking) skills.

Pinelli, Thomas E.↗
NASA NTRS1994

NASA/DOD Aerospace Knowledge Diffusion Research Project. Report 28: The technical communication practices of aerospace engineering and science students: Results of the phase 4 cross-national surveys

This report describes similarities and differences between undergraduate and graduate aerospace engineering and science students in the context of two general aspects of the educational experience. First, we explore the extent to which students differ regarding the factors that lead to the choice of becoming an aerospace engineer or a scientist, current satisfaction with that choice, and career-related goals and objectives. Second, we look at the technical communication skills, practices, habits, and training of aerospace engineering and science students. The reported data were obtained from a survey of students enrolled in aerospace engineering and science programs at universities in India, Japan, Russia, and the United Kingdom. The surveys were undertaken as part of the NASA/DOD Aerospace Knowledge Diffusion Research Project. Data are reported for the following categories: student demographics; skill importance, skill training, and skill helpfulness; collaborative writing; computer and information technology use and importance, use of electronic networks; use and importance of libraries and library services; use and importance of information sources and products; use of foreign language technical reports; and foreign language (reading and speaking) skills.

Pinelli, Thomas E.↗
NASA NTRS1994

NASA/DOD Aerospace Knowledge Diffusion Research Project. Report 27: The technical communication practices of engineering and science students: Results of the phase 3 academic surveys

This report describes similarities and differences between undergraduate and graduate engineering science students in the context of two general aspects of the educational experience. First, we explore the extent to which students differ regarding the factors that lead to the choice of becoming an engineer or a scientist, current satisfaction with that choice, and career-related goals and objectives. Second, we look at the technical communication practices, habits, and training of engineers and science (Physics) students. The reported data were obtained from a survey of students enrolled in the College of Engineering at the University of Illinois at Urbana-Champaign, Bowling Green State University, and Texas A&M University. The survey was undertaken as part of the NASA/DOD Aerospace Knowledge Diffusion Research Project. Data are reported for the following categories: student demographics; skill importance, skill training, and skill helpfulness; collaborative writing; computer and information technology use and importance, use of electronic networks; use and importance of libraries and library services; use and importance of information sources and products; use of foreign technical reports; and foreign language (reading and speaking) skills.

Pinelli, Thomas E.↗
NASA NTRS2005

ASK Magazine; No. 21

THIS ISSUE FEATURES A VISUAL DEPICTION OF THE ACADEMY of Program and Project Leadership (APPL). I imagine a variety of initial reactions to the drawing. One might be, "What is a cartoon doing in a magazine about project management?" Or perhaps, "Wow, nice colors-and fun." Another may be to closely search the image for signs, symbols and meaning. Still another, to read a new level of innovation and creativity into the picture. Undoubtedly, some readers will raise questions about the cost. Of course, any reaction is a sign of engagement. The stronger, the more energized the emotional and cognitive processing, the better. It is a sign of attention and interaction. For I've heard it said, "You only need to worry if they don t care one way or the other." So what is the point of the picture? To stimulate interest, raise questions, promote discussion, and maybe raise a smile.. .That, at least, was my initial reaction when I was introduced to the work of Nancy Hegedus, who helps to create these drawings for Root Learning Inc. At the NASA PM Conference, I was first shown the work Nancy had been doing with the help of Goddard s Knowledge Management Architect, Dr. Ed Rogers. I was immediately drawn into the power of visualization as a tool for more effective learning, communicating, and conveying complex knowledge concepts. We need new tools in today s world, where information and data overwhelms by sheer volume. There are articles, pamphlets, communications, and white papers-all aiming to convince and influence. Reactions to these tend to be either avoidance or mind-numbing, heavy-eyed consent; the message never registers or enters the soul. That s one of the reasons that APPL s Knowledge Sharing Initiative (KSI) has turned to storytelling as a memorable way of transfer- ring knowledge, inspiring imitation of best practices, and spurring reflection. ASK Magazine s recent fourth birthday marks an important milestone in APPL s continuing quest to provide ongoing support to project managers and to promote mission success. And similar to storytelling, the power of visualization is receiving increasing attention in recent years as a way to stimulate engagement. Pictures and visual graphs are viewed as one of the most effective ways for displaying, describing, and generating discussion about quantitative and technically complex information. Prototypes, models, and simulations are considered essential for stimulating innovation through open and engaging discussions. There has also been extensive writing on the use of visual graphics, pictures, and cartoons to facilitate memory, creativity, openness, attention-and even well-being. For many of these reasons, I am excited to have a colorful visual depiction of the APPL world included in ASK. Without the addition of text or slides, the intent is to invite people into the world of the APPL mission-as well as its products, services, customers, and partners- in a fun and engaging manner. As project leaders strive to find ways to encourage engagement, learning, and transmission of knowledge, traditional technologies are proving to be as valuable as modern technologies. (But for those who want more information in the form of texts and slide presentations, we certainly have an abundance of those as well.)

Laufer, Alexander↗
NASA NTRS1994

Optical storage media data integrity studies

Optical disk-based information systems are being used in private industry and many Federal Government agencies for on-line and long-term storage of large quantities of data. The storage devices that are part of these systems are designed with powerful, but not unlimited, media error correction capacities. The integrity of data stored on optical disks does not only depend on the life expectancy specifications for the medium. Different factors, including handling and storage conditions, may result in an increase of medium errors in size and frequency. Monitoring the potential data degradation is crucial, especially for long term applications. Efforts are being made by the Association for Information and Image Management Technical Committee C21, Storage Devices and Applications, to specify methods for monitoring and reporting to the user medium errors detected by the storage device while writing, reading or verifying the data stored in that medium. The Computer Systems Laboratory (CSL) of the National Institute of Standard and Technology (NIST) has a leadership role in the development of these standard techniques. In addition, CSL is researching other data integrity issues, including the investigation of error-resilient compression algorithms. NIST has conducted care and handling experiments on optical disk media with the objective of identifying possible causes of degradation. NIST work in data integrity and related standards activities is described.

Podio, Fernando L.↗
NASA NTRS1998

Reese Sorenson's Individual Professional Page

The subject document is a World Wide Web (WWW) page entitled, "Reese Sorenson's Individual Professional Page." Its can be accessed at "http://george.arc.nasa.gov/~sorenson/personal/index.html". The purpose of this page is to make the reader aware of me, who I am, and what I do. It lists my work assignments, my computer experience, my place in the NASA hierarchy, publications by me, awards received by me, my education, and how to contact me. Writing this page was a learning experience, pursuant to an element in my Job Description which calls for me to be able to use the latest computers. This web page contains very little technical information, none of which is classified or sensitive.

Sorenson, Reese↗