PROJECT AND PARTIES Sample Clauses

PROJECT AND PARTIES. DEED OF FUNDING The Recipient has applied and been approved for a funding grant from the Community Environment Fund, administered by the Ministry. The grant is subject to the terms of this Deed of funding. This Deed is made up of the following parts: Part A: Project and Parties Part B: Special Terms Part C: General Terms Any Schedules and Annexures attached to this Deed or incorporated by reference. RECIPIENT Full legal name: Trading name (if different): DEED NUMBER [generated by MfE] DURATION Commencement date: [ ] or the date this deed is executed; whichever is later. Completion date: [project’s end date – e.g. due date of last project deliverable]
Sample 1
AutoNDA by SimpleDocs

Related to PROJECT AND PARTIES

  • Agents and Subcontractors The MCP, in compliance with 45 CFR 164.502(e)(1)(ii) and 164.308(b)(2) as applicable, shall ensure all its agents and subcontractors that create, receive, maintain, or transmit PHI from or on behalf of the MCP and/or ODM agree to have, in a written agreement, the same restrictions, conditions, and requirements that apply to the MCP with respect to the use or disclosure of PHI.

  • Contractor Parties A Contractor’s members, directors, officers, shareholders, partners, managers, principal officers, representatives, agents, servants, consultants, employees or any one of them or any other person or entity with whom the Contractor is in privity of oral or written contract and the Contractor intends for such other person or entity to Perform under the Contract in any capacity.

  • Contractor’s Project Manager and Key Personnel Contractor shall appoint a Project Manager to direct the Contractor’s efforts in fulfilling Contractor’s obligations under this Contract. This Project Manager shall be subject to approval by the County and shall not be changed without the written consent of the County’s Project Manager, which consent shall not be unreasonably withheld. The Contractor’s Project Manager shall be assigned to this project for the duration of the Contract and shall diligently pursue all work and services to meet the project time lines. The County’s Project Manager shall have the right to require the removal and replacement of the Contractor’s Project Manager from providing services to the County under this Contract. The County’s Project manager shall notify the Contractor in writing of such action. The Contractor shall accomplish the removal within five (5) business days after written notice by the County’s Project Manager. The County’s Project Manager shall review and approve the appointment of the replacement for the Contractor’s Project Manager. The County is not required to provide any additional information, reason or rationale in the event it The County is not required to provide any additional information, reason or rationale in the event it requires the removal of Contractor’s Project Manager from providing further services under the Contract.

  • CONTRACTOR's Agents and Subcontractors To impose the same restrictions and conditions set forth in this Personal Information and Security Contract on any subcontractors or other agents with whom CONTRACTOR subcontracts any activities under the Agreement that involve the disclosure of DHCS PI or PII to such subcontractors or other agents.

  • Parties This Agreement shall each inure to the benefit of and be binding upon the Underwriters and the Company and their respective successors. Nothing expressed or mentioned in this Agreement is intended or shall be construed to give any person, firm or corporation, other than the Underwriters and the Company and their respective successors and the controlling persons and officers and directors referred to in Sections 6 and 7 and their heirs and legal representatives, any legal or equitable right, remedy or claim under or in respect of this Agreement or any provision herein contained. This Agreement and all conditions and provisions hereof are intended to be for the sole and exclusive benefit of the Underwriters and the Company and their respective successors, and said controlling persons and officers and directors and their heirs and legal representatives, and for the benefit of no other person, firm or corporation. No purchaser of Securities from any Underwriter shall be deemed to be a successor by reason merely of such purchase.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • Contracting Parties The Government customer (Licensee) is the “Ordering Activity”, “defined as an entity authorized to order under GSA contracts as set forth in GSA ORDER 4800.2G ADM, as may be revised from time to time. The Licensee cannot be an individual because any implication of individual licensing triggers the requirements for legal review by Federal Employee unions. Conversely, because of competition rules, the contractor must be defined as a single entity even if the contractor is part of a corporate group. The Government cannot contract with the group, or in the alternative with a set of contracting parties.

  • MCUA PARTIES Any of the following types of entities that have executed a Master Contract Usage Agreement with Enterprise Services: ▪ Political subdivisions (e.g., counties, cities, school districts, public utility districts) in the State of Washington; ▪ Federal governmental agencies or entities; ▪ Public-benefit nonprofit corporations (i.e., § 501(c)(3) nonprofit corporations that receive federal, state, or local funding); and ▪ Federally-recognized Indian Tribes located in the State of Washington.

  • Project Information Except for confidential information designated by the City as information not to be shared, Consultant agrees to share Project information with, and to fully cooperate with, those corporations, firms, contractors, public utilities, governmental entities, and persons involved in or associated with the Project. No information, news, or press releases related to the Project, whether made to representatives of newspapers, magazines, or television and radio stations, shall be made without the written authorization of the City’s Project Manager.

  • Parties’ Representatives Both Parties shall ensure that throughout the term of this Agreement, a duly appointed Representative is available for communications between the Parties. The Representatives shall have full authority to deal with all day-to-day matters arising under this Agreement. If a Party’s Representative becomes unavailable, the Party shall promptly appoint another Representative. Acts and omissions of Representatives shall be deemed to be acts and omissions of the Party. Owner and CAISO shall be entitled to assume that the Representative of the other Party is at all times acting within the limits of the authority given by the Representative’s Party. Owner’s Representatives and CAISO’s Representatives shall be identified on Schedule J.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!