MLP GP and SE Transmission Sample Clauses

MLP GP and SE Transmission. On the First Closing: (1) If the Target Third Party Indebtedness Balance in respect of, in the aggregate, SE Transmission II and the Companies held directly or indirectly by SE Transmission II (to the extent an interest therein is being contributed on the First Closing) minus the aggregate Third Party Indebtedness Balance of SE Transmission II and such Companies as of the First Closing Date is a positive number: SEP shall pay in cash to MLP GP an amount equal to X% of such positive number, and SEP shall pay in cash to SE Transmission an amount equal to Y% of such positive number.
Sample 1
AutoNDA by SimpleDocs
MLP GP and SE Transmission. On the First Closing: (1) If the Target Third Party Indebtedness Balance in respect of, in the aggregate, SE Transmission II and the Companies held directly or indirectly by SE Transmission II (to the extent an interest therein is being contributed on the First Closing) minus the aggregate Third Party Indebtedness Balance of SE Transmission II and such Companies as of the First Closing Date is a positive number: SEP shall pay in cash to MLP GP an amount equal to X% of such positive number, and SEP shall pay in cash to SE Transmission an amount equal to Y% of such positive number. (2) If the Target Third Party Indebtedness Balance in respect of, in the aggregate, SE Transmission II and the Companies held directly or indirectly by SE Transmission II (to the extent an interest therein is contributed on the First Closing) minus the aggregate Third Party Indebtedness Balance of such Companies as of the First Closing Date is a negative number: the Base Cash Consideration otherwise payable to MLP GP shall be decreased by an amount equal to X% of the aggregate Third Party Indebtedness Balance of such Companies as of the First Closing Date minus the aggregate Target Third Party Indebtedness Balance in respect of such Companies, and the SE Transmission (SE Transmission II) Unit Consideration shall be decreased by a number of Common Units equal to (x) Y% of such number divided by (y) the Base Unit Price (such number of Common Units rounded upward, if such calculation does not result in a whole number of Common Units).
Sample 1

Related to MLP GP and SE Transmission

  • NYISO and Connecting Transmission Owner Obligations Connecting Transmission Owner and NYISO shall cause the New York State Transmission System and the Connecting Transmission Owner’s Attachment Facilities to be operated, maintained and controlled in a safe and reliable manner in accordance with this Agreement and the NYISO Tariffs. Connecting Transmission Owner and NYISO may provide operating instructions to Developer consistent with this Agreement, NYISO procedures and Connecting Transmission Owner’s operating protocols and procedures as they may change from time to time. Connecting Transmission Owner and NYISO will consider changes to their respective operating protocols and procedures proposed by Developer.

  • Information Transmission The Provider, on behalf of itself and its respective Subsidiaries, shall use commercially reasonable efforts to provide or make available, or cause to be provided or made available, to the Recipient, in accordance with Section 6.1 of the Separation and Distribution Agreement, any Information received or computed by the Provider for the benefit of the Recipient concerning the relevant Service during the Service Period; provided, however, that, except as otherwise agreed to in writing by the Parties (a) the Provider shall not have any obligation to provide, or cause to be provided, Information in any non-standard format, (b) the Provider and its Subsidiaries shall be reimbursed for their reasonable costs in accordance with Section 6.3 of the Separation and Distribution Agreement for creating, gathering, copying, transporting and otherwise providing such Information, and (c) the Provider shall use commercially reasonable efforts to maintain any such Information in accordance with Section 6.4 of the Separation and Distribution Agreement.

  • Connecting Transmission Owner Obligations Connecting Transmission Owner shall maintain its transmission facilities and Attachment Facilities in a safe and reliable manner and in accordance with this Agreement.

  • Connecting Transmission Owner’s Attachment Facilities Connecting Transmission Owner shall design, procure, construct, install, own and/or control the Connecting Transmission Owner’s Attachment Facilities described in Appendix A hereto, at the sole expense of the Developer.

  • Transmission encryption All data transmissions of County PHI or PI outside the secure internal network must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as AES. Encryption can be end to end at the network level, or the data files containing PHI can be encrypted. This requirement pertains to any type of PHI or PI in motion such as website access, file transfer, and E-Mail.

  • Data Transmission The procedures for transmitting load obligation data to PJM for DS Supplier’s DS Load shall be as set forth by PJM.

  • Interconnection Agreement Seller shall comply with the terms and conditions of the Interconnection Agreement.

  • Interconnection 2.1 This section applies to linking with suppliers providing public telecommunications transport networks or services in order to allow the users of one supplier to communicate with users of another supplier and to access services provided by another supplier, where specific commitments are undertaken.

  • 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

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

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