The following principles are intended to guide the evolution and growth of the technical community and the ecosystem, over time. The living document can be found here.
- A group of 10 met four times to workshop ideas about principles and build alignment across members.
- The following document is a Version 1.0.
- The following principles received the highest votes from our second session on December 15th, 2020
- We then iterated as a group over the course of sessions three and four.
- There are additional principles that can be worked on over time.
- The Principles effort has been inspired by The TOGAF Standard, Version 9.2 - Architecture Principles (opengroup.org)
Without these principles, exclusions, favoritism, and inconsistency would rapidly undermine the growth and evolution of LF Energy
LF Energy initiatives and projects should seek to align with the principles
A conflict with a principle will be resolved through discussion and if necessary, changing the framework of the initiative
North Star Governing Principle
- Governance: The Governing Board will hold responsibility to the LF Energy community to ensure that the North Star Governing Principle is regularly reviewed for modifications or updates, and that these are handled in a timely manner.
North Star Governing Principle
This is the LF Energy steering principle
Support society and the planet
The LF Energy ecosystem is designed and engineered to support rapid decarbonization that benefits the environment, enables economic prosperity, and leads to social well-being for future generations.
To mitigate the worst of climate change, research scientists have concluded that power systems must lead global decarbonization efforts to remove fossil-fuel from our economies. Right behind power system transformation will be passenger vehicles, the built environment, and trucks. Together these interrelated efforts represent 75% of the carbon currently being emitted. Failure is not an option.
The goal of LF Energy is to enable this energy and power system transformation in a way that ensures both the health of the world’s economy and the health of people, the planet, and the well-being of future generations. Our mission is to provide a 21st century plan of action to respond to decarbonization of power systems, transportation, and buildings through open source, open frameworks, reference architectures, leveraged collaborative development, and a support ecosystem of complementary projects.
To enable open, global collaboration and cooperation around transforming economies to be carbon neutral, LF Energy recognizes that clean and renewable energy, power systems, and transportation are central to nearly every challenge and opportunity facing humanity. For this reason, LF Energy declares:
- Projects and working groups will support and not contradict the Universal Declaration of Human Rights.
- LF Energy projects will seek to ensure access to affordable, reliable, sustainable and modern energy for all people through alignment to the UN Sustainable Development Goals.
- Projects that do not contribute to the UN Sustainable Development Goals or that in some way violate the Universal Declaration of Human Rights will not be adopted into the LF Energy ecosystem.
- Governance: The TAC Chair holds responsibility to the TAC to ensure that the Principles are regularly reviewed and that needs for modifications or updates are handled in a timely manner.
- Statement: The following principles are intended to guide the evolution and growth of the technical community within LF Energy
Interoperability by default
Design and engineer for easy integration
The more it is interoperable, the easier it is adopted, the faster the community grows
- Consider interfaces as important as core feature.
- Clearly identify components that may be connected to the tool.
- Use internationally recognized standards, and where possible well governed, royalty-free and open standards are preferred.
- Use open source principles and open source licenses that allow for joint investment, and that include the right to modify and for source code, reference implementations, reference architectures, and other intellectual property to be shareable to ensure for long-term improvement, sustainability, and evolution.
|Resilience by design|
Design and engineer for continuous availability.
The energy transition leads to an increased share of renewable energy sources, resulting in more volatile and unpredictable power systems. This requires real-time situational awareness with minimal service interruptions.
- Minimize downtime (including planned maintenance)
- Design anti-fragile systems (anticipate failure)
- Design for automation
- Adopt software practices that enable scalability and resilience
|Simplify by design|
Design and engineer for simplicity.
Simple architectures are easier to communicate, build, deploy, operate, and evolve thus requiring lower costs.
- Simple is hard and requires a better understanding of the problem space, available technologies, experience with previous designs to eliminate unneeded complexity and ongoing effort to fight entropy over time.
- Avoid over-engineering today to pay off in the future at the same time balance to provide for the easy integration of near term capabilities.
- Avoid premature optimization and allow the design to emerge from known implementations.
- Focus on code that is directly supporting functionality that provides value that is differentiating for LF Energy.
- Strive for the Simplest Option:
Of two otherwise equal solutions, the simplest is usually better
Do the simplest thing that could possible work
Everything should be made as simple as possible, but not simpler
|Security and safety by design|
Design and engineer for security and safety
Security and safety must be a top priority from the start and cannot be bolted on afterwards.
Security and safety benefits include:
- It protects your and your customers businesses
- It protects personal information
- Allows employees and customers to work safely
- Inspire confidence in your solutions
- Security bowtie analysis & CII infrastructure best practice badge as a way of eliciting requirements for safety and reliability concerns.
- Security is based on identity and not location (zero-trust)
- Security in depth (multiple layers)
- Secure defaults; systems may never revert to insecure mode, e.g. in case of failure
- Use standards for authentication and authorization including federated identity protocols.
- Due diligence in terms of adding 3rd party components.
- Enable a full audit trail.