System parameters reference

Archive

Archive query window size (hours)

Numeric field. The time span (in hours) used to divide the amount of records being archived and purged at one time into smaller sets. This strategy helps to reduce the amount of data that is being retrieved and so lessen the impact of archiving and purging on database performance for production.

The queries that are used to retrieve the data records to archive or purge will ask only for data within the hourly window, based on the last_edit_at datetime in the data records. For example, if the window value is set to 6 hours, the first data retrieval will retrieve the first 6 hours of data records and archive or purge them. When that operation is complete, the next 6 hours of data records will be retrieved and processed, and so on until the final records are reached.

Archive root directory path

Free-form text field. Contains the root directory path (relative to the server) to which archived data is saved and from which archive data is restored.

The default path is C:\Program Files\Wonderware\MES\Archives.

Note the following:

• The archive root directory path must be the absolute path, including the drive letter.

• The path cannot be c:, c:\, or blank. If it is, it will revert to the default path.

• Make sure that any users who are performing archive and restore jobs have access to the archive directory.

• If the archive directory is changed, configure the MES DB/MW Communication component again with the post-install Configurator to grant the MES middleware's Windows user account access to the new directory location.

Archive server host

Free-form text field. Contains the name of the archive server host where the archive files are located.

If blank, the local host is assumed.

If the archive server host is changed, configure the MES DB/MW Communication component again with the post-install Configurator to grant the MES middleware's Windows user account access to the new directory location.

Days to keep data (0=never delete)

This parameter is no longer used.

Day to archive data

This parameter is no longer used.

Time to archive data (HH:MM)

This parameter is no longer used.

Required WO status for archiving

Drop-down list containing Complete and Closed. Determines, by status, which work orders will be archived.

Configuration

Lowest level process that can be instantiated

Drop-down list containing Experimental, Approved, and Certified.

Defines the minimum process level that is needed to create a work order. Experimental is the lowest possible level. If Experimental, processes of all 3 types may be instantiated. If Approved, Approved and Certified processes may be instantiated. If Certified, only Certified processes may be instantiated.

Include jobs with 0 quantity when creating work orders

If Yes, a job with no starting quantity can be created from a process. If No, a job with no starting quantity cannot be created from a process.

Supervisor file display

Drop-down list. Defines the combination of file name and/or description that will be displayed to the user.

Max. number of decimals for good piece part entries

Numeric field. Determines the maximum number of decimal places that may be used when reporting good production. The range is 0 - 7. The default is 0.

Max. number of decimals for BOM configuration

Numeric field. Determines the maximum number of decimal places that may be used when entering BOM configuration setting values. The range is 0 - 7. The default is 7.

Max. number of decimals for batch size entry

Numeric field. Determines the maximum number of decimal places that may be used when entering a batch size. The range is 0 - 7. The default is 3.

Disallow deletion of entities

Yes/No drop-down list. If Yes, a user would not be permitted to delete physical entities.

Disallow deletion of items and classes

Yes/No drop-down list. If Yes, a user would not be permitted to delete items or item classes from the system.

Disallow deletion of BOMs and BOM dependent data

Yes/No drop-down list. If Yes, a user would not be permitted to delete BOMs or data that is dependent on the BOM.

Disallow deletion of certification data

Yes/No drop-down list. If Yes, a user would not be permitted to delete certification data that was previously entered into the system.

Disallow deletion of spec data

Yes/No drop-down list. If Yes, a user would not be permitted to delete spec data that was previously entered into the system.

Disallow deletion of folder data

Yes/No drop-down list. If Yes, a user would not be permitted to delete Folders data that was previously entered into the system.

Disallow deletion of data log data

Yes/No drop-down list. If Yes, a user would not be permitted to delete any Data Log data that was previously entered into the system.

Disallow deletion of WO created from a certified process

Yes/No drop-down list. If Yes, a user would not be permitted to delete a work order created from a certified process.

Disallow deletion of users

Yes/No drop-down list. If Yes, a user would not be permitted to delete (other) users previously entered into the system.

May not delete or modify components of a certified process

Yes/No drop-down list. If Yes, a user would not be permitted to make any changes or deletions of certified processes.

May have only one certified process in a process class

Yes/No drop-down list. If Yes, a process class is limited to having only one certified process.

