[806] in I/T Delivery
5ESS upgrade and replacement project
daemon@ATHENA.MIT.EDU (Louise T. Keohane)
Fri Jun 14 18:55:57 2002
Message-Id: <5.0.2.1.2.20020614175506.00a1e010@hesiod>
Date: Fri, 14 Jun 2002 18:53:11 -0400
To: delivery@mit.edu
From: "Louise T. Keohane" <lu@MIT.EDU>
Cc: njj@mit.edu, telecom-ops@mit.edu
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="=====================_35133435==_.ALT"
--=====================_35133435==_.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Project Name: 5ESS upgrade and replacement
Project Leader: Lu Keohane
Report Date May 6, 2002
Submitted by: Lu Keohane
Project Notebook URL: http://web.mit.edu/is/delivery/5ess/
Accomplishments in May:
% The equipment for EXM6 was placed in the =93holding room=94 in 24.
% On May 24th at 6pm MIT shut off the old classic 5ESS and brought=20
the new 5ESS-2000 on line. The event was perfectly implemented. Issues=20
that arose were:
1) The classic (old) 5ESS switch wouldn't stop giving dial tone
o We had a contingency plan in place to deal with this and were back=
=20
on track within immediately after we physically removed all the ISDN fuses=
=20
(approx. 10,500) at all 3 switch locations. (We had teams of individuals=20
at all 3 locations standing by for just this operation.
2) SM21 that was on the classic 5E and being re-used and renamed=20
SM3 on the new 5ESS-2000 wouldn't come on line until:
o Two memory cards were exchanged (upgraded) (All spares were on=
site)
o Engineering for the =93SM3=94 was incorrect as it had Hardware=
assigned=20
in software that did not exist.
o Two cables were found to be in reverse order.
o We needed to move equipment from inactive sides of SM1 (in E19) and=
=20
place into SM3 to ensure working cards were not the problem. The same was=
=20
done in reverse on Saturday morning.
Even with the few service effecting issues related to SM3, less than .5% of=
=20
our customers experienced an outage during our troubleshooting hours (e.g.=
=20
5/24/02 at 10:30 pm until noon on 5/25/02). We maintained a 99.5% in=20
service before and after cutover. Reports were generated before cutover to=
=20
identify all Out-Of-Service (OOS) lines and trunks on the old 5ESS. Then=20
after cutover the report was run again eliminating those out of service=20
before cutover.
The .5% of troubles that occurred after cutover was all related to:
1. Modem pool room 25 bad cables found
2. Voice mail system loose or missing cables were found
3. Telephones on the East side of campus =3D 100 ISDN lines that=
printed=20
out on the OOS report.
A very organized team of talented individuals worked Saturday and=20
Sunday. Some tested feature test plans, dialing plans, ACD, Voice Mail,=20
Name Connector (IVR), Audio Conference Bridges, modem pool, operator=20
services, Video conferencing, ICE 9, Recorded Announcements, etc. We also=
=20
had a team verify the proper routing of all the trunks on campus=20
(Specifically to see if all of our dialing properties and access codes were=
=20
operational. This includes verifying properties that should not work are=20
still not working). We were able to work through all testing and=20
completing all OOS troubles within buy Sunday which allowed the 5E Team to=
=20
have Monday (Memorial Day) off. We regrouped on Tuesday morning to handle=
=20
calls from customers. During the =93soak=94 week we averaged 50-100=
troubles a=20
day. What we found:
20 % were related to bad jumper placement (jumper loose
30 % were a result of Lucent not having kept up with the moving of jumpers=
=20
as a result of the Moves, adds, & changes (MAC=92s) as well as the troubles=
=20
that were continuing as daily activity since December 2001. There were=20
approx. 3,200 MAC=92s and 2,700 troubles. Most included changing the wiring=
=20
on the main distribution frame. Our team planned for this possibility and=
=20
we were able to correct 95% of the troubles by mapping our ICE-9 and Frame=
=20
Verification databases with the field assessments and adjusted the jumpers=
=20
to the correct Cable and Pair (C/P) by Sunday May 26th.
25 % were a result of the double jumpers. Once the jumpers for the old=20
5ESS were removed phones came into service.
15% were a result of jumpers being disturbed as we began removing some of=20
the classic 5ESS equipment from Bldg. 24. Some jumpers became loose as a=20
result of removing old cables.
05 % were a result of ISDN phones not being plugged into the jack.
02 % was Stand-alone equipment that had a team in the process of changing=20
across campus.
03 % were with Trunks that were out of service as a result of another site=
=20
(Draper) performing an upgrade to their phone system and experiencing=20
multiple outages.
The week following the cutover we handled approximately 80 troubles a=20
day. We cleared on average within 24 hours of the report. Before cutover,=
=20
our averages troubles ran around 1.5% (which also includes issues with=20
voice mail, ACD, Name Connector, feature activation, Video Conferencing,=20
PBX=92s, Trunks, etc.).
One week after cutover, we deemed it safe to begin to power down the old=20
5ESS. This significantly improved the A/C within the E19 switchroom.
% ICE 9 modifications continue. Some anomalies were found and=20
corrected. We are currently waiting for the complete installation=
=20
of SM6 for the equipment assignment and PIDB layouts.
% The billing data dumped from the switch was successful.
The traffic reports were not operational for few days. The=20
circuit was tested and it is now collecting data on trunks,=20
operators, and other statistical data.
% Campus Police and Medical were very cooperative with the=20
implementation plan. They were told when we were cutting over and=
=20
verified there were no emergency (911) calls in progress. They were=20
provided cell phones and the script that we ran as the 5ESS-2000 came=20
on line immediately brought their lines into service first and it was timed=
=20
that they were back in service within 2 minutes for CP and 2.5=20
minutes for Medical.
% Additional communications to the community were provided. Robyn=20
Fizz and Susan Curran had the upgrade announced on Spotlight all day=20
5/24, as a reminder to the community.
% Tina Sands did an excellent job of taking care of the teams=20
needs. Tina your efforts
were not only noticed by our teams but Lucent also complimented=20
your work and
hospitality for a few times after cutover. You helped me=20
immensely. Thank you for
ordering all the food/beverages, running out and getting supplies,=
=20
arranging hotel
rooms, handling the paperwork for vouchers, diners club, etc. I=20
appreciate, as does
the whole team, all that you did to make us all comfortable and=20
happy. Thank you,
thank you, thank you.
% All vendors were prepared and available, including VDIST who=20
arranged for us to have access to a cable splicing vendor incase we=20
discovered a bad cable in the street.
% Coordinate the disconnect of the Vesda (smoke detection) system=20
while drilling in 24
% Drill holes for the SM6 cabinet string and drill holes for SM5=92s=
=20
future location
% Continue to meet with Lucent on Thursday in E19-732. This will=20
occur until the project is complete (e.g. removal=20
of classic equipment and clean-up)
% Continue to meet with Lucent Management one Wednesday a month or as=
=20
needed.
% Powered down 5ESS in E19 significant difference with the A/C.
Next Month=92s plans:
=B7 Install SM6, cable, ground and power up. Begin to build the=20
equipment and test assignments. Upgrade cards that were used as=20
temporaries on SM3 the night of cutover.
=B7 Relocate (hotslide) SM5, within the 24 switchroom.
=B7 Re-stock spares inventory of all items used cutover weekend.
=B7 Remove all classic cabinets from NW12 and E19 onto trucks
=B7 Remove all jumpers from the old 5ESS switch
=B7 Clean-up of cables to the frame blocks (e.g. shorten cable=
lengths)
=B7 Take the power cables off and cut down at shorter lengths
=B7 Re-attach in a permanent fashion the 5ESS-2000 blocks (careful not=
=20
to disconnect users)
=B7 Perform =93hot-slide.=94 Process of moving a working switch from=
one=20
location to another. We are planning to do each switch site location on=
=20
different weekends (we are looking at: July 12th for 24, July 19th for=
=20
NW12, and July 26th for E19.
Lucent has never performed this before on a switch of this size=20
and complexity and as a result, we are getting a lot of interested=20
companies wanting to visit to observe the =93hotslide=94 in E19. (The E19=
=20
switch site is the most risky to move since it is the nucleus of the=
5ESS).
=B7 Issues:
One issue that continued this month was the fact that Lucent did not have a=
=20
great Project Management team. As a result, MIT had to provide leadership=
=20
and direction for both teams. It was obvious at times that there was lack=
=20
of training in project management as well as in 5ESS technology.
Here are some interesting differences between the installations of the 5ESS=
=20
in 1987 vs. 2002.
5ESS installed in=20
1987 5ESS installed in 2002
Number of ISDN lines: Less than=20
5,000 9,100+
Number of Analog lines Approx.=20
13,000 Approx. 14,000
Offsite=20
PBX's Approx. 2=20
11
Voice=20
Mail 4,482=20
9,500
Number of=20
trunks 728=20
2,046
Cutover of telephone lines: 1st phase: 6,750 cutover=20
on Aug. 12, 1988 Whole system cutover 5/24-26/02
2nd phase: 8.652 cutover=20
on Oct. 28, 1988 (22,000 lines/2,046 trunks=20
&=20
peripherals)
Turnover of switch: February 10,=20
1989 planned for: 7/29-8/1/2002
% telephone lines out-of-service at cutover: ISDN=3D 51% not=20
working less than 1% both ISDN/analog
analog =3D 32-43% not=
working
Avg. length of time lines were out-of-service 7 to 14 days (some cases=20
months) 24 hour turnaround
Other systems running off of the 5ESS: Voice=20
mail Voice mail
Video Conferencing <=20
100 Video conferencing 300+
=
IVR=20
- Name Connector
Circuits =3D less than=20
100 Circuits & alarms =3D 250+
=
ACD=20
(automatic call distr)
Tie=20
lines Tie Lines
No tracking - ICE 9 wasn't=
=20
working ICE 9 (billing et al database)
=
Audio=20
conference meet-me bridge
External clocking from=20
Local/LD co. 5ESS Internal GPS clocking
Modem pool size Created with approx.=20
100+ 315
Dynamics:
I don=92t have words to describe how proud I am of this team (including=20
leadership support). This cutover was successful because MIT made it=20
successful. MIT fully ran this project from management down to technical=20
engineering. THANK YOU all for putting your heart and soul into making=20
this look like a piece of cake.
Key Learnings:
I feel privileged to be working with the extraordinary individuals that=20
make up 5ESS Project team. They are each independently remarkable and as a=
=20
whole they are indomitable.
The cutover was made successful because each team member put their heart=20
and soul into this exigent project and made a difference.
"Success is determined by those whom prove the impossible, possible." -=20
James W. Pence
=93As long as you can laugh at yourself you will never cease to be amused=94=
Lu
--=====================_35133435==_.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
Project Name: 5ESS upgrade and replacement<br>
Project Leader: Lu Keohane<br>
Report Date May 6, 2002<br>
Submitted by: Lu
Keohane<x-tab> </x-tab><br>
<font size=3D2>Project Notebook URL:
</font><a href=3D"http://web.mit.edu/is/delivery/5ess/"=
eudora=3D"autourl"><font size=3D2 color=3D"#0000FF"><u>h</a></font><a=
href=3D"http://web.mit.edu/is/delivery/5ess/" eudora=3D"autourl"><font=
face=3D"Arial Narrow, Helvetica"=
color=3D"#0000FF">ttp://web.mit.edu/is/delivery/5ess/</a><br>
<br>
</font><b>Accomplishments in May:<br>
<br>
</u></b><font=
face=3D"ZapfDingbats">%<x-tab> </x=
-tab></font><font color=3D"#993366">The
equipment for EXM6 was placed in the =93holding room=94 in 24.</font> <br>
<br>
<font=
face=3D"ZapfDingbats">%<x-tab> </x=
-tab></font><font color=3D"#993366">On
May
24</font><font size=3D1 color=3D"#993366"><sup>th</sup></font><font color=3D=
"#993366">
at 6pm MIT shut off the old classic 5ESS and brought the new 5ESS-2000 on
line. The event was perfectly implemented. Issues that arose
were:<br>
<br>
<x-tab> </x-tab>1) The
classic (old) 5ESS switch wouldn't stop giving dial tone </font>
<dl>
<dl>
<dl><font face=3D"Courier New, Courier" color=3D"#993366">
<dd>o<x-tab> </x-tab></font>We
had a contingency plan in place to deal with this and were back on track
within immediately after we physically removed all the ISDN fuses
(approx. 10,500) at all 3 switch locations. (We had teams of
individuals at all 3 locations standing by for just this operation. =20
</dl>
</dl>
</dl><x-tab> </x-tab>2)
SM21 that was on the classic 5E and being re-used and renamed SM3 on the
new 5ESS-2000 wouldn't come on line until:
<dl>
<dl>
<dl>
<dl><font face=3D"Courier New, Courier" color=3D"#993366">
<dd>o<x-tab> </x-tab></font>Two
memory cards were exchanged (upgraded) (All spares were on site)
</dl>
</dl>
</dl>
</dl><font face=3D"Courier New, Courier" color=3D"#993366">o<x-tab> &nb=
sp; </x-tab></font>Engineering
for the =93SM3=94 was incorrect as it had Hardware assigned in software that
did not exist. <br>
<font face=3D"Courier New, Courier" color=3D"#993366">o<x-tab> &n=
bsp; </x-tab></font>Two
cables were found to be in reverse order.<br>
<font face=3D"Courier New, Courier" color=3D"#993366">o<x-tab> &n=
bsp; </x-tab></font>We
needed to move equipment from inactive sides of SM1 (in E19) and place
into SM3 to ensure working cards were not the problem. The same was
done in reverse on Saturday morning.<br>
<br>
Even with the few service effecting issues related to SM3, less than .5%
of our customers experienced an outage during our troubleshooting hours
(e.g. 5/24/02 at 10:30 pm until noon on 5/25/02). We maintained a
99.5% in service before and after cutover. Reports were generated
before cutover to identify all Out-Of-Service (OOS) lines and trunks on
the old 5ESS. Then after cutover the report was run again
eliminating those out of service before cutover.<br>
<br>
The .5% of troubles that occurred after cutover was all related to:<br>
1.<x-tab> </x-tab>Modem pool
room 25 bad cables found<br>
2.<x-tab> </x-tab>Voice mail
system loose or missing cables were found<br>
3.<x-tab> </x-tab>Telephones on the
East side of campus =3D 100 ISDN lines that printed out on the
<x-tab> </x-tab>OOS report.<br>
<br>
A very organized team of talented individuals worked Saturday and
Sunday. Some tested feature test plans, dialing plans, ACD, Voice
Mail, Name Connector (IVR), Audio Conference Bridges, modem pool,
operator services, Video conferencing, ICE 9, Recorded Announcements,
etc. We also had a team verify the proper routing of all the trunks
on campus (Specifically to see if all of our dialing properties and
access codes were operational. This includes verifying properties
that should not work are still not working). We were able to work
through all testing and completing all OOS troubles within buy Sunday
which allowed the 5E Team to have Monday (Memorial Day) off. We
regrouped on Tuesday morning to handle calls from customers. During
the =93soak=94 week we averaged 50-100 troubles a day. What we
found:<br>
<br>
<font color=3D"#0000FF">20 %</font><font color=3D"#993366"> were related to
bad jumper placement (jumper loose <br>
</font><font color=3D"#0000FF">30 %</font><font color=3D"#993366"> were a
result of Lucent not having kept up with the moving of jumpers as a
result of the Moves, adds, & changes (MAC=92s) as well as the troubles
that were continuing as daily activity since December 2001. There
were approx. 3,200 MAC=92s and 2,700 troubles. Most included changing
the wiring on the main distribution frame. Our team planned for
this possibility and we were able to correct 95% of the troubles by
mapping our ICE-9 and Frame Verification databases with the field
assessments and adjusted the jumpers to the correct Cable and Pair (C/P)
by Sunday May
26</font><font size=3D1 color=3D"#993366"><sup>th</sup></font><font=
color=3D"#993366">.<br>
</font><font color=3D"#0000FF">25 %</font><font color=3D"#993366"> were a
result of the double jumpers. Once the jumpers for the old 5ESS
were removed phones came into service.<br>
</font><font color=3D"#0000FF">15% </font><font color=3D"#993366">were a
result of jumpers being disturbed as we began removing some of the
classic 5ESS equipment from Bldg. 24. Some jumpers became loose as
a result of removing old cables.<br>
</font><font color=3D"#0000FF">05 %</font><font color=3D"#993366"> were a
result of ISDN phones not being plugged into the jack.<br>
</font><font color=3D"#0000FF">02 %</font><font color=3D"#993366"> was
Stand-alone equipment that had a team in the process of changing across
campus.<br>
</font><font color=3D"#0000FF">03 %</font><font color=3D"#993366"> were with
Trunks that were out of service as a result of another site (Draper)
performing an upgrade to their phone system and experiencing multiple
outages.<br>
<br>
<br>
The week following the cutover we handled approximately 80 troubles a
day. We cleared on average within 24 hours of the report. Before
cutover, our averages troubles ran around 1.5% (which also includes
issues with voice mail, ACD, Name Connector, feature activation, Video
Conferencing, PBX=92s, Trunks, etc.).<br>
<br>
One week after cutover, we deemed it safe to begin to power down the old
5ESS. This significantly improved the A/C within the E19
switchroom. <br>
</font> <br>
<font face=3D"ZapfDingbats">%<x-tab> &nbs=
p;</x-tab></font>ICE
9 modifications continue. Some anomalies were found and
corrected. We are
<x-tab> </x-tab>currently
waiting for the complete installation of SM6 for the equipment assignment
and PIDB layouts. <br>
<br>
<font face=3D"ZapfDingbats">%</font><x-tab> &nb=
sp; </x-tab>The
billing data dumped from the switch was successful.<br>
<x-tab> </x-tab>The
traffic reports were not operational for few days. The circuit was
tested and it is now collecting data on trunks, operators,
<x-tab> </x-tab>and other statistical
data.<br>
<br>
<font face=3D"ZapfDingbats">%</font><x-tab> &nb=
sp; </x-tab>Campus
Police and Medical were very cooperative with the implementation
plan. <x-tab> </x-tab>They were told when we were cutting over
<x-tab> </x-tab>and verified
there were no emergency <x-tab> </x-tab>(911) calls in
progress. They were provided cell phones and the script that we ran
<x-tab> </x-tab>as the 5ESS-2000 came on line
immediately brought their lines into service first and it was timed that
they were back in
<x-tab> </x-tab>service within 2
minutes for CP and 2.5 minutes for Medical.<br>
<br>
<font face=3D"ZapfDingbats">%<x-tab> &nbs=
p;</x-tab></font>Additional
communications to the community were provided. Robyn Fizz and Susan
Curran had the upgrade announced on
<x-tab> </x-tab>Spotlight all day 5/24, as a
reminder to the community.<br>
<dl><font face=3D"ZapfDingbats">
<dd>%<x-tab> </x-tab></font>Tina
Sands did an excellent job of taking care of the teams needs. Tina
your efforts
<dd><x-tab> </x-tab>were
not only noticed by our teams but Lucent also complimented your work=20
and
<dd><x-tab> </x-tab>hospitali=
ty
for a few times after cutover. You helped me immensely. Thank
you for
<dd><x-tab> </x-tab>ordering
all the food/beverages, running out and getting supplies, arranging
hotel<x-tab> </x-tab>
<dd><x-tab> </x-tab>rooms,
handling the paperwork for vouchers, diners club, etc. I
appreciate, as does=20
<dd><x-tab> </x-tab>the
whole team, all that you did to make us all comfortable and happy.
Thank you,
<dd><x-tab> </x-tab>thank
you, thank you. <br>
<br>
</dl><font face=3D"ZapfDingbats">%<x-tab>  =
; </x-tab></font>All
vendors were prepared and available, including VDIST who arranged for us
to have access to a cable splicing vendor <x-tab> </x-tab>incase we
discovered a bad cable in the street.<br>
<dl><font face=3D"ZapfDingbats">
<dd>%<x-tab> </x-tab></font>Coordin=
ate
the disconnect of the Vesda (smoke detection) system while drilling in
24<br>
<br>
<font face=3D"ZapfDingbats">
<dd>%<x-tab> </x-tab></font>Drill
holes for the SM6 cabinet string and drill holes for SM5=92s future
location<br>
<br>
</dl><font face=3D"ZapfDingbats">%<x-tab>  =
; </x-tab></font>Continue
to meet with Lucent on Thursday in E19-732. This will occur until
the project is complete (e.g. removal of
<x-tab> </x-tab>classic
<x-tab> </x-tab>equipment
and clean-up)<br>
<br>
<font face=3D"ZapfDingbats">%</font><x-tab> &nb=
sp; </x-tab>Continue
to meet with Lucent Management one Wednesday a month or as needed.<br>
<dl><font face=3D"ZapfDingbats">
<dd>%</font><x-tab> </x-tab>Powered
down 5ESS in E19 significant difference with the A/C. =20
</dl> <x-tab> </x-tab><br>
<br>
<br>
<br>
<br>
<br>
<b><u>Next Month=92s plans:<br>
</u></b><font face=3D"Symbol">=B7<x-tab> =
</x-tab></font>Install
SM6, cable, ground and power up. Begin to build the equipment and
test
<x-tab> </x-tab>assignments.&=
nbsp;
Upgrade cards that were used as temporaries on SM3 the night of
<x-tab> </x-tab>cutover. <br>
<font face=3D"Symbol">=B7<x-tab> </=
x-tab><x-tab> </x-tab><x-tab>=
</x-tab></font>Relocate
(hotslide) SM5, within the 24 switchroom.<br>
<font face=3D"Symbol">=B7<x-tab> </=
x-tab></font>Re-stock
spares inventory of all items used cutover
weekend.<font face=3D"Symbol"><x-tab> </x-tab><br>
=B7<x-tab> </x-tab></font>Remove
all classic cabinets from NW12 and E19 onto trucks<br>
<font face=3D"Symbol">=B7<x-tab> </=
x-tab></font>Remove
all jumpers from the old 5ESS switch<br>
<font face=3D"Symbol">=B7<x-tab> </=
x-tab></font>Clean-up
of cables to the frame blocks (e.g. shorten cable lengths)<br>
<font face=3D"Symbol">=B7<x-tab> </=
x-tab></font>Take
the power cables off and cut down at shorter lengths<br>
<font face=3D"Symbol">=B7<x-tab> </=
x-tab></font>Re-attach
in a permanent fashion the 5ESS-2000 blocks (careful not to disconnect
<x-tab> </x-tab>users)<br>
<font face=3D"Symbol">=B7<x-tab> </=
x-tab></font>Perform
=93hot-slide.=94 Process of moving a working switch from one location
to <x-tab> </x-tab>another. We are planning to do each
switch site location on different weekends (we
<x-tab> </x-tab>are looking at: July
12<font size=3D1><sup>th</sup></font> for 24, July
19<font size=3D1><sup>th</sup></font> for NW12, and July
26<font size=3D1><sup>th</sup></font> for E19.<br>
<x-tab> </x-tab>Lucent has
never performed this before on a switch of this size and complexity and
<x-tab> </x-tab>as a result, we are getting
a lot of interested companies wanting to visit to observe
<x-tab> </x-tab>the =93hotslide=94 in E19. (The E19 switch site i=
s
the most risky to move since it is the <x-tab> </x-tab>nucleus
of the 5ESS).<br>
<br>
<font=
face=3D"Symbol">=B7<x-tab> </x-tab=
></font><b><u>Issues:<br>
</u></b>
<dl>
<dd>One issue that continued this month was the fact that Lucent did not
have a great Project Management team. As a result, MIT had to
provide leadership and direction for both teams. It was obvious at
times that there was lack of training in project management as well as in
5ESS technology. <br>
<br>
</dl>Here are some interesting differences between the installations of
the 5ESS in 1987 vs. 2002.<br>
<br>
<br>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp;</x-tab><x-tab> </x-tab><f=
ont color=3D"#000080"><b><u>5ESS
installed in
1987<x-tab> </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> </x=
-tab><x-tab> </x-tab>5ESS
installed in 2002<br>
</u></b></font>Number of ISDN
lines:<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp;</x-tab><x-tab> </x-tab>=
Less
than 5,000<x-tab> </x-tab>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab>9,100+
<br>
Number of Analog
lines<x-tab> </x-tab><x-tab> &=
nbsp; </x-tab><x-tab> </=
x-tab><x-tab> </x-tab>Approx.
13,000<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> <=
/x-tab><x-tab> </x-tab><x-tab=
> </x-tab>Approx.
14,000<br>
Offsite
PBX's<x-tab> </x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp;</x-tab><x-tab> </x-tab><=
x-tab> </x-tab>Approx.
2<x-tab> </x-tab>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> <=
/x-tab>
<x-tab> </x-tab>11<br>
Voice Mail<x-tab> </x-tab>=
<x-tab> </x-tab><x-tab>  =
; </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab>4,482<x-tab> </x-tab> =
<x-tab> </x-tab><x-tab>  =
; </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp;</x-tab><x-tab> </x-tab>=
9,500<br>
Number of=
trunks<x-tab> </x-tab>=
<x-tab> </x-tab><x-tab>  =
; </x-tab><x-tab> =
</x-tab>728<x-tab> </x-=
tab>=
<x-tab> </x-tab><x-tab>  =
; </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> </=
x-tab>2,046<br>
<br>
Cutover of telephone=
lines:<x-tab> </x-tab><x-tab>  =
; </x-tab><x-tab> =
</x-tab>1st phase: 6,750 cutover on Aug. 12,=
1988 Whole system cutover=
5/24-26/02<x-tab> </x-tab><br>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp;</x-tab><x-tab> </x-tab>2n=
d phase: 8.652 cutover on Oct. 28,=
1988<x-tab> </x-tab> <font size=3D=
2 color=3D"#0000FF">(22,000 lines/2,046 trunks &=
<x-tab> </x-tab><x-tab>  =
; </x-tab><x-tab> </x-ta=
b><x-tab> </x-tab><x-tab>&nbs=
p; </x-tab><x-tab>  =
; </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp;</x-tab><x-tab> </x-tab>=
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab>peripherals)<br>
<br>
</font>Turnover of=
switch:<x-tab> </x-tab><x-tab> &nbs=
p; </x-tab><x-tab>  =
; </x-tab><x-tab> =
</x-tab>February 10,=
1989<x-tab> </x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp; </x-tab>planned for: 7/29-8/1/2002<br>
<br>
% telephone lines out-of-service at=
cutover:<x-tab> </x-tab>ISDN=3D 51% not=
working<x-tab> </x-tab><x-tab> &nbs=
p; </x-tab><x-tab>  =
; </x-tab><x-tab> </x-ta=
b>less than 1% both ISDN/analog<br>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp;</x-tab><x-tab> </x-tab>an=
alog =3D 32-43% not working<br>
<br>
Avg. length of time lines were=
out-of-service<x-tab> </x-tab>7 to 14 days (some cases=
months)<x-tab> </x-tab><x-ta=
b> </x-tab>24 hour=
turnaround<br>
<br>
Other systems running off of the=
5ESS:<x-tab> </x-tab><x-tab> =
</x-tab>Voice=
mail<x-tab> </x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp; </x-tab><x-tab> </x-=
tab>Voice mail<br>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp;</x-tab><x-tab> </x-tab>Vi=
deo Conferencing <=
100<x-tab> </x-tab><x-tab>&n=
bsp; </x-tab><x-tab> &nb=
sp; </x-tab>Video conferencing 300+<br>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp;</x-tab><x-tab> </x-tab><x=
-tab> </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp; </x-tab><x-tab> &nbs=
p; </x-tab><x-tab>  =
;</x-tab><x-tab> </x-tab>IVR=
- Name Connector<br>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp;</x-tab><x-tab> </x-tab>Ci=
rcuits =3D less than=
100<x-tab> </x-tab><x-tab>&n=
bsp; </x-tab><x-tab> &nb=
sp; </x-tab><x-tab> &nbs=
p; </x-tab>Circuits & alarms =3D 250+<br>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp;</x-tab><x-tab> </x-tab><x=
-tab> </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp; </x-tab><x-tab> &nbs=
p; </x-tab><x-tab>  =
;</x-tab><x-tab> </x-tab>ACD=
(automatic call distr)<br>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp;</x-tab><x-tab> </x-tab>Ti=
e=
lines<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp;</x-tab>Tie Lines<br>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp;</x-tab><x-tab> </x-tab>No=
tracking - ICE 9 wasn't=
working<x-tab> </x-tab><x-tab> &nbs=
p; </x-tab>ICE 9 (billing et al=
database)<br>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp;</x-tab><x-tab> </x-tab><x=
-tab> </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp; </x-tab><x-tab> &nbs=
p; </x-tab><x-tab>  =
;</x-tab><x-tab> </x-tab>Audi=
o conference meet-me bridge<br>
<x-tab> </x-tab><x-tab> =
</x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab><x-tab> &nb=
sp;</x-tab><x-tab> </x-tab>Ex=
ternal clocking from Local/LD=
co.<x-tab> </x-tab>=
<x-tab> </x-tab>5ESS Internal GPS=
clocking<br>
<br>
Modem pool=
size<x-tab> </x-tab><x-tab> &=
nbsp;</x-tab><x-tab> </x-tab>=
<x-tab> </x-tab>Created with=
approx.=
100+<x-tab> </x-tab><x-tab> &=
nbsp; </x-tab><x-tab> &n=
bsp; </x-tab>315<br>
<br>
<br>
<br>
<br>
<font size=3D2><b><u>Dynamics: <br>
</u></b></font>
<dl>
<dd>I don=92t have words to describe how proud I am of this team (including=
leadership support). This cutover was successful because MIT made it=
successful. MIT fully ran this project from management down to=
technical engineering. THANK YOU all for putting your heart and soul=
into making this look like a piece of cake.<font size=3D1>
<dd> </font>
</dl><b><u>Key Learnings:</u></b>
<dl>
<dd><x-tab> </x-tab><br>
<br>
</dl>I feel privileged to be working with the extraordinary individuals that=
make up 5ESS Project team. They are each independently remarkable and=
as a whole they are indomitable. <br>
<br>
The cutover was made successful because each team member put their heart and=
soul into this exigent project and made a difference.<br>
<br>
"Success is determined by those whom prove the impossible,=
possible." - James W. Pence<br>
<br>
=93As long as you can laugh at yourself you will never cease to be=
amused=94 Lu<br>
<br>
<br>
</html>
--=====================_35133435==_.ALT--
