Service Availability Calculation Sample Clauses

Service Availability Calculation. Service Availability will be measured and reported in hours and percentages. Three basic figures will be calculated and reported to ensure transparency: · Maximum Availability (MA) — The maximum number of hours the service could be available for the given period, excluding scheduled downtime. · SLA Target Availability (STA) — MA minus the agreed unscheduled downtime. · Actual Availability (AA) — MA minus any unscheduled downtime The availability percentage for a particular period is calculated using the following formula: [*] [*] [*] X 100 [*]
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Service Availability Calculation. The Service Availability shall be measured on a per calendar month basis, and computed as follows: (a) determine a fraction, the numerator of which is the hours of Service Availability plus the hours of Excusable Downtime and the denominator of which is the total hours, and then (b) multiply the fraction by 100. Fractional hours are rounded up to the next tenth.
Sample 1
Service Availability Calculation. 8.1.3.1. The services availability calculation measures the percentage of time during any calendar month that the production instance of the application is available, as measured by one or more automated monitor (s) defined and implemented within the Xpertdoc monitoring system (the “Monitoring System”).
Sample 1
Service Availability Calculation. 100 * (Total # minutes in a month- Maintenance Minutes1 ) - (Total Service Unavailability minutes) (Total # minutes in a month – Maintenance Minutes) NOTE: Service Availability Calculation is based on a calendar month
Sample 1
Service Availability Calculation. The percentage of Service availability will be calculated as follows: P = ((A – B – C) / (A – B)) * 100 Where: P = % Availability A = Number of hours in a month B = Planned Downtime, as defined below C = Total time of Service unavailability The period when the Service was not available will be measured from the time such condition is reported to the Subscriber’s Administrator, and shall end when Brightidea resolves the trouble ticket and informs the Subscriber’s Administrator that the Service is available. (In addition, if Brightidea Inc. is aware of any unscheduled outages, they must inform the Subscriber’s nominated contact/s within 1 hour by phone or email.)
Sample 1
Service Availability Calculation. 3.1 Oak utilise an industry standard approach to calculate the availability of the Oak SaaS Platform, which is used by organisations, including Microsoft, for services such as the Microsoft Azure IaaS (infrastructure as a service) platform on which Oak is hosted.
Sample 1

Related to Service Availability Calculation

  • Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • DNS service availability Refers to the ability of the group of listed-­‐as-­‐authoritative name servers of a particular domain name (e.g., a TLD), to answer DNS queries from DNS probes. For the service to be considered available at a particular moment, at least, two of the delegated name servers registered in the DNS must have successful results from “DNS tests” to each of their public-­‐DNS registered “IP addresses” to which the name server resolves. If 51% or more of the DNS testing probes see the service as unavailable during a given time, the DNS service will be considered unavailable.

  • System Availability System Availability percentage is calculated as follows:  Total MinutesintheMonth −Downtime   System Availability%age =  Total MinutesintheMonth *100    System Availability SLA (“SLA”) 99.5% System Availability percentage during each Month for productive versions Credit 2% of Monthly Subscription Fees for each 1% below SLA, not to exceed 100% of Monthly Subscription Fees Excluded Downtime Total Minutes in the Month attributable to: (i) a Scheduled Downtime for which a Regular Maintenance Window is described in Section 4 below, or (ii) any other Scheduled Downtime according to Section 4 for which the customer has been notified at least five (5) business days prior to such Scheduled Downtime or (iii) unavailability caused by factors outside of SAP’s reasonable control, such as unpredictable and unforeseeable events that could not have been avoided even if reasonable care had been exercised. Scheduled Downtime Scheduled Downtime for the applicable Cloud Services to which customer has subscribed is set forth in Section 4 below entitled “Maintenance Windows for Cloud Services”.

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

  • Excess Availability Borrowers shall have Excess Availability at all times of at least (i) as of any date of determination during the period from July 25, 2016 through and including August 29, 2016, $10,000,000, (ii) as of any date of determination during the period from August 30, 2016 through and including October 6, 2016, $13,000,000, (iii) as of any date of determination during the period from October 7, 2016 through and including October 13, 2016, $17,500,000, and (iv) as of any date of determination during the period from October 14, 2016 through and including December 31, 2016, $20,000,000.

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