ANNUAL OPERATING AGREEMENT Sample Clauses

ANNUAL OPERATING AGREEMENT. The Municipality and the Authority shall enter into an Annual Operating Agreement prescribed by regulation made pursuant to the British Columbia Transit Act.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
ANNUAL OPERATING AGREEMENT. The Operating Company covenants and agrees with BC Transit to perform each and every one of the conditions, terms, covenants and provisos contained in the Annual Operating Agreement, which on the part of the Operating Company are to be observed and performed.
Sample 1Sample 2Sample 3See All (4)
ANNUAL OPERATING AGREEMENT. 10 (1) The annual operating agreement shall include provisions respecting the following matters:
Sample 1Sample 2
ANNUAL OPERATING AGREEMENT. Subsequent to approval of funding, the Annual Operating Agreement will be consummated reflecting positions to be funded, service standards, and funding amounts for the term. The term of the agreement will be October 1, 2011 through September 30, 2012. This agreement will continue to be reviewed and updated annually for the ten year term of the Basic Affiliation Agreement. The Annual Operating Agreement will specify the following:
Sample 1
ANNUAL OPERATING AGREEMENT. 5.1 The parties shall on an annual basis execute an operating agreement governing scheduling of the parties’ respective year-round uses of the Howelsen Hill Ski Area, pricing for season and other Howelsen Hill Ski Area passes, planning for snowmaking, grooming, and other operations, the costs of services to be charged by the City, allocating the funds anticipated to be available for use at the Howelsen Hill Ski Area, and other operations issues. The parties shall also discuss joint fundraising and potential capital projects / campaigns relating to potential improvements at Howelsen Hill Ski Area and shall work together where appropriate to secure grant funding for relevant projects. The City shall consult with the Club regarding pricing, cost of services, and allocation of funds, but the City shall retain final decision making authority regarding those issues. Discussions regarding the annual operating agreement shall commence between the City Parks, Open Space, and Recreational Services Department and Club representatives no later than May 15 each year and be concluded by June 15 of each year. During that time, the Club will present a proposed event schedule for the coming year. The City acknowledges that the Club may not have a final list of winter athletic events until September 1st and agrees to work with the Club in good faith to accommodate athletic events that have not been identified until after May 15. If the parties’ representatives are unable to agree on a schedule, the matter shall be referred for final resolution to the City Council.
Sample 1

Related to ANNUAL OPERATING AGREEMENT

  • ANNUAL OPERATING PLAN Purchaser may be required to submit a written annual operating plan, as specified by, and at the request of the Forest Officer.

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

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

  • Lease Agreement On the terms stated in this Lease, Landlord leases the Premises to Tenant, and Tenant leases the Premises from Landlord, for the Term beginning on the Commencement Date and ending on the Termination Date unless extended or sooner terminated pursuant to this Lease.

  • Initial Operation The following requirements shall be satisfied prior to Initial Operation of the Customer Facility:

  • Rental Agreement All of the Roommates agree to be bound by all of the terms of the Rental Agreement.

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

  • Enterprise Agreement 1.1 This Enterprise Agreement is made pursuant to the Fair Work Act 1994, Chapter 3, Part 2.

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

  • Reaching Agreement When agreement is reached covering the areas under discussion, the proposed Agreement shall be reduced in writing as a memorandum of understanding and signed by a representative of each negotiating team. Agreement on individual items during the negotiations is binding only when all items are agreed upon. Procedures for ratification of the Agreement by the Association and the Board shall be completed within ten (10) school days after the conclusion of negotiations.

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