The Board’s Compliance Sample Clauses

The Board’s Compliance. The University agrees, at any time and from time to time, upon not less than thirty (30) days prior written notice by the Corporation, to execute, acknowledge and deliver to the Corporation a statement in writing addressed to the Corporation or to such other party as the Corporation shall request, certifying (a) that this Ground Lease is unmodified and in full force and effect (or if there have been modifications that the same is in full force and effect as modified and stating the modifications); (b) the dates to which the Rent and other charges have been paid; (c) to the best of its knowledge after due inquiry, whether an Event of Default has occurred and is continuing hereunder (and stating the nature of any such Event of Default); (d) during the construction period, the status of construction of the Facilities and the estimated date of completion thereof; and (e) the dates of commencement and expiration of the Term, it being intended that any such statement delivered pursuant to this Section may be relied upon by any prospective (and permitted) assignee, sublessee or mortgagee of this Ground Lease or by any assignee or prospective assignee of any such permitted mortgage or by any undertenant or prospective undertenant of the whole or any part of the Facilities, or by any other Person.
Sample 1
AutoNDA by SimpleDocs

Related to The Board’s Compliance

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

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

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

  • OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.

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

  • DBE/HUB Compliance The Engineer’s subcontracting program shall comply with the requirements of Attachment H of the contract (DBE/HUB Requirements).

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

  • ETHICS COMPLIANCE All Bidders/Contractors and their employees must comply with the requirements of Sections 73 and 74 of the Public Officers Law, other State codes, rules, regulations and executive orders establishing ethical standards for the conduct of business with New York State. In signing the Bid, Bidder certifies full compliance with those provisions for any present or future dealings, transactions, sales, contracts, services, offers, relationships, etc., involving New York State and/or its employees. Failure to comply with those provisions may result in disqualification from the Bidding process, termination of contract, and/or other civil or criminal proceedings as required by law.

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

  • Permit Compliance Such Party fails to obtain and maintain in full force and effect any Permit (other than the Regulatory Approval) necessary for such Party to perform its obligations under this Agreement.

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