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 160 | 06/04/2025 | During the April 7th NPIF Architecture Planning Team (APT) meeting, the LNPA took an action item to draft a PIM to propose language to clarify the current FRS transactions/second (TPS) rate requirements regarding how the TPS requirements apply for Service Bureau/Primary SPIDs that may have one or more secondary SPIDs. These TPS requirements in the FRS indicate that the transaction rate for the SOA-to-NPAC SMS interface and the NPAC SMS-to-Local SMS interface is defined per “association”, which is a construct/term that applies to CMIP interface but should be updated to apply generically across any mechanized interface. See also the GUST (Giddy Up Sub-Team) Readout APT – May 22, 2024: Page 3 - Current requirements are silent or require clarification on certain key tps related topics: clarification required a) Service Bureau / Primary SPID and its Secondary SPIDs. | Download |
| PIM 159 | 06/04/2025 | In August 2023, the LNPA introduced a new method for submitting SPID Migration requests through the help desk. This method does not require use of the Excel “SPID Migration Workbook” but rather allows SPID Migration data (dates, NPA-NXXs, LRNs, etc.) to be entered directly into an NPAC help desk ticket. Submitting SPID Migration requests to the NPAC help desk via the SPID Migration Workbook continues to be supported. In calendar year 2024, 19.6% of SPID Migration requests submitted through the NPAC help desk used the SPID Migration Workbook method and the remainder (80.4%) used the newer method that does not require the workbook. Given a significant majority of requests are using the new method, the LNPA would like the industry to consider sunsetting submitting requests using the SPID Migration Workbook. |
Download |
| PIM 158 | 01/08/2025 | Currently, pseudo-LRN (LRN = 000-000-0000), aka pLRN, SVs are migrated with the NPA-NXX to the To SPID in a SPID Migration, regardless of NPBs that remain with the From SPID (or any SPID holding NPBs in the code). This leads to undesired consequences such as transfer of inventory and ‘invisible’ contaminants. | Download |
| PIM 157 | 12/04/2024 | Current requirements are silent or require clarification on certain key tps related topics. | Download |
| PIM 156 | 10/02/2024 | Due to the current SPID Migration count constraints, the majority of SPID Migration windows are full. Service Providers (SPs) must find the next available window which can be weeks/months from the desired date. SPs are also scheduling more SPID Migrations than desired across available SPID migration windows to stay within the current record max counts. | Download |
| PIM 155 | 09/11/2024 | Pooled TNs that are part of a Number Pool Block (NPB) cannot be modified. Any modification of routing data requires a Create-and-Activate Process. | Download |
| PIM 154 | 08/07/2024 | Currently, though NPBs having a pseudo-LRN (LRN = 000-000-0000) and the associated NPA-NXX-Xs are migrated when the NPA-NXX of the NPB exists in the NPA-NXX SIC-SMURF file, some local systems are only migrating the NPA-NXX-Xs that exist in the NPA-NXX-X SIC-SMURF file, which would not be the case for these pseudo-LRN NPBs. |
Download |
| PIM 153 | 01/10/2024 | Current and prospective NPAC users have a need for a list of vendors who offer services and systems related to NPAC such as LSMS systems, SOA systems and Service Bureaus. Currently there is no list of vendors that provide these services. | Download |
| PIM 152 | 09/13/2023 | NANPA obtains certain ad hoc NPAC data once a week. Obtaining such data each business day (as needed) instead would be beneficial to both NANPA and service providers by allowing NANPA to process returned/donated or abandoned thousands-blocks and NXX codes more quickly. The NPAC Help Desk process to produce these reports is a manual one. | Download |
| PIM 151 | 04/12/2023 | If a SOA notification is missed, there is no way to tell if T2 has expired. | Download |
| PIM 150 | 11/08/2022 | The FRS has requirements for the LNPA to support faxing reports. Since taking over the LNPA service in 2018, iconectiv has not faxed a single report. It appears that support for faxing of reports is no longer needed | Download |
| PIM 149 | 11/08/2022 | There is no mechanism to identify an Inter-Service Provider Port as a port within the same Company that is using different SPID values | Download |
| PIM 148 | 10/05/2022 | Prior to a SPID Migration, the LNP Administrator (LNPA) has several preliminary tasks that need to be worked, with some of these tasks directly impacting Service Providers (SP) that may not be the Ol… | Download |
| PIM 147 | 07/12/2022 | NANPA is in the process of developing a new system that will combine the functionality provided today in the existing NANP Administration System (NAS), Pooling Administration System (PAS) and Routing… | Download |
| PIM 146 | 06/07/2022 | Prior to a decision to increase the transaction per second (TPS) rate, industry production load testing is recommended to ensure any increase will not adversely impact industry service provider syste… | Download |
| PIM 145 | 05/03/2022 | Currently the FRS has requirements to validate that a Service Provider can be removed only if all associated Portable NPA-NXXs and LRNs have been removed. The FRS also has requirements to validate no… | Download |
| PIM 144 | 05/03/2022 | Portable NPA-NXXs, Number Pool Blocks, and SVs for 976 NXXs (i.e., codes of the form NPA-976) exist within three NPAC regions. According to the TBCOCAG Section 7.3.8, the “976 CO Code shall only be u… | Download |
| PIM 143 | 03/08/2022 | The FRS allows for a Portable NPA-NXX to be created with an Effective Date in the past but does not specify a reasonable limit for the past date allowed. | Download |
| PIM 142 | 02/08/2022 | VoIP service providers are susceptible to IP network attacks, as evident by recent DDoS attacks (see definition in section F below), both domestically and abroad in the last several months. In order … | Download |
| PIM 141 | 11/02/2021 | Currently, there is no limit to the number of delegate SPIDs that a single grantor SPID can have. There are currently grantor SPIDs that have multiple delegate SPIDs. Adding delegate SPIDs can signif… | Download |
| PIM 140 | 10/04/2021 | Currently, service provider SPIDs are allowed to be delegates of other service provider SPIDs. However, no two service provider SPIDs have entered into a delegation arrangement since the delegation … | Download |
| PIM 139 | 08/03/2021 | When a Delete SV message is sent from the NPAC to the LSMS, it is not clear as to why the number is being removed. The two options are 1.) because the number has been disconnected and is no longer i… | Download |
| PIM 138 | 08/03/2021 | Population of the AltSPID and Last Alt SPID fields for internal use is a common occurrence and could result in misinterpretation of the entries by other Service Providers that receive this data. Cre… | Download |
| PIM 137 | 05/04/2021 | Clarification on ONSP Obligations to Remove Translations When 10-Digit Triggers Cannot Be Set | Download |
| PIM 136 | 04/06/2021 | LSMS Systems are not meeting industry throughput requirements. | Download |