Reporting of Noncompliance Events from the previous month. 12 At the monthly progress meetings, Developer shall submit the Monthly Progress Report to 13 ADOT.
Reporting of Noncompliance Events from the previous month Sample Clauses
Related to Reporting of Noncompliance Events from the previous month
Annual Statement as to Compliance, Notice of Servicer Termination Event (a) To the extent required by Section 1123 of Regulation AB, the Servicer, shall deliver to the Trustee, the Owner Trustee, the Trust Collateral Agent, the Backup Servicer and each Rating Agency, on or before March 31 of each year (regardless of whether the Seller has ceased filing reports under the Exchange Act), beginning on March 31, 2012, an officer’s certificate signed by any Responsible Officer of the Servicer, dated as of December 31 of the previous calendar year, stating that (i) a review of the activities of the Servicer during the preceding calendar year (or such other period as shall have elapsed from the Closing Date to the date of the first such certificate) and of its performance under this Agreement has been made under such officer’s supervision, and (ii) to such officer’s knowledge, based on such review, the Servicer has fulfilled in all material respects all its obligations under this Agreement throughout such period, or, if there has been a failure to fulfill any such obligation in any material respect, identifying each such failure known to such officer and the nature and status of such failure. (b) The Servicer shall deliver to the Trustee, the Owner Trustee, the Trust Collateral Agent, the Backup Servicer and each Rating Agency, promptly after having obtained knowledge thereof, but in no event later than two (2) Business Days thereafter, written notice in an officer’s certificate of any event which with the giving of notice or lapse of time, or both, would become a Servicer Termination Event under Section 9.1(a). The Seller or the Servicer shall deliver to the Trustee, the Owner Trustee, the Trust Collateral Agent, the Backup Servicer, the Servicer or the Seller (as applicable) and each Rating Agency promptly after having obtained knowledge thereof, but in no event later than two (2) Business Days thereafter, written notice in an officer’s certificate of any event which with the giving of notice or lapse of time, or both, would become a Servicer Termination Event under any other clause of Section 9.1. (c) The Servicer will deliver to the Issuer, on or before March 31 of each year, beginning on March 31, 2012, a report regarding the Servicer’s assessment of compliance with certain minimum servicing criteria during the immediately preceding calendar year, as required under Rules 13a-18 and 15d-18 of the Exchange Act and Item 1122 of Regulation AB. (d) To the extent required by Regulation AB, the Servicer will cause any affiliated servicer or any other party deemed to be participating in the servicing function pursuant to Item 1122 of Regulation AB to provide to the Issuer, on or before March 31 of each year, beginning on March 31, 2012, a report regarding such party’s assessment of compliance with certain minimum servicing criteria during the immediately preceding calendar year, as required under Rules 13a-18 and 15d-18 of the Exchange Act and Item 1122 of Regulation AB. (e) Xxxxx Fargo Bank, National Association acknowledges, in its capacity as Backup Servicer and Trust Collateral Agent under this Agreement and in its capacity as Indenture Trustee under the Basic Documents, that to the extent it is deemed to be participating in the servicing function pursuant to Item 1122 of Regulation AB, it will take any action reasonably requested by the Servicer to ensure compliance with the requirements of Section 4.10(d) and Section 4.11(b) hereof and with Item 1122 of Regulation AB. Such required documentation will be delivered to the Servicer by March 15 of each calendar year.
Reporting of Compliance Matters (a) The Sub-Adviser shall promptly provide to the Trust’s Chief Compliance Officer (“CCO”) the following documents: (i) copies of all SEC examination correspondences, including correspondences regarding books and records examinations and “sweep” examinations, issued during the term of this Agreement, in which the SEC identified any concerns, issues or matters (such correspondences are commonly referred to as “deficiency letters”) relating to any aspect of the Sub-Adviser’s investment advisory business and the Sub-Adviser’s responses thereto; (ii) a report of any material violations of the Sub-Adviser’s Compliance Program or any “material compliance matters” (as such term is defined in Rule 38a-1 under the 0000 Xxx) that have occurred with respect to the Sub-Adviser’s Compliance Program; (iii) a report of any material changes to the policies and procedures that compose the Sub-Adviser’s Compliance Program; (iv) a copy of the Sub-Adviser’s chief compliance officer’s report (or similar document(s) which serve the same purpose) regarding his or her annual review of the Sub-Adviser’s Compliance Program, as required by Rule 206(4)-7 under the Advisers Act; and (v) an annual (or more frequently as the Trust’s CCO may reasonably request) representation regarding the Sub-Adviser’s compliance with Paragraphs 7 and 8 of this Agreement. (b) The Sub-Adviser shall also provide the Trust’s CCO with: (i) reasonable access to the testing, analyses, reports and other documentation, or summaries thereof, that the Sub-Adviser’s chief compliance officer relies upon to monitor the effectiveness of the implementation of the Sub-Adviser’s Compliance Program; and (ii) reasonable access, during normal business hours, to the Sub-Adviser’s facilities for the purpose of conducting pre-arranged on-site compliance related due diligence meetings with personnel of the Sub-Adviser.
Waiver of Past Events of Servicing Termination The Holders of Notes evidencing not less than 51% of the Note Balance of the Controlling Class may, on behalf of all Noteholders, waive any Event of Servicing Termination and its consequences, except an event resulting from the failure to make any required deposits to or payments from the Collection Account, the Note Payment Account, the Certificate Payment Account or the Reserve Account in accordance with this Agreement. Upon any such waiver of an Event of Servicing Termination, such event shall cease to exist, and shall be deemed to have been remedied for every purpose of this Agreement. No such waiver shall extend to any subsequent or other event or impair any right arising therefrom, except to the extent expressly so waived.
Certification Regarding Termination of Contract for Non-Compliance (Tex Gov. Code 552.374)
Compliance Certificate; Statements as to Defaults The Company shall deliver to the Trustee within 120 days after the end of each fiscal year of the Company (beginning with the fiscal year ending on December 31, 2020) an Officer’s Certificate stating whether the signers thereof have knowledge of any failure by the Company to comply with all conditions and covenants then required to be performed under this Indenture and, if so, specifying each such failure and the nature thereof. In addition, the Company shall deliver to the Trustee, as soon as possible, and in any event within 30 days after the occurrence of any Event of Default or Default, an Officer’s Certificate setting forth the details of such Event of Default or Default, its status and the action that the Company is taking or proposing to take in respect thereof.
Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include: (a) accident, death or severe injury to any person; (b) damaged or dislodged fixed equipment; (c) flooding of Project Highway; and (d) any other unusual occurrence.
Reporting Covenant Required Complies Quarterly consolidating financial statements Quarterly within 45 days Yes No Annual financial statement (CPA Audited) FYE within 150 days Yes No 10‑Q, 10‑K and 8-K Within 5 days after filing with SEC Yes No Quarterly Compliance Certificate Contemporaneously with delivery ofthe 10-Q and 10-K Yes No Annual operating budgets and annual financial projections FYE within 45 days Yes No
SUBMISSION OF THE MONTHLY MI REPORT 4.1 The completed MI Report shall be completed electronically and returned to the Authority by uploading the electronic MI Report computer file to MISO in accordance with the instructions provided in MISO. 4.2 The Authority reserves the right (acting reasonably) to specify that the MI Report be submitted by the Supplier using an alternative communication to that specified in paragraph 4.1 above such as email. The Supplier agrees to comply with any such instructions provided they do not materially increase the burden on the Supplier.
Covenant Compliance Certificate The Borrower shall, contemporaneously with the furnishing of the financial statements pursuant to Section 8.8, deliver to the Bank a duly completed compliance certificate, dated the date of such financial statements and certified as true and correct by an appropriate officer of the Borrower, containing a computation of each of the financial covenants set forth in Section 10 and stating that the Borrower has not become aware of any Event of Default or Unmatured Event of Default that has occurred and is continuing or, if there is any such Event of Default or Unmatured Event of Default describing it and the steps, if any, being taken to cure it.
Reporting of Reportable Events If Xxxxx determines (after a reasonable opportunity to conduct an appropriate review or investigation of the allegations) through any means that there is a Reportable Event, Xxxxx shall notify OIG, in writing, within 30 days after making the determination that the Reportable Event exists.
