Skip to main content
Solved

Long Duration Activity


Forum|alt.badge.img+9

In a Service Order for the open activity you can swith on “Long Duration Activity” for activities with a longer duration then the shift of the engineer. 

In Disptach Console, you see the actvity split over multiple days.

 

But in the work order in Mobile Edge, the engineer only sees 1 activity.

How can the engineer enter the travel and activity executed on both days like indicated in DC?

  • first day: start travel - start work - stop work
  • second day: start travel - start work - stop work - resolve order

Best answer by Roy Rahav

Hi,

You need to separate between activity and visits. 

The long duration activity divided to visits according to the service agent's shifts (for example: if the activity's duration is 24 hours and the agent's shift is 8 hours, the activity will divide for 3 visits).

Those visits are visible only on the Dispatch Console (and on DB).

When the engineer finishes his work on the first day, he should complete this activity by using incomplete stop code and then new activity will open, depend on setup. 

For example: the new activity can be set with long duration activity code, assigned for the same agent and using the remaining duration.

There are multiple ways to define this stop code setup. 

Now there is a new activity (for the same order) that will divide for visits if needed. 

On the next day, the agent will report his start travel - start work - stop work - resolve order for the second activity as he did on the first day, and so on until all the work is done. 

View original
Did this topic help you find an answer to your question?

2 replies

Forum|alt.badge.img+1
  • Do Gooder (Employee)
  • 4 replies
  • Answer
  • May 28, 2024

Hi,

You need to separate between activity and visits. 

The long duration activity divided to visits according to the service agent's shifts (for example: if the activity's duration is 24 hours and the agent's shift is 8 hours, the activity will divide for 3 visits).

Those visits are visible only on the Dispatch Console (and on DB).

When the engineer finishes his work on the first day, he should complete this activity by using incomplete stop code and then new activity will open, depend on setup. 

For example: the new activity can be set with long duration activity code, assigned for the same agent and using the remaining duration.

There are multiple ways to define this stop code setup. 

Now there is a new activity (for the same order) that will divide for visits if needed. 

On the next day, the agent will report his start travel - start work - stop work - resolve order for the second activity as he did on the first day, and so on until all the work is done. 


Phil Seifert
Ultimate Hero (Employee)
Forum|alt.badge.img+23
  • Ultimate Hero (Employee)
  • 1293 replies
  • May 28, 2024

Hi Piet,

I confirm there is not a possibility to add multiple start/end travel on a single activity in Mobile Edge.  If the activity is flagged as a long duration, it still will be treated as a single activity and Edge can only indicate a start and end travel once on the single activity.

Roy, I am not sure the customer wants to have multiple activities to manage/report to their customer which is the result of performing an incomplete that completes the activity.  

What I might consider is to create new expense codes to reflect the additional travel distance and time so these can be recorded separately as expenses.  It is a process change I am sure but I don’t see any other way to do this at this time except taking the long duration activity and splitting it up as you suggest with the incomplete stop code.

 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings