E-mail from Martin E. Grambow, Vice President & General Counsel, SBC Telecommunications, Inc., to Katherine Brown, Attorney, U.S. Department of Justice, Habeeb Affidavit (Feb. 3, 2000) (with attachment).
This is in response to your questions about Johnm Habeeb's affidavit.
1. The number of lines ported comes from the PSOD database. The 448,220 lines reported is lower than the total number in the database because we do not include the following cases:
* Ported number where ex-SWBT customers previously served by a CLEC return to SWBT (Win-backs)
* Ported numbers where a customer originally served by a CLEC changes to SWBT service. * Additionally, approximately 30,000 lines are ported in non-mandatory MSAs somewhere in SWBT's 5-state area. These records do not identify the state name - since we cannot accurately allocate any of these to Texas we do not include them in the count.
2. Between April 98 and October 98, SWBT-TX increased its retail business line count by 148,653. During this same period, CLECs increased their resold business line count by 94,306 and their facilities-based business line count by 769,559. The total CLEC increase was 863,865. The combined SWBT/CLEC increase in business lines was 1,012,518. CLECs account for about 85% of the total increase, better than 4 out of 5 during this period.
In any given month, the percentage increase from the previous month may vary considerably. The change from October 99 to November 99 shows the CLECs with the better than 90% of the increase. The change from July 99 to August 99 shows the CLECs with only 67%.
3. Please see attached spreadsheet for access lines in Texas, Sep 99 through Dec 99.
<<Lines in SWBT Serving Area-TX.xls>>
DOJ Exhibit 1
DOJ Exhibit 1, Attachment
E-mail from Martin E. Grambow, Vice President & General Counsel, SBC Telecommunications, Inc., to Katherine Brown, Attorney, U.S. Department of Justice, Line Counts (Feb. 7, 2000).
Katherine, the following are the line counts your requested this morning:
As of the end of September, 1999, CLECs had 32,452 UNE loops and 72,733 UNEP lines in service. As of October 8, CLECs had 306,071 interconnection trunks in service.
In addition, you have requested the "12/6/99 CLEC trunk actuals" referred to in paragraph 48 of the Decree affidavit. That number is 347,830.
Please call me if you have any questions.
DOJ Exhibit 2
E-mail from Martin E. Grambow, Vice President & General Counsel, SBC Telecommunications, Inc., to Luin Fitch, Attorney, U.S. Department of Justice, DSL (Feb. 7, 2000).
Luin, this is in response to your request for information relative to provisioning DSL capable loops.
1. PM 55.1 You have indicated that both Covad complained that their orders are rejected by SWBT for spectrum manangement reasons, which must then be supplemental and re-submitted. Further, they alleged that when supplemental order are submitted, we will only accept the order if they change the due date to one that is outside the normal interval and 15 days after we receive the supplement. The result is that over half of their order fall outside the normal interval and are not captured in PM 55.1.
Covad is incorrect, it has never been SWBT's policy to require CLECs to select a due date outside the standard interval. Covad raised this issue before the Texas PUC and was advised that they did not have to select a due date outside the standard interval.
If the CLEC requests that a loop meet industry standards for spectrum management -- i.e., a specific PSD -- and there is no loop available that meets the requested PSD, then SWBT will reject the order. The CLEC can then issue a supplement and ask for conditioning, change the PSD, accept the loop "as is," or cancel the order. In the case of a supplement, the CLEC can select a due date within the standard interval.
Today, SWBT also allows the CLEC to order the loop "as is" on the LSR prior to any loop qualification, regardless of whether it will meet the industry standards or not. In such a case, the CLEC can also select the standard interval.
CLECs also can request due dates that are outside the standard interval, which actually frequently occurs.
2. Maintenance and repair performance measurements. You have asked for an explanation why SWBT does not include DSL loops that do not meet industry standards in the maintenance and repair PMs, citing the Chapman Affidavit at p. 29.
This is correct, but for a very good reason. SWBT provides CLECs with the choice of deploying their DSL technologies in a manner that does not comply with industry standards. In many cases, this means the CLEC is attemption to reach customers beyond the recommended distance for the spectrum management class. The PMs relating to maintenance and repair were not designed to capture trouble related to whether or not the loop meets industry standards for DSL. Accordingly, the do not differentiate between trouble related to a DSL loop that does not meet industry standards, and other trouble on the line unrelated to whether the DSL loop meets industry standards.
DOJ Exhibit 3
Alothough the CLEC may be able to provisions their service over a loop outside the industry standard; in many cases, the CLEC is unable to provide the level of service desired because of the loop's length or condition. For example, the industry standard may state that a particular spectrum management class (PSD) can be deployed over loops up to 7,000 feet. The CLEC, however, may choose to attempt to offer service to an end user served by an 11,000 foot loop. SWBT does not prevent the CLEC will not be able to achieve the level of service desired, because the facilities serving the end user do not meet the parameters specified by the industry for the CLEC's chosen spectrum management class. Consequently, this results in a high number of trouble tickets for non-standard loops. Since these difficulties are not caused by an failure on SWBT's part but by the CLEC's business decision to attempt to provide DSL service in a manner outside that recommended by the industry standards, the volumes of trouble tickets associated with the non-standard deployment of DSL should not be held against SWBT in the calculation of performance measures.
3. PMs 5, 10,1 and 11.1. You asked whether these measurements capture FOCs and rejects for DSL, since they are not broken down for DSL.
The business rule for FOC was developed prior to August 1999, and did not contemplate DSL. For IDSL, CLECs purchase a Basic Rate Interface (BRI) loop, for which the FOCs are included in the PM 5 UNE Loop category (1-50). Rejects on DSL are included in PM 10 and 11 for those LSRs submitted electronically.
PM 57-01 You have asked if SWBT has implemented the change to this PM ordered by the Texas PUC.
The change in start and stop times for this measurements were implemented on January 1, 1999, and will be reflected in SWBT's reporting of January's performance results. The Texas PUC requested that SWBT begin to measure the time it takes to provide loop make-up information when it receives an accurate and complete Local Service Request, and end the measurement when the loop make-up information is sent back to the CLEC.
Letter from Paul A. Crotty, Group President, Bell Atlantic - New York, to the Honorable Maureen O. Helmer, Chairman, New York State Public Service Commission (Feb. 4, 2000).
February 4, 2000
Hon. Maureen O. Helmer
Dear Chairman Helmer:
I want to provide you with a detailed update of the status of the OSS issues now being resolved under the guidance of the Department of Public Service staff. These issues are commanding the full attention of Bell Atlantic-New York and its outside vendors. Our aim is to employ whatever near term solutions are necessary to ensure that our wholesale customers continue their successful mass marketing effots and at the same time eliminate the root causes of the current issues. I am pleased to report that progress has been made, and that we are working closely with our wholesale customers to meet their needs.
I also want to assure you that BA-NY will ensure that its reported metrics and market adjustments for January (and going forward if necessary) include the impact of the issues discussed below. In addition, BA-NY recognizes that the Amended Performance Assurance Plan permits the Public Service Commission to reallocate market adjustments funds and would not object to such reallocation related to the issues discussed here.
The recent requests for expedited dispute resolution are now under resolution deal principally with missing acknowledgement, completion and confirmation notifiers that inform our wholesale customers of the status of their orders. These status messages are important and Bell Atlantic recognizes its obligation to provide them. Their absence, however, does not mean that an order failed to generate the appropriate service charge. Our data shows that most of the orders related to the affected status messages are and have been proceeding through the provisioning and billing completion steps. Indeed, BA-NY has processed over 250,000 local service requests in January alone.
DOJ Exhibit 4
Acknowledgements are sent to our wholesale customers to comfirm receipt of an EDI order. The vast majority of the missing status notices reported have been acknowledgements not properly returned by BA-NY side of the interface. These acknowledgement concerns have been traced to the third-party product, ECXpert, which generates the acknowledgements.
These issues have been escalated to the highest levels with the vendor, which has responded with on-site technical support and has made a number of recommendations. We have implemented a number of these recommendations and have seen a dramatic improvement in acknowledgement receipt by one of our major wholesale customers. The vendor continues to investigate the root cause of the software problem.
In addition, beginning January 17, BA-NY implemented processes and procedures to ensure that -- until such time as the vendor fixes its software -- our wholesale customers will receive daily information confirming receipt of the order they have sent us. The information is sent by noon each day for the previous day's activities. On Mondays, the information sent includes the activity for the previous Friday, Satuday and Sunday. We are customizing the form of this information based on feedback from our customers. We also are monitoring the EDI processing itself on an hourly basis (on a 7x24 basis) to ensure that orders that are affected by the vendor software are placed in the order processing flow.
We are also taking other steps that we believe will improve the performance of the vendor product. By this weekend, we will implement a new load-balancing arrangement for one wholesale customer, which will substatially increase overall hardware capacity. We are also investigating the existing FTP connectivity with another wholesale customer to eliminate this as a possible source of trouble.
Confirmations and Completions
Confirmations inform our wholesale customers that a particular order is ready for provisioning and the date on which it will be provisioned. There are two types of completion notices. One indicates that an order has been provisioned: the other indicates that billing records changes associated with a provisioned order have been completed. As noted above, in the majority of instances the orders associated with the affected notifiers have in fact gone through the associated processing steps.
As with the acknowledgement issue, we are approaching this issue on two parallel paths. First, beginning on January 27, we began a daily file comparison process to ensure that our wholesale customers in fact received the comfirmations and completions sent by BA-NY. As with acknowledgement, the confirmations are sent by noon each day for the previous day's activity. On Mondays, the informations sent includes the activity for the previous Friday, Saturday and Sunday. This will ensure that any missing confirmations or completions are promptly resent. We are customizing the form of this information based on feedback from our customers. Second, a special team is performing an extreme, end-to-end cause analysis to resolve any other issues affecting confirmations and completions.
Status Notifier Recovery
We believe that the corrective actions and procedures we have put in place will ensure that our wholesale customers receive timely status notification, and that all orders sent to us are properly received and processed. In addition to these steps, BA-NY has committed to recover and return past missing status notifiers to our wholesale customers. The effort has -- with the construtive input and cooperation of our wholesale customers -- been differentiated depending on the type and vintage of the notifier. The bulk of this effort is directed to confirmations and completions (since most of the affected orders have proceeded to further stages of provisioning, we and the affected wholesale customers agree that returning an acknowledgement at this stage is not useful).
For December and earlier orders, we are returning basic information that enables our wholesale customers to update their records to show order status as either confirmed, provisioning-completed or billing-completed (the overwhelming majority of these orders have been completed through provisioning and billing.) One major wholesale customer has approved the test file that will be used for these purposes, and another has approved the specifications for the file. This recovery process has begun, we are committed to completing this recovery process by February 15 and we believe we have the resources in place to do so.
For missing notifiers in January, we will provide information equivalent to that in the original notifier. We expect to complete this effort by February 18.
CORBA is a new interface jointly developed by BA-NY and one wholesale customer and used by that customer for pre-order transactions. CORBA outages over the past few months have had a number of different causes. Late last year, we experienced issues with the CORBA software and the configuration, as well as a number of issues traced to our wholesale customer's systems. Those issues were addressed last year, except for one root-cause fix was completed after the close of the Y2K moratorium. We believe that the changes made by BA-NY and the wholesale customer last year had stabilized the CORBA environment by the end of December. The reported CORBA outages on January 18 were related to CORBA itself, and a software fix is scheduled for February 19. The outage on January 21 was related to the hardware failure in another system. This hardware failure was addressed and the affected system was restored by 8 a.m. We continue to monitor the availability of these systmes to minimize the effects of hardware crashes.
Suspensions for Non-Payment
BA-NY has been able to identify a few hundred instances (out of the nearly 400,000 UNE-Ps now in service) in which a retail customer has been suspended for non-payment nearly contemporaneouly with that customer's migration to a CLEC.
Although this problem appears to affect only a very small portion of migration customers, BA-NY is attempting to accelerate a software fix that is currently targeted for June. In addition, when the substitutes are identified, BA-NY restores services as quickly as possible, and is establishing a team focused on and trained for rapid restoration of this situation.