28.01.2013 Views

March 2004 Product & Process CMP Team Meeting ... - CenturyLink

March 2004 Product & Process CMP Team Meeting ... - CenturyLink

March 2004 Product & Process CMP Team Meeting ... - CenturyLink

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Product</strong> & <strong>Process</strong> Change Management <strong>Process</strong><br />

<strong>March</strong> <strong>2004</strong><br />

<strong>Product</strong> & <strong>Process</strong> <strong>CMP</strong> <strong>Team</strong> <strong>Meeting</strong><br />

Distribution Package<br />

<strong>March</strong> 17, <strong>2004</strong><br />

3/12/04 © <strong>2004</strong>, Qwest Corporation


<strong>Product</strong> & <strong>Process</strong> Change Management <strong>Process</strong><br />

<strong>Product</strong> & <strong>Process</strong><br />

Change Management <strong>Process</strong> (<strong>CMP</strong>)<br />

Monthly <strong>Meeting</strong><br />

8:00 a.m. – 3:00 p.m. (MT)<br />

Wednesday, <strong>March</strong> 17, <strong>2004</strong><br />

Room 180, 1005 17 th Street, Denver, Colorado<br />

Conference Bridge – 1-877-572-8687, Passcode 3393947<br />

Facilitator<br />

Susie Bliss – Director, Change Management<br />

Agenda<br />

Time Topic Presenter/Facilitator<br />

8:00 – 8:15 Introductions / Roll Call Kit Thomte<br />

8:15 – 8:30 Announcements & Previous <strong>Meeting</strong> Minutes<br />

• See Attachment A – Previous <strong>Meeting</strong> Minutes<br />

8:30 – 8:45 Review Global Action Items<br />

• See Attachment B – Global Action Items<br />

8:45 – 10:00 Review “Active” CLEC Originated Change Requests<br />

10:00 – 10:15 Morning Break<br />

• See Attachment C – CLEC CR Summary Report<br />

• See Attachment D – CLEC CR Detailed Reports<br />

Kit Thomte<br />

AI Owners / SMEs<br />

CR Owners / SMEs<br />

10:15 – 10:45 Review “Active” CLEC Originated Change Requests (continued) CR Owners / SMEs<br />

10:45 – 11:00 Review “Active” Qwest Originated Change Requests<br />

• See Attachment E – Qwest CR Summary List<br />

• See Attachment F – Qwest CR Detail Reports<br />

CR Owners / SMEs<br />

3/12/04 © <strong>2004</strong>, Qwest Corporation


<strong>Product</strong> & <strong>Process</strong> Change Management <strong>Process</strong><br />

Agenda – Continued<br />

Time Topic Presenter/Facilitator<br />

11:00 – 12:00 Discussion of <strong>CMP</strong> Operations and Proposed Modifications to<br />

<strong>CMP</strong> Framework<br />

12:00 – 1:00 LUNCH<br />

• See Attachment G – Proposed Modifications to <strong>CMP</strong><br />

Framework<br />

Kit Thomte<br />

1:15 – 1:45 CLEC Forum Update CLECs<br />

1:45 – 3:00 Walk On Items<br />

• Eschelon Walk on Request – Notice<br />

PROD.02.09.04.F.01327.Removal_of_LNP_Surcharge<br />

Announcements<br />

• April <strong>2004</strong> <strong>Product</strong> & <strong>Process</strong> <strong>CMP</strong> <strong>Meeting</strong> – April 21, <strong>2004</strong>, Room 180, 1005 17 th Street<br />

• April 7, <strong>2004</strong> is the last day to submit CRs for presentation at the April 21, <strong>2004</strong>, <strong>Product</strong> & <strong>Process</strong><br />

<strong>CMP</strong> <strong>Meeting</strong>.<br />

• Interactive Reports for <strong>CMP</strong> Change Requests can be found at<br />

http://www.qwest.com/wholesale/cmp/changerequest.html<br />

• The Qwest Wholesale Change Management <strong>Process</strong> Document can be found at<br />

http://www.qwest.com/wholesale/cmp/whatiscmp.html<br />

3/12/04 © <strong>2004</strong>, Qwest Corporation


<strong>Product</strong> & <strong>Process</strong> Change Management <strong>Process</strong><br />

Attachment A – Previous <strong>Meeting</strong> Minutes<br />

3/12/04 © <strong>2004</strong>, Qwest Corporation


Qwest Wholesale Change Management <strong>Process</strong> (<strong>CMP</strong>) <strong>Meeting</strong> Minutes<br />

Change Management <strong>Process</strong> (<strong>CMP</strong>) Monthly <strong>Meeting</strong><br />

<strong>Product</strong> / <strong>Process</strong><br />

8:00 – 3:00 Wednesday February 18, <strong>2004</strong><br />

1005 17 th Street Community Room<br />

Denver, Colorado<br />

INTRODUCTION<br />

Participants met February 18, <strong>2004</strong> to discuss and review status of Action Items; CLEC initiated Change Requests, Qwest initiated<br />

Change requests and other <strong>CMP</strong> items. Following is the write-up of the discussions, action items, and decisions made in the working<br />

session.<br />

The list of associated attachments is as follows:<br />

Attachment A – List of Attendees<br />

ATTACHMENTS<br />

MEETING MINUTES<br />

The meeting began with Qwest making introductions and welcoming all attendees. Qwest advised that the minutes were issued and posted<br />

to the <strong>CMP</strong> web site. Qwest asked if there were any additional comments. There were no additional comments.<br />

Review Global Action Items<br />

AI012103-3 Resource Requirements associated with TRO Activity<br />

Judy Schultz with Qwest said this action item was opened last month because Mike Zulevic with Covad had asked how Qwest would<br />

support the TRO system changes. Judy said additional resources will not be added to support TRO systems changes. Any systems<br />

changes and the systems support will be absorbed in the October release. This action item will be closed.<br />

AI012104-1 Binding Post Information on Non Design Orders<br />

Doug Andreen, Qwest stated that this action item continues to move forward to find the best solution for all parties. Two meetings were<br />

held in the past month.<br />

AI012104-2 Systems Architecture <strong>Meeting</strong><br />

Connie Winston with Qwest suggested that this meeting take place during the afternoon of the Systems <strong>CMP</strong> meeting and suggested that<br />

the first topic be high level LSR flow and then the CLECs can give thoughts on future topics. Carla Pardee said this discussion should<br />

help the CLECs frame their CRs. Carla did wonder about timing of the meeting because people are trying to leave during the afternoon of<br />

the Systems meeting. Connie said that Qwest plans to give a general overview for the first meeting and Kit Thomte with Qwest suggested<br />

that the first meeting be held in April due to discussion about open CRs planned for the <strong>March</strong> meeting. This action item will be closed in<br />

<strong>Product</strong> <strong>Process</strong> and will be opened on Systems.<br />

03/02/0402/24/04 Page 1 of 12


Qwest Wholesale Change Management <strong>Process</strong> (<strong>CMP</strong>) <strong>Meeting</strong> Minutes<br />

AI012104-4 Documentation <strong>Process</strong><br />

Mark Coyne – Qwest advised that at the January meeting we agreed to review the process. As a result of the review, we believe the<br />

process is meeting the intent. We gathered data and determined that the average turnaround time for Documentation CRs to be completed<br />

is 3-3 ½ months. This is less time than the <strong>CMP</strong> process. Some requests do go outside of the average time frame. The documentation<br />

team would like to propose 2 measures to help address Eschelon’s issues:<br />

• Add an escalation point at 14 days. The escalation would continue until we obtain a proposed completion date<br />

• Add a field on the Documentation Request form to identify how critical the request is; such as Minimum, Moderate and Major<br />

Impact.<br />

Mark advised that Qwest would try to determine within the first 14 days if the request can be completed in 60-90 days. If we don’t<br />

believe completion is possible in that time frame, then we will contact the CLECs and offer to drop the request from the Documentation<br />

process and put it into the <strong>CMP</strong> process.<br />

Bonnie recapped to clarify her understanding. Bonnie advised it doesn’t seem logical if we are 14 days into the process and then we are<br />

asked to go to the <strong>CMP</strong> process. Qwest has internal documentation but hasn’t done external documentation. Why, if we don’t have to<br />

develop the process, does it take so long? Bonnie said that she appreciates adding the additional steps to the process. Bonnie asked if we<br />

could get a time commitment to complete the request? Mark advised that he is not in control of the resources that provide the content of<br />

the process so he can not commit to a date to complete the request. Mark advised that these procedures are not always documented<br />

internally, that they are existing processes, but they may not be documented. Bonnie asked if she takes the request through <strong>CMP</strong> would it<br />

get completed faster (comment begin from Eschelon) and if the same Qwest personnel are doing the documentation for a CR as for the<br />

documentation process. Mark said yes it is the same personnel. Mark said a CR would take a higher priority, but it depends on what<br />

resource is impacted based on the request. Bonnie asked if we thought this made sense since it was the same people? (comment end from<br />

Eschelon). Mark advised that all current documentation requests are within the 60-90 timeframe. Mark would like to implement this<br />

process as a Level 1 and see how it works. Bonnie agreed to give this a try and Level 1 is okay. Bonnie advised it is okay to close this AI<br />

and if necessary another one could be opened later. This action item will move to Closed Status.<br />

AI012104-5 Network Disclosures<br />

Jim Maher – Qwest advised that he would explain the purpose of Network Disclosures at a high level. Jim advised that these are on the<br />

Wholesale web site, and are based on 1996 Telecom Act and Computer Inquiry lll requirements. There are only around 40 of them, so it<br />

isn’t a large volume. Network Disclosures alert the industry of network technology changes such as switch deployments / upgrades etc.<br />

All Wholesale customers IXC, CLECs, ESP etc. are addressed in the topics that are covered under Network Disclosures. The Network<br />

Disclosure site is updated and has been in place for quite some time. The question was how do Network Disclosures fit into <strong>CMP</strong>? When<br />

Qwest sends out the disclosure it is an announcement, not a commitment. There are two types of announcements; 6 month<br />

announcements that are posted to the website, and 60 day announcements that include a Network notification. Sometimes CRs are issued<br />

as a result of a Network Disclosure, if there is an impact to the CLEC. The Network Disclosure usually would go out prior to the <strong>CMP</strong><br />

notification. Bonnie Johnson – Eschelon asked if Network Disclosures do apply to <strong>Product</strong> <strong>Process</strong>? Jim advised if there is a CLEC<br />

impact there would be a subsequent <strong>CMP</strong> product or process notice. Phyllis Burt – ATT asked if Network Disclosures drive all Network<br />

Notifications? Jim Maher advised some Network Notification come out as <strong>CMP</strong> notices, and they are different than Network Disclosures.<br />

Phyllis asked about one Network Notification that impacted data that ATT receives. Phyllis asked why wasn’t this a Systems<br />

notification? Jim thanked Phyllis for the example and stated that the notification Phyllis was referring to was associated with Network<br />

dispatches and that Qwest had determined the category for that notice. Jim agreed that this was a gray area when the notices could<br />

involve content changes in the data that the CLECs received, and that Qwest would look at how notifications like this could be managed<br />

in the future. Connie Winston – Qwest advised that sending a system notice would depend on a number of things. Jim asked if we could<br />

close this action item, and Bonnie advised yes. This Action item will move to Closed Status.<br />

AI071603-1 Will Qwest offer CLECs a process to grant blanket approval for DSL Conditioning<br />

Kit Thomte - Qwest stated that this project would remain an open action item until spring (April <strong>2004</strong>) until additional system work is<br />

completed.<br />

AI111903-1 Construction Definition and Charges Review<br />

03/02/0402/24/04 Page 2 of 12


Qwest Wholesale Change Management <strong>Process</strong> (<strong>CMP</strong>) <strong>Meeting</strong> Minutes<br />

Jamal Boudhaouia with Qwest said that Network modifications would be available in mid-<strong>March</strong> for review. The TRO will determine the<br />

requirements for construction, which will drive the QPF fee. Bonnie Johnson with Eschelon asked when documentation would be<br />

available for review. Jamal responded that documentation will be available in mid-<strong>March</strong>. This action item will remain open.<br />

Review Active CLEC Originated Change Requests<br />

PC042103-2 Escalation Ticket Reporting<br />

Michelle Thacker with Qwest gave an update that the January reports were sent on 2/16/04 and asked if the CR could be closed.<br />

Stephanie Prull with Eschelon said that Eschelon agrees to close this CR and suggested that Qwest also contact Michelle Sprague at<br />

McLeod to close. Qwest will e-mail McLeod to confirm closing this CR. This CR will move to Completed status if McLeod agrees.<br />

PC070202-2X Time and Material Repair Charges Invoice <strong>Process</strong><br />

Jim Recker – Qwest advised that we made changes to the User Guide to help clarify and correct information regarding frequency of ticket<br />

updates and circuit id entry. We reviewed the Guide with Kathy Stitcher – Eschelon before we published it. Kathy agreed it met her<br />

needs and approved the changes. Kathy Stitcher – Eschelon advised she is fine with the changes and it is okay to close this CR. Kathy<br />

thanked Qwest for making the changes. Stephan Calhoun – Cbeyond asked if this tool is specific to a certain product. Jim Recker –<br />

Qwest advised no, it contains design and non design repair tickets. Kathy Stitcher – Eschelon advised this tool give CLECs a heads up on<br />

what will be billed. We use it to look at the invoice and CLEC repair system and compare charges. This CR will move to Completed<br />

status.<br />

PC072303-1 Customer Not Ready (CNR) jeopardy notice should not be sent to Qwest to CLECs before 5PM<br />

local time on the due date (for basic install)<br />

Jill Martain with Qwest said the final notice was sent on 1/2/04 and the PCAT was effective 1/19/04. Stephanie Prull asked if Qwest is<br />

holding the jep statuses in IMA. Jill said that a system CR would be required to hold jep statuses from the inquiry functionality, only the<br />

jeopardy notices were being held in IMA. This CR will be moved to Completed status.<br />

PC120803-1 Associated Move Orders<br />

Qiana Davis with Qwest reviewed the draft response and said that AT&T had revised the CR on 2/3/04 and that Qwest is evaluating the<br />

modifications and require additional time to respond to the CR. Qiana added that Qwest would provide an update in <strong>March</strong>. Carla Pardee<br />

with AT&T said AT&T had determined that a process does exist, however AT&T has had several examples where the orders are<br />

disconnected. Carla also said they have been working with their service management team on this issue as well. Qwest will provide an<br />

update in <strong>March</strong>. This CR will be moved to Evaluation status.<br />

PC120903-1 Qwest will track ‘access required’ information in its systems when Qwest installs new service,<br />

or when Qwest dispatches on the repair of an existing line/circuit. Qwest will make the information<br />

available to CLECs for use when a CLEC opens a repair ticket<br />

Don Tolman, Qwest stated that Qwest is currently reviewing the request and will provide a complete response in the <strong>March</strong> meeting. He<br />

requested the CR be moved to Evaluation status.<br />

PC011604-1 All Joint Maintenance and Trouble Isolation Documentation be placed in the same location on<br />

the Qwest Web Site<br />

This was a walk-on CR by Covad in January. Doug Andreen, Qwest in John Berard’s absence stated that a Clarification call was held and<br />

the intent of the CR is to provide a method of easy access to documentation that the Qwest and CLECs technicians commonly use in<br />

trouble isolation and maintenance work. The CR calls for the documentation to be located or accessible from a common point on the<br />

web. Jim Recker, Qwest added that John would provide us with examples of processes Covad now uses to find the documentation. This<br />

CR will be moved to Presented status.<br />

03/02/0402/24/04 Page 3 of 12


Qwest Wholesale Change Management <strong>Process</strong> (<strong>CMP</strong>) <strong>Meeting</strong> Minutes<br />

PC01<strong>2004</strong>-1 Include escalation ticket detail along with the monthly escalation ticket report or create a<br />

separate report to provide the detail.<br />

Bonnie Johnson with Eschelon presented this CR. Bonnie said this is an extension to the CR just closed and this CR asks for more detail<br />

than the report currently provides. Eschelon’s service manager has provided a report that included the level of detail required to address<br />

Eschelon’s training needs. This CR will be moved to Presented status.<br />

PC022703-9X Support <strong>Product</strong>ion Defect Report (crossed over from SCR022703-09)<br />

Connie Winston – Qwest advised that this CR is the one ATT originally issued. This was discussed during the Global Action Item<br />

meetings. IT looked at specific data elements on the request and we are planning on providing these via PC111903-1. Donna Osborne<br />

Miller – ATT advised we understood when Carla submitted the other CR, Qwest would deny this CR. Donna said she thought that Qwest<br />

would identify the parts of this original CR that would not be met but the new CR PC111903-1. Qwest agreed that we would identify the<br />

data elements that are not being met by the new CR and send this information to ATT and populate it in the database. This CR will<br />

change to Denied Status.<br />

PC062603-03 Business Rules Clarification calls and event notification updates through the Addendum<br />

process<br />

Beth Foster with Qwest said that this CR has been discussed at the global action item meetings and last week Qwest met with AT&T and<br />

Liz Balvin with MCI. Qwest took action items from that meeting and determined that meeting minutes will be provided and posted on the<br />

production support page along side the trouble ticket information which is currently populated on the Wholesale Web site. There was<br />

discussion regarding the timeframe of posting meeting minutes. Connie Winston with Qwest said they would post the minutes within 3<br />

days and would strive to get completed as soon as possible. Connie also said that Qwest would capture necessary information, necessary<br />

action items and a general re-cap of the meeting intent. Phyllis Burt mentioned that issues of importance to Qwest might not be the same<br />

as those that are important to the CLEC. Connie suggested that the CLEC could provide a red-line of meeting minutes back to Qwest.<br />

Donna Osborne-Miller with AT&T said that we could put this CR into CLEC test and see how the process works.<br />

Beth said that another action item was to look at how to handle the business rules clarification piece of the request, and noted that AT&T<br />

had initially asked that the Disclosure documentation be updated when CLECs ask for clarification. Qwest would like to start a single<br />

Q&A log with 15.0 release and provide the log on the wholesale website out where the EDI Documentation FAQ pages currently resides.<br />

This single Q&A log will provide needed clarification to documentation, a way to see documentation before the addendum is posted, and,<br />

will allow everyone to see what questions other CLECs have had and how Qwest has responded. Beth explained that the process for EDI<br />

will be covered by the CLECs EDI Implementation <strong>Team</strong>s, and included in the body of the Q&A document that will be posted.<br />

Randy Owen with Qwest said an e-mail address would be set up for CLECs to send questions.<br />

Phyllis Burt requested the Q&A log be categorized by topic, such as Appointment Scheduling. Randy Owen will take that action item to<br />

see if this is feasible. Donna Osborne-Miller said the Q&A log would be cumbersome if not broken out by fields.<br />

Beth asked if everyone agreed that the process trial could begin with 15.0, and once the documentation was posted the CR could move<br />

into CLEC test for AT&T feedback. All agreed and Beth said that a Systems Notification will be sent stating that the Q&A log will be<br />

located on the Wholesale Web Site, under OSS, IMA, EDI Documentation under the FAQ link. This CR will move to Development<br />

Status.<br />

PC102803-1 Improve Search Functionality of the Qwest Wholesale Website to minimize selections<br />

Doug Andreen, Qwest stated there is no new information this month. The CR will remain in Evaluation status.<br />

PC110403-1 Update accuracy of FAM records<br />

Connie Winston – Qwest advised that we have not gotten approval as of yet for this CR. We are still waiting for approval. Carla Pardee<br />

– ATT advised that ATT is disappointed that this did not get approved as it is a critical issue and it doesn’t seem as if this CR requires a<br />

lot of resources, so we do not understand the lack of approval. Bonnie Johnson – Eschelon asked is this one is like the ICON database?<br />

Connie advised she is not sure. Bonnie advised that her Service Manager (Jean Novak) told her that the fix would take place on <strong>March</strong> 1,<br />

03/02/0402/24/04 Page 4 of 12


Qwest Wholesale Change Management <strong>Process</strong> (<strong>CMP</strong>) <strong>Meeting</strong> Minutes<br />

<strong>2004</strong>. Connie advised that maybe an update is scheduled but not the entire fix. Cindy Macy – Qwest agreed to check with Jean Novak.<br />

This CR will remain in Evaluation Status.<br />

PC111903-1 Website for Event Notifiers<br />

Connie Winston – Qwest advised this CR also did not get approved as of yet. We are working on this and should have an update soon.<br />

This CR will remain in Evaluation Status.<br />

PC112003-1 Differentiate between Loop-MUX combos and EELs due to different FCC treatment (TRO<br />

Order)<br />

Pat Finley with Qwest said the examples Cbeyond provided following the January meeting were examples of circuits with jurisdiction<br />

based on the class of service. There were hundreds of circuits converted correctly via record orders and the 10 circuits provided as<br />

examples were issued incorrectly, and required record orders to fix. Pat explained that the PCATs for EEL and LMC were updated and<br />

now contains a downloadable list of USOCs for interstate and intrastate. The USOC list, combined with the TRAK FID on the CSR<br />

differentiates LMC and EEL and there is no need to establish separate classes of service. The work associated with establishing separate<br />

classes of service is prohibitive because of the conversion to the embedded base.<br />

Pat said that the e-mail received from Stephan Calhoun on 1/22/04, confuses the request with other CRs requesting billing changes and<br />

believe that this CR can be closed.<br />

Stephan Calhoun with Cbeyond said the PCAT updates are appreciated and that he was only able to review the Qwest response on this<br />

CR yesterday. Stephan said he has concerns with the 2/3/04 Qwest response and asked that Pat read through the response.<br />

Pat read the draft response. Stephan said that his understanding is that usually classes of service define the product but not the<br />

jurisdiction. Pat disagreed saying that the jurisdiction of many Qwest products is identified by class of service.<br />

Stephan also said that interstate class of service was assigned to conversion orders that were issued last year, are also being assigned on<br />

new requests for EEL and LMCE. Pat said that the interstate EEL and LMC classes of service are only used to convert to Special Access<br />

circuits.<br />

Stephan said that he doesn’t understand the reason UMX was changed to new EEL and LMC. Cbeyond has not made any changes in the<br />

way the services were ordered. Pat Finley said that interstate was only used for conversion orders only.<br />

Stephan said that Cbeyond is concerned that billing doesn’t support the Qwest response. The billing department was not able to identify<br />

what was converted and what was a new order. There seems to be a disconnect with the policy and what is actually done. Pat explained<br />

that the Billing Center is able to access history information on the services, and to tell what is new and what was converted. Stephen said<br />

that the billing manager, service manager and process manager were unable to determine and planned to contact the product manager.<br />

Stephan has provided examples to their service manager.<br />

Stephan is also concerned that the recurring interstate and intrastate EEL do not bill the same as UNE. Pat said that PLT has different<br />

rates and is a finished service. Interstate and intrastate EEL and LMC are billed the same recurring rates. Stephan said LMC jurisdiction<br />

is based on FCC definition and doesn’t seem to fit. Stephan said the concern is not the rate itself, but the rate elements, and asked what<br />

would keep Qwest from applying different rates to interstate and intrastate. Pat asked if the concern is that Qwest may raise UNE rates<br />

that are interstate. Pat explained that Qwest is obligated to make these UNEs available to CLECs at TELRIC rates.<br />

Judy Schultz with Qwest said there are many concerns with this CR and suggested that an ad hoc meeting be scheduled to discuss. This<br />

CR will remain in Evaluation status.<br />

PC112403-1 Request for blocking feature for 411 and 555-1212<br />

Carla Pardee, Qwest said that she is waiting for AT&T to conclude their testing with CustomNet Option 1 to see if this will satisfy the<br />

needs of this CR. She would like to move the Status to Deferred until AT&T completes testing.<br />

PC031103-1 Convert Common Area Splitter Collocation to Cageless Shelf at a time Collocation<br />

03/02/0402/24/04 Page 5 of 12


Qwest Wholesale Change Management <strong>Process</strong> (<strong>CMP</strong>) <strong>Meeting</strong> Minutes<br />

Dave Williams with Qwest said that the PCAT changes will be effective on 2/26/04 and a contract amendment will be available at the<br />

same time. This CR will remain in Development status.<br />

PC042103-1 Tracking process for FBDL order issues<br />

Lee Gomez with Qwest gave the update and advised that the CR is on track for implementation in April and will be sending a notification<br />

updating the listing document. The first report will be available in May and the CLECs should contact the Listing Account Manager to<br />

receive the report.<br />

Stephanie Prull with Eschelon asked if multiple ACNAs will all be on the same report. Lee Gomez said there would be a separate report<br />

for each ACNA. This CR will remain Development status.<br />

PC050703-1 Change Qwest Wholesale <strong>CMP</strong> Website to make it easier to search, retrieve and view CRs<br />

Kit Thomte and Doug Andreen, Qwest said the prototype will be available 3/25 and will be located next to the existing Interactive Report<br />

on the Qwest Web Site. It will contain six different sorts for the data. The format is somewhat changed although the content remains the<br />

same. Kit asked if the CLECs would agree to move this CR to test since the prototype will be available in a week. The CLECs agreed to<br />

move the CR to test.<br />

PC051403-4 Sync Test for Loop Splitting on Maintenance Trouble Tickets and Sync Testing for<br />

provisioning of Loop Splitting<br />

Heidi Moreland with Qwest gave an update that the Loop Splitting V16 PCAT adding sync testing for provisioning and repair requests<br />

will become effective on 2/27/04. This CR will remain in Development status.<br />

PC061103-1ES Intercept CLEC customer calls to Qwest Repair Center<br />

Jamal Boudhaouia with Qwest said that funding for the project has been approved and will provide a date for implementation as soon as<br />

available. Bonnie Johnson said that she has asked several times and has not received an answer about the Qwest retail VRU project and<br />

when that is scheduled for implementation or has it been implemented. Jamal said that the project hasn’t been implemented and all<br />

changes will be incorporated and will include the CR requested changes. Bonnie said that Qwest hasn’t made clear what the<br />

implementation date will be. Carla Pardee with AT&T said that the changes were supposed to be effective in April. Jamal said there is<br />

currently no date for implementation. Carla said that the CR is important to AT&T and would like to see solid dates next month adding<br />

that the CR was escalated previously and did not do any good. Judy Schultz with Qwest said that we had just received word that funding<br />

was approved on Friday and IT will determine the dates as soon as possible. The dates will be provided, if available, before the <strong>March</strong><br />

meeting. Bonnie said that Qwest had already provided the implementation date of April, (comment begin from Eschelon) <strong>2004</strong> but now<br />

states that this was just approved. Judy said all changes had to be reevaluated by Noteabart. (comment end from Eschelon). This CR will<br />

remain in Development status.<br />

PC070103-1 Provide ‘Lines in Service Report’ to CLECs<br />

Laura McGhghy with Qwest gave an update that 2/27/04 is targeted to provide the January data. In addition to the report, there will be a<br />

product code explanation file that provides a product code definition. Jennifer Arnold with U S Link asked how to get the report. Laura<br />

explained they should contact their service manager to request. This CR will remain in Development status.<br />

PC070103-3 DSL Volume provider and data migrations process to prevent extended<br />

DSL outage<br />

Anthony Washington with Qwest provided an update that we have received funding approval and are waiting for an implementation date.<br />

This CR will remain in Development status.<br />

PC081403-1 Jeopardy Notification <strong>Process</strong> Changes<br />

Phyllis Sunins – Qwest advised that she is working with Kim Isaacs – Eschelon and analyzing some examples that were sent in. Qwest<br />

did find a few process compliance examples that are being addressed. Cindy Macy – Qwest will provide a document to address<br />

Eschelon’s examples and this will be reviewed during the ad hoc meeting the first week in <strong>March</strong>. This CR will remain in Development<br />

Status.<br />

03/02/0402/24/04 Page 6 of 12


Qwest Wholesale Change Management <strong>Process</strong> (<strong>CMP</strong>) <strong>Meeting</strong> Minutes<br />

PC081403-2 Workback process/products expanded to include additional products and allow partial<br />

workbacks. Qwest will post the process and products included in the Business Procedure section of the web<br />

site.<br />

Cindy Macy – Qwest provided status for Joan Wells. The first part of this process was published and implemented. Joan is working on<br />

the process for the additional products. Joan is working with Retail to identify impacts. (comment begin from Eschelon) Bonnie<br />

explained Eschelon’s concerns about having a requirement that the porting cannot have occurred. Bonnie said that if the porting had not<br />

occurred we problably would not need this process because we could sup the LSR. The problem occurs when the customer is impacted<br />

after the order completes and the port has occurred. Qwest said that would have to go through Retail. Bonnie expressed concern about the<br />

customer going in the front door in an out of service condition and getting stuck in the Wholesale/Retail twilight zone. Bonnie said the<br />

existing process is that LNP workbacks are done AFTER the porting has occurred so Qwest is changing its existing process. Qwest did<br />

not disclose it would change the existing process along with adding partial workbacks. (comment end from Eschelon). This CR will<br />

remain in Development Status. Cindy, Where do we go with this?<br />

PC092903-1 Joint Inventory <strong>Process</strong><br />

Cindy Macy – Qwest provided status for Steve Nelson. Cindy advised that the team met with the CLECs on February 4, <strong>2004</strong>. The<br />

process and forms were reviewed. Qwest advised a Joint Inventory process trial would be held with some of the CLECs. Qwest will use<br />

the trial to work out any gaps in the process. This CR will remain in Development Status.<br />

PC102303-1 10,000 lines billed on Summary BANs before opening a new Summary BAN<br />

Sue Kriebel, Qwest said that an MCC notice has been issued to the centers reinforcing the minimum three day notice that Qwest must<br />

give the CLECs before opening a new BAN. Further, the PCAT covering the 6,000 limit per BAN will be published 3/18. This CR will<br />

stay in Development.<br />

PC111303-1 Allow multiple Billing Account Numbers Per <strong>Product</strong> Per State<br />

Sue Kriebel reviewed the action item concerning the examples from Cbeyond that carried non-active BAN numbers. Sue clarified the<br />

issue by stating that not all orders are assigned BANs automatically but only those that go through flow through. It was uncovered that<br />

orders manually typed were having BANs assigned incorrectly in some cases. She is working with the centers to correct. Stephen<br />

Calhoun, Cbeyond asked about the issue of the CLECs being able to use the alternate BAN field as they wished. Doug Andreen, Qwest<br />

said that was still being researched. Connie Winston, Qwest is looking into dropping existing edits of a formatting nature that now exist<br />

in the system. The CR will remain in development.<br />

Review Active Qwest Initiated Change Requests<br />

PC012604-1 LSR Rejects with RPON<br />

Anne Robberson – Qwest advised this is a new CR that is addressing a process that is not handled consistently and not currently<br />

documented. This CR was created as a result of a CLEC inquiry. Qwest is in the process of documenting the Draft <strong>Process</strong> and will<br />

review this with the CLECs the first week in <strong>March</strong>. Bonnie Johnson – Eschelon asked if the process would be sent out prior to the<br />

meeting. Cindy Macy – Qwest advised that a meeting notification would go out with the process attached. The intent of the meeting is to<br />

review the process and gather input from the CLECs. This CR will move to Presented Status.<br />

PC090203-1 Define criteria for use of CFLAG/PIA field<br />

Jill Martain – Qwest advised the PCAT was published and comments were addressed. This closed January 28, <strong>2004</strong>, effective <strong>March</strong> 3,<br />

<strong>2004</strong>. Subsequent FOC was addressed. There will be a CLEC meeting to discuss PIA 14 on February 26, <strong>2004</strong>. Stephanie Prull –<br />

Eschelon was in the 15.0 walkthrough meeting yesterday and realized that there would be an Order Level PIA and an LSR Level PIA.<br />

Stephanie advised this was never discussed in any of the PIA meetings. Qwest was able to page Denise Martinez-Qwest to join the call.<br />

Denise and Jill explained this is the way PIA is being implemented, opposed to the content or meaning of the PIA value. Denise and Jill<br />

advised this would allow Qwest to be specific with the correct level of PIA. Some PIA values are related to a BAN so that would be at an<br />

LSR level, and some PIA values are related to a Due Date or TN change so that would be at an Order level. Stephanie advised she<br />

understand the functionality and she agrees that it makes sense to implement it this way, but she was not aware of how she missed the way<br />

this was going to be implemented. Her understanding is that there would be multiple values, but not multiple fields or segments. Bonnie<br />

03/02/0402/24/04 Page 7 of 12


Qwest Wholesale Change Management <strong>Process</strong> (<strong>CMP</strong>) <strong>Meeting</strong> Minutes<br />

Johnson – Eschelon asked if the multiple PIA values are at different levels for the same PIA reason? This relates to PO20 impacts.<br />

Denise Martinez – Qwest advised it is a means for us to apply the value most accurately. It would not increase the amount of other PIAs.<br />

Jill Martain – Qwest advised that you might have LSR level PIA and then PIA values on the orders that are created from the LSR.<br />

Stephanie Prull – Eschelon advised our vendor does not support this so we will not be able to implement. Connie Winston – Qwest<br />

advised this is the CR in 15.0 for ‘Multiple PIA Values’. Bonnie Johnson – Eschelon said we never discussed (comment begin from<br />

Eschelon) nor did Qwest disclose(comment end from Eschelon) order versus LSR level. We were under the impression that PIA was PIA<br />

– no different between order and LSR levels. Connie Winston – Qwest asked if we can provide a comment on the draft Tech Specs and<br />

then we will provide a response the to comment. Stephanie Prull – Eschelon advised she already submitted it as a comment and that this<br />

would be fine to handle it this way, instead of holding an ad hoc meeting. This CR will stay in Development Status.<br />

PC103103-1 Buried service wire/placing/conduit/technician interface with end user<br />

Shirley Tallman, Qwest said the comment cycle completed with no comments being received. The PCAT will be published and<br />

operational on <strong>March</strong> 5. The CR will stay in Development status.<br />

PC103103-2 Binding Post information<br />

Shirley Tallman, Qwest said the comment cycle completed with no comments being received. The PCAT will be published and<br />

operational on <strong>March</strong> 5. The CR will stay in Development status.<br />

PC111003-1 Reserved TN Procedure<br />

Jan Dimmitt said she is currently working on the PCAT. No line ranges have been encountered that require contacting the CLECs. The<br />

CR will remain in Development.<br />

PC010604-1 Grandparent DSL Pro USOCs<br />

Janean Van Dusen with Qwest gave an update stating the effective date moved to 5/28/04 and some USOCs will be eliminated and some<br />

grandparented. A new list of USOCs will be provided. This CR will be moved to Development Status.<br />

PC0107043-2 Eliminate Analog Private Line USOCs from Qwest’s offering<br />

Janean Van Dusen, Qwest stated that the new effective date for the CR is May 28. The USOC has also changed and will go out with the<br />

notification. The CR will move to development.<br />

PC010704-3 Eliminate certain Voice Feature USOCs from Qwest’s offering<br />

Janean Van Dusen with Qwest gave an update that the effective date has moved to May 28 and an updated spreadsheet will be provided<br />

for the USOCs. This CR will be moved to Development Status.<br />

PC010704-4 Eliminate Access Line USOCs from Qwest’s offering<br />

Janean Van Dusen – Qwest provided status. This CR tentative implementation date is May 28. The USOCs have been updated and a new<br />

spreadsheet can be sent out. This CR will move to Development Status.<br />

PC020404-1 Grandparent Measured Service Plans in South Dakota, Bus and Res<br />

Janean Van Dusen, Qwest stated that the USOCs would be grandparented and eliminated at the same time since new USOCs will be<br />

implemented. The effective date will be April 21. The new USOCs are provided on the CR. The CR will move to Development status.<br />

PC020404-2 Grandparent Measured Service Plans in Minnesota, Bus and Res<br />

Janean Van Dusen with Qwest presented this CR and said that the USOCs will be grandparented on 4/21/04. This CR will be moved to<br />

Presented Status.<br />

03/02/0402/24/04 Page 8 of 12


Qwest Wholesale Change Management <strong>Process</strong> (<strong>CMP</strong>) <strong>Meeting</strong> Minutes<br />

PC020404-3 Grandparent Measured Service Plans in Utah, Bus and Res<br />

Janean Van Dusen – Qwest provided status. The Business portion of this CR has been cancelled. Residence still applies with a target<br />

implementation date of April 21. This CR will move to Presented Status.<br />

PC050503-2 Grandfather SVDS in all state tariffs including FCC tariff<br />

Janean Van Dusen – Qwest provided status. This CR is still pending FCC approval.<br />

This CR will remain in Development Status.<br />

PC050703-6 Grandfather Measured Service plans in CO, ID North, NM, ND<br />

Janean Van Dusen – Qwest provided status. New Mexico Residence is on hold and New Mexico Business is scheduled for<br />

implementation <strong>March</strong> 22. Idaho North is on hold, Colorado was cancelled and North Dakota was effective January 30 with the IT work<br />

complete with 15.0. This CR will remain in CLEC Test Status.<br />

PC100103-1 Grandparenting of Single Number Service in AZ<br />

Janean Van Dusen – Qwest provided status. This CR was implemented December 31, 2003. This CR will move to Completed Status.<br />

PC102703-1 Grandparent usocs BAUTB, BAMTB, and BAMHB in NE<br />

Janean Van Dusen, Qwest stated that this CR was implemented December 30 and requested the CR be closed. The CR will move to<br />

Completed status.<br />

PC120303-3 Grandparent Interstate SHNS and SST USOCs<br />

Janean Van Dusen – Qwest provided status. The final notification went out February 13. There are two effective dates with this CR.<br />

One is <strong>March</strong> 12 and the other is <strong>March</strong> 24. This CR will move to CLEC Test Status.<br />

Discussion of <strong>CMP</strong> Operations and Proposed Modifications to <strong>CMP</strong> Framework<br />

PC103003-1CM Notification of Planned Outage<br />

Jim Maher-Qwest advised we held several CLEC meetings to discuss this CR. In those meetings, Qwest had agreed to monitor the<br />

Planned Outage process during January and February. During this time the three Planned Outage notices had a 19-day advance time<br />

frame. Qwest has developed a forecast document ‘Potential Planned Outages’. This was modeled after the example that ATT provided<br />

from Verizon. The intent of this document is that Qwest would post the outage dates that they believe are potentially going to occur. The<br />

final communication would occur as defined in the current <strong>CMP</strong> <strong>Process</strong>. There was a language change requested by ATT, but ATT<br />

agreed that was not necessary. Qwest will meet a 15-day advance notification for most of the potential planned outages identified in the<br />

<strong>CMP</strong> document. There may be some emergency outages that will meet the minimum requirements identified in the <strong>CMP</strong> process.<br />

Additionally Qwest will update and post the Planned Outage Forecast calendar to the web site quarterly. Qwest requested for ATT to<br />

withdraw the CR. ATT advised they are happy with the document / calendar. Carla Pardee – ATT said she didn’t get a chance to share<br />

the final document with other CLECs due to schedule issues. ATT stated they would withdraw the CR and that they believed the other<br />

CLECs will be happy with the forecast calendar.<br />

PC112503-1CM <strong>CMP</strong> Document Language Change Section 3.0 to allow for alternative arrangements for<br />

the Change Management <strong>Process</strong> <strong>Meeting</strong>s<br />

This CR was approved at the January <strong>CMP</strong> meeting. It will carry an April 19 implementation. Status will move to complete.<br />

PC120303-1CM <strong>CMP</strong> Document Language Changes to Section 12.4 and 12.5<br />

This CR was approved at the January <strong>CMP</strong> meeting. It will carry an April 19 implementation. Status will move to complete.<br />

PC120303-2CM Changes to the <strong>CMP</strong> Document Section 12.7<br />

03/02/0402/24/04 Page 9 of 12


Qwest Wholesale Change Management <strong>Process</strong> (<strong>CMP</strong>) <strong>Meeting</strong> Minutes<br />

This CR was approved at the January <strong>CMP</strong> meeting. It will carry an April 19 implementation. Status will move to complete.<br />

PC010704-1CM Change to <strong>CMP</strong> Document, <strong>Product</strong>ion Support Section 12.3<br />

Cindy Macy – Qwest provided status that this CR was voted on and passed during an ad hoc meeting held on February 10, <strong>2004</strong>. It was<br />

agreed that this change would be implemented on April 19, <strong>2004</strong> with the 15.0 release time frame. There are three other CRs that were<br />

voted on during the January <strong>CMP</strong> meeting, and it was agreed that those CRs would also be implemented at the same time. (CR:<br />

PC112503-1CM <strong>CMP</strong> Document Language Change Section 3.0 to allow for alternative arrangements for the Change Management<br />

<strong>Process</strong> <strong>Meeting</strong>s, PC120303-1CM <strong>CMP</strong> Document Language Changes to Section 12.4 and 12.5, PC120303-2CM Changes to the <strong>CMP</strong><br />

Document Section 12.7).<br />

None<br />

General <strong>CMP</strong> Comments:<br />

CLEC Forum Update<br />

Bonnie Johnson – Eschelon advised the CLECs met and discussed the following items:<br />

• Morning Appointment<br />

• Performance Measurements Report<br />

• Late adders on Qwest CRs<br />

• Walk on – Tickets system help desk<br />

• Batch Hot Cut CRs<br />

• Optional BAN field<br />

• CALA ordering<br />

Walk On Items<br />

CR Archive Web Site – file size issues<br />

Bonnie Johnson – Eschelon explained that when they use the CR Archive file their computer locks up due to so much data. When she<br />

was searching using the word ‘escalation’ it stopped on page 3 and wouldn’t go past that. Bonnie said she didn’t have to reboot but she<br />

had to close the window and start over. Bonnie asked Cindy Macy – Qwest if she was able to recreate this. Cindy Macy – Qwest replied<br />

she wasn’t able to recreate the exact situation, but the file is large and it is slow when you use the ‘find’ command (comment begin from<br />

Eschelon) and Cindy had the same problem (comment end from Eschelon). Bonnie asked if we could improve this situation. Bonnie<br />

asked if the file gets duplicated when you are doing ‘finds’ or does it just search the file? Qwest replied that the file does not get<br />

duplicated on your machine. Kit Thomte – Qwest asked if Bonnie knows the CR number when she is searching? Bonnie advised not<br />

always. Judy Schultz – Qwest advised that we could take a look at the file and make a suggestion on how to break it up. ATT advised<br />

they are not aware of this problem. Bonnie advised they use the archive web site quite a bit and this just recently started happening. The<br />

suggestion was made to split the file and close out 2001 and 2002 CRs, or create separate reports. Qwest agreed to take an action item to<br />

look into this.<br />

Next <strong>Meeting</strong> Schedule<br />

<strong>March</strong> <strong>Product</strong> and <strong>Process</strong> <strong>CMP</strong> <strong>Meeting</strong> – <strong>March</strong> 17, <strong>2004</strong> to be held at 1005 17 th Street, Room 180<br />

03/02/0402/24/04 Page 10 of 12


Qwest Wholesale Change Management <strong>Process</strong> (<strong>CMP</strong>) <strong>Meeting</strong> Minutes<br />

<strong>CMP</strong> <strong>Meeting</strong> Attendee List<br />

February <strong>2004</strong> Monthly <strong>Product</strong> & <strong>Process</strong> <strong>CMP</strong> <strong>Meeting</strong> Wednesday, February 18, <strong>2004</strong><br />

Company Name Full Name Attendance Phone Number E-mail address POC Type<br />

Accenture McCluskey, James On Phone (612) 277-4632 James.f.mccluskey@accent Primary<br />

Allegiance Mendoza, Lori On Phone (425) 888-8585 lori.mendoza@algx.com Primary<br />

AT&T Burt, Phyllis On Phone (999) 999-9999 POC Data Unpublished<br />

AT&T Mosley, Regina On Phone (732) 457-5873 rdmosley@att.com<br />

AT&T Osborne-Miller, Donna In Person (303) 298-6178 dosborne@att.com Primary<br />

AT&T Pardee, Carla In Person (303) 298-6101 cdickinson@att.com Secondary<br />

Cbeyond Calhoun, Stephan On Phone (999) 999-9999 POC Data Unpublished<br />

COPUC Quintana, Becky On Phone (999) 999-9999 POC Data Unpublished Primary<br />

Eschelon Issacs, Kim On Phone (612) 436-6038 kdisaacs@eschelon.com<br />

Eschelon Johnson, Bonnie On Phone (612) 436-6218 bjjohnson@eschelon.com Primary<br />

Eschelon Prull, Stephanie On Phone (612) 436-6058 saprull@eschelon.com<br />

Eschelon Stichter, Kathy On Phone (612) 436-6022 klstichter@eschelon.com<br />

Qwest Communications Andreen, Doug In Person (303) 382-5777 douglas.andreen@qwest.c<br />

Qwest Communications Bliss, Susie In Person (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Boudhaouia, Jamal On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Bratetic, Pat On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Coyne, Mark On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Davis, Qiana On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Dimmitt, Jan On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Finley, Pat On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Foster, Beth In Person (303) 624-1305 beth.foster@qwest.com<br />

Qwest Communications Gonzales, Mark In Person (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Kast, Steven In Person (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Kirves, Kyle On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Kriebel, Sue On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Lorence, Susan On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Macy, Cindy In Person (303) 382-5765 Cynthia.Macy@qwest.com<br />

Qwest Communications Maher, Jim In Person (303) 382-5766 Jim.Maher@qwest.com<br />

Qwest Communications Martain, Jill On Phone (801) 239-4159 jill.martain@qwest.com<br />

Qwest Communications Martinez, Denise On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications McGhghy, Laura On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Miles, Linda On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Moreland, Heidi On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Nelson, Steve On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Owen, Randy On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Peterson, Lydell In Person (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Recker, Jim On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Robberson, Anne On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Sanchez-Steinke, Linda In Person (303) 382-5768 Linda.SanchezSteinke<br />

Qwest Communications Schultz, Judy In Person (303) 382-5769 Judy.Schultz@qwest.com Primary<br />

Qwest Communications Sunins, Phyllis On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Tallman, Shirley On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Thacker, Michelle On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Thomte, Kit In Person (303) 382-5772 Kit.Thomte@qwest.com Secondary<br />

Qwest Communications Tolman, Don On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Urevig, Russell On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Van Dusen, Janean On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Washington, Anthony On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Williams, David On Phone (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Winston, Connie In Person (999) 999-9999 POC Data Unpublished<br />

Qwest Communications Yohe, Eric On Phone (999) 999-9999 POC Data Unpublished<br />

USLink Arnold, Jennifer On Phone (218) 568-2647 jennifer.arnold@uslink.co Primary<br />

03/02/0402/24/04 Page 11 of 12


Qwest Wholesale Change Management <strong>Process</strong> (<strong>CMP</strong>) <strong>Meeting</strong> Minutes<br />

Company Name Full Name Attendance Phone Number E-mail address POC Type<br />

The information contained in this report is based upon <strong>CMP</strong> Point of Contact (POC) data for <strong>CMP</strong> Monthly <strong>Meeting</strong> attendees<br />

who announce themselves on the bridge or who sign in on the <strong>CMP</strong> <strong>Meeting</strong> Attendance List.<br />

Complete <strong>CMP</strong> Point of Contact (POC) information can be viewed in the POC reports available at<br />

http://www.qwest.com/wholesale/cmp/poc.html<br />

Updates to POC information (e.g. Phone Number, e-mail address, etc) can be made online at<br />

http://www.qwest.com/wholesale/cmp/ppform.html<br />

Report generated: 2/23/04 3:49:30 PM<br />

03/02/0402/24/04 Page 12 of 12


<strong>Product</strong> & <strong>Process</strong> Change Management <strong>Process</strong><br />

Attachment B – Global Action Items<br />

3/12/04 © <strong>2004</strong>, Qwest Corporation 5


Summary - Change Management <strong>Process</strong> (<strong>CMP</strong>) - <strong>Product</strong> & <strong>Process</strong> Action Items<br />

Report Line<br />

Number<br />

Action Item # Title Originator Current Status Owner CR PM<br />

1 AI012104-1 Binding Post information on Non Design Orders<br />

Qwest Open Tallman, Andreen, Doug<br />

Communication<br />

s<br />

Shirley<br />

2 AI021804-1 I believe the CR archive web site has grown so large that I am no longer Eschelon Submitted Andreen, Andreen, Doug<br />

able to use the acrobat find or print pages I need. Can you reduce the size<br />

using some criteria?<br />

Doug<br />

3 AI071603-1 Will Qwest offer CLECs a process to grant blanket approval for DSL<br />

Covad Open Buckmaster, Thomte, Kit<br />

Conditioning.<br />

Cindy<br />

4 AI111903-1 Construction Definition and Charges Review<br />

Covad Open Boudhaouia, Sanchez-Steinke,<br />

Jamal Linda<br />

Information Current as of: Friday, <strong>March</strong> 12, <strong>2004</strong> Page 1 of 1<br />

Report Name: 001 ProdProc OF FINAL ActionItem Summary ATTACH B<br />

Attachment B


Open <strong>Product</strong>/<strong>Process</strong> CR Detail<br />

CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

AI012104-1 Binding Post information on Non Design<br />

Orders<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc<br />

For non design orders how should the CLECs obtain binding post information. Associated CR PC103103-2 Binding Post Information (specifically<br />

for design orders)<br />

Status History<br />

Retka, Mary<br />

Andreen, Doug<br />

Tallman, Shirley<br />

Andreen, Doug<br />

Open<br />

1/23/04<br />

Originator Company Name:<br />

01-23-04 Action Item Opened<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Report Line Number<br />

Qwest Communications<br />

<strong>Product</strong>s<br />

Impacted<br />

Project <strong>Meeting</strong>s<br />

2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Doug Andreen, Qwest stated that this action item continues to move forward to find the best solution for all parties. Two meetings were held in the<br />

past month.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

002 ProdProc OF FINAL ActionItem Detail ATTACH B<br />

CR #<br />

AI012104-1<br />

Page 1 of 5<br />

Attachment B<br />

1


Open <strong>Product</strong>/<strong>Process</strong> CR Detail<br />

CR # Title Date Organization Area<br />

Current Status<br />

Impacted<br />

AI021804-1 I believe the CR archive web site has grown<br />

so large that I am no longer<br />

able to use the acrobat find or print pages I<br />

need. Can you reduce the size<br />

using some criteria?<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Status History<br />

Wholesale ProdProc<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Project <strong>Meeting</strong>s<br />

Bliss, Susie<br />

Johnson, Bonnie<br />

Andreen, Doug<br />

Andreen, Doug<br />

Submitted<br />

3/4/04<br />

Report Line Number<br />

<strong>Product</strong>s<br />

Impacted<br />

2/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Bonnie Johnson – Eschelon explained that when they use the CR Archive file their computer locks up due to so much data. When she was<br />

searching using the word ‘escalation’ it stopped on page 3 and wouldn’t go past that. Bonnie said she didn’t have to reboot but she had to<br />

close the window and start over. Bonnie asked Cindy Macy – Qwest if she was able to recreate this. Cindy Macy – Qwest replied she wasn’t<br />

able to recreate the exact situation, but the file is large and it is slow when you use the ‘find’ command (comment begin from Eschelon) and<br />

Cindy had the same problem (comment end from Eschelon). Bonnie asked if we could improve this situation. Bonnie asked if the file gets<br />

duplicated when you are doing ‘finds’ or does it just search the file? Qwest replied that the file does not get duplicated on your machine. Kit<br />

Thomte – Qwest asked if Bonnie knows the CR number when she is searching? Bonnie advised not always. Judy Schultz – Qwest advised<br />

that we could take a look at the file and make a suggestion on how to break it up. ATT advised they are not aware of this problem. Bonnie<br />

advised they use the archive web site quite a bit and this just recently started happening. The suggestion was made to split the file and close<br />

out 2001 and 2002 CRs, or create separate reports. Qwest agreed to take an action item to look into this.<br />

Information Current as of:<br />

Report Name:<br />

Originator Company Name:<br />

Eschelon<br />

Friday, <strong>March</strong> 12, <strong>2004</strong> Page 1 of 1<br />

rptOpenDetailed CR INDIVIDUAL REPORT prodproc<br />

CR #<br />

1<br />

AI021804-1


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

AI071603-1 Will Qwest offer CLECs a process to grant<br />

blanket approval for DSL Conditioning.<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Campbell, Bill<br />

Wholesale ProdProc<br />

Description Of Change<br />

This Action Item is a spin-off of PC022403-2. Covad seeks to understand if Qwest will offer a process under which CLECs can grant Qwest<br />

blanket authorization to automatically conduct Load Coil and Bridged Tap Removal.<br />

Project <strong>Meeting</strong>s<br />

<strong>CMP</strong> <strong>Meeting</strong>11-19-03<br />

Zulevic, Michael<br />

Buckmaster, Cindy<br />

Thomte, Kit<br />

Open<br />

7/16/03<br />

Originator Company Name:<br />

Report Line Number<br />

<strong>Product</strong>s<br />

Impacted<br />

Cindy Buckmaster Qwest stated that this project will remain an open action item until spring (April <strong>2004</strong>) until additional system work is completed.<br />

---------------------------------------------------------------------<br />

<strong>CMP</strong> <strong>Meeting</strong> 08-20-03<br />

White-Qwest stated that Qwest had agreed to re-look this action item following implementation of the DSL Footprint Expansion project. He stated<br />

that this project was not yet finished.<br />

Information Current as of:<br />

Report Name:<br />

Covad<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

002 ProdProc OF FINAL ActionItem Detail ATTACH B<br />

CR #<br />

AI071603-1<br />

Page 3 of 5<br />

Attachment B<br />

3


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

AI111903-1 Construction Definition and Charges Review Open Wholesale ProdProc Provisioning UNE's<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Qwest has agreed to review the current retail tariffs in conjunction with the definition of Construction based on the TRO Requirements. This action<br />

item has been opened as a result of denied CR PC071403-1.<br />

Status History<br />

Retka, Mary<br />

Berard, John<br />

Boudhaouia, Jamal<br />

Sanchez-Steinke, Linda<br />

11/19/03<br />

Originator Company Name:<br />

11/19/03 - Action Item opened to track review construction definition and charges in retail tariffs<br />

12/17/03 - December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

01/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Project <strong>Meeting</strong>s<br />

02/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Jamal Boudhaouia with Qwest said that Network modifications would be available in mid-<strong>March</strong> for review. The TRO will determine the<br />

requirements for construction, which will drive the QPF fee. Bonnie Johnson with Eschelon asked when documentation would be available for<br />

review. Jamal responded that documentation will be available in mid-<strong>March</strong>. This action item will remain open.<br />

______________________<br />

1/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Jamal Boudhaouia with Qwest said that this action item would be open until the definition of construction as it relates to TRO is completed. The<br />

TRO requires that Retail and Wholesale criteria for building facilities be treated the same. If there are three DS1s required for a route, the criteria<br />

for building facilities would consider Wholesale and Retail customer orders the same; both would be included in the same bucket. Wholesale<br />

customers are able to purchase services from the retail tariff if they would like to have construction charges the same as retail.<br />

Bonnie Johnson with Eschelon said that the estimate is given to retail customers without paying the Quote Preparation Fee up front. Bonnie asked<br />

if the processes for retail construction and the quote fee are paid up front for retail customers.<br />

Jamal said that the Quote Preparation Fee is not the same, and is not treated the same because Retail and Wholesale have different tariffs based<br />

on the cost recovery mechanism approved by the state commissions for either side. For Wholesale, the QPF recovers the cost of what is<br />

required to develop the estimate for the job that will be required to provide the facilities. The Retail tariffs were agreed to by the State PUCs and<br />

spread cost recovery mechanism projections. In Wholesale the QPF paid up front will be subtracted from the total cost of the project if the CLEC<br />

elects to move forward with the construction job.<br />

Mike Zulevic with Covad said that this is an issue of parity and creates a barrier for the CLEC to serve their customers.<br />

Bonnie said that Wholesale customers are out the QPF (Begin comment from Bonnie Johnson – Eschelon) if they get a quote and do not move<br />

forward (end comment), but Retail customers are not out the QPF if they do not wish for Qwest to construct facilities. Jamal said that the QPF is<br />

charged to CLECs in order for Qwest to be paid for work that has been performed. The risk with Retail customers is not as high because they<br />

provide more revenue and Qwest is recovering expenses from Retail based on the tariffs.<br />

Mike Zulevic asked if Qwest has finished the review. Jamal said Qwest is still reviewing the definition of construction from the TRO. Based on the<br />

new definition of construction from the TRO, the QPF may be lowered. Mike said that he hopes that new definitions will be incorporated into the<br />

QPF and the TRO identifies the true costs identified for construction. Jamal said that Wholesale could purchase from the retail tariff.<br />

Bonnie asked if the Qwest position right now is that Retail and Wholesale are in parity. Jamal answered yes.<br />

Report Line Number<br />

<strong>Product</strong>s<br />

Impacted<br />

Liz Balvin with MCI stated that the retail tariff has a higher rate, but Wholesale has the fee up front, which will be included in the total cost of the<br />

project. Jamal said that retail will be charged whatever the job costs, and Wholesale can purchase from the Retail tariff. Liz said she thought for<br />

Wholesale the QPF must be paid. Jamal said if purchased through Wholesale, then the QPF is charged.<br />

Mike Zulevic said that the QPF allows Qwest to recover costs for providing that construction and Qwest does engineering and gives an estimate<br />

back. If the CLEC wants Qwest to do the construction then the QPF is subtracted from the total cost of the project. For Retail they are not<br />

charged the QPF upfront.<br />

This action item will remain open and Jamal will provide an update at the February meeting.<br />

____________________________<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Jamal Boudhaouia with Qwest said that Qwest is reviewing the retail tariffs. Bonnie Johnson with Eschelon asked what Qwest is reviewing. Jamal<br />

Information Current as of:<br />

Report Name:<br />

Covad<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

002 ProdProc OF FINAL ActionItem Detail ATTACH B<br />

CR #<br />

AI111903-1<br />

Page 4 of 5<br />

Attachment B<br />

4


said that Qwest is reviewing the retail tariffs to determine how construction charges apply when a retail customer orders service and there are no<br />

facilities. Bonnie Johnson said that in the Covad change request that Qwest provides estimates to retail but not to Wholesale. Will this determine<br />

whether or not to bring retail in parity with Wholesale. Jamal said Qwest is reviewing how today Wholesale vs. Retail is charged and there is an<br />

obligation to do for Wholesale and align Wholesale with Retail. Bonnie Johnson said that in comparing the process, should determine if Wholesale<br />

and Retail are out of sync. Jamal said modification of tariffs may be needed. John Berard with Covad asked if this would preclude a changing of<br />

the process on the Wholesale side. Jamal answered that it doesn’t preclude anything because of legal obligations on both Retail and Wholesale<br />

side. John asked the timeline for Qwest to have information. Jamal said that he hopes to have information next month. John stated we would like<br />

the deliverable to be state by state what the differences are between Wholesale and Retail. Jamal said he would look at alignment of Wholesale<br />

vs. Retail side. Judy Schultz said that by the January meeting we would like to have Qwest’s response so this AI can be closed. Jamal agreed to<br />

provide the information or a date when the information will be provided.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

002 ProdProc OF FINAL ActionItem Detail ATTACH B<br />

CR #<br />

AI111903-1<br />

Page 5 of 5<br />

Attachment B


<strong>Product</strong> & <strong>Process</strong> Change Management <strong>Process</strong><br />

Attachment C – CLEC CR Summary Report<br />

3/12/04 © <strong>2004</strong>, Qwest Corporation 6


Summary - Change Management <strong>Process</strong> (<strong>CMP</strong>) - <strong>Product</strong> & <strong>Process</strong><br />

CLEC Initiated CRs<br />

Report Line<br />

Number<br />

CR # Title Company Current Status Owner Director CR PM<br />

1 PC011604-1 All Joint Maintenance and Trouble Isolation Documentation Covad Presented Graham, Retka, Mary Andreen, Doug<br />

be placed in the same location on the Qwest Web Site<br />

Denny<br />

2 PC01<strong>2004</strong>-1 Include escalation ticket detail along with the monthly Eschelon Presented Thacker, Huff, Loretta Sanchez-Steinke,<br />

escalation ticket report or create a separate report to<br />

provide the detail.<br />

Michelle<br />

Linda<br />

3 PC021904-1 Enhancement to existing Expedite <strong>Process</strong> for Provisioning Covad Clarification Martain, Jill Bliss, Susie Macy, Cindy<br />

4 PC022304-1 Develop a web based electronic interface to enter and<br />

maintain the New Customer Questionnaire<br />

Eschelon Clarification Lewis, Judy Hinkins, Ryan Andreen, Doug<br />

5 PC030204-1 Qwest to develop and implement a Directory Assistance<br />

only block.<br />

Eschelon Clarification foster, sandy Lynch, Randall Andreen, Doug<br />

6 PC062603-03 Business Rules Clarificaiton calls and event notification AT&T Development Winston, Winston, Sanchez-Steinke,<br />

updates through the Addendum processs<br />

Connie Connie Linda<br />

7 PC102803-1 Improve Search Functionality of the Qwest Wholesale Eschelon Evaluation Blackmun, McNa, Sue Andreen, Doug<br />

Website to minimize selections<br />

Jarby<br />

8 PC110403-1 Update accuracy of FAM records AT&T Evaluation Winston, Winston, Macy, Cindy<br />

Connie Connie<br />

9 PC111303-1 Allow multiple Billing Account Numbers Per <strong>Product</strong> Per<br />

State<br />

MCI<br />

Development Kriebel, Sue Burson, Sue Andreen, Doug<br />

10 PC111903-1 Website for Event Notifiers AT&T Evaluation Owen, Randy Winston,<br />

Connie<br />

Macy, Cindy<br />

11 PC112003-1 Differentiate between Loop-MUX combos and EELs due to Cbeyond Evaluation Finley, Pat Campbell, Bill Sanchez-Steinke,<br />

different FCC treatment (TRO Order)<br />

Communication<br />

s<br />

Linda<br />

Information Current as of: Friday, <strong>March</strong> 12, <strong>2004</strong> Page 1 of 3<br />

Report Name: 003 Summary CLEC Initiated FINAL ATTACH C<br />

Attachment C


Report Line<br />

Number<br />

CR # Title Company Current Status Owner Director CR PM<br />

12 PC120803-1 Associated Move Orders AT&T Evaluation Davis, Qiana Schultz, Judy Sanchez-Steinke,<br />

Linda<br />

13 PC120903-1 Qwest will track "access required" information in its<br />

systems when Qwest installs new service, or when Qwest<br />

dispatches on the repair of an existing line/circuit. Qwest<br />

will make the information available to CLECs for use when<br />

a CLEC opens arepair ticket<br />

Eschelon Evaluation Tolman, Don Diebel, Diane Andreen, Doug<br />

14 PC031103-1 Convert Common Area Splitter Collocation to Cageless Covad Development Williams, Campbell, Bill Sanchez-Steinke,<br />

Shelf at a time Collocation<br />

David<br />

Linda<br />

15 PC042103-1 Tracking process for FBDL order issues. McLeodUSA Development Gomez, Lee Townley, Robin Sanchez-Steinke,<br />

Linda<br />

16 PC050703-1 Change Qwest Wholesale <strong>CMP</strong> Website to make it easier<br />

to search, retrieve and view CRs.<br />

AT&T Development Thomte, Kit Schultz, Judy Thomte, Kit<br />

17 PC051403-4 Sync Test for Loop Splitting on Maintenance Trouble Covad Development Moreland, Retka, Mary Sanchez-Steinke,<br />

Tickets and Sync Testing for provisioning of Loop Splitting<br />

Heidi<br />

Linda<br />

18 PC061103-1ES Intercept CLEC customer calls to Qwest Repair Center AT&T Development Boudhaouia, Retka, Mary Sanchez-Steinke,<br />

Jamal<br />

Linda<br />

19 PC070103-1 Provide "Lines In Service Report" to CLECs MCI<br />

Development Mcghghy, Staebell, Todd Sanchez-Steinke,<br />

Laua D.<br />

Linda<br />

20 PC070103-3 DSL Volume provider and data migration process to Eschelon Development<br />

Campbell, Bill Sanchez-Steinke,<br />

prevent extended DSL outage<br />

Linda<br />

21 PC081403-1 Jeopardy Notification <strong>Process</strong> Changes (new title). Eschelon Development Sunins, Schultz, Judy Macy, Cindy<br />

Delayed order process modifed to allow theCLEC a<br />

designated time frame to respond to a released delayed<br />

order after Qwest sends an updated FOC (old title).<br />

Phyllis<br />

22 PC081403-2 Workback process/products expanded to include additional<br />

products and allow partial workbacks. Qwest will post the<br />

process and products included in the Business Procedure<br />

section of the web site.<br />

Eschelon Development Wells, Joan Bliss, Susie Macy, Cindy<br />

23 PC092903-1 Joint Inventory <strong>Process</strong> (previous name: New Collocation AT&T Development Nelson, Campbell, Bill Macy, Cindy<br />

<strong>Process</strong>)<br />

Steve<br />

Information Current as of: Friday, <strong>March</strong> 12, <strong>2004</strong> Page 2 of 3<br />

Report Name: 003 Summary CLEC Initiated FINAL ATTACH C<br />

Attachment C


Report Line<br />

Number<br />

CR # Title Company Current Status Owner Director CR PM<br />

24 PC102303-1 10,000 lines billed on Summary BANs before opening a<br />

new Summary BAN.<br />

Eschelon Development Kriebel, Sue Burson, Sue Andreen, Doug<br />

25 PC030204-2 Qwest will red line and provide the changes made to the<br />

SGAT, Amendments and Negotiation Template in its<br />

<strong>Process</strong> notices.<br />

Eschelon Submitted Houston, Neil Retka, Mary Macy, Cindy<br />

Information Current as of: Friday, <strong>March</strong> 12, <strong>2004</strong> Page 3 of 3<br />

Report Name: 003 Summary CLEC Initiated FINAL ATTACH C<br />

Attachment C


<strong>Product</strong> & <strong>Process</strong> Change Management <strong>Process</strong><br />

Attachment D – CLEC CR Detailed Reports<br />

3/12/04 © <strong>2004</strong>, Qwest Corporation


Open <strong>Product</strong>/<strong>Process</strong> CR Detail<br />

CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC011604-1 All Joint Maintenance and Trouble Isolation<br />

Documentation be placed in the same<br />

location on the Qwest Web Site<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Web Site<br />

Covad requests that joint maintenance and trouble isolation be placed in the same location on the Qwest web site. This would include wiring<br />

diagrams for connecting DS1/3 circuits on their ICDF, number conversion chart for splitters located in the common area, splitter card RMA<br />

process, process for strapping out defective data lines that impair voice, synch testing for new services, synch testing for trouble isolation, etc.<br />

Covad believes that this will assist both the Qwest and Covad operations technicians in insuring that the proper processes are being followed.<br />

Expected Deliverable: As Soon as Possible<br />

Status History<br />

01/16/04 - CR Submitted<br />

01/16/04 - CR Acknowledged<br />

1/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

1/21/04 - Status will remain in Submitted<br />

2/11/04 - Held Clarification call<br />

2/17/04 - Sent clarification call minutes<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

2/18/04 - Status changed to Presented<br />

Project <strong>Meeting</strong>s<br />

Retka, Mary<br />

Berard, John<br />

Graham, Denny<br />

Andreen, Doug<br />

2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

This was a walk-on CR by Covad in January. Doug Andreen, Qwest in John Berard’s absence stated that a Clarification call was held and the<br />

intent of the CR is to provide a method of easy access to documentation that the Qwest and CLECs technicians commonly use in trouble isolation<br />

and maintenance work. The CR calls for the documentation to be located or accessible from a common point on the web. Jim Recker, Qwest<br />

added that John would provide us with examples of processes Covad now uses to find the documentation. This CR will be moved to Presented<br />

status.<br />

----------------------------------------------------------------------------------------<br />

CLEC Change Request<br />

Clarification <strong>Meeting</strong><br />

2:30 p.m. (MDT) / Wednesday February 11, <strong>2004</strong><br />

1-877-521-8688<br />

1456160#<br />

PC011604-1 All Joint Maintenance and Trouble Isolation Documentation be placed in the same location on the Qwest Web Site<br />

Attendees<br />

John Berard, Covad<br />

Liz Balvin, MCI<br />

Kim Isaacs, Eschelon<br />

Jim Recker, Qwest<br />

Mike Johnson, Qwest<br />

Alice Matthews, Qwest<br />

Doug Andreen, Qwest<br />

Jarby Blackmun, Qwest<br />

Presented<br />

2/18/04<br />

Originator Company Name:<br />

Introduction of Attendees<br />

Introduction of participants on the conference call was made and the purpose of the call discussed.<br />

Report Line Number<br />

<strong>Product</strong>s<br />

Impacted<br />

Review Requested (Description of) Change<br />

Doug read and reviewed the CR. Covad requests that joint maintenance and trouble isolation be placed in the same location on the Qwest web<br />

site. This would include wiring diagrams for connecting DS1/3 circuits on their ICDF, number conversion chart for splitters located in the common<br />

area, splitter card RMA process, process for strapping out defective data lines that impair voice, synch testing for new services, synch testing for<br />

trouble isolation, etc. Covad believes that this will assist both the Qwest and Covad operations technicians in insuring that the proper processes<br />

are being followed.<br />

John Berard, Covad added that the request came from their technicans. He also wanted to add two items to the list of documentation ie. The<br />

Qwest Test Point Documents and the MOP form.<br />

Information Current as of: Friday, <strong>March</strong> 12, <strong>2004</strong><br />

CR # PC011604-1<br />

Report Name: 004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Page 1 of 105<br />

Covad<br />

1<br />

Attachment D


Mike Johnson, Qwest asked if all documents have been identified.<br />

John answered with the two additions and the documents on the CR that all have been.<br />

Doug Andreen, wanted to clarify that no change in any document is needed but they just need to somehow be located together on the web. John<br />

indicated that was correct.<br />

John further stated that using a table to link to the documents current locations would be acceptable.<br />

Jim Recker, Qwest brought up that we would need to find out how the documents are being arranged today and their current locations.<br />

Mike asked if there was a time frame for this CR. John answered no but as soon as reasonably possible.<br />

Jim asked how Covad technicians located the documents today.<br />

John said that a lot of the time the technician would call his office. He will then try to get in the correct section and then do a search.<br />

Jim asked if he could provide an example. John said he would email an example to Doug for distribution to the group.<br />

Jim questioned if what John was interested was sort of a front door.<br />

John replied that would work.<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

Documentation placement on web.<br />

Confirm Right Personnel Involved<br />

Correct personnel were involved in the meeting.<br />

Identify/Confirm CLEC’s Expectation<br />

Implementation to be as soon as possible<br />

Identify any Dependent Systems Change Requests<br />

None<br />

Establish Action Plan (Resolution Time Frame)<br />

John will present the CR for Covad at the February <strong>CMP</strong> meeting. The response will be due at the <strong>March</strong> meeting.<br />

-----------------------------------------------------------------<br />

1/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Mike Zulevic, Covad walked-on this CR which calls for the placement of all documentation used by technicians in a common location on the Web.<br />

He said most of the documentation is available but is located in several different locations. He is calling for a grouping perhaps by process or a<br />

functional grouping for the technician. Examples of the type of documentation would be demarc information, DS1-3 ICDFs and how they are wired<br />

out, blank form for MOP etc.<br />

Qwest Response<br />

<strong>March</strong> 9, <strong>2004</strong><br />

For Review by the CLEC community and discussion at the <strong>March</strong> 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

John Berard<br />

Covad<br />

SUBJECT: Qwest’s Change Request Response - CR PC011604-1<br />

"All Joint Maintenance and Trouble Isolation Documentation be placed<br />

in the same location on the Qwest Web Site"<br />

This CR as submitted by Covad requests that joint maintenance and trouble isolation be placed in the same location on the Qwest web site. This<br />

would include wiring diagrams for connecting DS1/3 circuits on their ICDF, number conversion chart for splitters located in the common area,<br />

splitter card RMA process, process for strapping out defective data lines that impair voice, synch testing for new services, synch testing for trouble<br />

isolation, etc. Covad believes that this will assist both the Qwest and Covad operations technicians in insuring that the proper processes are being<br />

followed.<br />

Qwest is evaluating this request in cooperation with Covad. Qwest is awaiting a response from John Berard in answer to a request from Qwest for<br />

examples of Covad’s current process to access this information. With this input Qwest can compare the Qwest <strong>Process</strong>es and the Covad<br />

processes to determine the feasibility of providing this request.<br />

At this time the CR is still in the clarification stage. Upon receipt of the Covad process, Qwest will move the CR into the Evaluation status.<br />

Sincerely,<br />

Denny Graham<br />

Staff Advocate, Policy & Law<br />

Qwest<br />

Cc: Mary Retka, Director-Legal Issues, Qwest<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC011604-1<br />

Page 2 of 105<br />

Attachment D


Catherine R. Garcia, Lead <strong>Process</strong> Analyst, Qwest<br />

Cheryl Rock, Senior <strong>Process</strong> Analyst, Qwest<br />

________________<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC011604-1<br />

Page 3 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC01<strong>2004</strong>-1 Include escalation ticket detail along with the<br />

monthly escalation ticket report or create a<br />

separate report to provide the detail.<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Pre-Ordering,<br />

Ordering, Billing<br />

Include escalation ticket detail along with the monthly escalation ticket report or create a separate report to provide the detail. The detail should<br />

include: (when applicable) escalation ticket number, date received, caller name, caller call back TN, PON, LSR ID, product, complete date, reason<br />

for call (code opened under), service order number, remarks, closing code, closing sub code. The customer name and TN optional. Qwest has<br />

provided this information to Eschelon before and has this detail.<br />

The detail should include: (when applicable) escalation ticket number, date received, caller name, caller call back TN, PON, LSR ID, product,<br />

complete date, reason for call (code opened under), service order number, remarks, closing code, closing sub code. The customer name and TN<br />

optional. Qwest has provided this information to Eschelon before and has this detail.<br />

Expected Deliverable:<br />

Include escalation ticket detail with the monthly escalation ticket report or develop a new report to provide the detail separate from the existing<br />

report Qwest provides to the CLEC.<br />

Status History<br />

01/20/04 - CR Submitted<br />

01/22/04 - CR Acknowledged<br />

02/04/04 - Held Clarification <strong>Meeting</strong><br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Project <strong>Meeting</strong>s<br />

Huff, Loretta<br />

Johnson, Bonnie<br />

Thacker, Michelle<br />

Sanchez-Steinke, Linda<br />

02/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Bonnie Johnson with Eschelon presented this CR. Bonnie said this is an extension to the CR just closed and this CR asks for more detail than the<br />

report currently provides. Eschelon’s service manager has provided a report that included the level of detail required to address Eschelon’s<br />

training needs. This CR will be moved to Presented status.<br />

_____________________<br />

CLEC Change Request<br />

Clarification <strong>Meeting</strong><br />

1:00 p.m. (MDT) / Tuesday February 3, <strong>2004</strong><br />

1-877-572-8687<br />

3393947#<br />

PC01<strong>2004</strong>-1 Include escalation ticket detail along with the monthly escalation ticket report or create a separate report to provide the detail.<br />

Name/Company:<br />

Bonnie Johnson, Eschelon<br />

Kim Isaacs, Eschelon<br />

Michelle Thacker, Qwest<br />

Linda Sanchez-Steinke, Qwest<br />

Introduction of Attendees<br />

Qwest welcomed all attendees to the meeting.<br />

Review Requested (Description of) Change<br />

Presented<br />

2/18/04<br />

Originator Company Name:<br />

Eschelon<br />

Report Line Number<br />

Linda Sanchez-Steinke with Qwest read the description of change; Include escalation ticket detail along with the monthly escalation ticket report or<br />

create a separate report to provide the detail. The detail should include: (when applicable) escalation ticket number, date received, caller name,<br />

caller call back TN, PON, LSR ID, product, complete date, reason for call (code opened under), service order number, remarks, closing code,<br />

closing sub code. The customer name and TN optional. Qwest has provided this information to Eschelon before and has this detail.<br />

The detail should include: (when applicable) escalation ticket number, date received, caller name, caller call back TN, PON, LSR ID, product,<br />

complete date, reason for call (code opened under), service order number, remarks, closing code, closing sub code. The customer name and TN<br />

optional. Qwest has provided this information to Eschelon before and has this detail.<br />

Expected Deliverable: Include escalation ticket detail with the monthly escalation ticket report or develop a new report to provide the detail<br />

separate from the existing report Qwest provides to the CLEC.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

2<br />

<strong>Product</strong>s<br />

Impacted<br />

PC01<strong>2004</strong>-1<br />

Page 4 of 105<br />

Attachment D


Bonnie Johnson with Eschelon said that the report Jean Novak provided was for February 2003 Escalation tickets. The report provided to<br />

Eschelon in April identified a high number of calls for account ownership. After researching the calls, Eschelon made internal changes and also<br />

discovered the loss report was inaccurate. Bonnie said she is disappointed that the original report did not include detailed information and it will be<br />

helpful to have additional details in the existing report as currently Eschelon doesn’t not have details about who made the calls and what<br />

department calls are being made from. Bonnie said that the report could be provided through the existing report or through the service manager.<br />

Michelle Thacker with Qwest asked if Eschelon tracks the calls made to Qwest. Bonnie said that only one group is tracking calls and there are<br />

many departments that call Qwest.<br />

Michelle asked if Eschelon asks the SDC for critical information on the ticket such as status or <strong>Product</strong> reason code, close code and sub close<br />

code. Bonnie said that she didn’t know if all departments were requesting that information. Bonnie said that Provisioning, Maintenance and Repair<br />

departments all make calls and the Billing group fields complaints for double billing, but primarily service delivery makes the calls.<br />

Bonnie added that she is hopeful that with 14.0, information will be stored and will have the capability to search by TN which will help reduce the<br />

number of calls and will provide order number and due date.<br />

Michelle asked if Jean would be tracking calls before and after the release. Bonnie said when Qwest provided the report in April 2003, no analysis<br />

was performed, just the report was provided.<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

Pre-Ordering, Ordering, Billing<br />

Confirm Right Personnel Involved<br />

Correct Qwest personnel were involved in the clarification meeting.<br />

Identify/Confirm CLEC’s Expectation<br />

Include escalation ticket detail with the monthly escalation ticket report or develop a new report to provide the detail separate from the existing<br />

report Qwest provides to the CLEC.<br />

I<br />

dentify any Dependent Systems Change Requests<br />

None identified.<br />

Establish Action Plan (Resolution Time Frame)<br />

Eschelon will present this CR at the February <strong>CMP</strong> <strong>Meeting</strong> and Qwest will provide a response in <strong>March</strong>.<br />

Qwest Response<br />

<strong>March</strong> 9, <strong>2004</strong><br />

DRAFT RESPONSE<br />

For Review by the CLEC Community and Discussion at the <strong>March</strong> 17, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Bonnie Johnson<br />

Eschelon<br />

SUBJECT: Qwest’s Change Request Response - PC01<strong>2004</strong>-1<br />

"Include escalation ticket detail along with the monthly escalation ticket report or create a separate report to provide the detail"<br />

This letter is in response to CLEC Change Request (CR) PC01<strong>2004</strong>-1. This CR is a request by Eschelon to establish a process whereby CLECs<br />

can receive, on a monthly basis, ticket detail including (when applicable) escalation ticket number, date received, caller name, caller TN, PON,<br />

LSR ID, product, complete date, reason for call (code opened under), service order number, remarks, closing code, and closing sub code. The<br />

customer name and TN is optional.<br />

Qwest is currently evaluating this change request and propose moving this CR into Evaluation Status while a complete answer to the request is<br />

prepared.<br />

Sincerely,<br />

Michelle Thacker<br />

Sr. <strong>Process</strong> Manager<br />

Qwest<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC01<strong>2004</strong>-1<br />

Page 5 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC021904-1 Enhancement to existing Expedite <strong>Process</strong><br />

for Provisioning<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc pre order, order,<br />

provisioning<br />

UNE, Transport<br />

(including EUDIT),<br />

Loop, UNE-P, Line<br />

Covad requests that Qwest provide a formal process to expedite an order that requires an interval that is shorter than what is currently available for<br />

the product.<br />

No expected deliverable listed<br />

Updated the title as a result of the Clarification call<br />

Status History<br />

Bliss, Susie<br />

02/20/04 CR Recieved<br />

02/20/04 CR Acknowledged<br />

2/23/04 - Contacted John Berard - Covad to set up Clarification Call<br />

2/27/04 - Held Clarification call<br />

Project <strong>Meeting</strong>s<br />

Berard, John<br />

Martain, Jill<br />

Macy, Cindy<br />

Clarification <strong>Meeting</strong><br />

February 27, <strong>2004</strong><br />

1-877-552-8688 7146042#<br />

PC021904-1 Expedite <strong>Process</strong> for Provisioning – enhancements to existing process<br />

Attendees<br />

John Berard – Covad<br />

Bryan Comras – Covad<br />

Mark Gonzales – Qwest<br />

Heidi Moreland – Qwest<br />

Jill Martain - Qwest<br />

Cindy Macy – Qwest<br />

<strong>Meeting</strong> Agenda:<br />

1.0 Introduction of Attendees<br />

Attendees introduced<br />

2.0 Review Requested (Description of) Change<br />

John Berard – Covad reviewed the change request. John explained that Covad would like the title of the CR updated, as this is really a request for<br />

an enhancement to the existing expedite process. Cindy agreed to update the CR.<br />

John advised that the expedite process is limited today to certain types of orders and processes. For example, medical emergencies. We may<br />

find that it is Covad’s error that caused the customer to be disconnected. We would like to be able to get our customers restored quicker than<br />

standard interval, when it is our error. We are willing to pay for this service. Other ILECs provide this service. We would like the criteria to be<br />

expanded to allow an expedite when the CLEC makes an error.<br />

Cindy Macy – Qwest asked for an example of this happening today. John Berard – Covad and Bryan Comras – Covad advised this relates to the<br />

Jeopardy process. When Covad fails to complete the order, but we complete the work at the DMARC the customer has service, but we do not<br />

close out the records so Qwest doesn’t think the customers service is working. Qwest issued a jeopardy notice and since we didn't respond to that<br />

notice within 30 days Qwest then cancelled the orders and the service gets disconnected. Covad then goes back and resends the order, but we<br />

have to wait the standard interval and that is too long for the end user customer to wait, especially if it is a business account.<br />

John Berard – Covad advised disconnects can also happen when the end user selects migration to a new ISP provider. This isn’t as critical as the<br />

down time is usually very limited as they are hooked up to the new provider.<br />

Heidi Moreland – Qwest asked how often this happens? Bryan – Covad replied approximately 20 times per month for Qwest, or once a day on<br />

average.<br />

Bryan advised that we get faster turn around time on certain products. Heidi confirmed that Shared Loop has a shorter standard installation<br />

interval than an unbundled xDSL-capable loop. Heidi advised that thethat the customer could be disconnected when the sync test fails and the<br />

notice is not cleared. The DSLAM port is done by the CLEC and the customer is in service. If a supplement is not sent by the CLEC, and if there<br />

is no response in 30 days, then the line gets cancelled and pulled down.<br />

Covad advised it shouldn’t matter what the history or circumstances are, if we are willing to pay for the expedite.<br />

3.0 Confirm Areas & <strong>Product</strong>s Impacted<br />

Information Current as of:<br />

Report Name:<br />

Clarification<br />

2/27/04<br />

Originator Company Name:<br />

Covad<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

3<br />

<strong>Product</strong>s<br />

Impacted<br />

PC021904-1<br />

Page 6 of 105<br />

Attachment D


DSL, Line Share, Designed and DSL <strong>Product</strong>s (all products<br />

This applies to any one that was in service and has gone out of service and needs to be set back up due to Customer or end-user error.<br />

4.0 Confirm Right Personnel Involved<br />

Jill agreed to get with Joan Wells regarding the Workback / Restoral Request proces<br />

5.0 Identify/Confirm CLEC’s Expectation<br />

Covad would like the ability to pay for an Expedited due date (restoral of disconnected end user<br />

Covad would like to treat these like trouble reports and get the end user back in service in one day.<br />

6.0 Identify any Dependent Systems Change Requests<br />

PC081403-1 Work Back Restoral Reques<br />

7.0 Establish Action Plan (Resolution Time Frame)<br />

Covad will present the CR at the <strong>March</strong> <strong>CMP</strong> Meetin<br />

Qwest will provide our Response at the April <strong>CMP</strong> <strong>Meeting</strong><br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC021904-1<br />

Page 7 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC022304-1 Develop a web based electronic interface to<br />

enter and maintain the New Customer<br />

Questionnaire<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc New Customer<br />

Questionnaire<br />

Eschelon is requesting that Qwest develop a web based electronic interface to enter and maintain information on the New Customer<br />

Questionnaire. The current Word version of the New Customer Questionnaire makes viewing the current information and updating the information<br />

difficult for CLECs. Eschelon requests that this web based tool allow multiple CLEC users to view the most current CLEC profile data and allows a<br />

CLEC to update individual sections of the CLEC profile as needed. Eschelon believes a web based New Customer Questionnaire would streamline<br />

the process to make needed updates to the questionnaire saving the CLEC and Qwest time and resources<br />

Expected Deliverable:<br />

1. Create a secure web based electronic New Customer Questionnaire<br />

2. Develop questionnaire sections so only sections requiring updates will need to be submitted<br />

Status History<br />

02/23/04 - CR submitted<br />

02/25/04 - CR acknowledged<br />

03/01/04 - Held Clarification call<br />

Project <strong>Meeting</strong>s<br />

CLEC Clarification Call<br />

11:00 a.m. (MDT) / Monday <strong>March</strong> 1, <strong>2004</strong><br />

1-877-521-8688<br />

1456160#<br />

PC022304-1 Develop a web based electronic interface to enter and maintain the New Customer Questionnaire<br />

Attendees<br />

*** Attended Conference Call Name/Company:<br />

Kim Isaacs, Eschelon<br />

Bonnie Johnson, Eschelon<br />

Doug Andreen, Qwest<br />

Judy Lewis, Qwest<br />

Carrie Bell, Qwest<br />

Jennifer Beach, Qwest<br />

Ryan Hinkins, Qwest<br />

<strong>Meeting</strong> Agenda:<br />

Hinkins, Ryan<br />

Isaacs, Kim<br />

Lewis, Judy<br />

Andreen, Doug<br />

Clarification<br />

2/25/04<br />

Originator Company Name:<br />

1.0 Introduction of Attendees<br />

Introduction of participants on the conference call was made and the purpose of the call discussed.<br />

2.0 Review Requested (Description of) Change<br />

Doug read the CR description: Eschelon is requesting that Qwest develop a web based electronic interface to enter and maintain information on<br />

the New Customer Questionnaire. The current Word version of the New Customer Questionnaire makes viewing the current information and<br />

updating the information difficult for CLECs. Eschelon requests that this web-based tool allows multiple CLEC users to view the most current<br />

CLEC profile data and allow a CLEC to update individual sections of the CLEC profile as needed. Eschelon believes a web based New Customer<br />

Questionnaire would streamline the process to make needed updates to the questionnaire saving the CLEC and Qwest time and resources. The<br />

expected deliverables are to create a secure web based electronic New Customer Questionnaire and Develop questionnaire sections so only<br />

sections requiring updates will need to be submitted.<br />

Kim Isaacs, Eschelon added that recently she needed to update both the Qwest questionnaire and the SBC GUI profile and found it much easier to<br />

update the SBC GUI. She feels that we would also get more accurate information from an on-line version. It would also save time and resources<br />

for both Qwest and the CLECs.<br />

Bonnie Johnson, Eschelon said that this used to be a frequent topic of conversation in the <strong>CMP</strong> meetings and that the CLECs were told quite<br />

some time ago that Qwest had started work. So there may be some work already done.<br />

Doug Andreen, Qwest stated that Qwest would look into any work that had been started.<br />

Information Current as of:<br />

Report Name:<br />

Eschelon<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

4<br />

<strong>Product</strong>s<br />

Impacted<br />

PC022304-1<br />

Page 8 of 105<br />

Attachment D


Jennifer Beach, Qwest asked if the amendments should also be added to the questionnaire.<br />

Bonnie Johnson answered yes after Judy Lewis, Qwest clarified that we were talking about the product amendments.<br />

Jennifer Beach asked if there should be edits for quality and business rules and Kim replied yes that would be fine.<br />

Judy Lewis, Qwest asked if the SBC GUI was set up with digital certificates and Kim replied that it was.<br />

Judy also asked if on the SBC system if multiple Eschelon employees can use the system at the same time. Kim replied yes but there are edits<br />

around who can submit the profile and who has read only capabilities.<br />

Ryan Hinkins, Qwest asked how long the SBC GUI had been active.<br />

Kim replied since January and added that each different section is routed mechanically to the appropriate employee in SBC.<br />

Ryan asked how access control was envisioned.<br />

Kim said either digital certificates or by id and password.<br />

Bonnie added that there would have to be one type for update capabilities and one for read only or view capabilities.<br />

Ryan asked if SBC allows read only and change.<br />

Kim said yes for Eschelon 2 employees can make changes and the remainder is read only.<br />

Judy said then it similar to what we have in IMA. Kim answered yes. Ryan verified that what your looking for is ability to retrieve, update and<br />

submit. Kim said yes with an added qualifier that SBC has time stamp and will reject sections with errors through status messages on the web.<br />

Ryan asked if there were different questionnaires for different states. Kim answered no, just one questionnaire but with the option to select states<br />

and contacts.<br />

Judy asked if the previous information in SBC was put in the GUI or if Eschelon had to load. Kim answered that Eschelon had to populate initially.<br />

3.0 Confirm Areas & <strong>Product</strong>s Impacted<br />

Web based questionnaire<br />

4.0 Confirm Right Personnel Involved<br />

Correct personnel were involved in the meeting.<br />

5.0 Identify/Confirm CLEC’s Expectation<br />

The expected deliverables are to create a secure web based electronic New Customer Questionnaire and Develop questionnaire sections so only<br />

sections requiring updates will need to be submitted.<br />

6.0 Identify any Dependent Systems Change Requests<br />

none<br />

7.0 Establish Action Plan (Resolution Time Frame)<br />

Eschelon will present at the <strong>March</strong> <strong>CMP</strong> meeting.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC022304-1<br />

Page 9 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC030204-1 Qwest to develop and implement a Directory<br />

Assistance only block.<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Centrex, Resale,<br />

Switched Service,<br />

Switching, UNE-P,<br />

Eschelon requests Qwest develop a block that allows blocking for local directory assistance (411 and 555-1212). Qwest currently only offers the<br />

ability to block 411 and 555-1212 through the Custom-net block. Customers do not always want to block direct dial long distance but do have a<br />

need to block local directory assistance. Custom-net forces the End User Customer to use an alternate billing method for long distance. Alternate<br />

billing for long distance is difficult to use because it requires a calling card or third party billing and can be very costly. Eschelon’s customers are<br />

often forced to absorb the cost of unauthorized directory assistance calls because the consequence of fraud or misuse on a calling card can be<br />

catastrophic to a business owner. Qwest should provide a blocking in a manner that meets customers needs. Qwest should not “package”<br />

directory assistance blocking so that a customer is forced to have additional blocks they do not need. The functionality does exist in at least the<br />

DMS100 and 5E switch to block only local directory assistance without requiring a customer use alternate billing for long distance.<br />

Expected Deliverable:<br />

Qwest will offer a block to block local directory assistance calls only without requiring additional blocks that a customer may not need.<br />

Status History<br />

Lynch, Randall<br />

Johnson, Bonnie<br />

foster, sandy<br />

Andreen, Doug<br />

3/2/04 CR Submitted<br />

3/3/04 CR Acknowledged<br />

Information Current as of:<br />

Report Name:<br />

Clarification<br />

3/2/04<br />

Originator Company Name:<br />

Eschelon<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

5<br />

<strong>Product</strong>s<br />

Impacted<br />

PC030204-1<br />

Page 10 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC062603-03 Business Rules Clarificaiton calls and event<br />

notification updates through the Addendum<br />

processs<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc All All<br />

AT&T requests that the Business Rules be opened up for clarification and that event notification updates be incorporated into the Addendum<br />

process. We seek Qwest adoption of SBC's process of a standard conference be established to address issues or concerns with the event<br />

notification and addendum updates. This SBC process includes conference call logistics: date, time and bridge number. They also send out a<br />

notification capturing the questions and answers provided durig the conference call.<br />

Expected deliverable: Adoption of SBC process relative to Business Rules Clarification and event notificattionupdates through the Addendum<br />

process<br />

Status History<br />

06/26/03 - CR Submitted<br />

06/30/03 - CR Acknowledged<br />

07/02/03 - CR Posted to Web<br />

07/11/03 - Held Clarification <strong>Meeting</strong><br />

07/16/03 - July <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

07/31/03 - Held Ad Hoc <strong>Meeting</strong> with CLEC community<br />

08/20/03 - August <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

09/09/03 - Held Ad Hoc <strong>Meeting</strong> with CLEC community<br />

09/17/03 - September <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

10/15/03 - October <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

11/19/03 - November <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

01/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

03/05/04 - Qwest sent SYST.03.05.04.F.01458.15.0_Comb_CLEC_QuestLog Combined Question Log for 15.0<br />

Project <strong>Meeting</strong>s<br />

Thu 2/19/04 3:59 PM<br />

From: Sanchez Steinke, Linda<br />

To: 'Osborne-Miller, Donna, NKLAM'<br />

Subject; RE: Phyllis's items for documentation<br />

Thank you Donna, I forwarded to<br />

Beth Foster, Kyle Kirves, and<br />

Randy Owen.<br />

Linda Sanchez-Steinke<br />

303-382-5768<br />

________________<br />

Thu 2/19/04 2:55 PM<br />

From; Osborne-Miller, Donna, NKLAM [dosborne@att.com]<br />

To: Sanchez Steinke, Linda<br />

cc: New Cr, Cmp<br />

Subject; Phyllis's items for documentation<br />

Hi Linda,<br />

Can you be sure to give this list to Beth Foster? It pertains to our conversation pertaining to PCO62603-03 and the Q&A log breakout of<br />

categories.<br />

thank you,<br />

Donna<br />

Winston, Connie<br />

Osborne-Miller, Donna<br />

Winston, Connie<br />

Sanchez-Steinke, Linda<br />

Development<br />

2/18/04<br />

Originator Company Name:<br />

Attachment<br />

Category breakdown based on IMA Appendix Categories for Collective Q&A Migration<br />

Information Current as of:<br />

Report Name:<br />

AT&T<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

6<br />

<strong>Product</strong>s<br />

Impacted<br />

PC062603-03<br />

Page 11 of 105<br />

Attachment D


A.1 ADDRESS VALIDATION<br />

A.2 APPOINTMENT RESERVATION<br />

A.3 TN APPOINTMENT CANCELLATION<br />

A.4 CONNECTING FACILITY ASSIGNMENT<br />

A.5 CUSTOMER SERVICE RECORDS<br />

A.6 DESIGN LAYOUT RECORD (DLR) RETURN<br />

A.7 FACILITY AVAILABILITY QUERY<br />

A.8 LISTINGS RECONCILIATION<br />

A.9 LOOP QUALIFICATION<br />

A.10 MEET POINT<br />

A.11 RAW LOOP<br />

A.12 SERVICE AVAILABILITY<br />

A.13 TELEPHONE NUMBER ASSIGNMENT<br />

B.1 END USER<br />

B.2 LOCAL SERVICE REQUEST<br />

C.1 CENTREX RESALE SERVICES<br />

C.2 DIRECTORY LISTING<br />

C.3 DID RESALE SERVICE<br />

C.4 HUNT GROUP INFORMATION<br />

C.5 LOOP SERVICE<br />

C.6 LOOP SERVICE WITH NUMBER PORTABILITY<br />

C.7 NUMBER PORTABILITY<br />

C.8 PORT SERVICE<br />

C.9 RESALE<br />

C.10 RESALE FRAME RELAY<br />

C.11 RESALE PRIVATE LINE<br />

C.12 RESALE SPLIT<br />

C.13 UNE CENTREX 21 (P OR STAR) SPLIT<br />

D.1 BILLING COMPLETION NOTICE<br />

D.2 COMPLETION RESPONSE<br />

D.3 DIRECTORY SERVICE CONFIRMATION AND ERROR DETAIL (DSRED) RESPONSE<br />

D.4 LOCAL RESPONSE<br />

D.5 PROVIDER NOTIFICATION<br />

D.6 SERVICE ORDER STATUS INQUIRY<br />

D.7 STATUS UPDATES<br />

D.8 PENDING SERVICE ORDER NOTIFICATION<br />

GENERAL/OTHER<br />

_____________________<br />

02/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Beth Foster with Qwest said that this CR has been discussed at the global action item meetings and last week Qwest met with AT&T and Liz<br />

Balvin with MCI. Qwest took action items from that meeting and determined that meeting minutes will be provided and posted on the production<br />

support page along side the trouble ticket information which is currently populated on the Wholesale Web site. There was discussion regarding the<br />

timeframe of posting meeting minutes. Connie Winston with Qwest said they would post the minutes within 3 days and would strive to get<br />

completed as soon as possible. Connie also said that Qwest would capture necessary information, necessary action items and a general re-cap of<br />

the meeting intent. Phyllis Burt mentioned that issues of importance to Qwest might not be the same as those that are important to the CLEC.<br />

Connie suggested that the CLEC could provide a red-line of meeting minutes back to Qwest.<br />

Donna Osborne-Miller with AT&T said that we could put this CR into CLEC test and see how the process works.<br />

Beth said that another action item was to look at how to handle the business rules clarification piece of the request, and noted that AT&T had<br />

initially asked that the Disclosure documentation be updated when CLECs ask for clarification. Qwest would like to start a single Q&A log with<br />

15.0 release and provide the log on the wholesale website out where the EDI Documentation FAQ pages currently resides. This single Q&A log<br />

will provide needed clarification to documentation, a way to see documentation before the addendum is posted, and, will allow everyone to see<br />

what questions other CLECs have had and how Qwest has responded. Beth explained that the process for EDI will be covered by the CLECs EDI<br />

Implementation <strong>Team</strong>s, and included in the body of the Q&A document that will be posted.<br />

Randy Owen with Qwest said an e-mail address would be set up for CLECs to send questions.<br />

Phyllis Burt requested the Q&A log be categorized by topic, such as Appointment Scheduling. Randy Owen will take that action item to see if this<br />

is feasible. Donna Osborne-Miller said the Q&A log would be cumbersome if not broken out by fields.<br />

Beth asked if everyone agreed that the process trial could begin with 15.0, and once the documentation was posted the CR could move into CLEC<br />

test for AT&T feedback. All agreed and Beth said that a Systems Notification will be sent stating that the Q&A log will be located on the Wholesale<br />

Web Site, under OSS, IMA, EDI Documentation under the FAQ link. This CR will move to Development Status.<br />

_____________________<br />

Fri 2/13/04 8:38 AM<br />

From; Linda Sanchez-Steinke<br />

To; 'dosborne@att.com'<br />

Subject; Updated Draft Response PC062603-03<br />

Hi Donna -<br />

As a follow up to yesterday's meeting regarding<br />

PC062603-03, attached is the updated draft response.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC062603-03<br />

Page 12 of 105<br />

Attachment D


As we discussed, Qwest took the following action<br />

items; documentation addendum notification<br />

meeting minutes, question and answer log. We<br />

will give an update at the <strong>CMP</strong> meeting.<br />

Thank you<br />

Linda Sanchez-Steinke<br />

CRPM<br />

Qwest<br />

303-382-5768<br />

_____________________<br />

<strong>Meeting</strong> Minutes<br />

PC062603-03 Business Rules Clarification calls and event notification update through the Addendum process<br />

<strong>CMP</strong> <strong>Product</strong> & <strong>Process</strong><br />

February 12, <strong>2004</strong><br />

1-877-572-8687, Conference ID 3393947#<br />

2:00 p.m. - 2:30 p.m. Mountain Time<br />

PURPOSE<br />

This meeting was held to discuss CR PC062603-03. The following is the write-up of the discussions, action items, and decisions made in the<br />

working session.<br />

List of Attendees:<br />

Liz Balvin - MCI<br />

Regina Mosley - AT&T<br />

Phyllis Burt - AT&T<br />

Donna Osborne-Miller - AT&T<br />

Beth Foster - Qwest<br />

Randy Owen - Qwest<br />

Kyle Kirves - Qwest<br />

Lynn Stecklein - Qwest<br />

Linda Sanchez-Steinke - Qwest<br />

MEETING MINUTES<br />

Linda Sanchez-Steinke with Qwest welcomed all attendees and explained that Qwest scheduled this meeting to discuss changes that have been<br />

implemented to address this CR.<br />

Kyle Kirves said that Qwest has made progress in the following areas; providing clearer information in the event notifications, revisited the event<br />

notification template, provide additional reasons behind severity issues, schedule conference calls on major impacts, and have initiated a CR to<br />

change the <strong>CMP</strong> document Section 12. A good example of Qwest’s effort to improve is the 2/13 conference call clarifying Event Notification<br />

674340. AT&T said they appreciated these efforts.<br />

Phyllis Burt with AT&T asked when clarification calls would take place. Kyle said they would take place for addendum changes. Phyllis Burt and<br />

Donna Osborne-Miller asked about meeting minutes from the clarification calls and Kyle said that minutes would be recapped in disclosure. Phyllis<br />

added AT&T prefers to get minutes as soon as possible because of the impacts to production. Randy Owen and Kyle Kirves agreed to address<br />

this action item and respond at <strong>Product</strong> <strong>Process</strong> <strong>CMP</strong>.<br />

Phyllis Burt asked about the question and answer log and said that with IMA 11 AT&T had lots of questions. Kyle said that in the addendum there<br />

will be a "change from" and a "change to" identification. Beth Foster added that the event notification would be in disclosure. Donna asked what<br />

the timing would be and Kyle answered that it may be two weeks after notification.<br />

Phyllis Burt said that when working with Wendy Green last year they wanted to have the ability to have clarifications added to the document about<br />

how the system behaves and didn’t want to wait until the next IMA release to get clarification updated.<br />

Beth Foster suggested that documentation changes could be made via the documentation request website. Kyle stated the website is for<br />

everything but disclosure document changes. Randy added that many times documentation changes have coding changes and is concerned<br />

about that. Kyle said that documentation rejects are not representative of what the system is doing, for simple clarification that represents<br />

enhancement to documentation. Phyllis said that AT&T builds systems from the documentation and then it will become a production problem.<br />

Beth said a trouble ticket should be opened for production problems. Phyllis said that AT&T asks questions and looks at the question log and<br />

gives them a good clarification and this is not in the Qwest disclosure document. Liz Balvin with MCI said we would want to assure that<br />

clarifications don’t get lost in the flow of the next release. Phyllis will provide examples of clarification questions and answers. Randy Owen said<br />

that Qwest had been considering a single Q&A log with all CLEC questions and clarifications. Liz added that the while Qwest might think<br />

clarification, it may be CLEC code impacting to have the update in the addendum especially from the EDI standpoint.<br />

Qwest will provide an update to the open action items at the <strong>Product</strong> <strong>Process</strong> <strong>CMP</strong>.<br />

_____________________<br />

01/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Connie Winston with Qwest said that this issue has been worked through oversight and in the emergency meetings. Qwest can initiate a quick<br />

meeting and CLECs are also able to initiate meetings. Carla Pardee with AT&T said that there had been a meeting held on loss and completion.<br />

Connie also said there are potential <strong>CMP</strong> language changes being proposed. Qwest will have an updated response in February. This CR will<br />

remain in Evaluation status.<br />

_________________________________<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC062603-03<br />

Page 13 of 105<br />

Attachment D


12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Connie Winston with Qwest said this CR has been discussed in the Global Action Item meetings and expects that the Global Action Item meetings<br />

will be wrapping up in the January timeframe. This was also discussed at the Oversight meeting and whether the new process will meet the intent<br />

of this CR.<br />

_________________________________<br />

11/19/03 November <strong>CMP</strong> <strong>Meeting</strong><br />

Kit Thomte with Qwest said that this CR was being discussed with the Global Action Item meeting 11/18/03. This CR will remain in Evaluation<br />

status.<br />

_________________________________<br />

10/15/03 October <strong>CMP</strong> <strong>Meeting</strong><br />

Kit Thomte with Qwest said that this CR was discussed at the 10/14/03 Global Action item meeting. It was agreed this CR would remain in<br />

Evaluation status.<br />

_________________________________<br />

09/17/03 September <strong>CMP</strong> <strong>Meeting</strong><br />

Connie Winston with Qwest provided an update and said that Qwest is reviewing what we can do better. Qwest has implemented calls to<br />

appropriate CLECs. When faxing becomes only solution Qwest is raising the severity level because there is no way for the CLEC to Communicate<br />

with Qwest. Liz Balvin said that a severity level 1 or 2 is fine and that 3 or 4 is not acceptable. Bonnie Johnson said there is a difference in the<br />

definition of immediately. Connie said that at Event Notification closure Qwest is providing clearer information about what we did and what we are<br />

doing. Monica Avila with VarTec provided an example that when Qwest end user fields went from optional to conditional, it required coding outside<br />

of the release. Liz Balvin said that because the fields were optional, had Qwest lifted the edits as emergency patch, then CLEC coding wouldn’t<br />

have to change. Connie said there was concern not knowing documentation was wrong CLECs didn’t know the CR made it into the release. Liz<br />

said by TN and SANO didn’t know back end changes were taking place. Liz said that address information needs to match SAV response. SAV<br />

needs to be in disclosure and in addendum for optional to conditional. Connie said that we are reviewing when it makes sense to reference the<br />

PCAT. Liz said that if it impacts coding then is should be in disclosure. Connie would like to roll this CR into the discussion of the Global Action<br />

item. It was determined that 10/14 from 10 a.m. –5 p.m. would be a good timeframe to discuss the CRs. This CR will remain in Evaluation Status.<br />

_________________________________<br />

Ad Hoc <strong>Meeting</strong> Minutes<br />

PC062603-03<br />

Business Rules Clarification calls and event notification updates through the Addendum processs<br />

<strong>CMP</strong> <strong>Product</strong> & <strong>Process</strong><br />

September 9, 2003<br />

1-877-572-8687, Conference ID 3393947#<br />

8:00 a.m. - 8:45 a.m. Mountain Time<br />

PURPOSE<br />

At the August <strong>CMP</strong> <strong>Meeting</strong>, participants agreed to hold a conference call to provide additional clarity and explain Phyllis Burt’s series of questions<br />

and statements about intent and meaning of the change request. The following is the write-up of the discussion.<br />

List of Attendees:<br />

Julie Pikar - U S Link<br />

Jen Arnold - U S Link<br />

Kim Issaacs - Eschelon<br />

Donna Osborne-Miller - AT&T<br />

Phyllis Burt - AT&T<br />

Regina Mosley - AT&T<br />

Tom Hyde - Cbeyond<br />

Byron Dowding - Alltel<br />

Stephanie Prull - McLeod<br />

Randy Owen - Qwest<br />

Kyle Kirves - Qwest<br />

Linda Sanchez-Steinke - Qwest<br />

MEETING MINUTES<br />

The meeting began with Qwest making introductions and welcoming all attendees.<br />

Linda Sanchez-Steinke with Qwest explained that the purpose of the meeting was to discuss and get further clarification about the AT&T CR<br />

PC062603-03. At the August <strong>CMP</strong> meeting, Qwest provided the draft denial response and Phyllis Burt with AT&T provided a counter proposal at<br />

the <strong>CMP</strong> meeting and asked that Qwest provide an updated response at the September meeting.<br />

Donna Osborne-Miller with AT&T provided the denial response red-lined with a series of questions and statements written by Phyllis Burt. Kyle<br />

Kirves with Qwest had received the questions/statements. Phyllis Burt with AT&T said that the purpose of the CR was to provide clearer<br />

information in event notifications. Phyllis said that when event notifications are not clear, AT&T goes to their implementation manager and then<br />

calls the help desk and try to get answers, but production problems are not clear. Phyllis said that with the SBC process there is a clarification call<br />

where questions can be asked. The issue is, if workarounds conflict with other business rules, then something else can fail. When AT&T<br />

Consumer converts from IMA 12 to 13 Phyllis will have to go back through the event notifications for the 13.0 release and look at to see if there is<br />

anything they would need to consider.<br />

Phyllis said that the purpose behind the CR is to make sure there are not long gaps in time on production impacts.<br />

AT&T suggests that there is a need for good clarification and AT&T has hundreds of questions in their Q&A log, and weeks go by and questions<br />

linger and wait. AT&T wants to find other avenues to head off production problems.<br />

Stephanie Prull with McLeod will not go back and look at Event Notifications for releases. McLeod will only do what is documented in the<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC062603-03<br />

Page 14 of 105<br />

Attachment D


Disclosure and try to code to the business rules. McLeod stated that they should not have to implement to anything other than the business<br />

rules. If McLeod has a CR or UR when going in then will code to it.<br />

Phyllis reiterated that there are two big things in the red-lined response: 1) AT&T wants to make sure that they understand the work around and<br />

that it is not conflicting with other rules so they don’t have to re-word the workaround. 2) AT&T would like clarification around the current impact<br />

and if they will receive rejects or jeopardies based on that impact.<br />

Kim Issacs said that Eschelon uses EDI and GUI (used for resale & UNE-P) and if they receive a work around notice and it conflicts with business<br />

rules Kim will call the help desk. Kim sometimes can wait up to two days to get an answer on what the product impact and issues are. In addition,<br />

they get communication of workarounds and then get rejects from the centers.<br />

Phyllis and Stephanie both have concerns with the PCRM ticket 167601 (LNUM) and still can’t explain what the impacts are to their companies.<br />

Randy Owen with Qwest said that he didn’t have specifics, and knows that the issue is discussed every day trying to get to a solution.<br />

U S Link said they are not on EDI, but share frustrations with process and support the AT&T CR. Randy said that we would take this information<br />

back and look at it further. Randy said that the CLECs should call the technical escalations if they are waiting too long on open trouble tickets that<br />

are severity level 3 and should escalate to severity level 2.<br />

Phyllis said that she suggests Qwest look at the proposal of having CLEC calls because questions and problems will be brought up as a group and<br />

would trigger discussions. With the technical escalation process, McLeod may raise an issue and AT&T may raise another issue, but discussion<br />

as a group would help.<br />

Randy said that he would like to know the rules and timing of the potential CLEC call. Kim said that having all CLECs on a call (for LNUM issue)<br />

would have helped. Stephanie Prull said that a call would not be needed on every event notice, but suggested that on event notices that the<br />

CLECs send an e-mail saying they want a call and if several CLECs sent an e-mail then Qwest should have a call.<br />

Phyllis said that AT&T just requests calls on workarounds event notifications that change a business rules and documentation appears not to be<br />

working the way Qwest says it is working.<br />

Phyllis also said that the second part of the red-lined document that with IMA 11 have Q&A log with major gaps. The next major release these will<br />

be worked into the addendum process.<br />

Randy said that we will take that back also and that if there is a bug identified or is this enhancement which would have to be in the next major<br />

release.<br />

Phyllis discussed the documentation for service address validation when look at Qwest Documentation it appears copied from pre-order, order and<br />

SANO populated. Phyllis said that what needs to be done is a documentation change.<br />

Linda asked if there were any other questions or additional information to provide. There were no additional comments or questions.<br />

_______________________________________<br />

08/20/03 - August <strong>CMP</strong> <strong>Meeting</strong><br />

Connie Winston with Qwest reviewed the draft response for this CR. Connie said that the information provided in the Event Notification Closure<br />

should include additional information that identifies the change, what was changed and what it was changed to. CLECs can also use the Technical<br />

Escalations to get more clarity in Event Notification. Donna Osborne-Miller with AT&T said that Phyllis Burt has provided documentation to the<br />

CLEC Community on Event Notifications and Donna will e-mail to Linda Sanchez-Steinke. Discussion continued when Connie Winston came into<br />

the <strong>CMP</strong> meeting. What AT&T would like is to hold an Ad Hoc meeting and provide additional clarity and explain Phyllis Burt’s counter proposal’s<br />

intent and meaning. Liz said that CLECs see the addendum as changes to EDI / GUI and want the ability to comment on the addendum. This CR<br />

will be moved to Evaluation status and Qwest will provide a revised response at the September meeting.<br />

_______________________________________<br />

8/20/03 4:53 p.m.<br />

Sent by: "Osborne-Miller, Donna, NKLAM" <br />

To: Linda.Sanchezsteinke@qwest.com><br />

cc: cmpcr@qwest.com><br />

Subject: Phyllis's counterproposal to documentation CR<br />

Linda,<br />

Here is the redline document Phyllis composed that I<br />

spoke with Connie about this morning.<br />

Thank you,<br />

Donna<br />

ATTACHMENT - PC062603-03 Response - FEEBACK.doc<br />

AT&T is seeking a clear understanding of the problem via a clarification call so all CLECs have a clear understanding of the problem/issue and the<br />

impact to their business so that they can make the appropriate business decisions.<br />

Currently, the event notification issued today are very vague as to the actually QWEST problem and the impact to the CLEC business. How can I<br />

identify this problem in production today? Is QWEST currently rejecting these orders, sending jeopardies or are the orders completing successfully<br />

but not being provisioned correctly?<br />

AT&T is requesting whenever a workaround is document that a clarification call to clearly communicate<br />

(1) the workaround in detail<br />

(2) the current impact to the CLECs order or service in production<br />

Example:<br />

(a) A notification for PCRM Ticket Number: 167601 has been issued several times. Initially it was not clear which <strong>Product</strong>s were impacted. The<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC062603-03<br />

Page 15 of 105<br />

Attachment D


extent of the change required and what happens to our orders when this occurs is still unknown. I’ve personally tried getting an answer via the<br />

contact number provided on the notification. A QWEST TT has been open since Friday August 15.<br />

AT&T is not requesting that the entire CLEC Q&A log be provided. QWEST has requested that AT&T provide the exact disclosure document<br />

update in the Q&A log. AT&T is requesting that CLECs that request documentation of clarifications provided in the Q&A and provide the exact<br />

wording required for the update to the Disclosure Document should be able to get these worked into the next Addendum update issued.<br />

AT&T Consumer disagrees that the current process is working effectively. If this were the case, I would not be making this request. The current<br />

notification process only provides confusion due to the lack of in depth analysis<br />

_______________________________________<br />

Ad Hoc <strong>Meeting</strong> Minutes<br />

PC062603-03 Business Rules Clarification calls and event notification update through the Addendum process<br />

<strong>CMP</strong> <strong>Product</strong> & <strong>Process</strong><br />

July 31, 2003<br />

1-877-572-8687, Conference ID 3393947#<br />

9:00 a.m. - 9:30 a.m. Mountain Time<br />

PURPOSE<br />

At the July <strong>CMP</strong> <strong>Meeting</strong>, participants agreed to hold a conference call to discuss and gain input from CLECs on this CR. The following is the writeup<br />

of the discussions, action items, and decisions made in the working session.<br />

List of Attendees:<br />

Liz Balvin - MCI<br />

Stephanie Prull - McLeod USA<br />

Regina Mosley - AT&T<br />

Phyllis Burt - AT&T<br />

Donna Osborne-Miller - AT&T<br />

Kyle Kirves - Qwest<br />

Linda Sanchez-Steinke - Qwest<br />

MEETING MINUTES<br />

Linda Sanchez-Steinke with Qwest read the change request description: AT&T requests that the Business Rules be opened up for clarification<br />

and that event notification updates be incorporated into the Addendum process. We seek Qwest adoption of SBC's process of a standard<br />

conference be established to address issues or concerns with the event notification and addendum updates. This SBC process includes<br />

conference call logistics: date, time and bridge number. They also send out a notification capturing the questions and answers provided during the<br />

conference call.<br />

Donna Osborne-Miller with AT&T said there were copies of the e-mail handout provided at the July <strong>CMP</strong> meeting and asked if CLECs on the call<br />

had the opportunity to look at the documentation. Liz Balvin asked if AT&T would give an overview. Linda Sanchez-Steinke with Qwest said the<br />

handout is also included in the body of the CR in the interactive report.<br />

Phyllis Burt with AT&T provided an overview of the handout. Phyllis explained how the SBC process of event notification is different from the<br />

Qwest process. In the Qwest event notifications there is an e-mail address to send questions to. SBC’s process for appending business rules<br />

documentation includes a set conference call within 3-5 days of the notification. This set conference call time is convenient because it allows<br />

everyone to have an hour free on their calendar and the opportunity, during event notification, to discuss issues or questions and understand how<br />

business rules are impacted. The meeting minutes from the conference calls are included in the final notification and that allows everyone unable<br />

to attend the conference call ability to read the minutes for additional information. AT&T is looking for Qwest to provide this type of process.<br />

Phyllis also said that if Qwest had this type of conference call it would provide the opportunity to discuss the change and the impact. That way<br />

everyone would understand how to communicate and what the business rule is. In addition, sometimes CLECs get different answers from different<br />

people at Qwest and we are all trying to understand and seek clarity to the blocking issues.<br />

Liz Balvin with MCI said the SBC process seems to be a more expeditious approach.<br />

Kyle Kirves with Qwest asked if CLECs were talking about providing PCAT and LSOG updates or addendum and disclosure document impacts.<br />

Phyllis Burt with AT&T said the Qwest notification explains that something is happening but there is no addendum. Kyle Kirves asked if CLECs<br />

were looking for information in the disclosure notification and if they want the notification to provide what the documentation change will be. Phyllis<br />

said yes.<br />

Linda Sanchez-Steinke with Qwest asked if there were any additional questions. There were no questions.<br />

_______________________________<br />

07/16/03 July <strong>CMP</strong> <strong>Meeting</strong><br />

Donna Osborne-Miller with AT&T presented this CR. Donna stated that AT&T would like Qwest to adopt the SBC process to address issues and<br />

concerns with event notifications and addendum updates. Donna said that they receive many event notifications from Qwest and the SBC process<br />

includes a clarification call 1-3 days after the notification to understand impacts. In addition, meeting notes are posted with a question and answer<br />

log. With EDI implementation 250-300 questions have been asked and some of the questions are not answered. Today, CLECs share their logs<br />

with other CLECs, MCI shares their log and McLeod shares their log. Judy Schultz with Qwest asked if the clarification call would take place<br />

during the production support timeframe. Donna said she is not sure if there is commonality between this CR and the CR for System Defects. Liz<br />

Balvin with MCI commented that if the Q& A logs were made public then they may not have to go to EDI teams which would be less work for<br />

Qwest. The CLEC community agreed to hold an ad hoc meeting to discuss this CR and Donna Osborne-Miller will provide the dates available for<br />

AT&T SMEs to Linda Sanchez-Steinke.<br />

_______________________________<br />

CLEC Change Request<br />

Clarification <strong>Meeting</strong><br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC062603-03<br />

Page 16 of 105<br />

Attachment D


2:00 p.m. (MDT) / Friday, July 11, 2003<br />

1-877-260-8255<br />

7616533#<br />

PC062603-03 Business Rules Clarification calls and event notification updates through the Addendum processs<br />

Name/Company:<br />

Donna Osborne-Miller, AT&T<br />

Carla Pardee, AT&T<br />

Phyllis Burt, AT&T<br />

Regina Mosley, AT&T<br />

Kyle Kirves, Qwest<br />

Dan Busetti, Qwest<br />

Wendy Thurnau, Qwest<br />

Linda Sanchez-Steinke, Qwest<br />

Introduction of Attendees<br />

Introduction of participants on the conference call was made and the purpose of the call discussed.<br />

Review Requested (Description of) Change<br />

AT&T’s CR requests that Qwest adopt SBC’s process of a standard conference to address issues or concerns with event notification and<br />

addendum updates. Phyllis Burt with AT&T read the e-mail below at the Clarification <strong>Meeting</strong> for participants on the call:<br />

(1) Several Event Notifications have come out that required discussion (see below). This CR is requesting that QWEST provide a clarification call<br />

for notifications that impact CLECS. The call should be held within 1-3 business days after the announcement at a set standard time for example<br />

(11am Mountain/12pm Central/1pm Eastern).<br />

(a) The initial notification should include the addendum summary if impacts the disclosure documents.<br />

(b) The appropriate SMEs should attend the clarification call to answer any issues/concerns and a walkthrough of the appropriate documentation<br />

should be completed.<br />

(c) The closure notifications should include meeting minutes from the clarification call and the new addendum version should be posted on the<br />

Disclosure document website with a reference to the closure notification #.<br />

Event Notification: 85434 IMA EDI GUI Initial Closure 061803<br />

"Description of Trouble: CLECs may be experiencing difficulty processing POTS and UNE-P POTS orders on the Resale form when attempting to<br />

change a line level USOC and a non-line level USOC on the same order. Business Impact: CLECs may not be able to process POTS or UNE-P<br />

POTS orders on a single form when a line level and a non-line level USOC is changing. Qwest Proposed Work Around: CLECs should send the<br />

requests for line and non-line level USOCs separately. Alternatively, CLECs may submit their orders, mark the request for manual handling, and<br />

provide instructions in the REMARKS."<br />

Event Notification: 75800 IMA EDI GUI 060503 Initial-Closure<br />

Description of Trouble: CLECs may be experiencing difficulty processing conversion LSRs with a Block Activity (BA) = N (no change to existing<br />

blocking). Business Impact: CLECs may be experiencing difficulties retaining existing blocks during conversion. Qwest Proposed Work Around:<br />

CLECs should use the Feature Activity (FA) = V to recap blocking USOCs.<br />

(2) QWEST/CLEC Q&A log clarification should be captured in the Addendum. There should be a monthly process to submit clarification updates.<br />

Followed by a standard monthly event notification and review as discussed above.<br />

Phyllis also said that MCI had quite a few questions when migrations were done and it would have been helpful to have Q & A logs for other<br />

CLECs to refer to. SBC identifies a timeline when the answers to questions will be given and includes center personnel and OSS personnel in<br />

their clarification calls for notifications that impact CLECS.<br />

Phyllis said that it would have been helpful for the April release to have included a Qwest/CLEC Q&A log because code wasn’t in the business<br />

rules. In addition, Phyllis has a concern that if IMA 10 or 11 had a clarification log then they could refer back to it for IMA 12 and 13. Whatever<br />

other CLECS have learned has not been documented in the disclosure document.<br />

Donna asked Kyle to provide an overview of the addendum process Qwest currently practices. Using the example above ( event 85434), Kyle<br />

described how this notification would justify an addendum. Specifically, he stated that, in this case, if the system were not functioning as<br />

documented, and the issue compromised the CLEC’s ability to process transactions, then a notification would be issued, and an addendum<br />

published. Situations that Qwest finds worthy of an addendum are those instances where the system is not functioning as documented.<br />

Clarification types of issues do not necessitate an addendum.<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

The area of this Change Request impacts addendum notifications.<br />

Confirm Right Personnel Involved<br />

Qwest confirmed the correct personnel were on the call to resolve the CR.<br />

Identify/Confirm CLEC’s Expectation<br />

AT&T’s expectation is that Qwest adopt the SBC process relative to Business Rules Clarification and even notification updates through the<br />

addendum process.<br />

Identify any Dependent Systems Change Requests<br />

No systems change requests.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC062603-03<br />

Page 17 of 105<br />

Attachment D


Establish Action Plan (Resolution Time Frame)<br />

AT&T will present this CR at the July <strong>CMP</strong> meeting.<br />

________________________________<br />

To: Sanchez Steinke, Linda, Donna Osborne-Miller<br />

From: Burt, Phyllis S, CSCIO [phyllissburt@att.com]<br />

Sent: Fri 7/11/03 1:56 PM<br />

Subject: RE: Clarification call for the documentation CR<br />

Here's some additional information for our call today.<br />

(1) Several Event Notifications have come out that required discussion (see below). This CR is requesting that QWEST provide a clarification call<br />

for notifications that impact CLECS. The call should be held within 1-3 business days after the announcement at a set standard time for example<br />

(11am Mountain/12pm Central/1pm Eastern).<br />

(a) The initial notification should include the addendum summary if impacts the disclosure documents.<br />

(b) The appropriate SMEs should attend the clarification call to answer any issues/concerns and a walkthrough of the appropriate documentation<br />

should be completed.<br />

(c) The closure notifications should include meeting minutes from the clarification call and the new addendum version should be posted on the<br />

Disclosure document website with a reference to the closure notification #.<br />

Event Notification: 85434 IMA EDI GUI Initial Closure 061803<br />

"Description of Trouble: CLECs may be experiencing difficulty processing POTS and UNE-P POTS orders on the Resale form when attempting to<br />

change a line level USOC and a non-line level USOC on the same order. Business Impact: CLECs may not be able to process POTS or UNE-P<br />

POTS orders on a single form when a line level and a non-line level USOC is changing. Qwest Proposed Work Around: CLECs should send the<br />

requests for line and non-line level USOCs separately. Alternatively, CLECs may submit their orders, mark the request for manual handling, and<br />

provide instructions in the REMARKS."<br />

Event Notification: 75800 IMA EDI GUI 060503 Initial-Closure<br />

Description of Trouble: CLECs may be experiencing difficulty processing conversion LSRs with a Block Activity (BA) = N (no change to existing<br />

blocking). Business Impact: CLECs may be experiencing difficulties retaining existing blocks during conversion. Qwest Proposed Work Around:<br />

CLECs should use the Feature Activity (FA) = V to recap blocking USOCs.<br />

(2) QWEST/CLEC Q&A log clarification should be captured in the Addendum. There should be a monthly process to submit clarification updates.<br />

Followed by a standard monthly event notification and review as discussed above.<br />

Thanks,<br />

Phyllis<br />

Qwest Response<br />

<strong>March</strong> 9, <strong>2004</strong><br />

DRAFT RESPONSE<br />

For Review by CLEC Community and Discussion at the <strong>March</strong> <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Donna Osborne-Miller<br />

AT&T<br />

SUBJECT: Qwest’s Change Request Revised Response - PC062603-03<br />

"Business Rules Clarification calls and event notification updates through the Addendum process"<br />

This response is a supplementary response to AT&T’s CR PC062603-03. Originally, Qwest denied this CR at the August <strong>CMP</strong> meeting. In<br />

response to a series of questions and statements provided by AT&T, and as a result of an ad hoc call held on 09/09/03, Qwest reviewed the points<br />

raised by the CLECs.<br />

As a result of the discussions held at the Global Action Items <strong>Meeting</strong>s (held on September 12, 2003; October 14, 2003; November 4, 2003;<br />

November 18, 2003; December 16, 2003), Qwest believes that the spirit of the original request has been met.<br />

Qwest is using this document to supplement its response to the request dated February 11, <strong>2004</strong>. Subsequent to the February 11 response, a<br />

meeting was held to discuss any gaps between Qwest’s understanding of the request, and the request’s intent. During that meeting, two gaps were<br />

discussed. They were:<br />

- AT&T requested that meeting minutes from any discussion around “Addendum to Disclosure Documentation” notifications be provided to the<br />

CLECs. Qwest committed to provide meeting minutes for these sessions no later than three (3) business days after the meeting. As the notification<br />

form itself is not designed to capture meeting minutes from the discussion, Qwest will record minutes from the meetings and publish them to the<br />

<strong>Product</strong>ion Support web site under the notification number. CLECs will have an opportunity to provide redlined edits to the minutes back to Qwest.<br />

- If any updates to the notification itself are required, Qwest will make those changes and republish the notification within one (1) day.<br />

- Regarding clarification to business rules, Qwest stated that it will continue to observe its established process for addendums and clarifications.<br />

Where “bugs” are identified, Qwest will publish a notification, documenting the bug, to be followed up by an addendum. For clarifications that do<br />

not constitute bugs, Qwest will capture the clarification in its Question/Answer log. Further, Qwest will start a single Q&A log with the15.0 release<br />

and provide the log on the wholesale website where the EDI Documentation FAQ pages currently reside. This single Q&A log will provide needed<br />

clarification to documentation, a way to see documentation before the addendum is posted, and, will allow everyone to see what questions other<br />

CLECs have had and how Qwest has responded.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC062603-03<br />

Page 18 of 105<br />

Attachment D


It was agreed that the process trial could begin with 15.0, and once the documentation was posted, the CR could move into CLEC test for AT&T<br />

feedback.<br />

Qwest maintains that the original request has been satisfied.<br />

Sincerely,<br />

Connie Winston<br />

Director, Information Technology<br />

Qwest<br />

____________________________<br />

February 11, <strong>2004</strong><br />

DRAFT RESPONSE<br />

For Review by CLEC Community and Discussion at the February <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Donna Osborne-Miller<br />

AT&T<br />

SUBJECT: Qwest’s Change Request Revised Response - PC062603-03<br />

"Business Rules Clarification calls and event notification updates through the Addendum process"<br />

This response is a supplementary response to AT&T’s CR PC062603-03. Originally, Qwest denied this CR at the August <strong>CMP</strong> meeting. In<br />

response to a series of questions and statements provided by AT&T, and as a result of an ad hoc call held on 09/09/03, Qwest reviewed the points<br />

raised by the CLECs.<br />

As a result of the discussions held at the Global Action Items <strong>Meeting</strong>s (held on September 12, 2003; October 14, 2003; November 4, 2003;<br />

November 18, 2003; December 16, 2003), Qwest believes that the spirit of the original request has been met.<br />

Qwest responds to these items by stating that, since the implementation of IMA EDI Release 14.0 on December 8, 2003, Qwest has made best<br />

efforts to invigorate the notification process. Qwest maintains that by revisiting its process, providing training to notifications authors, and revising<br />

the notification template itself. Qwest itemizes its actions taken to address this CR as follows:<br />

- Qwest is endeavoring to provide clearer information in the event notifications; and positive feedback from the CLECs indicates that Qwest has<br />

made significant progress on this front.<br />

- Qwest has a contingency plan in place to initiate calls with CLECs for high-profile, major impact event notifications and announce the conference<br />

calls in the body of the event notification. Qwest does not recognize the feasibility of initiating calls for every event, but will comply with major<br />

impact events, as stated.<br />

- As always, Qwest has worked to mitigate issues quickly; however, some production gaps will always exist due to prioritization of issues for<br />

resolution.<br />

- Qwest’s new internal process allows for event notification authors to work with the Interconnect Service Centers to generate appropriate, working<br />

workarounds that are approved by both Qwest and the CLEC.<br />

- Qwest now provides complete descriptions of impacts and error messages resultant from the issue, and has a separate place on the event<br />

notification form for capturing the error message verbatim.<br />

- Qwest now captures changes in documentation resulting in the body of the notification itself, in a “Change From:” and “Change To:” format.<br />

- As part of change request PC010704-1CM, Qwest is working toward language changes in the <strong>CMP</strong> document. The language change describes<br />

process improvements regarding notifications and documentation changes that cover some of the requests in this CR. Specifically, Qwest has<br />

updated the <strong>CMP</strong> document to demonstrate the following commitment regarding notifications, workarounds, and conference calls to CLECs:<br />

Qwest will attempt to make a software patch when the system is not working as defined in the technical specifications and/or the GUI systems<br />

documentation, and issue an event notification clearly defining the change.<br />

If Qwest determines that a software patch is not feasible, and/or Qwest or any CLEC identifies a Patch Release of software or related systems<br />

documentation changes that may impact CLEC production coding, Qwest will issue an event notification, initiate a Technical Escalation, and<br />

request a joint meeting between Qwest and the CLECs in order to discuss the particular Patch Release. Qwest will notify CLECs of the joint<br />

meeting in which Qwest will review the Patch Release, the proposed solution, and the variables which affect the resolution. In all instances, these<br />

joint meetings are exempt from the five (5) business day advance notification requirement described in Section 3.0. At this joint meeting, Qwest<br />

and the impacted CLECs will discuss how the pending Patch Release will affect their code. Qwest and the impacted CLECs will discuss any<br />

potential resolution options and implementation timeframes. In the event that agreement cannot be reached between Qwest and the impacted<br />

CLECs regarding the type of Patch Release to be implemented, the parties will attempt to negotiate an appropriate workaround.<br />

Qwest maintains that the original request has been satisfied.<br />

Sincerely,<br />

Connie Winston<br />

Director, Information Technology<br />

Qwest<br />

______________________<br />

September 10, 2003<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC062603-03<br />

Page 19 of 105<br />

Attachment D


DRAFT RESPONSE<br />

For Review by CLEC Community and Discussion at the September 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Donna Osborne-Miller<br />

AT&T<br />

CC:<br />

Lynn Notarianni<br />

Beth Foster<br />

Kit Thomte<br />

SUBJECT: Qwest’s Change Request Response - PC062603-03<br />

This response is a supplementary response to AT&T’s CR PC 062603-03. Originally, Qwest denied this CR at the August <strong>CMP</strong> meeting. In<br />

response to a series of questions and statements provide by AT&T, and as a result of an ad hoc call held on 09/09/03, Qwest is currently reviewing<br />

the points raised by the CLECs.<br />

Qwest proposes moving this Change Request into Evaluation Status while we continue to investigate to provide workable solutions. Qwest would<br />

like to add this item as a topic for discussion for the meeting on September 19th. Qwest will then provide an updated response no later than the<br />

October <strong>CMP</strong> <strong>Meeting</strong>.<br />

Sincerely,<br />

Connie Winston<br />

Director, Information Technology<br />

Qwest<br />

___________________________<br />

August 12, 2003<br />

DRAFT RESPONSE<br />

For Review by the CLEC Community and Discussion at the August 20, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Donna Osborne-Miller<br />

AT&T<br />

CC:<br />

Lynn Notarianni<br />

Beth Foster<br />

Kit Thomte<br />

SUBJECT: Qwest’s Change Request Response - PC062603-03<br />

CR Description:<br />

AT&T’s original change request states:<br />

AT&T requests that the Business Rules be opened up for clarification and that event notification updates be incorporated into the Addendum<br />

process. We seek Qwest adoption of SBC's process of a standard conference be established to address issues or concerns with the event<br />

notification and addendum updates. This SBC process includes conference call logistics: date, time and bridge number. They also send out a<br />

notification capturing the questions and answers provided during the conference call.<br />

Qwest Response:<br />

AT&T requests that Qwest adopt a regular call to address notifications issues that pertain to documentation changes or addenda to the Disclosure<br />

Documentation, and provide SMEs to answer the questions on the calls. In many cases, Qwest has not identified specific, word-for-word<br />

documentation impacts with the publication of the initial notification. Nor is that information available with the publication of the closure in all cases<br />

(in some cases, we are able to insert the Disclosure Documentation change into the closure, but this is typically a “documentation only” change<br />

notification). This is due to the fact that all documentation changes are reviewed by our System Requirements team. This System Requirements<br />

review is thorough and time consuming and would not be able to be completed during the timelines required by the notifications process in the<br />

<strong>CMP</strong> Document, Section 12.7. It involves research into field impacts, review of every instance to the field, cross-document impacts, systems and<br />

code impacts, and more. It is conducted over a period of time far greater than those involved in the notifications process.<br />

Qwest maintains that both a.) the initial notification cannot include the documentation impacts and b.) the clarification call would not be able to<br />

clarify the documentation changes, as there would be insufficient detail available at the time of the proposed call. Moreover, the Qwest resources<br />

who would be needed on the calls are those who would be working to remedy the issue. Having them on the calls removes them from working to<br />

effectively solve the problem, and would lengthen the time to resolve.<br />

If AT&T is requesting that all, or individual CLEC QA logs be provided as a part of the addendum process, this is not a logistically feasible business<br />

practice, because publishing these logs would require edits to every QA log for confidentiality.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC062603-03<br />

Page 20 of 105<br />

Attachment D


Qwest's existing process of providing notifications with workarounds, business impacts, and channels for escalation works effectively, and allows<br />

for targeted responses to customer concerns. Publishing the clarifications made to each individual CLEC to all other CLECs does not add a<br />

demonstrable business benefit to the process, to the CLECs, and would require Qwest to assume an additional two to three resources to<br />

implement the solution AT&T is proposing. Qwest will, however, endeavor to enhance its notifications pertaining to Disclosure Documentation by<br />

including the change in the body of the closure notification. For Disclosure Documentation changes that would constitute an addendum, Qwest will<br />

include the documentation change in a “Change From—Change To” format similar to the change summaries in the addenda themselves.<br />

Qwest respectfully denies this change request because the change does not result in a reasonably demonstrable business benefit and is<br />

economically not feasible.<br />

Sincerely,<br />

Connie Winston,<br />

Director, Information Technology<br />

Qwest<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC062603-03<br />

Page 21 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC102803-1 Improve Search Functionality of the Qwest<br />

Wholesale Website to minimize selections<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Qwest<br />

Wholesale<br />

Website<br />

Eschelon asks Qwest to improve the efficiency of the Qwest Wholesale Website search function. The CLEC community depends on the<br />

information Qwest provides on the Qwest Wholesale Website to obtain information on Qwest’s process, products, SGATs and OSS. The current<br />

search functionality of the Qwest Wholesale Website provides too many results and impedes a CLEC’s ability to quickly obtain important<br />

information. For example, on 10-14-03 Qwest sent a <strong>CMP</strong> notice regarding the grandparenting of Single Service in AZ. To fully understand the<br />

impact of this product retirement, Eschelon wanted to review the product information for Single Service on the Qwest Wholesale Website. Using<br />

the search function on the Qwest Wholesale Website, we received 12,300 results. A handful of these results did not pertain to wholesale but were<br />

Qwest retail information and Qwest corporate information. It is a burden to expect the CLECs to search through 12,300 results to find the<br />

information pertinent to a product. The above is one example of the struggles a CLEC faces when attempting to find specific information on the<br />

Qwest Wholesale Website. Improving the search functionality and <strong>CMP</strong> notice process is critical to a CLECs ability to find the information<br />

necessary for a CLEC to do business with Qwest. Qwest will also benefit if CLECs have better access to information on the Qwest Wholesale<br />

Website. Easy access to information may decrease the number of calls to the ISC, Qwest Service managers, WSHD and the Qwest <strong>CMP</strong> team.<br />

Expected Deliverable:<br />

1. Allow a CLEC an option to search the Qwest Wholesale Website only.<br />

2. Allow a CLEC the option to search each subsection (<strong>Product</strong> & <strong>Process</strong>, Resources, OSS, Network, Training, Notices and Forums, Customer<br />

Service) on the Qwest Wholesale Website.<br />

3. Qwest will start including a link to the <strong>Product</strong> on the Qwest Website on all <strong>CMP</strong> notifications that are grandparenting products.<br />

Status History<br />

McNa, Sue<br />

10/28/03 - CR Submitted<br />

10/29/03 - CR Acknowledged<br />

11/05/03 Held Clarification Call<br />

11/11/03 <strong>Meeting</strong> minutes sent<br />

11/19/03 - November <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

11/19/03 - Status changed to presented<br />

12/10/03 - Draft response issued<br />

12/17/03 -December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - Status changed to Evaluation<br />

1/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

1/21/04 - Status will remain in Evaluation<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Project <strong>Meeting</strong>s<br />

Isaacs, Kim<br />

Blackmun, Jarby<br />

Andreen, Doug<br />

Evaluation<br />

12/17/03<br />

Originator Company Name:<br />

Eschelon<br />

Report Line Number<br />

<strong>Product</strong>s<br />

Impacted<br />

2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Doug Andreen, Qwest stated there is no new information this month. The CR will remain in Evaluation status.<br />

------------------------------------------------------------------------<br />

1/21/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Doug Andreen, Qwest stated there is no new information this month. The CR will remain in Evaluation status.<br />

-------------------------------------------------------------------------<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Jarby Blackmun, Qwest reviewed the draft response. Kathy Stichter of Eschelon said she had looked over the response and tried the<br />

recommendations and still often was getting over 1,000 responses. Jarby agreed that if the type is Wholesale with other key words the system will<br />

look for any of the words making our best response to put more information in the notifications. Bonnie Johnson, Eschelon asked who would head<br />

up the effort to make sure the notification has current links. Jarby advised that this would be the <strong>Product</strong> Managers' and <strong>Process</strong> Managers via the<br />

documentation process. These managers have been advised. Bonnie also questioned what status this CR would be in. It was agreed to move<br />

the status to Evaluation.<br />

-----------------------------------------------------------------------<br />

11/19/03 Nov <strong>CMP</strong> <strong>Meeting</strong><br />

Kim Isaacs - Eschelon, presented the CR to improve the search capabilities of the Wholesale web site to be able to search only Wholesale, and to<br />

be able to search each category separately. She said Eschelon is encouraging the use of the web site and that many responses to searches is<br />

discouraging use. Bonnie Johnson - Eschelon, added that on a recent search for a grandfathered product, 12,300 results were returned. She<br />

further said that on the Clarification call Jarby Blackmun - Qwest, had indicated that changes to this site was in the works on a global level and that<br />

in the interim Jarby is investigating if more information can be added to the grandfather notices. Jarby added that the Wholesale search engine is<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC102803-1<br />

Page 22 of 105<br />

Attachment D<br />

7


the same engine driving the entire Qwest.com website. She also added that the capabilities described in the CR would be input to the Qwest effort<br />

to revamp Qwest.com. This CR will move to Presented status. Kim Issacs/Eschelon added that Eschelon asked Qwest to add links to notices to<br />

locate information contained in either the PCATS or Retail information. Qwest said it would work with the notice group to accomplish.<br />

---------------------------------------------------------------------<br />

Clarification <strong>Meeting</strong><br />

11:30 p.m. (MDT) / Wednesday November 5, 2003<br />

1-877-521-8688<br />

1456160#<br />

PC102803-1 Improve Search Functionality of the Qwest Wholesale Website to minimize selections<br />

Attendees:<br />

Name/Company:<br />

Kim Isaacs, Eschelon<br />

Bonnie Johnson, Eschelon<br />

Jarby Blackmun, Qwest<br />

Doug Andreen, Qwest<br />

Linda Sanchez-Steinke, Qwest<br />

Introduction of Attendees<br />

Introduction of participants on the conference call was made and the purpose of the call discussed.<br />

Review Requested (Description of) Change<br />

Doug read the description of the CR as follows: Eschelon asks Qwest to improve the efficiency of the Qwest Wholesale Website search function.<br />

The CLEC community depends on the information Qwest provides on the Qwest Wholesale Website to obtain information on Qwest’s process,<br />

products, SGATs and OSS. The current search functionality of the Qwest Wholesale Website provides too many results and impedes a CLEC’s<br />

ability to quickly obtain important information. For example, on 10-14-03 Qwest sent a <strong>CMP</strong> notice regarding the grandparenting of Single Service<br />

in AZ. To fully understand the impact of this product retirement, Eschelon wanted to review the product information for Single Service on the<br />

Qwest Wholesale Website. Using the search function on the Qwest Wholesale Website, we received 12,300 results. A handful of these results<br />

did not pertain to wholesale but were Qwest retail information and Qwest corporate information. It is a burden to expect the CLECs to search<br />

through 12,300 results to find the information pertinent to a product. The above is one example of the struggles a CLEC faces when attempting to<br />

find specific information on the Qwest Wholesale Website. Improving the search functionality and <strong>CMP</strong> notice process is critical to a CLECs ability<br />

to find the information necessary for a CLEC to do business with Qwest. Qwest will also benefit if CLECs have better access to information on the<br />

Qwest Wholesale Website. Easy access to information may decrease the number of calls to the ISC, Qwest Service managers, WSHD and the<br />

Qwest <strong>CMP</strong> team.<br />

Bonnie and Kim had nothing to add to the description or expected deliverables.<br />

Jarby stated that the request was clear to her.<br />

Kim mentioned that Eschelon is trying to encourage use of the website in her company and that the current search abilities are a hindrance.<br />

Jarby said that Qwest.com has one search engine that covers the entire website and that there is recognition with Qwest as to the need to improve<br />

the search engine.<br />

Bonnie stated that when the redesign architecture is done the needs of Wholesale and the CLECs need to be included.<br />

Jarby said that those concerns were and will be included and that she believes this could be on the books for next year.<br />

Doug explained the next steps including presenting the CR at the November <strong>CMP</strong> meeting and then having the response during the December<br />

cycle.<br />

Kim thought that in the interim if there could be a link established to the grandparented USOCS or a better description given in the notifications that<br />

this would help.<br />

Jarby said she would check with Susan Lorence and Mark Coyne on what could be done with the grandparenting issue. Jarby said she would also<br />

explore ways to do better searches on the existing engine since they are all a bit different this could make a good degree of difference.<br />

Kim and Bonnie agreed this could help.<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

Qwest Wholesale Website<br />

Confirm Right Personnel Involved<br />

Correct personnel were involved in the meeting.<br />

Identify/Confirm CLEC’s Expectation<br />

These expectations were confirmed.<br />

1. Allow a CLEC an option to search the Qwest Wholesale Website only.<br />

2. Allow a CLEC the option to search each subsection (<strong>Product</strong> & <strong>Process</strong>, Resources, OSS, Network, Training, Notices and Forums, Customer<br />

Service) on the Qwest Wholesale Website.<br />

3. Qwest will start including a link to the <strong>Product</strong> on the Qwest Website on all <strong>CMP</strong> notifications that are grandparenting products.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC102803-1<br />

Page 23 of 105<br />

Attachment D


Identify any Dependent Systems Change Requests<br />

None identified.<br />

Establish Action Plan (Resolution Time Frame)<br />

Kim will present the CR at the November 19 <strong>CMP</strong> <strong>Meeting</strong>. Response will be made during the December cycle.<br />

Qwest Response<br />

December 3, 2003<br />

For Review by the CLEC Community and Discussion at the December 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Kim Isaacs<br />

ILEC Relations <strong>Process</strong> Analyst<br />

Eschelon Telecom<br />

SUBJECT: Qwest Change Request Response - CR # PC102803-1 Improve Search Functionality of the Qwest Wholesale Website to<br />

minimize selections<br />

This letter is in response to Eschelon Communications Change Request CR # PC102803-1. This CR requests that Qwest provide improved<br />

search capabilities on the wholesale public web site and that Qwest include a link to the product on the Qwest Website on all <strong>CMP</strong> notifications<br />

regarding grandparented products. The request also include the need to refine searches to subsections within the Wholesale site, e.g. <strong>Product</strong> &<br />

<strong>Process</strong>, Resources, OSS, Network, Training, Notices and Forums, Customer Service.<br />

The current web search engine covers all content associated with the qwest.com site architecture. This includes all html sites and associated<br />

documents found within the qwest.com/wholesale. To narrow a search to content found only within the wholesale site architecture, a user must<br />

enter the word wholesale in the search prompt box and any other specific word or phrase description. When the search returns its results, only<br />

look at results that contain the word wholesale and the other words or phrases, e.g. wholesale, poles, ducts, right of way. As an example, if a<br />

result shows the phrase poles, but does not show wholesale, the search pulled results from outside the wholesale architecture.<br />

To further narrow a search, click on the advanced link (next to the search button), which should aid in refining a search. Choosing words or<br />

phrases that are specific to an inquiry can narrow a search. Example: searching for poles, ducts and right away will narrow the search and<br />

provide fewer responses than poles.<br />

Browsers (Explorer, Netscape, AOL) generally contain an option to search within an HTML web page. As an example, in Explorer, look under the<br />

Edit Menu and select the Find on this Page tool. This will allow a user to search only within that page.<br />

Qwest will include links to the appropriate product PCAT or will include the product manager contact information.<br />

Sincerely,<br />

Jarby Blackmun<br />

Senior Manager Wholesale Communications Initiatives<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC102803-1<br />

Page 24 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC110403-1 Update accuracy of FAM records Evaluation Wholesale ProdProc Pre-ordering,<br />

12/17/03<br />

Ordering<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Currently AT&T is experiencing difficulties with Qwest maintained FAM “Feature Availability Matrix” file being up to date. AT&T has been<br />

experiencing problems with the FAM file showing inaccurate USOCs or feature availability within NPA/NXX’s when a CSR shows that an existing<br />

Qwest customer has the features. AT&T believes this FAM file should be updated, at a minimum, weekly and that CLECs should be aware of<br />

updates to the FAM. This information must be readily available to Qwest as its own customers have the availability to obtain some features that<br />

CLECs are shown, via the FAM File, are unavailable. All CLECs will obtain valuable data from current, accurate and thoroughly updated<br />

information within the FAM file. AT&T therefore requests that these updates be made immediately and continually.<br />

Expected Deliverable:<br />

December 2003<br />

Status History<br />

11/04/03 - CR Submitted<br />

11/05/03 - CR Acknowledged<br />

11/10/03 - Contacted CLEC to schedule clarification call<br />

11/10/03 - Scheduled clarification call for 11/14<br />

11/14/03 - Held Clarification Call<br />

11/19/03 - Nov meeting minutes will be posted to the database<br />

12/10/03 - Emailed response to CLEC<br />

12/15/03 - Held CLEC ad hoc call to further discuss the FAM file<br />

12/17/03 - Dec meeting notes will be posted to the database<br />

12/22/03 - Emailed notes to CLECs<br />

1/21/03 - Jan <strong>CMP</strong> meeting minutes will be posted to the database<br />

2/18/04 -Feb <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the project meeting section<br />

Project <strong>Meeting</strong>s<br />

Pardee, Carla<br />

February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Connie Winston – Qwest advised that we have not gotten approval as of yet for this CR. We are still waiting for approval. Carla Pardee – ATT<br />

advised that ATT is disappointed that this did not get approved as it is a critical issue and it doesn’t seem as if this CR requires a lot of resources,<br />

so we do not understand the lack of approval. Bonnie Johnson – Eschelon asked is this one is like the ICON database? Connie advised she is not<br />

sure. Bonnie advised that her Service Manager (Jean Novak) told her that the fix would take place on <strong>March</strong> 1, <strong>2004</strong>. Connie advised that maybe<br />

an update is scheduled but not the entire fix. Cindy Macy – Qwest agreed to check with Jean Novak. This CR will remain in Evaluation Status.<br />

___________________________________________________<br />

Janaury 21, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Connie Winston – Qwest advised that this CR is in the same situation as some of the others. We are waiting to schedule and we hope to have a<br />

date in February. Carla Pardee – ATT asked what is the current process for updating the FAM file? Connie advised it is not being updated in a<br />

timely fashion. It has to be done manually and it is a huge manual effort. The way that we update FAM is that SONAR tracks availability by switch<br />

via tables in SONAR. This information is downloaded to a server and it becomes available to Qwest. This data should be published to FAM. We<br />

are working to get this update done in a mechanized fashion and looking at SONAR going away. Liz Balvin – MCI asked about the BPL edit that<br />

will reject the LSR if the feature is not available, that is part of 15.0. Connie Winston said this edit goes against the SAQ, not the FAM. Bonnie<br />

Johnson asked is there a need for the FAM file? Connie advised her understanding is that ATT wants to use it as a sales tool up front. Bonnie<br />

asked can it be used just from IMA so we don’t have to maintain two sources. Connie advised FAM is downloadable and in a bulk format, while<br />

IMA is an individual selection. The intent is both tools will use the same source in the future. Bonnie advised this is critical to our business as we<br />

use this information to offer products. Bonnie advised this is so critical that we will take another route if we don’t get it from <strong>CMP</strong>.<br />

________________________________________________________<br />

December 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Connie Winston – Qwest reported that we are still evaluating this CR. We are having a difficult time getting a process built for the updates and<br />

determining what that looks like. We are still looking at this CR and will change the status to Evaluation.<br />

__________________________________________________________________<br />

December 15, 2003 Ad hoc meeting<br />

PC110403-1 FAM File<br />

Ad Hoc <strong>Meeting</strong><br />

In attendance:<br />

Nicole James – Qwest<br />

Winston, Connie<br />

Winston, Connie<br />

Macy, Cindy<br />

Information Current as of:<br />

Report Name:<br />

Originator Company Name:<br />

AT&T<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

UNE-P<br />

8<br />

<strong>Product</strong>s<br />

Impacted<br />

PC110403-1<br />

Page 25 of 105<br />

Attachment D


Dave Fane - ATT<br />

Liz Balvin – MCI<br />

Phyllis Burt – ATT<br />

John Gallegos – Qwest<br />

Lydell Peterson – Qwest<br />

Carla Pardee – ATT<br />

Cindy Macy – Qwest<br />

Randy Owen – Qwest<br />

Kim Chambers – Qwest<br />

Cindy Macy – Qwest opened the call and explained that the purpose of the call is to review the issues associated with the FAM file and how the<br />

CLEC community uses the file. ATT requested this additional meeting with Qwest.<br />

Carla – ATT advised that ATT uses the file to figure out which features are available prior to submitting orders. Qwest doesn’t hard reject the<br />

LSRs when the data is not accurate. We may or may not get the feature provisioned. We do not know until our customer calls and tells us the<br />

feature is not working. Dave Fane – ATT advised that every other ILEC they work with sends and error report back that identifies the feature is not<br />

available. Then we update our file and don’t request the feature again. ATT would like Qwest to reject the order when we don’t detect the feature.<br />

John Gallegos – Qwest explained that this feature will be available in 15.0 EDI. This functionality is available today via SAQ in EDI. The CLECs<br />

said they do not have that EDI transaction built and they were told to use the FAM file as an alternative until 15.0 is available.<br />

ATT advised they assumed they would get rejects if the feature was not available. Qwest advised we are not billing the CLECs for features they<br />

are not getting. ATT advised we are billing our end users as we believed the feature did get provisioned.<br />

John Gallegos – Qwest advised he understands there is a gap in the FAM file data, and that the feature is available via the SAQ in EDI and that<br />

15.0 will reject upfront if features are not available.<br />

Liz Balvin – MCI asked if out of sync conditions are identified in the file so the CLECs can avoid those areas. John Gallegos- Qwest advised the<br />

file is too large as there are many switches and features and NPAs available in each state.<br />

Liz Balvin – MCI asked if Qwest is eliminating the FAM file after 15.0. John Gallegos – Qwest advised we are looking at all options. The concern<br />

that Qwest has is being able to support the FAM file going forward. We are doing everything we can to update the file. Qwest has manually<br />

updated the file. The last update was the end of September. This takes a considerable amount of time and manual effort.<br />

Carla – ATT advised they just wanted to reconfirm their need to access the FAM file. Liz Balvin – MCI advised that it is important to make sure the<br />

FAM file is updated. Phyllis Burt – ATT asked what is the correct process if we have trouble using the FAM file? Do we submit a trouble ticket to<br />

the Help Desk? John Gallegos advised it would probably be considered a Sev 3 ticket. John advised he can not give a timeframe as to when the<br />

trouble ticket / problem would be corrected. John assured the CLECs that Qwest is working on this issue and trying to determine the best action to<br />

take.<br />

_____________________________________________________________<br />

November 19, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Carla Pardee – ATT reviewed and presented this CR. Carla advised that ATT uses the FAM file to look at usoc availability by switch. Carla<br />

advised the data is not always accurate and ATT attempts to provide these features to their customers. ATT does not find out the feature is not<br />

available until their customer contacts them to report the feature is not working. This creates billing errors also. Bonnie Johnson – Eschelon<br />

asked if this was the ICON database. Carla advised you can access ICON and FAM on the web. Liz Balvin – MCI advised that MCI has also<br />

experienced situations when the SOC notice says the feature was provisioned, when it really isn’t available.<br />

____________________________________________________________________________<br />

PC110403-1 Clarification Call<br />

Update Accuracy of FAM file<br />

November 14, 2003<br />

In attendance:<br />

Monica Manning – Qwest Gary Berroa – Qwest<br />

Leo Demitriadis – ATT Nicole James – Qwest<br />

Doug Andrean – Qwest Cindy Macy – Qwest<br />

Carla Pardee – ATT Michael Whitt – Qwest<br />

Cindy Macy – Qwest opened the call, introduced attendees and reviewed the agenda.<br />

Carla Pardee – ATT reviewed the CR. Carla advised ATT has had problems with the FAM file not being up to date. The file shows inaccurate<br />

USOC feature availability information. ATT uses this file often. We order a feature and if Qwest doesn’t support the feature we don’t receive a<br />

reject on the LSR. Qwest continues to provision service. The order completion occurs and billing occurs but we don’t really provision the feature<br />

as it is not available. This causes billing errors to our end users. Leo Demitriadis – ATT explained ATT would like to have a change control log file<br />

we they know what has changed, or to have the file updated when ever the data changes, or to have it updated on a regular schedule.<br />

The team reviewed how to access the file to make sure we are all talking about the same file. The URL for instructions on how to access the file is;<br />

Doug Andrean – Qwest asked how often is the file updated. ATT advised they do not know.<br />

Micheal Whitt – Qwest asked if UNE –P was the product that ATT is concerned with. ATT advised yes.<br />

Nicole James – Qwest asked if ATT has an example of errors that you have found? Carla advised she will send Qwest an example. She believes<br />

she has an example in Minnesota.<br />

Mallory Paxton – Qwest asked how does ATT know when it is not accurate. Carla advised they do not know until their customer calls them back to<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC110403-1<br />

Page 26 of 105<br />

Attachment D


advise they did not get the feature provisioned.<br />

The team agreed they understand the request. Cindy Macy – Qwest advised this CR will be on the agenda for the November <strong>CMP</strong> meeting and<br />

ATT will present the CR. Qwest will provide a response at the December meeting.<br />

Qwest Response<br />

For Review by the CLEC Community and Discussion at the December 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

December 9, 2003<br />

AT&T<br />

Carla Dickinson Pardee<br />

LSAM Manager<br />

SUBJECT: CR # PC110403-1 Update accuracy of FAM records<br />

This letter is in response to AT&T’s Change Request (CR) PC110403-1. This CR requests that:<br />

- Qwest update the accuracy of FAM records<br />

Qwest is currently reviewing the processing and functionality provided by the FAM file. Qwest requests that this CR be placed in Evaluation<br />

status. AT&T has also requested an additional meeting be held to discuss the FAM file in more detail. Qwest will schedule the additional<br />

meeting.<br />

Sincerely,<br />

Connie Winston<br />

Qwest Communications<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC110403-1<br />

Page 27 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC111303-1 Allow multiple Billing Account Numbers Per<br />

<strong>Product</strong> Per State<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc UNE - P<br />

Qwest currently only supports a single BAN per product per state. MCI requests the ability to designate multiple BANs per product, per state. In<br />

doing so, the CLECs would have the ability to track orders submitted by different divisions of their company.<br />

Expected Deliverable:<br />

Determine whether a process change only is necessary whereby the CLECs would be required to populate differing BANs on each order.<br />

Otherwise, what system enhancements would need to be made to support.<br />

Status History<br />

11/13/03: CR Received<br />

11/14/03: CR Acknowledged<br />

11/25/03 - Held Clarification <strong>Meeting</strong><br />

11/25/03: Status Changed to Clarification<br />

12/17/03 -December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - Status changed to Presented<br />

01/14/04 - Response posted<br />

1/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

1/21/04 - Status changed to Development<br />

2/2/04 - Qwest generated notice <strong>CMP</strong>R.02.02.04.F.01317.AdHocBillingMtg<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Project <strong>Meeting</strong>s<br />

2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Burson, Sue<br />

Balvin, Liz<br />

Kriebel, Sue<br />

Andreen, Doug<br />

Sue Kriebel reviewed the action item concerning the examples from Cbeyond that carried non-active BAN numbers. Sue clarified the issue by<br />

stating that not all orders are assigned BANs automatically but only those that go through flow through. It was uncovered that orders manually<br />

typed were having BANs assigned incorrectly in some cases. She is working with the centers to correct. Stephen Calhoun, Cbeyond asked about<br />

the issue of the CLECs being able to use the alternate BAN field as they wished. Doug Andreen, Qwest said that was still being researched.<br />

Connie Winston, Qwest is looking into dropping existing edits of a formatting nature that now exist in the system. The CR will remain in<br />

development.<br />

----------------------------------------------------------------------------------------<br />

Ad Hoc <strong>Meeting</strong> Minutes<br />

PC111303-1<br />

Allow multiple Billing Account Numbers Per <strong>Product</strong> Per State<br />

<strong>CMP</strong> <strong>Product</strong> & <strong>Process</strong><br />

February 12, <strong>2004</strong><br />

1-877-521-8688, Conference ID 1456160<br />

9 a.m. – 10a.m. Mountain Time<br />

PURPOSE<br />

This meeting was to discuss action items from the January <strong>CMP</strong> <strong>Product</strong> and <strong>Process</strong> meeting, specifically:<br />

1. Cbeyond examples were old BANs have been populated<br />

2. Cost backup to the denial so CLECs can pursue other avenues<br />

3. Can CLECs use optional BAN field as they wish<br />

List of Attendees:<br />

Kathy Stichter, Eschelon<br />

T.J. Koller, Priority 1<br />

Liz Balvin, MCI<br />

Bonnie Johnson, Eschelon<br />

Kim Isaacs, Eschelon<br />

Jan Arnold, U S Link<br />

Carla Pardee, AT&T<br />

Stephan Calhoun, Cbeyond<br />

John Gallegos, Qwest<br />

Connie Winston, Qwest<br />

Information Current as of:<br />

Report Name:<br />

Development<br />

12/17/03<br />

Originator Company Name:<br />

MCI<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

9<br />

<strong>Product</strong>s<br />

Impacted<br />

PC111303-1<br />

Page 28 of 105<br />

Attachment D


Lydell Peterson, Qwest<br />

Sue Kriebel, Qwest<br />

MEETING MINUTES<br />

The meeting began with Qwest making introductions and welcoming all attendees.<br />

The meeting was called to discuss three outstanding items from the last <strong>CMP</strong> meeting:<br />

1. Cbeyond examples where old BANs have been populated (Sue Kriebel)<br />

2. Cost backup to the denial so CLEC can pursue other avenues (John Gallegos)<br />

3. Can CLECs use optional BAN field as they wish (Connie Winston)<br />

Issue 1.<br />

Sue Kriebel, Qwest stated that on the list from Cbeyond that not all products go through the FTS (flow through system) and have BANs<br />

automatically assigned. On the Cbeyond list several orders had been marked for manual handling and it was found that the control point not in<br />

place was to ensure that the person manually handling the order assigned the correct – active BAN.<br />

Stephan Calhoun, Cbeyond said that this more clearly explained why some orders were assigned BANs that were not expected. He feels that<br />

responses should initially carry this level of detail and thanked Qwest for the research<br />

Liz Balvin, MCI asked what audits were in place to ensure manually handled orders carry the correct BAN. Sue said the process organization had<br />

sent a reminder to the order typists reminding them that they need to look up the correct BAN in CPS. She also said that Qwest is looking for<br />

other methods to tighten this up.<br />

Issue 2:<br />

John Gallegos, Qwest explained the impacts of the LOE. He stated that numerous systems (7) were affected downstream.<br />

Connie Winston, Qwest added that CPS would have to be re-architect and then several changes to other impacted systems.<br />

Liz asked how the functionality had existed before when the burden for entering BANs fell to the CLECs. Connie answered that even then only one<br />

active BAN per product per state was permitted. Liz asked for more detail since the CLECs need to truly understand what is impacted rather than<br />

just saying multiple systems. Bonnie Johnson, Eschelon agreed saying that CLECs did not necessarily have to know the system names but need<br />

the hours breakdown. Connie suggested this be taken off line and thought through to determine the format and structure this might take. She<br />

added specific to this CR that the min impact was to CPS and other highly impacted systems would be IMA and CRM. Bonnie stated that this was<br />

more information than the CLECs have had before and Stephan added that it truly helps to understand the reasons behind the denial. Connie said<br />

she would take an action item to see what kind of language can be appended to the denial.<br />

Issue 3<br />

Connie said she was still checking if the CLECs could use the optional BAN field. Qwest does some formatting validation but is looking at what it<br />

would take to remove these edits. Liz asked if the editing was limited to things like A/N characters and not if the BAN was a “good BAN”. Connie<br />

said yes that it is formatting only. Liz asked what the timeframe was and Connie answered hopefully by the <strong>CMP</strong> meeting.<br />

--------------------------------------------------------------<br />

1/21/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Sue Kriebel, Qwest reviewed the response denying the request based on it being economically not feasible. Sue stated to allow multiple BANs per<br />

product per state would remove some automation and would require several front and back end system changes. Liz Balvin, MCI stated she had<br />

sent Cbeyond examples where old BANs had been populated and would like these to be investigated. Sue agreed to do so and also stated that<br />

when BANs are closed orders in queue will flow to the old BAN. Bonnie Johnson, Eschelon stated that it was also possible that the Cbeyond<br />

orders were handled on a manual basis. Steven Calhoun, Cbeyond said that the examples were new orders so this should not have been the<br />

case. Liz also wanted some cost backup to the denial citing that if it was important enough to the CLEC that they can pursue other avenues. Judy<br />

Schultz, Qwest said that a meeting was held a week ago explaining that detail needs to be provided on an economically not feasible denial.<br />

Bonnie Johnson, Eschelon did verify that if an incorrect BAN is placed on an order that it will be corrected automatically by Qwest. Bonnie added<br />

that the denial is based on “we can’t do this” when that very thing is happening today. Liz stated that the main thrust of the three multiple BAN<br />

CRs is to give the CLECs the ability to control the billing of their customers. She stated she didn’t know the trigger for changing BANs. Connie<br />

Winston, Qwest said the process is managed by the CPS system and is handled by specific centers. Connie verified that a CLEC could be notified<br />

when a BAN is at 6,000 and potentially could not be exhausted until 9,000 because of orders during the interim and that Qwest is trying to keep the<br />

BANs at an acceptable level to avoid processing problems. Connie mentioned that the process is the same for all CLECs. Liz asked if the CLECs<br />

could use the optional BAN field as they wished. Connie said she would check. It was verified that the FOC would provide the same information<br />

as it does today but CLECs could track to the outbound order. Kathy Stichter, Eschelon asked about BAN consolidation. Sue explained the<br />

process and that this was done manually with the center. It was agreed that there are multiple action items to research and that a conference call<br />

would be held when new information is available. The CR will remain open in Development status. (Comment from Stephanie Prull) Stephanie<br />

Prull – Eschelon stated she is interested in the economic breakdown as well due to the economic price discrepancies quoted between her CR and<br />

the MCI CR. (end comment).<br />

--------------------------------------------------------------<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Liz Balvin of MCI presented the CR and stated that a clarification meeting had already been held. Doug said that per the clarification call that two<br />

BANs per product per state would solve the MCI specific situation since they are trying to separate divisions. Sue Kriebel, Qwest clarified that<br />

today there is one active BAN and possibly many inactive. This CR calls for multiple active BANs. Liz said they were willing to assign BANs from<br />

MCI’s end if this would help although at the present time both Liz and Bonnie Johnson of Eschelon were sure that any BAN assigned by the CLEC<br />

was overrode when passing through Qwest systems. Bonnie pointed out that Eschelon has well over 100 bills to look at for disputes and<br />

discrepancies and that this presents an administrative nightmare. The CR was changed to Presented status.<br />

-----------------------------------------------------------------------<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC111303-1<br />

Page 29 of 105<br />

Attachment D


Clarification <strong>Meeting</strong><br />

11:00 a.m. (MDT) / Tuesday November 25, 2003<br />

1-877-521-8688<br />

1456160#<br />

PC111303-1 Allow multiple Billing Account Numbers Per <strong>Product</strong> Per State<br />

Attendees:<br />

Name/Company:<br />

Liz Balvin, MCI<br />

Sue Kriebel, Qwest<br />

John Gallegos, Qwest<br />

Doug Andreen, Qwest<br />

Introduction of Attendees<br />

Introduction of participants on the conference call was made and the purpose of the call discussed.<br />

Review Requested (Description of) Change<br />

Doug Andreen -Qwest read the description of the CR: Qwest currently only supports a single BAN per product per state. MCI requests the ability<br />

to designate multiple BANs per product, per state. In doing so, the CLECs would have the ability to track orders submitted by different divisions of<br />

their company.<br />

Doug also covered the expected deliverables of the CR: Determine whether a process change only is necessary whereby the CLECs would be<br />

required to populate differing BANs on each order. Otherwise, what system enhancements would need to be made to support.<br />

Liz Balvin MCI stated that she has confirmed with her service manager that MCI is only allowed one BAN per product per state. She said that<br />

there is a field on the LSR to populate the BAN and she was hoping this would be able to be used to solve the request.<br />

Sue Kriebel Qwest said that there are numerous customers that do not populate this field and that it is populated when it hits Qwest. She also<br />

clarified that there may be multiple BANs per product per state but only one is live.<br />

Liz said what she is trying to do is enable segregation of the two divisions in MCI that handle the same products. Two BANs per state per product<br />

would be sufficient for MCI. She also thought there was another CR in existence that was similar. John agreed.<br />

John gave some historical perspective on population of the BAN field on the LSR. While it was done by the CLECs for some time this became a<br />

problem and now this field is populated by Qwest. John stated that implementing this CR would possibly put the responsibility back on the CLECs<br />

for ensuring the right BAN was on the order.<br />

Liz said MCI would be willing to do this and is open to any way to support implementation of the CR.<br />

Liz found the CR that is very similar. SCR100903-02.<br />

Sue questioned if this CR could still be worked as only a process change.<br />

John said no that there would have to be changes to internal systems to accommodate the change.<br />

Liz mentioned that she thought the customer profile drove BAN assignment.<br />

John answered yes, but only in part<br />

Liz expressed the concern that if this requires systems changes especially to IMA that a time line of presenting the CR at the December <strong>Product</strong><br />

and <strong>Process</strong> meeting and having a response in January would conflict with the prioritization of 16.0 CRs in IMA for system changes.<br />

John responded that he would consider the expectations of her CR along with SCR100903-02 to ensure that the timeframes did not adversely<br />

impact prioritization.<br />

It was agreed to leave the CR in <strong>Product</strong> and <strong>Process</strong> for now.<br />

Doug agreed to relate to two CRs.<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

Billing and Wholesale Billing Interface<br />

Confirm Right Personnel Involved<br />

Correct personnel were involved in the meeting.<br />

Identify/Confirm CLEC’s Expectation<br />

The following expectations were identified/confirmed:<br />

1. Determine whether a process change only is necessary whereby the CLECs would be required to populate differing BANs on each order.<br />

2. Otherwise, what system enhancements would need to be made to support<br />

3. Relate this CR and SCR100903-02 in order to accelerate possible resolution of the CR.<br />

Identify any Dependent Systems Change Requests<br />

Related system change SCR100903-02 is related but not dependent<br />

Establish Action Plan (Resolution Time Frame)<br />

As it now stands, Liz will present the CR at the December 17 <strong>CMP</strong> <strong>Meeting</strong>. Response will be made during the January cycle.<br />

Qwest Response<br />

January 5, <strong>2004</strong><br />

DRAFT RESPONSE<br />

For Review by the CLEC Community and Discussion at the January <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Liz Balvin<br />

MCI Carrier Management - Qwest Region<br />

MCI<br />

SUBJECT: Qwest Change Request Response – CR PC111303-1<br />

Allow Multiple Billing Account Numbers Per <strong>Product</strong> Per Sta<br />

Qwest currently supports a single BAN per product per state. MCI requests the ability to designate multiple BANs per product, per state. In doing<br />

so, the CLECs would have the ability to track orders submitted by different divisions of their company.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC111303-1<br />

Page 30 of 105<br />

Attachment D


A clarification meeting was held on November 25, 2003 with MCI and Qwest representation. At this meeting, Qwest clarified with MCI there may be<br />

multiple BANs per state but only one is ‘live/active.’ MCI explained they would like the ability to segregate the two divisions of MCI that handle the<br />

same products and therefore would only need two active BANs per state.<br />

Qwest has completed an analysis for PC111303-1, Allow Multiple Billing Account Numbers, per <strong>Product</strong>, per State, and has determined that this<br />

change is economically not feasible. Qwest currently provides active BANs on a state by state basis. Qwest auto-populates these BANs to<br />

ensure ordering and billing accuracy. This change would require Qwest to remove this automation, which would require Qwest and CLEC manual<br />

intervention likely leading to additional errors or an increase in rejects. Additionally, several of Qwest’s front and back end systems would require<br />

changes in order to remove automation, modify existing accounts to allow the manipulation of BANs. Through Qwest’s analysis it was determined<br />

that the estimate for the initial implementation of this change would be at least $1 million. Qwest believes that to implement such a change to<br />

Qwest systems would be cost prohibitive.<br />

Therefore, Qwest respectfully denies your request for PC111303-01, Allow Multiple Bans per <strong>Product</strong>, per State, due to economic infeasibility.<br />

Sincerely,<br />

Sue Kriebel<br />

Manager <strong>Process</strong> Management<br />

Qwest<br />

CC:<br />

Connie Winston<br />

Lynn Notarianni<br />

Loretta Huff<br />

Beth Foster<br />

Kit Thomte<br />

Judy Schultz<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC111303-1<br />

Page 31 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC111903-1 Website for Event Notifiers Evaluation Wholesale ProdProc pre-ordering<br />

1/21/04<br />

provisioning<br />

ordering billing<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

AT&T and other CLECs desire Qwest to provide a website listing all Event Notifiers that have been submitted by Qwest for the past 90 days. This<br />

website will provide, at a minimum, the event number, description of event, date submitted, system used with version number, status (i.e. pending<br />

analysis, closed, initial, etc), severity level, and region effected. AT&T further requests that the description be complete enough to enable a CLEC<br />

to search any field by product, date, and trouble type. AT&T also requests that the website would have the functionality so that CLECs could sort<br />

by column, however, internal analysis management would be up to each individual CLEC.<br />

Expected Deliverable:<br />

By January <strong>2004</strong>, AT&T expects the following deliverable: A website listing all Event Notifiers sent by Qwest for the past 90 days. The website will<br />

provide, at a minimum: 1) event number; 2) complete description of event; 3) date submitted; 4) system type with Version number; 5) status; 6)<br />

severity level; and 7) region effected.<br />

Status History<br />

____________________________________________________<br />

11/19/03 <strong>CMP</strong> <strong>Meeting</strong><br />

Kit Thomte – Qwest advised that this CR was talked about Tuesday during the Global Action Item meeting. This CR was updated with the new<br />

title and description. Carla Pardee – ATT advised they would like to keep the old CR open and use the new CR description and title to open a<br />

different/new CR. Cindy Macy – Qwest asked if ATT would like to have the new CR clarified or had this happened during the Global Action Item<br />

meeting. Carla advised she would like Qwest to hold a Clarification Call for the new CR.<br />

_________________________________________________________________________________________<br />

11/19/03: CR Received (CR came in on 11/12 but ATT was not sure if they wanted to update existing CR PC022703-9 or create new one. During<br />

Nov 19 <strong>CMP</strong> meeting ATT advised they would like to open new CR and agreed for Qwest to accept CR and schedule clarification call.<br />

11/21/03: Acknowledge CR<br />

11/24/03: Scheduled Clarification Call for 12/4<br />

12/4/03: Held clarification call<br />

12/17/03 - December <strong>CMP</strong> notes will be posted to the database<br />

1/21/03 - Jan <strong>CMP</strong> meeting minutes will be posted to the database<br />

2/18/04 -Feb <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the project meeting section<br />

Project <strong>Meeting</strong>s<br />

Pardee, Carla<br />

February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Connie Winston – Qwest advised this CR also did not get approved as of yet. We are working on this and should have an update soon. This CR<br />

will remain in Evaluation Status.<br />

_______________________________________________________________<br />

January 21, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Connie Winston – Qwest advised this is the CR that was opened as part of the Global Action Item meetings. The work is not scheduled as of yet.<br />

Carla Pardee-ATT asked when is this planned for scheduling. Connie advised she does not have a definite date as of yet but hopes to have a<br />

schedule in February. Liz confirmed that this report would look like a spreadsheet of the Event Notification Report. Connie agreed. Liz asked<br />

about the additional details and root cause analysis information that was discussed. Connie advised we did not agree to provide that information.<br />

That information would be very labor intensive to provide. Liz advised it would be helpful to know what the problem was. Carla agreed that more<br />

detail is better. Bonnie said they want to know what made it break, how did we stop it (work around), and what is going to fix it going forward.<br />

Connie said that it takes a lot of over head to put together that level of detailed information on the event notification. The CLECs asked if Qwest<br />

looks at the reject code to find out if multiple CLECs are impacted. Connie advised Qwest does this, and looks at the global picture and<br />

sometimes the data does show a different perspective. This CR will move to Evaluation Status.<br />

__________________________________________________________________<br />

December 17 <strong>CMP</strong> <strong>Meeting</strong><br />

Carla Pardee – ATT presented this CR. Connie Winston – Qwest advised that this CR is related to the Global Action Item meetings and was<br />

opened as a result of PC022703-9X. This CR will move to Presented Status.<br />

_____________________________________________________________________________<br />

Clarification Call<br />

PC111903-1 Website for Event Notifiers<br />

December 4, 2003<br />

11: 00 – 11:30 a.m. MT<br />

Winston, Connie<br />

Owen, Randy<br />

Macy, Cindy<br />

Information Current as of:<br />

Report Name:<br />

Originator Company Name:<br />

AT&T<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

10<br />

<strong>Product</strong>s<br />

Impacted<br />

PC111903-1<br />

Page 32 of 105<br />

Attachment D


Attendees:<br />

Jim Recker – Qwest<br />

Kim Isaacs – Eschelon<br />

Kyle Kirves – Qwest<br />

Steph Prull – Eschelon<br />

Bonnie Johnson – Eschelon<br />

Carla Pardee – ATT<br />

Randy Owen – Qwest<br />

Cindy Macy – Qwest opened the call and clarified for the users that this CR was opened as a result of decisions made at the Global Action Item<br />

meeting. PC022703-9X originally requested similar functionality, but through the Global Action Item meetings agreement was reached that a new<br />

CR would be opened (PC111903-1).<br />

Carla Pardee - ATT reviewed the CR. Carla described the functionality that ATT is looking for. A website that displays all event notification, with<br />

event number, complete description of event, date submitted, system type and version number, status, severity level and region affected.<br />

The CR also states that this website would display event notifications that have been submitted in the past 90 days. The team clarified the better<br />

way to display event notifications is to make them available for 30 days after they have been implemented. The clock would start when they are<br />

implemented.<br />

Kim Isaacs – Eschelon asked if the description included the work around information. Randy Owen said they should be able to include this in the<br />

description, or include it as a field on the report. The plan is to use the event notification form. There may be an issue to the amount of space<br />

available on the web site. The original event notification is always available to view the work around information.<br />

Bonnie Johnson – Eschelon suggested we show a field work around ‘yes or no’ and then if yes is populated you could view the work around<br />

information on the original event notification.<br />

Discussion took place regarding sorting by system. Randy Owen – Qwest advised that system is a separate field on the event notification, so you<br />

should be able to sort by that field on the report. Sort functionality would be provided so users could sort by any specific field.<br />

The CLECs asked on average how many event notifications are there in a 30 day period? Randy estimated at less than 30 and greater than 10.<br />

Steph Prull – Eschelon requested the ability to sort by ‘individual version’. For example, if an event impacted multiple versions, to list the versions<br />

individually so the CLECs could view events by version. If a CLECs wanted to see all events that affect V13, they could sort by individual version.<br />

The team agreed the right personnel were involved and that Qwest understood the CLECs expectations. This CR impacts all products and any<br />

area that an event notification could be issued on.<br />

Next steps are for this CR to be presented by ATT at the December <strong>CMP</strong> meeting. Qwest will prepare a response at the January <strong>CMP</strong> meeting.<br />

______________________________________________________________________________________________________________________<br />

__________<br />

11/19/03 <strong>CMP</strong> <strong>Meeting</strong><br />

Kit Thomte – Qwest advised that this CR was talked about Tuesday during the Global Action Item meeting. This CR was updated with the new<br />

title and description. Carla Pardee – ATT advised they would like to keep the old CR open and use the new CR description and title to open a<br />

different/new CR. Cindy Macy – Qwest asked if ATT would like to have the new CR clarified or had this happened during the Global Action Item<br />

meeting. Carla advised she would like Qwest to hold a Clarification Call for the new CR.<br />

Qwest Response<br />

For Review by the CLEC Community and Discussion at the January 21, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

January 14, 2003<br />

AT&T<br />

Carla Dickinson Pardee<br />

LSAM Manager<br />

SUBJECT: CR # PC111903-1 Web site for Event Notifier<br />

This letter is in response to AT&T’s Change Request (CR) PC111903-1. This CR requests that<br />

Qwest provide a web site for Event Notifiers.<br />

Qwest understands the requested change and the enhancements are under evaluation. Qwest will move this CR to Evaluation status.<br />

Sincerely,<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC111903-1<br />

Page 33 of 105<br />

Attachment D


Connie Winston<br />

Qwest Communications<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC111903-1<br />

Page 34 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC112003-1 Differentiate between Loop-MUX combos<br />

and EELs due to different FCC treatment<br />

(TRO Order)<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Seperately identify LMCs and EELs on bills<br />

Status History<br />

Wholesale ProdProc Billing, EEL (UNE-C), Loop<br />

MUX Combo<br />

11/20/03 - CR Submitted<br />

11/21/03 - CR Acknowledged<br />

11/24/03 - Spoke with Morgan Halliday, he will call back & schedule clarification meeting<br />

12/01/03 - Clarification <strong>Meeting</strong> scheduled 12/4<br />

12/04/03 - Held Clarification Call<br />

12/17/03 - December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

01/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

02/17/04 - Qwest issued PROD.02.17.04.F.01369.EEL_V25, Level 1 effective 2/18/04, provides download in billing section w/ EEL/LMC Class of<br />

Service and EEL USOCs<br />

02/17/04 - Qwest issued PROD.02.17.04.F.01371.LMC_V21, Level 1 effective 2/18/04, provides download in billing section w/ EEL/LMC Class of<br />

Service and LMC USOCs<br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Project <strong>Meeting</strong>s<br />

Campbell, Bill<br />

Finley, Pat<br />

Sanchez-Steinke, Linda<br />

Ad Hoc <strong>Meeting</strong> Minutes<br />

PC112003-1<br />

<strong>March</strong> 5, <strong>2004</strong><br />

1-877-572-8687, Conference ID 3393947#<br />

9:00 a.m. - 10:00 a.m. Mountain Time<br />

List of Attendees:<br />

Tom Hyde - Cbeyond<br />

Kathy Stichter - Eschelon<br />

Kim Isaacs - Eschelon<br />

Rodney Johnson - SBC<br />

Pat Finley - Qwest<br />

Robyn Libadia - Qwest<br />

Gayla Samarripa - Qwest<br />

Sami Hooper - Qwest<br />

Jennifer Fisher - Qwest<br />

Susie Johnson - Qwest<br />

Sue Kriebel - Qwest<br />

Peggy Esquibel-Reed - Qwest<br />

Lynn Stecklein - Qwest<br />

Linda Sanchez-Steinke - Qwest<br />

Evaluation<br />

1/21/04<br />

Originator Company Name:<br />

The meeting began with Qwest making introductions and welcoming all attendees. Linda Sanchez-Steinke with Qwest explained that the purpose<br />

of the meeting was to discuss CR PC112003-1 agenda topics:<br />

- Qwest will not establish separate Class of Service for EEL & LMC<br />

- Qwest assigning interstate Classes of Service on new EEL/LMC requests<br />

- Determine if EEL/LMC services established as new connect or conversion<br />

- Jurisdiction of EEL/LMC<br />

- EEL/LMC XUMAX Interstate, UBNWN Intrastate Rates<br />

- PCAT updates<br />

The following is the write-up of the discussions and action items from the working session.<br />

Report Line Number<br />

Cbeyond Communications<br />

<strong>Product</strong>s<br />

Impacted<br />

- Qwest will not establish separate Class of Service for EEL & LMC. Pat Finley with Qwest explained that separate classes of service will not be<br />

provided for EEL and LMC. Qwest has developed the TRAK FID on the CSR which identifies EELs and LMC circuits. Pat added that Qwest will<br />

not count LMCs in the calculation of LIS trunking to EEL ratio.<br />

- Qwest assigning interstate Classes of Service on new EEL/LMC requests. Pat Finley said that Qwest did have a deviation from the process and<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

11<br />

PC112003-1<br />

Page 35 of 105<br />

Attachment D


orders for the conversion were issued with Interstate classes of service. Additional training has been provided to the center and the center is in the<br />

process or writing orders to correct. Tom Hyde with Cbeyond said that he is concerned that UNE billing deviates from Telcordia standards with<br />

respect to USOCs. Pat said the EEL and LMC PCATs have been updated to include a download of USOCs for interstate and intrastate. Tom said<br />

that he has not reviewed the PCAT. Sami Hooper with Qwest said that the Chan Term is the same as special access but has a unique class of<br />

service and ZCID. Tom Hyde said that the rate is driven by the ZCID. Sami said that the rate is driven by class of service, USOC and the<br />

company code or ZSID makes the rate unique. Tom said he is concerned that class of service is irrelevant to billing of basic Chan Term which is<br />

a finished service. Pat said that the company code makes rating unique and several UNEs borrow retail USOCs. The interconnection agreement<br />

provides rates. Tom said he was concerned that the PCAT will be ambiguous, an audit of billing will provide different information and the only<br />

method to audit is a manual method. The interoffice mileage and fixed charges are charged incorrectly. Pat said the USOC definitions will be the<br />

same and this is not unique to LMC and EEL. The rating is done per the interconnection agreement. Susie Johnson said that Gia is correcting the<br />

incorrectly billed multiple fixed mileage charges.<br />

- Determine if EEL/LMC services established as new connect or conversion. Tom said that Qwest has asked him to identify which were new<br />

connect circuits and which were converted circuits and that everything was being assigned Interstate. Pat said that Qwest knows how the services<br />

were established, either new connect or conversion.<br />

- Jurisdiction of EEL/LMC. Pat Finley said that 14 circuits have the incorrect circuit ID and are being corrected via record orders.<br />

- EEL/LMC XUMAX Interstate, UBNWN Intrastate Rates. Pat Finley said that Qwest has no plans to charge a higher rate for interstate vs.<br />

intrastate and UNE’s are billed at TELRIC. Tom Hyde said he doesn’t care for CRIS billing for UNE-P, that it was probably ok a couple years ago<br />

and is causing grief because of the lack of consistency and manual work involved to audit bills. CRIS billing is not part of <strong>CMP</strong> CR PC112003-1<br />

and was not discussed further.<br />

- PCAT updates. Pat Finley said the PCAT was updated and provides a download to map USOCs and class of service. Tom said he has not<br />

reviewed the changes made to the PCAT. Pat said that the combination of USOCs are unique. Sami said that is correct and the PCAT identifies<br />

the nonrecurring USOCs and the FID identifies if EEL or LMC. LMC has no mileage. Tom said that the bill will subtract LMC mileage and it was<br />

billed in error, identified in manual audit. Pat said that if orders are issued correctly the ZCID, etc. drives billing. Pat explained that establishing a<br />

new unique classes of service for LMC is cost prohibitive due to the conversion required to the embedded base. Tom said that a new USOC can’t<br />

be cost prohibitive. Tom added that the circuit ID is being corrected and has helped.<br />

There were no additional questions and Linda said that meeting minutes would be provided in the body of the change request.<br />

_______________________<br />

02/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Pat Finley with Qwest said the examples Cbeyond provided following the January meeting were examples of circuits with jurisdiction based on the<br />

class of service. There were hundreds of circuits converted correctly via record orders and the 10 circuits provided as examples were issued<br />

incorrectly, and required record orders to fix. Pat explained that the PCATs for EEL and LMC were updated and now contains a downloadable list<br />

of USOCs for interstate and intrastate. The USOC list, combined with the TRAK FID on the CSR differentiates LMC and EEL and there is no need<br />

to establish separate classes of service. The work associated with establishing separate classes of service is prohibitive because of the<br />

conversion to the embedded base.<br />

Pat said that the e-mail received from Stephan Calhoun on 1/22/04, confuses the request with other CRs requesting billing changes and believe<br />

that this CR can be closed.<br />

Stephan Calhoun with Cbeyond said the PCAT updates are appreciated and that he was only able to review the Qwest response on this CR<br />

yesterday. Stephan said he has concerns with the 2/3/04 Qwest response and asked that Pat read through the response.<br />

Pat read the draft response. Stephan said that his understanding is that usually classes of service define the product but not the jurisdiction. Pat<br />

disagreed saying that the jurisdiction of many Qwest products is identified by class of service.<br />

Stephan also said that interstate class of service was assigned to conversion orders that were issued last year, are also being assigned on new<br />

requests for EEL and LMCE. Pat said that the interstate EEL and LMC classes of service are only used to convert to Special Access circuits.<br />

Stephan said that he doesn’t understand the reason UMX was changed to new EEL and LMC. Cbeyond has not made any changes in the way the<br />

services were ordered. Pat Finley said that interstate was only used for conversion orders only.<br />

Stephan said that Cbeyond is concerned that billing doesn’t support the Qwest response. The billing department was not able to identify what was<br />

converted and what was a new order. There seems to be a disconnect with the policy and what is actually done. Pat explained that the Billing<br />

Center is able to access history information on the services, and to tell what is new and what was converted. Stephen said that the billing<br />

manager, service manager and process manager were unable to determine and planned to contact the product manager. Stephan has provided<br />

examples to their service manager.<br />

Stephan is also concerned that the recurring interstate and intrastate EEL do not bill the same as UNE. Pat said that PLT has different rates and<br />

is a finished service. Interstate and intrastate EEL and LMC are billed the same recurring rates. Stephan said LMC jurisdiction is based on FCC<br />

definition and doesn’t seem to fit. Stephan said the concern is not the rate itself, but the rate elements, and asked what would keep Qwest from<br />

applying different rates to interstate and intrastate. Pat asked if the concern is that Qwest may raise UNE rates that are interstate. Pat explained<br />

that Qwest is obligated to make these UNEs available to CLECs at TELRIC rates.<br />

Judy Schultz with Qwest said there are many concerns with this CR and suggested that an ad hoc meeting be scheduled to discuss. This CR will<br />

remain in Evaluation status.<br />

___________________________<br />

Thu 1/22/04 3:41 PM<br />

From; Stephan Calhoun [Stephan.Calhoun@cbeyond.net]<br />

To: Sanchez Steinke, Linda, Finley, Pat J<br />

cc; Morgan Halliday, Tom Hyde<br />

Subject; RE: Qwest Draft Response PC112003-1 (Differentiate LMC from EEL) - Cbeyond Response<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC112003-1<br />

Page 36 of 105<br />

Attachment D


Linda/Pat,<br />

I apologize for not getting this to you prior to yesterday's call. I got<br />

wrapped up in some other Qwest CRs that we received responses to at the<br />

same time. It appears that Qwest has addressed the regulatory concerns<br />

raised by the TRO in its response to this CR. Unfortunately, the billing<br />

implications on this CR appear to have been forgotten. Cbeyond has 3<br />

specific concerns to Qwest's response:<br />

1. Providing fields on the CSR for services that are billed in CRIS is<br />

not the same as for services billed in IABS. In the CRIS system, the<br />

CSR is not part of the bill. The CSR is provided as a separate file<br />

that is not in the same format as the invoice and is also not an<br />

OBF/industry standard format. Even this is a bit of a misnomer, the CSR<br />

is actually a collection of files per subaccount on an invoice. If an<br />

invoice has 2,000, the CSR is actually comprised of 2,000+ files. This<br />

is a partial explanation of why Cbeyond considers the delivery of<br />

information on the CSR as insufficient in addressing the billing concern<br />

of this CR.<br />

2. Qwest has demonstrated through reports from the billing group<br />

(because Qwest doesn't actually put the class of service on the bill),<br />

that it uses or appears to use 2 different classes of service and thus 2<br />

different sets of USOCs for the same bandwidth level, product, and<br />

jurisdiction as it applies to EELs and LMCs. Please find the attached<br />

examples.<br />

3. An even broader concern, and perhaps the subject of another CR, is<br />

that Qwest has failed to map the USOCs & Classes of Service that it<br />

bills for LMCs & EELs to a product. Conversely, the PCATs for LMCs and<br />

EELs do not define the classes of service or USOCs to be applied to the<br />

elements that define each product. Obviously, Qwest has this defined<br />

somewhere in their system, but has failed to publish it to the CLEC<br />

community.<br />

Again, I apologize if my comments caught you off guard as that was truly<br />

not my intent. I only saw the Qwest response the morning of the call and<br />

grew very concerned about what the response did not address.<br />

Sincerely,<br />

Stephan<br />

___________________<br />

01/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Pat Finley with Qwest said that Qwest held the Clarification meeting on 12/4/03 and that Qwest had sent an e-mail to Morgan Halliday stating that<br />

Qwest does not count EELs in the LMC ratio to LIS trunking. Pat reviewed the Qwest response and said that we will not establish unique classes<br />

of service for EELs and LMCs and that Qwest has created a way to distinguish EEL and LMC for the TRO by using TRAK FID. The TRAK FID<br />

information is available for CLECs on the CSR. Pat said that Qwest needed to distinguish between EELs and LMCs and has no intention of<br />

counting LMCs in the LIS trunking ratio.<br />

Stephen Calhoun with Cbeyond said he is confused by the response because in December he received one answer and then in January received<br />

another answer. The CSR is not part of the bill and is not populating the difference between EEL and LMC on the bill. It is a different process to<br />

view the CSR as opposed to looking at the bill. The Cbeyond concern is based on reports received from the billing team where LMCs and EELs<br />

have different classes of service and USOCs. LMCS or EELs could be either class of service. Stephen will provide examples.<br />

Pat Finley said there are 12 classes of service and they vary according to whether service is intrastate or interstate and the bandwidth requested.<br />

Stephen said these are brand new DS1 level, local installs and they have different classes of service assigned. In addition, when reviewing the<br />

PCAT there is a lack of documentation because LMC and EEL have no USOC mapping available to see the classes of service. Bonnie Johnson<br />

said that in reconciling bills, Qwest provides data is in so many different places, and there is a general concern that bills don’t provide enough<br />

detail to reconcile. (Begin comment from Bonnie Johnson – Eschelon) Bonnie said all of her personnel vendor bills contain the detail you need to<br />

know what you are paying for. (end comment). Carla Pardee with AT&T and Liz Balvin with MCI said they agree with Bonnie’s comments. This<br />

CR will move to Evaluation status.<br />

_____________________<br />

Mon 1/5/04 1:12 PM<br />

From; Linda Sanchez-Steinke<br />

To; 'tom.hyde@cbeyond.net'<br />

cc: Pat Finley<br />

Subject; Change Request PC112003-1<br />

Tom -<br />

The attached e-mail was sent to Morgan Halliday<br />

a couple of weeks ago regarding<br />

change request PC112003-1, titled "Differentiate between<br />

Loop-MUX combos and EELs due to different FCC<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC112003-1<br />

Page 37 of 105<br />

Attachment D


treatment (TRO Order)". I realize<br />

that with the holidays Cbeyond may not have had<br />

an opportunity to respond.<br />

Would you please let me know if Pat Finley's attached e-mail<br />

provides the information needed to resolve the<br />

change request or if the change request is still needed.<br />

Thank you<br />

Linda Sanchez-Steinke<br />

Change Request Project Manager<br />

Qwest<br />

303-382-5768<br />

-----Original Message-----<br />

From: Finley, Pat J<br />

Sent: Tuesday, December 16, 2003 4:43 PM<br />

To: 'morgan.halliday@cbeyond.net'<br />

Cc: Sanchez Steinke, Linda; Libadia, Robyn; Romano, Anthony<br />

Subject: Qwest's response to PC112003<br />

Mr. Halliday, I wanted to provide you a formal response to the primary concerns you raised on the clarification call we had on December 4, 2003,<br />

for the Change Request titled "Differentiate between Loop-MUX combos and EELs due to different FCC treatment (TRO Order)."<br />

You asked that Qwest provide you in writing, assurances that we will not count Loop-MUX combinations (LMCs) in the calculation of LIS trunking to<br />

EEL ratio, to determine service eligibility. Please consider this written confirmation, that Qwest has no intention of counting LMCs in the<br />

calculation of the LIS trunking to EEL ratio as specified in the service eligibility criteria of the Triennial Review Order.<br />

We hope this satisfies your request. Please contact me at 303 896-8466, if you have any questions.<br />

_____________________________<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Cbeyond presented this CR and said Cbeyond would like to be able to differentiate LMX and EELs class of service on billing invoices. Liz Balvin<br />

with MCI asked how they come on the bills today. Stephen Calhoun said that Qwest provides Cbeyond additional information on a spreadsheet to<br />

help differentiate, and Qwest does not have the ability to separate LMX and EEL class of service. Jamal Boudhaouia with Qwest asked if Cbeyond<br />

orders LMX by itself, or if it is part of the whole circuit being provisioned. Stephen Calhoun said there are definite differences and if look at two<br />

DS1’s there is no differentiation between LMX and EEL and there are many implications, TRO order, Performance Management Plan, Regulatory<br />

side and billing. Jamal asked if the CR is based on the TRO order and if Cbeyond is asking for differentiation between the classes of service<br />

because of TRO implications. Judy Schultz with Qwest said that we may need another clarification meeting to get clear what the CR is<br />

requesting. Bonnie Johnson with Eschelon said that she was at the clarification meeting and felt that the CR request was clear. Kit Thomte said<br />

that Pat Finley the SME was not on the call and Kit felt that the discussion wasn’t helpful if she was not involved in the discussion. This CR will<br />

move to Presented status.<br />

_____________________________<br />

Tue 12/16/03 4:43 PM<br />

From; Pat Finley<br />

To; 'morgan.halliday@cbeyond.net'<br />

cc: Sanchez Steinke, Linda; Libadia, Robyn; Romano, Anthony<br />

Subject; Qwest's response to PC112003<br />

Mr. Halliday, I wanted to provide you a formal response to the primary concerns you raised on the clarification call we had on December 4, 2003,<br />

for the Change Request titled "Differentiate between Loop-MUX combos and EELs due to different FCC treatment (TRO Order)."<br />

You asked that Qwest provide you in writing, assurances that we will not count Loop-MUX combinations (LMCs) in the calculation of LIS trunking to<br />

EEL ratio, to determine service eligibility. Please consider this written confirmation, that Qwest has no intention of counting LMCs in the<br />

calculation of the LIS trunking to EEL ratio as specified in the service eligibility criteria of the Triennial Review Order.<br />

We hope this satisfies your request. Please contact me at 303 896-8466, if you have any questions.<br />

_____________________________<br />

CLEC Change Request<br />

Clarification <strong>Meeting</strong><br />

2:00 p.m. (MDT) / Thursday December 4, 2003<br />

1-877-572-8687<br />

3393947#<br />

PC112003-1 Differentiate between Loop-MUX combos and EELs due to different FCC treatment (TRO Order)<br />

Name/Company:<br />

Morgan Halliday, Cbeyond<br />

Tom Hyde, Cbeyond<br />

Stephen Calhoun, Cbeyond<br />

Kim Isaccs, Eschelon<br />

Bonnie Johnson, Eschelon<br />

Pat Finley, Qwest<br />

Carl Sear, Qwest<br />

Tony Romano, Qwest<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC112003-1<br />

Page 38 of 105<br />

Attachment D


Paul Johnson, Qwest<br />

Introduction of Attendees<br />

Qwest welcomed all attendees to the meeting.<br />

Review Requested (Description of) Change<br />

Linda Sanchez-Steinke with Qwest read the description of change from the submitted change request; Seperately identify LMCs and EELs on<br />

bills.<br />

Tom Hyde with Cbeyond said that the primary part of the TRO is the ratio of, or test for EELs (high cap) to LIS trunking with the new service<br />

eligibility criteria. Since Qwest uses the same classes of services and USOCs for EELs and LMCs as are used for PLTS. Pat Finley with Qwest<br />

clarified that the TRO ratio is the number of interconnection trunks to EELs, however LMCs (Loop Mux Combinations) are excluded from the ratio<br />

requirement. Tom answered that Cbeyond would be satisfied if Qwest will acknowledge in writing that LMC is to be excluded from the service<br />

eligibility criteria (safe harbor), and therefore would be excluded from the LIS trunking to EEL ratio, that would satisfy Cbeyond’s concern.<br />

In the CPAP Qwest is lumping EELs and LMCs together. Tom said that Qwest is the only ILEC that has EELs and LMCs under the same class of<br />

service.<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

Loop Mux Combo and EEL billing<br />

Confirm Right Personnel Involved<br />

Correct Qwest personnel were involved in the clarification meeting<br />

Identify/Confirm CLEC’s Expectation<br />

Extablish different class of service for LMCs and EELs<br />

Identify any Dependent Systems Change Requests<br />

None identified.<br />

Establish Action Plan (Resolution Time Frame)<br />

Cbeyond will present this CR at the December <strong>CMP</strong> meeting. Qwest will provide a response in January <strong>2004</strong>.<br />

Qwest Response<br />

February 3, <strong>2004</strong><br />

DRAFT RESPONSE<br />

For Review by the CLEC Community and Discussion at the February <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Morgan Halliday<br />

Cbeyond Communications, LLC<br />

SUBJECT: Qwest’s Change Request Draft Response - PC112003-1<br />

"Differentiate between Loop-MUX combos and EELs due to different FCC treatment (TRO Order)"<br />

This letter is in response to the CLEC Change Request PC112003-1, that requests LMC (Loop Mux Combination) be assigned a unique class of<br />

service, to separately identify LMC from EEL (Enhanced Extended Loop) due to requirements in the Triennial Review Order (the Order).<br />

Qwest will not establish a separate class of service for LMC. Qwest will provide a link to a downloadable document in both the EEL and LMC<br />

PCATs that will identify USOCs that are utilized with XUMAX and UBNWN classes of service. This action will enable our customers to map<br />

EEL/LMC classes of service to USOCs for billing. The estimated costs to establish a separate class of service for LMC and convert the embedded<br />

base are considerable. Establishing a separate LMC class of service will not solve all of the billing issues Cbeyond has raised in subsequent<br />

meetings on this Change Request.<br />

In the email Mr. Calhoun sent to Qwest dated 1-22-<strong>2004</strong>, he listed examples of EEL and LMC circuits that have two different classes of service<br />

(interstate and intrastate) with two different sets of USOCs for the same bandwidth, product and jurisdiction. When Cbeyond’s PLT (Private Line<br />

Transport) circuits were converted to either EEL or LMC, the jurisdiction, circuit id, and billing USOCs remained the same as when billed and<br />

provisioned as PLT circuits. To prevent service interruptions during the conversion, the class of service on the PLT record is converted to the<br />

EEL/LMC equivalent. There is no difference in recurring billing between the inter- and intrastate EEL/LMC classes of service and USOCs. The<br />

use of both retail and EEL/LMC product specific USOCs is explained in detail in the LMC and EEL PCATs.<br />

In addition to the downloadable spreadsheet we will make available in the PCATs, we have established the TRAK FID and datasets that allow you<br />

and Qwest to differentiate between LMC and EEL. With this differentiation, Qwest will not include LMC circuits in your LIS to EEL ratio<br />

requirements per the Order service eligibility requirements. We believe these actions will address your specific concerns with billing associated<br />

with EEL and LMC. Your other pending change requests will help resolve the other issues you have raised with Qwest’s bills.<br />

Sincerely,<br />

Pat Finley<br />

<strong>Product</strong> Manager<br />

_____________________<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC112003-1<br />

Page 39 of 105<br />

Attachment D


January 13, <strong>2004</strong><br />

DRAFT RESPONSE<br />

For Review by the CLEC Community and Discussion at the January <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Morgan Halliday<br />

Cbeyond Communications, LLC<br />

SUBJECT: Qwest’s Change Request Response - PC112003-1<br />

"Differentiate between Loop-MUX combos and EELs due to different FCC treatment (TRO Order)"<br />

This letter is in response to the CLEC Change Request PC 112003-1, that requests EELs (Enhanced Extended Loops) and LMCs (Loop Mux<br />

Combinations) be assigned unique classes of service, to separately identify the services due to requirements of the Triennial Review Order (the<br />

Order).<br />

Qwest has researched this issue, and we will not be establishing separate classes of service and USOCs (Universal Service Order Codes) for<br />

EELs and LMCs. We have however, provided a method for you to validate, or identify EEL from LMC circuits, by using a FID (Field Identifier)<br />

called TRAK, which is a tracking code. If the circuit is an EEL, the dataset, or entry following TRAK FID on the CSR (Customer Service Record)<br />

will be IEEL. This entry will be shown following the class of service on the CSR. LMC circuits will be identified by the dataset ILMC after the TRAK<br />

FID. This information has been added to all EEL and LMC accounts in our embedded base, and it is a required service order entry on new EEL<br />

and LMC requests. We are able to produce reports that display the information, and we are working on producing reports from our order<br />

processing system to ensure the entries are appropriately made, when required. We are confident that this will allow us to validate the 24-to-1<br />

EEL to interconnection trunk ratio specified in the Order (paragraph 608). Please recall that the Order provides for tests based on the service<br />

eligibility criteria conducted by an independent auditor to insure that high capacity combinations such as DS1 and DS3 EELs are used for local<br />

voice service.<br />

As noted in the Order, if Qwest requests an audit, the independent auditor will evaluate compliance with the service eligibility criteria. The<br />

compliance testing will be designed by the independent auditor, and Qwest will provide all documentation requested to satisfy standard auditing<br />

principles. The independent auditor will perform an "examination engagement", and issue an opinion regarding Qwest’s and the CLECs<br />

compliance with the service eligibility criteria (paragraph 626).<br />

Sincerely,<br />

Patricia J. Finley<br />

<strong>Product</strong> Manager<br />

Qwest Communications, Inc.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC112003-1<br />

Page 40 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC120803-1 Associated Move Orders Evaluation Wholesale ProdProc Billing,<br />

2/18/04<br />

Maintenance/Rep<br />

air, Provisioning<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Revised Description of Change 02-03-04<br />

UNE, UNE-P,<br />

Resale, Unbundled<br />

Loops, <strong>Product</strong>s<br />

When a CLEC submits a move order (M) Qwest creates two orders, a to (T) and from (F) order. The problem resides in the fact that these orders<br />

are associated with each other but no action is taken when the T order is placed in jeopardy and the F order is not stopped. Clarification calls with<br />

Qwest has indicated that the F order is "always" worked prior to the T order. This process is a guarantee that the customer will be taken out of<br />

service prior to the T order being completed regardless of jeopardy, and the jeopardy will cause the the customer to be out of service for a longer<br />

period of time. When Qwest works the T order and the technician determines that the order cannot be completed as expected (either jeopardized<br />

for some reason or there is no access to the new site) there is no electronic/mechanical means of associating the T order to the F order. Some<br />

scenarios are:<br />

1) customer has X number of TN's and is moving within a building and retaining the same TN's.<br />

2) customer has X number of TN's is moving to another building within the same rate center and retaining the same TN's.<br />

3) Customer has X number of TN's and is moving within the same rate center but does not want to keep all of the TN's.<br />

4) customer has X number of TN's and is moving and wants to change TN's and have a forwarding message on the old TN's.<br />

In each of these instances the customer is taken out of service with the creation of the two orders and the F order being worked, or batched, prior<br />

to the T order being completed. Since it is a Qwest process to create two orders it would be Qwest responsibility to ensure a process that would<br />

prevent taking the customer out of service.<br />

Revised Expected Deliverable (02-03-04):<br />

That no customer would be taken out of service on any move order.<br />

Original Description of Change (12-08-03):<br />

When a CLEC submits a move order (M) Qwest creates two orders, a to (T) and from (F) order. The problem resides in the fact that these orders<br />

are not associated as related orders. It is an industry standard that related orders be associated in the RORD field in an effort to ensure that<br />

service is not interrupted. When Qwest works the T order and the technician determines that the order cannot be completed as expected (either<br />

jeopardized for some reason or there is no access to the new site) there is not electronic/mechanical means of associating the T order to the F<br />

order. Since these orders are not associated as RORD the F order is completed and the customer is taken out of service resulting in a disconnect<br />

in error.<br />

Original Expected Deliverable (12-08-03):<br />

Expected Deliverable: <strong>Process</strong>es be changed to associate all T&F orders to each other. That systems be modified to ensure that if a related T<br />

order is jeopardized that the F order is automatically placed in a jep status and the work to disconnect the order is stopped. Expected result will<br />

reduce, if not eliminate, disconnects in error because of a jeopardized T order. In the month of November AT&T had 10 disconnects in error<br />

because of jeopardized T orders. In the event the F order is completed before the T order on the due date and the T order is jepped, Qwest should<br />

immediately re-instate the service in an effort to prevent an out of service condition .<br />

Status History<br />

12/08/03 - CR Submitted<br />

12/09/03 - CR Acknowledged<br />

12/15/03 - Held Clarification <strong>Meeting</strong><br />

12/17/03 - December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/26/03 - Changed title of CR to Associated Move Orders<br />

01/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

01/28/04 - Held second Clarification <strong>Meeting</strong><br />

02/03/04 - Change request revised by AT&T, see description of change and expected deliverable<br />

02/06/04 - Held Clarification <strong>Meeting</strong><br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

03/05/04 - Qwest sent PROS.03.05.04.F.01462.NetCommCallCustRec.doc<br />

Project <strong>Meeting</strong>s<br />

Schultz, Judy<br />

Adkisson, Ann B.<br />

Davis, Qiana<br />

Sanchez-Steinke, Linda<br />

Information Current as of:<br />

Report Name:<br />

Originator Company Name:<br />

AT&T<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

12<br />

<strong>Product</strong>s<br />

Impacted<br />

PC120803-1<br />

Page 41 of 105<br />

Attachment D


02/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Qiana Davis with Qwest reviewed the draft response and said that AT&T had revised the CR on 2/3/04 and that Qwest is evaluating the<br />

modifications and require additional time to respond to the CR. Qiana added that Qwest would provide an update in <strong>March</strong>. Carla Pardee with<br />

AT&T said AT&T had determined that a process does exist, however AT&T has had several examples where the orders are disconnected. Carla<br />

also said they have been working with their service management team on this issue as well. Qwest will provide an update in <strong>March</strong>. This CR will<br />

be moved to Evaluation status.<br />

_______________________<br />

CLEC Change Request<br />

Clarification <strong>Meeting</strong><br />

2:30 p.m. (MDT) / Friday February 6, <strong>2004</strong><br />

1-877-572-8687<br />

3393947#<br />

PC120803-1 Associated Move Orders<br />

Name/Company:<br />

Ann Adkisson, AT&T<br />

Carla Pardee, AT&T<br />

Ervin Rea, AT&T<br />

Cheryl Peterson, AT&T<br />

David Belanger, AT&T<br />

Joyce Perry, AT&T<br />

Jim Recker, Qwest<br />

Mike Lanoue, Qwest<br />

Jerry Jenson, Qwest<br />

Qiana Davis, Qwest<br />

Pat Torkelson, Qwest<br />

Brenda DeFilippo, Qwest<br />

Doug Slominski, Qwest<br />

Lydell Peterson, Qwest<br />

Danelle Haynes, Qwest<br />

Linda Sanchez-Steinke, Qwest<br />

Introduction of Attendees<br />

Qwest welcomed all attendees to the meeting.<br />

Review Requested Change<br />

Linda Sanchez-Steinke with Qwest said that we are holding this clarification call to discuss the revisions AT&T made to the CR on 2/3/04.<br />

Linda read the description of change; When a CLEC submits a move order (M) Qwest creates two orders, a to (T) and from (F) order. The<br />

problem resides in the fact that these orders are associated with each other but no action is taken when the T order is placed in jeopardy and the F<br />

order is not stopped. Clarification calls with Qwest has indicated that the F order is "always" worked prior to the T order. This process is a<br />

guarantee that the customer will be taken out of service prior to the T order being completed regardless of jeopardy, and the jeopardy will cause<br />

the the customer to be out of service for a longer period of time. When Qwest works the T order and the technician determines that the order<br />

cannot be completed as expected (either jeopardized for some reason or there is no access to the new site) there is no electronic/mechanical<br />

means of associating the T order to the F order. Some scenarios are:<br />

1) customer has X number of TN's and is moving within a building and retaining the same TN's.<br />

2) customer has X number of TN's is moving to another building within the same rate center and retaining the same TN's.<br />

3) Customer has X number of TN's and is moving within the same rate center but does not want to keep all of the TN's.<br />

4) customer has X number of TN's and is moving and wants to change TN's and have a forwarding message on the old TN's.<br />

In each of these instances the customer is taken out of service with the creation of the two orders and the F order being worked, or batched, prior<br />

to the T order being completed. Since it is a Qwest process to create two orders it would be Qwest responsibility to ensure a process that would<br />

prevent taking the customer out of service.<br />

Expected Deliverable: That no customer would be taken out of service on any move order.<br />

Ervin Rea with AT&T said that this CR was revised as a result of the <strong>CMP</strong> clarification meeting 1/28/04 and the <strong>CMP</strong> meeting 1/21/04. If Qwest<br />

always works the F order first and if the F order is in a batch that is disconnected shortly after midnight on the due date then the business<br />

customer is always going to be out of service. Additionally, if there is a jep on the T order, then the business customer will be out of service for an<br />

extended amount of time.<br />

Cheryl Peterson with AT&T said that when she did a search on the Qwest web site, searching for “Move” she found three processes that say the F<br />

order is due the day after the due date of the T. The port within process<br />

http://www.qwest.com/wholesale/downloads/2003/030513/DNLD_PortWithin_<strong>Process</strong>10_05-13-03.doc<br />

Cheryl asked if there is an existing ordering process in place, would there be a need for a CR. Linda Sanchez-Steinke with Qwest said that she<br />

was not sure if a CR would be required for adherence of the process and would take the question back.<br />

Ervin said that he would still want to have adherence to the process through Service Management.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC120803-1<br />

Page 42 of 105<br />

Attachment D


Jim Recker with Qwest asked if we find the process is correct would that satisfy the request. Ervin said no it would not satisfy the request. The<br />

process should say that there should not be a disconnect of the F location.<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

Primarily UNE-P and POTS Residence and Business. Other products include Resale, Unbundled Loops and any products T&F orders are issued<br />

for when there is a move and there is a jeopardy situation.<br />

Confirm Right Personnel Involved<br />

Correct Qwest personnel were involved in the clarification meeting.<br />

Identify/Confirm CLEC’s Expectation<br />

Expected Deliverable: That no customer would be taken out of service on any move order.<br />

Identify any Dependent Systems Change Requests<br />

None identified.<br />

Establish Action Plan<br />

This CR will be discussed at the February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

_______________________<br />

Tue 2/3/04 11:46 AM<br />

From: Pardee, Carla D, NKLAM [cdickinson@att.com]<br />

To: Sanchez Steinke, Linda<br />

cc: Rea, Ervin E, NKLAM, Adkisson, Ann B, NKLAM, Perry, Joyce M, NKLAM, Peterson, Cheryl J, NKLAM, Peterson, Lydell<br />

Subject: Amended PC 120803-1<br />

Linda - per the Audix I left you a few minutes ago, please find the amended language to PC 120803-1. AT&T would like to set up another meeting<br />

to discuss this, at your earliest convenience - if possible this Friday, or early next week. I know we discussed submitting a new CR, but AT&T<br />

prefers to amend the language so that we don't lose any additional time resolving and implementing this CR. Please feel free to call me at 303-<br />

647-2234 if we need to discuss further. As usual, thanks for your assistance and help with this change request!<br />

_______________________<br />

CLEC Change Request<br />

Clarification <strong>Meeting</strong><br />

8:30 a.m. (MDT) / Wednesday January 28, <strong>2004</strong><br />

1-877-572-8687<br />

3393947#<br />

PC120803-1 Associated Move Orders<br />

Name/Company:<br />

Ann Adkisson, AT&T<br />

Carla Pardee, AT&T<br />

Irvin Rea, AT&T<br />

Sheryl Peterson, AT&T<br />

David Belanger, AT&T<br />

Joyce Perry, AT&T<br />

Jim Recker, Qwest<br />

Mike Lanoue, Qwest<br />

Jerry Jenson, Qwest<br />

Jeanette Barns, Qwest<br />

Qiana Davis, Qwest<br />

Kit Thomte, Qwest<br />

Pat Torkelson, Qwest<br />

Brenda DeFilippo, Qwest<br />

Linda Sanchez-Steinke, Qwest<br />

Introduction of Attendees<br />

Qwest welcomed all attendees to the meeting.<br />

Review Requested (Description of) Change<br />

Linda Sanchez-Steinke with Qwest said that we are holding a second clarification call to discuss this CR and the CR may be amended as a result<br />

of this clarification meeting.<br />

Linda read the description of change; When a CLEC submits a move order (M) Qwest creates two orders, a to (T) and from (F) order. The<br />

problem resides in the fact that these orders are not associated as related orders. It is an industry standard that related orders be associated in<br />

the RORD field in an effort to ensure that service is not interrupted. When Qwest works the T order and the technician determines that the order<br />

cannot be completed as expected (either jeopardized for some reason or there is no access to the new site) there is not electronic/mechanical<br />

means of associating the T order to the F order. Since these orders are not associated as RORD the F order is completed and the customer is<br />

taken out of service resulting in a disconnect in error.<br />

Expected Deliverable: <strong>Process</strong>es be changed to associate all T&F orders to each other. That systems be modified to ensure that if a related T<br />

order is jeopardized that the F order is automatically placed in a jep status and the work to disconnect the order is stopped. Expected result will<br />

reduce, if not eliminate, disconnects in error because of a jeopardized T order. In the month of November AT&T had 10 disconnects in error<br />

because of jeopardized T orders. In the event the F order is completed before the T order on the due date and the T order is jepped, Qwest should<br />

immediately re-instate the service in an effort to prevent an out of service condition.<br />

David Belanger with AT&T said the description of change sounds like what the UNE-P group is looking for and if Qwest relates the T&F orders the<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC120803-1<br />

Page 43 of 105<br />

Attachment D


issue will be resolved.<br />

Irvin Rea with AT&T said that the problem is the two orders are not related beyond creation of the orders. Joyce Perry with AT&T said the problem<br />

is that Qwest works the F order around mid-might before the T order is worked. AT&T wants the T order worked first, then if the T is jeoped the F<br />

be jeoped at the same time. Irvin clarified that AT&T doesn’t want the F order worked until the T order is completed.<br />

Brenda DeFilippo with Qwest asked if the T & F orders have different phone numbers. AT&T said that in some cases there would be different<br />

phone numbers.<br />

David Belanger said the T order must complete when worked before the F order and then the F order should have 24 hours to complete.<br />

Sheryl Peterson with AT&T asked her group if they really understand the process.<br />

Mike Lanoue with Qwest gave examples of different types of orders 1) if in same central office, same telephone number same wire center 2) in<br />

different central office, different telephone number<br />

Irvin said if the CLEC issues a move order, RORD has to be filled out by Qwest<br />

Qiana Davis with Qwest asked if the only type of orders that we would be concerned with were move orders and the activity of T. Irvin answered<br />

yes.<br />

Qiana asked if the orders are residence or business accounts and if the business is still located at the from address. Irvin said both Business and<br />

Residence. David Belanger said that the business is not always still located at the old address and sometimes someone goes back to the old<br />

address to answer phones. Qiana asked if the T order is jeoped would remote call forwarding help the situation. Irvin answered that partial remote<br />

call forwarding and David added that the disconnect recording is played.<br />

Sheryl Peterson with AT&T asked if the normal Qwest process was to batch down stream the orders worked at night. Sheryl clarified her question<br />

and said not batch as CLEC sending volumes, but talking about on due date working in the appropriate central offices. Jim Recker said that if<br />

frame due time is not requested, the F will be worked shortly after midnight on the due date.<br />

Brenda DeFilippo with Qwest said if T&F and the same TN, those are worked together. If T&F with different TN then the F comes through as<br />

disconnect.<br />

Irvin said that when issuing a move order with action of T, then create 2 orders, the F order should have a disconnect date of the day after the T is<br />

due.<br />

Brenda asked if same TN at different location. Jeanette Barns asked if the customer has vacated the location.<br />

AT&T had further discussion on whether or not all the products with scenarios were captured in the <strong>CMP</strong> CR submitted; same TN, different TN,<br />

customer has already moved from location and intercept message.<br />

As a result of this clarification meeting, AT&T will meet internally and determine what exact change they are requesting; and identify products and<br />

scenarios for this change request. AT&T will either submit revisions and scenarios to this change request or submit a new change request.<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

Currently CR reads: UNE-P, All POTS, Resale, Unbundled Loops and any products T&F orders are issued for when there is a move and there is a<br />

jeopardy situation.<br />

Confirm Right Personnel Involved<br />

Correct Qwest personnel were involved in the clarification meeting.<br />

Identify/Confirm CLEC’s Expectation<br />

Identify any Dependent Systems Change Requests<br />

None identified.<br />

Establish Action Plan (Resolution Time Frame)<br />

AT&T will meet internally meet determine what revisions are needed to the current CR or submit a new CR.<br />

_________________________<br />

01/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Ervin Rea with AT&T presented this CR and said when a CLEC submits a move order, Qwest creates two orders, an install and a disconnect.<br />

These two orders should be associated so that if something goes wrong with the install then the disconnect does not get worked. Ervin asked if<br />

the F order is worked first thing in the morning. Qiana Davis with Qwest said yes, Qwest works the disconnect order first. Ervin said that if the T is<br />

jeoped then AT&T wants to put the customer back in service. Qiana said that the F is worked to release the facilities. Ervin asked why the TN<br />

can’t be working in both locations. Qiana said that Qwest does offer Dual Service.<br />

Bonnie Johnson with Eschelon said that she sent an e-mail concerning when a dispatch is required on T&F orders, a technician working on the T<br />

order that is jeoped and the F is worked in the switch. Bonnie’s concern is connected to this CR and her service manager had called about the<br />

question. Linda Sanchez-Steinke with Qwest said she did not understand that the question was related to the CR. Bonnie also said that Dual<br />

Service requires two different due dates (Begin comment from Bonnie Johnson – Eschelon) and that is not what we are asking for. Bonnie said<br />

that for example, if the ”F” side of the T&F is flow through the customers service would be disconnected at the old location after midnight on the<br />

due date because of the way Qwest service orders flow through the system (D’s and F’s or disconnects go first) and Qwest agreed. Then if the “T”<br />

side required a dispatch and the tech could not instal until 5PM on the due date, the customer could be out of service for serveral hours. (end<br />

comment). Jim Recker with Qwest asked if AT&T requests frame due time on their orders. Ervin said that the orders may not be designed<br />

services. Liz Balvin with MCI added that DFDT is desired, and is not guaranteed that disconnect will be completed at the desired time. Qiana<br />

asked AT&T to identify the products. Ervin said that the products are Resale, UNE-P, Unbundled Loops.<br />

Qwest will arrange an additional clarification meeting for additional questions and the CR may need to be modified based on the clarification<br />

meeting output. Mike Zulevic with Covad said that when he worked on UNE-P orders if they resided in the same central office the same person did<br />

the work. If there was an F in another central office, the F was worked at midnight on the due date. Bonnie said there are two pieces to the CR;<br />

What should be done when the T order goes into jeopardy status and what needs to be done to relate the two orders. This CR will move to<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC120803-1<br />

Page 44 of 105<br />

Attachment D


Presented status.<br />

_________________________<br />

Wed 12/24/03 9:01 AM<br />

To: Sanchez Steinke, Linda<br />

From: Pardee, Carla D, NKLAM [cdickinson@att.com]<br />

cc: Rea, Ervin E, NKLAM<br />

Subject: RE: PC120803-1 Move Orders Associated<br />

Sorry for the delay in getting back to you Linda - been getting kicked off of my computer. I believe we agreed to change it to "Associated Move<br />

Orders." Thanks for taking care of this. Happy Holidays<br />

_________________________<br />

From: Sanchez Steinke, Linda<br />

Sent: Tuesday, December 23, 2003 2:15 PM<br />

To: Pardee, Carla D, NKLAM<br />

Subject: PC120803-1 Move Orders Associated<br />

Carla -<br />

During the <strong>CMP</strong> meeting did AT&T agree to change<br />

the name of this CR to "Associated Move Orders"<br />

or something different than currently titled?<br />

Would you let me know the title and I will<br />

change in the database.<br />

Thank you<br />

Linda Sanchez-Steinke<br />

CRPM<br />

Qwest<br />

303-382-5768<br />

________________________<br />

Tue 12/16/03 9:24 AM<br />

From; Johnson, Bonnie J. [bjjohnson@eschelon.com]<br />

To: Sanchez Steinke, Linda<br />

cc:<br />

Subject; Question for AT&T CR<br />

Linda,<br />

Here is my question:<br />

As it relates to a T&F order, excluding a jeopardy on the "T" order, does<br />

Qwest always keep the "F" side of the order (customers service at the old<br />

location) working until the "T" side is installed. I would like the answer<br />

for tech dispatch and flow through orders that do not require a dispatch.<br />

It was always my understanding that the Qwest tech had the "F" order worked<br />

(switch) after he installed the new line at the prem Can you confirm and<br />

tell me how it works when there is no tech?<br />

I am asking the question because I hear the CLECs continue to talk about<br />

their customers being impacted and out of service with moves even if a<br />

jeopardy condition does not exist. Perhaps we could address both issues if<br />

there is one.<br />

Thanks!<br />

Bonnie J. Johnson<br />

Director Carrier Relations<br />

Eschelon Telecom, Inc.<br />

Phone 612 436-6218<br />

Fax 612 436-6318<br />

Cell 612 743-6724<br />

bjjohnson@eschelon.com <br />

________________________<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Ervin Rea with AT&T discussed this CR and said when a CLEC submits a move order, Qwest creates a T&F order. The T order is to install at the<br />

new location and the F order is to disconnect at the old location. If something happens to the T order, the F order completes. When the F order<br />

completes, then the CLEC has to scramble to get the service back up at one of the locations. AT&T would like the T & F orders linked so that if<br />

anything happens to the T order then the F order is jep’d at the same time. Carla thinks there are system implications and wants this addressed<br />

as soon as possible to identify. Connie Winston will work with the business to see how systems are effected. _________________________<br />

CLEC Change Request<br />

Clarification <strong>Meeting</strong><br />

8:30 a.m. (MDT) / Monday December 15, 2003<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC120803-1<br />

Page 45 of 105<br />

Attachment D


1-877-572-8687<br />

3393947#<br />

PC120803-1 Move Orders Associated<br />

Name/Company:<br />

Ann Adkisson, AT&T<br />

Patty Garnier, AT&T<br />

Carla Pardee, AT&T<br />

Colleen Forbes, AT&T<br />

Kim Isaccs, Eschelon<br />

Bonnie Johnson, Eschelon<br />

P.J. Koller, Priority One Telecommunications<br />

Shon Higer, Qwest<br />

Linda Sanchez-Steinke, Qwest<br />

Introduction of Attendees<br />

Qwest welcomed all attendees to the meeting.<br />

Review Requested (Description of) Change<br />

Linda Sanchez-Steinke with Qwest read the description of change from the submitted change request; When a CLEC submits a move order (M)<br />

Qwest creates two orders, a to (T) and from (F) order. The problem resides in the fact that these orders are not associated as related orders. It is<br />

an industry standard that related orders be associated in the RORD field in an effort to ensure that service is not interrupted. When Qwest works<br />

the T order and the technician determines that the order cannot be completed as expected (either jeopardized for some reason or there is no<br />

access to the new site) there is not electronic/mechanical means of associating the T order to the F order. Since these orders are not associated<br />

as RORD the F order is completed and the customer is taken out of service resulting in a disconnect in error.<br />

Carla Pardee with AT&T & P.J. Koller with Priority One Telecommunications, discussed the products impacted would include; UNE-P, All POTS,<br />

Resale, Unbundled Loops and, any products where T&F orders are issued when there is a move and there is a jeopardy situation.<br />

Bonnie Johnson with Eschelon had a question regarding jeopardy conditions, related to dispatch of technician on T & F orders. Bonnie will e-mail<br />

the question to Linda Sanchez-Steinke.<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

UNE-P, All POTS, Resale, Unbundled Loops and any products T&F orders are issued for when there is a move and there is a jeopardy situation.<br />

Confirm Right Personnel Involved<br />

Correct Qwest personnel were involved in the clarification meeting.<br />

Identify/Confirm CLEC’s Expectation<br />

Linda Sanchez-Steinke read the Expected Deliverable; <strong>Process</strong>es be changed to associate all T&F orders to each other. That systems be<br />

modified to ensure that if a related T order is jeopardized that the F order is automatically placed in a jep status and the work to disconnect the<br />

order is stopped. Expected result will reduce, if not eliminate, disconnects in error because of a jeopardized T order. In the month of November,<br />

AT&T had 10 disconnects in error because of jeopardized T orders. In the event the F order is completed before the T order on the due date and<br />

the T order is jepped, Qwest should immediately re-instate the service in an effort to prevent an out of service condition.<br />

Identify any Dependent Systems Change Requests<br />

Carla Pardee said there may be a systems change request and she would check on any systems change requests issued.<br />

Establish Action Plan (Resolution Time Frame)<br />

AT&T will walk on this CR at the December <strong>CMP</strong> <strong>Meeting</strong>. Qwest will provide a response in February.<br />

Qwest Response<br />

<strong>March</strong> 9, <strong>2004</strong><br />

DRAFT RESPONSE<br />

For Review by the CLEC Community and Discussion at the <strong>March</strong> <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Ann Adkisson<br />

AT&T<br />

SUBJECT: Qwest’s Change Request Response - PC120803-1<br />

Associated Move Orders<br />

Description of request (partial): (Revised Description of Change 02-03-04) When a CLEC submits a move order (M) Qwest creates two orders, a<br />

(T) and from (F) order. The problem resides in the fact that these orders are associated with each other but no action is taken when the T order is<br />

placed in jeopardy and the F order is not stopped. Clarification calls with Qwest has indicated that the F order is "always" worked prior to the T<br />

order. This process is a guarantee that the customer will be taken out of service prior to the T order being completed regardless of jeopardy, and<br />

the jeopardy will cause the customer to be out of service for a longer period of time. When Qwest works the T order and the technician determines<br />

that the order cannot be completed as expected (either jeopardized for some reason or there is no access to the new site) there is no<br />

electronic/mechanical means of associating the T order to the F order.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC120803-1<br />

Page 46 of 105<br />

Attachment D


Response: Qwest and CLECs acknowledge the long-standing process for outside moves is a two order process for all non-designed services<br />

(e.g., Resale and UNE_P POTS) and some designed services (e.g., Unbundled Loops). For non-designed services, the association of the two<br />

orders is inherent within the process in that there is always a T order associated with an F order. Designed services utilize "critically related order"<br />

(e.g., CRO) entries to relate two orders, (e.g., N and D order types). These order and process designs are used for both Qwest Retail and<br />

Wholesale accounts and are an integral part of both Qwest systems and processes. To change these would require a complete redesign of<br />

multiple systems, internal processes/documentation and training at an extraneous cost to Qwest without real benefit. Instead, Qwest has reviewed<br />

and analyzed the existing process for outside moves and has summarized the processes and findings as follows.<br />

T & F orders in the same central office with no change to the telephone numbers are automatically sequenced and the provisioning is coordinated<br />

in the Qwest systems for both dispatched and non dispatched orders. If the T & F are located in different wire centers with same day due date,<br />

sequencing does not occur and the F order is worked on due date after 12:01 A. M.<br />

There are two basic reasons for "jeopardizing" the T & F orders; Qwest reasons or Customer reasons. When an order is jeopardized for Qwest<br />

reasons (e.g., CF - Qwest Facilities are not available), the T order is delayed until Qwest facilities become available. At the point Qwest<br />

determines the T order is going to be delayed, the customer of record is contacted to determine if the F order should continue through the process<br />

to disconnect the existing service. Qwest makes every attempt to contact the customer of record to determine the disposition of the "F" order. If<br />

the T portion of the order is CF'd (held for no facilities), and the customer of record is not contacted the F order will be put on hold until the<br />

customer of record is contacted.<br />

The Designed service process generates various order types within Qwest and is dependent upon the product type. If a designed service order is<br />

jeopardized, Qwest will contact the customer to determine if the customer wants to continue forward with disconnect activity. The orders are<br />

critically related and are worked together.<br />

Additionally, in response to Cheryl Peterson’s finding within the PortWithin process document<br />

(http://www.qwest.com/wholesale/downloads/2003/030513/DNLD_PortWithin_<strong>Process</strong>10_05-13-03.doc), which states "On a full conversion, Qwest<br />

will issue the disconnect of the trunks and facility at the old location, due one business day after the port order DD". This process acts as a<br />

product process guide specifically for the DID product.<br />

Findings: In reviewing/analyzing the processes and associated examples, Qwest determined:<br />

- Qwest technicians, on rare occasions, were not adhering to the process of contacting the customer of record a jeopardy situation.<br />

- the "can be reached" information provided by the CLEC does not provide the technician with a "live person" with whom the technician can work<br />

the issue of the pending disconnect.<br />

Conclusion: Qwest accepts this <strong>CMP</strong> CR and has identified the following activities to enable closure:<br />

- We are in the process of enhancing the CLEC documentation (PCAT) for T&F orders to reinforce the importance of supplying a can be reached<br />

number which allows Qwest to contact the customer of record.<br />

- We have issued a Communicator to selected Network groups to reinforce the process of contacting the customer in jeopardy situations to<br />

determine the disposition of the F orders (disconnect).<br />

- Qwest currently offers specific optional services to the CLECs that may remedy some of the unique requirements of some move activities, e.g.,<br />

dual service, overlapping service, etc. Qwest’s PCAT(s) will be updated by 4/19/04 to provide CLECs with more detailed information about these<br />

options.<br />

- Qwest will continue to review its current processes and seek opportunities for improvement.<br />

Sincerely,<br />

Qiana Davis - Sr. <strong>Process</strong> Analyst, Wholesale Service and Delivery<br />

Jim Recker - Staff Advocate, Qwest<br />

_________________________<br />

February 6, <strong>2004</strong><br />

DRAFT RESPONSE<br />

For Review by CLEC Community and Discussion at the February <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Ann Adkisson<br />

AT&T<br />

SUBJECT: Qwest’s Change Request Response - PC120803-1 Associated Move Orders<br />

AT&T is requesting process and system changes related to T and F orders. "The problem resides in the fact that these orders are associated with<br />

each other but no action is taken when the T order is placed in jeopardy and the F order is not stopped".<br />

On January 28, 2003, a second clarification meeting was held to review the description of the requested change. As a result of this meeting, AT&T<br />

decided to meet internally and amend the initial <strong>CMP</strong> CR to now include the exact change requested along with detailed scenarios.<br />

On February 3, <strong>2004</strong>, Qwest received the amended version of <strong>CMP</strong> CR PC-120803-1 and are currently evaluating the change request. Therefore,<br />

we require additional time to investigate and will provide a response at the <strong>March</strong> <strong>CMP</strong> meeting.<br />

Sincerely,<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC120803-1<br />

Page 47 of 105<br />

Attachment D


Qiana M. Davis<br />

FTS <strong>Process</strong> Specialist<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC120803-1<br />

Page 48 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC120903-1 Qwest will track "access required"<br />

information in its systems when Qwest<br />

installs new service, or when Qwest<br />

dispatches on the repair of an existing<br />

line/circuit. Qwest will make the information<br />

available to CLECs for use when a CLEC<br />

opens arepair ticket<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc<br />

Title: Qwest will track "access required" information in its systems when Qwest installs new service, or when Qwest dispatches on the repair of an<br />

existing line/circuit. Qwest will make the information available to CLECs for use when a CLEC opens a repair ticket for a CLEC end user customer.<br />

Eschelon requests that Qwest develop and train a process that tracks if Qwest will require access to the customer premise to perform repair and<br />

maintenance work. Qwest does not track this data for lines/circuits it installs/repairs. As a result Qwest is causing an unnecessary delay for CLECs<br />

customers repair interval. For Qwest to complete its work to repair a line, Qwest process always requires a CLEC to communicate access hours<br />

for access to the customer premise, however, Qwest does not always need access from the customer/building owner for Qwest to complete the<br />

required repair and maintenance work to repair the Qwest caused trouble. For example, if a CLEC opens a ticket at 4 PM because a customer is<br />

out of service, and the CLEC designates access hours of 8 AM to 5 PM for the customer and Qwest cannot dispatch by 5 PM that day, Qwest<br />

could put the ticket in a "No Access" status until 8 AM the next morning. Eschelon has provided examples to its Service Management team where<br />

Qwest put tickets in a "No Access" status after access hours , the trouble was in the Qwest network and Qwest did not require the customer end<br />

user or building owner to provide access. If Qwest tracked "Access required" information in its systems and made that information available to the<br />

CLECs when opening a ticket, the CLEC could set clear expectations for repair intervals with its own customers and Qwest could set clear<br />

expectations and interval with the CLECs. Because Qwest does not track this information, the decision is left to Qwest personnel to make a<br />

decision on whether Qwest needs access to its equipment. In addition, if Qwest and a CLEC knew when access was required, the number of<br />

unnecessary dispatches and associated charges to the CLEC could be reduced.<br />

Status History<br />

12/09/03 - CR Submitted<br />

12/11/03 - CR Acknowledged<br />

12/18/03 - Held Clarification Call<br />

12/26/03- Clarification Minutes sent<br />

01/07/04 - Updated Clarification Call minutes sent to CLECs<br />

1/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

1/21/04 - Status changed to Presented<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

2/18/04 - Status changed to evaluation<br />

Project <strong>Meeting</strong>s<br />

2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Don Tolman, Qwest stated that Qwest is currently reviewing the request and will provide a complete response in the <strong>March</strong> meeting. He requested<br />

the CR be moved to Evaluation status.<br />

-------------------------------------------------------------------------<br />

1/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Bonnie Johnson, Eschelon presented this CR. It is designed to provide information regarding if the end user customer or building manager is<br />

needed to access the demarc. Late in the day some tickets are put in “no access” status by Qwest when the customer was not needed to access<br />

the demarc. She is asking that Qwest note in their systems if the customer has to give access to the demarc when Qwest does an install or repair<br />

on a going forward basis. (She also stated to Doug Andreen later in the meeting that DS1 and above are the biggest concern because of<br />

customer impact). The CR will move to Presented status.<br />

----------------------------------------------------------------------<br />

1/7/04 Clarification to statement made in Clarification <strong>Meeting</strong> 12/18 (see Below) additional information is in parentheeses.<br />

Roszan Jarman-Konkel, Qwest said that in the design world, there is an ability to enter three days worth of premise ( and circuit) access(hours via<br />

CEMR.)<br />

-----------------------------------------------------------------------<br />

Clarification <strong>Meeting</strong><br />

8:00 a.m. (MDT) / Thursday 12/18, 2003<br />

1-877-521-8688 1456160#<br />

PC120903-1 Qwest will track access required information in it’s systems<br />

Attendees<br />

Diebel, Diane<br />

Johnson, Bonnie<br />

Tolman, Don<br />

Andreen, Doug<br />

Information Current as of:<br />

Report Name:<br />

Evaluation<br />

2/18/04<br />

Originator Company Name:<br />

Eschelon<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

13<br />

<strong>Product</strong>s<br />

Impacted<br />

PC120903-1<br />

Page 49 of 105<br />

Attachment D


Kim Isaacs, Eschelon<br />

Bonnie Johnson, Eschelon<br />

Julie Pickar, U S Link<br />

Doug Andreen, Qwest<br />

Roszan Jarman-Konkel<br />

Paul Hanser, Eschelon<br />

Curt Anderson, Qwest<br />

Tom McAldine, Eschelon<br />

Jim Recker, Qwest<br />

Jean Novak, Qwest<br />

Doug Andreen read the full title of the CR as follows: Qwest will track access required information in its systems when Qwest installs new service,<br />

or when Qwest dispatches on the repair of an existing line/circuit. Qwest will make the information available to CLECs for use when a CLEC opens<br />

a repair ticket for a CLEC end user customer.<br />

Bonnie Johnson, Eschelon explained the reason for the request is that a few months ago Eschelon noticed on POTS and Design that numerous<br />

tickets were going to a no access status. Through analysis Eschelon found that on certain tickets Qwest did not need access to the premise to<br />

clear the ticket. Eschelon then asked Qwest if they track access needs for the Demarc or circuit. The answer was no. The CR therefore is for<br />

Qwest to develop a tracking mechanism to track access information in its systems when installing new service or on the repair of an existing<br />

line/circuit.<br />

Doug asked if this would be on a going forward basis and Eschelon answered yes.<br />

Tom McAldine, Eschelon gave an example where a ticket is opened at 3 p.m., Qwest troubleshoots till 6 p.m. and finds the trouble to be outside<br />

the serving central office. Eschelon cannot contact the customer and the ticket is then put off till 6 a.m. the next day. Tom said in many cases<br />

Qwest will find that in order to fix the problem no premise access was required. Tom further stated that Qwest’s policy is to troubleshoot all the<br />

way to customer premise.<br />

Curt Anderson, Qwest clarified that what is asked for is to first ensure that Qwest is following process that is now in place and second, to begin<br />

tracking access requirements.<br />

Bonnie answered yes, but the CR is not designed for the compliance issue as this is being addressed by other means.<br />

Jim Recker, Qwest asked if Eschelon was asking for the location of the NIU? Bonnie answered yes.<br />

Roszan Jarman-Konkel, Qwest said that in the design world, there is an ability to enter three days worth of premise access.<br />

Jim asked if this were for design or POTS since different systems are used.<br />

Bonnie answered both.<br />

Doug asked of it was fair to say most of the existing problems are on the design side. Bonnie answered yes DS1 and above are the main areas.<br />

Tom added that the main point was looking beyond the end office to the fiber hut etc. i.e. the equipment between the end office and equipment<br />

needing premise access.<br />

Bonnie added that some of the existing information on the Qwest work docs is incomplete and Tom agreed.<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

All new service and all lines and circuits that require Qwest repair.<br />

Confirm Right Personnel Involved<br />

Cathy Garcia needs to be added. Doug will ensure this happens as she is on vacation now.<br />

Identify/Confirm CLEC’s Expectation<br />

These expectations were confirmed.<br />

1. Qwest will develop and train a process that will track whether access is required for future repairs for all new installs and repairs to existing lines<br />

circuits.<br />

2. Qwest will make the information available to CLECs when a CLEC opens a repair ticket.<br />

3. Qwest will complete any systems work required to implement the process.<br />

Identify any Dependent Systems Change Requests<br />

None identified.<br />

Establish Action Plan (Resolution Time Frame)<br />

Bonnie will present the CR at the January <strong>CMP</strong> meeting with a response being in the February timeframe.<br />

Qwest Response<br />

<strong>March</strong> 9, <strong>2004</strong><br />

For Review by the CLEC Community and Discussion at the <strong>March</strong> <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC120903-1<br />

Page 50 of 105<br />

Attachment D


Bonnie Johnson<br />

Senior Manager, ILEC Relations<br />

Eschelon Communications<br />

SUBJECT: Qwest Change Request Response CR # PC120903-1<br />

Description of CR: Qwest will track access required information in its systems when Qwest installs new service, or when Qwest dispatches on<br />

the repair of an existing line/circuit. Qwest will make the information available to CLECs for use when a CLEC opens a repair ticket for a CLEC<br />

end user customer.<br />

For example, if a CLEC opens a ticket at 4 PM because a customer is out of service, and the CLEC designates access hours of 8 AM to 5 PM for<br />

the customer and Qwest cannot dispatch by 5 PM that day, Qwest could put the ticket in a No Access status until 8 AM the next morning.<br />

Eschelon has provided examples to its Service Management team where Qwest put tickets in a No Access status after access hours, the trouble<br />

was in the Qwest network and Qwest did not require the customer end user or building owner to provide access. If Qwest tracked Access required<br />

information in its systems and made that information available to the CLECs when opening a ticket, the CLEC could set clear expectations for<br />

repair intervals with its own customers and Qwest could set clear expectations and interval with the CLECs. Because Qwest does not track this<br />

information, the decision is left to Qwest personnel to make a decision on whether Qwest needs access to its equipment. In addition, if Qwest and<br />

a CLEC knew when access was required, the number of unnecessary dispatches and associated charges to the CLEC could be reduced.<br />

The Qwest Operations Staff has reviewed the problem described above and have covered this issue with the repair managers of the maintenance<br />

centers. The repair managers are covering all technicians on the requirement to test to the last access point in the circuit that is available. When<br />

premise access is needed, Qwest technicians will call or send an electronic message to the CLEC to validate access to the network interface<br />

devise before establishing No Access time.<br />

Also, the CEMR user online help provides the following information to the CLEC for inputting of their trouble tickets and access information.<br />

The online help is available to the customers at:<br />

http://www.qwest.com/wholesale/systems/WebHelp/Introduction.htm<br />

This is CEMR version 2.0 and is supported by Netscape Communicator version 7.0 and Internet Explorer version 5.5.<br />

Access Hours (00:00-23:59 Local Time)<br />

Location<br />

The location of the premises where the trouble ticket is submitted, for a Qwest technician to access, if<br />

required. Enter the earliest and latest times that a Qwest technician can access the premises for three<br />

days, starting on the day the trouble report is entered. You must enter the time in the military format,<br />

and the earliest time must be prior to the latest time. For example, 8:00 a.m. must be entered as<br />

08:00, and 1:00 p.m. must be entered as 13:00. You cannot use 24:00 to indicate 12:00 a.m. Enter<br />

23:59 instead.<br />

If premises access is not available on these dates, enter normal business hours for both the earliest<br />

and latest times. Then, in the Description field, enter No prem access until (specific date).<br />

Circuit<br />

The location of the circuit, for a Qwest technician to access, if required. Enter the earliest and latest<br />

times that a Qwest technician can access the circuit for three days, starting on the day the trouble<br />

report is entered. You must enter the time in the military format, and the earliest time must be prior to<br />

the latest time. For example, 8:00 a.m. must be entered as 08:00, and 1:00 p.m. must be entered as<br />

13:00. You cannot use 24:00 to indicate 12:00 a.m. Enter 23:59 instead.<br />

If circuit access is not available on these dates, please enter normal business hours for both the<br />

earliest and latest times. Then, in the Description field, enter No prem access until (specific date).<br />

Additionally, in an effort to strengthen obtaining correct access, Qwest has made it mandatory for the repair answering centers to obtain all access<br />

information, circuit, premise and local contacts as they enter the trouble ticket.<br />

Again all technicians will be required to test to the last access point in the circuit that is available. When premise access is needed, Qwest<br />

technicians will call or send an electronic message to the CLEC to validate access to the network interface device before establishing No Access<br />

time.<br />

Sincerely,<br />

Don Tolman<br />

Qwest Communications<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC120903-1<br />

Page 51 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC031103-1 Convert Common Area Splitter Collocation<br />

to Cageless Shelf at a time Collocation<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Revised Description of Change (07-14-03):<br />

To facilitate the CLEC’s option to perform maintenance, Covad requests the following changes.<br />

Wholesale ProdProc Maintenance,<br />

Repair<br />

Collocation -<br />

Physical, Virtual<br />

1. Qwest allow the CLEC to access the front of the splitter shelf for testing thereby permitting test of a splitter card by the CLEC (Diagram A).<br />

2. Qwest will allow the CLEC to perform maintenance on the splitter cards including replacement as necessary.<br />

3. Qwest will continue to provision the CAS and will control the engineering configuration database for CAS. For new circuits, Qwest will install and<br />

provision the new splitter cards as necessary.<br />

4. Qwest will continue to maintain the splitter shelves and Common Area Splitter bays.<br />

5. CLEC’s will have the option to perform maintenance on the splitter cards or continue to have Qwest control all maintenance.<br />

6. If the CLEC impairs a Qwest voice customer during the maintenance of the splitter cards Qwest may temporarily remove the data portion of the<br />

circuit.<br />

7. The monthly recurring fees will be adjusted to remove the maintenance cost for those CLECs electing to perform the CAS splitter card<br />

maintenance.<br />

8. The CAS shelves will be clearly designated to identify those shelves maintained by Qwest or the CLEC.<br />

Original Description of Change (03-11-03):<br />

Covad requests to be allowed to convert any or all existing Common Area Splitter Collocation arrangements to Cageless Shelf at a time<br />

Collocation. The current arrangement, being a type of Virtual Collocation, requires Qwest technicians to perform all maintenance associated with<br />

the splitters and splitter cards. While this process has worked in some central offices, Covad continues to experience problems related to<br />

improperly performed maintenance including splitter cards removed in error, splitter cards not installed properly, splitter cards replaced<br />

unnecessarily and cards removed as defective which cannot be located. Further, Covad and Qwest have not been able to jointly develop and<br />

document a workable process for the replacement of defective splitter cards. Covad has been trying to resolve these problems for over three<br />

years but continues to have the same experiences. These problems, coupled with the high non-recurring costs, have caused Covad to begin<br />

placing splitters in its own collocation arrangements, as additional capacity is required. It is Covad’s hope that by converting the existing splitter<br />

capacity from Common Area Splitter Collocation to some form of Cageless Shelf at a time Collocation, most of the maintenance problems will be<br />

resolved. This proposal would remove the splitter maintenance responsibility from Qwest and place it with Covad. This conversion may also<br />

require adjustments to existing monthly recurring charges applicable to the current product.<br />

Expected Deliverable:<br />

As Soon As Possible<br />

Status History<br />

03-12-03 - CR Acknowledged<br />

03-26-03 - Clarification <strong>Meeting</strong> held<br />

04-16-03 - Presented at <strong>CMP</strong> <strong>Meeting</strong><br />

05/21/03 - Qwest response presented at <strong>CMP</strong> <strong>Meeting</strong><br />

06/11/03 - Qwest response posted and distributed<br />

06/18/03 - Discussed at <strong>CMP</strong> <strong>Meeting</strong><br />

07/16/03 - CR Discussed at <strong>CMP</strong> Monthly <strong>Meeting</strong><br />

08/21/03 - Discussed at <strong>CMP</strong> <strong>Meeting</strong><br />

09/17/03 - September <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

10/15/03 - October <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

11/19/03 - November <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

01/12/04 - Qwest sent PROD.01.12.04.F.01237.ComAreaSplitColloV11 proposed effective date 2/26/04<br />

01/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

02/11/04 - Qwest issued Final notification PROD.02.11.04.F.01324.FNL_Common_Area_Splitter effective date 2/26/04<br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Project <strong>Meeting</strong>s<br />

Campbell, Bill<br />

Berard, John<br />

Williams, David<br />

Sanchez-Steinke, Linda<br />

Development<br />

6/18/03<br />

Originator Company Name:<br />

Report Line Number<br />

<strong>Product</strong>s<br />

Impacted<br />

01/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Dave Williams with Qwest said that the PCAT changes will be effective on 2/26/04 and a contract amendment will be available at the same time.<br />

This CR will remain in Development status.<br />

Information Current as of:<br />

Report Name:<br />

Covad<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

14<br />

PC031103-1<br />

Page 52 of 105<br />

Attachment D


__________________________________<br />

1/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Dave Williams with Qwest provided an update to this CR and said changes for the PCAT were released 1/12/04 and the proposed effective date is<br />

2/26/04. Mike Zulevic asked if the change would be available across the board on 2/26/04. Dave said yes. This CR will remain in Development<br />

status.<br />

__________________________________<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Dave Williams with Qwest provided an update to this CR which allow the CLEC to maintain POTS splitter cards. Dave said changes for the PCAT<br />

should be out soon. This CR will remain in Development status.<br />

__________________________________<br />

11/19/03 November <strong>CMP</strong> <strong>Meeting</strong><br />

Dave Williams with Qwest provided an update to this CR and said we will be submitting level 3 changes for the PCAT and plan to have available in<br />

the December timeframe. Dave will send a copy to Mike Zulevic and John Berard for comments. This CR will remain in Development status.<br />

__________________________________<br />

10/15/03 October <strong>CMP</strong> <strong>Meeting</strong><br />

Dave Williams with Qwest provided an update to this CR which provides CLECs the option to do maintenance or have Qwest do the maintenance<br />

on splitter cards. There will be changes made to the PCAT in November. This CR will remain in Development status.<br />

__________________________________<br />

09/17/03 September <strong>CMP</strong> <strong>Meeting</strong><br />

Dave Williams provided an update to this CR and said that we have moved forward with a trial beginning 8/25 in Seattle areas and the trial has<br />

been well received by both Qwest and Covad. There will be a process change written in the next few weeks. This CR will remain in<br />

Development status.<br />

__________________________________<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

08-13-03<br />

White-Qwest presented the Qwest acceptance of the revised Covad Description of Change. Zulevic-Covad stated that Qwest and Covad were<br />

testing the process in 15 Central Offices in Washington state. He stated that it looked as if the process was progressing very well.<br />

============================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

07-16-03<br />

White-Qwest presented the status and stated that Covad had submitted a revised description of change that Qwest was working on. Williams-<br />

Qwest stated that Qwest would probably start a trial with Covad on August 1. Berard-Covad stated that this was good progress. CR remains in<br />

Development.<br />

==============================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

06-18-03<br />

Williams-Qwest presented the Qwest response. Zulevic-Covad stated that he had reviewed the response and that the Qwest recommended<br />

solution addressed a majority of his concerns. He asked how to proceed. White-Qwest recommended that Covad revise their description of<br />

change to align with the Qwest recommendation. He stated that he could forward a suggestion to Zulevic for approval. Zulevic-Covad agreed.<br />

White-Qwest stated that the change request would move into Development.<br />

==========================================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

05-21-03<br />

White-Qwest presented the Qwest response and suggested the CR be moved to Evaluation status.<br />

==========================================<br />

04-16-03 - <strong>CMP</strong> <strong>Meeting</strong><br />

Zulevic-Covad presented the CR. Williams-Qwest stated that another option would be to move the splitters to the cageless lineup. Zulevic-Covad<br />

stated that this was to difficult logistically. Williams-Qwest asked if Covad expected Qwest to develop a per shelf collocation cost. Zulevic-Covad<br />

stated that he expected a monthly recurring rental rate. Williams-Qwest asked if Covad had discussed this issue with any other CLECs. Zulevic-<br />

Covad stated that he had not and that this would probably create a bifurcated process for Qwest. Williams-Qwest stated that he would query other<br />

DLECs for interest. Van Meter-AT&T stated that AT&T would like to be involved in any development calls for this CR.<br />

==========================================================<br />

Clarification <strong>Meeting</strong><br />

Wednesday, <strong>March</strong> 26, 2003<br />

1-877-550-8686<br />

2213337#<br />

Attendees<br />

Matt White – CRPM<br />

Dave Williams – Qwest<br />

Jeff Cook – Qwest<br />

Mike Zulevic – Covad<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC031103-1<br />

Page 53 of 105<br />

Attachment D


John Berard – Covad<br />

Becky Neesen - Covad<br />

Introduction of Attendees<br />

White-Qwest welcomed all attendees and reviewed the request.<br />

Review Requested (Description of) Change<br />

Berard-Covad reviewed the CR. Zulevic-Covad this has been a tough issue for both companies and that Covad was just looking for a possible<br />

solution.<br />

Williams-Qwest asked if Covad was intending to physically move splitters. Zulevic-Covad stated that there was no move necessary; Covad would<br />

just take over maintenance of splitters. Williams-Qwest stated that the issue was that when Covad provisions loops Qwest sometimes makes<br />

mistakes.<br />

Cook and Williams had no further questions.<br />

Confirm Areas and <strong>Product</strong>s Impacted<br />

White-Qwest confirmed that the attendees were comfortable that the request appropriately identified all areas and products impacted.<br />

Confirm Right Personnel Involved<br />

White-Qwest confirmed with the attendees that the appropriate Qwest personnel were involved. He stated that Lillian Robertson would also be<br />

involved in analyzing this CR. Williams-Qwest stated that he would work with Robertson on this CR.<br />

Identify/Confirm CLEC’s Expectation<br />

White-Qwest reviewed the request to confirm Covad’s expectation.<br />

Identify and Dependant Systems Change Requests<br />

White-Qwest asked the attendees if they knew of any related change requests.<br />

Establish Action Plan<br />

White-Qwest asked attendees if there were any further questions. There were none. White-Qwest stated that the next step was for Covad to<br />

present the CR at the April Monthly <strong>Product</strong>/<strong>Process</strong> <strong>Meeting</strong> and thanked all attendees for attending the meeting.<br />

Qwest Response<br />

August 12, 2003<br />

REVISED RESPONSE<br />

For Review by CLEC Community and Discussion at the August 20, 2003,<br />

<strong>CMP</strong> <strong>Product</strong>/<strong>Process</strong> <strong>Meeting</strong><br />

John Berard<br />

Covad Communications<br />

SUBJECT: Qwest’s Change Request Response - CR #PC031103-1<br />

Qwest accepts this revised CR and proposes offering an optional maintenance program for Common Area Splitter configurations.<br />

Diagram A, attached, depicts a typical configuration for a CAS<br />

In this configuration Qwest maintains the common area splitter configuration and all provisioning of loops. Presently Qwest also performs all<br />

maintenance on the splitter shelf including splitter card installation and replacement. Qwest also keeps records of CAS in the<br />

administrative/engineering system SWITCH/FOMS.<br />

The current DMARC separating the CLEC controlled cabling from the Qwest network is the rear of the splitter shelf as shown in Diagram A. The<br />

CLEC also has access to the ICDF frame and specifically the voice block for testing purposes (Diagram A).<br />

Under this revised plan, the CLEC would have the option to have Qwest perform the maintenance, as is currently the practice, or the CLEC could<br />

perform the splitter card maintenance.<br />

To facilitate the CLEC’s option to perform maintenance, Qwest proposes the following changes.<br />

1. Qwest will allow the CLEC to access the front of the splitter shelf for testing thereby permitting test of a splitter card by the CLEC (Diagram A).<br />

2. Qwest will allow the CLEC to perform maintenance on the splitter cards including replacement as necessary.<br />

3. Qwest will continue to provision the CAS and will control the engineering configuration database for CAS. For new circuits, Qwest will install and<br />

provision the new splitter cards as necessary.<br />

4. Qwest will continue to maintain the splitter shelves and Common Area Splitter bays.<br />

5. CLEC’s will have the option to perform maintenance on the splitter cards or continue to have Qwest control all maintenance.<br />

6. If the CLEC impairs a Qwest voice customer during the maintenance of the splitter cards Qwest may temporarily remove the data portion of the<br />

circuit.<br />

7. The monthly recurring fees will be adjusted to remove the maintenance cost for those CLECs electing to perform the CAS splitter card<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC031103-1<br />

Page 54 of 105<br />

Attachment D


maintenance.<br />

8. The CAS shelves will be clearly designated to identify those shelves maintained by Qwest or the CLEC.<br />

This solution addresses Covad’s primary concern of maintenance of the CAS and enables Covad and other CLECs to dispatch their technicians to<br />

correct a defective splitter card without having to generate a trouble/maintenance ticket through Qwest.<br />

For Qwest, the proposed solution will require training and process updates but will not require the introduction of an entirely new product that would<br />

be cost prohibitive.<br />

The CLECs also have the option to place the splitters in their collocation site eliminating any maintenance issues.<br />

Sincerely,<br />

David Williams<br />

Qwest Wholesale <strong>Product</strong> Manager<br />

303-896-8166<br />

================================================<br />

June 11, 2003<br />

REVISED RESPONSE<br />

For Review by CLEC Community and Discussion at the June 18, 2003,<br />

<strong>CMP</strong> <strong>Product</strong>/<strong>Process</strong> <strong>Meeting</strong><br />

John Berard<br />

Covad Communications<br />

SUBJECT: Qwest’s Change Request Response - CR #PC031103-1<br />

Covad has requested a change to the common area splitter product as follows: “Covad requests to be allowed to convert any or all existing<br />

Common Area Splitter Collocation arrangements to Cageless Shelf at a time Collocation.”<br />

In response to this CR Qwest provides the following response.<br />

1. Issue 1. Covad requested to convert all existing Common Area Splitter Collocation arrangements to Cageless Shelf at a time Collocation. In<br />

order to change what now is a virtual collocation product to a cageless product, Qwest would require the development of a brand new product.<br />

Qwest's cageless collocation process is based on a per bay basis so this would not follow as a simple variation to the existing cageless collocation<br />

process. The Common Area Splitters are currently provisioned and maintained by Qwest. In a proposed conversion to a cageless product, a new<br />

provisioning process would be required in addition to a reconfiguration of the network to redefine the DEMARC. Qwest billing software changes<br />

would also be required. All of these changes would require significant funding from Qwest and none are practical when Common Area Splitter<br />

collocation is an optional process and experiences low ordering volumes. The CLEC always has the option to locate the splitters into their<br />

collocation space. The chart below summarizes the required effort to implement a new common area splitter (CAS) proposed by Covad.<br />

Task Person Months<br />

Define New <strong>Product</strong> 4<br />

Create M&P 1<br />

Define Provisioning <strong>Process</strong> 4<br />

Create M&P 1<br />

Implement software changes for billing system 3<br />

Update PCAT and documentation 2<br />

Create Amendment Language 2<br />

Total 17<br />

Qwest rejects this portion of the request because it is not economically feasible.<br />

2. From Qwest’s further evaluation of this change request, it appears that Covad’s primary issue is maintenance of the splitter and, specifically, the<br />

splitter cards. While there was no documentation provided with this CR to indicate that any maintenance issues exist, Qwest proposes offering an<br />

optional maintenance program for Common Area Splitter configurations to address Covad's apparent concern.<br />

Diagram A, attached, depicts a typical configuration for a CAS<br />

In this configuration Qwest maintains the common area splitter configuration and all provisioning of loops. Presently Qwest also performs all<br />

maintenance on the splitter shelf including splitter card installation and replacement. Qwest also keeps records of CAS in the<br />

administrative/engineering system SWITCH/FOMS.<br />

The current DMARC separating the CLEC controlled cabling from the Qwest network is the rear of the splitter shelf as shown in Diagram A. The<br />

CLEC also has access to the ICDF frame and specifically the voice block for testing purposes (Diagram A).<br />

Under this revised plan, the CLEC would have the option to have Qwest perform the maintenance, as is currently the practice, or the CLEC could<br />

perform the splitter card maintenance.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC031103-1<br />

Page 55 of 105<br />

Attachment D


To facilitate the CLEC’s option to perform maintenance, Qwest proposes the following changes.<br />

1. Qwest will change the DMARC for CAS and allow the CLEC to access the front of the splitter shelf for testing thereby permitting test of a splitter<br />

card by the CLEC (Diagram A).<br />

2. Qwest will allow the CLEC to perform maintenance on the splitter cards including replacement as necessary.<br />

3. Qwest will continue to provision the CAS and will control the engineering configuration database for CAS. For new circuits, Qwest will install and<br />

provision the new splitter cards as necessary.<br />

4. Qwest will continue to maintain the splitter shelves and Common Area Splitter bays.<br />

5. CLEC’s will have the option to perform maintenance on the splitter cards or continue to have Qwest control all maintenance.<br />

6. If the CLEC impairs a Qwest voice customer during the maintenance of the splitter cards Qwest may temporarily remove the data portion of the<br />

circuit.<br />

7. The monthly recurring fees will be adjusted to remove the maintenance cost for those CLECs electing to perform the CAS splitter card<br />

maintenance.<br />

8. The CAS shelves will be clearly designated to identify those shelves maintained by Qwest or the CLEC.<br />

This solution addresses Covad’s primary concern of maintenance of the CAS and enables Covad and other CLECs to dispatch their technicians to<br />

correct a defective splitter card without having to generate a trouble/maintenance ticket through Qwest.<br />

For Qwest, the proposed solution will require training and process updates but will not require the introduction of an entirely new product that would<br />

be cost prohibitive.<br />

The CLECs also have the option to place the splitters in their collocation site eliminating any maintenance issues.<br />

Sincerely,<br />

David Williams<br />

Qwest Wholesale <strong>Product</strong> Manager<br />

303-896-8166<br />

======================================<br />

May 14, 2003<br />

DRAFT RESPONSE<br />

For Review by CLEC Community and Discussion at the May 21, 2003,<br />

<strong>CMP</strong> <strong>Product</strong>/<strong>Process</strong> <strong>Meeting</strong><br />

John Berard<br />

Covad Communications<br />

SUBJECT: Qwest’s Change Request Response - CR #PC031103-1<br />

This is a preliminary response regarding Covad CR PC031103-1. This CR requests that CLECs be allowed to convert any or all existing Common<br />

Area Splitter Collocation arrangements to Cageless Shelf at a time collocation.<br />

Qwest is currently working internally to identify a solution to this request. Because there are a large number of issues Qwest must analyze, Qwest<br />

proposes moving this Change Request into Evaluation Status while Qwest prepares a complete answer to this request.<br />

Qwest will provide a status update at the June <strong>CMP</strong> meeting.<br />

Sincerely,<br />

Dave Williams<br />

<strong>Product</strong> Manager<br />

Qwest Corporation<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC031103-1<br />

Page 56 of 105<br />

Attachment D


ATTACHMENT A<br />

CLEC DSLAM<br />

New Proposed<br />

Demarcation Point<br />

Splitter Shelf<br />

Front<br />

Voice<br />

Data<br />

Voice and Data<br />

Hardwire<br />

Back<br />

Existing Demarcation<br />

Point<br />

ICDF<br />

Jumper Qwest<br />

V<br />

e<br />

r<br />

t<br />

i<br />

c<br />

a<br />

l<br />

H<br />

o<br />

r<br />

i<br />

z<br />

o<br />

n<br />

t<br />

a<br />

l<br />

CLEC Test<br />

Access Points<br />

Switch<br />

MDF/COSMIC<br />

OE CP<br />

To End<br />

User


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC042103-1 Tracking process for FBDL order issues. Development Wholesale ProdProc Escalations,<br />

7/19/03<br />

Customer<br />

Service<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

McLeod requests a process established for the listing operations center that is consistent with the CSIE center.<br />

LNP, Unbundled Loop<br />

Expected Deliverable:<br />

McLeod expects that a ticket be opened with the Directory Listing Operation center as is the process with the CSIE center today. Mcleod expects<br />

that these are tracked and available to any reporting that is available to the CSIE center tickets. Mcleod would accept a process where the ticket is<br />

initiated with the CSIE center then a warm transfer to the Directory Listing Operations Center is given. Again the ticket would need to be<br />

maintained and tracked as all other customer service tickets are today.<br />

Status History<br />

4/21/03 CR Received<br />

4/22/03 CR Acknowledged<br />

5/8/03 Clarification <strong>Meeting</strong><br />

05/21/03 - Presented at <strong>CMP</strong> <strong>Meeting</strong><br />

06/11/03 - Qwest response posted and distributed<br />

06/18/03 - Discussed at <strong>CMP</strong> <strong>Meeting</strong><br />

07/09/03 - Revised response posted and distributed<br />

07/16/03 - CR Discussed at <strong>CMP</strong> Monthly <strong>Meeting</strong><br />

08/21/03 - Discussed at <strong>CMP</strong> <strong>Meeting</strong><br />

09/17/03 - September <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

10/15/03 - October <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

11/19/03 - November <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

01/09/04 - Qwest sent <strong>CMP</strong>R.01.09.04.F.01241.Ad_Hoc_Mtg_SchldRESEND for ad hoc meeting scheduled 1/19/04<br />

01/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

03/05/04 - Qwest sent PROD.03.05.04.F.01446.WPDL_V23_DL_UserGuide Level 4 proposed effective date 4/19/04<br />

Project <strong>Meeting</strong>s<br />

02/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Lee Gomez with Qwest gave the update and advised that the CR is on track for implementation in April and will be sending a notification updating<br />

the listing document. The first report will be available in May and the CLECs should contact the Listing Account Manager to receive the report.<br />

Stephanie Prull with Eschelon asked if multiple ACNAs will all be on the same report. Lee Gomez said there would be a separate report for each<br />

ACNA. This CR will remain Development status.<br />

_______________________<br />

Fri 2/13/04 8:29 AM<br />

From; Sanchez Steinke, Linda<br />

To: bjjohnson@eschelon.com<br />

Subject: FW: Action Items Ad Hoc 1/19/04 PC042103-1 Tracking process for FBDL order issues<br />

Bonnie -<br />

As a follow up to your request in the January <strong>CMP</strong> meeting<br />

minutes, attached are the take back items that Lee Gomez<br />

had for PC042103-1. I also posted to the body of the CR<br />

under Project <strong>Meeting</strong>s.<br />

Thank you<br />

Linda Sanchez-Steinke<br />

303-382-5768<br />

Townley, Robin<br />

Prull, Stephanie<br />

Gomez, Lee<br />

Sanchez-Steinke, Linda<br />

Originator Company Name:<br />

McLeodUSA<br />

-----Original Message-----<br />

From: Sanchez Steinke, Linda<br />

Sent: Monday, January 26, <strong>2004</strong> 12:43 PM<br />

To: 'bjjohnson@eschelon.com'<br />

Subject: FW: Action Items Ad Hoc 1/19/04 PC042103-1 Tracking process for FBDL order issues<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

15<br />

<strong>Product</strong>s<br />

Impacted<br />

PC042103-1<br />

Page 57 of 105<br />

Attachment D


Bonnie -<br />

Forwarding to you -- I have your e-mail address<br />

incorrect in the first e-mail.<br />

Linda Sanchez-Steinke<br />

CRPM<br />

Qwest<br />

303-382-5768<br />

-----Original Message-----<br />

From: Sanchez Steinke, Linda<br />

Sent: Monday, January 26, <strong>2004</strong> 12:41 PM<br />

To: 'bjjohnson@escehlon.com'; 'kdisaacs@eschelon.com'; 'saprull@eschelon.com'; 'dosborne@att.com'; 'cdickinson@att.com'<br />

Subject: Action Items Ad Hoc 1/19/04 PC042103-1 Tracking process for FBDL order issues<br />

All,<br />

As a follow up to the ad hoc meeting held 1/19/04, regarding PC042103-1, the following are answers to<br />

questions asked during the meeting that Lee Gomez took as action items:<br />

Q) Bonnie said there are time when calls are referred to directory listings by CSIE and would like to know<br />

which report those would show on.<br />

A) CSIE opens a ticket for every call received. If they determine that a call should be referred to the LOC, CSIE will close that ticket.<br />

With the implementation of this report, when a call is referred from the CSIE, the LOC will open a Help Ticket and follow the new process.<br />

Q) Stephanie asked if tickets can be broken down by what tier closed.<br />

A) FBDL does not have tiers. The LOC representative is the primary point of contact for listing related questions and they<br />

will be responsible for opening the Tickets. If the CLEC is not satisfied with the status of a ticket, they may chose to<br />

escalate the issue to their Listing Resource Services (LRS) Account Manager (AM). The LRS AM will investigate<br />

the situation and may work with the LOC regarding a Ticket, but the LOC representative is responsible for opening,<br />

updating and closing Tickets.<br />

Thank you<br />

Linda Sanchez-Steinke<br />

CRPM<br />

Qwest<br />

303-382-5768<br />

______________________<br />

Mon 1/26/04 12:41 PM<br />

From; Sanchez Steinke, Linda<br />

To: 'bjjohnson@escehlon.com', 'kdisaacs@eschelon.com' 'saprull@eschelon.com' 'dosborne@att.com' 'cdickinson@att.com'<br />

Subject: Action Items Ad Hoc 1/19/04 PC042103-1 Tracking process for FBDL order issues<br />

All,<br />

As a follow up to the ad hoc meeting held 1/19/04, regarding PC042103-1, the following are answers to<br />

questions asked during the meeting that Lee Gomez took as action items:<br />

Q) Bonnie said there are time when calls are referred to directory listings by CSIE and would like to know<br />

which report those would show on.<br />

A) CSIE opens a ticket for every call received. If they determine that a call should be referred to the LOC, CSIE will close that ticket.<br />

With the implementation of this report, when a call is referred from the CSIE, the LOC will open a Help Ticket and follow the new process.<br />

Q) Stephanie asked if tickets can be broken down by what tier closed.<br />

A) FBDL does not have tiers. The LOC representative is the primary point of contact for listing related questions and they<br />

will be responsible for opening the Tickets. If the CLEC is not satisfied with the status of a ticket, they may chose to<br />

escalate the issue to their Listing Resource Services (LRS) Account Manager (AM). The LRS AM will investigate<br />

the situation and may work with the LOC regarding a Ticket, but the LOC representative is responsible for opening,<br />

updating and closing Tickets.<br />

Thank you<br />

Linda Sanchez-Steinke<br />

CRPM<br />

Qwest<br />

303-382-5768<br />

_________________________________<br />

01/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC042103-1<br />

Page 58 of 105<br />

Attachment D


Lee Gomez with Qwest gave an update that an ad hoc meeting was held to present the prototype report for FBDL tickets and that the targeted<br />

implementation is April. Stephanie Prull with Eschelon asked for the implementation date. Lee said it would be coincident with IMA 15.0. This CR<br />

will remain in Development status. (Begin comment from Bonnie Johnson - Eschelon) (Can you provide the answers to the take backs that Lee<br />

Gomez provided at the meeting?) (end comment).<br />

________________________________<br />

Ad Hoc<br />

<strong>Meeting</strong> Minutes<br />

PC042103-1<br />

January 19, <strong>2004</strong><br />

1-877-572-8687, Conference ID 3393947#<br />

10:00 a.m. - 10:30 a.m. Mountain Time<br />

List of Attendees:<br />

Carla Pardee - AT&T<br />

Donna Osborne-Miller - AT&T<br />

Kim Isaacs - Eschelon<br />

Stephanie Prull - Eschelon<br />

Bonnie Johnson - Eschelon<br />

Lee Gomez - Qwest<br />

Linda Sanchez-Steinke - Qwest<br />

The meeting began with Qwest making introductions and welcoming all attendees. Linda Sanchez-Steinke with Qwest explained that the purpose<br />

of the meeting was to gain input on the draft format of the report providing information on FBDL tickets opened by CLECs.<br />

Lee Gomez with Qwest explained that the reports would be similar to the CSIE reports provided monthly. The data will be reported for the entire<br />

month and will include calls made to the Listing Operations Center (LOC) regarding FBDL. The report will give the total number of calls per month,<br />

broken down by day and 8 categories of the tickets opened. Lee explained how the categories are defined:<br />

Account Ownership - account does not belong to Provider<br />

DLIS - question regarding information displayed in DLIS<br />

Ordering - question regarding how to complete an order.<br />

DSRED - question regarding data returned on a DSRED.<br />

Migration - question related to migration/conversion orders<br />

Missing Listing - question regarding listing not found<br />

Other - miscellaneous question.<br />

These categories will be defined in the Facility-Based CLECs and Reseller/Unbundled Network CLECS Directory Listing User Document.<br />

Stephanie Prull with Eschelon asked what category a ticket would go into when getting ready to do a conversion and DLIS is not correct. Lee said<br />

that it would fit into the account ownership if the order has already been issued.<br />

Stephanie asked where a ticket would be categorized if Eschelon has a customer and the information on CSR doesn’t match DLIS. Lee said that<br />

would be under DLIS because of what is being displayed in DLIS, however, the Provider may request a specific reason code if necessary.<br />

Stephanie asked if there is a trouble ticket opened with DLIS where would that be classified. Lee said that is would go under DLIS. The reason<br />

code can be negotiated between the CLEC and the Qwest LOC representative whenever the CLEC feels it is necessary.<br />

Bonnie Johnson with Eschelon asked if the FBDL report would be separate from the CSIE report. Lee answered yes. Bonnie said there are time<br />

when calls are referred to directory listings by CSIE and would like to know which report those would show on. Lee will get back with Bonnie after<br />

checking. Bonnie stated that the preference would be that CSIE would close their ticket and it would appear on the FBDL report. Lee will verify.<br />

Donna Osborne-Miller asked the if the number associated with the category is the total number. Lee said that was correct.<br />

Stephanie asked if tickets can be broken down by what tier closed. Lee will find out the answer.<br />

Linda will e-mail answers out to the group and will put the minutes in the body of this change request. There were no additional questions.<br />

__________________________________<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Linda Sanchez-Steinke gave status that this CR is targeted for the April timeframe and will arrange an ad hoc meeting to review draft format with<br />

Stephanie Prull. This CR will remain in Development status.<br />

___________________________________<br />

11/19/03 November <strong>CMP</strong> <strong>Meeting</strong><br />

Lee Gomez with Qwest gave the update on this CR. Qwest is planning to provide a report prototype at the next meeting. There is a help ticket<br />

generated today and there will be updates made in the applicable PCAT. This CR will remain in Development Status.<br />

____________________________________<br />

10/15/03 October <strong>CMP</strong> <strong>Meeting</strong><br />

Linda Sanchez-Steinke with Qwest gave the update on this CR. Qwest is planning to provide a report in the April <strong>2004</strong> timeframe. Linda will<br />

contact Stephanie Prull to arrange a meeting to discuss the report format. This CR will remain in Development Status.<br />

____________________________________<br />

09/17/03 September <strong>CMP</strong> <strong>Meeting</strong><br />

Lee Gomez provided an update on this CR. Lee said that Qwest is actively working on providing a report in the April timeframe. This CR will<br />

remain in Development Status. ____________________________________<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

08-20-03<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC042103-1<br />

Page 59 of 105<br />

Attachment D


White-Qwest stated that the proposed implementation date for the change was April <strong>2004</strong>. The CR was left in Development status.<br />

=======================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

07-16-03<br />

White-Qwest presented the Qwest acceptance and recommended the CR be moved in to Development.<br />

====================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

06-18-03<br />

White-Qwest presented the Qwest response. He stated that Qwest is currently working internally to identify a solution to this request. Because<br />

this request involves the creation of a complex and wide-reaching process, there are a large number of issues Qwest must analyze. He asked that<br />

the change move to Evaluation.<br />

==========================================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

05-21-03<br />

Prull-McLeod presented the CR. Johnson-Eschelon stated that Eschelon was interested in this CR as well.<br />

==========================================<br />

Clarification <strong>Meeting</strong><br />

Wednesday, May 07, 2003<br />

1-877-550-8686<br />

2213337#<br />

Attendees<br />

Matt White – Qwest<br />

Lee Gomez – Qwest<br />

Michelle Thacker – Qwest<br />

Stephanie Prull – McLeod<br />

Jennifer Arnold – USLink<br />

Introduction of Attendees<br />

White-Qwest welcomed all attendees and reviewed the request.<br />

Review Requested (Description of) Change<br />

Prull-McLeod reviewed the CR. She stated that McLeod has a hard time keeping track of their FBDL issues because they go to a different center<br />

once the order has been processed. Gomez-Qwest stated that the CLECs are now calling into the CSIE center for system related issues. She<br />

explained that they should be able to take calls and open tickets for DLIS issues. She asked McLeod what the wanted to track. Prull-McLeod<br />

stated that McLeod wanted visibility on ordering issues. Gomez-Qwest asked if McLeod was currently experiencing problems with the center.<br />

Prull-McLeod stated that they weren’t but that McLeod is doing more internal reporting. She stated that this is a gap in this reporting because they<br />

don’t have a good way to track it. Gomez-Qwest asked if this CR was related to DLIS issues. Prull-McLeod stated that it was not. She stated that<br />

McLeod wanted to have a ticket number and tracking capabilities. Thacker-Qwest asked if USLink had the same concern. Arnold-USLink stated<br />

that USLink did not have the same issue and needed to submit a separate CR<br />

Confirm Areas and <strong>Product</strong>s Impacted<br />

White-Qwest confirmed that the attendees were comfortable that the request appropriately identified all areas and products impacted.<br />

Confirm Right Personnel Involved<br />

White-Qwest confirmed with the attendees that the appropriate Qwest personnel were involved.<br />

Identify/Confirm CLEC’s Expectation<br />

White-Qwest reviewed the request to confirm McLeod’s expectation.<br />

Identify and Dependant Systems Change Requests<br />

White-Qwest asked the attendees if they knew of any related change requests.<br />

Establish Action Plan<br />

White-Qwest asked attendees if there were any further questions. There were none. White-Qwest stated that the next step was for McLeod to<br />

present the CR at the May Monthly <strong>Product</strong>/<strong>Process</strong> <strong>Meeting</strong> and thanked all attendees for attending the meeting.<br />

Qwest Response<br />

July 9, 2003<br />

REVISED RESPONSE<br />

For Review by CLEC Community and Discussion at the July 16, 2003,<br />

<strong>CMP</strong> <strong>Product</strong>/<strong>Process</strong> <strong>Meeting</strong><br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC042103-1<br />

Page 60 of 105<br />

Attachment D


Stephanie Prull<br />

McLeod USA<br />

SUBJECT: Qwest’s Change Request Response - CR #PC042103-1<br />

This is a revised response regarding McLeod CR PC042103-2. This CR requests a process be established for the listing operations center that is<br />

consistent with the CSIE center.<br />

Qwest accepts this CR. Qwest will create a system to track each incoming CLEC call to the Listing<br />

Operations Center. Similarly, this system will allow Qwest to provide the CLEC with a ticket number and reports that identify all CLEC calls/help<br />

tickets/status. These systems and processes will be completely separate from those within the CSIE.<br />

Qwest will provide a status update of the work to implement this CR at the August <strong>CMP</strong> meeting.<br />

Sincerely,<br />

Lee Gomez<br />

Lead <strong>Process</strong> Analyst<br />

Qwest Communications<br />

===========================================<br />

June 11, 2003<br />

DRAFT RESPONSE<br />

For Review by CLEC Community and Discussion at the June 18, 2003,<br />

<strong>CMP</strong> <strong>Product</strong>/<strong>Process</strong> <strong>Meeting</strong><br />

Stephanie Prull<br />

McLeod USA<br />

SUBJECT: Qwest’s Change Request Response - CR #PC042103-1<br />

This is a preliminary response regarding McLeod CR PC042103-2. This CR requests a process be established for the listing operations center<br />

that is consistent with the CSIE center.<br />

Qwest is currently working internally to identify a solution to this request. Because this request involves the creation of a complex and widereaching<br />

process, there are a large number of issues Qwest must analyze. Qwest proposes moving this Change Request into Evaluation Status<br />

while Qwest prepares a complete answer to this request.<br />

Qwest will provide a status update at the July <strong>CMP</strong> meeting.<br />

Sincerely,<br />

Lee Gomez<br />

Lead <strong>Process</strong> Analyst<br />

Qwest Communications<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC042103-1<br />

Page 61 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC050703-1 Change Qwest Wholesale <strong>CMP</strong> Website to<br />

make it easier to search, retrieve and view<br />

CRs.<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Operations<br />

AT&T is asking Qwest to make it easier to search, retrieve, and view a specific CR document on the Qwest Wholesale <strong>CMP</strong> Website. Although<br />

anyone can sort by CR, Originator Company, Current Status, Most Recently Updated, CR Project Manager, and CR Title - once the sort is<br />

completed, the CR cannot be accessed to read the document. AT&T is requesting that once the sort is completed, we can click on the CR number<br />

and it will bring up that specific CR. Another option might be to have a "search" field and by typing in the CR number, the CR would be retrieved<br />

and the document could be read. If these are not viable options, AT&T is asking Qwest to come up with suggestions/solutions.<br />

Status History<br />

05/07/03 - CR Submitted<br />

05/07/03 - Acknowledged CR<br />

05/12/03 - Clarification <strong>Meeting</strong><br />

05/21/03 - Presented at <strong>CMP</strong> <strong>Meeting</strong><br />

06/11/03 - Qwest response posted and distributed<br />

06/18/03 - Discussed at <strong>CMP</strong> <strong>Meeting</strong><br />

07/16/03 - CR Discussed at <strong>CMP</strong> Monthly <strong>Meeting</strong><br />

09/17/18 - <strong>CMP</strong> <strong>Meeting</strong> Thomte indicated that Qwest is continuing to pursue improvements to this web site.<br />

02/25/04 - Qwest originated notice PROS.02.25.04.F.01418.<strong>CMP</strong>_WEBSite_<strong>Process</strong>Opt<br />

Project <strong>Meeting</strong>s<br />

2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Kit Thomte and Doug Andreen, Qwest said the prototype will be available 3/25 and will be located next to the existing Interactive Report on the<br />

Qwest Web Site. It will contain six different sorts for the data. The format is somewhat changed although the content remains the same. Kit<br />

asked if the CLECs would agree to move this CR to test since the prototype will be available in a week. The CLECs agreed to move the CR to test.<br />

-----------------------------------------------------------------------------------------------<br />

<strong>CMP</strong> <strong>Meeting</strong> 1-21-04<br />

Thomte Qwest indicated that hopefully we might have a prototype for the meeting next month. The issue is continuing to be worked.<br />

The CR will remain in Development status.<br />

------------------------------------------------------------------------------------------<br />

<strong>CMP</strong> <strong>Meeting</strong> 12-17-03<br />

Thomte Qwest indicated that hopefully we might have a prototype for the meeting in January. The issue is continuing to be worked.<br />

The CR will remain in Development status.<br />

--------------------------------------------------------------------------------------------------<br />

<strong>CMP</strong> <strong>Meeting</strong> 10-15-03<br />

Thomte Qwest indicated that this CR is still being worked. Qwest is trying to find the appropriate vendor to handle these updates. This CR will<br />

reamin in Development status.<br />

___________________________________________________<br />

<strong>CMP</strong> <strong>Meeting</strong> 09-17-03<br />

Thomte indicated that Qwest is continuing to pursue improvements to this web site.<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

08-20-03<br />

Van Meter-AT&T stated that she liked the new report format but she would still like to be able to search by CR number. Balvin-MCI stated that she<br />

would like the ability to copy from the report and paste into other applications. White-Qwest stated that Qwest was still working on developing a<br />

more robust report format.<br />

==============================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

07-16-03<br />

Schultz, Judy<br />

Van Meter, Sharon<br />

Thomte, Kit<br />

Thomte, Kit<br />

Development<br />

5/7/03<br />

Originator Company Name:<br />

Report Line Number<br />

<strong>Product</strong>s<br />

Impacted<br />

White-Qwest stated that the new report format would be posted on 7/16. He recommended that the CR be left in Development status because<br />

Qwest was developing a more robust solution. Van Meter-AT&T agreed.<br />

Information Current as of:<br />

Report Name:<br />

AT&T<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

16<br />

PC050703-1<br />

Page 62 of 105<br />

Attachment D


==================================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

06-18-03<br />

White-Qwest presented the response. Van Meter-AT&T and Hines-MCI stated that they were fine with the proposed change. Van Meter-AT&T<br />

asked that Qwest distribute a notice when the change became effective. White-Qwest agreed and asked to move the CR into Development.<br />

==========================================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

05-21-03<br />

Van Meter-AT&T presented the CR. White-Qwest confirmed that the CLECs used the “sort by originator” option in the interactive report the most.<br />

All attendees agreed.<br />

============================================<br />

Clarification <strong>Meeting</strong><br />

Monday, May 12, 2003<br />

1-877-550-8686<br />

2213337#<br />

Attendees<br />

Matt White – Qwest<br />

Sharon Van Meter – AT&T<br />

Liz Balvin – MCI<br />

Bonnie Johnson – Eschelon<br />

Mike Zulevic – Covad<br />

Introduction of Attendees<br />

White-Qwest welcomed all attendees and reviewed the request.<br />

Review Requested (Description of) Change<br />

Osborne-Miller-AT&T reviewed the CR. She stated that she most frequently used the Sort by Originator button to find a CR when she didn’t know<br />

the number. She stated that it would be helpful if the buttons to link to the CR details were contained within that report. White-Qwest asked the<br />

other CLEC representatives if they also used the Sort by Originator function most frequently. All attendees responded that the most frequently<br />

used sort was the Sort by Originator. Van Meter-AT&T suggested that Qwest implement some sort of GUI front end that allows users to find a<br />

specific CR by inputting the number or to sort the CRs by originator/CRMP/status/title/etc. White-Qwest stated that he would query the attendees<br />

at the upcoming meeting to find out if all the CLECs used Sort by Originator most frequently.<br />

Confirm Areas and <strong>Product</strong>s Impacted<br />

White-Qwest confirmed that the attendees were comfortable that the request appropriately identified all areas and products impacted.<br />

Confirm Right Personnel Involved<br />

White-Qwest confirmed with the attendees that the appropriate Qwest personnel were involved.<br />

Identify/Confirm CLEC’s Expectation<br />

White-Qwest reviewed the request to confirm AT&T’s expectation.<br />

Identify and Dependant Systems Change Requests<br />

White-Qwest asked the attendees if they knew of any related change requests.<br />

Establish Action Plan<br />

White-Qwest asked attendees if there were any further questions. There were none. White-Qwest stated that the next step was for AT&T to<br />

present the CR at the May Monthly <strong>Product</strong>/<strong>Process</strong> <strong>Meeting</strong> and thanked all attendees for attending the meeting.<br />

Qwest Response<br />

June 11, 2003<br />

DRAFT RESPONSE<br />

For Review by CLEC Community and Discussion at the June 18, 2003,<br />

<strong>CMP</strong> <strong>Product</strong>/<strong>Process</strong> <strong>Meeting</strong><br />

Sharon Van Meter<br />

AT&T<br />

SUBJECT: Qwest’s Change Request Response - CR #PC050703-1<br />

This is an initial response to AT&T CR PC050703-1. This CR requests that Qwest Change Qwest Wholesale <strong>CMP</strong> Website to make it easier to<br />

search, retrieve and view CRs.<br />

Qwest accepts this Change Request. Qwest recommends that the changes to implement this request be implemented in with a phased approach.<br />

Qwest is still researching an appropriate means of providing more comprehensive linking in the current report and the possibility of providing a GUI<br />

front-end to the report. However, to meet the CLECs’ stated need, Qwest is prepared to immediately modify the existing Interactive Report as<br />

attached.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC050703-1<br />

Page 63 of 105<br />

Attachment D


Sincerely,<br />

Matt White<br />

Qwest<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC050703-1<br />

Page 64 of 105<br />

Attachment D


C:\WINNT\Profiles\dandree\Desktop\Screen prints Interactive.doc


C:\WINNT\Profiles\dandree\Desktop\Screen prints Interactive.doc


C:\WINNT\Profiles\dandree\Desktop\Screen prints Interactive.doc


<strong>Product</strong>/<strong>Process</strong> Change Request Status<br />

(Source: <strong>CMP</strong> Database Issued and Maintained by Wholesale Change Management)<br />

Information Current as of<br />

Monday, June 02, 2003<br />

Introduction Click to view explanation of this Status File<br />

Originator Company Listing Sorted by Originator Company


Report<br />

Line<br />

Number<br />

Summary - Change Management <strong>Process</strong> (<strong>CMP</strong>) - <strong>Product</strong>/<strong>Process</strong><br />

CR Number<br />

Current Status<br />

Report Sorted by Originator Company, by CR Number<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

1 PC021903-1CM 5/27/03 Change to Section 8.0 of the <strong>CMP</strong><br />

Document<br />

Presented<br />

Wholesale<br />

ProdProc<br />

AT&T<br />

Note: There is supplemental information pertaining to this CR. A copy of the supplemental information immediately follows the the detail report for this CR.<br />

2 PC022703-1 5/28/03 Seeking to reduce the interval of a<br />

FOC for the ASR associated with<br />

Development<br />

Dark Fiber from day thirteen (13)<br />

to day two (2) where Dark Fiber is<br />

reserved through the IRI process.<br />

3 PC022703-3 5/23/03 Request for Medical Expedite<br />

<strong>Process</strong><br />

Development<br />

4 PC022703-5 5/28/03 Subject line for PTA email<br />

notification changed.<br />

CLEC Test<br />

Information Current as of:<br />

Report Name:<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

AT&T<br />

AT&T<br />

AT&T<br />

Owner<br />

Director<br />

CR PM<br />

Buhler, Dean<br />

Buhler, Dean<br />

White, Matt<br />

Rein, Kathy<br />

Bliss, Susie<br />

Macy, Cindy<br />

Sunins, Phyllis<br />

Burson, Sue<br />

White, Matt<br />

Toye, Deni<br />

Diebel, Diane<br />

Macy, Cindy<br />

Monday, June 02, 2003 Page 1 of 13


Report<br />

Line<br />

Number<br />

CR Number<br />

Current Status<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

5 PC022703-6 5/28/03 UNE-P to UNE-L Bulk Conversion Wholesale<br />

AT&T<br />

ProdProc<br />

Evaluation<br />

6 PC022703-9X 5/23/03 Support <strong>Product</strong>ion Defect Report<br />

(crossed over from SCR022703-<br />

Development<br />

09)<br />

7 PC032603-1 5/30/03 Standardization of USOCs across<br />

regions<br />

Presented<br />

8 PC042303-1 5/27/03 AT&T requests that Vendor Meet<br />

(coordinated dispatch) requests<br />

Presented<br />

for non-design POTS service be at<br />

specific times.<br />

Information Current as of:<br />

Report Name:<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

AT&T<br />

AT&T<br />

AT&T<br />

Owner<br />

Director<br />

CR PM<br />

Urevig, Russell<br />

Bliss, Susie<br />

Macy, Cindy<br />

Paxton, Mallory<br />

Bliss, Susie<br />

White, Matt<br />

Paxton, Mallory<br />

Bliss, Susie<br />

Macy, Cindy<br />

Suellentrop, Craig<br />

Retka, Mary<br />

White, Matt<br />

Monday, June 02, 2003 Page 2 of 13


Report<br />

Line<br />

Number<br />

CR Number<br />

Current Status<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

9 PC042303-2 5/27/03 AT&T requests that pre-dispatch<br />

calls be limited to specific<br />

Presented<br />

scenarios, primarily address<br />

mismatches, no access situations<br />

and/or vendor meets requests.<br />

10 PC050503-4CM 5/28/03 Allow Originating CLEC to invite<br />

other CLECs to its Clarification<br />

Presented<br />

<strong>Meeting</strong> for a System CR<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

AT&T<br />

AT&T<br />

Note: There is supplemental information pertaining to this CR. A copy of the supplemental information immediately follows the the detail report for this CR.<br />

11 PC050703-1 5/23/03 Change Qwest Wholesale <strong>CMP</strong><br />

Website to make it easier to<br />

Presented<br />

search, retrieve and view CRs.<br />

12 PC011502-1 5/28/03 Joint testing of Qwest installed<br />

transmission cables<br />

CLEC Test<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

AT&T<br />

Covad<br />

Note: There is supplemental information pertaining to this CR. A copy of the supplemental information immediately follows the the detail report for this CR.<br />

Information Current as of:<br />

Report Name:<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

Owner<br />

Director<br />

CR PM<br />

Suellentrop, Craig<br />

Retka, Mary<br />

White, Matt<br />

Macy, Cindy<br />

Schultz, Judy<br />

Macy, Cindy<br />

White, Matt<br />

Schultz, Judy<br />

White, Matt<br />

Campbell, Ben<br />

Campbell, William<br />

Macy, Cindy<br />

Monday, June 02, 2003 Page 3 of 13


Report<br />

Line<br />

Number<br />

CR Number<br />

Current Status<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

13 PC012703-2 5/28/03 DATA Migration <strong>Process</strong> Wholesale<br />

Covad<br />

ProdProc<br />

Development<br />

14 PC031103-1 5/23/03 Convert Common Area Splitter<br />

Collocation to Cageless Shelf at a<br />

Evaluation<br />

time Collocation<br />

15 PC051403-1 5/29/03 Sync Test for Line share, Loop<br />

Splitting, and Line Splitting on<br />

Clarification<br />

Maintenance Trouble Tickets and<br />

Sync Testing for provisioning of<br />

Line and Loop Splitting.<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Covad<br />

Covad<br />

16 PC051403-2 5/28/03 Adding Zone information to Bills Wholesale<br />

Covad<br />

ProdProc<br />

Clarification<br />

Information Current as of:<br />

Report Name:<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

Owner<br />

Director<br />

CR PM<br />

Soderlund, Crystal<br />

Bliss, Susie<br />

Macy, Cindy<br />

Williams, David<br />

Campbell, Bill<br />

White, Matt<br />

Boudhaouia, Jamal<br />

Retka, Mary<br />

Sanchez-Steinke, Lind<br />

Kilker, Terri<br />

Bliss, Susie<br />

White, Matt<br />

Monday, June 02, 2003 Page 4 of 13


Report<br />

Line<br />

Number<br />

CR Number<br />

Current Status<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

17 PC051403-3 5/28/03 Request for By-Weekly Technical<br />

<strong>Meeting</strong>s on Pre-Qual Issues<br />

Clarification<br />

18 PC051903-1 5/30/03 Real Time API Connection to Raw<br />

Loop Data<br />

Clarification<br />

19 PC010603-1 5/28/03 MEL (market expansion line) LSR<br />

process documented on Qwest<br />

CLEC Test<br />

Wholesale web site.<br />

20 PC030603-1 5/28/03 Documentation process to allow<br />

CLECs to request documentation<br />

Development<br />

of existing processes, including<br />

documentation on the Qwest<br />

Wholesale web site.<br />

Information Current as of:<br />

Report Name:<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

Covad<br />

Covad<br />

Eschelon<br />

Eschelon<br />

Owner<br />

Director<br />

CR PM<br />

Suellentrop, Craig<br />

Retka, Mary<br />

Macy, Cindy<br />

To Be Determined<br />

To Be Determined<br />

Macy, Cindy<br />

Kilker, Terri<br />

Bliss, Susie<br />

Macy, Cindy<br />

Coyne, Mark<br />

McNa, Sue<br />

Macy, Cindy<br />

Monday, June 02, 2003 Page 5 of 13


Report<br />

Line<br />

Number<br />

CR Number<br />

Current Status<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

21 PC070202-2X 5/28/03 Time & Material Repair Charges<br />

Invoice <strong>Process</strong><br />

Development<br />

Wholesale<br />

ProdProc<br />

Eschelon<br />

Note: There is supplemental information pertaining to this CR. A copy of the supplemental information immediately follows the the detail report for this CR.<br />

22 PC100401-1XMN 5/21/03 LNP Port In/Port Within<br />

Completion Call (Crossover<br />

CLEC Test<br />

SCR100401-1X)<br />

23 PC031703-1 5/28/03 Make MDS/MDSI/MWI Document<br />

Available in Excel Format<br />

CLEC Test<br />

24 PC041503-1CM 5/23/03 Add to section 4.0 TYPES OF<br />

CHANGE CLEC impacting defect<br />

Presented<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Eschelon<br />

Note: There is supplemental information pertaining to this CR. A copy of the supplemental information immediately follows the the detail report for this CR.<br />

Information Current as of:<br />

Report Name:<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

MCI<br />

MCI<br />

Owner<br />

Director<br />

CR PM<br />

Suellentrop, Craig<br />

Retka, Mary<br />

Macy, Cindy<br />

Wells, Joan<br />

Bliss, Susie<br />

Sanchez-Steinke, Lind<br />

Paxton, Mallory<br />

Bliss, Susie<br />

Macy, Cindy<br />

White, Matt<br />

Schultz, Judy<br />

White, Matt<br />

Monday, June 02, 2003 Page 6 of 13


Report<br />

Line<br />

Number<br />

CR Number<br />

Current Status<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

25 PC050503-3 5/23/03 CEMR requests processed via the<br />

proper channels<br />

Presented<br />

26 PC042103-1 5/23/03 Tracking process for FBDL order<br />

issues.<br />

Clarification<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

MCI<br />

McLeodUSA<br />

27 PC042103-2 5/23/03 Escalation Ticket Reporting Wholesale<br />

ProdProc<br />

McLeodUSA<br />

Clarification<br />

28 PC051203-1 5/29/03 Versioning <strong>Process</strong> Change Wholesale McLeodUSA<br />

ProdProc<br />

Clarification<br />

Information Current as of:<br />

Report Name:<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

Owner<br />

Director<br />

CR PM<br />

McBride, Kathy<br />

Burson, Sue<br />

White, Matt<br />

Gomez, Lee<br />

Townley, Robin<br />

White, Matt<br />

Thacker, Michelle<br />

Burson, Sue<br />

White, Matt<br />

Manning, Monica<br />

Burson, Sue<br />

Macy, Cindy<br />

Monday, June 02, 2003 Page 7 of 13


Report<br />

Line<br />

Number<br />

CR Number<br />

Current Status<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

29 PC012103-1 5/21/03 Update Operator<br />

Services/Directory Assistance<br />

Wholesale<br />

ProdProc<br />

CLEC Test<br />

(OS/DA) Questionnaire on Website<br />

Qwest<br />

Communications<br />

Note: There is supplemental information pertaining to this CR. A copy of the supplemental information immediately follows the the detail report for this CR.<br />

30 PC022403-2 5/29/03 Conditioning for DSL Services in<br />

Line Sharing <strong>Product</strong>s at no<br />

CLEC Test<br />

charge to the CLEC/DLEC<br />

31 PC022403-3 5/23/03 Conditioning for Qwest DSL<br />

Services in UNE-P and Resale<br />

CLEC Test<br />

<strong>Product</strong>s at no charge to the<br />

CLEC/DLEC<br />

32 PC030503-1 5/28/03 Grandfathering of Consumer<br />

Packages<br />

CLEC Test<br />

Information Current as of:<br />

Report Name:<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

Qwest<br />

Communications<br />

Christofferson, Aelea<br />

Qwest<br />

Communications<br />

Christofferson, Aelea<br />

Qwest<br />

Communications<br />

Owner<br />

Director<br />

CR PM<br />

Bruggeman, Kathy<br />

Hooks, Perry<br />

Sanchez-Steinke, Lind<br />

Buckmaster, Cindy<br />

Campbell, William<br />

White, Matt<br />

Buckmaster, Cindy<br />

Campbell, Bill<br />

White, Matt<br />

Van Dusen, Janean<br />

Campbell, William<br />

Macy, Cindy<br />

Monday, June 02, 2003 Page 8 of 13


Report<br />

Line<br />

Number<br />

CR Number<br />

Current Status<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

33 PC031203-1 5/23/03 CLEC access to MLT information<br />

in WFA<br />

Development<br />

34 PC032703-2 5/23/03 Modifications to existing<br />

requirement to have Voice Circuit<br />

Development<br />

in-place before DSL can be added<br />

on Line Sharing <strong>Product</strong> Family<br />

35 PC032703-3 5/23/03 Modifications to existing<br />

requirement to have Voice Circuit<br />

Development<br />

in-place before Qwest DSL can be<br />

added on Resale and UNE-P<br />

Services<br />

36 PC032803-3 5/23/03 Grandfather Centrex , Centrex<br />

Plus and Centron service in<br />

Development<br />

Colorado, New Mexico, North<br />

Dakota and South Dakota<br />

Information Current as of:<br />

Report Name:<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

Qwest<br />

Communications<br />

Qwest<br />

Communications<br />

Christofferson, Aelea<br />

Qwest<br />

Communications<br />

Christofferson, Aelea<br />

Qwest<br />

Communications<br />

Owner<br />

Director<br />

CR PM<br />

Suellentrop, Craig<br />

Retka, Mary<br />

White, Matt<br />

Buckmaster, Cindy<br />

Campbell, Bill<br />

White, Matt<br />

Buckmaster, Cindy<br />

Campbell, Bill<br />

White, Matt<br />

Van Dusen, Janean<br />

Bliss, Susie<br />

White, Matt<br />

Monday, June 02, 2003 Page 9 of 13


Report<br />

Line<br />

Number<br />

CR Number<br />

Current Status<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

37 PC040103-2 5/23/03 Grandfather Nebraska and Iowa<br />

Measured Service offerings.<br />

Development<br />

Wholesale<br />

ProdProc<br />

Qwest<br />

Communications<br />

38 PC042303-4 5/28/03 Implement New USOC PGO2N Wholesale<br />

Qwest<br />

ProdProc Communications<br />

Presented<br />

39 PC050503-1 6/02/03 Grandparent Switchnet 56. Wholesale<br />

Qwest<br />

ProdProc Communications<br />

Presented<br />

40 PC050503-2 6/02/03 Grandfather SVDS in all state<br />

tariffs including FCC tariff.<br />

Presented<br />

Information Current as of:<br />

Report Name:<br />

Wholesale<br />

ProdProc<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

Qwest<br />

Communications<br />

Owner<br />

Director<br />

CR PM<br />

Van Dusen, Janean<br />

Bliss, Susie<br />

White, Matt<br />

Paxton, Mallory<br />

Bliss, Susie<br />

Macy, Cindy<br />

Van Dusen, Janean<br />

Campbell, Bill<br />

White, Matt<br />

Van Dusen, Janean<br />

Campbell, Bill<br />

White, Matt<br />

Monday, June 02, 2003 Page 10 of 13


Report<br />

Line<br />

Number<br />

CR Number<br />

Current Status<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

41 PC050703-3 5/23/03 Release of microduct technology. Wholesale<br />

Qwest<br />

ProdProc Communications<br />

Presented<br />

42 PC050703-4 5/28/03 DC Power Changes Wholesale<br />

Qwest<br />

ProdProc Communications<br />

Presented<br />

43 PC050703-6 5/28/03 Grandfather Measured Service<br />

plans in CO, ID North, NM, ND<br />

Presented<br />

44 PC081302-1 5/28/03 Qwest to establish a standard<br />

business day minimum DD on Port<br />

CLEC Test<br />

In to Resale/UNE-P, 1 + Lines.<br />

Information Current as of:<br />

Report Name:<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

Qwest<br />

Communications<br />

Qwest<br />

Communications<br />

Lacy, Jane<br />

Owner<br />

Director<br />

CR PM<br />

Campbell, Bill<br />

White, Matt<br />

Campbell, Ben<br />

Campbell, William<br />

Macy, Cindy<br />

Van Dusen, Janean<br />

Campbell, William<br />

Macy, Cindy<br />

Wells, Joan<br />

Bliss, Susie<br />

Macy, Cindy<br />

Monday, June 02, 2003 Page 11 of 13


Report<br />

Line<br />

Number<br />

CR Number<br />

Current Status<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

45 PC112202-1 5/28/03 Held Order <strong>Process</strong>es when<br />

Qwest does not have Facilities<br />

CLEC Test<br />

46 PC032803-1ES 5/30/03 Qwest to halt the implementation<br />

of CLEC impacting process<br />

Denied<br />

changes with no notice.<br />

47 PC042303-5 5/23/03 Local Carrier Freeze: ensure<br />

effective when freeze placed by a<br />

Presented<br />

CLEC for a customer.<br />

48 PC050703-5 5/23/03 Service Manager Transition:<br />

Qwest to create a documented<br />

Presented<br />

and adhered to process for the<br />

transition of Service Managers<br />

and review and revise its Service<br />

Manager staffing practices for<br />

quality improvement.<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

Qwest<br />

Communications<br />

Tel West<br />

Tel West<br />

Tel West<br />

Note: There is supplemental information pertaining to this CR. A copy of the supplemental information immediately follows the the detail report for this CR.<br />

Information Current as of:<br />

Report Name:<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

Owner<br />

Director<br />

CR PM<br />

Carlson, Barbara<br />

Burson, Sue<br />

Macy, Cindy<br />

Schultz, Judy<br />

Schultz, Judy<br />

Macy, Cindy<br />

White, Matt<br />

Schultz, Judy<br />

White, Matt<br />

White, Matt<br />

Schultz, Judy<br />

White, Matt<br />

Monday, June 02, 2003 Page 12 of 13


Report<br />

Line<br />

Number<br />

CR Number<br />

Current Status<br />

Last<br />

Originator Company<br />

Update Title<br />

Organization<br />

Originator<br />

49 PC041603-1 5/28/03 Document ASR process for<br />

ordering EICT to and from<br />

Presented<br />

Collocations; with LOA, to and<br />

from MUXs<br />

50 PC050703-2 5/28/03 Supplimental Routing Form<br />

<strong>Process</strong><br />

Presented<br />

Information Current as of:<br />

Report Name:<br />

Wholesale<br />

ProdProc<br />

Wholesale<br />

ProdProc<br />

08 Summary of qry_DetailedReport_ProdProc Sorted by Submitter<br />

USLink<br />

XO Communication<br />

Owner<br />

Director<br />

CR PM<br />

Campbell, Ben<br />

Campbell, Bill<br />

Macy, Cindy<br />

Moffatt, Connee<br />

Retka, Mary<br />

Macy, Cindy<br />

Monday, June 02, 2003 Page 13 of 13


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC051403-4 Sync Test for Loop Splitting on Maintenance<br />

Trouble Tickets and Sync Testing for<br />

provisioning of Loop Splitting<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Provisioning /<br />

Maintenance &<br />

Repaire<br />

Loop Splitting<br />

Covad requests that Qwest extend their existing process of sync testing on provisioning of line share orders to include Sync Testing for Trouble<br />

Tickets on Loop Splitting. In addition, Covad requests that the current process of provisioning for line sharing be expanded to include Loop<br />

Splitting.<br />

Expected Deliverable<br />

As soon as possible<br />

Status History<br />

06/30/03 - Opened CR for Loop Splitting product on behalf of Covad, Loop Splitting product removed from CR PC051403-1<br />

07/16/03 - July <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

08/20/03 - August <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

09/17/03 - September <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

10/15/03 - October <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

11/19/03 - November <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

01/14/04 - Qwest issued PROD.01.14.04.F.01233.LoopSplittingV16 proposed effective date 2/28/04<br />

01/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

02/12/04 - Qwest issued Final notice PROD.02.12.04.F.01321.FNL_Loop_Split_V16 will become operational 2/27/04<br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Project <strong>Meeting</strong>s<br />

02/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Heidi Moreland with Qwest gave an update that the Loop Splitting V16 PCAT adding sync testing for provisioning and repair requests will become<br />

effective on 2/27/04. This CR will remain in Development status.<br />

_____________________________<br />

01/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Linda Sanchez-Steinke with Qwest gave an update that the Loop Splitting V16 PCAT adding sync testing for provisioning and repair requests was<br />

posted on 1/14/04 as a Level 3 notification. The comment cycle will close on 1/29/04 and the proposed effective date is 2/28/04. This CR will<br />

remain in Development status.<br />

______________________________<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Heidi Moreland with Qwest said the PCAT changes will be out in the January timeframe for review. This CR will remain in Development status.<br />

______________________________<br />

11/19/03 November <strong>CMP</strong> <strong>Meeting</strong><br />

Heidi Moreland with Qwest reviewed the revised response and said that the process is under development. At the December meeting there will be<br />

a status update. This CR will remain in Development status.<br />

______________________________<br />

10/15/03 October <strong>CMP</strong> <strong>Meeting</strong><br />

Heidi Moreland with Qwest reviewed the revised response and said that Qwest will implement this change request. Carla Pardee asked what date<br />

this would be implemented. Heidi Moreland said that we do not have an implementation date. This CR will move to Development status.<br />

______________________________<br />

09/17/03 September <strong>CMP</strong> <strong>Meeting</strong><br />

Heidi Moreland with Qwest gave an updated response that Qwest is evaluating this request. Covad agreed this CR remain in Evaluation status.<br />

______________________________<br />

08/20/03 August <strong>CMP</strong> <strong>Meeting</strong><br />

Heidi Moreland with Qwest provided an update that Qwest is investigating providing Sync testing for Loop Splitting. Loop Splitting follows the<br />

design flow using TIRKS and the two databases, TIRKS and Switch/FOMS do not communicate with each other. Qwest would like to keep this CR<br />

in evaluation status while during further investigation and will provide an update at the September meeting.<br />

______________________________<br />

07/16/03 July <strong>CMP</strong> <strong>Meeting</strong><br />

Craig Suellentrop with Qwest explained that this CR was opened to address Sync testing for Loop Splitting. Craig presented the response for this<br />

CR saying that Qwest needs more time to evaluate sync testing for the Loop Splitting product. This CR will move to Evaluation status.<br />

Qwest Response<br />

Retka, Mary<br />

Berard, John<br />

Moreland, Heidi<br />

Sanchez-Steinke, Linda<br />

Information Current as of:<br />

Report Name:<br />

Development<br />

11/19/03<br />

Originator Company Name:<br />

Covad<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

17<br />

<strong>Product</strong>s<br />

Impacted<br />

PC051403-4<br />

Page 65 of 105<br />

Attachment D


November 11, 2003<br />

For Review by the CLEC Community and Discussion at the November 19, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

John Berard<br />

Director - Operations Support<br />

Covad Communications<br />

SUBJECT:Qwest’s Change Request Response - PC051403-4<br />

Sync Test for Loop Splitting on Maintenance Trouble Tickets and Sync Testing for provisioning of Loop Splitting<br />

This letter is in response to CLEC Change Request PC051403-4. This CR is a request by Covad for Qwest to extend the existing process of<br />

Synchronization Testing on Line Sharing requests to include the Loop Splitting product. Covad also requests that Sync Testing be implemented<br />

for repair tickets on Loop Splitting.<br />

This CR has been accepted and is currently under development. Qwest will expand the current provisioning process to include Sync Testing on<br />

Loop Splitting. For Loop Splitting repair, Qwest will perform Sync Testing upon CLEC request..<br />

Sincerely,<br />

Heidi Moreland<br />

Staff Advocate Policy and Law<br />

Qwest<br />

Craig Suellentrop<br />

Staff Advocate Policy and Law<br />

Qwest<br />

----------------------------------------------------------------<br />

October 1, 2003<br />

REVISED DRAFT RESPONSE<br />

For Review by the CLEC Community and Discussion at the October 15, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

John Berard<br />

Director - Operations Support<br />

Covad Communications<br />

SUBJECT: Qwest’s Change Request Response - PC051403-4<br />

"Sync Test for Loop Splitting on Maintenance Trouble Tickets and Sync Testing for provisioning of Loop Splitting"<br />

This letter is in response to CLEC Change Request PC051403-4. This CR is a request by Covad for Qwest to extend the existing process of<br />

Synchronization Testing on Line Sharing requests to include the Loop Splitting product. Covad also requests that Sync Testing be implemented<br />

for repair tickets on Loop Splitting.<br />

Qwest is accepting this CR for Sync Testing on Loop Splitting provisioning and repair and ask that it be moved into the development stage.<br />

Sincerely,<br />

Heidi Moreland<br />

Staff Advocate Policy and Law<br />

Qwest<br />

Craig Suellentrop<br />

Staff Advocate Policy and Law<br />

Qwest<br />

___________________________<br />

September 9, 2003<br />

REVISED DRAFT RESPONSE<br />

For Review by the CLEC Community and Discussion at the September 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC051403-4<br />

Page 66 of 105<br />

Attachment D


John Berard<br />

Director - Operations Support<br />

Covad Communications<br />

SUBJECT: Qwest’s Change Request Response - PC051403-4<br />

"Sync Test for Loop Splitting on Maintenance Trouble Tickets and Sync Testing for provisioning of Loop Splitting"<br />

This letter is in response to CLEC Change Request PC051403-4. This CR is a request by Covad for Qwest to extend the existing process of<br />

Synchronization Testing on Line Sharing requests to include the Loop Splitting product. Covad also requests that Sync Testing be implemented<br />

for repair tickets on Loop Splitting.<br />

Qwest is requesting an additional extension of the evaluation period for this CR for Sync Testing on Loop Splitting provisioning and repair.<br />

Today, for central office based Shared Loop DSLAMS, Qwest populates the Synchronization Testing protocol (i.e., DMT, etc.) into our<br />

Switch/FOMS database. This works well for central office based Line Sharing and Line Splitting products since they follow the POTS process flow<br />

and Switch/FOMS is utilized for POTS services. The Loop Splitting product follows Qwest’s designed service process and as such uses the<br />

TIRKS database. Switch/FOMS and TIRKS are not compatible systems nor are they linked to transfer information. Qwest is requesting this CR<br />

remain in evaluation status to enable further systems capability analysis. The complexity of the systems issues requires deep analysis from many<br />

departments and Qwest continues to explore possible options. Qwest will provide a revised response at the October <strong>CMP</strong> meeting.<br />

Sincerely,<br />

Heidi Moreland<br />

Staff Advocate Policy and Law<br />

Qwest<br />

Craig Suellentrop<br />

Staff Advocate Policy and Law<br />

Qwest<br />

_____________________<br />

August 13, 2003<br />

DRAFT RESPONSE<br />

For Review by the CLEC Community and Discussion at the August 20, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

John Berard<br />

Director - Operations Support<br />

Covad Communications<br />

SUBJECT: Qwest’s Change Request Response - PC051403-4<br />

"Sync Test for Loop Splitting on Maintenance Trouble Tickets and Sync Testing for provisioning of Loop Splitting"<br />

This letter is in response to CLEC Change Request PC051403-4. This CR is a request by Covad for Qwest to extend the existing process of<br />

Synchronization Testing on Line Sharing requests to include the Loop Splitting product. Covad also requests that Sync Testing be implemented<br />

for repair tickets on Loop Splitting.<br />

Qwest is requesting an extension of the evaluation period for this CR for Sync Testing on Loop Splitting provisioning and repair.<br />

Today, for central office based Shared Loop DSLAMS, Qwest populates the Synchronization Testing protocol (i.e., DMT, etc.) into our<br />

Switch/FOMS database. This works well for central office based Line Sharing and Line Splitting products since they follow the POTS process flow<br />

and Switch/FOMS is utilized for POTS services. The Loop Splitting product follows Qwest’s designed service process and as such uses the<br />

TIRKS database. Switch/FOMS and TIRKS are not compatible systems nor are they linked to transfer information. Qwest is requesting this CR<br />

remain in evaluation status to enable further systems capability analysis. Qwest will provide a revised response at the September <strong>CMP</strong> meeting.<br />

Sincerely,<br />

Heidi Moreland<br />

Staff Advocate Policy and Law<br />

Qwest<br />

Craig Suellentrop<br />

Staff Advocate Policy and Law<br />

Qwest<br />

________________________________<br />

July 2, 2003<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC051403-4<br />

Page 67 of 105<br />

Attachment D


DRAFT RESPONSE<br />

For Review by the CLEC Community and Discussion at the July 16, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

John Berard<br />

Director Operations Support<br />

Covad<br />

SUBJECT: Qwest’s Change Request Response - CR 051403-4<br />

"Sync Test for Loop Splitting on Maintenance Trouble Tickets and Sync Testing for provisioning of Loop Splitting"<br />

This CR requests that Qwest extend the existing process of Sync Testing on Line Sharing requests to include the Loop Splitting product. Covad<br />

also requests that Sync Testing be implemented for repair tickets on Loop Splitting.<br />

Since the Loop Splitting product follows Qwest’s designed services process while Line Sharing and Line Splitting follow the non-designed process,<br />

this request is much more complex than PC051403-1. Different systems are used for designed products and a different process would be<br />

required. Because of this complexity, Qwest needs additional time to evaluate this request. This change request should be placed in evaluation<br />

status.<br />

Sincerely,<br />

Craig Suellentrop, Staff Advocate-Policy & Law, Qwest<br />

Heidi Moreland, Staff Advocate-Policy & Law, Qwest<br />

Cc: Mary Retka, Director, Legal Issues<br />

Jamal Boudhaouia, Staff Advocate-Policy & Law, Qwest<br />

Debra S. Smith, <strong>Product</strong> Manager, Qwest<br />

Catherine R. Garcia, Lead <strong>Process</strong> Analyst, Qwest<br />

Michael Lanoue, Lead <strong>Process</strong> Analyst, Qwest<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC051403-4<br />

Page 68 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC061103-<br />

1ES<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Intercept CLEC customer calls to Qwest<br />

Repair Center<br />

Wholesale ProdProc Maintenance<br />

repair<br />

Currently, when an AT&T UNE-P end-user customer calls the Qwest repair line (800-573-1311), the call is routed to a Qwest representative, who<br />

then provides the customer with an AT&T 800 number. AT&T requests that Qwest change this procedure so that the call is intercepted when the<br />

customer enters their TN, and the customer should hear a branded message to the AT&T 1-800 repair number (800-288-2747).<br />

There are several reasons for this request: AT&T customers should not be speaking to a Qwest representative; it would be much more efficient to<br />

route the call directly to AT&T; it eliminates potential representative errors, and; it reduces the number of calls to the Qwest center.<br />

Expected Deliverable:<br />

August 2003<br />

Status History<br />

06/11/03 - CR Received<br />

06/12/03 - CR Acknowledged<br />

06/18/03 - June <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

06/24/03 - Held Clarification <strong>Meeting</strong><br />

07/16/03 - July <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

08/20/03 - August <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

09/17/03 - September <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

10/15/03 - October <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

10/21/03 - Qwest received escalation from AT&T<br />

10/21/03 - Qwest issued notificaiton, <strong>CMP</strong>R.10.21.03.F.01597.EscalationNotification<br />

11/19/03 - November <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

01/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Project <strong>Meeting</strong>s<br />

Retka, Mary<br />

Pardee, Carla<br />

Boudhaouia, Jamal<br />

Sanchez-Steinke, Linda<br />

Development<br />

9/17/03<br />

Originator Company Name:<br />

Report Line Number<br />

02/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Jamal Boudhaouia with Qwest said that funding for the project has been approved and will provide a date for implementation as soon as available.<br />

Bonnie Johnson said that she has asked several times and has not received an answer about the Qwest retail VRU project and when that is<br />

scheduled for implementation or has it been implemented. Jamal said that the project hasn’t been implemented and all changes will be<br />

incorporated and will include the CR requested changes. Bonnie said that Qwest hasn’t made clear what the implementation date will be. Carla<br />

Pardee with AT&T said that the changes were supposed to be effective in April. Jamal said there is currently no date for implementation. Carla<br />

said that the CR is important to AT&T and would like to see solid dates next month adding that the CR was escalated previously and did not do any<br />

good. Judy Schultz with Qwest said that we had just received word that funding was approved on Friday and IT will determine the dates as soon<br />

as possible. The dates will be provided, if available, before the <strong>March</strong> meeting. Bonnie said that Qwest had already provided the implementation<br />

date of April, (comment begin from Eschelon) <strong>2004</strong> but now states that this was just approved. Judy said all changes had to be reevaluated by<br />

Noteabart. (comment end from Eschelon). This CR will remain in Development status.<br />

____________________________________<br />

01/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Jamal Boudhaouia with Qwest provided an update that there is no date for implementation. Bonnie Johnson with Eschelon thought this was going<br />

to be worked in conjunction with a Qwest retail project. Judy Schultz with Qwest said that this is one of the projects subject to the funding approval<br />

process. Even projects that had previously been approved are subject to the new approval process. Qwest will find out when the internal project<br />

for the VRU will be worked and how these two projects are connected. This CR will remain in Development status. (Begin comment from Bonnie<br />

Johnson - Eschelon) Qwest took an action to review this CR. Bonnie said this CR was waiting for an update already underway for the VRU. That<br />

was the delay after this was opened in June 2003. (end comment).<br />

_____________________________________<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Jamal Boudhaouia with Qwest said that the CR is in development status and have no update on timeframe for implementation. Carla Pardee with<br />

AT&T said they would like to see progress on this CR by next month or AT&T will escalate the CR. This CR will remain in Development status.<br />

_____________________________________<br />

11/19/03 November <strong>CMP</strong> <strong>Meeting</strong><br />

Craig Suellentrop said that Qwest has accepted this CR and will make changes to the VRU. Work will be going on in the Qwest VRU and will<br />

provide implementation dates as soon as available. Carla Pardee with AT&T said that this CR has been open since June and AT&T would like a<br />

formal commitment on the timeframe. This CR will remain in Development Status.<br />

Information Current as of:<br />

Report Name:<br />

AT&T<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

UNE-P<br />

18<br />

<strong>Product</strong>s<br />

Impacted<br />

PC061103-1ES<br />

Page 69 of 105<br />

Attachment D


_____________________________________<br />

10/15/03 October <strong>CMP</strong> <strong>Meeting</strong><br />

Craig Suellentrop said that Qwest is looking at redesigning the repair VRU and plan to include changes for this CR at the same time. Carla Pardee<br />

with AT&T said AT&T is anxious to get the changes in place and asked for the implementation date. Craig said he hopes to have implementation<br />

dates for the November <strong>CMP</strong> meeting. Carla asked if the changes Qwest is looking at to make to the VRU should be included in a Qwest initiated<br />

<strong>CMP</strong> CR. Craig said it is still being looked at and determination has not been made if a CR will be required. This CR will remain in Development<br />

Status.<br />

_____________________________________<br />

09/17/03 September <strong>CMP</strong> <strong>Meeting</strong><br />

Craig Suellentrop said that Qwest accepts this CR with an implementation expected in 90 - 120 days. When a customer calls into the repair VRU<br />

between 11:30 p.m. - 5 a.m. the system accessed by the VRU to perform the ownership check may be down and the caller will automatically be<br />

transferred to a repair agent. However, during this time the system used by Qwest’s repair agents can still identify if a line is owned by a CLEC<br />

and will be able to direct the end-user to their local carrier. This CR will be moved to Development status.<br />

_____________________________________<br />

08/20/03 August <strong>CMP</strong> <strong>Meeting</strong><br />

Craig Suellentrop with Qwest reviewed the draft response to this CR. Craig said that Qwest has mapped the different ways that end users can get<br />

into repair VRU and now need the LOE. Qwest will have an update at the September meeting. This CR will be moved to Evaluation status.<br />

______________________________________<br />

07/16/03 July <strong>CMP</strong> <strong>Meeting</strong><br />

Carla Pardee with AT&T presented this CR. Craig Suellentrop with Qwest explained the current repair VRU process. When an end user calls into<br />

repair they enter the telephone number they are calling about. If the end user presses 1 for a repair agent the VRU does no ownership check and<br />

the repair agent inputs the telephone and if the telephone number is CLEC owned the repair agent refers the end user to their alternate provider. If<br />

the end user presses 2 for automatic ticket entry and the number is CLEC owned, the VRU will respond that the number is not serviced by Qwest.<br />

Then the end user can press 1, if they are the customer for the account. If it is a TN owned by an alternate service provider, the VRU reads the<br />

repair number for end user to call for repair services. If the VRU does not recognize the TN, it reads contact your service provider for assistance.<br />

Carla with AT&T would like the VRU to respond when the end user enters a telephone number owned by alternate provider, by intercepting the call<br />

and routing it to the correct company. Craig will provide the VRU process to the CLEC Community for input on changes.<br />

______________________________________<br />

CLEC Change Request<br />

Clarification <strong>Meeting</strong><br />

2:00 p.m. (MT) / Tuesday, June 24, 2003<br />

1-877-572-8687<br />

PIN 3393947 #<br />

PC061103-1 Intercept CLEC customer calls to Qwest Repair Center<br />

Name/Company:<br />

Donna Osborne-Miller, AT&T<br />

Dave Fane, AT&T<br />

Lydia Braze, AT&T<br />

Cathy Garcia, Qwest<br />

Craig Suellentrop, Qwest<br />

Michael Whitt, Qwest<br />

Linda Sanchez-Steinke, Qwest<br />

Introduction of Attendees<br />

Introduction of participants on the conference call was made and the purpose of the call discussed.<br />

Review Requested (Description of) Change<br />

The description of the change requested in the CR was reviewed. Currently, when an AT&T UNE-P end-user customer calls the Qwest repair line<br />

(800-573-1311), the call is routed to a Qwest representative, who then provides the customer with an AT&T 800 number. AT&T requests that<br />

Qwest change this procedure so that the call is intercepted when the customer enters their TN, and the customer should hear a branded message<br />

to the AT&T 1-800 repair number (800-288-2747). There are several reasons for this request: AT&T customers should not be speaking to a<br />

Qwest representative; it would be much more efficient to route the call directly to AT&T; it eliminates potential representative errors, and; it reduces<br />

the number of calls to the Qwest center.<br />

Dave Fane clarified that the intercept should be implemented for all CLEC customers, not just AT&T customers, and that the end user should be<br />

routed to the correct CLEC branding. In the testing, Dave used an AT&T test number and called into repair 6 or 8 times with different results.<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

<strong>Product</strong> impacted UNE-P<br />

Confirm Right Personnel Involved<br />

Qwest confirmed that Craig Suellentrop & Cathy Garcia are correct personnel to resolve the CR.<br />

Identify/Confirm CLEC’s Expectation<br />

AT&T would like this change to be effective in August 2003 .<br />

Identify any Dependent Systems Change Requests<br />

No dependent change requests were identified.<br />

Establish Action Plan (Resolution Time Frame)<br />

AT&T will present this CR at the July <strong>CMP</strong> <strong>Meeting</strong> and Qwest will provide response at the August <strong>CMP</strong>. Donna Osborne-Miller requested that<br />

Qwest provide a response or an update if available at the July <strong>CMP</strong>.<br />

_____________________________________<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC061103-1ES<br />

Page 70 of 105<br />

Attachment D


06/18/03 June <strong>CMP</strong> <strong>Meeting</strong><br />

Carla Pardee, Lydia Braze and Dave Fane with AT&T reviewed the walk on CR PC061103-1. Dave said that customers within the Qwest territory<br />

without Qwest local service call Qwest repair and AT&T would like the IVR to have the ability to route customers to AT&T and identify that the TN<br />

does not belong to Qwest. Other ILECs have this ability and it reduces calls to the repair center, mistakes made by repair representatives, and<br />

reduces call time for end users, who sometimes are involved in a call taking up to 3-4 minutes before the repair representative recognizes that the<br />

customer is not a Qwest customer. Eschelon, U S Link and McLeod all said they support this change request. Lynne Powers with TelWest asked<br />

if the end user would be inputting their telephone number and Dave said that is what occurs in the PacBell region. There will be a clarification call<br />

on this change request.<br />

Qwest Response<br />

September 9, 2003<br />

For Review by the CLEC community and discussion at the September 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Carla Pardee<br />

AT&T<br />

SUBJECT: Qwest’s Change Request Response - CR PC061103-1<br />

"Intercept CLEC customer calls to the Qwest Repair Center"<br />

This CR requests that when a CLEC end-user calls into Qwest repair “the call is intercepted when the end-user enters their TN, and the customer<br />

should hear a branded message to the [CLEC] 1-800 repair number.<br />

The August response illustrated Qwest’s current Voice Response Unit (VRU) scripting when an end-user calls into Qwest repair. For this CR<br />

Qwest investigated the possibility of performing the ownership check and replaying the same scripts for Option 2 as are performed for Option 1.<br />

Qwest accepts this CR and will make the changes indicated above. The systems accessed for this ownership check may be down for<br />

maintenance nightly between 11:30 pm and 5:00 am Mountain Time. Therefore, during this period, it may not be possible to perform the<br />

ownership check. However, the system used by Qwest’s repair agents will still detect if a line is owned by a CLEC and the agent will direct the enduser<br />

to call his or her local carrier.<br />

Sincerely,<br />

Craig Suellentrop<br />

Staff Advocate, Policy & Law<br />

Qwest<br />

Cc: Mary Retka, Director-Legal Issues, Qwest<br />

Catherine R. Garcia, Lead <strong>Process</strong> Analyst, Qwest<br />

Cheryl Rock, Senior <strong>Process</strong> Analyst, Qwest<br />

_____________________________<br />

August 13, 2003<br />

DRAFT RESPONSE<br />

For Review by the CLEC Community and Discussion at the August 20, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Carla Pardee<br />

AT&T<br />

SUBJECT: Qwest’s Change Request Response - PC061103-1<br />

"Intercept CLEC customer calls to the Qwest Repair Center"<br />

AT&T’s CR requests that when a CLEC end-user calls into Qwest repair "the call is intercepted when the end-user enters their TN, and the<br />

customer should hear a branded message to the [CLEC] 1-800 repair number."<br />

The attached document illustrates Qwest’s current Voice Response Unit (VRU) scripting when an end-user calls into Qwest repair. For this CR,<br />

Qwest investigated the possibility of performing the ownership check and replaying the same scripts for Option 2 as are performed for Option 1.<br />

The direct number to get into repair for all 14 states in Qwest’s local service region is 1-800-573-1311. However, other Qwest VRU systems have<br />

options allowing the caller to transfer to Local Network repair. Callers coming from these other systems do not always input their TN into the repair<br />

VRU. Because of this, Qwest has to map all of the various methods of getting into the repair VRU and determine how/if an ownership check can<br />

be conducted. Qwest is now in the process of getting an estimate for feasibility to perform the ownership check.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC061103-1ES<br />

Page 71 of 105<br />

Attachment D


Qwest will provide a revised response at the September <strong>CMP</strong> meeting with the findings of this research.<br />

Sincerely,<br />

Craig Suellentrop<br />

Staff Advocate, Policy & Law<br />

Qwest<br />

Cc: Mary Retka, Director-Legal Issues, Qwest<br />

Catherine R. Garcia, Lead <strong>Process</strong> Analyst, Qwest<br />

Cheryl Rock, Senior <strong>Process</strong> Analyst, Qwest<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC061103-1ES<br />

Page 72 of 105<br />

Attachment D


Qwest Repair VRU<br />

When an end user calls into repair they enter the telephone number they are calling about.<br />

• Option 1: allows the caller to enter an automated trouble ticket using a touch tone phone. An ownership<br />

check is performed on the number. If the TN is not served by Qwest the following message is returned,<br />

“The number you have entered is not serviced by Qwest. If you’re the customer for this account, Press 1.<br />

If you are the alternate service provider, Press 2.<br />

• Option 1: If Qwest recognizes who the alternate service provider is on the account and has a TN<br />

for that providers repair, the following message is returned. “The number for their repair service<br />

is (Alternate Providers TN). To repeat this information Press *. Or, if you are in the process of<br />

establishing your service with Qwest, press 1 now to speak with a Qwest Representative.<br />

Otherwise, Thank you for calling Qwest.”<br />

If Qwest does not recognize who the alternate service provider is on the account or does not have<br />

a TN for that providers repair bureau, then the following message is returned. “Since your<br />

telephone number is serviced by a company other than Qwest, you must contact that provider for<br />

assistance. If you would like to speak to a Qwest representative, Press 1. Otherwise, Thank you<br />

for calling Qwest.”<br />

• Option 2: Transfers call to Qwest Repair Agent.<br />

• Option 2: allows the caller to speak immediately to a Qwest Repair Agent. No ownership check is made<br />

by the VRU. When the Repair Agent enters the number into the Qwest system, a message is returned<br />

advising that this number is for an alternate provider. If the caller is not the alternate provider, the agent<br />

advises the caller to call their service provider and will provide that alternate service providers TN, if<br />

available.


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC070103-1 Provide "Lines In Service Report" to CLECs Development Wholesale ProdProc Resale, UNE P<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

MCI is requesting that Qwest implement a "Lines In Service Report". This report would result in what Qwest reflects as active UNE-P and Resale<br />

lines in service that belong to a given CLEC on the date the report is generated. MCI is requesting that the report be provided on a monthly basis<br />

via CD-ROM or equivalent media type. This report would provide needed insight to any discrepancies between CLEC customer data and Qwest<br />

data and assist with reconciliation efforts.<br />

Information MCI requests on the report:<br />

- CLEC Name<br />

- ACNA - Access Customer Name Abbreviation<br />

- BTN - Billing Telephone Number<br />

- WTN - Working Telephone Number<br />

- Service Delivery Method<br />

- Original Migrate/Completion Date<br />

- Date of snapshot extract<br />

- Type of Service (Bus/Res)<br />

- State<br />

Expected Deliverable:<br />

That Qwest provide a "lines in service report" for UNE-P and Resale lines on a monthly basis via CD-ROM or equivalent media type.<br />

Status History<br />

Balvin, Liz<br />

07/01/03 - CR Received<br />

07/01/03 - CR Acknowledged<br />

07/11/03 - Held Clarification <strong>Meeting</strong><br />

07/16/03 - July <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

08/20/03 - August <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

09/17/03 - September <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

10/15/03 - October <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

10/29/03 - Held Ad Hoc <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

11/19/03 - November <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

01/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

02/27/04 - Qwest issued PROS.02.27.04.F.01409.LinesInServiceReport effective immediately<br />

Project <strong>Meeting</strong>s<br />

Staebell, Todd D.<br />

Mcghghy, Laua<br />

Sanchez-Steinke, Linda<br />

9/17/03<br />

Originator Company Name:<br />

Report Line Number<br />

<strong>Product</strong>s<br />

Impacted<br />

02/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Laura McGhghy with Qwest gave an update that 2/27/04 is targeted to provide the January data. In addition to the report, there will be a product<br />

code explanation file that provides a product code definition. Jennifer Arnold with U S Link asked how to get the report. Laura explained they<br />

should contact their service manager to request. This CR will remain in Development status.<br />

_______________________<br />

01/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Laura McGhghy with Qwest gave an update that January data will be provided at the end of February and that a notification will be sent. This CR<br />

will remain in Development status.<br />

_________________________<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Laura McGhghy with Qwest gave an update on the CR. Laura said that during the ad hoc meeting she had an action item to determine if BTN<br />

would be available for non-design services. BTN will not be available for non-design services and will be available for design services. Laura<br />

added that the reports will be provided by state and each state will have one report for design services and one report for non-design services. Liz<br />

Balvin with MCI clarified that the reports will be state specific and will be broken down by design and non-design reports. This CR will remain in<br />

Development status.<br />

_________________________<br />

11/19/03 November <strong>CMP</strong> <strong>Meeting</strong><br />

Laura McGhghy with Qwest provided an update on this CR and said that Qwest is continuing development and expects to provide January results<br />

Information Current as of:<br />

Report Name:<br />

MCI<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

19<br />

PC070103-1<br />

Page 73 of 105<br />

Attachment D


in the February timeframe. Liz Balvin with MCI asked how the CLECs would get the data. Laura said that the data will be available where the PID<br />

results are located. This CR will remain in Development Status.<br />

_________________________<br />

Ad Hoc <strong>Meeting</strong> Minutes<br />

PC070103-1<br />

Provide "Lines In Service Report" to CLECs<br />

<strong>CMP</strong> <strong>Product</strong> & <strong>Process</strong><br />

October 29, 2003<br />

1-877-572-8687, Conference ID 3393947#<br />

9:00 a.m. - 10:00 a.m. Mountain Time<br />

PURPOSE<br />

At the October <strong>CMP</strong> <strong>Meeting</strong>, participants agreed to hold a conference call to review the format for the report.<br />

The following is the write-up of the discussion.<br />

List of Attendees:<br />

Donna Osborne-Miller, AT&T<br />

Liz Balvin, MCI<br />

Kim Issaacs, Eschelon<br />

Kathy Stitcher, Eschelon<br />

Cedric Cox, MCI<br />

Ed Boehme, MCI<br />

Laura McGhghy, Qwest<br />

Dave Phillips, Qwest<br />

Jon Boisseau, Qwest<br />

Linda Sanchez-Steinke, Qwest<br />

MEETING MINUTES<br />

The meeting began with Qwest making introductions and welcoming all attendees.<br />

Linda Sanchez-Steinke with Qwest explained that the purpose of the meeting was to review the draft report format. Laura McGhghy with Qwest<br />

reviewed the draft reports. Resale design products and non-design products will be available in two files. Design <strong>Product</strong>s report will include;<br />

CLEC ID, ACNA, BTN, Circuit ID, <strong>Product</strong> Code, Extract date, and State. Non-Design <strong>Product</strong>s report will include; CLEC ID, WTN, <strong>Product</strong> Code,<br />

Extract Date and State.<br />

Liz Balvin with MCI asked for further definition of the product code. Laura McGhghy said that the product name, i.e., DS1 would mean resale<br />

DS1. Liz asked if the CLEC ID would be the RSID. Laura said yes.<br />

Laura continued explaining the report and said that the original migration date is not something that is in our system and is unavailable for the<br />

reports.<br />

Cedric Cox with MCI asked if the BTN is available on non-design and added that most ILECs normally want the BTN with the WTN for disputes.<br />

Dave Phillips said that BTN is not available in the data that will be provided with the current report design. Cedric asked if the customer has<br />

multiple lines, will the WTNs show on the report as belonging to the CLEC. Dave answered yes. Laura took an action item to find out if BTN is<br />

available on the non-design data.<br />

Liz Balvin asked if the report was derived from PREMIS or CRIS, as PREMIS only has WTN data. Dave said that the non-design data is coming<br />

from LMOS, and the design data is from TIRKS.<br />

Cedric asked if there was a dispute on a WTN would the CLEC have to provide the BTN. Dave Phillips answered that we would have to work<br />

through disputes with the data available.<br />

Liz asked if the extract date is the date the data is pulled from LMOS. Dave and Laura responded that it is the date the data is pulled from either<br />

LMOS or TIRKS.<br />

Cedric asked if there will be indication of Residence or Business. Laura said that Res or Bus will be in the product code. Laura and Dave<br />

committed to provide a list of the prod_cd’s and their English names to MCI.<br />

Liz asked if they could get valid values populated and what date the reports would be available. Laura said that when the data is pulled the extract<br />

date is a snapshot of the date it occurs. Dave will find out when the data will be pulled and get back to MCI.<br />

Cedrick asked what the dispute process is if they have 1000 ANI’s that they believe do not belong to them. Jon Boisseau said there is the informal<br />

reconciliation process, the formal process through the PAP and Service Management can also take the dispute to regulatory reporting.<br />

Kathy Stitcher with Eschelon asked if unbundled loop would be in the design file. Laura said that resale and any other design type products would<br />

be in the design file.<br />

Linda asked if there were any questions. No questions were asked.<br />

_______________________________<br />

10/15/03 October <strong>CMP</strong> <strong>Meeting</strong><br />

Laura McGhghy with Qwest provided an update on this CR. Qwest plans to have January data available in the month of February. Laura would<br />

like to hold an ad hoc meeting to discuss the draft format of the report. Linda Sanchez-Steinke will e-mail Liz with possible dates for the meeting.<br />

This CR will remain in Development Status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC070103-1<br />

Page 74 of 105<br />

Attachment D


__________________________________________<br />

09/17/03 September <strong>CMP</strong> <strong>Meeting</strong><br />

Laura McGhghy with Qwest provided the Qwest draft response. Qwest will provide the report requested and target January <strong>2004</strong> for the data to be<br />

available. Liz Balvin said would like to see the data in a draft form as soon as available. Other CLECs would like to get the report as well and<br />

Laura said they should request the report through their service manager. This CR will move to Development Status.<br />

__________________________________________<br />

08/20/03 August <strong>CMP</strong> <strong>Meeting</strong><br />

Laura McGhghy with Qwest reviewed the draft response and said Qwest is investigating possible solutions for this CR and will have an updated<br />

response at the September meeting. This CR will be moved to Evaluation status.<br />

__________________________________________<br />

07/16/03 July <strong>CMP</strong> <strong>Meeting</strong><br />

Liz Balvin with MCI presented this CR. MCI would like a monthly report of UNE-P and Resale lines in service. This report would give the ability to<br />

sync up the lines in service with the CLEC and Qwest. Sue Kriebel asked for the name of the report provided for access lines and Liz will provide<br />

the information to Linda Sanchez-Steinke. Dusti Bastian asked what additional data fields would be included in the monthly report vs. the daily<br />

loss and completion report. Liz said this report will be on a specific month timeframe and will include lines in service Qwest identifies and tie back<br />

to losses, helping to track and resolve issues. Sue Kriebel asked how the monthly report would be different from the CSR report that identifies<br />

lines in service. Liz said they have to access the CSR. Sue said the CSR is received along with the bill, and when the bill is received you can see<br />

the TN that is being billed. Liz said that billing isn’t what Qwest identifies as the lines in service and there would also be timing issues with the<br />

CSR report. Sue asked if the monthly report would be pulled on a different day than the bill and Liz said MCI wants the report pulled on the 1st or<br />

the 31st of the month. Bonnie Johnson with Eschelon said that the loss and completion report received daily only identifies service order activity<br />

and not total lines in service. Liz would like to understand why the CR was unilaterally changed to a <strong>Product</strong> / <strong>Process</strong> CR and Kit Thomte with<br />

Qwest apologized that the CR was acknowledged as <strong>Product</strong> and <strong>Process</strong> without an explanation when MCI had requested it be a Systems CR.<br />

____________________________________________<br />

CLEC Change Request<br />

Clarification <strong>Meeting</strong><br />

3:00 p.m. (MDT) / Friday, July 11, 2003<br />

1-877-572-8687<br />

3393947#<br />

PC070103-1 Provide "Lines In Service Report" to CLECs<br />

Name/Company:<br />

Liz Balvin, MCI<br />

Cedric Cox, MCI<br />

Donna Lucio, Qwest<br />

Fred Howard, Qwest<br />

Kerri Waldner, Qwest<br />

Luke Von Hagen, Qwest<br />

Don Kerschner, Qwest<br />

Laurel Nolan, Qwest<br />

Linda Sanchez-Steinke, Qwest<br />

Introduction of Attendees<br />

Introduction of participants on the conference call was made and the purpose of the call discussed.<br />

Review Requested (Description of) Change<br />

MCI’s CR requests that Qwest implement a "Lines In Service Report". This report would result in what Qwest reflects as active UNE-P and Resale<br />

lines in service that belong to a given CLEC on the date the report is generated. MCI is requesting that the report be provided on a monthly basis<br />

via CD-ROM or equivalent media type. This report would provide needed insight to any discrepancies between CLEC customer data and Qwest<br />

data and assist with reconciliation efforts.<br />

Information MCI requests on the report:<br />

- CLEC Name<br />

- ACNA - Access Customer Name Abbreviation<br />

- BTN - Billing Telephone Number<br />

- WTN - Working Telephone Number<br />

- Service Delivery Method<br />

- Original Migrate/Completion Date<br />

- Date of snapshot extract<br />

- Type of Service (Bus/Res)<br />

- State<br />

Liz Balvin with MCI said that Qwest has a similar lines in service report on the Access side and this report allows a sync up with installed services<br />

and allows them to catch discrepancies sooner. Kerri Waldner with Qwest asked if the items requested are being provided in any other report. Liz<br />

said that she is not aware of any other report providing this information. Dusti Bastian asked for a definition of Service Delivery Method. Cedric<br />

said that is the product type, resale or UNE-P. Fred Howard asked if the report was requesting data for MCI only. Cedric answered yes, MCI only<br />

is what is requested. Dusti asked if this report would be for services billed or for services provisioned. Cedric said for those services provisioned.<br />

Kerri asked if the report would be a snapshot in time with no accumulation. Cedric said that the report would be a snapshot in time.<br />

Donna Lucio asked about the timing of the report and if MCI would want the report at the first or the last of the month. Liz and Cedric said it didn’t<br />

matter what date the report is pulled and that they are looking for a monthly report.<br />

Cedric said that MCI would take the TN’s and bounce them against a database for telco billing and traffic data. This would give them line loses<br />

that they hadn’t been made aware of previously. Kerri asked if MCI wants to get this monthly, would it be a snap shot in time or a monthly<br />

compilation. Liz and Cedric answered they would like a snapshot in time and don’t need a cumulative report.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC070103-1<br />

Page 75 of 105<br />

Attachment D


Liz said that she is concerned with the unilateral conversion process that this CR was moved to <strong>Product</strong> and process and would like an explanation<br />

why the CR was handled in this way.<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

<strong>Product</strong>s impacted with this CR are UNE and Resale Lines.<br />

Confirm Right Personnel Involved<br />

Qwest confirmed the correct personnel were on the call to resolve the CR.<br />

Identify/Confirm CLEC’s Expectation<br />

MCI’s expectation is a monthly report for active UNE-P and Resale lines in service.<br />

Identify any Dependent Systems Change Requests<br />

No systems change requests.<br />

Establish Action Plan (Resolution Time Frame)<br />

MCI will present this CR at the July <strong>CMP</strong> meeting.<br />

Qwest Response<br />

September 9, 2003<br />

Liz Balvin<br />

MCI<br />

SUBJECT: Qwest’s Change Request Response - CR PC070103-1<br />

"Provide 'Lines in Service Report' to CLECs".<br />

As a follow up to the August 20, 2003 <strong>CMP</strong> <strong>Meeting</strong>, Qwest is willing to provide a monthly report of all MCI lines in service for all products currently<br />

reported in 271 reporting.<br />

This report will be available to MCI from the secure website where MCI obtains all other PID reporting data.<br />

Qwest is beginning investigation and coding work at this time and expects to have the data available to MCI in January <strong>2004</strong>.<br />

Sincerely,<br />

Laura McGhghy<br />

Lead <strong>Process</strong> Analyst<br />

Qwest<br />

___________________________<br />

August 13, 2003<br />

DRAFT RESPONSE<br />

For Review by the CLEC Community and Discussion at the August 20, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Liz Balvin<br />

MCI<br />

SUBJECT: Qwest’s Change Request Response - PC070103-1<br />

Provide "Lines In Service Report" to CLECs<br />

MCI’s CR requests that Qwest provide a report reflecting active UNE-P and Resale lines in service that belong to a given CLEC on the date the<br />

report is generated.<br />

Qwest is investigating possible solutions to this change request and will provide an updated response at the September <strong>CMP</strong> meeting.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC070103-1<br />

Page 76 of 105<br />

Attachment D


Sincerely,<br />

Donna Lucio<br />

Sr. <strong>Process</strong> Analyst<br />

Qwest<br />

Cc: Sue Burson, Qwest<br />

Sue Kriebel, Qwest<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC070103-1<br />

Page 77 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC070103-3 DSL Volume provider and data migration<br />

process to prevent extended DSL outage<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Campbell, Bill<br />

Johnson, Bonnie<br />

Sanchez-Steinke, Linda<br />

Description Of Change<br />

Wholesale ProdProc Ordering,<br />

Provisioning<br />

line/loop splitting and<br />

sharing,<br />

UNE LOOP, UNE P<br />

Eschelon and Covad jointly submit this request. This request applies to all types of DSL (Qwest Retail, Qwest resold DSL, volume provider DSL,<br />

CLEC DSL, etc.). Any migration of voice, data or voice/data should be handled by Qwest with a single Local Service Request (“LSR”) with only<br />

minimal interruption to service.<br />

An end user customer should be able to obtain one due date for installation/functioning of both voice and data. Carriers should be able to place a<br />

single LSR to convert physical DSL service (regardless of the identity of the ISP) to any provider without undue service interruption. Regardless of<br />

the ISP (or of the sharing scenario, if any), customer switches that involve both voice and data should be performed with (1) one LSR, and (2) no<br />

extended service disruption. With this request, we seek, for example, to: (1) ensure that the use/presence of a DSL Volume provider does not<br />

adversely impact conversions/conversion intervals when switching providers. (If a conversion would not result in an extended outage or longer<br />

intervals if a non-volume DSL provider is involved, then the same conversion should not result in an extended outage or longer intervals if a volume<br />

DSL provider is involved); and (2) to convert (using a single LSR) a customer’s existing DSL service regardless of how service is provided<br />

[including various sharing scenarios (e.g., line sharing/splitting; loop sharing/splitting)] without extended service interruption to data or voice<br />

providers.<br />

#1<br />

There should be no exception to the process for volume providers. Currently, when a customer switches from Qwest Retail DSL and Qwest ISP<br />

service to a CLEC, Qwest processes allow a CLEC/DLEC, using one LSR, to (a) convert the DSL and change the ISP (for resale/UNE-P), or (b)<br />

perform a partial conversion (such as leaving the line and DSL with Qwest Retail for one line and converting the remaining lines in the account to<br />

CLEC) – both without disconnecting the DSL. In contrast, when the customer has DSL service from a volume provider, Qwest will disconnect the<br />

DSL in both of these scenarios. The disconnect is not momentary. It results in a DSL outage for the customer for the length of the entire interval<br />

required to add the DSL again (5 days or more). Such outages are harmful to competition, because customers are reluctant to switch carriers<br />

when faced with such an extended DSL outage. The presence or absence of a volume provider should not affect the result. In any case, such an<br />

extended DSL outage should not occur. CLECs should be able to request these conversions using one LSR.<br />

#2<br />

The current process that does not require DSL disconnects (see #1a and #1b) should be expanded to include the types of conversions that<br />

currently result in DSL disconnects/outages, cannot be ordered using one LSR, or both. When switching carriers, an end user customer should be<br />

able to obtain one due date for installation/functioning of both voice and data and should not experience extended DSL outages. This result should<br />

not depend on the product that the customer currently uses or to which it is switching. Currently, the result does vary by product. For example, if a<br />

customer is on line sharing (with Qwest Retail voice and Covad data) and wants to switch to a UNE-P line splitting product (with CLEC voice and<br />

Covad data), Qwest will disconnect the DSL. Again, the disconnect is not momentary and results in an extended DSL outage. Even though the<br />

data is staying with Covad in this example, Qwest requires disconnection of the line sharing product and re-establishment of the UNE-P line<br />

splitting product as a physical matter. In reality, however, this should just be a pure records change for data and should not affect the customer’s<br />

service. CLECs should be able to request these conversions using one LSR.<br />

Expected Deliverable:<br />

Qwest will develop, document and train a process(es) that meets the needs described in the above Description of Change. The process will<br />

expand the current one to avoid DSL disconnects/outages in situations that currently result in disconnects/outages; it will allow use of a single LSR<br />

for ordering these conversions; and it will not include any exception for volume providers. If different parts of this CR can be done earlier than<br />

others, please describe the options to CLECs. Also, if different methods would be used to provide these conversions (such as a coordinated hot<br />

cut type elective option), please describe. Eschelon and Covad bring these issues together in one CR so that portions of the request do not fall<br />

between the cracks.<br />

Text of e-mail message from Bonnie Johnson:<br />

Development<br />

11/19/03<br />

Originator Company Name:<br />

Eschelon<br />

Report Line Number<br />

<strong>Product</strong>s<br />

Impacted<br />

“Scenario #1<br />

Qwest Retail customer is converting to Eschelon (Resale or UNE-P) and hasQwest DSL with the DVDP FID. Eschelon sends conversion request<br />

and retains Qwest DSL but changes the ISP host (we do these today when the customer does not have volume provider arrangement).<br />

Scenario #2<br />

Qwest Retail customer is converting to Eschelon (Resale or UNE-P) and has Qwest DSL with the DVDP FID. Eschelon sends conversion request<br />

and requests the line with Qwest DSL with volume provider stay with Qwest and Eschelon converts all or a part of the remaining account (we do<br />

these today when the customer does not have volume provider arrangement).<br />

Scenario #3<br />

Qwest Retail customer is converting to Eschelon (Facility based) and has Qwest DSL with or without a volume provider. Eschelon converts the line<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

20<br />

PC070103-3<br />

Page 78 of 105<br />

Attachment D


with DSL to a DSL (XDSL-I) capable loop.”<br />

Status History<br />

07/01/03 - CR Received<br />

07/02/03 - CR Acknowledged<br />

07/16/03 - CR Discussed at <strong>CMP</strong> Monthly <strong>Meeting</strong><br />

08/04/03 - Sent e-mail question to Bonnie Johnson re: Scenario #2, rec'd e-mail response from Bonnie Johnson re: Scenario #2<br />

08/06/03 - Sent e-mail question to Bonnie Johnson re: Scenario #3<br />

08/08/03 - Rec'd e-mail response from Bonnie Johnson re: Scenario #3<br />

08/20/03 - Discussed at <strong>CMP</strong> <strong>Meeting</strong><br />

09/17/03 - September <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

09/30/03 - Held clarification meting with Bonnie Johnson re: Scenario #1<br />

10/15/03 - October <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

11/19/03 - November <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

01/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

01/26/04 - Qwest Issued PROS.01.26.04.F.01274.MigrationsV14 Level 1 effective 1/27/04<br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Project <strong>Meeting</strong>s<br />

02/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Anthony Washington with Qwest provided an update that we have received funding approval and are waiting for an implementation date. This CR<br />

will remain in Development status.<br />

____________________________<br />

01/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Russ Urevig with Qwest gave an update that the Migration/Conversion PCAT will contain a link for unbundled loop scenarios and will explain if a<br />

single or a combination of LSRs is required. The documentation will be available in the late January timeframe and will be located at the end of the<br />

ordering section in the Migration/Conversion PCAT. This CR will remain in Development status.<br />

____________________________<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Russ Urevig with Qwest said that there were questions submitting orders and the scenarios for migrations and conversions. Bonnie Johnson with<br />

Eschelon added they need to know how to submit the LSRs. Russ asked if the CR should be left open for this documentation change. Linda<br />

Sanchez-Steinke with Qwest said that the CR should remain open due to systems changes needed. This CR will remain in Development status.<br />

____________________________<br />

11/19/03 November <strong>CMP</strong> <strong>Meeting</strong><br />

Anthony Washington with Qwest gave an update on Scenario #1 and said that Qwest accepts this CR and the process changes will be initiated.<br />

Updates will be provided as the project moves forward. Jamal Boudhaouia with Qwest added that the CLECs should understand that the CLEC<br />

should provide the end user a modem and a profile should be ready and built in the new ISP to additionally minimize downtime. Bonnie Johnson<br />

with Eschelon said she did understand. Bonnie added that Qwest had announced PCAT changes associated with scenario #3 and needs to<br />

provide additional information on how to submit an LSR when ordering four voice retail lines to convert to an unbundled loop and one data line is<br />

converting to an unbundled loop with DSL service. Russ Urevig said that he is doing research and will determine if a PCAT update is needed.<br />

This CR will move to Development status.<br />

____________________________<br />

10/15/03 October <strong>CMP</strong> <strong>Meeting</strong><br />

Deb Smith with Qwest gave an update on Scenario #3 and #4. Updates have been made to PCATS for Line Sharing, Loop Splitting, Line Splitting,<br />

Unbundled Loops and Migrations and Procedures. The procedure identifies if 1 or more LSRs are needed and explains that downtime will not<br />

exceed 45 minutes. Kim Isaacs with Eschelon asked if the DSL notices were in the UNE loop PCAT. Deb Smith said the unbundled loop PCAT<br />

went out as a level 2 on 10/1/03. Kim said that she will review the changes and added that she didn’t know that the CR was associated with the<br />

PCAT.<br />

Anthony Washington with Qwest gave an update on Scenario #1. Qwest SME’s held a meeting with Bonnie Johnson to discuss looking at<br />

separate service orders to resolve the CR. Qwest is re-evaluating and will have an update at the November meeting. This CR will remain in<br />

Evaluation status.<br />

____________________________<br />

<strong>Meeting</strong> Minutes<br />

PC070103-3<br />

September 30, 2003<br />

1-877-572-8687, Conference ID 3393947#<br />

1:00 p.m. - 1:45 p.m. Mountain Time<br />

List of Attendees:<br />

Bonnie Johnson - Eschelon<br />

Janean Van Dusen - Qwest<br />

Cindy Schwartze - Qwest<br />

Anthony Washington - Qwest<br />

Michael Whitt - Qwest<br />

Linda Sanchez-Steinke - Qwest<br />

The meeting began with Qwest making introductions and welcoming all attendees. Linda Sanchez-Steinke with Qwest explained that the purpose<br />

of the meeting was to discuss CR PC070103-3 and Bonnie’s request at the September <strong>CMP</strong> meeting to review whether the process could be<br />

accomplished by Qwest initiating two service orders.<br />

Bonnie said at the September <strong>CMP</strong> meeting, Qwest denied this CR because it was economically unfeasible due to changes to systems that would<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC070103-3<br />

Page 79 of 105<br />

Attachment D


have to be done. Eschelon would like to convert customers with no downtime on DSL when a customer has a volume service provider. From a<br />

process perspective, issue an order to disconnect DSL volume service provider and ISP then consecutively issue an order to install Qwest DSL<br />

ISP of choice. This process would re-install the service order so the customer is not without DSL service.<br />

Cindy Schwartze asked if Eschelon wants Qwest to take the LSR and if it has VISP remove that and keep the same speed, change the host and<br />

there will no outage of DSL. Bonnie agreed.<br />

Bonnie said the response at September <strong>CMP</strong> didn’t make sense because systems would not need to be changed to accomplish, when it can be<br />

done by changing a process. An order could be issued with Qwest DSL staying or changing and another order, with one due date, the date of<br />

conversion, getting rid of the host and getting a new one. The request is not to have any downtime.<br />

Anthony Washington asked how much downtime, Bonnie said that we have discussed this and Linda said that 45 minutes downtime had been<br />

identified as acceptable in the change request.<br />

Janean Van Dusen said that we have legal and contractual obligations with the volume ISP.<br />

Bonnie said that when the LSR is sent in, Qwest allows the disconnect of the volume ISP. Bonnie suggested that if we look at this as a process<br />

solution, we could use 2 service orders to accomplish the same thing, the volume ISP would go away, and the customer would not have the 5 day<br />

lag time without DSL. It is not logical that system changes would be required to accomplish the change request.<br />

Cindy asked if this example would be accurate: Eschelon wants to issue 1 LSR to convert the account, remove the VISP, add or change what is<br />

existing for Qwest DSL with the same due date. Cindy further explained that today Eschelon issues 1 LSR to convert and remove the VISP and 1<br />

LSR to add Qwest DSL and host. Bonnie said that the second LSR can’t be submitted until the VISP order is completed.<br />

Michael Whitt asked if Eschelon would be willing to send more than 1 LSR. Bonnie said it is not Eschelon’s preference and it would leave more<br />

room for gaps and rejects in error. Bonnie asked if they would get IMA up front errors.<br />

Cindy asked if there was a question about different modems for the end user and new I-host. Anthony said he did not believe that has anything to<br />

do with Qwest.<br />

Cindy asked if the VCI/VPI would be an issue. Bonnie said that Qwest resale or Qwest retail change, VCI/VPI, on Qwest Q host on the same day.<br />

Cindy said the CLEC gets the VCI/VPI within 1 hour and Integrator does translations.<br />

Bonnie said that Eschelon is currently using this process with customers on Qwest retail DSL with Qwest ISP. Volume ISP is a contractual<br />

agreement. If it is not a Volume ISP and the costs are $1 M, what systems need to be changed and why does the process work currently when<br />

there is not a volume ISP.<br />

Cindy Schwartze said that the VISP isn’t a resale-able product. Originally we rejected LSR’s because it wasn’t a resale-able product. Cindy said<br />

that Qwest needs to get everyone together for an estimate of what it would take.<br />

Michael Whitt said that we can’t promise that the response will be different and said that we have been working on a way to provide the change<br />

requested. Bonnie said that the <strong>CMP</strong> process states that if the CR is denied that Qwest should provide details.<br />

Linda asked if there were any additional questions. No questions were asked and Linda said that we would discuss this CR at the October <strong>CMP</strong><br />

meeting.<br />

___________________________<br />

09/17/03 September <strong>CMP</strong> <strong>Meeting</strong><br />

Deb Smith with Qwest explained this CR was submitted jointly by Eschelon and Covad and was divided into Scenarios 1 through 4.<br />

Deb read the draft response for Scenario 3, a Qwest Retail customer is converting to Eschelon (Facility based) and has Qwest DSL with or without<br />

a volume provider. Eschelon converts the line with DSL to a DSL (xDSL-I) Capable Loop. Qwest and Eschelon agreed that downtime will not<br />

exceed 45 minutes on these type of requests and will update the Unbundled Loop PCAT with this information.<br />

Deb read the draft response for Scenario 4, Line Sharing, Line Splitting and Loop Splitting, has been addressed in a CR PC012703-2 and Qwest<br />

has updated the Migration and Conversion PCAT addressing the need for more than 1 LSR for each migration or conversion possible. The PCAT<br />

will be updated to reflect the 45 minute timeframe and will get the information to the documentation team by Friday. Notification of updated PCAT<br />

will be provided to the CLEC Community.<br />

Anthony Washington read the draft response for Scenario #1. Liz Balvin with MCI said that the <strong>CMP</strong> document says that if a CR is denied as<br />

economically not feasible, then Qwest should provide some details around the costs in excess of one million dollars. Bonnie Johnson with<br />

Eschelon stated she wants Qwest to go back to the drawing board and determine if this can be done by issuing separate service orders. Eschelon<br />

wants to have Qwest DSL that same day and not 5 days later. A separate call will be held to discuss alternate process solutions to implement this<br />

scenario.<br />

Anthony read the response for Scenario #2, Qwest is currently providing this capability. This CR will remain in Evaluation status.<br />

_______________________________<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

08-20-03<br />

Smith-Qwest presented the response; Qwest is still evaluating the request. The request was moved to Evaluation status.<br />

===========================================<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC070103-3<br />

Page 80 of 105<br />

Attachment D


Sent: Fri 8/8/03 5:48 AM<br />

From: Bonnie Johnson<br />

To: Linda Sanchez-Steinke<br />

RE: Question Scenario #3 PC070103-3<br />

Hi Linda,<br />

The customer in this scenario would be converting both voice and data to the<br />

CLEC. No services would be left with Qwest.<br />

Let me know if this helps!<br />

Have a good day!<br />

Bonnie Johnson<br />

Sr. Manager ILEC Relations<br />

Eschelon Telecom, Inc.<br />

Phone 612 436-6218<br />

Fax 612 436-6318<br />

Cell 612 743-6724<br />

__________________________________<br />

Sent: Wed 8/6/03 1:31 PM<br />

To: Bonnie Johnson<br />

From: Linda Sanchez-Steinke<br />

Subject: Question Scenario #3 PC070103-3<br />

Bonnie -<br />

Below is a question from Deb Smith, on CR PC070103-3. Would you respond back to<br />

me and I'll e-mail on to Deb.<br />

Thank you<br />

Linda Sanchez-Steinke<br />

CRPM<br />

Qwest<br />

303-965-0972<br />

Scenario #3<br />

Qwest Retail customer is converting to Eschelon (Facility based) and has Qwest DSL with or without a volume provider. Eschelon converts the line<br />

with DSL to a DSL (XDSL-I) capable loop.<br />

Bonnie,<br />

We need a bit more clarification on scenario #3. Our understanding of scenario #3 is that a Qwest Retail customer is converting both voice and<br />

data to Eschelon. Is that correct? If so, this would be a conversion to an Unbundled Loop xDSL-I reusing existing facilities (if facilities qualify).<br />

If the voice portion is remaining with Qwest, this is not a conversion and would require a new Unbundled Loop to the premise.<br />

Any additional clarification would be greatly appreciated.<br />

Thank you,<br />

Deb Smith<br />

___________________________________<br />

Mon 8/4/03 11:48 A<br />

From: Bonnie Johnson<br />

To: Linda Sanchez-Steinke<br />

RE: PC070103-3 Scenario #2<br />

Linda,<br />

I clarified all of this on the clarification call, however, if Qwest needs<br />

further information then we need a call. Yes Qwest currently offers partial<br />

conversions but the DSL is disconnected at the time of conversion when they<br />

have a volume provider.<br />

Bonnie Johnson<br />

Sr. Manager ILEC Relations<br />

Eschelon Telecom, Inc.<br />

Phone 612 436-6218<br />

Fax 612 436-6318<br />

Cell 612 743-6724<br />

__________________________________<br />

From: Linda Sanchez-Steinke<br />

To: Bonnie Johnson<br />

Sent 8/4/03 8:36<br />

Bonnie -<br />

I am backfilling for Matt White and Anthony Washington had a question about PC070103-3, scenario #2.<br />

The following is Anthony's question:<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC070103-3<br />

Page 81 of 105<br />

Attachment D


Scenario #2 appears to be a partial conversion, which Qwest already makes available to CLECs. Therefore, explain how the<br />

scenario differs from a partial conversion, and or, revise the scenario in a manner that differs from scenario #1 and #3.<br />

Bonnie, I've attached the scenarios and would you e-mail me back, if needed we can get Anthony on a conference call.<br />

Thank you<br />

Linda Sanchez-Steinke<br />

CRPM<br />

Qwest<br />

303-965-0972<br />

___________________________________<br />

Clarification <strong>Meeting</strong> - 07-21-03<br />

Attendees<br />

Matt White<br />

Deb Smith<br />

Crystal Soderlund<br />

Cindy Schwartze<br />

Janean Van Dusen<br />

Karen McClemic<br />

Bonnie Johnson<br />

John Berard<br />

(NOTE: Prior to this meeting, Johnson-Eschelon forwarded three scenarios that involved the change requested in this CR. The text of this e-mail<br />

is included at the end of these minutes.)<br />

White-Qwest described the purpose of the meeting and asked the Qwest attendees if they could articulate their questions to Bonnie.<br />

Smith-Qwest thanked Johnson for the scenarios she provided by e-mail. She stated that there is mention in the CR of line splitting and line<br />

sharing. Johnson-Eschelon stated that Berard should send Qwest examples of these scenarios. Berard-Covad stated that he would send those<br />

examples. He stated that what he wanted to address is the down time that is involved with a conversion. Smith-Qwest asked if Covad was<br />

seeking to issue only one LSR. Berard-Covad stated that he was interested in only one LSR and the issue of the 5 days of down time.<br />

Johnson-Eschelon stated that whatever process Qwest develops, even if it involves that CLECs need to send a separate LSR that piggybacks on<br />

the first one one, the due dates should match. Soderlund-Qwest asked what product Johnson was referring to. Johnson-Eschelon stated that she<br />

was interested in Resale, UNP-P, UNE loop, line sharing and line splitting. Soderlund-Qwest asked what the conversion would be from. Johnson-<br />

Eschelon stated that this was a very large CR that may have to be done in pieces. She emphasized that she wanted to ensure that no piece<br />

slipped through the cracks.<br />

Schwartze-Qwest stated that she had reviewed the scenarios Johnson had send and that she wanted to better understand scenario 1. She<br />

explained that the CR included information about converting to resale or UNE. She asked if Johnson understood, that with 13.0, Qwest would<br />

remove the DVDP FID and then the CLECs would need to submit another LSR. She stated that he understanding was the Eschelon did not want<br />

to submit the additional LSR or be subjected to the 5-day due date. Johnson-Eschelon stated that all the work happens on the due date.<br />

Schwartze-Qwest asked if Eschelon wanted to be able to provide the new I-host to Qwest rather than disconnecting the DSL and having to order<br />

the feature on the line.<br />

Van Dusen-Qwest asked what the difference was between scenarios 1 and 2. Johnson-Eschelon stated that scenario 2 is where the customer<br />

wants to keep DSL with MSN and Eschelon wants to opportunity to leave it behind. She stated that was doing a partial conversion where Eschelon<br />

leaves the line and DSL as they are. She explained that she was asking for a partial conversion but that she wanted the line and DSL to stay as a<br />

Qwest retail account. She stated that this would occur if a customer has 5 lines wherein one is 1FB with Qwest DSL with MSN and Eschelon<br />

wants to convert the other 4 lines. Smith-Qwest asked of the 3rd scenario referred only to unbundled capable XDSL-I. She confirmed that<br />

Eschelon wanted Qwest only to be validating that the line was DSL capable, not validating the dial tone. Johnson-Eschelon stated that Eschelon<br />

wants to reuse the facilities and turn it into a DSL capable loop.<br />

Berard–Covad stated that he could prioritize the scenarios that have already been identified. He stated that Covad could not live with a 5-day<br />

disconnect. He explained that Covad wanted voice and DSL to have same due date. Soderlund-Qwest asked Berard and Johnson could provide<br />

Qwest with a prioritized list of all the examples that fell under this change. Johnson-Eschelon stated that she had provided her examples and that<br />

numbers 1 and 2 were her top priority. She explained that every example left the customer without service. She stated that she did not want<br />

Qwest to work these examples in series. She stated that she expected to work on these examples in parallel. Soderlund-Qwest stated that she<br />

wanted to ensure that Eschelon and Covad were on the same page when it came to the examples. She explained that Qwest needed to be sure<br />

that Eschelon’s and Covad’s priorities are the same. Berard-Covad stated that he would take Johnson’s examples and add any additional ones<br />

that he felt were appropriate. Johnson-Eschelon stated that Eschelon and Covad were jointly submitting the CR and that the big scope of the CR<br />

is that we don’t want our customers to be without DSL service. She stated that the intent of the CR is to have Qwest develop a process to avoid a<br />

situation where customers are making decisions to change to Eschelon or Covad and then changing their minds because they will be without<br />

service for 5 days. She explained that she want processes to stop this impact on the customers and that she did not want to have to prioritize her<br />

examples. She stated that Eschelon wanted them all to have top priority. She explained that she understood that each product might have a<br />

different timeframe depending on the scope of the change, but that she did not want to send a prioritized list because the CR is asking for Qwest to<br />

develop processes. Soderlund-Qwest thanked he for her input.<br />

White-Qwest asked if there were any additional examples needed. Smith-Qwest asked if Covad was going to provide more examples. Berard-<br />

Covad stated that he would go through existing documentation and send any additional examples to White-Qwest. Berard-Covad asked if there<br />

were any instances when the DSL does not go down. Schwartze-Qwest stated that with the DVDP arrangement, DSL goes down on all sides. She<br />

stated that she was concerned about line sharing/splitting and loop sharing and asked if Berard could send outage examples for these products.<br />

Berard-Covad stated that the big examples for Covad are line sharing and line spliting. Johnson-Eschelon stated that she understand that there<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC070103-3<br />

Page 82 of 105<br />

Attachment D


would be some outage time on the dure date because work must occur. Smith-Qwest stated that Berard had said that 45 minutes would be an<br />

acceptable amount of down time. Berard-Covad stated that he was fine with that. He understood that Qwest needed time to move and test the<br />

cross connects.<br />

Johnson-Eschelon stated that she agreed. She also stated that her biggest challenge is getting the DVPIVCI info off Q-host. Schwartze-Qwest<br />

stated that she had been told that the integrator refreshes every hour. Johnson-Eschelon stated that her problem was with it getting translated.<br />

White-Qwest confirmed that there were no more questions. Johnson-Eschelon asked that if Qwest had any questions that they contact her for an<br />

impromptu meeting or call.<br />

Text of e-mail message from Bonnie Johnson:<br />

Scenario #1<br />

Qwest Retail customer is converting to Eschelon (Resale or UNE-P) and hasQwest DSL with the DVDP FID. Eschelon sends conversion request<br />

and retains Qwest DSL but changes the ISP host (we do these today when the customer does not have volume provider arrangement).<br />

Scenario #2<br />

Qwest Retail customer is converting to Eschelon (Resale or UNE-P) and has Qwest DSL with the DVDP FID. Eschelon sends conversion request<br />

and requests the line with Qwest DSL with volume provider stay with Qwest and Eschelon converts all or a part of the remaining account (we do<br />

these today when the customer does not have volume provider arrangement).<br />

Scenario #3<br />

Qwest Retail customer is converting to Eschelon (Facility based) and has Qwest DSL with or without a volume provider. Eschelon converts the line<br />

with DSL to a DSL (XDSL-I) capable loop.<br />

______________________________________<br />

07-17-03 Clarification <strong>Meeting</strong><br />

Attendees<br />

Matt White - Qwest<br />

Deb Smith – Qwest<br />

Heidi Moreland - Qwest<br />

Crystal Soderlund - Qwest<br />

Monica Manning - Qwest<br />

Karen McClimek - Qwest<br />

Janean Van Dusen - Qwest<br />

Cindy Schwartze - Qwest<br />

Terry Kilker - Qwest<br />

Anthony Washington - Qwest<br />

John Berard - Covad<br />

White-Qwest welcomed the attendees and explained the purpose of the call. He asked Berard-Covad to review the change. Berard-Covad<br />

reviewed the change. On any data migration CLECs should submit a single LSR for both voice and data. Similarly, the migration should get one<br />

due date for voice and data and there should be no more than 30-45 minutes of down time instead of five days. Soderlund-Qwest asked if Berard<br />

was talking about all of the shared products for this CR. Berard-Covad stated that he was. Smith-Qwest what UNE-P products the CR was<br />

referring to. Berard-Covad stated that the CR sought that the existing UNE P migration process now be linked to the data product. He stated that<br />

it encompasses many different scenarios and that Covad was looking for no down time for customers who ask for no down time. There was<br />

further discussion of different scenarios that this CR may apply to. Various Qwest SME’s asked that Berard and Johnson create a list of all<br />

possible scenarios that this CR would apply to so they could more appropriately respond to the request. Berard-Covad stated that he would like to<br />

have another clarification call with Johnson-Eschelon on the line. He stated that Covad and Eschelon would produce a list of all possible<br />

scenarios. White-Qwest stated that he would schedule another clarification call. He thanked the attendees and adjourned the meeting.<br />

============================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

07-16-03<br />

White-Qwest stated that this CR will have the clarification meeting on 7/17. Johnson-Eschelon presented the CR. CR to Presented status.<br />

Qwest Response<br />

November 11, 2003<br />

For Review by the CLEC Community and Discussion at the November 19, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Bonnie Johnson<br />

Director<br />

Eschelon Telecom Inc.<br />

720 2nd Avenue South, Suite 1200<br />

Minneapolis, MN 55402<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC070103-3<br />

Page 83 of 105<br />

Attachment D


SUBJECT:Qwest’s Change Request Revised Response PC070103-3<br />

DSL Volume provider and data migration process to prevent extended DSL outage<br />

This letter is in response to CLEC Change Request PC070103-3, scenario number one, re-evaluation. This CR is a request by Eschelon for Qwest<br />

to reduce its current provisioning interval for VISP conversions from the standard 5 days to a much more reasonable timeframe.<br />

Qwest will accept this request. The following provides details surrounding this decision.<br />

Qwest will allow CLECs to submit one LSR to convert VISP end users. The conversion process involves changing the host through a C & T action<br />

on the service order; therefore, Qwest will remove the VISP arrangement while not taking down the DSL service. This will alleviate the need for<br />

CLECs to submit two LSRs, one to remove the VISP and another to add the DSL service five days later.<br />

The conversion process will maintain the DSL service but the host change will require the standard five day interval.<br />

The new conversion process will impact several systems. After an analysis of the impact, Qwest has determined that more then 350 hours is<br />

required to complete systems changes, and develop and document the new process. Therefore, Qwest will schedule and complete the system<br />

changes, and develop the new process as soon as possible, and will provide updates as they become available.<br />

Sincerely,<br />

Anthony Washington<br />

<strong>Product</strong> Management<br />

Qwest<br />

-----------------------------------------------------<br />

September 30, 2003<br />

REVISED DRAFT RESPONSE<br />

For Review by CLEC Community and Discussion at the October 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Bonnie Johnson<br />

Eschelon<br />

John Berard<br />

Covad<br />

SUBJECT: Qwest’s Change Request Response - PC070103-3<br />

Scenario #1<br />

"Qwest Retail customer is converting to Eschelon (Resale or UNE-P) and has Qwest DSL with the DVDP FID. Eschelon sends conversion request<br />

and retains Qwest DSL but changes the ISP host."<br />

During the September 17th <strong>CMP</strong> meeting Qwest denied Scenario #1 of CR PC070103-3 based on it being economically unfeasible. At that time,<br />

we were asked if it would be possible to accept the CR if Qwest Wholesale changed the process to allow one LSR and two services orders.<br />

Currently we are re-evaluating this process change and identifying all the of the necessary process and systems changes that would be impacted.<br />

Therefore, we require more time to verify if it is possible to provide a minimal outage situation when a CLEC wishes to change the ISP host.<br />

Sincerely,<br />

Anthony Washington<br />

<strong>Product</strong> Manager<br />

__________________________________<br />

September 9, 2003<br />

REVISED RESPONSE<br />

For Review by CLEC Community and Discussion<br />

at the September 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Bonnie Johnson<br />

Eschelon<br />

Mike Zulevic<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC070103-3<br />

Page 84 of 105<br />

Attachment D


Covad<br />

SUBJECT: Qwest’s Change Request Response - PC070103-3<br />

This letter is in response to CLEC CR PC070103-3. This CR is a joint request from Covad and Eschelon to request that migrations (voice, data or<br />

voice/data) are obtained with a single LSR and minimal interruption of service. Clarification calls were held on July 17 and 21 to further identify the<br />

migration scenarios. Eschelon provided Qwest four scenarios. In this response, Qwest will provide responses to each of the scenarios separately.<br />

Scenario #1<br />

"Qwest Retail customer is converting to Eschelon (Resale or UNE-P) and has Qwest DSL with the DVDP FID. Eschelon sends conversion request<br />

and retains Qwest DSL but changes the ISP host."<br />

Qwest response:<br />

The proposed change to the existing retail DSL product and processes would require resource allocation and expenditures associated with legacy<br />

systems and software specifications in excess of one million dollars. Information Technology redesigns would include systems changes to the<br />

electronic business to business system for each VISP provider, which would require considerable funding and a redirection of scarce technology<br />

resources. This would also include, to a significant extent, additional expense for producing and implementing changes to system performance<br />

and functionality of the Qwest VISP Graphical User Interface (GUI) and XML Interface, as well as require manual interaction to allow for<br />

communications with respect to Qwest retail customer changes and current status. Additional changes likely include significant modifications to<br />

existing ordering and processing systems and functionality, which would be a considerable burden at a great expense to Qwest.<br />

Qwest respectfully denies Scenario #1 of this CR based on economic unfeasibility.<br />

Scenario #2<br />

"Qwest Retail customer is converting to Eschelon (Resale or UNE-P) and has Qwest DSL with the DVDP FID. Eschelon sends conversion<br />

requests and requests the line with Qwest DSL with volume provider stay with Qwest and Eschelon converts all or a part of the remaining account."<br />

Qwest response:<br />

Qwest allows partial conversions of existing Qwest retail end user accounts to UNE-P or Resale services. In the instance where an existing retail<br />

end user account has more than one (1) line and one (1) or more of those lines has Qwest DSL Host Volume Discount Program arrangements<br />

(indicated by the presence of a DSL USOC followed by a ‘DVDP’ FID), CLEC may convert the entire account or specify certain lines for<br />

conversion.<br />

If CLEC chooses to convert lines with DSL Host Volume Discount Program arrangements, as noted in the UNE-P with Qwest DSL PCAT, the<br />

(http://www.qwest.com/wholesale/pcat/unepqdsl.html) and similarly in the Resale DSL PCAT<br />

(http://www.qwest.com/wholesale/pcat/resaledsl.html), "Qwest will remove the DSL USOC and the DVDP FID from the account. This activity will<br />

remove end-user DSL functionality".<br />

If CLEC chooses to convert only lines without DSL Host Volume Discount Program arrangements, the remaining retail lines with the DSL Host<br />

Volume Discount Program arrangements will remain in service.<br />

Because Qwest currently offers this capability, Qwest accepts this Scenario of the CR.<br />

Scenario #3<br />

"Qwest Retail customer is converting to Eschelon (Facility based) and has Qwest DSL with or without a volume provider. Eschelon converts the<br />

line with DSL to a DSL (xDSL-I) Capable Loop."<br />

Qwest response:<br />

Unbundled Loop<br />

Scenario #3 is a conversion of Qwest Retail customer’s service to the CLEC requested xDSL-I Unbundled Loop. The CLEC would submit 1 LSR<br />

to convert the Qwest Retail customer to the requested xDSL-I Unbundled Loop service with or without number portability. A disconnect will be<br />

performed on the end customer’s Qwest Retail service at the time of the migration activities.<br />

During the PC070103-3 clarification meeting held on July 21, 2003, Covad, Eschelon and Qwest agreed that their request required that the<br />

activities of the migration not exceed 45 minutes. The migration activities would include the termination at the ICDF and any associated tests. For<br />

the Unbundled Loop services the migration work activities won’t exceed the 45-minute time frame.<br />

Qwest accepts Scenario #3 of this CR. Qwest will update the Unbundled Loop General PCAT to reflect the migration activities will not exceed 45<br />

minutes.<br />

Scenario #4<br />

Line Sharing, Line Splitting and Loop Splitting<br />

Qwest response:<br />

In accordance with the Qwest response to PC012703-2, Data Migrations, the Migrations and Conversions Procedural PCAT<br />

(http://www.qwest.com/wholesale/clecs/migrateconvert.html) has been updated (in accordance with <strong>CMP</strong> timelines) with CLEC input on<br />

identification of the Data Migration scenarios for Line Sharing, Line Splitting and Loop Splitting. In that documentation, Qwest identifies, by<br />

scenario, whether a specific migration would require 1 LSR or multiple LSR’s. If the migration request currently requires more that 1 LSR, Qwest<br />

has provided the IMA (15.0) release that effects the change to 1 LSR.<br />

During the PC070103-3 clarification meeting held on July 21, 2003, Covad, Eschelon and Qwest agreed that the activities of the migration will not<br />

exceed 45 minutes. The migration activities would include the ‘lift and lay’ of the cross connects and any associated tests. For the Line Sharing,<br />

Line Splitting, and Loop Splitting services the migration work activities won’t exceed the 45-minute time frame.<br />

Qwest accepts Scenario #4 of this CR. We have responded, identified and documented the Line Sharing, Line Splitting and Loop scenarios as a<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC070103-3<br />

Page 85 of 105<br />

Attachment D


esult of PC012703-2, Data Migrations. Qwest will update the Data Migration scenarios for Line Sharing, Line Splitting and Loop Splitting<br />

(downloadable links) to reflect the 1 LSR vs. multiple and the IMA (15.0) release that effects the change to 1 LSR. Qwest will update the Line<br />

Sharing, Line Splitting, and Loop Splitting PCATs to reflect the migration activities will not exceed 45 minutes.<br />

Sincerely,<br />

Deb Smith<br />

<strong>Product</strong> Manager<br />

Anthony Washington<br />

<strong>Product</strong> Manager<br />

_______________________<br />

August 12, 2003<br />

DRAFT RESPONSE<br />

For Review by CLEC Community and Discussion at the August 20, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Bonnie Johnson<br />

Eschelon<br />

Mike Zulevic<br />

Covad<br />

SUBJECT: Qwest’s Change Request Response - PC070103-3<br />

This is a preliminary response regarding the Eschelon/Covad CR PC070103-3. This CR requests a DSL Volume provider and data migration<br />

process to prevent extended DSL outage.<br />

Qwest is currently evaluating this request. Because this request involves the creation of a complex and wide-reaching process, there are a large<br />

number of issues Qwest must analyze. Qwest proposes moving this Change Request into Evaluation Status and while we continue to investigate<br />

and provide an updated response.<br />

Qwest will provide a status update at the September <strong>CMP</strong> meeting.<br />

Sincerely,<br />

Deb Smith<br />

<strong>Product</strong> Manager<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC070103-3<br />

Page 86 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC081403-1 Jeopardy Notification <strong>Process</strong> Changes (new<br />

title). Delayed order process modifed to<br />

allow theCLEC a designated time frame to<br />

respond to a released delayed order after<br />

Qwest sends an updated FOC (old title).<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Provisioning Private Line, Resale,<br />

Unbundled Loop,<br />

EEL (UNE-C), UNE-P<br />

Changed the description of this CR as a result of synergies with PC072303-1. During the October 15 <strong>CMP</strong> meeting we discussed whether we<br />

should close/leave open/ or update CR PC081403-1 'Delayed order process modified to allow the CLEC a designated time frame to respond to a<br />

released delayed order'. The reason we wanted to close/leave open or update PC081403-1 is because PC072303-1 is meeting many of the<br />

needs. Bonnie Johnson agreed to change this CR, as long as we retained the original CR description.<br />

********************************************************************************<br />

Change Jeopardy Notices sent on DVA and PTD for Designed Services<br />

After analysis of Due Dates that are being missed when jeopard<br />

notices are sent prior to the Due Date, Qwest is proposing that only<br />

specific jeopardy conditions be sent to the CLEC on the critical date of DVA<br />

and PTD. On DVA, Qwest would prefer to only send jeopardy notices for<br />

facility and plug-in issues. The jeopardy codes would be those that start<br />

with a "K" (facility reasons) or on a jeopardy code of V25 (PICS/BRI<br />

plug-ins required.) For the critical date of PTD, Qwest would continue to<br />

send all jeopardy notices except those that end in "33" (work force issues)<br />

i.e., B33, E33, P33. The reason for eliminating the "33" jeopardy code is<br />

due to the fact that Qwest is not missing Due Dates for this reason and is<br />

causing unnecessary jeopardy notices being sent to the CLEC. Along with these proposed changes, Qwest would also like to hear suggestions<br />

from the CLEC community any changes they feel would benefit the overall jeopardy notification process. Changes being implemented with<br />

PC072303-01, Expanding the Jeopardy Notifications to 6 p.m. Mountain Time are also helping the overall jeopardy process.<br />

Expected Deliverable:<br />

Change the jeopardy notification process to reduce unnecessar<br />

jeopardy notices being sent to the CLEC when the Due Date is not in jeopardy<br />

and to improve the overall jeopardy notification process.<br />

***********************************************************************************<br />

Qwest will contact the CLEC to test and accept only after the updated FOC has been sent and a designated time frame has passed. Qwest will not<br />

put the order in a CNR (customer not ready) jeopardy status until this time frame has passed and the CLEC is not ready.<br />

When Qwest puts a CLECs request in delayed for facilities jeopardy status, Qwest should be required to send the CLEC an updated FOC when<br />

the delayed order is released and allow the CLEC a reasonable time frame to prepare to accept the circuit. Qwest releases orders form a held<br />

status (in some cases the CLEC has not even received an updated FOC) and immediately contacts the CLEC to accept the circuit. Because<br />

Qwest does not allow the CLEC a reasonable amount of time to prepare for the release of the delayed order, the CLEC may not be ready when<br />

Qwest calls to test with the CLEC. Qwest then places the request in a CNR jeopardy status. Qwest should modify the Delayed order process, to<br />

require Qwest to send an updated FOC and then allow a reasonable amount of time for the CLEC to react and prepare to accept the circuit before<br />

contacting the CLEC for testing.<br />

Expected Deliverable:<br />

Qwest will modify, document and train a process, that requires Qwest to send an updated FOC and allow a CLEC a reasonable amount of time<br />

(from the time the updated FOC is sent) to prepare for testing before Qwest contacts the CLEC to test and accept the circuit. Qwest should cease<br />

applying a jeopardy status of CNR to delayed orders that are released and the CLEC has not been provided a reasonable amount of time to<br />

prepare to test/accept the circuit.<br />

This should apply to all orders where the delayed order process is followed and testing is required.<br />

Status History<br />

Schultz, Judy<br />

Johnson, Bonnie<br />

Sunins, Phyllis<br />

Macy, Cindy<br />

Development<br />

10/15/03<br />

Originator Company Name:<br />

Eschelon<br />

08/14/03 - CR Submitted<br />

08/15/03 - CR Acknowledged<br />

8/19/03 - LWTC for Bonnie regarding Clarification <strong>Meeting</strong><br />

8/26/03 - Held Clarification Call<br />

9/17/03 - Sep <strong>CMP</strong> meeting minutes will be posted to the database<br />

Information Current as of: Friday, <strong>March</strong> 12, <strong>2004</strong><br />

Report Name: 004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

21<br />

<strong>Product</strong>s<br />

Impacted<br />

PC081403-1<br />

Page 87 of 105<br />

Attachment D


10/6/03 - Held CLEC Ad Hoc call to discuss synergys between this CR and PC072303-1<br />

10/8/03 - Sent response to CLEC<br />

10/10/03 - Sent email to Bonnie to request change of statusto withdraw due to syncergy's with other CR PC072303-1<br />

10/13/03 - Bonnie advised she would like to keep open and reference PC072303-1 and Jill's new CR when it is issued<br />

10/15/03 - Oct <strong>CMP</strong> meeting minutes will be posted to the project meeting section<br />

10/30/03 - Changed the description of this CR as a result of synergies with PC072303-1. During the October 15 <strong>CMP</strong> meeting we discussed<br />

whether we should close/leave open/ or update CR PC081403-1 'Delayed order process modified to allow the CLEC a designated time frame to<br />

respond to a released delayed order'. The reason we wanted to close/leave open or update PC081403-1 is because PC072303-1 is meeting many<br />

of the needs. Bonnie Johnson agreed to change this CR, as long as we retained the original CR description.<br />

11/19/03 - Nov <strong>CMP</strong> meeting minutes will be posted to the database<br />

12/1/03 - Scheduled CLEC ad hoc meeting for 12/8/03 to review jep codes/content<br />

12/5/03 - <strong>CMP</strong>R.12.05.03.F.01144.Jeopardy<strong>Process</strong>Handout<br />

12/8/03 - Held ad hoc meeting to review jep codes / content<br />

12/17/03 - Dec <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the database<br />

1/21/03 - Jan <strong>CMP</strong> meeting minutes will be posted to the database<br />

2/18/04 -Feb <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the project meeting section<br />

Project <strong>Meeting</strong>s<br />

February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Phyllis Sunins – Qwest advised that she is working with Kim Isaacs – Eschelon and analyzing some examples that were sent in. Qwest did find a<br />

few process compliance examples that are being addressed. Cindy Macy – Qwest will provide a document to address Eschelon’s examples and<br />

this will be reviewed during the ad hoc meeting the first week in <strong>March</strong>. This CR will remain in Development Status.<br />

_____________________________________________________________________________<br />

Ad Hoc Call<br />

January 23, <strong>2004</strong><br />

PC081403-1 Jeopardy <strong>Process</strong><br />

In attendance:<br />

Liz Balvin – MCI Karen Severson – Telephone Associates<br />

Kim Isaacs – Eschelon Phyllis Sunins – Qwest<br />

Jill Martain – Qwest Stephanie Prull – Eschelon<br />

Trudy Hughs – Idea One Shirley Richard – Idea One<br />

Rosie Glastell – Idea One Bonnie Johnson – Eschelon<br />

Colleen Sponseller – MCI Mary Hunt – MCI<br />

Carla Pardee – ATT Linda Sanchez-Steinke – Qwest<br />

Cindy Macy – Qwest Nancy Sanders – Comcast<br />

Cindy Macy – Qwest opened the call and reviewed the agenda. Cindy advised that we will discuss providing more detail on Jep Notices, review<br />

the improvements as a result of the CNR 6pm Jep CR, and discuss examples that were sent in regarding subsequent FOC not sent.<br />

Jill Martain reviewed the agenda and advised that Phyllis Sunins will provide additional details regarding the work that has been completed. Phyllis<br />

will share where we have been, where we are and where we want to go with this CR.<br />

Phyllis began the discussion and asked the CLECs how the jeopardy notification process change to 6pm is going? Kim Isaacs – Eschelon advised<br />

she had gathered a couple weeks worth of data. It does appear there has been an effect. The impact is not as great as she thought it would be,<br />

but they will continue to monitor the change. Kim explained she noticed an interesting situation and Eschelon saw that quite a few sups of due<br />

date, then FOC on due date and then Jep on sup. Kim will send examples to Phyllis to investigate.<br />

Rosemary – Idea One asked why is Qwest holding the jep until 6 PM. Phyllis explained a CR was issued to implement a new process. Effective<br />

with the new process a jeopardy notification is not sent when a jeopardy condition is cleared the same day by 6 PM. Kim Isaacs – Eschelon<br />

advised this process is only on mechanized jeps, not manual jeps.<br />

Phyllis said the next topic to discuss is the request for additional wording on jeps. Phyllis explained that we can provide more detail on subsequent<br />

jeps. The first jep that goes out is considered a preliminary jep, with a preliminary view of the issue. Qwest does not know additional details until<br />

the engineer does investigation and finds out more. Our target is that within 72 hrs Qwest would either send an FOC or another jeopardy<br />

notification with additional detail. Bonnie Johnson – Eschelon advised the mechanical jeps are not detailed enough.<br />

Phyllis advised another idea that may be possible is to use HEET, which is used on the ASR side. This is a web tool to check status on delayed<br />

orders. It may be possible to implement for LSRs. Rosemary – Idea One asked what is RTT. Phyllis advised RTT is a Referral Tracking Tool that<br />

tracks facility shortages. RTT is Engineering’s database for resolving facility situations referred to them. Bonnie advised she would like to review<br />

other alternatives if HEET is not a viable solution.<br />

Today Qwest sends jeopardy notifications for both Critical Date Jeopardies and Due Date Jeopardies. Phyllis discussed the idea of sending<br />

jeopardy notifications that would impact the Due Date only. Qwest would discontinue sending jeopardy notifications for jeopardies on Critical Dates<br />

that are cleared the same day or the next day and the Due Date is still met. As an example; Qwest sends jeopardy notifications for PICs – V25<br />

(plug in network cards) problems. This jeopardy situation is resolved so that the Due Date is met. Another example is Jeopardy Notifications for<br />

Work Force Issues (33’s). Qwest works with our Work Forces to readjust their loads so that the Due Date is met. Bonnie Johnson – Eschelon<br />

agreed they do not want to see jeps for ‘interim date’ issues. If the end due date is impacted, then they need to know. Idea One and MCI<br />

supported Bonnie’s comment. Phyllis confirmed that the due date jep would still happen, (Qwest could discontinue the Critical Date jeopardies<br />

which are cleared by Due Date) . If the Due Date will be missed, it is part of Qwest’s Network <strong>Process</strong>es to call the CLEC on the Due Date. In<br />

addition, the CLECs will receive their jeopardy notification after 6 PM. MCI verified when the jep is sent it comes as an 865 EDI transaction, and<br />

the FOC is an 855 EDI transaction.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC081403-1<br />

Page 88 of 105<br />

Attachment D


Bonnie advised they do want more detail on what the jep’d problem is. They need to know if it is a F1 pair, or the street needs to be dug up. She<br />

would like more detail on one jep in particular: ‘Local Facility not available’. Bonnie asked when does this jep occur. What situation causes this<br />

jep to be assigned?<br />

Phyllis discussed the two examples that Eschelon sent in.<br />

1) One was a jeopardy notification sent for a PICs issue, no FOC was sent & then CNR. – This was an example of a Critical Date Jeopardy that<br />

would be addressed by the proposal of not sending Critical Date Jeopardy Notifications as the situation is cleared so that the Due Date can be<br />

met, thus the CLEC would expect Qwest to deliver on the Due Date.<br />

2) The other example is a Network compliance issue, which Phyllis is working with Network to correct.<br />

Bonnie thanked Phyllis for reviewing the examples. Bonnie advised that if they receive a CNR jep, and the CLEC has not received the FOC, they<br />

would escalate the situation. Bonnie advised they want the order worked without having to sup the order and they would like the jep lifted. Bonnie<br />

advised she would like to develop a process of how we will handle this situation when we get a CNR and didn’t get the FOC.<br />

Phyllis summarized our next steps:<br />

Kim Isaacs will send examples to Phyllis of orders sup’d on due date<br />

CLECs will continue to monitor 6pm jeps<br />

Jill / Phyllis will review wording of jeps to add more detail<br />

Bonnie brought up a concern on the time required for getting funding to implement the “Due Date only” Jeopardy notifications (from a mechanical<br />

perspective). She proposed having Qwest furnish a list of “Critical Date” jeopardy notifications which could be “disregarded on an interim basis.<br />

Phyllis will research this request. This information will be worked via the <strong>CMP</strong> process and additional meetings.<br />

________________________________________________________________________<br />

January 21, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Jill Martain – Qwest advised that we met with the CLECs last month and agreed to monitor the JEP process and then meet again in January to<br />

review additional information that can be put on the Jeopardy notice. We have a meeting scheduled for January 23 to discuss this further. Bonnie<br />

sent in two examples where they did not get a subsequent FOC and the order was jep’d for CNR. Bonnie advised that Qwest needs to find a way<br />

to get the FOC to the CLEC. The impact to our business is that we are forced to supp the order and take a new due date. Qwest no longer takes<br />

the hit on the held order in this situation too. Bonnie advised that Qwest needs to aggressively tackle this issue as it impacts our business, end<br />

users and held orders. It is high profile and critical and it needs to be fixed. Jill Martain – Qwest advised we have the examples and we are<br />

prepared to talk in more detail at the Friday meeting. This CR will remain in Development Status.<br />

_______________________________________________________________________-<br />

December 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Jill Martain – Qwest advised we had an ad hoc meeting to review the updated Jeopardy matrix. Jill is working with the centers to provide additional<br />

information on the Jeopardy notices. The team agreed to monitor the impact of the change to 6pm jep notices and meet again next month to<br />

review any additional changes needed and to review enhanced jeopardy description information. Bonnie Johnson – Eschelon advised she will<br />

monitor internally the impact to the change in jeopardy time frames and provide feedback at our next meeting. (Included comment from Bonnie<br />

Johnson in the following sentence). Bonnie said this CR is not related to CR to change the jeopardy to 6pm). This CR will remain in Development<br />

Status.<br />

__________________________________________________________________________________________<br />

Clarification Call<br />

PC081403-1 Jeopardy Notification <strong>Process</strong><br />

December 8, 2003<br />

3:00 – 4:00<br />

In attendance:<br />

Valerie Estorga – Qwest Valerie Star – NoaNet Oregon<br />

Marty Petrowski – WAN Tel Oregon Kim Isaacs – Eschelon<br />

Anne Atkinson – ATT Jill Martain – Qwest<br />

Phyllis Burt – ATT James McClusky – Accenture<br />

Donna Osborne Miller – ATT Steph Prull – Eschelon<br />

Ray Smith – Eschelon Cheryl Peterson – ATT<br />

Carla Pardee – ATT Wayne Hart – Idaho PUC<br />

Bonnie Johnson – Eschelon Cindy Macy – Qwest<br />

Cindy Macy – Qwest introduced the attendees and reviewed the purpose of the call. Cindy verified the attendees had the Jeopardy Notification<br />

matrix.<br />

Jill Martain – Qwest explained we have held discussions with the CLECs in hopes of improving the jeopardy process. Jill would like to review the<br />

matrix and allow the CLECs to ask questions and voice their concerns.<br />

Jill explained the change to send jeopardy notification at 6pm was effective over the weekend. This applies to all mechanized jeopardy codes.<br />

The intent of this change should reduce the number of jeopardies sent, as Qwest clears many jeopardies through out the day.<br />

Jill explained there are some manual jeopardies that are not part of this process, such as C)% and SX. Based on investigation, we are looking at<br />

sending jeopardies on Facility and Plug in equipment issues. These would be K and V25 – PICS jeps. Possibility exists to eliminate all _33 work<br />

force jeps. This will allow us to reduce the number of jeps sent on certain phases of the order.<br />

Bonnie Johnson – Eschelon said she would be glad to try this process and see what improvement it makes.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC081403-1<br />

Page 89 of 105<br />

Attachment D


Marty – WAN Tel asked if Qwest could send more information on the jep notification. If the description / content / reason why Qwest is placing the<br />

order in jep, would help the CLEC understand and address the problem. For example, if Qwest says there are local facility issues but does not say<br />

what kind of issue, the CLEC can not take action on the issue. It is very difficult for the CLEC to find more out about the issue too. Jill agreed she<br />

would see if we could provide more detail on why the order was placed in jeopardy. Jill said if more information can be included she would try to<br />

get that implemented as soon as possible.<br />

Bonnie Johnson – Eschelon agreed that providing adequate information on jeopardy notices is critical for the CLEC to look at alternative solutions.<br />

Steph Prull – Eschelon asked if the process could be revised to include the correlation between the ‘reason code’ and the ‘jeopardy detail code’ on<br />

the jeopardy notice. The Disclosure document has the reason code but does not have a correlation to the jeopardy detail code. Jill advised she<br />

would look into this.<br />

Kim Isaacs – Eschelon asked about C09 as this code seems in conflict with the held order process. Jill advised C09 would not occur on a held<br />

order situation. Jill advised jeps are per order, not per LSR.<br />

Bonnie Johnson – Eschelon asked about the CR request regarding when the CLEC gets a jep, and then Qwest does not allow the CLEC time to<br />

react to the FOC (4 hour minimum). Jill asked Bonnie if we could wait and determine the impact of the 6pm jep time change as this change should<br />

reduce the number of jeps and reduce this issue. Bonnie agreed we could discuss this later if it is still an issue.<br />

Bonnie also asked if there was a CLEC forum planned for January. Cindy advised she did not know but would check on. Bonnie suggested we<br />

talk about it at the December <strong>CMP</strong> meeting, and that possibly a better time for the Forum would be in February.<br />

Jill agreed to check on the following items:<br />

1 – adding content to the jeopardy description to make it more informative<br />

2 – check how reason codes match to jep codes in the Disclosure document<br />

Next Steps:<br />

The team agreed to meet again around the week of January 13 to review how the 6pm jeopardy change has impacted the process and to<br />

determine our next steps<br />

____________________________________________________________________<br />

Novmeber 19, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Jill Martain- Qwest advised this CR was revised to say that the CR was going to revisit the existing Jeopardy process, including what notices<br />

should be sent to the customer and then also discuss the content of those notices. Bonnie Johnson – Eschelon agreed updating the CR was<br />

okay. Jill Martain-Qwest advised the next step is to schedule an ad hoc meeting to review information and gather input. John Berard – Covad<br />

advised he has a jeopardy request item to be included in this CR.<br />

_______________________________________________________________________________<br />

Oct 15, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Phyllis Sunins – Qwest reported that she is doing a study of the August data and that there are synergies with this CR and PC072303-1. Jill<br />

Martain will also open a new CR to address the overall Jeopardy <strong>Process</strong>. Bonnie Johnson – Eschelon advised she would like to keep this CR<br />

open and reference it to PC072303-1 and Jill’s new CR. Discussion took place regarding maybe the scope of this CR should be changed, instead<br />

of Jill creating a new CR. Cindy agreed she would talk to Jill about this. Liz Balvin – MCI advised she has some questions about what certain jep<br />

codes mean. A documentation CR has been issued to request definition of jep codes. The team advised that Liz should respond during the<br />

comment cycle and ask about the jep codes she is interested in (C31 and C34). John Berard – Covad asked how many jeps are resolved the<br />

same day? Bonnie Johnson – Eschelon said she did not know numbers but Jill implied the majority of jeps are resolved the same day. This CR<br />

will move to Development Status.<br />

______________________________________________________________________________________________________________________<br />

___________<br />

10/6/03 Ad Hoc <strong>Meeting</strong><br />

Lori Mendoza Allegiance<br />

Russ Urevig Qwest<br />

Deni Toye Qwest<br />

Phyllis Burt ATT<br />

Julie Pickar US Link<br />

Dave Hahn Qwest<br />

Jeanne Whisnet Qwest<br />

Laurie Dalton Qwest<br />

Ann Adkinson ATT<br />

Jill Martain Qwest<br />

Phyllis Sunins Qwest<br />

Carla Pardee ATT<br />

Jen Arnold US Link<br />

Kim Issacs Eschelon<br />

Bonnie Johnson Eschelon<br />

Donna Osborne Miller ATT<br />

Regina Mosely ATT<br />

Jill Martain discussed the synergy's between PC072303-1 and this CR and the issue that came up in the CLEC Forum about FOCs not being sent<br />

after a delayed order is released. Jill explained she would like to implement changing the jep timeframe to 6 pm as identified in PC072303-1. As a<br />

result of this change it will address many of the issues with not enough time to respond to a jep. Jill referred to this as Phase 1. Jill will issue a<br />

Qwest CR to modify the Jep <strong>Process</strong> and make additional changes as needed. Changes such as define jep codes, determine when to send jeps,<br />

and for what conditions. Jill said she certainly can accommodate some time frames in between FOC and Jep. Jill referred to this as Phase 2.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC081403-1<br />

Page 90 of 105<br />

Attachment D


Bonnie agreed that Jill's new CR and implementing the changes for PC072303-1 will take care of this CR. Changing the jep times will take care of<br />

most of these issues.<br />

__________________________________________________________________________________-<br />

9/17/03 <strong>CMP</strong> <strong>Meeting</strong><br />

Bonnie Johnson – Eschelon presented the CR to the CLEC Community. Bonnie advised this continues to be a problem. Eschelon does not<br />

normally get an FOC after a delayed order gets released. Sometimes we get the FOC and we do not have time to react. Qwest needs to make<br />

certain that if we release an order from delayed status that the CLEC gets an FOC, and has time to react before the order is put in a CNR jep.<br />

This happens often. Our service delivery personnel escalate with the tester and the FOC group. Jill Martain is working on the issue with not<br />

receiving an FOC. This was brought up at the CLEC forum. Cindy Macy-Qwest asked if the changes associated to PC072303-1 – changing the<br />

time when Qwest jeps for CNR, would meet this CR. Bonnie advised no, because in this case the order is being released from delayed status and<br />

the original FOC has already occurred.<br />

______________________________________________________________________________________<br />

CLEC Change Request – PC081403-1<br />

Clarification <strong>Meeting</strong><br />

Tuesday August 26, 2003<br />

1-877-552-8688<br />

7146042#<br />

Attendees<br />

Cindy Macy – CRPM<br />

Russ Urevig – Qwest<br />

Phyllis Sunins – Qwest<br />

Laurie Dalton – Qwesst<br />

Bonnie Johnson – Eschelon<br />

Deni Toye – Qwest<br />

Stephanie Prull – McLeod<br />

Julie Picker - US Link<br />

Introduction of Attendees<br />

Cindy Macy-Qwest welcomed all attendees and reviewed the request.<br />

Review Requested (Description of) Change<br />

Bonnie Johnson-Eschelon reviewed the CR. Bonnie explained that ½ the time they do not get an FOC after the order is released. This problem is<br />

being addressed by Jill Martain and is not part of this CR but it is an issue that impacts this CR. The CLEC needs time to react to the released<br />

LSR and to accept the circuit.<br />

Phyllis explained the jep could be placed early in the morning and the tech working on the it may get a solution the same day. This creates a<br />

timing difficulty. The current process is for the order to be jep’d, Qwest would send an FOC when they find out the issue has been taken care of,<br />

and then if the customer is not ready the LSR is put in CNR.<br />

Bonnie advised they would like a 2-4 business hour time frame to respond to the FOC before Qwest puts the LSR in CNR.<br />

The process today does not give a time frame on the FOC, it gives a date but no time frame.<br />

Confirm Areas and <strong>Product</strong>s Impacted<br />

Macy - Qwest confirmed that the attendees were comfortable that the request appropriately identified all areas and products impacted.<br />

Confirm Right Personnel Involved<br />

Macy - Qwest confirmed with the attendees that the appropriate Qwest personnel were involved.<br />

Identify/Confirm CLEC’s Expectation<br />

Macy-Qwest reviewed the request to confirm Eschelon’s expectation.<br />

Identify and Dependant Systems Change Requests<br />

Macy-Qwest asked the attendees if they knew of any related change requests.<br />

Establish Action Plan<br />

Macy-Qwest asked attendees if there were any further questions. There were none. Macy-Qwest stated that the next step was for Eschelon to<br />

present the CR at the September Monthly <strong>Product</strong>/<strong>Process</strong> <strong>Meeting</strong> and thanked all attendees for attending the meeting.<br />

Qwest Response<br />

October 8, 2003<br />

For Review by CLEC Community and Discussion at the October 15, 2003,<br />

<strong>CMP</strong> <strong>Product</strong>/<strong>Process</strong> <strong>Meeting</strong><br />

Bonnie Johnson<br />

Eschelon<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC081403-1<br />

Page 91 of 105<br />

Attachment D


SUBJECT: CLEC Change Request Response - CR # PC081403-1<br />

This is a preliminary response regarding the Eschelon CR PC081403-1. This CR requests that the ‘Delayed order process be modified to allow the<br />

CLEC a designated time frame to respond to a released delayed order after Qwest sends and updated FOC. Qwest will contact the CLEC to test<br />

and accept only after the updated FOC has been sent and a designated time frame has passed. Qwest will not put the order in a CNR (customer<br />

not ready) jeopardy status until this time frame has passed and the CLEC is not ready’.<br />

Qwest believes this CR has synergies with the Eschelon CR PC072303-1 ‘Customer Not Ready (CNR) jeopardy notice should not be sent by<br />

Qwest to CLEC before 5 PM’. Qwest proposes moving this Change Request into Evaluation Status while we investigate the commonalities further<br />

and will provide a status update at the November <strong>CMP</strong> meeting.<br />

An Ad Hoc <strong>Meeting</strong> is scheduled for Monday, October 6, 2003 from 10:00 – 11:30 a.m. MST to discuss CR# PC072303-1 and PC081403-1.<br />

Sincerely,<br />

Phyllis Sunins<br />

Wholesale Markets <strong>Process</strong> Organization<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC081403-1<br />

Page 92 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC081403-2 Workback process/products expanded to<br />

include additional products and allow partial<br />

workbacks. Qwest will post the process and<br />

products included in the Business Procedure<br />

section of the web site.<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc <strong>Product</strong>s to be<br />

defined through a<br />

collaborative effort<br />

Qwest should expand the current work back process to include additional products and partial workbacks. Qwest currently allows workbacks for<br />

only LNP (Local number portability) orders and requires the entire LSR to be worked back. CLECs sometimes have a need to request a workback<br />

on only a portion of an LSR or for products outside of the current products this process applies to (LNP). The current Qwest documentation for the<br />

workback process is located in the Qwest LNP PCAT (titled end user out of service) and does not define that a CLEC is required to do the<br />

workback on an entire LSR. Qwest documentation should not leave this to interpretation. Qwest should provide clear documentation of the entire<br />

process in the Business Procedure section of the web site. This should include a detailed process and the products the workback process applies<br />

to.<br />

Expected Deliverable:<br />

Qwest will develop, document and train an expanded "workback" process to include additional products and partial workbacks. Qwest should allow<br />

the CLEC to do workbacks on partial LSRs and include additional products. Qwest should post this as a "process" under the business procedure<br />

section of the Qwest Wholesale web site.<br />

Status History<br />

Bliss, Susie<br />

08/14/03 - CR Submitted<br />

08/15/03 - CR Acknowledged<br />

8/19/03 - LWTC for Bonnie regarding Clarification meeting date<br />

8/26/03 - Held Clarification <strong>Meeting</strong><br />

9/17/03 - Sep <strong>CMP</strong> meeting minutes will be posted to the database<br />

10/8/03 - Sent response to CLEC<br />

10/15/03 - Oct <strong>CMP</strong> meeting minutes will be posted to the project meeting section<br />

11/19/03 - Nov <strong>CMP</strong> meeting minutes will be posted to the database<br />

12/17/03 - Dec <strong>CMP</strong> meeting minutes will be posted to the database<br />

1/2/04 - Notification distributed to review draft process on 1/12/03<br />

1/8/03 - PROD.01.08.04.F.01226.LNP_V25<br />

1/12/03 - Held CLEC ad hoc meeting to review draft process<br />

1/21/03 - Jan <strong>CMP</strong> meeting minutes will be posted to the database<br />

2/18/04 -Feb <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the project meeting section<br />

Project <strong>Meeting</strong>s<br />

Johnson, Bonnie<br />

Wells, Joan<br />

Macy, Cindy<br />

February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Cindy Macy – Qwest provided status for Joan Wells. The first part of this process was published and implemented. Joan is working on the<br />

process for the additional products. Joan is working with Retail to identify impacts. This CR will remain in Development Status.<br />

_______________________________________________________________<br />

January 21, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Cindy Macy – Qwest advised that Joan Wells – Qwest held an ad hoc meeting on January 12 and reviewed the draft process. Joan took some<br />

points to incorporate into the process and review. The documentation is in progress. This CR will remain in Development Status.<br />

________________________________________________________________________<br />

Ad-hoc <strong>Meeting</strong><br />

1:00 p.m. (MDT) / Monday January 12, <strong>2004</strong><br />

1-877-552-8688 7146042<br />

PC 081403-2<br />

*** Attended Conference Call Name/Company:<br />

Carla Pardee, AT&T<br />

Donna Osborn-Miller, AT&T<br />

Cheryl Miller, AT&T<br />

Andrea Niles, AT&T<br />

David Bellinger, AT&T<br />

Joyce Perry, AT&T<br />

Bonnie Johnson, Eschelon<br />

Information Current as of:<br />

Report Name:<br />

Development<br />

10/15/03<br />

Originator Company Name:<br />

Eschelon<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

22<br />

<strong>Product</strong>s<br />

Impacted<br />

PC081403-2<br />

Page 93 of 105<br />

Attachment D


Kim Isaacs, Eschelon<br />

Kim Sutton, Cox Communication<br />

Carol Roland, Cox Communication<br />

Carla Cox, 180 Communication<br />

Janet Harper, 180 Communication<br />

Joan Wells, Qwest<br />

Susie Wells, Qwest<br />

Terri Kilker, Qwest<br />

Linda Harmon, Qwest<br />

<strong>Meeting</strong> Agenda: Action<br />

1.0 Introduction of Attendees<br />

Introduction of participants on the conference call was made and the purpose of the call discussed<br />

2.0 Review Requested (Description of) Change<br />

Joan Wells, Qwest reviewed the Draft Proposal process and scenarios. This is for Part II Workback Expansion Proposal to include additional<br />

products.<br />

The following were questions or clarifications made during the meeting:<br />

David Bellinger, AT&T asked what the intervals would be for getting the customer back in service. Joan said she would have to check but in any<br />

case they would mirror the existing timeframes.<br />

Joan verified that this process is to cover when orders have completed and has nothing to do with LNP or number portability in general.<br />

Cheryl Peterson, AT&T asked what time orders are completed. Joan answered that it often depends on the type of order.<br />

Kim Isaacs, Eschelon ask if process steps 6-10 is for when the account is UNE-P with another CLEC. Joan answered yes and that she will clarify<br />

in document.<br />

Bonnie Johnson, Eschelon asked if Restriction 4 was also the practice in Retail as well. Joan said yes that there are no parity issues.<br />

Bonnie commented that process steps 11 through 13 are where most of these cases fall and customers are impacted. She stated the purpose of<br />

the CR was to have a different process from going through the Retail front door since the area between Wholesale and Retail is often painful to the<br />

customer and CLEC. Bonnie is not asking that Retail not be involved but to have a process where someone knowledgeable handles the situation<br />

and where the customer or CLEC does not have to start at the Retail front door. Joan stated that Wholesale couldn’t handle Retail involvement<br />

she agreed to look into what could be done. Bonnie said if we could get resolution to the front door issue that she is fine with the process. AT&T<br />

and 180 Communication agreed<br />

Joan stated that Part 1 of the documentation should be out in a few weeks. She also said she will try to have an update for the January <strong>CMP</strong><br />

meeting and will continue to evaluate the need for another meeting.<br />

________________________________________________________________<br />

December 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Joan Wells – Qwest advised she has sent the documentation for Partial Work backs on LNP to the documentation team. She also has a draft<br />

proposal available for the other products that she would like to review with the CLECs. A meeting will be scheduled the week of January 5 to<br />

review the draft proposal. Bonnie Johnson – Eschelon requested to have the process sent out in advance so it could be reviewed prior to the<br />

meeting. Joan agreed and advised it would be included in the meeting notification ahead of the meeting date. This CR will remain in<br />

Development Status.<br />

_________________________________________________________________________<br />

November 19, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Joan Wells reviewed Qwest’s response and identified the products that will be addressed with this CR. Joan explained she would like to call this<br />

process the ‘Restoral Request’ process. Ervin Rea-ATT asked what are the requirements to get the customer back in service? Joan advised they<br />

are developing those requirements as part of this CR. Basically the process would consist of the customer contacting the Call Center to advise of<br />

the problem. A ticket is issued. A supplement may need to be issued to the LSR depending on if the work or LSR is completed. The service<br />

would follow an expedite process to restore. Qwest is looking into the criteria to determine when a restoral request is allowed and when charges<br />

would be incurred to reinstate the service.<br />

___________________________________________________________________________<br />

Oct 15, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Cindy Macy – Qwest advised she would page Joan to the call as she is on vacation. Bonnie Johnson – Eschelon said she has reviewed the<br />

response and understands Qwest will begin working on the partial workback process for LNP and the other products are under review. Bonnie<br />

advised we did not need to page Joan to the meeting. This CR will move to Development Status.<br />

__________________________________________________________________________________<br />

Sept 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Bonnie Johnson advised we had a good clarification call. There were attempts made a reeling in the scope of this CR. Bonnie advised she would<br />

like the process expanded on product where it is workable. Today, Workback is on LNP and it is all or nothing. Bonnie requested for Qwest to<br />

expand where this can be done and also to be able to do a partial Workback. Joan asked if another ad hoc meeting may be appropriate to gather<br />

additional issues, on a product by product basis from other CLECs. Any product that is can be included on should be included. This request is<br />

clearly asking for these product and when a CLEC can do a Workback. Judy Schultz asked if it was appropriate for Qwest to prepare a<br />

recommendation. Bonnie agreed for Qwest to review scenarios and do this on a case by case basis. Bonnie advised this request is a result of an<br />

escalation. Escalations usually drive process improvements. Susie Bliss advised Qwest would also look at volumes and costs.<br />

_____________________________________________________________________________________<br />

CLEC Change Request – PC081403-2<br />

Clarification <strong>Meeting</strong><br />

Tuesday, August 26, 2003<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC081403-2<br />

Page 94 of 105<br />

Attachment D


1-877-552-8688<br />

7146042#<br />

Attendees<br />

Cindy Macy – CRPM<br />

Dusti Bastian – Qwest<br />

Mallory Paxton – Qwest<br />

Joan Wells – Qwest<br />

Sharon Van Meter – ATT<br />

Bonnie Johnson - Eschelon<br />

Introduction of Attendees<br />

Macy-Qwest welcomed all attendees and reviewed the request.<br />

Review Requested (Description of) Change<br />

Bonnie Johnson-Eschelon reviewed the CR. Bonnie explained the PCAT defines a work back process, however it is for LNP only and does not<br />

include partial work backs. Eschelon had a situation where they were trying to work back the DSL portion of a cut and could not do a partial work<br />

back. Qwest did do this but it was very difficult.<br />

Joan Wells asked if Bonnie wanted work backs available to new products or products associated to LNP? Bonnie advised there are multiple<br />

situations when this may be needed. For example, when we are converting a customer from Qwest Retail to Eschelon UNE-P.<br />

Joan Wells advised the work back process was put in place when Qwest was disconnecting customers and the CLECs were having trouble<br />

getting the customer installed on the same due date. This is not occurring very much any more. On a conversion there is usually no facility<br />

change that occurs so there wouldn’t be a work back situation. Bonnie advised there can be circumstances that cause facility changes and thus<br />

the need for a work back; such as Qwest record issues that show the DSL on the wrong line, or PBX that causes trouble on the line, credit card<br />

machines etc. Bonnie agreed it is not a high percentage of times that this happens, but it is important when it does happen.<br />

The group discussed that there are many variables and it could be a different process based on each circumstance. The group tried to determine<br />

the scope of the CR as the process may be different based on each product or situation. Joan Wells advised she can not document what the<br />

CLEC needs to do for their part of the work back.<br />

Joan asked if the CLECs would be willing to pay for this service. Bonnie advised under certain circumstances it makes sense. Mallory Paxton –<br />

Qwest advised in some cased it would involve Qwest doing a New Connect. Joan Wells advised there should be parameters around how much<br />

time can go by to determine if a work back is a valid option.<br />

Bonnie advised she would like this in the Business <strong>Process</strong> section of the PCAT, and not be product specific. Cindy Macy-Qwest advised this<br />

would imply the process would be a high level process about work backs in general and not be specific to each product. Mallory advised the<br />

process would be different for different products so a general process may not provide a lot of value. Some things to consider are the time<br />

constraints, charges, process by product, identify the limitations of the process versus all the conditions that it could apply to.<br />

Bonnie advised UNE-P and Resale are the most commonly ordered products so it would make sense to document it for those two products.<br />

Additionally, adding information to the LNP product to include partial work backs is needed. Bonnie advised she would lke the process defined and<br />

documented so we have a process to follow. It doesn’t have to cover the universe.<br />

Confirm Areas and <strong>Product</strong>s Impacted<br />

Cindy Macy-Qwest reviewed the scope of the CR.<br />

Confirm Right Personnel Involved<br />

Cindy Macy-Qwest confirmed with the attendees that the appropriate Qwest personnel were involved.<br />

Identify/Confirm CLEC’s Expectation<br />

Cindy Macy-Qwest reviewed the request to confirm Eschelon’s expectation.<br />

Identify and Dependant Systems Change Requests<br />

Cindy Macy-Qwest asked the attendees if they knew of any related change requests.<br />

Establish Action Plan<br />

Macy-Qwest asked attendees if there were any further questions. There were none. Macy-Qwest stated that the next step was for Eschelon to<br />

present the CR at the September Monthly <strong>Product</strong>/<strong>Process</strong> <strong>Meeting</strong> and thanked all attendees for attending the meeting.<br />

Qwest Response<br />

Response Update<br />

For Review by the CLEC Community and Discussion at the November 19, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

November 11, 2003<br />

Eschelon<br />

Bonnie Johnson<br />

Sr. Manager ILEC Relations<br />

SUBJECT: CR # PC081403-2 Workback process/products expanded to include additional products and<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC081403-2<br />

Page 95 of 105<br />

Attachment D


allow partial workbacks. Qwest will post the process and products included in the Business Procedure<br />

section of the web site.<br />

This letter is being issued to provide an updated response on the development of Eschelon’s Change Request<br />

(CR) PC081403-2. This CR requests that:<br />

· Qwest expand the existing LNP workback process to allow partial workbacks<br />

· Qwest expand the workback process to include additional products<br />

Qwest is currently in the development stages of both a new “Workback”(WB) process for LNP that will<br />

include partial restorals and a new expanded Workback process that will be identified as a “Restoral<br />

Request” (RR) for the Resale / UNE-P POTS and Resale / UNE-P Centrex 21 products.<br />

Qwest will provide an updated status on the process development at the December <strong>CMP</strong> meeting.<br />

Sincerely,<br />

Joan Wells<br />

Sr. <strong>Process</strong> Analyst<br />

Qwest Communications<br />

_____________________________________________________________________________________________________<br />

For Review by the CLEC Community and Discussion at the October 15, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

October 8, 2003<br />

Eschelon<br />

Bonnie Johnson<br />

Sr. Manager ILEC Relations<br />

SUBJECT: CR # PC081403-2 Workback process/products expanded to include additional products and allow partial workbacks. Qwest will post<br />

the process and products included in the Business Procedure section of the web site.<br />

This letter is in response to Eschelon’s Change Request (CR) PC081403-2. This CR requests that:<br />

? Qwest expand the existing LNP workback process to allow partial workbacks<br />

? Qwest expand the workback process to include additional products<br />

Qwest accepts this request. Qwest will change the workback process for Local Number Portability and Loop Service with Local Number Portability<br />

to include partial workbacks. This change will be identified and documented within the current workback process located in the existing LNP PCAT.<br />

Qwest is currently reviewing the workback process expansion request and its applicability to other products and processes that it will apply to.<br />

Qwest requests that this CR be placed in development status. Qwest will provide an update at the November <strong>CMP</strong> meeting.<br />

Sincerely,<br />

Joan Wells<br />

Sr. <strong>Process</strong> Analyst<br />

Qwest Communications<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC081403-2<br />

Page 96 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC092903-1 Joint Inventory <strong>Process</strong> (previous name:<br />

New Collocation <strong>Process</strong>)<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Collocation<br />

AT&T requests that Qwest, with the input of AT&T and other CLECs, develop a process where Qwest dispatches a person to verify information<br />

related to a Collocation site. For example, if AT&T needs information related to the APOT/CFA or power terminations or any other element<br />

associated with the Collocation site, Qwest will dispatch an employee to the specific Collocation site and verify existing information or provide<br />

additional information back to AT&T. The new process should include the application, intervals, RFS (ready for service date) and any other<br />

components relevant to the new process.<br />

Expected Deliverable<br />

Qwest and CLECs develop a process to verify existing information or provide additional information associated with a specific Collocation site.<br />

This new process should be available by the end of 2003.<br />

Status History<br />

09/29/03 - CR Submitted<br />

10/01/03 - CR Acknowledged<br />

10/3/03 - Contacted customer to schedule clarification call<br />

10/9/03 - Held Clarification call<br />

10/15/03 - Oct <strong>CMP</strong> meeting minutes will be posted to the project meeting section<br />

11/19/03 - Nov <strong>CMP</strong> meeting minutes will be posted to the database<br />

12/1/03 - Scheduled CLEC input meeting on 12-9 to review process<br />

12/9/03 - Reviewed the process with CLEC community<br />

12/16/03 - Posted meeting notes<br />

12/17/03 - Dec <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the database<br />

12/19/03 - Held ad hoc meeting<br />

1/21/03 - Jan <strong>CMP</strong> meeting minutes will be posted to the database<br />

2/4/04 - Held Ad Hoc <strong>Meeting</strong> to review process udpates<br />

2/18/04 -Feb <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the project meeting section<br />

Project <strong>Meeting</strong>s<br />

Campbell, Bill<br />

Nelson, Steve<br />

Macy, Cindy<br />

February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Cindy Macy – Qwest provided status for Steve Nelson. Cindy advised that the team met with the CLECs on February 4, <strong>2004</strong>. The process and<br />

forms were reviewed. Qwest advised a Joint Inventory process trial would be held with some of the CLECs. Qwest will use the trial to work out<br />

any gaps in the process. This CR will remain in Development Status.<br />

_____________________________________________________________________________<br />

Joint Inventory <strong>Process</strong><br />

February 4, <strong>2004</strong> - 1:00 – 2:30 p.m. MST<br />

In attendance:<br />

Steve Nelson – Qwest Steve Kast – Qwest<br />

Bill Fellman – Qwest Rene Lerma – Eschelon<br />

Mary Ann Wiborg – Qwest Cindy Macy – Qwest<br />

Lillian Robertson – Qwest Teresa McKenzie – Qwest<br />

John Waltrip – Qwest Kathy Battles – Qwest<br />

Cheryl McCombe – ATT Peggy Englert – Qwest<br />

Development<br />

11/17/03<br />

Originator Company Name:<br />

Report Line Number<br />

<strong>Product</strong>s<br />

Impacted<br />

Cindy Macy – Qwest opened the call and reviewed the agenda. Steve Nelson – Qwest reviewed the four documents at a high level and asked if<br />

there were any questions or concerns with the forms or process. Eschelon and ATT advised they are okay with the forms and process.<br />

Steve Nelson – Qwest explained we would like to start the trial and perform a joint inventory on 2 sites per CLEC. Qwest would like to do this on a<br />

mix of locations and a mix of types of collocation sites (virtual, cageless, caged, etc). The trial will be done at no cost, as it will help Qwest with our<br />

cost pricing study. Our draft cost estimate is approximately 19.25 hours at $1500.00.<br />

Steve reviewed each section of the Joint Inventory form; service level, virtual equipment, grounding, synchronization, power, administrative lines,<br />

space, and notes. Rene – Eschelon asked if we included CLEC to CLEC direct collocation sites? Qwest advised no, we don’t keep records of<br />

CLEC to CLEC facilities.<br />

Information Current as of:<br />

Report Name:<br />

AT&T<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

23<br />

PC092903-1<br />

Page 97 of 105<br />

Attachment D


Steve reviewed the process flow diagram. This process is a 60-day process. Qwest has tried to be responsive to the CLECs needs. The CLECs<br />

advised they are okay with the flow and intervals and the process looks good. Steve Nelson advised that we would update the process if needed<br />

after the trial.<br />

Steve reviewed the PCAT. Steve advised an amendment would be required. Steve reminded the team that there is not any time to repair or test<br />

during the inventory. Steve reviewed the description, terms, ordering , and procedures. Steve advised that if the CLECs have more than one site<br />

per location and they want them both inventoried, it would be best to schedule them together, however each site would require a separate<br />

application.<br />

Steve advised that Qwest will be using Telric based pricing, instead of market based pricing. This allows Qwest to bill a set amount and get the<br />

process completed faster and at the lowest cost to the CLEC customer.<br />

Bill Fellman – Qwest asked Steve to clarify what the ‘maximum of two scheduled visits’ means. The team advised this is regarding the reschedule<br />

/ cancellation / charge policy if the CLEC has to reschedules a joint inventory two times. The CLECs on the call stated this seemed fair.<br />

Steve Nelson – Qwest advised if there are discrepancies between billing and actual equipment located at the site, the billing will be corrected.<br />

Steve Nelson and Peggy Englert – Qwest discussed the trial. Peggy’s team will contact the four CLECs that expressed and interest (180, ATT,<br />

Sprint, Eschelon) to obtain a proposed and prioritized list of sites to inventory. Qwest would like a mix of locations and types of sites to inventory.<br />

Next Steps:<br />

Collocation Service Managers will contact and work with CLECs to obtain a proposed and prioritized list of sites to inventory<br />

CLECs will have a target date of February 13 to submit an application form to Qwest (this would start the process)<br />

Steve Nelson will prepare Amendment by February 20<br />

Steve Nelson will start the documentation process by February 20<br />

Qwest will work with the CLECs during the trial<br />

The team will get back together after the trial to discuss results<br />

Final pricing studies will be prepared.<br />

____________________________________________________________<br />

January 21, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Steve Nelson – Qwest advised they have developed the preliminary price structure. Qwest will do a trial with four CLECs and two Collocation sites<br />

each to help determine the correct pricing. The Amendment is in progress and it will be posted to the web site soon. The Application form,<br />

Inventory form, processes, and <strong>Product</strong> description will be available for the meeting that is scheduled next week on January 30. This CR will<br />

remain in Development Status.<br />

_____________________________________________________________________<br />

December 19, 2003<br />

Ad Hoc <strong>Meeting</strong><br />

PC092903-1 Joint Inventory <strong>Process</strong><br />

In Attendance:<br />

Bob Alex – Qwest John Waltrip – Qwest<br />

Steve Nelson – Qwest Stacy Meisenhiemer – Sprint<br />

Bonnie Johnson – Eschelon Lillian Robertson – Qwest<br />

Kathy Battles – Qwest Rene Lerma – Eschelon<br />

Cindy Macy – Qwest Peggy Englert – Qwest<br />

Mary Simon – 180 Communications<br />

Cindy Macy – Qwest opened the call and reviewed the agenda for the meeting. We will be reviewing the Application form, the Inventory form, and<br />

the high level flow and critical intervals.<br />

Steve Nelson – Qwest began by reviewing the draft intervals:<br />

Day 2 Quote<br />

Day 20 Identify Inventory participants<br />

Day 35 Perform Joint Inventory<br />

Day 55 Distribute the results of the Joint Inventory<br />

Day 60 Hold follow up call to review the results<br />

Steve advised the pricing study is not completed as of yet. The preliminary cost is $1250.00. Steve would like to conduct Beta tests with CLECs<br />

to get a better judge of time and effort. Steve advised next steps are to finalize the forms and cost. The team will meet again the 3rd week in<br />

January.<br />

John Waltrip – Qwest reviewed the Inventory and Application forms. John explained the engineer fills out the Inventory form and gives it to the<br />

SICM. Rene – Eschelon asked if Qwest could mirror what is on the APOT sheets. John advised Qwest will review the APOT form, if inventory<br />

differs than what is on the current APOT, we will then update the APOT. Kathy Battles – Qwest advised for ATT some jobs are old or they bought<br />

out another customer, so ATT may not have current APOT forms.<br />

Rene – Eschelon asked if this process applies to a CLEC to CLEC connection. John advised no, as Qwest does not inventory that equipment.<br />

Rene – Eschelon commented about the price and asked why managers will be gathering all the information. If managers are gathering the<br />

information the cost would be higher, and that is basically administrative work. Steve Nelson reviewed how the work is broken out between groups<br />

and explained that is how we have the work assigned. Steve would like to do a Beta trial for free with 3-4 of the CLECs, on 1-2 Collocation sites<br />

each. The trial will allow us to refine our time, cost and forms. Steve would like to do the trial in the January time frame. Steve advised he would<br />

work with Peggy Englert’s team to contact the CLECs to arrange the Beta trial. The CLECs participating in the calls advised they would be<br />

interested in the Beta test. That would include ATT, Eschelon, 180 and Sprint.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC092903-1<br />

Page 98 of 105<br />

Attachment D


Cindy Macy – Qwest asked Steve to consider that the timing of the trial and the release of the documented process can occur at the same time.<br />

Steve advised they would target publishing the document so it can be reviewed in the February time frame.<br />

_______________________________________________________________<br />

December 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Steve Nelson – Qwest reported that the team held a meeting on December 9 to review the process. There was a lot of participation and good<br />

discussion took place. The team agreed to meet again on December 19 to review the Application form and Inventory form. Steve explained the<br />

process will include a joint inventory of collocation sites that look at everything that is at the site. Liz Balvin – MCI asked if we made any progress<br />

on the cost analysis? Steve reported that the cost estimate is available but the final cost study will take 3-4 weeks to complete. The team will<br />

meet again in January to discuss the cost study more. This CR will stay in Development status.<br />

___________________________________________________________________<br />

PC092903-1 Joint Inventory <strong>Process</strong><br />

Ad Hoc <strong>Meeting</strong><br />

December 9, 2003<br />

In attendance:<br />

Eric Yohe – Qwest Peggy Englert – Qwest<br />

Carla Pardee – ATT Cindy Roni – Eschelon<br />

Rene Lerma – Eschelon Bonnie Johnson – Eschelon<br />

Liz Balvin – MCI Cheryl McCombs – ATT<br />

Michelle Brandt – ATT John Waltrip – Qwest<br />

John Lawrence – Qwest Bob Alex – Qwest<br />

Kim Isaacs – Eschelon Steve Nelson – Qwest<br />

Kathy Battles – Qwest Louis Ruiloba – ATG<br />

Paul Hansen - Eschelon<br />

Cindy Macy – Qwest opened the call and advised the purpose of today’s meeting is to review the draft Joint Inventory <strong>Process</strong> and gather input<br />

from the CLECS and make sure we are on track with expectations.<br />

Steve Nelson – Qwest reviewed in detail the <strong>Process</strong> Flow, which was distributed as part of the notification of the meeting. Steve advised the<br />

Application and Inventory form are under development and will be reviewed at our next meeting. Steve advised Qwest would offer a Joint<br />

Inventory application for virtual sites also.<br />

Steve Nelson – Qwest asked if the CLECs would like to identify what inventory they think they have at each site, or if the CLECs would like Qwest<br />

to identify what is actually at the site. Rene Lerma – Eschelon advised Qwest should identify what inventory is at each site. The CLECs agreed.<br />

Rene Lerma – Eschelon asked for timeframes and intervals to accomplish the different steps in the process. Steve Nelson – Qwest advised the<br />

draft timelines are expected to be as follows:<br />

Application submitted by CLEC<br />

Up front work that Qwest needs to do to schedule the Joint Visit: 15–20 days after receipt of application<br />

Schedule and conduct the Joint Visit: 20-45 days<br />

Review results: 55-60 days<br />

Schedule and hold wrap up call: 7-10 days<br />

Other actions based on results of visit:<br />

Billing changes<br />

Database changes<br />

Augment work (if needed)<br />

Steve Nelson – Qwest discussed pricing. The plan is that pricing will not include a QPF. An amendment will be done. Steve will look at a Telric<br />

Pricing study to determine price and present this to the team. Qwest would like to charge one rate to have a Joint Inventory done. This simplifies<br />

the process and pricing and allows the CLECs to budget appropriately for the work. Billing would be done in BART.<br />

Rene Lerma – Eschelon asked what would the results of the inventory look like, what would be sent to the CLECs? Steve Nelson – Qwest advised<br />

there is an Inventory Form that will be used. We will review this at the next meeting. It is a 3-page form, that would include items such as<br />

termination feeds, power feeds, fused locations, BDFB locations, frame id, block locations, DSC bay panel, etc.<br />

Steve Nelson – Qwest advised that Qwest would not do testing at the same time of the Joint Inventory. No additional work would be done at the<br />

same time. This is to keep costs low for performing a Joint Inventory.<br />

The team also discussed that Qwest could accept the application form to begin the inventory process without advance payment. The request<br />

would be irrevocable. Payment should be made by good faith. If the process is requested, then the payment will be made.<br />

Liz Balvin – MCI asked if there would be time for additional questions. Cindy Macy – Qwest advised the team will meet again, and after the<br />

process is documented it will go out for review and comment.<br />

Next Steps:<br />

Meet again on December 19, 2003<br />

Review forms (application and inventory form)<br />

_________________________________________________________________<br />

November 19, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Steve Nelson – Qwest recapped the CR request from ATT. ATT would like Qwest to develop a process where Qwest dispatches a person to verify<br />

and inventory information related to a Collocation site. Steve reviewed Qwest’s response. Qwest accepts this CR and is working to develop the<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC092903-1<br />

Page 99 of 105<br />

Attachment D


process to perform a comprehensive inventory of an existing Collocation site. SICMs will be involved with performing the comprehensive<br />

inventory. Steve is calling this process a ‘Joint Inventory <strong>Process</strong>’. As a result of this process billing corrections may be needed. Steve advised<br />

he will work with Cindy to schedule another CLEC review meeting. Topics of discussion at the meeting include high-level process flow,<br />

deliverables, costing model and ordering process. The CLECs agreed that Qwest could change the title of the CR to ‘Joint Inventory Visit’.<br />

___________________________________________________________________________<br />

October 15, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Michelle Brandt – ATT reviewed the CR and explaind ATT is looking for a joint survey process where Qwest would dispatch a person to a<br />

Collocation site to help provide information about the Collocation site, such as power information. Steve Nelson – Qwest advised a good<br />

clarification call was held and the Qwest team will be meeting internally to work out the details. The status will be moved to Presented.<br />

______________________________________________________________________________________________________________________<br />

__________<br />

October 9, 2003<br />

1-877-552-8688 7146042#<br />

PC092903-1 New Collocation <strong>Process</strong><br />

Attendees<br />

Steve Nelson – Qwest<br />

Lillian Robertson – Qwest<br />

Denise Martinez – Qwest<br />

Cheryl McCombs-ATT<br />

Rich Powers – ATT<br />

Peggy Englert – Qwest<br />

Janet Leonard – Qwest<br />

Ben Campbell – Qwest<br />

Bob Alex – Qwest<br />

Doug Andreen – Qwest<br />

Cindy Macy – Qwest<br />

<strong>Meeting</strong> Agenda:<br />

1.0 Introduction of Attendees<br />

Attendees introduce<br />

2.0 Review Requested (Description of) Change<br />

Rich Powers – ATT reviewed the Change Request. Rich explained ATT is looking for a mechanism to have a joint site survey done on particular<br />

Collocation sites. ATT needs to inventory some of their Collocation sites to determine type of space, size of space, and especially the power<br />

arrangement. ATT needs to update their inventory so they are ordering correctly, and to improve access planning. Rich explained there is a gap in<br />

their power inventory, at the assignment level. They are interested in the BDFB inventory, relay rack, fuse, etc.<br />

Cindy Macy – Qwest asked Rich if they need this on all Collocations or only certain sites and certain situations. Rich said they would like to be<br />

able to request this ‘as needed’.<br />

Steve Nelson – Qwest asked what level of detail is needed? Is this the circuit working level? Rich advised no, the total number of terminations is<br />

good.<br />

Lillian Robertson – Qwest asked Rich to clarify what was meant by ‘the new process should include the application intervals, RFS and any other<br />

components relevant to the new process’. Rich explained they would want to understand the intervals for ordering a site survey, for completing a<br />

site survey. Specifically, ATT is requesting A Joint Site Survey –1. The Terminations, 2 – Power Assignment of feeds needed and 3. How the<br />

Power is fused.<br />

Qwest asked what additional information is needed: Rich explained that for DS0 terminations, Qwest provides entire picture of CFA. If ATT orders<br />

power, Qwest only sends information about the power ordered, not the entire power inventory at the collocation.<br />

Cindy Macy-Qwest asked if the site survey would be requested before an order is placed? Rich advised normally yes, as they would like to have<br />

the records correct before an order is placed.<br />

Rich explained if he wanted to do a joint survey with Qwest, how would he go about ordering that? ATT would like Qwest to develop a process to<br />

perform a joint survey. Identify such things as intervals related to this request.<br />

Kathy Battles – Qwest advised that ATT bought several sites from another company that they do not have complete records on. The SICMs have<br />

done some survey of sites but additional help is needed.<br />

Ben Campbell – Qwest clarified that ATT is looking for power data first, and then other features are helpful, but the power components are critical.<br />

Rich advised power, then cross connects and then space information is needed. (In that order).<br />

Rich – ATT explained they are building a database to store this information; power inventory system.<br />

3.0 Confirm Areas & <strong>Product</strong>s Impacted<br />

Collocation Site Surve<br />

4.0 Confirm Right Personnel Involved<br />

<strong>Team</strong> agreed the right personnel are involved. Ben Campbell / Steve Nelson would be the lead on this CR.<br />

5.0 Identify/Confirm CLEC’s Expectation<br />

<strong>Process</strong> to request a Joint Sight Survey of Collocation Site<br />

Intervals for this process<br />

6.0 Identify any Dependent Systems Change Requests<br />

Non<br />

7.0 Establish Action Plan (Resolution Time Frame)<br />

ATT will present the CR at the October <strong>CMP</strong> Meetin<br />

Qwest will provide our Response at the November <strong>CMP</strong> <strong>Meeting</strong><br />

Qwest Response<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC092903-1<br />

Page 100 of 105<br />

Attachment D


November 11, 2003<br />

For Review by the CLEC community and discussion at the November 19, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Lydia Braze<br />

AT&T<br />

SUBJECT: Qwest’s Change Request Response - CR PC092903-1<br />

“New Collocation <strong>Process</strong>”<br />

This CR requests “Qwest, with the input of AT&T and other CLECs, develop a process where Qwest<br />

dispatches a person to verify information related to a Collocation site. For example, if AT&T needs<br />

information related to the APOT/CFA or power terminations or any other element associated with the<br />

Collocation site, Qwest will dispatch an employee to the specific Collocation site and verify existing<br />

information or provide additional information back to AT&T. The new process should include the<br />

application intervals, RFS and any other components relevant to the new process.”<br />

We have many collocation processes and procedures today which meet some of these needs. Qwest<br />

currently offers a comprehensive walk-through by a State Interconnect Manager (SICM) with the customer<br />

when the final 50% of the non recurring quote is paid. This procedure will still be offered. We provide<br />

APOT/CFA which includes a cumulative listing of all CLEC termination cables and entrance facilities. This<br />

will continue. Qwest offers a site visit associated with an Available Inventory request before order<br />

submission. Qwest offers up to three site visits after payment of the initial 50% on a collocation application.<br />

We plan to continue to provide these services.<br />

As per the CR, however, it was understood that AT&T wants a comprehensive process to ensure all aspects<br />

of the collocation site are accurate including terminations, power, space, type of collocation, APOT/CFA,<br />

and billing rate elements and quantities. This process relates to previously completed sites.<br />

Qwest accepts this CR and will work with the CLEC community to offer a new comprehensive process<br />

which can be submitted at the CLEC’s request. It will be priced out and offered as an amendment. The<br />

following is a high level overview of what services Qwest is prepared to offer to meet the CR request.<br />

A clarification call was held with AT&T on October 9, 2003. Subsequent to that call a cross-functional team<br />

was put together to start to frame what this added process would look like.<br />

The process being proposed looks like this in Qwest’s vision:<br />

· A separate application will be developed for these requests.<br />

· Every effort will be made to minimize the costs for this process.<br />

· Inventoried items will include space, power, and terminations.<br />

· A knowledgeable Qwest employee will be selected to conduct the joint visit such as a SICM or<br />

delegated employee.<br />

· Appointments will be jointly scheduled.<br />

· The timeframe from application to completion of the joint visit will be discussed and determined as<br />

part of the joint planning development of this CR.<br />

· Records and billing will be corrected upon completion of the joint visit. Any prior monthly recurring<br />

adjustments will be based on the CLEC’s ICA.<br />

· Detailed planning prior to the visit will include review of all engineering records.<br />

· CPMC will coordinate the overall end to end process.<br />

We will schedule calls to jointly develop this process as requested. Qwest will provide a format of the newly<br />

proposed process, intervals, deliverables, and pricing. The CLEC community will have the opportunity to<br />

partner with Qwest in the development and finalization of the process. An amendment will be prepared for<br />

CLEC to participate in this new process offering.<br />

Sincerely,<br />

Stephen C. Nelson<br />

<strong>Product</strong> Management<br />

Qwest<br />

Cc: Ben Campbell<br />

Bill Campbell<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC092903-1<br />

Page 101 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC102303-1 10,000 lines billed on Summary BANs before<br />

opening a new Summary BAN.<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Resale, Unbundled<br />

Loop, UNE Loop,<br />

UNE-p, EEL (UNE-C)<br />

Currently, Qwest caps the number of lines billed on a Summary BAN at 2,500. Then it will close the existing BAN and open a new BAN. Eschelon<br />

processes each BAN separately for reconciliation, dispute and payment. For each Summary BAN Eschelon completes several tasks. Each new<br />

Summary BAN means we must duplicate these tasks, which is extremely time consuming. Eschelon asks Qwest to allow 10,000 lines per<br />

Summary BAN. Also Qwest needs to provide more than 30 days notice before opening a new Summary BAN.<br />

Expected deliverables. Qwest will add the maximum of 10,000 lines to each of our summary BANs before opening new ones.<br />

Status History<br />

10/23/03 CR Recieved<br />

10/24/03 CR Acknowledge<br />

11/03/03 Held Clarification Call<br />

11/10/03 Minutes sent<br />

11/19/03 - November <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

11/19/03 - Status changed to presented<br />

12/10/03 - Draft response issued<br />

12/17/03 -December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - Status changed to Evaluation<br />

1/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

1/21/04 - Status changed to Development<br />

2/2/04 - Qwest initiated notice PROS.02.02.04.F.01294.CRIS_V24<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

3/3/03 - Qwest initiated notice PROS.03.03.04.F.01425.FNL_CRIS_V24<br />

Project <strong>Meeting</strong>s<br />

Burson, Sue<br />

Stichter, Kathy<br />

Kriebel, Sue<br />

Andreen, Doug<br />

Development<br />

12/17/03<br />

Originator Company Name:<br />

Eschelon<br />

Report Line Number<br />

<strong>Product</strong>s<br />

Impacted<br />

2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Sue Kriebel, Qwest said that an MCC notice has been issued to the centers reinforcing the minimum three day notice that Qwest must give the<br />

CLECs before opening a new BAN. Further, the PCAT covering the 6,000 limit per BAN will be published 3/18. This CR will stay in Development.<br />

--------------------------------------------------------------<br />

1/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Sue Kriebel, Qwest answered three action items from the last meeting. First she explained that the 6,000 cap on BANs refers to sub-accounts and<br />

that there can be many lines under a sub-account. Second, there is only one active BAN at a time and that re-activating an account is a manual<br />

process. If a BAN is re-activated there will still be only one active BAN. Lastly, regarding the minimal time to notify a CLEC of a new BAN, she will<br />

send out notification to reinforce this standard. Sue also said PCAT changes would be forthcoming on the new 6,000 limit. Carla Pardee, AT&T<br />

said that she thought CLECs would be notified when they are getting close to exhausting a BAN. Sue agreed but said this is the notification of a<br />

new BAN being activated. Connie Winston, Qwest added that the BAN takes into account the RSID, product and state. The CR will move to<br />

Development status.<br />

------------------------------------------------------------------------<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Sue Kriebel, Qwest reviewed the draft response increasing the lines per BAN to 6,000 from 2,000 without an increase to the current notification<br />

interval to open a new BAN. Liz Balvin, MCI clarified the existing process of when a BAN is close to the maximum that Qwest send a email to the<br />

CLEC with three days notice to open a new BAN. Carla Pardee, AT&T stated they have been getting one day notice. She further stated that<br />

6,000 is better than 2,000 and she would accept the response but that it is really not acceptable when dealing with large volumes. Sue said she<br />

would clarify the process to ensure three day notice. Sue explained that if we use the 6,000 limit by the time the BAN is closed we could have and<br />

have had 2,000 to 3,000 additions processed. Carla noted that AT&T has accounts that have exceeded the limit but have not been noticed. Sue<br />

explained that it depends on the type of product for instance UNE-L carries less processing risk than UNE-P because usage is on the UNE-P<br />

which makes it more complex. Kathy Stichter of Eschelon said she was ok with the 6,000 limit and that the time span was not an issue at<br />

Eschelon. Kathy asked what the difference was between a line and a sub-account? Sue took this as an action item. Later in the meeting Kathy<br />

asked if BANs previously closed that had less than 6000 lines could be re-opened. Sue Kriebel said she would investigate. The CR status was<br />

moved to Evaluation.<br />

-----------------------------------------------------------------------------<br />

11/19/03 Nov. <strong>CMP</strong> <strong>Meeting</strong><br />

Kathy Stichter - Eschelon presented this CR to increase the lines billed on Summary BANs from 2,000 to 10,000. She stated that each time a new<br />

BAN is opened Eschelon reviews, reconciles and handles dispute resolutions separately. Carla Pardee AT&T added that AT&T supports this CR.<br />

Liz Balvin - MCI said that MCI had submitted a CR sometime ago for this and it was denied. Liz stated she would like to see no limit on BANs, but<br />

that 10,000 is better than 2,000. Also, she has just submitted a similar CR requesting multiple BANs per product per state. Doug said the same<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

24<br />

PC102303-1<br />

Page 102 of 105<br />

Attachment D


SMEs will be looking at both CRs. Kathy stated she has 20 BANs in Minnesota for Resale alone and is trying to consolidate these. Carla added<br />

that the 2,000 restriction on BANs seems to be just recently enforced by Qwest. She has several that are over 2,000 lines and it never seemed to<br />

be a problem. Kathy agreed that it was not being enforced before. This CR will move to Presented status.<br />

---------------------------------------------------------------------------------<br />

Clarification <strong>Meeting</strong>: 3:00 p.m. (MDT) / Monday November 3, 2003<br />

1-877-521-8688<br />

1456160#<br />

PC102303-1 10,000 lines billed on Summary BANs before opening a new Summary BAN.<br />

Attendees:<br />

Name/Company:<br />

Carla Pardee, AT&T<br />

Kathy Stichter, Eschelon<br />

Doug Andreen, Qwest<br />

Kerri Waldner, Qwest<br />

Brenda Kerr, Qwest<br />

Cindy Macy, Qwest<br />

Wendy Thurnau, Qwest<br />

Paul Johnson, Qwest<br />

Anne Robberson, Qwest<br />

Lynn Loftus, Qwest<br />

Introduction of participants on the conference call was made and the purpose of the call discussed.<br />

Review Requested Description of Change:<br />

Doug read the CR description: Currently, Qwest caps the number of lines billed on a Summary BAN at 2,500. Then it will close the existing BAN<br />

and open a new BAN. Eschelon processes each BAN separately for reconciliation, dispute and payment. For each Summary BAN Eschelon<br />

completes several tasks. Each new Summary BAN means we must duplicate these tasks, which is extremely time consuming. Eschelon asks<br />

Qwest to allow 10,000 lines per Summary BAN. Also Qwest needs to provide more than 30 days notice before opening a new Summary BAN.<br />

Kathy Stichter - Eschelon said that entire process is extremely time consuming on the Eschelon side each time a new BAN is utilized.<br />

Carla Pardee – AT&T added that AT&T had been informed on short notice that they would have to close the existing BAN and begin using a new<br />

BAN.<br />

Anne Robberson - Qwest said she believed that the limit on BANs was a system restriction. She also stated that the limit is 2000 lines per BAN.<br />

Kathy and Carla both stated that they did not believe this to be true since they both have existing BANs with many more lines than 2,500.<br />

Kathy said that the number of BANs that are opened directly multiplies the process.<br />

Carla stated she was notified a week ago by Qwest’s billing department that they were exhausting BAN numbers.<br />

Kathy said she has 69 BANs for CRIS alone. She said ideally she would like to see one BAN per state and that she would like to see 45 if not 60<br />

days notice given before opening new BANs.<br />

Kerri Waldner - Qwest asked Kathy if she had any trends on how fast BANs were being exhausted. Kathy responded that she did not.<br />

Kathy added that a third issue (along with 1. The 2000 limit and 2. Insufficient advanced notification) is that it seems Qwest is just starting to<br />

enforce the line limit on BANs<br />

Confirm Areas & <strong>Product</strong>s Impacted<br />

Resale, Unbundled Loop, UNE Loop, UNE-P, EEL (UNE-C)<br />

Confirm Right Personnel Involved<br />

Correct personnel were involved in the meeting.<br />

Identify/Confirm CLEC’s Expectation<br />

Identified on initial CR: Allow 10,000 lines billed on Summary BANs before opening a new Summary BAN. Identified during call: Eschelon needs<br />

45 to 60 days’ notice before opening a new summary BAN.<br />

Identify any Dependent Systems Change Requests<br />

Eschelon would like the change applied to both CRIS and IABS.<br />

Establish Action Plan (Resolution Time Frame)<br />

Kathy will present for Eschelon at the November <strong>CMP</strong> meeting.<br />

Qwest Response<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC102303-1<br />

Page 103 of 105<br />

Attachment D


December 02, 2003<br />

For Review by the CLEC Community and Discussion at the December 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Kathy Stichter<br />

Senior Invoice Validation Analyst<br />

Eschelon Telecom<br />

SUBJECT: Qwest Change Request Response - CR # PC102303-1<br />

10,000 Lines billed on Summary BANs before opening a new Summary BAN<br />

After reviewing CR # PC102303-1, Qwest has determined that it will raise the current standard of 2,000 Sub Accounts per Summary BAN to 6,000<br />

Sub Accounts per Summary BAN. This is a business decision that was made that is sensitive to the request from the CLEC community to<br />

increase the size of the Sub Accounts per Summary BAN, but is also sensitive to the Qwest Billing SDC’s who have to manage the Summary<br />

Accounts.<br />

As to the second issue of requesting a 30 day notification prior to closing a Summary BAN cannot be accommodated. Once the Summary BAN<br />

has reached the 6,000 Sub Account limit, it will be closed and a new Summary BAN issued as is currently done. To continue to leave the<br />

Summary Account open for an additional 30 days to notify the CLEC after it has reached the Sub Account limit would continue to increase the<br />

number of Sub Accounts posting to the Summary BAN to an unacceptable level before it could be closed.<br />

Sincerely,<br />

Carl Sear<br />

Sr. <strong>Process</strong> Analyst<br />

Qwest Communications<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

CR #<br />

PC102303-1<br />

Page 104 of 105<br />

Attachment D


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC030204-2 Qwest will red line and provide the changes<br />

made to the SGAT, Amendments and<br />

Negotiation Template in its <strong>Process</strong> notices.<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc<br />

Eschelon requested and Qwest implemented a red line process to notify CLECs of changes to documents and/or PCATs. However, Qwest does<br />

not use this red line method or any method to identify changes it is making on SGAT, Amendment or Negotiation Template process notices.<br />

Eschelon asks that Qwest red line and provide CLECs with the changes being made in these documents. A CLEC should not have to do a<br />

comparison of documents to identify the process changes Qwest is making in the Qwest notices. A CLEC is required to do a comparison to<br />

determine the changes that have been made because Qwest does not provide a record of the changes.<br />

Expected Deliverable:<br />

Qwest will send a red line attachment of changes along with the <strong>Process</strong> Notification for the SGAT, Amendment and Negotiation Template.<br />

Status History<br />

Retka, Mary<br />

Johnson, Bonnie<br />

Houston, Neil<br />

Macy, Cindy<br />

3/2/04 CR Submitted<br />

3/3/04 CR Acknowledged<br />

3/5/04 Contacted CLEC to schedule Clarification call<br />

Information Current as of:<br />

Report Name:<br />

Submitted<br />

3/2/04<br />

Originator Company Name:<br />

Eschelon<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

004 Detailed CLEC Initiated ProdProc OF FINAL ATTACH D<br />

Report Line Number<br />

CR #<br />

25<br />

<strong>Product</strong>s<br />

Impacted<br />

PC030204-2<br />

Page 105 of 105<br />

Attachment D


<strong>Product</strong> & <strong>Process</strong> Change Management <strong>Process</strong><br />

Attachment E – Qwest CR Summary List<br />

3/12/04 © <strong>2004</strong>, Qwest Corporation


Summary - Change Management <strong>Process</strong> (<strong>CMP</strong>) - <strong>Product</strong> & <strong>Process</strong><br />

Qwest Initiated CRs<br />

Report Line<br />

Number<br />

CR # Title Company Current Status Owner Director CR PM<br />

1 PC021204-1 Port In and Add New Non Ported Tn(s) on same LSR Qwest<br />

Pending Wells, Susie Bliss, Susie Sanchez-Steinke,<br />

Communications Withdrawal<br />

Linda<br />

2 PC012604-1 LSR Rejects with RPON Qwest<br />

Presented Robberson, Huff, Loretta Macy, Cindy<br />

Communications<br />

Anne<br />

3 PC090203-1 Define criteria for use of CFLAG/PIA field Qwest<br />

Communications<br />

Development Martain, Jill Schultz, Judy Macy, Cindy<br />

4 PC103103-1 Buried service wire/placing/Conduit/Technician interface Qwest<br />

Development Tallman, Retka, Mary Andreen, Doug<br />

with end user<br />

Communications<br />

Shirley<br />

5 PC103103-2 Binding Post information Qwest<br />

Development Tallman, Retka, Mary Andreen, Doug<br />

Communications<br />

Shirley<br />

6 PC111003-1 Reserved TN Procedure Qwest<br />

Communications<br />

Development Dimmitt, Jan Burson, Sue Andreen, Doug<br />

7 PC010604-1 Grandparent DSL Pro USOCs. Qwest<br />

Pending Van Dusen, Campbell, Bill Sanchez-Steinke,<br />

Communications Withdrawal Janean<br />

Linda<br />

8 PC010704-2 Eliminate Analog Private Line USOCs from Qwest’s offering Qwest<br />

Development Van Dusen, Campbell, Bill Andreen, Doug<br />

Communications<br />

Janean<br />

9 PC010704-3 Eliminate certain Voice Feature USOCs from Qwest’s Qwest<br />

Development Van Dusen, Campbell, Bill Sanchez-Steinke,<br />

offering.<br />

Communications<br />

Janean<br />

Linda<br />

10 PC010704-4 Eliminate Access Line USOCs from Qwest’s offering Qwest<br />

Development Van Dusen, Campbell, Bill Macy, Cindy<br />

Communications<br />

Janean<br />

11 PC020404-1 Grandparent Measured Service Plans in South Dakota, Bus Qwest<br />

Development Van Dusen, Campbell, Bill Andreen, Doug<br />

and Res<br />

Communications<br />

Janean<br />

12 PC020404-2 Grandparent Measured Service Plans in Minnesota, Bus Qwest<br />

Presented Van Dusen, Campbell, Bill Sanchez-Steinke,<br />

and Res<br />

Communications<br />

Janean<br />

Linda<br />

Information Current as of: Friday, <strong>March</strong> 12, <strong>2004</strong> Page 1 of 2<br />

Report Name: 005 Summary Qwest Initiated FINAL ATTACH E<br />

Attachment E


Report Line<br />

Number<br />

CR # Title Company Current Status Owner Director CR PM<br />

13 PC020404-3 Grandparent Measured Service Plans in Utah, Bus and Res Qwest<br />

Presented Van Dusen, Campbell, Bill Macy, Cindy<br />

Communications<br />

Janean<br />

14 PC020404-4 Grandparent ValueChoice, 2-Line ValueChoice , and Qwest<br />

Presented Van Dusen, Campbell, Bill Andreen, Doug<br />

PrivacyPak<br />

Communications<br />

Janean<br />

15 PC022604-1 Elimination of ATM USOCs Qwest<br />

Clarification Van Dusen, Campbell, Bill Sanchez-Steinke,<br />

Communications<br />

Janean<br />

Linda<br />

16 PC050503-2 Grandfather SVDS in all state tariffs including FCC tariff. Qwest<br />

Development Van Dusen, Campbell, Bill Macy, Cindy<br />

Communications<br />

Janean<br />

17 PC050703-6 Grandfather Measured Service plans in CO, ID North, NM, Qwest<br />

CLEC Test Van Dusen, Campbell, Macy, Cindy<br />

ND<br />

Communications<br />

Janean William<br />

18 PC120303-3 Grandparent Interstate SHNS and SST USOCs Qwest<br />

CLEC Test Van Dusen, Campbell, Bill Macy, Cindy<br />

Communications<br />

Janean<br />

Information Current as of: Friday, <strong>March</strong> 12, <strong>2004</strong> Page 2 of 2<br />

Report Name: 005 Summary Qwest Initiated FINAL ATTACH E<br />

Attachment E


<strong>Product</strong> & <strong>Process</strong> Change Management <strong>Process</strong><br />

Attachment F – Qwest CR Detail Reports<br />

3/12/04 © <strong>2004</strong>, Qwest Corporation


Open <strong>Product</strong>/<strong>Process</strong> CR Detail<br />

CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC021204-1 Port In and Add New Non Ported Tn(s) on<br />

same LSR<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Ordering,<br />

Provisioning<br />

Resale, UNE-P<br />

This CR will streamline the Port In <strong>Process</strong>. Qwest will add a new scenario to existing Port In <strong>Process</strong>es which will allow the CLEC to place a Port<br />

In Request, and add additional new non ported tn(s) on the same LSR. The benefit to the CLECs is more timely and accurate completion of<br />

requests. The benefit to Qwest is more timely and accurate completion of a request.<br />

Expected Deliverable:<br />

Revision to the current process of submitting two separate LSRs for porting in and adding new lines at the same time for the same end user.<br />

Would like April time frame. Update to Port In PCAT will be necessary to add scenario for new process.<br />

Status History<br />

Bliss, Susie<br />

Wells, Susie<br />

Wells, Susie<br />

Sanchez-Steinke, Linda<br />

02/12/04 - CR Submitted<br />

02/16/04 - CR Acknowledged<br />

02/19/04 - Held Clarification <strong>Meeting</strong><br />

02/19/04 - CR status updated to Pending Withdrawal<br />

Information Current as of:<br />

Report Name:<br />

Pending<br />

Withdrawal<br />

2/19/04<br />

Originator Company Name:<br />

Report Line Number<br />

Qwest Communications<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

1<br />

<strong>Product</strong>s<br />

Impacted<br />

PC021204-1<br />

Page 1 of 32<br />

Attachment F


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC012604-1 LSR Rejects with RPON Presented Wholesale ProdProc Ordering Resale, Unbundled<br />

2/18/04<br />

Loop, UNE-P<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Establish a process on how RPONs should be handled when a reject condition exists on one or more the related LSRs.<br />

Expected Deliverable:<br />

Qwest currently does not have a documented process on how LSRs that are related with RPON should be handled when a reject condition exists<br />

on one or more of the LSRs. Qwest is proposing the following process: LSRs that are due dated the same day and are RPON’d, will reject all.<br />

LSRs submitted where processing one or more is dependent on processing the other(s) will all be rejected. Qwest will further define this statement<br />

with further research.<br />

Status History<br />

Huff, Loretta<br />

Robberson, Anne<br />

Robberson, Anne<br />

Macy, Cindy<br />

Originator Company Name:<br />

01/26/04 - CR Submitted<br />

01/28/04 - CR Acknowledged<br />

1/30/03 - Contacted originator and discussed CR<br />

2/10/04 - Posted CLEC input meeting on calendar for <strong>March</strong> 2, <strong>2004</strong><br />

2/18/04 -Feb <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the project meeting section<br />

Report Line Number<br />

Qwest Communications<br />

<strong>Product</strong>s<br />

Impacted<br />

Project <strong>Meeting</strong>s<br />

February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Anne Robberson – Qwest advised this is a new CR that is addressing a process that is not handled consistently and not currently documented.<br />

This CR was created as a result of a CLEC inquiry. Qwest is in the process of documenting the Draft <strong>Process</strong> and will review this with the CLECs<br />

the first week in <strong>March</strong>. Bonnie Johnson – Eschelon asked if the process would be sent out prior to the meeting. Cindy Macy – Qwest advised<br />

that a meeting notification would go out with the process attached. The intent of the meeting is to review the process and gather input from the<br />

CLECs. This CR will move to Presented Status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC012604-1<br />

Page 2 of 32<br />

Attachment F<br />

2


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC090203-1 Define criteria for use of CFLAG/PIA field Development Wholesale ProdProc Provisioning INP, Centrex, LNP,<br />

10/15/03<br />

Private Line, Resale,<br />

Unbundled Loop,<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Schultz, Judy<br />

Martain, Jill<br />

Martain, Jill<br />

Macy, Cindy<br />

Description Of Change<br />

Per discussions held with the CLEC Community, Qwest is submitting this CR as a Level 4 <strong>Process</strong> Change to define the criteria when the<br />

CFLAG/PIA fields are most commonly used. The following list can be used as a starting point for discussions with the CLECs:<br />

Change Flags (CFLAG)<br />

The CFLAG is used to communicate changes Qwest made on the service order that are different from what was requested on the original LSR.<br />

These changes are a result of two different conditions:<br />

1. Changes that occurred as a result of a verbal directive from you.<br />

1. Changes due to processing requirements within Qwest.<br />

Originator Company Name:<br />

When the CFLAG is marked, the Remarks section of the FOC contains text indicating any deviations from the original request. Examples of some<br />

of the uses of CFLAG in each of the preceding areas are as follows:<br />

- Changes that occurred as a result of a verbal directive from you when no supplement is sent:<br />

- On the DD, you request a Connecting Facility Assignment (CFA) slot change when the assigned slot is unavailable.<br />

- On the DD, you called and requested a verbal DD change.<br />

- You called and requested a verbal supplement as a result of a non-fatal error.<br />

- You called and requested a verbal supplement because a SUP 1 (Cancel) or SUP 2 (Desired Due Date (DDD) change) cannot be submitted due<br />

to a system (either yours or Qwest's) outage or limitation.<br />

- Changes that occurred as a result of the processing requirements within Qwest include the following:<br />

Report Line Number<br />

Qwest Communications<br />

- If special characters (i.e., a virgule "/" appears in specific fields such as the PON) that are not allowed in Qwest’s Service Order <strong>Process</strong>ors<br />

(SOP) are included on the service request, they will be changed to dashes to allow the request to process.<br />

- Whenever Qwest cannot use the DDD on the LSR as the DD. Examples include a DDD that did not meet standard interval requirements or the<br />

LSR requested an invalid DD such as a Sunday or Holiday.<br />

- The Summary Billing Account Number (BAN) is incorrect on the LSR and Qwest provides the correct BAN information on the FOC.<br />

- For LSRs with Requisition Type and Status of CB (Local Number Portability (LNP)) and BB (Unbundled Local Loop/LNP) that have the ported TN<br />

in the Account Number (AN) field instead of the main AN, Qwest will process the order (porting the requested TN) using the main AN and will<br />

provide the correct AN of the FOC.<br />

- When the LSR is requesting a feature and an additional USOC/feature is also required in order to provision the service correctly, Qwest adds the<br />

appropriate USOC/feature on the service order. This change is only made if Qwest has not provided the ordering rules externally. As trends are<br />

identified, Qwest will either make process changes and/or update the PCAT, as appropriate.<br />

- When the Coordinated Hot Cut (CHC) field equal "N" (or blank) and the Appointment Time (APPTIME) and Desired Frame Due Time (DFDT)<br />

fields are populated, Qwest will ignore the information in the APPTIME and DFDT fields because they are not required.<br />

- If the LSR requests a dispatch, but dispatch is not required for provisioning and you have not requested the service be "tagged", Qwest will not<br />

dispatch a technician because it was not necessary.<br />

- If during processing of a LSR Qwest determines that the TN entered on the LSR is not available, Qwest will provide a new TN.<br />

<strong>Product</strong>s<br />

Impacted<br />

- If the address entry is a minor deviation from Qwest PREMIS address data (e.g., LSR uses "suite" and PREMIS uses "unit"), Qwest will use the<br />

information in PREMIS.<br />

- If you set the Manual Indicator (IND) to "Y" and service order affecting information in the Remarks field causes a mismatch in field-to-field<br />

comparison, Qwest will use the information in the Remarks field to process the order.<br />

Expected Deliverable:<br />

To create a mutually agreed upon list of reasons when the CFLAG/PIA field would be checked on the LSR and document that criteria in the<br />

Ordering PCAT located on the Qwest external web site.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC090203-1<br />

Page 3 of 32<br />

Attachment F<br />

3


Status History<br />

09/02/03 - CR Submitted<br />

09/04/03 - CR Acknowledged<br />

9/8/03 - Contacted Jill Martain and held clarification call<br />

9/17/03 - Sep <strong>CMP</strong> meeting notes will be posted to the database<br />

9/18/03 - Sent Notification offering 3 options for CLEC Input <strong>Meeting</strong><br />

9/23/03 - Selected Oct 1 9:00 - 11:00 meeting time for CLEC Input <strong>Meeting</strong> - notification distributed.<br />

10/1/03 - Held CLEC Input <strong>Meeting</strong> and agreed to schedule another Ad Hoc call the last week in October<br />

10/13/03 - Sent notification for CLEC Ad Hoc meeting scheduled on October 30 from 10:00 - 11:00<br />

10/15/03 - Oct <strong>CMP</strong> meeting minutes will be posted to the database<br />

10/30/03 - CLEC Ad Hoc meeting held to review CFLAG/PIA matrix<br />

11/6/03 - Received input from Eschelon on matrix<br />

11/7/03 - Received input from MCI on matrix<br />

11/19/03 - Nov <strong>CMP</strong> meeting minutes will be posted to the database<br />

12/5/03 - Schedule CLEC ad hoc meeting to review CFLAG/PIA codes and reasons (12/15)<br />

12/8/03 - <strong>CMP</strong>R.12.08.03.F.01149.CFLAG_PIA_MTG<br />

12/15/03 - Held CLEC ad hoc meeting to review PIA matrix<br />

1/2/04 - Notification distributed for next CLEC meeting on 1/9/03<br />

1/9/03 - Held CLEC ad hoc meeting to review PIA matrix<br />

1/21/03 - Jan <strong>CMP</strong> meeting minutes will be posted to the database<br />

2/18/04 -Feb <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the project meeting section<br />

2/26/04 - Held CLEC ad hoc meeting<br />

Project <strong>Meeting</strong>s<br />

_________________________________________________________________________________________________<br />

PC090203-1 CFLAG/PIA<br />

Ad Hoc <strong>Meeting</strong> PIA14<br />

February 26, <strong>2004</strong><br />

In attendance:<br />

Linda Miles – Qwest Kim Isaacs – Eschelon<br />

Cindy Schwartze – Qwest Bonnie Johnson – Eschelon<br />

Crystal Soderlund – Qwest Jill Martain – Qwest<br />

Cindy Macy – Qwest<br />

Cindy Macy – Qwest opened the call and reviewed the agenda. During this call Qwest will review the current process, as Qwest understands it,<br />

and gather input and concerns from the CLECs.<br />

Cindy Schwartze – Qwest explained the current process was effective August 2003 with the IMA release. This process is for N and T 1 LSR for<br />

voice and Qwest DSL. When you are ordering DSL with voice, the address has to pass Loop Qual for flow through. If the address qualifies, then<br />

we would accept the LSR, and issue the Service Order to provision the request. If the address does not qualify, then the LSR for voice and Qwest<br />

DSL would be rejected upfront by IMA.<br />

In the event the DSL line can’t be provisioned and the order issued is for DSL and voice, we then follow the Retail provisioning process. We go<br />

ahead and provision the voice, send an FOC with a CFLAG saying that the data portion can not be provisioned. Cindy Schwartze – Qwest<br />

explained the volume is very low, and that we only have knowledge of this occurring once.<br />

Crystal Soderlund – Qwest reviewed the Line and Loop Splitting process. This process was put in place in June 2001. The UNE P request is<br />

submitted, if the LSRs have the same due date and the DSL is available, Qwest will issue a pending order change to the UNE-P service to add<br />

the DSL. If the data portion cannot be provisioned, Qwest would allow the voice LSR to get provisioned. The Line Splitting LSR would follow the<br />

Held Order process. Crystal did not remember seeing this occur in production. With 15.0 IMA Qwest is offering the process to provision the 2<br />

requests on 1 LSR. The CLEC may need to issue another LSR to condition the line. Loop Splitting will mirror Line Splitting.<br />

Bonnie said we are not talking about a situation when you order line conditioning. We are talking about when you can’t provision DSL. In this case<br />

it should follow the standard process when you order a feature and it is not available. Qwest should reject the order, as that is what is done when<br />

a feature is not available. If we can’t have the DSL then we don’t want the voice. We have no use for just the voice line. This is in conflict with the<br />

Qwest reject process. Bonnie advised that the CLECs want to receive a Jeopardy notification and it should identify if DSL can’t be provisioned at<br />

all or if it needs to be conditioned. Qwest considers DSL a feature in other areas. It should be treated as a feature.<br />

Crystal Soderlund – Qwest thanked Bonnie for helping us understand the issues. Crystal explained when the LSR is received the centers process<br />

the order. At that time we don’t know if the facility is DSL compatable. Crystal asked for clarification that the CLEC’s are really asking for Qwest to<br />

notify the CLECs with a Jeopardy notice and give 4 hours to respond? Bonnie asked if the SDC does not check to see if DSL is available? Crystal<br />

advised no, it is assumed the CLEC has done that up front, before the LSR is sent in. Bonnie asked what point in time is it determined when the<br />

DSL is not available? Crystal advised that the downstream organization contacts the SDC to remove the DSL. Bonnie said that Qwest should<br />

jeopardy the order at that time.<br />

Crystal said the ILECs should check to make sure the line can handle DSL and IMA also does a check. For example, if CLEC doesn’t loop qualify,<br />

then IMA should do a check right away and reject the order. This is why we don’t think this happens very much. Bonnie said if the line doesn’t<br />

qualify then we do not order the line. If it required line conditioning we do a separate order after the line goes in. So, why do we have a PIA value<br />

to accommodate this, if it doesn’t happen very often? Bonnie said it should be rejected.<br />

Crystal advised that the reject reason isn’t always clear to the SDC, so she requested a PIA value to provide more details. Bonnie advised that the<br />

CLECs would like to be able to have a choice on whether to accept, reject or jeopardy the order. Otherwise, if Qwest just removes the data and<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC090203-1<br />

Page 4 of 32<br />

Attachment F


installs the voice, then the CLEC would be liable for Non Recurring charges and 30-day billing in situations where they may have chosen otherwise<br />

to cancel the request. Her preference was to receive the jeopardy notice and then make the appropriate decision. Bonnie understands if we do<br />

follow the jeopardy process a sup or new LSR may be required and the standard interval would be followed.<br />

Bonnie advised the CLEC community would prefer to have an option. They would like for Qwest to jeopardy the LSR and follow the current<br />

jeopardy process. The CLEC would have 4 hours to respond or the LSR would be cancelled. In this case there would not be a need for PIA 14.<br />

Bonnie advised she would check with the other CLECs to make sure this represents their needs. If there are concerns, Bonnie will send an email<br />

to Cindy Macy.<br />

Cindy Macy advised that the team will meet internally to review the request and determine the impacts to this process. Qwest will provide status or<br />

schedule another meeting to discuss the results.<br />

_______________________________________________________________<br />

February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Jill Martain – Qwest advised the PCAT was published and comments were addressed. This closed January 28, <strong>2004</strong>, effective <strong>March</strong> 3, <strong>2004</strong>.<br />

Subsequent FOC was addressed. There will be a CLEC meeting to discuss PIA 14 on February 26, <strong>2004</strong>. Stephanie Prull – Eschelon was in the<br />

15.0 walkthrough meeting yesterday and realized that there would be an Order Level PIA and an LSR Level PIA. Stephanie advised this was<br />

never discussed in any of the PIA meetings. Qwest was able to page Denise Martinez-Qwest to join the call. Denise and Jill explained this is the<br />

way PIA is being implemented, opposed to the content or meaning of the PIA value. Denise and Jill advised this would allow Qwest to be specific<br />

with the correct level of PIA. Some PIA values are related to a BAN so that would be at an LSR level, and some PIA values are related to a Due<br />

Date or TN change so that would be at an Order level. Stephanie advised she understand the functionality and she agrees that it makes sense to<br />

implement it this way, but she was not aware of how she missed the way this was going to be implemented. Her understanding is that there would<br />

be multiple values, but not multiple fields or segments. Bonnie Johnson – Eschelon asked if the multiple PIA values are at different levels for the<br />

same PIA reason? This relates to PO20 impacts. Denise Martinez – Qwest advised it is a means for us to apply the value most accurately. It<br />

would not increase the amount of other PIAs. Jill Martain – Qwest advised that you might have LSR level PIA and then PIA values on the orders<br />

that are created from the LSR. Stephanie Prull – Eschelon advised our vendor does not support this so we will not be able to implement. Connie<br />

Winston – Qwest advised this is the CR in 15.0 for ‘Multiple PIA Values’. Bonnie Johnson – Eschelon said we never discussed order versus LSR<br />

level. We were under the impression that PIA was PIA – no different between order and LSR levels. Connie Winston – Qwest asked if we can<br />

provide a comment on the draft Tech Specs and then we will provide a response the to comment. Stephanie Prull – Eschelon advised she already<br />

submitted it as a comment and that this would be fine to handle it this way, instead of holding an ad hoc meeting. This CR will stay in<br />

Development Status.<br />

_____________________________________________________________<br />

January 21, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Jill Martain – Qwest advised that we had an ad hoc meeting with the CLEC and agreed to send the matrix documentation out. We agreed to omit<br />

PIA 14 from the matrix. The documentation will be distributed in two phases. The first phase will identify the PIA value definitions that are<br />

effective today. The second phase will be the additional PIA values added with 15.0 on April 19. Jill explained that we discussed PIA 14 and this<br />

was referred to the <strong>Product</strong> team. A CR should be issued this month to take care of this. Blocking will be discussed tomorrow in the systems<br />

meeting. Bonnie Johnson – Eschelon advised that the problem is that Qwest requires CLECs to send in the end state, opposed to adds and<br />

deletes. This causes a recap, and recaps don’t appear on the PSON. Bonnie advised it wasn’t disclosed that there were going to be exceptions to<br />

the PSON. It is good that it is on the service order. The CLECs wanted to discuss tomorrow in the systems meeting whether the recap on all the<br />

listing information will also fix this problem.<br />

______________________________________________________________________<br />

Ad Hoc <strong>Meeting</strong> PC090203-1<br />

In Attendance:<br />

Bonnie Johnson – Eschelon<br />

Phyliss Burt – ATT<br />

Jill Martain – Qwest<br />

Kim Isaacs – Eschelon<br />

Linda Harmon – Qwest<br />

Donna Osborne Miller – ATT<br />

Carla Pardee – ATT<br />

Liz Balvin – MCI<br />

Nancy Sanders – Comcast<br />

Ray Smith – Eschelon<br />

Cindy Macy – Qwest<br />

Cindy Macy – Qwest opened the call and advised the team will be reviewing the CFLAG/PIA matrix and the updates that were made based on<br />

previous meetings with the CLECs.<br />

Jill Martain – Qwest explained that because we have reviewed the matrix before, she would ask the CLECs if they have comments or questions on<br />

each item, opposed to reading each item. This way we will discuss only the items that the CLECs have questions about.<br />

Discussion occurred on the following items / topics:<br />

Adding a mini definition section to help clarify terms (subsequent FOC)<br />

PIA 5 – subsequent FOC<br />

PIA 8 – update to identify this will be used in 13/14.0.<br />

PIA 11 – Jill clarified #11 and Bonnie’s comments. Jill advised she agrees with Bonnie’s comment as both of them are saying the same thing.<br />

Phyllis Burt – ATT asked how would the customer get a PIA 11. Jill advised if the same reserved TN# was used mutiple times an we have to<br />

reassign a new TN. Work is going on to improve this process. Phyllis also clarified Bonnie’s comment.<br />

PIA 14 – Jill explained she understands Bonnie’s concern about needing to document the process. Jill explained this is Qwest’s existing process.<br />

Bonnie advised she is open to the process of sending a jep notice and to complete the voice part, but she would like to discuss how this process<br />

should work. Jill asked if she can explain the issue to the <strong>Product</strong> team and have them take care of this issue, as she is not the process person<br />

for this process. Bonnie agreed that would be okay. Bonnie explained her concern is that Qwest is trying to create a process with a PIA, opposed<br />

to creating the process first and using a PIA as part of the process. Jill agreed to omit PIA 14 from the matrix initially. Jill will issue the notice and<br />

matrix to publish this information and omit PIA 14.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC090203-1<br />

Page 5 of 32<br />

Attachment F


Jill discussed the blocking question. Jill explained that it is recapped on the service order but it is not visable to the CLECs. Jill advised a CR<br />

could be opened to change this. Bonnie advised that we can discuss this at <strong>CMP</strong> (systems meeting).<br />

Bonnie advised she appreciates Jill’s analysis of the PIA values and data. Bonnie still would prefer to have a more expanded PIA value list.<br />

Bonnie hopes that the use of PIA 4 decreases with this CR. Eschelon will continue to monitor the use of PIA. Liz Balvin – MCI agreed that we<br />

need to continue to review the information in remarks and create a new PIA value if necessary.<br />

Bonnie asked if the new PIA values will be effective with 15.0. Jill advised yes.<br />

Next Steps<br />

Publish documentation / matrix<br />

__________________________________________________________________<br />

December 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Jill Martain – Qwest advised that the team met and reviewed the PIA Matrix on December 15. Qwest agreed to make additional updates to the<br />

matrix. Liz Balvin – MCI verified that Qwest will clearly distinguish between LSR and Service Order activity and FOC and subsequent FOC in the<br />

document. Jill agreed those updates / clarifications would be made. Jill asked the CLECs if they would like to have another meeting or if the<br />

matrix is okay to be published. Liz Balvin – MCI and Bonnie Johnson – Eschelon advised they would like to have another meeting as they did<br />

request additional unique PIA values around Blocking. Jill advised she is working on the two issues that were brought up at the Ad Hoc <strong>Meeting</strong><br />

(Blocking and PIA14 Data Portion not provisioned). The team will discuss these at the next meeting. Cindy Macy – Qwest agreed to schedule a<br />

meeting for January 5 or 9. Bonnie expressed her concern that the CLECs did request additional specific PIA values that were not included in the<br />

matrix. Jill explained that she has tried to include all the scenarios that were discussed and the concern with having too many PIA values is that it<br />

becomes unmanageable and the centers would not use all of the values. This CR will remain in Development Status.<br />

_______________________________________________________________<br />

December 15, 2003 Ad hoc meeting<br />

PC090203-1 CFLAG/PIA<br />

Ad Hoc meeting<br />

In Attendance:<br />

Julie Pickar – US Link<br />

Kim Isaacs – Eschelon<br />

Ray Smith – Eschelon<br />

Stephanie Prull – Eschelon<br />

Carla Pardee – ATT<br />

Jill Martain – Qwest<br />

Cindy Macy – Qwest<br />

Colleen Sponseller – MCI<br />

Liz Balvin – MCI<br />

Bonnie Johnson – Eschelon<br />

Jill Martain – Qwest advised she has updated the matrix based on investigations and previous meetings. Jill advised there is a large list of PIA<br />

values and it is very hard for Qwest to manage so many different values. As an example, we have combined some PIA 4 reasons into one code.<br />

Bonnie Johnson – Eschelon asked about 20% of training issues identified in the matrix? Was the PIA field used inaccurately? Jill Martain –<br />

Qwest advised some were unclear selections and training will help. This is an example of how too many PIA values become hard to manage.<br />

Liz Balvin – MCI asked about subsequent FOCs as there is no such notifier. Jill Martain – Qwest advised if there is something missing Qwest will<br />

send a jep after the FOC. If Qwest makes an error and there is nothing to correct than Qwest will send another FOC with the correct PIA<br />

information. This is done on a Qwest typo error. Steph Prull – Eschelon advised their systems don’t look at the second FOC. So any updates<br />

on second FOC are not updated. Jill explained this is not new, it has always been the process. The CLECs asked if this is in the PCATs. Jill<br />

advised CFLAG was created to accommodate these situations so that is the purpose of CFLAG. Jill advised PIA is an industry standard. The<br />

industry only has four values.<br />

Bonnie Johnson – Eschelon asked about due date change by Qwest. Bonnie asked why can’t there be a different PIA value for each of these due<br />

date changes. Jill advised this created the possibility of error and the ‘reason change’ is the same. Jill is very concerned about the number of<br />

different values.<br />

The team agreed the next steps are to make changes to the document and then meet again to review. Liz wanted to make sure the changes<br />

would specify when Qwest felt it was appropriate to make changes. Specifically, Liz requested Qwest to identify if it was a change made from the<br />

CLEC LSR to Service Order or whether it was a change made to correct an error identified on the FOC notification . Jill agreed those changes<br />

would be included.<br />

______________________________________________________________________________________________________________________<br />

________________________<br />

November 19, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Jill Martain – Qwest advised that she received comments from the CLECs regarding the last matrix that was distributed. Jill is in the process of<br />

providing a response to those issues. In addition, as a result of those comments and internal discussions the list is growing and there is concern<br />

about the number of values Qwest could be requiring our centers to manually review and accurately select. Jill will take another look at the most<br />

commonly used reasons and the CLEC feedback and provide a final proposal to the CLEC community hopefully, within the next week.<br />

Lastly, there was discussion around retrofitting the multiple values and additional PIA values into the 13.0 and 14.0 releases. Since it has not been<br />

the practice to retrofit new changes into earlier EDI versions, Qwest does not plan to pursue retrofitting new PIA functionality into earlier EDI<br />

versions. However, Qwest is still looking into options of adding any new PIA values into the 15.0 release.<br />

_____________________________________________________________________________________________<br />

CLEC Ad Hoc <strong>Meeting</strong><br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC090203-1<br />

Page 6 of 32<br />

Attachment F


PC090203-1 CFLAG / PIA<br />

October 30, 2003<br />

In attendance:<br />

Julie Pickar – US Link<br />

Liz Balvin – MCI<br />

Kim Isaccs – Eschelon<br />

Ray Smith – Eschelon<br />

Jill Martain – Qwest<br />

Jenn Arnold – US Link<br />

Jackie Debold – US Link<br />

Denise Martinez – Qwest<br />

Cindy Macy – Qwest<br />

Cindy Macy – Qwest opened the call and explained we will review the matrix, make updates and determine next steps. Cindy confirmed that the<br />

users had copies of the matrix.<br />

Jill Martain – Qwest reviewed the PIA numbers and reasons. Discussion took place on several of the PIA values and reasons. See below.<br />

PIA 4/15 – MCI requested that Qwest validate that this is in the disclosure document and this may create an out of sync condition. Liz advised she<br />

would like the business rules to be clear in the disclosure document. If the centers are using PIA 15 they would also notify the process specialist<br />

so we can be sure we review and correct the reason that we are using PIA 15.<br />

Address Validation –MCI advised that different address systems are used to validate different forms or requests. Please be specific on PIA 4 as to<br />

which address system is being checked.<br />

Remarks field can cause a mismatch. The request was that Qwest would monitor PIA 4 and Other to improve the reason that is causing us to use<br />

PIA 4.<br />

The CLECs advised they will need to review this matrix with their coworkers to gather input. Jill asked the CLECs to get back to Cindy Macy at<br />

cynthia.macy@qwest.com to confirm that the PIA reasons are acceptable. After that, Jill would pursue obtaining new PIA values.<br />

Jill explained that to implement these changes there are process and documentation changes, system changes are needed to assign new PIA<br />

values, and the request to retrofit the 15.0 changes into 13/14.0 releases require an exception meeting.<br />

__________-__________________________________________________________________________________________<br />

October 15, 2003 <strong>CMP</strong> meeting minutes<br />

Cindy Macy – Qwest provided status for Jill as she is on vacation this week. Cindy advised the CLECs met October 1, 2003 to review the current<br />

use of CFLAG/PIA. During the Ad Hoc meeting Jill explained the reasons we use each CFLAG/PIA and the team began to further define<br />

acceptable reasons for ongoing use of CFLAG/PIA. Bonnie Johnson advised she made a request at the Long Term PID meeting that the<br />

CFLAG/PIA changes planned for Release 15.0 also be incorporated into 13, 14 and 15.0. Cindy advised she will discuss this with Jill when she<br />

returns from vacation. Stephanie Prull – McLeod advised they are on 13.0 and it seems like the use of CFLAG/PIA in the system is different with<br />

13.0. Every time a conversion order that goes through autoflow, a PIA 12 (cus code change) is assigned. Stephanie advised McLeod is aware of<br />

the cus code changing so a PIA of 12 is not needed. This CR will move to Development Status.<br />

______________________________________________________________________________________________________________________<br />

_____<br />

CLEC Ad Hoc <strong>Meeting</strong><br />

PC090203-1 CFLAG/PIA<br />

October 1, 2003<br />

In attendance:<br />

Julie Pickar US Link<br />

James McClusky Accenture<br />

Liz Balvin MCI<br />

Steve Trana Launch Now<br />

Phyllis Burt ATT<br />

Mike Zulevic Covad<br />

Jill Martain Qwest<br />

Bonnie Johnson Eschelon<br />

Kim Issacs Eschelon<br />

Jennifer Arnold US Link<br />

Stephanie Prull McLeod<br />

Cindy Macy – Qwest opened the call and advised the purpose of this call is to review the current use of CFLAG/PIA and to determine new uses for<br />

CFLAG/PIA. Bonnie Johnson-Eschelon advised her goal is to create a finite list for use of PIA. Liz Balvin-MCI advised at a minimum the CLECs<br />

have to know how the field is being used. Jill Martain-Qwest advised she has concerns over loosing the ability to use PIA in an interim process or<br />

work around. Liz Balvin-MCI asked why wouldn’t Qwest reject the LSR instead of use PIA. Jill advised sometimes the better option is to use PIA,<br />

opposed to missing a due date. Liz said she understands as long as the CLEC is contacted and advised about the use of PIA.<br />

Jill explained CFLAG will be eliminated with 13.0 and PIA will be used 13.0 going forward. EDI 11 and 12 it is still valid. CFLAG and PIA terms<br />

are interchangeable.<br />

Bonnie advised CFLAG/PIA has direct impacts to PO20. If CFLAG is used it excluded the order from PO20. The use of CFLAG/PIA has to be<br />

limited. Bonnie wants to have an exhaustive list. If something is broken, then Qwest needs to fix the problem opposed to using CFLAG.<br />

Phyllis Burt ATT asked to explain the use of PIA 4 value of ‘other’. Bonnie explained this allows the CLEC to enter the LSR so it can be rejected.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC090203-1<br />

Page 7 of 32<br />

Attachment F


Qwest uses this field to notify CLECs of changes made to the order. It helps the order be processed.<br />

Jill Martain – Qwest went through the CR and discussed the current uses for PIA. Bonnie requested that we go through the information and ask<br />

that the CLECs have time to go back to their organizations to gather input, before we make final decisions on the use of PIA. The team agreed<br />

this was okay and that we would have another meeting to discuss our findings. Jill agreed she would create a matrix that identifies the reason to<br />

use PIA and identify which PIA would be used in each situation. This matrix should be available to review at the next CLEC Ad Hoc <strong>Meeting</strong>.<br />

The group discussed the PIA changes as a result of Verbal direction from CLECs, Changes due to processing requirements within Qwest,<br />

Changes for ‘other’ reasons and System limitations.<br />

Jill agreed to look at creating multiple PIAs for system limitations such as:<br />

DD change per CLEC<br />

DD changes per Qwest<br />

Cancel per CLEC<br />

Cancel per Qwest<br />

Verbal DD changes<br />

Delayed order condition causing DD change<br />

The CLECs expressed their concerns over system limitation PIAs. If Qwest talks to the CLECs and gets their approval it is more acceptable.<br />

Liz Balvin advised MCI does not subscribe to PSONs so the process can not be to notify via a PSON. Jill agreed to look at the Dispatch field and<br />

PIA 11 to make sure we understand how this is being used.<br />

Bonnie Johnson advised the address field is another area where we may want multiple PIA. Qwest should identify minor deviations on address<br />

data. Jill explained we need to create a manageable list of PIAs. Bonnie and Liz advised they would like to know what specifically changed on the<br />

address so they can fix it next time. Jill offered to create a PIA for address and include the specifics in the remarks. Liz was okay with this.<br />

Non fatal errors were discussed and agreed that these should be talked about further to identify situations when it would be used.<br />

PIA 15 Requested USOC was discussed. Jill advised PIA 15 is only used when the feature PCAT does not tell us what to do.<br />

Bonnie asked if PIA 3 could go away with 15.0. Jill agreed to check on.<br />

PIA 13 BAN change – optional field. What happens is we don’t populate it? Jill advised if BAN is populated with the incorrect BAN Qwest uses<br />

PIA to fix it. If BAN is blank we don’t use PIA.<br />

PIA 14 should be further defined. Jill will updated the matrix to further define PIA 14.<br />

PIA 8 goes away with Release 15.<br />

The CLECs will take PIA and review with their organizations. Jill will update the PIA matrix and we will discuss it during our next meeting.<br />

Bonnie sent in the following information as a result of CLEC discussions:<br />

The CLECs committed to hold a meeting and review 3 issues on this CR.<br />

1. Verbal sups on non fatal errors:<br />

* The CLECs collectively agree with Qwest (Char Mahs communicated<br />

Qwest will be sending a level 3 notice soon) that verbal sups should be<br />

allowed only when a sup is not possible due to a system or some other unique<br />

limitation.<br />

2. PIA #15 value to be implemented in 14.0<br />

* The CLEC community has a concern about this value.<br />

* How will the process for blocking and hunting impact this. Qwest<br />

process states that the USOC will no longer be required. Will every LSR with<br />

blocking requested (requiring a USOC) and hunting have a #15 value?<br />

* If so the CLECs would like a new value to apply to USOCs not<br />

required on the LSR and one for USOCs that are required. More discussion is<br />

needed on this.<br />

3. Can we eliminate the #4 "other" field?<br />

* The CLECs would like to develop the detailed value list and discuss<br />

at that point, however, the general consensus is that if we can create a<br />

total list we may be able to accomplish that.<br />

Some additional points:<br />

* CLECs want to ensure that the PIA field is not replacing any<br />

processes. The PIA field is merely Qwest defining the LSR/Service order<br />

mismatch and CLECs will not be required to use the PIA field will not<br />

communicate any data currently relayed to CLECs via other methods. For<br />

example, Qwest marks PIA value 12 because the customer code has changed.<br />

Qwest communicates the new customer code in remarks on the FOC. The CLEC<br />

will not need to now obtain the new customer code from the remarks field<br />

when they currently obtain the information through other means.<br />

* Will Qwest submit a special request to make all changes requested in<br />

this process in 15.0 and update 13.0 and 14.0 at that time?<br />

______________________________________________________________________________________________<br />

September 17, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC090203-1<br />

Page 8 of 32<br />

Attachment F


Jill Martain presented this CR and asked if Qwest could hold a CLEC Input meeting on 9-29-03 from 9 – 11:00 a.m. Liz Balvin-MCI advised<br />

Monday’s do not work for her. Cindy agreed to send a notification to offer 3 meeting options and then reschedule.<br />

______________________________________________________________________________________________________________________<br />

____________<br />

MEETING MINUTES<br />

Request to change Level 2 Notification PROS.07.28.03.F.01137.Provisioning_V27 to a Level 4 Change Request<br />

August 20, 2003<br />

CLEC-Qwest Conference Call<br />

<strong>Meeting</strong> Time: 1:00 – 2:00 PM MDT<br />

Purpose<br />

The purpose of the ad-hoc meeting was to determine how to move forward with implementing changes notified in<br />

PROS.07.28.03.F.01137.Provisioning_V27 and how to manage the CLEC requests that came in asking that this change be managed as a Level 4<br />

CR.<br />

Attendees<br />

Carla Pardee-ATT, Donna Osborne-Miller- ATT, Sharon Van Meter – AT&T, Mike Zulevic-Covad, Kim Isaacs-Eschelon, Bonnie Johnson-Eschelon,<br />

Bill Littler-Integra, Stephanie Prull-McLeod, Liz Balvin-MCI, Jennifer Arnold-US Link, Susan Lorence-Qwest, Jim Maher-Qwest, Jill Martain-Qwest,<br />

Judy Schultz-Qwest, Kit Thomte-Qwest<br />

<strong>Meeting</strong> Minutes<br />

Jim Maher-Qwest opened the meeting and explained that Qwest had issued a Level 2 notification PROS.07.28.03.F.01137.Provisioning_V27<br />

updating information associated with CFLAG processes. The notification had been issued as Level 2 because it was an update that included<br />

documentation concerning existing processes/products not previously documented. Jim explained that comments had been received from<br />

Cbeyond, Covad, Eschelon and MCI requesting that the CLECs be involved in developing the procedures and that this could be accomplished by<br />

handling this as a Level 4 CR.<br />

Jill Martain-Qwest proposed that the Level 2 change be implemented based on a request from the CLECs that this process should be more clearly<br />

documented. Martain stated that having the processes documented through the Level 2 notification might be more advantageous to all involved<br />

with this process, and that a Level 4 <strong>CMP</strong> CR could be opened to modify the process.<br />

Bonnie Johnson-Eschelon stated that Eschelon had an issue with posting the information provided in the Level 2 notification because Eschelon did<br />

not think the information represented what was happening with CFLAG. She further explained that Eschelon had raised concerns regarding<br />

CFLAG for some time and that they had concerns with PID impacts. Mike Zulevic-Covad and Liz Balvin-MCI also stated they were uncomfortable<br />

with the Level 2 language being implemented and agreed that this should be managed as a CR. Jill Martain stated that the language provided in<br />

the Level 2 notification could be the starting point for the CR. Bonnie Johnson agreed with that approach. Martain agreed to proceed with th CR,<br />

and stated there may be a short term and longer term CR associated with this work.<br />

The meeting adjourned.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC090203-1<br />

Page 9 of 32<br />

Attachment F


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC103103-1 Buried service<br />

wire/placing/Conduit/Technician interface<br />

with end user<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Field Technician <strong>Process</strong> changes for Service drop wire and/or conduit Placement:<br />

1. Field Tech is dispatched out to perform installation on a Wholesale order.<br />

2. Field Tech determines that an initial or additional drop is required.<br />

Wholesale ProdProc Odering,<br />

Provisioning<br />

Residence premises: Placing is required for initial or additional drop.<br />

Business premises: The property owner may be required to place conduit with pull-string for initial or additional drop placement.<br />

Unbundled Loop,<br />

UNE Loop, UNE-P,<br />

EEL (UNE-C)<br />

3.<br />

Non-design (ie, UNE-P)- Qwest Field Tech will contact CLEC to let them know about a jeopardy condition for placing of drop and/or conduit. The<br />

notification to CLEC is either direct to the CLEC contact or through a Voice Message. If the CLEC’s Voice Message is full, the Field Tech will<br />

make one more attempt to contact CLEC. The Field Tech will then place the order into jeopardy status.<br />

Internal process Authorization of charges will need to be approved through a SUP on the LSR. Appropriate USOC's will be applied to the service<br />

order after SUP is received (Placement of conduit and the cost associated with it is the responsibility of the property owner.)<br />

If conduit placement is required, Field Tech will advise property owner where the conduit should start and end.<br />

Design (ie, Unbundled)- Qwest Field Tech makes a call to the QCCC or DSC and the QCCC or DSC will contact the CLEC for jeopardy condition<br />

for placing of drop and/or conduit and order will be placed into jeopardy status. Authorization of charges will need to be approved through a SUP<br />

on the LSR. Appropriate USOC will be applied to the service order after SUP is received (Placement of conduit and the cost associated with it is<br />

the responsibility of the property owner.)<br />

If conduit placement is required, Field Tech will advise property owner where the conduit should start and end.<br />

(If the QCCC or DSC cannot reach the CLEC, they will leave a VM.)<br />

4. Property owner or end-user will contact CLEC to advise conduit placement is complete and order can be re-scheduled.<br />

5. CLEC updates Qwest through LSR notification.<br />

6. BSW group receives notification and schedules contractor to place Service Wire.<br />

7. Field Technician is then dispatched out to complete installation.<br />

Expected Deliverable:<br />

January 1, <strong>2004</strong><br />

Status History<br />

10/31/03 - CR Submitted<br />

10/31/03 - CR Acknowledged<br />

11/11/03 Held Clarification Call<br />

11/19/03 - November <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

11/19/03 - Status changed to Presented<br />

11/19/03 - Qwest issued CLEC Input <strong>Meeting</strong> Notification <strong>CMP</strong>R.11.20.03.F.01085.CLECInput<strong>Meeting</strong><br />

12/04/03 - Held ad-hoc CLEC imput call<br />

12/11/03 - Sent Minutes for CLEC input meeting<br />

12/17/03 -December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - Status changed to Development<br />

1/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

1/21/04 - Status will remain in Devleopment<br />

1/30/04: Qwest initiated notification PROS.01.30.04.F.01311.Mtce_&_Rpr_Overview V25.0<br />

2/19/04: Qwest initiated notification PROS.02.19.04.F.01387.FNL_Prov_Overview_V34<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Project <strong>Meeting</strong>s<br />

Retka, Mary<br />

Tallman, Shirley<br />

Tallman, Shirley<br />

Andreen, Doug<br />

Information Current as of:<br />

Report Name:<br />

Development<br />

12/17/03<br />

Originator Company Name:<br />

Report Line Number<br />

Qwest Communications<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

4<br />

<strong>Product</strong>s<br />

Impacted<br />

PC103103-1<br />

Page 10 of 32<br />

Attachment F


2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Shirley Tallman, Qwest said the comment cycle completed with no comments being received. The PCAT will be published and operational on<br />

<strong>March</strong> 5. The CR will stay in Development status.<br />

-----------------------------------------------------------------<br />

1/21/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Shirley Tallman, Qwest said the PCAT language has been developed and will be on line for CLEC comments by the end of the month. Lydell<br />

Peterson, Qwest asked if the escalation process would change. Shirley said no, that it would continue to flow through the delayed order desk.<br />

The CR will stay in Development.<br />

-----------------------------------------------------------------<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Jamal Boudhaouia, Qwest provided an update to this CR that Qwest is moving forward on the PCAT language to establish the process for when<br />

initial or additional drops are needed to complete an order. This CR was moved to Development.<br />

------------------------------------------------------------------<br />

Ad Hoc <strong>Meeting</strong> Minutes<br />

PC103103-1<br />

Buried service wire/placing/Conduit/Technician interface with end user<br />

<strong>CMP</strong> <strong>Product</strong> & <strong>Process</strong><br />

December 4, 2003<br />

1-877-521-8688, Conference ID 1456160<br />

10:00 a.m. 11:00 a.m. Mountain Time<br />

PURPOSE<br />

At the November <strong>CMP</strong> <strong>Meeting</strong>, participants agreed to hold a conference call to discuss Qwest initiated CR PC103103-1. The following is the<br />

write-up of the discussion.<br />

List of Attendees:<br />

Bonnie Johnson, Eschelon<br />

Carla Pardee, AT&T<br />

Liz Balvin, MCI<br />

Patrick Hennesey, Eschelon<br />

Todd Miller, Eschelon<br />

Kim Isaacs, Eschelon<br />

Ann Atchison, AT&T<br />

Steve Kast, Qwest<br />

Cathy Augustson, Qwest<br />

Shirley Tallman, Qwest<br />

Allen Braeggar, Qwest<br />

Eric Yohe, Qwest<br />

Doug Andreen, Qwest<br />

MEETING MINUTES<br />

The meeting began with Qwest making introductions and welcoming all attendees.<br />

Doug Andreen with Qwest explained that the purpose of the meeting was to discuss Qwest initiated CR PC103103-1.<br />

Shirley Tallman, Qwest explained the purpose of the CR is to establish a process for the Qwest on site technician and the CLECs concerning a<br />

situation where the technician finds that either an additional drop wire or conduit needs to be run. Shirley than described the proposed process.<br />

She pointed out that while Qwest does not usually talk to the CLEC customer that in the case where the building owner/manager and the customer<br />

are one in the same that Qwest would talk to them in their capacity as the building owner/manager.<br />

Bonnie Johnson, Echelon questioned if this was a new or existing process.<br />

Shirley said it is a little of both. The purpose was to clarify the process for both the Qwest technician and the CLECs.<br />

Todd Miller, Eschelon added that he felt some of this was existing but that this process clarifies some unknowns.<br />

Bonnie stated that her concerns is the benefit of supplying the building manager/customer with the information in the sense that they will want the<br />

CLEC to fix the problem. Therefore she wanted to make sure there was a method for the CLEC to get the information.<br />

Shirley stated that at the same time the technician is giving the building manager/customer the information it would also be called to the QCCC for<br />

entry into the database. She suggested that we add a narrative of what the situation is after the notation that the order will be put in jeopardy<br />

status.<br />

Bonnie asked if this could be built into process.<br />

Shirley answered yes.<br />

Bonnie further questioned if there could be information on how to contact the technician in case additional information was needed.<br />

A discussion ensued on how this could best be done. Patrick Hennesey, Eschelon suggested the request go through the Service Manager. Steve<br />

Kast, Qwest suggested that there is an existing group in Cheyenne that handles jeopardy orders and that this might be the logical place to go for<br />

information.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC103103-1<br />

Page 11 of 32<br />

Attachment F


Shirley agreed to investigate what would be the best way.<br />

Doug asked if the intent is to have a CLEC contact that is a consistent place to go for additional information.<br />

Bonnie agreed and added that there be a CLEC facing document that outlines the procedure.<br />

Doug pointed out that a PCAT would be issued covering this process and that this document would be available for CLEC review.<br />

Shirley mentioned that the PCAT might be delayed from the expected January 1 due date.<br />

Bonnie pointed out that it is difficult for the CLECs to know what is going on if Qwest implements a process without the PCAT being issued.<br />

Shirley asked if she wanted the process to not go into effect until the PCAT is finalized.<br />

Bonnie said yes and Liz Balvin, MCI and Carla Pardee, AT&T concurred.<br />

Doug said he would ensure that the CLECs were kept apprised of the PCAT status.<br />

There were no further comments and the meeting was concluded.<br />

------------------------------------------------------------------------------------<br />

11/19/03 Nov. <strong>CMP</strong> <strong>Meeting</strong><br />

Shirley Tallman Qwest presented the CR, which details the process for field technicians to follow when the technician finds that an initial or<br />

additional drop is required or that conduit is required. She stated that the intent is to document the process so that technicians are clear on what<br />

to do. Shirley also pointed out that she wanted the CLECs to be clear that this change involves the technician discussing with the property owner<br />

what the situation is and what needs to be done. The technician would also do this if the CLEC customer is the property owner. Anticipated<br />

effective date is January 1. Bonnie Johnson Eschelon asked if this was a new process or a modification to an existing process. Shirley replied<br />

that it is a bit of both and the intention is to get clarity around the process. Bonnie asked if there would be an input meeting or comment cycle.<br />

Kim Isaacs pointed out that this needs to be in the PCAT. It was agreed that both a comment cycle and input meeting will be utilized. Doug<br />

Andreen Qwest said the CLEC Input meeting is tentatively set for December 4. This CR will move to Presented status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC103103-1<br />

Page 12 of 32<br />

Attachment F


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC103103-2 Binding Post information Development Wholesale ProdProc Maintenance/Rep<br />

12/17/03<br />

air<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

UNE Loop, EEL<br />

(UNE-C)<br />

Qwest will provide dmarc Binding Post information for Unbundled Loop and EEL <strong>Product</strong>s on CLEC orders through the Repair Department upon<br />

request, when information is available. If BP information is not available, the existing process for tagging the dmarc will apply.<br />

Information on dmarc BP on non-design orders is not retained in any database and is not available.<br />

Expected Deliverables:<br />

January 1, <strong>2004</strong><br />

Status History<br />

Retka, Mary<br />

Tallman, Shirley<br />

Tallman, Shirley<br />

Andreen, Doug<br />

Originator Company Name:<br />

Report Line Number<br />

Qwest Communications<br />

10/31/03 - Submitted<br />

10/31/03 - Acknowledged<br />

11/18/03 - Held clarification call<br />

11/19/03 - November <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

11/19/03 - Status changed to Presented<br />

11/20/03 - Qwest issued Clec Input <strong>Meeting</strong> Notification <strong>CMP</strong>R.11.20.03.F.01086.CLECInputMtgBindingPost<br />

11/24/03 - Qwest issued CLEC Input <strong>Meeting</strong> Time Change Notification <strong>CMP</strong>R.11.24.03.F.01095.TimeChangeCLECInputMtg<br />

12/04/03 - Held ad-hoc CLEC input call<br />

12/11/03 - Issued minutes from ad hoc call<br />

12/17/03 -December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - Status changed to Development<br />

1/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

1/21/04 - Status will remain in Development<br />

1/30/04: Qwest initiated notification PROS.01.30.04.F.01310.Prov_Overview_V34<br />

2/19/04: Qwest initiated notification PROS.02.19.04.F.01388.FNL_Mtce_&_Rpr_Ver25<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

<strong>Product</strong>s<br />

Impacted<br />

Project <strong>Meeting</strong>s<br />

2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Shirley Tallman, Qwest said the comment cycle completed with no comments being received. The PCAT will be published and operational on<br />

<strong>March</strong> 5. The CR will stay in Development status.<br />

------------------------------------------------------------------------<br />

1/21/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Shirley Tallman, Qwest stated that the PCAT language has been developed and will be on line for CLEC comments by the end of the month.<br />

Bonnie wanted to be sure that her comments about what an RSB representative had said about not giving out binding post information was about<br />

the situation and not about the employee. Kit Thomte, Qwest assured her that was understood. It was agreed that Doug Andreen will open a<br />

global action item concerning how CLECs will obtain Binding Post (demarc) information on non-design orders since this process only addresses<br />

design orders. The CR will stay in Development status.<br />

-----------------------------------------------------------------------------<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Jamal Boudhaouia, Qwest stated that the Qwest is moving forward on PCAT language to provide information for Binding Post. Bonnie Johnson,<br />

Eschelon questioned the status on the question of CLECs seeing proprietary information in CEMR. She stated that two or three days after the<br />

Clarification call Eschelon called Qwest for Binding Post information and was told that the information could not be given out. Bonnie said she had<br />

stated on the Clarification call that she was afraid that Qwest would discontinue a process without proper notice to the CLECs. Judy Schultz,<br />

Qwest stated that a memo had been issued to the effect that proper notice must be given before process changes can be implemented. Jamal<br />

stated he would take on the issue of CEMR and what is proprietary. Bonnie stated that Qwest has a major compliance problem with tagging and<br />

the Qwest is obligated to provide last point of termination and that Qwest needs to correct the tagging problem or provide the information. She<br />

said the result is the Eschelon customer’s service is delayed and both companies have to dispatch to the premise. John Berard, Covad said there<br />

is a process being implemented at SBC for a CLEC tech to send tone on a line and determine the demarc. The CR was moved to Design.<br />

---------------------------------------------------------------------------------<br />

Ad Hoc <strong>Meeting</strong> Minutes<br />

PC103103-2<br />

Binding Post Information<br />

<strong>CMP</strong> <strong>Product</strong> & <strong>Process</strong><br />

December 4, 2003<br />

1-877-521-8688, Conference ID 1456160<br />

3:00 p.m. 4:00 p.m. Mountain Time<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC103103-2<br />

Page 13 of 32<br />

Attachment F<br />

5


PURPOSE<br />

At the November <strong>CMP</strong> meeting, participants agreed to hold a conference call to discuss Qwest initiated CR PC103103-2. The following is the<br />

write-up of the discussion.<br />

List of Attendees:<br />

Jeff Bellin, Eschelon<br />

Bonnie Johnson, Eschelon<br />

Rhonda Knutson, Eschelon<br />

Allen Braeggar, Qwest<br />

Cathy Augustson, Qwest<br />

Shirley Tallman, Qwest<br />

Eric Yohe, Qwest<br />

Pat Finley, Qwest<br />

Don Deland, Qwest<br />

MEETING MINUTES<br />

The meeting began with Qwest making introductions and welcoming all attendees.<br />

Doug Andreen with Qwest explained that the purpose of the meeting was to discuss Qwest initiated CR PC103103-2.<br />

Shirley Tallman, Qwest explained the purpose of the CR: Qwest will provide dmarc Binding Post information for Unbundled Loop and EEL<br />

<strong>Product</strong>s on CLEC orders through the Repair Department upon request, when information is available. If BP information is not available, the<br />

existing process for tagging the dmarc will apply.<br />

Information on dmarc BP on non-design orders is not retained in any database and is not available.<br />

Bonnie Johnson, Eschelon asked if that meant Qwest would no longer tag.<br />

Shirley responded no that normal processes for tagging still apply. This is primarily for when there is not a truck roll.<br />

Bonnie said that on non-design orders she was surprised to hear that the information was not available.<br />

Shirley responded that terminal information like at multi-tenant buildings is actual terminal information and not binding post at the dmarc.<br />

Bonnie said Eschelon seems to be successful with data in CEMR and wondered on new orders if this process would prevent the CLECs from<br />

doing what they have done all along?<br />

Shirley answered it would not as this is not designed to replace any existing process.<br />

Bonnie asked if in the PCAT it would state that the information is not available?<br />

Shirley said no, it would state that Qwest would provide the information it has if available.<br />

Rhonda, Eschelon said that if an order is completed on non-design that Eschelon asks for binding post or F2 information. It may not be the last<br />

point but is close.<br />

Shirley stated that Qwest should not be providing F2 information since this is in our network.<br />

Rhonda stated that she was aware that cable and pair information should not be available but that F2 information was ok.<br />

Jeff, Eschelon pointed out that on record 651-466-0492 in CEMR he could see binding post 272.<br />

Shirley agreed to check out exactly what CLECs are seeing in CEMR.<br />

Rhonda said that sometimes binding post and F2 are used interchangeably and she wondered if this could be causing the problem.<br />

Bonnie stated that this information is critical especially when dealing with customer who has not paid their bill.<br />

Shirley stated that Qwest should never be providing terminal binding post information but rather just binding post.<br />

Bonnie stated that this would cause more dispatches for tagging.<br />

Rhonda wondered how the information would show up. Will it say dmarc?<br />

Shirley said at this point she was not sure.<br />

Cathy Augustson, Qwest added when tech calls in an order complete that the tech provides the information at that time.<br />

Rhonda asked if the last point of dmarc is where Qwest terminates the line.<br />

Don Deland, Qwest said could be RJ11 or a 66 block.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC103103-2<br />

Page 14 of 32<br />

Attachment F


Rhonda asked if F2 is where Qwest takes ownership.<br />

Don said that it is jumpered from the F2 to a dmarc box or jack where the CLEC takes ownership.<br />

Bonnie had two questions, first, is it called something else on a non-design and why doesn’t Qwest keep a record of it, and second isn’t Qwest<br />

obligated to provide information on where the dmarc is and where the CLEC takes ownership?<br />

Shirley stated that the dmarc is not always our block that it can be the building owners.<br />

Rhonda asked if beyond this point is the CLECs.<br />

Don said usually the jumper is tagged to where the alternate provider takes over.<br />

Bonnie asked if there would be a PCAT update and comment cycle.<br />

Doug answered that there would be however the original date for the PCAT of January 1 would be delayed.<br />

Doug asked Bonnie if her main concern is that these processes not supercede or replace anything in place today.<br />

Bonnie said that was correct<br />

Shirley added that this would not supercede or replace anything existing.<br />

Bonnie said she would check if other CLECs were interested in this CR.<br />

It was agreed there might be a need for another input meeting after the <strong>CMP</strong> meeting.<br />

There was no disagreement with the design part of this CR, making the goal to not hold up design implementation while resolving issues on the<br />

non-design side.<br />

--------------------------------------------------------------------------------<br />

11/19/03 Nov. <strong>CMP</strong> <strong>Meeting</strong><br />

Shirley Tallman Qwest presented the CR for providing dmarc Binding Post information for Unbundled Loop and EEL <strong>Product</strong>s on CLEC orders<br />

through the Qwest Repair Department upon request. She pointed out that this information on non-design orders is not available. Anticipated<br />

implementation is January 1. Bonnie Johnson Eschelon ask if the information was available through LMOS? Shirley responded that dmarc<br />

information is available but binding post is not. Bonnie questioned if the issue is a compliance issue since it is the existing process for the<br />

technician to tag at the dmarc. Shirley pointed out that there are times when a Qwest technician is not dispatched. Doug stated that a CLEC Input<br />

<strong>Meeting</strong> is tentatively set for December 4. This CR will move to Presented status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC103103-2<br />

Page 15 of 32<br />

Attachment F


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC111003-1 Reserved TN Procedure Development Wholesale ProdProc PreOrdering,<br />

12/17/03<br />

Ordering,<br />

Provisioning,<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Implement procedure to either activate or cancel TNs reserved for 180 days or more to comply with December 2000 FCC Mandate.<br />

Status History<br />

Burson, Sue<br />

Robberson, Anne<br />

Dimmitt, Jan<br />

Andreen, Doug<br />

11/10/03: CR Received<br />

11/11/03: CR Acknowledged<br />

11/18/03: Held Clarification meeting<br />

11/18/03: Status changed to clarification<br />

11/19/03: Qwest initiated notification <strong>CMP</strong>R.12.19.03.F.01201.Mtg_On_Reserve_TN_<strong>Process</strong><br />

12/17/03 -December <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

12/17/03 - Status changed to Presented<br />

01/12/04 - Held CLEC Input Call<br />

01/15/04 - Sent CLEC Input Minutes<br />

1/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

1/21/04 - Status changed to Development<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Centrex, Resale<br />

POTS, UNE-P, any<br />

TN based product is<br />

Project <strong>Meeting</strong>s<br />

2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Jan Dimmitt said she is currently working on the PCAT. No line ranges have been encountered that require contacting the CLECs. The CR will<br />

remain in Development.<br />

-------------------------------------------------------------------<br />

1/21/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Jan Dimmitt said there was a CLEC Input meeting held January 12 and that the purpose of the CR is to establish a procedure where CLECs are<br />

notified when a line range has been reserved for over 180 days. She also said she is still looking into if a TN is part of a common block is it<br />

considered reserved or activated. Bonnie Johnson, Eschelon asked about the re-reserve policy. Jan said this is strictly a courtesy with no<br />

additional fees. A CLEC can continue to reserve, cancel the reservation, activate the line range, or re-reserve only a portion of the original. The<br />

CR will be moved to Development status.<br />

----------------------------------------------------------------------------------<br />

CLEC Input <strong>Meeting</strong><br />

9:00 a.m. (MDT) / Monday January 12, <strong>2004</strong><br />

1-877-521-8688<br />

1456160<br />

PC 111003-1-Reserve TN Procedure<br />

Attendees<br />

Carla Pardee, AT&T<br />

Phyllis Burt, AT&T<br />

Liz Balvin, MCI<br />

Kim Isaacs, Eschelon<br />

Stephanie Prull, Eschelon<br />

James McCluskey, Accenture<br />

Cheryl Peterson, AT&T<br />

Anne Robberson, Qwest<br />

Jan Dimmitt, Qwest<br />

Doug Andreen, Qwest<br />

<strong>Meeting</strong> Agenda:<br />

1.0 Introduction of Attendees<br />

Introduction of participants on the conference call was made and the purpose of the call discussed.<br />

2.0 Review Requested (Description of) Change<br />

Originator Company Name:<br />

Report Line Number<br />

Qwest Communications<br />

<strong>Product</strong>s<br />

Impacted<br />

Doug Andreen, Qwest read the CR description: Implement a procedure to either activate or cancel TNs reserved for 180 days or more to comply<br />

with December 2000 FCC Mandate.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC111003-1<br />

Page 16 of 32<br />

Attachment F<br />

6


Jan Dimmitt, Qwest explained this process is not applicable to Resale Pre-Order TN Reservations through IMA and is applicable to numbers or<br />

number ranges that the CLEC has reserved and is paying a monthly fee to hold. This process is also not applicable to the 30 day reservations<br />

done through IMA. She said that Qwest gets a report of all reservations of over 150 days that have not been activated. They are compared with<br />

CNUM and the billing system for a match and to see if there are pending orders. The question is if the CLECs would like a courtesy call to inform<br />

them that they have a number or range of numbers that have been reserved for some time.<br />

Kim Isaacs, Eschelon asked what happens after the courtesy call. Jan answered that the CLEC can either activate, continue to hold or cancel.<br />

Kim then asked if the number is on the common block CSR is it activated or reserved. Jan said she would have to find out.<br />

Liz Balvin, MCI wanted to verify that it is the CLECs choice of what to do with the reservation after the courtesy call.<br />

Jan said yes and that some of these may take some research on the CLEC side. Qwest will continue to hold the number until advised by the<br />

CLEC what to do.<br />

Anne Robberson, Qwest added that this is more of an effort to ensure the CLECs get what they want. The re-reserve policy still needs to be<br />

worked out.<br />

Liz asked if Qwest was willing to hold another 180 days and Anne said yes. Anne then summarized that the process is to notify the CLECs of the<br />

choices they have.<br />

Stephanie Prull, Eschelon asked if the non recurring charge would be applicable on re-reserves. Jan said she would have to check.<br />

Cheryl Peterson, AT&T asked if only a portion of the original reservation could be re-reserved. Jan answered yes but it is now a verbal<br />

commitment. However, an email could verify the PON or service order. (The following was added after the meeting for further clarification: Qwest<br />

can initiate a service order without an LSR using PONS for specific order function. PON for cancel: CANRESRVTN180, PON for line range<br />

activation: ACTRESRVTN180, PON for cancel of portion of block and re-reserve portion of block: RERESRVTN180.)<br />

Cheryl then said she needed more information on how the process works today and what now happens at the 150th day. Anne said the entire<br />

process is out in the LSOG and this is simply an addition.<br />

Kim asked what the escalation process would look like iF something goes wrong. Jan said normal escalation procedures would apply.<br />

Anne added that the preliminary investigation is a manual process.<br />

Jan also added that the billing at the current time just continues on after 180 days without notifying the CLECs.<br />

No other CLEC input was offered. There will be an update given in the January <strong>CMP</strong> meeting.<br />

3.0 Confirm Areas & <strong>Product</strong>s Impacted<br />

UNE-P, Centrex (not resale Centrex), any TN product is impacted including resold ISDN, DID, and Retail POTS<br />

4.0 Confirm Right Personnel Involved<br />

Correct personnel were involved in the meeting.<br />

--------------------------------------------------------------------------------------------------<br />

12/17/03 December <strong>CMP</strong> <strong>Meeting</strong><br />

Jan Dimmitt presented this CR which asks if the CLECs would like to be notified when a TN or range of TNs have been reserved for longer than<br />

180 days. The CR was moved to Presented status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC111003-1<br />

Page 17 of 32<br />

Attachment F


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC010604-1 Grandparent DSL Pro USOCs. Pending<br />

Withdrawal<br />

3/11/04<br />

Wholesale ProdProc Provisioning Resale, UNE-P<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Campbell, Bill<br />

Van Dusen, Janean<br />

Van Dusen, Janean<br />

Sanchez-Steinke, Linda<br />

Description Of Change<br />

The following USOCs will be grandparented effective 3/31/04:<br />

USOC Description<br />

G5L21 QDSL DMT Pro 640k Centrex PlusPrime 1 yr<br />

G5L23 QDSL DMT Pro 640k Centrex PlusPrime 3 yr<br />

G5L25 QDSL DMT Pro 640k Centrex PlusPrime 5 yr<br />

G5L2M QDSL DMT Pro 640k Centrex PlusPrime MTM<br />

G5L31 QDSL DMT Pro 960k Centrex PlusPrime 1 yr<br />

G5L33 QDSL DMT Pro 960k Centrex PlusPrime 3 yr<br />

G5L35 QDSL DMT Pro 960k Centrex PlusPrime 5 yr<br />

G5L3M QDSL DMT Pro 960k Centrex PlusPrime MTM<br />

G5L41 QDSL DMT Pro 1 Meg Centrex PlusPrime 1 yr<br />

G5L43 QDSL DMT Pro 1 Meg Centrex PlusPrime 3 yr<br />

G5L45 QDSL DMT Pro 1 Meg Centrex PlusPrime 5 yr<br />

G5L4M QDSL DMT Pro 1 Meg Centrex PlusPrime MTM<br />

G5L51 QDSL DMT Pro 4 Meg Centrex PlusPrime 1 yr<br />

G5L53 QDSL DMT Pro 4 Meg Centrex PlusPrime 3 yr<br />

G5L55 QDSL DMT Pro 4 Meg Centrex PlusPrime 5 yr<br />

G5L5M QDSL DMT Pro 4 Meg Centrex PlusPrime MTM<br />

G5L61 QDSL DMT Pro 7 Meg Centrex PlusPrime 1 yr<br />

G5L63 QDSL DMT Pro 7 Meg Centrex PlusPrime 3 yr<br />

G5L65 QDSL DMT Pro 7 Meg Centrex PlusPrime 5 yr<br />

G5L6M QDSL DMT Pro 7 Meg Centrex PlusPrime MTM<br />

G5LB1 QDSL DMT Pro 640k Centrex 1 yr<br />

G5LB3 QDSL DMT Pro 640k Centrex 3 yr<br />

G5LB5 QDSL DMT Pro 640k Centrex 5 yr<br />

G5LBM QDSL DMT Pro 640k Centrex MTM<br />

G5LC1 QDSL DMT Pro 960k Centrex 1 yr<br />

G5LC3 QDSL DMT Pro 960k Centrex 3 yr<br />

G5LC5 QDSL DMT Pro 960k Centrex 5 yr<br />

G5LCM QDSL DMT Pro 960k Centrex MTM<br />

G5LD1 QDSL DMT Pro 1 Meg Centrex 1 yr<br />

G5LD3 QDSL DMT Pro 1 Meg Centrex 3 yr<br />

G5LD5 QDSL DMT Pro 1 Meg Centrex 5 yr<br />

G5LDM QDSL DMT Pro 1 Meg Centrex MTM<br />

G5LE1 QDSL DMT Pro 4 Meg Centrex 1 yr<br />

G5LE3 QDSL DMT Pro 4 Meg Centrex 3 yr<br />

G5LE5 QDSL DMT Pro 4 Meg Centrex 5 yr<br />

G5LEM QDSL DMT Pro 4 Meg Centrex MTM<br />

G5LF1 QDSL DMT Pro 7 Meg Centrex 1 yr<br />

G5LF3 QDSL DMT Pro 7 Meg Centrex 3 yr<br />

G5LF5 QDSL DMT Pro 7 Meg Centrex 5 yr<br />

G5LFM QDSL DMT Pro 7 Meg Centrex MTM<br />

G5LG1 QDSL DMT Pro 256k Centrex 21 1 yr<br />

G5LG3 QDSL DMT Pro 256k Centrex 21 3 yr<br />

G5LG5 QDSL DMT Pro 256k Centrex 21 5 yr<br />

G5LGM QDSL DMT Pro 256k Centrex 21 MTM<br />

G5LJ1 QDSL DMT Pro 256k Centrex PlusPrime 1 yr<br />

G5LJ3 QDSL DMT Pro 256k Centrex PlusPrime 3 yr<br />

G5LJ5 QDSL DMT Pro 256k Centrex PlusPrime 5 yr<br />

G5LJM QDSL DMT Pro 256k Centrex PlusPrime MTM<br />

GPRBM QDSL DMT Pro 640k Ctx Analog MTM<br />

GPRCM QDSL DMT Pro 960k Ctx Analog MTM<br />

GPRDM QDSL DMT Pro 1 Meg Ctx Analog MTM<br />

GPREM QDSL DMT Pro 4 Meg Ctx Analog MTM<br />

Information Current as of:<br />

Report Name:<br />

Originator Company Name:<br />

Report Line Number<br />

Qwest Communications<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

7<br />

<strong>Product</strong>s<br />

Impacted<br />

PC010604-1<br />

Page 18 of 32<br />

Attachment F


GPRFM QDSL DMT Pro 7 Meg Ctx Analog MTM<br />

GPRNM QDSL DMT Pro 256k Ctx Analog MTM<br />

GRLB1 QDSL DMT Pro 640k dn/544 up 1 yr<br />

GRLB3 QDSL DMT Pro 640k dn/544 up 3 yr<br />

GRLB5 QDSL DMT Pro 640k dn/544 up 5 yr<br />

GRLBM QDSL DMT Pro 640k dn/544 up MTM<br />

GRLC1 QDSL DMT Pro 960k 1 yr<br />

GRLC3 QDSL DMT Pro 960k 3 yr<br />

GRLC5 QDSL DMT Pro 960k 5 yr<br />

GRLCM QDSL DMT Pro 960k MTM<br />

GRLD1 QDSL DMT Pro 1 Meg 1 yr<br />

GRLD3 QDSL DMT Pro 1 Meg 3 yr<br />

GRLD5 QDSL DMT Pro 1 Meg 5 yr<br />

GRLDM QDSL DMT Pro 1 Meg MTM<br />

GRLE1 QDSL DMT Pro 4 Meg 1 yr<br />

GRLE3 QDSL DMT Pro 4 Meg 3 yr<br />

GRLE5 QDSL DMT Pro 4 Meg 5 yr<br />

GRLEM QDSL DMT Pro 4 Meg MTM<br />

GRLF1 QDSL DMT Pro 7 Meg 1 yr<br />

GRLF3 QDSL DMT Pro 7 Meg 3 yr<br />

GRLF5 QDSL DMT Pro 7 Meg 5 yr<br />

GRLFM QDSL DMT Pro 7 Meg MTM<br />

GRLG1 QDSL DMT Pro 256-640k dn/272 up 1 yr<br />

GRLG3 QDSL DMT Pro 256-640k dn/272 up 3 yr<br />

GRLG5 QDSL DMT Pro 256-640k dn/272 up 5 yr<br />

GRLGM QDSL DMT Pro 256-640k dn/272 up MTM<br />

Expected Deliverable:<br />

03/31/04<br />

Status History<br />

01/06/04 - CR Submitted<br />

01/08/04 - CR Acknowledged<br />

01/13/04 - Held Clarification <strong>Meeting</strong><br />

01/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

03/11/04 - Status changed to Pending Withdrawal<br />

Project <strong>Meeting</strong>s<br />

01/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen with Qwest gave an update stating the effective date moved to 5/28/04 and some USOCs will be eliminated and some<br />

grandparented. A new list of USOCs will be provided. This CR will be moved to Development Status.<br />

________________________________<br />

1/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen with Qwest presented this CR and said that effective 3/31/04 all DSL Pro Line USOCs will be grandfathered. Bonnie Johnson<br />

asked if the DSL pro product would be going away. Janean said yes. This CR will be moved to Presented Status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC010604-1<br />

Page 19 of 32<br />

Attachment F


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC010704-2 Eliminate Analog Private Line USOCs from<br />

Qwest’s offering<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Provisioning Resale<br />

Qwest will be eliminating attached Analog Private Line USOCs from it’s offerings. These USOCs have no end users.<br />

Status History<br />

Campbell, Bill<br />

Van Dusen, Janean<br />

Van Dusen, Janean<br />

Andreen, Doug<br />

Development<br />

2/18/04<br />

Originator Company Name:<br />

01/07/04 - CR Submitted<br />

01/08/04 - CR Acknowledged<br />

01/08/04 - Held clarification call with Janean<br />

1/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

1/21/04 - Status changed to Presented<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

2/18/04 - Status changed to development<br />

Report Line Number<br />

Qwest Communications<br />

<strong>Product</strong>s<br />

Impacted<br />

Project <strong>Meeting</strong>s<br />

2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen, Qwest stated that the new effective date for the CR is May 28. The USOC has also changed and will go out with the<br />

notification. The CR will move to development.<br />

-----------------------------------------------------------------<br />

1/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen presented this CR. It is to eliminate certain USOCs from Analog Private Line. It is due to be implemented <strong>March</strong> 31st. There<br />

will be the standard notifications and a comment cycle in lieu of a CLEC Input meeting. This CR will be moved to Presented status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC010704-2<br />

Page 20 of 32<br />

Attachment F<br />

8


ROUND 2 - AZ TIMCODE MATCH<br />

AS OF 11-18-03<br />

135<br />

USOC<br />

1U5Q6<br />

TUSA4<br />

TUSC2<br />

TUSC4<br />

TUSK2<br />

TUSO2<br />

TUSP2<br />

TUSR2<br />

TWTNB<br />

PJPAA<br />

PJPEA<br />

BGA<br />

6BN<br />

PJPA1<br />

PJPA2<br />

PJPA8<br />

PJPAD<br />

PJPAF<br />

PJPAG<br />

PJPAK<br />

PJPAT<br />

PJPDE<br />

PJPED<br />

PJPGA<br />

PJPGE<br />

PJPGG<br />

PJPGJ<br />

PJPGO<br />

PJPHA<br />

1LMBB<br />

1LMBD<br />

1LMBR<br />

1LMBY<br />

1LMDE<br />

1LME9<br />

1LMEQ<br />

1LMES<br />

1LMEY<br />

1LMFM<br />

1LMFQ<br />

1LMFY<br />

1LP94<br />

1LP9C<br />

1LP9D<br />

1LP9Q<br />

1LP9S<br />

1LP9Y<br />

1LPAY<br />

1LPDO<br />

1LPFJ<br />

1LPFO<br />

1LPG+<br />

1LPH+<br />

1LPQW<br />

Status<br />

Printed 1/22/04 8:26 AM CONFIDENTIAL: Not for Disclosure Outside of Qwest. 1 of 3


ROUND 2 - AZ TIMCODE MATCH<br />

AS OF 11-18-03<br />

USOC<br />

1LPR4<br />

CDQ2X<br />

4GTAD<br />

PJPAB<br />

PJPDB<br />

1L314<br />

1L31C<br />

1L31K<br />

1L31M<br />

1L31S<br />

1L31Y<br />

1L374<br />

1L37C<br />

1L37D<br />

1L37Q<br />

1L37S<br />

1L37Y<br />

1L3A8<br />

1L3AC<br />

1L3AE<br />

1L3AG<br />

1L3AO<br />

1L3AT<br />

1L3AY<br />

1L3C4<br />

1L3CC<br />

1L3CS<br />

1L3CY<br />

1L3L8<br />

1L3QR<br />

1L6AC<br />

1L6AR<br />

1L6AS<br />

1L6AY<br />

1L6B4<br />

1L6BA<br />

1L6BJ<br />

1L6BN<br />

1L6BO<br />

1L6BP<br />

1L6BQ<br />

1L6BS<br />

1L6BY<br />

1L6CC<br />

1L6CY<br />

1L6D1<br />

1L6D2<br />

1L6D3<br />

1L6D4<br />

1L6DA<br />

1L6DB<br />

1L6DJ<br />

1L6DN<br />

1L6DP<br />

1L6DQ<br />

Status<br />

Printed 1/22/04 8:26 AM CONFIDENTIAL: Not for Disclosure Outside of Qwest. 2 of 3


USOC Status<br />

1L6DR<br />

1L6DS<br />

1L6DY<br />

1L6FJ<br />

1L6FO<br />

1L6GC<br />

1L6GY<br />

1L6OC<br />

1L6OS<br />

1L6OY<br />

1L6WC<br />

1L6WS<br />

1L6WY<br />

1L7A4<br />

1L7B4<br />

1L7E4<br />

1L7F4<br />

1L7H4<br />

1SE1Q<br />

1SEHQ<br />

1SEHX<br />

1SES2<br />

1SESJ<br />

1SESM<br />

96H<br />

96L<br />

ROUND 2 - AZ TIMCODE MATCH<br />

AS OF 11-18-03<br />

Printed 1/22/04 8:26 AM CONFIDENTIAL: Not for Disclosure Outside of Qwest. 3 of 3


55<br />

USOC Status<br />

SA9 Keep - Scan Alert<br />

TJ5CX Keep - SVDS<br />

TJ5DX Keep - SVDS<br />

TJ5EX Keep - SVDS<br />

TJ5GX Keep - SVDS<br />

TJ5HX Keep - SVDS<br />

TJ5JX Keep - SVDS<br />

TJ5KX Keep - SVDS<br />

TJ5MX Keep - SVDS<br />

TJ5PX Keep - SVDS<br />

TZUVX<br />

CVS - not my product - belongs<br />

on Tom Wilson's team<br />

B5NAF Keep - SVDS<br />

B5NBF Keep - SVDS<br />

FQYV1 Keep - SVDS<br />

FQYV2 Keep - SVDS<br />

FQYV4 Keep - SVDS<br />

FQYW1 Keep - SVDS<br />

FQYW3 Keep - SVDS<br />

FQYW4 Keep - SVDS<br />

JZ3VA Keep - SVDS<br />

JZ3VB Keep - SVDS<br />

JZ3VD Keep - SVDS<br />

JZ3WA Keep - SVDS<br />

JZ3WB Keep - SVDS<br />

JZ3WC Keep - SVDS<br />

JZ3WD Keep - SVDS<br />

MXN2A Keep - SVDS<br />

MXN4A Keep - SVDS<br />

MXN4B Keep - SVDS<br />

MXN9A Keep - SVDS<br />

MXN9B Keep - SVDS<br />

PM25X Keep - SVDS<br />

PM27X Keep - SVDS<br />

PM28X Keep - SVDS<br />

PMW1X Keep - SVDS<br />

PMW2X Keep - SVDS<br />

PMW3X Keep - SVDS<br />

PMW4X Keep - SVDS<br />

PMW5X Keep - SVDS<br />

PMW6X Keep - SVDS<br />

PMWJX Keep - SVDS<br />

PMWLX Keep - SVDS<br />

PMWMX Keep - SVDS<br />

PMWNX Keep - SVDS<br />

PMWOX Keep - SVDS<br />

PMWPX Keep - SVDS<br />

PMWSX Keep - SVDS<br />

PMWTX Keep - SVDS<br />

PMWUX Keep - SVDS<br />

PMWZX Keep - SVDS<br />

PCFCD Keep - Patrick Landry's GeoMax<br />

ROUND 2 - AZ TIMCODE MATCH<br />

AS OF 11-18-03<br />

Printed 1/22/04 8:26 AM CONFIDENTIAL: Not for Disclosure Outside of Qwest. 1 of 2


USOC Status<br />

PCFCE Keep - Patrick Landry's GeoMax<br />

ROUND 2 - AZ TIMCODE MATCH<br />

AS OF 11-18-03<br />

Printed 1/22/04 8:26 AM CONFIDENTIAL: Not for Disclosure Outside of Qwest. 2 of 2


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC010704-3 Eliminate certain Voice Feature USOCs<br />

from Qwest’s offering.<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Qwest will be eliminating attached Voice Feature USOCs from it’s offerings. These USOCs have no end users.<br />

Expected Deliverable:<br />

03/31/04<br />

Status History<br />

Campbell, Bill<br />

Van Dusen, Janean<br />

Van Dusen, Janean<br />

Sanchez-Steinke, Linda<br />

Development<br />

2/18/04<br />

Originator Company Name:<br />

01/07/04 - CR Submitted<br />

01/08/04 - CR Acknowledged<br />

01/13/03 - Held Clarification <strong>Meeting</strong><br />

01/21/04 - January <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

Report Line Number<br />

<strong>Product</strong>s<br />

Impacted<br />

Wholesale ProdProc Provisioning Resale, UNE-P<br />

Qwest Communications<br />

Project <strong>Meeting</strong>s<br />

02/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen with Qwest gave an update that the effective date has moved to May 28 and an updated spreadsheet will be provided for the<br />

USOCs. This CR will be moved to Development Status.<br />

_____________________________<br />

1/21/04 January <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen with Qwest presented this CR and said on 3/31/04 Qwest will be eliminating certain USOCS from Voice Features. This CR will<br />

be moved to Presented Status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC010704-3<br />

Page 21 of 32<br />

Attachment F<br />

9


USOC Description<br />

RCFGA REMOTE CALL FORWARDING<br />

- BUS FLAT - INTRALATA<br />

MPU2X BUILDING OWNER/TENANT<br />

SOLUTION MAINTENANCE<br />

PLAN 1 - EACH GROUP OF<br />

LINES - 2ND LEVEL<br />

MPU3X BUILDING OWNER/TENANT<br />

SOLUTION MAINTENANCE<br />

PLAN 1 - EACH GROUP OF<br />

LINES - 3RD LEVEL<br />

MPU5X BUILDING OWNER/TENANT<br />

SOLUTION MAINTENANCE<br />

PLAN 1 - EACH GROUP OF<br />

LINES - 5TH LEVEL<br />

MPU6X BUILDING OWNER/TENANT<br />

SOLUTION MAINTENANCE<br />

PLAN 1 - EACH GROUP OF<br />

LINES - 6TH LEVEL<br />

MPK1X BUILDING OWNER/TENANT<br />

SOLUTION MAINTENANCE<br />

PLAN 2 - EACH GROUP OF<br />

LINES - 1ST LEVEL<br />

MPK2X BUILDING OWNER/TENANT<br />

SOLUTION MAINTENANCE<br />

PLAN 2 - EACH GROUP OF<br />

LINES - 2ND LEVEL<br />

MPK3X BUILDING OWNER/TENANT<br />

SOLUTION MAINTENANCE<br />

PLAN 2 - EACH GROUP OF<br />

LINES - 3RD LEVEL<br />

MPK4X BUILDING OWNER/TENANT<br />

SOLUTION MAINTENANCE<br />

PLAN 2 - EACH GROUP OF<br />

LINES - 4TH LEVEL<br />

MPK5X BUILDING OWNER/TENANT<br />

SOLUTION MAINTENANCE<br />

PLAN 2 - EACH GROUP OF<br />

LINES - 5TH LEVEL<br />

MPK6X BUILDING OWNER/TENANT<br />

SOLUTION MAINTENANCE<br />

PLAN 2 - EACH GROUP OF<br />

LINES - 6TH LEVEL<br />

MPK7X BUILDING OWNER/TENANT<br />

SOLUTION MAINTENANCE<br />

PLAN 2 - EACH GROUP OF<br />

LINES - 7TH LEVEL


US22X MAINTENANCE PLAN -<br />

ENHANCED - LEVEL 2; PER<br />

PBX TRUNK - QWEST REPAIR<br />

COORDINATING SERVICE<br />

E1NFP INTERCOM LINE CAPABILITY<br />

ON EXCHANGE LINE -<br />

FEATURE INCLUDED IN A<br />

PACKAGE; TELECHOICE -<br />

RES.<br />

ESXTC CALL WAITING -<br />

TERMINATING - TELECHOICE<br />

DISCOUNT<br />

ESXFP CALL WAITING -<br />

TERMINATING - FEATURE<br />

INCLUDED IN A PACKAGE;<br />

TELECHOICE/TEENLINK<br />

LCS LOCAL ACCESS TO SYSTEM<br />

FEATURES NO NETWORK<br />

ACCESS<br />

C19 CALLER ID DISPLAY UNIT<br />

R8TAC SELECT CALL ROUTING<br />

SERVICE - TIME OF DAY/DAY<br />

OF WEEK ROUTING - PER<br />

ACCOUNT - USED FOR<br />

ACCOUNTS WITH BUSINESS<br />

EXCHANGE LINES & NON DID<br />

PBX TRUNKS<br />

PGY1X PAGER NOTIFICATION - 1ST<br />

GROUP OF LINES<br />

PGY2X PAGER NOTIFICATION - 2ND<br />

GROUP OF LINES<br />

PGY3X PAGER NOTIFICATION - 3RD<br />

GROUP OF LINES<br />

PGY4X PAGER NOTIFICATION - 4TH<br />

GROUP OF LINES<br />

PGZ1X PAGER NOTIFICATION WITH<br />

CALL CONNECTION - 1ST<br />

GROUP OF LINES<br />

PGZ2X PAGER NOTIFICATION WITH<br />

CALL CONNECTION - 2ND<br />

GROUP OF LINES<br />

PGZ3X PAGER NOTIFICATION WITH<br />

CALL CONNECTION - 3RD<br />

GROUP OF LINES<br />

PGZ4X PAGER NOTIFICATION WITH<br />

CALL CONNECTION - 4TH<br />

GROUP OF LINES


PML1X CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

MULTIPLE LOCATIONS &<br />

PAGER NOTIFICATION WITH<br />

CALL CONNECTION - 1ST<br />

GROUP OF LINES<br />

PML2X CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

MULTIPLE LOCATIONS &<br />

PAGER NOTIFICATION WITH<br />

CALL CONNECTION - 2ND<br />

GROUP OF LINES<br />

PML3X CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

MULTIPLE LOCATIONS &<br />

PAGER NOTIFICATION WITH<br />

CALL CONNECTION - 3RD<br />

GROUP OF LINES<br />

PML4X CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

MULTIPLE LOCATIONS &<br />

PAGER NOTIFICATION WITH<br />

CALL CONNECTION - 4TH<br />

GROUP OF LINES<br />

PSF1X CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

SINGLE LOCATION & PAGER<br />

NOTIFICATION - 1ST GROUP<br />

OF LINES<br />

PSF2X CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

SINGLE LOCATION & PAGER<br />

NOTIFICATION - 2ND GROUP<br />

OF LINES<br />

PSF3X CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

SINGLE LOCATION & PAGER<br />

NOTIFICATION - 3RD GROUP<br />

OF LINES<br />

PSF4X CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

SINGLE LOCATION & PAGER<br />

NOTIFICATION - 4TH GROUP<br />

OF LINES<br />

PYZ1M CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

MULTIPLE LOCATIONS - 1ST<br />

GROUP OF LINES<br />

PYZ1S CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

SINGLE LOCATION - 1ST<br />

GROUP OF LINES


PYZ2M CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

MULTIPLE LOCATIONS - 2ND<br />

GROUP OF LINES<br />

PYZ2S CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

SINGLE LOCATION - 2ND<br />

GROUP OF LINES<br />

PYZ3M CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

MULTIPLE LOCATIONS - 3RD<br />

GROUP OF LINES<br />

PYZ3S CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

SINGLE LOCATION - 3RD<br />

GROUP OF LINES<br />

PYZ4M CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

MULTIPLE LOCATIONS - 4TH<br />

GROUP OF LINES<br />

PYZ4S CALL FORWARDING -<br />

LOCATION SEQUENCING -<br />

SINGLE LOCATION - 4TH<br />

GROUP OF LINES<br />

ES3DX CUSTOM CALLING PACKAGE -<br />

CALL FORWARDING - CALL<br />

WAITING - SPEED CALLING - 8<br />

CODE & 3-WAY CALLING -<br />

2ND RATE LEVEL; IN<br />

CENTRAL, USED ON<br />

PACKAGED SERVICE<br />

ES3FP CUSTOM CALLING PACKAGE -<br />

CALL FORWARDING - CALL<br />

WAITING - SPEED CALLING 8<br />

CODE & 3-WAY CALLING -<br />

FEATURE INCLUDING A<br />

PACKAGE; TELECHOICE -<br />

RESIDENCE<br />

ESADX CALL WAITING - SPEED<br />

CALLING - 8 CODE & CALL<br />

FORWARDING - 2ND RATE<br />

LEVEL<br />

ESRDX CUSTOM CALLING PACKAGE -<br />

CALL FORWARDING - SPEED<br />

CALLING 8 CODE - 3-WAY<br />

CALLING - 2ND RATE<br />

LEVEL;IN CENTRAL, USED ON<br />

PACKAGED SERVICE<br />

ET8DX CALL WAITING - SPEED<br />

CALLING - 8 CODE - 3-WAY<br />

CALLING - 2ND RATE LEVEL;<br />

IN CENTRAL, USED ON<br />

PACKAGED SERVICE


EZTFP CALL WAITING - CALL<br />

FORWARDING - 3-WAY<br />

CALLING - SPEED CALLING - 8<br />

CODE & 30 CODE - FEATURE<br />

INCLUDED IN A PACKAGE;<br />

TELECHOICE PERCENT<br />

DISCOUNT<br />

N6SOX ROUTING THROUGH<br />

CONTROL OFF - NON-<br />

SELECTIVE ROUTING -<br />

OUTGOING TRUNK<br />

ARRANGEMENT -<br />

INDEPENDENT TERRITORY<br />

ES5FP CUSTOM CALLING PACKAGE -<br />

CALL FORWARDING - CALL<br />

WAITING - SPEED CALLING 30<br />

CODE & 3-WAY CALLING -<br />

FEATURE INCLUDED IN A<br />

PACKAGE; TELECHOICE -<br />

RES<br />

ESMFP CALL FORWARDING -<br />

VARIABLE - FEATURE<br />

INCLUDED IN A PACKAGE;<br />

TELECHOICE - RESIDENCE<br />

EVDTC CALL FORWARDING - DON'T<br />

ANSWER; TELECHOICE<br />

DISCOUNT<br />

N6S1X ROUTING THROUGH<br />

CONTROL OFF - NON-<br />

SELECTIVE ROUTING -<br />

INCOMING TRUNK<br />

ARRANGEMENT -<br />

INDEPENDENT TERRITORY<br />

RCFGB REMOTE CALL FORWARDING<br />

- BUS FLAT - INTERLATA<br />

RCFHA REMOTE CALL FORWARDING<br />

- RES FLAT - INTRALATA<br />

RCFHB REMOTE CALL FORWARDING<br />

- RES FLAT - INTERLATA<br />

RCFRL REMOTE CALL FORWARDING<br />

- RESIDENCE - FIRST ACCESS<br />

PATH; FLAT LOCAL CALL<br />

FORWARDING; IN CENTRAL-<br />

NONSTANDARD-USED AS<br />

MESSAGE-USE 'H'SUFFIX<br />

RCFVL REMOTE CALL FORWARDING<br />

- BUSINESS - FIRST ACCESS<br />

PATH; FLAT LOCAL CALL<br />

FORWARDING; IN CENTRAL-<br />

NONSTANDARD-USED AS<br />

MESSAGE-USE 'H' SUFFIX


RCFW<br />

G<br />

REMOTE CALL FORWARDING<br />

- WATS - FIRST ACCESS<br />

PATH; INTERSTATE-<br />

INTRAEXCHANGE; MARKET<br />

EXPANSION LINE; IN<br />

CENTRAL-NONSTANDARD<br />

USE 'T' SUFFIX<br />

RDEXS REMOTE CALL FORWARDING<br />

RFA REMOTE CALL FORWARDING<br />

- ADDITIONAL ACCESS PATH -<br />

2ND RATE LEVEL - FOR NNX<br />

SPLITS<br />

ES6DX CALL WAITING - SPEED<br />

CALLING - 8 CODE - 2ND<br />

RATE LEVEL; IN CENTRAL,<br />

USED ON PACKAGED<br />

SERVICE<br />

HNE NON PUBLISHED LISTING;<br />

USED WITH PACKAGED<br />

SERVICE - TELECHOICE<br />

HU5 CALL WAITING & 3-WAY<br />

CALLING; USED ON<br />

PACKAGED SERVICE<br />

HUK CALL WAITING - CALL<br />

FORWARDING; USED ON<br />

PACKAGED SERVICE<br />

HUN CALL WAITING - CALL<br />

FORWARDING - 3-WAY<br />

CALLING - SPEED CALLING - 8<br />

CODE & 30 CODE; USED ON<br />

PACKAGED SERVICE<br />

HUV CALL WAITING - SPEED<br />

CALLING - 30 CODE; USED ON<br />

PACKAGED SERVICE<br />

NLTFP NON LIST - FEATURE<br />

INCLUDED IN A PACKAGE;<br />

TELECHOICE - RES.<br />

NPUFP NON PUBLISHED - FEATURE<br />

INCLUDED IN A PACKAGE;<br />

TELECHOICE - RES.<br />

NPUTR NON PUBLISHED - CHANGE<br />

FOR DURATION OF DIR WHEN<br />

CHANGED TO LISTED<br />

SERVICE<br />

RLTFP CHARGE - LISTING - RES -<br />

FEATURE INCLUDED IN A<br />

PACKAGE; TELECHOICE -<br />

RES.<br />

R25 RESERVED NUMBER<br />

REQUEST - EACH<br />

TELEPHONE NUMBER<br />

RESERVED


V4DXB VOICE MAILBOX - WITH CALL<br />

FORWARDING - BUSY LINE -<br />

DON'T ANSWER, MESSAGE<br />

WAITING AUDIBLE & VISUAL<br />

INDICATOR - DISCOUNTED<br />

SERVICE<br />

V4DXX VOICE MAILBOX - 3RD RATE<br />

LEVEL - DISCOUNTED<br />

SERVICE<br />

V5D MAILBOX PARTITIONING -<br />

DISCOUNTED SERVICE<br />

V6D MESSAGE NOTIFICATION -<br />

WAITING NOTIFICATION TO<br />

DIFFERENT LOCATION -<br />

DISCOUNTED SERVICE<br />

VTMMX CUSTOM REPORT TRAFFIC<br />

STUDY - TRACKING MAILBOX<br />

- CALLS ROUTED TO MAILBOX<br />

- PER BUTTON ROUTED<br />

VTMNX CUSTOM REPORT TRAFFIC<br />

STUDY - TRACKING MAILBOX<br />

- CALLS ROUTED TO NUMBER<br />

- PER BUTTON ROUTED<br />

KDBLD INCOMING CALLS<br />

MANAGEMENT REPORT<br />

SERVICE - BASIC - BASED ON<br />

VOLUME - 1 PER CENT<br />

SAMPLE - DAILY<br />

KDBND INCOMING CALLS<br />

MANAGEMENT REPORT<br />

SERVICE - BASIC - BASED ON<br />

VOLUME - 10 PER CENT<br />

SAMPLE - DAILY<br />

KDDLD INCOMING CALLS<br />

MANAGEMENT REPORT<br />

SERVICE - DID/PBX - BASED<br />

ON VOLUME - 1 PER CENT<br />

SAMPLE - DAILY<br />

KDDND INCOMING CALLS<br />

MANAGEMENT REPORT<br />

SERVICE - DID/PBX - BASED<br />

ON VOLUME - 10 PER CENT<br />

OWMM<br />

X<br />

SAMPLE - DAILY<br />

MAINTENANCE - OPTIONAL<br />

WIRE PLAN - MULTILINE SVC -<br />

RESIDENCE


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC010704-4 Eliminate Access Line USOCs from Qwest’s<br />

offering<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Provisioning Resale<br />

Qwest will be eliminating attached Access Line USOCs from it’s offerings. These USOCs have no end users.<br />

Status History<br />

Campbell, Bill<br />

Van Dusen, Janean<br />

Van Dusen, Janean<br />

Macy, Cindy<br />

Development<br />

2/18/04<br />

Originator Company Name:<br />

01/07/04 - CR Submitted<br />

01/08/04 - CR Acknowledged<br />

1/9/04 - Contact originator to discuss CR<br />

1/19/03 - Discussed CR with originator<br />

1/21/03 - Jan <strong>CMP</strong> meeting minutes will be posted to the database<br />

2/18/04 -Feb <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the project meeting section<br />

Report Line Number<br />

Qwest Communications<br />

<strong>Product</strong>s<br />

Impacted<br />

Project <strong>Meeting</strong>s<br />

February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen – Qwest provided status. This CR tentative implementation date is May 28. The USOCs have been updated and a new<br />

spreadsheet can be sent out. This CR will move to Development Status.<br />

________________________________________________________________________________<br />

January 21, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen – Qwest this CR is effective <strong>March</strong> 31, <strong>2004</strong>. There are currently no end users. This list of USOCs is attached to the CR.<br />

This CR will move to Presented Status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

10<br />

PC010704-4<br />

Page 22 of 32<br />

Attachment F


USOC Description<br />

RSXC1 RATE STABILIZED SERVICE -<br />

COMPLEX BUS FLAT - PLAN<br />

1 - DOES NOT INCLUDE LINE<br />

RSXC2 RATE STABILIZED SERVICE -<br />

COMPLEX BUS FLAT - PLAN<br />

2 - DOES NOT INCLUDE LINE<br />

RSXC3 RATE STABILIZED SERVICE -<br />

COMPLEX BUS FLAT - PLAN<br />

3 - DOES NOT INCLUDE LINE<br />

RSXC4 RATE STABILIZED SERVICE -<br />

COMPLEX BUS FLAT - PLAN<br />

4 - DOES NOT INCLUDE LINE<br />

RSXC5 RATE STABILIZED SERVICE -<br />

COMPLEX BUS FLAT - PLAN<br />

5 - DOES NOT INCLUDE LINE<br />

RSXS1 RATE STABILIZED SERVICE -<br />

SIMPLE BUS FLAT - PLAN 1 -<br />

DOES NOT INCLUDE LINE<br />

RSXS2 RATE STABILIZED SERVICE -<br />

SIMPLE BUS FLAT - PLAN 2 -<br />

DOES NOT INCLUDE LINE<br />

RSXS3 RATE STABILIZED SERVICE -<br />

SIMPLE BUS FLAT - PLAN 3 -<br />

DOES NOT INCLUDE LINE<br />

RSXS4 RATE STABILIZED SERVICE -<br />

SIMPLE BUS FLAT - PLAN 4 -<br />

DOES NOT INCLUDE LINE<br />

RSXS5 RATE STABILIZED SERVICE -<br />

SIMPLE BUS FLAT - PLAN 1 -<br />

DOES NOT INCLUDE LINE<br />

1FBCN FLAT - TERMINATING AT<br />

CONC<br />

8SS 8 PARTY FLAT RESIDENCE -<br />

CONNECTED TO URBAN<br />

ZONE RATE AREA FACILITY<br />

AL6 FLAT - WITH FEATURE<br />

PACKAGE; TEENLINK<br />

AL62H FLAT - USAGE PACKAGE -<br />

TOLL RESTRICTION, THREE-<br />

WAY CALLING TEENLINK<br />

AL62J FLAT - USAGE PACKAGE -<br />

TOLL RESTRICTION, CALL<br />

WAITING TEENLINK<br />

AL62K FLAT - USAGE PACKAGE -<br />

TOLL RESTRICTION, THREE<br />

WAY CALLING, CALL<br />

WAITING TEENLINK


AL63B FLAT - WITH 3 FEATURE<br />

PACKAGE; TOLL<br />

RESTRICTION, TONE<br />

DIALING & 3-WAY CALLING;<br />

TEENLINK<br />

AL63C FLAT - WITH 3 FEATURE<br />

PACKAGE; CALL WAITING,<br />

TOLL RESTRICTION & TONE<br />

DIALING; TEENLINK<br />

AL63D FLAT - WITH 3 FEATURE<br />

PACKAGE; CALL WAITING,<br />

TONE DIALING & 3-WAY<br />

CALLING; TEENLINK<br />

AL63E FLAT - WITH 3 FEATURE<br />

PACKAGE; DIRECTORY<br />

ASSISTANCE ALLOW, TONE<br />

DIALING, 3-WAY CALLING<br />

AL63F FLAT - WITH 3 FEATURE<br />

PACKAGE; CALL WAITING,<br />

DIRECTORY ASSISTANCE<br />

ALLOW & TONE DIALING<br />

AL63G FLAT - WITH 3 FEATURE<br />

PACKAGE; DIRECTORY<br />

ASSISTANCE ALLOW, TOLL<br />

RESTRICTION & TONE<br />

DIALING


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC020404-1 Grandparent Measured Service Plans in<br />

South Dakota, Bus and Res<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Resale<br />

Residence - Eliminate USOCs R1M, AKR, RWG, AWJ, RWH & AWQ after convert to USOCs RWV & AWV<br />

Business - Eliminate USOC B1M after convert to new Measured USOC LMB<br />

Status History<br />

Campbell, Bill<br />

Van Dusen, Janean<br />

Van Dusen, Janean<br />

Andreen, Doug<br />

Development<br />

2/18/04<br />

Originator Company Name:<br />

02/04/04 - CR Submitted<br />

02/04/04 - CR Acknowledged<br />

2/10/04 - Held clarification call<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

2/18/04 - Status changed to Development<br />

030904 - Qwest initiated notification PROD.03.09.04.F.01448.GrandparentMS_USOCs_SD<br />

Report Line Number<br />

Qwest Communications<br />

Project <strong>Meeting</strong>s<br />

2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen, Qwest stated that the USOCs would be grandparented and eliminated at the same time since new USOCs will be<br />

implemented. The effective date will be April 21. The new USOCs are provided on the CR. The CR will move to Development status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

11<br />

<strong>Product</strong>s<br />

Impacted<br />

PC020404-1<br />

Page 23 of 32<br />

Attachment F


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC020404-2 Grandparent Measured Service Plans in<br />

Minnesota, Bus and Res<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Grandparent USOCs R1M, AKR & 1MR<br />

Expected Deliverable:<br />

04-21-04<br />

Status History<br />

Campbell, Bill<br />

Van Dusen, Janean<br />

Van Dusen, Janean<br />

Sanchez-Steinke, Linda<br />

Presented<br />

2/18/04<br />

Originator Company Name:<br />

Report Line Number<br />

Wholesale ProdProc Resale<br />

Qwest Communications<br />

02/04/04 - CR Submitted<br />

02/04/04 - CR Acknowledged<br />

02/06/04 - Held Clarification <strong>Meeting</strong><br />

02/18/04 - February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

03/09/04 - Qwest sent product notification PROD.03.09.04.F.01449.GrandparentMS_USOCsMN_Res Level 4 proposed effective 4/23/04<br />

<strong>Product</strong>s<br />

Impacted<br />

Project <strong>Meeting</strong>s<br />

02/18/04 February <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen with Qwest presented this CR and said that the USOCs will be grandparented on 4/21/04. This CR will be moved to Presented<br />

Status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

12<br />

PC020404-2<br />

Page 24 of 32<br />

Attachment F


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC020404-3 Grandparent Measured Service Plans in<br />

Utah, Bus and Res<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Residence - Grandparent USOCs 1MR, AHR & 2MR.<br />

Convert USOCs LW1 & AKN to new Measured USOCs RWV & AWV<br />

Eliminate USOCs LW1, AKN & 21M<br />

Business - Convert USOCs THB & THF to USOC TMB<br />

Eliminate USOCs THB & THF<br />

Status History<br />

Campbell, Bill<br />

Van Dusen, Janean<br />

Van Dusen, Janean<br />

Macy, Cindy<br />

Presented<br />

2/18/04<br />

Originator Company Name:<br />

02/04/04 - CR Submitted<br />

02/04/04 - CR Acknowledged<br />

2/9/04 - Discussed and clarified CR with orginator<br />

2/18/04 -Feb <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the project meeting section<br />

Report Line Number<br />

Wholesale ProdProc Resale<br />

Qwest Communications<br />

Project <strong>Meeting</strong>s<br />

February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen – Qwest provided status. The Business portion of this CR has been cancelled. Residence still applies with a target<br />

implementation date of April 21. This CR will move to Presented Status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

13<br />

<strong>Product</strong>s<br />

Impacted<br />

PC020404-3<br />

Page 25 of 32<br />

Attachment F


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC020404-4 Grandparent ValueChoice, 2-Line<br />

ValueChoice , and PrivacyPak<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Resale<br />

ValueChoice (PCV6X), 2-Line ValueChoice (PGOVB), and PrivacyPak (FFKX2)will be grandparented and no longer offered for sale.<br />

2/11/04 This CR will not include Northern Idaho at this time.<br />

Status History<br />

Campbell, Bill<br />

Van Dusen, Janean<br />

Van Dusen, Janean<br />

Andreen, Doug<br />

Presented<br />

2/18/04<br />

Originator Company Name:<br />

02/04/04 - CR Submitted<br />

02/04/04 - CR Acknowledged<br />

2/10/04 - Held clarification call<br />

2/18/04 -February <strong>CMP</strong> <strong>Meeting</strong> - <strong>Meeting</strong> minutes will be posted to this CR's Project <strong>Meeting</strong>s section.<br />

2/18/04- Status changed to Presented<br />

Report Line Number<br />

Qwest Communications<br />

<strong>Product</strong>s<br />

Impacted<br />

Project <strong>Meeting</strong>s<br />

2/18/04 <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen, Qwest stated that this CR affects all states except northern Idaho. The effective date is May 17 and the USOC list is provided<br />

in the CR. The CR will move to development.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

14<br />

PC020404-4<br />

Page 26 of 32<br />

Attachment F


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC022604-1 Elimination of ATM USOCs Clarification Wholesale ProdProc Resale<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

The attached list of ATM USOCs will be eliminated 6/15/<strong>2004</strong>. There are no customers with these USOCs.<br />

Expected Deliverable:<br />

6/15/04<br />

Status History<br />

Campbell, Bill<br />

Van Dusen, Janean<br />

Van Dusen, Janean<br />

Sanchez-Steinke, Linda<br />

02/26/04 - CR Submitted<br />

02/27/04 - CR Acknowledged<br />

Information Current as of:<br />

Report Name:<br />

2/26/04<br />

Originator Company Name:<br />

Report Line Number<br />

Qwest Communications<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

15<br />

<strong>Product</strong>s<br />

Impacted<br />

PC022604-1<br />

Page 27 of 32<br />

Attachment F


CTNH1<br />

CTNH2<br />

CTNH3<br />

CTNH4<br />

CTNH5<br />

CTNH6<br />

CTNH7<br />

CTNHM<br />

CTNJ1<br />

CTNJ2<br />

CTNJ4<br />

CTNJ6<br />

CTNJ7<br />

CTNK1<br />

CTNK2<br />

CTNK6<br />

CTNK7<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 1 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 149 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 2 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 149 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 3 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 149 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 4 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 149 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 5 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - 149 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 6 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - 149 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 7 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 149 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - MONTH-TO-<br />

MONTH - INCREMENTAL CELL TRANSFER - PER<br />

CONSTANT(PEAK) BIT RATE - PER 149 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 1 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 75 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 2 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 75 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 4 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 75 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 6 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 75 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 7 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 75 KBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 1 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 1.787 MBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 2 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 1.787 MBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 6 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 1.787 MBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - 7 YEAR -<br />

INCREMENTAL CELL TRANSFER - PER CONSTANT (PEAK)BIT<br />

RATE - PER 1.787 MBPS


ATM CELL RELAY SERVICE - CELL TRANSFER - MONTH TO<br />

CTNKM MONTH - INCREMENTAL CELL TRANSFER - PER CONSTANT<br />

(PEAK)BIT RATE - PER 1.787 MBPS<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - VARIABLE<br />

CTNN1 INCREMENTAL BIT RATE - REAL TIME - 1.544 MBPS - 12 MONTH<br />

PLAN<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - VARIABLE<br />

CTNN2 INCREMENTAL BIT RATE - REAL TIME - 1.544 MBPS - 24 MONTH<br />

PLAN<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - VARIABLE<br />

CTNN3 INCREMENTAL BIT RATE - REAL TIME - 1.544 MBPS - 36 MONTH<br />

PLAN<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - VARIABLE<br />

CTNN4 INCREMENTAL BIT RATE - REAL TIME - 1.544 MBPS - 48 MONTH<br />

PLAN<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - VARIABLE<br />

CTNN5 INCREMENTAL BIT RATE - REAL TIME - 1.544 MBPS - 60 MONTH<br />

PLAN<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - VARIABLE<br />

CTNN6 INCREMENTAL BIT RATE - REAL TIME - 1.544 MBPS - 72 MONTH<br />

PLAN<br />

ATM CELL RELAY SERVICE - CELL TRANSFER - VARIABLE<br />

CTNN7 INCREMENTAL BIT RATE - REAL TIME - 1.544 MBPS - 84 MONTH<br />

PLAN<br />

ATM CELL RELAY SERVICE - CELL TRANSFER -VARIABLE<br />

CTNNM INCREMENTAL BIT RATE - REAL TIME - 1.544 MBPS - MONTH-TO-<br />

MONTH


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC050503-2 Grandfather SVDS in all state tariffs<br />

including FCC tariff.<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

SVDS will be grandfathered in all states effective 8/15/03.<br />

Expected Deliverable:<br />

Grandfather SVDS effective 8/15/03<br />

Status History<br />

05/05/03 - CR Submitted<br />

05/05/03 - Acknowledged CR<br />

05/13/03 - Claification <strong>Meeting</strong><br />

05/21/03 - Presented at <strong>CMP</strong> <strong>Meeting</strong><br />

06/03/03 - Input <strong>Meeting</strong><br />

06/18/03 - Discussed at <strong>CMP</strong> <strong>Meeting</strong><br />

07/16/03 - CR Discussed at <strong>CMP</strong> Monthly <strong>Meeting</strong><br />

8/21/03 - Discussed at <strong>CMP</strong> <strong>Meeting</strong><br />

9/17/03 - Sep <strong>CMP</strong> meeting minutes will be posted to the database<br />

10/17/03 - Oct <strong>CMP</strong> meeting minutes will be posted to the database<br />

11/19/03 - Nov <strong>CMP</strong> meeting minutes will be posted to the database<br />

12/17/03 - Dec <strong>CMP</strong> meeting minutes will be posted to the database<br />

1/21/03 - Jan <strong>CMP</strong> meeting minutes will be posted to the database<br />

2/18/04 -Feb <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the project meeting section<br />

Project <strong>Meeting</strong>s<br />

February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen – Qwest provided status. This CR is still pending FCC approval.<br />

This CR will remain in Development Status.<br />

Wholesale ProdProc Provisioning Resale, UNE-P<br />

_________________________________________________<br />

<strong>CMP</strong> <strong>Meeting</strong> 1/21/04<br />

Janean Van Dusen – Qwest advised this CR is still waiting for a date. It is in front of the FCC pending approval. This CR will remain in<br />

Development Status.<br />

_____________________________________________________<br />

<strong>CMP</strong> <strong>Meeting</strong> 12/17/03 -<br />

Janean VanDusen – Qwest advised there is not an effective date for this CR as of yet. The CR will remain in Development status.<br />

_______________________________________________________<br />

<strong>CMP</strong> <strong>Meeting</strong> 11/19/03<br />

Janean VanDusen – Qwest advised there is not an effective date for this CR as of yet. The CR will remain in Development status.<br />

________________________________________________________<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

10-15-03<br />

Janean VanDusen – Qwest advised there is not an effective date for this project as of yet. This CR will remain in Development Status.<br />

_______________________________________________________<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

9-17-03<br />

Janean advised the FCC tariff does not have an effective date as of yet. This CR will stay in Development status.<br />

_____________________________________________________________________<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

08-20-03<br />

Van Dusen-Qwest stated that no precise implementation date was available.<br />

============================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

Campbell, Bill<br />

Van Dusen, Janean<br />

Van Dusen, Janean<br />

Macy, Cindy<br />

Information Current as of:<br />

Report Name:<br />

Development<br />

5/5/03<br />

Originator Company Name:<br />

Report Line Number<br />

Qwest Communications<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

16<br />

<strong>Product</strong>s<br />

Impacted<br />

PC050503-2<br />

Page 28 of 32<br />

Attachment F


07-16-03<br />

Van Dusen-Qwest stated that the implementation date would be pushed back from 8/15.<br />

===========================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

06-18-03<br />

Van Dusen-Qwest stated that the implementation was scheduled for August although it may slip. She recommended that that CR move to<br />

Development.<br />

==========================================================<br />

Input <strong>Meeting</strong> – 06-03-03<br />

Attendees<br />

Matt White – Qwest<br />

Janean Van Dusen – Qwest<br />

Skip Olson – Qwest<br />

Barb Newton – Qwest<br />

Richard Journey – Qwest<br />

Mallory Paxton – Qwest<br />

Dalene Fuqua – Qwest<br />

Bonnie Johnson – Eschelon<br />

White-Qwest welcomed the attendees, described the purpose of the meeting and asked Van Dusen-Qwest to describe the CRs. Van Dusen-<br />

Qwest described the CRs.<br />

050703-6<br />

Johnson-Eschelon asked if this CR would follow the same format as the previous grandfathering CRs. Fuqua-Qwest and Newton-Qwest stated<br />

that it would.<br />

050503-2<br />

Johnson-Eschelon asked if grandfathering and grandparenting the same and if they were different from retiring. Van Dusen-Qwest stated that<br />

grandfathering and grandparenting were synonymous and that they did not mean the same thing as retiring. Johnson-Eschelon asked if only new<br />

customers would be impacted. Van Dusen-Qwest stated that was correct.<br />

050503-1<br />

Johnson-Eschelon asked what switchnet 56 was. Olson-Qwest stated that it was digital data just like ISDN. He explained that switchnet can only<br />

run at 58 kbps and that there is a lack of demand for this product.<br />

==========================================================<br />

<strong>CMP</strong> <strong>Meeting</strong><br />

05-21-03<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC050503-2<br />

Page 29 of 32<br />

Attachment F


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC050703-6 Grandfather Measured Service plans in CO,<br />

ID North, NM, ND<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

The following Measured Service Plans will be grandfathered effective 8/15/03:<br />

Colorado:<br />

LW1- Main line .05 first .02 additional<br />

AKN- additional line<br />

1MR- Main line .11 per call after 50 call allowance<br />

AHR- additional line<br />

1MB- Individual Message rate line 50 allowable .11 each additional<br />

ALS- additional line<br />

Idaho North:<br />

LW1<br />

1MR<br />

New Mexico:<br />

LW1<br />

AKN<br />

North Dakota:<br />

RVJ- Main line .05 1st minute .01 each additional<br />

AKN<br />

Status History<br />

05/07/03 - CR Submitted<br />

05/08/03 - CR Acknowledged<br />

5/13/03 - Scheduled Clarification Call for 5/15/03<br />

5/15/03 - Held Clarification Call<br />

5/21/03 - May <strong>CMP</strong> <strong>Meeting</strong> Minutes will be posted to the database<br />

06/03/03 - Input <strong>Meeting</strong><br />

6/18/03 - June <strong>CMP</strong> P/P meeting mintues will be posted to the database<br />

7/16/03 - July <strong>CMP</strong> monthly meeting will be posted to the database<br />

8/20/03 - Aug <strong>CMP</strong> meeting minutes - see notes<br />

9/17/03 - Sep meeting minutes will be posted to the database<br />

10/13/03 - Ad Hoc meeting held to review changes to CR<br />

10/15/03 - Oct <strong>CMP</strong> meeting minutes will be posted to the database<br />

11/7/03 - Final Notice PROD.11.07.03.F0128.FNL_GrandparentMS<br />

11/19/03 - Nov <strong>CMP</strong> meeting minutes will be posted to the databas<br />

12/5/03 - Retraction of Grandparenting notification PROD.12.05.03.F.01141.RetractGrandparentMS_NM<br />

12/17/03 - Dec <strong>CMP</strong> notes will be posted to the database<br />

1/21/03 - Jan <strong>CMP</strong> meeting minutes will be posted to the database<br />

2/18/04 -Feb <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the project meeting section<br />

Project <strong>Meeting</strong>s<br />

Campbell, William<br />

Van Dusen, Janean<br />

Van Dusen, Janean<br />

Macy, Cindy<br />

Wholesale ProdProc Resale<br />

February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen – Qwest provided status. New Mexico Residence is on hold and New Mexico Business is scheduled for implementation <strong>March</strong><br />

22. Idaho North is on hold, Colorado was cancelled and North Dakota was effective January 30 with the IT work complete with 15.0. This CR will<br />

remain in CLEC Test Status.<br />

______________________________________________<br />

January 21, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong><br />

Janean Van Dusen – Qwest recapped that Colorado was cancelled, Idaho was on hold, ND was effective January 30, <strong>2004</strong> but it won’t be<br />

implemented until 15.0 gets installed. New Mexico was retracted last month due to the commission not approving it yet. NM now has an effective<br />

date of January 30 so Qwest would like to implement this as a Level 1. The CLECs agreed. This CR will remain in CLEC Test Status.<br />

_______________________________________________<br />

December 17, 2003 <strong>CMP</strong> <strong>Meeting</strong> notes<br />

Information Current as of:<br />

Report Name:<br />

CLEC Test<br />

12/1/03<br />

Originator Company Name:<br />

Report Line Number<br />

Qwest Communications<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

17<br />

<strong>Product</strong>s<br />

Impacted<br />

PC050703-6<br />

Page 30 of 32<br />

Attachment F


Janean VanDusen – Qwest advised this CR will be implemented December 1, 2003. NM was retracted by the state PUC and the retraction notice<br />

went out. This CR will remain in CLEC Test status.<br />

_________________________________________<br />

November 19, 2003 <strong>CMP</strong> <strong>Meeting</strong><br />

Janean VanDusen – Qwest advised this CR will be implemented December 1, 2003. This CR will remain in Development status, until December 1<br />

and then the CLECs agreed that Qwest could change the status to CLEC Test.<br />

____________________________________________________<br />

October 15, 2003<br />

Janean VanDusen – Qwest advised this project is scheduled for implementation 11-28-03. A CLEC ad hoc meeting was held as there were some<br />

changes made to New Mexico and South Dakota. These changes were reviewed during the ad hoc meeting. This CR will remain in Development<br />

Status.<br />

______________________________________<br />

September 17, 2003<br />

Janean advised NM and ND are scheduled for 10/20/03. Idaho North is on hold and Colorado has been cancelled. This CR will remain in<br />

Development status.<br />

__________________________________________<br />

August 20, 2003 Monthly <strong>Meeting</strong> minutes<br />

Janean VanDusen-Qwest advised this CR was delayed and is now scheduled for implementation on October 15, 2003.<br />

_______________________________________________________________<br />

July 16, 2003 Monthly <strong>Meeting</strong> minutes<br />

Janean VanDusen-Qwest advised this CR is scheduled and on track for implementation August 15, 2003.<br />

____________________________________________________________________________________________________<br />

June 18, 2003 Monthly <strong>Meeting</strong> minutes<br />

Janean VanDusen – Qwest advised there was a CLEC input meeting held and this CR is on track for deployment in August.<br />

______________________________________________________________________________________________________________________<br />

______<br />

Input <strong>Meeting</strong> – 06-03-03<br />

Attendees<br />

Matt White – Qwest<br />

Janean Van Dusen – Qwest<br />

Skip Olson – Qwest<br />

Barb Newton – Qwest<br />

Richard Journey – Qwest<br />

Mallory Paxton – Qwest<br />

Dalene Fuqua – Qwest<br />

Bonnie Johnson – Eschelon<br />

White-Qwest welcomed the attendees, described the purpose of the meeting and asked Van Dusen-Qwest to describe the CRs. Van Dusen-<br />

Qwest described the CRs.<br />

050703-6<br />

Johnson-Eschelon asked if this CR would follow the same format as the previous grandfathering CRs. Fuqua-Qwest and Newton-Qwest stated<br />

that it would.<br />

050503-2<br />

Johnson-Eschelon asked if grandfathering and grandparenting the same and if they were different from retiring. Van Dusen-Qwest stated that<br />

grandfathering and grandparenting were synonymous and that they did not mean the same thing as retiring. Johnson-Eschelon asked if only new<br />

customers would be impacted. Van Dusen-Qwest stated that was correct.<br />

050503-1<br />

Johnson-Eschelon asked what switchnet 56 was. Olson-Qwest stated that it was digital data just like ISDN. He explained that switchnet can only<br />

run at 58 kbps and that there is a lack of demand for this product.<br />

______________________________________________________________________________________________________________________<br />

___________<br />

May 21, 2003 <strong>CMP</strong> <strong>Meeting</strong> Minutes<br />

Van Dusen – Qwest presented the CR and suggested an input meeting on June 3 at 11 AM MT.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

PC050703-6<br />

Page 31 of 32<br />

Attachment F


CR # Title Status Organization Area<br />

Status Date<br />

Impacted<br />

PC120303-3 Grandparent Interstate SHNS and SST<br />

USOCs<br />

Director:<br />

Originator:<br />

Owner:<br />

CR PM:<br />

Description Of Change<br />

Wholesale ProdProc Resale<br />

Excel spreadsheet of 1302 Interstate and SHNS USOCs being grandparented on 3/1/04. There are three types of elements being grandparented;<br />

ports, shelves and port to port connecting agreements.<br />

-Ports with month to month rates are not being affected. We are grandparenting 1,2,3 and 5 year rated ports.<br />

-Shelves are being replaced by a fully loaded node. The currently tariffed nodes will become these fully loaded nodes once shelves are<br />

grandfathered.<br />

-If a customer would have ordered a port to port connecting agreement, once that is grandparented, they will be able to order the currently tariffed<br />

COCC (central office connecting channel).<br />

Expected Deliverable: 03/01/<strong>2004</strong><br />

Status History<br />

Campbell, Bill<br />

Van Dusen, Janean<br />

Van Dusen, Janean<br />

Macy, Cindy<br />

CLEC Test<br />

2/18/04<br />

Originator Company Name:<br />

12/03/03 CR Submitted<br />

12/05/03 CR Acknowledged<br />

12/8/03 Contacted Janean VanDusen<br />

12/10/03 - Clarified CR<br />

12/17/03 - Dec <strong>CMP</strong> meeting notes will be posted to the database<br />

1/21/03 - Jan <strong>CMP</strong> meeting minutes will be posted to the database<br />

1/16/04 - PROD.01.16.04.F.01240.ResaleSST_SHNS level 4 implementation date <strong>March</strong> 1, <strong>2004</strong><br />

2/13/04 - PROD.02.12.04.F.01354.FNL_ResaleSST_SHNS<br />

2/18/04 -Feb <strong>CMP</strong> <strong>Meeting</strong> notes will be posted to the project meeting section<br />

Report Line Number<br />

Qwest Communications<br />

<strong>Product</strong>s<br />

Impacted<br />

Project <strong>Meeting</strong>s<br />

February 18, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong> notes:<br />

Janean Van Dusen – Qwest provided status. The final notification went out February 13. There are two effective dates with this CR. One is<br />

<strong>March</strong> 12 and the other is <strong>March</strong> 24. This CR will move to CLEC Test Status.<br />

______________________________________<br />

January 21, <strong>2004</strong> <strong>CMP</strong> <strong>Meeting</strong> notes:<br />

Janean Van Dusen – Qwest advised this CR is effective <strong>March</strong> 1, <strong>2004</strong>. The USOC list is on the customer notification web site. It was noticed on<br />

January 16, <strong>2004</strong>. This CR will move to Development Status.<br />

________________________________________<br />

December 17, 2003 <strong>CMP</strong> <strong>Meeting</strong> notes:<br />

Janean Van Dusen – Qwest reported that this is a new CR that is grandfathering USOCs related to these services. The intent is to streamline the<br />

number of USOCs associated to this product. There is a spreadsheet with 1302 USOCs on it. This spreadsheet is too large to include as part of<br />

the CR but it will be sent out with the Notification. This CR will move to Presented status.<br />

Information Current as of:<br />

Report Name:<br />

Friday, <strong>March</strong> 12, <strong>2004</strong><br />

006 Detailed Qwest Initiated ProdProc OF FINAL JUL 2002 ATTA<br />

CR #<br />

18<br />

PC120303-3<br />

Page 32 of 32<br />

Attachment F


<strong>Product</strong> & <strong>Process</strong> Change Management <strong>Process</strong><br />

Attachment G – Proposed Modifications to <strong>CMP</strong><br />

Framework<br />

3/12/04 © <strong>2004</strong>, Qwest Corporation

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!