GALILEO JOINT UNDERTAKING

Transcription

1 GALILEO Research and development activities First call Activity B Galileo Local Component Development STATEMENT OF WORK GJU/03/099/issue2/OM/ms Issue issue2 6th FP B SOW 1

2 TABLE OF CONTENT INTRODUCTION 3 1. SCOPE OF WORK 3 2. SUMMARY OF CURRENT SITUATION 4 3. OVERVIEW OF ACTIVITY TO BE PERFORMED WITHIN THIS CALL 5 Figure 1: Activity Structure 5 4. TASK DESCRIPTION B1 : DEVELOPMENT OF CORE TECHNOLOGIES Description of Work Inputs Outputs Schedule 8 5. TASK DESCRIPTION B2 : GALILEO LOCAL COMPONENT IMPLEMENTATION PLAN Description of Work - B2.1 Technical Development : Inputs Outputs Schedule Description of Work - B2.2 Infrastructure Development Inputs Outputs: Schedule issue2 6th FP B SOW 2

3 INTRODUCTION An important and necessary enhancement to the Global Galileo services for a great many applications will be Galileo Local Services. These will deliver improvements in accuracy, integrity, availability, continuity and communication in various combinations and levels, to meet the specific requirements of different applications within the Professional, Safety of Life and Mass Market user communities. To this end, any work undertaken with respect to the Galileo Local Component has the overall objective of ensuring that when Galileo reaches Full Operational Capacity, associated Galileo Local Services are also in place to deliver maximum benefit to as many users as possible. 1. SCOPE OF WORK The primary scope within this call shall be focused on Technological Activities. As a basis for this, the Local Service architectures defined within Galilei will initially be used to identify critical Core Technologies. These Core Technologies shall subsequently be defined, and in some cases implemented, as part of this activity, with the objective that they will act as the Building Blocks for future physical implementations of Galileo Local Service Demonstrators, that will be developed in the future. Some effort will also be directed to an Implementation Plan, which has two aspects. The first of these is related to Technical Development, and this shall identify, highlight and address all technical issues related to Galileo on the Critical Path for delivering Galileo Local Services. An initial such plan, defined along a domain basis, will form part of the proposal, and this will in turn act as the basis for identification, and on completion of investigative studies, the reflection of the findings on a largely technical basis. The second aspect is Infrastructure Development, which shall consider the effect of existing infrastructure and its future developments, along with market and business forces, on the development of Galileo Local Services. All activities shall ensure that they build upon previous applicable work, (in particular Galilei ) and also take the next step in the end goal of delivering Galileo Local Services. The work undertaken in this first call will in turn act as the basis for future work to be undertaken in this domain (including the 2 nd and 3 rd calls). 099 issue2 6th FP B SOW 3

4 2. SUMMARY OF CURRENT SITUATION As an initial step in this process of delivering Galileo Local Services, the previous procurement study on Galileo (called Galilei ) developed a number of both Generic and Customised Local Element architectures. The Generic Architectures were based upon environmental constraints and formed a basis for the elaboration of more detailed and specific architectures in the following domains (Road, Rail, Aviation, Maritime, High Precision Professional, Location Based Services, Assisted GNSS and Indoor). In addition dedicated work packages on aspects of Local Integrity Provision, the use of Pseudolites, Deployment and Operational Costings, Operational Aspects and Receiver Issues have been undertaken. To summarise, the work undertaken to date in the domain of the Galileo Local Component has provided architectures across both a broad range of applications and functional aspects of implementation and it is this that will act as the basis on which to take the development of the Local Component to the next level. 099 issue2 6th FP B SOW 4

