contenu.php?arbo=5&page=
| Term | Description |
| ESA GMES Service Element Programme, RISK-EOS Stage 2 | ESA GMES Service Element Programme, RISK-EOS Stage 2 project (« Project ») is the project co-funded by ESA for Services delivery to Project Users Community. RISK-EOS stage 2 is implemented in 3 (three) sequential phases of 12 months each:
|
| Main user | Main User means a User which role is to interface between a set of Users and the Main Service Provider. Main User is the party who sign an SLA with a Main Service Provider.
|
| Main Service Provider | Main
Service Provider means a Party that has contracted,
with a Main User or User or Customer, a SLA by which he endorses the responsibility of the performance for
providing one or more Services, through one or more Service Chains. The following documents have to be
provided by the Main Service Provider and the Service Provider: [U7] Service Utility Report provided by the Main Service Provider. Main Service Provider is responsible for [U7] document, [S6] Service Operation Report provided by the Service Provider with inputs of the Main Service Provider when applicable. The Service Provider is responsible for this document.
|
| Operational Validation | Operational Validation gathers the production of the Service Operation Report [S6] and the Service Utility Report [U7]. The operational “Product” validation is part of the Operational validation. It is performed each year on the Products delivered to the User, depending on available reference information (existing ground surveys, existing databases, maps, aerial photographs…). In most of the cases these information are provided by the User. This Operational product validation is performed by the Service Provider or the Main Service Provider. Method applied for the operational validation and results obtained must be documented in the [S6] Service Operation report. The Main Service Provider performs the Operational validation and provides the inputs to the Service Provider who is responsible for the [S6] document completion.
|
| Product | RISK-EOS Product(s) or “Products” means a set of information layers as deriving from operating a service chain, according to what specified in the relative Service Specification [S5] document. A product gives added value information resulting from the process of different data source inputs. Some of its main features are the targeted users, the needed input data, covered area, output format, delivery mode, delivery frequency, key performances parameters, accuracy.
|
| RISK-EOS Service specifications and qualification documents | RISK-EOS
Service Specification and Qualification documents (« Service Specification and Qualification ») are the following Project documents: [S3] RISK-EOS Service Prospectus, [S5] Risk-EOS Service Portfolio Specifications, [C5] RISK-EOS Service Validation Protocol, [C6] RISK-EOS Service Validation Report. [D2] Service Network Configuration Master Document
|
| Service | RISK-EOS
Service(s) (« Service(s) »)
means a set of information products with associated delivery
conditions, all further defined in the RISK-EOS Service
Specification and Qualification documents. A
Service aims at providing added value Products, mainly
geo information based, to Users (risk management actors
such as Civil Protection, flood/water/forest management services,
municipalities, authorities, ..). Main features characterizing a
service are: Service description and objectives, Targeted Users, Products delivered, Key Performance parameters, Product frequency delivery, Product delivery mode, Product delivery delay, Service avaibility, Service Provider name and status
|
| Service Level Agreement | Service Level Agreement (« SLA ») means an agreement signed between a Main Service Provider and a Main User or User or Customer. Each SLA specifies the quality, quantity, terms of access and funding conditions for the Services to be delivered for a period of time not less that one year.
|
| Service Partnership Protocol - SPP | The « SPP » or the « Agreement »), is a cooperation agreement between the Parties open to new Partners. It is also a deliverable document to the Project.
|
| Service chain | Service Chain means a technical solution which allows delivering a Service. The Service Chain shall be qualified accordingly with Service Specification and Qualification.
|
| Service Developer | Service Developer means a Party, who is the owner of a Service Chain. He can have developed itself the Service Chain or has sub-contracted its development or implementation to a third Party.
|
| Service Network | RISK-EOS Service Network (« Service Network ») means the Parties at the SPP which undertake to collaborate at the development, maintenance, operational exploitation and promotion of the Service Portfolio. The Service Network Coordinator is INFOTERRA France, assisted by TELESPAZIO as Service Network Technical Coordinator
|
| Service Network Coordinator | Service
Network Coordinator means the party who is in charge of: reviewing and approving the Service Level Agreements [C7.x], establishing and updating the Service Partnership Protocol [S4], establishing the Service Annual Work Plan for each Phase of RISK-EOS [D1], maintaining the Service Prospectus [S3].
In addition he supervises the coordination work done by the Service Network Technical Coordinator and reviews with the Service Network Technical Coordinator the Service Validation reports [C6]. He reviews also the service Utility Reports [U7]. The Service Network Coordinator is INFOTERRA France.
|
| Service Network Technical Coordinator | Service
Network Technical Coordinator means the party who is in
charge of ensuring the overall management of the service network
technical documentation. The Service Network Technical
Coordinator is TELESPAZIO. He is responsible for the services
validation process. He is in charge of reviewing the following
documents: [S6] Service Operations report[C6] Service Validation reports.
and he maintains and updates the following documents:
[S5] the Service Portfolio Specification, [D2] the Service Network Configuration, [C5] the Service Validation Protocol.
|
| Service chain qualification | RISK-EOS
Service chain qualification is the process to pronounce to a
service chain “its” RISK-EOS qualification. To
be “RISK-EOS” qualified a Service Chain has to
follow the 3 steps as documented in Art.5.1: Scientific Validation (not mandatory), Technical Validation (mandatory), Acceptance by an Independent Body (mandatory).
|
| Service provider | Service Provider means a Party that operates a Service Chain, either for a Main Service Provider or for his Users or Main users as Main Service Provider
|
| Scientific Validation | Scientific Validation means a scientific analysis of the methodology used in a service chain to derive the “Product(s)”. Main document to allow an “Independent Body” to perform the scientific validation is the RISK-EOS Service Specification [S5]. In addition any publication on this Service chain is an input for the scientific validation. Scientific validation is not mandatory to get the “RISK-EOS” Service chain qualification
|
| Service Strategy Committee | Service Strategy Committee, provides strategic guidance and support to the service network coordination. It is composed of permanent members from DDSC, DPC Italy, Bundesamt für Bevölkerungsschutz (German Civil Protection), Spanish Civil Protection, Swedish Civil Protection.
|
| ESA GMES Service Element Programme, RISK-EOS Stage 2 | ESA
GMES Service Element Programme, RISK-EOS Stage 2 project
(« Project ») is the project
co-funded by ESA for Services delivery to Project Users
Community. RISK-EOS stage 2 is implemented in 3 (three)
sequential phases of 12 months each: PHASE 1: Network Set-Up and service delivery to first-year service Review. T0 of PHASE 1 is 17th November 2005. PHASE 2: Services Scaling-up to second-year service Review, PHASE 3: Service Sustainability Demonstration to third-year service Review.
|
| Technical Valivation | Technical
Validation is one of the steps to be followed to obtain the “RISK-EOS” qualification for a Service
chain. It consists in documenting: The validation protocol in the Validation Protocol [C5], Document the Service Specification [S5], Document the Service Prospectus [S3], Document the Validation report [C6].
and performing the technical validation itself. For instance the technical validation would consist in performing field surveys and comparing them with the results derived by the “Product(s)”. The results of the technical validation are documented in the Service Validation report [C6] and they must be in line with the Service Specification [S5] and the expected minimum performance of the Service documented in the Validation Protocol document [C5]. The Technical validation is mandatory to obtain the “RISK-EOS” Service chain qualification. This validation is a one shot validation. It must be applied again if evolutions are performed on the Service chain. Documentation has to be completed by the Service Developer or the Service Provider.
|
| User Excecutive Body | The User Executive Body, gathers one permanent member per country of each Party of this protocol. Main objectives of the User Executive Body are to promote RISK-EOS Services and provide feedback to the Service Network Coordinator of the Users with regards to RISK-EOS Services. User Executive Body is the interface between the Users and the Service Network coordinator. In RISK-EOS PHASE 1, it gathers 1 permanent member for each of the following countries: France, Germany, Italy, Spain, Slovakia and Sweden and the management of the User Executive Body, who is the French Civil Protection (DDSC).
|
