Wholesale: Products & Services

Archived System CR SCR111402-01 Detail

PON (All forms): Prohibit special characters (anything that is not a letter or a number, excluding a hyphen. A hyphen is allowed in the PON). Entries will continue to be stored in upper case.

CKR (DRS, LS, LSNP, PS, RFR) - Prohibit Virgule (/) as a valid character.

NAME (EU, RPL (10a, 44a)) - Prohibit Virgule (/) as a valid character.

TC NAME primary (EU, CRS, LS, LSNP, NP, PS, RS) - Prohibit Virgule (/) as a valid character.

TC NAME secondary (EU, CRS, LS, LSNP, NP, PS, RS) - Prohibit Virgule (/) as a valid character.

BILLNM (LSR, RPL, EU) - Prohibit Virgule (/) as a valid character.

SBILLNM (LSR, RPL, EU) - Prohibit Virgule (/) as a valid character.

AUTHNM (LSR) - Prohibit Virgule (/) as a valid character.

INIT (LSR) - Prohibit Virgule (/) as a valid character.

INIT (LSR) - Prohibit Comma (,) as a valid character.

IMPCON (LSR) - Prohibit Virgule (/) as a valid character.

ALT IMPCON (LSR) - Prohibit Virgule (/) as a valid character.

DSGCON (LSR) - Prohibit Virgule (/) as a valid character.

Status History

Project Meetings

-- August 18, 2004 Systems CMP Meeting Discussion: Connie Winston/Qwest stated that this CR was implemented in 15.0 and would remain in CLEC Test.

- July 22, 2004 Systems CMP Meeting Discussion: Connie Winston/Qwest stated that this was implemented in 15.0 and would remain in CLEC Test.

- June 17, 2004 Systems CMP Meeting Discussion: Connie Winston/Qwest stated this CR will remain in CLEC Test for another month per the request of Donna Osborne-Miller/AT&T.

May 20, 2004 Systems CMP Meeting Discussion: Connie Winston/Qwest stated that the majority of the CRs in Attachment G were deployed in 15.0. Connie said that we usually like to wait for the 1st EDI customer to certify a new release. Bonnie Johnson/Eschelon said that when the submitting CLEC of a CR has not moved to the release and another CLEC performs the test, they may not understand the submitting CLECs intent or their system may be different. Bonnie said that she initiated a CR to establish a new status and Qwest voted no. 6/1/04 - Revision to Minutes from Eschelon. Bonnie said that we need to define in the CMP Document, a new status that fits the situation when a CR has not been tested in a release. Randy Owen/Qwest said that we might look at something between CLEC Test and Completed. Cheryl Peterson/AT&T said that we might use CLEC Test One and Two. Bonnie Johnson/Eschelon said that we could use ‘Pending Test’ or ‘CLEC Hold’. Connie Winston/Qwest stated that we would create an action item to research the possibility of establishing a new Status Code.

This CR will remain in CLEC Test

- April 22, 2004 Systems CMP Meeting Discussion: Connie Winston/Qwest stated that this CR just deployed with the IMA 15.0 Release and will remain open for another month. There were no questions or comments. This CR remains in CLEC Test.

- March 18, 2004 Systems CMP Meeting Discussion: Connie Winston/Qwest stated that this CR is deploying on April 19, 2004, in the IMA 15.0 Release. There were no questions or comments.

February 19, 2004 Systems CMP Meeting Discussion Excerpt (Attachments H & J): Judy Schultz/Qwest stated that she wanted to provide an update to the funding approval process that was discussed in the January CMP Systems Meeting. Judy referred everyone to Attachment J in the Distribution Package. She stated that all CRs are being re-evaluated and must be approved. Judy said that CRs could not be scheduled without approval. Judy stated that the CRs with an impact to the IMA interface would follow the existing prioritization process. Judy noted that the funding for IMA 15.0 and IMA 16.0 has been approved, as well as funding to begin work on IMA 17.0.

- MEETING MINUTES-February 17, 2004 Hi-Level Walk Through of IMA 15.0 Committed CR's

Attendees: Anne Robberson-Process Analyst (Qwest), Curt Anderson- IT Systems Analyst (Qwest), Diane Burt-Systems Analyst (AT&T), Donna Osborne-Miller- Carrier Relations Manager (AT&T), Dusti Bastian-Process Analyst (Qwest), Ellen McArthur-Process Analyst (Qwest), Hank Martinez-IT Systems Analyst (Qwest), James McCluskey- ILEC Manager (Accenture), John Daugherty-Product Management (AT&T), John Gallegos-IT Manager (Qwest), Kathy Miller-Process Manager (Qwest), Kim Isaacs-ILEC Relations Process Analyst (Eschelon), Kyle Kirves-IT Analyst (Qwest), Linda Miles-Process Manager (Qwest), Lori Langston-Process Manager (Qwest), Marie Acceno-Systems Analyst (AT&T), Nancy Denny-IT Analyst (Qwest), Nicole James-IT Analyst (Qwest), Pat Bratetic-Process Manager (Qwest), Phyllis Burt-Systems Analyst (AT&T), Randy Owen-IT Manager (Qwest), Shon Higer-Process Analyst (Qwest), Shonna Pasionek-IT Analyst (Qwest), Stephanie Prull-EDI Business Analyst (Eschelon), Susie Wells-Product/Process Analyst (Qwest) Meeting Facilitator: Nancy Denny (Qwest)