5 3. OVERVIEW OF ACTIVITY TO BE PERFORMED WITHIN THIS CALL An overview of the Galileo Local Component Activity is given below. Figure 1: Activity Structure Activity B Galileo Local Component Task B1 Core Technologies Task B2 Implementation Plan Phase 1 Identification Phase 2 Definition Sub Task B2-1 Technical Development Sub Task B2-2 Infrastructure Development Phase 3 Design Phase 4 Implementation & Testing Figure 1 shows the Tasks and sub-tasks and phases related to the Galileo Local Component activity. The first of these Tasks (B1) relates to the Development of Core Technologies, and this shall be the primary activity of the two. The logic of this activity is that it shall develop various Building Blocks to be used in future (not part of this task) demonstrators/applications, facilitating a standardised approach. In particular the future contribution that these Core Technologies can bring to the Validation Procedure for Galileo Local Services is of prime importance. It has 4 main phases in development (Identification, Definition, Design and Implementation & Testing). The Implementation Plan (B2) consolidates the critical issues related to future Galileo Local Service Provision. This process is addressed in two parts, with the Technical Development sub-task addressing all Technical issues related to the provision of Galileo Local Services, whilst the Infrastructure Development addresses the other actors that have an influence on this process (existing 099 issue2 6th FP B SOW 5

6 infrastructure and its modernisation, market forces etc). The scope of this task is detailed in Section 5. In order to maximise the use of the effort undertaken to date on this subject within Galilei, and in order not to disadvantage new entities, both tasks shall largely build upon the results of existing work, as reflected in the Documentation that will be made available to the successful bidder. The schedule for the Development of Core Technologies is 18 months, and for the Implementation Plan an overall schedule of 24 months will be undertaken (24 months for Technical Development and 18 months for Infrastructure Development). 4. TASK DESCRIPTION B1 : DEVELOPMENT OF CORE TECHNOLOGIES 4.1. Description of Work Using as a basis the Generic and Customised architectures, and the supporting Pseudolite and Local Integrity activities undertaken as part of Galilei, appropriate demonstration activities, and existing experience/information on Local GNSS Service Provision, Core Technologies shall be identified and developed. In particular, the Customised architectures specify requirements to element level, and as such full utilisation of this detailed description shall be made. This task will act as a necessary pre-cursor to the future development of Galileo Local Component infrastructure, as it will speed up the time necessary for development and implementation, thus saving on cost whilst simultaneously improving standardisation between the various applications. All such development part of this task must be focused on specific additional and innovative opportunities/requirements brought by Galileo, and shall not simply propose alternate solutions to existing techniques that will also work perfectly well with Galileo. By means of example, potential Core Technologies could include, Local Integrity Algorithms, Transmission Protocols, Interference Detection Modules, T-CAR RTK Algorithms etc. From this list it is clear that such Core Technologies will range in implementation from hardware, through software to detailed definition. In all instances it shall be the intention to progress with the development to the maximum extent, whilst remaining aware of the limitations that associated issues, such as a current lack of a Galileo Signal In Space, may impose on certain of these developments, both now and in the future. All related activities within parallel Galileo Research & Development Activities, and also within ESA s continued GalileoSat activities, also need to be fully considered in order to ensure both the usefulness and timely cross-fertilisation of results between these activities. In summary, the work to be undertaken within this activity will contain the following key elements within each of the phases highlighted in: 099 issue2 6th FP B SOW 6

7 1. Identification Using as a basis experience gained from existing Local infrastructure implementation and operation, complementary demonstrations and pilot projects, and the Generic and Customised architecture definitions, the set of critical Core Technologies which will have been developed and proposed as part of the initial proposal shall be refined. As part of this process the associated justifications and re-use strategy that shall also be provided as part of the initial proposal shall be refined. 2. Definition Having identified the Core Technologies the next step is to finalise the requirements for each Core Technology. It is important that the applicability of each Core Technology be maintained across a number of applications, whilst simultaneously ensuring that the level of definition necessary to lead to the subsequent phases is achieved. 3. Design Design of all Core Technologies identified to the level of Detailed Design. 4. Implementation & Testing Depending upon the nature of the Core Technology, it shall in some instances be implemented and tested as part of this activity (e.g. Local integrity algorithm tested using GPS data and a Test Harness) Inputs The following inputs shall be provided to this task: Ref Title Delivery V5.1 Galileo Mission Requirements Document. Galilei 026 Generic Local Element Architecture Synthesis. ITT Launch 027 Generic Local Element Architecture Definition. ITT Launch 062 Summary Report ITT Launch 046 Pseudolites To Augment Galileo. 047 Local Integrity Customised Local Element Architectures. & GalileoSat Service Definitions. [Excluding PRS] SIS ICD. 38a -h External ICD s. 33 User Segment Requirements. 33a Local Component Demonstrator Requirements. 28c Galileo System Architecture Baseline. 40 Performance Budget Receiver Design Outputs 099 issue2 6th FP B SOW 7

