The vision of RobMoSys is to create better models, as the basis for better tools and better software, which then allow to build better robotic systems. To not just let this vision remain a dream, a broad uptake by the robotics community is needed.

Watch our short video “RobMoSys explained: What is the aim of RobMoSys?” for a quick introduction to the core idea of RobMoSys.

So what is in for you? Why should you as a software developer, why should you as a system builder, why should you as a decision maker in your company decide to use the RobMoSys approach for further system developments and build your applications following our methodology?

From a commercial perspective, main incentives of the RobMoSys approach are:

  • Reduction of development time, resulting both in
    • reduced costs and
    • shorter time to market
  • Systems should become more easily re-usableand, as a consequence, should
  • Enable larger production volumesof components and systems (using flexible production units)
  • Base componentscould be commoditised
  • Systems will become certifyable
  • Safetyof systems will be predictable
  • Easier reconfigurablesystems will allow for mass customization of products
  • Better comparabilityof systems and components will be enabled through appropriate metrics (benchmarking)

 

 

 

 

 

Of course, the benefits of the RobMoSys approach depend, to various degrees, on your:

  • Role in the robotics value chain
    (end-user, system integrator, robot manufacturer, component supplier, etc.)
  • Field of application
    (industry, medical, agriculture, etc.)
  • Function in the company
    (CEO, manager, software developer, engineer, etc.)
  • Role in the RobMoSys ecosystems
    ( Behavior Developer, Function Developer, Safety Engineer, System Builder, etc.)
Have a look at our user-stories for a user-perspective on the aims of RobMoSys.

 

From a technical perspective, the benefits of the RobMoSys methodology and tools will lead to:

  • simplifying the setupand configuration of hardware and software
  • Easy integrationand extension of software tool-chains and eco-systems in industrial production setups in a vendor-neutral style
  • composableand replaceable components
  • predictableand traceable properties
  • reusablesystems
  • ease of useby simplifying the entrance and usability of software components
  • reliably quality of service
  • standardizationof models and interfaces
  • certifyablesystems

 

 

 

 

If you want to go more into details, you can also read our technical user-stories.

 

Pilots are used to valide the methodology and to demonstrate the use of its approach through the development of real robot applications targeted at real customers, to illustrate vendor-neutral and environment-neutral composition of systems. Pilots span different domains and different kind of applications and requirements – centered around navigation and (mobile) manipulation.