Archived System CR SCR012203-01 Detail |
Title: PSON sent after the service order is in a ready to be worked status | |||||
CR Number |
Current Status Date |
Level of Effort |
Interface/ Release No. |
Area Impacted |
Products Impacted |
|
|||||
SCR012203-01 |
Withdrawn 12/14/2005 |
3500 - 4000 | 3/ | Ordering | All |
Originator: Johnson, Bonnie |
Originator Company Name: Eschelon |
Owner: Winston, Connie |
Director: |
CR PM: Stecklein, Lynn |
Description Of Change |
CLECs have attempted different approaches to address the problem of mismatches between the order placed by the CLECs on an LSR and the order typed by Qwest on the Qwest service orders. When the Qwest service order is incorrect, customer-affecting problems can result. One approach has been to request a document showing the information on the Qwest service order so that CLECs can compare that information to the LSR to attempt to identify and correct errors before the due date. In other words, CLECS requested the service order detail to identify service order accuracy issues. While CLECs do not believe they should bear the burden of identifying these errors, the alternative of allowing customer-affecting errors on the due date is even worse. Qwest calls the document reflecting the service order detail a Pending Service Order Notification (PSON). CLECs were clear about the need to be addressed when requesting the PSON information. In CR 25497, for example, CLECs said: Providers are requesting a summary of the order by USOC to be included with the FOC so that errors can be identified and corrected before the order completes. Because Qwest said it completed the CR and closed it, CLECs understood that the request had been met. Since then, however, CLECs have learned that Qwest is generating the PSON at the time the Qwest service order is issued. In some cases, Qwest generates the PSON and sends it for review by the CLEC before the Qwest service order is in an RL (released Eastern and Western region) or PD (pending in the Central Region) status. When a service order is sent before it is in an RL or PD status, it may require manual attention by Qwest. As a result, the CLEC will contact Qwest to have corrections made to the service order when the Qwest service order could be in a status that requires manual attention by Qwest. The CLEC spends valuable time and resources to review a Qwest service order that is not in a ready to work status and may request a correction to a service order that may need additional attention by Qwest. This is inconsistent with the request initially made by CLECs to obtain a document that reflects the service order detail “to be included in the FOC so that errors can be identified and contacted before the order completes.” The PSON should be created at a point in time when the information provided is sufficient to allow a meaningful comparison between the LSR and the service order detail. By not disclosing that Qwest is generating the PSON prematurely in at least some cases, Qwest has reserved for itself the argument that the mismatch may not result in an error on the due date while imposing upon its competitors a resource burden that ultimately does not accomplish the purpose expressly stated by the CLECs when requesting the PSON. Giving CLECs a PSON before it has gone through the edit and assignment process is not logical. Given the clear statement of their purpose in requesting the PSON, CLECs could not have anticipated that Qwest would provide a document so early in the process that it cannot be used for the very comparison requested by CLECs. Completed CR 25497 providing the PSON, clearly stated the purpose of the receiving the information was to review the service order for accuracy. Generating and sending the information prior to a ready to work status on the Qwest service order does not fulfill the original CR.
|
Status History |
Date | Action | Description |
1/22/2003 | CR Submitted | |
1/22/2003 | CR Acknowledged | |
1/27/2003 | Clarification Meeting Scheduled | |
1/29/2003 | Clarification Meeting Held | |
2/20/2003 | Discussed at Monthly CMP Meeting | Discussed at February Systems CMP Monthly meeting; please see Systems CMP Distribution Package February CMP - Attachment B. |
2/20/2003 | Status Changed | Status changed to presented |
4/7/2003 | Release Ranking | 14.0 Prioritization- Ranked #17 out of 53 |
4/28/2003 | Release Ranking | Rank changed due to Late Adders- Ranked #18 |
4/30/2003 | Discussed at Monthly CMP Meeting | Discussed at April Systems CMP Monthly meeting; please see Systems CMP Distribution Package April CMP |
7/9/2003 | Status Changed | Status changed to pending prioritization with release of I MA 14.0 Packaging. |
9/2/2003 | Release Ranking | 15.0 Prioritization- Ranked #41 out of 57 |
9/18/2003 | Discussed at Monthly CMP Meeting | Discussed at the September Systems CMP Monthly Meeting; please see September Systems CMP Distribution Package - Attachment I |
9/29/2003 | Release Ranking | 15.0 Revised Prioritization, due to Late Adder - Ranked #42 out of 58 |
11/5/2003 | Status Changed | Status changed to pending prioritization |
2/4/2004 | Release Ranking | 16.0 Prioritization- Ranked #37 out of 50 |
2/16/2004 | Status Changed | Status changed to deferred |
3/1/2004 | Release Ranking | IMA 16.0 Revised Prioritization, Late Adder Ranking - #38 out of 51 |
7/5/2005 | Additional Information | QPP will benefit with the implementation of this CR |
11/30/2005 | Status Changed | Status changed to Pending Withdrawal |
12/15/2005 | Status Changed | Status changed to Withdrawn |
Project Meetings |
12/14/05 Systems CMP Meeting Jill Martain/Qwest stated that this CR was in a deferred status. She said that we contacted Eschelon to determine if this CR could be withdrawn. Bonnie Johnson/Eschelon stated that she didn’t believe that they really needed to do anything with the CR, but that if it was causing Qwest issues she was OK to withdraw the CR. This CR is closed.
Lynn, Eschelon does not believe it needs to take any action on this CR and could leave it in a deferred status, however, Eschelon will agree to withdraw the CR at this time and resubmit if necessary. Thanks, Bonnie J. Johnson Director Carrier Relations Eschelon Telecom, Inc. Phone 612 436-6218 Fax 612 436-6318 Cell 612 743-6724 bjjohnson@eschelon.com --Original Message-- From: Stecklein, Lynn [SMTP:Lynn.Stecklein@qwest.com] Sent: Tuesday, November 22, 2005 4:00 PM To: Johnson, Bonnie J. Subject: SCR012203-01 PSON sent after the service is in a ready to be worked status Hi Bonnie, his is a follow up on the attached CR that is currently in a deferred status. In reviewing the notes from February 16, 2004, you requested that we put this CR in a deferred status until PO-20 was well underway. Are you ok with closing this CR or do we need to have additional discussion. Thanks for your help in advance. Lynn Stecklein Qwest Wholesale CRPM 303 382-5770 Lynn.Stecklein@qwest.com << File: SCR012203-01.pdf >> E-mail from Eschelon 2/16/04 Hi Lynn, I would like to put this in a deferred status until PO-20 is well underway. Thanks,
Bonnie J. Johnson Director Carrier Relations Eschelon Telecom, Inc. Phone612 436-6218 Fax612 436-6318 Cell 612 743-6724 bjjohnson@eschelon.com
--Original Message-- From:Stecklein, Lynn [SMTP:Lynn.Stecklein@qwest.com]
Hi Kim,
I am following up on an action item from the January CMP Systems Meeting regarding SCR012203-01 (PSON sent after the service is in a ready to be worked status). In that meeting you said you needed to check with Bonnie Johnson to determine if this CR could be withdrawn. Have you had an opportunity to do that? I have attached a copy of the CR.
Thanks!
9/18/03 CMP Systems Meeting
8/26/03 Response from Bonnie Johnson In the August 21, 2003 CMP Systems Meeting, Qwest stated that we needed to confirm with Bonnie Johnson if she had any further questions on the the PSON cycle SCR012203-01 PSON sent aft SO in ready status. The following response was received from Bonnie Johnson/Eschelon via voice mail: Bonnie stated that she had no further questions regarding this action item. The action item will be closed in the September CMP Systems Meeting.
8/21/03 CMP Systems Meeting Kim Isaacs/Eschelon stated that their interest was moderate. Connie Winston/Qwest stated that this CR applied when provisioning the order. Connie also stated that we will contact Bonnie Johnson/Eschelon to confirm that Bonnie has no further questions regarding the PSON cycle.
4/17/03 CMP Systems Meeting Chris Viveros/Qwest asked if there was a handout on the PSON Flow. Lynn Notarianni/Qwest stated yes and noted that the handout is posted to the web. Lynn reviewed the PSON Flow attachment. PSON Flow High Level Description of the PSON Flow:
The LSR is entered & passes all edits in IMA, Service Order(s) are then created and must pass all Service Order Processor edits, The Service Order data is then made available to IMA to create the PSON.
If Changes are made to the Service Order a new PSON will be created.
Chris Viveros/Qwest stated Eschelon submitted this CR and that there was some confusion or miscommunication between what was being communicated in CMP vs. how they were described the process as working in LTPA. Chris stated that Qwest understood that the CR would be withdrawn but there were some concerns around that due to the need for some additional clarification. Chris also stated that he believed we cleared up that clarification in a meeting last week. He asked if there were any questions and asked Bonnie Johnson (Eschelon) if his assessment was accurate. He also asked Bonnie whether the CR should be closed or do we move forward. Bonnie Johnson/Eschelon said that assessment is correct. Some comments made in long term PID made us ask our service managers some questions; they did not necessarily have to do with quality review but with functionality in the service order processor. We were wondering if the PSON was being sent prematurely. Evidently, the information and reasons to that request that Eschelon provided was not necessarily accurate information. We committed to determine if we want to change the CR to get the PSON sent later in the process or to see if Eschelon can change our internal manual process. We need to make certain that we are looking at the most recent PSON and the timeframe that Qwest communicated to us as to where it would be counted and would not be counted (36 hrs after FOC). As far as the CR we need to determine if the LOE provided was to hold it and issue it at a later interval than it is currently being issued now. We then need to determine if that is what we want to move forward with, or if we want to withdraw it. As for the internal assessment, we currently aren’t able to determine what we want to do. Liz Balvin/MCI said that she read the last statement in the document and asked if that meant that regardless of who initiates the changes and that a correction is made than a second PSON is sent. Chris Viveros/Qwest said that is correct. Liz Balvin/MCI asked if there some way to know that there needed to be a second PSON issued and is there any indication that it is the second PSON. Liz also asked if they have seen what she considers duplicate PSONs. Bonnie Johnson/Eschelon said that they have seen multiple PSONs and that you just never know when it is going to be the final PSON Chris Viveros/Qwest said that there is no way we could know that until the order is completed. The option to supplement is always out there. Bonnie Johnson/Eschelon said that because of this manually intensive process that Eschelon put in place and when it was communicated to us that we might be getting the PSON sooner in the process than is appropriate, that’s what prompted us to ask the question, we have to come to some common ground about where is the cutoff point for Qwest to do quality check to look for these errors on their own. After such point in time when does it become the CLECs issue to determine if it is a performance issue. We still need to discuss it at Eschelon, but I think we’re close to finding that common ground. Chris Viveros/Qwest agreed. Bonnie Johnson/Eschelon stated that the ball is in Eschelon’s court. We can close this action item. Lynn Notarianni/Qwest stated that the Level of Effort needs to be reviewed based on our understanding. Lynn noted that the conclusions is a little different than what is in the CR and what was in the LOE, so we want to go back and look at the LOE. Bonnie Johnson/Eschelon stated that Connie (Winston-Qwest) advised last month that the LOE was based on delaying the PSON. Bonnie noted that Eschelon needs to decide to either go forward with the CR or withdraw it.
2/20/03 CMP Systems Meeting
Bonnie Johnson/ Eschelon presented the Change Request. Connie Winston/Qwest said that Qwest issued the PSON after the SOP edits. Bonnie Johnson/Eschelon said that is not what Eschelon was told. Connie Winston/Qwest said that the SOP sends to many different systems (I.e., IMA, Assignments). Bonnie Johnson/Eschelon said that the reason she referenced all the back end system information in the CR is because of what they have been told. We were told that we were calling to have corrections made prior to it's edits. Connie Winston/Qwest said that Qwest would schedule an internal meeting to determine where the disconnect occurred. Kit Thomte/Qwest said that the status would be changed to presented.
1/29/03 Clarification Meeting
Introduction of Attendees - Bonnie Johnson - Eschelon, Denise Martinez - Qwest, Conrad Evans - Qwest, Lynn Stecklein - Qwest
Review Description of Change Bonnie Johnson/Eschelon summarized request. Eschelon is looking for Qwest to modify the PSON process to meet the original intent. Qwest would need to generate the PSON later and not until the service or is in RL or PD status.
Confirm Areas and Products Impacted This change request is IMA Common and applies to all products that generate a PSON.
Confirm Right Personnel Involved Conrad Evans/Qwest will brief Connie Winston/Qwest on Eschelon's request.
Identify/Confirm CLECs Expectation Bonnie Johnson/Eschelon summarized request. Eschelon is looking for Qwest to modify the PSON process to meet the original intent. Qwest would need to generate the PSON later and not until the serviceorder is in RL or PD status.
Identify any Dependent Systems Change Requests #25497, SCR093002-04
Establish Action Plan Bonnie Johnson/Eschelon will present this CR in the February Systems CMP Meeting. Qwest will schedule an internal meeting to discuss PSON and this change request. Denise Martinez/Qwest will also meet with Jean Novak/Qwest (Service Mgr- Eschelon) and discuss this CR further.
|
CenturyLink Response |
2/11/03 DRAFT RESPONSE RE: SCR12203-01 PSON sent after the service order is in a ready to be worked status Qwest has reviewed the information submitted as part of Change Request (SCR012203-01). Based upon the scope of this CR as agreed to in the Clarification Meeting, Qwest is able to provide an estimated Level of Effort (LOE) of 3500 and 4000 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 14.0 Release. Sincerely, Qwest
|
Information Current as of 1/11/2021