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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS1984

Software control and system configuration management: A systems-wide approach

A comprehensive software control and system configuration management process for flight-crucial digital control systems of advanced aircraft has been developed and refined to insure efficient flight system development and safe flight operations. Because of the highly complex interactions among the hardware, software, and system elements of state-of-the-art digital flight control system designs, a systems-wide approach to configuration control and management has been used. Specific procedures are implemented to govern discrepancy reporting and reconciliation, software and hardware change control, systems verification and validation testing, and formal documentation requirements. An active and knowledgeable configuration control board reviews and approves all flight system configuration modifications and revalidation tests. This flexible process has proved effective during the development and flight testing of several research aircraft and remotely piloted research vehicles with digital flight control systems that ranged from relatively simple to highly complex, integrated mechanizations.

Petersen, K. L.↗
NASA NTRS1990

GSC configuration management plan

The tools and methods used for the configuration management of the artifacts (including software and documentation) associated with the Guidance and Control Software (GCS) project are described. The GCS project is part of a software error studies research program. Three implementations of GCS are being produced in order to study the fundamental characteristics of the software failure process. The Code Management System (CMS) is used to track and retrieve versions of the documentation and software. Application of the CMS for this project is described and the numbering scheme is delineated for the versions of the project artifacts.

Withers, B. Edward↗
NASA NTRS1992

Ground Systems Development Environment (GSDE) software configuration management

This report presents a review of the software configuration management (CM) plans developed for the Space Station Training Facility (SSTF) and the Space Station Control Center. The scope of the CM assessed in this report is the Systems Integration and Testing Phase of the Ground Systems development life cycle. This is the period following coding and unit test and preceding delivery to operational use. This report is one of a series from a study of the interfaces among the Ground Systems Development Environment (GSDE), the development systems for the SSTF and the SSCC, and the target systems for SSCC and SSTF. This is the last report in the series. The focus of this report is on the CM plans developed by the contractors for the Mission Systems Contract (MSC) and the Training Systems Contract (TSC). CM requirements are summarized and described in terms of operational software development. The software workflows proposed in the TSC and MSC plans are reviewed in this context, and evaluated against the CM requirements defined in earlier study reports. Recommendations are made to improve the effectiveness of CM while minimizing its impact on the developers.

Church, Victor E.↗
NASA NTRSDate not supplied

Airport Runway Configuration Management with Offline Model-free Reinforcement Learning

Runway configuration management (RCM) deals with the optimal selection of runways to operate on (for arrivals and departures) based on traffic, surface wind speed, wind direction and other environmental variables. RCM is one of the most challenging tasks in air traffic management, as it relies on operational and environmental variables (e.g., weather forecast) that are highly uncertain and complex to model. In this paper, an innovative and automated approach is deployed using offline model-free reinforcement learning to provide decision-support for RCM. The proposed technology processes historical data about variables of interest, decisions made regarding RCM, and their subsequent outcome, to identify a policy that would encourage good decisions and avoid the poor ones. The policy search is guided by an appropriately chosen weighted utility function (e.g., based on minimizing delays and go-arounds). Finally, the performance of the proposed tool is validated using Charlotte Douglas International Airport as the case study, which shows that the proposed method is superior to other conventional rule-based approaches.

Milad Memarzadeh↗
NASA NTRSDate not supplied

Airport Runway Configuration Management with Offline Model-free Reinforcement Learning

Runway configuration management (RCM) deals with the optimal selection of runways to operate on (for arrivals and departures) based on traffic, surface wind speed, wind direction and other environmental variables. RCM is one of the most challenging tasks in air traffic management, as it relies on operational and environmental variables (e.g., weather forecast) that are highly uncertain and complex to model. In this paper, an innovative and automated approach is deployed using offline model-free reinforcement learning to provide decision-support for RCM. The proposed technology processes historical data about variables of interest, decisions made regarding RCM, and their subsequent outcome, to identify a policy that would encourage good decisions and avoid the poor ones. The policy search is guided by an appropriately chosen weighted utility function (e.g., based on minimizing delays and go-arounds). Finally, the performance of the proposed tool is validated using Charlotte Douglas International Airport as the case study, which shows that the proposed method is superior to other conventional rule-based approaches.

