×

Frequently Asked Questions

About EOSC marketplace

EOSC Portal Catalogue and Marketplace provides a platform which enables different kinds of users, with different skills and interests to discover, access, use and reuse a broad spectrum of EOSC Resources. It not only does offer advanced compute and data services from publicly-funded and commercial organisations, it also allows researchers and institutions to focus on value creation and increase excellence of research and European competitiveness. From the supplier side, the EOSC Portal Catalogue and Marketplace offers local, national and international providers the opportunity to advertise their own services and resources to a broader community.
The EOSC marketplace is free of charge for everyone. We are committed to making the EOSC Portal Catalogue and Marketplace as accessible as possible to the scientific community. Services provided via the EOSC Portal Catalogue and Marketplace are expected to be free of charge at the point of use. But the service providers are free to define the pricing model for their services which is visible to the end-users via the EOSC Portal Catalogue and Marketplace.
If you are European scientists, EEOSC Portal Catalogue and Marketplace also helps you to find scientific service providers and services, allowing you to access technologies that are not available at your institution or better elsewhere and optimise your ability to use existing European solutions that can be useful in your research and research collaboration. You can also obtain assistance from international technical teams on the most suitable solutions If you are a Service provider, EOSC Portal Catalogue and Marketplace allows you to showcase your technology and promote services among European researchers and private companies. Get access to experience and tools supporting professional service delivery. If you are SMEs representatives, EOSC Portal Catalogue and Marketplace can help to discover available European services and be able to use them in R&D teams. If you are EOSC representatives, EOSC Portal Catalogue and Marketplace can help provide valuable European services with those who can use them to achieve meaningful scientific results and participate to increase scientific discovery in Europe.
The EOSC Portal Catalogue and Marketplace helps to develop synergy in data handling between research infrastructures, optimise technological implementation thus contributing to the development of a consistent European research infrastructures ecosystem and ensure integration and interoperability of data and tools within the EOSC.
EOSC Portal Catalogue and Marketplace is a worldwide platform. Each service is indicated with the countries/regions in which it is available to the users. It may be used in 'Europe' or Worldwide' or list individual two letter country codes using the tab with 'ISO Country Codes'.

Registration and Account Settings

In case you want to access technologies or obtain assistance from the international technical teams on the most suitable solutions, you need to log in via available services. There are different mechanisms to authenticate users and to grant appropriate access levels. The Marketplace is tightly integrated with already available services from both EUDAT and EGI infrastructure (e.g. Service Portfolio Management Tool, Operational Tools, GOCDB).
Current roles in the system:
  • Unregistered user
  • Registered user
  • Service owner / service provider
  • Admin
The primary difference is that an unregistered account doesn't have login credentials associated with it. This effectively means that we don't know who you are and your profile is restricted from certain actions. An unregistered users don’t have the possibility to fully use the EOSC marketplace functionality. Such functionalities as the service catalog and possibility to ask a question about the service is the same for Registered and Unregistered Users. But Only Registered Users have access to the ordering process, modification and possibility to create a project.
To become a registered you should Login to the EOSC Portal using checkin IDP.
The Marketplace is tightly integrated with already available services from both EUDAT and EGI infrastructure, so in case you want to change your profile information, it should be done on the infrastructure which is used while you log in to the Marketplace.
There is no set up account in the Marketplace. You log in to the platform by using already existing accounts. So there is no physical account in the Marketplace to be deleted.

Services in the EOSC Portal Catalogue and Marketplace

Service is a way to provide value to customers through bringing about results that they want to achieve. Services are in general related with all kinds of products, because they “manage” them and requires instantiation by a Service Provider.
  • For Sharing & Discovery: Services to search and discover data, publications, tools and other resources useful for your research.
  • For Processing & Analysis: Software, platforms, tools, analytics and end-user applications offered-as-a-service or deployed-on-demand also specialised by discipline or research domain.
  • For Compute: Services to access virtual machines, containers and job processing to support your general computing needs.
  • For Storage: Service for storing your data.
  • For Data Management: Service to manage your data.
  • For Networking: Services for Ultra-fast connectivity and ubiquitous access to eInfrastructures resources.
  • For Training & Support: Service that helps you to grow your research knowledge and skills with specialised training or seek dedicated professional support for a wide range of scientific disciplines and research activities.
  • For Security & Operations: Services that helps to integrate identity management, authorisation to comply with the policies and regulations or access services to support the operations of your infrastructures and services.
We have 3 types of services access:  Open access, external ordering type, internal ordering type.
  • Open access - services is open to everyone, no login required. The user is immediately redirected to the services and no orders are created. The access ‘requests’ are tracked for accounting aim. 
  • External ordering - service orders are handled externally, but access requests coming from EOSC-hub can be tracked and reflected in the Management Back Office. Access to the service can be granted automatically after sending the request. 
  • Internal ordering - identity of a user is required (user has to be logged in in the EOSC Portal to get access to the service). Service requires submitting a service request with filled in information relevant from provider’s perspective. Access has to be granted manually after analysis of the request.
Technology Readiness Level (TRL) is a means of systematically gauging the maturity of a technology. It is used to describe the maturity of underlying technologies rather than the delivery of them in the form of a service to end users. In addition to this, an end service may be the union of multiple subcomponents, each based on various technologies with differing levels of maturity.
Resources and services onboarded in the initial phase of EOSC-hub are expected to have a minimum Technology Readiness Level of 7.
TRL 7 - Beta

EC definition: "System prototype demonstration in operational environment"

  • Service has passed through development and is an advanced stage of pre-production: the software is stable, reliable and has been deployed in an operational environment.   
  • Functionality as required by the target users is documented, understood, validated with target sample users and accepted by them. Internal documentation exists regarding preliminary validation tests.
  • An assessment has been made of the required load of the system once the transition into production is complete and a plan has been made to service this load. This assessment has been documented.
  • An SLA is optional.
TRL 8 - Production

EC description: "System complete and qualified"

  • There are users who are making real use of the service and rely on it for their work.
  • Service documentation for end-users exists and is made available.
  • An acceptable use policy/terms of use/SLA is in place.
  • Evidence that the service is being delivered in a way consistent with user expectations.
  • Provision is made for user support, with response to incident and problem management.
TRL 9 - Production

EC description: "Actual system proven in operational environment"

  • All requirements of TRL 8 are met.
  • Customer feedback is gathered and documented. The service has been in a production state and relied upon by users for at least 1 year and evidence is provided to show this.
  • There are quantitative outputs as a direct result of the service usage.
Resources and services onboarded in the initial phase of EOSC-hub are expected to have a minimum Technology Readiness Level of 7 . At TRL 7 we are able to list  services, but TRL 8 or 9 will be needed in order to order through the portal. This is to ensure a c trusted implementation base of technical solutions and service offerings through quality of standards to evolve an open, mature end-to-end data lifecycle workflow. For lower TRL services we may offer some support to increase maturity of services.
Service terms of use is a link describing the rules, service conditions and usage policy which one must agree to abide by in order to use the service.
  • Services shall be delivered to a defined quality, sufficient to satisfy requirements identified from business processes.
  • A clear service portfolio shall be developed and maintained as a basis for all service delivery and service management activities.
  • For all services, a corporate level SLA and / or specific SLAs, which have been agreed with relevant stakeholders, shall be in place.
Service terms of use is a link describing the rules, service conditions and usage policy which one must agree to abide by in order to use the service.

You should receive an email asking to post an opinion about the service.

You will need to rate the service based on two questions : 

  • ordering via marketplace: about the service itself and about the order process or
  • open access services / external oderging: about the service itself and about the usage of the project functionality - in case your service has been added to the project 
You can also leave your comment about the service. Your opinion cannot be commented on by another user. The below rate will be shown on the main page of the service.

