Remote Trip Sample Clauses

Remote Trip. (A) A Remote Trip is a manual trip signal issued by the APS Control Center to trip the generation off line and isolate it from the APS Distribution System. This signal will normally be communicated via fiber optic cable originating at the APS substation or by a radio frequency via an antenna. It will generally trip the generator breaker(s) via a Customer installed breaker control circuit. (B) A GF with an aggregate generator nominal nameplate rating less than 1 MW will not typically require remote trip capability specified. However, depending upon the GF’s impact on the APS System, APS may require remote trip and remote monitoring capability. (C) The Remote Trip function will be accomplished via a Remote Terminal Unit (RTU) provided by APS at Customer’s expense and the cabinet and connections will be installed by Customer at Customer’s Facility. (D) For a GF comprising static inverters located on a non-Dedicated Utility Feeder, should APS need to switch the section of the normal feeder on which the GF is located to another feeder for line/breaker maintenance, feeder sectionalizing/switching, and/or load transfer operations, APS reserves the right, without liability, to remotely trip the GF off- line for the duration of any such operation.
Sample 1
AutoNDA by SimpleDocs

Related to Remote Trip

  • Remote Work Buyer agrees that Honeywell may provide some or all of the Services remotely using an internet connection and may install additional software and related communication and/or diagnostic devices on Buyer's applicable systems (the “Systems”) to enable such connection and/or remote work. Xxxxx agrees to fully cooperate with Honeywell’s installation and commissioning of such software and devices on the Systems. To the extent required by Honeywell, Buyer will enable and consents to internet connectivity between its applicable Systems and Honeywell’s applicable computer server(s)/system(s) and/or the Honeywell cloud platform(s) throughout the term of this Agreement.

  • Remote Access Access to and use of the Data over the State Governmental Network (SGN) or Secure Access Washington (SAW) will be controlled by DSHS staff who will issue authentication credentials (e.g. a Unique User ID and Hardened Password) to Authorized Users on Contractor’s staff. Contractor will notify DSHS staff immediately whenever an Authorized User in possession of such credentials is terminated or otherwise leaves the employ of the Contractor, and whenever an Authorized User’s duties change such that the Authorized User no longer requires access to perform work for this Contract.

  • Remote Terminal Unit Prior to the Initial Synchronization Date of the Large Generating Facility, a Remote Terminal Unit, or equivalent data collection and transfer equipment acceptable to the Parties, shall be installed by Developer, or by Connecting Transmission Owner at Developer’s expense, to gather accumulated and instantaneous data to be telemetered to the location(s) designated by Connecting Transmission Owner and NYISO through use of a dedicated point-to-point data circuit(s) as indicated in Article 8. 1. The communication protocol for the data circuit(s) shall be specified by Connecting Transmission Owner and NYISO. Instantaneous bi-directional analog real power and reactive power flow information must be telemetered directly to the location(s) specified by Connecting Transmission Owner and NYISO. Each Party will promptly advise the appropriate other Party if it detects or otherwise learns of any metering, telemetry or communications equipment errors or malfunctions that require the attention and/or correction by that other Party. The Party owning such equipment shall correct such error or malfunction as soon as reasonably feasible.

  • Help Desk A help desk for Product support issues (the “Help Desk”) will be available to Customer. Unless specified in an Order, Customer should contact 000.000.0000 to receive a telephone number for the applicable supporting Solutions & Support Center. Customer will appoint one Product administrator and one backup administrator to serve as the primary point of contact regarding maintenance services.

  • Outages 9.7.1.1 Outage Authority and Coordination. Interconnection Customer and Transmission Owner may each in accordance with Good Utility Practice in coordination with the other Party and Transmission Provider remove from service any of its respective Interconnection Facilities, System Protection Facilities, Network Upgrades, System Protection Facilities or Distribution Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency Condition, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to notify one another and schedule such removal on a date and time mutually acceptable to the Parties. In all circumstances, any Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Parties of such removal.

  • Tandem Transit Traffic ‌ 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Onvoy's network, and is transported through Frontier’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Frontier, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Frontier. Subtending End Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). For the avoidance of any doubt, under no circumstances shall Frontier be required to transit traffic through a Frontier Tandem to a Central Office that the LERG does not identify as subtending that particular Frontier Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic. 12.2 Tandem Transit Traffic Service provides Onvoy with the transport of Tandem Transit Traffic as provided below. 12.3 Tandem Transit Traffic may be routed over the Interconnection Trunks described in Sections 2 through 6 of this Attachment. Onvoy shall deliver each Tandem Transit Traffic call to Frontier’s Tandem with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions. 12.4 Onvoy may use Tandem Transit Traffic Service only for traffic that originates on Onvoy’s network and only to send traffic to an Other Carrier with whom Onvoy has a reciprocal traffic exchange arrangement (either via written agreement or mutual tariffs) that provides for the Other Carrier, to terminate or complete traffic originated by Onvoy and to bill Onvoy, and not to bill Frontier, for such traffic. Onvoy agrees not to use Frontier’s Tandem Transit Traffic Service to send traffic to an Other Carrier with whom Onvoy does not have such a reciprocal traffic exchange arrangement or to send traffic that does not originate on Onvoy’s network. 12.5 Onvoy shall pay Frontier for Tandem Transit Traffic Service at the rates specified in the Pricing Attachment. Frontier will not be liable for compensation to any Other Carrier for any traffic that is transported through Frontier’s Tandem and Frontier reserves the right to assess to Onvoy any additional charges or costs any Other Carrier imposes or levies on Frontier for the delivery or termination of such traffic, including any Switched Exchange Access Service charges. If Frontier is billed by any Other Carrier for any traffic originated by Onvoy, Frontier may provide notice to Onvoy of such billing. Upon receipt of such notice, Onvoy shall immediately stop using Frontier’s Tandem Transit Traffic Service to send any traffic to such Other Carrier until it has provided to Frontier certification that the Other Carrier has removed such billed charges from its bill to Frontier and that the Other Carrier will not bill Frontier for any traffic originated by Onvoy. Such certification must be signed by an authorized officer or agent of the Other Carrier and must be in a form acceptable to Frontier. 12.6 If Onvoy uses Tandem Transit Traffic Service for traffic volumes that exceed the Centum Call Seconds (Hundred Call Seconds) busy hour equivalent of 200,000 combined minutes of use per month (a DS1 equivalent) to the subtending End Office of a particular Other Carrier for any month (the “Threshold Level”). Onvoy shall use good faith efforts to establish direct interconnection with such Other Carrier and reduce such traffic volumes below the Threshold Level. If Frontier believes that Xxxxx has not exercised good faith efforts promptly to obtain such direct interconnection, either Party may use the Dispute Resolution processes of this Agreement. 12.7 If Onvoy fails to comply with Section 12 of this Attachment, such failure shall be a material breach of a material provision of this Agreement and Frontier may exercise any and all remedies under this Agreement and Applicable Law for such breach. 12.8 If or when a third party carrier plans to subtend an Onvoy switch, then Onvoy shall provide written notice to Frontier at least ninety (90) days before such subtending service arrangement becomes effective so that Frontier may negotiate and establish direct interconnection with such third party carrier. Upon written request from Frontier, Onvoy shall offer to Frontier a service arrangement equivalent to or the same as Tandem Transit Traffic Service provided by Frontier to Onvoy as defined in this Section such that Frontier may terminate calls to a Central Office or its equivalent of a CLEC, ILEC other than Frontier, CMRS carrier, or other LEC, that subtends an Onvoy Central Office or its equivalent (“Reciprocal Tandem Transit Service”). Onvoy shall offer such Reciprocal Transit Service arrangements under terms and conditions of an amendment to this Agreement or a separate agreement no less favorable than those provided in this Section. 12.9 Neither Party shall take any actions to prevent the other Party from entering into a direct and reciprocal traffic exchange arrangement with any carrier to which it originates, or from which it terminates, traffic.

  • ATTENDANCE AT MANDATORY MEETINGS/SCHOOL EVENTS Where an employee is required through clear direction by the board to attend work outside of regular working hours, the provisions of the local collective agreement regarding hours of work and compensation, including any relevant overtime/lieu time provisions, shall apply. Required attendance outside of regular working hours may include, but is not limited to school staff meetings, parent/teacher interviews, curriculum nights, Individual Education Plan and Identification Placement Review Committee meetings, and consultations with board professional staff.

  • Unbundled Network Element Combinations 5.1. Unbundled Network Element Combinations shall include: 1) Enhanced Extended Links (EELs); 2) UNE Loops/Special Access Combinations; 3) Loop/Port Combinations; and 4)

  • Conference Attendance The Federation will be entitled to five (5) person days per year release time for designated Federation representatives to attend conferences. All conference expenses will be the responsibility of the Federation, unless funding is requested and approved through regular District processes for conference attendance.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!