Frequently asked questions on the Open calls

At our first brokerage day and after the publication of the first open call, we received a set of questions that seem to be of general relevance. Please find a selection of the most common and their respective answer answer below.

If you have a question that is not yet adressed, please address it to the open call ticketing system via

Please send your question to We are obliged to handle all questions related to the open calls through our ticketing system in order to comply with the obligations from the European Commission for a closed loop. We will make sure that your request is addressed to the appropriate person and answered in a reasonable timeframe.

If you think something is missing, this is your reason and driver to get involved! Please note that half of the project budget is dedicated to third party projects. The development of the RobMoSys ecosystem is clearly a community effort. We are looking forward to your proposal responding to that need addressed.

To achieve this goal, types of activities that qualify for financial support are software developments under the form of:

  • Models
    • Composable models of components (ports, blocks, connectors enriched with composition constraints, resource requirements, etc.).
    • Models of system-level composition (system composed out of models of components) within a relevant use-case (composition for design-time or run-time composability).
    • Models to realise an architectural pattern, a design principle or best practice.
  • Tools and Meta-Models
    • Extensions and/or improvements of, the provided RobMoSys meta-models (for instance for additional non-functional concerns such as Quality of Service, timing, performance, etc.).
    • Extensions and/or improvements of, the provided RobMoSys tools baseline (e.g. for design-time predictability, sanity checks, composability analysis, formal conformance verification, etc.). The current RobMoSys tools baseline is available here.

It is crucial that the contributions to the RobMoSys ecosystem strictly adhere to the RobMoSys modelling principles (composability, and conformity to meta-models). Full open source contributions are preferred but not mandatory. However, we expect at least the models and their transformations to proprietary tools to be under an open source license. Let us also note that in the first open call, we prefer projects that illustrate their contribution in the domain of robot-centric motion, navigation and manipulation.

The RobMoSys technical user-stories provide a variety of possible topics that RobMoSys encourages to consider.

On, you find all necessary documents, like call text, guide for applicants and proposal templates, as well as the link to the proposal submission platform.

Proposal evaluation criteria are described in section 9 (page 6f) of the guide for applicants.

Each proposal will be evaluated by at least two acknowledged evaluators with different expertise, for example in the technology field or in application area(s). External experts (independent of the RobMoSys consortium and of any proposer) as well as internal experts from the core consortium will be involved in the evaluation process. More details on the evaluation process are described in section 7 (page 6) of the guide for applicants.

As a special service to potential applicants, pre-proposals can be submitted via the RobMoSys Open Call Platform during the first nine weeks after publication of the call (so until September 8, 2017). A member of the staff of the RobMoSys Project will respond to applicants within a reasonable period (if longer than five business days, the applicants will be informed).

The response will be limited to clarifying whether the proposal fits into the scope of the call and how the proposal could be improved.

Please note that it is not mandatory to submit one and it has no influence on the evaluation of the full proposal. Pre-proposal should be based on the Proposal Template but Excellence and Impact sections are obligatory.

There will be a direct contract between CEA as coordinator of RobMoSys and the selected third party. A template funding agreement is provided at RobMoSys Funding Agreement Template.

Please note that the rights and obligations contained in this Funding Agreement derived from the RobMoSys Grant Agreement and Consortium Agreement and consequently are not negotiable. Only content in Annex 1 content is negotiable.

A template funding agreement is provided at RobMoSys Funding Agreement Template.

Please note that the rights and obligations contained in this Funding Agreement derived from the RobMoSys Grant Agreement and Consortium Agreement and consequently are not negotiable. Only content in Annex 1 content is negotiable.

Yes, as in Horizon 2020, indirect costs are eligible. You can add 25% of overheads to your direct costs. Please note that equipment costs are not eligible, all the necessary equipment (robotic platforms, etc.) are made available by third-parties themselves. The electronic tool in the open call submission platform will help you to properly calculate your budget.

