In Attendance:
Phil Presworski TCG
Betti Shelby World Com
Donna Navickas Ameritech
Sue Seitz Ameritech
Ed Elkin AT&T
Walt Subora Ameritech
Dick Dowd MCI
Bill Belshaw MCI
Oc Jackson AT&T
Robin Meier Ameritech
Don Dabny SWBT
Mitch Fuchs AT&T
Daren Liston Sprint
Dick Anderson World Com
Jim Joerger MCI
Barry Bishop Ameritech
Team, the following are some very brief minutes
from our conference call. If their are any items misrepresented
or missing which you feel need to be corrected or added to the
minutes, please feel free to contact me.
The conference call had originally been scheduled to discuss the
NPA/NXX flows. Due to changes to the provisioning process flows
agreed upon by the NANC team last week, and subsequent decisions
by the ICC co-chairs and the LLC that the changes would be incorporated
in the initial phase, the meeting agenda was "re-aligned".
Donna Navickas (Ameritech) and Phil Presworski (TCG) gave the
group an overview of the changes to the flows (see flows previously
sent). The current agreements by the NANC team affect those portions
of the flows which mainly impact the NPAC. Additional agreements
and concurrence to the rest of the flows will be forthcoming
from the NANC team at a future date.
Some of the key changes are:
The Due Date is the same date as the Firm Order Commitment (FOC).
Due date is no sooner than 3 business days after the FOC is issued
(FOC to be issued within 24 hours of the LSR).
Order cannot be activated before the FOC date.
An order placed in conflict by the old service provider can stay
in conflict for 6 hours where only the old SP can remove the order
from conflict.
An order can only be out into conflict until noon prior to the
due date.
A two digit conflict cause code has been added. The old SP populates
the Conflict field.
Conflict codes have not been completely defined, but current process appears to have the following reasons:
No LSR
No FOC
Vacant #
Due Date does not match
This item appears to be open for further input. Do we have any
for the NANC team that we agree upon and/or feel is necessary?
Business days have been defined as a 12 hour day, Monday through Friday. The actual hours (6-6,7-7,8-8, etc) have not been defined. Holidays have not been defined. Again we can provide input on these items.
Based on these changes, there will be additional software modifications
by Lockheed to support the flows. It is anticipated that these
additional changes will require an additional 3 weeks, 3 days
to complete. It appears from the NPAC team perspective, that
this will slip their timeline on a day for day basis. This would
mean that the test team could not start the tests originally scheduled
for 7/1, until 7/28/97. Any additional delay in signing off by
the LLC participants could cause additional slippage on a day
by day basis.
Based on this, the FCC mandated field trial could not begin until
7/28/97. Discussion then focused on what could be done to shorten
the Testing time frame. It was the opinion of those on the conference
call, that the testing required for the field trial was already
at a point where it could not be condensed further and still be
a valid trial . It was agreed to by those on the call that
if testing began on 7/28/97, that testing could be completed by
9/26/97, with a final report written for the FCC by 10/17/97.
Please note that these dates are with the caveats that the
testing does not reveal any major problems which cannot be fixed
expeditiously.
With the above taken into consideration, the discussion moved
to when offices would be ready to port live customers on an ongoing
basis in MSA 1. After much discussion, it was suggested for the
purpose of the timeline that this be identified as the "Ready
to Port" date. It was agreed that baring any unforseen
complications that the date the initial offices would be "Ready
to Port" would be 9/29/97, with all offices that are
ready on that date, and succeeding offices identified by date
in the timeline.
The steering committee has mandated that the timeline be updated
based on the agreed upon flows, and a report be given at the next
Steering Committee meeting (2/19/97). The report (and timeline)
should reflect any slippage known or expected by each company
and the reason slippage is expected to occur. This would include
slippage which may or may not be directly attributable to the
change in the process flows. This would include slippage for internal
support systems, SCP/STP/SSP hardware and Software delivery, etc,
which would affect the ability of the carrier to participate.
I have asked the Operations team members to canvass their companies
internally to identify any issues, and attempt to bring the necessary
timeline information to the next Operations meeting where we can
do a quick review of the information. In any case I will need
the information no later than the end of day on Friday Feb 14th,
1997.
I would also like to ask all to review one more time, any possible
way to complete the NPAC and FCC trial testing without jepordizing
the validity of the testing of the results.
Earlier today a timeline was sent (with generic time frames) to
assist you in your timeline preparations.
I would also like to ask that each person who provided text for
the Illinois flow, to review the NANC flows for any necessary
changes, and bring the changes to the Operations meeting on Feb
11th and 12th.
In discussion with Dave Garner (Sprint) who is also part of the
NANC team, he told me that NANC has not put together the text
behind the process flows and may be very receptive to a submission
by this team.
Hope that covers it. Any questions, please feel free to contact
me.
Barry Bishop
Operations Chairperson
312-220-8000