Archived System CR SCR092501-2 Detail |
Title: Eliminate multiple LSRs for Moves, Changes and Disconnects of TNs | |||||
CR Number |
Current Status Date |
Level of Effort |
Interface/ Release No. |
Area Impacted |
Products Impacted |
|
|||||
SCR092501-2 |
Completed 7/18/2002 |
- | 3/10 | LSR | UBL |
Originator: Mendoza, Lori |
Originator Company Name: Allegiance |
Owner: Winston, Connie |
Director: |
CR PM: Stecklein, Lynn |
Description Of Change |
On unbundled loop ordering, once an end user has been established with the CLEC, all subsequent order activity for the end user must be on a separate LSR for each TN involved even when all TNs are at the same end user location. This order activity includes Move orders, Change orders, and Disconnect orders. Allegiance wants the ability to put multiple TNs on one LSR without having to supply each separate SBN for each circuit. There is no place to put multiple SBNs on one LSR. There are fields to put multiple TNs and circuit IDs.
This current practice required by Qwest greatly increases the processing time and hard dollar expense to the CLECs to have to submit separate LSRs for multiple TNs. Qwest is the only ILEC that requires separate LSRs for multiple TNs for the same End User at the same location. Allegiance is requesting that Qwest develop the ability to allow CLECs to process multiple TNs on one LSR.
Also, Qwest does not allow for the migration of existing facilities from Qwest and the addition of new facilities for the same end user at the same location to be processed on the same LSR. Allegiance is requesting that Qwest develop the ability to allow the CLECs to be able to do this as well.
|
Status History |
Date | Action | Description |
9/25/2001 | CR Submitted | CR submitted |
10/8/2001 | Clarification Meeting Held | Clarification meeting was held with Allegiance |
10/18/2001 | Discussed at Monthly CMP Meeting | Presented at Oct CMP meeting |
10/25/2001 | Status Changed | Prioritization list sent to all CLECs for IMA 10.0 ranking, status changed to prioritization |
10/30/2001 | Draft Response Issued | Draft response posted to CMP database |
10/31/2001 | Release Ranking | Ranking for Release 10.0 occurred at October, 2001 CMP Meeting. SCR092501-2 ranked 7 |
11/14/2001 | LOE Issued | CR is priority #7. LOE is large to extra large. |
11/14/2001 | Discussed at Monthly CMP Meeting | CR was discussed in the Nov CMP meeting |
1/17/2002 | Discussed at Monthly CMP Meeting | CR # SCR092501-2 discussed during 10.0 Packaging Presentation |
1/17/2002 | Status Changed | CR # SCR092501-2 status updated to 'Packaged' for 10.0 |
3/7/2002 | CLEC Call | CLEC call scheduled 3/12/02 to discuss 10.0 packaging and status |
3/8/2002 | Communicator Issued | CMPR.03.07.02F.01235 Meeting with CLEC Community to discuss status 3/12/02 |
3/13/2002 | Status Changed | Status updated from 'Packaged' to 'Development |
3/13/2002 | Qwest CR Review Meeting | A meeting was held on 3/12/02 with the CLEC Community to provide status and an overall summary of this change request. |
3/21/2002 | Discussed at Monthly CMP Meeting | SCR092501-2 discussed March Systems CMP Monthly meeting; please see Systems CMP Distribution Package March CMP - Attachment G; also discussed during IMA Release 10.0 Commitment discussion (Attachment I) |
4/5/2002 | CLEC Call | Status of CR reviewed |
6/20/2002 | Discussed at Monthly CMP Meeting | SCR092501-2 discussed at June Systems CMP Monthly meeting; please see Systems CMP Distribution Package June CMP -- Attachment N |
6/20/2002 | Discussed at Monthly CMP Meeting | SCR092501-2 discussed at June Systems CMP Monthly meeting; please see Systems CMP Distribution Package July CMP -- Attachment G |
6/25/2002 | Status Changed | Status updated to CLEC Test based upon discussion at June Systems CMP Meeting and IMA 10.0 Deployment on June 17, 2002 |
7/18/2002 | Discussed at Monthly CMP Meeting | SCR092501-2 discussed at July Systems CMP Monthly meeting; please see Systems CMP Distribution Package July CMP -- Attachment G |
7/18/2002 | Status Changed | Status changed to completed |
Project Meetings |
4/5/02 A call was held to discuss the status of this CR and a written overview was provided and reviewed. Attendees - Jonathan Spangler - AT&T, Nancy Conant - Telecordia, Monica Avila - Vartec, Bonnie Johnson - Eschelon, Terry Wicks - Allegiance, Butch Stahlberger - XO Communication, Connie Winston - Qwest, Russ Urevig - Qwest, Lynn Stecklein - Qwest 1. History The Unbundled Loop (UBL) product initial implementation requirements were that a request for disconnects, changes, and moves would require the CLEC to submit a request for each circuit individually. The change request was made to allow these types of activities involving multiple circuits be allow on a single Loop service request (LSR) when the changes being made to the circuits are the same and at the same end user (EU) address. Change Objectives Changes to the IMA (Interconnect Mediated Access) and FTS (Flow Through Services) will allow multiple circuit requests to be processed from one LSR for the same activity and EU. FTS will process up to 10 requests in a mechanized format, greater than 10 requests on an LSR will drop to the SDC to be handled manually. This does NOT restrict the CLEC from requesting more that 10 disconnect, changes and move on a single LSR. IMA entry issues for the CLEC The CLEC submits an LSR for disconnect, change, and moves with the REQTYP = AB only, the ACT field can equal D, C, T, and M. REQTYP = AB and ACT = D (Disconnect) The CLEC will follow the normal entries for the disconnect requests, IMA will allow the entry of additional circuits on the LS form (loop service page). Flow through will handle up to 10 disconnect request, greater than 10 will drop to manual handling for the SDC’s within Qwest. The FOC’s for greater than 10 requests will follow the manual time lines not the mechanized time lines. NO manual indicated will be set by the CLEC, this will be handled through edit coding internally. All disconnect request will be basic disconnects. REQTYP = AB and ACT = C, T, M The CLEC will follow the normal entries for these for these types of requests, editing will be preformed to verify the circuits on the LS page match the EU address. If the address does not match the requested change will not be allowed. The FOC will contain information for all service orders, also loss/completions reports will remain the same. 3/12/02 - A meeting was held with the CLEC Community to provide status and an overall summary of this CR. A written summary will be provided to the CLEC Community so that they can communicate the change internally. A follow-up meeting will be scheduled to discuss any questions.Alignment/Clarification Meeting 9:00 p.m. (MDT) / Monday October 8, 2001 Attendees Terry Wicks- Allegiance Peggy Esquibel Reed, Qwest J J Bradley, Qwest Jerry Mohatt Qwest Lynn Stecklein Qwest Beth Foster Qwest Tracy Gilford Qwest Confirm Interfaces & Products Impacted Interfaces - IMA/EDI Product - UBL Identify/Confirm CLEC’s Expectation Change the current practice to allow the CLECs to submit multiple SBNs on one LSR. 3/12/02 - A meeting was held with the CLEC Community to provide status and an overall summary of this CR. A written summary will be provided to the CLEC Community so that they can communicate the change internally. A follow-up meeting will be scheduled to discuss any questions.
|
CenturyLink Response |
October 30, 2001 DRAFT RESPONSE For Review by the CLEC Community and Discussion at November CMP Meeting Terry Wicks ILEC Relations Manager Allegiance CC: Mark Routh Gerald Mohatt Joseph J. Bradley This letter is in response to your CLEC Change Request Form, SCR92501-2 dated September 25, 2001 - Eliminate Multiple LSRs for Moves, Changes and Disconnects of TNs. Description of Change - On unbundled loop ordering, once an end user has been established with the CLEC, all subsequent order activity for the end user must be on a separate LSR for each TN involved even when all TNs are at the same end user location. This order activity includes Move orders, Change orders, and Disconnect orders. Allegiance wants the ability to put multiple TNs on one LSR without having to supply each separate SBN for each circuit. There is no place to put multiple SBNs on one LSR. There are fields to put multiple TNs and circuit Ids. This current practice required by Qwest greatly increases the processing time and hard dollar expense to the CLECs to have to submit separate LSRs for multiple TNs Qwest is the only ILEC that requires separate LSRs for multiple TNs for the same End User at the same location. Allegiance is requesting that Qwest develop the ability to allow CLECs to process multiple TNs on one LSR. Also, Qwest does not allow for the migration of existing facilities from Qwest and the addition of new facilities for the same end user at the same location to be processed on the same LSR. Allegiance is requesting that Qwest develop the ability to allow the CLECs to be able to do this as well. Qwest Response: The clarification meeting with Allegiance to discuss this Change Request was held on October 8, 2001. From this meeting, the level of effort was determined to be Extra Large. At this time Qwest will not provide the functionality to allow the addition of new facilities at the same time a migration is done. This Change Request is a candidate for IMA Release 10.0. Sincerely, John I. Gallegos Information Technologies Manager
|
Information Current as of 1/11/2021