Remote Terminal Unit (RTU) Sample Clauses

Remote Terminal Unit (RTU). Prior to the Initial Synchronization Date of the Generating Facility, a remote terminal unit, or equivalent data collection and transfer equipment acceptable to both Parties, shall be installed by Interconnection Customer, or by Transmission Owner at Interconnection Customer’s expense, to gather accumulated and instantaneous data to be telemetered to the location(s) designated by Transmission Owner and Transmission Provider 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 Transmission Owner and Transmission Provider. Instantaneous bi- directional analog real power and reactive power flow information must be telemetered directly to the location(s) specified by Transmission Provider and Transmission Owner.
AutoNDA by SimpleDocs
Remote Terminal Unit (RTU). Prior to the Initial Synchronization Date of the Generating Facility, a remote terminal unit, or equivalent data collection and transfer equipment acceptable to both Parties, shall be installed by Interconnection Customer, or by Transmission Owner at Interconnection Customer’s expense, to gather accumulated and instantaneous data to be telemetered to the location(s) designated by Transmission Owner and Transmission Provider 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 Transmission Owner and Transmission Provider. Instantaneous bi-directional analog real power and reactive power flow information must be telemetered directly to the location(s) specified by Transmission Provider and Transmission Owner. Each Party will promptly advise the other Parties if it detects or otherwise learns of any metering, telemetry or communications equipment errors or malfunctions that require the attention and/or correction. The Party owning such equipment shall correct such error or malfunction as soon as reasonably feasible.
Remote Terminal Unit (RTU). Prior to the Initial Synchronization Date of the Generating Facility, a remote terminal unit, or equivalent data collection and transfer equipment acceptable to both Parties, shall be installed by Interconnection Customer, or 1. The communication protocol for the data circuit(s) shall be specified by Transmission Owner and Transmission Provider. Instantaneous bi- directional analog real power and reactive power flow information must be telemetered directly to the location(s) specified by Transmission Provider and Transmission Owner. Each Party will promptly advise the other Parties if it detects or otherwise learns of any metering, telemetry or communications equipment errors or malfunctions that require the attention and/or correction. The Party owning such equipment shall correct such error or malfunction as soon as reasonably feasible.
Remote Terminal Unit (RTU). Database
Remote Terminal Unit (RTU). The RTU is a small vulnerable part, making it a potentially easy prey to attackers. Therefore, to reduce its attack surface, the device should be hardened (4.1.8) and segregated as much from the other systems as possible (4.1.1). Segregation is also one way to protect data flow confidentiality; alternatively, the data may be encrypted (4.1.12.2). Also, to avoid spoofing, the connected device shout authenticate itself (4.1.12.4). Table 25 gives a structured overview of the requirements for the RTU. Communications Segregation* 4.1.1 Device Hardening 4.1.8 Communications Encryption* 4.1.12.2 Device Authentication 4.1.12.4
Remote Terminal Unit (RTU). Prior to the Initial Synchronization Date of the Generating Facility, a remote terminal unit, or equivalent data collection and transfer equipment acceptable to both Parties, shall be installed by Interconnection Customer, or by Transmission Owner at Interconnection Customer’s expense, to gather accumulated and instantaneous data to be telemetered to the location(s) designated by Transmission Owner and Transmission Provider 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 Transmission Owner and Transmission Provider. Instantaneous

Related to Remote Terminal Unit (RTU)

  • 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.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PCS, PCS shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs. 2.4.2 Prior to ordering any Two-Way Interconnection Trunks from Verizon, PCS shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, PCS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that PCS anticipates Verizon will need to provide during the ensuing two (2) year period to carry traffic from PCS to Verizon and from Verizon to PCS. PCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Unbundled Sub-Loop Feeder 2.8.4.1 Unbundled Sub-Loop Feeder (USLF) provides connectivity between BellSouth's central office and cross-box (or other access point) that serves an end user location. 2.8.4.2 USLF utilized for voice traffic can be configured as 2-wire voice (USLF-2W/V) or 4-wire voice (USLF-4W/V). 2.8.4.3 USLF utilized for digital traffic can be configured as 2-wire ISDN (USLF-2W/I); 2-wire Copper (USLF-2W/C); 4-wire Copper (USLF-4W/C); 4-wire DS0 level loop (USLF-4W/D0); or 4-wire DS1 and ISDN (USLF-4W/DI). 2.8.4.4 USLF will provide access to both the equipment and the features in the BellSouth central office and BellSouth cross box necessary to provide a 2W or 4W communications pathway from the BellSouth central office to the BellSouth cross- box. This element will allow for the connection of Lightyear’s loop distribution elements onto BellSouth's feeder system.

  • Master Feeder Structure If permitted by the 1940 Act, the Board of Trustees, by vote of a majority of the Trustees, and without a Shareholder vote, may cause the Trust or any one or more Series to convert to a master feeder structure (a structure in which a feeder fund invests all of its assets in a master fund, rather than making investments in securities directly) and thereby cause existing Series of the Trust to either become feeders in a master fund, or to become master funds in which other funds are feeders.

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

  • Shared Transport The Shared Transport Network Element (“Shared Transport”) provides the collective interoffice transmission facilities shared by various Carriers (including Qwest) between end-office switches and between end-office switches and local tandem switches within the Local Calling Area. Shared Transport uses the existing routing tables resident in Qwest switches to carry the End User Customer’s originating and terminating local/extended area service interoffice Local traffic on the Qwest interoffice message trunk network. CLEC traffic will be carried on the same transmission facilities between end- office switches, between end-office switches and tandem switches and between tandem switches on the same network facilities that Qwest uses for its own traffic. Shared Transport does not include use of tandem switches or transport between tandem switches and end-office switches for Local Calls that originate from end users served by non- Qwest Telecommunications Carriers (“Carrier(s)”) which terminate to QLSP End Users.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Xxxxx’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • 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.

  • Television Equipment Recycling Program If this Contract is for the purchase or lease of covered television equipment, then Contractor certifies that it is compliance with Subchapter Z, Chapter 361 of the Texas Health and Safety Code related to the Television Equipment Recycling Program.

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