UAF — Operational Exchange/Resource Interaction for triggering Transitions in StateMachines

If I want to populate an L3 diagram I am asked for an operational exchange item and this quickly ends up in a selection of information elements.
When I create state machines the only trigger I can make use of is a signal event if I need to handle asynchronous information flowe. This to me indicates that the only way to tie the two together would be to create the same amount of information elements as there are signals and allow the signal to have a single parameter typed by the information element. This would allow me to create a trigger based on the signal and also get an operational exchange item that points to the information element by the same name.

To me this seems somewhat redundant. The question is therefore whether exchange should also be allowed to be a signal in order to open up the possibility of a consistent way of dealing with with state machines and other types of diagrams.

*Add signals to UAFP *

Add signals to UAFP at the operational and resource levels.
Add descriptions to the elements
Modify relevant diagrams