Through the wish to bring vendors on board with an open source SCT and to make it easy for other outsiders to participate Chris form OMICRON has extracted a core component from OpenSCD and call it OpenSCD core. With the help of this the rest of the ecosystem including CoMPAS functionality can be further modularized.
This page shall collect what work need to be done and what we are still missing to do this per plug-in.
Please fill in your insights what needs to be done. The lower the priority number, the higher the
| Prio | Plugin name | ToDos | Preconditions | Decisions needed | Status (done, in-progress, waiting) |
|---|---|---|---|---|---|
| 1 | CoMPAS open | tbd | tbd | waiting | |
| 1 | CoMPAS save | tbd | tbd | waiting | |
CoMPAS save as | tbd | tbd | waiting | ||
| 1 | CoMPAS compare | tbd | tbd | waiting | |
CoMPAS auto-align | tbd | tbd | waiting | ||
CoMPAS import CIM | tbd | tbd | waiting | ||
CoMPAS save as version | tbd | tbd | waiting | ||
CoMPAS OCL validation | tbd | tbd | Seperate plug-in since it is calling a back-end service | waiting | |
| 1 | CoMPAS export IED params | tbd | tbd | waiting | |
| 2 | Locomation VMU | tbd | tbd | Seperate plug-in since it is vendor specific | waiting |
| 1 | CoMPAS settings | tbd | tbd | waiting | |
| 1 | CoMPAS extentions | tbd | tbd | waiting | |
| 4 | OpenSCD 104 | tbd | tbd | waiting | |
| 2 | OpenSCD IED browser | tbd |
| waiting | |
| 2 | OpenSCD Substation editor | ||||
| 2 | OpenSCD single line diagram | ||||
| 6 | CoMPAS import from API | tbd | tbd | Do we need to keep this concept? Yes, but only for demo purposes | waiting |
| 3 | OpenSCD subscriber plug-in | tbd | tbd | ||
Example decisions:
How do we split the plug-in?
Maintainer / repository?