September 2, 2008 at 6:35 am
How would you create a handover plan from many systems (in different separate locations) to a single system in a new location? The new system would use the staff based at the current locations who will have to travel. To make the matter interesting, the information feeding the systems comes in and out via telephone line and , once switched to the new location, cannot be switched back.
Its not one of my systems but a friend's; I was just asked for any thoughts. I suggested parrallel running but its not possible because of the telephone lines. I've come up with several suggestions but each one won't work for valid reasons.
I just wondered if there was someone who experience of this sort of transfer. The databases aren't the problem; its the logistics
:Whistling:
Madame Artois
September 2, 2008 at 9:18 pm
I'm not quite sure what you mean. Handover as in handing over control of systems to someone else? Or moving systems to a new location? Which steps in the handover are you looking for?
September 3, 2008 at 1:04 am
Its moving systems to a new location. Once the phone lines have been swapped over to the new location, they cannot be swapped back so you cannot parrellal run both systems which it what I suggested. In theory, with all the staff previously trained on the new system and the new system software having been tested to destruction, there should be no problems. Hah, I say 'theory versus practice'.
Which is why I was asking if anyone had ever done this before. I'm sure (and so is my friend) that there will be problems. I'm just to help her plan for the switchover so if anyone has experience of this, it could help. Hundreds of heads are better than 2!!
:Whistling:
Madame Artois
September 3, 2008 at 8:37 pm
I'm not sure what you can do other than document how things work. I wouldn't call this a handover plan, since you aren't really handing things over to anyone, you're more migrating to new systems.
People have talked about this in terms of moving data centers. You can only test so much, and cannot test in parallel, though that's what you'd like to do. If you have it well documented, as in what data comes in from what lines, time, expected rate/speed, etc., then you can troubleshoot issues quickly.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply