Standard work activities
Standard work is performed as a series of activities defined by workload, lead time and offset.
Defining the sequence of activities for standard work
Click add first (another) activity
Describe the activity and hit enter or click create. Remark: the descriptions of the activities should be unique within the service.
Enter the workload = hours it takes to execute the activity. If batched enter the workload for batches with minimum and maximum runsize.
Enter the lead time = days it takes to execute the activity. If batched enter the lead time for batches with minimum and maximum runsize.
Enter the offset time = days to wait after the start of the service execution to start this particular activity. If batched enter the offset for batches with minimum and maximum size.
Leadtime and offset can be configured in calendar or working days by clicking on the underlined calendar days or working days:
- Calendar days means workload will be planned on weekend days as well
- Leadtime = 8 calendar days —> execution from Monday to Monday
- Offset = 6 calendar days —> execution starts on Saturday
- Working days means no workload planned on weekend days
- Leadtime = 8 working days —> execution from Monday to Wednesday
- Offset = 6 working days —> execution starts on Tuesday (of the second week)
Add tag to service activity
- Click add tag
- Choose one of the suggested tags in the dropdown list or enter a few letters to get a dropdown list with a more narrow selection of tags. If the tag you like to add doesn’t exist yet,create a new tag by entering a name and selecting the tag type in which you like to add the new tag.
Tip: when entering the tag name, check in the dropdown list if the tag is already created.
Remark: Per tag type you can only add 1 tag. New tags can only be added to open tag types. When no new tags are allowed, choose a tag from the predefined tag list.
You like to create a new tag type within service activity tag type? Learn how to add tag types.
Capacity profile explained
Once the activity parameters are filled out, they define a capacity profile. Workload is the bar hight. If there are more then one activity the workload can be the sum of workload of each activity.
Lead time is shown as the number of weeks.
The effect of setting the offset time is translated in the capacity profile, as the workload/week will depend on the offset time of each activity.
Total time per units = the time needed to execute one unit. If batched it’s the time needed to execute one unit in a batch with average runsize.
Total number of weeks = weeks it takes to execute one unit. If batched it’s the number of weeks it takes to execute one unit in a batch with average runsize.