GALA REF : Gala-Aspi-dd087 DATE : 08/12/2000 Executive Summary ISSUE : 06 PAGE: a DOCUMENT PRODUCTION You are using a template created for the GALA data production: • Do not delete the Document Production and Document Distribution sections. • Do not modify its styles which are common to all project documents. • At each section, a short guideline is given to help you find the nature of information to fill in. Those guidelines are given in “Italics” font and are to be deleted. • Some text are already included . They are presented in the “Normal” font style used in the template. Keep those and complete with the information requested. • The Company Logo can be added in the footer part. Before final edition of your document you need to update: • in the "Summary Folder" : • Title • Author (Check it) • Comments (Document summary) • in the " Custom Folder", the following properties : • Doc Approved By (Name) • Doc Classification (TBD) • Doc Company (TBD) • Doc Contract Number (TBD) • Doc Date Issue (Issue Date) • Doc Identification (Document Identification) • Doc Issue Number (Issue Number) • Doc Project Acronym (GALA) • Doc Project Name (GALILEO Overall Architecture Definition) • Doc Status (- / Reviewed / Approved) • Doc Type (A / R / I) • Doc Verified By (Name) • Doc WBS Code (WBS Code) To do so follow following instructions: • Double-click on the following button Update Properties • Select the property • Modify it and click on the button Modify • CTRL+A, F9 , F9 and answer to the questions. (If some are to be ignored, leave the default ones proposed.) • Before printing, check that Table of Content has been properly updated and fill the field "Date" of Change record with current date. Insert your logo GALA REF : Gala-Aspi-dd087 DATE : 08/12/2000 Executive Summary ISSUE : 06 PAGE: b Hereafter the mandatory fields with a TBD value are listed in RED Double-Click on the above button to initialise the Doc Status Field in the Custom Folder in the Property Box Double-Click on the above button to initialise the Doc Type Field in the Custom Folder in the Property Box Insert your logo GALA REF : Gala-Aspi-dd087 DATE : 08/12/2000 Executive Summary ISSUE : 06 PAGE: A DOCUMENT DISTRIBUTION From : Sylvain LODDO Project Acronym : GALA Project Name : Galileo Overall Architecture Definition Title : Executive Summary Issue : 06 Reference : Gala-Aspi-dd087 Date : 08/12/2000 Pages Number : 93 File : dd087v6 Issue : 06 Classification : P.U WBS : 11.8 Contract : gala-1999-am004 Emitting Entity : Alcatel Space Industries Type of Document : TBD Status : TBD Template Name : gala_v1.dot To : Internal Distribution Service Name N° Ex. Service Name N° Ex. External Distribution Company Name N° Ex. Company Name N° Ex. Insert your logo GALA REF : Gala-Aspi-dd087 DATE : 08/12/2000 Executive Summary ISSUE : 06 PAGE: B THIS PAGE IS INTENTIONALLY LEFT BLANK Insert your logo GALA REF : Gala-Aspi-dd087 DATE : 08/12/2000 Executive Summary ISSUE : 06 PAGE: 1 Sustainable Mobility and Intermodality Promoting Competitive and Sustainable Growth Galileo Overall Architecture Definition Executive Summary Written by Responsibility - Company Date Signature Sylvain LODDO Verified by Approved Documentation Manager WBS Code : 11.8 Emitting entity : Alcatel Space Industries GALA REF : Gala-Aspi-dd087 DATE : 08/12/2000 Executive Summary ISSUE : 06 PAGE: 2 CHANGE RECORDS ISSUE DATE § : CHANGE RECORD AUTHOR 1 13/10/00 First issue S. Loddo 2 10/11/00 Consolidated inputs after PM5 S. Loddo 3 21/11/00 Complementary inputs S. Loddo 4 23/11/00 Complementary inputs S. Loddo 5 27/11/00 Complementary inputs S. Loddo 6 08/12/00 Draft final issue S. Loddo GALA REF : Gala-Aspi-dd087 DATE : 08/12/2000 Executive Summary ISSUE : 06 PAGE: 3 TABLE OF CONTENTS 1 SCOPE.......................................................................................................................................... 10 2 MISSION REQUIREMENTS AND SERVICE DEFINITION............................................... 11 2.1 REQUIREMENTS DERIVED FROM USER NEEDS AND COMPETITION ANALYSIS....................................................................................................................................... 11 2.1.1 Introduction......................................................................................................................11 2.1.2 User needs.........................................................................................................................11 2.1.2.1 Accuracy, Integrity and availability.......................................................................11 2.1.2.2 Other requirements .................................................................................................13 2.1.3 Navigation Services..........................................................................................................14 2.1.3.1 User requirements driven service definition .........................................................14 2.1.3.2 Application to navigation service mapping ...........................................................14 2.1.3.3 Comparison between the user and architecture driven definitions ....................16 2.1.4 Market size and revenue .................................................................................................16 2.1.4.1 Market size ...............................................................................................................16 2.1.4.2 Revenue.....................................................................................................................17 2.2 DESIGN REQUIREMENTS .................................................................................................. 19 2.2.1 Candidate services ...........................................................................................................19 2.2.2 Security policy..................................................................................................................19 2.2.2.1 Rationale for a dedicated service............................................................................19 2.2.2.2 Access management .................................................................................................20 2.2.2.3 Encryption of SAS ranging signals.........................................................................20 2.2.3 EGNOS .............................................................................................................................21 2.2.4 GALILEO integrity and certification/standardisation ................................................21 2.2.5 GPS assumptions..............................................................................................................21 2.2.5.1 Assumptions .............................................................................................................22 2.2.5.2 Dual mode Galileo/GPS receiver ............................................................................22 2.3 LEGAL AND INSTITUTIONAL REQUIREMENTS......................................................... 23 2.3.1 Technical and legal definition........................................................................................23 2.3.2 Certification and the international credibility of the system .......................................23 2.3.3 Service guaranty, control access and the need to limit risks........................................24 2.3.4 The need for a strong guarantor for Galileo .................................................................24 2.3.5 Compensation and the viability of the system...............................................................25 2.3.6 Jurisdiction and possible relevant legal regimes...........................................................25 2.4 NAVIGATION SERVICES AND SYSTEM PERFORMANCES ...................................... 26 2.4.1 Open Access Service (OAS) ............................................................................................26 2.4.2 Controlled Access Service 1 (CAS1)...............................................................................27 2.4.3 Safety of life Access Service (SAS) .................................................................................28 2.4.4 Governmental Access Service (GAS) .............................................................................29 2.4.5 Timing Services................................................................................................................30 2.4.6 Service Performances ......................................................................................................30 2.5 SAR SERVICE......................................................................................................................... 32 2.6 COMMUNICATIONS SERVICE.......................................................................................... 33 3 SYSTEM CONCEPTS ................................................................................................................34 3.1 CONSTELLATION ANALYSIS ........................................................................................... 34 3.1.1 Introduction......................................................................................................................34 3.1.2 Constellation sizing..........................................................................................................34 GALA REF : Gala-Aspi-dd087 DATE : 08/12/2000 Executive Summary ISSUE : 06 PAGE: 4 3.1.3 Outcomes of the analyses ................................................................................................34