If a service is not operational, so the provider no longer responds, in this case the hub operator needs to be notified in order to suspend/remove the service.

If a service contains material which is not permitted, e.g. copied images or a service which is 'stolen' and the actual owner wishes to report it, in this case the hub operator needs to be notified in order to suspend/remove the service.

If a service has a security breach which might impact the Marketplace and the Portal,in this case the hub operator needs to be notified in order to suspend/remove the service.

Searching in the Marketplace

The user can search for services in the following ways:

  • browse category tree, filter all services by category or subcategories
  • search services using text (all services matching text of category, name, short and long description apply)
  • find services by its name, by target group, by selecting service properties specific to the category, by quality tags

After a customer has identified a suitable working service, he/she might be tempted to find another similar one to further explore the EOSC and make comparisons. This use case can be supported with a tag mechanism allowing to identify similar services. Tags can be triggered in two ways:

  • inserting a tag into the search bar;
  • looking up the tags connected with a service in its description page and clicking on one of them. 

The visual linkage between services that are somehow interoperable is another mechanism that fosters service composition and integration. This feature improves the service discovery and guides users in choosing the right solutions to create a service pipeline that can fully support their data processing needs, exploiting all the potential of the EOSC service catalogue.

EOSC services are classified, with respect to the service interoperability, in the following three categories:

  1. Not interoperable services: inputs and outputs from them cannot create a logical workflow - trying to run them together makes no sense. There is no linking at the GUI level, user should have a clear message that those services, even if added to the same project, will not be exploitable together.
  2. Compatible services: there is no low level integration but it makes sense to use those services together. Their inputs and outputs can create a logical workflow. The Marketplace GUI provides visible links to those services on a service entry level.
  3. Services integrated at a technical level: as a result of this integration, new solution based on a service bundle can be made available in the EOSC Portal Catalogue and Marketplace and offered as a unique service in the GUI. Ordering a bundle (two or more services) will trigger the creation of one order for multiple services.

Ordering process

The marketplace projects is a lightweight approach to assist users on organising their services and related orders into logical blocks which share a common purpose and gaining support in the scope of the created project. Its ultimate goal is to provide a user-friendly and helpful UI where EOSC services of interest can be gathered and managed. The user is guided step by step through the service order management process and able to get assistance from international technical teams who provide advice on the most suitable solutions to address the digital needs.

You can create a project as:

  • Single user as your own academic research,
  • Representing a research community as a larger community collaboration
  • Representing a private company as a R&D work of your company
  • Representing a project as an EC project

The marketplace project is the place to follow the status of your orders, get all relevant information about the service access when the access is granted and contact the EOSC support if necessary.

To create a project:

  1. Go to a Tab > My Projects.
  2. Select Create project (top left).
  3. Give your Project a name.
  4. Describe the Reason to request access to the EOSC services*
  5. Choose the Research areas from the list ( can be multiple).
  6. Fill in your CUSTOMER DETAILS
  7. Edit the relevant details and select Save details.

You can remove the project if no orders were placed. The functionality was created only for the project that has been created by a mistake. If you want to adjust an information in the project, you can use the Edit functionality.

To DELETE a project's details:

  1. Open the project you want to change.
  2. From your project's sidebar, select Project Details > DELETE
  3. Your project will disappear from your list

The user can edit all the values in the project.

  1. Open the project you want to change.
  2. From your project's sidebar, select Project Details > EDIT
  3. Edit the relevant details and select Save details.

If you want to have a new project with the same parameters that you already have, you should select "DUPLICATE" to select an existing project in order to use that project's schemes. Note that when you're copying schemes, any change to the existing scheme will not affect all the projects using that scheme.

To DUPLICATE a project's details:

  1. Open the project you want to change.
  2. From your project's sidebar, select Project Details > DUPLICATE
  3. Edit the relevant details and select Save details.

