EnCana System Sample Clauses

EnCana System. The Parties recognize that it will be necessary for EnCana to construct, own, maintain and operate a gathering system to move production from the North Block from EnCana operated xxxxx to the facilities contemplated by the Tenaska Agreement. Assuming the existence of this EnCana operated or controlled gathering system, EnCana agrees that STML shall have the right, but not the obligation, to transport gas on this gathering system from xxxxx in which STML owns an interest and that produce from an interval outside of the Assigned Interval. This right by STML shall be on a space available basis with no obligation on the part of EnCana to provide space on the gathering system, unless such space is readily available. EnCana will also allow STML the right to use its rights-of-way related to the gathering system provided such use is not prohibited by the terms of the particular right-of-way grant. If STML moves gas on the EnCana gathering system in accordance with this paragraph, EnCana shall charge STML a reasonable market-based fee to which the Parties mutually agree acting in a commercially reasonable manner. In addition, EnCana agrees that STML shall have the right, but not the obligation, to transport gas on this gathering system from xxxxx in the North Block in which STML owns an interest within the Assigned Interval. If STML moves gas produced from the Assigned Interval in the North Block on the EnCana gathering system in accordance with this paragraph, EnCana shall charge STML a reasonable market-based fee to which the Parties mutually agree acting in a commercially reasonable manner.
Sample 1
AutoNDA by SimpleDocs

Related to EnCana 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.

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

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

  • Drainage Systems (1) Clear culvert inlets, outlets, and sediment catching basins. (2) Maintain waterbars, drainage dips, and other water diversion measures. (3) During active use, patrol and maintain functional drainage. (4) Repair damaged culvert ends.

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

  • Interconnection Facilities 4.1.1 The Interconnection Customer shall pay for the cost of the Interconnection Facilities itemized in Attachment 2 of this Agreement. The NYISO, in consultation with the Connecting Transmission Owner, shall provide a best estimate cost, including overheads, for the purchase and construction of its Interconnection Facilities and provide a detailed itemization of such costs. Costs associated with Interconnection Facilities may be shared with other entities that may benefit from such facilities by agreement of the Interconnection Customer, such other entities, the NYISO, and the Connecting Transmission Owner. 4.1.2 The Interconnection Customer shall be responsible for its share of all reasonable expenses, including overheads, associated with (1) owning, operating, maintaining, repairing, and replacing its own Interconnection Facilities, and

  • 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

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Pipelines Developer shall have no interest in the pipeline gathering system, which gathering system shall remain the sole property of Operator or its Affiliates and shall be maintained at their sole cost and expense.

  • NETWORK INTERCONNECTION METHODS 3.1 The Interconnection provided herein may not be used solely for the purpose of originating a Party’s own interexchange traffic.

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