 session. It's time to start, I think the other will join, but we can shortly start. I hope you can see my screen now with a welcome presentation. This is session about focus on requirements collections in relation to EOS portal. I'm Thomas Shapines, I work in the SYNFORNET, I'm involved in the EOS hub from the part which is responsible for the marketplace and portal. Some few words to begin about the session. Please keep in mind that all the sessions, so also this one is recorded and the link to the recording will be available. Please do not activate microphones even if you have rights. The video option should be only for speakers. For the questions in the session, we activated Slido for the session, so the usual event name is EOS Hub Week, of course, and then you can select the session name and then you can ask the questions there and vote for the questions. We will have a Q&A session after each presentation, so you'll be able to ask questions there for those questions which are most voted. Also in the Slido there is a pool activated with additional questions as this idea to collect the additional information, so the session is small. We couldn't put all the contributions here, but we know there are many contributions relevant to this requirements collection actions around EOS portal. This pool will give you the option to contribute with your materials with your use cases collected and documented somewhere. The question in the pool is what are the existing materials that might be useful as a source of requirement for your portal, so please report there. Also you can put there the contact for the relevant people in your project or your initiatives, so this information will be gathered and passed to the ongoing actions on requirements collection. For the agenda today, we have four speakers. The first was meant to be Bartosby from SACFONET, but he contacted me yesterday evening that he had some rapid medical action with a child, so he cannot join. It's nothing serious, don't worry about him, but still he had to be and then in some places I couldn't connect, so he asked me to take over his presentation, so I will present the EOS portal developments in EOS Hub, a kind of contribution from the EOS Hub to the EOS portal. In fact, the agenda is building the way that we are starting with EOS portal to explain somehow where we are and we will end up with a specific EOS portal requirements collection process that are currently ongoing in EOS and HANS and this will be presented by Sara Garabelli and in the middle of the session we have two broader presentation which show the broader concept of requirements collection and collecting experience with working with people, so Garabelli Shippos will give us the overview of experience from research infrastructures and Marcin Puccini will give us the business perspective from the digital innovation hub that he was involved. So yeah, that's the four speakers, four presentations and as I said, after each presentation we will switch to Slido and read or give the author a right to ask the question and have a little discussion. All right, if you have some immediate stuff, especially technical, you can also put this in the chat. We have Diego with us that he is able to help. Okay, that's the introduction, so now I will switch to the first presentation which is given by me but the real author of this was Bartosz. I hope you see the slides. So the idea of this presentation is to show the EOS hub contribution to the EOS portal. I will show you also some some insight over how EOS portal was initially implemented without a source and how the different contributions fit into the whole concept of a portal. So again, I mean this was probably shown for a few times how we understand the EOS portal. It's a delivery channel that connects demand side and the supplier side with a context of all, as we say today, EOS resources. So services, data and other scientific outputs. So this meant to be kind of a helping place, a helping tool that connects the demand side and the supply side. So still I think in the current version of the portal which is available in EOS portal, you who forgot the URL, is that still like history is visible here and it's important that at November 2018 when we launched the portal there was a collaboration between different projects and so there was no single project that delivered this but a few different initiatives, different projects that contributed to the EOS portal in various ways. So from the technical part that was mostly visible was the an infra-central project and EOS hub and from then we had already existing catalog at the marketplace and also there was an EOS pilot who contributed a lot to the understanding the rules of participation and other materials and also OpenAir whose mission was focus on scientific data. But from the, I mean, portal point of view there was like two different places, catalog and the marketplace that have a separate set of services and slightly different understanding of them also. So the huge amount of energy was spent to create the integrated one which you can see now online. So you have an integrated view of catalog and the marketplace with combined standardized description of the services which are supplied together with both teams which are currently working together in EOS and Hans project. About EOS and Hans project we will learn slightly more on SAR presentation at the end and now it's important that the EOS portal is still very, I mean, converging into integrating the existing components and also trying to achieve the seamless experience. So now I will go through a few ideas that are contributions from the EOS hub project. So to understand this you may see that EOS hub project was always focused on the services and service delivery. So the idea of the marketplace with a full support of federated processes was always in the core of the EOS hub project. So that also the contribution to the EOS portal from EOS hub was mostly focused on services and some other partners contributed to the other parts as well. So the first important contribution was that besides the service description of the services that we have already already in the portal and it was also the standardized service description template was a contribution of an infrastructure later called developed. We also added service offers that was the configuration of the ordering. So those service offers make the services easier to grasp in a technical sense by specifying what exactly what are the conditions of the service delivery that can be adapted for the particular users or customers. So you can see that the service offer are displayed now for the for the services that of course had it because it's not obligation. I mean this is an extension so you can have a service in the market in the portal without or with offers. So the offers are connected with ordering. It works I think best with infrastructure services, with technical service and you have a lot of parameters which are purely technical. So what you can see now is a user view but also the portal offers and the parameterization from the suppliers. So this is configuration of the orders available for the provider. So the provider can modify the existing offers and manage them in the way they like. Also the interesting track and this is slightly related to the to the business perspective was a piloting something which is related to the pay for use models in the portal. So we implemented the use case with Halix Nebelov portraits which are also visible as an extension. So this mechanism is linked and also this was for piloting non-free offers that can be available in the use port. The other side of the contribution was to a kind of reaction for the many voices that researchers need to have some way to first group themselves together in the research teams and also that usually those teams require more than one service. They require plenty of different services that can work together for them. So that was the initial idea behind the research project. The project you can just create in the catalog and marketplace space. You can configure them, provide information so there will be this simplification of order regulator coming based on this information and you can see that in the project you can have a single user project which is just a personal project. Also you can configure a research group there and in future the idea is that it will be connected with a service provider to give the permission to use the resources on access. So when you create this you can add to the project various services that you need and track the state of ordering. Also for the projects, EOS Portal offers the support which is also embedded in the portal. So we are aware that this is kind of an initial step towards supporting research groups and this probably will involve in time into something more tangible and also more integrated with the service providers. As almost the last features, I have recently almost published the feature which is which is possibility to create a white label marketplaces. This is the answer for the ideas that maybe it's not a good idea to have an integrated marketplace in one place. But there might be an option to have a multiple constellation of the services as we say EOS is an integrated services and there is a lot of few levels of those integration. So white label marketplace is kind of a step in this direction. We can in the same scheme share the services and related processes because as I mentioned before EOS is focused on processes. So the providers that offers more than one service can create this the separate view and present it in the white label way. So we will with their own branding. But this is better if you're interested with this feature you can contact the EOS Hub team for this. There are also some other improvements like optimized user experience. There is a lot of work around this alignment with operational processes like capacity management like the issues management and so on. There is an API for ordering. So for the supplier that wants to manage orders the user can do this in a portal. But from this providers point of view there is API and also we have a reference implementation for this API. So it's almost directly you can go there and manage their orders. Also there was a feature added recently to compare between services based on the SDT. And the last one was developed in the frame of of enhance. So for the conclusions I want to stress here that and this is somehow visible from the from the results that EOS contribution to EOS portal was always focused on delivery of services. And that's why I'm in this so much focus on orders on the professional way to deal with operational processes. And that was the initial idea of the project. So of course we assess the user portal. It's always the value. It's mostly not in the portal itself. It's just an entry point or marketplace or something. But I mean the quality is in the services. So I think in the future EOS we should put a lot of attention on the quality of services and how they are supported, how they are delivered and so on. And then we can we can integrate them with a good quality. And my last remark at the end is that currently portal is COVID developed between EOS Hub and EOS Enhanced. This is a schema that both project contributed to the portal. EOS Hub is operating this. And for the for the requirements collection there is all people involved. I think they are aware that the new requirements comes. This is only the beginning and we defined the new phases of EOS. So the portal will also go in the direction to fit the understanding of EOS and the mobile users. Thank you. So now I can change my hack from presenter to the chair of the session. So we have a Q&A session. So maybe Sara can I ask you to share this session after the presentation? Yeah, you should see the Slido Q&A. So at the moment there are no questions in Slido. So please if you have any questions enter them on Slido. There was a comment in the chat from Sai. I don't know if you want to pick it up while people enter the question. I don't know if Sai you want to say you want to comment. Can you can you hear me okay? Yeah okay no it was just a comment because basically what one you mentioned pay for use and two we did have an issue with an ISO 27k training request that came through the system and requesting it and then I realized like later when I was kind of dealing with the ticket that the generic template made the training look as if it was free. So we had to kind of do an ad hoc update to the to the text on the portal so it didn't make it seem like the ISO 27k trainings that we offer and which then also applies to the finessem trainings that it shouldn't be made to seem like those were those were free services or sponsored services through the EOS or whatever. So it was kind of like a miscommunication that we ended up having to deal with the back end. So since you mentioned that you had this kind of pay for use prototype or proof of concept I was thinking well I might as well bring that up to the attention that maybe we can use the trainings also as a mechanism for testing the pay for use option. That was it. Yeah thanks for for rising this up. I think this shows that that the services related to the training need some special attention and probably they should be dealt with with a different way than the structure services. Okay I see I see the the question from from Anka and Nola mentioning the data search engine is missing. So I can answer on this. So this is true and this is perfect true and in fact the the questions the question or remark we have really we hear quite often and probably this is also the functionality that would contribute the most to the to the value to the portal. However I mean it's not there yet. Of course in the in the extension of the portal in the plan is this plan to integrate search engine but somehow the idea of portal development is that we are we are we are integrating something which is developed by some projects. So so from what I know the open areas is almost ready to to provide this contribution in some way. Okay Kostas can you can you maybe speak up and give the background of your question Yes um as you all know there's been a huge discussion about the resource or service description templates and they which is the um the required information that one needs to say provide in order to onboard the resources or services and yesterday there was a presentation by for the exactly by in the session about onboarding from Jorge Sanchez from Aos and Hans and he presented what the what is now called profiles the measurements 3.0 in essence this is the new version of the service description templates and there's been quite some discussion going around that we need to at some point let's say converge and use the same template it's in order to onboard services and present services in the portal or portals that then may exist. The the vision is that there is going to be a airscan and Hans and then by extension the the new project from if infrared zero three is going to produce a registry of all the resources including services data sets data providers everything described let's say with one common profile and from then onwards with extensions for its specific field for datasets for example and my question whether respect the portal is if you have a new roadmap or in your timeline when do you do you expect that you have you will have adopted the new profile version 3.0 okay so so so this uh template description which are it's evolving yeah that's that's the point i mean the new version was was announced quite recently and currently in the in the years and hence there is a discussion how to converge because i mean this is this convergence into the common template is i think on the way from from some kind of time and we are and and the convergence was was achieved on the previous version of services different template but we have new one now so it will take time to to to to implement i don't i can give you the the specific date because it's not decided yet but it's it's still on the agenda how quickly we should adapt this into the the portal and how what how the migration should should work okay um i think we need to uh switch to uh do another uh another presentation maybe maybe at the end of the session we'll take uh additional questions that just appeared okay so i'd like to introduce uh uh gary elixipos who will give us the the the overview as i said a little bit broader the a little bit broader perspective on the on the eosk uh and the and the eosk and the portal at the effect portal this perspective comes from the eosk experience on working with research thank you can you see my slides yes i can see yeah okay great so thank you for inviting me for this session i will give a brief overview of the experiences we had in eosk hub concerning the work with research infrastructures and particularly working with them in the work package eight uh which i coordinate and which is titled uh competence centers and let me show you what i'm going to talk about so i will talk about what are the competence centers and how they fit into eosk hub then the working approach that we adopted in the competence centers to work and engage with uh research infrastructure research infrastructures and focusing on the use cases they had for the project and the requirements that we captured and how we captured them i will show two specific use cases from two of the competence centers one from atmospheric physics the other is from earth sciences seismology and i will close with with the summary so let me start with the introduction of the competence centers in eosk hub which as i said it's a dedicated work package work package eight and the main purpose of the competence centers is to be a kind of playground or test ground for research infrastructures to integrate services with the so-called federation and common services stack of the eosk hub project this federation and common services stack includes roughly four areas which you can see here federation services uh concerning user authentication authorization accounting of use monitoring of service availability reliability some added value services and basic infrastructure services that all fit more into the handling big compute big storage and data management in open science and then some kind of repository and additional services that help providers share items and distribute items towards their audiences the competence centers integrate with these federation and common services in order to co-develop what we call thematic service which is basically a science discipline specific online service that's available through the eosk portal for users for uptake so the ultimate goal of the competence centers is to see which of these underlying federation and common services fit for their particular use case do the testing do the integration and then push out these thematic services into the eosk space for uptake within different disciplines in parallel with that or as part of this for the competence centers also deliver kind of promotion and training in order to engage with early adopters test users from whom they can gather feedback they can gather design guidances requirements for the further development to take those on board and then to deliver the final products through the eosk portal so ultimately the lifecycle of competence centers is to set up and run proof of concepts with integration of these common and federation services conduct pilots with the involvement of early adopter users prepare the production environments and then right now we are working with many of those on defining business models for the operation of these services beyond the end of the eosk hub project so who are the competence centers or what subject areas they cover they started with eight competence centers in 2018 at the start of eosk hub these competence centers have been selected through an open process that was conducted during the preparation of the eosk hub proposal through this open call we received more than 30 applications many from research infrastructures from the S3 landscape and we selected eight of those competence centers into the proposal actually they covered 10 research groups because the marine links to two research groups as well as the icos eotr fit into a carbon cycle competence center so you have one of these research groups you can see here that many link to the S3 landmark or S3 projects from the european research infrastructure landscape and in terms of the coverage these eight competence centers cover 36 institutes and they each more or less correspond to one full-time equivalent or roughly 32 person months for the three years of the project you can see here that we have a kind of balance between our coverage of life sciences physical sciences environmental sciences and energy sciences but you can see that earth sciences or environmental sciences dominate the landscape besides these eight pre-selected competence centers we also onboarded 2019 early 2020-2013 additional early adopter pilots which act very similarly to competence centers they will integrate or are integrating with the common and federation services in order to deliver thematic services so how we do the work in the project actually so each competence center is basically a group of institutes that is a mix of different expertise on one hand we have pure science or research institutes who more or less define the use cases and define requirements we have service providers which are expert on specific common or federation services that are required for that particular community thematic service and we have software providers or call them technology providers who are able to further develop certain software code in order to fit into the thematic service and what each of these small consortia did in work package eight or are doing in work package eight we started with service planning and design which I said was already based on a pre-selection of competence centers in the proposal preparation so we had already a relatively good understanding of the use cases and the systems that these competence centers want to put in place but we further refined those through regular teleconference and face-to-face meetings we capture those use cases on confluence pages which form a so-called community requirement database which is a database we set up in 2018 we allocated one confluence page for each of the competence centers these confluence pages capture exactly the same structure for each competence center which is basically what's the ambition of the scientific community in the project what are the use cases that define the work plan the use cases basically cover the scientific challenges that the community is facing break those scientific challenges into IT challenges and data management and challenges and then map those challenges onto specific services in the portfolio of YOSCUB and articulate specific requirements that we know are there to satisfy the use cases and these requirements can be either technical requirements in terms of functionality usability of a service or can be capacity requirements which just scaling up the back end of a certain provider and also capture the validation plan so after these requirements are met how the system will be validated so we work with each of the competence center on the setup of such requirement database entries and we capture the technical and capacity requirements in JIRA tickets that are linked to each of these entries so confluence and JIRA were the main tools that we use for the requirement gathering extraction and refinement and these were the tools that we use to interface this activity with the other work packages of the project where there are additional providers and developers who can help us resolve these requirements through this work through this iterative work we produced first the page itself the the conference pages and the JIRA tickets and then we worked on the setup of the proof of concepts which basically meant that these thematic services started to be integrated with the different common and federation services offered by the project and here I show you a snapshot of what we call a service integration matrix or service assessment matrix that we keep as a live document where we indicate with different colors the interest of a certain competence center in the different common and federation services offered by the project you can see these services are are covering compute data and AI areas and also there are services from outside the project and the different colors I will show you later what they mean but basically indicate how a community is moving forward with the integration the testing the validation of a certain technology in its own tech in its own thematic service setup if you are interested you can read about this approach you can read the content of these use cases and requirements and also have a snapshot of this service integration matrix in the deliverable 8.1 which was published I think in January February this year and you can find a link on the web page the ultimate goal as I said is to validate working setups working integrations and to push thematic services into the ESC space and such thematic services have been already pushed from three from four competent centers from the fusion a Scott marine and disaster mitigation and additional compute services are also made available studio's portal from three of the elixir compute sites so let me just zoom a bit into each of the competent centers the eight competent centers to give you a glimpse of the challenges the use cases that they defined for the project in order to show you the diversity of cases that we had to work with and also to show you the diversity or a mix of the underlying services that were considered or are considered by these competent centers to integrate with so the elixir competent center aims to establish a federation of cloud resources across the elixir nodes in order to have them replicate elixir core data sets and applications into the different nodes in order to to innate the user access within the elixir countries the fusion competent center is working on computational workflows that should be deployed on federated compute resources that pull data together from federated data environments from federated repositories that have been accumulating data for many many years in the different fusion centers the modern competence center which includes two groups the uroga and cdata net have slightly different use cases the uroga use case is having a data what they call subscription service where users can subscribe themselves to data that meets certain criteria or characteristics and the system should deliver those into their personal data space for access and then computation the cdata net community aims to set up a virtual research environment in in a infrastructure service cloud to gather data from different this distributed repositories from the c domain and then have them perform computation on top of those federated data the eskat 3d competence center is setting up or set up already basically a web portal which operates as a i like to refer to that as a data webshop where users can search data based on metadata can put them into a kind of a shopping cart then check out the data either for download onto the client computer or download them into a cloud environment where they can run computational applications on top of that checked out data the iposaurus competence center is working with seismic data centers which need to be able to replicate data among themselves and need to enable users to pull data into a computational environment which is based on jupiter in order to perform custom analysis the radio astronomy competence center wants to do a similar setup but working on predefined workflows that the users scientists can choose from in order to transform instrument data into higher level science ready data products the icos and elter competence center which is two different groups posted in atmospheric research the icos community integrated an icos web portal with analysis tools and compute resources and data staging resources to enable compute analysis the elter is experimenting with jupiter and defines workflows in jupiter that users can re-execute with their own data or data pulled or imported from community repositories and finally the disaster mitigation competence center set up a number of web portals that they use to simulate or resimulate historical natural hazard events in order to better understand the reasons behind why certain events occurred or occurred in a way that we experienced so that's the kind of diversity of use cases we have and let me just show two examples if i have time two examples of competence centers in terms of what requirements they had so one is the asca 3d which i mentioned as a data web portal which looks like this it's available already through the elter portal and this web interface provides the users on one hand with the data search capability where users can find data based on some metadata characteristics they can then feed this data into compute engines where they can run calculations and then browse the final results of the calculations which for example can look like this which showing the the enter of certain particles into the upper layers of the atmosphere and this system or this community to achieve this system articulated earlier during the project four requirements one is to integrate the direct web portal engine with the eos compatible ai service the second one to integrate certain chinese and japanese idps in order to enable their collaborators from those countries to access the portal and this capability in a controlled manner they required allocation of virtual machine images and capacity behind the portal and they required pid service for the user data and for the raw data that goes through the portal there are a number of open questions still remaining for the remaining half year or one year of the project on one hand is how to complicate the metadata structure to enable different layers of metadata as as we move through pipelines the second is to how to procure and secure cloud resources for beyond the project as now the project is co-funding the the procurement the provisioning of cloud so if you're interested you can try this or apply for access in this portal through the through the eos marketplace the second example i have is from the epos orpheus community which works with basically two sets of providers on one hand there are the seismic data centers with which gather seismic data from a large number hundreds of seismic stations that cover whole europe there are four large data centers in the consortium and there are compute centers which offer cpu storage for the user analysis of those seismic data and the challenge of this competence center is to provide a data staging layer or service or architecture that the seismic centers can use to on one hand replicate data between each other in order to make the same data set available everywhere and to enable the staging of data right into their partner compute centers where the end users the scientists can access those data to perform custom analysis the other challenge is to enable the users to enter through a single entry point which provides a harmonized and harmonious access to different compute centers irrespective of their location and setup this entry point is foreseen to be a jupiter notebook which can federate data for the compute center from the respective data centers and provide an overall and overarching view on the seismic data from the whole landscape there are a number of services that are integrated here and basically irons and b2 safe integration with jupiter was the main requirement here uh customizing jupiter in such a way that custom libraries apis are available was a was another requirement and the third one is how to mount personalized folders into jupiter to show a customized user specifically for each other right now the different elements are more or less integrated the question now which is still open is how to harmonize the view for the user so there is a seamless experience for everyone irrespective of the compute center that they are using so let me go back to the service assessment matrix and let me finish with that one which is showing a bigger view of how compact compact centers are integrating with the different services and here you can see that basically each cell can transition from gray through yellow to blue to red or green which indicates the success of technology integration and validation or or technology wasn't found suitable and here you can see also which compact centers already produced services in eosk okay let me close with this last slide which basically just shows that in terms of the requirement management and capturing we relied on conference and jira and a lot of meetings to to refine those and to hand those over the first results are already available from the project which are services available in the eosk portal these rely on five common services from the common services stack and gathered already a number of views and orders that are handled by the respective provider teams so thank you thank you very for this for this presentation and we are switching now for the for the marching Puchenny to be uh we will skip just for for i mean i'm saying this just watching to start sharing screen on the slide there is no new questions to to gargay especially because those are those after previous presentation okay there is one um Anka can i ask you to to speak up and and write a question yes hello can you hear me hi Anka um hi well i think that question is kind of clear um i i check very fast now the this report 8.1 which gives some general examples of what the users feedback were but i was wondering if we if we could get some sort of detailed feedbacks from the users from you are they available or or so uh right now that the 8.1 was user the kind of community requirements from each competent center these kind of use cases that i explained yeah the final results of each of these competent centers will be in a d 8.2 deliverable which is due later this year in that one we will have more details on the experiences that the competent center users had with the integrations so it's coming okay great thank thank you very much that was all thank you i think i i think also that the use cases that the gargay shows showed that we have a very very large need to integrate the infrastructure services with the with the portals and with other stuff but now it's time to switch to to marching presentation about quite different perspectives business perspective on on yours and can you hear me well from from digital innovation i think we can hear you okay thank you so my name is marchin butchening i'm from posna super computing networking center and i'm at the eos dih business pilot coordinator and together with site that is also present in this session we work in dih so uh basically i will give just short introduction to digital innovation hub and to do to our activities and what kind of business pilots we have and and then i will move to pilots requirements and some conclusions lessons learned okay so since i i think looking at the list of the participants not everybody were yesterday doing our session we discussed the digital innovation hub itself so just just to introduce this is an ecosystem of a startup SME start industries also researchers and this foster creation of partnership and stimulate innovation so that's the main goal of digital innovation hub so basically digital innovation hubs as per as for the name has has been here for i would say last two years two three years where this this was created according to co-commission european commission definition but this kind of activities has been here in this area for last 20 years in kind of clusters or or ict clusters or or other other innovation initiatives okay so what are the the dih service needs so first of all if you look at this this is first uh the companies was wanted to test before invest they want to find the support for the new funds they are looking for skills and training in different technologies and and different services and and they are also looking for the innovation ecosystem and the networking where this is the world of innovators right so so our so the goal of digital innovation hub is to create such such ecosystem that enables this for main features so if you look into what is the role of industry in eos so there are different perspectives one is the customer so it's really about making use of existing eos services another is to become an provider so so to offer a new service new new added value service and and innovation through through the eos so in this case the services would need to be onboarded then it is about the partner partnership and co-development of new services so you can imagine that that these new services combine the company services plus some eos services and resources and final this is about the procurement or participating in procurement process so about the eos digital innovation hub so this has been created from the scratch in the eos hub project and it builds on on the easy initiative and so this is joint effort from years of this kind of activities from different individual infrastructure that came together and so we mainly focus on the innovators of startups at the miss but not only so in our focus the larger industry larger players as well so so we started in the project with six business pilots where they came during the initial project stage that helped us to define better and this digital innovation hub and to try out a few and and work out a few procedures so to start up the the age and so basically the idea is to persist the age beyond the life of this project and the different support projects like eos hub and this this is the longer term initiative so basically what we are doing we are offering the the access to different infrastructure resources and services we are facilitating the different partnerships and we are also kind of industrial engagement channel for for different also for other easy related projects in this area and there's a lot a lot of activities related to business coaching with accelerating with with finding funding opportunities and helping with developing more long-term business relationships and plans and and exploitations so for the current stage we work in with different actors so we've so we work out several partnerships to to kind of boost different services a usage of different services and to to to extend our portfolio so later on I will show the example of one of this very successful initiative with the hybrid data cloud where we define together one of the one of the pilot so we work together with several providers and also we partnership in larger networks of basically mainly of of other the ages in in Europe and and not only so basically our six initial pilots came from different domains so they are really spread over different scenarios it is about the at the seaport space weather data is about what mitigation and engine so in this case the rate of security is about data analysis related to sport to to to furniture area also some other area so this again as I said this this was the way to to start with and to work out all the procedures and mechanisms and we had a lot of lessons learned from these first six pilots so basically after this stage we have onboarded another five business pilots from again different domains and with different perspectives and requirements and one of these is like bbc so you see we were also with with the large large players but one of the example is here to be inside a pilot it's thanks through partnership with another project with the hybrid data cloud project where they bring in some of the services like machine learning deep learning and we bring the resources and knowledge and some other services we combine that with the offer of the company and I think they have also here a poster and a demo so it could be seen what what they are doing in details but okay okay so coming to to the requirements what are the pilot requirements so basically this is where they did the initial requirements from the initial pilot so to test by the solution scaling the cloud environment to move basically for someone to move to cloud environment to try test offered services of eos understand what is the real value of what is besides all the marketing let's say buzzwords what is the real things behind to build new solutions that will make use of selected your services and then they rise interest in but this is the initial pilot so in something that was obvious for them or more easy to understand so cloud resources machine learning data deep learning services testing data management solutions so many of other services were not that easy to understand like like this kind of of of mentioned services so it required well more more explanation and it's not it was not enough just to read the portal let's say description about this so it's it's also because these initial pilots were when the eos cap was starting we started month one and there was not really much offer available a month one of the project so also they are interesting marketing dissemination solutions towards eos users so now what we are doing we are expanding service offering and usage to to diverse eos services and so we are promoting services for different partnerships and also we are we are trying to gather the requirements from new pilots and and we've contacted companies okay and some open points there came so from from discussing with them so it is understanding which of the service can be used by industrial partners it's not trivial to understand which so this this relates to whole chain from resource providers to services because behind this service is usually it needs also several different resources and sometimes even if the service is available for the company the resource provider are not willing really to to do to provide this the for example on necessary services also what are the rules for for them to use this service so what are there are if you look into service availability portal many of them are saying okay we are available for business usage but in terms of usage there's nothing but potential commercial usage business cases nothing so it's not clear how and in which conditions and maybe some of them can be used in piloting phase that's in validation maybe pre-commercial and can those services be used in commercial matter or not if so what are the rules costs and can they be used for the companies for the r&d activities for example that they want to try it out and develop new new things so another point if they get a voucher for services usage can they get immediate response of of it's a value per service so let's say we say okay you get a voucher for I don't know 10k worth service of years and they ask okay I want this and this and this service okay from the portal but how much does it cost in terms of this voucher so they are not really maybe paying but it's in value that it should be quantified right and well the things like click and go so basically can I really just they are comparing what is available here with the offers of different service providers you know that are available and and well most of the things that we have here is not click and go it's click and wait one two three four weeks and yeah so that's it's not I think the best maybe best understood environment for them so what is the level of reliability and accessibility of the provided services are the are there data sets available so and 40 services are the similar services interoperable can I try one and then exchange with another and make some benchmarking of that or can I how can I compare it and so another another point on that is can I compose the service really of two free subservices are they compatible this is not very very clear for for them and like AI things like standards if this is the same standard can I still use both services and where can I how can I understand that some lessons learned so it's a moving target and that really does not help and use happy is also really moving target and it's you know it's it is not trivial we are dealing here with the innovators and their value services ideas and it's also so the communication between pilots and project members it's you know many of project related aspects are not always well understood I would say and and and they're really we are into word of eos and there are so many buzzwords and terminology that are really very unclear in in for the SMEs and that leads to many confusions and so also availability of issues with the resources so in general they have higher expectations I think then in I would say for scientific users maybe it's not well maybe not but yeah probably it's the case also they the general issues that are comparing us with the the eos and its services to commercials over something market and and and I think that's that's the kind of an issue and we always explain in our ending slide that if you can buy something with the credit card easily then you just go there and and and this this kind of eos design innovation hub and and eos it's not it's not maybe for you if you just need I don't know I ask if you just need virtual machines things like that but if you need added value services that's why it takes more time and there are complex services but still they are still all the time comparing us and this is also important point about response time like in the commercial providers you have dashboards you do click click click click and you have it and here okay this is a matter of of okay even if you order something through portal do you really get it in a moment or or not and and it's also the feedback we got it's not really trivial to understand what the eos really offers and how to compare different tools available so by standard supporters available features so is this an automatic way common criteria to facilitate such comparison so this is this is you know not clear for them okay and that's it and thank you and I would be happy to answer any of the questions thank you Marcin we've shown you've asked this perspective from from from business partners I think we have a time for a question I see there is a question from from Michelle Michelle can maybe it will be easier if you just yeah sure yeah thank you for giving me the opportunity I noticed there was some really interesting use cases in there in the deal I have the digital innovation hub presentation and thank you for sharing those I wondered there is a potential risk that private or industrial organizations might seek to utilize eosk resources or or or participating pilots only to benefit from from free resources that would reduce the costs of their R&D in quite a cynical way BC in particular is a very well funded organization and I wonder is there is is that risk being mitigated are they and other pilot participants able to offer value to the to the eosk or to the digital innovation hub in return for their participation yeah so basically we started with some of the pilots that were looking you know for these free cloud resources plus some other value services but it was the initial stage where really the the offers from the eosk hub or from eosk were not really yet very well defined and we have had to start from something right so that was the easiest way you know to start with but now what we are looking for the next pilots it's mostly about the co-development and this is mostly about you know working out new added value services where where the eosk services are part would be a part of okay what are the business let's say kind of business model this depends case to case and we are now in the phase of defining kind of pre-commercial agreements with them and kind of SLAs to understand this and so that's one point and but we are not clearly we are not really interested in just offering like I don't know storage or cloud resources and that's that's what I said also that if they can just go and buy it easily they it's we are not the the one that they should deal with right so I hope that this responds to your your questions and we are also open because you you ask how can participate and so we are open we are we have for example we had recently the open call where we are giving out vouchers and we are asking specifically for using several of these services and we have like 16 interested applications for that and we are in evaluation phase now thank you we do move to the to the next presentation I see that there is a few questions and in fact the the topics for discussion on Slido most of them are related to the to the previous presentation so just I think we can keep continue to discuss on this and then we at the end of the discussion will find time to to to best vote at topic to to to discuss the game and now I like to you introduce the Sarah and Sarah will give us the overview of the of the process of requirements collection that are currently starting in yours and hence which is a new project that takes the development of the world. Thanks Thomas good morning everyone so I'm Sargara Belli from trust city services and today here I'm representing the Yoscanans project and so actually I see that we have online Carmela Azzaro who is the project coordinator for Yoscanans I don't know Carmela if you want to say a couple of words about the project before I start well thank you Sarah can you hear me yes okay perfect so thank you very much for giving the floor so Yoscanans is a recent project and started in December 2019 and it is the first project which had let's say dedicated funding for the Yosporta since the first version of the Yosporta came to life from a collaboration between existing projects namely the infrascentral which ended last summer led by Efis and Yoscap coordinated by EGI the portal of course reflected in this first version the fact that it was the result of this collaboration which was for open air participate and so the structure of the portal was for some time building on two pillars the Yoscap marketplace and the catalog catalog of service developed by infrascentral so now one of the first tasks of Yoscanans is really to integrate let's say and recreate the portal and their unique architecture which we are going to finalize and also to review a bit the description of the specifications for providers of the resources of any kind so ranging from data and computing services and pain services so to ease the to facilitate both for the provider to provision and to offer services to the portal for the user to discover and use the service offer they will run until the end of 2021 this project we will onboard the new services and especially the thematic platform and some S3 services and now Sarah will talk to you about the parallel collection of requirements new requirements and then there will be a follow-up projects which will progress in further developing the portal so namely it will be the resulting project from the infrascentral Yoscap 03 and 07 calls which are going to close in the next few weeks thank you thanks Carmela for this introduction so as Carmela said so one of the objective of Anansi is to increase the user demand so the requirements collection is a fundamental aspect of this project and as she said we have just started and what we have done in this month was to put together a process to collect new requirements not only collect them but also validate them and prioritize them because of course we have a two-year work plan and we need to understand what are the priorities that we should address in this short time the process is steered by Yoscan Anansi but clearly the Yoscap project and open air are strongly collaborating with us and this process will involve different instruments and we have identified two phases for the requirements collection so one the first phase is for 2020 and the target audience for these requirements collection are mainly the Yosca related projects and namely the 5b project which are the regional projects the clusters in the somatic clouds and implementation projects in phase two 2021 we will we want to outreach also to individual researchers and scientists representatives from academia and other stakeholders so why this two phase approach because we are fully aware that there are still some things and some functionalities that needs to be fixed or improved before exposing the portal to a wider audience and because we have already collected some feedback in the previous stakeholder engagement events we continuously receive some questions from the project so that's why we decided to start first from the people that are really involved in the development and then move to the actual end users of the of the portal the topics for the requirements collection are covering the all portal starting from general portal announcements from each perspective and deepening into the finding the resources on the Yos portal so how people can discover and access the services how they can use the resources on the Yos portal so we are talking about ordering system help desk and so on but also how to make resources available by the Yos portal so the service onboarding procedures accounting procedures and so on as well as the general training on the portal uh on this slide so i'm not going to the details but just to inform you that uh at this point in time we have a built a process that will allow Yos can answer to have in place a continuous requirements ingestion for the project but also a system to provide feedback to those that are expressing some requirements there are different actors involved in this process and in particular and i want to put the focus on the reviewers team so this team is built is made up by representatives of the project partners and the project is participated by the infrastructure projects but also by the clusters and the idea is that these reviewers team will be in charge of prioritizing and assessing the feasibility of the requirements to build really a roadmap for the short long term development the service owners are also important players in this process because they really are those with the knowledge about the feasibility and where we can move the new implementations and clearly well the development team and finally last but not least the testers and for these we will seek um testers also from the communities so we really want to engage all the stakeholders to try out the features that are implemented to collect feedback and potential announcements uh how we are going to do that um so in the next weeks we are going to publish a permanent web form on the us portal so this will be a feature that everybody and browsing the portal will be able to use to provide some feedback or some request for new features and this is something that we're going to the process that i've shown before then we will have a more structured approach with the use related projects and we have prepared a questionnaire targeting different roles that are part of these that we can find in the use related projects both from the end users but also from the service providers side this questionnaire will address will be run in forms of interviews and will be done in the timeframe between May and July this year and what are we going to do with the results of the interviews so clearly they will use the results will be analyzed by the use can answer requirements gathering passports and the outputs of these analysis will be a set a series of requirements that will be put on into a roadmap and clearly also the participants of the questionnaire will be involved in these phases and then what's next in addition to the questioners and the structure interviews we will have a series of workshop we have already done the first workshop with the regional projects last week and we have this session today to kick off this activity as well and then we have already planned the workshop with the cluster projects to really focusing on collecting input for new features of the portal another mean that we're going to use to engage the stakeholders will be the US Secretariat interest group on the service and research product catalogs so these will be our way also to reach out to the community to inform the community about the new developments and to gather their feedback and these close my presentation so I think I can go back to the slider then thank you Sarah for this for this presentation I think this is this is very important to include in this in this process also all researchers not the organized infrastructures only and things that that somehow are very organized but also include the researchers which are spread around universities yeah absolutely I don't see the specific question to to Sarah so I think we can spend like maybe three more minutes to answer the most water question and this this is not a surprise about data searching gene because this is I believe really the most uh wanted feature so the so the discussion that Katrina started was about what will be exactly the the model for for the searching because so we can see two different different options and we can try to make a integrated search or just keep the links to the to the repositories and you know some other places so if I may take this question and share my field my personal feelings about the discussion that we are having now in the in the different groups I think the situation looks like and the the appetite for the functionality is is like between saying the links are not enough because the the links are not adding value to the discoverability of the uh with the useful sources but from other hand fully integrated search it's expected to be uh to be uh expensive in implementation and also unclear how how value how much values can can happen so I mean the usual people say I mean the Google Google already did that yeah and the usability is it's not so so I think there is a still discussion on how to find the the better way between those two extreme and also as as it replies mentioned uh I mean there is an ongoing discussion if eos will be like a more integrated or more federated and only linked together so it's not only about the search and g but uh but I think uh this is a general discussion of of of eos itself how much integration we need and what what what level of integration is this possible I don't know if if some other people want to review about this okay so thanks for this session thanks to all the speakers for the presentations and discussion I have we have few other subjects on sliders so we can keep uh this discussing this in slide though also I see the uh there are four replies to the pool so thank you for for for this contribution and uh yes again thank you for participation this this is open to the session