Search NASA⌕ Search

SEARCH · Search NASA

Results for “Universal Utility Data Exchange”

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

Universal Utility Data Exchange (UUDEX) – Protocol Design - Rev 1

This design document describes protocol related aspects of Universal Utility Data Exchange (UUDEX). The focus of the design is to describe the interactions between UUDEX Clients and UUDEX Servers in the UUDEX Infrastructure. This design is purposely transport and programming language agnostic.

97 MATHEMATICS AND COMPUTING↗

Universal Utility Data Exchange (UUDEX) Initial Interview Results

The purpose of the Universal Utility Data Exchange (UUDEX) project is to develop a flexible utility communications protocol that can dynamically accommodate new data elements and new users partners while remaining secure. The first step toward the development of this tool is to understand data exchange requirements from stakeholders in the industry. Towards this end, we performed a survey of five different energy industry stakeholders. This document captures a summary of our initial findings.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Universal Utility Data Exchange (UUDEX): Information Exchange Models for Solar DER

This report describes how the Universal Utility Data Exchange (UUDEX) can encapsulate and exchange information about distributed energy resources (DER) within UUDEX-formatted JSON documents. It proposes to use the existing extensible markup language (XML) information exchange format described in IEEE Std 2030.5, IEEE Standard for Smart Energy Profile Application Protocol but not other information exchange provisions of IEEE 2030.5, rather, relying on equivalent mechanisms in UUDEX. This will allow adoption of the UUDEX exchanges with minimal changes to the structure of the information exchanged and will not require a modification to the UUDEX documentation if IEEE 2030.5 makes changes to the information models.

42 ENGINEERING↗

Universal Utility Data Exchange (UUDEX) - Workflow Design - Rev 1

This workflow design document describes the process of establishing a Universal Utility Data Exchange (UUDEX) Connection between two or more UUDEX Endpoints. The existing processes required to establish a data link using Inter Control Center Communications Protocol (ICCP) are very time consuming, from both the perspectives of effort and calendar time. The intent of UUDEX is to provide a more streamlined alternative. The UUDEX Workflow is also used to establish UUDEX Connections to exchange data other than that found in traditional ICCP data exchanges such as exchanges of power system model files, security events and mitigations, disturbance reports, and market data.

97 MATHEMATICS AND COMPUTING↗

Universal Utility Data Exchange (UUDEX): Information Exchange Models for Solar DER (Rev. 1)

This report describes how the Universal Utility Data Exchange (UUDEX) can encapsulate and exchange information about distributed energy resources (DER) within UUDEX-formatted JSON documents. It proposes to use the existing extensible markup language (XML) information exchange format described in IEEE Std 2030.5, IEEE Standard for Smart Energy Profile Application Protocol but not other information exchange provisions of IEEE 2030.5, rather, relying on equivalent mechanisms in UUDEX. This will allow adoption of the UUDEX exchanges with minimal changes to the structure of the information exchanged and will not require a modification to the UUDEX documentation if IEEE 2030.5 makes changes to the information models.

14 SOLAR ENERGY↗

Universal Utility Data Exchange Workflow Design

This workflow design document describes the process of establishing a Universal Utility Data Exchange (UUDEX) Connection between two or more UUDEX Endpoints. The existing processes required to establish a data link using Inter Control Center Communications Protocol (ICCP) are very time consuming, from both the perspectives of effort and calendar time. The intent of UUDEX is to provide a more streamlined alternative. The UUDEX Workflow is also used to establish UUDEX Connections to exchange data other than that found in traditional ICCP data exchanges such as exchanges of power system model files, security events and mitigations, disturbance reports, and market data.

97 MATHEMATICS AND COMPUTING↗

Universal Utility Data Exchange (UUDEX) – Security and Administration: Cybersecurity of Energy Delivery Systems (CEDS) Research and Development

A critical component of the Universal Utility Data Exchange (UUDEX) approach is the integrated security contained within its processing. This document describes how that security is designed and expected to be implemented by UUDEX Implementations (U-Implementations), including the UUDEX Server (U-Server) and UUDEX Clients (U-Clients). The UUDEX security hierarchy consists of three levels: 1. The UUDEX Instance (U-Instance) itself, which sits at the top of the hierarchy and contains the U-Server, the UUDEX Identity Authority (U-Identity Authority), and the UUDEX Administrator (U-Administrator) functions; 2. A group of one or more UUDEX Participants (U-Participants) that present “organizations” that participate in the U-Instance and contains the UUDEX Administrator Participant (U-U-Administrator Participant) function; 3. A group of one or more UUDEX Endpoints (U-Endpoints) that represent the individual UUDEX Publish Clients (U-Publish Client) responsible for supplying data to the U-Instance that is consumed by UUDEX Subscriber Clients (U-Subscriber Clients). U-Endpoints can be either autonomous devices that publish and subscribe data such as data exchange servers found in supervisory control and data acquisition and energy management systems, or they can be tied to users of applications that, for example, submit DOE OE-417 disturbance reports. U-Participants and U-Endpoints can be organized into UUDEX Groups (U-Groups). Any number of U-Participants or U-Endpoints can be members of a U-Group. A given U-Participant or U-Endpoint can be a member of multiple U-Groups, but a U-Group cannot contain other U-Groups. For example, a U-Group could be created to contain all U-Participant Transmission Operators within the purview of a Reliability Coordinator, and another U-Group could be created to contain all U-Participant Generator Operators within the purview of a Reliability Coordinator. U-Participants that are both Transmission Operators and Generator Operators would be members of both U-Groups. U-Participants, U-Endpoints, and U-Groups are used in the access control structures to provide access to individual UUDEX Subjects (U-Subjects). U-Groups are created by the U-Administrator and are managed by the U-Administrator or the designated U-Group Managers. U-Endpoints can be assigned UUDEX Roles (U-Roles) that can be used to further restrict access. U-Roles are assigned to individual U-Endpoints. For example, a U-Role of “Security Analyst” could be used to restrict which U-Endpoints can publish or subscribe security incident reports and vulnerability notifications, while a U-Role of “Transmission Planner” can be used to restrict which U-Endpoints can publish power system model updates. U-Role definitions are created by the U-Administrator, but the U-Roles are assigned to U-Endpoints by their respective UUDEX Participant Administrators (U-Participant Administrator). Because all information required to make security decisions is either included within the U-Endpoint’s X.509 digital certificate or stored in a datastore on the U-Server, all security decisions are performed and enforced within the U-Server. This reduces the complexity of the U-Client code and minimizes the chance for compromise of the integrity of the UUDEX security features.

97 MATHEMATICS AND COMPUTING↗

Universal Utility Data Exchange (UUDEX) Phase 4 Demonstration Environment and Results

This report provides an overview of the environment used by the Pacific Northwest National Laboratory (PNNL) in the Universal Utility Data Exchange (UUDEX) Phase 4 demonstration, and description of the demonstrations performed in the environment. The UUDX Phase 4 demonstration took place on March 31, 2021, with representatives from PNNL and the two project sub-contractors, OATI and MITRE, performing the demonstration for members of the UUDEX Industry Advisory Board (IAB). The demonstration tasks were based on the previous Phase 3 demonstration but conducted in a multi-site environment. Additional demonstrations showed features that were developed since the Phase 3 demonstration. The development environment was constructed by PNNL programming staff using the previously developed UUDEX Functional Design, Protocol Design, and Workflow Design documents as a starting point. The environment was augmented with subject creation management and access control security data structures and workflows, and data exchange structure documents developed as part of Phase 3 and Phase 4.

97 MATHEMATICS AND COMPUTING↗

Universal Utility Data Exchange (UUDEX) Functional Design Requirements - Rev 1

This document provides a set of high-level functional design requirements for Universal Utility Data Exchange (UUDEX). These requirements include a set of use cases, data exchanges supported by UUDEX, both for grid operations and for cyber security data, functional requirements for data exchange, data models used by UUDEX, data exchange architectures, and security considerations. These functional design requirements are intended to be used in more detailed design documents.

97 MATHEMATICS AND COMPUTING↗

Universal Utility Data Exchange (UUDEX) Functional Design Requirements: Cybersecurity of Energy Delivery Systems Research and Development

This document provides a set of high-level functional design requirements for Universal Utility Data Exchange (UUDEX). These requirements include a set of use cases, data exchanges supported by UUDEX, both for grid operations and for cyber security data, functional requirements for data exchange, data models used by UUDEX, data exchange architectures, and security considerations. These functional design requirements are intended to be used in more detailed design documents.

97 MATHEMATICS AND COMPUTING↗

Plant-Scale Concentration Column Designs for SHINE Target Solution Utilizing AG 1 Anion Exchange Resin

