SPID Migrations
How do I get added to the SPID Migration Notification List?
Please send an e-mail request to contact.updates@neustar.com. Please include the following information: Company Name, SPID, Contact Name, E-mail Address.
What information is needed to process a SPID Migration request?
A SPID Migration request, using either of the available submission methods, must contain:
- the Migrating-To SPID
- the Migrating-From SPID
- company contact information
- the NPA-NXX(s)
- LRN(s)
- Pool Blocks associated to the migrations (U.S. Only)
- LERG effective date
How do I submit a SPID migration request?
If you are an Authorized User for either the Migrating-To or Migrating-From Service Provider, there are two ways to submit a SPID Migration Request:
- Completing the SPID Migration Request Form and submitting the form to SPIDMigration@neustar.biz; or
- If you have access to the NPAC/SMS LTI GUI and have “SPID Migration” authorization on your logon, you can submit the request through the LTI GUI.
What are the fees associated with processing a SPID Migration?
There are no charges for submitting or processing a SPID Migration request.
Who determines if a SPID Migration is necessary?
The NPAC SPID Migration coordinator reviews the migration request and determines if a SPID Migration is necessary. If few Subscription Versions are affected by the SPID Migration, the coordinator may schedule a manual disconnect / reconnect of the affected Subscription Versions in order to update the code owner of the NPA-NXX.
How long does the overall SPID Migration process take?
Once the SPID Migration request has been reviewed for accuracy by the NPAC SPID Migration coordinator and the Migration request has been approved by the non-requesting Service Provider indicated in the request form, the migration is then scheduled at a minimum of 32 days from the receipt of the migration request on the next available SPID Migration date. It may take two to three days for the request to be scheduled, depending on the scope of the migration and the quickness in the non-requesting Service Provider response.
How many SPID migrations can be processed during a maintenance window?
For the U.S. Regions the following migration guidelines have been approved by the LNPA-WG:
No more than -
- 25 total migrations (nationally) per maintenance window;
- 7 migrations maximum per region;
- 500,000 SV per region.
What is a SPID Migration?
A SPID Migration is a coordinated update of the SPID attribute in the NPA-NXX, NPA-NXX-X (U.S. Regions only), and LRN as well as the respective Subscription Version or Number Pool Block (U.S. Regions only) record. NANC Change Order 323 defines this process.
Who can submit a SPID Migration request?
SPID Migration requests must be submitted by an Authorized User for either of the SPIDs involved in the migration.
How can I find contact information for the Migrating-To or Migrating-From SPID?
SPID Migration contact information for Service Providers is located on the NPAC Secure site, under NPAC User, Help Desk & Training.
Can a SPID Migration be scheduled prior to the 32-day minimum scheduling window? If so, how should I request an accelerated scheduling?
If a Service Provider has a need in accelerating the scheduling of a SPID Migration, the Service Provider can request a waiver of the 32-day minimum scheduling window by contacting the LNPA-WG Co-Chairs. Their contact information is found on LNPA Working Group.
When are SPID Migrations conducted?
SPID Migrations are only conducted during the NPAC Sunday maintenance windows. Some Sunday maintenance windows are not available (Black-out). These are usually the first Sunday of the month, holiday weekends, and other dates deemed to be blacked out by approval of the LNPA-WG.
The processing of the SPID Migrations occur at the beginning of the NPAC maintenance window (00:00 CT) and SIC-SMURF files are delivered to Service Provider FTP sites within the first hour of maintenance. This enables Service Providers to load and process the SIC-SMURF files within the Service Provider Maintenance Window.
What is a SIC-SMURF file?
Selection Input Criteria SPID Mass Update Request Files are files based on the affected data as it exists on the NPAC/SMS. Mechanized (SOA/LSMS) Service Providers use these files update their databases to the Migrating-To SPID.
When and how are SIC-SMURF files delivered?
For each SPID Migration scheduled for a particular date, there are two sets of SIC-SMURF files generated; a “Preliminary” and a “Final”.
- The “Preliminary” SIC-SMURF files are generated for each SPID Migration on the Wednesday one full week prior to the scheduled SPID Migration. These files are placed on Service Provider FTP sites for the provider to review the migrating data. These files are NOT to be downloaded and processed on their production SOA or LSMS systems.
- The “Final” SIC-SMURF files are generated at the beginning of the NPAC Sunday maintenance window for each SPID Migration scheduled for that date. These files are placed on Service Provider FTP sites for the provider to update their SOA and LSMS systems.
How do I receive notifications once a SIC-SMURF file is available?
Notifications through the SPID Migration distribution list are sent by the NPAC SPID Migration coordinator for both the “Preliminary” and the “Final” sets of SIC-SMURF files. If you wish to be included on the distribution list, please sent an e-mail to contact.updates@neustar.biz, and indicate the e-mail address or addresses that should be added.
How do I receive notifications once a SPID Migration request has been scheduled?
SPID Migration requests that are scheduled are sent through the SPID Migration distribution list. If you wish to be included on the distribution list, please sent an e-mail to contact.updates@neustar.biz, and indicate the e-mail address or addresses that should be added.
What is a Pending-Like SV Report?
Pending-Like SVs are Subscription Versions that are associated with the migrating LRN. Pending-Like SVs must be Activated or Cancelled prior to the processing of the SPID Migration during NPAC Sunday Maintenance windows.
Two reports for each SPID Migration request are generated by the NPAC SPID Migration coordinator and sent to Service Providers.
- The first report is e-mailed to the Primary and Secondary SPID Migration contacts for each company specified as the New or Old Service Provider in the Subscription Versions. This report is e-mailed on the Wednesday one full week prior to the scheduled SPID Migration.
- The second report is generated and e-mailed on the Thursday immediately prior to the scheduled SPID Migration. This report is again e-mailed to the Primary and Secondary SPID Migration contacts for each company specified as the New or Old Service Provider in the Subscription Versions.
When are Pending-Like SVs cancelled?
Service Providers have until 23:59 Central time on the Friday immediately prior to the scheduled SPID Migration to Cancel or Activate their respective Pending-Like SVs. At any time after 00:01 Central time on Saturday immediately prior to the scheduled SPID Migration, NPAC Personnel will Cancel the Pending-Like SVs.
The NPAC SPID Migration coordinator e-mails a “Cancelled, Pending-Like SV Report” to the Primary and Secondary SPID Migration contacts for each Service Provider involved in the ports by 17:00 Central time on the Monday immediately following the SPID Migration.
