Search NASA⌕ Search

SEARCH · Search NASA

Results for “COMPUTER PROGRAM DOCUMENTATION”

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 451 records · Page 25
All sourcesNASA NTRSDOE OSTI
DOE OSTI2019

Integrated Simulation Capabilities for Analysis of Experiments in the Versatile Test Reactor

The DOE-initiated Versatile Test Reactor (VTR) program aims to establish a domestic fast-neutron irradiation testing capability that meets a variety of domestic and international nuclear energy needs. Currently, integrated tools capable of mechanistic modeling of VTR and a test vehicle do not exist. To address this modeling and analysis deficiency, Argonne's SAS4A/SYSSYS-1 safety analysis code has been coupled with SAM (System Analysis Module) to provide a novel modeling capability that supports VTR and other fast test facilities. This report documents the design, implementation, and testing of this integrated capability. A coupling boundary has been identified at the test vehicle and primary coolant interface, where SAS4A/SASSYS-1 treats primary coolant thermal hydraulics outside the test vehicle, while SAM treats all thermal hydraulic behavior within the test vehicle, including the vehicle walls. Essential to this integrated tool is its newly developed capability to properly model the conjugate heat transfer process which ensures equality of temperatures and heat fluxes at the vehicle wall interface while ensuring energy conservation. A range of testing has been completed to support demonstration of this interface. The testing scope includes steady-state verification using a series of increasingly complex analytical solutions and transient demonstration for a range of design basis accident scenarios using prototypic VTR and test vehicle (i.e. cartridge loop) configurations. Results of this testing confirm verification of the steady-state solutions and provide reasonable and expected transient behavior. The coupling interface has been developed to be robust yet flexible. The implementation within SAS4A/SASSYS-1 supports coupling to any external software or module. The use of decomposed domains and the existing in-core thermal-hydraulic calculational framework within SAS4A/SASSYS-1 enable treatment of arbitrary test vehicle geometries with nonuniform meshing between SAS4A/SASSYS-1 and the coupled code. Modeling of multiple test locations is also supported. Furthermore, computational efficiency is enhanced by utilizing named pipes (or FIFOs), an interface for interprocess communication (IPC).

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
DOE OSTI2019

Augmented Reality for Managing Nuclear Infrastructure and Operations - 19605

Emerging augmented reality tools offer great promise for helping manage nuclear infrastructure throughout its life cycle. These tools have the ability to provide operators with actionable holographic information as they work. Perhaps more excitingly these tools also feature sensors that provide the ability to document work at very high spatial resolution. These sensors include onboard cameras as well as active infrared sensors that can capture 3D geometry information on-the-fly. Coupling the visualization and sensing tools provided by augmented reality headsets with computational intelligence opens up many exciting new possibilities for managing nuclear infrastructure throughout its life cycle. In this presentation we show a number of examples of how augmented reality tools can be incorporated into the management of nuclear infrastructure. We show examples of using augmented reality as a human-machine interface for robotic control, and we show examples of augmented reality being interfaced with external sensors. Finally, we show how these sensing and visualization capabilities of augmented reality can be interfaced with intelligent algorithms to help operators perform their work in nuclear facilities. The goal of the work is to spark discussions on how emerging augmented reality tools can help enable the next generation of efficient, high-performance nuclear infrastructure. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
DOE OSTI2021

Application of Point Precipitation Frequency Estimates to Watersheds

