Dispatching Dispatch Events Sample Clauses

Dispatching Dispatch Events. Once a Dispatch Event has been scheduled by PNM the Software will execute that Dispatch Event by dispatching control commands via the RF network to the DCUs connected to the Participating Facility’s A/C unit. Once the Software issues the Dispatch Event all Participating Facilities will be controlled within 10 minutes. The Status field shows the current status of each scheduled event, which can be any of the following: Inactive No schedule submitted Pending Schedule was submitted, but load control has not begun Executing The system is under load control as specified in the schedule Done The system finished executing the load control schedule Restoring After executing the schedule, the system is updating the database Error There was error in processing this schedule
View SourceView Similar (3)
Dispatching Dispatch Events. Once a Dispatch Event has been scheduled by NPC the Software shall execute the Dispatch Event by dispatching control commands via the RF network to *** Portions of this agreement marked by *** have been omitted pursuant to a request for confidential treatment. Omitted material for which confidential treatment has been requested has been filed separately with the Securities and Exchange Commission. ***
View Source

Related to Dispatching Dispatch Events

  • Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include: (a) accident, death or severe injury to any person; (b) damaged or dislodged fixed equipment; (c) flooding of Project Highway; and (d) any other unusual occurrence.

  • Transmission Delivery Service Implications Under ER Interconnection Service, Interconnection Customer will be eligible to inject power from the Generating Facility into and deliver power across the Transmission System on an “as available” basis up to the amount of MW identified in the applicable stability and steady state studies to the extent the upgrades initially required to qualify for ER Interconnection Service have been constructed. After that date FERC makes effective MISO’s Energy Market Tariff filed in Docket No. ER04-691-000, Interconnection Customer may place a bid to sell into the market up to the maximum identified Generating Facility output, subject to any conditions specified in the Interconnection Service approval, and the Generating Facility will be dispatched to the extent the Interconnection Customer’s bid clears. In all other instances, no transmission or other delivery service from the Generating Facility is assured, but Interconnection Customer may obtain Point-To-Point Transmission Service, Network Integration Transmission Service or be used for secondary network transmission service, pursuant to the Tariff, up to the maximum output identified in the stability and steady state studies. In those instances, in order for Interconnection Customer to obtain the right to deliver or inject energy beyond the Point of Interconnection or to improve its ability to do so, transmission delivery service must be obtained pursuant to the provisions of the Tariff. The Interconnection Customer’s ability to inject its Generating Facility output beyond the Point of Interconnection, therefore, will depend on the existing capacity of the Transmission or Distribution System as applicable, at such time as a Transmission Service request is made that would accommodate such delivery. The provision of Firm Point-To-Point Transmission Service or Network Integration Transmission Service may require the construction of additional Network or Distribution Upgrades.

  • Reporting of Reportable Events If ▇▇▇▇▇ determines (after a reasonable opportunity to conduct an appropriate review or investigation of the allegations) through any means that there is a Reportable Event, ▇▇▇▇▇ shall notify OIG, in writing, within 30 days after making the determination that the Reportable Event exists.

  • Determination of Responsiveness 28.1 The Procuring Entity's determination of a Tender's responsiveness is to be based on the contents of the Tender itself, as defined in ITT28.2.

  • Reporting of Non-Force Majeure Events Each Party (the “Notifying Party”) shall notify the other Parties when the Notifying Party becomes aware of its inability to comply with the provisions of this Agreement for a reason other than a Force Majeure event. The Parties agree to cooperate with each other and provide necessary information regarding such inability to comply, including the date, duration, reason for the inability to comply, and corrective actions taken or planned to be taken with respect to such inability to comply. Notwithstanding the foregoing, notification, cooperation or information provided under this Article shall not entitle the Party receiving such notification to allege a cause for anticipatory breach of this Agreement.