Scope Concept
The following sections describe the concept of scopes and how to use scopes in Part Traceability module. The active usage of scopes becomes relevant in the following two cases:
-
Migration of existing MES multi-installations into one Industrial Application System deployment:
In classical MES installations a separate configuration folder for each installation of a module is present. These folders may even contain configuration files (Test Specifications) with the same name. Each of those installations may use designated databases with a large amount of data. In order to differentiate between those configurations, the Configuration Scope is used. -
Separating configuration and data underneath a tenant:
For some tenants, a separation of configuration and data underneath a tenant may be necessary. Scopes are defined at tenant level. In order to allow for designated configurations per value stream the Configuration Scopes can be used to separate the configuration elements and data views. Once dynamic resources are implemented the access to Configuration Scopes can be limited to users that are associated with a certain value stream.
| The usage of custom scopes is purely optional and may be omitted if not required. If no scopes are configured, all configuration data is stored and read from the respective default scopes. |
