|
|
| Line 6: |
Line 6: |
| | | | |
| | *'''(a) Rationale and structure of your work programme:''' Explain briefly the rationale and structure of the work programme: main phases of the action, logics and links between work packages. | | *'''(a) Rationale and structure of your work programme:''' Explain briefly the rationale and structure of the work programme: main phases of the action, logics and links between work packages. |
| | + | |
| | + | |
| | | | |
| | *'''(b) Flow chart of your work programme:''' Provide a flow chart, showing the logic of your work | | *'''(b) Flow chart of your work programme:''' Provide a flow chart, showing the logic of your work |
| | programme. | | programme. |
| − |
| |
| − | ==='''7.2 Work Packages'''===
| |
| − |
| |
| − | ''This will be a critical part of your proposal, describing your planned activities. You will need to break them into work packages. Work packages represent major, natural packages of your proposed action. The size should be about 3-5 pages per Work Package.''
| |
| − |
| |
| − | There are specific previsions for the three mandatory wps:
| |
| − | *'''Work Package N° 1 Management:''' consortium management, including consortium meetings, monitoring and evaluation of progress/results and reporting;
| |
| − |
| |
| − | *'''Work Package N° n-1 Communication activities:''' covers the specific communication activities in your proposal;
| |
| − |
| |
| − | *'''Work Package N° n EACI dissemination activities:''' covers specific requests from the EACI and pre-defined standard activities for all IEE actions
| |
| − |
| |
| − | '''! Important notes:'''
| |
| − |
| |
| − | *The number of work packages used must match the complexity of the work and the overall value of
| |
| − | the proposed action. It is standard to have between 5 and 10 work packages. Do not exceed 10 work
| |
| − | packages.
| |
| − |
| |
| − | *Within each work package, illustrate the main tasks needed to reach the objectives of the proposal,
| |
| − | describe the tasks with sufficient detail.
| |
| − |
| |
| − | *When designing the work packages, keep in mind your target groups, key actors and the European
| |
| − | added value – how is this translated into tasks and outputs in your work programme?
| |
| − |
| |
| − | *The description of the work packages should be sufficiently detailed to justify the proposed effort
| |
| − | and allow progress monitoring. Mind the consistency with the level of effort proposed in your
| |
| − | budget (person hours).
| |
| − |
| |
| − | *Outputs should be consistent with the tasks – and vice versa!
| |
| − |
| |
| − | *Work packages must show how the tasks are distributed amongst the partners. Note that it is
| |
| − | recommended to allocate responsibility for leading the work packages to different partners of your
| |
| − | consortium, relevant to their competence.
| |
| − |
| |
| − | *"Major subcontracts" are services that you intend to acquire in the course of the action and which
| |
| − | are critical in terms of (technical) input and/or in terms of budgetary volume. Those should be
| |
| − | shortly described.
| |
| − |
| |
| − | ==='''7.3 Overview of Deliverables'''===
| |
| − |
| |
| − | ''List the deliverables of each work package in the following summary table. They should be identical with those in the work packages and vice versa. Provide here the appropriate key (descriptive) information for each deliverable.''
| |
| − |
| |
| − |
| |
| − | '''Important note on deliverables:'''
| |
| − |
| |
| − | * Limit the number of deliverables and do not include minor sub-items (such as invitations to workshops) or internal working papers (such as internal coordination reports). Similar deliverables for several countries should be grouped, where appropriate.
| |
| − |
| |
| − | * A Publishable Result-Oriented Report is required. This report is the main document to inform the target groups about the achievements of the action. It presents results, lessons learnt and impacts.
| |
| − |
| |
| − | * Concerning the dissemination level, it is expected that all deliverables will be publicly available and free of charge for potential users. If appropriate, the dissemination of some deliverables could be limited to a target group, but please justify. Should you wish exceptionally to define a deliverable as confidential, you must provide a justification. In exceptional cases, deliverables can be offered for sale but it must be clearly justified. Revenues must be budgeted and by no means may the action generate profit. Justifications are to be given in the relevant work package.
| |
| − |
| |
| − | * The table "Overview of deliverables" and the "Schedule" must indicate the month of completion of the deliverable; for public deliverables (PU) this should coincide with their availability e.g. for distribution via the website/mail shot/press releases etc.
| |
| − |
| |
| − | * Note that the technical progress reports (PR), interim reports (IR) or final reports (FR) for the EACI, as well as deliverables from the EACI Dissemination Activities, do not need to be included in the List of Deliverables.
| |
| − |
| |
| − | ==='''7.4. Schedule of activities'''===
| |
| − |
| |
| − | * Show the time schedule for your action - adapting the template below to your needs (here an example for a 30-month action). Take into account that the maximum duration is 36 months.
| |
| − | * Do not use anything other than “month 1, month 2, etc.”, e.g. do not use fixed dates such as June 2012, January 2013.
| |
| − | * Break down the planning of the work packages on the level of tasks, in order to make this chart meaningful.
| |
| − | * Schedule carefully and foresee sufficient time towards the end of the action to effectively disseminate and transfer your results.
| |
