Wholesale: Products & Services

Archived System CR SCR092705-01 Detail

Status History

Project Meetings

Mark Coyne-Qwest stated that this CR was implemented on 11/6/06 and asked if everyone was ok to close. Kim Isaacs-Eschelon stated that this CR could be closed.

11/15/06 Systems CMP Meeting Discussion:

Mark Coyne-Qwest stated that this CR was implemented on 11/6/06 and asked if everyone was ok to close. Kim Isaacs-Eschelon asked that this CR remain open for another month.

-

9/27/06 Ad Hoc Meeting

Attendees: Diana Capelli - AT&T, Steph Prull - Eschelon, Jill Martain - Qwest, Cindy Kalakis - Qwest, Lynn Stecklein - Qwest

Lynn Stecklein - Qwest stated that the purposed of this meeting was to provide an update on SCR092705-01 QORA: Display Completion Notice and Completed Status that is targeted for deployment in November. She referred everyone to the Wholesale Resource Website for the draft document that will be discussed in this meeting. Http://www/qwest.com/wholesale/calendar

Jill Martain - Qwest stated that we have stated in previous meetings that Qwest would continue to look at additional opportunities for adding additional notices. She said that we are looking at adding jeopardy notifications to this request. Jill reviewed Qwest’s proposal.

DRAFT PROPOSAL -

Jeopardy notifications for service requests ordered via an ASR are provided to you via the ASOG Clarification/Notification Request Form (C/NR) or via a phone call, depending on when the jeopardy condition is identified. If a jeopardy condition is identified prior to a FOC, the initial facility jeopardy notification is provided via the C/NR form as an “informational” notification (Clarification/Notification Type (C/NT) = D). Unless otherwise specified below, subsequent jeopardy conditions identified after a FOC are notified via a phone call.

Jeopardy Resolution Responsibilities

Qwest provides a C/NR form associated with jeopardy conditions that are outlined in the Access Service Request (ASR) Jeopardy Data document. (Link italicized text to the download document.) If a jeopardy condition is identified prior to a FOC, the jeopardy information is contained in the remarks of the informational notification. If a jeopardy condition is identified after a FOC and it is one of the jeopardy scenarios that is outlined in the Access Service (ASR) Jeopardy Data document, Qwest provides a C/NR form to advise you of the jeopardy condition.

