------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Notice:

Effective August 1, 2017 the role of Change Management Administrator (CMA) of the Local Number Portability Administration Working Group (LNPAWG) for all US Regions was transferred to Telcordia Technologies, Inc., d/b/a iconectiv.

To contact the iconectiv CMA or to be added/removed from the LNPAWG distribution list please email cma@iconectiv.numberportability.com.

Please note that on or about September 30, 2017 the collection and history of industry documents will be transferred to https://numberportability.com/. Stay tuned for further updates at upcoming LNPAWG meetings and conference calls.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

NANC Change Orders

The NANC Change Order section contains descriptions of the business functionality of the Number Portability Administration Center (NPAC) Service Management System (SMS) as defined by the Local Number Portability Administration Working Group (LNPA WG), which has a direct relationship to the processes and systems that each Service Provider uses to participate in LNP.

When a change in the NPAC software design is discussed at  the LNPA WG, the proposed change eventually is described in the form of a change order.  The change order document describes the business need for the software change and, at a high level, the software changes required to implement the proposal.  As discussions progress, the technical portion of the change order is expanded to document both new software requirements and changes to existing software requirements that would result if the Change Order were implemented.  (Operational impacts of a change order are described in "Method & Procedures" documents issued before the change order is implemented.)  In this section of the NPAC.com web site, all change orders ever considered are listed.  The final change order document and the LNPA WG discussion notes, the change order's status, and the identity of the software release in which the change order was implemented are provided here.

 The status of a change order may be either Closed, Open, Implemented, or Requested.  These terms are defined as follows:

  • Closed – The change order was considered and rejected.
  • Open – The change order has been considered and there may be further discussion.
  • Implemented – The change order was adopted and has been implemented in the NPAC system.
  • Requested – The LNPA WG has asked the NAPM LLC to arrange for the change order's implementation, but the change order is not yet implemented.

Change Order Summary sent to LNPA WG distribution --> Change Orders

Change Order Implemented List sent to LNPA WG distribution --> Implemented Change Orders

Change Order Prioritization Guidelines --> Guidelines Document

NANC Change Orders

Change Order Date Originated Description Status
NANC 338 10/05/2001 Doc Only Change Order for FRS: Add requirement for NPAC SMS sending subscriptionVersionDonorSP-CustomerDisconnectDate notifications to the Donor SP SOA when a Number Pool Block De-Pool occurs and update the note in requirement RR5-85. Implemented
NANC 337 10/25/2001 Doc Only Change Order for IIS: Flow B.8.3 – note at the beginning of the text needs to be updated. Implemented
NANC 336 10/25/2001 Doc Only Change Order for IIS: Flows B.4.4.3 and B.4.4.6 have typos that need to be corrected. Implemented
NANC 335 10/10/2001 Doc Only Change Order for GDMO: Update GDMO to explain how the Primary/Secondary Service Provider situation works with Range notifications. Implemented
NANC 334 10/02/2001 Doc Only Change Order for FRS: Clarification needed in Items L-11.0 F & G in Table C-7 of Appendix C in the FRS. Implemented
NANC 333 09/26/2001 Doc Only Change Order for GDMO & IIS Implemented
NANC 332 09/10/2001 Doc Only Change Order for FRS: Clarification of requirement RR5-42.1. Implemented
NANC 331 08/01/2001 IIS Document Only Changes - Add missing flow for Subscription Version Create: Failure to Receive Response from New SOA after “Initial Concurrence Window” Expiration Implemented
NANC 330 07/13/2001 IIS Document Only Changes to Multiple Flows Implemented
NANC 329 06/13/2001 Prioritization of SOA Notifications Implemented
NANC 328 03/20/2001 Tunable for Long and Short Business Days Implemented
NANC 327 03/19/2001 FRS Document Only Change – Update Appendix C – System Tunables Implemented
NANC 326 02/02/2001 IIS Document Only Change – Flow B.5.6: Subscription Version Query Implemented
NANC 325 01/25/2001 GDMO Document Only Change – 4.0 LNP Subscription Version Cancel Action Implemented
NANC 324 01/25/2001 IIS Document Only Change – Flow B.5.4.7.3: Subscription Version Disconnect With Effective Release Date Implemented
NANC 323 01/10/2001 Partial Migration of a SPID via Mass Update Implemented
NANC 322 12/13/2000 Clean Up of Failed SP Lists Based on Service Provider BDD Response File Implemented
NANC 321 12/13/2000 Regional NPAC NPA Edit of Service Provider Network Data - NPA-NXX Data Implemented
NANC 320 11/01/2000 NPAC Retries when Local System is in Congestion Closed
NANC 319 10/25/2000 NPAC Edit to Ensure NPA-NXX of LRN is in Same LATA as NPA-NXX of Ported TN Implemented
NANC 318 10/11/2000 FRS Documentation Only Change – Update Requirement RR3-49 NPA Splits and the Number Pool Block Holder Information – Mass Update that includes one or more Blocks for an NPA-NXX involved in a NPA Split. Implemented
NANC 317 09/06/2000 Name Change to service-prov-download-reason in ASN.1 – ASN.1 Recompile Implemented
NANC 316 08/16/2000 Change the NSAP Field Size Declaration in ASN.1 – ASN.1 Recompile Implemented
NANC 315 08/10/2000 FRS Document Only Change – NSAP Field Size Implemented
NANC 314 07/05/2000 FRS Documentation Only Change – Subscription and Block Download File section in Appendix E have incorrect DPC data examples. Implemented