Hi @uddersnz, welcome! Appreciate the good words! I think your thoughts are quite well in line with what we recommend. I am writing down my thoughts in the hope I can answer your question and provide more background information. In general, there is edge, on-premise and the cloud. Edge only to handle the situations with Demilitarized Zones On-Premise to be able to keep the factory running in case of internet outages Cloud to leverage cloud features like reduced cost for data storage (S3, etc.), flexibility, etc. THe other way to think about this is OLAP vs OLTP (https://learn.umh.app/blog/integrating-the-unified-namespace-into-your-enterprise-architecture-an-architects-guide/) It boils down to what you want to use with the data. Are you using it more for real-time dashboards (Performance Management, OEE, Maintenance, etc.), then it fits more into the OLTP section. Do you want to run long running complex queries over vast amount of data? Then it is OLAP. Even though some tools can do both, I would say it helps in architecture to still think in two different database types. How you described the on-premise database is to let the factory run on an on-premise database for real-time dashboard scenarios. What is important there is that everything that happens to the data is also fed back into the UNS, so that you know later in the cloud what was the "truth" on the shopfloor at any given time. Otherwise, there is a risk that the data on-premise is calculated / shown slightly different than in the cloud, and that is a real digital transformation killer (what data is now right?). this deviation can happen if on-prem and cloud scenarios are not updated exactly at the same time. Multi-site dashboards is something that for me fits more into OLAP section.