[pypy-svn] rev 1301 - pypy/trunk/doc/funding

lac at codespeak.net lac at codespeak.net
Mon Sep 15 14:12:22 CEST 2003


Author: lac
Date: Mon Sep 15 14:12:21 2003
New Revision: 1301

Added:
   pypy/trunk/doc/funding/strep_boilerplate.txt
Log:
This is the boilerplate for STRP section B


Added: pypy/trunk/doc/funding/strep_boilerplate.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/strep_boilerplate.txt	Mon Sep 15 14:12:21 2003
@@ -0,0 +1,213 @@
+Annex 2 - Proposal Part B
+IST Priority - ­ 2nd call - Guide for Proposers ­ Specific Targeted Research 
+Projects ­ June 2003
+
+Instructions for preparing proposal Part B for
+Specific targeted research projects  in the IST Priority
+
+In addition to the detailed technical information provided in Part B,
+a proposal must also contain a Part A, containing basic information on
+the proposal and the consortium making the proposal1. The forms for
+Part A are provided elsewhere in this Guide. Incomplete proposals are
+not eligible and will not be evaluated
+
+
+Specific targeted research projects will aim at improving European
+competitiveness.  They will be sharply focused and will take either of
+the following two forms, or a combination of the two: 
+
+(a) a research and technological development project designed to gain 
+    new knowledge either to improve considerably or to develop new products, 
+    processes or services or to meet other needs of society and community 
+    policies;
+
+(b) a demonstration project designed to prove the viability of new 
+    technologies offering potential economic advantage but which cannot 
+    be commercialised directly.
+
+Proposers should particularly note that only research, demonstration and 
+project management activities are funded in STREPs. Training activities 
+cannot be included among the eligible costs of projects.
+
+Information which fully details what a STREP comprises and how such a 
+project should be implemented can be found at 
+http://www.cordis.lu/fp6/instrument-strp/. Proposers should study this
+information thoroughly before commencing the preparation of their proposal 
+
+Part B.
+
+Front page
+Proposal full title
+Proposal acronym
+Date of preparation
+Type of instrument in this case: Specific targeted research project
+List of participants
+
+Participant no.                Participant name                                        Participant short name
+1 (coordinator)
+2
+3
+4
+            etc
+Coordinator name
+Coordinator organisation name
+Coordinator email
+Coordinator fax
+
+Contents page
+            show contents list
+
+Proposal summary page
+Proposal full title
+Proposal acronym
+Strategic objectives addressed 
+  (If more than one objective , indicate their order of importance 
+  to the project).
+Proposal abstract copied from Part A  (if not in English, include an 
+   English translation)
+
+B.1  Scientific and technological objectives of the project and state of 
+     the art  In the event of inconsistency between information given in 
+     Part A and that  given in Part B, the Part A version will prevail
+
+Describe in detail the proposed project's S&T objectives. The
+objectives should be those achievable within the project, not through
+subsequent development, and should be stated in a measurable and
+verifiable form. The progress of the project work will be measured
+against these goals in later reviews and assessments. Describe the
+state-of-the-art in the area concerned and how the proposed project
+will enhance the state-of-the-art in that area. 
+
+(Recommended length ­ three pages)
+
+B.2  Relevance to the objectives of the IST Priority
+
+Describe the manner in which the proposed project's goals address the
+scientific, technical, wider societal and policy objectives of the IST
+Priority in the areas concerned. 
+
+(Recommended length ­ three pages)
+
+B.3  Potential impact
+       
+Describe the strategic impact of the proposed project, for example in
+reinforcing competitiveness or on solving societal problems. Describe
+the innovation-related activities. Describe the exploitation and/or
+dissemination plans which are foreseen to ensure use of the project
+results. Describe the added-value in carrying out the work at a
+European level. Indicate what account is taken of other national or
+international research activities.
+
+(Recommended length ­ three pages)
+
+B.3.1   Contributions to standards: 
+
+Describe contributions to national or international standards which
+may be made by the project, if any.
+
+(Recommended length ­ one page)
+
+B.4     The consortium and project resources
+
+Describe the role of the participants and the specific skills of each
+of them. Show how the participants are suited and committed to the
+tasks assigned to them; show the complementarity between
+participants. Describe how the opportunity of involving SMEs has been
+addressed. Describe the resources, human and material, that will be
+deployed for the implementation of the project.  Include a STREP
+Project Effort Form, as shown below, covering the full duration of the
+project.  Demonstrate how the project will mobilise the critical mass
+of resources (personnel, equipment, finance... ) necessary for
+success; and show that the overall financial plan for the project is
+adequate.
+
+(Recommended length ­ five pages)
+
+B.4.1 	Sub-contracting: 
+
+If any part of the work is foreseen to be sub-contracted by the
+participant responsible for it, describe the work involved and explain
+why a sub-contract approach has been chosen for it.
+
+(Recommended length ­ one page)
+       
+B.4.2   Other countries : 
+
+If one or more of the participants is based outside of the EU Member
+and Associated states, explain in terms of the project's objectives
+why this/these participants have been included, describe the level of
+importance of their contribution to the project.
+
+(Recommended length ­ one page).
+
+B.5 Project management
+
+Describe the organisation, management and decision making structures
+of the project. Describe the plan for the management of knowledge, of
+intellectual property and of other innovation-related activities
+arising in the project.
+
+(Recommended length ­ three pages)
+
+B.6 Detailed Implementation plan
+       
+This section describes in detail the work planned to achieve the
+objectives for the full duration of the of the proposed project. The
+recommended length, excluding the forms specified below, is up to 15
+pages. An introduction should explain the structure of this workplan
+plan and how the plan will lead the participants to achieve the
+objectives. The workplan should be broken down according to types of
+activities: Research, technological development and innovation related
+activities, demonstration activities and project management
+activities. It should identify significant risks, and contingency
+plans for these. The plan must for each type of activity be broken
+down into workpackages (WPs) which should follow the logical phases of
+the project, and include management of the project and assessment of
+progress and results. 
+
+Essential elements of the plan are:
+       
+a) Detailed Implementation plan introduction ­ explaining the structure 
+   of this plan and the overall methodology used to achieve the objectives.
+       
+b) Work planning, showing the timing of the different WPs and their 
+   components (Gantt chart or similar)
+       
+c) Graphical presentation of the components showing their 
+   interdependencies (Pert diagram or similar)
+            
+d) Detailed work description broken down into workpackages:
+   Workpackage list (use Workpackage list form below);
+   Deliverables list (use Deliverables list form below);
+   Description of  each workpackage (use Workpackage description form 
+                                     below, one per workpackage):
+           
+Note: The number of workpackages used must be appropriate to the
+complexity of the work and the overall value of the proposed
+project. Each workpackage should be a major sub-division of the
+proposed project and should also have a verifiable end-point (normally
+a deliverable or an important milestone in the overall project).  The
+planning should be sufficiently detailed to justify the proposed
+effort and allow progress monitoring by the Commission ­ the
+day-to-day management of the project by the consortium may require a
+more detailed plan.
+
+(recommended length, excluding the forms specified above,- up to 15 pages)
+
+B.7 Other issues
+            
+B.7.1. If there are ethical or gender issues associated with the
+subject of the proposal, show they have been adequately taken into
+account - indicate which national and international regulations are
+applicable and explain how they will be respected. Explore potential
+ethical aspects of the implementation of project results. Include the
+Ethical issues form given below.
+
+B.7.2 Are there other EC-policy related issues, and are they taken
+into account? Demonstrate a readiness to engage with actors beyond the
+research to help spread awareness and knowledge and to explore the
+wider societal implications of the proposed work; if relevant set out
+synergies with education at all levels.
+            
+(No recommended length ­ depends on the number of such other 
+ issues which the project involves).


More information about the Pypy-commit mailing list