EDA / ESA INDUSTRY DAYemits.sso.esa.int/emits-doc/ESTEC/DeSIRE2_IndustryDay... · 2014-03-27 · EDA / ESA INDUSTRY DAY . Demonstration of the use of Satellites complementing RPAS

EDA / ESA INDUSTRY DAY

Demonstration of the use of Satellites complementing RPAS integrated in non-

segregated airspace (DESIRE II)

EDA premises 21 March 2014

ESA Unclassified – for official use

ESA UNCLASSIFIED – For Official Use DESIRE 2 Industry day | 21/03/2014 | Slide 2

AGENDA


Introduction

David Chinn Head of Unit Air Domain and EDA R&T Coordinator European Defence Agency

Amnon Ginati Head of the Integrated and Telecommunications-related Applications Department European Space Agency


EDA-ESA collaboration on RPAS (1)

ESA and EDA collaboration on RPAS started in 2009 (1st ESA/EDA workshop May 5th 2009) with the aim of supporting RPAS integration in the general airspace.

EASA and Eurocontrol have joined this initiative supporting the DeSIRE and DeSIRE2 projects.


EDA-ESA collaboration on RPAS (2)

ESA UNCLASSIFIED – For Official Use

4th user/stakeholder RPAS workshop Noordwijk, 29/11/2013, ESA-TIAA-HO-2013-99

M.A. Gonzalez Lopez D. Chinn (EDA)

L. Duquerroy

R. Rinaldo (ESA)

ESA/EDA DeSIRE 2 Industry day 21st March – EDA premises, Brussels

DeSIRE 2 demonstration

project

ESA-TIAA-HO-2014-178


Table of Content

Recall: DeSIRE

DeSIRE 2 objectives

Project requirements

Work Logic


DeSIRE demonstration project

• Kicked-off in August 2012. Final Presentation was held in November 2013

• Led by Indra (ES) with AT-One (DE), SES (LU), TAS-I (IT), TAS-F(FR) as sub-contractors

• It addressed the needs of governmental organizations responsible for maritime surveillances operations:

• It was supported by a wide range of RPAS potential users and stakeholders from different countries (France, Germany, Italy, Netherlands and Spain)

• The Spanish Guardia Civil played a key role in the demonstration as user

• It addressed the capability of safe insertion of RPAS in non-segregated airspace, based on requirements defined by aviation/regulatory authorities (EASA , EUROCONTROL, local authorities)

• The demonstration campaign took place in Murcia, Spain, over south-east Spanish Mediterranean sea, on 22nd-24th April.


DeSIRE System overview

ATC: Air Traffic Control BLOS: Beyond Line of Sight CNPC: Control and Non Payload Communication (RPA Command and Control and ATC communication relay) GDT: Ground Data Terminal LOS: Line of Sight OPAC: Operation Payload Analysis Center RPA: Remotely Piloted Aircraft RPS: Remote Pilot Station SIVE: External Surveillance Integrated System (Guardia Civile) UPL: Uplink RT: Return link

Mission communications (Payload data, payload Command & control)(BLOS)

CNPC incl. ATC (BLOS)

CNPC incl. ATC (LOS)

ATC



Civil operational area

military operational area

BLOS satellite antenna

LOS antenna



maritime patrol radar data with AIS data

multimission optronic stabilized payload data



DeSIRE key facts (I)

• The Maritime Surveillance mission was performed during day and at night (3 missions of around 6 hours each), with mission information integrated into the Spanish Guardia Civil border surveillance system in near real time

• Mission objectives: • Detection and location of targets on sea and on the coasts • Tracking, recognition and identification of targets on sea and on the coasts

• Payload data collected by the RPAS was provided in real time to the ground using satellite communications:

• Maritime Patrol Radar Data • multimission optronic stabilized payload data (optical and Infra Red video) • AIS data

• Based on the data received, the Spanish Guardia Civil confirmed that such a service

can satisfy their needs for maritime and coastline surveillance, complementing their existing infrastructure.


DeSIRE key facts (II)

DeSIRE provided initial proofs that such RPAS controlled through satcom links can safely fly in European civil controlled airspace (Class C) under ATC guidance:

• Demonstration that RPAS in BRLOS conditions relying on SatCom could timely proceed with ATC instructions/clearances in non-segregated airspace (civil controlled Class C), notably with a realistic separation exercise

• Coordination with civil and military ATC for entering and leaving different control areas (military /civil)

