EGNOS Adoption in Aviation - GSA/GRANT/06/2017

Deadline: May 21, 2018  
CALL EXPIRED

1. CONTEXT

1.1. Introduction

The European Geostationary Navigation Overlay Service (EGNOS) provides an augmentation signal to the Global Positioning System (GPS) Standard Positioning Service (SPS). Presently, EGNOS augments GPS using the L1 (1575.42 MHz) Coarse/Acquisition (C/A) civilian signal function by providing correction data and integrity information for improving positioning and navigation services over Europe.

Currently the system delivers the following services:

•   An EGNOS Open Service (OS), which is free of charge to the user and provides positioning and synchronisation information intended mainly for mass market and general navigation applications in the area covered by the EGNOS system. The EGNOS Open Service was declared on 1 October 2009.

•   An EGNOS Safety of Life service (SoL), which is available free of charge to all European users within the service coverage area and is tailored for safety critical applications which have stringent accuracy, integrity, continuity and availability needs. The EGNOS SoL service was declared on 2 March 2011 and enables RNP APCH down to a minimum as low as 200ft without the need of any ground infrastructure installation as of October 2015, LPV-200 service was declared and enables aircraft approaches that are operationally equivalent to ILS CAT I: providing lateral and angular vertical guidance without the need for visual contact with the ground until a Decision Height (DH) of down to only 200 ft above the runway. These EGNOS-based approaches are considered as ILS look-alike, but without the need for the expensive ground infrastructure required for ILS. EGNOS LPV-200 service requires no upgrade to an airport’s ground infrastructure or to existing certified EGNOS receivers.

•   An EGNOS Data Access Service (EDAS) to promote the development of applications for professional or commercial use by providing data with greater added value than those obtained through the EGNOS Open Service; The EGNOS Data Access Service was declared on 26 July 2012.

  EGNOS improves flexibility allowing performance based navigation (PBN), for advanced arrival, approach and departure procedures at European aerodromes and helipads. The specific objective is to ensure a safe, efficient and harmonised implementation of specific PBN specifications and functionality in the European Air Traffic Management Network (EATMN).

  In achieving this objective, there are some main regulatory activities affecting EGNOS adoption which are currently effective or under discussion:

•   Pilot Common Projects (PCP) Implementing Rule (IR): Commission Implementing Regulation (EU) No 716/2014, dated 27 June 2014 on the establishment of the Pilot Common Project supporting the implementation of the European Air Traffic Management Master Plan. This IR is targeting the implementation of PBN RNP APCH vertically guided (LNAV/VNAV and LPV) at all 24+1 airports and PBN SIDs/STARs/Transitions (with RF leg) by 01/01/2024.

•   PBN Implementing Rule, the Notice of Proposed Amendment (NPA) 2015-01 “Performance-Based Navigation (PBN) implementation in the European Air Traffic Management Network (EATMN)”, RMT.0639 — 19.1.2015, issued by EASA, addresses the safety, interoperability, proportionality and coordination issues related to the implementation of Performance Based Navigation (PBN) within European airspace. This NPA extends the PBN implementation requirements beyond the 24 EU aerodromes as required by the PCP, mitigates the risks associated with a non-harmonised implementation, thus ensuring a smooth transition to PBN operations, fully supporting the implementation of the European Air Traffic Management Master Plan. This regulation is under discussion and is targeting the PBN approach procedures with vertical guidance at all instrument runway ends in coming years. Aircraft operators wishing to operate these routes and procedures will be required to ensure that their aircraft and flight crew are approved for PBN operations.

•  EGNSS for Surveillance- ADS-B: The European Commission has published Commission Implementing Regulation (EU) No 1207/2011 and (EU) No 1028/2014 laying down requirements for the performance and the interoperability of surveillance for the Single European Sky. These regulations stipulate mandatory milestones comprising the implementation of ADS-B airborne capability on new-build aircraft and the upgrading and retrofitting of such equipment in previous-build examples. The existing regulations are currently under discussion. However, EGNOS is not required by European regulations, it improves localization information to be used on-board the aircraft. SBAS-based positioning ensures higher availability (99% availability) with respect to GPS/RAIM and enables enhancing both surface and airborne (e.g. ADS-B) surveillance functions. Following the conclusions of an analysis carried out by the European GNSS Agency (the GSA), the increased availability enabled by GNSS/EGNOS can support surveillance functionality, lead to costs saving for ANSPs and reduce reliance on the current infrastructure, as justified by a safety assessment.

In conclusion, the operational implementation of EGNOS in aviation is a strategic goal to ensure the success of the programme and comply with the EU Navigation strategy. In this context, the objective of this call is to foster EGNOS adoption in the European civil aviation, enabling on the one hand users to equip and use their aircraft/rotorcraft fleet with GPS/SBAS enabled avionics and, on the other hand, Air Navigation Service Providers and aerodromes/heliports to implement EGNOS based operations in Europe.

1.2. Background of the call

Under the Delegation Agreement concluded between the European Union, represented by the European Commission, and the GSA on the Exploitation Phase of the EGNOS Programme signed on 16 April 2014, the GSA is entrusted with the management of operational activities relating to the exploitation of the EGNOS Programme, including infrastructure management, maintenance and continuous improvement in accordance with the Programme Management Plan.

In this framework, and in accordance with the EGNOS Exploitation Grants Plan 2017 published on the GSA website (https://www.gsa.europa.eu/sites/default/files/egnos_annual_2017_grants_plan_0.pdf), the GSA is launching a call for proposals to increase EGNOS adoption in civil aviation.

 

2. OBJECTIVES AND SCOPE OF THE CALL

2.1. Objective of the call for proposals

The purpose of this call is to award a number of grants to foster EGNOS operational implementation for commercial aviation, regional aviation, business (corporate) aviation, general aviation (training, emergency services) and rotorcraft, considered the main aviation market segments for EGNOS and those maximising public benefits in order to increase and foster a network effect on current development of EGNOS enabled operations. Original Equipment Manufacturers (EOM) interested in benefitting from EGNOS may also apply to the call. The result of this activity will be a wide scale operational implementation of the EGNOS based operations throughout European airports and airspace users.

In particular, the objectives of this call for proposals is to foster EGNOS adoption in the European aviation by enabling users to equip their aircraft/rotorcraft fleet with SBAS/EGNOS enabled avionics, Air Navigation Service Providers and airports/heliports to publish RNP APCH down to LPV/LPV200, /Point in Space procedures (PinS) and low level IFR routes in Europe. It will also consider pilot cases on advanced navigation operations benefitting from EGNOS and activities promoting the use of EGNOS for other communication, navigation and surveillance applications in all phases of flight.

2.2. Scope and areas of activities of the call for proposals

In order to reach the objectives of the call, beneficiaries are expected to conduct at least one of the following activities:

• -  The design, development and operational implementation of EGNOS LPV/LPV 200 approach procedures,

  PinS, low level IFR routes at different European airports/heliports/routes.

• -  Design and implementation of other communication, navigation and surveillance applications benefitting

  from EGNOS for all phases of flight.

• -  The installation of EGNOS enabled avionics and granting of airworthiness certification for RNP APCH

  procedures down to LPV minima, including PinS.

• -  Development of retrofit and forwardfit solutions including LPV capabilities.

-  Development of enablers and other EGNOS based operations, such as, but not limited

to simulators, validation tool, training materials or drones.

The additional ADS-B functionality using EGNOS together with the LPV capability is also eligible under this Call.

Activities falling within one or more of the areas described below shall be eligible under this call for proposals:

A – RNP APCH procedures to LPV/LPV200 minima

Projects under this area of activity shall focus on the design, development and publication of EGNOS LPV approach procedures at European airports, aiming at publication of 3D approach procedures in accordance with the requirements of the RNP approach (RNP APCH) specification at European airports, including LPV/LPV200minima. Activities including radius to fix (RF) legs and RNP authorisation required approach (RNP AR APCH) leveraging EGNOS are also eligible. Activities typically required to set up such PBN Instrument Approach Procedures may include, among others, procedure design (according to APV SBAS and SBAS Cat I design criteria), obstacle survey, safety assessment, ground and flight validation, training for air traffic control officers and/or pilots, and publication. Proposals shall contribute to track actual EGNOS based performed approaches in Europe. Applications are mostly expected from ANSPs, aerodrome owners or airport operators.

B – PinS Procedures to LPV minima and Low Level Routes This area of activity is focused on helicopter specific operations, such as Point in Space (PinS) approach operations and Low Level Routes leveraging EGNOS. PinS approaches may be implemented to serve heliports, helipads or oil rigs, and even be designed as Simultaneous Non-Interfering Approaches (SNI) to avoid conflicts with fixed-wing traffic operating at a certain airport. The proposal shall envisage the operational implementation of the new PinS procedures including LPV minima and connecting routes based on EGNOS by the end of the project. Proposals shall contribute to track actual EGNOS based performed approaches and routes in Europe and the development of RNP 0.3 routes where GNSS prediction is replaced by EGNOS. Cross border routes are encouraged. Applications are mostly expected from ANSPs, airport/heliport owners or airport/heliport operators.

 

C – Aircraft or rotorcraft forward fit

A large number of aircraft currently under production include LPV approach capabilities as part of their standard avionics suites. This is becoming a trend for most regional, business and general aviation new models. However, certain aircraft OEMs may include the SBAS LPV capability as an optional package in some of their models. The additional ADS-B functionality using EGNOS together with the LPV capability is also eligible under this area.

A proposal addressing this area of activity shall target the development of SBAS/EGNOS LPV (including, but not mandatory, ADS-B capability using EGNOS) in new aircraft models and/or its entry into operation. Proposals shall contribute to track actual EGNOS based performed approaches in Europe in case the proposal addresses the SBAS upgrade for LPV applications. Applications are mostly expected from aircraft or rotorcraft OEMs and operators.

D – Aircraft or rotorcraft retrofit

This area of activity focuses on in-service aircraft and rotorcraft not certified to perform LPV approaches. Proposals should target the tasks to achieve operational use of the LPV capabilities, including hardware upgrades or acquisition, hardware installation and certification and/or obtaining the specific operational approval from the national authority, when necessary. Proposals may also include flight demonstrations. Airframes already equipped with the suitable avionics, may require funding contribution to obtain specific approval.

A proposal addressing this area of activity shall target the development of SBAS LPV in new aircraft models and/or its entry into operation. The additional ADS-B functionality using EGNOS together with the LPV capability is also eligible under this area. Proposals shall contribute to track actual EGNOS based performed approaches in Europe in case the proposal addresses the SBAS upgrade for LPV applications. Applications are mostly expected from aircraft or rotorcraft operators from all market segments: Commercial, Regional, General and Business, including government operators - for aircrafts used in commercial operations - and flight inspection/validation operators.

E – Development of Service Bulletin and/or Supplemental Type Certificate

This area of activity addresses the development of SBs and/or STCs involving SBAS LPV and their commercialisation.

Aircraft or rotorcraft manufacturers may generate Service Bulletins (SBs) to include SBAS LPV capabilities in some of their models. These improvements are usually offered to customers as optional items for purchase. Applications for SBs development are mostly expected from aircraft or rotorcraft manufacturers. Supplemental Type Certificates (STCs) are major modifications to an existing type certified aircraft. STCs are usually developed, designed and owned by non-TC holders (Part-21 EASA approved organisations). Applications including STCs development are mostly expected from EASA Part-21 organisations (DOA) and avionics manufacturers. Proposals shall contribute to track actual EGNOS based performed approaches in Europe.

F – Development of enablers and other EGNOS based operations adoption

This area of activity addresses the development of enablers to accelerate EGNOS adoption and its operational use by civil aviation. Proposals may include but not be limited to hardware/software development, processes implementation and related trials. The proposals should demonstrate the need for such enablers by aviation stakeholders with short term impact on acceleration of EGNOS adoption and prove readiness of the proposer to accomplish the proposed tasks within the time of the project. Examples of activities in this area include development of simulators or validation tools for EGNOS based operations.

In addition, activities covered in this area of activity may also include other EGNOS based operations, beyond RNP approaches down to LPV minima, such as, but not limited to Communication, Navigation, Surveillance (CNS) applications and those described below:
- Advanced RNP (A-RNP) using SBAS and the use of curved segments with the RNP AR specification and

-

2.3. Core activities

A – RNP APCH procedures to LPV minima

As minimum the core activities shall include the coordination of the implementation.

B – PinS Procedures to LPV minima and Low Level Routes

As minimum the core activities shall include the coordination of the implementation.

C – Aircraft or rotorcraft forward fit

As minimum the core activities shall include coordination of the implementation, operational feedback, plus operational manual update, obtaining the operational approval and training unless it is strictly necessary.

D – Aircraft or rotorcraft retrofit

As minimum the core activities shall include coordination of the implementation, operational feedback, plus operational manual update, obtaining the operational approval and training unless it is strictly necessary.

E – Development of Service Bulletin and/or Supplemental Type Certificate

As minimum the core activities shall include coordination of the implementation, design of the STC/SB bulletin and achieving the certification.

F – Development of enablers and other EGNOS based operations adoption

This area of activity addresses the development of enablers to accelerate EGNOS adoption and its operational use by civil aviation. Proposals may include but not be limited to hardware/software development, processes implementation and related trials. The proposals should demonstrate the need for such enablers by aviation stakeholders with short term impact on acceleration of EGNOS adoption and prove readiness of the proposer to accomplish the proposed tasks within the time of the project. Examples of activities in this area include development of simulators or validation tools for EGNOS based operations.

 

In addition, activities covered in this area of activity may also include other EGNOS based operations, beyond RNP approaches down to LPV minima, such as, but not limited to Communication, Navigation, Surveillance (CNS) applications and those described below:

- Advanced RNP (A-RNP) using SBAS and the use of curved segments with the RNP AR specification and assessment

-  Use of EGNOS for RPAS robust and safe navigation aligned with the European standardization roadmap for RPAS. In particular, the activities in this area shall be aimed at developing operational concept, demonstrations and enabling the use of EGNOS for drones navigation and assessment of the added value, in topics such as, but not limited to: geofencing, vertical accuracy, final approach requirements and solutions, detect-avoid, non-interfering orbiting patterns-trajectories, operations in urban environments and very low level routes.

 

2.3 Core activities

For the purpose of this call the following activities (belonging to one or more of the six areas of activities described above in section 2.2) are considered core to the project:

 

A – RNP APCH procedures to LPV minima

As minimum the core activities shall include the coordination of the implementation.

B – PinS Procedures to LPV minima and Low Level Routes

As minimum the core activities shall include the coordination of the implementation.

C – Aircraft or rotorcraft forward fit

As minimum the core activities shall include coordination of the implementation, operational feedback, plus operational manual update, obtaining the operational approval and training unless it is strictly necessary.

D – Aircraft or rotorcraft retrofit

As minimum the core activities shall include coordination of the implementation, operational feedback, plus operational manual update, obtaining the operational approval and training unless it is strictly necessary.

E – Development of Service Bulletin and/or Supplemental Type Certificate

As minimum the core activities shall include coordination of the implementation, design of the STC/SB bulletin and achieving the certification.

F – Development of enablers and other EGNOS based operations adoption

The core activities in this area may vary depending on the content of the submitted proposal. Indicative core activities may include the system integration of EGNOS based receiver, the software development for EGNOS receiver integration or the EGNOS operations definition and development.

2.4. Deliverables

The beneficiaries are expected to submit during the implementation of the action a list of deliverables. Proposals (in B1 Form) should define a minimum set of deliverables together with the planning for their submission as follows:

 For Areas A and B - design, development and operational implementation of EGNOS LPV/LPV 200 approach procedures, PinS, low level IFR routes at different European airports/heliports/routes:

 

• -  Initial Report including evidence on: Feasibility, Cartography, Obstacle Survey, Conceptual and Initial Design Report and draft Chart;

• -  Chart for procedure with FAS DB information;

• -  Report from the flight procedure designer who review the procedure design, according to ICAO

  quality assurance process;

• -  Safety Assessment;

• -  Ground/Flight Validation Report taking into account all the investment, costs and savings coming

  from LPV usage;

• -  Final Report including evidence on: Procedure Design Report, ATCO training, approval, publication

  and effectiveness dates, EWA signature, Benefits-Risks and other comments.

•   For Area C - aircraft or rotorcraft forward fit:

  • -  Design data package;

  • -  Operation Approval and associated documentation;

  • -  Final Report including: summary of the complete process, dates, main barriers found, future

    expected, benefits/risks and other comments.

•   For Area D - aircraft or rotorcraft retrofit:

  • Airworthiness Certification and associated documentation;

  • Operation Approval and associated documentation;

  • LPV Procedure Flown Report;

  • Final Report including: summary of the complete process, dates, main barriers found, future expected, benefits/risks, tool to monitor LPV usage and other comments.

•   For  Area E - development of Service Bulletin and/or Supplemental Type Certificate:

  • Feasibility Analysis (including aircraft survey);

  • Design data package;

  • Compliance demonstration and EASA STC/SB approval;

  • Final Report including: summary of the complete process, dates, main barriers found, future expected, benefits/risks and other comments.

     

•   For Area F - development of enablers and other EGNOS based operations adoption:
  In this area, the minimum set of deliverables should be defined by the applicant(s) together with a short description of the content, their link with the project plan, the expected delivery date and periodicity. Indicative deliverables may be the commercially available enabler (hardware/software/certification) and/or operational implementation of the new EGNOS based operation. It shall also include one demonstration or other dissemination activity of the project result upon request by GSA.

2.5. Outputs expected from the implementation of activities

The proposals shall aim to achieve the objectives of the action. All the deliverables (as listed in section 2.4), will be used by EU and GSA in accordance with Articles I.9 and II.9 of the Grant Agreement.

 

3. TIMETABLE

Scheduled start-up date for the action: from the date of signature of the grant agreement, unless the applicants can demonstrate the need to start the action before the agreement is signed.

Indicative maximum duration of the action under (each) grant agreement: 2 (two) years.
 

a) Publication of the call
12 February 2018