How to automatically downgrade a certified process version

Drop-down list containing Experimental and Approved. Indicates what level a certified process should be set to when a new certified process is added to a process class and the process class may have only one certified process in it.

Cloned certified process status if only one certified process is allowed

Drop-down list containing Experimental and Approved. Determines the status given to a process that is cloned from a certified process, if only one certified process is allowed in a process class.

Process approver and editor must be different users

Yes/No drop-down list. If Yes, a user may not approve processes he edited.

Process version number format (# = number to increment)

Free form text field. Defines the format mask for auto-incrementing process version numbers.
Example: P-AB#, shows as P-AB1, P-AB2, …

Automatically generate process version numbers

Yes/No drop-down list. If Yes, automatically generates a version number when a new process is created.

Prompt for check in when closing Process window?

Drop-down list, containing No, Yes, Default None Selected, and Yes, Default All Selected. If Yes, provides a dialog box when exiting the Process window for the user to check-in processes that he currently has checked out, with the requested number of processes automatically selected (All or None). The user may change the selections before closing the dialog box.

Use check-in/check-out for processes

If Yes, processes must be checked out in order to be modified. If No, processes do not need to be checked out to be modified.

Require notes upon process check-in

Yes/No drop-down list. If Yes, provides a dialog box for the user to enter notes when checking-in a process.

Data Entry

Sample wait time for delayed production (in minutes)

For samples based on a units-of-production frequency, the MES middleware maintenance service will adjust sample request times based on the setting of this parameter.

If this parameter is set to 0, then there are no adjustments to future sample request times and it is possible for a future request time to have a value in the past.

If this parameter is set to a non-zero value, then when the time for a future sample passes without there being enough production reported to warrant it, all future samples for the entity and for the production count frequency will have their requested times increased by the specified number of minutes, thereby keeping them in the future.

Enforce Calendar Frequency by Characteristic

Specifies whether each characteristic within a QM specification with a calendar frequency must wait the defined time interval.

If this parameter is set to TRUE, more than one sample can be generated from the QM specification where each sample has some of the characteristics.

If this parameter is set to FALSE, all characteristics in the QM specification will be included in each sample generated by it.

The default is TRUE.

Frequency to call sample updates (in seconds)

Specifies the interval at which sample information (creating new future samples, readying samples, or updating the sample state), is updated. The default is 30 seconds.

How long to keep old context information (in days)

Specifies the number of days to keep context information that is no longer current.In case the context information becomes current again (e.g., as may happen when a suspended job is restarted), sampling may pick up where it left.

Maintain distinct consumption records

Yes/No drop-down list. If Yes, writes a new record in the Item_cons table for any changes made to consumption records.

Maintain distinct good production records

Yes/No drop-down list. If Yes, writes a new record in the Item_Prod table for any changes made to good records.

Maintain distinct reject production records

Yes/No drop-down list. If Yes, writes a new record in the Item_Prod table for any changes made to reject records.

Verify quantity entry

Yes/No drop-down list. If Yes, the quantities entered by a user of the Operator module will be verified by a Yes/No prompt.

Require filter for work orders?

If Yes, the user is prompted to restrict the number of work orders displayed in a list if there is no filtering by default.

Display

Default language

The language that appears on the initial log on screen before a user logs in.

Critical error color

Selection field. Allows you to set/modify the color used for critical errors throughout the system.

Serious error color

Selection field. Allows you to set/modify the color used for serious errors throughout the system.

Error color

Selection field. Allows you to set/modify the color used for the text of error messages throughout the system.

Warning color

Selection field. Allows you to set/modify the color used for warnings throughout the system.

Information message color

Selection field. Allows you to set/modify the color used for informational messages throughout the system.

User display

Drop-down list. Defines which combination of user ID and/or user description will be displayed.

Item class display

Drop-down list. Defines which combination of Item Class ID and/or Item Class Desc(ription) will be displayed.

Item display

Drop-down list. Defines which combination of Item ID and/or Item Desc(ription) will be displayed.

Customer display

Drop-down list. Defines which combination of Customer ID and/or Customer Name will be displayed in the Customers window.

Show only file name

Yes/No drop-down list. If Yes, shows only the name of a file and not the complete path in all modules that display file information.

Items require filtering

If Yes, a user will first be prompted to restrict the number of items displayed in a list. If No, the user will not be prompted to restrict the number of items displayed in a list.

Storage entities require filtering

If Yes, a user will first be prompted to restrict the number of storage entities displayed in a list. If No, the user will not be prompted to restrict the number of storage entities displayed in a list.

Sample Result Good Color

For the .NET Sample Viewer control, indicates a sample characteristic with all variables and attributes within normal range.

Sample Result OOC Color

For the .NET Sample Viewer control, indicates a sample characteristic with at least one variable or attribute out of the SPC control, and no variables or attributes out of specification.

Sample Result OOC Critical Color

For the .NET Sample Viewer control, indicates a sample characteristic with at least one variable or attribute with a severity setting of critical, that is out of the SPC control, and no critical variables or attributes out of specification.

Sample Result OOC Key Color

For the .NET Sample Viewer control, indicates a sample characteristic with at least one variable or attribute with a severity of key out of the SPC control, no critical or key variables or attributes out of specification, and no critical variables or attributes out of control.

Sample Result OOS Color

For the .NET Sample Viewer control, indicates a sample characteristic result with at least one variable or attribute out of specification. This color indicates individual variable characteristics.

Sample Result OOS Critical Color

For the .NET Sample Viewer control, indicates a sample characteristic result with at least one variable or attribute with a severity setting of critical, that is out of specification.

Sample Result OOS Key Color

For the .NET Sample Viewer control, indicates a sample characteristic result with at least one variable or attribute with a severity setting of key, that is out of specification.

Sample Result Pending Color

For the .NET Sample Viewer control, indicates a sample characteristic with some variables and attributes that are waiting to be collected. The collected variables and attributes are within normal range.

Sample Status Cancelled Color

For the .NET Sample Viewer control, indicates a sample for which measurements are not taken.

Sample Status Complete Color

For the .NET Sample Viewer control, indicates a sample where the recorded time at which the minimum number of original results in the sample is less than or equal to the sample expiration time, and there are enough results for every characteristic linked to the sample.

Sample Status Complete Late Color

For the .NET Sample Viewer control, indicates a sample where the recorded time for at least one original result in the sample at or below the minimum number is greater than the sample expiration time, and there are enough results for every characteristic linked to the sample.

Sample Status Future Color

For the .NET Sample Viewer control, indicates a sample for which measurement results are to be collected at a future date.

Sample Status In Progress Color

For the .NET Sample Viewer control, indicates a sample that has a requested time less than or equal to the current time, and an expiration time greater than or equal to the current time. The sample does not have enough results for at least one of the characteristics linked to it. The sample pulled time is either Not Null or there is at least one result.

Sample Status Late Color

For the .NET Sample Viewer control, indicates a sample that has an expiration time less than or equal to the current time, and does not have enough results for every characteristic linked to it. Either the sample pulled time is Not Null or there is at least one result.

Sample Status Missed Color

For the .NET Sample Viewer control, indicates a sample that has an expiration time less than or equal to the current time, the sample pulled time is Null, and there are no results.

Sample Status Ready Color

For the .NET Sample Viewer control, indicates a sample where the current time is greater than or equal to the requested time of the sample, and less than or equal to the expiration time of the sample. If the warning interval is Not Null, or less than the sample requested time and the warning interval, the sample pulled time is Null, and there are no results collected for the sample.

Sample Status Ready Warning Color

For the .NET Sample Viewer control, indicates a sample where the current time is greater than or equal to the requested time of the sample, and less than or equal to the expiration time of the sample. If the warning interval is Not Null, and the current time is greater than the sample requested time, the sample pulled time is Null, and there are no results collected for the sample.

Color for automatic collection column

Allows you to set/modify the column heading colors in Sample Viewer, for characteristics that are collected automatically.

Cut-off time (in days) to limit the number of samples while calculating process statistics from the samples (0 = Include all samples)

Upper bound on the age of sample data used to calculate process statistics. This time range is applied to the sample’s requested time. Use this parameter to exclude sample data that is considered too old to be relevant. For example, setting this parameter to a value of 2 would mean that only the last 2 days of sample data would be used to calculate process statistics.

Number of samples to consider calculating process statistics

Maximum number of samples to include when calculating process statistics. Use this parameter to tune the performance of the system so that there is not too much data being analyzed.

Dismiss production dialog upon entry

Yes/No drop-down list. If Yes, the Add Production dialog in the Operator module closes automatically after the user clicks Save and the production is successfully recorded. If No, the user of the Operator module must click Close to dismiss the Add Production dialog.

Re-use concurrent link values to aid color coding

Yes/No drop-down list. Refers to the 16 colors used to color-code link #s in the Queue window. If Yes, new links will be given an unused number between 1 & 16, to simplify color-coding. If No, a new link will be given the next highest number (a color will still be reused).

Warning level number of records for the Sample Characteristic filter dialog in SRO

Specifies the maximum number of records to be returned in this dialog, before the operator is prompted to narrow the filter criteria.

Warning level (number of records) for filter dialog in Item Prod Editor

When applying a filter setting, if the number of records that will be returned exceeds this number, the user is warned that a large set of data will be displayed in the Item Production Editor.

Warning level (number of records) for filter dialog in Item Cons Editor

When applying a filter setting, if the number of records that will be returned exceeds this number, the user is warned that a large set of data will be displayed in the Item Consumption Editor.

Warning level (number of records) for filter dialog in Job Step Data Editor

When applying a filter setting, if the number of records that will be returned exceeds this number, the user is warned that a large set of data will be displayed in the Job Step Data Editor.

Warning level (number of nodes) for filter in Item Lot Editor

When applying a filter setting, if the number of nodes that will be returned exceeds this number, the user is warned that a large set of data will be displayed in the Item Lot Editor.

Use saved filters in Item Production Editor

If Yes, the previously saved Item Production Editor filter settings will be used for the current user.

Use saved filters in Item Consumption Editor

If Yes, the previously saved Item Consumption Editor filter settings will be used for the current user.

Use saved filters in Job Step Data Editor

If Yes, the previously saved Job Step Data Editor filter settings will be used for the current user.

Prompt for confirmation of deletions in Data Editor?

Yes/No drop-down list. If Yes, provides a dialog box requesting confirmation before a deletion requested in Data Editor is executed in the database.

Dynamic Routing

Combine dynamic routing from the same operations of different work orders

If Yes, instead of instantiating a separate rework job for additional production requiring rework, add it into existing rework jobs, provided they are not started and the jobs that would have been created differ only in the work order and operation from those to which the rework is to be added.

This is enabled only if Dynamic Routing is a separate WO from original is True, as otherwise rework from different work orders stays within the original work order.

Copy remaining jobs to end of WO created for dynamic routing

If Yes, when a job is identified as needing rework and a new work order is created for the rework, all subsequent jobs are copied to the end of the new work order.

Differentiate rework count by item reason

If Yes, the dynamic processing count is differentiated based on the item reason.

Differentiate rework count by job sequence number

If Yes, the dynamic processing count is differentiated based on the job sequence number.

Differentiate rework count by operation ID

If Yes, the dynamic processing count is differentiated based on the operation ID.

Differentiate rework count by process

If Yes, the dynamic processing count is differentiated based on the rework process.

Differentiate rework count by WO ID

If Yes, the dynamic processing count is differentiated based on the work order ID.

Dynamic Routing is a separate WO from original

If Yes, jobs from dynamic routing become associated with a new work order with an automatically generated ID.

If No, rework jobs are associated with the original work order and the reworked parts can be merged back into the original flow of jobs.

Label for work orders created by a dynamic route

Defines the description used if a separate work order or job is created for dynamic routing.

Modify lot numbers of dynamic routes

Defines whether the lot numbers of the parts to be dynamically routed remain the same always, are always changed to new automatically generated values, or are changed to new values only if the quantity being reworked is less than the total quantity for that lot (as defined by inventory). This parameter applies only if the lot numbers are not the serial numbers.

Redo job originating dynamic routing at end of dynamic process

Defines whether a copy of the current job is appended to the end of the set jobs created in the mini-process when rework or alternate processing is required at the current job. For example, after reworking, items may require inspection.

Use label in dynamic routing work order or operation IDs

If Yes, the operation ID for rework jobs are appended with a dash immediately followed by the value specified in Description for rework work orders immediately followed by incremental numbers.

For example, a rework job consisting of operations A, B, and C would create jobs identified as A-Rework1, B-Rework1, and C-Rework1 the first time the job was added to a work order and A-Rework2, B-Rework2, and C-Rework2 the second time the job was added to a work order.

Folders

Revision justification

Drop-down list containing Right and Left. Determines the justification of a revision to a folder.

Check file date/time/size for design hold

Yes/No drop-down list. If Yes, allows the user to check folder date, time and size for putting on design hold.

Log changes to file type or description

Yes/No drop-down list. If Yes, the system will log changes to file types or file descriptions.

General

Allow clients from multiple time zones on the same Middleware server

If Yes, time zone information must be passed to the Middleware server from each client. If No, the middleware server’s time zone is assumed to be the same as that of its clients.

Allow user to account for less than 100% of their time

Yes/No drop-down list. If Yes, allows a user to account for less than their complete shift.

Allow user to account for more than 100% of their time

Yes/No drop-down list. If Yes, allows a user to account for more than their complete shift.

User ID for background tasks

Free-form text field. This is the user ID which will be used for background tasks.

Error log level 0 (critical) to 4 (events/information)

Numeric field. Determines the error log level setting, logging errors of the specified value and more critical.

0 = Critical errors - significant, may crash system

1 = Serious errors - will affect operation and data

2 = Partial errors - some data will be wrong

3 = Trivial errors - small adverse effect on some data

4 = Events - will not affect data or operation, information only

Work order ID format (# = number to increment)

Free-form text field. Defines the format mask for auto-incrementing work order ID numbers.
Example: WO-AB#, shows as WO-AB1, WO-AB2, …

Lot number format (#=number to increment)

Free-form text field. Defines the format mask for auto-incrementing lot numbers.
Example: LOT-AB#, shows as LOT-AB1, LOT-AB2, …

PO ID number format ( # = number to increment)

Free-form text field. Defines the format mask for auto-incrementing PO numbers.
Example: PO-AB#, shows as PO-AB1, PO-AB2, …

Storage entity serial number format (# = number to increment)

Free-form text field. Defines the format mask for auto-incrementing entity serial numbers.
Example: Bin #, shows as Bin 1, Bin 2.

Default Item Class ID

Free-form text field. Determines the default item class ID.

Default Item ID

Free-form text field. Determines the default item ID.

Default job priority

Numeric field. Defines the default priority of a job if the priority is not set when the job is created.

Default labor rate

Currency field. Defines the default labor rate for a user if No labor rate is entered.
Ex: $15

Default percent to start

Numeric field. Assume an operator is going to produce 1,000 of an item in operation 10. If this default percentage is set to 50, then when 500 parts have been completed in operation 10, operation 20 (or the next operation) may begin.

Default Unit of Measure for Items

Free-form text field. Determines the default UOM for an item.

Default Work Order ID

Free-form text field. Determines the default work order ID.

Default Operation ID

Free-form text field. Determines the default operation ID.

Ready all new jobs of a work order together

Yes/No drop-down list. If Yes, the status of all jobs in a work order will be changed automatically to Ready after the release date/time. If No, only the first job’s status will be changed automatically to Ready after the release date/time.

Ready downstream jobs automatically

If Yes, jobs receiving material from an upstream job are changed from new to ready automatically once sufficient material has been produced upstream. If No, jobs receiving material from an upstream job are not changed from new to ready automatically once sufficient material has been produced upstream.

May start and stop multiple jobs for a WO concurrently

Will be implemented in a future release.

Prevent automatic readying of first jobs.

Yes/No drop-down list. Sets the default job state for the first job created for a work order. If Yes, the first job will not start automatically until manually changed.

Schedule work to lowest level

Applies only if you have a license for Scheduler.

Steps must be completed prior to production

Yes/No drop-down list. Indicates whether all steps must be completed or bypassed prior to recording production.

Production counts when no job running

Drop down list. Specifies how to handle production counts received from a custom application when no job is running.

Automatically update scheduled finish time for running jobs

Yes/No drop-down list. If Yes, automatically updates the scheduled finish time for running jobs, to reflect the expected time to produce the remaining required quantity, every minute. If No, the scheduled finish time, once determined, is not recalculated.

Prompt for job status notes

Yes/No drop-down list. If Yes, provides a dialog box allowing the user to enter notes whenever a job status is changed.

Sort job state by

Drop-down list containing Code number and State description. Determines the key field by which the job states will be sorted.

Limit schedulable entities on Jobs window

Yes/No drop-down list. Defines which entities are displayed when changing the Schedule to or Can Schedule to fields. If Yes, the user will only be able to select from entities defined in the process, including the entities’ child entities. If No, the user may select from all defined entities.

Limit schedulable entities on Queue Window

Yes/No drop-down list. Defines which entities are displayed when changing the Schedule to or Can Schedule to fields. If Yes, the user will only be able to select from entities defined in the process, including the entities’ child entities. If No, the user may select from all defined entities.

Log certification sign off as job events

Yes/No drop-down list. If Yes, job event records are inserted into the job_event table when an audit certification is approved.

Log consumption transactions as job events

Yes/No drop-down list. If Yes, job event records are inserted into the job_event table when an item is consumed during a job.

Log production transactions as job events

Yes/No drop-down list. If Yes, job event records are inserted into the job_event table when an item is produced during a job.

Log job state changes as job events

Yes/No drop-down list. If Yes, job event records are inserted into the job_event table when a job state is altered from one state to another.

Log spec changes during job execution as job events

Yes/No drop-down list. If Yes, job event records are inserted into the job_event table when the value of a defined job spec is altered.

Log step completions as job events

Yes/No drop-down list. If Yes, job event records are inserted into the job_event table when a job step’s status is changed to Completed.

Log storage entity changes

Yes/No drop-down list. If Yes, records are inserted into the job_event table when a storage entity’s definition is changed.

Log inventory transfers

Yes/No drop-down list. If Yes, records are inserted into the item_transfer table when an inventory item is transferred, shipped, received, or scrapped.

Apply entity access to inventory

Yes/No drop-down list. If Yes, limits the logged in user to "view only" for those inventory locations that the user has not been granted access. This would apply to both inventory window and inventory control.

Apply grade code preference when consuming from inventory

Yes/No drop-down list.

Minimum traceable inventory amount

The smallest amount of inventory that is kept track of for genealogy purposes when consuming from an entity in which lots are indistinguishable.

This parameter can be used with the physical entities Storage parameter Multiple lots/items stored here become indistinguishable in the following way: If the Multiple lots/items stored here become indistinguishable parameter is selected and the Minimum traceable inventory amount parameter has a value entered, then once the quantity for a lot drops below that value, the balance of the item quantity for that lot (that is, the quantity set as the minimum traceable inventory) will be distributed across the other lots, and the quantity for that lot will be set to 0.

Allowable deviation above start quantity (%); -1 if no limit

Numeric field. This is the allowable percentage above a job’s starting quantity that an operator can report as produced. A value of -99 is viewed as unlimited.

Allowable deviation below start quantity (%)

Numeric field. This is the allowable percentage below a job’s starting quantity that an operator may report as produced.

Category for labor not to be applied

Specifies the labor category that will always have a percent to apply value of 0 to captures of applied labor for inactive jobs. If the No value is specified, then no labor category will take on this characteristic.

Description for automatically-generated (Kanban) work orders

Free-form text field. Determines the standard description for automatically-generated work orders.

Path to Form program

When opening a form, a flag that identifies that the first value in the comma-separated list being supplied specifies the Forms program to launch, as a fully qualified path. This program is used to open any defined forms attached to a step or to the Open Form button on the various controls. The parameters to pass are specified in the Default parameters to pass to Forms program system parameter.

XML encoding style

Free-form text field. Defines the encoding standard to be used. If blank, defaults to the U.S. standard. As an example, for Russian: encoding=iso-8859-1

Operator

Allow inactive entity log-on to move between PCs

Yes/No drop-down list. If Yes, a user that has logged on to an entity and is inactive can then log back on to that entity from another machine.

Allow to minimize

Yes/No drop-down list. If Yes, the user may utilize Windows’ Minimize function for the MES Operator’s window.

Auto start jobs when using job based login

This system attribute will only apply to users who have a job-based log on. If Yes, the Start Some button and Start Job button are disabled. Only the Log on button is enabled; however, the Log on button will join an operator to a running job, start jobs that are not running, and will automatically create new split jobs if one does not exist for the selected entity.

The Log on button will only be enabled when the selected job can be started based on operator privileges and possible run on entities are accessible to logged in operator.

Default parameters to pass to Forms program

Defines the replaceable parameters to be used, if not otherwise defined, when invoking a third-party form tool in the Steps control. The entry is a comma-separated string with the first value being the forms program to run, followed by additional parameters such as the form name. Whether the string includes the forms program to be launched is specified by the Path to Form program system parameter.

How to handle comments when merging utilization events

When merging two utilization events, specifies whether and, if so, how the merge will occur if the comments for the two events are different. The options are:

• Do not merge if comments differ. The events will not be merged.

  Note: You must edit an event's comment so that it matches the comment of the other event prior to merging events. In addition, you can only apply new comments after successfully merging existing events.

• Merge using the comment from the earlier event.The events will be merged, and the comment from the earlier event will be used as the comment for the merged event.

• Merge using the comment from the later event.The events will be merged, and the comment from the later event will be used as the comment for the merged event.

How to handle raw reason codes when merging utilization events

When merging two utilization events, specifies whether and, if so, how the merge will occur if the raw reason codes for the two events are different. The options are:

• Do not merge if raw reason codes differ. The events will not be merged.

• Merge using the raw reason code from the earlier event.The events will be merged, and the raw reason code from the earlier event will be used as the raw reason code for the merged event.

• Merge using the raw reason code from the later event.The events will be merged, and the raw reason code from the later event will be used as the raw reason code for the merged event.

Include labor in updates to subscribed data

This option will be implemented in a future release.

Determines if changes to the current labor information for an entity will refresh the subscribed data.

Include OEE in updates to subscribed data

This option will be implemented in a future release.

Determines if changes to the current OEE information for an entity will refresh the subscribed data.

Include running jobs in updates to subscribed data

This option will be implemented in a future release.

Determines if changes to the current job information for an entity will refresh the subscribed data.

Include storage in updates to subscribed data

This option will be implemented in a future release.

Determines if changes to the storage status or characteristics of an entity will refresh the subscribed data.

Include utilization in updates to subscribed data

This option will be implemented in a future release.

Determines if changes to the current utilization information for an entity will refresh the subscribed data.

Logging out of the last job on an entity logs the user off the entity

Yes/No drop-down list. If Yes, logging out of the last job on an entity logs the user off the entity.

Operator file display

Drop-down list. Defines which combination of File name and/or Description will be displayed to the user of the Operator module.

Operator tab orientation

Drop-down list, containing Top and Left. Provides a choice on the default location of the entity tabs in Operator’s window.

Operator tab text orientation

Drop-down list, containing Normal and Horizontal. Provides a choice of how the entity text is shown on the entity selection tabs in the Operator’s window.

Prevent job with unapproved data log from being finished

Yes/No drop-down list. If Yes prevents job with unapproved data log from being finished.

Prompt for alternate user

Yes/No drop-down list. If Yes, log on screen will be displayed when current user does a switch user, preventing a return to the Windows’ interface.

Prompt for production quantities on log off/exit

Yes/No drop-down list. If Yes, the Add Production window will be displayed when a user logs out of or exits Operator. The user can then enter production quantities.

Ready only downstream jobs that have input percent greater than zero

If a job normally receives no material from an upstream job, it is never automatically readied.

Seconds between checks for updates to data subscriptions

The number of seconds between checks for changes to an entity that could initiate a refresh.

Step auto bypass operator name

The user to which the action of bypassing a step be attributed if the step bypass occurs automatically.

Use original button icons

Yes/No drop-down list. If Yes, the original icons will be used for Operator.

Reports

System parameters used by MES BI Gateway Reports to specify what constitutes the start of the production day. For more information, see the MES BI Gateway Reports User Guide.

Production Day Start (Hour)

If the Production Day Start parameter is set to Time of Day, specifies the hour portion of the cut-off time for the production day. The valid range of values is 0 (the default) to 23.

Production Day Start (Minute)

If the Production Day Start parameter is set to Time of Day, specifies the minute portion of the cut-off time for the production day. The valid range of values is 0 (the default) to 59.

Production Day Start

Specifies when the 24 hours of the production day starts:

• ShiftStart: The production day starts with the first shift that starts in the day. For example, if the first shift that starts in the day starts at 08:00:00, then the production day starts at 08:00:00 of the current calendar day and ends at 07:59:59 of the next calendar day. If the current calendar day is December 1, then the production day would be from December 1 at 08:00:00 to December 2 at 07:59:59.

• ShiftEnd: The production day ends with the last shift that ends in the day. For example, if the last shift that ends in the day ends at 23:00:00, then the production day starts at 23:00:00 of the previous calendar day and ends at 22:59:59 of the current calendar day. If the current calendar day is December 1, then the production day would be from November 30 at 23:00:00 to December 1 at 22:59:59.

• TimeOfDay: The production day starts with the first shift that occurs after the cut-off time specified by the Production Day Start (Hours) the Production Day Start (Minutes) parameters. For example, if the cut-off time is defined to be 06:00:00 and the first shift that starts after that time starts at 07:00:00, then the production day starts at 07:00:00 of the current calendar day and ends at 06:59:59 of the next calendar day. If the current calendar day is December 1, then the production day would be from December 1 at 07:00:00 to December 2 at 06:59:59.

Security

Allow default entity logon

Yes/No list which defaults to No. If set to Yes, shows a check box on the entity logon dialog entitled ‘Always log on to these entities’. If checked, on subsequent logs on the entities which are selected will be automatically logged into.

Automatic Login

Controls whether the current Windows user will be automatically logged in to MES Client when the Security mode is set to OS User or OS Group.

If set to Yes and both of the following conditions are true, the user is automatically logged in to MES Client:

• The Security Mode parameter is set to OS User or OS Group.

• In OS User mode, the current Windows user has been added to the MES database or, in OS Group mode, the current Windows user is a member of a Windows user group that has been added to the MES database.

  If set to No, MES Client prompts for a user name and password.

  If this parameter is set to Yes, the Security Mode parameter is set to OS Group, and the current Windows user is not a member of one of the Windows user groups that have been added to the MES database, the following error message appears if the user attempts to log in to MES Client: OS User group is not configured. After dismissing the message, the MES Client Login window appears.

  This parameter is not used for MES Web Portal auto-logins, which is controlled by Windows system and web browser settings.

Default BOM substitution level

Numeric field. Defines the initial security level when a substitution item is created.

Default document download level

Numeric field. Defines the initial security level for downloadable documents.

Default document edit level

Numeric field. Defines the initial security level for editing documents.

Default document print level

Numeric field. Defines the initial security level for printing documents.

Default document view level

Numeric field. Defines the initial security level for viewing documents.

Default specification access level

Numeric field. Defines the initial security level when a specification is assigned to an operation or item.

Maximum duration in minutes which constitutes consecutive logins (0=forever)

Numeric field. Defines the time window during which failed log on attempts are to be considered consecutive. For example, if a user attempts to log on Monday and their log on attempt failed due to an incorrect password and then he attempts to log back in on Tuesday, this would not be considered consecutive if this parameter were less than 1440 (that is, 1 day).

Minimum password length

Numeric field. The fewest number of characters a password may contain.

Note: This parameter applies to Native security mode only.

Number of days a password is valid (0 = passwords are always valid)

Numeric field. The number of consecutive days for which a user's password will be active; after that, a new password must be selected.

Number of failed login attempts before deactivation (0=never)

Numeric field. The number of attempts a user may enter an incorrect password before he is terminated from the program.

Note: This parameter applies to Native security mode only.

Seconds of inactivity before automatic logoff (0=never)

Numeric field. The number of seconds of inactivity before the user is automatically logged off the module. Applies to all MES programs a user log into except Operator.

You must restart the application after changing these settings.

Seconds of inactivity before automatic switch user (Operator; 0 = never)

Specifies the number of seconds of inactivity before a user is deactivated in Operator. The Operator displays the Switch User window and the user enters their password before returning to the Operator screen.

You must restart the Operator after changing these settings.

Security Mode

Specifies which Security Mode to use to authenticate MES users when they attempt to log in to an MES application:

• Native: The MES database user account is used.

• OS Group: The user’s Windows Active Directory (AD) user group is used.

• OS User: The user’s Windows AD user account is used.

  You cannot change the Security Mode if a process is checked out. Otherwise, the process will not be able to be checked in.

  MES Web Portal requires either OS Group or OS User security mode.

Switch user requires password

Yes/No drop-down list. If Yes, a user must re-enter their password before their session in Operator is reactivated.