Common use of Abnormal Operating Conditions Clause in Contracts

Abnormal Operating Conditions. A Party that is experiencing system conditions that require the system operators’ immediate attention may temporarily delay implementation of the M2M redispatch process or cease an active M2M redispatch event until a reasonable time after the system condition that required the system operators’ immediate attention is resolved. Either Party may temporarily suspend an active M2M coordination process or delay implementation of the M2M coordination process if a Party is experiencing, or acting in good faith suspects it may be experiencing, (1) a failure or outage of the data link between the Parties prevents the exchange of accurate or timely real-time data necessary to implement the M2M coordination process; or (2) a failure or outage of any computational or data systems preventing the actual or accurate calculation of data necessary to implement the M2M coordination process. The Parties shall resolve the issue causing the failure or outage of the data link, computational systems, or data systems as soon as possible in accordance with Good Utility Practice. The Parties shall resume implementation of the M2M coordination process following the successful testing of the data link or relevant system(s) after the failure or outage condition is resolved.

Appears in 28 contracts

Samples: Joint Operating Agreement, Joint Operating Agreement, Joint Operating Agreement

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