Relationship to Project Agreements Sample Clauses

Relationship to Project Agreements. This Agreement is a Project Agreement and is subject to the full range of rights, exemptions, protections and Government guaranties as are provided in and appended to the Host Government Agreement.
AutoNDA by SimpleDocs

Related to Relationship to Project Agreements

  • Project Agreements Provided that where the company commences work on a project where a site agreement exists to which the company is contractually obligated or where a site agreement exists between the union and the client or their agent that provides for higher rates of pay and conditions, the conditions contained in any such site agreement will take precedence over this Agreement for the duration of the project.

  • Project Agreement (a) Subsequent to the establishment of a Cooperative Agreement pursuant to § 81.3, the Secretary may further agree with the States to provide xxxxx- cial assistance in the development and implementation of acceptable projects for the conservation of endangered and threatened species. Financial agree- ments will consist of an Application for Federal Assistance and a Project Agreement. Such agreements’ contin- ued existence, and continued financial assistance under such agreements, shall be contingent upon the continued existence of the Cooperative Agree- ment described in § 81.3 of this part.

  • Relationship to Other Agreements You agree that when you use Mobile Banking, you will remain subject to the terms and conditions of all your existing agreements with us or any service providers of yours; including service carrier or provider and that this Agreement does not amend or supersede any of those agreements. You understand that those agreements may provide for fees, limitations and restrictions which might impact your use of Mobile Banking (for example, your mobile service carrier or provider may impose data usage or text message charges for your use of or interaction with Mobile Banking, including while downloading the Software, receiving or sending Mobile Banking text messages, or other use of your Wireless device when using the Software or other products and services provided by Mobile Banking), and you agree to be solely responsible for all such fees, limitations and restrictions. You agree that only your mobile service carrier or provider is responsible for its products and services. Accordingly, you agree to resolve any problems with your carrier or provider directly with your carrier or provider without involving us. You also agree that if you have any problems with Mobile Banking, you will contact us directly.

  • Service Agreements Manager shall negotiate and execute on behalf of Owner such agreements which Manager deems necessary or advisable for the furnishing of utilities, services, concessions and supplies, for the maintenance, repair and operation of the Property and such other agreements which may benefit the Property or be incidental to the matters for which Manager is responsible hereunder.

  • Project contract 1. For each approved project a project contract shall be concluded between the Programme Operator and the Project Promoter.

  • Relationship with other agreements The implementation of this Treaty shall not prejudice obligations undertaken by States Parties with regard to existing international agreements, to which they are party, where those obligations are consistent with the Treaty.

  • Service Agreement Refers to the Contract, Purchase Order or Terms of Service or Terms of Use. Student Data: Student Data includes any data, whether gathered by Provider or provided by LEA or its users, students, or students’ parents/guardians, that is descriptive of the student including, but not limited to, information in the student’s educational record or email, first and last name, birthdate, home or other physical address, telephone number, email address, or other information allowing physical or online contact, discipline records, videos, test results, special education data, juvenile dependency records, grades, evaluations, criminal records, medical records, health records, social security numbers, biometric information, disabilities, socioeconomic information, individual purchasing behavior or preferences, food purchases, political affiliations, religious information, text messages, documents, student identifiers, search activity, photos, voice recordings, geolocation information, parents’ names, or any other information or identification number that would provide information about a specific student. Student Data includes Meta Data. Student Data further includes “Personally Identifiable Information (PII),” as defined in 34 C.F.R. § 99.3 and as defined under any applicable state law. Student Data shall constitute Education Records for the purposes of this DPA, and for the purposes of federal, state, and local laws and regulations. Student Data as specified in Exhibit “B” is confirmed to be collected or processed by the Provider pursuant to the Services. Student Data shall not constitute that information that has been anonymized or De-Identified, or anonymous usage data regarding a student’s use of Provider’s services.

  • Compliance Between Individual Contract and Master Agreement An individual contract between the Board and an individual employee, heretofore or hereafter executed, shall be subject to and consistent with the terms and conditions of this Agreement. If an individual contract contains any language inconsistent with this Agreement, this Agreement during its duration shall be controlling.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Agreements with Subcontractors Business Associate shall enter into a Business Associate Agreement with any Subcontractor to whom it provides PHI received from Covered Entity or created or received by Business Associate on behalf of Covered Entity in which the Subcontractor agrees to the same restrictions and conditions that apply through this Agreement to Business Associate with respect to such PHI. Business Associate must enter into this Business Associate Agreement before any use by or disclosure of PHI to such agent. The written agreement must identify Covered Entity as a direct and intended third party beneficiary with the right to enforce any breach of the agreement concerning the use or disclosure of PHI. Business Associate shall provide a copy of the Business Associate Agreement it enters into with a subcontractor to Covered Entity upon request. Business associate may not make any disclosure of PHI to any Subcontractor without prior written consent of Covered Entity.

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