JSCS Proposal. The high level statement of what the JSCS should deliver and achieve

Transcription

1 JSCS Proposal The high level statement of what the JSCS should deliver and achieve

2 Introduction... 3 Project Requirements... 3 Assumptions... 3 Proposed JSCS Service Catalogue... 5 Introduction... 5 Universal Services... 5 Education Services... 7 Scientific Computing Services... 7 Storage Services... 8 Hosting Services... 8 Development Services... 9 Administrative Services... 9 Page 2 of 9

3 Introduction The Joint School Computing Service (JSCS) proposal is a statement of the project team s current understanding of what the service should deliver. It is based on the project requirements, the current services delivered in both Schools, the common needs already identified across both Schools, and assumptions based on those requirements. Those assumptions have been validated and stated here as a proposal, and this proposal is what will be reviewed, developed and finally agreed. Project Requirements 1. Provide a service as good or better and to equivalent cost to peer institutions worldwide 2. Meet the IT needs of all participating Departments and Institutes 3. Deliver a Catalogue of Services from which Departments can select according to the specific needs, requirements and finances. 4. Deliver a service catalogue with Service Level Agreements covering resilience, capacity, performance, security and usability. 5. Provide service uptime of 99.9% for both Schools subscribed to the JSCS 6. Deliver a service that can grow its existing capability and expand in new areas as needed 7. Must result in a management structure allowing for continuous improvement, training, striving for excellence 8. Must result in a clearly defined overview and description of minimum level of experience and competences required for the JSCS staff roles 9. Should provide expanded skill sets and increased development opportunities for staff 10. Should result in a Financial and Governance model enabling the JSCS to be implemented and allow for growth and investment 11. For existing CSCS Users, should enable further economies of scale and consequently an expanded catalogue of services Assumptions In order to deliver something which satisfies the project requirements we have made some assumptions based on those requirements. We then need to test, validate and if necessary change those assumptions through discussion with stakeholders. Once we have reached a consensus on these assumptions they (and the project requirements) will form the basis of the JSCS design from this point on. 1. Transition 2. Services a. In scope institutions will engage fully with the requirements gathering and catalogue sign off process, resulting in a detailed understanding of their IT needs. b. There will be a phased migration from current IT service provision to the relevant JSCS services. Page 3 of 9

4 3. Systems 4. Staff a. A service level agreement and minimum response time for providing support will be defined for all types of incident. b. There will be a single point of contact for JSCS service users (a helpdesk or service desk). c. There will be single instances of the necessary supporting systems (e.g. incident, request and problem management, configuration, knowledge and change management, monitoring systems). d. There will be a single set of working practices, standard operating procedures, project management methodologies, information security management system etc. e. JSCS will offer services either entirely based on JSCS infrastructure, based on UIS infrastructure but managed, maintained and supported by JSCS, or support service provided directly by UIS to the end user, but supported in the first instance and to some extent administered by JSCS staff. f. The default position will be to use existing UIS services where they meet the user requirements, or can be adapted or transformed within a reasonable timescale to meet those requirements. g. All JSCS Services will be included in the University IT Service Catalogue as either Core Services (available to all) or Local Services (available across both Schools). a. All services will be designed to work on Windows, Mac and Linux (as supported by the vendor) and both desktop and mobile devices wherever possible. b. Infrastructure hardware and software, staff skills and working practices will be of the highest level to achieve the target uptime (e.g. strong change control, enterprise level equipment). c. The JSCS service will be based on a single Active Directory forest to which all JSCS users will authenticate, which is likely to integrate with University Active Directory forest run by UIS either at the point of creation or after. a. Based on the information obtained to date and in order to enable the new service to be provided whilst fulfilling the project objectives, it is envisaged that potential changes would be required to the existing CSCS and SBS IT structures. b. One proposal is that the staff currently part of CSCS and the IT staff in SBS in scope departments may merge into a single service provider unit. In that event the following assumptions would apply: i. The unit would be managed under a new management structure. ii. Role descriptions of staff will be standardised to ensure parity of roles, responsibilities and appropriate grading across the potential merged group. iii. Existing line management arrangements may change. iv. Staff may be relocated from their existing locations. Page 4 of 9

5 5. Finance v. Staffing levels would be appropriate to support the existing scope but with flexibility to support growth whilst continuously improving the service. vi. Training and upskilling may be required and where appropriate will be made available to staff within any new structure/role. c. A full 90 day managing change process would be conducted under the University Organisational policy which would include a thorough consultation process once a full business case had been drafted on any formal proposals. a. Services will be tiered to meet different needs and budgets (e.g. bronze/silver/gold) rather than a one size fits all model. b. Funding will be a combination of cost recovery, CHEST funding and grant funding. The finance and governance stage of the project will define the balance of these and will ensure that we make best use of the funding available, with cost recovery only where absolutely necessary. Proposed JSCS Service Catalogue Introduction Below are listed all the services which we have deduced from the requirements gathered thus far. In some cases these requirements will probably be met by a JSCS Service, but in some cases these services may be better provided by UIS, and some services below are identified accordingly. If there is a service which you require which is not on this list, please contact us at jscs@medschl.cam.ac.uk. All services should be assumed to be accessible from Windows, Mac and Linux unless specified otherwise. Any web based services should be accessible from mobile devices as well as desktop or laptop systems. All JSCS services will be documented online with a how-to guide and an FAQ. In addition, training will be made available either online or in classroom format, aimed at both novice and advanced users. For software and University systems existing UIS training courses will be highlighted, and other free training resources where available. There will also be a specific training package aimed at staff induction and new student intakes to highlight appropriate services and make key information easily available. Universal Services These services were requested by all in scope in departments during the requirements gathering and are considered a baseline of services which should be available to all departments without restriction. User Accounts All staff, students and (where appropriate) visitors will get a Directory User Account, provisioned either by UIS or JSCS, which will enable access to JSCS systems including the network, managed computers and online services. These accounts could be requested manually or created automatically from University system data feeds (e.g. CHRIS, CamSIS). Accounts may also be created for shared use (e.g. a shared role based mailbox for a research study). Page 5 of 9

6 Every staff account will come with a personal home directory for storing files. This will be accessible from any internet connection via a web interface and allow staff to store, search and sync files with one or more devices. Staff accounts will also include a groupware account which will allow communication and meeting scheduling with any other JSCS user or JSCS managed resource. This would include list functionality (with membership delegated to specific users) and either aliases or role based mailboxes for multiple users to access. quotas and archiving should allow users to retain access to for as long is needed, in a searchable form. Finally, staff accounts will also be able to communicate with any other JSCS user using instant messaging, accessible from any desktop, laptop or mobile device running Windows, Mac OS X, ios, or Android. Network Connection All staff will have access to wired and/or wireless network connections (local conditions allowing) authenticated using their User Account. They will also have remote access via VPN, which will allow connection to any internal JSCS system as if they were physically on the network. Where appropriate staff will be able to connect to hosts within the JSCS network via SSH or Remote Desktop. Computer Support All staff will get technical support for one or more nominated computers (whether desktop PC, laptop, notebook or tablet, and running Windows, Mac or Linux). In addition, several options will be available for more specialist support (e.g. support for attaching microscopes, scanners, imaging equipment etc.) The response time for computer support will vary according to the severity and impact (e.g. a computer which stops working completely in a lecture will get the fastest possible response, one computer amongst a cluster of student computers going slow will be responded to more slowly). There are a number of specialised requirements which fall under the general heading of Computer Support, which are outlined below. Instrument Connected Computer Support A light touch service supporting PC's attached to lab equipment. The service would provide a minimal amount of care / changes so as not to disrupt the equipment or its usage, i.e. anti-virus, networking and remote or onsite support and appropriate operating system patches on a case by case basis. Where support for legacy operating systems is required to service expensive equipment security precautions would be taken to minimise the risk of the system being compromised. Student Clusters Provision and support of computer rooms for student use, either based on UIS Managed Clusters or locally provisioned systems. Procurement All staff will be able to contact JSCS for assistance in procuring IT hardware (including computers, workstations, laptops, tablets, phones, servers, printers, scanners, projectors and peripherals) and software (including desktop and server software, business applications, building and facilities management etc.) This could also include configuration, delivery and installation of purchased hardware Page 6 of 9

