Program Operations Compliance Sample Clauses

Program Operations Compliance 
AutoNDA by SimpleDocs

Related to Program Operations Compliance

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

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

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

  • Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.

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

  • CRA Compliance Neither Buyer nor any Buyer Subsidiary has received any notice of non-compliance with the applicable provisions of the CRA and the regulations promulgated thereunder. As of the date hereof, Buyer Sub received a CRA rating of “satisfactory” or better from the FDIC in its most recent examination. Buyer knows of no fact or circumstance or set of facts or circumstances which would be reasonably likely to cause Buyer or any Buyer Subsidiary to receive any notice of non-compliance with such provisions or cause the CRA rating of Buyer or any Buyer Subsidiary to decrease below the “satisfactory” level.

  • FDA Compliance The Company: (A) is and at all times has been in material compliance with all statutes, rules or regulations of the FDA and other comparable governmental entities applicable to the ownership, testing, development, manufacture, packaging, processing, use, distribution, marketing, labeling, promotion, sale, offer for sale, storage, import, export or disposal of any product under development, manufactured or distributed by the Company (“Applicable Laws”); (B) has not received any FDA Form 483, notice of adverse finding, warning letter, untitled letter or other correspondence or notice from the FDA or any governmental entity alleging or asserting material noncompliance with any Applicable Laws or any licenses, certificates, approvals, clearances, exemptions, authorizations, permits and supplements or amendments thereto required by any such Applicable Laws (“Authorizations”); (C) possesses all material Authorizations and such Authorizations are valid and in full force and effect and the Company is not in material violation of any term of any such Authorizations; (D) has not received notice of any claim, action, suit, proceeding, hearing, enforcement, investigation, arbitration or other action from the FDA or any governmental entity or third party alleging that any product operation or activity is in material violation of any Applicable Laws or Authorizations and has no knowledge that the FDA or any governmental entity or third party is considering any such claim, litigation, arbitration, action, suit, investigation or proceeding; (E) has not received notice that the FDA or any governmental entity has taken, is taking or intends to take action to limit, suspend, modify or revoke any material Authorizations and has no knowledge that the FDA or any governmental entity is considering such action; and (F) has filed, obtained, maintained or submitted all material reports, documents, forms, notices, applications, records, claims, submissions and supplements or amendments as required by any Applicable Laws or Authorizations and that all such reports, documents, forms, notices, applications, records, claims, submissions and supplements or amendments were materially complete and correct on the date filed (or were corrected or supplemented by a subsequent submission).

  • Permits; Compliance The Company and each of its Subsidiaries is in possession of all franchises, grants, authorizations, licenses, permits, easements, variances, exemptions, consents, certificates, approvals and orders necessary to own, lease and operate its properties and to carry on its business as it is now being conducted (collectively, the “Company Permits”), and there is no action pending or, to the knowledge of the Company, threatened regarding suspension or cancellation of any of the Company Permits. Neither the Company nor any of its Subsidiaries is in conflict with, or in default or violation of, any of the Company Permits, except for any such conflicts, defaults or violations which, individually or in the aggregate, would not reasonably be expected to have a Material Adverse Effect. Since September 30, 2016, neither the Company nor any of its Subsidiaries has received any notification with respect to possible conflicts, defaults or violations of applicable laws, except for notices relating to possible conflicts, defaults or violations, which conflicts, defaults or violations would not have a Material Adverse Effect.

  • SOX Compliance The Company has taken all actions it deems reasonably necessary or advisable to take on or prior to the date of this Agreement to assure that, upon and at all times after the Effective Date, it will be in compliance in all material respects with all applicable provisions of the Sxxxxxxx-Xxxxx Act of 2002 and all rules and regulations promulgated thereunder or implementing the provisions thereof. (the “Sxxxxxxx-Xxxxx Act”) that are then in effect and will take all action it deems reasonably necessary or advisable to assure that it will be in compliance in all material respects with other applicable provisions of the Sxxxxxxx-Xxxxx Act not currently in effect upon it and at all times after the effectiveness of such provisions.

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

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