SEARCH · Search NASA

Results for “Help Request”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 91 records · Page 5

All sources NASA NTRS DOE OSTI

DOE OSTI2025

BuildingSync® v.2.7.0 (released 9.11.2025) [SWR-18-28]

BuildingSync® is a building data exchange schema to better enable integration between software tools and building data workflows. The schema's original use case was focused on commercial building energy audits; however, several additional use cases have been realized including building energy modeling and more high-level generic building data exchange. Version 2.7.0 adds new elements for file attachment feature and FederalBuilding, and generalizes usage of Optional Elements (e.g. EquipmentCondition, EquipmentID) to all assets/systems. BuildingSync helps streamline the data exchange process, improving the value of the data, minimizing duplication of effort for subsequent building data collection efforts (including audits), and facilitating the achievement of greater energy efficiency. This in done in part by standardizing on (a) reporting audits in an electronic format, (b) tracking proposed, implemented, and discarded energy conservation measures, and (c) storing building characteristics (at multiple levels) for audits, benchmarking, and building energy analysis. BuildingSync has several documents and tools available to help users understand how to best leverage BuildingSync. The list below are only a subset of the resources available. If new resources are discovered, then feel free to create a new pull request with the additions. Generic BuildingSync information is available on the DOE website and the project website. BuildingSync Examples - These examples are kept up to date and show a wide range of implementations. Any new update to BuildingSync is required to pass validation on these example files. BuildingSync Use Case Validator allows for users to determine if their instance complies with a specific use case for BuildingSync by checking if the required elements are implemented in an uploaded instance. An API is also provided for automated integration into other tools. Also, the website contains an easy way to view the entirety of the schema and how elements relate to the Building Exchange Data Exchange Specification. The Validator is open sourced here Use Case TestSuite provides a Python package for easier generation of BuildingSync use cases. BuildingSync use cases depend on the generation of schematron documents, which is time-consuming and difficult to implement well. The TestSuite allows users to define a use case using a more palatable CSV template, which it then turns into a Schematron document. The source code is available here. BuildingSync to OpenStudio/EnergyPlus. The translator is open sourced here. This project will translate a Level 1 (and partial Level 2) ASHRAE Energy Audit to a fully defined OpenStudio and EnergyPlus model. This project is in early Beta testing and any feedback is welcome!