By archiving a project, you can remove it from the marketplace and preserve the data it contains.  Please remember that you can archive a project only in case all your orders are in status rejected or completed. If you still have not completed order, you will need to wait until it is finalized or canceled. Only then the option for archivization will be active. If you created a project by mistake, you will need to use the functionality : Delete the project.

To Archive a project's details:

  1. Open the project you want to change.
  2. From your project's sidebar, select Project Details >Archive
  3. Your project will disappear from your list
There are 3 different types of ordering systems in the EOSC Portal Catalogue and Marketplace.
No ordering

The service is advertised in the Marketplace, but there is no integration with the EOSC-hub service order management system. When a customer selects one of these kinds of services, he/she should be directly redirected to the service (in a new browser window) without the need of any further actions.

  • Such services are open to everyone, no login required.
  • The user can add the service to the project for the tracking aim, to have a history.
Orders to be delegated

This scenario applies to all services of service providers that decided to allow ordering via the EOSC-hub Marketplace but to use their own tools to manage them.

  • The user can order the service following the EOSC-hub marketplace workflow without the need of following customer procedures
  • The user can check the status of their orders and download the SLA from the EOSC-hub Marketplace
Orders to be processed

This scenario applies to all services of service providers that decided to adopt the EOSC-hub service order mgmt tool to process orders related to its service.

  • The user can order the service following the EOSC-hub marketplace workflow without the need of following customer procedure.
  • The user can check the status of their orders and download the SLA (when the order is approved) from the EOSC-hub Marketplace

To Order a Service to the Project:

  1. Open the project.
  2. On your Service sidebar, select Add the Service to this project
  3. Choose the service from the list. The service will be automatically added to your selected project.

In case you need more details about the next steps, please refer to the FAQ section What is the difference between the service order statuses

There is no limitation to the number of services that you can add to the project.

Order has many attributes but most importantly - it has a life cycle. Order points in its life cycle relevant to the user:

  • REGISTERED - Your service request was registered and shared with customer service team
  • UNDER REVIEW - Your service request is under review by customer service team
  • ADDITIONAL INFORMATION REQUIRED - Customer service team are waiting for your response
  • BEING PREPARED - You service request has been accepted and is currently being processed
  • READY TO USE - Your service is now ready to be used
  • REJECTED - Your service request has been rejected
  • CLOSED - Your service request is closed. If you want to use the service again, please contact customer service team
If you have placed an order, there is no possibility to remove or cancel the order by yourself. You will need to write an email and ask your customer service team to reject the request. You will need to write a small explanation with the reason for your cancelation.

Methods of payment

Services provided via the EOSC marketplace to the end-users are expected to be free of charge at the point of use. Some of the services provide fee-based access and service providers are free to define the pricing model for their services which would be visible to end-users via the marketplace. The marketplace announced fees reflect subsidies and state-aid, where applicable, so that the Member State funding is visible/traceable across the different service layers of the EOSC.

The funds to pay for researchers’ use of fee-based services may come from multiple sources such as research grants at national or research funder level as well as a centralised funding model whereby multiple countries or agencies collectively fund access to services.

The voucher scheme was proposed by Exoscale, the IaaS computing resources for the RHEA Cloud platform, as a result of the collaboration with the HNSciCloud Pre-Commercial Procurement (PCP) project.

The Exoscale vouchers provide a pre-paid access for users to a commercial cloud service provider for a specific monetary value and allow researchers with limited computing resources to test different configurations and choose the best service offer for their needs.

The vouchers aim to: Encourage the uptake of the resulted HNSciCloud pilot services for limited scale usage.allow commercial cloud service providers to contribute to the EOSC. Offer a convenient means to finance the use of EOSC services and increase the user base.

How to use it?
  • Access the EOSC portal marketplace.
  • Select the Elastic Cloud Compute Cluster (EC3) platform from the list of available services.
  • Submit a service-order request to use the EC3 platform (select the voucher option). When the request is approved, the user will be notified by email by the EOSC portal Marketplace.
