Early compliance of DLRs Sample Clauses

Early compliance of DLRs. If the Bank is satisfied that a DLR has been achieved, in a manner that it fully achieves a subsequent and respective DLR, the Bank may decide, in its sole discretion, to authorize the withdrawal of such amount allocated to said DLR, corresponding to the degree of achievement of said DLR.
AutoNDA by SimpleDocs

Related to Early compliance of DLRs

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

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

  • Performance or Compliance Audits The Department may conduct or have conducted performance and/or compliance audits of the Contractor and subcontractors as determined by the Department. The Department may conduct an audit and review all the Contractor’s and subcontractors’ data and records that directly relate to the Contract. To the extent necessary to verify the Contractor’s fees and claims for payment under the Contract, the Contractor’s agreements or contracts with subcontractors, partners, or agents of the Contractor, pertaining to the Contract, may be inspected by the Department upon fifteen (15) calendar days’ notice, during normal working hours and in accordance with the Contractor’s facility access procedures where facility access is required. Release statements from its subcontractors, partners, or agents are not required for the Department or its designee to conduct compliance and performance audits on any of the Contractor’s contracts relating to this Contract. The Inspector General, in accordance with section 5.6, the State of Florida’s Chief Financial Officer, the Office of the Auditor General also have authority to perform audits and inspections.

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

  • FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:

  • Law Compliance In providing the SOLID WASTE HANDLING SERVICES required by this AGREEMENT, CONTRACTOR shall observe and comply with all applicable federal and, state laws, regulations and codes regarding the provision of the SOLID WASTE HANDLING SERVICES described herein, as such may be amended from time to time, including where required by such laws, the funding and maintenance of sufficient closure and post-closure maintenance financial assurances for any landfill operated or utilized by CONTRACTOR for disposal of the SOLID WASTE. Any violation of this Paragraph shall constitute a major breach.

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

  • Legal Compliance Contractor represents and warrants that it shall secure all notices and comply with all applicable laws, ordinances, rules and regulations of any governmental entity in conjunction with the performance of obligations under the Contract. Prior to award and during the Contract term and any renewals thereof, Contractor must establish to the satisfaction of the Commissioner that it meets or exceeds all requirements of the Bid and Contract and any applicable laws, including but not limited to, permits, licensing, and shall provide such proof as required by the Commissioner. Failure to comply or failure to provide proof may constitute grounds for the Commissioner to terminate or suspend the Contract, in whole or in part, or to take any other action deemed necessary by the Commissioner. Contractor also agrees to disclose information and provide affirmations and certifications to comply with Sections 139-j and 139-k of the State Finance Law.

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