The Operational/Resource/Service Exchanges can be inherited, aggregated, or composed. You can redefine the inherited flows.

You can see the inherited, aggregated, and composed exchanges in:

The simplified scenarios illustrating the Aggregation and Inherited Exchanges are described in the following cases:

Case 1. Aggregated Exchanges

Let's say, we have Operational Performers Helicopter and Signal Receiver related to the Operational Exchange Reported Condition. Then we draw an association between Medical Assistance and Signal Receiver. In this case, the drawn association can realize the Reported Condition exchange, since the Operational Performer Medical Assistance aggregates the Operational Performer Helicopter.

If Composition is used instead of Aggregation to connect Medical Assistance and Helicopter, the Exchanges will be collected the same way as in the Aggregation case.


 Aggregation of information flow

To hide aggregated exchanges in dialogs

  1. Click Options > Project.
  2. In the Project Options dialog, select General > UAF.
  3. Set the Respect UAF Information Flows on Aggregation property value to false.


  • The exchange is not created for the drawn association, it is only realized.
  • The realization of the exchange will be removed from the association when Aggregation or Exchange is removed.


All the aggregated exchanges can also be seen in the role-based connectivity tables. The aggregated exchange rows are displayed in gray. 


To see the aggregated exchanges

  1. On the table toolbar, select Show Rows.
  2. In the open menu, click the Aggregated Operational Exchange or Resource Exchange command.

Case 2. Inherited Exchanges

Let's say, we have an Operational Performers Search Node and Place Of Safety related to the Operational Exchange Warning Order. The Operational Performer Aircraft specifies the Operational Performer Search Node. Then we draw an association between Aircraft and Place Of Safety. In this case, the drawn association inherits the Operational Exchange information that can be realized and redefined.

Let's realize the Operational Exchange. We can do this in two ways:


To hide inherited exchanges in dialogs

  1. Click Options > Project.
  2. In the Project Options dialog, select General > UAF.
  3. Set the Respect UAF Information Flows on Generalization property value to false.


  • The exchange is not created for the drawn association, it is only realized.
  • The realization of the exchange will be removed from the association when Generalization or Exchange is removed.


All the inherited exchanges can also be seen in the role-based connectivity tables. The inherited exchange rows are displayed in gray. 


To see the inherited exchanges

  1. On the table toolbar, select Show Rows.
  2. In the open menu, click the Inherited Operational Exchange or Resource Exchange command.

When we have the inherited Operational Exchange, we can redefine it. This means, that the inherited Operational Exchange will be copied together with the information such as Actual Measurements, Conveyed Items, Documentation. The new Operational Exchange will be created in the model.

The redefinition of Operational Exchange Warning Order

To redefine the Operational Exchange

  1.  In the Operational Exchange Manager dialog, select the inherited Operational Exchange and click the Redefine button. The new Operational Exchange is created.

All the information that comes from the inherited exchange when redefining it can be modified in the model.



Related pages