Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “MICROSOFT”

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
DOE OSTI2019

Multi–LDAP Dynamic User Management Tool Utilizing Oracle Application Express and PL/SQL

A Center for Infrastructure Security Analysis (CISA) client system required support of multiple Lightweight Directory Access Protocol (LDAP) directories for multiple, varied user communities. The LDAP directories were all based upon different technologies, i.e., Microsoft Active Directory (AD), Microsoft Active Directory Lightweight Directory Services (ADLDS), and Oracle Internet Directory (OID), depending on system setup, security requirements, and legacy software. Research revealed that PL/SQL provided the capability to execute dynamic PL/SQL and SQL blocks. The dynamic capabilities were utilized along with several configuration tables to provide an object-oriented, polymorphic-like behavior. This architecture was chosen so that a top-level application programming interface (API) could be defined for all calls, no matter what type of LDAP was being manipulated, as each LDAP type has slightly different attributes and requirements. The dynamic nature of the user management system allowed for easy setup and utilization of any new LDAP directories, minimizing the time and effort expended on system changes.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2017

Technical Evaluation Report for the NDMAS AGR-5/6/7 TRISO Irradiation Monitoring System

The Nuclear Data Management and Analysis System (NDMAS) manages irradiation experiment data collected under the Advanced Gas Reactor (AGR) Fuel Development and Qualification program within the Advanced Reactor Technologies Technology Development Office. The AGR-5/6/7 irradiation experiment combines the fifth, sixth, and seventh planned irradiation campaigns of the U.S. Department of Energy AGR Fuel Development and Qualification Program. These combined irradiation tests will consist of fuel qualification tests (AGR-5/6) and a margin test (AGR-7) for the industrially produced uranium oxycarbide (UCO) tristructural isotropic (TRISO) coated particle fuel developed by the AGR program. The objective of the AGR-5/6/7 irradiation experiment is to establish the performance of UCO TRISO fuel fabricated using engineering-scale equipment in a production environment under and beyond normal operating conditions (PNL-5245). Experimental irradiation measurements for this experiment (i.e., thermocouple temperature, gas flow rate, fission product release rate, gross gamma count, and Advanced Test Reactor (ATR) operational parameters) are captured automatically to the NDMAS database. Data derived from numerical simulation or other mathematical analyses (i.e., fast fluence, burnup, temperature, and fission product release to birth ratio) are captured to the database when provided by the researchers. The NDMAS database is a relational database accessed via structured query language and managed with Microsoft SQL Server. While select users can directly access the database, that is not the most convenient way to interact with the data. The NDMAS team constructs numerous tables that combine related datasets, and delivers those data to researchers via graphs and spreadsheets on a Microsoft SharePoint-based website. For the AGR-5/6/7 experimental data, a new subsite has been developed, along with a set of web pages. These pages will be used by members of fuel irradiation team for monitoring irradiation conditions according to specification (SPC-1749), by the physics modelers to access necessary model inputs, and by the nuclear engineering community to view and access data such as fuel temperatures, fission product release from capsules, and ATR operational parameters. The deliverable represented in this document is a SharePoint website containing tables of the AGR-5/6/7 measured and calculated data, graphs displaying the data, and links to source documents and references.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗
DOE OSTI2023

Precursor Analysis Report: SQL Slammer Worm Infection of Davis-Besse Nuclear Power Plant 2003

