Skip to end of metadata
Go to start of metadata
Go Back to Start of Tutorial

Go back to Start of Section

Move to Last Page
Move to Next Page
Jump to Next Section 















The MES Modules store data in a SQL database. Because Ignition can be configured to use multiple databases, the MES Module Settings configuration page is used to select which databases will be used by the MES module(s) to store data in. If only one database has been configured in Ignition, then it will be selected by default.

  • Log in to the Ignition Gateway configuration page and select MES Modules > Settings from the menu.
  • In the Authentication section, select the user source profile that the MES system will use. For this training, we will use default.
  • Set the Runtime Database to point to the MES database connection we created in the previous step.
  • Set the Analysis Database to point to the MES database connection we created in the previous step.
  • Save your changes to lock in those settings.




Help Manual - How to Configure the MES Databases

The Track and Trace, OEE Downtime, Scheduling, SPC and Recipe modules all store data in the SQL databases defined in this section. All MES table schema and indices will be created automatically in the selected database. Because Ignition can be configured to use multiple databases, the MES Module Settings configuration page is used to select which databases to store the data. To change the MES module settings, go to the configuration section in the gateway and select the MES Modules > Settings section from the left-hand side configuration menu. Once a database connection is created, and if only one database connection exists, then it will be automatically selected to be used by the MES modules. If more than one database connection exists, then the desired database connection can be selected to be used by the MES modules as shown below.

In This Section

  • MES Settings

 









MES Settings

SectionNameDescriptionScreenshot
Authentication

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 UsersMES 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 DatasourceRuntime DatabaseThe Runtime datasource points to the database where production items (site, area, line, cell location etc.) are stored. This database is used by the Recipe Management module for recipe data and by the SPC module for sample definition data. The runtime database is not used by the OEE 2.0 or Track and Trace Modules.

Analysis Datasource



Analysis Database

The Analysis datasource points to the database used by Track & Trace and OEE 2.0 modules to store configuration and production data. 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.

Tip

  • We strongly recommend keeping the MES data in a separate database from any other data that you may store as part of custom ignition applications. Keeping them separate ensures that table schemas are not modified that may break the MES Module functionality. It also provides the ability to troubleshoot database connection issues through the Ignition Gateway by identifying the source of queries that may be affecting Gateway performance.
  • The recommended procedure to change the database on an existing system, is to stop current production in the MES system, disable the production model in the designer (uncheck the Enabled property in the General tab at the enterprise level of the production model), change the data setting, re-enable the production model and restart production.

Go Back to Start of Tutorial

Go back to Start of Section

Move to Last Page
Move to Next Page
Jump to Next Section 















  • No labels