Presenting RISE
•Download as PPTX, PDF•
1 like•1,932 views
The Research Infrastructure Self-Evaluation (RISE) framework aims to facilitate communication between stakeholders and foster a shared understanding of research data management service development. RISE identifies common service elements and organizes them into 10 areas and 21 capabilities. It provides a flexible tool for institutions to benchmark current services, define targets, and identify gaps to guide strategy. Field testing validated that RISE allows institutions to assess compliance and contribute to business cases in a half day workshop. Future work includes using RISE in training and connecting its competencies to the European Open Science Cloud.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Presenting RISE
Similar to Presenting RISE (20)
More from Jisc RDM
More from Jisc RDM (20)
Recently uploaded
Recently uploaded (20)
Presenting RISE
- 1. The Research Infrastructure Self- Evaluation framework (RISE) Jonathan Rans Digital Curation Centre, Edinburgh J.Rans@ed.ac.uk Twitter: @JNRans RDM service development using RISE, 27 June 2017, Jisc RDN, York
- 2. What will we cover? 1. Background to RISE 2. The issues that RISE aims to address 3. Developing the framework 4. Trying RISE out 5. Lessons learned
- 3. Previous support for RDM services 2010-2015 – DCC Institutional Engagements • Worked with ca. 50 UK Universities • Deeply embedded support • Resource intensive Development of RDM support tools
- 4. RDM is a shared endeavour RDM servicesLibrary Research Office IT Academics Ethics Business Office Faculty Support Service Managers Infrastructure Managers Administrators
- 5. Issues we aimed to address • Facilitate communication between stakeholders • Get a broad range of input into each service element • Place service elements within the big picture • Foster a shared understanding of service development • Ensure all RDM service elements are addressed • Avoid getting mired in detail • Recognise the impact of institutional context • Confidence that services meet RCUK requirements
- 6. RISE model • Provide a framework to guide discussion • Ability to benchmark current and future service provision to guide strategy development • Define a baseline level of service but • Be relevant regardless of institutional context We aimed to develop a flexible, practical tool which could be used independently
- 7. Identifying common elements CC-BY2.0 Arne HendriksCC0 Alexas_Fotos
- 9. Service elements into capability areas Active data management • Scalability and synchronisation • Collaboration support • Security management 21 capabilities across ten RDM service elements
- 10. Service value levels – our approach Level 0 Level 1 Level 2 Level 3
- 11. Statements describe service levels Security management Level One Level Two Level Three The service provides authenticated access to storage that is protected from unauthorised data access, and researchers are made aware of procedures for data protection and de-identification. The service provides tools/environments that enable researchers to de- identify, encrypt or control access to data as required. The service provides researchers from across the institution with access to ISO 27001/2 or equivalently accredited facilities for analysis of shared sensitive data.
- 12. Using RISE Consider each service element individually Assess your current capability Define your target capability Identify barriers and opportunities OUTPUTS • Reassurance that compliance has been achieved • Gap analysis • Contributes to service development strategy • Contributes to business case • Fostering links between support departments
- 13. Field-testing RISE • Validate the approach • Ensure the descriptions were clear • Apply the framework in different contexts • Use the tool to feed in to different outputs We used the tool with 16 UK universities
- 14. Test subjects Edinburgh – RDM manager Stirling – Intensive, semi-structured interviews Cranfield – Small workshop Northumbria – Small, focused workshop Then a final workshop with 12 universities to validate the final approach. • Aimed for a spread of sizes, specialisation and geographical spread • Brunel, Cambridge, Durham, Exeter, Glasgow School of Art, Hull, London South Bank, Newcastle, SOAS, Strathclyde, Surrey and Sussex.
- 15. Lessons learned • Have a fixed goal communicated to all participants • Allow sufficient time to work through RISE • It will take ½ day to work through with up to six people • Participants should work through the framework individually before discussing collectively • Capture discussion – contextual information is important
- 16. Future directions • DCC is using RISE in training and consultancy • We are developing competency models to connect skills development with service capabilities through EOSC • We have a draft model for repository development capabilities we are connecting with RISE (ReCAP) Image: CC0, Ken Kistler
- 17. Many thanks to for supporting the development of RISE DCC introduction to RISE: http://www.dcc.ac.uk/resources/how- guides/RISE Follow us on twitter: @DMPonline and #ukdcc
Editor's Notes
- When developing individual capability level descriptions we had these general ideas in mind. It’s interesting to note that when people apply RISE to their own context they tend to think of it as a sliding scale.
- Levels are cumulative and represent a development progression. However, unlike other models, the ideal end-point is defined by institutional factors rather than automatically sitting at the right-hand end of the scale. In some circumstances, services can be over-developed…