Advanced architecture with shared data sources for 2 sites
Scenario 3 covers advanced architecture with shared data source for multiple sites, 2 in this example for illustration.
In addition to scenario 2 there is a new data source. Historian CD stores data coming from 2 plants: Plant C and Plant D.
For each data set a separate connection should be created. Service Account 1 has access only to Tags C. Service Account 2 has access only to Tags D.
This can be configured according to company policy and historian vendor best practice, e.g. through PI trusts or PI mappings for the AVEVA PI Server.
On the TrendMiner side, access to the data source can be granted to users (local users, LDAP users or SAML users) and groups (groups can contain local users, LDAP users or SAML users).
In the example architecture below User A and Group A have access only to the data from Plant A (Tags A). User B and Group B have access only to the data from Plant B (Tags B). User ABD has access to data from Plant A, Plant B and Plant D (Tags A, Tags B and Tags D). User C has access only to the data from Plan C (Tags C)
 |