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 101 05/21/1997 Subscription Version Remove From Conflict Action Behavior modification Implemented Download
NANC 100 05/21/1997 NANC IIS 1.1, section 10 Subscription Version Status Row 1 Implemented Download
NANC 099 05/21/1997 NANC IIS 1.1, section 10 Subscription Version Status Row 2 Implemented Download
NANC 098 05/22/1997 TSAP data required in FRS Implemented Download
ILL 098 11/19/1996 Limit of Mass Update Range Closed Download
NANC 097 05/15/1997 OID usage and NpacAssociationUserInfo Implemented Download
NANC 096 05/12/1997 T2 Timers not on subscriptionVersionNPAC Implemented Download
NANC 095 05/12/1997 Reference: IIS NANC 1.1, section 4.2.2 Implemented Download
NANC 094 05/12/1997 IIS NANC 1.1, section 4.2.1 Implemented Download
NANC 093 05/13/1997 Date and Time in GDMO/ASN.1 Implemented Download
NANC 092 05/04/1997 Flow 6.5.3.2 Clarification Implemented Download
NANC 091 05/01/1997 IIS Section 4.2.2 Implemented Download
NANC 090 04/30/1997 SP Download Indicator Addition to IIS Closed Download
NANC 089 05/01/1997 Action Scoping and Filtering Support Implemented Download
NANC 088 05/01/1997 Id Naming attributes Non-zero Implemented Download
NANC 087 04/30/1997 RR5-39 requirement modification Closed Download
NANC 086 04/30/1997 Unique NPAC customer Ids Implemented Download
NANC 085 04/30/1997 Flow 6.5.5.1 Modification Implemented Download
NANC 084 04/30/1997 LnpNetwork behavior update Implemented Download
NANC 083 05/01/1997 NPAC Time Synchronization Implemented Download
NANC 082 04/18/1997 Audit Download Filtered LSMS Closed Download
NANC 081 04/18/1997 Audit Download Filtered LSMS Closed Download
NANC 080 04/18/1997 Audit indication of SP’s not Audited Due to a Download Filter Closed Download
NANC 079 04/18/1997 Multiple SPIDs per Service Provider LSMS Closed Download
ILL 079 11/19/1996 Notification Recovery Implemented Download