Search NASA⌕ Search

SEARCH · Search NASA

Results for “Technical Scope”

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 163 records · Page 9

Coordinating Council. Seventh Meeting: Acquisitions

The theme for this NASA Scientific and Technical Information Program Coordinating Council meeting was Acquisitions. In addition to NASA and the NASA Center for AeroSpace Information (CASI) presentations, the report contains fairly lengthy visuals about acquisitions at the Defense Technical Information Center. CASI's acquisitions program and CASI's proactive acquisitions activity were described. There was a presentation on the document evaluation process at CASI. A talk about open literature scope and coverage at the American Institute of Aeronautics and Astronautics was also given. An overview of the STI Program's Acquisitions Experts Committee was given next. Finally acquisitions initiatives of the NASA STI program were presented.

Source record↗

Comparison of Two Recent Launch Abort Platforms

The development of new and safer manned space vehicles is a top priority at NASA. Recently two different approaches of how to accomplish this mission of keeping astronauts safe was successfully demonstrated. With work already underway on an Apollo-like launch abort system for the Orion Crew Exploration Vehicle (CEV), an alternative design concept named the Max Launch Abort System, or MLAS, was developed as a parallel effort. The Orion system, managed by the Constellation office, is based on the design of a single solid launch abort motor in a tower positioned above the capsule. The MLAS design takes a different approach placing the solid launch abort motor underneath the capsule. This effort was led by the NASA Engineering and Safety Center (NESC). Both escape systems were designed with the Ares I Rocket as the launch vehicle and had the same primary requirement to safely propel a crew module away from any emergency event either on the launch pad or during accent. Beyond these two parameters, there was little else in common between the two projects, except that they both concluded in successful launches that will further promote the development of crew launch abort systems. A comparison of these projects from the standpoint of technical requirements; program management and flight test objectives will be done to highlight the synergistic lessons learned by two engineers who worked on each program. This comparison will demonstrate how the scope of the project architecture and management involvement in innovation should be tailored to meet the specific needs of the system under development.

Dittemore, Gary D.↗

Exploring Mission Concepts with the JPL Innovation Foundry A-Team

The JPL Innovation Foundry has established a new approach for exploring, developing, and evaluating early concepts called the A-Team. The A-Team combines innovative collaborative methods with subject matter expertise and analysis tools to help mature mission concepts. Science, implementation, and programmatic elements are all considered during an A-Team study. Methods are grouped by Concept Maturity Level (CML), from 1 through 3, including idea generation and capture (CML 1), initial feasibility assessment (CML 2), and trade space exploration (CML 3). Methods used for each CML are presented, and the key team roles are described from two points of view: innovative methods and technical expertise. A-Team roles for providing innovative methods include the facilitator, study lead, and assistant study lead. A-Team roles for providing technical expertise include the architect, lead systems engineer, and integration engineer. In addition to these key roles, each A-Team study is uniquely staffed to match the study topic and scope including subject matter experts, scientists, technologists, flight and instrument systems engineers, and program managers as needed. Advanced analysis and collaborative engineering tools (e.g. cost, science traceability, mission design, knowledge capture, study and analysis support infrastructure) are also under development for use in A-Team studies and will be discussed briefly. The A-Team facilities provide a constructive environment for innovative ideas from all aspects of mission formulation to eliminate isolated studies and come together early in the development cycle when they can provide the biggest impact. This paper provides an overview of the A-Team, its study processes, roles, methods, tools and facilities.

Team Eureka↗

PAN AIR: A computer program for predicting subsonic or supersonic linear potential flows about arbitrary configurations using a higher order panel method. Volume 4: Maintenance document (version 1.1)

The Maintenance Document is a guide to the PAN AIR software system, a system which computes the subsonic or supersonic linear potential flow about a body of nearly arbitrary shape, using a higher order panel method. The document describes the over-all system and each program module of the system. Sufficient detail is given for program maintenance, updating and modification. It is assumed that the reader is familiar with programming and CDC (Control Data Corporation) computer systems. The PAN AIR system was written in FORTRAN 4 language except for a few COMPASS language subroutines which exist in the PAN AIR library. Structured programming techniques were used to provide code documentation and maintainability. The operating systems accommodated are NOS 1.2, NOS/BE and SCOPE 2.1.3 on the CDC 6600, 7600 and Cyber 175 computing systems. The system is comprised of a data management system, a program library, an execution control module and nine separate FORTRAN technical modules. Each module calculates part of the posed PAN AIR problem. The data base manager is used to communicate between modules and within modules. The technical modules must be run in a prescribed fashion for each PAN AIR problem. In order to ease the problem of supplying the many JCL cards required to execute the modules, a separate module called MEC (Module Execution Control) was created to automatically supply most of the JCL cards. In addition to the MEC generated JCL, there is an additional set of user supplied JCL cards to initiate the JCL sequence stored on the system.

Baruah, P. K.↗

ExMC Technology Watch

The Technology Watch (Tech Watch) project is a NASA project that is operated under the Human Research Programs (HRP) Exploration Medical Capability (ExMC) element, and focuses on ExMC technology gaps. The project coordinates the efforts of several NASA centers, including the Johnson Space Center (JSC), Glenn Research Center (GRC), Ames Research Center (ARC), and the Langley Research Center (LaRC). The objective of Tech Watch is to identify emerging, high-impact technologies that augment current NASA HRP technology development efforts. Identifying such technologies accelerates the development of medical care and research capabilities for the mitigation of potential health issues encountered during human space exploration missions. The aim of this process is to leverage technologies developed by academia, industry and other government agencies and to identify the effective utilization of NASA resources to maximize the HRP return on investment. The establishment of collaborations with these entities is beneficial to technology development, assessment and/or insertion and further NASAs goal to provide a safe and healthy environment for human exploration. In 2012, the Tech Watch project expanded the scope of activities to cultivate student projects targeted at specific ExMC gaps, generate gap reports for a majority of the ExMC gaps and maturate a gap report review process to optimize the technical and managerial aspects of ExMC gap status. Through numerous site visits and discussions with academia faculty, several student projects were initiated and/or completed this past year. A key element to these student projects was the ability of the project to align with a specific ExMC technology or knowledge gap. These projects were mentored and reviewed by Tech Watch leads at the various NASA centers. Another result of the past years efforts was the population of the ExMC wiki website that now contains more the three quarters of the ExMC gap reports. The remaining gap reports will be completed in FY13. Finally, the gap report review process for all ExMC gaps was initiated. This review process was instrumental in ensuring that each gap report was thoroughly reviewed for accuracy and relevant content prior to its public release. In the upcoming year, the gap report review process will be refined such that in addition to the gap report update, programmatic information related to gap closure will also be emphasized.

Krihak, M.↗

NASA Patent Abstracts October 2006: A Continuing Bibliography

Several thousand inventions result each year from research supported by the National Aeronautics and Space Administration. NASA seeks patent protection on inventions to which it has title if the invention has important use in government programs or significant commercial potential. These inventions cover a broad range of technologies and include many that have useful and valuable commercial application. NASA inventions best serve the interests of the United States when their benefits are available to the public. In many instances, the granting of nonexclusive or exclusive licenses for the practice of these inventions may assist in the accomplishment of this objective. This bibliography is published as a service to companies, firms, and individuals seeking new, licensable products for the commercial market. The NASA Patent Abstracts Bibliography is an annual NASA publication containing comprehensive abstracts of NASA-owned inventions covered by U.S. patents. The citations included were originally published in NASA s Scientific and Technical Aerospace Reports (STAR) and cover STAR announcements made since May 1969. The citations published in this issue cover the period July 2005 through September 2006. The range of subjects covered includes the NASA Scope and Subject Category Guide's 10 broad subject divisions separated further into 76 specific categories. However, not all categories contain citations during the dates covered for this issue; therefore, the Table of Contents does not include all divisions and categories. This scheme was devised in 1975 and last revised in 2005 in lieu of the 34 category divisions which were utilized in supplements (01) through (06) covering STAR abstracts from May 1969 through January 1974. Each entry consists of a citation accompanied by an abstract and, when appropriate, a key illustration taken from the patent or application for patent. Entries are arranged by subject category in ascending order. When available, citations contain a link to the full-text document online. Two indexes, Subject Term and Personal Author, are available within the publication.

Source record↗

Turning Operational Lessons Learned into Design Reality

The capabilities and limitations of a particular system design are well known by the people who operate it. Operational workarounds, operational notes and lessons learned are traditional methods for dealing with and documenting design shortcomings. The beginning of each new program brings the hope that hard-learned lessons will be incorporated into the next new system. But often operations personnel find their well-intentioned efforts frustrated by an inability to have their inputs considered by design personnel who have strictly-scoped requirements that are coupled with ambitious cost and schedule targets. There is a way for operational inputs to make it into the design, but the solution involves a combination of organizational culture and technical data. Any organization that utilizes this approach can realize significant benefits over the life cycle of their project.

