NANPA / NOWG MEETING MINUTES

February 15, 2011

Contents

Attendees 1

Process Improvement Plan (PIP) Review 1

Monthly Operational Report (MOR) 1

NANPAComplaints 1

NANP Administration System (NAS) 2

CO Code Administration 2

Other NANPA Resource Administration 2

Numbering Resource Utilization/Forecasting (NRUF) 3

NPA Relief Planning 4

INC Activities 4

Number Administration Activities/Events/Projects 4

Action Item Review 4

Open Discussion 4

Next Meeting 4

Attendees

NOWG / NANPA
Jan Doell - Qwest
Paula Hustead – Windstream
Linda Richardson – AT&T
Natalie McNamer – T-Mobile
Karen Riepenkroger - Sprint
Rita Schmitz – CenturyLink
Laura Dalton – Verizon
Gwen Zahn – Verizon Wireless / Al Cipparone
Joe Cocke
Nancy Fears
Tom Foley
John Manning
Wayne Milby

Process Improvement Plan (PIP) Review

·  Review Existing PIP Status Report – On the following report, the item in red is one that was reported on in late January.

·  Areas Under Consideration for PIP Treatment - none

Monthly Operational Report (MOR)

·  Highlights of monthly activities – Items in red are new as of the last MOR document.

NANPAComplaints

·  New Complaints Received- no complaints to report

·  Status of Existing Complaints – no existing complaints on which to report

NANP Administration System (NAS)

·  Metrics/Benchmarks – Please see the “NANP Administration System (NAS)” section of the MOR document embedded above for metrics information.

·  Change Order Status – no open change orders on which to report

·  New/Ongoing Development Activities- Please see the “NANP Administration System (NAS)” section of the MOR document embedded above for information.

·  Client Usage/Difficulties Reported/Observed - John reviewed the following tickets:

·  On January 26, 2011, an external user reported that three codes returned to NANPA with a Part 3 approval date prior to December 31, 2010 were appearing on the Utilization Missing Report. NANPA concurred that these codes were incorrectly appearing on the report and implemented a change in NAS that removed these codes from the report. The ticket was open on 1/26/11 at 10:11am ET and closed 1/27/11 at 4:36pm ET.

·  On January 27, 2011, an external user indicated that a specific code appearing on the Utilization Missing Report should not be shown as assigned to the user. In researching this issue, it was discovered that NAS was displaying central office codes other than those assigned (e.g., codes identified as odd ball codes, special use codes or test codes) on the Utilization Missing Report. A fix was implemented on January 27. The ticket was open on 1/27/11 at 11:00am ET and closed the same day at 5:51pm ET.

·  Areas Under Consideration for System Improvement – nothing reported

·  NANPA website updates/modifications/enhancements - Please see the “NANP Administration System (NAS)” section of the MOR document embedded above for website information.

CO Code Administration

·  Metrics/Benchmarks –

Note - There were two CO code applications that exceeded the 7-day calendar window. Both applications were submitted through PAS and both were change requests. NANPA determined the NAS/PAS interface didn’t detect the applications. The response deadline for both applications was 1/28 (Friday). They were both processed on 1/31 (Monday). John indicated they are still determining potential causes and will report back to the NOWG once additional information has been acquired.

·  New Developments/Activities/Issues – none reported

·  Rate Center Changes/Consolidations – none reported

·  Training/Education Activities – Please see the “Code Administration” section of the MOR for more information.

Other NANPA Resource Administration

·  Metrics/Benchmarks

o  All metrics were met for January 2011.

·  Status of Resources

·  Other NANP Resources Developments/Activities/Issues – none reported

Numbering Resource Utilization/Forecasting (NRUF)

Metrics/Benchmarks -

Note - Under Performance Measurements (highlighted in yellow) - Starting this year, the processing timeframe was reduced from 21 calendar days down to 7.

Please see the “NRUF” section of the MOR document for additional NRUF information.

·  New Developments/Activities/Issues

·  Utilization Missing Report and Donation Discrepancy Report –

·  The NANPA is trying to do everything they can to bring the carriers’ attention to the reports.

·  NANPA advised that they’ve registered issues from both SPs and the states regarding the reports; some of which relates to the snapshot data for codes and blocks as of 12/31/2010.

·  Changes are being made by the SPs as they review the Utilization Missing and Donation Discrepancy reports. The Pooling Administrator, as appropriate, may make corrections to their assignment data based upon communications with SPs that have contacted them regarding specific records. Those corrections made in November and December 2010 would be included in the 12/31/10 snapshot. Any changes/corrections made after 12/31/10 to the PA assignment data would not be reflected in the 12/31/10 snapshot.

·  Regardless, NANPA believes the reports are serving to highlight potential data issues, which should be viewed as a positive step toward mitigating discrepancy issues.

·  The NANPA has heard the industry feedback (SPs and regulators alike) and is looking at what they can do to stay ahead of any issues. What NANPA proposes to do is update specific records in the snapshot in NAS that have been changed/corrected in PAS as a result of data discrepancies identified after 12/31/10. NANPA looks to possibly update the snapshot in the April 2011 timeframe.

A participant asked if there’s anything on the report that notifies users that they’re looking at a snapshot? NANPA indicated no- there isn’t anything there now that notes the Utilization data is from 12/31/2010.

A participant asked if NANPA has received any inquiries from states regarding the data? NANPA noted that they have not yet received inquiries from any states on the static data.

A participant asked if Regulators and Carriers know that the PA is the correct source for up-to-date information on blocks? NANPA noted that the only place the discrepancy comparison resides is in NAS. However, Regulators and SPs should know that to do in-depth research on the actual record, they would have to log in to the correct Administrator site to research the individual records.

If there’s a mistake in the pooling data or CO code data, unless that snapshot is changed, the error will continue to show up until the next NRUF is filed. NANPA noted that prior to CO 18’s implementation, the NOWG was advised that it will take multiple cycles to get the data cleaned up. SPs had an opportunity to clean up data in advance of the implementation. Any remaining discrepancies appeared on the current reports. During the transitional period, we will see the errors on the report until the next NRUF cycle.

·  Client Usage/Difficulties Reported/Observed – none reported

·  Areas Under Consideration for Improvement – See the “New Developments/Activities/Issues” section above for more information.

NPA Relief Planning

·  Metrics/Benchmarks

·  Status of Current NPA Relief Projects/Activities

In addition to what’s embedded in Wayne’s spreadsheet above, Wayne indicated he provided the 570 and 814 exhaust reports to the PA PUC on 2/14.

·  NANPA interactions with Industry and State Commissions on relief planning – please see the Relief Planning word documents above for additional information.

·  NPA Exhaust Date Changes – none reported

INC Activities

·  Summary of INC Issues/Contributions – no updates

·  NANPA Areas of Concern – Guidelines/Requirements – none reported

Number Administration Activities/Events/Projects

·  Review of industry/regulatory activities impacting number administration – none reported

·  FCC and NANC meeting/activities/reports – none reported

·  Status of Special Projects underway – none reported

Action Item Review

·  No action items on which to report

Open Discussion

·  The draft 2010 NANPA Annual Report to be forwarded to the NOWG near the end of the week. The NANPA is requesting feedback from the NOWG no later than 3/1 (sooner would be better, if at all possible).

Next Meeting

·  Next meeting is scheduled for 3/25 @ 1:00 PM EST