Systems Availability Sample Clauses

Systems Availability. Service unavailability resulting from Systems Unavailability will not be included in the “Estimated Response Time” calculation. For the purposes hereof, “Systems Unavailability” is defined as the Service Provider’s inability to connect to systems associated with the applicable Support Request, including, but not limited to, Oracle-NetSuite, Wrike, Google Drive, and Dell-Boomi.
AutoNDA by SimpleDocs
Systems Availability. Applies to those systems provided by Q2 for access by Customer. System Availability is the ratio of minutes those production systems are available (excluding regularly scheduled maintenance) in a calendar month to the total number of minutes in that calendar month. Problems or outages associated with systems or providers outside of Q2’s control, such as, but not limited to, ISPs, or from 3rd party application integration (e.g., check image retrieval, xxxx payment, statement image retrieval, check ordering, core processing) are not included in this service component. Q2 shall not be liable to Customer to the extent that a breach by Customer of its obligations under this Agreement results in Q2’s failure to perform the Services in accordance with this SLA. Performance Objective: ******% availability in a calendar month. Penalty: ***% of monthly subscription fees for Q2 Services per ***% below the performance objective for the impacted month. Monthly reporting on Systems Availability is available at customer portal. In the event that there are ****** or more months in a ****** month period which the Monthly System Availability rate falls below ***%, in addition to the aforesaid performance credits as applicable, Customer shall have the right to terminate the Q2 Services upon providing Q2 with ****** days prior written notice. In the event of a termination by Customer under this provision, neither party shall owe the other any further obligation, liability or debt under this Agreement, except for the return or refund of any unearned deposit and except for any obligations under Sections 8 through 13 which shall survive termination.
Systems Availability. Availability refers to the availability of the WFB Operating Systems under Xxxxx Fargo Bank's operational responsibility in both production and test. Xxxxx Fargo Bank will maintain appropriate staffing to meet the stated availability for services provided.
Systems Availability. The New Securities Company shall have received confirmation from the Tokyo, Osaka and Nagoya stock exchanges, the Bank of Japan and Japan Securities Depository Center, Inc. that the systems managed by them which are necessary for NCS’s business will be available to the New Securities Company after the NCS Demerger without interruption or disruption.
Systems Availability. The ratio of hours the CheckFree xxxx payment and banking systems are able to accept payment instructions and banking transactions (excluding regularly scheduled weekly maintenance) to the total number of hours in a month shall not be less than 99% on a rolling three-month basis.
Systems Availability. Ingram hereby warrants and represents that it shall take all reasonable steps required to maintain the availability of its systems that are required to support this Agreement, including without limitation EDI, Xxxxxx Xxxxx.xxx, IMPulse and Speedsource. Ingram shall use its best efforts to remedy any system failure within eight hours of any systems failure.
Systems Availability. The service level objective for Systems availability is ninety nine and nine tenths (99.9%) percent of the time measured over three consecutive months. The following conditions do not apply to this objective: ● Scheduled maintenance. ● Force majeure event. ● Systemic Internet failures. ● Client’s own ISP. ● Client’s bandwidth restrictions. ● Client’s hardware, software or network failure. ● Client’s acts or omissions. ● Suspension or termination of Client’s account. Recovery Point Objective. The service level objective of the data replication and backup systems is to provide a recovery point of no more than fifteen (15) minutes. Therefore in the event of a disaster or disruption event, the potential of loss would be no more that 15 minutes of data preceding the event. Restore Point Objective. The service level objective of the continuity plan is to provide a restore point of no more than three (3) hours. Therefore in the event of a disaster or disruption event, service would be restored within 3 hours.
AutoNDA by SimpleDocs
Systems Availability 
Time is Money Join Law Insider Premium to draft better contracts faster.