Search NASA⌕ Search

SEARCH · Search NASA

Results for “Administration and Management”

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 343 records · Page 19
All sourcesNASA NTRSDOE OSTI
NASA NTRS1996

Nutrient management effects on sweetpotato genotypes under controlled environment

Sweetpotato is one of several crops recommended by National Aeronautics and Space Administration (NASA) for bioregenerative life support studies. One of the objectives of the Tuskegee University NASA Center is to optimize growth conditions for adaptability of sweetpotatoes for closed bioregenerative systems. The role of nutrient solution management as it impacts yield has been one of the major thrusts in these studies. Nutrient solution management protocol currently used consists of a modified half Hoagland solution that is changed at 14-day intervals. Reservoirs are refilled with deionized water if the volume of the nutrient solution was reduced to 8 liters or less before the time of solution change. There is the need to recycle and replenish nutrient solution during crop growth, rather than discard at 14 day intervals as previously done, in order to reduce waste. Experiments were conducted in an environmental growth room to examine the effects of container size on the growth of several sweetpotato genotypes grown under a nutrient replenishment protocol. Plants were grown from vine cuttings of 15cm length and were planted in 0.15 x 0.15 x 1.2m growth channels using a closed nutrient film technique system. Nutrient was supplied in a modified half strength Hoagland's solution with a 1:2.4 N:K ratio. Nutrient replenishment protocol consisted of daily water replenishment to a constant volume of 30.4 liters in the small containers and 273.6 liters in the large container. Nutrients were replenished as needed when the EC of the nutrient solution fell below 1200 mhos/cm. The experimental design used was a split-plot with the main plot being container size and genotypes as the subplot. Nine sweetpotato genotypes were evaluated. Results showed no effect of nutrient solution container size on storage root yield, foliage fresh and dry mass, leaf area or vine length. However, plants grown using the large nutrient solution container accumulated more storage root dry mass than those with the small containers. Although plants grown with the smaller containers showed greater water uptake, plant nutrient uptake was lower than with the larger container. All genotypes evaluated showed variation in their responses to all parameters measured.

Solanaceae/genetics/growth & development↗
NASA NTRS2005

Thermal Assessment of Swift BAT Instrument Thermal Control System in Flight

THE BAT is the primary instrument on the Swift spacecraft. The Swift mission is part of the National Aeronautics and Space Administration (NASA) Medium-Size Explorer (MIDEX) Program, and is managed by Goddard Space Flight Center (GSFC). It is designed to detect gamma ray burst over a broad region of the sky in a low Earth orbit of 600-km altitude and quickly align the telescopes on the spacecraft to the gamma ray source. It was successfully launched into orbit on November 20, 2004. The Swift mission is a first of its kind of multi-wavelength transient observatory for gamma ray burst astronomy. Its mission life is 2 years. The inclination is 22 deg maximum. The spacecraft bus voltage to the instruments is in the 24 V to 35 V range. The instruments will be turned off when the voltage is below 27 V. The BAT is mounted to the optical bench through five titanium flexures. The BAT has been developed at GSFC. Its telescope assembly consists of 256 Detector Modules (DMs) in the Detector Array. There are 16 Detector Array Blocks. Each Block holds 16 DMs, 3 Block Voltage Regulator (BVR) units and 3 Block Command & Data Handling (BCDH) units. The power dissipation of each Block has been measured to be 13 W. Therefore the total power dissipation of the 16 Blocks is 208 W. The DAP is 1.3 m (4.3 ft) x 1 m (3.3 ft), accommodates all the 16 Blocks. It also provides the mounting surface and the positional stability for the Blocks. The DMs are located at the top (+X side) of the DAP and is enclosed by graded-Z shields on the sides and a coded mask at the top. The BVRs and BCDHs are located at the bottom (-X side) of the DAP. Eight Blocks are located at the front (-Z side or radiator side) of the DAP, and eight are located at the rear (+Z side) of the DAP. The DMs and top of DAP are insulated with a 7-layer multi-layer insulation (MLI). There is a 5.08 cm (2 in) x 5.08 cm (2 in) MLI cutout over each Block heater controller so that heat radiates from the heater controller to the mask. The exterior of the mask, graded-Z shields and bottom of DAP is insulated with a 15-layer MLI.

Choi, Michael K.↗
NASA NTRS2005

STS-114: Discovery Launch Postponement Press Briefing

This press briefing addresses the problem that occurred prior to the launch of the STS-114. Dean Acosta, Deputy Assistant Administrator of Public Affairs, introduces the panel which consists of Dr. Michael Griffin, NASA Administrator, William Readdy, Associate Administrator for Space Operations, Wayne Hale, Space Shuttle Program Deputy Manager, Steve Poulas, Orbiter Project Manager, Mike Leinbach, NASA Launch Director, and Bill Parsons, Space Shuttle Program Manager. Wayne Hale expresses that a problem occurred with one of the low level sensors in the hydrogen tank and that the cause of the problem must be identified and rectified. Steve Poulos talks about establishing a troubleshooting plan as a part of the scrub effort and Mike Leinbach describes the process of draining the external tank. Wayne Hale answers questions about the sensors and if the Space Shuttle Discovery is safe to fly and Steve Poulos answers questions about the possible suspects for this problem.

Source record↗
NASA NTRS2008

Development and Application of an Integrated Approach toward NASA Airspace Systems Research

The National Aeronautics and Space Administration's (NASA) Airspace Systems Program is contributing air traffic management research in support of the 2025 Next Generation Air Transportation System (NextGen). Contributions support research and development needs provided by the interagency Joint Planning and Development Office (JPDO). These needs generally call for integrated technical solutions that improve system-level performance and work effectively across multiple domains and planning time horizons. In response, the Airspace Systems Program is pursuing an integrated research approach and has adapted systems engineering best practices for application in a research environment. Systems engineering methods aim to enable researchers to methodically compare different technical approaches, consider system-level performance, and develop compatible solutions. Systems engineering activities are performed iteratively as the research matures. Products of this approach include a demand and needs analysis, system-level descriptions focusing on NASA research contributions, system assessment and design studies, and common systemlevel metrics, scenarios, and assumptions. Results from the first systems engineering iteration include a preliminary demand and needs analysis; a functional modeling tool; and initial system-level metrics, scenario characteristics, and assumptions. Demand and needs analysis results suggest that several advanced concepts can mitigate demand/capacity imbalances for NextGen, but fall short of enabling three-times current-day capacity at the nation s busiest airports and airspace. Current activities are focusing on standardizing metrics, scenarios, and assumptions, conducting system-level performance assessments of integrated research solutions, and exploring key system design interfaces.

Barhydt, Richard↗
NASA NTRS2015

Commercial Orbital Transportation Services (COTS) Program Lessons Learned

This report has been developed by the National Aeronautics and Space Administration (NASA) Human Exploration and Operations Mission Directorate (HEOMD) Risk Management team in close coordination with the COTS Program. This document provides a point-in-time, cumulative, summary of actionable key lessons learned derived from the design project. Lessons learned invariably address challenges and risks and the way in which these areas have been addressed. Accordingly the risk management thread is woven throughout the document.

COTS↗
NASA NTRS2011

Ares Knowledge Capture: Summary and Key Themes Presentation

This report has been developed by the National Aeronautics and Space Administration (NASA) Human Exploration and Operations Mission Directorate (HEOMD) Risk Management team in close coordination with the MSFC Chief Engineers Office. This document provides a point-in-time, cumulative, summary of actionable key lessons learned derived from the design project. Lessons learned invariably address challenges and risks and the way in which these areas have been addressed. Accordingly the risk management thread is woven throughout the document.

Ares Knowledge↗
NASA NTRS2013

Systems Engineering Lessons Learned from Solar Array Structures and Mechanisms Deployment

This report has been developed by the National Aeronautics and Space Administration (NASA) Human Exploration and Operations Mission Directorate (HEOMD) Risk Management team in close coordination with the Engineering Directorate at LaRC. This document provides a point-in-time, cumulative, summary of actionable key lessons learned derived from the design project. Lessons learned invariably address challenges and risks and the way in which these areas have been addressed. Accordingly the risk management thread is woven throughout the document.

Solar Array Structures↗
NASA NTRS2012

NASA System Safety Framework and Concepts for Implementation

This report has been developed by the National Aeronautics and Space Administration (NASA) Human Exploration and Operations Mission Directorate (HEOMD) Risk Management team knowledge capture forums.. This document provides a point-in-time, cumulative, summary of actionable key lessons learned in safety framework and concepts.

