Wholesale: Products & Services

Archived System CR SCR092601-1 Detail

Status History

Project Meetings

Participants included Denise Martinez, J.J. Bradley, Jerry Mohatt, Beth Foster, Lynn Stecklein. Further discussion and research is necessary within the Process Specialist organization. A follow-up meeting will be scheduled.

=============

10/18/01 October CMP Meeting

During Oct CMP meeting held on 10/18/01 CLECs voted for a jeopardy notice after FOC instead of the nonfatal error after FOC.

=============

11/15/01 - CR discussed in the Nov CMP meeting. Action Item 370 was created - Jill will provide process options by Nov 30.

=============

11/28/01 - Qwest Internal Clarification Meeting

A meeting was held to discuss the following 2 CR's. In attendance Jill Martain, Joan Wells, Todd Mead, Michael Buck, Lynn Stecklein The latest status is Discussed at Systems CMP meeting. There are interim process solutions available for SCR092601-1. Qwest will discuss potential interim process at the December CMP P&P meeting. CR 5582295 should be closed on agreement from CLEC community. SCR092601-1 - Lynn will maintain this CR. It has been prioritized high by the CLECs for 10.0 and will be in development for June Release. We need to maintain this in the systems CMP meeting and report on progress as it progresses through CMP process.

===============

December P&P CMP Meeting 12/12/01

Qwest reviewed the proposed manual process for the Systems CR (SCR092601-1) and explained that this process would apply to all products. AT&T is concerned about the time frame for Qwest to issue a Jeopardy notification to CLECs, specifically for LNP and Broadband. Qwest to take an action to advise what the interval is before this interim process is implemented. The details of the Systems CR will be reviewed in tomorrow's Systems CMP Meeting. Based upon resolution of the timeframes with AT&T, the CLEC participants agreed that Qwest could move forward with the manual process with an effective target date of 2/1/02.

================

12/19/01; Letter received from AT&T

December 19, 2001

Todd Mead CMP Manager Qwest Communications 1801 California Street Denver, Colorado 80202

RE: E-mail titled SCR092601-1 – Time Interval

Dear Todd:

AT&T does not believe the proposed three-day interval to monitor AT&T Broadband’s LNP LSRS for Qwest jeopardy notices satisfies Broadband’s needs nor CR5582295 sent to Qwest June 6th, 2001.

AT&T believes Qwest should not fatal reject nor send a jeopardy notice after the FOC for a product which has a three-day service interval. AT&T understands that Qwest has reduced many circumstances requiring a jeopardy notice by implementing and improving their OSS front-end edits. If there are isolated cases where a jeopardy notice must be sent after the FOC, AT&T expects this notice to be sent no later than four hours after the FOC. This jeopardy notice should be followed up with a call from the Qwest typist who issued the notification.

AT&T Broadband has established internal processes which rely on a reliable FOC. Qwest’s three-day proposal places a burden on AT&T and creates a situation where the end customer resides in both switches causing a degradation of service and a double billing issue.

AT&T cannot agree to go forward with the proposed implementation of SCR092601-1 in February as agreed upon in the December CMP meeting.

Sincerely,

Terry Bahner Supervisor AT&T Local Services Access Management Western Region

Cc: Tim Boykin Sharon Van Meter Donna Osborne-Miller

CenturyLink Response

Qwest draft process documentation for procedures.

Upon Qwest identifying the Fatal or Non-Fatal error condition after a FOC, the Service Delivery Coordinator will:

1. Issue a jeopardy notification to the CLEC via IMA EDI, fax, or email stating the reason for the jeopardy condition and the action necessary to correct the error. The reason will be a C05 for design requests and SX for non-designed requests. The associated jeopardy description will state: Error or Reject Condition Identified After the FOC Was Sent to the CLEC.

2. For the first week, place a courtesy call to the CLECs that are currently receiving a call on the non-fatal error to advise them that a jeopardy notice has been issued.

3. Follow-up the LSR in 4-hours to see if a supplement has been received to correct the error condition. If a supplement has not been received, the service order(s) will be canceled (the LSR remains in a jeopardy status).

4. The LSRs will then be followed up in 30-business days to validate if the jeopardy condition has been satisfied. If the LSR remains in a jeopardy status after 30-days, the LSR will be rejected back to the CLEC.

Once a supplement has been received, the LSR will be placed back into the provisioning process and the jeopardy condition satisfied. The original Due Date may or may not be changed, depending on the error condition and the interval in which the supplement was received.

NOTE: SCR92601-1 has been scheduled for 10.0 to enforce not allowing a Non-Fatal Error Notice after a FOC. This process can be manually implemented prior to 10.0 if the CLECs desire the change in process prior to system enforcement.

Draft Response Update for November 15, 2001 CMP Meeting

In regards to the discussion at the last CMP meeting, Qwest agreed to investigate what would be required to be able to implement the CLEC request to receive a jeopardy notice when a CLEC error is detected after FOC issuance instead of the non-fatal error that is currently sent.

Qwest has reviewed process and system impacts across all products and has determined that:

1. One issue that was not discussed at the last meeting was driving closure to the jeopardy notice. Since Qwest will be issuing a jeopardy notice, the 4-hour requirement for resolution before rejection is removed. A timeline for resolution is still required. Qwest is proposing that if the CLEC jeopardy condition is not resolved within 30 calendar days that the LSR is rejected. 2. Internal system changes are needed; however, the opportunity to move forward with process changes in advance of system changes does exist. Qwest could implement the process change manually, without the system changes that would prevent a non-fatal error message from being sent after the FOC. With this approach, the chance for human error exists, especially when the process change is first implemented. Qwest can monitor the process change for compliance and reinforce it through reports, but the ultimate results are realized when the system changes are made. Therefore, in order to use this approach, CLECs must recognize that Qwest would be using process changes to transition from non-fatal error messages to jeopardy notices. The transition would be complete with the implementation of the necessary system changes.

Based on the above information, Qwest cannot determine an actual implementation date at this time. Because of the proposed process changes mentioned above, this Change Request will also be discussed in the Product and Process Meeting scheduled on December 12, 2001.