Search NASA⌕ Search

SEARCH · Search NASA

Results for “records management requirements”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

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

At least 19 records

Metadata Standards for the NSE: Extended Field Standards

This standard presents a set of optional metadata fields for managed digital objects within the Nuclear Security Enterprise (NSE) and provides a deeper look at data representation in metadata by looking at the representation of 1) Records Management required metadata, and 2) common representations of technical/scientific data. Metadata standardization is a critical enabler for effectively sharing data, documents, and other digital objects between NSE sites, and for tracing the digital thread at the object level. Standardization is necessary for both schemas and vocabularies, meaning that both field standards and value standards must be specified. This document serves as a complementary field standard, recommending an optional set of fields that should be uniformly built for all managed digital objects within the NSE. This document specifically focuses on extending the shared discovery layer defined in the first white paper by introducing additional descriptive and data representation fields that improve cross-site search and interpretation.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

USACE FUSRAP Records Management Challenges in the Digital Age - 20242

In late 2016, the U.S. Army Corps of Engineers (USACE) implemented a Headquarters-supported nationwide records management initiative managed by the USACE-New England District to address the digitization and organization of Formerly Utilized Sites Remedial Action Program (FUSRAP) project files. This initiative will prepare USACE FUSRAP for moving toward a fully electronic system of records management. Additionally, the records management initiative streamlines the process and prepares the Administrative Record (AR) and Permanent Record (PR) file for transfer from USACE to the U.S. Department of Energy (DOE)-Office of Legacy Management (LM) following project closeout. Over the past couple of years, USACE and DOE-LM have been working to finalize a joint guidance document to assist in the FUSRAP records transition process. However, there remain key records management topics that require further discussion and development. Specifically, these topics include the implementation, process, and procedure for the capture of social media records and compliance with Section 508 of the Rehabilitation Act of 1973 (29 USC 794d), as amended. Due to advances in technology and the ease of communication it provides, USACE is using social media more often to interface with the public than 5, 10 or 15 years ago. The identification and capture of these records are challenging because it requires each USACE district or producer of a record to track what has been released through social media so that it can be captured as part of the AR or PR. USACE is currently evaluating processes and procedures for social media records capture. This paper explores how social media is being used by USACE across FUSRAP projects and best practices for the capture of social media records. Public accessibility to the project AR is required under the Comprehensive Environmental Response, Compensation, and Liability Act, which USACE FUSRAP must follow. As USACE FUSRAP ARs are converted to a digital format, greater accessibility to the files can be provided through web sites or other electronic media. However, Section 508 of the Rehabilitation Act must be considered when releasing electronic files to the public. Under Section 508, government agencies must ensure that information is made available to the public in a format that provides equal access to persons with disabilities. This paper discusses the electronic records requirements under Section 508 and addresses broad implementation of compliance across large digital records sets. Records management challenges are presented in the context of the FUSRAP records management program; however, these records management considerations and best practices are applicable across all Federal agency records management programs. Examples presented will further aid in understanding electronic records requirements that may be included on new USACE FUSRAP contracts as well as upcoming National Archives Records Administration requirements that will move us toward an electronic government. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

A Goldilocks Approach to Water Management: Hydrochannel Porous Transport Layers for Unitized Reversible Fuel Cells

Abstract This work presents a novel porous transport layer (PTL), the hydrochannel PTL, that enables improved water management and record high round trip efficiency in unitized reversible fuel cells (URFCs). URFCs require rapid transport of O 2 and H 2 O to provide high performance in both fuel cell and water electrolyzer operation, but cell design is complicated by conflicting water management requirements: electrolyzers perform best with high liquid water saturation, whereas fuel cells perform best when liquid water saturation is as low as possible while still maintaining effective ionomer hydration. The hydrochannel PTL circumvents this obstacle by providing hydrophilic channels for water transport through an otherwise hydrophobic PTL, enabling optimal performance in both fuel cell and water electrolyzer modes. Neutron radiography measurements of water content in both operating modes confirm that the hydrochannel PTL enables high performance due to its improved water management capabilities.

25 ENERGY STORAGE↗

Metaevaluation Final Report: Sandia National Laboratories Recorded Information Management Training Program Evaluation

