Permitted Downtime Sample Clauses

Permitted Downtime. 4.1. The following circumstances are agreed by the Parties to be Permitted Downtime and shall not be considered as periods of service outage when calculating whether or not the Service Availability Target has been met: 4.1.1. Outages caused by any type of denial-of-service attack regardless of the target. 4.1.2. Outages caused by: (i) the actions or inactions of the Customer or any User; or (ii) disclosure of Account Information or other system security information to an unauthorised party by the Customer or any User. 4.1.3. Outages that occur at the request of the Customer. 4.1.4. Network or internet connectivity issues which: (i) are not directly attributable to Infonetica; (ii) are caused by or relate to the Customer’s network connections, servers or telecommunications links; or (iii) are caused by the internet. 4.1.5. Implementation of upgrades or Revisions that require suspension of the Software to ensure data integrity and security. Infonetica aims to implement such Revisions outside of Customer Standard Working Hours, although they may occur during Customer Standard Working Hours. 4.1.6. Any period of downtime for or during a data migration required between Revisions as described in paragraph 10.3. 4.1.7. Downtime or outages that occur which are beyond the control of Infonetica, including where attributable to its Hosting Provider. 4.1.8. Planned outages and/or those which have been scheduled in accordance with the notification periods set out in paragraph 2.4. 4.1.9. Outages as a result of a Force Majeure Event. 4.1.10. Any outage caused by the Customer’s failure to comply with paragraph 5 or failure to provide Infonetica with sufficient notice (as set out in the Contract) of a change to its Authentication Option.
Permitted Downtime. Permitted Downtime includes Planned Service Disruptions and any disruptions in the availability of the Campus Pack Services caused by Problems Beyond Learning Objects’ Control.
Permitted Downtime. Total possible uptime minutes does not include downtime minutes required in order to perform the maintenance services described in paragraph 6.6 below;
Permitted Downtime. “Permitted Downtime” means the following:
Permitted Downtime. 0.01% aggregate downtime on the Temperature Range is permitted one time during the said 12 month period, which is equivalent to a single occurrence of not more than 52.56 minutes in duration over the 12-month period.
Permitted Downtime. Total possible uptime minutes does not include downtime minutes: (a) required in order to perform the maintenance services described in paragraph 1.4 below; (b) Licensee-caused or third party-caused outages or disruptions; (c) as a result of outages, disruptions or emergency maintenance attributable in whole or in part to force majeure events within the meaning of paragraph 1.5 below.

Related to Permitted Downtime

  • Downtime Each of Zero Hash and ZHLS uses commercially reasonable efforts to provide the Services in a reliable and secure manner. From time to time, interruptions, errors, delays, or other deficiencies in providing the Services may occur due to a variety of factors, some of which are outside of Zero Hash’s and/or ZHLS’ control, and some which may require or result in scheduled maintenance or unscheduled downtime of the Services (collectively, “Downtime”). You understand and acknowledge that part or all of the Services may be unavailable during any such period of Downtime, and you acknowledge that Zero Hash and ZHLS are not liable or responsible to you for any inconvenience or losses to you as a result of Downtime. Following Downtime, you further understand and acknowledge that the prevailing market prices of cryptocurrency may differ significantly from the prices prior to such Downtime.

  • Use of Interconnection Facilities by Third Parties 494950 9.9.1 Purpose of Interconnection Facilities 494950 9.9.2 Third Party Users. 50 9.10 Disturbance Analysis Data Exchange. 50 ARTICLE 10. MAINTENANCE 50 10.1 Participating TO Obligations. 50 10.2 Interconnection Customer Obligations. 50 10.3 Coordination 505051

  • Outage Repair Standard In the event of an outage or trouble in any Service being provided by a Party hereunder, the Providing Party will follow Verizon’s standard procedures for isolating and clearing the outage or trouble.

  • Purpose of Interconnection Facilities Except as may be required by Applicable Laws and Regulations, or as otherwise agreed to among the Parties, the Interconnection Facilities shall be constructed for the sole purpose of interconnecting the Large Generating Facility to the Participating TO’s Transmission System and shall be used for no other purpose.

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

  • System Upgrade Facilities Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Scope of Interconnection Service 1.3.1 The NYISO will provide Energy Resource Interconnection Service and Capacity Resource Interconnection Service to Interconnection Customer at the Point of Interconnection. 1.3.2 This Agreement does not constitute an agreement to purchase or deliver the Interconnection Customer’s power. The purchase or delivery of power and other services that the Interconnection Customer may require will be covered under separate agreements, if any, or applicable provisions of NYISO’s or Connecting Transmission Owner’s tariffs. The Interconnection Customer will be responsible for separately making all necessary arrangements (including scheduling) for delivery of electricity in accordance with the applicable provisions of the ISO OATT and Connecting Transmission Owner’s tariff. The execution of this Agreement does not constitute a request for, nor agreement to, provide Energy, any Ancillary Services or Installed Capacity under the NYISO Services Tariff or any Connecting Transmission Owner’s tariff. If Interconnection Customer wishes to supply or purchase Energy, Installed Capacity or Ancillary Services, then Interconnection Customer will make application to do so in accordance with the NYISO Services Tariff or Connecting Transmission Owner’s tariff.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Maintenance Outages If Seller reasonably determines that it is necessary to schedule a Maintenance Outage, Seller shall notify Buyer of the proposed Maintenance Outage at least five (5) days before the outage begins (or such shorter period to which Buyer may reasonably consent in light of then existing conditions). Upon such notice, the Parties shall plan the Maintenance Outage to mutually accommodate the reasonable requirements of Seller and the service obligations of Buyer; provided, however, that, unless Buyer otherwise consents, such consent not to be unreasonably withheld, no Maintenance Outage may be scheduled between the hour ending 0700 through the hour ending 2200, Monday through Saturday, during the time period commencing on May 15 and concluding on September 15. Notice of a proposed Maintenance Outage shall include the expected start date and time of the outage, the amount of Capacity of the Facility that will not be available, and the expected completion date and time of the outage. Seller shall give Buyer notice of the Maintenance Outage as soon as Seller determines that the Maintenance Outage is necessary. Buyer shall promptly respond to such notice and may request reasonable modifications in the schedule for the outage. Seller shall use all reasonable efforts to comply with any request to modify the schedule for a Maintenance Outage. Seller shall notify Buyer of any subsequent changes in Capacity available to Buyer or any changes in the Maintenance Outage completion date and time. As soon as practicable, any notifications given orally shall be confirmed in writing. Seller shall take all reasonable measures and exercise its best efforts in accordance with Prudent Electrical Practices to minimize the frequency and duration of Maintenance Outages.

  • Trading Facilities Most open-outcry and electronic trading facilities are supported by computer-based component systems for the order-routing, execution, matching, registration or clearing of trades. As with all facilities and systems, they are vulnerable to temporary disruption or failure. Your ability to recover certain losses may be subject to limits on liability imposed by the system provider, the market, the clearing house and/or member firms. Such limits may vary; you should ask the firm with which you deal for details in this respect.