-
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
Open Renewable Energy System (ORES) Working Group #107
Comments
Hi @chrisxie-fw, thanks for this proposal! There is a standard we are working with, called S2, which might be a great fit here, to model energy flexibility offers and usage between assets and (home or microgrid) energy management systems. "S2 is an open standard to unlock flex in the electricity grid. It is our ambition that all devices larger than 1 kW will support the S2 standard." It is now an accepted standard on EU level and put forward by TNO (also part of the Interflex project whihc is mentioned in the report you linked) and the Flexible power Alliance (FAN). It has now also endorsed by ECOS (an environmental lobby organisation putting their weight behind standards). And there is already open source development: We (Seita BV, also maintainers of another LF Energy project) are currently working with TNO on a few projects which hopefully demonstrate how to implement S2 in behind-the-meter EMS systems and drive implementation forward. We'll also need the OEMs to implement it on their (asset) end - one large heat pump manufacturer is already on board. Anyway, on the technical end we have implemented S2 message encoding in two places:
|
Hi @chrisxie-fw - we've put this on the schedule for March 12th; let us know if this timing works for you. |
Thank you very much for the feedback! IEC 61850 seems to be primarily a standard for grid substations and not specifically designed for residential renewable energy solutions. Its primary application is in the automation, communication, and integration of systems within electrical substations and across the wider electricity grid, particularly in the context of large-scale power systems. For residential renewable energy solutions, such as small-scale solar panels or wind turbines, different standards and protocols are typically used. These standards would focus more on the safe and efficient integration of renewable energy sources into the home's electrical system and, in some cases, into the local grid. They would cover aspects like inverter specifications, energy storage, interconnection with the grid, and safety standards. ORES would initially focus on these areas. |
https://github.com/FlexMeasures/ is interesting. We'll see if it can be leveraged in ORES. For S2 (EN50491-12-2), what are the differences between CEM (Customer Energy Manager) and RM (Resource Manager)? Is CEM on the customer premise (residential house), and RM is on the Utility/Grid side, or the other way around? ORES may explore OpenADR (Open Automated Demand Response) protocol, IEEE 2030.5 (Smart Energy Profile) and SunSpec Modbus to communicate to Utility side. |
@chrisxie-fw The resource manager (RM) is on the asset, the customer energy manager (CEM) aggregates them on some higher level, e.g. building or neighborhood. We would appreciate work that uses FlexMeasures in OpenADR contexts. S2 and OpenADR could also be useful in tandem (S2 focusing on implicit energy flexibility on sites, and OpenADR being used to leverage explicit energy flexibility towards grid-level actors, like aggregators) |
Approved by TAC vote- 3/12/2024 |
Mission Statement
To revolutionize the residential renewable energy sector by developing an open standard architecture, APIs, and protocols, fostering innovation, accessibility, and sustainability.
Description
Background
The formation of the Open Renewable Energy System (ORES) Working Group is a follow-up endeavor that stems from the insights of the LF Research whitepaper "The Open Source Opportunity for Microgrids: Five Ways to Drive Innovation and Overcome Market Barriers for Energy Resilience." In light of the considerable potential for open source solutions in areas such as Microgrids, Virtual Power Plants, and Distributed Energy Resources, Futurewei has taken the initiative to develop a thoughtful and innovative architecture for ORES. This includes designing a power network topology, block diagrams, functional requirements, and core design principles. Supported by community interest, this effort led to the creation of the ORES Working Group within LF Energy.
Objective
ORES aims to develop an open standard architecture, API, and protocol for renewable energy systems, initially for residential use cases. This project seeks to provide an open alternative to the dominance of proprietary black box energy solutions and promote a more open, innovative, and collaborative approach in the renewable energy sector.
Initial Contribution
Futurewei will contribute the initial project design specifications, architecture, API specifications, and protocols to the LF Energy community. Furthermore, Futurewei will sponsor a hardware vendor to further develop the specification, and to further design and implement these standards, providing a reference implementation of the ORES standard.
Problem Statement
The residential renewable energy sector is currently hindered by several key issues:
Description
ORES aims to address these challenges by developing a set of easy-to-follow open standard specifications on system architecture, APIs, and communication protocols that empower device manufacturers, hardware and software developers, and DIYers to implement their own disaggregated, easy-to-use and plug-and-play renewable energy solutions, initially for residential use cases, and potentially expand to commercial and industrial usage scenarios in the future.
Is this a new project or an existing one?
New project
Current lead(s)
Sponsoring organization(s), along with any other key contributing individuals and/or organizations
Futurewei
Detail any existing community infrastructure, including:
None
Are there any specific infrastructure needs or requests outside of what is provided normally by LF Energy ? If so please detail them.
None
Why would this be a good candidate for inclusion in LF Energy?
The Open Renewable Energy System (ORES) is a suitable candidate for LF Energy inclusion due to several key factors:
Overall, ORES's inclusion in LF Energy would support the shared goal of promoting sustainable and innovative energy solutions through open source collaboration.
How would this benefit from inclusion in LF Energy?
Inclusion in LF Energy offers several key benefits to the Open Renewable Energy System (ORES):
Provide a statement on alignment with the mission in the LF Energy charter.
The Open Renewable Energy System (ORES) closely aligns with the mission outlined in the LF Energy charter, as it seeks to:
What specific need does this project address?
The ORES project addresses specific needs in the renewable energy sector by:
Describe how this project impacts the energy industry.
The ORES project impacts the energy industry by:
Describe how this project intersects with other LF Energy projects/working groups/special interest groups.
The ORES project intersects with other LF Energy projects, working groups, and special interest groups in several ways:
Who are the potential benefactors of this project?
The potential benefactors of the ORES project include:
What other organizations in the world should be interested in this project?
Organizations that should be interested in the ORES project include:
Plan for growing in maturity if accepted within LF Energy
If accepted within LF Energy, the ORES project can grow in maturity through the following plan:
Community Engagement and Expansion:
Technical Development and Iteration:
Collaborative Projects with LF Energy Members:
Visibility and Advocacy:
Policy Influence and Regulatory Alignment:
Demonstration Projects and Case Studies:
Feedback Loop and Continuous Improvement:
Educational Outreach:
Expected deliverables
Key Deliverables
Working Group Detailed Operation Plan
Timeline for the working group
Timeline/Roadmap
The text was updated successfully, but these errors were encountered: