Shared Internet Sample Clauses

Shared Internet 
Sample 1
AutoNDA by SimpleDocs

Related to Shared Internet

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

  • Shared Services CUPE agrees to adopt a shared services model that will allow other Trusts to join the shared services model. The shared services office of the Trust is responsible for the services to support the administration of benefits for the members, and to assist in the delivery of benefits on a sustainable, efficient and cost effective basis recognizing the value of benefits to the members.

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

  • 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

  • Shared roles The Parties will meet the requirements of Schedule E, Clause 26 of the IGA FFR, by ensuring that prior agreement is reached on the nature and content of any events, announcements, promotional material or publicity relating to activities under this Agreement, and that the roles of both Parties will be acknowledged and recognised appropriately.

  • Shared Personal Data This clause sets out the framework for the sharing of personal data between the parties as data controllers. Each party acknowledges that one party (the Data Discloser) will regularly disclose to the other party (the Data Recipient) Shared Personal Data collected by the Data Discloser for the Agreed Purposes.

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

  • Other Transmission Rights Notwithstanding any other provision of this Agreement, nothing herein shall be construed as relinquishing or foreclosing any rights, including but not limited to firm transmission rights, capacity rights, or transmission congestion rights that the Developer shall be entitled to, now or in the future under any other agreement or tariff as a result of, or otherwise associated with, the transmission capacity, if any, created by the System Upgrade Facilities and System Deliverability Upgrades.

  • Treatment of Shared Contracts (a) Subject to applicable Law and without limiting the generality of the obligations set forth in Section 2.1, unless the Parties otherwise agree or the benefits of any contract, agreement, arrangement, commitment or understanding described in this Section 2.8 are expressly conveyed to the applicable Party pursuant to this Agreement or an Ancillary Agreement, any contract or agreement, a portion of which is a Varex Contract, but the remainder of which is a Parent Asset (any such contract or agreement, a “Shared Contract”), shall be assigned in relevant part to the applicable member(s) of the applicable Group, if so assignable, or appropriately amended prior to, on or after the Effective Time, so that each Party or the member of its Group shall, as of the Effective Time, be entitled to the rights and benefits, and shall assume the related portion of any Liabilities, inuring to its respective businesses; provided, however, that (i) in no event shall any member of any Group be required to assign (or amend) any Shared Contract in its entirety or to assign a portion of any Shared Contract which is not assignable (or cannot be amended) by its terms (including any terms imposing consents or conditions on an assignment where such consents or conditions have not been obtained or fulfilled) and (ii) if any Shared Contract cannot be so partially assigned by its terms or otherwise, or cannot be amended or if such assignment or amendment would impair the benefit the parties thereto derive from such Shared Contract, then the Parties shall, and shall cause each of the members of their respective Groups to, take such other reasonable and permissible actions (including by providing prompt notice to the other Party with respect to any relevant claim of Liability or other relevant matters arising in connection with a Shared Contract so as to allow such other Party the ability to exercise any applicable rights under such Shared Contract) to cause a member of the Varex Group or the Parent Group, as the case may be, to receive the rights and benefits of that portion of each Shared Contract that relates to the Varex Business or the Parent Business, as the case may be (in each case, to the extent so related), as if such Shared Contract had been assigned to a member of the applicable Group (or amended to allow a member of the applicable Group to exercise applicable rights under such Shared Contract) pursuant to this Section 2.8, and to bear the burden of the corresponding Liabilities (including any Liabilities that may arise by reason of such arrangement), as if such Liabilities had been assumed by a member of the applicable Group pursuant to this Section 2.8. (b) Each of Parent and Varex shall, and shall cause the members of its Group to, (i) treat for all Tax purposes the portion of each Shared Contract inuring to its respective businesses as an Asset owned by, and/or a Liability of, as applicable, such Party, or the members of its Group, as applicable, not later than the Effective Time, and (ii) neither report nor take any Tax position (on a Tax Return or otherwise) inconsistent with such treatment (unless required by applicable Law). (c) Nothing in this Section 2.8 shall require any member of any Group to make any non-de minimis payment (except to the extent advanced, assumed or agreed in advance to be reimbursed by any member of the other Group), incur any non-de minimis obligation or grant any non-de minimis concession for the benefit of any member of any other Group in order to effect any transaction contemplated by this Section 2.8.

  • Initiating Interconnection 4.1 If ENT determines to offer Telephone Exchange Services and to interconnect with Verizon in any LATA in which Verizon also offers Telephone Exchange Services and in which the Parties are not already interconnected pursuant to this Agreement, ENT shall provide written notice to Verizon of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.2 The notice provided in Section 4.1 of this Attachment shall include (a) the initial Routing Point(s); (b) the applicable technically feasible Point(s) of Interconnection on Verizon’s network to be established in the relevant LATA in accordance with this Agreement; (c) ENT’s intended Interconnection activation date; (d) a forecast of ENT’s trunking requirements conforming to Section 14.2 of this Attachment; and (e) such other information as Verizon shall reasonably request in order to facilitate Interconnection. 4.3 The interconnection activation date in the new LATA shall be mutually agreed to by the Parties after receipt by Verizon of all necessary information as indicated above. Within ten (10) Business Days of Verizon’s receipt of ENT’s notice provided for in Section 4.1of this Attachment, Verizon and ENT shall confirm the technically feasible Point of Interconnection on Verizon’s network in the new LATA and the mutually agreed upon Interconnection activation date for the new LATA.

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