Defining Average Travel Speed for Some Areas in PSO/IFS Cloud Integration

You probably don’t want to specify this on the technician, but just for the geographical area? The only option I would know are Areas/Area Weightings/Barriers maintained directly in PSO. See Scheduling Concepts - Travel.pdf

They would specify an average, but rather a factor to multiply the calculated travel time with. Can even be by time of day.

Did the customer purchase the HTM for the UK? 

Hi Alex, 
yes, the client uses the HTM matrix for the UK. 
I was thinking of Areas/Area Weightings /Barriers, not sure if it works well in integration with ifs Cloud and if it would fit my scenario

Okay, cool, so they have a starting point already. All these are completely maintained in PSO, so there should not be anything to be considered on the IFS Cloud side. To test I usually enforce a specific route during a specific day/time and see if there is an effect on travel time.

Is it correct after all to say that it is not necessary to create an IFS unTravel profile on the Cloud as I have done in the image below?

On Cloud: 

Thanks

You still need the Travel Profile in IFS Cloud to be able to associate it to a resource/resource type, but the actual administration of the profile happens in PSO.

I haven’t tried this myself TBH, so you may want to try one resource with and one without the profile and see if the logic is applied. When you succeed, please share… 😉

I have tried as you suggested with only one resource and route in the area, but unfortunately nothing seems to change in terms of travel time. Within the load file, my resource has the travel profile I set by IFS CLOUD, so the information is received by the PSO. Is there something I am not considering?

Hi Alex,

I had tried exactly as you indicated but used too low  a weight and could not see the real advantage. 

It works! 😁
Thank you as always for your helpfulness and support.