Usage Conditions & Utilization Policy. Red Hat 3Scale API Management Subscriptions are subject to the same usage and utilization terms as set forth in Sections 1.6.1 and 1.6.2 above.
Usage Conditions & Utilization Policy Sample Clauses
Related to Usage Conditions & Utilization Policy
Safe Conditions Whenever an employee reports a condition which the employee feels represents a violation of safety or health rules and regulations or which is an unreasonable hazard to persons or property, such conditions shall be promptly investigated. The appropriate administrator shall reply to the concern, in writing, if the employee's concern is communicated in writing.
Unsafe Conditions In accordance with 29 CFR § 1977, occasions might arise when an employee is confronted with a choice between not performing assigned tasks or subjecting himself/herself to serious injury or death arising from a hazardous condition at the workplace. If the employee, with no reasonable alternative, refuses in good faith to expose himself/herself to the dangerous condition, he/she would be protected against subsequent discrimination. The condition causing the employee's apprehension of death or injury must be of such a nature that a reasonable person, under the circumstances then confronting the employee, would conclude that there is a real danger of death or serious injury and that there is insufficient time, due to the urgency of the situation, to eliminate the danger by resorting to regular statutory enforcement channels. In addition, in such circumstances, the employee, where possible, must also have sought from his Employer, and been unable to obtain, a correction of the dangerous condition.
Service Conditions Customer acknowledges that in the event of a service issue, Customer is responsible for on-site cooperative testing with LightEdge Technical Support to assist in the diagnosis of the trouble. Customer agrees to be bound to current terms of LightEdge Acceptable Use Policy. Terms of the Acceptable Use Policy are subject to change without notice. Current Acceptable Use Policy can be found here: xxxx://xxx.xxxxxxxxx.xxx/legal Customer agrees that any service complaints including concerns regarding level of support, products, service reliability, or any other concerns related to LightEdge or Services being provided by LIghtEdge will be communicated to LightEdge by sending an email to xx@xxxxxxxxx.xxx.
Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Subloop that may diminish the capability of the Loop or Subloop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the BellSouth’s TR 73600 Unbundled Local Loop Technical Specification. 2.5.2 BellSouth will remove load coils only on copper Loops and Subloops that are less than eighteen thousand (18,000) feet in length. 2.5.3 For any copper loop being ordered by NewPhone which has over six thousand (6,000) feet of combined bridged tap will be modified, upon request from NewPhone, so that the loop will have a maximum of six thousand (6,000) feet of bridged tap. This modification will be performed at no additional charge to NewPhone. Loop conditioning orders that require the removal of bridged tap that serves no network design purpose on a copper Loop that will result in a combined total of bridged tap between two thousand five hundred (2,500) and six thousand (6,000) feet will be performed at the rates set forth in Exhibit A. 2.5.4 NewPhone may request removal of any unnecessary and non-excessive bridged tap (bridged tap between zero (0) and two thousand five hundred (2,500) feet which serves no network design purpose), at rates pursuant to BellSouth’s SC Process as mutually agreed to by the Parties. 2.5.5 Rates for ULM are as set forth in Exhibit A. 2.5.6 BellSouth will not modify a Loop in such a way that it no longer meets the technical parameters of the original Loop type (e.g., voice grade, ADSL, etc.) being ordered. 2.5.7 If NewPhone requests ULM on a reserved facility for a new Loop order, BellSouth may perform a pair change and provision a different Loop facility in lieu of the reserved facility with ULM if feasible. The Loop provisioned will meet or exceed specifications of the requested Loop facility as modified. NewPhone will not be charged for ULM if a different Loop is provisioned. For Loops that require a DLR or its equivalent, BellSouth will provide LMU detail of the Loop provisioned. 2.5.8 NewPhone shall request Loop make up information pursuant to this Attachment prior to submitting a service inquiry and/or a LSR for the Loop type that NewPhone desires BellSouth to condition. 2.5.9 When requesting ULM for a Loop that BellSouth has previously provisioned for NewPhone, NewPhone will submit a SI to BellSouth. If a spare Loop facility that meets the Loop modification specifications requested by NewPhone is available at the location for which the ULM was requested, NewPhone will have the option to change the Loop facility to the qualifying spare facility rather than to provide ULM. In the event that BellSouth changes the Loop facility in lieu of providing ULM, NewPhone will not be charged for ULM but will only be charged the service order charges for submitting an order.
Service Level Agreement 6.1 NCR Voyix will use commercially reasonable efforts to make the Service available to you at or above the Availability Rate set forth at xxxxx://xxx.xxx.xxx/support/aloha-sla. If NCR Voyix does not meet the Availability Rate, you are entitled to request a service-level credit subject to the terms of this Agreement. This credit is calculated as a percentage of the monthly recurring bill (or monthly pro rata share of billing, if billing does not occur monthly) for the Service for the month in which the Availability Rate was not met. The Availability Rate is determined by: (a) dividing the total number of valid outage minutes in a calendar month by the total number of minutes in that month; (b) subtracting that quotient from 1.00; (c) multiplying that difference by 100; and (d) rounding that result to two decimal places in accordance with standard rounding conventions. The number of outage minutes per day for a given service is determined by the lesser of the number of outage minutes. 6.2 Unavailability due to other conditions or caused by factors outside of NCR Voyix’s reasonable control will not be included in the calculation of the Availability Rate. Further, the following are expressly excluded from the calculation of the Availability Rate: (a) service unavailability affecting services or application program interfaces that are not used by you; (b) cases where fail-over to another data center is available but not utilized; (c) transient time-outs, required re-tries, or slower-than-normal response caused by factors outside of NCR Voyix’s reasonable control; (d) Scheduled Downtime, including maintenance and upgrades; (e) force majeure; (f) transmission or communications outages outside the NCR Voyix- controlled environment; (g) store-level down-time caused by factors outside of NCR Voyix’s reasonable control; (h) outages attributable to services, hardware, or software not provided by NCR Voyix, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services; (i) use of the Service in a manner inconsistent with the documentation for the application program interface or the NCR Voyix Product; (j) your Point of Sale (“POS”) failure or the failure to properly maintain the POS environment, including updating the POS firmware or version of the software running on the POS as recommended by either NCR Voyix, a third-party POS reseller or servicer; and (k) issues related to third party domain name system (“DNS”) errors or failures. 6.3 To obtain a service-level credit, you must submit a claim by contacting NCR Voyix through the website at xxxxx://xxx.xxx.xxx/support/aloha-sla Your failure to provide the claim and other information will disqualify you from receiving a credit. NCR Voyix must receive claims within 60 days from the last day of the impacted month. After that date, claims are considered waived and will be refused. You must be in compliance with the Agreement in order to be eligible for a service-level credit. You may not unilaterally offset for any performance or availability issues any amount owed to NCR Voyix. If multiple Services experience an outage in a given month, the total credit for that month will be the highest credit allowed for any single Service which failed; there is no stacking of credits. 6.4 The remedies set forth in the Section are your sole and exclusive remedies for performance or availability issues affecting the Services, including any failure by NCR Voyix to achieve the Availability Rate.
Service Level Commitment IBM provides the following service level commitment (“SLA”) for the Cloud Service, after IBM makes the Cloud Service available to you.
Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).
Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.
Terms & Conditions The Contractor agrees to comply with the Terms and Conditions.
Service Level Agreements If a Service or a Plan includes a Service Level Agreement (SLA): (a) we are liable for any remedy or rebate specified by the SLA; and (b) subject to clauses 40 to 42, and to the express terms of the SLA, our liability for breach of the SLA is limited to such remedy or rebate.
