STML South Block System Sample Clauses

The STML South Block System clause defines the operational framework and responsibilities related to the use or management of the South Block System within the STML context. Typically, this clause outlines which party is responsible for maintaining, operating, or accessing the South Block System, and may specify technical standards, access rights, or maintenance obligations. For example, it might detail how the system is to be used for data transmission or infrastructure sharing. The core function of this clause is to ensure clear allocation of duties and rights regarding the South Block System, thereby preventing disputes and ensuring smooth operation.
STML South Block System. The Parties recognize that it will be necessary for STML to construct, own, maintain and operate a gathering system to move production from the South Block from STML operated ▇▇▇▇▇ to the facilities contemplated by the Tenaska Agreement. Assuming the existence of this STML operated or controlled gathering system, STML agrees that EnCana shall have the right, but not the obligation, to transport gas on this gathering system from ▇▇▇▇▇ in the South Block in which EnCana owns an interest within the Assigned Interval. If EnCana moves gas on the STML gathering system in accordance with this paragraph, STML shall charge EnCana a reasonable market-based fee to which the Parties mutually agree acting in a commercially reasonable manner.

Related to STML South Block System

  • PFPC System PFPC shall retain title to and ownership of any and all data bases, computer programs, screen formats, report formats, interactive design techniques, derivative works, inventions, discoveries, patentable or copyrightable matters, concepts, expertise, patents, copyrights, trade secrets, and other related legal rights utilized by PFPC in connection with the services provided by PFPC to the Fund.

  • Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters). The UCL-D will be offered in two versions - Short and Long. 2.4.2.2 A short UCL-D (18,000 feet or less) is provisioned according to Resistance Design parameters, may have up to 6,000 feet of bridged tap and will have up to 1300 ohms of resistance. 2.4.2.3 The long UCL-D (beyond 18,000 feet) is provisioned as a dry copper twisted pair longer than 18,000 feet and may have up to 12,000 feet of bridged tap and up to 2800 ohms of resistance. 2.4.2.4 The UCL-D is a designed circuit, is provisioned with a test point, and comes standard with a DLR. OC is a chargeable option for a UCL-D; however, OC is always required on UCLs where a reuse of existing facilities has been requested by Granite. 2.4.2.5 These loops are not intended to support any particular services and may be utilized by Granite to provide a wide-range of telecommunications services so long as those services do not adversely affect BellSouth’s network. This facility will include a Network Interface Device (NID) at the customer’s location for the purpose of connecting the loop to the customer’s inside wire. 2.4.2.6 BellSouth will make available the following UCL-Ds:

  • Signaling Link Transport 9.2.1 Signaling Link Transport is a set of two or four dedicated 56 kbps transmission paths between Global Connection-designated Signaling Points of Interconnection that provide appropriate physical diversity.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS 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 WCS 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 WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS 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 WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

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