Payment of Non-compliance Penalties j) Subject to Clause (i) above, the Service Provider shall pay the Non-compliance Penalty indicated in the Non-compliance Penalty Certificate within 10 (ten) Business Days of Transnet issuing a valid Tax Invoice to the Service Provider for the amount set out in that certificate. If Transnet does not issue a valid Tax Invoice to the Service Provider for Non-compliance Penalties accrued during any relevant period, those Non-compliance Penalties shall be carried forward to the next period.
Notification of Non-Compliance If Seller is unable to comply with the obligations stated in this Section, Seller shall promptly notify Apple, and Apple may take any one or more of the following actions: (i) suspend the transfer of Confidential Data to Seller; (ii) require Seller to cease processing Confidential Data; (iii) demand the secure return or destruction of Confidential Data; and/or (iv) immediately terminate this Agreement.
PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations.
Agreement Deviation/Compliance Does the vendor agree with the language in the Vendor Agreement?
Effect of Non-Compliance Failure to comply with the requirements set forth herein may result in termination of this Agreement and/or ineligibility for award of future contracts.
Significant Non-Compliance a) A Competent Authority shall notify the Competent Authority of the other Party when the first-mentioned Competent Authority has determined that there is significant non-compliance with the obligations under this Agreement with respect to a Reporting Financial Institution in the other jurisdiction. The Competent Authority of such other Party shall apply its domestic law (including applicable penalties) to address the significant non-compliance described in the notice.
Non-Compliance Any Products or Services that are not in conformity with the requirements of an Order (“Non-Complying Products” and “Non-Complying Services”, respectively), may be returned at DXC’s option at Supplier’s risk and expense. DXC may procure similar Products or Services in substitution for the Non-Complying Products or Services, and Supplier shall refund the cost of the Non-Complying Products and Service and reimburse DXC upon demand for all additional costs incurred by DXC.
CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.
Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.
Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data management incidents should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.