The SQL Slammer Worm Infection of Davis-Besse Nuclear Power Plant 2003 Precursor Analysis Report leverages publicly available information about Davis-Besse’s 2003 cyber attack and catalogs anomalous observables for each technique employed in the attack. This analysis is based upon the methodology of the Cybersecurity for the Operational Technology Environment (CyOTE) program. On 25 January 2003, the SQL Slammer worm infected more than 90% of vulnerable hosts and crashed the internet in 10 to 15 minutes, making it one of the fastest spreading worms in history. SQL Slammer is a fileless, memory-resident worm that remotely exploits a stack-based buffer overflow vulnerability on local hosts to intensively scan and rapidly self-propagate across the internet. The worm infected approximately 300,000 unpatched hosts running Microsoft Structured Query Language (SQL) Server 2000 or Microsoft Desktop Engine (MSDE) 2000 with SQL Server Resolution Service. The SQL Slammer worm indirectly infected FirstEnergy’s Davis-Besse nuclear power plant by first infecting a consultant’s company network server and then propagating through an external misconfigured connection into Davis-Besse’s site network. The infection caused major network congestion, slow performance, data overloads, and the inability of local hosts to communicate with each other, which eventually caused a loss of availability and a loss of view when the Safety Parameter Display System (SPDS) and Plant Process Computer (PPC) crashed. At the time of the infection, the plant was already offline, the digital monitoring systems had redundant analog backups, and the plant control and safety functions were not affected, so there were no concerns of a safety breach. However, this incident resulted in many lessons learned and spawned important discussions about cybersecurity’s role in nuclear safety and electric power reliability regulation, policy, and guidance. Researchers and analysts identified 10 unique techniques utilized during the attack with a total of 640 observables using MITRE ATT&CK® for Industrial Control Systems. The CyOTE program assesses observables accompanying techniques used prior to the triggering event to identify opportunities to detect malicious activity. If observables accompanying the attack techniques are perceived and investigated prior to the triggering event, earlier comprehension of malicious activity can take place. Eight of the identified techniques used during Davis-Besse cyber attack were precursors to the triggering event. Analysis identified 596 observables associated with these precursor techniques, 428 of which were assessed to have an increased likelihood of being perceived in the 331 days preceding the triggering event. The response and comprehension time could have been reduced if the observables had been identified earlier. The information gathered in this report contributes to a library of observables tied to a repository of artifacts, data sources, and technique detection references for practitioners and developers to support the comprehension of indicators of attack. Asset owners and operators can use these products if they experience similar observables or to prepare for comparable scenarios.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗
DOE OSTI2025

Leveraging Open-Source Satellite-Derived Building Footprints for Height Inference

At a global scale, cities are growing and characterizing the built environment is essential for deeper understanding of human population patterns, urban development, energy usage, climate change impacts, among others. Buildings are a key component of the built environment and significant progress has been made in recent years to scale building footprint extractions from satellite datum and other remotely sensed products. Billions of building footprints have recently been released by companies such as Microsoft and Google at a global scale. However, research has shown that depending on the methods leveraged to produce a footprint dataset, discrepancies can arise in both the number and shape of footprints produced. Therefore, each footprint dataset should be examined and used on a case-by-case study. In this work, we find through two experiments on Oak Ridge National Laboratory and Microsoft footprints within the same geographic extent that our approach of inferring height from footprint morphology features is source agnostic. Regardless of the differences associated with the methods used to produce a building footprint dataset, our approach of inferring height was able to overcome these discrepancies between the products and generalize, as evidenced by 98% of our results being within 3m of the ground-truthed height. This signifies that our approach can be applied to the billions of open-source footprints which are freely available to infer height, a key building metric. This work impacts the broader domain of urban science in which building height is a key, and limiting factor.

Stipek, Clinton [ORNL] (ORCID:0000000280501096)↗
DOE OSTI2023

