Hi,

If I understand your question correctly the IRD can execute two different functions, but only one at a time:

• Demodulator + Decoder
• IP input + Decoder

If the above is correct, then I would suggest that you have two resource pools:

• Demodulator
• Decoder

The IRD can be added to both pools with a concurrency of 1, this way you can define on each of the pools different scheduling configuration settings for the different functions/pools (e.g. different automated actions) while ensuring the IRD can only be booked to execute one function at a time.

In case you also have cases where two devices are needed to do demodulation and decoding, the operator will still have to add two nodes (one of the demodulators pool and one of the decoders pool). So, the operator still needs to have the knowledge which demodulators can do both demodulating and decoding at the same time. For this you could use a naming convention on the resource.

The ultimate solution that would cover your needs would be the 'Media Functions' feature that is on our backlog. A Media Function lets you describe the functional building blocks that can be used in your signal flow while they are decoupled from the actual resource usage. Based on the selected Media Function and the configuration provided by the operator, the resource usage is calculated and added by predefined code. This functionality is not going to be available in the short near future (coming months), but is one of our highest priorities to work towards. We are currently preparing the solution by introducing 'Dynamic input arguments for automated actions' and 'Edit job mode to allow multiple changes to be pushed at once' as steppingstones towards the Media Functions feature.