ARIANE 6 The new Governance in Ariane world

Transcription

1 ARIANE 6 The new Governance in Ariane world

2 Key objectives for Ariane 6 1. Autonomous access to space for Europe 1. Family of launchers addressing both institutional and commercial markets (scale factor) 2. Implementation of European Preference principles for institutional launch services 2. No more public support to commercial exploitation 3. Increased market share, reduced running costs and total cost of ownership 3. Respecting time-to-market (maiden flight in 2020, full operational capability in 2023) 4. Fast track development plan and simplified management rules for minimized decision time 4. Maximizing commonalities within the European launcher family 5. Common Solid Rocket Motor P120C with Vega-C (implying specific organization) and maximal reuse from A5 (Main stage) and ME (Upper stage) 5. Transferring risks to the Private sector 6. Increasing industrial responsibilities by entrusting a Design Authority to ASL that delivers related warranties. 7. Ensuring continuity between development and exploitation. 8. Commercial exploitation borne by the Private Sector. 2

3 Reference documents on new governance for Ariane 6 Program Memorandum of Understanding concerning the development of the Ariane 6 Launch System Including mainly Objectives (defining general principles of the new governance for Ariane 6) Roles and responsibilities of ESA as Procuring Entity and Launch System Architect, CNES as Launch Base Prime and ASL as Launcher System Prime Contractual principles Main principles of the sharing of risks related to the development of the launcher system High Level Requirements for Ariane 6 Launch System A6-HLR-0-X ESA Including mainly Overarching requirements reflecting Ariane 6 key objectives Mission requirements for institutional and commercial missions Contract principles and industrial policy requirements Management requirements ESA Applicable Documents architecture is reported in annex 3

4 Roles & responsibilities in Ariane 6 development Element Entity Roles & Responsibilities Launcher System Airbus Safran Launche rs Prime Contractor for Launcher Development Design Authority Defines the High level Requirements (HLR) specific to commercial missions Proposes Launcher needs for the launch base to be reflected in interface requirements, including operational requirements. (*) Launch base CNES Prime Contractor for Launch base Development Design Authority Proposes launch base needs to be reflected in interface requirements, including operational constraints. (*) Launch System ESA** Development Procuring Entity Defines the launch system HLR and in particular the HLR specific to institutional missions. Checks compliance with the launch system HLR Accepts the deliverables of the Launcher and Launch Base development contracts Carries out Ariane 6 maiden flight with the support of the Launch Service Provider (***) Launch System Architect Defines the set of Launcher / Launch base interface requirements (IRD) by integrating Launcher System and Launch Base inputs Ensures coherence between Launcher & Launch Base with support from Airbus Safran Launchers and CNES Manages the definition and execution of Launch System validation tests Launch Certification CNES Checks compliance with French Space Operations Act (FSOA - RT/REI) throughout development * Both Prime Contractors also directly coordinate their respective actions ** In its role, ESA will be assisted by other Agencies, notably by CNES as Main ESA Technical Assistant as explained in next slide *** ESA takes the role and responsibility as qualification launch operator in front of French Authority as defined in FSOA 4

5 Innovative features of Ariane 6 development versus previous Ariane developments High Level Requirements (HLR) Instead of detailed technical and management specifications, relying on design choices and management solutions, the development of the Launch System will be based on a set of High Level Requirements (HLR) collecting : Overarching requirements Institutional mission requirements under the responsibility of ESA Commercial mission requirements under the responsibility of Airbus Safran Launchers Management requirements Contract principles and industrial policy requirements Design Authority Both Prime Contractors on their respective perimeters are entrusted with a Design Authority which entails: Responsibility to define the applicable design standards Responsibility to perform design choices and technical trade-offs Signature of the Launcher Qualification Certificate Liable for design and product warranties during development and exploitation phases Visibility given to ESA during development phase Increased accountability This increased autonomy for Airbus Safran Launchers is a counterpart to the transfer of risk, with associated financial consequences linked to the Launcher System development contract (with increased liability compared to previous contracts). In particular, risks linked to shortfalls, state of the art issues will be under its responsibility. 5

6 Focus on Ariane 6 Launch System Architect ESA bears the responsibility of the launch system validation by assuring coherency between Launcher System and Launch Base definitions. This will include responsibility over the interface requirements verification and interface products validation that is achieved through classical methods like analysis, review of design and integrated (combined) tests. Qualification flight campaign is presently deemed to be part of the Launch System check-out in the frame of the Launch System hand-over to Launch Service Provider This function is provided by a dedicated part of the ESA Ariane 6 Project Team, the Launch System Architect team Some specific roles and tasks in the launch system architect responsibility perimeter will be contracted to ASL and CNES Primes to exploit their specific competences in the relevant domain and to foster coherence and synergies with Launcher System and Launch Base products respectively January

7 New contractual principles in Ariane 6 development A payment plan based on a limited number of milestones Launcher system development milestones will be associated with a limited number of deliverables and reviews (to be agreed between the concerned Parties). An indirect payment scheme There will be no more direct payment from ESA to subcontractors Payment by Airbus Safran Launchers to its subcontractors will be put in place, granting visibility to ESA and providing appropriate justifications in case of deviations. Incentive and penalty scheme The launcher system development contract will include an incentive and penalty scheme according to the following two sets of criteria: Development schedule, including maiden flight; Launcher performance, including technical performance, planning, costs and stability of the requirements towards external interfaces (in particular the Launch base). 7

8 Principle for the definition of a Governance scheme in exploitation for Ariane 6 - ESA Resolution for Access to Space The Resolution on Europe s access to Space adopted on 02/12/2014 introduces principles for an agreement on A6 Exploitation governance to be concluded between the concerned parties in 2016 and underlines: On Private side : ASL will bear all commercial market risks during exploitation without support from Member States under the understanding that ASL will control the commercial exploitation of the launch service when On Public side : a number of launches will be contracted per year by different institutional actors in Europe that consider as a collective priority and an individual benefit to use competitive European-developed launchers. The preparation of an agreement among European institutions is necessary to mandate ESA to negotiate with the future launch service provider a collective framework contract for launch services procurement to be signed in 2018 confirming the guaranteed prices and related conditions. The number of institutional launches is not defined in the Resolution. A number of 5/year was considered by ESA and Airbus DS and SAFRAN during the Ministerial Conference preparation as a realistic assumption from both Public and Private perspective January

9 ANNEX: Ariane 6 Documents Specification s applicable Tree to Ariane 6 Development Programme Launch Service Ins0tu0onal Needs - ESA Member States - InsVtuVonal Missions Synergies (e.g. VEGA) Launch System HLR (MRD data in a5achment) JV Commercial Needs Launch System (Level 0) IRD 1/3 LS / Payload SRD- 1* Launcher System ST- 0 DF- 0 DV- 0 CONOPS- 0 IRD 1/2 SRD- 2* A6 Launch Base IRD 2/3 Launcher System LSPC ST- 1 DF- 1 / DV- 1 Standards Launcher System needs for ½ interface ICD- 1/2** Launch Base needs for ½ interface ST- 2 DF- 2 DV- 2 A6 Launch Base **ICD- 1/2: This document is managed by ESA throughout the development phase. Set of requirements for Launcher System Set of requirements for Launch Base * SRD- 1 and SRD- 2 could be defined in a unique document 9

10 Thank You For Your Attention