HarDWR - Raw Water Rights Records

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. In order to hold a water right in the western United States, an entity, (e.g., an individual, corporation, municipality, sovereign government, or non-profit) must register a physical document with the state's water regulatory agency. State water agencies each maintain their own database containing all registered water right documents within the state, along with relevant metadata such as the point of diversion and place of use of the water. All western U.S. states have digitized their individual water rights databases, along with the geospatial data describing the spatial units where water rights are managed. Each state maintains and provides their own water rights data in accordance with individual state regulations and standards. We collected water rights databases from 11 western United States states either by downloading them from publicly accessible web portals, or by contacting state water management representatives; detailed descriptions of where and when the data was collected is provided in the README.txt, as well as Lisk et al.(in review). This collection of data are those raw water rights. Each state formats their data differently, meaning that file types, field availability, and names vary from state to state. Note, the data provided here reflects the state of the water rights databases at the time we collected the data; updates have likely occurred in many states. Some pieces of information are common among all states. These are: priority date, volume or flow of water allowed by the right, stated water use of the right, and some means of identifying the geography and source of the water pertaining to the right - typically the coordinates of the Point of Diversion (PoD) of a waterbody or well. Arizona regulates water in a different way than the other 10 states. Outside of some relatively small critical agricultural areas called Active Management Areas (AMAs), Arizona does not maintain any water rights. However, the state does require registration of surface and groundwater pumping devices, which includes disclosing the mechanical specifics of the devices. We used these records as a proxy for water rights. Each state, and their respective water right authorities, have made their water right records available for non-commercial reference uses. In addition, the states make no guarantees as to the completeness, accuracy, or timeliness of their respective databases, let alone the modifications which we, the authors of this paper, have made to the collected records. None of the states should be held liable for using this data outside of its intended use. In addition, the following states have requested specifically worded disclaimers to be included with their data. Colorado: "The data made available here has been modified for use from its original source, which is the State of Colorado. THE STATE OF COLORADO MAKES NO REPRESENTATIONS OR WARRANTY AS TO THE COMPLETENESS, ACCURACY, TIMELINESS, OR CONTENT OF ANY DATA MADE AVAILABLE THROUGH THIS SITE. THE STATE OF COLORADO EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the Web feed is being used at one's own risk." Montana: "The Montana State Library provides this product/service for informational purposes only. The Library did not produce it for, nor is it suitable for legal, engineering, or surveying purposes. Consumers of this information should review or consult the primary data and information sources to ascertain the viability of the information for their purposes. The Library provides these data in good faith but does not represent or warrant its accuracy, adequacy, or completeness. In no event shall the Library be liable for any incorrect results or analysis; any direct, indirect, special, or consequential damages to any party; or any lost profits arising out of or in connection with the use or the inability to use the data or the services provided. The Library makes these data and services available as a convenience to the public, and for no other purpose. The Library reserves the right to change or revise published data and/or services at any time." Oregon: "This product is for informational purposes and may not have been prepared for, or be suitable for legal, engineering, or surveying purposes. Users of this information should review or consult the primary data and information sources to ascertain the usability of the information." The available data is provided as a series of compressed files, which each containing the full data collected from each state. Some of the files have been renamed, to more easily know which state the data belongs to. The file renaming was also required as some files from different states had the same name. In other cases, the data for a state has been placed in a folder indicating which state it belongs to - as the state organized its data by selected subregions. Below is a brief description of the format of the collected data from each state. ArizonaRights_StatementOfClaimants: A folder containing a database of interconnected CSV files. The soc_erd.pdf file contains a visual flowchart of how the various files are connected, beginning with SOC_MAIN.csv in the center of the page. ArizonaRights_SurfaceWaterRightsData: A folder containing a database of a single Shapefile and 10 associated CSVs. SurfaceWater.pdf contains a visual flowchart of how the various files are connected, beginning with ADWR_SW_APPL_REGRY.csv. ArizonaRights_Well55Registry: A folder containing a database of a single Shapefile and 59 associated CSVs. Wells55.pdf contains a visual flowchart of how the various files are connected, beginning with WellRegistry.shp. CaliforniaRights_eWRIMS_directDatabase: A folder containing a collection of four "series" Microsoft Excel files, as either XLS or XLSX. The four "series": byCounty, byEntity (what type of legal entity holds the right), byUse (stated water use), and byWatershed, are various methods by which the California water rights are organized within the state's database. However, it was observed that by only collecting a single series, not all water rights were being provided. So, essentially, the majority of records within each "series" are copies of each other, with each "series" containing some unique records. ColoradoRights_NetAmounts: A folder containing 78 CSV files, with one file per Colorado Water District. IdahoRights_PointOfDiversion: A Shapefile containing the Points of Diversion for the entire state of Idaho. IdahoRights_PlaceOfUse: A Shapefile containing the Place of Use polygons for the entire state of Idaho. MontanaRights_WaterRights: A Geodatabase file containing the Points of Diversion and Places of Use for the entire state of Montana. The name of the Points of Diversion Feature Layer within the Geodatabase is "WRDIV", and the name of the Places of Use Feature Layer is "WRPOU". NevadaRights_POD_Sites: A Shapefile containing the Points of Diversion for the entire state of Nevada. NewMexicoRights_Points_of_Diversion: A Shapefile containing the Points of Diversion for the entire state of New Mexico. OregonRights_state_shp: A folder containing 36 Shapefiles and are split between "pod" (Point of Diversion) and "pou" (Place of Use) for each water management basin within Oregon. In other words, each basin has one "pod" file and one "pou" file. The "pod" files are point shapes, and the "pou" files are polygons. UtahRights_Points_of_Diversion: A Shapefile containing the Points of Diversion for the entire state of Utah. WashingtonRights_WaterDiversions_ECY_NHD: A Geodatabase file containing both the Points of Diversion for the entire state of Washington. The name of the Feature Layer within the Geodatabase is "WaterDiversions_ECY_NHD". WyomingRights: A folder containing four subdirectories, one for each Wyoming Water Division. Each Division directory includes a varying number of subdirectories for each Wyoming Water District. Each District folder contains two copies of the Point of Diversion records for that area, with one copying being in CSV and one copy in Microsoft Excel XLS format.

