JDLom

Hi, We are running with a decentralized historian architecture having (Wonderware/ignition/Siemens/PHD) historians in every plant locally and sometimes even other SQL DB's, all containing their own framework, some pretty well structured, some not. The goal is to provide the users a more structured way of finding all their relevant data of the business unit/ plants. The idea is to combine all these datasources into 1 tree I'd like to learn what is the best way to manage this via datalab as these are the challenges that I see: Some layers in the native frameworks are useless/not clear and I want to remove or rename them I want to add a clear root on top of those trees (Business unit name / plant / rest of the tree) Some plants also have other data sources (SQL) that I also want to embed into the right branch of the tree Whenever the local OT engineers add a new signal to their historian, I'd like to have that signal in the new tree as well Any tips or is this an idea to bury away?

Thanks Mark, that did the trick! I was confused with other column names

Hi, We are working on a variety of use cases where each time we need a purpose built asset tree. What we want to do is to search all signals and conditions from an existing simple asset tree, containing only the machine serial number as a parent. Next load our machine database containing all the useful metadata (like model type, width, power source, firmware version, etc) to allow us to build a new structure based on on the metadata that we want. For example in this case i want to build a new tree using driver, Model Type & width. (level 1, 2, 3, 4) I can easily merge the 2 dataframes (searched signals & machine metadata per serial number) together and choose the necessary levels of my tree like this: but what is still needed to convert this into a Seeq asset tree and push this to a local workbook? when I push this df I only get empty assets and no signals. Thanks, Jan