GALILEO JOINT UNDERTAKING

Transcription

1 GALILEO Research and Development Activities First call Activity C Introduction of GALILEO services using EGNOS STATEMENT OF WORK GJU/03/100/issue2/OM/ms Issue issue2 6th FP C SOW 1

2 TABLE OF CONTENTS 1. INTRODUCTION Background Development objectives and constraints 4 2. ACTIVITY DESCRIPTION Phase A - Preliminary activities for the service provision prototyping Phase B - Implementation of the service provision prototyping 7 3. PROJECT SCHEDULE 8 4. PROJECT INPUT AND OUTPUT Reference and applicable documents Deliverable items Documentation Software 9 5. LIST OF ACRONYMS issue2 6th FP C SOW 2

3 1. INTRODUCTION 1.1. Background The development of the satellite navigation applications is currently performed in the frame of commercial and private initiatives, mainly based on the use of GPS and ground techniques for location based services (LBS). With the advent of Galileo - and EGNOS as a first step in the European GNSS strategy - the availability of innovative features that differentiate the navigation service provision (improved accuracy and service availability, the integrity, service guarantee, certification, etc.) will enable new applications that will provide benefits to all the participants of the service provision value chain. Other existing infrastructures (e.g. communication means and content providers) will represent a complementary base for the addressed services. The implementation of end-to-end services and, possibly, the related revenue schemes, requires the achievement of a number of steps. Typically, those include: Definition of user needs and requirements Development of prototypes and test tools Test and validation activities Standardisation and certification Set up of the service provision framework At this stage, there is a need to focus on the early development of these prototypes, in order to boost the growth of the EGNOS and Galileo market. This service prototyping exercise will be followed by further activities in the frame of a global coherent plan. There are currently a number of pilot projects which were launched under various funding schemes (e.g. the 5 th Framework Programme, ESA, etc.), with the aim of demonstrating the feasibility of innovative applications, and the advantages of using the EGNOS system. Beyond the proof of concepts, they already develop service provision prototypes, with analysis of related non-technical issues and end-to-end solutions. The current projects are mainly based on the exploitation of the GPS and the EGNOS System Test-Bed (ESTB), and they address a quite wide range of user communities (e.g. train, road, maritime, aviation, etc). The majority of these projects will be concluded by the end of 2003, and new developments based on the available EGNOS signal are now needed. With the transition now to the EGNOS operational system, the opportunity to implement real services - and to pave the way to the introduction of the Galileo ones - appears, and it is time now to implement early developments and end-to-end service provision prototypes for specific applications. 100 issue2 6th FP C SOW 3

4 1.2. Development objectives and constraints In the context of the implementation of the service provision, in its phase of service prototyping, there is a need today to progress in the study and experimentation of the use of the innovative features of Galileo and EGNOS, and to capitalise on the achieved results for the benefits of all the user communities. It is therefore essential to set up new early developments, trials, and demonstrations, in the various user domains, with the target of introducing the EGNOS as the initial Galileo service showing how it is the enabler of the implemented solution and its business case. The use of integrity, for example, shall be expanded from its initial application (i.e. aviation in Europe) to other applications that will need guaranteed positioning. The activity consists in the implementation of the GNSS services based on the operational EGNOS, demonstrating the added value of the European satellite navigation services (EGNOS and Galileo) with respect to the existing positioning solutions. In this context, the provision of the EGNOS products through non-geo means and the combination of the EGNOS services with other systems and products (other navigation sensors, communication systems, digital maps, satellite images, etc.) have to be considered, as it would allow some service providers to expand the EGNOS market. The project proposed shall comply with the following objectives and constraints: [1] The project shall be based on a GNSS application characterised by: - Use of the EGNOS and Galileo service differentiators (see point [2]) - Clearly quantified benefits to the user and/or social benefits - Commercial opportunities for the service provider - Revenue opportunities for Galileo - Conditions for geographical extension of the service - Simple evolution of the user towards combined EGNOS/Galileo service in the longer term. [2] The project shall demonstrate, with practical implementations of the service provision in the real utilisation environment, the value added of the Galileo and EGNOS service differentiators with respect to the existing systems and services (GPS and its other augmentations). This includes for examples: - Use of real-time navigation integrity information (for users out of the aviation domain) - Enhanced accuracy and availability - Service provision guarantee - Encryption and authentication features - Value of the certification for some categories of users, etc. [3] The project shall identify the overall service value-chain, and clearly demonstrate the benefits derived from the applications to its stake-holders (e.g. the users, the service providers, the manufacturers, the institutions, etc.) 100 issue2 6th FP C SOW 4