System Safety↗
NASA NTRS2011

TPSAS-NF1676L-12168-DND

The Federal Aviation Administration’s Surveillance and Broadcast Services Program Office considers Interval Management (IM) to be one of the three key, near-term applications to make use of ADS-B-In, the receiving and processing of Automatic Dependent Surveillance – Broadcast data on-board an aircraft. Interval Management is used to describe a wide range of operational applications and uses of airborne spacing technology. Interval Management makes use of improved scheduling and sequencing capabilities for the air traffic controllers (ATC) and precise, relative spacing of aircraft, to improve airport throughput, increase the use of Optimized Profile Descents (OPD), and reduce tactical controller workload. The IM applications are subdivided into two categories: one where the flight crew is authorized to manage their speed to achieve the IM goal while the controller retains separation responsibility and a second where the flight crew takes responsibility for both managing speed but also for separation from the specified target aircraft. The former is referred to as Interval Management-Spacing (IM-S) and the latter as Interval Management-Delegated Separation (IM-DS). For the past 10 years NASA has been working on a specific IM application called Airborne Precision Spacing (APS). This concept has focused on increasing runway throughput while enabling OPDs. It is seen as a specific application within the IM class of applications. This talk will present the current state of the APS concept including support for dependent parallel runway operations and how NASA is working to have APS support the broader IM activities. Planned development and testing of APS, including extensions to support IM-DS and FAA-planned flight trials will be presented along with several up-coming simulations.

Bryan E Barmore↗
NASA NTRS2011

TPSAS-NF1676L-12329-DND

The Federal Aviation Administration’s Surveillance and Broadcast Services Program Office considers Interval Management (IM) to be one of the three key, near-term applications to make use of ADS-B-In, the receiving and processing of Automatic Dependent Surveillance – Broadcast data on-board an aircraft. Interval Management is used to describe a wide range of operational applications and uses of airborne spacing technology. Interval Management makes use of improved scheduling and sequencing capabilities for the air traffic controllers (ATC) and precise, relative spacing of aircraft, to improve airport throughput, increase the use of Optimized Profile Descents (OPD), and reduce tactical controller workload. The IM applications are subdivided into two categories: one where the flight crew is authorized to manage their speed to achieve the IM goal while the controller retains separation responsibility and a second where the flight crew takes responsibility for both managing speed but also for separation from the specified target aircraft. The former is referred to as Interval Management-Spacing (IM-S) and the latter as Interval Management-Delegated Separation (IM-DS). For the past 10 years NASA has been working on a specific IM application called Airborne Precision Spacing (APS). This concept has focused on increasing runway throughput while enabling OPDs. It is seen as a specific application within the IM class of applications. This talk will present the current state of the APS concept including support for dependent parallel runway operations and how NASA is working to have APS support the broader IM activities. Planned development and testing of APS, including extensions to support IM-DS and FAA-planned flight trials will be presented along with several up-coming simulations.

Brian T Baxley↗
NASA NTRS2023

SUBSLAB SOIL GAS SAMPLING PLAN FOR COMMUNICATION, MAINTENANCE, AND STORAGE, SOLID WASTE MANAGEMENT UNIT (SWMU) 082

HydroGeoLogic, Inc. (HGL) prepared this Subslab Soil Gas (SSSG) Sampling Plan for Communications, Maintenance, and Storage (CM&S), Solid Waste Management Unit (SWMU) 082 for the National Aeronautics and Space Administration (NASA), Kennedy Space Center (KSC), Florida, under Contract Number 80KSC019D0012, Task Order 80KSC021F0097 technical directive #1, awarded on September 26, 2022. As described herein, all SSSG sampling and evaluations will be completed in accordance with U.S. Environmental Protection Agency’s (EPA), OSWER Technical Guide for Assessing and Mitigating the Vapor Intrusion Pathway from Subsurface Vapor Sources to Indoor Air (EPA, 2015).

Jason J Bublitz↗
NASA NTRS2018

Air Traffic Management-eXploration Testbed for Urban Air Mobility Research and Development

