Personal tools
You are here: Home Local Information Deputy Director

Deputy Director

Job Description

Job Title:

LFCS Deputy Director

Responsible to:

Director of Institute

Responsible for:

Implementing the academic and scientific management of LFCS, as determined by the Director.

Term of Appointment:

Normally for a period of three years, with the possibility of renewal.


To maintain and further the activities and continuing success of LFCS as a coherent and effective research institute within the Division of Informatics.


While the LFCS Director is responsible for setting general direction and strategy for the Institute, the Deputy Director and the Service Manager are jointly responsible for making things happen. They work in close collaboration to achieve this.

It is the experience of LFCS that institute management has a significant scientific as well as a purely administrative component. As an academic staff member, the Deputy Director is responsible for this scientific component. The detailed allocation of duties between the Deputy Director and the Service Manager is agreed by them in consultation with the Director.

The most visible part of the Deputy Director's role is as a first point of contact for LFCS matters. The day-to-day life of LFCS depends on the Deputy Director and the Service Manager arranging rapid solutions to a host of ad-hoc requests from Institute members.

In the Division at large, the Deputy Director is also the default LFCS contact for the assorted committees and other bodies that need to talk to the Institute.

Specific duties

Many of the Deputy Director's tasks are one-off actions, under the instruction of the Director. There are also a number of ongoing responsibilities, as detailed in the following list.

  • Fostering a productive and coordinated research profile.
    • Convening the LFCS research committee.
    • Stimulating individual grant proposals by LFCS members.
    • Arranging periodic reviews of research areas.
    • Coordinating LFCS response to EPSRC managed programs.
    • Involvement in the Director's determination of LFCS research strategy.
  • Publicity and visibility.
    • Dissemination of research results.
    • Licensing and distribution of software.
    • Content of the institute web site.
    • Relations with EPSRC and other funding bodies.
    • Advocacy for LFCS within the wider research community.
  • LFCS activities.
    • Minicourses, schools, workshops and conferences hosted by LFCS.
    • The annual Milner Lecture.
    • Lab lunch and theory seminar series.
    • Fostering the various LFCS clubs.
    • LFCS awaydays.
  • Educational concerns.
    • Oversight of the Theory Postgraduate course.
    • LFCS postgraduate admissions.
    • Institute representative on the Informatics Graduate School committee.
    • Impact of degree content on LFCS postgraduate studies and recruitment; appropriate vertical integration.
    • Courses for external participants.
  • Finances.
    • Assisting the Director in budget planning and preparation.
    • Stewardship of assorted institute funds: travel, equipment, PhD studentship, small project grants.
  • Relations with industry.
    • Initiating and maintaining industrial contacts and collaborations.
    • Interaction with ERI.
    • Industrial affiliates.
    • Institute representative on the divisional industrial liaison committee.
  • Promoting collaborations within and outwith LFCS.
    • Connecting individual LFCS researchers.
    • Matching specific LFCS skills to the needs of projects in other institutes across the division.
    • Identifying possible partners for involvement in EU and other initiatives.

Ian Stark
Thursday 4 November 1999

Document Actions