@Diederik I think a good way would be to create a new standalone datasource with an UI where you as an integrator could setup tag renaming. schemas etc. So basically the integrator does a setup in the UI and tell the datasource to automatically map/rename tags based on a defined schema.. Enable which topcis/tag that should be avalible in the datasource and perhaps add some aggregations as well. This could perhaps be done in two different sections where you could use postgres for historian data and kafka for live/short historian. So you could in the datasource have like /umh/_historian/machine/data/tag1 for historian data and /umh/_7daysHistorian/machine/data/tag1 for live kafka data. And for aggregations /umh/_historian/machine/CALCULATED_DATA/value1. This is however a lot of work, especially with UI. What are your thoughts? How do you want to use the data? One thing i have done is to create small functions in postgres for easier use. For example when getting data from a machine we have unique name for the machines so i have a function called: get_asset_by_name('123'). This makes it easier in our case to use the correct machine.