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 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 |
| PIM 32 | 02/27/2004 | Wireless carriers are not receiving customer service records (CSRs) from all wire line network service providers when a reseller is the local service provider. Wireless port requests do not collect t… | Download |
| PIM 31 | 02/27/2004 | "Wireless cannot process ""Jeopardizes"" following confirms from wireline service providers when they are not able to meet the original due date and time." | Download |
| PIM 30 | 01/23/2004 | There is differing interpretation of N-1 Number Portability Querying responsibilities, and whether wireless carriers are obligated to perform default NP Queries when the N-1 carrier fails to dip the … | Download |
| PIM 29 | 01/20/2004 | Due to inconsistent inter-modal processes some customers are experiencing loss of service between disconnects and activations. | Download |
| PIM 28 | 01/02/2004 | When porting between wireless and wireline there is an interface difference between WPRR (wireless) and FOC (wireline). FOC allows for a due date and time change on confirms. WPRR does not allow a du… | Download |
| PIM 27 | 09/29/2003 | There is no way to get an SV out of Cancel Pending status other than waiting out the timers. The timers could take up to 24 business hours (two 9-hour Cancel Pending timers plus 6-hour Conflict timer… | Download |
| PIM 26 | 09/03/2003 | The NPAC Testbed hardware platform does not reflect a production environment to support volume performance tests. | Download |