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

Performance monitor system functional simulator, environmental data, orbiter 101(HFT)

Information concerning the environment component of the space shuttle performance monitor system simulator (PMSS) and those subsystems operational on the shuttle orbiter 101 used for horizontal flight test (HFT) is provided, along with detailed data for the shuttle performance monitor system (PMS) whose software requirements evolve from three basic PMS functions: (1) fault detection and annunciation; (2) subsystem measurement management; and (3) subsystem configuration management. Information relative to the design and operation of Orbiter systems for HFT is also presented, and the functional paths are identified to the lowest level at which the crew can control the system functions. Measurement requirements are given which are necessary to adequately monitor the health status of the system. PMS process requirements, relative to the measurements which are necessary for fault detection and annunciation of a failed functional path, consist of measurement characteristics, tolerance limits, precondition tests, and correlation measurements.

Parker, F. W.↗
NASA NTRS1974

Management approach recommendations. Earth Observatory Satellite system definition study (EOS)

Management analyses and tradeoffs were performed to determine the most cost effective management approach for the Earth Observatory Satellite (EOS) Phase C/D. The basic objectives of the management approach are identified. Some of the subjects considered are as follows: (1) contract startup phase, (2) project management control system, (3) configuration management, (4) quality control and reliability engineering requirements, and (5) the parts procurement program.

Source record↗
NASA NTRS1980

Comparative thermal analysis of alternate Cryogenic Fluid Management Experiment (CFME) configurations

The Cryogenic Fluid Management Experiment (CFME) was analyzed to assess the feasibility and advisability of deleting the vapor cooled shield (VCS) from the baseline CFME insulation and pressure control system. Two alternate concepts of CFME insulation and pressure control, neither of which incorporated the VCS, were investigated. The first concept employed a thermodynamic vent system (TVS) to throttle the flow through an internal wall mounted heat exchanger (HX) within the pressure vessel to decrease boiloff and pressure rise rate, while the second concept utilized a TVS without an internal heat exchanger. Only the first concept was viable. Its performance was assessed for a seven day mission and found to be satisfactory. It was also concluded that VCS development costs would be greater than for an internal HX installation. Based upon the above comparisons, the HX was recommended as a replacement for the VCS.

Merino, F.↗
NASA NTRS1976

Mission Control Center (MCC) System Specification for the Shuttle Orbital Flight Test (OFT) Timeframe

System specifications to be used by the mission control center (MCC) for the shuttle orbital flight test (OFT) time frame were described. The three support systems discussed are the communication interface system (CIS), the data computation complex (DCC), and the display and control system (DCS), all of which may interfere with, and share processing facilities with other applications processing supporting current MCC programs. The MCC shall provide centralized control of the space shuttle OFT from launch through orbital flight, entry, and landing until the Orbiter comes to a stop on the runway. This control shall include the functions of vehicle management in the area of hardware configuration (verification), flight planning, communication and instrumentation configuration management, trajectory, software and consumables, payloads management, flight safety, and verification of test conditions/environment.

Source record↗
DOE OSTI2023

The Benefits of a Software Bill of Materials Program at Nuclear Facilities

Software supply chain attacks are becoming increasingly more prevalent in both information communications technology and operational technology environments. Often, a supplier or other entity discloses vulnerability information about software components and subcomponents used in a digital asset, but an asset owner is unable to quickly ascertain if the vulnerable component is installed in their facility. The generation and use of a software bill of materials (SBOM) for installed digital assets can enable an asset owner to quickly identify if and where a component is used, allowing them to evaluate the risk and determine necessary risk treatments. The integration of an SBOM program into a nuclear facility not only improves vulnerability management and risk management processes, it also benefits asset and configuration management, cybersecurity, and supply chain programs. This paper reviews the U.S. Department of Energy Office of Nuclear Energy Cybersecurity Crosscutting Technology Development program’s work on integrating an SBOM program into a nuclear facility. It also provides a discussion on the benefits of such a program.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
NASA NTRS2005

SQL-RAMS

