Triggers Sample Clauses

Triggers. The Company shall dissolve at any time after February 10, 2003, if at such time the aggregate Liquidation Preference is at least $7.5 million (excluding the Liquidation Preference on any PIK Preferred Stock distributed as a dividend) and holders of at least a majority of PIK Preferred Stock then outstanding vote to dissolve the Company and provide notice of such vote to the Board of Directors; provided, however, that in the event that such a vote and resulting dissolution of the Company would result in an event of default or an incipient default under any then existing indebtedness of the Company or any Subsidiary with an outstanding balance of $10 million or more, then such majority vote shall not cause the dissolution of the Company, but rather shall constitute notice by the holders of the PIK Preferred Stock to the Board of Directors that such holders desire that the Board of Directors promptly arrange the sale of the Company (including its Subsidiaries) or a sale of all or substantially all of its assets.
Triggers. For all incremental Minimum Purchase transfers pursuant to this Agreement mutually approved by East Palo Alto and Mountain View (initial or exceed the corresponding Temporary Minimum set forth in Article B, Section 2, of this Agreement for three (3) consecutive fiscal years, one (1) increment of twenty-five East Palo Alto.
Triggers. Upon and at any time following the occurrence of any of the following events (each, a "Trigger"), the Put Rights and the Call Rights shall be exercisable:
Triggers. Any obligation of Micron to pay Intermolecular a [***]Fee identified in a Project SOW shall be conditioned upon Intermolecular's satisfaction of certain technical criteria for Deliverables (the “Trigger(s)”) set forth in such Project SOW. A Project SOW for Category B2 or Category C may include multiple Triggers, consisting of several distinct criteria capable of independent satisfaction, such that Intermolecular's satisfaction of each individual Trigger shall give rise to an obligation for Micron to pay a corresponding portion of the overall [***]Fee (calculated by dividing the Success Fee by the number of Triggers, or as otherwise set forth in a Project SOW), subject to satisfaction of the related Production Threshold and provided that the total number of Triggers for any Project SOW shall not exceed four (4). As an example, for illustrative purposes only, a hypothetical Project SOW for Category B2 may have a [***]Fee of [***] per year, [***] for five (5) years, and may be determined to have three (3) Triggers. In this example, assuming that Intermolecular satisfies a first Trigger and related Production Threshold initially and satisfies a second Trigger and related Production Threshold one year later, but never satisfies the third Trigger, then Micron would [***] of [***] per year, payable for five (5) years, upon satisfaction of the first Trigger and related Production Threshold, and one year later Micron would [***] a second, separate [***] of [***] per year, [***] for five (5) years, upon satisfaction of the second Trigger and related Production Threshold, but the full [***] would not be payable by Micron because Intermolecular failed to satisfy the third Trigger and related Production Threshold.
Triggers. The drought triggers are presented in the below table. They have been defined based on: - Groundwater level: characteristics of the abstraction system (pump level and well depth) - Reservoir level: operational philosophy and water retention capacity - Customer demand: peak demand and maximum Deployable Output (DO) Table 1 – Drought triggers Level Trigger Level 1 - Normal Groundwater level above 90m AOD* Reservoir level reaching low threshold Customer demand < 8.4 ML/d Level 2 - Developing Drought Groundwater level above 90m and below 75m AOD* Reservoir level dropping below the low threshold over less than a week Customer demand at 8.4 ML/d Level 3 - Drought Groundwater level below 75m AOD* Reservoir level dropping below the low threshold over less than 36 hours Customer demand at 8.4 ML/d Level 4 - Severe Drought Groundwater level below 30m AOD* Reservoir level dropping below the low threshold over less than 24 hours Customer demand at 8.4 ML/d *AOD: Above Ordnance Datum (with datum as mean sea level) Note: These triggers may be subject to changes following the modelling work being undertaken to validate the drought vulnerability assessment of VWPL’s supply.
Triggers. A Minority Investor may exercise its Put Right (i) during the 10-day period commencing on each anniversary of the Effective Date by delivering written notice to Holdco 1 during such period of such Minority Investor's exercise of such right under this Section 10.1(b)(i), provided that no Minority Investor shall be entitled to exercise its Put Right under this clause (i) if (x) prior to October 1, 2005, the effect of the transaction is to cause a "change in ownership" of Huntsman Group under Section 382 of the Code and at such time Huntsman Group has any tax attributes that would be limited under Section 382 or 383 of the Code or (y) a Qualifying IPO shall have been consummated at any time prior to the exercise of such Put Right, or (ii) in connection with a Huntsman Liquidity Transaction, as provided below. Holdco 1 hereby agrees to provide each Minority Investor with reasonable notice of any potential Huntsman Liquidity Transaction at least 20 days prior to consummation thereof. Each Minority Investor may exercise its Put Right with respect to a Huntsman Liquidity Transaction by providing Holdco 1 with written notice thereof within 10 days after such Minority Investor has received notice of a potential Huntsman Liquidity Transaction from Holdco 1.
Triggers. 4.1 Short Term and / or Repeated Absence
Triggers. A trigger is a self-contained routine associated with a table or view that automat- ically performs an action when a row in the table or view is inserted, updated, or deleted. Triggers can provide: • Automatic enforcement of data restrictions to ensure that users enter only valid values into columns. • Reduced application maintenance, because changes to a trigger are auto- matically reflected in all applications that use the associated table with- out the need to recompile and relink them. • Automatic logging of changes to tables. An application can keep a run- ning log of changes with a trigger that fires whenever a table is modified. • Event alerters in triggers can automatically notify applications of changes to the database. When a trigger is invoked, it has immediate access to data being stored, modi- fied, or erased. The trigger may also access data in other tables. Using the avail- able data, you can design the trigger to: • Abort an operation, possibly with an error message. • Set values in the accessed record. • Insert, update, or delete rows in other tables. • Signal that an event has occurred using an event alerter.
Triggers. The Parties accept the following "triggers" for a change in adders from those set forth in Sections 2(e) and 2(f) above (it being understood that megawatt-hours of consumption of all customers being served by RESs affiliated with ComEd shall be excluded from the calculations below which are relevant to the "triggers"). The calculations relevant to the triggers referred to below will be released by ComEd as soon as practical after the first business day of January in 2004, 2005, and 2006, but not later that February 1. In addition, ComEd will submit to the ICC Staff for verification the methodology used to determine each of the 2002 Base Consumption and 2003, 2004, and 2005 Annual Consumption figures.
Triggers. The issue resolution process may be initiated by any Signatory Agency for the following reasons: there is a disagreement on the interpretation of this agreement; a Resource Agency gives a response of non-concurrence to a request for concurrence; or any other dispute in the process that cannot be resolved by a consensus of agency representatives.