# Presentation: 585841

## LNPA Working Group

*LNPA Working Group*

- June 18, 1997
- Status Report
- LNP Administrative Task Force

## LNPA Working Group Charge

- May 2 LNPA Working Group Meeting
- Form administrative team open to all Working Group and Task Force members to address:
- LNPA Initial Deployment Oversight
- LNPA General Oversight
- NPAC SMS Change Management Process
- LNP Dispute Resolution Process
- Wireless LNP
- LNPA Working Group Co-Chairs to Address
- Number Pooling
- Location and Service Portability

## LNPA Administrative Task Force

- Invitation sent to all Working Group and Task Force Members
- Met on June 5-6, 1997, in St. Louis
- Meeting Objective
- Define Purpose and specific objective for each issue
- Perform preliminary discussions
- Determine Next Steps
- Identify team to complete each issue

## LNPA Initial Deployment Oversight

- _PURPOSE_
- To monitor compliance with the FCC LNP Order through the initial deployment of the regional LNPAs
- _PROPOSED PROCESS_
- Oversight Committee
- Chaired by Chief, Common Carrier Bureau
- Staffed by LNPA Working Group/Task Force Members
- Open to all interested parties
- LLCs report monthly to NANC on the following high level deployment milestones
- NPAC Data Center Operational
- Interoperability Testing
- Turn up Testing
- End-to-End Testing
- Production Implementation Complete
- Any jeopardy issues

## LNPA Initial Deployment Oversight

- _NEXT STEPS_
- Determine FCC desire to chair oversight committee
- Requested informally to Marian Gordon - FCC Designate to NANC
- Requested formally at June 10 NANC meeting
- Finalize Reporting requirements
- Frequency
- Content
- Establish process with LLCs
- _STATUS_
- LNPA T&O Task Force Co-Chairs to finalize process following LNPA Working Group input

## LNPA General Oversight

- _PURPOSE_
- Ensure that LNPA activities support FCC objective of neutral operation of the LNPAs and to ensure that national uniformity and interoperability in LNP administration is maintained
- _PROPOSED PROCESS_
- Neutral operations established for initial deployment and described in the LNPA selection criteria documented in the April 25, 1997, LNPA Selection Working Group report to NANC
- Neutral operations maintained in the future through LNP dispute resolution process currently under development
- National uniformity and interoperability achieved through NANC standards as recommended in the LNPA Selection Working Group report to NANC
- National uniformity and interoperability maintained through the change management process currently under development
- _STATUS_
- Issue Closed

## NPAC SMS Change Management

- _PURPOSE_
-     To provide an open and neutral process to submit and prioritize requests to add or modify features and functions to Number Portability Administration Center  Service Management Systems (NPAC SMS) in order to maintain standard features and functions across NPAC regions
- _INTERIM PROCESS_
- Process established to manage changes to industry requirements
- NANC Functional Requirements Specification (FRS)
- NANC Interoperable Interface Specifications (IIS)
- Administration Provided by Telecom Software Enterprises
- Subcontractor of Lockheed Martin, IMS
- Weekly Conference Calls
- Discuss requirements for open change orders
- Monthly Status Meeting
- Discuss new change order requests
- Develop requirements
- Prioritize change orders and assign to a specific release
- Update FRS/IIS as appropriate
- Change orders tracked on website
- Open change orders
- by Release
- Closed change orders
- by Release
- Future Release Open Change Orders

## NPAC SMS Change Management

- _PROPOSED PERMANENT PROCESS_
- Propose change requests to neutral body with broad industry representation
- Develop requirements and document in:
- NANC Functional Requirements Specification (NANC FRS)
- NANC Interoperable Interface Specification (NANC IIS)
- LLC’s develop vendor impacts
- Time and Cost
- LLCs approve change request
- Return to industry team for scheduling

## Proposed NPAC SMS Change Management Process

*Proposed NPAC SMS Change Management Process*

- Change
- Order
- Documentation

- Change
- Request

- Change
- Request

- Technical
- Discussions

- Develop
- IIS/FRS
- Specifications

- Develop and
- Document
- IIS/FRS
- Specifications

- Change
- Approved
- ?

- Review Change
- and Negotiate
- Vendor Costs

- Change
- Order
- Documentation

- Schedule
- Change
- Order

- End

- No

- Yes

- Change
- Management
- Administrator

- LNPA
- T&O
- Task
- Force

- LLC

- Change
- Request
- Documentation

- Successful
- Negotiation
- ?

- Yes

- No

## NPAC SMS Change Management

- _NEXT STEPS_
- Develop administrator selection process with Lockheed Martin and Perot Systems
- Finalize administrator requirements
- Finalize change management process
- _OPEN ISSUES_
- Are changes optional or are all LLCs/Service Providers required to deploy standard functionality?
- Does NANC or FCC want a continuing role in authorizing changes before deployment or does the industry group have the authority to implement changes on consensus vote?
- _STATUS_
- LNPA T&O Task Force to finalize
- Next meeting July 1-2, 1997

## LNPA Dispute Resolution

- _PURPOSE_
-   To produce a dispute resolution process so that LNP disputes can be escalated to NANC as an option to direct requests to commissions
- _PROCESS_
- Implement a process for public policy dispute resolution
- Use “Resolution of Numbering Disputes” as foundation

## LNPA Dispute Resolution

- _NEXT STEPS_
- Drafting committee to prepare proposal to present to LNPA Working Group
- AT&T/BellSouth/MCI/SBC/USWC
- Work with NANC Dispute Resolution Working Group to develop process document
- Work with LLCs to modify Operating Agreements to remove binding arbitration clause for public policy disputes
- _OPEN ISSUES_
- What disputes are subject to this process?
- How to satisfy non-NANC member companies that process is neutral?
- Who is the Administrator and the Expert Industry Body?
- _STATUS_
- Drafting committee met on June 13
- Preparing Draft for review at next LNPA Working Group meeting
- LLC Operating Agreement modification begin as soon as possible in LLCs

## Wireless LNP

- _PURPOSE_
-   To address and include wireless number portability requirements in LNP industry standards.
- _PROCESS_
- Identify where wireless LNP standards are required
- Identify wireless LNP issues requiring industry consensus
- Determine NPAC SMS requirements for wireless LNP
- _OPEN ISSUES_
- Rate Center boundaries - Architecture Report 7.3 vs. Wireless Report 1.6
- LRN Implementation - Architecture Report 7.2
- Call blocking on default routing - Architecture Rpt 7.10 vs. Wireless Rpt 1.7.1
- Call Scenarios - Architecture Report 8
- N-1 routing language - Architecture 7.8 vs. Wireless 2.2

## Wireless LNP

- _NEXT STEPS_
- Propose formation of LNPA Wireless/Wireline Integration Task Force
- _STATUS_
- First meeting of LNPA W/W Task Force scheduled for June 30, 1997

## LNP Administration Task Force

- No on-going role
- All work items assigned to another team
- LNPA Initial Deployment Oversight
- LNPA T&O Task Force Co-Chairs
- LNPA General Oversight
- Closed
- NPAC SMS Change Management Process
- LNPA T&O Task Force
- LNP Dispute Resolution Process
- Drafting Team
- AT&T/BellSouth/MCI/SBC/USWC
- Wireless LNP
- LNPA Wireless/Wireline Integration Task Force

## LNPA Proposed Dispute Resolution Process

- Publicize
- Dispute
- on www

- Select
- 3 member
- panel
- within
- 7 days2

- Prepare
- written
- report &
- recom-
- mendation

- Full
- NANC
- Review
- within
- 4 weeks

- Send
- recom-
- mendation
- to FCC
- within
- 7 days

- NANC
- Recom-
- mendation

- NANC
- Recom-
- mendation

- Develop
- Notice to
- Administrator
- and NANC
- within
- 10 days

- Document
- results

- End

- Yes

- Resolved
- in LLC
- ?

- Public
- Policy
- Dispute

- Apply
- Decisional
- Principles
- within
- 14 days

- Dispute
- Resolved
- ?

- No

- Yes

- No

- Notify
- parties of
- continuing
- Dispute

- Notice
- of
- Dispute

- Develop
- independent
- written
- report
- within
- 4 months

- NANC

- Expert
- Industry
- Body1

- Administrator1

- LLC

- 1 May be the LNPA Working Group or some other body appointed by NANC.
- 2 NANC Selects two (2) members/Initiating party selects one (1) member or non-member