This report documents work sponsored by the U.S. Nuclear Regulatory Commission (NRC) at the Oak Ridge National Laboratory (ORNL) as part of the RES project, “Application of Point Precipitation Frequency Estimates to Watersheds.” This project was implemented as part of the Probabilistic Flood Hazard Assessment (PFHA) Research Program. The objective of the PFHA Research Program is to develop tools and guidance on the use of PFHA methods to risk-inform NRC’s licensing of new facilities as well as licensing and oversight of currently operating facilities as they relate to flooding hazards. Many nuclear power plants (NPPs) are located on or near rivers so riverine flooding hazards need to be considered in their design and operation. Probabilistic riverine flood models are important tools for realistic assessment of flooding risks. However, these models require areal estimates of the depth, duration, and frequency of rainfall distributed over the watershed, which are not often available. Point precipitation frequency estimates are more widely available. For example, the National Oceanic and Atmospheric Administration (NOAA) has published NOAA Atlas 14, which provides point precipitation frequency estimates for 5-minute through 60-day durations at average recurrence intervals of 1-year through 1,000-year. The research documented in this report addresses areal reduction factors (ARFs), which can be used to convert the widely available point precipitation frequency estimates, to estimates of areal precipitation frequency over a watershed. The most widely used ARF source is Technical Paper 29 (TP-29) published by the then U.S. Weather Bureau in 1958. However, both the methods and the underlying precipitation data used to produce TP-29 are seriously out of date. For example, due to the small gauge network available at the time of TP-29’s compilation, ARF estimates developed are only for watersheds smaller than about 400 square miles. Due to the relatively short record lengths of precipitation data available, frequency considerations could not be accurately determined. Other factors such as regional climate and seasonality were not addressed. Several newer methods have been published since TP-29 was developed and both the type and quantity of precipitation data have increased significantly, along with computational resources and analytical tools such as geographic information systems. This report reviewed and assessed the available precipitation products and methods for conducting ARF analysis. The work applied up-to-date precipitation data products and analysis methods with a novel watershed-based approach to investigate how ARF estimates vary across different methods, data sources, geographical locations, return periods, and seasons. The overall findings reported here regarding basic ARF trends are in line with other recent studies showing that ARFs decrease with increasing area, increase with increasing duration, and decrease with increasing return period. This study found significant differences among the available ARF methods. This work also found a strong geographical variability across different US hydrologic regions, suggesting that the ARF are specific to regional climate patterns and geographical characteristics and should not be applied arbitrarily to other locations. The results also reveal the importance of data record length, especially for high return level ARFs. The work reported in NUREG/CR-7271 will assist NRC staff in assessing different classes of ARF methods in conjunction with available rainfall data sets. It will also support the development of guidance for application of point precipitation data in PFHAs. It should be noted that the ARF values presented in this report for any location or region were developed for the purposes of comparing methods and investigating the factors that influence ARFs. They should not be considered official and should not be used in leu of a site-specific analysis.

54 ENVIRONMENTAL SCIENCES↗
DOE OSTI2022

Precursor Analysis Report: Doppelpaymer Ransomware Attack on Petroleos Mexicanos (PEMEX) 2019

The DoppelPaymer Ransomware Attack on Petroleos Mexicanos (PEMEX) 2019 Precursor Analysis Report leverages publicly available information about the PEMEX cyber attack and catalogs anomalous observables for each technique employed in the attack. This analysis is based upon the methodology of the Cybersecurity for the Operational Technology Environment (CyOTE) program. The 2019 DoppelPaymer ransomware attack on PEMEX, Mexico’s nationalized petroleum corporation, highlights a unique threat that ransomware and cybercriminal extortion poses to Operational Technology (OT) environments in critical infrastructure. The incident began with an employee downloading commodity malware that allowed adversaries to gain initial access to PEMEX’s enterprise environment. After conducting privilege escalation, tool ingress, and data exfiltration, the adversaries deployed DoppelPaymer ransomware throughout the PEMEX enterprise environment, resulting in the company having to take dozens of systems offline for at least several days. Although PEMEX stated that their operations were not affected, the data exfiltrated from PEMEX was made available for download on DoppelPaymer’s leak site, as well as on other illicit criminal forums. This stolen data included not only company information, but also sensitive OT-specific configuration data. This incident showcases how cybercriminal exfiltration and posting of sensitive OT architecture documentation can pose security concerns for the targeted organization for years due to the long lifespan of OT assets and architectures. Researchers and analysts identified 18 unique techniques utilized during the attack with a total of 190 observables using MITRE ATT&CK® for Industrial Control Systems. The CyOTE program assesses observables accompanying techniques used prior to the triggering event to identify opportunities to detect malicious activity. If observables accompanying the attack techniques are perceived and investigated prior to the triggering event, earlier comprehension of malicious activity can take place. Fifteen of the identified techniques used during the DoppelPaymer ransomware attack were precursors to the triggering event. Analysis identified 163 observables associated with these precursor techniques, 34 of which were assessed to have an increased likelihood of being perceived in the 60 days preceding the triggering event. The response and comprehension time could have been reduced if the observables had been identified earlier. The information gathered in this report contributes to a library of observables tied to a repository of artifacts, data sources, and technique detection references for practitioners and developers to support the comprehension of indicators of attack. Asset owners and operators can use these products if they experience similar observables or to prepare for comparable scenarios.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗
DOE OSTI2025

University Data Management Pilot Utilizing the Nuclear Research Data System

