Collateral incident Sample Clauses

Collateral incident. 1. A collateral incident occurs in the following cases: (a) the collaterals are insufficient to secure the amount due for the Long Term Transmission Rights held by a Registered Participant on the next payment date as set forth in Article 65 considering the amount and the validity of the collaterals; or (b) the collaterals are not renewed in accordance with Article 22 paragraph 2; or (c) the collaterals are not restored after a payment incident in accordance with Article 26 or new collateral was provided that is not compliant with the conditions specified in Article 19(3), Article 20 and Article 21. 2. The Allocation Platform shall notify the collaterals incident to the Registered Participant by email. The Registered Participant shall increase its collaterals within two (2) Working Days from sending of the notification if this is done during Working Hours or two (2) Working Days starting from the next Working Day if sent after Working Hours. If the collaterals provided by the Registered Participant remains insufficient after this period, the Allocation Platform may suspend or terminate the Participation Agreement in accordance with Article 71 and Article 72.
AutoNDA by SimpleDocs
Collateral incident. 1. A collateral incident occurs in the following cases: a. the collaterals are insufficient to secure the amount due for the Transmission Rights held by a Registered Participant on the next payment date as set forth in Article 52 considering the amount and the validity of the collaterals; or b. the collaterals are not renewed in accordance with Article 20 paragraph 2; or c. the collaterals are not restored after a payment incident in accordance with Article 24 or new collateral was provided that is not compliant with the conditions specified in Articles 17(3), 18 and 19. 2. The Allocation Platform shall notify the collaterals incident to the Registered Participant by electronic means as specified by the Allocation Platform on its website. The Registered Participant shall increase its collaterals within two (2) Working Days from sending of the notification if this is done during Working Hours or two (2) Working Days starting from the next Working Day if sent after Working Hours. If the collaterals provided by the Registered Participant remains insufficient after this period, the Allocation Platform may suspend or terminate the Participation Agreement in accordance with Articles 58 and 59.
Collateral incident. 1. A collateral incident occurs in the following cases: (a) the collaterals are insufficient to secure the amount due for the Intraday Transmission Rights held by a Registered Participant on the next payment date as set forth in Article 45 considering the amount and the validity of the collaterals; or (b) the collaterals are not renewed in accordance with Article 20 paragraph 2; or (c) the collaterals are not restored after a payment incident in accordance with Article 24 or new collateral was provided that is not compliant with the conditions specified in Articles 17 paragraph 3, 18 and 19. 2. Without prejudice to the other rights of the Allocation Platform, the Allocation Platform shall notify the collateral incident to the Registered Participant by electronic means as specified by the Allocation Platform on its website. The Registered Participant shall increase its collaterals within two (2) Working Days from sending of the notification if this is done during Working Hours or two (2) Working Days starting from the next Working Day if sent after Working Hours. If the provided collaterals by the Registered Participant remain insufficient after this period, the Allocation Platform may suspend or terminate the Participation Agreement in accordance with Article 51 and Article 52.
Collateral incident. 1. A collateral incident occurs in the following cases: (a) the collaterals are insufficient to secure the amount due for the Long Term Transmission Rights held by a Registered Participant on the next payment date as set forth in Article 65 considering the amount and the validity of the collaterals; or (b) the collaterals are not renewed in accordance with Article 22 paragraph 2; or (c) the collaterals are not restored after a payment incident in accordance with Article 26 or new collateral was provided that is not compliant with the conditions specified in Article 19(3), Article 20 and Article 21.
Collateral incident. ‌ 1. A collateral incident occurs in the following cases: (a) the collaterals are insufficient to secure the amount due for the Transmission Righttransmission rights held by a Registered Participantregistered participant on the next payment date as set forth in Article 52 considering the amount and the validity of the collaterals; or (b) the collaterals are not renewed in accordance with Article 20 paragraph 2; or (c) the collaterals are not restored after a payment incident in accordance with Article 24 or new collateral was provided that is not compliant with the conditions specified in Articles 17(3), 18 and 19. 2. The Allocation Platformallocation platform shall notify the collaterals incident to the Registered Participantregistered participant by electronic means as specified by the Allocation Platformallocation platform on its website. The Registered Participantregistered participant shall increase its collaterals within two (2) Working Dayworking days from sending of the notification if this is done during Working Hourworking hours or two (2) Working Dayworking days starting from the next Working Dayworking day if sent after Working Hourworking hours. If the collaterals provided by the Registered Participantregistered participant remains insufficient after this period, the Allocation Platformallocation platform may suspend or terminate the Participation Agreementparticipation agreement in accordance with Articles 58 and 59.
Collateral incident. 1. A collateral incident occurs in the following cases: (a) the collaterals are insufficient to secure the amount due for the Long Term Transmission Rights held by a Registered Participant on the next payment date as set forth in Article 65 considering the amount and the validity of the collaterals; or (b) the collaterals are not renewed in accordance with Article 21 paragraph 2; or (c) the collaterals are not restored after a payment incident in accordance with Article 25 or new collateral was provided that is not compliant with the conditions specified in Article 18 paragraph 3, Article 19 and Article 20. 2. Without prejudice to the other rights of the Allocation Platform, the Allocation Platform shall notify the collaterals incident to the Registered Participant by electronic means as specified by the Allocation Platform on its website. The Registered Participant shall increase its collaterals within two (2) Working Days from sending of the notification if this is done during Working Hours or two
Collateral incident. 1. A collateral incident occurs in the following cases: (a) the collaterals are insufficient to secure the amount due for the Transmission Rights held by a Registered Participant on the next payment date as set forth in Rule 76 considering the amount and the validity of the collaterals; or (b) the collaterals are not renewed in accordance with Rules 21A and 21B paragraph 2; or (c) the collaterals are not restored after a payment incident in accordance with Rule 25 or new collateral was provided that is not compliant with the conditions specified in Rule 18(3), Rule 19 and Rule 20. 2. The Allocation Platform shall notify the collateral incident to the Registered Participant by electronic means as specified by the Allocation Platform on its website. The Registered Participant shall increase its collaterals within two (2) Working Days from the sending of the notification if this is done during Working Hours or two (2) Working Days starting from the next Working Day if sent after Working Hours. If the collateral provided by the Registered Participant remains insufficient after this period, the Allocation Platform may suspend or terminate the Allocation Platform Participation Agreement in accordance with Rule 83 and Rule 84. 1. The Allocation Platform is entitled to call upon collaterals of a Registered Participant in the event of a registered payment incident in accordance with Rule 79 in relation to any sum invoiced under these Access Rules that a Registered Participant has failed to pay by the due date for payment. 2. The Registered Participant shall restore its collaterals after a payment incident or collateral incident by following the conditions as set forth in Rule 18(3), Rule 19 and Rule 20 unless the Allocation Platform Participation Agreement is suspended or terminated in accordance with Rule 83 or Rule 84. 1. The Allocation Platform shall allocate Transmission Rights to Registered Participants by way of explicit Allocation. Prior to the Auction, the Allocation Platform shall publish Auction Specifications on its website. 2. The Auctions shall be organised via the Auction Tool. Each Registered Participant fulfilling the requirements for participating in the Auction may place Bids in the Auction Tool until the Bidding Period for the specific Auction expires according to the respective Auction Specification. 3. After the Bidding Period for the specific Auction has expired, the Allocation Platform shall evaluate the Bids including against the respective ...
AutoNDA by SimpleDocs
Collateral incident. 1. A collateral incident occurs in the following cases: (a) the collaterals are insufficient to secure the amount due for the Daily Transmission Rights held by a Registered Participant on the next payment date as set forth in Article 53 considering the amount and the validity of the collaterals; or (b) the collaterals are not restored after a payment incident in accordance with Article 24 or new collateral was provided that is not compliant with the conditions specified in Articles 17(3), 18 and 19. 2. The Allocation Platform shall notify the collaterals incident to the Registered Participant by email. The Registered Participant shall increase its collaterals within two (2) Working Days from sending of the notification if this is done during Working Hours or two (2) Working Days starting from the next Working Day if sent after Working Hours. If the collaterals provided by the Registered Participant remain insufficient after this period, the Allocation Platform may suspend or terminate the Participation Agreement in accordance with Articles 59 and 60.
Collateral incident. ‌ 1. A collateral incident occurs in the following cases: (a) the collaterals are insufficient to secure the amount due for the transmission rights held by a registered participant on the next payment date as set forth in Article 52 considering the amount and the validity of the collaterals; or (b) the collaterals are not renewed in accordance with Article 20 paragraph 2; or (c) the collaterals are not restored after a payment incident in accordance with Article 24 or new collateral was provided that is not compliant with the conditions specified in Articles 17(3), 18 and 19. 2. The allocation platform shall notify the collaterals incident to the registered participant by electronic means as specified by the allocation platform on its website. The registered participant shall increase its collaterals within two (2) working days from sending of the notification if this is done during working hours or two (2) working days starting from the next working day if sent after working hours. If the collaterals provided by the registered participant remains insufficient after this period, the allocation platform may suspend or terminate the participation agreement in accordance with Articles 58 and 59.

