Other Wikis
- EC Internal Users
- EC Internal Users
Page History
...
Contractual deliverables are defined during the preparation of the Contract (or Request for Service in the case of Specific Contracts under Framework Contracts). Following the awarding and the signature by both parties (Framework i.e. Contractor and Contracting Authority) of the Specific Contract, the Contracting Authority (following a prior agreement with the Contractor) sets the effective start date of the Contract in the system, and the implementation of the Contract begins.
OPSYS automatically updates the contractual deliverables (as defined with their indicative due dates during the preparation of the Request for Servicecontract preparation or request) with their effective due dates once the effective start date of the Contract is known.
| Note |
|---|
Please note that the system will generate as many placeholders as deliverable types and periodicities required in the Deliverable Submission section of the Request for Servicecontract preparation or request. |
The Contractor uploads and submits the required contractual deliverables, by the effective due dates and following the schedule of the Contract accessible in the Funding & Tenders Portal. The deliverables can then be commented and/or validated by the Contracting Authority. The Contractor has the sole responsibility to deliver the required deliverable(s), or in the case of a Consortium, this responsibility lies with the Consortium Leader. The Contractor must also ensure a quality control of the required outputs, before delivering them.
...
Deliverables are contractual, as they are defined at the level of the preparation of the Contract or Request for Service, and form an integral part of the execution of the Contract. The For Framework Contracts, the required deliverables are generally identified at the level of the Framework Contract, but are distinctly detailed in the specific ToRs for the individual assignment.
Deliverables must therefore be defined for each specific assignment, are encoded in OPSYS by the Contracting Authority during the preparation of the Contract or Request for ServicesService, and their effective management is a requirement for the good execution of the Specific Contract.
| Div | ||
|---|---|---|
| ||
Each assignment may require multiple deliverables, each characterised by type (e.g. report, data set, document, assessment, study, etc.), by language, by periodicity (once or intermediary – interim), period delimiter (amount of day(s), month(s) week(s), year(s)), and by defining point of implementation (start of project, end of project). For example, Inception Report within 7 Day(s) from the project starting date. |
...
Following the e-signatures of the Specific Contract, the Contracting Authority sets the effective start date of the project in OPSYS. There is no deadline in the system to set the effective start date, and it should be done after the confirmation of the effective starting date of the project date by the Contractor.
...
The effective start date of the Specific Contract is also the principal reference date, from which the system can calculate the end date of the project, and schedule the deadlines and/or periodicity of the contractual deliverables set during the preparation of the Contract or Request for Services Service with respect to the reference date(s).
...
If the Final Progress Report is not approved (where applicable), the dispute settlement procedure is automatically invoked.
...
Overview
Content Tools
Apps