Optimization results

Understand how to interpret and analyze optimization results in Skedulo.

Overview 

The Results page provides a summary of an optimization run. It includes a Gantt chart preview of the schedule, a map and travel data overview of routes, and list views of scheduled and unscheduled work.

Results pages are available from both the Background tasks button and the Optimization history page. 

Finding the optimization results page

Optimization results are shown for each optimization run, including both one-off and scheduled optimization runs.

For one-off optimization, you can click Ready to view results in the Background tasks menu to view the results page of any optimization run from the past seven days.

Schedule preview

The Schedule preview tab is the default tab of the Optimization results page, and appears as follows:

schedule preview tab

Schedulers can apply or reject the results from the Schedule preview tab.

  • If the results are rejected, they cannot be applied to the schedule later, but they can still be viewed from the Optimization history page.
  • If the results are accepted, they are applied to the schedule and can be viewed on the swimlanes.

Routes

The Routes shows a day-by-day view of their allocations plotted on a map with the suggested routes they may make as they travel and undertake their allocated work.

the routes tab on the Optimization results page

The default view shows the first day of the schedule window. Move between any date within the schedule window using the date picker.

the date picker on the Routes tab

Each resource scheduled to work for the selected day will appear on the map. Resources are represented by their personal avatars, which are placed on their home address.

Work allocations are represented by small nodes that are placed on the road outside the address given. The node that represents the resource’s first allocation of the day is labeled with a 1.

Hover the cursor over an avatar or node to display more information.

the map on the Routes tab with a resource and their work allocations

The table to the right of the map displays a summary of the selected day in terms of the number of jobs undertaken, the travel time, and the distance traveled along with the total travel and distance for the whole schedule window optimized.

the summary table on the Routes tab

Scheduled work

Jobs that were scheduled in the optimization run are listed with their job number and type, start times, and allocated resources.

Unscheduled work

Jobs that could not be scheduled, or were removed during the optimization run, are listed along with the reason for their status.

There are several possible reasons why a job may remain unscheduled or be descheduled. See Unscheduled reasons below for a complete list of possible causes.

Unscheduled reasons

Jobs that remain unscheduled after the optimization run are listed in the Unscheduled tab of the Details page.

Unscheduled reasons fall into two categories – job reasons and resource reasons.

Job reasons are non-resource specific, such as job time constraints.

Resource reasons are resource specific, such as having missing skills or a missing resource tag. All resource reasons will have a resourceId associated with them.

Resource reason templates follow this pattern:

  • Single resource: Resource <Resource.Name> <reason>
  • Multiple resources: X resources <reason> — with a tooltip listing the affected resource names
Reason Reason template
Resource has exhausted availability (no time constraint or job time constraint is within their availability window) Resource <Resource.Name> does not have enough availability to be allocated to the job.
Resource has for no availability in job time constraint window Resource <Resource.Name> does not have availability for the window(s) of time the job can be scheduled in.
Resource is missing critical skills to do the job Resource <Resource.Name> is missing the following required skill tags: <Tag.Name>
Resource is excluded or not included from the account (and an inclusion list exists)

Resource <Resource.Name> is restricted from working with the account <Account.Name>

Resource <Resource.Name> is not allowed to work with the account <Account.Name>.
Resource is excluded or not included from the location (and an inclusion list exists)

Resource <Resource.Name> is restricted from working at the location <Location.Name>

Resource <Resource.Name> is not allowed to work at the location <Location.Name>.
Job cannot be fully allocated to a resource Resource <Resource.Name> had no feasible time window for this job due to one or more constraints.
Resource has no feasible time window for the job Resource <Resource.Name> had no feasible time window for this job due to one or more constraints.
Resource would exceed their maximum working hours for one or more periods within the scheduling window Resource <Resource.Name> would exceed maximum hours for one or more periods within the scheduling window.
Resource would violate custom constraints for one or more periods within the scheduling window Resource <Resource.Name> would break custom constraints for one or more periods within the scheduling window.

Excluded work

Excluded jobs are those that cannot be considered in the optimization problem.

In most cases the Excluded tab will not appear, as the majority of excluded jobs are out of scope of the run. When it does appear, it indicates jobs that were requested but could not be matched to the regions specified in the optimization run.

Excluded reasons

Reason Reason template
Job is outside of the regions requested in the optimization run The job was from a different region than the region(s) being optimized.