Why bids fail: Bidding for EU ICT research projects
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Why bids fail: Bidding for EU ICT research projects

on

  • 1,232 views

This seminar gave an insider’s view on bidding for EU research funds. It focused on EU FP7 IST research instruments (IPs, STREPS etc), what they are, how they are evaluated, why bids fail and what ...

This seminar gave an insider’s view on bidding for EU research funds. It focused on EU FP7 IST research instruments (IPs, STREPS etc), what they are, how they are evaluated, why bids fail and what a successful bid looks like.

Statistics

Views

Total Views
1,232
Views on SlideShare
1,225
Embed Views
7

Actions

Likes
0
Downloads
11
Comments
0

1 Embed 7

http://cdelondon.wordpress.com 7

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Why bids fail: Bidding for EU ICT research projects Presentation Transcript

  • 1. Why bids fail: Bidding for EU ICT research projects Stephen Brown, 20 May 2010
  • 2. Overview
    • FP7 ICT call 1 results
    • Project types
    • The evaluation process
    • Evaluation criteria
    • Scoring
    • Good proposals
    • Bad proposals
  • 3. Most proposals fail
  • 4. FP7 ICT call1 results
    • 188 eligible proposals submitted
    • 12 proposals funded (52m Euros)
    • 6% success
    • Most proposals fail…..
    • …… but not because they are bad
  • 5. FP7 ICT call1 results Most proposals have to fail Project type Funding requested Funding published IPs 181.5 M€ 20-32.5 M€ STREPs 506.8 M€ 10-22 M€ NoEs 15.6 M€ 5 M€ CSAs 14.2 M€ 2.5 M€
  • 6. Project types
    • STREPs
    • IPs
    • NoEs
    • CAs
    • SAs
  • 7. STREPs
    • Focused objectives
    • Clearly identified problem
    • Research and demonstration activities
    • Scope for competing approaches to solving problems
    • Small scale (2-4 M€ over 1-2 years)
  • 8. IPs
    • Integration of projects within a coherent set of activities
    • Outreach and validation are important
    • Include training, innovation, takeup and dissemination activities
    • Active partners with substantial roles and clear responsibilities
    • Large IPs (average range is 6-9 M€ over 3-4 years) need to show very clearly how they will make a significant impact in their target area
  • 9. NoEs
    • Aim is the durable integration of high calibre research capacity
    • NoEs should involve the stakeholders, especially industry
    • Funding is for convergence and embedding, not research
    • Size and funding of NoEs much smaller than in FP6 (2-3M€ over 3 years)
  • 10. CSAs
    • Bringing researchers together either in new areas (as forerunner of eventual NoEs)
    • Supporting workshops and communities of practice – eg in creating framework conditions for take up of research work
    • Support for building and maintaining the body of evidence of research
    • <1M € each
  • 11. The evaluation process
  • 12. The evaluation process
    • STREPs
    • Individual expert
    • Consensus Group
    • Panel meeting
    • IPs & NoEs
    • Individual expert
    • Consensus Group
    • Interim panel meeting
    • Hearing
    • Panel meeting
    Plenty of opportunities to fail
  • 13. Evaluation criteria
  • 14. S/T QUALITY “ Scientific and/or technological excellence (relevant to the topics addressed by the call)” IMPLEMENTATION “ Quality and efficiency of the implementation and the management” IMPACT “ Potential impact through the development, dissemination and use of project results”
    • Soundness of concept, and quality of objectives
    • • Progress beyond the state-of-the-art
    • • Quality and effectiveness of the S/T methodology and associated work plan
    • Appropriateness of the management structure and procedures
    • Quality of the consortium as a whole (including complementarity, balance)
    • Quality and relevant experience of the individual participants
    • Appropriateness of the allocation and justification of the resources to be committed (budget, staff, equipment)
    • Contribution, at the European and / or international level, to the expected impacts listed in the work programme under relevant topic/activity
    • Appropriateness of measures for the dissemination and/or exploitation of project results, and management of intellectual property
  • 15. Scoring
    • 0 - The proposal fails to address the criterion under examination or cannot be judged due to missing or incomplete information.
    • 1 - Very poor . The criterion is addressed in a cursory and unsatisfactory manner.
    • 2 - Poor . S erious inherent weaknesses in relation to the criterion in question.
    • 3 - Fair . While the proposal broadly addresses the criterion, there are
    • significant weaknesses that would need correcting.
    • 4 - Good . The proposal addresses the criterion well, although certain
    • improvements are possible.
    • 5 - Excellent . The proposal successfully addresses all relevant aspects of the criterion in question. Any shortcomings are minor.
  • 16. Funding thresholds
    • Proposals must score at least 3 on any criterion to be funded
    • Proposals scoring 10 or above can be considered for funding
    • 35% above threshold but not funded
    • Proposals scoring 13.5 or above are usually considered for funding
    • You need drop only 3 half marks to fail
  • 17. FP7 ICT call1 results
    • 67% failed on multiple thresholds
    • of these 43% failed on criterion 1 – scientific excellence relevant to the objectives
    • 52% IPs and 40% STREPS failed criterion 3 - impact
  • 18. Don’t give up
  • 19. What good proposals look like
    • Describe your problem, explain why it is relevant and how you will tackle it
    • Describe the specific state-of-the-art with referenced evidence , as well as the technical baseline , and expected advancements against which progress can be measured
    • Show you understand the state of the art – don’t just list projects and articles
    • Check the timelines and anticipated outputs of ongoing research in defining your starting point and the advances you will make – don’t replicate existing work
  • 20. What good proposals look like
    • Explain how you will ensure impact
    • Adopt a scientifically sound approach to involving users in the research, including to the assessment and validation necessary to build the evidence of impact
    • Find the right partners – not necessarily the nearest or most convenient. Do justice to the multi-disciplinary nature of the area – ensure the expertise and the roles are balanced and appropriate.
    • Cost out work packages clearly and realistically
  • 21. Relevance
  • 22. Work Programme
    • Target outcomes
    • Fifth call results
  • 23. Common mistakes
  • 24.
    • Provide yet another training solution for a particular set of users (eg training for engineers) with no new work on how people acquire skills and competences, in different contexts
    • Develop a Learning Management System, Content Delivery Platform or VLE – these are mainstream eLearning products
    • Develop something for a specific language, geography, history and don’t justify how ICTs will improve learning in that field
  • 25.
    • Describe a “technology driven” type of project
    • Fail to leverage a balance of research across the contributing disciplines
    • Fail to identify what the different disciplines contribute
    • Produce a proposal that tries to do everything and is just not credible. Often less is more
  • 26. Critical questions you should ask yourselves
    • Does the proposal address the right published target outcomes?
    • Does the proposal address a new problem or offer different and innovative insights into an existing one?
    • How far is the problem you intend to address already being tackled elsewhere?
    • Which communities are likely to benefit from the project / how are they involved?
    • What will the benefits / impact of the project be?
    • What are the challenges and potential risks and how are they tackled?
  • 27. Further information
    • Comprehensive EC guide to “How to fail”
      • ftp://ftp.cordis.europa.eu/pub/ist/docs/telearn/what-not-to-do_en.pdf
    • Introduction to Cultural Heritage & Technology Enhanced Learning, including links to programme descriptions, publications that describe currently funded projects and links to commission / project web sites and contacts.
      • http://cordis.europa.eu/fp7/ict/telearn-digicult/home_en.html
  • 28. Stephen Brown For further information contact