The Technical Evaluation Group (TEG) was responsible for defining the technical requirements for the groupware solution. These included, but were not limited to: scalability, system availability, security, authentication and authorisation, data import/export, hardware platfoms, backup and disaster recovery, accessibility and standards for interoperability. The technical requirements were driven by a combination of the functional requirements, critical success factors for delivering enterprise systems, and the standards necessary to ensure that the groupware solution is suited to Oxford's devolved and heterogeneous IT environment (where, for example, there exist a mixture of hardware devices, operating systems, and client applications). The Technical Evaluation Group operated in conjunction with the Short-listing Panel and had the responsibility for advising on, and recommending, solutions on the basis of the technical specification.
1. TEG remit
The remit of the Technical Evaluation Group was to take a full and active part in the groupware evaluation and selection process through:
- defining the technical requirements and standards that any groupware solution must meet;
- evaluating proposed solutions against the specified technical requirements including, where appropriate, technical analysis and testing of short-listed solutions;
- identifying outstanding technical issues with any short-listed solutions and seeking clarification from suppliers through the Chair of the Short-listing Panel;
- providing expert advice and clear recommendations to the Short-listing Panel relating to all technical aspects;
- acting as a source of technical expertise to the Project Team during the initial implementation phase.
2. Membership of the TEG
Members of the TEG are appointed for their technical knowledge and experience of deploying and supporting University-wide systems. The TEG is not intended to be representative of different constituencies (that is the role of the Short-listing Panel). Members are expected to dedicate significant time to the Group, especially during the selection phase.
The TEG is chaired by Peter Jones, Senior Specialist, Hierarchical File Server, OUCS.
The TEG has established an email list (email@example.com) which is open to individuals who have an active interest and expertise in the technical aspects of a groupware solution.
The Chair of the TEG is an ex officio member of the Short-listing Panel. The Vice-Chair and/or the Technical Secretary of the TEG may be in attendance at Short-listing Panel meetings.
Currently, the TEG membership includes:
- Adrian Parks, Systems Administrator, NSMS
- Alex Winawer, Systems Development and Support, OUCS
- Andy Cotgreave, Student Information Systems
- Andy Saunders, Communications Programmer, Networks
- Barry Cornelius, Information Services, OUCS
- David Janes, NSMS
- David Popplewell, Experimental Psychology
- David Rischmiller, OUCS
- Ian McArthur, Department of Phyics
- John Ireland, Jesus College
- Lou Burnard, Assistant Director, OUCS
- Mark Norman, Groupware Project Manager, OUCS
- Mark Timms, BSP
- Matthew Buckett, WebLearn Developer, OUCS
- Mike Fraser, Infrastructure Systems and Services, OUCS
- Pete Biggs, Groupware Project Board
- Pete Jones, Senior Specialist, Hierarchical File Server
- pod, Systems Development and Support, OUCS
- Ray Miller, Section Manager, Systems Development and Support
- Robin Stevens, Network Security, OUCS
- Sebastian Rahtz, Information Manager, OUCS
- Sylvain Phaneuf, IMSU
- Tom Jones, Systems Development and Support, OUCS
3. Contacting the TEG
The TEG may be contacted via the Groupware Project email address, firstname.lastname@example.org.
4. TEG documentation
Minutes of TEG meetings and other relevant documents will be made available online.