Today, system designs and their management are crucial parts of most systems development processes. To stay competitive engineers from several expertise domains use Model-Based engineering (MBE) to design the systems they intend to implement in order to specify, test, simulate, validate and iterate their design as soon as possible. System designs are living and evolving artefacts this imply to be able to manage them in an efficient and agile way. The MONDO FP7 EU project aims to comprehensively tackle the challenge of scalability in system design and management by developing the theoretical foundations and an open-source implementation of a platform and will offer to Model-Driven Engineering (MDE) users advanced flexibility in their different modeling approaches. This paper describes three different industrial demonstrators and three different modelling approaches that will be utilised to evaluate the capabilities of the MONDO technologies. For each demonstrator the interests of the industrial user partners are described along with their current and desired improvements in technologies to support MBE in a much more flexible way. Specific evaluation scenarios are specified for each of the targeted industrial domains as well.
Gen AI in Business - Global Trends Report 2024.pdf
Flexible and Scalable Modelling in the MONDO Project: 3 Industrial Case Studies @ XM 2014
1. 29th September, 2014
17th International Conference on
Model Driven Engineering Languages & Systems
Alessandra Bagnato, Etienne Brosse, Andrey Sadovykh, Pedro Maló,
Salvador Trujillo, Xabier Mendialdua and Xabier de Carlos
XM 2014 - Extreme Modeling
Workshop at MoDELS 2014
2. The MONDO Project
◦ Motivation
◦ Overview
Case Studies:
1. The Modelling Tool Domain
2. The Open-BIM Construction Domain
3. The Offshore Wind Power Domain
Conclusion and Future Work
2
3. Achieving scalability in MDE involves:
Constructing large models and
associated DSLs.
Enabling collaborative development.
Querying and transforming
large-scale models.
Efficiently storing, indexing and
retrieving large models.
3
4. MONDO technologies
will support scalable:
◦ Queries and
transformations
◦ DSLs
◦ Collaborative modelling
◦ Persistence
Contribution:
◦ Advances within project
page:
www.mondo-project.org
◦ License open-source
software under EPL
◦ Industrial partners
proprietary extensions.
4
6. The Modelling Tool Domain
The Open-BIM Construction
Domain
The Offshore Wind Power Domain
6
7.
8. The role of SOFTEAM
◦ Apply MONDO technologies within
the SOFTEAM Open Source Modelio
(www.modelio.org)
◦ MONDO technologies will be applied
using different Modelio modules and
standards benefiting multiple
market sectors and users.
What SOFTEAM expects from
MONDO
◦ Enhance Modelio capabilities to
manage large-scale models:
scalable model persistence and
querying.
8
9. Evaluation
◦ In-house modelling applications
◦ Model: Voyages Discount
application (developed using
TOGAF modelling)
Voyages Discount application:
service provider proposing a list
of unsold package tours from
travel agencies.
Model provides a complicated
business process that requires
multiple stockholders
/ professionals communications
◦ MONDO technologies evaluated using this model in a
collaborative environment composed by a large team.
9
10. Scenario 1: MONDO framework querying facility
◦ Purpose: comparison of the query facilities and performances
provided by both Modelio and MONDO frameworks.
◦ Expected benefits: improve the Modelio querying facilities to
better meet end user’s needs in terms of performance (time and
memory).
10
11. Scenario 2: MONDO framework collaborative
modelling
◦ Purpose: integrate the MONDO technologies for supporting large
and complex models and large collaborating teams.
◦ Expected benefits: improve end users’ experience of modelling
gaining speed in the overall design in large team and large
model context.
11
12. Scenario 3: MONDO support in M2T trans.
◦ Purpose: specification and execution of M2T transformations.
Benchmarking and performance analysis: M2T transformations
within Modelio.
◦ Expected benefits: improve the scalability and performance of
Modelio M2T transformations in a large model context.
12
13. Scenario 4: MONDO support in M2M trans.
◦ Purpose: compare the M2M transformation support by both
frameworks. Benchmarking and performance analysis: M2M
transformations inside Modelio and EMF UML2 XMI import/export
facilities.
◦ Expected benefits: improve the scalability and performances of
Modelio M2M transformations in a large model context
by reducing the amount of needed time and
resources .
13
14.
15. The role of UNINOVA
◦ Research and development institute
◦ Well-known activities on data and interoperability, at European
and National level
◦ Special focus on the Architecture, Engineering, Construction and
Operations (AECO) domains.
What UNINOVA expects from MONDO
◦ Enable an efficient management and exploitation of Open-BIM
large-to-huge-scale data models
using best-of-breed MBE solutions
incorporating AECO domain knowledge for the
best possibly experience and performance.
16
16. Scenario 1: File- (huge-)
based collaboration
◦ Purpose: enable model designers to
work on separate models and share
models (large files) having model
coordination
◦ Expected benefits: enable off-line work on part of a large
model, but having all parts promptly merged together
within a single BIM model
17
(*) Picture included courtesy of “Use of IFC Model Servers: Modelling
Collaboration Possibilities in Practice” Kaj A. Jørgensen,
Jørn Skauge, Per Christiansson, Kjeld Svidt,
Kristian, Birch Sørensen,
John Mitchell
May 2008
17. Scenario 2: Shared- (huge-) model collaboration
◦ Purpose: all users (model designers,
model coordinator, model clients) interact
via a large shared-model in Model Server.
◦ Expected benefits: efficient
querying/updating on
large-sized BIM models
enabling fruitful extreme
BIM modelling collaboration.
18
(*) Picture included courtesy of “Use of IFC Model Servers: Modelling
Collaboration Possibilities in Practice” Kaj A. Jørgensen,
Jørn Skauge, Per Christiansson, Kjeld Svidt,
Kristian, Birch Sørensen,
John Mitchell
May 2008
18. Scenario 3: Quantity
Take-Off in huge BIM models
◦ Purpose: QTO are a detailed
measurement of the materials
needed to complete a
construction project used to
format a bid. BIM provides a
direct way to extract the quantities of a building by doing a
complex query to the large BIM model.
◦ Expected benefits: Ability to traverse large BIM data model
with outstanding performance (on-the-fly) to generate
complex QTO reports making it possible to improve model
for best quantities arrangement (thus best cost solution).
19
19.
20. The role of IKERLAN
◦ Modelling Control Systems of Wind Turbines: specify behaviour of
of the wind turbines’ control system .
◦ Own modelling tools
Open-source Eclipse modelling technology
Not conceived to be used in an agile and
collaborative manner.
What IKERLAN expects from MONDO
◦ Provide collaboration in the modelling tool
◦ Add new features: concurrent model edition,
partial load of models, advanced querying capabilities.
◦ Support modelling activities in out-of-the-office
environments: modelling from mobile devices.
◦ Future: use tools in other domains.
21
21. Scenario 1: Wind turbine control system
collaborative modelling
◦ Purpose: provide agile development to the wind turbine
control system engineers to be able to specify models
concurrently/together.
◦ Expected benefits:
add teamworking capabilities to the modelling tool.
a more flexible wind turbine control system
development.
improve communication among engineers.
22
22. Scenario 2: Partial-load / Load-on-demand
of subsystems’ related models
◦ Purpose: allow engineers to be able to manage
partially specific parts of the model.
◦ Expected benefits: agility and flexibility through
the partial model validation.
23
23. Scenario 3: Modelling from mobile devices
◦ Purpose: use models in the common activities that
nowadays are not used on grounds of non-comfort.
E.G. Field maintenance
◦ Expected benefits:
allow different teams
(development, customization, installation
and maintenance) to work over the
same model.
Provide adapted modelling tools/views to each team
(e.g. mobile modelling)
24
24. MONDO technologies: benefits to the
software development on industry
MONDO technologies: extend MODELIO
◦ Large-scale models
◦ Collaborative and agile development
◦ To be used within three case studies
MONDO evaluation:
for October 2015
◦ Qualitative and quantitative
25
25.
26. 29th September, 2014
17th International Conference on
Model Driven Engineering Languages & Systems
Alessandra Bagnato, Etienne Brosse, Andrey Sadovykh, Pedro Maló,
Salvador Trujillo, Xabier Mendialdua and Xabier de Carlos
Editor's Notes
The role of SOFTEAM
- SOFTEAM aims at applying MONDO technologies within the SOFTEAM Open Source Modelio Modelling tool (www.modelio.org)
- MONDO technologies will be applied to models using different Modelio modules and standards benefiting multiple market sectors and users.
What SOFTEAM expects from MONDO
- The MONDO technologies are expected to make possible to enhance Modelio capabilities to manage very large models using different Modelio modules. In particular, the MONDO results will enhance the Modelio Modeling Tool capabilities on scalable model persistence and querying.
SOFTEAM will evaluate the MONDO improvements through in-house modelling applications.
The primary application for evaluation is called Voyages Discount, which uses TOGAF modelling, TOGAF modelling improves business efficiency ensuring consistent standards, methods, and communication among enterprise architecture professionals.
The model describes the situation of Voyages Discount, which is a service provider proposing to consumers a list of unsold package tours from travel agencies.
The model has been chosen since it provides a complicated business process that required multiple stockholders / professionals communications to be completed.
MONDO technologies will be evaluated within this model when dealing with a large team and much collaboration.
Scenario 1: MONDO framework querying facility
Purpose: This scenario focusses on the comparison of the query facilities and performances provided by both Modelio and MONDO frameworks.
Expected benefits: MONDO technology will improve the Modelio querying facilities to better meet end user’s needs in terms of performance (time and memory).
Scenario 2: MONDO framework collaborative modelling
Purpose: This scenario aims at integrating the MONDO technologies within the Modelio modelling tool for supporting large and complex models and large collaborating teams.
Expected benefits: MONDO technology will improve end users’ experience of modelling gaining speed in the overall design in large team and large model context.
Scenario 3: MONDO framework support in transforming model to text
Purpose: Specification and execution of ModelToText transformations are the aim of this third evaluation scenario. In particular, Modelio document publisher extension provides by default a set of existing transformation including the analysis and design one’s which will be used as benchmark.
Expected benefits: MONDO technology will improve the scalability and performances of Modelio ModelToText transformations in a large model context.
Scenario 4: MONDO support in transforming model to model
Purpose: The purpose of this scenario is to compare the ModelToModel transformation support by both frameworks. Among all existing ModelToModel transformation specified inside Modelio or its extension, the performance analysis will take EMF UML2 XMI import/export facilities as reference.
Expected benefits: MONDO technology will improve the scalability and performances of Modelio ModelToModel transformations in a large model context by reducing the amount of needed time and resources .
Modelio models size: larger than 400 MB.
Number of Modelio users that typically work in parallel on the same model or fragment of model: 20 engineers.
Number of documentations generated: i.e. existing ModelToText transformations are performed: 2 (Requirements and AnalysisAndDesign ).
Number of Jython scripts are used to quickly query larger models and extract relevant informations: 1
Number of ModelToModel transformations that have been defined and are applied to create models related to existing specification:
Modelio2Eclipse ( import and export XMI),
Modelio2Modelio and in particular transform
TOGAF Architectural model into modelio Java model,
TOGAF Business model into message model,
TOGAF Business model into database model.
Number of target managed by ModelToText transformation: 5 respectively Model2Java, Model2MSword, Model2OpenOffice, Model2HTML, ModelToSQL.
Number of users collaborating simultaneously on the same fragment or on the same model elements: 20.
Time for change propagation and notification among concurrent users on class name change: less than 1 sec.
Time for query execution on the execution of transformations for code generation on finding a class name: less than 1 sec.
Number of heterogeneous visualisation managed: TOGAF, UML, BPMN, Analyst, Java, DataBase modelling
Maximum number of elements that can be displayed in a diagram: 40
The role of UNINOVA
UNINOVA is a research and development institute, with well-known activities on data and interoperability, at European and National level, with a special focus on the Architecture, Engineering, Construction and Operations (AECO) domains.
What UNINOVA expects from MONDO
MONDO to enable an efficient management and exploitation of Open-BIM(*) large-to-huge-scale data models by both using best-of-breed MBE solutions and incorporating AECO domain knowledge for the best possibly experience and performance.
(*) Open-BIM: youtu.be/2m_IL99WOzQ
----Scenario 1----
Purpose:
The file-based collaboration scenario is one where model designers work on separate models and share models (as huge files) with a model coordinator (that aggregates models altogether) and then with some model clients. Here the Heterogeneous Model Server exists especially at the Model Coordinator that can “upload” models and merge models together as well as doing some validations and checks to provided models. Data models are then exported in designated formats to be shared with model clients.
Benefits:
Technology provided by MONDO will allow designers & engineers to work on a specific part of the model, but with the added flexibility of having all parts merged together within a single model. Technology is to allow users to perform off-line work and then be able to readily reconvene for review and development.
(*) “Model servers are special database systems, by which multiple users can share building models. Users can be granted access rights to a model server and can then, as a basic functionality, upload models to a server and download models from a server. In addition, model servers potentially provide high level functions of coordination and project life cycle management and operational data management” [Plume 2007] [InPro 2008]
A Model Server provides
supports for modelling, storing, sharing, inspect, visualise, and operate BIM model
----Scenario 2----
Purpose:
The shared-model collaboration scenario is one where all users (model designers, model, model coordinator, model clients) interact using a share-model hosted in a Model Server. Users are provided with data models views of the huge data models in the Model Server and can check-in/check-off model parts for off-line manipulation
Benefits:
MONDO technology will allow system engineers to work only with specific parts of the model, with the added flexibility of providing features that allow partial load and load/unload on demand of parts of the model where different subsystems are specified.
----Scenario 3----
Purpose:
Quantity take-off’s (QTO) is a key process in construction. QTO are a detailed measurement of the materials needed to complete a construction project. These measurements are used to format a bid on the scope of construction. Estimators review drawings and specifications to find these quantities, which is a very time consuming, and erroneous process. BIM provides a direct way to extract the quantities of a building. It is done using a complex query to the BIM model.
Benefits:
On huge BIM data models performing QTO is a nontrivial task due to the complexity of the query and need to traverse the whole of the data model.
The scenario tests then the ability of MONDO to report out of large-to-huge data models using complex queries situations.[10] [11] [12]
Scenario 1
------------
El objetivo es pasar de un escenario en el que cada modelador trabaja de manera aislada modelando el comportamiento del control del aerogenerador a un escenario en el que varios ingenieros puedan trabajar conjuntamente.
El proceso de desarrollo del sistema de control de un aerogenerador es un proceso en el que participan multiples ingenieros.
Las herramientas de modelado a día de hoy no están diseñadas para que todos estos ingenieros puedan trabajar conjuntamente sobre el mismo modelos. Son herramientas desarrolladas para que cada ingeniero pueda trabajar aislado y con su modelo. El modelo se comparte a través de un repositorio, pero la fusión de modelos editados por distintos ingenieros y la resolución de los conflictos que puedan surgir es una actividad manual que puede llevar mucho tiempo y trabajo y puede ser error prone.
Los beneficios esperados de los resultados de este escenario es que los ingenieros puedan trabajar sobre el mismo modelo (concurrentemente o no), eliminando así la necesidad de fusionar varios modelos editados por distintos ingenieros, minimizandose los conflictos y disponiendo de herramientas que permitan resolver los conflictos.
En definitiva, disponer de herramientas que faciliten el trabajo en equipo y flexibilicen el proceso de desarrollo de sistemas de control (en este caso para aerogeneradores, pero también aplicable a otros dominios).
Otra de las mejoras con estas herramientas es la mejora en la comunicación entre ingenieros al trabajar todos ellos al mismo tiempo sobre el mismo modelo, pudiendo ver los cambios incorporados al modelo por otros ingenieros.
Scenario 2
------------
A menudo el trabajo de un ingeniero se centra en diseñar (en este caso modelar) el comportamiento del control de uno de los múltiples subsistemas que conforman el aerogenerador. Un subsistema es solo una pequeña parte de un modelo completo de aerogenerador. Pero el ingeniero necesita disponer de mecanismos/herramientas que le faciliten el trabajo permitiéndole seleccionar un subsistema y proporcionándole los mecanismos para trabajar y validar un subsistema de manera aislada (con toda la información del modelo necesaria para realizar su trabajo).
El beneficio que se busca es que el modelo puede ser desarrollado y validado de manera parcial por distintos ingenieros, ya que aunque todos trabajan sobre el mismo modelo cada uno puede seleccionar la parte que necesita para llevar a cabo su trabajo.
Y que disponga de mecanismos para cargar y descargar distintas partes del modelo para llevar a cabo sus trabajo.
El propósito de este escenario es poder trabajar con modelos utilizando para ello dispositivos móviles.
Con ello se desea poder llegar a aplicar estas tecnologías en entornos de trabajo ”no cómodos”, en los que a día de hoy no se utilizan debido a su incomodidad . Para, de esta manera, poder facilitar al personal que realiza tareas de mantenimiento en un aerogenerador además de poder monitorizar el comportamiento del sistemas de control poder incorporar pequeños cambios (ajuste de valores de parámetros, desactivación de algoritmos de control ,…) en el sistema de control, todo ello en escenarios perfectamente delimitados y controlados.
Los beneficios esperados es que los distintos equipos que trabajan con el control: equipo de desarrollo, el de personalización, el de instalación y puesta a punto y el de mantenimiento puedan trabajar con un mismo modelo del control y que toda la evolución del modelo a lo largo de los distintos procesos esté registrada y esté disponible para los distintos stakeholders.