------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Notice:

Effective August 1, 2017 the role of Change Management Administrator (CMA) of the Local Number Portability Administration Working Group (LNPAWG) for all US Regions was transferred to Telcordia Technologies, Inc., d/b/a iconectiv.

To contact the iconectiv CMA or to be added/removed from the LNPAWG distribution list please email [email protected].

Please note that on or about September 30, 2017 the collection and history of industry documents will be transferred to https://numberportability.com/. Stay tuned for further updates at upcoming LNPAWG meetings and conference calls.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

NANC Change Orders

The NANC Change Order section contains descriptions of the business functionality of the Number Portability Administration Center (NPAC) Service Management System (SMS) as defined by the Local Number Portability Administration Working Group (LNPA WG), which has a direct relationship to the processes and systems that each Service Provider uses to participate in LNP.

When a change in the NPAC software design is discussed at  the LNPA WG, 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.  (Operational impacts of a change order are described in "Method & Procedures" documents issued before the change order is implemented.)  In this section of the NPAC.com web site, all change orders ever considered are listed.  The final change order document and the LNPA WG discussion notes, the change order's status, and the identity of the software release in which the change order was implemented are provided here.

 The status of a change order may be either Closed, Open, Implemented, or Requested.  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.
  • Implemented – The change order was adopted and has been implemented in the NPAC system.
  • Requested – The LNPA WG has asked the NAPM LLC to arrange for the change order's implementation, but the change order is not yet implemented.

Change Order Summary sent to LNPA WG distribution --> Change Orders

Change Order Implemented List sent to LNPA WG distribution --> Implemented Change Orders

Change Order Prioritization Guidelines --> Guidelines Document

NANC Change Orders

Change Order Date Originated Description Status
NANC 188 01/19/1998 Mass Update Flow 6.7.4 Modification Implemented
NANC 187 01/07/1998 Linked Action Replies Implemented
NANC 186 01/07/1998 Linked Notification Recovery Reply Closed
NANC 185 01/05/1998 Notification Recovery Error Response Implemented
NANC 184 01/05/1998 Response for Notification Recovery not Linked Implemented
NANC 183 01/05/1998 PDU Size Closed
NANC 182 01/07/1998 NPA-NXX effective date validation Implemented
NANC 181 12/08/1997 Tag Value Addition to the ASN.1 for NANC 146 Closed
NANC 180 12/07/1997 Key Exchange Security Strengthening Closed
NANC 179 11/25/1997 TN Range Notifications Implemented
NANC 178 11/25/1997 NANC 048 Clarifications Implemented
NANC 177 11/25/1997 Clarification to ILL3 Closed
NANC 176 11/15/1997 Modification of Status Change Cause Code Implemented
NANC 175 11/15/1997 Timestamp default when not set Implemented
NANC 174 11/14/1997 Removal of SOA and LSMS combined association Implemented
NANC 173 11/15/1997 Flow 6.5.2.1 Modification Implemented
NANC 172 11/05/1997 LSMS accepting downloads in the Flows Implemented
NANC 171 11/01/1997 Audit Response Error Code Clarification Implemented
NANC 170 11/01/1997 ActivationTS vs BroadcastTS in IIS Flows Implemented
NANC 169 05/23/1997 Delta Download File Creation by Time Range for SVs Implemented
NANC 168 10/18/1997 SOA Bulk Download Files Closed
NANC 167 10/01/1997 ILL 3 Clarification Closed
NANC 166 09/29/1997 Flow 6.5.4.1 Modification Implemented
NANC 165 09/29/1997 Flow 6.5.5.2 Correction Implemented
NANC 164 09/25/1997 Duplicate NPA-NXX's and LRN's Implemented