Open Product/Process CR PC032803-1ES Detail |
Title: Qwest to halt the implementation of CLEC impacting process changes with no notice. | ||||||
CR Number |
Current Status Date |
Area Impacted | Products Impacted | |||
|
||||||
PC032803-1ES |
Denied 5/21/2003 |
Pre Ordering, Ordering, Provisioning | All Products |
Originator: Powers, Lynne |
Originator Company Name: Tel West |
Owner: Schultz, Judy |
Director: |
CR PM: Harlan, Cindy |
Description Of Change |
Qwest should at all times ensure that it provides proper notice and follows procedures before implementing CLEC affecting process changes. CLEC involvement is necessary to ensure that changes which adversely affect the CLEC community are reviewed to determine options for implementation that are best for all parties and are not unilaterally in favor of minimizing impact to Qwest. In some cases, Qwest states that the change in process or procedure is not actually a change because Qwest has started to follow previously documented procedures. Qwest will say, for example, that it is just tightening up processes. The affect on CLECs, however, is that of a process change. One day, orders are processed just fine, and the next they are not. The tightening up in allegedly existing procedures has changed the process for CLECs. Even assuming the alleged existing process appears in the Qwest documentation, the documentation is meaningless if the Qwest business is not following that documented process. When Qwest begins to follow it, it needs to let CLECs know how and when it is changing its practices and what the resulting impact to CLECs will be. Essentially, changes in actual processes that impact CLECs are occurring under the guise that it is only an implementation of previously documentation. See examples (from multiple carriers) below:
Example 1 - Tel West
Qwest recently began rejecting orders for having the A block on LSRs without having the usoc RTVXQ. After questioning the CLEC impacting change that was implemented with no notice Tel West was told that when Block A is selected, RTVXQ may or may not be required on the order depending on whether TBE A is chargeable item in the state tariff. Additionally, Tel West was told that it could review this information in RPD (Resale Product Database) under "Billed Number Screening (Long Distance Blocking) - All States Bus Res.
Example 2 – Tel West
Recently Tel West was told after a CLEC impacting change was implemented with no notice that USOC – ORDMS is now being required on all LSRs that are addressing accounts on a 5E switch. Subsequently, Qwest stated that it was not all 5E switches but that ORMDS in now required only on a 5E switch that has Call Return Deluxe. In addition, Qwest stated that there was not a method for determining which 5E switches have Call Return Deluxe and that Tel West should submit the order and if it errors out, then Tel West will know the switch has Call Return Deluxe. For example, rejected LSR 6312075 for PON 30310RB07. This was rejected and was the first one rejected that was on a 5E switch.
Example 3 - Eschelon
Eschelon populated the hunt group (A, b or c…so on) with the hunt sequence. Qwest accepted and worked our LSR. Qwest then implemented a CLEC impacting change with not notice then all of the sudden one day they started rejecting the orders, and though the documentation indicated the order should be rejected that was not Qwest business practice until recently. Eschelon had to react very quickly to change process.
Example 4 - Eschelon
Qwest recently implemented a CLEC impacting change with no notice in which it suddenly change the requirements for Type of Service (TOS) when ordering Resale and UNE-P. Eschelon always used multi-line flat rate as a default. Qwest is now requiring single line when it applies and measured for UNE-P.
Example 5 - Eschelon
Qwest recently implemented a CLEC impacting change with no notice regarding listings when changing at time of conversion. Qwest now requires the CLEC to populate the omit address and direct marketing field on the listing that is being removed.
Example 6 – Eschelon
Qwest recently implemented a CLEC impacting change with no notice regarding call forwarding features…intra VS inter. Previously Qwest would correct the type of CF’ing from FVJ to EVF or visa versa if needed. Qwest is now rejecting for these.
Example 7 – McLeod
Qwest recently implemented a CLEC impacting change with no notice regarding CFLAG. In the past, Qwest’s practice was that the CFLAG is only to be used when a verbal has been given to the CLEC for a change to their order. Recently Qwest began using this if they can determine what the CLECs intent was without contacting the CLEC or to communicate to the CLEC regarding process issues.
Example 8 – McLeod
Qwest recently implemented a CLEC impacting change with no notice regarding the BA field. In the past the CLEC populated the BA =N on a 1FB order then the USOC's do not need to be recapped would be retained. Recently Qwest changed its business practices and instructed CLECs that this is incorrect and flow through has been dropping the blocking. All the while, McLeod thought the orders were recapping.
Example 9 - McLeod
Qwest recently implemented a CLEC impacting change with no notice regarding IMP CON telephone number. In the past Qwest’s business practice was to not require a local or toll free number for the IMP CON TN. Recently Qwest changed its business practices and started rejecting McLeod orders due to the IMP CON TN not being a local number or toll free number for pots. McLeod pointed out That this is not documented in the EDI developer worksheets but is in the LSOG.
Example 10 - McLeod
Qwest recently implemented a CLEC impacting change with no notice regarding Partial Moves. In fact this process has been changed several times and Qwest is not sure what the process is supposed to be. Qwest issues rejects on a process that is not documented.
Example 11 - McLeod
Qwest recently implemented a CLEC impacting change with no notice regarding MDSI fids. Qwest accepted call forwarding and Message waiting indicators for voicemail without fids in the 5ESS switches. Recently Qwest changed its business practices and started requiring them to be on all orders where the features were being added or changed. They then made the change to flow through to add the mdsi fids to the call forwarding usoc's if we sent it with the MWW usoc.
Example 12 - McLeod
Qwest recently implemented a CLEC impacting change with no notice regarding PFG. In the past McLeod was instructed to pass the PFG fid in all CO's. Recently, Qwest changed their practice and started requiring that the McLeod pass this in the 5ESS switches individually at a later date stating this was the correct process.
Example 13 – McLeod
Qwest recently implemented a CLEC impacting change with no notice regarding ALI Codes. In the past, - Qwest allowed the use of a placeholder for ALI Codes on all directory listing related orders. Recently Qwest changed its business practices and started requiring the correct ALI and disallowing the placeholder.
Example 14 – McLeod
Qwest recently implemented a CLEC impacting change with no notice regarding Hunt Ids. Qwest was allowing a placeholder for all hunt activities the. Then recently Qwest started requiring correct hunt ids and disallowed the placeholder on orders. Qwest is now requiring McLeod to fill in the Hunt Id on move orders even though the hunt activity is new. This is contrary to the developer worksheets, which state it must be blank. But the LSOG states its conditional and again that is what the business unit is following.
Expected Deliverable: Immediate implementation date is expected.
|
Date | Action | Description |
3/28/2003 | CR Received | |
3/31/2003 | CR Acknowledged | |
4/2/2003 | Contact Customer to schedule Clarification Meeting for 4/8/03 | |
4/8/2003 | Held Clarification Call with CLEC | |
4/16/2003 | April CMP Meeting minutes will be posted to the database | |
5/14/2003 | Sent response to CLEC via email and posted to database 5/13 | |
5/21/2003 | May CMP Meeeting minutes will be posted to the database | |
5/21/2003 | This CR will be handled via the oversight committee - see notes posted to the web under Oversight Committee Notes for details |
Project Meetings |
5/21/03 May CMP Meeting - Judy Schultz – Qwest reviewed the response. Judy explained this CR is asking Qwest to comply with an existing process. This is outside the scope of CMP as outlined in Section 5.3. The correct avenue to bring items to Qwest when the CLECs believe Qwest is not following an established process is via the Oversight Committee (Section 18 CMP Process) or to their Service Manager if it is a performance related issue. Judy explained we are denying this request but we have done investigation on each item and would be glad to review them with the participating CLECs. Lynne Powers – Tel West advised she did escalate the CR yesterday. Lynne said if Qwest creates an MCC internally to change the process, then this also needs to be communicated externally via a notification. Judy agreed these items are important and advised that we have done an investigation on each item. Lynne advised she has not gotten anything in writing. Judy asked what procedure would you like to take to review the investigation? Oversight committee or Service Manager review? Bonnie Johnson said when she calls Escalations they tell her she can’t issue the LSR that way as they got an MCC that tells them they need to comply with the process. If the CLEC is not doing something correctly and Qwest has been processing the LSR and now we are rejecting them, it is a courtesy for Qwest to notify the CLECs that we are going to adhere to the process. Judy agreed that if we begin enforceing a process across the board it is our responsibility to notify. When we reviewed the 14 items there were multiple reasons for each item. Covad asked if this CR includes creating a process for how to stop a process when it is implemented without notification? Cindy – Qwest advised this is the first time that was discussed so it wasn’t part of the original request. Section 2.4.5 talks about how to stop a process. Bonnie Johnson – Eschelon requested for Qwest to identify how/where the CLECs should have taken these items if it wasn’t via a CR. Qwest agreed to add that to their investigation documentation. The group agreed this CR would be denied and show the suffix of Escalation and be taken to the Oversight Committee and be discussed after the P/P meeting in June. 4/16/03 April CMP Meeting - PC032803-1 Qwest to halt implementation of CLEC impacting process changes with no notice Lynne Powers – Tel West reviewed and clarified the CR. Lynne explained Tel West has 2 examples, Eschelon has 4 and McLeod has the remainder. Lynne explained the CLECs have been following a process and the next day the process is different. This is systematic across the board. This is not a ‘onesy twosy’ occurrence. Sharon ATT said she does not have a recent example but this has happened in the past. Qwest made an upgrade to back end systems and it impacted the LSR process. No notification was sent as it was a back end system. This has happened a couple of times and it does impact the CLECS. This CR will be moved to Presented status.
Clarification Call CR PC032803-1 Qwest to halt the implementation of CLEC impacting changes without notification In Attendance: Dusti Bastian Qwest Mark Early Qwest Terri Kilker Qwest Bonnie Johnson Eschelon Susie Wells Qwest Jolene Wees Qwest Stephanie Prull McLeod Shon Higer Qwest Lynn Powers Tel West Chris Scurgul Tel West Matt Myers Tel West Cindy Macy Qwest Pete Budner Qwest Jean Novak Qwest Jennifer Fisher Qwest Lynn Powers reviewed the overall intent of the CR. Lynn advised she would cover the Tel West examples and the other CLEC in attendance will cover their own examples. Lynn explained that sudden changes in policies and procedures without notification negatively affects the CLECs. Lynn said she has been advised that Qwest is just tightening up the process. From a CLEC perspective this has a large impact. Example 1 Lynn Powers – Tel West Lynn read example 1. There were no questions. Example 2 Lynn Powers – Tel West Lynn read example 2. There were no questions. Example 3 Bonnie Johnson – Eschelon Bonnie read example 3. Shon Higer asked if the field on the LSR where you input the Hunt Sequence is the field that is referenced on the CR? And what was the Hunt Activity on this example? Bonnie agreed to provide the Hunt Activity Indicator on a flow thru order that caused it to fall out. Example 4 Bonnie Johnson – Eschelon Bonnie read example 4. There were no questions. Example 5 Bonnie Johnson – Eschelon Bonnie read example 5. Mark Early asked for an example to be able to investigate. Bonnie agreed to send an example. Example 6 Bonnie Johnson – Eschelon Bonnie read example 6. There were no questions. Example 7 Stephanie Prull - McLeod Stephanie read example 7. Stephanie explained CFLAG is being used without McLeod’s input. Bonnie also added that she was looking for a process on how to use CFLAG and couldn’t find one. She sent a question to ‘Ask Questions’ on the documentation page and her reply was there isn’t a process documented. There are internal discussions going on about this. Bonnie advised she believes the LSOG is different than EDI documentation. There were no questions. Example 8 Stephanie Prull - McLeod Stephanie read example 8. Stephanie said she was told they should be recapping the Toll Denied and 900 Block USOCs and then they would not drop out. McLeod didn’t know they should be doing anything with these USOC. No questions were asked. Example 9 Stephanie Prull - McLeod Stephanie read example 9. Stephanie said they started getting rejects saying they need an 800#. They brought this to their Service Manager’s attention. In December they got information about this in the LSOG. There were no questions. Example 10 Stephanie Prull - McLeod Stephanie read example 10. McLeod was told to write two orders for a partial move. At some point the SDC said they only needed to write 1 order, but then the CLEC gets a reject. It seems like this process is not documented or very clear to Qwest. Susie Wells asked if this is regarding a certain product? Stephanie said mainly 1FB and some 1FR POTS. Example 11 Stephanie Prull- McLeod Stephanie read example 11. McLeod has voice mail products and was told not to pass MDSI trouble information. Then McLeod was told we need to pass on all Call Forwarding features. Then we were told to not pass on this information as FTS is doing it. This process keeps changing and we were not notified. There were no questions asked. Example 12 – Stephanie Prull- McLeod Stephanie read example 12. McLeod was told to pass the PFG fid in 5ESS offices. Having to pass this information caused a hard coding change in our systems. There were no questions. Example 13 – Stephanie Prull - McLeod Stephanie read example 13. Mark Early asked for examples to be able to investigate further. Example 14 – Stephanie Prull McLeod Stephanie said that Qwest was allowing placeholders and we didn’t have to match to a hunt group and now we don’t allow the placeholder. This is also happening on EDI. Stephanie said she was advised an MCC has been issued to help clarify the LSOG and Developer worksheets. There were no questions. Cindy summarized our next steps. The participating CLECs will Clarify this CR to the CLEC Community at the April 16 CMP Meeting. Qwest will provide our response at the May CMP Meeting.
|
CenturyLink Response |
May 14, 2003 For Review by CLEC Community and Discussion at the May 21, 2003 CMP Meeting Lynne Powers Tel West Communications SUBJECT: Change Request Response – CR #PC032803-1 ‘Qwest to halt the implementation of CLEC impacting process changes with no notice’ This letter is in response to Tel West Communications Change Request (CR) PC032803-1. This CR requests that Qwest halt the implementation of CLEC impacting process changes with no notice. Qwest denies this CR on the basis that it is outside the scope of the Change Management Process because the CR seeks adherence to existing procedures. It is Qwest’s practice to notify CLECs when it makes CLEC impacting changes to its processes. However, Qwest has investigated the issues raised in the CR and will be happy to discuss our findings with you. Alternatively, you may submit your issues to the CMP Oversight Committee pursuant to Section 18 of the CMP. Sincerely, Judith Schultz Director Program / Project Management Qwest
|
Information Current as of 1/11/2021