Section R. 484.85 - Migration responsibilities of local service providersRule 5.
(1) Each service provider shall maintain a publicly accessible website with all of the following information:(a) All applicable processes and procedures for end user migration.(b) Company contact escalation list, which shall include a company contact for operational issues and a contact for escalation of those issues.(2) The old local service provider shall release any assigned telephone numbers associated with the end user's service that are properly requested in accordance with industry standards and federal law.(3) Except for migrations described in 47 CFR 64.1120(e), the new local service provider shall communicate directly with the end user, receive the end user's authorization to switch service providers, and provide all pertinent information to the end user associated with the end user migration. (4) The new local service provider is responsible for the coordination required to migrate the end user. The underlying network service providers shall promptly provide necessary support and assistance to migrate the end user. Neither the old local service provider nor underlying network service provider shall interfere in the transfer or otherwise use this opportunity to win back the customer. (5) Before requesting a customer service record, the new local service provider or authorized agent shall have obtained an end user's authorization.(6) All providers shall follow industry standard procedures and federal law for porting an end user's telephone number and processing to actual completion the migration of the end user upon receipt of an accurate request from the new local service provider. For requests received outside of business hours, the date and time of receipt shall be considered to be the beginning of the next business day.(7) When local exchange service to be migrated is currently provided using resale or local wholesale arrangements, the old underlying network service provider shall provide a loss notification to the old local service provider upon completion of a request. (8) Upon completion of the service order, the old underlying network service provider shall unlock the end user's E911 records that are being migrated, within industry standard or federally mandated timeframes, whichever is earlier. The new underlying network service provider shall assure the new E911 database record is accurately entered into the E911 database and that the database is locked.(9) Directory listing information shall be submitted by the new local service provider to the directory service provider using a local service request or other mutually agreeable format. If the old local service provider is a facilities-based provider and directory listing migration capabilities are not available from the directory service provider, then the old local service provider shall remove its listings upon completion of a local service request to migrate local service. The new local service provider shall ensure that the directory listing information is accurate.(10) The new local service provider may reuse an unbundled loop upon request if reuse is technically feasible. Any of the following exclusions shall apply: (a) The new local service provider has made all reasonable efforts to obtain the circuit identification for reuse, and the circuit identification information was not provided by the old local service provider.(b) Upgrade or downgrade of existing facilities is required.(11) The old local service provider shall release the circuit identification and facilities for reuse when the existing circuit or facilities are no longer needed by the old local service provider to provide service to the migrating end user or any other end user that is currently using those facilities.(12) The old local service provider shall not retain a requested facility for possible future use.(13) An unbundled loop shall be considered released for reuse when the old local service provider provides the circuit identification for release.(14) Subject to subrule (10) of this rule, when requested, and reuse of the unbundled loop facility is available, the old local service provider shall provide the circuit identification number with the associated telephone number for the requested unbundled loop facility to the new local service provider as part of the customer service record or firm order confirmation response. To order the reuse of an unbundled loop facility, the new local service provider shall furnish the circuit identification number on the local service request issued to the new underlying network service provider.(15) If the new local service provider requests reuse of the unbundled loop facility, and it is not available, then the old local service provider shall use best efforts to indicate as part of the customer service record or firm order confirmation response the reason why the unbundled loop is not reusable.(16) The local service providers and underlying network service providers involved in the transfer shall maintain accurate unbundled loop circuit identification information and customer service record content, as applicable, to the end user service to facilitate migration activity as described in these rules. (17) The underlying network service provider shall notify the local service providers involved in the transfer of changes affecting information contained in this rule within 5 business days of completion of the transfer.Mich. Admin. Code R. 484.85
2010 AACS; 2013 AACS; 2016 AACS; 2019 AACS; 2022 MR 5, Eff. 6/17/2022