[694] in I/T Delivery
5ESS Uprade and Replacement Project
daemon@ATHENA.MIT.EDU (Lu Keohane)
Fri Feb 8 18:23:15 2002
Message-Id: <5.0.2.1.2.20020208181907.00a4bce0@hesiod>
Date: Fri, 08 Feb 2002 18:23:05 -0500
To: delivery@mit.edu
From: Lu Keohane <lu@MIT.EDU>
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="=====================_25287993==_.ALT"
--=====================_25287993==_.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Project Notebook
Project Name: 5ESS Upgrade and Replacement
Project Leader: Louise T. Keohane
Report Date: February 7, 2002
URL: http://web.mit.edu/is/delivery/5ess/
Accomplishments in the Month of January:
=B7 Programmed the of 3A Translator and will begin to test on-line=
with=20
the Voice Mail system.
=B7 Relocated all ACD links on the MDF
=B7 ACD Hardware identified and will be ordered.
=B7 ACD Software and RTU (right to use) fees being negotiated with=20
Lucent/Avaya and IEX Corp.
=B7 Plans to install and test new ACD hardware & software have begun.
=B7 Resolved SM1 issues associated with the modem pool lines.
=B7 Continue to Build and make modifications to the database for the=
=20
new ICE9 program that simulates the new 5ESS.
=B7 Have performed some testing of the ICE 9 database and will=
continue=20
after code modifications are complete.
=B7 Testing of analog and ISDN services is as follows:
o E19 70% of analog & 31% of ISDN
o 24 80% of analog & 11 % of ISDN
o NW12 96% of analog & 59 % of ISDN
o Total Analog lines tested: 9,522
o Total ISDN lines tested: 9,944
=B7 Verify testing plan from all 3 locations including IVR, ACD,=
VMail,=20
Modem pool, etc.
=B7 Continued to host meetings with the Lucent=92s management team to=
=20
investigate options on an interim basis to providing additional=20
ISDN/analog services from NW12 and Bldg. 24 until the new cutover date=20
(e.g. at least a few months). Both of these two options that=20
Lucent provided were not sufficient, as they did not meet MIT=92s=20
requirements.
=B7 5EOps suggested a third option, to place EXM 6 in the hallway of=
=20
Bldg. 24. After working with Facilities on a preliminary walk=20
through of space needed and available in the existing corridor, we=20
presented this option to Lucent. Lucent is very resistant to=20
performing this work before cutover.
o FYI: Lucent, due to space constraints within the building 24=20
switch room, designed EXM 6 to be placed after the removal of the old 5ESS=
=20
classic equipment. The expected time line for installing EXM6 after=20
cutover is a minimum 30 days (again, after the old equipment is=20
removed). Had the cutover taken place on Martin Luther King weekend, MIT=20
would have had plenty of time to remove the classic equipment out, install=
=20
EXM 6 and load balance both EXM 5 & 6 to provide the appropriate dial tone=
=20
to meet customer demand and project schedules. Setting up a new cutover=20
date, MIT, would have taken into consideration the additional 30 days for=
=20
EXM 6 to come on-line.
=B7 Lucent had many reasons why they could not perform option three=
and=20
the 5E Ops team had as many reasons why they could and should:
1. Lucent would require a minimum of $400k with a maximum of $500K to=
=20
perform this work. (EXM 6 has always been part of the original proposal,=20
so MIT has already contracted to pay Lucent to install this equipment in=20
Bldg. 24 as part of the overall project).
o When trying to get Lucent to identify the equipment that MIT would=
=20
require now for approximately $400-500K, they agreed to provide a=20
printout. None of the 5ESS Project team to date, has seen any=
documentation.
2. Lucent=92s sales team suggested that the room wouldn't be ready soon=
=20
enough and it would move the cutover date out to 30 days. Accepting the=20
additional 30 days, and suggesting the room could be built within a week=20
(thanks to Joe Collins in Facility), Lucent turned back to needing the=20
additional monies ($400-500K) to perform the extra work.
=B7 An example of what would the scenario look like if we performed=
the=20
cutover in April: I/S announces the new cutover date (e.g. April 15th=20
), to the community. Yet, we also tell the community that not only are we=
=20
cutting over, but as of April 15th and until at least June 1st, we can not=
=20
provide any additional ISDN or analog services from the Bldg. 24=20
switchroom. (Doesn't seem like a viable plan to me since Lucent has been=20
unable to commit to all goals mutually agreed upon since the start of this=
=20
project. Also, it=92s very possible that the 30 days they are suggesting it=
=20
will take is more realistically like > 45 days). Also, MIT chose not to=20
cutover on MLK weekend, because Lucent had less than 40% of all analog=20
lines accurately configured and wired on the new switch. They hadn't even=
=20
begun the verification process for the ISDN lines and given that the analog=
=20
failed at such a high rate, we consider we were looking at a higher rate of=
=20
failure on the ISDN lines. Estimated to be around: 10% accurate. (Need I=
=20
say more)?
3. Lucent then presented to MIT that we would have a contamination=20
issue and we would need to sign a waiver that relieved Lucent for ANY=20
failing equipment from the 24 switchroom. First, let me say, since being=20
in I/S we have done many projects that required construction. Some, walls=
=20
were added, removed or changed as well as reinforcing the floors of NW12=20
and E19. None of these projects ever contaminated the =93 5ESS equipment=94=
or=20
jeopardized its integrity. Second, the plan we discussed with Facilities=20
for the expansion of the switchroom, would have been completed by:
o A) Placing plastic up against the back door; B) Building an=20
extension off of the wall of the switchroom; C) Removing the door, the door=
=20
jam; and D) Begin installing EXM 6 and lastly after the classic is=20
removed, the new equipment is rolled into its permanent space and the room=
=20
is returned to its original configuration. Lucent never visited MIT or=20
asked any questions to get a thorough understanding of the whole=20
plan. Typically Lucent will make a site visit and perform a walk through=20
with MIT.
4. 5ESS Ops team was then told that it would require money to perform=
=20
new engineering schematics and that it would put EXM 6 at risk at cutover=20
after the old equipment is removed. The risk, they describe, is that a=20
=93hot=94 slide would be required to align the equipment and this could lead=
to=20
many problems (e.g. equipment failures, outages, breaks, etc.). 5ESS Ops=20
reminded them that the entire switch is being performed as a =93hot=94=
slide.
5. Since money seemed to be a driving force for Lucent not to perform=
=20
option three, the 5ESS Ops team explored with possibility with Lucent to=20
receive their second payment (to be received at cutover) in hopes that we=20
can move this project forward and ease whatever financial stress was=20
blocking the completion of this project. Lucent never responded to this=20
suggestion. And as a side note: Lucent has already invested an additional=
=20
4-6 million since starting this project. (This does not affect MIT=92s=20
bottom line on the purchasing price of the new switch).
6. Lucent then suggested that they haven't done anything to pursue=20
option three because they have been waiting three weeks for the floor plans=
=20
for Bldg. 24=92s switchroom. This is interesting because, 1) 5E Ops=20
suggested Option three only two weeks ago and 2) they are the one=92s that=
=20
gave us the first set of floor plans to work from because it has the=20
equipment line ups.
7. They also told us that we would be passing up a try and buy program=
=20
that was made available with option two. The equipment would provide the=20
5ESS with Sonet capabilities. This isn't a technological improvement that=
=20
we have been investigating and find it to be more important for the teams=20
to focus on the existing project of bringing the new switch on-line before=
=20
adding equipment we are not sure the community wants or would ever=20
use. This in no way would provide an interim solution to the ISDN requests=
=20
5ESS Support is being asked to provide.
8. In a nutshell, we will continue forward with the installation of=20
the new 5ESS switch. The team will continue to discuss and hopefully=20
influence the installation of EXM 6. The team will continue to work across=
=20
teams and with our customers to fulfill every requirement.
Goals for the month of February and until cutover:
We will:
=B7 Continue testing all analog lines and tracing and repairing=
troubles.
=B7 Continue testing all ISDN lines and correcting problems as they=
occur.
=B7 Continue to influence the installation of EXM 6 to occur in=20
parallel with the cutover.
=B7 Continue with database comparisons; the classic 5ESS to ICE9, the=
=20
new 5ESS to the classic 5ESS and the new ICE9 database to the existing=
=20
ICE9 database) must be 100% accurate. Making modifications as necessary.
=B7 Complete all jumpers to the MDF=92s
=B7 To begin spot checking of all jumpers with attention paid to all=
=20
moves, adds & changes that have occurred since December.
=B7 Continue tracking all MAC=92s (Moves, Adds & Changes) since August=
to=20
insure all jumpers have moved with the relocation/changes that=20
occurred on telephones.
=B7 Perform voice-overs for all the recorded announcements in the new=
=20
switch (this includes the ACD recorded announcements).
=B7 Continue testing the integration of 5ESS with the existing voice=
=20
mail, IVR & ACD systems with the new 5ESS and making modifications as=20
necessary.
=B7 Perform 300 + frame verification and ISDN card changes.
=B7 Communicate to community via article, web notification, email, and=
=20
presentations around the 5ESS upgrade and replacement and possible=20
dates for cutover.
=B7 Continue testing all widgets (e.g. modem pool, circuits, etc.)=20
twice and repair when necessary.
=B7 Test all boards for the new SM6 on SM1, 2 and 3. (SM6=92s=
equipment=20
was temporarily taken and placed in SM1, 2 and 4 when problems=
occurred).
=B7 Install New ACD hardware and software. Cutover old system to new=
=20
platform. Will coordinate with I/S=92s help desk.
=B7 Test ACD integration before and after upgrade.
=B7 Complete spreadsheets to database conversion and debug
=B7 Prepare for cutover
=B7 Night of cutover change 250 ISDN U-A to U-B cards from 24 and=
NW12.
Challenges:
=B7 Lucent
=B7 The installation and testing teams were working around the clock=
=20
with 52 technicians. Recently, they are only working 8 hours a day with 25=
=20
technicians. Lucent has suggested that they could present to the 5E team a=
=20
date on February 1st that they would be confident to commit to a new=20
cutover date.
Inspirational quote: "Make one person happy each day, and in=20
forty years
you will have made 14,600 human beings happy for a
little time, at least."
Thanks,
Lu
=BA=BF=BA
~=20
--=====================_25287993==_.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<div align=3D"center">
<font size=3D5>Project Notebook<br>
<br>
<br>
</font></div>
<font face=3D"Arial Narrow, Helvetica">Project
Name:<x-tab> </x-tab><x-tab> &=
nbsp; </x-tab>5ESS
Upgrade and Replacement<br>
Project
Leader:<x-tab> </x-tab><x-tab>  =
; </x-tab>Louise
T. Keohane<br>
Report
Date:<x-tab> </x-tab><x-tab> &=
nbsp; </x-tab>February
7, 2002<br>
URL:<x-tab> </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp; </x-tab></font><a href=3D"http://web.mit.edu/is/delivery/5ess/"=
eudora=3D"autourl"><font face=3D"Arial Narrow, Helvetica"=
color=3D"#0000FF"><b><u>http://web.mit.edu/is/delivery/5ess/<br>
<br>
<br>
<br>
</a></font><font face=3D"Arial Narrow, Helvetica">Accomplishments in the
Month of January:<br>
</u></b></font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Programmed
the of 3A Translator and will begin to test on-line with the Voice Mail
system.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Relocated
all ACD links on the MDF<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">ACD
Hardware identified and will be ordered.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">ACD
Software and RTU (right to use) fees being negotiated with Lucent/Avaya
and IEX Corp.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Plans
to install and test new ACD hardware & software have begun.
<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Resolved
SM1 issues associated with the modem pool lines.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Continue
to Build and make modifications to the database for the new ICE9 program
that simulates the <x-tab> </x-tab>new 5ESS.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Have
performed some testing of the ICE 9 database and will continue after code
modifications are
<x-tab> </x-tab>complete.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Testing
of analog and ISDN services is as follows:<br>
</font><font face=3D"Courier New, Courier"=
size=3D4><x-tab> </x-tab>o<x=
-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">E19<x-tab> </=
x-tab>70%
of analog & 31% of
ISDN<x-tab> </x-tab><br>
</font><font face=3D"Courier New, Courier"=
size=3D4><x-tab> </x-tab>o<x=
-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">24<x-tab> &nb=
sp;</x-tab>80%
of analog & 11 % of ISDN<br>
</font><font face=3D"Courier New, Courier"=
size=3D4><x-tab> </x-tab>o<x=
-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">NW12<x-tab> </x-tab=
>96%
of analog & 59 % of ISDN<br>
</font><font face=3D"Courier New, Courier"=
size=3D4><x-tab> </x-tab>o<x=
-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">Total
Analog lines tested:<x-tab> </x-tab>
9,522<br>
</font><font face=3D"Courier New, Courier"=
size=3D4><x-tab> </x-tab>o<x=
-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">Total
ISDN lines
tested:<x-tab> </x-tab>
9,944 <br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Verify
testing plan from all 3 locations including IVR, ACD, VMail, Modem pool,
etc.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Continued
to host meetings with the Lucent=92s management team to investigate options
on an interim basis
<x-tab> </x-tab>to
providing additional ISDN/analog services from NW12 and Bldg. 24 until
the new cutover date (e.g. at
<x-tab> </x-tab>least a
few months). Both of these two options that Lucent provided were
not sufficient, as they did not
<x-tab> </x-tab>meet MIT=92s
requirements.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">5EOps
suggested a third option, to place EXM 6 in the hallway of Bldg.
24. After working with Facilities
<x-tab> </x-tab>on a preliminary walk
through of space needed and available in the existing corridor, we
presented this
<x-tab> </x-tab>option to
Lucent. Lucent is very resistant to performing this work before
cutover. </font>
<dl>
<dl><font face=3D"Courier New, Courier" size=3D4>
<dd>o<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">
FYI: Lucent, due to space constraints within the building 24 switch=
room, designed EXM 6 to be placed after the removal of the old 5ESS classic=
equipment. The expected time line for installing EXM6 after cutover=
is a minimum 30 days (again, after the old equipment is removed). Had=
the cutover taken place on Martin Luther King weekend, MIT would have had=
plenty of time to remove the classic equipment out, install EXM 6 and load=
balance both EXM 5 & 6 to provide the appropriate dial tone to meet=
customer demand and project schedules. Setting up a new cutover date,=
MIT, would have taken into consideration the additional 30 days for=
EXM 6 to come on-line.</font>
</dl><font face=3D"Symbol" size=3D4>
<dd>=B7<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">Lucent had many reasons why they could not=
perform option three and the 5E Ops team had as many reasons why they could=
and should:</font><font face=3D"Arial Narrow, Helvetica" size=3D4>
<dd>1.<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">Lucent would require a minimum of $400k=
with a maximum of $500K to perform this work. (EXM 6 has always been=
part of the original proposal, so MIT has already contracted to pay Lucent=
to install this equipment in Bldg. 24 as part of the overall=
project).</font>
<dl><font face=3D"Courier New, Courier" size=3D4>
<dd>o<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">When trying to get Lucent to identify the=
equipment that MIT would require now for approximately $400-500K, they=
agreed to provide a printout. None of the 5ESS Project team to date,=
has seen any documentation.</font>
</dl><font face=3D"Arial Narrow, Helvetica" size=3D4>
<dd>2.<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">Lucent=92s sales team suggested that the=
room wouldn't be ready soon enough and it would move the cutover date=
out to 30 days. Accepting the additional 30 days, and=
suggesting the room could be built within a week (thanks to Joe Collins in=
Facility), Lucent turned back to needing the additional monies ($400-500K)=
to perform the extra work. </font>
<dl><font face=3D"Symbol">
<dd>=B7<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">An example of what would the scenario look=
like if we performed the cutover in April: I/S=
announces the new cutover date (e.g. April 15</font><font face=3D"Arial=
Narrow, Helvetica" size=3D1><sup>th</sup></font><font face=3D"Arial Narrow,=
Helvetica"> ), to the community. Yet, we also tell the community that=
not only are we cutting over, but as of April 15</font><font face=3D"Arial=
Narrow, Helvetica" size=3D1><sup>th</sup></font><font face=3D"Arial Narrow,=
Helvetica"> and until at least June 1</font><font face=3D"Arial Narrow,=
Helvetica" size=3D1><sup>st</sup></font><font face=3D"Arial Narrow,=
Helvetica">, we can not provide any additional ISDN or analog services from=
the Bldg. 24 switchroom. (Doesn't seem like a viable plan to me since=
Lucent has been unable to commit to all goals mutually agreed upon since=
the start of this project. Also, it=92s very possible that the 30=
days they are suggesting it will take is more realistically like > 45=
days). Also, MIT chose not to cutover on MLK weekend, because Lucent=
had less than 40% of all analog lines accurately configured and wired on=
the new switch. They hadn't even begun the verification process for=
the ISDN lines and given that the analog failed at such a high rate, we=
consider we were looking at a higher rate of failure on the ISDN=
lines. Estimated to be around: 10% accurate. (Need I say=
more)? </font>
</dl><font face=3D"Arial Narrow, Helvetica" size=3D4>
<dd>3.<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">Lucent then presented to MIT that we would=
have a contamination issue and we would need to sign a waiver that relieved=
Lucent for ANY failing equipment from the 24 switchroom. First, let=
me say, since being in I/S we have done many projects that required=
construction. Some, walls were added, removed or changed as well as=
reinforcing the floors of NW12 and E19. None of these projects ever=
contaminated the =93 5ESS equipment=94 or jeopardized its integrity.=
Second, the plan we discussed with Facilities for the expansion of the=
switchroom, would have been completed by: </font>
<dl>
<dl>
<dl>
<dl>
<dl><font face=3D"Courier New, Courier">
<dd>o<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">A) Placing plastic up against the back=
door; B) Building an extension off of the wall of the switchroom; C)=
Removing the door, the door jam; and D) Begin installing EXM 6 and=
lastly after the classic is removed, the new equipment is rolled into its=
permanent space and the room is returned to its original=
configuration. Lucent never visited MIT or asked any questions=
to get a thorough understanding of the whole plan. Typically Lucent=
will make a site visit and perform a walk through with MIT.<br>
<br>
</font>
</dl>
</dl>
</dl>
</dl>
</dl><font face=3D"Arial Narrow, Helvetica" size=3D4>
<dd>4.<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">5ESS Ops team was then told that it would=
require money to perform new engineering schematics and that it would put=
EXM 6 at risk at cutover after the old equipment is removed. The=
risk, they describe, is that a =93hot=94 slide would be required to align=
the equipment and this could lead to many problems (e.g. equipment=
failures, outages, breaks, etc.). 5ESS Ops reminded them that the=
entire switch is being performed as a =93hot=94 slide.
</dl> </font>
<dl><font face=3D"Arial Narrow, Helvetica" size=3D4>
<dd>5.<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">Since money seemed to be a driving force=
for Lucent not to perform option three, the 5ESS Ops team explored with=
possibility with Lucent to receive their second payment (to be received at=
cutover) in hopes that we can move this project forward and ease whatever=
financial stress was blocking the completion of this project. Lucent=
never responded to this suggestion. And as a side note: Lucent=
has already invested an additional 4-6 million since starting this=
project. (This does not affect MIT=92s bottom line on the purchasing=
price of the new switch).<br>
<br>
</font><font face=3D"Arial Narrow, Helvetica" size=3D4>
<dd>6.<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">Lucent then suggested that they haven't=
done anything to pursue option three because they have been waiting three=
weeks for the floor plans for Bldg. 24=92s switchroom. This is=
interesting because, 1) 5E Ops suggested Option three only two weeks ago=
and 2) they are the one=92s that gave us the first set of floor plans to=
work from because it has the equipment line ups.<br>
<br>
</font><font face=3D"Arial Narrow, Helvetica" size=3D4>
<dd>7.<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">They also told us that we would be passing=
up a try and buy program that was made available with option two. The=
equipment would provide the 5ESS with Sonet capabilities. This isn't=
a technological improvement that we have been investigating and find it to=
be more important for the teams to focus on the existing project of=
bringing the new switch on-line before adding equipment we are not sure the=
community wants or would ever use. This in no way would provide an=
interim solution to the ISDN requests 5ESS Support is being asked to=
provide.<br>
<br>
</font><font face=3D"Arial Narrow, Helvetica" size=3D4>
<dd>8.<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">In a nutshell, we will continue forward=
with the installation of the new 5ESS switch. The team will continue=
to discuss and hopefully influence the installation of EXM 6. =
The team will continue to work across teams and with our customers to=
fulfill every requirement.<br>
<br>
</dl><b><u>Goals for the month of February and until cutover:<br>
<br>
</u></b>We will: <br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Continue testing all analog lines=
and tracing and repairing troubles.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Continue testing all ISDN lines and=
correcting problems as they occur.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Continue to influence the=
installation of EXM 6 to occur in parallel with the cutover.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Continue with database comparisons;=
the classic 5ESS to ICE9, the new 5ESS to the classic 5ESS and=
<x-tab> </x-tab>the new ICE9 database to the=
existing ICE9 database) must be 100% accurate. Making modifications=
as <x-tab> </x-tab>necessary.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Complete all jumpers to the=
MDF=92s<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">To begin spot checking of all=
jumpers with attention paid to all moves, adds & changes that have=
occurred <x-tab> </x-tab>since=
December.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Continue tracking all MAC=92s=
(Moves, Adds & Changes) since August to insure all jumpers have moved=
<x-tab> </x-tab>with the=
relocation/changes that occurred on telephones.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Perform voice-overs for all the=
recorded announcements in the new switch (this includes the ACD=
<x-tab> </x-tab>recorded=
announcements).<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Continue testing the integration of=
5ESS with the existing voice mail, IVR & ACD systems with the new=
<x-tab> </x-tab>5ESS and making modifications as necessary.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Perform 300 + frame verification and=
ISDN card changes.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Communicate to community via=
article, web notification, email, and presentations around the 5ESS=
<x-tab> </x-tab>upgrade and=
replacement and possible dates for cutover.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Continue testing all widgets (e.g.=
modem pool, circuits, etc.) twice and repair when necessary.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Test all boards for the new SM6 on=
SM1, 2 and 3. (SM6=92s equipment was temporarily taken and placed=
<x-tab> </x-tab>in SM1, 2 and 4 when problems=
occurred).<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Install New ACD hardware and=
software. Cutover old system to new platform. Will coordinate=
with I/S=92s=
<x-tab> </x-tab>help=
desk.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Test ACD integration before and=
after upgrade.<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Complete spreadsheets to database=
conversion and debug<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Prepare for cutover<br>
</font><font face=3D"Symbol"=
size=3D4>=B7<x-tab> </x-tab></font=
><font face=3D"Arial Narrow, Helvetica">Night of cutover change 250 ISDN U-A=
to U-B cards from 24 and NW12.<br>
<br>
<br>
<br>
<b><u>Challenges:</u></b></font>
<dl>
<dl><font face=3D"Symbol" size=3D4>
<dd>=B7<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">Lucent<br>
<br>
</font><font face=3D"Symbol" size=3D4>
<dd>=B7<x-tab> </x-tab></font><font=
face=3D"Arial Narrow, Helvetica">The installation and testing teams were=
working around the clock with 52 technicians. Recently, they are only=
working 8 hours a day with 25 technicians. Lucent has suggested that=
they could present to the 5E team a date on February 1</font><font=
face=3D"Arial Narrow, Helvetica" size=3D1><sup>st</sup></font><font=
face=3D"Arial Narrow, Helvetica"> that they would be confident to commit to=
a new cutover date. <br>
<br>
</dl>
</dl><x-tab> </x-tab>Inspirat=
ional quote: </font>"Make one person happy each day, and in forty=
years<br>
<x-tab> </x-tab>you will have=
made 14,600 human beings happy for a<br>
<x-tab> </x-tab>little time,=
at least."<br>
<br>
<br>
<font color=3D"#0000FF">Thanks,<br>
Lu<br>
<br>
=BA</font><font color=3D"#800080">=BF</font><font color=3D"#0000FF">=BA</fon=
t> <br>
<font color=3D"#FF0000"> ~</font> </html>
--=====================_25287993==_.ALT--