b) Deadline for submission of request for clarification
30 April 2018

c) Deadline for GSA answering to request under b) above
15 May 2018

d) Deadline for submitting applications
21 May 2018 – at 18:00 Prague time

e) Evaluation period
June/July 2018

f) Information to applicants on the outcome of the evaluation
August 2018

g) Signature of the first Grant Agreement (s)
September/October 2018

 

4. EU FINANCING

Maximum budget allocated for EU financing under this call: EUR 10,000,000.00 Indicative number of projects: 12
Indicative EU financing amount for each project: EUR 800,000.00
Maximum EU financing rate of eligible costs: 60%

Publication of the call does not guarantee the availability of funds for the above action and it places no obligation on the GSA to award grants to any applicant.

GSA reserves the right to award a grant of less than the amount requested by the applicant. In such a case, the applicant(s) will be asked either to increase his co-financing, propose other co-financing means or to decrease the total costs without altering the substance of the proposal. Grants will not be awarded for more than the amount requested.

 

5. ROLES AND TASKS WITHIN THE CONSORTIUM

5.1. Entitiesinvolvedintheactivitiessubjecttotheproposal

The proposal shall clearly identify the entities (legal and/or natural persons) to be involved in the activities subject to the proposal, being the applicant1(s) (including coordinator and co-applicants) as well as any third parties, such as affiliated entities and subcontractors and their contributions to the implementation of the proposal under the grant agreement. Parties’ participation in the project will be subject to the requirements as laid down in this Call for Proposals.