5 [4] The project shall address the provision of end-to-end services, implementing a functional prototype of the complete service provision chain. All the actors shall be represented in the project, including the user community, preferably through the recognised user associations in the relevant domain. [5] The project implementation should not be focused only in the technical feasibility aspects but should also develop elements to allow the operational introduction of the services in a commercial and/or regulated framework. [6] The project shall also identify the necessary further steps for the consolidation of the application in the real operational domain after the project end. [7] The international dimension of the Galileo and EGNOS service implementation should also be taken into account in the projects set-up, and its system performance assessment. The corresponding potential for export and international opportunities should also be considered in the market analyses. [8] The proposed service prototype shall use the available EGNOS signal. The relations and interfaces with the EGNOS service provider shall also be analysed and defined. [9] The proposed service prototype shall clearly identify which are the features to be implemented later when Galileo will become available, as well as identify the impacts of Galileo on the identified service provision scheme. 2. ACTIVITY DESCRIPTION The activities to be implemented in the project are described in this section. The project shall be based in two phases, addressing respectively the preliminary definition of the system for the service provision, including the analysis of the nontechnical aspects, and subsequently its implementation and operation. In this approach, the first phase ( Phase A ) whose duration shall be about 6 months will be mainly devoted to the initial refining of the application, with input from the users and analysis of the overall service value chain. This phase must end with clear requirements for the constituents that will be developed in the second phase, and with precise indications in support to the operational phase, including the regulation aspects, the standardisation issues, the business case and market estimation for the service provision. 100 issue2 6th FP C SOW 5

6 The Phase B of the project will implement a prototype of the system for the provision of the service, in an end-to-end approach that consider the overall chain. The implementation will be based on new hardware and software development, and in the reuse of already developed or commercial infrastructure. Within the last part of this Phase B, once the system is implemented, the operational phase of the project will be launched. In this part, all the actors are involved in the utilisation of the service from the service provider to the final users and the results of the trials shall be collected day-by-day from all in their operational environment. This feedback shall then be organised and properly disseminated. The specific tasks to be performed under the project are described hereafter Phase A - Preliminary activities for the service provision prototyping In the first phase of the project, which will have a total duration of about 6 months, the projects shall perform as a minimum the following tasks: A.1. Analysis of the user needs, application definition and service differentiators. This content of the task is to perform the consolidation of the user needs in the relevant area, with a deep analysis of the benefits for the users of one or many EGNOS and Galileo service differentiators. The analysis shall target the EGNOS system for the project implementation, but shall consider also Galileo for the analysis of the evolution. A.2. Current solutions for the application, analysis of the service provision value-chain. The output of this task shall gives an overview of the status of the infrastructure - currently existing or planned for the provision of services in the relevant domain. Also the service provision framework, including the regulatory aspects for the service, shall be considered. This is done in support to the activities on the evaluation of the benefits and definition of the business case (see A.6). A.3. Preliminary design of the system architecture and its constituent elements. This task defines the concept of the intended service provision for the application, describes it, and gives a preliminary outline of the system architecture needed for the final service provision. The preliminary design shall also include the description of the constituent elements of the final system. A.4. Definition and preliminary design of the service prototype. Building on the results of the preliminary design activity for the overall system (see point A.3), this task defines and details the architecture of the system to be implemented. The service prototype will be fully designed and developed in the Phase B of the project and is therefore not part of this task A.4. The differences between the prototype and the proposed final solution shall be also clearly described in the task. 100 issue2 6th FP C SOW 6