Milad Memarzadeh↗
DOE OSTI2020

A LEAN SYSTEMS APPROACH TO IMPROVING MAINTENANCE OUTPUT AND CONFIGURATION MANAGEMENT

The purpose of this capstone paper is to apply a lean systems approach to the current maintenance planning program in the Assembly/Disassembly Organization. This capstone will take a two-pronged approach to address both output rate in maintenance planning and accurate configuration management resulting from maintenance work orders. In short, the current system suffers from waste in the planning process due lack of procedures to address varying maintenance packages, including maintenance packages which include changes to configuration managed systems. The capstone will detail a lean systems approach to proper characterization of maintenance jobs and integration of change management into the maintenance process in order to retain proper control of the systems used to produce in this nuclear facility.

99 GENERAL AND MISCELLANEOUS↗
NASA NTRS1993

NCCDS configuration management process improvement

By concentrating on defining and improving specific Configuration Management (CM) functions, processes, procedures, personnel selection/development, and tools, internal and external customers received improved CM services. Job performance within the section increased in both satisfaction and output. Participation in achieving major improvements has led to the delivery of consistent quality CM products as well as significant decreases in every measured CM metrics category.

Shay, Kathy↗
NASA NTRS1992

NASA's acquisition requirements for configuration management

A viewgraph presentation on NASA's acquisition requirements for configuration management (CM) goes over CM requirements for single mission and multi-mission orientations, CM automation and CALS implementation initiatives, NASA implementation of DOD standards and DID's (data item descriptions), impact of traceability in NASA CM support, NASA's CM efforts in modifying/upgrading equipment, and CM control of multi-vendor hardware.

Coletta, Mark P.↗
NASA NTRS2009

How Configuration Management Helps Projects Innovate and Communicate

This slide presentation reviews the concept of Configuration Management (CM) and compares it to the standard view of Project management (PM). It presents two PM models: (1) Kepner-Tregoe,, and the Deming models, describes why projects fail, and presents methods of how CM helps projects innovate and communicate.

Cioletti, Louis A.↗
NASA NTRS1994

Earth Observing System (EOS)/Advanced Microwave Sounding Unit A (AMSU-A) configuration management plan

This plan describes methods and procedures Aerojet will follow in the implementation of configuration control for each established baseline. The plan is written in response to the GSFC EOS CM Plan 420-02-02, dated January 1990, and also meets he requirements specified in DOD-STD-480, DOD-D 1000B, MIL-STD-483A, and MIL-STD-490B. The plan establishes the configuration management process to be used for the deliverable hardware, software, and firmware of the EOS/AMSU-A during development, design, fabrication, test, and delivery. This revision includes minor updates to reflect Aerojet's CM policies.

Cavanaugh, J.↗
NASA NTRS2008

Current Practices in Runway Configuration Management (RCM) and Arrival/Departure Runway Balancing (ADRB)

Significant air traffic increases are anticipated for the future of the National Airspace System (NAS). To cope with future traffic increases, fundamental changes are required in many aspects of the air traffic management process including the planning and use of NAS resources. Two critical elements of this process are the selection of airport runway configurations, and the effective management of active runways. Two specific research areas in NASA's Airspace Systems Program (ASP) have been identified to address efficient runway management: Runway Configuration Management (RCM) and Arrival/Departure Runway Balancing (ADRB). This report documents efforts in assessing past as well as current work in these two areas.

Lohr, Gary W.↗
NASA NTRS1991

Configuration management plan. System definition and project development. Repository Based Software Engineering (RBSE) program

This is the configuration management Plan for the AdaNet Repository Based Software Engineering (RBSE) contract. This document establishes the requirements and activities needed to ensure that the products developed for the AdaNet RBSE contract are accurately identified, that proposed changes to the product are systematically evaluated and controlled, that the status of all change activity is known at all times, and that the product achieves its functional performance requirements and is accurately documented.

