WT2 list of deliverables Sample Clauses

WT2 list of deliverables. Deliverable Number14 Deliverable Title WP number9 Lead beneficiary Type15 Dissemination level16 Due Date (in months)17 D1.1 Preliminary Data Management Plan WP1 1 - UPEM Report Public 6 D1.2 Data Management Plan 1st full version WP1 1 - UPEM ORDP: Open Research Data Pilot Public 24 D1.3 Data Management Plan 2nd full version WP1 1 - UPEM ORDP: Open Research Data Pilot Public 42 D2.1 Website and materials WP2 4 - CNR Websites, patents filling, etc. Public 12 D2.2 First Report on activities developed for training, communication and interactions with users & stakeholders WP2 4 - CNR Report Public 18 D2.3 Analysis of users’ needs WP2 4 - CNR Report Public 24 D2.4 Report on Press and media actions WP2 4 - CNR Report Public 30 D2.5 Second Report on activities developed for training, communication and interactions with users & stakeholders WP2 4 - CNR Report Public 36 D2.6 Policy Brief on achievements and lessons learned WP2 4 - CNR Report Public 46 D3.1 Report on options for the future by the SWG WP3 1 - UPEM Report Confidential, only for members of the consortium (including the Commission Services) 30 D3.2 Plan for the future WP3 1 - UPEM Report Public 42 D3.3 Report on indirect contract approach WP3 1 - UPEM Report Confidential, only for members of the consortium (including the Commission Services) 18 Deliverable Number14 Deliverable Title WP number9 Lead beneficiary Type15 Dissemination level16 Due Date (in months)17 D4.1 Joint-Opening of RCF beta version WP4 1 - UPEM Websites, patents filling, etc. Public 18 D4.2 Opening of Open Data VRE WP4 4 - CNR Websites, patents filling, etc. Public 18 D4.3 Frontend to access and navigate datasets WP4 1 - UPEM Websites, patents filling, etc. Public 18 D4.4 Access to core Risis services WP4 1 - UPEM Websites, patents filling, etc. Public 18 D4.5 Opening RCF data and services including external services linkage and VRE WP4 1 - UPEM Websites, patents filling, etc. Public 36 D4.6 Usage Monitoring and infrastructure documentation WP4 1 - UPEM Report Public 46 D5.1 Consolidated work plan on Maintenance WP5 2 - AIT Report Public 6 D5.2 First interim report on Maintenance of RISIS core datasets WP5 2 - AIT Report Public 18 D5.3 Second interim report on Maintenance of core RISIS datasets WP5 2 - AIT Report Public 36 D5.4 Final report on Maintenance of core RISIS datasets WP5 2 - AIT Report Public 46 D6.1 Consolidated report on the new services opened (based upon corresponding milestones) WP6 6 - USFD Other Public 18 D6.2 First re...
Sample 1See All (5)
AutoNDA by SimpleDocs
WT2 list of deliverables. Deliverable Number14 Deliverable Title WP number9 Lead beneficiary Type15 Dissemination level16 Due Date (in months)17 D1.1 Dissemination WP1 1 - GANIL Report Public 12
Sample 1Sample 2Sample 3
WT2 list of deliverables. Deliverable Number14 Deliverable Title WP number9 Lead beneficiary Type15 Dissemination level16 Due Date (in months)17 D1.1 Short annual progress reports to the consortium 2019 WP1 1 - RCN Report Confidential, only for members of the consortium (including the Commission Services) 12 D1.2 Short annual progress reports to the consortium 2020 WP1 1 - RCN Report Confidential, only for members of the consortium (including the Commission Services) 24 D1.3 Short annual progress reports to the consortium 2021 WP1 1 - RCN Report Confidential, only for members of the consortium (including the Commission Services) 36 D1.4 Short annual progress reports to the consortium 2022 WP1 1 - RCN Report Confidential, only for members of the consortium (including the Commission Services) 48 D1.5 Report on cumulative expenses incurred (M12) WP1 1 - RCN Report Confidential, only for members of the consortium (including the Commission Services) 12 D1.6 Report on cumulative expenses incurred (M24) WP1 1 - RCN Report Confidential, only for members of the consortium (including the Commission Services) 24 D1.7 Report on cumulative expenses incurred (M36) WP1 1 - RCN Report Confidential, only for members of the consortium (including the Commission Services) 36 D1.8 Report on cumulative expenses incurred (M48) WP1 1 - RCN Report Confidential, only for members of the consortium (including the Commission Services) 48 Deliverable Number14 Deliverable Title WP number9 Lead beneficiary Type15 Dissemination level16 Due Date (in months)17 D1.9 Report on cumulative expenses incurred (M60) WP1 1 - RCN Report Confidential, only for members of the consortium (including the Commission Services) 60 D1.10 Progress report to the Commission WP1 1 - RCN Report Confidential, only for members of the consortium (including the Commission Services) 36 D2.1 Call documents – cofounded call WP2 12 - JÜLICH Report Confidential, only for members of the consortium (including the Commission Services) 1 D3.1 Ranking list and report from the pre-proposal evaluation WP3 24 - UEFISCDI Report Confidential, only for members of the consortium (including the Commission Services) 11 D3.2 Ranking list and report from the full proposal evaluation WP3 24 - UEFISCDI Report Confidential, only for members of the consortium (including the Commission Services) 14 D3.3 Joint selection list and report of the projects to be funded WP3 24 - UEFISCDI Report Confidential, only for members of the consortium (including the Commission Servic...
Sample 1
WT2 list of deliverables. Deliverable Number14 Deliverable Title WP number9 Lead beneficiary Type15 Dissemination level16 Due Date (in months)17 D1.1 Activity 1 - Progress Technical Report WP1 1 - CAC Report Confidential, only for members of the consortium (including the Commission Services) 13 D1.2 Activity 1 - Final Technical Report WP1 1 - CAC Report Confidential, only for members of the consortium (including the Commission Services) 24 D2.1 Activity 2 - Progress Technical Report WP2 2 - ITC Report Confidential, only for members of the consortium (including the Commission Services) 13 D2.2 Activity 2 - Final Technical Report WP2 2 - ITC Report Confidential, only for members of the consortium (including the Commission Services) 24 D3.1 Activity 3 - Progress Technical Report WP3 1 - CAC Report Confidential, only for members of the consortium (including the Commission Services) 13 D3.2 Activity 3 - Final Technical Report WP3 1 - CAC Report Confidential, only for members of the consortium (including the Commission Services) 24 D4.1 Updated communication strategy and work plan (due in month 3) WP4 1 - CAC Report Confidential, only for members of the consortium (including the Commission Services) 3 D4.2 Updated communication strategy and work plan (due in month 15) WP4 1 - CAC Report Confidential, only for members of the consortium (including the Commission Services) 15
Sample 1
WT2 list of deliverables. Deliverable Number14 Deliverable Title WP number9 Lead beneficiary Type15 Dissemination level16 Due Date (in months)17 D1.1 Activity 1 – Final Technical Report WP1 1 - CAC Report Confidential, only for members of the consortium (including the Commission Services) 12 D2.1 Activity 2 – Final Technical Report WP2 2 - ITC Report Confidential, only for members of the consortium (including the Commission Services) 12 D3.1 Activity 3 – Final Technical Report WP3 1 - CAC Report Confidential, only for members of the consortium (including the Commission Services) 12 D4.1 Communication strategy and work plan WP4 1 - CAC Report Confidential, only for members of the consortium (including the Commission Services) 3 D4.2 Activity 5 – Final Technical Report WP4 1 - CAC Report Confidential, only for members of the consortium (including the Commission Services) 12
Sample 1

Related to WT2 list of deliverables

  • Description of Deliverables The Contractor shall Perform as set forth in Exhibit A.

  • 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.

  • 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.

  • Acceptance of Deliverables The State’s Project Manager shall be responsible for the sign-off acceptance of all Deliverables required and performed/submitted pursuant to this Agreement. Upon successful completion of a Deliverable, Contractor shall provide the State’s Project Manager with a completed Acceptance and Signoff Form (Exhibit E). The State’s Project Manager will apply the standards established in Exhibit D and the acceptance criteria set forth in subparagraph B of this article, as appropriate, to determine the acceptability of the Deliverable provided by Contractor. If the State’s Project Manager rejects the Deliverable, the parties agree to any dispute(s) resulting from such rejection(s) will be resolved as set forth in this article. Acceptance Criteria for Deliverables (“Criteria”) provided by Contractor pursuant to this Agreement include: Timeliness: The Work was provided on time; according to schedule; Completeness: The Deliverable contained all of the, Data, Materials, and features required by the Agreement; and Technical accuracy: The Deliverable complied with the standards of this Agreement, or, if this Agreement lacks a standard for provision of the Work, the currently generally accepted industry standard. Contractor shall provide the Deliverable to the State, in accordance with direction from the Project Manager and as provided for in Exhibit D. The State shall accept the Deliverable, provided that Contractor has delivered the Deliverable in accordance with the Criteria. The State’s Project Manager shall assign the Acceptance and Signoff Form to notify Contractor of the Deliverable’s acceptability. If the State rejects the Deliverable provided, the State’s Project Manager shall submit to Contractor’s Project Manager a written rejection describing in detail the failure of the Deliverable as measured against the Criteria. If the State rejects the Deliverable, then Contractor shall have a period of ten (10) Business Days from receipt of the Notice of rejection to correct the stated failure(s) to conform to the Criteria.

  • Closing Deliverables (a) At the Closing, Seller shall deliver to Buyer the following:

  • Post-Closing Deliverables On or before the Closing Date, the applicable Seller shall deliver to Buyer the following:

  • 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.

  • Drug-Free Workplace Certification As required by Executive Order No. 90-5 dated April 12, 1990, issued by the Governor of Indiana, the Contractor hereby covenants and agrees to make a good faith effort to provide and maintain a drug-free workplace. The Contractor will give written notice to the State within ten (10) days after receiving actual notice that the Contractor, or an employee of the Contractor in the State of Indiana, has been convicted of a criminal drug violation occurring in the workplace. False certification or violation of this certification may result in sanctions including, but not limited to, suspension of contract payments, termination of this Contract and/or debarment of contracting opportunities with the State for up to three (3) years. In addition to the provisions of the above paragraph, if the total amount set forth in this Contract is in excess of $25,000.00, the Contractor certifies and agrees that it will provide a drug-free workplace by:

  • SERVICE DELIVERABLES You will receive service on the Covered Product as described below: Carry-In: Unless otherwise provided in this Agreement, the Covered Product must be shipped or delivered and retrieved by You at Our authorized service center during normal business hours. In-Home/On-Site: Service will be performed in Your home or on-site as indicated on the Declarations Page of this Agreement, or on Your sales receipt or invoice provided You have fulfilled the following requirements: (1) provide Our authorized technician with accessibility to the Covered Product; (2) provide a non-threatening and safe environment for Our authorized technician; and (3) an adult over the age of 18 must be present for the period of time Our authorized technician is scheduled to provide service and while Our authorized technician is on Your property servicing the Covered Product. In-Home Service will be provided by Our authorized service provider during regular business hours, local time, Monday through Friday, except holidays. Our authorized service center may opt to remove the Covered Product to perform service in-shop. The Covered Product will be returned upon completion. Additional time and mileage charges for in-home repairs outside of twenty-five (25) contiguous land miles or the normal service radius of Our authorized service center are not covered by this Agreement, and are Your responsibility.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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