Skip to content

Exchange models securely between partners in a collaboration


1. Introduction

Traditionally the collaboration between partners did not include the exchange of full models between partners, but now companies need to collaborate more closely in the product design phase. In order to optimise products as much as possible and to get an increased speed of cooperation, a need for the exchange of models has arisen. Two of the problems with exchanging models are (a) the size of the data that needs to be exchanged stresses the data bandwidth to the limit, and (b) confidentiality and intellectual property rights need to be preserved.

The surrogate modelling technique implemented in the MACROS product gives a solution for this problem.

2. Use of MACROS in the process of exchanging data between partners

MACROS is used in this process as follows:

  1. Discrete data instead of full dataset are sent by partner A to partner B: both the size of data is reduced and the confidentiality and IPR of the full dataset is insured.
  2. Partner B creates a surrogate model of the dataset with the MACROS software.
  3. Partner B uses this surrogate model in his calculations

A surrogate model is an approximation of the original dataset. Partner B creates this approximative model using the data that partner A has sent to him. With a powerful enough approximation method, this process is sufficiently accurate.

3. Industrial use case

We present a use case that concerns the modelling of an helicopter engine compartment, with coupled aerothermal modelling of the engine integrated into the helicopter engine bay. The thermal model of the engine is simulated by the thermal department of the engine manufacturer (Turbomeca), the thermal model of the engine compartment is simulated by the thermal department of the helicopter manufacturer (Eurocopter), and the full aerothermic model of the engine compartment is simulated by the aerodynamic department of the helicopter manufacturer.

The modelling process has several simulation steps, that involve data exchange between three parties:

  • Aerodynamic department of the helicopter manufacturer
  • Thermal department of the helicopter manufacturer
  • Thermal department of the engine manufacturer

The data exchange between the thermal departments of helicopter (Eurocopter) and engine manufacturer (Turbomeca) is sensitive to IPR and data size issues. The engine manufacturer owns the full engine model, and will not give it to the helicopter manufacturer. In order to safeguard its IPR and to reduce the size of the data, the engine manufacturer just sends the heat rejection in a discrete set of flying points to the helicopter manufacturer. A flying point is defined by engine power, external air temperature, heat rejection value, position, and altitude. Since the flying points delivered by the engine manufacturer do not always match to the flying points needed by the helicopter manufacturer, he needs to create an approximate or surrogate engine model, to be able to predict engine behaviour in the whole flying domain.

With the MACROS tool, an engine surrogate model is constructed, using data from the engine manufacturer. The data consists of a set of curves for each flying point. The curves concern the engine skin temperature as function of space variable x. The surrogate models were created on the basis of these input data, and are then used to find a heat rejection value for an arbitrary flying point. This heat rejection value is then used by the helicopter manufacturer to perform simulations of the engine compartment model and of the aero-thermal model.

4. Conclusion

MACROS gives a solution for preserving confidentiality and IPR and for reducing data size in the exchange of data models. A model owner can give discrete data points to his partner, and the partner then uses surrogate models instead of the full model to get the data he needs.

Ref: MACROS is developed and distributed by Datadvance. IRIAS was involved for creation of the surrogate model. The Eurocopter-Turbomeca use case was developed in the CRESCENDO project.

From → PLM

Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: