Data Exchange Overview

Energy Web Data Exchange simplifies communication and business logic execution in complex markets by replacing heterogeneous point-to-point integrations among participants with a hub-and-spoke model in which all participants maintain a single integration to communicate with all other parties. Unlike conventional hub architectures that rely on a central broker to administer access and host the infrastructure, EW Data Exchange combines multiple open-source technologies to establish a shared platform that is owned, operated, and governed by multiple participants.

EW Data Exchange is tailored to execute high-volume, business-critical communications in electricity markets and e-mobility applications, but can be customized to support any business process involving data exchange between multiple organizations. Enterprise Data Exchange is protocol agnostic, and supports established standards including IEEE 2030.5, XML, OADR, and OCCP.

In its simplest form, Data Exchange is a secure, open-access messaging infrastructure that:

  • Allows multiple parties to send, receive, and authenticate messages based on the roles that have been issued to and associated with their self-managed identity;

  • Allows parties to exchange diverse datasets, ranging from real-time telemetry to bulk file uploads, in support of multiple DER and e-mobility use cases;

  • Provides end-to-end encryption for all messages and data transfers, using cryptographic signatures from self-managed identities;

  • Requires only a single integration mechanism with a central infrastructure in order to communicate via one:one (bilateral), one:many (broadcast), and many:many (multicast) channels.

Data Exchange can support a wide variety of use cases, including:

  • Coordinating DER installation data among installers grid operators

  • Streamlining DER registration in wholesale and/or local markets

  • Enabling seamless roaming and advanced tariffs for electric vehicles

  • Coordinating real-time grid operations between transmission and distribution system operators (operating envelopes, local constraints)

  • Facilitating customer switching between retailers in deregulated markets

  • Consolidating disparate market operations communications channels and processes (e.g. registration, nomination, bids/offers, dispatch, settlement)

  • Establishing dynamic registries for DERs and EVs

A use case is defined by a particular configuration of a messaging channel (i.e. who is allowed to read/write, how messages are routed) and data schema (the format, frequency, and logic governing messages). Thus Data Exchange is a practically infinitely customizable solution; much like the way a road supports many types of transportation (from cars, to bicycles, scooters, trucks, etc.) Data Exchange provides a foundation for many types of business processes in electricity markets.

Who is it for?

EW Data Exchange can be applied in any energy market context where many-to-many data exchanges are critical. Companies or consortia can design how user roles are defined and acquired; what data structures and protocols are supported; and what types of integration options are made available to participants.

  • Wholesale market & transmission system operators who need a solution to facilitate data exchange among market participants and distribution system operators in order.

  • Distribution utilities who need to coordinate local services and non-wires alternatives with multiple vendors or aggregators.

  • E-mobility service providers and charge point operators who want to reduce the cost and complexity of managing e-roaming and advanced charging programs.

  • Industry consortia

EW Data Exchange allows companies seeking to offer / build / operate market-wide data exchange hubs to define the following aspects:

  • Onboarding and issuing roles to organizations, systems, assets and users with DIDs, via the SSI-Hub

  • Configuring role-based permissions, conditions, and restrictions for users

  • Defining hosting and integration patterns (e.g. self-hosting clients, exposing APIs)

  • Establishing communication channels between participants

  • Scheduling jobs for batch processing and caching of data

  • Use the channels for passing data between participants

Last updated