Open Product/Process CR PC120301-6 Detail |
| Title: Two Six Code Inventory For Local Interconnection Trunk Groups Ordered By Qwest | ||||||
| CR Number |
Current Status Date |
Area Impacted | Products Impacted | |||
|
|
||||||
| PC120301-6 |
Completed 12/18/2002 |
Provisioning | Local Interconnection Service (LIS) | |||
| Originator: Stryczek, Kathy |
| Originator Company Name: AT&T |
| Owner: Olsen, Linda |
| Director: |
| CR PM: Thomte, Kit |
Description Of Change |
|
When Qwest orders a local interconnection trunk group, AT&T assigns the two-six code and returns it to Qwest on the FOC. Qwest should be inventorying the two-six code that AT&T assigns for Qwest-initiated ASRs. However, Qwest is not inventorying the AT&T two-six code. Qwest is assigning their own two-six code. This presents a major problem in a number of areas including maintenance. One of the first pieces of information asked by Qwest when AT&T reports a trouble is to provide the two-six code. AT&T provides the AT&T-assigned two-six code, but Qwest didn't inventory it so the Qwest maintenance group can't find the trunk group AT&T is reporting.
Here is the industry documentation from the ASOG for two-six code assignment:
53 TSC - Two Six Code
Identifies a code assigned to a trunk group or a CCS link Set.
NOTE 1: The code set is unique to each established trunk group or CCS Link Set and is provided to the customer on the Firm Order Confirmation or Design and Order Confirmation. The TSC entry may then be populated by the customer when ordering changes, additions or deletions to an existing trunk group or CCS Link Set.
Clearly Qwest is not in compliance with inventorying the two-six code, as the ASOG specifically states the two-six code is provided to the customer on the FOC. In the case where Qwest initiates ASRs, Qwest is the customer and AT&T is the supplier. Consequently, Qwest should be inventorying the two-six code provided by AT&T to Qwest on the FOC.
Expected Deliverables: AT&T expects that Qwest will comply with industry guidelines and change process to begin to inventory the two-six code that AT&T assigns to Qwest-initiated ASRs.
|
| Date | Action | Description |
| 12/3/2001 | CR Submitted by AT&T and acknowledged by Qwest | |
| 12/7/2001 | Clarification call arranged for 12/10/01, rescheduled for 12/11/01 at AT&T's request | |
| 12/11/2001 | Clarification call held with AT&T | |
| 12/12/2001 | CMP Meeting, AT&T introduced their CR, status changed to Clarification | |
| 12/14/2001 | Draft clarification meeting minutes issued to AT&T | |
| 1/16/2002 | January CMP meeting. The CR was clarified with the CLEC community. Qwest presented various potential manual and system options. Qwest received feedback on potential solutions and will continue to evaluate scenarios for presentation at the February CMP meeting. Status changed to "Evaluation" | |
| 2/12/2002 | Draft response sent to AT&T and entered into CMP Database | |
| 2/19/2002 | E-mail from AT&T with some questions about Qwest's response | |
| 2/20/2002 | February CMP meeting: Qwest response dated 02/12/02 presented to CLECs. Qwest will present expected time frame for system implementation at the March CMP meeting. CR Status changed to "Development" Meeting discussions will be set forth in the Product/Process Draft Meeting Minutes contained in the Product/Process CMP Meeting Distribution Package 03/20/02 | |
| 2/22/2002 | Formal response dated 02/12/02 issued to CLECs - Document Number: CMPR.02.22.02.F.01229.CR_Responses | |
| 3/20/2002 | March CMP Meeting: Status update provided to CLECs, CR status to remain in "Development." Meeting discussions will be set forth in the Product/Process Meeting Minutes to be posted on the CMP Web site | |
| 4/12/2002 | Revised response dated 04/10/02 sent to AT&T | |
| 4/12/2002 | Revised response dated 04/10/02 posted to the web | |
| 4/17/2002 | April CMP Meeting: Qwest presented revised response dated 04/10/02. Qwest agreed to open a related systems CR. Status of this CR to be advised after discussions with Judy Schultz. Meeting discussions will be set forth in the Product/Process Meeting Minutes to be posted on the CMP Web site | |
| 4/24/2002 | Issued Systems CR to cmpcr@qwest.com on behalf of AT&T | |
| 5/15/2002 | May CMP Meeting: CLEC participants agreed that the CR could be closed. Meeting discussions will be set forth in the Product/Process Meeting Minutes to be posted on the CMP Web site. | |
| 6/14/2002 | Held status session with AT&T | |
| 6/25/2002 | Held status session with AT&T | |
| 6/27/2002 | Held status session with AT&T | |
| 7/11/2002 | Held status session with AT&T | |
| 7/18/2002 | This CR was reopened under Product and Process as agreed to in the monthly Systems CMP meeting. | |
| 7/25/2002 | Held status session with AT&T | |
| 8/21/2002 | August CMP Meeting: This CR will remain in "Development" Meeting minutes posted to this CR's Project Meetings section and the CMP Web site. | |
| 9/11/2002 | Sent Revised Response to AT&T | |
| 9/18/2002 | September CMP Meeting: This CR will remain in "Development" Meeting minutes posted to this CR's Project Meetings section and the CMP Web site. | |
| 9/26/2002 | Contacted AT&T to establish status session. | |
| 10/7/2002 | Held status Meeting with AT&T | |
| 10/16/2002 | October CMP Meeting: This CR will remain in "Development" Status Meeting minutes posted to this CR's Project Meetings section and the CMP Web site. | |
| 11/20/2002 | November CMP Meeting: This CR was changed to "CLEC Test" Status, Meeting minutes posted to this CR's Project Meeting section and the CMP Web site. | |
| 12/18/2002 | December CMP Meeting: This CR Changed to Completed status. Meeting Minutes posted to this CR's Project Meeting sectiona dn the CMP Web site. |
Project Meetings |
| 12/18/02 - December CMP Meeting Qwest (Thomte) reported that the process is working as agreed to AT&T advised it is O.K. to close this CR. This CR will change to Completed status. 11/20/02 November CMP Meeting Qwest (Thomte) indicated that the trial orders that were established to convert the embedded base trunk groups in Wyoming were successful. The result is that both new trunks and embedded trunk groups appear to process through the systems using the AT&T Two Six code of CC. Qwest recommended that this CR move to CLEC Test and potentially be completed in December. 10/16/02 October CMP Meeting Qwest (Thomte) indicated that the trial was continuing and that two trial groups that are due to complete in early November. This CR to remain in “Develoment”.
08/21/02 - August CMP Meeting Qwest (Thomte) indicated progress had been made on this CR. Back end systems and reporting capability should be capable of accepting non Qwest two six code during September. Qwest and AT&T anticipate having a status meeting in late August. AT&T (Van Meter) concurred with the read out. This CR will remain in "Development" status
02/19/02 E-mail from AT&T with some questions about Qwest's response
Subject: RE: Qwest Response to Change Request PC120301-6 "Two-Six Code Inv entory for Local Interconnection Trunk Groups Ordered by Qwest" Date: Tue, 19 Feb 2002 17:20:24 -0600 From: "Stryczek, Kathleen K (Kathy), BNSVC"
Clarification Call, December 11, 2001, 11:00 am (MDT)
Attendees: Todd Mead, Qwest Linda Kae Olsen, Qwest Peggy Kilgus, Qwest Ann Adkinisson, AT&T Kathy Stryczek, AT&T Ester Shearer, AT&T
Reviewed description of Change Request.
Products impacted: Local Interconnection Service (LIS) Qwest need to have someone from the repair group who is involved in the management and use of the TIRKS system, involved in preparing the response to this CR. AT&T's expectation: AT&T would like Qwest to use the two-six code provided by AT&T when Qwest places an order for a local trunk group.
Action Plan: - Qwest will evaluate various options. This CR will be clarified with the CLEC Community at the January CMP Meeting. Qwest will provide a draft response for discussion at the February 2002 CMP meeting. - AT&T will provide Qwest with a contact in Ameritech to discuss ordering process and use of two-six codes. - Qwest to identify and involve the appropriate repair/TIRKS person to assist Linda in developing the draft response. An internal meeting will be held by next Wednesday (12/19/01)
|
CenturyLink Response |
|
REVISED RESPONSE September 6, 2002 Kathy Stryczek AT&T Subject: PC120301-6 Two-Six Code Inventory for Local Interconnection Trunk Groups Ordered By Qwest This is a revised Qwest response to AT&T’s request, that Qwest comply with industry guidelines and change process to begin to inventory the two-six code that AT&T assigns to Qwest-initiated ASRs. Qwest accepts AT&T’s request regarding complying with industry guidelines and inventory the two six code that is provided to Qwest on the FOC. Qwest has worked in conjunction with AT&T to provide a trial request that will flow through the various systems and reporting processes. Qwest is currently making the appropriate modifications to support the request for AT&T. Currently Qwest has one order that is in a trial process. AT&T has advised that they have additional orders expected in the near future. Qwest expects to address AT&T’s additional orders with the revised process. Sincerely, Qwest
REVISED RESPONSE September 6, 2002 Kathy Stryczek AT&T Subject: PC120301-6 Two-Six Code Inventory for Local Interconnection Trunk Groups Ordered By Qwest This is a revised Qwest response to AT&T’s request, that Qwest comply with industry guidelines and change process to begin to inventory the two-six code that AT&T assigns to Qwest-initiated ASRs. Qwest accepts AT&T’s request regarding complying with industry guidelines and inventory the two six code that is provided to Qwest on the FOC. Qwest has worked in conjunction with AT&T to provide a trial request that will flow through the various systems and reporting processes. Qwest is currently making the appropriate modifications to support the request for AT&T. Currently Qwest has one order that is in a trial process. AT&T has advised that they have additional orders expected in the near future. Qwest expects to address AT&T’s additional orders with the revised process. Sincerely, Qwest
REVISED RESPONSE April 10, 2002 Ms. Kathy Stryczek Manager AT&T SUBJECT: Qwest’s Change Request Response - CR # PC120301-6 Two-Six Code Inventory for Local Interconnection Trunk Groups Ordered by Qwest This letter is a follow-up response to AT&T Change Request PC120301-6, requesting Qwest inventory the two-six code that AT&T assigns for Qwest initiated ASRs. Qwest’s written response dated February 12, 2002 informed the CLEC community that Qwest was willing to perform a detailed economic and technical investigation to evaluate the feasibility of implementing the system changes required to meet the intent of this CR. Qwest has completed its evaluation and has concluded the cost of changing the myriad of downstream-related systems needed to effect this change is prohibitive. Qwest suggests deferral of this CR until the 2003 fiscal year funding review, planned for later this year. Therefore Qwest regretfully informs AT&T that this CR cannot be processed this year. Sincerely, Susan Bliss Director Process Management Qwest
FORMAL RESPONSE February 12, 2002 AT&T Ms. Kathy Stryczek Manager SUBJECT: Qwest’s Change Request Response - CR PC120301-6 Two-Six Code Inventory for Local Interconnection Trunk Groups Ordered by Qwest This letter is in response to AT&T Change Request PC120301-6, Two-Six Code Inventory For Local Interconnection Trunk Groups Ordered By Qwest. AT&T has requested that Qwest inventory the two-six code that AT&T assigns for Qwest initiated ASRs. During the CLEC Community clarification meeting held January 16, 2002, AT&T confirmed their desire for Qwest to inventory the TSC provided on the FOC for the order. AT&T agreed that this TSC, along with the TCICs and ACTL information provided today, could be provided during the up-front planning meeting for new markets. Qwest could then use this code as the PON number as well as possibly make program modifications that would allow it to be used as the TSC (TGAC) in the processing and inventory systems used by Qwest (EXACT, IABS, TIRKS, WFA, TRDB, etc.) Qwest is willing to pursue internal system changes to evaluate the feasibility (technical and economical) of implementing such changes. Qwest can not determine all of the systems that would be impacted, nor what the downstream effects on the process would be until the systems evaluations are performed. If this approach is acceptable to AT&T, Qwest will initiate the required internal system changes and provide a status update at the March CMP meeting. Sincerely, Linda Kae Olsen Process Specialist - LIS Qwest
|
Information Current as of 1/11/2021