Why:
The recording of mechanic time in Fusion has been designed to follow certain guidelines. These help to make sure that the correct amount of time is paid for and at the correct rate of pay.
Where:
These rules do not need to be set up in Fusion, it's just important to be aware of them when using any of the time recording functions.
XFNSH Rule:
This can be used multiple times within a 24 hour period but calculations for the automatic payment category will not take place outside the shift core time.
For Example Calculations for automatic payments are only made up to the 1st XFNSH and any subsequent ones are not calculated.
XCLEN = Workshop Cleaning 02:00 AA.
XFNSH (1) = Finishing Time 04:00 EE.
XCLEN = Workshop Cleaning 07:00 AC.
XCLEN = Workshop Cleaning 08:00 AA.
XLNCH = Unpaid Meal Breaks (CODE EE) 12:00 EE.
XCLEN = Workshop Cleaning 13:00 AA.
XCLEN = Workshop Cleaning 17:00 AB.
XFNSH (2) = Finishing Time 18:00 EE.
XCLEN = Workshop Cleaning 21:00 AA.
XFNSH (3) = Finishing Time 23:00 EE.
To make sure that payment categories re-calculate, the first and the second XFNSH must be changed to XSTBY (see below). Because the XSTBY has been inserted select the ‘Refresh’ icon and the payment categories will re-calculate.
XCLEN = Workshop Cleaning 02:00 AC.
XSTBY = Standby (CODE EE) 04:00 EE.
XCLEN = Workshop Cleaning 07:00 AC.
XCLEN = Workshop Cleaning 08:00 AA.
XLNCH = Unpaid Meal Breaks (CODE EE) 12.00 EE.
XCLEN = Workshop Cleaning 13:00 AA.
XCLEN = Workshop Cleaning 17:00 AB.
XSTBY = Standby (CODE EE) 18:00 EE.
XCLEN = Workshop Cleaning 21:00 AB.
XFNSH = Finishing Time 23:00 EE.
XSCON Rule:
Please note that time recorded across the hour of midnight, when using XSCON in manual time recording, must be immediately followed by a 00:00 (midnight) clock-in on the subsequent day.
XSCON must be set up with a blank payment category within the non productive table.
Rule for Clocking While on Holiday:
If a mechanic has clocking's whilst on holiday, then these records will be added at the default payment code registered in the Parameter File and these will have to be changed manually. Alternatively the holiday exception should be removed and the appropriate shift clocking pattern should be registered as an exception.
Rule for Clocking Call Outs Over Midnight (Dayshift):
If a mechanic has a call out over midnight within manual time recording, normally only one XFNSH is allowed per day.
When a mechanic shift ends, then XSTBY should be used and an XFNSH record created at 24:00 with a start record of 00.00 the next day.
If a mechanic uses online time recording for a call out over midnight, then an XSCON will be created at 24:00 and the job will be started again the next day at 00.00.
When he clocks off the next morning an XFNSH record will be created.
After any subsequent calls outs are recorded or he completes his shift with an XFNSH, then report THP1035 will be generated listing any days to be reviewed.
From the dates on this report any XSCON should be changed to XFNSH for end of day and any duplicate XFNSH in the same day changed to XSTBY.
Press the Refresh icon on both days to update the data.
Auto Multiple XFNSH Report THR1035:
This report will automatically run if a mechanic uses more than one XFNSH within a 23 hour period and/or a mechanic has a call out that goes over midnight where an XSCON is created in online time recording.
The report will only run for mechanics using online time recording and records on the dates printed should be reviewed.
The report will not run from the manual time recording function, if using manual time recording you should be aware of the rules before using the system!
System Generated XFNSH Report THP666:
This report will run if a mechanic hasn't clocked off within a set period (controlled by parameter TIM 002). The next time a mechanic makes a clocking within online time recording then this report will run.
System Generated Breaks and XFNSH:
Breaks will be inserted automatically (where the start and end time is not within the break spell) when an XFNSH record is added based on parameter TIM006. These cannot be deleted so if a user works through these then these will need to be amended to the previous order/operation.
An XFNSH record will be added at the end of day if the Scheduler is set up within the Daily batch. This can be set to run XXX minutes + rounding after the end of each shift core time.
Core Time Calculation - Overtime Apportionment:
The system can calculate core and overtime apportionment in three very different ways. Depending on a parameter setting, (TIM010) one of the following will apply:
Overtime is only apportioned once core hours are complete.
Populate payment codes on a time basis compared to the shift clocking times. This means that payment categories are applied at the set times within the clocking pattern, regardless of the hours worked. For example if a user clocks on at 16:00 and overtime starts at 17:00, then overtime will be apportioned from 17:00 onwards.
Populate payment codes as mechanic start time equals shift start time at all times. This is similar to the first method. However, regardless of his start time he must complete his core time before the overtime is applied. For example, if the user clocks on at 3:00 and works to 18:00 then the first 8 hours would be basic hours, followed by overtime (in the first option, overtime would be applied between 3:00 and 8:00 and then basic hours applied after that).
How to Create Shifts:
When creating night shifts that start in the evening of one day and end in the morning of another day, then the shift detail must be set as follows:
The hours worked on a Saturday will only be those from Midnight on Friday until 6am Saturday when the person 'clocks off'. When viewing the shift by mechanic it appears that the person only has Sunday off, which of course is not correct.
|
From |
To |
Down |
Core |
Cat |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
Sun | |
|
0000 |
0600 |
50 |
Y |
NA |
N |
Y |
Y |
Y |
Y |
Y |
N | |
|
0000 |
2400 |
|
|
NC |
N |
N |
N |
N |
N |
N |
Y | |
|
0600 |
2200 |
|
|
NB |
N |
Y |
Y |
Y |
Y |
N |
N | |
|
0600 |
2200 |
|
|
NC |
Y |
N |
N |
N |
N |
N |
N | |
|
0600 |
2400 |
|
|
NC |
N |
N |
N |
N |
N |
Y |
N | |
|
2200 |
2400 |
|
Y |
NA |
Y |
Y |
Y |
Y |
Y |
N |
N | |
The Shift pattern will look like this:
(NITE) Nights - From 22:00 To 24:00 Monday
(NITE) Nights - From 00:00 To 06:00 & 22:00 To 24:00 Tuesday
(NITE) Nights - From 00:00 To 06:00 & 22:00 To 24:00 Wednesday
(NITE) Nights - From 00:00 To 06:00 & 22:00 To 24:00 Thursday
(NITE) Nights - From 00:00 To 06:00 & 22:00 To 24:00 Friday
(NITE) Nights - From 00:00 To 06:00 Saturday non-working day (Works early hours of the morning)
What else would you like to do?
Related Topics
Set up:
Parameter TIM 002 controls the number of elapsed hours before GDS should automatically create a finish record for a job when a mechanic does not clock off. (See system generated XFNSH Report above).
Parameter TIM 010 controls the appointment of overtime. (See Core Time Calculation above).
Parameter TIM 005 controls the set up of rounding’s within the shift clocking table.
Parameter TIM 006 controls the set up of fixed breaks and also conditions the creation of XFNSH records via the scheduler. (Note based on the setting of TIM005)