6. MIGRATION INTERVALS.

Currently ASI provides standard and consistent due date intervals totaling 10-12 business days for the process of placing disconnect orders and new connect orders to migrate an end user from one ISP to another ISP when both ISPs use ASI as the underlying DSL transport provider. This interval assumes the appropriate end user authorization or acknowledgement and coordination between the releasing ISP, the acquiring ISP and the ISP Service Center utilizing the stacked order process. This interval is the time associated with the order processing and provisioning of the DSL Transport service, and does not reflect the down time experienced by the end user, which should be less than the 10-12 business days, depending on the coordination between the ISPs, and the ability of the acquiring ISP to provision its service and any necessary CPE or software to the end user. ASI shall not be responsible for delays caused by inappropriate authorization or lack of cooperation from the involved ISPs.

ASI will use commercially reasonable efforts to provide the ISPs with the ability to reduce the down time experienced by an end user when migrating from one ISP to another, with a goal of minimizing the down time of the DSL Transport service. ASI commits to a target of no more than one business day of down time of the DSL Transport service for any central office-based end user seeking to migrate from one ISP to another ISP when both ISPs use the same ASI DSLAM, subject to the appropriate ISP authorization, cooperation and coordination. As an initial step in this direction, ASI entered into a trial with ISPs to develop processes and procedures which may yield an ISP migration with reduced downtime for the end user. The results of the trial allowed ASI to determine appropriate business requirements for mechanization. ASI represents that it is currently working on systems enhancements to enable an ISP to send a single "ISP Change Order" that would trigger disconnection of the DSL Transport service from the current ISP and connection of the DSL Transport service to the new (or "acquiring") ISP when the ISP has obtained the end user's authorization and has provided ASI with the appropriate ISP authorization.

With the ISP Change Order process, ASI expects to be able to offer, by the end of the Third Quarter of 2003, a standard interval of no more than one business day downtime of its DSL Transport service when the acquiring ISP asks for service in the same ASI DSLAM. For those instances in which the acquiring ISP asks for service in Remote Terminals, or in a different DSLAM in the same Central Office, ASI expects to be able to offer an average interval of no more than one business day downtime of the DSL Transport service in the Fourth Quarter of 2003. The one business day downtime interval for the DSL Transport service is targeted to begin and end on the same day. Such downtime interval targets do not include instances in which the end user is moving its location at the same time they are changing its ISP, or in which other changes to the DSL Transport service are being requested by the ISP. This end user downtime interval target is for the DSL Transport service only and does not include any time associated with the provisioning of service by the ISP and any necessary CPE or software to the end user. ASI commits to advising CISPA and the Commission of the status of these enhancements at the end of the third quarter of 2003. With an ISP Change Order, the ISP will not be required to acquire additional Virtual Paths (VPs) to migrate an end user, so long as the ISP has an existing VP to a DSLAM with an available port within the same CO.