Brady, David A.↗

The Helios program and the sun

Helios A and B are the first two missions inside the orbit of the Mercury towards the sun. They were launched from Cape Kennedy December 10, 1974 and January 15, 1976 respectively. The interplanetary cruise in the ecliptic plane carried the Helios Solar Probes in an ecliptical orbit around the sun to perihelions as close as 0.31 (Helios A) and 0.29 (Helios B) Astronomical Units to the sun. In this technical paper the scientific mission and German and American plans and design versus accomplished mission are presented by the German and United States Project Managers and the Mission Operations Manager. A brief outline of the scope of the project, spacecraft and experiments development, integration and test programs is given. Engineering and system performance results from the Helios A and B flights, which succeeded in passing closer to the sun than any previous spacecraft, are presented. Some of the preliminary scientific findings of the ten active and two passive experiments of this ambitious German/United States cooperative project are outlined.

Ousley, G. W.↗

Study of Synthetic Vision Systems (SVS) and Velocity-vector Based Command Augmentation System (V-CAS) on Pilot Performance

This study investigated the effects of synthetic vision system (SVS) concepts and advanced flight controls on single pilot performance (SPP). Specifically, we evaluated the benefits and interactions of two levels of terrain portrayal, guidance symbology, and control-system response type on SPP in the context of lower-landing minima (LLM) approaches. Performance measures consisted of flight technical error (FTE) and pilot perceived workload. In this study, pilot rating, control type, and guidance symbology were not found to significantly affect FTE or workload. It is likely that transfer from prior experience, limited scope of the evaluation task, specific implementation limitations, and limited sample size were major factors in obtaining these results.

Liu, Dahai↗

Study of Synthetic Vision Systems (SVS) and Velocity-vector Based Command Augmentation System (V-CAS) on Pilot Performance

This study investigated the effects of synthetic vision system (SVS) concepts and advanced flight controls on single pilot performance (SPP). Specifically, we evaluated the benefits and interactions of two levels of terrain portrayal, guidance symbology, and control-system response type on SPP in the context of lower-landing minima (LLM) approaches. Performance measures consisted of flight technical error (FTE) and pilot perceived workload. In this study, pilot rating, control type, and guidance symbology were not found to significantly affect FTE or workload. It is likely that transfer from prior experience, limited scope of the evaluation task, specific implementation limitations, and limited sample size were major factors in obtaining these results.

Liu, Dahai↗

Reconfigurable, Bi-Directional Flexfet Level Shifter for Low-Power, Rad-Hard Integration

Two prototype Reconfigurable, Bi-directional Flexfet Level Shifters (ReBiLS) have been developed, where one version is a stand-alone component designed to interface between external low voltage and high voltage, and the other version is an embedded integrated circuit (IC) for interface between internal low-voltage logic and external high-voltage components. Targeting stand-alone and embedded circuits separately allows optimization for these distinct applications. Both ReBiLS designs use the commercially available 180-nm Flex fet Independently Double-Gated (IDG) SOI CMOS (silicon on insulator, complementary metal oxide semiconductor) technology. Embedded ReBiLS circuits were integrated with a Reed-Solomon (RS) encoder using CMOS Ultra-Low-Power Radiation Tolerant (CULPRiT) double-gated digital logic circuits. The scope of the project includes: creation of a new high-voltage process, development of ReBiLS circuit designs, and adjustment of the designs to maximize performance through simulation, layout, and manufacture of prototypes. The primary technical objectives were to develop a high-voltage, thick oxide option for the 180-nm Flexfet process, and to develop a stand-alone ReBiLS IC with two 8-channel I/O busses, 1.8 2.5 I/O on the low-voltage pins, 5.0-V-tolerant input and 3.3-V output I/O on the high-voltage pins, and 100-MHz minimum operation with 10-pF external loads. Another objective was to develop an embedded, rad-hard ReBiLS I/O cell with 0.5-V low-voltage operation for interface with core logic, 5.0-V-tolerant input and 3.3-V output I/O pins, and 100-MHz minimum operation with 10- pF external loads. A third objective was to develop a 0.5- V Reed-Solomon Encoder with embedded ReBilS I/O: Transfer the existing CULPRiT RS encoder from a 0.35-micron bulk-CMOS process to the ASI 180-nm Flexfet, rad-hard SOI Process. 0.5-V low-voltage core logic. 5.0-V-tolerant input and 3.3-V output I/O pins. 100-MHz minimum operation with 10- pF external loads. The stand-alone ReBiLS chip will allow system designers to provide efficient bi-directional communication between components operating at different voltages. Embedding the ReBiLS cells into the proven Reed-Solomon encoder will demonstrate the ability to support new product development in a commercially viable, rad-hard, scalable 180-nm SOI CMOS process.