Additional information: Each Exoscale voucher is worth around 400 euros. A total of 10 vouchers are available for running applications for scientific purposes. The vouchers proposed by the HNSciCloud project will have a validity of one year from the date of issue. All vouchers should be consumed before the end of 2019.
  • With no.1 voucher user can use of 9 instances of "small" [2] type for 3 months
  • With no.1 voucher user can use of 4 instances of "medium"  [2] type for 3 months
  • With no.1 voucher user can use of 2 instances of "large" [2] type for 3 months

For providers

Here are the steps to help you prepare:
  • Conform to Principles of Participation.
  • To lower the barrier and enable gradual adoption, multiple compliance levels for services joining the EOSC are envisioned.
  • The Service will need to be registered in the EOSC service catalogue, and at a minimum provide structured information about the offered resources. EOSC will define the minimum level of components to be provided, and service providers will describe their service.
  • The EOSC Service Management Framework provides multiple levels of federation to enable different “commitment” levels for services provider integration with the EOSC Service Catalogue. At a minimum, a service description will need to be provided containing structured information on aspects of the service such as:
    • Quality indicators
    • FAIR indicators
    • Licenses / Terms of Usage / Access Policies
    • Curation & preservation policies
    • Access methods
    • Etc.
  • Federation will apply mostly at the resource delivery level, rather than at the infrastructure level. This facilitates EOSC-fying resources selectively and lowers the barrier for participation.
  • In the case of data / metadata resources, specific interoperability requirements will need to be met to enable the findability and accessibility of the provided resources / datasets.
  • EOSC allows service providers to show that they can provide a service offering, which is compliant with the needs of the European research community.
  • By entering the EOSC realm, the first beneficiaries will be the users of your community.
  • Make use of EOSC services / resources.
  • Broaden the set of services / access to data you provide to your users.
  • Moral or even legal obligation to contribute to open science.
Services should include, but not be limited to running virtual machines on demand with complete control over computing services, executing compute and data-intensive workloads, analysing large datasets and executing parallel computing tasks, utilizing large amount of processing capacity over long periods of time, sharing resources and enabling collaborative research.

Open access

The service is advertised in the EOSC Portal Catalogue and Marketplace, but there is no integration with the EOSC-hub service order management system.
Benefits:
  • The service is advertised through the EOSC Portal Catalogue and Marketplace.
  • The service provider is aware of how many people access its service via the EOSC Portal Catalogue and Marketplace.

External ordering

This scenario applies to all services of service providers that decided to allow ordering via the EEOSC Portal Catalogue and Marketplace but to use their own tools to manage them.
Benefits:
  • The service is advertised through the EOSC Portal Catalogue and Marketplace.
  • The service provider is aware of how many people access its service via the EOSC Portal Catalogue and Marketplace.
  • The order contains information about user identity.
  • The order contains information about the customer type (single user, organisation, project, private companies, etc.)
  • The order contains information about the reason to access the service.
  • A specific service configuration is requested by the customer.

Internal ordering

This scenario applies to all services of service providers that decided to adopt the EOSC-hub service order mgmt tool to process orders related to its service.
Benefits for the service providers:
  • The service is advertised through the EOSC Portal Catalogue and Marketplace.
  • The service provider is aware of how many people access its service via the EOSC Portal Catalogue and Marketplace.
  • The order contains information about user identity.
  • The order contains information about the customer type (single user, organisation, project, private companies, etc.)
  • The order contains information about the reason to access the service.
  • A specific service configuration is requested.
  • The service provider can approve/reject orders in the SLA order mgmt tool.
  • The service provider can monitor all its SLAs/OLAs.
  • Service providers do not need to setup and/or operate their own order management system.
Report a technical problem

The EOSC portal is been jointly developed and maintained by the EOSC-hub, eInfraCentral and OpenAIRE-Advance projects funded by the Euopean

Union’s Horizon 2020 research and innovation programme with contribution of the European Commission

2018 EOSC Portal