Non Compliance and Charges Sample Clauses

Non Compliance and Charges 
AutoNDA by SimpleDocs

Related to Non Compliance and Charges

  • COMPLIANCE AND CERTIFICATION 25.1 Each Party shall comply at its own expense with all Applicable Laws that relate to that Party’s obligations to the other Party under this Agreement. Nothing in this Agreement shall be construed as requiring or permitting either Party to contravene any mandatory requirement of Applicable Law.

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

  • Record Maintenance and Retention A. Grantee shall keep and maintain under GAAP or GASB, as applicable, full, true, and complete records necessary to fully disclose to the System Agency, the Texas State Auditor’s Office, the United States Government, and their authorized representatives sufficient information to determine compliance with the terms and conditions of this Grant Agreement and all state and federal rules, regulations, and statutes.

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.

  • Operating and Maintenance Manuals 58.1 If “as built” Drawings and/or operating and maintenance manuals are required, the Contractor shall supply them by the dates stated in the Contract Data.

  • Standards Compliance DNS. 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”).

  • Maintenance and Testing 54.5.1. Sprint is only responsible for maintaining the facilities that it owns.

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

  • Records Maintenance and Access Grantee must maintain all financial records relating to this Grant in accordance with generally accepted accounting principles. In addition, Grantee must maintain any other records, whether in paper, electronic or other form, pertinent to this Grant in such a manner as to clearly document Grantee’s performance. All financial records and other records, whether in paper, electronic or other form, that are pertinent to this Grant, are collectively referred to as “Records.” Grantee acknowledges and agrees Agency and the Oregon Secretary of State's Office and the federal government and their duly authorized representatives will have access to all Records to perform examinations and audits and make excerpts and transcripts. Grantee must retain and keep accessible all Records for a minimum of six (6) years, or such longer period as may be required by applicable law, following termination of this Grant, or until the conclusion of any audit, controversy or litigation arising out of or related to this Grant, whichever date is later.

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