Skip to main content

Hello,

I am currently working on a FSM-PSO solution where the field technicians of the client work on an external custom app. 
The field tech is gonna have a number of tasks pre-allocated sent by PSO at the start of the day and as he completes one, more are sent. 

Everything is fine until the field tech may get sent to a place with no service (no internet and/or no phone service) for several hours and complete all the tasks assigned without being possible to communicate with PSO.

In this case, there is also a scenario in which he could complete a given task(change its status offline) and go to the next one he has in his phone (previously sent). 
Because he is without coverage, the updates won't go to from that external legacy app to FSM and as a result PSO won't be updated with the right status therefore for PSO it would mean that he is still doing the second task and once the app goes online he will receive all the updates but potentially this will have an impact on the optimization since he could go to the next task without taking into account more nearby tasks.

Anybody has a good approach that could handle this scenario?

 

Thanks

Hi Jose,

There is a rule commit override for areas with lack of coverage.

If you use this commit rule you can increase the number of activities sent to the mobile and the time horizon if a location is known to have poor mobile coverage (such as an underground location).

Hope that helps,

Tom


Reply