For my internship project, I chose to evaluate the training program for the Sandia National Laboratories (SNL) Recorded Information Management (RIM) Program. The purpose of the evaluation was to identify: Where the current training meets federal and corporate requirements and if not, what gaps exist; If the training is accessible in a consistent location; If the training contains a consistent message about the responsibility of managing documents; If the training is organized by records management subject areas.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

Corrective Action Unit 98: Frenchman Flat Five-Year Evaluation Nevada National Security Site, Nevada (Revision 1)

The Corrective Action Unit (CAU) 98, Frenchman Flat (FF) Closure Report (CR) (NNSA/NFO, 2016) and its ensuing Records of Technical Change (ROTCs) (compiled in DOE/EMNV, 2019) required the U.S. Department of Energy (DOE), Environmental Management (EM) Nevada Program’s Underground Test Area (UGTA) Activity to collect data for five years to establish triggers for the monitoring network and analyze the monitoring points for viability in long-term monitoring. This document provides the results of the five-year evaluation and presents recommendations for future monitoring of CAU 98.

54 ENVIRONMENTAL SCIENCES↗

Compliance of NNSS Activities with P322-4 Issues Management and NNSSWAC Requirements

The Institutional Quality and Performance Assurance Division's Quality Support Services Group conducted a surveillance of the compliance of Waste Management Program activities to Issues Management/Corrective Action requirements communicated in P322-4 and the Nevada National Security Site Waste Acceptance criteria (NNSSWAC). All corrective actions reviewed and records examined were found to be compliant with appropriate and relevant procedures. There were no Findings or Opportunities for Improvement noted.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Frontier Job-Centric Telemetry Dataset

Comprehensive analysis of high-performance computing (HPC) systems requires linking workload execution to system behavior. This kind of analysis is vital for diagnosing performance issues, managing capacity, detecting anomalous workloads, and understanding how applications interact with system hardware. This job-centric telemetry dataset unifies scheduler job records with node-level measurements, enabling direct association between workloads and their corresponding power, thermal, and performance characteristics. It contains sanitized, scheduler related metadata for 152,400 individual jobs that ran on the Frontier supercomputer and ended on selected days throughout 2024 and 2025, a subpopulation of ~6.8% of the total number of allocated jobs with non-zero run time on the system over that same period. Each is linked with files that contain telemetry time series records of the power utilization and temperature behavior of its allocated nodes and their processors during the run time of the job. Where available, a portion of the job files also contain network performance time series. Jobs are sampled from select days that reflect normal levels of user activity and possess job size distributions with large numbers of leadership class jobs (>20% of Frontier nodes). Jobs in this dataset attempt to best represent successful user workflows.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Nevada National Security Site Radiological Control Manual

Please have this STIP assigned, documented, and recorded in OSTI as Report Number DOE/NV/03624--0257 Revision 1 and Author as Radiological Control Managers' Council. This manual contains the radiological control requirements to be used for all radiological activities conducted by programs under the purview of the U.S. Department of Energy (DOE), National Nuclear Security Administration Nevada Field Office (NNSA/NFO). (Activities conducted under the purview of the U.S. Department of Energy, Office of Environmental Management Nevada[(EM Nevada] may require additional approval authorities as described in the EM Nevada Prime Contractor’s implementation plan.) Compliance with these requirements will ensure compliance with Title 10 Code of Federal Regulations (CFR) Part 835, “Occupational Radiation Protection.” This manual represents policies, guidelines, and best practices for implementing the DOE/NV/03624--0082, “Nevada National Security Site Radiation Protection Program,” (NNSS RPP) according to the requirements of 10 CFR 835.

61 RADIATION PROTECTION AND DOSIMETRY↗

A U.S. Scientific Community Vision for Sustained Earth Observations of Greenhouse Gases to Support Local to Global Action

Managing carbon stocks in the land, ocean, and atmosphere under changing climate requires a globally‐integrated view of carbon cycle processes at local and regional scales. The growing Earth Observation (EO) record is the backbone of this multi‐scale system, providing local information with discrete coverage from surface measurements and regional information at global scale from satellites. Carbon flux information, anchored by inverse estimates from spaceborne Greenhouse Gas (GHG) concentrations, provides an important top‐down view of carbon emissions and sinks, but currently lacks global continuity at assessment and management scales (<100 km). Partial‐column data can help separate signals in the boundary layer from the overlying atmosphere, providing an opportunity to enhance surface sensitivity and bring flux resolution down from that of column‐integrated data (100–500 km). Based on a workshop held in September 2024, the carbon cycle community envisions a carbon observation system leveraging GHG partial columns in the lower and upper troposphere to weave together information across scales from surface and satellite EO data, and integration of top‐down/bottom‐up analyses to link process understanding to global assessment.

