Development of an Advanced RAIM
multi-constellation receiver
Katerina Strelcova, Aviation Market Development Innovation Officer
Vincenza de Tommaso, Financial Officer
Alina Hriscu, Market Development Officer
Fundamental Elements Webinar, 29th March 2017
2
• Participants’ microphones are muted. To
avoid any echo, please switch off your
microphone.
• Make sure your speakers or headphones
are switched on, and turn up the
volume.
• To interact you can use the common chat
room. Questions to individual
participants will not be answered.
• Your questions will appear anonymously
to the other participants
Before we start – way of working (1/2)
• Questions are collected and addressed at the end of
the session, if time allows it.
• All questions and answers will be published on the
GSA website in order to guarantee the equal
treatment of tenderers/applicants.
• Slides and clarifications will be available in due course
online after this webinar.
• After the information session, you will receive a short
satisfaction questionnaire, please fill it in.
3
Before we start – way of working (2/2)
 CALL BACKGROUND
 TECHNICAL SCOPE
 ELIGIBLE PARTICIPANTS
 HOW TO PREPARE YOUR PROPOSAL
 GRANT AGREEMENT
 Q&A TIME
Agenda
4
• Specific ARAIM Technical Sub-Group (TSG) established in
2010
‒ under the U.S.-EU Agreement on GPS-Galileo Cooperation signed
in 2004 on the cooperation activities between the USA and the
EU in the field of satellite navigation
‒ aims to develop an advanced integrity concept in civil aviation
‒ to develop a solution to ensure navigation integrity for en-route
flight, terminal, and approach operations, which should support
lateral and vertical guidance down to a Decision Height/Altitude
(DH/DA) of 200 feet
‒ produced 3 reports publicly available
‒ defined roadmap
EU-US ARAIM Technical Sub-Group
5
• Advanced Receiver Autonomous Integrity Monitoring is a concept
with the intention to provide a global integrity service based on
multiple satellite constellation
• The ARAIM concept is based on three possible architectures
enabling different level of performance:
‒ Horizontal ARAIM, to support horizontal navigation based on an occasional
Integrity Support Message (ISM) updates
‒ Offline ARAIM, to support horizontal and vertical navigation based on a
monthly Integrity Support Message (ISM) updates
‒ Online ARAIM, to support horizontal and vertical navigation based on an
Integrity Support Message (ISM) frequently updates (e.g. every 12 minutes)
ARAIM
6
OBJECTIVES OF THE CALL
7
• To develop, test and assess the performance of an
ARAIM receiver’s prototype, following the guidelines
defined by the ARAIM TSG (Technical Sub Group).
• To characterise, consolidate and validate the local
effects of the threat model as specified by the ARAIM
TSG.
• To contribute to the standardisation activities on
ARAIM.
Objective of the Call
8
Expected project flow
9
• Aims to define the requirements and implementing
the ARAIM receiver’s first version prototype
1) Define all receiver’s requirements (functional,
safety, performance)
2) Design and develop the prototype receiver using
the most updated ARAIM reference algorithm
available
3) Consolidate a performance validation plan
TASK 1
10
• Aims to assess the achievable performance of the
implemented receiver’s prototype
• Testing execution:
1) in a simulated environment (with support of JRC)
2) using real GNSS signal in a number of representative scenarios (real
signal validation)
• ARAIM receiver performance to be assessed against SoL
requirements
TASK 2
11
NOTE: Tests to be conducted in coordination with other relevant projects
• R&D FOR ADVANCED RECEIVER AUTONOMOUS INTEGRITY MONITORING:
ARAIM DEMONSTRATOR
‒ ARAIM Demonstrator development including tests with real Galileo Signal In Space (SIS)
• AVIATION STANDARDISATION FOR MULTICONSTELLATION (ATLAS)
‒ draft technical standards for implementation of multiconstellation/dual frequency, next
generation SBAS and Advanced RAIM techniques, as aviation receiver standards are
currently published for GPS stand-alone and GPS/SBAS equipment
• AVIATION DFMC SBAS RECEIVER PROTOTYPE
‒ design, develop and test a prototype of the DFMC SBAS user terminal for the aviation SoL
service, augmenting GPS and Galileo capabilities including Horizontal-ARAIM and RAIM
Other initiatives related to ARAIM
12
Applicants shall propose a project plan aiming at maximising the effectiveness of the project
results allowing for the interaction with the above as minimum or any other relevant projects.
TASK 3
13
• Transversal activity
1) Disseminate of the project results
- including at least 2 technical papers to international conferences
2) Contribute to standardisation activities
- if the results deemed satisfactory and meaningful as an input
3) Provide technical support to GSA/EC
Minimum list of deliverables
14
Work plan
ARAIM receiver
Requirements
Justification File
Safety assessment
document
Preliminary
architecture of the
ARAIM receiver
Detailed architecture
and Design Justification
File of the ARAIM
receiver
Error model –
characterisation and
validation
ARAIM prototype
validation plan against
SoL operations
requirements
Validation report
Testing tool
specifications
Testing tool validation
plan and report
Dissemination Plan
Report on the
Demonstration
activities
Roadmap for
operational
implementation (H-
ARAIM, V-ARAIM)
Dissemination
documents and multi-
media
ARAIM receiver
prototypes
ARAIM receiver
requirements
document
Demonstration kit
Report on the
Demonstration of the
ARAIM receiver
prototypes
Demonstration training
material
Report about the status
of implementation of
the dissemination plan
only in case the demo is proposed by the applicant
DEL v0 ~ preliminary deliverable to be included in the proposal
DEL v1 ~ as defined in the Call text
Award criteria
15
Relevance, credibility of the proposed
approach and innovation of the
solution proposed
(max 50)
Impact in terms of
economic and public
benefits
(max 20)
Coherence and
effectiveness of the work
plan, appropriate task
and resources allocation
(max 30)
 Relevance and quality of
 the proposed validation approach
(Preliminary DEL 8)
 Requirements identification,
development and testing of
developed receiver
 the methodology to characterize the
ARAIM errors (Preliminary DEL 7)
 Overall proposal quality in term of
deliverables, their content and structure
 The main key stakeholders involvement
 Roadmap for operational
