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 19 records

Document Management: A Focused Analysis on the Configuration Management Process at Y-12 National Security Complex

The configuration management process at Y-12 is a crucial process to ensure safe operations and compliance with Department of Energy (DOE) regulations and requirements. This process is evaluated utilizing systems-thinking methodology in order to understand the current operational flow, with the ultimate goal of building an easily understandable, representative model. This model offers insights on key areas of waste and provides a potential solution by modernizing rate limiting steps: a software implementation to update the traditional document management system and make it paperless. Stakeholders of the software implementation are identified in order to define characteristic requirements of an effective product and the anticipated benefit is evaluated. Ultimately, this project is an effort to increase the quality of life for all stakeholders, while improving the capacity, throughput, and effectiveness of a necessary process at Y-12.

42 ENGINEERING↗

Document Configuration Management (DCM) Team Weapon Product Definition Group

Document Configuration Management (DCM) is the ongoing process of identifying and managing changes to deliverables and other work products. ALDW’s Document Configuration Plan provides a systematic, standardized process for the configuration management of documents to ensure that the most current and/or appropriate documents are being used, that any canceled or superseded document is properly processed, and that both a clear history and traceability of previous revisions are available.

99 GENERAL AND MISCELLANEOUS↗

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↗

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↗

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↗

The ERSDT Software Quality Assurance Plan Practices and Development Environment Setup for RASCAL 5

This document includes the information pertaining to the practices of the Emergency Response Software Development Team (ERSDT) for the RASCAL software project. The content includes information regarding: 1) Software Quality Assurance. 2) Project Management. 3) Configuration Management. 4) Development Standards. 5) Third-Party Software. 6) Verification and Validation. The information contained in this report is considered living documentation. The information contained in this report was assembled from multiple documents and content management systems.

97 MATHEMATICS AND COMPUTING↗

MiniDAQ-3: Providing concurrent independent subdetector data-taking on CMS production DAQ resources

The data acquisition (DAQ) of the Compact Muon Solenoid (CMS) experiment at CERN, collects data for events accepted by the Level-1 Trigger from the different detector systems and assembles them in an event builder prior to making them available for further selection in the High Level Trigger, and finally storing the selected events for offline analysis. In addition to the central DAQ providing global acquisition functionality, several separate, so-called “MiniDAQ” setups allow operating independent data acquisition runs using an arbitrary subset of the CMS subdetectors. During Run 2 of the LHC, MiniDAQ setups were running their event builder and High Level Trigger applications on dedicated resources, separate from those used for the central DAQ. This cleanly separated MiniDAQ setups from the central DAQ system, but also meant limited throughput and a fixed number of possible MiniDAQ setups. In Run 3, MiniDAQ-3 setups share production resources with the new central DAQ system, allowing each setup to operate at the maximum Level-1 rate thanks to the reuse of the resources and network bandwidth. Configuration management tools had to be significantly extended to support the synchronization of the DAQ configurations needed for the various setups. We report on the new configuration management features and on the first year of operational experience with the new MiniDAQ-3 system.

Amoiridis, Vassileios↗

Towards Software Bill of Materials in the Nuclear Industry

Large, modern industrial facilities often incorporate thousands of digital assets in their operational technology. Regulated facilities, such as nuclear power plants (NPPs), maintain robust cybersecurity and configuration management programs that often use bills of materials (BOMs) for these assets, including make, model, and version of hardware, firmware, and software. However, these BOMs typically capture only first- or second-tier information provided by the original equipment manufacturer (OEM). Unfortunately, as indicated by the increasing number and sophistication of software supply chain attacks, this level of detail is insufficient for identifying all the potential vulnerabilities and risks in software applications. Software BOMs (SBOMs) provide detailed enumeration of components and dependencies within the product or devices, including firmware. SBOMs can be combined with vulnerability data sources and vendor vulnerability attestations to improve vulnerability management and enable rapid identification of affected components when new software vulnerabilities are discovered. Ideally, SBOMs are created by the OEM prior to installation. However, since this practice is not yet commonplace and since NPPs are typically slow to adopt new technology, most NPPs do not incorporate SBOMs into their asset or configuration management programs. Fortunately, SBOMs can be generated by NPPs on existing digital assets to provide further insight into risk management decisions. This report provides an overview of the current SBOM ecosystem and recommends guidance on how to get started in a “crawl, walk, run” manner to develop and implement a sustainable SBOM program for digital assets in an NPP.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

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↗

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↗

A Probabilistic Approach To Selecting Build Configurations in Package Managers

In the past decade software has grown significantly in complexity and scale. Likewise the number of dependencies for most software has increased with typical software packages depending on tens to hundreds of other packages. Such large numbers of dependencies place a significant burden on package managers to correctly maintain dependency lists and constraints between them. Due to this package managers have incorporated sophisticated tooling such as SAT solvers into their dependency management mechanisms. Despite these tools package managers still rely on many human annotated constraints for dependency and version selection. These are error-prone and require a significant amount of labor to constantly update and test. In this paper we propose a methodology to make use of historical build results in selecting the version for package dependencies. Our method utilizes the flexibility of the Spack package manager’s heavily parameterized package configurations to incorporate a machine learning model trained to predict the probability of build outcomes. This work is able to build and install packages with a 13% higher success rate than the default version selection mechanism in Spack.

97 MATHEMATICS AND COMPUTING↗

NLIT 2022 Axonius Presentation

Axonius, a cybersecurity asset management tool used at INL, provides visibility into users, devices, software, and hardware in use at the lab. This visibility, provided by aggregating data on lab entities from many tools' perspectives, makes incident response, configuration management, and IT operations more capable.

42 ENGINEERING↗

Performance analysis of hybrid power configurations: Impact on primary energy intensity, carbon dioxide emissions, and life cycle costs

In this work, utilization of Natural gas and Hydrogen to support current and future building energy needs to offset the total electric demand while improving the grid resiliency and energy efficiency was investigated. Demand side energy management will play an important role in efficiently managing the available energy resources. Performance assessment of different power generation and energy management configurations is presented in this paper. Development of solutions in addressing grid resiliency by providing the ability to design suitable configurations for meeting individual building energy needs is discussed. Primary movers (PM) such as internal combustion engines (ICE) and fuel cells (FC) along with small scale auxiliary renewable energy source such as photovoltaics (PV) were considered. Key attributes of total carbon foot-print, life cycle costs including capital and operational expenditure, electric grid offset or peak shaving capability, thermal energy availability and its further potential to offset total electric demand, and primary energy intensity are analyzed and discussed in detail.

08 HYDROGEN↗