Terminal Setting Types are assigned to Terminals in the Terminal Setting form. Each setting represents a specific function, such as Offline Charge Element Validation and Biometric Enforce.
If a Terminal Setting is modified, the application server and terminal must both be restarted in order for the new setting to take effect.
Note that a Terminal Setting will override a Terminal Profile Setting. For example, if a terminal is configured to enforce biometric authentication (BIOMETRIC_ENFORCE), but its Terminal Profile is not, employees will still be required to use a finger scan.
This setting is used to designate an InTouch terminal as a biometric verification terminal. If the terminal has a fingerprint scanner and this setting is enabled, employees can log into the terminal using a fingerprint instead of a badge number.
Set BIOMETRIC_ENFORCE to Enabled if you want employees to log into the terminal using the fingerprint scanner.
Set BIOMETRIC_ENFORCE to Disabled if you do not want employees to log into the terminal using the fingerprint scanner.
If the terminal has BIOMETRIC_ENROLL (see below) enabled, then typically the BIOMETRIC_ENFORCE setting will not be used or will be disabled.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
See Also: Biometric Configuration
This setting is used to designate an InTouch terminal as a biometric enrollment terminal. Employees can use a biometric enrollment terminal to record their fingerprints. The employees can then log into the InTouch terminals using a fingerprint instead of a badge number (provided the terminal has a fingerprint scanner and is configured to enforce biometric verification).
Set BIOMETRIC_ENROLL to Enabled if you want the terminal to be used for biometric enrollment.
Set BIOMETRIC_ENROLL to Disabled if you do not want the terminal to be used for biometric enrollment.
If the terminal has BIOMETRIC_ENFORCE (see above) enabled, then typically the BIOMETRIC_ENROLL setting will not be used or will be disabled.
See Also: Biometric Configuration
Determines the date format used in date fields for elapsed events on a terminal (9540, 9300/9500,or 9520 terminal types). The default value is yyyyMMdd. For example, January 2, 2011 would display as 20110102.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
This setting enforces a password requirement when user wants to transfer a file to the terminal via FTP. The password must match the value you enter in the Setting Value field.
This setting enforces a user name when user attempts to transfer a file to the terminal via FTP. The user name must match the value you enter in the Setting Value field.
This setting enforces a password requirement when user attempts to log into the terminal's web server via an HTTP request. The password must match the value you enter in the Setting Value field.
This setting enforces a user name when to log into the terminal's web server via an HTTP request. The user name must match the value you enter in the Setting Value field.
This setting is used to assign an InTouch Config record to a terminal. An InTouch Config record defines the settings used by InTouch terminals with Shop Floor Time.
In the Setting Value field, the available options are defined in the InTouch Config form.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
Enforces a password for using the local fingerprint enrollment feature on a terminal. Enter a numeric password in the Setting Value field.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
This setting applies to Offline Charge Validation. The numeric value you enter in the Setting Value field is the maximum number of charge element records that can be stored in the offline charge validation document that resides in the terminal.
This setting can also be configured as a Terminal Type Setting.
Note: Terminal memory consumption will increase as the charge element record count increases.
This setting applies to Offline Person Validation. The numeric value you enter in the Setting Value field is the maximum number of person records that can be stored in the offline person validation document that resides in the terminal.
You should not enter more records than the amount listed below. These are the maximum number of person records allowed for a particular terminal. If you do not specify an amount, or if you specify an invalid amount, these values will be used:
Terminal Type - Max Person Records in Offline Validation Document
B-web 9300/9500 - 1000
B-Net 9520/9540 terminals (terminal type 4, 7, 8) - 1000
B-Net 9380/9580 - 2000
Mobile Terminal - 100
This setting can also be configured as a Terminal Type Setting.
Note: Terminal memory consumption will increase with increased person record count.
This setting indicates whether Offline Charge Validation will occur on the terminal. Offline charge validation allows charge elements to be validated locally on the terminal, so that users will not be able to enter an invalid work order number, project number, or other charge element when the terminal is not connected to the server.
Enabled Offline Only: Select this option if you only want offline charge validation to occur when the terminal is offline. When the terminal is offline, charge elements will be validated against a file that resides locally on the terminal. When the terminal is online, charge elements will be validated against the database.
Enabled Online and Offline: Select this option if you want offline charge validation to occur when the terminal is online or offline. Charge elements will be validated against a file that resides locally on the terminal, whether the terminal is offline or not.
Disabled: Select this option to disable offline charge validation. Charge elements will only be validated against the database (when the terminal is online). If the terminal is offline, no validation will occur.
Note: To limit the number of charge element records that can be downloaded to the terminal, use the MAX_CHARGE_ELEMENT_RECORDS setting in the Terminal Setting form.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
When this setting is enabled for a terminal (via Terminal Profile Setting or Terminal Setting), you can use the Document Transfer button in the Terminal Monitor form or the TRIGGER_OFFLINE_VALIDATION_DOC_TRANSFER service to trigger the transfer of updated charge element data to selected terminals for offline validation.
This setting defines the Charge Filter Policy that will be used for Offline Charge Validation. The Charge Filter Policy determines which charge types will be validated when the terminal is offline.
Note: If you are using Offline Charge Validation, you also need to enable the OFFLINE_CHARGE_ELEMENT_VALIDATION setting.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
This setting determines whether offline charges will be validated against an employee’s assigned Charge Filtration Group. The Charge Filtration Group is part of the Charge Element Filtration feature, which is used to limit the charge elements to which an employee can charge their time. The OFFLINE_CHARGE_PERSON_FILTRATION setting makes Charge Element Filtration available when the terminal is offline.
Select Enabled if you want to validate offline charges against an employee’s assigned Charge Filtration Group.
Select Disabled if you do not want to validate offline charges against an employee’s assigned Charge Filtration Group.
This setting can be added as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
Note: If you are using Offline Charge Validation, you also need to enable the OFFLINE_CHARGE_ELEMENT_VALIDATION setting.
This setting applies to the Offline Person Validation feature. It offers support for validation of data in offline mode locally on XML based terminals. The support includes validation of the following authentication credentials:
Badge Number
Biometric Validation
Biometric Exempt Validation
Terminal Filtration
You must enable the setting in order to allow authentication credentials.
Enabled Offline Only: Local/offline person authentication will take place when the terminal is in Offline mode only. The terminal will validate the badge against the local/Offline Person repository (Person.XML) to check if the badge is valid or not.
Enabled Online and Offline: Local/offline person authentication will take place in both Online and Offline mode.
If the terminal is Online, the terminal will validate the badge against the local/offline Person repository (Person.XML) to check if the badge is valid or not. If the badge is not valid the terminal does not contact the server but displays an error message (for example, "Invalid Badge"). If the badge is valid, the terminal sends the transaction to the server, where it gets validated the second time.
If the terminal is Offline, the terminal will validate the badge against the local/offline Person repository (Person.XML) to check if the badge is valid or not.
Disabled: The setting is disabled.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
When this setting is enabled for a terminal (via Terminal Profile Setting or Terminal Setting), you can use the Document Transfer button in the Terminal Monitor form or the TRIGGER_OFFLINE_VALIDATION_DOC_TRANSFER service to trigger the transfer of updated person data to selected terminals for offline validation.
This setting is only available for the Web Service Terminal Type.
The OFFLINE_RECORDS_MAX_AGE setting defines the maximum age in seconds allowed for the Web Service terminal’s offline records in order to return the terminal to an online state.
If OFFLINE_RECORDS_MAX_AGE is set to a value greater than zero, then the terminal may go back online if it has offline records, provided the maximum age of these records does not exceed this number of seconds.
If you do not use this setting or the value for this setting is zero, then the terminal may remain offline until all offline records are processed.
Note that the OFFLINE_RECORDS_MAX_NUM setting will also affect whether the Web Service terminal can go back online when it still has unprocessed offline records.
For example, OFFLINE_RECORDS_MAX_AGE is set to 60 seconds (1 minute) and the OFFLINE_RECORDS_MAX_NUM setting is not used. The Web Service terminal is currently offline. The terminal has offline records that are more than a minute old. Therefore the terminal stays offline. However, if all the terminal’s offline records are less than a minute old, then the terminal will go back to online mode.
You need to configure the OFFLINE_RECORDS_MAX_AGE setting if you are Configuring Shop Floor Time to Use Multiple Data Collection Systems. Although this setting is only defined for the triggering terminal in a Terminal Group, it is used as a threshold for the offline records of all the terminals in the group. If a Terminal Group has multiple triggering terminals, the TERMINAL_MONITOR service looks at the OFFLINE_MAX_AGE of each triggering terminal and uses the OFFLINE_MAX_AGE with the lowest value as the threshold for the group.
This setting is only available for the Web Service Terminal Type.
The OFFLINE_RECORDS_MAX_NUM setting defines the maximum number of offline records that the Web Service terminal can have in order to return to an online state.
If OFFLINE_RECORDS_MAX_NUM is set to a value greater than zero, then the terminal may go back online if it has offline records, provided the maximum number of these records does not exceed this threshold.
If you do not use this setting or the value for this setting is zero, then the terminal may remain offline until all offline records are processed.
Note that the OFFLINE_RECORDS_MAX_AGE setting will also affect whether the Web Service terminal can go back online when it still has unprocessed offline records.
For example, OFFLINE_RECORDS_MAX_NUM is set to 5 and the OFFLINE_RECORDS_MAX_AGE setting is not used. The Web Service terminal is currently offline. If the terminal has 10 offline records, it stays offline. If the terminal has 5 or fewer records, it will go back to online mode.
You need to configure the OFFLINE_RECORDS_MAX_NUM setting if you are Configuring Shop Floor Time to Use Multiple Data Collection Systems. Although this setting is only defined for the triggering terminal in a Terminal Group, it is used as a threshold for the offline records of all the terminals in the group. If a Terminal Group has multiple triggering terminals, the TERMINAL_MONITOR service looks at the OFFLINE_MAX_NUM of each triggering terminal and uses the OFFLINE_MAX_NUM with the lowest value as the threshold for the group.
This setting is only available for the Web Service Terminal Type.
When PING_SUPPORT is Enabled, the TERMINAL_MONITOR service uses the terminal’s last communication time (Last Comm to Server field in Terminal Monitor/Communication Details) and the Check Online Time setting in the Terminal Type form to determine whether the Web Service terminal is online or offline. The Last Comm To Server timestamp is updated each time the Web Service terminal sends a ping request to Shop Floor Time.
If PING_SUPPORT is not used or is set to Disabled, the TERMINAL_MONITOR service may not update the Web Service terminal’s status correctly.
For example, the Web Service terminal sends a ping at 12:00 p.m. and the Last Comm To Server field in Terminal Monitor updates accordingly to 12:00 p.m. The Check Online Time setting for the Web Service terminal is 60 (seconds) and PING_SUPPORT is Enabled. If the Web Service terminal does not send another online ping by 12:01 p.m. (60 seconds after the Last Comm To Server time), Shop Floor Time will assume the Web Service terminal is offline.
Note that if the Web Service terminal is using the OFFLINE_CHECK_ONLINE_TIME Terminal Profile setting, it will override the Terminal Type’s Check Online Time setting.
You need to configure the PING_SUPPPORT setting if you are Configuring Shop Floor Time to Use Multiple Data Collection Systems. Set PING_SUPPORT to Enabled for the Web Service terminal in the Terminal Group. The PING_SUPPORT setting ensures that the TERMINAL_MONITOR service will correctly update the Web Service terminal’s status, which will in turn affect the status of the Terminal Group.
This setting defines the Rounding Policy that will be used for transactions posted on this terminal. The Rounding Policy form is used to configure the rules that determine how and when time-related activities, such as Clock Ins, Clock Outs, Breaks, Labor start/stop, etc. are rounded.
This setting can be added as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
This setting assigns a terminal relay schedule to a terminal. A terminal relay schedule is used to schedule one or more terminals to activate a relay signal which can perform an action such as sounding an alarm or opening a door. A relay schedule can be defined for a particular day of the week and time of day. For example, a terminal may be configured to ring a bell for 10 seconds during the start of a shift (9:00 a.m.) and the end of a shift (5:00 p.m.) every week day (Monday – Friday).
For the Setting Value, select the name of the terminal relay schedule you want to assign to the terminal. Available options are defined in the Terminal Relay Sched form.
The RELAY_SCHEDULE setting is typically assigned to a Terminal Profile (as a Terminal Profile Setting Type). If it is assigned to a terminal, the Terminal Setting will override the Terminal Profile setting. For example, a group of terminals in a facility are all configured to ring a bell for 5 seconds when the shift starts at 7:00 a.m.; this relay schedule is assigned to a Terminal Profile. However, one of the terminals has a relay schedule that also opens a door for 10 minutes when the shift starts. This relay schedule is assigned as a Terminal Setting. When the shift starts, this terminal will activate the door opening instead of ringing the bell.
This feature is supported on B-Net 9520 and B-Web 9300/9500 terminals. You will need to know how many relays are on the terminal you are using and which relays are already in use. Consult your terminal’s operation manual for information.
When this setting is enabled for a terminal (via Terminal Profile Setting or Terminal Setting), you can use the Document Transfer button in the Terminal Monitor form or the TRIGGER_OFFLINE_VALIDATION_DOC_TRANSFER service to trigger the transfer of updated relay schedules to selected terminals.
This setting enables or disables the display of seconds in the clock field on a B-Web 9300 or 9500 terminal. The seconds display will update every second.
This setting is disabled by default (seconds will not display). If you do not include this setting in your Terminal Profile, the setting is disabled.
If SHOW_SECONDS_IN_CLOCK is enabled, the terminal will need to use its minimal processing resources to update the seconds display. If the terminal is busy processing transactions, the seconds display may skip an update. To make sure the terminal use its resources most efficiently (for online transactions and offline status checks), it is recommended that you disable SHOW_SECONDS_IN_CLOCK unless absolutely necessary.
This setting can be added as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
The STATE_CODE setting is used to populate the F_STATE_CODE prompt when posting a PROJECT, PROJECT_ACCOUNT, PROJECT_ORGANIZATION, or PROJECT_ACCOUNT_ORGANIZATION event. The Setting Value should represent the State Code for the Facility, Terminal, or Terminal Profile where the event will be posted.
The STATE_CODE setting can be assigned to a:
Person Group Setting for Person Group Type FACILITY
Terminal
Terminal Profile
When a person posts a PROJECT, PROJECT_ACCOUNT, PROJECT_ORGANIZATION, or PROJECT_ACCOUNT_ORGANIZATION event, the STATE_CODE that is used for the F_STATE_CODE prompt depends on whether the event is posted from the Web or from a data collection terminal:
If the event is posted from a data collection terminal, the STATE_CODE will come from the Terminal Setting for the terminal where the event is posted. If the terminal does not have a STATE_CODE Terminal Setting, the STATE_CODE will come from the Terminal Profile Setting for the terminal where the event is posted.
If the event is posted from the Web, the STATE_CODE will come from the Person Group Setting for the FACILITY of the person for whom the event is posted.
Use this setting to prevent events from being posted at a terminal.
The Setting Value is the name of an Event Group. The events in this Event Group cannot be posted at the terminal.
For example, if you only want users to Clock In at a terminal, use the TERMINAL_EVENT_RESTRICTION setting to select an Event Group with a CLOCK event that has the Event Stage set to Stop. Clock Outs will then be restricted from the terminal. If a user who is already clocked in attempts to clock out at the terminal, an error message will display that the clock out is not allowed.
You may want to use this setting if you have dedicated clock in and clock out terminals.
This setting can be added as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.