GALILEO Research and Development Activities Second Call Area 1A GNSS Introduction in the Road Sector Statement of Work Rue du Luxembourg, 3 B 1000 Brussels Tel +32 2 507 80 00 Fax +32 2 507 80 01 www.galileoju.com - 1 -
TABLE OF CONTENT 1. INTRODUCTION...3 1.1. BACKGROUND...3 1.2. ACRONYMS...3 1.3. DEVELOPMENT OBJECTIVES AND CONSTRAINTS...4 1.3.1. General objectives...4 2. STUDY LOGIC...5 3. WORK DESCRIPTION...6 3.1. MANAGEMENT AND COORDINATION ACTIVITY...6 3.1.1. Consortium and project management...6 3.1.2. Coordination with other activities...7 3.2. ROAD APPLICATIONS DEVELOPMENT...7 3.2.1. Applications Survey...7 3.2.2. Service enabler analysis...7 3.2.3. Action plan and recommendation...8 3.3. TECHNOLOGICAL ACTIVIT Y...8 3.3.1. Introduction...8 3.3.2. Demonstration development...8 3.3.3. Road user terminal development...9 3.3.4. Road Sector Local Component...9 3.4. BUSINESS AND MARKET ACTIVITY...10 3.4.1. Road sector market seizing... 10 3.4.2. Business development in the road domain... 11 3.5. SERVICE PROVISION...12 3.6. REGULATORY ACTIVITY...12 3.7. STANDARDS AND CERTIFICATION ACTIVITY...13 3.8. AWARENESS AND TRAINING ACTIVITY...14 3.9. COMPLEMENTARY SERVICE ENABLERS...15 3.9.1. Development of the application operational environment... 15 3.9.2. Co-ordination with GIS development... 15 3.9.3. Synergies with communication... 15 3.9.4. Safety and security issues... 15 4. PROJECT INPUTS AND OUTPUTS... 16 4.1. REFERENCE INPUTS...16 4.2. DELIVERABLE ITEMS...16-2 -
1. INTRODUCTION 1.1. Background The Road is the second mass market in terms of number of users and business volume. In this domain the most developed applications are the telematic services based on the car navigator and linked additional services (emergency, point of interest, anti theft, etc). In this domain there are very different applications, from mass-market comfort services, through safety related like dangerous goods transportation up to sophisticated and demanding safety related applications like the Advanced Driver Assistance Systems. The road tolling, and derived applications like road-taxing and black box concept, are liability demanding and require a legal and regulatory framework for their exploitation according to EU directives and policies. The main drivers are: integration of the satellite receiver with others on-board sensors, including the digital tachygraph, interoperability across Europe for road tolling, accurate cartography, availability of added value services based on location for static and dynamic information. 1.2. Acronyms ADAS AG A-GNSS CBA EGNOS EOTD FOC GJU GNSS GOC GPS GSTB ICD IOV IPR ITS LBS MRD MTR PDA PPP SA SIS SOW TDOA UC UMTS Advanced Driver Assistance System APPLICATIONS GROUP Assisted GNSS Cost-benefit Analysis European Geostationary Navigation Overlay Service Enhanced Observed Time-Difference of arrival Final Operation Capability Galileo Joint Undertaking Global Navigation Satellite System Galileo Operating Company Global Positioning System Galileo System Test Bed Interface Control Document In-orbit Validation Intellectual Property Right Intelligent Transport System Location Based Service Mission Requirements Document Mid-Term Review Personal Digital Assistant Public-Private Partnership Supervisory Authority (GALILEO) Signal-In-Space Statement Of Work Time-difference Of Arrival User Community Universal Mobile Telecommunication System - 3 -
1.3. Development objectives and constraints 1.3.1. General objectives The main objectives of this Project are: OBJ-1. To facilitate and optimise the introduction of GNSS and in particular of EGNOS and Galileo in the road sector. OBJ-2. To involve and promote awareness for all the main actors, decision makers, investors, institutions, regulators, industries, service and data providers around the GNSS technology use in this sector. For examples this may include: car manufacturers, equipment manufacturers, map providers, touring associations, car insurance companies, highway operators, city councils, etc. OBJ-3. To evaluate and assess all the EGNOS/Galileo social and commercial benefits against current exiting solutions (e.g. applications, performances, technology, investments, standards, regulations, jobs, services and infrastructures). OBJ-4. To identify the main necessary steps to maximise the beneficial use of EGNOS/Galileo in Europe and in the world for this user community. OBJ-5. To play the role of reference, for this user community, for the development of EGNOS/Galileo applications and services on the global context of Galileo (i.e. Supervisory Authority, Centre for Security and Safety, Concessionaire, International agreements and cooperation) under GJU coordination. OBJ-6. To provide a platform for the representation of the interests of this user community in the overall discussion for the EGNOS and Galileo optimisation in term of different aspects (e.g. commercial, PPP scheme and risk allocation between public and private sides, social benefits and public interests, industrial and research development and innovation, operational and system evolution). OBJ-7. To provide a platform to join satellite navigation experts and industries with the user community experts in order to optimise the use of this technology in the target environment. OBJ-8. To provide an instrument for the dissemination and promotion of the EGNOS/Galileo benefits and added-values with respect to the current GPS OBJ-9. Solution, inside this user community targeting non-experts on satellite navigation. - 4 -
OBJ-10. To assess all the already identified EGNOS/Galileo applications in this user community domain against all the different technical and non-technical aspects. OBJ-11. To identify and promote new and innovative EGNOS/Galileo applications in this user community domain in order to explore all the potentiality of this technology in medium and long term including potential mission evolutions ideas. OBJ-12. To support the validation, qualification and certification of the different applications/services (for different aspects and with different involvement depending on the nature of the addressed application/service) in the overall frame of EGNOS and Galileo User Segment validation, qualification and certification. OBJ-13. To the project shall gather all the parties involved in the introduction of the Galileo/EGNOS service in the road domain, in order to have a reference frame to link the industry, service providers, users and institutions. 2. STUDY LOGIC The Project shall have a duration of 2 to 3 years. The project shall be divided in two distinct phases. The end of the first phase shall be marked by a Mid Term Review (MTR), and the activities for the second phase will be steered according to the main outcomes of the first phase. At the end of each cycle, the project shall produce the following outputs: a. Critical analysis of the current status for this user community (existing services, systems, results form previous studies/projects, on-going linked activities, current trends, etc); b. Identification of the detailed action plan and short/long term objectives and priorities (including potential synergies with others IP s and projects/studies); c. Implementation of the actions for this cycle (and development of prototypes and tools when applicable); d. Critical analysis of the results/achievements produced during this cycle and coordination/cross check with the others IP s and projects/studies; e. Demonstration and dissemination of the intermediate results/achievements; f. Discussion and consultations for the next cycle action plan; - 5 -
A detailed project schedule shall be presented by the contractor, taking into account: Specific applications/service implementation steps (introduction of a service, etc) User community events (major standards definition milestones, international events); EGNOS and Galileo milestones (availability of the EGNOS FOC SIS, Galileo GSTB, IOV, FOC, GPS L5, etc); A management meeting will be held with the GJU every 6 months. A progress meeting will be held with the GJU every 3 months. 3. WORK DESCRIPTION The consortium shall take into account the available achievements and results coming from previous EGNOS/Galileo studies and projects. The consortium shall take into account the on-going activities, initiatives, studies and projects (mainly but not limited to EU MS s) addressing the user community with the goal to identify and promote coordination and synergy opportunities with parallel works. 3.1. Management and coordination activity 3.1.1. Consortium and project management This activity consists in providing the overall management for the entire contract. The activities to be performed as a minimum are: Technical project coordination Contractual management Organisation and coordination of internal communication flow Documentation management Tracking project status Establish and maintain travel plan Review and verification of deliverables Organisation of progress meetings (calling notice, agenda, chairing and reporting) Organisation of reviews Identifying needs for interfaces with external entities Ensure coordination between the different activities where needed. The contractor shall report on this every 3 months. - 6 -
3.1.2. Coordination with other activities The activity consists in supporting the coordination between the contractor and: - Other consortia involved in other activities having some link with this one (safety of life receiver, aviation). - Other activities performed in the frame of the Galileo project. For example, the production of comments and recommendations for the EGNOS and Galileo MRD s optimisation from the specific addressed user community prospective. - Other activities performed in the frame of the Road navigation domain 3.2. Road applications development 3.2.1. Applications Survey ACT-1. The project shall identify all the GNSS applications in the road domain, including non-safety of life (e.g. infomobility) and safety of life (e.g. ADAS). ACT-2. The project shall group all the applications for the road community in Application Group (AG), in order to optimise the related activities and the involvements of experts for each homogeneous group of interests. ACT-3. The AG s shall be identified according, at least, to the following major cohesion criteria: the same type of users, common customers, the same or similar regulatory bodies, the same or similar standards, common leading industries, etc. ACT-4. The project shall identify for each AG the major international and European actors, regulators and decision makers to be involved and/or consulted for the introduction of EGNOS/Galileo. 3.2.2. Service enabler analysis ACT-5. The project shall assess each identified AG against the technological and non-technological service enablers (receiver development, local elements, market, standardisation, commercial, public interest, regulatory aspects, applications demonstration, etc.). ACT-6. The project shall perform, for each AG, a critical analysis of the financial, commercial, technical and legal feasibility of the GNSS applications/services. ACT-7. The project shall identify, for each AG and for each service enabler, the open issues and the main risks linked to the successfully introduction of EGNOS/Galileo. - 7 -
3.2.3. Action plan and recommendation ACT-8. The project shall elaborate an action plan for each AG in order to resolve the open points and to mitigate the risks for the short term (current project cycle) and medium-long term (the next cycle and/or the successive cycle/s). ACT-9. The project shall develop a list of recommendations and expected actions not under the project responsibility that are integral part of the overall developed action plan for EGNOS/Galileo introduction (e.g. creation of a service centre, implementation of an international standard). 3.3. Technological activity 3.3.1. Introduction The road sector represents today the first market for the GNSS, and among the road applications, the car navigation system is the most commonly used. The architecture of the car navigation system has been made at the beginning of the 90 s when the GPS constellation was not yet complete and when the GPS accuracy was still degraded by the Selective Availability. Actually, the other sensors (odometer, gyroscope or magnetic compass) were the main contributor for the localisation function and GPS receiver were playing an aiding role. Thus the price of the localisation unit of such a navigation system was essentially based on the price of the sensors. Galileo, thanks to its interoperability with GPS, will provide the possibility to have better availability of GNSS portion with a better accuracy even in urban area. The basic technologies and investigation activities for the development of a receiver answering the need of the car-navigation system manufacturer will be conducted through the Receiver Mass market development activities proposed in another SoW of this Galileo Research and Development activities (Second Call). Nevertheless, additional development activities are included in this project and are described in the next sections. 3.3.2. Demonstration development ACT-10. For the identified applications in the road domain, the project shall address the relevant architecture for the provision of the service. This shall include the analysis and definition of the following issues: User equipment (GNSS receivers, hybridisation with sensors, etc.) taking into account the issues of user authentication, GPS/Galileo interoperability, etc. Ground infrastructures (local elements, existing systems for car monitoring and toll collect, communication systems including SISNET, etc.) Service centres, including operations-related aspects - 8 -
Added value data (GIS, databases, cartography, data updating needs/requirements) Certification and guarantee of position information ACT-11. The project shall perform technical assessment and demonstrations for a selected set of applications in the road domain. 3.3.3. Road user terminal development ACT-12. In the frame of the project, the contractor shall analyse, design and develop new architecture for the localisation unit of the car, possibly combining different GNSS with different sensors, whilst considering the new features offered by EGNOS, Galileo and the interoperability between Galileo and GPS. The implementation of a prototype for the demonstration of the service provision shall be part of the project. ACT-13. The architecture shall also take into account the possible merging of the navigation equipment utilised for car navigation and the equipment utilised for personal mobility. ACT-14. The project shall include the resource to facilitate the coordination between the activities here proposed and the activities that will be performed under the massmarket receiver development activities of the Galileo Research and Development activities (Second Call). ACT-15. The project shall give feedback to the EGNOS and Galileo mission requirements (including local elements, core and combined services) in order to reflect the needs of the road community. ACT-16. The project shall include the resource to facilitate the coordination between the activities here proposed and the activities that will be performed under the massmarket receiver development activities, as well as the other projects of the second call (e.g. LBS user community). The project shall perform the study on the mentioned user terminal aspects, and implement the development of a prototype for demonstration purposes. The activity shall be linked to the tasks on local elements development, service provision definition, etc., for the development of a demonstrator representative of a service provision in support to applications in the road domain. 3.3.4. Road Sector Local Component The specific requirements from and Local Augmentations is for the Road Sector very much driven by the specifics of the application to be addressed within it. As part of this project it is however expected that as a minimum the following aspects of local service provision shall be addressed - 9 -
ACT-17. Improvements to Accuracy. For a number of applications, the accuracy attainable from using Galileo, combined Galileo and GPS or indeed combined Galileo and GPS interfaced with onboard sensors, will not be sufficient to meet the targeted application requirements. As such, the Local Component shall in such instances be required to derive and deliver to the user differential corrections to the SIS of the satellites. With the advent of Galileo and the modernisation of GPS, multiple civil frequencies will shortly become available to such road users. This feature will present the opportunity to implement a number of improvements over existing differential techniques (especially those based on Carrier Phase), and as such its use and implementation in the Road domain is a topic worth investigation. ACT-18. Improvements to Integrity. The overall concept of integrity as applicable to the requirements of the Road community is deserving of consideration, and the advent of Galileo with its Global Integrity concept, the relationship and performance that combined Galileo/GPS operation will deliver in the integrity process, integration with other sensors (e.g. odometer), map matching and the role of Galileo Local Service provision in the delivery of further integrity enhancements, as part of this overall mix shall be considered. ACT-19. As part of the Project, it is of particular interest to investigate the role and provision of the appropriate levels of all aspects (Time To Alarm, Alarm Limit, Risk of Miss-detection) of local integrity in the Road sector. As part of this process it is initially important to adequately address the relative integrity apportionments across the various sensors involved, in order to adequately determine the contribution required from the Local Augmentation. ACT-20. A critical analysis of the development and demonstration of Galileo based local augmentations to Accuracy and Integrity as applied to the Road domain shall as a minimum be performed. As part of this process very clear references as to the means proposed to replicate the Galileo signal shall be included. ACT-21. Complementary Receiver functionality is required for each of these augmentation developments and thus shall be provided within the framework of this IP. The project shall perform the study on the mentioned local element aspects, and implement the development of a prototype for demonstration purposes. The activity shall be linked to the tasks on user terminal development, service provision definition, etc., for the development of a demonstrator representative of a service provision in support to applications in the road domain. 3.4. Business and market activity 3.4.1. Road sector market seizing - 10 -
ACT-22. The project shall perform an in-depth review of the market studies on the GNSS market in the road domain. This shall provide a refined and trustworthy assumption for the business plans, and a valid support to the interactions with the Galileo concessionaire. Analysis of the competitors (e.g. GPS and its evolution), sensitivity of the market to the service product pricing, international dimension are all issues to be considered. ACT-23. The market analysis will address both commercial and social benefits and customised per main geographical regions. The addressable market shall be associated to all the applications in the road domain. ACT-24. The project shall define the basic data and assumptions for the business model for satellite navigation products in the road domain (e.g. product prices, replacement rates, type approval and certification costs, royalties, costs for upgrade to EGNOS and Galileo combined services). This activity shall address the chipset, the receiver, terminal (receivers + others sensors + communication + others), etc. ACT-25. The project shall define the basic data and assumptions for the business model for satellite navigation services in the road domain (e.g. service fees, combined services, license costs, service level agreements, public funds, validation and certification costs). This activity shall address the provision of navigation services via satellite as well as value-added services (e.g. infomobility). ACT-26. For each AG the addressable market will be analysed for a time period sufficient to include the Galileo FOC and GPS upgrades and for different world region. ACT-27. The project shall identify for each AG the already existing investments in infrastructures, products and services (e.g. the existing infrastructure for road tolling, the current solutions for city zone restriction, etc.) in order to analyse the benefits/drawbacks coming from the introduction of EGNOS/Galileo based solution. 3.4.2. Business development in the road domain ACT-28. The project shall develop a business model for each set of applications (AG), describing the complete value chain and the involved investors, users, customers, services providers, EGNOS/Galileo Operators and Service providers, etc. A cost benefits analysis (CBA) shall be performed for each actor of the addressed downstream value-chain in order to justify his participation to the business. ACT-29. The project shall define and consider in the business model the cost associated to the deployment of ground infrastructure for the envisaged solutions, including cost for deployment, validation, certification, maintenance, etc. ACT-30. For the various applications, the project shall evaluate the social benefits for the use of the EGNOS/Galileo based solutions. - 11 -
ACT-31. The project shall extend the analysis of the business development for the road domain to the other world regions, considering market issues such as number of users, industry, service providers, etc. 3.5. Service provision ACT-32. The project shall refine the aspects related to the provision of the EGNOS and Galileo services, as well as to the provision of the value-added services. ACT-33. The project shall address in detail the issues related to the EGNOS and Galileo services, to the collection of revenues from the stakeholders (users, etc.) to the service provider, to the commercial or institutional relation of the GNSS user community with the Galileo Operating Company, etc. ACT-34. A detailed modelling of the service provision and the value chain for the different applications, and a quantified analysis of all the revenue flow (e.g. towards the GOC). The relevant licensing aspects, specific mechanisms to secure revenues, the implementation of the service centres, the services ICD, etc., should also be addressed. 3.6. Regulatory activity The regulatory frame is an important non-technological enabler for the successful introduction of Galileo and related added value services in the road sector. This activity shall consist in an in-depth analysis of the regulatory framework in road transport domain. ACT-35. The project shall include a detailed analysis of the current legislation and regulatory frame on the road transport domain in order to identify: whether Galileo operation and service provision in the specific user environment are compliant with such rules, and the regulatory provisions hindering the provision of Galileo Services in the above mentioned user environment. ACT-36. The analysis shall be undertaken on a EU and national level (EU Member States). ACT-37. The project shall deliver recommendations on how the legal/ regulatory obstacles could be overcome, and in particular on the concrete measures to be undertaken in order to adopt a positive regulatory frame for the introduction of Galileo and added value related services in the road domain. ACT-38. The Contractor shall produce recommendations on what should be the pertinent decision level for, eventually, adopting new policy schemes (national / EU). - 12 -
ACT-39. While elaborating the analysis and the related recommendations above described, the following non-exhaustive list of items shall be considered: Protection of personal data, privacy and data distribution policies Convergence of applications and networks, for the combined use of systems Regulatory aspects related to the infrastructure designed to support GNSS road applications (including threats of tampering, signal jamming, interconnection, etc.) Patents and IPR in the GNSS applications in the road domain, considering the market dimension (for the service provider and for the GOC), and the standardisation issues (e.g. the interoperability of Electronic Fee Collection systems). Liability / service guarantee in the provision of the Galileo and related added value services until the end user ACT-40. The project shall support the definition of service agreement relations between the GOC and service providers. This shall take into account the service guarantee and liability of all the parties, including the international dimension. ACT-41. The project shall address and analyse the scenarios for the agreement relations between the Galileo management (GOC and Galileo Supervisory Authority) and other institutions in Europe and outside in the domain of geographical information provision. 3.7. Standards and certification activity The project shall contribute to the standardisation activities in the road domain for the following objectives: ACT-42. The project shall contribute to build awareness in the standardisation community and main bodies. This would include: Presentations to the principal standardisation bodies, etc. Preparation of communication material Co-ordination with industry and manufacturers in support to the standardisation process ACT-43. The project shall contribute to build awareness in the ITS industry and operational community. This would include: Preparation of specific communication material to target the industry like car manufacturers and terminal makers Support the Galileo Joint Undertaking to the lobby activity towards ITS industry ACT-44. The project shall contribute to develop basic, generic and framework standards for GNSS system performance, services and receivers - 13 -
Generic standards, e.g. Galileo ICD and receiver performance levels ITS framework standards (for a group of applications) ACT-45. The project shall contribute to develop application specific standards for ITS, or introduce GNSS elements into current standards, where necessary Verify the regulation proposals and stimulate the introduction of EGNOS/Galileo (and not only GPS) as standard for the use of satellite navigation ACT-46. The project shall contribute to develop a certification regime for GNSS receivers and equipped terminals used in the ITS domain To identify the requirements for certification, based on a review of GNSSdependent ITS applications Formulate a proposal for a certification regime to be applied in the road domain, and the specific instances where this should be implemented through standards, i.e. through GNSS performance requirements. 3.8. Awareness and Training activity ACT-47. The project shall make an overview of the status of other demonstration projects in the road domain. ACT-48. The project shall identify all the awareness targets (public, private, investors, users). ACT-49. Per target, the project shall identify the demonstrations needed and built the proper dissemination strategy (including event and conference planning, use of web, etc.), hold user fora, at European and international level. ACT-50. The project shall identify all the major international and European events for which its involvement is planned for the different activities and for the whole project schedule. ACT-51. The project shall define and organise dedicated events for the addressed user community with different objectives (e.g. to make awareness for users not expert in GNSS, to support the introduction of EGNOS/Galileo in this sector, to attract investors, to present preliminary/intermediate results achievements, to discuss open points, to involve others projects/studies). ACT-52. The project shall produce the materials (brochure, notes, web-pages, articles, presentations) needed to implement the awareness strategy per each target. - 14 -
3.9. Complementary service enablers 3.9.1. Development of the application operational environment ACT-53. The project shall analyse the need for the development of all the operational aspects related to the applications in the road domain. This includes also the analysis of all the aspects related to the safety of life applications (e.g. for ADAS) like the need for development of tools for the safety analysis, etc. 3.9.2. Co-ordination with GIS development ACT-54. The project shall address the aspects related to the development of the maps and the GIS for the various applications in the road domain, defining a roadmap for its development. This shall include: Analysis of the current status and coverage of the maps Evaluation of the effort for the GIS improvement Planning Analysis and definition of the standardisation issues related to the GNSS and GIS Analysis of the static and dynamic source of information and its characterisation Intelligent map data (e.g. streets direction, tunnels and bridges heights, etc.), its production, maintenance and certification. 3.9.3. Synergies with communication ACT-55. The project shall analyse, for the various applications in the domain, needs for harmonisation, standardisation, etc., of the communication component. This includes local elements and the integration of communication capability at terminal level. 3.9.4. Safety and security issues ACT-56. The project shall analyse the safety related issues, also for the non SoL applications, e.g. the human-machine interface requirements, etc. ACT-57. The system vulnerability and other security issues shall be analysed, including enforcement constraints (e.g. anti-jamming for road tolling). - 15 -
4. PROJECT INPUTS AND OUTPUTS 4.1. Reference inputs Set of reference documentation produced by the GALLANT project. Set of reference documentation produced by the GALILEI project. Available output of the VERT project 4.2. Deliverable items In addition to the deliverable identified in the previous paragraphs of this statement of work, the contractor shall deliver a list of documents that reflects the work accomplished within the project and can support the dissemination of the achieved results outside of the consortium. A final report shall be issued at the end, addressing all the tasks performed within the project. Also promotion and dissemination material and tools (video, websites, etc.) shall be produced in the frame of the project. - 16 -