(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The attributes marked with a * are confidential and should not be disclosed outside the service provider.
| Service overview |
Service where the main outcomes or products provided by the Envrionment Research Infrastructure involved in ENVRIplus provide. This includes data services and acquisition services (observatories). The purpose is to enable users to discover this resources at transdisciplinary level.
|
| Service name |
RI flagship product catalogue
|
| Service area |
discovery of data and acquisition services
|
| Service phase |
under development
|
| Service description |
a portal is provided and machine to machine link for harvesting or semantic linking.
|
| Customer group |
ENVRIplus project managers. RI managers. Eventually EU DG Research.
|
| User group |
researchers
|
| Value |
enlarge the target of users who can use the data services or acquisition services provided by the RI beyond their traditionnal communities (atmosphere, biodiversity, biodiversity, solid earth, marine).
|
| Tagline |
discover what data or experiment hosting support you can get from the European envrionment Research Infrastructures.
|
| Features |
portal
|
| Service options |
| Option |
Name |
Description |
Attributes |
|
| 1 |
|
|
|
|
| 2 |
|
|
|
|
| 3 |
|
|
|
|
|
| Access policies |
free access
|
| Service management information |
demonstration for envriplus project.
|
| Service owner * |
ENVRIplus project; Operated by EUDAT/DKRZ
|
| Contact (internal) * |
thomas loubrieu (thomas.loubrieu@ifremer.fr)
|
| Contact (public) |
|
| Request workflow * |
access will be free and open
|
| Service request list |
|
| Terms of use |
|
| SLA(s) |
|
| Other agreements |
|
| Support unit |
|
| User manual |
|
| Service architecture |
|
| Service components |
| # |
Type |
Name |
Description |
TRL [1]
|
| 1 |
|
|
|
|
| 2 |
|
|
|
|
|
| Finances & resources |
|
| Payment model(s) |
|
| Pricing |
|
| Cost * |
|
| Revenue stream(s) * |
|
| Action required |
|
[1] Technology Readiness Levels (TRL) are a method of estimating technology maturity of components during the acquisition process. For non-technical components, you can specify “n/a”. For technical components, you can select them based on the following definition from the EC:
- TRL 1 – basic principles observed
- TRL 2 – technology concept formulated
- TRL 3 – experimental proof of concept
- TRL 4 – technology validated in lab
- TRL 5 – technology validated in relevant environment (industrially relevant environment in the case of key enabling technologies)
- TRL 6 – technology demonstrated in relevant environment (industrially relevant environment in the case of key enabling technologies)
- TRL 7 – system prototype demonstration in operational environment
- TRL 8 – system complete and qualified
- TRL 9 – actual system proven in operational environment (competitive manufacturing in the case of key enabling technologies)
