System Availability Calculation Sample Clauses

The System Availability Calculation clause defines how the operational uptime of a system or service is measured and reported. Typically, it outlines the formula or method used to calculate the percentage of time the system is accessible, often excluding scheduled maintenance or approved downtime from the calculation. This clause ensures both parties have a clear, agreed-upon standard for evaluating system performance, which is crucial for service level agreements and for addressing issues related to system reliability.
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. 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:
View SourceView Similar (2)
System Availability Calculation a) Netsmart will calculate System Availability as set forth below for each month during the Term of this Netsmart Contract Addendum. b) System Availability will be calculated as follows(and will be rounded to up to the next one tenth of a percentage point): System Availability= [(Base Time - Unscheduled Downtime) /(Base Time) ] x 100 "Base Time" equals the product of the number of days in the applicable month times 24 hours times 60 minutes. "Unscheduled Downtime" equals the time(in minutes) during which the Production System is not operational (excluding "Scheduled Downtime") from Netsmart's hosting facility internet connection based on the measuring methodology documented below. "Scheduled Downtime" equals the aggregate total of all minutes of planned and scheduled maintenance performed during the month to perform any necessary hardware, operating system, network, database, application software maintenance, repair, upgrades, and updates. Netsmart will work with Client to determine and use commercially reasonable efforts to Schedule Downtime after regular business hours, during times that minimize the disruption to operations. The amount of scheduled downtime may vary from month to month depending on the level of change to the system such as the project implementation phase, adding new products, upgrading products, etc. c) Client is permitted to audit the Unscheduled Downtime based on the methodology established below. Netsmart agrees to cooperate with Client in connection with any audit of the 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 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 se...
View SourceView Similar (2)
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)
View SourceView Similar (2)

Related to System Availability Calculation

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

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

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