General Compliance This Agreement is intended to comply with Section 409A or an exemption thereunder and shall be construed and administered in accordance with Section 409A. Notwithstanding any other provision of this Agreement, payments provided under this Agreement may only be made upon an event and in a manner that complies with Section 409A or an applicable exemption. Any payments under this Agreement that may be excluded from Section 409A either as separation pay due to an involuntary separation from service or as a short-term deferral shall be excluded from Section 409A to the maximum extent possible. For purposes of Section 409A, each installment payment provided under this Agreement shall be treated as a separate payment. Any payments to be made under this Agreement upon a termination of employment shall only be made upon a “separation from service” under Section 409A. Notwithstanding the foregoing, the Company makes no representations that the payments and benefits provided under this Agreement comply with Section 409A, and in no event shall the Company be liable for all or any portion of any taxes, penalties, interest, or other expenses that may be incurred by the Executive on account of non-compliance with Section 409A.
Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).
Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.
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 …………………………………………………… .
Contractual and Operational Compliance Audits (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and (b) use commercially reasonable efforts to conduct such audit during regular business hours and in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information reasonably necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than ten (10) calendar days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15.
Performance and Compliance Purchaser shall have performed all of the covenants and complied, in all material respects, with all the provisions required by this Agreement to be performed or complied with by it on or before the Closing.
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. 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.
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.
Compliance Control Services (1) Support reporting to regulatory bodies and support financial statement preparation by making the Fund's accounting records available to the Trust, the Securities and Exchange Commission (the “SEC”), and the independent accountants. (2) Maintain accounting records according to the 1940 Act and regulations provided thereunder. (3) Perform its duties hereunder in compliance with all applicable laws and regulations and provide any sub-certifications reasonably requested by the Trust in connection with any certification required of the Trust pursuant to the Xxxxxxxx-Xxxxx Act of 2002 (the “SOX Act”) or any rules or regulations promulgated by the SEC thereunder, provided the same shall not be deemed to change USBFS’s standard of care as set forth herein. (4) Cooperate with the Trust’s independent accountants and take all reasonable action in the performance of its obligations under this Agreement to ensure that the necessary information is made available to such accountants for the expression of their opinion on the Fund’s financial statements without any qualification as to the scope of their examination.
Standards Compliance Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).
