Service Level Agreement Performance Sample Clauses

Service Level Agreement Performance. Compare Service Level Agreement requirements with actual performance measures for the reporting month.
Sample 1Sample 2Sample 3See All (41)
AutoNDA by SimpleDocs
Service Level Agreement Performance. Compare DNS, EPP and RDPS service performance for the reporting month against the SLA as described in section 4 of SPECIFICATION 6. This report shall be transmitted to ICANN electronically in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD_sla_yyyy-mm.csv”, where “gTLD” is the gTLD name; in case of an IDN- TLD, the A-label shall be used; “yyyy-mm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Notes 01 epp-service-dt-min EPP service downtime in minutes. It shall be an integer number.
Sample 1Sample 2
Service Level Agreement Performance. Compare Service Level Agreement requirements with actual performance measures for the reporting month. TLD Zone File Access Activity. State the total number of zone file access passwords at end of the reporting month.
Sample 1
Service Level Agreement Performance. Compare DNS, EPP and RDPS service performance for the reporting month against the SLA as described in section 4 of SPECIFICATION 6Per-Registrar Transactions Report. This report shall be transmitted to ICANN electronicallycompiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD_sla_yyyy-mm-transactions-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyy-mmyyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field Name Notes 01 epp-service-dt-min EPP service downtime in minutes. It shall be an integer number.
Sample 1
Service Level Agreement Performance. Compare DNS, EPP and RDPS service performance for the reporting month against the SLA as described in section 4 of SPECIFICATION 6Per-
Sample 1
Service Level Agreement Performance. Compare Service Level Requirements as listed in Section 6(A)4.2 — Service Definition and Service Level Requirement of Appendix 7, with actual performance measures for the reporting month.
Sample 1
Service Level Agreement Performance. Compare Service Level Agreement requirements with actual performance measures for the reporting month.Per-Registrar Transactions Report. This report shall be compiled in a comma separated- value formatted file as specified in RFC 4180. The file shall be named “net-transactions- yyyymm.csv.” The file shall contain the following fields per registrar:
Sample 1
AutoNDA by SimpleDocs

Related to Service Level Agreement Performance

  • 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 All service level requirements will be set forth in Exhibit A (“XXXX.xxx Referral Service Level Requirements”). Recipient Xxxxxx agrees to adhere, and encourage Recipient Agent’s adherence, with the version of the XXXX.xxx Referral Service Level Requirements in effect at the time XXXX.xxx identifies the Referral to Recipient Broker/Agent.

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

  • Service Level Credits If Verint does not meet the Uptime Percentage levels specified below, Customer will be entitled, upon written request, to a service level credit (“Service Level Credit”) to be calculated, with respect to the applicable Hosted Environment, as follows: • If Uptime Percentage is at least 99.95% of the month’s minutes, no Service Level Credits are provided; or • If Uptime Percentage is 99.75% to 99.94% (inclusive) of the month’s minutes, Customer will be eligible for a credit of 5% of a monthly average fee derived from one-twelfth (1/12th) of the then-current annual fee paid to Verint; or • If Uptime Percentage is 99.50% to 99.74% (inclusive) of the month’s minutes, Customer will be eligible for a credit of 7.5% of a monthly average fee derived from one-twelfth (1/12th) of the then-current annual fee paid to Verint; or • If Uptime Percentage is less than 99.50% of the month’s minutes, Customer will be eligible for a credit of 10.0% of a monthly average fee derived from one-twelfth (1/12th) of the then-current annual fee paid to Verint. Customer shall only be eligible to request Service Level Credits if Customer notifies Verint in writing within thirty (30) days from the end of the month for which Service Level Credits are due. All claims will be verified against Verint’s system records. In the event after such notification Verint determines that Service Level Credits are not due, or that different Service Level Credits are due, Verint shall notify Customer in writing on that finding. With respect to any Services Level credits due under Orders placed directly by Customer on Verint, Service Level Credits will be applied to the next invoice following Customer’s request and Verint’s confirmation of available credits; with respect to any Service Level Credits due for SaaS Services under Orders placed on Verint by a Verint authorized reseller on Customer’s behalf, Service Level Credits will be issued by such reseller following Customer’s request and Verint’s confirmation of available credits and such Services Level Credits may only be used by Customer with respect to subsequent purchases of Verint offerings through that reseller. Service Level Credits shall be Customer’s sole and exclusive remedy in the event of any failure to meet the Service Levels. Verint will only provide records of system availability in response to Customer’s good faith claims.

  • KEY PERFORMANCE INDICATORS 10.1 The Supplier shall at all times during the Framework Period comply with the Key Performance Indicators and achieve the KPI Targets set out in Part B of Framework Schedule 2 (Goods and/or Services and Key Performance Indicators).

  • Excused Performance 6.1 Notwithstanding the occurrence of a Force Majeure Event, in which case Clause 17 will govern, BT will not be liable for any failure or delay to perform any of its obligations under this Agreement (including any of its obligations to meet any Service Levels) to the extent that BT’s failure or delay in performing arises as a result of:

  • Performance Standard The Department’s Grant Manager will review the documentation to verify that the deliverables have been completed as described above. Upon review and written acceptance by the Department’s Grant Manager, the Grantee may proceed with payment request submittal. Payment Request Schedule: The Grantee may submit a payment request for cost reimbursement no more frequently than monthly.

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