Editing TC 4 Sensor Registry

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 11: Line 11:
 
# Edit deployments, enable traceability from observation data back to the sensor and procedures used for acquisition (link with implementation case on provenance IC_3).
 
# Edit deployments, enable traceability from observation data back to the sensor and procedures used for acquisition (link with implementation case on provenance IC_3).
  
The use case is applicable to the management of various types of platforms, deep-sea observatories (e.g. EMSO), marine gliders (e.g. [http://eurogoos.eu/gliders-task-team/ {+}][http://eurogoos.eu/gliders-task-team/+ <span style="color: #222222">http://eurogoos.eu/gliders-task-team/+</span>]) as well as solid earth (EPOS) or atmosphere (ICOS) observations.<br />
+
The use case is applicable to the management of various types of platforms, deep-sea observatories (e.g. EMSO), marine gliders (e.g. [http://eurogoos.eu/gliders-task-team/ {+}]http://eurogoos.eu/gliders-task-team/+) as well as solid earth (EPOS) or atmosphere (ICOS) observations.<br />
 
This can also be used to track usage of specific sensor models (e.g. CO2) across the RI 's observation networks.
 
This can also be used to track usage of specific sensor models (e.g. CO2) across the RI 's observation networks.
  
Line 84: Line 84:
 
* hydrosphere
 
* hydrosphere
 
* geosphere
 
* geosphere
 
  
 
'''<span style="color: #BBCE00">Community</span>'''
 
'''<span style="color: #BBCE00">Community</span>'''
Line 91: Line 90:
 
* Data service provision
 
* Data service provision
 
* Data usage
 
* Data usage
 
  
 
'''<span style="color: #BBCE00">Behavior</span>'''
 
'''<span style="color: #BBCE00">Behavior</span>'''
Line 106: Line 104:
 
* Optimal use of sensor resources within RI by using tools to manage the network of sensors, calibration planning, spare parts, …
 
* Optimal use of sensor resources within RI by using tools to manage the network of sensors, calibration planning, spare parts, …
 
* Better qualification, error bars on data by harmonized and high level documentation on data acquisition conditions.
 
* Better qualification, error bars on data by harmonized and high level documentation on data acquisition conditions.
 
  
 
'''<span style="color: #BBCE00">Challenges</span>'''
 
'''<span style="color: #BBCE00">Challenges</span>'''
Line 114: Line 111:
 
* provide them with very user-friendly interfaces and services around this sensor registry (e.g., alerts or schedule for calibration, deployment reports, …) at RI level or cross-cutting.
 
* provide them with very user-friendly interfaces and services around this sensor registry (e.g., alerts or schedule for calibration, deployment reports, …) at RI level or cross-cutting.
 
* enable interoperability with pre-existing and well established tools and systems maintained in the RI.
 
* enable interoperability with pre-existing and well established tools and systems maintained in the RI.
 
  
 
'''<span style="color: #BBCE00">Detailed scenarios</span>'''
 
'''<span style="color: #BBCE00">Detailed scenarios</span>'''
Line 126: Line 122:
 
* Edit a deployment (on fixed or mobile platform), get a deployment report including graphical schemes.
 
* Edit a deployment (on fixed or mobile platform), get a deployment report including graphical schemes.
 
* Enable traceability from observation data back to the sensor and operations carried on the sensor (e.g., latest calibration), see connexion with provenance implementation case (IC_2).
 
* Enable traceability from observation data back to the sensor and operations carried on the sensor (e.g., latest calibration), see connexion with provenance implementation case (IC_2).
 
  
 
'''<span style="color: #BBCE00">Technical status and requirements</span>'''
 
'''<span style="color: #BBCE00">Technical status and requirements</span>'''
Line 132: Line 127:
 
''<Please describe the possible components in what detail you can, considering both functionality and current status (e.g. does it involve existing tools/data?). Please also consider the requirements for the use case.>''
 
''<Please describe the possible components in what detail you can, considering both functionality and current status (e.g. does it involve existing tools/data?). Please also consider the requirements for the use case.>''
  
# Models: Sensor and hardware model distributed registry. Example available for EMSO RI: [http://www.esonetyellowpages.com/ {+}][http://www.esonetyellowpages.com/+ <span style="color: #222222">http://www.esonetyellowpages.com/+</span>]
+
# Models: Sensor and hardware model distributed registry. Example available for EMSO RI: [http://www.esonetyellowpages.com/ {+}]http://www.esonetyellowpages.com/+
# Instances and operations: Sensor and hardware instances and operation distributed registry and tools (edition, reports, alerts, …). Example : LabCollector ([http://www.labcollector.com/ {+}] [http://www.labcollector.com/+ <span style="color: #222222">http://www.labcollector.com/+</span>])
+
# Instances and operations: Sensor and hardware instances and operation distributed registry and tools (edition, reports, alerts, …). Example : LabCollector ([http://www.labcollector.com/ {+}] http://www.labcollector.com/+)
# Deployments: Sensor deployment edition, deployment report, traceability in observation data. Example : 52°North suite ([http://52north.org {+}][http://52north.org/+ <span style="color: #222222">http://52north.org/+</span>]). Under development sensor nanny (see screenshot).
+
# Deployments: Sensor deployment edition, deployment report, traceability in observation data. Example : 52°North suite ([http://52north.org {+}]http://52north.org/+). Under development sensor nanny (see screenshot).
 
 
[[File:Worddavdd1294de25b573d15b80b19fa13cf455.png|650px]]
 
  
 +
Image https://confluence.egi.eu/download/attachments/6225962/worddavdd1294de25b573d15b80b19fa13cf455.png
  
 
'''<span style="color: #BBCE00">Implementation plan and timetable</span>'''
 
'''<span style="color: #BBCE00">Implementation plan and timetable</span>'''
Line 147: Line 141:
 
# Involved RI: EMSO, EPOS, Euro-ARGO, marine gliders, ICOS, drones,
 
# Involved RI: EMSO, EPOS, Euro-ARGO, marine gliders, ICOS, drones,
 
# Resources in task 8.2 (catalogue), 8.3 (provenance) WP5 (reference model) and deployment (WP9). RI are also involved for tools reviews , requirement definition and test.
 
# Resources in task 8.2 (catalogue), 8.3 (provenance) WP5 (reference model) and deployment (WP9). RI are also involved for tools reviews , requirement definition and test.
 
  
 
'''<span style="color: #BBCE00">Expected output and evaluation of output</span>'''
 
'''<span style="color: #BBCE00">Expected output and evaluation of output</span>'''
Line 156: Line 149:
  
 
== <span style="color: #BBCE00">External Links</span> ==
 
== <span style="color: #BBCE00">External Links</span> ==
# TC_4 notebook: [https://envriplus.manageprojects.com/projects/wp9-service-validation-and-deployment-1/notebooks/655 {+}][https://envriplus.manageprojects.com/projects/wp9-service-validation-and-deployment-1/notebooks/655+ <span style="color: #222222">https://envriplus.manageprojects.com/projects/wp9-service-validation-and-deployment-1/notebooks/655+</span>]
+
# TC_4 notebook: [https://envriplus.manageprojects.com/projects/wp9-service-validation-and-deployment-1/notebooks/655 {+}]https://envriplus.manageprojects.com/projects/wp9-service-validation-and-deployment-1/notebooks/655+
  
  
 
[[Category:Use Cases]]
 
[[Category:Use Cases]]

Please note that all contributions to may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Copyrights for details). Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)