Background In 2022, the Office of Science and Technology Policy (OSTP) issued a memo that significantly reshaped the landscape of access to federally funded research. The memo mandated that all taxpayer-funded research be made available to the public without delay upon publication, without an embargo period, superseding the 2013 OSTP public access policy. This public access policy promotes transparency and the democratization of knowledge, ensuring that the fruits of scientific endeavors funded by federal agencies could be immediately accessed and built upon by scientists, educators, students, and the public at large. To implement the requirements of the OSTP guidance and DOE Public Access Plan, the Office of Nuclear Energy (NE) has implemented public access plan guidance and has identified several areas where better data management practices would further expand public access to important nuclear energy related scientific data, reports, and other technical products. Significant NE supported efforts are already underway for data management and public access to important nuclear energy related data.1 2 To address gaps in data management practices, and improve retention and accessibility of data, NE is actively exploring enhanced data management options utilizing its high-performance computing resources administered by its Nuclear Scientific User Facility Program. A newly piloted system, the Nuclear Research Data System (NRDS) acts as a portal for data collection and dissemination. Nuclear Energy University Program Research and Development Portfolio According to Web of Science, NEUP has produced 2,345 journal publication that have been cited more than 61,000 times3 and countless conference proceedings. These publications are publicly available through OSTI.gov and in the open literature. Additional scientific and technical products including project milestones that are not publications and NEUP project final reports are vetted through OSTI.gov and released once reviewed and approved by DOE. Since 2009, NEUP has awarded close to 1,000 different R&D projects in technical areas across the NE research programs. As of June 2023, 512 NEUP reports are publicly available on OSTI. The underlying data for projects is still held at universities, and data transfer, co-location, and dissemination has not occurred in a systematic way. NEUP data is currently accessible through myriad university-based data repositories, or through direct requests to PIs. The program identified this patchwork of repositories, or often lack of publicly available data, as a significant barrier to an organized, accessible, and comprehensive solution to sharing data with the larger nuclear energy community. Approach The goal of this pilot project is to establish a pathway to a consolidated long-term repository for NEUP project data. To accomplish this goal, the pilot strives to accomplish the following objectives: Establish data collection standards, including a standard set of required supplementary information to contextualize and support raw data files. Work with the HPC group collect and upload information and to modify the NRDS system, as needed, to support a standardized approach. Resolve potential barriers to successful roll out of an expanded data collection strategy, including modifying data management plan guidelines and establishing a document and data release process that accounts for potential intellectual property and/or export control concerns. Results Overall, the pilot was successful in collecting 8,982 raw and processes data files, 220 reports, 56 calibration files, and 5,931 other supplementary documents. Supplementary documents included experimental plans, methods, journal publications and conference proceedings, milestone reports, and final reports. Figure 2 shows the number of data sets and supplementary project information provided by each project. Projects has significantly different input, depending on experimental data produced and completeness of the datasets provided.

Data collection↗
DOE OSTI2016

Contingency Contractor Optimization Phase 3 Sustainment Platform Requirements - Contingency Contractor Optimization Tool - Prototype

Sandia National Laboratories (Sandia) is in Phase 3 Sustainment of development of a prototype tool, currently referred to as the Contingency Contractor Optimization Tool - Prototype (CCOTP), under the direction of OSD Program Support. CCOT-P is intended to help provide senior Department of Defense (DoD) leaders with comprehensive insight into the global availability, readiness and capabilities of the Total Force Mix. The CCOT-P will allow senior decision makers to quickly and accurately assess the impacts, risks and mitigating strategies for proposed changes to force/capabilities assignments, apportionments and allocations options, focusing specifically on contingency contractor planning. During Phase 2 of the program, conducted during fiscal year 2012, Sandia developed an electronic storyboard prototype of the Contingency Contractor Optimization Tool that can be used for communication with senior decision makers and other Operational Contract Support (OCS) stakeholders. Phase 3 used feedback from demonstrations of the electronic storyboard prototype to develop an engineering prototype for planners to evaluate. Sandia worked with the DoD and Joint Chiefs of Staff strategic planning community to get feedback and input to ensure that the engineering prototype was developed to closely align with future planning needs. The intended deployment environment was also a key consideration as this prototype was developed. Initial release of the engineering prototype was done on servers at Sandia in the middle of Phase 3. In 2013, the tool was installed on a production pilot server managed by the OUSD(AT&L) eBusiness Center. The purpose of this document is to specify the CCOT-P engineering prototype platform requirements as of May 2016. Sandia developed the CCOT-P engineering prototype using common technologies to minimize the likelihood of deployment issues. CCOT-P engineering prototype was architected and designed to be as independent as possible of the major deployment components such as the server hardware, the server operating system, the database, and the web server. This document describes the platform requirements, the architecture, and the implementation details of the CCOT-P engineering prototype.

42 ENGINEERING↗
DOE OSTI2022

Development and Demonstration of a Fuel-Efficient, Class 8 Tractor & Trailer Engine System (SuperTruck II)