Lisk, Matthew↗
NASA NTRS1992

Estimating Effects Of Rain On Ground/Satellite Communication

LeRC-SLAM provides static and dynamic statistical assessment of impact of attenuation by rain on communication link established between Earth terminal and geosynchronous satellite. Program designed for use in specification, design, and assessment of satellite link for any terminal location in continental United States. IBM PC version written in Microsoft QuickBASIC, and Macintosh version written in Microsoft Basic.

Manning, R. M.↗
NASA NTRS1994

Aircraft stress sequence development: A complex engineering process made simple

Development of stress sequences for critical aircraft structure requires flight measured usage data, known aircraft loads, and established relationships between aircraft flight loads and structural stresses. Resulting cycle-by-cycle stress sequences can be directly usable for crack growth analysis and coupon spectra tests. Often, an expert in loads and spectra development manipulates the usage data into a typical sequence of representative flight conditions for which loads and stresses are calculated. For a fighter/trainer type aircraft, this effort is repeated many times for each of the fatigue critical locations (FCL) resulting in expenditure of numerous engineering hours. The Aircraft Stress Sequence Computer Program (ACSTRSEQ), developed by Southwest Research Institute under contract to San Antonio Air Logistics Center, presents a unique approach for making complex technical computations in a simple, easy to use method. The program is written in Microsoft Visual Basic for the Microsoft Windows environment.

Schrader, K. H.↗
NASA NTRS1996

LTCP 2D Graphical User Interface. Application Description and User's Guide

A graphical user interface (GUI) written for NASA's LTCP (Liquid Thrust Chamber Performance) 2 dimensional computational fluid dynamic code is described. The GUI is written in C++ for a desktop personal computer running under a Microsoft Windows operating environment. Through the use of common and familiar dialog boxes, features, and tools, the user can easily and quickly create and modify input files for the LTCP code. In addition, old input files used with the LTCP code can be opened and modified using the GUI. The application is written in C++ for a desktop personal computer running under a Microsoft Windows operating environment. The program and its capabilities are presented, followed by a detailed description of each menu selection and the method of creating an input file for LTCP. A cross reference is included to help experienced users quickly find the variables which commonly need changes. Finally, the system requirements and installation instructions are provided.

Ball, Robert↗
NASA NTRS1998

Preliminary In-Flight Loads Analysis of In-Line Launch Vehicles using the VLOADS 1.4 Program

