CHAIN-REDS has worked hard on providing regional use cases that demonstrate how an international e-Infrastructure can be exploited to produce tangible results in terms of scientific/industrial/social impact, but also, as a benefit for the community they are addressing.
In order to pass the baton about the expertise acquired, this list of “Good Practices" has been written in the form of a guide in order to allow future initiatives, groups and/or entities to count on a document that will serve them as an example to follow.
The guide consists of itemized steps that regional service providers can follow to approach and engage with user organizations or communities that will exploit their services. It is based on the expertise acquired by the European Commission co-funded project CHAIN-REDS to produce a set of use cases that lately become success stories during the period 2014-15.
- To investigate the scientific/industrial/social interests that are of importance in the region/country is being approached. Look for communities that count on one or several of the following points:
- Big scientific impact (publications, patents, or general impact);
- Big social impact;
- Covers a number of countries or regions;
- Has large international collaborations and visibility in relevant scientific or technical fora.
- To consider the status of the applications/codes/data that the community is using and how they fit in the portfolio of services that the provider offers. In this regard, the following points could be analysed:
- Readiness/feasibility of the application/service to be deployed on the existing e-Infrastructure;
- Relevance of the application/service;
- Number of countries/groups that could potentially be interested in the application/service;
- Availability of an organisation and/or a community to collaborate with the regional service provider for the deployment, the evaluation of the relevance and follow-up activities;
- Evaluation of the risk compared to the possible challenge.
- To evaluate the sustainability of the use case in the following aspects:
- Human resources devoted to use and maintain the services to be deployed;
- Creation of long-term collaborations between the community and the resource provider and with external institutions.
- To establish a working team once that the selection and acceptance of the use case is set up. Such a team must:
- Be formed by qualified people belonging to both the community and the regional service provider;
- Draft a MoU that will rule the collaboration between the community and the regional service provider;
- Monitor how the selected use case comes into production with regular meetings;
- Apply contingency plans, if any.
- To define a list of technical milestones that must be achieved in order to properly deploy the use case/application/service selected. Such a list can be part of the MoU previously mentioned and it is intended to set a framework that will be beneficial for both parts of the collaboration. Some example of milestones follow:
- Number of CPU hours consumed in a period of time, if applicable;
- Number of storage capacity used in a period of time, if applicable;
- Number of services deployed in a period of time;
- Number of resource providers (sites) involved.
- To define a list of dissemination and outreach milestones that must be achieved in order to properly publicise the use case/application/service selected. Such a list can be part of the MoU previously mentioned and it is intended to set a framework that will be beneficial for both parts of the collaboration. Some example of milestones follow:
- Collection of feedbacks and interviews from the community users;
- Collection of feedbacks and interviews from stakeholders;
- Presentation of the joint work carried out in international events;
- Publication of the joint work carried out in relevant publications;
- Announcement in the respective websites;
- Actions devoted to general public (visits, media, open-days, etc.).
Some examples of how this Good Practices guide has been come into success can be found in the project deliverable D4.5. In this document, the editor and his corresponding contact are available for any potential support.