Navistar presents the SuperTruck II (ST II) Final Report to the Unites States Department of Energy (US DOE), which covers the five Budget Periods (BPs) from 10-1-2016 through 6-30-2022. For ST II, Navistar built on the achievements of the SuperTruck I (ST I) Program as a catalyst to continue critical research, design and development, testing, and operations to reach the ambitious goals of the ST II project. This approach allowed Navistar to continue contributing to the essential needs of our nation for safe, efficient, and cost-effective delivery of goods and services, as we reduced negative environmental effects and improved operational productivity. This document contains information specified in DOE F 4600.2, Final Scientific/Technical Report DOE F 241.3, B. SCIENTIFIC/TECHNICAL REPORTS, explaining how we met and exceeded program requirements. Throughout this Final Report, Navistar extracted information from documents prepared during the project that represent our management, design and development, building, and testing efforts to meet and exceed SuperTruck II project goals. Navistar followed Plan requirements to achieve / exceed Project Objectives: a) >100% improvement in vehicle freight efficiency (FE) (on ton-MPG basis) relative to 2009 baseline with stretch goal of 140% improvement [actual: 170%); b) >55% engine brake thermal efficiency (BTE) demonstrated in operational engine at a 65-mph cruise point on a dynamometer – ≥31% increase from 2009 baseline [actual: 55.20% of combined BTE) ; and c) development and implementation of commercially cost effective technologies (in terms of a simple payback). Technology selection / development path focused on developing technologies applicable for production within 3-year approach, while ensuring technology readiness and cost of ownership for end users. The Program was organized into five budget periods: Requirements / Technology Assessment and Initial Hardware Testing; Technology Development and Concept Readiness Demonstration; Technology Finalization and Validation Tractor / Trailer Fabrication, Integration and Commissioning Demonstration; and Fuel Economy (FE) and Brake Thermal Efficiency (BTE) and Program Completion. Leadership was provided by DOE, with tasks performed by laboratories (Argonne National Laboratory, Lawrence Livermore National Laboratory); partners at Bosch, TPI, Dana, and J.B. Hunt; , and support from University of Michigan and Clemson University. Navistar lead this team with Principal Investigator / Contracting Officer; Project Manager (PM); Vehicle, Engine, and Aftertreatment Engineers; Finance Manager, Technical Program Leads, and Legal/IP; and other key personnel. Work also included personnel in risk management; funding / budget / finance. Work involved analysis, development, testing, and down selection of individual/system engine, aftertreatment, and vehicle technologies, with integration of selected technologies into a prototype vehicle for demonstration of fuel-efficiency gain. Work also included component/integrated system level development of truck and trailer aerodynamics, base engine efficiency, advanced aftertreatment, combustion efficiency, waste heat recovery, hybrid powertrain, reduced rolling resistance, weight reduction, idle reduction, and driver feedback. As ST II progressed, Navistar performed computer-based modeling / simulations of technologies focused on the primary operational areas: Engine, Aftertreatment, and Vehicle. During the ST II Program, the COVID Virus outbreak unexpectedly challenged by the effects of, which affected staffing, scheduling, design, supplies, availability of materials, production procedures, and testing. The DOE responded by extending the program by three quarters to ensure that project tasks were completed for this vital project. Focus continued on analyzing, developing, testing, and down selecting individual-/system-level engine and vehicle technologies for integration of the final selected technologies into a prototype vehicle that would demonstrate fuel-efficiency gains made possible through these technologies. This included component/integrated system-level development of truck and trailer aerodynamics, base engine efficiency, advanced aftertreatment, combustion efficiency, waste heat recovery, solar power, distributed and intelligent vehicle power, hybrid powertrain, reduced rolling resistance, weight reduction, idle reduction, and driver feedback. Throughout the program, function, reliability, and performance at all levels were ensured through testing. Proof of this approach was demonstrated in multiple, on-road demonstrations: Scenario A (Flatland) Fuel Economy, Scenario B (Hilly) Fuel Economy, and City Cycle Tests. Other benefits derived from ST II included new/improved products, publications, patents, and next-step capabilities related to electric/hydrogen vehicles and autonomous driving.

Zukouski, Russ↗
DOE OSTI2026

Best practices in software development for robust and reproducible geoscientific models based on insights from the Global Carbon Budget's dynamic vegetation models