To calculate structural loads of in-line launch vehicles for preliminary design, a very useful computer program is VLOADS 1.4. This software may also be used to calculate structural loads for upper stages and planetary transfer vehicles. Launch vehicle inputs such as aerodynamic coefficients, mass properties, propellants, engine thrusts, and performance data are compiled and analyzed by VLOADS to produce distributed shear loads, bending moments, axial forces, and vehicle line loads as a function of X-station along the vehicle's length. Interface loads, if any, and translational accelerations are also computed. The major strength of the software is that it enables quick turnaround analysis of structural loads for launch vehicles during the preliminary design stage of its development. This represents a significant improvement over the alternative-the time-consuming, and expensive chore of developing finite element models. VLOADS was developed as a Visual BASIC macro in a Microsoft Excel 5.0 work book on a Macintosh. VLOADS has also been implemented on a PC computer using Microsoft Excel 7.0a for Windows 95. VLOADS was developed in 1996, and the current version was released to COSMIC, NASA's Software Technology Transfer Center, in 1997. The program is a copyrighted work with all copyright vested in NASA.

Graham, J. B.↗
NASA NTRS2000

Evaluation of X-38 Crew Return Vehicle Input Control Devices in a Microgravity Environment

This report was created by students from Longview High School, Longview, Texas. Longview High School was selected from a group of Texas high schools to participate in the 1999 Texas Fly High Program. This program gives Texas high school students a chance to work with NASA engineers to design and fly a real-world experiment aboard the KC-135 during zero-g parabolas. Jeffrey Fox's role was to provide a concept for the experiment and to mentor the students in its design and testing. The students were responsible for executing all phases of the project. The X-38 Project Office at the Lyndon B. Johnson Space Center Johnson Space is designing a crew return vehicle (CRV) to be docked at the International Space Station for crew rescue in an emergency. Vehicle controls will be almost completely automated, but a few functions will be manually controlled. Four crew input control devices were selected for evaluation by Longview High School students as part of the 1999 Texas Fly High program. These were (1) Logitech Trackman Marble (optical trackball), (2) Smart Cat Touchpad. (3) Microsoft SideWinder 3D-Pro Joystick, and (4) Microsoft SideWinder Gamepad. In two flight tests in the KC-135 aircraft and a series of ground tests, the devices were evaluated for ability to maneuver an on-screen cursor, level of accuracy, ease of handling blind operations, and level of user comfort in microgravity. The tests results led to recommendation of further tests with the Joystick and the Trackman by astronauts and actual space station residents.

Welge, Kirsten↗
NASA NTRS2000

Do-It-Yourself: A Special Library's Approach to Creating Dynamic Web Pages Using Commercial Off-The-Shelf Applications

Many librarians may feel that dynamic Web pages are out of their reach, financially and technically. Yet we are reminded in library and Web design literature that static home pages are a thing of the past. This paper describes how librarians at the Institute for Defense Analyses (IDA) library developed a database-driven, dynamic intranet site using commercial off-the-shelf applications. Administrative issues include surveying a library users group for interest and needs evaluation; outlining metadata elements; and, committing resources from managing time to populate the database and training in Microsoft FrontPage and Web-to-database design. Technical issues covered include Microsoft Access database fundamentals, lessons learned in the Web-to-database process (including setting up Database Source Names (DSNs), redesigning queries to accommodate the Web interface, and understanding Access 97 query language vs. Standard Query Language (SQL)). This paper also offers tips on editing Active Server Pages (ASP) scripting to create desired results. A how-to annotated resource list closes out the paper.

Relational databases↗
NASA NTRS2004

Unitized Regenerative Fuel Cell System Gas Dryer/Humidifier Analytical Model Development

A lightweight Unitized Regenerative Fuel Cell (URFC) Energy Storage System concept is being developed at the NASA Glenn Research Center (GRC). This Unitized Regenerative Fuel Cell System (URFCS) is unique in that it uses Regenerative Gas Dryers/Humidifiers (RGD/H) that are mounted on the surface of the gas storage tanks that act as the radiators for thermal control of the Unitized Regenerative Fuel Cell System (URFCS). As the gas storage tanks cool down during URFCS charging the RGD/H dry the hydrogen and oxygen gases produced by electrolysis. As the gas storage tanks heat up during URFCS discharging, the RGD/H humidify the hydrogen and oxygen gases used by the fuel cell. An analytical model was developed to simulate the URFCS RGD/H. The model is in the form of a Microsoft (registered trademark of Microsoft Corporation) Excel worksheet that allows the investigation of the RGD/H performance. Finite Element Analysis (FEA) modeling of the RGD/H and the gas storage tank wall was also done to analyze spatial temperature distribution within the RGD/H and the localized tank wall. Test results obtained from the testing of the RGD/H in a thermal vacuum environment were used to corroborate the analyses.