7 A.5. Preliminary definition of the trials and validation activities. This task shall provide an initial assessment of the validation strategy and the trial definition for the identified service. The activity shall consider the overall context of the EGNOS and Galileo development, thus duly taking into account the needs for promotion and awareness of the satellite navigation services in the specific application domain. A.6. Steps towards the operational introduction of the application in a commercial and/or regulated context. Under this task, a comprehensive analysis of all the aspects related to the full introduction of the proposed service in the market shall be performed. Aspects such as regulations, revenue-collection mechanism, integration with other technology, and certification, should be clearly identified in the plan for the operational introduction of the applications based on EGNOS/Galileo services. It shall include the analysis of the potential revenues and market size associated to the service provision for the specific application, evaluation of the benefits, and cost-benefit analysis for the service provision scheme. The majority of the results shall be presented at the end of the first phase of the project. If needed by the study logic, this activity can follow-on after the first phase Phase B - Implementation of the service provision prototyping The second phase of the projects, which will have a total duration up to 18 months, shall cover the following tasks, building on the results of the first phase: B.1. Detailed design of the service prototype architecture. Based on the preliminary design of the service prototype (see point A.4), this task shall perform the detailed design of the architecture, and should define the specifications down to the level needed for the development (or procurement) of the system constituents. B.2. Implementation of the service prototype architecture, including the systems development or procurements, integration, and system validation. The output of this task is the complete development, implementation and testing of the prototype, as designed under the activities described in point B.1. B.3. Definition of the operations for the service prototype and refinement of the exploitation plan. The purpose of this activity is to define the details related to the operation of the system, for all the actors concerned by its exploitation, from the service provider to the user. The definition shall also marginally address the evolution of the identified operations in the case of the final service. 100 issue2 6th FP C SOW 7

8 B.4. Operation of the service prototype, trials and test campaign. This task is related to the performing of the testing demonstrations, providing the service and collecting the test results in the operational environment. These activities shall be planned according to the needs identified in the task described in A.5. The feedback on the application shall be collected from every component of the service chain, from the users to the service provider. B.5. Analysis of the results and dissemination. This task is based on the outcome of the demonstration activity, and is devoted to the elaboration of the trials results. It shall include the system level analysis of the results, the definition of dissemination strategy and awareness activity, and production of dissemination and promotional material. The possibility to replicate short demonstration events should also be analysed and proposed in the dissemination package. 3. PROJECT SCHEDULE [1] The project will have duration of up to 24 months. It shall be based on a two phases approach. [2] A common milestone (Mid Term Review) shall conclude the first phase, at the end of which the foreseen activities shall have produced the results to be used in the following phase. The first six-months phase shall be concluded by an extensive review event, addressing in details all the aspects studied. The possibility of followon, or re-work on specific aspects if the result is not deemed satisfactory, shall be foreseen, while the impact of this case on the start of the second phase shall be minimised. Some of the activities started in the first phase could therefore have follow-on after the six months, if deemed appropriate. [3] The definition and development of the system shall be concluded within 18 months from the start of the project. The activity related to the use of the service prototype in the operational environment, the test campaign, analysis of results, and dissemination activity shall follow, and be concluded within 24 months form the start of the project. 4. PROJECT INPUT AND OUTPUT 4.1. Reference and applicable documents The project shall be implemented based on the current status of the EGNOS and Galileo specifications. The project shall consider as reference documents: - The EGNOS Mission Requirements Document - The Galileo Mission Requirements Document 100 issue2 6th FP C SOW 8

9 The version of the mentioned reference documents shall be the latest available at the project start. The two documents will be provided by the Customer at the project kick-off Deliverable items Documentation All the documentation produced in the frame of the project shall be delivered to the Customer. This includes also the test results, and all the data produced or used within the project (e.g. electronic maps, recorded signals, etc.). The delivered document package shall contain as a minimum: - User Needs Analysis and Service Requirements for the specified application - Preliminary Design Documents for the final system architecture and its constituents - Preliminary Design Documents for the service prototype - Detailed Design Documents for the service prototype and its constituents - System Validation Plan - Service Demonstration Plan - Preliminary Business Case for the system exploitation and associated Development Plan - Result analysis and Dissemination package Software The ownership of the source and compiled code developed under the project will be negotiated with the bidder on a case-by-case basis. 5. LIST OF ACRONYMS EGNOS GPS ICD LBS ESTB GNSS RTD European Geostationary Navigation Overlay Service Global Positioning System Interface Control Document Location Based Services EGNOS System Test-Bed Global Navigation Satellite Service Research and Technology Development 100 issue2 6th FP C SOW 9