Segmentable Activities Assignment Using Bulk Routing

You can now route segmentable activities using Bulk Routing. Whether you route the segmentable activity from the bucket using Immediate Routing or Bulk Routing, the assignment rules are the same; the routing plan (Immediate or Bulk Routing) either assigns the whole activity to a single resource or leaves it in the bucket.

Note: Earlier, you could assign segmentable activities to a resource either using manual move or through Immediate Routing.

Both Immediate and Bulk Routing observe these rules for segmentable activities:

• Work zones—the resource's work zone must match the work zone of the activity

• Work skills—the resource's work skills must match the work skills required by the activity

• Resource preference—routing should assign the activity to preferred resources or only to required resources, if specified

• Service window—routing should observe the activity service window for all the segments

• Access hours – routing should observe the activity access hours for all the segments

• SLA start—the SLA start of the activity observed for the first segment

• SLA end—the SLA end of the activity observed for the last segment

• Minimum segment duration for a single day <> minutes – indicates that those segments having lesser than minimal duration are not created

• Maximum segment duration for a single day <> minutes – indicates that the total daily amount of segments cannot exceed the configured value. (with the exception for the days containing the last segment of activity, which can exceed the configured amount but the remainder cannot be more than the minimum segment duration)

However, during the initial activity assignment, Immediate Routing optimizes only start/finish time of the segmentable activity. Bulk routing also tries to optimize travel time to and from each activity segment and overtime, overdue and other parameters of the segment the same way as they are optimized for single-day activities.