When collecting data real-time, the system will track time for you. The only thing the user needs to do is start a (new) activity whenever a new activity occurs.

Whether the system should count time- or not is determined by checking the actual time versus the time of the shift that is being registered.  When not entering a duration within 60 seconds after adding a new activity, the timer will start automatically recording the elapsed time. However, if you want to change the recorded (start or duration) time (i.e. you started the recording too late) this is possible. The system will always support you to have all activities in a sequence without ‘lost time’.

How does it work

Example 1:

The shift has started at 7:00 with [Heating the equipment].

At 7:30 you start a new activity: [Filling Raw Material].

• Activity [Heating the equipment] will automatically get a duration of 30 min. (from 7:00 till 7:30)
• Activity [Filling Raw Material], started at 7:30, is now waiting for your action. If you do not enter a duration, after 60 seconds the timer will start counting time of the duration
• The timer keeps counting time until you add a new activity. The elapsed time will be the duration of the activity that now has ended.

At the beginning of the shift, most probably, the first activity will not be added exactly at the start time of the shift. The system will do so for you.

Example 2:

The shift starts at 7:00.

At 7:08 you add the calculation for this shift and start to add the first activity: [Shift Meeting]. The system now assumes this will have actually started at 7:00, so already 8 minutes have elapsed.

If within the next 60 seconds you add a new activity, the [Shift Meeting] get a duration of 8 min. and the next activity starts. If you do not add a new activity, nor change the duration of the [Shift meeting], after 60 seconds the timer starts with an elapsed time of 8+1 minutes.