Long, Nicholas [National Renewable Energy Lab. (NR↗

NASA NTRS2009

Configuring a Graphical User Interface for Managing Local HYSPLIT Model Runs Through AWIPS

Responding to incidents involving the release of harmful airborne pollutants is a continual challenge for Weather Forecast Offices in the National Weather Service. When such incidents occur, current protocol recommends forecaster-initiated requests of NOAA's Hybrid Single-Particle Lagrangian Integrated Trajectory (HYSPLIT) model output through the National Centers of Environmental Prediction to obtain critical dispersion guidance. Individual requests are submitted manually through a secured web site, with desired multiple requests submitted in sequence, for the purpose of obtaining useful trajectory and concentration forecasts associated with the significant release of harmful chemical gases, radiation, wildfire smoke, etc., into local the atmosphere. To help manage the local HYSPLIT for both routine and emergency use, a graphical user interface was designed for operational efficiency. The interface allows forecasters to quickly determine the current HYSPLIT configuration for the list of predefined sites (e.g., fixed sites and floating sites), and to make any necessary adjustments to key parameters such as Input Model. Number of Forecast Hours, etc. When using the interface, forecasters will obtain desired output more confidently and without the danger of corrupting essential configuration files.

Wheeler, mark M.↗

DOE OSTI2024

Electricity Markets Design Challenge [Slides]

Electricity markets are at a crossroads - join the U.S. Department of Energy and the National Renewable Energy Laboratory for an exclusive one-hour workshop where you'll engage directly with the project team and help shape the rules for a potential prize. This competition could redefine how electricity markets support renewables and storage resources and create innovative solutions for the challenges ahead. NREL has also issued a Request for Information (RFI) to gather feedback and gauge interest in this potential prize. Whether or not you attend the workshop, we encourage you to review the brief presentation and share your thoughts through the RFI.

16 TIDAL AND WAVE POWER↗

NASA NTRS1993

RENEW v3.2 user's manual, maintenance estimation simulation for Space Station Freedom Program

RENEW is a maintenance event estimation simulation program developed in support of the Space Station Freedom Program (SSFP). This simulation uses reliability and maintainability (R&M) and logistics data to estimate both average and time dependent maintenance demands. The simulation uses Monte Carlo techniques to generate failure and repair times as a function of the R&M and logistics parameters. The estimates are generated for a single type of orbital replacement unit (ORU). The simulation has been in use by the SSFP Work Package 4 prime contractor, Rocketdyne, since January 1991. The RENEW simulation gives closer estimates of performance since it uses a time dependent approach and depicts more factors affecting ORU failure and repair than steady state average calculations. RENEW gives both average and time dependent demand values. Graphs of failures over the mission period and yearly failure occurrences are generated. The averages demand rate for the ORU over the mission period is also calculated. While RENEW displays the results in graphs, the results are also available in a data file for further use by spreadsheets or other programs. The process of using RENEW starts with keyboard entry of the R&M and operational data. Once entered, the data may be saved in a data file for later retrieval. The parameters may be viewed and changed after entry using RENEW. The simulation program runs the number of Monte Carlo simulations requested by the operator. Plots and tables of the results can be viewed on the screen or sent to a printer. The results of the simulation are saved along with the input data. Help screens are provided with each menu and data entry screen.

Bream, Bruce L.↗

NASA NTRSDate not supplied

The Satellite Needs Working Group (SNWG) Biennial Survey: Analyzing Satellite Earth Observation Needs Across U.S. Federal Civilian Agencies

The Satellite Needs Working Group (SNWG) is part of the U.S. Group on Earth Observations (USGEO) and was established to identify high-priority Earth observation satellite needs across U.S. federal civilian agencies. Federal agencies often rely on Earth observation data to fulfill multidisciplinary agency responsibilities such as assessing agricultural crop conditions, detecting wildfires, and monitoring water quality; however, the data sets and tools required to meet these needs are not always readily available or accessible to agency personnel. SNWG conducts a biennial survey of federal satellite needs in order to bridge the gap between Earth observation data providers and their government stakeholders and users. The SNWG Management Office completes an analysis of these survey submissions to gain insight into the types of satellite needs that exist across the government. Within the survey, agencies provide details on how satellite data are used to meet their objectives, measurement requirements needed for their use cases, and gaps that exist in currently available satellite data products and services. For the SNWG 2024 cycle, there were 125 surveys submitted from 25 different agencies. This presentation will discuss findings from the statistical analysis of the SNWG 2024 survey responses and highlight the diverse nature of the needs, common themes in agency requests, and differences in the responses compared to previous cycles. The presentation will also discuss the newly approved SNWG Aggregate Statistics Report that will make these analysis results available to the public and help inform what’s next for science.

Essence Raphael↗

DOE OSTI2025

Validation Testing for Molten Chloride Reactor Experiment Equipment Removal and Disposal Techniques

The Molten Chloride Reactor Experiment (MCRE) will be the first reactor featuring a fast-spectrum molten chloride circulating nuclear fuel system in the world. Planning for equipment removal and disposal (ERD) of MCRE has identified several technology gaps due to the unique environment of this nuclear experiment. Some of the gaps arise from the application of existing disassembly and/or sizing methods to novel material forms or in novel configurations. Others arise from unknown material behavior. This paper summarizes proposed test plans for ERD validation experiments to address these complicated or unknown equipment removal procedures. At the Waste Management Symposia in 2024, the Idaho National Laboratory (INL) MCRE ERD team presented the challenges associated with hosting multiple nuclear experiments in series with only brief transition periods between systems. Such difficulties include higher dose rates, the presence of radioisotopes infrequently encountered in reactor decommissioning and radioactive waste management, lack of intrinsic remote-operations infrastructure in the test bed, space constraints in the test bed, and contamination minimization requirements. To address these challenges, remote or semi-remote technologies are planned to be implemented in a non-hot cell environment with limited space availability. The team also discussed how a systems engineering approach is being used for conceptual development and design of equipment removal systems to address these challenges. For example, to reduce constraints for the removal of more difficult components, non-activated, noncontaminated elements are planned to be taken out first where possible. Still, there are complexities associated with the remaining components. In this work, the operational framework for MCRE ERD was reviewed for technical gaps and open questions, and test plans were drafted to address these areas. The tests plans were written for the following categories: vision systems, pipe cutting, drill/grout/filler, flush salt, and miscellaneous, with the miscellaneous group consisting of tests like techniques for removing bearings and reflector bricks. The test plans explore material, infrastructure, and staffing requirements needed for test execution. The test plans additionally focus on the evaluation of success. Determining the outcome of a test is imperative - as these explorative actions have the potential to rearrange or re-scope planned ERD activities. Success criteria identified thus far include required tool output, required area(s), debris production and mitigation, and repeatability. Test plans are an essential aspect of the systems engineering approach to MCRE ERD. They are used as the beginning steps in defining use cases for the ERD system. Performance of the validation tests is expected to begin in the summer of 2025 and will take approximately 9 to 12 months to complete. Execution of these plans will be expedited by specifying test needs ahead of time, facilitating efficient interactions with any subcontractors tasked with running the requested tests. Evaluating the outcomes of these tests will inform MCRE ERD procedures and timing and will also identify additional technical constraints for the MCRE ERD System. This upfront process optimization effort will help the project save time and resources at the end of the experiment.

21 - SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLAN↗

NASA NTRS1997

SOFIA Science Working Group

The SOFIA Science Working Group was established to help develop the plans and specifications for the next-generation airborne observatory ("SOFIA"), which is now under development. The P.I. has developed several astronomical instruments for the Kuiper Airborne Observatory, NASA's previous airborne astronomy platform (which was decommisioned in 1995 in preparation for SOFIA). SOFIA, which will be a 747 SP aircraft carrying a 2.7 meter diameter telescope, is a joint project sponsored by NASA and DLR (the German space agency), and is now under development by a consortium including Universities Space Research Association (USRA), Raytheon, Sterling Software, and United Airlines. Rather than develop the SOFIA observatory in-house, NASA decided to privatize the project by issuing a Request for Proposals (RFP). The respondents to this RFP were consortia of private organizations which together had the required facilities and expertise to be able to carry out the project; the winner was the group led by USRA. One of the main roles of the SSWG was to help develop the technical specifications for the SOFIA observatory. In particular, the SSWG provided advice to NASA on the specifications that were written into the RFP, particularly those which had an important impact on the scientific productivity of the observatory. These specifications were discussed at the meetings of the SSWG, which were held primarily at NASA/Ames (in California) and at NASA Headquarters (in Washington DC). Apart from these meetings, members of the SSWG were expected to perform more detailed analyses of the impact of certain parameters and specifications on the performance of astronomical instruments. The SSWG ended its activities with the selection of the USRA team in January 1997.

Zmuldzinas, J.↗

NASA NTRS2018

From Apollo to the Future, the NASA Curation Model for Engaging the Sample Science Community Maximizes Science on Extraterrestrial Samples

The Astromaterials Acquisition and Curation Office at Johnson Space Center (JSC) has enjoyed a long-term partnership (50 years!) with a broad community of planetary sample scientists. This partnership has enabled the curators of planetary samples to plan for and enact evolving requirements for preservation of sample scientific integrity and for handling and long-term storage. The basis for this relationship is a standing peer review advisory committee composed of leading scientists who are recognized for achievements in sample analysis. The committee and its descendants have brought familiarity with the most relevant scientific investigations and the associated analytical and contamination challenges. Beginning with Apollo, the review committee was charged with oversight of curatorial operations and with ensuring fair access to samples. As additional samples from other planetary bodies were acquired, the committee evolved, taking on new responsibilities, reflected in committee name changes. However, oversight of curatorial operations and fair allocation of samples remain basic responsibilities. Committee recommendations are sent to the NASA Headquarters Discipline Scientist for approval. To minimize conflict of interest and maximize fair access, the rules governing the make-up of the committee is structured. Systematic rotation of leadership and staggered terms of membership allow the committee to retain expertise while bringing in fresh ideas. The first peer review committee was called the Lunar Sample Analysis and Planning Team (LSAPT) and was formalized in early 1968 with about 15 members. Their function was to review a) the equipment and procedures used in the new Lunar Receiving Laboratory (LRL); b) the proficiency and capability of the LRL staff; c) the sequence of sample analysis and allocation after quarantine release; and d) the findings of the Preliminary Examination Team (PET). According to LSAPT member Gerald Wasserburg, one of the first issues they faced was deciding whether to have most of the sample analyses performed in house at the LRL or to distribute samples to members of the scientific community. LSAPT concluded that the major scientific investigations should be carried out externally to the LRL by scientists chosen for their expertise in specific disciplines. Further they recommended that the PET's basic characterization of samples be circulated to the broad scientific community. LSAPT set its own agenda, paid attention to facility details, closely monitored the move of samples from the LRL to the interim curatorial facility in 1973, and was active in inspecting curation facilities. Between 1975 and 1979, a Facility Subcommittee of LSAPT oversaw the design and construction of a permanent facility for preservation of lunar samples. The result was an outstanding facility still in use today. In 1977, a separate peer review committee, the Meteorite Working Group (MWG), was formed to evaluate requests for new meteorites then being collected in Antarctica under what would in 1980 become a 3-agency agreement (National Science Foundation, NASA, Smithsonian Institution). By 1979, after lunar samples were moved into the new permanent facility, the vacated gloveboxes and laboratory were prepared for meteorite curation. Recognizing that LSAPT had been helpful in setting up the JSC curatorial facility for Antarctic meteorites, JSC recommended the review committee be given expanded duties, including advice on curation and analysis of materials from other planetary bodies and the name be changed to Lunar and Planetary Sample Team (LAPST). In 1993, LAPST was renamed the Curation and Analysis Planning Team for Extraterrestrial Materials (CAPTEM) to reflect additional functions. CAPTEM is chartered to be (1) a community-based, interdisciplinary forum for discussion and analysis of matters concerning the collection and curation of extraterrestrial samples, including planning future sample return missions and (2) a standing review panel, charged with evaluating proposals requesting allocation of all extraterrestrial samples contained in NASA collections. Efficiency and flexibility are gained through use of subcommittees, both ad hoc and standing. Transition of the MWG to a subcommittee of CAPTEM was completed in 2017. Today subcommittees review allocation requests for lunar samples, Antarctic meteorites, cosmic dust, Stardust cometary samples, Genesis solar wind samples, and samples returned from asteroids. Other subcommittees address facilities, informatics, and micro-cratered substrates. Planetary samples have been sent to research teams in over 30 countries world-wide. The expertise in the care and fair distribution of astromaterials by NASA using this model spans generations of planetary sample scientists and is a valuable resource to be tapped for future sample returns - OSIRIS-REx, Hayabusa 2, and Mars 2020.

