Common use of NC/NCI CODES Clause in Contracts

NC/NCI CODES. xDSL Capable Loops 9.2.2.3.5.5.1 For Embedded Base xDSL Capable Loops, there may be instances when the NC code and/or NCI code associated with the CLEC customer’s xDSL Service [which has been working for the customer, irrespective of the NC/NCI code(s) associated with the customer’s xDSL Service] is not the same as the NC code and/or NCI code the Parties will use after the Final Implementation Date. When the need for a Repair occurs or Spectrum Management issues arise (e.g., after a Qwest network maintenance and modernization activity), however, CLEC may desire a change in the NC/NCI code(s) to conform it to the NC/NCI code(s) reflected in this Amendment. Qwest may not decline to proceed with Conditioning or with accepting and working to resolve trouble reports on the grounds that the NC/NCI code(s) are different or need changing for Embedded Base xDSL Capable Loops. 9.2.2.3.5.5.1.1 For Embedded Base xDSL Capable Loops, when submitting a trouble report, CLEC may request that Qwest change the NC code and/or NCI code to the applicable NC code and/or NCI code, such as described in Attachment 2. No CLEC service request, supplement, or supplemental request is needed to change the NC/NCI code(s) before CLEC submits a trouble report or before Qwest performs the Repair. After submitting a trouble report, CLEC will promptly submit a service request to change the NC/NCI codes to the xDSL Service actually deployed on the Embedded Base xDSL Capable Loop. Qwest will implement the change to the NC code and/or NCI code in Qwest’s records with no change to the circuit identifier. After processing of the service request, the circuit history in CEMR (or successor system) will reflect the change in NC/NCI code(s) to identify the new NC/NCI code(s). These NC/NCI code changes do not require project handling. 9.2.2.3.5.5.1.1.1 Regarding future changes to NC/NCI codes, see Section 9.2.2.3.5.5.3.1. 9.2.2.3.5.5.2 For Non-Embedded Base xDSL Capable Loops, the Parties agree to use the NC/NCI codes as described in Attachment 2 and Section 9.2.2.

Appears in 9 contracts

Samples: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement

AutoNDA by SimpleDocs

NC/NCI CODES. xDSL Capable Loops 9.2.2.3.5.5.1 For Embedded Base xDSL Capable Loops, there may be instances when the NC code and/or NCI code associated with the CLEC customer’s xDSL Service [which has been working for the customer, irrespective of the NC/NCI code(s) associated with the customer’s xDSL Service] is not the same as the NC code and/or NCI code the Parties will use after the Final Implementation Date. When the need for a Repair occurs or Spectrum Management issues arise (e.g., after a Qwest CenturyLink network maintenance and modernization activity), however, CLEC may desire a change in the NC/NCI code(s) to conform it to the NC/NCI code(s) reflected in this Amendment. Qwest CenturyLink may not decline to proceed with Conditioning or with accepting and working to resolve trouble reports on the grounds that the NC/NCI code(s) are different or need changing for Embedded Base xDSL Capable Loops. 9.2.2.3.5.5.1.1 For Embedded Base xDSL Capable Loops, when submitting a trouble report, CLEC may request that Qwest CenturyLink change the NC code and/or NCI code to the applicable NC code and/or NCI code, such as described in Attachment 2. No CLEC service request, supplement, or supplemental request is needed to change the NC/NCI code(s) before CLEC submits a trouble report or before Qwest CenturyLink performs the Repair. After submitting a trouble report, CLEC will promptly submit a service request to change the NC/NCI codes to the xDSL Service actually deployed on the Embedded Base xDSL Capable Loop. Qwest CenturyLink will implement the change to the NC code and/or NCI code in QwestCenturyLink’s records with no change to the circuit identifier. After processing of the service request, the circuit history in CEMR (or successor system) will reflect the change in NC/NCI code(s) to identify the new NC/NCI code(s). These NC/NCI code changes do not require project handling. 9.2.2.3.5.5.1.1.1 Regarding future changes to NC/NCI codes, see Section 9.2.2.3.5.5.3.1. 9.2.2.3.5.5.2 For Non-Embedded Base xDSL Capable Loops, the Parties agree to use the NC/NCI codes as described in Attachment 2 and Section 9.2.2.

Appears in 1 contract

Samples: Interconnection Agreement

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