Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 487 records · Page 27

AmeriFlux CA-GL4 Nine Mile Lighthouse

This is the AmeriFlux version of the carbon flux data for the site CA-GL4 Nine Mile Lighthouse. Site Description - Nine Mile Lighthouse is located at the south end of Simcoe Island on Lake Ontario. The eddy covariance instrumentation is located on the historic lighthouse, built in 1833, and instrumented with eddy covariance data in 2016 by a network of scientists from both US and Canada (eventually to be called the Great Lakes Evaporation Network (GLEN)). The intent of GLEN has been to provide observations of over-lake meteorology and evaporation, improve forecasting of Great Lakes water levels, and support a wide variety of stakeholders, including the National Weather Service (NWS), Environment and Climate Change Canada, National Oceanic and Atmospheric Administration, U.S. Coast Guard, recreational boaters and commercial shipping, emergency management officials, and the Great Lakes research community.

Spence, Chris [Environment and Climate Change Cana↗

HarDWR - Harmonized Water Rights Records

A dataset within the Harmonized Database of Western U.S. Water Rights (HarDWR). For a detailed description of the database, please see the meta-record v2.0. Changelog v2.0 - Recalculated based on data sourced from WestDAAT - Changed using a Site ID column to identify unique records to using aa combination of Site ID and Allocation ID - Removed the Water Management Area (WMA) column from the harmonized records. The replacement is a separate file which stores the relationship between allocations and WMAs. This allows for allocations to contribute to water right amounts to multiple WMAs during the subsequent cumulative process. - Added a column describing a water rights legal status - Added "Unspecified" was a water source category - Added an acre-foot (AF) column - Added a column for the classification of the right's owner v1.02 - Added a .RData file to the dataset as a convenience for anyone exploring our code. This is an internal file, and the one referenced in analysis scripts as the data objects are already in R data objects. v1.01 - Updated the names of each file with an ID number less than 3 digits to include leading 0s v1.0 - Initial public release Description Here we present an updated database of Western U.S. water right records. This database provides consistent unique identifiers for each water right record, and a consistent categorization scheme that puts each water right record into one of seven broad use categories. These data were instrumental in conducting a study of the multi-sector dynamics of inter-sectoral water allocation changes though water markets (Grogan et al., *in review*). Specifically, the data were formatted for use as input to a process-based hydrologic model, Water Balance Model (WBM), with a water rights module (Grogan et al., *in review*). While this specific study motivated the development of the database presented here, water management in the U.S. West is a rich area of study (e.g., Anderson and Woosly, 2005; Tidwell, 2014; Null and Prudencio, 2016; Carney et al., 2021) so releasing this database publicly with documentation and usage notes will enable other researchers to do further work on water management in the U.S. West. We produced the water rights database presented here in four main steps: (1) data collection, (2) data quality control, (3) data harmonization, and (4) generation of cumulative water rights curves. Each of steps (1)-(3) had to be completed in order to produce (4), the final product that was used in the modeling exercise in Grogan et al. (*in review*). All data in each step is associated with a spatial unit called a Water Management Area (WMA), which is the unit of water right administration utilized by the state in which the right came from. Steps (2) and (3) required use to make assumptions and interpretation, and to remove records from the raw data collection. We describe each of these assumptions and interpretations below so that other researchers can choose to implement alternative assumptions an interpretation as fits their research aims. Motivation for Changing Data Sources The most significant change has been a switch from collecting the raw water rights directly from each state to using the water rights records presented in WestDAAT, a product of the Water Data Exchange (WaDE) Program under the Western States Water Council (WSWC). One of the main reasons for this is that each state of interest is a member of the WSWC, meaning that WaDE is partially funded by these states, as well as many universities. As WestDAAT is also a database with consistent categorization, it has allowed us to spend less time on data collection and quality control and more time on answering research questions. This has included records from water right sources we had previously not known about when creating v1.0 of this database. The only major downside to utilizing the WestDAAT records as our raw data is that further updates are tied to when WestDAAT is updated, as some states update their public water right records daily. However, as our focus is on cumulative water amounts at the regional scale, it is unlikely most records updates would have a significant effect on our results. The structure of WestDAAT led to several important changes to how HarWR is formatted. The most significant change is that WaDE has calculated a field known as `SiteUUID`, which is a unique identifier for the Point of Diversion (POD), or where the water is drawn from. This separate from `AllocationNativeID`, which is the identifier for the allocation of water, or the amount of water associated with the water right. It should be noted that it is possible for a single site to have multiple allocations associated with it and for an allocation to be able to be extracted from multiple sites. The site-allocation structure has allowed us to adapt a more consistent, and hopefully more realistic, approach in organizing the water right records than we had with HarDWR v1.0. This was incredibly helpful as the raw data from many states had multiple water uses within a single field within a single row of their raw data, and it was not always clear if the first water use was the most important, or simply first alphabetically. WestDAAT has already addressed this data quality issue. Furthermore, with v1.0, when there were multiple records with the same water right ID, we selected the largest volume or flow amount and disregarded the rest. As WestDAAT was already a common structure for disparate data formats, we were better able to identify sites with multiple allocations and, perhaps more importantly, allocations with multiple sites. This is particularly helpful when an allocation has sites which cross WMA boundaries, instead of just assigning the full water amount to a single WMA we are now able to divide the amount of water between the number of relevant WMAs. As it is now possible to identify allocations with water used in multiple WMAs, it is no longer practical to store this information within a single column. Instead the stAllocationToWMATab.csv file was created, which is an allocation by WMA matrix containing the percent Place of Use area overlap with each WMA. We then use this percentage to divide the allocation's flow amount between the given WMAs during the cumulation process to hopefully provide more realistic totals of water use in each area. However, not every state provides areas of water use, so like HarDWR v1.0, a hierarchical decision tree was used to assign each allocation to a WMA. First, if a WMA could be identified based on the allocation ID, then that WMA was used; typically, when available, this applied to the entire state and no further steps were needed. Second was the spatial analysis of Place of Use to WMAs. Third was a spatial analysis of the POD locations to WMAs, with the assumption that allocation's POD is within the WMA it should belong to; if an allocation still had multiple WMAs based on its POD locations, then the allocation's flow amount would be divided equally between all WMAs. The fourth, and final, process was to include water allocations which spatially fell outside of the state WMA boundaries. This could be due to several reasons, such as coordinate errors / imprecision in the POD location, imprecision in the WMA boundaries, or rights attached with features, such as a reservoir, which crosses state boundaries. To include these records, we decided for any POD which was within one kilometer of the state's edge would be assigned to the nearest WMA. Other Changes WestDAAT has Allowed In addition to a more nuanced and consistent method of assigning water right's data to WMAs, there are other benefits gained from using the WestDAAT dataset. Among those is a consistent categorization of a water right's legal status. In HarDWR v1.0, legal status was effectively ignored, which led to many valid concerns about the quality of the database related to the amounts of water the rights allowed to be claimed. The main issue was that rights with legal status' such as "application withdrawn", "non-active", or "cancelled" were included within HarDWR v1.0. These, and other water rights status' which were deemed to not be in use have been removed from this version of the database. Another major change has been the addition of the "unspecified water source category. This is water that can come from either surface water or groundwater, or the source of which is unknown. The addition of this source category brings the total number of categories to three. Due to reviewer feedback, we decided to add the acre-foot (AF) column so that the data may be more applicable to a wider audience. We added the ownerClassification column so that the data may be more applicable to a wider audience. File Descriptions The dataset is a series of various files organized by state sub-directories. In addition, each file begins with the state's name, in case the file is separate from its sub-directory for some reason. After the state name is the text which describes the contents of the file. Here is each file described in detail. Note that st is a placeholder for the state's name. stFullRecords_HarmonizedRights.csv: A file of the complete water records for each state. The column headers for each of this type of file are: state - The name of the state to which the allocations belong to. FIPS - The two digit numeric state ID code. siteID - The site location ID for POD locations. A site may have multiple allocations, which are the actual amount of water which can be drawn. In a simplified hypothetical, a farm stead may have an allocation for "irrigation" and an allocation for "domestic" water use, but the water is drawn from the same pumping equipment. It should be noted that many of the site ID appear to have been added by WaDE, and therefore may not be recognized by a given state's water rights database. allocationID - The allocation ID for the water right. For most states this is the water right ID, and what is recommended to use should a right be looked up on a given state's water rights database. The water amounts associated with these IDs tend to be finer scaled than those associated with siteID. It should be noted that some allocations may be extracted from multiple sites, particularly for larger Places of Use. ownerClassification - A classification of the types of owners for water rights. The most common is `Private` which incorporates a wide range of entities. Several classifications would be grouped into a government category, most of which are for the U.S. Federal Government. These allocations could be listed as "Federal", "United States of America", or as the names of any number of federal agencies. The last major grouping of entities is for "Native American"s. priorityDate - The date we use as the water right priority date for our modeling analysis. This is the legal priority date when it is available. However, for some rights, specifically from California and New Mexico, we used a pseudo priority date (e.g. well completion date or start of well drilling date) when a legal priority date was not available. The most questionable dates come from New Mexico, where the only date associated with certain water right records was the date the allocation was recorded in the database. As the allocation record creation tended to be within a few months of the filing of the application of the water right, from manually double checking the water rights, and our analysis focuses on aggregating water rights on the timescale of years, we determined it was acceptable to use such dates to include as many records as possible. primaryBeneficialUse - From the numerous state water use categories, WaDE categorized them into 21 categories WestDAAT. This column is the original WaDE category for the primary water use at the PoD site. allocationBeneficialUse - From the numerous state water use categories, WaDE categorized them into 21 categories for WestDAAT. This column is the original WaDE category

Economics↗

Development of the propulsion subsystem for the Viking 75 Orbiter

The development of the Viking 75 Orbiter propulsion subsystem has been completed and qualification is under way. This development required an extension of the Mariner Mars 1971 propulsion subsystem technology to meet the Viking 75 requirements of three times the burn time and five times the number of burns. Modifications have been incorporated into the rocket engine to increase the cooling margin for the 2700-second Mars orbit insertion burn. This capability has been demonstrated in both engine firings and subsystem tests. A new surface tension device has been developed to position the propellants (N2O4 and MMH) over the tank outlets during zero-g flight. Extensive scale model testing has been conducted to prove this propellant management concept. This subsystem will provide midcourse corrections, an orbit insertion burn and 20 orbit trims for the Viking 75 Spacecraft. The Viking Project is managed by the Langley Research Center, National Aeronautics and Space Administration.

Vote, F. C.↗

The database management system: A topic and a tool

Data structures and data base management systems are common tools employed to deal with the administrative information of a university. An understanding of these topics is needed by a much wider audience, ranging from those interested in computer aided design and manufacturing to those using microcomputers. These tools are becoming increasingly valuable to academic programs as they develop comprehensive computer support systems. The wide use of these tools relies upon the relational data model as a foundation. Experience with the use of the IPAD RIM5.0 program is described.

Plummer, O. R.↗

Space Resources Development: The Link Between Human Exploration and the Long-Term Commercialization of Space

In a letter to the NASA Administrator, Dan Goldin, in January of 1999, the Office of Management and Budget (OMB) stated the following . OMB recommends that NASA consider commercialization in a broader context than the more focused efforts to date on space station and space shuttle commercialization. We suggest that NASA examine architectures that take advantage of a potentially robust future commercial infrastructure that could dramatically lower the cost of future human exploration." In response to this letter, the NASA Human Exploration and Development of Space (HEDS) Enterprise launched the BEDS Technology & Commercialization Initiative (HTCI) to link technology and system development for human exploration with the commercial development of space to emphasize the "D" (Development) in BEDS. The development of technologies and capabilities to utilize space resources is the first of six primary focus areas in this program. It is clear that Space Resources Development (SRD) is key for both long-term human exploration of our solar system and to the long-term commercialization of space since: a) it provides the technologies, products, and raw materials to support efficient space transportation and in-space construction and manufacturing, and b) it provides the capabilities and infrastructure to allow outpost growth, self-sufficiency, and commercial space service and utility industry activities.

Sanders, Gerald B.↗

National Aeronautics and Space Administration Fiscal Year 2001 Accountability Report

The National Aeronautics and Space Administration (NASA) is an independent Agency established to plan and manage the future of the Nation's civil aeronautics and space program. This Accountability Report covers Federal Fiscal Year (FY) 2001 (October 1, 2000, through September 30, 2001), with discussion of some subsequent events. The Report contains an overview addressing the Agency's critical programs and financial performance and includes highlights of performance organized by goals and objectives of the Enterprises and Crosscutting Processes. The Report also summarizes NASA's stewardship over budget and financial resources, including audited financial statements and footnotes. The financial statements reflect an overall position of offices and activities, including assets and liabilities, as well as results of operations, pursuant to requirements of Federal law (31 U.S.C. 3515(b)). The auditor's opinions on NASA's financial statements, reports on internal controls, and compliance with laws and regulations are included in this report.

Source record↗

National Aeronautics and Space Administration FY 2001 Accountability Report

The National Aeronautics and Space Administration (NASA) is an independent Agency established to plan and manage the future of the Nation's civil aeronautics and space program. This Accountability Report covers Federal Fiscal Year (FY) 2001 (October 1, 2000, through September 30, 2001), with discussion of some subsequent events The Report contains an overview addressing the Agency's critical programs and financial performance and includes highlights of performance organized by goals and objectives of the Enterprises and Crosscutting Processes. The Report also summarizes NASA's stewardship over budget and financial resources, including audited financial statements and footnotes. The financial statements reflect an overall position of offices and activities, including assets and liabilities, as well as results of operations, pursuant to requirements of Federal law (31 U.S.C. 3515(b)). The auditor's opinions on NASA's financial statements, reports on internal controls, and compliance with laws and regulations are included in this Report.

Source record↗

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↗

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.↗

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↗

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↗

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↗

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↗

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 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↗

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↗

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↗