Computational models play an increasingly vital role in scientific research by enabling the numerical simulation of complex processes. Such models are also fundamental in geosciences. For instance, they offer critical insights into the impacts of global change on the Earth system today and in the future. Beyond their value as research tools, models are also software products and should therefore adhere to certain established software engineering standards. However, scientists are rarely trained as software developers, which can lead to potential deficiencies in software quality like unreadable, inefficient, or erroneous code. The complexity of models, coupled with their integration into broader workflows, also often makes it challenging to reproduce results, evaluate processes, and build upon them. In this paper, we review the state and current practices of the development processes of the state-of-the-art land surface models used by the Global Carbon Budget. We combine the experience of modelers from the respective research groups with the expertise of software engineers from tech companies to outline key principles and tools for improving software quality in research. We explore four main areas: (1) model testing and validation, (2) scientific, technical, and user documentation, (3) version control, continuous integration, and code review, and (4) the portability and reproducibility of workflows. Our review reveals that while modeling communities are incorporating many best practices, significant room for improvement remains in areas such as automated testing, automated documentation, and reproducibility. Therefore, we here identify and promote essential software engineering practices, including numerous examples of practices from within the community that can serve as guidelines for other models and could help streamline processes across the entire community. We conclude with an open-source example implementation of these principles, demonstrating portable and reproducible data flows, a continuous integration setup, and web-based visualizations. This example may serve as a practical resource for model developers, users, and all scientists engaged in scientific programming.

Gregor, Konstantin [Technical Univ. of Munich (Ger↗
DOE OSTI2019

Methodology Development for Cybersecurity Robustness and Vulnerability Assessment of University Research Reactors

In 2012, the U.S. Nuclear Regulatory Commission (NRC) formed a working group in collaboration with the Test, Research and Training Reactors (TRTR) group to review cyber security programs at US nuclear nonpower reactor (NPR) facilities. Following their review of cyber security at four different university NPR (i.e. university research reactor (URR)) facilities, the NRC staff made recommendations for improvements at URR including 1) augmenting the URR licensees’ understanding of the protective features provided with their physical security systems, 2) educating URR facility staff on cyber security issues, and 3) developing guidance to help the URR facilities maintain adequate cyber security going forward. This three-year project to develop and implement a cyber-security risk assessment methodology and defense-in-depth mitigation strategy for application at URR facilities provides solutions effectively addressing each of the recommendations given in the NRC review referenced above. In support of this project, cyber security documentation and guidance from the NRC, Department of Homeland Security (DHS) Industrial Control Systems (ICS) Cyber Emergency Response Team (CERT), National Institute of Standards and Technology (NIST), and the International Atomic Energy Agency (IAEA), were reviewed. Most of this documentation did not take the unique resources, configuration, and infrastructure associated with URR facilities into account. The NRC-TRTR effective practices document provides useful guidance for implementing cyber security protections at URR, but lacks a structured framework for systematically auditing facility digital control assets (DCA) and evaluating associated cyber threats, vulnerabilities, and risk. The outcomes from this project, therefore, seek to build on the general resources above by providing a straightforward DCA auditing and risk assessment methodology, as well as mitigation strategies, that may be implemented to address the risk of cyber-attack at URR facilities.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2021

Exploring Explicit Uncertainty for Binary Analysis (EUBA)

Reverse engineering (RE) analysts struggle to address critical questions about the safety of binary code accurately and promptly, and their supporting program analysis tools are simply wrong sometimes. The analysis tools have to approximate in order to provide any information at all, but this means that they introduce uncertainty into their results. And those uncertainties chain from analysis to analysis. We hypothesize that exposing sources, impacts, and control of uncertainty to human binary analysts will allow the analysts to approach their hardest problems with high-powered analytic techniques that they know when to trust. Combining expertise in binary analysis algorithms, human cognition, uncertainty quantification, verification and validation, and visualization, we pursue research that should benefit binary software analysis efforts across the board. We find a strong analogy between RE and exploratory data analysis (EDA); we begin to characterize sources and types of uncertainty found in practice in RE (both in the process and in supporting analyses); we explore a domain-specific focus on uncertainty in pointer analysis, showing that more precise models do help analysts answer small information flow questions faster and more accurately; and we test a general population with domain-general sudoku problems, showing that adding "knobs" to an analysis does not significantly slow down performance. This document describes our explorations in uncertainty in binary analysis.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2022

ARM data-oriented metrics and diagnostics package for climate model evaluation (ARM-DIAGS-V3) version 3