SQL-RAMS (where "SQL" signifies Structured Query Language and "RAMS" signifies Rocketdyne Automated Management System) is a successor to the legacy version of RAMS a computer program used to manage all work, nonconformance, corrective action, and configuration management on rocket engines and ground support equipment at Stennis Space Center. The legacy version resided in the FileMaker Pro software system and was constructed in modules that could act as stand-alone programs. There was little or no integration among modules. Because of limitations on file-management capabilities in FileMaker Pro, and because of difficulty of integration of FileMaker Pro with other software systems for exchange of data using such industry standards as SQL, the legacy version of RAMS proved to be limited, and working to circumvent its limitations too time-consuming. In contrast, SQL-RAMS is an integrated SQL-server-based program that supports all data-exchange software industry standards. Whereas in the legacy version, it was necessary to access individual modules to gain insight to a particular work-status documents, SQL-RAMS provides access through a single-screen presentation of core modules. In addition, SQL-RAMS enable rapid and efficient filtering of displayed statuses by predefined categories and test numbers. SQL-RAMS is rich in functionality and encompasses significant improvements over the legacy system. It provides users the ability to perform many tasks which in the past required administrator intervention. Additionally many of the design limitations have been corrected allowing for a robust application that is user centric.

Alfaro, Victor O.↗
NASA NTRS2005

SQL-RAMS

SQL-RAMS (where "SQL" signifies Structured Query Language and "RAMS" signifies Rocketdyne Automated Management System) is a successor to the legacy version of RAMS -- a computer program used to manage all work, nonconformance, corrective action, and configuration management on rocket engines and ground support equipment at Stennis Space Center. The legacy version resided in the File-Maker Pro software system and was constructed in modules that could act as standalone programs. There was little or no integration among modules. Because of limitations on file-management capabilities in FileMaker Pro, and because of difficulty of integration of FileMaker Pro with other software systems for exchange of data using such industry standards as SQL, the legacy version of RAMS proved to be limited, and working to circumvent its limitations too time-consuming. In contrast, SQL-RAMS is an integrated SQL-server-based program that supports all data-exchange software industry standards. Whereas in the legacy version, it was necessary to access individual modules to gain insight into a particular workstatus document, SQL-RAMS provides access through a single-screen presentation of core modules. In addition, SQL-RAMS enables rapid and efficient filtering of displayed statuses by predefined categories and test numbers. SQL-RAMS is rich in functionality and encompasses significant improvements over the legacy system. It provides users the ability to perform many tasks, which in the past required administrator intervention. Additionally, many of the design limitations have been corrected, allowing for a robust application that is user centric.

Alfaro, Victor O.↗
NASA NTRS2004

SCDM in a Distributed Environment

The Software Configuration Management (SCM) of the Space Launch Initiative (SLI) Advanced Engineering Environment (AEE) products is performed in a distributed environment-meaning the activities performed during the project lifecycle are across numerous NASA Centers, facilities, organizations, colleges and industry. SCM is the glue that holds the project and products together-especially in a distributed environment. It identifies, controls, accounts, and verified the details of the products; the schedule of activities; the assigned responsibilities; and the required resources, including staff, tools, and computer facilities. Data/document management (DM) captures and conveys the SCM and project efforts. SCM and DM are integrally linked; hence, Software Configuration and Data Management (SCDM). This paper discusses one team's challenges in implementing SCDM in a distributed environment. The distributed nature of the project introduces new opportunities for moving SCDM to the next level of usefulness in today's high-tech development arena. The lessons learned from the implementation of distributed SCDM in support of the SLI AEE Project provide valuable information for future implementations of SCM and DM.

Crowley, Sandra L.↗
NASA NTRS2011

TPSAS-NF1676L-12441-DND

The increasing presence of airport surface surveillance technologies has spawned a strong interest in airport surface traffic management research; the vast majority has assumed that the airport’s runway configuration is known and constant. Tactical Runway Configuration Management (TRCM), one component of NASA’s System Oriented Runway Management concept, plans the airport configuration to optimize traffic efficiency for the forecast weather, traffic, and other factors. While planning runway configuration can provide benefit and is required by other automation concepts, larger benefits are possible by planning other airport configuration decisions, such as runway assignment policies, that are currently made manually by controllers. A laboratory prototype of the TRCM algorithm which selects optimal airport configuration schedules has been implemented and studied within a simulation environment. The presentation will describe simulation results for several airports, under various weather and traffic conditions. The sequence of airport configurations recommended by TRCM result in significantly less delay than the airport configurations that were actually used by controllers, illustrating both the potential benefit from airport configuration optimization and the ability of TRCM to provide effective airport configuration schedules. The application to several, distinct airports demonstrates the approach is capable of handling the differences between airports with a common algorithm, while providing decision support that respects the current procedures at those airports. Consequently, TRCM is able to be deployed to any airport within the current National Airspace System. The TRCM algorithmic approach is also extensible to future operational scenarios. NASA is in the process of transferring the initial TRCM technology to the FAA. Future research will extend the concept and algorithm to provide coordinated plans for metroplex airports and study NextGen applications.

