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

NANC Change Orders

Change Order Date Originated Description Status
NANC 401 01/13/2005 Separate LSMS Association for OptionalData Fields Open
NANC 400 01/05/2005 URI Fields Implemented
NANC 399 01/05/2005 SV Type and Alternative SPID Fields Implemented
NANC 398 09/27/2004 WSMSC data discrepancy situation with NANC 323 Migration Closed
NANC 397 07/28/2004 Large Volume Port Transactions and SOA Throughput Implemented
NANC 396 09/09/2004 NPAC Filter Management – NPA-NXX Filters Implemented
NANC 395 06/30/2004 LATA ID and NPA Split Reference Files Implemented
NANC 394 06/16/2004 Consistent Behavior of Five-Day Waiting Period Between NPA-NXX-X Creation and Number Pool Block Activation, and Subscription Version Creation and its Activation Implemented
NANC 393 05/06/2004 NPAC Updated Performance Requirements Implemented
NANC 392 03/11/2004 Removal of Cloned Copies of SVs and NPBs Implemented
NANC 391 01/07/2004 Doc-Only Change Order: FRS Updates Implemented
NANC 390 10/16/2003 New Interface Confirmation Messages SOA/LSMS- to- NPAC Open
NANC 389 10/16/2003 Performance Test-Bed Closed
NANC 388 v2 05/11/2006 Un-do a “Cancel Pending” SV Implemented
NANC 388 09/17/2003 Un-do a “Cancel Pending” SV Implemented
NANC 387 09/03/2003 Doc-Only Change Order: IIS Updates Implemented
NANC 386 07/24/2003 Single Association for SOA/LSMS Implemented
NANC 385 07/10/2003 Timer Calculation – Maintenance Window Timer Behavior Implemented
NANC 384 06/05/2003 NPAC Change Order Effectiveness Metrics Closed
NANC 383 05/06/2003 Separate SOA channel for notifications Implemented
NANC 382 04/04/2003 “Port-Protection” System Open
NANC 381 01/27/2003 Doc Only Change Order: FRS Updates Implemented
NANC 380 01/23/2003 Doc Only Change Order: IIS Updates Implemented
NANC 379 12/11/2002 Doc Only Change Order: Update IIS Flow, 5.1.18 Implemented
NANC 378 12/05/2002 Doc Only Change Order: Missing IIS Flow for cancellation of a disconnect-pending SV Implemented