5.2. Single Applicant

 

In case the proposal is submitted by a single applicant, it will be considered as mono-beneficiary if the proposal is successful.

5.3. Coordinator

If the proposal is submitted by a group of several co-applicants they will form a consortium and will become consortium members. The consortium members (multi-beneficiaries) should choose within their midst a lead organisation, referred to as the “Coordinator”.

The coordinator submits the application on behalf of the consortium and will be the intermediary for all communication between the co-beneficiaries and the GSA as well as responsible for supplying all documents and information to the GSA in due time upon request. The coordinator will also be responsible for distribution of payments received from GSA to the co-beneficiaries.

5.4. Co-applicant(s)

Each co-applicant will be considered as co-beneficiary if the proposal is successful. Before signature of the grant agreement all applicants within the consortium shall agree upon appropriate arrangements between themselves for the proper performance of the specific actions. Co-applicants are required to analyse the specific provision on financial recoveries as provided in the draft grant agreement.

Co-applicants shall immediately inform the coordinator of any event liable to substantially affect or delay the implementation of the action, who will communicate with the GSA subject to grant agreement as well as clauses ensuring compliance with the requirements on ownership and usage rights of results and any pre- existing rights towards the GSA and the European Union as specified in the draft grant agreement.

When a grant is awarded, the co-beneficiaries forward to the coordinator in a timely manner all the data needed to draw up the reports, the financial statements and other documentation required by the grant agreement.