implementation of H-ARAIM
and V-ARAIM (Preliminary
DEL 14)
 Maximisation of the benefits
to citizens by the adoption
of the results in market
 Representation of
companies with their
headquarters geographically
based in EU member State ,
Norway or Switzerland
 Consistency of the work
plan
 Appropriate management
structure, procedures
 Coherent activity
definition, schedule, effort
and cost
 Appropriate task and
resources distribution
 Credible and effective
dissemination plan
(Preliminary DEL 12)
If a total score lower than 60 points or a score lower than 60% for any of the above three criteria is obtained, the proposal
Call timeline (indicative)
16
Stage Deadline
Publication of the call 28 February 2017
Deadline for request for clarifications 26 April 2017
Publication of the clarifications 3 May 2017
Deadline for submission of applications 19 May 2017
Evaluation period June - July 2017
Information to applicants on the outcome of the
evaluation
August - September 2017
Signature of the Grant Agreement October 2017
• Maximum total budget allocated to the call: EUR 2.500.000
• Maximum number of projects: 2
• Indicative EU financing per project up to: EUR 1.250.000
• Maximum EU financing rate of eligible costs: 70%
• Maximum duration of the action: 2 years
Budget allocation and duration
17
ELIGIBLE PARTICIPANTS
18
Participation conditions
19
• Applications by legal persons established1 in and/or natural person(s) being nationals of
any of the EU Member States, Switzerland or Norway.
1 Legal persons are considered to be established in the EU when they are formed in
accordance with the law of an EU Member State, Norway or Switzerland, and have
their central administration, registered office or principal place of business in an EU
Member State, Norway or Switzerland
• Applicants: active in the development and/or integration and/or performance
assessment of GNSS receivers and/or development and validation of safety-critical
software, and/or expert in the field of GNSS research and development (R&D), and/or
expert in the assessment or development of aviation standards and/or active in the
dissemination of the project’s results;
Eligible applicants
Only applicant consortia shall be eligible to participate in this call –
proposals by single legal or natural person shall not be admissible.
HOW TO PREPARE YOUR PROPOSAL
20
 The Administrative package
 The Technical package
 The Financial package
Summary of the proposals
21
Summary of the proposals
22
FORM CONTENT CO-ORDINATOR CO-APPLICANT(S)
A1 PROPOSAL OVERVIEW X
A2 PROPOSAL SUMMARY X
A3 COORDINATOR PROFILE X
A4 CO-APPLICANT PROFILE X
A5 DECLARATION OF HONOUR X X
A6 FINANCIAL CAPACITY X X
B1 TECHNICAL PROPOSAL X
B2 OPERATIONAL CAPACITY X X
C1 PRELIMINARY BUDGET X X
ADMIN
PACKAGE
TECHNICAL
PACKAGE
FINANCIAL
PACKAGE
 Admin package:
WHO does WHAT?
23
FORM CONTENT Co-ordinator Co-applicant(s)
Affiliated
entity
A1
PROPOSAL
OVERVIEW
X
A2
PROPOSAL
SUMMARY
X
A3
COORDINATOR
PROFILE
X
A4
CO-APPLICANT
PROFILE
X
A5
DECLARATION OF
HONOUR
X X X
A6 FINANCIAL CAPACITY X X X
24
Admin package – overview of forms
Cover page
It serves 2 purposes:
COVER PAGE (TO BE FILLED BY THE COORDINATOR + GSA)
 Checklist for the applicants: list of the submission set +
number of docs to be submitted
 Basic information on the Proposal for GSA: project
acronym and consortium composition + receipt of the
documents.
25
Admin package – overview of forms
Form A1 & Form A2
 Contact details: Name/Surname, Organisation, ..
 Proposal Abstract: high level description of the proposed technical solution
 About the participants: name, role in the project and represented country
FORM A1. PROPOSAL OVERVIEW (TO BE FILLED BY THE COORDINATOR)
FORM A2. PROPOSAL SUMMARY (TO BE FILLED BY THE COORDINATOR)
 Objectives of the proposal: target of the proposal, including value proposition and
benefit for the users
 Description of the work: high level project’s workflow
 Milestone and Expected results
26
Admin package – overview of forms
Form A3 & Form A4
FORM A3. COORDINATOR PROFILE
(TO BE SUBMITTED BY THE COORDINATOR WITH: LEGAL ENTITY AND FINANCIAL IDENTIFICATION FORMS)
 Legal Information: LEF (Legal Entity Form: private or public company, registration info)
 Financial Identification: (FIF) banking details and account holder’s info
 Power of attorney: to commit the company/organisation
 Information on co-financing: how the applicant would do it? under which form?
 Previous EU contracts/grants: to check the no-double payment principle.
 Stamp: in UK it’s not common however for admin purposes EC needs it!
FORM A4. CO-APPLICANT PROFILE
(TO BE FILLED BY THE CO-APPLICANTS WITH: LEGAL ENTITY FORM)
 Same as for Coordinator: to be filled by the co-applicant.
27
Admin package – overview of forms
Form A5 & A6
FORM A5. DECLARATION OF HONOUR
(TO BE SUBMITTED BY ALL APPLICANTS – INCLUDING AFFILIATED ENTITIES)
 It serves to check the exclusion and selection criteria
 Generic text used by EU.
 (The template was made after the amendment of the EU Financial Regulations as of 1 Jan
2016.)
 If requested consider to start early enough collecting all the evidences; since might be
time consuming
FORM A6. FINANCIAL CAPACITY
(TO BE SUBMITTED BY ALL APPLICANTS – INCLUDING AFFILIATED ENTITIES)
 Technical package:
