SEARCH · Search NASA

Results for “Resource Management Software”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 649 records · Page 36

All sources NASA NTRS DOE OSTI

DOE OSTI2019

Chapter 1: Looking Forward: The Promise and Challenge of Exascale Computing

The demand for HFM development and HPC resources for improved predictive modelling capability for wind energy will continue to grow as industry and government seek solutions to (1) mitigate risk and uncertainty of technology development at multimegawatt-turbine scales, (2) address new requirements driving renewable energy deployment and high -penetration scenarios, (3) understand the impacts of multiple gigawatt-scale plant deployments on microclimatology and grid architectures for both land-based and offshore installation, and (4) evolve the systems and processes needed for the dispatch of renewable energy generation on a national scale supporting a mix of power-generation technologies. When considering the cost of developing a new offshore multimegawatt commercial wind turbine product line or the financial risk of a large offshore wind plant deployment, predictive HPC and HFM simulations that incorporate integrated design, cost analysis, and O&M predictions will become an essential part of the early design and development process.

97 MATHEMATICS AND COMPUTING↗

NASA NTRS2013

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗

DOE OSTI2019

A Python Package for Fuel Cycle and Waste Management Analysis - 19545

The future of nuclear power utilization in the United States may involve a transition from the once-through light water reactor fuel cycle to a so-called advanced fuel cycle. An advanced fuel cycle may offer improvements in natural resource utilization, reactor safety, and environmental impact. In addition, adoption of an advanced fuel cycle will result in changes in the amount, composition, and disposal of the nuclear wastes they produce. Characteristics intrinsic to the wastes themselves, such as mass and radioactivity at specific times, were used as waste management metrics in the Department of Energy 2014 Fuel Cycle Evaluation and Screening (FCES) study. Binning of these metrics informed fuel cycle according to relative potential benefit. However, waste properties alone cannot qualify management strategy. Therefore, comparing fuel cycles from the perspective of waste management can provide additional insights. To that end, an object-oriented Python package has been developed to perform fuel cycle waste management calculations. The package, named nwpy (short for Nuclear Waste analysis in Python), mimics the mass flow operations reported in the FCES study and interfaces with the ORIGEN-S code to assess metric data as reported in the FCES. In addition, this Python package determines the loading of waste streams into forms suitable for final disposal in a geological repository and uses such data for repository performance assessment. This work describes the Python package methodology, assumptions, and capabilities. As input data, the package requires information about the fuel cycle such as the mass of fuel discharged, the cooling time between reactor discharge and subsequent operations, and the separations process efficiencies and waste forms it produces. In addition, the isotopic composition of the reactor discharge stream, such as that available from the FCES database, is required. With that, it can perform prescribed mass flow and decay operations throughout the back end of the fuel cycle, the latter carried out by the ORIGEN-S code distributed with the SCALE6.2 software suite. The result is time-dependent data characterizing the waste on a per-package basis. Package loading for waste streams depends on the stream form (i.e. UNF vs. HLW, or glass HLW from aqueous reprocessing vs. ceramic HLW from electrochemical processing) and is based on literature review and engineering assumption. As an example of the application of the code, calculations for the areal footprint of direct-contact repositories for different fuel cycles is shown. Development is ongoing, and the package is expected to grow incorporating capabilities for waste management analyses such as waste transportation and radionuclide transport through the biosphere. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

NASA NTRS2010

Model for Simulating a Spiral Software-Development Process

