Technical References. Technical References that describe the practices, procedures and specifications for certain services (and the applicable interfaces relating thereto) are listed on Schedule 2.3 (the “Technical Reference Schedule”) to assist the Parties in meeting their respective responsibilities hereunder.
Technical References. The Parties agree that the Technical References listed on Schedule 2.3 (the “Technical Reference Schedule”), are generally accepted guidelines for interface and performance parameters of equipment and facilities used by LEC’s in the United States for delivering Telephone Exchange Service. These Technical References are used by the Parties in specifying suitable equipment and facilities components for use in their respective networks, and for assuring interoperability between components that collectively comprise such networks. Each Party will strive to their utmost ability to comply with these industry standards, but will not be liable for any non-compliance by any vendor furnishing such equipment or facilities, provided that such equipment/facilities are of a type generally deployed throughout the industry, currently or at the time deployed. Nothing in this Section shall require a Party to deliver performance, functionality or capabilities from specific equipment or facilities beyond that intended by its vendor. CLEC is entitled to request through the BFR process functions and capabilities described in the Technical References listed in Schedule 2.3 which CBT has not deployed or activated in its own network.
Technical References. 23.19.1 This Agreement contains technical references for unbundled network elements, ancillary services, and interconnection facilities. Due to the manner in which individual equipment manufacturers have chosen to implement industry standards into the design of their products, along with differing vintages of individual facility components and the presence of embedded technologies that pre-date current technical references, individual facility components deployed within GTE’s network need not meet or adhere to, and may differ significantly from, the technical references included in this Agreement. Nothing in this Agreement shall prohibit GTE from improving or otherwise modifying its network, including, but not limited to, improvements or modifications to individual facility components, and such improvements or modifications need not meet or adhere to any of the technical references cited throughout this Agreement. Accordingly, the Parties acknowledge and agree that the technical references contained in this Agreement shall be used only by them as a reference for their own internal network and operational service planning for unbundled network elements, ancillary services, and interconnection facilities. The technical references contained in this Agreement shall not, however, be interpreted to require GTE to satisfy any of its obligations set forth in this Agreement in accordance with any specification set forth therein.
23.19.2 AT&T may request technical information related to any unbundled network element, ancillary service, or interconnection facility offered pursuant to this Agreement. GTE will supply such technical information pursuant to the processes and procedures currently in place between the Parties for answering similar requests for technical information with regard to interLATA access. The Parties agree that GTE will provide technical information belonging to GTE that GTE designates as proprietary and that GTE is otherwise authorized to release pursuant to the nondisclosure provisions of this Agreement. In the event GTE's supplier has designated such information as proprietary, GTE will assist AT&T in seeking the supplier's consent to review such technical information. The number and nature of requests shall be reasonable. If at such time as the above processes and procedures have been utilized by the Parties for a period no shorter than ninety (90) days after receipt by the applicable Party of an initial request, and upon receipt of notice fro...
Technical References. (subject to Section 23.19 of the General Terms and Conditions of this Agreement): Specific Loops as described in 3.1.1.1 through 3.1.1.4 are capable of transmitting signals for the following services (as needed by AT&T to provide end-to-end service capability to its end-user customer):
Technical References. (subject to Section 23.19 of the General Terms and Conditions of this Agreement): The technical references set forth in this Section 4.2 apply to Local Switching.
Technical References. 15.1 The Parties agree that the Bell Atlantic technical references set forth in Appendix I to this Part A (Technical Reference Schedule) provide the current technical specifications for the services offered by Bell Atlantic under this Agreement. Bell Atlantic reserves the right with reasonable notification to revise its technical references for any reason including, but not limited to, laws or regulations, conformity with updates and changes in standards promulgated by various agencies, utilization of advances in the state of technical arts, or the reflection of changes in the design of any facilities, equipment, techniques, or procedures described or referred to in the technical references. Notification of changes that are made to the underlying Bell Atlantic services will be made in conformance with the requirements of Section 251(c)(5), Notice of Changes, of the Act, and the FCC’s Rules and Regulations. The Parties acknowledge that the general technical references set forth below contain certain generally accepted industry guidelines for particular interface and performance parameters for telecommunications equipment used by LECs in the United States. Such accepted technical references may be used by LECs to specify suitable equipment and facilities components for use in their respective networks, to assure interoperability between components that collectively comprise such networks, and to specify the interface characteristics and typical end-to- end performance of certain services.
15.2 The Parties acknowledge that they and their vendors and suppliers derive guidance from such technical references, and make reasonable efforts to conform to them. Requests for specific performance, functionality, or capabilities not applied in a Party’s network should be handled using the BFR process set forth in Section 25 (BFR Process for Further Unbundling) of this Part A.
15.3 If one or more of the technical requirements set forth in Appendix I are in conflict, the Parties shall reasonably agree on which requirement shall apply.
15.4 The Parties agree that they each intend, to the extent technically feasible and commercially reasonable, to conform generally to industry standards applicable to the Parties set by the OBF, within a reasonable time after publication of final standards. With respect to OBF and other industry standards, the Parties agree that they will negotiate in good faith the applicability, technical feasibility and commercial reasonableness for imple...
Technical References. Technical References that describe and/or define the practices, procedures and specifications for those services, Interconnections and access to unbundled Network Elements available hereunder (and the applicable interfaces relating thereto) include, but are not limited to, those listed on Schedule 2.3 (the “Technical Reference Schedule”). The Implementation Team may mutually agree in writing to add or delete Technical References from the Technical Reference Schedule from time to time.
Technical References. The Parties agree that the Technical References listed on
Technical References. The Parties agree that the BA technical references set forth in the Exhibit to this Attachment 14 (Technical Reference Schedule) provide the current technical specifications for the services offered by BA under this Agreement. BA reserves the right with reasonable notification to revise its technical references for any reason including, but not limited to, laws or regulations, conformity with updates and changes in standards promulgated by various agencies, utilization of advances in the state of technical arts, or the reflection of changes in the design of any facilities, equipment, techniques, or procedures described or referred to in the technical references. Notification of changes that are made to the underlying BA services will be made in conformance with the requirements of Section 251, Notice of Change, of the Act, and the FCC’s Rules and Regulations. The Parties acknowledge that the general technical references set forth below contain certain generally accepted industry guidelines for particular interface and performance parameters for telecommunications equipment used by LECs in the United States. Such accepted technical references may be used by LECs to specify suitable equipment and facilities components for use in their respective networks, to assure interoperability between components that collectively comprise such networks, and to specify the interface characteristics and typical end-to-end performance of certain services.
Technical References. SCPs/Databases shall be consistent with the following technical references:
9.16.7.1 GR-246-CORE, Xxxx Communications Research Specification of Signaling System Number 7, Issue 1 (Telcordia, December 1994);
9.16.7.2 GR-1432-CORE, CCS Network Interface Specification (CCSNIS) Supporting Signaling Connection Control Part (SCCP) and Transaction Capabilities Application Part (TCAP) (Telcordia, March 1994);
9.16.7.3 GR-954-CORE, CCS Network Interface Specification (CCSNIS) Supporting Line Information Database (LIDB) Service 6, Issue 1, Rev. 1 (Telcordia, October 1995);
9.16.7.4 XX-0000-XXXX, XXXXX Section 10: System Interfaces, Issue 1 (Telcordia, October 1995) (Replaces TR-NWT-001149);
9.16.7.5 XX-0000-XXXX, XXXXX Section 22.3: Line Information Database 6, Issue (Telcordia, October 1995); and
9.16.7.6 WGR-1428-CORE, CCS Network Interface Specification (CCSNIS) Supporting Toll Free Service (Telcordia, May 1995).
