Network Elements Clause Samples
The 'Network Elements' clause defines the specific components, infrastructure, and equipment that make up a telecommunications or data network as referenced in the agreement. This clause typically outlines what constitutes a network element, such as routers, switches, transmission lines, or other hardware and software necessary for network operation. By clearly identifying these elements, the clause ensures both parties have a mutual understanding of the assets involved, which is essential for maintenance responsibilities, service level agreements, and risk allocation.
Network Elements. At the request of Requesting Carrier, Ameritech shall provide Requesting Carrier access to the following Network Elements on an unbundled basis:
9.2.1 Unbundled Local Loops, as more fully described on Schedule 9.2.1; and
9.2.2 Interoffice Transmission Facilities, as more fully described on Schedule 9.2.2.
Network Elements. At the request of CLEC, CBT shall provide CLEC access to the following Network Elements on an unbundled basis:
9.2.1 Local Loops, as more fully described on Schedule 9.2.1;
9.2.2 The Network Interface Device, as more fully described on Schedule 9.2.2;
9.2.3 Switching Capability, as more fully described on Schedule 9.2.3;
9.2.4 Interoffice Transmission Facilities, as more fully described on
9.2.5 Signaling Links and Call-Related Databases, as more fully described on
9.2.6 Operations Support Systems (“OSS”) functions as more fully described on
9.2.7 Subloops, as more fully described on Schedule 9.2.7; and
9.2.8 High Frequency Portion of the Loop, as more fully described on Schedule
Network Elements. 9.2.1 SBC-AMERITECH shall provide CLEC access to Network Elements on an unbundled basis (and combinations of Network Elements as set forth in Section 9.3 of this Article) at rates, terms and conditions that are just, reasonable and non-discriminatory in accordance with the terms and conditions of this Agreement and the requirements of Section 251 and Section 252 of the Act and applicable FCC Orders and other applicable laws.
9.2.2 SBC-AMERITECH will permit CLEC to interconnect CLEC’s facilities or facilities provided by CLEC or to CLEC by SBC-AMERITECH or third parties with each of SBC-AMERITECH’s unbundled Network Elements or Combinations at any technically feasible point designated by CLEC. Any request by CLEC to interconnect at a point not previously established: (i) in accordance with the terms of this Agreement (e.g., other than as set forth in the descriptions of unbundled Network Elements and Combinations under the following provisions of this Article IX and Schedules 9.2.1 through 9.2.9.), or (ii) under any arrangement SBC-AMERITECH may have with another Telecommunications Carrier, shall be subject to the Bona Fide Request process set forth in Article XIX (General Responsibilities of the Parties) of this Agreement. Any arrangement SBC-AMERITECH may have with another Telecommunications Carrier is presumed to be technically feasible; however, SBC-AMERITECH may rebut this presumption with clear and convincing evidence to the contrary in its response to an CLEC Bona Fide Request, pursuant to 47 C.F.R. §51.321(c).
Network Elements. At the request of Requesting Carrier, Ameritech shall provide Requesting Carrier access to the following Network Elements on an unbundled basis:
9.2.1 Local Loops, as more fully described on Schedule 9.2.1;
9.2.2 The Network Interface Device, as more fully described on Schedule 9.2.2;
9.2.3 Switching Capability, as more fully described on Schedule 9.2.3;
9.2.4 Interoffice Transmission Facilities, as more fully described on Schedule 9.2.4;
9.2.5 Signaling Links and Call-Related Databases, as more fully described on Schedule
9.2.6 Operations Support Systems (“OSS”) Functions, to be used in conjunction with other Network Elements, as more fully described on Schedule 9.2.6; and
9.2.7 Operator Services and Directory Assistance, as more fully described on Schedule
Network Elements. The charges that MCIm shall pay to Bell Atlantic for Network Elements are set forth in Table 1 of this Attachment I. BELL ATLANTIC-PENNSYLVANIA, INC. AND MCIm DETAILED SCHEDULE OF ITEMIZED CHARGES1
Network Elements. At the request of CLEC, CBT shall provide CLEC access to the following Network Elements on an unbundled basis:
9.2.1 Local Loops, as more fully described on Schedule 9.2.1;
9.2.2 The Network Interface Device, as more fully described on Schedule 9.2.2;
Network Elements. Until the Federal Communications Commission or the State Commission promulgate new rules specifying the mandatory unbundled Network Elements in accordance with the remand instructions of the United States Supreme Court, at the request of CLEC, CBT shall provide CLEC access to the following Network Elements on an unbundled basis: 9.2.1 Local Loops, as more fully described on Schedule 9.2.1;
Network Elements. At the request of Requesting Carrier, Ameritech shall provide Requesting Carrier access to the following Network Elements on an unbundled basis:
Network Elements. At the request of CLEC, Ameritech shall provide CLEC access to the following Network Elements on an unbundled basis:
IX.2.1 Local Loops, as more fully described on Schedule 9.2.1;
IX.2.2 The Network Interface Device, as more fully described on Schedule 9.2.2;
IX.2.3 Switching Capability, as more fully described on Schedule 9.2.3;
IX.2.4 Interoffice Transmission Facilities, as more fully described on Schedule 9.2.4;
IX.2.5 Signaling Links and Call-Related Databases, as more fully described on Schedule
IX.2.6 Operations Support Systems (OSS) Functions, to be used in conjunction with other Network Elements, as more fully described on Schedule 9.2.6; and
IX.2.7 Operator Services and Directory Assistance, as more fully described on Schedule
Network Elements. 9.2.1 SBC-AMERITECH shall provide AT&T access to Network Elements on an unbundled basis (and combinations of Network Elements as set forth in Section 9.3 of this Article) at rates, terms and conditions that are just, reasonable and non- discriminatory in accordance with the terms and conditions of this Agreement and the requirements of Section 251 and Section 252 of the Act and applicable FCC Orders and other applicable laws.
9.2.2 SBC-AMERITECH will permit AT&T to interconnect AT&T’s facilities or facilities provided by AT&T or to AT&T by SBC-AMERITECH or third parties with each of SBC-AMERITECH’s unbundled Network Elements or Combinations at any technically feasible point designated by AT&T. Any request by AT&T to interconnect at a point not previously established: (i) in accordance with the terms of this Agreement (e.g., other than as set forth in the descriptions of unbundled Network Elements and Combinations under the following provisions of this Article IX and Schedules 9.2.1 through 9.2.9), or (ii) under any arrangement SBC-AMERITECH may have with another Telecommunications Carrier, shall be subject to the Bona Fide Request process set forth on Schedule 2.2 of this Agreement.
9.2.3 At such time that AT&T provides SBC-AMERITECH with an order for particular unbundled Network Elements or Combinations, AT&T, at its option, may designate any technically feasible network interface, including without limitation, DS0, DS-1 and DS-3 interfaces, and any other interface described in the applicable Bell Communications Research (“Bellcore”) and any other industry standard technical references. Any such requested network interface shall be provided by SBC- AMERITECH, unless SBC-AMERITECH provides AT&T, within five (5) days, with a written notice that it believes such a request is technically infeasible, including a detailed statement supporting such claim. Any such denial shall be resolved in accordance with the Alternative Dispute Resolution process set forth in Article XXVIII of this Agreement. Unless otherwise specified, any references to DS-1 in this Article IX shall mean, at AT&T’s option, either DS-1 AMI or xDSL facility.
9.2.4 AT&T may use one or more Unbundled Network Elements or Combinations to provide to AT&T Customers any feature, function, capability or service option that such Network Element provided on an unbundled basis or Combination is technically capable of providing or any feature, function, capability or service option that is described in th...