Problems and Issues Management

In late 1999, the LNPA WG, now known as the Number Portability Industry Forum (NPIF), established a "Problem Identification and Management" (PIM) process for Number Portability (np) issues. The group, made up of Number Portability Industry members, developed:

  • Issue submittal guidelines (PIM Process Scope)
  • Issue submittal form (Problem/Issue Identification and Description Form)
  • Issue referral form (Problem/Issue Referral Cover Letter)
  • Process flows (PIM Process Flow Narratives and PIM Process Flow Graphics)
  • Tracking mechanism (PIMs Tracking Matrix)

The NPIF is not responsible for resolving all Number Portability problems. The NPIF performs an initial evaluation of each problem/issue submitted, then either develops a resolution for the issue or refers it to the appropriate forum for resolution. Issues submitted are tracked in the PIMs Tracking Matrix.

Issues should be submitted to the NPIF using the Problem/Issue Identification and Description Form, at least two weeks before the NPIF meeting at which Number Portability issue's discussion is desired.


 

Related Documents


 

Title Date Description Document
PIM 57 08/14/2006 Attempting to port a consumer when a Reseller abruptly discontinues business and/or declares bankruptcy. Download
PIM 56 05/03/2006 While all carriers receive updates in their LSMS when porting customers, some carriers are not provisioning their LNP databases correctly. When this scenario occurs, customers are not able to termina… Download
PIM 55 05/08/2006 Intermodal porting faces a challenge in the form of a process gap between the wireless and wireline carriers after a confirmation has been received. The 2 processes are not in synch, causing fall out… Download
PIM 54 04/28/2006 Comcast is requesting NANC support a standard porting interval for wireline to wireline and wireline to wireless of one day based on certain criteria Download
PIM 53 02/27/2006 Carriers are taking back numbers that have been ported out several months or even years because their systems do not reflect a valid FOC was sent. In many cases they have not removed the number from … Download
PIM 52 11/15/2005 Carriers are receiving blocks in which the Intra-Service Provider ports (ISPs) have not been completed by the donor provider prior to being donated to the pool. These blocks should be considered unus… Download
PIM 51 03/07/2005 Currently a carrier can open a Code (NPA-NXX) for portability in the NPAC whether or not they own the NPA-NXX. Download
PIM 50 01/17/2005 A large number of wire line to wireless ports fail the automated process because they are from large accounts where the customer service record (CSR) is too large to return on a CSR query. The CSR is… Download
PIM 49 09/27/2004 Service Providers do not have clear direction in the NANC flows regarding the proper porting procedure for Type 1 numbers Download
PIM 48 09/21/2004 "Both the NIIF Company Specific Contact Directory and the National LNP Contact Directory are documents used by several companies to assist in troubleshooting LNP problems as well as for general inter… Download
PIM 47 07/12/2004 The intention of this PIM is to discuss minimum industry intermodal standards for purging old/abandoned ports. This issue is related to WNPO Issue 04-13- 'Purge Old Port Requests with No Response' an… Download
PIM 46 07/19/2007 The existing NPAC Filter Management process only allows a filter to be applied for a particular NPA-NXX if that particular NPA-NXX has previously been entered into NPAC. Download
PIM 45 07/21/2004 When there are errors in local service requests to port a number some service providers only respond identifying a single error. Additional LSRs and responses are required until all errors are finall… Download
PIM 44 07/21/2004 Wire line carriers rules for developing a local service request (LSR) in order to port a number are unique to each carrier, dynamic and complex requiring dozens of different fields. Each carrier can … Download
PIM 43 07/09/2004 Verizon Wireless has concerns about the volume of port transactions that the NPAC can process per second when mass changes need to be made and broadcasted to the industry. Now that wireless service p… Download
PIM 42 07/07/2004 The wireless process for porting based on developing and sending a 'wireless port request' (WPR) does not collect and provide all the information that is needed to map to the wireline "local service … Download
PIM 41 07/08/2004 Outside of NANC 323 - SPID Migrations, when carriers acquire or trade markets, unexpected fallout can occur for their LNP trading partners during the time the markets are being transitioned from one … Download
PIM 40 05/27/2004 "The intention of this PIM is to discuss minimum industry standards for LNP readiness that must be adhered to by all companies in order to port. " Download
PIM 39 06/02/2004 Current wireline business practices allow carriers flexibility to set their own unique "business rules" or porting requirements and change them as often as needed. Some carriers will change their bus… Download
PIM 38 05/26/2004 The current -x object (1k Pool Block) tunable of 5 business days between the Create and Activate is too long and acts as a constraint against service providers. Download
PIM 37 05/27/2004 "The intention of this PIM is to discuss minimum industry standards for LNP readiness that must be adhered to by all companies in order to port. " Download
PIM 36 04/05/2004 NPANXXs are sometimes opened in the wrong NPAC region. Download
PIM 35 03/26/2004 Why are all service providers required to participate in certification testing if the vendors are already completing the same testing? Download
PIM 34 02/27/2004 Wireless carriers are not receiving customer service records (CSRs) from all wire line network service providers when porting 'Type 1' numbers from other wireless service providers who are leasing th… Download
PIM 33 02/13/2004 "We have to pay for a non-discretionary ""Active Like TN's in a NPA-NXX Report"" when taking over a code to verify blocks that are over 10% contaminated." Download