Asset Framework in Ignition to support browsing and swapping assets in Seeq?

Hi,

Curious to see if there are any other Ignition historian users here that run Seeq on top of it?
also I'm interested to see if in some way you can build up an asset framework (like Pi) within Ignition to use friendly names for tags that reoccur in other assets in your asset tree.

We have been experimenting with UDT's but we did not get the desired result yet.

kr,

Jan

Hi,
Looks to me that it's more related to Seeq than to Ignition. When using asset modelization with Canary Historian, it's all within Canary (virtual views).

But I'm interested in your finding...

In Seeq you can also model your Asset Tree but it's purely done with CSV files and is pretty tedious, new signals from your historian then also need to be added manually to your CSV file in Seeq and you also can't leverage the framework in other applications.

Any experience in Canary Historian on top of Ignition platform? One of our plants is also starting a PoC on that combo.

Does Seeq support input interface to SQL data bases? Then tables that can be generated and imported in Seeq for further analysis.

What shortcomings are you finding in using UDT for asset definitions? Only friendly names for tags? can you not use SQL tables to define the meta data of assets using friendly names and link them with UDT names?