Service Level Commitments Clause Samples

Service Level Commitments. For purposes of the service level commitment categories set forth below, the described services shall be deemed to be “available” to Client if the Fiserv computer system, including all hardware and software necessary to provide the Client with the Services contemplated by this Agreement, is functioning and able to accept and process all input contemplated by this Agreement from Client and necessary to provide the Services in question. All service levels commitments shall be averaged over a calendar month and national holidays are excluded.

Service Level Commitments. Trinnex shall make the functionality of the Services available to Customer pursuant to the Agreement and shall use commercially reasonable efforts to make the Services available during the Subscription Term, and to protect against the Services containing or transmitting Malicious Code, except for: (i) scheduled maintenance and downtime (of which Trinnex shall, to the extent practicable, schedule so as not to materially adversely affect Customer’s business); (ii) circumstances beyond Trinnex’s control; (iii) Emergency Maintenance; and (iv) as set forth in the Agreement.

Service Level Commitments. 2.1. Target. In each Service Period, the target for availability of the Solutions is 99.9% (“Availability Target”). “Service Period” means 24 hours per day Monday through Sunday each calendar month that Customer receives the Solutions, excluding Sundays between 12:00 AM and 12:00 PM Eastern Time for scheduled maintenance. During this time, Customers may experience intermittent interruptions. CentralSquare will make commercially reasonable efforts to minimize the frequency and duration of these interruptions and CentralSquare will notify the Customer if the entire maintenance window will be required.

Service Level Commitments. A. Availability. During any calendar month, the availability of the Solution shall be no less than 99.9%, excluding scheduled maintenance. CentralSquare shall provide Customer with prompt notification as soon as it becomes aware of any actual or potential unscheduled downtime of the Solution, as well as continual periodic updates during the unscheduled downtime regarding CentralSquare’s progress in remedying the unavailability and estimated time at which the Solution shall be available.

Service Level Commitments. The parties to this Agreement desire to define a mutually beneficial relationship between Dyax and US Bio in order to achieve Dyax’s goals of high patient level product availability, high levels of consumer and pharmacy confidence in the integrity and quality of the Product, and achievement of a collaborative, transparent, and cost-effective distribution system. In order to achieve the stated goals, US Bio agrees to dispense and distribute the Product and perform the Hub Services hereunder in accordance with the key performance indicators described in the Statement of Work attached hereto as Exhibit B and incorporated herein by this reference.

Service Level Commitments. Vendor will ensure that the Software is available for use by the City at least 99.999 per cent of the time during the term of this Agreement. In addition to this commitment, Vendor shall also comply with the service level commitments described in Schedule A.

Service Level Commitments. Notwithstanding the above, Customer shall have the right to terminate this Agreement for cause upon written notice to Sabre (and without the provision of a cure period) in the event that the Availability of the System falls below (i) *****, (ii) ***** for any ***** consecutive months, or (iii) ***** for any ***** months in any *****. Customer may only exercise its right to terminate as permitted under this provision within ***** from the end of the month in which such termination right was triggered. (a) Customer then has ***** days from the point in time that Sabre is deemed in Default of the Service Level to notify Sabre that it will terminate the agreement. (b) Customer then will migrate-off of the System at least ***** days after this notification date. (c) Customer will provide Sabre at least ***** days advance notification of the date it will migrate off the System

Service Level Commitments. Sabre will meet the following Service Level Commitments in connection with its performance under this Work Order: (a) Availability – the System will collectively be Available ***** of the time. For purposes of calculating the Availability of a System, the following metric shall apply: (a) Availability: This Performance Metric is a measure of the time of the System is available to Customer for Productive Use at Sabre’s Data Center (“Availability” or “Available”). It is expressed as a percentage of the Agreed Service Time, during the “Measurement Window” (i.e., a calendar month), for a specific System. The Availability shall be measured in percentage points to ***** decimal places as follows: (b) Agreed Service Time is equal to the total time available in the Measurement Window excluding Routine Downtime. (c) For any period that a System is not Available other than for Routine Downtime (“Unscheduled Outage”), the period of such Unscheduled Outage shall be measured from the point in time when Sabre determines that the Unscheduled Outage began, which shall be the earliest of: (i) the point in time that such Unscheduled Outage is detected by Sabre through its Monitoring System; or (ii) Customer reports such Unscheduled Outage to the Sabre Help Desk; or (iii) any other manner in which Sabre has actual knowledge that the System(s) is not available to Customer (d) The Unscheduled Outage shall end at the point in time which is earlier of: (i) the time Sabre registers in its Monitoring System that the affected System(s) is Available; or (ii) the time Sabre registers traffic from Customer which generates responses from the affected System(s).

Service Level Commitments. 17 (a) Definition of Service Level Commitments . . . . . . . . . . . . . . 17 (b) Exclusive Remedies for Failure to Satisfy Service Level Commitments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 17. Conformity with Documentation. . . . . . . . . . . . . . . . . . . . . . 19 (a) Covenant by BCBSSC. . . . . . . . . . . . . . . . . . . . . . . . . 19 (b) Exclusive Remedies for Failure of System to Conform to Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 18.