Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.
Termination Notice for Force Majeure Event If a Force Majeure Event subsists for a period of 180 (one hundred and eighty) days or more within a continuous period of 365 (three hundred and sixty five) days, either Party may in its discretion terminate this Agreement by issuing a Termination Notice to the other Party without being liable in any manner whatsoever, save as provided in this Article 34, and upon issue of such Termination Notice, this Agreement shall, notwithstanding anything to the contrary contained herein, stand terminated forthwith; provided that before issuing such Termination Notice, the Party intending to issue the Termination Notice shall inform the other Party of such intention and grant 15 (fifteen) days time to make a representation, and may after the expiry of such 15 (fifteen) days period, whether or not it is in receipt of such representation, in its sole discretion issue the Termination Notice.
What if a Prohibited Transaction Occurs If a “prohibited transaction”, as defined in Section 4975 of the Internal Revenue Code, occurs, the Xxxxxxxxx Education Savings Account could be disqualified. Rules similar to those that apply to Traditional IRAs will apply.
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.
Notification of Anticipatory Breach Vendor agrees that should it, for any reason, not be able to provide or maintain appropriate safeguards to fulfill its obligations under this Section, it will immediately inform Citizens in writing of such inability and such inability on Vendor’s part will serve as justification for Citizens’ termination of this Agreement, at Citizens’ sole election, at any time after the inability becomes known to Citizens.
Payment in the Event Losses Fail to Reach Expected Level On the date that is 45 days following the last day (such day, the “True-Up Measurement Date”) of the calendar month in which the tenth anniversary of the calendar day following the Bank Closing occurs, the Assuming Bank shall pay to the Receiver fifty percent (50%) of the excess, if any, of (i) twenty percent (20%) of the Stated Threshold less (ii) the sum of (A) twenty-five percent (25%) of the asset premium (discount) plus (B) twenty-five percent (25%) of the Cumulative Shared-Loss Payments plus (C) the Cumulative Servicing Amount. The Assuming Bank shall deliver to the Receiver not later than 30 days following the True-Up Measurement Date, a schedule, signed by an officer of the Assuming Bank, setting forth in reasonable detail the calculation of the Cumulative Shared-Loss Payments and the Cumulative Servicing Amount.
Notification of Incidents If Contractor becomes aware of or has reasonable suspicion of a privacy incident or security incident regarding any State data, Contractor must report such incident to the State and the State Chief Information Security Officer as soon as possible, but no later than twenty-four (24) hours after such incident. The decision to notify the affected data subjects and the form of such notice following report of a privacy incident or security incident are the responsibility of the State. Notwithstanding anything to the contrary in this Contract, Contractor will indemnify, hold harmless and defend the State and its officers, and employees for and against any claims, damages, costs and expenses related to any privacy incident or security incident involving any State data. For purposes of clarification, the foregoing sentence shall in no way limit or diminish Contractor’s obligation(s) to indemnify, save, hold harmless, or defend the State under any other term of this Contract. Contractor will reasonably mitigate any harmful effects resulting from any privacy incident or security incident involving any State data.
Available Relief for a Force Majeure Event 11.7.1 Subject to this Article 11: (a) no Party shall be in breach of its obligations pursuant to this Agreement except to the extent that the performance of its obligations was prevented, hindered or delayed due to a Force Majeure Event; (b) every Party shall be entitled to claim relief in relation to a Force Majeure Event in regard to its obligations, including but not limited to those specified under Article 4.5; (c) For avoidance of doubt, neither Party’s obligation to make payments of money due and payable prior to occurrence of Force Majeure events under this Agreement shall be suspended or excused due to the occurrence of a Force Majeure Event in respect of such Party. (d) Provided that no payments shall be made by either Party affected by a Force Majeure Event for the period of such event on account of its inability to perform its obligations due to such Force Majeure Event.
Default under Specified Transaction The party, any Credit Support Provider of such party or any applicable Specified Entity of such party (1) defaults under a Specified Transaction and, after giving effect to any applicable notice requirement or grace period, there occurs a liquidation of, an acceleration of obligations under, or an early termination of, that Specified Transaction, (2) defaults, after giving effect to any applicable notice requirement or grace period, in making any payment or delivery due on the last payment, delivery or exchange date of, or any payment on early termination of, a Specified Transaction (or such default continues for at least three Local Business Days if there is no applicable notice requirement or grace period) or (3) disaffirms, disclaims, repudiates or rejects, in whole or in part, a Specified Transaction (or such action is taken by any person or entity appointed or empowered to operate it or act on its behalf);
Error Incident An Error Incident is a single or series of NAV Errors that results from the same act, omission, or use of incorrect data. NAV Errors will be corrected as follows: · If an NAV Error is less than ½ of 1% of NAV and results in a Net Benefit, the fund will retain the benefit. · If an NAV Error is less than ½ of 1% of NAV and results in a Net Loss, the Net Loss will be paid to the fund by the party responsible for causing the NAV Error. · In the case of a Material NAV Error, shareholder transactions/accounts will be corrected/ reprocessed at the corrected (restated) NAV, subject to a $10 per-account correction minimum threshold; any residual Net Benefit after correction of shareholder accounts will be retained by the fund and any residual Net Loss (resulting from uncorrected accounts below the $10 minimum threshold) will be paid to the fund by the party responsible for causing the error. If an NAV error is not caused by either the fund accounting agent or TRP, both TRP and the fund accounting agent will provide all reasonable assistance to the fund in its attempt to recover all costs from the responsible third party. · Notwithstanding any contractual provisions to the contrary, to the extent a NAV Error was caused by the actions or omissions of the fund’s accounting agent, any Net Loss or residual Net Loss equal to $5,000 or less that results from the same Error Incident will be paid by the accounting agent. TRP will be responsible for summarizing and reporting to the funds’ Audit Committee or Trust Company’s Board (or designated committee), as applicable, all NAV Errors related to the funds/trusts in conjunction with other relevant error statistics on a quarterly basis. The report will include corrected NAV Errors as well as the aggregate effect of any uncorrected NAV Errors. The report will also include information about shareholder accounts that were corrected in the discretion of TRP in the case of an NAV Error that is not a Material NAV Error. The funds’ Audit Committee and the Trust Company’s Board shall have the authority to adjust these procedures with respect to the funds and trusts, respectively, to the extent necessary or desirable to address NAV Errors by providing notice thereof to TRP and the fund’s accounting agent.