Purpose: High-level walk-through of the CRs that are committed in the IMA 15.0 Release.

Supporting Documents: Qwest Notification: SYST.02.13.04.F.01366.IMAEDI15.0Cand&DocWkth Documentation containing 15.0 Candidate Summaries: February 17, 2004, attached to notification CRs can be found in the Qwest Wholesale Change Request Interactive Report located at: http://www.qwest.com/wholesale/cmp/changerequest.html

Functional Overview: This enhancement is applying Business rules for invalid special characters on LSR requests to increase Flow Through activity. PON (All forms): Prohibit special characters (anything that is not a letter or a number, excluding a hyphen. A hyphen is allowed in the PON). Entries will not be stored in uppercase as previously indicated in the SCR. CKR (DRS, LS, LSNP, PS, RFR) - Prohibit Virgule (/) as a valid character. NAME (EU, RPL (10a, 44a)) - Prohibit Virgule (/) as a valid character. TC NAME primary (EU, CRS, LS, LSNP, NP, PS, RS) - Prohibit Virgule (/) as a valid character. TC NAME secondary (EU, CRS, LS, LSNP, NP, PS, RS) - Prohibit Virgule (/) as a valid character. BILLNM (LSR, RPL, EU) - Prohibit Virgule (/) as a valid character. SBILLNM (LSR, RPL, EU) - Prohibit Virgule (/) as a valid character. AUTHNM (LSR) - Prohibit Virgule (/) as a valid character. INIT (LSR) - Prohibit Virgule (/) as a valid character. INIT (LSR) - Prohibit Virgule (/) and Comma (,) as a valid character. IMPCON (LSR) - Prohibit Virgule (/) as a valid character. ALT IMPCON (LSR) - Prohibit Virgule (/) as a valid character. DSGCON (LSR) - Prohibit Virgule (/) as a valid character.

Form Impacts: CRS, EU, DRS, LS, LSNP, LSR, NP, PS, RFR, RPL, RS Products: All products

Activities: All applicable activity types

Meeting Discussion: Ellen McArthur provided the overview based on the document circulated with the meeting agenda.

There were no questions.

-- August 21, 2003 Systems CMP Meeting Discussion: Connie Winston/Qwest stated that Qwest is moderately passionate about this CR. Liz Balvin/MCI asked what was currently happening when these characters were used. Connie Winston/Qwest stated that they were causing rejects, especially when a virgule is used.

- March 20, 2003 Systems CMP Meeting Discussion Regarding IMA 14.0 Prioritization: Kit Thomte/Qwest stated that Jo Netherton/Qwest attended the last meeting and talked about how important this was. Connie Winston/Qwest stated that virgules should not ever be used. She stated that Qwest was supportive of this CR.

February 20, 2003 Systems CMP Meeting Discussion: Jo Netherton/Qwest asked the CLECs to review the CR and consider it for the 14.0 vote as it will help with flow through. Jill Martain/Qwest stated that if any CLECs consider to use the new rules, it would help with LSR accuracy. There were no questions or comments.

January 16, 2003 Systems CMP Meeting Discussion: Shon Higer/Qwest stated that a hyphen in the PON is not a problem to allow and will not be restricted. Shon stated that a period in the PON does cause problems in the Central region and with the implementation of this CR, a period in the PON will not be allowed at all. Shon stated that the investigation is continueing to determine if other special characters are needed to be included in this effort. Bonnie Johnson/Eschelon asked if this is an exhaustive list. Connie Winston/Qwest stated that Qwest is still investigating if others need to be included. Shon Higer/Qwest stated that currently alpha/numeric characters and the hyphen are allowed in the PON. Kathleen Holtz/USLink asked if the hyphen can be used now. Shon Higer/Qwest stated that yes it is currently allowed and will continue to allow the hyphen in the PON.

December 19, 2002 Systems CMP Meeting Discussion: Shon Higer/Qwest reviewed the description of the CR. Jonathan Spangler/AT&T asked if Qwest wanted to have an upfront edit to reject based on these special characters. Shon Higer/Qwest said that it would be to identify and reject special characters in certain fields. Bonnie Johnson/Eschelon said that she wanted to make sure there is no work around necessary. Liz Balvin/WorldCom said maybe Qwest should take an action item to evaluate some CSRs to see if there are any other special characters that may need to be added. Jonathan Spangler/AT&T said we were just commenting on a problem when a Qwest system incorporates special characters on CSRs and you have to put them on the LSR, they get rejected. You are adding an additional set of special characters. Shon Higer/Qwest said that the only special character Qwest was addressing was the virgule and that he would take an action item to do more follow up. Bonnie Johnson/Eschelon said that would be great. Connie Winston/Qwest stated the only other one is INIT that does not have a comma. Shon Higer/Qwest stated that the other exception is the PON. Connie Winston/Qwest said that yes, that was the very top one. Jonathan Spangler/AT&T said that the CLEC Community would have to see additional support of this CR to consider it for prioritization. If there weren’t any special characters in any of the CSRs out there, then we would support this. Mike Zulevic/Covad stated that Covad is very concerned about any new edits because of difficulty in the past when new edits have been introduced because of the rejects upfront. Therefore, I am concerned about our system being compatible. Jonathan Spangler/AT&T said that the intent was to improve flow through. The problem is the CLEC would not be able to get the LSR to you. We will have to put it into manual to get it to you because we pull the information from the CSR. IMA now rejects these special characters. Therefore, we then have to submit this to Qwest as a manual order. Lynn Notarianni/Qwest said that when we go back and do research, I see a potentially different issue with the &, in these cases there may be a situation where we are very clear with the rules, always put this here, instead of not getting to the right information. Therefore, we can look into an alternative on what could make sense. Connie Winston/Qwest said that I think you’d like the edit applied only to the CLEC data instead of the CSR data. Jonathan Spangler/AT&T said that the only caveat is that you are rejecting what Qwest is sending us. Judy Schultz/Qwest suggested Qwest take this offline as we had this discussion earlier. Bonnie Johnson/Eschelon stated that the edits are logical in theory, there are processes out there for when these edits are imposed. When talking about implementing a CR with edits that you are certain that you don’t have manual processes that are impacted by these edits. Jonathan Spangler/AT&T asked if this CR is proposing to prohibit everything but letters, including hyphens in the PON. Shon Higer/Qwest said that is correct. Kit Thomte/Qwest said that this would remain pending prioritization. Jonathan Spangler/AT&T said that the impression of the PON is whatever format we choose. We were under the impression that whatever was on the PON was acceptable. Ian Coleman/Allegiance stated that the only thing we are concerned about is the PON and the hyphen. Judy Schultz/Qwest stated that the CR reads that anything that is not a letter or number needs to be updated. Judy Schultz/Qwest asked if you just say a hyphen would still be allowed. Shon Higer/Qwest said not as an edit. Bonnie Johnson/Eschelon asked why because we use the hyphen quite regularly. Kit Thomte/Qwest said that will remain Pending Prioritization, there are some confused looks so we’ll have to do some more research. Connie Winston/Qwest said if this happens to make the release, we will work with the CLECs to get a definition that works, but if it doesn’t make it, we will take it back and work on the definition internally. Terry Bahner/AT&T asked if is this a comprehensive list, this is exactly what you are looking for. Shon Higer/Qwest said yes.

11/14/02 Clarification Meeting

Introduction of Attendees: Shonna Pasionek-Qwest, Ray Wilson-Qwest, Shon Higer-Qwest, Lynn Stecklein-Qwest, Peggy Esquibel-Reed-Qwest

Review Requested (Description of Change) Call participants reviewed CR Description: Reject LSRs when special characters are input in specific fields. PON (All forms): Prohibit special characters (anything that is not a letter or a number). Entries will continue to be stored in upper case. CKR (DRS, LS, LSNP, PS, RFR) - Prohibit Virgule (/) as a valid character. NAME (EU, RPL (10a, 44a)) - Prohibit Virgule (/) as a valid character. TC NAME primary (EU, CRS, LS, LSNP, NP, PS, RS) - Prohibit Virgule (/) as a valid character. TC NAME secondary (EU, CRS, LS, LSNP, NP, PS, RS) - Prohibit Virgule (/) as a valid character. BILLNM (LSR, RPL, EU) - Prohibit Virgule (/) as a valid character. SBILLNM (LSR, RPL, EU) - Prohibit Virgule (/) as a valid character. AUTHNM (LSR) - Prohibit Virgule (/) as a valid character. INIT (LSR) - Prohibit Virgule (/) as a valid character. INIT (LSR) - Prohibit Comma (,) as a valid character. IMPCON (LSR) - Prohibit Virgule (/) as a valid character. ALT IMPCON (LSR) - Prohibit Virgule (/) as a valid character. DSGCON (LSR) - Prohibit Virgule (/) as a valid character.

Confirm Interfaces and Products Impacted: IMA Common for All Products

Confirm Right Personnel Involved - All appropriate personnel participated in the clarification meeting.

Establish Action Plan - Shon Higer/Qwest to present this change request in the December Systems CMP meeting.

CenturyLink Response

December 11, 2002

RE: SCR111402-01 Reject Invalid Special Characters.

Qwest has reviewed the information submitted as part of Change Request (SCR111402-01). Based upon the scope of this CR as agreed to in the Clarification Meeting (held November 18, 2002) Qwest is able to provide an estimated Level of Effort (LOE) of 950 to 1600 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.

This Change Request is an eligible candidate for the IMA 13.0 prioritization vote.

Sincerely, Qwest