The presentation will describe the architecture, current capabilities and some future enhancements of the testbed that is being developed at the National Aeronautics and Space Administration (NASA) to enable benefit, impact, safety and cost assessments for accelerating the deployment of air traffic management concept and technologies in the national airspace system. The testbed will support analysis of operational feasibility of urban air mobility operations, a part of NASA's Air Traffic Management eXploration project, and provide the data needed by regulatory agencies charged with public safety. Introduction of concepts and technologies, especially new concepts and technologies, is difficult and often takes decades because of the inability to assess the operational impact of the interaction between the proposed concept and technology and operationally deployed systems in terms of system-wide safety, traffic flow efficiency, roles and workload of controllers and traffic managers, and impact on airlines and other operators. To overcome these limitations, the testbed is developing infrastructure to enable mathematical modeling, human-in-the-loop evaluations and testing with operational systems in a simulated environment. In addition to the difficulty of establishing communications between geographically distributed systems, downloading/installing software, and management of startup, error-handling and shutdown, a major impediment for conducting simulations and human-in-the-loop testing with operational systems is the tedious manual scenario generation process. Several of these difficulties have been addressed in the current state of the testbed. The testbed can be described in terms of the following elements (1) web-based frontend and backend, (2) Testbed Builder, (3) Data Distribution Service, (4) Component Library, (5) Simulation Management, and (6) Scenario Generation. The web-based frontend and backend enable the user to interact with the testbed for tasks such as composing a simulation, running a simulation and retrieving output data. The Testbed Builder application launched from the web frontend is a graphical user interface for the user to drag-and-drop and connect predefined blocks for composing a simulation/scenario generation task. The Builder writes a set of instructions for Simulation Management based on the links between the blocks and the block properties such as the component (executable) associated with a particular block. Management of the distributed simulation is accomplished by Execution and Component Managers. Execution Manager interprets the instructions provided by the Builder to instruct the Component Managers to download components from the Component Library to specified computers and to start them up. Once started, the components communicate with each other by publishing messages and subscribing to messages that are delivered by the Data Distribution Service. The Scenario Generation capability can be used for creating traffic scenarios for Multi-Aircraft Control System, which has been used extensively at NASA for human-in-the-loop-based concept evaluations. The presentation will provide a testbed enabled example scenario of Multi-Aircraft Control System based simulation in which the urban air mobility pilot using the conflict detection and resolution system would interact with the air traffic controllers for resolving conflicts with other aircraft during terminal area operations.

Testbed↗
NASA NTRS2018

Air Traffic Management-eXploration Testbed for Urban Air Mobility Research and Development

The presentation will describe the architecture, current capabilities and some future enhancements of the testbed that is being developed at the National Aeronautics and Space Administration (NASA) to enable benefit, impact, safety and cost assessments for accelerating the deployment of air traffic management concept and technologies in the national airspace system. The testbed will support analysis of operational feasibility of urban air mobility operations, a part of NASA's Air Traffic Management eXploration project, and provide the data needed by regulatory agencies charged with public safety. Introduction of concepts and technologies, especially new concepts and technologies, is difficult and often takes decades because of the inability to assess the operational impact of the interaction between the proposed concept and technology and operationally deployed systems in terms of system-wide safety, traffic flow efficiency, roles and workload of controllers and traffic managers, and impact on airlines and other operators. To overcome these limitations, the testbed is developing infrastructure to enable mathematical modeling, human-in-the-loop evaluations and testing with operational systems in a simulated environment. In addition to the difficulty of establishing communications between geographically distributed systems, downloading/installing software, and management of startup, error-handling and shutdown, a major impediment for conducting simulations and human-in-the-loop testing with operational systems is the tedious manual scenario generation process. Several of these difficulties have been addressed in the current state of the testbed. The testbed can be described in terms of the following elements- (1) web-based frontend and backend, (2) Testbed Builder, (3) Data Distribution Service, (4) Component Library, (5) Simulation Management, and (6) Scenario Generation. The web-based frontend and backend enable the user to interact with the testbed for tasks such as composing a simulation, running a simulation and retrieving output data. The Testbed Builder application launched from the web frontend is a graphical user interface for the user to drag-and-drop and connect predefined blocks for composing a simulation/scenario generation task. The Builder writes a set of instructions for Simulation Management based on the links between the blocks and the block properties such as the component (executable) associated with a particular block. Management of the distributed simulation is accomplished by Execution and Component Managers. Execution Manager interprets the instructions provided by the Builder to instruct the Component Managers to download components from the Component Library to specified computers and to start them up. Once started, the components communicate with each other by publishing messages and subscribing to messages that are delivered by the Data Distribution Service. The Scenario Generation capability can be used for creating traffic scenarios for Multi-Aircraft Control System, which has been used extensively at NASA for human-in-the-loop-based concept evaluations. The presentation will provide a testbed enabled example scenario of Multi-Aircraft Control System based simulation in which the urban air mobility pilot using the conflict detection and resolution system would interact with the air traffic controllers for resolving conflicts with other aircraft during terminal area operations.

