Wholesale: Products & Services

Archived System CR SCR010705-01 Detail

Sprint has been working with Charlie Fetters and Patricia Salazar to understand Qwest’s current process. While it has been an education, Sprint believes that the process can be significantly improved in this area. This change will greatly benefit other CLECs that have to make changes to the directory listing when processing an LNP order. This change would be of tremendous value to Sprint because the majority of our orders (98% or higher) that are sent to Qwest are for LNP. Statistics are not available for the number of changes to the directory listing.

When conducting the same type of transaction with other ILECs, Sprint can port the number AND make the appropriate changes on one order. I can describe this process at the exception call if required.

Expected Deliverables/Proposed Implementation Date (if applicable):

Sprint would like the ability to send an LNP order AND make appropriate Directory Listing changes on one order. Sprint proposes an implementation date of no greater than 90 days from the date that the change request is accepted.

Status History

Project Meetings

Hi, I'm ok to close all 20.0 CRs except SCR121305-01 Implement XML Interface for IMA EDI. I would like for this to remain in CLEC test until we have some users actually in production on this. At this time there is no one in production yet. So we can not really say how its going or say we have given it a fair test.

Thanks

Steph

Stephanie Prull EDI Business Analyst Eschelon Telecom, INC Voice - 612-436-6058 Fax - 612-436-6158 Email - saprull@eschelon.com Web - www.eschelon.com

11/15/06 Systems CMP Meeting

Mark Coyne-Qwest stated that this CR deployed on October 16, 2006 with the IMA 20.0 release and asked if this CR could be closed. Bonnie Johnson-Eschelon stated that she would like to check with Steph Prull (Eschelon) before closing this CR. She said that she would send an e-mail to the CMP CR mailbox if the CR could be closed.

10/19/06 Systems CMP Meeting

Susan Lorence-Qwest stated that this CR deployed on October 16, 2006 with the IMA 20.0 release and will remain in CLEC Test.

9/20/06 Systems CMP Meeting

Mark Coyne-Qwest stated that this CR will deploy in the IMA 20.0 release on 10/16/06.

7/19/06 Systems CMP Meeting

Mark Coyne-Qwest asked if there were any questions or comments on any of the open CRs. Jeff Sonnier-Sprint asked which Release SCR010705-01(Directory Listing Changes in Conjunction With LNP) was Packaged for.

Peggy Esquibel Reed-Qwest stated that this CR is Packaged for the IMA 20.0 Release.

Mark Coyne-Qwest then noted that the IMA CRs in this attachment could be included in the IMA 21.0 prioritization effort.

5/17/06 Systems CMP Meeting

IMA and SATE 20.0 Release - Packaging and Commitment Jill Martain - Qwest reviewed the IMA Release 20.0 Packaging and Commitment documents. She said that Item #2 – SCR021904-02 Suppression of Jeopardy Status Updates will be withdrawn. Jill said that the following CRs will be included in the IMA 20.0 Release scheduled in October: SCR010705-01 - Directory Listing Changes in Conjunction with LNP SCR042704-01 - FBDL PON Field SCR102505-02 - Edits for the LSR Delivery Address Activity (DACT) SCR032202-1 - Download capability for all applications of the post order status tool

5/18/05 Systems CMP Meeting

Jill Martain - Qwest stated that the LOE for this request is 4700 to 7840 hours and that this action item will be closed.

3/11/05 Response from Sprint

Lynn, I have checked with our folks and today via the GUI, we limit the characters on the PON to 11 A/N. However, we are in the process of converting to EDI and I spoke with our developer and we could very easily create a PON generator for Qwest only that would limit the PON to 11 character positions. Currently we have it set up for 16 (all numeric) with the other ILECs (VZ East and SBC). We are in the process of bringing the rest of the ILECs on board (BS, Qwest, and VZ West). This is supposed to occur within the next couple of months (way before the implementation of this Scope Change Request), so I think we will be okay. Thanks for the meeting yesterday, as it was very informative. Jeff Sonnier CLEC CMP for Qwest and SBC 6330 Sprint Parkway Overland Park, KS 66251 MS: KSOPHA0206 PH: 913-762-1290 FX: 913-762-0129

3/10/05 Adhoc Meeting

Attendees: Carol Debrough - Wiser, Roslyn Davis - MCI, Tom Larson - Cox Communications, Kim Isaacs - Eschelon, Chris Terrell - AT&T, Steph Prull - Eschelon, Liz Balvin - Covad, Amanda Silva - VCI Company, Jeff Sonnier - Sprint, Russ Urevig - Qwest, Chuck Anderson - Qwest, Jennifer Fisher - Qwest

Lynn Stecklein - Qwest stated that the purpose of this call was to discuss SCR010705-01 Directory Listing changes in conjunction with LNP submitted by Sprint. Lynn stated that this CR is currently in an Evaluation status and that during our analysis several questions were raised. Lynn said that we scheduled this meeting to get input and feedback from the CLEC Community regarding these questions.

Russ Urevig- Qwest stated that we wanted to have an opportunity to talk with everyone about some considerations or inherit issues related to moving forward with this candidate. We are currently looking at different ways of accommodating this request and we are still researching this candidate, so there may be other issues we uncover. So this is a point in time during our brainstorming where we see some inherit issues because of Qwest legacy systems, and how Qwest handles listings in a different manner than other RBOCs. We just wanted to make sure there is a clear understanding of the issues and inherit rules that would apply to the LNP request when listing changes or the DL form is present. These conditions can NOT be changed and will be enforced. Russ stated that the request is asking for LNP with ACT = V to allow the DL form to be present to allow changes to current listings. Russ said that he wanted to make sure it is clear that when this occurs that the listing changes will still be migrated to a FBDL listing. All listings edits current or implements for FDBL in any release will apply to this type of request as well. An example of this is, Release17.0 the IMA edits for FBDL have been enhanced to ensure order accuracy. This means that when a request for LNP ACT = V and the DL form is present, the DL form will be subject to all the current BPL edits for the FBDL application. The accuracy of the request for LNP with listing changes must be equal to that for the FBDL listing application.

Russ stated that some of the concerns or inherit issues we wanted to share with you are:

1. In making the request for LNP you would log in as an LNP CCNA, but because the DL form will mirror the requirements of the FBDL edits, the user would be required to provide the FBDL CCNA and the CC value on the DL form associated to this request. These fields would not flow forward and be populated from the LSR CCNA information. This FBDL CCNA and CC value is edited for accuracy to avoid fallout in processing (which would result in a DSRED Notice and CLEC possibly require CLEC to submit new FBDL LSR.

2. PON number length becomes an issue on the LNP request, the rules associated to the FBDL request would apply. They are:

Product 14: Must be a minimum of 4 characters and a maximum of 11 characters. The LSR for LNP rule is 16 The last character must be numeric. Only numeric characters 0 through 9 and alpha characters A through Z in upper case allowed. The FBDL request inherits the PON of the request under the FBDL CCNA account.

3. Duplicate PON rules will still apply for the LNP and FBDL requests.

(CCNA+PON with last 2 years) 4. This FBDL CCNA and CC value is edited for accuracy to avoid fallout in processing; this which would result in a DSRED Notice after the request for the LNP is complete. This could result in a CLEC to submit new FBDL LSR after the DSRED notice. Because the LNP request has already completed the LSR can not be modified.

5. An additional point with the LNP request and the DL request which would be handled through the FBDL processes would are handled in sequential order processing. This means that currently the LNP request must complete before you are allowed to submit a request for the FBDL request. The legacy systems will still require this action, so the LNP request will need to complete first, then Qwest will generate the FDBL request to be processed. Russ stated again that when a DESRED is delivered on the FBDL portion of the request, you may be required to resubmit the listing request through the FBDL process.

Russ said that also the FBDL NOTICES - DSRED will remain the same and the LNP NOTICE - LR responses FOC, COMPLETION, JEP, etc. will remain the same.

Russ said that just as an FYI - things that don't change are time intervals on handling the request, first the LNP request completes then the listing request which is converting to FBDL internally will kick off. No improvement on timing of work.

Russ stated that the main issue was the intervals for processing the request would not change, there is NO parallel processing done. There is is s restriction on the PON length right now. There would be additional training required for there provisioners to understand the FDBL language for inputting the listing request.

Jeff Sonnier - Sprint stated that he did not think that the PON length will be a problem and said that he would contact his developers.

2/16/05 Systems CMP Meeting

Jill Martain - Qwest stated that this CR was presented as a walk-on in the January CMP Systems Meeting. Jill said that Qwest is still evaluating to determine what options exist and will provide a readout in the March CMP Systems Meeting. Jeff Sonnier - Sprint asked about the last paragraph in the draft response dated February 9, 2005 posted in the CR. Lynn Stecklein - Qwest stated that the draft response is a standard response. She said that in the March meeting, Qwest will provide the final response and CMP participants will be able to comment at that time.

1/19/05 Systems CMP Meeting

Jeff Sonnier/Sprint stated that they are requesting the capability to send a Local Number Portability order and make changes to the Directory Listing on one order. Jeff said that currently Qwest requires two orders to accommodate this request. Jeff stated that Qwest is the only ILEC that requires two orders. Dianne Friend/Time Warner stated that they support this request. Sharon Van Meter/AT&T said they also support this CR. Jen Arnold/TDS Metrocom said that they support this request as well. Jeff Sonnier/Sprint stated that the clarification meeting was held with Qwest and that there were no outstanding questions associated with this request. Jeff said to contact him with any questions that may come up. Jill Martain/Qwest stated that the status of this CR will change to Presented.

1/14/05 Clarification Meeting

Attendees:

Jeff Sonnier - Sprint, Randy Owen - Qwest, Russ Urevig - Qwest, Lee Gomez - Qwest, Jim Recker - Qwest, Lynn Stecklein - Qwest

Review Description of CR

Sprint would like the capability to send a Local Number Portability order and make changes to the Directory Listing (all on one order or one transaction). Currently, Qwest requires two orders to accommodate this type of request. The first order allows the porting of the number and either retains the exact same directory listing (ACT = Z) or deletes it entirely (ACT = V). If changes to the Directory Listing are required, a second order is initiated to make the appropriate changes to the directory listing.

Discussion:

Jeff Sonnier - Sprint stated that other ILECs allow them to port the number and make the appropriate changes on 1 order. Russ Urevig - Qwest asked if it made a difference on full or partial conversions. Jeff Sonnier said no

Products and Interface impacted

IMA Common and LNP

Establish Action Plan

Sprint will present this CR in the January CMP Systems Meeting

CenturyLink Response

May 18, 2005

RE: SCR010705-01 Directory Listing Changes in conjunction with LNP

Qwest has reviewed the information submitted as part of Change Request SCR010705-01. Based upon the scope of this CR as agreed to in the Clarification Meeting (held January 14, 2005) Qwest is able to provide an estimated Level of Effort (LOE) of 4700 to 7840 hours for this IMA Change Request.

At the next Monthly Systems CMP Meeting, CMP participants will be given the opportunity to comment on this Change Request and provide additional clarifications. Any clarifications and/or modifications identified at that time will be incorporated into Qwest’s further evaluation of this Change Request. Upon obtaining consensus from CMP participants as to the appropriate direction for Qwest to take on this Change Request, Qwest will review release schedules and development timetables in an effort to evaluate options for potential scheduling of Change Request SCR10705-01

Sincerely, Jeff Thompson Qwest, Information Technologies

DRAFT RESPONSE

February 9, 2005

RE: SCR010705-01 Directory Listing Changes in conjunction with LNP

Qwest has reviewed the information submitted as part of Change Request SCR010705-01. Based upon research that has been conducted following the Clarification Meeting (held January 14, 2005, Qwest is still evaluating the change request. Qwest will provide an updated response at the March Systems CMP Meeting.

At the March Monthly Systems CMP Meeting, CMP participants will be given the opportunity to comment on this Change Request and provide additional clarifications. Qwest is interested in the experiences of the CMP community as relates to this issue. Qwest will incorporate any feedback received at the next Monthly Systems CMP Meeting into further evaluation of this Change Request.

Sincerely, Qwest