Allton, Judith↗

DOE OSTI2024

The Design and Evaluation of Zero Trust Architecture for Electric Vehicle Charging Infrastructure: EVs @ Scale Series on EV Charging Station Cybersecurity

Implementing a zero trust architecture can significantly bolster the security of electric vehicle (EV) charging infrastructure. EV charging infrastructure includes numerous networked interfaces, each of which can present potential vulnerabilities. When these vulnerabilities are exploited, they can compromise the entire system, leading to severe operational and security risks. Zero trust is a security model that operates on the principle of "never trust, always verify," which helps manage the attack surface and limit the scope of any potential compromises. Fundamentally, this model ensures that no entity, whether inside or outside the network, is trusted by default. The design principles of zero trust include continuous verification, strict deny-by-default access controls, and micro-segmentation. Continuous verification ensures that every request is thoroughly checked, regardless of its origin. Strict access controls enforce the principle of least privilege, allowing users and devices only the minimum necessary access to perform their functions. Micro-segmentation involves dividing the network into smaller, isolated segments to prevent lateral movement in case of a breach. In the context of EV charging infrastructure, zero trust can be implemented through various strategies. For example, multi-factor authentication (MFA) can be required for engineers to access the management interfaces and control systems of charging stations. Real-time monitoring and analysis of network traffic can help detect and respond to anomalies. Systems that do not need to communicate with each other can be micro-segmented to enhance security. All communications should adhere to predefined policies to be permitted. Additionally, encrypting communications can protect sensitive information exchanged between chargers and management systems. This paper presents a zero trust architecture specifically designed for EV charging infrastructure. Implementing zero trust not only mitigates risks but also builds a resilient infrastructure capable of withstanding and quickly recovering from cyber threats. The architecture addresses six defined security objectives. A comprehensive test plan is developed to assess the architecture against these objectives, and the results of the evaluation are reported. This approach is essential for maintaining the reliability and integrity of EV charging services in an increasingly interconnected and vulnerable digital landscape. This is the first in a planned series of papers exploring the implementation of zero trust in EV charging infrastructure. Each paper will delve into different aspects and applications of zero trust, highlighting how various work processes and requirements can lead to distinct architectural designs. These architectures will be tailored to address specific security challenges and operational needs within the EV charging ecosystem, ensuring a robust and adaptable security framework.

