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 192 01/23/1998 NPA Split NPAC SMS Load File Implemented Download
NANC 191 01/19/1998 DPC/SSN Value Edits Implemented Download
NANC 190 01/19/1998 NPA Split Requirement 33 Interpretation Implemented Download
NANC 189 01/19/1998 Service Provider Allowable Functions Modification Implemented Download
ILL 188 02/24/1997 FRS RR5-38.3 Consistency Problem Implemented Download
NANC 188 01/19/1998 Mass Update Flow 6.7.4 Modification Implemented Download
ILL 187 02/22/1997 NXX split handling for 6 digit Closed Download
NANC 187 01/07/1998 Linked Action Replies Implemented Download
NANC 186 01/07/1998 Linked Notification Recovery Reply Closed Download
NANC 185 01/05/1998 Notification Recovery Error Response Implemented Download
NANC 184 01/05/1998 Response for Notification Recovery not Linked Implemented Download
ILL 183 02/14/1997 Download of Service Provider Data ASN.1 Issue Closed Download
NANC 183 01/05/1998 PDU Size Closed Download
NANC 182 01/07/1998 NPA-NXX effective date validation Implemented Download
ILL 181 02/24/1997 Key’s for EACH Service Provider Interface Implemented Download
NANC 181 12/08/1997 Tag Value Addition to the ASN.1 for NANC 146 Closed Download
NANC 180 12/07/1997 Key Exchange Security Strengthening Closed Download
NANC 179 11/25/1997 TN Range Notifications Implemented Download
NANC 178 11/25/1997 NANC 048 Clarifications Implemented Download
NANC 177 11/25/1997 Clarification to ILL3 Closed Download
NANC 176 11/15/1997 Modification of Status Change Cause Code Implemented Download
NANC 175 11/15/1997 Timestamp default when not set Implemented Download
NANC 174 11/14/1997 Removal of SOA and LSMS combined association Implemented Download
NANC 173 11/15/1997 Flow 6.5.2.1 Modification Implemented Download
NANC 172 11/05/1997 LSMS accepting downloads in the Flows Implemented Download