Yes, third parties can receive pre-financing of up to 25%.

Third parties can receive pre-financing of up to 25%. Further payments will be made upon successful completion of milestones and/or deliverables as specified in the respective contract with CEA and measured against Key Performance Indicators (KPI).

We will be working with a traffic light system on the monitoring platform to visalize whether you are on track or further improvements are deemed necessary. This usually should be done within 2 weeks after submission of a deliverable / milestone.

Payment process might take up to four weeks.

ITP proposals suggest a limited but sharp set of individual KPIs, these KPIs will be fine-tuned during the preparation of the contract.

The funding is limited to 300,000€ for an ITP in total. There are no restrictions regarding the number of proposals in which an entity can participate. Please note that the funding for the beneficiary (as defined by the EC) will not exceed 250,000€ (even if a party participates in more than one ITP; for both calls in total). Restriction of shifts between partners in an ITP concerning this matter will be part of the contract.

Full open source contributions are preferred but not mandatory. However, we expect at least the models and their transformations to proprietary tools to be under an open source license that enables composability similar to proven platform projects like Eclipse.

The Intellectual Property Rights policy is part of the funding agreement between CEA and the third party. Please refer to paragraph 5 of the H2020 RobMoSys Funding Agreement (page 6f).

Because of the expected step change contributions, RobMoSys is looking for experiments which will be realized in a joint effort by preferably at least two partners offering complementary, multi-disciplinary competences that go beyond the mainstream robotics community; for example, robotics experts teaming up with software engineering people, or tool builders, or experts from automotive, aerospace, embedded, cyber physical systems.

If your organisation is large enough to cover this mix of competences internally, this is sufficient.

The Call welcomes consortia offering complementary, multi-disciplinary competences that go beyond the mainstream robotics community; for example, robotics experts teaming up with software engineering people, or tool builders, or experts from automotive, aerospace, embedded cyber physical systems. RobMoSys is offering another Brokerage Day on August 24, 2017 to find an appropriate partner for your idea. Moreover, we also offer an online tool for finding tandem partners on our website (please noe that you need to register yourself in order to acces full information on the profiles).

No, this is not possible. Consortium partners cannot be beneficiaries of third party funding. But there will have a set of Inter-project meetings to have a proper exchange between the ITPs and the core team.

No, this would result in a situation with conflict of interest for reasons involving economic interest, political or national affinity, family or emotional ties or any other shared interest. Therefore, those beneficiaries cannot apply.

Other entities who have some link (loose or not) to core consortium partners can apply. We will make sure that the evaluation process is completely independent and none of the above situations with conflict of interest will occur.

Although industry representation in your team is highly welcome, it is no prerequisite for a successful proposal. Evaluation is based on whether all required competences are represented in the team. Moreover, it is important to demonstrate usability in real-world scenarios and the industry-grade quality of their realisation.

In the first call, we are looking for models and tools, so basically digital artefacts. We do not require productive software in real world environments.

We prefer projects that illustrate their contribution in the domain of robot-centric motion, navigation and manipulation.

Within the platform concept, the First Open call focuses on composable software development (models, tools and meta-models) while the Second Open Call focuses on system-level through application pilots using the RobMoSys ecosystem.

More in detail, the First Open Call will focus on basic components, that is functional building blocks for motion, perception, real-world software stacks, navigation and manipulation. By the end of this first open call, it is expected that the community will already be able to benefit from industry-grade modelling tools supporting the creation of robotic applications that can be built by composing high quality composable models and associated software functions in the domains of motion, perception, navigation and manipulation.

The Second Open Call will focus on pilot cases, that is, application-centric systems. It is expected that pilot applications will be built out of the basic building blocks developed in the First Open Call, together with many more that have been developed in project-independent ways. Additional tooling features, however, will be needed, mainly with respect to validation capabilities, run-time execution and code generation towards specific middleware platforms. Once again prototypical software models and implementations, developed by core team members, will be enriched and improved during the Second Open Call.

