Local Number Portability Administration

08/20/07

     

 

Best Practices Document

Item Number 44
Topic: Why carriers had discrepancies between PAS and NPAC for pooled blocks.
Date Logged 12/19/2006
Date Modified  
Related Regulation / Document Ref

CO41 Final Summary

Related Issue  
Reported to NANC?  
Recommended Change to Requirements?  
Submitted by LNPA-WG
Decisions / Recommendations
Change Order 41 directed the Pooling Administrator (PA) to perform a one-time scrub of the entire PAS Database to reduce the likelihood that carriers will receive over-contaminated blocks or incorrectly identified contaminated blocks in lieu of pristine blocks.  The PA provided a list of blocks to the NPAC in order to determine the contamination level of each block.  The NPAC then provided the PA with the results;  the PA compared the NPAC data against the block contamination status in PAS.  Out of the 189,552 available blocks, 10,758 resulted in a discrepancy, which meant that the information entered by the Service Provider into PAS or the NPAC was incorrect, and in addition, out of the 10,758 discrepant blocks, 506 blocks appeared to be over 10% contaminated.  The carriers involve din these discrepancies were notified to correct these discrepancies.  Following is a list of explanations from the carriers as to why they had discrepancies:

Lack of communication between the carriers departments;

The SPs did not realize they needed to do intra-SP ports prior to donating blocks;

The SPs did not have a process in place to notify the PA when the contamination status of a previously donated block goes from contaminated to non-contaminated;

Some SPs mistakenly believed that updating NRUF automatically updated the NPAC; and

Some SPs thought they could donate the block even though it was over 10% contaminated, if the numbers were ported to another carrier.

   

This site was last updated 08/20/07