|
Acceptable Use Policy
(AUP)
|
A policy defining the way in which an institution’s network may be used. The JANET network as a whole also has an acceptable use policy. Often these policies require a signature from a new member of staff or student before access to the network is granted.
|
|
|
|
|
Development Project
|
A project involving non-academic research or development with the objective of investigating a new technology or approach, or conducting research to inform the planning of a pilot or implementation project. Typically these would result in the acquisition of knowledge rather than the development of services.
|
|
|
|
|
|
Producing the optimal result.
|
|
|
|
|
Efficiency
|
Producing a result with the minimal required resources.
|
|
|
|
|
Failover
|
The ability to switch automatically to standby networks, servers or systems without the need for human intervention. This is often built into critical systems to ensure business continuity in the event of a failure.
|
|
|
|
|
Information Strategy Steering Committee
|
The internal group or committee assigned responsibility for overseeing the implementation of the institution’s information strategy.
|
|
|
|
|
Information System
|
A system that involves the organised collection, processing and transmission of information.
|
|
|
|
|
Information Workers
|
Institutional staff whose primary role is to support the institution’s information systems including IT staff, library staff, etc.
|
|
|
|
|
Interoperability
|
Interoperability standards specify structures and formats that allow data to be shared between systems.
|
|
|
|
|
Implementation Project
|
A full-scale implementation with significant resources attached, clearly defined objectives and an agreed timescale. This type of project lends itself to formal project management techniques.
|
|
|
|
|
Institutional Governing Body
|
The governing body of the institution e.g. University Council or Court
|
|
|
|
|
Pilot Project
|
Projects, usually small-scale, to explore the potential costs, benefits and risks associated with new technologies or systems. The objective of these projects is usually to inform a decision about a larger implementation.
|
|
|
|
|
Policies
|
Documents defining the rights and responsibilities of two or more parties in relation to a particular area of activity.
|
|
|
|
|
Procedures
|
Documents providing guidance in relation to a particular area of activity.
|
|
|
|
|
Senior Executive Group
|
The most senior management group within the institution (e.g. the University Management Group, the University Executive)
|
|
|
|
|
Senior Information Systems Manager
|
The most senior manager in the institution charged with direct management responsibility for information systems (e.g. The Director of Learning and Information Services)
|
|
|
|
|
Service Definition Statements
|
A statement of service availability and service provision. A service statement is much less detailed than a service level agreement
|
|
|
|
|
Service Level Agreements
|
A service level agreement is a formal agreement between a service provider and a service recipient indicating the expected level of service and the rights and responsibilities associated with each party.
|
|
|
|
|
Switchover
|
The ability to switch to standby networks, servers or systems on the event of a technical failure.
|
|
|
|
|
Total Cost of Ownership
|
The total cost of a piece of hardware or software throughout its life. This will include the acquisition cost, on-going support and maintenance costs, etc.
|
|
|
|
|
Users
|
All users of information systems, primarily staff and students within the institution, but also including others who may access information and/or systems through the internet (e.g. potential students, research partners, funders, etc.)
|