Feedback from projects and teams will be constantly gathered to improve specifications and will be reported back to the Tier-1 Experts Group. This procedure will ensure flexibility and continuous interaction to maximize the quality and the impact of Open Call results. The results also will feed into the technical specifications for the second open call.

The members of the core consortium are responsible for kickstarting all specifications of meta-models with concrete contents, motivations and documentation. They will develop and publish a “living on-line document” (the RobMoSys Wiki [LINK] describing the methodology and the models; this document also offers a discussion infrastructure for the community. Similarly, the core consortium is in charge of the development of prototypical proof-of concept (PoC) software libraries and tooling.

The open call applicants are expected to contribute to, to extend, to improve and to use the models and tooling, to maximise the influx of knowledge and brains.

Their role is to identify the best tools already available, to adjust them, to validate the results in the best application areas and to establish benchmarks. They shall also assist in providing the access to integrated sets of common tool chains and real-world test installations to support the development of complex robotics systems.

An ITP, a so-called Integrated Technical Project, is a sub-project within the scope of the RobMoSys Integration Action, selected and contracted under an open-call.

ROSIN (ROS-Industrial quality-assured robot software components) aims at enhancing the quality of ROS-Industrial, both the framework and its content, via continuous integration and code-testing in order to push robotics by broad availability of high-quality software.

RobMoSys (Composable Models and Software for Robotics) focusses on a model-driven and composition-oriented approach to system integration to establish a European robotics software ecosystem.

ROSIN aims to enhance the quality of existing software through software quality assurance, while RobMoSys addresses better quality of robotics software right from the beginning via providing adequate structures as a fundament that improve the quality and composability of building blocks.

We strongly advise you to focus on the quality of a single proposal rather than to submit a series of proposals with different scopes. Please keep in mind that your maximum funding is fixed over all submissions. In case more than one of your proposals were to be selected, you would have to withdraw from your other partners.

Yes, the pilots can be provided to project contributors to support designing, developing, testing, benchmarking and demonstrating their contribution.

Moreover, we are able to offer the services and equipment of the Robotics Innovation Facilities (RIF Paris-Saclay, CEA) and Centres of Competence (CoC in Munich, TUM) to stimulate the developments coordinated by the project.

Pilots span different domains and different kind of applications (and hence requirements), centred around the core applications of “navigation” and “(mobile) manipulation”. We as core consortium provides a set of concrete Pilot applications to kick-start implementations. Find out more about these pilots at and in the technical wiki at

RobMoSys is a joint effort with close involvement of the robotics community to ensure delivery of adequate structures and supporting tools. The RobMoSys core consortium therefore needs your input and contributions! RobMoSys needs the support of the robotics community to identify and realize the necessary structures to enable composition in a robotics ecosystem. We have funding to do so in Open Calls.

Delivering components that can be composed to systems is not the main aim of RobMoSys. The aim of RobMoSys is to provide structures and tools such that these components can be supplied and composed in an ecosystem.

Check our basic commercial User stories , the technical user stories in our wiki as well as Composition in an Ecosystem.

The core concepts are already now usable. A tooling baseline also is already provided.

Please also refer to the technical FAQ for an answer to the question “When will RobMoSys be ready to use?“


The schedule will be the following:

  • Opening 10th July 2017 – closing 9th October 2017 (5 pm Brussels time)
  • Evaluation & Physical panel meeting between October and December 2017
  • Results & Information to applicants in December 2017
  • Contract negotiation and signature in January / February 2018
  • Start of projects March 2018

So we plan to inform you in December on the outcome of the evaluation.

Deadline for pre-proposal submission is September 11, 2017, 17:00 Brussels time.

Pre-proposal should be based on the Proposal Template, but only Excellence and Impact sections are obligatory.

No, there is no requirement to have an end-user in the consortium and having and end-user in your consortium does not automatically increase the chances that your proposal is accepted. What is most relevant is that you have all relevant competences represented in your team.

There is no criterium to form multi-national consortia. In the framework of RobMoSys ITPs, you can opt for mono-national consortia without reducing your chances to get selected.

Yes, the funding constraint of € 250.000 per entity (PIC) is valid for the sum of the two calls. So if you plan to have a follow up-proposal in the second call, you should not use your full budget already in the second call.

If you only team up with one partner and plan to do so again the next call, you should have in mind to stay below the funding maximum per project of € 300.000.

The entity is identified by the PIC, thus the funding constraint of € 250.000 for large institutions, like e.g. Fraunhofer, is summed up for all sub-entities (institutes).

More general questions that could be of overall interest will be published in the FAQ section. If you have more in-depth technical or scientific questions that might even be related to a concrete project idea, we will keep it confidential, of course.

For the proposal, a budget calculation form is included in the open call platform. Please enter your figures there. Once you select an institution, the budget section is available to fill. And there is a budget subsection per institution added. It is important that you select if your institution is for profit (75%) or non-for-profit (100%).
After submission, you will receive by email an excel sheet with the proposed budget (for your own records). There is no need to inclue the budget information in the proposal template.

For the pre-proposal, it is not necessary to include the budget.

It is part of the robotics domain, but RobMoSys is not focusing on autonomous driving as application domain. Of course, all platform-level aspects are, such as the motion stack and information and software architectures.

Nevertheless, outcomes of RobMoSys are expected to be of high relevance for autonomous driving as well as we consider input from the automotive domain being of high relevance for robotics. The contributions need to make a difference in robotics in general and should not be specialized to autonomous driving.

We see no difference in the “platform” between application of it in space contexts or other contexts. But, as the guide for applicants says, the size of the potential users group(s) is a relevant criteria. Adequateness in any means with respect to civilian applications is thus relevant (solutions for space robotics applications are typically not affordable for civilan applications).

Horizon 2020 is open to the world, and this is also valid for the RobMoSys Open Call. Partners from outside Europe can fully contribute to and benefit from Europe’s research and innovation capacity, but will need to cover their participation costs in RobMoSys with their own funds.

During the project runtime, snapshots of the wiki are taken to freeze it. The snapshots provide a stable reference to use in project proposals. The contractual agreement will be based on these snapshots.

Nevertheless, we of course encourage you to trace the updates in the live Wiki for selected pages of your interest (an updated changelog helps you easily finding new contents).

The contractual agreement will be based on static wiki snapshots that you can rely on. If tooling is adapted during the runtime of your project, you are free to adapt to it, but you are not obliged to do so.

We are currently investigation the options to combine the Inter ITP workshops with a Summer School (or Spring School) and to thus make them also accessible to interested “outsiders” that want to follow and contribute to the RobMoSys approach without being “officially” involved.

We will also continue to organize open workshops (e.g. at ERF) and presentations ( automatica and international conferences).

The RobMoSys website and newsletters will keep you posted.

The outcome ideally should be a combination of models, meta-models, description and tools.

Their step change will be demonstrated by pilot applications which will be built using the above outcomes.

There are more frequently asked questions related to technical aspects, like the following

  • When will RobMoSys be ready to use?
  • Does providing a model for my building block mean that I have to expose all my IP in that model?
  • The RobMoSys structures seem to be complex. What’s in for me as a user?
  • Where can I find the RobMoSys metamodel?
  • What is a component in RobMoSys?
  • What is the difference between composition and integration?
  • I am a system integrator; where to start?
  • I am a technology provider; where to start?
  • I am a tooling provider; where to start?
  • I am new to MDSE, DSLs, and modeling. Where can I read about it?
  • Can I use RobMoSys with <insert robotics framework here>?
  • ROS is in very widespread use; why does RobMoSys not build upon ROS?

You can find more questions and the related answers in our wiki at

Please subscribe to our newsletter to get information on important updates.