top of page
IPR zApplication Asset Information
IPR Asset Name
Contact Email for template
What is the Main associated RTD Task?
Define the envisage state now in narrative.
Expected TRL (2021-06 - Project Month 30)
Expected TRL (2022-12 - Project Month 48)
Main component/subcomponent(s) name in ZDMP Architecture connected to / included in the zApp?
VERY IMPORTANT MAKE SURE EACH SUBCOMPONENT COVERED IF RELEVANT.
Are any of the above mentioned components/subcomponents critically needed to run the zApp (cannot be replaced by existing market solutions)?
For Background and Augmented Background
Are there relevant BACKGROUND Statements covering this asset in the ZDMP CA Annex 1? If so, state any critical points (be relevant – do not just cut-paste whole thing)
For Results and Augmented Background
Do you envisage any joint ownership? Carefully judge this if in a task with several partners. If YES, then with who and will it be fully joint or with an additional agreement? If NO and you are in such a joint task, why not?
Which other project Results is it dependent on (if any)?
Expected IP protection — NB whilst Licensing for commercial use is valid, any i4FS use agreement in GA/CA overrides this for i4FS specifically.
For Augmented Background only
What Augmented Background is it dependent on including subdependencies?
Is it Open Source?
For Licensing of the Asset regardless of type
If YES, what is Current License Type Now (if Background), or Anticipated (if Augmented Background or Results)
If NOT Open Source, is there an Open Source variant of this zApp, and if so, what is the prime candidate? How are its limits compared with commercial offering?
Other (Main) Sublicenses – ie which other licenses is it dependent on. Either Now, or Anticipated if Results
Commercial/Use Aspects – Considering i4FS specifically both IN and BEYOND PROJECT
i4FS — Use IN the project restrictions – cover issues (technical and commercial) and costs although for costs there should be none according to CA (Section 9.3*)
i4FS — Use AFTER the project restrictions for 3 years – cover issues (technical and commercial) and costs although for costs there should be none according to CA (Section 9.4*)
Commercial/Use Aspects – OTHER THAN i4FS both IN and BEYOND PROJECT
Other than i4FS — Use IN the project restrictions – cover issues (technical and commercial) and costs although for costs there should be none.
Other than i4FS — Use AFTER the project restrictions – cover issues (technical and commercial) and costs although for costs there should be none.
Commercial Aspects – Subcalls IN PROJECT
The zApp may need to be used by the open call partners within the project: Do you see issues with this? Costs, Limitations, Support, etc
Do you intend to claim confidentiality of the zApp and oppose its exploitation?
If YES, justify this decision (please don’t justify your answer simply by the “competitive advantage provided” by the confidential information)
bottom of page