Technician/CSO responsibilities

Network wiring/patching

Any wiring/patching required to a switch should be undertaken by the technicians. Should a technician not be available, then we should contact the Infrastructure Unit in the first instance. If there is no-one available, only then should the support unit make any changes to the switch configuration. The technicians must then be made aware of any changes made as soon as possible.

Port configuration files can be edited by both technicians and the support team.

Broken Equipment

  • Suspected broken desktops should be reported to the technicians but as much information as possible will be gathered by the support team in the first instance.
  • Suspected faulty servers will be dealt with by C(S)Os.
  • Faulty network switches will be looked at by the Infrastructure team.
  • Suspected faulty AV equipment should be reported to the technicians but as much information as possiblewill be gathered by the support team in the first instance.
  • The technicians will look after the installation/maintenance of the screens in the flip-desks.

Lab upgrades

The lab upgrades will be the responsibility of the support team but technician help may be available.

AV support

The frontline support for AV will be the responsibility of the support team, including the maintenance of the DICE machines in lecterns. The wiring and rack kit in G.Z11 will be the responsibility of the technicians.

Printers

Frontline support will be the responsibility of the support team but printer repairs (including printer maintenance kits?) will be the responsibility of the technicians. The support team currently change HP toner while users now change toner in the Canon MFDs.

-- AlisonDownie - 08 Jun 2009

Topic revision: r3 - 12 Jun 2009 - 10:58:52 - AlisonDownie
 
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