A Python-based metrics and diagnostics package is currently being developed by the ARM Infrastructure Team at Lawrence Livermore National Laboratory to facilitate the use of long-term high frequency measurements from the ARM program in evaluating the regional climate simulation of clouds, radiation, precipitation, and aerosols. This metrics and diagnostics package computes climatological means of targeted climate model simulation and generates tables and plots for comparing the model simulation with ARM observational data. The CMIP model data sets are also included in the package to enable model inter-comparison as demonstrated in Zhang et al. (2018) and Zhang et al. (2020). The mean of the CMIP model can be served as a reference for individual models. Basic performance metrics are computed to measure the accuracy of mean state and variability of climate models. The evaluated physical quantities include cloud fraction, temperature, relative humidity, cloud liquid water path, total column water vapor, precipitation, sensible and latent heat fluxes, aerosol optical depth, and radiative fluxes, with plan to extend to more fields, such as the evaluation of model simulated aerosol physicochemical properties and cloud microphysics properties. Process-oriented diagnostics focusing on aerosol, cloud, and precipitation-related phenomena are also being developed for the evaluation and development of specific model physical parameterizations. In addition to the Southern Great Plains (SGP), North Slope of Alaska (NSA) and Tropical Western Pacific (TWP) atmospheric observatories in the ARMDIAGS version 2.0, the version 3.0 package have extended to the data collected at the ARM Eastern North Atlantic (ENA) atmospheric observatory and the Observation and Modeling of the Green Ocean Amazon (GOAMAZON) field campaign. The metrics and diagnostics package are currently built upon standard Python libraries and additional Python packages developed by DOE (CDAT). The ARM metrics and diagnostic package is available publicly with the hope that it can serve as an easy entry point for climate modelers to compare their models with ARM data. In this report, we first provide an overview of major metrics in section 2. The input data, which constitutes the core content of the metrics and diagnostics package, is summarized in section 3. A user's guide documenting the workflow/structure of the version 3.0 codes and including step-by-step instruction for running the package is described in section 4.

54 ENVIRONMENTAL SCIENCES↗
DOE OSTI2016

SU-G-TeP4-06: An Integrated Application for Radiation Therapy Treatment Plan Directives, Management, and Reporting

Purpose: With electronic medical records, patient information for the treatment planning process has become disseminated across multiple applications with limited quality control and many associated failure modes. We present the development of a single application with a centralized database to manage the planning process. Methods: The system was designed to replace current functionalities of (i) static directives representing the physician intent for the prescription and planning goals, localization information for delivery, and other information, (ii) planning objective reports, (iii) localization and image guidance documents and (iv) the official radiation therapy prescription in the medical record. Using the Eclipse Scripting Application Programming Interface, a plug-in script with an associated domain-specific SQL Server database was created to manage the information in (i)–(iv). The system’s user interface and database were designed by a team of physicians, clinical physicists, database experts, and software engineers to ensure usability and robustness for clinical use. Results: The resulting system has been fully integrated within the TPS via a custom script and database. Planning scenario templates, version control, approvals, and logic-based quality control allow this system to fully track and document the planning process as well as physician approval of tradeoffs while improving the consistency of the data. Multiple plans and prescriptions are supported along with non-traditional dose objectives and evaluation such as biologically corrected models, composite dose limits, and management of localization goals. User-specific custom views were developed for the attending physician review, physicist plan checks, treating therapists, and peer review in chart rounds. Conclusion: A method was developed to maintain cohesive information throughout the planning process within one integrated system by using a custom treatment planning management application that interfaces directly with the TPS. Future work includes quantifying the improvements in quality, safety and efficiency that are possible with the routine clinical use of this system. Supported in part by NIH-P01-CA-059827.

60 APPLIED LIFE SCIENCES↗
DOE OSTI2018

Argonne Reactor Code Software Verification and Validation Plan for the Versatile Test Reactor

This Argonne Reactor Code (ARC) software has taken a pivotal role in the design work of the Versatile Test Reactor. The ARC software itself consists of several independent or semiindependent pieces of software that are used in concert to carry out specific analysis and design objectives. In this report, we discuss the validation that is needed for the ARC software overall and discuss available, usable experimental data and how it relates to the VTR project. We also discuss the verification that is required for the ARC software with respect to its usage in the VTR project and give some concrete examples as to what it must accomplish. A list of goals for the verification and validation work are presented as the general procedure that will be implemented for every individual piece of software in ARC. The ARC software has been continuously developed for over 50 years and many of the features used for the VTR project have thus been rigorously tested for accuracy during that timeframe. The ARC software is presently under source code control and undergoes nightly regression testing of not only the individual pieces, but the interconnected aspects that are common to most analysis projects. Its greatest weakness, from a software verification and validation perspective, is both a lack of documentation and outdated documentation. As an example, much of the previous validation work will require contemporary effort to re-evaluate given the updated base data libraries and modifications to the software that have occurred since. This requires new documentation to be produced to support the usage of the software in the VTR project. The bulk of the ARC software is focused on steady state neutronics and TH behavior of a reactor system. In this regard, we have identified the ZPPR, FFTF, and EBR-II programs as the best candidates for sources of validation data for the VTR project. The ZPPR-15 series in the ZPPR program was chosen as it is the best representation of the VTR fuel form and reactor core layout of all of the ZPPR measurements. Additional support for it comes from the fact that most of the data has already been processed into usable ARC models for VTR validation. The FFTF and EBR-II reactors were both functional reactors that provide reactor scale measurements. FFTF is clearly a closer match to VTR and its startup measurements would be a very valuable validation basis. EBR-II has invaluable burnup related measurements that will play a key role in the ARC software validation work. Each piece of ARC software will require a report detailing the software verification. The validation work will be logically split into the results of modeling each identified experimental resource (ZPPR, EBR-II, FFTF). The intended timeline for the VTR project is to have the ARC software verified and validated by the end of fiscal year 2020. This is incumbent on sufficient funding allocated to V&V activities and no change in programmatic priorities.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
DOE OSTI2021

