Implementation - 3.1 Deliverables

Instructions

Deliverables are the outcomes a project puts out for the Commission to review and evaluate. They are the smaller concrete results of the work done.

Deliverables can be:

• Document, report (excluding the periodic and final reports) (Code: R)
• Demonstrator, pilot, prototype, plan designs (Code: DEM)
• Websites, patents filing, press & media actions, videos, etc. (Code: DEC)
• Software, technical diagram, etc. (Code: OTHER)

Each deliverable also needs to define what the distribution level is:

• Public, fully open, e.g. web (Code: PU)
  • Each public deliverable is published as delivered publicly in the Commission CORDIS website.
• Confidential, restricted under conditions set out in Model Grant Agreement (Code: CO)
  • Only the project partners, the Commission relevant officials and the reviewers see the deliverable.
• Classified, information as referred to in Commission Decision 2001/844/EC. (Code: CI)
  • Special circumstances that only apply to Security restricted results.

Names of the deliverables should be specific to the work it showcases, and in WP descriptions their content must be clearly explained.

Delivery date refers to the month counting from beginning of the project when the deliverable is submitted to the Commission for review. Submission is done as a single PDF document, that can contain text, pictures, screenshots, code, etc.

Each Work Package lists the Work Package specific deliverables. The table 3.1c lists the deliverables in order of delivery dates, starting from the beginning of the project.

Deliverable numbering should follow the logic of <Work Package number>.<deliverable number>.

Note: Mandatory periodic or final reports to the Commission should not be counted or listed as deliverables.

Example

In Work Package table 3.1b:

D6.1 Project handbook (Lead: Company A), M01

The project handbook will contain the technology development roadmap with guidelines on specification, design, testing and integration of results. The handbook will also include a risk management plan. The handbook will be reviewed at each General Meeting and updated according to identified needs.

Table 3.1c: