Settings can normally be assigned to all users, specific facilities, specific employee groups, or individual persons. Check each setting type below to see where the setting can be assigned.
The settings are listed in alphabetical order below.
Can Be Assigned To indicates whether the setting can be assigned globally to all users via the System Settings form, to an Employee Group with type FACILITY or POLICY_GROUP via the Employee Group Setting form, or to an Employee via the Employee Setting form. An Employee setting overrides an Employee Group setting, which overrides a System Setting. See Settings Precedence for details.
Default System Setting indicates which value is assigned by default to all users via the System Settings form.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: SYSTEM_DEFAULT
An Attendance Policy determines which non-labor events can post to employee timecards via the ATTENDANCE service. The rules include posting holiday and penalty events, removing penalties, and using balances to cover penalty events. Only the events that are configured in an employee's Attendance Policy will post to the employee's timecard when the service runs.
Can Be Assigned To:
System
FACILITY Person Group
Person
Default System Setting: None
The AT6 DB Host Name setting defines the data source for the AutoTime 6 database that is used to display data in the Period (AutoTime 6) tab. You can access this tab in the Self Service and Supervisor Review timecards.
The available Setting Values for AT6 DB Host Name are Receivers with a Host Data Source defined in the Interface Host form.
To use the Period (AutoTime 6) tab in the timecard:
The AUTOTIME 6 TIMECARD module must be licensed and enabled.
Your AutoTime 6 Employee Number must be the same as your Shop Floor Time Employee/Person Number.
The Period (AutoTime 6) tab must be enabled in your Security Role.
The AutoTime 6 database must be configured in the Interface Host form. You will also need to deploy the data source for your AutoTime 6 database.
The AT6 DB Host Name setting must be assigned to employees who will be using the tab.
The AT6 DB Host Name setting can be assigned to employees at the Person, Facility, or the System level. The Facility setting overrides the System setting. The Person setting overrides the Facility and System settings.
If you have multiple AutoTime 6 databases (e.g., each facility has its own database), you will need to deploy a data source for each database, and define an Interface Host record for data source.
Can Be Assigned To:
System
Employee Group (FACILITY or POLICY_GROUP)Employee (Person)
Default System Setting: None
A Leave Policy is used to determine how and when Leave Type Codes should be accrued and can be used to offset employee time off. Balance (Leave Type) Codes are the categories that time off can count against in the application (Sick, Vacation, Short Term Disability, etc.).
The Leave Policy setting also includes the Discipline Balance Policy with the same name. The Leave Policy and the Discipline Balance Policy have the same name but are configured in separate forms. The Policy Name field in both forms will display the same values. If you create the Policy Name in the Leave Policy form, you can select this same Policy Name in the Discipline Balance Policy form. However, in the Discipline Balance Policy form you will be configuring Discipline Balance Codes instead of Balance (Leave Type) Codes. Both policies are assigned to persons via the Balance Policy setting.
This setting pertains to legacy B-Net 9520 and B-Net 9540 terminals which are no longer supported in Shop Floor Time although they are still available in the application for use by customers upgrading from AutoTime 6 or AutoTime 7.
Can Be Assigned To:
Person
Default System Setting: None
The Biometric Exempt Employee feature allows a person to use a hand-held CCD scanner or keypad instead of the fingerprint reader.
For example, a person might not have sufficient minutiae on their finger for the fingerprint reader to authenticate the user with 100% accuracy. Only employees that have the Biometric Exempt type set to Yes will be able to use a hand-held CCD scanner or keypad where biometric authentication is enforced.
Select Yes in the Setting Value to enable the exemption.
Can
Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: SYSTEM_DEFAULT
The Change Comparison Policy is used to define which transaction changes will trigger the reprocessing of an export. It is defined in the Reprocess Change Policy form.
When a column is enabled in this policy, a change to the column’s value will cause the old transaction to be marked as Cancelled After Processing (Z) or Cancelled Before Processing (X); this status change will prevent the old transaction from being reprocessed. The new transaction’s status will be Ready for processing (R) and the transaction will therefore be included in the next export.
For example, in a Labor Export, the Column Name duration is Required-Enabled. If a transaction’s duration changes, the transaction will be reprocessed. The old transaction will be cancelled and the new transaction will be marked as ready. The old transaction will have “X” status (Cancelled Before Processing) if it was not yet processed, or “C” (Complete) or “Z” (Cancelled After Processing) if it was already processed. The new transaction’s status will be Ready for processing (R).
In the same Labor Export, the Column Name classification is Disabled. If a transaction’s classification changes, this change will not trigger the need for reprocessing. The old transaction will have “D” status (Cancelled And Any Further Processing Complete) and the new transaction will have “C” (Complete) status.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Hierarchy Person Group
Person
Default System Setting: None
The Charge Element Filtration Group setting specifies the charge elements that are enabled for filtration.
This setting is part of the Charge Element Filtration feature. Charge Element Filtration is a validation feature that limits users to a certain list of charge elements and thus restricts them from charging time to elements that do not apply to them.
When an employee is assigned a Charge Element Filtration Policy (see the system setting below) that has a charge type enabled for filtration, the employee's Charge Element Filtration Group determines which specific charge elements are allowed for the type. The employee can only charge time against the elements that have been configured for the charge type in the Charge Element Filtration Group. If no elements have been configured for the charge type in the Charge Element Filtration Group, the employee cannot charge time against that charge type at all.
Can
Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: SYSTEM_DEFAULT
A Charge Element Filtration Policy is used to configure which charge types (such as Work Order and Project) are enabled for filtration. For example, a Charge Element Filtration Policy (also called a Charge Filter Policy) may include orders but not projects. Employees who are assigned to this policy will only be able to charge time to work orders (not projects).
This system setting is part of the Charge Element Filtration feature. Charge Element Filtration is a validation feature that limits users to a certain list of charge elements and thus restricts them from charging time to elements that do not apply to them.
The employee’s Charge Element Filtration Group (see the system setting above) determines which specific charge elements are allowed for the type. For example, the Charge Element Filtration Group may only include Order 3000 but not Order 3001. The employee can only charge time against the elements specified in Charge Element Filtration Group.
Can
Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: SYSTEM_DEFAULT
Clock Policy rules are created for time-related activities. Each Clock Policy defines how clock-outs are handled.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: SYSTEM_DEFAULT
A Color Policy determines which events and charge elements may determine the background and foreground colors on the Web timecard. The policy also determines which Status columns may appear in colors throughout the application (current status, service status, and terminal status) and what those colors are.
The System Default Color Policy is pre-defined with colors for all values that can appear inside the current status, service status, and terminal status columns. The default policy does not have any colors defined for events or charge elements.
Current Situation Status Event Group
Can Be Assigned To:
System
Person
Default System Setting: Current Situation Status
This setting determines which time-off events can display in the Current Status field in the Current Situation form. The Current Status field will display the name of a time-off event (vacation, sick, holiday, etc.) provided the event is included in the Current Situation Status Event Group setting for the supervisor who is viewing the time card.
The available Setting Values are defined in the Event Group Event form. The default setting (Current Situation Status) is an Event Group with the following events:
ATTENDANCE:HOLIDAY
ATTENDANCE:SICK
ATTENDANCE:TIME_OFF
ATTENDANCE:VACATION
You can configure which events to display in the Current Status field by modifying or adding a new Event Group and selecting it for the Current Situation Status Event Group setting value.
When an event in this Event Group is posted for the employee, the name of the event will display in the Current Status field in Current Situation. This field will also display time off requests that have been approved but not yet posted.
If the duration of the event is less than the person's scheduled paid hours for the day, the word Partial will display next to the event. If more than one of these events has posted, the event names will be separated by commas.
The Current Status field will display the color of the specified event as configured in the BACKGROUND_COLOR and FOREGROUND_COLOR Event Settings.
Can Be Assigned
To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: MM/dd/yyyy
The Date Pattern value sets the default date format for any date values. For example, you can choose dd/MM/yy, yy-M-d, etc. The default value is MM/dd/yyyy.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: None
The Delegation Restriction setting determines whether an acting supervisor can sign, unsign, add, or modify transactions in employee timecards when the post date falls outside the date range of the delegation record.
For example, Supervisor A delegates authority to Supervisor B from 12/5 to 12/9.
On 12/5, Supervisor B is acting as Supervisor A and views the timecard one of Supervisor A’s employees. Supervisor B tries to sign the employee’s timecard for the date 12/1.
If the Delegation Restriction setting is False, Supervisor B can sign the timecard for the date 12/1, even though this date is outside his delegation assignment.
If the Delegation Restriction setting is True, Supervisor B cannot sign the timecard for the date 12/1, because this date is outside his delegation assignment.
Note that the Delegation Restriction setting takes effect based on the current date (i.e., the date you are modifying the timecard) and not the post date you are modifying.
For example, suppose Supervisor B is assigned the Delegation Restriction setting of True from December 1 to December 31. His delegation assignment is December 1 to January 31.
On December 6, Supervisor B is acting as Supervisor A and tries to sign an employee’s timecard for the date November 30. He cannot sign the timecard because the Delegation Restriction setting is True on December 6, which means he can only modify the post dates in the delegation assignment range (December 1 to January 31).
On January 2, Supervisor B again tries to sign the employee’s timecard for the date November 30. This time, he can sign the timecard, because the Delegation Restriction setting is False on January 2. On this date, Supervisor B can modify post dates that fall outside the delegation assignment range.
To use the Delegation Restriction setting, you must enable the DELEGATION_RESTRICTION record in the PVE Plugin form. To do so:
1. Click Main Menu > Configuration > System > PVE Plugin.
2. Select DELEGATION_RESTRICTION and click Modify.
3. Check the Enabled box and click Save.
4. Restart the application server.
Can Be Assigned To:
System
Terminal Profile
Employee Group (FACILITY or POLICY_GROUP)
Employee
Default System Setting: DEFAULT-EN-US
The Dictionary setting determines the language displayed in the application. You can create and manage your custom dictionaries via the Dictionary Label form. Custom dictionaries are applicable when you want to change the display of buttons and fields according to who is using the application. For example, you may want to display buttons in English for one set of employees, but display them in German for another set of employees. Or, you may want to keep the buttons in English, but change their names slightly for particular forms. The Default setting is English.
A Dictionary can be assigned to an Employee, Employee Group, Terminal Profile, or System Setting. The Dictionary Person setting overrides the Dictionary Person Group setting. The Dictionary Person Group setting overrides the Dictionary Terminal Profile setting. The Dictionary Terminal Profile setting overrides the Dictionary System Setting.
Note: You can also select a Dictionary when you Log In to the application. This selection will override the Dictionary assigned to you in the System Settings, Terminal Profile, Employee Group, or Employee form.
Can
Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: None
When adding labor to a Batch or Multi labor, this setting determines which events an employee can add.
If this setting is True, the employee can only add the same event to the Batch or Multi labor.
If this setting is not used or is set to False, the employee can add the same event or another labor event to a Batch or Multi labor.
This setting will only be supported when the terminal’s PROMPT_TYPE is STARTSTART or STARTSTOP.
For example, an employee starts a Multi labor with an event called Work_Order_1. When the employee selects More Labor, the events Work_Order_2, Work_Order_3, and Project are available to add to the Multi. If the setting Disallow Mixed Events in Batch and Multi is set to True for this employee, the employee will only see the event Work_Order_1 when selecting More Labor.
When Disallow Mixed Events in Batch and Multi is set to True, the following methods for adding punch transactions will be affected.
Add Punch Pair
When Disallow Mixed Events in Batch and Multi is set to True, the Add Punch Pair option in the web timecard may filter out events depending on the timestamp of the pair you are adding. If this timestamp falls within an existing Multi labor, you will only be able to add the same event that is in the existing Multi. If Disallow Mixed Events in Batch and Multi is set to False, you will be able to add other labor events to the Multi.
For example, an employee clocks in at 7 a.m. and begins a Multi labor with WorkOrder101. At 10 a.m. the employee stops the Multi labor but realizes he forgot to include WorkOrder102, which he worked on from 8 a.m. to 9 a.m. The employee’s supervisor wants to use Add Punch Pair to insert WorkOrder102 from 8 a.m. to 9 a.m. If Disallow Mixed Events in Batch and Multi is set to True, the supervisor will only be able to add WorkOrder101 using Add Punch Pair. If Disallow Mixed Events in Batch and Multi is set to False, the supervisor will be able to use Add Punch Pair to add WorkOrder102.
Replace Punch
When Disallow Mixed Events in Batch and Multi is set to True, the Replace Punch option in the web timecard will not be available for a Batch or Multi labor with more than one labor.
Offline Punches or Punches from External Systems
If a Batch or Multi labor is posted while the terminal is offline and the Disallow Mixed Events in Batch and Multi setting is True, the employee will not be restricted to a single event. Because the terminal is offline, the Disallow setting will not be checked. The same is true for events posted from an external system (such as Solumina).
However, when the terminal comes back online and the offline transactions are processed, an error will occur if the Disallow setting is True and the Batch or Multi labor includes more than one event.
Can Be Assigned To:
System
Employee
Default System Setting: Disabled
This setting determines whether a password is required when an employee signs or unsigns his/her own timecard.
When this setting is Enabled and the employee clicks the Sign or Unsign button on their own timecard, the system will display a pop-up form. The employee must enter his or her application login password and click OK to sign or unsign the timecard.
When this setting is Disabled, the system will not prompt the employee for a password when signing or unsigning the timecard.
Note: For supervisors signing employee timecards, the Supervisor Authentication on Sign setting will apply.
Can Be Assigned To:
System
Default System Setting: None
This setting is used by ERP systems such as Oracle Time and Labor that regularly poll the database for updates. If you are using an ERP system, make sure the ERP Timezone setting in the System Settings form matches the time zone of your ERP application server.
Can Be Assigned To:
System
Default System Setting: INCLUSIVE
Event Filtration is used to control the events which an employee can access. Event filtration may be used in a facility that has many different types of employees recording their time on the same terminals, but not all the employees should have access to the same events. The Event Filtration settings will include or exclude events from the person’s Menu Tree.
Event filtration can be INCLUSIVE or EXCLUSIVE, depending on your Event Filtration System Setting.
When Event Filtration is INCLUSIVE, employees have access to the events in their filtration group (the terminal menu includes events in their filtration group). If Event Filtration is INCLUSIVE and the employee does not belong to any filtration groups, the employee will have access to all the events in their Menu Tree.
When Event Filtration is EXCLUSIVE, employees do not have access to the events in their filtration group (the terminal menu excludes the events in their filtration group). If Event Filtration is EXCLUSIVE and the employee does not belong to any filtration groups, the employee will have access to all the events in their Menu Tree.
If the employee does not belong to any filtration groups, the employee will have access to all the events in his or her Menu Tree (regardless of the Event Filtration System Setting).
If there is NO Event Filtration System Setting, the system acts as if the setting is EXCLUSIVE. Employees will have access to all the events in their Menu Tree except the events that are in an Event Filtration Group.
Events that are in the employee’s Menu Tree but are not assigned to a filtration group can be accessed regardless of the Event Filtration System Setting and whether the employee is assigned to a filtration group.
The Event Filtration form is used to assign events to an Event Filtration Employee Group. You can also use the Event Filtration tab in the Events form to assign an event to an Event Filtration Employee Group.
You can assign employees to an Event Filtration Employee Group using the Employee Group form.
In this example, a terminal menu has the following
events:
Clock, Meal, Work Order, Project, and Account.
There is an Event Filtration Group for each of the labor events (the Work Order Event Filtration Group contains all Work Order events, the Project Event Filtration Group contains all Project events, etc.). The Clock and Meal events are not assigned to any Event Filtration Groups.
An employee is a member of the Work Order Event Filtration Group.
When the Event Filtration System setting is INCLUSIVE, the employee can only access events that meet either of these criteria: (1) The events are part of the terminal Menu Tree and the events are assigned to the employee's Event Filtration Group or (2) The events are part of the terminal Menu Tree and are not assigned to any Event Filtration Group. When the employee in this example uses the terminal, the available events are Clock, Meal, and Work Order. The Work Order event is assigned to the employee's Event Filtration Group. The Clock and Meal events are in the terminal’s Menu Tree and are not assigned to any Event Filtration Groups. The Project and Account events do not meet the criteria for Inclusive Event Filtration.
When the Event Filtration System setting is EXCLUSIVE, the employee can only access events that meet either of these criteria: (1) The events are part of the terminal Menu Tree and are not assigned to any Event Filtration Group or (2) The events are part of the terminal Menu Tree and are assigned to Event Filtration Groups for which he is not a member. When the employee in this example uses the terminal, the available events are Clock, Meal, Project, and Account. The Clock and Meal events are in the terminal’s Menu Tree and are not assigned to any Event Filtration Groups. The Project and Account events are in the terminal’s Menu Tree and are assigned to Event Filtration Groups for which he is not a member. The Work Order event does not meet the criteria for Exclusive Event Filtration.
Can Be Assigned To:
System
Employee Group (FACILITY or POLICY_GROUP)Employee
Default System Setting: SYSTEM_DEFAULT
An Event Policy determines:
If a user can/must enter a comment and/or reason code to explain why a transaction/punch is added, modified, or deleted in the timecard (Comments And Reason Code tab).
The absence events that are considered excused absences when viewed in the Time Card Review form (Excused Absences tab).
Any event restrictions that apply when the user is posting or modifying time in the web timecard (Event Setting tab).
The System Default Event Policy does not contain any settings for the above options (i.e., users will not be prompted for comments/reason codes and no excused absences or event restrictions are defined).
Note: The Event Setting Manager Policy (see below) is also defined in the Event Policy form. However, the Event Setting Manager Policy does not include the settings in the Comments and Reason Code tab or the Excused Absences tab. The settings in these tabs only apply when the policy is assigned as an Event Policy.
Can Be Assigned To:
System
Employee Group (FACILITY or POLICY_GROUP)Employee
Default System Setting: None
The Event Setting Manager Policy is defined in the Event Setting tab of the Event Policy form. This policy is used to define the event restrictions that apply to a manager posting or modifying hours on employee timecards in the Supervisor Review form.
These restrictions determine whether the supervisor can add, modify, or delete certain events in employee timecards. You can also restrict supervisors from replacing punch events and indirectly modifying punch events for employees.
Both the Event Setting Manager Policy and the Event Policy (see above) are defined in the Event Policy form. However, when this policy is assigned as an Event Setting Manager Policy, the settings defined in the Comments and Reason Code tab and the Excused Absences tab are ignored. The settings in these tabs do not apply when the policy is assigned as an Event Setting Manager Policy.
Can Be Assigned To:
Person Group (FACILITY only)
Default System Setting: None.
When an employee is assigned an Export Premium Policy and the employee works non-regular hours and/or a shift with a premium amount larger than 0, the configuration determines the following:
How premium hours are paid (which rates to use)
If the premium hours are mapped to a payroll, financial, and/or manufacturing location
How payroll, financial, and manufacturing locations are determined
When premium hours are detected in an employee transaction, the transaction's regular portion and premium portions are defined according to the configured premium hours details. These records are stored in the trans_action_duration and trans_action_duration_dtl tables. The values can be used for GL, Labor, and Payroll.export.
Can Be Assigned To:
Person Group (FACILITY only)
Default System Setting: None
The Financial Hierarchy Level and Financial Hierarchy Name settings for a Person Group are used to determine the available HOME_LOCATION_FINANCIAL options that can be assigned to members of that Person Group (via the Person Assignment form). HOME_LOCATION_FINANCIAL defines an element in a hierarchy as the person’s home location for financial purposes.
For example, the Financial Hierarchy Name is Acme_Widgets_Company and the Financial Hierarchy Level is Cost Center (Level 3). When you assign a HOME_LOCATION_FINANCIAL to a member of the Person Group, the available options will be the Level 3 Cost Centers defined for this hierarchy in the Hierarchy Elements form.
Note: You must select a Financial Hierarchy Name before you select a Financial Hierarchy Level. You must also have an Organizational Hierarchy defined.
Can Be Assigned To:
Person Group (FACILITY only)
Default System Setting: None
The Financial Hierarchy Level and Financial Hierarchy Name settings for a Person Group are used to determine the available HOME_LOCATION_FINANCIAL options that can be assigned to members of that Person Group (via the Person Assignment form). HOME_LOCATION_FINANCIAL defines an element in a hierarchy as the person’s home location for financial purposes.
For example, the Financial Hierarchy Name is Acme_Widgets_Company and the Financial Hierarchy Level is Cost Center (Level 3). When you assign a HOME_LOCATION_FINANCIAL to a member of the Person Group, the available options will be the Level 3 Cost Centers defined for this hierarchy in the Hierarchy Elements form.
Note: You must select a Financial Hierarchy Name before you select a Financial Hierarchy Level. You must also have an Organizational Hierarchy defined.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: None
The Fiscal Calendar form is used to create calendars that do not have to correspond to a traditional calendar year. For example, your organization may require a report once per twelve months, but does not require that the period reported on constitutes a calendar year (i.e., January through December). A new fiscal year can begin on any date that meets your fiscal reporting requirements.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Terminal Profile (TERMINAL_FORM_PROFILE setting)
Default System Setting: Default
Form Profiles determine:
Which fields/columns the user can see on a form.
Which fields/columns in a form the user can sort and how the fields should be sorted.
Which fields/columns in a form will display to the user when adding or modifying a record.
The order of the tabs in a form.
A Form Profile can also be assigned to a Terminal Profile using the TERMINAL_FORM_PROFILE setting. This setting will determine how forms such as Accrual Balance and Daily Timecard are displayed. These forms are included in the Form Profile under Terminal Forms.
The TERMINAL_FORM_PROFILE setting will override the Form Profile System Setting, Person Group Setting, or Person Setting.
Can Be Assigned To:
Employee Group (FACILITY or POLICY_GROUP)
Employee
Default System Setting: None
The Holiday Calendar Override setting is used to assign a Holiday Calendar to a Facility, Policy Group, or to individual persons. The Holiday Calendar Override setting takes precedence over the Holiday Calendar defined in the person’s Attendance Policy.
Use the Setting Value field to select the Holiday Calendar you want to assign. Available options are defined in the Holiday Calendar form.
The Holiday Calendar Override setting may be useful when the same Attendance Policy is assigned to a large number of employees but some of the employees require a different Holiday Calendar.
This setting can be assigned to individual persons in the Setting tab of the Employee form, or to an Employee Group of type FACILITY or POLICY_GROUP on the Employee Group Setting tab. If a Holiday Calendar Override is assigned at both levels, the Person setting overrides the Employee Group Setting.
Holiday Calendar Override takes precedence over the Attendance Policy/Holiday Calendar, regardless of the level at which the Attendance Policy is assigned. For example, if the Attendance Policy/Holiday Calendar is assigned at the Employee level, and Holiday Calendar Override is assigned at the Employee Group Level, the Holiday Calendar Override setting will still take precedence over the Attendance Policy/Holiday Calendar.
Can Be Assigned To:
Person Group (FACILITY only)
Person
Default System Setting: None
The HR Hierarchy Level and HR Hierarchy Name settings are used to determine the available HOME_LOCATION_HR options that can be assigned to members of that Person Group. HOME_LOCATION_HR defines an element in a hierarchy as the person’s home location for HR purposes.
The HR Hierarchy Level can be defined as a FACILITY Person Group Setting and as a Person Setting. The Person Setting overrides the Person Group Setting. This function allows a person to have a HOME_LOCATION_HR assignment with a different location (HR Hierarchy Level) than the one specified in their Person Group.
For example, the HR Hierarchy Name is Acme_Widgets_Company and the HR Hierarchy Level is Cost Center (Level 3). When you assign a HOME_LOCATION_HR to a member of the Person Group, the available options will be the Level 3 Cost Centers defined for this hierarchy in the Hierarchy Elements form.
Note: You must select an HR Hierarchy Name before you select an HR Hierarchy Level. You must also have an Organizational Hierarchy defined.
Can Be Assigned To:
Person Group (FACILITY only)
Default System Setting: None
The HR Hierarchy Level and HR Hierarchy Name settings are used to determine the available HOME_LOCATION_HR options that can be assigned to members of that Person Group. HOME_LOCATION_HR defines an element in a hierarchy as the person’s home location for HR purposes.
For example, the HR Hierarchy Name is Acme_Widgets_Company and the HR Hierarchy Level is Cost Center (Level 3). When you assign a HOME_LOCATION_HR to a member of the Person Group, the available options will be the Level 3 Cost Centers defined for this hierarchy in the Hierarchy Elements form.
Note: You must select an HR Hierarchy Name before you select an HR Hierarchy Level. You must also have an Organizational Hierarchy defined.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: None
An Indirect Charge Policy determines which charge element should be used when user posts an event with type LABOR:INDIRECT. The system will charge the event to the charge element that has been mapped to the indirect charge code listed in the user's Indirect Charge Policy. When there are multiple mapping records that match a transaction, the precedence is determined by the Match Precedence setting in the Indirect Charge Policy.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: None
An LDAP (Lightweight Directory Access Protocol) Policy determines which directory service database the system should query against when authenticating a user or group of users via LDAP. In order for this policy to take effect, the user must also have a Web Authentication Profile setting where the setting value is LDAP User/Password Validation. The settings can be applied via System Settings/Person Group, or Person.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: en_US
Locale determines how values such as numbers, currencies and dates are formatted. For example, the value 123, 456, 789.00 may display as 123,456,789,00 or 123,456,789,00 depending on the locale used. The default value is English (United States).
Can Be Assigned To:
Person Group (FACILITY only)
Default System Setting: None
The Manufacturing Hierarchy Level and Manufacturing Hierarchy Name settings for a Person Group are used to determine the available HOME_LOCATION_MANUFACTURING options that can be assigned to members of that Person Group (via the Person Assignment form). HOME_LOCATION_MANUFACTURING defines an element in a hierarchy as the employee's home location for manufacturing purposes.
For example, the Manufacturing Hierarchy Name is Acme_Widgets_Company and the Manufacturing Hierarchy Level is Work Center (Level 4). When you assign a HOME_LOCATION_MANUFACTURING to a member of the Person Group, the available options will be the Level 4 Work Centers defined for this hierarchy in the Hierarchy Elements form.
Note: You must select a Manufacturing Hierarchy Name before you select a Manufacturing Hierarchy Level. You must also have an Organizational Hierarchy defined.
Can Be Assigned To:
Person Group (FACILITY only)
Default System Setting: None
The Manufacturing Hierarchy Level and Manufacturing Hierarchy Name settings for a Person Group are used to determine the available HOME_LOCATION_MANUFACTURING options that can be assigned to members of that Person Group (via the Person Assignment form). HOME_LOCATION_MANUFACTURING defines an element in a hierarchy as the employee's home location for manufacturing purposes.
For example, the Manufacturing Hierarchy Name is Acme_Widgets_Company and the Manufacturing Hierarchy Level is Work Center (Level 4). When you assign a HOME_LOCATION_MANUFACTURING to a member of the Person Group, the available options will be the Level 4 Work Centers defined for this hierarchy in the Hierarchy Elements form.
Note: You must select a Manufacturing Hierarchy Name before you select a Manufacturing Hierarchy Level. You must also have an Organizational Hierarchy defined.
Can Be Assigned To:
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: None
A Message Policy defines the settings for a group of system message triggers and event message triggers. System triggers generate messages that are sent to employees throughout the company based on specific actions (such as a supervisor adjusting an employee’s timecard, which triggers a message sent to the employee). Event triggers generate messages based on the start or stop of an event.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Default System Setting: SYSTEM_DEFAULT
An Order Policy defines the various attributes that will affect WIP (Work In Progress) labor, as well as material movement.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: SYSTEM_DEFAULT
The OT Offer Policy form determines how many hours of overtime a manager may offer an employee per day and per week.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: SYSTEM_DEFAULT
When an employee refuses an overtime offering, the employee's OT Response Policy determines if a refusal code is required. If a refusal code is required or optional, the policy also determines which code to use.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: DEFAULT_PASSWORD_PROFILE
A Password Profile determines the settings of a user's password (when logging in to the application). For example, here you determine the number of characters allowed in a password, or how many tries a user is allowed to enter the wrong password when logging in to the application.
Can Be Assigned To:
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: None
A Pay Policy determines how often employees are paid (weekly, biweekly, etc.).
An employee must be assigned a Pay Policy in order to appear in the Time Card Review form.
Can Be Assigned To:
System
Employee Group (FACILITY or POLICY_GROUP)
Default System Setting: SYSTEM_DEFAULT
This setting assigns a Preferences Policy to a group of time reporters. The Preferences Policy affects the way data is displayed on the timecard.
You can use this policy to change the system default Preferences for a group of time reporters. For example, if you want timecards to display decimal hours (e.g., 2 ½ hours display as 2.5 instead of 2:30), create a Preferences Policy with Duration Format set to DECIMAL.
Each person can still change his or her Preferences using the Preferences pop-up form. These Preferences changes are saved in a Preferences Policy that is named with the person’s ID Number. When a person changes his or her Preferences, the new settings are updated in this policy. You cannot add a Preferences Policy for a person; you can only modify it.
Can Be Assigned To:
System
Employee Group (FACILITY or POLICY_GROUP)Employee
Default System Setting: SYSTEM_DEFAULT
A Post Date Policy determines how time stamps are calculated for real-time transactions so that they appear properly on the timecard.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: None
A Process Policy is used to determine which export processes are applicable for a given transaction. It is also used to determine the Sender Name for a given export process. The Sender Name will be used to determine which external system will receive attendance and labor transactions from Shop Floor Time.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: SYSTEM_DEFAULT
A Recalculation Policy determines how the Recalculation Service will process time reporters' timecards. For example, a Requires Payroll Lock setting may prevent the selection of employees for recalculation if their timecards are not locked appropriately.
Can Be Assigned To:
System
Employee Group (FACILITY or POLICY_GROUP)Employee
Default System Setting: SYSTEM_DEFAULT
A Rounding Policy determines how time will be rounded for time-related activities, such as Clock Ins, Clock Outs, Breaks, Labor start/stop, etc. The policy determines how and when these activities are rounded to a certain point in time, based on configured grace periods and rounding policy rules. The rules allow the rounding policy to perform calculation of durations between actions that can later on be exported to an ERP system.
Can Be Assigned To:
System
Employee Group (FACILITY or POLICY_GROUP)Employee
Default System Setting: SYSTEM_DEFAULT
A Schedule Policy is used to define how certain scenarios within a schedule should be handled. See Schedules for details about the Schedules feature.
Can Be Assigned To:
System
Employee Group (FACILITY or POLICY_GROUP)Employee
Default System Setting: None
Security Data Roles either limit or increase the user's access to data in the application. You limit the data access by adding Data Restriction items to a role. You increase the data access by adding Supervisor Admin rights to a role.
Can Be Assigned To:
System
Employee Group (FACILITY or POLICY_GROUP)Employee
Default System Setting: Default
Security Roles are used to access to the various forms in the application. Each security role can be set up to enable a unique set of forms. Because Security Roles allow you to restrict certain users from using certain forms, you can create as many Security Roles as you find necessary.
The default security role does not have access to any forms in the application.
If a person is assigned to more than one Security Role, then the person will have the security permissions defined in all the roles at the highest settings preference.
For example, a person is assigned to two Security Roles in the Employee Setting form: Employee (contains only the Self Service menu forms) and Admin (contains only the Administration menu forms). This person is also assigned to two Security Roles via System Settings: Employee and Supervisor (contains only the Manage menu forms). The Employee Setting has precedence over the System Settings. Therefore the person has access to the forms in the Employee and Admin Security Roles. If the person did not have any Security Roles in the Employee or Employee Group Settings, then the Security Roles in System Settings would take precedence. In this case, the person would have access to the forms in the forms in the Employee and Supervisor Security Roles.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: None
A Shift Policy determines if an employee’s shift premium is decided by the shift defined in the employee's Shift Policy or the shift defined in the employee's Schedule. If the employee has no Shift Policy, the shift listed in the employee's Person Assignment applies. Shift Policies are created in the Shift Policy form. The actual shifts are created in the Shift Definition form.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: SYSTEM_DEFAULT
A Sign Policy determines if/when a time reporter and/or supervisor is required to sign a timecard, and what actions a sign/unsign action may trigger. Sign policies are configured in the Sign Policy form.
Can Be Assigned To:
Person Group (FACILITY only)
Terminal
Terminal Profile
Default System Setting: None
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.
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 neither of these settings are configured, the STATE_CODE prompt will be blank.
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. If this setting is not configured, the STATE_CODE prompt will be blank.
Can Be Assigned To:
System
Employee
Default System Setting: Disabled
This setting determines whether a password is required when a supervisor signs or unsigns an employee's timecard.
When this setting is Enabled and the supervisor clicks the Sign or Unsign button on an employee's timecard, the system will display a pop-up form. The supervisor must enter his or her application login password and click OK to sign or unsign the employee's timecard.
When this setting is Disabled, the system will not prompt the supervisor for a password when signing or unsigning an employee's timecard.
Note: If a supervisor is viewing his or her own timecard, the Employee Authentication on Sign setting will apply.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: SYSTEM_DEFAULT
The Time Off Request Policy determines the settings at which an employee can request time off via the Time Off Request form or a client terminal. Time Off request policies are configured in the Time Off Request Policy form.
Can Be Assigned To:
System
Employee Group (FACILITY or POLICY_GROUP)Employee
Default System Setting: hh:mm:ss a
Time Pattern determines how time is displayed in forms that have a timestamp field, such as Add Punch or Schedule Cycle.
Capital "H" indicates the hour in military (24-hour) time. Lowercase "h" indicates the hour in standard 12-hour time. An "m" indicates minutes and an "s" indicates seconds. An "a" indicates AM or PM is included in the timestamp.
Available options are listed below. An example of each format is shown for the timestamp 2:46:11 p.m.:
H:mm - 14:46
H:mm:ss - 14:46:11
hh:mm - 02:46
hh:mm a - 02:46 PM
hh:mm:ss - 02:46:11
hh:mm:ss a - 02:46:11 PM
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Terminal Profile
Default System Setting: Eastern Standard Time (America/New_York)
The default timezone (defined in the System Settings form) is Eastern Standard Time (America/New_York).
If a person does not have a timezone configured in a Person or Person Group setting, the Timezone specified in the System Settings will be used.
Timezone can also be configured for a Terminal Profile. The Timezone in the Terminal Profile will override the Timezone System Setting, Person Group Setting, or Person Setting.
You can also change the timezone in the Current Situation form to view employees in a particular time zone for a particular date. To do so, you need to make the As Of Timezone and As Of Date fields visible in the Current Situation form.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Default System Setting: SYSTEM_DEFAULT
When you check Show Only Exceptions in the Time Card Review form, only the records with exceptions that are enabled in the person’s Warning Policy will be displayed. This option allows supervisors to quickly view only those employees whose timecards need further review before signing. Exceptions include the following:
Employees who have not signed all the specified days on their timecards
Employees whose hours worked do not match their scheduled hours
Employees who worked outside their schedule, even if the total number of hours worked matches their scheduled hours
Employees with paid hours that received a rate other than the standard rate
Employees with excused or unexcused absences
Can Be Assigned To:
System
Employee Group (FACILITY or POLICY_GROUP)Employee
Default System Setting: Employee/Person/PIN Validation
Recommended Setting: LDAP User/Password Validation
Determines how the system authenticates the user when he or she attempts to log in to the application. The options are:
Person/PIN Validation - The user is authenticated against the Login Name and Password combination in the application database. The Login Name is listed on the Employee form. If you select this authentication method, you should set your Algorithm in the Product form to PBKDF2.
LDAP User/Password Validation - The user is authenticated against the directory service provider identified in the user's LDAP Policy. Note that an LDAP Policy must be configured and assigned to an Employee, Employee Group or System Setting. See LDAP Authentication Feature for more information. This setting is the recommended authentication method because it is more secure than Person/PINValidation.
Can Be Assigned To:
System
Employee Group (FACILITY or POLICY_GROUP)Employee
Default System Setting: None
The Web Terminal Manager Menu setting is used to make certain events available only to supervisors who are modifying employee timecards.
This setting assigns a Menu Tree to the supervisor. The events in this Menu Tree will only be available when the supervisor is modifying employee timecards (e.g., in the Supervisor Review form). These events will not be available in the Self Service Time Card.
If a supervisor does have this setting, when the supervisor is modifying an employee’s timecard, the available events will include the Web Terminal Manager Menu events and the events that are normally available to the employee (the events in the employee’s Menu Tree).
If a supervisor does not have this setting, when the supervisor is modifying an employee’s timecard, the supervisor will only have access to the events that are normally available to the employee (the events in the employee’s Menu Tree).
Note that the events in the Web Terminal Manager Menu will not be restricted by Event Filtration.
If you also want to prevent employees from modifying or deleting the events that only the supervisor can access, you can use the Event Posting Restriction feature.
Can Be Assigned To:
System
Person Group (FACILITY or POLICY_GROUP)
Person
Terminal Profile (Menu Group Name field)
Default System Setting: None
A Menu Tree determines which events are available to an employee posting time and to the employee’s supervisor when modifying the employee’s timecard. The event’s in a person’s Web Terminal Menu will be restricted based the person’s Event Filtration group.
Menu Trees are also assigned to Terminal Profiles (in the Menu Group Name field). The Web Terminal Menu setting will override the Terminal Profile’s Menu Group for the web timecard, Web Time Clock, Mobile Client, and Mobile Web Application.
When a supervisor modifies an employee’s timecard, the supervisor will have access to the same events as the employee (based on the employee’s Web Terminal Menu or Terminal Profile Menu Group Name and the employee’s Event Filtration settings). However, you can allow supervisors to access additional events with the Web Terminal Manager Menu setting.
If a person is not assigned a Web Terminal Menu, the system will use the Menu Group Name in the Terminal Profile. If the Terminal Profile also does not have a Menu Group Name, an error will display when the person tries to post an event.