Service Level Agreements & Targets Sample Clauses

Service Level Agreements & Targets. This section is agreed to by Purchaser and Supplier as the key supplier performance indicator for this engagement. The following section reflects the measurements to be used to track and report systems performance on a regular basis. The targets shown in the following tables are for the period of contact or its revision whichever is later. Table 2: Service Level Chart Mapping with Section G5 of SRS Document Service Parameter Service Level Validation Penalty
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs
Service Level Agreements & Targets. 46.1 This section is agreed to by Authority and SI as the key performance indicator for the project. This may be reviewed and revised according to the procedures detailed in Clause 46 SLA Change Control.
Sample 1
Service Level Agreements & Targets. This section is agreed to by Purchaser and Supplier as the key supplier performance indicator for this engagement. The following section reflects the measurements to be used to track and report systems performance on a regular basis. The targets shown in the following tables are for the period of contact or its revision whichever is later. Service Level Chart For overall system availability Availability per quarter Deduction as % of the apportioned price of total FMS for SCADA-DMS portion of the contract applicable for that site > 99% NIL Less than 99% Deduction of 2% of the apportioned price of the apportioned quarterly AMC for every 1% or part there of decrease in availability under 99%. For individual hardware & non critical functions Availability per quarter Deduction as % of the apportioned price of total FMS for SCADA-DMS portion of the contract applicable for that site > 98% NIL Less than 98% Deduction of 2% of the apportioned price of the apportioned quarterly AMC for every 1% or part there of decrease in availability under 98%. (An ISO 9001:2008 Certified Company) While calculating Availability following shall be considered : The Overall SCADA/DMS System shall be considered as available if
Sample 1

Related to Service Level Agreements & Targets

  • Service Level Agreements If a Service or a Plan includes a Service Level Agreement (SLA):

  • Service Level Agreement Subject to the terms and conditions of this Agreement, Bank agrees to perform the custody services provided for under this Agreement in a manner that meets or exceeds any service levels as may be agreed upon by the parties from time to time in a written document that is executed by both parties on or after the date of this Agreement, unless that written document specifically states that it is not contractually binding. For the avoidance of doubt, Bank’s Service Directory shall not be deemed to be such a written document.

  • Service Levels Annex 1 to this Part A of this Call Off Schedule sets out the Service Levels the performance of which the Parties have agreed to measure. The Supplier shall monitor its performance of this Call Off Contract by reference to the relevant performance criteria for achieving the Service Levels shown in Annex 1 to this Part A of this Call Off Schedule (the Service Level Performance Criteria) and shall send the Customer a Performance Monitoring Report detailing the level of service which was achieved in accordance with the provisions of Part B (Performance Monitoring) of this Call Off Schedule. The Supplier shall, at all times, provide the Services in such a manner that the Service Levels Performance Measures are achieved. If the level of performance of the Supplier of any element of the provision by it of the Services during the Call Off Contract Period: is likely to or fails to meet any Service Level Performance Measure or is likely to cause or causes a Critical Service Failure to occur, the Supplier shall immediately notify the Customer in writing and the Customer, in its absolute discretion and without prejudice to any other of its rights howsoever arising including under Clause 12 of this Call Off Contract (Service Levels and Service Credits), may: require the Supplier to immediately take all remedial action that is reasonable to mitigate the impact on the Customer and to rectify or prevent a Service Level Failure or Critical Service Level Failure from taking place or recurring; and if the action taken under paragraph (a) above has not already prevented or remedied the Service Level Failure or Critical Service Level Failure, the Customer shall be entitled to instruct the Supplier to comply with the Rectification Plan Process; or if a Service Level Failure has occurred, deduct from the Call Off Contract Charges the applicable Service Level Credits payable by the Supplier to the Customer in accordance with the calculation formula set out in Annex 1 of this Part A of this Call Off Schedule; or if a Critical Service Level Failure has occurred, exercise its right to Compensation for Critical Service Level Failure in accordance with Clause 13 of this Call Off Contract (Critical Service Level Failure) (including subject, for the avoidance of doubt, the proviso in Clause 13.1.2 of this Call Off Contract in relation to Material Breach). Approval and implementation by the Customer of any Rectification Plan shall not relieve the Supplier of any continuing responsibility to achieve the Service Levels, or remedy any failure to do so, and no estoppels or waiver shall arise from any such Approval and/or implementation by the Customer. SERVICE CREDITS Annex 1 to this Part A of this Call Off Schedule sets out the formula used to calculate a Service Credit payable to the Customer as a result of a Service Level Failure in a given service period which, for the purpose of this Call Off Schedule, shall be a recurrent period of [one Month] during the Call Off Contract Period (the Service Period).

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

  • Service Level In the event that League InfoSight discovers or is notified by you of the existence of Non-Scheduled Downtime, we will use commercially reasonable efforts to determine the source of the problem and attempt to resolve it as quickly as possible.

  • Penalties for Non-compliance to Service Level Agreement Where the Supplier/Service Provider fails to deliver the Goods/Services within the agreed and accepted milestone timelines and provided that the cause of the delay was not due to a fault of Transnet, penalties shall be imposed at …………………………………………………… .

  • Specification and Service Levels The Specification sets out the Services that the Contractor has undertaken to provide. The Specification includes Service Levels setting out particular levels of service that the Contractor has undertaken to meet.

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

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

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