A discrete-event simulation model, and a computer program that implements the model, have been developed as means of analyzing a spiral software-development process. This model can be tailored to specific development environments for use by software project managers in making quantitative cases for deciding among different software-development processes, courses of action, and cost estimates. A spiral process can be contrasted with a waterfall process, which is a traditional process that consists of a sequence of activities that include analysis of requirements, design, coding, testing, and support. A spiral process is an iterative process that can be regarded as a repeating modified waterfall process. Each iteration includes assessment of risk, analysis of requirements, design, coding, testing, delivery, and evaluation. A key difference between a spiral and a waterfall process is that a spiral process can accommodate changes in requirements at each iteration, whereas in a waterfall process, requirements are considered to be fixed from the beginning and, therefore, a waterfall process is not flexible enough for some projects, especially those in which requirements are not known at the beginning or may change during development. For a given project, a spiral process may cost more and take more time than does a waterfall process, but may better satisfy a customer's expectations and needs. Models for simulating various waterfall processes have been developed previously, but until now, there have been no models for simulating spiral processes. The present spiral-process-simulating model and the software that implements it were developed by extending a discrete-event simulation process model of the IEEE 12207 Software Development Process, which was built using commercially available software known as the Process Analysis Tradeoff Tool (PATT). Typical inputs to PATT models include industry-average values of product size (expressed as number of lines of code), productivity (number of lines of code per hour), and number of defects per source line of code. The user provides the number of resources, the overall percent of effort that should be allocated to each process step, and the number of desired staff members for each step. The output of PATT includes the size of the product, a measure of effort, a measure of rework effort, the duration of the entire process, and the numbers of injected, detected, and corrected defects as well as a number of other interesting features. In the development of the present model, steps were added to the IEEE 12207 waterfall process, and this model and its implementing software were made to run repeatedly through the sequence of steps, each repetition representing an iteration in a spiral process. Because the IEEE 12207 model is founded on a waterfall paradigm, it enables direct comparison of spiral and waterfall processes. The model can be used throughout a software-development project to analyze the project as more information becomes available. For instance, data from early iterations can be used as inputs to the model, and the model can be used to estimate the time and cost of carrying the project to completion.

Mizell, Carolyn↗

NASA NTRS2023

Adaptive Independent Verification and Validation (IV&V) Reduces Risk of Software Impacting Safety in Artemis Missions

The National Aeronautics and Space Administration (NASA) is asking more of its human spaceflight programs than ever before through the collective Artemis Missions. The NASA Independent Verification and Validation (IV&V) Program contributes to NASA’s human spaceflight goals by providing IV&V services for NASA’s critical spacecraft and ground software. The IV&V Program is tasked with providing assurance from both individual and integrated mission software perspectives. The Artemis IV&V organization is actively supporting six distinct development efforts: Orion, the Space Launch System (SLS), Exploration Ground Systems (EGS), Mission Control Center (MCC), the Lunar Gateway, and the Human Landing System (HLS), representing a wide diversity of developer organizations, management structures, and development approaches. With much of this extremely complex flight and ground software being essential to human safety both on the ground and in space, Artemis IV&V is likewise challenged to provide more value-added assurance to future Artemis missions within a constrained budget. To meet this challenge, Artemis IV&V employs a variety of novel and evolving “Adaptive IV&V” approaches for planning and executing IV&V analysis to increase both the efficiency and effectiveness of the IV&V Program’s assurance activities, and to address the difficulties imposed by assuring software for a large, highly integrated, multi-mission enterprise managed and executed by physically and organizationally distinct programs. Instilling agile principles like iterative planning cycles, self-organizing teams, and regular retrospectives, into IV&V planning and execution has led to a more rapid turnaround of a minimum viable assurance product and allowed for increased alignment of assurance activities with development progress. Adopting an assurance case methodology has led to greater consistency and clearer communication of assurance design and provided a foundation for long-term maintenance of assurance plans, products, and results across missions. The IV&V-developed Assurance / Safety Case Analytical Network (A-SCAN) framework and tool has enabled the quantification and tracking of system/software risk and confidence. These confidence measures provide a means to repeatedly express the impact of planned and completed assurance work and the remaining residual risk. Applied as part of a “Follow-the-Risk” organizational ethos, this allows consistent rightsizing of analysis rigor and intensity commensurate with the perceived risk of defects, as well as appropriate targeting of the highest risk areas of the software to find safety issues before they can manifest. Finally, the development of the IV&V Advanced Risk Reduction Integrated Software Test and Operations Tri-program Lightweight Environment (ARRISTOTLE), an integrated software-only simulation of Orion, SLS, and EGS systems, has made it possible to independently test integrated pad and flight scenarios and inject faults to observe how the Artemis multi-program, mission software behaves in degraded modes and in response to hazards. These adaptive IV&V investments have enabled Artemis IV&V to become more efficient and effective in IV&V planning and execution and respond more readily to changes in the risk landscape, increasing the breadth and depth of risk reduction possible within the available resources. Residual risk tracking allows IV&V to communicate more effectively with stakeholders, both internal and external at all levels, and inform key decision-making personnel. This evolving assurance design approach provides IV&V surety that work is performed in the highest risk, most value-added areas of the software, to keep our astronauts and ground crews safe and ensure mission success.

