Frequently Asked Questions

Please find below KITT4SME calls FAQ where there are answers to some common questions. Note that this FAQ is frequently updated and the answers therein are not definitive and could change over time based on further questions or clarifications. If you plan to apply to the first Open Call, you should frequently review this FAQ and at least check it 1 day before submission when it will be definitive. After examining the FAQ below, if you still don’t find the answer please contact us on – Please note that we expect to respond within 2 working days.

Yes, provided that (a) you have opted to validate your solution under the Type-A call, (b) that you come in as part of a team through Type-B call, (c) that the validation pilot (location & use case) is different between Type-A & Type-B and (d) that your total amount of funding from the EU does not exceed 100.000€


After your proposal to enter the KITT4SME Cascade Funding scheme has been accepted you will be assigned a partner from the project’s Consortium, which will be your primary point of contact and will assist you with all matters related to the integration of your solution to the KITT4SME platform and the validation phase.

Applicants should demonstrate that their solution can be easily integrated into the KITT4SME platform. Ideally the solution should comprise RESTful services which are made available through Docker images and can be deployed to the KITT4SME service mesh by means of Kubernetes resource descriptors. Solutions featuring services with the aforementioned characteristics will be preferred. However, solutions grounded on different technical choices may be considered too depending on required integration effort and value to the platform. The technical integration will be carried out with the contribution from technical partners from the project during the execution phase of the Open Call.

It means that the solution has been validated in an real-life setting (preferable industrial), that is has a TRL-5 and above according to the definition by the EU. During the submission phase you are asked to provide documentation of the solution, description of the data used as input and data generated (type, format, additional requirements), description of the container and evidence of real-life testing (video, publication). More information will be made available through the Guide for Applicants.

Although not mandatory - strongly encouraged. Solutions that opt-out of the validation phase will be eligible for lower funding.

Not exactly. The solution will still be tested with historic data or data generated by simulation to verify that it works as intended before coming into the KITT4SME Marketplace. The mentor will be responsible for the provision of the most appropriate dataset.

We try to find the best match between your solution and our pilot cases. This is one of the reasons why we request that you provide an accurate description of the functionality and the requirements of your solution during the proposal submission. Adjustment of your solution is also foreseen during the execution phase.

The assignment to a specific Pilot will be done by your mentor in collaboration with you as part of the ‘Deployment Description’ milestone (a detailed timeline will be available in the Guide for Applicants). You are required to describe the Use Case that best demonstrates the value proposition of your solution in your proposal. You are encouraged to consult the description of our pilots in our webpage ( and propose a pilot case that is the best match for you (description of the pilots & lighthouse experiments will be available through the Guide for Applicants as well). During the assignment phase, you will be assigned to a pilot that may come from (a) pilot cases used in the KITT4SME project, (b) lighthouse experiments in the KITT4SME project or (c) pilots that come from Type-B Open Calls depending on the availability of resources & relevant data as well as proximity to the end-user requirements.

The funding that you receive via the Cascade Funding Scheme is intended to cover the costs (technical, administrative) related to the solution adaptation, integration of the solution to the KITT4SME platform and validation (where applicable) through the pilots.

Yes, provided that it is done with the consent of the respective end-user. The details of conducting the experiment will be finalized until the ‘Deployment Description’ (for Type-A) or the ‘Workplan Finalization’ (for Type-B) milestones with the participation of the corresponding mentor.

Yes, we would like to have a positive answer from you, but this does not necessarily mean that one will be assigned to you by one of our mentors. It will depend on the nature of the solutions that come inside the project via the Type-A Open Calls. If an experiment/ solution is assigned to your pilot, following a mutual agreement between the mentor, the experimenter and you (as an end-user), the appropriate arrangements will be made in collaboration with the mentor of your experiment until the ‘Workplan Finalization’ milestone. The total amount of additional equipment (& relevant external to the end-user’s infrastructure technologies) burdens the experiment. Integration and testing of ‘additional equipment’ is expected to be carried out jointly by the experimenter and the personnel of the factory (end-user). In this case, you as an end-user have the extra benefit that you will have additional AI-services validated in your own premises, which means that they can be easily adopted by your own workflow and day-to-day activities.

The KITT4SME framework is provided for testing and experimentation. Some of its components are coming with open source licensing, but some others may be proprietary. A cost-free license to use the proprietary components will be provided for the duration of the project, extending the duration of the license will be negotiation on per-case base. The experimenters retain full rights to the intellectual property developed during the experiments for their own results, as the results belong to those who generate them.

The participants for the open calls, should follow the participation rules as for any H2020 Innovation Action project. Therefore, the rates should be actual and occurred during the project. The Participants should keep their records for any future potential audit in the same way as for participating as partners in H2020 projects. The hourly rates must correspond to the hourly rates at similar positions and tasks of the participating party.

As already explained the experiments are supporting experimentation and extension of the KITT4SME framework to implement still existing challenging use cases for manufacturing industries. The positive validation of those experiments (which should also be considered in the experiment execution workplan) will surely require additional investment for full scale deployment.

The KITT4SME project and experiments contracts foresee an internal review process for all submitted deliverables. Approval of the deliverables is necessary for any intermediate or final payment. If the deliverables are not accepted the experiment work carried out will be evaluated and there is a risk for requesting to return the advance payment if no work can be actually justified and accepted.

When the proposal is submitted by consortium (mostly in Type B case), the contracts are negotiated with the coordinator of the project, who should have partners’ agreement with the involved parties. The rules of the contract are binding for the involved parties and the partners’ agreement should ensure this. The payment from KITT4SME goes to the coordinator who distributes it to the partners.

The proposals should provide a good balance of ambition and effort. They should be realistic. This aspect will be evaluated as well during the experiment selection process. Should any such risk be realized, will have to be dealt by the experiment which has to organize to provide the extra effort. Keep in mind that no additional payment beyond the proposed and contracted budget will be possible.

There is the possibility to reasonable changes of the workplan as long as these are fully justified. The rules of H2020 projects apply here as well.

From the FIWARE webpage ( “FIWARE is an open source initiative defining a universal set of standards for context data management which facilitate the development of Smart Solutions for different domains such as Smart Cities, Smart Industry, Smart Agrifood, and Smart Energy.” The KITT4SME architecture uses the FIWARE Context Broker as part of the data management mechanism. Your interaction with FIWARE (where appropriate) is considered to be part of the ‘integration activities’. For more about integration see question above.

RAMP stands for “Robotics and Automation Marketplace” and is an open platform for manufacturing end-users and solutions’ providers, offering dynamic networking and interaction functionalities between the users. It is being supported by 5 projects and more than 30 DIHs and offers unique opportunities for exposure. It is accessible online via RAMP is part of the KITT4SME platform and the solutions incorporated to the KITT4SME platform will be invited to be registered to RAMP as well (at least for the duration of the project).

The payments will be made in lump sum form in more than one installments. An advance payment will be provided to start. The KITT4SME project and experiments contracts foresee an internal review process for all submitted deliverables. Approval of the deliverables is necessary for any intermediate or final payment. Failing to provide approved deliverables may result in no further payments.

This website uses cookies and asks your personal data to enhance your browsing experience. Read cookie policy