The coordinator and all co-applicants forming the consortium must equally satisfy the eligibility criteria.

5.5. Affiliated entities

Legal persons having a legal or capital link with applicant(s), which is neither limited to the action nor established for the sole purpose of its implementation, may take part in the action as affiliated entities, and may declare eligible costs. For that purpose, applicant(s) shall identify such affiliated entities in the application forms and in the proposal.

Each affiliated entity shall have to comply with the same eligibility and non-exclusion criteria as those applying to the applicant(s) and submit the same forms, including the forms proving the financial and operational capacity (see section 9.1 and 9.2 below).

Affiliated entities can be:

1. a)  several legal persons forming together one legal person or 'sole beneficiary' which may, or may not,

   have been specifically established for carrying out the action (e.g. groupings, joint ventures).

2. b)  legal persons having a legal or capital link with a beneficiary or co-beneficiary, which is neither limited to the action nor established for the sole purpose of its implementation (e.g. networks, federations, trade-unions).

5.6. Subcontractors

Sub-contractors are not beneficiaries to the grant, nor affiliated entities.

Subcontracting2 refers to contracts concluded for the externalisation of specific tasks or activities which form part of the action.

The beneficiaries remain solely responsible for the implementation of the action. Subcontracting is not allowed among the beneficiaries in the project. Please note that the beneficiaries must have the necessary capacity to perform the project themselves.

