Availability Goal Sample Clauses

Availability Goal. For purpose of the Availability Goal, the duration of a Service Outage shall be deemed to commence upon the opening of a Verifiable Trouble Ticket by LightEdge Technical Support, in response to the Customer request, and ends when the Service Outage ends. Trouble tickets, where the Service Outage cannot be verified with LightEdge's standard diagnostic procedures, do not count towards the Availability SLA.
AutoNDA by SimpleDocs

Related to Availability Goal

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

  • Staffing Levels To the extent legislative appropriations and PIN authorizations allow, safe staffing levels will be maintained in all institutions where employees have patient, client, inmate or student care responsibilities. In July of each year, the Secretary or Deputy Secretary of each agency will, upon request, meet with the Union, to hear the employees’ views regarding staffing levels. In August of each year, the Secretary or Deputy Secretary of Budget and Management will, upon request, meet with the Union to hear the employees’ views regarding the Governor’s budget request.

  • Performance Levels (a) The Performance Levels which apply to the performance by the respective Parties of their obligations under this Agreement are set out in Part 1 of Schedule 5. A failure by either Party to achieve the relevant Performance Level will not constitute a breach of this Agreement and the only consequences of such failure as between the Parties shall be the consequences set out in this Clause 5.6. (b) If the Operator does not comply with the Operator Performance Level then the Access Holder must pay to QR Network the amount determined in accordance with Schedule 5 as part of the invoice issued by QR Network for Access Charges and other charges for the Billing Period immediately following QR Network becoming entitled to that amount. Where there is no next Billing Period, the Operator must pay such amount to QR Network within fourteen (14) days after receipt of a Tax Invoice from QR Network. (c) If QR Network does not comply with the QR Network Performance Level then QR Network will credit to the Access Holder the amount determined in accordance with Schedule 5 by way of a deduction from the invoice issued by QR Network for Access Charges and other charges for the Billing Period immediately following the Access Holder becoming entitled to that amount. Where there is no next Billing Period, QR Network must pay such amount to the Access Holder within fourteen (14) days after receipt of a Tax Invoice from the Access Holder. (d) The Parties must, if requested by either Party, meet to review the Performance Levels subject to such review not occurring within six (6) Months after the Commitment Date or any previous review of the Performance Levels. If either Party notifies the other that it considers that the Performance Levels are no longer appropriate, the Parties may agree on varied Performance Levels and any associated variations to the Agreement including the Base Access Charges and the Train Service Description. If the Parties are unable to agree to such variations, then the existing Performance Levels shall continue to apply unless varied by QR Network in accordance with the provisions of Clause 5.6(e). (e) In the event that the Access Holder and/or the Operator (i) does not comply in any material respect with the Train Service Description; and (ii) the Access Holder fails to demonstrate to the reasonable satisfaction of QR Network when requested to do so, that the Access Holder will consistently comply with the Train Service Description for the remainder of the Term then, following consultation with the Access Holder, QR Network will be entitled to: (iii) vary the Train Service Description to a level it reasonably expects to be achievable by the Access Holder for the remainder of the Term having regard to the extent of previous compliance with the Train Service Description (ignoring, for the purpose of assessing previous compliance, any non-compliance to the extent that the non-compliance was attributable to a Railway Operator (other than the Access Holder) or to QR Network); and (iv) vary the Agreement (including, without limitation, the Operator Performance Level and the Base Access Charges) to reflect the impact of the change in the Train Service Description. (f) The Access Holder shall be entitled to dispute any variation proposed by QR Network pursuant to Clause 5.6(e) and such dispute will be referred to an expert for resolution in accordance with Clause 17.3.

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

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

  • 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 Excess Availability Borrower shall have Excess Availability under the Revolving Credit Loans facility of not less than the amount specified in the Schedule, after giving effect to the initial advance hereunder and after giving effect to any applicable Loan Reserves against borrowing availability under the Revolving Credit Loans.

  • Product Availability Under no circumstances shall Company be responsible to Representative or anyone else for its failure to fill accepted orders, or for its delay in filling accepted orders, when such failure or delay is due to strike, accident, labor trouble, acts of nature, freight embargo, war, civil disturbance, vendor problems or any cause beyond Company's reasonable control.

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

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