Activity duration estimate example¶

A simple example of using an activity duration estimate is outlined below.

An activity of activity type 'type1' is sent to the DSE to be scheduled with duration set to 8 hours and not requesting to use auto-duration (auto_duration_enabled=false). The activity gets scheduled by the DSE on the first day of his two shifts at 9am, expected to take 8 hours to complete. See below screenshot of activity on-site at 9am on the first day:

Later on in the first day, at midday, the activity is actually completed early - 4 hours after it has started:

Once the Archiving service has processed a snapshot of this scheduling data, it analyses the activities and estimates that the good duration estimate for this type of activities (type1), is 4 hours and adds a record (or updates if it exists previously) to the Activity_Duration_Estimate table for this grouping of activities (of activity type 'type1') with column values:

On the next day, when a new activity of the type ('type1') is sent to the DSE to be scheduled - this time asking for an auto duration, if it exists (auto_duration_enable=true). The Input Manager recognises that there is an activity duration estimate for this activity of 4 hours, and sets the auto_duration to this. The auto_duration is used in turn by DSE to schedule the activity:

If the activity had not requested for an auto duration, the activity would be scheduled with a duration of 8 hours: