TEADUS- JA ARENDUSTÖÖ LEPING
Käesoleva teadus- ja arendustöö lepingu (Leping) on selle digiallkirjastamise kuupäeval sõlminud:
(1) Milrem AS, registrikood 12494266, asukoht Betooni tn 1, Tallinn 13619 (Tellija), keda esindab
juhatuse liige Mikk Mägi ja
(2) Kaitsevägi, registrikood 70008641, asukoht Juhkentali 58, 15007 Tallinn (Töövõtja), keda
esindab Kaitseväe juhataja 31.12.2025 käskkirjaga nr 78 antud volituse alusel Kaitseväe
Akadeemia ülem mereväekapten Johan-Elias Seljamaa,
edaspidi eraldi nimetatud ka kui Pool või koos kui Pooled,
VÕTTES ARVESSE
A. Tellija kuulub Euroopa ettevõtete konsortsiumisse, mis on sõlminud toetuse lepingu Euroopa
Komisjoniga, eesmärgiga viia läbi Euroopa kaitsevaldkonna tööstusliku arendamise programmi
projekt “Integrated Modular Unmanned Ground System 2“ (iMUGS 2 projekt või Projekt), kus
Tellija tegutseb konsortsiumi koordinaatori ja tarnijana;
B. Vastavalt Euroopa Komisjoniga sõlmitud toetuse lepingule toimub Projekti tööde vastuvõtmine ja
kvaliteedi hindamine Projektis osalevate liikmesriikide esindajate poolt loodud komisjonis
(Project Office), mis kinnitab tingimustele vastava töö vastava sertifikaadiga nn Certificate of
Conformity;
C. Tellija on iMUGS 2 projektis registreerinud Töövõtja oma ametlikuks alltöövõtjaks ning käesoleva
Lepinguga soovivad pooled kokku leppida alltöövõtu täpsemates tingimustes.
POOLED ON SÕLMINUD LEPINGU ALLJÄRGNEVATEL TINGIMUSTEL.
1. LEPINGU ESE JA TÖÖ TEOSTAMISE TÄHTAEG
1.1. Tellija tellib ja Töövõtja viib läbi Lepingu tingimuste kohaselt teadus ja arendustöö, mille täpsem
kirjeldus on sätestatud lisas 1 Töö kirjeldus “20251216_WP2_MLR_iMUGS2 EMA
WorkDescription_v1.5” (Töö).
1.2. Tellija tagab Töö käigus, et Tellija iMUGS2 projekti tööpakett nr 2 (lisa 1) tegevused säilitaksid
eetilise, doktrinaalse ja operatsioonilise kooskõla vastavuses kehtivate kaitsevaldkonna
standarditega.
1.3. Töövõtja toetab Tellijat sõjandusliku ja sõjateadusliku ekspertiisiga, mis seob uurimiseesmärgid
praktilise rakendusega. Ekspertiis hõlmab liitlaste doktrinaalsete käsitluste ühtlustamist ning
panustamist realistlike operatsioonistsenaariumite ja missioonilõimede (mission threads)
väljatöötamisse (vastavalt lisale 1, edaspidi Töö). Samuti sisaldab Töö oluliste tehnoloogiliste
komponentide operatsioonilise toimivuse hindamist, näiteks võrgu- ja sidelahendused,
mehitamata õhusõidukite vastane võime (CUAS) ja emissioonikontroll (EMCON).
1.4. Töö tulemusena suurendab Töövõtja Projekti usaldusväärsust ja tagab, et Projekti tööpaketi nr 2
(lisa 1) väljundid on kooskõlas sõjalise doktriini ja tegelike olukordadega.
1.5. Töö tuleb teha inglise keeles ning läbi viia vastavalt käesolevas lepingu lisadele 1 ja 2.
1.6. Tellija poolt tehtav Töö on jaotatud järgmiseks seitsmeks osaks, mis on toodud lisas 1:
1. EMA-DEL-01
2. EMA-DEL-02
3. EMA-DEL-03
4. EMA-DEL-04
5. EMA-DEL-05
6. EMA-DEL-06
7. EMA-DEL-07
Lk 1 / 5
1.7. Töö tehakse ja antakse Tellijale üle vastavalt lisa 1 peatükis 6 “Deliverables table” toodud
tähtaegadele.
2. LEPINGU DOKUMENDID
2.1. Leping koosneb Lepingu tekstist, selle lisadest ja Poolte kirjalikest kokkulepetest Lepingu
mistahes muudatuste või täienduste kohta, mis sõlmitakse pärast Lepingu jõustumist. Kui
Lepingu ja sellele allkirjastamise hetkel lisatud lisade vahel esineb lahknevusi, on ülimuslik
Lepingu tekst. Kui Lepingu ja selle lisade ning hiljem allkirjastatud Lepingu lisade või hilisemate
kirjalike lepingute vahel esineb lahknevusi, on ülimuslikud hilisemad lisad ja kirjalikud lepingud.
2.2. Lepingu allkirjastamisel on sellel järgmised lisad:
1) Lisa 1._Töö kirjeldus _WP2_MLR_iMUGS2 EMA WorkDescription_v1.5;
2) Lisa 2. Põhilepingust alltöövõtjale edasiantavad tingimused.
3. TÖÖ ÜLEANDMINE JA VASTUVÕTMINE
3.1. Töö raames saavutatud tulemused antakse Tellijale üle eraldiseisvalt ning iga tulemuse
üleandmine ja vastuvõtmine toimub käesolevas peatükis sätestatud korras.
3.2. Töövõtja teavitab tulemuste valmimisest viivitamata Tellijat ning esitab tulemused
ülevaatamiseks Tellijale elektroonselt e-posti teel. Töövõtja kohustub koos tulemustega Tellijale
üle andma kõik olemuslikult tulemuste juurde kuuluvad dokumendid.
3.3. Töö osad esitatakse Tellijale kahes versioonis – mustandversioon ning lõplik versioon.
Mustandversioon on Töövõtja poolt lõplik ja Töövõtja poolt kinnitatud dokument. Lõplik versioon
on mustandversioon, mida on täiendatud vastavalt Tellija ja Project Office juhistele.
3.4. Töö mustandversiooni kinnitab Tellija mõistliku aja jooksul pärast selle esitamist kirjaliku
kinnitusega.
3.5. Tellija esitab mõistliku aja jooksul pärast seda, kui Töövõtja on esitanud Tellijale Töö lõpliku
versiooni, Töö tulemuste vastavuse hindamiseks Project Office’ile.
3.6. Töö lõplik versioon loetakse Tellija poolt lõplikult vastuvõetuks, kui Project Office kinnitab
tulemused kinnitusega „Certificate of Conformity“.
3.7. Kui Project Office või Tellija esitab pretensioone tulemuste kohta (nii mustand- kui ka lõplikus
versioonis), kohustub Töövõtja kõrvaldama puudused mõistliku aja jooksul peale puudustest
teavitamist ning esitama tulemused uuesti üle vaatamiseks Tellijale ja Project Office’ile.
4. TASU
4.1. Tellija maksab Töövõtjale nõuetekohase Töö teostamise eest kokku 100 000 eurot (Tasu),
millele lisandub seaduses sätestatud käibemaks. Tellija maksab Tasu vastavalt järgnevale
maksetingimustele:
1) Makse 1 - 40 000 eurot (ilma KM-ta):
a. Töövõtja on esitanud Tellijale kirjalikult kõik Tööde osade mustandversioonid
(eeldatav Töö osade teostamise tähtaeg 29.05.2026);
b. Tellija on kinnitanud vastavate Töö mustandversioonide vastavuse tingimustele.
2) Makse 2 – 60 000 eurot (ilma KM-ta):
a. Töövõtja on esitanud Tellijale kirjalikult kõik Tööde osade lõplikud versioonid
(eeldatav Töö osade teostamise tähtaeg 31.10.2026);
b. Tellija ja Project Office on kinnitanud vastavate Töö lõplike versioonide
vastavuse tingimustele väljastades „Certificate of Conformity“’i.
4.2. Tellija maksab Töövõtjale Tasu vastavalt eelnevale maksegraafikule Töövõtja poolt esitatud
arvete alusel, mille maksetähtaeg ei ole lühem kui 30 kalendripäeva.
4.3. Töövõtjal on õigus esitada Tellijale Tasu arve alates punktis 4.1 sätestatud tingimuste täitmisest.
Arved loetakse tasutuks, kui kogu arvel näidatud summa on laekunud Töövõtja arveldusarvele.
Lk 2 / 5
5. POOLTE ÕIGUSED JA KOHUSTUSED
5.1. Töövõtja kohustub:
5.1.1. teostama Töö vastavalt Lepingule, kehtivatele õigusaktidele ja Tellija juhistele;
5.1.2. järgima Töö teostamisel ja korraldamisel Tellija mõistlikke huve ja eesmärke ning kõiki
Tellija poolt antud seaduslikke juhiseid;
5.1.3. viivitamata pöörduma Tellija poole juhiste saamiseks, kui need on vajalikud Töö
teostamiseks;
5.1.4. teavitama Tellijat viivitamatult kõikidest asjaoludest, mis mõjutavad Töö teostamist või
Töövõtjapoolsete muude Lepinguliste kohustuste täitmist ning mille vastu on Tellijal
mõistlik huvi;
5.1.5. hankima kõik Töö teostamiseks vajalikud materjalid;
5.1.6. ilma eraldi kokkuleppeta teostama ka sellised tööd ja toimingud, mis ei ole Lepingus ega
selle lisades selgesõnaliselt ette nähtud, kuid mille tegemine on tavapäraselt vajalik
Lepingu kohaseks täitmiseks ja eesmärgi saavutamiseks ning mis olemuslikult kuuluvad
Töö hulka;
5.1.7. tagama Töö käigus valmivate dokumentide vastavuse kehtivatele õigusaktidele ja
Lepingule;
5.1.8. mitte rikkuma Tellijale või kolmandatele isikutele kuuluvaid õigusi, sh intellektuaalse
omandi õigusi ning tagama, et Töövõtjal oleks kõik õigused anda Töö Tellijale üle
vastavalt käesolevas Lepingus sätestatule.
5.2. Töövõtjal on õigus:
5.2.1. nõuda Tellijalt juhiseid, kui need on vajalikud Töö teostamiseks;
5.2.2. peatada Töö teostamine, kui Töövõtja on nõudnud Tellijalt juhiseid ja Tellija ei ole mõjuva
põhjuseta neid mõistliku aja jooksul andnud;
5.2.3. saada Töö teostamise eest tasu vastavalt Lepingule.
5.3. Tellija kohustub:
5.3.1. andma Töövõtjale viivitamata juhiseid, kui need on vajalikud Töö teostamiseks;
5.3.2. andma viivitamata Töövõtjale üle kõik Töö teostamiseks vajalikud lähteandmed;
5.3.3. Töö valmimisel korraldama Töö üle vaatamise ja koos Project Office’iga selle vastu
võtma või vastuvõtmisest keelduma mõistliku aja jooksul pärast seda, kui Töövõtja on
Tellijat Töö valmimisest teavitanud ning seda Tellijale ja Project Office’le esitlenud;
5.3.4. maksma Töövõtjale valminud Töö eest tasu vastavalt Lepingule;
5.3.5. teavitama Töövõtjat koheselt kõikidest asjaoludest, mis mõjutavad Tellijapoolsete
Lepinguliste kohustuste täitmist ning mille vastu on Töövõtjal mõistlik huvi;
5.3.6. Töös puuduse avastamisel teavitama Töövõtjat avastatud puudusest mõistliku aja
jooksul pärast puuduse avastamist;
5.3.7. Töös avastatud puudusest teavitamisel kirjeldama avastatud puudust võimalikult täpselt.
5.4. Tellijal on õigus:
5.4.1. igal ajal tutvuda Töö käiguga, välja arvatud juhul, kui see segaks oluliselt Töö teostamist;
5.4.2. Töös esinevate puuduste korral nõuda Töö vastavusse viimist Lepingu tingimustega;
5.4.3. kõrvaldada Töös esinev puudus ise või lasta see kõrvaldada kolmandal isikul juhul, kui
Töövõtja ei kõrvalda Töös esinevat puudust mõistliku aja jooksul pärast Tellijapoolset
puudusest teavitamist;
5.4.4. nõuda Töövõtjalt Töö puuduse kõrvaldamisega seotud kulutuste hüvitamist;
5.4.5. jätta Töö vastu võtmata, kui Töös esineb puudusi, välja arvatud pisipuudused, mis ei
takista Töö tulemuse kasutamist;
Lk 3 / 5
5.4.6. keelduda Töö eest tasumast kui Töö ei vasta Lepingutingimustele, muuhulgas kui
Lepingutingimustele ei vasta Töö juurde kuuluvad dokumendid või sellised dokumendid
on Tellijale üle andmata.
6. INTELLEKTUAALNE OMAND
6.1. Töövõtja annab Lepingu täitmise käigus loodud Töö omandiõiguse ja loovutatavad
intellektuaalomandiõigused (sh autori varalised õigused, õigus esitada taotlus kaubamärgi,
patendi, kasuliku mudeli, tööstusdisainilahenduse või mikrolülituse topoloogia registreerimiseks,
samuti õigused tundmatutele kasutusviisidele, mis tekivad tulevikus) Lepingus või Eesti Vabariigi
seadustes sätestatud maksimaalses ulatuses Töö üleandmisega üle Tellijale mistahes täiendava
toimingu või tahteavalduseta.
6.2. Töövõtja annab Töövõtjale kuuluvate või temale litsentsi alusel kasutusse antud
võõrandamatute, ent litsentseeritavate õiguste osas Tellijale tagasivõetamatu ainulitsentsi
Töövõtjale kuuluvate võõrandamatute õiguste kasutamiseks ja/või teostamiseks maksimaalses
kohalduva õiguse alusel lubatud ulatuses ilma geograafiliste piiranguteta ning ilma piiranguteta
kasutamise viisi, eesmärgi ja kasutajate ringi suhtes. Litsents on ülemaailmne ja loovutatav ning
sisaldab õigust luua teoste põhjal tuletatud teoseid, väljastada all-litsentse nii kolmandatele
isikutele kui ka üldsusele, süstematiseerida ja lülitada teosed kogumikku, kasutada teost
kollektiivse teose või andmebaasi loomiseks, samuti kasutada teose eri osi ja elemente
tulemusest eraldi isegi juhul, kui need on salvestatud koos ja moodustavad ühtse terviku.
Ainulitsents kehtib alates vastava õiguse tekkimisest kuni litsentsitud intellektuaalse omandi
õiguse kehtivuse tähtaja lõppemiseni.
6.3. Kahtluste vältimiseks on Pooled kokku leppinud, et Töövõtja kohustub piirama oma
intellektuaalse omandi õiguste teostamist järgmiselt:
6.3.1. kui Töövõtja on Töö Tellijale üle andnud või muul moel Tellijale kättesaadavaks teinud,
võib Tellija otsustada, kas Töö on sellisel kujul valmis avaldamiseks kolmandatele
isikutele või avalikkusele. Töövõtja ei tee Tellijale takistusi Töö avaldamiseks. Töövõtja
ei või ise ilma Tellija eelneva kirjaliku nõusolekuta Tööd avaldada;
6.3.2. Nii Tellija kui ka kolmandad isikud võivad Tellija nõusolekul või heakskiidul muuta,
parandada ja täiendada Tööd ning lisada Tööle teiste autorite loomingut ja muid
materjale, mida Tellija peab vajalikuks.
6.4. Töövõtjal on õigus kasutada Tööd enda teadustöödes ja/või publikatsioonides tingimusel, et
avalikustatava teabe sisu, koht, viis ja aeg kooskõlastatakse eelnevalt kirjalikult Tellijaga. Tellija
vastab Töövõtja vastavasisulisele päringule 20 tööpäeva jooksul alates päringu saamisest. Kui
Tellija päringule ei vasta, loetakse, et Tellija nõustub Tulemi kasutamise lubamisega päringus
märgitud viisil.
6.5. Pooled on leppinud kokku, et tasu intellektuaalse omandi ja kaasnevate õiguste Tellijale
loovutamise ja litsentsi andmise eest sisaldub Tasus.
6.6. Töövõtja kohustub tagama, et tema poolt Töö tegemisel loodavad intellektuaalse omandi objektid
on loodud Töövõtja poolt ega kahjusta mistahes kolmanda isiku autori- või mistahes muid
intellektuaalse omandi õigusi. Kui Töövõtja on teose loomisel rikkunud kolmandate isikute õigusi
ning Tellija on sellega seoses kohustatud hüvitama kolmandale isikule tekitatud varalise ja/või
mittevaralise kahju, on Töövõtja kohustatud Tööandja poolt maksmisele kuuluvad summad ning
sellega seoses kantavad kulutused ja kahju Tellijale hüvitama.
7. POOLTE VASTUTUS
7.1. Kui Tellija viivitab Töövõtjale tasu maksmisega, siis on Töövõtjal õigus nõuda Tellijalt viivist
0,05% päevas viivitatud summalt iga tasumisega viivitatud päeva eest.
7.2. Töö valmimise, üleandmise või Töös esineva puuduse kõrvaldamisega viivitamisel kohustub
Töövõtja tasuma Tellijale leppetrahvi 0,05% valmimata, üle andmata või puudusega Töö
maksumusest päevas iga viivitatud päeva eest. Tellija kohustub leppetrahvi nõudmisest
Töövõtjat teavitama mõistliku aja jooksul pärast seda, kui ta Töövõtjapoolsest viivitusest teada
sai.
Lk 4 / 5
8. KEHTIVUS JA LÕPPEMINE
8.1. Kumbki Pool võib Lepingust taganeda, kui teine Pool on Lepingut oluliselt rikkunud ja rikkuv Pool
ei ole heastanud rikkumist täiendava mõistliku tähtaja jooksul, mis ei tohi olla lühem kui 30
kalendripäeva.
8.2. Kui Tellija ütleb käesoleva Lepingu üles või loobub Töö edasisest tellimisest, on Töövõtja
õigustatud saama tasu enne katkestamise hetke faktiliselt teostatud Töö eest.
9. TEATED
9.1. Kõik Lepingu kohased teated, nõuded, pretensioonid või muud teated edastatakse eesti keeles,
ning kirjalikku taasesitamist võimaldavas vormis teisele Poolele järgmistel kontaktisikutele:
Kaitsevägi (Kaitseväe Akadeemia Milrem AS:
kaudu):
Karl Salum Urmas Tiirik
Riia 12, Betooni tn 1
51010 Tartu Tallinn 13619
e-mail:
[email protected] e-mail:
[email protected]
või mõnele muule kontaktaadressile, mille vastav Pool võib edaspidi teisele Poolel täpsustada
kirjalikult.
9.2. Pooled teatavad teineteisele viivitamata kõigist muudatustest oma kontaktandmetes. Kuni sellise
teate kättesaamiseni loetakse punktis 9.1. nimetatud kontaktisikutele edastatud teated
nõuetekohaselt edastatuks.
10. LÕPPSÄTTED
10.1. Leping jõustub selle digiallkirjastamisest mõlema Poole poolt ning on kehtiv kuni Poolte
lepinguliste kohustuste täitmiseni.
10.2. Töövõtja peab hoidma saladuses talle Lepingu täitmisega teatavaks saanud asjaolusid, mille
saladuses hoidmiseks on Tellijal õigustatud huvi (sealhulgas, kuid mitte ainult asjaajamist ja
majandustegevust puudutavat teavet) arvestades Poolte tegevuses väljakujunenud tavasid ja
praktikat.
10.3. Lepingut võib muuta või täiendada ainult Poolte sellekohasel kirjalikul kokkuleppel. Kirjaliku vormi
järgimata jätmine on õigustühine. Kõik Lepingu muudatused vormistatakse kirjalikult Lepingu
lisana, mis on Lepingu lahutamatuks osaks.
10.4. Kumbki Pool ei tohi käesolevast Lepingust tulenevaid õigusi ja kohustusi üle anda kolmandale
isikule ilma teise Poole kirjaliku nõusolekuta.
10.5. Lepingu suhtes kohaldatakse Eesti Vabariigi õigust.
10.6. Pooled lahendavad Lepingust tulenevad vaidlused läbirääkimiste teel. Kokkuleppe
mittesaavutamise korral lahendatakse vaidlused Harju Maakohtus.
10.7. Lepingu tingimusteks ei loeta Poolte varasemaid tahteavaldusi ega kokkuleppeid, mis ei ole
Lepingus otseselt sätestatud. Samuti ei oma Lepingu suhtes tähendust Poolte varasem
käitumine.
KINNITAMAKS EELTOODUT on Pooled allkirjastanud käesoleva Lepingu
/allkirjastatud digitaalselt/ /allkirjastatud digitaalselt/
Milrem AS Kaitsevägi
Mikk Mägi mereväekapten Johan-Elias Seljamaa
Lk 5 / 5
Lisa 1 - Work Description – EMA Contribution to iMUGS2
Work Package 2 – Concept Development
Work Description – EMA Contribution to iMUGS2
Version History
Version Changes Author
1.0 Initial version Sami L.
1.1 Reviewed, reworded and specified parts 3 and 5. Tõnu N.
1.2 Minor updates after TNO WP kick-off Ivan Z.
1.3 Change in format, wording, added deliverable table to Urmas T.
part 6
1.4 Change in deliverable table Urmas T.
1.5 Change in EMA-DEL-05 deadline Urmas T.
1
Work Description – EMA Contribution to iMUGS2
Contents
1. GLOSSARY ........................................................................................................................... 2
2. OBJECTIVE ........................................................................................................................... 3
3. SCOPE & OUTPUTS ............................................................................................................... 3
4. METHODS & APPROACH ....................................................................................................... 4
5. DELIVERABLES & MILESTONES DESCRIPTION ........................................................................ 4
5.1. CONTRIBUTIONS TO CONSORTIUM DELIVERABLES ........................................................................... 4
5.2. PARTICIPATE IN WP2 WORKSHOPS: ............................................................................................ 4
5.3. PARTICIPATE IN T.2.2 WORKFLOW:.............................................................................................. 5
5.4. PARTICIPATE IN OTHER WORKFLOWS:........................................................................................... 5
6. DELIVERABLES TABLE ........................................................................................................... 7
7. ESTONIAN MILITARY ACADEMY ROLES (RACI) ........................................................................ 9
8. REFERENCES ....................................................................................................................... 9
1. Glossary
EMA Estonian Militarty Academy (Eesti Kaitseväe Akadeemia)
ELSA Ethical, Legal, and Societal Aspects (Ethical Framework)
LandOps Land Operations
UGS Unmanned Ground System
MDMP Military Decision-Making Process
OITL Operator-In-The-Loop
RoE Rules of Engagement
CONUSE Concept of Use
ConOps Concept of Operations
EMCON Emission Control
CUAS Counter Unmanned Aircraft Systems
UGV Unmanned Ground Vehicle
2
Work Description – EMA Contribution to iMUGS2
2. Objective
The objective of EMA’s work within the iMUGS2 scope is to ensure that all WP2 activities
maintain ethical, doctrinal, and operational coherence in line with current and emerging
defence standards.
EMA supports Milrem Robotics by providing military-academic expertise that bridges
research objectives with practical application. This includes aligning doctrinal
approaches across partners, contributing to the development of realistic operational
scenarios and mission threads, and validating the operational soundness of key
technological components such as networking, counter-UAS (CUAS), and emission
control (EMCON). Through this collaboration, EMA strengthens the project’s credibility
and ensures that WP2 outputs are consistent with military doctrine and operational
realities.
3. Scope & Outputs
• T2.1 Ethical, Legal, Societal Aspects & Regulations of LandOps with Unmanned
Autonomous Systems
• Capitalize on IMUGS results, hand-over to task lead.
• Contribute doctrinal/ethical input:
▪ Doctrine extraction, MDMP mapping, OITL points;
▪ Analyse changes in accountability chain, RoE cross-ref;
▪ Asses the Ethical Design Framework, validate domain related training
solutions in the Baltics.
• T2.2 Operational Framework
• Validate Operational Framework against Baltic States Defence Forces (in
collaboration with Baltic Defence College) doctrine and training practices.
• Support Milrem Robotics in Scenarios and Mission Threads development .
• Review and co-author Operational Framework.
• Support in Mission Concept Review Workshop facilitation.
• T2.3 Scenario Development: T2.3.2 Trial Plan
• Support in the development of a trial plan (10–12 pages) including objectives,
scenarios, and expected outcomes, integrating Estonian Defence Forces’
expertise.
• T2.4 CONOPS: T2.4.2 Wingman Concept for Mechanised Units / T2.4.3
Distributed Multi-Layer Counter-UAS / T2.4.5 EMCON Levels for UGVs
• Support Milrem in defining operational aspects of wingman and CUAS
employment (within Mission Scenarios and Threads development).
3
Work Description – EMA Contribution to iMUGS2
• Contribute to EMCON level definitions and validation of communication
limitations
• T2.5 Manned Unmanned Teaming (MUM-T) concepts: T2.5.10 Deployment Case
Studies
• Contribute to the definition of 8 deployment case studies (8–10 pages each)
on UGS use in MUM-T operations in different armies.
4. Methods & Approach
• Use military SME workshops and wargaming to assess CONOPS
• Provide academic/military research and doctrine review (Estonian/Baltics/NATO
perspective)
• Co-develop and review scenarios, mission threads, and operational roles
5. Deliverables & Milestones description
5.1. Contributions to consortium deliverables
D2.1 Ethical Framework (operational aspects, changes from IMUGS)
T2.1.1- Ethical Design Framework:
Contribute to the ethical design framework (20–25 pages) consolidating best practices
for AI-enabled defense systems. Framework must include auditable criteria for
compliance verification. Circulate draft to at least 2 external reviewers for auditing
feedback.
T2.1.5 - iMUGS1 ELSA adaptation report:
Contribute to reviewing the ethical, societal, and legal studies from iMUGS1 (minimum
3 documents). Produce an adaptation report (10–12 pages) identifying transferable
insights and gaps and propose adjustments for current project context.
D2.2 Operational Requirements
Give input in operational aspects, support in reviewing and specifying requirements.
D2.3 Operational Framework
Co-author and review sections of Light/Medium Infantry Battalion Group augmented
with Robotics, Concepts for Heavy Infantry/Armor Wingman, CUAS, EMCON.
5.2. Participate in WP2 workshops:
• Kick-off Workshop at MLT (Tallinn) M2
• 2nd Workshop at TNO (Netherlands) M4 (ELSA and Operations WS happens at the
same time separately).
• Scenario and MUM-T Workshop PIAP (Poland) M7
• Trial scenarios workshop FFI (Norway) M12
4
Work Description – EMA Contribution to iMUGS2
5.3. Participate in T.2.2 workflow:
ONLINE: Intro meeting: setting of goals and work procedures, introduction to WS1
(Operational Analysis Workshop), validation meeting.
PHYSICAL #1 WS (Operational Analysis Workshop) in Tallinn,: Kick-off for T2.2:
1. Introduce working procedure within Milrem Mission Engineering.
2. Introduce Mission Thread template.
3. Agree on the way of working and responsibilities for the assignment of Mission
Threads development. Top-down (Mission Scenarios to Mission Threads) and
bottom-up (Mission Threads traced to Mission Scenarios) method is being
proposed.
4. Introduce template for Military Problem Statements
5. Brainstorming to mature list of problems (Milrem to add identified problems).
ONLINE: Continuation of work with:
1. Further refine Mission Scenarios
2. Evaluate problems with consortium, refine, specify, consortium cross listing of
who is interested in solving what problem(s).
3. Tasking Consortium members to validate problem statements with Nations.
5.4. Participate in other workflows:
5.4.1. Three (3) agreed Mission Scenarios, Problem Statement List with
cross-listing/allocation of consortium members.
ONLINE: Status-check-up meeting biweekly (1,5 mo):
1. Check up on how validation is going (EMA to validate with Estonian/Baltics MOD
reps).
2. Introduction to problem prioritization.
ONLINE: Scenario Validation meeting: to prioritize problems statement to be further
analysed in #2 WS: Mission Analysis WS, intro to the #2 WS.
PHYSICAL: #2 WS: Mission Analysis WS
1. Introduction of Mission Thread template and filling in procedure.
2. Developing of Mission Threads
3. Review of Mission Threads
4. Guidance for Maturing Mission Threads.
5. Guidance on Mission Thread Workshop facilitation with the Nations.
6. Tasking consortium members to validate concepts with Nations (EMA to
validate with Estonia, Baltics, Finland)
5
Work Description – EMA Contribution to iMUGS2
5.4.2 Several Mission Threads to be shared with partnering Nations for
validation of concepts.
4 x Company level Mission Threads, 12 x lower-level Mission Threads
ONLINE: Biweekly check-up meeting on progress (1,5 months), introduce a feedback
format and decision matrix (EMA to come up with the format)
ONLINE: Concept Validation meeting: Analyse answers from Nations and introduce #3
WS: Concept Validation.
PHYSICAL: #3 WS: Concept Validation WS (tentative)
1. Introduction to how Concepts move on to Operational Needs and Requirements
2. Hand-over with Systems Engineers, walking through the Mission Threads with
them.
5.4.3 Operational Framework structure
ONLINE: Bi-weekly sync-up: review what SE has created in the form of Operational
(Stakeholder) Needs and Requirements, comment and assist in specifying the content.
ONLINE: Operational Framework authoring meeting - assign specific parts of the
document to members, establish procedures of filling it in and reviewing.
ONLINE: Bi-weekly status meeting.
6
Lisa 1 - Work Description – EMA Contribution to iMUGS2
6. Deliverables table
Draft version – Finalized report approved by EMA
Final version – Amendments to draft version according to Milrem feedback
ID GA task(s) Delivery description Format Due dates
*page amount indicative
EMA-DEL-01 T2.1.1 / D2.1 Ethical design framework consolidating Report of 20-25 pages* Draft version 15.02.2026
best practices for AI-enabled defense
Final version 31.08.2026
systems. Framework must include
auditable criteria for compliance
verification.
EMA-DEL-02 T2.1.5 / D2.1 iMUGS1 ELSA adaptation report Report of 10-12 pages* Draft version – submitted
identifying transferable insights/gaps
Final version 31.08.2026
and proposing adjustments for iMUGS2
context.
EMA-DEL-03 T2.2.3 Mission Scenarios + Military Problem Report of 8–10 pages* Draft version 30.04.2026
Statements package: three (3) agreed per mission scenario,
Final version 30.06.2026
mission scenarios and a problem focus on security
statement list with operations
cross‑listing/allocation of interested
consortium members.
Work Description – EMA Contribution to iMUGS2
EMA-DEL-04 T2.2.3 Mission Threads package: agreed Report of 8–10 pages* Draft version 30.04.2026
mission threads to share with Nations per mission thread
Final version 30.06.2026
for validation (4× company-level and
12× lower-level mission threads).
EMA-DEL-05 T2.2.5 / D2.3 Operational Framework contribution Report on Operational Draft version 29.05.2026
(and T2.4.1– package: (a) validated structure and key Framework content
Final version 31.08.2026
T2.4.5 operational viewpoints; (b)
support) authored/reviewed sections on
Wingman (mechanised units),
Distributed multi-layer CUAS, and
EMCON levels for UGVs; plus
comments on stakeholder
needs/requirements drafts.
EMA-DEL-06 T2.3.2 Trial Plan contribution: operational Suggestions of 10-12 Draft version 30.04.2026
input to the trial plan (objectives, pages* for trial
Final version 30.06.2026
scenarios, expected outcomes) execution
leveraging Estonian Defence Forces
expertise.
EMA-DEL-07 T2.5.10 Deployment case studies input 8 – 10 pages* per case Draft version 30.04.2026
package: contributions to defining 8 study
Final version 30.06.2026
deployment case studies on UGS use in
MUM‑T operations (different armies).
End of project: 31.10.2026
8
Work Description – EMA Contribution to iMUGS2
7. Estonian Military Academy Roles (RACI)
• T2.1.1, T2.1.5: R (Responsible for doctrine/ethics)
• T2.2, T2.2.3: R/C (Responsible/Consulted for validation)
• T2.3, T2.3.2: R (Responsible for support tasks)
• T2.4.2, T2.4.3, T2.4.5: R (Responsible for support tasks)
• T2.5, T2.5.10: R (Responsible for support tasks)
• T2.6: I (Informed, optional support if tasked)
8. References
Grant Agreement – GAP-101223988
9
Lisa/ Annex 2
Põhilepingust alltöövõtjale edasiantavad tingimused/
Terms and conditions transferred from the main contract to the subcontractor
Article 9.3 Subcontractors
Subcontractors may participate in the action, if necessary for the implementation.
Subcontractors must implement their action tasks in accordance with Article 11. The costs for the
subcontracted tasks (invoiced price from the subcontractor) are eligible and may be charged by the
beneficiaries, under the conditions set out in Article 6. The costs will be included in Annex 2 as part of
the beneficiaries’ costs.
The beneficiaries must ensure that their contractual obligations under Articles 11 (proper
implementation), 12 (conflict of interest), 13 (confidentiality and security), 14 (ethics), 17.2 (visibility),
18 (specific rules for carrying out action), 19 (information) and 20 (record-keeping) also apply to the
subcontractors.
The beneficiaries must ensure that the bodies mentioned in Article 25 (e.g. granting authority, OLAF,
Court of Auditors (ECA), etc.) can exercise their rights also towards the subcontractors.
Action tasks involving classified information may be subcontracted only after explicit approval (in writing)
from the granting authority.
Flow-downs:
Article 11 (proper implementation)
11.1 Obligation to properly implement the action The beneficiaries must implement the action
as described in Annex 1 and in compliance with the provisions of the Agreement, the call
conditions and all legal obligations under applicable EU, international and national law.
11.2 Consequences of non-compliance If a beneficiary breaches any of its obligations under this
Article, the grant may be reduced (see Article 28).
Article 12 (conflict of interest)
12.1 Conflict of interests The beneficiaries must take all measures to prevent any situation
where the impartial and objective implementation of the Agreement could be compromised
for reasons involving family, emotional life, political or national affinity, economic interest
or any other direct or indirect interest (‘conflict of interests’). They must formally notify the
granting authority without delay of any situation constituting or likely to lead to a conflict of
interests and immediately take all the necessary steps to rectify this situation. The granting
authority may verify that the measures taken are appropriate and may require additional
measures to be taken by a specified deadline.
12.2 Consequences of non-compliance If a beneficiary breaches any of its obligations under
this Article, the grant may be reduced (see Article 28) and the grant or the beneficiary may
be terminated (see Article 32).
Article 13 (confidentiality and security)
13.1 Sensitive information The parties must keep confidential any data, documents or other
material (in any form) that is identified as sensitive in writing (‘sensitive information’) —
during the implementation of the action and for at least until the time-limit set out in the
Data Sheet (see Point 6). If a beneficiary requests, the granting authority may agree to
keep such information confidential for a longer period. Unless otherwise agreed between
the parties, they may use sensitive information only to implement the Agreement. The
beneficiaries may disclose sensitive information to their personnel or other participants
involved in the action only if they: (a) need to know it in order to implement the Agreement
and (b) are bound by an obligation of confidentiality. The granting authority may disclose
sensitive information to its staff and to other EU institutions and bodies. It may moreover
disclose sensitive information to third parties, if: (a) this is necessary to implement the
Agreement or safeguard the EU financial interests and (b) the recipients of the information
are bound by an obligation of confidentiality. The confidentiality obligations no longer apply
if: (a) the disclosing party agrees to release the other party (b) the information becomes
publicly available, without breaching any confidentiality obligation (c) the disclosure of the
sensitive information is required by EU, international or national law. Specific confidentiality
rules (if any) are set out in Annex 5.
13.2 Classified information The parties must handle classified information in accordance with
the applicable EU, international or national law on classified information (in particular,
Decision 2015/44417 and its implementing rules). Deliverables which contain classified
information must be submitted according to special procedures agreed with the granting
authority. Action tasks involving classified information may be subcontracted only after
explicit approval (in writing) from the granting authority. Classified information may not be
disclosed to any third party (including participants involved in the action implementation)
without prior explicit written approval from the granting authority. Specific security rules (if
any) are set out in Annex 5.
13.3 Consequences of non-compliance If a beneficiary breaches any of its obligations under
this Article, the grant may be reduced (see Article 28). Such breaches may also lead to
other measures described in Chapter 5.
Additions from Annex 5
Sensitive information with security recommendation
Sensitive information with a security recommendation must comply with the additional
requirements imposed by the granting authority.
Before starting the action tasks concerned, the beneficiaries must have obtained all approvals or
other mandatory documents needed for implementing the task. The documents must be kept on
file and be submitted upon request by the coordinator to the granting authority. If they are not in
English, they must be submitted together with an English summary.
For requirements restricting disclosure or dissemination, the information must be handled in
accordance with the recommendation and may be disclosed or disseminated only after written
approval from the granting authority.
EU classified information
If EU classified information is used or generated by the action, it must be treated in accordance
with the security classification guide (SCG) and security aspect letter (SAL) set out in Annex 1
and Decision 2015/4441 and its implementing rules — until it is declassified.
Deliverables which contain EU classified information must be submitted according to special
procedures agreed with the granting authority.
Action tasks involving EU classified information may be subcontracted only with prior explicit
written approval from the granting authority and only to entities established in an EU Member
State or in a non-EU country with a security of information agreement with the EU (or an
administrative arrangement with the Commission).
EU classified information may not be disclosed to any third party (including participants involved
in the action implementation) without prior explicit written approval from the granting authority.
National classified information
Where the call conditions allow for the setting up of a specific national security framework under
Article 27(4) of the EDF Regulation 2021/6972 or Article 13 of the EDIRPA Regulation
2023/24183 and the action uses or generates information classified by a national authority under
national law, the national rules apply.
For deliverables which contain classified results (‘foreground information’, i.e. information
generated in carrying out the action) by national authorities, the beneficiaries must respect the
security elements attached in Annex 1 (SAL and PSI) and give access for any purposes required
under this Agreement.
Article 14 (ethics)
14.1 Ethics The action must be carried out in line with the highest ethical standards and the
applicable EU, international and national law on ethical principles. Specific ethics rules (if
any) are set out in Annex 5.
14.2 Values The beneficiaries must commit to and ensure the respect of basic EU values (such
as respect for human dignity, freedom, democracy, equality, the rule of law and human
rights, including the rights of minorities). Specific rules on values (if any) are set out in
Annex 5.
14.3 Consequences of non-compliance If a beneficiary breaches any of its obligations under
this Article, the grant may be reduced (see Article 28). Such breaches may also lead to
other measures described in Chapter 5.
Additions from Annex 5
Ethics
Where the call conditions provide for specific ethics rules in Annex 5, actions involving activities
raising ethics issues must be carried out in compliance with:
- ethical principles (including the highest standards of research integrity), and
- applicable EU, international and national law, including the EU Charter of Fundamental
Rights and the European Convention for the Protection of Human Rights and Fundamental
Freedoms and its Supplementary Protocols.
The beneficiaries must pay particular attention to the principle of proportionality, the right to
privacy, the right to the protection of personal data, the right to the physical and mental integrity
of persons, the right to non-discrimination, the need to ensure protection of the environment and
high levels of human health protection.
Before the beginning of an action task raising an ethical issue, the beneficiaries must have
obtained all approvals or other mandatory documents needed for implementing the task, notably
from any (national or local) ethics committee or other bodies such as data protection authorities.
The documents must be kept on file and be submitted upon request by the coordinator to the
granting authority. If they are not in English, they must be submitted together with an English
summary, which shows that the documents cover the action tasks in question and includes the
conclusions of the committee or authority concerned (if any).
Article 17.2 (visibility)
17.2 Visibility — European flag and funding statement Unless otherwise agreed with the
granting authority, communication activities of the beneficiaries related to the action
(including media relations, conferences, seminars, information material, such as
brochures, leaflets, posters, presentations, etc., in electronic form, via traditional or social
media, etc.), dissemination activities and any infrastructure, equipment, vehicles, supplies
or major result funded by the grant must acknowledge EU support and display the
European flag (emblem) and funding statement (translated into local languages, where
appropriate): /../ The emblem must remain distinct and separate and cannot be modified
by adding other visual marks, brands or text. Apart from the emblem, no other visual
identity or logo may be used to highlight the EU support. When displayed in association
with other logos (e.g. of beneficiaries or sponsors), the emblem must be displayed at least
as prominently and visibly as the other logos. For the purposes of their obligations under
this Article, the beneficiaries may use the emblem without first obtaining approval from the
granting authority. This does not, however, give them the right to exclusive use. Moreover,
they may not appropriate the emblem or any similar trademark or logo, either by
registration or by any other means.
Additions from Annex 5
Additional communication and dissemination activities
If agreed with the granting authority, the beneficiaries may engage in the following additional
communication and dissemination activities:
- present the project (including project summary, coordinator contact details, list of
participants, European flag and funding statement and project results) on the beneficiaries’
websites or social media accounts
- upload the public project results to the European Defence Fund Project Results platform,
available through the Funding & Tenders Portal.
Article 18 (specific rules for carrying out action)
18.1 Specific rules for carrying out the action Specific rules for implementing the action (if
any) are set out in Annex 5.
18.2 Consequences of non-compliance If a beneficiary breaches any of its obligations under
this Article, the grant may be reduced (see Article 28). Such a breach may also lead to
other measures described in Chapter 5.
Additions from Annex 5
Specific rules for EDF actions
Where imposed by the call conditions, when implementing EDF actions, the beneficiaries must
respect the following conditions:
- ensure that none of the entities that participate as affiliated entities, associated partners,
subcontractors or recipients of financial support to third parties are established in countries
which are not eligible countries or target countries set out in the call conditions (or are
controlled by such countries or entities from such countries) — unless otherwise agreed
with the granting authority
- ensure that any cooperation with entities established in countries which are not eligible
countries or target countries set out in the call conditions (or are controlled by such
countries or entities from such countries): - does not affect the security and defence
interests of the EU or its Member States or the objectives of the EDF Programme as set
out in Article 3 of Regulation (EU) 2021/697
- excludes the possibility of unauthorised access to classified information linked to the action
(background, foreground or sideground)
- avoids potential negative effects over security of supply of inputs critical to the action
- prevents that contributions could be subject to control or restrictions (directly, or indirectly
through one or more intermediate undertakings, including concerning technology transfer)
- ensure that subcontracts or subcontractors are removed or added only after formal
amendment of Annex 1 (no simplified approval procedure; see Article 5,5, 6.2)
- ensure that the provisions in this Agreement relating to subcontracting, subcontracting
costs and subcontractors are also extended to the following types of sub-subcontractors
(Data Sheet, Articles 5, 6, 9, 13, 20, Annex 5): - sub-subcontractors to which at least 10%
of the total eligible costs of the action is allocated; - sub-subcontractors which may require
access to classified information in order to carry out the action
- for communication and dissemination activities (Article 17) request prior written approval
by the granting authority before: - implementing the communication or dissemination
activities
- acknowledging EU support (European flag (emblem) and funding statement) in the
communication or dissemination activities or on infrastructure, equipment, vehicles,
supplies or major results
- for linked actions involving a Member State project manager: - ensure that the action
remains at all times aligned with the linked action (i.e. including work packages,
deliverables, milestones, budget/lump sum breakdown and timetable)
- acknowledge and accept that: - the grant depends on the linked action managed by the
project manager and that the grant cannot reimburse costs that are fully paid under the
linked action
both actions will be managed and monitored in parallel and in close coordination with the project
manager, in particular:
- all information, data and documents will be exchanged and may be relied on for the
management of the other action (if needed);
- the coordinator must provide the project manager with a copy of the Grant Agreement and
the pre-financing reports/periodic reports when they are submitted to the granting authority
- approval to payments will be subject to consultation with the project manager and the
payment deadline is automatically suspended until the granting authority is informed about
the opinion of the project manager
- issues in one action may impact the other (e.g. suspension or termination in one action
may lead to suspension or termination also of the other action)
- checks, reviews or audits may also involve the project manager; moreover the project
manager has the right to object to the use of external experts or audit firms on grounds of
commercial confidentiality, conflict of interest or, in duly justified cases, of security reasons
- for other actions where a Member State project manager is appointed, the coordinator
must also provide the project manager with a copy of the Grant Agreement and the pre-
financing reports/periodic reports for information.
Article 19 (information)
19.1 Information requests The beneficiaries must provide — during the action or afterwards
and in accordance with Article 7 — any information requested in order to verify eligibility of
the costs or contributions declared, proper implementation of the action and compliance
with the other obligations under the Agreement. The information provided must be
accurate, precise and complete and in the format requested, including electronic format.
19.2 Participant Register data updates The beneficiaries must keep — at all times, during the
action or afterwards — their information stored in the Portal Participant Register up to date,
in particular, their name, address, legal representatives, legal form and organisation type.
19.3 Information about events and circumstances which impact the action The beneficiaries
must immediately inform the granting authority (and the other beneficiaries) of any of the
following: (a) events which are likely to affect or delay the implementation of the action or
affect the EU’s financial interests, in particular: (i) changes in their legal, financial,
technical, organisational or ownership situation (including changes linked to one of the
exclusion grounds listed in the declaration of honour signed before grant signature) (ii)
linked action information: not applicable (b) circumstances affecting: (i) the decision to
award the grant or (ii) compliance with requirements under the Agreement.
19.4 Consequences of non-compliance If a beneficiary breaches any of its obligations under
this Article, the grant may be reduced (see Article 28). Such breaches may also lead to
other measures described in Chapter 5.
Article 20 (record-keeping)
20.1 Keeping records and supporting documents The beneficiaries must — at least until the
time-limit set out in the Data Sheet (see Point 6) — keep records and other supporting
documents to prove the proper implementation of the action in line with the accepted
standards in the respective field (if any). In addition, the beneficiaries must — for the same
period — keep the following to justify the amounts declared: (a) for actual costs: adequate
records and supporting documents to prove the costs declared (such as contracts,
subcontracts, invoices and accounting records); in addition, the beneficiaries’ usual
accounting and internal control procedures must enable direct reconciliation between the
amounts declared, the amounts recorded in their accounts and the amounts stated in the
supporting documents (b) for flat-rate costs and contributions (if any): adequate records
and supporting documents to prove the eligibility of the costs or contributions to which the
flat-rate is applied for the following simplified costs and contributions: the beneficiaries do
not need to keep specific records on the actual costs incurred, but must keep: (i) for unit
costs and contributions (if any): adequate records and supporting documents to prove the
number of units declared (ii) for lump sum costs and contributions (if any): adequate
records and supporting documents to prove proper implementation of the work as
described in Annex 1 (iii) for financing not linked to costs (if any): adequate records and
supporting documents to prove the achievement of the results or the fulfilment of the
conditions as described in Annex 1 (d) for unit, flat-rate and lump sum costs and
contributions according to usual cost accounting practices (if any): the beneficiaries must
keep any adequate records and supporting documents to prove that their cost accounting
practices have been applied in a consistent manner, based on objective criteria, regardless
of the source of funding, and that they comply with the eligibility conditions set out in
Articles 6.1 and 6.2.
Moreover, the following is needed for specific budget categories: (e) for personnel costs:
time worked for the beneficiary under the action must be supported by declarations signed
monthly by the person and their supervisor, unless another reliable time-record system is
in place; the granting authority may accept alternative evidence supporting the time worked
for the action declared, if it considers that it offers an adequate level of assurance (f)
additional record-keeping rules: not applicable The records and supporting documents
must be made available upon request (see Article 19) or in the context of checks, reviews,
audits or investigations (see Article 25). If there are on-going checks, reviews, audits,
investigations, litigation or other pursuits of claims under the Agreement (including the
extension of findings; see Article 25), the beneficiaries must keep these records and other
supporting documentation until the end of these procedures. The beneficiaries must keep
the original documents. Digital and digitalised documents are considered originals if they
are authorised by the applicable national law. The granting authority may accept non-
original documents if they offer a comparable level of assurance.
20.2 Consequences of non-compliance If a beneficiary breaches any of its obligations under
this Article, costs or contributions insufficiently substantiated will be ineligible (see Article
6) and will be rejected (see Article 27), and the grant may be reduced (see Article 28).
Such breaches may also lead to other measures described in Chapter 5.