The manual scheduling (w/o RSO) should be enhanced with a functionality which helps the dispatcher to find the best fitting FSE calculated with following criterias:
Skills: – Check if there resource has Characteristics mentioned in the resource requirement
Availability: – Check if there is an existing booking (regular or absence) between Start Time & end time of the Resource Requirement

Distance: – Check if the resource is nearer to the service account address

Branch:- Check if the resource belong to the branch(it’s a hard filter)

Technical Limitation today:
Data which is shown on schedule board for resource comes from a fetch xml which runs on bookable resource entity.​ For Distance Geolocation data is stored on service account and we don’t have a direct or indirect relation with bookable resource so such kind of factors cannot be included in rating calculations

In this fetchxml we can retrieve data from bookable resource entity or from a entity which is related to bookable resource .If a factor is based on an entity which doesn’t have a relation with bookable resource then we cannot retrieve data and this cannot be included in the rating calculation.​

​