Team, attached are the minutes of the March Operations meeting, recorded by Lorin Pollock (Sprint). Thanks Lorin! The items in italics I have added from my notes.
Barry
In attendance:
Robin Meier Ameritech
Kent Roberts Ameritech
Lorin Pollock Sprint
Rajeen Trika TCG
Stu McDowell TCG
David Strand AGCS
Bob Angevine GTE
Ron Steen Bell South
Kelvin Murray Perot Systems
Ed Elkin AT&T
Bettie Shelby World Com
Arthur Brett TCG
Gil Broyles Bell Atlantic
Larry Neeper Brooks Fiber Comm.
Fay Seymour Lucent
Jeannine Whalen Lockheed Martin
Sue Seitz Ameritech
Karen Kay Time Warner
Gene Johnston GTE
Barbara Bennett PacBell
Don Dabney SWBT
Larry Lovett Sprint
Darin Liston Sprint
Jim Joerger MCI
Dick Dowd LLC/ICC
Bill Belshaw MCI
Leigh Ann Clavenna MCI
Rick Jones IL NENA
Hampton Oberle MCI
Paul F. LaGattuta AT&T
Joan Ahern Bell Atlantic
Donna Navickas Ameritech
David Loose Sprint
Marcel Champagne Nortel/Perot
Larry Vagnoni Lockheed Martin
Larry Vasquez AT&T
Hazel Wagner Nortel/Perot
Barry Bishop Ameritech
LNP MEETING WEDNESDAY 3/12/97 8:30am
227 w. Monroe at AT&T Headquarters for the April Meeting
Minneapolis Rm 4th Floor (April 10-11) Take escalator to 2nd
floor, then elavator to 4th
floor.
Update of NANC Meeting by Phil of TCG.
Changed provisioning figures and verbiage which will
be delivered this am.
Phil went through the flow chart that changed at the NANC Meeting.
INTER-SERVICE PROVIDER LNP OPERATIONS FLOWS PROVISIONING (DRAFT) Fig 1 Iss.0.20
Box 5 changed
Box 10 changed
Box 14 Changed considerably
Box 17 changed
Box 24 verbiage changed
Discussion about when the process flows will be frozen
----- March 20th ???
The Illinois LNP deployment is on a tight time frame and cannot wait for National agreement.
An Ameritech position.
Ed of AT&T went through the "INTER-SERVICE
PROVIDER LNP OPERATIONS FLOWS--CANCELLATION FLOWS FOR PROVISIONING
PROCESS" narrative. Numerous changes were made changing
service order to subscription. Adding with the proper cause
code.
DMS10 LNP availability is June of 1998 with the same
characteristics as the DMS100 per NORTEL.
Continued review of "cancellation" process flow.
Remove note 11 from box 10 & 11 and the back
page.
Remove note 12 from box 13.
Subscription can only be activated from a pending
status should be noted somewhere in the operations document as
generic statement. "activation cannot occur at this point"
Agreed to make no change to box 13.
Box 16-- Change question to "Did information
match?" Agreed to delete box 16 in it's entirety.
LUNCH
Review of "CANCELLATION CONFLICT FLOWS FOR PROVISIONING
PROCESS" by Ed of AT&T.
Box 4 -- Change "transaction" to "subscription".
Ed to make changes and give disc copies to Lorin
and Barry.
1. End user decided to disconnect service.
1a. The current service provider initiates a disconnect
of service based upon their regulatory authority.
2. End User notifies current service provider of
desire to disconnect. The End User provides disconnect date
and negotiates intercept treatment with current Service Provider.
3. Current Service Provider arranges for intercept treatment.
The current Service Provider arranges intercept treatment as negotiated with the end user, or, when the disconnect is Service Provider initiated, per internal processes.
4. Current Service Provider creates and processes service order.
Current Service Provider follows existing internal
process flows to ensure the disconnect within their own systems.
5. Current Service Provider notifies NPAC of disconnect
and optionally effective release date. add NOTE 13: If no effective
release date is given the default will be immediate. The maximum
interval between disconnect due date and effective release date
is 18 months.
6 NPAC removes telephone number from its database on effective release date.
NPAC /SMS removes telephone number from their database
on effective release date.
7.NPAC notifies NPA NXX owner /holder of the disconnected telephone numbers effective release and disconnect dates.
8. NPAC broadcasts to all applicable service providers
to remove subscription(s) from their LSMS/SCP.
9. End
REPAIR PROCESS FLOW discussion as related to California process flow charts.
A motion was made to accept the Illinois version
without further changes.
*** Note *** Copies of Fig 5-7 verbiage have
been previously faxed and are also available with the associated
drawings (Power Point format) on the Internet at "http://www.ported.com"
under the Illinois workshop logo/ Operations.
Barry will bring copies of the timelines sent to
the FCC tomorrow.
Tomorrow we would like to go through the issues for review and the IVR unit questions.
Suggested at the 911 meeting that one central agency such as the State Police be allowed access to the IVR through whom all other agencies can go to for finding the service provider. Police agencies are not allowed to access the 911 ALI for information. They go to the service provider of the number in questions and trace/trap requests.
911 agencies do not have a requirement to have IVR
access.
Tomorrow's agenda
1. Holidays and business hours
2. Issues list
3. IVR questionnaire
4. New issues/business
5. Code opening time line discussion.
6. Review of LERG document.(maybe).
Phil stated that the LERG changes have been published.
Suggested that we should review that document.
MARCH 13 MEETING 08:30am
Reviewed FCC Test Plan letter and deleted "all"
in the 2nd sentence of the fourth paragraph on page 1. The words
"has successfully completed intra-network testing and"
from the 3rd paragraph on page 2 were deleted.
Disconnect Process Flow review of changes made yesterday and modifications were made which Barry noted and will re-issue to participates.
Definition of terms was completed - release date
and disconnect date.
Review of OBF issue #1290 by Jim J. of MCImetro.
Review of IVR questionnaire.
Add contact number of the Service Provider. Jim
J. stated if only Sp's use the IVR there is no need for the contact
number. Discussion of cable trouble and the Technician need to
identify and contact the correct service provider using the IVR.
The repair process includes utilizing the IVR to obtain service
provider name and number. Suggested that 8 ports be provided
for Law Enforcement and 8 for Service Providers with distinct
telephone numbers. Most IVR systems have standard set ups. Suggested
that NPAC tell the committee what they will have available. Lockheed
will return with characteristics of the IVR proposal to include
capabilities: # of ports, # of transactions per call, holding
time including keying pin # and # being queried, etc. Changed
to 3 distinct telephone numbers.
Major discussion of what should be listed as holidays-----specifically,
the day after Thanksgiving. MCI did not want the day after as
a holiday because they would anticipate that this would be a time
of movement of customers porting. Reached an impass about the
day after TG. Sprint can go with either decision. TCG agreed
to utilize the day after TG. All agreed that it would be a working
day.
The following are the days we have consensus on:
Christmas
New Years
Memorial Day
4th of July
Labor Day
Thanksgiving
The Business day hours that we had consensus
on are: 7 a.m. to 7 p.m. (Central)
Reviewed issues.
Issue 4: Closed Not a necessary item. Test
numbers exist today.
Issue 6-9: Refer to Switch Requirements team
to verify if capabilities are in the requirements document.
Issue 10: Closed On re-evaluation of issue
it was determined that this item is not a necessary function.
Issue 11: Refer to Switch Requirements team
to verify if capabilities are in the requirements document.
Issue 12: Closed On re-evaluation of issue
it was determined that this item is not a necessary function.
Issue 13: Closed (P) Item closed pending review
of the LERG for the required information.
Issue 14: Closed On re-evaluation of issue
it was determined that this item is not a necessary function.
Issue 15: Still Open Needs to be reviewed with
the NPAC and SCP team.
Issue 16: Still Open Needs to be reveiwed with
the NPAC team.
Issue 17: Closed NPA/NXX Code opening process
resolves this issue.
Issue 18: Closed Not a relevant issue.
Issue 19: Closed Resolved with NPAC/SMS Audit
capability.
Issue 21: Robin Meier (Ameritech) to check
with NIIF to verify if appropriate verbiage has been developed.
Issue 22-25: Barry Bishop will draft trouble
resolution document for these issues.
*****Note***** To minimize the fax's, the
above Issue documents will not be forwarded. Updated copies of
these issues will be available on the Internet at "http://www.ported.com".
They are located under the Illinois workshop logo/Operations.
Attached you will find two documents which
need to be discussed at the April meeting. The first from Ed Elkin
(AT&T) concerns the LRN assignment, and the 2nd
from Bryan Bentlin (Lockheed) the IVR.
If there are any major omissions or errors
to the above minutes, please let me know and I will have the minutes
corrected.
Barry Bishop
Operations Chairperson
Barry Bishop
Ameritech
ICC Workshop Operations Committee Chairperson
Barry,
As a follow-on to Brian Baldwin's LRN Assignment Guideline Proposal
(attached), I suggest a modification which will enable its convenient
use by all Facility Based Service Providers.
By revising:
"... use the lowest numerical NXX value assigned to a particular
(donor) switch, followed by all zeroes."
to read:
"... use a NPA NXX wholly assigned to the donor switch."
we allow all other considerations to be handled internally by each
Service Provider.
Thanks,
Ed Elkin
AT&T
----------------- Brian Baldwin's Proposal follows -------------
LOCATION ROUTING NUMBER ASSIGNMENT
PROPOSAL
I like to take this opportunity to propose a standard methodology for
assigning LRNs to ported numbers. Some parties have suggested the
assigning of different LRNs for a given (donor) switch to identify the
terminating rate center. Although today we do assign separate NXXs for
each rate center served by a particular switch, in the future this
will probably not prevail. The current assignment practices have
resulted in premature NPA exhaust situations, especially in Illinois
and many state PUCs, including the ICC are pressing the industry to
implement some form of number pooling. As such in the future we can
expect to see a limit of one NXX per switch unless/until all numbers
within have been assigned. In addition Bellcore has now reversed its
GUBB proposal for location portability and no longer utilizes the last
4 digits of the LRN for rate center
identification.
With this in mind to facilitate the adoption of a simple assignment
convention for LRNs. I propose that we use the lowest numerical NXX
value assigned to a particular (donor) switch, followed by all zeroes.
For example, if an office has e NXX assigned ie, 708-301-0000,
708-249-0000, 708-630-0000 the LRN value would always be 708-249-0000.
Although 1A ESS and the 5ESS switches have a specific designation for
each NXX (eg NOC 1, NOC 2, etc) Nortel and Siemens do not. As such I
believe that the only method of adopting a standard selection would be
numerical order. It must be remembered that LRNs were only intended to
identify the terminating switch for routing proposes. Use of LRNs for
any other propose may lead to major problems down the road. It should
also be remembered that signaling format allows the LRN value to also
be a working(and ported) number. Attempting to reserve certain
numbers in each switch for LRN assignment
seem counter productive.
Brian Baldwin
Ameritech
From Bryan Bentlin
To Barry Bishop
Barry,
I tried to page you, but wanted to follow up on email in case I didn't talk
to you.
In order to even size the new IVR needs that have been brought up, we need
to have the Operations Subcommitte send a formal request letter to the LLC
requesting that these enhancements be
sized.
We have been given the directive by Joe Fanlin to go through this
formalized process before beginning
any new assessments.
I was not aware of this, or I would have brought it up at the meeting
today. We can begin the assessment as soon as we receive the directive
from the LLC as a result of your formal request. Please run it by the
Operations Subcommittee and let me know
when the letter has been sent.
Call me if you have any questions,
Thanks,
Bryan