Having an Industrial Connection (required by the UI), or at least tag bindings in Composer (required by the Excel import method) would be ideal. Either of these should be enough.
There is a third way you could look into, it's not perfect but it may be a sufficient workaround. You're saying you're using subscriptions to send values into the required properties. Well we can extend this and I believe everything can work with this. Here is how I would do it :
- Use the Excel import method to create the Attributes you want. This will let you create alarms against them and let you use the UI to prepare the asset cards.
- Then use your subscription to send the values into those properties' valuestream. Alarms read valuestream.
- Use the Configuration -> Equipment screen, the Asset Monitoring tab, to select the attributes you want to see in the asset cards.
- This will set up the AMUAttributeX_MCC properties (names, colours), but the values will be missing at this point.
- Then use your subscription to send the values into the values (not valuestream) of the AMUAttributeXValue_MCC properties. The asset cards read the current value of the properties, not valuestream.
- Do the same for property RunningStatus_MCC, which is a boolean and used for the down/running status in the asset card.
I believe this should be enough to make both the alarms & asset cards work. The bad side of this is the required workaround steps and also that those steps will need to be repeated every time you change the list of attributes in the Asset Card configuration screen.
I will check with my team if they know a way to make either Industrial Connection or the tag binding work, as those would be much easier to use and be better supported.