Search NASA⌕ Search

SEARCH · Search NASA

Results for “configuration 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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

Benefits Assessment for Single-Airport Tactical Runway Configuration Management Tool (TRCM)

The System-Oriented Runway Management (SORM) concept was developed as part of the Airspace Systems Program (ASP) Concepts and Technology Development (CTD) Project, and is composed of two basic capabilities: Runway Configuration Management (RCM), and Combined Arrival/Departure Runway Scheduling (CADRS). RCM is the process of designating active runways, monitoring the active runway configuration for suitability given existing factors, and predicting future configuration changes; CADRS is the process of distributing arrivals and departures across active runways based on local airport and National Airspace System (NAS) goals. The central component in the SORM concept is a tool for taking into account all the various factors and producing a recommendation for what would be the optimal runway configuration, runway use strategy, and aircraft sequence, considering as many of the relevant factors required in making this type of decision, and user preferences, if feasible. Three separate tools were initially envisioned for this research area, corresponding to the time scale in which they would operate: Strategic RCM (SRCM), with a planning horizon on the order of several hours, Tactical RCM (TRCM), with a planning horizon on the order of 90 minutes, and CADRS, with a planning horizon on the order of 15-30 minutes[1]. Algorithm development was initiated in all three of these areas, but the most fully developed to date is the TRCM algorithm. Earlier studies took a high-level approach to benefits, estimating aggregate benefits across most of the major airports in the National Airspace Systems (NAS), for both RCM and CADRS [2]. Other studies estimated the benefit of RCM and CADRS using various methods of re-sequencing arrivals to reduce delays3,4, or better balancing of arrival fixes5,6. Additional studies looked at different methods for performing the optimization involved in selecting the best Runway Configuration Plan (RCP) to use7-10. Most of these previous studies were high-level or generic in nature (not focusing on specific airports), and benefits were aggregated for the entire NAS, with relatively low fidelity simulation of SORM functions and aircraft trajectories. For SORM research, a more detailed benefits assessment of RCM and CADRS for specific airports or metroplexes is needed.

Oseguera-Lohr, Rosa↗
NASA NTRS2010

Configuration Management (CM) Support for KM Processes at NASA/Johnson Space Center (JSC)

Collection and processing of information are critical aspects of every business activity from raw data to information to an executable decision. Configuration Management (CM) supports KM practices through its automated business practices and its integrated operations within the organization. This presentation delivers an overview of JSC/Space Life Sciences Directorate (SLSD) and its methods to encourage innovation through collaboration and participation. Specifically, this presentation will illustrate how SLSD CM creates an embedded KM activity with an established IT platform to control and update baselines, requirements, documents, schedules, budgets, while tracking changes essentially managing critical knowledge elements.

Cioletti, Louis↗
NASA NTRS1996

Integrated Advanced Sounding Unit-A (AMSU-A). Configuration Management Plan

The purpose of this plan is to identify the baseline to be established during the development life cycle of the integrated AMSU-A, and define the methods and procedures which Aerojet will follow in the implementation of configuration control for each established baseline. Also this plan establishes the Configuration Management process to be used for the deliverable hardware, software, and firmware of the Integrated AMSU-A during development, design, fabrication, test, and delivery.

Cavanaugh, J.↗
NASA NTRS1974

Configuration management during transition for a powered lift STOL aircraft

Presented in this paper are the analytical and moving-base simulation results of a study to improve flight safety and operations of V/STOL type aircraft. One of the more significant and novel aspects of the work accomplished has been the concept and implementation of a configuration management flight control system designed to take the guesswork out of, and improve the operational safety of, transition flight in the region from cruise to STOL.

Johnson, W. A.↗
NASA NTRS1999

Configuration Management of an Optimization Application in a Research Environment

Multidisciplinary design optimization (MDO) research aims to increase interdisciplinary communication and reduce design cycle time by combining system analyses (simulations) with design space search and decision making. The High Performance Computing and Communication Program's current High Speed Civil Transport application, HSCT4.0, at NASA Langley Research Center involves a highly complex analysis process with high-fidelity analyses that are more realistic than previous efforts at the Center. The multidisciplinary processes have been integrated to form a distributed application by using the Java language and Common Object Request Broker Architecture (CORBA) software techniques. HSCT4.0 is a research project in which both the application problem and the implementation strategy have evolved as the MDO and integration issues became better understood. Whereas earlier versions of the application and integrated system were developed with a simple, manual software configuration management (SCM) process, it was evident that this larger project required a more formal SCM procedure. This report briefly describes the HSCT4.0 analysis and its CORBA implementation and then discusses some SCM concepts and their application to this project. In anticipation that SCM will prove beneficial for other large research projects, the report concludes with some lessons learned in overcoming SCM implementation problems for HSCT4.0.

Townsend, James C.↗
NASA NTRS2010

Context based configuration management system

A computer-based system for configuring and displaying information on changes in, and present status of, a collection of events associated with a project. Classes of icons for decision events, configurations and feedback mechanisms, and time lines (sequential and/or simultaneous) for related events are displayed. Metadata for each icon in each class is displayed by choosing and activating the corresponding icon. Access control (viewing, reading, writing, editing, deleting, etc.) is optionally imposed for metadata and other displayed information.

Gawdiak, Yuri O.↗
DOE OSTI2026

Configuration Management Plan

The Los Alamos Neutron Science Center (LANSCE) is located at Technical Area 53 (TA-53) at Los Alamos National Laboratory (LANL) in Los Alamos, New Mexico. LANSCE is driven by an 800 megaelectronvolt (MeV) proton accelerator that delivered its first beam in 1972. The LANSCE accelerator is unique in that it accelerates both H– (to full energy of 800 MeV) and H+ ions (up to 100 MeV currently but has accelerated high-power H+ beam to 800 MeV in the past) and supports five separate experimental areas that operate simultaneously, with each having different timing and beam current requirements. Many of the LANSCE accelerator front-end components date back to original commissioning in 1972, including the ion sources, Cockcroft-Walton (CW) generators, and the Drift Tube LINAC (DTL), which accelerates the beam up to 100 MeV.

43 PARTICLE ACCELERATORS↗
DOE OSTI2020

Exploiting CRIC to streamline the configuration management of GlideinWMS factories for CMS support

GlideinWMS is a workload management and provisioning system that allows sharing computing resources distributed over independent sites. Based on the requests made by GlideinWMS frontends, a dynamically sized pool of resources is created by GlideinWMS pilot factories via pilot job submission to resource sites’ CEs. More than 400 CEs are currently serving more than ten virtual organizations through GlideinWMS, with CMS being the biggest user with 230 CEs. The complex configurations of the parameters defining resource requests, as submitted to those CEs, have been historically managed by manually editing a set of different XML files. New possibilities arise with CMS adopting the CRIC, an information system that collects, aggregates, stores, and exposes, among other things, computing resource data coming from various data providers. The paper will describe the challenges faced when CMS started to use CRIC to automatically generate the GlideinWMS factory configurations. The architecture of the prototype, and the ancillary tools developed to ease this transition, will be discussed. Finally, future plans and milestones will be outlined.

Dost, Jeffrey↗
NASA NTRS1979

Configuration management and automatic control of an augmentor wing aircraft with vectored thrust

An advanced structure for automatic flight control logic for powered-lift aircraft operating in terminal areas is under investigation at Ames Research Center. This structure is based on acceleration control; acceleration commands are constructed as the sum of acceleration on the reference trajectory and a corrective feedback acceleration to regulate path tracking errors. The central element of the structure, termed a Trimmap, uses a model of the aircraft aerodynamic and engine forces to calculate the control settings required to generate the acceleration commands. This report describes the design criteria for the Trimmap and derives a Trimmap for Ames experimental augmentor wing jet STOL research aircraft.

Cicolani, L. S.↗
NASA NTRS2003

Managing configuration software of ground software applications with glueware

This paper reports on a simple, low-cost effort to streamline the configuration of the uplink software tools. Even though the existing ground system consisted of JPL and custom Cassini software rather than COTS, we chose a glueware approach--reintegrating with wrappers and bridges and adding minimal new functionality.

ground software glueware Cassini↗