System Availability Calculation Sample Clauses

System Availability Calculation. For each Primary Business Component during the applicable Measurement Period, Availability is equal to number of Total Service Minutes excluding Downtime Minutes divided by Total Service Minutes during such Measurement Period, with the result expressed as a percentage. Total Service Minutes = Number of days in the month x 24 hours per day x 60 minutes per hour Availability % = (Total Service Minutes – Downtime Minutes) / Total Service Minutes x 100 Downtime Minutes: Total minutes a Primary Business Component is unavailable for all users or all functions during the calendar month − Maintenance Window minutes that it is unavailable for all users or all functions − Urgent Service Change minutes that it is unavailable for all users or all functions − Minutes that it is unavailable for all users or all functions for Items not within Contractor’s scope − Minutes that it is unavailable for all users or all functions when State has not authorized a recommended patch or upgrade − Minutes that it is unavailable for all users or all functions as a result of the Internet or User network or equipment − Restart Minutes necessary when it is unavailable for all users or all functions − Minutes that it is unavailable for all users or all functions for Excused Performance situations EXAMPLES: • Example 1 Siebel Primary Business Component in Production is down for 20 minutes on October 7th and 35 minutes on October 20th. During the October 20th outage the server needed to be recycled to restore service. The recycling of the server took 15 minutes. The Availability percentage is computed as follows: Downtime minutes = 20 + (35 – 15) = 40 minutes Availability percentage = (44,640 – 40 downtime minutes) / 44,640 x 100 = 99.91%
Sample 1See All (4)
AutoNDA by SimpleDocs
System Availability Calculation. For purposes of this Contract: (a) the System will be deemed “Available” when the System is available for access by End Users and (b) the “System Availability” is calculated each Measurement Interval as follows: System Availability (Minutes per Measurement Interval in which the System is Available) = x 100 (Total minutes in the Measurement Interval – minutes of Scheduled Maintenance during such Month)
Sample 1
System Availability Calculation a. Netsmart will calculate System Availability as set forth below for each month during the Term. b. System Availability will be calculated as follows (and will be rounded to up to the next one tenth of a percentage point): c. Client is permitted to audit Unscheduled Downtime based on the methodology established below. Netsmart agrees to cooperate with Client in connection with any audit of Unscheduled Downtime. This audit must take place within 30 days of the month end. d. Netsmart recommends that Client implement, on a timely basis, the Service Packages that will be provided to Client by Netsmart on a periodic basis. Netsmart will advise Client on Service Packages that may enhance performance and availability and will advise Client of the advantages of implementing the Service Packages as well as the implication of electing not to implement the Service Packages. Netsmart will perform the technical requirements needed for Client to use the Service Packages that Client elects to implement, at no additional charge and as part of the recurring SaaS/Hosting fees. Client and Netsmart will work together to establish a mutually agreeable implementation schedule for the Service Packages. Upon notice to Client that the system’s performance and availability will be adversely affected if Client elects not to implement a Service Package, Client will waive any credits set forth above, until such time as Client performs its obligations as necessary to implement the required Service Packages. e. Client must allow Netsmart to implement the latest Netsmart supported layered software version (i.e. OS, DBMS, etc.) and patches within six (6) months of the general support announcement from Netsmart. Netsmart will advise Client regarding the layered software enhancements as well as the implications of electing not to implement the layered software enhancements. Netsmart will perform the technical requirements needed for Client to use the layered software enhancements that Client elects to implement as part of the fees. Client and Netsmart will work together to establish an implementation schedule for the layered software enhancements. If Netsmart provides notice to Client that the system’s performance and availability will be adversely affected if Client elects not to implement the layered software enhancements, Client waives its right to any credits set forth above until Client implements the required layered software enhancements. f. If Client is operating beyond the Scope o...
Sample 1

Related to System Availability Calculation

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

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

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

  • Funds Availability Funds from items deposited through the Service will be available in accordance with the Credit Union’s Funds Availability Policy disclosure, as amended from time to time, which is incorporated herein by reference. You agree that the imaging and transmitting of checks alone does not constitute receipt by Credit Union. Also, acknowledgment of receipt or delivery does not constitute an acknowledgment by Credit Union that the transmission of a check or items does not contain errors or that funds will be available. Checks deposited though Mobile Deposit are not received by the Credit Union until we have acknowledged receipt and provided credit to your account.

  • Fund Availability Financial obligations of the University payable after the current fiscal year are contingent upon funds for that purpose being appropriated, budgeted, and otherwise made available.

  • Funding Availability 1. This Contract is contingent upon the continued availability of funding. If funds become unavailable through the lack of appropriations, legislative or executive budget cuts, amendment of the Appropriations Act, state agency consolidation or any other disruptions of current appropriations, DFPS will reduce or terminate this Contract.

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!