Jeopardy Data Subsequent due dates for service requests in jeopardy for customer reasons will be established using current processes. If the service request in jeopardy requires a supplemental service request, no further processing will occur until the supplement is received. Supplement service request processing is covered in the Ordering Overview. (Link italicized text to: http://www.qwest.com/wholesale/clecs/ordering.html) and in the Customer Not Ready section of this PCAT (Link italicized text to: Anchor italicized text to: Customer Not Ready Section of this PCAT)

Jeopardy Notice Timeline

If a ASR goes into a jeopardy condition and it is detected: And: Then the following occurs:

Prior to the FOC - The RFS Date is not known - Qwest provides status to the ASR customer via the C/NR form. Within 72 hours of the initial notification advising that the order is delayed for facilities, Qwest sends an FOC or a subsequent C/NR to provide more specific details of the jeopardy condition. Qwest will send an FOC when the RFS Date is known. Prior to the FOC - The RFS Date is known - Qwest sends the FOC to advise you of the due date that Qwest can meet. Post FOC - Once the Qwest Wholesale Service Delivery center is advised of the condition (if the RFS Date is not known - Qwest provides a C/NR form to advise you of the status on the delayed order. Once the RFS Date is known, a subsequent C/NR form is submitted advising you of the new due date. Post FOC - Once the Qwest Wholesale Service Delivery center is advised of the condition (if the RFS Date is known) - Qwest submits a C/NR form to provide status on the delayed order and advises you of the DD Qwest can meet.

Access Service Request (ASR) Jeopardy Data

Designed

Jeopardy Data (Customer/Notification Request Form (C/NR)) - ASR

Note: if the initial jeopardy condition is identified prior to a FOC, the RCCODE information will be provided in the Remarks section of the informational notice.

C/NR RCCODE - Responsible Party - Is the Due Date in jeopardy? - Jeopardy Notice Description - User Friendly Jeopardy Description - Responsibilities 1A - Qwest - Engineering - Yes - Interoffice Facility Shortage - Qwest Engineering interoffice facility is not available or is defective. - Qwest will look for a possible solution. 1D - Qwest - Engineering - Yes - No Loop Available - Qwest Engineering local facility is not available or is defective.- Qwest will look for a possible solution. 1Q - Qwest - Yes - Assignment Problem - Qwest Engineering interoffice facility is not available or is defective. - Qwest will look for a possible solution.

Steph Prull - Eschelon said that this proposal should work.

Jill Martain - Qwest stated that this proposal will eliminate the phones call that are received today.

Steph Prull - Eschelon asked if this will replace the e-mails that are sent today.

Jill Martain - Qwest stated that e-mails are not sent today.

Cindy Kalakis - Qwest said that with invalid ASR conditions e-mails are sent.

Jill Martain Qwest stated that this proposal is not for the end to end portion that was initially requested. She said that the PCAT will be out for review and will be a 21 day notification.

Steph Prull - Eschelon asked if this had anything to do with CNR.

Cindy Kalakis - Qwest said that this is the same for the CNR and Completion notices.

Jill Martain - Qwest said that the CR also includes completion notices, invalid ASR, CNR, and initial jeopardy notices.

Steph Prull - Eschelon stated that she would follow up with Kim Isaacs (Eschelon).

Jill Martain - Qwest said that this CR is targeted for deployment on N

7/19/06 Systems CMP Meeting

Cindy Kalakis-Qwest stated that Qwest is implementing the C/NR Form in order to provide completion status related to SCR092705-011-Comp Status. She said that when this form is created by Qwest on ASRs issued through the QORA GUI, it will be added to the request as an additional form (like the Confirmation Form is today) Cindy said that the GUI will include a new column in the Submitted Screen called "C/NR Status", and the title of the current "Status" column will change to "ASR Status." Cindy said that the GUI documentation when distributed for this release would include information related to these changes. Mark Coyne-asked if there were any objection in closing this action item. There were no objections.

Mark Coyne-Qwest asked if there were any objections in closing this action item. There were no objections.

5/17/06 Systems CMP Meeting

Jill Martain - Qwest stated that this CR will include Invalid ASR, Completion and CNR notices. Kim Isaacs - Eschelon asked when this CR is scheduled to deploy. Jill Martain - Qwest stated that this CR is targeted for November 2006.

2/15/06 Systems CMP Meeting

Jill Martain-Qwest stated the Qwest will implement the functionality for all notices. She said that the LOE is 1200 to 1300 hours and that the targeted implementation date is November 4, 2006. Jill said that the Completion Notice will be deployed in the November release. She said that Qwest is reviewing the other processes associated with the other notices, and if Qwest is able to change those processes to start utilizing the functionality installed with this CR that those will be communicated via Level 3 Process Notices. Kim Isaacs and Bonnie Johnson-Eschelon thanked Qwest. Bob Eggert-SBC asked if the November Release was ASOG 32 or ASOG 33. Jill Martain-Qwest said ASOG 33.

1/18/06 Systems CMP Meeting

Jill Martain - Qwest stated that we have received the Vendor costs and are now looking at this CR from a cost perspective. She said that we are getting closer to an answer and hope to have a response in February as to whether or not we can do this. Jill asked Kim Isaacs (Eschelon) if she would be willing to revise this CR is necessary. Kim Isaacs - Eschelon said that she would and to let her know.

12/14/05 Systems CMP Meeting

Jill Martain/Qwest stated that we are evaluating this CR to determine if additional notices could be added to this request. She said that we will provide an updated status in the January CMP Meeting.

11/16/05 Systems CMP Meeting

Jill Martain/Qwest stated that we are having internal discussions to determine if the additional statuses that Eschelon requested can be added to this CR. Jill said that this CR will remain in Evaluation status.

10/19/05 Systems CMP Meeting

Kim Isaacs/Eschelon said that currently QORA does not provide a completed status or a completion notice. She said that the last status that QORA displays is Confirmed at which point the confirmation notice can be retrieved and viewed by the CLEC. Kim said that if the CLEC needs to verify when and if an ASR has completed, there is no way in QORA to retrieve this information. She said that the CLEC must call Qwest to determine the final status of the ASR. Kim said that this practice is manual, cumbersome and does not provide the CLEC with a lasting record of when the ASR completed. Kim said that Eschelon is requesting that QORA provide a Completed status and a completion notice, which can be retrieved by the CLEC in QORA. Liz Balvin/Covad asked how one would know when the order is completed. Kim Isaacs/Eschelon said that you have to call to determine if the order was completed on the due date. Liz Balvin/Covad asked if this was for QORA and EXACT. Jill Martain/Qwest said that we would have to look at the functionality as to where it would best be implemented. Dianne Friend/Time Warner asked if this was for QORA or NDM. Jill Martain/Qwest said that we are looking at functionality across the board. Bob Eggert/SBC asked if we could add clarification that the completion notice is a manual process. He said that other ILECs send clarification via the GUI. Jill Martain/Qwest asked if this was similar to the error notice on the LSR for pre-foc. Bob Eggert/SBC said that it could be pre or post. He stated that Qwest could see an error in a field and he would get a phone call saying that it is wrong. Jill Martain/Qwest stated that SBC could partner with Eschelon to get that request added to this CR or SBC could issue a new CR. Kim Isaacs/Eschelon stated that in QORA you can review a reject or error status only on BPL. She said that if the error is found by the Center on the back side it will stay in confirmed status and Qwest will call to have a SUPP issued Bonnie Johnson/Eschelon asked if Qwest was looking at adding this to QORA. Jill Martain/Qwest stated that we are looking at several items for QORA. She said that we can go back and ask that question. Bonnie Johnson/Eschelon said that it might be easier and beneficial for Qwest to do all (Comments to minutes received from Eschelon 10/27/05) the statuses for the ASR. Jill Martain/Qwest stated that we will go back and take a look at ASR notifications. Bob Eggert/SBC asked if Qwest could also look at maintaining history. Bonnie Johnson/Eschelon asked Qwest to let them know if they needed to revise their CR.

10/10/05 Clarification Meeting

Attendees: Kim Isaacs - Eschelon, Cindy Kalakis - Qwest, Steve Edwards - Qwest, Cassandra Hunt - Qwest, Curt Anderson - Qwest, Peggy Esquibel-Reed.

Review Description of Change Peggy Esquibel-Reed - Qwest stated that currently QORA does not provide a completed status or a completion notice. She said that the last status that QORA displays is Confirmed at which point the confirmation notice can be retrieved and viewed by the CLEC. Peggy said that if the CLEC needs to verify when and if an ASR has completed, there is no way in QORA to retrieve this information. She said that the CLEC must call Qwest to determine the final status of the ASR. She said that this practice is manual, cumbersome and does not provide the CLEC with a lasting record of when the ASR completed. Eschelon is requesting that QORA provide a Completed status and a completion notice, which can be retrieved by the CLEC in QORA. Peggy said that the completion notice should contain, at the minimum, a completion date, Qwest order number, and the circuit ID.

Discussion Peggy Esquibel-Reed - Qwest confirmed if the Interface was QORA and asked if the Products impacted were specific local ASR Products. Kim Isaacs - Eschelon said that Private Line and LIS Trunks were impacted. Cindy Kalakis - Qwest asked if other products (I.e UDIT, EUDIT, CCSAC, UDF, E911 - PS ALI) were impacted. Kim Isaacs - Eschelon said that this applies to any Product ordered through QORA. She said that Eschelon does not order UDIT. Kim Isaacs - Eschelon said that the Trainer said that Qwest would like to look at enhancements to provide additional status and now has a need for them. Cassandra Hunt - Qwest asked if this applied to the GUI only or if batch was included. Kim Isaacs - Eschelon said that this was for GUI only. Cassandra Hunt - Qwest asked if Eschelon wanted the PON included. Kim Isaacs - Eschelon said yes.

Confirm Products and Interface impaced See above discussion

Establish Action Plan Peggy Esquibel-Reed stated that this CR was eligible for presentation in the October Systems CMP Meeting scheduled on October 19th and that the response will be provided by the November 16th CMP Meeting

CenturyLink Response

February 2, 2006

RE: SCR092705-01 QORA: Display Completion Notice and Completed Status

Qwest has reviewed the information submitted as part of Change Request SCR092705-01. Based upon the scope of this CR as agreed to in the Clarification Meeting and subsequent meetings, Qwest is able to provide an estimated Level of Effort (LOE) of 1200 to 1300 hours for this 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. Qwest will review release schedules and development timetables in an effort to evaluate options for potential scheduling of Change Request SCR092705-01

Sincerely,

Qwest