Below is a list of tips and tricks for the Administer Schedules and Rules course. Click on the links below to see information that may be helpful to you as you teach the course.
Role | User | Emp No | Employee Name | Position ID | Subordinate | ||
Emp No | Employee Name | Position ID | |||||
Teacher | ALAIN | 1002 | Alain Prost | HRM and PROD-0 | |||
Student | ALEX | 1004 | Alexander Danielsson | PROD-01 | 3002 | Don Bishop | TEAML-01 |
Student | DAVID | 1014 | David Coulthard | PROD-02 | 3003 | Bob Garnet | TEAML-02 |
Student | EDDIE | 1016 | Eddie Irvine | PROD-03 | 3004 | Diane Dutton | TEAML-03 |
Student | EMERSON | 1018 | Emerson Fittipaldi | PROD-04 | 3005 | Sylvia Smith | TEAML-04 |
Student | ENZO | 1020 | Enzo Ferrari | PROD-05 | 3006 | Roger Curtis | TEAML-05 |
Student | GIANCO | 1022 | Giancarlo Fisichella | PROD-06 | 3007 | Steve Hammond | TEAML-06 |
Student | JAQUES | 1026 | Jacques Villeneuve | PROD-07 | 3008 | Betsy Taylor | TEAML-07 |
Student | JEAN | 1028 | Jean Alesi | PROD-08 | 3009 | Chris Marshall | TEAML-08 |
Student | MARIO | 1034 | Mario Andretti | PROD-09 | 3010 | Sarah Pullman | TEAML-09 |
Student | MIKA | 1036 | Mika Häkkinen | PROD-10 | 3011 | Tim Taylor | TEAML-10 |
Student | MIKE | 1038 | Michael Schumacher | PROD-11 | 3012 | Al Borland | TEAML-11 |
Student | NIGEL | 1040 | Nigel Mansell | PROD-12 | 3013 | Norma Ray | TEAML-12 |
Explain that the ID of the wage class has to be unique and that every student has to have his/her own wage class in which he/she will be working during the rest of the course.
This is a difficult exercise since this is the student’s first encounter with the complexity of parameter settings in IFS/Time & Attendance. As a teacher, it is recommended that you go through the parameters and apply them to the wage codes that are created. Recommended parameter settings are:
Wage Code for | Conversion | Flex Handling | Repeating | Increment Handling | Free Day Covering | Overtime Subtract |
Sickness | Not converted | No flex subtraction | Repeated | No increments | Sickness over holiday, automatic removal (for Swedish market | Overtime reduced |
Vacation | Not converted | No flex subtraction | Repeated | No increments | No sickness over holidays | Overtime reduced |
Unpaid Absence | Not converted | No flex subtraction | Not Repeated | No increments | No sickness over holidays | Overtime reduced |
This is a simple example of parameter settings for absence wage codes, not suitable for all customers, but sufficient for the purpose of training.
In this exercise, students learn how to apply the double set of overtime wage codes which could cause some problems in the beginning of this lesson. The students add both wage codes in the respective column named Cash/Comp wage code, and learn to understand the interaction with a compensatory time balance.
Creating a Flex day rule is generally difficult for students. Common mistakes are:
The absence parameter causes the system to use the flex limits from the day type before generating absence when the employee clocks in as absent.
You should also demonstrate the interaction with the flextime balance.
The effects of the different calculation parameters are sometimes hard to understand for the students. There might be a need for the teacher to demonstrate and explain the effects of the different settings and their effects on the overtime/flex results that are calculated.
Use a clocking that starts one hour before normal time and ends one hour later than normal time. Clock in with overtime in the morning and clock out with flex (normal) in the afternoon. The options in the Calculation Parameter field are:
Option | Description |
No flex, overtime for actual clocking only | Overtime is issued for the morning and flex in the afternoon. |
No flex, overtime for both in and out | Overtime is issued for both morning and afternoon. |
Flex first, overtime for actual clocking only | The overtime will be converted into flex in the morning (if the flex limit is one hour or more). |
Flex first, overtime for both in and out | The overtime will be converted into flex in the morning (if the flex limit is one hour or more). |
Keep in mind when to use negative values for the parameters.
There are some common problem areas in this part of the course. The first is the design of day types, the second is creating the schedule cycle, and the last is the link between substitute schedules and working hours schedules.
Day Type:
One major problem students seem to have when creating day types is that they don’t understand how the day type defines the workday based on wage codes.
To make this more understandable, the teacher should define a work day by drawing a timeline. On this timeline, break down the workday in intervals of overtime, normal time and Lunch or breaks.
See the following example:
From 00:00 | From 08:00 | From 12:00 | From 13:00 | From 17:00 |
Overtime | Normal | Lunch | Normal | Overtime |
It is important that the students understand that all days in a week have to have a day type. It is not uncommon that students forget to create day types for weekends, which would create an error message if the employee clock in for an overtime work.
For public holidays, encourage the students to analyze how they themselves work on public holidays or days before public holidays. This usually clarifies the need for additional day types other than the ones already created.
The overtime priority flag has to be set on rows with overtime wage codes. If this isn't done, it can cause some problems when the students try to save.
Explain when it is required to use day types and when it is sufficient to enter "work hours sum" directly in the schedule details.
Cycle Schedules:
As with the day type, it may be a good idea to define a normal working week on a timeline, showing that the same day type is applicable to all days Monday through Friday, and a separate day type is used during the weekend, resulting in a one week cycle.
It’s quite common that students forget to connect the day types to the schedule.
Point out the importance of the "cycle start date" when extracting the cycle information for, e.g., a full year. Show an example using a calendar. Start with the simple one-week (one-shift) schedule and continue with a multi-week (multi-shift) schedule. Clarify that the shift, entered in the employee schedule assignment, together with the cycle start date entered in the cycle schedule definition, is the information needed to derive the correct schedule information for the employee.
Also show that the cycle can be extracted both for future dates and past dates. Use for instance the Employee Schedule Information window.
Day-by-Day Schedules:
Normally a cycle schedule will do. In extreme cases of scheduling where no cycle pattern can be found, a day-by-day schedule is the alternative. Note that the schedule start date and end date defines the validity of the day-by-day schedule.
Substitute Schedules:
A common mistake is that students forget to connect the substitute schedules to the working hours schedule.
This is a relatively easy exercise where students may experience minor problems such as:
There are two parts of this exercise that might cause some problems:
The periodic calculation normally won’t have any effect on the daily results in the Time Registration window, and the results of this calculation will only be visible in the Periodic Result form.
Point out how the periodic overtime rules actually can affect the daily calculation.