33 ADVANCED PROPULSION SYSTEMS↗

NASA NTRS1997

Sofia Science Working Group

The purpose of this grant was to enable the Principal Investigator (P.I.) to travel to and participate in the meetings and activities of the NASA SOFIA Science Working Group (SSWG), and to spend time working on some of the associated technical issues relating to the SOFIA (Stratospheric Observatory for Infrared Astronomy) project. The SOFIA Science Working Group was established to help develop the plans and specifications for the next-generation airborne observatory ("SOFIA"), which is now under development. The P.I. was asked to serve on the SSWG due to his experience in airborne astronomy: he has developed several astronomical instruments for the Kuiper Airborne Observatory NASA's previous airborne astronomy platform (which was decommissioned in 1995 in preparation for SOFIA). SOFIA, which will be a 747 SP aircraft carrying a 2.7 meter diameter telescope, is a joint project sponsored by NASA and DLR (the German space agency), and is now under development by a consortium including Universities Space Research Association (USRA), Raytheon, Sterling Software, and United Airlines. Further details on the SOFIA project can be found on the internet at http: //sofia. arc. nasa. gov. Rather than develop the SOFIA observatory in-house, NASA decided to privatize the project by issuing a Request for Proposals (RFP). The respondents to this RFP were consortia of private organizations which together had the required facilities and expertise to be able to carry out the project; the winner was the group led by USRA. One of the main roles of the SSWG was to help develop the technical specifications for the SOFIA observatory. In particular, the SSWG provided advice to NASA on the specifications that were written into the RFP, particularly those which had an important impact on the scientific productivity of the observatory. These specifications were discussed at the meetings of the SSWG, which were held primarily at NASA/Ames (in California) and at NASA Headquarters (in Washington DC). Apart from these meetings, members of the SSWG were expected to perform more detailed analyses of the impact of certain parameters and specifications on the performance of astronomical instruments. The SSWG ended its activities with the selection of the USRA team in January 1997.

Zmuidzinas, J.↗

NASA NTRS2002

Software Assists in Extensive Environmental Auditing

The Base Enivronmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists on an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign manditory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: It helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗

NASA NTRS2002

Software Assists in Extensive Environmental Auditing

The Base Environmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists of an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign mandatory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: it helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗

NASA NTRS2011

The NASA Experience

Projects assigned to: (1) Testing, fixing, and procuring enclosure systems and components for Kennedy Ground Controls Systems at launch pad B. (2) Organizational spreadsheets for all subsystems involved in the project. (Procurement, parts lists, drawings, purchase requests, etc) (3) Resolve is a project devoted to the lunar rover that will sample lunar soil in an effort to remove the moister and separate the metal from the oxygen to produce drinkable water. I helped with the humidity environmental generator for the experiment (moister detector).

Ramos, Alberto↗

NASA NTRS2003

Software Assists in Extensive Environmental Auditing

Callac, Christopher↗

NASA NTRS1989

Tracking and data relay satellite fault isolation and correction using PACES: Power and attitude control expert system

The Power and Attitude Control Expert System (PACES) is an object oriented and rule based expert system which provides spacecraft engineers with assistance in isolating and correcting problems within the Power and Attitude Control Subsystems of the Tracking and Data Relay Satellites (TDRS). PACES is designed to act in a consultant role. It will not interface to telemetry data, thus preserving full operator control over spacecraft operations. The spacecraft engineer will input requested information. This information will include telemetry data, action being performed, problem characteristics, spectral characteristics, and judgments of spacecraft functioning. Questions are answered either by clicking on appropriate responses (for text), or entering numeric values. A context sensitive help facility allows access to additional information when the user has difficulty understanding a question or deciding on an answer. The major functionality of PACES is to act as a knowledge rich system which includes block diagrams, text, and graphics, linked using hypermedia techniques. This allows easy movement among pieces of the knowledge. Considerable documentation of the spacecraft Power and Attitude Control Subsystems is embedded within PACES. The development phase of TDRSS expert system technology is intended to provide NASA with the necessary expertise and capability to define requirements, evaluate proposals, and monitor the development progress of a highly competent expert system for NASA's Tracking and Data Relay Satellite Program.