• The performances of the BRLOS satellite based communications used during the demonstration campaign were analyzed, and gave promising results in terms of latency, continuity, integrity and availability, although stakeholders expressed the need of performing more extensive validation under different conditions (e.g. weather, bandwidth, channel access)

• Safety measures and contingency procedures for BRLOS communication loss (i.e. back-up telephones lines, return to home procedures) were defined, implemented and approved by local authorities, and could be used as a basis for future operations

• Improved situational awareness was available to the pilot using data from on-board sensor and terrestrial infrastructure (ATC radar data), and its added value for improving the safety of RPAS operations was demonstrated.


DeSIRE2 Objectives

To develop and demonstrate a service based on a RPA flying Beyond Radio Line of Sight (BRLOS) using space assets (SatCom, SatNav) for: 1. supporting the regulatory process within the European context: focus on BRLOS

operations under Instrument Flight Rules (IFR) using satellite communications

2. providing new applications to relevant user communities

This entails the following perspectives: Regulatory perspective: demonstrate a set of capabilities (in terms of e.g.

performances, operational procedures) contributing to some of the regulatory improvements set forth in the ERSG Roadmap.

User perspective: develop and demonstrate the application(s) in pre-

operational conditions, allowing for operational service provision shortly after the completion of the project.

Technology perspective: demonstrate the technology required for supporting the regulatory improvements defined by ERSG as well as for satisfying user needs.


ERSG Regulatory WG Roadmap

ESA ARTES 1 activity

DeSIRE

DeSIRE 2


General system architecture (recall)

Air Traffic Control/Services (ATC/S)

Satellite Relay of• Payload Communication (data, payload control and command)and• Control and Non-Payload communications (including ATS and D&A communications)

ATS (2)

The RPA carries a payload, e.g. camera, radar, or other

electronic sensors

Operation Payload Analysis Center

(OPAC)

Ground Control Station (GCS)

CNPC(BRLOS) (1)

Satcom assets

Satnav(GPS, EGNOS)

CNPC(RLOS)(1’)

Payload dataAnd C2

(BRLOS) (3)

Payload Communications

CNPC (incl. ATS and D&A communications)

Back-up terrestrial link(s)

Use of a European platform is preferred!


Air Traffic Insertion requirements: regulatory perspective (1/3)

AR – 1 Concept of Operations (CONOPS) The RPAS Satellite based Data Link CONOPS shall be established and validated as well as the demonstration system architecture. The CONOPS shall detail the way BRLOS link performances (AR-3) will be evaluated for the different frequency bands (AR-4) in order to conclude on their compliance with the Safety requirements (AR-2).

AR - 2 Safety requirements The safety requirements (in terms of availability, continuity, integrity and latency) related to the Satellite based Data Link for C2/ATS and D&A shall be consolidated and justified against the generic safety objectives, by considering:

• appropriate split between terrestrial and satellite component • dependency on the level of autonomy of RPAS and severity of hazards

AR - 3 BRLOS Link performances BRLOS link Performances (quality/bit error rate, availability, latency) shall be verified with respect to safety requirements, entailing performing accurate and extensive measurements, preferably also in degraded conditions (i.e. low elevation angle, bad weather).



AR - 4 Multiple frequency bands The compliance of BRLOS link Performances requirements (AR-3) with Safety Requirements (AR-2) shall be evaluated for various frequency bands among which conventional satellite bands (Fixed Satellite Service or Mobile Satellite Service) and bands allocated to the Aeronautical Mobile Satellite (en Route) Satellite Service AMS(R)S.

AR - 5 Cost-efficient bandwidth allocation Satellite capacity shall also be allocated according to cost-efficient bandwidth allocation scheme (e.g. data oriented scheme).

AR - 6 Latency improvement Improved latencies for Air Traffic Services communications shall be demonstrated, notably by separating ATC communications from Payload communications



AR - 7 D&A data transmission D&A data derived from dedicated sensors shall be transmitted via satcom in BRLOS for situational awareness and preferably also for traffic avoidance AR - 8 Emergency procedures Enhanced emergency procedures shall be demonstrated (multiple failure conditions)

AR – 9 Satellite hand-over The switch over between 2 different satellite systems shall be preferably demonstrated, otherwise simulated AR-10 Non segregated airspace The demonstration of the RPAS based service shall be conducted under guidance of the competent civil ATC, in non-segregated air space under IFR for part of the demonstration


