Non-Compliance Problems Sample Clauses

Non-Compliance Problems. If Client notifies TCP of a problem and TCP correctly determines that the problem is due to Client’s incorrect or improper use of the Software or failure to comply with the terms of the License Agreement an attached Addendums, the resolution of such problem is not covered by Support and Maintenance. However, TCP may provide additional services to correct the problem pursuant to a separate Statement of Work.
AutoNDA by SimpleDocs

Related to Non-Compliance Problems

  • Labor Compliance Program The City has its own Labor Compliance Program authorized in August 2011 by the DIR. The City will withhold contract payments when payroll records are delinquent or deemed inadequate by the City or other governmental entity, or it has been established after an investigation by the City or other governmental entity that underpayment(s) have occurred. For questions or assistance, please contact the City of San Diego’s Equal Opportunity Contracting Department at 000-000-0000.

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

  • PCI-DSS Compliance Merchant shall be in full compliance with rules, regulations, guidelines and procedures adopted by any Card Association or Payment Network relating to the privacy and security of Cardholder and Card transaction data, including without limitation the most up-to-date version of the Payment Card Industry Data Security Standard (PCI-DSS), as amended from time to time by the Payment Card Industry Security Standards Council. Detailed information pertaining to aforementioned requirements may be found at xxxxx://xxx.xxxxxxxxxxxxxxxxxxxx.xxx. Additional information regarding security requirements may be found on the Card Association’s respective web sites.

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

  • HIPAA Compliance If this Contract involves services, activities or products subject to the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Contractor covenants that it will appropriately safeguard Protected Health Information (defined in 45 CFR 160.103), and agrees that it is subject to, and shall comply with, the provisions of 45 CFR 164 Subpart E regarding use and disclosure of Protected Health Information.

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

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.

  • CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.

  • Child Abuse Reporting Requirement Grantee will:

  • Reasonable Suspicion Testing The Employer may, but does not have a legal duty to, request or require an employee to undergo drug and alcohol testing if the Employer or any supervisor of the employee has a reasonable suspicion (a belief based on specific facts and rational inferences drawn from those facts) related to the performance of the job that the employee:

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