Submitted deliverables Sample Clauses

Submitted deliverables. ‌ All deliverables expected in the second half of the Project were submitted by the PC to the EC within the due date, with one exception: D8.9, due by 30 June 2016, was submitted on 1 July 2016, due to a documented wrong behaviour of the Participant Portal, that on 30 June 2016 prevented the uploading. ID Title WP Lead beneficiary Type Dissemination level Due month Submission date D1.1 Project management plan WP1 LIUC Report Confidential 2 28.2.2015 D1.2 Consortium Agreement WP1 LIUC Report Confidential 2 28.2.2015 D1.3 Internal quality assurance plan WP1 LIUC Report Confidential 3 31.3.2015 D1.8 Informed consent procedures and recruitment criteria WP1 LIUC Report Public 3 31.3.2015 D8.1 Project website WP8 FKI Website Public 3 31.3.2015 D8.2 Dissemination and communication plan WP8 FKI Report Public 3 31.3.2015 D2.1 Options for the knowledge framework WP2 LIUC Report Public 4 30.4.2015 D2.2 Foundational interpretation of DiDIY WP2 LIUC Report Public 4 30.4.2015 D8.3 First online surveys WP8 FKI Website Public 5 31.5.2015 D2.3 Knowledge framework, initial version WP2 LIUC Report Public 6 30.6.2015 D4.1 Research space and agents WP4 ABACUS Report Public 6 30.6.2015 D4.2 Integration of background knowledge WP4 ABACUS Report Public 6 30.6.2015 D4.3 Methodological plan WP4 ABACUS Report Public 9 30.9.2015 Report D8.4 Current DiDIY support and awareness WP8 FKI Public 10 31.10.2015 in Europe
AutoNDA by SimpleDocs

Related to Submitted deliverables

  • Tasks and Deliverables A description of and the schedule for each task and deliverable, illustrated by a Xxxxx chart. Start and completion dates for each task, milestone, and deliverable shall be indicated. Must include deliverables specified in SOW-RFP as well as other deliverables that may be proposed by Contractor.

  • Reports and deliverables 1. The consortium shall submit a periodic report to the REA for each reporting period within 60 days after the end of each respective period. The report shall comprise:

  • Scope of Work and Deliverables 9.1 Background and Scope

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives.

  • Services and Deliverables The Services and the required Deliverables for the Services are specified below. SPID: Service outlet: MDS ID: Funding ID: Service Type Output Measure Quantity per annum Number of Service Users Funding amount per annum (excl. GST) $ $ $ Description of Services Funding amount one-off (excl. GST) $ Geographic Catchment Area: SPID: Service outlet: MDS ID: Funding ID: Service Type Output Measure Quantity per annum Number of Service Users Funding amount (excl. GST) $ $ $ Description of Services Funding amount one-off (excl. GST) $ Geographic Catchment Area: *Note: Refer to clause 4.3 in the Funding and Service Details about permitted variations in Output Quantities.

  • Contract Deliverables The Contractor shall provide information technology staff augmentation services, including comprehensive management of staff, as set forth in this Contract. The term “staff” refers to the temporary staff provided by the Contractor to render information technology services identified by Customers, but that staff shall not be deemed an employee of the State or deemed to be entitled to any benefits associated with such employment. Contracts resulting from this solicitation should not be structured as fixed-price agreements or used for any services requiring authorization for payment of milestone tasks. Contractor shall only provide information technology staff augmentation services for those Job Titles awarded to the Contractor and shall be paid on an hourly basis. The Department’s intent is for Contractor’s information technology staff to provide services closely related to those described in the Job Family Descriptions document. Detailed scopes of work, specific requirements of the work to be performed, and any requirements of staff shall be provided by the Customer in a Request for Quote. The Contractor shall possess the professional and technical staff necessary to allocate, outsource, and manage qualified information technology staff to perform the services requested by the Customer. The Contractor shall provide Customers with staff who must have sufficient skill and experience to perform the services assigned to them. All of the information technology staff augmentation services to be furnished by the Contractor under the Contract shall meet the professional standards and quality that prevails among information technology professionals in the same discipline and of similar knowledge and skill engaged in related work throughout Florida under the same or similar circumstances. The Contractor shall provide, at its own expense, training necessary for keeping Contractor’s staff abreast of industry advances and for maintaining proficiency in equipment and systems that are available on the commercial market. The Contractor shall be responsible for the administration and maintenance of all employment and payroll records, payroll processing, remittance of payroll and taxes, and all administrative tasks required by state and federal law associated with payment of staff. The Contractor shall, at its own expense, be responsible for adhering to the Contract background screening requirements, testing, evaluations, advertising, recruitment, and disciplinary actions of Contractor’s information technology staff. The Contractor shall maintain during the term of the Contract all licenses, permits, qualifications, insurance and approvals of whatever nature that are legally required to perform the information technology staff augmentation services.

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

Time is Money Join Law Insider Premium to draft better contracts faster.