1 / 19

STEP-F Project Workshop Tuesday 14 th June 2011

STEP-F Project Workshop Tuesday 14 th June 2011. Timetable 10:00 Arrive, coffee 10:30 Start – Welcome etc 12:30 Lunch (buffet) 13:15 Restart 15:30 End/tea Wireless network Access Network: DMU-Guest Username: itms2011 Password: tdqy3199. Timetable. Agenda 1) Welcome & Introduction

leroy-lawrence
Download Presentation

STEP-F Project Workshop Tuesday 14 th June 2011

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. STEP-F Project WorkshopTuesday 14th June 2011

  2. Timetable 10:00 Arrive, coffee 10:30 Start – Welcome etc 12:30 Lunch (buffet) 13:15 Restart 15:30 End/tea Wireless network Access Network: DMU-GuestUsername: itms2011Password: tdqy3199 Timetable

  3. Agenda 1) Welcome & Introduction 2) Background to Step-F Project and its relationship to other JISC/HEFCE programmes 3) Demonstration of STEP-F solution 4) STEP-F project: Solution Design 5) Discussion: ESB, Data standards, Connector design standards 6) Summary of STEP-F and implications for other JISC/HEFCE projects Agenda

  4. 1. WelcomeDr Claire Baines – Chief Operating Officer

  5. 2. Background to STEP-F and its relationship to other JISC/HEFCE programmes

  6. IT Director’s perspective Mike Robinson STEP-F within UMF programme Steve Butcher JISC SPSS and its role Les Ormonde/John Chapman UMF Cloud programme John Milner HEDD application Adrian Preston Background to STEP-F

  7. Les Ormonde Manager SSPS at JISC Advance

  8. SSPS has 4 main dimensions Making it easier for buyers to buy administration systems and associated services and get better deals Anticipation and aggregation of demand Our procurement expertise Upskilling HEI procurement staff Making it easier for sellers to sell Bigger, better defined procurements with lower cost of sales Make information exchange between administration systems easier Agreeing cross-sector standards Creating and maintaining integration tools that all can use Moving towards shared services, operated off site A few words about SSPS

  9. We want to understand the appetite for the kind of integration that you will see today When demand is proven, we expect to build an industrial strength ESB SSPS will inherit the IP from this project We will maintain a library of integration artefacts to be used in future implementations Important Messages

  10. We want to gauge interest in a sector/industry-wide forum for developing ideas We need to hear from Institutions About their procurement plans About their integration requirements We want to hear from suppliers About their product plans About their innovative ideas for making their products available To have a discussion or to take things further, contact me les.ormonde@jiscadvance.ac.uk We want to hear from you

  11. 3. Demonstration of STEP-F

  12. 4. STEP-F Solution Design

  13. 5. STEP-F Discussion

  14. Key areas for agreement or further work Cloud-based ESB What issues should be considered prior to procuring the sector-cloud? b) Should there be one or many ESBs? Does it matter whether there are different ESBs at different HEIs? What guidance could be given to any institution? e) Who should STEP-F hand over their knowledge to? STEP-F Project outcomes

  15. Key areas for agreement or further work 2. Data standards within the ESB Is it agreed that the ESB layer should ONLY carry data of agreed data standards? b) Who should point to which standards should be used? What is the role of the ‘standards body’ in defining, certifying, policing data usage? d) Who should STEP-F hand over their knowledge to? STEP-F Project outcomes

  16. 3. Connectors at the ESB end Are there multiple potential solutions/designs in different circumstances? b) Can STEP-F make any strong recommendations? c) Does the sector require ‘best practise’ design standards for these connectors? d) How should these standards be developed? e) Once developed, how should HEIs/vendors be encouraged to adopt them? STEP-F Project outcomes

  17. 4. Connectors at the application end Are there multiple potential solutions/designs in different circumstances? b) Can STEP-F make any strong recommendations? c) Does the sector require ‘best practise’ design standards for these connectors? d) How should these standards be developed? Who will lead this work? e) Once developed, how should projects/ HEIs/vendors be encouraged to adopt them? STEP-F Project outcomes

  18. 5. Next STEPs

  19. thank you

More Related