NANC 318

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.

Origination Date :10/11/2000

Originator:ESI

Description:

Currently this requirement states that either the Old or New NPA-NXX can be used for a Mass Update to a NPA-NXX that is in permissive dialing.  This is incorrect as the Mass Update functionality does not do split processing.

Existing 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 an NPA Split

NPAC SMS shall accept a mass update request that could span one or more Blocks from NPAC personnel, with either the old NPA-NXX or the new NPA-NXX for an NPA-NXX that is currently in permissive dialing.  (Previously B-552)

Suggested Updated 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 an NPA Split

NPAC SMS shall process a mass update request from NPAC personnel that spans one or more Blocks that are part of an NPA Split that is currently in permissive dialing only when the new NPA-NXX is used.

Final Resolution:

During NPAC Release 3.0 testing there was a test case (5.2) that required NPAC Personnel to do a mass update on Number Pool Blocks during permissive dialing period using the Old NPA.  The NPAC SMS responded with a message that “0 SV records would be affected”.  A defect was opened.  The NPAC vendor responded that mass updates did not do split processing.  This was presented to the LNPA WG during the October ’00 meeting and it was explained to the group that this was not functionality that should be implemented because it was too dangerous.  The group agreed and decided that the requirement being tested in the above test case should be modified and the test case revised.  The test case was revised and distributed to the industry.  This document only change order would modify the affected requirement.

November 00 – Change order was accepted and moved to ‘Next Documentation Release Change Orders’.

Related Release:

3.0.2

Status: Implemented