Joint School Computing Service (JSCS)

Transcription

1 Joint School Computing Service (JSCS) Requirements and Design Workshops: Online Services and Communication School of Biological Science & School of Clinical Medicine

2 Today s Agenda Project background Overview of related services Q&A Break out sessions Review of findings Next steps

3 What is the JSCS project? A collaborative project between SBS and SCM. To establish the feasibility of a Joint School Computing Service, which could potentially provide a wider suite of IT Services to both Schools. The project aims to: determine the requirements of the staff across the two Schools design a set of services which would meet those requirements outline the systems and structures which would deliver those services agree a financial and governance model to enable such a service.

4 JSCS Universal Services User Accounts All staff will get a JSCS Directory User Account which will enable access to JSCS systems including the network, managed computers and online services. Network Connection All staff will have access either to a wired or wireless network connection (local conditions allowing) which they will access using either their JSCS user account or Raven.

5 JSCS Universal Services Computer Support All staff will can get technical support for one or more nominated computers In addition, several options are available for more specialist support. Procurement All staff can contact JSCS for assistance in procuring IT hardware and software. Backup Appropriate backup will also be designed into JSCS services.

6 JSCS, UIS and Local IT Services Relationship between UIS and your local IT support via JSCS: UIS provides centralised IT services Local IT support provides departmental IT service JSCS recognises that both Schools have common needs and that we can improve local IT services, by grouping them together. JSCS will not look to replicate an existing UIS service JSCS and UIS services should be broadly complimentary.

7 Today s workshop Online services & communication Electronic communication, i.e. , instant messaging, phones etc. Using the web to facilitate research input and output. Web based access to research systems. Collaborative tools.

8 Core Services Groupware Voice and Video Telephony Software Services Website and Database hosting Virtual and Physical Server Hosting Managed access to intranet based systems

9 Additional Services Website design, development & consultancy Database design, development & consultancy Application deployment & support.

10 Communication Services Standard IMAP/SMTP services MAPI/RPC mail services Calendar and task scheduling Delegated access to accounts, calendars and tasks Address book and directory lookup Unified communication Instant Messaging Voice Telephony Video Conferencing

11 Collaboration Services Web based application platform Document Management Workflow Management Web Content Management File access and data transfer Web based Standard Protocol based

12 Website and Database Hosting Web hosting for intranet and extranet sites Database hosting for widely used database platforms

13 Software Services Web based access Thin Client based access

14 Web based access to internal systems Data processing applications with a web based interfaces Publication of interface sites to the internet Managed authentication access to the interface site

15 Discussion Topics , Groupware, Voice and Video Telephony and Software Services Website, Database Hosting and Managed access to intranet based systems

16 Break Out Sessions Format for today Break into small groups (one group per topic) Group discussion requirements / identify common ground Each group will write up key points After 30 minutes, rotate round to next topic Present/review feedback

17 Questions? Q. Are there any gaps we missed? Q. Which requirements are common and which specialised? Q. What do we need to add or refine to make the catalogue complete? Q. Which services might be offered by UIS and which by JSCS?

18 Project Next Steps Project team will review all the feedback from this week s workshops. Check that the information gathered is complete. Review this information against the JSCS prototype proposal. The captured requirements can then be drawn into the design of the proposed JSCS services. Any gaps may require follow-up discussions.

19 Project Next Steps (continued) The project team will then finalise the JSCS proposal and catalogue. Circulate to all in-scope departments for final feedback. This will be considered for approval by SBS and SCM IT Committees, the JSCS Steering Group and the Secretaries of both Schools. If approved, Finance and Governance part of the project will begin in January Regular projects updates will be provided via JSCS mailing list.