DeGregorio, Kelly↗

Rover and Telerobotics Technology Program

The Jet Propulsion Laboratory's (JPL's) Rover and Telerobotics Technology Program, sponsored by the National Aeronautics and Space Administration (NASA), responds to opportunities presented by NASA space missions and systems, and seeds commerical applications of the emerging robotics technology. The scope of the JPL Rover and Telerobotics Technology Program comprises three major segments of activity: NASA robotic systems for planetary exploration, robotic technology and terrestrial spin-offs, and technology for non-NASA sponsors. Significant technical achievements have been reached in each of these areas, including complete telerobotic system prototypes that have built and tested in realistic scenarios relevant to prospective users. In addition, the program has conducted complementary basic research and created innovative technology and terrestrial applications, as well as enabled a variety of commercial spin-offs.

Weisbin, Charles R.↗

Scientific and technical photography at NASA Langley Research Center

As part of my assignment connected with the Scientific and Technical Photography & Lab (STPL) at the NASA Langley Research Center I conducted a series of interviews and observed the day to day operations of the STPL with the ultimate objective of becoming exposed first hand to a scientific and technical photo/imaging department for which my school prepares its graduates. I was also asked to share my observations with the staff in order that these comments and observations might assist the STPL to better serve its customers. Meetings with several individuals responsible for various wind tunnels and with a group that provides photo-optical instrumentation services at the Center gave me an overview of the services provided by the Lab and possible areas for development. In summary form these are some of the observations that resulted from the interviews and daily contact with the STPL facility. (1) The STPL is perceived as a valuable and almost indispensable service group within the organization. This comment was invariably made by everyone. Everyone also seemed to support the idea that the STPL continue to provide its current level of service and quality. (2) The STPL generally is not perceived to be a highly technically oriented group but rather as a provider of high quality photographic illustration and documentation services. In spite of the importance and high marks assigned to the STPL there are several observations that merit consideration and evaluation for possible inclusion into the STPL's scope of expertise and future operating practices. (1) While the care and concern for artistic rendition of subjects is seen as laudable and sometimes valuable, the time that this often requires is seen as interfering with keeping the tunnels operating at maximum productivity. Tunnel managers would like to shorten down-time due to photography, have services available during evening hours and on short notice. It may be of interest to the STPL that tunnel managers are incorporating ever greater imaging capabilities in their facilities. To some extent this could mean a reduced demand for traditional photographic services. (2) The photographic archive is seen as a Center resource. Archiving of images, as well as data, is a matter of concern to the investigators. The early holdings of the Photographic Archives are quickly deteriorating. The relative inaccessibility of the material held in the archives is problematic. (3) In certain cases delivery or preparation of digital image files instead of, or along with, hardcopy is already being perceived by the STPL's customers as desirable. The STPL should make this option available, and the fact that it has, or will have this capability widely known. (4) The STPL needs to continue to provide expert advice and technical imaging support in terms of application information to users of traditional photographic and new electronic imaging systems. Cooperative demo projects might be undertaken to maintain or improve the capabilities of the Lab. (5) STPL personnel do not yet have significant electronic imaging or electronic communication skills and improvements in this is an area could potentially have a positive impact on the Center. (6) High speed photographic or imaging services are often mentioned by the STPL as being of primary importance to their mission but the lab supports very few projects calling for high speed imaging services. Much high speed equipment is in poor state of repair. It is interesting to note that when the operation of lasers, digital imaging or quantitative techniques are requested these are directed to another NASA department. Could joint activities be initiated to solve problems? (7). The STPL could acquire more technical assignments if examples of the areas where they posses expertise would be circulated around the center. The fact that the STPL owns high speed video capability could be 'advertised' among its customer base if there truly was an interest in building up a customer base in this area. The STPL could participate in events like TOPS as an exhibitor, as well as a documenter, of the event.

Davidhazy, Andrew↗

The capability of satellite borne remote sensors to measure stratospheric trace constituents. Volume 1: Background and requirements