Gerek A Whitman↗

NASA NTRS2023

Adaptive Independent Verification and Validation (IV&V) Reduces Risk of Software Impacting Safety in Artemis Missions

Gerek Whitman↗

DOE OSTI2018

A New Approach for Short-Term Solar Radiation Forecasting Using the Estimation of Cloud Fraction and Cloud Albedo

Solar generation is an increasing part of the energy portfolio in the United States. An accurate forecast of the available solar resource and power is essential to managing the electric grid, market operations, and reducing the cost of solar energy. High-frequency forecasts of solar radiation in intra-hour horizons is important for real-time electric power system energy management, especially at the distribution level. Conventional Numerical Weather Prediction models perform poorly in intra-hour, high-frequency forecasts because of the limits on real-time computing, spatial resolution, and infrequent availability of observations. Although a number of alternative technologies, e.g., time-series analysis and machine learning, have been used to fill this gap, the smart persistence model is among the top-performing models in short-term forecasting and therefore often serves as the baseline to evaluate other forecasting models. Although the smart persistence model often serves as the baseline model in these intra-hour forecasts, obvious uncertainties exist in the current smart persistence model: (1) clear-sky index does not respond to the variation of the solar incident angle when cloud conditions are persistent within the forecast horizon, and (2) cloud coverage is inherently persistent though it is constrained by cloud advection. In this study, we developed a Physics-Based Smart Persistence Model for Intra-Hour Solar Forecasting (PSPI) that integrates cloudy property estimation, a radiative transfer model, and cloud fraction forecasts to improve the performance of the smart persistence model. Compared to the smart persistence model, PSPI does not require additional observations of various atmospheric parameters past global horizontal irradiance, but it is customizable because additional observations, if available, can be ingested to further improve the forecast. Our results show that the PSPI outperforms the persistence and smart persistence model on 5-minute, 15-minute, and 30-minute forecast horizons. The software package of PSPI is flexible to users' needs and provides low computational time to run at site-specific locations across the continental United States.

14 SOLAR ENERGY↗

DOE OSTI2018

Improved Hybrid Modeling of Spent Fuel Storage Facilities

This work developed a new computational method for improving the ability to calculate the neutron flux in deep-penetration radiation shielding problems that contain areas with strong streaming. The “gold standard” method for radiation transport is Monte Carlo (MC) as it samples the physics exactly and requires few approximations. Historically, however, MC was not useful for shielding problems because of the computational challenge of following particles through dense shields. Instead, deterministic methods, which are superior in term of computational effort for these problems types but are not as accurate, were used. Hybrid methods, which use deterministic solutions to improve MC calculations through a process called variance reduction, can make it tractable from a computational time and resource use perspective to use MC for deep-penetration shielding. Perhaps the most widespread and accessible of these methods are the Consistent Adjoint Driven Importance Sampling (CADIS) and Forward-Weighted CADIS (FW-CADIS) methods. For problems containing strong anisotropies, such as power plants with pipes through walls, spent fuel cask arrays, active interrogation, and locations with small air gaps or plates embedded in water or concrete, hybrid methods are still insufficiently accurate. In this work, a new method for generating variance reduction parameters for strongly anisotropic, deep penetration radiation shielding studies was developed. This method generates an alternate form of the adjoint scalar flux quantity, Φ Ω , which is used by both CADIS and FW-CADIS to generate variance reduction parameters for local and global response functions, respectively. The new method, called CADIS-Ω, was implemented in the Denovo/ADVANTG software. Results indicate that the flux generated by CADIS-Ω incorporates localized angular anisotropies in the flux more effectively than standard methods. CADIS-Ω outperformed CADIS in several test problems. This initial work indicates that CADIS- may be highly useful for shielding problems with strong angular anisotropies. This is a benefit to the public by increasing accuracy for lower computational effort for many problems that have energy, security, and economic importance.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

NASA NTRS1993

Earthbound applications for NASA's physician workstation

