Wholesale: Products & Services

Open Product/Process CR PC013002-1 Detail

Description Of Change

Modification after Clarification Meeting:

Establish a process to request the removal of bridge-taps.

Status History

Project Meetings

February 6, 2002 9:00 a.m. (MT) Conference Call 877-564-8688 PC013002-1, Removing Bridge Taps from LADA Circuits

Attendees:

Ric Martin, Qwest Neil Houston, Qwest Jeff Cook, Qwest Cindy Buckmaster, Qwest (Part Time) Steve Kast, Qwest (Follow-up conference call) Doug Worden, Vanion, Inc.

Introduction of Attendees Introductions of the participants on the Conference Call were made and the purpose of the call discussed.

Review Requested (Description of) Change Doug advised that on LADA Circuits, which are for low speed data, but can handle high speed they want the ability to request the removal of bridge taps is requested. Doug clarified that LADA was 2-wire dry pair cable. Qwest indicated that this was data/data non-load service. It was clarified that this was for point to point service passing through the same wire center. Doug indicated that he had no way to order repair and provided an example of where Qwest moved a pedestal and added a bridge-tap, which has disrupted a customer’s service. Doug clarified that for this service Vanion was reselling Private Line services for High-Speed data. He also indicated that Vanion was also a Facility Based CLEC. Cindy Buckmaster joined the call and explained the Line Condition that can be ordered for UBL. However, she indicated that we need to review what was offered for Resale Qwest unable to bring Freddie Pennington, Wholesale Product Manager for Resale, into the call. Qwest indicated that they would coordinate internally and may get Doug back on an additional clarification meeting. Doug indicated that it was OK to have the CR follow the normal process, but wanted Qwest to investigate his trouble ticket CD328473 which was closed and was escalated. Doug advised that Steve Kast, Vanion Service Manager, was involved. Qwest advised that if they caused the problem and were responsible to fix it, they would look into it further. Note: it was clarified further with Doug Worden, Steve Kast and Ric Martin that Qwest was not committing to correcting the problem, but would look into it further to see if there was anything else that could be done.

Confirm Areas & Products Impacted It was confirmed that the product was for Resold Private Line . Confirm Right Personnel Involved Network personnel would be involved, but it was agreed that Process person should be the Owner. Qwest will coordinate.

Identify/Confirm CLEC’s Expectation It was confirmed that Vanion was looking for a process to request the removal of a bridge tap.

Identify any Dependent Systems Change Requests None

Establish Action Plan (Resolution Time Frame) Qwest will look into the Trouble Ticket Qwest will coordinate internal reviews of the CR.

CenturyLink Response

Vanion, Inc. Doug Worden Provisioning Manager

SUBJECT: Qwest’s Change Request Response - CR #PC013002-1 Removing Bridged Taps from LADS circuits

This letter is in response to Vanion Inc.’s Change Request PC013002-1 requesting a process for CLECs to request the removal of Bridge Taps from Local Area Data Service (LADS) circuits.

Local Area Data Service (LADS) is ordered in the Colorado Tariffs. Specifically LADS is offered in “Private Line Transport, Services Tariff, COLO. P.U.C. No. 19, Section 5.2”. LADS is described in Section 5.2.4, A.:

Service is offered only for balanced transmission of data signals conforming to the signal power limitations and other parameters specified in the applicable Technical Reference. These circuits are furnished on either a two-wire or four-wire basis, over non-loaded, metallic cable facilities.

Note the facility is non-loaded, but no reference is made to Bridged Tap. Additionally Section 5.2.4, C., 4. states:

No repair will be performed to change the electrical characteristics of the circuit, if they are within the parameters specified in the Technical Publication.

The General Regulations section of COLO. P.U.C. No. 19, Section 2.1.8 states:

It is expressly declared that metallic facilities are in continually decreasing supply and the Company is not obligated to continue to provide such facilities. Due to facility rearrangements, continued use of metallic facilities may be denied to existing customers with no obligation on the Company’s part to pay customer rearrangement costs.

As referenced above, Qwest’s Technical Publication 77314, Local Area Data Service (LADS), Issue C, July 2001 supports the Colorado Tariff on LADS. In addition to qualifying the LADS technical parameters, the General Section 1. states:

The customer should also be aware that Qwest has no obligation to continue to provide this service if suitable facilities are no longer available. Non-availability of suitable facilities may be caused by the continuing need to add new central offices and to transfer areas between serving wire centers, and the increasing use of Digital Loop Carrier technology on lines between the serving wire center and customer locations.

Vanion has stated that their high-speed data has deteriorated with changes in Qwest’s Network, allegedly from the addition of bridged tap to the circuit. LADS is not designed for high-speed data transmission and is not dependent upon the absence of bridged tap. As referenced above, in the Colorado Tariff and Technical Publication 77314, facility rearrangements could impact existing service. Also, as long as the service is within its technical parameters, repair is not required and will not be performed.

Qwest offers a variety of Unbundled Loop products that should meet Vanion’s transmission requirements. These include 2/4/ Wire Non-Loaded Loop, Basic ISDN Capable Loop, DS-1 Capable Loop, and the ADSL Qualified Loop.

Qwest will provide Vanion LADS service as described in its tariffs and technical publications. However, since LADS is not a high speed data service, Qwest declines to initiate a process to remove bridged tap from LADS and respectfully denies Vanion, Inc’s change request.

Sincerely,

Neil G. Houston Staff Advocate-Policy & Law Qwest

Cc: Mary Retka Kathleen Lucero Barry Orrel Jamal Boudhaouia

Open Product/Process CR PC061302-1 Detail

Description Of Change

Status History

Project Meetings

Qwest advised that since Vanion was not on the call, Qwest would get with Vanion independently to go over the response. Qwest reviewed its draft response with the CLEC participants. Eschelon asked how many calls does the retail customer have to make to get DSL. Qwest advised that one call is made and Qwest follows up with the customer after POTS is in service. Eschelon stated that CLECs do not get a follow-up call and the retail customer doesn’t have to call back to get DSL. Qwest confirmed that comment. Eschelon asked if this was a deny and Qwest confirmed that it was.

07/17/02 - July CMP Meeting Minutes: Vanion had to leave the CMP meeting early and asked that their CR be rolled over to the August CMP meeting for presentation. CR status is clarification.

CLEC Change Request Clarification Meeting

June 18, 2002, 11:30 a.m. (MT) Conference Call 877-564-8688 PC061302-1, Process for ordering Megabit DSL service to connect to Mega Central Hubs now installed.

Attendees: Ric Martin, Qwest Cindy Buckmaster, Qwest Jeff Cook, Qwest Steve Kast, Qwest Doug Worden, Vanion, Inc. Becky Watson, Vanion, Inc.

Introduction of Attendees Introductions of the participants on the Conference Call were made and the purpose of the call discussed

Review Requested (Description of) Change Doug reviewed Vanion’s CR. He indicated that they wanted to put in one order (LSR) for Megabit DSL service and POTS. Becky clarified that Vanion was not collocated in Qwest facilities and was not interested in the Line Sharing product. They wanted to order on the customer’s behalf. They would like to order a 1FB with DSL. They want to be able to take the customer out of dealing with Qwest. Becky indicated they currently can’t offer the DSL product because it’s a moving target on whether facilities would be available. Cindy indicated that data would not be available only if the facility can’t support it. Becky confirmed they were only interested carrying data and having Qwest as the voice provider. Cindy clarified that Vanion is looking to be able to provision the POTS circuit on copper cable versus pair gain capable to allow data service.

Confirm Areas & Products impacted It was confirmed that the area impacted was Pre-Ordering, Ordering and Provisioning. The product impacted are Resale POTS and Megabit DSL.

Confirm Right Personnel Involved Qwest indicated that they would need to include their Resale SMEs, Janean Van Dusen and Stacy Hartman.

Identify/Confirm CLEC’s Expectation Vanion’s expectation is to be able to place one LSR and be able to provision DSL on the POTS line ordered.

Identify any Dependent Systems Change Requests There are no related Systems CRs. Qwest advised that there was a similar CR issued by Eschelon, PC122701-2. Qwest requested Vanion to review the Archive Interactive Report for the CR and Qwest’s response.

Establish Action Plan (Resolution Time Frame) The CR will have the collective CLEC clarification and SME input at the July CMP meeting.

CenturyLink Response

Doug Worden Provisioning Manager Vanion, Inc.

SUBJECT: Qwest’s Change Request Response - CR #PC061302-1 Process for ordering Megabit DSL service to connect to Mega Central hubs now installed

This letter is in response to Vanion’s Change Request PC061302-1 requesting that they be allowed to place one LSR and be able to provision DSL on the POTS line ordered.

Vanion’s Change Request is similar to two (2) previously submitted Change Requests, PC122701-1, Qwest to offer line conditioning to qualify a loop for Qwest resale DSL service, and PC122701-2, Qwest to allow 1FB POTS and DSL on one LSR.

Qwest’s response to the two previous Change Requests was that basically the service was not offered to Qwest Retail customers and, therefore, was not going to be offered to Resale customers. Qwest’s responses to each CR can be reviewed in Qwest’s Product/Process CR Archive Report located at URL http://www.qwest.com/wholesale/cmp/archive.html. After additional review, Qwest’s position remains the same. It is not technically and economically feasible for Qwest Retail to offer this service at this time. Qwest does not offer pre-qualification of facilities for DSL prior to the end user’s line being in place. Current process for Retail and Resale is that two (2) orders must be issued. One (1) for the POTs and one (1) for the DSL once the POTS line is loop qualified.

At last month's CMP meeting, there was a question on the Retail process for ordering POTS and DSL. The Retail process does require 2 orders, whether it is an N (new) order or a T (transfer) order. If the end user is interested in DSL, then after the N or T order is installed, a Loop qualification is done on the N (telephone number) or the T (telephone number) and the end user is contacted to place the 2nd order, which would be a C (change) order to add the DSL service.

Sincerely,

Janean Van Dusen (801) 239-4305

Cc:

Open Product/Process CR PC072902-1 Detail

Description Of Change

Status History

Project Meetings

Allegiance advised that they had a conference call with Qwest where it was clarified the difference between requesting an extension of a jack versus a NID/DEMARC. It is Qwest’s policy that CLECs cannot request an extension to a NID/DEMARC and only in Minnesota and Oregon is it mandated that CLECs can request and extension of a Jack. Allegiance advised that based on this clarification, they would like to withdraw their CR. Qwest asked if any other CLEC would like to sponsor the CR and no CLECs expressed an interest. It was agreed that the CR would be status as withdrawn.

-

Subject: RE: CR PC072902-1 Clarification Meeting Minutes Date: Mon, 5 Aug 2002 13:41:39 -0500 From: "Wicks, Terry" To: "'Richard Martin'"

The department that we fax a form to for Southwestern Bell , to get an estimate of cost, is called the LSC (Local Service Center). This is the department that processes our LSRs.

Terry Wicks LEC Account Manager allegiancetelecom, inc 469-259-4438 terry.wicks@algx.com

CLEC Change Request Clarification Meeting

August 2, 2002 10:00 a.m. (MT) Conference Call 877-564-8688 PC072902-1, Request for estimate of cost for extending or moving a DMARC beyond the MPOE prior to doing the work

Attendees: Ric Martin, Qwest Russ Urevig, Qwest Shirley Tallman, Qwest Bob Mohr, Qwest Linda Sanchez-Steinke, Qwest Terry Wicks, Allegiance

Introduction of Attendees Introduction of the participants on the Conference Call was made and the purpose of the call discussed

Review Requested (Description of) Change Terry indicated that when Allegiance is taking a customer, they may want to move or extend the DMARC beyond the MPOE. They want to get an estimate of the cost before the work is performed. Currently they put their request in when they place the order and get billed for the work after the order is completed. Terry indicated that another ILEC has a form that they complete and submit to get an estimate before the order is submitted. Terry indicated that they have an 800 number and a fax number to which this form is sent. He believes they are dealing with the ILECs engineering department. Terry will confirm what department they deal with. The department is the LSC, Local Service Center at Southwestern Bell. Terry indicated that they were billed for the estimate and would be willing to pay for the estimate. He agreed that an estimate was acceptable with actual costs being billed per their agreement with Qwest. Russ asked if Allegiance was looking at a multi-tenant facility and looking more at an individual customer’s DMARC. Terry indicated that Allegiance is looking at extending the DMARC or sometimes moving the DMARC beyond the MPOE for an individual tenant of a multi-tenant building.

Confirm Areas & Products impacted Terry indicated that their product focus was UBL. Qwest may have to look at other products that would have the same need. It was agreed that the area impacted was Pre-Ordering and Ordering.

Confirm Right Personnel Involved Qwest confirmed that the Network department would be responsible.

Identify/Confirm CLEC’s Expectation Terry confirmed that they wanted a process to request and receive a written cost estimate for extending or moving a DMARC beyond the MPOE prior to submitting an order.

Identify any Dependent Systems Change Requests There are no systems changes associated with this request.

Establish Action Plan (Resolution Time Frame) The CR will have the collective CLEC clarification and SME input at the August CMP meeting.

Open Product/Process CR PC010302-1 Detail

Description Of Change

Qwest does not allow the provisioning of an Unbundled Loop within a colocation when an End User is serviced by a Remote Switching Unit (RSU). The orders are cancelled and a reject notice is sent to the CLEC. At this time, the CLEC has absolutely no recourse to be able to switch this customer's local service over to that CLEC. The inability to switch an End User that is serviced by a RSU over to a facility based CLEC is unacceptable and anti-competitive. The End User also has no capability to choose another carrier for local service. Allegiance has spent tremendous amounts of money to co-locate in Qwest Central Offices in order to be able to swith Qwest customers over to Allegiance facilities. Allegiance is requesting that Qwest develope a means to allow the switching of End Users service by a RSU to CLEC facilities .

Status History

Project Meetings

Subject: Re: CR Location Date: Fri, 28 Jun 2002 14:05:05 -0400 From: John Sheehan Organization: Frontier / ELI Carrier Services To: Richard Martin

Rick, Sounds fine. This can be closed.

--

Subject: CR Location Date: Fri, 28 Jun 2002 10:56:25 -0600 From: Richard Martin Organization: Qwest Communications International, Inc. To: johnsheehan@frontiercorp.com

John,

Go to URL, http://www.qwest.com/wholesale/cmp/changerequest.html

Click on, "CLEC Qwest Change Request - Product/Process Interactive Reports" to launch the interactive report. The report is in Adobe Acrobat.

When in the report, click on the blue button with CR number PC010302-1. Review Action Item No. 5.

If the response satisfies the intent of Peder's question, please advise. If further clarification is required, please let me know.

Thanks

Ric

--

Subject: Action Item 4 to CR PC010302-1 Date: Fri, 28 Jun 2002 09:28:57 -0600 From: Richard Martin Organization: Qwest Communications International, Inc. To: Mike Zulevic CC: Craig Saunders , Kelly Trachsel

Mike,

Based on our conversation regarding Action Item 4 to the subject CR, the response, which is stated below, didn't fully answer what you were looking for.

Action Item 4 Question and Answer:

Q. Covad expressed the need to have the geographical area of a RSU and the number of lines served by the RSU included in the ICONN database tool.

A. The ICONN database has not been set-up to provide the geographical area of a RSU. This is done through utilization of the DA Maps (refer to CR PC110201-1 and PC012902-1). The number of lines in a RSU will be delineated if the RSU does not share a NXX with another wire center. The number of lines associated with a Central Office NXX can be identified by performing a search on the NPA NXX under the Cetral Office Find tool located at the same URL as Action Item No. 3.

It is my understanding, from our call, that Covad would like to identify what RSUs are tied to a CO, where are the RSUs and what area do they cover.

If this is not correct, please provide further clarification.

Thanks

Ric

-- Subject: CR PC010302-1 Action Item EEL Pricing Comparison Date: Mon, 15 Apr 2002 10:38:51 -0600 From: Richard Martin Organization: Qwest Communications International, Inc. To: Terry Wicks CC: Robert Mohr , Robyn Libadia , Cindy Buckmaster

Terry,

The attached rate sheet is in response to the Action Item on your Change Request PC010302-1 requesting that Qwest provide pricing for an EEL from the Denver Dry Creek to an end-user fed from the Denver Tech Center wire center. You also requested rates for an Unbundled Loop to feed this same user from the one wire center.

The attached rates are for the EEL and UNE products for an EEL from the Drycreek office to an end-user fed from the Tech Center wire Center. As the only way to feed a customer located in the Tech Center Wire Center on an Unbundled Loop is with a collocation placed in the Tech Center Wire Center, the pricing example for the Unbundled Loop is for an Unbundled Loop feed from a collocation space located in the Tech Center Wire Center.

The rates for the EEL were taken from the Qwest templated agreement and, because Allegiance currently doesn’t have the ability to order EELs in Colorado in their contract, a request of this kind would require an amendment to the Allegiance Interconnection Agreement (ICA) before ordering could commence on this product. Rates for the loop were taken from the Allegiance ICA . Collocation would also need to be established at the Tech Center wire center for this example.

Please contact us if you require additional information on these products, or have any questions.

Sincerely,

Ric Martin - CRPM (303) 896-9823 Robyn Libadia- EEL Product Manager (253) 445-0234 Bob Mohr- Unbundled Loop Product Manager (303) 896-2160

PC010302-1 Allegiance response 4-12-02.xls

--

CLEC Change Request Clarification Meeting

March 4, 2002, 9:00 (MT) Conference Call

PC010302-1, RSUs – the inability to provision UNEs

Attendees: Ric Martin, Qwest Cheri Hurless, Qwest Bernadette Derlein, Qwest Cindy Buckmaster, Qwest Terry Wicks, Allegiance

Introduction of Attendees Introduction of the participants on the Conference Call was made. Qwest explained that they wanted to review the current situation and get feedback from Allegiance.

Review Requested (Description of) Change Cindy advised that Qwest would be providing a drawing explaining how the Dry Creek CO was configured to the Tech Center RSU. Cindy explained that the Tech Center was connected to the Dry Creek CO by a transport medium (umbilical) and the end user would have a loop to the Tech Center. Cindy explained that there were two ways a CLEC could get a loop for the end user connected to the Tech Center. The first would be for the CLEC to be physically collocated in the Tech Center. The second would be to request an EEL from the dry creek office at whatever transmission level for the end user. Terry wanted to know how to tell if a customer was serviced out of an RSU. Cindy advised that the Raw Loop Data Tool cable field designation of EX would indicate this. Terry advised that it wasn’t practical for them to obtain a certificate for all their sales folks and to check each address separtely. Cindy explained that there is a Raw Loop Data Dump for each central office that would allow for various sorts on the data in the RLDT. A sort could be made on cables with EX and then by address. Terry asked if Qwest could provide information on how the transport for an EEL works and a narrative on the Raw Loop Data Dump. Terry asked about the RSUs that were tied to Dry Creek CO, Eagan, MN and Chandler AZ. Qwest will identify those RSUs tied to those Central Offices Qwest Identified the following Action Items to address: 1. Breakdown how an EEL works that uses a MUX, riding a higher capacity transport 2. Identify how collocation would occur in the different types of RSUs. 3. Identify the Raw Loop Data Tool Training available. Terry requested Qwest to address why the CLEC cannot obtain a loop for an end user that is identified out of the Central Office of record.

CLEC Change Request Clarification Meeting

Date: January 11, 2002, 9:00 (MT) Place: Conference Call 877-564-8688 Subject: PC010302-1, RSUs – the inability to provision UNEs

Attendees: Ric Martin, Qwest Neil Houston, Qwest Laurel Neher, Qwest Bernadette Derlein, Qwest Cindy Buckmaster Terry Wicks, Allegiance

Introduction of Attendees Introduction of the participants on the Conference Call were made and the purpose of the call discussed

Review Requested (Description of) Change Terry reviewed Allegiance’s CR. He explained that they had several orders they had to cancel due receiving reject notices on orders for UNEs. The problem indicated that COs customers given service by RSUs and routes to the CO where they are collocated and there is no place to cross connect. They are unable to port because they are in a RSU. He explained that they do not know they are in a RSU when processing an order. Laurel explained that the RSU would look like a CO. The switch depends on another switch for intelligence. She said that the LERG should have the CLLI. Qwest will look at the LERG to see if it has the information. Qwest thought that the NPNAXX would have the CO location. Neil advised that the Account Manager should advise which Colos have RSUs. The following COs have RSUs: Colorado – Dry Creek ? Center Park ? Denver SE ? Denver Tech Center – ISDN ? Aberdene ? Northglen Minnesota – Egan Arizona – Chandler Laurel explained that the RSU would need to the loop extended to the CO and this is done by ordering an EEL. Terry indicated that they look at customers that are serviced out of the CO where they are collocated at. Neil asked if Allegiance had any volume on the number of instances this is happening. Terry indicated that he did not. He advised that the reject notice was 10/24. Terry provided the TNs that were involved: RFG Management, Inc. 8400 E Cressent Parkway, suite 475, Greenwood Village, 80111, 303-771-0321. Banta, Hoyt, Everall 7979 Tufts Parkway, sutie 1050, Denver 80237, 303-220-8000 Terry indicated that he could go to the Raw Loop Data Tool and pull the address which provides the cable name fixed EX, but he could not identify on a CSR. Terry asked how Qwest determines a customer is in a RSU. Neil advised that it was a matter of Geography. The RSU is an electronic switch with a switch module connected by a TI to the CO. Neil advised that the customers referenced by Terry are in the Denver Tech Center. He explained that the loop is coming out of the RSC and doesn’t extend to the CO. Terry asked what is covered and what is available to view by CLEC. He does not want to have the cost of adding the EEL. He wants to be able to port from the CO where the records show the CO. His record is the CSR. Laurel indicated that the LERG should be used to determine the CO. Terry advised that another ILEC, GTE, put a card in their switch.

Identify/Confirm CLEC’s Expectation Allegiance wants to be able to port a UNE serviced out of an RSU from the CO where the records show the RSU’s CO is serviced and do not want to pay an additional cost.

Establish Action Plan (Resolution Time Frame) Qwest will identify what is contained in the LERG. The CR will have the collective CLEC clarification and SME input at the February CMP meeting.

CenturyLink Response

Terry Wicks Allegiance Telecom Inc

SUBJECT: Qwest Change Request Supplemental Response - CR PC010302-1 Remote Swiching Unit- Inability to provision UNEs

This letter is in response to the additional clarification requirements provided at the April 17, 2002 CMP Monthly Meeting on your Change Request PC010302-1 and supplements Qwest’s response dated March 12, 2002. The additional clarification requirements requested that Qwest:

1) Consider the reduction of the Non-Recurring Charge (NRC) for the EEL to allow a CLEC to order the EEL at the Loop NRC price. 2) Consider the elimination of transport rates where the transport would otherwise be billed in the EEL product. 3) Consider the identification of RSUs upon application of the CLECs for a collocation so as to ensure the CLECs make sound decisions about where to spend their collocation monies.

In response to items 1 and 2 above, Qwest’s research indicates that Qwest is in alignment with other ILECs on the handling of RSUs. As described in Qwest’s March 12, 2002 response, Qwest deploys RSUs in a number of situations. Primary among these situations is the deployment of augment switches to accommodate growth in a given geographic area. Installation efforts for EELs are more time and labor intensive than those for UBL, thus the higher NRC. In regard to transport, at times, the new RSU is either programmed to have the same NXX as the host, or has a unique NXX. Where the NXX is the same as the host, mileage is rated at $0. If the NXX is unique, mileage is calculated and the appropriate band rate applies. Reduction of the non-recurring charge or the elimination of the transport rate would tend to undermine both the embedded EEL and Collocation base. Based on our alignment with other ILECs, and the additional cost of the EEL product, Qwest is unable to reduce the NRC or eliminate the Transport charge from EELs provisioned under this arrangement.

In response to item 3, CLECs have access to several resources that indicate the structure of the Qwest network. Among these resources, the Raw Loop Data Tool indicates remotes via the ‘EX’ cable naming convention and the ICONN Database is being modified to identify remotes assigned to a given Central Office. As Qwest is not in a position to counsel CLECs on the construction of their network, Qwest would encourage CLECs to perform their own analysis and research.

Sincerely,

Cindy Buckmaster Product Manager Unbundled Loop Qwest Communications

CC: Bill Campbell – Product Director Qwest Communications Richard Martin – CMP Project Manager Qwest Communications

-

March 12, 2002

Terry Wicks Allegiance Telecom Inc

SUBJECT: Qwest Change Request Response - CR PC010302-1 Remote Swiching Unit- Inability to provision UNEs

This letter is in response to your Change Request PC010302-1 requesting that Qwest develop a process to allow the switching of end users service via an RSU to CLEC facilities.

General Information

The structure of the Qwest network occasionally results in the placement of Remote Switching Units (RSUs). These RSUs are a “spin off” of a host wire center and are created where geographic distance and/or population density requires. For the purposes of the Unbundled Loop, an RSU becomes the serving wire center for the end users it touches. As RSUs are deployed, end users served by the RSUs are terminated at the RSU. The structure between the host and the remote units becomes transport, therefore, there is no contiguous loop between the host and the end-users served by the RSU. End users of the remote are not individually identified at the host.

The underlying requirement of an Unbundled Loop is a Collocation in the serving wire center. The serving wire center for end users in the remote is the remote Central Office. Unbundled Loop can be ordered out of the remote only if the CLEC is collocated in the remote.

How to tell if an end user is in a RSU

The Raw Loop Data Tool (RLD) provides the CLEC with the information during pre-order to determine that the end user customer is served from an RSU. In the Raw Loop Data Tool the end user’s cable pair will indicate an “EX” prefix when the facility originates from an RSU (i.e., F1 ca EXA7).

There are two versions of the RLD tool. Using the IMA version a CLEC can view information specific to an end user address. With a digital certificate the CLEC can use the wire center version of the Raw Loop Data Tool. Data from this version of the RLD tool can be downloaded into an Excel spreadsheet or a database provided by the CLEC. Using the “File, Save As” commands from the browser software the CLEC can save the information to the location and in the format they prefer. Approximately 50 – 150 MB of disk space is needed per wire center. The process may be time intensive, as each wire center is checked separately.

See Loop Qualification and Raw Loop Data- CLEC Job Aid on URL http://www.qwest.com/wholesale/training/coursecatalog.html

How to serve customers in an RSU

The first option available to CLECs, to serve end users in a Remote Serving Unit (RSU), is to Collocate in the RSU.

Central Office Collocation:

For Central Office Collocation, each Central Office will be evaluated to determine if your Collocation requirements can be met (e.g., space, power, and heat dissipation).

Three types of Central Office Collocation are available:

Physical Caged Collocation – Allows the CLEC to physically collocate the CLECs own equipment in a Qwest Central Office in a space that is completely enclosed via chain link fencing. The CLEC installs, maintains and repairs their collocated equipment.

Physical Cageless Collocation - Allows the CLEC to physically collocate the CLECs own equipment in a Qwest Central Office in a space shared by Qwest and other CLECs that opt for Cageless Collocation. The CLEC installs, maintains and repairs their collocated equipment.

Virtual Collocation - Allows the placement of the CLECs equipment in a Qwest Central office, however, Qwest will install, maintain and repair the CLECs collocated equipment. In a Virtual Collocation arrangement, the CLEC does not have physical access to the virtually collocated equipment in the Qwest Central Office.

More information can be found in the Collocation Product Catalog (PCAT) at: http://www.qwest.com/wholesale/pcat/collocation.html

Enhanced Extended Loop (EEL):

The second option available to CLECs to serve end users in an RSU, is to request an Enhanced Extended Loop (EEL).

As the facility between the host Central Office and the remote Central Office is transport, the requested EEL would originate in the host office, extend through the remote Central Office and terminate at the end users premises. EEL can be ordered in two configurations; point-to-point (one transmission level from point of origination to point of termination) or Multiplexed EEL (a higher transmission level between the two central offices and a lower transmission level to the end user).

The "Multiplexed EEL" most closely resembles the network Allegiance has described. The CLEC can order a Multiplexed EEL with transport from their Collocation to another Qwest wire center. The Multiplexed EEL must be turned up before ordering EEL links (loops) to be connected to the Multiplexer. The EEL link orders must provide CFA (CKTID and slot number from the Multiplexed EEL). Each EEL, whether link or multiplexed, is ordered via an LSR. Standard intervals apply to each LSR EEL request. Intervals may be found under EEL/LMC in the Interconnection Service Interval Guide (SIG), also located on the Qwest wholesale website: http://www.qwest.com/wholesale/guides/sig/index.html

An abbreviated copy of that SIG has been attached to this document for ease of discussion (see Attached).

More information can be found in the EEL Product Catalog (PCAT) at: http://www.qwest.com/wholesale/pcat/eel.html

Billing elements are further described in the EEL PCAT and each billing element is labeled on the PCAT diagram. Billing elements for this situation are defined below.

Monthly recurring charges for a DS1 or DS3 multiplexed EEL, originating from a collocation, include: ITP, for the connection to the collocation, transport between the two Qwest wire centers, and multiplexing. Multiplexed EEL nonrecurring charges include transport and are applied to the multiplexer.

Monthly recurring charges for the DS1 or DS0 EEL links would be for the link only. EEL link nonrecurring charges include transport and are applied to the link.

Channel Performance charges may also apply (for DSO only).

A CLEC requiring EEL will need both EEL language and all applicable rate elements in their Interconnection Agreement in order to prevent rejection of the LSR. A CLEC with incomplete or no EEL information will need an amendment before EEL can be ordered. All rates and charges associated with EEL can be found in the CLEC Interconnection Agreement or the SGAT, Exhibit A.

Summary

As described above, Qwest will provide CLEC access to all end users, including those served by an RSU. As Qwest’s network complexities are vast, requests may require individual case basis (ICB) review. Qwest continues to modify its process to ensure CLEC access on a timely basis. Status will be provided in accordance with Change Management Process notification methods as updates to the process warrant.

Sincerely,

Bernadette Derelin Product Manager Unbundled Loop Qwest Communications

CC: Bill Campbell – Product Director Qwest Communications Cindy Buckmaster- Product Group Manager Unbundled Loop Qwest Communications Debra S Smith- Product Manager Unbundled Loop Qwest Communications Neil Houston – Network Qwest Communications Richard Martin – CMP Project Manager Qwest Communications

Open Product/Process CR PC071502-1 Detail

Description Of Change

This is resulting in Allegiance spending extra time, effort and money to isolate the NDT issue to the Qwest side. What would resolve this is if the Pair Information was also on the PTA notification next to the telephone number. With this information showing what pairs Qwest is testing to, we can identify the error quicker.

Expected Deliverable:

Receiving the PTA email notifications of NDT with the CFA information provided in addition to PON, TNs and DD

Status History

Project Meetings

11/20/02 November CMP Meeting Qwest (Thomte) indicated that she thought some problems had been identified recently through a comment from Lori Mendoza. Linda Hendricks confirmed that was true. Allegiance (Mendoza) indicated that they were getting CFA on the PTA about 50 percent of the time. Other CLECs indicated they were seeing problems as well. This CR will remain in CLEC Test.

10/16/02 October CMP Meeting Qwest initiated a Level 1 notification (PROS.10.14.02.F.00598.CFAEmailNotice) on October 14 advising the CLEC community that CFA information would be provided on PTA E-mail notifications. This CR moved to “CLEC Test”

09/18/02 September CMP Meeting This CR should be discussed in conjunction with PC050302-1. Qwest provided an updated response indicating this Change Request has been accepted, although it is dependent on the implementation of PC050302-1. Participants agreed that PC071502-1 CR can implement with a Level 1 notice after comments cycle is completed for PC050302-1. This CR will change to "Development"status with agreement to update to "CLEC Test" once Level 1 notice is sent.

08/21/02 - August CMP Meeting Minutes

This CR is dependent on CR PC050302-1. This CR status changed to "Evaluation"

Date: July 22, 200 Place: 1005 17th St Room 1770-C Call-In No.: 877 550-8686 CR No.: CLEC Change Request PC071502-1 Clarification Meeting

Attendees Name/Company: Terry Wicks Allegiance Russ Urevig Qwest Linda Hedricks Qwet Steve Hilleary Qwest Phyllis Sunnins Qwest Kit Thomte Qwest

Meeting Agenda: Action 1.0 Introduction of Attendees See list above 2.0 Review Requested (Description of) Change Terry Wicks reviewed the CR with the SMEs from Qwest. 2.1During the trial that was held in May and June Allegiance investigated situations that resulted in NDT. *One scenario was due to the Service Order being written with information that was different than what appeared on the LSR. *Another scenario was due to the Central Office being wired incorrectly. 2.2Terry indicated that if Allegiance knows up front what CFA Qwest is testing to it allows them to resolve the issue faster. Allegiance can review based on what they passed on the LSR and what Qwest FOCd back. 2.3

3.0 Confirm Areas & Products impacted 3.1 UNE, Unbudled Loop 4.0 Confirm Right Personnel Involved 4. The team agreed that Linda Hendricks would be the respondent Steve will participate, and Phyllis and Russ would have no further action.

5.0 Identify/Confirm CLEC’s Expectation 5.1 Receive notification regarding CFA used in no dial tone situations

6.0 Identify any Dependent Systems Change Requests 6.1

7.0 Establish Action Plan (Resolution Time Frame) 7.1 No systems are impacted the time frame would be dependent on the participation of the CLEC in the meeting and the timing of updating the documentation.

CenturyLink Response

Terry Wicks Allegiance

SUBJECT: Qwest’s Change Request Response - CR #PC071502-1 Include CFA Information on PTA Email Notifications of NDT.

This is a preliminary response regarding Allegiance CR PC071502-1 (Include CFA Information on PTA E-Mail Notifications of NDT). As discussed in the August Product & Process Monthly CMP Meeting, this CR is dependent on the outcome of PC050302-1 (Email Notification of No Dial Tone at 48 Hours).

The implementation of Change Request PC050302-1 is being pursued as a CMP Level 3 change as agreed to in the July Product & Process Monthly CMP Meeting. Based upon the issuance of notice PROD.09.05.02.F.00818.AnalogLoop24Wire, Change Request PC050302-1 is currently in a comment cycle.

Upon the implementation of Change Request PC050302-1 Qwest anticipates being able to make changes as described in PC071502-1. Specifically, Qwest expects to be able to include CFA information in addition to PON, TNs and DD in PTA e-mail notifications.

Assuming the successful implementation of e-mail notifications of No Dial Tone (NDT) per Change Request PC050302-1, Qwest would propose to notify the CLEC community of the changes specified in PC071502-1 as a Level 1 change (i.e. “additional information that does not change the product or process”). Qwest will seek concurrence with this approach at the September Product & Process Monthly CMP Meeting.

Sincerely,

Linda Hendricks Lead Project Analyst Qwest

Open Product/Process CR PC081902-2 Detail

Description Of Change

*********************************************************************************************

Announcement Date: July 19, 2001

Effective Date: July 29, 2001

Document Number: PROS.07.19.01.F.00012

Notification Category: Process Update

Target Audience: CLEC

Subject: Dial Tone Test 48 Hours Before Due Date

Effective July 29, 2001, a process enhancement will be added to both the Coordinated and Basic Installation Option Processes. Qwest will verify the CLEC’s Dial Tone at the CLEC’s CFA 48 hours prior to the Due Date. This will assist CLECs in identifying dial tone concerns prior to the due date.

Central Office Technicians (COT’s) will check for CLEC Dial Tone 48 hours prior to the Due Date. The Dial Tone check will be for the Unbundled Loop Analog (Voice Grade) Product.

The COT will check for Dial Tone at the CLEC CFA. The COT will document the results from the Dial Tone test and the results will be forwarded to the Implementer/Coordinator (C/I).

If the COT does not detect Dial Tone 48 hours prior to the Due Date, then the (C/I) will contact the CLEC with the information. The CLEC should investigate and supply the dial tone by the Due Date or issue a supplement to the LSR to change the due date.

If the CLEC has requested a Coordinated Installation, the COT will check for Dial Tone one hour prior to the Coordinated Installation time. If dial tone is not detected at that time, then the COT will report this to the C/I who will in turn inform the CLEC.

This Process will be put in place to ensure that the CLEC will receive their circuit on the due date.

*********************************************************************************************

Allegiance believes that Qwest is not complying with the process as stated above. The testing for dial tone is actually being conducted on DVA date (48 hours after Application Date not 48 hours prior to Due Date). Also it is not clear as to when Qwest is notifying the CLEC of no dial tone conditions. This process implies that once the COT forwards the results to the QCCC tester at 48 hours prior to due date, then the tester will immediately notify the CLEC of No Dial Tone conditions. In actual practice, Qwest is not consistently notifying the CLEC at 48 hours prior to cut date. There are inconsistencies between the process and Qwest's actual application of the process. Qwest needs to comply with its published process. This process is not published in the PCAT. The only reference to this process that Allegiance could find was the mailout sent to CLECs on July 19, 2001.

Expected Deliverable

Qwest will comply with its published process. Qwest will update the PCAT to include this process.

Status History

Project Meetings

- 10/16/02 October CMP Meeting Linda Hendricks with Qwest reviewed the draft response to this CR dated 10/3/02. Language was updated in the 2-Wire 4-Wire PCAT Version 10 which was published on 10/11/02. There were no questions from the CMP participants and this CR will be updated to CLEC test.

- 09/18/02 September CMP Meeting Minutes Allegiance reviewed the CR submitted and explained that they would like to have the dial tone testing and notification sync up in the PCAT documentation because the process document, PROS.07.19.01.F.00012, is not clear. Allegiance and Eschelon would like the testing process and the notification process of a no dial tone condition on 5-day interval and on longer than standard interval orders clarified. If the CLECs understand when the dial tone testing is done, then, they can adjust the date their translations are complete. Qwest explained that the CLEC is notified 24 - 36 hours before the due date of a no dial tone condition. The dial tone test is performed on DVA, which on 5-day interval orders is 48 hours after application date. Qwest will clarify the process, for 5-day and longer than standard interval orders, in the PCAT. Allegiance said that clarification in the PCAT would satisfy this CR.

- CLEC Change Request Clarification Meeting 3:00 p.m. (Mountain Time) / Monday 26th August 2002

1-877-554-8688 1930099 # PC081902-2 The 48 Hour Dial Tone Testing Requirements

Attendees Terry Wicks, Allegiance Deb Smith, Qwest Linda Hendricks, Qwest Bob Mohr, Qwest Cindy Macy, Qwest Neil Houston, Qwest Linda Sanchez-Steinke, Qwest

Introduction of the participants on the Conference Call was made and the purpose of the call discussed.

Review Requested (Description of) Change Terry indicated that Qwest is not following the process in document number PROS.07.19.01.F.00012. The process is interpreted that Qwest does the dial tone test and then calls the CLEC right away. The following is extracted from the CR submitted by Allegiance: Allegiance believes that Qwest is not complying with the process as stated above. The testing for dial tone is actually being conducted on DVA date (48 hours after Application Date not 48 hours prior to Due Date). Also it is not clear as to when Qwest is notifying the CLEC of no dial tone conditions. This process implies that once the COT forwards the results to the QCCC tester at 48 hours prior to due date, then the tester will immediately notify the CLEC of No Dial Tone conditions. In actual practice, Qwest is not consistently notifying the CLEC at 48 hours prior to cut date. There are inconsistencies between the process and Qwest's actual application of the process. Qwest needs to comply with its published process. This process is not published in the PCAT. The only reference to this process that Allegiance could find was the mailout sent to CLECs on July 19, 2001.

Confirm Areas & Products Impacted Unbundled Loop 2 wire 4 wire Analog Voice Grade, Coordinated and Basic Option

Confirm Right Personnel Involved Qwest confirmed the correct personnel were on the call. Identify/Confirm CLEC’s Expectation

Allegiance requests the following deliverables on this CR: - Update the PCAT with the Qwest process, and the agreed upon number of hours before due date the dial tone check is done, and, the agreed upon number of hours before the due date that the CLEC is notified of a no dial tone condition. - Provide notification of the process above - Improve on the CLEC notification process when there is a no dial tone condition. Determine the minimum number of hours before due date that the CLEC’s would like to be notified of a no dial tone condition.

Identify any Dependent Systems Change Requests PC081902-1, PC050302-1

Establish Action Plan (Resolution Time Frame) Allegiance will clarify and review this CR at the 9/18/02 CMP Meeting. Qwest will present the draft response at the 10/18/02 CMP Meeting.

CenturyLink Response

Lori Mendoza LEC Account Manager Allegiance Telecom, Inc.

SUBJECT: Qwest’s Change Request Response - CR #PC081902-2 48 Hour No Dial Tone Notification

This in response to Allegiance Telecom’s Change Request (CR) PC081902-2. This CR requests that Qwest clarify its 48 Hour No Dial Tone notification process and to document the process in the PCAT.

Qwest accepts this CR and the following language has been added to the 2-Wire or 4-Wire Analog (Voice Grade) Loop V10 PCAT.

Qwest verifies for dial tone at your CFA 48 hours after Qwest’s APP (application) date. If Qwest finds No Dial Tone (NDT), Qwest will retest 48 hours prior to due date. If dial tone is still not present, Qwest will email the NDT results to you through Qwest’s Provider Test Access (PTA) email system. You will receive the NDT PTA email notification approximately 24 to 36 hours prior to the due date. Qwest will email only when there is No Dial Tone. You will need to supply the dial tone by the due date or supplement the LSR, changing the due date.

This language is in document review and will be published to the Wholesale PCAT web site on October 11, 2002.

Sincerely,

Neil Houston Staff Advocate Policy & Law

Linda Hendricks Lead Project Analyst

cc: Mary Retka, Director, Technical Regulatory Interconnection Planning

Open Product/Process CR PC091201-1 Detail

Description Of Change

Also what is the process to negate the charges for these cuts and how is this tracked to insure the CLEC is not billed?

Status History

Project Meetings

Introduction of Attendees Terry Wicks, terry.wicks@algx.com, Allegiance Gary Stacy, gstacy@qwest.com, Qwest W. Rob Tomlinson, wtomlin@qwest.com, Qwest Linda Hendricks, lkhendr@qwest.com, Qwest Russ Urevig, rurevig@qwest.com, Qwest Joan Wells, jmwell2@qwest.com, Qwest Deni Toye, dtoye@qwest.com, Qwest Kate Spry, kspry@qwest.com, Qwest Ric Martin, rhmart2@qwest.com, Qwest

Terry, Gary, Rob, Linda, Russ, Joan, Deni, Kate, and Ric Review Requested (Description of) Change Clarify and document process for when orders are held on cut date, when Qwest has no facilities. Confirm Areas & Products Impacted Areas: Ordering and Day of Cut Products: UNE Confirm Right Personnel Involved Linda is the ‘owner’ of this CR and will be the point of contact for future problems of this nature until the root cause is established and draft response issued. Russ will forward necessary SCAT documentation to Kate. After the clarification meeting, it was determined that Gary, Rob, Joan, and Deni will not need to be involved in this CR. Kate will coordinate all necessary clarification meetings, complete meeting minutes, and review, forward, and store necessary documentation to database. Identify/Confirm CLEC’s Expectation Per Allegiance, “Allegiance wants clarification about the process when the problem is on Qwest’s side – Qwest should not have to SUP orders for no facilities on cut date. Allegiance provided an example of this happening (PON 824041-LP); Qwest should investigate this example and provide a documented process and reason why this happens on cut date. Also, what is the process to negate the charges for these cuts and how is this tracked to insure the CLEC is not billed?” Per Linda, there are no non-reoccurring charges. Identify any Dependent Systems Change Requests No related system CR’s were identified Establish Action Plan (Resolution Time Frame) Linda will clarify this process via a written formal response draft. She will forward this documentation to Kate by 9/27/01. Russ will forward the necessary SCAT documentation to Kate by 9/26/01. Kate will review and forward this information to Michael Belt and Matt Rossi to store in the CR database by 9/28/01 for CLEC review. The web location will be noted in Matt Rossi’s email regarding the response document on 9/28/01. This information can then be reviewed and discussed by the CLEC Community at the October CMP Meeting. Terry can view this information on the CR database and this CR can then be reviewed and discussed by the CLEC Community at the October CMP Meeting. Corrections/updates can then be made at that time.

CenturyLink Response

Terry Wicks LEC Manager, Allegiance Telcom Inc.

CC: Scott Simanson Fred Aesquivel

Re: DRAFT RESPONSE for PCCR 091201-1 For Review By CLEC Community and Discussion at October CMP Meeting" Topic: Provide the standard, documented process for when orders are held on cut date, when Qwest has no facilities Dated: 09/12/01

Dear Terry:

This letter is in response to the following CLEC Change Request Form PCCR 091201-1, dated 09-12-2001. The Change Request pertains to the Clarification and documented process for when orders are held on cut date, when Qwest has no facilities.

Qwest has a Pre Survey procedure in place to identify facility issues before due date. When it is discovered that facilities are not available or good an internal Qwest process looks for other facilities or place the order in a held status if no facilities can be located. The CLEC is then notified of the held status. The Cheyenne Held Order group notifies the CLEC after the order is placed in held. If the facility problem is found on test and turn up the CLEC is notified verbally at that time.

The orders that Allegiance inquired about on PON 824041-LP were held for facility problems on the due date, 8-29-01. The problem was discovered while trying to turn up the orders. The orders were all on Integrated Pair Gain and the process for handling Integrated Pair Gain orders was followed. A problem was discovered between the D4 channel and the SLC equipment in the Central Office. Qwest did not know of this problem until they tried to turn up the loops. The orders are being worked on to discover how to fix the problem and get the service provisioned. According to the WFA/C OSSLOG the CLEC has been advised of the progress.

Waiving the Non Recurring Charge does not apply to these orders because Qwest did meet the appointment time. The negating of Non Recurring Charge applies when Qwest does not meet the appointment time as specified on the CLEC’s LSR. MC The Missed Commitment should be applied only on Coordinated Orders (new and reuse) when Qwest misses the CLEC requested appointment time by 30 minutes or more. This MC=Y or MC causes a billing error to make the billing “fall-out” so the installation charges are dropped. This is placed on the OSSOI Cmnt/Rmk line in WFA/C. Systems captures and passes on to the billing CRIS system. When the billing error falls out, the SDC (service delivery coordinator) negates the nonrecurring charge on the customer's bill. This is how they receive their negated charges. The CLEC approved the start of the cut at 1007 on 8-29-01 by Scott at Allegiance.

Sincerely

Linda K. Hendricks Lead Project Analyst

Open Product/Process CR 5548229 Detail

Description Of Change

Status History

Project Meetings

Allegiance (Wicks) agreed this CR could be moved to “Completed” status. Allegiance did indicate they would like to see a higher level of compliance in this area. Currently they are still not receiving updated FOC’s 30% of the time.

-

"'Russ Urveig'" cc: "'Kit Thomte'"

Subject: Allegiance - Same Day CFA Changes - No Updated FOCs Week of 7/15 - 7/19

Here is the last spreadsheet that I will send to you for updates. Beginning 7/22 we are using the new process to release busy CFAs should the situation arise.

There was only one PON that we did not get an updated FOC on last week. Please confirm the CFA change was corrected on you records for PON 1388133-LP and return the updated spreadsheet to me. Thanks.

<>

Terry Wicks LEC Account Manager allegiancetelecom, inc 469-259-4438 terry.wicks@algx.com

07/17/02 - July CMP Meeting Minutes: Qwest (Buck) provided the following status. Qwest had provided information back to Allegiance on the spreadsheet they have been tracking from. Allegiance agreed that they would begin using the escalation process on July 22. Qwest indicated that in the interim the escalation information has been provided to the CLECs to allow everyone to use the process. Worldcom inquired how someone that did not attend CMP could get the information. Qwest responded that the information was updated in the Qwest Raw Loop Data Qualification Tool Job Aid. This CR will remain in "CLEC Test" until the next CMP meeting to determine if the process is working properly and can be closed.

"Cheri Hurless" , "Wicks, Terry" cc: kthomte@qwest.com

Subject: Spreadsheets

Here is the completed spreadsheet for the CFA changes and no FOC sent, if you have any question please get with Cheri. There was only one request for CFA change where as the records were incorrect, I had a service order issue to correct the problem and it was due dated today. Just to clarify the spread sheet, in the column for NO FOC if the correct CFA was applied in TIRKS and the service order, I place an OK next you your N indicator. In the Comment section I just stated CFA verified. (See attached file: Same Day CFA Spreadsheet No FOC Master.xls)

I believe we have made great improvements on the FOC during the last several week and in all but 1 case the CFA had been correctly changed. I feel that this spread sheet should be discontinued and any concerns for CFA changes should move to the BUSY CFA activity, but only after the CFA query function had been performed on both the old CFA to make sure it is vacant and against the new CFA tom make sure it is busy. Any time we take activities out of the normal process flow and I an referring to requesting a CFA change without documentation there are extra steps we both must take to work together. Thanks for all your feed back on this matter Terry, and I look forward to closing this CR. Russ,

Here are my latest examples of not receiving updated FOCs on same day CFA changes.

5/20/02 thru 5/24/02

1268042-LP Received Updated FOC 1253525-LP Did Not receive updated FOC 1275739-LP Did Not receive updated FOC 1273724-LP Received Updated FOC 1272870-LP Received Updated FOC 1265872-LP Received Updated FOC 1277072-LP Received Updated FOC 1270017-LP Received Updated FOC 1276114-LP Received Updated FOC 1153382-LP Received Updated FOC

5/28/02 thru 5/31/02

1296008-LP 303-706-9024 Did Not receive updated FOC

1284062-L 480-237-0350 Did Not receive updated FOC 1308512-L1 480-966-8198 Did Not receive updated FOC 1295225-LP 303-781-8307 Received Updated FOC Received Updated FOC

1287395-L 303-771-0816 Received Updated FOC 1301207-LP Did Not receive updated FOC

1301991-LP Did Not receive updated FOC 303-762-9176 1278540-LP Received Updated FOC

1303185-L Received Updated FOC 1307043-L Did Not receive updated FOC 1303880-LP Received Updated FOC

1309037-LP Received Updated FOC 1309503-LP Did Not receive updated FOC 1292144-L Did Not receive updated FOC 1301212-LP Received Updated FOC

1285714-LP Received Updated FOC

Terry Wicks LEC Account Manager allegiancetelecom, inc 469-259-4438

Subject: CFA'S FOR 5/13/02 THRU 5/17/02

FOC 1242682-LP TN 720-932-8789 NEW 1263 OLD 1299

FOC 1257259-LP TN 303-755-3199 NEW 829 OLD 814

FOC 1284374-LP TN 206-323-1751 NEW 1279 OLD 1259 AND 1341 SHOWS WORKING IMA

NO FOC 1211795-LP2 TN 752-888-7554 NEW 247 OLD 276

FOC 1261532-LP TN 623-931-8086 NEW 808 OLD 768

FOC 1265023-L TN 303-991-0119 NEW 696 OLD 1183

FOC 1280325-MVL TN 763-576-6636-1 NEW 152 OLD 161

Thank you and have a good day,

Tasha Nichols/Supervisor Qwest/Verizon West 469-259-4823 fax 469-259-9051 tasha.nichols@algx.com

CenturyLink Response

Terry Wicks LEC Account Manager Allegiance Telecom

SUBJECT: Qwest’s Change Request Response - CR 5548229 Same Day Pair Change

This letter is in response to your recent request regarding the Escalation process associated with busy CFA. A subsequent request was made to include information to the CLECs regarding how they should initiate an escalation for busy CFA.

Below is the information that is necessary to initiate an Escalation for busy CFA.

Busy Connecting Facility Assignment (CFA) is defined as; When validating the CFA the slot shows that it is currently in use by a circuit in the Trunk Integrated Record Keeping System (TIRKS). The busy CFA can be the result of several different reasons: normal activity, pending service order activity, pending Inventory Availability Date (IAD) issues, and canceled service orders that have not cleared in TIRKS. Should you receive an indicator that the CFA is currently in use, however you records indicate the CFA is NOT in use, an Escalation ticket may be opened.

Information that is required for an Escalation ticket will be for BUSY CFA problems.

1. TERM Z TYPE LONG CLLI (ex.ALBONMNEHG1)

2. TERM A TYPE SHORT TYPE CLLI (e.g., ALBQNMNE)

3. CABLE TYPE (e.g., alt01)

4. UNIT NUMBER (e.g., 086)

5. Was there a disconnect request submitted to free CFA location. (EX. Yes, a disconnect request was submitted and an FOC was received. The PON number for the disconnect was AAA121211-MA)

6. Was the Slot changed during installation? If so what was the old slot and what should the current slot be? (EX. Yes, we changed the CFA during test and turn-up the previous CFA was ALT01 slot 89 TCANAZMAHG1 and slot changed to slot 91. The PON number associated to this change was AAA121211-MA)

7. Was there any migration activity on this CFA? (EX. Yes, we should that a migration to another Provider on 06/17/2002)

8. Want type of request were you attempting when you encounter the busy CFA problem? (EX. We were attempting to request a new loop and utilize this CFA, or we were attempting a change activity against circuit 99.LXFU.000111.nw.)

9. Were there any change activity against the circuit, if so PON number for activities. (EX. Our records show a change activity should have taken place on 06/17/2002 from PON AAA121211-MA to free this CFA. Or our records indicate a disconnect request on 06/17/2002 on PON AAA121211-MA which should have freed the CFA.)

If you have any questions regarding this information please feel free to contact me.

Sincerely,

Russ Urevig Senior Process Analyst

01/07/02 Response to Allegiance e-mail dated 12/28/01 January 7, 2002

Terry Wicks LEC Account Manager Allegiance Telecom

CC: Catherine Garcia

This letter is in response to your e-mail dated Friday, December 28th, 2001 – Allegiance – Same Day CFA Change – No Updated FOC Received.

Response: Since we have received examples of FOC’s not being sent to the CLEC’s when a CFA has been changed, new focus on this process has been brought forward. The QCCC have put the following procedures in place to insure that the CFA process is followed.

- All testers have been re-trained on the CFA Change Process.

- Four compliance reviews, for each tester, are completed every month focusing on compliance to the CFA Change Process.

- Performance managing is being done to insure the CFA Change Process is being complied with. If a tester fails their compliance review, there is documented discussion around the issue.

- Weekly Leadership meeting are held to discuss issues for the center. The CFA Change Process has been brought forward during these meetings to insure that the process is understood and followed.

Sincerely,

Deni Toye Network Unbundled Loop Process

October 10, 2001 Terry Wicks, Allegiance

This letter is in response to your CLEC Change Request Form CR5548229 dated August 30, 2001, Request:

Allegiance has sent Qwest examples of orders when Allegiance had problems on same day CFA changes. Allegiance was not receiving FOC’s back specifying that a CFA had been changed. Allegiance would like to know that there is a process for a CFA change on test and turn up for the same day.

Qwest Response: There was a process put into place to allow the CLEC to have a CFA change before or on the due date. On August 9, 2001 a process was put in place to allow this activity to happen. Terry Wicks sent some examples to show that the process is not working. After investigation of these orders, it was determined that a process is in place and does work, however, there are isolated cases of non-compliance issues. The orders that Terry sent to us did have the CFA changed the day of the due date, however, non-compliance to the process did not produce a call to the SDC, therefore, a FOC was not sent to the CLEC. These examples have been forwarded to the centers for process compliance verification.

Sincerely,

Deni Toye Network Unbundled Loop Process

Open Product/Process CR PC062602-2 Detail

Description Of Change

While some of the rejects proved out that there were no reusable UNE DS0 circuits, the reject reasons did not clearly state the true circumstances. For example one reject stated “no working circuits found”. When further researched, it was found that there were indeed working circuits there but the only working circuits for the End User were DS1s.

Allegiance would also like to collaboratively work with Qwest and other CLECs to establish clear, definitive reject reasons for CLEC to CLEC reuse of facilities orders to insure that all resources available to the SDCs have been utilized to find working circuits. When Allegiance submits CLEC to CLEC reuse of facilities orders, we already have obtained a CSR from the CLEC so we know the numbers we are porting are indeed working on some kind of circuit. These reject reasons should be clear enough to insure the CLEC that there are indeed no working UNE DS0 circuits to reuse. As stated above some of the orders rejected did indeed have available working UNE DSO circuits that could be reused. Allegiance currently does not have confidence that the SDC’s reject reasons are valid and their training is adequate to locate reusable UNE DS0 circuits. In many instances we are having to drop new loops in order to take the customer when there are reusable loops available. Installing new loops is more expensive, more time consuming for the cut over, and there is the risk the orders will be held for lack of facilities. The ability to “reuse” facilities is less expensive, the cut over process is less time consuming, and the end user has less down time.

Expected Deliverable:

Clear, definitive reject reasons that the CLECs can rely on that all resources were utilized to “find” working UNE DS0 circuits for CLEC to CLEC reuse of facilities orders.

Status History

Project Meetings

Qwest requested that Allegiance research to determine if Allegiance personnel is receiving the comments that were agreed to. Attendees agreed that this could be closed off line if Allegince (Mendoza) agreed.

09/18/02 September CMP Meeting The improved comments associated with rejects on CLEC to CLEC Reuse of Facilities were implemented on August 23. The response indicated it was implemented on August 22. Qwest will update the status history to reflect the actual date. Allegiance (Wicks) indicated they were unaware that the process was underway, Terry will check with his people to find out. Eschelon (Johnson) indicated they had encountered a couple of problems with the process, Russ worked through these issues for them. This CR will remain in “CLEC Test” until the October meeting when it is anticipated that the CR will be updated to "Completed."

- 08/21/02 - August CMP Meeting Minutes Qwest (Urevig) reviewed the three scenarios and comments that are associated with the reject reasons. Allegiance (Wicks) inquired about the second scenarios comments. Are they intended to be two separate or one comment? Qwest indicated that they are two distinct comments. This CR was moved to "CLEC Test".

"Wicks, Terry" , Kathleen Thomte/Mass/USWEST/US@USWEST cc: Cheri Hurless/GROUPWARE/USWEST/US@USWEST

Subject: CR

I wanted to get back to you with the different type of comments we are looking at placing on the rejected CLEC to CLEC migrations request, during our last meeting we determined there were 4 different types of rejects which would require different comment.

1. Wrong type of circuit being requested does not match what was requested by CLEC. 2. Multiple circuits at customer location not all circuits being migrated. 3. No circuits found for migration 4. CLEC to CLEC reuse of facility show detail of which CLEC migration is from (This is probably going to be included in the first scenario).

These are the scenarios and the comments that will reject will contain, I combined the 2 and 3

1. When Qwest finds the circuit at the requested address is NOT the same type of circuit to which the migrate has been requested, the comment remark associated with this will read: Circuits at request address do not match the type of circuit indicated on the LSR for migration. The circuits found are (ex. LX-N or AD--, HCE-, etc)

2. Multiple circuits are found at the requested address, if the number of circuits at the address do NOT match the number of migrations indicated on the LSR. It is very important that the CLEC indicate who the OLSP (old local service provider) is when requesting migration because this will aid in determining whether multiple circuits are really an issue. Qwest will provide these comment remarks for the reject: Multiple circuits have been identified at request address, circuits are currently not those of the indicated OLSP or Multiple circuit have been identified for the OSLP but do not match the number of loops requested for migration.

3. Qwest has searched all available records to identify circuits at end user address, but was NOT able to identify circuit for migration. Qwest will review all data on LSR to obtain circuits to be migrated. Additional data that is recommended to aid in the migration request are: the TN that is being ported to the NLSP’s (new local service provider) switch and the name of the OLSP. If Qwest can NOT find the circuits, the following comment remarks will be provided on the reject: Qwest has search for circuits at the requested address, using the end user name, address, OLSP, and TN provided. Qwest can not find circuits please verify data on LSR for accuracy.

If these cover additional comments or consistent comments will help the CLEC determine the reason for the reject I will place these into the Job aid for Migration then cover this with the SDC's, coaches, SME's and SDC to make sure everyone has the same understanding.

If you have any comments or concerns maybe we can talk or discuss this at the next CMP meeting.

August 12, 2002

Terry Wicks Allegiance Russ Urevig Qwest Kit Thomte Qwest

Notes from follow up meeting: PC062602-2 Rejects on CLEC to CLEC Reuse of Facilities order for no Circuit Ids found. Qwest agreed to hold follow up meeting to collaborate with Allegiance regarding comments associated with reject reasons.

The team agreed that Russ would put together proposed comments for Terry to review. The group also agreed to talk through on the call what the 3-4 scenarios are that exist that could drive the comments.

1. Wrong type of circuit being requested does not match what was requested by CLEC. 2. Multiple circuits at customer location not all circuits being migrated. 3. No circuits found for migration 4. CLEC to CLEC reuse of facility show detail of which CLEC migration is from (This is probably going to be included in the first scenario).

The team agreed that Russ would put together scenarios and new comments for Terrys review.

07/17/02 - July CMP Meeting Minutes: Allegiance (Wicks) reviewed the CR and indicated that his representatives were not using the prescribed process. When analyzed he discovered that the reject reasons did not really make sense. Through discussions with Qwest it appeared that our SDC need access to a special database. Qwest and Allegiance will review the reject reasons to help clarify them. Qwest will provide an initial response prior to the August meeting. This CR will carry a “Clarification” status

Date: July 3, 2002 Place: 1005 17th St Room 1770-C Call-In No.: 877 550-8686 PC062602-2 CR No.:PC062602-2 CLEC Change Request Clarification Meeting

Attendees Name/Company: Terry Wicks Allegiance Russ Urevig Qwest Debbie Osborne Qwest Neil Houston Qwest Kit Thomte Qwest

Meeting Agenda: Action 1.0 Introduction of Attendees See list above

2.0 Review Requested (Description of) Change Terry Wicks reviewed the CR with the SME from Qwest. Process to find working circuits needs to be re designed and reviewed with personnel. Update reject reasons to be clearer specify scenarios that relate to the reject so the SDC can provide better information to the CLECs.

2.1 Terry believes that a collaborative process should be used to allow input from Allegiance and other CLECs in the development of the error messages. We agreed that we could discuss at the CMP meeting and determine the level of interest. 2.2 Terry presented an example that the SMEs reviewed to ensure a level of understanding for the problem. 2.3 Qwest inquired about what changed in May 2002 that seemed to impact thee errors. Allegiance clarified that was when they discovered that the process was not being used.

3.0Confirm Areas & Products impacted 3.1CLEC to CLEC migrations Qwest wanted to clarify that this was a specific issue associated with one product (UNE). And not a global issue. Allegiance indicated it was not global. Qwest inquired about what changed in May 2002 that seemed to impact thee errors. Allegiance clarified that was when they discovered that the process was not being used. 4.0Confirm Right Personnel Involved 4.1Russ Urevig will have the lead on this CR. Neil will stay involved as required.

5.0 Identify/Confirm CLEC’s Expectation 5.1Ensure that Qwest personnel understand the process and are trained. Improve the reject remarks to be more specific to scenarios thus providing the CLECs a better idea of the problem.

6.0Identify any Dependent Systems Change Requests 6.1 None apply

7.0 Establish Action Plan 7.1 No systems are impacted the time frame would be dependent on the participation of the CLEC in the meeting and the timing of updating the documentation. 7.2

CenturyLink Response

Terry Wicks, LEC Manger Allegiance Telecom, Inc

SUBJECT: Qwest’s Change Request Response - CR # PC062602-2 Rejects on CLEC to CLEC Reuse of Facilities orders for no circuit IDs found

This is in response to the request from Allegiance where as Allegiance would like to collaboratively work with Qwest to establish clear, definitive reject comment reasons for CLEC to CLEC reuse of facilities orders to insure that all resources available to the SDCs have been utilized to find working circuits.

After meeting with Terry Wicks several times to discuss the application of the comment remarks that are associated with the reject for CLEC to CLEC migration, we have clarified the comments and have modified the comments as set forth below to address the following scenarios.

1. When Qwest finds the circuit at the requested address is NOT the same type of circuit to which the migrate has been requested, the comment remark associated with this will read: Circuits at request address do not match the type of circuit indicated on the LSR for migration. The circuits found are (ex. LX-N or AD--, HCE-, etc)

2. Multiple circuits are found at the requested address, if the number of circuits at the address do NOT match the number of migrations indicated on the LSR. It is very important that the CLEC indicate who the OLSP (old local service provider) is when requesting migration because this will aid in determining whether multiple circuits are really an issue. Qwest will provide these comment remarks for the reject: Multiple circuits have been identified at request address, circuits are currently not those of the indicated OLSP or Multiple circuit have been identified for the OSLP but do not match the number of loops requested for migration.

3. Qwest has searched all available records to identify circuits at end user address, but was NOT able to identify circuit for migration. Qwest will review all data on LSR to obtain circuits to be migrated. Additional data that is recommended to aid in the migration request are: the TN that is being ported to the NLSP’s (new local service provider) switch and the name of the OLSP. If Qwest can NOT find the circuits, the following comment remarks will be provided on the reject: Qwest has search for circuits at the requested address, using the end user name, address, OLSP, and TN provided. Qwest can not find circuits please verify data on LSR for accuracy.

A review of the internal documentation for Qwest has been completed and several changes have been made to streamline the search for unbundled loop circuits. The completed changes and notification to the Wholesale Service Delivery centers will be complete by August 22. The change notifications will be distributed with an MCC, the details of the MCC are the TOPIC is Standardized Comments for CLEC to CLEC Migration Rejects, the SUBJECT is Unbundled Loop, the USER GROUPS AFFECTED are Wholesale. A joint review meeting with the Team Leads, Coaches and SMEs (subject matter experts) will also be held to review the changes and clarify the importance of this process. We have accepted the request to modify the comment remarks on the rejected migration, so that the comments are more standard for the problem encountered. If the Qwest deviates from the standard comments it will be only to provide additional information about that reject.

Sincerely,

Russell Urevig Sr Process Analyst Wholesale Service Delivery

Open Product/Process CR PC062602-1 Detail

Description Of Change

While there is a process in place to be able to submit CLEC to CLEC reuse of facilities orders without providing circuit ID information, 90% of the orders submitted by Allegiance since late May 2002 are being rejected for various erroneous or unclear reasons regarding the circuit ID information. (I will be addressing that issue in a separate change request.) Allegiance believes that having this additional capability, will greatly enhance our ability to get reuse orders successfully processed and in a more timely manner.

Expected Deliverable:

A process for CLECs to be able to request Circuit IDs up front for CLEC to CLEC reuse of facilities orders that is in parity with Retail’s capability to get such circuit IDs before placing a reuse order for UNE DS0 loops.

Status History

Project Meetings

09/18/02 September CMP Meeting Qwest reviewed its draft response and summarized the September 4th conference call with Allegiance, walking through Raw Loop Data Tool. When the end user location was a single tenant address the circuit ID was produced. When the end user location was a multi-tenant address, the circuit ID was produced when the suite number was included and when the suite number was in PREMIS database. Allegiance appreciated the assistance with RLD, and, said that providing the circuit ID will get migration orders through the first time with fewer rejects. This CR will stay in development status while determining the tool for CLEC’s to obtain circuit IDs is identified. Eschelon asked if Qwest is not able to come to a systems solution, would a single point of contact be implemented for CLEC’s. Qwest responded that such a solution may be entertained but it was more likely that a mechanized process would be identified.

-- 08/21/02 - August CMP Meeting Minutes: Qwest reviewed its draft response. Allegiance would like to walk through on the phone with Qwest and use Raw Loop Data Tool. Eschelon asked how to identify which CLEC owns the circuit. Qwest stated that the RLDT will provide the circuit ids and that retail and CLECs rely on Qwest Wholesale to identify the local provider. Allegiance indicated they would like to move this CR into development.

07/17/02 - July CMP Meeting Minutes: Allegiance presented their Change Request. Qwest stated that current tools will be reviewed for their capability to look at curcuit IDs in conjunction with end user addresses, including specific addresses that have suite numbers. CR status is clarification

Time/Date: 9:00 a.m. (MDT) / Monday, July 8, 2002 Place: Conference Call Conference: TEL: 877.521.8688 Call-In No: CODE: 7901848 CR No: PC062602-1" Circuit IDs on CLEC to CLEC Reuse of Facilities orders"

Attendees: Terry Wicks, Allegiance Russ Urevig, Qwest Neil Houston, Qwest Bob Mohr, Qwest Michael Keegan, Qwest

Introduction of Attendees Attendees introduced. Review Requested (Description of) Change Description: Allegiance wants the capability to get CLEC circuit ID information from Qwest on UNE DS0 loops prior to submitting a CLEC to CLEC reuse of facilities order. If Qwest Retail wants to reuse facilities when porting a customer from a CLEC back to Qwest, they have the capability to "look up" circuit ID information. Qwest Retail does not have to get this information directly from the CLEC, thus the ability to access circuit ID information speeds up their process of submitting orders to Wholesale and eliminates rejects for "bad or missing" circuit IDs. Giving the CLECs a process to obtain CLEC circuit ID detail up front for reuse orders, will allow the CLECs the same parity in submitting accurate orders in a timely manner. This capability will also allow more frequent use of the CLEC to CLEC reuse of facilities process. In many instances, some CLECs that are loosing a customer will not provide circuit ID information to the winning CLEC, thus inhibiting the process of reusing the facilities. When facilities are not reused and the CLEC submits new loop orders, the results may be held orders for lack of facilities. Also installing new loops is much more expensive.

While there is a process in place to be able to submit CLEC to CLEC reuse of facilities orders without providing circuit ID information, 90% of the orders submitted by Allegiance since late May 2002 are being rejected for various erroneous or unclear reasons regarding the circuit ID information. (I will be addressing that issue in a separate change request.) Allegiance believes that having this additional capability, will greatly enhance our ability to get reuse orders successfully processed and in a more timely manner.

Discussion: Allegiance stated they cannot force a CLEC to provide circuit ID information. Allegiance is dependent on Qwest to provide this information. Reuse of facilities benefits both the CLEC and Qwest. Qwest stated that the current tools will be reviewed for their capability to look at circuit IDs in conjunction with end user addresses. Confirm Areas & Products Impacted Areas Impacted: Ordering, Provisioning Products Impacted: Unbundled Loop, UNE Loop Confirm Right Personnel Qwest confirmed the correct personnel were on the call.

Identify/Confirm CLEC’s Expectation A process for CLECs to be able to request Circuit IDs up front for CLEC to CLEC reuse of facilities orders that is in parity with Retail’s capability to get such circuit IDs before placing a reuse order for UNE DS0 loops. Identify any Dependent Systems Change Requests None Establish Action Plan (Resolution Time Frame) Allegiance can present this Change Request to the CLEC community at the July Product/Process CMP meeting scheduled for July 17 Qwest will issue draft response to this Change Request by Aug 14 (one week prior to the Aug 21 CMP meeting). Qwest will discuss the draft response at the Aug 21 CMP meeting.

CenturyLink Response

Lori Mendoza LEC Account Manager Allegiance Telecom

SUBJECT:Qwest’s Change Request Revised Response - CR # PC062602-1 Circuit IDs on CLEC to CLEC Reuse of Facilities orders

At the September CMP meeting, Qwest agreed to continue to research the issues, to determine the most suitable path forward in determining circuit ID information to allow the CLECs the ability to get circuit ID information on DSO type loops for CLEC to CLEC migrations.

Qwest has reviewed the current process of obtaining loop circuit ID’s using the Raw Loop Data (RLD) Query for CLEC to CLEC migrations. We find the tool meets the needs of the change request to provide CLECs a process to obtain Loop Circuit ID details for reuse orders. To clarify, the RLD Query can be used as follows: - Enter a valid address, this must be suite or unit specific if address is multi-tenant. - If address is valid, RLD will provide information on all working TN’s or circuits. - If no matches are found for a specific address, RLD will return a message indicating no information found.

When no circuit information is found, proceed with submitting the LSR and Qwest will determine the circuit and migrate the end user as requested.

The current process provides parity with migrations between Wholesale CLEC to CLEC migrations and migrating end users back to Qwest Retail. The work performed, the results and the responses are handled in the same manner between Retail and the CLECs

LSRs for CLEC to CLEC migration do not require that the Circuit ID field be populated. - Qwest will accept the requests for migration without circuit information. - Qwest will research and determine the circuit or circuits at that address. - If the Loop Circuit ID cannot be determined, Qwest will provide a standard remark associated with the reject of a migration request as follows:

1. When Qwest finds the circuit at the requested address is NOT the same type of circuit to which the migrate has been requested, the comment remark associated with this will read: Circuits at requested address do not match the type of circuit indicated on the LSR for migration. The circuits found are (ex. LX-N or AD--, HCE-, etc).

2. Multiple circuits are found at the requested address: If the quantity of circuits at the address do not match the quantity of lines migrating, as indicated on the LSR, Qwest will use the OLSP information provided by the CLEC to try to determine which services will be migrated. It is very important that the CLEC indicate who the OLSP (old local service provider) is when requesting migration because this will aid in determining whether multiple circuits are really an issue. Qwest will provide these comment remarks for the reject: Multiple circuits have been identified at request address, circuits are currently not those of the indicated OLSP or Multiple circuits have been identified for the OSLP but do not match the number of loops requested for migration.

3. Qwest has searched all available records to identify circuits at the end user address, but was not able to identify circuit for migration: Qwest will review all data on the LSR to obtain circuits to be migrated. Additional data that is recommended to aid in the migration request are: the TN that is being ported to the NLSP’s (new local service provider) switch and the name of the OLSP. If Qwest can not find the circuits, the following comment remarks will be provided on the reject: Qwest has searched for circuits at the requested address, using the end user name, address, OLSP, and TN provided. Qwest can not find circuits, please verify data on LSR for accuracy.

- The CLEC should review the reject remarks, validate any issues in question, and re-submit the LSR once the information is found and the LSR is corrected. - Qwest provides a method to escalate questions on rejects or clarification on remarks for rejects.

Sincerely,

Russ Urevig Senior Process Analyst Wholesale Service Delivery

Open Product/Process CR PC050302-1 Detail

Description Of Change

Status History

Project Meetings

Qwest explained this process was implemented effective October 11, 2002. No issues have been identified with the process and Qwest requested to close this CR. Lori Mendoza - Allegiance advised they are using the process and it is working without any issues. Allegiance and the other CLECs in attendance agreed to close the CR.

10/18/02 October CMP Monthly Meeting Minutes Qwest explained this process was implemented effective October 11, 2002. As of October 16, four CLECs have signed up to receive E-Mail Notification of NDT via the PTA tool. Eschelon verified that if you do not sign up for email notification via the PTA tool then you will not get any NDT notification, as the only method of NDT notification is now the PTA tool. CLECs can continue to sign up at any time. Qwest agreed to leave the CR in CLEC Test since this process was just implemented, with potential closure in November.

09/18/02 September CMP Monthly Meeting Minutes

Qwest advised that the Level 3 notification had been issued and that the comment cycle was scheduled to end this Friday, September 20th. Qwest advised that Qwest Service Managers had sent out notifications to their CLECs advising them to provide their e-mail address. The CLECs expressed concern over the 48-our language as written and intervals that were longer than the standard intervals. Qwest confirmed that the 48-hour notification was from the due date and this would be clarified in the PCAT or in writing. CLECs expressed concern over participation in the trial. It was agreed that next time Qwest does a trial, Qwest could evaluate if additional CLECs need to be involved. CLECs requested that the final notification advise the CLECs of the impact of the e-mail notification change. Qwest advised that they would add language in the final notification that advises the CLECs that if they do not provide an e-mail address they would not receive the No Dial Tone notifications.

08/21/02 August CMP Monthly Meeting Minutes

Qwest provided a status update on issuance of the Level 3 notice. Qwest indicated that they were holding off until the current 2-wire 4-wire PCAT language gets published to the Web on August 26, 2002. Allegiance expressed concern that issuance was based on the no dial tone PCAT language since they have taken exception to the language. Qwest advised that this could be addressed during the 1:00 p.m. discussion on issuance of the PCAT language. Eschelon advised that they were disappointed that they will need to wait longer for issuance of the Level 3 notice. They stated that Qwest advised last month that it would be issued by this month’s meeting and now they have to wait longer. AT&T asked if they could only have one e-mail. Qwest advised that they could only have one and it must be different than the e-mail if they are receiving test results.

-

07/17/02 - July CMP Meeting Minutes: Qwest will continue with the trial that began May 6, 2002. It is available to all CLECs. Allegiance asked if all CLECs had to request the process in order for it to proceed. Qwest responded that the answer is yes, it is all or nothing. Allegiance stated that there should be a choice and that the Qwest response does not reference the “all or nothing” position. Qwest responded that the Level 3 process will support this effort and will allow other CLEC participation.. Qwest will issue the Level 3 initial notice prior to the August CMP meeting. CR status was changed to development.

Subject: Allegiance - NDT Trial E-mail Notification Final Spreadsheet 5/6 - 5/31/02 Date: Mon, 10 Jun 2002 11:36:25 -0500 From: "Wicks, Terry" To: "'Cheri Hurless'" , "'Deni Toye'" , "'Kathie Simpson'" , "'Linda Hendricks'" , "'Mary Pat Cheshire'" CC: "Reece, Mamie" , "Best, Doreen" , "Hill, Todd"

Here is the finalized spreadsheet with the data and comments captured for May. The trial is continuing through June and I will have a separate spreadsheet for June.

<>

Terry Wicks LEC Account Manager allegiancetelecom, inc 469-259-4438 terry.wicks@algx.com

--

CLEC Change Request Clarification Meeting

May 9, 2002, 3:30 p.m. (MT) Conference Call 877-564-8688 PC050302-1, E-Mail Notification of No Dial Tone at 48 Hours

Attendees: Ric Martin, Qwest Neil Houston, Qwest Mike Raleigh, Qwest Deni Toye, Qwest Terry Wicks, Allegiance

Introduction of Attendees Introductions of the participants on the Conference Call were made and the purpose of the call discussed

Review Requested (Description of) Change Terry reviewed Allegiance’s CR. He explained that the initial phone call would roll to voice mail and the issue is with the voice mail notifications falling through the crack. He would like to get an e-mail to have a record to hold Allegiance personnel accountable. Terry advised that there is currently a trial with Qwest and Allegiance on this process that started in February with the QCCC. Deni advised that the trial started May 6th and is to be concluded May 31st. Currently they are having the PTA System send the e-mail. Terry advised that the CR was submitted in addition to the trial to have this process implemented for all CLECs.

Confirm Areas & Products impacted It was confirmed that the area impacted was Provisioning for coordinated hot cuts and basic cuts. The product impacted is UBL, LX—Reuses.

Confirm Right Personnel Nvolved Qwest confirmed that Neil Houston would be the SME for response to this Change Request.

Identify/Confirm CLEC’s Expectation Allegiance would like this process implemented for all CLECs.

Identify any Dependent Systems Change Requests There are no related Systems CRs.

Establish Action Plan (Resolution Time Frame) The trial will complete May 31st. The CR will have the collective CLEC clarification and SME input at the June CMP meeting.

CenturyLink Response

Terry Wicks LEC Manager Allegiance Telecom, Inc.

SUBJECT: Qwest’s Change Request Response - CR # PC050302-1 E-mail notifications of NDT at 48 hours through PTA tool

This is in response to Allegiance’s Change Request (CR) PC050302-1. This CR requests that all notifications of No Dial Tone (NDT) at 48 hours prior to the cut date be provided to the CLEC via e-mail using Qwest’s Plant Test Access (PTA) tool. The current trial of PTA e-mail notifications with Allegiance began on May 6, 2002. The trial with Allegiance will continue during the implementation phase for this CR.

Qwest is able to provide all NDT notifications via e-mail using the PTA tool. PTA notifications require that CLECs provide Qwest with an e-mail address separate from the e-mail address provided for test results. CLECS should send their NDT PTA e-mail location to Deni Toye, dtoye@qwest.com. Qwest will add the CLECs NDT PTA e-mail address to the notification list upon receipt. To provide an efficient and uniform notification, Qwest will provide NDT notifications via the PTA tool to all CLECs.

Based upon Qwest’s understanding of the scope of this CR, Qwest views the implementation of this CR as a Level 3 Product & Process change. Timing of the implementation of this change will be dependent upon the quantity and nature of CLEC comments.

Qwest will seek concurrence for this approach at the July Monthly Product & Process CMP Meeting.

Sincerely,

Neil Houston Staff Advocate Policy & Law

cc: Mary Retka, Director, Technical Regulatory Interconnection Planning

Open Product/Process CR PC092701-2 Detail

Description Of Change

Status History

Project Meetings

CenturyLink Response

Terry Wicks LEC Manager Allegiance Telecom, Inc.

This letter is being issued to revise Qwest’s response dated November 8, 2001 to Change Request PC092701-2 requesting confirmation of all WTNs for a particular End User at a specific address for a Centrex Resale Customer. Qwest is prepared to implement the attached process to accommodate the CLECs request of confirming an End User WTNs.

Sincerely,

Susie Wells Sr. Process Analyst

(See Supplemental Information following detail report for Process)

December 4, 2001

Terry Wicks LEC Manager Allegiance Telecom, Inc. And, Kathy Stichter ILEC Relations Manager Eschelon Telecom, Inc.

This letter is in response to questions/concerns generated at the November CMP Meeting regarding Qwest’s response dated November 8, 2001 to Change Request PC092701-2.

Question: Is there a manual process available to Qwest retail that was not available to CLECs?

Answer: No. Qwest retail only retrieves CSRs for the WTNS provided by their customer .

Question: Does Qwest Retail have to get all WTN Numbers from new customers?

Answer: Yes. Qwest retail has to obtain all WTNs from their customer.

Sincerely,

Carolyn Brown Director Process Management

Cc: Monica Manning

--

DRAFT RESPONSE For Review By CLEC Community and Discussion at November CMP Meeting

Wholesale Product Marketing

November 8, 2001

Terry Wicks LEC Manager Allegiance Telecom, Inc

This letter is being sent in response to CLEC Change Request Form # PCR092701-2. PCR092701-2 pertains to a request for a process to get Full CSRs on Resale Centrex lines.

An IMA System Change would be required, in order to allow CLECs to request a Full CSR for all telephone numbers for a specific end user at a specific location. For the Resale Centrex account, DPA or DEPT and LOCN selection criteria might be added to the Review/Retrieve CSR functionality in IMA. However, a Systems Change Request would need to be created for these enhancements.

Until the IMA system changes can be deployed, you had requested that QWEST develop an interim process for obtaining end user specific Resale Centrex CSRs. Because a mechanized process does not exist, our service center personnel would have to gather this information manually. Unfortunately, QWEST does not have the resources to devote to these kinds of special requests. As long as a CLEC has the appropriate authorization, full CSRs can be retrieved through IMA. In lieu of the full CSR, partial CSRs by WTN can be retrieved. When a CLEC is unable to identify all WTNs associated with a request, the end user customer will have to be the provider of the information.

Sincerely,

Monica Manning IMA Process Specialist

Open Product/Process CR PC073101-7 Detail

Description Of Change

Granted the process of the 48 pre-testing will catch most of these ahead of cut date, things happen on cut date that cannot be prevented. Allegiance wants the decision to bring the lines over or not to be the CLEC’s call.

Status History

Project Meetings

Action : Linda Hendricks will provide definition of Qwest 'flexibility' on cut date. Allegiance will submit a new CR to clarify the Qwest process when dial tone problems are on the Qwest side.

August 23rd, 2001 Clarification Meeting 1-866-289-7092 PC 741-1286 # PCCR073101-7

Terry Wicks/Allegiance Patrick Weston/Allegiance Doug Barman/Allegiance Linda Hendricks/Qwest Todd Mead/Qwest Introduction of Attendees Terry, Patrick, Doug, Linda and Todd Review Qwest Response Linda’s response to the original CR (PCCR073101-7) was discussed. Essentially Qwest will not hand over bad circuits to a CLEC. In mitigation, Qwest has implemented the 48/1 hour DT test on July 29, 2001 to resolve this issue. There is also the opportunity for the CLEC to split the order and have the bad circuits moved to another LSR. CLEC Response Allegiance accepted that when there is no DT on the Qwest side, Qwest should not hand over circuits until the problem has been resolved. Allegiance’s position is that they would still like to be able to take the circuit. If Qwest is consistently pre-testing on their side at least 48 hours prior to cut date, then the number of incidents of bad facilities on the Qwest side on cut date should be minimal. Allegiance will track and report accordingly. Allegiance will not pursue the issue at this point when the circuit is “bad” on the Qwest side. However, they will be pursuing to take the circuit when the problem is on Allegiance’s side. Allegiance agreed that the 48/1 hour DT test implemented on July 29 should substantially reduce the number of occurrences related to this issue on the Allegiance side. However, when the “no DT” is on the CLEC side, Allegiance wants to have the circuits passed over “as is”, and do not want to split the order. Allegiance has options to get the end user service on any “broken” line when the NDT is on their side. Once the TN is activated and Allegiance has the number in their switch, they can call forward the line to another line or to cell phones they supply to the end user. Allegiance has processes in place that they use daily with this type of situation when dealing with the other LECs. Allegiance would like to be able to use their processes in this situation with Qwest as well. Allegiance is prepared to escalate as needed if this cannot be resolved at this level. Confirm Right Personnel Involved Scott Simanson, VP and Fred Aesquivel Director (Qwest) need to be involved to make the final determination on Qwest’s position with respect to this issue. An internal meeting involving these people needs to take place. Todd will organize. Identify/Confirm CLEC’s Expectation Allegiance wants Qwest to hand over good circuits if the “no DT” is on the CLEC side. Allegiance stated every other ILEC they deal with (including PacBell, SW Bell, Bell North and South, Verizon and Ameritech) do this, as part of their normal business. Establish Action Plan (Resolution Time Frame) Review these minutes as an accurate account of this mornings discussion Set up a meeting with Scott, Fred and Linda to discuss Qwest’s position and draft a response. Set up a walk-through meeting with Allegiance to discuss the Qwest final response.

08/23/01 - Clarification Meeting Allegiance - Terry Wicks, Patrick Western, Doug Baram Qwest - Linda Hendricks, Todd Mead

Allegiance accepted that when there is no DT on the Qwest side, Qwest should not hand over circuits until the problem has been resolved. Allegiance agreed that the 48/1 hour DT test implemented on July 29 should substantially reduce the number of occurrences related to this issue. However, when the “no DT” is on the CLEC side, Allegiance wants to have the circuits passed over “as is”, and do not want to split the order.

08/09/01 - Alignment Meeting Terry Wicks/Allegiance Qwest - Scott Simanson, James Mackie,Dana Frenking, Linda Hendricks, John Moore, Cindy Buckmaster, Nancy Hoag, Lisa Schuzer

Turning up loops that do not meet Qwest test requirements or do not have CLEC DT on them. Their example was if they send in an LSR with 10 loops and 2 do not have CLEC DT on them or if Qwest has a facility problem, Qwest should allow Allegiance to make the decision to accept all of the orders even if problems exist. They want Qwest to close the order and open a repair ticket to provision the loops with the problems. No CLEC DT concern: Turning up loops that do not meet requirements will leave Qwest and the end user in a vulnerable position. If the CLEC decides they can't get DT working after we have closed the order and (if applicable had the translations ran), the end user customer could be out of service. Qwest wouldn't be able to work the order back, because it is closed. In order for the end user to get back to Qwest they would need to issue a WINBACK order and the CLEC would need to issue a disconnect order on the "BAD circuit/loop turned up". Qwest's facilities concern: If Qwest has the problem and our facilities are bad or maybe in some cases won't be built out at all, the following could occur if loop is turned up bad: mask facility issues on Qwest side (or perceive that is what we are doing) open the door for repair PID issues open our selves up to many issues from provisioning to repair PID measurement accuracy billing on a bad loop

CenturyLink Response

Wholesale Product Marketing

This letter is in response to the following CLEC Change Request Form PC073101-7 dated 07/30/2001. The Change Request related to Qwest’s current practice to not complete all circuits and/or orders on a given LSR, when there is known trouble either in the Qwest or CLEC network on one or more of the circuits being turned up.

In an effort to minimize the risk of the of an out of service condition during a migration, and to ensure the readiness of all parties to maximize success, Qwest has put the following process improvements in place:

48-Hour Dial Tone Check – Qwest Central Office Technician (COT) tests for Dial Tone at the CLEC CFA on the ICDF 48 hours prior to the scheduled cut. If Dial Tone is not present, the COT notifies the Qwest QCCC Coordinator, who in turn notifies the CLEC. This gives the CLEC 48 hours to correct the no dial tone condition.

1 Hour Dial Tone Check – Qwest COT tests for Dial Tone at the CLEC CFA on the ICDF 1 hour prior to the scheduled cut. If Dial Tone is not present, the COT notifies the Qwest QCCC Coordinator, who in turn notifies the CLEC. This second notification gives the CLEC an hour to correct the no dial tone condition.

Field Pre-Survey - Qwest Field Technicians Pre Survey outside plant facilities to identify any before due date. If Field Technicians determine that facilities are not available or acceptable for the service ordered, the Technician invokes an internal Qwest process to search for other facilities or place the order in a held status if suitable facilities are unavailable. The CLEC is then notified of the Held status.

Order Splitting – Qwest has offered to “split” orders on an LSR and “supp” the order with the circuit with the trouble condition at the time of the cut, allowing the CLEC the necessary time to correct the known condition.

After considerable deliberation and reconsideration, Qwest will continue to follow its practice to not turn over circuits that do not meet all defined standards at the time of the migration. CLEC’s retain the right to escalate and to petition through the Bona Fide Request (BFR) process.

Respectfully,

Frederick M Aesquivel III Director – Local Network Operations Support

CC: Scott Simanson Linda Hendricks Dana Filip

Open Product/Process CR 5608353 Detail

Description Of Change

Status History

Project Meetings

CenturyLink Response

This letter is in response to the following CLEC Change Request Forms #5263137, dated December 1, 2000 and #5608177 and #5608353, dated June 13, 2001. All of these Change Requests pertain to the CLEC to CLEC Migration process. The revised process was released via the Co-Provider Industry Change Management Process (CICMP) on May 25, 2001.

? Re-use of facilities for CLEC to CLEC carrier changes, improving the CLEC to CLEC reuse of facilities process and to ensure nondiscrimination.

? Response: The Qwest Release Notification Forms #5393537 (CLEC Unbundled Loop to CLEC Unbundled Loop), #5393543 (CLEC Unbundled Loop to CLEC Resale), and #5467108 (CLEC LNP with Unbundled Loop to CLEC Unbundled Loop) Revision B, released on May 25, 2001, noted changes in the Pre-Order section that the requirement to obtain the “Circuit Identification Number from the OLSP” is optional. Both Eschelon and Allegiance provided Qwest with examples of orders that were rejected by Qwest due to no Circuit Identification Number provided. After gap analysis, it was determined that additional training of Qwest Service Center personnel and updates to Service Delivery M&Ps were required. The following measures have been implemented:

? An updated Multi Channel Communicator (MCC) New or Changed Information Procedure was issued on July 9, 2001. ? Issued to target Qwest internal personnel in the Wholesale Customer Care, Customer Service, Error Group, Held Order/Escalation, Order Processing and Order Resolution organizations. ? Topic of the MCC: “CLEC to CLEC Migration of an Unbundled Loop and Unbundled Loop to other products.” ? CLEC to CLEC Migration is defined as; unbundled to unbundled, unbundled to resale, unbundled to Centrex resale. ? Emphasis placed on processing orders without circuit ids (ECCKT’s) on LSR requesting migration. ? States included in this communication are; AZ, CO, IA, ID-N, ID-S, MN, MT, ND, NE, NM, OR, Outside 14 State Region, SD, UT, WA and WY. ? All internal job aids and on-line support documentation have been updated. ? Qwest Service Center specific training sessions are currently in progress for both center coaches and center personnel. The training will be on going to ensure process compliance.

Sincerely

Nancy J. Hoag Qwest Wholesale Product Team

Open Product/Process CR PC092701-3 Detail

Description Of Change

The most recent example happened today. PON 806241-HDSL1 – The FOC date to put in the circuit for this client is 09/25/01. Qwest was at the customer premises on 09/24/01 at 5:10 p.m. to do some work. The Qwest tech who went out was extremely rude to the customer. The Tech stated he has come several times, always after closing (5p.m.) and was not happy that he did not have access to the MPOE. The tech did not identify himself until the owner mentioned another company. The owner asked the tech if he worked for End 2 End Communications and the tech got upset and simply left. Several times the Qwest techs have told the customers that they would go down if they proceeded with converting to Allegiance.

Allegiance is requesting that an improved process be put in place that the CLECs can report these occurrences of anti-competitive behavior when they happen. This process should include a single point of contact , a thorough investigation with an appropriate response to the CLECs in a timely manner. The process should also include the proper training of Qwest personnel to prevent future occurrences

Status History

Project Meetings

Open Product/Process CR PC092701-1 Detail

Description Of Change

These DID numbers were for the local police and fire station in this city. Due to the inaccurate CSR we left a two-way trunk with Qwest which disrupted the hunting (this line had a DPA on it that the customer wanted to keep). There were two sets of DIDs that were not addressed so when the TFD trunk they were riding on was ported the DIDs went down. The only way we were able to find the additional DIDs was by call Qwest for assistance.

Status History

Project Meetings

Name/Company: Terry Wicks, terry.wicks@algx.com, Allegiance Monica Manning, mxmanni@qwest.com, Qwest Susie Wells, sdwell2@qwest.com, Qwest Kate Spry, kspry@qwest.com, Qwest

Introduction of Attendees Terry, Monica, Susie, and Kate Review Requested (Description of) Change Develop a process for CLECs to get a “full” CSRs on DID numbers. Confirm Areas & Products Impacted Areas: Pre-Ordering / Ordering Products: Resale Confirm Right Personnel Involved Monica Manning is the ‘owner’ of this CR and will be the point of contact for future problems of this nature until the root cause is established and draft response issued. Susie would like to stay informed as to response and is available for questions pertaining to her area. Terry Wicks would like to stay informed as to response. Kate will coordinate all necessary clarification meetings, complete meeting minutes, and review, forward, and send information to Mike Keegan and Matt Rossi to store to database. Identify/Confirm CLEC’s Expectation Allegiance is requesting that a process be developed by Qwest to allow CLECs to be able to retrieve a full and complete CSR for all DID numbers for a specific End User at a specific location. Currently Allegiance is not confident that the information received through IMA is accurate. We have had several instances of End Users going down after conversion due to DIDs not being addressed. The reason for this is that not all DIDs are showing up on the CSRs. One example is for City of Tukwila BTN 206-433-1800. The CSR we pulled in IMA only shows the block 206-433-1844 to 1851 when in actuality the range goes to 1871. Qwest also advised us the DID 206-433-1856 did not exist. This meant that there was a break in the range of 206-433-1844 to 1855 then 206-433-1857 to 1871. DID range 206-433-7140 to 7199 is totally unaccounted for on the CSR.

These DID numbers were for the local police and fire station in this city. Due to the inaccurate CSR we left a two-way trunk with Qwest which disrupted the hunting (this line had a DPA on it that the customer wanted to keep). There were two sets of DIDs that were not addressed so when the TFD trunk they were riding on was ported the DIDs went down. The only way we were able to find the additional DIDs was by call Qwest for assistance. To clarify, two points are being addressed: ? When you pull a CSR and submit a request, the phone numbers aren’t on the CSR in the LSR. Is it then rejected? If so, why don’t they show up in the CSR if they are rejected? Terry gave the following examples: Here are the PONs where we ported these DID ranges: PON 699510-NP 206-431-3650 thru 3689 699510-NP1 206-431-3890 thru 3899 699510-NP2 206-433-1804 thru 1843

We have not completed the porting of these PONs: PON 860171-NP1 206-433-1844 thru 1855 PON 860171-NP2 206-433-1857 thru 1871 PON 860171-NP3 206-433-7140 thru 7199

The following TNs were on our CSR but we were told by Qwest there were additional TNs not showing up: 206-433-1844 thru 1851

The following TNs were not on our CSR we pulled from IMA for BTN 206-433-1800 206-433-1852 thru 1855 206-433-1857 thru 1871 206-433-7140 thru 7199

? Additional DIB ranges need to be addressed.

Identify any Dependent Systems Change Requests No related system CR’s were identified Establish Action Plan (Resolution Time Frame) Monica will clarify process via a written formal response draft. After clarification is received regarding possible system changes. She will forward this documentation to Kate by 10/18/01. Kate will review and forward the response draft to Mike Keegan and Matt Rossi to store in the CR database by 10/19/01 for CLEC review. The web location will be noted in Matt Rossi’s email regarding the response document by 10/22/01. This information can then be reviewed and discussed by the CLEC Community at the following CMP Meeting. Terry can view this information on the CR database and this CR can then be reviewed and discussed by the CLEC Community at the following CMP Meeting. Corrections/updates can then be made at that time.

CenturyLink Response

November 8, 2001

Terry Wicks LEC Manager Allegiance Telecom, Inc

This letter is being sent in response to CLEC Change Request Form # PC092701-1. PC092701-1 pertains to a request for a process to get a full CSR on DID numbers.

We have reviewed the list of LSRs and associated CSR you provided to QWEST for this Change Request. While it may have appeared that a Full CSR was provided to you by IMA, the Review Full CSR Response displayed a message indicating that only 52 of 61 pages were returned. This would explain why only a portion of the DID numbers for the account appeared.

The IMA User Guide provides instructions on how to retrieve additional CSR data, when the complete CSR is not displayed. This information can be found in Chapter 1 of the User Guide, under Reviewing Customer Service Records. As long as a Full CSR request does not exceed the page number limitation (300 pages in the IMA GUI, 450 pages in IMA EDI) and the CLEC is authorized, all of the CSR pages should be returned. If the instructions in the User Guide are followed, all of the CSR pages can be retrieved.

If you should encounter this trouble again while trying to retrieve a full CSR and have followed the steps outlined in the User Guide, please contact the Wholesale Systems Help Desk at (888) 796-9102 immediately. If we receive a trouble report regarding CSR retrieval "as it is occurring", we will be able to determine the root cause and correct the problem.

Sincerely,

Monica Manning IMA Process Specialist

Open Product/Process CR PC081902-1 Detail

Description Of Change

Qwest has been pointed out that this is not a new or even a changed process. Qwest has stated that this information has been in the SGAT for approximately 6 years. Allegiance has never opted into the SGAT language for our ICA and up until 8/02/02, Allegiance was never aware that this information was documented in the SGAT.

Here is the wording for reference:

“If you are not ready within thirty (30) minutes of the scheduled appointment time, then you must reschedule the installation by submitting a supplemental LSR. If Qwest is not ready within thirty (30) minutes of the scheduled appointment time, Qwest will waive the nonrecurring charge for the installation option. You and Qwest will attempt to set a new appointment time on the same day and, if unable to do so, Qwest will issue a jeopardy notice and a FOC with a new Due Date.”

The statement implies that “if for any reason” the CLEC is not ready, then it will be SUPd at 31 minutes. It does not take into account that if Qwest fails to notify us of a no dial tone issue, according to the current 48 hour dial tone testing requirements, then the CLEC is still held accountable for not being ready and the order will be SUPd. At the maximum, we may have 1 hour and 30 minutes from the start time of the cut to resolve a no dial tone issue if no notification was sent prior to due date. This has happened to Allegiance several times, and some QCCC testers hold fast to this policy. We have had to escalate on these instances and in some cases it has been denied and the order was JEPd. The wording needs to change to identify exceptions to the rule.

If Qwest is not ready for whatever reason according to this policy, Qwest will work with the CLEC throughout the day to get it cut. But if the CLEC is not ready, Qwest is only allowing a maximum of 1 hour and 30 minutes ( less in many instances) to "get ready" or the order will be JEPd.

Qwest is not taking it into consideration when Qwest fails to follow all steps of the 48 hour dial tone testing requirements and timely notification to the CLEC. When Qwest fails to do this, Qwest is considering that the CLEC is not ready. Allegiance believes that in this type of situation, it is Qwest that is not really ready because Qwest has not followed all steps of the process. Qwest’s consequence for not doing the cuts on due date is the potential that Qwest may have to pay penalties. The current policy is allowing Qwest to work with the CLEC to get it done on cut date to avoid such penalties. The consequence to the CLEC is we can lose that customer if we cannot get the order cut on due date as promised and we only have a limited time to “get ready” in order to complete the cut.

Status History

Project Meetings

02/19/03 February CMP Meeting

Deni Toye–Qwest provided statistics regarding PTA NDT Notifications. All were sent within the 24-36 hour time frame. The QCCC has not been out of compliance so we have not executed the 30 minute rule. Lori Mendoza–Allegiance reported they have not had any problems, except they have gotten some PTA notifications without CFA information. This information has been provided to their Service Manager to investigate. Sharon Van Meter–ATT advised she will be meeting with her company to determine whether they will begin to use the PTA tool. This CR will be left in CLEC Test status until next month. At that time we will review additional feedback from the CLEC Community and determine a close date.

01/15/03 - Janaury CMP Meeting

Toye-Qwest stated that Qwest had distributed a notification on this CR and had responded to CLEC comments to the changes. Johnson-Eschelon stated that she had not yet read the Qwest response. Mendoza-Allegiance stated that Qwest has been much better, recently, on no-dial-tone notifications. This CR remains in CLEC Test.

12/18/02 - December CMP Monthly Meeting Minutes Qwest-Linda Hendricks advised the PCAT is out for CLEC comments with a planned implementation date of January 31. This CR will change to CLEC Test.

11/20/02 - November CMP Monthly Meeting Minutes Qwest (Hendricks) reported the PCAT is under development. This project will remain in Development status.

10/16/02 - October CMP Meeting Minutes Qwest reviewed the Acceptance Response to this CR and outlined when the exception will apply and when it will not apply. Eschelon clarified the following scenario: If Qwest can not reschedule the CHC for the same day the exception process will not apply. ATT expressed their concern that the exception process does not apply to VP Expedites. Qwest clarified the current VP Expedite Process does not change and this CR does not override the current VP Expedite Process. Qwest obtained agreement this CR would be handled as a Level 3 change and will follow the Level 3 process. This CR will move to Development status.

09/24/02 - September CMP Meeting Minutes Terry Wicks - Allegiance introduced and explained this CR would allow for an exception to the 30 minute rule for CHC process if CLECs do not get at least 24 - 48 hours NDT notification from Qwest. This applies to CHC only, not basic. In the case of not receiving notification QCC would work with the CLEC to reschedule the technician for sometime the same day instead of sup the LSR at 31 minutes. Jonathan-ATT said this should reduce the number of C01 misses. Linda Hendricks - Qwest explained if we are not doing the PTA email notification we won't be able to track whether the 48 hour NDT notifcation occurred. Eschelon and Allegiance expressed their support of the PTA tool. Qwest advised a response would be provided at the October meeting.

1:30 p.m. (MDT) / Monday 26th August 2002 1-877-561-8688 PC738 5723# Review CR PC081902-1 30 minute rule for Coordinated Hot Cuts

In Attendance: Terry Wicks - Allegiance Linda Hendricks - Qwest Bob Mohr – Qwest Cheri Hurless – Qwest Neil Houston – Qwest Cindy Macy – Qwest Ric Martin – Qwest Linda Sanchez-Steinke – Qwest Deb Smith – Qwest Deni Toye - Qwest

Introduction of Attendees

Review Requested (Description of) Change : Reviewed CR and confirmed business issues this CR will address. Terry requests the wording in the PCAT be changed to reflect an exception to the 30 minute rule if Qwest does not follow the 48 hour DT testing process. If Qwest notifies CLEC with 24 hours or less advance notice an exception process needs to be available. The exception process would allow Qwest and the CLEC to set a new appointment time on the same day, instead of jeopardizing the order and requiring the installation to be rescheduled by submitting a supplemental LSR. The business issue this CR is addressing is prevention of customer loss.

Confirm Areas & Products Impacted : Unbundled Loop / UNE / Loop Conversion orders existing customers PCAT – Ordering Wholesale UNE Installation Option Coordinated Installation with / with out testing

Confirm Right Personnel Involved : Linda Hendricks – confirmed as Lead SME Neil Houston – Network Regulatory Bob Mohr – Product Manager Cheri Hurless – Service Manager Cindy Macy – Change Request Project Manager

Identify/Confirm CLEC’s Expectation : Terry requests the wording in the PCAT be changed to reflect an exception to the 30 minute rule if Qwest does not follow the 48 hour DT testing process. If Qwest notifies CLEC with 24 hours or less advance notice an exception process needs to be available. The exception process would allow Qwest and the CLEC to set a new appointment time on the same day, instead of jeopardizing the order and requiring the installation to be rescheduled by submitting a supplemental LSR.

Identify any Dependent Systems Change Requests : CR PC 081902-2

Establish Action Plan (Resolution Time Frame) Document and issue meeting minutes within 5 business days (9-3-02) - Qwest Present CR at September CMP Meeting - Allegiance Present Draft Response at October CMP Meeting - Qwest

CenturyLink Response

October 16, 2002 For Review by CLEC Community and Discussion at October's CMP Meeting

Allegiance Telecom, Inc

SUBJECT: Qwest’s Change Request Response - CR #PC081902-1 The 30 minute rule for Coordinated Hot Cuts

Allegiance Telecom, Inc is requesting that Qwest change the wording and current process to allow the CLEC to work with Qwest on due date to get the cut done, when Qwest has failed to timely notify the CLEC according to the notification of NDT process, just as Qwest is allowing itself to do when Qwest is not ready. Update the PCAT with any changes resulting from this CR.

Qwest will accept the “30 Minute Exception” CR with the following guidelines:

-All CLECs must be enrolled in the NDT PTA Notification procedure in order to have accurate tracking and parity to ensure the success of the “30 minute rule” process.

-If Qwest fails to notify the CLEC within the timeframe of the NDT notification procedure, we will attempt to reschedule at a mutually agreed upon time for the same day.

-If Qwest is able to reschedule the same day it will not require a Customer Not Ready jeopardy and will not require a supp to the LSR. However the order will be in a CLEC delay status documented on the OSSCN screen in WFA/C.

- Rescheduling the Coordinated Hot Cut may not be workable on the same day. The appointment may require another date and time. This will result in a Customer Not Ready jeopardy.

- This process will be rework for Qwest in several departments and will require the CLEC to supp their LSR if another day and time is required.

The “30 Minute Exception” will not apply when:

- If Dial Tone is found at 48 hours before Due Date and noted in the OSSLOG, then at 1 hour before the due date the Dial Tone is no longer present.

- If the CLEC is not using the PTA NDT Email Notification.

- If the email systems of either Qwest or the CLEC were not working during the notification period, tracking would be invalid.

- If the CLEC has requested a VP Expedite and the interval does not allow the appropriate time for DT verification and CLEC notification (This process does not over ride the VP Expedite Process)

Qwest will issue this as a Level 3 change and seek concurrence of this approach at the October CMP Meeting.

Sincerely,

Linda Hendricks Lead Project Analyst Qwest

Cc: Mary Pat Cheshier, Diane Diebel

Open Product/Process CR PC062602-3 Detail

Description Of Change

Status History

Project Meetings

Allegiance advised they would withdraw this CR which will be satisfied with the System CR’s, providing Qwest opens a Global Action Item to research if a column with their Trouble Ticket Number could be added to the current spreadsheet they receive from their Service Manager. Qwest advised that they are looking into this action item. Qwest expressed that development of the spreadsheet is a complicated process. No participating CLEC indicated that they wanted to assume sponsorship of this CR. The CR will be status Withdrawn and a Global Action Item will be opened.

--

08/30/02 Conference Call

Ric Martin and Craig Suellentrop, Qwest, held a conference call with Terry Wicks, Allegiance to discuss the manual and system aspects of their CR. Qwest advised that the system aspect of Allegiance’s CR would be covered under the resultant Systems CR from combining the various System CRs on Trouble Tickets and Repair Charges. Qwest advised that the Systems resolution would look at the “Input” aspect (CEMR and MEDIACC) of getting CLEC Trouble Tickets and the “Output” aspect (Bill) of cross-referencing trouble tickets and Circuit IDs, etc. Allegiance was in agreement with the handling of the systems aspect of their CR. Qwest explained that there might be something that could be done on the manual process aspect, but there wouldn’t be any meaningful output until the systems fix was accomplished. Qwest indicated that they would still pursue the manual aspect if Allegiance were interested in this. Allegiance indicated that they didn’t want Qwest to duplicate efforts on a manual and systems fix. Allegiance asked if Qwest would look into modifying the spreadsheet they get from their Service Manager to include their internal Ticket Number. Qwest advised that they would open a Global Action Item to look at this and asked Allegiance to send an e-mail with a copy of the spreadsheet and details on what they would like included and at the September CMP meeting we would discuss the disposition of their CR.

08/21/02 August CMP Monthly Meeting Minutes

Qwest reviewed its draft response and advised that this CR would be reviewed in conjunction with other CRs related to trouble tickets, repair charges, etc. scheduled for August 27, 2002. The CLEC participants agreed to have this CR reviewed at that meeting. Qwest clarified that a manual process could be developed to request the CLEC trouble ticket, but it would be input into the remarks field that doesn’t have any sorting capability. Allegiance indicated that they currently receive a spreadsheet with the Qwest trouble ticket identified and asked if Qwest couldn’t put Allegiance’s ticket number on the spreadsheet. Qwest confirmed that the spreadsheet is created from a Web site and maintained by Nancy Tangeman.

07/17/02 - July CMP Meeting Minutes: Allegiance introduced their Change Request. Qwest stated the need is to create a process to capture the information Allegiance has requested. CR status is evaluation.

CLEC Change Request Clarification Meeting

July 2, 2002 9:00 a.m. (MT) Conference Call 877-564-8688 PC062602-3, Cross Reference CLEC Trouble Ticket number on Qwest Trouble Ticket Numbers

Attendees: Ric Martin, Qwest Lynn Stecklein, Qwest Craig Suellentrop, Qwest Alice Matthews, Qwest Terry Wicks, Allegiance

Introduction of Attendees Introductions of the participants on the Conference Call were made and the purpose of the call discussed

Review Requested (Description of) Change Terry indicated that this CR was different than the Systems CR that has to do with the CEMR update. Allegiance does not use CEMR and call in their trouble to the AMSC. Allegiance wants to be able to call tickets in, provide their internal number, have it cross referenced with Qwest’s number and to have their internal number show up on the bill. Terry indicated that they would like to see a process change that would require Qwest to get an Internal Ticket number from the CLEC before they open up a trouble ticket. Terry indicated that they intend to e-bond with MEDIACC in the future, which allows them to electronically report trouble without making a phone call. Craig confirmed that the trouble tickets called in are entered into WFA-C and Qwest would need to look into what the flow through systems are. Additionally Qwest will need to look into what is needed to have Allegiance’s ticket number appear on the bill. Terry indicated that no matter how we open up a ticket, the cross-reference to the CLEC Ticket on the bill is what matters. Terry will look into how e bonding to MEDIACC would be communicated and if there is a field currently that would allow this. He will look into whether a systems CR would be required for MEDIACC.

Confirm Areas & Products impacted It was confirmed that the area impacted was Billing and Maintenance & Repair. The product impacted is UBL.

Confirm Right Personnel Involved Qwest confirmed that Craig would remain the SME for now.

Identify/Confirm CLEC’s Expectation Terry confirmed that they were looking for: 1. A process to have the AMSC not open a trouble ticket without first getting a CLEC internal trouble ticket. 2. Determine best method to get CLEC trouble ticket number on the bill.

Identify any Dependent Systems Change Requests Systems CR SCR030702-1 has to do with CEMR update to include a field for CLEC Trouble Ticket. Systems CR SCR042902-01 has to do with getting the CLEC trouble ticket number onto the bill.

Establish Action Plan (Resolution Time Frame) The CR will have the collective CLEC clarification and SME input at the July CMP meeting.

CenturyLink Response

Terry Wicks LEC Manager Allegiance Telecom, Inc.

SUBJECT: Qwest’s Revised Change Request Response - CR PC062602-3 “Cross Reference CLEC Trouble Ticket number on Qwest Trouble Ticket numbers.”

This CR requests that “the CLECs internal trouble ticket number to be a required item to be provided to the Qwest Representative issuing the Qwest trouble ticket. This will allow for both the Qwest trouble ticket number and the CLECs internal trouble ticket number to be cross referenced to each other.” Allegiance would also like the CLEC’s trouble ticket number to appear on bills for maintenance and repair charges.

Because of the large number of Charge Requests related to Maintenance and Repair, a meeting was held on August 27, 2002 to discuss possible synergies between the various CRs. As a result of this meeting and further consultation with Allegiance on August 30, 2002, it was determined that the system CRs SCR030702-1 – CLEC Trouble Ticket Cross Reference and SCR042902-01 – Use CLEC Internal Repair Ticket number on CLEC bill to identify maintenance and repair charges would address the concerns raised by this CR relating to cross-referencing trouble ticket numbers and CLEC trouble ticket numbers appearing on the bill. Allegiance agreed that a separate manual process would not be required with the development of the system enhancements covered by these CRs.

Allegiance also raised an issue concerning a spreadsheet they receive from their Qwest Service Manager that contains all of the TOK and NTF tickets. Allegiance would like to see their trouble ticket number on this spreadsheet. Qwest and Allegiance agreed that this issue could be pursued as a Global Action Item and that Qwest will continue to investigate this issue.

Sincerely,

Craig Suellentrop Staff Advocate, Policy & Law Qwest

Cc: Mary Retka, Director-Legal Issues, Qwest Catherine R. Garcia, Senior Process Analyst, Qwest Alice Matthews, Senior Process Analyst, Qwest Dan Busetti, Lead IT Analyst, Qwest

--

August 13, 2002

Terry Wicks LEC Manager Allegiance Telecom, Inc.

SUBJECT: Qwest’s Change Request Response - CR PC062602-3 “Cross Reference CLEC Trouble Ticket number on Qwest Trouble Ticket numbers.”

This CR requests that “the CLECs internal trouble ticket number to be a required item to be provided to the Qwest Representative issuing the Qwest trouble ticket. This will allow for both the Qwest trouble ticket number and the CLECs internal trouble ticket number to be cross referenced to each other.” Allegiance would also like the CLEC’s trouble ticket number to appear on bills for maintenance and repair charges.

The current repair process for Designed Services allows a CLEC to offer the CLEC trouble ticket number to the Qwest representative opening the Qwest trouble ticket. The CLEC trouble ticket number will be entered into a remark field. This field is not “searchable” and does not appear on CLEC bills. This option is not available for Non-Designed Services. Qwest would agree to a process change to ask all CLECs for their internal trouble ticket number, but without systems changes this would not address the majority of Allegiance’s concerns.

Open System CR’s SCR030702-1 – CLEC Trouble Ticket Cross Reference and SCR042902-01 – Use CLEC Internal Repair Ticket number on CLEC bill to identify maintenance and repair charges also would require a very similar process. A meeting will be scheduled for late August to discuss the similarities between these and some other CR’s involving maintenance and repair. Further clarification and direction for this CR will be determined after this meeting.

Sincerely,

Craig Suellentrop Staff Advocate, Policy & Law Qwest

Cc: Mary Retka, Director-Legal Issues, Qwest Catherine R. Garcia, Senior Process Analyst, Qwest Alice Matthews, Senior Process Analyst, Qwest

Open Product/Process CR PC061002-1 Detail

Description Of Change

Expected Deliverable:

Qwest to change this process ASAP, give the CLEC a reasonable amount of time (90 minutes) to correct a no dial tone situation on a reuse of existing facilities and give loops to the CLEC if there is continuity to the spot pair on new facilities

Status History

Project Meetings

- 10/16/02 October CMP Meeting Michael Buck with Qwest said that final notification PROD.10.11.02F.00839.Final24WireLoop was sent on 10/11/02 and the implementation date is 10/27/02. The CR is currently in Development Status and Qwest would like to move it to CLEC Test on the deployment date later this month. Byron Dowding with Alltel said that it was appropriate to move to CLEC test and discuss again at the November CMP meeting.

09/18/02 September CMP meeting Minutes Qwest discussed the revised draft response and provided an update that Qwest would no longer require dial tone on new unbundled loops effective mid-October. Conversion orders will continue to require dial tone. Qwest explained that the effective date is following the PCAT update for 2-wire 4-wire, Version 11, which is effective October 21, 2002. Allegiance and Eschelon appreciate Qwest changing to the no dial tone requirement on new unbundled loops. Allegiance also noted a clarification from the August Meeting minutes regarding the conversation on this CR. At the August meeting Lyndall Nipps – Allegiance asked why doesn't Qwest check for continuity on DS0 loops like you do for DS1 and above loops by plant test date. Qwest responded that it was not in the infrastructure to test for continuity on DS0 loops. A pre-survey is done for all UBL except for LX - -. LX - - is worked on the due date. This CR was moved to Development status.

9/12/02 2:29 p.m. To: cc:

Subject: RE: Updated Draft Response to CR PC061002-1

Byron -

The following is in response to Alltel's questions in your e-mail dated 8/27/02:

1. CHC means Coordinated Hot Cut (Y or N). You can have a Hot Cut with the Basic Option. Hot Cut means we go from one service provider to another on an existing service, this option can be ordered Coordinated or Basic.

2. Qwest is preparing to only require dial tone on reuse LX-- in mid-October.

3. The polarity of the Qwest wiring and facilities, from the CFA to the NI at the end user locations, can be checked using normal Qwest test systems and sets. The polarity of the supplied CLEC service can not be tested without the CFA operationally in service. If the CLEC provides service on the CFA with reversed polarity, Qwest will not reverse their wiring or facilities to correct, as this would impair Qwest’s ability to properly maintain the circuit in service. The polarity of a loop start line is of significant importance when the facility provided is anything but a plain copper loop. Pair Gain facilities require correct polarity of supplied service to operate correctly.

4. Qwest is preparing to only require dial tone on reuse LX-- in mid-October.

Please call me if you have any questions.

Thank you

Linda Sanchez-Steinke Change Request Project Manager Qwest

-- From: Byron.Dowding@alltel.com on 08/27/2002 08:03:51 a.m. To:

Subject: RE: Updated Draft Response to CR PC061002-1 Linda This is ALLTEL's response to the Qwest response I don't have any feedback yet to verify Qwest allowing more than 30 mintutes to provide dial tone on a loop. Byron

SUBJECT: ALLTEL response to Qwest response regarding change request PC061002-1 dated 08/19/2002

ALLTEL would like to make the following points.

1. The first statement in Qwest’s response states that this CR is about Qwest’s Hot Cut process. CR PC061002-1 has nothing to do with Hot Cuts. This CR is about ordering an unbundled loop with the Basic option and no testing (CHC is N). The service being ordered is 2/4 wire analog with the NC code of LX--. Due date on the loop being turned over to the CLEC and actual customer in service date don’t have a direct relationship. 2. The CLECs have stated several times that ordering a new loop and reuse should be handled as 2 different issues. We are willing to provide dial tone in a reasonable time when we are reusing a facility. When ordering a new loop no dial tone should be provided. 3. Our techs check for polarity when shooting trouble and can reverse the jumper/drop to correct the problem. Polarity should never be an issue with loop start dial tone. I would like to know how Qwest could check for polarity on loop start dial tone when dial tone is provided. 4. For the most part providing dial tone requires CLECs to program dummy numbers in their switch and then reprogramming when the service is actually turned up. This places a costly and unneeded burden on the CLECs.

ALLTEL is planning to charge Qwest for providing joint test capabilities when ordering unbundled loops that Qwest requires dial tone on. ALLTEL is also going to work with the regulatory agencies to significantly reduce the one-time charges associated with provisioning these types of loops.

-- 08/21/02 - August CMP Meeting Minutes: Qwest provided an updated draft response dated August 19, 2002 because information was missing in the August 13, 2002 draft response. The updated draft response is available on line and was handed out to participants in the meeting. Allegiance expressed concern that the 2-wire 4 wire PCAT updated language does not distinguish between new loops and conversions and that Allegiance and other CLECS are trying to find out the technical reasons why Qwest requires dial tone on new loops when there are other ways to check for continuity. Allegiance asked if Qwest checks for continuity from demarc to the central office before plant test date. Eschelon also asked for Allegiance’s question to be answered; does Qwest dispatch for continuity. Qwest stated (Hilleary) that we are pushing for dial tone on due date and dial tone 48 hours before due date is not a requirement. Allegiance disagreed. Qwest stated (Hendricks) that dispatch for continuity is not done, and the pre-survey is done to make sure there are facilities. Qwest stated (Braegger) that on services provided on UDC there is no way to verify correct service operation without Dial Tone on the circuit. Covad said that on digital loop carrier card verified set options correctly if have dial tone. Qwest (Braegger) stated that if Dial Tone is coming in reversed to the card, the card will not operate correctly and won’t operate unless there is battery to it.

Covad asked what would prevent Qwest technician from putting dial tone on temporarily from ICDF at cosmic frame. Qwest (Retka) asked that Covad send in procedure on a CR for Qwest to use spare dial tone temporarily from the ICDF.

Allegiance indicated that Qwest was the only ILEC requiring dial tone on new loops and is a burden on all CLECs when changing from T1 to UNE loop because translations are required for two different numbers and when Qwest checks for ANI the line is not the right number. Eschelon said there is effort that they must go through internally assigning dummy numbers to CFA to provide dial tone for Qwest.

Allegiance asked how Qwest identifies a fault and what does it mean in PCAT wording, pages 5-6 under the ordering section, asked if the purpose of notification is relationship managing. Eschelon asked if they should receive a jeopardy rather than a call if there was a short. Qwest (Boudhaouia) stated Qwest will re-write the PCAT. Allegiance said that the language creates concern over PIDS managing to process and Allegiance does not want the PCAT updated on 8/26/02. Qwest (Maher) stated that for Qwest and the CLECs to follow the CMP, the PCAT would be updated on 8/26/02 because there were comments from the CLEC community on the PCAT change, and Qwest had followed CMP and responded to those comments. Qwest (Schultz) clarified that the PCAT update included documentation of processes that were currently in effect. Allegiance objected to the PCAT update on 8/26/02.

Alltel asked for status of CR. Qwest (Graham) reviewed draft response part 1 reviewing why tests are done and the technical reasons for dial tone requirement.

Qwest (Hendricks) reviewed draft response part 2 reviewing the procedure for the basic option. When the CLEC selects the basic option and is not ready on due date, the technicians go on to their other work. If the CLEC calls back later in the day, then Qwest will try to get technicians back out. Alltel (Dowding) will check with Alltel people that asked for CR because they had said at 31 minutes the order has to be supplemented. Qwest explained that the 31 minutes would be applicable on the appointment time option but is not applicable on the basic option.

Due to another scheduled meeting, which many CMP participants wished to attend, the meeting was adjourned before discussion on the final disposition of the CR was concluded. Qwest will work offline with Alltel regarding the status of the CR and bring the CR back up for discussion at the September CMP meeting.

CLEC – Qwest Change Management Process Monday, August 12, 2002 Ad-Hoc meeting to discuss CLEC comments and CR Conference Bridge: 877.521.8688, passcode 7901848#

NOTE: These DRAFT meeting minutes were developed August 19, 2002 by Qwest following a meeting on the 2Wire 4Wire CLEC Dial Tone Requirement

MEETING MINUTES

The meeting was initiated by Qwest via Change Management notice CMPR.08.06.02.F.01307.CMPMtgFinalized that was distributed to the CLECs on August 6, 2002. Qwest scheduled the meeting to discuss the following two items with members of the CLEC community:

1) CLEC comments received for Notice PROD.07.12.02.F.00784.AnalogLoop24Wire 2) CMP Change Request PC061002-1 titled, “LSR put in Jeopardy when no dial tone present when Qwest installs Unbundled Loop” from Alltel.

The meeting began with Qwest reviewing the Qwest response to CLEC comments from Allegiance, Alltel, and Eschelon on the Level 3 notification sent out by Qwest on July 12th, 2002, PROD.07.12.02.F.00784.AnalogLoop24Wire. Several CLECs asked when the comments response had been distributed and Qwest responded that the notification had gone out the evening of August 9th, 2002, via notice PROD.08.09.02.F.00807.AnalogLoop24Wire and that the Qwest response to the comments had been posted under the Qwest CMP Product/Process Archive Document Review site under PROD.07.12.02.F.00784.AnalogLoop24Wire. Qwest then reviewed the response to comments with the attendees on the call. Allegiance stated that the Qwest posted comments referred to both conversion of analog loops as well as new installations, and that Allegiance did agree that CLEC dial tone should be required on conversion orders but not on new orders. Eschelon asked why the PCAT was being updated associated with PROD.07.12.02.F.00784.AnalogLoop24Wire. Qwest responded that the PCAT was being updated to reflect the requirement that Qwest currently has in place for these types of orders, and that the requirement was for CLEC dial tone prior to order completion. Eschelon, Allegiance, and ATT requested that the PCAT update be delayed until there was final resolution of the Alltel CR. Qwest responded that this request was out of process because the PCAT update needed to take place August 26th based on the final notice PROD.08.09.02.F.00807.AnalogLoop24Wire, but Qwest would take the request to delay the PCAT update back for final determination. Eschelon stated that there was no reason for CLEC comments if Qwest did nothing with them. Qwest responded that Qwest does take CLEC comments under consideration, but there is no CMP requirement to revise product/process changes based upon CLEC comments. Allegiance then stated that Qwest was the only ILEC requiring CLEC dial tone prior to order completion on NEW orders, and that Qwest needed to reevaluate the requirement. Covad stated that the issue could be resolved by Qwest providing Qwest dial tone to test the circuits, or that there were other test alternatives Qwest could implement. Qwest responded that the requirement for CLEC dial tone was still in effect due to technical requirements outlined in the response to CLEC comments, and that Qwest would provide a response to the Alltel CR at the August 21st CMP Monthly Product/Process meeting. The CLECs requested that a specific block of time be set aside at the CMP Monthly Product Process meeting to discuss this issue so they could have their technical subject matter experts on the call. Qwest agreed to set aside a specific time on August 21, 2002 to further discuss this. The time will be 1PM MT. The call-in number is 877 572-8687 passcode 3393947. The meeting then adjourned.

-

07/17/02 - July CMP Meeting Minutes: Alltel introduced their Change Request. Alltel requested the wording in the meeting minutes for the clarification meeting held on June 18, 2002 be changed from “48 hours before the Due Date” to “48 hours after application date”. Allegiance stated that Qwest is the only ILEC requiring dial tone testing for testing continuity. Covad stated it should be the CLECs responsibility for providing dial tone. Eschelon stated all CLECs are interested in this Change Request. CR status is presented.

Clarification Call Time/Date: 11:00 qa.m. (MDT) / Tuesday, June 18, 2002 Place: Conference Call Conference: TEL: 877.521.8688 Call-In No: CODE: 7901848 CR No: PC061002-1 "LSR put in Jeopardy when no dial tone present when Qwests installs Unbundled Loop"

Attendees: Byron Dowding, Alltel Neil Houston, Qwest Linda Hendricks, Qwest Steve Hilleary, Qwest Michael Keegan, Qwest

1.0 Attendees introduced. 2.0 Description: The following is extracted from the CR submitted by Alltel: When ALLTEL orders an unbundled loop with a NC Code of LX--and the CHC marked N, Qwest checks for dial tone at the end user (new loops) or at the spot pair (reuse facilities). If there is no dial tone present, Qwest contacts the CLEC gives them 30 minutes to get dial tone on the loop or the LSR is put in Jeopardy and a new LSR has to be written with a new due date. If the order contains multiple loops and one of the loops does not have dial tone, all of the loops are placed in Jeopardy. Qwest has responded to our concerns saying that this has always been their procedure but it was not being followed. Because these orders are not coordinated hot cuts, Qwest can make their cut anytime during the day. It could even happen over a lunch hour. We have also had situations where Qwest has put a loop on the wrong spot pair, had no dial tone at the customer’s premise and placed the order in Jeopardy.

Clarification Call Discussion: Alltel indicated that this problem started recently (60 – 90 days ago) and has occurred at both Omaha and Grand Island, Nebraska

Alltel said the problem is they get a call from Qwest on the due date when no dial tone is present and the order is placed in jeopardy if the problem is not corrected in 30 minutes.

Qwest does a Dial Tone check on both Basic and Coordinated LX - - (2W/4W Analog)type orders on DVA (Design Verify Assign) which is approximately 48 hours after application Date. If there is no Dial Tone at that time Qwest contacts the CLEC to let them know there is no dial tone at this time. The notification is approximately 24-36 hours before the Due Date. I have verified a couple of orders and we have called Alltel after the Dial Tone Check to notify them that there was No Dial Tone at DVA. On Due Date Qwest does another Dial Tone check before they do the install or hot cut before Qwest starts to do the work. If Dial Tone is not present, the COT calls the QCCC (Qwest CLEC Coordination Center) Coordinator. The QCCC Coordinator calls the CLEC and lets them know that Dial Tone is not present at their CFA (Connecting Facility Assignment). The CLEC is given 30 minutes to correct the Dial Tone situation. If the CLEC is not ready in 30 mintues they are requested to send a supplement to their LSR for a new Due Date. If the LX- - has a Reverse Battery or No Signal NCI (Network Channel Interface) Qwest does not require Dial Tone to be present at the CLEC’s CFA. If the order has multiple loops the CLEC may split out the LSR and accept those that do have Dial Tone. The order without Dial Tone may be put on a separate LSR. The Coordinated Appointment Time Option allows the CLEC to choose exactly when they want the installation or hot cut to be performed. The Basic Option allows Qwest to start the installation or hot cut any time between 8AM and 5PM regional time. The COT should be doing the ANI test on the loop before and after they perform the lift and lay. The correct number should be identified. This is the process in place and should be followed to insure the accuracy of the request.

Linda Hendricks will prepare the Qwest response.

3.0 Confirmed that UNE Loop is the product impacted.

4.0 Qwest confirmed the correct personnel were on the call.

5.0 CLEC expects Qwest to change this process ASAP, give the CLEC a reasonable amount of time (90 minutes) to correct a no dial tone situation on a reuse of existing facilities and give loops to the CLEC if there is continuity to the spot pair on new facilities

6.0 No Dependent Systems Change Requests were identified,.

7.0 Action Items Alltel can present this Change Request to the CLEC community at the July Product/Process CMP meeting scheduled for July 17 Qwest will issue draft response to this Change Request by Aug 14 (one week prior to the Aug 21 CMP meeting). Qwest will discuss the draft response at the Aug 21 CMP meeting.

CenturyLink Response

Byron Dowding OSS Coordinator Alltel

SUBJECT: Qwest’s Change Request Revised Response - CR #PC061002-1 LSR put in jeopardy when no dial tone present when Qwest installs unbundled loop Alltel is requesting that Qwest change its Hot Cut process to allow for 90 minutes when no Dial Tone is present at the CFA and not to reject orders with multiple service requests when one of the requests must be rescheduled. (Part 1, No Dial Tone) Dial tone is required to provide a quality installation of the service ordered. To ensure adequate circuit level performance, installation and operational tests are performed. Dial tone must be present to perform these tests across the entire circuit: - To verify the assurance of the assignment and translation of the CFA. - To confirm the Competitive Local Exchange Carrier (CLEC) Connecting Facility Assignment (CFA) is operational and test hard wiring from the Qwest Interconnection Distribution Frame (ICDF) to the CLEC CFA. - To perform a polarity test at the termination of the Network Interface Device (NID) and to perform an overall end to end operational circuit test to ensure reliability and functionality. - When provisioning over Digital Loop Carrier (DLC), to perform ground start, loop start and polarity check tests to assure the electronic card in the DLC is operational and optioned correctly. These operational tests require dial tone to minimize trouble reports immediately following test and turn up. If the NC/NCI codes are such that the circuits do not require Dial Tone, Qwest does not require Dial Tone to be present at the CLEC’s CFA.

Qwest is preparing to no longer require the CLEC to provide Dial Tone on new Unbundled Loops (LSR ACT = N) in mid-October and will follow all appropriate CMP timelines. Prior to new Unbundled Loop Basic or Coordinated Hot Cuts, the Qwest Technician will conduct performance testing to assure the new Unbundled Loop complies with its respective NC/NCI standards.

(Part 2, 90 minutes) Perhaps the CLEC request reflects a misunderstanding. Qwest believes that the process in place more than meets the needs of the CLECs. The Basic Option allows Qwest to start the installation or hot cut any time between 8AM and 5PM regional time. Qwest actually allows more than 90 minutes when a Basic Installation is ordered.

Here is the procedure when the Basic Installation Option is ordered:

On Due Date when Qwest is finished doing the installation and core tests, we call to notify the CLEC that we are done and that the test has been completed. If the CLEC wants to do more testing on their own or they can't get something working on their end, Qwest waits 30 minutes, then calls the CLEC again. If the CLEC still isn’t ready Qwest lets the field tech and the Central Office Technician (COT) go to their next jobs.

Qwest will hold the order open and if we do not have a CLEC resolution by the end of day we will have the COT disable the circuit. If the CLEC calls back on the same day and is ready, we will try to get a tech back out (if applicable) and the COT back in the central office. If it is too late in the day, or the resources are not available, Qwest will jeopardize the order and the CLEC must supplement the LSR with a new desired due date.

If the order has multiple loops the CLEC should accept the loops that have Dial Tone and supplement the LSR to remove the loop that does not have Dial Tone. The loop without Dial Tone should be put on a separate LSR with a new desired due date.

In mid-October, on a New order the Outside Technician (OST) will check for dial tone. If the OST does not have dial tone they will: - Call the Central Office and have the COT check for dial tone. If dial tone exists, the OST needs to check the facilities and resolve. - If no dial tone exists, the COT needs to check for dial tone at the Connecting Facility Assignment (CFA). If dial tone exists at the CFA, the COT needs to check the wiring in the CO and resolve. - If dial tone does not exist, the COT will notify the OST and the COT will wire in temporary Qwest dial tone for the OST to perform core tests to complete the order. The QCCC Coordinator / Implementor will not need to notify the CLEC.

Sincerely,

Linda Hendricks Lead Project Analyst Qwest

Cc: Mary Retka, Mary Pat Cheshier, Diane Diebel

Open Product/Process CR PC120301-6 Detail

Description Of Change

Here is the industry documentation from the ASOG for two-six code assignment:

53 TSC - Two Six Code

Identifies a code assigned to a trunk group or a CCS link

Set.

NOTE 1: The code set is unique to each established

trunk group or CCS Link Set and is provided to the

customer on the Firm Order Confirmation or Design and

Order Confirmation. The TSC entry may then be

populated by the customer when ordering changes,

additions or deletions to an existing trunk group or CCS

Link Set.

Clearly Qwest is not in compliance with inventorying the two-six code, as the ASOG specifically states the two-six code is provided to the customer on the FOC. In the case where Qwest initiates ASRs, Qwest is the customer and AT&T is the supplier. Consequently, Qwest should be inventorying the two-six code provided by AT&T to Qwest on the FOC.

Expected Deliverables:

AT&T expects that Qwest will comply with industry guidelines and change process to begin to inventory the two-six code that AT&T assigns to Qwest-initiated ASRs.

Status History

Project Meetings

11/20/02 November CMP Meeting Qwest (Thomte) indicated that the trial orders that were established to convert the embedded base trunk groups in Wyoming were successful. The result is that both new trunks and embedded trunk groups appear to process through the systems using the AT&T Two Six code of CC. Qwest recommended that this CR move to CLEC Test and potentially be completed in December.

10/16/02 October CMP Meeting Qwest (Thomte) indicated that the trial was continuing and that two trial groups that are due to complete in early November. This CR to remain in “Develoment”.

08/21/02 - August CMP Meeting Qwest (Thomte) indicated progress had been made on this CR. Back end systems and reporting capability should be capable of accepting non Qwest two six code during September. Qwest and AT&T anticipate having a status meeting in late August. AT&T (Van Meter) concurred with the read out. This CR will remain in "Development" status

02/19/02 E-mail from AT&T with some questions about Qwest's response

Subject: RE: Qwest Response to Change Request PC120301-6 "Two-Six Code Inv entory for Local Interconnection Trunk Groups Ordered by Qwest" Date: Tue, 19 Feb 2002 17:20:24 -0600 From: "Stryczek, Kathleen K (Kathy), BNSVC" To: Michael Keegan CC: "Olsen, Linda Kae" , "Martin, Richard" , "Mead, Todd" , "Adkisson, Ann B, NCAM" , "Feinstein, Philip G (Phil), NNCER" , "Scherer, Esther A, NCAM" Michael, Thank you for your response to request PC120301-6 for Qwest to inventory the two-six code provided by AT&T on local interconnection trunk groups ordered by Qwest. If Qwest used the two-six code as the PON, would AT&T be able to report trouble tickets using the AT&T assigned two-six code? Also, would the Qwest maintenance group be able to locate a trunk group by searching for a PON which would have the two-six code embedded? If Qwest uses the AT&T two-six code only in the PON, but not in other systems, then I am concerned that Qwest may not be able to find the two-six code and associated trunk group when AT&T is reporting a trouble involving trunk groups ordered by Qwest. Kathy Stryczek AT&T 602-277-4527

Clarification Call, December 11, 2001, 11:00 am (MDT)

Attendees: Todd Mead, Qwest Linda Kae Olsen, Qwest Peggy Kilgus, Qwest Ann Adkinisson, AT&T Kathy Stryczek, AT&T Ester Shearer, AT&T

Reviewed description of Change Request.

Products impacted: Local Interconnection Service (LIS) Qwest need to have someone from the repair group who is involved in the management and use of the TIRKS system, involved in preparing the response to this CR. AT&T's expectation: AT&T would like Qwest to use the two-six code provided by AT&T when Qwest places an order for a local trunk group.

Action Plan: - Qwest will evaluate various options. This CR will be clarified with the CLEC Community at the January CMP Meeting. Qwest will provide a draft response for discussion at the February 2002 CMP meeting. - AT&T will provide Qwest with a contact in Ameritech to discuss ordering process and use of two-six codes. - Qwest to identify and involve the appropriate repair/TIRKS person to assist Linda in developing the draft response. An internal meeting will be held by next Wednesday (12/19/01)

CenturyLink Response

September 6, 2002

Kathy Stryczek AT&T

Subject: PC120301-6 Two-Six Code Inventory for Local Interconnection Trunk Groups Ordered By Qwest

This is a revised Qwest response to AT&T’s request, that Qwest comply with industry guidelines and change process to begin to inventory the two-six code that AT&T assigns to Qwest-initiated ASRs.

Qwest accepts AT&T’s request regarding complying with industry guidelines and inventory the two six code that is provided to Qwest on the FOC.

Qwest has worked in conjunction with AT&T to provide a trial request that will flow through the various systems and reporting processes. Qwest is currently making the appropriate modifications to support the request for AT&T.

Currently Qwest has one order that is in a trial process. AT&T has advised that they have additional orders expected in the near future. Qwest expects to address AT&T’s additional orders with the revised process.

Sincerely, Qwest

REVISED RESPONSE

September 6, 2002

Kathy Stryczek AT&T

Subject: PC120301-6 Two-Six Code Inventory for Local Interconnection Trunk Groups Ordered By Qwest

This is a revised Qwest response to AT&T’s request, that Qwest comply with industry guidelines and change process to begin to inventory the two-six code that AT&T assigns to Qwest-initiated ASRs.

Qwest accepts AT&T’s request regarding complying with industry guidelines and inventory the two six code that is provided to Qwest on the FOC.

Qwest has worked in conjunction with AT&T to provide a trial request that will flow through the various systems and reporting processes. Qwest is currently making the appropriate modifications to support the request for AT&T.

Currently Qwest has one order that is in a trial process. AT&T has advised that they have additional orders expected in the near future. Qwest expects to address AT&T’s additional orders with the revised process.

Sincerely, Qwest

REVISED RESPONSE

April 10, 2002

Ms. Kathy Stryczek Manager AT&T

SUBJECT: Qwest’s Change Request Response - CR # PC120301-6 Two-Six Code Inventory for Local Interconnection Trunk Groups Ordered by Qwest

This letter is a follow-up response to AT&T Change Request PC120301-6, requesting Qwest inventory the two-six code that AT&T assigns for Qwest initiated ASRs.

Qwest’s written response dated February 12, 2002 informed the CLEC community that Qwest was willing to perform a detailed economic and technical investigation to evaluate the feasibility of implementing the system changes required to meet the intent of this CR.

Qwest has completed its evaluation and has concluded the cost of changing the myriad of downstream-related systems needed to effect this change is prohibitive. Qwest suggests deferral of this CR until the 2003 fiscal year funding review, planned for later this year.

Therefore Qwest regretfully informs AT&T that this CR cannot be processed this year.

Sincerely,

Susan Bliss Director Process Management Qwest

FORMAL RESPONSE

February 12, 2002

AT&T Ms. Kathy Stryczek Manager

SUBJECT: Qwest’s Change Request Response - CR PC120301-6 Two-Six Code Inventory for Local Interconnection Trunk Groups Ordered by Qwest

This letter is in response to AT&T Change Request PC120301-6, Two-Six Code Inventory For Local Interconnection Trunk Groups Ordered By Qwest. AT&T has requested that Qwest inventory the two-six code that AT&T assigns for Qwest initiated ASRs.

During the CLEC Community clarification meeting held January 16, 2002, AT&T confirmed their desire for Qwest to inventory the TSC provided on the FOC for the order. AT&T agreed that this TSC, along with the TCICs and ACTL information provided today, could be provided during the up-front planning meeting for new markets. Qwest could then use this code as the PON number as well as possibly make program modifications that would allow it to be used as the TSC (TGAC) in the processing and inventory systems used by Qwest (EXACT, IABS, TIRKS, WFA, TRDB, etc.)

Qwest is willing to pursue internal system changes to evaluate the feasibility (technical and economical) of implementing such changes. Qwest can not determine all of the systems that would be impacted, nor what the downstream effects on the process would be until the systems evaluations are performed.

If this approach is acceptable to AT&T, Qwest will initiate the required internal system changes and provide a status update at the March CMP meeting.

Sincerely,

Linda Kae Olsen Process Specialist - LIS Qwest

Open Product/Process CR pc081904-1 Detail

Description Of Change

Expected deliverable: Revised Process ATT desires the capability to re-MLT at during open referral time.

Status History

Project Meetings

Clarification Call PC081904-1 MLT a TN during the open referral time

Attendance: Joyce Atwell – ATT John Wright – ATT Justin Sewell - Qwest Communications Jim Recker - Qwest Communications Cindy Macy - Qwest Communications

Cindy Macy - Qwest Communications opened the call and reviewed the agenda. Cindy explained that Qwest has met internally on this CR before the Clarification Call and we believe that we already provide the functionality that ATT is requesting.

Joyce Atwell introduced John Wright and explained that he is the requestor of this functionality. John explained that ATT is blocking the ability to perform MLT with Qwest so he is not aware if this feature works or not. John will work with his lab organization to remove the restriction and then test the feature.

Justin advised that Qwest added this feature in the 2001 time frame. John advised that ATT wanted to make sure that Qwest is aware that ATT will begin using this feature. Justin advised it is okay to begin using the feature. ATT believes it will reduce the number of Qwest dispatches.

John advised it will take several weeks for ATT to remove the feature. The team agreed that this CR will be withdrawn at the September CMP meeting. After ATT removes the feature they will test the functionality. If they have any trouble at that time they would contact the Help Desk to report a trouble report. If ATT determines they need to issue another CR they will do that at a later date.

Open Product/Process CR PC102601-1 Detail

Description Of Change

Status History

Project Meetings

CenturyLink Response

December 28, 2001

Carla Dickinson Pardee LSAM Manager AT&T

This letter is in response to the CLEC Change Request Form #PC102601-1 regarding RSID/ZCID Assignment for UNE-P. Qwest would like to close this Product/Process CR and open a new Systems CR to properly consider the best way of meeting this business need.

Today, the assignment of an RSID/ZCID value drives a lot of business processes in Qwest. USOC rates are maintained for each RSID/ZCID, Loss/Completion reports are generated for each RSID/ZCID, separate bills are generated, security and authorizations are specific per RSID/ZCID, etc. To assign multiple RSID/ZCID values per CLEC would create potential issues with contract updates, authorizations, etc. Qwest would prefer to create another mechanism for CLECs to tell Qwest how to segment customers for purposes of Loss/Completion reports, Daily Usage Feeds and any other system interfaces CLECs desire to have segmented.

This new separation mechanism would need to be accomodated on the LSR and IMA, as well as the other systems involved. A Systems CR would be required to accomplish this. Qwest will open the Systems CR on AT&T’s behalf.

If you have any questions, feel free to e-mail me or call me. Happy New Year!

Sincerely,

Alan Zimmerman (303)896-8346 azimmer@qwest.com

Open Product/Process CR PC020802-1 Detail

Description Of Change

Modification:

Revised Category reference from "013" to "011"

Status History

Project Meetings

AT&T agreed to close this Change Request

Subject: Clarification Response to Questions from 4/26/02 CLEC Conference Call Date: Tue, 25 Jun 2002 09:06:57 -0600 From: Richard Martin Organization: Qwest Communications International, Inc. To: Kathy Stichter , wdmarkert CC: Alan Zimmerman , "Pardee, Carla"

Kathy/Bill,

Based on our conference call, Monday June 17, 2002, the following clarifications were made to the previous questions asked and anwered from our 4/26/02 CLEC Conference Call to review System Fixes Implemented Pursuant to Third Party Tests on DUF Transmission:

Meeting Minute item 3.2 - The original question had to do with why access records appear on the DUF with zero's in the CIC. The original answer discussed Feature Group A usage. There is one more circumstance when an access record would show a CIC of zero's. That has to do with 110125 records in the Central region when Qwest is the underlying provider of the 8XX service.

Those records currently go out with a zero CIC as well.

Meeting Minute item 3.3 - It was confirmed that Eschelon will be getting two separate files for Meet Point Billing and DUF. The type of file and mehtod of transmission will depend on the agreements made between Eschelon and Qwest.

To: wdmarkert@eschelon.com, Richard H Martin/Mass/USWEST/US@USWEST cc:

Subject: 0000's in the CIC

Hello; Yesterday I mentioned that I thought that the issue of CICs being 0000 in the 110125 access records was limited to the Central region. I have since confirmed that this is correct. Central is the only region where this occurs. As discussed in our call yesterday, this is usage that was carried by Qwest, so we would be the billable carrier. This should be the only FG-D usage you see with 0000 in the CIC field.

Have a good day!

Alan Zimmerman Qwest Wholesale Billing Manager (303)896-8346

--

CLEC Conference Call

April 26, 2002 10:00 am (MDT) Conference Call TEL: 877-564-8688 CODE: 8973036 System Fixes Implemented Pursuant to Third Party Tests on DUF Transmission (Product/Process CR PC020802-1)

Attendees: Ric Martin, Qwest Wendy Thurnau, Qwest Brad Wickes, Qwest Alan Zimmerman, Qwest Carla Pardee, AT&T Jonathan Spangler, AT&T Kathy Stichter, Eschelon Bill Markert, Eschelon Jack Mungia, Eschelon Deb Hoffman, US Link

Introduction of Attendees Introduction of the participants on the Conference Call was made. Ric Martin explained that the call was a result of an Action Item from March’s CMP Monthly Meeting under Change Request PC020802-1. Details on the CR can be viewed in the CLEC Change Request – Product/Process Interactive Report located at the following URL: http://www.qwest.com/wholesale/cmp/changerequest.html This call will discuss the system fixes that were implemented by Qwest to become compliant with third party tests on the transmission of DUF Records and provide an update on the Central Regions compliance. Ric Martin requested that all CLEC participants send their e-mail address for receipt of meeting minutes.

Review of System Fixes Alan Zimmerman explained the 3rd Party Testing of the DUF conducted by KPMG Consulting and Cap Gemini, Ernst & Young (CGE&Y). The tests involved thousands of calls, and about 43 different call types. Both KPMG and CGE&Y have now concluded that Qwest’s DUF does adequately reflect usage made from Resale and UNE lines. To get to this successful conclusion, Qwest had to make several system changes, as detailed in KPMG’s Exceptions 3036, 3037, 3113 and 3098, as well as CGE&Y IWO 2129. Alan explained that these system changes are generally grouped into two categories: Pending Order File implementations and specific Local Measured Service issues, with a few additional fixes for specific other circumstances. Alan described the fixes and fix dates from those KPMG Exceptions, and answered questions from Eschelon and AT&T. The major fixes discussed included: Pending Order File Process --The pending order file (POF) Process was installed September 13th to more precisely handle usage made within a few days of customer conversion between local service providers. --The Western region had some inconsistencies in the way local measured service usage made on conversion day was handled. This was fixed Nov. 22. --8XX usage did not go to POF process in Western region until Nov 12. Central region had some specific circumstances where 8XX usage delayed in the POF process could be dropped. These circumstances were fixed November 20. --There were timing issues with POF processing in Central such that conversions done via a C order posted on a Thursday or Friday could have some of the usage released from POF for processing before all toll guides and databases were updated. This was fixed Feb. 7th. Local Measured Service (LMS) Records --Central & Eastern had problems that caused a very small percent of Local Measured Svc usage to error. These were fixed in December 2001. --Sent Paid LMS calls that were operator assisted were not properly sent on the DUF in the Western region. This was fixed Nov 22. --Central region LMS calls that originated from a UNE and billed to a resold line did not get a DUF record passed to the reseller until Dec 17. Additional Fixes --WATS attempts that originated from UNEs and did not complete did not have a DUF record generated for the Central region until Feb 18th. --Toll calls that intraLATA calls originated from a coin phone, were sent paid (not alternately billed), were carried by Qwest, and terminated to a UNE account did not have access records generated on the DUF until March 28th. --The Eastern region had a problem that resulted in duplicate records being generated to the DUF when an operator handled LMS call was made. This duplicate record condition was fixed 2/04.

Questions Raised During Discussion AT&T asked what products were covered and Qwest confirmed UNE-P and Resale. Eschelon asked what 0 meant and Qwest replied that if it comes from Qwest and it is a 0, bill Qwest. Qwest was requested to advise what condition access calls show up with a kick of 5123 versus 0 in all 3 regions. Eschelon asked what the meet point billing is on the same DUF. Qwest to provide response.

Closing Ric Martin advised that meeting minutes would be issued to the CLEC participants for review before posting to the CLEC community. Also responses to the Qwest action items would be issued to the all CLEC participants.

Subject: FW: CR PC020802-1 - Clarification Date: Thu, 14 Mar 2002 12:00:18 -0500 From: "Pardee, Carla D, NCAM" To: CC: "Hayes, Robert W (Bob), NCAM"

Ric:

AT&T has been discussing this CR (asking for correct and accurate transmission of DUF records) internally. AT&T would like to know the scope of the problem that was fixed. Did this fix correct only billing systems for UNE-P, or did this DUf transmission problem extend to meet point billing records as well? Does this fix have anything to do with the recent notification about the UNE-P records credits? We would like to set up another meeting to discuss this, or, if it is appropriate to discuss it in the CMP meeting next week, we are amenable to that as well. Let me know what works best for you. Thank you.

ps - I don't have Allan Zimmerman's correct e-mail address, if you wouldn't mind forwarding this to him also. Thank you.

Carla Dickinson Pardee Manager - LSAM (303) 298-6101

Revised (2/24/02) CLEC Change Request Clarification Meeting

2:30 p.m. (MDT) / Friday February 15, 2002 Conference Call TEL: 877-564-8688 CODE: 8973036 PC020802-1, Correct and Accurate Transmission of ADUF, DUF Records

Attendees: Carla Pardee, AT&T Richard Martin, Qwest Lynn Stecklein, Qwest Peggy Esquibel-Reed, Qwest Alan Zimmerman, Qwest Mark Pomeroy, Qwest Doug Warren, Qwest

Introduction of Attendees Introduction of the participants on the Conference Call were made and the purpose of the call discussed

Review Requested (Description of) Change Carla advised that the 013 DUF was to transmit Access records. She indicated that the ADUF records were not being transmitted correctly for UNE-P. She indicated that AT&T didn’t believe they were getting all DUF records and subsequently couldn’t bill their IXCs. Carla indicated that she thought that this was something the ROC was monitoring. Alan advised that the test were in the 3036 ROC Test. Alan further stated that the tests indicated that the Eastern and Western regions were 100% compliant. He indicated that the Central region is having issues with access of records received within a couple of days from a Change Order. Carla asked if there was any documentation on this. Alan advised that the documentation is on the WEB under Exception 3036. Alan explained that there is no Category 013, it is 011 for UNEs. Ric explained that there was a Systems Change to split the ADUF and ODUF records

Confirm Areas & Products Impacted It was confirmed that AT&T was interested in the product covered under Cat 011, which is Switched Access. . Confirm Right Personnel Involved It was confirmed that this is a Product/Process CR and Alan Zimmerman is the appropriate SME.

Identify/Confirm CLEC’s Expectation It was confirmed that AT&T wants confirmation that the Central Region is in compliance with providing 100% of the records.

Identify any Dependent Systems Change Requests It was confirmed that there is a System CR to break out Category 010 from 011.

Establish Action Plan (Resolution Time Frame) Qwest will report back on Central compliance progress by March’s CMP meeting

CenturyLink Response

Carla Pardee LSAM Manager AT&T

SUBJECT: Qwest’s Change Request Response - CR #PC020802-1 Correct and Accurate Transmission of ADUF or Category 011 DUF Records

This letter is in response to AT&T’s Change Request PC020802-1 requesting accurate and correct transmission of access DUF records (category 011 or ADUF).

During the February 15, 2002 Clarification Meeting, Qwest advised that the 3036 ROC Tests indicated Qwest’s Western and Eastern Regions were 100% compliant with issuance of DUF records. Qwest’s Central Region was still under testing by KPMG.

On Wednesday, KPMG officially closed the last issues associated with the DUF test for the 13 state ROC test area. These last issues had to do with correct population of Indicator 4 and the matches of calls made to DUF records passed in the Central region. KPMG found no records with incorrect Indicator 4 values, and found about 96% of the calls expected on the DUF. KPMG has now sent us the calls that comprise the four- percent of expected calls that KPMG did not find. Qwest will investigate these messages to see if any problems are found. Historically, however, there have been several percent of KPMG's expected calls that did not generate AMA records, did not complete a billable call, did not in fact belong to a wholesale account, or were passed on the DUF but were missed by KPMG. So Qwest expects to be able to explain essentially all the KPMG calls with these valid reasons. That analysis has just begun.

Qwest will provide the results of the analysis when they become available.

Sincerely,

Alan Zimmerman (303)896-8346 azimmer@qwest.com

Cc: Susan Burson

Open Product/Process CR PC110702-1 Detail

Description Of Change

Expected Deliverable

Notifications/mailouts list the precise rates effected.

Status History

Project Meetings

01/15/03 January CMP Meeting Barb Cornwell with Qwest gave an update on this CR and said that a generic Exhibit A will be provided with the Arizona Phase II A cost docket. This CR will remain in Development status.

12/18/02 December CMP Meeting Barb Cornwell presented the Qwest draft response and said that starting with the next Cost Docket, Qwest will include an Exhibit A in the notification. The Exhibit A will include the rates that are changing and timeframe the rates will be changed. Individual contract rate sheets are available from Qwest service managers. Joan Matzler added that SGAT rate changes are also available on the web site. This CR will be moved to Development status. Stichter-Eschelon provided updates to the notes to include the following: Would any change in the SGAT rate because of a cost docket apply to Eschelon? And Qwest responded yes.

11/20/02 November CMP Meeting Carla Pardee with AT&T presented this CR and said that the rate change notifications that Qwest currently provides do not meet AT&T’s needs. Carla said that they would like to have the new rates included in the notifications. Mike Zulevic with Covad said this is something he requests from the Account Team. Once rates are effective, Covad wants to understand the impact prior to implementation. Bonnie Johnson said that Eschelon has asked for rate changes many times and Kathy Stitcher added that previous change requests have been denied. A CR was denied in the May timeframe, because of the number of staff hours required. Sue Burson with Qwest said that she remembered the change request. Mike Zulevic said that Qwest might want to look at the dispute resolution process for billing and determine if providing the new rates is unduly burdensome. Judy Schultz with Qwest asked if AT&T was looking for rates associated with specific USOCs applying to AT&T. Carla Pardee said that last week they received notification about Arizona and the week before on Utah. They would like to know what the elements are, and what the new rate will be. With the Colorado UNE, we never received rates and it causes confusion, and the account team doesn’t always provide what is needed. Kathy Stitcher said that Eschelon submitted CR number PC053002-2X and it was denied because it was economically not feasible. Kathy said that on Arizona they did contact their service manager and also received a spreadsheet for Utah with some items missing. It was agreed this CR would move to clarification status.

- CLEC Change Request Clarification Meeting

November 14, 2002, 2:30 p.m. (MT) Conference Call 1-877-554-8688 PIN 1930099 # PC110702-1 Request that rate change notifications/mailouts contain rates effected. Introduction of the participants on the Conference Call was made and the purpose of the call discussed. Attendees Carla Pardee, AT&T Sue Kriebel, Qwest Barb Cornwell, Qwest Laurel Neher, Qwest Cliff Dinwiddie, Qwest Cindy Pierson, Qwest Dana Nielsen, Qwest Linda Sanchez-Steinke, Qwest

1 Introduction of Attendees Introduction of the participants on the Conference Call was made and the purpose of the call discussed.

2. Review Requested (Description of) Change The description of change requested in the CR was reviewed. Carla indicated that AT&T receives the mailouts when there is a Commission order or Cost Docket for rate changes and they would like to review the rates in a more efficient way and would like ability to compare the old rates to the new rates. Laurel Neher with Qwest asked if this would apply to Exhibit A SGATs. Carla said that most would be applicable and the Utah Order is what prompted the CR and it would be helpful to compare the new rates that were effective and be able to distribute throughout AT&T. Cindy Pierson with Qwest said that today on the Qwest web site Utah 10/16/02 is available in Exhibit A in the SGAT. Carla asked if there is a footnote that references the commission order and Cindy said that the note section lists the dockets approved in. Barb Cornwell with Qwest said that when the notice is received that if interested in AT&T specific rate sheets, an electronic copy of the rate sheet can be sent by the Service Manager. Barb also said that a notification for Arizona would be received today by AT&T. Carla will contact her Service manager and get with the AT&T people who requested the CR to provide information on the web site information available.

3. Confirm Areas & Products Impacted Carla indicated that all products are impacted.

4. Confirm Right Personnel Involved Qwest confirmed that the right personnel were involved in the conference call.

5. Identify/Confirm CLEC’s Expectation Carla confirmed that AT&T is interested in comparing the old rates to the new rates and that they are interested in AT&T specific rates.

6. Establish Action Plan (Resolution Time Frame) This CR will be walked on by Carla at the November CMP Meeting.

CenturyLink Response

Carla Dickinson Pardee ILEC Relations Manager AT&T

SUBJECT: Qwest’s Change Request Response - CR PC110702-1 Request rate change notifications/mailouts contain rates effected.

As a follow up to the December 18, 2002 CMP Meeting, Qwest will enhance the current process to additionally provide an Exhibit "A" rate sheet customized to specifically reflect only the rates Ordered in the Docket. This document will be attached as a communication piece with the rate change notifications/mailouts for CLEC distribution and reference.

Qwest plans to have this solution coordinated and operational to coincide with the implementation of the Arizona Cost Docket Phase IIA. Notification of the Arizona rate change is expected on or about January 15, 2003. Level 1 Process Change, PROS.12.26.02.F.00973.CRRateChange, was sent on December 26, 2002.

Sincerely,

Barb Cornwell Senior Process Analyst Qwest

December 3, 2002

DRAFT RESPONSE For Review by CLEC Community and Discussion at December’s CMP Meeting

Carla Dickinson Pardee ILEC Relations Manager AT&T

SUBJECT:Qwest’s Change Request Response - CR PC110702-1 Request rate change notifications/mailouts contain rates effected.

Currently, Qwest notifications/mailouts advising of a rate change do not identify the affected rates. The purpose of the notification is to advise the CLEC of the pending implementation of a rate change as Ordered by a Public Utilities Commission. Qwest’s standard operating procedure is to ensure Interconnect Contract Agreements are updated with the Ordered rates are available to CLECs during the implementation process.

In response to this request, Qwest will enhance the current process to additionally provide an Exhibit "A" rate sheet customized to specifically reflect only the rates Ordered in the Docket. This document will be attached as a communication piece with the rate change notifications/mailouts for CLEC distribution and reference.

Qwest plans to have this solution coordinated and operational to coincide with the implementation of the New Mexico Cost Docket. Notification of the New Mexico rate change is expected on or about January 15, 2003.

Sincerely,

Barb Cornwell Senior Process Analyst Qwest

Open Product/Process CR PC040501-1 Detail

Description Of Change

Status History

Project Meetings

Open Product/Process CR PC102802-1 Detail

Description Of Change

- Pre-ordering (http://www.qwest.com/wholesale/clecs/preordering.html),

- LOA/POA (http://www.qwest.com/wholesale/preorder/index.html), and

- the IMA User’s guide (http://www.qwest.com/wholesale/downloads/2002/020916/ugpreorder_101_091302.pdf).

The Pre-Ordering website states "Before initiating activity, obtaining a CSR and placing orders on behalf of an end-user, you are required to have a Letter of Authorization or Proof of Authorization giving you authorization to do activity on their behalf." In a separate paragraph, the website provides "While it is not necessary for the LOA to accompany your request, the indication of authorization is required when you request a CSR for an account owned by Qwest or another CLEC." The initial reference to “Letter of Authorization or Proof of Authorization” by itself is fine, but the later reference only to "LOA" suggests written approval from the customer is required for access to the CSR. This is not the case. AT&T understands that customer authorization is required, but a written authorization is not. See 47 CFR Section 64.2007(b). This section of the federal rules identifies the methods by which a carrier may obtain customer approval to access CPNI. It states that "A telecommunications carrier may obtain approval through written, oral or electronic methods." State requirements in the Qwest territory largely mirror the federal rules.

The LOA/POA document states "Prior to obtaining records or placing orders for an end-user you must obtain permission from the end-user to act on their behalf in matters pertaining to the communications services." The following paragraph states "Proof of authorization can be arranged through a Letter of Agency" -- indicating there are options for obtaining authorizations from the customer. The third option cited is "oral authorization verified by an independent third party (with third party verification as POA)." Third party verification is necessary for a transfer of service, but is not required just to view a CSR. The website further states "While the Letter of Agency need not accompany your request for records or services, the indication of agency authorization is a required field entry when you request customer service records or submit Local and Access Service Request forms." As written, this language seems to require a written letter of authorization from the customer in order to view customer records. This is not consistent with the federal and state rules referenced above.

In the IMA user’s guide, "Reviewing Customer Service Records", 10.01 page 1-18 also provides that "Proof that a CLEC has received a Letter of Authorization (LOA) is required if the CLEC attempts to retrieve a CSR for a customer account owned by Qwest or another CLEC". Once again, this language suggests that a written letter of authorization is required. It is not.

While AT&T understands it is necessary to obtain customer consent prior to reviewing CSRs, it is not necessary to obtain written consent or third party verification of oral consent. Qwest does not have the authority through its PCAT, or otherwise, to demand more of CLECs than applicable law requires. AT&T would like to believe that the Qwest language referenced in this CR is simply inadvertent and does not represent Qwest’s intent to require more of CLECs than applicable law requires. However, AT&T does find this documentation troubling and believes that it is important that Qwest clean up its documentation to reflect what is required by applicable law. Please make these corrections and clarifications as soon as possible to avoid further confusion among Qwest’s CLEC customers. Suggestions AT&T would offer include: (i) do not use LOA interchangeably with other forms of authorization that may be obtained; and (ii) simply refer to applicable law in the places where the requirement for authorization needs to be referenced.

Expected Deliverable

AT&T expects Qwest to provide uniform instructions, in accordance with applicable law, within 60 days of submission of this CR.

Status History

Project Meetings

02/19/03 February CMP Meeting This CR is in development status and Donna Osborne-Miller with AT&T said that Qwest will incorporate the PCAT changes requested, the submitted comments, and they would like to leave the CR open another month. This CR will remain in development status.

01/15/03 January CMP Meeting Michelle Thacker with Qwest gave an update on this CR. Documentation for IMA will be effective 1/21/03 with IMA release 11.01. PCAT documentation is targeted to be available in late January. LSOG documentation and Preparation Guide will be available with the 12.0 IMA release in April. This CR will stay in Development status.

12/18/02 December CMP Meeting Linda Sanchez-Steinke with Qwest presented the draft response to this CR and said that CLEC facing documentation and the IMA User’s Guide will be updated. AT&T agreed with the Qwest response and Liz Balvin with Worldcom asked if there would be updates to the Preparation Guide. Qwest will e-mail an answer to Liz Balvin’s question and include in meeting minutes. This CR will be moved to Development status.

11/20/02 November CMP Meeting Carla Pardee with AT&T presented this CR and said that three of the Qwest pre-ordering web sites have different requirements ranging from oral to written approval prior to CLECs reviewing the customer service record. AT&T Legal interpretation is that only oral approval from customers is required prior to reviewing the CSR. Qwest will present the draft response at the December CMP Meeting.

CLEC Change Request Clarification Meeting

November 5, 2002, 3:00 p.m. (MT) Conference Call 1-877-554-8688 PIN 1930099 # PC102802-1 Correction/clarification of Qwest documentation (PCAT, IMA User’s Guide, etc.) describing customer authorization requirements for retrieval of CSR’s.

Carla Pardee, AT&T Mike Johnson, Qwest Sharon King, Qwest Cap Hamilton, Qwest Beth King, Qwest Michelle Thacker, Qwest Linda Sanchez-Steinke, Qwest

Introduction of the participants on the Conference Call was made and the purpose of the call discussed.

Review Requested (Description of) Change The description of change requested in the CR was reviewed. Carla indicated that AT&T is asking that there be consistency in all Qwest documentation associated with the review of customer service records (CSRs). AT&T Legal interprets the wording in the following Qwest websites to be inaccurate according to federal rules, 47 CFR Section 64.2007(b) - Pre-ordering (http://www.qwest.com/wholesale/clecs/preordering.html), - LOA/POA (http://www.qwest.com/wholesale/preorder/index.html), and - the IMA User’s guide (http://www.qwest.com/wholesale/downloads/2002/020916/ugpreorder101091302.pdf) AT&T’s interpretation is that approval to view the customer service record (CSR) can be in written, oral or electronic format.

Confirm Areas & Products Impacted Carla indicated that all products are impacted.

Confirm Right Personnel Involved Qwest confirmed that the right personnel were involved in the conference call.

Identify/Confirm CLEC’s Expectation Carla confirmed that AT&T is not disputing oral approval from customer to review CSR. The documentation wording sounds like the CLECs have to get written permission from customers to view their CSR and AT&T is asking that Qwest documentation be revised.

Establish Action Plan (Resolution Time Frame) This CR will be presented by Carla at the November CMP Meeting.

CenturyLink Response

Carla Pardee LSAM Manager AT&T

SUBJECT:Qwest’s Change Request Response - CR # PC102802-1 (Correction/clarification of Qwest documentation (PCAT, IMA User’s Guide, etc.) describing customer authorization requirements for retrieval of CSRs.)

This is in response to AT&T’s Change Request CR PC102802-1. This CR requests that Qwest clarify and correct as needed Qwest documentation (PCAT, IMA User’s Guide, etc.) that describes customer authorization requirements for retrieval of CSRs.

Qwest accepts this CR and will review and clarify CLEC facing documents pertaining or referencing customer authorization requirements.

The IMA User Guide 11.01, is targeted for review in late December and Qwest External Documentation is targeted for review in late January.

Sincerely,

Michelle Thacker Process Specialist Qwest

Open Product/Process CR PC120803-1 Detail

Description Of Change

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 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 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 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 period of time. When Qwest works the T order and the technician determines 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 electronic/mechanical means of associating the T order to the F order. Some scenarios are:

1) customer has X number of TN's and is moving within a building and retaining the same TN's.

2) customer has X number of TN's is moving to another building within the same rate center and retaining the same TN's.

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.

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.

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 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 prevent taking the customer out of service.

Revised Expected Deliverable (02-03-04):

That no customer would be taken out of service on any move order.

Original Description of Change (12-08-03):

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 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 service is not interrupted. When Qwest works the T order and the technician determines that the order cannot be completed as expected (either 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 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 in error.

Original Expected Deliverable (12-08-03):

Expected Deliverable: Processes be changed to associate all T&F orders to each other. That systems be 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 order is stopped. Expected result will 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 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 immediately re-instate the service in an effort to prevent an out of service condition .

Status History

Project Meetings

06/16/04 June CMP Meeting Linda Sanchez-Steinke with Qwest said the PCAT update was effective on 6/4/04. This CR will move to CLEC Test status.

05/19/04 May CMP Meeting Qiana Davis with Qwest said there was one comment received on the Pre-ordering PCAT. Qwest will provide a response back today. The proposed effective date is 6/4/04. This CR will remain in Development status.

04/21/04 April CMP Meeting Qiana Davis with Qwest said there will be level 3 changes made to the Pre-ordering PCAT that will include the interim manual process and the can be reached number. Tomorrow at the Systems meeting the CR for the systems solution will be presented. Bonnie Johnson with Eschelon said she was really excited that the changes were being made because recently Eschelon had a customer move and the customer was out of service for an entire day. Donna Osborne-Miller with AT&T said that she will alert Ervin Rea that the PCAT will be coming out soon and to make any comments. This CR will move to Development status.

03/17/04 March CMP Meeting Qiana Davis with Qwest said the T & F process is used for both Retail and Wholesale orders. In researching the T & F process, Qwest has initiated an MCC because in rare instances, technicians were not adhering to the process of calling the customer to find out the disposition of the F order when the T order is held. Qwest is updating the PCAT process for the can be reached number because sometimes the number forwards to voice mail. In addition, Qwest will be sending a level 3 notification for a manual interim process allowing population of the FDT field. This interim process will allow the F order to be delayed if the T order will be held. Qwest will also submit a systems CR for the 17.0 release to mechanize the manual process. Bonnie Johnson with Eschelon asked what IMA changes need to be made. Qiana said the details are still being worked out and that the DFDT field edits will be lifted to allow a value to be input and that will be used to inform the technician to hold the F order. Bonnie asked if this would give the ability to communicate if the T order is held the F should be held. Qiana said the field is currently used for a time value and the edit will be lifted to indicate hold the F order. Bonnie asked what work is being done in the backend systems to force the holding of the F order. Qiana said the technician would be informed to hold the F order until a call is received and this will be an interim manual handling process. Bonnie asked Qiana to keep everyone updated of the progress. Ervin Rea with AT&T said he was surprised and glad that Qwest had found a way to associate the T & F orders, and asked if orders would no longer be disconnected at 12:01 a.m. Qiana said yes, if the order has the DFDT field populated it will allow the F order to be held. This CR will move to Development status.

- 02/18/04 February CMP Meeting 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 modifications and require additional time to respond to the CR. Qiana added that Qwest would provide an update in March. Carla Pardee with 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 also said they have been working with their service management team on this issue as well. Qwest will provide an update in March. This CR will be moved to Evaluation status.

CLEC Change Request Clarification Meeting

2:30 p.m. (MDT) / Friday February 6, 2004

1-877-572-8687 3393947# PC120803-1 Associated Move Orders

Name/Company: Ann Adkisson, AT&T Carla Pardee, AT&T Ervin Rea, AT&T Cheryl Peterson, AT&T David Belanger, AT&T Joyce Perry, AT&T Jim Recker, Qwest Mike Lanoue, Qwest Jerry Jenson, Qwest Qiana Davis, Qwest Pat Torkelson, Qwest Brenda DeFilippo, Qwest Doug Slominski, Qwest Lydell Peterson, Qwest Danelle Haynes, Qwest Linda Sanchez-Steinke, Qwest

Introduction of Attendees Qwest welcomed all attendees to the meeting.

Review Requested Change 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.

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 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 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 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 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 cannot be completed as expected (either jeopardized 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 scenarios are:

1) customer has X number of TN's and is moving within a building and retaining the same TN's.

2) customer has X number of TN's is moving to another building within the same rate center and retaining the same TN's.

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.

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.

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 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 prevent taking the customer out of service.

Expected Deliverable: That no customer would be taken out of service on any move order.

Ervin Rea with AT&T said that this CR was revised as a result of the CMP clarification meeting 1/28/04 and the CMP meeting 1/21/04. If Qwest 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 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 extended amount of time.

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 order is due the day after the due date of the T. The port within process http://www.qwest.com/wholesale/downloads/2003/030513/DNLDPortWithinProcess1005-13-03.doc

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 was not sure if a CR would be required for adherence of the process and would take the question back.

Ervin said that he would still want to have adherence to the process through Service Management. 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 process should say that there should not be a disconnect of the F location.

Confirm Areas & Products Impacted Primarily UNE-P and POTS Residence and Business. Other products include Resale, Unbundled Loops and any products T&F orders are issued for when there is a move and there is a jeopardy situation.

Confirm Right Personnel Involved Correct Qwest personnel were involved in the clarification meeting.

Identify/Confirm CLEC’s Expectation Expected Deliverable: That no customer would be taken out of service on any move order.

Identify any Dependent Systems Change Requests None identified.

Establish Action Plan This CR will be discussed at the February 18, 2004 CMP Meeting

Tue 2/3/04 11:46 AM From: Pardee, Carla D, NKLAM [cdickinson@att.com] To: Sanchez Steinke, Linda cc: Rea, Ervin E, NKLAM, Adkisson, Ann B, NKLAM, Perry, Joyce M, NKLAM, Peterson, Cheryl J, NKLAM, Peterson, Lydell Subject: Amended PC 120803-1 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 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 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-647-2234 if we need to discuss further. As usual, thanks for your assistance and help with this change request!

CLEC Change Request Clarification Meeting

8:30 a.m. (MDT) / Wednesday January 28, 2004

1-877-572-8687 3393947# PC120803-1 Associated Move Orders

Name/Company: Ann Adkisson, AT&T Carla Pardee, AT&T Irvin Rea, AT&T Sheryl Peterson, AT&T David Belanger, AT&T Joyce Perry, AT&T Jim Recker, Qwest Mike Lanoue, Qwest Jerry Jenson, Qwest Jeanette Barns, Qwest Qiana Davis, Qwest Kit Thomte, Qwest Pat Torkelson, Qwest Brenda DeFilippo, Qwest Linda Sanchez-Steinke, Qwest

Introduction of Attendees Qwest welcomed all attendees to the meeting.

Review Requested (Description of) Change 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 of this clarification meeting. 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 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 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 cannot be completed as expected (either 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 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 in error.

Expected Deliverable: Processes be changed to associate all T&F orders to each other. That systems be 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 order is stopped. Expected result will 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 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 immediately re-instate the service in an effort to prevent an out of service condition.

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 issue will be resolved. 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 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 be jeoped at the same time. Irvin clarified that AT&T doesn’t want the F order worked until the T order is completed.

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 phone numbers. 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.

Sheryl Peterson with AT&T asked her group if they really understand the process.

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 different central office, different telephone number Irvin said if the CLEC issues a move order, RORD has to be filled out by Qwest

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 yes. 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 Residence. David Belanger said that the business is not always still located at the old address and sometimes someone goes back to the old address to answer phones. Qiana asked if the T order is jeoped would remote call forwarding help the situation. Irvin answered that partial remote call forwarding and David added that the disconnect recording is played.

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 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 frame due time is not requested, the F will be worked shortly after midnight on the due date.

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 disconnect. 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 due. Brenda asked if same TN at different location. Jeanette Barns asked if the customer has vacated the location.

AT&T had further discussion on whether or not all the products with scenarios were captured in the CMP CR submitted; same TN, different TN, customer has already moved from location and intercept message.

As a result of this clarification meeting, AT&T will meet internally and determine what exact change they are requesting; and identify products and scenarios for this change request. AT&T will either submit revisions and scenarios to this change request or submit a new change request.

Confirm Areas & Products Impacted 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 jeopardy situation.

Confirm Right Personnel Involved Correct Qwest personnel were involved in the clarification meeting.

Identify/Confirm CLEC’s Expectation

Identify any Dependent Systems Change Requests None identified.

Establish Action Plan (Resolution Time Frame) AT&T will meet internally meet determine what revisions are needed to the current CR or submit a new CR.

01/21/04 January CMP Meeting 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. 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 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 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 can’t be working in both locations. Qiana said that Qwest does offer Dual Service.

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 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 question. Linda Sanchez-Steinke with Qwest said she did not understand that the question was related to the CR. Bonnie also said that Dual Service requires two different due dates (Begin comment from Bonnie Johnson – Eschelon) and that is not what we are asking for. Bonnie said 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 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” 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 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 services. Liz Balvin with MCI added that DFDT is desired, and is not guaranteed that disconnect will be completed at the desired time. Qiana asked AT&T to identify the products. Ervin said that the products are Resale, UNE-P, Unbundled Loops.

Qwest will arrange an additional clarification meeting for additional questions and the CR may need to be modified based on the clarification 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 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; 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 Presented status.

Wed 12/24/03 9:01 AM To: Sanchez Steinke, Linda From: Pardee, Carla D, NKLAM [cdickinson@att.com] cc: Rea, Ervin E, NKLAM Subject: RE: PC120803-1 Move Orders Associated 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 Orders." Thanks for taking care of this. Happy Holidays

From: Sanchez Steinke, Linda Sent: Tuesday, December 23, 2003 2:15 PM To: Pardee, Carla D, NKLAM Subject: PC120803-1 Move Orders Associated

Carla -

During the CMP meeting did AT&T agree to change the name of this CR to "Associated Move Orders" or something different than currently titled?

Would you let me know the title and I will change in the database.

Thank you

Linda Sanchez-Steinke CRPM Qwest 303-382-5768

Tue 12/16/03 9:24 AM From; Johnson, Bonnie J. [bjjohnson@eschelon.com] To: Sanchez Steinke, Linda cc: Subject; Question for AT&T CR

Linda, Here is my question: As it relates to a T&F order, excluding a jeopardy on the "T" order, does Qwest always keep the "F" side of the order (customers service at the old location) working until the "T" side is installed. I would like the answer for tech dispatch and flow through orders that do not require a dispatch.

It was always my understanding that the Qwest tech had the "F" order worked (switch) after he installed the new line at the prem Can you confirm and tell me how it works when there is no tech?

I am asking the question because I hear the CLECs continue to talk about their customers being impacted and out of service with moves even if a jeopardy condition does not exist. Perhaps we could address both issues if there is one.

Thanks!

Bonnie J. Johnson Director Carrier Relations Eschelon Telecom, Inc. Phone 612 436-6218 Fax 612 436-6318 Cell 612 743-6724 bjjohnson@eschelon.com

12/17/03 December CMP Meeting 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 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 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 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 as soon as possible to identify. Connie Winston will work with the business to see how systems are effected. CLEC Change Request Clarification Meeting

8:30 a.m. (MDT) / Monday December 15, 2003

1-877-572-8687 3393947# PC120803-1 Move Orders Associated

Name/Company: Ann Adkisson, AT&T Patty Garnier, AT&T Carla Pardee, AT&T Colleen Forbes, AT&T Kim Isaccs, Eschelon Bonnie Johnson, Eschelon P.J. Koller, Priority One Telecommunications Shon Higer, Qwest Linda Sanchez-Steinke, Qwest

Introduction of Attendees Qwest welcomed all attendees to the meeting.

Review Requested (Description of) Change Linda Sanchez-Steinke with Qwest read the description of change from the submitted change request; 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 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 service is not interrupted. When Qwest works the T order and the technician determines that the order cannot be completed as expected (either 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 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 in error.

Carla Pardee with AT&T & P.J. Koller with Priority One Telecommunications, discussed the products impacted would include; UNE-P, All POTS, Resale, Unbundled Loops and, any products where T&F orders are issued when there is a move and there is a jeopardy situation.

Bonnie Johnson with Eschelon had a question regarding jeopardy conditions, related to dispatch of technician on T & F orders. Bonnie will e-mail the question to Linda Sanchez-Steinke.

Confirm Areas & Products Impacted 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.

Confirm Right Personnel Involved Correct Qwest personnel were involved in the clarification meeting.

Identify/Confirm CLEC’s Expectation Linda Sanchez-Steinke read the Expected Deliverable; Processes be changed to associate all T&F orders to each other. That systems be 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 order is stopped. Expected result will 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 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 immediately re-instate the service in an effort to prevent an out of service condition.

Identify any Dependent Systems Change Requests Carla Pardee said there may be a systems change request and she would check on any systems change requests issued.

Establish Action Plan (Resolution Time Frame) AT&T will walk on this CR at the December CMP Meeting. Qwest will provide a response in February.

CenturyLink Response

DRAFT RESPONSE For Review by the CLEC Community and Discussion at the March 2004 CMP Meeting

Ann Adkisson AT&T

SUBJECT: Qwest’s Change Request Response - PC120803-1 Associated Move Orders

Description of request (partial): (Revised Description of Change 02-03-04) When a CLEC submits a move order (M) Qwest creates two orders, a (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 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 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 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 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 electronic/mechanical means of associating the T order to the F order.

Response: Qwest and CLECs acknowledge the long-standing process for outside moves is a two order process for all non-designed services (e.g., Resale and UNEP POTS) and some designed services (e.g., Unbundled Loops). For non-designed services, the association of the two 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" (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 Wholesale accounts and are an integral part of both Qwest systems and processes. To change these would require a complete redesign of multiple systems, internal processes/documentation and training at an extraneous cost to Qwest without real benefit. Instead, Qwest has reviewed and analyzed the existing process for outside moves and has summarized the processes and findings as follows.

T & F orders in the same central office with no change to the telephone numbers are automatically sequenced and the provisioning is coordinated 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, sequencing does not occur and the F order is worked on due date after 12:01 A. M.

There are two basic reasons for "jeopardizing" the T & F orders; Qwest reasons or Customer reasons. When an order is jeopardized for Qwest reasons (e.g., CF - Qwest Facilities are not available), the T order is delayed until Qwest facilities become available. At the point Qwest 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 to disconnect the existing service. Qwest makes every attempt to contact the customer of record to determine the disposition of the "F" order. If 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 customer of record is contacted.

The Designed service process generates various order types within Qwest and is dependent upon the product type. If a designed service order is jeopardized, Qwest will contact the customer to determine if the customer wants to continue forward with disconnect activity. The orders are critically related and are worked together.

Additionally, in response to Cheryl Peterson’s finding within the PortWithin process document (http://www.qwest.com/wholesale/downloads/2003/030513/DNLDPortWithinProcess1005-13-03.doc), which states "On a full conversion, Qwest 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 product process guide specifically for the DID product.

Findings: In reviewing/analyzing the processes and associated examples, Qwest determined: - Qwest technicians, on rare occasions, were not adhering to the process of contacting the customer of record a jeopardy situation. - the "can be reached" information provided by the CLEC does not provide the technician with a "live person" with whom the technician can work the issue of the pending disconnect.

Conclusion: Qwest accepts this CMP CR and has identified the following activities to enable closure: - 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 number which allows Qwest to contact the customer of record. - We have issued a Communicator to selected Network groups to reinforce the process of contacting the customer in jeopardy situations to determine the disposition of the F orders (disconnect). - Qwest currently offers specific optional services to the CLECs that may remedy some of the unique requirements of some move activities, e.g., 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 options. - Qwest will continue to review its current processes and seek opportunities for improvement.

Sincerely,

Qiana Davis - Sr. Process Analyst, Wholesale Service and Delivery Jim Recker - Staff Advocate, Qwest

February 6, 2004

DRAFT RESPONSE For Review by CLEC Community and Discussion at the February 2004 CMP Meeting

Ann Adkisson AT&T

SUBJECT: Qwest’s Change Request Response - PC120803-1 Associated Move Orders

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 each other but no action is taken when the T order is placed in jeopardy and the F order is not stopped".

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 decided to meet internally and amend the initial CMP CR to now include the exact change requested along with detailed scenarios.

On February 3, 2004, Qwest received the amended version of CMP CR PC-120803-1 and are currently evaluating the change request. Therefore, we require additional time to investigate and will provide a response at the March CMP meeting.

Sincerely,

Qiana M. Davis FTS Process Specialist

Open Product/Process CR PC042303-1 Detail

Description Of Change

Expected Deliverable:

ATT requests a similar process as described above. (MOU) This would include any system changes necessary by Qwest to be implemented to support this type of process. Implementation of this process/system change would allow both AT&T and QWEST to better manage situations requiring a coordinated dispatch, resulting in fewer "no access" or "vendor meet ,no show" and would reduce missed commitments for these reasons.

Status History

Project Meetings

September 17, 2003 CMP Meeting Craig Suellentrop – Qwest reported that an internal status meeting is scheduled for next week. The development is on track and estimated time frame is December 2003. Liz asked Craig to refresh her memory and Craig advised this is for the joint meet which has to be requested.

CMP Meeting 08-20-03

Suellentrop-Qwest stated that the CR should stay in development because there were a number of internal systems that had to move through the 90 day development cycle. Osborne-Miller-AT&T asked when she could expect delivery. Suellentrop-Qwest stated that he estimated implementation would come in December 2003.

=================================

CMP Meeting 07-16-03

Sullentrop-Qwest presented the Qwest acceptance. He stated that when Qwest developed the full solution it would follow the appropriate notification process. He stated that this might entail systems changes, but he wasn’t sure if they would be CLEC facing changes. Zimmerman-AT&T asked for Qwest’s tentative implementation date. Sullentrop-Qwest stated that he thought it would take at lease a couple of months. Osborne-Miller-AT&T asked if the systems changes would involve IMA. Suellentrop-Qwest stated that he didn’t think they would involve prioritized systems. He stated that he would have much more information at the August CMP Meeting. He stated that Qwest was looking at a 30 minute meeting window. Zimmerman-AT&T stated that was good. Suellentrop-Qwest stated that this new process would be available for systems other than electronic bonding. Johnson-Eschelon stated that Eschelon had submitted a CR in 2001 (PC092801-2) for the same thing and Qwest denied it. She asked why Qwest was accepting AT&T’s. White-Qwest stated that he would research the reason and correspond directly with Johnson.

=================================== CMP Meeting 06-18-03

Suellentrop-Qwest asked that the CR be moved into Evaluation status. Osborne-Miller-AT&T stated that AT&T would forward their contacts in the other ILECs to Qwest. ========================================================== CMP Meeting 05-21-03

Osborne Miller-AT&T presented the CR. Suellentrop-Qwest stated that UNE-P and resale products are affected by this. Stichter-Eschelon stated that she had opened a similar CR that was denied. Johnson-Eschelon asked if there should be a CMP process to review previously denied CRs. Osborne Miller-AT&T stated that Verizon, SBC and Bellsouth have all converted to a similar process after AT&T presented them with the data. Suellentrop-Qwest asked AT&T to send the appropriate data to White-Qwest. ========================================== Clarification Meeting Friday, May 09, 2003

1-877-550-8686 2213337#

Attendees Matt White – Qwest Craig Suellentrop – Qwest Anthony Washington – Qwest Donna Osborne-Miller – AT&T Craig Zimmerman – AT&T Lydia Braze – AT&T Paulita Moore – AT&T

Introduction of Attendees White-Qwest welcomed all attendees and reviewed the request.

Review Requested (Description of) Change Osborne-Miller-AT&T reviewed the CR. Suellentrop-Qwest verified that this CR was for UNE-P and resale and that the request was for 24 hours advance notification. Zimmerman-AT&T stated that he envisioned a 24 to 48 hour notification. He explained that AT&T submitted the initial dispatch request via electronic bonding system and then followed up with a call. Zimmerman-AT&T asked if any other CLECs have approached Qwest with similar requests. Suellentrop-Qwest stated that he seemed to remember a similar request around 2 years ago. Zimmerman-AT&T stated that this request only applies to only 1-2% of total dispatches in any area.

Confirm Areas and Products Impacted White-Qwest confirmed that the attendees were comfortable that the request appropriately identified all areas and products impacted.

Confirm Right Personnel Involved White-Qwest confirmed with the attendees that the appropriate Qwest personnel were involved.

Identify/Confirm CLEC’s Expectation White-Qwest reviewed the request to confirm AT&T’s expectation.

Identify and Dependant Systems Change Requests White-Qwest asked the attendees if they knew of any related change requests.

Establish Action Plan 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 present the CR at the May Monthly Product/Process Meeting and thanked all attendees for attending the meeting.

CenturyLink Response

July 9, 2003

REVISED RESPONSE For Review by CLEC Community and Discussion at the July 16, 2003, CMP Product/Process Meeting

Donna Osborne-Miller AT&T

SUBJECT: Qwest’s Change Request Response - CR PC042303-1

This CR requests that vendor meets for non-designed products be made at a specific date and time. AT&T has suggested that all AM vendor meets could take place at 9:00 am and all PM vendor meets take place at 1:00 pm.

A Joint Meet involves Qwest, CLECs, and possibly third party vendors, meeting at a designated location to isolate hard-to-find faults, verify existing trouble and diagnosis, and resolve chronic and repeat problems. Qwest accepts this change request to allow CLECs to request a joint meet at a specific time. Qwest proposes this CR be moved into development status. Qwest needs to finalize the mechanics of this process, including how far in advance a joint meet request must be made and any system changes that will be required.

Sincerely,

Craig Suellentrop Staff Advocate, Policy & Law Qwest

Cc: Mary Retka, Director-Legal Issues, Qwest Cathy Augustson, Lead Process Analyst, Qwest

========================================== June 11, 2003

DRAFT RESPONSE For Review by CLEC Community and Discussion at the June 18, 2003, Monthly CMP Product/Process Meeting

Donna Osborne-Miller AT&T

SUBJECT: Qwest’s Change Request Response - CR PC042303-1 “AT&T requests that Vendor Meet (coordinated dispatch) requests for non-design POTS service be at specific times.”

This CR requests that vendor meets for non-designed products be made at a specific date and time. AT&T has suggested that all AM vendor meets could take place at 9:00 am and all PM vendor meets take place at 1:00 pm.

The current vendor meet process for non-designed products gives the customer a 4-hour window for the vendor meet. Because of the complexity in evaluating this request, including possible systems changes that may be required, Qwest requests that this CR be moved into Evaluation Status. Qwest will provide an updated response at the July CMP meeting.

Sincerely,

Craig Suellentrop Staff Advocate, Policy & Law Qwest

Cc: Mary Retka, Director-Legal Issues, Qwest

Open Product/Process CR PC042303-2 Detail

Description Of Change

Expected Deliverable:

Do not call to dispacth on any other that specific scenarios noted in Title of change. Utilize EBTA for "other" dispatch situations.

Status History

Project Meetings

CMP Meeting 11/19/03 Craig Suellentrop – Qwest advised the PCAT has been updated and no comments have been received. Implementation is scheduled for December 1, 2003. This CR will remain in CLEC Test.

CMP Meeting 10/15/03 Craig Suellentrop –Qwest advised pre-dispatch calls will only occur when the CLEC requests them. The notification will go out October 17. This CR will move to CLEC Test Status.

CMP Meeting 9/17/03 Craig advised the notification is almost ready. The documentation team is currently reviewing the documentation. This is a Level 3 change.

CMP Meeting 08-20-03

Suellentrop-Qwest stated that Qwest was finalizing the training and the documentation. He stated that the documentation should be in the review site within the next two weeks. Zulevic-Qwest asked if the change was UNE-P specific. Suellentrop-Qwest stated that the change was for all non-design products.

================================================

CMP Meeting 07-16-03

Osborne-Miller-AT&T described the Qwest acceptance and asked if the response would apply to MEDIACC. Suellentrop-Qwest stated that MEDIACC users would use the comments field. While CEMR users would have a button to select. Zimmerman-AT&T stated that this sounded good. Osborne-Miller-AT&T and Johnson-Eschelon stated that they were very pleased with Qwest’s acceptance of this CR. CR moved to Development.

================================================= CMP Meeting 06-18-03

Suellentrop-Qwest presented the Qwest response. Johnson-Eschelon stated that she thought Qwest was going to check to see if Qwest could use the Call Before Dispatch option in CEMR and only perform the pre-dispatch call for those CLECs. Suellentrop-Qwest stated that it was Qwest’s policy to call regardless of whether the CLEC checks “Call Before Dispatch” in CEMR. He stated that he will check to see if this was an option. Osborne-Miller stated that AT&T was split on the proposed solution in the response. ========================================================== CMP Meeting 05-21-03

Osborne Miller-AT&T presented the CR. Suellentrop-Qwest asked what the other CLECs thought about this request. Johnson-Eschelon stated that Eschelon wanted the calls to continue. She suggested that there might be a systems solution to determine which CLECs wanted the call. Balvin-MCI stated that she would like to see a list of all calls the AT&T would not want. Zimmerman-AT&T stated that AT&T wanted only the CRs denoted in the CR. Johnson-Eschelon stated that there was a field in CEMR for a call before dispatch. She stated that Eschelon wanted the calls. She stated that this should be the CLEC’s option regardless of the reporting medium. ========================================== CLEC Change Request – PC042303-2 Clarification Meeting Friday, May 09, 2003

1-877-550-8686 2213337#

Attendees Matt White – Qwest Craig Suellentrop – Qwest Anthony Washington – Qwest Donna Osborne-Miller – AT&T Craig Zimmerman – AT&T Lydia Braze – AT&T Paulita Moore – AT&T

Introduction of Attendees White-Qwest welcomed all attendees and reviewed the request.

Review Requested (Description of) Change Osborne-Miller-AT&T reviewed the CR. Suellentrop-Qwest asked if AT&T was asking for this change to apply to all trouble tickets. Zimmerman-AT&T stated that most of the tickets are electronically submitted, but that the intent would be for the change to apply to all. He explained that AT&T has a separate line for LEC technicians to call in to. That line does not get a higher priority than customer calls. As a result, because Qwest calls in status reports that do not require AT&T action the supplier line is flooded with unnecessary calls. This call volume and causes AT&T to miss the important action-required calls. Suellentrop-Qwest stated that he understood the request. He stated that he would also be interested to hear other CLEC opinions of this request. Osborne-Miller-AT&T asked if there was any way Qwest would implement this process only for AT&T. Suellentrop-Qwest stated that Qwest would prefer an universal policy.

Confirm Areas and Products Impacted White-Qwest confirmed that the attendees were comfortable that the request appropriately identified all areas and products impacted.

Confirm Right Personnel Involved White-Qwest confirmed with the attendees that the appropriate Qwest personnel were involved.

Identify/Confirm CLEC’s Expectation White-Qwest reviewed the request to confirm AT&T’s expectation.

Identify and Dependant Systems Change Requests White-Qwest asked the attendees if they knew of any related change requests.

Establish Action Plan 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 present the CR at the May Monthly Product/Process Meeting and thanked all attendees for attending the meeting.

CenturyLink Response

July 9, 2003

REVISED RESPONSE For Review by CLEC Community and Discussion at the July 16, 2003, CMP Product/Process Meeting

Donna Osborne-Miller AT&T

SUBJECT: Qwest’s Change Request Response - CR PC042303-2 “AT&T Requests that pre-dispatch calls be limited to specific scenarios, primarily address mismatches, no access situations, and/or vendor meet requests”

This CR requests that the pre-dispatch call made by the Qwest repair technician prior to leaving to the end-user location is only made when there are address mismatches, no access situations, and/or vendor meet requests. AT&T believes that making the pre-dispatch call on all dispatches places an undue burden on their call centers.

The current non-designed repair process for outside technicians requires a courtesy call to the customer of record (both wholesale and retail) prior to leaving to the end-user location. At the May 21 CMP meeting other CLECs requested that this process not be changed and that they want Qwest to make the pre-dispatch call. Therefore, this request was denied at the June CMP meeting.

However, the question was raised about using a box titled, “Call Before Dispatch” in the CEMR application. This function is also available to Qwest’s repair agents on manually reported trouble. The CLEC community was agreeable to the idea of Qwest only performing the pre-dispatch calls when requested via the above mentioned methods. If this is still the case, Qwest accepts this request and will issue a Level 3 notification to implement the modified process.

Sincerely,

Craig Suellentrop Staff Advocate, Policy & Law Qwest

Cc: Mary Retka, Director-Legal Issues, Qwest Cathy Augustson, Lead Process Analyst, Qwest Catherine R. Garcia, Lead Process Analyst, Qwest

====================================== June 11, 2003

DRAFT RESPONSE For Review by CLEC Community and Discussion at the June 18, 2003, Monthly CMP Product/Process Meeting

Donna Osborne-Miller AT&T

SUBJECT: Qwest’s Change Request Response - CR PC042303-2 “AT&T Requests that pre-dispatch calls be limited to specific scenarios, primarily address mismatches, no access situations, and/or vendor meet requests”

This CR requests that the pre-dispatch call made by the Qwest repair technician prior to leaving to the end-user location is only made when there are address mismatches, no access situations, and/or vendor meet requests. AT&T believes that making the pre-dispatch call on all dispatches places an undue burden on their call centers.

The current non-designed repair process for outside technicians requires a courtesy call to the customer of record (both wholesale and retail) prior to leaving to the end-user location. At the May 21 CMP meeting other CLECs requested that this process not be changed and that they want Qwest to make the pre-dispatch call.

Therefore, Qwest respectfully denies this change request because the requested change does not result in a reasonably demonstrable business benefit; this request will negatively impact other CLECs.

However, Qwest would like to address AT&T’s concern regarding placing an undue burden on their call center. As Qwest understands, AT&T has a supplier line and the hold times could be quite lengthy. Qwest would like to propose a process that on the courtesy pre-dispatch calls, the technician would wait in a Voice Response Unit (VRU) for at least a set period of time (say 90 seconds). After this time the technician would drop the call. This would relieve most of the volume into the call center. When there are address mismatches, no access situations, and/or vendor meet requests, the technician would wait on the line until someone is reached. If someone answers the phone, or if the call is routed to voice mail, the process in place today would not change.

Sincerely,

Craig Suellentrop Staff Advocate, Policy & Law Qwest

Cc: Mary Retka, Director-Legal Issues, Qwest Cathy Augustson, Senior Process Analyst, Qwest

Open Product/Process CR 5582318 Detail

Description Of Change

·1: A certified letter - stating that either no customers were ever installed in the collo or if customers were installed, AT&T has notified them their service will be disconnected or moved - and a copy of the decommission application must to be sent to the Account Team Representative. Prior to this process change, AT&T was not required to do this. We have processed approximately 10 decommission applications so far this year and have not sent a certified letter for any of them.

Resolution: AT&T wants to send the application via email only as before.

2. The decommission process reads "The completion of a decommission request and 100% payment of any outstanding financial obligation, will terminate the billing of recurring charges for the site." What this means to AT&T is that we should be current on any bills for the collocation we are decommissioning. What this means to Qwest is that if there is any outstanding bills - either non recurring or recurring - due for any collocation in Qwest territory, they will NOT process the decommission application until all bills for all sites are paid. AT&T may incur additional monthly charges for the collocation being decommissioned since the application is on hold.

Resolution: It is AT&T’s request that only the non recurring and recurring bills for the collocation being decommissioned be subject to scrutiny.

3. Since Qwest charges AT&T a flat fee to decommission a site, AT&T has inquired about the possibility of conducting a site visit to ensure that Qwest has completed the decommissioning of the site. Qwest has denied AT&T this final site visit. Although Qwest may disconnect power cables, conduct a site visit and complete database work, they do not actually tear down the actual site. Qwest is hoping to lease the space to another CLEC and will not have to rebuild the space. Qwest assures AT&T that if the space is leased within a year of the decommissioning, AT&T will reimbursed some monies for the collo space.

Resolution: AT&T would like proof that the work has been completed.

Status History

Project Meetings

As a result of your feedback concerning Qwest’s recently issued Decommission procedures for existing Collocation sites, Qwest is adopting an interim plan for 90 days. During this interim 90-day period, Qwest will hold a series of meetings and conference calls with the industry to develop mutually acceptable procedures to follow concerning this issue. Please review the interim changes and the calendar of meetings below. We sincerely hope that you will participate.

Interim Changes Effective August 9, 2001 • Qwest will no longer issue a Quote of $3455 for each decommission before monthly recurring billing stops.

Qwest is waiving the Decommission Quote charges effective immediately with issuance of this announcement. Future pricing will be reviewed as part of the “Future Procedures Modifications Process” as described below.

• Qwest will credit past decommission quotes paid and any monthly charges paid past the date of acceptance of the valid application. CLECs can contact their Wholesale Project Manager regarding past decommissions processed or currently being processed.

• The vacating CLEC submitting the “Collocation Application for Cancel, Decommission, or Change of Responsibility” will no longer be required to be current on all billing for all collocation sites, including both monthly and non-recurring quotes before Qwest will process a decommission request.

• The interim requirement will state that a CLEC must be current on “all billing for the specific site for which the decommission application is submitted” for Qwest to decommission a site.

• Qwest will no longer require receipt of the quote charges to stop billing. Monthly billing will stop effective with the valid receipt of a decommission application.

• Applications will no longer need to be sent via certified mail for processing. “Electronic submission of requests to decommission a site can be sent to colo@qwest.com”

Future Procedures Modifications Process Qwest intends to issue future procedures that are acceptable to those parties concerned. For Qwest to implement satisfactory procedures, CLEC feedback is needed and valued. At the completion of this joint 90-day effort, the revised product procedures will be priced, and if appropriate, a template offered by Qwest for an amendment to the CLEC/Qwest

Interconnection Agreements. Please join Qwest in participating in the following calendar of meetings. These meetings will be chaired by Steve Nelson, Group Product Manager Collocation. He can be reached on 303-896-6357. Interested CLECs are encouraged to participate.

Kick-off meeting

August 9th, from 9am to 3pm, 1801 California, Executive Conference room, 23rd floor. Conference bridge: 877-542-1778, pass code 6904985.

1. Review existing product offerings and proposed changes, gather information on additional proposed changes, understand all concerns. Here is a brief outline of the discussion: 2. Agree to as many items as possible initially, table for future review those items requiring detailed response, and respond to disputed items by next meeting for resolution. 3. Capture voting record of participants on each issue, and dissenting opinion as agreed to by the team. 4. Prioritization of changes and timelines. 5. Review costing of current products. Items included in the costing model. 6. Discuss how other ILECs handle cancellation, decommission, change of responsibility or network transfer.

CenturyLink Response

October 31, 2001 Sharon Van Meter Manager, AT&T 1875 Lawrence St., 10th floor Denver, Colorado 80202

CC: William Campbell Steve Nelson Jane Lacy

This letter is in response to CLEC Change Request Form #5582318, dated June 25, 2001. This Change Request pertains to several issues regarding the Decommission product offering. On July 9th Qwest committed to partnering with the CLEC industry to resolve the issues identified in the Change Request Form specifically referring to decommission procedures. In addition, Qwest expanded this effort to review the product offerings for Cancellation, and Change of Responsibility. Throughout the month of August, September and October representatives from Qwest and the CLEC industry met to review the procedures for administering a Cancellation and Decommission request. The Qwest/CLEC Forum meetings will continue as we work together to revamp the Change of Responsibility product offering procedures. Successful resolution was achieved for those items addressed in the Decommission Change Request Form. Your efforts were instrumental in this partnership effort.

The following is a summary of the issues identified in the Decommission Change Request Form and the resolution for each: AT&T objected to process changes unilaterally without input from AT&T. Qwest committed to participate in a joint effort to review the Cancel, Decommission, and Change of Responsibility product offerings with CLEC industry and met that commitment. AT&T objected to the requirement to submit a certified letter stating that AT&T customers were notified of the disconnect or move. Qwest agreed to modify the process and allow both the application and confirmation notice to be sent electronically to the rfsmet@qwest.com mailbox. AT&T objected to the requirement that 100% payment of any outstanding financial obligation must be met in order to terminate billing of recurring charges. Qwest modified the procedures to state that financial obligations must be met with respect to the collocation site that is being decommissioned only. We further defined the financial obligations to include all non-recurring and monthly recurring charges must not be greater than thirty (30) days past due. AT&T objected to when the monthly recurring charges would cease. Qwest agreed that the billing end date will coincide with the date of a valid Decommission Application submit date. AT&T felt that they should be entitled to some monies for reimbursable elements at the Decommission site. Qwest agreed that a CLEC would be eligible for reimbursement on the re-usable elements for up to one (1) year from the Decommission Application submit date.

The following is the implementation schedule for the revised Cancellation and Decommission procedures: 11/15/01 - CMP Notification 12/01/01 - CLEC Review Period 12/15/01 - Revised Cancellation and Decommission procedures posted on the Collocation PCAT 01/01/02 - Effective date for the revised Cancellation and Decommission procedures

In summary, Qwest believes that we have satisfied your concerns regarding the Decommission and Cancellation procedures and therefore are considering this Change Request closed.

Sincerely,

Steve Nelson Group Collocation Product Manager

Open Product/Process CR 5579794 Detail

Description Of Change

Status History

Project Meetings

Open Product/Process CR 5582288 Detail

Description Of Change

Description changed resulting from 8/27/01 meeting.

The app date calculation for all LNP requests will reflect a 7 p.m. daily cut-off time rather than the 3 p.m. cut-off currently in place. Any LNP request received prior to 7 p.m. will receive an app date of the current date. Any LNP request received after 7 p.m. will receive an app date of the next business day.

Status History

Project Meetings

RE: CR Form #5582288 AT&T understands Qwest is denying our request to include Saturday as a business day in the SIG. In addition, Qwest is denying our request to manually change orders submitted prior to 7 p.m. MST on Wednesday to reflect a Saturday install date in lieu of a system change.

AT&T appreciates Qwest expanding the LSR submission deadline from 3 p.m. to 7 p.m. MST with the IMA 8.0 release. We are disappointed at the restriction placed on Saturday ports which Qwest had previously honored under the 3-day SIG (submissions of LSRs on Wednesday). Any additional action concerning this change request will be handled in a different venue when prudent. Sincerely, Terry Bahner AT&T Local Services – LSAM Western Region

CC: Sharon Van Meter Tim Boykin Donna Osborne-Miller Mitch Menezes

September 14, 2001

Lorna Dubose LNP Wholesale Product Manager Qwest Communications 1801 California Street Denver, Colorado 80202

RE: Your letter dated September 5, 2001 regarding change request 5582288 - Saturday as a business date

Dear Lorna:

It was not the intention of AT&T to worsen the service delivery to our customers by accepting the LNP Service Intervals in the State 271 Workshops. Section 10.2.5.2 LNP Standard Intervals has been reviewed and AT&T does not believe this section prevents Qwest from processing the change request to include Saturday as a business date for the LNP product. In fact, AT&T can find no dialogue from the 271 workshops which addressed omitting Saturday as a business day when determining LNP intervals.

Before the IMA 8.0 upgrade the weekend of August 18th, Qwest honored a 3-day interval for a Saturday install as long as AT&T Broadband submitted the LSR prior to 3 p.m. MST on Wednesday. Qwest’s typing center set expectations that AT&T passed on to its customers by providing a FOC with the 3-day interval.

Qwest has stated Saturday cannot be counted in the standard interval. Per Qwest, all local service requests must be submitted prior to 3pm MST on Tuesday to receive the Saturday install date. While AT&T understands Qwest has implemented and updated their systems to reflect its intervals, AT&T believes changes to the same system including Saturday as a business day can also be accomplished in an upcoming release. Though AT&T realizes Qwest is extending its business day from 3:00 p.m. to 7:00 p.m. MST, it does not satisfy the CR5582288 AT&T submitted. Saturday is a critical install day for AT&T Broadband. Qwest’s shift in process and the failure to inform AT&T of this change created an undue and sudden burden for AT&T Broadband’s customers.

Therefore, AT&T would like to partner with Qwest to implement a change as previously practiced by Qwest which includes Saturday. In the interim, AT&T is requesting Qwest to manually change orders submitted prior to 3:00 p.m. MST on Wednesday to reflect a Saturday install date. Thank you for your consideration.

Sincerely,

Terry Bahner Supervisor Local Services Access Management Western Region

CC: Tim Boykin Sharon Van Meter Mitchell Menezes

###

September 7, 2001 2:15 p.m. Attendees:Terry Bahner (AT&T), Donna Osborne-Miller (AT&T), Sharon Van Meter (AT&T), Lorna Dubose (Qwest), Joan Wells (Qwest), Michael Buck (Qwest), Todd Mead (Qwest) The Qwest response to this CR was presented. AT&T reiterated concerns presented in an e-mail from August 30, 2001. The concerns centered on the fact that from June 1 until August 20 Qwest had used a process that allowed for a 3-day interval. After August 20 Qwest adjusted its process, requiring that requests be received by 3 p.m. Tuesday to qualify for a Saturday install. AT&T understands Qwest’s position that the process in place from June 1 through August 20 was incorrect. Furthermore, AT&T understands Qwest’s position that a reversion of process is necessary to remain compliant with guidelines decided in 271 Workshops. However, AT&T believes that Qwest should have been more effective in communicating the process change which resulted in an increase in the necessary interval to support a Saturday install. Qwest indicated that effective communication is a key element to implementing changes that affect CLECs.

Action Items: - Terry Bahner (AT&T) to provide confirmation of response acceptance (9/13)

### E-Mail from Terry Bahner (AT&T) to Qwest Thursday, August 30, 2001 12:15 p.m.

It's clear from the Qwest-Broadband call I facilitated this morning that Qwest has changed their process regarding the 3 day interval proces+U3when it pertains to a Saturday install date. From June 1st (PCNRN051601-1) to August 18, Qwest FOC'd a Saturday install date using the 3 day interval guide. As long as the LSR was sent prior to 3pm mst on Wednesday, Qwest gave the Saturday install date. On August 20th, Qwest changed its process. The LSR must be submitted on Tuesday before 3pm to have a Saturday install date. Qwest now states the due date interval guidelines do not include Saturday. Qwest has indicated the process was always in place and it was incorrectly interpreted by Qwest Escalations and typists and was therefore granted in error. AT&T reviewed the RN on multiple conference calls with Qwest and was told the requested Saturday date would be met. Further more AT&T was never informed the RN was a test/trial subject to change and/or interpretation by Qwest. AT&T considered the notification sent by Qwest on June 1st as a product and process change not a temporary fix as so indicated on this morning's call. While I welcome the extension of 3pm mst to the tentative 7pm mst, it no longer meets the intent of the CR. Therefore, please pursue with AT&T's request to include Saturday in Qwest's due date interval guidelines.

Thank you. Terry L. Bahner AT&T LSAM

###

Monday, August 27, 2001 1 p.m. Attendees: Terry Bahner (AT&T), Sharon Van Meter (AT&T), Lorna Dubose (Qwest), Michael Buck (Qwest), Todd Mead (Qwest) Terry re-confirmed AT&T understands CR scope resulting from 8/14/01 meeting. To wit, the app date calculation for all LNP requests will reflect a 7 p.m. daily cut-off time rather than the 3 p.m. cut-off currently in place. Any LNP request received prior to 7 p.m. will receive an app date of the current date. Any LNP request received after 7 p.m. will receive an app date of the next business day.

In follow-up, Terry clarified: This is separate from agreeing to the current app date calculation Qwest has adopted August 20 (IMA 8.0 release) for LNP orders which now negatively impacts AT&T Broadband’s provisioning process and directly affects our market entry. AT&T will submit a separate change request to Qwest to resolve the additional day added to the LNP service interval if Qwest continues the new app date calculation process. This change request’s intent was to further extend the timeframe in submitting LSRs to facilitate a 3-day install; however, Qwest’s new app date calculation has negated this. Lorna indicated that a new Qwest User Request (UR # 2491) has been created to support the requested change. Work is underway to prioritize the request and determine when it will be implemented. This information will be provided in the Qwest response for this CR.

Lorna indicated that efforts had been underway to (piggyback) this CR on an existing user request in an attempt to complete the change sooner. However, that effort failed and new UR (2491) was issued.

Action Items: - Lorna Dubose (Qwest) to formulate Qwest response by 8/31/01 - Michael Buck (Qwest) to organize a walk-through meeting with AT&T during week of 9/3/01.

###

LNP Meeting Notes 08/13/01 Attendees: Lorna Dubaose Matt Rossi Terry Bahner Donna Osborne-Miller

NPAC does not currently consider Saturday as a business day AT&T gave an example: if LSR submitted 3:01 pm on Friday - Monday is day 1, AT&T would like Saturday as day 1 Joan Wells mentioned at last CICMP that hours might be expanded to 7pm MST AT&T said that 7pm wold be sufficient and CR could be closed

CenturyLink Response

Wholesale Product Marketing Ms. Terry Bahner and Ms. Donna Osborne, AT&T

This letter is in response to your letter dated September 14, 2001, regarding Change Request 5582288 – Saturday as a business day.

Qwest acknowledges AT&T’s acceptance of the agreed upon 271 Workshop LNP Service Intervals.

As stated in your letter, before the IMA 8.0 release, Qwest would honor a three day interval for a Saturday install for LSR’s submitted prior to 3:00 p.m. Mountain Time on Wednesdays. However, after the IMA 8.0 release each CLEC, will need to submit its LSR for flow-through LNP orders on Tuesday by 7:00 p.m., Mountain Time, in order to have a Saturday due date.

Qwest identified the need to implement system logic to obtain parity between our manual and mechanized processes, company policies, as well as documentation. As a result, IMA was upgraded to support the company Service Interval Guide (SIG), which excludes the calculation of Saturdays, Sundays, and Holidays.

Qwest recognizes Saturday is a critical install day for AT&T Broadband and will continue to offer Saturdays, Sundays, and Holidays as due dates in our switches where the 10-digit unconditional LNP trigger can be set automatically. However, the CLEC will need to submit the LSR within the appropriate interval timeframe as far as business days.

At this time, Qwest appreciates AT&T offer to partner with us to include Saturday as a business day, however, Qwest declines, and will continue to support the agreed upon 271 Workshop intervals and existing company practice for the use of Business days. Thank you for your request.

Sincerely,

Lorna Dubose LNP Product Manager

Open Product/Process CR PC110201-2 Detail

Description Of Change

Modification - 11/27-01:

The CR will focus on accepting partial LSRs that are related to multiple LSRs and will also evaluate any differences on managed cuts versus coordinated cuts.

Status History

Project Meetings

CenturyLink Response

December 27, 2001

Jonathon Spangler ILEC Relations Manager AT&T

This letter is being sent in response to CLEC Change Request Form # PC110201-2. PC110201-2 pertains to a request to change the due date on one or more LSRs that were previously submitted in a group of related PONs. This response addresses the current IMA process for changing the due date on one or more LSRs within a group of related PONs allowing the remaining PONs to be processed.

IMA Process:

A supplemental LSR should be issued for the PON requiring the due date change. The value entered in LSOG field 25 SUP should be “3” because there will be other changes on the LSR in addition to the due date change.

The value entered in LSOG field 51 RPON should be blank to indicate that this PON is no longer part of a related group.

The value of LSOG field 14 DDD should contain the new desired due date.

The value of LSOG field 10 PGofPageof should follow the LSOG business rules for the product specified on the LSR.

The LSOG business rules are documented on the Qwest website http://www.qwest.com/wholesale/clecs/lsog.html.

Sincerely, Deborah Osborne Process Specialist

Open Product/Process CR PC090401-1 Detail

Description Of Change

Request for Qwest to separate daily usage files by separating category 01 and 010 from category 011. Categories 01 and 010 separate daily usage records for end users while category 011 tracks billing for other carriers. AT&T separates billing entities by these functions. AT&T believes that other carriers utilize this same process. AT&T believes would be more efficient if the daily usage files were separate in this manner.

Status History

Project Meetings

Alan indicated that he was familiar with this subject. He believed it had been submitted once before but did not have the support of the other CLECs at that time. Alan indicated that he thought some of the CLECs might see the need for this now.

Alan stated the issue: In the current environment two usage files containing the same data are sent to two locations. ATT would like to have the file containing message types 01 and 10 split out on one file. The other file should contain message type 11, to be distributed separately.

Carla indicated she would take this CR to the next community meeting to propose this change to other CLECs.

CenturyLink Response

November 6, 2001

This letter is in response to the CLEC Change Request Form #PC090401-1. This Change Request requests that the Daily Usage Feed (DUF) be split into two pieces - with local usage (generally Category 1 & 10 EMI records) on one file, and access usage (Category 11 records) on a separate file.

Today, both local usage and access usage is sent on a single DUF file for each CLEC. It is fairly straight-forward to separate this usage into two files. To do so requires some small programming changes, as well as some JCL and NDM/Connect: Direct changes for every CLEC that chooses to have their DUF split into two pieces. This would be a medium-sized effort. This CR will be moved to the Systems CMP process in order to prioritize this system work.

Qwest would implement this CR in such a way that those CLECs that wish to continue to receive their DUF file as one file (like today) would be able to continue with that implementation. Those that wish to receive two separate files would be able to do so, having those two files sent to two different destinations (assuming connections exist) or to the same destination as the CLEC desires.

Any CLEC who would like to have their DUF split in two as this CR requests may send an e-mail to me at azimmer@qwest.com to be included in the deployment of this functionality. If you have any questions, feel free to e-mail me or call me at the number below.

Sincerely,

Alan Zimmerman (303)896-8346

Open Product/Process CR PC030802-1 Detail

Description Of Change

- Caller must be a Qwest retail customer

- Customer must call business office and say they wish to "remove the freeze off of their local service"

- Do not instruct the customer to use the word "PIC". This is used for inter and intra lata services and causes confusion which can delay removing the LEFV

- CLEC can be a third party on the call to Qwest by the local customer

- Customer can call up to 7pm in his local service area to remove the freeze

- The LEFV resides in a repository that is worked overnight which means it will be removed off the customer's account that night and the LSR can be sent the next day without rejection

- Although updates to a CSR can take up 3-5 days, the removal of the freeze is not dependent on that CSR being updated.

- Qwest does not charge $5 to remove the freeze

- A Communicator will be sent to the CLEC community when the PCAT is updated

The last 2 bullet points can be removed from the CR as per clarification call 03/18/02

Scope expanded to include business accounts as well (per CLEC request 03/20/20)

Status History

Project Meetings

Documentation and disposition of AT&T CR PC 03802-1 – Local Service Freeze

As you know, I submitted this CR and requested application of the CMP “Exception Process”. I then escalated the issue based on discussions with Qwest. It’s a strange dichotomy for Qwest to state at the CMP Product and Process meeting that AT&T had five business days to respond to Qwest’s binding response to AT&T’s escalation of PC 030802-1 and then infer it was at Qwest’s own discretion whether to even document AT&T’s comments let alone where. At a minimum, the correspondence generated as part of the escalation should be included with the documentation of the CR, just as all other correspondence and minutes relating to CRs are documented. Since Qwest indicated in its binding response to AT&T’s escalation that Qwest would continue “to do problem solving working sessions with AT&T”, I don’t understand why my request to move the escalated change request to a ”Development” status was denied. AT&T understood the main purpose of escalating a change request was to ensure it received top priority based on business needs, not to house it in the dead-end file once Qwest provides its binding response. Qwest was clearly not prepared to present the binding response at the CMP meeting. No copies were provided to the CLEC community at the meeting and Sue Burson appeared unsettled by the request to present the binding response and respond to questions. While I have provided detailed written comments on Qwest’s binding response, AT&T has not rejected it. The areas addressed by Qwest’s response may satisfy most of AT&T’s needs, however, it is not clear from Qwest’s response that the problems AT&T has been experiencing have actually been resolved. AT&T expects that Qwest will work collaboratively with AT&T to resolve these issues. We are extremely disappointed that Qwest chose to then send out the local service freeze notice as a Level 1 notification (Announcement Date: April 18, 200; Document Number: PROS.04.18.02.F.00426.LocalServFreeze) . Judy, you had articulately explained the five levels of Qwest-initiated product/process changes in the morning portion of the April 17th meeting. Yet, the notice was sent on April 18th as a Level 1 instead of the Level 3 AT&T had strongly recommended in our written and oral responses on April 17th. We have repeatedly indicated to Qwest the local service freeze has had a daily negative impact on our ability to meet the end customers’ requests for a change in local service provider. For Qwest to indicate at this juncture of the change request that no comment cycle is available to the CLEC community shows a true disregard for the redesigned CMP, to the commitment made by the entire CMP re-design team since its work began in July 2001 and to Qwest’s commitment in its binding response “to do problem solving working sessions with AT&T.”

04/10/02 - AT&T comments on Qwest's draft response

1. Caller must be a Qwest retail customer This is a true statement. The Qwest Retail end user may contact their Qwest Retail business office to have their local service freeze removed. Their new CLEC may be on the phone with them at the same time (Three-way call).

AT&T - AT&T should be able to call the retail office without having the customer on line, this would eliminate the unnecessary time it takes to reach the customer. (Portland Metro Market – AT&T Broadband)

2. Customer must call business office and say they wish to "remove the freeze off of their local service" This is a true statement. When the end user customer contacts the Qwest Retail business office, they should ask to have their local service freeze removed. If the end user customer simply states that they are moving to AT&T, there may be some confusion as to whether this is a PIC change or the customer is moving their local service to AT&T.

AT&T - Does the retail office see the pending order to port to the CLEC? End users are being told their Qwest number(s) are disconnected and therefore Qwest cannot remove the LEFV. Perhaps they are confusing the "pending" disconnect. Notation on the Qwest side is very poor. Customers are given information such as their number is disconnected, but when they call back again, there is no note of the information they were given or even that they called in earlier. (Denver Metro Market - AT&T Broadband) AT&T believes the Qwest Retail business office is not the best arm of Qwest to be responsible for removing the LEFV. Sales’ organizations are based on revenue generating actions. They should not be responsible for lifting the LEFV when this clearly indicates a loss of revenue when the end customer moves to another competing CLEC for their local service. We believe this accounts for the lack of notations on the customer’s account after he has called nine times to remove the LEFV. (Terry Bahner - LSAM)

3. Do not instruct the customer to use the word "PIC". This is used for inter and intraLATA services and causes confusion which can delay removing the LEFV This is true. It is helpful in guiding the end user customer through the process since they may have a PIC, LPIC, and Local Service Freeze. The Sales Consultants have been provided training and job aids to help determine the customer’s need.

AT&T - Again, Qwest’s notation is very poor. The notes need to indicate what "type" of freeze the customer wishes to remove. The customer will use the word "LOCAL" and the Qwest notes will indicate "PIC". This is still a training issue on the Qwest side. The "R" order number should be noted so both sides of Qwest’s offices have access to this information. (Denver Metro Market - AT&T Broadband) AT&T believes the lack of notation or the wrong notation on the customer’s account and the multiple times the end customer has to call Qwest to lift the LEFV is indicative of a failed process and a serious training deficit. (Terry Bahner - LSAM)

4. CLEC can be a third party on the call to Qwest by the local customer See question #1

AT&T - AT&T believes Qwest needs to send out additional internal memos to drive home this statement. (Terry Bahner - LSAM)

5. Customer can call up to 7pm in his local service area to remove the freeze Qwest has customers across three different time zones. The Residence end user customer may call their Qwest Retail business office until the close of business in the Pacific time zone. - Central time zone until 9:00 PM (they will be routed to a center in the Mountain or Pacific time zones after 7:00 PM local time) - Mountain time zone until 8:00 PM (they will be routed to a center in the Pacific time zone after 7:00 PM local time) - Pacific time zone until 7:00 PM The hours for the Business, Federal Government, Education, Public Access Lines business offices are listed in the April 3, 2002 update to the PCAT.

AT&T - The window of opportunity to reach the retail office should be extended to include Saturdays. (Portland Metro Market - AT&T Broadband) Prime selling hours are until 9pm. The 7pm time could prevent us from closing the sale if the customer has a freeze on. It is not enough to rationalize that the customer can always call back later to remove the freeze. Sales organizations know that any obstacle thrown in the way of completing the sale at the time of offering the sale diminishes the chances of completing the sale. This places Qwest at an unfair competitive advantage. (Salt Lake Metro Market - AT&T Broadband) AT&T requests expanded hours to include Saturdays. (Denver Metro Market - AT&T Broadband) AT&T believes that Qwest for the time being should at least match their hours of removing the LEFV to the Monday-Saturday schedule already in existence. A second option would be for the CSIE to field the calls and note the customer’s account. (Terry Bahner - LSAM)

6. The LEFV resides in a repository that is worked overnight which means it will be removed off the customer service record. Qwest has a Local Freeze Repository where all frozen phone numbers are stored. That repository is updated on a daily basis as orders are issued to add or remove local freeze. When an order is issued to remove the freeze, the telephone number is removed from the Repository that night. The LEFV will not be removed from the CSR for 3-5 days. See further explanation in response to question 7.

AT&T - If the "R" order number is supplied in the remarks field...why cannot this be done manually and resubmitted the same day? See # 7’s explanation that SDC’s are already checking for system notations and if there is a notation, they will process the LSR. If Qwest does include Saturday hours but not same day supps, what day would the number update in the repository? (Denver Metro Market - AT&T Broadband)

7. Although updates to a CSR can take up 3-5 days, the removal of the freeze is not dependent on the CSR being updated. The Customer Service Record does not update for 3-5 days after the R order is issued to add or remove the Local Service Freeze. When a LSR is issued and there is LEFV on the CSR, the Wholesale Service Delivery Coordinators are checking system notations to determine if an order has been issued to remove the local service freeze. If there is a notation, they will process the LSR. In addition, if the LSR contains the R order number (of the freeze removal) the SDC will allow the order to be processed.

AT&T - The centers should be able to send the LSR immediately after calling the retail office to remove the freeze. Waiting 24hrs to submit is unacceptable unless Qwest is willing to reduce the 3-business day port rule. (This point was made my Jonathan Wolf on last week’s call. (Portland Metro Market - AT&T Broadband) However, the LSR will be rejected if submitted the same day as the LEFV removal request. This adds an additional day to the installation process. This may also require AT&T to contact the customer again to reschedule the originally promised installation date. This, in turn, could cause the original install to be missed if the customer cannot be contacted again in enough time to meet the due date. (Salt Lake Metro Market - AT&T Broadband)

The following questions were submitted by AT&T in a letter to Qwest dated 03/19/02

8. Customer required to call Qwest multiple times to remove LEFV The customer should be able to accomplish removal of the local service freeze in one call to Qwest.

AT&T - Simply remove the freeze with one call. (Portland Metro Market - AT&T Broadband) Should be able to and can are two different things. (Salt Lake Metro Market - AT&T Broadband) AT&T has provided examples where this demonstrates that it does not occur. As stated in earlier meetings with Qwest, this is one of the three process requirements that must be addressed to move the CR towards a workable process. (Terry Bahner - LSAM)

9. No established process to remove the LEFV at the Qwest retail offices Qwest has had established processes in place for local service freeze removal since March 10, 2001 when Local Service Freeze was first implemented.

AT&T - There are no established process by Qwest, until a workable process is in place a all frozen accounts should be lifted per Mike Mason’s request on the last two calls. (Portland Metro Market - AT&T Broadband) It’s apparent these "established processes" are broken. (Denver Metro Market - AT&T Broadband) AT&T has repeatedly indicated the process is not consistent. This has been demonstrated to Qwest by examples that range from Qwest refusing to help the end customer when AT&T Broadband is on the call to actually adding the LEFV and issuing a "D" order to disconnect the customers service instead of the "R" order. (Terry Bahner - LSAM)

10. No consistent confirmation number provided by the Qwest retail offices to note customer account Qwest Sales Consultants are currently providing the R order number to any end user customer or CLEC (on 3-way call) who requests it. We have determined that a specific work group has been providing "confirmation numbers" instead of the R order numbers. That situation has been corrected by the issuance of internal memo (MCC) and managing the performances of the involved individuals. Do not hesitate to request the R order that is being issued to remove the freeze.

AT&T - AT&T believes Qwest needs to continue to monitor how the LEFV is noted on the customer’s account by the Qwest representative. Although AT&T acknowledges and appreciates Qwest identifying a specific work group who was incorrectly providing a "good" confirmation number, a problem still surfaced after the MCC was sent. Once again we reference when Qwest issued either a "D" order or a "C" order for removing the LEFV. (Terry Bahner - LSAM)

11. Inconsistent information between the account team and the PCAT pertaining to submission of the LSR The PCAT is the Qwest official source for CLEC information.

AT&T - AT&T believes Qwest subject matter experts did provide inconsistent information to the service managers. It placed them in a precarious position by having to always "go to the SPOC" for every issue concerning the LEFV. This caused delays in developing a working process and delays in the status of the examples provided. It created a unnecessary extra layer in resolving outstanding LEFV issues. (Terry Bahner - LSAM)

12. Inconsistent Quality Check process at the Sierra Vista Center Calls and orders are monitored on a regular basis to ensure quality.

AT&T - Improved communication between the retail office and Sierra Vista (Portland Metro Market - AT&T Broadband) Inconsistencies still exist. (Denver Metro Market - AT&T Broadband) If this is true, why is Qwest saying they can cancel an LSR related to an LEFV issue? If this is true, why are some orders rejected and others are issued a jeopardy condition after the FOC? (Terry Bahner - LSAM)

13. Inconsistent escalation process at the Denver CSIE once confirmation has been received There are several determining factors as to how the escalation is handled. Each escalation is reacted to on an individual case basis.

AT&T - A single point of contact for escalations. (Portland Metro Market - AT&T Broadband) AT&T believes this does not meet our business requirements. Our third standing request is for Qwest to provide an escalation process that addresses LEFV issues that occur out of process. AT&T should not be penalized and lose their requested due date when Qwest fails to remove the LEFV. Our customer should never be placed in jeopardy when he wishes to have another CLECS’ local service because a Qwest system or agent failed to respond properly to a LSR issue regarding LEFV. (Terry Bahner - LSAM)

14. IMA 9.0 edit pulled and no notice sent to the CLEC Qwest did not remove any IMA 9.0 edits; therefore, notification to the CLECs was not necessary. There was a non-IMA edit in place that was checking the CSRs for LEFV which was relaxed so LSRs could flow through and allow the Service Order Processors to check the Freeze Repository and edit for a freeze at that point in the process.

AT&T - Qwest has stated on numerous occasions that back end systems are not considered CLEC impacting. Therefore, these back end system edits are neither subject to a CLEC review nor a CLEC upgrade notification. AT&T believes these edits did affect our orders. We believe they changed whether a LSR was rejected up front or issued a jeopardy condition after the FOC. This alters how a CLEC responds to an LSR. AT&T has repeatedly asked how these non-IMA edits affect our orders. Qwest has not provided an answer. AT&T has reconfirmed the information provided on March 15th by the Qwest service managers that an edit did occur on March 14th, 2002. If we cannot question Qwest’s backend systems, then we will refer to it as an IMA change when we believe our orders have been impacted. (Terry Bahner - LSAM)

15. IMA 9.0 edit to be implemented at a future date without CLEC notice All planned CLEC Impacting changes to IMA are currently being presented to the CLECs for prioritization. There are no plans to implement a 9.0 edit pertaining to Local Service Freeze.

AT&T - AT&T wants Qwest to not implement any edits in any systems (IMA, non-IMA) until a workable process to remove the LEFV has been agreed upon by AT&T and the CLEC community. (Terry Bahner - LSAM)

16. Jeopardy condition codes issued after the FOC affecting CLEC due date Qwest has listened to the concerns raised by AT&T on this issue and has taken steps to fortify existing processes to alleviate this problem.

AT&T - However, since we have to wait to supp the Pon AFTER the freeze is removed, this still results in a due date push out/reschedule for the customer. (Denver Metro Market - AT&T Broadband) AT&T wants to know what these steps are. The action of issuing a jeopardy condition after the FOC drastically affects our due date. If this jeopardy condition is a result of Qwest’s inability to successfully lift the LEFV, we believe we should not lose our due date under any circumstances. (Terry Bahner - LSAM)

17. Inconsistent Qwest retail process where CLEC can be a third party on the call with end customer See question #1

18. Inconsistent process between removing the LEFV and the updating of the CSR See question #6

19. Confusing reject /jeopardy condition message issued by Qwest The reject/jeopardy message currently being used is the only existing message that fits the local service freeze situation. Requests for new reject messages go through the CMP CR process. LSRs received to change lines/accounts with a local service freeze are rejected with the error message "Features on account are not compatible with requested features". In the Customer Comments section of the Reject Notice Qwest will include the following: "Please have end user contact current local service provider to have local service freeze removed."

AT&T - According to an earlier Qwest communication, Qwest stated the error message would read "Change activity not allowed, CLEC does not own account". Is this the message if the reject is caught up front (fatal reject) as opposed to the message for a jeopardy reject after the FOC? Or has this been changed altogether? (Denver Metro Market - AT&T Broadband) AT&T believes Qwest has not adequately addressed this issue. AT&T has requested LEFV be listed as a reason for a reject/jeopardy message in the PCAT. The jeopardy matrix needs to address LEFV. (Terry Bahner - LSAM)

20. AT&T reiterated they would like all of the above bullet points validated by Qwest and the process clearly documented in the PCAT The PCAT will be updated April 3, 2002.

AT&T - Under the current circumstances, Qwest needs to provide a collaborative atmosphere in resolving LEFV issues before any future PCAT documentation takes place. (Terry Bahner - LSAM)

21. What kind of questions does Qwest ask a Retail end user customer before adding a local service freeze? Upon initial contact with the end user customer, the Qwest Sales Consultant informs the customer of the availability of the freeze as follows: "We offer free protection to ensure that your provider of local service, long distance service, and local long distance service cannot be changed unless you contact us directly. You may remove this protection from your account at any time by contacting Qwest directly with a verbal, written, or electronically signed authorization. Would you be interested in setting that up now?" If the end user customer indicates they would like a freeze established, they are transferred to a Third Party Verifier (TPV) who asks the customer for the Billing Name on the account, Billing Address, the last four digits of their Social Security Number, and their date of birth. In addition, they ask if the caller is over 18 years old and is responsible for the account, and if they have permission to place the local service freeze on each specific line of the account.

AT&T - AT&T believes Qwest needs to go beyond the statement provided. It’s apparent the end customer is unaware of the cumbersome process to remove the LEFV when he wishes to obtain local service from a different company. (Terry Bahner - LSAM)

22. What changes have been made in the Local Service Freeze Removal process since 02/18/02? The process was working well before that date. Qwest has had established processes in place for local service freeze since March 10, 2001 when Local Service Freeze was first implemented. The only changes made to the process have been made within the past two weeks as a result of this CR.

AT&T - It is very clear to AT&T that Qwest did not have a working process in place on March 10, 2001. If Qwest had a good process in place that didn’t harm both the end customer and the CLEC, this CR would have never been submitted. (Terry Bahner - LSAM)

As a general proposition, Qwest has responded in the theoretical realm to many of the questions versus saying what the actual situation is (like in #8 above, but there are many other examples in their responses). It's easy to set up a theoretical process, but that is meaningless if the practical implementation is not being accomplished effectively. (Salt Lake Metro Market - AT&T Broadband)

-

04/08/02 - Draft follow-up meeting minutes sent to participating CLECs via e-mail

CLEC Change Request Follow-up Meeting 11:30 a.m. (MDT) / Thursday 4th April 2002 1-877-564-8688 ID 626-5401 # PC030802-1 Local Service Freeze - Process to remove LEFV from Qwest residential accounts

Attendees: Terry Bahner / AT&T Sharon Van Meter / AT&T Lindel Watkis / AT&T Mike Mason / AT&T Cynthia Linenberger / AT&T Rick Wolters / AT&T Johnthon Wolf / AT&T Joan Russell / AT&T Mitchell Menezes / AT&T Bonnie Johnson / Eschelon Karen Clauson / Eschelon Terry Wicks / Allegiance Leilani Hines / Worldcom Susan Travis / Worldcom Monica Avila / VarTec Telecom, Inc. Judy Schultz / Qwest Todd Mead / Qwest Harriett Berry / Qwest Pam DeLaittre / Qwest Scott Riley / Qwest Pete Budner / Qwest Carylon Brown / Qwest Sue Burson / Qwest

Introduction: - Qwest presented a brief history of the CR, (submitted 03/08/02, clarification call 03/18/02, AT&T expedite letter 03/19/02, AT&T walked-on @ CMP 03/20/02, general clarification call 03/26/02, Qwest draft response issued 04/02/02). The purpose of this call is to review Qwest’s draft response dated 04/02/02 - Note: Notification CMPR.04.01.02.F.01248.CRMeeting issued to CLECs on the 1st of April, informing them of a call on 04/04/02 for a follow up discussion on this issue. Standard P&P Redline guidelines of 5 business days for notifications to CLECs not followed due to expedited status of this CR.

Review Qwest Draft Response - Harriett Berry reviewed Qwest’s draft response dated April 2, 2002 - AT&T commented that using Aegis is currently their only option, as when they call the Qwest Business Offices they be on hold for long periods and the staff do not appear to be familiar with this process. AT&T asked that the 866-311-0222 number remain in effect. Qwest agreed that the Aegis number will remain in effect until this issue is resolved. - AT&T stated that the Qwest web site states the Local Service Freeze can be removed immediately, which has not been their experience. Qwest reiterated that it is effective the same day, but the LSR has to be submitted the next day. AT&T then asked Qwest to reduce the process time by one business day. Qwest took an action to reply to this. - AT&T stated that their desire is for Qwest to lift the Local Service Freeze so the LSR can be submitted the same day - see 2.10 - Eschelon asked if the LSR can be submitted using the R-Order number in the PON field? Qwest believed this would work. Qwest will investigate and report back. - AT&T reiterated they believe something changed on February 18th. They believe this process is broken and asked Qwest to lift the Freeze to before February 18th conditions - see 2.10 - Eschelon stated that Qwest could go to the State Commissions and seek a waiver on the Local Service Freeze. Eschelon also asked about a written process to remove the Freeze. Besides the presence of a form, Eschelon wanted to know whether there was a back end process in place to deal with this and what had been communicated to the CLECs? Qwest took an action to respond to this. - AT&T reiterated they are seeking: 1. To only have to make one call 2. To send in their LSR without rejection 3. A clear and concise escalation process 4. Have the AGIS number available on Saturday’s - AT&T also stated they continue to see large numbers of customers with the Freeze implemented, who believe they have never asked for it on their account. Qwest replied that they are continuing to investigate the AT&T examples and have already found most of the TPV’s for the AT&T examples. AT&T replied they have heard this before but have yet to receive any validation from Qwest. AT&T stated the implementation of a freeze is not clear as too many customers are not aware of this action on their account. Qwest will provide validation to Terry Bahner (AT&T) - AT&T stated they were going to escalate this CR as they expected resolution today, but believed this call had failed in its intent. AT&T want the freeze lifted and want an official response on this from Qwest in 24 hours. AT&T also offered to support an application by Qwest to the commission to get a waiver on Local Service Freeze until this issue is resolved. - AT&T also stated they believe the interim exception process has not worked for them as they had expected a response to this CR immediately.

Establish Action Plan - Qwest will respond to the above actions as soon as possible. - Qwest will either respond or provide a status update on lifting the freeze within 24 hours

-

04/05/02 - Status update from Qwest on AT&T's request to immediately lift the freeze

Status Update: Per action from April 4th CLEC Meeting

All, Qwest continues to review and analyze AT&T's request made yesterday to lift the Local Service Freeze. Qwest has not arrived at its final position at this time, however executive management is deeply engaged. We will follow up with another status update prior to close of business Monday April 8th 2002.

CR details can be found in the Product & Process Interactive report. The Product & Process Interactive report can be found at: http://qwest.com/wholesale/cmp/changerequest.html

Thanks Todd Mead

-

04/05/02 - Letter from AT&T expressing their disappointment with Qwest's response presented in the follow-up meeting on 04/04/02

1875 Lawrence St. Denver, CO 80202-1847

April 5, 2002

Todd Mead CMP Manager Qwest Communications 1801 California Street Denver, Colorado 80202

RE: Change Request PC 030802-1

Dear Todd:

This reconfirms AT&T’s repeated request that Qwest suspend the local service freeze until a collaborative Qwest-CLEC process can ensure an effective, efficient and prompt way to remove the LEFV with no impact to the end customer. AT&T does not believe Qwest’s draft response presented at the April 4th conference call meets our company’s immediate needs.

AT&T is disappointed that Qwest cannot recognize the impact the LEFV has on our daily LNP operations. It is very disturbing when Qwest continues to fail to bring to the table a workable solution. It is discouraging when Qwest continues to ignore our requests to engage the appropriate Qwest subject matter experts to participate in discussions with AT&T to help resolve this issue quickly. Had the appropriate operational SMEs from Qwest participated on the call yesterday, we might have made progress resolving these issues. Unfortunately, once again such individuals were absent.

AT&T’s expectations of the LEFV process is really quite simple. The end customer should be able to remove the LEFV with one call. AT&T Broadband should then be able to submit the LSR to port the customer immediately after the customer has taken the appropriate step to remove the LEFV without fear of an order rejection or a jeopardy condition being issued after the FOC. And last, if the process fails, there is a working escalation process to effectively handle the issue quickly.

Up to this point, Qwest has made minimal effort to work with AT&T to hammer out a workable solution. We view this as a dismal Qwest failure. First, it demonstrates Qwest’s inability to perform a normal function adequately. Second, it clearly shows Qwest does not acknowledge nor recognize the urgency related to the CMP exception process. Third, it demonstrates Qwest’s inability to effectively manage changes to its processes when they adversely impact CLECs.

AT&T will send to Qwest written comments embedded in Qwest’s April 2, 2002, rough draft response to change request PC 030802-1. It will also include AT&T’s proposed resolutions. In the meantime, AT&T will continue to direct the end customer to call AEGIS directly to remove the LEFV from his account. We are expecting at least a verbal response from Sue Burson by close of business today regarding AT&T’s request to suspend LEFV until a workable process can be implemented. AT&T would expect Sue to then send a written response to AT&T. Please insure the minutes from the April 4th conference call reflect AT&T has officially escalated this to Sue Burson.

Sincerely,

Terry Bahner Supervisor AT&T Local Services Access Management Western Region 303-298-6149

Cc: Tim Boykin Sharon Van Meter Donna Osborne-Miller Judy Schultz Mike Mason

-

04/02/02 - Notification PROS.04.02.02.F.00414.LocalServiceFreeze issued informing CLECs of PCAT update

Announcement Date: April 2, 2002 Effective Date: April 3, 2002 Document Number: PROS.04.02.02.F.00414.LocalServiceFreeze Notification Category: Process Notification Target Audience: CLECs, Resellers Subject: Options to Remove Local Service Freeze

Beginning April 4, 2002, Qwest will issue updates to its Wholesale Product Catalog that includes new/revised documentation for Local Service Freeze.

The Local Service Freeze PCAT will be updated to outline the options of requesting the removal of the Local Service Freeze. The PCAT also lists the information the retail end-user needs to provide to have the Local Service Freeze removed.

You will find a summary of these updates on the attached Web Change Notification Form. Actual updates are found on the Qwest Wholesale Web site at this URL: http://www.qwest.com/wholesale/clecs/lsfreeze.html

You are encouraged to provide feedback to this notice through our web site. We provide an easy to use feedback form at http://www.qwest.com/wholesale/feedback.html. A Qwest representative will contact you shortly to discuss your suggestion.

-

03/28/02 - Letter from AT&T expressing their disappointment with the general clarification call held on 03/26/02

1875 Lawrence St. Denver, CO 80202-1847

March 28, 2002

Todd Mead CMP Manager Qwest Communications 1801 California Street Denver, Colorado 80202

RE: Change Request PC 030802-1

Dear Todd:

AT&T is greatly disappointed with the conference call Qwest facilitated March 26, 2002 to discuss the expedited CR PC 030802-1. Qwest stated at the March 20, 2002 Product and Process CMP monthly meeting they understood the urgency of this change request regarding the local service freeze (LEFV). There was no need for a second clarification call. A clarification call had already been held on March 18, 2002.

We believed Qwest was willing to resolve the issue expediently, Todd, when you indicated you would have your subject matter experts available on the March 26th call. I then indicated to you that I was expecting my AT&T Broadband subject matter experts to also be available to help resolve the issue in the e-mail I sent March 22, 2002 (RE: CR # 5582295 - Updated Matrix). I suggested, in order getting to immediate resolution, that you include operational subject matter experts. I was very clear about AT&T’s expectations for the March 26th conference call.

AT&T also believes Qwest implied a resolution would be forthcoming by indicating the temporary 800 telephone number was directly dependent on the outcome of the March 26th meeting. If Qwest was not ready to problem solve the issue then there should never have been a question about keeping the 800 number available. While AT&T appreciates Qwest extending the use of the 800 telephone to help ease the burden of this issue, we should not have had to explain why we needed the extended use of it.

AT&T once again reminds Qwest of the negative impact the LEFV has imposed on our ability to port a customer. It continues to affect our daily ability to port a customer who wants our local service. This truly is unacceptable to us. AT&T has identified and shared with Qwest some of the most basic obstacles in a letter sent March 18, 2002 (RE: Change Request PC 030802-1).

Since Qwest has indicated a formal response will be issued to the CLEC community on April 3rd without a collaborative effort between Qwest and the CLEC community, AT&T clearly expects Qwest to be open to additional suggestions on the follow up conference call scheduled April 4th. AT&T expects that conference call to resolve outstanding issues and the appropriate decision-making individuals from Qwest will attend.

We believe going forward explicit timelines should be provided and adhered to by Qwest for an expedited CR. It should mirror the expedited CR Qwest presented as a walk on at the same March 20 meeting. Qwest clearly defined the timeframe and expectations of the CLEC community during that presentation. It should not be any different for an expedited CLEC CR.

AT&T looks forward to partnering with Qwest and the CLEC community to enhance the Interim Exceptions Process for OSS interfaces, Product and Process Changes (RE: Qwest Re-Design Web site) in future re-design CMP sessions. We believe use of the process, as it now stands for this specific change request, clearly indicates its’ lack of substance.

Sincerely,

Terry Bahner Supervisor AT&T Local Services Access Management Western Region 303-298-6149

Cc: Tim Boykin Sharon Van Meter Donna Osborne-Miller Judy Schultz Mike Mason

-

03/27/02 - Draft general clarification meeting minutes sent to participating CLECs via e-mail

General Clarification Meeting

3:00 p.m. (MDT) / Tuesday 26th March 2002

1-877-564-8688 ID 626-5401 # PC030802-1 Local Service Freeze - Process to remove LEFV from Qwest residential accounts

Attendees: Terry Bahner / AT&T Carla Dickinson-Pardee / AT&T Sharon Van Meter / AT&T Lindel Watkis / AT&T Mike Mason / AT&T Cynthia Linenberger / AT&T Noriko Wilson / AT&T Anthony Robert / AT&T Leilani Hines / Worldcom Susan Travis / Worldcom Monica Avila / VarTec Telecom, Inc. Judy Schultz / Qwest Todd Mead / Qwest Harriett Berry / Qwest Pam DeLaittre / Qwest Gay Abrahamson / Qwest Joan Smith / Qwest Connie Winston / Qwest

Introduction: Qwest presented a brief history of the CR, (submitted 03/08/02, clarification call 03/18/02, AT&T expedite letter 03/19/02, AT&T walked-on @ CMP 03/20/02 and general notification to all CLECs advising them of this meeting 03/21/02) Note: Notification CMPR.03.21.02.F.01239.CRMeeting issued on 03/21/02 to CLECs informing them of a call on 03/26/02 to discuss this issue. Standard P&P Redline guidelines of 5 business days for notifications to CLECs not followed due to expedited status of this CR.

Review Description of Change: Terry Bahner read out the following from Change Request PC030802-1: VALIDATE THESE FOLLOWING BULLET ITEMS AS PART OF THE PROCESS: - Caller must be a Qwest retail customer - Customer must call business office and say they wish to "remove the freeze off of their local service" - Do not instruct the customer to use the word "PIC". This is used for inter and intra lata services and causes confusion which can delay removing the LEFV - CLEC can be a third party on the call to Qwest by the local customer - Customer can call up to 7pm in his local service area to remove the freeze - The LEFV resides in a repository that is worked overnight which means it will be removed off the customer's account that night and the LSR can be sent the next day without rejection - Although updates to a CSR can take up 3-5 days, the removal of the freeze is not dependent on that CSR being updated. - Qwest does not charge $5 to remove the freeze * - A Communicator will be sent to the CLEC community when the PCAT is updated * *Removed as per clarification meeting 03/18/02 Terry also read out additional scope as per AT&T’s expedite request (AT&T letter dated 3/19/02) - Customer required to call Qwest multiple times to remove LEFV - No established process to remove the LEFV at the Qwest retail offices - No consistent confirmation number provided by the Qwest retail offices to note customer account - Inconsistent information between the account team and the PCAT pertaining to submission of the LSR - Inconsistent Quality Check process at the Sierra Vista Center - Inconsistent escalation process at the Denver CSIE once confirmation has been received - Qwest retail office confusing end customers by referring to the LEFV as a PIC freeze (Repeated above 3rd bullet) - IMA 9.0 edit pulled and no notice sent to the CLEC - IMA 9.0 edit to be implemented at a future date without CLEC notice - Jeopardy condition codes issued after the FOC affecting CLEC due date - Inconsistent Qwest retail process where CLEC can be a third party on the call with end customer - Inconsistent process between removing the LEFV and the updating of the CSR - Confusing reject /jeopardy condition message issued by Qwest

- AT&T reiterated they would like all of the above bullet points validated by Qwest and the process clearly documented in the PCAT - AT&T confirmed they would like the CR scope expanded to include Business Accounts as per CLEC request at the March CMP meeting. Todd will adjust CR documentation. - AT&T stated that 68% of all orders for removing LEFV in the Portland region had to be rescheduled last month. AT&T are seeking clarification on what exactly is the process for removing LEFV. AT&T also asked for an extension on the 800 number until the LEFV process is clarified and documented. - Qwest reiterated that they are working as expeditiously as possible to resolve this issue, and they aim to present a written draft response to the CLECs next week. - AT&T said they are willing to wait for the written response next week but need immediate ‘relief’ now. Immediate ‘relief’ was defined by AT&T as: - Keeping the 800 number live until next week (and include Saturday availability) - Someone in CSIE to take the lead on this issue and be nominated as the Single Point of Contact (SPOC) - Qwest would confirm later in the day on the status of this request. - AT&T also stated that they believe 100% of customers they talk too, insist they never asked for the freeze to be installed. AT&T would like to know what type of validation/questions Qwest ask to believe the customer has requested this product. - AT&T also asked for clarification on the R-Number and whether the order number is sufficient as some LSRs are currently being rejected with this information. - Worldcom and VarTec Telecom expressed their continued interest in this issue. - Qwest restated that they are currently not aware of anything that was ‘backed out’ of IMA 9.0 and also reiterated that the only work currently pending for IMA is in the prioritization list for all CLECs to vote on. - AT&T stated that since February 18th 2002, this process has not been working. They requested that in light of Qwest’s inability to support the process and the fact that the freeze placed on accounts were questionable as far as customer approval to begin with. That the best and quickest way to fix this matter was to lift the freeze and go back to the way we were prior to February 18th and not go back until all the issues were properly addressed and good process was actually in place. Qwest stated that a number of States were ‘turned-up’ on Feb 18th so this may be a volume issue. AT&T believe their volume did not change on Feb 18th and asked for the freeze to be lifted until a working process is put in place by Qwest. Qwest replied they understood AT&T’s concern and reiterated they are working as fast as possible on getting an accurate and workable solution for all CLECs.

Establish Action Plan: Next Meeting: Thursday 4th April @ 11:30 am (MDT) - same bridge number as this call. Qwest will present written response. Qwest will investigate and report back to AT&T this afternoon on providing ongoing ‘relief’

-

03/21/02 - Notification CMPR.03.21.02.F.01239.CRMeeting issued to CLECs informing them of a call on 03/26/02 to discuss this issue

Qwest will host a general clarification meeting on CLEC Change Request (CR) PC030802-1 (Process to remove LEFV from Qwest residential accounts) on Tuesday March 26, 2002.

Date: Tuesday, March 26, 2002 Time: 3:00 p.m. MST Conference Line: 1-877-564-8688 Passcode 626-5401 #

Details of the CR can be found in the Product/Process Interactive report at: http://qwest.com/wholesale/cmp/changerequest.html Sincerely,

Todd Mead

-

03/19/02 AT&T advised Qwest they would like this CR expedited

1875 Lawrence St. Denver, CO 80202-1847

March 18, 2002

Todd Mead CMP Manager Qwest Communications 1801 California Street Denver, Colorado 80202

RE: Change Request PC 030802-1

Dear Todd:

AT&T is requesting Qwest to officially expedite PC 030802-1. The local service freeze (LEFV) is critically affecting AT&T Broadband’s ability to port customers. This LEFV has presented multiple obstacles. We are requesting to have an immediate discussion between Qwest and AT&T Broadband subject matter experts to discuss the many problems associated with LEFV. What have been identified to date are the following:

- Customer required to call Qwest multiple times to remove LEFV - No established process to remove the LEFV at the Qwest retail offices - No consistent confirmation number provided by the Qwest retail offices to note customer account - Inconsistent information between the account team and the PCAT pertaining to submission of the LSR - Inconsistent Quality Check process at the Sierra Vista Center - Inconsistent escalation process at the Denver CSIE once confirmation has been received - Qwest retail office confusing end customers by referring to the LEFV as a PIC freeze - IMA 9.0 edit pulled and no notice sent to the CLEC - IMA 9.0 edit to be implemented at a future date without CLEC notice - Jeopardy condition codes issued after the FOC affecting CLEC due date - Inconsistent Qwest retail process where CLEC can be a third party on the call with end customer - Inconsistent process between removing the LEFV and the updating of the CSR - Confusing reject /jeopardy condition message issued by Qwest

It is critical Qwest establish a team to address the customer impact and at the same time improve the processes. As I have indicated both in e-mail and on the clarification call to Qwest, this is now a high profile issue between both companies. Mike Mason, Vice-President AT&T Broadband, has escalated this to Scott Shipper, Vice-President Qwest.

AT&T’s account team has declined to work directly with AT&T to resolve this issue and has instructed AT&T to move all discussion to CMP. In addition Todd, you stated on the clarification call held March 18, 2002, Qwest would not provide a resolution to this CR until the monthly CMP forum in May. This is unacceptable to AT&T.

AT&T requests Qwest to expedite PC 030802-1 immediately. AT&T will present this CR as a "walk on". Please inform Jim Beers. Under the Interim Exception Process for OSS Interfaces, Product and Process Changes (RE: Qwest Re-Design Web site) this can be addressed at Wednesday’s monthly CMP meeting and voted on as an expedited issue by the CLEC community.

Sincerely,

Terry Bahner Supervisor AT&T Local Services Access Management Western Region 303-298-6149

Cc: Tim Boykin Sharon Van Meter Donna Osborne-Miller Judy Schultz

-

Clarification Meeting

11:00 a.m. (MDT) / Monday 18th March 2002 1-877-564-8688 ID 626-5401 # PC030802-1 Local Service Freeze – Process to remove LEFV from Qwest residential accounts

Attendees: Terry Bahner / AT&T Donna Osborne-Miller / AT&T Cynthia Linenberger / AT&T Lindel Watkis / AT&T Mike Harggert / AT&T Harriett Berry / Qwest Chris Quinn-Struck / Qwest Pete Budner / Qwest Todd Mead / Qwest

Review Requested (Description of) Change: Terry read out the change request: VALIDATE THESE FOLLOWING BULLET ITEMS AS PART OF THE PROCESS: * Caller must be a Qwest retail customer * Customer must call business office and say they wish to "remove the freeze off of their local service" * Do not instruct the customer to use the word "PIC". This is used for inter and intra lata services and causes confusion which can delay removing the LEFV * CLEC can be a third party on the call to Qwest by the local customer * Customer can call up to 7pm in his local service area to remove the freeze * The LEFV resides in a repository that is worked overnight which means it will be removed off the customer's account that night and the LSR can be sent the next day without rejection * Although updates to a CSR can take up 3-5 days, the removal of the freeze is not dependent on that CSR being updated. * Qwest does not charge $5 to remove the freeze * A Communicator will be sent to the CLEC community when the PCAT is updated

- AT&T asked for more clarification around the 6th Bullet as the updated PCAT indicated the LSR can be submitted immediately after the LEFV is removed (not the next business day). - The last two bullet points can be removed from the original CR. Todd will adjust the CR documentation. - AT&T asked for clarification around the edit that is going into IMA - AT&T asked for Qwest to explain the role and also train the duty pager on the Local Service Freeze process. AT&T have experienced significant problems with issues they have escalated to the duty pager - AT&T also asked Qwest to provide clarification on what remarks to expect in the remarks section of the jep notification re: Joan Wells

Confirm Areas & Products Impacted: Products: LNP, Private Line, Unbundled Loop & UNE Areas: Pre-ordering, Ordering & Provisioning - Billing was added

Confirm Right Personnel Involved: Harriett confirmed she is the correct person to be the Qwest SME in relation to this CR.

Identify/Confirm CLEC’s Expectation: AT&T want to see a clear and concise process around removing the Local Service Freeze, verified and documented in PCAT.

Establish Action Plan (Resolution Time Frame): General clarification – April CMP meeting. Qwest’s initial response presented at May CMP meeting. AT&T will send Change Management a letter this afternoon requesting Qwest expedite this CR. AT&T will ‘walk-on’ this CR at Wednesday’s CMP meeting.

CenturyLink Response

April 2, 2002

Terry Bahner Supervisor AT&T Local Services Access Management 1875 Lawrence St. Denver, CO 80202-1847

SUBJECT: Qwest’s Change Request Response - CR # PC 030802-1 "Local Service Freeze Removal for Residence and Business Customers"

Following are responses to your list of issues and questions from CR #PC030802-1, your additional list of issues dated March 19, as well as questions from our March 26, 2002 conference call.

1. Caller must be a Qwest retail customer This is a true statement. The Qwest Retail end user may contact their Qwest Retail business office to have their local service freeze removed. Their new CLEC may be on the phone with them at the same time (Three-way call).

2. Customer must call business office and say they wish to "remove the freeze off of their local service" This is a true statement. When the end user customer contacts the Qwest Retail business office, they should ask to have their local service freeze removed. If the end user customer simply states that they are moving to AT&T, there may be some confusion as to whether this is a PIC change or the customer is moving their local service to AT&T.

3. Do not instruct the customer to use the word "PIC". This is used for inter and intraLATA services and causes confusion which can delay removing the LEFV This is true. It is helpful in guiding the end user customer through the process since they may have a PIC, LPIC, and Local Service Freeze. The Sales Consultants have been provided training and job aids to help determine the customer’s need.

4. CLEC can be a third party on the call to Qwest by the local customer See question #1

5. Customer can call up to 7pm in his local service area to remove the freeze Qwest has customers across three different time zones.

The Residence end user customer may call their Qwest Retail business office until the close of business in the Pacific time zone.

- Central time zone until 9:00 PM (they will be routed to a center in the Mountain or Pacific time zones after 7:00 PM local time) - Mountain time zone until 8:00 PM (they will be routed to a center in the Pacific time zone after 7:00 PM local time) - Pacific time zone until 7:00 PM

The hours for the Business, Federal Government, Education, Public Access Lines business offices are listed in the April 3, 2002 update to the PCAT.

6. The LEFV resides in a repository that is worked overnight which means it will be removed off the customer service record. Qwest has a Local Freeze Repository where all frozen phone numbers are stored. That repository is updated on a daily basis as orders are issued to add or remove local freeze. When an order is issued to remove the freeze, the telephone number is removed from the Repository that night. The LEFV will not be removed from the CSR for 3-5 days.

See further explanation in response to question 7.

7. Although updates to a CSR can take up 3-5 days, the removal of the freeze is not dependent on the CSR being updated. The Customer Service Record does not update for 3-5 days after the R order is issued to add or remove the Local Service Freeze.

When a LSR is issued and there is LEFV on the CSR, the Wholesale Service Delivery Coordinators are checking system notations to determine if an order has been issued to remove the local service freeze. If there is a notation, they will process the LSR. In addition, if the LSR contains the R order number (of the freeze removal) the SDC will allow the order to be processed.

The following questions were submitted by AT&T in a letter to Qwest dated 03/19/02

8. Customer required to call Qwest multiple times to remove LEFV The customer should be able to accomplish removal of the local service freeze in one call to Qwest.

9. No established process to remove the LEFV at the Qwest retail offices Qwest has had established processes in place for local service freeze removal since March 10, 2001 when Local Service Freeze was first implemented.

10. No consistent confirmation number provided by the Qwest retail offices to note customer account Qwest Sales Consultants are currently providing the R order number to any end user customer or CLEC (on 3-way call) who requests it. We have determined that a specific work group has been providing 'confirmation numbers' instead of the R order numbers. That situation has been corrected by the issuance of internal memo (MCC) and managing the performances of the involved individuals. Do not hesitate to request the R order that is being issued to remove the freeze. 11. Inconsistent information between the account team and the PCAT pertaining to submission of the LSR The PCAT is the Qwest official source for CLEC information.

12. Inconsistent Quality Check process at the Sierra Vista Center Calls and orders are monitored on a regular basis to ensure quality.

13. Inconsistent escalation process at the Denver CSIE once confirmation has been received There are several determining factors as to how the escalation is handled. Each escalation is reacted to on an individual case basis.

14. IMA 9.0 edit pulled and no notice sent to the CLEC Qwest did not remove any IMA 9.0 edits; therefore, notification to the CLECs was not necessary. There was a non-IMA edit in place that was checking the CSRs for LEFV which was relaxed so LSRs could flow through and allow the Service Order Processors to check the Freeze Repository and edit for a freeze at that point in the process.

15. IMA 9.0 edit to be implemented at a future date without CLEC notice All planned CLEC Impacting changes to IMA are currently being presented to the CLECs for prioritization. There are no plans to implement a 9.0 edit pertaining to Local Service Freeze.

16. Jeopardy condition codes issued after the FOC affecting CLEC due date Qwest has listened to the concerns raised by AT&T on this issue and has taken steps to fortify existing processes to alleviate this problem.

17. Inconsistent Qwest retail process where CLEC can be a third party on the call with end customer See question #1

18. Inconsistent process between removing the LEFV and the updating of the CSR See question #6

19. Confusing reject /jeopardy condition message issued by Qwest The reject/jeopardy message currently being used is the only existing message that fits the local service freeze situation. Requests for new reject messages go through the CMP CR process.

LSRs received to change lines/accounts with a local service freeze are rejected with the error message "Features on account are not compatible with requested features." In the Customer Comments section of the Reject Notice Qwest will include the following: "Please have end user contact current local service provider to have local service freeze removed."

20. AT&T reiterated they would like all of the above bullet points validated by Qwest and the process clearly documented in the PCAT. The PCAT will be updated April 3, 2002. 21. What kind of questions does Qwest ask a Retail end user customer before adding a local service freeze? Upon initial contact with the end user customer, the Qwest Sales Consultant informs the customer of the availability of the freeze as follows: "We offer free protection to ensure that your provider of local service, long distance service, and local long distance service cannot be changed unless you contact us directly. You may remove this protection from your account at any time by contacting Qwest directly with a verbal, written, or electronically signed authorization. Would you be interested in setting that up now?"

If the end user customer indicates they would like a freeze established, they are transferred to a Third Party Verifier (TPV) who asks the customer for the Billing Name on the account, Billing Address, the last four digits of their Social Security Number, and their date of birth. In addition, they ask if the caller is over 18 years old and is responsible for the account, and if they have permission to place the local service freeze on each specific line of the account.

22. What changes have been made in the Local Service Freeze Removal process since 02/18/02? The process was working well before that date. Qwest has had established processes in place for local service freeze since March 10, 2001 when Local Service Freeze was first implemented. The only changes made to the process have been made within the past two weeks as a result of this CR.

Sincerely,

Harriett Berry Senior Process Analyst Qwest

Cc: Sue Burson, Director Process Management, Qwest

Open Product/Process CR 5582099 Detail

Description Of Change

Status History

Project Meetings

Cc: Tim Boykin Sharon Van Meter Donna Osborne-Miller

November 14 - CMP Meeting Callan-Qwest described the CR and the Qwest response. Bahner-AT&T stated that she did not want the CR to be closed as she had just received the response. She also noted that Qwest has not shared its PID data with AT&T. Clausen-Eschelon stated that this CR should not be in CLEC test. Bahner-AT&T stated that she was under the impression that Qwest was moving toward a solution to the CR, but that the recent response was a denial. Callan-Qwest stated that Qwest had evaluated the potential solution and was not prepared to accept the risk of changing a stable system platform, which would be the result of moving forward with a solution to the CR. Dixon-Worldcom asked if this measure was in the PAP. Callan-Qwest stated that it is a PID and it is also a PAP, except in Arizona. Dixon-Worldcom stated that this was inconsistent with his understanding of the Qwest agreements. He understood that Qwest would automatically incorporate all of the ROC measures into the Arizona filing. Callan-Qwest stated that it was her understanding that this had not been requested as a PAP in Arizona. Schultz-Qwest stated that Qwest would take an action item and report at the next meeting. She stated that the CR is denied and asked what status AT&T wanted to leave it in. Bahner-AT&T stated that she would like it left as Presented until next month.

November 6, 2001 AT&T Response to our final position on the CR. Lorna Dubose Qwest LNP Wholesale Product Manager

RE: CR Form #5582099 This letter is in response to the status you provided at the October 17, 2001 Product and Process CMP meeting. We look forward to Qwest implementing a system change that would disconnect the TN out of the switch immediately after AT&T Broadband activates the number. This change would eliminate unnecessary loss of dial tone between Qwest and AT&T Broadband, reduce the number of work backs and snap backs and in general, provide continuity to the LNP process. In the interim, AT&T Broadband will continue to operate under the process formally introduced on August 20th, 2001.

We look forward to the next status in November and a possible implementation date in 2002.

Sincerely, Terry Bahner AT&T Local Services – LSAM Western Region

CC: Sharon Van Meter Tim Boykin Donna Osborne-Miller Mitch Menezes

Internal Status Update Meeting (9/18/01 4:30 p.m.) Attendees: Michael Buck (Qwest), Lorna Dubose (Qwest) Internal cost analysis still on track for 9/28/01 completion. Lorna updated target date for formal AT&T response to 10/12/01.

###

September 7, 2001 2:15 p.m.

Attendees:

Terry Bahner (AT&T), Donna Osborne-Miller (AT&T), Sharon Van Meter (AT&T), Lorna Dubose (Qwest), Joan Wells (Qwest), Michael Buck (Qwest), Todd Mead (Qwest)

Qwest provided a status update on this CR. Qwest has received time and cost estimates from 2 vendors to date. Qwest will be seeking a time and cost estimate from a third vendor. The addition of a third vendor is not expected to adjust the dates communicated in the August 27, 2001 Clarification Meeting. AT&T asked whether Qwest has yet committed to performing the change requested in this request. In response to a question from Sharon, Lorna indicated that Qwest has not yet committed to doing the work requested in this CR. The decision whether or not do the work is dependent upon the cost analysis scheduled for completion by 9/28/01.

Action Items:

- Lorna Dubose (Qwest) to create cost analysis based upon vendor time and costs by 9/28/01 - Lorna Dubose (Qwest) to develop Qwest response based upon cost analysis (tentative target: 10/5/01)

###

Monday, August 27, 2001 1 p.m. Attendees: Terry Bahner (AT&T), Sharon Van Meter (AT&T), Lorna Dubose (Qwest), Michael Buck (Qwest), Todd Mead (Qwest) Terry confirmed that the goal of this CR is to have Qwest provide a response regarding AT&T’s desire that LNP disconnects not be released until a corresponding activate transaction is received from NPAC indicating that AT&T service is operational.

Terry indicated that previous action taken by Qwest (i.e. delayed posting of disconnects until due date plus 1 day) is helpful, but does not address the core of this request. Lorna reiterated that Qwest is still seeking vendor time and cost estimates to provide the functionality requested by AT&T.

Lorna expects to develop a cost analysis based upon vendor responses by the end of September. At that time Qwest will make a decision whether or not to pursue the vendor proposals.

Lorna does expect to be able to provide an interim status update at the September CMP meeting. As of August 29, 2001 time and cost bids have been received from both vendors involved in this CR.

Action Items: - Lorna Dubose (Qwest) to create cost analysis based upon vendor time and costs by 9/28/01 - Lorna Dubose (Qwest) to develop Qwest response based upon cost analysis (tentative target: 10/5/01)

###

LNP Meeting Notes - 8/13/01

Attendees: Lorna Dubose Matt Rossi Terry Bahner Donna Osborne-Miller

- Qwest looking at long term solution - Price bid expected from Telcordia by 8/27 - Price bid expected from another vendor 08/30 - Cost analysis and internal analysis to be conducted by Qwest 09/28 - Estimated implementation date set for no earlier than Q1 2002

CenturyLink Response

Ms. Terry Bahner Ms. Donna Osborne-Miller

AT&T

This letter is in response to your CLEC Change Request Form, number 5582099 dated June 6, 2001 – LNP Switch Disconnect Timing.

Request: Change current switch disconnect process to where disconnect occurs immediately after AT&T Broadband activates the number.

Response: Qwest understands the goal is to eliminate disconnection of customers in error. Qwest has agreed to Performance Measurement OP-17 - Timeliness of Disconnects Associated with LNP Orders with a standard of 98.25%. Qwest is in full support of this measure and has committed to this standard.

In August, Qwest completed the mechanization of the solution to hold the switch translations and the service orders until 11:59 P.M. of the next business day after the port due date. Initial analysis of internal data from before and after the implementation indicates a 73% reduction in loss of dial tone and an 84% reduction in workbacks.

Qwest did evaluate several vendor proposals outlining a system solution to time the switch disconnect with the port activation. Qwest believes that our current process and recent system mechanization has provided a reliable and stable platform for the completion of port orders. As a result of the analysis of the vendor proposals, and the service improvements from our own internal system changes; we will not be pursuing any additional system enhancements. No further action is planned. Sincerely,

Maureen Callan Group Product Manager

Open Product/Process CR PC031203-2X Detail

Description Of Change

Status History

Project Meetings

- From: Stecklein, Lynn [mailto:Lynn.Stecklein@qwest.com] Sent: Friday, June 22, 2007 1:49 PM To: LEE, KATHY T, ATTCORP Subject: Question on PC031203-2X Resolve Disconnect of Account Number

Hi Kathy, I believe you missed the discussion in the June Product/Process CMP Meeting on SCR031203-2X Resolve Disconnect of Account Number. Here is what was discussed: PC031203-2X Resolve Disconnect of Account Number (Cross Over from SCR031203-02)

Mark Coyne-Qwest stated that this CR was a crossover from Systems and was implemented on 6/4/07. Mark asked if AT&T was ok to close.

No one from AT&T was on the bridge.

Mark Coyne-Qwest stated that we would work offline with AT&T.

I wanted to check with you to determine if this CR can be closed. I have attached a copy of the CR.

Thanks!

Lynn Stecklein

Qwest Wholesale CMP

-- 6/20/07 Product/Process CMP Meeting

Mark Coyne-Qwest stated that this CR was a crossover from Systems and was implemented on 6/4/07. Mark asked if AT&T was ok to close. No one from AT&T was on the bridge. Mark Coyne-Qwest stated that we would work offline with AT&T.

5/16/07 Systems CMP Meeting

Mark Coyne-Qwest stated that this CR was crossed over from Systems and is scheduled for implementation on June 4th. Mark then noted that the Level 2 Notice would be going out on May 14th. Mark asked if there were any questions or comments. There were none.

-- 4/18/07 Product/Process CMP Meeting

Mark Coyne-Qwest stated that this CR was a crossover from Systems and was discussed in the March CMP Meeting.

Lynn Stecklein-Qwest stated that a notification will be sent to update the documentation.

3/21/07 Product/Process CMP Meeting

Mark Coyne-Qwest stated that this Systems CR was submitted by AT&T and will be crossed over to a Product/Process CR.

Lynn Stecklein-Qwest stated that this System CR, as Mark said, was submitted by AT&T requesting a solution for when a CLEC migrates a multi-line account and then sometime later their customer requests to disconnect the main number. AT&T stated that disconnecting the BTN on a multi-line account means that a new account number may have to be assigned and that they did not know what the rules were for when this happened. Lynn said that during the requirements review for this CR it was determined that this request can be accommodated with a Process change instead of a System change. She said that a clarification call was held with AT&T and other CLECs on March 1 to communicate the process solution. Lynn said that during that meeting, Qwest stated that when a customer has a multi-line account and the main BTN is being removed from the account, the customer has the option of using specific fields (i.e. NAN) to select what remaining TN they would like to use as the new BTN. If no notification is received from the CLEC then the next logic line number will be assigned as the new BTN. Lynn stated that AT&T agreed that this process would work for them and stated that they preferred this to a system change. She said that that this process is documented in various PCATs and updates will be made for this CR.

Mark Coyne-Qwest stated that the system CR will be closed and will cross over to a Product and Process CR.

3/1/07 Additional Clarification Meeting

SCR031203-02 Resolve Disconnect of Account Number

Attendees: Chris Terrell-AT&T, Kathi Lee-AT&T, Leo Dimitriatis-AT&T, Kim Isaacs-Eschelon, Anne Pent-Qwest, Lynn Stecklein-Qwest

Lynn Stecklein-Qwest stated that the purpose of this meeting was to communicate a solution for this change request that would require no system work. If everyone agreed with this solution we would cross this CR over to a Product/Process CR.

Anne Pent-Qwest cited the example of a 5 line account with the main billing TN (BTN) being removed from the account. Anne said that you have the option of using the NAN field on selecting what remaining TN you would like to use as the new BTN.

Leo Dimitriatis-AT&T reviewed the scenario of a 5 line account and 4 TNs are being left behind and belong to Qwest. Leo said that they would have the option of choosing the BTN.

Anne Pent-Qwest stated that we would take the next logic line number if no notification is received from the CLEC. She said that the TNs on the CSR may not be sequential.

Leo Dimitriatis-AT&T said that the next logic line number would then become the BTN and asked if the account would be updated with the 4 remaining TNs.

Anne Pent-Qwest stated that happens prior to completion.

Leo Dimitriatis-AT&T said that after the migration occurs, they will see the newly assigned BTN. He said that this is a good scenario.

Kim Isaacs-Eschelon asked what happens to the listing associated with the old BTN.

Anne Pent-Qwest said that we don’t make the listing change. She said that the FOC on a ported number has a remarks section to indicate if the listing is to be changed.

Kim Isaacs-Eschelon said that with a Resale or QPP account, you have 1 CSR with the Main Listing and the other number on another CSR with no listing. Kim asked if the listing would apply to the BTN. Kim also asked if the phone book would have a different listing.

Anne Pent-Qwest said that they would.

Kim Isaacs-Eschelon asked if a new account number could be requested as non- published.

Anne Pent-Qwest said no and that the customer would have to make a change.

Leo Dimitriatis-AT&T asked if the listings still belonged to Qwest in the scenario discussed above with the 4 remaining TNs.

Anne Pent-Qwest said that the listings do belong to Qwest. She said that the decision was made not to assume and that the end user would have to call Qwest to make a change.

Chris Terrell-AT&T said that she understood that Qwest would use the next logical number on the CSR for the new BTN. She asked how the customer would know.

Leo Dimitriatis-AT&T said that after the BTN was migrated the BCN will have that information and the customer can look at the CSR and that the rules will be reflected in the CSR. He asked how Qwest would handle the scenario where you have 5 lines migrating to AT&T on one order and the customer wants to disconnect the TN that happens to be the BTN.

Anne Pent-Qwest stated that you can designate if the customer has a preference for the main line or the next number to be the BTN and this information will be on the FOC.

Leo Dimitriatis-AT&T asked about listing treatment with using the next logical number.

Anne Pent-Qwest stated since you own the account in this instance the listing would have to ‘O’ and ‘I’ ‘d for the remaining TN.

Chris Terrell-AT&T asked if this was done on a disconnect order.

Anne Pent-Qwest said that this would be done on a partial C order with an ACT of ‘C’.

Leo Dimitriatis-AT&T said that on the change order for the account they could include the listing. He also said that if they don’t use the FOC, they will assume that Qwest has used the next logical line number and that no listing treatment is applicable.

Chris Terrell-AT&T asked if Qwest would do anything with the listing for the TN.

Anne Pent-Qwest said that if the main TN is disconnected the listing will stay the same.

Leo Dimitriatis-AT&T stated that they do support this solution. He said that Verizon Business uses the next logical number and automatically assigns the main listing when a BTN is disconnected.

Anne Pent-Qwest said that is what we will do and said that if you want a change to let us know.

Leo Dimitriatis-AT&T said that with this solution there are no changes for AT&T except to let their operations people know.

Chris Terrell-AT&T said that the ‘NAN’ field is a good thing and that they would prefer to let Qwest know what they prefer.

Leo Dimitriatis-AT&T asked if this process was documented.

Anne Pent-Qwest stated that this process is documented in various PCATs and will be updated with the Product/Process CR.

Lynn Stecklein-Qwest stated that this CR will be discussed in the March Product/Process CMP Meeting on March 21, 2007.

10/31/06 Additional Clarification Meeting

Chris Terrel - AT&T, Kathy Lee - AT&T, Leo Dimitriatis - AT&T, Chuck Anderson - Qwest, Anne Pent - Qwest, Lynn Stecklein - Qwest Communications

Lynn Stecklein - Qwest stated that the purpose of this meeting is to further clarify this change request.

Chuck Anderson - Qwest asked if this request was associated with a migration request on a number that is a BTN that is disconnected between the time the conversion happens.

Leo Dimitriatis - AT&T stated there are 2 cases - the 1st is when a customer wants to disconnect the BTN that has a WTN. Leo asked what the process is for the WTN and how to obtain the WTN housing. He said that 2nd scenario is when you migrate a multi-line account with a WTN and BTN and the BTN migrates to Qwest and the WTN belongs to AT&T.

Chris Terrell - AT&T asked what if you have one BTN with multiple WTNs on the account - what is the BTN to WTN status.

Chuck Anderson - Qwest stated that he needed to investigate the WTN with the next highest sequence.

Leo Dimitriatis- AT&T asked what the CLEC needs to do when the BTN has been elevated. He said that they need to know what happens to the remaining WTNs and which WTN is elevated to BTN.

Chuck Anderson - Qwest said that we just need to figure out the notification or disclosure process when the BTN has been taken off the account and which WTN becomes the BTN.

Leo Dimitriatis - AT&T asked what happens if you have 1 BTN and 1 main listing.

Chuck Anderson - Qwest stated that we need to talk with the Listing SME. He said that this may not require system work and would just be a process change.

Chris Terrel - AT&T stated that they would prefer an enhancement without system work.

2/16/05 Systems CMP Meeting - IMA 18.0 Candidate Discussion

Chris Terrell-AT&T stated that they would like to leave this CR open and is a medium priority for AT&T.

7/22/04 CMP Systems Meeting

Jill Martain/Qwest stated that Qwest would distribute the ballot on July 27th, it is due back to Qwest on July 30th, and Qwest would email the initial prioritization list to the CLECs on August 3rd. There were no questions.

Donna Osborne-Miller/AT&T stated this was low for AT&T.

8/21/03 CMP Systems Meeting

Phyllis Burt/AT&T stated that AT&T’s interest was moderate.

4/17/03 CMP Systems Meeting Donna Osborne-Miller/AT&T reviewed the description of change. John Gallegos/Qwest stated that the LOE is 1700 to 2800 hours for this request. The status will be changed to presented.

4/3/03 Clarification Meeting Introduction of Attendees Phyllis Burt - AT&T, Donna Osborne-Miller - AT&T, Curt Anderson- Qwest, Berkley Loggie - Qwest, Joan Pfeffer - Qwest, Shon Heiger, John Gallegos - Qwest, Mark Early

Review Requested Description of Change When a CLEC migrates a multi-line account and then sometime later the customer requests to disconnect the main number, this must be supported through system or operation. Disconnecting the BTN on a Muliline account means that a new Account Number may have to be assigned and these rules must be known. One of the remaining numbers may have to attain BTN status with Directory Listing treatment applied to it.

Confirm Areas & Products Impacted UNE-P Pots, IMA Common

Confirm Right Personnel Involved All appropriate personnel were involved in the clarification call.

Identify/Confirm CLECs Expectation When a BTN has been disconnected, one of the remaining TNs will have to be the BTN.

Identify any Dependent Systems Change Requests NA

Establish Action Plan This change request was a walk on in the March CMP Systems Meeting and will be presented in the April Meeting by AT&T.

4/1/03 Clarification Meeting Customer not present, meeting rescheduled.

3/20/03 CMP Systems Meeting Donna Osborne-Miller/AT&T presented the CR. Phyllis Burt/AT&T said that she was not real familiar with this CR but thought that the description of change was self explanatory. If you lose the main number how do you get a new main listing. It currently doesn’t allow us to do a new main listing. Bonnie Johnson/Eschelon said that they have run into this with EDI. The answer is that when you migrate the BTN, regardless if you identified the new BTN you want, Qwest says that it’s an optional field. It is automatically processed as non-published. We have no say of what it should be and if the customer wants it any different they have to call Qwest Retail. Liz Balvin/WorldCom said that it sounds like the request is for after the fact. Connie Winston/Qwest noted that Qwest will schedule the clarification call and that this CR will be eligible for the 15.0 release Donna Osborne-Miller/AT&T suggested that AT&T send out the information regarding the clarification call to the other CLECs.

Open Product/Process CR PC090401-4 Detail

Description Of Change

Status History

Project Meetings

RE: CR Form #PCCR090401-4

The intent of this change request was to clarify Qwest’s LNP process and to address any discrepancies in the information provided by their Denver Interconnect Center on August 15th, August 17th, August 24th and August 31st to AT&T. Qwest’s Denver Interconnect Center stated on multiple conference calls (to AT&T Broadband and to LNS) that calendar days, instead of business days, would be counted in the LNP process. Discussions with Qwest at the October 17th Product and Process CMP meeting clarified that Qwest uses business days.

AT&T understands this to mean that if a port is scheduled on a Friday or Saturday, Qwest will not jeopardize the end customer by closing the LSR or removing the switch translation any earlier than the next business day. Next business day is defined as the following Monday at 11:59 p.m. AT&T wants to clarify that holidays do not constitute a Qwest business day. Therefore, Friday, Saturday or Sunday ports would not be disconnected out of the switch until the following Tuesday at 11:59 p.m. if Monday is a designated holiday.

Qwest states that their Interconnect Centers have been advised and are aware of this process. The process states that the ten (10) digit unconditional trigger and switch translations associated with the end user customer’s telephone number will not be removed, nor will Qwest disconnect the customer’s billing and account information, until 11:59p.m. (local time) of the next business day after the due date.

AT&T interprets this to mean Qwest has provided documentation and training to the typists at Sierra Vista, Phoenix, and Duluth Centers, both Interconnect Service Centers, the RCMAC center and any additional Qwest centers directly related to the LNP process. AT&T Broadband will reference Qwest’s letter dated October 29, 2001 to restore loss of dial tone when it is a direct result of non-adherence to Qwest’s LNP process by any Qwest employee of these centers. AT&T further expects the duty supervisors to be well versed in this process and provide consistent action and information based on this process.

Sincerely, Terry Bahner AT&T Local Services – LSAM Western Region

CC: Sharon Van Meter Tim Boykin Donna Osborne-Miller Mitch Menezes

Friday, September 21st, 2001 Alignment/Clarification Meeting

Donna Osborne-Miller, dosborne@att.com,AT&T Terry Bahner, tbahner@att.com, AT&T Kathleen Stichter, klstichter@eschelon.com, Eschelon Telecom Linda Miles, llmiles@qwest.com, Qwest Russ Urevig, rurevig@qwest.com, Qwest Joan Wells, jmwell2@qwest.com, Qwest Kate Spry, kspry@qwest.com, Qwest Ric Martin, rhmart2@qwest.com, Qwest

Introduction of Attendees Donna, Terry, Kathy, Linda, Russ, Joan, Kate, and Ric Review Requested (Description of) Change Clarify process to complete LSRS the day after due date. Confirm Areas & Products Impacted Areas: Ordering and Billing Products: LNP Confirm Right Personnel Involved Joan is the ‘owner’ of this CR and will be the point of contact for future problems of this nature until the root cause is established and draft response issued. After the clarification meeting, it was determined that Linda and Russ will not need to be involved in this CR. Kate will coordinate all necessary clarification meetings, complete meeting minutes, and review, forward, and store necessary documentation to database. Identify/Confirm CLEC’s Expectation AT&T has asked Qwest to clarify the process for completing LSRS the day after due date. Per AT&T, “Qwest notified the CLEC community LSRS would complete orders day after at 11:59 p.m. of install date to coincide with disconnect in switch. Qwest escalation center is stating that orders can start closing as early as 3 p.m. with the possibility of closing even sooner with disconnect to follow. Interconnect has stated that Qwest determines that there is a large volume of orders to close, they can decide a random time to start the process. AT&T would like to understand why this time frame fluctuates if the closing of these orders causes the disconnect in the switch to shift to an earlier time. AT&T is requesting a flow chart or documentation explaining and listing the backend systems for this process.” Identify any Dependent Systems Change Requests No related system CR’s were identified Establish Action Plan (Resolution Time Frame) Joan will clarify this process via a flowchart and written formal response draft. She will forward this documentation to Kate by the morning of 10/5/01. Kate will review and forward this information to Michael Belt to store in the CR database by 10/8/01 for CLEC review. This information can then be reviewed and discussed by the CLEC Community at the October CMP Meeting. Donna and Terry can view this information on the CR database and this CR can then be reviewed and discussed by the CLEC Community at the October CMP Meeting. Corrections/updates can then be made at that time.

CenturyLink Response

November 6, 2001

Ms. Terry Bahner Ms. Donna Osborne-Miller AT&T Communications

This letter is in response to CLEC Change Request PCR090401-4, dated September 4th, 2001, title of change: Clarify Qwest’s process on completing LSR’s day after due date. This Change Request pertains to the implementation of the new LNP process involving stand alone LNP port out service order requests.

Description of Change as noted in CR: QWEST notified CLEC community LSRS would complete orders day after at 11:59 pm of install date to coincide with disconnects in switch.. Qwest escalation center is stating that orders can start closing as early as 3pm with the possibility of closing even sooner with disconnect to follow. Interconnect has stated that if Qwest determines that there is a large volume of orders to close, they can decide a random time to start the process. AT&T would like to understand why this time frame fluctuates if the closing of these orders causes the disconnect in the switch to shift to an earlier time. AT& T is requesting a flow chart or documentation explaining and listing the backend systems for this process.

Implementation of this Qwest business process change was included in the IMA 8.0 release and was deployed effective August 20th, 2001.

The change is as stated: The ten (10) digit unconditional trigger and switch translations associated with the end user customer’s telephone number will not be removed, nor will Qwest disconnect the customer’s billing and account information, until 11:59p.m. (local time) of the next business day after the due date. Internal Qwest systems have been adjusted to accommodate this process change.

* Order completion and disconnect of translation’s will not occur prior to 11:59 p.m. the next business day following the due date.

* The subscription date to ASMS is sent to match the CLEC requested due date as available per the standard interval guide.

* The FOC is sent and matches the ASMS subscription date requested by the CLEC as available per the standard interval guide.

* An effective billing date to discontinue account billing is added to the order to match the actual port subscription date as requested by the CLEC and as available per the standard interval guide.

* Additional notification and a reminder of this current process was sent to the Interconnect Center’s through an internal communicator dated 10/29/01. The title was “Qwest response to CLEC questions concerning the current LNP Port Out process of holding switch translations and order completion until the next business day at 11:59pm.” * The process agreement is as stated: The ten (10) digit unconditional trigger and switch translations associated with the end user customer’s telephone number will not be removed, nor will Qwest disconnect the customer’s billing and account information, until 11:59p.m. (local time) of the next business day after the due date.

For due date changes or cancellation’s on existing LSR’s the following process should be followed:

Due Date Changes * You must notify Qwest via LSR supplement or notification to the ISC if you require a DD change for your port activity * Notifications of DD changes via a LSR supplement should be made as soon as possible on the DD and prior to 8:00 PM Mountain Time. * Late notification of DD changes will require that you call the ISC prior to 12:00 noon on the day after the DD (in the end-users' time zone) and issue a LSR supplement via IMA or IIS to confirm the request. If the port due date falls on a Saturday, the CLEC should notify the ISC no later than the following Monday by noon of the DD change. * Late DD change notifications after 12:00 noon the day after the DD, will require you to contact the Call Center Representative at 888-796-9087 to initiate an escalation ticket for these late changes. The CLEC should also issue a LSR supplement via IMA or IIS to confirm the request. The CLEC should also issue a LSR supplement via IMA or IIS to confirm the request.

Cancels * You must notify Qwest via LSR supplement or notification to the ISC if you require a cancel of the port activity. ? Notifications of DD cancels via a LSR supplement should be made as soon as possible on the DD and prior to 8:00 PM Mountain Time. * Late notification of DD cancels will require that you call the ISC prior to 12:00 noon on the day after the DD (in the end-users time zone) and issue a LSR supplement via IMA or IIS to confirm the request. . If the port due date falls on a Saturday, the CLEC should notify Qwest no later than the following Monday by noon of the cancellation. * Late cancel notifications after 12:00 noon the day after the DD will require you to contact the Call Center Representative at 888-796-9087 to initiate an escalation ticket for these late cancels. The CLEC should also issue a LSR supplement via IMA or IIS to confirm the request.

Qwest Interconnect Service Center hours of operation to support the functions described above are: 6 AM to 8 PM Mountain Time, Monday-Friday 7 AM to 5 PM Mountain Time on Saturday

With the implementation of this new process, the CLEC is still responsible for notifying Qwest if they are unable to meet their requested port due date. Service order completion and disconnect of switch translation’s are not scheduled to occur anytime prior to the 11:59 p.m. time frame the next business day following the due date. However, the port subscription message was sent for the initial CLEC desired due date and changes or cancellation’s must occur as outlined above or as noted in the supplement information listed in the Product catalog.

Sincerely,

Joan Wells Process Manager Local Number Portability

CC: Margaret Bumgarner Lorna Dubose Constance Overly Kate Spry

Open Product/Process CR 5582295 Detail

Description Of Change

Status History

Project Meetings

Subject: CR # 5582295 Update Date: Thu, 11 Apr 2002 09:15:41 -0600 From: "Todd Mead" Organization: Qwest Communications International, Inc. To: Terry Bahner

Terry, Please see below in response to your question about PCAT update:

"The LEFV fid alone is not necessarily cause for the CLEC to be sent a jeopardy notification. Only if the FOC has been sent to the CLEC would we send a jeopardy notification. And the current process of jeopardy after FOC states that in all conditions where an FOC is sent and Qwest has found a problem with the request, we will follow the jeopardy after FOC process. No matter what, if it has been FOC'd and Qwest finds a problem with the LSR, we will follow the jeopardy after FOC process.

Thanks

Todd

03/06/02 Letter from AT&T offering a counter proposal to the matrix Qwest has presented for CR5582295

1875 Lawrence St. Denver, CO 80202-1847

March 6, 2002

Todd Mead CMP Manager Qwest Communications 1801 California Street Denver, Colorado 80202

RE: CR5582295, SCR092601, & Matrix

Dear Todd:

AT&T still has concerns surrounding the interim manual process of how and when Qwest issues a jeopardy after sending the CLEC a FOC for an LSR. We have two specific concerns. This first is the introduction of the Application Date (APP) as a tool to determine AT&T Broadband’s due date when orders are issued a jeopardy condition. And the second is the subjective use of the term "renegotiated".

AT&T believes Qwest could proactively minimize disruption to the customer if Qwest would maintain the CLEC ordered due date more frequently than is possible with the Qwest proposal.

AT&T proposes the following changes to achieve this objective:

1. Jeopardy Condition identified within 24 hours then original FOC’d due date will be maintained - Identified within 24 hours after LSR submission by CLEC - CLEC notified within 24 hours after LSR submission by CLEC - Jeopardy cleared within 4 business hours

Jeopardy Condition identified within 24 hours then original FOC’d due date will be renegotiated - Jeopardy not cleared within 4 business hours

2. Jeopardy Condition identified more than 24 hours then original FOC’d due date will be maintained - Identified more than 24 hours after LSR submission by CLEC but before the due date - CLEC notified more than 24 hours after LSR submission by CLEC but before the due date - Jeopardy condition is Qwest’s fault and CLEC clears the condition within 4 business hours

Jeopardy Condition identified more than 24 hours then original FOC’d due date will be renegotiated - Jeopardy condition is CLEC’s fault and CLEC clears the condition within 4 business hours - Jeopardy condition is not cleared within 4 business hours

3. Jeopardy condition identified on or after the due date - Qwest will immediately work with CLEC to resolve end user customer impact. No negotiated due date

AT&T would like written rules about the meaning of “renegotiated”. AT&T believes the renegotiated interval should have minimal customer impact and never exceed the standard service interval for LNP.

AT&T believes Qwest has reasonable time to identify all errors during the first 24 hours. If an error is discovered and the error is related to a Qwest CSR, a pending retail order or any error Qwest fails to identify, AT&T believes the FOC’d due date should be maintained. Our proposed changes define and clarify the process. We believe this will reduce misinterpretation of the process and provide a consistent response from Qwest during the escalation process.

AT&T appreciates Qwest extending the courtesy call to a third week. This allowed sufficient time for AT&T to verify the jeopardy was being received via EDI. It also provided sufficient time for AT&T to provide Qwest examples of when the process broke.

Sincerely,

Terry Bahner Supervisor AT&T Local Services Access Management Western Region 303-298-6149

Cc: Tim Boykin Sharon Van Meter Donna Osborne-Miller

02/22/02 Response e-mail from Qwest clarifying AT&T question on jeopardy and DD process for LNP

Subject: Re: CMP 2/20/2002: Action Item & Clarification Date: Fri, 22 Feb 2002 16:45:31 -0700 From: "Joan Wells" To: "Bahner, Teresa L (Terry), NCAM" CC: "Jill Martain" , Jill"

02:00 p.m. (MDT) / Friday 08 February 2002

Followup meeting to Investigate top reasons for error condition after FOC

Terry Bahner, AT&T Jonathan Spangler, AT&T Sharon Van Meter, AT&T Donna Osborne-Miller, AT&T Jill Martain, Qwest Joan Wells, Qwest Ric Martin, Qwest Michael Keegan, Qwest Christine Quinn-Struck, Qwest

Jill Martain presented the following historical values : Total LSRs submitted for AT&T in December for LNP was 15,121. Total Non-Fatal errors issued after FOC , 28. Of those 28, 13 were identified on the same day, 7 next day but within 24-hours, 8 after 24-hours.

Joan Wells discussed: The Service Interval Guide for Resale and Interconnection Services The Matrix for resolving Jeopardy Conditions and Effect on the DDD. The Qwest Ordering Screening Process The root cause for PON ZXDNV25275001 TN 303 463-0715 See attached PDF file "CR5582295 Interval Guide & jep matrix" which documents the above.

Joan Wells will revise the Qwest response to reference the discussion outlined in 2.2. The Qwest response will also indicate the desire by Qwest to work with AT&T to minimize changes to the AT&T FOC’d DD.

-

02:00 p.m. (MDT) / Thursday 31 January 2002

Investigate top reasons for error condition after FOC

Terry Bahner, AT&T Jonathan Spangler, AT&T Sharon Van Meter, AT&T Donna Osborne-Miller, AT&T Tim Boykin, AT&T Vernise York, AT&T Cynthia Linenberger, AT&T Ed Longstreet, AT&T Kerri Burke, AT&T Cheryl Moilanen, AT&T Scott Eicher, AT&T Jill Martain, Qwest Joan Wells, Qwest Ric Martin, Qwest Michael Keegan, Qwest Brandi Bentley, AT&T

Jill Martain provided a recap on the progress of CR 5582295 and Systems CR SCR 092601-1 stating we are still moving forward with a February 18 implementation. The process change will discontinue sending a non-fatal error notice after a FOC if an error condition is identified, and will send a jeopardy notice instead. If the error condition is identified within 24-hours, only a jeopardy notice will be sent. If it is after the 24th hour, a courtesy call (for LNP only) will also be made to notify the CLEC of the error condition. Clarification was made it is a courtesy call and the jeopardy notice is the official notification of the jeopardy condition. Jill further explained that if the jeopardy condition was responded to within 4-hours the orders would remain in the system and if no response was received the service orders would be canceled but the LSR would remain in a jeopardy condition for 30-business days. If at the end of 30-business days the LSR is still in a jeopardy status, the LSR would be rejected back to the CLEC..

Jill explained that the error report indentified several types of rejects. AT&T asked if Qwest had an idea of what the numbers were. Jill advised that she did not have time to review the details. AT&T asked for a listing of the areas of the error and the numbers. Jill explained that some problems came about when the order was pending disconnect then the Quality Checkers would notice a retail dissconnect that came through. She also indicated that some problems occur when there is a dfferent address then the one on the LSR.

AT&T asked if Qwest would honor the due date if AT&T issued their Sup. Qwest indicated that it was dependent on the time the Sup came in. Qwest clarified the process advising that when an error condition occurs after an FOC, Qwest will send a Jep notice, not a non-fatal error. The Jep would be sent back the same way the request was received (i.e. EDI, fax, etc.). Qwest explained that the LSR Order will stay in Jep status for 30 days. Qwest will only Jep the order in the first 24 hrs. On the 25th hour, Qwest will send the Jep and place a call. Qwest needs the Sup turnaround within 4 hrs and Qwest will respond in 24 hours after receipt of Sup. Qwest would issue an FOC, which would start the calculation over. AT&T advised that Qwest should still honor the due date if the Sup was issued within the time interval, especially if the Jep was due to a Qwest error. AT&T suggested that we have another meeting to address this question.

Joan Wells discussed the quality check process. A quality check typically takes place within the first day after the FOC. Qwest cannot commit to this timeframe due to potential volume and resource issues.

A question was raised on whether AT&T could have the Due Date. It was clarified that this would be only for LNP. Joan Wells indicated that she would have to go back to the team.

Qwest provided the root cause for the TN example that AT&T provided . The initial reject was due to a wrong address; however, that was corrected by AT&T Broadband. All following actions were the result of a Qwest agent mishandling this order after that FOC was sent. Joan Wells said this person was individually coached.

Action Plan Qwest will review the due date issue and revise its response to CR 5582295 as required. Qwest will pull historical data to identify the percentage of AT&T LSRs that are receiving an error condition after a FOC.. Qwest will set-up another meeting for Friday, February 8, 2002, from 2:00 PM to 4:00 PM. The manual process for all products associated with SCR 092601-1 is scheduled for implementation on 2/18

--

November 6, 2001 AT&T Reply to Final Response dated 10-24-01 Joan Wells Qwest LNP Process Manager

RE: CR Form #5582295

AT&T has stated in previous correspondence to Qwest and at the monthly CMP Product and Process forum the seriousness surrounding Qwest’s process to send a FOC then fatal reject it without notification to the CLECS. AT&T understands Qwest’s current process providing a 4-hour window for response to a non-fatal error notice. However, examples have been shared with Qwest on weekly calls where this process continues to fail. Therefore, AT&T expects Qwest to adhere to its commitment to allow a jeopardy notification after a FOC instead of a non-fatal error after a FOC as submitted under SCR092601-1. This was presented as a walk on at the October 18 Systems CMP meeting by Jill Martain as a candidate for the IMA 10.0 release scheduled for 2002. The CLEC community unanimously agreed to include the LNP product for this CR. Jill Martain concurred.

In regards to AT&T system changes, AT&T anticipated the need to update their IBICS system only after Qwest discounted the use of jeopardy codes on previous calls. When Qwest announced they would pursue using jeopardy codes (Loretta Huff calls August 31, 2001 and September 5th respectively) and informed AT&T that system changes were not required, AT&T did not pursue modifying IBICS since it is currently capable of handling jeopardy codes. AT&T OSS anticipates the upgrade to IMA 10.0 with SCR092601-1 to resolve this issue.

In the interim, AT&T expects Qwest to continue to follow its current 4-hour window process and make every effort to call AT&T Broadband before issuing a fatal reject. AT&T also expects Qwest to socialize this process with all centers directly involved with the LNP process with special emphasis on the Sierra Vista and Phoenix Centers and the duty supervisor in any Qwest Interconnect Center which provisions AT&T Broadband LSRs.

AT&T does not believe this CR has been fully addressed until SCR092601-1 can be implemented or Qwest discontinues its process of fatal rejecting an LSR without CLEC notification.

Sincerely, Terry Bahner AT&T Local Services – LSAM Western Region

CC: Sharon Van Meter Tim Boykin Donna Osborne-Miller Mitch Menezes

September 14, 2001

Lorna Dubose LNP Wholesale Product Manager Qwest Communications 1801 California Street Denver, Colorado 80202

RE: Your letter dated September 5, 2001 regarding change request 5582295 – Cancel after the FOC

Dear Lorna:

Qwest has forwarded two proposals to AT&T. The first was discussed with Loretta Huff from Qwest on Friday, August 31st. The second proposal, Qwest letter sent September 5th, was based on Qwest changing its process and AT&T making changes to IBICS. Ms. Huff, in a conference call, indicated to the CLEC community that Qwest would utilize jeopardy codes on local service requests to alert the CLEC community when an LSR is rejected.

Qwest has taken an action item to internally review which process will be the final resolution to CR 5582295. AT&T has stopped all plans to augment its EDI system based on Ms. Huff’s proposal. AT&T believes the CR has not been sufficiently addressed. Please let me know when Qwest would like to schedule a conference call to discuss the final resolution for CR 5582295.

Sincerely,

Terry Bahner Supervisor Local Services Access Management Western Region

CC: Tim Boykin Sharon Van Meter Mitchell Menezes

Internal Response Clarification Meeting (9/10/01 3:30 p.m.)

Attendees: Joan Wells, Mark Coyne, Jill Martain, Todd Mead, Michael Buck

Mark and Jill explained the context of the Loretta Huff process. Joan provided information regarding Qwest response provided to AT&T. It was determined that the already provided Qwest response was probably accurate and not affected by the Loretta Huff response. However, Joan took an action item to review the Loretta Huff process. Following the review, Joan will update the CR response as necessary.

Action Items:

- Jill Martain to provide Joan Wells with the Loretta Huff process given to the CLECs - Joan Wells to review process and update CR response as necessary (target due date: 9/26/01)

September 7, 2001 2:15 p.m. Attendees: Terry Bahner (AT&T), Donna Osborne-Miller (AT&T), Sharon Van Meter (AT&T), Lorna Dubose (Qwest), Joan Wells (Qwest), Michael Buck (Qwest), Todd Mead (Qwest) Before the Qwest response was presented AT&T indicated that the information contained in the response was contrary to information presented in another meeting held on September 6. Because of this inconsistency, AT&T requested that Qwest clarify the response before AT&T would accept it. Terry Bahner did confirm that the incidence of this situation (i.e. rejection of LSRs after FOC) had been much reduced since installation of IMA 8.0. However, Terry indicated that she was aware of a few situations where an LSR was rejected after FOC. Joan Wells and Lorna Dubose both reiterated that according to guidelines in the PCAT there were some situations in which rejects might occur after an FOC. To rule out system bugs or non-compliance with process Terry will provide examples to Lorna for investigation

Action Items: - Mike Buck (Qwest) to gather additional data from Judy Schultz (9/7) -- completed 9/7/01 - Mike Buck (Qwest) to schedule meeting with Loretta Huff (Qwest), Mark Coyne (Qwest), Joan Wells, and Lorna Dubose (9/10) -- completed 9/10/01 - Qwest to formalize single consistent response to this request (9/12) - Terry Bahner (Qwest) to provide Lorna Dubose (Qwest) examples of rejected requests after FOC (9/14)

Monday, August 27, 2001 1 p.m. Attendees: Terry Bahner (AT&T), Sharon Van Meter (AT&T), Lorna Dubose (Qwest), Michael Buck (Qwest), Todd Mead (Qwest) Terry confirmed that initial indications are that IMA 8.0 fix seems to be working; original problem has occurred only once since IMA 8.0 release. Further testing is still required, but Terry is please with the results. Terry will continue her efforts to confirm/test recent change and report to Lorna as necessary. Terry also provided further information on a second aspect for this CR. Concurrent with the change to IMA, another change was made to AT&T’s IBICS system. The IBICS system change required some coordination with Qwest systems that resulted in the involvement of Cim Chambers (among others). At this point, AT&T recognizes a system change is required in order to receive the final reject from Qwest. AT&T has asked its vendor to supply the patch. The estimated time the patch will be ready is within 30 days. No systems changes have been made at this point in time to recognize a final reject after a FOC. Evaluation will begin once the patch has been installed. Like the changes to IMA 8.0, AT&T needs to evaluate the fix for its efficacy. Terry does not anticipate any further action needed by Qwest to support either the Qwest IMA changes or the AT&T IBICS changes. But until AT&T installs patch and completes confirmation testing Terry would like this CR to remain open. The time frame for observation is dependent on the system patch and Qwest’s newly adopted process to consistently call the Broadband centers prior to the final reject. Allowing AT&T Broadband a four hour window to change or cancel the LSR. Terry also expressed concern that AT&T’s new system, Launch Now, might have the same limitation that resulted in the changes to IBICS. However, Terry agreed that should problems be identified with Launch Now, she would open a new CR to address any Qwest involvement that might be required to support AT&T’s modifications to their system. Action Items: - Terry Bahner (AT&T) to provide Michael Buck with e-mail of Qwest contacts involved with IBICS issue (completed 8/28/2001) - Michael Buck (Qwest) to contact Qwest contacts involved with IBICS issue to confirm no further Qwest involvement needed (completed 8/30/01) - Terry Bahner (AT&T) to provide Lorna with any additional feedback on the results of AT&T confirmation testing for recent IMA changes. Terry to provide confirmation testing results feedback based on when the patch has been installed by AT&T’s vendor. The estimate is 30 days. Terry will provide Qwest a tentative date no later than September 19th CMP if patch has not already been installed. If no issues are identified as part of AT&T confirmation testing, CR to be subsequently closed.

LNP Meeting Notes - 8/13/01

Attendees: Lorna Dubose Matt Rossi Terry Bahner Donna Osborne-Miller

- AT&T getting rejects after FOC - They are not seeing the cancel notification/no phone call – cannot act on 4 hr interval for action - AT&T report that they are still receiving rejects - Terry to get examples of rejected LSRs from the Denver Center (PON numbers) to Lorna and Joan

CenturyLink Response

October 24, 2001 Wholesale Product/Process Ms. Terry Bahner AT&T Communications

This letter is in response to CLEC Change Request Form #5582295, dated June 6, 2001, title of change: Qwest does not cancel LSR after confirming FOC via pending “C’ order. This Change Request pertains to CLEC receipt of an order request cancellation, after having already received a Firm Order Confirmation (FOC). One resolution of this Change Request is specific to LNP Port Out and involved an update to a Qwest internal system. Qwest business process in the IMA 8.0 release was deployed effective August 20th, 2001. A check for pending orders on LNP Port Out requests will now be made, before the FOC is issued. If a pending order exists, the order is placed for manual review.

Additionally, Qwest examined our exception handling processes, including the notifications issued by Qwest in exception situations. The analysis revealed that current Qwest processes sometimes resulted in a non-standard series of notifications, such as an FOC after a reject notice or an FOC after an LSR completion.

To address concerns about exception handling processes, a call was held with a small number of CLEC’s on 8/31/01 to solicit their input on Qwest’s current process. After considering the input that was provided, Qwest is taking the following current actions:

In those cases where an error is discovered after an FOC is sent, Qwest will continue to follow its current process of following the non-fatal reject process. This process was documented in a notice issued on 7/26/01. The process was also documented in IMA EDI 7.0 Disclosure, Addendum #6, released on 8/30/01 and in IMA EDI 8.0 Disclosure, Addendum #1, released on 9/04/01. The current versions of the disclosure documentation states that the CLEC has 2 hours to respond to the non-fatal error notice.

A documentation notice will be sent 9/24/01 indicating that in the situation where an FOC has been sent in error, a 4-hour window will be given for responding to the non-fatal error notice. The EDI Disclosure document will be updated following resolution of the Change Management Process (CMP) Change Request (CR) described below. (Product Specific to LNP, Qwest will allow a 4-hour window for response to a non-fatal error notice, whether or not the FOC has been previously sent.)

Due to CLEC input during the 8/31/01 call requesting a different process be followed, Qwest has opened a CR through the Change Management Process (CMP) for CLEC consideration. The purpose of SCR092601-1 will be to address the process of sending jeopardy notifications instead of following the non-fatal reject process, once the FOC has been sent to the CLEC.

Currently there are internal system limitation’s involving the inability to send jeopardy notification’s in association with Local Number Portability service order requests. This system change is being looked into with completion of the change request SCR092601-1. There is no time frame available for this system change at this time.

Local Number Portability Service Order requests will continue to follow the non-fatal reject process until such time that a system change can be implemented.

Related to this Change Request, AT&T had anticipated the need to update their IBICS system. In response to this perceived need Qwest previously provided systems expertise and answers to questions in support of AT&T planning efforts for intended modifications to their IBICS system. In a status update meeting held on August 27, 2001 AT&T indicated that no further Qwest support was likely to be needed in support of AT&T’s IBICS system modifications. Furthermore, in a letter dated September 14, 2001, AT&T has indicated that all plans to augment its EDI systems have been halted. Should AT&T elect to make IBICS system modifications, Qwest believes that the necessary information has already been provided. The change to Qwest process (via IMA) and the potential change to AT&T’s IBICS system will need to be evaluated to ensure their effectiveness. This confirmation testing effort is the responsibility of AT&T. Qwest understands that AT&T will notify Qwest of any issues that arise during testing of these changes, should they occur. However, it is noted that upon implementation of the new jeopardy process after FOC, that AT&T system changes may no longer be necessary.

It is anticipated that no further Qwest involvement is necessary with regard to this Change Request and that further involvement will center around SCR092601-1.

Sincerely,

Joan Wells Process Manager Local Number Portability

CC: Mark Coyne Loretta Huff Michael Belt Jill Martain Lorna Dubose Margaret Bumgarner Michael Buck Todd Mead

Open Product/Process CR 5582078 Detail

Description Of Change

Status History

Project Meetings

To discuss order processing or status, including Firm Order Confirmation (FOC) and Service Order Confirmation (SOC) Notice, or to send associated information to the appropriate Center for processing, contact our Customer Service Centers. Based on the location of your end-user and the type of service you requested, Local or Access Services, our Service Center numbers are:

LSRs for Interconnect Resale Services, Asynchronous Transfer Mode (ATM) Services, Resale Frame Relay, Complex Resale, Centrex, Local Number Portability (LNP), Interim Number Portability (INP), Unbundled Local Loops and Elements: Location Contact Fax Hours of Operation Interconnect Service Center (ISC) 888-796-9087 888-796-9089 - FAX Monday-Friday 6:00 AM - 10:00 PM Mountain Time Saturday 7:00 AM - 6:00 PM Mountain Time

Qwest's Service Center is available to assist with your needs and, if additional assistance is required you will be transferred to the Customer Service Inquiry and Education (CSIE) Center until 8:00 PM MTN Time Monday – Friday. If additional assistance is required after 8:00 PM or on Saturday, Qwest will coordinate a call back or provide additional assistance as needed.

November 6, 2001

Joan Wells Qwest LNP Process Manager

RE: CR Form #5582078

AT&T understands Qwest has denied its request to expand Qwest’s Interconnect Centers hours as stated at the October 17, 2001 monthly CMP meeting. Qwest has agreed to change the CR status to “deferred” until the May 2002 Product and Process CMP meeting. AT&T has three areas of concern with Qwest’s response:

AT&T recognizes NeuStar’s standard hours of operation do not include Saturday or Sunday; however, Qwest’s own action of providing support on Saturday acknowledges Saturday as an important port day for AT&T Broadband regardless of NeuStar’s hours of operation. Therefore, AT&T believes NeuStar’s standard hours of operation is not a determining factor for Qwest in regards to expanding its hours of support for Saturday or specifically, Sunday.

Although “port activity may currently be scheduled for any desired frame due time”, there are switches within Qwest’s network that cannot be set mechanically. Does Qwest have edits built into its systems to reject or defer LSRs in this scenario? How can these switches be identified?

The last concern centers on the 24-hour AMSC level of support that Qwest has offered. In the October 17 Product and Process CMP meeting, Qwest stated that the technicians at the AMSC center do not have access to Qwest’s provisioning systems for LNP. Offering this center as an alternative to expanding the Interconnect Centers hours only delays and provides a false expectation to CLECS trying to resolve outstanding porting issues. Therefore, AT&T does not believe this as an acceptable alternative to our change request.

AT&T believes continued discussions need to take place as AT&T’s business volumes continue to grow with Sunday porting activity.

Sincerely, Terry Bahner AT&T Local Services – LSAM Western Region

CC: Sharon Van Meter Tim Boykin Donna Osborne-Miller Mitch Menezes September 7, 2001 2:15 p.m.

Attendees:

Terry Bahner (AT&T), Donna Osborne-Miller (AT&T), Sharon Van Meter (AT&T), Lorna Dubose (Qwest), Joan Wells (Qwest), Michael Buck (Qwest), Todd Mead (Qwest)

Qwest clarified some information regarding the forecast information provided by AT&T on 9/5; the forecast information provided is a projection of daily volume in all markets within Qwest territory

Action Items: - Lorna Dubose (Qwest) to communicate forecast information to Ken Beck and Toni Dubuque (9/10) - Lorna Dubose (Qwest) to provide Qwest response (9/14/)

###

Monday, August 27, 2001 1 p.m. Attendees: Terry Bahner (AT&T) Sharon Van Meter (AT&T), Lorna Dubose (Qwest), Michael Buck (Qwest), Todd Mead (Qwest) Terry explained that AT&T is interested in a window of Qwest support for LNP on Sundays after NPAC comes up. There is also a desire for Qwest support into the evening hours during the week. As an example, Terry cited the fact that AT&T gets orders until 10 p.m. (daylight time) in Salt Lake City. Lorna explained that Qwest center management could evaluate the possibility of expanded hours once the appropriate forecasting information is provided. The information to be included in the forecast: Expected volume by day and hour; any fluctuations expected (e.g. due to daylight savings time). Terry explained that she expected to be able to provide Qwest with forecast data by September 4. Lorna indicated that Qwest would attempt to examine forecast data prior to the September CMP meeting. Qwest will aim to provide a response prior to the September CMP meeting, but the formulation of a response might not be possible. Action Items: - Terry Bahner (AT&T) to provide Qwest with forecast volumes by 9/4/01 - Lorna Dubose (Qwest) to provide Qwest center management with forecast by 9/5/01 - Lorna Dubose (Qwest) to develop Qwest response by working with center management (tentative target: 9/7/01; with Michael Buck to organize walk-through meeting with AT&T during early week of 9/10/01)

###

LNP Meeting Notes 8/13/01

Attendees: Lorna Dubose Matt Rossi Terry Bahner Donna Osborne-Miller CR #5582078 – Expand Qwest’s interconnect center’s hours - Lorna currently waiting on response from the Qwest Interconnect Hours - Terry to give estimate to Lorna on call volume to expect

CenturyLink Response

Ms.Terry Bahner, Ms. Donna Osborne-Miller, AT&T

This letter is in response to CLEC Change Request Form #5582078, dated June 6, 2001. This Change Request pertains to a request by AT&T to Expand Qwest’s Interconnect Center hours to include a window of 6am MST to 10pm MST, Sunday through Saturday.

At this time, Qwest has no plans to expand the Interconnect Center hours. The following are some of the reasons that Qwest has made this decision: Currently, Qwest’s published normal hours of work are Monday – Friday 7am MST to 7pm MST. These hours are in parity in both Qwest Wholesale and Qwest Retail. Qwest Interconnect Center’s hours have already been previously expanded to 6am MST to 8pm MST Monday-Friday and 7am – 5pm MST on Saturday’s. NeuStar’s standard hours of Operation for the NPAC are Monday – Friday 7am – 7pm CST/CDT. The Qwest Interconnect Center hours currently exceeds this standard. Economic conditions currently do not facilitate an increase in head count to support the proposed increase in order activity and expansion. Lack of support from downstream systems, currently operating under the standard business hours. System maintenance necessities (i.e. scheduled down time) do not support expansion. Access to automated systems for order input is already available. Port activity may currently be scheduled for any desired frame due time in those switches where the ten digit triggers are set mechanically. 24-hour support is currently available through the Account Maintenance Support Center (AMSC) in handling repair issues that are a result of number portability.

At this time, Qwest will not expand its Interconnect Center hours further. Qwest had originally proposed that we review the expansion request again in one year, but at Clec request, Qwest has agreed to review again in six months.

Sincerely, Joan Wells Qwest LNP Process Manager

September 20, 2001

DRAFT RESPONSE For Review By CLEC Community and Discussion at October CMP Meeting Wholesale Product/Process Ms.Terry Bahner, Ms. Donna Osborne-Miller, AT&T

This letter is in response to CLEC Change Request Form #5582078, dated June 6, 2001. This Change Request pertains to a request by AT&T to Expand Qwest’s Interconnect Center hours to include a window of 6am MST to 10pm MST, Sunday through Saturday. At this time, Qwest has no plans to expand the Interconnect Center hours. The following are some of the reasons that Qwest has made this decision: Currently, Qwest’s published normal hours of work are Monday – Friday 7am MST to 7pm MST. These hours are in parity in both Qwest Wholesale and Qwest Retail. Qwest Interconnect Center’s hours have already been previously expanded to 6am MST to 8pm MST Monday-Friday and 7am – 5pm MST on Saturday’s. NeuStar’s standard hours of Operation for the NPAC are Monday – Friday 7am – 7pm CST/CDT. The Qwest Interconnect Center hours currently exceeds this standard. Economic conditions currently do not facilitate an increase in head count to support the proposed increase in order activity and expansion. Lack of support from downstream systems, currently operating under the standard business hours. System maintenance necessities (i.e. scheduled down time) do not support expansion. Access to automated systems for order input is already available. Port activity may currently be scheduled for any desired frame due time in those switches where the ten digit triggers are set mechanically. 24-hour support is currently available through the Account Maintenance Support Center (AMSC). At this time, Qwest will not expand its Interconnect Center hours further. Qwest will review this expansion request again in one year.

Sincerely,

Joan Wells Qwest LNP Process Manager

CC: Lorna Dubose Judy Schultz Margaret Bumgarner Michael Buck Todd Mead

Open Product/Process CR PC062603-03 Detail

Description Of Change

Expected deliverable: Adoption of SBC process relative to Business Rules Clarification and event notificattionupdates through the Addendum process

Status History

Project Meetings

06/16/04 June CMP Meeting Donna Osborne-Miller with AT&T said that AT&T is migrating to 15.0 and the business partners submitted questions to the Q&A process and responses were received. The Qwest responses asked that the questions be submitted through the external documentation process and the response was sent within 14 days. Regina Mosley is not on the call today and is available tomorrow to discuss during the systems meeting. Randy Owen with Qwest said that the questions submitted were not determined to be related to EDI. Liz Balvin with MCI said there were USOC driven questions and the business rules are not in the EDI disclosure. This CR will remain in CLEC Test status.

05/19/04 May CMP Meeting Randy Owen with Qwest said that the CR is in CLEC test with 15.0 and that we are waiting for feedback. Carla Pardee from AT&T said they would start 15.0 in June. Randy asked if they could look at other CLECs information. Amanda Silva with VCI said there was a business rule for conversion on TN and the business rule is there but got rejected. There was supposed to be an event notification regarding the work around. Randy took the two trouble ticket numbers and will provide information at Thursday’s meeting. Liz Balvin with MCI said she attended one of the conference calls and has recommendations for improvement: 1) Highlight in the ticket that a conference call will be taking place. Put in bold type. 2) On the call Qwest should bring forth what the changes were, what it is changing from and what is it changing to. Unless you have the event notification during the call it is hard to understand what is changing. Add what interface is impacted by this change. Randy said he would take this back and can probably accommodate the request. Bonnie Johnson with Eschelon said this is AT&T’s CR and they could be viewing the CR differently than Qwest. This CR should be allowed to go into a different status. Eschelon had submitted a CR to change the CMP document to add a re-open status and Qwest voted no. (Begin Bonnie’s comment) Bonnie said that Eschelon will not be closing CR’s until we go into the release that the CR was implemented in. Bonnie recommended that Qwest and the CLECs find a status that appropriately reflects this situation. (end Bonnie’s comment) Linda Sanchez-Steinke said that the CR is not ready to be closed. This CR will remain in CLEC Test status

04/21/04 April CMP Meeting Randy Owen with Qwest advised that we have held conference calls with the release as a trial and we are drafting the implementation notification that will include a comment cycle and plan to have the notification out at the end of this week. Donna Osborne-Miller asked for an update on the action item opened for the escalation process. Randy said that this was related to the question log and he was still researching the action item on the system side. This CR will remain in CLEC Test status.

03/17/04 March CMP Meeting Randy Owen with Qwest said that the combined question log will be provided with 15.0 and two or three event calls have taken place. Donna Osborne-Miller said that discussion on the wrap-up of the global action items would take place during the Systems meeting tomorrow. Phyllis Burt with AT&T said she would provide feedback on the question and answer log and the event log. This CR will move to CLEC Test status. -- Thu 2/19/04 3:59 PM From: Sanchez Steinke, Linda To: 'Osborne-Miller, Donna, NKLAM' Subject; RE: Phyllis's items for documentation

Thank you Donna, I forwarded to Beth Foster, Kyle Kirves, and Randy Owen.

Linda Sanchez-Steinke 303-382-5768

Thu 2/19/04 2:55 PM From; Osborne-Miller, Donna, NKLAM [dosborne@att.com] To: Sanchez Steinke, Linda cc: New Cr, Cmp Subject; Phyllis's items for documentation

Hi Linda, 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 categories.

thank you, Donna

Attachment Category breakdown based on IMA Appendix Categories for Collective Q&A Migration

A.1 ADDRESS VALIDATION A.2 APPOINTMENT RESERVATION A.3 TN APPOINTMENT CANCELLATION A.4 CONNECTING FACILITY ASSIGNMENT A.5 CUSTOMER SERVICE RECORDS A.6 DESIGN LAYOUT RECORD (DLR) RETURN A.7 FACILITY AVAILABILITY QUERY A.8 LISTINGS RECONCILIATION A.9 LOOP QUALIFICATION A.10 MEET POINT A.11 RAW LOOP A.12 SERVICE AVAILABILITY A.13 TELEPHONE NUMBER ASSIGNMENT B.1 END USER B.2 LOCAL SERVICE REQUEST C.1 CENTREX RESALE SERVICES C.2 DIRECTORY LISTING C.3 DID RESALE SERVICE C.4 HUNT GROUP INFORMATION C.5 LOOP SERVICE C.6 LOOP SERVICE WITH NUMBER PORTABILITY C.7 NUMBER PORTABILITY C.8 PORT SERVICE C.9 RESALE C.10 RESALE FRAME RELAY C.11 RESALE PRIVATE LINE C.12 RESALE SPLIT C.13 UNE CENTREX 21 (P OR STAR) SPLIT D.1 BILLING COMPLETION NOTICE D.2 COMPLETION RESPONSE D.3 DIRECTORY SERVICE CONFIRMATION AND ERROR DETAIL (DSRED) RESPONSE D.4 LOCAL RESPONSE D.5 PROVIDER NOTIFICATION D.6 SERVICE ORDER STATUS INQUIRY D.7 STATUS UPDATES D.8 PENDING SERVICE ORDER NOTIFICATION GENERAL/OTHER

02/18/04 February CMP Meeting 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 Balvin with MCI. Qwest took action items from that meeting and determined that meeting minutes will be provided and posted on the production support page along side the trouble ticket information which is currently populated on the Wholesale Web site. There was discussion regarding the timeframe of posting meeting minutes. Connie Winston with Qwest said they would post the minutes within 3 days and would strive to get completed as soon as possible. Connie also said that Qwest would capture necessary information, necessary 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 as those that are important to the CLEC. Connie suggested that the CLEC could provide a red-line of meeting minutes back to Qwest.

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

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 initially asked that the Disclosure documentation be updated when CLECs ask for clarification. Qwest would like to start a single Q&A log with 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 will provide needed clarification to documentation, a way to see documentation before the addendum is posted, and, will allow everyone to see 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 Implementation Teams, and included in the body of the Q&A document that will be posted.

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

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 is feasible. Donna Osborne-Miller said the Q&A log would be cumbersome if not broken out by fields.

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 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 Web Site, under OSS, IMA, EDI Documentation under the FAQ link. This CR will move to Development Status.

Fri 2/13/04 8:38 AM From; Linda Sanchez-Steinke To; 'dosborne@att.com' Subject; Updated Draft Response PC062603-03

Hi Donna -

As a follow up to yesterday's meeting regarding PC062603-03, attached is the updated draft response.

As we discussed, Qwest took the following action items; documentation addendum notification meeting minutes, question and answer log. We will give an update at the CMP meeting.

Thank you

Linda Sanchez-Steinke CRPM Qwest 303-382-5768

Meeting Minutes PC062603-03 Business Rules Clarification calls and event notification update through the Addendum process CMP Product & Process February 12, 2004 1-877-572-8687, Conference ID 3393947# 2:00 p.m. - 2:30 p.m. Mountain Time

PURPOSE

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 working session.

List of Attendees: Liz Balvin - MCI Regina Mosley - AT&T Phyllis Burt - AT&T Donna Osborne-Miller - AT&T Beth Foster - Qwest Randy Owen - Qwest Kyle Kirves - Qwest Lynn Stecklein - Qwest Linda Sanchez-Steinke - Qwest

MEETING MINUTES

Linda Sanchez-Steinke with Qwest welcomed all attendees and explained that Qwest scheduled this meeting to discuss changes that have been implemented to address this CR.

Kyle Kirves said that Qwest has made progress in the following areas; providing clearer information in the event notifications, revisited the event notification template, provide additional reasons behind severity issues, schedule conference calls on major impacts, and have initiated a CR to change the CMP document Section 12. A good example of Qwest’s effort to improve is the 2/13 conference call clarifying Event Notification 674340. AT&T said they appreciated these efforts.

Phyllis Burt with AT&T asked when clarification calls would take place. Kyle said they would take place for addendum changes. Phyllis Burt and Donna Osborne-Miller asked about meeting minutes from the clarification calls and Kyle said that minutes would be recapped in disclosure. Phyllis 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 this action item and respond at Product Process CMP.

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 will be a "change from" and a "change to" identification. Beth Foster added that the event notification would be in disclosure. Donna asked what the timing would be and Kyle answered that it may be two weeks after notification.

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 how the system behaves and didn’t want to wait until the next IMA release to get clarification updated.

Beth Foster suggested that documentation changes could be made via the documentation request website. Kyle stated the website is for everything but disclosure document changes. Randy added that many times documentation changes have coding changes and is concerned about that. Kyle said that documentation rejects are not representative of what the system is doing, for simple clarification that represents enhancement to documentation. Phyllis said that AT&T builds systems from the documentation and then it will become a production problem. 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 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 clarifications don’t get lost in the flow of the next release. Phyllis will provide examples of clarification questions and answers. Randy Owen said that Qwest had been considering a single Q&A log with all CLEC questions and clarifications. Liz added that the while Qwest might think clarification, it may be CLEC code impacting to have the update in the addendum especially from the EDI standpoint.

Qwest will provide an update to the open action items at the Product Process CMP.

01/21/04 January CMP Meeting Connie Winston with Qwest said that this issue has been worked through oversight and in the emergency meetings. Qwest can initiate a quick 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. Connie also said there are potential CMP language changes being proposed. Qwest will have an updated response in February. This CR will remain in Evaluation status.

12/17/03 December CMP Meeting Connie Winston with Qwest said this CR has been discussed in the Global Action Item meetings and expects that the Global Action Item meetings 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 of this CR.

11/19/03 November CMP Meeting 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 status.

10/15/03 October CMP Meeting 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 Evaluation status.

09/17/03 September CMP Meeting Connie Winston with Qwest provided an update and said that Qwest is reviewing what we can do better. Qwest has implemented calls to appropriate CLECs. When faxing becomes only solution Qwest is raising the severity level because there is no way for the CLEC to Communicate 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 definition of immediately. Connie said that at Event Notification closure Qwest is providing clearer information about what we did and what we are doing. Monica Avila with VarTec provided an example that when Qwest end user fields went from optional to conditional, it required coding outside 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 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 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 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 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 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.

Ad Hoc Meeting Minutes PC062603-03 Business Rules Clarification calls and event notification updates through the Addendum processs CMP Product & Process September 9, 2003 1-877-572-8687, Conference ID 3393947# 8:00 a.m. - 8:45 a.m. Mountain Time

PURPOSE

At the August CMP Meeting, participants agreed to hold a conference call to provide additional clarity and explain Phyllis Burt’s series of questions and statements about intent and meaning of the change request. The following is the write-up of the discussion.

List of Attendees: Julie Pikar - U S Link Jen Arnold - U S Link Kim Issaacs - Eschelon Donna Osborne-Miller - AT&T Phyllis Burt - AT&T Regina Mosley - AT&T Tom Hyde - Cbeyond Byron Dowding - Alltel Stephanie Prull - McLeod Randy Owen - Qwest Kyle Kirves - Qwest Linda Sanchez-Steinke - Qwest

MEETING MINUTES

The meeting began with Qwest making introductions and welcoming all attendees.

Linda Sanchez-Steinke with Qwest explained that the purpose of the meeting was to discuss and get further clarification about the AT&T CR PC062603-03. At the August CMP meeting, Qwest provided the draft denial response and Phyllis Burt with AT&T provided a counter proposal at the CMP meeting and asked that Qwest provide an updated response at the September meeting.

Donna Osborne-Miller with AT&T provided the denial response red-lined with a series of questions and statements written by Phyllis Burt. Kyle Kirves with Qwest had received the questions/statements. Phyllis Burt with AT&T said that the purpose of the CR was to provide clearer information in event notifications. Phyllis said that when event notifications are not clear, AT&T goes to their implementation manager and then 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 where questions can be asked. The issue is, if workarounds conflict with other business rules, then something else can fail. When AT&T 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 anything they would need to consider.

Phyllis said that the purpose behind the CR is to make sure there are not long gaps in time on production impacts. 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 linger and wait. AT&T wants to find other avenues to head off production problems.

Stephanie Prull with McLeod will not go back and look at Event Notifications for releases. McLeod will only do what is documented in the Disclosure and try to code to the business rules. McLeod stated that they should not have to implement to anything other than the business rules. If McLeod has a CR or UR when going in then will code to it.

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 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 and if they will receive rejects or jeopardies based on that impact.

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 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, they get communication of workarounds and then get rejects from the centers.

Phyllis and Stephanie both have concerns with the PCRM ticket 167601 (LNUM) and still can’t explain what the impacts are to their companies. 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.

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 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 are severity level 3 and should escalate to severity level 2.

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 would trigger discussions. With the technical escalation process, McLeod may raise an issue and AT&T may raise another issue, but discussion as a group would help.

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) 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 CLECs send an e-mail saying they want a call and if several CLECs sent an e-mail then Qwest should have a call.

Phyllis said that AT&T just requests calls on workarounds event notifications that change a business rules and documentation appears not to be working the way Qwest says it is working.

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 be worked into the addendum process.

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 release.

Phyllis discussed the documentation for service address validation when look at Qwest Documentation it appears copied from pre-order, order and SANO populated. Phyllis said that what needs to be done is a documentation change.

Linda asked if there were any other questions or additional information to provide. There were no additional comments or questions.

08/20/03 - August CMP Meeting Connie Winston with Qwest reviewed the draft response for this CR. Connie said that the information provided in the Event Notification Closure should include additional information that identifies the change, what was changed and what it was changed to. CLECs can also use the Technical Escalations to get more clarity in Event Notification. Donna Osborne-Miller with AT&T said that Phyllis Burt has provided documentation to the CLEC Community on Event Notifications and Donna will e-mail to Linda Sanchez-Steinke. Discussion continued when Connie Winston came into the CMP 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 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 will be moved to Evaluation status and Qwest will provide a revised response at the September meeting.

8/20/03 4:53 p.m. Sent by: "Osborne-Miller, Donna, NKLAM" To: Linda.Sanchezsteinke@qwest.com> cc: cmpcr@qwest.com> Subject: Phyllis's counterproposal to documentation CR Linda,

Here is the redline document Phyllis composed that I spoke with Connie about this morning.

Thank you, Donna

ATTACHMENT - PC062603-03 Response - FEEBACK.doc

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 impact to their business so that they can make the appropriate business decisions. 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 identify this problem in production today? Is QWEST currently rejecting these orders, sending jeopardies or are the orders completing successfully but not being provisioned correctly?

AT&T is requesting whenever a workaround is document that a clarification call to clearly communicate (1) the workaround in detail (2) the current impact to the CLECs order or service in production Example: (a) A notification for PCRM Ticket Number: 167601 has been issued several times. Initially it was not clear which Products were impacted. The 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 contact number provided on the notification. A QWEST TT has been open since Friday August 15.

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 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 wording required for the update to the Disclosure Document should be able to get these worked into the next Addendum update issued.

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 notification process only provides confusion due to the lack of in depth analysis

Ad Hoc Meeting Minutes PC062603-03 Business Rules Clarification calls and event notification update through the Addendum process CMP Product & Process July 31, 2003 1-877-572-8687, Conference ID 3393947# 9:00 a.m. - 9:30 a.m. Mountain Time

PURPOSE

At the July CMP Meeting, participants agreed to hold a conference call to discuss and gain input from CLECs on this CR. The following is the write-up of the discussions, action items, and decisions made in the working session.

List of Attendees: Liz Balvin - MCI Stephanie Prull - McLeod USA Regina Mosley - AT&T Phyllis Burt - AT&T Donna Osborne-Miller - AT&T Kyle Kirves - Qwest Linda Sanchez-Steinke - Qwest

MEETING MINUTES

Linda Sanchez-Steinke with Qwest read the change request description: AT&T requests that the Business Rules be opened up for clarification and that event notification updates be incorporated into the Addendum process. We seek Qwest adoption of SBC's process of a standard conference be established to address issues or concerns with the event notification and addendum updates. This SBC process includes conference call logistics: date, time and bridge number. They also send out a notification capturing the questions and answers provided during the conference call.

Donna Osborne-Miller with AT&T said there were copies of the e-mail handout provided at the July CMP meeting and asked if CLECs on the call 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 handout is also included in the body of the CR in the interactive report.

Phyllis Burt with AT&T provided an overview of the handout. Phyllis explained how the SBC process of event notification is different from the Qwest process. In the Qwest event notifications there is an e-mail address to send questions to. SBC’s process for appending business rules documentation includes a set conference call within 3-5 days of the notification. This set conference call time is convenient because it allows everyone to have an hour free on their calendar and the opportunity, during event notification, to discuss issues or questions and understand how business rules are impacted. The meeting minutes from the conference calls are included in the final notification and that allows everyone unable 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. 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 everyone would understand how to communicate and what the business rule is. In addition, sometimes CLECs get different answers from different people at Qwest and we are all trying to understand and seek clarity to the blocking issues.

Liz Balvin with MCI said the SBC process seems to be a more expeditious approach.

Kyle Kirves with Qwest asked if CLECs were talking about providing PCAT and LSOG updates or addendum and disclosure document impacts. Phyllis Burt with AT&T said the Qwest notification explains that something is happening but there is no addendum. Kyle Kirves asked if CLECs were looking for information in the disclosure notification and if they want the notification to provide what the documentation change will be. Phyllis said yes.

Linda Sanchez-Steinke with Qwest asked if there were any additional questions. There were no questions.

07/16/03 July CMP Meeting 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 concerns with event notifications and addendum updates. Donna said that they receive many event notifications from Qwest and the SBC process includes a clarification call 1-3 days after the notification to understand impacts. In addition, meeting notes are posted with a question and answer log. With EDI implementation 250-300 questions have been asked and some of the questions are not answered. Today, CLECs share their logs with other CLECs, MCI shares their log and McLeod shares their log. Judy Schultz with Qwest asked if the clarification call would take place 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 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 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 AT&T SMEs to Linda Sanchez-Steinke.

CLEC Change Request Clarification Meeting

2:00 p.m. (MDT) / Friday, July 11, 2003

1-877-260-8255 7616533# PC062603-03 Business Rules Clarification calls and event notification updates through the Addendum processs

Name/Company: Donna Osborne-Miller, AT&T Carla Pardee, AT&T Phyllis Burt, AT&T Regina Mosley, AT&T Kyle Kirves, Qwest Dan Busetti, Qwest Wendy Thurnau, Qwest Linda Sanchez-Steinke, Qwest

Introduction of Attendees Introduction of participants on the conference call was made and the purpose of the call discussed.

Review Requested (Description of) Change AT&T’s CR requests that Qwest adopt SBC’s process of a standard conference to address issues or concerns with event notification and addendum updates. Phyllis Burt with AT&T read the e-mail below at the Clarification Meeting for participants on the call:

(1) Several Event Notifications have come out that required discussion (see below). This CR is requesting that QWEST provide a clarification call 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 (11am Mountain/12pm Central/1pm Eastern). (a) The initial notification should include the addendum summary if impacts the disclosure documents. (b) The appropriate SMEs should attend the clarification call to answer any issues/concerns and a walkthrough of the appropriate documentation should be completed. (c) The closure notifications should include meeting minutes from the clarification call and the new addendum version should be posted on the Disclosure document website with a reference to the closure notification #.

Event Notification: 85434 IMA EDI GUI Initial Closure 061803 "Description of Trouble: CLECs may be experiencing difficulty processing POTS and UNE-P POTS orders on the Resale form when attempting to 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 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 requests for line and non-line level USOCs separately. Alternatively, CLECs may submit their orders, mark the request for manual handling, and provide instructions in the REMARKS."

Event Notification: 75800 IMA EDI GUI 060503 Initial-Closure Description of Trouble: CLECs may be experiencing difficulty processing conversion LSRs with a Block Activity (BA) = N (no change to existing blocking). Business Impact: CLECs may be experiencing difficulties retaining existing blocks during conversion. Qwest Proposed Work Around: CLECs should use the Feature Activity (FA) = V to recap blocking USOCs.

(2) QWEST/CLEC Q&A log clarification should be captured in the Addendum. There should be a monthly process to submit clarification updates. Followed by a standard monthly event notification and review as discussed above.

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 CLECs to refer to. SBC identifies a timeline when the answers to questions will be given and includes center personnel and OSS personnel in their clarification calls for notifications that impact CLECS.

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 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 other CLECS have learned has not been documented in the disclosure document.

Donna asked Kyle to provide an overview of the addendum process Qwest currently practices. Using the example above ( event 85434), Kyle described how this notification would justify an addendum. Specifically, he stated that, in this case, if the system were not functioning as documented, and the issue compromised the CLEC’s ability to process transactions, then a notification would be issued, and an addendum published. Situations that Qwest finds worthy of an addendum are those instances where the system is not functioning as documented. Clarification types of issues do not necessitate an addendum.

Confirm Areas & Products Impacted The area of this Change Request impacts addendum notifications.

Confirm Right Personnel Involved Qwest confirmed the correct personnel were on the call to resolve the CR.

Identify/Confirm CLEC’s Expectation AT&T’s expectation is that Qwest adopt the SBC process relative to Business Rules Clarification and even notification updates through the addendum process.

Identify any Dependent Systems Change Requests No systems change requests.

Establish Action Plan (Resolution Time Frame) AT&T will present this CR at the July CMP meeting.

To: Sanchez Steinke, Linda, Donna Osborne-Miller From: Burt, Phyllis S, CSCIO [phyllissburt@att.com] Sent: Fri 7/11/03 1:56 PM Subject: RE: Clarification call for the documentation CR Here's some additional information for our call today.

(1) Several Event Notifications have come out that required discussion (see below). This CR is requesting that QWEST provide a clarification call 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 (11am Mountain/12pm Central/1pm Eastern). (a) The initial notification should include the addendum summary if impacts the disclosure documents. (b) The appropriate SMEs should attend the clarification call to answer any issues/concerns and a walkthrough of the appropriate documentation should be completed. (c) The closure notifications should include meeting minutes from the clarification call and the new addendum version should be posted on the Disclosure document website with a reference to the closure notification #.

Event Notification: 85434 IMA EDI GUI Initial Closure 061803 "Description of Trouble: CLECs may be experiencing difficulty processing POTS and UNE-P POTS orders on the Resale form when attempting to 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 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 requests for line and non-line level USOCs separately. Alternatively, CLECs may submit their orders, mark the request for manual handling, and provide instructions in the REMARKS."

Event Notification: 75800 IMA EDI GUI 060503 Initial-Closure Description of Trouble: CLECs may be experiencing difficulty processing conversion LSRs with a Block Activity (BA) = N (no change to existing blocking). Business Impact: CLECs may be experiencing difficulties retaining existing blocks during conversion. Qwest Proposed Work Around: CLECs should use the Feature Activity (FA) = V to recap blocking USOCs.

(2) QWEST/CLEC Q&A log clarification should be captured in the Addendum. There should be a monthly process to submit clarification updates. Followed by a standard monthly event notification and review as discussed above.

Thanks,

Phyllis

CenturyLink Response

DRAFT RESPONSE For Review by CLEC Community and Discussion at the March 2004 CMP Meeting

Donna Osborne-Miller AT&T

SUBJECT: Qwest’s Change Request Revised Response - PC062603-03 "Business Rules Clarification calls and event notification updates through the Addendum process"

This response is a supplementary response to AT&T’s CR PC062603-03. Originally, Qwest denied this CR at the August CMP meeting. In 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 raised by the CLECs.

As a result of the discussions held at the Global Action Items Meetings (held on September 12, 2003; October 14, 2003; November 4, 2003; November 18, 2003; December 16, 2003), Qwest believes that the spirit of the original request has been met.

Qwest is using this document to supplement its response to the request dated February 11, 2004. Subsequent to the February 11 response, a 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 discussed. They were:

- AT&T requested that meeting minutes from any discussion around “Addendum to Disclosure Documentation” notifications be provided to the CLECs. Qwest committed to provide meeting minutes for these sessions no later than three (3) business days after the meeting. As the notification form itself is not designed to capture meeting minutes from the discussion, Qwest will record minutes from the meetings and publish them to the Production Support web site under the notification number. CLECs will have an opportunity to provide redlined edits to the minutes back to Qwest. - If any updates to the notification itself are required, Qwest will make those changes and republish the notification within one (1) day. - Regarding clarification to business rules, Qwest stated that it will continue to observe its established process for addendums and clarifications. Where “bugs” are identified, Qwest will publish a notification, documenting the bug, to be followed up by an addendum. For clarifications that do 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 and provide the log on the wholesale website where the EDI Documentation FAQ pages currently reside. This single Q&A log will provide needed clarification to documentation, a way to see documentation before the addendum is posted, and, will allow everyone to see what questions other CLECs have had and how Qwest has responded.

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 feedback.

Qwest maintains that the original request has been satisfied.

Sincerely,

Connie Winston Director, Information Technology Qwest

February 11, 2004

DRAFT RESPONSE For Review by CLEC Community and Discussion at the February 2004 CMP Meeting

Donna Osborne-Miller AT&T

SUBJECT: Qwest’s Change Request Revised Response - PC062603-03 "Business Rules Clarification calls and event notification updates through the Addendum process"

This response is a supplementary response to AT&T’s CR PC062603-03. Originally, Qwest denied this CR at the August CMP meeting. In 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 raised by the CLECs.

As a result of the discussions held at the Global Action Items Meetings (held on September 12, 2003; October 14, 2003; November 4, 2003; November 18, 2003; December 16, 2003), Qwest believes that the spirit of the original request has been met.

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 efforts to invigorate the notification process. Qwest maintains that by revisiting its process, providing training to notifications authors, and revising the notification template itself. Qwest itemizes its actions taken to address this CR as follows:

- Qwest is endeavoring to provide clearer information in the event notifications; and positive feedback from the CLECs indicates that Qwest has made significant progress on this front. - Qwest has a contingency plan in place to initiate calls with CLECs for high-profile, major impact event notifications and announce the conference 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 impact events, as stated. - As always, Qwest has worked to mitigate issues quickly; however, some production gaps will always exist due to prioritization of issues for resolution. - Qwest’s new internal process allows for event notification authors to work with the Interconnect Service Centers to generate appropriate, working workarounds that are approved by both Qwest and the CLEC. - Qwest now provides complete descriptions of impacts and error messages resultant from the issue, and has a separate place on the event notification form for capturing the error message verbatim. - Qwest now captures changes in documentation resulting in the body of the notification itself, in a “Change From:” and “Change To:” format. - As part of change request PC010704-1CM, Qwest is working toward language changes in the CMP document. The language change describes process improvements regarding notifications and documentation changes that cover some of the requests in this CR. Specifically, Qwest has updated the CMP document to demonstrate the following commitment regarding notifications, workarounds, and conference calls to CLECs:

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 documentation, and issue an event notification clearly defining the change.

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 documentation changes that may impact CLEC production coding, Qwest will issue an event notification, initiate a Technical Escalation, and request a joint meeting between Qwest and the CLECs in order to discuss the particular Patch Release. Qwest will notify CLECs of the joint meeting in which Qwest will review the Patch Release, the proposed solution, and the variables which affect the resolution. In all instances, these joint meetings are exempt from the five (5) business day advance notification requirement described in Section 3.0. At this joint meeting, Qwest and the impacted CLECs will discuss how the pending Patch Release will affect their code. Qwest and the impacted CLECs will discuss any potential resolution options and implementation timeframes. In the event that agreement cannot be reached between Qwest and the impacted CLECs regarding the type of Patch Release to be implemented, the parties will attempt to negotiate an appropriate workaround.

Qwest maintains that the original request has been satisfied.

Sincerely,

Connie Winston Director, Information Technology Qwest

September 10, 2003

DRAFT RESPONSE For Review by CLEC Community and Discussion at the September 2003 CMP Meeting

Donna Osborne-Miller AT&T

CC: Lynn Notarianni Beth Foster Kit Thomte

SUBJECT: Qwest’s Change Request Response - PC062603-03

This response is a supplementary response to AT&T’s CR PC 062603-03. Originally, Qwest denied this CR at the August CMP meeting. In 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 the points raised by the CLECs.

Qwest proposes moving this Change Request into Evaluation Status while we continue to investigate to provide workable solutions. Qwest would 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 October CMP Meeting.

Sincerely,

Connie Winston Director, Information Technology Qwest

August 12, 2003

DRAFT RESPONSE For Review by the CLEC Community and Discussion at the August 20, 2003 CMP Meeting

Donna Osborne-Miller AT&T

CC: Lynn Notarianni Beth Foster Kit Thomte

SUBJECT: Qwest’s Change Request Response - PC062603-03

CR Description: AT&T’s original change request states:

AT&T requests that the Business Rules be opened up for clarification and that event notification updates be incorporated into the Addendum process. We seek Qwest adoption of SBC's process of a standard conference be established to address issues or concerns with the event notification and addendum updates. This SBC process includes conference call logistics: date, time and bridge number. They also send out a notification capturing the questions and answers provided during the conference call.

Qwest Response: AT&T requests that Qwest adopt a regular call to address notifications issues that pertain to documentation changes or addenda to the Disclosure Documentation, and provide SMEs to answer the questions on the calls. In many cases, Qwest has not identified specific, word-for-word documentation impacts with the publication of the initial notification. Nor is that information available with the publication of the closure in all cases (in some cases, we are able to insert the Disclosure Documentation change into the closure, but this is typically a “documentation only” change notification). This is due to the fact that all documentation changes are reviewed by our System Requirements team. This System Requirements review is thorough and time consuming and would not be able to be completed during the timelines required by the notifications process in the CMP Document, Section 12.7. It involves research into field impacts, review of every instance to the field, cross-document impacts, systems and code impacts, and more. It is conducted over a period of time far greater than those involved in the notifications process.

Qwest maintains that both a.) the initial notification cannot include the documentation impacts and b.) the clarification call would not be able to clarify the documentation changes, as there would be insufficient detail available at the time of the proposed call. Moreover, the Qwest resources 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 effectively solve the problem, and would lengthen the time to resolve.

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 practice, because publishing these logs would require edits to every QA log for confidentiality.

Qwest's existing process of providing notifications with workarounds, business impacts, and channels for escalation works effectively, and allows for targeted responses to customer concerns. Publishing the clarifications made to each individual CLEC to all other CLECs does not add a demonstrable business benefit to the process, to the CLECs, and would require Qwest to assume an additional two to three resources to implement the solution AT&T is proposing. Qwest will, however, endeavor to enhance its notifications pertaining to Disclosure Documentation by including the change in the body of the closure notification. For Disclosure Documentation changes that would constitute an addendum, Qwest will include the documentation change in a “Change From—Change To” format similar to the change summaries in the addenda themselves.

Qwest respectfully denies this change request because the change does not result in a reasonably demonstrable business benefit and is economically not feasible.

Sincerely,

Connie Winston, Director, Information Technology Qwest

Open Product/Process CR PC103003-1CM Detail

Description Of Change

AT&T Proposed language: At the beginning of each month Qwest posts the forecast of the current month and two (2)months of system availability. The three (3) months system availability forecast notes planned changes to standard system availability. This forecast will be posted electronically in a calendar format.

Status History

Project Meetings

February 18, 2004 CMP Meeting Jim Maher-Qwest advised we held several CLEC meetings to discuss this CR. In those meetings, Qwest had agreed to monitor the Planned Outage process during January and February. During this time the three Planned Outage notices had a 19-day advance time frame. Qwest has developed a forecast document ‘Potential Planned Outages’. This was modeled after the example that ATT provided from Verizon. The intent of this document is that Qwest would post the outage dates that they believe are potentially going to occur. The final communication would occur as defined in the current CMP Process. There was a language change requested by ATT, but ATT agreed that was not necessary. Qwest will meet a 15-day advance notification for most of the potential planned outages identified in the CMP document. There may be some emergency outages that will meet the minimum requirements identified in the CMP process. Additionally Qwest will update and post the Planned Outage Forecast calendar to the web site quarterly. Qwest requested for ATT to withdraw the CR. ATT advised they are happy with the document / calendar. Carla Pardee – ATT said she didn’t get a chance to share the final document with other CLECs due to schedule issues. ATT stated they would withdraw the CR and that they believed the other CLECs will be happy with the forecast calendar.

February 17, 2004 Ad hoc meeting PC103003-1CM Planned Outage Notification

In attendance: Pat Moran - ATT Jim Maher- Qwest Carla Pardee – ATT Cindy Macy – Qwest

Cindy Macy – Qwest advised that we wanted to meet again to see how the process is working, to review the draft ‘Potential Planned Outage’ document, and determine if we should withdraw the CR as there would not be a language change, if the Potential Planned Outage calendar is acceptable.

Pat Moran – ATT reviewed the calendar and clarified her expectations. Pat reviewed the March 19, 20 and 21 date scenario. Jim explained that the Friday March 19 outage is less likely to occur, than the Saturday March 20 and Sunday March 21 outage. Pat suggested that we identify this on the calendar.

Jim reviewed that the January notices all provided 19 days of advance notification. IT is working on being more proactive with this process. Pat thanked Qwest for their efforts.

Pat advised that she would like Qwest to provide notification on the items identified on this calendar 15 days in advance. Pat explained that Qwest should be able to do this, as we are already aware of the potential and we should know if the release would impact system availability within 15 days. Jim agreed that this should be possible for items identified on the ‘Potential Planned Outage calendar’. Jim advised that there would not be a change to the language in the CMP, and this was agreed to by ATT. Jim clarified that there could be situations when Planned Outages required a shorter notification interval, and that these would be the exception based on the work Qwest had done. Pat stated she understood those exceptions could take place, but wanted as much advance notification as possible.

The group discussed whether we could withdraw the CR at the February CMP meeting. Carla and Pat Moran – ATT discussed the proposed solution and agreed that if Qwest published this calendar and updates it quarterly, and we provide 15 days advance notification for outages identified on this calendar, than they would agree to withdraw the CR.

Carla and Pat – ATT asked when we would identify 2005 dates. Jim advised this would be a rolling calendar so by the end of the 3rd quarter 2004 we should have a start on 2005 dates.

The team agreed to discuss at the February CMP meeting and withdraw the CR.

January 21, 2004 CMP Meeting Carla Pardee- ATT advised the last Planned Outage Notifications were sent out with much more advance notice and ATT is glad about this. Carla would like to have another meeting scheduled so we can discuss this with her internal representatives that are impacted by this process. Jim Maher – Qwest advised we have had 3 planned outages in January and all three notifications provided 19 days advance notice. Cindy Macy – Qwest will schedule another review meeting to discuss the CR and determine next steps.

December 17, 2003 CMP Meeting Cindy Macy – Qwest reported that we held a CLEC meeting on December 10 to discuss the Planned Outage Notification process. Qwest has met internally and we are reviewing the reasons why Planned Outage Notifications are occurring. Planned Outage Notification are at times related to issues that are uncovered during system releases. Qwest is reviewing the possibility of whether we could provide a quarterly notification that identifies when we think possible Planned Outages would be needed. We could publish that notification and then if the Planned Outage is truly needed we could use the existing Planned Outage Notification process to notify again. Qwest and the CLECs in attendance agreed to meet again in January. This CR will move to Development Status.

November 19, 2003 CMP Meeting Carla Pardee – ATT presented this CR. Pat Moran – ATT recapped the issues ATT has experienced due to short notice of planned outages. Carla advised that ATT would like Qwest to forecast out 90 days and publish their planned outages. This will give ATT advance notice and time to respond to system availability. ATT is looking for a list of scheduled down time 90 days in advance, and 60 days advance notice if there is any changes to that schedule. In mid-October ATT was given 2 days notice on additional downtime.

Clarification Meeting November11, 2003 1-877-552-8688 7146042#

PC103003-1CM Notification of Planned Outage Attendees Par Moran – ATT Liz Balvin – MCI Kim Isaacs – Eschelon Kyle Kirves – Qwest Carla Pardee – ATT Jim Maher – Qwest Randy Owen – Qwest Bonnie Johnson – Eschelon Cindy Macy – Qwest

Meeting Agenda: Action 1.0 Introduction of Attendees Attendees introduced 2.0 Review Requested (Description of) Change Cindy Macy – Qwest explained this CR is a request to change the Change Management Process document. This CR will require a vote at a monthly CMP meeting. Carla Pardee – ATT reviewed the change request. Carla explained she will be representing all Product Proces CRs. Donna will represent all System CRs. Carla explained they need to have the notification time increased when ever Qwest does planned outage notfications. Carla advised other ILECs provide 30-90 days notice. Qwest provides 2 days notice and this is not enough time to respond and prepare out centers. This causes problems. Jim Maher – Qwest attempted to explain the difference between what Qwest calls Scheduled Maintenance/Scheduled Outages, the OSS Release Calendar, Event Notifications and Planned Outage Notifications. Scheduled Maintenance is what takes place during regular scheduled downtime (night time down time). System Availability time is published on the OSS Hours of Availability document. System Release information is available on the Release Calendar and Release Notification documents. Planned outages are used for correcting system behaviors that are not causing immediate impacts to CLECs but they do need to be corrected quickly. Event Notification are used to notify the CLECs of system issues that impact the CLECs. The CLECs advised they believe Qwest has to know about scheduled downtime more than 2 days in advance. Jim explained part of the confusion is terminology as our scheduled downtime is down in the hours the system is not available. We do not notify about scheduled downtime as that is identified in the OSS Hours of Availability document. Planned Notifications are used to extend regular system downtime. Qwest uses the Planned Notifications to fix system issues that need to be addresses and cannot be accommodated in the regular system downtime. Pat Moran – ATT explained they receive hourly notifications from other ILECs on scheduled downtime. Carla – ATT advised she gets pre-notifications from Qwest and filters them to her people. Carla and Pat can review these notification to see if Pat needs to get additional ones.

ATT advised 2 days is not enough time to react to an extended downtime schedule. More detail on the functions impacted would be helpful as that would save us time in determining the impacts. Carla – ATT advised she would send the schedule that Verizon publishes as they publish downtime several months in advance. Bonnie Johnson – Eschelon asked if Qwest should really be using Event Notifications for these outages. Jim Maher – Qwest explained that these are not CLEC impacting so they are not really Event Notifications. They are correcting system behavior issues that are not currently visible to the CLECs. Qwest agreed we would meet internally to discuss and review data. Qwest would schedule an additional CLEC ad hoc meeting after we do some preliminary investigation. ATT will present this CR at the November CMP meeting. 3.0 Confirm Areas & Products Impacted Planned System Outage Notifications 4.0 Confirm Right Personnel Involved Correct people involved 5.0 Identify/Confirm CLEC’s Expectation For Qwest to provide additional time on Planned Outage Notifcations 6.0 Identify any Dependent Systems Change Requests none 7.0 Establish Action Plan (Resolution Time Frame) ATT will present the CR at the November CMP Meeting Qwest will schedule another ad hoc meeting after we complete our investigation.

Open Product/Process CR 5582212 Detail

Description Of Change

Status History

Project Meetings

Joan Wells Process Manager Local Number Portability

RE: CR Form #5582212 AT&T has submitted LSRs requesting the new 3-day service interval for Megabit service established after April 4th, 2001. At this point in time, only a small number of orders have been pushed out to the previous 5-day interval. AT&T considers this a coaching issue within Qwest and has socialized it with the typing centers and the Denver Interconnect center during our weekly conference calls. We will close this CR at the November 14th, 2001 Process and Product CMP meeting. Thank you for providing AT&T Broadband the tools to identify the appropriate USOCS. Sincerely, Terry Bahner AT&T Local Services – LSAM Western Region

CC: Sharon Van Meter Tim Boykin Donna Osborne-Miller Mitch Menezes

September 14, 2001

Lorna Dubose LNP Wholesale Product Manager Qwest Communications 1801 California Street Denver, Colorado 80202

RE: Your letter dated September 5, 2001 regarding change request 5582212 – 3-day interval Megabit Line

Dear Lorna:

AT&T believes Qwest has, in part, addressed CR 5582212. Going forward, any local service request to port an end-user’s telephone number that Qwest currently lists as a Megabit service qualifies for the 3-day interval if the Megabit service was installed with Qwest after April 4, 2001. AT&T would prefer this 3-day interval apply to all Megabit services regardless of the April 4th date.

Qwest has indicated AT&T Broadband can determine this date by reviewing the customer service record. AT&T Broadband has yet to determine if a Qwest install timestamp is present next to the USOC. AT&T would like Qwest to issue a unique USOC to help identify Megabit services installed after April 4th to assist in acquiring the 3-day interval. Your consideration to this request would be appreciated.

Sincerely,

Terry Bahner Supervisor Local Services Access Management Western Region

CC: Tim Boykin Sharon Van Meter Mitchell Menezes

###

September 7, 2001 2:15 p.m.

Attendees:

Terry Bahner (AT&T), Donna Osborne-Miller (AT&T), Sharon Van Meter (AT&T), Lorna Dubose (Qwest), Joan Wells (Qwest), Michael Buck (Qwest), Todd Mead (Qwest)

The Qwest response to this CR was presented; multiple clarification questions were asked and answered:

Q: Why is April 4, 2001 date important? A: This is the date when the process change for engineering megabit requests as non-design took place

Q: So the service offered did not change after April 4? A: Correct. Only an internal process was changed. The megabit service offered did not change.

Q: How should CLEC determine the customers’ install date? A: The necessary information should be available in the CSR (Customer Service Record). In Qwest internal systems both the USOC and the date are visible. Also, another option is to ask the customer when their service began.

Action Items:

- Terry Bahner (AT&T) to confirm that necessary information is available in the CSR visible to AT&T (9/13) - Terry Bahner (AT&T) to take Qwest response to AT&T stakeholders (9/13)

###

Monday, August 27, 2001 1 p.m. Attendees: Terry Bahner (AT&T), Sharon Van Meter(AT&T), Lorna Dubose (Qwest), Michael Buck (Qwest), Todd Mead (Qwest)

Terry clarified that the request for a reduced interval for LNP of megabit lines applies only to the ported number NOT the facilities. Terry indicated that AT&T had put in place procedures to inform customers of the impact to megabit facilities when AT&T ports only the number. Lorna indicated that she was working with appropriate product and process groups to address this request.

Action Items: - Lorna Dubose (Qwest) to formulate Qwest response by 9/5/01 - Michael Buck (Qwest) to organize a walk-through meeting with AT&T during late week of 9/3/01.

###

LNP Meeting Notes – 8/13/01

Attendees: Lorna Dubose Matt Rossi Terry Bahner Donna Osborne-Miller

- Lorna scheduled meeting with Megabit Product Manager on 8/16 - Status update will be given to Terry Bahner after that meeting

CenturyLink Response

This letter is in response to CLEC Change Request Form, number 5582212 – 3 day LNP LSR interval for Megabit Line, dated June 6, 2001.

Request: Qwest considers a megabit line as a complex and requires a 5-day interval. Since LNP is porting a number only and does not need the special facilities, it should be treated as a ported number and have a 3 day interval.

Response: After meeting with the Megabit Product Manager and the Interconnect Service Centers, it has been determined that as of April 4, 2001, Qwest implemented a new process for engineering Megabit service and it is now considered a non-design/simple service. Therefore, end-user customers that ordered Megabit service after April 4, 2001 had their service installed as non-design/simple service. This type of Megabit service can have a 3-day interval, which is the same as simple LNP orders today. However, if the Megabit end-user service was installed prior to April 4, 2001, the service is still considered a design/complex service. This requires service interval timeframes that allow Qwest systems to accurately remove the switch translations and process the order completion. Appropriate intervals for the Complex Product type will continue to apply. These intervals are shown in the LNP Product Catalog under Standard Intervals for LNP or the Service Intervals for Interconnection & Resale located at Qwest.com.

New USOC’s were developed for this network platform change. Effective 04-04-01, the Basic and Pro Services using the HRL++ USOCs will be grandparented and may not be used for ordering new services. The new Qwest DSL basic line 1FB/1FR, AFK/AFH Usoc’s are GRL++ and will be used after the 04-01-01 date.

The Select Service using HRC++ USOCs also, are no longer available for use.

Grandparented USOC’s are as follows: HRCA1, HRCA3, HRCA5, HRCWM & HRL51, HRL53, HRL55, HRL5M, HRLA1, HRLA3, HRLA5, HRLAM, HRLB3, HRLB5, HRLBM, HRLC1, HRLC3, HRLC5, HRLCM, HRLD1, HRLD3, HRLD5, HRLDM, HRLE1, HRLE3, HRLE5, HRLEM, HRLF1, HRLF3, HRLF5, HRLFM, HRLG1, HRLG3, HRLG5, HRLGM, HRLW1, HRLW3, HRLW5, HRLWM

New USOC’s are as follows: GRLA1, GRLA3, GRLA5, GRLAM, GRLB1, GRLB3, GRLB5, GRLBM, GRLC1, GRLC3, GRLC5, GRLCM, GRLD1, GRLD3, GRLD5, GRLDM, GRLE1, GRLE3, GRLE5, GRLEM, GRLF1, GRLF3,GRLF5, GRLFM, GRLG1, GRLG3, GRLG5, GRLGM, GRLSM, GRLW1, GRLW3, GRLW5, GRLWM, GRLYM.

This list in not inclusive of all products provisioned with DSL. If further information is needed, please consult your Service Manager or a USOC guide.

In conclusion: In order to qualify for the 3-day interval, it will be necessary for the CLEC to know when Qwest installed the end-user’s Megabit service (before or after April 4, 2001) and whether the account meets the required criteria for requesting a 3-day interval. If the CLEC is unable to obtain the date of the installation information from the CSR or is unable to determine by the USOC, then additional consultation with the end user by the CLEC may be needed to find out when their Megabit service was installed, prior to or after the April 4th, 2001 date. Should the CLEC submit an LSR with a 3-day interval request and Qwest determines that the Megabit service does not qualify for the simple interval, then the FOC would be sent to the CLEC with the appropriate Design/Complex interval due date.

Discussion has occurred with the Interconnect Service Centers to reinforce this change that was previously documented, and sent out to the Centers, when the change occurred in April. Qwest will continue to follow the service interval guidelines for simple and complex services as outlined in the Product Catalog (PCAT).

Sincerely, Joan Wells Process Manager Local Number Portability

Open Product/Process CR PC112603-1X Detail

Description Of Change

Status History

Project Meetings

11/17/04 November meeting minutes Cindy Macy – Qwest advised the PCAT was effective November 6. This CR will move to CLEC Test Status.

10/20/04 October meeting minutes Cindy Macy – Qwest advised the notification went out September 22 and the effective date is November 6. This CR will remain in Development Status.

9/15/04 CMP Meeting Minutes: Cindy Macy – Qwest provided status and advised that the documentation should be available next week for review and comment. This CR will remain in Development Status.

8/20/04 Ad hoc Meeting

Anne Trees - Qwest Elizabeth Hamilton - Qwest Donna Osborn Miller - ATT Cindy Macy - Qwest

Cindy introduced the team and advised the purpose of this call is to review the draft process and address Donna's question regarding mechanizing the solution. Anne and Elizabeth reviewed the process. Donna advised that she has talked with representatives who perform this function and they are okay with implementing the process as described in the Clarification Call notes and then if needed, later, issue another CR to request mechanization of the process. Donna explained they thought it would be cumbersome to fill out forms for multiple special needs customers. Donne asked if they had a large number of customers to set up, could it be done via a spreadsheet so they do not have to fill out 2000 forms. Elizabeth advised Donna that if this occurs we can discuss the best way to accomplish the large update. Elizabeth was open to a spreadsheet type of update. Potentially the accounts could be broken down between the Regions (Central, Western and Eastern) and that may help. If this is needed you should contact and work with your Service Manager first. Donna asked how soon do the updates occur. Anne and Elizabeth advised generally within a 48 hour time frame and this includes the receipt and turn around. Donna thanked the team for having the call and advised she is okay with the process.

8/16/04 CMP Meeting Mintues: Cindy Macy – Qwest advised that an ad hoc meeting is scheduled for Friday August 20 to review the process. Donna Osborne-Miller ATT asked for a systems person to be at the meeting as they would like to have the form mechanized. It is a labor intensive process to fill out the form and send it in manually. Cindy advised Qwest will try to invite a systems person, and will discuss this at the ad hoc meeting. This CR will remain in Development Status.

7/21/2004 CMP Meeting Minutes: Jill Martain – Qwest advised that this CR was crossed over from systems to product process this month. Anne Trees – Qwest advised that effective with the August CRIS release the DUF records will be rated. This is step 1 of the process. The screen codes will be updated at the operator station. The operator will know that the customer is a special needs customer. Qwest will handle and rate the call appropriately and pass the information to the DUF file. The PCAT and Operator Services Questionnaire will be updated. The target date for implementation is in September. Donna Osborne-Miller verified that the CLEC will have to identify the customer as special needs. Anne advised that the Directory Assistance Questionnaire is filled out by the CLEC and that is where the CLEC identifies which customers need this service. These questionnaires are forwarded to the operator services group, which enter the codes into their system, and that drives the correct handling of the call. Liz Balvin – MCI asked how long does Qwest anticipate for this process to take? Anne advised she would check on this and advise Cindy Macy. Cindy advised she will include this information in the notes. Anne provided the following update: The CLECs will only be filling out an attachment to the OS/DA Questionnaire to implement the Special Needs screening codes. They will fax the completed attachment directly to the OIS group. This is the same process they do today for other screen code updates. So the special needs screening code updates will follow the existing process. Once the complete and accurate attachment is received by the OIS group they will implement within a two business day timeframe. They will not need to complete the OS/DA questionnaire to add, change or delete screen codes including the Special Needs screen codes. This CR will move to Development status.

5/20/04 Systems CMP Meeting

Peggy Esquibel-Reed/Qwest stated that the LOE for this CR is 2350 to 2600 hours. This action item will be closed.

12/17/03 CMP Systems Meeting

Donna Osborne-Miller/AT&T stated that the clarification call was held and presented the CR. Donna said that AT&T would like the operator to stay on the line until the call is completed. Judy Schultz/Qwest said that we may have to split this CR into a System and Product/Process CR. Judy stated that the request to have the operator stay on line until the call is completed would most likely be a process change. Connie Winston stated that the interface needs to change from ‘other’ to IMA Common. Liz Balvin/MCI asked if ‘other’ interface is really the operator platform. Connie Winston/Qwest said that if we set this up it would be IMA. Donna Osborne-Miller/AT&T also want the DDD call rated. Connie Winston/Qwest stated the rate is based on the code given to us. Liz Balvin/MCI said that the rate would be populated on the order via IMA.

12/8/03 Clarification Meeting

Attendees: Donna Osborne-Miller - AT&T, Jo Ann Symenec - AT&T, Al Paris - AT&T, David Fane - AT&T, Kim Isaacs - Eschelon, Ann Trees - Qwest, John Gallegos - Qwest, Shonna Pasionek - Qwest, Connee Moffat

Review Description of Change AT&T is requesting that Qwest identify and rate AT&Ts Special Needs Customers for OS/DA assisted calls.

Discussion Donna Osborne-Miller - AT&T stated that they would like the Operator to stay on the line until the call is completed. Anne Trees - Qwest asked what kind of request is this associated with - IXC, Facility Based, UNE-P. Donna Osborne-Miller - AT&T said that it is UNE-P. John Gallegos/Qwest stated that Qwest understood this request and had no other questions.

Identify/Confirm CLECs Expectation AT&T would like to invoke the use of the DI and SOE LSOG fields in order to provide OS/DA service to AT&T Special Needs Customers.

Establish Action Plan AT&T will present this CR in the December CMP Systems Meeting.

CenturyLink Response

April 22, 2004

RE: SCR112603-01 Qwest to identify and rate AT&T's Special Needs Customers for OS/DA assisted calls

Qwest has reviewed the information submitted as part of Change Request (SCR112603-01). Based upon the scope of this CR as agreed to in the Clarification Meeting (held December 8, 2003) Qwest is able to provide an estimated Level of Effort (LOE) of 2325 to 2600 hours for this IMA Change Request with no SATE impacts.

At the next Monthly Systems CMP Meeting, CMP participants will be given the opportunity to comment on this Change Request and provide additional clarifications. Any clarifications and/or modifications identified at that time will be incorporated into Qwest's further evaluation of this Change Request.

This Change Request is an eligible candidate for the IMA 17.0 prioritization vote.

Sincerely, Qwest

DRAFT RESPONSE December 11, 2003 RE: SCR112603-01

Qwest has reviewed the information submitted as part of AT&T's Change Request SCR112603-01. Based upon research that has been conducted following the Clarification meetings (held November 18 and December 8, 2003) Qwest is still examining the issue. Qwest will continue to research the problem and provide an updated response at the March Systems CMP Meeting.

At the December Systems CMP Meeting, CMP participants will be given the opportunity to comment on this Change Request and provide additional clarifications. Qwest is interested in the experiences of the CMP community as relates to this issue. Qwest will incorporate any feedback received into further evaluation of this Change Request.

Sincerely, Qwest

Open Product/Process CR 5548341 Detail

Description Of Change

8-01 AT&T request add’l testing documents in regards to end to end testing.

Status History

Project Meetings

CenturyLink Response

Memorandum To: Central Office Directors

September 21, 2001

LX - - DVA (48 Hour) DIAL TONE TESTING REQUIREMENTS

There has been some confusion about the requirement, documented in the CO DVA PROCESS, for the CO to perform a Dial Tone test on DVA for Unbundled Dial Tone Capable Loops (NC Code LX - -). The requirements are:

1. ALL orders provisioning LX - - circuits MUST be checked for Dial Tone at the ICDF CFA. This includes both HOT CUT (Reuse of Facility) and Basic New (Vacant Facility) orders. 2. If the CO performs this test prior to the DVA and: A. Dial Tone is present the results must be logged in the order OSSLOG, using the OSSRMK screen in WFA-C. B. Dial Tone is NOT present the CO personnel MUST arrange to retest for Dial Tone on the DVA Critical Date by either: - Completing the DVA step partially and reloading the step to the DVA date. - Completing the DVA step and manually handling the order for retest (Manual holding bin) - Completing the DVA step and creating their own work request to retest on the DVA, loading this item to themselves or someone else. If someone else is loaded, the person loading the request must check to ensure that person is scheduled to work and that they know the item is loaded to them. 3. If the test is performed on the DVA and: A. Dial Tone is present the results must be logged in the order OSSLOG, using the OSSRMK screen in WFA-C. B. Dial Tone is NOT present, the testing CO personnel MUST contact the Implementer or Coordinator assigned to work the order (check the OSSOI screen in WFA-C). If none is assigned them must call the toll free number for the Design Service Center handling the order and give the trouble condition to the first implementer or coordinator they reach. Any Center personnel receiving this call SHOULD take the report and initiate Center activity for CLEC notification. This test failure MUST be logged in the OSSLOG. 4. If the time between DVA critical date and Due Date commitment time is greater that two (2) business days, the DSC/QCCC Implementer or Coordinator will determine this and hand off an SPL48 ticket requesting a Dial Tone retest two business day before commitment date. This should be the only time the CO would expect such a handoff.

The important points to remember are: - The CO is ultimately responsible for ensuring this Dial Tone test is peformed. - The CO must arrange their own retest if working DVA steps prior to DVA and NO DIAL TONE is found. - SPL48 tickets will only be generated by the DSC/QCCC under the situation stated in item (4.) above.

Please cascade this memo through your organizations. If you have any questions or comments, please contact me.

Cc: Central Office Senior Directors Deborah Heckart Fred Aesquivel

Open Product/Process CR PC022703-9X Detail

Description Of Change

AT&T is requesting a report for all known IMA EDI & IMA GUI problems.

This report will be a list of IMA EDI and GUI problems currently

identified either internally identified by QWEST or reported by a CLEC

thru the ISC Help Desk or Service/Account Manager. The report will

identify all open issues that are pending investigations. Once an issue

has been reported and determined to be a problem/clarification/defect

issue it should be noted on the report with the appropriate QWEST

Trouble Ticket # as it goes through the phases within QWEST well before

it makes it to the Event Notification process. Once an event

notification issued for the problem, the notification number would be

referenced on this report. This gives CLEC one central point of

reference for all IMA EDI & GUI problems. The CLECs can use this report

to:

(1) find out the current status of their IMA EDI or GUI problem

(2) determine if a new problem has already been identified and the

current status

(3) proactively address problems that have been identified by other

CLECs that have potential impacts to their business

Similar to the SBC's Defect Report, the QWEST report should include

the:(1)Trouble Ticket(TT) Number, (2) IMA Version(s) Impacted, (3)

Indicator whether problem impacts IMA GUI, EDI or both (4)Indicator

whether the defect is impacting production code or code only in the SATE

environment, (5) Date the TT was opened, (6) Short Description used to

identify the Problem - for example the actual message being returned

from QWEST, (7) REQTYP and ACT values impacted,(8) Event notification

Number (9) Status of the Fix(Pending Analysis, In Analysis, Pending

Development, IN Development, Pending Testing, In Testing, Pending Prod

Migration, Pending Prod Validation, CLOSED), (10) Status Comments,

(11)Target Implementation/Resolution Date

All Closed Issues should be moved to a separate document or EXCEL Tab

(similar to SBC's Defect Documentation) and retained for 3 months.

Any IMA problems that are currently in analysis and haven't been

reported via event notification should be placed on this report is

activated.

Description of Change - Submitted 02-27-03