Understanding critical software for UKRI digital research infrastructure
Understanding critical software for UKRI digital research infrastructure
This scoping study explores key issues around the critical software required to deliver the UKRI digital research infrastructure (DRI), and recommends what help UKRI could provide to support their investments. It also suggests next steps for future research to support DRI.
In a complex software ecosystem, understanding what software requires support and investment from UKRI is a complicated task. The Software Sustainability Institute (SSI) examined not just a list of software used by infrastructures, but considered a range of other issues. Our research questions were:
What software is used by the UKRI DRI infrastructures researched?
What should be considered as ‘critical software’ for UKRI Digital Research Infrastructure?
What are the risks to critical software for UKRI Digital Research Infrastructures?
How might audits support the infrastructures in preparing for and mitigating risks?
To begin to address these questions, the SSI conducted a short study over the course of six months starting in November 2024, interviewing staff from 3 Compute infrastructures (ARCHER2, JASMIN, Isambard-AI) and 3 Data infrastructures (Seshat - part of iDAH, DARE-UK, PSDI) to ascertain details of their set up, funding, software stack, and audit/risk assessment processes, as well as their definitions of ‘critical software’ and opinions on the risks of disruption to the running of their infrastructures. Then, two focus groups were conducted with staff and users of the wider Compute and Data DRI community in order to corroborate and expand on the themes that arose in the interviews.
The report explores the software stacks of the 6 infrastructures (Appendix B), and provides illustrations of different ‘critical software’. It looks at risks to software and also addresses the role of audits in understanding and preparing for risks to infrastructures. The report indicates how different parameters – types and size of infrastructure, users, available funding, and where the infrastructures were in their life cycle – influence the choices of software in use, and what this means for the risks to the infrastructures.
software, infrastructure, critical software
Thomas, Ben
1baccbdb-cfaa-499b-8773-77c8d4a597cb
Chue Hong, Neil
e71b880a-b3b5-477b-af96-5fdde0e4db98
Hettrick, Simon
9eef9cf0-86e8-4562-bead-684915a1de5c
18 August 2025
Thomas, Ben
1baccbdb-cfaa-499b-8773-77c8d4a597cb
Chue Hong, Neil
e71b880a-b3b5-477b-af96-5fdde0e4db98
Hettrick, Simon
9eef9cf0-86e8-4562-bead-684915a1de5c
Thomas, Ben, Chue Hong, Neil and Hettrick, Simon
(2025)
Understanding critical software for UKRI digital research infrastructure
34pp.
(doi:10.5281/zenodo.15696603).
Record type:
Monograph
(Project Report)
Abstract
This scoping study explores key issues around the critical software required to deliver the UKRI digital research infrastructure (DRI), and recommends what help UKRI could provide to support their investments. It also suggests next steps for future research to support DRI.
In a complex software ecosystem, understanding what software requires support and investment from UKRI is a complicated task. The Software Sustainability Institute (SSI) examined not just a list of software used by infrastructures, but considered a range of other issues. Our research questions were:
What software is used by the UKRI DRI infrastructures researched?
What should be considered as ‘critical software’ for UKRI Digital Research Infrastructure?
What are the risks to critical software for UKRI Digital Research Infrastructures?
How might audits support the infrastructures in preparing for and mitigating risks?
To begin to address these questions, the SSI conducted a short study over the course of six months starting in November 2024, interviewing staff from 3 Compute infrastructures (ARCHER2, JASMIN, Isambard-AI) and 3 Data infrastructures (Seshat - part of iDAH, DARE-UK, PSDI) to ascertain details of their set up, funding, software stack, and audit/risk assessment processes, as well as their definitions of ‘critical software’ and opinions on the risks of disruption to the running of their infrastructures. Then, two focus groups were conducted with staff and users of the wider Compute and Data DRI community in order to corroborate and expand on the themes that arose in the interviews.
The report explores the software stacks of the 6 infrastructures (Appendix B), and provides illustrations of different ‘critical software’. It looks at risks to software and also addresses the role of audits in understanding and preparing for risks to infrastructures. The report indicates how different parameters – types and size of infrastructure, users, available funding, and where the infrastructures were in their life cycle – influence the choices of software in use, and what this means for the risks to the infrastructures.
This record has no associated files available for download.
More information
Published date: 18 August 2025
Keywords:
software, infrastructure, critical software
Identifiers
Local EPrints ID: 505757
URI: http://eprints.soton.ac.uk/id/eprint/505757
PURE UUID: 24bfe532-367e-459f-8c3f-97d9aab994af
Catalogue record
Date deposited: 17 Oct 2025 16:44
Last modified: 30 Oct 2025 03:12
Export record
Altmetrics
Contributors
Author:
Ben Thomas
Author:
Neil Chue Hong
Author:
Simon Hettrick
Download statistics
Downloads from ePrints over the past year. Other digital versions may also be available to download e.g. from the publisher's website.
View more statistics