ECHOES Quality and Risk Management Plan (D1.3)

ECHOES Project 101157364 – D1.3 Quality and Risk Management Plan European Cloud for Heritage Open Science D1.3 Quality and Risk Management Plan HORIZON-CL2-2023-HERITAGE-ECCCH-01 Horizon Innovation action Responsible author: Xavier RODIER (CNRS) © 2025 by the authors, the ECHOES consortium. This work is licensed under a “CC BY 4.0” license. Project start 1 June 2024 Project duration 60 months Document Identifier 10.5281/zenodo.17600734 ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 1 Deliverable Information Project Number 101157364 Acronym ECHOES Full title European Cloud for Heritage OpEn Science Project Url https://www.echoes-eccch.eu/ EU Project Officer Christian WILK Lead Partner CNRS Responsible author Xavier Rodier (CNRS) Authors Xavier Rodier, Louise Gadoin, Mailane Sampaio (CNRS) Contributors Léna Czech, Areti Damala (CNRS), Carlos Andujar (UPC), Charlotte Gallini (FSP) Deliverable D1.3 Title Quality and Risk Management Plan Work Package WP1 Title Project Management Submission date 31/01/2025 Pages 36 Keywords Quality Management, Risk Management, Mitigation, Communication Change log Date Version Author Change 13/01/2025 v0.1 Mailane Sampaio, Louise Gadoin Initial version 15/01/2025 V0.2 Xavier Rodier, Areti Damala Revisions 16/01/2025 V0.3 Mailane Sampaio, Louise Gadoin Revisions 17/01/2025 V0.4 Léna Czech Grammar and editing 17/01/2025 V0.5 Louise Gadoin Final version 24/01/2025 V0.6 Carlos Andujar Revisions 24/01/2025 V0.7 Charlotte Gallini Grammar and editing 28/01/2025 V1 Xavier Rodier Proofreading ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 2 Disclaimer: Views and opinions expressed are however those of the author(s) only and do not necessarily reflect those of the European Union or the European Research Executive Agency. Neither the European Union nor the granting authority can be held responsible for them. ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 3 Executive Summary The QRMP establishes a robust framework for ensuring high-quality project outcomes and proactive risk management. Key components include: 1. Quality Management Strategy: • Defined roles and responsibilities within the consortium, • Quality control measures such as regular progress reporting, milestone tracking, and stakeholder engagement, • KPIs to monitor achievements across work packages and deliverables. 2. Risk Management Strategy • Identification of potential risks (scientific, technical, financial, and operational) and mitigation plans, • Regular risk monitoring and reporting mechanisms, with escalations to governance bodies when necessary, • Clear assignment of risk ownership to specific roles within the project. ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 4 Table of Contents List of tables ....................................................................................................................... 5 List of abbreviations ......................................................................................................... 6 Introduction ....................................................................................................................... 7 1. Quality Management Strategy .................................................................................... 9 1.1 Quality Procedures ........................................................................................................... 9 1.1.1 Roles and Responsibilities .......................................................................................... 10 1.1.2 Quality Control Procedures ........................................................................................ 19 1.2 Internal communication plan ....................................................................................... 21 1.3 Key Performance Indicators (KPIs) ............................................................................... 24 2. Risk Management Strategy ........................................................................................ 28 2.1 Risk Identification and Mitigation Plan ........................................................................ 28 2.2 Risk Monitoring and Reporting ..................................................................................... 33 2.3 Risk Owner Assignment ................................................................................................. 34 Conclusion ........................................................................................................................ 35 ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 5 List of tables Table 1: Roles and responsibilities Table 2: Deliverable timeline Table 3: ECHOES mailing list Table 4: KPIs description and targets Table 5: Risk identification and mitigation plan Table 6: Risk owner and their responsibilities ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 6 List of abbreviations Abb. DMP Data Management Plan EITF ECHOES Integration Task Force ECCCH European Collaborative Cloud for Cultural Heritage EB Executive Board GA General Assembly GDPR General Data Protection Regulation HDT Heritage Digital Twin PAB Policy Advisory Board QRMP Quality and Risk Management Plan ScS Scientific Committee SEP Single Entry Point SOs Specific objectives StaC Stakeholders Council SC Steering Committee TAC Technical Assessment Committee VAs Vertical Applications WP Work Packages ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 7 Introduction This document serves as the Quality and Risk Management Plan (QRMP) for the ECHOES project, formally titled European Cloud for Heritage OpEn Science. The QRMP outlines the strategies, processes, and tools that will guide the consortium in delivering highquality outputs while effectively identifying, assessing, and mitigating risks throughout the project lifecycle. It ensures alignment with Horizon Europe standards, including compliance with ethical guidelines, data management protocols, and Open Science principles. The scope of this document encompasses all activities, deliverables, and objectives described in Annex 1 of the Grant Agreement, particularly those contributing to the development of the European Collaborative Cloud for Cultural Heritage (ECCCH). As an interdisciplinary initiative, ECHOES bridges the fields of cultural heritage, digital humanities, and advanced computational science to empower stakeholders with stateof-the-art tools and resources. ECHOES aims to establish the ECCCH as a transformative platform that enables heritage professionals and researchers to access data, collaborate on analyses, and co-create knowledge. This digital environment will integrate advanced technologies such as Digital Twins and Artificial Intelligence, fostering new insights into both tangible and intangible cultural heritage. The project adopts a holistic and inclusive approach, promoting Open Science, Open Access, and Open Source principles to ensure democratized access to knowledge and tools. The ultimate vision is to deliver “the heritage of tomorrow,” semantically rich and collaboratively produced, by the end of the project in Month 60. Key goals of the project include: 1. The design and implementation of the ECCCH platform. 2. The integration of fragmented communities in cultural heritage around Digital Commons. 3. The delivery of a sustainable governance model for the ECCCH platform, anchored in inclusivity and transparency. The consortium includes 26 beneficiaries, 16 affiliated entities and 9 associated partner entities across Europe, led by the Centre National de la Recherche Scientifique (CNRS) as the coordinator. With a budget of €23,970,598, ECHOES is structured into clearly defined Work Packages (WPs), each with measurable milestones and deliverables. ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 8 This QRMP is organized into two sections: 1. Quality Management Strategy 1.1 Quality Procedures a. Roles and responsibilities b. Quality control measures c. Communication plan d. Document control and archiving 1.2 KPIs 2. Risk Management Strategy 2.1 Risk Identification and Mitigation Plan 2.2 Risk Monitoring and Reporting 2.3 Risk Owner Assignment By adhering to this framework, the project ensures that all outputs are delivered on time and at the highest quality, in compliance with the Grant Agreement and Horizon Europe guidelines. This plan is intended as a living document, subject to updates based on project progress, stakeholder feedback, and emerging challenges. By adhering to the QRMP, the ECHOES consortium commits to delivering on its objectives with excellence, transparency, and accountability, ensuring the success and long-term impact of the project. ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 15 WP5 (Europeana) - Julia FALLON/Ad POLLE WP6 (PSNC) - Aleksandra NOWAK WP7 (CYI) - Sorin HERMON WP8 (CNR) - Paolo CIGNONI WP9 (UPC) - Carlos ANDUJAR Representatives of the Virtual Applications VA1: Collaborative ConservationRestoration Platform (Lead: CNR): Marco CALLIERI VA2: Virtual Transcription Laboratory (Lead: DARIAH): Anne BAILLOT VA3: Collection Ingestion Tool (Lead: ETT-META): Sam MINELLI Representatives from current and future ECCCH-funded projects AUTOMATA (Holly WRIGHT University of York) TEXTaiLES (George IOANNAKIS, Athena Research Center) ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 16 HERITALISE (Mikel BORRAS, IDP Ingerieria y Arquitectura Iberia SL) Independent and External Board of the consortium Policy Advisory Board (PAB) Ensures coherence at the policy level between all ECCCH-related activities; Provides recommendations on strategic decisions related to governance and sustainability of the Cloud within its ecosystem. Manuel CASTIÑEIRAS GONZALEZ (ES) Chris DE LOOF (BE) David DE ROURE (UK) David FIALA (FR) Pascal LIEVAUX (FR) Paul KELLER (NE) Marina SOLOMIDOUIERONYMIDOU (CY) Eva STENSKÖLD (SE) Elena THEODOULOUCHARALAMBOUS (CY) Brigitte VEZINA (NE) Ben WAGNER (NE) Katarzyna WALETKO (PL) Scientific Committee (ScS) Provide expert advice not only on activities carried out within ECHOES but also on activities performed in other ECCCH-funded projects once they are integrated into the horizontal infrastructure. Pere BRUNET (ES) Livio DE LUCA (FR) ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 17 Paola DERUDAS (SE) Diane DUSSEAUX (FR) Eero HYVÖNEN (FI) Adeline JOFFRES (FR) Peter PLASSMEYER (DE) Martjn PRONK (NE) Antonino ROTOLO (NE) Roberto SCOPIGNO (IT) Matija STRLIC (SI) Melissa TERRAS (UK) Jean François TRUBERT (FR) Technical Assessment Committee (TAC) It will assess the Cloud’s structure and the evolving components, tools and services. Once established, it will be linked to the legal entity. Provides expert advice on the technical activities carried out within ECHOES. It is currently composed of 8 experts from the computer sciences domain and from different sectors of CH. CANDELO Gustavo (ES) GUELTON Rémi (FR) JONES Bob (CH) LESJAK Dejan (SI) LEVERS Andrew (UK) ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 18 NEGRI Antonella (IT) SZPROT Jakub (PO) VAN WEZEL Jos (DE) Stakeholders Council (StaC) It will bring together other ECCCH-funded projects and Representatives from European initiatives related to CH. Advises the General Assembly. Final list expected by Autumn 2025: Gabriele GATTIGLIA (AUTOMATA); Georgios IOANNAKIS (TEXTaiLES); Mikel BORRAS (HERITALISE); Future representatives of ECCCHfunded projects; Representatives from other European initiatives related to CH. Table 1: Roles and responsibilities ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 19 1.1.2 Quality Control Procedures Quarterly Reports by WP Leaders WP leaders must submit detailed progress reports every three months, including the planned progress and the actual progress in the mentioned period. If there is a reason for difference or major risks and problems encountered, they must declare it. In addition, the WP leader must present the planned activities for the following three months. Quarterly Reports by Beneficiaries Beneficiaries must submit progress reports every three months, including updates about their activities and the work of their Affiliated Entities. They must highlight the contributions made in each Work Package they are involved in and include the quantity of Person-Months engaged during the period. Quarterly meetings by the Steering Committee The Work Package leaders, the Pillar Coordinators and the Chair of the Executive Board shall supervise the progress of the project and propose further actions. The purpose of the meeting is to discuss the most relevant topics such as monitoring compliance with milestones and deliverables, the progress of tasks and sub-tasks by WP, and internal and external events. Monthly follow-up by the Executive Board The Executive Board, composed of the coordinating institution and the two co-leading institutions, meets once a month to review the project’s progress in line with the strategic directions defined by the EB. Annual Meetings One general meeting per year of the project will be held with all the partners to review project progress, address cross-WP challenges, and ensure alignment across teams. These meetings will include presentations of WPs’ progress, updates on risks, and feedback from stakeholders. Additionally, the meetings of the Policy Advisory Board, the Scientific Committee, the Technical Assessment Committee and the Stakeholders Council will be convened in the same place and location, after this meeting. The goal is that the members of the independent boards can follow the on-site discussions and be updated on ECHOES’s latest achievements and activities carried out during the next year. The location of the annual meeting will rotate geographically to encourage the participation of stakeholders from different parts of the EU and the engagement with local heritage institutions and policymakers during the public event. ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 20 General Assembly With a representative of each partner, including affiliated entities and associated partners, the role of the General Assembly is to set out decisions to ensure that the activities carried out are compatible with the project described. Except for the first General Assembly that will be held online, all future General Assemblies will be organized jointly with the Annual meetings. Decisive matters may be presented by email as well, according to Section 6.3.1.3 of the Consortium Agreement. The goal is to have an agile procedure while securing the right of every partner to vote and have a voice. Periodic Reports to the European Commission Technical and financial reports must be submitted by the Coordinator at the end of each reporting period, as required by Article 21 of the Grant Agreement: • RP1 (Months 1–24): Due 60 days after Month 24. • RP2 (Months 25–48): Due 60 days after Month 48. • RP3 (Months 49–60): Final report due 60 days after project completion. Deliverables The internal review process for deliverables will involve a two-tier validation system: one at the WP level and another at the coordinator level. On the WP level, the WP leader oversees the development of the Deliverable under a task or sub-task. The lead beneficiary of the Deliverable is identified on the list of Deliverables available on page 45 of the Grant Agreement. The WP leader must appoint the lead author(s) of the Deliverable and inform the Coordinator up to one month before the deadline. The Pillar Coordinators conduct the internal review process and must assign one or more collaborators for proofreading. The project manager will send a reminder to the lead author and the WP leader one month before the deliverable submission. The process for finalizing the deliverable is as follows: • Four weeks before the deadline: the lead author has one week to complete the final draft of the Deliverable and share with the Coordinator, Pillar Coordinators and Project Manager. • Three weeks before the deadline: one-week period dedicated to the internal review of the deliverable. • Two weeks before the deadline: The lead authors must implement the contributions from the reviewers to the final text. • One week before the deadline: final editing will be done. • On the last day: the deliverable will be uploaded to the platform. ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 21 Table 2: Deliverable timeline All deliverables listed in the Grant Agreement must undergo internal review before being submitted to the granting authority via the EU Funding and Tenders Portal. In case of possible delay of Deliverable, the lead author shall inform the Coordinator by email with a detailed explanation of the reason and the estimated future date. This should be done at least before the start day of the internal process review, four weeks before the deadline. The Coordinator will contact the Project Officer to notify the delay. 1.2 Internal communication plan Effective communication is crucial for the success of the ECHOES project, ensuring seamless coordination among all partners and work packages. This communication plan outlines the primary tools and channels used for communication within the project, including the ECHOES Teams group and various mailing lists. The plan details the procedures for accessing these platforms, managing communications, and ensuring that all relevant information is shared efficiently. Furthermore, it addresses the rhythm of communication, the responsibilities of various team members, and the proper documentation and storage of project materials. By adhering to these guidelines, the project team will foster transparent and organized communication, supporting the overall goals of ECHOES. The main channels for general communication are the ECHOES group on Teams and the mailing lists. To first access the ECHOES Teams group, the Project Manager needs to add the new participant’s email on the platform. Once the email is registered, the person will receive a link to enter the group. Due to the internal authorization settings of the institution hosting the ECHOES group in Teams, some Responsible Lead author(s) Reviewer(s) Lead author(s) Coordinator and author Coordinator Production timeline Four weeks before Three weeks before Two weeks before One week before Deadline Task Final draft provided Internal review Implementation of requested changes Revision/Final editing (CO) Upload Final version submitted by the lead author Check the consistency with the project plans and give feedback and/or approval. Check the consistency with the project plans and give feedback and/or approval. Final formatting and language check Upload on the Funders & Tenders Portal ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 22 institutional emails do not have standard access. In this case, an alternative email address is required to obtain access to the group, its channels and documents. The ECHOES Teams group is divided into 12 channels: one general channel and 11 Work Packages channels. The general channel is the main communication channel of the Coordination Team. The folders contain the agenda and presentation from ECHOES events; official documents such as the Grant Agreement and the Consortium Agreement; reports including the final version of Deliverables and Milestones, the list and calendar of Deliverables and Milestones, and the internal progress reports from WP leaders and partners; and document related to internal consultations. The WP channels are the main communication channel of the WP Leaders. The draft version of Deliverables, the minutes, agenda and attendees list of all the meetings and extra documents related to the work developed on tasks and sub-tasks are available in the folders. Messages posted via Teams must also be shared on the corresponding mailing list. The following table contains all ECHOES mailing lists. Name Address General ECHOES list All the members [email protected] General Assembly Representatives of partners echoes_general_assem[email protected]nater.fr Steering Committee [email protected] Executive Board [email protected] WP 02 [email protected] WP 03 [email protected] WP 04 [email protected] WP 05 [email protected] WP 06 [email protected] WP 07 [email protected] WP 08 [email protected] WP 09 [email protected] WP 10 [email protected] WP 11 [email protected] Scientific Committee [email protected] Policy Advisory Board [email protected] Technical Assessment Committee [email protected] Stakeholders Council [email protected] ECHOES Diffusion Institutions interested in the project [email protected] ECHOES integration Task Force [email protected] Table 3: ECHOES’ mailing list ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 23 All the lists are managed by the Coordination Team on the platform Renater. In addition, the WP leaders have access and rights to manage their lists on Renater by adding or removing contact addresses and to moderate messages sent by members. A contact master list is available on Teams in the “General” channel folder, and it is accessible to all partners. It is divided into contact lists by WP. Partners are required to add or modify information about their team. The lists on Renater are synchronized by the coordination team and the WP leaders in accordance with this master list. Rhythm of communication The Project Manager will send reminders to the responsible for a Deliverable and Milestone one month and 15 days before the deadline. For the internal progress reports, the same deadline is established. The reminders will be sent to the Work Package leaders and the designated representatives of Beneficiaries (list available in Annex 6 of the Consortium Agreement). It is the Coordination Team’s responsibility to communicate to all partners when a Deliverable is uploaded on the EU Fundings & Tenders Portal or if it is delayed. Communication with the European Commission is an exclusive responsibility of the Coordinator. Document Control and Archiving Gathering documents in one place with a clear allocation and denomination will facilitate democratic access for all members of this consortium. All the working and final documents will be available on the ECHOES Teams group and stored in the consortium’s shared repository, the SharePoint, which is accessible through Teams. This ensures traceability and compliance with Horizon Europe documentation standards. If an alternative platform is being used for the work in progress, the WP leader must register in the Teams group which platform it is and for which task and sub-task it is being used. The documents should be in English, shared in Word format when it is a draft version and in PDF as a final version. The WP 2 channel - in the folder “Communication material” - has relevant template documents: Deliverables, presentations, agenda, minutes and list of attendees. The templates for the Internal progress report are available on Teams > General > Reporting > Internal Progress report folder. For the Beneficiaries, one standard template is available; and for the WP leaders were provided individual templates each trimester. All documents uploaded onto the shared space must follow the following naming convention: • YYMMDD_ECHOES_title_of_the_document; • YYMMDD_ECHOES_WPXX_title_of_the_document; • YYMMDD_ECHOES_[BOARD_ACRONYM]_Title_of_the_document Working documents and draft versions are excluded from this naming convention. ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 24 Additionally, all the final documents are being stored in the University of Tours server by the Coordination Team. 1.3 Key Performance Indicators (KPIs) Progress Indicators at WP-Level will be monitored using predefined Key Performance Indicators (KPIs) specified in Annex 1 of the Grant Agreement. These KPIs will track the progress of deliverables and milestones for each WP. This table outlines the Key Performance Indicators (KPIs) associated with the specific objectives (SOs) of the project. Each KPI is designed to measure the progress and success of key deliverables under the corresponding objectives, with defined targets for completion. These indicators will help track the project's achievements and ensure that all milestones are met within the designated timeframes. Additional KPIs for the ECCCH will be established by WP3, WP4, WP6, WP7, WP8, WP9, and WP11 under the responsibility of CYU. They are expected by Month 20 (January 2026). ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 31 c. Schedule iterative testing phases (by Months 18, 30, and 48) to refine tools based on community feedback. 12 Data loss/corruption (due to equipment failure, procedural failure, etc.), data privacy Loss or corruption of critical data could undermine project progress and stakeholder trust, while data privacy breaches may violate EU standards. a. Implement robust data management protocols aligned with Horizon Europe’s requirements for data protection (Article 15). b. Perform regular backups with off-site storage to minimize data loss risks. c. Conduct security audits quarterly to identify and address vulnerabilities. 13 Innovation: Delays in the VAs deployment Delays in Virtual Agents (VAs) deployment may hinder the project’s ability to meet its milestones and deliverables. a. Set a clear timeline for VAs development with intermediate checkpoints (by Months 12, 24, and 36). b. Allocate dedicated resources and teams to focus on VAs deployment. c. Include a risk buffer in the timeline to accommodate unforeseen challenges. 14 Tools created do not function as planned or do not satisfy requirements The tools developed may fail to meet performance or usability expectations, reducing their effectiveness. a. Define clear success metrics for each tool during the design phase and validate them through regular testing. b. Engage users in the co-creation process to ensure tools align with practical needs. c. Allocate resources for bug fixes and performance optimization during the final project phase (Months 48-60). 15 The cloud services fail to achieve expected results The ECCCH cloud services may not provide the expected functionalities or scale required by the community. a. Collaborate with experienced cloud infrastructure providers to ensure scalability and reliability. b. Include stress testing and performance optimization as part of WP6 deliverables (by Month 30). c. Monitor cloud services using real-time analytics to identify and address issues promptly. ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 32 16 Sustainability: The stakeholder’s engagement in the governance-building process is low or unstable Limited or inconsistent engagement from stakeholders could compromise the establishment of a sustainable governance model for ECCCH. a. Create a targeted communication plan to engage stakeholders early and maintain their interest throughout the project. b. Organize biannual stakeholder forums to gather input and keep stakeholders informed of progress. c. Leverage the project’s advisory board to champion the governance-building process and advocate for its importance. 17 Feasibility of the business plan after the end of the project The business plan for ECCCH may lack sufficient feasibility or funding pathways, jeopardizing sustainability post-project. a. Conduct a feasibility study by Month 48 to assess potential funding sources and revenue streams. b. Include private and public stakeholders in the development of the business plan to ensure alignment with their priorities. c. Explore partnerships with external organizations to secure longterm financial support. Table 5: Risk identification and mitigation plan ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 33 2.2 Risk Monitoring and Reporting In order to ensure that risks are continuously monitored and addressed, the ECHOES consortium will implement a structured process for tracking, evaluating, and mitigating risks throughout the project lifecycle. Regarding reporting mechanisms, WP leaders will submit quarterly risk updates to the project manager, including any new risks, updates on mitigation actions, and issues requiring consortiumlevel intervention. A summary of risk management activities will be included in the periodic technical and financial reports submitted to the European Commission, following Article 21 of the Grant Agreement. As part of the escalation protocol, high-impact risks requiring immediate action will be escalated to the project Steering Committee (SC) for strategic decision-making. The SC will provide guidance on resource reallocation, timeline adjustments and other corrective actions. By combining regular updates and real-time monitoring, the ECHOES consortium ensures a proactive approach to risk management and minimizing its impact on the project’s objectives. ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 34 2.3 Risk Owner Assignment To ensure accountability in risk management, each identified risk will be assigned a specific risk owner responsible for its monitoring, mitigation, and reporting. No Role Description 1 WP Leaders as Primary Risk Owners Each WP leader will serve as the primary risk owner for risks specific to their work package. They will oversee the identification and mitigation of risks within their scope and provide regular updates to the project manager. 2 Project Manager The project manager will act as the central risk coordinator, consolidating updates from WP leaders, maintaining the risk register, and ensuring that mitigation measures are implemented across the consortium. For consortium-wide risks, such as delays in deliverables or stakeholder engagement issues, the project manager will collaborate with the scientific coordinator and escalate as needed to the PSC. 3 Scientific Coordinator The scientific coordinator will be responsible for overseeing high-level scientific risks, such as unsatisfactory results from the Knowledge Base or delays in the definition of the HDT model. 4 Specialized Risk Ownership Data Privacy and Security Risks (e.g., data loss or corruption): Assigned to the WP6 leader, who will work with external IT consultants to ensure compliance with EU data protection standards (Article 15 of the Grant Agreement). Sustainability Risks (e.g., stakeholder engagement and business plan feasibility): Assigned to the WP7 leader, responsible for governance-building and post-project sustainability. 5 ConsortiumLevel Support For cross-cutting risks, such as those related to collaboration across WPs or with external stakeholders, the Project Steering Committee will provide oversight and guidance to ensure alignment and effective resolution. Table 6: Risk owner and their responsibilities ECHOES Project 101157364 - D1.3 Quality and Risk Management Plan 35 By clearly assigning responsibilities, the consortium ensures that risks are managed efficiently and transparently, with all partners contributing to the project’s overall success. Conclusion The ECHOES Quality and Risk Management Plan (QRMP) establishes a comprehensive framework to ensure the successful delivery of the project’s objectives while maintaining the highest standards of quality and effectively managing potential risks. By defining clear processes for quality assurance, risk identification, and mitigation, this document serves as a roadmap for ensuring the project’s compliance with Horizon Europe requirements and the expectations of its diverse stakeholders. The QRMP is designed to be a living document, evolving alongside the project to adapt to new challenges and opportunities. Regular monitoring and evaluation will ensure that all work packages, deliverables, and milestones are achieved within the defined scope, timeframes, and budget. Key tools, such as progress indicators, reporting mechanisms, and iterative reviews, will support the project consortium in maintaining transparency, accountability, and a collaborative spirit throughout the project lifecycle. Moreover, the strong emphasis on stakeholder engagement, sustainability, and inclusivity reflects the project’s commitment to creating a long-lasting impact on the cultural heritage community. The consortium will continue to foster collaboration, leverage innovative technologies, and uphold ethical standards to deliver the European Collaborative Cloud for Cultural Heritage (ECCCH) as a transformative platform that aligns with the principles of Open Science and Open Access. Through diligent adherence to the strategies outlined in this QRMP, the ECHOES consortium reaffirms its dedication to achieving excellence and ensuring the project’s success for the benefit of heritage professionals, researchers, and society at large.