Obligation to keep minutes. (a) The corporation must keep minute books in which it records within 1 month:
Obligation to keep minutes Sample Clauses
Related to Obligation to keep minutes
OBLIGATION TO SERVE As between the Parties, Competitive Supplier has the sole obligation to obtain sources of supply, whether from generating facilities owned or controlled by its affiliates, through bilateral transactions, or the market, as may be necessary to provide All-Requirements Power Supply for all of the Participating Consumers under the Program. Competitive Supplier, except as explicitly limited by the terms included in Exhibit A, shall be obligated to accept all Participating Consumers, regardless of their location or energy needs, subject to Competitive Supplier’s standard credit policies (to the extent permitted by law), Article 5.5 hereof, Exhibit A hereof and the terms of any approval or other order of the Department with respect to this ESA.
OBLIGATION TO NEGOTIATE 50.01 The Employer and the Union acknowledge that during negotiations which preceded this Agreement, each had the unlimited right and opportunity to make demands and proposals with respect to any subject or matter not removed by law from the area of collective bargaining/negotiations and that the understandings and agreements arrived at by the parties after the exercise of that right and opportunity are set forth in this Agreement.
OBLIGATION TO SUPPORT The parties agree that subsequent to the execution of this Memorandum of Understanding and during the period of time said Memorandum is pending before the Board of Supervisors for action, neither SEIU Local 721, nor Management, nor their authorized representatives, will appear before the Board of Supervisors or meet with members of the Board of Supervisors individually to advocate any amendment, addition or deletion to the terms and conditions of this Memorandum of Understanding. It is further understood that this Article shall not preclude the parties from appearing before the Board of Supervisors nor meeting with individual members of the Board of Supervisors to advocate or urge the adoption and approval of this Memorandum of Understanding in its entirety.
APPLICANT’S OBLIGATION TO MAINTAIN VIABLE PRESENCE In order to receive and maintain the limitation authorized by Section 2.4 in addition to the other obligations required by this Agreement, the Applicant shall Maintain Viable Presence in the District commencing at the start of the Tax Limitation Period through the Final Termination Date of this Agreement. Notwithstanding anything contained in this Agreement to the contrary, the Applicant shall not be in breach of, and shall not be subject to any liability for failure to Maintain Viable Presence to the extent such failure is caused by Force Majeure, provided the Applicant makes commercially reasonable efforts to remedy the cause of such Force Majeure.
Obligations of Registry Operator to TLD Community Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-‐based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto.
Obligation to Make Payments Any Interconnection Party's obligation to make payments for services shall not be suspended by Force Majeure.
Exception to Obligations Neither Party's obligations under this Section shall apply to the extent the infringement is caused by: (i) modification of the facilities or equipment (including software) by the indemnitee; (ii) use by the indemnitee of the facilities or equipment (including software) in combination with equipment or facilities (including software) not provided or authorized by the indemnitor, provided the facilities or equipment (including software) would not be infringing if used alone; (iii) conformance to specifications of the indemnitee which would necessarily result in infringement; or (iv) continued use by the indemnitee of the affected facilities or equipment (including software) after being placed on notice to discontinue use as set forth herein.
Notification to Union The Hospital will provide the union with a list, monthly of all hirings, lay-offs, recalls and terminations within the bargaining unit where such information is available or becomes readily available through the Hospital's payroll system."
Developer Obligations In accordance with applicable NYISO requirements, Developer shall maintain satisfactory operating communications with Connecting Transmission Owner and NYISO. Developer shall provide standard voice line, dedicated voice line and facsimile communications at its Large Generating Facility control room or central dispatch facility through use of either the public telephone system, or a voice communications system that does not rely on the public telephone system. Developer shall also provide the dedicated data circuit(s) necessary to provide Developer data to Connecting Transmission Owner and NYISO as set forth in Appendix D hereto. The data circuit(s) shall extend from the Large Generating Facility to the location(s) specified by Connecting Transmission Owner and NYISO. Any required maintenance of such communications equipment shall be performed by Developer. Operational communications shall be activated and maintained under, but not be limited to, the following events: system paralleling or separation, scheduled and unscheduled shutdowns, equipment clearances, and hourly and daily load data.
COUNCIL’S OBLIGATIONS Save as otherwise expressly provided, the obligations of the Council under the Contract are obligations of the Council in its capacity as a contracting counterparty and nothing in the Contract shall operate as an obligation upon, or in any other way xxxxxx or constrain the Council in any other capacity, nor shall the exercise by the Council of its duties and powers in any other capacity lead to any liability under the Contract (howsoever arising) on the part of the Council to the Provider.
