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 342 | 11/06/2001 | Doc Only Change Order for IIS: Flow B.5.1.5 – Text at end of this flow needs clarification. | Implemented | Download |
| NANC 341 | 11/06/2001 | Doc Only Change Order for GDMO: Section 7.0 LNP Subscription Version Modify Action – Clarification of allowable modify activities for subscription versions with status of ‘conflict’. | Implemented | Download |
| NANC 340 | 11/06/2001 | Doc Only Change Order for IIS: Update Appendix A | Closed | Download |
| NANC 339 | 10/05/2001 | Doc Only Change Order for IIS: Flow B.4.4.24 to include the Donor Disconnect notifications that get sent to the Donor SOA when a Number Pool Block De-pool occurs. | Implemented | Download |
| NANC 338 | 10/05/2001 | Doc Only Change Order for FRS: Add requirement for NPAC SMS sending subscriptionVersionDonorSP-CustomerDisconnectDate notifications to the Donor SP SOA when a Number Pool Block De-Pool occurs and update the note in requirement RR5-85. | Implemented | Download |
| NANC 337 | 10/25/2001 | Doc Only Change Order for IIS: Flow B.8.3 – note at the beginning of the text needs to be updated. | Implemented | Download |
| NANC 336 | 10/25/2001 | Doc Only Change Order for IIS: Flows B.4.4.3 and B.4.4.6 have typos that need to be corrected. | Implemented | Download |
| NANC 335 | 10/10/2001 | Doc Only Change Order for GDMO: Update GDMO to explain how the Primary/Secondary Service Provider situation works with Range notifications. | Implemented | Download |
| NANC 334 | 10/02/2001 | Doc Only Change Order for FRS: Clarification needed in Items L-11.0 F & G in Table C-7 of Appendix C in the FRS. | Implemented | Download |
| NANC 333 | 09/26/2001 | Doc Only Change Order for GDMO & IIS | Implemented | Download |
| NANC 332 | 09/10/2001 | Doc Only Change Order for FRS: Clarification of requirement RR5-42.1. | Implemented | Download |
| NANC 331 | 08/01/2001 | IIS Document Only Changes - Add missing flow for Subscription Version Create: Failure to Receive Response from New SOA after “Initial Concurrence Window” Expiration | Implemented | Download |
| NANC 330 | 07/13/2001 | IIS Document Only Changes to Multiple Flows | Implemented | Download |
| NANC 329 | 06/13/2001 | Prioritization of SOA Notifications | Implemented | Download |
| NANC 328 | 03/20/2001 | Tunable for Long and Short Business Days | Implemented | Download |
| NANC 327 | 03/19/2001 | FRS Document Only Change – Update Appendix C – System Tunables | Implemented | Download |
| NANC 326 | 02/02/2001 | IIS Document Only Change – Flow B.5.6: Subscription Version Query | Implemented | Download |
| NANC 325 | 01/25/2001 | GDMO Document Only Change – 4.0 LNP Subscription Version Cancel Action | Implemented | Download |
| NANC 324 | 01/25/2001 | IIS Document Only Change – Flow B.5.4.7.3: Subscription Version Disconnect With Effective Release Date | Implemented | Download |
| NANC 323 | 01/10/2001 | Partial Migration of a SPID via Mass Update | Implemented | Download |
| NANC 322 | 12/13/2000 | Clean Up of Failed SP Lists Based on Service Provider BDD Response File | Implemented | Download |
| NANC 321 | 12/13/2000 | Regional NPAC NPA Edit of Service Provider Network Data - NPA-NXX Data | Implemented | Download |
| NANC 320 | 11/01/2000 | NPAC Retries when Local System is in Congestion | Closed | Download |
| NANC 319 | 10/25/2000 | NPAC Edit to Ensure NPA-NXX of LRN is in Same LATA as NPA-NXX of Ported TN | Implemented | Download |
| NANC 318 | 10/11/2000 | FRS Documentation Only Change – Update Requirement RR3-49 NPA Splits and the Number Pool Block Holder Information – Mass Update that includes one or more Blocks for an NPA-NXX involved in a NPA Split. | Implemented | Download |