Common use of Joint Network Implementation and Grooming Process Clause in Contracts

Joint Network Implementation and Grooming Process. Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia, (a) standards to ensure that Traffic Exchange Trunks experience a grade of service, availability and quality which is comparable to that achieved on interoffice trunks within BA’s network and in accord with all appropriate relevant industry-accepted quality, reliability and availability standards. Trunks provided by either Party for Interconnection services will be engineered using a design blocking objective of B.01 (Blocking Level B.01 – high-day-network-busy-hour blocking standard as defined in Bellcore’s special report- (Bellcore –SR TAP000191)); (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the trunk groups, including, but not limited to, standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery provision escalations; (d) additional technically feasible and geographically relevant IP(s) in a LATA as provided in Section 4.2.3 and 4.2.4; and (e) such other matters as the Parties may agree, including, e.g., End Office to End Office high usage trunks as good engineering practices may dictate. Nothing in this Section 10.1 shall affect either Party’s obligations to meet the milestone dates set forth in Schedule 4.1 hereof.

Joint Network Implementation and Grooming Process. Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia, (a) standards to ensure that Traffic Exchange Trunks experience a grade of service, availability and quality which is comparable to that achieved on interoffice trunks within BAVERIZON’s network and in accord with all appropriate relevant industry-accepted quality, reliability and availability standards. Trunks Except as otherwise stated in this Agreement, trunks provided by either Party for Interconnection services will be engineered using a design blocking objective of B.01 (Blocking Level B.01 – high-high- day-network-busy-hour blocking standard as defined in Bellcore’s special report- (Bellcore –SR TAP000191)); (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the trunk groups, including, but not limited to, standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery provision escalations; (d) additional technically feasible and geographically relevant IP(s) in a LATA as provided in Section 4.2.3 and 4.2.4; and (e) such other matters as the Parties may agree, including, e.g., End Office to End Office high usage trunks as good engineering practices may dictate. Nothing in this Section 10.1 14.1 shall affect either Party’s obligations to meet the milestone dates set forth in Part V, Schedule 4.1 1.1 hereof.

Joint Network Implementation and Grooming Process. Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia, (a) standards to ensure that Traffic Exchange Trunks experience a grade of service, availability and quality which is comparable to that achieved on interoffice trunks within BA’s network and in accord with all appropriate relevant industry-accepted quality, reliability and availability standards. Trunks provided by either Party for Interconnection services will be engineered using a design blocking objective of B.01 (Blocking Level B.01 – high-day-network-busy-hour blocking standard as defined in Bellcore’s special report- (report “Bellcore –SR TAP000191)”); (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the trunk groups, including, but not limited to, standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery provision escalations; (d) additional technically feasible and geographically relevant IP(s) in a LATA as provided in Section 4.2.3 and 4.2.4; and (e) such other matters as the Parties may agree, including, e.g., End Office to End Office high usage trunks as good engineering practices may dictate. Nothing in this Section 10.1 shall affect either Party’s obligations to meet the milestone dates set forth in Schedule 4.1 hereof.

Joint Network Implementation and Grooming Process. Upon request of either PartyOn or before March 1, 1997, unless the Parties agree to a different date, TCG and BA shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may shall define and detail, inter alia, (a) standards to ensure that Traffic Exchange Trunks Interconnection trunk groups experience a grade of service, availability and quality which is comparable to that achieved on interoffice trunks within BA’s network and in accord with all appropriate relevant industry-accepted quality, reliability and availability standards. Trunks provided by either Party for Interconnection services will be engineered using a design blocking objective of B.01 (Blocking Level B.01 – high-day-network-busy-hour blocking standard as defined in Bellcore’s special report- (Bellcore –SR TAP000191))B.01; (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the trunk groups, including, but not limited to, standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery provision escalations; (d) migration from one-way to two-way Interconnection Trunks upon mutual agreement of the Parties; (e) the procedures to govern any TCG request for information concerning available BA network facilities that TCG may purchase as unbundled Network Elements to connect the beginning and end points within given exchanges specified by TCG in its request; and (f) additional technically feasible and geographically relevant IP(s) IPs in a LATA as provided in Section 4.2.3 and 4.2.4subsection 4.1.4 above; and (eg) such other matters as the Parties may agree, including, e.g., End Office to End Office high usage trunks as good engineering practices may dictate. Nothing in this Section subsection 10.1 shall affect either Party’s obligations to meet the milestone dates set forth in Schedule 4.1 3.0 hereof.

Joint Network Implementation and Grooming Process. Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia, (a) standards to ensure that Traffic Exchange Trunks experience a grade of service, availability and quality which is comparable to that achieved on interoffice trunks within BA’s network and in accord with all appropriate relevant industry-accepted quality, reliability and availability standards. Trunks provided by either Party for Interconnection services will be engineered using a design blocking objective of B.01 (Blocking Level B.01 – high-day-network-busy-hour blocking standard as defined in Bellcore’s special report- (Bellcore –SR TAP000191)); (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the trunk groups, including, but not limited to, standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery provision escalations; (d) additional technically feasible and geographically relevant IP(s) in a LATA as provided in Section Sections 4.2.3 and 4.2.4; and (e) such other matters as the Parties may agree, including, e.g., End Office to End Office high usage trunks as good engineering practices may dictate. Nothing in this Section 10.1 shall affect either Party’s obligations to meet the milestone dates set forth in Schedule 4.1 hereof.

Joint Network Implementation and Grooming Process. Upon the request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia,alia,‌‌ (a) standards to ensure that Traffic Exchange Trunks experience a grade of service, availability and quality which is comparable to that achieved on interoffice trunks within BA’s network and in accord with all appropriate relevant industry-accepted quality, reliability and availability standards. Trunks provided by either Party for Interconnection services will be engineered using a design blocking objective of B.01 (Blocking Level B.01 – - high-day-network-busy-hour blocking standard as defined in Bellcore’s special report- report - (Bellcore –SR - ST TAP000191)); (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the trunk groups, including, but not limited to, standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery provision escalations; (d) additional technically feasible and geographically relevant IP(s) in a LATA as provided in Section Sections 4.2.3 and 4.2.4; and (e) such other matters as the Parties may agree, including, e.g., End Office to End Office high usage trunks as good engineering practices may dictate. Nothing in this Section 10.1 shall affect either Party’s obligations to meet the milestone dates set forth in Schedule 4.1 hereof.

Joint Network Implementation and Grooming Process. Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia, (a) standards to ensure that Traffic Exchange Trunks experience a grade of service, availability and quality which is comparable to that achieved on interoffice trunks within BA’s network and in accord with all appropriate relevant industry-accepted quality, reliability and availability standards. Trunks provided by either Party for Interconnection services will be engineered using a design blocking objective of B.01 (Blocking Level B.01 – high-day-network-busy-hour blocking standard as defined in Bellcore’s special report- (Bellcore –SR TAP000191)); (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the trunk groups, including, but not limited to, standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery provision escalations; (d) additional technically feasible and geographically relevant IP(s) in a LATA as provided in Section 4.2.3 and 4.2.4; and (e) such other matters as the Parties may agree, including, e.g., End Office to End Office high usage trunks as good engineering practices may dictate. dictate.‌‌ Nothing in this Section 10.1 shall affect either Party’s obligations to meet the milestone dates set forth in Schedule 4.1 hereof.

Joint Network Implementation and Grooming Process. Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia, (a) standards to ensure that Traffic Exchange Trunks experience a grade of service, availability and quality which is comparable to that achieved on interoffice trunks within BA’s network and in accord with all appropriate relevant industry-accepted quality, reliability and availability standards. Trunks provided by either Party for Interconnection services will be engineered using a design blocking objective of B.01 (Blocking Level B.01 – high-day-network-busy-hour blocking standard as defined in Bellcore’s special report- (Bellcore –SR TAP000191));TAP000191));‌‌ (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the trunk groups, including, but not limited to, standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery provision escalations; (d) additional technically feasible and geographically relevant IP(s) in a LATA as provided in Section 4.2.3 and 4.2.4; and (e) such other matters as the Parties may agree, including, e.g., End Office to End Office high usage trunks as good engineering practices may dictate. Nothing in this Section 10.1 shall affect either Party’s obligations to meet the milestone dates set forth in Schedule 4.1 hereof.

Joint Network Implementation and Grooming Process. Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia, (a) standards to ensure that Traffic Exchange Trunks experience a grade of service, availability and quality which is comparable to that achieved on interoffice trunks within BA’s network and in accord with all appropriate relevant industry-accepted quality, reliability and availability standards. Trunks provided by either Party for Interconnection services will be engineered using a design blocking objective of B.01 (Blocking Level B.01 – high-day-day- network-busy-hour blocking standard as defined in Bellcore’s special report- (report “Bellcore –SR TAP000191)”); (b) the respective duties and responsibilities of the Parties with respect to the administration and maintenance of the trunk groups, including, but not limited to, standards and procedures for notification and discoveries of trunk disconnects; (c) disaster recovery provision escalations; (d) additional technically feasible and geographically relevant IP(s) in a LATA as provided in Section 4.2.3 and 4.2.4; and (e) such other matters as the Parties may agree, including, e.g., End Office to End Office high usage trunks as good engineering practices may dictate. Nothing in this Section 10.1 shall affect either Party’s obligations to meet the milestone dates set forth in Schedule 4.1 hereof.