Stephen Atkins↗
NASA NTRS2011

TPSAS-NF1676L-12263-DND

The increasing presence of airport surface surveillance technologies has spawned a strong interest in airport surface traffic management research; the vast majority has assumed that the airport’s runway configuration is known and constant. Tactical Runway Configuration Management (TRCM), one component of NASA’s System Oriented Runway Management concept, plans the airport configuration to optimize traffic efficiency for the forecast weather, traffic, and other factors. While planning runway configuration can provide benefit and is required by other automation concepts, larger benefits are possible by planning other airport configuration decisions, such as runway assignment policies, that are currently made manually by controllers. A laboratory prototype of the TRCM algorithm which selects optimal airport configuration schedules has been implemented and studied within a simulation environment. The presentation will describe simulation results for several airports, under various weather and traffic conditions. The sequence of airport configurations recommended by TRCM result in significantly less delay than the airport configurations that were actually used by controllers, illustrating both the potential benefit from airport configuration optimization and the ability of TRCM to provide effective airport configuration schedules. The application to several, distinct airports demonstrates the approach is capable of handling the differences between airports with a common algorithm, while providing decision support that respects the current procedures at those airports. Consequently, TRCM is able to be deployed to any airport within the current National Airspace System. The TRCM algorithmic approach is also extensible to future operational scenarios. NASA is in the process of transferring the initial TRCM technology to the FAA. Future research will extend the concept and algorithm to provide coordinated plans for metroplex airports and study NextGen applications.

Stephen Atkins↗
NASA NTRSDate not supplied

Predicting Airport Runway Configuration for Decision-Support Using Supervised Learning

One of the most challenging tasks for air traffic controllers is runway configuration management (RCM). It deals with the optimal selection of runways to operate on (for arrivals and departures) based on current and forecast of traffic, surface wind speed, wind direction, other environmental variables, noise constraints, and several other airport-specific factors. In this paper, a methodology using supervised learning is developed to build a predictive model for RCM decision-support from large volumes of historical data. Data from two full years (2018 and 2019) related to current and forecast weather, demand/capacity, etc. is collected, analyzed, and fused together. A variety of supervised learning algorithms are tested for predicting runway configuration and hyperparameter tuning is carried out to select the best performing model. The validation process involves two airports of low (Charlotte Douglas International Airport, CLT) and high (Denver International Airport, DEN) complexity of configuration decision-making. The results show significant promise for the two airports with test accuracy of 93% (CLT) and 73% (DEN). The methodology is scalable and generalizable to other airports across the U.S. National Airspace System.

air traffic management↗
NASA NTRSDate not supplied

Predicting Airport Runway Configurations for Decision-Support Using Supervised Learning

One of the most challenging tasks for air traffic controllers is runway configuration management (RCM). It deals with the optimal selection of runways to operate on (for arrivals and departures) based on current and forecast of traffic, surface wind speed, wind direction, other environmental variables, noise constraints, and several other airport-specific factors. In this paper, a methodology using supervised learning is developed to build a predictive model for RCM decision-support from large volumes of historical data. Data from two full years (2018 and 2019) related to current and forecast weather, demand/capacity, etc. is collected, analyzed, and fused together. A variety of supervised learning algorithms are tested for predicting runway configuration and hyperparameter tuning is carried out to select the best performing model. The validation process involves two airports of low (Charlotte Douglas International Airport, CLT) and high (Denver International Airport, DEN) complexity of configuration decision-making. The results show significant promise for the two airports with test accuracy of 93% (CLT) and 73% (DEN). The methodology is scalable and generalizable to other airports across the U.S. National Airspace System.

air traffic management↗
NASA NTRS1972

Study of solid rocket motor for space shuttle booster, Volume 3: Program acquisition planning

The program planning acquisition functions for the development of the solid propellant rocket engine for the space shuttle booster is presented. The subjects discussed are: (1) program management, (2) contracts administration, (3) systems engineering, (4) configuration management, and (5) maintenance engineering. The plans for manufacturing, testing, and operations support are included.

Source record↗
NASA NTRS1991

Heterogeneous distributed databases: A case study

