The project starts with the specification of a scenario. We call scenario the description of a use case for a particular sets of robots implementing some particular tasks.

  1. From this use-case, we create a formal description of the scenario, in particular, we define the three following artefacts:
    1. A set of standardised types and their relationships: here we identify the models and the set of data types to be used in the scenario. Mainly we are concerned here by the knowledge exchanged inside the robotic systems and between the different robots through communication links;
    2. An architecture model which defines the relations between the different objects of a scenario and their relationship, the behaviours of the objects and the data flows between the objects;
    3. A challenge that is a subset of this formalized scenario.
  2. In coordination with the scenario formalisation activity described above, we implement the different behaviours needed to model the robots, their capabilities and the associated environment. The link with the formalisation is made by generating the data types and behaviour interfaces from their formal descriptions.
  3. Once we have a challenge and its associated set of implemented behaviours have been defined, we generate from the formal architecture a challenge simulation.
  4. These challenge simulations are then be delivered to those entering the competitions;
  5. From the results of the challenges, methods from some of those competitors will be selected and ported in real environment…

Considering these different tasks, we organised the project around the three following technical work packages:

  • WP1: Formalisation of robotics scenarios and implementation of their associated behaviours.
  • WP2: Tooling for ontology modelling; architecture support, and simulation generation.
  • WP3: Settings of the different challenges and evaluation of results in a representative environment.

These three work packages are technical ones implementing the core of the project. As denoted in figure 5, they are completed with two work packages. The former one, WP0 (called Management) is concerned with project management. The second one, WP4 (called Dissemination, exploitation and synthesis) deals with both following concerns:

  • Dissemination: in order for the project’s results and software to be used, a dissemination methodology has to be created and implemented providing the portal as  presented above. The “GDR Robotique” web site will introduce pages that will allow those subscribed to download tools and existing domain specific elements. This web site will also allow users to upload modifications. This task is viewed as essential by the partners as it conditions the success of the project;
  • Exploitation: it is trivial to state that properties’ rights can lead to stalemate when considering use of results. As the work to be done means to share results and tools, the partners introduce a task totally dedicated to these problems. Moreover, the consortium will no longer exists after the project end and this task will define how the outputs of  the project will live and grow after the end of the project.