TECHNICAL AND OPERATIONAL REQUIREMENTS Sample Clauses

TECHNICAL AND OPERATIONAL REQUIREMENTS. The Parties agree that the engineering, construction, testing and commissioning of the Renewable Energy Installation shall be carried out in accordance with the T&O Rules. The Feed-in Approval Holder further agrees to provide the Distribution Licensee, its employees, officers and agents unrestricted access to the Interconnection Facilities and Communication Facilities at all reasonable times upon giving reasonable notice (other than in the case of an emergency condition when immediate access will be given) so as to enable the Distribution Licensee to comply with the provisions of this Agreement and applicable laws. The Distribution Licensee, its employees, officers and agents shall at all times be subject to the Feed-in Approval Holder’s safety rules and regulations and shall exercise such access rights in a manner that will not interfere with the operation of such facilities and the Renewable Energy Installation.
Sample 1Sample 2Sample 3See All (14)
AutoNDA by SimpleDocs
TECHNICAL AND OPERATIONAL REQUIREMENTS. NETSTREAM shall provide services -------------------------------------- that meet the specifications as set forth in this Section 4 and in Exhibit B ("Operational Requirements"):
Sample 1Sample 2Sample 3
TECHNICAL AND OPERATIONAL REQUIREMENTS. AVANTEL shall provide services that -------------------------------------- meet the specifications as set forth in this Paragraph 4 and in Exhibit B ("Operational Requirements"):
Sample 1Sample 2Sample 3
TECHNICAL AND OPERATIONAL REQUIREMENTS. IMPSAT shall provide services that -------------------------------------- meet the specifications as set forth in this Paragraph 4 and in Exhibit B ("Operational Requirements"):
Sample 1Sample 2
TECHNICAL AND OPERATIONAL REQUIREMENTS. 2.5.1 All relevant Technical Criteria and Operational Procedures shall apply to shared LESs as for p hysical LESs.
Sample 1Sample 2
TECHNICAL AND OPERATIONAL REQUIREMENTS. EMBRATEL shall provide services -------------------------------------- that meet the specifications as set forth in this Section 4 and in Exhibit B ("Operational Requirements"):
Sample 1Sample 2
TECHNICAL AND OPERATIONAL REQUIREMENTS. The Parties undertake and agree that the construction, installation, testing and commissioning of the Renewable Energy Installation shall be carried out in accordance with the applicable provisions of the T&O Rules.
Sample 1
AutoNDA by SimpleDocs
TECHNICAL AND OPERATIONAL REQUIREMENTS. The Parties undertake and agree that the construction, installation, testing and commissioning of the Renewable Energy Installation shall be carried out in accordance with the applicable provisions of the T&O Rules. CLAUSE 10: FORCE MAJEURE EVENT Neither Party shall be liable for any delays or omissions to the extent they result from events or circumstances beyond their control such as, but not limited to, natural disasters, strikes, war, riots etc. If a Force Majeure Event results in the revocation of the Feed-in Approval due to the failure by the Feed-in Approval Holder to meet its minimum performance threshold as stipulated in such Feed-in Approval, this Agreement shall automatically terminate upon the date specified in a notice from the Authority to the Parties confirming such revocation.
Sample 1
TECHNICAL AND OPERATIONAL REQUIREMENTS. 2.5.1 All relevant Technical Criteria and Operational Procedures shall apply to shared LESs as for physical LESs.
Sample 1

Related to TECHNICAL AND OPERATIONAL REQUIREMENTS

  • Procedural and Operational Requirements By accepting and using the Financial Assistance awarded under this Agreement and for this Program Element, LPHA agrees to conduct activities in accordance with the following requirements:

  • 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

  • Operational Requirements 4 At-Sea Monitors are deployed, in accordance with coverage rates developed by 5 NMFS and as assigned through the Pre-Trip Notification System (PTNS), to 6 vessels. Due to availability of funding, changes in the fishery management, 7 such as emergency closures, court ordered closures, weather, and unforeseen 8 events must remain flexible. Additional funding for sea days may be added to 9 the contract within the scope and maximum allowable sea days. 10 The following items define the operational services to be provided by the 11 contractor under this contract.

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

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • Business and Operations Borrower will continue to engage in the businesses presently conducted by it as and to the extent the same are necessary for the ownership, maintenance, management and operation of the Property. Borrower will qualify to do business and will remain in good standing under the laws of each jurisdiction as and to the extent the same are required for the ownership, maintenance, management and operation of the Property.

  • Use and Operation 3.1 Permitted Use ......................................................................................................

  • DEVELOPMENTAL REQUIREMENTS The Personal Development Plan (PDP) for addressing developmental gaps is attached as Annexure B.

  • Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.

  • Technical Requirements 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.

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