Bureau and agency reports
A summary of the work done by Geography and Human-Cultural Resources Work Group on EROS resources management program is given. Work covers archeological surveys, outdoor recreational planning, and engineering studies.
SEARCH · Engineering Papers
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.
A summary of the work done by Geography and Human-Cultural Resources Work Group on EROS resources management program is given. Work covers archeological surveys, outdoor recreational planning, and engineering studies.
The prospect of undertaking a reusable launch vehicle development led the NASA Office of Manned Space Flight (OMSF) to request the Office of Advanced Research and Technology (OART) to organize and direct a program to develop the technology that would aid in selecting the best system alternatives and that would support the ultimate development of an earth-to-orbit shuttle. Such a Space Transportation System Technology Program has been initiated. OART, OMSF, and NASA Flight and Research Centers with the considerable inputs of Department of Defense personnel have generated the program through the efforts of several Technology Working Groups and a Technology Steering Group. Funding and management of the recommended efforts is being accomplished through the normal OART and OMSF line management channels. The work is being done in government laboratories and under contract with industry and universities. Foreign nations have been invited to participate in this work as well. Substantial funding, from both OART and OMSF, was applied during the second half of fiscal year 1970. The Space Transportation System Technology Symposium held at the NASA Lewis Research Center, Cleveland, Ohio, July 15-17, 1970, was the first public report on that program. The Symposium goals were to consider the technology problems, their status, and the prospective program outlook for the benefit of the industry, government, university, and foreign participants considered to be contributors to the program. In addition, it offered an opportunity to identify the responsible individuals already engaged in the program. The Symposium sessions were intended to confront each presenter with his technical peers as listeners, and this, I believe, was substantially accomplished. Because of the high interest in the material presented, and also because the people who could edit the output are already deeply involved in other important tasks, we have elected to publish the material essentially as it was presented, utilizing mainly the illustrations used by the presenters along with brief words of explanation. Those who heard the presentations, and those who are technically astute in specialty areas, can probably put this story together again. We hope that more will be gained by compiling the information in this form now than by spending the time and effort to publish a more finished compendium later.
The prospect of undertaking a reusable launch vehicle development led the NASA Office of Manned Space Flight (OMSF) to request the Office of Advanced Research and Technology (OART) to organize and direct a program to develop the technology that would aid in selecting the best system alternatives and that would support the ultimate development of an earth-to-orbit shuttle. Such a Space Transportation System Technology Program has been initiated. OART, OMSF, and NASA Flight and Research Centers with the considerable inputs of Department of Defense personnel have generated the program through the efforts of several Technology Working Groups and a Technology Steering Group. Funding and management of the recommended efforts is being accomplished through the normal OAR T and OMSF line management channels. The work is being done in government laboratories and under contract with industry and universities. Foreign nations have been invited to participate in this work as well. Substantial funding, from both OART and OMSF, was applied during the second half of fiscal year 1970. The Space Transportation System Technology Symposium held at the NASA Lewis Research Center, Cleveland, Ohio, July 15-17, 1970, was the first public report on that program. The Symposium goals were to consider the technology problems, their status, and the prospective program outlook for the benefit of the industry, government, university, and foreign participants considered to be contributors to the program. In addition, it offered an opportunity to identify the responsible individuals already engaged in the program. The Symposium sessions were intended to confront each presenter with his technical peers as listeners, and this, I believe, was substantially accomplished. Because of the high interest in the material presented, and also because the people who could edit the output are already deeply involved in other important tasks, we have elected to publish the material essentially as it was presented, utilizing mainly the illustrations used by the presenters along with brief words of explanation. Those who heard the presentations, and those who are technically astute in specialty areas, can probably put this story together again. We hope that more will be gained by compiling the information in this form now than by spending the time and effort to publish a more finished compendium later.
The prospect of undertaking a reusable launch vehicle development led the NASA Office of Manned Space Flight (OMSF) to request the Office of Advanced Research and Technology (OART) to organize and direct a program to develop the technology that would aid in selecting the best system alternatives and that would support the ultimate development of an earth-to-orbit shuttle. Such a Space Transportation System Technology Program has been initiated. OART, OMSF, and NASA Flight and Research Centers with the considerable inputs of Department of Defense personnel have generated the program through the efforts of several Technology Working Groups and a Technology Steering Group. Funding and management of the recommended efforts is being accomplished through the normal OART and OMSF line management channels. The work is being done in government laboratories and under contract with industry and universities. Foreign nations have been invited to participate in this work as well. Substantial funding, from both OART and OMSF, was applied during the second half of fiscal year 1970. The Space Transportation System Technology Symposium held at the NASA Lewis Research Center, Cleveland, Ohio, July 15-17, 1970, was the first public report on that program. The Symposium goals were to consider the technology problems, their status, and the prospective program outlook for the benefit of the industry, government, university, and foreign participants considered to be contributors to the program. In addition, it offered an opportunity to identify the responsible individuals already engaged in the program. The Symposium sessions were intended to confront each presenter with his technical peers as listeners, and this, I believe, was substantially accomplished. Because of the high interest in the material presented, and also because the people who could edit the output are already deeply involved in other important tasks, we have elected to publish the material essentially as it was presented, utilizing mainly the illustrations used by the presenters along with brief words of explanation. Those who heard the presentations, and those who are technically astute in specialty areas, can probably put this story together again. We hope that more will be gained by compiling the information in this form now than by spending the time and effort to publish a more finished compendium later.
Data management areas were studied to identify pertinent problems and issues that will affect future NASA data users in terms of performance and cost. Specific topics discussed include the identifications of potential NASA data users other than those normally discussed, consideration affecting the clustering of minicomputers, low cost computer system for information retrieval and analysis, the testing of minicomputer based data base management systems, ongoing work related to the use of dedicated systems for data base management, and the problems of data interchange among a community of NASA data users.
The Urban Air Mobility (UAM) architecture is leveraged from the Unmanned Traffic Management (UTM) concept of operations. Within the UAM environment, UAM operators work collaboratively to manage aerial vehicles in the urban environment. Providers of Services for UAM (PSU), UAM operators, and Supplemental Data Service Providers (SDSP) provide services to support flight operations within that environment. As a recognized need, various views of UAM flight information are provided to the public and public safety entities. To accomplish this, among other goals, the Federal Aviation Administration (FAA) can coordinate flight information between the FAA controlled National Airspace System (NAS) and the UAM environments through the FAA-Industry Data Exchange Protocol (FIDXP). This concept of UAM proposes to develop short-range, point-to-point transportation systems in metropolitan areas using vertical take-off and landing (VTOL) or short take-off and landing (STOL) aircraft to overcome increasing surface congestion. To garner the support of UAM and to realize its potential, an assurance of cybersecurity is critical for public acceptance. Understanding the various components communicating with one-another cybersecurity, like in other industries, has come to the forefront highlighting the need to protect these networks and systems from cyberattacks. With the planned growth and reach of UAM systems, it’s clear that the associated data exchange and service interactions will be at risk due to numerous types of cybersecurity attacks. Consequently, as these threats evolve, the UAM cybersecurity capabilities must adapt to these changes as well. While learning is always the goal, the overall intent of this workshop is to make recommendations on the following: (1) how future UAM environments can be protected against cyber-attacks, and (2) what mechanisms should be put in place to detect attacks against UAM environments.
Approaches used to manage major projects are studied and the existing documents on NASA management are reviewed. The work consists of: (1) the project manager's role, (2) request for proposal, (3) project plan, (4) management information system, (5) project organizational thinking, (6) management disciplines, (7) important decisions, and (8) low cost approach.
A detailed Lunar Ultraviolet Telescope Experiment (LUTE) program plan representing major decisions and tasks leading to those decisions for program execution are presented. The purpose of this task was to develop an integrated plan of project activities for the LUTE project, and to display the plan as an integrated network that shows the project activities, all critical interfaces, and schedules. The integrated network will provide the project manager with a frame work for strategic planning and risk management throughout the life of the project.
Working group goals for this year are: Goal 1. Due to many review comments the green books will be updated and available for re-review by CCSDS. Submission of green books to CCSDS for approval. Goal 2.Initial set of 4 new drafts of the red books as following: SM&C protocol: update with received comments. SM&C common services: update with received comments and expand the service specification. SM&C core services: update with received comments and expand the service the information model. SM&C time services: (target objective): produce initial draft following template of core services.
The objectives of this program were to develop health monitoring systems and physics-based fault detection models for engine sub-systems including the start, lubrication, and fuel. These models will ultimately be used to provide more effective sub-system fault identification and isolation to reduce engine maintenance costs and engine down-time. Additionally, the bearing sub-system health is addressed in this program through identification of sensing requirements, a review of available technologies and a demonstration of a demonstration of a conceptual monitoring system for a differential roller bearing. This report is divided into four sections; one for each of the subtasks. The start system subtask is documented in section 2.0, the oil system is covered in section 3.0, bearing in section 4.0, and the fuel system is presented in section 5.0.
No abstract available
This document presents the design details of a granular activated carbon (GAC) hydraulic containment and groundwater treatment system Interim Measures Work Plan for the South Repeater Building site (South Repeater, Solid Waste Management Unit 121), located at John F. Kennedy Space Center (KSC), Florida. The interim measures (IM) treatment area includes the source area and downgradient property boundary, which have been impacted by per- and polyfluoroalkyl substances (PFAS). The objectives of the IM are to treat the source area and mitigate PFAS migration to areas outside of KSC boundaries. This document was prepared by AECOM Technical Services, Inc., for the National Aeronautics and Space Administration under Contract 80KSC019D0010, Task Order 80KSC021F0096. The IM consists of the installation and operation of 19 extraction wells and an associated groundwater treatment system. A total of 13 wells will be installed to a depth of 34 feet below land surface (bls) to target the upper medium-grained sand with shell layer. A total of six wells will be installed to a depth of 56 feet bls to target the lower layer of poorly graded sand with shell fragments. The system will be designed to operate each extraction well simultaneously using submersible pumps at flow rates of 5 or 10 gallons per minute (gpm), excluding one extraction well with a flow rate of 30 gpm. The extracted groundwater will be conveyed to a groundwater treatment system, where it will be treated via GAC prior to disposal via infiltration. To evaluate treatment system performance, baseline groundwater sampling will be conducted prior to treatment system startup. Performance monitoring will be completed quarterly for the first year. A total of eight performance monitoring wells will be installed to a depth of 12 feet bls, and eight performance monitoring wells will be installed to a depth of 30 feet bls. In addition to the installation of 16 performance monitoring wells, 12 existing monitoring wells will be incorporated into the performance monitoring program.
The mission planning processor is a user oriented tool for consumables management and is part of the total consumables subsystem management concept. The approach to be used in developing a working model of the mission planning processor is documented. The approach includes top-down design, structured programming techniques, and application of NASA approved software development standards. This development approach: (1) promotes cost effective software development, (2) enhances the quality and reliability of the working model, (3) encourages the sharing of the working model through a standard approach, and (4) promotes portability of the working model to other computer systems.
In the past five years, a number of automation applications for control of crew life support systems have been developed and evaluated in the Adjustable Autonomy Testbed at NASA's Johnson Space Center. This paper surveys progress on an adjustable autonomous control architecture for situations where software and human operators work together to manage anomalies and other system problems. When problems occur, the level of control autonomy can be adjusted, so that operators and software agents can work together on diagnosis and recovery. In 1997 adjustable autonomy software was developed to manage gas transfer and storage in a closed life support test. Four crewmembers lived and worked in a chamber for 91 days, with both air and water recycling. CO2 was converted to O2 by gas processing systems and wheat crops. With the automation software, significantly fewer hours were spent monitoring operations. System-level validation testing of the software by interactive hybrid simulation revealed problems both in software requirements and implementation. Since that time, we have been developing multi-agent approaches for automation software and human operators, to cooperatively control systems and manage problems. Each new capability has been tested and demonstrated in realistic dynamic anomaly scenarios, using the hybrid simulation tool.
Increasing turbine up-time and reducing maintenance costs are key technology drivers for wind turbine operators. Components within wind turbines are subject to considerable stresses due to unpredictable environmental conditions resulting from rapidly changing local dynamics. Systems health management has the aim to assess the state-of-health of components within a wind turbine, to estimate remaining life, and to aid in autonomous decision-making to minimize damage. Advanced adaptive controls can provide the mechanism to enable optimized operations that also provide the enabling technology for Systems Health Management goals. The work reported herein explores the integration of condition monitoring of wind turbine blades with contingency management and adaptive controls. Results are demonstrated using a high fidelity simulator of a utility-scale wind turbine.
This paper describes recent work on developing an extensible information grid for risk management at NASA - a RISK INFORMATION GRID. This grid is being developed by integrating information grid technology with risk management processes for a variety of risk related applications. To date, RISK GRID applications are being developed for three main NASA processes: risk management - a closed-loop iterative process for explicit risk management, program/project management - a proactive process that includes risk management, and mishap management - a feedback loop for learning from historical risks that escaped other processes. This is enabled through an architecture involving an extensible database, structuring information with XML, schemaless mapping of XML, and secure server-mediated communication using standard protocols.
This work plan serves as the design to remove soil with concentrations of copper and barium above Florida Department of Environmental Protection Residential Soil Cleanup Target Levels in the vicinity where radar station refurbishment activities were conducted.
During a series of network management retreats in June and July 1990, representatives from NASA Headquarters Codes O and S agreed on networking roles and responsibilities for their respective organizations. The representatives decided that NASA Science Internet (NSI) will assume management of both the Space Physics Analysis Network (SPAN) and the NASA Science Network (NSN). SPAN is now known as the NSI/DECnet, and NSN is now known as the NSI/IP. Some management functions will be distributed between Ames Research Center (ARC) and Goddard Space Flight Center (GSFC). NSI at ARC has the lead role for requirements generation and networking engineering. Advanced Applications and the Network Information Center is being developed at GSFC. GSFC will lead the NSI User Services, but NSI at Ames will continue to provide the User Services during the transition. The transition will be made as transparent as possible for the users. DECnet service will continue, but is now directly managed by NSI at Ames. NSI will continue to work closely with routing center managers at other NASA centers, and has formed a transition team to address the change in management. An NSI/DECnet working group had also been formed as a separate engineering group within NSI to plan the transition to Phase 5, DECnet's approach to Open System Integration (OSI). Transition is not expected for a year or more due to delays in produce releases. Plans to upgrade speeds in tail circuits and the backbone are underway. The proposed baseline service for new connections is up to 56 Kbps; 9.6 Kbps lines will gradually be upgraded as requirements dictate. NSI is in the process of consolidating protocol traffic, tail circuits, and the backbone. Currently NSI's backbone is fractional T1; NSI will go to full T1 service as soon as it is feasible.