PROJECT FUNDING AGREEMENT TEMPLATE Sample Clauses

PROJECT FUNDING AGREEMENT TEMPLATE. Project Funding Agreement Template Note: This project template is intended to be used to fund one-off projects or for the provision of services not ordinarily provided by the HSP. Whether or not the HSP provides the services directly or subcontracts the provision of the services to another provider, the HSP remains accountable for the funding that is provided by the LHIN. THIS PROJECT FUNDING AGREEMENT (“PFA”) is effective as of [insert date] (the “Effective Date”) between: XXX LOCAL HEALTH INTEGRATION NETWORK (the “LHIN”) - and - [Legal Name of the Health Service Provider] (the “HSP”)
AutoNDA by SimpleDocs
PROJECT FUNDING AGREEMENT TEMPLATE. Project Funding Agreement Template Note: This project template is intended to be used to fund one-off projects or for the provision of services not ordinarily provided by the HSP. Whether or not the HSP provides the services directly or subcontracts the provision of the services to another provider, the HSP remains accountable for the funding that is provided by the LHIN. THIS PROJECT FUNDING AGREEMENT (“PFA”) is effective as of March 31, 2014 (the “Effective Date”) between: CENTRAL WEST LOCAL HEALTH INTEGRATION NETWORK (the “LHIN”) - and - Brampton Meals on Wheels (the “HSP”)
PROJECT FUNDING AGREEMENT TEMPLATE. HSP’s Representative has authority to legally bind the HSP.
PROJECT FUNDING AGREEMENT TEMPLATE. Project Funding Agreement Template Note: This project template is intended to be used to fund one-off projects or for the provision of services not ordinarily provided by the HSP. Whether or not the HSP provides the services directly or subcontracts the provision of the services to another provider, the HSP remains accountable for the funding that is provided by the LHIN. THIS PROJECT FUNDING AGREEMENT (“PFA”) is effective as of March 31, 2014 (the “Effective Date”) between: CENTRAL WEST LOCAL HEALTH INTEGRATION NETWORK (the “LHIN”) - and - Family Transition Place (the “HSP”)
PROJECT FUNDING AGREEMENT TEMPLATE. Project Funding Agreement Template Note: This project template is intended to be used to fund one-off projects or for the provision of services not ordinarily provided by the HSP. Whether or not the HSP provides the services directly or subcontracts the provision of the services to another provider, the HSP remains accountable for the funding that is provided by the LHIN. THIS PROJECT FUNDING AGREEMENT (“PFA”) is effective as of March 31, 2014 (the “Effective Date”) between: CENTRAL WEST LOCAL HEALTH INTEGRATION NETWORK (the “LHIN”) - and – Corporation of the County of Dufferin (the “HSP”)

Related to PROJECT FUNDING AGREEMENT TEMPLATE

  • Schedule for Completing Agreement Closeout Activities Provide All Draft and Final Written Products on a CD-ROM or USB memory stick, organized by the tasks in the Agreement. Products: • Final Meeting Agreement Summary (if applicable) • Schedule for Completing Agreement Closeout Activities • All Draft and Final Written Products

  • CONTRACTOR’S SUBMISSION OF CONTRACT MODIFICATIONS In connection with any Contract modification, OGS reserves the right to:  request additional information  reject Contract modifications  remove Products from Contract modification requests  request additional discounts for new or existing Products

  • TIPS Sales and Supplemental Agreements If awarded, when making a sale under this awarded contract, the terms of the specific TIPS order, including but not limited to: shipping, freight, insurance, delivery, fees, bonding, cost, delivery expectations and location, returns, refunds, terms, conditions, cancellations, defects, order assistance, etc., shall be controlled by the purchase agreement (Purchase Order, Contract, AIA Contract, Invoice, etc.) (“Supplemental Agreement” as used herein) entered into between the TIPS Member Customer and Vendor only. TIPS is not a party to any Supplemental Agreement. All Supplemental Agreements shall include Vendor’s Name, as known to TIPS, and TIPS Contract Name and Number. Vendor accepts and understands that TIPS is not a legal party to TIPS Sales and Vendor is solely responsible for identifying fraud, mistakes, unacceptable terms, or misrepresentations for the specific order prior to accepting. Vendor agrees that any order issued from a customer to Vendor, even when processed through TIPS, constitutes a legal contract between the customer and Vendor only. When Vendor accepts or fulfills an order, even when processed through TIPS, Vendor is representing that Vendor has carefully reviewed the order for legality, authenticity, and accuracy and TIPS shall not be liable or responsible for the same. In the event of a conflict between the terms of this TIPS Vendor Agreement and those contained in any Supplemental Agreement, the provisions set forth herein shall control unless otherwise agreed to and authorized by the Parties in writing within the Supplemental Agreement. The Supplemental Agreement shall dictate the scope of services, the project delivery expectations, the scheduling of projects and milestones, the support requirements, and all other terms applicable to the specific sale(s) between the Vendor and the TIPS Member.

  • INTENT OF CONTRACT DOCUMENTS 1.1 It is the intent of the Contract Documents to describe a functionally complete Project (or portion thereof) to be constructed in accordance with the Contract Documents. Any work, materials or equipment that may reasonably be inferred from the Contract Documents as being required to produce the intended result shall be supplied whether or not specifically called for. When words which have a well-known technical or trade meaning are used to describe work, materials or equipment, such words shall be interpreted in accordance with that meaning. Reference to standard specifications, manuals or codes of any technical society, organization or association or to the laws or regulations of any governmental authority having jurisdiction over the Project, whether such reference be specific or by implication, shall mean the latest standard specification, manual, code, law or regulation in effect at the time the Work is performed, except as may be otherwise specifically stated herein.

  • AMENDING OPERATING AGREEMENT This Agreement may only be amended by an affirmative vote or consent of all Members.

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

  • Operating Agreement You haves received and read a copy of the Company’s Operating Agreement (the “Operating Agreement”) and agree that your execution of this Agreement constitutes your consent to and execution of the Operating Agreement, and, that upon acceptance of this Agreement by the Company, you will become a member of the Company as a holder of Shares. When this Agreement is countersigned by the Company, the Operating Agreement shall be binding upon you as of the closing date.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Modifications and Updates to the Wire Center List and Subsequent Transition Periods 2.1.4.12.1 In the event BellSouth identifies additional wire centers that meet the criteria set forth in Section 2.1.4.5, but that were not included in the Initial Wire Center List, BellSouth shall include such additional wire centers in a carrier notification letter (CNL). Each such list of additional wire centers shall be considered a “Subsequent Wire Center List”.

  • Contract Closure Contracting Officer shall give appropriate written notice to Purchaser when Purchaser has complied with the terms of this contract. Purchaser shall be paid refunds due from Timber Sale Account un- der B4.24 and excess cooperative deposits under B4.218.

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