Search Knowledge Base by Keyword
< Back
You are here:

Service Delivery Report

WebEye Service Delivery Report

Service Delivery report shows how much time is spent on site by all your staff. It calculates for the site as a total, but shows each individual staff member and the time they spent.

Key to this report is measuring time between actual attendances. Since staff must be on site to log data, this report measures when staff are actually performing their duties on site. That’s why we call it ‘Service Delivery’ as they were doing exactly that.

For example, if you have 10 staff, then it will show for each staff member, how much time was spent on the site. This time will be broken up into ‘Service Bands’ of start-finish times that cater for split shift sites. Each service band shows a start and finish time so an analysis of site attendance is easily done.

It also shows a total time on site for all staff.

* A similar report is “AtSite Hours On Site” – this report show only login and lougout time accumulated. It does not look at attendances.

How Accuate Is this Report?

It is very accurate for time on site. It counts time between staff attendances at locations on your site so it measures when they are doing work on site. Since data is only logged when on site, you know your staff were actually there!

This does not take into account extended time spent getting ready before actually getting on site. It does not included extended time doing paperwork when data is not being logged, and the same for extended time doing back of house functions. If staff wander off for some reason, this will also be taken into account.

To accumulate time on site, they must actually be on site.

Calculation Method

For each staff member logging data, WebEye Service Delivery report counts the time between attendances. Since staff may take a tea break, they may do other jobs where data is not being logged, the system takes this into account in a simple way. It is able to cater for split shift sites, continuous staff sites and combinations.

It does this using the ‘Maximum Service Gap’ parameter. This is used to specify the maximum number of minutes between attendances that a staff member will be considered still on site. So, to cater for a tea break, this can be set to say 45 minutes. If there are no attendances for a staff member for longer than this time, then they will be considered not in site and only the previous times between attendances used.

Here is an example. “Bob” arrives on site at 6am. Then he gets his equipment ready. He signs in. He does some housekeeping functions. Then he starts work on site and his first attendance is at 6:30. Then for the next few hours he is walking around the site collecting more attendances. He has a 15 minute break. Then Bob goes home at midday. His last attendance was at 11:45 as he had to clean up his gear and finish his paper work. Then Bob returns to work at 2pm and works for 3 hours. He logs attendances with just a few minutes missed as a result of paperwork and setups.

So, Bob has 2 service bands of time delivered. One from 6:30 till 11:45. The second from 14:10 till 16:45 (remember time not logging data). The report will show the exact times of service and the total time on site for him and any other staff.

How Does it account for the split shift? The Maximum Service Gap is set to, say 30 minutes. When Bob leaves site, the gap is 2 hours. Hence with the 30 minute maximum, Bob will be considered not on site and hence the time accumulated will be correct.

Does the time include the Maximum Gap? No. Bob left at midday. His last attendance was 11:45 – so only time up to the last logged attendance is used.

What About the 15 Minute Break? This depends on the Maximum Service Gap option. If this is set to longer than his tea break, then Bob’s tea break will be counted as time on site (since he was off site for less than the maximum). However, if it is set to 10 minutes, then the tea break time of 15 minutes of not logging data will not be counted.


Previous Application Ideas
Next Insufficient Logins
Table of Contents
Close Menu