WHO does WHAT?
28
FORM CONTENT Co-ordinator Co-applicant(s)
Affiliated
entity
B1
TECHNICAL
PROPOSAL
X
B2
OPERATIONAL
CAPACITY
X X X
29
Technical package
• Every proposal shall be assessed against the criteria
set out in the relevant Call for Proposal.
• In particular, for the technical package:
The Technical proposal (B1 Form) shall be assessed against
the AWARD criteria (CfP sect. 9)
The Operational capacity (B2 Form) shall be assessed against
the SELECTION criteria (CfP sect. 8.2)
30
Technical package – overview of forms
Form B1
The co-ordinator, on behalf of the consortium, shall
submit the TECHNICAL PROPOSAL.
1. CONCEPT and APPROACH (max. 30 pages)
2. EXPECTED IMPACT (max. 10 pages)
3. IMPLEMENTATION (max. 20 pages)
4. TECHNICAL ANNEXES
1. This section shall contain, as minimum:
 Description of the proposed technical solution and its compliance with the
CfP’s objectives
 Technology involved (focusing on innovation elements), E-GNSS
differentiators, etc.
 Description of the applied methodologies which shall be used in the
implementation of the action
 The feasibility of the proposal targeting market implementation
 Considerations about the engagement of the key stakeholders (e.g. chipset
manufacturer, system integrator, service provider, etc.)
31
Technical package – overview of forms
Form B1: Concept and approach
32
Technical package – overview of forms
Form B1: Expected impact
2. This section shall at least address the following topics:
 Which benefits to the user will derive from the implementation of the
project? Which additional applications shall be enabled?
 Elaboration of a Preliminary Business Plan, describing the strategy to
exploit the results.
 Elaboration of a Preliminary Dissemination Plan, establishing the
measures to disseminate the achievements of the project among
relevant stakeholders in the appropriate phases of the project
33
Technical package – overview of forms
Form B1: Implementation (1/2)
3. Structured section guiding the applicant through the following
points:
 Work Plan definition
 Work Packages: description, effort, resp., objectives, etc.
 WP schedule: Gantt chart, or similar
 WP inter-dependencies: Pert chart, or similar
 List of Deliverables (e.g. specification, report, demo kit, etc.)
 Project management
 Milestones, and relevant decision making
 Preliminary Risk register
34
Technical package – overview of forms
Form B1: Implementation (2/2)
3. Structured section guiding the applicant through the following
points:
 Consortium as a whole:
 Partners complementarity
 Tasks allocation
 Effectiveness in the project execution and to target
commercialisation
 Project’s Resources:
 Planned staff effort
 Other Direct Costs
 Subcontracting
 Budget overview
35
Technical package – overview of forms
Form B1: Technical annexes
4. Table to be filled out with the following information:
 Partners name (Organisation/Company)
 Company category (e.g. Research institute, chipset manufacturer, other)
 Country
Legal person: origin meaning “established”: having a registered office OR
central administration OR principal place of business in one of those
countries.
Natural Person: citizenship
36
Technical package – overview of forms
Form B1: Operational capacity
Every applicant (coordinator and co-applicants), shall
submit the OPERATIONAL CAPACITY Form.
Objective: to demonstrate compliance with SELECTION criteria set out in the
CfP
Ref. CfP section 8.2 – “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.”
37
FORM CONTENT CO-ORDINATOR CO-APPLICANT(S)
A1 PROPOSAL OVERVIEW X
A2 PROPOSAL SUMMARY X
A3 COORDINATOR PROFILE X
A4 CO-APPLICANT PROFILE X
A5 DECLARATION OF HONOUR X X
A6 FINANCIAL CAPACITY X X
B1 TECHNICAL PROPOSAL X
B2 OPERATIONAL CAPACITY X X
C1 PRELIMINARY BUDGET X X
ADMIN
PACKAGE
TECHNICAL
PACKAGE
FINANCIAL
PACKAGE
 Financial package:
WHO does WHAT?
• Filled in with figures from your annual (audited)
accounts
• GSA calculates ratios (e.g. profitability, indebtedness,
financial independence)
• Used to assess your financial viability
Not applicable to public bodies and international
organisations
Financial package – overview of forms
Form A6: Financial capacity (1/2)
38
If outcome of the check is not satisfactory and in any other case GSA can:
• 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 lower percentage of a pre-financing;
• propose a grant agreement with a pre-financing covered by a bank
guarantee
• reject the application
39
Financial package – overview of forms
Form A6: Financial capacity (2/2)
Financial package – overview of forms
Form C1: Estimated budget
40
Project Name Participant Name
Project Acronym
Estimated eligible direct costs
Estimated eligible indirect
costs Total estimated eligible costs
Total requested GSAgrant
(EUR) (EUR) (EUR) (EUR)
A B C = A+B D = 70% x C
Direct eligible costs
(Numbering of categories as in "Eligible Costs for
the grants" section 12.2 of the Call for Proposals -
apply the rules detailed thereunder)
declared on the basis of flat rate of 7%
of 1. + 2. without costs of
subcontractors, costs of third parties
not working on beneficiary premises,
and cost of financial support to 3rd
parties
Total requested GSA grant at the
maximum reimbursment rate of 70%of
total costs
1.1 Personnel under direct empl. contract 0.00 € 0.00 € 0.00 € 0.00 €
1.2 Personnel under other than under empl.
contract (in-house consultants)
0.00 € 0.00 € 0.00 € 0.00 €
Sub-total for cost category 1 0.00 € 0.00 € 0.00 € 0.00 €
2.1 Travel costs 0.00 € 0.00 € 0.00 € 0.00 €
2.2 Costs for equipment and other assets
procured for the action
2.2 a) Costs for equipment and other assets
procured for the action: Full purchase costs
2.2 b) Costs for equipment and other assets
procured for the action: Depreciation costs
0.00 € 0.00 € 0.00 € 0.00 €
2.3 Costs for equipment or other assets not
procured but used for the action (depreciation
costs)
0.00 € 0.00 € 0.00 € 0.00 €
2.4 Costs for rental or lease of equipment or
other assets only to the portion of use and
limited to the duration of the action
0.00 € 0.00 € 0.00 € 0.00 €
2.5 Costs for use of technical facilities or
laboratories
0.00 € 0.00 € 0.00 € 0.00 €
2.6 Costs for consumables and supplies 0.00 € 0.00 € 0.00 € 0.00 €
2.7 Costs arising directly from requirements
imposed by the grant agreement
0.00 € 0.00 € 0.00 € 0.00 €
2.8 Costs entailed by subcontracts as
described in the proposal
0.00 € Not applicable 0.00 € 0.00 €
2.9 costs of financial support to third parties
2.10 Duties, taxes and charges paid by the
beneficiary
0.00 € 0.00 € 0.00 € 0.00 €
Sub-total for cost category 2 0.00 0.00 € 0.00 € 0.00 €
Total direct eligible costs 0.00 €
Total indirect eligible costs 0.00 €
Total eligible costs 0.00 €
5. Total EU contribution 0.00 €
Not applicable in this call for proposals
ESTIMATED BUDGET
Not applicable in this call for proposals
Estimated eligible costs of the action and GSA contribution (Table 1)
1. PERSONNEL COSTS
2. OTHER DIRECT COSTS
• During evaluation it will be checked:
‒ Staff effort – in relation to estimated budget for
personnel
‒ Description of other direct costs
‒ List of subcontracts
‒ Cumulative budget overview
Financial package – overview of forms
Form B1: Technical proposal
41
The amounts
should fit with
amounts in C1
Form
• 3 payments in total:
‒ Pre-financing 30%
‒ Interim payment up to 40%
‒ Final payment (30-70%)
Payment scheme
42
• When the tasks in B1 cannot be done by the consortium
• Principles:
‒ Best value for money or the lowest price
‒ No Conflict of Interest
‒ May only cover a limited part of the action and can not cover the core activities
‒ Necessary for implementation
‒ Stated in the proposal and in estimated budget
Subcontracting among beneficiaries is not possible!
Subcontracting
43
GRANT AGREEMENT
44
Draft Grant Agreement
45
• NOT part of the submitted proposal
• Please read it before submitting a proposal!
• It contains important elements on payments,
reporting, IPR etc.
• GSA: Legal and Procurement Department
• E-mail address: gnss.grants@gsa.europa.eu
• Office address: GSA, Janovského 438/2, 170 00, Prague 7, Czech
Republic
Contact coordinates for the call
46
Submit requests for clarifications by: 26 April 2017
Submit proposals by: 19 May 2017
Please refer in the subject to the relevant reference number of the Call
GSA/GRANT/01/2017

Development of an Advanced RAIM multi-constellation receiver

  • 1.
    Development of anAdvanced RAIM multi-constellation receiver Katerina Strelcova, Aviation Market Development Innovation Officer Vincenza de Tommaso, Financial Officer Alina Hriscu, Market Development Officer Fundamental Elements Webinar, 29th March 2017
  • 2.
    2 • Participants’ microphonesare muted. To avoid any echo, please switch off your microphone. • Make sure your speakers or headphones are switched on, and turn up the volume. • To interact you can use the common chat room. Questions to individual participants will not be answered. • Your questions will appear anonymously to the other participants Before we start – way of working (1/2)
  • 3.
    • Questions arecollected and addressed at the end of the session, if time allows it. • All questions and answers will be published on the GSA website in order to guarantee the equal treatment of tenderers/applicants. • Slides and clarifications will be available in due course online after this webinar. • After the information session, you will receive a short satisfaction questionnaire, please fill it in. 3 Before we start – way of working (2/2)
  • 4.
     CALL BACKGROUND TECHNICAL SCOPE  ELIGIBLE PARTICIPANTS  HOW TO PREPARE YOUR PROPOSAL  GRANT AGREEMENT  Q&A TIME Agenda 4
  • 5.
    • Specific ARAIMTechnical Sub-Group (TSG) established in 2010 ‒ under the U.S.-EU Agreement on GPS-Galileo Cooperation signed in 2004 on the cooperation activities between the USA and the EU in the field of satellite navigation ‒ aims to develop an advanced integrity concept in civil aviation ‒ to develop a solution to ensure navigation integrity for en-route flight, terminal, and approach operations, which should support lateral and vertical guidance down to a Decision Height/Altitude (DH/DA) of 200 feet ‒ produced 3 reports publicly available ‒ defined roadmap EU-US ARAIM Technical Sub-Group 5
  • 6.
    • Advanced ReceiverAutonomous Integrity Monitoring is a concept with the intention to provide a global integrity service based on multiple satellite constellation • The ARAIM concept is based on three possible architectures enabling different level of performance: ‒ Horizontal ARAIM, to support horizontal navigation based on an occasional Integrity Support Message (ISM) updates ‒ Offline ARAIM, to support horizontal and vertical navigation based on a monthly Integrity Support Message (ISM) updates ‒ Online ARAIM, to support horizontal and vertical navigation based on an Integrity Support Message (ISM) frequently updates (e.g. every 12 minutes) ARAIM 6
  • 7.
  • 8.
    • To develop,test and assess the performance of an ARAIM receiver’s prototype, following the guidelines defined by the ARAIM TSG (Technical Sub Group). • To characterise, consolidate and validate the local effects of the threat model as specified by the ARAIM TSG. • To contribute to the standardisation activities on ARAIM. Objective of the Call 8
  • 9.
  • 10.
    • Aims todefine the requirements and implementing the ARAIM receiver’s first version prototype 1) Define all receiver’s requirements (functional, safety, performance) 2) Design and develop the prototype receiver using the most updated ARAIM reference algorithm available 3) Consolidate a performance validation plan TASK 1 10
  • 11.
    • Aims toassess the achievable performance of the implemented receiver’s prototype • Testing execution: 1) in a simulated environment (with support of JRC) 2) using real GNSS signal in a number of representative scenarios (real signal validation) • ARAIM receiver performance to be assessed against SoL requirements TASK 2 11 NOTE: Tests to be conducted in coordination with other relevant projects
  • 12.
    • R&D FORADVANCED RECEIVER AUTONOMOUS INTEGRITY MONITORING: ARAIM DEMONSTRATOR ‒ ARAIM Demonstrator development including tests with real Galileo Signal In Space (SIS) • AVIATION STANDARDISATION FOR MULTICONSTELLATION (ATLAS) ‒ draft technical standards for implementation of multiconstellation/dual frequency, next generation SBAS and Advanced RAIM techniques, as aviation receiver standards are currently published for GPS stand-alone and GPS/SBAS equipment • AVIATION DFMC SBAS RECEIVER PROTOTYPE ‒ design, develop and test a prototype of the DFMC SBAS user terminal for the aviation SoL service, augmenting GPS and Galileo capabilities including Horizontal-ARAIM and RAIM Other initiatives related to ARAIM 12 Applicants shall propose a project plan aiming at maximising the effectiveness of the project results allowing for the interaction with the above as minimum or any other relevant projects.
  • 13.
    TASK 3 13 • Transversalactivity 1) Disseminate of the project results - including at least 2 technical papers to international conferences 2) Contribute to standardisation activities - if the results deemed satisfactory and meaningful as an input 3) Provide technical support to GSA/EC
  • 14.
    Minimum list ofdeliverables 14 Work plan ARAIM receiver Requirements Justification File Safety assessment document Preliminary architecture of the ARAIM receiver Detailed architecture and Design Justification File of the ARAIM receiver Error model – characterisation and validation ARAIM prototype validation plan against SoL operations requirements Validation report Testing tool specifications Testing tool validation plan and report Dissemination Plan Report on the Demonstration activities Roadmap for operational implementation (H- ARAIM, V-ARAIM) Dissemination documents and multi- media ARAIM receiver prototypes ARAIM receiver requirements document Demonstration kit Report on the Demonstration of the ARAIM receiver prototypes Demonstration training material Report about the status of implementation of the dissemination plan only in case the demo is proposed by the applicant DEL v0 ~ preliminary deliverable to be included in the proposal DEL v1 ~ as defined in the Call text
  • 15.
    Award criteria 15 Relevance, credibilityof the proposed approach and innovation of the solution proposed (max 50) Impact in terms of economic and public benefits (max 20) Coherence and effectiveness of the work plan, appropriate task and resources allocation (max 30)  Relevance and quality of  the proposed validation approach (Preliminary DEL 8)  Requirements identification, development and testing of developed receiver  the methodology to characterize the ARAIM errors (Preliminary DEL 7)  Overall proposal quality in term of deliverables, their content and structure  The main key stakeholders involvement  Roadmap for operational implementation of H-ARAIM and V-ARAIM (Preliminary DEL 14)  Maximisation of the benefits to citizens by the adoption of the results in market  Representation of companies with their headquarters geographically based in EU member State , Norway or Switzerland  Consistency of the work plan  Appropriate management structure, procedures  Coherent activity definition, schedule, effort and cost  Appropriate task and resources distribution  Credible and effective dissemination plan (Preliminary DEL 12) If a total score lower than 60 points or a score lower than 60% for any of the above three criteria is obtained, the proposal
  • 16.
    Call timeline (indicative) 16 StageDeadline Publication of the call 28 February 2017 Deadline for request for clarifications 26 April 2017 Publication of the clarifications 3 May 2017 Deadline for submission of applications 19 May 2017 Evaluation period June - July 2017 Information to applicants on the outcome of the evaluation August - September 2017 Signature of the Grant Agreement October 2017
  • 17.
    • Maximum totalbudget allocated to the call: EUR 2.500.000 • Maximum number of projects: 2 • Indicative EU financing per project up to: EUR 1.250.000 • Maximum EU financing rate of eligible costs: 70% • Maximum duration of the action: 2 years Budget allocation and duration 17
  • 18.
  • 19.
    Participation conditions 19 • Applicationsby legal persons established1 in and/or natural person(s) being nationals of any of the EU Member States, Switzerland or Norway. 1 Legal persons are considered to be established in the EU when they are formed in accordance with the law of an EU Member State, Norway or Switzerland, and have their central administration, registered office or principal place of business in an EU Member State, Norway or Switzerland • Applicants: active in the development and/or integration and/or performance assessment of GNSS receivers and/or development and validation of safety-critical software, and/or expert in the field of GNSS research and development (R&D), and/or expert in the assessment or development of aviation standards and/or active in the dissemination of the project’s results; Eligible applicants Only applicant consortia shall be eligible to participate in this call – proposals by single legal or natural person shall not be admissible.
  • 20.
    HOW TO PREPAREYOUR PROPOSAL 20
  • 21.
     The Administrativepackage  The Technical package  The Financial package Summary of the proposals 21
  • 22.
    Summary of theproposals 22 FORM CONTENT CO-ORDINATOR CO-APPLICANT(S) A1 PROPOSAL OVERVIEW X A2 PROPOSAL SUMMARY X A3 COORDINATOR PROFILE X A4 CO-APPLICANT PROFILE X A5 DECLARATION OF HONOUR X X A6 FINANCIAL CAPACITY X X B1 TECHNICAL PROPOSAL X B2 OPERATIONAL CAPACITY X X C1 PRELIMINARY BUDGET X X ADMIN PACKAGE TECHNICAL PACKAGE FINANCIAL PACKAGE
  • 23.
     Admin package: WHOdoes WHAT? 23 FORM CONTENT Co-ordinator Co-applicant(s) Affiliated entity A1 PROPOSAL OVERVIEW X A2 PROPOSAL SUMMARY X A3 COORDINATOR PROFILE X A4 CO-APPLICANT PROFILE X A5 DECLARATION OF HONOUR X X X A6 FINANCIAL CAPACITY X X X
  • 24.
    24 Admin package –overview of forms Cover page It serves 2 purposes: COVER PAGE (TO BE FILLED BY THE COORDINATOR + GSA)  Checklist for the applicants: list of the submission set + number of docs to be submitted  Basic information on the Proposal for GSA: project acronym and consortium composition + receipt of the documents.
  • 25.
    25 Admin package –overview of forms Form A1 & Form A2  Contact details: Name/Surname, Organisation, ..  Proposal Abstract: high level description of the proposed technical solution  About the participants: name, role in the project and represented country FORM A1. PROPOSAL OVERVIEW (TO BE FILLED BY THE COORDINATOR) FORM A2. PROPOSAL SUMMARY (TO BE FILLED BY THE COORDINATOR)  Objectives of the proposal: target of the proposal, including value proposition and benefit for the users  Description of the work: high level project’s workflow  Milestone and Expected results
  • 26.
    26 Admin package –overview of forms Form A3 & Form A4 FORM A3. COORDINATOR PROFILE (TO BE SUBMITTED BY THE COORDINATOR WITH: LEGAL ENTITY AND FINANCIAL IDENTIFICATION FORMS)  Legal Information: LEF (Legal Entity Form: private or public company, registration info)  Financial Identification: (FIF) banking details and account holder’s info  Power of attorney: to commit the company/organisation  Information on co-financing: how the applicant would do it? under which form?  Previous EU contracts/grants: to check the no-double payment principle.  Stamp: in UK it’s not common however for admin purposes EC needs it! FORM A4. CO-APPLICANT PROFILE (TO BE FILLED BY THE CO-APPLICANTS WITH: LEGAL ENTITY FORM)  Same as for Coordinator: to be filled by the co-applicant.
  • 27.
    27 Admin package –overview of forms Form A5 & A6 FORM A5. DECLARATION OF HONOUR (TO BE SUBMITTED BY ALL APPLICANTS – INCLUDING AFFILIATED ENTITIES)  It serves to check the exclusion and selection criteria  Generic text used by EU.  (The template was made after the amendment of the EU Financial Regulations as of 1 Jan 2016.)  If requested consider to start early enough collecting all the evidences; since might be time consuming FORM A6. FINANCIAL CAPACITY (TO BE SUBMITTED BY ALL APPLICANTS – INCLUDING AFFILIATED ENTITIES)
  • 28.
     Technical package: WHOdoes WHAT? 28 FORM CONTENT Co-ordinator Co-applicant(s) Affiliated entity B1 TECHNICAL PROPOSAL X B2 OPERATIONAL CAPACITY X X X
  • 29.
    29 Technical package • Everyproposal shall be assessed against the criteria set out in the relevant Call for Proposal. • In particular, for the technical package: The Technical proposal (B1 Form) shall be assessed against the AWARD criteria (CfP sect. 9) The Operational capacity (B2 Form) shall be assessed against the SELECTION criteria (CfP sect. 8.2)
  • 30.
    30 Technical package –overview of forms Form B1 The co-ordinator, on behalf of the consortium, shall submit the TECHNICAL PROPOSAL. 1. CONCEPT and APPROACH (max. 30 pages) 2. EXPECTED IMPACT (max. 10 pages) 3. IMPLEMENTATION (max. 20 pages) 4. TECHNICAL ANNEXES
  • 31.
    1. This sectionshall contain, as minimum:  Description of the proposed technical solution and its compliance with the CfP’s objectives  Technology involved (focusing on innovation elements), E-GNSS differentiators, etc.  Description of the applied methodologies which shall be used in the implementation of the action  The feasibility of the proposal targeting market implementation  Considerations about the engagement of the key stakeholders (e.g. chipset manufacturer, system integrator, service provider, etc.) 31 Technical package – overview of forms Form B1: Concept and approach
  • 32.
    32 Technical package –overview of forms Form B1: Expected impact 2. This section shall at least address the following topics:  Which benefits to the user will derive from the implementation of the project? Which additional applications shall be enabled?  Elaboration of a Preliminary Business Plan, describing the strategy to exploit the results.  Elaboration of a Preliminary Dissemination Plan, establishing the measures to disseminate the achievements of the project among relevant stakeholders in the appropriate phases of the project
  • 33.
    33 Technical package –overview of forms Form B1: Implementation (1/2) 3. Structured section guiding the applicant through the following points:  Work Plan definition  Work Packages: description, effort, resp., objectives, etc.  WP schedule: Gantt chart, or similar  WP inter-dependencies: Pert chart, or similar  List of Deliverables (e.g. specification, report, demo kit, etc.)  Project management  Milestones, and relevant decision making  Preliminary Risk register
  • 34.
    34 Technical package –overview of forms Form B1: Implementation (2/2) 3. Structured section guiding the applicant through the following points:  Consortium as a whole:  Partners complementarity  Tasks allocation  Effectiveness in the project execution and to target commercialisation  Project’s Resources:  Planned staff effort  Other Direct Costs  Subcontracting  Budget overview
  • 35.
    35 Technical package –overview of forms Form B1: Technical annexes 4. Table to be filled out with the following information:  Partners name (Organisation/Company)  Company category (e.g. Research institute, chipset manufacturer, other)  Country Legal person: origin meaning “established”: having a registered office OR central administration OR principal place of business in one of those countries. Natural Person: citizenship
  • 36.
    36 Technical package –overview of forms Form B1: Operational capacity Every applicant (coordinator and co-applicants), shall submit the OPERATIONAL CAPACITY Form. Objective: to demonstrate compliance with SELECTION criteria set out in the CfP Ref. CfP section 8.2 – “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.”
  • 37.
    37 FORM CONTENT CO-ORDINATORCO-APPLICANT(S) A1 PROPOSAL OVERVIEW X A2 PROPOSAL SUMMARY X A3 COORDINATOR PROFILE X A4 CO-APPLICANT PROFILE X A5 DECLARATION OF HONOUR X X A6 FINANCIAL CAPACITY X X B1 TECHNICAL PROPOSAL X B2 OPERATIONAL CAPACITY X X C1 PRELIMINARY BUDGET X X ADMIN PACKAGE TECHNICAL PACKAGE FINANCIAL PACKAGE  Financial package: WHO does WHAT?
  • 38.
    • Filled inwith figures from your annual (audited) accounts • GSA calculates ratios (e.g. profitability, indebtedness, financial independence) • Used to assess your financial viability Not applicable to public bodies and international organisations Financial package – overview of forms Form A6: Financial capacity (1/2) 38
  • 39.
    If outcome ofthe check is not satisfactory and in any other case GSA can: • 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 lower percentage of a pre-financing; • propose a grant agreement with a pre-financing covered by a bank guarantee • reject the application 39 Financial package – overview of forms Form A6: Financial capacity (2/2)
  • 40.
    Financial package –overview of forms Form C1: Estimated budget 40 Project Name Participant Name Project Acronym Estimated eligible direct costs Estimated eligible indirect costs Total estimated eligible costs Total requested GSAgrant (EUR) (EUR) (EUR) (EUR) A B C = A+B D = 70% x C Direct eligible costs (Numbering of categories as in "Eligible Costs for the grants" section 12.2 of the Call for Proposals - apply the rules detailed thereunder) declared on the basis of flat rate of 7% of 1. + 2. without costs of subcontractors, costs of third parties not working on beneficiary premises, and cost of financial support to 3rd parties Total requested GSA grant at the maximum reimbursment rate of 70%of total costs 1.1 Personnel under direct empl. contract 0.00 € 0.00 € 0.00 € 0.00 € 1.2 Personnel under other than under empl. contract (in-house consultants) 0.00 € 0.00 € 0.00 € 0.00 € Sub-total for cost category 1 0.00 € 0.00 € 0.00 € 0.00 € 2.1 Travel costs 0.00 € 0.00 € 0.00 € 0.00 € 2.2 Costs for equipment and other assets procured for the action 2.2 a) Costs for equipment and other assets procured for the action: Full purchase costs 2.2 b) Costs for equipment and other assets procured for the action: Depreciation costs 0.00 € 0.00 € 0.00 € 0.00 € 2.3 Costs for equipment or other assets not procured but used for the action (depreciation costs) 0.00 € 0.00 € 0.00 € 0.00 € 2.4 Costs for rental or lease of equipment or other assets only to the portion of use and limited to the duration of the action 0.00 € 0.00 € 0.00 € 0.00 € 2.5 Costs for use of technical facilities or laboratories 0.00 € 0.00 € 0.00 € 0.00 € 2.6 Costs for consumables and supplies 0.00 € 0.00 € 0.00 € 0.00 € 2.7 Costs arising directly from requirements imposed by the grant agreement 0.00 € 0.00 € 0.00 € 0.00 € 2.8 Costs entailed by subcontracts as described in the proposal 0.00 € Not applicable 0.00 € 0.00 € 2.9 costs of financial support to third parties 2.10 Duties, taxes and charges paid by the beneficiary 0.00 € 0.00 € 0.00 € 0.00 € Sub-total for cost category 2 0.00 0.00 € 0.00 € 0.00 € Total direct eligible costs 0.00 € Total indirect eligible costs 0.00 € Total eligible costs 0.00 € 5. Total EU contribution 0.00 € Not applicable in this call for proposals ESTIMATED BUDGET Not applicable in this call for proposals Estimated eligible costs of the action and GSA contribution (Table 1) 1. PERSONNEL COSTS 2. OTHER DIRECT COSTS
  • 41.
    • During evaluationit will be checked: ‒ Staff effort – in relation to estimated budget for personnel ‒ Description of other direct costs ‒ List of subcontracts ‒ Cumulative budget overview Financial package – overview of forms Form B1: Technical proposal 41 The amounts should fit with amounts in C1 Form
  • 42.
    • 3 paymentsin total: ‒ Pre-financing 30% ‒ Interim payment up to 40% ‒ Final payment (30-70%) Payment scheme 42
  • 43.
    • When thetasks in B1 cannot be done by the consortium • Principles: ‒ Best value for money or the lowest price ‒ No Conflict of Interest ‒ May only cover a limited part of the action and can not cover the core activities ‒ Necessary for implementation ‒ Stated in the proposal and in estimated budget Subcontracting among beneficiaries is not possible! Subcontracting 43
  • 44.
  • 45.
    Draft Grant Agreement 45 •NOT part of the submitted proposal • Please read it before submitting a proposal! • It contains important elements on payments, reporting, IPR etc.
  • 46.
    • GSA: Legaland Procurement Department • E-mail address: gnss.grants@gsa.europa.eu • Office address: GSA, Janovského 438/2, 170 00, Prague 7, Czech Republic Contact coordinates for the call 46 Submit requests for clarifications by: 26 April 2017 Submit proposals by: 19 May 2017 Please refer in the subject to the relevant reference number of the Call GSA/GRANT/01/2017

