Compliance Extensions Sample Clauses

Compliance Extensions. A. Modify Section 63.863 of the proposed rule as follows: 1. Modify 63.863(a) to read: “The owner or operator of an existing affected source shall comply with the requirements in this subpart no later than [insert date 3 years after the effective date of the final rule], except as specified in paragraph (c) of this section. 2. Add paragraph (c) to Section 63.863 to specify the types of possible compliance extensions for the Big Island facility’s existing smelters. (See next page for more detail on this paragraph). 3. Add three subparagraphs to Section 63.867(a) - Notifications - to describe the notices G-P must provide to appropriately document the need for any of the compliance extensions from 63.863(c). (See next page for more detail on this paragraph).
AutoNDA by SimpleDocs
Compliance Extensions. A. Modify Section 63.863 of the proposed rule as follows: 1. Modify 63.863(a) to read: “The owner or operator of an existing affected source shall comply with the requirements in this subpart no later than [insert date 3 years after the effective date of the final rule], except as specified in paragraph

Related to Compliance Extensions

  • Additional Compliance If any Proposed Key Holder Transfer is not consummated within forty-five (45) days after receipt of the Proposed Transfer Notice by the Company, the Key Holders proposing the Proposed Key Holder Transfer may not sell any Transfer Stock unless they first comply in full with each provision of this Section 2. The exercise or election not to exercise any right by any Investor hereunder shall not adversely affect its right to participate in any other sales of Transfer Stock subject to this Section 2.2.

  • Compliance; Modification The Asset Representations Reviewer will cooperate with and provide information to the Issuer regarding the Asset Representations Reviewer’s compliance with this Section 4.10. The Asset Representations Reviewer and the Issuer agree to modify this Section 4.10 as necessary from time to time for either party to comply with applicable law.

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

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

  • Monitoring Compliance Upon the request of the Lender, but without incurring any liability beyond the Guaranteed Obligations, from time to time, Guarantor shall promptly provide to the Lender such documents, certificates and other information as may be deemed reasonably necessary to enable the Lender to perform its functions under the Servicing Agreement as the same relates to the Guarantor.

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

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

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

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

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

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