Section R. 484.88 - Service quality standardsRule 8.
(1) Upon receipt of an accurate request from the new local service provider, the old local service provider shall port the telephone number and, if requested, transfer the unbundled loop to the new local service provider within the specified time period listed in subdivisions (a) and (b) of this subrule, unless a later due date is requested. If the old local service provider reschedules the original due date without the consent of the new local service provider, or the old local service provider fails to complete the migration by the original due date, the original due date shall be the one measured against. The following apply to due dates: (a) Due dates for migrations involving number portability with or without a loop. For a migration request involving 1 to 18 lines, the due date is a monthly average of 4 business days after a request is made. Any migration request involving 19 or more lines involving number portability with or without a loop is a project for which a due date shall be negotiated.(b) Due dates for migrations involving a simple port request only, for example, not for orders that require other facilities, such as loops. For a migration involving a simple port, the due date is the date required by 47 CFR 52.35. For migration involving simple ports for 2 to 30 lines, the old local service provider shall send a firm order confirmation within 24 hours and complete the porting of the telephone number to the new local service provider within 3 business days of the firm order confirmation. Any migration request that involves simple ports for 31 or more lines is a project for which a due date shall be negotiated. (2) The provider shall keep records on provisioning due dates that are not met. This measurement shall be reported by the provider at an order level for resale plain old telephone service, and at a feature or circuit level for resale specials and local wholesale arrangements. The records shall be available for review upon the request of commission staff. (3) Data used to measure performance concerning due dates shall not include misses caused by either of the following: (a) Action or inaction of the new local service provider or the end user.(b) The number portability administration center.Mich. Admin. Code R. 484.88
2010 AACS; 2013 AACS; 2016 AACS; 2019 AACS; 2022 MR 5, Eff. 6/17/2022