web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Service | Customer Service, Contact Center, Fie...
Unanswered

RSO moved bookings overlaps with a present bookings

(0) ShareShare
ReportReport
Posted on by 10

Hi,

In our Field Service solution, the RSO is used to optimize scheduled bookings. The bookings are time-locked and may only move between resources. However, the RSO is moving bookings to a position that overlaps with existing bookings (see example).

Note:

  • The resources workhours have capacity set to 1
  • The booking record 'allow overlapping' is set on No
  • RSO Goals objectives 1) Locked bookings 2) Minimize total travel time 3) Maximize total working hours
  • Engine effort level: Highest

In the RSO documentation, I did not find information to troubleshoot this issue.

Examples:

00025.png

6153.png

5140.png

 

Did anyone else endure similar outcomes from the RSO? and have a found a solution or a clarification why the bookings overlap?

Thanks in advance.

 

I have the same question (0)
  • JCo Profile Picture
    305 on at

    Are the overlapped bookings impossible? Do they have some attribute that makes them impossible to satisfy: Time Promised/From-To window that cannot be legitimately satisfied, Characteristic that noone has, territory that is not able to be fulfilled, etc.

    If the RSO determines that the bookings are impossible to satisfy, an overlapping booking may be made.

  • D.R.K. Profile Picture
    10 on at

    Thank you for the reply.

    If I understand correctly you suggest that the bookings overlap due to the booking being impossible to satisfy by the RSO. It still seems odd that the RSO decides to ignore a booking and positioned another booking on top of an existing booking (which is impossible to satisfy). Is there a way to prevent a potential creation of an overlapped booking.

    Moreover, the fields Time Promised/From-To window are not used and contain no value. Moreover, there should not be a conflict with characteristics or territory satisfactory is functionally wist the support of the planning assistant. The values that vary between the bookings which are moved by the RSO and which are impossible to satisfy are the address, resource, and booking-related Date/time fields and they contain bookable values such as geocoding.

    Our RSO setup is optimizing the schedule for 100 resources with around 800-1200 bookings in 14 days spread. Is it possible that the input is too large? Even if the RSO is triggered four times in an hour (during midnight) and on the highest-engine level?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 49 Super User 2025 Season 2

#2
Daniyal Khaleel Profile Picture

Daniyal Khaleel 27 Most Valuable Professional

#3
Soundari Profile Picture

Soundari 15

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans