-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OneNet Framework #112
Comments
Hello, @pativar. Would April 23 work for you? Can you provide me with names and emails for those who will present? |
@pativar. Please let me know if you still have interest in presenting and if 4/23 works. You can register for the meeting here: https://zoom-lfx.platform.linuxfoundation.org/meeting/95214651568?password=eda16f17-bdd1-4a9f-a594-0947a1433153 |
@pativar, are you still interested in presenting this? We are now booked for 4/23 but I can find another time. |
Hi, Sorry but I did not notice this question until now. |
Presenter will be from |
Hello @yarille, what time will the meeting take place? in the registration form I see 17.00 but without the time zone. Thanks! |
Approved by TAC vote on 5/14. |
Mission Statement
To provide a middleware and data connector supporting secure and controllable data exchange among grid operators and also other market players.
Description
OneNet Framework: the core layer of the OneNet Architecture. It consists of four main components:
i) OneNet Decentralized Middleware,
ii) OneNet Connector
iii) OneNet Orchestration Workbench,
iv) OneNet Monitoring and Analytics Dashboard.
The OneNet Framework combines the International Data Spaces principles with the advantages of the FIWARE ecosystem ensuring a seamless and secure data exchange in a completely end-to-end decentralized approach.
The OneNet Decentralized Middleware is the core component of the OneNet system. It is implemented using a decentralized approach based on the more used and promising standard architecture and interfaces, namely IDS and FIWARE. It allows the integration and collaboration of the OneNet participants, facilitating the cross-platform market and network operations, ensuring scalability and interoperability, while maintaining the data ownership.
The OneNet Connector is ready-to-go for being deployed and integrated in any already existing platform and offers user-friendly interfaces (both as REST APIs and GUI), enabling users and platforms to exchange data. In addition, the OneNet Connector offers a pre-defined, dynamically evolving list of Cross Platform Services, Business Objects and corresponding Data Profiles is available enabling semantic and data interoperability.
OneNet Decentralized Middleware and OneNet Connector are strictly linked. The Decentralized Middleware is the middleware that enables the identification of Connectors as well the creation of services and catalogues. The Connector enables the data exchange in an end-to-end way; thus the Connector can be perceived as the main entry point for Energy stakeholders for participating in the data space ecosystem through the integration of the decentralized middleware features and then enabling a complete decentralized end-to-end data exchange.
The OneNet Orchestration Workbench is one of the components of the OneNet system. It acts as a data orchestrator to evaluate the performance and scalability of the cross-platform services that aims to use near real-time IoT metering and Big Data at consumer and/or network level.
The OneNet Monitoring and Analytics Dashboard is a comprehensive cybersecurity tool designed to enhance security through analytics within the OneNet Interoperable Network of Platforms. Core features include a data analytics dashboard that displays various information regarding connector usage arranged in a number of charts. The dashboard also offers the ability to generate a security report based on the results of the anomaly detection algorithm and to use the advanced filtering tool to query any connector logs which fulfil certain criteria. Finally, it provides alerting functionality as well as administrative and configuration tools for OneNet participants through the account management page.
Is this a new project or an existing one?
This project is currently active within a European Project, OneNet. More projects will continue and expand the work: Interstore, Enershare, TwinEU, ENFLATE, WeForming, iStentore.
Current lead(s)
Engineering spa, European Dynamics, Ubitech Energy, Fraunhofer FIT
Sponsoring organization(s), along with any other key contributing individuals and/or organizations
• EUROPEAN DYNAMICS
• ENGINEERING SPA
• UBITECH ENERGY
• FRAUNHOFER FIT
Detail any existing community infrastructure, including:
https://www.onenet-project.eu/ (Project website)
Onenet (eurodyn.com) (Middleware test instance)
OneNet Monitoring and Analytics Dashboard
european-dynamics-rnd/OneNet (github.com) - Connector Project Github – to be complemented with the rest of the components
Are there any specific infrastructure needs or requests outside of what is provided normally by LF Energy ? If so please detail them.
No.
Why would this be a good candidate for inclusion in LF Energy?
OneNet will provide integration of all the actors in the electricity network across Europe to create the conditions for a synergistic operation that optimizes the overall energy system while creating an open and fair market structure. One of the key elements of the project structure was the establishment of a Common IT Architecture and Common IT Interfaces, which resulted in the development of the OneNet system, a software-based approach to harmonize data-exchange between stakeholders.
How would this benefit from inclusion in LF Energy?
Joining LF Energy would help continue and expand the solutions started in the OneNet project, making them more scalable and useful for everyday industry operations. This move would support the energy sector's needs, including, for instance, the development and establishment of new flexibility markets.
Provide a statement on alignment with the mission in the LF Energy charter.
The alignment between LF Energy's mission and the OneNet project centres on promoting open-source solutions and standards for energy systems. As LFE focuses on supporting projects that enhance energy generation, transmission, distribution, and infrastructure, which aligns with OneNet's goal of integrating European electricity network actors through a common IT architecture to optimize the energy system and market. Both aim to improve the sector's efficiency and interoperability, making OneNet a fitting inclusion for LF Energy.
What specific need does this project address?
The project addresses the need for a decentralized edge-level middleware layer to enable secure and reliable data exchange among various energy stakeholders within the OneNet interoperable network of platforms. It aims to integrate actors in the electricity network across Europe.
Describe how this project impacts the energy industry.
This project impacts the energy industry by providing a scalable and technology-agnostic architecture that allows for seamless integration and data exchange across the European electrical system. The project fosters an open market structure, enabling universal stakeholder participation and the development of new customer-centric business models.
Describe how this project intersects with other LF Energy projects/working groups/special interest groups.
The OneNet Framework may bring complementarity to other projects which are part of the LFE, especially in the area of flexibility and ancillary services mobilisation and provisioning. Additionally, it may explore synergies from other advanced stage projects in other to maximize the possibility for widespread adoption.
Who are the potential benefactors of this project?
The project may be of interest for many stakeholders within the electricity sector, namely system operators (transmission and distribution), Flexibility Service Provides, Market Operators, Utilities, Research Institutions, among others.
What other organizations in the world should be interested in this project?
Energy sector stakeholders, including utility companies, technology providers, regulatory bodies, and renewable energy providers, should be interested in the OneNet project due to its focus on creating an interoperable network for optimizing energy system.
Plan for growing in maturity if accepted within LF Energy
The OneNet Framework will be further developed in upcoming EU projects.
Project license
Is the project's code available now? If so provide a link to the code location.
Yes. https://github.com/european-dynamics-rnd/OneNet
Does this project have ongoing public (or private) technical meetings?
Private project meetings.
Does this project's community venues have a code of conduct? If so, please provide a link to it?
Plan to adopt LF Energy code of conduct (https://www.lfenergy.org/community/code-of-conduct/)
Describe the project's leadership team and decision-making process.
None yet.
Does this project have public governance (more than just one organization)?
None yet.
Does this project have a development schedule and/or release schedule?
None yet.
Does this project have dependencies on other open source projects? Which ones?
TRUE Connector (https://github.com/Engineering-Research-and-Development/true-connector)
FIWARE Context Broker (https://github.com/FIWARE/context.Orion-LD)
Docker
Describe the project's documentation.
The documentation includes:
Public results include:
Describe any trademarks associated with the project.
None to our knowledge.
Do you have a project roadmap? If so please attach or provide a link.
Not yet.
Are this project's roadmap and meeting minutes public posted?
Not yet.
Does this project have a legal entity and/or registered trademarks?
No.
Has this project been announced or promoted in any press?
The OneNet Middleware/Connector software is one of the results of the OneNet EU H2020 project. The H2020 project has been promoted on the website (https://www.onenet-project.eu/), newsletters and conferences.
Does this project compete with other open source projects or commercial products?
Other energy data space projects (e.g., EDC Connector).
The text was updated successfully, but these errors were encountered: