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
|NANC 539||03/05/2019||Vendor Certification and Regression Test Plan Updates – Doc Only Updates||Implemented||Download|
|NANC 538||03/05/2019||Expanded Deletion of Inactive SPIDs||Implemented||Download|
|NANC 537||12/05/2018||MUMP Due Date Matching||Implemented||Download|
|NANC 536||11/06/2018||MUMP Email Notification List||Implemented||Download|
|NANC 535||11/06/2018||Service Provider Deletion Validations for Alt SPID and Last Alt SPID||Implemented||Download|
|NANC 534||11/06/2018||Reference Data updates for new NPA-NXXs - Doc Only Change||Implemented||Download|
|NANC 533||11/06/2018||Audits with Activation Timestamp Range||Implemented||Download|
|NANC 532||11/06/2018||MUMP File Formats – Doc Only Change||Implemented||Download|
|NANC 531||09/12/2018||Recovery and Roll-up||Implemented||Download|
|NANC 530||09/11/2018||Hold/Replay Clarifications||Implemented||Download|
|NANC 529||09/11/2018||Multiple SVs for TN in BDD File||Implemented||Download|
|NANC 528||09/11/2018||Transition Related GDMO/ASN.1/XSD updates||Implemented||Download|
|NANC 527||06/05/2018||Modify SV AVC Notifications||Implemented||Download|
|NANC 526||06/05/2018||SIC SMURF File Production||Implemented||Download|
|NANC 525||07/10/2018||MUMP Mass Pooling||Implemented||Download|
|NANC 524||07/10/2018||MUMP File layouts – Near Term||Implemented||Download|
|NANC 523||04/24/2018||Implicit NPAC SMS Requirements||Implemented||Download|
|NANC 522||06/05/2018||BDD Files SSN Field||Implemented||Download|
|NANC 521||03/06/2018||Group & RR Testing – Doc Only Changes||Implemented||Download|
|NANC 520||03/06/2018||SIC SMURF Naming Convention – Doc Only Changes||Implemented||Download|
|NANC 519||03/06/2018||BDD File Compression||Implemented||Download|
|NANC 518||02/14/2018||PTO SV Create FRS Doc-Only Change||Implemented||Download|
|NANC 517||02/14/2018||Turn-Up Test Plan Doc-Only Clarifications||Implemented||Download|
|NANC 516||01/09/2018||XML Messages - Extraneous SPIDs||Implemented||Download|
|NANC 515||01/09/2018||LSMS XML Messages - Boolean Attributes||Implemented||Download|