A Risk Event Occurs Sample Clauses

The 'A Risk Event Occurs' clause defines what constitutes a risk event within the context of the agreement and outlines the procedures that follow when such an event takes place. Typically, this clause specifies the types of incidents or circumstances that are considered risk events, such as natural disasters, accidents, or breaches, and details the notification and response obligations of the parties involved. Its core practical function is to ensure that both parties have a clear understanding of what triggers risk-related provisions in the contract, thereby facilitating prompt and coordinated responses to mitigate potential losses or liabilities.
A Risk Event Occurs. If a Risk Event occurs , (i) your rights in respect of all or a portion of your RSUs (whether or not Vested) will terminate and no RSU Shares will be delivered in respect of such RSUs, (ii) your rights to all or a portion of any Shares at Risk will terminate and such Shares at Risk will be cancelled and (iii) you will be obligated immediately upon demand therefor to pay the Firm an amount not in excess of the greater of the Fair Market Value of the RSU Shares (plus any dividend payments) delivered in respect of the Award (without reduction for any amount applied to satisfy tax withholding or other obligations) determined as of (A) the date the Risk Event occurred and (B) the date that the repayment request is made.
View SourceView Similar (9)
A Risk Event Occurs. If a Risk Event occurs , (i) your rights in respect of all or a portion of your Short-Term RSUs will terminate and no RSU Shares will be delivered in respect of such Short-Term RSUs and (ii) you will be obligated immediately upon demand therefor to pay the Firm an amount not in excess of the greater of the Fair Market Value of the RSU Shares (plus any dividend payments and payments under Dividend Equivalent Rights) delivered in respect of the Award (without reduction for any amount applied to satisfy tax withholding or other obligations) determined as of (A) the date the Risk Event occurred and (B) the date that the repayment request is made.
View SourceView Similar (3)
A Risk Event Occurs. If a Risk Event occurs , (i) your rights in respect of all or a portion of your PSUs will terminate and no Settlement Amount will be delivered in respect of such PSUs, (ii) your rights to all or a portion of any Shares at Risk will terminate and such Shares at Risk will be cancelled and (iii) you will be obligated immediately upon demand therefor to pay the Firm an amount not in excess of the greater of the Fair Market Value of the Shares (plus any dividend payments) delivered in respect of the Award (without reduction for any amount applied to satisfy tax withholding or other obligations) determined as of (A) the date the Risk Event occurred and (B) the date that the repayment request is made.
View SourceView Similar (3)
A Risk Event Occurs. Prior to the later of the last day of the Performance Period and , there occurs a loss of 5% or more of firmwide total capital from a reportable operational risk event determined in accordance with the firmwide Reporting Operational Risk Events Policy (a “Risk Event”).]
View Source
A Risk Event Occurs. [______________________]. If a Risk Event occurs [______________________], (i) your rights in respect of all or a portion of your RSUs (whether or not Vested) will terminate and no RSU Shares will be delivered in respect of such RSUs, (ii) your rights to all or a portion of any Shares at Risk will terminate and such Shares at Risk will be cancelled and (iii) you will be obligated immediately upon demand therefor to pay the Firm an amount not in excess of the greater of the Fair Market Value of the RSU Shares (plus any dividend payments) delivered in respect of the Award (without reduction for any amount applied to satisfy tax withholding or other obligations) determined as of (A) the date the Risk Event occurred and (B) the date that the repayment request is made.
View Source

Related to A Risk Event Occurs

  • Notification of Event of Default Borrower shall notify Agent immediately of the occurrence of any Event of Default.

  • Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-­‐level domain names identified by ICANN and set forth at <▇▇▇▇://▇▇▇▇▇▇▇▇.▇▇▇▇▇.▇▇▇/en/announcements-­‐and-­‐ media/announcement-­‐2-­‐17nov13-­‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-­‐OARC) <▇▇▇▇▇://▇▇▇.▇▇▇-­‐▇▇▇▇.▇▇▇/▇▇▇▇/▇▇▇▇/▇▇▇▇>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/groups/board/documents/resolutions-­‐ new-­‐gtld-­‐annex-­‐1-­‐07oct13-­‐en.pdf>.

  • Default Events (a) Any material breach of the Funding Agreement by the Recipient, including those set out below, will be an event of default (“Default Event”): 1. the Recipient has amounts owing to the IESO in respect of another funding agreement or other program, contract or arrangement with the IESO that have not been paid after due notice; 2. the IESO notifies the Recipient that it is in default of any existing agreements with the IESO, its predecessor entities, or any of their third party funds managers, including funding agreements; 3. the Recipient fails to complete or submit to the IESO any Activities set out in Schedule C by the applicable Target Completion Date; or 4. the Recipient fails to notify the IESO of any of the events set out in Section 6.1. (b) Should a Default Event occur, the IESO will be entitled to deliver to the Recipient a written notice that the Recipient is in default of the obligations under the Funding Agreement (the “Notice of Default”). The Notice of Default will set out the nature of the Default Event and a reasonable period of time by which the Default Event must be cured.

  • Additional Event of Default The following will constitute an additional Event of Default with respect to Party B: "NOTE ACCELERATION NOTICE. A Note Acceleration Notice is served on Party B in relation to the Relevant Notes."

  • Termination Event If any of the following events (each a "Termination Event") shall occur: (a) default is made by the Administrator in the payment on the due date of any payment due and payable by it under this Agreement and such default continues unremedied for a period of five London Business Days after the Administrator becoming aware of such default; (b) default is made by the Administrator in the performance or observance of any of its other covenants and material obligations under this Agreement or any of the other Transaction Documents, which , the Security Trustee having been informed thereof as specified below in this sub-clause, is materially prejudicial to the interests of the holders of the First Issuer Notes and any New Notes from time to time and such default continues unremedied for a period of twenty (20) days after the Administrator becoming aware of such default, provided however that where the relevant default occurs as a result of a default by any person to whom the Administrator has sub-contracted or delegated part of its obligations hereunder, such default shall not constitute a Termination Event if within such twenty (20) day period the Administrator replaces the relevant sub-contractor or delegate with an entity capable of remedying such default or alternatively indemnifies the Mortgages Trustee and the Beneficiaries against the consequences of such default; (c) the Administrator at any time fails to obtain the necessary license or regulatory approval required by any UK mortgage regulatory regime which would be required in order to enable it to continue administering the Mortgage Loans; or (d) the Administrator becomes subject to an Insolvency Event, then the Mortgages Trustee and/or Funding and the Security Trustee may at once or at any time thereafter while such default continues, by notice in writing to the Administrator, terminate its appointment as Administrator under this Agreement with effect from a date (not earlier than the date of the notice) specified in such notice. Upon termination of the Administrator, the Security Trustee shall use its reasonable endeavours to appoint a substitute Administrator that satisfies the conditions set forth in Clause 19.2(c), (d) and (e), provided that in the event the Security Trustee has not, having used reasonable endeavours, appointed a substitute Administrator, the Security Trustee shall have no liability to any person and, notwithstanding any other provision of the Transaction Documents, shall not itself be required to perform any duties of the Administrator.