Subcontracting of specific tasks or activities (i.e. the externalisation) which form part of the action as described in the proposal must satisfy the conditions applicable to any implementation contract (as specified above) and in addition to them the following conditions:

1. it may only cover the implementation of a limited part of the action and shall in no case cover core activities as described in Section 2.3;

2. it must be justified having regard to the nature of the action and what is necessary for its implementation;

3. it must be clearly stated in the proposal.

The applicants must have operational capacity to perform the work proposed in their proposal. This operational capacity will be assessed at the time of the evaluation of the proposal (please refer to section 9.2 below).

In exceptional cases, where the implementation of the action or the technical proposal (B1-B2 Forms) can be done more efficiently and effectively through the award of subcontracts (implementation contracts), the beneficiary must award the contract to the bid offering best value for money or the lowest price (as appropriate), avoiding conflicts of interests and retain the relevant documentation for the event of an audit. Entities acting in their capacity of contracting authorities in the meaning of Directive 2004/18/EC3 or contracting entities in the meaning of Directive 2004/17/EC4 shall abide by the applicable national public procurement rules.

The costs of subcontracting can be eligible under the conditions indicated in the grant agreement (see also point 2.8 in section 12.2 below). The proposal should clearly specify the activities that will be subcontracted in the description of the action and the corresponding costs must be indicated in the estimated budget. The contract should be awarded in accordance with the conditions set in the grant agreement. Recourse to the award of contracts must be duly justified having regard to the nature of the action and what is necessary for its implementation.

Any justification provided by the beneficiary needs to be pre-endorsed by the GSA and subcontracting shall require GSA’s approval which may be considered granted in cases where the subcontracting is already fully described in the proposal so accepted by the GSA, given that it will then be implemented accordingly and fulfilling the eligibility criteria specified in the signed grant agreement.

 

The tasks concerned must be set out in the description of the action (i.e. form B1 and Annex I to the grant agreement) and the estimated costs of subcontracting must be clearly identifiable in the preliminary budget (Form C1). However, approval of subcontracting by GSA (whether at the time of the evaluation of proposal or later during implementation of the action) does not automatically mean that the related costs will be considered eligible and reimbursed. The costs will need to comply with the eligibility criteria set up in the grant agreement in order for them to be reimbursed.

Any modifications on an ad hoc basis while the action is under way must be presented for ex-ante approval of the GSA and for major items will require an amendment to the grant agreement otherwise will not be reimbursed.

It is not necessary to have already selected subcontractors at the time the proposal is submitted. However, cost of subcontractors not selected in accordance with the rules referred to in this Section will not be eligible.

 

6. ADMISSIBILITY REQUIREMENTS

Applications must comply with the following conditions in order to be admissible:

• −  Applications must be sent no later than the deadline for submitting applications referred to in section 17,

• −  Applications must be submitted in writing, using the submission set described in section 16,

• −  Applications must be drafted in one of the EU official languages with a preference to English. For

  further information please refer to Section 17 below,

• −  Applications must respect the maximum rate for EU co-financing,

• −  Applications must respect the maximum budget allocated for EU financing5.

 

In this context, any project directly or indirectly contrary to EU policy or against public health, human rights or against citizen’s security will be rejected.

 

