Re: [ADSM-L] TS3500/3584 installation time frame
2013-04-30 10:25:20
>From what I've observed, the 3584 doesn't' just drop in.
There is a lot of positioning and leveling and connecting and wiring and
testing by the FE when you have multiple frames.
I'd say 8 hours might be enough to do a single L-frame.
But 7 drive frames is a lot.
OTOH, when he says "burn in", I'm assuming he means the time to run the test
exercises of the actuator that they do, and they do need to run it a
significant amount of time. But I've never had an FE tell me that the customer
needs to do a "burn in". They've always turned them over to me ready to rock
and roll.
W
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray
Sent: Tuesday, April 30, 2013 9:58 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TS3500/3584 installation time frame
As you are aware from previous posts, we are heading into a "deinstall 3494
- install 3584". This is a pull-push since we don't have the floor space/power
to run both.
We met with Mainline/IBM yesterday and concerns were raised about the time slot
being allotted to this project - roughly 24-hours and if needed, 48-hours. The
comment from the IBM SE/FE was they usually allow a week for an install/burn-in
of a 3584. Originally, the Mainline (sales) person threw out 8-hours for
deinstall of the 3494 (this is for scrap/parts - no care taken in how it is
taken apart and removed) and 8-hours for the 3584 install.
So, I am looking for experiences on how long it took for you to get your
3584 installed and what, if any, issues there were.
We are removing a 12-frame 3494 and pushing in a 7-frame TS3500/3584 (1-L23
6-D23)
--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will never
use email to request that you reply with your password, social security number
or confidential personal information. For more details visit
http://infosecurity.vcu.edu/phishing.html
|
|
|