STEP-F PROJECT WORKSHOP

TUESDAY 14TH JUNE 2011

Timetable

Timetable10:00 Arrive, coffee 10:30 Start – Welcome etc12:30 Lunch (buffet)13:15 Restart15:30 End/tea

Wireless network Access Network: DMU-GuestUsername: itms2011Password: tdqy3199

Agenda

Agenda1) 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

1. WELCOMEDR CLAIRE BAINES –

CHIEF OPERATING OFFICER

2. BACKGROUND TO STEP-F AND ITS RELATIONSHIP TO

OTHER JISC/HEFCE PROGRAMMES

Background to STEP-F

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

LES ORMONDEManager SSPS at JISC Advance

A FEW WORDS ABOUT SSPS• SSPS has 4 main dimensions

1. 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

2. Making it easier for sellers to sell Bigger, better defined procurements with lower cost of sales

3. Make information exchange between administration systems easier Agreeing cross-sector standards Creating and maintaining integration tools that all can use

4. Moving towards shared services, operated off site

IMPORTANT MESSAGES

• 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

WE WANT TO HEAR FROM YOU• 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

3. DEMONSTRATION OF STEP-F

4. STEP-F SOLUTION DESIGN

5. STEP-F DISCUSSION

STEP-F Project outcomes

Key areas for agreement or further work

1. Cloud-based ESBa) What issues should be considered prior to procuring the sector-cloud?

b) Should there be one or many ESBs?

c) Does it matter whether there are different ESBs at different HEIs?

d) What guidance could be given to any institution?

e) Who should STEP-F hand over their knowledge to?

STEP-F Project outcomes

Key areas for agreement or further work

2. Data standards within the ESBa) 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?

c) 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

3. Connectors at the ESB enda) 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

4. Connectors at the application enda) 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?

5. NEXT STEPS

THANK YOU