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 use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, KDL, at its own expense, shall:
2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or
2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon.
2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Interconnection Trunks, KDL 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 Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. 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.4 On a semi-annual basis, KDL shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that KDL anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between KDL and Verizon. KDL’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 Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced.
2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ 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 ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Verizon and KDL shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as 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
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 Global Connection’s loop distribution elements onto BellSouth's feeder system.
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 Onvoy’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.
Compressed Work Week The Company and Union recognize the concept of the compressed work week. It is further understood that the compressed work week conditions will apply only to those departments that are on the compressed work week.