7. ELIGIBILITY CRITERIA

APPLICATIONS MUST COMPLY WITH ALL OF THE ELIGIBILITY CRITERIA SET OUT IN THIS SECTION.

7.1. Eligible applicants

To be eligible, applications must be submitted by:

Legal persons established6 in and/or natural person(s) being citizen of one of the following countries:

 EU Member State;
 Norway, Switzerland.

For British applicants: Please be aware that eligibility criteria must be complied with for the entire duration of the grant. If the United Kingdom withdraws from the EU during the grant period without concluding an agreement with the EU ensuring in particular that British applicants continue to be eligible, you will cease to receive EU funding (while continuing, where possible, to participate) or be required to leave the project on

 

the basis of Article II.17.3.1(a) of the multi-beneficiary grant agreement or Article II.17.2.1(a) of the mono- beneficiary grant agreement.

7.2. Structure of the consortium (multi-beneficiaries)

In the case of multiple-applicants, the coordinator will submit the proposal on behalf of the consortium. It shall be the intermediary for all communication between the co-applicants and the GSA and responsible for supplying all documents and information to the GSA in due time upon request.

The proposal consequently must be submitted by a consortium composed of at least two (2) entities out of which:

• ●  the coordinator shall be a legal person;

• ●  the co-applicant(s) can be either legal and/or natural person(s).

For the sake of clarity, the term “applicant”, referred to in this call, shall encompass co-applicants and coordinator as appropriate.

All co-applicants in the same consortium shall agree upon appropriate arrangements (internal cooperation agreements) among themselves for the proper performance of the action.

The grant agreement shall be signed by coordinator of the successful consortium; provided that a mandate (Annex IV of the grant agreement) has been provided to it by the other co-applicants. A copy of this mandate shall be provided to the GSA.

Legal persons having a legal or capital link with applicants, which is neither limited to the action nor established for the sole purpose of its implementation, may take part in the action as affiliated entities (see ref. to section 5.5), and may declare eligible costs. For that purpose, applicants shall identify such affiliated entities in the application form.

7.3. Supporting documents proving compliance with the eligibility criteria (both for mono- and multi-beneficiaries)

The applicant(s) and any affiliated entities shall provide the following supporting documents as further detailed below to establish their eligibility:

➢ All the applicants and any affiliated entities (see ref. to section 5.5) shall provide the following supporting documents to establish their eligibility:

• ▪  A duly filled and signed Legal Entity Form (LEF) accompanied by the relevant evidence (see below) of the applicant's legal status has to be provided at the stage of submission. A specific form in all official languages of the EU is available at the following internet page (use of the English forms is preferred): http://ec.europa.eu/budget/contracts_grants/info_contracts/legal_entities/legal_entities_en.cfm

▪  In addition:

• − private legal person(s) : extract from the official journal, copy of articles of association, extract of trade or association register OR a copy of the certificate of liability to VAT (if, as in certain countries, the trade register number and VAT number are identical, only one of these documents is required);

• −  public legal person(s) : a copy of the resolution, law, decree or decision establishing the public company, or as an alternative, any other official document establishing the public legal person by the national authorities may be submitted;

• −  natural person(s) : legible photocopy of identity card and/or passport OR an official VAT document (if applicable).

  For the Consortium: In addition to the above supporting documents, each applicant shall further submit letters confirming their participation to the project, their role in the consortium (coordinator or co- applicant) and the main task to be performed.

   The single applicant and the coordinator7, who will be receiving payments, shall provide:

▪ A duly filled Financial Identification Form (FIF),
which can be downloaded from the following website: http://ec.europa.eu/budget/contracts_grants/info_contracts/financial_id/financial_id_en.cfm

It must be duly filled in and signed, and if applicable be accompanied by the relevant bank statement.

IMPORTANT NOTE (1): Applicant(s) may participate in multiple applicant consortia, if the actions covered in the respective Technical Proposals (B1 form) are different from each other in order to comply with the principle of non-cumulative financing and award.

 

8. EXCLUSION CRITERIA

APPLICATIONS MUST COMPLY WITH ALL OF THE EXCLUSION CRITERIA SET OUT IN THIS SECTION.

