For normal observation of who is onsite or offsite at a given time, Jarrison Time’s I/O Register will suffice. However the I/O Register is intended to consider the current day, not an extended time period between clocking in and out, where a person may clock “in” and be considered onsite for weeks or months before they clock “out” (with no clockings between). This article looks at how to configure the system to report on long-term clockings.
The solution will involve the use of formulas on Day Programs, and a report then triggered accordingly.
The following counters will be used: T&A Clockings, Missing Clockings, Absence, Onsite, Offsite. The last two should be set as Is a Running Total and since they will be the basis of the report they can also be checked to Include in Event Comments.
From System Configuration, the Allocations tab should have the T&A clocking counter set:
A day program with otherwise empty (unset) tabs will have the following added on the Rules tab. The only other option enabled should be ‘Work Day‘ on the Profile tab.
The first formula checks the value for Missing Clocking yesterday, and if it had a value then give it a value today. In practical terms, this line checks if a person clocked “in” on the previous day. Note this is the only line not to be marked for Post Process.
The second line checks if Missing Clocking has a value (today), if so then cancel (zero) the Absence count. Since we have an “in” clocking for the person then per assumption they’re no longer considered absent, even though there were no clockings for them today.
The third formula assigns a value to the Onsite counter, if Missing Clockings has a value. We are establishing that the person clocked in, and per the scenario assumption this means they are now considered onsite.
The fourth line checks the Absence counter, if it has a value then give the Offsite counter a value. Absence would only have a value if the person had no missing clockings yesterday, and no clockings today.
The fifth formula checks if Missing Clocking equals two, meaning the first formula condition was true and there is a missing clocking for today. Today’s missing clocking is from the person clocking “out” (the “in” having occurred some time previously and so considered missing today by the system). Per scenario assumption if we have a pair of clockings we then consider the person as no longer onsite.
The last line handles the scenario of a person clocking in and out on the same day, by checking the T&A Clockings counter; if it’s equal to two (in and out) for the day then the person is no longer considered onsite, thus assign Offsite counter a value.
Below is a Daily Summary example of a person having clocked in (10h00 3 June) and some days later clocked out (12h00 12 June) (the system still places this clocking in the “Clock In” column, as it only can see it as the first clocking of the 12th).
A report for this can be configured similarly to below from View > Report Creator.
The below report was formed by copying the ‘Absentee list’ report and modifying the trigger field to Event Name. If you’re not using counters with the event comments option, then you’ll use the Onsite counter as trigger instead.
