Use RSO from the schedule board
After an organization defines its goals, scopes, and schedules, it needs to manage and automate its scheduling. Dispatchers or schedule managers can use the schedule board to gain deeper insight into how items are being optimized, review results, and work with optimization requests.
Use the schedule board to help with optimization
By using schedule board integration, organizations can:
Understand optimization scopes better - Each optimization scope that is created is available from the schedule board. When the scope is selected, any resources, requirements, and bookings that are within the scope are displayed on the schedule board.
View optimization results in a visual way - As results are optimized, they're displayed in the familiar schedule board interface to make it easier for dispatchers or resource managers to understand the results.
Analyze failed optimization requests - Detailed information on optimization requests, including details on items that failed to be optimized, are available. Organizations can identify why specific items failed and make modifications as needed.
Create a new schedule spontaneously - New schedules can be created and run from within the schedule board as needed.
The following image shows an example of what the schedule board looks like when it's being used to take advantage of optimization functionality.
The following features are offered in the schedule board, as highlighted in the image:
Pre-populated filters match the filters that are defined for the scope that is currently being used.
The Open and eligible for optimization tab shows all eligible unscheduled requirements that match scope definition, requirement range, and requirement state setting.
The Eligible for optimization tab shows all eligible unscheduled requirements and any eligible bookings to be reoptimized that match scope definition, requirement range, and requirement state setting.
The Excluded from optimization tab shows any eligible requirements or bookings that fail to be optimized for certain reasons (such as invalid longitude/latitude).
The icon and corresponding tooltip in the corner of the resource name record indicates that a resource isn't in the optimization scope.
The lock icon and tooltip indicate that the booking is locked.
Yellow lines indicate the start and end time for the optimization range.
The From and To dates and times match the time range that is defined in the optimization scope.
These ranges can be modified from this screen, and any changes that are made can be saved back to the original scope.
Note
If the same scope is being referenced by multiple optimization schedules, the change applies to all of these schedules with the same scope.
After a goal is defined, you can run optimization requests on demand by selecting the Run Now button.
Show the status and details of the optimization request.
If an exception occurs, the request can be opened to view details.
This option also provides booking details and analytic charts that show how many hours of travel time versus how many work hours are scheduled for this run.
Having the ability to use a schedule board can be useful in scenarios where a dispatcher might need to evaluate what is happening to help dictate scheduling decisions.
For example, a dispatcher might examine an optimization scope that was created for working with items and resources in the state of Washington. When the dispatcher selects the Washington scope from the schedule board, they can see which resources, requirement records, and currently scheduled items are within the scope. If the dispatcher wanted to modify the date range of records that are involved, they can make those changes directly from the schedule board. If those changes need to be reflected in the scope moving forward, they can be saved directly to the scope from the schedule board.
If the dispatcher is currently more concerned with maximizing productivity instead of finding the most qualified technician, they could determine which optimization goal to use. If items are set to run as simulations, the dispatcher could simulate the results first, and then determine which one would be most effective before applying it.
See Using the schedule board for optimization results.
When resources aren't being assigned to bookings
When you first run optimization jobs, you might notice that some (or all) resources aren't assigned to bookings. While many different reasons for this occurrence exist, the likely reason is related to resource configuration. Improperly configured resources can lead to issues such as:
The resource not being within the defined optimization scope
Not having the appropriate settings defined on the resource record to ensure that it can be optimized
In this situation, your first step is to review the optimization results from the schedule board and examine the corresponding optimization request job. This action lets you examine the resource view that identifies which resources were in scope so you can start looking for reasons why bookings aren't being scheduled.
Consider the following items that are related to resource records:
Territories - Determine whether your resources have related resource territories that match requirement territories.
Resource attributes - Always verify that the Optimize Schedule field is set to Yes. Additionally, consider the following parameters:
If your resources have a start and end location set
If your resource locations have geocodes
Organizational Unit Address' geocode is held in the related Organizational Unit
Resource Address' geocode is held on the related resource's user, contact, and so on
Resource characteristics - Establish whether the resource has any of the required characteristics and required skill levels.
Resource work hours - Verify if the resource's work hours are configured and if they're available during the optimization range.
If they're unconfigured, they could still be scheduled.
They might be set to not work on the days that are being optimized according to the RSO run scope.
Additionally, consider if the resource has any items such as time-off requests that were created or approved for the period that is being optimized.
Resource status - Check if the resource's status is set to Active. If it isn't, then the resource is likely not to be included if the scope is looking at active resources.
Resource preferences - While this scenario is unlikely, examine if any resource preferences would exclude the resource from consideration from all their possible work orders and resource requirements.