Baton Rouge Srv Ctr Specs WTK v6.1 rev3.pdf
Transcript of Baton Rouge Srv Ctr Specs WTK v6.1 rev3.pdf
Filename: Baton Rouge Specs WTK v6.1
Version Date: March 30, 2010
Product Design
Document
Workforce Timekeeper v6.1
Dresser-Rand Baton Rouge Service Center
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 2 of 33
DOCUMENT CONTROL
Filename Baton Rouge Specs WTK v6.1 rev3.doc
Customer Name Dresser- Rand
Solution ID
Engagement ID
Original Author(s) Jordan Lara
Revision Author(s) Jordan Lara
REVISION HISTORY
Version Date Author (s) Revision Notes
1 2/15/2010 Jordan Lara Baton Rouge Pay Rule functional specification document
2 3/22/2010 Jordan Lara Adjustments to Field Premium Pay Amts
3 3/30/2010 Jordan Lara Adjustments related to call in pay, night shift prem, and break rules. 3.2.2, 3.5.2.1, and 3.12.2.1
4
5
6
7
APPROVALS DISTRIBUTION LIST
Copy No Approver Name Title Approval Date
1 Jenine Bogrand HRMS Sr. Manager
2 Chris Laurin Service Center Manager
3 Johnny Zeringue Baton Rouge Service Ctr Controller
4
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 3 of 33
TABLE OF CONTENTS
1 INTRODUCTION 5
1.1 DOCUMENT PURPOSE 5
2 GLOBAL SETTINGS 6
2.1 PAY PERIOD / FIXED RULE INFORMATION 6 2.1.1 DEFINITION 6 2.1.2 PRACTICES 6 2.2 LABOR LEVELS 7 2.2.1 DEFINITION 7 2.2.2 PRACTICES 8 2.3 PAY CODES 9 2.3.1 DEFINITION 9 2.4 NAMING CONVENTIONS 14 2.4.1 DEFINITION 14 2.4.2 PRACTICES 14 2.5 COMMENTS 15 2.5.1 DEFINITION 15 2.5.2 CUSTOM 15 2.6 CUSTOM FIELDS 16 2.6.1 DEFINITION 16
3 BUSINESS UNIT SETTINGS – BUILDING BLOCKS 17
3.1 ROUNDING RULES 17 3.1.1 DEFINITION 17 3.1.2 PRACTICES 17 3.2 SHIFT GUARANTEES 18 3.2.1 DEFINITION 18 3.2.2 PRACTICES 18 3.3 EXCEPTIONS 19 3.3.1 DEFINITION 19 3.3.2 PRACTICES 20 3.4 HOLIDAYS 21 3.4.1 DEFINITION 21 3.4.2 PRACTICES 21 3.5 PUNCHED BREAKS 22 3.5.1 DEFINITION 22 3.5.2 PRACTICES 22 3.6 AUTOMATIC BREAK DEDUCTIONS 23 3.6.1 DEFINITION 23 3.6.2 PRACTICES 23 3.7 OVERTIMES 23 3.7.1 DEFINITION 23 3.7.2 PRACTICES 23 3.8 ZONES 24 3.8.1 DEFINITION 24 3.8.2 PRACTICES 24 3.8.3 COMBINATION RULE NAMES: 24 PAY CODE DISTRIBUTION RULES: 25
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 4 of 33
3.8.4 DEFINITION 25 3.9 WORK RULES 26 3.9.1 DEFINITION 26 3.9.2 PRACTICES 26 3.10 SIGN-OFF RESTRICTIONS 26 3.10.1 DEFINITION 26 3.10.2 PRACTICES 26 3.11 TIMECARD PRE-POPULATION 27 3.11.1 DEFINITION 27 3.11.2 PRACTICES 27 3.12 MANUAL PROCESSES 27 3.12.1 DEFINITION 27 3.12.2 PRACTICES 27
4 BUSINESS UNIT SETTINGS - PAY RULES 28
4.1 DEFINITION 28 4.2 PRACTICES 29 4.2.1 PAY RULE DETAIL 29
5 BUSINESS UNIT SETTINGS - ACCRUAL RULES 30
5.1 ACCRUAL RULES 30 5.1.1 DEFINITION 30 5.1.2 ACCRUAL RULES 31 5.1.3 ACCRUAL PROFILES 32
6 ACCEPTANCE – SIGN OFF 33
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 5 of 33
1 INTRODUCTION
1.1 DOCUMENT PURPOSE The information contained within this document will detail the configuration that is required to be implemented within Workforce Timekeeper 6.0 for Dresser-Rand Baton Rouge Service Center payment policies. The information contained in this document is based on the submitted surveys and interviews with the Dresser-Rand Baton Rouge Service Center personnel.
This document is split into two (2) major sections:
• Global Settings – The settings that are contained within this section are applied across the entire WTK configuration such that any changes made to a component within this section are applied across all pay rules that use that particular component.
• Business Unit Settings – Split into two sub-sections i) Building Blocks and ii) Pay Rules. These are the settings that are only applicable to, or that can be different across, the various business units.
Please read this document thoroughly as it outlines the system configuration for Dresser-Rand Baton Rouge Service Center. Any features or functionality not mentioned herein will not be included in the solution build.
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 6 of 33
2 GLOBAL SETTINGS
2.1 PAY PERIOD / FIXED RULE INFORMATION
2.1.1 DEFINITION A pay period or fixed rule represents a normal pay cycle. It can be weekly, bi-weekly, semi-monthly or monthly. It must have a starting date and time and an ending date and time. It also contains information on where time is applied when a shift spans multiple days.
2.1.2 PRACTICES WTK information will be interfaced into Dresser-Rand Baton Rouge Service Center’s payroll system on a per period basis.
The following table shows details of pay periods for Dresser-Rand Baton Rouge Service Center:
Pay Period Name
Pay Cycle Length
Start Day
End Day
Day Divide
Work Across Midnight
Hours Belong To
Pay Period Ref. Date
Payroll Process Day
Weekly-In Weekly Mon Sun 12.00 AM
Yes Scheduled IN Day
Monday, 04/02/07
Mon
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 7 of 33
2.2 LABOR LEVELS
2.2.1 DEFINITION The Labor Level structure is integral to the configuration of the system. The Labor Level structure represents the current Reporting Structures and Costing within Dresser-Rand Baton Rouge Service Center.
Labor Levels are the categories that define Dresser-Rand Baton Rouge Service Center’s Costing and Reporting Structure and / or Job Functions. Labor Level Entry Values define the structure within each Labor Level.
Labor Accounts consist of a combination of Labor Level Entry Values. This combination consists of one entry from each labor level. Labor accounts will allow you to clearly visualize the Account for costing and general ledger accounting purposes. Labor Accounts can also be used to restrict the employee groups that Managers can view and edit.
The following table shows labor account options per terminal.
4500 Terminals with numeric key pad Only
Transfer with Swipe Badge
Numeric entries Only
Transfer with Key Pad
Numeric entries Only
Transfer using clock list
Alpha-numeric allowed
Ad hoc Entries at Clock
Numeric entries Only
Max Entry length at clock
20
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 8 of 33
2.2.2 PRACTICES
2.2.2.1 Labor Level Structure The following table shows details of labor level structure for Dresser-Rand Baton Rouge Service Center:
Level No.
Level Description Short Name (Abbreviation)
Min Length of Entries
Max Length of Entries
Sample Entry Sample Description
Transfer to Payroll (Y/N)
Transfer Level at Terminal (Y/N)
Create Ad Hoc Entries at Terminal Timecard (Y/N)
Data Entry Supplied By
1 RUI Location RUI 1 20 346 SD Srv Ctr N N N Payroll
2 Job JOB 1 20 ENG Engineering Development. Manager
Y N N Payroll
3 Supervisor SUP 1 20 113 John Case N N N Payroll
4 Type TYPE 1 20 FR Full Time Regular N N N Payroll
5 Department DEPT 1 20 280 200.201000.ENG-Product CC
Y Y N Payroll
6 Temporary Rate Change
TEMP 1 20 0 Inspector, 24.05 Y N N Payroll
7 Reserved 3 RES3 1 20 0 Default N N N N/A
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 9 of 33
2.3 PAY CODES
2.3.1 DEFINITION Pay Codes can be setup in the following ways:
• Most pay Codes will directly relate to an appropriate code within the payroll system
• Some Pay Codes can be created to have no bearing on payments in payroll and can be used purely for reporting purposes in WTK
• Pay Codes can have a naming convention or numbering in WTK that is different from that in payroll, and if so, can be matched up via a mapping or translation file when the information is extracted from WTK and sent to the payroll system
Pay Codes can hold either Hours or money. Money pay codes are used for automatic bonuses and manual transactions.
Pay Codes will be automatically added to the timesheet when the punches of the employees are interpreted by WTK (totalized), or they may be added manually to the timesheets of an employee when required.
Examples of pay codes are 100-US-REG, 200-US-OT1.5, 209-US-DBL2.0, 300-US-PVC.
Pay Codes can be added at any time into the system, however, it must be remembered that a further procedure is required to enable this new code to interface to the payroll system.
Combined Pay Codes are totals of several individual Pay Codes.
For example, you could create a combined pay code named TOTAL NP that is a sum of all non productive pay codes, such as Sick, Vacation, and Personal.
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 10 of 33
2.3.1.1 General Codes
Pay Code Name Short Name
Time or Money
Display on Totals tab in Timecard
Display in totals column on Timecard (shift totals)
Display on
Reports
Edit Counts toward OT limits
Edit Counts toward Consecutive Day OT
Edit Excuses Absence
Edits repeat on scheduled days until cancelled
Multiplier Add
Should this Code be passed to Payroll?
Regular 100-US-REG T Yes Yes Yes Yes No Yes No 1.0 No Yes
Double Time 209-US-DBL T Yes Yes Yes No No Yes No 2.0 No Yes
Holiday 413-US-HOL T Yes Yes Yes No No Yes No 1.0 No Yes
Jury Duty 620-US-JD T Yes Yes Yes No No Yes No 1.0 No Yes
Bereavement 621-US-BRV T Yes Yes Yes No No Yes No 1.0 No Yes
Vacation 319-US-PVC T Yes Yes Yes No No Yes No 1.0 No Yes
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 11 of 33
Pay Codes Continued:
Pay Code Name Short Name
Time or Money
Display on Totals tab in Timecard
Display in totals column on Timecard (shift totals)
Display on Reports
Edit Counts toward OT limits
Edit Counts toward Consecutive Day OT
Edit Excuses Absence
Edits repeat on scheduled days until cancelled
Multiplier Add
Should this Code be passed to Payroll?
Sick (Unpaid) 500-US-SCK T Yes Yes Yes No No Yes No 1.0 No No
Excused Absence
507-US-XAB T Yes Yes Yes No No
Yes No 1.0 No
No
Unexcused Absence
508-US-UAB T Yes Yes Yes No No
Yes No 1.0 No
No
Disciplinary Action Unpaid
603-US-DAU T Yes Yes Yes No No
Yes No 1.0 No
No
Overtime 200-US-OT T Yes Yes Yes Yes No Yes No 1.5 No Yes
Holiday Worked
401-US-HLW
T Yes Yes Yes No No
Yes No 2.0 No
Yes
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 12 of 33
Pay Codes Continued:
Pay Code Name Short Name
Time or Money
Display on Totals tab in Timecard
Display in totals column on Timecard (shift totals)
Display on Reports
Edit Counts toward OT limits
Edit Counts toward Consecutive Day OT
Edit Excuses Absence
Edits repeat on scheduled days until cancelled
Multiplier Add
Should this Code be passed to Payroll?
FMLA 503-US-FML T Yes Yes Yes No No Yes No 1.0 No No
Roving Holiday 320-US-ROV T Yes Yes Yes No No Yes No 1.0 No Yes
2nd Shift Prem 1.00 800-US-2ST T Yes Yes Yes No No Yes No 1.0 No Yes
2nd Shift Prem OT 1.50
802-US-OT2 T Yes Yes
Yes No No
Yes NO 1.0 No
Yes
2nd Shift Prem DT 2.00 804-US-DT2
T Yes Yes Yes No
No Yes
No 1.0 No Yes
Field Premium 1.00 836-US-Field Premium T Yes Yes
Yes No No
Yes No 1.0 No
Yes
Field Premium OT 1.50
837-US-Field Premium OT T Yes Yes
Yes No No
Yes No 1.0 No
Yes
Field Premium DT 2.00
838-US-Field Premium DT
T Yes Yes Yes No
No Yes
No 1.0 No Yes
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 13 of 33
Pay Codes Continued:
Pay Code Name Short Name
Time or Money
Display on Totals tab in Timecard
Display in totals column on Timecard (shift totals)
Display on
Reports
Edit Counts toward OT limits
Edit Counts toward Consecutive Day OT
Edit Excuses Absence
Edits repeat on scheduled days until cancelled
Multiplier Add
Should this Code be passed to Payroll?
Leadman Premium 1.00 826-US-LMP T Yes Yes Yes No No Yes No 1.0 No Yes
Leadman OT 1.50 827-US-LMO T Yes Yes Yes No No Yes No 1.0 No Yes
Leadman DT 2.00 828-US-LMD T Yes Yes Yes No No Yes No 1.0 No Yes
In some cases generic leave codes are used and comments can be added for more detail.
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 14 of 33
2.3.1.2 Combined Codes
THE FOLLOWING ARE COMBINED PAY CODES TO BE CONFIGURED:
Combined Pay Code Name
Time or Money
Display Totals in Timecard
Display Totals on Reports
Total Hrs Worked
T N Y
Non Productive Hours
T N Y
2.4 NAMING CONVENTIONS
2.4.1 DEFINITION This section contains the common naming conventions that will be used for pay rules, work rules, building blocks (if applicable), device groups, schedule groups, & labor level sets.
Sample:
It is important, at this point, to discuss the naming conventions for all pay rules. We have some rules that will be distinctively different from site by site. To easily distinguish one site’s pay rules and building blocks from another it is advisable to adopt a naming strategy such as the example in the table below.
It is the recommendation of Kronos that the above naming convention be used for ease of use in terms of understanding from any users’ point of view.
2.4.2 PRACTICES The following are some examples of naming conventions:
The naming convention will start with first three digits of the Location followed by a dash, then a description. For example, SC-1st-Shift” will be the name of a pay rule.
All rules will be prefixed by the proper Site abbreviation
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 15 of 33
2.5 COMMENTS
2.5.1 DEFINITION A comment is predetermined descriptive text that a user can associate with amounts, punches, shifts, schedules, and historical amounts. You can use comments to manage employee activity, communicate information between users, and identify problems by tracking the reasons for the edit. For example, you can indicate why an employee received a particular bonus or why an employee punched in late.
Use the Comments module to create comments. You can also inactivate, reactivate, and delete comments from this module. You can also attach and view comments on amounts, punches, and historical amounts in the Timecard Editor, Schedule Editor, and Group Edits modules.
As comments appear in alphabetical format, it is recommended that the organization’s naming conventions are understood by users entering comments, e.g., you don’t want to have four different comments meaning the same thing
2.5.2 CUSTOM The following comments have been requested by SC, in addition to the comments already in the system:
Name/Number of Comment All Shifts Punch Pay
Code
Pay From
Sched
Refer to Kronos for full list of available comments.
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 16 of 33
2.6 CUSTOM FIELDS
2.6.1 DEFINITION Up to 10 custom fields can be created in order to be able to capture detailed information for employees such as emergency contact details, Social Security Number, pay group, etc. These fields can also be used for reporting or output purposes.
The following example shows customer fields that are currently setup in Kronos:
Custom Field Description Expected Value to be Entered
1 Legacy ID Import from Oracle
2 Organizational Name Import from Oracle
3 Expenditure Type Import from Oracle
4
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 17 of 33
3 BUSINESS UNIT SETTINGS – BUILDING BLOCKS
The items that are listed within this section are the groups of parameters that will be used to build Baton Rouge Service Center’s specific pay rules. After a building block is created, they can be reused in different work rules as required by Baton Rouge Service Center along with reusing commonly used items between employees.
3.1 ROUNDING RULES
3.1.1 DEFINITION Rounding is a way to simplify payroll accounting and reporting, and to enforce shift start and end times. Punch rounds divide Hours into even increments of an Hour. Graces determine whether an employee's shift start and end times move backward to the previous round increment or forward to the next round increment. If shift start and end times occur during the grace period, they round back to the previous round increment. If shift start and end times occur after the grace period, they round forward to the next round increment.
For example, the following occurs with a rounding to the closest 15 minute mark is used with in punches early or late:
A 07:07 punch rounds to 07:00. (The punch rounds back to the next increment).
A 07:15 punch rounds to 07:15. (The punch stays minute to minute).
A 06:54 punch rounds to 07:00. (The punch rounds forward to the next increment).
3.1.2 PRACTICES The WTK setup for Dresser-Rand Baton Rouge Service Center will be configured with the following rounding rules, which will apply as detailed in the Pay Rule tables:
Rounding Rule Name: QTR-Rounding
Early In Punch
Punch Time Round/Grace Effective Time
Example: Scheduled start time = 07:00
0654 Rounds to 0700
0644 Rounds to 0645
All punches, regardless of scheduled start time, will round to the nearest quarter Hour.
0629 Rounds to 0630
Late In Punch
Punch Time Round/Grace Effective Time
Example: Scheduled start time = 07:00
0701 Rounds to 0700
0705 Rounds to 0700
0708 Rounds to 0715
All punches, regardless of scheduled start time, will round to the nearest quarter Hour.
0908 Rounds to 0915
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 18 of 33
Early Out Punch
Punch Time Round/Grace Effective Time
Example: Scheduled finish time = 17:00
1659 Rounds to 1700
1654 Rounds to 1700
All punches, regardless of scheduled start time, will round to the nearest quarter Hour.
1637 Rounds to 1630
Late Out Punch
Punch Time Round/Grace Effective Time
Example: Scheduled finish time = 17:00
1701 Rounds to 1700
1706 Rounds to 1700
1740 Rounds to 1745
All punches, regardless of scheduled start time, will round to the nearest quarter Hour.
1752 Rounds to 1745
Unscheduled Punches and Labor Account Transfers
All Unscheduled In and Out punches will be rounded minute to minute.
3.2 SHIFT GUARANTEES
3.2.1 DEFINITION Shift Guarantees apply a minimum payment (HH.DD) when an employee has not worked their full entitlement and are guaranteed full payment for a particular shift.
3.2.2 PRACTICES All applicable shift guarantees are defined in each associated Pay Rule.
SC guarantees 4 paid Hours per shift for call ins Only.
BRSC Guarantees 4 hours straight time, regardless of how many other hours worked in the day or week, as well as lead man premium on weekends as call in pay for lead men. ???
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 19 of 33
3.3 EXCEPTIONS
3.3.1 DEFINITION Exceptions are used for reporting and as an employee selection tool. Their purpose is to bring extra attention to an occurrence for attendance or reporting purposes. They have no affect on Hour calculations.
Early and Late exceptions will be triggered when an employee has a schedule in the system, while other interval based exception will work regardless.
Exception Description
Unscheduled Punch Shows all employees who have not been scheduled to work and have a punch for that day.
Long Interval Shift This exception defines an unusually long period of time between an in-punch and an out-punch
Short Shift This exception occurs if the rounded shift length is less than or equal to the short shift setting.
IN Punch Very Early Exceptions for very early in-punch appear because employees punch-in very much before their scheduled start time.
IN Punch Early Exceptions for early in-punch appear because employees punch-in before their scheduled start time.
IN Punch Late Exceptions for late in-punch appear because employees punch-in after their scheduled start time.
OUT Punch Early Exceptions for early out-punch appear because employees punch-out before their scheduled end time.
OUT Punch Late Exceptions for late out-punch appear because employees punch-out after their scheduled end time.
OUT Punch Very Late Exceptions for very late out-punch appears because employees punch-out much after their scheduled end time.
Long Meal or Break Exception This exception defines a long period of time between an out punch for meal or break and a returning in-punch.
Short Meal or Break Exception This except defines a long period of time between an out punch for meal or break and a returning in-punch.
Absent This exception will appear if an employee is scheduled to punch in, and does not punch in.
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 20 of 33
3.3.2 PRACTICES Exceptions identify when shifts deviate from normal work patterns and are included in WTK Reporting. The following are the Exception Rules, which will be configured for Dresser-Rand Baton Rouge Service Center.
The following table/s shows the exceptions that will be used for Dresser-Rand Baton Rouge Service Center and will be applied as detailed in the Pay Rule Tables:
Exception Rule Name
Unscheduled Long Interval
Short Shift
Very Early In
Early In
Late In
Early Out
Late Out
Very Late Out
SC-Exceptions Yes Over 14 Hours
5 Hours or less exception
30 8 More than 1 Min
8 8 15
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 21 of 33
3.4 HOLIDAYS
3.4.1 DEFINITION Holiday Credit – Employees may be given an amount of time or money automatically on dates detailed in the Holiday Table.
Holiday Worked – Any Hours worked on dates detailed in the Holiday Table may be paid differently. The Holiday’s start and end time will be taken in to account.
The individual Pay Rule’s configuration will determine whether the selected dates will trigger “Holiday Credit” and/or “Holiday Worked” payments.
3.4.2 PRACTICES The following table indicates the holidays for the Baton Rouge Service Center site.
Holiday Name Date Start time
Date Finish Time
Applies To Calendar Group(s)
US-2010 New Years Day
01/01/2010 0:00 01/02/2010 0:00 Srvc Ctr
US-2010 Good Friday 04/02/2010 0:00 04/03/2010 00:00 Srvc Ctr
US-2010Memorial Day 05/31/2010 0:00 06/01/2010 0:00 Srvc Ctr
US-2010 Independence Day
07/05/2010 0:00 07/06/2010 0:00 Srvc Ctr
US-2010 Labor Day 09/06/2010 0:00 09/07/2010 0:00 Srvc Ctr
US-2010 Thanksgiving
11/25/2010 0:00 11/26/2010 0:00 Srvc Ctr
US-2010 Day After Thanksgiving
11/26/2010 0:00 11/27/2010 0:00 Srvc Ctr
US-2010 Christmas Eve
12/24/2010 0:00 12/25/2010 0:00 Srvc Ctr
US-2010 Christmas Day
12/27/2010 0:00 12/28/2010 0:00 Srvc Ctr
US-2010 New Year’s Eve
12/31/2010 0:00 1/01/2011 0:00 Srvc Ctr
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 22 of 33
3.5 PUNCHED BREAKS
3.5.1 DEFINITION This section deals with meal and break practices. These meals and breaks can be paid or unpaid, automatically deducted, or require employees to punch in and out. This time is traditionally used for a meal break, but can be for doctor’s appointments, family emergency, or any work stoppage in the middle of a shift. If an employee punches for a meal the interval of time that they are out will be rounded according to the rules below.
3.5.2 PRACTICES The WTK setup for Baton Rouge Service Center will be configured with the following punched break rules, which will apply as detailed in the Pay Rule Tables:
3.5.2.1 Break Rule Name1: SC-30 Min unpaid break Baton Rouge full-time Hourly employees get a 15 minute paid break that they will not clock out for, and a 30 minute unpaid lunch. Note: If the employee clocks out for lunch and it is more than 30 minutes they will be docked the all time off the clock. 2nd Shift workers also get an unpaid 30 min lunch auto-deduction. These auto-deductions also apply on Saturday and Sunday.
For example:
Swipe Out: 12:00 and Back In at: 12:32 = 32 minute break = 32 minute deduction
Swipe Out: 20:00 and Back In at: 20:20 = 20 minute break = 30 minute deduction
Meal /Break Rule Name
Normal Length
Short Meal Round
Short Meal Grace
Long Meal Round
Long Meal Grace
Max Meal Paid Amt
SC-30 Min unpaid break 7 days
30 0:20 0:00 0:01 0:00 1:00 0:00
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 23 of 33
3.6 AUTOMATIC BREAK DEDUCTIONS
3.6.1 DEFINITION Deductions are amounts of time that are automatically deducted from an employee’s timecard. As a part of this configuration the following deductions will be configured for Baton Rouge Service Center. This deduction is applicable to employees as per their pay rule, and will be based on employees in punch time.
3.6.2 PRACTICES The WTK setup for Baton Rouge Service Center will be configured with the following deductions:
More than 5 Hours worked = 30 min deduction
3.7 OVERTIMES
3.7.1 DEFINITION Overtime rules establish the limits and reset methods for accumulating overtime Hours. When employees work past a threshold limit within a specified time period, they start to earn overtime Hours. Overtime Rules may also require a minimum number of Hours necessary to qualify for the overtime pay.
3.7.2 PRACTICES Overtime is calculated on a daily basis, not a weekly one. OT and DT are paid as follows:
Straight Pay (Reg) Over time (1.5) Double Time Pay (2.0) First 8 Hours M-F Hours > 8 and < 12 M-F Hours > 12 on Monday-Saturday First 12 Hours on Saturday All Hours on Sundays, and Holidays Holidays, Vacation, Jury Duty, and all other non-worked paid days do not count towards Overtime. Doubletime does not count towards Overtime. Premium pay is not paid for paid non-worked days like Holidays, and Vacation.
The WTK setup for Baton Rouge Service Center will be configured with the following Overtime rules, which will apply as detailed in the Pay Rule Tables:
Rule Name Starts After Overtime Period
Minimum to Qualify Reset Reset On
8 Daily 8 Hrs Day 0 New Day Daily
12 Daily 12 Hrs Day 0 New Day Daily
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 24 of 33
3.8 ZONES
3.8.1 DEFINITION Zones define specific intervals of time where employees may earn extra pay or shift differentials. Zone rules establish the required number of Hours in a specified time period that an employee is required to work. For example, Evening, Night, Sunday, Weekend, and Consecutive days are zones that you can create.
Zones establish specified intervals of time as Hour types. The following are the zone types:
• Holiday • Daily shift differential • Weekend differential • Days of week
3.8.2 PRACTICES The WTK setup for will be configured with the following Zone rules, which will apply as detailed in the Pay Rule Tables:
Zone Rule Name Start Time
End Time
Min Zone [hrs]
Min Shift [hrs]
Must Start At / Or After
Must Start At /Or Before
Must End At /Or After
Must End At / Or Before
Holiday 0:00a 0:00a 0 0 N/A N/A N/A N/A
Sunday 0:00a 0:00a 0 0 N/A N/A N/A N/A
Saturday 0:00a 0:00a 0 0 N/A N/A N/A N/A
Note: If a day shift employee works one or more shifts on 2nd, he is paid shift premium for the Hours worked in the 2nd shift. Day shift employees are normally scheduled from 6 to 2:30p weekly.
Note: If the 2nd shift employee works on days he still gets his shift premium.
Note: If the shift change is per the employee’s request, the shift premium does NOT apply. This shift change will require a manual update to the employee’s timesheet.
3.8.3 COMBINATION RULE NAMES: The WTK setup for Baton Rouge Service Center will be configured with the following Combination rules, which will apply as detailed in the Work Rule Tables:
Name Selected Items
1st Shift Hol,Sun, Sat
SC-Holiday Over 12 Over 8 Saturday
Shift 1
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 25 of 33
Sunday
2nd Shift Hol, Sun, Sat
SC-Holiday Over 12 Over 8 Saturday Sunday
Shift 2
PAY CODE DISTRIBUTION RULES:
3.8.4 DEFINITION Pay code Distribution rules are the combination of Overtime combination, Zone combinations. These rules determine how employee Hours accrue. The WTK setup for Baton Rouge Service Center will be configured with the following Work rules, which are detailed in the table below:
Name Combination Rule
SC-1st Shift 1st Shift Hol,Sun, Sat
SC-2nd Shift 2nd Shift Hol, Sun, Sat
SC-Training-1st Shift 1st Shift Hol,Sun, Sat
SC-Training-2nd Shift 2nd Shift Hol, Sun, Sat
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 26 of 33
3.9 WORK RULES
3.9.1 DEFINITION Work rules are the combination of work rule building blocks, apply specific payroll rules to shifts. These rules determine how employee Hours accrue. The following Work Rules will be configured to represent each unique employee configuration group.
3.9.2 PRACTICES The WTK setup for Baton Rouge Service Center will be configured with the following Work rules, which are detailed in the table below:
Work Rule Name Round Break Rule/ Auto
Deduct Exception Name Zones/Overtime Pay code Distribution Name
SC-1st Shift QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8
SC-1st Shift
SC-2nd Shift QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8
SC-2nd Shift
SC-Field Pay QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8
SC-Field Pay
SC-Field Night QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8
SC-Field Night
SC-Leadman QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8
SC-Leadman
SC Field Lead QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8
SC Field Lead
SC-Field Night Lead
QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8
SC-Field Night Lead
3.10 SIGN-OFF RESTRICTIONS
3.10.1 DEFINITION Sign-Off Restrictions are conditions that can be assigned to an individual Pay Rule that prevents the Timecard from being Signed Off by the manager if any of the specified conditions are not met.
If the Sign-Off Restrictions option is used and the manager attempts to sign off the individual Timecard with any of the restrictions in force then a message is given advising the manager of this and the timecard is not signed off.
3.10.2 PRACTICES The following table/s shows the signoff restrictions that will be used for Dresser-Rand Baton Rouge Service Center and will be applied as detailed in the Pay Rule Tables:
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 27 of 33
3.10.2.1 Signoff Restriction Name: US-Sign-Off-Restrict
Missing Punch Unexcused Absence
Zero Hours Against Pay Code:
Yes No No
3.11 TIMECARD PRE-POPULATION
3.11.1 DEFINITION
The system can automatically populate employees' time cards with punches, pay code amounts, or durations from their assigned schedules. This feature is sometimes used for salaried employees, employees who schedule their time off, such as vacation, and employees who Only report exceptions to their normal work Hours.
3.11.2 PRACTICES The following table/s shows the Pay Rules that will be utilizing this pre-population feature and the method applied.
Pay Rule Name Pre-Population of Pay Code Amount Only
Pre-Population of Shifts and Pay Code Amounts
SC-1st-Shift No No
SC-2nd-Shift No No
3.12 MANUAL PROCESSES
3.12.1 DEFINITION Manual Processes are any additional functions that will be required to be performed by the manager and/or Employee in Order for correct payment of Hours in Kronos. Manual Processes can be as little as Approving Overtime, Work Rule Overrides required for Call Back scenarios to as extensive as additional Connect Links required to handle complex payment conditions.
3.12.2 PRACTICES Listed below are the Manual Processes identified by Kronos and Dresser-Rand Baton Rouge Service Center during the investigation of the payment conditions:
3.12.2.1 Night Shift Premium: Note: If a day shift employee works one or more shifts on 2nd shift, he is paid shift premium for the Hours he works on 2nd shift. Day shift employees are normally scheduled from 6 to 14:30 weekly. This shift change will require a manual update to the employee’s timesheet (work rule transfer).
Note: If the 2nd shift employee works on days, he does not receive his shift premium.
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 28 of 33
The conditions of Shift Premium are as follows.
• Monday through Friday - All Hours worked will include shift premium.
• Saturday – all Hours are OT, plus the OT shift premium.
• Sunday – all Hours at Double, plus the DT shift premium.
• Holidays – all Hours at Double, plus the DT shift premium.
Work Rule Name Round Break Rule/ Auto Deduct
Exception Name Zones/Overtime Pay Code Distribution
Name
SC-1st Shift QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8 SC-1st Shift
SC-2nd Shift QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8 SC-2nd Shift
SC-Field Pay QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8 SC-Field Pay
SC-Field Night QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8 SC-Field Night
SC-Leadman QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8 SC-Leadman
SC Field Lead QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8 SC Field Lead
SC-Field Night Lead QTR-Rounding SC-30 Min unpaid break SC-Exceptions Hol, Sat, Sun,Over12,Over8 SC-Field Night Lead
Note: The manager will be required to perform a Work Rule Transfer for these Hours applying the “Temporary Shift assignment” work rule which will then apply the above conditions.
4 BUSINESS UNIT SETTINGS - PAY RULES
4.1 DEFINITION A Pay rule is a rule made up of many building blocks (as previously outlined within this document) within the Kronos Database. This rule acts as the “award interpreter” to determine how an employee’s Hours will be paid within the system. A Pay rule is individually assigned to each employee with the People Editor in the Kronos Workforce Timekeeper database.
Workforce Time Keeper uses pay rules and work rules to pay all employees. The Pay Rule has a Work Rule attached as a default rule. There are other Work Rules existing in the database that are not attached to Pay Rules and these rules are used to force a particular payment for a particular day. For the naming conventions used to make up the pay rule names see “GLOBAL SETTINGS/NAMING CONVENTIONS” section of this document.
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 29 of 33
4.2 PRACTICES
4.2.1 PAY RULE DETAIL
Pay Rule Name Fixed Rule Default Work Rule Sign-Off Restrictions Holiday Credit
SC-1st Shift Weekly-In SC-1st Shift US-Restrict SC-HOL-Credit
SC-2nd Shift Weekly-In SC-2nd Shift US-Restrict SC-HOL-Credit
SC-Field Pay Weekly-In SC-Field Pay US-Restrict
SC-HOL-Credit
SC-Field Night Weekly-In SC-Field Night US-Restrict
SC-HOL-Credit
SC-Leadman Weekly-In SC-Leadman US-Restrict
SC-HOL-Credit
SC Field Lead Weekly-In SC Field Lead US-Restrict
SC-HOL-Credit
SC-Field Night Lead Weekly-In SC-Field Night Lead US-Restrict
SC-HOL-Credit
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 30 of 33
5 BUSINESS UNIT SETTINGS - ACCRUAL RULES
5.1 ACCRUAL RULES
5.1.1 DEFINITION An Accrual is an amount of time or money that people earn or accrue based on Hours worked or longevity with the company. Some people refer to these Accruals as benefit Hours. The Accrual Codes are the categories or "buckets" that hold accrual balances. The company's Accrual Rules determine how much time is granted for these codes. The Accrual Profile is assigned to the employee, and determines both which Accrual Codes the employee is eligible for and which Accrual Rules will be followed for them.
Dresser-Rand Vacation Policy:
Vacation Year is January 1 thru December 31 of each year.
Work requirements –
Vacation Schedule – Based on service as January 1
0 – 9 years 15 days
10 - 24 years 20 days
25 or more years 25 days
The following Accrual Codes are required by Dresser-Rand Baton Rouge Service Center:
Accrual Code Name Accrual Code Abbreviation
Earnings Calculated In
Balance Imported from Payroll
Display in timecard editor
Pay Codes that cause Balances to Decrease
Pay Codes that cause Balances to Increase
Vacation VAC HOURS No Yes 319-US-PVC None
The accrual balances can be either imported from the payroll system or granted based on the programmed accrual rules.
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 31 of 33
5.1.2 ACCRUAL RULES Allowing balances to be overdrawn is determined by each accrual code. Listed below are the overdraft rules for Dresser-Rand Baton Rouge Service Center.
Accrual Rule Name Allow Overdraft
Warn User when Balance is Negative?
Limit when Overdrafts are not allowed?
Allow Future Overdraft
Warn User when Future Balance is Negative?
Limit when Future Overdrafts are not allowed
Auto-approve Overdrafts during Import?
Auto-approve Overdrafts during Group Edits?
Vacation No N/A N/A No N/A N/A No No
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 32 of 33
5.1.3 ACCRUAL PROFILES Accrual profiles are collections of individual Accrual Rules. The Accrual Profile is assigned to the employee and therefore dictates which Accrual Rules are followed by the employee. The Accrual Rules will affect the Accrual Codes differently according to how they are programmed. All employees can use the Accrual Code SICK, but it is the rule that will determine how SICK get used.
The following Accrual Profiles are required by Dresser-Rand Baton Rouge Service Center:
Accrual Profile Name Description Included Accrual Rules
DR-ACCRUALS For all full time Hourly employees Vacation
Baton Rouge Srv Ctr Specs WTK v6.1 rev3.doc Page 33 of 33
6 ACCEPTANCE – SIGN OFF
Please read this document thoroughly, as it outlines the software methodology and the system configuration for Dresser-Rand Baton Rouge Service Center. Any features or functionality not mentioned herein will not be included in the solution build. Any additional requirements not mentioned within this document will be subject to standard Change Control procedures.
This Product Design document supersedes any previous written or verbal description regarding the operation of the Kronos system being implemented for Dresser-Rand Baton Rouge Service Center. The system defined in the statement accurately describes the requirements for our implementation.
Any changes to these requirements will be assessed on a case by case basis, and may involve the use of a “Project Change Request”. All Project Change Requests will be subject to joint agreement and may incur additional cost, time and other impacts to the Dresser-Rand Baton Rouge Service Center project.
Your signature below attests that you have read, understand and agree to the implementation solution put forth within this Workforce Product Design Document and that this document constitutes the full WTK configuration required to be performed by Kronos for Dresser-Rand Baton Rouge Service Center.
I understand and agree with the contents of this document as presented. I have reviewed it and am satisfied it will fulfill our current requirements. By signing this document I confirm I have the authority to do so on behalf of Dresser-Rand Baton Rouge Service Center.
Acceptance Certificate
Customer Name Dresser-Rand Baton Rouge Service Center
Document Title Product Design WTK v6.1_REV3.doc
Document Revision Date March 30, 2010
For and on behalf of Dresser-Rand Baton Rouge Service Center
Name Chris Laurin
Position Service Center Manager
Signed
Date
For and on behalf of Dresser-Rand GSP
Name Jenine Bogrand
Position HRMS Sr. Manager
Signed
Date