Burke, Kenneth A.↗
NASA NTRS2004

A Three-fold Outlook of the Ultra-Efficient Engine Technology Program Office (UEET)

The Ultra-Efficient Engine Technology (UEET) Office at NASA Glenn Research Center is a part of the Aeronautics Directorate. Its vision is to develop and hand off revolutionary turbine engine propulsion technologies that will enable future generation vehicles over a wide range of flight speeds. There are seven different technology area projects of UEET. During my tenure at NASA Glenn Research Center, my assignment was to assist three different areas of UEET, simultaneously. I worked with Kathy Zona in Education Outreach, Lynn Boukalik in Knowledge Management, and Denise Busch with Financial Management. All of my tasks were related to the business side of UEET. As an intern with Education Outreach I created a word search to partner with an exhibit of a Turbine Engine developed out of the UEET office. This exhibit is a portable model that is presented to students of varying ages. The word search complies with National Standards for Education which are part of every science, engineering, and technology teachers curriculum. I also updated a Conference Planning/Workshop Excel Spreadsheet for the UEET Office. I collected and inputted facility overviews from various venues, both on and off site to determine where to hold upcoming conferences. I then documented which facilities were compliant with the Federal Emergency Management Agency's (FEMA) Hotel and Motel Fire Safety Act of 1990. The second area in which I worked was Knowledge Management. a large knowledge management system online which has extensive documentation that continually needs reviewing, updating, and archiving. Knowledge management is the ability to bring individual or team knowledge to an organizational level so that the information can be stored, shared, reviewed, archived. Livelink and a secure server are the Knowledge Management systems that UEET utilizes, Through these systems, I was able to obtain the documents needed for archiving. My assignment was to obtain intellectual property including reports, presentations, or any other documents related to the project. My next task was to document the author, date of creation, and all other properties of each document. To archive these documents I worked extensively with Microsoft Excel. different financial systems of accounting such as the SAP business accounting system. I also learned the best ways to present financial data and shadowed my mentor as she presented financial data to both UEET's project management and the Resources Analysis and Management Office (RAMO). I analyzed the June 2004 financial data of UEET and used Microsoft Excel to input the results of the data. This process made it easier to present the full cost of the project in the month of June. In addition I assisted in the End of the Year 2003 Reconciliation of Purchases of UEET.

Graham, La Quilia E.↗
NASA NTRS2004

Resource Management in the Microgravity Science Division

In the Microgravity Science Division, the primary responsibilities of the Business Management Office are resource management and data collection. Resource management involves working with a budget to do a number of specific projects, while data collection involves collecting information such as the status of projects and workforce hours. This summer in the Business Management Office I assisted Margie Allen with resource planning and the implementation of specific microgravity projects. One of the main duties of a Project Control Specialists, such as my mentor, is to monitor and analyze project manager s financial plans. Project managers work from the bottom up to determine how much money their project will cost. They then set up a twelve month operating plan which shows when money will be spent. I assisted my mentor in checking for variances in her data against those of the project managers. In order to successfully check for those variances, we had to understand: where the project is including plans vs. actual performance, why it is in its present condition, and what the future impact will be based on known budgetary parameters. Our objective was to make sure that the plan, or estimated resources input, are a valid reflection of the actual cost. To help with my understanding of the process, over the course of my tenure I had to obtain skills in Microsoft Excel and Microsoft Access.

Casselle, Justine↗
NASA NTRS2005

Performance (Off-Design) Cycle Analysis for a Turbofan Engine With Interstage Turbine Burner

This report presents the performance of a steady-state, dual-spool, separate-exhaust turbofan engine, with an interstage turbine burner (ITB) serving as a secondary combustor. The ITB, which is located in the transition duct between the high- and the low-pressure turbines, is a relatively new concept for increasing specific thrust and lowering pollutant emissions in modern jet-engine propulsion. A detailed off-design performance analysis of ITB engines is written in Microsoft(Registered Trademark) Excel (Redmond, Washington) macrocode with Visual Basic Application to calculate engine performances over the entire operating envelope. Several design-point engine cases are pre-selected using a parametric cycle-analysis code developed previously in Microsoft(Registered Trademark) Excel, for off-design analysis. The off-design code calculates engine performances (i.e. thrust and thrust-specific-fuel-consumption) at various flight conditions and throttle settings.

Liew, K. H.↗
NASA NTRS2006

A Comparison of Coolant Options for Brayton Power Conversion Heat Rejection Systems

This paper describes potential heat rejection design concepts for Brayton power conversion systems. Brayton conversion systems are currently under study by NASA for Nuclear Electric Propulsion (NEP) and surface power applications. The Brayton Heat Rejection Subsystem (HRS) must dissipate waste heat generated by the power conversion system due to inefficiencies in the thermal-to-electric conversion process. Sodium potassium (NaK) and H2O are two coolant working fluids that have been investigated in the design of a pumped loop and heat pipe space HRS. In general NaK systems are high temperature (300 to 1000 K) low pressure systems, and H2O systems are low temperature (300 to 600 K) high pressure systems. NaK is an alkali metal with health and safety hazards that require special handling procedures. On the other hand, H2O is a common fluid, with no health hazards and no special handling procedures. This paper compares NaK and H20 for the HRS pumped loop coolant working fluid. A detailed Microsoft Excel (Microsoft Corporation, Redmond, WA) analytical model, HRS_Opt, was developed to evaluate the various HRS design parameters. It is capable of analyzing NaK or H2O coolant, parallel or series flow configurations, and numerous combinations of other key parameters (heat pipe spacing, diameter and radial flux, radiator facesheet thickness, fluid duct system pressure drop, system rejected power, etc.) of the HRS. This paper compares NaK against water for the HRS coolant working fluid with respect to the relative mass, performance, design and implementation issues between the two fluids.

Mason, Lee S.↗
NASA NTRS2009

Interactive, Automated Management of Icing Data

IceVal DatAssistant is software (see figure) that provides an automated, interactive solution for the management of data from research on aircraft icing. This software consists primarily of (1) a relational database component used to store ice shape and airfoil coordinates and associated data on operational and environmental test conditions and (2) a graphically oriented database access utility, used to upload, download, process, and/or display data selected by the user. The relational database component consists of a Microsoft Access 2003 database file with nine tables containing data of different types. Included in the database are the data for all publicly releasable ice tracings with complete and verifiable test conditions from experiments conducted to date in the Glenn Research Center Icing Research Tunnel. Ice shapes from computational simulations with the correspond ing conditions performed utilizing the latest version of the LEWICE ice shape prediction code are likewise included, and are linked to the equivalent experimental runs. The database access component includes ten Microsoft Visual Basic 6.0 (VB) form modules and three VB support modules. Together, these modules enable uploading, downloading, processing, and display of all data contained in the database. This component also affords the capability to perform various database maintenance functions for example, compacting the database or creating a new, fully initialized but empty database file.

Levinson, Laurie H.↗
NASA NTRS2009

Human-System Integration Scorecard Update to VB.Net

The purpose of this project was to create Human-System Integration (HSI) scorecard software, which could be utilized to validate that human factors have been considered early in hardware/system specifications and design. The HSI scorecard is partially based upon the revised Human Rating Requirements (HRR) intended for NASA's Constellation program. This software scorecard will allow for quick appraisal of HSI factors, by using visual aids to highlight low and rapidly changing scores. This project consisted of creating a user-friendly Visual Basic program that could be easily distributed and updated, to and by fellow colleagues. Updating the Microsoft Word version of the HSI scorecard to a computer application will allow for the addition of useful features, improved easy of use, and decreased completion time for user. One significant addition is the ability to create Microsoft Excel graphs automatically from scorecard data, to allow for clear presentation of problematic areas. The purpose of this paper is to describe the rational and benefits of creating the HSI scorecard software, the problems and goals of project, and future work that could be done.

Sanders, Blaze D.↗