The dream of a space probe to Mars or an astronaut colony on the moon persists. Despite years of setbacks and delays, NASA continues to lay the foundation for a new frontier in space. The necessity of a self contained health maintenance facility is an integral part of this stellar venture. As a subsystem of this health maintenance facility, the physician or astronaut workstation was envisioned as the vehicle of interface between the computer resources of the space station and the care provider. Our efforts to define and build this interface have resulted in a series of programs which can now be tested and refined using earth-based applications. The modules which have dual-use application from the NASA workstation include: patient scheduling and master patient index, pharmacy, laboratory, medical library, problem list/progress notes, and digital medical records. Our current plan is to develop these tools as objects that can be assembled in a variety of configurations. This will allow the technology to be used by the private sector where each doctor can select the starting point of his outpatient office system and add modules as he makes progress in system integration and training.

NASA Discipline Number 70-30↗

DOE OSTI2019

Preliminary Logistics Modeling of the Integrated Wash Aid Treatment Emergency Reuse System - 19495

We employed Analysis of Mobility Platform (AMP) and GoldSim software to model the logistics of deploying materials to implement the Integrated Wash Aid Treatment Emergency Reuse System (IWATERS) in a hypothetical cesium-contamination scenario covering a four-block strip of downtown Chicago, IL. In this deployment of IWATERS, buildings were washed down via fire-hosing and contaminated wash solution was collected in the city's waste/stormwater collection system. The contaminated wash water was treated to remove Cs via ad hoc sand/clay filtration beds, and the treated wash solution was recycled during continuing decontamination operations. A detailed task timeline for the IWATERS deployment and information (or assumptions) on the availability and location of required resources for operations provided input parameters, as well as a framework, to enable the AMP and GoldSim simulations. From the decision to deploy IWATERS to the end of operations, including the completion of processing all contaminated wash water, took 49 days with decontamination teams active for 35 days and treatment bed teams active for 37 days. The modeling results showed the availability of vermiculite clay (based on data supplied by its commercial vendors/distributors) as the limiting factor for deploying treatment bed teams and, consequentially, the recycling rate of wash water and the timeline for decontamination operations. These simulations represent the first attempt at understanding the material and personnel requirements for large-scale IWATERS operation. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

NASA NTRS2007

Science Archives in the 21st Century: A NASA LAMBDA Report

Lambda is a thematic data center that focuses on serving the cosmic microwave background (CMB) research community. LAMBDA is an active archive for NASA's Cosmic Background Explorer (COBE) and Wilkinson Microwave Anisotropy Probe (WMAP) mission data sets. In addition, LAMBDA provides analysis software, on-line tools, relevant ancillary data and important web links. LAMBDA also tries to preserve the most important ground-based and suborbital CMB data sets. CMB data is unlike other astrophysical data, consisting of intrinsically diffuse surface brightness photometry with a signal contrast of the order 1 part in 100,000 relative to the uniform background. Because of the extremely faint signal levels, the signal-to-noise ratio is relatively low and detailed instrument-specific knowledge of the data is essential. While the number of data sets being produced is not especially large, those data sets are becoming large and complex. That tendency will increase when the many polarization experiments currently being deployed begin producing data. The LAMBDA experience supports many aspects of the NASA data archive model developed informally over the last ten years-that small focused data centers are often more effective than larger more ambitious collections, for example; that data centers are usually best run by active scientists; that it can be particularly advantageous if those scientists are leaders in the use of the archived data sets; etc. LAMBDA has done some things so well that they might provide lessons for other archives. A lot of effort has been devoted to developing a simple and consistent interface to data sets, for example; and serving all the documentation required via simple 'more' pages and longer explanatory supplements. Many of the problems faced by LAMBDA will also not surprise anyone trying to manage other space science data. These range from persuading mission scientists to provide their data as quickly as possible, to dealing with a high volume of nuisance (spam) messages. Because so many data center problems and solutions are common across individual data centers and disciplines it would be very valuable to establish some new systems of communication - such as informal email lists for administrators and developers. But resources are very limited, so new timeconsuming and inefficient mechanisms - like too-frequent and too-structured meetingsshould be avoided. Although there are great advantages to being small, agile and independent, there are also some areas where science data centers within and without NASA could be better coordinated - for the assignment of persistent identifiers; to encourage the early adoption of useful standards and technologies; etc. Some super-structure to facilitate such coordination might be beneficial as long as it doesn't begin to control the other work of the archives, and become a "methodology police". In this respect the CCSDS "Reference Model for an Open Archive Information System" is a little worrying. It may be that the closer a data center gets to following such a detailed prescription, the less effective it will become. It is much better to have an informal coordination process than a bureaucratic straight-jacket.

