The UMEI defines a set of standard rules to enable an agnostic, adaptable, and modular combination of different APIs to link DSOs and market parties with flexibility market platforms, in coordination with other flexibility users.
This approach allows distributed communication without the need for a central hub.
In its current structure, the UMEI covers the following flexibility process phases:
OpenAPI [https://www.openapis.org] was used as the definition language. This is the most common and well-supported way of defining APIs accessible using the standard web technologies of today – JSON over HTTP.
Steps for the implementation:
The setup process for the implementation implies that there’s the possibility to have more than one hosting actor for the system, and no need for a mediation platform, making the UMEI a truly distributed data exchange interface. This makes the usage of the UMEI particularly straightforward for actors which act moslty as UMEI API clients (case of DSO and FSP), since they just need to invoke a API endpoint to send and retrieve information.
The UMEI prototype is already available on GitHub https://euniversal.github.io/umei-api-specification/
The UMEI is open to be used by any interested parties, being set as an open-source component to enable market based flexibility.
Updates to the specifications are already being developed in other research projects tackling TSO-DSO coordination and electric mobility. Developments can also be proposed by the users or potential new users, whenever new needs arise, since all can collaborate to its evolution, through the GitHub.
Further technical enhancements may include:
Questions / Suggestions / Collaborations > Contact us at email@example.com