From DeSIRE to DeSIRE2

DeSIRE DeSIRE2

CONOPS Yes Yes

Safety requirements Preliminary Consolidated

BRLO Link performances Partial assessment Accurate and extensive measurements, preferably also in degraded conditions

Multiple frequency bands No Yes

Cost-efficient bandwidth allocation

No Yes

Latency improvement No Yes

D&A data transmission Partial (no dedicated sensor), for situational awareness

Dedicated sensors, for situational awareness and preferably also for traffic avoidance

Emergency procedures Limited Multiple links failure

Satellite hand-over No Yes

Non segregated airspace Yes Yes


Achieving the ATI requirements

The activity, and particularly CONOPS establishment and safety requirements

consolidation (AR-1 and AR-2), shall build on the most recent developments in the European regulatory fora as well as on the results of precursor ESA activities (e.g. ESA ARTES 1 activity “Certification requirements and performances standards of satcom links for RPAS C2/ATS/D&A”)

Emulation combined with analytical analysis shall be undertaken in

complement to the demonstration campaign to achieve the targeted objectives, notably on satcom link performances assessment.


Mission requirements (user perspective) (1/3)

MR – 1 Application/Service The utilization of RPAS complemented by satellites shall be demonstrated in the users’ context for civilian applications such as:

Maritime Surveillance and Border Control Environmental Surveillance Monitoring of critical infrastructure Law enforcement Crisis management

MR - 2 User Engagement Representatives of the user community of the selected application/service shall participate to the project with the following tasks as a minimum:

define the user requirements, integrate the RPAS service in their operational system, take part of the demonstration campaign, validate the demonstration results, validate the defined service delivery concept.


Mission requirements (user perspective) (2/3)

MR – 3 Mission data transmission The added value for the users of the transmission of mission data from the RPA through the satcom link shall be demonstrated.

MR – 4 Service delivery concept The integration of the data provided by the RPAS in the users’ operational system shall be performed and extensively demonstrated for validating the service delivery concept. MR – 5 Readiness for operational service The service to be demonstrated and the technology to be used shall be selected planning a start of operations shortly after project completion (taking into account the planned European regulatory evolution).


Mission requirements: (user perspective) (3/3)

MR – 6 Mission area Most of the mission area, as well as some parts of the en-route flight, shall be located BRLOS. MR - 7 RPAS selection

The RPAS performances in terms of endurance and altitude and payload sensors shall satisfy the needs expressed by the user(s) involved in the project.


Work logic

Duration : 18 months

2 consecutive phases:

Phase 1 : demonstration preparation (maximum 6 months duration).

Phase 2 : developments (if any), demonstration execution and results analysis.


Phase 1 logic

Task 1Demonstration requirements

consolidation

KO

Task 2Demonstration Concept and

System architecture definition

Task 3 – 1st partDemo Authorisation/Approval

acquisition

CDR

BDR


Phase 1 task description (I)

Task 1 Demonstration requirements consolidation • Consolidation of ATI aspects / regulatory improvements to be addressed during the

demonstration and definition of detailed ATI requirements (to be agreed with EASA and Eurocontrol)

• Collection of the users needs and definition of the user requirements • Definition of the Demonstration System Architecture and Flight campaign

requirements, as well as emulation requirements

Task 2 Detailed demonstration concept and system architecture definition • Definition of the demonstration mission details (geographical location, flight plan,

flight tests) and design of the system architecture. • Definition of the safety case and contingency procedures in accordance with local

stakeholders (ANSPs, airport Authorities, etc). • Simulations to pre-validate demonstration flights if needed • Definition of complementary emulations and needed tools (e.g. test bed/emulator). • Definition of the development and procurement plans. • Provide a first iteration of the service delivery concept of the system for the users

involved in the project.


Phase 1 task description (II)

Task 3 Demonstration authorization / approval acquisition – 1st part

• Perform the actions to get the necessary authorisations, certificates and approvals from the relevant authorities to perform the demonstration flights

• Evidence demonstrating that all the needed actions have been launched and the required authorisations will be obtained in due time for the scheduled demonstration campaign shall be provided at the end of phase 1.


Phase 2 logic


Phase 2 task description (I)

Task 3 Demonstration authorization / approval acquisition – 2nd part • Finalisation of the actions to obtain the necessary authorizations, certificates and

approvals to perform the demonstration flights