Simulation↗
NASA NTRS2018

Systems Development, Data Mining, and Knowledge Discovery

The primary role of the Technical Integration Office is to provide technical solutions and services to different branches at KSC (Kennedy Space Center) and NASA program customers. The Technical Integration Office helps support KSC's operational needs by providing services such as digital connectivity, data center services, modelling and simulation tools, and communication video services. To learn the necessary technology and processes for my internship, I am working on two projects: learning C# (C Sharp programming language) with SQL and developing requirements for a PX (Communication and Public Engagement) inventory management system. To learn how to efficiently program with C#, my mentor assigned me to complete a sports informatics application that would let users discover facts and rules about various sports. The sports informatics application comes with search capabilities, report generating features, rule lists that users can modify, and diagrams for various sport strategies. To further build upon this project, I also developed a sport simulation game with the application. Once I begin more SQL-based projects, I will have the opportunity to learn how to manage databases and link SQL servers with C# programs. To develop requirements for the inventory management system, I have met with PX representatives and toured their storage facilities to see how they organize and store their items and equipment. I will also be meeting with representatives from the budget office to find out what information must be in a system budget report. The main components the system must have are customer request management, a search feature for items and equipment, report generation capabilities, and automated system warnings when item quantities reach or go below administrator-specified threshold levels. I have drafted questions and shall statements that will ultimately become part of the inventory management system requirements document.

Espinosa, Gabriel↗
NASA NTRS2006

Education and Training Module in Alertness Management

The education and training module (ETM) in alertness management has now been integrated as part of the training regimen of the Pilot Proficiency Awards Program ("WINGS") of the Federal Aviation Administration. Originated and now maintained current by the Fatigue Countermeasures Group at NASA Ames Research Center, the ETM in Alertness Management is designed to give pilots the benefit of the best and most recent research on the basics of sleep physiology, the causes of fatigue, and strategies for managing alertness during flight operations. The WINGS program is an incentive program that encourages pilots at all licensing levels to participate in recurrent training, upon completion of which distinctive lapel or tie pins (wings) and certificates of completion are awarded. In addition to flight training, all WINGS applicants must attend at least one FAA-sponsored safety seminar, FAA-sanctioned safety seminar, or industry recurrent training program. The Fatigue Countermeasures Group provides an FAA-approved industry recurrent training program through an on-line General Aviation (GA) WINGS ETM in alertness management to satisfy this requirement. Since 1993, the Fatigue Countermeasures Group has translated fatigue and alertness information to operational environments by conducting two-day ETM workshops oriented primarily toward air-carrier operations subject to Part 121 of the Federal Aviation Regulations pertaining to such operations. On the basis of the information presented in the two-day ETM workshops, an ETM was created for GA pilots and was transferred to a Web-based version. To comply with the requirements of the WINGS Program, the original Web-based version has been modified to include hypertext markup language (HTML) content that makes information easily accessible, in-depth testing of alertness-management knowledge, new interactive features, and increased informational resources for GA pilots. Upon successful completion of this training module, a participant receives a computer- screen display of a certificate of completion. The certificate, which includes the pilot s name and an identifying number, can be printed out and submitted, for ground training credit, with the pilot s WINGS application.

Mallis, M. M.↗
NASA NTRS1983

Guidelines for development of NASA (National Aeronautics and Space Administration) computer security training programs

The report presents guidance for the NASA Computer Security Program Manager and the NASA Center Computer Security Officials as they develop training requirements and implement computer security training programs. NASA audiences are categorized based on the computer security knowledge required to accomplish identified job functions. Training requirements, in terms of training subject areas, are presented for both computer security program management personnel and computer resource providers and users. Sources of computer security training are identified.

Tompkins, F. G.↗