SINGLE EVENT Sample Clauses

SINGLE EVENT. (precisely state all dates and times of the event;
AutoNDA by SimpleDocs
SINGLE EVENT. (Date and start/end times of the event)
SINGLE EVENT. Monthly registration/application must be completed each month and received by the 15th of the month.
SINGLE EVENT. In the event a single * triggers more than one milestone payment under Sections 4.2, 4.3 and 4.4 the Parties agree that only the milestone payments for the highest Region shall actually be due within thirty (30) days and the milestone payments for the other Regions that are triggered by such event shall be deferred until twelve (12) months after the date of the triggering event. For example, in the event a * shall be due (if not already paid) within thirty (30) days, and the * shall be paid in full (if not already paid) within thirty (30) days after twelve (12) months from the *.
SINGLE EVENT. UPSETS (SEU) The design of the satellite shall be such that the effects of single event upsets are minimized. Design techniques such as 2-out-of-3 voting shall be used to make the system SEU immune. System recovery mechanisms such as data refresh and command retries will be used. No SEU shall cause the spacecraft to be in a non-restorable (latch-up) state. Single event upsets capable of causing service interruption shall be limited to the following three conditions only:

Related to SINGLE EVENT

  • Reportable Events No such Employee Benefit Plan which is an Employee Pension Benefit Plan has been completely or partially terminated or been the subject of a Reportable Event as to which notices would be required to be filed with the PBGC. No proceeding by the PBGC to terminate any such Employee Pension Benefit Plan has been instituted or threatened; and

  • Reportable Event Reportable Event" means a "reportable event" as defined in Section 4043(b) of ERISA.

  • ERISA Reportable Event A reportable event with respect to a Guaranteed Pension Plan within the meaning of §4043 of ERISA and the regulations promulgated thereunder as to which the requirement of notice has not been waived.

  • Definition of Reportable Event For purposes of this CIA, a “Reportable Event” means anything that involves:

  • Sale Event During the Term, if within twelve (12) months after a Sale Event, the Executive’s employment is terminated by the Company without Cause as provided in Section 3(d) or the Executive terminates employment for Good Reason as provided in Section 3(e), then, subject to the signing of the Separation Agreement and Release by the Executive and the Separation Agreement and Release becoming irrevocable, all within 60 days after the Date of Termination,

  • Reportable Events Involving the Xxxxx Law Notwithstanding the reporting requirements outlined above, any Reportable Event that involves solely a probable violation of section 1877 of the Social Security Act, 42 U.S.C. §1395nn (the Xxxxx Law) should be submitted by Practitioner to CMS through the self-referral disclosure protocol (SRDP), with a copy to the OIG. If Practitioner identifies a probable violation of the Xxxxx Law and repays the applicable Overpayment directly to the CMS contractor, then Practitioner is not required by this Section III.G to submit the Reportable Event to CMS through the SRDP.

  • Termination Due To Lack Of Funding Appropriation If, in the judgment of the Director of Accounts and Reports, Department of Administration, sufficient funds are not appropriated to continue the function performed in this agreement and for the payment of the charges hereunder, State may terminate this agreement at the end of its current fiscal year. State agrees to give written notice of termination to contractor at least 30 days prior to the end of its current fiscal year, and shall give such notice for a greater period prior to the end of such fiscal year as may be provided in this contract, except that such notice shall not be required prior to 90 days before the end of such fiscal year. Contractor shall have the right, at the end of such fiscal year, to take possession of any equipment provided State under the contract. State will pay to the contractor all regular contractual payments incurred through the end of such fiscal year, plus contractual charges incidental to the return of any such equipment. Upon termination of the agreement by State, title to any such equipment shall revert to contractor at the end of the State's current fiscal year. The termination of the contract pursuant to this paragraph shall not cause any penalty to be charged to the agency or the contractor.

  • Reportable Events under Section III J.1.c. For Reportable Events under Section III.J.1.c, the report to OIG shall include:

  • Subsequent Taxable Events If, within 10 years from the date on which the relevant Participating TO's Interconnection Facilities are placed in service, (i) the Interconnection Customer Breaches the covenants contained in Article 5.17.2, (ii) a "disqualification event" occurs within the meaning of IRS Notice 88-129, or (iii) this LGIA terminates and the Participating TO retains ownership of the Interconnection Facilities and Network Upgrades, the Interconnection Customer shall pay a tax gross-up for the cost consequences of any current tax liability imposed on the Participating TO, calculated using the methodology described in Article 5.17.4 and in accordance with IRS Notice 90-60.

  • Uncontrollable Events BISYS assumes no responsibility hereunder, and shall not be liable for any damage, loss of data, delay or any other loss whatsoever caused by events beyond its reasonable control.

Time is Money Join Law Insider Premium to draft better contracts faster.