8 This task shall produce as a minimum the following outputs: Ref Title Delivery B1-10 Identification and Justification of Core Technologies. +1.5m B1-20 Detailed Definition of all Core Technologies. +5m B1-30 Detailed Design of all Core Technologies. +11m B1-40 Results of Implementation & Testing of selected Core +17m Technologies Schedule The full duration of this task shall be 18 months, and shall include the following milestones on top of normal progress meetings to be held periodically: 1. Kick Off. () 2. Completion of Identification Phase. ( + 2 months) 3. Completion of Detailed Definition Phase. ( + 6 months) 4. Completion of Detailed Design Phase. ( + 12 months) 5. Completion of Implementation & Testing. ( + 18 months) 5. TASK DESCRIPTION B2 : GALILEO LOCAL COMPONENT IMPLEMENTATION PLAN This Implementation Plan consists of two main sub-tasks that, whilst linked, can be separated along the lines of technical and non-technical issues. They are described in turn below: Description of Work - B2.1 Technical Development : The first sub-task relates to the development of a Technical Development Plan, which shall identify, highlight and address all Technical issues related to Galileo that lie on the Critical Path in delivering Galileo Local Services. This activity will be based on what has been submitted in the proposal. The detailed guidelines and constraints for the development plan will be agreed with the customer at the beginning of the activity (at M). With respect to the content of the Technical Development Plan, the contractor shall develop and consolidate as a minimum the followings elements: 1. The different phase (development and validation phase, deployment phase, operational phase) and overall project milestones (utilisation of EGNOS Operation, GSTB V2, IOV...). 2. GPS evolution and modernisation (e.g. introduction of L2, L5) 3. The various phases of the development of the Galileo Local Component (definition, prototyping, testing, validation, commercialisation). 4. The different types of Local Services (Safety of Life, Mass Market and Commercial) 099 issue2 6th FP B SOW 8

9 5. The evolution of existing infrastructure, complementary navigation system (inertial sensors, UWB ) and communication technologies (UMTS) that will have an influence on the Galileo Local Component. 6. Existing market analysis of the GNSS application and services. At each issue of this Technical Development Plan the contractor shall provide: An executive summary. A Gantt chart representation of the development plan. The development plan. A justification document including all the analysis made to support the consolidation of the development plan. The development plan shall include as a minimum: The main actions and milestones. The key external factor (GPS modernisation, UMTS, other technologies development) The key internal factor (development of the local elements, GSTB v2, Galileo full operation capability ) The justification document shall include as a minimum: Assumptions taken for the development plan. Open issues remaining. Support information for the choices made. Information Sources. In addition to the development plan and associated document, the contractor shall perform the necessary analysis to extract the following information and provide it under the form of dedicated analysis documents. Identification of Receiver related issues related to the Galileo Local Component. Identification of Frequency issues related to the Galileo Local Component. Identification of the Standardisation & Certification needs for the Galileo Local Component. 099 issue2 6th FP B SOW 9

