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:
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.
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.
Title to Improvements and Delivered Materials Title to all improvements constructed at the Site vests instanter in the Board of Regents. Title to all materials vests in the Board of Regents upon their delivery without rejection by the Contractor at the Site, regardless of the status of payment or nonpayment of the costs thereto. Protection of laborers and Suppliers (regarding payment for services and materials) is effected through the provision of payment and performance bonds by the State.
License and Delivery a. Subject to Customer's compliance with the terms of this Agreement, including payment of fees, for any Software delivered to Customer, Licensor grants Customer a limited, non- transferable, non-sublicensable, non-exclusive license to install, run, and use the Number of Units of Software stated in an Order Form in accordance with the Documentation for the Term solely for Customer's internal business purposes. Maintenance, if purchased or provided, is delivered pursuant to the Order Form.
Scope of Work and Deliverables 9.1 Background and Scope
Objection Right for New Sub-processors Client may reasonably object to Data Processor’s use of a new Sub-processor for reasons related to the GDPR by notifying Data Processor promptly in writing within three (3) business days after receipt of Data Processor’s notice in accordance with the mechanism set out in Section 5.2 and such written objection shall include the reasons related to the GDPR for objecting to Data Processor’s use of such new Sub-processor. Failure to object to such new Sub-processor in writing within three (3) business days following Data Processor’s notice shall be deemed as acceptance of the new Sub-Processor. In the event Client reasonably objects to a new Sub-processor, as permitted in the preceding sentences, Data Processor will use reasonable efforts to make available to Client a change in the Services or recommend a commercially reasonable change to Client’s use of the Services to avoid Processing of Personal Data by the objected-to new Sub-processor without unreasonably burdening the Client. If Data Processor is unable to make available such change within a reasonable period of time, which shall not exceed thirty (30) days, Client may, as a sole remedy, terminate the applicable Agreement and this DPA with respect only to those Services which cannot be provided by Data Processor without the use of the objected- to new Sub-processor by providing written notice to Data Processor provided that all amounts due under the Agreement before the termination date with respect to the Processing at issue shall be duly paid to Data Processor. Until a decision is made regarding the new Sub-processor, Data Processor may temporarily suspend the Processing of the affected Personal Data. Client will have no further claims against Data Processor due to the termination of the Agreement (including, without limitation, requesting refunds) and/or the DPA in the situation described in this paragraph.
COMPLETION OF MEET AND NEGOTIATION 24.1 During the term of this Agreement, the Association expressly waives and relinquishes the right to meet and negotiate and agrees that the District shall not be obligated to meet and negotiate with respect to any subject or matter whether referred to or covered in this Agreement or not, even though each subject or matters may not have been within the knowledge or contemplation of either or both the District or the Association at the time they met and negotiated on and executed this Agreement, and even though such subjects or matters were proposed and later withdrawn.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
COMPLETION OF MEET AND NEGOTIATE During the term of this Agreement, the parties waive and relinquish the right to meet and negotiate except as provided below and elsewhere in this Agreement, and agree that they shall not be obligated to meet and negotiate with respect to any subject or matter referred to or covered in this Agreement, nor on those subjects or matters which were proposed by either party and later withdrawn. Negotiations may be reopened at any time on any section of this contract on petition of either party and with the concurrence of the second party.