Wholesale: Products & Services

Archived System CR SCR051903-1X Detail

type of interface, which has greatly increased Covad’s ability to determine the loop characteristics early on in the ordering process (pre-order).

The major advantage of this system is that it allows a DLEC/CLEC real time access to LFACS data. This information is critical to the ability of

a DLEC to determine early on if the high frequency portion of the loop can handle DSL service. Here is a description of BellSouth’s system:

The information contained in LQS (Loop Qual System) is derived from the Loop Engineering Assignment Data(LEAD) Database and provides

a 'best effort' response regarding a loop’s ability to support BellSouth’s ADSL service.

The LEAD Database is a once-per-month-per-wire-center 'snapshot' of the information

contained in the Loop Facilities Assignment and Control System (LFACS) Database.

1/30th of all wire centers are updated every day. Currently there is a 98% accuracy rate

on returned responses within LQS.

Here's a public link to the LQS (Loop Qualification System, aka SuperLoopy)

document:

http://www.interconnection.bellsouth.com/guides/bpobr/pdf/lqs.pdf

This document is mainly LQS Application focused. The Java API is briefly mentioned,

referencing the following, more technical link (however, it is not public):

http://lqs.bellsouth.com

All the data accessible from the application and more is available via the API.

Eric Fogle is the appropriate BellSouth contact for additional information on this system. The effort via OBF, for which he was the CLEC

workshop chair, was very much along these lines.

Eric Fogle can be reached at 404-927-3433, Eric.Fogle@BellSouth.com

Expected Deliverable:

As soon as possible

Status History

Project Meetings

-- July 22, 2004 Systems CMP Meeting Discussion: 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. John Berard/Covad stated that this is a medium priority for Covad due to the LOE, for the value.

-- February 19, 2004 Systems CMP Meeting Discussion Excerpt (Attachments H & J): Judy Schultz/Qwest stated that she wanted to provide an update to the funding approval process that was discussed in the January CMP Systems Meeting. Judy referred everyone to Attachment J in the Distribution Package. She stated that all CRs are being re-evaluated and must be approved. Judy said that CRs could not be scheduled without approval. Judy stated that the CRs with an impact to the IMA interface would follow the existing prioritization process. Judy noted that the funding for IMA 15.0 and IMA 16.0 has been approved, as well as funding to begin work on IMA 17.0.

- January Systems CMP Meeting Discussion: John Berard/Covad stated that this CR is a high priority for Covad, even thought the LOE hours are high.

- August 21, 2003 Systems CMP Meeting Discussion: Connie Winston/Qwest stated that the Level of Effort for this request is 6875 to 11450 hours for IMA and 300 to 375 hours for SATE. Connie stated that this is a brand new interface and is a voteable candidate for 15.0. Liz Balvin/MCI stated that Covad told her that this was their very first choice and is very important to Covad.

July 17, 2003 Systems CMP Meeting Discussion: Action Item: Covad to Submit Recent Examples Where Real Time Data Was Not Provided John Berard/Covad stated that he has worked with his Account Team and that Eric Yohe-Qwest has helped. John stated that examples were provided a while ago and that Covad is looking for a different step, they want the information that is in IMA’s pre-qual tool. Lynn Notarianni/Qwest stated that in the initial discussion, when Mike (Zulevic) presented this, he indicated that Qwest is not providing real time data and that is why Qwest had asked for current examples. Lynn noted that her understanding is that Qwest does currently provide real time data. Lynn stated that the action item for this CR could be closed and that we would proceed with the conference call scheduled with Qwest and Covad tomorrow. John Berard/Covad agreed. There were no additional comments or questions. This Action Item is Closed.

Action Item: Verify that Loop Qual in IMA Provides Most Current Information Connie Winston/Qwest stated that Raw Loop Data is a snapshot of time and that Mike (Zulevic) thought was that IMA was different data and is more up-to-date. Connie stated that this would be discussed on tomorrow’s call. John Berard/Covad agreed and stated that this Action Item could be Closed.