10 5.1.2 Inputs The following inputs shall be provided to this sub-task: Ref Title Delivery V5.1 Galileo Mission Requirements Document. Galilei 026 Generic Local Element Architecture Synthesis. ITT Launch 027 Generic Local Element Architecture Definition. ITT Launch 062 Summary Report ITT Launch 046 Pseudolites To Augment Galileo. 047 Local Integrity Customised Local Element Architectures. & Local Component Certification & Standardisation. Sub-task B2.2 B2.2- Existing Local Service Infrastructure. +6m 10 B2.2- Infrastructure Development Plan for Galileo Local +18m 20 Services. GalileoSat Service Definitions. [Excluding PRS] SIS ICD. 38a -h External ICD s Outputs This sub-task shall produce as a minimum the following outputs: Ref Title Delivery B B B B Technical Development Plan (Outline) Technical Development Plan V1 Technical Development Plan V2 Technical Development Plan V3 Technical Development Plan V4 Frequency Assignment for Galileo Local Services Complementary Receiver Development for Galileo Local Services Certification and Standardisation Aspects of Local Service Provision +01m +07m +15m +23m +5m +5m +5m Schedule The full duration of this sub-task shall be 24 months, and shall include the following milestones on top of normal progress meetings to be held periodically: 1. Kick Off 099 issue2 6th FP B SOW 10

11 2. Completion of Specific Support Documentation. ( + 6 months) 3. Update of Technical Development Plan Version 3. (+16 months) 4. Final Technical Development Plan Version 4. ( + 24 months) Description of Work - B2.2 Infrastructure Development The work to be performed within this sub-task shall be undertaken in 2 phases as described below: 1. The Galileo Local Component will in a great many instances, be built upon existing/planned services and infrastructure (e.g. D-GPS). In addition to this, experience gained from existing Local GNSS service operation to be listed and analysed by the successful bidder will provide valuable information in the elaboration of certain similar business cases for future Local Galileo Service operation. As such, the successful bidder shall undertake all actions to gain visibility of what is currently in place and the update/enhancement schedules envisaged for this (to include Galileo and GPS L2C). The owners/operators of all such infrastructure shall simultaneously be made fully aware of Galileo and it s development schedule, in order that they can fully consider it when formulating any update plans they may have (e.g. Installation of new GNSS hardware). It is also important to note that Local Services is an area where significant interest and potential exists for cooperation on a Global scale, and as such some effort should be devoted to the identification of potentially attractive synergies. In summary, the work to be performed will detail existing services offered, the infrastructure used (e.g. number and distribution), the market targeted, the operational entity (e.g. public or private), the revenues generated (including generation mechanism) and evolution envisaged. The response to the Galileo Awareness exercise will also be detailed. This will focus on 3 areas, namely the European Union (to include accession countries), North America and Asia. 2. Building upon the findings of this Infrastructure analysis, and using as an additional input the deployment and operational costs calculated for Local Service Architectures, as well as Market analysis data specific to Local Services, an infrastructure development process that includes associated Business Plans, shall be elaborated for Local GNSS Services that will incorporate Galileo. The precise nature of the Local Services and their coverage (National, European, Global) shall be finalised, using as a basis the findings of the awareness exercise. Again, where complementary actors exist (e.g. EuroControl for Aviation Local Services), then any pertinent information or input that they may have should be fully incorporated. 099 issue2 6th FP B SOW 11

12 5.2.2 Inputs The following inputs shall be provided to this sub-task: Ref Title Delivery V5.1 Galileo Mission Requirements Document. Galilei 062 Summary Report ITT Launch 059 Local Element Cost Report. 060 Operational Issues Report. 112 Market Intelligence Briefing. 023 Synthesis of Market Aspects. B Sub-task B2.1 Technical Development Plan V1. Technical Development Plan V2. Activity D All related documentation when available. GalileoSat Service Definitions. [Excluding PRS] +2m +8m Outputs: This sub-task shall produce as a minimum the following outputs: Ref Title Delivery B B Existing Local Service Infrastructure Report Infrastructure Development Plan for Galileo Local Services + 5m + 17m Schedule The full duration of this sub-task shall be 18 months, and shall include the following milestones on top of normal progress meetings to be held periodically: 1. Kick Off. 2. Completion of Survey of Existing/Planned Infrastructure and Complementary Awareness exercise. ( + 6 months) 3. Mid Term Review of Infrastructure Development Plan. ( + 12 months) 4. Completion of Infrastructure Development Plan. ( + 18 months) 099 issue2 6th FP B SOW 12