Service Name

Audience Response System (ARS)

Support

Service Description

To provide support and development for staff on the innovative uses of audience response technologies in their learning and teaching. This will be through the collection and dissemination of good practice (both internal and external to the University) and the provision of staff development opportunities.

To provide ongoing research into the effective uses of Audience Response Systems within UK HEIs.

Service Users

All members of the University of Bath may use the service.

Service Provision

included

  • Provision, maintenance and development of the Audience Response System blog (http://blogs.bath.ac.uk/ars)
  • Provision, maintenance and development of documentation and FAQs for the TurningTechnologies’ ARS hardware. Including, the provision, of the latest stable PC version of TurningPoint 2008 software, which made available via the ARS blog and FAQs via the ARS blog, and the LT FAQs database, http://www.bath.ac.uk/learningandteaching/ltfaq
  • User support and development for technical and pedagogical support and advice, 1-2-1 face to face staff development
  • Development of a community of practice at the University of Bath around the effective use of audience response systems in learning and teaching.

excluded

  • Support for non TurningTechnologies’ ARS hardware.
  • Authoring of materials, content and the development of activities, as the expectation is that users will create their own materials for their learners.
  • Booking of the ARS hardware through the Audio Visual service, http://www.bath.ac.uk/bucs/services/audiovisual/index.html
  • Installation of the TurningPoint 2008 software. For BUCS maintained PCs, this can be requested by filled out the form at: http://www.bath.ac.uk/bucs/help/contact/

Conditions of Use

Remote Access

  • The ARS blog is available both on and off campus via a web browser. The ARS FAQs are available both on and off campus via a web browser.

Access Rights

User Registration

  • N/A

Service Owner (Project Leader)

Business Owner

  • N/A

Technical Lead

  • AV Unit for hardware maintenance
  • BUCS for software installation

Deputy Technical Lead (System Manager)

  • N/A

Escalation

Service hours

Monday to Friday Saturday and Sunday
0:00 to 9:00 Non-core Non-core
9:00 to 17:00 Core Non-core
17:00 to 23:59 Non-core Non-core

Service standards

Core Non-core
Services available Support and development via ARS service blog, LT FAQs database, email, phone and face to face meetings. As core, excluded email and phone.
Hours & days See service hours See service hours
Key performance indicators n/a n/a
Availability (service blog) n/a n/a
Response times – maximum to answer phone (a) acknowledge email (b) and respond to email Phone calls answered within core hours subject to staff availability within the e-Learning team. The aim is to reply to an email query within 2 working days of their arrival. First contact on the next working day
Fix time N/A N/A

Scheduled Maintenance Windows

  • There are no planned maintenance windows for the ARS blog and FAQ service. We will maintain the service on a best endeavour model.

Communication of Service and software updates

  • ARS blog

Critical Incident Notifications

Data Retention and Restoration Service

  • N/A

Recovery Point Objectives

  • ARS Service blog: As soon as possible – best endeavours

Recovery Time Objective

  • ARS Service blog: As soon as possible – best endeavours