Ad-Hoc Call - Covad and Qwest - July 18, 2003 Introduction of Attendees: John Berard/Covad, Shiva Chere/Covad, Vin W/Covad, Kasie Murphy/Covad, Raj/Covad, Peggy Esquibel Reed/Qwest, Connie Winston/Qwest, Crystal Soderlund/Qwest, Woldey Assefa/Qwest, Eric Yohe/Qwest, Lane Jones/Qwest, Evelyn Montez/Qwest, Barb Brohl/Qwest, John Ebbert/Qwest, Lucy Higley/Qwest Review Requested Description of Change: Peggy Esquibel Reed/Qwest stated that the purpose of the call is for additional discussion regarding Real Time API Connection to Raw Loop Data and to communicate how Qwest currently provides. Meeting Discussion: Connie Winston/Qwest noted that Covad is certified for loop qual. John Berard/Covad stated that Covad needs to know how the pre-qual tool works and stated that this request is for API connection to the data. John then asked if there was a way to get access. Connie Winston/Qwest asked if the request is due to Covad’s being unable to read EDI. Covad stated that their architecture is set-up for an API connection, once an order is accepted. John stated that Covad currently relies on extracts. Connie Winston/Qwest stated that once Covad accepts the order from the customer, they could go to EDI. Covad stated that EDI is not a synchronous call and that is what they need. Connie Winston/Qwest asked why the need for synchronous. Connie asked if Covad’s need is to make sure that the customer qualifies. Covad stated that once a customer contacts them, they do need to be sure. Covad stated that once the order is placed, they use EDI data through extracts and sometimes it is not current data. Covad stated that this results in a reject from Qwest and they then need to communicate the reject to their customer. Connie Winston/Qwest stated that when we share Raw Loop Data, if the data changes, it is a favorable change, it would not be a negative change going backwards. Connie asked if that was what they were experiencing. Covad stated that the extracts are 30 days old and that the changes are not always favorable. Covad stated that 30 days is too long to wait. Covad stated that EDI is asynchronous mode and that it sometimes can take up to an hour to respond. Covad stated that EDI is not real time in that sense. Connie Winston/Qwest stated that EDI is in real time. Woldey Assefa/Qwest stated that EDI does provide real-time transactions. Covad stated that the timeframe usually is not an hour, but the response has to be less than a second. Barb Brohl/Qwest stated that Qwest has performance measures and that Qwest does evaluate and measure the amount of time it takes to respond. Barb stated that for DSL Qwest loop qual and loop qual, Qwest has agreed to less than 20 seconds. Barb noted that it has not been missed and that Qwest is providing data quickly. Covad stated that maybe it is not for EDI. Barb Brohl/Qwest stated that it is for EDI. Covad stated that EDI is an asynchronous protocol. Barb Brohl/Qwest asked for the effect, as long response time is not an issue, Qwest has a short response time. Connie Winston/Qwest stated that Qwest is trying to understand what makes this request beneficial. Connie stated that Qwest does have an electronic interface that provides this data. Covad stated that per business requirements for loop qual, a certain amount of response time is required so they have built a system, from the extract from different vendors, and stated that the format differences was an issue. Connie Winston/Qwest asked if Covad was referring to the format of how Qwest provided ‘the big file’. Covad responded yes, and stated that it breaks their process. Covad stated would like the extract replaced with an API connection. Connie Winston/Qwest stated that if Covad is using the bulk data for analysis, it would seem that Covad would be using API constantly. Connie stated that the bulk data would give Covad a focus and asked how line-by-line would be better. John Berard/Covad stated that when their partners go in to see if they qualify, bulk data is used and it could be outdated by 30 days. John stated that Covad would like their partners to go directly to the data. Connie Winston/Qwest asked if Covad was externally exposing a GUI and letting their customers perform the loop qual. John Berard/Covad responded yes and stated that Covad does not double check loop qual. John stated that once an order is accepted, the address is verified and they do a loop qual. Connie Winston/Qwest asked to confirm that the reason why Covad is uncomfortable with EDI is because Covad is going externally with a GUI. Covad stated yes and noted that it could also impact their systems. Covad stated that response time is crucial. Connie Winston/Qwest stated that from Qwest’s perspective, Qwest does provide the data via EDI. Covad stated that they have already implemented with Bell South and use API to verify information which is up-to-date. Connie Winston/Qwest stated that Qwest does provide the data via EDI. Covad stated that if the data is being provided through EDI, it is not synchronous. Covad stated that they are requesting that Qwest provide the data in synchronous mode, in addition to providing the current extract. Covad stated that API is synchronous. John Berard/Covad stated that Covad’s end user’s need to not time out and stated that 20 seconds is too long. Covad stated that accessing real-time would enable additional information to be retrieved that the extract does not have. Connie Winston/Qwest stated that Qwest is not excited about providing another interface and stated that from Qwest’s perspective, Qwest is meeting qualification requests and is currently providing loop qual data in real time. Covad stated that Qwest does provide in real time, but after they have accepted the order from their customer. John Berard/Covad stated that their customer’s are getting the extract information but is not real time. Connie Winston/Qwest stated that if the bulk data has changed in the extract, Qwest needs to tell the CLECs how it changed and why so the CLECs can code to the changes. Connie stated that if the format changed, it was probably for more data, but stated that she had not seen the format. Covad stated that if the format changes, it could create a problem. Covad asked that if the format does change, do they get notified. John Berard/Covad stated that if the format changes or a meaning changes, they do need to get notified. Connie Winston/Qwest stated that she was not aware of a format or meaning change. Eric Yohe/Qwest stated that if there are issues with a system, there are established processes that need to be used, such as calling in a trouble ticket, or placing a call to a service manager. Eric stated that this is a separate issue than this CR’s discussion. John Berard/Covad asked that if the source is the same but there is a difference, there been a change. Connie Winston/Qwest asked that if Covad is seeing that the bulk data is different, to please open a trouble ticket or place a call into their service manager. John Berard/Covad stated that there is a problem, in Phoenix, where the loops are labeled incorrectly or that they appear extremely long. John stated that he is seeing this in the extract and in EDI. John noted that this issue would be discussed in the pre-qual forum that has been established as a result of a Product/Process CR and is due to start in August. (Product/Process CR is PC051403-3 Request for By-Weekly Technical Meetings on Pre-Qual Issues) Barb Brohl/Qwest asked that if Covad has seen that fields have changed, to please get the information to the Covad service manager, Eric Yohe. There were no additional questions or comments. The call was concluded.

-- July 10, 2003 Email sent to Covad: Good Afternoon John -- This email is to follow-up and check status on your availability and your technical staffs availability to further discuss your submitted CMP CR for Real Time API Connection to Raw Loop Data. Please provide several dates and times and I will schedule the meeting and send you the call details. Thanks Much!! Peggy Esquibel-Reed Qwest CRPM -- Systems pesquib@qwest.com

-- June 27, 2003 Email sent to Covad: John, Thanks for the prompt revision to your CR. Would you please provide several dates and times as to when you and your technical staff are available for the follow-up call? I will then get the next call scheduled. Thanks, Peggy Esquibel-Reed Qwest CRPM -- Systems

- CLARIFICATION MEETING - June 27, 2003 ATTENDEES: John Berard (Covad), Mike Zulevic (Covad), Sharon Van Meter (AT&T), Donna Osborne-Miller (AT&T), Liz Balvin (MCI), Bonnie Johnson (Eschelon), Peggy Esquibel-Reed (Qwest), Dusti Bastian (Qwest), Jamal Boudhaouia (Qwest), Barbara Brohl (Qwest), Dan Busetti (Qwest), Suzy Enney (Qwest), John Gallegos (Qwest), Mark Gonzales (Qwest), Barry Orrel (Qwest) Joan Pfeffer (Qwest), Michelle Thacker (Qwest), Deni Toye (Qwest), Crystal Soderlund (Qwest), Heidi Moreland (Qwest) REVIEW CR DESCRIPTION: Peggy Esquibel-Reed (Qwest) stated that this CR was discussed and crossed over, to systems, during the June Product and Process CMP Meeting. Peggy Esquibel-Reed (Qwest) reviewed the CR description: Covad is requesting the implementation of a new Real Time Interface connection to Pre-Qual Raw Loop Data. Currently BellSouth has this type of interface, which has greatly increased Covad’s ability to determine the loop characteristics early on in the ordering process (pre-order). The major advantage of this system is that it allows a DLEC/CLEC real time access to LFACS data. This information is critical to the ability of a DLEC to determine early on if the high frequency portion of the loop can handle DSL service. Here is a description of BellSouth’s system: The information contained in LQS (Loop Qual System) is derived from the Loop Engineering Assignment Data (LEAD) Database and provides a 'best effort' response regarding a loop’s ability to support BellSouth’s ADSL service. The LEAD Database is a once-per-month-per-wire-center 'snapshot' of the information contained in the Loop Facilities Assignment and Control System (LFACS) Database. 1/30th of all wire centers are updated every day. Currently there is a 98% accuracy rate on returned responses within LQS. Here's a public link to the LQS (Loop Qualification System, aka SuperLoopy) document: http://www.interconnection.bellsouth.com/guides/bpobr/pdf/lqs.pdf This document is mainly LQS Application focused. The Java API is briefly mentioned, referencing the following, more technical link (however, it is not public): http://lqs.bellsouth.com All the data accessible from the application and more is available via the API. Eric Fogle is the appropriate BellSouth contact for additional information on this system. The effort via OBF, for which he was the CLEC workshop chair, was very much along these lines. Eric Fogle can be reached at 404-927-3433, Eric.Fogle@BellSouth.com. Peggy Esquibel-Reed (Qwest) asked if there was any additional information that Covad would like to share. John Berard (Covad) stated that Covad is requesting this functionality in addition to the extract, as a second application for the data. EXPECTED DELIVERABLE: As soon as possible CONFIRMED IMPACTED INTERFACE: IMA Common CONFIRMED IMPACTED PRODUCT’S: UNE, Line Sharing, Line Splitting, Loop Splitting DISCUSSION: Peggy Esquibel-Reed (Qwest) opened the bridge for questions and/or comments. Barbara Brohl (Qwest) asked if this request was for the wire center tool. John Berard (Covad) responded yes. Barbara Brohl (Qwest) stated that the data is currently updated real-time and that for 1/20th of the wire center’s, it is updated daily. Barbara stated that is real-time thru the loop qual database, via IMA. Barbara stated that transactions through IMA go through the application database, and then a query is done in LFACs to see if the loop has changed. If it has changed, the updated data is populated and the CLEC gets a response of the current data. John Berard (Covad) stated that Covad’s request is for real-time via their own pre-qual through an API Connection and asked how it should be set-up. John stated that Covad does not want to go through the GUI. Barbara Brohl (Qwest) asked if EDI would be sufficient. Barbara stated that she has had discussions with Kasie Murphy (Covad) and stated that there should be a way to provide, through EDI. John Berard (Covad) stated that Covad does not want via EDI, wants pre-order up-front on a real-time basis. John requested a follow-up call to include technical personnel. Peggy Esquibel-Reed (Qwest) agreed to schedule a follow-up call with Covad. There were no additional questions or comments. ACTION PLAN: Peggy Esquibel-Reed (Qwest) stated that this CR would be discussed at the July Systems CMP Meeting.

- June 19, 2003 Systems CMP Meeting Discussion: Kit Thomte/Qwest stated that this CR was discussed yesterday, at the Product/Process CMP Meeting and crossed-over to system’s. Kit asked if anyone wanted to discuss this CR at today’s CMP Meeting. Mike Zulevic/Covad stated that this would help address one of Covad’s chronic problems to get the most accurate data in order to start their provisioning process. Mike Zulevic/Covad presented the CR and stated that this is something that BellSouth is currently providing. Bonnie Johnson/Eschelon asked if this was creating a situation where you think you can provide DSL when you can’t. Mike Zulevic/Covad stated yes, and results in Covad setting false expectations because we think we can and can’t or because we know that we can’t. Lynn Notarianni/Qwest stated that Qwest believes that there are processes in place that provide this info in real time. Lynn asked that if Covad believes that there are situations where the data is not accurate or not provided, to please provide example to Qwest. Lynn stated that examples would be tremendously helpful. Mike Zulevic/Covad stated that Covad could provide more examples and stated that he has already provided examples to someone at Qwest. Lynn Notarianni/Qwest asked Mike (Zulevic) whom the examples were provided to at Qwest, so Qwest can obtain the examples from them. Mike Zulevic/Covad stated that he did not know whom, at Qwest, the examples were provided to. Mike stated that he has more recent examples but that he doesn’t want to do more research. Lynn Notarianni/Qwest stated that Qwest does not want Covad to spend a lot of time looking at it, but asked that if had data readily available, it would be very helpful. Lynn stated that Qwest would evaluate the data. Stephanie Prull/McLeodUSA stated that McLeodUSA is also interested in this request as well. Bonnie Johnson/Eschelon stated that Covad had submitted a CR that requested that updates be more than every 30-days and that the CR was denied. Bonnie stated that is probably why Covad submitted this CR. Bonnie Johnson/Eschelon stated that loop qual has been problematic for Eschelon as well. Bonnie stated that she is providing examples, to Eschelon’s service manager, where a Qwest retail customer qualifies for a specific speed but a CLEC gets a different speed. Lynn Notarianni/Qwest stated that the examples would help Qwest and look at the tool to see if a problem exists. Bonnie Johnson/Eschelon stated that the discrepancy could be due to the time difference. Lynn Notarianni/Qwest stated that this should not be an issue; it should have already been resolved. Lynn stated that this is where the examples would be very helpful. Bonnie Johnson/Eschelon asked if the data in Loop Qual is real time. Lynn Notarianni/Qwest asked if it was the Loop Qual tool that Eschelon is getting the data dump from or from IMA. Bonnie Johnson/Eschelon responded IMA. Lynn Notarianni/Qwest stated that Qwest has put in the capability to see if the data had changed and if it had, the CLEC would be able to get the new information. Bonnie Johnson/Eschelon stated that Qwest might want to investigate every ‘no’ in the last 30 days. That might help Mike Zulevic/Covad stated that at yesterday’s Product/Process meeting, another CR was presented that requests bi-weekly meetings with SMEs that handle loop qual to identify what kind of problems we’re having. Mike stated that the next walk-on CR is similar. Lynn Notarianni/Qwest stated that it needs to be kept in mind what products you’re using wanting the tool to do a loop qual on. Lynn noted that a resale provider might not do the same thing because they wouldn’t use the loop qual tool. Lynn stated that CR’s are very specific to certain things. There were no additional questions or comments. This CR will be crossed over to Systems.

PC051903-1 Real Time API Connection to Raw Loop Data 5/30/03: Held Clarification Call - discussed this would potentially cross over to systems Clarification Meeting Friday May 30, 2003 Attendees Cindy Macy - Qwest CRPM Michelle Thacker - Qwest Communications Dave Manica - Qwest Communications Craig Suellentrop - Qwest Communications John Berard - Covad Raj - Covad Shiva Sharif - Covad Cindy Buckmaster - Qwest Communications Cliff Dinnwiddie - Qwest Communications

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

Review Requested (Description of) Change Berard-Covad reviewed the CR. Berard explained they would like access to the individual TN Loop Qualification data that is the most current via a synchronous API. This data is available in IMA currently but via EDI or GUI and Covad would like to access via an API connection. Covad currently uses the Raw Loop Data tool to access loop qual data. They download the data to their own tool. This data is not always current or accurate. Covad wants the most current data, at an Individual TN level, via an API connection. Covad would like a Pre Qual API connection to IMA. Currently Covad also has access to Pre Qual EDI but this is not a fast enough response time due to the volume of data they download. Qwest and Covad discussed if there were certain data elements that were needed. Covad advised they would like access to the same data that they get from Pre Qual IMA EDI today, except in a synchronous API connection. If they want additional data elements added that would be a different CR. The team discussed that this should be a systems CR. Cindy agreed to check with the systems team and cross this CR over.

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

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

Identify/Confirm CLEC’s Expectation Macy-Qwest reviewed the request to confirm Covad’s expectation.

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

Establish Action Plan Macy-Qwest asked attendees if there were any further questions. There were none. Macy-Qwest stated that the next step was to cross this CR over to systems.

5/19/03: CR Received 5/20/03: CR Acknowledged 5/23/03: Contacted customer to schedule Clarification call

CenturyLink Response

August 12, 2003

RE: SCR051903-1X Real Time API Connection to Raw Loop Data

Qwest has reviewed the information submitted as part of Change Request (SCR051903-1X). Based upon the scope of this CR, Qwest is able to provide an estimated Level of Effort (LOE) of 6875 to 11,450 hours for this IMA Change Request. The SATE impact is 300 to 375 hours.

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 15.0 prioritization vote.

Sincerely, Qwest