User Source Profile
|MES Person objects are created for any users configured that have first or last name assigned. Since Ignition can have multiple User Source Profiles, the MES system must be configured to know which one to use. In the Authentication section, select the user source profile that MES will use.|
|Auto Sync Users||MES Person objects will periodically synchronize themselves with the current state of the selected Ignition User Source Profile. It is possible to lose all MES Person objects if a synchronization is performed while the User Source Profile is down. Some users may wish to avoid this by un-checking this box, and performing manual synchronizations by calling the scripting function system.mes.synchronizeMESPersonnel() in the Designer's Script Console.|
|Auto Sync Rate (Seconds)||If the user chooses to have Automatic Synchronization enabled, this setting will dictate the rate (in seconds) at which to perform the synchronizing operation. A minimum of 300 seconds (5 minutes) is enforced.|
|Runtime Datasource||Runtime Database|
The Runtime database is used by the Recipe Management module for recipe data and by the SPC module for sample definition data. It also contains ProductionBase item ID tables for both SPC and Recipe. It is not used by the OEE 2.0 or Track and Trace modules (those modules use the MESEquipment table and the MESObjectLink table from the Analysis Database). It does not store the Production Model, since that is a ProjectResource stored in Ignition internal database with all other project resources.
The Analysis datasource points to the database used by Track & Trace and OEE 2.0 modules to store configuration and production data (including the Production Model). Actual SPC sample data is also stored here.
Analysis Database (Auxiliary)
The MES Modules will mirror the information that is written to the local analysis database to the Auxiliary database. For single site implementations, set this to -none-. When you have MES running on multiple servers, setting up the Auxiliary database connection will push MES data up to a central Database to allow enterprise analysis to be performed.
Analysis Query Cache Duration
This setting represents the number of seconds to cache analysis results before refreshing the cached data. The cache is used to optimize gateway performance by maintaining analysis data in memory that can be accessed by clients, reducing the number of queries to the database. Reduce this duration if you need analysis results updated on a more frequent basis or use the system.mes.analysis.invalidateAnalysisCache() function to force the cache to refresh.
|Analysis Read Lock Timeout|
The number of seconds to wait when the analysis engine configuration is being updated.
MES Object Cache
Maximum Cached MES Objects
The MES Object Cache provides some configuration settings that can be used to affect database performance. This property refers to the maximum number of MES objects that is cached at a specific time interval.
Inactive MES Object Threshold (Seconds)
The cached MES objects that are inactive within the specified threshold time would be removed even though the cache is not full.