Volume 1 of a three volume report issued as MITRE/METREX Technical Report is presented. This volume contains a synthesis of the results of two previous MITRE/METREX studies and an update of the information. These studies deal with a comprehensive review of stratospheric trace constituent measurement requirements. The scope of the study was restricted to those contituents which fall into the general category of air pollutants.

Keitz, E. L.↗

Bibliography of spatial interferometry in optical astronomy

The Bibliography of Spatial Interferometry in Optical Astronomy is a guide to the published literature in applications of spatial interferometry techniques to astronomical observations, theory and instrumentation at visible and infrared wavelengths. The key words spatial and optical define the scope of this discipline, distinguishing it from spatial interferometry at radio wavelengths, interferometry in the frequency domain applied to spectroscopy, or more general electro-optics theoretical and laboratory research. The main bibliography is a listing of all technical articles published in the international scientific literature and presented at the major international meetings and workshops attended by the spatial interferometry community. Section B summarizes publications dealing with the basic theoretical concepts and algorithms proposed and applied to optical spatial interferometry and imaging through a turbulent atmosphere. The section on experimental techniques is divided into twelve categories, representing the most clearly identified major areas of experimental research work. Section D, Observations, identifies publications dealing specifically with observations of astronomical sources, in which optical spatial interferometry techniques have been applied.

Gezari, Daniel Y.↗

Problems and issues for short-haul air transportation.

The problems of developing an efficient short-haul air system are not primarily technical, but economic and political. The key issues are whether the community will accept new and expanded air facilities, what standards of service the passengers will demand and how the system will evolve. The solutions recommended are national in scope and require the federal government to take a leading role.

Vittek, J. F., Jr.↗

Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for Work Breakdown Structure (WBS) and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements. The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. The guidance contained in this document is applicable to both in-house, NASA-led effort and contracted effort. It assists management teams from both entities in fulfilling necessary responsibilities for successful accomplishment of project cost, schedule, and technical goals. Benefits resulting from the use of an effective WBS include, but are not limited to: providing a basis for assigned project responsibilities, providing a basis for project schedule development, simplifying a project by dividing the total work scope into manageable units, and providing a common reference for all project communication.

Source record↗

A Comparison of Two Terminal Area Detect and Avoid Well Clear Definitions

Technical requirements are currently under development for a detect and avoid system (DAA) that would support the operation of Unmanned Aircraft Systems (UAS) within the National Airspace System (NAS). Such a system would aid UAS operators in maintaining sufficient separation, or "well clear", from other aircraft in their vicinity. The first set of technical standards for a UAS DAA system (referred to as "Phase 1" requirements) was limited to UAS operations transiting through Class D, E, and G airspace to, or from, Class A (or special-use) airspace. Explicitly out of scope of the Phase 1 requirements was the operation of UAS within terminal airspace in the NAS. Fern, Rorie, Roberts and Monk (2018) explored the application of a Phase 1 DAA system within Class D terminal airspace in a human-in-the-loop simulation. The results of the study demonstrated a poor fit of the Phase 1 DAA well clear (DWC) definition to these terminal operations. The original DWC definition was designed for the en-route environment and could not account for the complex, tightly-choreographed nature of traffic typically found near an airport. The interaction of the en-route DWC definition and the terminal area traffic led to excessive DAA alerting against safely-separated traffic. The frequent alerting quickly degraded pilots' ability to discriminate between encounters where a maneuver was or was not necessary. This resulted in slower response times, higher rates of losses of DAA well clear, and more severe losses of DAA well clear than had been observed in previous DAA research (e.g., Rorie et al., 2017). The current paper reports on a follow-on study to Fern et al. (2018) that tested two DWC definitions designed to accommodate standard terminal area operating procedures, such as traffic in the downwind leg of a VFR traffic pattern while the UAS is on final. The two definitions utilized identical horizontal and vertical thresholds but differed in whether or not Tau (a function that takes into account the closure rate of two aircraft) was included as a part of the DWC hazard zone. The "Tau" DWC candidate definition nominally extended the DWC hazard zone by 15 seconds in the direction of the intruder aircraft, while the "No Tau" DWC candidate definition did not extend the DWC hazard zone. The results of this follow-on study indicated that both candidate definitions improved pilot and DAA system performance relative to Fern et al (2018). Pilot response times and rates of losses of DWC returned to levels comparable to earlier research in the en-route environment. Several important differences between the two DWC candidate definitions, however, are also discussed.

Terminal Area↗