Butterworth, P.↗

DOE OSTI2023

Engineering Computational Practices (Rev. 1)

This manual will attempt to motivate the use of an automated build system for the purposes of computational science and engineering. As part of this motivation, the surrounding computational practices of version control, documen tation, compute environment management, and regression testing will also be addressed as applied to the practice of computational engineering. Specifically, this manual intends to motivate the adoption of these traditional software engineering practices for use in research and production engineering simulation projects. This manual is not the first such effort in the greater scientific computing community. In fact, the authors relied heavily on the lesson plans of the Software Carpentry, established to teach computing skills to researchers in 1998. As the intention for this manual is to lay out fundamental practices of engineering computing, it will not attempt to fully teach the underlying concepts and will instead reference the well designed lesson plans of the Software Carpentry. Where possible, this manual will explain to general computing practices and concepts and limit discussion of specific software implementations to examples or vehicles for practice in concrete application. The specific software taught by the Software Carpentry curriculum is an excellent starting point to learn the core concepts of computational engi neering. However, the authors have found that applications to engineering simulation and analysis require translation of these software development concepts into the language and workflows of computational engineers. Adopting these computational tools may require engineers to re-imagine their workflows in some combination of traditional engineer ing and software concepts. It has also been necessary to extend existing software build systems for engineering practices beyond the simple wrap ping of engineering software execution. Where necessary, examples of specific software and their method of extension to engineering simulations will be given, with reference to the User Manual for recommended practical use. Where this manual relies on specific implementation examples, it should be understood that the practicing engineer may find that different software is more amenable to their specific work. It is always the overall collection of computational practices is more important than any specific software implementation. The ability to recognize which concepts are implemented by a software package will make a practicing engineer agile to changing project needs, computing resources, numeric solvers, programming languages, and even available funding.

42 ENGINEERING↗

DOE OSTI2022

AmeriFlux FLUXNET-1F US-Me2 Metolius mature ponderosa pine

This is the AmeriFlux Management Project (AMP) created FLUXNET-1F version of the carbon flux data for the site US-Me2 Metolius mature ponderosa pine. This is the FLUXNET version of the carbon flux data for the site US-Me2 Metolius mature ponderosa pine produced by applying the standard ONEFlux (1F) software. Site Description - Site Description before Fire (January, 2002 - August, 2020): The mean stand age is 71 years old and the stand age of the oldest 10% of trees is about 108 years old. This site is one of the Metolius core cluster sites with different age and disturbance classes and part of the AmeriFlux network. The overstory is almost exclusively composed of ponderosa pine trees (Pinus ponderosa Doug. Ex P. Laws) with a few scattered incense cedars (Calocedrus decurrens (Torr.) Florin) and has a peak leaf area index (LAI) of 2.1 m2 m-2. Tree height is relatively homogeneous at about 18 m, and the mean tree density is approximately 339 trees ha-1 (Irvine et al., 2008). The understory is sparse with an LAI of 0.2 m2 m-2 and primarily composed of bitterbrush (Purshia tridentata (Push) DC.) and greenleaf manzanita (Arctostaphylos patula Greene). Soils at the site are sandy (69%/24%/7% sand/silt/clay at 0–0.2 m depth and 66%/27%/7% at 0.2–0.5 m depth, and 54%/ 35%/11% at 0.5–1.0 m depth), freely draining with a soil depth of approximately 1.5 m (Irvine et al., 2008; Law et al., 2001b; Schwarz et al., 2004). Green Ridge Fire: On August 20, 2020, the Green Ridge Fire burned through Us-Me2. The fire was ignited by lightning on August 16th, and grew rapidly to the east over the first few days driven by strong, downslope (westerly) afternoon winds. Fire behavior and observed fire effects were highly heterogeneous due to the localized wind pattern carrying the flaming head of the fire forward, and the efforts being made by suppression resources to contain the fire. The site experienced the full range of fire effects, from <1 m high surface fire that charred litter and duff and only consumed shrubs and herbaceous material to full tree (>15 m) crown fire that consumed 100% of needles, small limbs, and surface fuels at high intensity, leaving only ash and bare soil post-fire. Salvage Logging: From late March to late April 2021, salvage logging by the landowner occurred at the site. Almost all trees within the flux footprint were logged except a small area with lower burn severity, where sap flow and automatic soil respiration measurements are continued since the fire. In August 2022 the primary flux system was moved from the top of the damaged tall tower to a nearby shorter tower centering on the salvage/regenerating footprint.

Hanson, Chad↗

DOE OSTI2017

The Future of EPA's Waste Estimation Support Tool - 17227

The Environmental Protection Agency's (EPA's) Waste Estimation Support Tool (WEST) is a GIS-based decision support tool for estimating the characteristics, amount, and residual radioactivity of waste generated from remediation and cleanup activities after a radiological incident, including those involving radiological dispersal devices, improvised nuclear devices, and nuclear power plants. WEST has been released to the public and has been used in numerous national level exercises and planning scenarios; however, it continues to be improved and refined to add additional functionality and performance. Since its inception, WEST has undergone a myriad of updates, routinely ensuring compatibility with ESRI's ArcGIS and FEMA's Hazus, a tool for estimating potential losses from earthquakes, wind, and flood events. Furthermore, recent enhancements have added reporting and mapping features and multi-state support. Over time, this progress has strained WEST's Microsoft{sup C} Excel based platform. The inherent limitations of Excel have limited the capacity of WEST and narrowed the scope of potential enhancements. Recent collaborative efforts between the Department of Homeland Security's (DHS's) Science and Technology Directorate (S and T) and EPA will see the introduction of a new software platform for easing memory limitations and new and innovative features for improving the accuracy of waste estimates. The planned enhancements include: 1) Systems approach: measure or predict the outcome of decisions associated with disaster response (e.g., decontamination efficacy vs. waste) and to a greater extent, the overall resource demand (e.g., cost, time, etc.); 2) Custom infrastructure data and international support: accommodate non-US building information where available and also add new data and information on recently used decontamination technologies as applied in a real-world incident; 3) Additional waste factors: addition of waste factors that are unique to wide area scenarios such as vehicles and trees as they will likely contribute in a significant manner to the overall waste stream;4) Site analysis and logistics: apply spatial information and analysis technologies to locate and prioritize potential waste staging or storage sites; and use GIS-based logistics planning to better organize, route, and estimate the cost, time, and logistical requirements (i.e., resource demand) associated with transporting large volumes of waste from a disaster-stricken area to waste staging or storage sites; 5) Decontamination technologies: introduce new decontamination technologies, better understand the feasibility and efficacy of new and preexisting decontamination technologies when applied to a wide area incident, and use historical incidents to ground truth waste results; and 6) Resource demand: ability to estimate resource demand information associated with decontamination technologies, waste staging and storage, and logistical information for transporting waste. This paper will describe the next version of WEST (WEST 4.0), and how the aforementioned enhancements will contribute to improving the planning and response capabilities of the tool. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

DOE OSTI2024

Enhancing Cloud Cybersecurity: Prescriptive Controls for Operational Technology

This whitepaper provides strategic insights and recommendations into security cloud-based solutions for electric utilities, encompassing operational technology (OT), virtual power plants (VPP), distributed energy resources (DERs), applications, networks, and data storage as they transition to and leverage cloud infrastructure through managed service providers (MSPs) and cloud service providers (CSPs). Principles derived from established frameworks serve as a foundation for best practices across cybersecurity projects and remove the constraints of settling on a single framework. For organizations that prefer not to integrate a specific framework altogether, elements of the proposed approach could be adopted or tailored to best fit defined requirements and expected functionalities. The Cirrus assessment, a utility cloud feasibility tool, and the roadmap it provides serve as a precursor to this paper, which seeks to be a valuable resource for defining next steps following cloud technology integration feasibility appraisal. With its comprehensive approach to adoption, the Cirrus framework offers strategic guidance on responsibly preparing for or deploying a utility cloud solution. The previously published whitepaper, “Use Case-Informed Framework for Utility Cloud Migration,” details the guiding strategy, research, and deployment of cloud solutions within electric and interconnected grid systems. Before implementing the controls suggested in this document, it is recommended that stakeholders complete Cirrus's cloud integration assessment and pair the results with their unique cybersecurity controls to form a comprehensive cloud-based utility cybersecurity plan. The Cirrus outcome will consider a series of future architectures for the grid before and after the energy transition and evaluate the arguments for and against cloud applications for each electric and interconnected grid layer. This document is a companion to the original whitepaper, "Use Case-Informed Framework for Utility Cloud Migration" to further identify and recommend security controls based on Cirrus’s cloud integration assessment output. The following whitepaper outlines the cybersecurity controls that secure cloud-service models pertinent to the electric sector using the predefined categories identify, protect, detect, and respond and recover. The objective is to outline prescriptive security controls based on the type of architecture and data stored in the cloud. The focus includes dissecting the shared responsibility model and elucidating what on-premises Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) entail. A pivotal consideration in this context is allocating responsibility for foundational cybersecurity aspects—having used Cirrus for the cloud integration assessment. The ensuing controls detailed herein also represent a checklist of controls necessary for a secure cloud transition, equipping utilities with the knowledge to navigate this digital transformation with confidence and strategic foresight in a safe and responsible manner.

42 ENGINEERING↗

DOE OSTI2023

Extended Bandwidth Spread Spectrum Time Domain Reflectometry Cable Test for Thermal Aging, Low Resistance Fault, and Water Detection

In 2022, researchers at Pacific Northwest National Laboratory (PNNL) used the Accelerated and Real-Time Environmental Nodal Assessment (ARENA) cable and motor test bed to characterize spread spectrum time domain reflectometry (SSTDR) and compare the responses of an SSTDR instrument to those of a frequency domain reflectometry (FDR) instrument. Results showed both techniques could detect and locate cable anomalies such as phase-to-phase low resistance and shorts, thermal insulation damage, mechanical insulation damage, and the presence or absence of water in some conditions. The SSTDR tests used a commercial instrument provided by LiveWire Innovations Inc. This commercial instrument performed tests at 6, 12, 24, and 48 MHz bandwidth. The results of these tests were compared to FDR tests where bandwidths could be extended up to 1.3 GHz, although the best responses for cable tests were from 100 to 500 MHz. Lower bandwidth signals can propagate better along the cable while higher bandwidths have higher resolution for impedance change reflections allowing more precise indication of location and separation of anomalies. The 2022 research found that FDR responses were clearer than SSTDR and speculated that a higher bandwidth SSTDR could more successfully detect and locate cable anomalies. One advantage of the SSTDR system investigated was that it was designed for energized online use up to 1,000 volts, which may be a significant advantage for nuclear power plant use. The LiveWire SSTDR instrument is an established product in the rail and aircraft industry and updating the SSTDR hardware parameters is difficult to justify without more conclusive testing. Therefore, a software adjustable laboratory SSTDR instrument was developed by PNNL and was used to test extended bandwidth SSTDR cable tests. Within the ARENA test bed, 42 cable conditions were tested with the PNNL SSTDR, FDR, and the LiveWire SSTDR—each operating at four different bandwidths. Observations and conclusions regarding the relative performance of the three instruments over different bandwidths are note below. Responses of the PNNL SSTDR (at 50 MHz) and the LiveWire SSTDR (at 48 MHz) were similar. The PNNL SSTDR higher frequency bandwidths behaved as expected showing sharper peaks and higher noise. This validated the PNNL SSTDR as a reasonable implementation of the SSTDR technology. Lower bandwidth SSTDR responses (particularly 6 and 12 MHz) may have increased value for use within longer cables but were not particularly effective at identifying anomalous cable behavior in the 100 ft cables tested here. The higher bandwidths of the PNNL SSTDR (50, 100, 200, and 400 MHz) did not provide substantially clearer cable reflectometry responses, but having the higher frequency responses available did add to the cable test evaluation. Strong responses to shorts and low impedance faults between phases were particularly evident in the higher bandwidth PNNL SSTDR and the FDR data. Measurements were repeatable, with similar responses obtained from a thermally aged cable for tests taken a month apart. Signal noise was affected in the unshielded cable by the local in-tray cable arrangement including proximity to metal edges and rungs of the cable tray. Foam isolation of the cable from the tray metal reduced in both FDR and SSTDR responses. Cable condition monitoring in nuclear power plants will likely benefit from both more informative off-line testing methods and from the development of on-line methods for continuous monitoring of cables in use. The LWRS-funded ARENA test bed was a valuable resource for this development and direct comparison of nuclear electrical cable condition monitoring technologies. Test results are targeted to guide industry advancement of testing and monitoring tools for cable aging management.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

NASA NTRSDate not supplied

Analysis of Oxygen Liquefaction with Transient Flow Rates for ISRU Systems

Human occupation of lunar and Martian surfaces requires in-situ resource utilization (ISRU) to create a sustainable environment with the limited resources available in space. Fuel and oxidizer generation is essential for developing a refueling capability for spacecraft, significantly reducing the propellant mass required for landing. Liquefaction systems are a key step in producing and storing cryogenic liquids such as oxygen, hydrogen, and methane. All those fluids are critical to propulsion, life support, and other spacecraft systems. NASA has previously confirmed the presence of water on the Moon and an electrolysis process can be used to separate the oxygen from the hydrogen molecules. Oxygen has also been found within lunar regolith and can be separated through ISRU processes. The extracted oxygen gas can then be liquefied inside a storage tank with tube-on-tank heat exchangers for future use as an oxidizer for propellants. While steady state liquefaction performance is easy to model, power limitations and cyclical environments caused by the change in Sun exposure between day and night periods potentially call for transient operations. The following analysis was performed using the Thermal Desktop software to investigate how various transient gaseous oxygen (GOX) flow rates impact the production and storage of liquid oxygen (LOX) in a 1-g liquefaction system. Variations of sinusoidal and exponential step functions were selected to model potential GOX flow rates that could be experienced by ISRU systems on lunar or Martian surfaces. This early computational analysis provides some insight on how transient operations impact oxygen liquefaction systems and helps illustrate operational questions to explore experimentally throughout the design process.

Cryogenic Fluid Management↗

DOE OSTI2022

Hierarchical Model-Free Transactive Control of Building Loads to Support Grid Services

Residential buildings consume 4.4 quads of electricity annually, approximately 37% of the total electricity consumption in the United States. This represents a vast resource that can be used for demand management and other ancillary services. This project aims to develop a robust, scalable hierarchical transactional control mechanism incorporating elements of model-free control (MFC) and game theory to harness buildings to provide ancillary services to the grid. This approach is being taken to address the challenges of incorporating traditional transactional control schemes into existing buildings. The challenges include small individual building sizes requiring aggregation of many buildings, unpredictable energy usage that makes model identification difficult, and satisfying the sensitive occupant comfort constraints. In the proposed approach, by separating the control mechanism into two layers above and below the load aggregator, MFC can be used below the aggregator to modulate flexible building loads in response to pricing signals with guaranteed performance. This allows the burden of identifying an accurate model of the system to be shifted to the above-aggregator layer, where fluctuations in individual building usage have less impact on predicted building system behavior. Game theory concepts can then be used to determine pricing curves and control signals among regional aggregators. Managing this control in a game-theoretic approach will allow us to build in financial incentives that increase customer engagement. Additionally, the usage of MFC necessitates less burdensome computational and communication requirements, thus, it is easily deployable on small, embedded devices. In a broader sense, developing a strategy capable of effectively incorporating residential and small commercial buildings will allow greater throughput of existing and emerging grid services in addition to future transactive energy grid management methods. Using MFC within a hierarchical control architecture will allow the shifting of existing forecasting challenges to an aggregate level, where dynamics are slower and more predictable. This will enable a smooth interface between the grid services requests of utilities and the reliable control required by participating buildings. MFC, which supports distributed control architecture, permits a scalable solution that can be deployed to neighborhood-size systems as well as individual buildings. This project focuses on three objectives: (1) developing the mathematical framework, algorithm toolkit, and software toolset of the two-layer transactive control testbed; (2) developing a scalable solution for application over many residential and small-size commercial buildings with sparse distributed communication; and (3) field testing and implementation on hardware of the control strategies developed in the previous two objectives. The research and development activities are focused and designed to be impactful within the relevant 2025 targets timeframe. An open-source control framework for exploiting variability and dispatchability of building loads will be delivered as the outcome of the project. This capability enables greater participation of loads in electricity markets and ancillary services that are both useful for the utility and financially beneficial for building owners.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