Erikson, Carol-Lee↗

NASA NTRS2004

Intelligent Medical Systems for Aerospace Emergency Medical Services

The purpose of this project is to develop a portable, hands free device for emergency medical decision support to be used in remote or confined settings by non-physician providers. Phase I of the project will entail the development of a voice-activated device that will utilize an intelligent algorithm to provide guidance in establishing an airway in an emergency situation. The interactive, hands free software will process requests for assistance based on verbal prompts and algorithmic decision-making. The device will allow the CMO to attend to the patient while receiving verbal instruction. The software will also feature graphic representations where it is felt helpful in aiding in procedures. We will also develop a training program to orient users to the algorithmic approach, the use of the hardware and specific procedural considerations. We will validate the efficacy of this mode of technology application by testing in the Johns Hopkins Department of Emergency Medicine. Phase I of the project will focus on the validation of the proposed algorithm, testing and validation of the decision making tool and modifications of medical equipment. In Phase 11, we will produce the first generation software for hands-free, interactive medical decision making for use in acute care environments.

Epler, John↗

NASA NTRS2011

Implementation of Enhanced Propulsion Control Modes for Emergency Flight Operation

Aircraft engines can be effective actuators to help pilots avert or recover from emergency situations. Emergency control modes are being developed to enhance the engines performance to increase the probability of recovery under these circumstances. This paper discusses a proposed implementation of an architecture that requests emergency propulsion control modes, allowing the engines to deliver additional performance in emergency situations while still ensuring a specified safety level. In order to determine the appropriate level of engine performance enhancement, information regarding the current emergency scenario (including severity) and current engine health must be known. This enables the engine to operate beyond its nominal range while minimizing overall risk to the aircraft. In this architecture, the flight controller is responsible for determining the severity of the event and the level of engine risk that is acceptable, while the engine controller is responsible for delivering the desired performance within the specified risk range. A control mode selector specifies an appropriate situation-specific enhanced mode, which the engine controller then implements. The enhanced control modes described in this paper provide additional engine thrust or response capabilities through the modification of gains, limits, and the control algorithm, but increase the risk of engine failure. The modifications made to the engine controller to enable the use of the enhanced control modes are described, as are the interaction between the various subsystems and importantly, the interaction between the flight controller/pilot and the propulsion control system. Simulation results demonstrate how the system responds to requests for enhanced operation and the corresponding increase in performance.

Csank, Jeffrey T.↗

NASA NTRS2004

Automation of Design Engineering Processes

A method, and a computer program that helps to implement the method, have been developed to automate and systematize the retention and retrieval of all the written records generated during the process of designing a complex engineering system. It cannot be emphasized strongly enough that all the written records as used here is meant to be taken literally: it signifies not only final drawings and final engineering calculations but also such ancillary documents as minutes of meetings, memoranda, requests for design changes, approval and review documents, and reports of tests. One important purpose served by the method is to make the records readily available to all involved users via their computer workstations from one computer archive while eliminating the need for voluminous paper files stored in different places. Another important purpose served by the method is to facilitate the work of engineers who are charged with sustaining the system and were not involved in the original design decisions. The method helps the sustaining engineers to retrieve information that enables them to retrace the reasoning that led to the original design decisions, thereby helping them to understand the system better and to make informed engineering choices pertaining to maintenance and/or modifications of the system. The software used to implement the method is written in Microsoft Access. All of the documents pertaining to the design of a given system are stored in one relational database in such a manner that they can be related to each other via a single tracking number.

Torrey, Glenn↗