THE ‘ADD DEFAULT’ BUTTON Sample Clauses

Open Split View

Download

Share

Cite

THE ‘ADD DEFAULT’ BUTTON. This selection adds a wire containing the WirePro default Wire Record values to the harness.

Sample 1

Save

Copy

Related to THE ‘ADD DEFAULT’ BUTTON

• 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”):

• DISTRIBUTION AND DEFAULT SERVICE TERMS AND CONDITIONS Capacity Pipeline Capacity, Underground Storage Withdrawal Capacity, Underground Storage Capacity and Peaking Capacity as defined in these Terms and Conditions. Capacity Allocators The proportion of the Customer’s Total Capacity Quantity that comprises Pipeline Capacity, Underground Storage Withdrawal Capacity and Peaking Capacity. City Gate The interconnection between a Delivering Pipeline and the Company’s distribution facilities. Company Eversource Gas Company of Massachusetts d/b/a Eversource Energy Company Gas Allowance The difference between the sum of all amounts of Gas received into the Company’s distribution system and the sum of all amounts of Gas delivered from the Company’s distribution system as calculated by the Company for the most recent twelve (12) month period ending July 31. Such difference shall include, but not be limited to, Gas consumed by the Company for its own purposes, line losses and Gas vented and lost as a result of an event of Force Majeure, excluding gas otherwise accounted for. Company-Managed Supplies Capacity contracts held and managed by the Company in accordance with governing tariffs, but made available to the Supplier pursuant to Section 13.9 of these Terms and Conditions, including supply-sharing contracts and load- management contracts. Consumption Algorithm A mathematical formula used to estimate a Customer’s daily consumption. Critical Day In accordance with Section 19.0 of these Terms and Conditions, a Day declared at any time by the Company in its reasonable discretion when unusual operating conditions may jeopardize operation of the Company’s distribution system.

• Developer Default Each of the following shall be an Event of Default by Developer:

• Events of Default Defined The following shall each constitute an "Event of Default" hereunder:

• Developer Event of Default Any of the following events shall constitute an event of default by the Developer ("Developer Event of Default") unless such event has occurred as a result of a Force Majeure Event or the Authority Event of Default or any governmental action for reasons other than any breach, default or lapse on the part of the Developer:

• Train Operator Events of Default The following are Train Operator Events of Default:

• EVENT OF DEFAULT/REMEDIES 8.1 Any one or more of the following acts or omissions of the Contractor shall constitute an event of default hereunder (“Event of Default”):

• Customer Default The occurrence at any time of any of the following events shall constitute a “Customer Default”:

• BREACH AND DEFAULT PROVISIONS Xxxxxx is expected to fully and timely comply with all of its CIA obligations.

• Breach and Default 7.6.1 No Breach of this Agreement shall exist where such failure to discharge an obligation (other than the payment of money) is the result of a Force Majeure Event or the result of an act or omission of the other Parties. Upon a Breach, the non-breaching Party shall give written notice of such Breach to the Breaching Party. Except as provided in article 7.6.2, the Breaching Party shall have 60 calendar days from receipt of the Breach notice within which to cure such Breach; provided however, if such Breach is not capable of cure within 60 calendar days, the Breaching Party shall commence such cure within 20 calendar days after notice and continuously and diligently complete such cure within six months from receipt of the Breach notice; and, if cured within such time, the Breach specified in such notice shall cease to exist.