EOSC Beyond Workshops: Definition of EOSC Nodes and their federation, requirements for EOSC Core services from a use case perspective and integration activities.

Contribution List

3. 'Who is who' round table and workshop goals and objectives

10/06/2024, 12:00

Conceptual and Technical Definition of an EOSC Node

Hands-on: Round table and the introductory slides on the current view on EOSC Nodes Federation.

4. What do we need to define a node? Node's description areas. (node typology, stakeholders, offering, RoP, architecture, business models etc.)

10/06/2024, 12:40

Conceptual and Technical Definition of an EOSC Node

Hands-on: Common discussion on the pre-defined list of possible areas of description for an EOSC Node
Conceptual and Technical Definition of an EOSC Node:
What do we need to define a node? Node's description areas. (node typology, stakeholders, offering, RoP, architecture, business models etc.)

5. EOSC Node's stakeholder typology, node's offering typology.

10/06/2024, 15:00

Conceptual and Technical Definition of an EOSC Node

Hands-on: Split into 4 groups and work with the boards diving into the details of selected description areas. After one round of working in the groups per board - common discussion and summary of a possible way to describe chosen areas - > delivery of a template to describe a node.

6. EOSC Node's typology and possible technical architecture (Minimum Viable Node technical architecture). Final remarks and summary documentation.

10/06/2024, 16:40

Conceptual and Technical Definition of an EOSC Node

Hands-on: Split into 4 groups and work with the boards diving into the details of selected description areas. After one round of working in the groups per board - common discussion and summary of a possible way to describe chosen areas - > delivery of a template to describe a node.

14. Technical descriptions of the Pilot EOSC Node according to the common template from day 1 (Instruct-ERIC, LifeWatch,, NI4OS, e-INFRA CZ, NFDI, ENVRI)

11/06/2024, 10:00

Use cases definition

Hands-on: Working with the EOSC Node template inserted into the dedicated Google doc.

15. Technical descriptions of the Pilot EOSC Node according to the common template from day 1 (CNB-CSIC, ENES, MetroFood-RI, CESSDA, EGI, PaN, FC4E)

11/06/2024, 12:10

Use cases definition

Hands-on: Working with the EOSC Node template inserted into the dedicated Google doc.

9. Integrations with the EOSC Core and horizontal services (of the EU Node) and potential scaling scenarios using e-Infra nodes such as the EGI Node (which federating services will be integrated in what scope and for what resources)

11/06/2024, 15:00

Integration use cases

Integration matrix per use case (pilot Node) with timeline build on top of it. Seeking for the scenarios of scaling up with the EGI Node.
Start with one showcase (ENES) and then everyone works with their own material (online - google doc).

10. Integrations with the federating services and horizontal (of the EU Node) and potential scaling scenarios using e-Infra nodes such as the EGI Node (which Core services will be integrated in what scope and for what resources)

11/06/2024, 16:40

Integration use cases

Integration matrix per use case (pilot Node) with timeline build on top of it. Seeking for the scenarios of scaling up with the EGI Node.
Start with one showcase (ENES) and then everyone works with their own material (online - google doc).

11. Possible integrations and dependencies between Pilot EOSC Nodes (from EOSC Beyond and others gathered in the workshops)

12/06/2024, 10:30

EOSC Node Federation

‘Use case x Use case’ matrix where we mark possible integrations and express which federating services (who is the giver, who is the taker) might be the ground for it.

12. Provider Portal, Service Monitoring, Service Accounting, Research Products Accounting

12/06/2024, 12:20

Requirements for EOSC Core Services

1. (40 mins max)
Mural for user stories per use case, everyone working on their own user stories (3-4 most important user stories in around 10 groups)
2. (as long as needed)
Short intro of all gathered user stories. One registered user story will work as a showcase.Then, 3-4 groups working on their own user stories. As a result, user stories should be splitted into high-level...

13. AAI, Marketplace, Resource Catalogue, Order Management, Helpdesk, PiD Service

12/06/2024, 15:00

Requirements for EOSC Core Services

1. (40 mins max)
Mural for user stories per use case, everyone working on their own user stories (3-4 most important user stories in around 10 groups)
2. (as long as needed)
Short intro of all gathered user stories. One registered user story will work as a showcase.Then, 3-4 groups working on their own user stories. As a result, user stories should be splitted into high-level...

Back to the event