Make a planning for open sourcing of NBIlity

[PrinceAlliander]

Background work and discussions :

1. Stakeholders a. Wie zijn ons stakeholder (binnen en buiten Alliander) ? b. Licentie keuze - de adoptie dremple voor ons beoogd users zo laag mogelijk houden. c. Transitie maken vanaf openbaar naar open source. d. Ons target audience zijn NBN, DSO/TSO's andere europese landen and bedrijven in het energie sector.

2. What is the expected timeline for making the Nbility project opensource - End 2023

3. What parts of Nbility would we like to open sources a. In essentie - alles -maar in een phased manier b. Wat zijn de fases dan ?

4. What the pro and cons for making Nbility

5. What contributions do we expect from the community - stap 2 -

6. Which community events are applicable and relevant

7. Besides Alliander what is the view, and vision from other partners to make Nbility open source - allee DSO + Netbeheer Nederlands

8. Make a bi-weekly meeting with Alliander collegaues (in the beginning) to consult and review the planning

[PrinceAlliander]

Work packages

• Core Capablities
• Enterprise Capabilities
• Value Streams (Waarde stroom)
• Core Capabilities per value stream
• Enterprise capabiltie per value streams
• Business Objects
• Mapping between other standards
• Release Note (on webiste and landing page)
• Use cases and examples

Strategy and Planning

1. Based on the phased release approach. In November 2023 we can make the core capabilities and enterprise capabilities models open sources. My assumption of work is that based on the already existing .xml files for these capabilities (version 2.1.1) we can import the files in Archi. After that we proceed further (i.e., publishing, versioning and collaborating) just as we do for other open source projects like LFE. To be completed - 2 Nov. 2023
2. Repository website and the landing page - The text (release notes, defintions etc.) in Nbility 2.1. presentation can be used as inspiration for an introductory explanation. - 16 Nov. 2023
3. Two use case - to make it easier for the communuity to understand, apply and give feedback - we can add two use uses. One each for the core and enterprise capabilities. - 30 Nov. 2023

Notes Bi -weekly status update meeting Involve external stakeholders - other (inter)national TSO, DSO, scientific organisations I am not aware of the paper work or formal process when making a project open source so the time and effort required for that is not in the planning Core working and discussions group ?

[PrinceAlliander]

Actions w.r.t the Strategy and Planning action written above.

1. In line with our plan of making releasing the Nbility framework in a phased manner, one strategy is to have a first release consisting of only Core capabilities and Enterprise Capabilities.

• Action done (one branch made - dedicated to core and enterprise capabilities). The branch is called OS_release_1, corresponding to Open Source Release 1. Problem - not able to make changes and commit.

2. To do. A part of this work has already is done by colleague. Proposal (Slide 54 to 57 of Nbility-Model-2.1.pptx) have Rationales behind Nbility model (generic and specific) - can these be added to the pages on GitHub ? Which pages ? The original text is in english and has to be translated into English.

3. Discuss what should be in the use case ? Considering we are opensourcing core and enterprise capabilities for the first release, the use case should encompase these two aspects only. It would be ideal to start with a simple use case for example; the Financial Compensation process to the CSP (congestion service provider market party) and link it to the core and enterprise capabilities which this process support. Another example could be the Operate congestion management (Run process) of System operations, which supports/realizes many capabilities. In the coming months as we release more aspects of the Nbility model the same use case can be used to explain the newly released aspects. Open questions ?

   • Feedback over the case ?
   • Where will the textual description of the case be written down ?
   • Post the use case on the GitHub website ?
   • Model the use case (i.e., the link between processes and capabilities) in the Archi branch.