Limits on Availability Sample Clauses

Limits on Availability. The ISO may limit the availability of Non-Historic Fixed Price TCCs for initial purchase, by Load Zone, based on each LSE’s average hourly load in that Load Zone and number of Grandfathered Rights and TCCs, Historic Fixed Price TCCs and other Non-Historic Fixed Price TCCs with POWs in that Load Zone held by or on behalf of the LSE. In no event shall an LSE be eligible to purchase new Non-Historic Fixed Price TCCs with a Point of Withdrawal in a Load Zone for which the number of Grandfathered TCCs, Grandfathered Rights, Non-Historic and Historic Fixed Price TCCs held by or on behalf of the LSE with a Point of Withdrawal in that Load Zone equals or exceeds the average hourly load of the LSE in that Load Zone. Additional details shall be specified in the ISO Procedures. Non-Historic Fixed Price TCCs may be offered by the ISO periodically, but no less frequently than every other year. They will be offered, if at all, with an initial term of two years. Renewal terms for Non-Historic Fixed Price TCCs shall be one year.

Related to Limits on Availability

  • Minimum Availability Borrower shall have minimum availability immediately following the initial funding in the amount set forth on the Schedule.

  • General Availability The commitment to availability specified in the letter of appointment shall be subject to mutually acceptable revision. Such revision will occur once per year, or, if mutually agreed between the Employer and the employee, on a more frequent basis. The Employer will issue a revised letter of appointment to reflect approved changes to employee’s general availability.

  • RDDS availability Refers to the ability of all the RDDS services for the TLD, to respond to queries from an Internet user with appropriate data from the relevant Registry System. If 51% or more of the RDDS testing probes see any of the RDDS services as unavailable during a given time, the RDDS will be considered unavailable.

  • High Availability Registry Operator will conduct its operations using network and geographically diverse, redundant servers (including network-­‐level redundancy, end-­‐node level redundancy and the implementation of a load balancing scheme where applicable) to ensure continued operation in the case of technical failure (widespread or local), or an extraordinary occurrence or circumstance beyond the control of the Registry Operator. Registry Operator’s emergency operations department shall be available at all times to respond to extraordinary occurrences.

  • System Availability Although we will try to provide continuous access to the Service, we cannot and do not guarantee that the Service will be available 100% of the time and will not be liable in the event Service is unavailable. Actual service or network performance is dependent on a variety of factors outside of our control. If you notify us within twenty-four (24) hours and we confirm an outage consisting of a period of two (2) hours in any calendar month, and not due to any service, act, or omission of you, a third party, your applications, equipment or facilities, or reasons outside of our control, you shall be eligible for a service credit. A service credit shall be computed as a pro-rated charge for one day of the regular monthly fees for the Service in the next monthly statement. Intermittent service outages for periods of less than two (2) hours are not considered service outages. Outages caused by routine scheduled maintenance are also not considered an outage. You shall receive advance notice no less than forty-eight (48) hours in advance of our scheduled maintenance. Scheduled maintenance will be performed between 12:00 a.m. and 6:00 a.m. CST.