IER-539 CED-1: Preliminary Design of a New Horizontal Split Table

This report presents the preliminary design (CED-1) of IER-539, focused on a new Horizontal Split Table (HST) critical assembly machine. The Department of Energy (DOE) National Nuclear Criticality Safety Program (NCSP) funds critical experiment R&D and its Mission and Vision document identifies a long-standing technical gap of a general purpose HST. HSTs have historically been used for experiments that are impractical to assemble on a vertical lift machine (VLM), usually due to their large physical size or weight. While many HSTs were historically employed in the US (including at LLNL), there are currently no surviving HSTs in the US. While there are two critical experiments facilities remaining in the US, the National Critical Experiments Research Center (NCERC) operated by LANL and the Critical Experiments Facility (CX) operated by SNL, these facilities are not equipped with a general purpose HST. There are a number of experiment designs that require an HST, including needs for Defense Programs and Nuclear Energy. Lack of an HST constraints the national ability to perform large and heavy experiments. Large footprints are needed to successfully create mockup experiments for advanced reactors (mock-up cold critical reactor cores, which is a urgent need for new reactor designs using novel materials and longer cycle lengths), to create solution experiments in lattices, or to test nuclear data of heavy metals. A new HST is a vital piece of criticality experiment infrastructure that would allow for the conduct of integral critical experiments to address needs in the nuclear criticality safety, nuclear data, and other DOE stakeholder communities.

42 ENGINEERING↗
DOE OSTI2020

Facility Cybersecurity Framework Best Practices

Federal facilities are increasingly adopting automation and connecting to the Internet creating an energy-internet-of-things environment that converges operational technology (OT) and information technology (IT). Today's buildings increasingly weave together networked sensors and cyber and physical systems that enable data to be collected, aggregated, exchanged, stored and monetized in new ways. Building technological advances have created new energy technology, services, markets and value creation opportunities (e.g. transactive energy, two-way grid communications, machine learning, and increased use of renewable and distributed energy resources). But as larger data sets are being exchanged at faster speeds between an increasing number of OT systems, it becomes more difficult to protect the security of the data lifecycle and the physical equipment it interacts with. These challenges are especially difficult to overcome because the economic and environmental gain (interoperability, big data, social networks and ubiquitous information sharing) are driving these prominent trends in the digital age. Often cybersecurity is an afterthought. The U.S. Department of Energy’s (DOE) Federal Energy Management Program (FEMP) funded the Pacific Northwest National Laboratory (PNNL) to develop various cybersecurity tools, trainings, and reports to aid federal facility managers – and other building owners and operators – in better applying frameworks and lessons learned from the National Institute of Standards and Technology (NIST) Cybersecurity Framework (CSF), risk management framework (RMF), DOE’s cybersecurity capability maturity model (C2M2), and a wide variety of industry best practices and guidance documents (i.e., NIST 800 series, Department of Defense United Facilities Criteria). This set of tools, collectively known as the FEMP Facility-Related Control System Cyber Toolkit (FRCS Cyber Toolkit)2, is focused on cybersecurity concerns from facility-related control systems and other operational technology (OT), such as industrial control systems (ICS). The FRCS Cyber Toolkit can be applied across six of the sixteen critical infrastructure sectors designated by the Department of Homeland Security, including government facilities, healthcare and public health, commercial facilities (e.g., public assembly, offices, lodging), financial services (e.g., banking and insurance), emergency services (e.g., fire and police stations), and information technology. With increasingly converged IT and OT systems, it is crucial to address OT cybersecurity considerations and assess how the seam of these two systems could impact the overall cybersecurity posture of a facility. The objective of this report is to provide an overview of the best possible method to use FRCS Cyber Toolkit (section 2.0) and distilled cybersecurity best practices for the federal facilities to address growing non-linear cyber threats (section 3.0). Recommendations in this document are aggregated from several NIST and other documents (see Appendix A for additional details).

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2021

Terry Turbopump Expanded Operating Band Modeling and Simulation Efforts in Fiscal Year 2021 Extended Period of Performance (Final Report)

