SPECTRUM: A Strategic Framework and Technical Blueprint for European Exascale Research Data and Compute Infrastructure
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
Preprint of a paper submitted to the proceedings of the 28th Conference on Computing in High Energy and Nuclear Physics (CHEP 2026), to be published in EPJ Web of Conferences.
arXiv:2610.40493v1 [cs.DC] 29 Oct 2026
SPECTRUM: A Strategic Framework and Technical Blueprint for European Exascale Research Data and Compute Infrastructure Sergio Andreozzi1 ,∗ , Stefano Bagnasco2 , Florian Berberich3 , Tommaso Boccali4 , Concezio Bozzi5 , Luis Cifuentes3 , Luca dell’Agnello6 , Amaël Ellien7 , Chiara Ferrari7 , Luciano Gaido2 , Maria Girone8 , Hanno Holties9 , Hans-Christian Hoppe3 , Valentin Jay Blanchard10 , Corentin Lefevre10 , Kristen Lutz11 , Andrea Manzi1 , Shan Mignot7 , Raymond Oonk11 , Xavier Salazar Forn1 , David Southwick8 , John Swinbank9 , Jeff Wagg7 , and Eric Wulff8 1
EGI Foundation, Amsterdam, Netherlands INFN Sezione di Torino, Torino, Italy 3 Forschungszentrum Jülich, Jülich Supercomputing Centre, Jülich, Germany 4 INFN Sezione di Pisa, Pisa, Italy 5 INFN Sezione di Ferrara, Ferrara, Italy 6 INFN CNAF, Bologna, Italy 7 Observatoire de la Côte d’Azur, Université Côte d’Azur, CNRS, Nice, France 8 CERN, Geneva, Switzerland 9 ASTRON, Netherlands Institute for Radio Astronomy, Dwingeloo, Netherlands 10 NEOVIA Innovation, Paris, France 11 SURF B.V., Utrecht, Netherlands 2
Abstract. The HiLumi LHC, the SKA Observatory and LOFAR 2.0 will take
High Energy Physics (HEP) and Radio Astronomy (RA) towards exabyte-scale data within the next decade, beyond the capacity of today’s infrastructure. The SPECTRUM project responded with two documents built on the same evidence. A Technical Blueprint describes a European compute and data continuum as a capability map, consolidates the gaps found in HEP, RA and related use cases, and recommends technical actions in eight areas. A Strategic Research, Innovation and Deployment Agenda (SRIDA) organises thirteen priorities in four pillars, maps them to investment areas and European funding instruments, and phases them over a roadmap set against the timelines of the three instruments. This paper, by editors and contributors of both documents, summarises them, their consultative method and the impact the SRIDA expects.
1 Introduction High Energy Physics (HEP) and Radio Astronomy (RA) enter the exascale era in the same decade. The LHC, where the Higgs boson was discovered, is undergoing a major upgrade. The High-Luminosity LHC (HiLumi LHC) should be operational in mid-2030, to study the Higgs boson in greater detail and look for rare new phenomena [1]. The two largest LHC ∗ e-mail: sergio.andreozzi@egi.eu
experiments, ATLAS and CMS, project disk needs of about 3 EB and 1.5 EB and tape archives of 4 to 6 EB by the mid-2030s [2–4]; ALICE expects its computing needs to grow by about 15% a year until 2041, and LHCb its simulation output about 7.5-fold from Run 4 to Run 5 [5]. LOFAR [6] surveys the low-frequency radio sky to study how galaxies, clusters and active galactic nuclei form and evolve. Its upgrade, LOFAR 2.0, will start full operations during 2027; it is expected to need about 100 PB of archive storage over five years and 200 million core-hours of processing a year [5]. The SKA Observatory [7], whose science cases include the formation of structure in the early universe and neutral hydrogen in galaxies [5], processes its data streams in Science Data Processors near the telescope sites in Australia and South Africa [8]. During full operations it will distribute up to 700 PB of observatory data products a year to the SKA Regional Centre Network (SRCNet) [2, 5]. At full operation, from 2030 onwards, the HiLumi LHC and the SKA Observatory will each generate hundreds of petabytes a year, an order of magnitude beyond current capacity [9]. The large-scale computing, data and network capabilities that both communities use come from several sources. Central facilities, such as the CERN Tier-0 and the SKA Science Data Processors, are funded by the host organisation. Most other capacity is pledged by countries and institutes: WLCG rests on 65 memoranda of understanding signed by funding agencies [10], the LOFAR Long Term Archive already runs as a distributed system at three sites under service-level agreements [8], and SRCNet, still under construction, is developing comparable arrangements [2, 9]. The pledged capacity is itself part of wider pan-European digital infrastructures: European WLCG Tier-1 centres, for example, belong to the EGI Federation’s high-throughput infrastructure, which serves many other communities [2]. The EGI Federation also supports WLCG with federation services [10], EOSC offers channels for the secondary reuse of research data, and GÉANT connects the sites through its high-speed network. More recently, EuroHPC has offered access to its supercomputers, where HEP and RA can explore extending their workloads; its allocation model differs from pledges, granting time by competitive calls, typically for one year [9]. SPECTRUM, a Horizon Europe coordination and support action (January 2024 to June 2026), produced two documents on the compute and data continuum that Europe needs for HEP and RA, together with research infrastructures, digital infrastructure providers and policy stakeholders. The Technical Blueprint (D6.1) [2] covers what the continuum must deliver, for infrastructure architects. The Strategic Research, Innovation and Deployment Agenda (SRIDA, D7.1) [9] identifies who should act, when and with which resources, for programme owners, funders and infrastructure leaders. Compared with earlier studies, SPECTRUM adds an integrated analysis of HEP and RA requirements and gaps, with one template for both, joint actions mapped to European funding instruments and phased in a roadmap, and a proposal to credit users in units of environmental impact in place of core-hours. The SRIDA’s priorities rest mainly on HEP and RA needs. For other communities to judge which findings transfer, it lists its assumptions: data correlated or reconstructed centrally, non-personal, open after time-limited embargoes, processed for throughput with real-time filtering at source, and governed by formal multinational structures over decades [9]. It also names the network underpinning the continuum as important but leaves its detailed treatment to follow-up work.
2 Method Both documents came out of one consultative process (Figure 1). The Community of Practice, launched in June 2024, had 65 distinct participants from HEP, RA and digital infrastructures in six working groups at the start of 2025, and a survey of these communities in July 2024 received 75 valid answers, about a quarter from infrastructure managers [11]. The findings were then drafted from fourteen use cases (six from HEP, five from RA and three from other
Figure 1. The consultative process behind the Technical Blueprint and the SRIDA, 2024 to 2026, from D3.1, the Experts Meeting summary and D7.1 (Section 2, Annex C and version history) [9, 11, 16].
domains) documented with one template [5], an assessment of twenty European digital infrastructures [8], an analysis of access policies [12] and desk research on strategy documents and earlier studies [9]. Among the earlier studies, the HEP Software Foundation roadmap set the software and computing R&D agenda for the HiLumi LHC era [13]; the WLCG Strategy 2024–2027 calls for a reference implementation for integrating high performance computing (HPC) and multi-year resource planning, and for WLCG to consider pledges from timelimited allocations [10]; the Strategy for HPC Integration in WLCG/HEP (2025) sets out the technical, organisational and policy barriers to using HPC [14]; and the JENA computing initiative, which ran a joint survey with SPECTRUM [11], made compatible recommendations on HPC access, interoperability and identity [15]. Working groups led by project partners drafted the SRIDA priorities, which were grouped into pillars in November 2025; interviews with community experts tested the draft findings, and the External Advisory Board advised on the priority framework (D7.1, Annex C). Polls at the EGI 2025 and ISC 2025 conferences gave early public input. The drafts were published on 11 December 2025 [17]; the consultation survey received 26 completed responses from nine countries (25 on the Blueprint, 10 on the SRIDA), and invited experts discussed the results in Barcelona on 18 and 19 February 2026 [16]. The SRIDA’s investment and roadmap sections were written after this consultation. The SRIDA frames the work as three phases [9]: anticipate how gaps and technologies may evolve, analyse (the two documents drafted in parallel, each priority checked against the Blueprint) and prepare a roadmap working back from a vision for 2035. It names crossimpact analysis and backcasting among its techniques; its published record is a priority template that cites the Blueprint’s gaps, capabilities and actions (D7.1, Annex B), the evidence tables of Annex C and a table of dependencies between priorities (D7.1, Table 6.4.1). The evidence has a known scope: the Community of Practice chose the use cases [5], the RA cases predate many SRCNet design decisions [2], consultation respondents self-selected, and theoretical and lattice HEP were under-represented [16].
3 The Technical Blueprint This section follows the Blueprint’s four steps: a capability map, consolidated gaps, recommended actions in eight technical areas, and sustainability [2]. 3.1 Capability map
The Blueprint treats the continuum as a system of systems linking data centres, HPC, cloud and quantum platforms, networks and instruments, and breaks it down into capabilities: functions or services that the infrastructure provides to scientific workflows [2]. Figure 2 shows the capability map: five layers from resources to applications and three transversal areas.
Figure 2. Capability map of the European compute and data continuum: five layers (right) and three transversal areas (left). Redrawn from the Technical Blueprint, Figure 1 [2], under CC BY 4.0.
Most of these capabilities already exist in one or both communities, but they are not necessarily aligned between them or at the same level of maturity. Rucio manages more than an exabyte for ATLAS and CMS across over 120 storage centres and provides data management for SRCNet [2, 9]; CernVM-FS distributes software to thousands of WLCG nodes and to LOFAR, and EESSI uses it to deliver optimised stacks to EuroHPC systems [2]. Working through the map helped HEP and RA align on these capabilities. For assessments as capabilities mature, SPECTRUM defined a Capability Alignment Maturity Framework with six levels, from unaligned (0) to operational integration (5). 3.2 Gaps and recommended actions
The Blueprint consolidates sixteen gaps from the use cases, the infrastructure assessment, the access policy analysis and the Community of Practice (D6.1, Table 1). We classify them into four groups. Access: fragmented identity, little interactive access, few high-level interfaces, and multi-factor authentication that breaks unattended workflows. Workflows and software: stacks that differ between sites and architectures, workflow engines split between communities, and AI/ML platforms detached from data and compute services. Data: no unified approach to FAIR storage and provenance, site-specific transfer tools, and near-real-time processing for RA transient searches and some HEP triggers. Resources: one- to two-year allocations against decadal programmes, accounting bound to single infrastructures, and no cross-site monitoring. Three gaps cut across all groups: co-design, a fragmented workforce, and security for sensitive data, which HEP and RA primary data do not involve [9]. The recommended actions fall in eight technical areas (D6.1, Sections 5.1 to 5.8), listed in Table 1 with the SRIDA priorities that take them up. Many have both an organisational and a technical side: strategic access within EuroHPC with a voice in system co-design, joint data challenges, standard HPC interfaces, and a service-account model that HPC security policies can accept. On GPUs and other accelerators the Blueprint is cautious for offline HEP workloads: general-purpose simulation, reconstruction and analysis codes remain largely
Table 1. Recommended action areas of the Technical Blueprint (D6.1, Sections 5.1 to 5.8; abridged) and the SRIDA priorities that take them up, from D7.1 Annex A and Table C.4.1 (whose pre-final D6.1 section numbers are matched here by title). P09 and P12 draw on D6.1 Section 3. Action area
Recommended actions
SRIDA
5.1 Interface standardisation 5.2 Co-design of computing, data, networks 5.3 Software portability 5.4 Data management and networks 5.5 Workflow adaptation 5.6 Security and AAI
Standard HPC access interfaces; middleware interoperable with the EuroHPC Federation Platform (EFP) identity and allocation APIs. Strategic access or long-term allocations in EuroHPC and national HPC, with a voice in system design; programmable networking.
P04
Code surveys for GPU and HPC readiness; portability-framework pilots; CernVM-FS and container distribution; FAIR software curation. Joint SRCNet, WLCG, LOFAR, HPC data challenges; EFP-ready transfer tools (FTS, Rucio, iRODS); aligned site policies. Workflow systems integrated with HPC resource managers; common APIs with unattended execution, provenance and orchestration. AARC-compliant AAI mapping VO membership to HPC access; harmonised HPC authorisation policies; auditable service accounts. Tasks suitable for ML acceleration identified; double-precision needs communicated to HPC planners; ML training. Multi-year and strategic HPC projects for allocations aligned with experiment timelines; a study of lifecycle-aligned allocation models.
P08, P10
5.7 AI/ML integration 5.8 Long-term provisioning
P01, P11, P13
P05 P04, P06 P03 P07 P01, P02
CPU-bound, pilot ports have so far widened hardware coverage more often than they have delivered large speed-ups, and CPUs will still be needed to drive GPU pipelines [2]. Online processing is further ahead: GPU reconstruction runs in production in the Run 3 trigger and synchronous-processing farms of LHCb, ALICE and CMS [18–20]. RA already runs GPUs at the instrument: LOFAR’s correlator and beamformer, COBALT, is GPU-based [8]. The planned LOFAR 2.0 fast radio burst search needs 64 GPUs and 1,024 cores with 32 GB of memory per core, and SKA and LOFAR pipelines are expected to move key algorithms to GPUs [5]. The portability actions therefore aim to decouple code from hardware. 3.3 Sustainability
The Blueprint addresses sustainability in two senses: preservation and reuse, since archives mostly serve single communities, and environmental impact, assessed over the whole life cycle (ISO 14040 and 14044) across all 16 impact categories, to avoid shifting impacts between phases or categories. For IT equipment, given its short lifetimes and an energy mix such as Europe’s, fabrication outweighs use in climate impact, so the first recommendation is to use hardware longer; efficiency gains are not counted as reductions because cheaper resources raise demand [2]. SRIDA Priority 12 builds on this and proposes environmental impact, instead of core-hours, as the unit of user credit [2, 9].
4 The Strategic Research, Innovation and Deployment Agenda 4.1 Drivers, pillars and priorities
The SRIDA starts from seven drivers: digital infrastructure scale, AI adoption, environmental sustainability, security and trust, long-term preservation, workforce capacity and digital sovereignty [9]. Its vision for 2035 is a continuum in which researchers run workflows across HPC, high throughput computing (HTC), cloud, quantum and edge resources without concern for infrastructure boundaries, authentication barriers or data locality.
Table 2. The thirteen SRIDA priorities and their key messages, condensed from D7.1, Section 4 [9]. Priority
Key message
Pillar 1: Policy, Trust and Governance P01 Cross-Infrastructure A coordination forum where WLCG, SRCNet and LOFAR ERIC align and Governance seek formal representation in pan-European digital infrastructures. P02 Federated Resource Multi-year allocation aligned with facility timelines and standard accounting, Allocation building on WLCG national commitments and EuroHPC Strategic Access. P03 Federated Identity and Trust Federated access with service accounts for unattended workflows, by making the existing AARC-compliant proxies interoperate [21]. Pillar 2: Architecture and Interoperability P04 Heterogeneous Computing Unified, API-based access to HPC, HTC, cloud, edge and quantum resources, Integration so that workflows span providers without custom integration for each one. P05 Data Management and Cross-domain FAIR data management standards and automated bulk data Transport movement, with remote access for datasets too large to move repeatedly. P06 Workflow Orchestration and Cross-facility orchestration with resilience, provenance capture and Management unattended execution of long-running workflows. Pillar 3: Software and Science Enablers P07 AI AI as first-class infrastructure across HPC, HTC, cloud and edge, with GPU and AI Factory allocations counted as pledged resources. P08 Software Portability Portable programming models and container distribution, following FAIR4RS [22] and building on EESSI. P09 Open Science and Workflows and results reproducible over five to ten years, through preserved Reproducibility computational context, metadata and provenance. P10 Software Preservation and Scientific codes that stay functional across the 20 to 50 year lifetimes of the Sustainability instruments, through preservation and modernisation. Pillar 4: Human Capital and Responsibility P11 Community Collaboration Channels for community requirements into the coordination forum, building and Co-Design on the Community of Practice and existing networks. P12 Environmental Life-cycle assessment tied to procurement and allocation rules, with Sustainability environmental impact as the unit of credit given to users. P13 Skills, Careers and Training Hybrid domain and computing skills through training and career frameworks on the Research Software Engineer model.
Table 2 lists the thirteen priorities with a key message for each. For each pillar the SRIDA also recommends actions for three groups: scientific communities and research infrastructures, e-infrastructures and service providers, and policy makers and funding bodies (D7.1, Sections 4.2.3 to 4.5.3). For access, it asks communities for multi-year resource plans, einfrastructures to allocate beyond annual cycles, and funders to enable multi-year access. 4.2 Investment areas and funding instruments
The SRIDA maps the priorities to five investment areas: computing infrastructure, data infrastructure, software and tools, governance and coordination, and human capital [9]. It also asks funders to support network capacity for exabyte-scale data movement (P05). It estimates that EU framework programmes provide about 10% of research infrastructure budgets, and it treats national and European funding as complementary: national programmes provide most HTC, cloud and storage capacity, EuroHPC concentrates on exascale and AI-optimised compute, and the task is to align the two streams (P01). The Horizon Europe work programme for 2026–2027 supports cluster and integrated-access activities in the ESFRI domain “Data, Computing and Digital Research Infrastructures”, which can pay for foundation-phase coordination, software and access but not hardware. For Framework Programme 10 (2028 to 2034, under negotiation), the SRIDA warns that the e-infrastructure federations lose the dedicated line they held under Horizon 2020. It names three costs that budgets underestimate: coordination, software maintenance and the retention of technical staff.
Figure 3. The three SRIDA roadmap phases against funding cycles and the timelines of LOFAR 2.0, the HiLumi LHC and the SKA Observatory. Adapted from the SRIDA, Figure 6.2.1 [9], under CC BY 4.0. Phases are counted from 2026, with boundaries in the shared years 3 (2028) and 5 (2030); facility dates as given in D6.1, D7.1 and by CERN [1, 2, 9], LOFAR 2.0 as of September 2026. Indicative.
4.3 Roadmap
The roadmap phases the priorities over three periods (Figure 3) under four rules: governance and trust ready before integration at scale, with piloting in parallel; infrastructure and applications scaled up together; investment in people, community and sustainability in every phase; and alignment with EU funding cycles [9]. By the end of the foundation phase (2028) a coordination forum, the AARC baseline with cross-infrastructure authentication pilots, and FAIR preservation guidelines should be in place. After the integration phase, workflows span HPC, HTC and cloud with automated data staging, under multi-year allocation agreements (D7.1, Section 6.3). The foundation phase coincides with HiLumi LHC preparation and SKA construction; the integration phase ends as Run 4 begins. The SRIDA asks for operational capabilities by then and production scale before full luminosity in the late 2030s [9].
5 Conclusion The Technical Blueprint and the SRIDA give HEP and RA one account of the compute and data continuum they need: what it must deliver, who should act, when, and with which instruments. The SRIDA’s picture is concrete: a researcher reaches reconstructed data across federated sites, runs each step on the resource best suited to it and publishes the results through shared open archives, with one identity, one allocation and one portable software stack [9]. Much of the work is coordination between research infrastructures, digital infrastructures and funders, who could organise the continuum as a commons for research [23, 24]. Many questions remain open; the two documents set them out as gaps, recommended actions and priorities, and SRIDA Section 7 covers its wider impact [2, 9]. We hope they help these actors align their plans for the continuum that HEP, RA and other data-intensive sciences need. This work is co-funded by SPECTRUM (European Union Grant Agreement Number 101131550). Views and opinions expressed are however those of the authors only and do not necessarily reflect those of the European Union. Neither the European Union nor the granting authority can be held responsible for them. The authors thank the other contributors to and reviewers of both documents, the SPECTRUM Community of Practice, the External Advisory Board, and everyone who gave feedback.
References [1] CERN, HiLumi LHC (2026), https://home.cern/science/accelerators/hilumi-lhc/
[2] SPECTRUM Project, D6.1 Technical Blueprint for Compute and Data Continuum, Zenodo (2026), https://doi.org/10.5281/zenodo.20341621 [3] ATLAS Collaboration, ATLAS Software and Computing HL-LHC Roadmap, CERNLHCC-2022-005 (2022), https://cds.cern.ch/record/2802918 [4] CMS Offline Software and Computing, CMS Phase-2 Computing Model: Update Document, CERN (2022), https://cds.cern.ch/record/2815292 [5] SPECTRUM Project, D5.1 Representative Use Cases: Analysis and Alignment, Zenodo (2025), https://doi.org/10.5281/zenodo.15310223 [6] M.P. van Haarlem et al., LOFAR: The LOw-Frequency ARray, Astron. Astrophys. 556, A2 (2013). 10.1051/0004-6361/201220873 [7] A.M.M. Scaife, Big telescope, big data: towards exascale with the Square Kilometre Array, Phil. Trans. R. Soc. A 378, 20190060 (2020). 10.1098/rsta.2019.0060 [8] SPECTRUM Project, D5.3 Landscape of Research Infrastructures: Technologies, Services, Gaps, Zenodo (2025), https://doi.org/10.5281/zenodo.15647755 [9] SPECTRUM Project, D7.1 Strategic Research, Innovation and Deployment Agenda (SRIDA), Zenodo (2026), https://doi.org/10.5281/zenodo.21820494 [10] D. Britton, S. Campana, T. Boccali, WLCG Strategy 2024–2027, WLCG Collaboration, Zenodo (2024), https://doi.org/10.5281/zenodo.12623280 [11] SPECTRUM Project, D3.1 Community of Practice: Interim Report, Zenodo (2025), https://doi.org/10.5281/zenodo.15100586 [12] SPECTRUM Project, D5.2 Interoperable Access Policies: Analysis and Recommendations, Zenodo (2025), https://doi.org/10.5281/zenodo.15647608 [13] HEP Software Foundation, A Roadmap for HEP Software and Computing R&D for the 2020s, Comput. Softw. Big Sci. 3, 7 (2019). 10.1007/s41781-018-0018-8 [14] M. Girone et al., Strategy for HPC Integration in WLCG/HEP, Zenodo (2025), https: //doi.org/10.5281/zenodo.15032799 [15] JENA Computing Initiative, JENA White Paper on European Federated Computing, 23 Mar. 2025 (2025), https://nupecc.org/jenaa/ [16] SPECTRUM Project, SPECTRUM Experts Meeting: Summary of Discussions, Zenodo, v2, 26 Mar. 2026 (2026), https://doi.org/10.5281/zenodo.19231191 [17] SPECTRUM Project, Draft Technical Blueprint and SRIDA for review, Zenodo, 11 Dec. 2025 (2025), https://doi.org/10.5281/zenodo.17901519 [18] R. Aaij et al., Allen: A High-Level Trigger on GPUs for LHCb, Comput. Softw. Big Sci. 4, 7 (2020). 10.1007/s41781-020-00039-7 [19] ALICE Collaboration, ALICE upgrades during the LHC Long Shutdown 2, JINST 19, P05062 (2024). 10.1088/1748-0221/19/05/P05062 [20] A. Bocci et al., Heterogeneous Reconstruction of Tracks and Primary Vertices With the CMS Pixel Tracker, Front. Big Data 3, 601728 (2020). 10.3389/fdata.2020.601728 [21] AARC Community, AARC Blueprint Architecture 2025 (AARC-G080) (2025), https: //aarc-community.org/guidelines/aarc-g080/ [22] M. Barker et al., Introducing the FAIR Principles for research software, Sci. Data 9, 622 (2022). 10.1038/s41597-022-01710-x [23] E. Waegemaekers et al., Organizing research as a commons, SURF report, Zenodo (2026), https://doi.org/10.5281/zenodo.21526773 [24] T. Ferrari, D. Scardaci, S. Andreozzi, The Open Science Commons for the European Research Area, in Earth Observation Open Science and Innovation (Springer), pp. 43–67 (2018), https://doi.org/10.1007/978-3-319-65633-5_3
Related documents
- SPECTRUM: A Strategic Framework and Technical Blueprint for European Exascale Research Data and Compute Infrastructure#1492101
- Emittance tuning of the FCC-ee high energy booster ring#1144181
- Design study for an energy-efficient MeV-ranged photon-beam facility#1165843
- How to verify the precision of density-functional-theory implementations via reproducible and universal workflows#1128483
- OMA-IETF Standardization Collaboration#135091
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive