#Fsl Scheduling0 人正在讨论

Hello all,

I have a number of issues which I'm hoping this brilliant community could help...

Issue #1

I'm seeing violation error messages from Resource Availability work rule - *** must have a gap at least xmins *** in almost all cases when I bulk load SA which assign to the same resource. Work rule settings wise - Travel home is set to blank (or zero) , Fixed Gap unticked. Break Start 12:00, duration 30 mins.

How do I stop the rule violation from occurring?

Issue #2

Also pls refer to my screenshot (ending 345) - why did FSL put the break at the end of the day? Humanly, it doesn't make sense?

On another screenshot (ending 538), the first appointment's travel time is before the start of the operating hour - setting the resource rule travel from to blank will put the start on the start of the operating hour and the travel time before the operating hour.

However, setting the resource rule travel from to zero will shift the starting time beyond the start  of the operating hour but the travel start time is still before the operating hour start time. how can i make the travel time to start at the start of the operating hour i.e not at the resource's own expense.

Issue #3 

I tried to use Fixed Gap settings to overcome the above issues - in Resource availability rule, fiexed gap ticked and minimum gap set to 10 mins, what happened with this was even bizzare, it scheduled the SA today starting at the current time but travel time was set to the past...i.e if current time is 15:00. Start time will be 15:00 and the travel time line started from say 14:15, in the past.

I hope someone could help me understand and point me to the right settings.

Thanks

Firman.

Hello!

I have couple of questions with respect to FSL Scheduling, Drive Time and Resource Absences.

1. I have a resource absence with "Non Availability" as the record type on few of my service resource's calendars. With the resource absences what I am trying to achieve is that the resource is not being assigned service appointments on their calendars where they should not be required to drive during the resource absence timeframe. For example, I have a resource absence from 10-11AM on a service resource calendar, I want FSL to return the 1130AM slot only if the drive time is less than 30 minutes. If the drive time is more than 30 minutes, I don't want FSL to return 1130 as an available slot for this resource. Is this possible? If yes, what is the process to make this possible? I looked up to Work rules but couldn't exactly relate to my usecase.

2. I have time slots setup in my calendar for 1 hour duration work types. For Example, 8AM-9AM, 10AM-11AM & 12PM-1PM. The slot 10AM - 11AM was taken(Service Appointment Scheduled) to a resource. When using FSL.AppointmentBookingService.GetSlots method, we see the slot 8AM-9AM being returned as an available slot, however the estimated travel time between the 2 Service Appointments(8AM-9AM and 10AM-11AM) is more than 60 minutes(9AM-10AM). If the drive time is more than 60 minutes which is the maximum allowed drive time between appointments, why would FSL return the slot at 8AM as an eligible appointment that the same resource could perform? Is there anything that I am missing in this that could relate to my usecase.

Many thanks in advance for any help/direction on this.

Thank you.

Hi @Steve Hupp /All -

We have use case where 

1.Technicians are travelling by air within USA and working on appointments in other corner from his/her home location(assuming they are secondary resources on multiple territories) and 

2.Additionally - these same technicians can work on local appointments(in Primary territories and can travel by Car) whenever it's needed.

3.Point to mention is - Mostly Appointments are multi-day.

Now -

1. Whenever they are travelling locally - gantt is showing Travel time correctly (Start and End ) - Working as designed.

2.In case Air travel we don't want gantt to show and Scheduler Engine to block resource time - As we know - for air time we cant predict travel details and its not even supported in Product.

e.g. here by using resource address and Appointment address, resource are getting blocked for entire week using default travel calculation and dispatcher /optimization will not able to use that travel time period to book other appointment(except if we forcibly book using drag-drop with rule violation).

3.In reality resources are travelling by air and we are planning to show resources air travel(to and from air travel dates-entire day and  these dates are with SA start and End date- we can easily figure out total duration and travel duration - this is also working good with some customization) on gantt by using Resource Absence with new value in Picklist type - Travel/xyz.

3.In order to Prevent automatic travel calculation - I am thinking to remove address from SA if resource is planning to travel by air.- In this case Scheduling will not calculate to and fro travel time and resource will be available for other Appointments during that period.

Could you please suggest if you any better/alternate solution for this work in order to ignore travel time calculation for long distance/air travel appointments.

CC: @Leigh-Anne Nugent

#SFS #FSLOfficeHours #FSL #Multi-day #AirTravelling #Fsl Scheduling #TravelTime