Annual Disposal and Operational Report Sample Clauses

Annual Disposal and Operational Report 
AutoNDA by SimpleDocs

Related to Annual Disposal and Operational Report

  • Contractual and Operational Compliance Audits (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and

  • Project Monitoring Reporting Evaluation A. The Project Implementing Entity shall monitor and evaluate the progress of its activities under the Project and prepare Project Reports in accordance with the provisions of Section 5.08(b) of the General Conditions and on the basis of indicators agreed with the Bank. Each such report shall cover the period of one

  • Continued Operation In the event of a Breach or Default by either Interconnected Entity, and subject to termination of the Interconnection Service Agreement under Section 16 of this Appendix 2, the Interconnected Entities shall continue to operate and maintain, as applicable, such DC power systems, protection and Metering Equipment, telemetering equipment, SCADA equipment, transformers, Secondary Systems, communications equipment, building facilities, software, documentation, structural components, and other facilities and appurtenances that are reasonably necessary for Transmission Provider and the Interconnected Transmission Owner to operate and maintain the Transmission System and the Transmission Owner Interconnection Facilities and for Interconnection Customer to operate and maintain the Customer Facility and the Customer Interconnection Facilities, in a safe and reliable manner.

  • Maintenance and Operation Member-Generator agrees to maintain their system and facilities in accordance with applicable manufacturer's recommended maintenance schedule and standard prudent engineering practices. Member-Generator covenants and agrees to operate their system, facilities and equipment so as to minimize the likelihood for a malfunction or other disturbance, damaging or otherwise affecting or impairing Cooperative’s electrical system. Member-Generator shall comply with all applicable laws, regulations, zoning, building codes, safety rules and other environmental regulations or restrictions applicable to the design, installation, operation and maintenance of the Member-Generator's System. Member-Generator must, at least once every year, conduct a test to confirm that Member-Generator’s System automatically ceases to energize the output (interconnection equipment output voltage goes to zero) within two (2) seconds of being disconnected from Cooperative’s electrical system. Disconnecting the Member-Generator’s System from Cooperative’s electrical system at the visible disconnect switch and measuring the time required for the unit to cease to energize the output shall satisfy this test. Member-Generator shall maintain a record of the results of these tests and, upon request by Cooperative, shall provide a copy of the test results to Cooperative. If Member-Generator is unable to provide a copy of the test results upon request, Cooperative shall notify Member- Generator by mail that Member-Generator has thirty (30) days from the date Member-Generator receives the request to provide Cooperative with the results of a test. If Member-Generator does not provide Cooperative with the test results within the thirty (30) day time period or if the test results provided to Cooperative show that Member-Generator’s net metering unit is not functioning correctly, Cooperative may immediately disconnect Member-Generator’s System from Cooperative’s electrical system. If Member-Generator’s equipment ever fails this test, Member-Generator shall immediately disconnect Member-Generator’s System from Cooperative's electrical system. Member-Generator’s System shall not be reconnected to Cooperative's electrical system by the Member-Generator until Member-Generator’s System is repaired and operating in a normal and safe manner. Cooperative shall have the right to have a representative present and informed when any such tests are conducted. Cooperative does not warrant the testing procedures or results by the presence of its representative. Member-Generator is responsible for protecting their equipment from transient high voltage spikes caused by lightning and/or transient low voltage conditions caused by faults or short circuits, and from any other causes or events. Therefore, Cooperative shall not be responsible for damage to Member-Generator’s equipment allegedly caused by transient high voltage spikes caused by lightning and/or transient low voltage conditions caused by faults or short circuits or other causes or events. Member-Generator agrees to notify Cooperative no less than thirty (30) days prior to modification of the components or design of the Member-Generator’s System that in any way may degrade or significantly alter the System’s output characteristics. Member-Generator acknowledges that any such modifications will require submission of a new Application and Agreement to Cooperative.

  • Completed Operations For Construction Agreements, Contractor shall maintain insurance as required by this Agreement to the fullest amount allowed by law and shall maintain insurance for a minimum of five (5) years following the completion of this project. In the event Contractor fails to obtain or maintain completed operations coverage as required by this Agreement, the City at its sole discretion may purchase the coverage required and the cost will be paid by Contractor. THE FOLLOWING PROVISIONS APPLY TO ALL AGREEMENTS Deductibles and Self-Insured Retentions (“SIR”): Any deductibles or self-insured retentions must be declared to and approved by City. The City may require the Contractor or Consultant to purchase coverage with a lower deductible or retention or provide proof of ability to pay losses and related investigations, claim administration, and defense expenses within the retention. At the option of the City, either (1) the insurer shall reduce or eliminate such deductibles or self-insured retentions as respects the City, its elected and appointed officials, officers, attorneys, agents, and employees; or (2) the Contractor or Consultant shall procure a bond guaranteeing payment of losses and related investigations, claim administration and defense expenses. All SIRs must be disclosed to Risk Management for approval and shall not reduce the limits of liability. Policies containing any SIR provision shall provide or be endorsed to provide that the SIR may be satisfied by either the named insured or the City. City reserves the right to obtain a full-certified copy of any insurance policy and endorsements. Failure to exercise this right shall not constitute a waiver of right to exercise later. Acceptability of Insurers: Insurance is to be placed with insurers with a current A.M. Best’s rating of no less than A-:VII, unless otherwise acceptable to City. Claims Made Policies: (note - should be applicable only to professional liability, see below)

  • TAM Service Coverage Each TAM Service Subscription will be limited to certain parameters (that is, a region, a customer team and/or a product line) and will be listed in the Order Form and, if not listed, the TAM parameters will be established upon the initiation of the TAM Service. • Regions: North America, Latin America, EMEA, Asia-Pacific (excluding Japan, China and India), China, India or Japan. • Customer Team: The customer team supported by the TAM, such as your development team, your system administration team, your support team, etc. • Red Hat Product Line: The supported Red Hat product line, such as the Red Hat Enterprise Linux, Red Hat JBoss Middleware, Red Hat Storage or Red Hat Cloud product lines.

  • Variation and Operation Pursuant to and subject to clause 5 of the State Agreement the parties agree to amend the State Agreement in the manner set out in this Agreement.

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • Management and Operations 15.1 The Operator shall prepare an annual work programme and budget for each Calendar Year during the term of this Agreement. Each such work programme and budget shall set out in reasonable details, the work to be carried out, facilities to be purchased or created, training and employment programme, establishment, salaries and wages, social welfare schemes to be undertaken, and an estimate of the Expenditure to be incurred. The Operator shall present such work programme and budget to the Government and the Working Interest Owners before the start of each Calendar Year and thereafter provide a quarterly update on the implementation of such work programme and budget.

  • Operational Control Directing the operation of the Transmission Facilities Under ISO Operational Control to maintain these facilities in a reliable state, as defined by the Reliability Rules. The ISO shall approve operational decisions concerning these facilities, made by each Transmission Owner before the Transmission Owner implements those decisions. In accordance with ISO Procedures, the ISO shall direct each Transmission Owner to take certain actions to restore the system to the Normal State. Operational Control includes security monitoring, adjustment of generation and transmission resources, coordination and approval of changes in transmission status for maintenance, determination of changes in transmission status for reliability, coordination with other Control Areas, voltage reductions and Load Shedding, except that each Transmission Owner continues to physically operate and maintain its facilities.

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