Argonne is assisting SHINE Medical Technologies (SHINE) in their efforts to develop SHINE, an accelerator-driven process that will utilize a uranyl-sulfate solution for the production of fission product Mo-99. An integral part of the process is the development of a column for the separation and recovery of Mo-99, followed by a concentration column to reduce the product volume from 15-25 L to <1 L. Argonne has collected data from batch studies and breakthrough column experiments to utilize the VERSE (Versatile Reaction Separation) simulation program (Purdue University) to design plant-scale product recovery and concentration processes.

38 RADIATION CHEMISTRY, RADIOCHEMISTRY, AND NUCLEA↗

COUPLING OF RELAP5-SCDAP MOD4.0 AND NEUTRONIC CODES

High-fidelity and accurate nuclear system codes play a key role in the design and analysis of complex nuclear power plants, which consist of multiple subsystems, such as the reactor core (and its fuel, burnable poisons, control elements, etc.), the reactor internal structures, the vessel, and the energy conversion subsystem and beyond to grid demand. Most commonly the interplay between these various subsystems is modeled using coupled codes, each of which represents one of the subsystems. And the most common direct coupling is that of thermal-hydraulics and neutronics codes. The subject of this paper is the coupling of codes that model not only thermal-hydraulics and neutronics, but also structural components damage. Furthermore, the neutronic component is not limited to the sole core solver. The coupled code system encompasses thermal-hydraulics, material performance of the fuel, neutronic solver, and neutronic data preparation. Thus, this paper presents a framework for coupling RELAP5/SCDAPSIM/MOD4.0 with a suite of neutron kinetics codes that includes NESTLE, DRAGON and a version of the ENDF library. The version of the RELAP5/SCDAPSIM/MOD4.0 code used in this work is one developed by Innovate System Software (ISS) as part of the international SCDAP Development and Training Program (SDTP) for best-estimate analysis to model reactor transients including severe accident phenomena. This RELAP5/SCDAPSIM/MOD4.0 code version is also capable of predicting nuclear fuel performance. It uses nodal power distributions to calculate mechanical and thermal parameters such as heat-up, oxidation and meltdown of fuel rods and control rods, the ballooning and rupture of fuel rod cladding, the release of fission products from fuel rods, and the disintegration of fuel rods into porous debris and molten material. On the neutronics side, this work uses the NESTLE and DRAGON codes. NESTLE is a multi-dimensional static and kinetic neutronic code developed at North Carolina State University. It solves up to four energy groups neutron diffusion equations utilizing the Nodal Expansion Method (NEM) in Cartesian or hexagonal geometry. The DRAGON code, developed at Ecole Polytechnique de Montreal, performs lattice physics calculations based on the neutron transport equation and is capable of using very fine energy group structures. In this work, we have developed a coupling approach to exchange data among the various modules. In the coupling process, the generated nuclear data (in fine multigroup energy structure) are collapsed down into two- or four-group energy structures for use in NESTLE. The neutron kinetics and thermal-hydraulics modules are coupled at each time step by using the cross-section data. The power distribution results of the neutronic calculations are transmitted to the thermal-hydraulics code. The spatial distribution of coolant density and the fuel-moderator temperature, which result from the thermal-hydraulic calculations, are transmitted back to the neutron kinetics codes and then the loop is closed using new neutronics results. Details of the actual data transfers will be described in the full length paper.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

A Community Energy Operations and Planning System: Concept, Use cases, Metrics, and Benefits

Community and city leaders are interested in achieving sustainability goals, providing resilient energy infrastructure, and improving economic competitiveness. Community-level data acquisition and analysis can provide energy and associated benefits that are not possible at the single building level. However, there is a lack of organizational structure, common semantic data models, interoperable systems, and methods to support data-driven decision-making for community-scale energy supply and demand systems. We explored the need and opportunity for a Community Energy Operations and Planning System (Community EOPS), a potential data exchange platform. We conducted “customer discovery” interviews, and reviewed literature, public tools, and technology platforms to identify key energy data “users” and use cases in communities. The key users of the Community EOPS could be developers of mixed-use districts, corporate, defense and university campus energy managers, and city managers of cities that own their energy utility. The value could be for community planning and reporting (for energy data-integrated land use planning and community infrastructure investments in microgrids, storage, district heating and cooling), energy efficiency (leveraging optimizations for community scale energy supply and demand), flexible load management (grid-edge load management to offset, shift, and flatten loads for multiple buildings and EV fleets), cost savings and revenue generation (participating in grid services), and social benefits such as energy resilience, equity, and awareness. We developed a conceptual Community EOPS architecture with recommendations for streamlined and prioritized data acquisition, sharing, and integration driven by prioritized use cases, common metrics, and actionable visualizations that can provide value to a community’s users.

Singh, Reshma↗