Archived System CR 25381 Detail |
Title: Implement edit to reject requests for conversion from Remote Call Forward for UBL | |||||
CR Number |
Current Status Date |
Level of Effort |
Interface/ Release No. |
Area Impacted |
Products Impacted |
|
|||||
25381 |
Completed 7/18/2002 |
- | 3/10 | IMA | UBL |
Originator: Gallegos, John |
Originator Company Name: Qwest Corporation |
Owner: Winston, Connie |
Director: |
CR PM: Routh, Mark |
Description Of Change |
Implement the edit to automatically reject request in IMA for conversion from a Remote Call Forwarding (also referred to as a Market Expansion Line) to an UBL or UBL with Number Port. This CR is related to the Electronic Flow-through Performance Indicator Definition (PIDs PO2A and B) and the LSR Rejection Notice Interval PID (PO3). Colorado Docket 01I-041T. PID definitions can be found at http://www.nrri.ohio- state.edu/oss/master/perform/perform.htm.
The benefit to CLECs is that errors are caught much earlier in the process and reduces the likelyhood that the CLEC customer will be impacted.
When a CLEC sends in an LSR requesting a conversion from a Remote Call Forwarding to an unbundled loop it is erroring in the Qwest Service Order Processor, which impacts the PO2 measurement. A conversion from an RCF to an Unbundleld Loop is not applicable since there are no facilities on the RCF and the LSR is later rejected. This request will reject the LSR upfront. The CLEC can then submit the LSR for a new loop with portability and use the RCF as the ported number and an LSR for the disconnect order on the RCF account. This applies to Unbundled Loop and Unbundled Loop with number port, REQ TYPE = A and B; ACT=V, Z. A remote Call Forwardiong or Market Expansion Line has the below classes of service, based on the state. The USOC and Class of Service are the same. Only One RCF is billed to an account but it may have multiple paths (or additional lines that use the same TN). The table below defines the States, Service and USOC associated with this CR.
STATES SERVICE USOC AZ, ID-S MT, NM, UT, WY Local RCFVH Toll RCFVT WATS RCFWT Remote Call Forwarding (Res) RCFRH Toll (Res) RCFRT Add'l path RCA CO Local RCFVF Toll RCFVT WATS RCFWT Add'l path RCA IA, MN, NE, ND, SD Local RCFVF Interstate/WATS outside of state RCFVE Intrastate/WATS inside of state RCFVS International/Canada RCFVN Remote Call Forwarding(Res) RCFRF Toll Interstate (Res) RCFRE Toll International (Res) RCFRN Toll Intrastate (Res) RCFRS Add'l path RCA Malheur, OR Toll RCFVT Add’l path RCA ID-N, OR,WA Local RD5 Remote Call Forwarding(Res) RD6 LD-Intrastate RCFVS LD-Interstate RCFVE WATS-Intrastate RCFWS WATS-Interstate RCFWE International/Canada RCFVN Add'l path RCA
|
Status History |
Date | Action | Description |
10/18/2001 | CR Submitted | CR transferred from legacy database to CMP database |
10/18/2001 | Discussed at Monthly CMP Meeting | Presented at Oct CMP meeting, status changed to development |
10/18/2001 | Clarification Meeting Held | Clarified CR at the Monthly CMP meeting. |
10/25/2001 | Qwest Response Issued | Qwest response included with CLEC prioritization request |
10/31/2001 | Release Ranking | Ranking for Release 10.0; 25381 is "Above the Line" |
1/17/2002 | Discussed at Monthly CMP Meeting | CR # 25381 discussed during 10.0 Packaging Presentation |
1/17/2002 | Status Changed | CR # 25381 status updated to 'Packaged' for 10.0 |
3/13/2002 | Status Changed | Status updated from 'Packaged' to 'Development |
3/21/2002 | Discussed at Monthly CMP Meeting | 25381 discussed at March Systems CMP Monthly meeting during IMA Release 10.0 Commitment Discussion (Attachment I) |
6/20/2002 | Discussed at Monthly CMP Meeting | 25381 discussed at June Systems CMP Monthly meeting; please see Systems CMP Distribution Package June CMP -- Attachment N |
6/25/2002 | Status Changed | Status set to CLEC Test |
7/18/2002 | Discussed at Monthly CMP Meeting | 25381 discussed at July Systems CMP Monthly meeting; please see Systems CMP Distribution Package July CMP -- Attachment G |
7/18/2002 | Status Changed | Status updated to Completed |
Project Meetings |
|
CenturyLink Response |
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.
|
Information Current as of 1/11/2021