H2020EDFHORIZONFP7
Thales Las France Sas
- Country
- FRFrance
- Defence projects
- 19
- Projects, all programmes
- 78
- As coordinator
- 7
- EU contribution (CORDIS)
- EUR 71,334,918
- Active
- 2008 to 2026
Projects
78 projects, newest first
| Project | Programme | Year | Role | EU contribution |
|---|---|---|---|---|
| PJ22 SEabirdPJ22:Validation and Demonstration Engineering | H2020 | 2016 | Participant | EUR 228,000 |
| PJ17 SWIM-TISWIM Technical Infrastructure | H2020 | 2016 | Coordinator | EUR 2,784,999 |
| PJ09 DCBAdvanced DCB | H2020 | 2016 | Participant | EUR 975,000 |
| PJ01 EADEnhanced Arrivals and Departures | H2020 | 2016 | Participant | EUR 1,839,000 |
| PJ20 AMPLEMaster Plan Maintenance | H2020 | 2016 | Participant | EUR 195,000 |
| PJ15 COSERCommon Services | H2020 | 2016 | Participant | EUR 1,562,000 |
| PJ19 CIContent Integration | H2020 | 2016 | Participant | EUR 540,999 |
| PJ04 TAMTotal Airport Management | H2020 | 2016 | Participant | EUR 2,552,000 |
| PJ02 EARTHIncreased Runway and Airport Throughput | H2020 | 2016 | Participant | EUR 2,219,500 |
| PJ03a SUMOIntegrated Surface Management | H2020 | 2016 | Participant | EUR 1,884,999 |
| PJ06 ToBeFREETrajectory based Free Routing | H2020 | 2016 | Participant | EUR 444,017 |
| Future Sky SafetyFuture Sky Safety | H2020 | 2015 | Participant | EUR 449,980 |
| EXISTExtended Image Sensing Technologies | H2020 | 2015 | Participant | EUR 717,267 |
| ASCOSAviation Safety and Certification of new Operations and Systems | FP7 | 2012 | Participant | EUR 132,881 |
| UFOUltraFast wind sensOrs for wake-vortex hazards mitigation | FP7 | 2012 | Coordinator | EUR 519,774 |
| PARSIMOPartitioning and Modeling of SiP | FP7 | 2011 | Participant | EUR 31,638 |
| NANOTECNanostructured materials and RF-MEMS RFIC/MMIC technologies for highly adaptive and reliable RF systems | FP7 | 2011 | Participant | EUR 40,614 |
| WAKENET3-EUROPEEuropean Coordination Action for Aircraft Wake Turbulence | FP7 | 2008 | Participant | EUR 70,072 |
The country is the one the source records for the organisation’s registration (its PIC), and each profile says what it rests on. Where the record contradicts itself (the address in one country, the site name and the VAT number in another) we follow the two that agree: the Spanish research council CSIC is shown under Spain although its address is recorded in Italy. A body with sites in several countries is shown under the first of them in alphabetical order, and its profile lists the others. Beyond that we do not guess.
Where this comes from
- CORDIS: EU research projects (Horizon Europe, Horizon 2020, FP7)Last read on . Licence: Commission Decision 2011/833/EU (reuse of Commission documents). Source: CORDIS, European Commission.Participants and amounts as the Commission's CORDIS database states them (reuse under Commission Decision 2011/833/EU).
- European Defence Fund: project factsheets of the call resultsLast read on . Licence: Commission Decision 2011/833/EU (reuse of Commission documents). Source: European Commission, DG DEFIS, EDF results factsheets.European Defence Fund participants are read from the project factsheets that DG DEFIS publishes, by a language model; every name is checked against the factsheet text and a name that is not in it is dropped. The factsheets state no amount per participant.
EU contribution is the amount CORDIS's open data pays to the participant. For a participant with linked third parties it may include their share (the CORDIS page prints the net); an amount the data does not hold is left out, not counted as zero. EDF factsheets state none per participant, so EDF projects count as projects but add nothing to the amounts.
Organisation-level facts only: a name, a country, a role, an amount, a year. A participant is recognised by its PIC where the source gives one, otherwise by name; the page says which. How the data is built.
Names are as CORDIS and the EDF project factsheets publish them. We do not list an organisation whose name looks like a natural person’s. If this entry is you, or a business named after you, and you want it removed, write to the contact in the imprint; the privacy notice (sections 7 and 9) says how a request is handled.