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

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 cma@iconectiv.numberportability.com.

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 313 07/05/2000 FRS Documentation Only Change – Bulk Data Download Files for NPA-NXX-X and Block Data to be Delivered in GMT instead of Central Time. Implemented
NANC 312 06/14/2000 Different User Levels on the LTI Closed
NANC 311 06/05/2000 Query Message of SP Association Status Closed
NANC 310 02/18/2000 Time Reference in the NPAC SMS Closed
NANC 309 02/14/2000 Block Transition Diagram in FRS and IIS Implemented
NANC 308 02/09/2000 R3 GDMO update for First Port Notification Removal from NPA-NXX-X Object Implemented
NANC 307 02/04/2000 Change BDD Format for NPA-NXX and NPA-NXX-X Files Closed
NANC 306 01/24/2000 R3 GDMO update for WSMSC Package Implemented
NANC 305 01/24/2000 R3 ASN.1 documentation-only updates Implemented
NANC 304 01/24/2000 R3 GDMO documentation-only updates Implemented
NANC 303 01/24/2000 R3 IIS documentation-only updates Implemented
NANC 302 01/24/2000 R3 FRS documentation-only updates Implemented
NANC 301 01/12/2000 NPAC Monitoring of SOA and LSMS Associations via NPAC TCP Level Heartbeat (transport layer) Implemented
NANC 300 12/06/1999 7-digit Block Filters for Number Pooling Implemented
NANC 299 09/15/1999 NPAC Monitoring of SOA and LSMS Associations via Heartbeat Implemented
NANC 298 09/15/1999 Line Level Splits (10 digits) Closed
NANC 297 09/15/1999 Sending SV Problem During Recovery Implemented
NANC 296 08/24/1999 Documentation Change for Central Standard Time Implemented
NANC 295 08/19/1999 Documentation Updates to the National Number Pooling requirements, IIS Flows, ASN.1, GDMO Implemented
NANC 294 08/11/1999 Changing Due Date Edit Functionality in the NPAC SMS for 7PM on Due Date Problems Implemented
NANC 293 08/11/1999 Skipping Time Portion of Due Date Edits in the NPAC SMS Closed
NANC 292 07/07/1999 FRS Documentation Update – Query SV Valid Statuses Implemented
NANC 291 07/07/1999 SSN Edits in the NPAC SMS Implemented
NANC 290 06/14/1999 Documentation Change – FRS RR3-13.2 and R5-19.6 wording changes Implemented
NANC 289 05/27/1999 R3 Requirements Update – documentation only – from Pooling Assumptions walk-thru Implemented