Service Level Agreement Credit Application Structure Sample Clauses

Service Level Agreement Credit Application Structure.  For any calendar month in which Verizon fails to meet any of the Service Level Standards stated in this document the credit structure for the Service Level Standards listed above will be applied to the corresponding net billing MRC for the specific Connection(s) affected by a PIP Network Hard Outage(s) or Service Issue(s).  The total of all credits within any one month is limited to a maximum of 100% of the MRC for the specific Connection or Site, as applicable, which was impacted by any non-compliance with the Service Level Standard(s). Credits are not cumulative month to month.  Credits for Hard Outages are determined based on Eligible Hard Outage Minutes and Customer may claim the TTR Service Level Standard credit in addition to the Availability Service Level Standard credit in a given calendar month. Customer may claim only one credit within a particular Service Issue Service Level Standard category during a given month. Customer cannot claim credits from both the Hard Outage and Service Issue categories for the same event. Customer can request to have compliance checked for all of the standard Service Level Standard commitments when requesting credits in any given month.  To receive a credit, a trouble ticket must be opened with Verizon and Customer must submit their credit request no later than the stipulated time allowed to claim the specific Service Level Standard credit. The appropriate refund amount will be credited to the Customer’s account at the billing account number (BAN) level in one lump sum, as opposed to each individual circuit or all circuits under multiple BANs. The appropriate refund amount will be appearing as a line item on a xxxx delivered within 90 calendar days following Verizon’s confirmation of non-compliance with the Service Level Standard.  Credits do not apply to Local Access or backhaul charges.
AutoNDA by SimpleDocs

Related to Service Level Agreement Credit Application Structure

  • 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 Level Agreements If a Service or a Plan includes a Service Level Agreement (SLA):

  • Competitive Supplier’s Standard Credit Policy The Competitive Supplier will not require a credit review for any consumer participating in the Program, nor does Competitive Supplier require any consumer to post any security deposit as a condition for participation in the Program. The Competitive Supplier may terminate service to a Participating Consumer and return such consumer to a Basic Service in the event that the Participating Consumer fails to pay to Competitive Supplier amounts past-due greater than sixty (60) days.

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

  • XXXX ANTI-LOBBYING AMENDMENT Xxxx Anti-Lobbying Amendment (31U.S.C. 1352) – Contractors that apply or bid for an award exceeding ,000 must file the required anti-lobbying certification. Each tier must certify to the tier above that it will not and has not used Federal appropriated funds to pay any person or organization for influencing or attempting to influence an officer or employee of any agency, a member of Congress, officer or employee of Congress, or an employee of a member of Congress in connection with obtaining any Federal contract, grant or any other award covered by 31 U.S.C. 1352. Each tier must also disclose any lobbying with non-Federal funds that takes place in connection with obtaining any Federal award. Such disclosures are forwarded from tier to tier up to the Customer. As applicable, Contractor agrees to file all certifications and disclosures required by, and otherwise comply with, the Xxxx Anti-Lobbying Amendment (31 USC 1352).Contractor certifies that it is currently in compliance with all applicable provisions of the Xxxx Anti-Lobbying Amendment (31 U.S.C. 1352) and will continue to be in compliance throughout the term of the Contract and further certifies that:

  • COMMENCEMENT OF WORK UNDER A SOW AGREEMENT Commencement of work as a result of the SOW-RFP process shall be initiated only upon issuance of a fully executed SOW Agreement and Purchase Order.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • ATTACHMENT E BUSINESS ASSOCIATE AGREEMENT This Business Associate Agreement (“Agreement”) is entered into by and between the State of Vermont Agency of Human Services, operating by and through its Department of Vermont Health Access (“Covered Entity”) and OptumInsight, Inc. (“Business Associate”) as of June 6, 2014 (“Effective Date”). This Agreement supplements and is made a part of the contract/grant to which it is attached. Covered Entity and Business Associate enter into this Agreement to comply with standards promulgated under the Health Insurance Portability and Accountability Act of 1996 (“HIPAA”), including the Standards for the Privacy of Individually Identifiable Health Information, at 45 CFR Parts 160 and 164 (“Privacy Rule”), and the Security Standards, at 45 CFR Parts 160 and 164 (“Security Rule”), as amended by Subtitle D of the Health Information Technology for Economic and Clinical Health Act (HITECH), and any associated federal rules and regulations. The parties agree as follows:

  • Service Level Commitment IBM provides the following service level commitment (“SLA”) for the Cloud Service, after IBM makes the Cloud Service available to you.

  • Review and Amendment 1. The Council for TRIPS shall review the implementation of this Agreement after the expiration of the transitional period referred to in paragraph 2 of Article 65. The Council shall, having regard to the experience gained in its implementation, review it two years after that date, and at identical intervals thereafter. The Council may also undertake reviews in the light of any relevant new developments which might warrant modification or amendment of this Agreement.

Time is Money Join Law Insider Premium to draft better contracts faster.