OpenSCD LFEnergy Project Proposal

Poroject proposal here: https://github.com/lf-energy/tac/issues/new?assignees=&labels=1-new-project-wg&projects=&template=02-new-project-proposal.yml&title=New+Project+Proposal+-+PROJECT+NAME

OpenSCD history: https://github.com/openscd/.github/blob/OpenSCDhistory/History.md

Thank you for looking to bring your project to the LF Energy Foundation. Please put the name of the project in the title above replacing PROJECT NAME, and then answer the questions below to have this project be added to the agenda at a future TAC meeting for consideration as a new project. Please refer to the guideance in the project lifecycle.
Please also note you must be available to lead this discussion on a TAC meeting. You can get information on TAC meetings and how to join the meetings at https://lf-energy.atlassian.net/wiki/display/HOME/Technical+Advisory+Council.


OpenSCD is a platform to enable fully digital substations - from design and commissioning through to maintenance and replacement


(what it does, why it is valuable, origin and history)

OpenSCD is an open-source, browser-based substation communication designer platform for editing IEC 61850 compatible Substation Configuration Language (SCL) files.

IEC 61850 is an international standard defining communication protocols, guidelines and datamodel for intelligent electronic devices (IED's) at electrical substations.

https://github.com/openscd/.github/blob/OpenSCDhistory/History.md


It is an existing project


Maintainers: Pascal Wilbrink - Alliander [https://github.com/pascalwilbrink] and Tamás Rusz - SprintEins [https://github.com/trusz]


Alliander, Omicron, Transpower, TransnetBW, SprintEins



( please refer to the lifecycle for project benefits )

Not for now; The current infrastructure/tooling options will fit for now.


OpenSCD is a good candidate because it fits perfectly together with the other projects classified as Digital Substation Automation Systems, like CoMPAS, SEAPATH and Fledge. OpenSCD joinin will increase the presence in this field.


It would make collaboration with other projects easier, it would be easier from a community perspective attracting developers to the project. The project would also benefit from a 'marketing' perspective, being able to use the LF Energy resources. Having a neutral collaboration organisation/infrastructure.


We would definitely like to remove barriers to adoption and for us that can be achieved by joining a larger foundation that trusted by many.


The need to adhere to the IEC61850 System configuration language standard without the use of proprietary software and therefore reducing vendor-locking.

The plug-in architecture makes it easy for organisations to build their own plug-in and therefore tailor their engineering process to their needs. It allows vendor to add their vendor specific knowledge in a seperate plug-in.

Browser based: No need to install and manage seperate executables.

Enable/disable plug-ins: Ability to enable only the plug-in that are needed.


The project aims to standardise the configuration of substations, reducing cost and speed of implementation. Many players in the field will be able to use this solution for free and having a large community to ask for feedback on specifc questions.


Digital Substation Automation Systems, like CoMPAS, SEAPATH and FLedge


DSO's - Distribution System Operators

TSO's - Transmission System Operatos

IED Vendors

Engineering/integration companies e.g. building systems for DSO/TSO etc.

Other IEC61850 SCL users (e.g. in the DER control domain)


See


If accepted and we can move ahead without having to care too much about administration and infrastructure we would love to focus on communicating the project and growing the community.


Apache 2.0


https://github.com/openscd/


Yes, on a monthly basis


https://github.com/openscd/.github/blob/main/profile/code_of_conduct.md


The (Technical) Steering Committee consists of product owners of the companies that work on the project. The two previously mentioned maintainers have the power to push some decisions, but in general decisions are made in an agile manner.


Not current; We try to reach consensus, if this turns out to be hard, the maintainers will make a decision.


No; Release are currently made ad-hoc


material, lit, ace-editor, panzoom, marked, open-wc standaard


https://github.com/openscd/open-scd/wiki Current

Home · openscd/open-scd Wiki (github.com)


No trademarks


No; Just a bunch of idea's:

Planned Features · Roadmap (github.com)

open-scd/ROADMAP.md at main · openscd/open-scd (github.com)


Yes


No


No; Search on Linkedin on OpenSCD for a white paper; The project is promoted by e.g. CoMPAS, Omicron and theirefore already known by a bunch of engineers.


Does this project compete with other open source projects or commercial products?

Commercial partly competing: Siemens SITIPE, HELINKS, ASE Inc/Kalkitech, IED vendor tools