Mckay, Charles↗
NASA NTRS1992

Configuration management and software measurement in the Ground Systems Development Environment (GSDE)

A set of functional requirements for software configuration management (CM) and metrics reporting for Space Station Freedom ground systems software are described. This report is one of a series from a study of the interfaces among the Ground Systems Development Environment (GSDE), the development systems for the Space Station Training Facility (SSTF) and the Space Station Control Center (SSCC), and the target systems for SSCC and SSTF. The focus is on the CM of the software following delivery to NASA and on the software metrics that relate to the quality and maintainability of the delivered software. The CM and metrics requirements address specific problems that occur in large-scale software development. Mechanisms to assist in the continuing improvement of mission operations software development are described.

Church, Victor E.↗
NASA NTRSDate not supplied

Configuration Management of Distributed cFS Repositories for Multiple Projects

The presentation describes how we use Git and Jira tools to do configuration management (CM) of a multitude of Git repositories for various cFS products being used by multiple cFS projects. Our CM setup takes in considerations the followings: 1. A Git repository can come from an open-source site or an internal site; AND 2. A Git repository can be owned and maintained by an organization, where release milestones and planned changes are controlled internally; AND 3. A Git repository can be shared among projects, where each project uses a specific branch of the code base; AND 4. Tracking and tracing tasks/issues that affect multiple Git repositories. This presentation complements the talk on cFS latest updates, to be presented by Daniel Knutsen from Goddard Space Flight Center.

Tam M Ngo↗
NASA NTRS2015

Benefit Assessment for Metroplex Tactical Runway Configuration Management (mTRCM) in a Simulated Environment

The System-Oriented Runway Management (SORM) concept is a collection of capabilities focused on a more efficient use of runways while considering all of the factors that affect runway use. Tactical Runway Configuration Management (TRCM), one of the SORM capabilities, provides runway configuration and runway usage recommendations, and monitoring the active runway configuration for suitability given existing factors. This report focuses on the metroplex environment, with two or more proximate airports having arrival and departure operations that are highly interdependent. The myriad of factors that affect metroplex opeations require consideration in arriving at runway configurations that collectively best serve the system as a whole. To assess the metroplex TRCM (mTRCM) benefit, the performance metrics must be compared with the actual historical operations. The historical configuration schedules can be viewed as the schedules produced by subject matter experts (SMEs), and therefore are referred to as the SMEs' schedules. These schedules were obtained from the FAA's Aviation System Performance Metrics (ASPM) database; this is the most representative information regarding runway configuration selection by SMEs. This report focused on a benefit assessment of total delay, transit time, and throughput efficiency (TE) benefits using the mTRCM algorithm at representative volumes for today's traffic at the New York metroplex (N90).

Phojanamongkolkij, Nipa↗
NASA NTRS2014

Throughput Benefit Assessment for Tactical Runway Configuration Management (TRCM)

The System-Oriented Runway Management (SORM) concept is a collection of needed capabilities focused on a more efficient use of runways while considering all of the factors that affect runway use. Tactical Runway Configuration Management (TRCM), one of the SORM capabilities, provides runway configuration and runway usage recommendations, monitoring the active runway configuration for suitability given existing factors, based on a 90 minute planning horizon. This study evaluates the throughput benefits using a representative sample of today's traffic volumes at three airports: Memphis International Airport (MEM), Dallas-Fort Worth International Airport (DFW), and John F. Kennedy International Airport (JFK). Based on this initial assessment, there are statistical throughput benefits for both arrivals and departures at MEM with an average of 4% for arrivals, and 6% for departures. For DFW, there is a statistical benefit for arrivals with an average of 3%. Although there is an average of 1% benefit observed for departures, it is not statistically significant. For JFK, there is a 12% benefit for arrivals, but a 2% penalty for departures. The results obtained are for current traffic volumes and should show greater benefit for increased future demand. This paper also proposes some potential TRCM algorithm improvements for future research. A continued research plan is being worked to implement these improvements and to re-assess the throughput benefit for today and future projected traffic volumes.

Phojanamongkolkij, Nipa↗