Departure Team

Team of people responsible for make sure IT equipment leave the buildings correctly label and keeps a what is moving list up-to-date.

Site Date Team (Manager first)
AT 16/6/2008 Tim, Ewan, Archie
BP 17/6/2008 - 21/6/2008 Neil, Ross, Toby, Roger, Carol, Bill
FH 25/6/2008 - 27/6/2008 Roger, Jennifer, Gordon
JCMB 30/6/2008 - 3/7/2008 Iain, Richard, Toby, Graham, Archie, Rosemary, Neil
AT 4/7/2008 Tim, Archie, Gordon, Ewan

The following is included from ForumDepartureTeamDuties

Departure Team Duties

Ken will provide a daily list of people moving (sorted by room) listing: the person, where they are now, where they are going to, and the machines/hardware they are taking with them.

On the day prior to their move day, visit every person/room being moved on the following day and do the following.

  • Note any changes to the hardware in Ken's list, ie
    • machines not actually in the current room
    • machines there but not moving to the new room
    • machines in the room but not listed on Ken's list
    • for occupants with no machine listed by them, state if they really don't have hardware, or if they do what it is.
  • For each machine being moved note whether DICE, MDP or self-managed.
  • Power down and disconnect all hardware.
  • If user has already disconnected and packed the mouse and/or keyboard then make a note of same (e.g. 'mouse and keyboard in green crate') and attach to the base unit so that the arrival team know what the situation is.
  • Collect TP cables and power blocks.
  • Make sure all the hardware that is moving is labeled correctly (and actually stuck down). Pickfords will move IT equipment that has been packed by us/occupants providing it is in its original packaging (and labeled) and migration@inf (also CC local migration rep.) have been told about it (so they can tell Pickfords). Otherwise they will pack it in their generic containers. Local reps.

Once that's done for everyone, pass the changes to Ken's list back to Ken (and the Arrival Team - Alison).

Note we are only interested in computing hardware, not crates. Though it might be wise to see if the details match.

Data Flow

We require the following information

  • list of people moving on each day (Ken)

We should pass on the following information

  • amendments to list of hardware moving (to Ken/Arrival Team)


  • What do we do with hardware that is not being moved at all, or we don't know where it is moving to?
  • It is likely (should be the case) that the affected users will not be around on the day prior to their move. It would be sensible to visit them a day or so before hand to remind them and explain what will happening.
  • I take it we are not concerned with cupboards full of old IT equipment.

-- NeilBrown - 11 Jun 2008

Edit | Attach | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 11 Jun 2008 - 16:43:12 - NeilBrown
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies