Multi tier historian deployment

in a mutli tier historian deployment, each site has its own historian instance for local collection and access (tier 1), while selected data is forwarded to a central historian (tier 2) this architecture can be extended with an arbitrary number of 'tiers' at each tier, data is aggregated, potentially enriched and subsequently forwarded to the next tier when it’s used uninterrupted local access to historian data is critical local data ownership and governance is important short term high resolution data lives on premise and long term, typically lower resolution, data is stored in a central location for secure access from the business or enterprise network to data from a historian in a high security ot network architecture collectors feed data into a local historian at each site local historians store historical data (short or medium term) local historians forward all or a subset of the data to the central historian factry historian uses out of the box connectivity through open standards therefore there is not one, but there are multiple ways to implement this historian to historian communication the central historian runs in the cloud or on one of the production sites functions used push strategy forwarders docid\ td6emj3f 0xsgji7p4dag can be used to control what data is shared with central historian benefits continuous local access to dashboards and data, even during outages centralized reporting and enterprise integration still possible flexibility to forward only relevant data considerations more servers and datasets to manage across sites local it/ot support required to maintain historian instances data duplication across local and central historians extra load on local historians data governance processes needed to maintain central truth dashboards/configurations are harder to share between sites summary a more complex version of hub and spoke data is collected and stored locally, then aggregated in the next tier useful when local data access and ownership is crucial