Skip to main content

Our business has some activities that will not allow travel.  As in the customer is not willing to pay travel time on these work orders as they know that there will be other work orders that will already require travel, and the work can wait until such time as we travel to the site.

These will be separate work orders as the no travel work order will likely be open before a PM work order.  We do use a specific priority ID for the work tasks that have this requirement, so are easily able to identify them.

I have not been able to find any setting in PSO or IFS Apps 10 that marks an activity as not allowing travel and needing to be done while onsite on a per work task basis.  Only those settings surrounding the travel of the resources.

We are aware at times this will lead to the activity going unallocated for periods of time and accept that inevitability, but since we will not be paid for the travel on these, we never want to schedule travel on them individually, only when we have other work on the same site.

Hi,

We don’t have specific functionality to support ‘no travel’ activities, but customers with similar requirements in the past have been able to use a combination of low valued activities and ‘do on location incentive’ to achieve the desired result. 

Using a low value for the activity will mean that the DSE will not consider the activity worth scheduling unless there is very little travel involved (or even no travel if the value is low enough). A soft do on location incentive can then be used to increase the value of carrying out the work when there is other work at the same location. Note that the do on location incentive can be used both on the low valued work, and on the other work at the location, to ensure that carrying out the extra work is worth doing in this situation. 

Thanks,

Paul

 

We already have “Do on Location” set to a 2 as it is since, if possible, we want all work available at a single site to be done together at all times.  

The work orders that get opened that do not allow travel are already set at a lower default value.  They have their own priority ID and are configured that way intentionally.  But it seems since they are a lower value, PSO would rather use that extra time in the day to do other work instead, even if it means a little travel.

Reply


Terms & ConditionsCookie settings