Archived System CR 31766 Detail |
| Title: Reject Duplicate LSRs | |||||
| CR Number |
Current Status Date |
Level of Effort |
Interface/ Release No. |
Area Impacted |
Products Impacted |
|
|
|||||
| 31766 |
Completed 4/7/2003 |
1600 - 2400 | 3/12 | All Products | |
| Originator: Higer, Shon |
| Originator Company Name: Qwest Corporation |
| Owner: Winston, Connie |
| Director: |
| CR PM: Stecklein, Lynn |
| Description Of Change |
|
IMA should reject duplicate requests. They are currently accepted and processed as new LSRs.
A duplicate LSR can be described as any LSR requesting the same activity for the same account, telephone number(s), or circuit(s) as another pre-existing LSR from the same CLEC. The intent of this request is to mechanically reject any duplicate LSR before it is accepted in IMA. Currently, duplicate LSRs are identified and rejected manually. The current manual process to identify a duplicate is tedious and time-consuming which causes delays in notifying the CLEC.
Approximately 1,000 duplicate LSRs were measured in the month of December, 2001
Currently, LSRs that are a duplicate of another LSR can qualify for flow through. However, the duplicate should not be eligible for flowthrough. The duplicate will usually fall out for manual handling, most often because a service order associated with the first LSR is already pending.
|
Status History |
| Date | Action | Description |
| 9/28/2001 | CR Submitted | CR transferred from legacy database to CMP database |
| 9/28/2001 | Clarification Meeting Held | Clarified this CR with Shon Higer. |
| 10/18/2001 | Discussed at Monthly CMP Meeting | Presented at Oct CMP meeting, status changed to development |
| 10/18/2001 | Discussed at Monthly CMP Meeting | Qwest is concerned that there is no CR Type that clearly encompasses these CRs. Qwest believes these CRs are most closely aligned with the Regulatory Change CR type. Qwest proposes to address this concern during the next Redesign Working Session. |
| 10/25/2001 | Qwest Response Issued | Qwest response included with CLEC prioritization request |
| 1/31/2002 | Record Update | Change Request description updated to provide additional details regarding the nature of the change |
| 2/21/2002 | Discussed at Monthly CMP Meeting | Eligible for the IMA 11.0 Prioritization. |
| 2/21/2002 | Discussed at Monthly CMP Meeting | 31766 discussed during 'Review of 11.0 Prioritization Eligible CRs' portion of February Systems CMP Monthly meeting; please see Attachment I of February Systems CMP Distribution Package |
| 3/1/2002 | Release Ranking | Ranking for Release 11.0 following the February 2002 Systems CMP Meeting. 31766 ranked number 4 |
| 3/1/2002 | Status Changed | Status updated to 'Prioritized' from 'Presented' |
| 4/1/2002 | Release Ranking | Ranking for SATE following the March 2002 Systems CMP Meeting. 31766 ranked number 15 |
| 6/7/2002 | Status Changed | 31766 status updated to 'Pending Prioritization' based upon outcome of IMA 11.0 Packaging Selection vote |
| 7/18/2002 | Discussed at Monthly CMP Meeting | 31766 discussed at July Systems CMP Monthly meeting; please see Systems CMP Distribution Package July CMP -- Attachment P |
| 7/26/2002 | Status Changed | Status set to Prioritized as a result of the release prioritization for IMA 12.0 |
| 7/26/2002 | Release Ranking | Ranking for Release 12.0 following the July 2002 Systems CMP Meeting. 31766 ranked number 13 (tie) |
| 10/30/2002 | Status Changed | 31766 status updated to 'Packaged' based upon outcome of release 12.0 packaging effort |
| 12/19/2002 | Discussed at Monthly CMP Meeting | 31766 discussed at December Systems CMP Monthly meeting; please see Systems CMP Distribution Package December CMP -- Attachment N |
| 4/7/2003 | Status Changed | Status changed to CLEC Test due to IMA 12.0 deployment |
| 4/17/2003 | Discussed at Monthly CMP Meeting | 31766 discussed A;pril Systems CMP Monthly meeting; please see Systems CMP Distribution Package April CMP |
| 4/30/2003 | Status Changed | Status changed to completed |
Project Meetings |
| 4/17/03 CMP Systems Meeting No Comments. CR changed to Completed Status
|
CenturyLink Response |
|
|
Information Current as of 1/11/2021