H5 Disruption The Contractor shall take reasonable care to ensure that in the performance of its obligations under the Contract it does not disrupt the operations of the Authority, its employees or any other contractor employed by the Authority.
Disruption 41.1 The Contractor shall take reasonable care to ensure that in the performance of its obligations under the Framework Agreement it does not disrupt the operations of the Authority, its employees or any other Contractor employed by the Authority. 41.2 The Contractor shall immediately inform the Authority of any actual or potential industrial action, whether such action be by their own employees or others, which affects or might affect its ability at any time to perform its obligations under the Framework Agreement. 41.3 In the event of industrial action by the Staff, the Contractor shall seek Approval to its proposals to continue to perform its obligations under the Framework Agreement. 41.4 If the Contractor’s proposals referred to in clause 41.3 are considered insufficient or unacceptable by the Authority acting reasonably, then the Authority may by notice terminate the Framework Agreement with immediate effect.
Downtime There may be downtime during the Migration. The duration of the downtime will depend on the amount of data that Agency is migrating. Axon will work with Agency to minimize any downtime. Any VIEVU mobile application will need to be disabled upon Migration.
Notification of market disruption The Agent shall promptly notify the Borrowers and each of the Lenders stating the circumstances falling within Clause 5.7 which have caused its notice to be given.
Market Disruption (a) If a Market Disruption Event occurs in relation to a Loan for any Interest Period, then the rate of interest on each Lender’s share of that Loan for the Interest Period shall be the percentage rate per annum which is the sum of: (i) the Margin; (ii) the rate notified to the Agent by that Lender as soon as practicable and in any event before interest is due to be paid in respect of that Interest Period, to be that which expresses as a percentage rate per annum the cost to that Lender of funding its participation in that Loan from whatever source it may reasonably select; and (iii) the Mandatory Cost, if any, applicable to that Lender’s participation in the Loan. (b) In this Agreement “Market Disruption Event” means:
Disruption of Service Customer acknowledges and understands that Voice Service will not be available for use under certain circumstances, including without limitation when the network or facilities are not operating or if normal electrical power to the MTA, ATA or ALG is interrupted and such equipment does not have a functioning backup. Customer also understands and acknowledges that the performance of the battery backup is not guaranteed. If the battery backup does not provide power, Voice Services will not function until normal power is restored. Customer also understands that certain online features of Voice Service, where such features are available, will not be available under certain circumstances, including but not limited to the interruption of the Internet connection.
Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:
Emergency Escalation Escalation is strictly for purposes of notifying and investigating possible or potential issues in relation to monitored services. The initiation of any escalation and the subsequent cooperative investigations do not in themselves imply that a monitored service has failed its performance requirements. Escalations shall be carried out between ICANN and Registry Operators, Registrars and Registry Operator, and Registrars and ICANN. Registry Operators and ICANN must provide said emergency operations departments. Current contacts must be maintained between ICANN and Registry Operators and published to Registrars, where relevant to their role in escalations, prior to any processing of an Emergency Escalation by all related parties, and kept current at all times.
Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.
Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.