7 where required. Software procurement (wherever possible) will be on a self-service basis where users install software on demand and only need to enter a license key where appropriate. Intranet Provision of web based services to facilitate communication and collaboration within a department or group, or between departments or groups and their external collaborators (including file sharing). This would also improve knowledge retention within and across groups irrespective of staff changes. Securely accessible outside the JSCS network it will allow for granular access control for groups or individual users, and features to encourage communication such as team and project spaces, search, discussion pages etc., and provide a simple application interface for administrative functions such as equipment and room booking. Education Services Virtual Learning Environment Design, maintenance and support of Moodle based virtual learning environments, whether hosted by UIS or JSCS. Timetabling software Software to allow for the planning and scheduling of teaching, and the communication of those timetables in a user friendly format for a variety of audiences and devices. Audio-Visual systems in teaching and meeting rooms Setup, maintenance and support for audio-visual systems (projectors, speakers, microphones, recording and streaming systems etc.) used in seminar rooms, lecture theatres, meeting and committee rooms. Live or after the event streaming of lecture videos would be delivered in collaboration with UIS, and would have to deal with Intellectual Property and other data and privacy issues. Scientific Computing Services UIS HPCS For established computational analysis jobs requiring significant resources (processor, memory or storage) the UIS HPC Service would be the most effective option. JSCS Local Clusters Support of local HPC resources used for development and testing of jobs before scale out to the UIS HPCS, or live operation of smaller analysis workloads or workloads which otherwise cannot be run on the UIS HPCS. This service will be aligned with the UIS service to allow a smooth scale out. The service may also include an end of life migration path to UIS HPCS (where appropriate). Scientific Computing Support The installation, management and support of scientific computing hardware and software, e.g. Bioinformatics, Geographic Information System (GIS) or Imaging. This includes but is not limited to: large processor / RAM machines, high performance desktops and their associated operating system and software, usually used in relation to statistical analysis. This service sits alongside and complements the JSCS Computer Support, Managed Server and HPCS Services. Page 7 of 9

8 Laboratory Information Management System (LIMS) A service which would support sample management and auditing, potentially integrate with instruments (e.g. barcode handling and instrument calibration) and applications (e.g. inventory management and time tracking). Storage Services Group Data Store Group shares provided to departments or smaller groups to allow easy access to shared data, this area will be fully backed up and mirrored offsite. Large Data Store A storage platform that allows large storage of data but also takes into account the requirements for Storage that's optimised for high performance computing and larger datasets. Access should be provided to all users hardware using all supported protocols e.g. NFS/CIFS/ISCSI etc. Archive Store Long term storage at lower cost for data which is no longer in use but may still need to be retrieved for open access purposes, or to satisfy grant funder conditions. Secure Data Store A storage platform that allows the storage of sensitive data including PID. This data should be stored using the HSCIC Information Governance Toolkit and/or ISO27001 policies and procedures to ensure the security of sensitive research, in line with best practice guidance. Secure File Transfer Service for Sensitive Data A secure system to share sensitive data/pid with remote users inside and outside of the University. Hosting Services Managed Server Installation, maintenance and support for Windows and Linux servers providing scientific computing services other than HPC, including (but not limited to) databases, web servers, hosted applications, collaboration and sharing. Unmanaged Server Installation and hosting for Windows and Linux servers providing scientific computing services as above, but maintained and supported by the department or group who uses it. Database hosting Provision of a database(s) that will be fully supported by a central management system, providing support for a wide range of database technology s e.g. MS SQL, MySQL, PostgreSQL etc. This will include backup/restore and provide a fully user hands off service for those that need a database but don t know how to support the backend infrastructure. Page 8 of 9

9 Website hosting Provision of a website for departments and groups using the current University style. These sites will be hosted in a centrally managed and supported content management system (CMS) and the service will include a migration path. Provision of more sophisticated research data driven web applications without a CMS to facilitate communication or analysis of research data, or satisfy Open Access requirements. Development Services Website Design/Development/Consultancy Web design/development/consultancy to assist with design, advanced CMS configuration including development of plugins, or provide additional functionally outside the CMS. Database Design/Development/Consultancy Database design/development/consultancy for users that require a fully managed/unmanaged database service. Users can choose the level of support they require based on their needs to level of technical knowledge. This would include migration from legacy or outgrown database formats to more robust enterprise database platforms. Data Curation and Management Assistance with the planning of data collection, organisation, and sharing of data for research. Provided in partnership with the University Library and Open Data Team. Administrative Services Online room and equipment booking A centralised system for the booking of meeting and committee rooms, lecture theatres, laboratory and audio-visual equipment. Building and Facilities Management System Support Support for building and facilities management systems such as card access, building management and CCTV, including the liaison with the system supplier to fix problems outside the remit of JSCS. Visitor Information System A system which tracks visitors from the initiation and signing of the visitor s agreement, the setup of services required for the duration of their stay, their support whilst they are visitors, and the termination of their agreement. This may be a service provided by UIS, or JSCS, or a mixture of the two. Printer Support Setup, configuration and maintenance for desktop printers, network/workgroup printers and multifunction printers. The level of service will differ dependent upon the printer, with improved functionality, performance, capacity and security the larger the device. Software and Hardware Asset Management and Reporting A web based interface which provides department administrators and other authorised staff with information about the PCs, laptops and printers on the network, and any software installed on those systems. Page 9 of 9