ESA Iris Programme Analysis & definition of the Satellite System Operations Briefing 28 July 2009 - Nathalie.Ricard@esa.int 1
Analysis & Definition of Satellite Operations Study rationale ESA s involvement in development and deployment of the satellite system of the EATMS will cease by 2016. Roles and responsibilities of entities involved in provision of telecommunications services for the EATMS shall be defined by SESAR Joint Undertaking and the European Commission and is beyond the mandate of the Iris Programme. However, early involvement of potential operators and service providers is the best way to ensure future suitability of the system design for the intended purpose. In order not to prevent competition from the start, it is planned to place at least 2 parallel contracts will be placed for the study. Results of the study will enable preparation of a collaboration framework between ESA and operators/service Providers for Iris Programme Phase 2.2 2
Analysis & Definition of Satellite Operations Competitive ITT to be issued 1st week of August closes end September o planned to place at least 2 parallel contracts (max. EUR 500k each) o Kick-off foreseen in November o 12 months study, split in two 6-months phases o Start of the second phase depends on the outcome of the System Requirements review of the Iris System Design Phase B study and is subject to ESA authorisation The study targets satellite operators and satellite service providers, with welcome involvement of CSPs, ANSPs and airspace users De-coupling required between manufacturing industry and operators; the satellite manufacturing industry is involved in the System Design Phase B study, which is carried out in the same timeframe Formal exchange of information via ESA takes place with this study 3
Context of the study 4
ESA, EC and SESAR JU European Commission: ESA-EC Framework Agreement o Formal cooperation on Iris under agreement procedure Regular meetings with DG TREN Single European Sky Unit ESA EC Steering Committee Iris - SESAR Supervisory Board Political level Strategy level SESAR Joint Undertaking Iris SESAR coordination group Working level Coordination of overall strategy Technical interface: o SJU Satcom Project & Iris Programme activities are coordinated and info shared Iris Programme ICD Mission Requirements Satcom Project o Regular meetings Specification & validation elements 5
ESA and EASA European Aviation Safety Agency (EASA) Transition phase towards new regulatory process cf. SES II legislation o Competency foreseen for regulation/certification of pan-european provision of services o New Implementing Rules expected to be published in 2012 Iris Safety Board (EASA, ESA, SJU) will work to anticipate and facilitate preparation of safety case 6
ESA and Aviation stakeholders Focus Groups for discussions and exchanges with aviation stakeholders Dialogue with end users to: o understand drivers for aeronautical communications, with sufficient details to properly orient design iterations between user requirements and system's capabilities o consolidate requirements for applications beyond SJU s scope (esp. commercial AOC services) Meetings foreseen throughout Iris Phase 2.1 (mostly up to System Requirements Review in 2010) o ESA is currently establishing contact points o Calendar of meetings TBD with SJU depending on Project 15.2.6 activities 7
Other Iris Phase 2.1 activities System Design Phase B: ITT is closed and under negotiation o Targets manufacturing industry only o Includes both design of the standard and design of the satellite system o System Requirements Review in May/June 2010 PDR in 3Q2011 Technology support studies (incl. evolution of Inmarsat s Swift BroadBand safety) Consultancies and Technical Assistance activities 8
Operation studies vs System Design Phase B Workflow Operation studies Proposed input Mission Requirement Document System Requirement Document System Design Phase B study System architecture info Input SRD Change Control Board Iterations For some tasks, the Operation study uses input from the System Requirements Document, or input on the System Architecture same input to each Operations study Iterations of SRD at T0, T0+3 (Architecture Options), T0+5 (baseline) System Architecture information from System Design study: options given in Phase 1; baseline architecture in Phase 2 The System Design study requires inputs on Operations costs for its own trade-off NB: No direct interface between ESA study teams 9
Link between Iris Phase 2.1 activities Requirements control Iris Programme Level Co-Chair Observer Iris Phase 2.1 Contractors Coordination Group Controls Iris Mission Reqs. Doc Co-Chair Phase B Project Level Co-Chair Observer Operation study Contractors Change Control Board Iris System Reqs. Doc Controls Observer Co-Chair Phase B study Prime Contractor 10
Analysis & Definition of the Satellite Operations Tasks description 11
WP1 Service Provision Aim: definition of roles and responsibilities of all stakeholders Service Model o Who does what and what is the revenue flow? Timeline for service set-up and system lifecycle Interoperability and transition o How to ensure interoperability with other satellite systems in practice? o What about the transition period until 2020? Definition of responsibilities and liabilities 12
WP2 Engineering requirements analysis Aim: define the impact of the operations on the system design Review the Mission Requirements and System Requirements documents and their updates Analyse service availability requirements Define system operations o specifications for Satellite Operations Centre/Satellite Control Centre o specifications for Network Management Centre/Network Control centre Define interfaces with the terrestrial system (i.e. EATMS interface) Assess System Architecture options and associated operations o What is the impact on operations (complexity, cost ) of each System Architecture option considered in the System design Phase B study? Detailed costing of operations o based on the baseline chosen at SRR 13
WP3 Regulatory constraints Aim: definition of regulatory activities for service certification and system validation Service certification o define pre-requisites and interfaces to Regulatory Bodies System verification and system validation o Define elements and functionalities required for the technical validation campaign (i.e. until the end of the Iris Programme) Service validation o What would have to be carried out in practice after the technical validation? identify potential regulatory issues 14
WP4 Financial analysis Aim: define the conditions for financial sustainability of the service Revenue model o For ATS services o For AOC services Business case o Define investment profiles o Study a Public Procurement and Public-Private partnership schemes Sensitivity analysis o What influences the sustainability of the business case? o Which are the go/no go conditions for a PPP? 15
WP5 Strategic analysis Aim: prepare future activities Definition of pre-requisites for private investment o For a satellite operator o For service providers Risk analysis Support to the preparation of Iris Programme Phase 2.2 o Which role for satellite operators, satellite service providers, and CSPs? o Which are your conditions to participate in Iris Phase 2.2? 16
Any questions? 17
Iris - Contact Points ESA Iris Programme Franco.Ongaro@esa.int Nathalie.Ricard@esa.int ESA Iris System Design Studies Andrea.Santovincenzo@esa.int (Satellite System) Catherine.Morlet@esa.int (Communication System) Tony Azzarelli (Regulatory / frequency management) Documentation available via www.telecom.esa.int/iris 18