Alternatives are reviewed for accessing distributed heterogeneous databases and a recommended solution is proposed. The current study is limited to the Automated Information Systems Center at the Naval Sea Combat Systems Engineering Station at Norfolk, VA. This center maintains two databases located on Digital Equipment Corporation's VAX computers running under the VMS operating system. The first data base, ICMS, resides on a VAX11/780 and has been implemented using VAX DBMS, a CODASYL based system. The second database, CSA, resides on a VAX 6460 and has been implemented using the ORACLE relational database management system (RDBMS). Both databases are used for configuration management within the U.S. Navy. Different customer bases are supported by each database. ICMS tracks U.S. Navy ships and major systems (anti-sub, sonar, etc.). Even though the major systems on ships and submarines have totally different functions, some of the equipment within the major systems are common to both ships and submarines.

Stewart, Tracy R.↗
DOE OSTI2020

Performance Potential of Mixed Data Management Modes for Heterogeneous Memory Systems

Many high-performance systems now include different types of memory devices within the same compute platform to meet strict performance and cost constraints. Such heterogeneous memory systems often include an upper-level tier with better performance, but limited capacity, and lower-level tiers with higher capacity, but less bandwidth and longer latencies for reads and writes. To utilize the different memory layers efficiently, current systems rely on hardware-directed, memory -side caching or they provide facilities in the operating system (OS) that allow applications to make their own data-tier assignments. Since these data management options each come with their own set of trade-offs, many systems also include mixed data management configurations that allow applications to employ hardware- and software-directed management simultaneously, but for different portions of their address space. Despite the opportunity to address limitations of stand-alone data management options, such mixed management modes are under-utilized in practice, and have not been evaluated in prior studies of complex memory hardware. In this work, we develop custom program profiling, configurations, and policies to study the potential of mixed data management modes to outperform hardware- or software-based management schemes alone. Our experiments, conducted on an Intel ® Knights Landing platform with high-bandwidth memory, demonstrate that the mixed data management mode achieves the same or better performance than the best stand-alone option for five memory intensive benchmark applications (run separately and in isolation), resulting in an average speedup compared to the best stand-alone policy of over 10 %, on average.

Effler, Chad↗
NASA NTRS1973

Systems performance monitoring for advanced manned spacecraft

Optimum system mechanizations for advanced manned spacecraft are considered. Several studies have proposed automation of the onboard system management task, with functions such as system status monitoring, configuration management, and redundancy management being accomplished under computer control. An experimental system was used in the laboratory to investigate hardware and software requirements for accomplishing these onboard system management functions. A performance monitor system is proposed for the space shuttle. This system provides support to the flight crew in the management of all onboard systems but does not perform critical switching functions during the flight phase.

Chambers, T. V.↗
NASA NTRS2002

PIMS-Universal Payload Information Management

As the overall manager and integrator of International Space Station (ISS) science payloads and experiments, the Payload Operations Integration Center (POIC) at Marshall Space Flight Center had a critical need to provide an information management system for exchange and management of ISS payload files as well as to coordinate ISS payload related operational changes. The POIC's information management system has a fundamental requirement to provide secure operational access not only to users physically located at the POIC, but also to provide collaborative access to remote experimenters and International Partners. The Payload Information Management System (PIMS) is a ground based electronic document configuration management and workflow system that was built to service that need. Functionally, PIMS provides the following document management related capabilities: 1. File access control, storage and retrieval from a central repository vault. 2. Collect supplemental data about files in the vault. 3. File exchange with a PMS GUI client, or any FTP connection. 4. Files placement into an FTP accessible dropbox for pickup by interfacing facilities, included files transmitted for spacecraft uplink. 5. Transmission of email messages to users notifying them of new version availability. 6. Polling of intermediate facility dropboxes for files that will automatically be processed by PIMS. 7. Provide an API that allows other POIC applications to access PIMS information. Functionally, PIMS provides the following Change Request processing capabilities: 1. Ability to create, view, manipulate, and query information about Operations Change Requests (OCRs). 2. Provides an adaptable workflow approval of OCRs with routing through developers, facility leads, POIC leads, reviewers, and implementers. Email messages can be sent to users either involving them in the workflow process or simply notifying them of OCR approval progress. All PIMS document management and OCR workflow controls are coordinated through and routed to individual user's "to do" list tasks. A user is given a task when it is their turn to perform some action relating to the approval of the Document or OCR. The user's available actions are restricted to only functions available for the assigned task. Certain actions, such as review or action implementation by non-PIMS users, can also be coordinated through automated emails.

Elmore, Ralph↗