Skip to main content

Hi Experts,

We have a customer query on checking the feasibility of tracking technician location in real time (or closer to real time).

From the out of the box parameters, I know that we can set the ‘LOCATION_TRACKING_INTERVAL_MIN’ parameter and get the location in about 5-minute frequency (at the latest). But the requested feature would require something more than the above setting.

 

Is there a possibility to achieve this either from configurations or customizations? 

And how much of an impact it will have on the overall performance.

What’s their expected business value of tracking techs at shorter intervals? And do they need to see this is IFS Cloud or PSO or can it be any map solution?


What’s their expected business value of tracking techs at shorter intervals? And do they need to see this is IFS Cloud or PSO or can it be any map solution?

Customer is expecting to integrate the location data into another application which provides the end user (the contact person of the task location) the ability to track the technician when he/she is on the way to the job.


There is also a Last Mile Portal solution from IFS as part of the Customer Engagement (CE) module, which shows the end customer the location of their assigned technician, it updates the location every 60 seconds. I am however not sure if it would be feasible to get such frequent updates from MWO - @Rukmal Fernando can you provide a suggestion?


@Alexander Heinze I agree, MWO isn’t intended or designed to provide near-real time location updates. 

@IniNimesK does the customer have a 3rd party app that can provide the location updates, that MWO can invoke?

Best regards,

Rukmal


Another alternative would be a dongle in the vehicle that transmits the location data independent from apps.


Hi ​@Alexander Heinze 

 

Is there a way to see the technicians (service resources) locations to dispatchers. I saw there is an option in Dispatch Console called View route.

But, it is only for one resource. Can we see a cluster of techs in a nearby area. That will be helpful for dispatchers.

 

TIA.


Hi ​@Alexander Heinze 

 

Is there a way to see the technicians (service resources) locations to dispatchers. I saw there is an option in Dispatch Console called View route.

But, it is only for one resource. Can we see a cluster of techs in a nearby area. That will be helpful for dispatchers.

 

TIA.

Can you try submitting location data from MWO? You should see the resource location on the map.


Hi ​@Alexander Heinze 

 

Is there a way to see the technicians (service resources) locations to dispatchers. I saw there is an option in Dispatch Console called View route.

But, it is only for one resource. Can we see a cluster of techs in a nearby area. That will be helpful for dispatchers.

 

TIA.

Can you try submitting location data from MWO? You should see the resource location on the map.

HI ​@Alexander Heinze 

 

We have MWO users with GPS enabled. Even though resources are fetched, locations are not showing in the map. Do we need more prerequisites?


Did you look at the DC chapter in IFS Cloud - Scheduling demystified (24R2) | IFS Community regarding map visualization? Also check the MWO parameters in IFS Cloud - MWO Service demystified (24R2) | IFS Community and check if the locations actually arrive in IFS Cloud.


Hi ​@Alexander Heinze 

 

Thanks it is working.

One more thing. I need to know what will happen If we choose Gps Enabled = False in Installed App Details.

Does that only stop system tracking the exact location of techs while allowing techs to use all other GPS functionalities such as navigation? Then the resource location is also not fetching to dispatch location?

We have a requirement for not monitoring techs location in some areas while only giving them location and navigation options.


Thanks,

Kasun.

 


Switching that off will prevent MWO from sending location data to IFS Cloud. Essentially the same as not allowing the app on the device to access the location. It only affects MWO i.e., other apps for navigation are not affected.


Reply