Central Historian (Hub-and-Spoke) deployment

a single factry historian instance collects data from multiple production sites into one central server it is a simple setup common for companies with multiple, often similar sites that have a need to aggregate and centralize data when it’s used for corporate level reporting across multiple production sites when sharing data, analytics, dashboards and insights between sites is valuable in cases where robust local collection is needed, but long term data lives centrally architecture factry's collectors run close to the data sources, e g machines and scada systems, on each site the collectors make sure the data is buffered locally and securely sent to the shared central historian factry historian runs either in a cloud/corporate datacenter, or sometimes one production site is chosen to host the server on premise functions used collectors perform buffering in case the sites lose connectivity with the central factry historian server \[optional] organizations docid\ ie9bm zmn69tumtdfngbk to separate environments per production site benefits a single source of truth for production data across the organisation only one server and dataset to maintain easy integration with other enterprise systems via one central interface governance and security can be handled in one place considerations the individual sites are dependent on a active network connection to access the data stored in factry historian this becomes increasingly important to recognise when production critical dashboards are built on that central dataset risk of central bottleneck if not built to scale properly think of a bare metal server that has reached a storage or performance limit upgrading this server would render factry historian temporarily unavailable for all sites local ot teams can become heavily depent on a central it team to connect new data sources or onboard new users summary a simple and common hub and spoke setup data collected locally, processed and stored centrally, then shared enterprise wide