Related to Collateral incident

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

  • Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.

  • Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

  • Security Incident Notification The Transfer Agent shall promptly notify the Trust but in no event later than 72 hours following discovery of any Security Incident(s). Such notification shall include the extent and nature of such intrusion, disclosure, or unauthorized access, the identity of the compromised Customer Confidential Information (to the extent it can be ascertained), how the Transfer Agent was affected by the Security Incident, and its response to such Security Incident. The Transfer Agent shall use continuous and diligent efforts to remedy the cause and the effects of such Security Incident in an expeditious manner and deliver to the Trust a root cause analysis and future incident Mitigation plan with regard to any such incident. The Transfer Agent shall reasonably cooperate with the Trust’s investigation and response to each Security Incident. If the Trust determines in its sole discretion that it may need or be required to notify any individual(s) as a result of a Security Incident, the Trust shall have the right to control all such notifications and the Transfer Agent shall bear all direct costs associated with the notification, to the extent the notification and corresponding actions are required by U.S. law, and subject to the limitation of liability set forth in the Agreement. Without limiting the foregoing, unless otherwise required by U.S. law, no such notifications shall be made by the Transfer Agent without the Trust’s prior written consent and the Trust shall, together with the Transfer Agent, determine the content and delivery of all such notifications. For the avoidance of doubt, the Transfer Agent shall be solely responsible for all costs and expenses, subject to the limitations of liability under the Agreement that the Trust and/or the Transfer Agent may incur to the extent that they are attributable to or arise from the Transfer Agent’s breach of its confidentiality obligations under the Agreement.

  • Security Incident Reporting A security incident occurs when CDA information assets are or reasonably believed to have been accessed, modified, destroyed, or disclosed without proper authorization, or are lost, or stolen. Subrecipient must comply with CDA’s security incident reporting procedures located at xxxxx://xxx.xxxxx.xx.xxx/ProgramsProviders/#Resources.

  • Collateral Event In the event that either (a) the Advisor does not make the Fund Reimbursement Payment due in connection with a particular calendar month by the tenth day of the following calendar month or (b) the Board enacts a resolution calling for the liquidation of the Fund (either (a) or (b), a “Collateral Event”), then, in either event, the Board shall have absolute discretion to redeem any shares or other Collateral held in the Collateral Account and utilize the proceeds from such redemptions or such other Collateral to make any required Fund Reimbursement Payment, or to cover any costs or expenses which the Board, in its sole and absolute discretion, estimates will be required in connection with the liquidation of the Fund (the “Liquidation Expenses”). Pursuant to the terms of Paragraph 6 of this Agreement, upon authorization from the Board, but subject to the provisions of the Control Agreement, no further instructions shall be required from the Advisor for the Securities Intermediary to transfer any Collateral from the Collateral Account to the Fund. The Advisor acknowledges that in the event the Collateral available in the Collateral Account is insufficient to cover the full cost of any Fund Reimbursement Payment or Liquidation Expenses, the Fund shall retain the right to receive from the Advisor any costs in excess of the value of the Collateral.

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

  • Ratings Event Upon the occurrence of a Ratings Event (as defined below) Party A has not, within 10 days after such rating withdrawal or downgrade (unless, within 10 days after such withdrawal or downgrade, each such Swap Rating Agency has reconfirmed the rating of the Swap Certificates which was in effect immediately prior to such withdrawal or downgrade (determined without regard to any financial guaranty insurance policy, if applicable), unless the rating of the Swap Certificates were changed due to a circumstance other than the withdrawal or downgrading of Party A's (or its Credit Support Provider's) rating), complied with one of the solutions listed below, then an Additional Termination Event shall have occurred with respect to Party A and Party A shall be the sole Affected Party with respect to such Additional Termination Event. It shall be a ratings event ("Ratings Event") if at any time after the date hereof Party A shall fail to satisfy the Swap Counterparty Ratings Threshold. Swap Counterparty Ratings Threshold shall mean that both (A) the unsecured, long-term senior debt obligations of Party A (or its Credit Support Provider) are rated at least "BBB-" by S&P, and (B) either (i) the unsecured, long-term senior debt obligations of Party A (or its Credit Support Provider) are rated at least "A2" by Moody's (including if such rating is on watch for possible downgrade) and the unsecured, short-term debt obligations of Party A (or its Credit Support Provider) are rated at least "P-1" by Moody's (including if such rating is on watch for possible downgrade) or (ii) if Party A (or its Credit Support Provider) does not have a short-term rating from Moody's, the unsecured, long-term senior debt obligations of Party A (or its Credit Support Provider) are rated at least "A1" by Moody's (including if such rating is on watch for possible downgrade).

  • Breaches and Security Incidents During the term of the Agreement, CONTRACTOR 27 agrees to implement reasonable systems for the discovery of any Breach of unsecured DHCS PI and PII 28 or security incident. CONTRACTOR agrees to give notification of any beach of unsecured DHCS PI 29 and PII or security incident in accordance with subparagraph F, of the Business Associate Contract, 30 Exhibit B to the Agreement.

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