In ecTA/ecPayroll System, “Time Attendance Analysis” is a
process which compare the Duty Roster (i.e. required working time) and the
actual clock IN/OUT records (i.e. actual working time) to calculate the
attendance result such as Late-IN, Early-OUT, Overtime, Working hours, …etc.
In ecTA/ecPayroll System,
user can provide the duty roster by defining some “Duty Rules” that may apply
to a particular period that may be a week, a month, or 6 months, or 2 years, or
even anytime. If a Duty rule was changes, all attendance result within the
defined period will be affected. If the system was designed to auto run the attendance
analysis, which may spend a lot of time or causes system halt. Therefore, the
“Analysis” process was extracted to be run separately and trigger on demand.
Before you can see the correct attendance
result on screen or report, the analysis process must be run. Normally, the
process will be configured to run automatically, say 2 AM on every day, by
adding a “Time attendance analysis task” in “Automation Server”. So that you will have your attendance
result in next day morning. Besides of this regular, scheduled task, sometimes
you may want to run the process by manual.
Below are some examples:
Scenario |
Action |
Objective |
Boss
wants to know who were late in this morning and don’t want to wait until next
day. |
Manual
run “analysis” for all staffs but today only. |
To
calculate this morning attendance to see if anyone was late. At this moment,
all status will show “No OUT”. It is normal as the staffs have not yet clock
OUT. Note that the scheduled process to be run in mid-night will not be
affected. |
The
settings of a Shift was changed. The changes should be effective since last
week. |
Manual
run “analysis” for the staffs who may involve, and all dates since last week. |
To correct
and update the attendance data since last week, based on the new Shift
settings. |
Missing
clock IN/OUT records yesterday due to suspension of electricity. |
Manual
run “analysis” for all staffs but yesterday only. |
To
correct and calculate attendance for yesterday. Before running analysis, the
attendance status should be “Absence” because no clock IN/OUT record found. |
The
roster of last week was not yet input to the system. |
Input the
roster and manual run “analysis” for all staffs since last week. |
To calculate
the missing attendance records since last week. |
The card
number of a staff was incorrect. |
Correct
the card number and manual run “analysis” for that staff for all affected
date. |
To
correct the attendance result that showing “Absence” due to mis-match of card number. |
|
|
|
In the system, there are several places can
trigger running the “analysis” process as follow:
|
Where to run |
Characteristics |
|
1 |
Back-end
> Automation Server > Add “Analyse Attendance Result” task |
Auto,
scheduled, all or group of staffs |
|
2 |
Back-end
> Access Log > [Analysis]
button |
Manual,
selected staffs by EE filter, selected date range |
|
3 |
Back-end
> Timetable > Right-click on
the Attendance Result |
Manual, 1
staff, 1 day or 1 period |
|
4 |
Back-end
> Employee > Attendance > Daily
Attendance Result > [Re-analysis] button |
Manual, 1
staff, 1day |
|
5 |
Front-end
> Retail Web > Timesheet > [Analysis] button |
Manual,
selected staffs, selected date range |
|