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” process (PIM) 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 NP 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 (PIM) 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 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
PIM 135 04/06/2021 The XIS indicates that systems should accept a schema_version value with a different minor version than the XSD schema version used by the system. However, there are no vendor test cases that verify … Download
PIM 134 02/09/2021 Given the high-volume porting activity occurring across the industry, there has been an increase in LSMS LNP record growth rate for providers resulting in record capacity issues and concerns. Download
PIM 133 08/11/2020 Use of NPAC Data for preventing financial fraud is difficult due to missing or potentially inaccurate data. When numbers are given to Virtual Network Operators, it is difficult to find the service p… Download
PIM 132 08/11/2020 SPID Naming Standards adopted in PIM 117 need further updating to reflect another scenario Download
PIM 131 05/13/2020 LNP Best Practice 0004 – N-1 Carrier Methodology addresses the FCC requirement that the “N-1” carrier (2nd to last carrier) should perform the number portability database query. FCC 18-95 eased the C… Download
PIM 130 04/07/2020 As of 2020, the XML interface has been in production for several years. Over the past two years, there has been an increase in the number of systems using the XML interface. Through experience of u… Download
PIM 129 02/25/2020 Existing Best Practice 0069 indicates that users should inform the LNPA of large ports – defined as 25,000 or more TNs affected per hour – in advance of such porting activity, so that all service pro… Download
PIM 128 02/25/2020 The LNPA observes that LSMS operators are performing maintenance tasks outside of the scheduled maintenance windows on Sundays. When LSMS systems are unavailable, it has a detrimental effect on port… Download
PIM 127 09/10/2019 The Billing ID field for SVs is defined in the FRS as: “For future use. Can be variable 1-4 alphanumeric characters.” The Alt-Billing ID field is defined as a variable 1-4 character string (no limi… Download
PIM 126 07/09/2019 The XML Interface Specification (XIS), currently does not specify the Content Type to be used in interface messages except in the message examples. Since multiple Content Types can be used and have b… Download
PIM 125 07/09/2019 Prior to the NPAC Transition, a separate test plan document outside of the Certification and Regression Testing Plan was developed to test Notification Suppression (for XML) in NANC Release 3.4.8, pu… Download
PIM 124 03/05/2019 The LNPA has observed that on several occasions that the current service provider has attempted to modify an active subscription version (SV) by simultaneously submitting both a modify active request… Download
PIM 123 03/05/2019 iconectiv developed recovery capabilities based on NPAC SMS FRS requirements to allow CMIP-based local systems to recover Subscription Version and Network data elements. During industry discussions, … Download
PIM 122 03/05/2019 The Industry, through a series of discussions (dating back approximately 20+ years), concluded that the appropriate retry and time interval would be 1x15 due to messages not lost on interface so retr… Download
PIM 121 09/11/2019 During transition, it became apparent to iconectiv that there were a number of SPIDs in the NPAC database that were no longer in use. iconectiv has carefully planned a clean-up process for obsolete … Download
PIM 120 09/11/2019 The Alternate SPID attribute was introduced in NANC 399 in Release 3.3. The Last Alternate SPID attribute was then added in NANC 438 in Release 3.3.4. During transition, iconectiv noticed that a num… Download
PIM 119 09/11/2019 The NPA-NXX Create will be rejected if the ownership information is not present in the NPAC SMS industry reference data. Service Providers sometimes experience NPA-NXX Create rejections when they a… Download
PIM 118 07/05/2018 During transition, iconectiv was required to outreach to every SPID defined in the NPAC database or assigned to an NPAC user. One discovery was that some SPIDs were either choosing to not onboard or … Download
PIM 117 07/05/2018 One function of the LNPA is to assign SPIDs (NPAC Customer ID) and Names for approved applicants to NPAC. During the transition, iconectiv presented its SPID Naming methodology. No such defined metho… Download

141 results returned