| Dokumendiregister | Justiits- ja Digiministeerium |
| Viit | 7-12/8238 |
| Registreeritud | 12.11.2026 |
| Sünkroonitud | 13.11.2026 |
| Liik | Sissetulev kiri |
| Funktsioon | 7 EL otsustusprotsessis osalemine ja rahvusvaheline koostöö |
| Sari | 7-12 Euroopa Komisjoni programmid (Arhiiviväärtuslik) |
| Toimik | 7-12/26-10 |
| Juurdepääsupiirang | Avalik |
| Adressaat | Agencia Digital de Andalucía (ADA) |
| Saabumis/saatmisviis | Agencia Digital de Andalucía (ADA) |
| Vastutaja | Kadri Kungla (Justiits- ja Digiministeerium, Kantsleri vastutusvaldkond, Digiriigi valdkond, Digiriigi osakond, AI ja andmete talitus) |
| Originaal | Ava uues aknas |
| Taotle dokumendi eemaldamist või parandamist |
From: Keaty Siivelt - JUSTDIGI
Sent: Wednesday, October 14, 2026 4:49 PM
To: Kadri Kungla - JUSTDIGI <[email protected]>
Subject: FW: Estonia/JDM implementation clarifications before accession
From: Eunomia Ada <[email protected]>
Sent: Wednesday, October 14, 2026 10:20 AM
To: Keaty Siivelt - JUSTDIGI <[email protected]>; Kaarel Sepp - JUSTDIGI <[email protected]>
Subject: Re: Estonia/JDM implementation clarifications before accession
|
Tähelepanu!
Tegemist on välisvõrgust saabunud kirjaga. |
Dear Keaty, dear Kaarel,
We hope you are both well.
Following Jaanus' handover, we would like to kindly follow up on a few pending items on the JDM side:
We would appreciate any update you could provide on these points and remain at your disposal should you need any clarification or support.
Thank you very much for your collaboration.
Kind regards,
--
Project Office | Agencia Digital de Andalucía (ADA) — ES
EUNOMIA.AI | WP1 Lead - Project Management and Coordination
Subdirección de Servicios Digitales y Analítica de Datos
Agencia Digital de Andalucía
Granada
Centro de Inteligencia Artificial de Andalucía (ANIA)
Av. del Conocimiento, 33, 18016 Granada
www.juntadeandalucia.es
El 2026-09-30 09:38, Eunomia Ada escribió:
Dear Jaanus,
Thank you for your message and for your contribution to EUNOMIA throughout your involvement in the project. It has been a pleasure working with you, and we wish you all the best in your future endeavours.
We wish you all the best in your next professional chapter and hope our paths will cross again in the European public sector AI ecosystem.
In the meantime, and to help ensure a smooth transition on the JDM side, it would be very helpful if you could support the handover of the following items:
- Updating the JDM entries in the project contact list available at this link, so that we have the latest contact details and points of contact.
- Signing the Accession Form to the Consortium Agreement when possible, as requested in our communications over the past weeks.
- Keeping us informed regarding JDM's intentions concerning the potential involvement of RIA in support activities for JDM within the project.
Thank you again for your collaboration and support. Please do not hesitate to reach out if there is anything we can do from the coordination side during this transition.
Kind regards,
--
Project Office | Agencia Digital de Andalucía (ADA) — ES
EUNOMIA.AI | WP1 Lead - Project Management and Coordination
Subdirección de Servicios Digitales y Analítica de Datos
Agencia Digital de Andalucía
GranadaCentro de Inteligencia Artificial de Andalucía (ANIA)
Av. del Conocimiento, 33, 18016 Granada
www.juntadeandalucia.esEl 2026-09-29 18:49, Jaanus Vänt - JUSTDIGI escribió:
Dear Rafael, Ivan and EUNOMIA colleagues,
I wanted to let you know directly that my final working day at the Estonian Ministry of Justice and Digital Affairs will be 30 September.
I have been involved with EUNOMIA since the project was being developed last year, initially helping shape Estonia's participation and use-case direction, and later carrying that work through proposal development, Grant Agreement preparation, accession and now the implementation phase.
During that time I have coordinated much of JDM's practical EUNOMIA work on the Estonian side, including our beneficiary obligations, the connection between the WP5 use-case work and WP2 technical requirements, the possible RIA contribution route, and the governance, legal and infrastructure questions behind implementation.
We also completed the WP2 kick-off on 28 September. One useful outcome from that discussion was the need to connect the technical work much more tightly to the actual WP5 use cases, including the data, interfaces, deployment constraints and validation requirements. I think that is particularly relevant for Estonia, because much of our value in the project sits exactly at that boundary between real public-sector requirements and technical implementation.
I am now completing the internal handover so that the decisions, source material and open questions remain with JDM. Going forward, Keaty Siivelt will be the main JDM continuity contact and the best route for Estonia-side coordination.
There are still several Estonia-side decisions that JDM will need to close internally, particularly the accountable project and WP5 ownership, staffing of the agreed effort, co-financing, and the exact Estonian pilot / RIA delivery model. Those should then feed back into the WP2 and WP5 work before the next project milestones.
I have appreciated working with the EUNOMIA team. I also intend to remain close to Estonian and European public-sector AI, governance and implementation work, so I hope this is a change of role rather than the end of the relationship.
If there is anything you would like me to close or clarify before EOB tomorrow Sept 30, please let me know and I will make sure it is covered in the handover.
Best regards,
Jaanus
Jaanus Vänt
AI and Data Strategy Coordinator
AI and Data Unit (AIAT)
Ministry of Justice and Digital AffairsRepublic of Estonia
[email protected]
www.justdigi.ee | Suur-Ameerika 1, Tallinn
From: RAFAEL MATA SANCHEZ <[email protected]>
Sent: Friday, June 26, 2026 21:26
To: Jaanus Vänt - JUSTDIGI <[email protected]>
Cc: IVAN BAILON BALLESTEROS <[email protected]>; Eunomia <[email protected]>
Subject: RV: Estonia/JDM implementation clarifications before accession
Tähelepanu! Tegemist on välisvõrgust saabunud kirjaga.
Tundmatu saatja korral palume linke ja faile mitte avada.Dear Jaanus,
Many thanks for your message and for the constructive discussion. We fully understand the need to provide your management with a clear distinction between what is already fixed through the Grant Agreement and Annexes, what will be further detailed in the Consortium Agreement, and what is intentionally expected to be refined during project implementation, especially in WP5.
Please find below our preliminary clarification from the coordinator's perspective. We can of course complement this with a focused discussion involving the PMO (in cc) and the WP5 lead, if useful.
At Grant Agreement level, Estonia/JDM is included as a beneficiary of EUNOMIA.AI and participates in several work packages, with a particularly relevant role in WP5 – UC Piloting. The WP5 lead is KISC, while ADA remains responsible for overall project coordination. JDM's role should therefore be understood as a pilot/use-case partner with strong domain, legal, governance and public-sector expertise, rather than as the main technical developer or infrastructure operator.
In practical terms, we would expect JDM's contribution to WP5 to include the definition, prioritisation and validation of a relevant public-sector use case in the judicial/regulatory domain; contribution to requirements and feasibility analysis; support to data-governance, legal and organisational assessment; engagement with relevant users and stakeholders; participation in pilot design, validation and evaluation; and contribution to lessons learned and replication outputs. The exact operational configuration of the Estonian pilot is not expected to be fully finalised before project kick-off. It is precisely one of the purposes of the first WP5 activities to refine the use cases, assess feasibility, define requirements, clarify data and deployment conditions, and agree the most appropriate implementation path.
On the flexibility of the pilot, our understanding is that JDM can narrow, refine or adjust its pilot during the first months of WP5 if detailed planning shows that the initial idea is legally difficult, technically unsuitable, resource-constrained or no longer fully aligned with national priorities. This flexibility must remain within the overall scope and objectives of the project, the Grant Agreement and the Description of the Action. If an adjustment remains consistent with the existing work plan and does not imply a substantive change to the action, it would normally be assessed and handled through project governance and WP5 planning. If a more substantial change were ever required, it would need to be assessed through the appropriate project governance and, where necessary, the formal procedures foreseen under the Grant Agreement.
Regarding implementation ownership, JDM should not understand its role as having to develop or operate the core technical components alone. WP2 is responsible for development, integration and standardisation, WP3 for AI safety and compliance, WP4 for infrastructure and procurement, and WP5 for piloting under KISC's leadership. JDM's primary role is expected to focus on public-sector ownership of the Estonian use case: defining the problem, validating requirements, ensuring national legal and organisational fit, engaging the relevant users, supporting pilot execution and evaluating results. Technical implementation should be supported through the relevant technical partners and work packages, with JDM contributing domain knowledge and ensuring that the solution is meaningful and usable in the Estonian public-sector context.
On the data model, there is no single fixed approach imposed on Estonia before kick-off. The appropriate data model should be determined during WP5 planning, in coordination with WP2 and WP3, based on legal feasibility, data availability, sensitivity, security requirements and pilot objectives. Depending on the use case, this may involve real public-sector data, anonymised or pseudonymised data, synthetic data, open/non-sensitive datasets, or a phased approach starting with lower-risk data before moving to more operationally relevant validation. The project documentation already recognises the need to address data protection, governance and security from the outset.
Similarly, the deployment approach is not intended to be fixed at this stage for each individual pilot. The project includes a central GenAI infrastructure, but also foresees the possibility of federated or local deployment where national constraints, data sensitivity or practical feasibility make this more appropriate. The specific deployment model for Estonia should therefore be agreed during WP5/WP4 planning, taking into account legal, technical and security requirements.
Regarding the EUR 100,000 subcontracting allocation for JDM, the current description links it to specialised expertise for the legal and technical validation of judicial and regulatory use cases under WP5. This includes domain-specific compliance checks and alignment with national and EU frameworks. The detailed scope should be defined by JDM, in coordination with the WP5 lead, WP3 where relevant, and the PMO, so that it is consistent with the Grant Agreement, Annex 1 and Annex 2. JDM retains responsibility for its own procurement and supplier selection, in accordance with its applicable national and internal procurement rules, while ensuring best value for money, transparency, absence of conflict of interest, and proper documentation. The subcontracting allocation should therefore be seen as an enabling resource for JDM's WP5 contribution, not as a pre-selected supplier or a fully pre-defined contract.
As regards first-phase implementation expectations, the main early priorities for partners will be to confirm operational contacts, ensure internal availability of the staff foreseen for the project, participate in the kick-off and WP-level planning, contribute to the first requirements and use-case selection activities, and identify any procurement or subcontracting processes that may require early preparation. For JDM, this would mainly mean confirming the operational team, preparing for WP5 use-case planning, and starting internal reflection on the scope and timing of the subcontracting support, without launching anything that would be inconsistent with national rules or the final project governance arrangements.
The Consortium Agreement is expected to cover practical internal arrangements between beneficiaries that complement, but do not contradict, the Grant Agreement. This typically includes internal governance, decision-making, escalation, access rights, background and results, confidentiality, liability between beneficiaries, internal financial arrangements, and practical procedures for managing changes or disputes. Matters such as operational WP coordination, internal escalation if a pilot needs to be adjusted, data-sharing arrangements between partners, and additional internal rules on IP/confidentiality are therefore expected to be addressed or further detailed through the Consortium Agreement and project governance.
To summarise the distinction:
Matters already fixed include JDM's status as beneficiary once the accession form is signed, the overall project objectives, JDM's allocated budget and person-months, the existence of JDM's WP5 subcontracting allocation, the WP structure, the formal WP5 lead, and the general deliverables and milestones.
Matters expected to be clarified in the Consortium Agreement include internal decision-making, escalation mechanisms, practical governance between beneficiaries, confidentiality arrangements, internal liability, access rights, background/results management, and complementary operational procedures. (Regarding documentation, we would suggest using the Grant Agreement and its Annexes as the formal reference at this stage. The Consortium Agreement is currently under internal legal and financial review on our side and will be circulated to the consortium once a stable version is available for partner review. Therefore, the clarifications below should be read as a coordinator-level explanation of the current Grant Agreement package and expected implementation approach, not as a replacement for the future Consortium Agreement.)
Matters intentionally left for WP5 planning include the detailed Estonian pilot configuration, final use-case requirements, precise data model, deployment approach, user validation process, detailed implementation responsibilities, KPIs at pilot level, and the detailed scope of JDM's subcontracting support.
I hope this helps your executive recommendation. From the coordinator's perspective, the important point is that accession confirms JDM's commitment to participate in the project under the Grant Agreement, while the normal and necessary operational refinement of the Estonian pilot will take place during WP5 planning, in coordination with KISC, ADA/PMO and the relevant technical and compliance partners.
This clarification is provided from the coordinator's perspective to support internal alignment and does not modify, extend or replace the Grant Agreement, its Annexes, or any future provisions of the Consortium Agreement. In case of any discrepancy, the Grant Agreement and its Annexes remain the legally binding reference.
We would be happy to organise a focused follow-up call with ADA/PMO and KISC to go through these points and ensure that the Estonian implementation path is clear and realistic from the beginning.
Best regards,
EUNOMIA.AI | WP1 Lead - Project Management and Coordination
Rafael Mata Sánchez
Head of the Innovative Digital Transformation Service
Coordinator of the Andalusian Artificial Intelligence Center (ANIA)
Deputy Directorate of Digital Services and Data Analytics
Inteligencia Artificial - Agencia Digital de Andalucía - Junta de Andalucía
Avda. del Conocimiento, 33. 18016 - Granada, España.
M: +34 608 86 24 84 (corp. 662034)
[email protected] | www.juntadeandalucia.es
Think in green, do not print.
CONFIDENTIALITY NOTICEThis message (including any attachments) contains information that may be confidential. Unless you are the intended recipient (or authorized to receive for the intended recipient), you may not read, print, retain, use, copy, distribute or disclose to anyone the message or any information contained in the message. If you have received the message in error, please destroy all copies of the original message (including any attachments).
De: Jaanus Vänt - JUSTDIGI <[email protected]>
Enviado: Viernes, 26 de Junio de 2026 14:52
Para: RAFAEL MATA SANCHEZ <[email protected]>
Asunto: Estonia/JDM implementation clarifications before accession
Este es un correo externo, por favor verifique la identidad del remitente y tenga especial cuidado con los adjuntos y enlaces que pudiera contener.
Hi Rafael,
Thank you again for the constructive discussion and for all your support throughout the Grant Agreement preparation process.
Estonia/JDM remains supportive of the objectives of EUNOMIA.AI. We see clear strategic value in the project, particularly around trustworthy generative AI for public administration, digital-government use cases, legal and governance maturity, and practical public-sector adoption.
We are now preparing the executive recommendation on Estonia/JDM's accession and implementation readiness. To support that we are trying to distinguish between matters that are already sufficiently defined and those that are intentionally expected to be agreed during project implementation.
From our perspective, the remaining questions are about how the practical implementation of Estonia's role is expected to work. We appreciate that not every operational detail can or should be finalised before project kick-off, but we would like to distinguish between what is already fixed through the Grant Agreement and Annexes, and what is intentionally left to be developed during the WP5 planning phase.
It would be helpful to clarify the following points, or route them to the appropriate WP or PMO colleagues.
- Estonia's practical role in WP5
What is Estonia/JDM expected to deliver under WP5 in practical terms?
For example, should we expect our primary role to be defining and validating a public-sector use case, providing governance and legal expertise, supporting implementation with users and domain knowledge, running an operational pilot, or some combination of these and what would you consider to be Estonia's primary responsibility within that overall delivery model?
- Flexibility to refine the pilot
This is probably the most important executive question for us.
Can Estonia still narrow, refine or redefine its pilot during the first months of WP5 if, after detailed planning, the currently envisaged pilot proves unrealistic, legally difficult, technically unsuitable, resource constrained or no longer aligned with national priorities?
Understanding how much flexibility exists after project kick-off would significantly help us assess the practical implementation risk.
- Implementation ownership
How should Estonia understand the expected division of responsibilities between JDM, the WP5 lead, WP2/WP3 technical partners, infrastructure partners and any external experts?
In particular, we would like to understand whether Estonia is expected to develop or operate technical components itself, or whether our primary role is expected to focus on defining, validating and evaluating the public-sector use case while technical implementation is supported elsewhere in the consortium.
- Data model and deployment approach
At a practical level, what data model is currently envisaged for Estonia's pilot? Is it real public-sector data, synthetic data, anonymised data or another approach and how will this be determined during WP5 planning?
Similarly, is there already an expectation whether Estonia's pilot would primarily use the central infrastructure, a federated/local deployment model, or whether this will also be agreed during the WP5 planning phase?
- JDM subcontracting budget
The current budget includes a €100,000 subcontracting allocation for JDM.
Could you clarify how JDM's €100,000 subcontracting allocation is expected to be used in practice?
In particular:
- is this subcontracting already linked to a specific implementation concept or deliverable;
- who is expected to define its scope;
- how much discretion JDM has regarding procurement and supplier selection; and
- whether the detailed scope is expected to be agreed during the early WP5 planning activities.
- First-phase implementation expectations
Beyond the standard beneficiary obligations under the Grant Agreement, are there any project-level expectations regarding the timing of staffing, procurement or other implementation activities that partners should be aware of during the initial phase of the project?
- Consortium Agreement
Which practical implementation matters should partners expect to be governed through the Consortium Agreement rather than through the Grant Agreement and Annexes?
From Estonia's perspective, this is particularly relevant for operational decision-making, WP5 responsibilities, data governance, intellectual property, confidentiality, liability, subcontracting and escalation procedures should a pilot need to be adjusted during implementation.
- Implementation governance
Could you help distinguish between:
- matters already fixed;
- matters expected to be clarified in the Consortium Agreement;
- matters intentionally left for WP5 planning.
This distinction would help us brief our management accurately by clearly separating contractual commitments from the normal collaborative planning that will take place after project kick-off.
Our objective is simply to ensure that our executive recommendation accurately reflects both the commitments already established through the Grant Agreement and the areas where implementation planning will continue after project kick-off. We believe that distinction is important for setting realistic expectations from the outset for both Estonia and the consortium.
If helpful, I believe the easiest approach would be a short written response to these points, followed by a focused discussion with ADA/PMO and, if appropriate, the WP5 lead.
Thank you again for your continued support. We appreciate all the work that has gone into bringing the project to this stage.
Best regards,
Jaanus Vänt
AI and Data Strategy Coordinator
AI and Data Unit (AIAT)
Ministry of Justice and Digital AffairsRepublic of Estonia
[email protected]
www.justdigi.ee | Suur-Ameerika 1, Tallinn