This report documents the progress made under the Terry Turbine Expanded Operating Band (TTEXOB) program's modeling and simulation (MODSIM) initiative at Sandia National Laboratories (SNL ). It describes the US Federal Fiscal Year 2021 (FY21) extended period-of-performance MODSIM work completed since the closure of FY20 with due reference to the Texas A&M University (TAMU) hybrid milestone 5/6 experimental program. This work, which falls under Milestone 7 of the program, provides a counterpart to the various experiments. The overall TTEXOB program and its milestone-based approach are described in the program's Summary Plan. Details of the individual milestone test plans can be found in the corresponding detailed test plan, e.g. the Milestone 3 and 4 Detailed Test Plan. SNL MODISM is conducted alongside experiments performed at TAMU, and SNL technical staff regularly consults with TAMU on the experimental program. In FY21, MELCOR code models and capabilities were exercised in two different contexts: experimental comparisons to the TAMU ZS-1 and GS-2, and stand-alone analyses of a station black-out (SBO) scenario in a generic boiling water reactor (BWR). Code to experiment comparisons met with fair success when turbine losses were well characterized as for the ZS-1 turbine. Both deterministic and Bayesian calibration processes were used to find a recommended turbine torque multiplier for ZS-1 type turbines. This process could be repeated for GS-2 type turbines if GS-2 losses were better understood. Stand-alone generic BWR SBO calculations revealed that three different modes of self-regulating turbopump behavior may be observed depending on certain modeling parameters and choices having to do with turbine nozzles. Aspects of this predicted behavior may have been observed in TAMU GS-2 experiments.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗
DOE OSTI2017

Evaluation of Roadmap to Achieve Energy Delivery Systems Cybersecurity

The Department of Energy/Office of Electricity Delivery and Energy Reliability (DOE/OE) Cybersecurity for Energy Delivery Systems (CEDS) program is currently evaluating the Roadmap to Achieve Energy Delivery Systems Cybersecurity document that sets a vision and outlines a set of milestones. The milestones are divided into five strategic focus areas that include: 1. Build a Culture of Security; 2. Assess and Monitor Risk; 3. Develop and Implement New Protective Measures to Reduce Risk; 4. Manage Incidents; and 5. Sustain Security Improvements. The most current version of the roadmap was last updated in September of 2016. Sandia National Laboratories (SNL) has been tasked with revisiting the roadmap to update the current state of energy delivery systems cybersecurity protections. SNL is currently working with previous and current partners to provide feedback on which of the roadmap milestones have been met and to identify any preexisting or new gaps that are not addressed by the roadmap. The specific focus areas SNL was asked to evaluate are: 1. Develop and Implement New Protective Measures to Reduce Risk and 2. Sustain Security Improvements. SNL has formed an Industry Advisory Board (IAB) to assist in answering these questions. The IAB consists of previous partners on past CEDS funded efforts as well as new collaborators that have unique insights into the current state of cybersecurity within energy delivery systems. The IAB includes asset owners, utilities and vendors of control systems. SNL will continue to maintain regular communications with the IAB to provide various perspectives on potential future updates to further improve the breadth of cybersecurity coverage of the roadmap.

24 POWER TRANSMISSION AND DISTRIBUTION↗
DOE OSTI2024

EV SALaD 2023 Demonstration: Best Practices and Mitigations for Protecting EVSE Infrastructure

The Electric Vehicle Secure Architecture Laboratory Demonstration (EV SALaD) program is a demonstration of cybersecurity best practices for high-power electric vehicle (EV) charging infrastructure led by Idaho National Laboratory (INL), in collaboration with other DOE National Laboratories participating in the EVs at Scale Consortium.a Sandia National Laboratories (SNL) and Pacific Northwest National Laboratory (PNNL) participated in the first 2-year (FY22-23) demonstration cycle for EV SALaD. This report documents the FY23 demonstration, the second in a series of demonstrations and collaborations in deploying and operating cybersecure EV charging infrastructure. It includes a summary of improvements from the FY22 demonstration, technical analysis of the FY23 demonstration, how the research demonstrates cyber-physical and cybersecurity best practices for high-power EV charging infrastructure, and related impacts to national and energy security. For EV SALaD, the FY22 demonstration focused on the detection, ranking, and prioritization of anomalous events for high-power EV charging. The FY23 demonstration additionally included the demonstration of cybersecurity best practices, which included protection and mitigation solutions to prevent, respond, and recover from anomalous events. During the demonstrations, the multi-lab EV SALaD team conducted a Test Effect Payload (TEP)b evaluation on extreme fast charger (XFC) hardware equipped with Cerberus, a detection and response solution, to demonstrate anomaly detection and mitigation cybersecurity best practices against cyber-enabled events.

33 ADVANCED PROPULSION SYSTEMS↗