Assistant Director, John McAuley

Role Definitions

1. Security

Role: To oversee all matters in relation to the security of University ICT systems and the information they process. To ensure that appropriate policies, processes and procedures are in place - and that these are reviewed, monitored and enforced.

Scope: All aspects of the security of lCT systems and the information they process including: server systems, end user systems, network infrastructure components.

Includes: IS Policy; Security Incident protocol; SA Charter; secure protocols. Security incident management - ensuring that incidents are handled and that processes/rules etc are in place to control this.

2. Regulatory

Role: To ensure that University responds appropriately to the regulatory contexts within which it operates; that CiCS systems policies and processes fit within the University's own regulatory framework; and to ensure that CiCS documents, promotes and enforces it's own regulations. To ensure that issues that arise from these regulations are dealt with.

Scope: External legal context (e.g. RIPA, computing misuse laws), JANET. Regulations include University regulations and policies. Does not include DP A or FolA.

Includes: Code of practice; CiCS 'rules and regulations'; policies on eligibility/access to systems and control of this; UCard Handbook, UCards system, CRISP. Ensures that breaches of regulations are investigated, reports/complaints are dealt with, policies and procedure to cover this documented and published including any sanctions.

3. Policy

Role: To take an overarching view of CiCS policies and to provide a framework that ensures consistency and completeness: provides a comprehensive list and reference point; facilitates the publication and promotion of policies, defines the need for review and responsibility; deals with issues that arise (e.g. contradiction, conflict; breach)

Includes: All CiCS policies - except that nearly all will actually be owned and maintained under separate roles.

4. Customer Service Strategy

Role: To develop an overarching framework that defines how our services are developed, introduces, implemented and supported - and how these are monitored, measured, evaluated and reviewed. To ensure that our services become/remain customer focussed.

Scope: All services/systems in as much as all services ultimately affect the end user.

Includes: A framework such as ITIL: services strategy, service development, service transition, service operationalisation, service review. Plan of how to develop and implement such a framework.

5. Communication Strategy

Role: To develop an overarching communication strategy that aims to define integrate all modes of communication internal and external to the department.

Scope: All communication whether formal or informal

Includes: Formal channels: e.g web site, emails, presentations, documentation, training, publicity, marketing, Annual report, specific meetings (e.g. CiCS User group, dept meeting) newsletters. Informal channels: responses to individuals and groups; telephone manner; incidental comms within more formal e.g within specific training, what we say elsewhere at meetings with individuals etc.

6. Learning and Teaching Strategy

Role: To ensure involvement in, and influence on, University L&T processes and policies.

Scope: All aspects but especially in relation to infrastructure and physical provision.

Includes: AV, student computing, teaching spaces, webCT, managed desktop apps, portal, wireless, residences, broader infrastructure ideas. Working with Library and other keystakeholers.