Parazoo, Nicholas C. [California Institute of Tech↗

Code of Record: DOE Standard Canister (DOESC)

The United States Department of Energy (DOE) Spent Nuclear Fuel (SNF) Packaging Demonstration seeks to develop and demonstrate the designs, technology, processes, and regulatory framework for packaging DOE SNF for road-ready dry storage (RRDS); and establish the processes that will be used in a future production facility. The Packaging Demonstration will utilize the DOE Standard Canister (DOESC) for packaging select DOE-managed SNF types for interim storage, transportation and disposal as part of RRDS. Placing DOE-managed SNF into RRDS is part of the strategic framework for SNF on the Idaho National Laboratory (INL) site. To comply with DOE, INL and Nuclear Regulatory Commission (NRC) requirements, this Code of Record establishes the American Society of Mechanical Engineers (ASME) Boiler and Pressure Vessel Code (BPVC), Section III, Division 3 as the Code that will govern DOESC and internal support structure constructioni, with certain clarifications. This Code of Record establishes a rationale for proceeding without construction certification of the DOESC (i.e., “N-stamping) and the extent to which a Registered Professional Engineer is required for the DOE Spent Fuel Packaging Demonstration. Given the (i) standard industry practice to pursue independent licensure of commercial storage casks and transportation packages by the NRC in lieu of ASME certification and (ii) guidance provided by 10 CFR 830, DOESC construction activities need not be certified (i.e., “stamped”) to the ASME BPVC. However, additional quality assurance requirements will apply as outlined in this Code of Record.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Overview of the Instrumentation for the Dark Energy Spectroscopic Instrument

Abstract The Dark Energy Spectroscopic Instrument (DESI) embarked on an ambitious 5 yr survey in 2021 May to explore the nature of dark energy with spectroscopic measurements of 40 million galaxies and quasars. DESI will determine precise redshifts and employ the baryon acoustic oscillation method to measure distances from the nearby universe to beyond redshift z > 3.5, and employ redshift space distortions to measure the growth of structure and probe potential modifications to general relativity. We describe the significant instrumentation we developed to conduct the DESI survey. This includes: a wide-field, 3.°2 diameter prime-focus corrector; a focal plane system with 5020 fiber positioners on the 0.812 m diameter, aspheric focal surface; 10 continuous, high-efficiency fiber cable bundles that connect the focal plane to the spectrographs; and 10 identical spectrographs. Each spectrograph employs a pair of dichroics to split the light into three channels that together record the light from 360–980 nm with a spectral resolution that ranges from 2000–5000. We describe the science requirements, their connection to the technical requirements, the management of the project, and interfaces between subsystems. DESI was installed at the 4 m Mayall Telescope at Kitt Peak National Observatory and has achieved all of its performance goals. Some performance highlights include an rms positioner accuracy of better than 0.″1 and a median signal-to-noise ratio of 7 of the [O ii ] doublet at 8 × 10 −17 erg s −1 cm −2 in 1000 s for galaxies at z = 1.4–1.6. We conclude with additional highlights from the on-sky validation and commissioning, key successes, and lessons learned.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

HarDWR - Raw Water Rights Records

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. In order to hold a water right in the western United States, an entity, (e.g., an individual, corporation, municipality, sovereign government, or non-profit) must register a physical document with the state's water regulatory agency. State water agencies each maintain their own database containing all registered water right documents within the state, along with relevant metadata such as the point of diversion and place of use of the water. All western U.S. states have digitized their individual water rights databases, along with the geospatial data describing the spatial units where water rights are managed. Each state maintains and provides their own water rights data in accordance with individual state regulations and standards. We collected water rights databases from 11 western United States states either by downloading them from publicly accessible web portals, or by contacting state water management representatives; detailed descriptions of where and when the data was collected is provided in the README.txt, as well as Lisk et al.(in review). This collection of data are those raw water rights. Each state formats their data differently, meaning that file types, field availability, and names vary from state to state. Note, the data provided here reflects the state of the water rights databases at the time we collected the data; updates have likely occurred in many states. Some pieces of information are common among all states. These are: priority date, volume or flow of water allowed by the right, stated water use of the right, and some means of identifying the geography and source of the water pertaining to the right - typically the coordinates of the Point of Diversion (PoD) of a waterbody or well. Arizona regulates water in a different way than the other 10 states. Outside of some relatively small critical agricultural areas called Active Management Areas (AMAs), Arizona does not maintain any water rights. However, the state does require registration of surface and groundwater pumping devices, which includes disclosing the mechanical specifics of the devices. We used these records as a proxy for water rights. Each state, and their respective water right authorities, have made their water right records available for non-commercial reference uses. In addition, the states make no guarantees as to the completeness, accuracy, or timeliness of their respective databases, let alone the modifications which we, the authors of this paper, have made to the collected records. None of the states should be held liable for using this data outside of its intended use. In addition, the following states have requested specifically worded disclaimers to be included with their data. Colorado: "The data made available here has been modified for use from its original source, which is the State of Colorado. THE STATE OF COLORADO MAKES NO REPRESENTATIONS OR WARRANTY AS TO THE COMPLETENESS, ACCURACY, TIMELINESS, OR CONTENT OF ANY DATA MADE AVAILABLE THROUGH THIS SITE. THE STATE OF COLORADO EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the Web feed is being used at one's own risk." Montana: "The Montana State Library provides this product/service for informational purposes only. The Library did not produce it for, nor is it suitable for legal, engineering, or surveying purposes. Consumers of this information should review or consult the primary data and information sources to ascertain the viability of the information for their purposes. The Library provides these data in good faith but does not represent or warrant its accuracy, adequacy, or completeness. In no event shall the Library be liable for any incorrect results or analysis; any direct, indirect, special, or consequential damages to any party; or any lost profits arising out of or in connection with the use or the inability to use the data or the services provided. The Library makes these data and services available as a convenience to the public, and for no other purpose. The Library reserves the right to change or revise published data and/or services at any time." Oregon: "This product is for informational purposes and may not have been prepared for, or be suitable for legal, engineering, or surveying purposes. Users of this information should review or consult the primary data and information sources to ascertain the usability of the information." The available data is provided as a series of compressed files, which each containing the full data collected from each state. Some of the files have been renamed, to more easily know which state the data belongs to. The file renaming was also required as some files from different states had the same name. In other cases, the data for a state has been placed in a folder indicating which state it belongs to - as the state organized its data by selected subregions. Below is a brief description of the format of the collected data from each state. ArizonaRights_StatementOfClaimants: A folder containing a database of interconnected CSV files. The soc_erd.pdf file contains a visual flowchart of how the various files are connected, beginning with SOC_MAIN.csv in the center of the page. ArizonaRights_SurfaceWaterRightsData: A folder containing a database of a single Shapefile and 10 associated CSVs. SurfaceWater.pdf contains a visual flowchart of how the various files are connected, beginning with ADWR_SW_APPL_REGRY.csv. ArizonaRights_Well55Registry: A folder containing a database of a single Shapefile and 59 associated CSVs. Wells55.pdf contains a visual flowchart of how the various files are connected, beginning with WellRegistry.shp. CaliforniaRights_eWRIMS_directDatabase: A folder containing a collection of four "series" Microsoft Excel files, as either XLS or XLSX. The four "series": byCounty, byEntity (what type of legal entity holds the right), byUse (stated water use), and byWatershed, are various methods by which the California water rights are organized within the state's database. However, it was observed that by only collecting a single series, not all water rights were being provided. So, essentially, the majority of records within each "series" are copies of each other, with each "series" containing some unique records. ColoradoRights_NetAmounts: A folder containing 78 CSV files, with one file per Colorado Water District. IdahoRights_PointOfDiversion: A Shapefile containing the Points of Diversion for the entire state of Idaho. IdahoRights_PlaceOfUse: A Shapefile containing the Place of Use polygons for the entire state of Idaho. MontanaRights_WaterRights: A Geodatabase file containing the Points of Diversion and Places of Use for the entire state of Montana. The name of the Points of Diversion Feature Layer within the Geodatabase is "WRDIV", and the name of the Places of Use Feature Layer is "WRPOU". NevadaRights_POD_Sites: A Shapefile containing the Points of Diversion for the entire state of Nevada. NewMexicoRights_Points_of_Diversion: A Shapefile containing the Points of Diversion for the entire state of New Mexico. OregonRights_state_shp: A folder containing 36 Shapefiles and are split between "pod" (Point of Diversion) and "pou" (Place of Use) for each water management basin within Oregon. In other words, each basin has one "pod" file and one "pou" file. The "pod" files are point shapes, and the "pou" files are polygons. UtahRights_Points_of_Diversion: A Shapefile containing the Points of Diversion for the entire state of Utah. WashingtonRights_WaterDiversions_ECY_NHD: A Geodatabase file containing both the Points of Diversion for the entire state of Washington. The name of the Feature Layer within the Geodatabase is "WaterDiversions_ECY_NHD". WyomingRights: A folder containing four subdirectories, one for each Wyoming Water Division. Each Division directory includes a varying number of subdirectories for each Wyoming Water District. Each District folder contains two copies of the Point of Diversion records for that area, with one copying being in CSV and one copy in Microsoft Excel XLS format.

Lisk, Matthew↗

Blockchain cybersecurity audit platform

A cybersecurity distributed ledger is provided herein for managing, tracking, auditing, and securing assets in a power infrastructure. The cybersecurity distributed ledger may include a blockchain, and may combine with smart contract or smart negotiation technology, such as in a permissioned proof of authority blockchain. The cybersecurity distributed ledger may manage the complete life cycle of a grid asset, from asset requirement and specification, through production, testing, deployment, maintenance, and retirement. The cybersecurity distributed ledger may create an immutable record of the grid asset, which may be audited for regulatory compliance or build or development compliance. Further, the cybersecurity distributed ledger may store unique identifying information for a grid asset, which may be used to detect a security breach or other tampering with a grid asset. The cybersecurity distributed ledger may also track control or ownership of the grid asset, as well as changes or updates to the grid asset.

Mylrea, Michael E.↗

HarDWR - Harmonized Water Rights Records

A dataset within the Harmonized Database of Western U.S. Water Rights (HarDWR). For a detailed description of the database, please see the meta-record v2.0. Changelog v2.0 - Recalculated based on data sourced from WestDAAT - Changed using a Site ID column to identify unique records to using aa combination of Site ID and Allocation ID - Removed the Water Management Area (WMA) column from the harmonized records. The replacement is a separate file which stores the relationship between allocations and WMAs. This allows for allocations to contribute to water right amounts to multiple WMAs during the subsequent cumulative process. - Added a column describing a water rights legal status - Added "Unspecified" was a water source category - Added an acre-foot (AF) column - Added a column for the classification of the right's owner v1.02 - Added a .RData file to the dataset as a convenience for anyone exploring our code. This is an internal file, and the one referenced in analysis scripts as the data objects are already in R data objects. v1.01 - Updated the names of each file with an ID number less than 3 digits to include leading 0s v1.0 - Initial public release Description Here we present an updated database of Western U.S. water right records. This database provides consistent unique identifiers for each water right record, and a consistent categorization scheme that puts each water right record into one of seven broad use categories. These data were instrumental in conducting a study of the multi-sector dynamics of inter-sectoral water allocation changes though water markets (Grogan et al., *in review*). Specifically, the data were formatted for use as input to a process-based hydrologic model, Water Balance Model (WBM), with a water rights module (Grogan et al., *in review*). While this specific study motivated the development of the database presented here, water management in the U.S. West is a rich area of study (e.g., Anderson and Woosly, 2005; Tidwell, 2014; Null and Prudencio, 2016; Carney et al., 2021) so releasing this database publicly with documentation and usage notes will enable other researchers to do further work on water management in the U.S. West. We produced the water rights database presented here in four main steps: (1) data collection, (2) data quality control, (3) data harmonization, and (4) generation of cumulative water rights curves. Each of steps (1)-(3) had to be completed in order to produce (4), the final product that was used in the modeling exercise in Grogan et al. (*in review*). All data in each step is associated with a spatial unit called a Water Management Area (WMA), which is the unit of water right administration utilized by the state in which the right came from. Steps (2) and (3) required use to make assumptions and interpretation, and to remove records from the raw data collection. We describe each of these assumptions and interpretations below so that other researchers can choose to implement alternative assumptions an interpretation as fits their research aims. Motivation for Changing Data Sources The most significant change has been a switch from collecting the raw water rights directly from each state to using the water rights records presented in WestDAAT, a product of the Water Data Exchange (WaDE) Program under the Western States Water Council (WSWC). One of the main reasons for this is that each state of interest is a member of the WSWC, meaning that WaDE is partially funded by these states, as well as many universities. As WestDAAT is also a database with consistent categorization, it has allowed us to spend less time on data collection and quality control and more time on answering research questions. This has included records from water right sources we had previously not known about when creating v1.0 of this database. The only major downside to utilizing the WestDAAT records as our raw data is that further updates are tied to when WestDAAT is updated, as some states update their public water right records daily. However, as our focus is on cumulative water amounts at the regional scale, it is unlikely most records updates would have a significant effect on our results. The structure of WestDAAT led to several important changes to how HarWR is formatted. The most significant change is that WaDE has calculated a field known as `SiteUUID`, which is a unique identifier for the Point of Diversion (POD), or where the water is drawn from. This separate from `AllocationNativeID`, which is the identifier for the allocation of water, or the amount of water associated with the water right. It should be noted that it is possible for a single site to have multiple allocations associated with it and for an allocation to be able to be extracted from multiple sites. The site-allocation structure has allowed us to adapt a more consistent, and hopefully more realistic, approach in organizing the water right records than we had with HarDWR v1.0. This was incredibly helpful as the raw data from many states had multiple water uses within a single field within a single row of their raw data, and it was not always clear if the first water use was the most important, or simply first alphabetically. WestDAAT has already addressed this data quality issue. Furthermore, with v1.0, when there were multiple records with the same water right ID, we selected the largest volume or flow amount and disregarded the rest. As WestDAAT was already a common structure for disparate data formats, we were better able to identify sites with multiple allocations and, perhaps more importantly, allocations with multiple sites. This is particularly helpful when an allocation has sites which cross WMA boundaries, instead of just assigning the full water amount to a single WMA we are now able to divide the amount of water between the number of relevant WMAs. As it is now possible to identify allocations with water used in multiple WMAs, it is no longer practical to store this information within a single column. Instead the stAllocationToWMATab.csv file was created, which is an allocation by WMA matrix containing the percent Place of Use area overlap with each WMA. We then use this percentage to divide the allocation's flow amount between the given WMAs during the cumulation process to hopefully provide more realistic totals of water use in each area. However, not every state provides areas of water use, so like HarDWR v1.0, a hierarchical decision tree was used to assign each allocation to a WMA. First, if a WMA could be identified based on the allocation ID, then that WMA was used; typically, when available, this applied to the entire state and no further steps were needed. Second was the spatial analysis of Place of Use to WMAs. Third was a spatial analysis of the POD locations to WMAs, with the assumption that allocation's POD is within the WMA it should belong to; if an allocation still had multiple WMAs based on its POD locations, then the allocation's flow amount would be divided equally between all WMAs. The fourth, and final, process was to include water allocations which spatially fell outside of the state WMA boundaries. This could be due to several reasons, such as coordinate errors / imprecision in the POD location, imprecision in the WMA boundaries, or rights attached with features, such as a reservoir, which crosses state boundaries. To include these records, we decided for any POD which was within one kilometer of the state's edge would be assigned to the nearest WMA. Other Changes WestDAAT has Allowed In addition to a more nuanced and consistent method of assigning water right's data to WMAs, there are other benefits gained from using the WestDAAT dataset. Among those is a consistent categorization of a water right's legal status. In HarDWR v1.0, legal status was effectively ignored, which led to many valid concerns about the quality of the database related to the amounts of water the rights allowed to be claimed. The main issue was that rights with legal status' such as "application withdrawn", "non-active", or "cancelled" were included within HarDWR v1.0. These, and other water rights status' which were deemed to not be in use have been removed from this version of the database. Another major change has been the addition of the "unspecified water source category. This is water that can come from either surface water or groundwater, or the source of which is unknown. The addition of this source category brings the total number of categories to three. Due to reviewer feedback, we decided to add the acre-foot (AF) column so that the data may be more applicable to a wider audience. We added the ownerClassification column so that the data may be more applicable to a wider audience. File Descriptions The dataset is a series of various files organized by state sub-directories. In addition, each file begins with the state's name, in case the file is separate from its sub-directory for some reason. After the state name is the text which describes the contents of the file. Here is each file described in detail. Note that st is a placeholder for the state's name. stFullRecords_HarmonizedRights.csv: A file of the complete water records for each state. The column headers for each of this type of file are: state - The name of the state to which the allocations belong to. FIPS - The two digit numeric state ID code. siteID - The site location ID for POD locations. A site may have multiple allocations, which are the actual amount of water which can be drawn. In a simplified hypothetical, a farm stead may have an allocation for "irrigation" and an allocation for "domestic" water use, but the water is drawn from the same pumping equipment. It should be noted that many of the site ID appear to have been added by WaDE, and therefore may not be recognized by a given state's water rights database. allocationID - The allocation ID for the water right. For most states this is the water right ID, and what is recommended to use should a right be looked up on a given state's water rights database. The water amounts associated with these IDs tend to be finer scaled than those associated with siteID. It should be noted that some allocations may be extracted from multiple sites, particularly for larger Places of Use. ownerClassification - A classification of the types of owners for water rights. The most common is `Private` which incorporates a wide range of entities. Several classifications would be grouped into a government category, most of which are for the U.S. Federal Government. These allocations could be listed as "Federal", "United States of America", or as the names of any number of federal agencies. The last major grouping of entities is for "Native American"s. priorityDate - The date we use as the water right priority date for our modeling analysis. This is the legal priority date when it is available. However, for some rights, specifically from California and New Mexico, we used a pseudo priority date (e.g. well completion date or start of well drilling date) when a legal priority date was not available. The most questionable dates come from New Mexico, where the only date associated with certain water right records was the date the allocation was recorded in the database. As the allocation record creation tended to be within a few months of the filing of the application of the water right, from manually double checking the water rights, and our analysis focuses on aggregating water rights on the timescale of years, we determined it was acceptable to use such dates to include as many records as possible. primaryBeneficialUse - From the numerous state water use categories, WaDE categorized them into 21 categories WestDAAT. This column is the original WaDE category for the primary water use at the PoD site. allocationBeneficialUse - From the numerous state water use categories, WaDE categorized them into 21 categories for WestDAAT. This column is the original WaDE category

Economics↗

Characterization of Precipitate Reactor Feed Tank (PRFT) Batches 15, 22, and 26 from the Defense Waste Processing Facility (DWPF)

The Savannah River Site (SRS) Defense Waste Processing Facility (DWPF) processes a Monosodium Titanate/Sludge Solids (MST/SS) waste stream received from the Salt Waste Processing Facility (SWPF) via the Precipitate Reactor Feed Tank (PRFT). During processing, DWPF is required to provide evidence of compliance with the Waste Acceptance Product Specifications (WAPS) to ensure acceptance of their vitrified high-level waste (HLW) into the Civilian Radioactive Waste Management System. Production Records must document the constituents of the MST/SS material in the PRFT from each salt batch (StB) processed at SWPF. Savannah River Mission Completion (SRMC) has requested Savannah River National Laboratory (SRNL) to analyze PRFT samples representing each SWPF salt batch for thirty-two radionuclides. Additionally, elemental analysis of PRFT slurry and MST/SS solids was performed to aid SRMC in further refinement of the inputs and assumptions used in future frit development and Material Tracking Program calculations. The analyses of PRFT Batches 15, 22, and 26, which corresponds to material from the processing of StB4, StB5, and StB7, respectively, are reported herein. The unwashed dried solids of the PRFT batches were found to be 86-87% MST. Additionally, the total sulfur values are well below the assumed 982 mg of sulfate/kg of PRFT slurry used in Material Tracking Program calculations.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Electrical Load Forecasting Over Multihop Smart Metering Networks With Federated Learning

Electric load forecasting is essential for power management and stability in smart grids. This is mainly achieved via advanced metering infrastructure, where smart meters (SMs) record household energy data. Traditional machine learning (ML) methods are often employed for load forecasting, but require data sharing, which raises data privacy concerns. Federated learning (FL) can address this issue by running distributed ML models at local SMs without data exchange. However, current FL-based approaches struggle to achieve efficient load forecasting due to imbalanced data distribution across heterogeneous SMs. Here, this article presents a novel personalized FL (PFL) method for high-quality load forecasting in metering networks. A meta-learning-based strategy is developed to address data heterogeneity at local SMs in the collaborative training of local load forecasting models. Moreover, to minimize the load forecasting delays in our PFL model, we study a new latency optimization problem based on optimal resource allocation at SMs. A theoretical convergence analysis is also conducted to provide insights into FL design for federated load forecasting. Extensive simulations from real-world datasets show that our method outperforms existing approaches regarding better load forecasting and reduced operational latency costs.

Rahman, Ratun [Univ. of Alabama, Huntsville, AL (U↗

Critical and Californium Source-Driven Noise Analysis Subcritical Measurements with an Unreflected Cylindrical Tank of Mixed Uranium-Plutonium Nitrate Solution

The reported experiments were performed by Oak Ridge National Laboratory (ORNL) at the Battelle Northwest Laboratory’s (now Pacific Northwest National Laboratory) critical experiments facility at Hanford, Washington in 1981 and used 16 days of critical facility time, not including 10 days for setup and removal of ORNL equipment. These measurements were to assess the capability of the Cf source-driven noise analysis (CSDNA) method to measure the subcriticality (keff) of mixed U-Pu nitrate solutions. In addition to the CSNDA measurements, measurements were also performed near delayed criticality where CSDNA measurements cannot be performed. This report documents the experiments that were not reported at that time by presenting the ORNL experimental results and any online analysis performed during and shortly after the measurements. The mixed nitrate solution had a U concentration at 188 grams per liter (g/L), a Pu concentration of 280 g/L, free acid normality of 2.80, H ion molarity of 5.9 and a specific gravity of 1.754 g/cm 3 , a 240 Pu isotopic content of 7.981 wt. %, and a 235 U isotopic content of 0.724 wt. %. The stainless-steel tank for the solution had an inside diameter of 35.38 cm, an outside diameter of 35.53 cm, a height of 56.72 cm, and bottom thickness of 0.9525 cm. A Zircaloy pipe with a 3.1496 cm outside diameter, a 2.7788 cm inside diameter, and bottom thickness of 0.635 cm was available for insertion of the Cf source in the center of the fissile solution. The Cf source was also located at the outside surface of the tank (solution height varied from 10 to 53 cm) and in the center of the solution (solution height varied from 10 to 60.7 cm). The CSDNA measurements were not analyzed online to determine the subcritical neutron multiplication factors. At all subcritical states, the break frequency noise analysis data was fitted to obtain the prompt neutron decay constant. The neutron multiplication factors were determined for the two configurations of the measurements near delayed criticality. The subcritical neutron multiplication factors from the CNSDA measurements can be obtained with further analysis. However, the near delayed critical configuration, the prompt neutron decay constants, the count rates, and the measured cross and auto power spectral densities can be calculated directly for benchmarking. Much of data presented in this report are from ORNL notes—not in the ORNL logbooks. For the final benchmark analysis, the data from the Battelle Northwest Laboratory (which operated the critical facility in 1981) critical facility logbook should be consulted and be incorporated where appropriate. The purpose of this report is to document the experimental information for the measurements performed so that at a later date researchers could perform the required uncertainty and calculational analyses and documentation to use these data for an International Criticality Safety Benchmark Program (ICSBEP) or Nuclear Energy Agency benchmark. The data from these measurements are available from the ORNL Records Management Services Department, and the logbook is available from ICSBEP at Idaho National Laboratory. Preparation of the present report is part of a larger cooperative effort between Idaho National Laboratory (INL) and Oak Ridge National Laboratory (ORNL) to document more than 15 undocumented critical and subcritical experiments enumerated in ORNL/TM-2019/18 and performed by ORNL at ORCEF and other USDOE critical experiments facilities using more than 500 operational days of critical facility time.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