Paragraphs 1 to 4, 6 and 7, except point (b) of the first subparagraph and the second subparagraph of that paragraph, paragraphs 8, 9, 11 and 13 to 17 of Article 106 of the Financial Regulation shall apply to grant applicants and beneficiaries. Applicants shall declare whether they are in one of the situations referred to in Article 106(1) and, where applicable, whether they have taken remedial measures as referred to in point (a) of Article 106(7).

8.1. Exclusion from the participation
Exclusion criteria are specified in the standard Declaration of Honour (A5 Form) of this call. The same exclusion criteria apply to all affiliated entities (see ref. to section 5.5).
8.2. Exclusion from award

Applicants will not be granted EU funds if, in the course of the grant award procedure, they:

• −  are in an exclusion situations established in the A5 form;

• −  have misrepresented the information required by the GSA as a condition of participation in the grant award procedure or fail to supply this information upon request by GSA;

• − were previously involved in the preparation of the call for proposal documents where this entails a distortion of competition that cannot be remedied otherwise.

 

The same exclusion criteria apply to affiliated entities.

Administrative and financial penalties may be imposed on applicants that are guilty of misrepresentation.

8.3. Supporting documents proving compliance with exclusion criteria

All applicants and any affiliated entities (see ref. to section 5.5) must sign and submit a Declaration of Honour (A5 Form).

Please note that according to this A5 Form, the successful applicants – subject to the outcome of the risk assessment8 performed by GSA on a case by case basis – may be required to send a number of supporting documents related to aspects of the Declaration of Honour before the respective grant agreement can be signed. Collecting these supporting documents may take some time and applicants shall ensure their timely availability for performing this requirement accordingly. Applicants shall approach the GSA in due time in case they are of the opinion that certain points of the declaration are not applicable to them (e.g. due to their legal structure).

 

9. SELECTION CRITERIA

APPLICATIONS MUST COMPLY WITH ALL OF THE SELECTION CRITERIA SET OUT IN THIS SECTION.

9.1. Financial capacity

Applicants must have stable and sufficient sources of funding to maintain their activity throughout the period during which the action is being carried out. The applicants' financial capacity will be assessed on the basis of the following supporting documents to be submitted with the application by each applicant and affiliated entity (thresholds applying by applicants):

a) Low value grants (≤ EUR 60 000): - a declaration on their honour.

b) Grants ≥ EUR 60 000:
- a declaration on their honour and,
- the table provided for in the application form (Annex B3), filled in with the relevant statutory accounting figures, in order to calculate the ratios as detailed in the form. For newly created entities, the business plan might replace the above documents.

c) Grants for an action ≥ EUR 750 000, in addition:
- an audit report produced by an approved external auditor certifying the accounts for the last

financial year available
In the event of an application grouping several applicants (consortium), the above thresholds apply by applicants.

On the basis of the documents submitted, if GSA considers that financial capacity is not satisfactory, it may: - request further information;

 

 

• -  propose a grant agreement without pre-financing;

• -  propose a grant agreement with a pre-financing paid in instalments;

• -  propose a grant agreement with a pre-financing covered by a bank guarantee;

• -  reject the application.
  The verification of the financial capacity shall not apply to public bodies, international organisations or no- profit organisations.

9.2. Operational capacity (B2 Form)

Applicants must show they have the operational (technical and management) capacity to complete the activities to be supported by this Call for Proposal and must demonstrate their capacity to manage the activities corresponding to the size of the project for which the grant is requested.

In particular:

• -  The team responsible for the activities must have an eminent technical competence,

• -  Applicants must have a high degree of specialisation in areas relevant for the activities subject to the proposal,

• -  Applicants must prove that they are able to develop the necessary components of MEOSAR Beacons;

• -  Applicants must prove that they have at their disposal technical infrastructures (relevant design and validation tools and/or hardware/software tools) necessary to perform the implementation.

  In this respect, applicants have to submit in B2 Form, the following elements:

• -  description of the profile of the individuals9 primarily responsible for managing and implementing the activities;

• -  a description of the technical equipment, tools or facilities at the disposal of the applicant;

• -  a description of the role of each applicant (coordinator, co-applicants and affiliated entities) in the organisational structure in general and regarding the performance of activities subject to grant agreement.

In the case of affiliated entities (see ref. to section 5.5) taking part in the project, the above requirements apply to each affiliated entity.

 

(TRUNCATED -- please see the public link the full proposal)

Public link:   Only for registered users