Task 4 System development and integration • Perform the required development, integration and procurement actions for the

demonstration system, as well as for emulation system. • Verification of the full demonstration system and emulation system. • Demonstration of the readiness of the system to start the demonstration .


Task 5 Demonstration campaign and results assessment • Performance of the demonstration campaign and ancillary

simulation/emulation tests and collection of the results • Collection of the feedback from users and other stakeholders

Task 6 Results assessment, recommendations for follow-on actions and results dissemination

• Results analysis, assessment and conclusions. • Consolidation of the safety requirements and establishment of the CONOPS for a

Satellite based Data Link service for RPAS. • Consolidation of the service delivery concept • Dissemination of the obtained results • Recommendations for further initiatives

Phase 2 task description (II)


4th user/stakeholder RPAS workshop Noordwijk, 29/11/2013, ESA-TIAA-HO-2013-99

Information on Tender Procedure

L. Duquerroy R. Rinaldo C. Piesche

(ESA)

ESA/EDA DeSIRE 2 Industry day 21st March – EDA premises, Brussels


Table of Content

Funding aspects

ESA tender procedure

ITT timeline


Funding aspects (I)

A co-funding scheme requiring a financial contribution from the Industry is applied.

Envisaged overall projected costs are 2,400,000 EUR, of which: EDA funds 600,000 EUR, Industry’s contribution is anticipated to be 600,000 EUR IAP ARTES20 will match the EDA plus Industry’s contribution up to a

maximum of 1,200,000 EUR (up to 50% of the projected costs)


Funding aspects (II): Eligible costs

In addition to manpower effort, eligible cost elements could be related to: • the lease and/or procurement of equipment for the project,

• amortized costs related to the in-kind provision of own assets,

• and other costs to be borne by the Contractor, sub-Contractor(s) and Users

for performing the project tasks.

In its proposal, the bidder shall explicitly report all the project costs in the PSS forms.


Funding aspects (III) EDA funding

EDA funding (600,000 EUR) is

accessible only to industry residing in an EDA participating Member State.

To date EDA participating Members States are: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden and United Kingdom.


Funding aspects (IV)

Attached to the cover letter accompanying their Full Proposal, tenderers shall submit a statement (“letter of support”) signed by their National Delegate(s) representing the country in which the Prime and, if applicable, his subcontractor(s) reside(s), authorising the Agency to fund the quoted ESA ARTES20 price share from their contribution to the ARTES20 Programme.

Contact information of all National Delegations : http://iap.esa.int/delegates.

IAP ARTES 20 (up to 50% of total budget, 1,200,000 EUR maximum) is accessible only to Industry from a State which subscribes to the ESA ARTES 20 Phase 2 and has the support of the national delegation for the present activity.

To date ESA ARTES 20 Phase 2 Participating States are : Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Ireland, Italy, Luxembourg, the Netherlands, Norway, Poland, Portugal, Romania , Switzerland and United Kingdom.

http://telecom.esa.int/telecom/www/object/index.cfm?fobjectid=8043


Procurement aspects

Open-competitive tender, addressed to companies from ESA ARTES 20 Participating States and EDA Participating Member States will be issued.

The procurement procedure will follow ESA’s Procurement Regulations and related Implementing Instructions (ref. ESA/REG/001 rev. 3) The tenderer will be selected by a TEB composed of ESA/EDA

representatives One contract only (party to the contract : ESA and selected Bidder) Contract will be governed by General Clauses and Conditions for ESA

Contracts (GCC)(ref. ESA/REG/002 rev.1)

ESA Procurement rules and ESA GCC are available on http://emits.sso.esa.int/emits/owa/emits.main, under "Reference Documentation" ---> "Administrative Documents"


Invitation To Tender (ITT) Planning

The DeSIRE 2 ITT is planned to be issued by beginning of Q2 2014 The ITT will be published on the ESA Invitations to Tender on-line tool EMITS

• http://emits.sso.esa.int/

• Registration is required to access ITTs documentation

A notification will also be published within EDA Procurement Gateway:

http://www.eda.europa.eu/procurement-gateway

During the tendering period, all clarification questions need to be addressed

to the responsible ESA Contracts Officer.

http://emits.sso.esa.int/

http://emits.sso.esa.int/


Thank You

Contacts:

M. Gonzalez Lopez (EDA): [email protected]

R. Rinaldo (ESA): [email protected]

mailto:[email protected]