Change Orders

The Change Order section contains descriptions of the business functionality of the Number Portability Administration Center Service Management System (NPAC/SMS) as defined by the Number Portability Industry Forum (NPIF). The NPIF was formerly known as the Local Number Portability Administration Working Group (LNPA WG). Change Orders created/managed prior to the restructuring are identified with ‘NANC’ before the Change Order number. The NPIF has a direct relationship to the processes and systems that each Service Provider uses to participate in Number Portability. 

When a change in the NPAC software design is discussed at the NPIF, 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. Doc Only Change Orders may also be utilized to update Industry Specification(s) as required. 

In this section of the NPIF web site, all Change Orders ever considered are listed. The final Change Order document and the NPIF discussion notes, the Change Order status, and the identity of the software release in which the change order was implemented, are provided in the Change Order Summaries located below.

The status of a Change Order may be either Closed, Open, Requested, or Implemented. 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.
  • Requested – The NPIF has reached agreement on the Change Order and either a Statement of Work (SOW) may be requested and/or the requirements updates (Doc Only) will be included in a future version of the Industry Specification(s).
  • Implemented – The Change Order was adopted and has been implemented in the NPAC system.


Summary & Guidelines


Title Date Originated Description Status Document
NANC 171 11/01/1997 Audit Response Error Code Clarification Implemented Download
NANC 170 11/01/1997 ActivationTS vs BroadcastTS in IIS Flows Implemented Download
NANC 169 05/23/1997 Delta Download File Creation by Time Range for SVs Implemented Download
NANC 168 10/18/1997 SOA Bulk Download Files Closed Download
NANC 167 10/01/1997 ILL 3 Clarification Closed Download
NANC 166 09/29/1997 Flow 6.5.4.1 Modification Implemented Download
NANC 165 09/29/1997 Flow 6.5.5.2 Correction Implemented Download
NANC 164 09/25/1997 Duplicate NPA-NXX's and LRN's Implemented Download
NANC 163 09/25/1997 NPA Split Implementation Implemented Download
NANC 162 09/26/1997 TN-Attribute as GET-Replace Implemented Download
NANC 161 09/19/1997 Subsequent Port Flow Implemented Download
NANC 160 09/17/1997 Single TN in a Range Create Implemented Download
NANC 159 09/17/1997 Single TN in a Range Create Implemented Download
NANC 158 09/17/1997 Other Notification Recovery Implemented Download
NANC 157 09/10/1997 Key exchange interval default value Implemented Download
NANC 156 09/10/1997 6.5.3.1 Flow Modification Implemented Download
NANC 155 08/05/1997 End User Location Type and Value Definition Implemented Download
NANC 154 09/08/1997 Implementation of Key Validation Implemented Download
NANC 153 10/01/1997 Download file creation by SP for application of Filters Closed Download
NANC 152 09/04/1997 Audit Number of TNs Notification Implemented Download
NANC 151 09/04/1997 TN and Number Pool Block Addition to Notifications Implemented Download
NANC 150 08/27/1997 Subscription Version M-Delete to LSMS – Continued Closed Download
NANC 149 01/01/1998 Use of Time in the Due Date - Continued Closed Download
NANC 148 08/25/1997 LNPType in SV Object Creation Notification Closed Download
NANC 147 08/27/1997 Version ID Rollover Strategy Implemented Download