[pypy-svn] rev 1407 - pypy/trunk/doc/funding
lac at codespeak.net
lac at codespeak.net
Tue Sep 23 11:40:30 CEST 2003
Author: lac
Date: Tue Sep 23 11:40:30 2003
New Revision: 1407
Added:
pypy/trunk/doc/funding/STREP-template.txt
Log:
Here is a text version of the STREP template. I thought I had checked
this in before. Sorry about that.
Added: pypy/trunk/doc/funding/STREP-template.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/STREP-template.txt Tue Sep 23 11:40:30 2003
@@ -0,0 +1,1084 @@
+Please note that these documents and this Template is aimed
+specifically at IST Call 2 fixed deadline. It is of particular
+importance to understand the Evaluation Criteria to be used on a STREP
+so I reproduce them here (Note overall threshold of 21 points out of
+30 for STREP)
+
+
+0.1 Relevance
+
+(Threshold: 3 out of 5) Weight 1
+
+What is the extent to which the proposal addresses the scientific,
+technical, socio-economic and policy objectives of the Workprogramme
+in the areas open in the call ?
+
+
+0.2 Potential impact
+(Threshold: 3 out of 5) Weight 1
+
+The extent to which
+
+· the proposed project is likely to have an impact in terms of
+ strategic impact on reinforcing competitiveness or solving societal
+ problems
+
+· exploitation and dissemination plans are adequate to ensure optimum use of
+ project results
+
+· the proposal demonstrates a clear added-value in carrying out the
+ work at a European level and takes account of research activities
+ at a national level and under European initiatives (e.g. Eureka) ?
+
+
+0.3 Scientific and technical excellence
+(Threshold: 4 out of 5) Weight 1
+
+The extent to which
+· the proposal has clearly defined and well focused objectives
+
+· the objectives represent clear progress on the state-of-the-art
+
+· the proposed S&T approach is likely to enable the project to achieve
+ its objectives in research and innovation
+
+
+0.4 Quality of the consortium
+(Threshold: 3 out of 5) Weight 1
+
+The extent to which
+
+· the participants collectively constitute a consortium of high
+ quality
+
+· the participants are well suited and committed to their tasks
+ assigned to them
+
+· there is good complementarity between the participants
+
+· the real opportunity to involve SMEs been adequately addressed
+
+0.5 Quality of the management
+(Threshold: 3 out of 5) Weight 1
+
+The extent to which
+
+· the project management of high quality
+
+· there is a satisfactory plan for the management of knowledge, IPR
+ and innovation-related activities
+
+0.6 Mobilisation of resources
+(Threshold: 3 out of 5) Weight 1
+
+The extent to which
+
+· the project forsees the resources (personnel, equipment, finance...)
+ necessary for success
+
+· the resources are convincingly integrated to form a coherent project
+
+· the overall financial plan for the project adequate
+
+
+0.7 Horizontal Issues (comment if applicable)
+
+· If there gender issues associated with the subject of the proposal,
+ have they been adequately taken into account?
+
+· Have the applicants identified the potential ethical and/or safety
+ aspects of the proposed research regarding its objectives, the
+ methodology and the possible implications of the results?
+
+· To what extent does the proposal demonstrate a readiness to engage
+ with actors beyond the research community and the public as a
+ whole, to help spread awareness and knowledge and to explore
+ the wider societal implications of the proposed work?
+
+· Have the synergies with education at all levels been clearly set out?
+
+· If third country participation is envisaged in the proposal, is it
+ well justified and the participation well integrated in the activities?
+
+
+TEMPLATE STARTS HERE:
+
+Proposal full title:
+
+
+
+
+
+Proposal acronym:
+
+
+Date of preparation:
+
+
+Type of instrument: Specific Targeted Research Project
+
+
+List of participants (Co-ordinator first):
+
+
+Participant no. Participant name Participant short name
+1 (coordinator)
+2
+3
+4
+etc
+
+
+
+
+Co-ordinator Organisation name:
+Point of Contact name:
+Point of Contact email:
+Point of Contact telephone:
+
+
+Contents
+
+
+Contents
+
+Proposal summary page
+B.1 Scientific & technological objectives of the project & state of the art
+B.1.1 Problem to be solved
+B.1.2 Quantified specific objectives
+B.1.3 Current State of the Art
+B.1.4 Beyond the State of the Art
+B.2 Relevance to the objectives of the IST Priority
+B.3 Potential impact
+B.3.1 Contributions to Standards
+B.3.2 Strategic impact
+B.3.2.1 Potential Impact on Industrial/Research Sector
+B.3.2.2 Balance of Trade
+B.3.2.3 European Dimension and AddedValue
+B.3.3 Innovation Related Activities
+B.3.3.1 Management of Knowledge Produced
+B.3.3.2 Protection of Intellectual Property
+B.3.4 Dissemination
+B.3.5 Exploitation
+B.4 The consortium and project resources
+Description of the consortium (1 page)
+B.4.1 Sub-contracting
+B.4.2 Other countries
+B.4.3 Description of the participants
+B.4.4 Quality of partnership, involvement of users and SMEs
+B.4.5 Resources to be deployed
+B.4.6 Overall FinancialPlan
+B.4.7 STREP Project Effort Form
+B.5 Project management
+B.5.1 Project Manager
+B.5.2 Management Structure
+B.5.3 Co-ordinator
+B.5.4 Project Meetings
+B.5.5 Quality procedures
+B.5.6 Communication and Reporting
+B.5.7 Consortium Agreement
+B.5.8 Management of Knowledge and Intellectual Property
+B.6 Detailed Implementation Plan
+B.6.1 Introduction
+B.6.2 Research and Technological Aspects and Options
+B.6.3 Risks in the Project and Steps to Minimise
+B.6.4 Project planning and time table; (Gantt chart)
+B.6.5 Graphical presentation of the project's components; (PERT diagram)
+B.6.6 Deliverables list (full duration of project)
+B.6.7 Workpackage description (full duration of project)
+B.7 Other issues
+B.7.1 Ethical Considerations
+B.7.2 Gender Issues
+B.7.3 Safety Issues
+B.7.4 Conservation Regulations
+B.7.5 Other Policy related Issues
+
+
+ Proposal summary page
+
+
+ Proposal full title:
+
+
+ Proposal acronym:
+
+ Strategic Objectives:
+
+ List here the Strategic Objectives in this call that are
+ addressed by this proposal in priority order with the most
+ important one first if there is more than one. Remember the
+ proposal must be specifically directed at this first one and will
+ normally be evaluated by that team.
+
+
+ Proposal abstract:
+
+ Proposal abstract copied from Part A1 to be added here (Maximum
+ 2,000 characters)
+
+
+B.1 Scientific & technological objectives of the project & state of the art
+
+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)
+
+
+This section describes the scientific/technological objectives of the
+proposal in a measurable and verifiable form. The progress of the
+project work will be measured against these objectives in later
+reviews and assessments.
+
+Although this section talks about objectives, I strongly recommend you
+only have a single high level objective to ensure project focus. You
+could identify spin off benefits or subsidiary objectives but try to
+ensure you start off by identifying a single objective.
+
+B.1.1 Problem to be solved
+
+It is also a good idea to clearly identify the problem to be solved
+
+
+B.1.2 Quantified specific objectives
+
+Try to quantify statements whereever made, especially technical targets.
+
+B.1.3 Current State of the Art
+
+Demonstrate awareness of the current state-of-the-art and differences
+between this proposal and any similar existing or previous projects.
+
+B.1.4 Beyond the State of the Art
+
+Show the degree of originality, innovation and promise of progress
+beyond it. Strike an appropriate balance in the level of risk
+associated with the project compared to its potential benefits - high
+risk may be acceptable in return for high benefits. Avoid very large
+or unacceptable levels of risk.
+
+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)
+
+Information for this section comes from several main sources -
+
+
+ 1. Each Workprogram and the Commission specific program documents
+ identify and address the policy needs to a certain extent.
+ The introductory sections of the Workprogram for IST 2003/4
+ contains good reference material.
+
+
+ 2. Via the Europa web site, http://europa.eu.int there is
+ information on all EU policies and they can be identified and
+ downloaded from there. For example we have the following
+ Policies - Access by subject to legal instruments in force,
+ legislative activity in progress, implementation of common
+ policies, EU grants and loans, statistics and publications.
+
+
+ 3. There is also good material under eEurope initiatives and at
+ the ISPO (information Society Project Office) site.
+
+
+You must also address where appropriate ERA related issues such as
+relationships to any Eureka activities, (such as commonality of partners)
+or relationships to national research programs.
+
+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 four pages,
+including one for "Contribution to Standards")
+
+This section should include the description of plans for the
+dissemination and/or exploitation of the results for the consortium as
+a whole and for the individual participants in concrete terms, for
+example by describing the dissemination and/or exploitation
+strategies, the user groups to be involved and how they will be
+involved, the tools and/or means to be used to disseminate the results
+and the strategic impact of the proposed project in terms of
+improvement of competitiveness or creation of market opportunities for
+the participants.
+
+
+B.3.1 Contributions to Standards
+
+Describe contributions to national or international standards which
+may be made by the project, if any. Identify specific standards
+bodies and committees with an emphasis on European bodies such as
+CEN/CENELEC, ETSI, ECMA etc and International bodies such as ISO JTC
+as well as Industrial Informal Standards Bodies. It is better to avoid
+purely US bodies such as ANSI if possible.
+
+B.3.2 Strategic impact
+
+Show that the project will have a significant strategic impact and not
+merely satisfy intellectual curiosity.
+
+B.3.2.1 Potential Impact on Industrial/Research Sector
+
+Convincingly describe the impact it will have on its
+industry/commerce/research sector and how it will improve European
+competitiveness and assist in market development where
+applicable. Demonstrate a clear view of the market segment(s) and
+market needs, which it addresses.
+
+B.3.2.2 Balance of Trade
+
+Showing how it will contribute to an improvement in the balance of
+trade is also an important aspect.
+
+B.3.2.3 European Dimension and Added Value
+
+Does the proposal address European issues or merely address a national
+issue? Assess the extent to which the project is required by the EU as
+a whole? Does the proposal identify and describe interdependencies or
+links with other national or international activities?
+
+What are the European/international dimension in the execution of the
+work, for example is there a need to establish a critical mass in
+human or financial terms, or does adequate resources and expertise not
+exist in individual countries? Will the impact of carrying out the
+work at the European level be greater than the sum of the impacts of
+national projects?
+
+B.3.3 Innovation Related Activities
+
+Please note that "innovation" as used here is not technological
+innovation. The commission in their wisdom have redefined the term to
+mean the following (within a STREP) "Specific targeted projects
+should also include innovation-related activities, in particular with
+respect to the management of the knowledge produced and the protection
+of intellectual property."
+
+Note that management aspects of this are addressed under B.5.8.
+
+B.3.3.1 Management of Knowledge Produced
+
+Describe this activity.
+
+This is the ongoing identification, tracking and registration of
+knowledge as it is produced within the project. It is particularly
+concerned with the deciisons on ownership of IP and should be covered
+in the Consortium Agreement. IP, not forseen or falling outside of the
+agreement will require special treatment and may even require
+modification to the agreement. The process should be identified and
+covered in B.5.8.
+
+
+B.3.3.2 Protection of Intellectual Property
+
+Describe this activity.
+
+The owner of knowledge should provide adequate and effective
+protection for knowledge that is capable of industrial or commercial
+application.
+
+The Commission may adopt protective measures when it considers it
+necessary to protect knowledge in a particular country, and when such
+protection has not been applied for or has been waived.
+
+Participants may publish information on the knowledge acquired under
+the project, provided this does not affect the protection of that
+knowledge.
+
+Basically this section should define how the project will protect the
+IP produced by it, identifying the process and responsibility. It
+should be cross referenced from the management section in B.5.8.
+
+B.3.4 Dissemination
+
+The project is not funded merely to benefit the participating
+organisations. Show that results will be adequately disseminated so
+as to support general European scientific or technological progress.
+Define specific plans for dissemination, with explicit commitments by
+participants. i.e. Papers at European conferences, web site,
+publication of papers etc.
+
+B.3.5 Exploitation
+
+Emphasise the usefulness and range of applications, which might arise
+from the project. Explain the partners' capability to exploit the
+results of the project and detail how you foresee doing this in a
+credible way. Refer to the draft Consortium Agreement with respect to
+exploitation rights within the consortium. This is particularly
+important. Be specific and quantify things such as accessible market
+etc.
+
+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 seven pages, including one for B.4.1
+and one for B.4.2)
+
+
+Description of the consortium (1 page)
+
+Short description of one page of the consortium stating who the
+participants are, what their roles and functions in the consortium
+are, and how they complement each other.
+
+
+ Participant Country Role Function Note
+
+Either add in here or put under Notes column, Complementarity as appropriate.
+
+
+ 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. Do not
+sub-contract R&D. Remember if a company sub-contracts some work
+they will normally have to pay 100% of their costs (potentially
+with profit) and will normally only get 50% back. Do not
+subcontract project management.
+
+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.
+
+Where a non-EU/Associated State participation is involved, demonstrate
+it is in conformity with the interest of the Community, and it is
+of substantial added value for implementing all or part of the
+specific programme.
+
+B.4.3 Description of the participants
+
+Short description of the participating organisations including:
+
+· The expertise and experience of the organisation,
+
+· Short CVs of the key persons to be involved indicating relevant
+ experience, expertise and involvement in other EC projects. (Each
+ CV no more than 10 lines) Remember that you cannot contractually
+ commit to these specific persons being assigned so you should state
+ that these named people or their equivalent will be assigned
+
+The CV of the nominated Project Manager is of particular importance.
+You have to show that he has experience of successful international
+project management. Emphasise this aspect.
+
+
+B.4.4 Quality of partnership, involvement of users and SMEs
+
+Show that the organisations involved in the consortium are capable of
+doing the tasks allotted to them. Ensure there is no unnecessary
+redundancy and duplication in the make-up of the consortium. Ensure
+the consortium does not lack an obvious participant with some
+essential skill or resource.
+
+Describe how involvement of SMEs has been addressed.
+
+B.4.5 Resources to be deployed
+
+Show how the project will mobilise the critical mass of resources
+(personnel, equipment, finance...) necessary for success.
+
+
+B.4.6 Overall Financial Plan
+
+Show that the overall financial plan for the project is adequate.
+
+
+In B4.7 (below) do not identify any activities as "demonstration"
+i.e. leave that section blank.
+
+B.4.7 STREP Project Effort Form
+
+Full duration of project (insert person-months for activities in which
+partners are involved)
+
+Project acronym -
+
+
+ Short Names
+ Partner 1
+ Partner 2
+ Partner 3
+ Partner 4
+ Partner 5
+ etc
+ TOTAL PARTNERS
+
+
+ WP name
+ WP name
+ WP name
+ etc
+ Total research/innovation
+
+
+
+ Demonstration activities
+ WP name
+ WP name
+ WP name
+ etc
+ Total demonstration
+
+
+
+ Consortium management activities
+ WP name
+ WP name
+ WP name
+ etc
+ Total management
+
+
+ TOTAL ACTIVITIES
+
+
+
+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)
+
+This section should describe how the proposed project will be managed,
+the decision making structures to be applied, the communication flow
+within the consortium and the quality assurance measures which will be
+implemented, and how legal and ethical obligations will be met.
+
+Quality of the management
+
+Make it clear how progress will be monitored and how an effective
+management structure will be put in place, with agreed lines of
+communication and responsibility. Describe how corrective actions
+will be initiated and how conflicts will be resolved.
+
+
+B.5.1 Project Manager
+
+Every project must have a Project Manager. He will be responsible for
+the Management of the Project and execution of the contract. He
+is appointed by the Co-ordinator and chairs the Management
+Meetings. He approves all outputs and reports, is the prime
+external interface and also may be the Technical Director (if one
+is deemed necessary).
+
+
+There is some confusion as to the role of the Project Manager. This is
+not an administrative chore. A Project Manager will require some
+administrative support, but that is far from the essence of the job.
+The administrative functions such as status tracking, financial
+reporting, change control and project library maintenance are really a
+minor part of the overall job.
+
+Project management activities
+
+Specific targeted research projects will also include an overall
+management structure. Over and above the technical management of
+individual work packages, an appropriate management framework linking
+together all the project components and maintaining communications
+with the Commission will be needed.
+
+Project management will include:
+
+· co-ordination of the technical activities of the project;
+
+· the overall legal, contractual, ethical, financial and administrative
+ management of the project;
+
+· preparing, updating and managing the consortium agreement between
+ the participants;
+
+· co-ordination of knowledge management and other innovation-related
+ activities;
+
+· overseeing the promotion of gender equality in the project;
+
+· overseeing science and society issues, related to the research
+ activities conducted within the project;
+
+· obtaining audit certificates (as and when required) by each of the
+ participants;
+
+· bank guarantees for SMEs (if applicable).
+
+Successful Project Management of a FrameWorkprogram Project
+requires various skills and knowledge. In my view it requires a
+person with the following attributes
+
+ · Good appreciation of the relevant business area
+
+ · Participation in a previous Framework project
+
+ · Knowledge of Framework procedures
+
+ · Good interpersonal skills
+
+ · Well organised and systematic in own work
+
+ · Good knowledge of ISO 9001
+
+ · Good knowledge of English
+
+ · Some knowledge of project technical area
+
+ · Some knowledge of financial management
+
+Project Management is a combination of all of the above skills. Extra
+strength in some areas could compensate for weakness in others.
+Remember this function includes legal responsibility aspects and thus
+keeping of good records is essential. Any telephone calls and
+agreements, especially with the Project Officer should be minuted
+and/or confirmed in writing, at least by email.
+
+
+ B.5.2 Management Structure
+
+As this type of project is essentially the same as the previous RTD
+project, I would maintain the traditional structure as follows -
+
+(see the PDF)
+
+For smaller projects and depending on the technical abilities of the
+company representatives, it is sometimes possible and more effective
+to combine the Management and Technical Boards although they must
+continue to deal with both aspects.
+
+
+ B.5.3 Co-ordinator
+
+This is the principal interface to the Commission - both during
+proposal and project stages and is responsible for submitting the
+proposal; also conducts the contract negotiation. During project
+appoints the Project Manager, submits all reports, normally handles
+the financial statements and payments, chairs the Project Management
+Board and has overall control of the project.
+
+Note that the Coordinator normally appoints the project manager. If,
+under rare circumstances it is decided to split the management into
+Managerial and Technical parts, then a Technical Director is also
+appointed, although he is not necessarily from the Coordinating
+Organisation.
+
+
+A distinction between Financial Coordinator and Scientific
+Coordinator is no longer recognised in the contract. Any
+distinctions of role between the partners must be embodied in
+the Consortium Agreement.
+
+It is also normal for the Technical Director to chair a Technical
+Board that would consist of the Key Technical staff - one per partner
+normally or Work package leaders. Such meetings are normally held
+adjacent to Management Board meetings.
+
+
+The Technical Director would also sit on the Management Board ex
+officio and the Project Manager on the Technical Board.
+
+It is normal to have a structure as shown above under B.5.2 (note the
+Technical Board could be combined into the Management board).
+
+I am trying here to give a flavour of the type of words and content to
+use. It is not exhaustive. Do not copy them verbatim.
+
+
+A Management Board will be created that will be responsible for the
+successful completion of the project and the exploition of its
+result. It will be chaired by the appointed Project Manager and will
+consist of a senior representative of each partner.
+
+Decisions regarding the project will be made by vote with each partner
+having a single vote. In cases of a tie, the project manager will
+have a casting vote.
+
+ The role of the Management Board will include the following -
+
+ · Management of resources in order to meet schedules and goals
+ · To ensure the quality management of the project
+ · Tracking of costs related to budget
+ · Resolution of conflicts
+ · Creation of technology implementation plan and its updating
+ · Ensuring compliance with legal and ethical obligations
+
+Explain the role/responsibilities of Technical Board if constituted
+and state that it reports to the Management Board.
+
+B.5.4 Project Meetings
+
+The Management Board will meet at the start of the project and (2/3/4)
+times per year or on an ad hoc basis as requested. The meetings will
+normally be scheduled to rotate between the principal contractors
+home base.
+
+Add info on Technical meetings as required.
+
+
+B.5.5 Quality procedures
+
+The project manager will circulate a draft Quality Management plan
+forthe project prior to first Project Meeting and and then present it
+for approval at the first Meeting.
+
+ It will contain as a minimum, procedures for -
+
+ · Document procedures, standards and control
+ · Issue control for documents
+ · Reporting procedures, frequency and format
+ · Communication procedures
+ · Corrective actions
+ · Exception control
+ · Conflict resolution
+ · Meeting draft agenda
+ · Format of meeting minutes
+ · Tracking system for actions
+ · Specific responsibilities within the project
+
+B.5.6 Communication and Reporting.
+
+Amplify here specific policies on this subject ie use of email or
+communication via web site management page, telephones, video
+conferencing, frequency etc
+
+B.5.7 Consortium Agreement
+
+A Consortium Agreement between the partners is now mandatory and must
+be signed before any participant start work on the project. The
+Project Manager must be responsible for this activity.
+
+
+B.5.8 Management of Knowledge and Intellectual Property
+
+The rules regarding the protection dissemination and use of knowledge
+have been simplified and a larger flexibility is granted to the
+participants:
+
+ · rules are identical for all participants;
+ · rules concentrate on the principles and provisions considered
+ necessary for an efficient cooperation and the appropriate use and
+ dissemination of the results;
+ · participants may define among themselves the arrangements that
+ fit them the best within the framework provided in the model
+ contract.
+
+
+ See also comments under B.3.3.1 and B.3.3.2 and address here.
+
+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.
+
+I strongly suggest you do not identify any "demonstration activities".
+Do not use the word "demonstration" anywhere. Anything you consider
+may fall under this heading refer to as "trial", "validation"
+or"system test" or something similar. This simplifies the proposal
+and more importantly avoids, or at least may mitigate against, being
+reduced to 35% funding.
+
+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). Ensure that the workplan is
+ appropriate, clear, consistent, and efficient without serious omissions.
+ Ensure a clear working schedule is laid out, with clearly identified
+ review points.
+
+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.
+
+Ensure the manpower effort for each partner and workpackage is
+credible, without seriously under/over estimating. Ensure the other
+resources required are also credible. Make sure there are no
+resources required which appear not to be foreseen.
+
+It is normal to assign WP1 to Project Management. This would include
+all general activities such as Board Meetings etc. It is normal for
+the Coordinator to have the majority of this with small amounts for
+each of the partners to cover their participation in the general
+meetings.
+
+A useful metric is that Project Management is usually expected to
+average around 10% of the project effort. Any significant deviation
+should be justified.
+
+Allow the evaluators to make an overall assessment of the quality of
+the research proposed to be carried out, from a scientific and
+technical point of view.
+
+Dont forget to have a Workpackage or Task related to disseminating the
+results.
+
+B.6.1 Introduction
+
+Explain the structure of the workplan and the overall methodology used
+to achieve the objectives
+
+B.6.2 Research and Technological Aspects and Options
+
+Explain the adequacy of the chosen approach, methodology and work plan
+for achieving the objective(s). As appropriate, you may describe
+overall systems design. Schematics can help to illustrate this
+section.
+
+B.6.3 Risks in the Project and Steps to Minimise
+
+Be frank about potential risks. They may be technical, organisational,
+business related etc. For each risk say how you will monitor it, minimise
+it or even what the contingency or backup plan is.
+
+B.6.4 Project planning and time table; (Gantt chart)
+
+It is normal to identify key events on the Gantt chart such as Board
+Meetings (Bx) and /or other specific events (Evx, MTR = Mid term
+Report, etc)
+
+B.6.5 Graphical presentation of the project's components; (PERT diagram)
+
+Broken down into workpackages and showing constraints and events with
+the critical path identified:
+
+It is usually a good idea to identify major milestones on this PERT
+diagram as appropriate.
+
+B.6.4 Workpackage list (full duration of project)
+ B.6.7 Workpackage description (full duration of project)
+
+ One page description of each workpackage (use form below):
+
+ 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
+ workplan).
+
+
+ In medium to large projects it is also good practice to further
+ divide each Workpackage into Tasks. Each with a leader and each
+ ending in deliverable.
+
+
+ The level of detail expected under the Fifth Framework is
+ unclear. It is hoped to have CEC advice shortly.
+
+
+ Do not plan long running activities (ie more than a year)
+ without an interim deliverable.
+
+
+ Numbering scheme:
+
+ In the past it was normal to adopt the following type of scheme
+ (note this is an illustration only) -
+
+
+ WP Task Deliverables
+
+
+ WP1
+ T1.1 D1.1.1, D1.1.2
+ T1.2 D1.2.1
+ WP2
+ T2.1 D2.1.1
+ T2.2 D2.2.1, D2.2.2
+ T2.3 D2.3.1
+ WP3
+ T3.1 D3.1.1, D3.1.2, D3.1.3
+ WP4
+ T4.1 D4.1.1
+ T4.2 D4.2.1, D4.2.2
+ T4.3 D4.3.1
+ T4.4 D4.4.1, D4.4.2, D4.4.3, D4.4.4
+
+
+ This type of numbering allows deliverables to be related to
+ Workpackages and Tasks and thus permits simpler tracking.
+
+
+ Project Management
+
+ Workpackage number WP1 Start date or starting event:
+ Participant id
+ Person-months per participant:
+
+
+ Objectives
+
+
+ Description of work
+
+ Deliverables
+
+ Milestones and expected result
+
+
+
+
+
+ Milestones are control points at which decisions are
+ needed; for example concerning which of several
+ technologies will be adopted as the basis for the next
+ phase of the project.
+
+
+ Workpackage number WP2 Start date or starting event:
+ Participant id
+ Person-months per participant:
+
+ Objectives
+
+
+ Description of work
+
+
+ Deliverables
+
+
+ Milestones and expected result
+
+B.7 Other issues
+
+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. See Annexes 3 and four of Proposers Guide
+for more information on Ethical Rules and Gender Dimension.
+
+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).
+
+B.7.1 Ethical Considerations
+
+
+ A. Proposers are requested to fill in the following table
+
+ Does your proposed research raise sensitive ethical YES NO
+ questions related to:
+
+ Human beings
+
+
+ Human biological samples
+
+
+ Personal data (whether identified by name or not)
+
+
+ Genetic information
+
+
+ Animals
+
+
+ B. Proposers are requested to confirm that the proposed research does
+ not involve:
+
+
+ Research activity aimed at human cloning for reproductive purposes,
+
+ Research activity intended to modify the genetic heritage of
+ human beings which could make such changes heritable12
+
+ Research activity intended to create human embryos solely for
+ the purpose of research or for the purpose of stem cell
+ procurement, including by means of somatic cell nuclear
+ transfer;
+
+ Research involving the use of human embryos or embryonic stem
+ cells with the exception of banked or isolated human embryonic
+ stem cells in culture13
+
+
+
+ 12 Research relating to cancer treatment of the gonads can be financed
+
+ 13 Applicants should note that the Council and the Commission
+ have agreed that detailed implementing provisions concerning
+ research activities involving the use of human embryos and
+ human embryonic stem cells which may be funded under the 6th
+ Framework Programme shall be established by 31 December 2003.
+ The Commission has stated that, during that
+ Confirmation : the proposed research involves none
+ of the issues listed in section B
+
+
+
+ Further information on ethics requirements and rules are given
+ at the science and ethics website at
+ http://europa.eu.int/comm/research/science-society/ethics/ethics_en.html.
+
+
+
+ B.7.2 Gender Issues
+
+
+ B.7.3 Safety Issues
+
+
+ B.7.4 Conservation Regulations
+
+
+
+ B.7.5 Other Policy related Issues
More information about the Pypy-commit
mailing list