Editor's Notes

  • #5 First I will give you a little bit of background….
  • #6 Good morning, let me welcome you at this seminar as a first speaker. My name is KS and I will introduce you one of the currently opened Call for proposal on Development of an Advanced RAIM multi-constellation receiver. As the integrity is one of the essential qualities of service to be provided to the users of Safety of Life applications, Cooperation of EU –US formally established EU-US cooperation agreement in July, 2010 and a specific ARAIM Technical Sub-Group (TSG) of US and EU Under the U.S.-EU Agreement on GPS-Galileo Cooperation signed in 2004 on the cooperation activities between the USA and the EU in the field of satellite navigation With an aim to develop an advanced integrity concept in Civil Aviation The task of this TEchGroup is to develop a solution to ensure navigation integrity for en-route flight, terminal, and approach operations, which should support lateral and vertical guidance down to a Decision Height/Altitude (DH/DA) of 200 feet This group produced 3 reports so far that are publicly available and you can find the reference in the Call text
  • #7 As an outcome of this Group is to develop Advanced Receiver Autonomous Integrity Monitoring (ARAIM) that is a concept with the intention to provide a global integrity service based on multiple satellite constellation. Basically, 2 constellations and dual-frequency are required to meet minimum availability requirements globally for LPV-200 using ARAIM, therefore the availability of both Galileo and GPS constellation and a receiver able to process their broadcasted signal in the space (SIS) is at the basis of the implementation of the ARAIM concept, that is based on the 3 possible architectures enabling different level of performance: Horizontal ARAIM, to support horizontal navigation based on an occasional Integrity Support Message (ISM) updates Offline ARAIM, to support horizontal and vertical navigation based on a monthly Integrity Support Message (ISM) updates Online ARAIM, to support horizontal and vertical navigation based on an Integrity Support Message (ISM) frequently updates (e.g. every 12minutes)
  • #9 Objective of the Call are: To develop, test and assess the performance of an ARAIM receiver’s prototype, following the guidelines defined by the ARAIM TSG (Technical Sub Group). To characterise, consolidate and validate the local effects of the threat model as specified by the ARAIM TSG. To contribute to the standardisation activities on ARAIM.
  • #10  In the Call text and on the current slide you can find an expected project flow that describes and summarises the objectives and relevant main milestones of each project’s task. Also, the most critical sub-tasks on which most of the effort is expected to be allocated are also identified there. Basically each activity subject to the call shall follow avionics system engineering lifecycle and foresee intermediate milestones which shall already be reflected as far as possible in the submitted proposal, according to the work flow described in the Call text.
  • #11 If we take a look at the Expected Workflow in more details. It is divided into 3main Tasks that are linked to the 3objectives mentioned previously. Task 1 - Aims to define the requirements and implementing definition of the ARAIM receiver’s first version prototype. This aim might be splited into the following actions: Define all receiver’s requirements (functional, safety, performance) Design and develop the prototype receiver using the most updated ARAIM reference algorithm available. Alternative or evolution version of the reference algorithm may be proposed (with equivalent or better performance). Define and consolidate a performance validation plan ------------------ Propose operational requirements for ConOps (Concept of Operations) for the porotype design Options for de/select the constellation(s) and frequencies(s) Switch between ARAIM and SBAS
  • #12 Task 2 aims to assess the achievable performance of the implemented receiver’s prototype Receiver testing should be executed: in a simulated environment (with a support of JRC) using real GNSS signal in a number of representative scenarios (real signal validation) ARAIM receiver performance to be assessed against SoL requirements Here is important to mention that Tests needs to be conducted in coordination with other relevant projects which I introduce you on the next slide ---- Analysis of RAIM and ARAIM performance
  • #13 The following initiatives, as well as any other project relevant for the scope of this action that are not included on this slide must be taken into account by the applicants while preparing the proposals, and by the beneficiary while executing the project: R&D FOR ADVANCED RECEIVER AUTONOMOUS INTEGRITY MONITORING: ARAIM DEMONSTRATOR where purpose of this project is to develop an ARAIM Demonstrator and to conduct the necessary tests, including tests with real Galileo Signal In Space (SIS) – as well as other constellations that will enhance to clarify the open questions related to its implementation. This project was kicked-off in September 2016. AVIATION STANDARDISATION FOR MULTICONSTELLATION (ATLAS): This project aims to support the introduction of Galileo and modernised version of EGNOS in the civil aviation sector in the context of new multiconstellation services recommended by ICAO. The activities will consist in delivering draft technical standards for implementation of multiconstellation/dual frequency and of next generation SBAS as well as of Advanced RAIM techniques, as aviation receiver standards are currently published for GPS stand-alone and GPS/SBAS equipment. You can find the examples of deliverables that will be generated by this project in the Call text. AVIATION DFMC SBAS RECEIVER PROTOTYPE - The purpose of the project is to design, develop and test a prototype of the DFMC SBAS (Dual Frequency Multi-Constellation SBAS) user terminal for the aviation SoL service, and augmenting GPS and Galileo capabilities. The developed receiver, shall also include Horizontal-ARAIM and RAIM. Based on the above identified projects, the applicant shall propose a project plan considering maximum effectiveness of the project results and allowing the interaction with the above projects as minimum or any other relevant projects. The needed information about the progress of the above mentioned projects will be provided by GSA/EC to the beneficiary during the project implementation.
  • #14 Task 3 is a Transversal activity with a goal to: Disseminate of the project results including at least 2 technical papers to international conferences Contribute to standardisation activities if the results deemed satisfactory and meaningful as an input Provide technical support to GSA/EC
  • #15 On this slide you can find a list of minimum set of 20 deliverables defined in the Call text for ARAIM project. Green boxes shows deliverables, its preliminary version must be included in the proposal. Their updated version shall be delivered during the implementation of the project. Grey for deliverables that are applicable just in case the demonstration is proposed by the applicant in the proposal. You can find the legend placed on the bottom of the slide and notes regarding the each deliverable in the Call text.
  • #16 Proposals will be assessed on the basis of the 3 following award criteria groups: Relevance, credibility of the proposed approach and innovation of the solution proposed (with a max score of 50) Impact in terms of economic and public benefits (with a max score of 20) Coherence and effectiveness of the work plan, appropriate task and resources allocation (max 30) That give a maximum score of 100. If a total score lower than 60 points or a score lower than 60% for any of the above three criteria is obtained, the proposal will not be evaluated further and will be rejected. Also, You can see on the slide preliminary deliverables highlighted that are requested to be submitted together with your proposal and will be evaluated within the mentioned criteria.
  • #17 On this slide you can see important dates of this Call: Among the most important is a Deadline for submission of applications – 19.5.2017 Evaluation will take place June - July 2017. Applicants will be informed about the results August - September 2017 Signature of the Grant Agreement is planned for October 2017
  • #18 Allocated budget is… And maximum duration of the projects is 2y
  • #23 Purely financial forms: A6 and C1 Some important fin. input needed (staff effort, subcontractors, overview budget, breakdown of other direct costs): B1 Some minor financial input needed: A1 and A5
  • #38 Purely financial forms: A6 and C1 Some important fin. input needed (staff effort, subcontractors, overview budget, breakdown of other direct costs): B1 Some minor financial input needed: A1 and A5
  • #43 Pre-financing: paid automatically once the GA is signed Interim payment: - After the end of 1st period Following a request for interim payment from the Consortium – financial reporting Max. 70% cumulatively for pre-financing and interim payment – i.e. if pre-financing was paid at 30% then maximum 40% of grant will be paid in interim payment Final payment: Payment of the balance – the final amount depending on the amount of total actual eligible costs After the end of the project Following a request for final payment from the consortium – financial reporting
  • #44 Subcontracting: the externalisation of specific tasks or activities which form part of the action as described in the proposal – however, beneficiaries must have operational capacity to perform the tasks in B1 therefore subcontracting has to be justified Stated in the proposal and in estimated budget: if not in the proposal/budget then needs prior approval of GSA. If major change, amendment to the GA will be needed.
  • #46 Pre-financing: paid automatically once the GA is signed Interim payment: - After the end of 1st period Following a request for interim payment from the Consortium – financial reporting Max. 70% cumulatively for pre-financing and interim payment – i.e. if pre-financing was paid at 30% then maximum 40% of grant will be paid in interim payment Final payment: Payment of the balance – the final amount depending on the amount of total actual eligible costs After the end of the project Following a request for final payment from the consortium – financial reporting