ࡱ> ghfܥhc e<t84X0[DDp.000JzLLX0PR0D@.ίμJH|.6Title: Number Portability Administration Center (NPAC) Service Management System (SMS) Standards Date: October 9, 1997 Source: Co-Chairs - LNPA T&O Task Force Contacts: Bonnie Baca - AT&T Marilyn Murdock - SBC 20 Knightsbridge Road 500 East 8th Street Piscataway, NJ 08854 Kansas City, MO 64106 (732) 457-1681 (816) 275-3990 (732) 457-1456 (Fax) (816) 275-0683 (Fax) baca@att.com mm0771@sbc.com Abstract: This contribution contains a description of the work assigned by the FCC to the North American Numbering Council (NANC) in the 1996 LNP First Report and Order. The work described was principally carried out by the Local Number Portability Administration (LNPA) Technical and Operational Requirements (T&O) Task Force. Notice This contribution was prepared to assist the Committee T1 in understanding the nature of the standards work conducted to date by the LNPA T&O Task Force under the auspices of the NANC. The document is also intended to describe the ongoing activities of the LNPA T&O Task Force as directed by the FCC to the NANC and to define the policy role currently played by the NANC in the LNP arena. This document is offered to the Committee T1 as a basis for discussion and does not represent consensus of the LNPA T&O Task Force or the membership of the NANC. NPAC SMS Standards I. North American Numbering Council (NANC) A. NANC is a Federal Advisory Committee formed in October 1996 at direction of the FCC to, among other things, select independent third-party Local Number Portability Administrators (LNPAs) to manage a national system of regional LNP databases, to develop standards as may be required by these regional LNP databases, and to insure compliance with the FCC LNP implementation schedule of the top 100 Metropolitan Statistical Areas (MSAs). B. The FCC directed the NANC to address the following: 1. Determine what neutral third party or parties will be the LNPAs (i.e., Number Portability Administration Center (NPAC) vendors) 2. Determine whether one or multiple LNPAs should be selected 3. Determine how the LNPAs should be selected 4. Define the specific duties of the LNPAs 5. Define the geographic coverage of the regional databases 6. Develop various technical standards, including interoperability standards, network interface standards, and technical specifications 7. Develop guidelines and standards by which North American Numbering Plan Administrators (NANPA) and LNPAs share numbering information C. In November 1996, THE NANC established the LNPA Working Group, the LNPA Architecture Task Force, and the LNPA Technical & Operational Requirements (T&O) Task Force to carry out the FCC directives. These groups are open to all concerned parties and are representative of all segments of the telecommunications industry. The LNPA T&O Task Force was assigned responsibility for developing LNPA standards as described in 6 above. II. T&O Task Force Work Plan A. Create a repository of industry documentation from each region and state currently involved in LNP efforts. 1. Functional Requirements Specifications (FRS) Defines the functional requirements of the NPAC SMS, the hardware and software platform that contains the database of information required to effect the porting of telephone numbers. 2. Interoperable Interface Specifications (IIS) Contains the information model for the NPAC SMS mechanized interfaces, which reflect the functionality defined in the FRS. 3. NPAC SMS Provisioning Process Flows The following flows document the processes between the Service Provider and the NPAC SMS: Provisioning Provisioning Without Unconditional 10-Digit Trigger Provisioning With Unconditional 10-Digit Trigger Conflict Flow for Service Creation Provisioning Process Cancellation Flow for Provisioning Process Cancellation Conflict Flow for Provisioning Process Disconnect Process for Ported Telephone Numbers Audit Process Code Opening Process 4. Determine similarities and differences between the regional and state technical and operational documents. 5. Establish a single set of technical documents that each regional NPAC SMS, Service Providers, and related vendors must adopt in order to obtain NANC endorsement. 6. The LNPA T&O Task Force met frequently from December 1996 through April 1997 developing these standards documents. B. The LNPA T&O Task Force report, which incorporates the standards documents described in A1, A2, and A3 above, was endorsed by the NANC and released to the FCC on May 1, 1997, as an attachment to the LNPA Working Group Report. This report, which also attached the report of the LNPA Architecture Task Force, contained the following recommendations in response to the directives of the FCC: 1. Determine what neutral third party or parties will be the LNPA Recommendation RegionNPAC VendorNortheastLockheed Martin IMSMid-AtlanticLockheed Martin IMSMidwestLockheed Martin IMSSoutheastPerot Systems, Inc.SouthwestLockheed Martin IMSWesternPerot Systems, Inc.West CoastPerot Systems, Inc. 2. Determine whether one or multiple LNPAs should be selected Recommendation - It was the intention of the LNPA Working Group to select more than one (1) LNPA. Since the regions selected two (2) vendors, no recommendation was necessary. 3. Determine how the LNPAs should be selected Recommendation - The LNPA Working Group reviewed the selection criteria used in each state and region to ensure that the process satisfies the FCC LNP Order. The group concluded that the steps taken in each region satisfied the LNP Order, therefore, the process was recommended for adoption by the FCC. 4. Define the specific duties of the LNPAs Recommendation - Recommended adoption of the duties outlined in LNPA Architecture Task Force report and in the FRS and IIS. 5. Define the geographic coverage of the regional databases Recommendation - Recommended adoption of a seven (7) region structure with the selected LNPA vendor developing one (1) NPAC SMS in each region. The regions mirror the geographic territories of the original seven (7) RBOC territories. 6. Develop various technical standards, including interoperability standards, network interface standards, and technical specifications Recommendation - Recommended adoption of the FRS, IIS, and Provisioning Process Flows developed by the LNPA T&O Task Force as industry standards. 7. Develop guidelines and standards by which NANPA and LNPAs share numbering information Recommendation - The manner in which NANPA and the LNPAs might share numbering information is considered to be an aspect of number pooling and outside the original scope of the group. Therefore, no recommendation was made. C. The April 25, 1997, LNPA Working Group report also recommended future roles including: 1. Number Pooling - Address steps to achieve number utilization efficiency 2. LNPA Oversight - Develop a plan to oversee deployment of LNP in the top 100 MSAs 3. NPAC SMS Change Management - Develop a process to provide an open and neutral facility for submission and consideration of change requests to the NANC FRS and NANC IIS standards and to manage future releases of the NPAC SMS. 4. Wireless LNP - Develop a plan to incorporate wireless into the LNP process 5. LNP Dispute Resolution - Develop a process for handling public policy disputes concerning LNP D. The April 25, 1997, LNPA Working Group report, along with the report of the LNPA T&O Task Force, are available at the FCC website, http://www.fcc.gov/ccb/Nanc. Current versions of the NANC FRS and NANC IIS are available at http://www.npac.com. III. LNP Second Report and Order A. On August 18, 1997, the FCC released the LNP Second Report and Order. This Order adopted all recommendations made in the April 25, 1997, LNPA Working Group report. Therefore, the NANC FRS, NANC IIS, and Provisioning Process Flows are adopted as national standards by the FCC. B. The Order directs the NANC to continue its oversight role of LNP requiring NANC to maintain, update, and modify the technical and operational standards as necessary. C. The Order also adopted all future roles identified in the April 25, 1997, LNPA Working Group report. This includes a directive to the NANC to establish a change management process to manage change orders to the NPAC SMS for future software releases. D. The Order clearly establishes the NANC as the body to oversee the initial LNP deployment, to make recommendations to the FCC concerning LNP policy issues, and to resolve LNP disputes that concern public policy. IV. The LNPA T&O Task Force Change Management Process A. The LNPA T&O Task Force developed and implemented a change management process during its initial phase to deal with change orders requesting modification or new features or functions to the FRS and IIS and to schedule future software releases by the NPAC vendors. B. The change management process has been improved over the last six (6) months resulting in a procedure endorsed by the members of the LNPA T&O Task Force. Work is currently underway to gain the endorsement of the Limited Liability Companies (LLCs), the regional entities responsible for contracting with and managing the activities of the NPAC vendors. A flow diagram and associated descriptions of the change management process is contained in Attachment A. IV. Conclusion A. In the LNP Second Report and Order the FCC clearly directs the LNPA T&O Task Force, under the auspices of the NANC, to continue its role in managing any changes to the LNP Provisioning Process Flows, the FRS, and the IIS requirements. This includes controlling the change management process to ensure a neutral facility for industry members to request modifications or new features or functions to the NPAC SMS and to schedule appropriate future releases. Therefore, there is no current need to bring this activity under an ATIS committee. B. In addition, in the LNP Second Report and Order, the FCC directs that the NANC be the body responsible for establishing national LNP policy. It is therefore recommended that the Committee T1 establish a communication vehicle to keep the NANC apprised of LNP activities undertaken in the future. Attachment A NPAC SMS Change Management Process NPAC SMS Change Management Process StepDescription1. and 2. Change RequestChange requests can originate in the LLC, in the T&O Task Force or by others who refer change requests to either the LLC or the Task Force. All requests will be documented in a standard format and forwarded to the Change Management Administrator (CMA). 3. Document and Publish Change RequestThe CMA will accept all change requests and will track requests for the T&O Task Force. 4. Document and Publish Change OrdersThe CMA will document all change requests as change orders in a standard format and will publish change order summaries on a web site. 5. Technical Discussions The T&O Task Force will host weekly conference calls and monthly meetings to discuss all change orders submitted as change requests to the CMA. These meetings provide an open forum for all interested Service Providers and vendors. 6. Technically Feasible? The T&O Task Force members will determine the technical feasibility of each change order. Where change orders are determined to be unfeasible, alternative solutions will be explored and the results communicated to the originator of the change request. 7. Develop Requirements The T&O Task Force will develop system or interface requirements at a level appropriate for LLC and vendor consideration. 8. Document and Publish Requirements The CMA will document the requirements for each change order and will make these requirements available to the T&O Task Force.  9. Sanctioned Core Requirement? The T&O Task Force will evaluate each change order to determine if it satisfies the following definition of a Core Requirement:A Core Requirement is one that is sanctioned by the T&O Task Force and is necessary for all regions to implement in order to maintain uniform NPAC interfaces and operation.Core Requirements will be grouped together at the discretion of the T&O Task Force and will be transmitted to all LLC chairpersons with copies to the LLC project executives. A 45 calendar day turn around will be requested of the LLC by the T&O Task Force co-chairs. 10. Review Change and Negotiate Vendor Costs The LLCs will receive requirements from the T&O Task Force and will negotiate with the NPAC vendor concerning costs and potential development schedules. 11. Successful Negotiation? Information regarding the status of LLC negotiations will be formally transmitted to the T&O Task Force co-chairs by the LLC Chairpersons within 45 calendar days of receipt.Successfully negotiated requirements are returned to the T&O Task Force co-chairs for specification development; unsuccessfully negotiated requirements are returned for additional discussion and consideration by the T&O Task Force. 12. Sanctioned Optional Requirements? Requirements that are not sanctioned as Core Requirements are evaluated against the following criteria to determine if they are optional requirements sanctioned by the T&O Task Force?An Optional Requirement is one that is sanctioned by the T&O Task Force and is not a core requirement.These requirements are implemented at the discretion of each LLC.13. EndRequirements determined to be neither Core nor Optional Requirements sanctioned by the T&O Task Force are removed from further consideration. LLC may decide to implement such requirements at their discretion. A reference list will be maintained by the CMA of these requirements and where they were implemented. 14. Develop IIS/FRS Specifications The T&O Task Force will develop IIS and/or FRS Specifications for each Sanctioned Core and Sanctioned Optional Requirement. 15. Document and Publish IIS/FRS Specifications The CMA will document the IIS and FRS Specifications for each Sanctioned Core and Sanctioned Optional Requirement. 16. Prioritize and Package Release The T&O Task Force will review all sanctioned requirements and will, based on the input of the LLCs as appropriate, schedule a group of sanctioned requirements into a release. 17. Document and Publish Release The CMA will combine and publish the change orders contained in each scheduled release. 18. Schedule ReleaseThe T&O Task Force will release the agreed upon schedules to the vendors and LLCs.  Committee T1 Contribution LNP Technical Requirements  DATE 10/1/97 Page  PAGE 7  DATE 10/1/97 Page  PAGE 9  DATE 10/1/97 Page  PAGE 12  77/=nnnn/=nnnn=/SSS7n a:f@-:$ 0:&B} $ &&TNPPb=Pu & TNPP &&TNPP  }B E "--"Britannic Bold-.  :2 ?"NPAC SMS Change Management Process~EFz|tE{{|ttKFc~qton "- 1n1$(Times New Roman-.  <2 dDocument:(#(?#(Times New Roman -.  <2 hO and Publish$((,(( (Times New Roman-.  <2 - Requirements5$((#>$(Times New Roman -.  <2 " Review Change5$($96(#(($Times New Roman-.  <2  and Negotiate$((9$(($#Times New Roman -.  <2  Vendor Costs:#(((5(Times New Roman-.  <2 `Schedule,$($((#Times New Roman -.  <2 Release5$$#$ & Times New Roman-.  < 2 End;00 &--"Systemn-v@; "-9p--'-  $_h _ --@+ "-ee%--'-  $eKPe --@g "-8e8--'-  $Rw8nw8; --k@c "-ae--'-  $vT]T --@q "-eke--'-  $ZceZKe --@c "-aJJ--'--@RV "-LT--'--@] "-V[V--'-  $plVcLN"Britannic Bold-.  0; 2 Task>@9?"Britannic Bold-.  0;2 vForce<A3;<"Britannic Bold-.  0; 2 ~LLC==H ---@ z-  $x4x<<4  $4<<4  $4<<4  $848$(Times New Roman-.  0;2  Sanctioned,$($((#(Times New Roman -.  0;2 Z,Optional:((($Times New Roman-.  0;2  Requirement5$((#>$( & "--!Times New Roman -.  0; 2 Z?End;00 &Times New Roman-.   | 2 No:(---@- "-[['--'-  $u[AR[Times New Roman -.  ['2 -1Develop4 $ $$Times New Roman-.  0;2 5IIS/FRS((0(Times New Roman -.  0;2 Specifications($  $$ ---@@ "-eye>--'-  $hqehKe --@s "-eme--'-  $\ee\Ke --@F "-[D[--'Times New Roman -.  [2  Prioritize$ Times New Roman-.  0; 2 K@and Times New Roman -.  0;2 Package$  Times New Roman-.  0;2 Release+---@0 "-.--'-  $j "-- aP PTimes New Roman -.  2 Document:(#(?#(Times New Roman-.  0;2  and Publish$((,(( (Times New Roman -.  0;2 eIIS/FRS-,6,Times New Roman-.  0;2  Specification,($$#$((Times New Roman -.  0;2 [Document:(#(?#(Times New Roman-.  0;2 8F and Publish$((,(( (Times New Roman -.  0;2 Release5$$#$Times New Roman-.  0; 2 1 Times New Roman -.  0; 2 p2 Times New Roman-.  0; 2 0p3 Times New Roman -.  0; 2 04 Times New Roman-.  0; 2 P5 Times New Roman -.  0; 2 6 Times New Roman-.  0; 2 P7 Times New Roman -.  0; 2 0yNo. Times New Roman-.  0; 2 0Yes.Times New Roman -.  0; 2 p9 Times New Roman-.  0; 2 p12 Times New Roman -.  0; 2 p13 Times New Roman-.  0; 2  14 Times New Roman -.  0; 2 16 Times New Roman-.  0; 2 18 Times New Roman -.  0; 2 08 Times New Roman-.  0; 2 15 Times New Roman -.  0; 2 P17 Times New Roman-.  0; 2 19 Times New Roman -.  0; 2 @10 Times New Roman-.  0; 2 `11 &TNPP &---bcy{!#67bp6D$t.< !$$''&+Z+\++++;;;;2<4<5<;<<<C<D<L<M<S<T<U<V<W<X<Y<_<`<g<h<<< PacPcuDPcacc uDc uD=cU^]c4^c]]cchcc ]c L<<<<<<<<<<<<<<<<<<<<<ucac uDcc PacuDPcPcbcyz{4V!"67c R  D p 6 O;;e '& ' ( ) 1%-qe '& ' ( ) 1%-q#6 o0$qQq  4   4  4 4   4;;O; $1e-]kB~]]  4  4  4  4 J  4() ';<I]^fz{ l ;c' 4 4;O;G6qkO !!4""#$$%''''))&I&I&I&a&I&I&I&I&I&&I&I&I&a&I&I&I; 4;O; 4 l ;c')$+%+&+'+(+)+6+7+Z+[++++++++&I&@&@&@&@&@&@&I&Il {b' 4 4; 4+++,,,,/-0-1-W---zE^z`l {b'! $ 4l {b'  !  4l {b' ----....////0000000:1;1~`{~`l {b' l {b' $! $ 4l {b' ;1<1>1_1`111122233smKH! $ 4Vl {b'l {b'!  4l {b'   3333f4g4h4444555656 6!6oSl {b' !  4l {b'$! $ 4Vl {b'!6H6I6777j7k7l77778889999|jl {b'l {b'l {b'l {b' ! $ 49999::;:<:`:a:;;;4;5;cl {b' ! $ 4l {b'!  4Vl {b' 5;;;;;;;;;;<2<3<4<W<X<<<<<<~~=7`!zxttt:7& ( 4l {b'  l {b' !  4<<=7`! 4K@Normala c"A@"Default Paragraph Font @ Header ! @ Footer !)@ Page Number&(89<<< !!      ! ! ! ! #p H^$&(\(=.489vah# 7[<PQ6 $)+-;13!695;<<RSTUVWXYZ[\]^_7>FOVX[bj!!!9""896Colleen Davies$C:\MSOFFICE\WINWORD\Committee T1.doc@HP LaserJet 5P/5MP PostScriptLPT1:PSCRIPTHP LaserJet 5P/5MP PostScriptHP LaserJet 5P/5MP PostScriptg odXX$$PRdCustom page 1XCCCustom page 2XCCCustom page 3XCCHP LaserJet 5P/5MP PostScriptg odXX$$PRdCustom page 1XCCCustom page 2XCCCustom page 3XCC""""[Times New Roman Symbol &Arial&Britannic BoldMonotype Sorts"1h fF >. d YaTitle: Number Portability Administration Center (NPAC) Service Management System (SMS) StandardsColleen DaviesColleen Davies  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdejrRoot Entry<$4` Fy;ʼίμi WordDocument& !`tCompObj<!!jSummaryInformation&(<"^$$  FMicrosoft Word Document MSWordDocWord.Document.69qOh+'0 0<HX p|    bTitle: Number Portability Administration Center (NPAC) Service Management System (SMS) StandardsFColleen Davies HADocumentSummaryInformation8 4՜.+,0HP`hp x AT & Td bTitle: Number Portability Administration Center (NPAC) Service Management System (SMS) StandardsNormalColleen Davies9Microsoft Word for Windows 95@%@ͼ@ʼ@$Ppμ >.՜.+,0HP`hp x AT & Td bTitle: Number Portability Administration Center (NPAC) Service Management System (SMS) Standards